Database Develop

[Q] Revert to stock

Not sure if I am in the right place to ask this question, well, i'll ask anyway.
I unlocked my bootloader using Revolutionary. I now need to revert to stock for warranty. I downloaded the INDIA RUU from goo manager.
I managed to replace the Revolutionary HBOOT by changing mainver. However, my radio is not getting replaced, no matter what I try. As a result, my phone bootloops though the RUU install was successful. So I had to revert to Revolutionary by installing WWE ASIA RUU. This was successful because the Radios are the same ie 3805.04.03.27_M.
I am currently on
HBOOT - 6.13.1002
Radio-3805.04.03.27_M
How can I go back to HBOOT 1.13 and Radio 38.02.01.11_M?

HBOOT - 6.13.1002 is still Revolutionary HBOOT?
I think that this is the easiest way to get stock bootloader and rom back. You need to find the latest WWE ASIA RUU for that.
Is that this one: RUU_VIVO_SENSE30_S_hTC_Asia_WWE_3.09.707.1_Radio_20.4802.30.0822U_3822.10.08.28_M_release_226940_signed.exe ?
If you have the latest RUU succesfully installed including the HBOOT, you're OK.

Inferi0r said:
HBOOT - 6.13.1002 is still Revolutionary HBOOT?
I think that this is the easiest way to get stock bootloader and rom back. You need to find the latest WWE ASIA RUU for that.
Is that this one: RUU_VIVO_SENSE30_S_hTC_Asia_WWE_3.09.707.1_Radio_20.4802.30.0822U_3822.10.08.28_M_release_226940_signed.exe ?
If you have the latest RUU succesfully installed including the HBOOT, you're OK.
Click to expand...
Click to collapse
thanks for the reply...but i don't think i explained my problem properly.
I first downloaded PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip from Goo Manager. This is India RUU, but Froyo. This was what was installed on my phone first.
I first changed the mainver and renamed this RUU to PG32IMG.zip and let the bootloader install it. The HBOOT flashed perfectly, so my HBOOT became 1.09 but my radio was stuck at the same. This led the phone to bootloop because of incompatible radios.
So i tried extracting radio.img from PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip and renamed to PG32IMG.zip and bootloader flash it. But it does not flash. My question is how do I replace the current radio with 38.02.01.11_M? The current radio is 3805.04.03.27_M.

craynet said:
thanks for the reply...but i don't think i explained my problem properly.
I first downloaded PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip from Goo Manager. This is India RUU, but Froyo. This was what was installed on my phone first.
I first changed the mainver and renamed this RUU to PG32IMG.zip and let the bootloader install it. The HBOOT flashed perfectly, so my HBOOT became 1.09 but my radio was stuck at the same. This led the phone to bootloop because of incompatible radios.
So i tried extracting radio.img from PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip and renamed to PG32IMG.zip and bootloader flash it. But it does not flash. My question is how do I replace the current radio with 38.02.01.11_M? The current radio is 3805.04.03.27_M.
Click to expand...
Click to collapse
If you currently have a GB ROM on your phone you also have a GB radio. If you attempt to flash the Froyo RUU you have downloaded, you are going to brick your phone because you cannot flash an older Froyo radio over a GB radio. This is a sure way to brick your phone.

fastboot....

tpbklake said:
If you currently have a GB ROM on your phone you also have a GB radio. If you attempt to flash the Froyo RUU you have downloaded, you are going to brick your phone because you cannot flash an older Froyo radio over a GB radio. This is a sure way to brick your phone.
Click to expand...
Click to collapse
yeah, you are right...i now remember that this will brick my phone, a risk not worth taking.

just a quick question, my phone is factory unlocked (the user I bought if from bought it on amazon.de) and currently I have an ICS rom with ICS radio, can I flash the GB RUU and then update to oficial ICS?
Do I still have to make goldcards and stuff?

