Database Info

[Q] RUU error 155, can't get into recovery, HALP

Okay so I have been running CM10 fine for months. But I got a notification about an OTA update to CM10.1 and decided to let it install... bad idea.
the install process failed somehow and then my phone was stuck at the HTC screen when booting. Booting into recovery wouldn't work because it would try to install the ROM but always fail. So I figured I could just flash my recovery and restore. So I download the newest TWRP and flasht he recovery. Once I get into TWRP I couldn't read the SDCARD or find any of my files. But if I use an adb shell I can see CM10.1 and Gapps for 4.2.2 So I tried restarting recovery a couple times but I could never get the recovery to see the files. I figured I would just relock the bootloader, run RUU, then start the rooting/unlocking process fresh as I have done in the past when I got into trouble. Only problem now is that I get error 155 when trying to run the RUU utility, and can't boot into recovery since I re-locked my bootloader. I can still use fastboot but that's it, HALP!

What ruu are you using? Error 155 usually means its the wrong ruu.

iElvis said:
What ruu are you using? Error 155 usually means its the wrong ruu.
Click to expand...
Click to collapse
I tried this one. http://forum.xda-developers.com/showthread.php?t=1814217

SkuzeeII said:
I tried this one. http://forum.xda-developers.com/showthread.php?t=1814217
Click to expand...
Click to collapse
Do you have an AT&T phone? Or something else?

I was able to get the RUU to work last time, but when I try to unlock using the X_Factor root it doesn't actually unlock the bootloader. I've done this plenty of times before and followed the steps correctly. Any idea what's going on?

SkuzeeII said:
I was able to get the RUU to work last time, but when I try to unlock using the X_Factor root it doesn't actually unlock the bootloader. I've done this plenty of times before and followed the steps correctly. Any idea what's going on?
Click to expand...
Click to collapse
unlock yourself using "fastboot flash unlocktoken Unlock_code.bin"

Right, just push your unlock token again. Once you unlock the first time, subsequent unlocks are a simple fastboot command.

iElvis said:
Right, just push your unlock token again. Once you unlock the first time, subsequent unlocks are a simple fastboot command.
Click to expand...
Click to collapse
I've been at the same issue myself.
Have tried using the toolkit and pushing manually. I can get to the screen where you choose yes/no to unlock, which I choose yes. Then the phone just shuts off. When I turn it back on, the factory reset is done but I'm still stuck at "RELOCKED". I've probably tried this 20 times tonight and do not know what I'm missing. My CID is still all 1s.
FYI, using 2.20 RUU (had a similar issue... CM10 nightly bricked phone completely so used 2.20 RUU to restore phone)

i sometimes have alot of problems getting token to stick. try booting into bootloader without phone plugged up to computer, once booted into bootloader plug in phone, then push the token.

I've found that you need to unplug and reboot your phone before pushing the token. When I do this, it always takes the first time.
Sent from my HTC One X using Tapatalk 2

So I found that I was rebooting the phone myself when I shouldn't have during the unlock process. So I've got it unlocked now, and I can install recovery like TWRP or CWM but now I'm trying to get a ROM to load. I'm using the last Evita CM10 build but it always gets stuck on the booting screen. I think maybe I need an update.zip or need to use adb to get root from fastboot or recovery but I can't remember how and searching hasn't helped me yet...

I'm going to try to do a fastboot flash boot boot.img with the boot.img file from my CM10 zip file. Maybe that's what I was missing

I really should just be more patient before creating a thread. I got into CM10 then got S-OFF so now I'm on CM10.1

No luck trying to apply recovery...

