Moto G not boot, it just gets in the bootloader screen warning
I'm having the exact same issue, just flashed the latest stable version of CM11 (with gapps obviously) from dhacker's thread in CWM.
Coming from 4.3 with the US version t-mobile moto g.
Stuck on the bootloader unlocked screen.
I thought for a while it was just that the first loadup takes awhile but has been 10 minutes now and am figuring something bad happened.
ignore all the italics, I'm an idiot
Edit: 25 minutes in, have tried connecting the phone to computer and running command prompts to it like I did to get into recovery, device not recognized under cmd "adb devices" or "fastboot devices" when connected to computer
Phone screen goes black for about 0.8 seconds when power button is held down and immediately pops back up into warning bootloader unlocked screen, trying to go into fastboot or anything like with volume down and power button achieves the exact same effect.
Any help would be greatly appreciated.
Edit2: If I hold the power button and down volume for 20 seconds (just ignore when the screen goes black and hold it for 20 seconds) it will boot into fastboot mode
Recovery seems to do nothing but the device is now recognized by the mototool all in one, I will report back if I figure out anything more useful, I am hoping the mototool will save me
Edit3: tried flashing stock recovery, my phone now says in pink "hab check failed for recovery", tried flashing CWM recovery, it seemed to work. I then clicked "fix boot logo" it worked. The phone is now showing the motorola logo but doesn't seem to be doing much else, I'll let it sit for a couple minutes.
Edit4: If none of this works at least you'll have an interesting read about how to further destroy your phone
Tried rebooting to recovery, the mototool thinks it did it but my phone stays stuck at the motorola logo. I then told it to check connection and it now thinks there is no longer a device connected. Tried turning the phone off again, went immediately back to the motorola screen. I seem to be in the same situation except the bootlogo is no longer that ugly text. Back into fastboot mode, lets see what else we can do.
I checked to see if it was recognized by command prompts now and it IS, if you go back under like you were unlocking the bootloader and open up a cmd prompt and type "fastboot devices" it's recognized in this fastboot mode. This has given me new optimism, I'm feeling hopeful that my device is not destroyed, hopeful and very hungry, I will report back in after getting food.
Edit5: I've realized that I have no idea where to go from here, while I can access command prompts I have no idea what commands to put in, I tried hitting "factory" under the fastboot in hopes that it would flash my factory recovery, no such luck, I'm back to the same situation, tried hitting BP tools next because I didn't know what it was and thought it would be helpful, no such luck, back to the same screen, my quickly inflated confidence is now waning, I do have hope that someone can fix this issue but I am thinking that someone is not me.
I hit the recovery button, I'm sure I had done this before but this time it worked, went to restore from sd card, and restored my backup I made right before all these issues, it recovered my device, I then restarted it and everything is good now.
Apparently I am an idiot, but that's okay because my phone is working again now, after only about an hour or something.
TO FIX YOUR ISSUE HOLD DOWN VOLUME AND POWER AT THE SAME TIME FOR 20 SECONDS, IGNORE WHEN THE SCREEN GOES BLACK, KEEP HOLDING FOR ALL 20 SECONDS, CHOOSE RECOVERY, THEN GO BACK TO YOUR BACKUP THAT YOU SAVED BEFORE FLASHING A NEW ROM, RESTART THE DEVICE AND NOW THE DAY IS SAVED
Related
I almost had a heart attack last night doing some kernel work. This is what happened, and how I got out of it.
I had just finished compiling a kernel I was working on and was excited to flash it and give it a run. So I built the boot.img and did
Code:
adb reboot bootloader
I got into the bootloader and
Code:
fastboot flash boot [B][I]boot.zip[/I][/B]
fastboot reboot
Working quickly, a got a little sloppy. Most unfortunately, I had a boot.zip in the same folder as the boot.img so boot.zip got flashed to the boot partition. Upon reboot, I got the usual splash screen but the upper left hand corner indicated I was in "RSD Mode 3". I pressed and held Vol up + power to get into bootloader but that was unresponsive. All I could do was press Vol Down + power which brought me back to the same state. I was unable to issue fastboot commands from here as well. This is what I did to fix it.
While I was in "RSD Mode 3" I did
Code:
fastboot flash boot boot.img
Even though there was no response from the device, I pressed Vol Down + power until the screen went black. I then quickly pressed and held Vol Up + power. The device then went into the bootloader, received the queued command from fastboot, and flashed the boot.img. Finally, I did
Code:
fastboot reboot
and was back in the game.
Guys, I think the moral of the story is to slow down and be careful with fastboot. You can bet i'll be a little more careful
good post I'm sure this will help devs in the future
way to stay calm under pressure lol. good info.
Small world, I used to live in Fontana for 25 years and moved to NY couple of years ago Oh and thanks for the tip
Ran into this today, i had a similar, but different experience..hope this helps
Once i got into the RSD 3 mode, fastboot commands were basically dead...all i would get was <waiting for device>...
in order to get out, i had to hold BOTH VOL+ and VOL- and Power at the same time, then as soon as the screen turned off, I had to press VOL- and power at the same time to get to a 'regular' looking boot screen. I saw regular because there was no text at the top ofthe screen; however fastboot commands would work here. Because i FUBAR'd a kernel install, i just did
fastboot flash boot boot.img
fastboot reboot
and voila...it was alive again
a bit scary though
Ok, so I definitely know the heart attack feeling, and hopefully someone here can help me out. I got my Xoom today(wifi), and went looking for a root. I found a link to a root here that -said- it worked for both 3g and wifi models(found out later that it doesn't, obviously). So, I flashed the boot image, and came up with the RSD message. At that point all fastboot and adb capability was lost, and I can't seem to get it back.
Here's what happens with the following button combo's:
Hold Power+VolUp and release on screen-black: Motorola splash screen(dual core etc) with no text in corner
Hold Power+VolUp until after the splash comes up: splash with "Starting RSD protocol support 3"
Hold Power+VolUp and then hold VolDown immediatedly afterward: Splash screen with "Starting Fastboot protocol support."
Hold Power+VolUp and then VolDown after waiting a second: Splash screen with NvFlash/RSD/Fastboot menu
Hold Power+VolUp and then press VolUp again: Splash with "Starting RSD protocol support 3"
If I choose Fastboot from the menu, it just sits at the "starting fastboot protocol support".
If I choose RSD, it gives me the "starting RSD protocol support 3"
If I choose NvFlash, it says "entering nvFlash (something) and the screen immediately goes black and the notification led comes on (sits there until reboot)
No other button combinations seem to do anything. Holding Power+VolDown doesn't do anything from any mode, and Power+VolUp+VolDown acts just like Power+VolUp.
In any mode, I can't issue fastboot or adb commands. Fastboot simply says <waiting for device> for anything. I tried the advice above, to queue up a "good" boot.img (from here at xda), but it doesn't recognize it on a reboot from/to any mode I can get to. I've tried each about 20-30 times now, and I'm about ready to test the thing's shatter-resistance with my fist, so any help here would be -greatly- appreciated.
Quick update to previous post: Resolved!!
My advice? If you get stuck unable to fastboot or adb in linux, try it in windows. I hadn't booted into win for over a year, so it never occured to me until I saw someone mention it in the Tiamat thread. Even a fresh JDK/SDK install in Ubuntu didn't work for me. I didn't have any tools or SDK's installed in my winXP partition, but after a quick install, it worked first time, so now I'm the happy owner of a rooted Wifi Xoom with SD card.
Once again, the XDA forum saves the day. I love this place.
I recommend everyone keep a backup copy of their system.img around just in case too. I was going nuts after messing with my framework-res.apk file to get SMS working (for the verizon web account activiation message). I used root explorer, and BAM! crash, crash, FC, FC, then stuck at the moto logo at boot. I couldnt get it back with just a boot.img flash. I went for broke and found a post of the HI66 system.img. it was HUGE, dont know if thats what I needed. but flashed that and I was back in business as nothing else was working and couldnt get ADB to take to push the old framework-res.apk.
I have a similar issue. I have tried for over three hours now to understand why I cannot reboot into fastboot. It seems lika I have lost both fastboot and NVflash. Only RSD mode and a logo screen without text. Can't shut it down with powerbutton or factory reset. I tried to root it with a 3g boot.img whitch was terribly wrong on a wifi-only xoom and I'm now trying to flash a stock wifi boot.img. It just sits there on the M dual core screen.
What can I do from RSD mode 3?
EDIT: I have a feeling that it has freezed on that logo screen. I want to try a hard reset and the only way for me is to try to first shut it down then power it on again. Don't know if it helps but it is silly to be unable to stop it. How can I shut it down?
I've tried all the suggestions above with no luck
Will try a windows machines tonight to see if that will help, but I fear I will need to send my Xoom back to mfg for rework
may seem a stupid suggestion but what if you let the battery go dead. it will turn off. Then connect to power supply and do a fast boot restart, holding power button and vol down.
Just a thought!
I will try but I think I already tried that. It seems like boot and recovery is dead. I tried to flash the 3g .sbf file today. Thought that an already bricked tab couldn't be more bricked and perhaps it would restore the recovery or boot but RSD Lite couldn't do it. It's unvisible for a computer. I've tried both win7 and my Arch Linux box. The device is dead. Hopefully they wont have to replace the motherboard. I'm sending it for repair on Monday.
mines bricked also says
failed image lnx 0x0002
starting rsd mode 2
i can get it in the fastboot protocol mode with the - button and power but cmd window says waiting on device. my started after i did an fastboot oem lock with a bad kernel.
dogma444 said:
mines bricked also says
failed image lnx 0x0002
starting rsd mode 2
i can get it in the fastboot protocol mode with the - button and power but cmd window says waiting on device. my started after i did an fastboot oem lock with a bad kernel.
Click to expand...
Click to collapse
iirc the Failed Image lnx 0x0002 is due to locking the boot loader with custom stuff.
Unplug xoom usb
boot into fastboot
plug in xoom usb
fastboot oem unlock
orionshock said:
iirc the Failed Image lnx 0x0002 is due to locking the boot loader with custom stuff.
Unplug xoom usb
boot into fastboot
plug in xoom usb
fastboot oem unlock
Click to expand...
Click to collapse
Man that just sound to easy to work. ADB has no clue the device is.....wel, a device! Its like my xoom de-evolutionized to a primitive state and is suffering from tourrets. Anyway command typed in adb gives you back < waiting for device >. I've tried just about all the techniques here on the forums. And the people who claim to have been brought back to life are not victims of this "RSD mode 2" Im pretty sure this is like a failsafe if you blow up the original bootloader, 3. IDK though, pretty sure they are going to require some hardware replacements. Im not sure people are recognizing the degree of our bricks. These are what appear to be real BRICKS. no "soft" ness up in here. straight up cement
http://forum.xda-developers.com/showthread.php?t=1041192
adb wait-for-device && adb reboot recovery
tried this command and seemed pretty slick but, still nothing
Same thing here, was there any solution?
Give this a try:
http://forum.xda-developers.com/showthread.php?t=1079784
Please, I have same problem, but I can just reset it by pressing and holding Vol Up + Power On. When I press Vol Down + Power Down, nothing happens. If I press Vol Down when it restarts, it doesn't show me the message but shows the Motorola Dual Core logo and stops. Even in this situation I can't comunicate via usb. Now it just turn off when the battery is totally low.
I CAN boot into fastboot mode and issue fastboot commands from CMD. apparently mine is booting into RMD 3 mode or whatever it's called. when I boot normally (just hold down power button, I get the moto dual-core screen, and then it boots into the Clockwork Recovery Mod... PLEASE HELP
I'm new to Xoom but gave unlocking and rooting a go. That was todays mistake! I flashed a 3g version of boot.img. Then I tried to flash back to stock img-file. Found out that it also was a 3g img-file. Flashed once more. Now it was a wifi-only boot.img. Now I'm stuck at the Motorola Dual Core logo with Starting RSD mode 3 written in top left corner. I can't shut this thing off or anything else but rebooting back to same screen. I really don't know what to do. I bought it yesterday from a man that bought it in the US a week ago so I can't go to the shop and I don't think there are any shop that can flash it for me because it's not available here in Sweden yet. Please help. I have RSD Lite installed and the correct drivers for the Xoom installed. I'm used to ADB but it can't find the device and fastboot doesn't see it either.
Edit. I can't go into fastboot mode.
Grab the wifi's boot.img off of here:
http://forum.xda-developers.com/showthread.php?t=1017398
http://forum.xda-developers.com/showthread.php?t=973355
This might be helpful. Not sure.
Don't worry you are in good company, even BRD had the same problem. Here's how he fixed it:
While I was in "RSD Mode 3" I did
Code:
fastboot flash boot boot.img
Even though there was no response from the device, I pressed Vol Down + power until the screen went black. I then quickly pressed and held Vol Up + power. The device then went into the bootloader, received the queued command from fastboot, and flashed the boot.img. Finally, I did
Code:
fastboot reboot
and was back in the game.
Guys, I think the moral of the story is to slow down and be careful with fastboot. You can bet i'll be a little more careful
Click to expand...
Click to collapse
Edit: Same advice as linked above by milehighclubAV8R
That doesn't do it. Propably it's some stupid misstake from me but I cannot do this because of " I pressed Vol Down + power until the screen went black". It wont get black. When I press Power + Vol down nothing happens. Am I doing something wrong. I have tried holding the buttons for about 30 seconds and nothing happens.
Did you just press the buttons or did you also enter the fastboot code as suggested?
First cmd command then pressing the buttons. When I reboot using power + vol up it starts into RSD mode 3. When rebooting it with power + vol up then vol down when black it starts into the logo screen without any text in the upper left corner. Can't even shut it down with long press on power button
Can I pull the battery? On my Galaxy S that's the way out if I get in a boot loop or need to redo a failed flash.
Not AFAIK, the unit is sealed and can't access the battery to pull it.
Perhaps ask in this thread - http://forum.xda-developers.com/showthread.php?t=973355, there may be more technical people seeing it there than in the general section.
OK. I will do that. Thank you for trying to help.
Press power+volume up. Hold it til it restarts. Let go of both buttons once you see the motorola logo then just press volume down once, and you should be then able to cycle through 3 different modes. Press volume down to cycle to different modes, volume up to select. Hope that helps.
Sent from my Xoom using XDA Premium App
Sorry but I can't cycle through anything. There are two modes. Either "Starting RSD mode 3" or nothing and RSDLite can't communicate with it so I belive that my xoom is dead. Sending it in for repair tomorrow. I'm giving up.
mine is stuck in the rsd mode 2. if i push and power and the up it will boot cycle if i the down button it says it is the the flashboot protocol mode, but i cannot get it to respond from the cmd window. my computer doesnt think its connected. i have the correct mot drivers. any help or is it bricked
Some people have been getting lucky with ADB commands however others have not been so luck. I myself am in the others category with one of my XOOMS.
Sucks, but some people have been able to get back. I however have not been so lucky with one of the WiFi XOOM's I have and did this purposely to see if maybe something can be done with it. Looks like we have to wait for all the files to be released......
Any day now Moto, util then people will continue to send these devices in and con the stores . For this, I applaud them.
This might work or it might not.
I had a bricked xoom too. no matter what fastboot i entered it wouldnt recognise it. all it would say is "waiting for device"
This is what i did.
Turn the xoom off
Do not connect you USB cable yet
Fastboot reboot-bootloader
It should say "waiting for devices"
Now plug your xoom
Turn on the xoom.
When you see the Motorola logo press volume down till you see "fastboot protocol"
Press volume up.
It recognise my xoom that way
couldnt turn mine off. let the battery run down. plugged it into power booted it up. no help. bricked
stevenege said:
Some people have been getting lucky with ADB commands however others have not been so luck. I myself am in the others category with one of my XOOMS.
Sucks, but some people have been able to get back. I however have not been so lucky with one of the WiFi XOOM's I have and did this purposely to see if maybe something can be done with it. Looks like we have to wait for all the files to be released......
Any day now Moto, util then people will continue to send these devices in and con the stores . For this, I applaud them.
Click to expand...
Click to collapse
I have to admit, I'm one of them. Sure is a nice way to tell Moto to hurry the F up. I can't say I felt great about it but I wasn't about to lose $600 either.
me to one of them
shipped mine back to the factory today. not sure what they can do to it. is there such a thing as a force flash or will they have to replace the firmare chip to make it work? unstable combo tegra and honeycomb, aint messin with mine anymore.
i just recovered mine from this. i flashed recovery with clockwork mod:
at the rsd 3 screen with the usb attached
fastboot flash recovery recovery.img
held the volume down while pressing the power off on until fastboot started flashing the recovery
fastboot reboot
xoom started in clockwork mod, did a restart and it worked
****This happened after attempting to load recovery from rom manager without flashing new recovery image.***
Did you happen to mention in your explanation about what went wrong with your xoom anything about unlocking or relocking?
The light was flashing, i thought someone i loved sent me a text, i pressed the button, the screen didn't come on, strange...Pressed it again, it rebooted, i felt the P.O.S.T. vibration and then the Pink Motorola Logo thats it. it wouldn't boot.
So, next day after a full charge i try again, still, stuck on moto logo. i pres vol- & Pwr get in to fastboot Vol- to recovery then vol+ to select. from there it just rebooted again and displayed motorola logo for an hour, so it wasnt doing squat.
so i go looking around for my stock rom, 4.4.3 WIND or (Dave Wireless) ----AWS 1700+2100 network---- Nothing. do some reading, see this moto g tool to convert to google play edition, WHY NOT RIGHT, so i try, nothing happens despite my pc telling me otherwise i still the same problem.
*cracks knuckles*
So i open up command prompt, try to remember my fastboot commands and unlocked my bootloader. i wipe everything, then go to install a rom by going through the "fastboot flash logo logo.bin commands. - this failed so i did some more reading, i need a motorola variant of fastboot, no problem, i download it.
everything is successful so far except recovery, i get Hab check failed for recovery or mismached partition size for whatever recovery from any source i could find at this point.
now at this point, i BELIEVE i had a xt1032 but fastboot tells me its a xt1034. i googled the specs of each, and well maybe i do have a xt1034 because of the aws,
so i read more, it says i should just continue with doing what im doing and forget about the errors, but it still wont boot.
can anyone walk me through fastboot by fastboot command to get me up and running on ANYROM with ANYRECOVERY
i just need it to boot.
I use this forums a lot for info but in this case i can't find any leads of whee to go with this, so wondering if someone can chip in some ideas?
I flashed a ROM via flashtool but wasn't happy with it, so i thought i'd just go back to stock and so used flash tool AKA emma to flash one of the options given there.
First attempt to flash it said "flash failed" or something like that and had the "flashing failed, connect to computer" note in the phone when booting it. (I'm sort of making up the terms, not that much into the tech ). Anyway, i tried flashing the same FW again and this time it went through really quick being 'completed' in a few seconds.
Now when i try to boot it gets stuck in the 'Sony' logo. Can go into Fastboot but no Flash Mode (nothing happens using the vol down key), and USB debugging seems to be off now as well.
Emma only works in Flashmode so can't do anything with that. Flashtool doesn't offer anything useful in Fastboot and Xperia Companion recognises the phone when in Fastboot but asks that i unlock the screen and enter MTP...
Any help of where i can go with this?
Thanks
P.s. While keeping buttons pressed randomly it went once into flash mode, but trying to flash a ROM with flashtool it got stuck at "reding device data" and i haven't been able to enter the mode again. Is there an alternative key press combination that i stumbled on by chance? I think i just kept vol up and power held for a while and let go at a random number of phone vibrations
Just tried: Flashed twrp via fastboot and then rebooted into recovery. Same thing. It still opens to Sony splash screen and stays there
Ok, i'm kind of talking to myself here, but mild success and something that might help someone.
Managed to get back in flash mode. Don't know if it's a fluke, unique to this phone, or how it's actually meant to work, but the sequence is:
From the freezed up splash screen, and the USB connected, press and keep pressed power+vol up (hard restart/shutdown)
You get a single vibration, if you let go here it restarts. Keep pressing
You get a triple vibration, if you let go here it shuts down. Keep pressing
You get a single vibration, if you let go here it starts in fastboot. Keep pressing
You get a second single vibration, if you let go here it starts in flash mode.
Possibly a fluke but don't want to have to try again!
Anyway, i managed to flash the last working firmware and it's all good, yet this is the unwanted one. So issue is i still need to downgrade the phone to 7.1.1
Moto G7 Power XT1955-5: Stuck in BootLoop at "Unlocked and Can't Be Trusted"
I made several attempts to install twrp-3.4.0-0-ocean to this new Moto G7 Power. I was able to Unlock the Bootloader, and even had TWRP running twice., but after it was rebooted it would never go back to TRWP, it would reboot to the Stock ROM. Then, runnng adb reboot bootloader would bring me back to the stock bootloader page.
Each time it boots, it has displayed the "Your Device Has Been Unlocked and Can't Be Trusted." page, and then would eventually boot. Annoying, but ok. It is what it is.
However, this last attempt to reboot from the stock bootloader has created an endless bootloop to that "Cant Be Trusted" page.
No combos of holding down the down volume for 3 seconds with the power key.. or holding down the power key for 15 or 20 seconds.. nothing works. All it does it turn the screen off for a couple of seconds and then goes back to the "Can't Be Trusted" warning page.
Well.. turns out it does work, it's just finnicky. This video showed me how to do it.. https://www.youtube.com/watch?v=fA0DHvbIlWY
Holding down the Down Volume and Power for several seconds until the screen goes black, release the buttons, then waiting a moment will allow the bootloader to appear.
1- Should I replace the stock rom? If so, how? I can't boot far enough along to run adb push.. and TWRP will not run.
What I cant do now is factory restore the device. Where can I get a stock rom, or any suggestions? I am pretty sure that's what I get for trying to use the xt1955_5.img file from Minimal+adb_fastboot_platform-tools_r29.0.6_2020 on unofficialtwrp.com's how to page, right?
Thanks in advance..
bryangrant4 said:
I made several attempts to install twrp-3.4.0-0-ocean to this new Moto G7 Power. I was able to Unlock the Bootloader, and even had TWRP running twice., but after it was rebooted it would never go back to TRWP, it would reboot to the Stock ROM. Then, runnng adb reboot bootloader would bring me back to the stock bootloader page.
Each time it boots, it has displayed the "Your Device Has Been Unlocked and Can't Be Trusted." page, and then would eventually boot. Annoying, but ok. It is what it is.
However, this last attempt to reboot from the stock bootloader has created an endless bootloop to that "Cant Be Trusted" page.
No combos of holding down the down volume for 3 seconds with the power key.. or holding down the power key for 15 or 20 seconds.. nothing works. All it does it turn the screen off for a couple of seconds and then goes back to the "Can't Be Trusted" warning page.
Well.. turns out it does work, it's just finnicky. This video showed me how to do it.. https://www.youtube.com/watch?v=fA0DHvbIlWY
Holding down the Down Volume and Power for several seconds until the screen goes black, release the buttons, then waiting a moment will allow the bootloader to appear.
1- Should I replace the stock rom? If so, how? I can't boot far enough along to run adb push.. and TWRP will not run.
What I cant do now is factory restore the device. Where can I get a stock rom, or any suggestions? I am pretty sure that's what I get for trying to use the xt1955_5.img file from Minimal+adb_fastboot_platform-tools_r29.0.6_2020 on unofficialtwrp.com's how to page, right?
Thanks in advance..
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Glad you're out of boot loop.
Recovered from bootloop and "dead" bootloader screen! Tips to recovery
I was able to Rescue the device from periodic BootLoops and a dead end Bootloader screen.
I referenced the information on this thread in the XDA forums, specifically the “Motorala Unbricking Tools” section.
I then tried the "LMSA: Lenovo's Motorola Smart Assistant" thread to find the link to the Lenovo / Motorola download page.
The Rescue software is a bit clunky. Powerful, but clunky.
There are also some cool tools such as Clipboard Copy Text between Device and PC, a Gif Maker, a Ringtone Maker, and a SCREEN RECORDER!!
Back on Track with the Rescue:
-Linux or Mac versions are NOT available; Windoze only.
-You will need at least 2gb of ram in your virtual Windoze7 machine to run it or it will not run in a useful manner.
- Parallels16/Windoze7-64bit worked fine.
-WINE based installs will NOT work.
To run, you will need to enable USB Debugging, although there are two other ways to connect the phone I did not also try. There even appears to be a way to rescue even a truly bricked dead device.
To Rescue your device:
Download, Install, and Run Rescue and Smart Assistant.
The Rescue process will NOT relock your bootloader.
Select the Rescue tab, then select Rescue Now. If you need to backup the device, try the Backup button right next to the Rescue Now button.
The application has some bugs, shortcomings.. here's some heads up to reduce Stress caused by those bugs..
The software will ask you to select the phone you own. The slider dialogue UI is badly done, so you will go back and forth a dozen times before learning how to navigate the menu. It might auto-recognize, but it did not on mine. Good luck!
Next, download the ROM.. the progress bar does not reflect what is actually going on. Once the 2bg down is 100% complete, it will sit there for a LONG TIME doing nothing. Dont kill the app and restart. It's actually busy unpacking the .zip Rom file into a directory tree on your harddrive. Just go eat some lunch, and come back.
Then, a similar issue occurs when you install the ROM. The progress bar is pretty much done, it just sits there doing nothing.. Let it go for a long time.. it's actually doing it's job, and the progress bar is just badly done.
If you are going to use the backup.. TURN OFF YOUR POWERSAVING stuff on both ends. If it is interupted by Power Saving/Sleep mode, the software will start at the beginning. The backup process takes hours, not minutes, so this is not a good result.
Once backed up, if you are moving to a new phone, there is a couple of ways to do that. I am going to perform these functions today or tomorrow, and will update with the results of those efforts.