skinniezinho said:
just a quick question, my phone is factory unlocked (the user I bought if from bought it on amazon.de) and currently I have an ICS rom with ICS radio, can I flash the GB RUU and then update to oficial ICS?
Do I still have to make goldcards and stuff?
Click to expand...
Click to collapse
With Revolutionary S-OFF, the RUU will not successfully overwrite the HBOOT and you will end up with a phone that won't boot past the HTC screen.
You would need to follow this procedure to allow the GB RUU to run successfully:
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
This would leave you with a stock, unrooted phone. You woud be able to use HTCDEV.com to ulock the bootloader so you could root, but you are much better off staying S-OFF and using custom ICS ROMs.

tpbklake said:
With Revolutionary S-OFF, the RUU will not successfully overwrite the HBOOT and you will end up with a phone that won't boot past the HTC screen.
You would need to follow this procedure to allow the GB RUU to run successfully:
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
This would leave you with a stock, unrooted phone. You woud be able to use HTCDEV.com to ulock the bootloader so you could root, but you are much better off staying S-OFF and using custom ICS ROMs.
Click to expand...
Click to collapse
Well I was stupid enought to flash the RUU so ended like you said.
I have macOs, downloaded fastboot and did fine till 2d.
I have the rom.zip but when I try to do
"fastboot flash hboot rom.zip"
it says:
cannot load 'rom.zip'
and the same if I try the vivo_downgrade.img
But if I do fastboot reboot-bootloader
It works..any suggestions?
exnerjan said:
This procedure is tested only AplhaRevX.
1. Install RUU ROM from: http://forum.xda-developers.com/show....php?t=1033922
2. Downgrade HBOOT
2a. download this file: http://alpharev.nl/vivo_downgrade.img
2aa. Connect your phone to the USB
2b.Turn your phone into FastBoot not to HBOOT!!! (VOL DOWN + POWER Button)
2c. Install over fastboot: cmd: "fastboot flash hboot vivo_downgrade.img" (you must install sdk tools)
2d. still fastboot cmd: fastboot reboot-bootloader
3. Start Installation RUU ROM, but DON´T INSTALL !!!!
3a. go tu C:\Users\%username%\AppData\Local\Temp and at last folder find rom.zip
3b. open it, and copy tu folder sdk hboot and instal the same as step 2c.
Click to expand...
Click to collapse

skinniezinho said:
Well I was stupid enought to flash the RUU so ended like you said.
I have macOs, downloaded fastboot and did fine till 2d.
I have the rom.zip but when I try to do
"fastboot flash hboot rom.zip"
it says:
cannot load 'rom.zip'
and the same if I try the vivo_downgrade.img
But if I do fastboot reboot-bootloader
It works..any suggestions?
Click to expand...
Click to collapse
Make sure that you have vivo_downgrade.img in the same folder where you run fastboot from.
Also, you cannot flash a ROM.zip file using the command fastboot flash hboot.

tpbklake said:
Make sure that you have vivo_downgrade.img in the same folder where you run fastboot from.
Also, you cannot flash a ROM.zip file using the command fastboot flash hboot.
Click to expand...
Click to collapse
So I do I do?
edit:
Just found it:
6. Rename this "rom.zip" file to "PG32IMG.zip"
7. Now take your SD card from Phone and connect it to your PC using a card reader or some other phone.
8. Paste that renamed "PG32IMG.zip" at the root of your SD Card.
9. Now power off your phone. Pull out the battery.
10. Insert the SD Card back in the phone. Insert the battery.
11. Now hold your volume down key and press power button. Keep the volume down key pressed. It will start your phone in boot-loader menu.
12. Select FASTBOOT if its not already selected and press power button.
13. It will search your SD Card for files and will find "PG32IMG.zip" file and will ask if you want to update.
14. Press the volume up button as instructed to continue and then sit back and relax.
Once finished it will ask you to reboot. Once rebooted, you'll be back on stock ROM with S-On.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1705913

Guys just a quick question.
Is any way to remove the "relocked" status of the bootloader?
My phone came from warranty,downgraded hboot with htcdev+alpharevx, now I must go to stock again because I need to send it again, did the whole thing but the bootloader says "relocked"