Brand new 5 minute old HTC one with a 2.19.0000 HBOOT S-On. Unlocked bootloader via htcdev with no problem. Reboot into fastboot and flash recovery with cwm, it says its applied. I vol up to bootloader, power button, vol down to recovery and power button. I get a pink "Entering Recovery..." after about 10 seconds the device reboots, its the stock htc logo screen and then its back into the stock ROM. I'm new to this whole HTC "S-On" thing but it seems that the securityn defeats anyone perm writing to recovery, etc. Okay, cool no prob. I read theres tools like rumrunner,revone etc that break that. I run revone however it doesnt seem to work with my 2.19.0000 HBOOT and I get a "Segmentation Fault (core dumped) 139" when trying to run them. (and yes i tried running them 183011 times) Rumrunner cant even find my device however adb does and fastboot works fine.
What am I missing? Is this like an anti-tamper mechanism by the carrier that HTC puts on there? The whole reason I stayed HTC is because my previous phone was so great to root/rom. I had 0 problems putting a rom and cwm/rooting my HTC One S. Now the mini I cant even get passed step 2 of the process.

well i was finally able to get things working. im still s-off but rooted and running h8rifts cm11 m4 rom. so far so good. :good:

Make sure you phone is unlocked and try and different recovery like the twrp recovery. It's great! I've been using it all the time and it's easy to use because its touch screen. Flash it via fastboot on cmd. Here is the link to the twrp: http://forum.xda-developers.com/showthread.php?t=2418938

[Q] Help with returning to stock/Stuck at bootloader

I'm having a problem with my One X and returning it to stock. I've been rooted with S-ON for quite some time now and had the Viper ROM installed. Now it's time to trade it in to Amazon and I wanted to return it to stock and hopefully remove the tampered text. I seem to have gotten myself in to a pickle though and I'm stuck at the bootloader.
I've been using the WinDroid Universal HTC Toolkit to install stuff, I have the unlock.bin file from HTC, and I've been able to communicate with the phone through my Windows 7 computer no problem. But after the last attempt I relocked the phone and not I'm stuck. Here's what it says on the bootloader screen:
*** TAMPERED
*** RELOCKED
*** Security Warning
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
Using the WinDroid kit it shows that it successfully unlocked the bootloader and loaded TWRP, but since it's in fastboot, WinDroid doesn't recognize the phone model and won't let me send any files to it though. When I reboot the phone in to recovery, it returns me to the bootloader.
Anyone have any advice?

First piece of advice: ditch the toolkit, you don't need it. The best way for you to go about this is to follow these steps:
1) Unlock the bootloader again.
2) Flash TWRP again.
3) Flash a ROM.
4) Get s-off (this is the most important step, and all the previous steps were all leading to this).
5) Run an at&t RUU (to return the phone to stock, I'm assuming it's the at&t model?).
6) Return the CID to the original CID.
Code:
fastboot oem writecid CWS__001
7) Relock the bootloader.
Code:
fastboot oem lock
8) Return the phone to s-on.
Code:
fastboot oem writesecureflag 3
Voila.
Sent from my Evita

Wow. Nice Tim !!!
Sent from my Inspire 4G using Tapatalk

Thanks for the help so far. Under your advice I'm using fastboot commands manually to try and get this to work. So now I'm unlocked again, but I'm having a problem flashing TWRP. I downloaded the latest TWRP for the Evita and ran fastboot flash recovery evita.img (that's what I renamed the file to). It tells me that sending and writing was OKAY, so it should work. Then I try to reboot to recovery from the bootloader menu, and it fails after this. It appears to boot something up, I get a blank screen, then it reboots again on it's own without showing the TWRP menus.
What am I doing wrong?

You can't reboot to the recovery, you can only reboot to the bootloader and then manually select recovery using the hardware buttons (volume = scroll, power = select). The whole process should go like this:
Code:
fastboot flash recovery evita.img
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can manually select recovery and it should hopefully boot into it.
Sent from my Evita

That's what I did, although I just tried these steps again. When I used the volume/power buttons and chose recovery, it reboots as it should, then it tries to load the recovery, fails, then reboots and starts up the phone. I should note, and this might be the problem, is that phone boots up totally in to the full blown OS. It's Android 4.1.1 with the 3.18 kernel.
I have SuperCID, and the phone says it is unlocked with S-ON.
Does it make sense and try to flash the 2.15 firmware at this point since my HBOOT is older?

