Help recovering from Nandroid Backup ? [Solved] - Hero, G2 Touch Android Development

Hi I tried installing the "HERO21 Community (version 1.8)" (see here)on my rooted Tmobile G2 which was previously running the 3.0 modoco rom.
When I started it up for the first time when it finally loaded I got about 15 force close messages that kept reappearing.
I did a nandroid backup before hand but I was wondering how can I get to this seeing as I can't use the adb command prompt because I can't mount the MicroSD Card anymore ?
I tried pressing Home and the Power button but it comes up with a picture of a phone and exclamation mark ?
I can get into the hboot mood using volume down and power but I don't know how I can get to mount the SD from here. Previously the way I got into the nandroid recovery thing was by using this command in command prompt when my MicroSD was mounted "fastboot boot recovery-RA-hero-v1.5.3.1.img"
Thanks
Edit: If it helps I can still gain access to my Micro SD using a usb card reader I have?

Nobody got any ideas or am I screwed lol ?
Edit: If what I said originally didn't make any sense basically I can't mount my SD Card because the custom Rom I've flashed onto my Hero so I can't work out a way to get back to the recovery mode ?

james_white said:
Nobody got any ideas or am I screwed lol ?
Edit: If what I said originally didn't make any sense basically I can't mount my SD Card because the custom Rom I've flashed onto my Hero so I can't work out a way to get back to the recovery mode ?
Click to expand...
Click to collapse
still doesn't make any sense for me. if you want recovery shut down the device, then hold home and push power. hold home until you see the recovery menu.

Have since solved it by doing some kind of reset which I don't really understand what it changed tbh but I'm not complaining I've got 2.1 on there now
Also I had tried home + power but it gave me a picture of a phone with an exclamation mark, Thanks anyway.

Related

Problems with ROOT, Am I bricked!???