skinniezinho said:
Guys just a quick question.
Is any way to remove the "relocked" status of the bootloader?
My phone came from warranty,downgraded hboot with htcdev+alpharevx, now I must go to stock again because I need to send it again, did the whole thing but the bootloader says "relocked"
Click to expand...
Click to collapse
The only way is to load a stock RUU/ROM that has bootloader 1.13. If you have a ROM that uses HBOOT 2.00-2.02 then it will always show RELOCKED or UNLOCKED.

tpbklake said:
The only way is to load a stock RUU/ROM that has bootloader 1.13. If you have a ROM that uses HBOOT 2.00-2.02 then it will always show RELOCKED or UNLOCKED.
Click to expand...
Click to collapse
do you know wich one is it?for wwe phone.

skinniezinho said:
do you know wich one is it?for wwe phone.
Click to expand...
Click to collapse
wwe -> 2.30.405.1

[SOLVED] [Q] in bootloader at the OS version line text is red. Why ?

Hello Guys
Anyone know why my Os version is red line otherwise green...
look my picture please
thank you for ur response

ankorez said:
Hello Guys
Anyone know why my Os version is red line otherwise green...
look my picture please
thank you for ur response
Click to expand...
Click to collapse
Maybe its saying your installed system version doesn't match the one that came with the hboot version. Maybe the tampered is something to do with it.

ankorez said:
Hello Guys
Anyone know why my Os version is red line otherwise green...
look my picture please
thank you for ur response
Click to expand...
Click to collapse
This guy had a similar problem: http://forum.xda-developers.com/showthread.php?t=2493798&highlight=os+red+text
But then again, yours looks pretty weird: you bootloader is showing two firmware versions: 2.24.401.8 and (3.62.401.1) AND ON TOP OF THAT you're S-On, so you cannot flash unsigned firmware.
were you trying to flash a signed firmware package by any chance?

nkk71 said:
This guy had a similar problem: http://forum.xda-developers.com/showthread.php?t=2493798&highlight=os+red+text
But then again, yours looks pretty weird: you bootloader is showing two firmware versions: 2.24.401.8 and (3.62.401.1) AND ON TOP OF THAT you're S-On, so you cannot flash unsigned firmware.
were you trying to flash a signed firmware package by any chance?
Click to expand...
Click to collapse
i check it
thank you

nkk71 said:
This guy had a similar problem: http://forum.xda-developers.com/showthread.php?t=2493798&highlight=os+red+text
But then again, yours looks pretty weird: you bootloader is showing two firmware versions: 2.24.401.8 and (3.62.401.1) AND ON TOP OF THAT you're S-On, so you cannot flash unsigned firmware.
were you trying to flash a signed firmware package by any chance?
Click to expand...
Click to collapse
yes i have flash firmware from here : http://forum.xda-developers.com/showthread.php?t=2182823
and he say : Can I flash this firmware.zip on any HTC One?
in your thread the guy say he's fixed with gruureset but i don't found on the forum

ankorez said:
yes i have flash firmware from here : http://forum.xda-developers.com/showthread.php?t=2182823
and he say : Can I flash this firmware.zip on any HTC One?
in your thread the guy say he's fixed with gruureset but i don't found on the forum
Click to expand...
Click to collapse
But he was S-Off. You are S-On -> very dangerous flashing firmware with S-On, as you can only flash signed firmware, and only upgrade NO DOWNGRADE.
would I be correct in assuming you did the following commands:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot reboot
as opposed to:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot flash zip <name of firmware>.zip <- yes it has to be done twice, the first one will report failed, the second should succeed.
fastboot reboot
?

nkk71 said:
But he was S-Off. You are S-On -> very dangerous flashing firmware with S-On, as you can only flash signed firmware, and only upgrade NO DOWNGRADE.
would I be correct in assuming you did the following commands:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot reboot
as opposed to:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot flash zip <name of firmware>.zip <- yes it has to be done twice, the first one will report failed, the second should succeed.
fastboot reboot
?
Click to expand...
Click to collapse
yes it's my problem ! i have do this only
would I be correct in assuming you did the following commands:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot reboot
---------------
i 've found that http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
you think if i flash it my problem solved?

