I've been trying to re-root my phone since late last night, and have had nothing but problems. I've searched all over the internet, and tried anything that I thought would apply to my situation in the slightest.
I originally downgraded from 2.3.4 to 2.3.3 and rooted my phone using the method in this thread:
http://forum.xda-developers.com/showthread.php?t=1298990
I ran Revolutionary, ClockworkMod, and SuperUser. Everything worked perfect the first time around. Installed the Cyanogenmod 7.2 ROM and Tiamat v1.1.5 kernel. Then I started having issues with my battery, and Cyanogenmod seemed to be increasing the issues. At that time HTC announced they'd be releasing ICS, yada yada yada. I found a stock ROM online, and installed it, and updated as they were released OTA. Having finally gotten a new extended battery, I'd like to re-root & ROM my phone, but I've hit some road blocks.
I currently have the Android Version of 2.3.4 & Software Number of 5.10.605.9
I tried to re-do the entire process that had previously worked for me, but once I used the command hack-vivow.cmd, the phone would boot to the Revolutionary (of HBOOT ?) screen. Command line shows this, and just hangs:
c:\vwhk-12102011-c>fastboot oem rebootRUU
< waiting for device >
Click to expand...
Click to collapse
Phone shows this:
-Revolutionary-
VIVO_W XB SHIP S-OFF RL
HBOOT -6.13.1002
RADIO -1.09.01.1111
eMMC -boot
Click to expand...
Click to collapse
Phone gives me the options of "BOOTLOADER", "REBOOT", "REBOOT BOOTLOADER", & "POWER DOWN". "REBOOT BOOTLOADER" changes "FASTBOOT" briefly to "FASTBOOT USB", but changes back in about 15-20 seconds. When I select "BOOTLOADER", the screen freezes for a few seconds, and it won't let me select any options, "FASTBOOT" changes to "HBOOT", and I get this in green text:
SD Checking
Loading...[PG32DIAG.zip]
No image!
Loading...[PG32DIAG.nbh]
No image or wrong image!
Loading...[PG32IMG.zip]
Click to expand...
Click to collapse
The next screen of green text says "Parsing...[SD ZIP]" followed by 9 things, and I'm only given an option to Update or No/Reboot. No/Reboot reboots my phone into an endless bootloop, until I remove the battery and power back on with Volume Down + Power Button. Update does a reset of my phone, and puts me right back to where I am now. While it is updating there is an error message at the bottom that says "Can not roll back hboot version".
I've tried multiple things to attempt to fix this... I ran the TacoRoot method from here:
http://forum.xda-developers.com/showthread.php?t=1751796
When the 8th line was completed
adb shell /data/local/tacoroot.sh --setup
Click to expand...
Click to collapse
, the phone rebooted, it got stuck in a bootloop.
So that's where I am now. I'm stuck with S-Off, the PG32DIAG/PG32IMG errors, an HBOOT that seems to be far too new of a version, and I haven't found a way to get back to 2.3.3. As you can see I'm a noob. I'm really not sure where I went wrong (other than going back to a stock ROM and allowing it to update). Unfortunately a lot of things are just way over my head, without seeing a step by step process. But I'm just stuck at the moment. If anyone has any ideas on how to fix this, or any ideas of things to try I GREATLY appreciate it.
Still looking for an answer, but I've done some more digging.
Would I be correct is assuming that I have to find a way to downgrade hboot (which Revolutionary won't allow) and get S-On, in order to do what I need to do? If so, does anyone know of an accurate way to accomplish this? All I've found are old threads that apparently are no longer relevant for newer Software & hboot updates.
Cleanincubus said:
Still looking for an answer, but I've done some more digging.
Would I be correct is assuming that I have to find a way to downgrade hboot (which Revolutionary won't allow) and get S-On, in order to do what I need to do? If so, does anyone know of an accurate way to accomplish this? All I've found are old threads that apparently are no longer relevant for newer Software & hboot updates.
Click to expand...
Click to collapse
I am by no means an expert, but my limited understanding would suggest this: try flashing a new recovery like clockworkmod with fastboot. If that is successful you can flash a superuser zip in clockwork. I don't recall the steps to flash the recovery, but I think since you are s-off you should be able to do it fairly easily.
gtdtm said:
I am by no means an expert, but my limited understanding would suggest this: try flashing a new recovery like clockworkmod with fastboot. If that is successful you can flash a superuser zip in clockwork. I don't recall the steps to flash the recovery, but I think since you are s-off you should be able to do it fairly easily.
Click to expand...
Click to collapse
Sorry for my ignorance, I'm trying to understand exactly what you mean. From my very limited knowledge, there might be 2 ways of doing what you're saying.
First, rebooting the phone with Volume Down + Power button, with the the ClockworkMod file placed on the root of my SD card, and renamed PG32IMG.zip. Then selecting Bootloader, and allowing it to Update.
Second would be rebooting the phone (Volume Down + Power), and then "force" the flashboot via command, with the phone connected to the USB cable.
The 1st option I would love to try, if that has a chance of working. The 2nd option though, won't work, because the phone won't respond to any commands via command lines.
The reason I'm not immediately jumping on option #1 for a try, is that I might be on track to get things straightened out, with a possibility of critical failure. I found this thread:
rootzwiki.c om/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
I'm currently using Revolutionary, but apparently Alpharevx is a previous incarnation of that, and some users in that thread claim that it worked for their Revolutionary S-Off phones. So far, I have gotten to the point where I now have Android Froyo/ Android version 2.2.1 (from the same way of doing things as Option #1 above). The rest of that thread is messing with the Bootloader, which I'd rather not risk if I don't have to (I do realize how serious the consequences are). If there's any other way to do it, I'll gladly give it a try, as long as it doesn't put me in a place much worse than I'm at now (bricking my phone by messing with the bootloader certainly would be.)
I apologize for being a pain in the ass, I just want to make sure I understand any recommendations fully before I do something wrong. Clearly I should have done a lot more research before "un-rooting" my phone. Had my original issues not been my battery, I'd still be out of warranty for having S-Off. :laugh: Thank you very much for the response, it is truly appreciated.
Cleanincubus said:
Sorry for my ignorance, I'm trying to understand exactly what you mean. From my very limited knowledge, there might be 2 ways of doing what you're saying.
First, rebooting the phone with Volume Down + Power button, with the the ClockworkMod file placed on the root of my SD card, and renamed PG32IMG.zip. Then selecting Bootloader, and allowing it to Update.
Second would be rebooting the phone (Volume Down + Power), and then "force" the flashboot via command, with the phone connected to the USB cable.
The 1st option I would love to try, if that has a chance of working. The 2nd option though, won't work, because the phone won't respond to any commands via command lines.
The reason I'm not immediately jumping on option #1 for a try, is that I might be on track to get things straightened out, with a possibility of critical failure. I found this thread:
rootzwiki.c om/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
I'm currently using Revolutionary, but apparently Alpharevx is a previous incarnation of that, and some users in that thread claim that it worked for their Revolutionary S-Off phones. So far, I have gotten to the point where I now have Android Froyo/ Android version 2.2.1 (from the same way of doing things as Option #1 above). The rest of that thread is messing with the Bootloader, which I'd rather not risk if I don't have to (I do realize how serious the consequences are). If there's any other way to do it, I'll gladly give it a try, as long as it doesn't put me in a place much worse than I'm at now (bricking my phone by messing with the bootloader certainly would be.)
I apologize for being a pain in the ass, I just want to make sure I understand any recommendations fully before I do something wrong. Clearly I should have done a lot more research before "un-rooting" my phone. Had my original issues not been my battery, I'd still be out of warranty for having S-Off. :laugh: Thank you very much for the response, it is truly appreciated.
Click to expand...
Click to collapse
So with Froyo on there can you get to the stock recovery?
Oh wow, yes I can. I just tried the fastboot clockworkmod flash, but it doesn't seem to be working, or even more likely, I don't know what I'm doing.
I booted the phone with Volume Down + Power, selected "Fastboot", which changed HBOOT to FASTBOOT USB. I used the command prompt and typed "fastboot flash recovery cwm-4.0.1.4-vivow.img". The command prompt stalls at "< waiting for device >" and FASTBOOT USB changed to FASTBOOT. Maybe I just don't know what to do after than. I tried "Recovery", which I thought would have booted ClockworkMod, had it been installed properly.
Cleanincubus said:
Oh wow, yes I can. I just tried the fastboot clockworkmod flash, but it doesn't seem to be working, or even more likely, I don't know what I'm doing.
I booted the phone with Volume Down + Power, selected "Fastboot", which changed HBOOT to FASTBOOT USB. I used the command prompt and typed "fastboot flash recovery cwm-4.0.1.4-vivow.img". The command prompt stalls at "< waiting for device >" and FASTBOOT USB changed to FASTBOOT. Maybe I just don't know what to do after than. I tried "Recovery", which I thought would have booted ClockworkMod, had it been installed properly.
Click to expand...
Click to collapse
I think you should be able to do 1B at this little how-to site:
http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
Cleanincubus said:
Oh wow, yes I can. I just tried the fastboot clockworkmod flash, but it doesn't seem to be working, or even more likely, I don't know what I'm doing.
I booted the phone with Volume Down + Power, selected "Fastboot", which changed HBOOT to FASTBOOT USB. I used the command prompt and typed "fastboot flash recovery cwm-4.0.1.4-vivow.img". The command prompt stalls at "< waiting for device >" and FASTBOOT USB changed to FASTBOOT. Maybe I just don't know what to do after than. I tried "Recovery", which I thought would have booted ClockworkMod, had it been installed properly.
Click to expand...
Click to collapse
I also just noticed...did you do "fastboot devices" first to make sure it actually recognized your phone? I'm really guessing, but I figured it was worth asking.
Yes it does recognize my phone. I think you're exactly right, in the direction you're showing me. I think flashing CWM is the key to getting this all to work.
But I'm getting some strange stuff happening. When I was finally able to select the Fastboot section, I had CWM saved as PG32IMG.zip. I started getting an error (black screen with a little center image of my phone, with a red "!" on it), after rebooting. I had to press Volume Up + Power, which brought me to some kind of Android settings (Wipe Cache, & something about clearing or wiping partition). I selected to just reboot, and the phone rebooted fine. I changed the PG32IMG.zip file back to the Froyo, and I can no longer get past the "Recovery" and forcing to do the Update or Bootloop from declining.
So now I don't know what to do, when it comes to the PG32IMG.zip file. I even just changed the Froyo PG32IMG.zip to a 2.3.3 Gingerbread PG32IMG.zip, so now I'm at the correct ROM for rooting. I changed it because I wasn't sure if being at Froyo was preventing me from doing all of this from the beginning, similar to how the most up to date update did as well.
But back to the PG32IMG.zip, what would be the best thing to do with this situation? Should I change it back to the CWM, and deal with the Android error, while still allowing me to get into FASTBOOT. Or should I just keep it as the GB 2.3.3, as it is now? Can I just delete the PG32IMG.zip file altogether, or is it absolutely necessary? It just keeps trying to update to what the file already is, and prevents me from doing anything else.
I think I'm going to try the CWM.zip renamed to PG32IMG.zip and see if I can get it to work.
Cleanincubus said:
Yes it does recognize my phone. I think you're exactly right, in the direction you're showing me. I think flashing CWM is the key to getting this all to work.
But I'm getting some strange stuff happening. When I was finally able to select the Fastboot section, I had CWM saved as PG32IMG.zip. I started getting an error (black screen with a little center image of my phone, with a red "!" on it), after rebooting. I had to press Volume Up + Power, which brought me to some kind of Android settings (Wipe Cache, & something about clearing or wiping partition). I selected to just reboot, and the phone rebooted fine. I changed the PG32IMG.zip file back to the Froyo, and I can no longer get past the "Recovery" and forcing to do the Update or Bootloop from declining.
So now I don't know what to do, when it comes to the PG32IMG.zip file. I even just changed the Froyo PG32IMG.zip to a 2.3.3 Gingerbread PG32IMG.zip, so now I'm at the correct ROM for rooting. I changed it because I wasn't sure if being at Froyo was preventing me from doing all of this from the beginning, similar to how the most up to date update did as well.
But back to the PG32IMG.zip, what would be the best thing to do with this situation? Should I change it back to the CWM, and deal with the Android error, while still allowing me to get into FASTBOOT. Or should I just keep it as the GB 2.3.3, as it is now? Can I just delete the PG32IMG.zip file altogether, or is it absolutely necessary? It just keeps trying to update to what the file already is, and prevents me from doing anything else.
I think I'm going to try the CWM.zip renamed to PG32IMG.zip and see if I can get it to work.
Click to expand...
Click to collapse
You shouldn't be flashing romantic zips as PG32IMG. That's what clockwork is for. If get it back to froyo, then go to the HTC recovery and follow the clockwork instructions I linked to. But maybe someone more knowledgeable than I can answer better.
Sent from my ADR6350 using xda app-developers app
After you go onto bootloader and it flashes your IMG you either rename the file on your SD card or delete it from your SD card. You will be able to proceed after that has been done
sent from my incredibly paranoid inc2
---------- Post added at 07:00 PM ---------- Previous post was at 06:58 PM ----------
Your s-off so the hard part is done.
sent from my incredibly paranoid inc2
You're right. The PG32IMG.zip was a problem. I removed them from the SD card's root, and it's working as it should.
Now the issue is the instructions in that link. I can't find any update.zip for the phone anywhere. I also can't find any options in the Recovery for "re-install package". I go to "BOOTLOADER" and then "RECOVERY". The Phone then boots to a small image of my phone with a red "!". I press Volume Up + Power button, and it loads the "Android system recovery <3e>". I have a Yellow error at the bottom stating"
E:Can't open /cache/recovery/command
Click to expand...
Click to collapse
You need to flash a new recovery. Do you adb setup on your pc? If not, google it and get it setup.
Here is a link to CWM
http://goo.im/devs/aeroevan/cwm/recovery-clockwork-6.0.1.5-vivow.img
Save it to your adroid-tools folder
You will need to navigate to your anroid tools folder in cmd before issuing the commands below
Code:
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img
---------- Post added at 11:55 PM ---------- Previous post was at 11:44 PM ----------
FYI cmd needs to be run as administrator.
sjpritch25 said:
You need to flash a new recovery. Do you adb setup on your pc? If not, google it and get it setup.
Here is a link to CWM
http://goo.im/devs/aeroevan/cwm/recovery-clockwork-6.0.1.5-vivow.img
Save it to your adroid-tools folder
You will need to navigate to your anroid tools folder in cmd before issuing the commands below
Code:
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img
---------- Post added at 11:55 PM ---------- Previous post was at 11:44 PM ----------
FYI cmd needs to be run as administrator.
Click to expand...
Click to collapse
screenshot for you
The version I have has the correct files in the "platform-tools" folder.
I get an error with the "adb remount" command, saying "remount failed: Operation not permitted"
When I use the command "fastboot devices", my phone doesn't show up, and it just skips to the next command line, showing nothing. My phone does say "FASTBOOT" though.
Then when I type "fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img" it just hangs at "< waiting for device >"
Maybe I didn't set it up the sdk stuff properly? I'll look more stuff up when I get home later tonight. But I figured, I'd at least post this up now, in case this is showing another issue.
Cleanincubus said:
The version I have has the correct files in the "platform-tools" folder.
I get an error with the "adb remount" command, saying "remount failed: Operation not permitted"
When I use the command "fastboot devices", my phone doesn't show up, and it just skips to the next command line, showing nothing. My phone does say "FASTBOOT" though.
Then when I type "fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img" it just hangs at "< waiting for device >"
Maybe I didn't set it up the sdk stuff properly? I'll look more stuff up when I get home later tonight. But I figured, I'd at least post this up now, in case this is showing another issue.
Click to expand...
Click to collapse
I don't think it's going to work until you get fastboot devices and adb devices to recognize your phone. I wish I could point you in the right direction, but I'm not very experienced with it.
I'm assuming you have the drivers for our phone installed? Some people have to reboot the pc to get those to recognize the device...
Yeah, I'm going to have to do some more digging. ADB device does recognize my phone, at the 6th line on the screen cap I posted. I've restarted the pc multiple times since first trying to get all of this to work.
Cleanincubus said:
Yeah, I'm going to have to do some more digging. ADB device does recognize my phone, at the 6th line on the screen cap I posted. I've restarted the pc multiple times since first trying to get all of this to work.
Click to expand...
Click to collapse
First of all make sure you have fastboot.exe in your tools folder
Code:
adb kill-server
adb start-server
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery***.img
Make sure you have the drivers and that you delete HTC sync from your computer. If you can get it to boot up into the phone make sure you have android debugging turned on.
sent from my incredibly paranoid inc2
sjpritch25 said:
First of all make sure you have fastboot.exe in your tools folder
Code:
adb kill-server
adb start-server
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery***.img
Click to expand...
Click to collapse
Yup, it's there.
Did those commands, and it ended in the same result. No errors or "waiting" messages at the flashboot devices command, but it didn't show my device either.
Jasonp0 said:
Make sure you have the drivers and that you delete HTC sync from your computer. If you can get it to boot up into the phone make sure you have android debugging turned on.
sent from my incredibly paranoid inc2
Click to expand...
Click to collapse
Definitely installed driver. I originally tried to install the driver I previously used with my original s-off/root/rom, but it didn't work with Windows 8 (previous PC was WinXP), so I found the correct one for my OS. The "adb devices" command never found my phone, before installing the current driver.
I never installed HTC Sync. Just double checked the "Uninstall or change program" in the Win8 control panel (previously "Add/Remove Programs") to make sure it didn't get installed with out my knowledge, and it's not in there.
If you mean on the phone: "Settings" > "Applications" > "Development" > check box for "USB debugging", then yes. If it's a command of some sort, then no & I don't know how to do it.
I'm also making sure to run these commands by right-clicking the Command Prompt and selecting "Run as administrator", before doing these commands.
Related
Hi XDA Community!
Completely bone-headed n00b here (is there any other kind)?
Firstly, a quick background:
HTC Desire, rooted, S-Off, 16 gig Class 4 SD card with 1 gb ext4 partition
I was flashed with a perfectly working Leedroid 2.2f rom, overkill backed up with Clockwork, AmonRa, Titanium, MyBackup Pro, complete SD card backup (you name it, I did it), then wiped and flashed ownhere's Rom because I was running out of app space. The flash was successful then I proceeded to backup ownhere's rom after re-installing all my apps and I think that's where the problem began. I began my first backup with Clockwork via Rom Manager, but was not getting any response, so I rebooted my phone into Clockwork Recovery and backed up ownhere's rom there. After that, I could not turn on my phone.
I'd appreciate if someone could point me in the right direction. As of right now, my phone goes into a vicious boot loop whenever I try to turn it on. I can still get into hboot by holding down the power button and volume down button and then get into Android system recovery (Amon Ra Recovery, build: RA-desire-v2.0.0) by selecting "recovery", but when I try to do a nandroid restore, the error message I get is:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:/nandroid/
I've googled many times and have attempted to follow the steps outlined by various tutorials with similar sounding problems, but unfortunately to no avail. I've tried formatting my SD card on my computer, re-partitioning the SD card on my phone (not sure if that was successful), wiping it, attempting to restore it, attempting to flash it, but I keep getting that same error message above in the end.
I certainly don't deserve it after what I've done, but any help would be greatly appreciated! Thanks for having the patience to read.
EDITED: Below are the steps I took to resolve the issue.
First and foremost, I'd like to point out that prior to encountering this problem (or any problem for that matter), I did a very thorough job of backing up my entire phone multiple times through various methods, but it turns out I only really needed a single nandroid backup and mariosraptor's help. Still, better safe than sorry, I say, which is ironic considering what I did to my phone. Ah well.
Anyway, after running into my problem as described in my OP (original post), the following steps were needed to restore functionality to the phone:
1) With the phone turned off, I booted it into Fastboot by either a) holding down volume rocker+power on button, then choosing "fastboot" or b) holding back button+power on button, which takes you straight into "fastboot".
2) Once in fastboot, I connected my phone to my computer via USB cable.
3) I'm not sure if I needed it running or not, but I then ran Android SDK (a program I used back when I first got my phone and was tinkering with rooting and forcing apps to install onto the SD card before I learned about SD card partitioning and AP2SD/AP2SD+ supported roms and now DATA2SD/DATA2EXT). This program can be downloaded here and an example of how it's used is here, but I'm assuming (I know I shouldn't assume, but I can only describe things I've done or have already done) anyone who as gotten this far already has this program and used it before, even with limited knowledge.
4) I then went into my Start Menu in Windows and ran command prompt. The simplest way to run command prompt, I find, is to type "cmd" into the run dialog, then enter.
5) Once command prompt popped up, I typed in cd\ to change the directory to C:\ and then entered in cd android-sdk-windows/tools to open the directory to c:\android-sdk-windows\tools (I just noticed that you enter in /backsplashes, but end up with \forwardslashes, weird!).
6) I then typed in the fastboot commands as outlined by mariosraptor, that is, I entered "fastboot oem enableqxdm 0" pressed enter, let it finish, then typed in "fastboot reboot" and enter. Wait for phone to reboot, could take a while.
I'm hoping for most people those are all the steps needed in order to restore the phone, but in my case, after entering "fastboot oem enableqxdm 0", I received an error saying: "The program can't start because AdbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem." I was about to re-install when mariosraptor provided me with the AdbWinApi.dll file here. This is rapidshare link so it will expire. My suggestion is to search for it somewhere (google) if you run into the same missing file as me.
My problem actually didn't stop there either. I found my phone was stuck on the boot animation, although I supposed I could've left it even longer just to make sure it wasn't working, but I actually took my battery out to shut the phone down. I then proceeded to do a nandroid restore to a previous backup I had done before I created this whole problem. I did that by booting the phone into recovery by holding down volume rocker+power button, selecting "recovery", then selecting "nandroid backup/restore" and letting the process go through fully, which took quite some time.
Anyway, it's been a long 20 or so hours for me. I'm going to go rest now. Props again to mariosraptor!
in fastboot mode through adb cmd
fastboot oem enableqxdm 0
fastboot reboot
as long as you are S-off you can use fastboot commands and it is recommended that whatever you do from the moment that youre S-off'd you use fastboot and adb for various works on your Desire.
for more fastboot commands in adb just type fatboot
Hey mario, thanks for the quick reply.
I'm currently reading ADB for Dummies to figure out what you're talking about and will get back to you. I know I've used it before when I rooted my phone, but I was just following step-by-step instructions and had no idea what I was doing.
I recall seeing "unknown device" in device manager while my phone was plugged into my computer via USB during one of my recent attempts at fixing my current issue.
PS. I'm on Windows 7.
So I haven't been able to get far. I've noticed all the ADB commands that need to be entered in command prompt require me to have my phone in "USB debugging mode" by going into in Settings>Applications>Development, but I can't even turn on my phone to get there.
Am I missing something from your instructions? Sorry, my knowledge is quite limited.
When you are in Amonra, you are automaticly in "adb mode" so you can ignore that step. You should however install htc sync for the drivers needed.
turn off your phone by removing battery. press the back button+power on. you are in fastboot mode. the correct cmd's are fastboot commands.
like "fastboot reboot-bootloader" w/o the quotes.
ayato kamina said:
So I haven't been able to get far. I've noticed all the ADB commands that need to be entered in command prompt require me to have my phone in "USB debugging mode" by going into in Settings>Applications>Development, but I can't even turn on my phone to get there.
Am I missing something from your instructions? Sorry, my knowledge is quite limited.
Click to expand...
Click to collapse
Gotcha, I was able to get into "fastboot USB" by following your back button+power on (or down volume+power, then selecting fastboot) and connecting a USB cable to from the phone to my computer. I then went into command prompt (cmd) in the start menu. Typed in:
1) cd\
2) cd android-sdk-windows\tools
3) entered in "fastboot oem enableqxdm 0"
I then received the error message: The program can't start because AdbWinApi.dll is missing from you computer. Try reinstalling the program to fix this problem.
That will be my next step is to re-install Android SDK Windows.
Will report back, thanks!
Lennyz1988 said:
When you are in Amonra, you are automaticly in "adb mode" so you can ignore that step. You should however install htc sync for the drivers needed.
Click to expand...
Click to collapse
Thanks for pointing that out, Lenny. I didn't know that. I'm not sure if I have the HTC Sync drivers, but in fastboot mode (as instructed by mario), I checked device manager in properties of My Computer and the unknown device exclamation icon is gone. I see, ADB interface>HTC Bootloader.
http://rapidshare.com/files/380196682/AdbWinApi.dll
donload it from the link and put in tools foder of SDK
mariosraptor said:
http://rapidshare.com/files/380196682/AdbWinApi.dll
donload it from the link and put in tools foder of SDK
Click to expand...
Click to collapse
Phew! Thanks Mario! I was struggling to re-install Android SDK for some reason. A problem with Java SE JDK. *shrugs*
Will continue now....
i hope it helps. i will see more tomorrow. good luck!!!
ayato kamina said:
Phew! Thanks Mario! I was struggling to re-install Android SDK for some reason. A problem with Java SE JDK. *shrugs*
Will continue now....
Click to expand...
Click to collapse
PROGRESS!!
So I'm finally passed the S-off splash screen and am waiting on the boot animation screen. I expect there to be a problem because I've been formatting and partitioning my SD card so much, the card itself may actually be empty at the moment (not sure). I will wait for while and if nothing changes, I'm going to restore my SD card and try again.
Thanks for getting me this far so far, Mario! Much appreciated!
just let see what happens and hopefully it will work again.
ayato kamina said:
PROGRESS!!
So I'm finally passed the S-off splash screen and am waiting on the boot animation screen. I expect there to be a problem because I've been formatting and partitioning my SD card so much, the card itself may actually be empty at the moment (not sure). I will wait for while and if nothing changes, I'm going to restore my SD card and try again.
Thanks for getting me this far so far, Mario! Much appreciated!
Click to expand...
Click to collapse
mariosraptor said:
in fastboot mode through adb cmd
fastboot oem enableqxdm 0
fastboot reboot
as long as you are S-off you can use fastboot commands and it is recommended that whatever you do from the moment that youre S-off'd you use fastboot and adb for various works on your Desire.
for more fastboot commands in adb just type fatboot
Click to expand...
Click to collapse
my phone is connected,drivers are installed and it is available in fastboot. But when I am typing "fastboot oem enableqxdm 0" it returnes: "... FAILED (status malformed (1 bytes))" and nothing happens.
could u help pleas?
mariosraptor said:
just let see what happens and hopefully it will work again.
Click to expand...
Click to collapse
YES! I can finally turn on my phone again! Thanks so much, Mario! You are a genius and thank you for being so patient with me.
This is what happened:
I waited a while and the phone remained stuck on the boot animation so I took the battery out and completely restored all my files onto my partitioned SD card. I tried booting again with similar results so I tried running a nandroid restore to a previous Leedroid rom from Amon Ra Recovery and no longer received the cannot mount message so the restore was finally able to execute and after a lengthy boot process, I'm up and running again!
Thanks again so much! Once more, I could not have done it without your help. I'm going to see how stable it is, but it looks very good. By tomorrow if I'm still up, I will re-edit my first post with the exact steps I took to remedy my particular problem.
May I have your paypal email address?
persianblue said:
my phone is connected,drivers are installed and it is available in fastboot. But when I am typing "fastboot oem enableqxdm 0" it returnes: "... FAILED (status malformed (1 bytes))" and nothing happens.
could u help pleas?
Click to expand...
Click to collapse
Sorry to hear that, persianblue. In light of your problem, I will write the solution right now, although it sounds like a you're getting a different error message than I did after entering the fastboot command. Regardless, I will post the step-by-step instructions because there's no guarantee you did exactly what I did to recover my phone.
I'll have it up shortly.
SOLUTION
copied and pasted from the first post:
Below are the steps I took to resolve the issue.
First and foremost, I'd like to point out that prior to encountering this problem (or any problem for that matter), I did a very thorough job of backing up my entire phone multiple times through various methods, but it turns out I only really needed a single nandroid backup and mariosraptor's help. Still, better safe than sorry, I say, which is ironic considering what I did to my phone. Ah well.
Anyway, after running into my problem as described in my OP (original post), the following steps were needed to restore functionality to the phone:
1) With the phone turned off, I booted it into Fastboot by either a) holding down volume rocker+power on button, then choosing "fastboot" or b) holding back button+power on button, which takes you straight into "fastboot".
2) Once in fastboot, I connected my phone to my computer via USB cable.
3) I'm not sure if I needed it running or not, but I then ran Android SDK (a program I used back when I first got my phone and was tinkering with rooting and forcing apps to install onto the SD card before I learned about SD card partitioning and AP2SD/AP2SD+ supported roms and now DATA2SD/DATA2EXT). This program can be downloaded here and an example of how it's used is here, but I'm assuming (I know I shouldn't assume, but I can only describe things I've done or have already done) anyone who as gotten this far already has this program and used it before, even with limited knowledge.
4) I then went into my Start Menu in Windows and ran command prompt. The simplest way to run command prompt, I find, is to type "cmd" into the run dialog, then enter.
5) Once command prompt popped up, I typed in cd\ to change the directory to C:\ and then entered in cd android-sdk-windows/tools to open the directory to c:\android-sdk-windows\tools (I just noticed that you enter in /backsplashes, but end up with \forwardslashes, weird!).
6) I then typed in the fastboot commands as outlined by mariosraptor, that is, I entered "fastboot oem enableqxdm 0" pressed enter, let it finish, then typed in "fastboot reboot" and enter. Wait for phone to reboot, could take a while.
I'm hoping for most people those are all the steps needed in order to restore the phone, but in my case, after entering "fastboot oem enableqxdm 0", I received an error saying: "The program can't start because AdbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem." I was about to re-install when mariosraptor provided me with the AdbWinApi.dll file here. This is rapidshare link so it will expire. My suggestion is to search for it somewhere (google) if you run into the same missing file as me.
My problem actually didn't stop there either. I found my phone was stuck on the boot animation, although I supposed I could've left it even longer just to make sure it wasn't working, but I actually took my battery out to shut the phone down. I then proceeded to do a nandroid restore to a previous backup I had done before I created this whole problem. I did that by booting the phone into recovery by holding down volume rocker+power button, selecting "recovery", then selecting "nandroid backup/restore" and letting the process go through fully, which took quite some time.
Anyway, it's been a long 20 or so hours for me. I'm going to go rest now. Props again to mariosraptor!
Click to expand...
Click to collapse
Congrats mate. nice to hear that you are up and running again. this is what the community does. Help each other!!!
mariosraptor said:
Congrats mate. nice to hear that you are up and running again. this is what the community does. Help each other!!!
Click to expand...
Click to collapse
Absolutely! I'm discovering that firsthand thanks to you. Again, I appreciate your help. I had spent soooo much time trying to figure it out on my own and you were able to help me right away.
You sir, are a class act!
So it's been over a full day since my personal debacle and I'm happy to say my phone is still up and running . There has been, however, one abnormality. It's not a huge issue in the long run as I can still use the phone as I normally do, but I've noticed whenever I plug my micro-usb cable into my phone (with the other end either connected to a computer or a power outlet), there is a noticeable delay before it starts charge. Also, when connected to a computer, I'm no longer receiving the prompt for 1) charge only 2) mount sd card 3) sync 4) etc etc.
The icon in the top left that normally pops up doesn't show either when I have it connected to computer. Again, not a big deal in the long run, but obviously it can be a nuisance not being able to transfer files b/t my phone and computer via this method anymore. Not sure if anyone else has encountered this issue. I'm using the same cable, same computer. My next step is to try it on a diff computer, then eventually a different cable and hopefully that might be the issue.
Hello, I have like eight hours of continuous searching for solve this problem.
I installed like two months ago the Android Revolutionary HD 6.1.5 ROM, i did S-off, Radio-off, Root, etc, following the tutorials of XDA. But i installed the actualization of ARHD 6.2.0 and it works very nice but one day later when i was talking by the phone it stopped, then sense was not responding, and it finally restarted alone.
The big problem is it was only showing the HTC logo and then the screen puts black.
I get into HBoot and it searches for PD98IMG.zip
i putted the PD98IMG.zip in the card and it says this:
- Sd checking...
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nhb]
No image or wrong image!
Loading...[PD98img.zip]
I say yes and it shows:
- Image unzipping fail!
Update Fail!
Press <POWER> to reboot
I tried a lot of RUU`s, like 13 and i can´t find one who works, the only who was acepted was ono withe the recovery only. With USB it does not work either.
I sent it to the company who sold me it and they have no idea about...
I hope you can help me, i am a little dissapointed, because i tried all the RUU`s what i founded in the web.
Thank you very much, Freesoft.
Freesoft64 said:
Hello, I have like eight hours of continuous searching for solve this problem.
I installed like two months ago the Android Revolutionary HD 6.1.5 ROM, i did S-off, Radio-off, Root, etc, following the tutorials of XDA. But i installed the actualization of ARHD 6.2.0 and it works very nice but one day later when i was talking by the phone it stopped, then sense was not responding, and it finally restarted alone.
The big problem is it was only showing the HTC logo and then the screen puts black.
I get into HBoot and it searches for PD98IMG.zip
i putted the PD98IMG.zip in the card and it says this:
- Sd checking...
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nhb]
No image or wrong image!
Loading...[PD98img.zip]
I say yes and it shows:
- Image unzipping fail!
Update Fail!
Press <POWER> to reboot
I tried a lot of RUU`s, like 13 and i can´t find one who works, the only who was acepted was ono withe the recovery only. With USB it does not work either.
I sent it to the company who sold me it and they have no idea about...
I hope you can help me, i am a little dissapointed, because i tried all the RUU`s what i founded in the web.
Thank you very much, Freesoft.
Click to expand...
Click to collapse
Try to go into recovery mode. What exactly is the problem. If it is not booting in...go to recovery and select fix permissions... this will solve any problems. If not try to install a rom with full wipe and reboot. If you flash a PD98IMG.zip then once again you need to root, S OFF, etc etc....
Stop what you are doing before you brick your phone.
The PD98 error you are getting happens to all rooted DHD's, and is nothing to worry about (delete it from your sd card). RUU's are for stock devices, or for returning to stock.
Check to make sure you haven't screwed up your root access, and flash a ROM .zip file from the developers thread (in recovery, from your sd card). And always check the checksum before flashing.
Sent from The App that Time Forgot.
JagDave said:
Stop what you are doing before you brick your phone.
The PD98 error you are getting happens to all rooted DHD's, and is nothing to worry about (delete it from your sd card). RUU's are for stock devices, or for returning to stock.
Check to make sure you haven't screwed up your root access, and flash a ROM .zip file from the developers thread (in recovery, from your sd card). And always check the checksum before flashing.
Sent from The App that Time Forgot.
Click to expand...
Click to collapse
Well, actualy, i can`t get into Recovery, it reboots and the screen turns black, the only thing what the phone admits is PD98IMG.zip.
Thank you very much for responding!
Delete that file from your SD card, and check if you can get into recovery. If yes, download superWIPE for ARHD, and ARHD rom and install it ( it's different base i think, so you have to superWipe it )
PD98IMG.zip is the radio, if that's what you need they can all be found here:
http://forum.xda-developers.com/showthread.php?t=996630
Might be worth flashing the latest and seeing if your phone behaves enough afterwards to let you get into recovery.
I take it you are trying from bootloader?
Also does your computer recognize the phone on usb?
Sent from The App that Time Forgot.
Sounds to me your Recovery has an error.
Download and extract Android Flasher http://forum.xda-developers.com/showthread.php?t=794638
Boot into Bootloader & select fastboot
Use AndroidFlasher to install a new Recovery image.
Link to my copy of of the previous 4ext Touch recovery, so it should work.
Extract the image to wherever you extracted AndroidFlasher and make sure you select 'already in fastboot' prior to flashing.
Then you should be able to get into Recovery. Full wipe, install ROM, etc.
Hope this solves your problem.
JagDave said:
Sounds to me your Recovery has an error.
Download and extract Android Flasher http://forum.xda-developers.com/showthread.php?t=794638
Boot into Bootloader & select fastboot
Use AndroidFlasher to install a new Recovery image.
Link to my copy of of the previous 4ext Touch recovery, so it should work.
Extract the image to wherever you extracted AndroidFlasher and make sure you select 'already in fastboot' prior to flashing.
Then you should be able to get into Recovery. Full wipe, install ROM, etc.
Hope this solves your problem.
Click to expand...
Click to collapse
I am trying all this and i think it will work, the problem is my phone is "SHIP S-OFF"
But i don`t know hot to change from Ship to ENG...
Thank you very much for the answer, from now in one week i think my DHD will work again
If memory serves, you only need Eng to change the radio.
But don't quote me on that
Sent from The App that Time Forgot.
I have tried this http://forum.xda-developers.com/showthread.php?t=1396253
The PD98IMG.zip worked, so i am glad my desire is not bricked yet.
I still not having access to recovery, my phone is SHIP S-OFF not ENG S-OFF and i can`t change the Recovery, i can`t install the SDK drivers for bootloader.
I tried too with Android Flasher, and there doesn`t work because my phone is not ENG S-OFF.
My questions are this: how i can change now to ENG S-OFF?
What else i can do for revive the Desire HD?
Thank a lot for responding this post, i don`t know what i`ll do without all of you!
Personally I see no reason to Eng soff. You can still flash radios and recoveries with just regular soff. Just its done in a different way.
In that thread you posted their is a link for cwr in a pd98img. Just follow the directions I wrote.(its the first section)
But if you are set on getting Eng soff in the dev section you can use jkoljo tool.
Your second question confuses me. You said your phone is now working so what do you mean by reviving your phone?
Well, i tried ADB, the problem now is when i installed the drivers, in the command prompt i cant find my phone.
I was trying with this:
C:\adb devices
List of devices attached
In Device Manager it appairs like: Android Phone>Android ADB Interface
What i can do now?
I know I'm a little annoying, but I will really appreciate your help if we make it work!
Anyone can help with ADB with desire hd?
Well to be able to use command prompt on your computers first off would be to add the adb path which is normally C:\Program Files (x86)\Android\android-sdk\platform-tools or in C:\Program Files (x86)\Android\android-sdk\tools
Then you'll be able to use adb commands.
if not while in command prompt, just use the cd command to get in that directory so you can use the adb.exe
per exemple;
cd C:\Program Files (x86)\Android\android-sdk\tools
then you'll be able to use commands has
adb push [the file which should be in the same place] /data/local/tmp
Then if you just want to run command on your cell interface just write
adb shell
if you're in root you should start to write beside a #
it would look
<C:\[path]>adb shell
# [here you'll run command on your cellphone]
because if you run in command prompt right away
<C:\>adb device
without having the file to get the adb.exe
But as for using adb shell, if your device is connected and activated in debugged mode you'll be fine.
earthbrother said:
Well to be able to use command prompt on your computers first off would be to add the adb path which is normally C:\Program Files (x86)\Android\android-sdk\platform-tools or in C:\Program Files (x86)\Android\android-sdk\tools
Then you'll be able to use adb commands.
if not while in command prompt, just use the cd command to get in that directory so you can use the adb.exe
per exemple;
cd C:\Program Files (x86)\Android\android-sdk\tools
then you'll be able to use commands has
adb push [the file which should be in the same place] /data/local/tmp
Then if you just want to run command on your cell interface just write
adb shell
if you're in root you should start to write beside a #
it would look
<C:\[path]>adb shell
# [here you'll run command on your cellphone]
because if you run in command prompt right away
<C:\>adb device
without having the file to get the adb.exe
But as for using adb shell, if your device is connected and activated in debugged mode you'll be fine.
Click to expand...
Click to collapse
I did that, it doesn`t work because it says "error: device not found" i tried reinstalling many times the ADB drivers and another few with the path file, no results. With "adb devices" it says "list of devices attached" then, nothing.
I am really gratefull with all your answers, i hope we can made it work
I have a question more, it`s posible to put it in "debugging mode" from HBOOT?
Thanks a lot!
So, nobody can help me? that who help me will be rewarded!
You said only the recovery pd98 works. Reflash it. After it reboot and hangs take out battery and SD card. Reinsert battery and enter boot. Wait for it to scan, then reinsert sdcard and enter recovery. Wipe and reflash a rom or backup
Edit - still confused, from your pm you suggested that your dhd doesn't work? I need a simple yes it boots or doesn't, before we can go anywhere
Sent from my Desire HD using XDA App
I don't know what exactly happened. Today I wanted to upgrade my HOX to JB coming from AOKP to OrDroid. So, I followed the instructions and relocked my bootloader while on fastboot, then it went downhill from there. Phone automatically rebooted into HBOOT and it said that my bootloader was re-locked and below it "Security Warning". Everytime I reboot it always takes me to Fastboot. The weird thing is whenever I try to flash something in fastboot mode the CMD Window just says "Waiting for Device". When I check my phone, I can not move the volume rocker up and down in Fastboot mode while having my phone connected to my PC, but when I disconnect the USB plug, I can move it up and down. When I try to go through the RUU process, it says ERROR 170 and can't find my phone. I am lost as what to do, since I don't know how to get Fastboot to work properly and out of ideas. Please help. Thank you.
http://forum.xda-developers.com/showthread.php?t=1920060
follow this guide to help you its fantastic
I had the same problem when I first tried to flash leedroid 10.4.5. Try installing DroidExplorer.
Worked great for me! let me know if it worked for you:good:
You need to add the ADB paths to your actual windows path.
Right click "Computer" click "Properties" then Click "Advanced System Properties" then go to Envioronment variables and add the paths to adb folders into that, using a ";" to separate each path.
Hope that makes sense, a little hard to textually explain
kotaro_14 said:
I don't know what exactly happened. Today I wanted to upgrade my HOX to JB coming from AOKP to OrDroid. So, I followed the instructions and relocked my bootloader while on fastboot, then it went downhill from there. Phone automatically rebooted into HBOOT and it said that my bootloader was re-locked and below it "Security Warning". Everytime I reboot it always takes me to Fastboot. The weird thing is whenever I try to flash something in fastboot mode the CMD Window just says "Waiting for Device". When I check my phone, I can not move the volume rocker up and down in Fastboot mode while having my phone connected to my PC, but when I disconnect the USB plug, I can move it up and down. When I try to go through the RUU process, it says ERROR 170 and can't find my phone. I am lost as what to do, since I don't know how to get Fastboot to work properly and out of ideas. Please help. Thank you.
Click to expand...
Click to collapse
Unplug your phone
Turn off your phone
turn on your phone
choose fastboot
connect usb[
use fastboot commands /B]
(it's very important that you do it in this order because otherwise the bootloader will think your pc is a storage device and will lag because it will attempt to search for update.zip nowhere)
Use fastboot commands not adb (adb commands almost never work on bootloader)
If that still doesnt work then either the drivers aren't installed properly, otherwise you have to check with repair centers(i dont think its this one)
Hi all,
Been having problems with my DHD for ages now - got myself a GS3 after a while so had kind of given up on it but now I really want to get it back to life as a backup (and for a temp replacement for my gf who got her phone driven over yesterday!). I've seen loads of similar problems to mine, but after searching here for months and following several soutions to one point or another, I always seem to get some kind of error that no-one else is getting and from there it branches off into new problems/methods. Kind of getting sick of going in circles so here I am asking for some DHD justice!
The problem is this:
A few months back the DHD started freezing/restarting intermittently (something to do with Sense I think, but tried the goldcard method of rooting it a few weeks before which failed, not sure if this could have affected things but it didnt seem to have any noticable effect for a while anyway) then eventually got either stuck in a loop on the carriers logo animation or hanging at the white background/green HTC logo screen. Couldn't get any further. Did a factory reset but the problem persisted. After a few weeks I came back to it and found that very occasionally I could get the phone to start up and get on the home screen. I can do a few things (like enabling USB debugging luckily) there but get DOZENS of notifications that various processes are failing and eventually the phone reboots or jumps to the HTC logo screen again. Either this happens before I can do very much on the phone or some process fails and nothing happens. So really I need a solution thats mostly PC based - but pretty much every program or command line operation fails to actually see the phone. I'm assuming here what I need to do it flash a new ROM to replace what I also assume is a corrupt existing one? I've tried RUU .exe type fixes - which don't see the phone. Most of the command line instructions fail to see the phone either. The phone isn't rooted so I'm guessing this would need to be done to flash a new ROM (a working version of the stock one would be fine for what I need it for but having a custom one would be nice). I've got nowhere with trying to flash ROMs as is (not rooted, S-ON), and also nowhere with various root/s-off tools. TBH I'm not really sure which stage of the process I need to be trying first. The other day the phone suddenly booted ok without the notifications and worked for around 6 hours before something made it reboot and return to the boot loop.
On the HBOOT screen I have the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.28_M2
eMMC-boot
Trying to boot into recovery just gets me the red triangle screen. Trying a new image from SD doesnt work as it doesnt see the card mounted.
Thanks for taking the time to read my tale of woe. Anyone got an idea where to start with this?
MerkyBlud said:
Hi all,
Been having problems with my DHD for ages now - got myself a GS3 after a while so had kind of given up on it but now I really want to get it back to life as a backup (and for a temp replacement for my gf who got her phone driven over yesterday!). I've seen loads of similar problems to mine, but after searching here for months and following several soutions to one point or another, I always seem to get some kind of error that no-one else is getting and from there it branches off into new problems/methods. Kind of getting sick of going in circles so here I am asking for some DHD justice!
The problem is this:
A few months back the DHD started freezing/restarting intermittently (something to do with Sense I think, but tried the goldcard method of rooting it a few weeks before which failed, not sure if this could have affected things but it didnt seem to have any noticable effect for a while anyway) then eventually got either stuck in a loop on the carriers logo animation or hanging at the white background/green HTC logo screen. Couldn't get any further. Did a factory reset but the problem persisted. After a few weeks I came back to it and found that very occasionally I could get the phone to start up and get on the home screen. I can do a few things (like enabling USB debugging luckily) there but get DOZENS of notifications that various processes are failing and eventually the phone reboots or jumps to the HTC logo screen again. Either this happens before I can do very much on the phone or some process fails and nothing happens. So really I need a solution thats mostly PC based - but pretty much every program or command line operation fails to actually see the phone. I'm assuming here what I need to do it flash a new ROM to replace what I also assume is a corrupt existing one? I've tried RUU .exe type fixes - which don't see the phone. Most of the command line instructions fail to see the phone either. The phone isn't rooted so I'm guessing this would need to be done to flash a new ROM (a working version of the stock one would be fine for what I need it for but having a custom one would be nice). I've got nowhere with trying to flash ROMs as is (not rooted, S-ON), and also nowhere with various root/s-off tools. TBH I'm not really sure which stage of the process I need to be trying first. The other day the phone suddenly booted ok without the notifications and worked for around 6 hours before something made it reboot and return to the boot loop.
On the HBOOT screen I have the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.28_M2
eMMC-boot
Trying to boot into recovery just gets me the red triangle screen. Trying a new image from SD doesnt work as it doesnt see the card mounted.
Thanks for taking the time to read my tale of woe. Anyone got an idea where to start with this?
Click to expand...
Click to collapse
1. S-off your device
2. Use android flasher
3. AND easily flash flash recovery thorough this software....
Sent from my HTC Desire HD using xda premium
MaratabHashmi said:
1. S-off your device
2. Use android flasher
3. AND easily flash flash recovery thorough this software....
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
S-off requires rooting it first, am I right? Not having much luck with that - HTC Quickroot claims its been done but none of the apps such as SuperUser are present when it reboots...
Suggestions anyone? efforts to S-OFF not working so far...:fingers-crossed:
You don't need to root if all you want to do is run a RUU. Are you trying to do it through ADB or fastboot? Is the RUU you're trying compatible with your phone's region?
bananagranola said:
You don't need to root if all you want to do is run a RUU. Are you trying to do it through ADB or fastboot? Is the RUU you're trying compatible with your phone's region?
Click to expand...
Click to collapse
I'm trying running the .exe file from the pc, I'm 99.9% sure its the correct region (3UK stock). It gets as far as bringing up a screen with a grey HTC logo while the PC says 'waiting for bootloader' before I get an error message saying the USB connection is lost (tried 3 different cables and there is no issue with faulty cables, or either end being unplugged, ). ADB doesnt see the phone as connected. Fastboot doesnt seem to do much as usually when the phone reboots as part of the process it freezes or goes back into bootloop. I've tried putting ROMs on the sd card and updating from the recovery menu but the phone doesnt see the card as mounted in this mode (when it does boot and run ok for a few minutes it does eventually see the card).
I'm confused. You have a recovery menu? Is your phone's bootloader unlocked?
Sorry, I mean the menu accessed through power on + vol down. No, tried unlocking it through the HTC site but no joy.
That's the bootloader. What procedure are you using for fastboot?
Via ADB commands - havent tried with fastboot methods recently though so I forget which particular guide I was using. I'm sure there are all kinds of noob alarms and flashing lights going off somewhere
You cannot run a RUU from adb. Only fastboot.
Where do I start with this then? I have the fastboot pc files installed already but didn't get anywhere, seem to remember the phone rebooting from a command and then just going back to the logo bootloop before it could progress - very possibly doing something wrong though.
Update: Tried the following:
Ran the RUU.exe until the wizard comes up. While the RUU wizard was open, found the temporary folder it created.Found ROM.zip. Opened it, extracted recovery.img. Put it in the location where Android SDK tools is installed. Booted the phone into bootloader, gone to FASTBOOT USB. Opened a command prompt, navigated to the folder with Android SDK tools. Entered:
fastboot flash recovery recovery.img
BUT still getting an error: "'fastboot' is not recognized as an internal or external command, operable program or batch file." :S
MerkyBlud said:
Where do I start with this then? I have the fastboot pc files installed already but didn't get anywhere, seem to remember the phone rebooting from a command and then just going back to the logo bootloop before it could progress - very possibly doing something wrong though.
Update: Tried the following:
Ran the RUU.exe until the wizard comes up. While the RUU wizard was open, found the temporary folder it created.Found ROM.zip. Opened it, extracted recovery.img. Put it in the location where Android SDK tools is installed. Booted the phone into bootloader, gone to FASTBOOT USB. Opened a command prompt, navigated to the folder with Android SDK tools. Entered:
fastboot flash recovery recovery.img
BUT still getting an error: "'fastboot' is not recognized as an internal or external command, operable program or batch file." :S
Click to expand...
Click to collapse
You need to change to the correct folder on your PC where your fastboot.exe file is, thats why your getting your error.
Why you trying to flash stock recovery? Unless I missed it, From what I can see on your posts your still s-on, so you can't flash anything like that from fastboot anyway.
Sent from my GT-I9505 using xda app-developers app
The error you're getting is that your computer can't find the fastboot file. It's not an error from fast out itself. Open the folder with fastboot in it, shift-rightclick, and choose "open command window here." Also, I thought you were running a RUU, not actually using fastboot to flash images. If you want to flash stuff you need to unlock bootloader.
bananagranola said:
The error you're getting is that your computer can't find the fastboot file. It's not an error from fast out itself. Open the folder with fastboot in it, shift-rightclick, and choose "open command window here." Also, I thought you were running a RUU, not actually using fastboot to flash images. If you want to flash stuff you need to unlock bootloader.
Click to expand...
Click to collapse
Yeah, I was initially trying to run the RUU.exe but that method wasn't working as I mentioned, so I tried extracting the rom it created and flashing that via fastboot.(Didn't know that shift/rightclick thing, thanks). As for s-off I haven't found a way of doing that without rooting, hence why I thought I couldn't get anywhere without rooting the phone first.
When I try and unlock the bootloader ( at http://www.htcdev.com/bootloader/ruu-downloads) , it wants to update the HBOOT first, this is how far I get with the process:
"BEFORE beginning the Unlock Bootloader process your product requires that you update the ROM to the version listed in the table below first, then download the RUU next to it to enable the unlocking capability.
To install the RUU, simply follow these instructions:
On your phone, enable USB debugging. (From the Home screen, MENU > Settings > Applications > Development > Check USB debugging)
Connect your phone to the computer using the USB cable that came with your phone. Wait a moment for your computer to identify your phone, this may take a few minutes. After your computer has found your phone, double click on the RUU to start the process"
I get as far as bringing up a screen with a grey HTC logo while the PC says 'waiting for bootloader' before I get an error message saying the USB connection is lost (so exactly the same problem trying to update the HBOOT as trying to run the RUU.exe) so I'm not sure how I'm going to unlock the bootloader if this method isn't working - direct .exe method doesnt work, and the process I need to unlock the bootloader so I can flash via fastboot doesnt work for the same reason.
Have you tried booting into bootloader and choosing fastboot before trying the RUU?
Yep. Same USB connection error despite having 'FASTBOOT USB' showing....
Type "fastboot devices." What does it say? Do you have your drivers from HTC Sync installed?
Hi all, had the phone working ok for a while, it wanted to do a software update which froze at 12%, however after cancelling it the phone seems to be problem free. Dont really get this as surely the incomplete update wouldnt take..? but something must have changed. The phones been ok for over a week now although I havent rebooted it or let the battery run flat...still dont trust it entirely!
Hey there
I want to start off by saying I have very little experience with rooting, but am very familiar with jailbreaking apple devices so I figured i could manage.
I have a htc one m8 on rogers network locked. I rooted it and had super user and all that jazz, then flashed AOKP. Then I thought i actually liked the stock HTC sense better, so I tried to "get things back to normal"...lol.
Now im at the point where if i turn my phone on it goes straight to the fastboot screen(?) with all the "fast boot, recovery, factory reset, etc". Since I'm super new to all of this is there anybody that can write some instructions on how to get my phone back to stock? I would really appreciate it after panicking over this for 3 days.
Edit: In the fastboot screen at the top it says ***Tampered*** ***Relocked*** ***security warning**
also when i try to press recovery it shows the htc screen for 1 second then back to the same menu
i found this http://forum.xda-developers.com/showthread.php?t=2710735 but i cannot even get into recovery
haydenrbm said:
Hey there
I want to start off by saying I have very little experience with rooting, but am very familiar with jailbreaking apple devices so I figured i could manage.
I have a htc one m8 on rogers network locked. I rooted it and had super user and all that jazz, then flashed AOKP. Then I thought i actually liked the stock HTC sense better, so I tried to "get things back to normal"...lol.
Now im at the point where if i turn my phone on it goes straight to the fastboot screen(?) with all the "fast boot, recovery, factory reset, etc". Since I'm super new to all of this is there anybody that can write some instructions on how to get my phone back to stock? I would really appreciate it after panicking over this for 3 days.
Click to expand...
Click to collapse
While being an expert with rooting and flashing custom recoveries on Samsung devices, I am also new to the world of HTC. Out of curiosity, what happens when you hit factory reset?
Unlock the boot loader again then install twrp recovery then head over to the stock backup thread and flash one of the nandroids for your cid.
MattMJB0188 said:
While being an expert with rooting and flashing custom recoveries on Samsung devices, I am also new to the world of HTC. Out of curiosity, what happens when you hit factory reset?
Click to expand...
Click to collapse
When i hit factory reset it the screen changes to the HTC in green for 1 second then back to where i started
ashyx said:
Unlock the boot loader again then install twrp recovery then head over to the stock backup thread and flash one of the nandroids for your cid.
Click to expand...
Click to collapse
I would...but when im trying to use ADB devices it isn't found
haydenrbm said:
When i hit factory reset it the screen changes to the HTC in green for 1 second then back to where i started
I would...but when im trying to use ADB devices it isn't found
Click to expand...
Click to collapse
Do fastboot devices ... adb commands itself won't work in bootloader, it has to be fastboot commands.
now you have a locked bootloader which means you cant do anything.. so your first step is to unlock it again then flash a custom recovery (TWRP) after that flash the stock rom+ boot.img ( to be safe) make sure it boots. RELOCK the bootloader then flash your firmware.zip.. hope it helps
mushages said:
now you have a locked bootloader which means you cant do anything.. so your first step is to unlock it again then flash a custom recovery (TWRP) after that flash the stock rom+ boot.img ( to be safe) make sure it boots. RELOCK the bootloader then flash your firmware.zip.. hope it helps
Click to expand...
Click to collapse
How can I unlock the bootloader again without the device showing in adb?
haydenrbm said:
How can I unlock the bootloader again without the device showing in adb?
Click to expand...
Click to collapse
i think you have your unlock token. start from here
http://www.htcdev.com/bootloader/unlock-instructions/page-4/
haydenrbm said:
How can I unlock the bootloader again without the device showing in adb?
Click to expand...
Click to collapse
If it's in bootloader it should show in command prompt when you type fastboot devices after connecting it to PC. If it doesn't then there is a driver problem perhaps. Check to make sure you have HTC drivers installed, or reinstall them. Might as well make sure adb is up to date as well, can do that through the Android SDK Manager. Another possibility might be that the usb cable isn't working correctly, try another cable. Fact of the matter though is, if it's in bootloader and you connect it to the PC adb/fastboot SHOULD pick it up.
So check and fix those things. Also make sure you use the correct commands, in bootloader mode, it'll be fastboot commands, not "adb devices" but "fastboot devices" ... "fastboot reboot" etc etc. Also make sure you're running the commands from within the adb/fastboot folder path(just for in case yeah...)
mushages said:
i think you have your unlock token. start from here
Click to expand...
Click to collapse
Okay it is unlocked, but now it just stays on the AOKP boot screen
Thank you for the help btw, it must be very painful.
haydenrbm said:
Okay it is unlocked, but now it just stays on the AOKP boot screen
Thank you for the help btw, it must be very painful.
Click to expand...
Click to collapse
Press Volume UP + Power button, once the screen goes dead, press Volume DOWN + Power button to get back into bootloader. Then flash a custom recovery (Like TWRP) and start flashing the Stock nandroid backups, can be found from here Collection of Stock backups
BerndM14 said:
Press Volume UP + Power button, once the screen goes dead, press Volume DOWN + Power button to get back into bootloader. Then flash a custom recovery (Like TWRP) and start flashing the Stock nandroid backups, can be found from here Collection of Stock backups
Click to expand...
Click to collapse
Okay i have got into the bootloader now, thanks.
I cannot put the rom into the internal storage because my computer wont detect the phone
haydenrbm said:
Okay i have got into the bootloader now, thanks.
the adb devices will show it if i have it in recovery mode but not bootloader, why is that ?
Click to expand...
Click to collapse
You didn't read any of my posts about that, did you? lol
I already stated adb commands like "adb devices" "adb reboot" etc will NOT work in bootloader, it'll work in the system and yes, it'll work in recovery for sideloading etc, but NOT in bootloader. For bootloader you HAVE to use fastboot commands, "fastboot devices" "fastboot reboot" "fastboot oem lock" "fastboot oem get_identifier_token" "fastboot flash unlocktoken Unlock_code.bin" etc etc
BerndM14 said:
You didn't read any of my posts about that, did you? lol
I already stated adb commands like "adb devices" "adb reboot" etc will NOT work in bootloader, it'll work in the system and yes, it'll work in recovery for sideloading etc, but NOT in bootloader. For bootloader you HAVE to use fastboot commands, "fastboot devices" "fastboot reboot" "fastboot oem lock" "fastboot oem get_identifier_token" "fastboot flash unlocktoken Unlock_code.bin" etc etc
Click to expand...
Click to collapse
Sorry I skipped past your first response, that makes sense now.
So I need to put the rom on my internal storage then go into recovery and install the zip using TWRP..but when I plug my phone into the computer the internal storage wont show up.
I do have sync manager installed also, and it wont show up in that either
haydenrbm said:
Okay i have got into the bootloader now, thanks.
I cannot put the rom into the internal storage because my computer wont detect the phone
Click to expand...
Click to collapse
With that adb devices command again in bootloader? Did you flash TWRP yet? If so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload.
Place the ROM.zip file in your adb folder then:
Connect phone to PC, while still in recovery mode type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. Next type adb sideload name_of_zip.zip wait until fully finished.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ flash as per usual then.
Yet somehow I don't think you even need to go to these steps
BerndM14 said:
With that adb devices command again in bootloader? Did you flash TWRP yet? If so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload.
Place the ROM.zip file in your adb folder then:
Connect phone to PC, while still in recovery mode type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. Next type adb sideload name_of_zip.zip wait until fully finished, once done reboot back into recovery and flash rom.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ flash as per usual then.
Yet somehow I don't think you even need to go to these steps
Click to expand...
Click to collapse
haha..thank you for baby steps
The sideload completed and i rebooted then went back into recovery and install but there isn't a zip file anywhere
Edit: wow..some how i reset it and it turned on and got into the phone... and now it connects to the computer so i should be able to follow the other tutorial now...man you are a life saver thank you so much
haydenrbm said:
haha..thank you for baby steps
The sideload completed and i rebooted then went back into recovery and install but there isn't a zip file anywhere
Edit: wow..some how i reset it and it turned on and got into the phone... and now it connects to the computer so i should be able to follow the other tutorial now...man you are a life saver thank you so much
Click to expand...
Click to collapse
I made a small mistake with the sideload though, it actually installs automatically as such you don't have to go back into recovery to flash, as it did it already, sorry. Edited post to fix.
Well as long as you can get into phone now to copy the nandroid backup to the phone all should be in order, can flash back stock from the nandroid then.
Glad it worked out then.:good:
BerndM14 said:
I made a small mistake with the sideload though, it actually installs automatically as such you don't have to go back into recovery to flash, as it did it already, sorry. Edited post to fix.
Well as long as you can get into phone now to copy the nandroid backup to the phone all should be in order, can flash back stock from the nandroid then.
Glad it worked out then.:good:
Click to expand...
Click to collapse
Hello BerndM14, thank you for this baby steps. Mine m8 is a gpe version, it's 4.4.2 google rom, rooted, cwm recovery, s-on. I was trying to flash the full google 4.4.3 zip rom under recovery, however, after that, my m8 automaticlly enter recovery everytime reboot. And I can manually enter the bootloader, my pc can find the m8 both in recovery and bootloader. I searched this post, and do it accordingly, I download the gpe stock backup KOT49H.H16 - 1.16.1700.16 - CWM Philz touch and use adb sideload gpe3.zip to the cell phone sucessfully, then the recovery automaticlly starts installing rom, then, I got below message:
-- Erasing & formatting /system as ext4 (Unmounted system)
system partition formatted!
-- Mounting system partition for writing
Writing rom system to system partition
Rom system written successfully!
@symlinking and permissions
--Creating toolbox symlinks
--creating additional symlinks
Symlinks Set!
--installing busybox
Set_perm: some changes failed
E:Error in /tmp/update.zip
(status 7)
installation aborted.
Install from sideload complete.
then, I reboot it manually. problem still there, still enter the recovery automaticlly.
do you have any comments on this? please.
thanks,