Database Info

[HOW TO] Flash RUU / OTA when getting ERROR 155 although phone is back to stock

If you're constantly getting ERROR 155 when trying to flash an RUU even though you've already returned your phone to stock, you also need to RELOCK the bootloader!
I'm writing this because for some reason just getting the phone back to stock (i.e. restore image of stock ROM through custom recovery then flash stock recovery) didn't work for me. It only worked after I RELOCKED the bootloader.
Step 0. Restore your phone to stock FIRST, i.e. restore stock ROM from image using custom recovery then flash stock recovery.
Step 1. Restart your phone into bootloader either by hard-off (i.e. keep power button pressed for min. 10 sec) then volume up + power button or by adb at the command prompt:
Code:
C:\> adb reboot-bootloader
Step 2. Type this command at the command prompt:
Code:
C:\> fastboot oem lock
Don't worry if it says FAILED anywhere in the output, it should all be fine regardless. The phone should reboot automatically into bootloader and should say RELOCKED.
Now you can flash any RUU (EDIT: only if compatible with your CID) and you can also check for and install OTA updates. Once you've done this, your HBOOT and RADIO should be updated to the latest version so you can UNLOCK again using the HTCDev method and then flash whatever you want to flash.
Hope this helps you guys!
P.S. I think it's worth also trying this for other ERROR codes... you never know, it may help.

Getting error 131 didn't help. But much thanks for trying help
i hear voices in my head

Any RUU or still only the specific carrier RUU?
Sent from my HTC One S using xda premium

I think the prob is that i have VODAP102 CID in ruu 1.5... and 1.78
i hear voices in my head

had that error too, worked for me with locking bootloader
again, starting ruu-exe after that.
thanks

ovimunt said:
If you're constantly getting ERROR 155 when trying to flash an RUU even though you've already returned your phone to stock, you also need to RELOCK the bootloader!
I'm writing this because for some reason just getting the phone back to stock (i.e. restore image of stock ROM through custom recovery then flash stock recovery) didn't work for me. It only worked after I RELOCKED the bootloader.
Step 0. Restore your phone to stock FIRST, i.e. restore stock ROM from image using custom recovery then flash stock recovery.
Step 1. Restart your phone into bootloader either by hard-off (i.e. keep power button pressed for min. 10 sec) then volume up + power button or by adb at the command prompt:
Code:
C:\> adb reboot-bootloader
Step 2. Type this command at the command prompt:
Code:
C:\> fastboot oem lock
Don't worry if it says FAILED anywhere in the output, it should all be fine regardless. The phone should reboot automatically into bootloader and should say RELOCKED.
Now you can flash any RUU (EDIT: only if compatible with your CID) and you can also check for and install OTA updates. Once you've done this, your HBOOT and RADIO should be updated to the latest version so you can UNLOCK again using the HTCDev method and then flash whatever you want to flash.
Hope this helps you guys!
P.S. I think it's worth also trying this for other ERROR codes... you never know, it may help.
Click to expand...
Click to collapse
now I get error 132 : signature error. I have superCID help?

I don't know how you can sort out the CID issue. I have a SIM free phone so I haven't really looked into that. Sorry....

are you refering to recovery stock (step 1)?

i get error 155 but i have stock recovery and locked bootloader,
my bootloader says security warning though which is strange.
current rom is the ir1 modaco stock rom

i had 155, i put stockrecovery back and relocked bootloader, then 155 changed to battery too low error, so turned it off, charged for 2hrs, and the ruu worked for the first time

I have HTC One S z560e and i want to go back to stock but even with the bootloader unlocked i still get 155error.... what should i do?

Hey people.
Can someone tell what version of RUU i can use for HTC one S4 im in portugal?
Tks

[S-OFF] revone s-off