I was rooted and running a 2.2 rom and wanted to install the damagecontrol 3.2 rom, which, as I understand it, requires NAND to be unlocked. I downloaded Simple Root and tried to unlock NAND.
When I turn on the phone I get stuck in a boot loop.
I try the recovery console. It takes a few minutes to load PC36diag.zip, the update for NAND which I already installed.
When I say no to the update and no to restarting I get into the menu, but if I try RECOVERY it loads the phone with the exclamation point, but I am unable to connect using the adb batch file I have always used before.
Also, when I try HBOOT USB the drivers aren't able to be installed. The device is read as "Android 1.0".
Can someone please help me?
devin.slick said:
I was rooted and running a 2.2 rom and wanted to install the damagecontrol 3.2 rom, which, as I understand it, requires NAND to be unlocked. I downloaded Simple Root and tried to unlock NAND.
When I turn on the phone I get stuck in a boot loop.
I try the recovery console. It takes a few minutes to load PC36diag.zip, the update for NAND which I already installed.
When I say no to the update and no to restarting I get into the menu, but if I try RECOVERY it loads the phone with the exclamation point, but I am unable to connect using the adb batch file I have always used before.
Also, when I try HBOOT USB the drivers aren't able to be installed. The device is read as "Android 1.0".
Can someone please help me?
Click to expand...
Click to collapse
Bootloop means you need to do a full wipe.
First thing's first, delete the PC36IMG.zip file from your SD. Then when you get the image of a phone with an exclamation mark, hold down the power and volume up key to get into recovery.
As for the last bit, I'm sorta' confused what you're problem is.
Part of my problem is that I can't delete the file from the SD card. Can't get into the OS and can't turn on USB.
Something similar happened to me. For me, instead of booting Damage Control, I switched it to Fresh and booted Fresh v3.0 and it worked and booted. Then I unlocked the Nand and made a nandroid. Then whipped everything 2 times and booted DC and it worked fine after that.
devin.slick said:
Part of my problem is that I can't delete the file from the SD card. Can't get into the OS and can't turn on USB.
Click to expand...
Click to collapse
You can get in to usb and put fresh on there by going to recovery mode and selecting one of the options that says USB, i can't remember the exact wording.
Added: I just checked it's called "USB-MS toggle"
devin.slick said:
Part of my problem is that I can't delete the file from the SD card. Can't get into the OS and can't turn on USB.
Click to expand...
Click to collapse
When you get the exclamation mark screen, hold down the Power and Volume Down key. Once in recovery mode, select the USB-MS Toggle feature, this mounts your SD card yto your PC. You should then be able to access the root of your SD card via the Removable Disk icon on your computer.
It wouldn't let me load USB from the console/whatever either... Another weird driver issue.
But after several more hard battery pulls I let it try again to boot and it showed me the "HTC, quietly brilliant" boot screen, which was different that what it had before.. I let it load and now I'm in android, but it says my SD card is removed.
Is this a part of the process necessary to unlock NAND?... Do I have NAND?
devin.slick said:
It wouldn't let me load USB from the console/whatever either... Another weird driver issue.
But after several more hard battery pulls I let it try again to boot and it showed me the "HTC, quietly brilliant" boot screen, which was different that what it had before.. I let it load and now I'm in android, but it says my SD card is removed.
Is this a part of the process necessary to unlock NAND?... Do I have NAND?
Click to expand...
Click to collapse
Check and see if your USB connection is in Charge Only or Disk Drive mode.
devin.slick said:
Is this a part of the process necessary to unlock NAND?... Do I have NAND?
Click to expand...
Click to collapse
no. You make your nand back up when you are in recovery mode and you select nand back up and it backs up everything. You'll need to follow through with the rest of the Nand unlocking instructions.
Did you download and follow the steps of the flash_image and mtg-eng.img etc etc...? Then the rest of the steps?
That's the first thing I tried to do when android loaded. It's not even an option. It says I removed my SD card.
I restarted, denied the update to get through to recovery, and I still can't connect with adb -it shows "Unknown Device" in the device manager.
devin.slick said:
That's the first thing I tried to do when android loaded. It's not even an option. It says I removed my SD card.
I restarted, denied the update to get through to recovery, and I still can't connect with adb.
Click to expand...
Click to collapse
are you connected with charge only? try hot sync (you need to install the program, which include drivers. this is on the htc website)
Mine worked for hot sync but not charge only
Looks like you may need to run through this. http://forum.xda-developers.com/showthread.php?t=695243
I've been reading that post.
When I select fastboot, it gives me other options.
bootloader
reboot
reboot bootloader
powerdown
If I select bootloader it takes me back to the main menu, if I select reboot, I get back to android and still do not have access to my SD card, so I can't get out of the debugging rom, or whatever it is.
I put another SD card in, so I don't have to wait on the update.zip to be read every single reboot, but that's all it did.
Am I doing something wrong?
Don't know then... sorry. You can try starting over from the beginning?
Best of luck.
FML.
Someone? I'm totally stuck.
And my phone says the the charger isn't delivering sufficient voltage... and I'm down to 8%.
HEEELLLPPP
its always an good idea to have a micro sd to sd adapter
After 3 locations, I found a Sprint store that actually existed... had them copy an update.zip that I brought on a flash drive onto my micro sd card. I tried booting into recovery and it didn't do the update. They suggested another store that does repairs, so I went to my 5th store, where I just dropped off my phone, hoping they'll reflash it fore me. I'm expecting a call back.
What a wonderful birthday this is turning out to be... lol. FML
UPDATE: I called them and they said the phone needs to be exchanged... but I don't know how they're going to react to it having the recovery/debug version of android on it.
Does anyone have ANY advice?
Just tell them to put in a fully charged battery for you. Then when you get it home try the Simple Root Guide you tried at first. This time post your issue (if you have any others) in that thread and myself or Jiqqa will help. Make sure before starting that guide that you have .NET framework and HTC sync installed on your computer. But you should be able to root phone and then be able to flash custom ROM after that.

