AS OF RIGHT NOW THIS WILL NOT WORK FOR 32A DEVICES WITH THE 6.35 RADIO
I AM NO LONGER SUPPORTING THIS THREAD SINCE I HAVE MOVED ON TO THE HTC SENSATION AND NO LONGER HAVE A MYTOUCH 3G TO MESS WITH. THIS DOES NOT MEAN THAT YOU CAN NO LONGER POST ISSUES IN THE THREAD SINCE OTHER MEMBERS WILL HOPEFULLY STILL HELP OUT.
As Amon Ra put it:
"The following instructions :
will void all warranties of your phone!
will erase all your userdata!
will change your current ROM/SPL!
will change your current splash screen!
could brick your phone!
Proceed at your own risk!"
There's been a lot of questioning about how to root the new 2.2.1 updates that have rolled out for myTouch users to get a custom ROM loaded. So I decided to create an updated guide. I'm writing this as I'm rooting my own myTouch 1.2 so it should be pretty accurate, but we'll find out. Please please please read through this whole post before doing anything! Without further adu, let's begin.
1. First thing you need to know is what kind of myTouch you have. With the phone turned off, boot into fastboot by holding (back+power). You'll get something that looks like this:
Code:
Sapphire PVT 32A Ship S-on G
Hboot-1.33.0013 (Sapp31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009
What your looking for is whether you have 32A or 32B in the first line and what you've got in the radio line. Write this down for reference later on. (If you have a myTouch with the headphone jack on top, you need to read this first.)
2. Let's go ahead and get all the downloads out of the way since this is probably the single longest step. Download each of the following items:
Everyone - AndroidSDK
Everyone - SuperOneClick, just download the latest version at the bottom of the first post.
Everyone - CyanogenMod 5.0.8-DS
Everyone - Google Add-on for CM 5.0.8
Only if the first line in fastboot says 32A and you DO NOT have a headphone jack - EBI1 Port for CM 5.0.8
Only if the radio line says 2.22.27.08 or 2.22.28.25 - New Kernel for New Radio's
It may make it easier to put all the files in the same folder once downloaded. For example, open "My Documents" and make a new folder called "Phone Stuff" and put everything in there.
3. Extract the contents of the "android-sdk_r08-windows.zip" files to any folder (just make sure you know where). After extracting, using file explorer find the file called "SDK Manager" and open it. When it starts up a window will pop-up with "Choose packages to install" in the upper left-hand corner, just click Cancel. In the left pane, select "Available Packages", then in the right pane, expand "Third party add-ons", then "Google Inc. add-ons", and finally check "Google USB Driver Package". In the bottom right-hand corner, click "Install Selected". In the window that opens, make sure "Accept" is selected, then click install. Select "Yes" in the next window and close everything out.
4. With the phone powered on and sitting at the home screen, press Menu->Settings->Applications->Development->Look at "USB Debuggin" and make sure it is turned on. Now, plug the phone into the computer with your USB cable. Mount your SD card to the computer using the option in the notification bar. Copy over the CM 5.0.8 and Google Add-on to the root of your SD card.
5. Back on the computer, locate the SuperOneClickv*.zip file and extract it to a folder (make sure you know where). Navigate to that folder, and open the SuperOneClick.exe. Once it starts up, hit the "Root" button.
Here's the tricky part, if you see a line saying "***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***" then do as it says and turn off "USB Debugging" on the phone. Wait until the program shows "Waiting for device..." and turn USB Debugging back on. It may take a few tries before the program finishes. Your phone may do some funky stuff, such as the screen going black showing "Android System" at the top, just let it sit and once it starts responding again, turn USB Debugging back on. Once the program finishes, it'll say "Root files have been installed! Would you like to run a test?" click yes. In the next prompt, click OK. Once you get a pop-up saying "Your device has been rooted! Would you like to donate?" click yes to donate to the program's creator or click no to continue on. If you get "failed" whenever running the root test from SuperOneClick, you need to run the program again.
5a. Reboot the phone.
6. Now, from the phone, download ROM Manager and SuperUser from the market and install them.
7. Once they both are installed, open ROM Manager. Click "OK" to both the prompts that come up. At the top, click the "Flash ClockworkMod Recovery" button. A prompt will come up asking you to confirm your phone model. If you have a 32B phone or the myTouch 1.2 (headphone jack), select "ION/MyTouch 3G". If you have a 32A phone without a headphone jack, select HTC Magic. Once it has finished flashing, click OK. Scroll to the bottom of the ROM Manager menu and select "Flash Alternate Recovery". If you have a 32B/1.2 phone you should see "RA Recovery v1.7.0G". If you have a 32A without a headphone jack, you should see "RA Recovery v1.7.0H". Once verified to be correct, select that option and then click OK. Once completed click OK again. Power off your phone.
NOTE: I use these steps to get Amon Ra's Recovery installed since the steps in this guide will be using it and not Clockwork Mod. If, after getting more familiar with using recovery, you want to use ClockworkMod recovery instead, the steps are the same, just don't select the "Flash alternate recovery" option.
8. With the phone powered off, hold down (home+power) to get into your new custom recovery. Here you'll use the trackball to navigate the menu's, press the trackball to select, and the back button to go back. From the main menu, select "Backup/Restore", then select Nand backup and press the home button to confirm. Once it's completed the backup, use the back button to get back to the main menu. Select the "Wipe" option, then select "Wipe data/factory reset", press home when prompt, then press "Wipe cache", hit home when prompted, then select "Wipe Dalvik-cache", hit home when prompted, and finally back out to the main menu. Select the "Flash zip from sdcard" option, first select the CM 5.0.8.zip and hit home to confirm, then the Google Add-on file and select home to confirm.
8a. If you have a 32A device WITHOUT a headphone jack, you'll now also flash the EBI1 port (boot-cm_2634.7_ds_32a-oc-uv-xtra-fp-091310) and hit home to confirm when prompted.
8b. If you have either of the new radios (2.22.27.08 or 2.22.28.25) then flash the new kernel (ezBiffTestKernel20110222-2708_S.zip) and hit home to confirm when prompted.
NOTE: If you don't get into the custome recovery (you get a picture with a phone and a triangle with exclamation mark) boot back up as normal and repeat step #7.
NOTE 2: The backup you make is in case anything goes wrong and the ROM doesn't boot. Go back into recovery, select the "Backup/Restore" option, then select the "Nand restore" option. Just click the trackball throught the menus and hit home to confirm when prompted, then reboot.
9. After flashing all the files, back out to the main menu again and select "Reboot system now". It will take about 5-10 minutes for your phone to boot the first time. Once your in, enjoy.
If you need help and I'm not on here, feel free to try and get up with me on Google Talk or MSN at [email protected].
Thanks to Amon Ra for his recovery images!
Thanks to the Cyanogen team for an awesome ROM!
Thanks to Pershoot for his awesome kernels!
Thanks to CLShortFuse for his awesome app!
Thanks to the ClockworkMod team for their awesome app!
Thanks to MarcAntonyy for pointing out I'm a retard!
Resources:
SuperOneClick
Kernels
CyanogenMod
OK, I've updated the original guide with ezTerry's kernel that will work with the 2708/2825 radio's, which should completely alleviate people running into bootloops.
Things I deem important.
1. CLShortFuse is rolling out updates for SuperOneClick, so now the link directs you to his post instead of being a direct download.
2. I updated the guide to flash CM 5.0.8 instead of CM 6.1. Some people are having issues getting CM 6.1 flashed, plus CM 5.0.8 (for me at least) is much more stable than CM 6.1.
3. Added steps to take if the first guide ends with you being in a boot loop in the second post.
4. First guide updated to hopefully keep users from running into the boot loop.
OK
Remounting system with read-only access...
OK
Running a SU test...
Test failed!
FAILED
Is this normal?
No, try running the program again.
Did you get my PM, the one I sent you isn't showing up in my "Sent" items. For some reason your /system partition is full, so SuperOneClick is failing trying to push the SuperUser.apk. Try installing SuperUser from the market and then running SuperOneClick.
Yeah. Still nothing. Could the update possibly lock me from rooting?
Sent from my T-Mobile myTouch 3G using XDA App
No, I did this guide from the 2.2.1 update. Did you pull it OTA or did you manually do the update? Just to be sure, it's still failing after installing SuperUser from the market, correct?
Got root, but cant install recovery
Used superoneclick and all went well. I cant get a alt recovery on my phone though. once i reset the phone, holding the home button I get the green screen with th fastboot usb in the right corner. I have full sdk with limited adb skills. I need Clockwork or preferably AmonRA. I get superuser permissions and all but I am trying to avoid re-partioning my card. Is there a way around this?
Installing a recovery will not repartition your SD card. Actually, nothing in this guide will partition or require that you partition your SD card.
It was the manual update.
Sent from my T-Mobile myTouch 3G using XDA App
Something might have been hosed. Do you have the 3.5mm jack? You may want to try booting into recovery, do a data wipe/factory reset, reapply the update, then try rooting again. You should be out of system memory. Another quick thing you can try is turn your phone off and start the program. When it gets to "waiting for device" turn your phone on with USB debugging on. Yeah...try that first, then reapplying the update.
On a side note, the developer of SuperOneClick is working on version 2.0, which will hopefully fix the issue your experiencing plus the issue with having to toggle USB debugging, but for the time being, let's get this figured out.
I am going to try this guide, this will be my first time rooting as i have a 2.2 fender mytouch will this guide work?
how long will this take? i have to work in an hour lol
Assuming everything goes smoothly, about 30 minutes. Honestly though, nothing in the guide will prevent you from using your phone until you start flashing the custom ROM. Furthermore, once you get rooted with the program and get ROM Manager working and move the files, you won't need a computer anymore.
Maybe print the directions and take them with if you can use your phone while at work. Yes this will work on a Fender with the new update. I made it using my 1.2 on the update, which is pretty much the exact same thing.
it would be hell of alot easier with a Youtube Video guide? that way we can follow exactly step by step without messing up the phone! also will i be able to sign in using WIFI? beause there is no data coverage in my area of living. if i user superoneclick will that reset my phone to factory settings and make me sign into google again? lol i dont wanna drive 2 hours to the nearest data coverage area. pain in the ass lol
SuperOneClick just roots the 2.2.1 ROM to allow you to use ROM Manager so no data reset in that part. You will be doing a factory reset when you flash CM 6.1, however CM 6.1 will allow you to update over wifi. Even if something happens when you start flashing CM 6.1, you can restore your backup that you make following the guide, which will still be activated. Are you living on the top of a mountain or something? I haven't been anywhere that gets a signal without data coverage (at least G).
lol check my zip code 50501 you'll see i have no data coverage for miles lol its ridic. and we use a partner web with t-mobile.
Dude, that sucks, I think you went with the wrong carrier, lol. Are you in the Army? Navy here.
Ahhh, your roaming on AT&T's network. You just need to enable roaming data. Go to Menu->Settings->Wireless & Networks->Mobile networks->And check "Data roaming". T-Mobile doesn't charge for domestic roaming, so as long as your in the US, you'll be good.
OK , cool but,
still an issue with recovery. I try to install a recovery image via fastbooot and it wont read it. wiping my card is redundant. but if I must? Then I willThat is an excellent tool though.
Related
So, after following this forum on and off over the past few months, I finally decided to root my Rogers Dream.
I was one of the first customers to receive a phone with SPL 1.33.0010, as mine was shipped to me directly from rogers as a hardware upgrade. Because of this, rooting was a little more difficult for me than I had initially anticipated, however, after having found this thread (http://forum.xda-developers.com/showthread.php?t=558301), I was able to downgrade to SPL 1.33.2005.
From this point, I started following the instructions found here: http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod. I was able to re-flash the downgraded OS, and rebooted to a T-mobile G1 splash screen. After going through the various steps, I got stuck where it said to reboot into recovery mode. I held down the home key while powering up, as instructed, but instead of booting to the recovery screen, I was greeted with an image of an exclamation point inside a triangle, hovering over a cartoon of a G1.
I was able to reboot using the 3 fingered salute (send-menu-power), but I was unable to load the recovery screen. I then attempted to bring up the boot loader by holding down the camera button while powering on. The screen I was greeted with did not resemble the boot loader I was used to seeing. It is composed of four horizontal coloured bars, and lists the phone information as follows:
DREA210 PVT 32B
HBOOT-0.95.000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
I'm looking for suggestions on how I should proceed from here. Any help would be most appreciated. Although the phone does make phone calls, and will send and receive text messages, it will not send or receive data, unless connected to wifi.
Thanks,
Grant
So I'm a little rusty but let me give it a shot. While holding home + power it may seem to just get stuck after a minute, but have you tried pressing alt + L ? This makes the recovery text visable (if it's not by default).
hope this helps..
Looks like you've ended up on the stock g1 bootloader.. did you flash the rc29 DREAIMG?
goldenarmZ said:
Looks like you've ended up on the stock g1 bootloader.. did you flash the rc29 DREAIMG?
Click to expand...
Click to collapse
Yes. The phone thinks it's a T-mobile G1, but it still works with my Rogers SIM.
sonikamd said:
So I'm a little rusty but let me give it a shot. While holding home + power it may seem to just get stuck after a minute, but have you tried pressing alt + L ? This makes the recovery text visable (if it's not by default).
hope this helps..
Click to expand...
Click to collapse
I did this, and the recovery text did indeed become visible, however, I now have a new problem.
I hit Alt+W as per the instructions in the wiki, and it reset the phone. I then hit Alt+A, and nothing happens.
This is the text I see on the screen when I'm in recovery mode:
Androind system recovery utility
E:Can't open /cache/recovery/com
mand
Home+Back - reboot system now
Alt+L - toggle log text display
Alt+S - apply sdcard:update.zip
Alt+W - wipe data/factory reset
After attempting Alt+A, I hit Alt+S, just to see what would happen. Of course, it tried to update from package, but returned an error because there is no "update.zip" on the phone. I'm tempted to rename "update-cm-4.2.5-signed.zip" as "update.zip", just to see what happens. I'll post again once I've done this, but any suggestions from more experienced people would be most appreciated.
Grant
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
Alright, so I renamed "update-cm-4.2.5-signed.zip" as "update.zip", and it aborted the installation because there was no signature. I did the same thing with "signed-dream_devphone_userdebug-ota-14721.zip", with the same result.
It sounds like you still have the stock recovery image
jackslim said:
It sounds like you still have the stock recovery image
Click to expand...
Click to collapse
When you say stock recovery image, are you referring to the one I have installed on the phone already, or the one I'm trying to install with no success?
The image currently on the phone is the DREAIMG.nbh (rc29), which I downloaded via the wiki. The images I am trying to load also came from links in the wiki.
By recovery I'm refering to what you access when you boot with home + power where you can apply your updates (where you're seeing your triangle & exclamation point)
I just looked at cyanogen's wiki and it seems like that particular part could stand to be updated androidandme has a decent guide on how you could do this though.
http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
I'm not sure if flashrec works with RC29 which is what version you should be on after flashing DREAIMG.nbh, but you can give parts A1, A2, & A3 a shot, that would probably be the easiest way to update your recovery. If you can't get flashrec to work skip down to B2 and that will show you how to do it using telnet which does work from RC29
Once you update you're recovery image you should be able to apply "update.zip" or without renaming them by selecting the "apply any zip from sd" option
Thanks, Jackslim. I did as you suggested, and was able to install the CM update, as per the wiki, however, when it boots up, it shows the blue cyanogen android, and then reverts to a completely blank screen. I'm going to try reinstalling everything to see if that fixes it. Thanks for your help though.
gmupps said:
Thanks, Jackslim. I did as you suggested, and was able to install the CM update, as per the wiki, however, when it boots up, it shows the blue cyanogen android, and then reverts to a completely blank screen. I'm going to try reinstalling everything to see if that fixes it. Thanks for your help though.
Click to expand...
Click to collapse
After you install that recovery image you still have to go through the steps to install the ADP image before you add the cyangen update, then you should be cookin' with crisco
So just start back up on cyanogen's wiki from the section called "File Download"
Just to clarify, even though it is not booting up properly, I am now able to install whatever I want using recovery mode, so it's just a matter of figuring out what will work. Thanks again for all your help.
jackslim said:
After you install that recovery image you still have to go through the steps to install the ADP image before you add the cyangen update, then you should be cookin' with crisco
So just start back up on cyanogen's wiki from the section called "File Download"
Click to expand...
Click to collapse
I did get it working, thanks. Now I just have to reload all my contacts and apps, but I have already noticed a difference in device responsiveness. It's like going from Windows Vista to Windows 7. Thanks again.
I'm pretty sure I have these items in the correct order to "Permaroot" my MT4G and begin using Clockworkmod to load ROMs (and or/also want to be able to back up my default ROM)
My current attempts:
Downloaded and installed: VISIONary, from android.modaco.com, sorry I can't post actual links (VISIONary+, most recent version) was no longer avalible in the market so I had to install it from the URL)
Downloaded and installed "Clockwordmod" from the Market.
Put the phone into USB-Debugging mod, and disabled fast boot.
VISIONary+ question: I setup TEMPROOT, and "Root on Boot", assuming I would than be able to boot into "Recovery mode" via "Clockworkmod"
The phone reboots, and I'm assuming that would boot into "Root" **Root on boot** (Yes I know the temp. should fail after a reboot, but I thought, I'll stay away from "Permaroot" for now). However, I don't get to any sort of recovery mode, instead I get a screen with a triangle and exclamation in red, and that's it, it just hangs there, I'm thinking that this is just USB-Debugging, and I'm not achieving recovery mode, so this must be the result of not booting into a root mode.
Going back to VISIONary+, I attempt to "Permaroot", the phone's homescreen goes blank and nothing happens. The phone eventually turns itself off but doesn't reboot, subsequently, I must restart it manually, again, I'm not sure if I've achieved anything?
Advice, suggestions? Would be very appreciated.
Questions that might explain what's wrong?
Even in USB-Debugging mode, should I be connected to a PC via USB-Cable during all of this?
Any thoughts on why the PERMAROOT fails, or the "Root on boot" fails to get me to "Recovery mode"?
Last thing, I get a complaint from "Clockworkmod" when loading, that my SD Card must be mounted (which I'm assuming it isn't due to USB-Debugging mode and/or being connected to the PC) So should I get a good charge and disconnect from the PC while attempting all this? Fixed, disconnected USB-Cable, and mounted SD card in settings, this stopped this error
Also, I'm interested in backing up my default ROM ASAP as a safety-net in-case I screw something up. Is this possible via recovery mode in "Clockworkmod"? Links to advice on doing this?
Thanks everyone! Great board!
you should follow this as it worked for me flawlessly
http://forum.xda-developers.com/showthread.php?p=9534017#post9534017
thanks! that post seems to answer a lot of the specifics I might have been missing! Guess I missed it in search! I'll report my results!
I followed it exactly but I still get the Red Exclamation Point. I have rooted my phone s-off and I have superuser and rom manager. I did the Flash Clockwork Recovery but when I reboot into recovery I get Red Exclamation Point then when I click vol up and power the next says " E:Can't open /cashe/recovery/command " What should I do??
[*]The phone reboots, and I'm assuming that would boot into "Root" **Root on boot** (Yes I know the temp. should fail after a reboot, but I thought, I'll stay away from "Permaroot" for now). However, I don't get to any sort of recovery mode, instead I get a screen with a triangle and exclamation in red, and that's it, it just hangs there, I'm thinking that this is just USB-Debugging, and I'm not achieving recovery mode, so this must be the result of not booting into a root mode.
Click to expand...
Click to collapse
You can NOT flash clockwork without S-OFF and the red triangle is recovery. It is stock recovery if you press volup+power you will see the menu
S is off I rooted my phone using the terminal Emulator and that worked fine
When I press upvol and power I see
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cashe partition
E:Can't open /cashe/recovery/command
This is what my screen shows when I try to go into recovery and again my phone is rooted s-off and I use superuser
Try flashing the recovery again... for some reason people have reported it not sticking... just go back and flash it like 2 or 3 times then reboot
I found out the problem it was so easy but I never would of thought of checking but my wife said maybe my Rom Manager is a bad copy (because I get all my apps from a not so honest site) so I deleted my RM and downloaded the freebie on the market and it worked on the first try.....Now I have Glacier Rom running and I feel like a new man
slhpss said:
Try flashing the recovery again... for some reason people have reported it not sticking... just go back and flash it like 2 or 3 times then reboot
Click to expand...
Click to collapse
+1 on that, When I first flashed it, I was still getting the red triangle, after a quick google search I re flashed it an extra 2 times and it worked flawlessly
Hi
I had a problem with my htc magic after trying to flash the RA-sapphire-v1.0.0 recovery image into the phone. Before the problem occurred I rooted my phone and flashed RA-sapphire-v1.6.5, but because I had an issue with it I tried to flash an old version " RA-sapphire-v1.0.0".
Now my phone keeps rebooting endlessly and I can not access recovery mode, fastboot or anything else?
Is it bricked? Can I fix this issue?
The phone is 32A
Radio is 6.35 (I can not access fastboot so this is from my memory)
If you have no access to fastboot nor recovery, then you are pretty bricked!!!
Are you sure you can't get into fastboot? Pull the batter, press and hold down the back button, and put the battery back in. See if it goes into fastboot then. Do the same thing again, but holding the home button instead to see if you can get into recovery. I dunno why you used an old one and not the new one.
DonJuan692006 said:
Are you sure you can't get into fastboot? Pull the batter, press and hold down the back button, and put the battery back in. See if it goes into fastboot then. Do the same thing again, but holding the home button instead to see if you can get into recovery. I dunno why you used an old one and not the new one.
Click to expand...
Click to collapse
I tried both method and it did not work. The phone is still rebooting endlessly. I used the old recovery since the new one kept restarting the phone to the actual system after I go into recovery mode after 2-3 seconds.
1.6.5 isn't the new one. The newest version is 1.7.0. Well if that didn't work, then year your bricked.
so is there anything i can do to fix it?
JTAG is your only option.
Where are you from ?
usernome said:
Where are you from ?
Click to expand...
Click to collapse
I am from Australia
I have HTC Magic Vodafone (32B) and have a similar issue with phone in a reboot loop, however, i can get into fastboot but not sure what next to do. Is there a guide anywhere on what to recover my phone.
Depends, what is your current fastboot information?
Not sure what info you want from Fastboot screen so this is everything i can see
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0013 (SAPP10000)
CPLD-10
RADIO-2.22.28.25
Oct 21 2009,22:33:27
Is this the right kind of information?
Two options. Downgrade to 1.5, then update to 1.6, then root, flash a custom ROM, reinstall the 1.33.0013 SPL and 2.22.28.25 radio, and then flash a new custom ROM. Optionally, you can downgrade to 1.5 and upgrade back up to 2.2.1. Either way just let me know and I can assist.
Thanks for you help with regards to the approach, is one easier than the other? If they are both roughly the same then would go for the Downgrade to 1.5 and upgrade back up to 2.2.1. route as it may be easier to sell in a few weeks when the Galaxy S2 out.
So, here we go, please read through all the steps before starting and then reading each step as you go along:
1. Go here and download "sappimg.nbh" and "update1-5.zip".
2. Put all of them on your SD card. I would suggest downloading to a folder on your computer, then copying them over. Have had issues in the pass with people downloading files directly to their SD card and it corrupting the file.
3. With the phone turn off and the SD card in it, boot holding (volume down+power) to get into hboot. The phone should detect the sappimg.nbh, check the file (you'll see a progress bar in the upper right-hand corner), and then ask you to hit "ACTION" to continue. (ACTION being pressing the trackball)
4. The phone will start flashing the different parts of the phones partitions. You'll see the progress bar in the upper right-hand corner a few more times, then after about 5 minutes, it'll ask you to hit "ACTION" again to reboot.
5. Let the phone boot all the way up (this may take a few minutes) and then turn it off without signing in.
NOTE: Unless you need the phone to access the SD card from the computer, in that case sign in and do the next step.
6. Access the SD card, find "update1.zip" and rename it to "update.zip".
7. With the phone off turn it back on by holding (home+power) to get into recovery. You'll see a triangle with an ! in it, press (home+power) again to bring up the menu.
8. Using the trackball, scroll to the "wipe data/factory reset" option and press the trackball to select it. After it completes, scroll to "apply update.zip from SD card" and select it. It should pickup the update file on the SD card and flash it, then reboot.
9. When you get to the login screen again, turn the phone off.
Note: Again, as before, you can optionally login to get into the ROM for access to the SD card from your computer.
10. Repeat steps 6-9 for the "update2-update5.zip" files. You will need to remove the old "update.zip" before renaming the next update file. When you get to the login screen the last time (after flashing "update5.zip") you can sign in and use the phone.
Thanks for the guide but I've hit a problem. The phone recognise the sappimg.nbh and starts to flash itself but when then a message:
model ID incorrect!
Update Fail!
appears and the flash has failed. I've tried this a few times now downloading the file again, formating the SD card etc but to no avail. Do you have any suggestion on how to get round this issue?
Geffen22 said:
Thanks for the guide but I've hit a problem. The phone recognise the sappimg.nbh and starts to flash itself but when then a message:
model ID incorrect!
Update Fail!
appears and the flash has failed. I've tried this a few times now downloading the file again, formating the SD card etc but to no avail. Do you have any suggestion on how to get round this issue?
Click to expand...
Click to collapse
Crap gave you the wrong sappimg. What country did you get the phone from?
Sent from my LG-P500 using Tapatalk
I got phone from Vodafone in the UK.
Geffen22 said:
I got phone from Vodafone in the UK.
Click to expand...
Click to collapse
Need the specific country.
United Kingdom or England to be exact.
Tutorial/Walkthrough How to update your Droid R2D2 Phone using 2.2 if it fails to update to Gingerbread 2.3.3 Build 4.5.1_57_DR2-32
After spending a few days dealing with my phone automatically downloading and trying to install the updating and failing at 25%. I had to fix this since it will killing my battery.
With the instructions below this should restore your phone to the stock version of your Droid R2D2. This method will not delete anything on your phone. I would recommend backing up everything before you proceed just in case something does go wrong but I didn't have any issues. It will only restore all the original settings on your phone. This includes unrooting your phone and restoring all apk's and system files edited/removed from your device.
WARNING : This must be done using your PC. Do not attempt this using your cell phone
This information is provided without warranty. I cannot be held responsible if you brick or damage up your cell phone. I simply wrote a walkthrough/tutorial to help deal with an update issue on your Droid R2D2. I did not produce the procedure or the steps below. I just simply consolidated all the information from multiple sources to make it easier to understand and execute. You are welcome to share this information anywhere you want. If needed I will reformat the instructions so it's easier to understand.
1) First download and install the Motorola RSD Lite v5.5 (I attached the file at the bottom of this thread)
2) Download the Motorola 5.2.0 Driver with Motohelper and install from the link below
Motorola Drivers - http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
3) Download the SBF Droid R2D2 file VRZ_A957_2.4.5_1FF_01.
http://www.multiupload.com/8XGQBDG3GV
4) Once you download the VRZ_A957_2.4.5_1FF_01 file. Unzip the file into a folder. You will be using this file shortly
5) Launch RSD Lite. Once the application is launched click on the button with the 3 dots.
Navigate to the SBF file you just unzipped and once you find it click open.
You will see on the right side in the File properties window
Filename: VRZ_A957_2.4.5_1FF_01.sbf
Creation Date: 09/15/2010 03:16:26
File size: 455655933
RAM DL Version: N / A
Bootloader Version: N / A
Platform: 4G OMAP
HAB Type: Signed Production
This is a video to give you an idea how to use RSD Lite. I used this as a guide to make sure I was doing everything in the correct order.
http://www.youtube.com/watch?v=9udWx-KXwGY&feature=player_embedded#!
6) (This step isn't necessary, but you can do it.)
Back up anything on your SD card to your computer. Plug in your Droid2 to the computer via USB cable. Pull down the notification menu/blind, choose USB connection, and then choose USB Mass Storage Device. Now there should be a removable storage in your "My Computer." Go through your SD card and back up your important things. Probably the DCIM and download folder. You should also make sure that your phone is set up to "Back Up Data." Go to the system menu (the 4 squares icon/button in the lower left), choose Settings, then Privacy, then make sure the "Back up my data" and "Automatic restore" are checked.
7) Plug the USB cable into your cell phone and Power off your phone. Once your phone is powered off, Slide out your keyboard and hold the Up Arrow and press the power button. You will see a boot loader screen pop up and it will say Battery OK, Transfer mode USB. You will see the computer detect the USB device and install the new drivers onto Windows.
If the drivers in Windows Fail DO NOT PROCEED. Reinstall the Motorola drivers and try this again
8) Once you see the Transfer mode say USB. Go back to RSD Lite and click Start. You will see the progress bar Executing and slowing moving up to 100%. Your phone will eventually Power on.
Do not unplug or touch it until it hits 100% if you unplug the phone early you risk screwing up the system files on your phone.
You'll know when it is done when the Progress field in the table of RSD Lite says complete. This will take between 5-10 minutes to complete
9) Once it hits 100% you will see the status change and say Please manually power up this phone.(You phone should be already powered on if not you could power it on). Once this is completed you could either turn off your phone and power it back on or you could click Close in RSD lite. A pop up window will appear saying Application is currently busy. Do you wish to continue click Yes.
UPDATE 10/27/11
After your phone reboots and doesn't get past the boot animation
1) Turn off your phone
2) Hold down X on the keyboard
3) Turn on your phone while continuing to hold X( it will boot into the recovery mode after the Motorola logo disappears)
4) When you get the Android guy with a '!' in a triangle push the search button on the keyboard (the magnifying glass button, two keys to the left of the space bar)
5) Select both 'wipe cache' and 'wipe data' from the menu.
6) Select Reboot your phone
10) Once you unplug your phone you should see all the apks or applications which were removed originally off the device back on the device (I removed practically everything and everything was restored). If you have used z4root you will notice if you open the application it is no longer rooted.
I had a Blue triangle in my notification bar. To clear this you will need to reactivate your phone. Dial *228 and press send. Once you hear the options press 1 to activate your phone. Once this is completed you get a message saying your phone is activated and to wait up to 15 mins. You will also see the blue triangle disappear and will see the 3g reappear.
11) Once you are connected start downloading over the air the new gingerbread update to your phone. Once it is complete your phone will reboot and start installing the file and once it completed you should have the new gingerbread update on your phone
To Root your Droid R2D2 Please follow the directions below (Special Thanks to psouza4 for creating this program) http://www.psouza4.com/droid3/
NOTE: Do this at your own risk. I am not responsible for any damage caused.
1. First step is that you need to make sure if all Drivers are installed.
2. Once that is done, download and install
(Windows) http://www.mediafire.com/?g226n7as6cb1y6e
(Mac/Linux) http://www.mediafire.com/?2ugcdue4cw7dtc5
3. Now, go to Settings > Applications > Development on your Droid R2D2 and enable the USB debugging option.
4. Now connect your device to the computer and make sure you select the ” Charge Only ” mode.
5. Go the folder where you extracted the zip and run MotorolaOneClickRoot.exe (Windows) or run_to_root_your_droid3.sh (Mac/Linux).
6. Once it finished just click any button to exit the program and you will see superuser installed on your Phone.
Thats it. Hopefully this was easy to understand and works for everyone.
I cannot even root my phone. It will not go past the first rebooting stage. Any advice?
Are you currently on 2.3.3 or you still on 2.2?
Also make sure debugging mode is on and you have the correct motorola drivers installed.
Cant get VRZ file to work.
Hello,
I am trying to run threw this to reset my R2D2 Droid 2. When I try and download the VRZ_A957_2.4.5_1FF_01 file from the the link you provided all I get is a rar file that doesn't work on RSD Lite. Am i missing something on the download sight for the VRZ file?
---------- Post added at 08:41 PM ---------- Previous post was at 08:09 PM ----------
Hello again,
Sorry for my stupidity I forgot a rar file is a compressed file and I had to download win zip to decompress it. Don't deal with a lot of compressed files. Thank you for all this info will post if I got it to work.
all good. let me know if it works or if you get stuck
ok so i've been working at doing this for roughly an hour the damn drivers won't install on my computer...
Where you able to install Download Motorola 5.2.0 Driver with MotoHelper or are you getting stuck when your phone is connected to the pc?
Worked for me
Awesome, worked for me from my mac. I did get an error between phases 2 and 3 of the root process, but it worked anyway:
* Running exploit [part 2 of 3]...
*
* Rebooting the phone... when the reboot is complete, you may need to unlock the phone to continue.
*
error: protocol fault (no status)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* Running exploit [part 3 of 3]...
remount succeeded
Does this only work for the Motorola Droid R2D2 or will it work for the Motorola Droid 2 with the Gingerbread 2.3.3? Which I thought are the same phone except for the R2D2 add-on's.
ehrune - I am glad it worked for you. I will write a email to psouza and see what he says on it or ill look for an new update maybe it was a known issue which is now fixed
dfthompson - I own a droid R2D2 phone which is technically a Droid 2 with all the add-ins as you stated. I wrote the instructions because if you were like me and deleted all the bloat and junk off your phone (when you originally purchased it) you are unable to do the OTH gingerbread update because it will fail once you are doing the installation.
The file is for 2.2
thank you for posting this. my phone has been trying to update for weeks every night around midnight and failing, this is a huge help.
I must admit, after using it for a week, this update sucks big-time. Everything is much slower, button presses take a second or two to register, etc. Anyone else seeing this?
well said, guys these instructions are flawless. basic computer skills required
Ok so does this exe file get run from the computer or launch it from the phone?
Sent from my DROID2 using XDA App
Everything is done using the PC the only thing you need to do with the phone is plug it into the computer and to turn it on to go into the boot screen as instructed.
Ehrune - Yes i notice a few things running slower. i removed a ton of apk's and changed some settings and it works a lot better
boot loop
the flash was 100% successful, but now my phone is stuck in a boot loop. should I try reflashing?
edit: I ended up booting into recovery & doing a factory reset. I was able to boot & run the update from there. Good thing I backed up first..
still locked! afther full flash & no way to factory reset on my phone
i only need to factory reset ive try any times with
---------------------------------------------------
Power down the DROID 2 by holding the power button and then selecting Power Off
Hold the X key on the keyboard and turn the power back on, keep holding down the X key until you see a yellow triangle icon
Now close the slider and hold down the Volume Up button, then press the Camera button while still holding volume up
A menu will appear and one of the choices will be "wipe data/factory reset" -- use the direction pad on they keyboard to select this option
Scroll down using the direction pad to the "yes" option and select it with the d-pad select key
---------------------------------------------------
& with
---------------------------------------------------
a. Turn off your phone
b. Hold down X on the keyboard
c. Turn on your phone while continuing to hold X
d. When you get the Android guy with a '!' in a triangle push the search button on the keyboard (the magnifying glass button, two keys to the left of the space bar)
e. Select both 'wipe cache' and 'wipe data' from the menu.
f. Reboot your phone
---------------------------------------------------
the hard reset no work for my with any form (& the keys7Buttons are working properly)
i been full flashed Thanks to your tutorial
But still locked
Too many attempts
any ideas¿?
I lost my SBF file for R2-D2, and the link not available for now (multiupload). can anyone help me where I can find the file?
Thanks
I'm also looking for the r2-d2 sbf. All the links I come across are 1 of 2 dead links. Either the multiupload or the adrive links. None of which are standing today. Am I to believe that no one has a copy to upload elsewhere? So can someone please point me in the right direction.
I already found the file.
u can email me for the link, I don't have any right to post the link here
my email: [email protected]
THIS WILL BE USING THE CM 7.1 ROM. IT WORKS WITH OTHER ROMS TOO. JUST FOLLOW SAME PROCEDURE WITH YOUR ROM.
INTRODUCTION AND WARNINGS:
If you have an Evo 4g updated to android 2.3.5 with hboot 2.18.0001 and your wifi always randomly disconnects this guide is for you! The reason the server disconnects is because your router could be incompatible with your HTC phone. If it's just because of some wifi problems and some easy fixes could be made, I would go with that. But for those who have the same problem, not only will you get a cool Cyanogenmod 7.1 look... you'll be able to play PL with wifi.
I'll try to make it as easy to understand as possible... as I'm not good with this stuff either and it took time to understand the guides. Actually I used several guides but I'll kind of combine them.
This guide is for flashing Cyanogenmod 7.1 and what to do before. I am not responsible if there are any problems with your device. Use this guide at your own risk, although there's 99.99999% chance everything will go right if you follow the guide.
PART ONE:
First you'll want to install this file, you need winrar. Just unzip onto desktop so it's easier. You won't actually be using the tool but the root folder. Read the xda first post first though... http://forum.xda-developers.com/show...75&postcount=1
Here's link to download if you've read the post:
http://goo-inside.me/apps/frigid/
Then you'll want to go to www.htcdev.com.
You'll have to register there and use a real email address.
After you register login and click unlock boot loader. Where there's a scroll-down, choose "all other supported models"
Then click get started, the site will guide you through the next steps. Remember, this could void your warranty, I'm pretty sure there is a way to undo this all but remember do this at your own risk.
Tips: If you can't navigate to the right place remember to type "cd [insert name of root folder]"
To get the address, just go to root folder and click copy address at the top. (Right click on where it shows what folder you're in)
After you have successfully unlocked your boot loader you are ready for part 2.
PART TWO:
Enter fast boot on your phone again.
If you closed your command prompt, (which is fine) open it again.
Download this file and save it:
http://files.androidspin.com/downlo...ECOVERY/&file=recovery-RA-supersonic-v2.3.img
The file should appear in downloads.
Move the file into your folder titled root.
If the file is not named recovery rename it to that.
In your command prompt go the the root folder address like you did in part one.
Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img
(Remember your phone should be connected to your computer with usb debugging on, with disk drive on, and it should be in fast boot)
Once the prompt finishes the command, go back to main boot loader screen. Then use the volume keys to go down to select recovery.
Press the power button to select recovery.
Once the recovery boots on your phone, select use the volume keys to select/highlight USB MS then press the power button.
Take this zip (don't unzip it) and place it into your sd card (just the root, not in any folders).
Zip: http://download.cyanogenmod.com/get/...nic-signed.zip
Press the power button to exit USB MS.
Now go back to main screen of recovery.
Highlight/select the choice flash zip from sd card and press the power button.
Select/highlight the zip you put in your sd card and press the power button to flash.
Press the power button again to confirm.
Once it's done flashing reboot your phone.
If your phone goes into boot loop (keeps rebooting at cyanogen logo thing) then go to your recovery again and select wipe and select wipe all data/factory reset.
OPTIONAL PART 2.5:
If you're looking for Google apps you might want to flash this too, same thing with the Cyanogen ROM, flash it same way.
http://cmw.22aaf3.com/gapps/gapps-gb...828-signed.zip
This working for everyone?
Do people actually read this? Did I post in wrong section?
Guide updated v1.1
Fixed link to Amon Ra Recovery. Last link worked but file was deleted.
Hey man, I have no need for the guide , but much thanks, sincerely. Thanks
sent from AOKP heaven
Ok... I guess...
so does using that htc super tool folder instead of android sdx not wipe everything while unlocking? Or does it still do a factory reset when you unlock?
Trying to figure out what I'm missing here. I have step one all finished. On step two I'm doing the part that says:
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img"
I have the USB Debugging on and Disk Drive on, and the phone in Fast Boot. When I type the "fastboot flash recovery recovery.img" and hit enter it says Waiting for device. Should it say waiting in the command prompt area? Even with that saying waiting, if I use volume down and pick recovery, the screen shows the green circle and downloading logo, then I get the red exclamation screen. What's messing things up? I have the instructions followed exactly up to this point.
BigPimpin said:
Trying to figure out what I'm missing here. I have step one all finished. On step two I'm doing the part that says:
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img"
I have the USB Debugging on and Disk Drive on, and the phone in Fast Boot. When I type the "fastboot flash recovery recovery.img" and hit enter it says Waiting for device. Should it say waiting in the command prompt area? Even with that saying waiting, if I use volume down and pick recovery, the screen shows the green circle and downloading logo, then I get the red exclamation screen. What's messing things up? I have the instructions followed exactly up to this point.
Click to expand...
Click to collapse
have to take it out of disk drive mode i believe and put it in charge only
evo4gnoob said:
have to take it out of disk drive mode i believe and put it in charge only
Click to expand...
Click to collapse
Tried doing that and it goes right to the red exclamation screen instead of the green first. The instruction say to have it in disk drive, so not sure what to do.
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img
(Remember your phone should be connected to your computer with usb debugging on, with disk drive on, and it should be in fast boot)"
BigPimpin said:
Tried doing that and it goes right to the red exclamation screen instead of the green first. The instruction say to have it in disk drive, so not sure what to do.
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img
(Remember your phone should be connected to your computer with usb debugging on, with disk drive on, and it should be in fast boot)"
Click to expand...
Click to collapse
when i did it to my phone i had it in charge only
This is my first time trying to do anything to my phone. What exactly does the recovery step I'm doing do? It is saving all my personal data on the phone? I could care less if the phone gets wiped. I have all my contacts in Gmail and re-installing apps take like 5 minutes, so wondering if I could just skip it?
This rooting thing is getting more and more confusing. I'm pretty good computer wise, but reading on this site to try and root this phone, I find topics which are like 100+pages long, and the topic I find link to other topics and it keeps going on and on, and not sure what to do after a while. This topic has gotten me closer to finally doing it then any other. Hopefully I can get it to work fully.
Tried disk drive on and off a couple times and still getting stuck on the red exclamation.
BigPimpin said:
This is my first time trying to do anything to my phone. What exactly does the recovery step I'm doing do? It is saving all my personal data on the phone? I could care less if the phone gets wiped. I have all my contacts in Gmail and re-installing apps take like 5 minutes, so wondering if I could just skip it?
This rooting thing is getting more and more confusing. I'm pretty good computer wise, but reading on this site to try and root this phone, I find topics which are like 100+pages long, and the topic I find link to other topics and it keeps going on and on, and not sure what to do after a while. This topic has gotten me closer to finally doing it then any other. Hopefully I can get it to work fully.
Click to expand...
Click to collapse
Recovery just puts a base place where you can flash roms and stuff.
And if you get a bootloop on CM7.1 yes you will have to wipe all.
As for the recovery flash problem, try putting it on charge only and usb debugging. Then power off phone or just take out battery and reboot into bootloader. Go into fastboot again and try to flash recovery on again. Then try it.
Did you rename the recovery img to recovery? Or if it's not saved as recovery.img rename it to that.
I have it named recovery like it's supposed to be. Still get the green screen then the red exclamation mark.
What should happen when you first go into the fast boot? The reason I ask that is, when it first goes into the fast boot screen it takes a second or so to do it's thing. I see some text going on the screen real quick, and from what I can read of the text I see something about no image and can't read much else, then it is ready to use the volume up and down to make selections. Is that normal, the text part and all about no image? My phone works fine, just can get the steps in this tutorial to work.
BigPimpin said:
I have it named recovery like it's supposed to be. Still get the green screen then the red exclamation mark.
What should happen when you first go into the fast boot? The reason I ask that is, when it first goes into the fast boot screen it takes a second or so to do it's thing. I see some text going on the screen real quick, and from what I can read of the text I see something about no image and can't read much else, then it is ready to use the volume up and down to make selections. Is that normal, the text part and all about no image? My phone works fine, just can get the steps in this tutorial to work.
Click to expand...
Click to collapse
When you go to the bootloader it scans for a PC36IMG.zip file. Normally if you were s-off that's how you would flash a recovery. Since your s-on unlocked the only thing that can be flashed in PC36IMG.zip format is a file signed by HTC like a RUU
Sent from my swiper using XDA App
I got a chance to see some of the names of the missing files it lists when going into boot load. The PC36IMG.zip is one of them that says no image. So guessing that file isn't even there at all. I searched for a PC36IMG.zip file and put it in there and got more then I have seeme before on that screen. I had a blue progress meter on the right side. When it got done it said something about being too old and unsuccessful.
Also, I tried starting all over, even going into the htcdev site again. When I did that all the step worked, but when it's supposed to get to the screen where it tells you it will wipe your phone, that screen never comes up. Now I'm wondering if I can just start all the way over. Can I go into my phone and of I select factory reset, will it make the phone a totally stock phone again and change anything I might have changed? Not that I'm sure I have even changed anything at all to this point.
Removed the batter over and over till I could see the message that comes up very quickly when fast book first starts up. It reads:
Loading...[PC36DIAG.ZIP]
No Image!!!
Loading...[PC36DIAG.NBH]
No Image!!! or Wrong Image!!!
Loading...[PC36IMG.ZIP]
No Image!!!
Loading...[PC36IMG.NBH]
No Image!!! or Wrong Image!!!
Know where I go from here to correct things?
BigPimpin said:
Removed the batter over and over till I could see the message that comes up very quickly when fast book first starts up. It reads:
Loading...[PC36DIAG.ZIP]
No Image!!!
Loading...[PC36DIAG.NBH]
No Image!!! or Wrong Image!!!
Loading...[PC36IMG.ZIP]
No Image!!!
Loading...[PC36IMG.NBH]
No Image!!! or Wrong Image!!!
Know where I go from here to correct things?
Click to expand...
Click to collapse
it shouldnt find a PC36IMG.zip file or the other. Only files in that can be flashed in that format is radios hboots splash screen RUUs recoveries. You shouldnt go around just flashing random things in the bootloader you can end up bricking your phone