I have found that revone s-off originally for the HTC One/Droid DNA works on the One S. You MUST be rooted for this to work. Super CID is NOT required. I do NOT take any credit for this, I just want to bring it to your atention. All the credit goes to @ieftm who made this tool.
HTC One revone s-off link: http://forum.xda-developers.com/showthread.php?t=2314582
HTC Droid DNA revone s-off link: http://forum.xda-developers.com/showthread.php?t=2314706
NOTE
Please do not ask me if this works on any other firmware other than 3.16.401.8/9. Unfortunately I cannot tell you or test it with your firmware. Please try it at least and if it WORKED, comment below and I will add it to the list below.
CONFIRMED working on:
3.16.401.8/9 WWE
If you are not rooted or on stock rom you can root by downloading Kingo Android Root from here. You need a Windows PC or a Mac/Linux running Wine Windows Program Loader
Instructions
1. Download revone here.
2. Connect your phone with USB Debugging On and open a Command/Terminal window.
3. cd to the folder containing revone.
4. Type in the following:
Code:
adb push revone /data/local/tmp/
adb shell
cd /data/local/tmp/
chmod 755 revone
5. Prepare your phone by typing:
Code:
./revone -P
6. If you get a message saying "success" then proceed to step 7.
**If your phone reboots then wait 2 minutes and try again from step 3.
**If you are told to reboot then do so and try again from step 3.
**If you get an error and your phone does not reboot or if you are not told to reboot then you can try step 7 but not guaranteed to work.
7. To s-off using revone type in:
Code:
./revone -s 0 -u
8. If it reported success type in:
Code:
exit
adb reboot bootloader
9. You should now see s-off. If not try again.
10. Here are some OPTIONAL commands:
Code:
./revone -u (Unlocks the bootloader)
./revone -l (Locks the bootloader with locked message)(Important for warranty reasons)
./revone -r (Relocks the bootloader with relocked message)
./revone -t (Removes the tampered message)
Please hit the thanks button here and here if this helped.​

Good to have a another option
Sent from my One S using Tapatalk

at least now we can unlock bootloader without htcdev or losing data, i've tested all of the commands myself and can confirm they all work

Does this work with 3.16.401.9?

it should, i tried it with 3.16.401.8 and please tell me if it does work

is superCID required for this?

dd98 said:
at least now we can unlock bootloader without htcdev or losing data, i've tested all of the commands myself and can confirm they all work
Click to expand...
Click to collapse
I may have missed something out but, how can you be root (to use revone s-off) without htcdev?

@twist3d0n3 its not

@Bricolo_fr i added program called kingo android root which supports the htc one s and doesnt require a bootloader unlock

i get 'unable to open revone: permission denied' when doing the chmod 755 revone command... what do?

after adb shell type su and try again

aye that gets past it, thanks.
when i run ./revone -P it says failed (code 1).
i carried on based on what the OP says, says successful but still won't s-off on reboot. tried 4 times now and still the same

twist3d0n3 said:
i get 'unable to open revone: permission denied' when doing the chmod 755 revone command... what do?
Click to expand...
Click to collapse
I assume you're doing it straight from the phone, so try the "su" command before you start all the other commands (which is done by simply typing in "su".)
I have aquestion of my own also... On the "./revone -P" command, I get a "revone failed (error code = 1)". What do I do about this? I'm trying to do it straight from the terminal emulator by he way.

Speeder975 said:
I assume you're doing it straight from the phone, so try the "su" command before you start all the other commands (which is done by simply typing in "su".)
I have aquestion of my own also... On the "./revone -P" command, I get a "revone failed (error code = 1)". What do I do about this? I'm trying to do it straight from the terminal emulator by he way.
Click to expand...
Click to collapse
You haven't read too much from those links in OP aren't you? If you have done that, you've noticed that the same error was discussed there as well. Shortly, you are either on the wrong ROM to try revone or you should reboot till it works. If after rebooting several times you got the same error, then you might need to flash first a ROM as close to stock as possible... Viper could be an option but I'm not sure cause I didn't try
Sent from nowhere over the air...

Rapier said:
You haven't read too much from those links in OP aren't you? If you have done that, you've noticed that the same error was discussed there as well. Shortly, you are either on the wrong ROM to try revone or you should reboot till it works. If after rebooting several times you got the same error, then you might need to flash first a ROM as close to stock as possible... Viper could be an option but I'm not sure cause I didn't try
Sent from nowhere over the air...
Click to expand...
Click to collapse
I DID read those links. Tried about 4 different ROMS, two of which were Sense-based. Oddly enough, Viper is a ROM I haven't tried yet... I'll do that

Speeder975 said:
I DID read those links. Tried about 4 different ROMS, two of which were Sense-based. Oddly enough, Viper is a ROM I haven't tried yet... I'll do that
Click to expand...
Click to collapse
OK, sorry I presumed wrongly...try Viper also. I remember in the first days of the S-Off "thing",, it was one of the ROMs of choice for starting this. I was never trying S-Off since I don't needed but I've read alot about it and the ways of achieving it.

This looks like the perfect solution to get S-OFF without losing all my data. But I can't even get root with Kingo. It tells me "Root Failed! The current status of your device is S-ON, please go to "Tools"=>"HTC UnlockBootloader" to unlock it to S-OFF and try again." I know this is the wrong thread for Kingo questions, but maybe someone on his way to S-OFF has solved the problem? Btw: Where is this "Tools" menu?
I'm stuck in an endless loop here

