Hey Guys PACO here, after watching this amazing video on how to root your phone and apply the JF 1.5 ADP I am really tempted to do it. As of now I have a stock G1 but really really want to do this update. soo what do you think, should I wait till the OTA release orrrr should I just do it now. What are the pro and cons, I know I can roll it back and did it before on my last G1. SO what do you think.
Hey Guys PACO here, after watching this amazing video on how to root your phone and apply the JF 1.5 ADP I am really tempted to do it. As of now I have a stock G1 but really really want to do this update. soo what do you think, should I wait till the OTA release orrrr should I just do it now. What are the pro and cons, I know I can roll it back and did it before on my last G1. SO what do you think.
I dont think you will be unhappy ... and if you try also Moving apps to SD ... the Build in my Signature is the Build to get ...
If you want to return to RC29 and then manually update to the OTA version you will have that option...
__________________ Help Us: Submit FAQ's You have answered over and over! Will add them to OUR FAQ LIB. Check out our FAQ's.... Also Check out our Tag Search.
Soo what your saying is....I can just swap back just like that. well then...I think I know what I'm doing today...
If you want to UN-Root .. You have to flash with the Same file that took you back to Pre-Blocked Root-Acces ... then work you way back up to the most recent Legit TMO build ...
I am not sure ... but in Settings you MAY/Should be able to do a Check for Updates ... and go from there via OTA ...
I have not done this yet ... So if you do ... Please return and let me know your findings .. and how things went ... then I will add this as a FAQ to the forums ...
I dont think you will be unhappy ... and if you try also Moving apps to SD ... the Build in my Signature is the Build to get ...
If you want to return to RC29 and then manually update to the OTA version you will have that option...
Quote:
Originally Posted by justjimjpc
If you want to UN-Root .. You have to flash with the Same file that took you back to Pre-Blocked Root-Acces ... then work you way back up to the most recent Legit TMO build ...
I am not sure ... but in Settings you MAY/Should be able to do a Check for Updates ... and go from there via OTA ...
I have not done this yet ... So if you do ... Please return and let me know your findings .. and how things went ... then I will add this as a FAQ to the forums ...
Yah I tried it on the last G1 I had, there is no "Check for updates" in that build, So I guess I would have to find a legit RC33 and manually update it...if thats even possible. Otherewise wait for it to come OTA
================================================== ============
THIS GUIDE ASSUMES YOU ARE STARTING FROM A WORKING ROOTED VERSION
================================================== ============
EDIT: Here are the files you will need To Go From : Root to Legit RC33 build 1.1
Question for you. All your doing is putting the files on your fat32 sd card and naming them "update" right...? same as if you want to update to a newer JF version or whatever your just going backwards...im just curious.
I go to the link you post for Root 2 Legit (which I assume means what I want to do) and it takes me to how to root and install cupcake (which I do not want to do). I installed cupcake and need to get back to T-Mo U.S. legit.
I installed RC29, 1.0 firmware, but getting to step 2 is confusing because the link appears to be talking about installing cupcake.
All the posts on the net say "how to upgrade and downgrade."
I need to downgrade. Is there any thread that says how to ONLY downgrade.
I have the files that were posted and downgraded with the Dream file, so now I show build TC4-RC29 115247 installed.
So now what.
UPDATE: I think I see how it's done.
I simply renamed and numbered each of the OS updates and installed them in order.
E.g. gave each file a distinct name. "01 Original OS", "O2 next update" and so one.
Transferred all files to my G1 microSd chip.
Then one by one renamed each to be installed, to "update.zip"
Installed each "update.zip" file, starting with file I named "01"
Rebooted after install.
Then deleted file just installed, the one named "update.zip"
Renamed the next one in order, "02" for example, to "update.zip"
Then installed that.
Did this for all four files you provided.
I confirmed after each install that the OS had in fact been updated. It went from 1.0 to 1.1 (or builds 29, 30, 33)
Just now I installed the RC30 to RC33. "About" shows successful install to RC33.
WOOT....
Also, I now have the T-Mo menu item that says "System updates."
I assume that now I can wait for the OTA cupcake from T-Mo.
Thanks for the help!
Sidenote: was I able to do these updates because I rooted my phone, used TelNet, etc.? IN other words, can one do these updates and downgrades if they had not rooted their G1?
Last edited by MichaelSF; May 13th, 2009 at 02:16 PM.
Sidenote: was I able to do these updates because I rooted my phone, used TelNet, etc.? IN other words, can one do these updates and downgrades if they had not rooted their G1?
If your going from a non-root phone you cannot just simply throw these onto your phone and update them and have cupcake. You have to take advantage of the root hole in RC29 by using the telnet. as far as YOUR phone goes I am curious to see if you can just update to cupcake again now that you have already gone through all that.
...As far as YOUR phone goes I am curious to see if you can just update to cupcake again now that you have already gone through all that.
That's a good question. Is my phone permanently rooted or do I have to go back to installing the original OS (RC29), do the TelNet thing, and after that install cupcake?
Or when I returned to the latest pre-cupcake OS (RC33, 1.1) did that close the security hole that was in RC29. If it's closed, do I have to downgrade to RC29 to reopen the security hole?
I guess I could try to install cupcake directly from the MicroSD chip and see what happens.
But as you may suspect, I am not willing to risk I might brick the phone, especially since the reason I went back to the original 1.1 firmware OS was to be able to receive the T-MO OTA cupcake update.
Sidenote: For those who might wonder, reasons I got rid of cupcake was because it showed that I was with Vodafone and the default location was in the UK. For example, when I opened GPS mapping software it opened to the European map and not the U. S. map.
So while none of that affected the phone and features, I did not like seeing that "Vodafone Magic" in the <Settings> <About phone> <Model Number> box.
Another thing is that in the version of cupcake I downloaded it had a different interface and icons. E.g., while I had the camcorder feature, I did not have a camcorder icon. I did not like that. A niggle, I know, but I wanted that icon in my menu.
Last edited by MichaelSF; May 13th, 2009 at 04:20 PM.
When I try and downgrade my phone, it fails verification. I cannot find a otacerts.zip file on my phone, what can I do to get it back, get a new one, or ignore the verification so that I can un-root my phone? Thanks, Darren
When I try and downgrade my phone, it fails verification. I cannot find a otacerts.zip file on my phone, what can I do to get it back, get a new one, or ignore the verification so that I can un-root my phone? Thanks, Darren
UN-Root with the link in my signature .... pay attention to whether your are US or UK and select the correct Builds and Radios ...
Your link ends up back at this thread. I have tried to follow this thread several times, but each time I alt+s to install the RC29 update, it fails because it cannot verify the update. I have read elsewhere that it is because the otacers.zip file is incorrect/missing. Am I missing something in your guide that should help me get past the verification step?
Your link ends up back at this thread. I have tried to follow this thread several times, but each time I alt+s to install the RC29 update, it fails because it cannot verify the update. I have read elsewhere that it is because the otacers.zip file is incorrect/missing. Am I missing something in your guide that should help me get past the verification step?
Except for the .nbh file in STEP 1. .. the other downloaded zip files must be named update, update.zip make sure (depending on your OS) that you dont end up naming it update.zip.zip, on XP desktop the files would just show the base file name like (JFv1.42_RC33) just change it to Update ... if you right mouse the file and check the properties you will see the file is still a zip file ....this is what you want ... the file can then be copied to the phone into the /sdcard directory ...
Last edited by justjimjpc; May 20th, 2009 at 08:14 AM.
Quick question about unroot. When I get tto the bootloader step, is it necessary to do this to get ota updates? or is it just nesecary for the whole process to work smoothly?. Is it ok to leave the bootloader as the eng boot loader or does it realy matter
Quick question about unroot. When I get tto the bootloader step, is it necessary to do this to get ota updates? or is it just nesecary for the whole process to work smoothly?. Is it ok to leave the bootloader as the eng boot loader or does it realy matter
If you are following the guide in my signature .... then you need to all the steps in order to return phone to standard ... so the OTA will work as if the rooting had never been done.
Thank you for all the help, but I am still having problems.
I followed the instructions without a problem in the G1 t-mobile total newbie HELP link up to step 4 without a problem.
I installed the engineer boot loader per your recommendation.
Once I get to step 4, I download RC29 IMG Pre-root (45.2MB file that I have downloaded a couple of different times to make sure that it is not corrupt).
When I follow the instructions for step 4, this is what I see:
Android system recovery utility
Using test keys
E:Can't open /cache/recovery/command
Home+Back - reboot system now
Alt+L - toggle log text display
Alt+S - apply sdcard:update.zip
Alt+W - wipe data/factory reset
I have verified that I followed the instructions as outlined. I have verified that there is only a single extension (I run windows XP with "hide known extensions" turned off).
Last edited by bfdarren; May 21st, 2009 at 02:05 PM.
Thank you for all the help, but I am still having problems.
I followed the instructions without a problem in the G1 t-mobile total newbie HELP link up to step 4 without a problem.
I installed the engineer boot loader per your recommendation.
Once I get to step 4, I download RC29 IMG Pre-root (45.2MB file that I have downloaded a couple of different times to make sure that it is not corrupt).
When I follow the instructions for step 4, this is what I see:
Android system recovery utility
Using test keys
E:Can't open /cache/recovery/command
Home+Back - reboot system now
Alt+L - toggle log text display
Alt+S - apply sdcard:update.zip
Alt+W - wipe data/factory reset
I have verified that I followed the instructions as outlined. I have verified that there is only a single extension (I run windows XP with "hide known extensions" turned off).
SO IF YOU DID INSTALL the RC29 IMAGE in Step 4 as you stated above you have mixed up the files and steps... and things should be going wrong ...
Please place the link you are talking about .. because the RC29 45MB zipped file is the 89GB DREAIMG.nbh And the one zip that you do need to extract .. and that file is USED in STEP 2 not in step 1 ... because this is the IMAGE file that has the root security hole.
Step 1 the RC29 IMAGE (has root security hole) ....
Step 2 Is for RECOVERY, TEST KEYS and SU service the actual root service...
Step 3 Is to install The Boot-Loader so that additional Modified-Builds can be added ...
Step 4 is where you would be installing the latest/Final build like RC33 (~42GB) or Possibly the ADP 1.5, Or Haykuro 1.5, etc ...
SO if you WILL POST the file links you used for each step ... then that will let us verify that you have them in the proper sequence NOW !!!
PS: DONT Forget STEP 5 ... which is the Radios for the Build you are using as you final Install version ...
.
Last edited by justjimjpc; May 21st, 2009 at 03:03 PM.
Since I am trying to go from root to legit, I have been following the post from above. After following the instructions for steps 1 to 3, I was using the instructions with links as quoted below. It specifically states to use the RC29 IMG Pre-Root in step 4. If this is not correct, then I will try again and skip the RC29 IMG Pre-Root step.
Quote:
Originally Posted by justjimjpc
Try a Search for RC33 1.1 Build .. HTC or XDA sites ... I will try to find a biuld as well ....
Since I am trying to go from root to legit, I have been following the post from above. After following the instructions for steps 1 to 3, I was using the instructions with links as quoted below. It specifically states to use the RC29 IMG Pre-Root in step 4. If this is not correct, then I will try again and skip the RC29 IMG Pre-Root step.
In Your previous post it was not clear that you were trying to go back to a legit phone.
THIS ASSUMES YOU HAVE A WORKING ROOT VERSION INSTALLED ...
Then yes the Builds RC29, RC30, RC33 you would use Step 4 for each build. The Last builds are ALL of course unmodified LEGIT ROMs to accomplish the LEGIT end config.... Radios goes back to RC33-Version if you had installed Cupcake 1.5 radios by using Step 5...
THIS ASSUMES YOU HAVE A WORKING ROOT VERSION INSTALLED ...
Then yes the Builds RC29, RC30, RC33 you would use Step 4 for each build. The Last builds are ALL of course unmodified LEGIT ROMs to accomplish the LEGIT end config.... Radios goes back to RC33-Version if you had installed Cupcake 1.5 radios by using Step 5...
Sorry that I was not clear that I was trying to un-root the phone. I have been following the instructions, but I keep getting the error that it cannot verify the RC29 file. Is there something else that I am missing or am I just screwed?
Last edited by bfdarren; May 21st, 2009 at 03:45 PM.
Sorry that I was not clear that I was trying to un-root the phone. I have been following the instructions, but I keep getting the error that it cannot verify the RC29 file. Is there something else that I am missing or am I just screwed?
This should get things back in order ....
Try doing the ROOT procedure ... Again until you are back at a stable ROOTED phone ...
I verified that the phone was working correctly and was rooted.
I started the procedure for un-rooting the phone using the above link. I was able to perform steps 1 - 3 without a problem, but as soon as I try to install the RC29 IMG pre-Root zip file (renamed update.zip) I get the error messages:
E:No signature (1 files)
E:Verification failed
Installation aborted.
I skipped that file and was able to install up to RC33, but when I try to install the radios I get the verification failed. I noted that at the end of the RC33 install process, it said that it installed radios, so I tried to install the original boot loader, but again I received a verification failure.
Last edited by bfdarren; May 21st, 2009 at 06:31 PM.
Why can't I find this guide? I see a guide to root, but can't find step by step instructions to go legit??
Am I just missing it?
YES ... you are missing it ... It is the same Guide you just need to follow the Numbered steps using the reference files ... in the UN-ROOT Thread ..
================================================== ============
THIS GUIDE ASSUMES YOU ARE STARTING FROM A WORKING ROOTED VERSION
================================================== ============
EDIT: Here are the files you will need To Go From : Root to Legit RC33 build 1.1
Why can't I find this guide? I see a guide to root, but can't find step by step instructions to go legit??
Am I just missing it?
I spent a long time trying to figure it all out too. IMHO the confusion is because he has the word "update", rooting instructions and legit mixed into one post, so the instructions not clear. Also, he has his instructions in his signature that makes it a circular path where one keeps going back to the same spot. Probably a thread that only deals with going back to legit would be better.
Hats off to the effort, but I think a step by step in simple terms for people like me would help.
I'll come up with a step by step to go back to legit. Will post it on YouTube sometime next week.
Last edited by MichaelSF; May 24th, 2009 at 09:23 PM.
I spent a long time trying to figure it all out too. IMHO the confusion is because he has the word "update", rooting instructions and legit mixed into one post, so the instructions not clear. Also, he has his instructions in his signature that makes it a circular path where one keeps going back to the same spot. Probably a thread that only deals with going back to legit would be better.
Hats off to the effort, but I think a step by step in simple terms for people like me would help.
I'll come up with a step by step to go back to legit. Will post it on YouTube sometime next week.
I think I understand, I have a couple of questions though.
In step two, what recovery_testkeys.img file do I need to use, and do I need to do anything in telnet? I suppose I don't completely understand the process and what exactly I'm doing here.
I think I understand, I have a couple of questions though.
In step two, what recovery_testkeys.img file do I need to use, and do I need to do anything in telnet? I suppose I don't completely understand the process and what exactly I'm doing here.
Thanks for the help guys...
this is the one you need and was a link in the quide ....
Well, after a couple hours of trying, I've officially given up. I've re-rooted and flashed JF's latest 1.5 build (which is seriously awesome.) The things I was missing (voice search and latitude) have returned. So screw the OTA.
Once again, thanks to justjimjpc for his unwavering help and support. You are truly a hero among men.
Well, after a couple hours of trying, I've officially given up. I've re-rooted and flashed JF's latest 1.5 build (which is seriously awesome.) The things I was missing (voice search and latitude) have returned. So screw the OTA.
Once again, thanks to justjimjpc for his unwavering help and support. You are truly a hero among men.
I was going to go back to legit, so to get the T-Mo OTA notice and download of Cupcake.
But I decided against it since JF's version is far better. It has more features and you can get his updates (with new features) in the future.
Also, keep in mind that his latest update (1.51) is the U. S. version of cupcake with his tweaks. (And MyFaves is now back, if you use that.)
If it's OTA feature that you miss, go to Market and download JFUpdater. That program automatically notifies you of any updates JF comes out with, so you can get a shot of OTA if the need arises. Matter of fact, I got his OTA notice that he had Cupcake 1.51 available for download.
Remember, JF's Cupcake is BETTER than anything that T-Mo would publish because he fixes any bugs, etc. T-Mo is far slower to issue patches and updates. I expect we won't see one for another three to five months, if at all.
So I would remain with and feel good about having JF's Cupcake installed.
Last edited by MichaelSF; May 26th, 2009 at 04:20 PM.
Has anyone figured out what causes this? I am on Step 4 of Unrooting, going from RC29 to RC30. And I get this error. The reason I am doing this whole procedure is because I was getting this error trying to get Cupcake on my already rooted phone, so I wanted to start from square 1. Anyone know why this error occurs and what causes it? Ive reformated my SD card a million times, and reset to factory defaults. The file is named Update because im running vista and it already recognizes it as a Zip file. Ive varified through my computer that the file IS there. Any ideas?
I reformatted my SD card again. Still no dice. Looks like im stuck at RC29 for now.
Last edited by Poehring; June 9th, 2009 at 05:38 PM.
Has anyone figured out what causes this? I am on Step 4 of Unrooting, going from RC29 to RC30. And I get this error. The reason I am doing this whole procedure is because I was getting this error trying to get Cupcake on my already rooted phone, so I wanted to start from square 1. Anyone know why this error occurs and what causes it? Ive reformated my SD card a million times, and reset to factory defaults. The file is named Update because im running vista and it already recognizes it as a Zip file. Ive varified through my computer that the file IS there. Any ideas?
I reformatted my SD card again. Still no dice. Looks like im stuck at RC29 for now.
I you download the correct files and followed the procedure ... you should be ok ...
When you copy the update file to the sdcard .... you are in the Mounted mode for the SDCard...
The Update file name when you look at the /sdcard directory should display the file as update.zip Vista may not display the file extension ... If you right mouse the update file in the /sdcard directory the file type should show as a ZIP type and the name should be Update ... if this is not the case you may have a mis-named file that is really update.zip.zip and will not work ...
when you have RC29 running and then reboot phone into the recovery mode..
Yep I did all that. The file is named Update and when I right click on it, Vista recognizes it as a Zip File, so that is good. In recovery mode, I do Alt+W, Alt+L (Just in case) then I do Alt+S to install the update and that's when I get the message. Ive tried the same file downloaded from different Sites, each times its named Update and it is recognized as a Zip file. Ill go a head and give it one more shot and see what happens, lol. Ill try re-formatting my SD card again using the card reader. Stand By
Yep, I get the same error. So im in RC29 right now...everything works fine. Firmware version 1.0. Everything works on my phone. I just get the error when in recovery mode trying to apply the RC30 from RC29 Update.
Last edited by Poehring; June 11th, 2009 at 12:22 AM.
Yep I did all that. The file is named Update and when I right click on it, Vista recognizes it as a Zip File, so that is good. In recovery mode, I do Alt+W, Alt+L (Just in case) then I do Alt+S to install the update and that's when I get the message. Ive tried the same file downloaded from different Sites, each times its named Update and it is recognized as a Zip file. Ill go a head and give it one more shot and see what happens, lol. Ill try re-formatting my SD card again using the card reader. Stand By
Yep, I get the same error. So im in RC29 right now...everything works fine. Firmware version 1.0. Everything works on my phone. I just get the error when in recovery mode trying to apply the RC30 from RC29 Update.
I think possibly the file you are using is RC29 To RC30 with would be used for Returning the phone to a Legit(Non-Rooted) phone ...
post your file link so we can verify what you are trying to use ..,.
You may have tried these files from a AF member's site ... but here is the link