I tried another thing since I can actually use the phone and I'm rooted, I installed GooManager from the store and let that install the recovery then rebooted. It did the same thing. At the very least, if I could only get TWRP working I could recover a TWRP backup I made.
And ultimately, the phone works at this point, I just want to remove the tampered text and keep it at stock. Since I have a working ROM, should I just follow your steps 6, 7 and 8? Do I still need to achieve S-Off and worry about the recovery?

You need s-off, otherwise running the RUU will brick your phone. Just try getting s-off without the recovery. Which ROM is currently installed?
Sent from my Evita

I have an AT&T stock deodexed ROM version 3.18.502.6.

Ok, scratch that, without root you cannot get s-off. What's the exact filename of the recovery you've tried to flash?
Sent from my Evita

[Q] HTC One Mini not booting up fully and no access to recovery

Hello,
My phone was updating and crashed. The phone turns on but only the HTC logo appears and then goes to a black screen. I can't fastboot into the device as it is not recognised. I can't access TWRP recovery any more and goes to a downloading screen and then restarts again. While in the bootloader the phone shows the following:
***TAMPERED***
*** RELOCKED***
M4_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.19.0000
RADIO-1.22.40e.00.07
OpenDSP-v19.2.0268.0927
OS-1.31.401.1
eMMC-boot 1024MB
Aug 7 2013, 17:37:54.0
Please help me, any help greatly appreciated!
Update:
The phone is working and has an update but it can not update on the device, is there a way i can get the downloaded OTA file on to my PC?

CoolAndroid1 said:
Hello,
My phone was updating and crashed. The phone turns on but only the HTC logo appears and then goes to a black screen. I can't fastboot into the device as it is not recognised. I can't access TWRP recovery any more and goes to a downloading screen and then restarts again. While in the bootloader the phone shows the following:
***TAMPERED***
*** RELOCKED***
M4_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.19.0000
RADIO-1.22.40e.00.07
OpenDSP-v19.2.0268.0927
OS-1.31.401.1
eMMC-boot 1024MB
Aug 7 2013, 17:37:54.0
Please help me, any help greatly appreciated!
Click to expand...
Click to collapse
Hi,
What do you want to flash stock sense 6...??
greets

shivasrage said:
Hi,
What do you want to flash stock sense 6...??
greets
Click to expand...
Click to collapse
Hello,
Yes I would like to go back to Sense 6 or any stock firmware preferably 4.4.2
Thanks

CoolAndroid1 said:
Hello,
Yes I would like to go back to Sense 6 or any stock firmware preferably 4.4.2
Thanks
Click to expand...
Click to collapse
Ok
First I recommend you to unlock your bootloader.
So if you are in bootloader and your device is not recognised I think it´s a driver issue.
If you allready checked it check it once more or update your tools (ADB, fastboot)
If nothing helps you could go to recovery and format your device (not only wipe format) should be clear that all data on device is lost.
Try different recoverys some people report that philz also works fine on M_4. (try install new rom option on philz).
DONT flash stock sense 6 ROM (wrong partition layout for this hboot) with this hboot rather take 5.5.
I´m sorry but without get connectet via ADB or fastboot I think there is no chance to get it working again.
greets

shivasrage said:
Ok
So if you are in bootloader and your device is not recognised I think it´s a driver issue.
If you allready checked it check it once more or update your tools (ADB, fastboot)
If nothing helps you could go to recovery and format your device (not only wipe format) should be clear that all data on device is lost.
Try different recoverys some people report that philz also works fine on M_4. (try install new rom option on philz).
DONT flash stock sense 6 ROM (wrong partition layout for this hboot) with this hboot rather take 5.5.
With out get connectet via ADB or fastboot I think there is no chance to get it working again.
greets
Click to expand...
Click to collapse
I can not access recovery to wipe anything out, on bootloader if i choose to wipe it attempts to load recovery which goes into download mode. The device comes up as "Device failed emulation" on Windows 8