tried this a few times on my stock (rooted) backup and still no go... says failed at both bits that start ./revone

FraBle said:
Does this work with 3.16.401.9?
Click to expand...
Click to collapse
Read OP

hi i got this message after step 5
Gaining root access (thanks to Dan's motochopper)...Segmentation fault
139|[email protected]:/data/local/tmp $
whats the problem.

[Q] Cannot Root after XNPH30O

Hello guys, after a long time with the APPLE, i´ve changed to android.. mainly because of OPO. No regrets.
After a few seconds using it i´ve rooted it and was really happy...
But... after the OTA of the version XNPH30O of CyanogenMod i´m unable to root it again...
I can fastboot... but it stay at the fastboot logo...
Reading arond the interwebs, i´ve realized that it could be something related with the bootloader being locked.... so i´ve unlocked (i think) using the OPO toolkit.. I wiped it and still cannot bypass the fastboot screen..
Any sugestion or help would be awesome.
I´m running th OPO on CyaniogenMod XNPH30O, chinese model.
Thanks and cheers from Brazil.

Go into fastboot mode and issue this command:
Code:
fastboot oem device-info
Post the results.
Transmitted via Bacon

ogabriel said:
Hello guys, after a long time with the APPLE, i´ve changed to android.. mainly because of OPO. No regrets.
After a few seconds using it i´ve rooted it and was really happy...
But... after the OTA of the version XNPH30O of CyanogenMod i´m unable to root it again...
I can fastboot... but it stay at the fastboot logo...
Reading arond the interwebs, i´ve realized that it could be something related with the bootloader being locked.... so i´ve unlocked (i think) using the OPO toolkit.. I wiped it and still cannot bypass the fastboot screen..
Any sugestion or help would be awesome.
I´m running th OPO on CyaniogenMod XNPH30O, chinese model.
Thanks and cheers from Brazil.
Click to expand...
Click to collapse
To root you need to unlock the boot loader than you install a customer recovery. After you do this I recommend that you make a nandroid backup for when you want to go back to stock (a nandoid is an exact back up of you phone). Once you have unlocked the boot loader and installed a custom recovery made a backup you would put a flashable root zip on your SD and flash it in recovery. Most will recommend that you do not use a tool kit because it is doing the work for you and you don't really know/understand what is happening. I have not updated to XNPH30O but I'm sure its been rooted.
You need to have ADB and fastboot on your computer. << Google how to get this done.
Use this guide it will help do the following. >> http://forum.xda-developers.com/showthread.php?t=2788632
1. Put phone in fastboot
2. run command "fastboot OEM unlock" < this is what unlocks the bootloader it wipes your phone.
3. You will need to install a customer recovery
4. Flash the flashable Super User.
Hope this helps.

jdh10475 said:
To root you need to unlock the boot loader than you install a customer recovery. After you do this I recommend that you make a nandroid backup for when you want to go back to stock (a nandoid is an exact back up of you phone). Once you have unlocked the boot loader and installed a custom recovery made a backup you would put a flashable root zip on your SD and flash it in recovery. Most will recommend that you do not use a tool kit because it is doing the work for you and you don't really know/understand what is happening. I have not updated to XNPH30O but I'm sure its been rooted.
You need to have ADB and fastboot on your computer. << Google how to get this done.
Use this guide it will help do the following. >> http://forum.xda-developers.com/showthread.php?t=2788632
1. Put phone in fastboot
2. run command "fastboot OEM unlock" < this is what unlocks the bootloader it wipes your phone.
3. You will need to install a customer recovery
4. Flash the flashable Super User.
Hope this helps.
Click to expand...
Click to collapse
That's all good, but we need more information from him before giving advice, hence my post.
Transmitted via Bacon

timmaaa said:
That's all good, but we need more information from him before giving advice, hence my post.
Transmitted via Bacon
Click to expand...
Click to collapse
True

timmaaa said:
Go into fastboot mode and issue this command:
Code:
fastboot oem device-info
Post the results.
Click to expand...
Click to collapse
I am not the original poster, but I seem to have the same problem—no root after flashing the SuperSU zip file. Here is the result of the above command:
Code:
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.000s]
finished. total time: 0.000s

Thanks everyone for the help...
i´ve been reading a lot since this post... and, still wraping my head in Android rooting.
But i managed to fix the problema... I needed to install the TWRP.
So... in this particular case after entering fastboot i´ve installed TWRP (with OPO toolkit in Boot a recovery>Boot!>TWRP) and proceeded to root after that.

