We are going to remove the carrier check (since VZ and AT&T carriers will NOT work with the regular Sprint webOS Doctor) and we are going to remove the model check (since there is no such thing as a Pre Plus on Sprint). The makefile is located in the "meta-doctor" directory and is called "Makefile". However, once you have the basic packages installed and in place, do the following things: I will not summarize those steps here (they are well-documented elsewhere and OS-dependent). All the initial icky steps on the meta-doctor setup involve getting the proper UNIX architecture setup to run the shell scripts that comprise meta-doctor (installing git, etc). Read these steps first, BEFORE setting up meta-doctor. I will summarize the steps that we are taking with meta-doctor. However, there are a few little things that need to be done to do what we are trying to do. I recommend following the directions located here: Application:MetaDoctor. This is actually sort of tricky and the setup process is a little different for each operating system you are running on. (Note: If you would like to upgrade your device straight to 2.1.0 and not install 1.4.5, please follow the directions for creating your meta-doctor in the #Baking_tokens_into_the_meta-sprint-pre-2.1.0_script section.) Make SURE you open "Show Properties" and have it email ALL and not just the com tokens. Then you install Preware and then install "Show Properties". To recover them, you will need to use the Activation-Bypass tool (found here: ) to activate the device as a wifi only device. The tokens are stored in the devices memory and not the communications board. Notes: The tokens can still be extracted even after you do the hardware swap. However, if you ever wish to return the Pre Plus to it's stock condition, you will need those tokens. They will not be used at all in this process. It is also a good idea to extract the tokens from the Pre Plus as well. The only supported way to get these tokens is to install "Show Properties" using Preware and have the system email you a castle.xml file directly. Each token is represented by a file with that exact name, and the value is contained in the file. The values we want to extract are ProdSN, ModemSN, BATToRSP, BATToCH, DMSVRoNONCE, DMSVRoAUTHPW, DMCLoNONCE, DMCLoAUTHPW, DMCLoAUTHNAME, DMCARRIER, DMMODEL, WIFIoADDR, BToADDR, PalmSN, PRODoID, PN. The tokens on your Sprint Pre are located at /tmp/tokens on your device. Process Step 1: Extract working Sprint Pre Tokens A moderately high level of confidence and competence with electronics is required to attempt this. The Pre is *NOT* an easy device to disassemble and especially to re-assemble. The most important requirement: the understanding that if done incorrectly, you can end up with TWO broken phones or malfunctioning phones.Meta-Doctor (get it here Application:MetaDoctor - WebOS Internals).T5 screwdriver (required to disassemble phones).Buy whatever you can get the best deal on. It also doesn't really matter if the ESN is clean or not, I used a brand new Pre Plus I got off Craigslist with a clean ESN, however the ones with bad ESN's tend to be cheaper on Craigslist or Ebay. Palm Pre Plus- It can be Verizon or AT&T, it doesn't matter.You can test if you remember them correctly at Palm's profile login page. That's the email and password you activated your Pre with in the first place. 3 Baking tokens into the meta-sprint-pre-2.1.0 script.2.7 Step 7: Have a beer! You've earned it.2.6 Step 6: Run regular Sprint webOS Doctor 1.4.5. ![]() ![]() 2.5 Step 5: Re-program your Pre Plus using meta-doctor.2.4 Step 4: Swap Sprint Pre coms board into Pre Plus.2.1 Step 1: Extract working Sprint Pre Tokens.
0 Comments
Leave a Reply. |