CoolAndroid1 said:
I can not access recovery to wipe anything out, on bootloader if i choose to wipe it attempts to load recovery which goes into download mode. The device comes up as "Device failed emulation" on Windows 8
Click to expand...
Click to collapse
Ok
I tell you in short terms:
If you can´t get a fastboot connection to your device it looks very bad to bring your device back.
For wiping something you need recovery for flashing new recovery you need fastboot.
For flashing a new firmware to fix messed up partitions you need fastboot.
And first of all to unlock your bootloader you need fastboot.
You see all ends up with fastboot.
As what the device is shown in the manager of windows?
Better to use Windows 7 there are much driver problems people reporting on win 8
greets

Ok, I will use a win 7 pc and let you know

shivasrage said:
Ok
I tell you in short terms:
If you can´t get a fastboot connection to your device it looks very bad to bring your device back.
For wiping something you need recovery for flashing new recovery you need fastboot.
For flashing a new firmware to fix messed up partitions you need fastboot.
And first of all to unlock your bootloader you need fastboot.
You see all ends up with fastboot.
As what the device is shown in the manager of windows?
Better to use Windows 7 there are much driver problems people reporting on win 8
greets
Click to expand...
Click to collapse
After i fix my drivers issue what can i do afterwards?

shivasrage said:
Ok
I tell you in short terms:
If you can´t get a fastboot connection to your device it looks very bad to bring your device back.
For wiping something you need recovery for flashing new recovery you need fastboot.
For flashing a new firmware to fix messed up partitions you need fastboot.
And first of all to unlock your bootloader you need fastboot.
You see all ends up with fastboot.
As what the device is shown in the manager of windows?
Better to use Windows 7 there are much driver problems people reporting on win 8
greets
Click to expand...
Click to collapse
I can now do the fastboot command from CMD

CoolAndroid1 said:
After i fix my drivers issue what can i do afterwards?
Click to expand...
Click to collapse
If you have a connection via fastboot you first have to decide what ROM you want, search for the matching firmware.
for example flash the latest firmware for M_4... 4.09.401.3 from here (new partition layout for e.g. sense 6):
https://docs.google.com/file/d/0BzCFBBNdXagdcEMybkdBME5iUE0/edit
After that flash TWRP 2.7.1.1 or philz and format all you have to try one of this recoverys should work.
Next push or sideload a ROM via adb I recommend you one them:
http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921
You can decide what you want rooted or not it doesn´t matter.
After installing with succsess try to reboot that´s it.
greets