[Q] DHD crashed and won't go pass the Bootscreen/ can't navigate it either

Hallo,
just now I was trying to open an app on my DHD but it kept force closing so I decided to Normaly restart it. When I did that it went to the Welcome Logo then got stuck and kept on turning on and Off.
Then I removed the battery and tried again. This time the Bootscreen appeared (I was glad since I could recover a backup version of the RAM) but to my amazement I couldn't navigate through the options. Even the power button didn't work. I tried several times but with the same results.
I was wondering is there a way to restore my mobile from my laptop (USB Debugging?) now after I reached this state?!
How could I solve this?
Any help would be appreciated
UPDATE: I noticed before the Bootscreen loads, there appears some messages quickly before they disappear. I kept on turning my phone on and off to see what they said eventually I came out with this
P98DIAG.ZIP
Image not found
.
.
P98DIAG.NBH
Image not found
.
.
ring any bell?
Reda88 said:
Hallo,
just now I was trying to open an app on my DHD but it kept force closing so I decided to Normaly restart it. When I did that it went to the Welcome Logo then got stuck and kept on turning on and Off.
Then I removed the battery and tried again. This time the Bootscreen appeared (I was glad since I could recover a backup version of the RAM) but to my amazement I couldn't navigate through the options. Even the power button didn't work. I tried several times but with the same results.
I was wondering is there a way to restore my mobile from my laptop (USB Debugging?) now after I reached this state?!
How could I solve this?
Any help would be appreciated
UPDATE: I noticed before the Bootscreen loads, there appears some messages quickly before they disappear. I kept on turning my phone on and off to see what they said eventually I came out with this
P98DIAG.ZIP
Image not found
.
.
P98DIAG.NBH
Image not found
.
.
ring any bell?
Click to expand...
Click to collapse
Can you navigate any menus? If you can't you probably have a volume key hardware issue. If you can, i would just put a p98diag.zip on the root and reflash (use the rooted one).
Sounds like you are booting into bootloader. You need recovery. Pull the battery, then reinsert and hold volume down + hit power. If that doesn't work if you have adb set up on computer, plug it in to computer and use adb reboot recovery.
Sent from my Inspire 4G using XDA
I guess that you have a PD98IMG.zip on sd card.
Remove it or everytime you reboot in bootloader it will ask you to update in a never ending story. Probably this is why all other commands are not working except reboot.
Then reboot bootloader and go to recovery.
No I can't navigate (the weird thing is the power button also dosen't respond) it's like it freezes as soon as it turns on... Could you give me the PD98IMG.zip in a separate link?
I tried reinst the battery while holding the volume + but it didn't work. It vibrated 4 times while the charge light turned green but that was it. It stayed green and the screen was off...
I've always had the volume keys issue even before it went crazy (they do not always respond to my press) but I just installed 3rd party apps as a workaround.
I couldn't find the p98diag.zip anywhere on the SD card (could you give me the path for it?)
I will try to reboot it through my laptop but could someone give me the commands I should write? I'm not that experienced in that field.
Btw I left it for a while before I turned it on again, it went into Safe Mode (no apps no nothing) then I turned it off and after several tries it finally turned on in the normal mode and was almost stable until I restarted it and it went to point 0 again and now I'm stuck with the bootscreen :S
Thanks for your help
Do you have adb set up on your computer? If so then connect phone to laptop. Open command prompt type "adb remount" then "adb reboot recovery"
Sent from my Desire HD using XDA
while looking through the files I used to root my phone when I bought it I found the p98diag.zip. I copied it to my SD Card and wanted to install it. It found it but then it said
Parsing...[SD ZIP]
[1] BOOTLOADER
[2] BOOT
....
but it's been like that for 2 hours now. I tried reinst the battery and pluging in the mobile to my laptop but it didn't recognize it. (I tried the adb and it gave me Device not found" error!
Is it normal for the phone to take long to parse the zip file? what should I do now?
Reda88 said:
while looking through the files I used to root my phone when I bought it I found the p98diag.zip. I copied it to my SD Card and wanted to install it. It found it but then it said
Parsing...[SD ZIP]
[1] BOOTLOADER
[2] BOOT
....
but it's been like that for 2 hours now. I tried reinst the battery and pluging in the mobile to my laptop but it didn't recognize it. (I tried the adb and it gave me Device not found" error!
Is it normal for the phone to take long to parse the zip file? what should I do now?
Click to expand...
Click to collapse
You shouldn't have installed pd98diag. I would suggest either trying to run the ruu to get back to stock, or find the stock rom in pd98img.zip form and place on root of sdcard. Then reroot and start over.
Edit: if you find the stock rooted in pd98img.zip form that should work too and you won't have to reroot.
Edit 2: be sure to remove the pd98diag.zip from your sd card.
Sent from my Desire HD using XDA
bcd420 said:
You shouldn't have installed pd98diag. I would suggest either trying to run the ruu to get back to stock, or find the stock rom in pd98img.zip form and place on root of sdcard. Then reroot and start over.
Edit: if you find the stock rooted in pd98img.zip form that should work too and you won't have to reroot.
Edit 2: be sure to remove the pd98diag.zip from your sd card.
Sent from my Desire HD using XDA
Click to expand...
Click to collapse
Good advice! I still have all the files I used to root (even the RUU)
And you're right I shouldn't have flashed the old pd98img because now my laptop can't recognize my mobile and I can't debug it from the command line (it says Device not found)
Can I still be able to root the img without using my phone? I used this guide to root my phone (http://www.addictivetips.com/mobile/how-to-downgrade-htc-desire-hd-to-root-it-after-ota-update/)
Where can I find the rooted img? and will it be possible for me to upload it here so that someone could root it for me on his device and give it to me rooted?
To boot into recovery
Hold down volume - button (not +) while pressing power button.
Let go of power button but continue pressing down on volume -.
Hey presto ... recovery.
It's a very easy mistake to make, I did it myself a few times when I first got into rooting and flashing ROM's.
lol!
no mate I wish it was like that.
Found this in the inspire section may be helpful. http://forum.xda-developers.com/showthread.php?t=986014
Sent from my Desire HD using XDA

[Q] Rooted Desire Hd help please

Hi had all different roms on my DHD and settled on Ice cold sandwich which it has been running for a few months now, earlier on today I noticed that it had gone off and only the backlight was on, So I restarted it and it started loading the screen up but then just went into a loop.
So i pulled the battery and went into recovery and reloaded the ICS rom, but know it just vibrates 5 times and shows the splash screen and goes off with just the backlight on again.
I can get into fastboot but when i press the button for recovery it does the same I've tried every pd98img I could find and it says wrong image after I try and load them.
And when I connect it to the pc it can't be recognised by htcsync or thru any adb commands, and windows tried to load a driver called Q_USB-DLOAD or something similar then loads a qualcom usb driver but adb commands still won't recognise it, been looking all bnight for an answer getting desperate.
Thanx in advance Michael
1. Remove your sd card and try to boot up again if it boots up then there might be something corrupted on your sd. (Possible sd may have gone bad)
2. Try to enter hboot with power button and volume down at same time to see if you can get into hboot. If it dont your boot img may be damaged and you may need to push it again thru ADB.
3. If you can get into recovery try full wipe and reflashing rom. (You may have to use an adapter to get rom on to sd since computer dont see phone then place sd back in phone)
These are just a few ideas you can try hope it helps.
EDIT: Also there is no need to create a double post of the same issue. This is what causes clutter among the forum. When you post a question you need to wait for an answer not ask again when there is no reply on your first post. Thank you

[Q] Help! Accidentally deleted system and can't restore or install

Coming from a phone with microSD extension, I had never encountered such an issue:
I bought this phone with a stock 4.2 Rom installed and tried to install a custom Rom. I first installed the latest version of touch recovery (tried it and it seemed to work fine) and did a backup using the default settings. Then I erroneously chose to format system and data, thinking that I could then "install from zip". Strangely, these steps deleted everything in the /sdcard directory and I couldnt select "external SD" (because the phone isnt equipped with it anyways?). Then I made a second mistake and restarted the phone, despite the message warning that I no longer had an OS installed. I took the battery out, and then held the power down while pressing the power button. The phone couldn't get into recovery, but instead showed a screen with the android logo, a large "Start" sign above it, and "Downloading...", "Do not turn off target !!" below it. Pressing the power button now got the phone to show just "Google" and a lock logo under it. The PC (windows 7) can not detect the phone throughout the process.
I tried the latest tool kit and samsung's USB driver but couldnt get the phone recognized by the PC.
Does this mean that the phone is doomed???
Please help!!!
Trent
Relax, it's not easy to 'doom' your Nexus. Especially with all the hard-workers in XDA
Try accessing Recovery mode by holding down BOTH vol up + vol down, as well as power. Holding just vol down + power is 'Download Mode', and at the least you can get to this. Means your phones far from doomed
Thanks a lot for the reply!
As a matter of fact, I also figured out how to get back to recovery (if only I had read your post earlier, my pain would've been much less!). But the problem remains that I can not get a target ROM onto the phone, since: 1. whatever I did seemed to have gotten rid of the nand backup supposedly stored in /data/media/TWRP/BACKUPS/ (I'm using TWRP V. 2.3.2.1). 2. I can not get my PC(or Mac, for that matter) to recognize the phone or the internal storage.
Any pointer from here?
Thanks again!!!
Trent
You can download a factory image and install with fastboot. It's quite easy and instructions are readily available on this forum. You can then install a custom ROM afterwards if stock is not your thing.
Found the answer finally!
It's the adb push method. Basically, it's to install adb drivers and execute a few commands via the command window. Not too bad... Don't know much about fastboot yet though ... If anyone else needs more details, please PM me (to save public bandwidth).
Thanks a lot anyways, whpnhp and jocalderone!!!
Trent

[Q] Updating GPE failed via sideload now no ADB connection

Device charges but that's all.
Nothing detected in USB devices. I tried factory reset and different cables. No good.
I get no Android file transfer program ( I'm on a mac) when I plug into USB.
Any ideas?
gunnyman said:
Device charges but that's all.
Nothing detected in USB devices. I tried factory reset and different cables. No good.
I get no Android file transfer program ( I'm on a mac) when I plug into USB.
Any ideas?
Click to expand...
Click to collapse
I had major problems as well. Remove your SD card and download the 510 stock rom. Reinsert SD card and manually boot in recovery by powering off your device, then holding the down button and powering on your device while still holding the down button. This will put you into your bootloader where you will be able to access recovery and install the 510 stock rom.
of course, if you have a good backup you can skip the last part and once in recovery restore your backup to get you back into action. Look in the developer section for further possible ways to do this there is a full backup that you can install from TWRP that may solve your problem. I was unable to make it work, and am hoping somebody will find an answer for me, but maybe it will work for you!
sleekmason said:
I had major problems as well. Remove your SD card and download the 510 stock rom. Reinsert SD card and manually boot in recovery by powering off your device, then holding the down button and powering on your device while still holding the down button. This will put you into your bootloader where you will be able to access recovery and install the 510 stock rom.
of course, if you have a good backup you can skip the last part and once in recovery restore your backup to get you back into action. Look in the developer section for further possible ways to do this there is a full backup that you can install from TWRP that may solve your problem. I was unable to make it work, and am hoping somebody will find an answer for me, but maybe it will work for you!
Click to expand...
Click to collapse
Turns out all three of he usb cables I tried were bad
Got that fixed.

Categories

Resources