Develop Bugs

how to RUU with new bootloader?

I have an incredible that bootloops at the white screen that was s-on that I got to repair. I tried to flash the gingerbread RUU through hboot and the exe and it still bootlooped. I saw that the official unlock method came out so I updated to the 1.02.0000 hboot and unlocked the phone. I flashed cwm through fastboot but the phone still bootloops. Since the official unlock doesn't allow all the fastboot commands, I can't completely wipe the system or flash different radios, hboot, NV etc. I think this phone is completely bricked unless I can find an RUU that will work with the 1.02.0000 hboot. Since you can't flash RUUs while the phone is unlocked, I have to relock and then I get the main version is older error.

Try flashing this one thru hboot. Its stock GB ruu modified for new hboot.
http://dinc.does-it.net/New_Hboot/StockGB/PB31IMG.zip
And also try this. Its cwm recovery updated for the new hboot.
http://dinc.does-it.net/New_Hboot/CWM_5.2.0.2/PB31IMG.zip

thanks for the files. The RUU reads but stops after parsing. The cwm file does flash correctly, but I still cannot access recovery. I think the partitions are corrupt on the internal memory and I can't ADB in to fix them without recovery. Sucks, I spent way too much time trying to fix this phone. Its perfect condition, but its not worth my time anymore. Hopefully I can resell it for what I paid.

these files need to be stickied somewhere. I searched for around 4 hours on how to root after htcdev unlock and finally found this

the modded RUU wont flash via a locked s-on hboot if its not signed by htc. simply pulling the hboot out wont trick the phone into flashing it,as it breaks the signiture.
if flashing it unlocked,the modified RUU is not working for 1 or both of these reasons:
1)the main version may be higher than that on the android info text doccument
2)you need to also pull splash.nb0 and radio out,as htcdev only lets you access boot/system/recovery.
check your main version number in fastboot with fastboot getvar all
make yourself up an "RUU" using only the system/boot/recovery images,and the Android info text document. if your mainversion is less than 4.08.605.2,then your good to go. just realize that this is going to change it to that. if your main version is higher,then youll have to edit the android info to reflect your current main version before zipping it back up with the images. flash it with bootloader unlocked.
if you can at least get a working custom recovery via htcdev(i use fastboot flash rather than PB31IMGs) then you can flash superuser,and mount data,and rewrite your misc image to downgrade.
we are working on downgrading an htcdev hboot to the .79 in this thread: http://androidforums.com/incredible-all-things-root/495687-htc-dev-unlock-problems.html
and the adb commands and such for rewriting the misc image are in this thread: http://androidforums.com/incredible-all-things-root/427344-how-root-2-3-4-downgrade-get-s-off.html (some specific comments on recovery/adb in post #865)
if you cant get a recovery to permanently flsh,try booting it into memory with unlocked hboot and
fastboot boot <recovery name>.img
unfortunately,ive learned alot about htcdevs limitations with my rezound. holler if i can be of further assistance

cmlusco said:
Try flashing this one thru hboot. Its stock GB ruu modified for new hboot.
http://dinc.does-it.net/New_Hboot/StockGB/PB31IMG.zip
And also try this. Its cwm recovery updated for the new hboot.
http://dinc.does-it.net/New_Hboot/CWM_5.2.0.2/PB31IMG.zip
Click to expand...
Click to collapse
Thanks, I did it with this file and it worked like a charm.
Thanks guys

Help! Dev edition going to gpe and back again!?

Listen guys, sorry I've screwed this up so badly. I got a developer edition from swappa, and it came rooted with the stock sense ui. It was rooted, twrp installed. S-on, NOT, s-off was enabled.
I switched to gpe edition seamlessly through twrp. Now, looking to go back to stock sense ui and cannot.
Here's what I've done attempting to go back.
Attempted RUU for developer edition software. No luck because of error in software, error 155.
Tried to flash the RUU zip and that too errored out on me.
I then figured it was because of S-on, so tried to figure that out... Unsuccessfully.
Then thought I needed stock recovery, flashed that with error and now stuck with no recovery at all. Fastboot flash recovery recovery. IMG didn't work. Yeah, so no recovery.
Then I thought RUU wouldn't work because I'm unlocked bootloader. So, I locked the boot loader via fastboot OEM lock.... Probably not good
Fastboot menu days tampered, relocked.
Oh, Wi-Fi doesn't work either.... I forgot to mention that before I attempted to flash a stock sense ROM with no root.
Sow now what? Any advice?

