Develop Bugs

[Q] Major issues re-rooting

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.

[Q] DHD woes

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!

No "Yes or No" page when Unlocking bootloader!

Hello,
I tried to unlock the bootloader of my HTC Desire 816 Dual SIM, but the last step does not occur; that is, the page that should appear on the phone's screen and ask me to choose Yes or No (the page you see in the first attachment below), does not appear on my screen.
1. What is wrong?
2. Please help me to unlock the bootloader.
(Some points about the conditions my phone is in:
1. does not boot normally,
2. boots directly into Fastboot page,
3. in fastboot page I can select and enter Hboot page,
4. in Hboot menu, when I select Recovery, or Factory Reset, it only returns to Fastboot page.
5. as the attachment shows, the OS- is blank)

If you connect your phone to pc and select Fastboot, is Fastboot usb written at the top? Does your pc recognize the phone?
Have you tried flashing your original RUU?
For flashing RUU bootloader won't need to be unlocked. Just place your RUU zip on sd-card and it should flash the file on its own.

nukaru said:
If you connect your phone to pc and select Fastboot, is Fastboot usb written at the top? Does your pc recognize the phone?
Have you tried flashing your original RUU?
For flashing RUU bootloader won't need to be unlocked. Just place your RUU zip on sd-card and it should flash the file on its own.
Click to expand...
Click to collapse
1. Yes FASTBOOT USB is written at the top
2. I have installed HTC Sync Manager; when I connect the phone, HTC Sync Manager starts but it says "no device connected". I think this is because the phone is not in normal mode but in fastboot mode.
3. I downloaded an "0P9CIMG_A5_DUG,... 2.34.401.2..." zip and put it in sdcard; it started to update but at the stage [1] BOOTLOADER, -FAIL-PU appeared and at the bottom of the page "Device halted due to Large Image". (see attachment)
Now I want to download "RUU_A5_DUG,... 2.34.401.1...exe" and I will try it. But before downloading, Let me ask the following question:
If 'adb devices' command won't work even if FASTBOOT USB is written on the phone, what does this mean?
(4. Please use "Reply" button in response to my post in order that I get a notification)

Dr.Ghobar said:
1. Yes FASTBOOT USB is written at the top
2. I have installed HTC Sync Manager; when I connect the phone, HTC Sync Manager starts but it says "no device connected". I think this is because the phone is not in normal mode but in fastboot mode.
3. I downloaded an "0P9CIMG_A5_DUG,... 2.34.401.2..." zip and put it in sdcard; it started to update but at the stage [1] BOOTLOADER, -FAIL-PU appeared and at the bottom of the page "Device halted due to Large Image". (see attachment)
Now I want to download "RUU_A5_DUG,... 2.34.401.1...exe" and I will try it. But before downloading, Let me ask the following question:
If 'adb devices' command won't work even if FASTBOOT USB is written on the phone, what does this mean?
(4. Please use "Reply" button in response to my post in order that I get a notification)
Click to expand...
Click to collapse
http://forum.gsmhosting.com/vbb/f485/htc-desire-816-official-stock-roms-always-updated-1948682/
Plz select another ruu from the link

If the command adb devices doesn't work, it's most likely not the snapdragon version. then the whole flashing process is completely different and most ruus you'll find won't work.

ajeshmanu said:
http://forum.gsmhosting.com/vbb/f485/htc-desire-816-official-stock-roms-always-updated-1948682/
Plz select another ruu from the link
Click to expand...
Click to collapse
I have seen the link you gave. it does not contain A5_DUG, 401. it only contains 1402.

nukaru said:
If the command adb devices doesn't work, it's most likely not the snapdragon version. then the whole flashing process is completely different and most ruus you'll find won't work.
Click to expand...
Click to collapse
My procssor kind is: Quad-core 1.6 GHz Cortex-A7
The picture of the result of "adb devices" command I have attached.
1. You said "whole flashing process is completely different".
How is the flashing process for non-snapdragon version?
2. You said "most ruus you'll find won't work".
a. Do you know why? b. What kind of RUU might work for non-snapdragon version?