hgmichna said:
I am not the original poster, but I seem to have the same problem—no root after flashing the SuperSU zip file. Here is the result of the above command:
Code:
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.000s]
finished. total time: 0.000s
Click to expand...
Click to collapse
So what exactly is your problem? Your bootloader is unlocked, so just flash TWRP and then flash SuperSU.
Transmitted via Bacon

timmaaa said:
So what exactly is your problem? Your bootloader is unlocked, so just flash TWRP and then flash SuperSU.
Click to expand...
Click to collapse
Had done that at least five times without success, but eventually, after finding a slightly newer version, it worked. Problem solved.

Simple process don't use toolkits
For any newbs reading this, your Oneplus is simple to unlock, add custom recovery and root. Please do not use tool kits follow the simple steps to do it manually. You will be better off in the long run.

jk8260 said:
For any newbs reading this, your Oneplus is simple to unlock, add custom recovery and root. Please do not use tool kits follow the simple steps to do it manually. You will be better off in the long run.
Click to expand...
Click to collapse
What he said. http://forum.xda-developers.com/showthread.php?t=2788632 is a great guide to use. Very easy to follow and doesn't take long.

OS keeps saying "OS-"

Hi, I just updated to the latest firmware and well at first it tells me I have the latest number on the OS part and then after flashing a ROM or something or maybe even rebooting into it it says what the threads name states. It doesn't effect anything but I like having everything perfect and would like to know why its happening, any ideas?
& Yes I do have a ROM and everything loaded working perfectly.

S1L3nTShaDoWz said:
Hi, I just updated to the latest firmware and well at first it tells me I have the latest number on the OS part and then after flashing a ROM or something or maybe even rebooting into it it says what the threads name states. It doesn't effect anything but I like having everything perfect and would like to know why its happening, any ideas?
& Yes I do have a ROM and everything loaded working perfectly.
Click to expand...
Click to collapse
Happened on the M7 too...like you said, it doesn't affect anything. As long as you're not staring at the information on your bootlader screen you won't even notice.

brholt6 said:
Happened on the M7 too...like you said, it doesn't affect anything. As long as you're not staring at the information on your bootlader screen you won't even notice.
Click to expand...
Click to collapse
But I am... bootloader is life, life is bootloader, must stare! Lol well anyways no fix I guess then? As a perfectionist every little flaw makes me crave a solution.... and if there isn't one well I turn into Darth Vader and force choke someone... no one wants that!

S1L3nTShaDoWz said:
But I am... bootloader is life, life is bootloader, must stare! Lol well anyways no fix I guess then? As a perfectionist every little flaw makes me crave a solution.... and if there isn't one well I turn into Darth Vader and force choke someone... no one wants that!
Click to expand...
Click to collapse
It's a Twrp bug.
Update your recovery and reflash the firmware.
(Assuming we have a fixed version...)

santod040 said:
It's a Twrp bug.
Update your recovery and reflash the firmware.
(Assuming we have a fixed version...)
Click to expand...
Click to collapse
I didnt flash it with TWRP, used RUU mode. Could it still be related?

Hi friend i need some unguent help. I am stuck on this 2 screen cant go no where. any kind of reboot brings me back on this 2 screens. if i connect with my pc via usb and try to flash recovery its keep giving error signature verify fail some if i try to flash any rom by put it into sd card.
All i have done is run following command and now i am not able to do anything.
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
adb reboot bootloader
fastboot oem writesecureflag 3

alibhatti said:
Hi friend i need some unguent help. I am stuck on this 2 screen cant go no where. any kind of reboot brings me back on this 2 screens. if i connect with my pc via usb and try to flash recovery its keep giving error signature verify fail some if i try to flash any rom by put it into sd card.
All i have done is run following command and now i am not able to do anything.
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
adb reboot bootloader
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
I'm still fairly new to HTC, but I'm going to try...You're showing S-on and locked. I would assume locked means your boot loader is locked. You probably won't be able to flash a recovery if you're locked. I'm not even sure what "security warning" means.
Sent from my HTC6525LVW using Tapatalk