ankorez said:
yes it's my problem ! i have do this only
would I be correct in assuming you did the following commands:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot reboot
---------------
i 've found that http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
you think if i flash it my problem solved?
Click to expand...
Click to collapse
The Guru Reset will flash stock ROM (and stock recovery and radio, if you select them in the installer), but it may not solve the firmware issue.
I am just guessing, but because you only ran the "fastboot flash zip <name of firmware>.zip" once, your firmware may be in a state of limbo (if I can call it that):
on one hand it was prepared to upgrade to 3.62.401.1 and that's why it's in the brackets, but since you didn't run the fastboot command another time it actually stayed on 2.24.401.8, and that why you have two different firmware versions in bootloader; one installed 2.24.401.8 another "waiting" to be installed 3.62.401.1. (all this is only a theory)
So what are the options now? Since you were trying to upgrade your firmware (even with S-On, which I take is your preference to stay S-On), I guess you should do it, but this time do it correctly and run the fastboot command twice and make sure it reports success the 2nd time around.
Here's what I would recommend (taking into account you do not wish to S-Off),
1- do a nandroid of your phone, then backup everything to your PC (including the nandroid), just in case.
2- update the firmware, but correctly this time
3- depending on what ROM you were on, either restore it, or get an updated version for your firmware
And actually, before that, if you just want to test the Guru Reset:
1- do a nandroid of your phone, then backup everything to your PC (including the nandroid), just in case.
2- flash Guru Reset and see if that works out for you
Those are pretty much my thoughts
PS: when I say backup everything to PC, it's because (sometimes) flashing stock recovery will completely wipe your phone including internal storage (not to mention that unlocking bootloader does that too)
Hit the thanks button IF i helped

nkk71 said:
The Guru Reset will flash stock ROM (and stock recovery and radio, if you select them in the installer), but it may not solve the firmware issue.
I am just guessing, but because you only ran the "fastboot flash zip <name of firmware>.zip" once, your firmware may be in a state of limbo (if I can call it that):
on one hand it was prepared to upgrade to 3.62.401.1 and that's why it's in the brackets, but since you didn't run the fastboot command another time it actually stayed on 2.24.401.8, and that why you have two different firmware versions in bootloader; one installed 2.24.401.8 another "waiting" to be installed 3.62.401.1. (all this is only a theory)
So what are the options now? Since you were trying to upgrade your firmware (even with S-On, which I take is your preference to stay S-On), I guess you should do it, but this time do it correctly and run the fastboot command twice and make sure it reports success the 2nd time around.
Here's what I would recommend (taking into account you do not wish to S-Off),
1- do a nandroid of your phone, then backup everything to your PC (including the nandroid), just in case.
2- update the firmware, but correctly this time
3- depending on what ROM you were on, either restore it, or get an updated version for your firmware
And actually, before that, if you just want to test the Guru Reset:
1- do a nandroid of your phone, then backup everything to your PC (including the nandroid), just in case.
2- flash Guru Reset and see if that works out for you
Those are pretty much my thoughts
PS: when I say backup everything to PC, it's because (sometimes) flashing stock recovery will completely wipe your phone including internal storage (not to mention that unlocking bootloader does that too)
Hit the thanks button IF i helped
Click to expand...
Click to collapse
Thank you very much i have reflash firmware.zip x2 and the second flash has worked
Thankyou again for you rapid help

ankorez said:
Thank you very much i have reflash firmware.zip x2 and the second flash has worked
Thankyou again for you rapid help
Click to expand...
Click to collapse
My pleasure, if everything is OK now, please add [SOLVED] in the main thread title. Thanks.

By the way im the guy in the other thread,did not get any answers or help had no choice but to use ruu zip to downgrade then ota back up
sent from my s-off 801n M7_UL

steelmaggot said:
By the way im the guy in the other thread,did not get any answers or help had no choice but to use ruu zip to downgrade then ota back up
sent from my s-off 801n M7_UL
Click to expand...
Click to collapse
Quite right it was you, sorry I didnt help out, but I honestly didnt know what the problem was. Only after seeing this guy's screen with two different versions and S-ON, did I think it was an incomplete firmware flash.
Might have been the case with you as well, but I couldnt tell cause the versions were the same, and you were S-Off.
Anyway, lesson learned.