mcgrathpatj said:
Listen guys, sorry I've screwed this up so badly. I got a developer edition from swappa, and it came rooted with the stock sense ui. It was rooted, twrp installed. S-on, NOT, s-off was enabled.
I switched to gpe edition seamlessly through twrp. Now, looking to go back to stock sense ui and cannot.
Here's what I've done attempting to go back.
Attempted RUU for developer edition software. No luck because of error in software, error 155.
Tried to flash the RUU zip and that too errored out on me.
I then figured it was because of S-on, so tried to figure that out... Unsuccessfully.
Then thought I needed stock recovery, flashed that with error and now stuck with no recovery at all. Fastboot flash recovery recovery. IMG didn't work. Yeah, so no recovery.
Then I thought RUU wouldn't work because I'm unlocked bootloader. So, I locked the boot loader via fastboot OEM lock.... Probably not good
Fastboot menu days tampered, relocked.
Oh, Wi-Fi doesn't work either.... I forgot to mention that before I attempted to flash a stock sense ROM with no root.
Sow now what? Any advice?
Click to expand...
Click to collapse
The command is fastbooot flash recovery.img. No caps on the img and no space after the period, if that helps. Plus recovery only once, not twice.
You are placing the recovery.img into your fastboot folder, correct?
EDIT: fastboot oem unlock to unlock your bootloader again.

fastboot flash recovery xxxxxxx.img is the command i used. probably looked conufsing as i didn't use a proper variable for the image file but rather recovery.img

xunholyx said:
The command is fastbooot flash recovery.img. No caps on the img and no space after the period, if that helps. Plus recovery only once, not twice.
You are placing the recovery.img into your fastboot folder, correct?
EDIT: fastboot oem unlock to unlock your bootloader again.
Click to expand...
Click to collapse
It's fastboot flash recovery recovery.img
The first recovery tells the device the location to which you want to flash it, in this case "recovery" for the recovery partition and the second one is the file you wish to flash in this case "recovery.img".
---------- Post added at 07:26 PM ---------- Previous post was at 07:04 PM ----------
mcgrathpatj said:
fastboot flash recovery xxxxxxx.img is the command i used. probably looked conufsing as i didn't use a proper variable for the image file but rather recovery.img
Click to expand...
Click to collapse
Do you know what software version you were on?
Just try the Developer Edition RUU again. If you're S-ON which you are, then bootloader needs to be relocked. I can't think of a reason why it shouldn't work, even if recovery is gone it completely returns device to stock(Including recovery).
You don't have to do the CID/MID part seeing as you're S-ON and you need S-OFF to do that. I don't think you used the converted GPE but instead a GPE ROM

I donwloaded the RUU for the Develoer Edition and it errored out at 155. I must have tried this 5-6 times.
I think I finally figured this out, so it may be useful for someone else. Who knows.
1) I downloaded another users NANDROID backup from the Dev Edition from this thread: http://forum.xda-developers.com/showthread.php?t=2701376
2) I flashed TWRP, restored the NANDROID from the above thread using TWRP.
3) Then, I flashed the original STOCK corresponding recovery from the same thread.
4) I was able to reboot and wifi FINALLY worked properly on a sense rom. I downloaded the OTA and it updated successfully, upon reboot through, wifi was broken again.
5) Re-locked the bootloader via fastboot oem lock, then performed the RUU for the Dev Edition from this thread here: http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
The RUU just completed successfully, so I think I'm out of the woods. But man oh man that was painful.

[Q] Help Flashing Stock ROM onto Developer M8