OS keeps saying OS-
They could have written that to the data rather than the actual OS name/number, seen it before in an unofficial ROM.
Sent from my SM-T210
---------- Post added at 04:57 AM ---------- Previous post was at 04:45 AM ----------
alibhatti said:
Hi friend i need some unguent help. I am stuck on this 2 screen cant go no where. any kind of reboot brings me back on this 2 screens. if i connect with my pc via usb and try to flash recovery its keep giving error signature verify fail some if i try to flash any rom by put it into sd card.
All i have done is run following command and now i am not able to do anything.
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
adb reboot bootloader
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
Tampered : fastboot oem writesecureflag - you've triggered this because you are S-ON.
S-ON : You cannot flash anything other than Recovery if I remember rightly, due to 'Locked'
Locked : Bootloader is locked, meaning hboot is locked so no flashing, this also locks any other partitions they include which can be almost the whole devices partitions, a Custom Recovery can be installed though (or you'd have a brick with nearly zero access)
Unlocking Bootloader : if I'm not mistaken usually done through HTC with an unlock token (some devices can be done without going through htc), if you're stuck with it booting to hboot you'll have to check the devices forums for a solution :what:
Sent from my SM-T210

S1L3nTShaDoWz said:
I didnt flash it with TWRP, used RUU mode. Could it still be related?
Click to expand...
Click to collapse
I realize that, as you can't flash firmware in recovery.
Yes I'm certain it's a Twrp bug that has effected multiple HTC devices.
Flashing a version that has been fixed(we don't have one yet) and then flashing the firmware again fixes the blank OS version.
The problem is that once you use twrp again after updating firmware, it's wiping your /misc partition, which wipes out that info.
Once we get an updated version with the fix for that included, this will no longer be an issue.
I was never implying that using Twrp to flash the firmware was the problem, just the fact that you are using that recovery is enough to wipe the info.

Here is a working version: http://forum.xda-developers.com/verizon-htc-one-m8/general/twrp-blank-os-fix-t2879306

[SOLVED] Completely re-stock from 5.0.1 for Edge upgrade

Solved this one on my own. Went from LolliGPE 5.0.1 with Elite kernel and TWRP, S-OFF and unlocked to stock VZW 5.0.1, S-ON and locked. Here's what I did:
1) Remove developer warnings. Follow the instructions on this thread. Unsure if this is entirely necessary as the next step probably takes care of this, but better safe than sorry.
2) Flash stock everything. Follow the instructions on this thread. I used the USB all-in-one FUU method, but whatever works for you is best. I ran into a problem in which an error symbol appeared next to the progress bar and the flash failed; to fix this I held power and volume up for about 30 seconds until it rebooted and the error symbol appeared in all four corners, and then started the FUU again. This time it was successful.
3) Reboot and load up the phone. It will be completely stock and will take about 5-10 minutes to fully boot the first time around. Afterwards, head to settings > about > software information > more and hit the Build number entry until you are a developer. Then go back to Developer options and enable USB debugging.
If rebooting shows the developer information, re-flash the zip from step 1.
4) Run adb devices and ensure your phone is listed. Then run adb shell followed by su. Accept the superuser request on your phone, and then copy the following and paste it into the prompt:
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
Hit enter and then run adb reboot bootloader. You should be locked.
5) Put it back into S-ON by running
fastboot oem writesecureflag 3
...followed by
fastboot reboot-bootloader
You should be locked and S-OFF on stock 5.0.1. The only thing that's there is SuperSU. To remove root, simply install HTC Sync Manager, connect your device, and choose to repair it. The official clean Verizon software will be flashed and your phone will be as if it just came out of the box.

Klayderpus said:
Solved this one on my own. Went from LolliGPE 5.0.1 with Elite kernel and TWRP, S-OFF and unlocked to stock VZW 5.0.1, S-ON and locked. Here's what I did:
1) Remove developer warnings. Follow the instructions on this thread. Unsure if this is entirely necessary as the next step probably takes care of this, but better safe than sorry.
2) Flash stock everything. Follow the instructions on this thread. I used the USB all-in-one FUU method, but whatever works for you is best. I ran into a problem in which an error symbol appeared next to the progress bar and the flash failed; to fix this I held power and volume up for about 30 seconds until it rebooted and the error symbol appeared in all four corners, and then started the FUU again. This time it was successful.
3) Reboot and load up the phone. It will be completely stock and will take about 5-10 minutes to fully boot the first time around. Afterwards, head to settings > about > software information > more and hit the Build number entry until you are a developer. Then go back to Developer options and enable USB debugging.
If rebooting shows the developer information, re-flash the zip from step 1.
4) Run adb devices and ensure your phone is listed. Then run adb shell followed by su. Accept the superuser request on your phone, and then copy the following and paste it into the prompt:
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
Hit enter and then run adb reboot bootloader. You should be locked.
5) Put it back into S-ON by running
fastboot oem writesecureflag 3
...followed by
fastboot reboot-bootloader
You should be locked and S-OFF on stock 5.0.1. The only thing that's there is SuperSU. To remove root, simply install HTC Sync Manager, connect your device, and choose to repair it. The official clean Verizon software will be flashed and your phone will be as if it just came out of the box.
Click to expand...
Click to collapse
It's a lot quicker to just do step 4 in twrp and flash my s-on ruu and then turn s-on.