Please help, possible brick after following guide to flash firmware

I was following Vomer's guide on my One, which has been working great. I had HBOOT 1.54, S-Off, SuperCID, and pushed the firmware twice, got the success message, and waited and when it says finished used adb to tell it to reboot. Now I get the splash, with the lock gone, as expected, and then the screen goes black. If I hold power, or power and down, the hardware keys start blinking and then nothing. A few seconds later I get the splash again, then blank again.
It appears to be communicating briefly over USB because my laptop starts trying to install a HTC MTP device (drive is already on the PC and has been fine) before it looses comms and drops out. I can't seem to get adb device to recognize it....
PLEASE tell me someone can help me recover my phone!!! I will be immensely grateful.

And what the HBOOT version you wanted to downgrade to?

Ivanovic said:
And what the HBOOT version you wanted to downgrade to?
Click to expand...
Click to collapse
I wasn't trying to downgrade HBOOT, just rather ensure my firmware was up to date. I'd had mine set up as a GPE and was flashing the DE (after supercid).
By way of an update, I've been able to get into bootloader and I'm a bit scared on what to do next so I dont screw this up. I notice that I still have S-OFF, but HBOOT is now showing 1.56 and it says RELOCKED at the top. My plan was to use rumrunner (just because of the HBOOT, but it is erroring anyway) to unlock bootloader, and then to look up the fastboot commands to push a ROM and recovery. Any advice?

Downgrade to 1.44 and change cid according to the Rom you want. Then unlock or set your bootloader to LOCKED
Here is the file for 1.44 http://www69.zippyshare.com/v/95229262/file.html
Sent from my HTC One using Tapatalk

Can you help me with the adb commands to flash that boot zip? Also, should I run " fastboot flash unlocktoken Unlock_code.bin" to unlock my bootloader first?

vettejock99 said:
Can you help me with the adb commands to flash that boot zip? Also, should I run " fastboot flash unlocktoken Unlock_code.bin" to unlock my bootloader first?
Click to expand...
Click to collapse
You can unlock if you want to flash custom recovery.
Place the file i gave you to the fastboot folder. Boot into bootloader and choose FASTBOOT.
Run the following : fastboot oem rebootRUU
fastboot flash zip filename.zip *where filaname the actual filename of the file i gave you
You will get FAILED or sth so do this command again to succesfully flash the firmware.

Ivanovic said:
You can unlock if you want to flash custom recovery.
Place the file i gave you to the fastboot folder. Boot into bootloader and choose FASTBOOT.
Run the following : fastboot oem rebootRUU
fastboot flash zip filename.zip *where filaname the actual filename of the file i gave you
You will get FAILED or sth so do this command again to succesfully flash the firmware.
Click to expand...
Click to collapse
Awesome. So I've got HBOOT 1.44, S-OFF, bootloader unlocked, supercid, and TWRP 2.6.3.3 flashed again, and I tried sideloading ARHD rom. It all looked good but same thing for the moment, I get the splash and then black......I can't figure out why I can't boot into a rom right now. About to try flashing ROM again.
Okay, so didnt' work. After sideload flashing gets to 100% it just does nothing. Manually rebooting gets me back into the splash then blackness bootloop......

Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu

SaHiLzZ said:
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
Click to expand...
Click to collapse
The former didn't get me anywhere, but I did follow your thinking and decided to use the RUU and start over. I'm happy to report that got me going, and then I was able to get AR HD on. I probably had to do that all along once I wiped the ROM and recovery, as sideloading clearly wasn't going to work (in retrospect) as it has an AROMA installer.
Thanks so much everyone!!

SaHiLzZ said:
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
Click to expand...
Click to collapse
Nice that everything is solved now.
Verstuurd van mijn HTC One

[Q] I Have Completely Bork'd My Phone