Dr.Ghobar said:
My procssor kind is: Quad-core 1.6 GHz Cortex-A7
1. You said "whole flashing process is completely different".
How is the flashing process for non-snapdragon version?
2. You said "most ruus you'll find won't work".
a. Do you know why? b. What kind of RUU might work for non-snapdragon version?
Click to expand...
Click to collapse
Sorry, I've had issues with my own phone the last few days( bad flash) and have been working to get it back to normal.
1. If you had the Mediatek processor like the 816g you would have to use the MTK toolkit to flash roms to your phone. Your device has a Snapdragon processor so that's not an issue. Nukaru was just saying if your phone wasn't responding to fastboot command then it might not be a Snapdragon but it is so your fine there.
2. No RUU you find will work unless it is the "exact" file for your version. These are signed files from the phone carrier/manufacture and they check your bootloader for the CID/version ID before allowing any rom to flash. Also trying to flash an older version of your rom than the one that was previously on the phone won't work. You can only flash either the last firmware version(401.2) or a newer version if available.
Your problem is twofold. Your phone's firmware is not readily available on the net and your OS seems to be either missing or corrupted with an unlockable bootloader. Unless you can either find or get your phone's carrier to find and give you the stock firmware zip/RUU so that you can restore your rom things aren't looking good and I don't ever like saying that trust me. Contact your carrier and request access to a flashable zip/RUU of your current rom. You haven't modified or changed anything on your phone so what can it hurt to ask? That's the best advice I've got without being able to unlock your bootloader.

Can my phone's lacking a ROM be the cause of non-appearance of "Yes or No" page (described in original post)?

Okay, was saving this for last. Please only post yes or no answers.
1. Are you a 100% sure your phone wasn't tampered with? Was the sealing intakt when you bought it?
2. Have you ever send your device to HTC to get it repaired?
3. Have you tried flashing another RUU before the error first popped up?
4. Did your device lag after you updated to lollipop?
5. Was this (drained battery) the first reboot after OTA update?
6. Have you installed all drivers correctly? HTC, java and adb? If you're not sure, try installing them again. After that try adb command again.
6. In which region did you buy this phone? Is it an Indian dual SIM version?

Dr.Ghobar said:
Can my phone's lacking a ROM be the cause of non-appearance of "Yes or No" page (described in original post)?
Click to expand...
Click to collapse
Probably yes.

nukaru said:
Okay, was saving this for last. Please only post yes or no answers.
1. Are you a 100% sure your phone wasn't tampered with? Was the sealing intakt when you bought it?
2. Have you ever send your device to HTC to get it repaired?
3. Have you tried flashing another RUU before the error first popped up?
4. Did your device lag after you updated to lollipop?
5. Was this (drained battery) the first reboot after OTA update?
6. Have you installed all drivers correctly? HTC, java and adb? If you're not sure, try installing them again. After that try adb command again.
6. In which region did you buy this phone? Is it an Indian dual SIM version?
Click to expand...
Click to collapse
1. Yes. I am sure. because it was sealed.
2. Yes.
3. No. I have tried only one 0P9CIMG.zip and got "Device halted due to Large Image".
4. I am not sure. It worked a long time with 5.0.2 before the problem.
5. No.
6. java and adb are good. I have installed HTC Sync Manager successfully and when I connect the phone to PC, HTC Sync Manager starts but cannot recognize the device.
7 (actully). It has been bought from Iran. HTC middle east chat, told me that its Carrier is "Paratel FZE" which is in United Arab Emirates.

Is there a method(s) or tool(s) for unlocking HTC Desire 816 Dual SIM which has no need to agreement from the user?

Dr.Ghobar said:
Is there a method(s) or tool(s) for unlocking HTC Desire 816 Dual SIM which has no need to agreement from the user?
Click to expand...
Click to collapse
There's S off using the Sunshine app but you need to be rooted first and that means unlocking your bootloader thru HTCDEV first to root it then re locking your bootloader before running the Sunshine app which then unlocks it again. So basically the answer is no. Sorry.

1. Is it possible to flash bootloader?
2. My 0P9CIMG.zip fails at the stage "[1] BOOTLOADER". (look at attachment)
Why it stops at this particular stage?