I encountered a similar issue when playing around with returning my device to stock. I flashed stock recovery, then re-locked my bootloader. What is the downloading screen you're seeing? Is it the stock recovery screen?
To fix, i had to change CID back to stock (for me that was, CWS__001)
Unlock bootloader again, using HTC unlock.bin (unlock.bin wouldn't work when i was on super cid)
Flash custom recovery TWRP 2.6.3.0 (I'm not sure if 2.7.1.1 works with the old partition layout, so i used this version until i had upgraded to hboot 2.22, then I flashed 2.7.1.1. This may be an unnecessary step, but it always worked for me)
Once twrp was working again...
Flash stock hboot 2.22 found in the dev section
Flash TWRP 2.7.1.1 (again, might be an unnecessary step)
Boot to recovery
From TWRP, adb push the sense 6 rom i wanted to flash (IC 3.07 in my case)
After the push completed, flash ROM and reboot and all was good
As you can see, the steps i took require that fastboot and adb drivers work flawlessly, especially when pushing ROM to the device using abd.
If any of this seems unfamiliar, then don't do these steps. Again, this is just what i did when i flashed stock recovery and re-locked bootloader with a ROM that wouldn't boot.

jollywhitefoot said:
I encountered a similar issue when playing around with returning my device to stock. I flashed stock recovery, then re-locked my bootloader. What is the downloading screen you're seeing? Is it the stock recovery screen?
To fix, i had to change CID back to stock (for me that was, CWS__001)
Unlock bootloader again, using HTC unlock.bin (unlock.bin wouldn't work when i was on super cid)
Flash custom recovery TWRP 2.6.3.0 (I'm not sure if 2.7.1.1 works with the old partition layout, so i used this version until i had upgraded to hboot 2.22, then I flashed 2.7.1.1. This may be an unnecessary step, but it always worked for me)
Once twrp was working again...
Flash stock hboot 2.22 found in the dev section
Flash TWRP 2.7.1.1 (again, might be an unnecessary step)
Boot to recovery
From TWRP, adb push the sense 6 rom i wanted to flash (IC 3.07 in my case)
After the push completed, flash ROM and reboot and all was good
As you can see, the steps i took require that fastboot and adb drivers work flawlessly, especially when pushing ROM to the device using abd.
If any of this seems unfamiliar, then don't do these steps. Again, this is just what i did when i flashed stock recovery and re-locked bootloader with a ROM that wouldn't boot.
Click to expand...
Click to collapse
I cant unlock my bootloader as its relocked and fails, I cant install TWRP either

CoolAndroid1 said:
I cant unlock my bootloader as its relocked and fails, I cant install TWRP either
Click to expand...
Click to collapse
Did you get fastboot working yet? Does "fastboot devices" show your device? You can't do anything until fastboot works...but I imagine it worked at some point, since you unlocked and re-locked your device.
You can't install recovery because your bootloader is locked. And you can't unlock your bootloader until you change your CID back to whatever it was when you created the unlock.bin file on the HTC website.
Are you getting this error when you attempt to unlock?
FAILED (remote: unlock token check failed)

jollywhitefoot said:
Did you get fastboot working yet? Does "fastboot devices" show your device? You can't do anything until fastboot works...but I imagine it worked at some point, since you unlocked and re-locked your device.
You can't install recovery because your bootloader is locked. And you can't unlock your bootloader until you change your CID back to whatever it was when you created the unlock.bin file on the HTC website.
Are you getting this error when you attempt to unlock?
FAILED (remote: unlock token check failed)
Click to expand...
Click to collapse
Hello,
I did have the error code above but i used FUU to flash back to stock and all is fine now!!

CoolAndroid1 said:
Hello,
I did have the error code above but i used FUU to flash back to stock and all is fine now!!
Click to expand...
Click to collapse
Cool. Did you use fuu from here?
http://forum.xda-developers.com/showthread.php?t=2659109

jollywhitefoot said:
Cool. Did you use fuu from here?
http://forum.xda-developers.com/showthread.php?t=2659109
Click to expand...
Click to collapse
Yep! Windows 8 sucks with drivers and didn't work so had to switch to a different laptop!

CoolAndroid1 said:
Yep! Windows 8 sucks with drivers and didn't work so had to switch to a different laptop!
Click to expand...
Click to collapse
That's what i had to do when i first tried to root my phone. I was on Windows 7, but it was an old install and had all kinds of software on it that might have been preventing usb from working (iTunes, HTC Sync, some other random software, etc.) Sometimes, I would even have trouble connecting an external HD!
I ended up installing a clean copy of XP on an old computer that i now use strictly for flashing stuff to my phone.

New problem
I have 4.3 on my HTC now and have received an update for 4.4.2, however when I try this it goes a quarter of the way then comes up with a red triangle and exclamation point. The device is still rooted somehow. Can you help me update?

CoolAndroid1 said:
New problem
I have 4.3 on my HTC now and have received an update for 4.4.2, however when I try this it goes a quarter of the way then comes up with a red triangle and exclamation point. The device is still rooted somehow. Can you help me update?
Click to expand...
Click to collapse
I don't think OTA will work on unlocked/tampered device with custom recovery.I think you need to run ruu.exe if one is available for you to get 100% stock before OTA will work again.

jollywhitefoot said:
I don't think OTA will work on unlocked/tampered device with custom recovery.I think you need to run ruu.exe if one is available for you to get 100% stock before OTA will work again.
Click to expand...
Click to collapse
Hello,
I found an FUU for 4.4 Kitkat on the link you posted earlier, It does all the necessary actions with no failures and completes with a Congrats screen but the firmware is the same?

[Q] [Help] My HTC One S not booting on after rooting

Hi Everyone,
This is the first time I am playing with a mobile software.
I did the unlock bootloader as per the instructions given in htc website, and my phone status shows unlocked, but it is still S-ON.(Hboot 2.51)
I was planning to install a custom rom either CM11 or MIUI5.
After reading many threads in xda as well as in other sites, I tried to do a S-OFF to install a custom ROM.
I tried Rumrummer, Moonshine and firewater, but nothing has made my mobile as S-OFF.
I tried to restore back to the original stock rom, and followed the process in htconeforum(how-unbrick-restore-htc-one-s-stock-relocked)
So, I tried to do an oem lock and it got relocked.
Now, I tried to do an RUU, and it didn't work with data transfer error.
Only Hboot comes on my phone with the below details
***Tampered***
***Relocked***
My Phone doesn't start now; tried pushing lot of CWM and TRWM recoveries, it got stuck in sending recovery for long time, and i exit.
Can anyone please help me and let me know, how can i restore back to htc rom or go forward and install custom rom.
Thanks,
Deepak

deepak_raja20 said:
Hi Everyone,
This is the first time I am playing with a mobile software.
I did the unlock bootloader as per the instructions given in htc website, and my phone status shows unlocked, but it is still S-ON.(Hboot 2.51)
I was planning to install a custom rom either CM11 or MIUI5.
After reading many threads in xda as well as in other sites, I tried to do a S-OFF to install a custom ROM.
I tried Rumrummer, Moonshine and firewater, but nothing has made my mobile as S-OFF.
I tried to restore back to the original stock rom, and followed the process in htconeforum(how-unbrick-restore-htc-one-s-stock-relocked)
So, I tried to do an oem lock and it got relocked.
Now, I tried to do an RUU, and it didn't work with data transfer error.
Only Hboot comes on my phone with the below details
***Tampered***
***Relocked***
My Phone doesn't start now; tried pushing lot of CWM and TRWM recoveries, it got stuck in sending recovery for long time, and i exit.
Can anyone please help me and let me know, how can i restore back to htc rom or go forward and install custom rom.
Thanks,
Deepak
Click to expand...
Click to collapse
Well i got S-OFF with Rumrummer but i got it till my 7th try. you should keep trying with it

Stuck in sending recovery/sending zip flash
Some how , I managed to push CWM recovery to my phone.
But when I select install from zip, it says "Error mounting SDCard".
I tried the fastboot oem lock using all in one tool kit and now it says Tampered, Relocked.
So, i am trying to run factory RUU exe , it stuck at sending recovery.
I tried to push the .zip factory RUU, and it says sending and stuck there.
Even I tried the adb sideload, it says data transfer failed.
Looks like all the data on the SD card(in my case internal storage) is gone during erase and I don't have any flash zips on the device and I am not able to send any flash zips to the device.
The drivers are installed correctly, and my HBoot 2.15 says fastboot usb when in bootloader, but when i type adb devices, it gives no device.
Can some one please help me in getting my phone back.
Thanks,
Deepak

deepak_raja20 said:
Some how , I managed to push CWM recovery to my phone.
But when I select install from zip, it says "Error mounting SDCard".
I tried the fastboot oem lock using all in one tool kit and now it says Tampered, Relocked.
So, i am trying to run factory RUU exe , it stuck at sending recovery.
I tried to push the .zip factory RUU, and it says sending and stuck there.
Even I tried the adb sideload, it says data transfer failed.
Looks like all the data on the SD card(in my case internal storage) is gone during erase and I don't have any flash zips on the device and I am not able to send any flash zips to the device.
The drivers are installed correctly, and my HBoot 2.15 says fastboot usb when in bootloader, but when i type adb devices, it gives no device.
Can some one please help me in getting my phone back.
Thanks,
Deepak
Click to expand...
Click to collapse
I suggest you get the OTG USB cable. Load the ROM on a Flash USB and then use TWRP to install the ROM (Remember to mount the OTG in TWRP) Check Amazon, it only cost less than $3. I've never push the ROM to the phone. Saves a lot of time when you have multiple phones.