After flashing updates regularly for over two years I do not know what I have done to mess my phone up this bad, but I did. There is no more file structure on the phone whatsoever. Nothing. At all.
Currently I can boot into Bootloader or I can boot into CWM Touch Recovery.
Whenever I go to "Install a Zip" using Recovery, there is no option to choose anything because there is no file structure.
Whenever I go to "Install a Zip from Sideload," and ROM file I send to it returns with a Status 7 error. I read online about removing the PROP comments from the update-script to fix the Status 7 error but that did not work, still got a Status 7 error.
I downloaded the RUU for the correct CID, there were two, and both of them fail with Error 155 Unknown Error.
I'm at my wit's end here and am pretty afraid I have bricked my phone. Would anybody here be willing to try to steer me out of the mess I have created?
Thank you,
Chris Williams

misterasset said:
After flashing updates regularly for over two years I do not know what I have done to mess my phone up this bad, but I did. There is no more file structure on the phone whatsoever. Nothing. At all.
Currently I can boot into Bootloader or I can boot into CWM Touch Recovery.
Whenever I go to "Install a Zip" using Recovery, there is no option to choose anything because there is no file structure.
Whenever I go to "Install a Zip from Sideload," and ROM file I send to it returns with a Status 7 error. I read online about removing the PROP comments from the update-script to fix the Status 7 error but that did not work, still got a Status 7 error.
I downloaded the RUU for the correct CID, there were two, and both of them fail with Error 155 Unknown Error.
I'm at my wit's end here and am pretty afraid I have bricked my phone. Would anybody here be willing to try to steer me out of the mess I have created?
Thank you,
Chris Williams
Click to expand...
Click to collapse
You've had an htc one for two years?

BableMan said:
You've had an htc one for two years?
Click to expand...
Click to collapse
No. Started out with my Nexus S, then moved to a Nexus 4, then gave that to my wife and got an HTC One. I love this phone so much I wish I'd had it for two years already, but no.
Do you have any idea of a new path I can try?

misterasset said:
After flashing updates regularly for over two years I do not know what I have done to mess my phone up this bad, but I did. There is no more file structure on the phone whatsoever. Nothing. At all.
Currently I can boot into Bootloader or I can boot into CWM Touch Recovery.
Whenever I go to "Install a Zip" using Recovery, there is no option to choose anything because there is no file structure.
Whenever I go to "Install a Zip from Sideload," and ROM file I send to it returns with a Status 7 error. I read online about removing the PROP comments from the update-script to fix the Status 7 error but that did not work, still got a Status 7 error.
I downloaded the RUU for the correct CID, there were two, and both of them fail with Error 155 Unknown Error.
I'm at my wit's end here and am pretty afraid I have bricked my phone. Would anybody here be willing to try to steer me out of the mess I have created?
Thank you,
Chris Williams
Click to expand...
Click to collapse
Just to know.. Did you try to flash a RUU.exe or a RUU.zip? I had a lot of problems with the .exe files, while flashing the RUU.zip from command line usually work like a charm to me.
Sent from my HTC One using Tapatalk