Dr.Ghobar said:
1. Is it possible to flash bootloader?
2. My 0P9CIMG.zip fails at the stage "[1] BOOTLOADER". (look at attachment)
Why it stops at this particular stage?
Click to expand...
Click to collapse
1. Not unless your bootloader is first unlocked and the phone is rooted and you have the proper bootloader image to flash
2. Are you using an SD card that is formatted fat32( 32gb/64gb?) The larger 128gb cards are formatted exfat I believe. The file your trying to flash was never unzipped after download correct? If your transferring the file to your phone via your USB from your computer you might try using an SD card reader and remove your card and put it in the reader and transfer it from your computer to your card that way to ensure it got transferred ok(not corrupted in the MTP transfer.)

nukaru said:
Okay, was saving this for last. Please only post yes or no answers.
1. Are you a 100% sure your phone wasn't tampered with? Was the sealing intakt when you bought it?
2. Have you ever send your device to HTC to get it repaired?
3. Have you tried flashing another RUU before the error first popped up?
4. Did your device lag after you updated to lollipop?
5. Was this (drained battery) the first reboot after OTA update?
6. Have you installed all drivers correctly? HTC, java and adb? If you're not sure, try installing them again. After that try adb command again.
6. In which region did you buy this phone? Is it an Indian dual SIM version?
Click to expand...
Click to collapse
thoctor said:
1. Not unless your bootloader is first unlocked and the phone is rooted and you have the proper bootloader image to flash
2. Are you using an SD card that is formatted fat32( 32gb/64gb?) The larger 128gb cards are formatted exfat I believe. The file your trying to flash was never unzipped after download correct? If your transferring the file to your phone via your USB from your computer you might try using an SD card reader and remove your card and put it in the reader and transfer it from your computer to your card that way to ensure it got transferred ok(not corrupted in the MTP transfer.)
Click to expand...
Click to collapse
I think the bootloader of my device is ill or damaged, because rom zips or ruu.exe's stop just at bootloader stage.
How can I fix bootloader?

Dr.Ghobar said:
I think the bootloader of my device is ill or damaged, because rom zips or ruu.exe's stop just at bootloader stage.
How can I fix bootloader?
Click to expand...
Click to collapse
It's probably not because you've had no access to it as it is still locked. Even if it was damaged it can't be flashed over unless its unlocked and you'd need the correct bootloader image and that might be hard to find. Might be getting close to the time to consider getting another phone as your operating system is gone or damaged and can't find the correct ffirmware to flash back.

thoctor said:
It's probably not because you've had no access to it as it is still locked. Even if it was damaged it can't be flashed over unless its unlocked and you'd need the correct bootloader image and that might be hard to find. Might be getting close to the time to consider getting another phone as your operating system is gone or damaged and can't find the correct ffirmware to flash back.
Click to expand...
Click to collapse
I have found the correct ruu.exe. The problem is that when the ruu.exe reaches the stage of "Rebooting to bootloader.........." (attachment 1) and sends the command to the phone, the phone is so slow in booting to bootloader that ruu.exe stops and says usb connection error.

I extracted rom.zip from ruu.exe.
Should I rename "rom.zip" to "0P9CIMG.zip" before putting it in sdcard?

M8 stuck in bootloader?

Hi,
my son's m8 just stopped working, came up with a screen saying something like "illegal use of software....."
It only boots to bootloader. Won't go into recovery, Factory recovery, I've tried a few things but things but fastboot commands won't recognize the phone. The phone does show "fast boot USB" but my PC doesn't seem to recognize the connection.
Phone is original software, locked, S-on, no mods. It does say on the screen "software modified"
Any way around this? I'll upload some screen pics.
Thanks for any advice
Marky_

Marky_ said:
Hi,
my son's m8 just stopped working, came up with a screen saying something like "illegal use of software....."
It only boots to bootloader. Won't go into recovery, Factory recovery, I've tried a few things but things but fastboot commands won't recognize the phone. The phone does show "fast boot USB" but my PC doesn't seem to recognize the connection.
Phone is original software, locked, S-on, no mods. It does say on the screen "software modified"
Any way around this? I'll upload some screen pics.
Thanks for any advice
Marky_
Click to expand...
Click to collapse
Run your device specific RUU via sd card method .
Hit THANKS if somebody help you