Hey guys,
So I have a Developer Edition M8 (HBOOT- 3.19), and I went through multiple steps trying to get GPE onto it. Since I'm posting here, I screwed up along the way, and Google hasn't been to helpful. To put it simply, I do not have an OS on the phone right now, and need to flash stock back onto it, and am having trouble because TWRP recovery no longer wishes to run.
Here's what happened:
I was following an outdated guide to getting GPE (I didn't know it was outdated at the time) and it said to flash insertcoin in order to be able to use firewater to get S-Off. I flashed insertcoin, realized firewater was no longer supporeted, and felt like I had wasted a few hours. I then found sunshine and tried to use it, but insertcoin was not close enough to stock to be compatible, so I tried to flash a stock ROM I found on this thread here onto the phone. I am fairly certain I downloaded the correct file, as the HBOOT 3.19 leads to the 3.xx file, and my CIS is BS_US002, so I downloaded the 3.28 file available. I took the zip, placed it onto the phone, and wiped insertcoin, and tried to install the stock ROM. Well, it failed.
I went back to the drawing board, actually read the instructions, and did this: I placed the unpacked zip into the TWRP/Backups folder on the phone. I then used fastboot flash recovery FILE.IMG to flash boot.emmc.win from my computer to the phone. Now, when I try to go into recovery to wipe and recover, it no longer enters TWRP. It is stuck on the HTC screen.
What do I do from here? My main goal is just to get stock back onto the phone, and I hope I did not mess up the phone.
To put all phone info in one place:
HTC One M8 Developer Edition
HBOOT- 3.19
CID- BS_US002
Thank you!

rbalutiu said:
Hey guys,
So I have a Developer Edition M8 (HBOOT- 3.19), and I went through multiple steps trying to get GPE onto it. Since I'm posting here, I screwed up along the way, and Google hasn't been to helpful. To put it simply, I do not have an OS on the phone right now, and need to flash stock back onto it, and am having trouble because TWRP recovery no longer wishes to run.
Here's what happened:
I was following an outdated guide to getting GPE (I didn't know it was outdated at the time) and it said to flash insertcoin in order to be able to use firewater to get S-Off. I flashed insertcoin, realized firewater was no longer supporeted, and felt like I had wasted a few hours. I then found sunshine and tried to use it, but insertcoin was not close enough to stock to be compatible, so I tried to flash a stock ROM I found on this thread here onto the phone. I am fairly certain I downloaded the correct file, as the HBOOT 3.19 leads to the 3.xx file, and my CIS is BS_US002, so I downloaded the 3.28 file available. I took the zip, placed it onto the phone, and wiped insertcoin, and tried to install the stock ROM. Well, it failed.
I went back to the drawing board, actually read the instructions, and did this: I placed the unpacked zip into the TWRP/Backups folder on the phone. I then used fastboot flash recovery FILE.IMG to flash boot.emmc.win from my computer to the phone. Now, when I try to go into recovery to wipe and recover, it no longer enters TWRP. It is stuck on the HTC screen.
What do I do from here? My main goal is just to get stock back onto the phone, and I hope I did not mess up the phone.
To put all phone info in one place:
HTC One M8 Developer Edition
HBOOT- 3.19
CID- BS_US002
Thank you!
Click to expand...
Click to collapse
use this
http://dl3.htc.com/application/RUU_..._2G_20.63.4196.01_release_394319_signed_2.exe

clsA said:
use this
Click to expand...
Click to collapse
Just flash the exe onto the phone using the fastboot command? or is there something more to it?

rbalutiu said:
Just flash the exe onto the phone using the fastboot command? or is there something more to it?
Click to expand...
Click to collapse
it's a RUU just click it in windows
no flashing just put the phone in bootloader fastboot usb

clsA said:
it's a RUU just click it in windows
no flashing just put the phone in bootloader fastboot usb
Click to expand...
Click to collapse
I downloaded the RUU and tried running it: it gave me error code 155 and said that it cannot update the phone. Right below it also states to get the correct RUU and try again, although I think this is the right one.
Is there any way to troubleshoot this/fix this?

rbalutiu said:
I downloaded the RUU and tried running it: it gave me error code 155 and said that it cannot update the phone. Right below it also states to get the correct RUU and try again, although I think this is the right one.
Is there any way to troubleshoot this/fix this?
Click to expand...
Click to collapse
Flash this first
https://www.androidfilehost.com/?fid=95784891001612796
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then flash the RUU ...

clsA said:
Flash this first
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then flash the RUU ...
Click to expand...
Click to collapse
I put in both flash zip commands and both resulted in failures, stating "remote: 99 unknown fail". Was this intended or something went wrong?

rbalutiu said:
I put in both flash zip commands and both resulted in failures, stating "remote: 99 unknown fail". Was this intended or something went wrong?
Click to expand...
Click to collapse
I figured out the problem but still no solution: both of these require s-off. The bootloader is unlocked, but I currently have S-On. What can we do to either make it S-Off or put the stock ROM on the phone?

The ruu and Firmware works fine with s-on
post the command window output ..your doing something wrong

rbalutiu said:
I figured out the problem but still no solution: both of these require s-off. The bootloader is unlocked, but I currently have S-On. What can we do to either make it S-Off or put the stock ROM on the phone?
Click to expand...
Click to collapse
bootloader needs to be relocked when you are s-on, for ruu mode flashing (firmware.zip or full ruu)

nkk71 said:
bootloader needs to be relocked when you are s-on, for ruu mode flashing (firmware.zip or full ruu)
Click to expand...
Click to collapse
Thanks nkk71, but the Developer edition he has comes with the bootloader unlocked .. i never locked mine to flash the RUU ( I did s-off the phone so I'm not sure if it's needed or not)
OP: use fastboot oem lock to relock your bootloader and try the RUU again

clsA said:
Thanks nkk71, but the Developer edition he has comes with the bootloader unlocked .. i never locked mine to flash the RUU ( I did s-off the phone so I'm not sure if it's needed or not)
OP: use fastboot oem lock to relock your bootloader and try the RUU again
Click to expand...
Click to collapse
Yep, I know it's silly that the US Dev edition (bootloader unlocked by default), has to be relocked for RUU mode flash with S-ON... same thing on the M7

nkk71 said:
Yep, I know it's silly that the US Dev edition (bootloader unlocked by default), has to be relocked for RUU mode flash with S-ON... same thing on the M7
Click to expand...
Click to collapse
Progress made.
I locked bootloader, ran the RUU, got stock back onto there. Then unlocked again, rerooted, and got s-off. Now I'm trying to install the GE RUU as said by this site and its giving me something that says "FAILED <remote: 42 custom id check fail>" .
Just this one last step, what can I do to go around this and fix this?
Thank you both for your help so far!

rbalutiu said:
Progress made.
I locked bootloader, ran the RUU, got stock back onto there. Then unlocked again, rerooted, and got s-off. Now I'm trying to install the GE RUU as said by this site and its giving me something that says "FAILED <remote: 42 custom id check fail>" .
Just this one last step, what can I do to go around this and fix this?
Thank you both for your help so far!
Click to expand...
Click to collapse
you'll need to edit the android_info.txt to include your MID and CID
Should look like this
modelid: 0P6B12000
modelid: 0P6B17000
modelid: 0P6B1****
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: BS_US002
cidnum: GOOGL001
mainver: 3.11.1700.5
btype:0
aareport:1
hbootpreupdate:3
Click to expand...
Click to collapse
And you'll want these new files, not the old one's on that site
Lollipop > http://forum.xda-developers.com/showthread.php?t=2708589
and the older Build: 4.4.4 - 2.12.1700.1 about half way down the page here >> http://www.graffixnyc.com/m8.php

clsA said:
you'll need to edit the android_info.txt to include your MID and CID
Should look like this
And you'll want these new files, not the old one's on that site
Lollipop > http://forum.xda-developers.com/showthread.php?t=2708589
and the older Build: 4.4.4 - 2.12.1700.1 about half way down the page here >> http://www.graffixnyc.com/m8.php
Click to expand...
Click to collapse
Thanks so much! Got 5.0.1 running on the phone, thanks for all the help!

No recovery.... ?

Is it possible to have a working phone without a recovery installed ?
Unlocked bootloader, flashed twrp 3.0.1.0, phone wouldn't boot into recovery.
Relocked bootloader cause phone is s-on, ran 401 ruu but can't get into stock recovery but otherwise phone works ok
:banghead:

There is always a recovery installed. Either the stock one or the custom one. What does it do when you go to the recovery?

10rdan said:
Is it possible to have a working phone without a recovery installed ?
Unlocked bootloader, flashed twrp 3.0.1.0, phone wouldn't boot into recovery.
Relocked bootloader cause phone is s-on, ran 401 ruu but can't get into stock recovery but otherwise phone works ok
:banghead:
Click to expand...
Click to collapse
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.

jollywhitefoot said:
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
Click to expand...
Click to collapse
With s-on you need to relock the bootloader to use official signed ruu files. When he flashed the ruu he could be seeing the exclamation mark that is normal as a warning before entering the stock recovery for which you need to push a volume and power button combo (don't know them heads up)
A possibility is to clear the cache and try to enter again (as this was a thingy on older HTC devices) or indeed as suggested at least to use the latest twrp available

Mr Hofs said:
With s-on you need to relock the bootloader to use official signed ruu files. When he flashed the ruu he could be seeing the exclamation mark that is normal as a warning before entering the stock recovery for which you need to push a volume and power button combo (don't know them heads up)
A possibility is to clear the cache and try to enter again (as this was a thingy on older HTC devices) or indeed as suggested at least to use the latest twrp available
Click to expand...
Click to collapse
It doesn't get as far as red exclamation mark, that's what I was waiting for. I'll try the newer version of twrp tomorrow after I've unlocked bootloader again. Do you think the same unlock code will work again?

10rdan said:
It doesn't get as far as red exclamation mark, that's what I was waiting for. I'll try the newer version of twrp tomorrow after I've unlocked bootloader again. Do you think the same unlock code will work again?
Click to expand...
Click to collapse
Yes i think it does work again. But that's a try and find out. There is always the possibility i could be wrong.
Edit :
This is why i love s-off....no more relocking / unlocking the BL with also an increased chance of bricks. The BL isn't made to be relocked and unlocked over and over.

Mr Hofs said:
With s-on you need to relock the bootloader to use official signed ruu files.
Click to expand...
Click to collapse
Sorry, but I believe this is misinformation, possibly residual to older HTC devices. I've heard this going back to the M7.
You need to be s-off to flash in download mode, but s-on can flash signed firmware and ruu's in RUU mode. I'm s-off so I can't test at the moment, but I'm about 99% that my information is correct.
S-on, you can only flash same or newer, though. You can't flash older firmware.
See post 19 here:
http://forum.xda-developers.com/htc-10/how-to/unlocked-official-ruu-t3378540/page2
I'm 100% that you can flash signed firmware package in ruu mode with bootloader unlocked and s-on.

jollywhitefoot said:
Sorry, but I believe this is misinformation, possibly residual to older HTC devices. I've heard this going back to the M7.
You need to be s-off to flash in download mode, but s-on can flash signed firmware and ruu's in RUU mode. I'm s-off so I can't test at the moment, but I'm about 99% that my information is correct.
S-on, you can only flash same or newer, though. You can't flash older firmware.
See post 19 here:
http://forum.xda-developers.com/htc-10/how-to/unlocked-official-ruu-t3378540/page2
I'm 100% that you can flash signed firmware package in ruu mode with bootloader unlocked and s-on.
Click to expand...
Click to collapse
That's new to me. Hopefully it isn't just tied to the developers edition then.
Thanks for the information

Mr Hofs said:
This is why i love s-off....no more relocking / unlocking the BL with also an increased chance of bricks. The BL isn't made to be relocked and unlocked over and over.
Click to expand...
Click to collapse
I'll bare that in mind, will unlock tomorrow again and try newer twrp. Only reason I relocked was to run ruu to get phone running again.

jollywhitefoot said:
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
Click to expand...
Click to collapse
Where can I find 3.0.2.2, can only see 3.0.2.0 on twrp site?
Cheers
Edit.... Found it. ?

@jollywhitefoot
I've got stock recovery back on phone. Can you think of any reason, other than old version, as to why twrp wouldn't boot after flashing it ?
Will try again tomorrow.

10rdan said:
@jollywhitefoot
I've got stock recovery back on phone. Can you think of any reason, other than old version, as to why twrp wouldn't boot after flashing it ?
Will try again tomorrow.
Click to expand...
Click to collapse
I'm not exactly sure, but up until 3.0.2.2 Captain Throwback didn't even have the device and was working blind. I know he was trying different things to make it compatible with different variants, too, so in my mind that was a test build. I'm not sure why they have it on the downloads page. For me, I always download it from the download section of the twrp thread.

Request at&t 6.20.502.5 stock recovery.img

Hi i have s-on with unlocked bootloader iam trying to restore back to stock using this guide here https://forum.xda-developers.com/htc-one-m8/general/guide-restore-european-htc-one-m8-to-t3072235
But iam unable to find stock recovery.img for at&t in order to proceed, Can anyone help out?

To return to "full" stock, just relock the bootloader and flash the 6.20.502.5 RUU (will wipe all user data on the phone). I don't know why that guide is advising to flash the boot.img and recovery.img before flashing the RUU. It isn't necessary.

redpoint73 said:
To return to "full" stock, just relock the bootloader and flash the 6.20.502.5 RUU (will wipe all user data on the phone). I don't know why that guide is advising to flash the boot.img and recovery.img before flashing the RUU. It isn't necessary.
Click to expand...
Click to collapse
Will this work even though the device is s-on?

David_UK said:
Will this work even though the device is s-on?
Click to expand...
Click to collapse
Yes. RUU that is intended for your specific device version (AT&T) will work just fine with s-on. As long as it's equal or greater to version number on the phone (no "downgrading" by RUU is allowed with s-on).
S-off is only needed to run RUU for another version (need s-off to change CID, MID), or to run an older version RUU (downgrade).