Delgra said:
Just to know.. Did you try to flash a RUU.exe or a RUU.zip? I had a lot of problems with the .exe files, while flashing the RUU.zip from command line usually work like a charm to me.
Click to expand...
Click to collapse
I have tried both actually. I used Hansoon2000's (I'm at work so hopefully I'm referencing that correctly) all in one toolkit to try to flash the RUU.zip file back to the device. It fails while transferring to the device every single time.
So next I tried to use the RUU.exe, both a newer and older version, for my CID and I get the mysterious Error 155 Unknown Error.
How do I flash the RUU.zip from the command line? I have tried using "Install zip from sideload" but I get a Status Error 7 when trying to flash ROM.zip files, and I have tried using ADB PUSH to push the ROM.zip over to the phone but since there's no file structure it doesn't really ever end up anywhere on the phone. (I'm using ROM.zip generically here for my CM ROMs, not RUU) Is there a command line or ADB function to flash the RUU.zip file that I'm not aware of?
Thanks,
Chris

misterasset said:
So next I tried to use the RUU.exe, both a newer and older version, for my CID and I get the mysterious Error 155 Unknown Error.
Thanks,
Chris
Click to expand...
Click to collapse
Error 155 -> you're probably on hboot 1.55+, so you need to downgrade hboot separately first, (to hboot 1.44) then you can run the RUU. download here: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then in bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot reboot-bootloader
-> confirm hboot is 1.44
and run RUU.
PS: you have to be s-off obviously.

nkk71 said:
Error 155 -> you're probably on hboot 1.55+, so you need to downgrade hboot separately first, (to hboot 1.44) then you can run the RUU. download here: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then in bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot reboot-bootloader
-> confirm hboot is 1.44
and run RUU.
PS: you have to be s-off obviously.
Click to expand...
Click to collapse
Thanks for the info. I'm actually on HBOOT 1.44 already luckily. But I am not S-Off. Is that why the RUU is not working? I tried to use the All-In-One Toolkit to achieve S-Off now, but without a file structure it didn't work.
Any direction on achieving S-Off while it's so messed up?
Thanks,
Chris

misterasset said:
Thanks for the info. I'm actually on HBOOT 1.44 already luckily. But I am not S-Off. Is that why the RUU is not working? I tried to use the All-In-One Toolkit to achieve S-Off now, but without a file structure it didn't work.
Any direction on achieving S-Off while it's so messed up?
Thanks,
Chris
Click to expand...
Click to collapse
Please:
1- date of bootloader
2- a "fastboot getvar all" (remove IMEI and s/n)
3- link to the RUU you are trying to use.
Don't forget pressing the little thanks button for people who have helped

No offense but it sounds as if you simply aren't running an ruu.zip correctly. I'm not understanding all this hensonn2000 or toolkit talk that you have going on. You flash ruu.zip while the phone is in fastboot oem RUU mode. Not that complicated. Also the error 155 was the bootloader being unlocked if I recall correctly. You have to relock it before flashing or running the appropriate RUU. Specially if youre s-on.

Thanks guys. I ended up getting it all working. I did not have the Bootloader relocked and that was why the RUU kept failing.
Thanks again for the extra direction,
Chris

Help Reverting back to stock/flashing RUU

Hello, I need some serious help here! So ive modded the hell out of my phone and now I need to go back to stock. I am trying Mike return to stock guide (which Ive used before successfully) but I keep getting error 155 over and over and phone gets stuck on grey HTC screen (no exclamation marks), I don't know if it has anything to do anything with my firmware having been updated via fastboot to get rid of the red warning. CID is stock, running latest att stock rooted, s-off unlocked bootloader and ive tried 2 different RUUs giving me the same issue
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2
RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2
I will post my bootloader screen and if someone can help me out I appreciate it much!

DroidManIc said:
Hello, I need some serious help here! So ive modded the hell out of my phone and now I need to go back to stock. I am trying Mike return to stock guide (which Ive used before successfully) but I keep getting error 155 over and over and phone gets stuck on grey HTC screen (no exclamation marks), I don't know if it has anything to do anything with my firmware having been updated via fastboot to get rid of the red warning. CID is stock, running latest att stock rooted, s-off unlocked bootloader and ive tried 2 different RUUs giving me the same issue
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2
RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2
I will post my bootloader screen and if someone can help me out I appreciate it much!
Click to expand...
Click to collapse
downgrade hboot to 1.44 and flash the 1.26.502.12 ruu.exe
or flash any x.xx.502.xx decrypted ruu.zip
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_cingular-1-26-502-15-decrypted-zip/
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip
fastboot reboot
do not use windows 8 if using a 1.xx.502.x ruu

alray said:
downgrade hboot to 1.44 and flash the 1.26.502.12 ruu.exe
or flash any x.xx.502.xx decrypted ruu.zip
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_cingular-1-26-502-15-decrypted-zip/
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip
fastboot reboot
do not use windows 8 if using a 1.xx.502.x ruu
Click to expand...
Click to collapse
Nice man thanks so much! Now to get it up to date? It's not showing me an OTA notifications even when I check do I have to flash updates incrementally?
Sent from my HTC One_M8 using XDA Free mobile app