hi,
I have "Run your device specific RUU via sd card method . "
I have tried multiple RUU files for my device from a couple of different sources. none worked
see attached pics. fastboot, adb and htc_fastboot won't communicate with my phone either.
any other sources that anyone could recommend that may get this M8 booting again?
regards
Marky_

It's not easy to fix this kind of problem when the correct RUU version is not available and the bootloader is LOCKED
I suggest :
a) Not sure whether this will work as 6.24.841.1 firmware is partial update from 6.12.841.4 but worth a try.
Get the fw_6.24.841.1.zip from my thread : http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Since you said your PC is not communicating with your device (which I believe due to lack of HTC USB drivers - you can check in PC Device Manager to make sure), you can install it with microsd method
Rename the fw_6.24.841.1.zip to 0P6BIMG.zip (make sure your PC doesn't have windows extension hidden, it not it may read as 0P6BIMG.zip.zip and won't install)
Put in microsd and go to hboot to update, reboot and see whether it can boot now.
b) if the above fails, you need to try to unlock bootloader thru http://www.htcdev.com/
if it can be unlocked, install TWRP then restore the 6.24.841.1 backup that you can get from my thread linked in my signature.

ckpv5 said:
It's not easy to fix this kind of problem when the correct RUU version is not available and the bootloader is LOCKED
I suggest :
a) Not sure whether this will work as 6.24.841.1 firmware is partial update from 6.12.841.4 but worth a try.
Get the fw_6.24.841.1.zip from my thread : http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Since you said your PC is not communicating with your device (which I believe due to lack of HTC USB drivers - you can check in PC Device Manager to make sure), you can install it with microsd method
Rename the fw_6.24.841.1.zip to 0P6BIMG.zip (make sure your PC doesn't have windows extension hidden, it not it may read as 0P6BIMG.zip.zip and won't install)
Put in microsd and go to hboot to update, reboot and see whether it can boot now.
b) if the above fails, you need to try to unlock bootloader thru http://www.htcdev.com/
if it can be unlocked, install TWRP then restore the 6.24.841.1 backup that you can get from my thread linked in my signature.
Click to expand...
Click to collapse
Hi I am back.... doh.
After numerous attempts the above did finally work BUT the phone could not connect to internet or google playstore.
So, I tried the above FW method again, now it just keeps rebooting => HTC screen, optimizing apps then reboots
any other suggestions / links for me to try.
question..... what are the ****diag.zip & ****diag.nbh that HBOOT also looks for when booting to SDcard? Would one of these files be worth a try?
Thanks
Marky_

Marky_ said:
Hi I am back.... doh.
After numerous attempts the above did finally work BUT the phone could not connect to internet or google playstore.
So, I tried the above FW method again, now it just keeps rebooting => HTC screen, optimizing apps then reboots
any other suggestions / links for me to try.
question..... what are the ****diag.zip & ****diag.nbh that HBOOT also looks for when booting to SDcard? Would one of these files be worth a try?
Thanks
Marky_
Click to expand...
Click to collapse
I believe you do have hardware issue. Maybe corrupted data/emmc.
When it was working but no internet .. why didn't you try to unlock bootloader ? It's already out of warranty .. with bootloader unlock, you can try other thing like formatting data partition and restore a non-rooted stock nandroid.
Until now .. I never see a RUU been released for device version.

ckpv5 said:
I believe you do have hardware issue. Maybe corrupted data/emmc.
When it was working but no internet .. why didn't you try to unlock bootloader ? It's already out of warranty .. with bootloader unlock, you can try other thing like formatting data partition and restore a non-rooted stock nandroid.
Until now .. I never see a RUU been released for device version.
Click to expand...
Click to collapse
Hi, I did try to unlock bootloader, when I got the m8 working. yes it is out of warranty
I re-downloaded all files to my PC as HTC Dev asked but the fastbboot service could not recognize the phone. HTC sync was connecting and the phone was showing in my PC but the USB fastboot still would not let me :crying:
so..... without unlocking the bootloader, how do I "try formatting data partition and restore a non-rooted stock nandroid"
thank you

Marky_ said:
Hi, I did try to unlock bootloader, when I got the m8 working.......
I re-downloaded all files to my PC as HTC Dev asked but the fastbboot service could not recognize the phone. HTC sync was connecting and the phone was showing in my PC but the USB fastboot still would not let me :crying: .......
Click to expand...
Click to collapse
fastboot (( service )) only works in fastboot mode ( bootloader ) not while the device booting into android
Marky_ said:
........ without unlocking the bootloader, how do I "try formatting data partition and restore a non-rooted stock nandroid" .....
Click to expand...
Click to collapse
you can't
the only way is the RUU

No ADB, No bootloader, Recovery with no useful options and a new rom to install

Hello!
I work at a kind of phone repair store, and today I got somebody who asked me if I can remove the secure OS from their phone.
"This shouldn't be so hard, I guess..."
Well... I have no idea what to do right now. It's a phone of somebody from a company my boss works with. The phone is HTC One m8.
As the title says, I can't enable ADB since the phone is protected and they wanted to see if there was a way to enable it without going into the phone's settings. The bootloader also is turned off and I can't enable it because I can't enable ADB. The recovery doesn't give me too much help either. The only options there are Install (I have no idea what I could install with it since I always get the message saying Zip signature verification failed), I also have Wipe which I don't need to use at the moment, Settings that looks like it's broken... No settings to see there anyways. I don't even know why they added this since there are no settings in there. And I have Reboot.
It's my second day trying to install the stock rom.

Turn off phone, boot in hboot by pressing volume down and power, then select fastboot.
Open an adb window and do "fastboot getvar all" and post the result here(remove imei, sn)

HTC devices have a lot of nuance to them, and if you aren't specifically familiar, what you are trying to do is probably nearly impossible without specific guidance. For instance, the stock RUU (ROM update utility - probably what you are referring to "stock ROM") needs to match the device version (region/carrier). So as lucyr03 requested above, we need a lot more specific info about the device before we can advise further.
Also, what is the exact file name and source of the "stock ROM" you are trying to install? The error "Zip signature verification failed" usually means you are trying to flash an unofficial file (unsigned zip) which is not going to happen in the current condition.
---------- Post added at 09:09 AM ---------- Previous post was at 09:03 AM ----------
Potato626 said:
The bootloader also is turned off and I can't enable it because I can't enable ADB.
Click to expand...
Click to collapse
I don't know what you mean by this. There is no such thing as "turning off" the bootloader. No bootloader would mean the device is fully bricked, and the screen would not be coming on at all, which is not your situation.
The white screen which lets you go to recovery is the bootloader (also called hboot).
The recovery you describe is the stock recovery. It seems you are expecting a custom recovery, such as TWRP which has more options (such as to make ore restore nandroid backups, flash custom ROMs, etc.)? The stock recovery is what would be expected for a secure company phone.
It sounds like the secure functions are required by the customer's (phone user) company? Does the customer realize that modifying the phone will possibly/likely disable the ability for that person to access their company email, network, and other resources? May even cause them to lose their job. I want to be sure they actually understand and want to do this. Because modifying the phone is pretty involved. And no use in describing the whole process (and you performing it) if it isn't what the customer actually wants, or in their self interest.

lucyr03 said:
Turn off phone, boot in hboot by pressing volume down and power, then select fastboot.
Open an adb window and do "fastboot getvar all" and post the result here(remove imei, sn)
Click to expand...
Click to collapse
Adb command's are not working.

**Update**
The customer wanted his phone back. A huge thanks to everybody who wanted to help me!

Potato626 said:
Adb command's are not working.
Click to expand...
Click to collapse
adb commands don't work in fastboot mode. adb only works in OS or custom recovery, and USB debugging needs to enabled in phone settings.
Fastboot is related to adb, but has important differences. Fastboot command only work in fastboot mode, and debugging does not need to be enabled.
Also, I know it is a moot point (since you don't have the phone anymore), but for your future knowledge: if you a really wanted help with errors like this (adb not working), you need to be more specific and post more than one (vague) sentence. Describe the exact command used (you were told to use a fastboot command, not adb, for instance), and the resulting error messages, outputs, etc.
Always post as much specific and detailed information as possible, when asking for help. That should be the main takeaway here.