Database Info

Cannot apply RUU

I have a DS with S-off running hboot 6.x. I applied the OTA (2.3.5 with Sense 3) and after the installation, I got stuck on the white screen with HTC logo even after waiting for more than 2 hours.
Running recovery never did anything to fix it. So I managed to run fastboot and updated it with the RUU (Asia 1.47.x version) through USB. I got my phone back and retried the OTA. Still got stuck at the white screen with HTC logo. I repeated this for about 5x with no luck.
Having the white screen with HTC logo, I decided to downgrade hboot. I got a version 0.98.x with S-on now. My problem is that I am still stuck at the white screen with HTC logo and my biggest problem is that whenever I try to use the RUU (same asian version), it gives me a signature error message. I couldn't install the RUU anymore nor I can boot my phone. What should I do?

gjj1056 said:
I have a DS with S-off running hboot 6.x. I applied the OTA (2.3.5 with Sense 3) and after the installation, I got stuck on the white screen with HTC logo even after waiting for more than 2 hours.
Running recovery never did anything to fix it. So I managed to run fastboot and updated it with the RUU (Asia 1.47.x version) through USB. I got my phone back and retried the OTA. Still got stuck at the white screen with HTC logo. I repeated this for about 5x with no luck.
Having the white screen with HTC logo, I decided to downgrade hboot. I got a version 0.98.x with S-on now. My problem is that I am still stuck at the white screen with HTC logo and my biggest problem is that whenever I try to use the RUU (same asian version), it gives me a signature error message. I couldn't install the RUU anymore nor I can boot my phone. What should I do?
Click to expand...
Click to collapse
In order to install a OTA, you must replace the custom recovery with the stock HTC recovery.

tpbklake said:
In order to install a OTA, you must replace the custom recovery with the stock HTC recovery.
Click to expand...
Click to collapse
Thanks for your quick response. How exactly can I replace it with the stock HTC recovery? Can I do it even if my phone is stuck at the white screen with HTC logo?

gjj1056 said:
Thanks for your quick response. How exactly can I replace it with the stock HTC recovery? Can I do it even if my phone is stuck at the white screen with HTC logo?
Click to expand...
Click to collapse
Can you boot to the HBOOT screen? If so then you should be able to get into fastboot mode and flash a recovery.img file extracted from an official RUU/ROM.zip file using the command:
fastboot flash recovery recovery.img

tpbklake said:
Can you boot to the HBOOT screen? If so then you should be able to get into fastboot mode and flash a recovery.img file extracted from an official RUU/ROM.zip file using the command:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Yes, I can boot to hboot. Where can I get the recovery.img? The official RUU I have is an .exe file, and if I extract it, couldn't find the recovery.img file inside.
If I have the recovery.img, how can I install it?
Sorry, kinda newbie. Thanks for your quick response..

gjj1056 said:
Yes, I can boot to hboot. Where can I get the recovery.img? The official RUU I have is an .exe file, and if I extract it, couldn't find the recovery.img file inside.
If I have the recovery.img, how can I install it?
Sorry, kinda newbie. Thanks for your quick response..
Click to expand...
Click to collapse
Search for how to extract the ROM.zip from a RUU. There is plenty of information. Once you get the ROM.zip file you will find the recovery.img in it.
Then you would flash it just like you did for CWM.

tpbklake said:
Search for how to extract the ROM.zip from a RUU. There is plenty of information. Once you get the ROM.zip file you will find the recovery.img in it.
Then you would flash it just like you did for CWM.
Click to expand...
Click to collapse
What's CWM? Do I need to copy the recovery.img in my SD card? Or just leave the recovery.img in my PC and let it run through USB?
By the way, why do you think that I got stuck on the white screen with HTC logo after the 2.3.5 OTA update in the first place?

gjj1056 said:
What's CWM? Do I need to copy the recovery.img in my SD card? Or just leave the recovery.img in my PC and let it run through USB?
By the way, why do you think that I got stuck on the white screen with HTC logo after the 2.3.5 OTA update in the first place?
Click to expand...
Click to collapse
The OTA didn't complete because you had S-Off using Revolutionary. A OTA can only be applied to a phone that has the original HBOOT and recovery image in place. The Revolutionary S-Off process replaced the original HBOOT with a modified one and the recovery image with ClockworkMod (CWM).
You leave the recovery.img file on your PC and boot into Fastboot mode and then enter the following command:
Fastboot flash recovery recovery.img

bro! i have exactly same problem here!
i can't install ruu as well as cannot connect to usb
so i have the same question is how to extract rom.zip
and wht's the whole flow doing this?

tpbklake said:
The OTA didn't complete because you had S-Off using Revolutionary. A OTA can only be applied to a phone that has the original HBOOT and recovery image in place. The Revolutionary S-Off process replaced the original HBOOT with a modified one and the recovery image with ClockworkMod (CWM).
You leave the recovery.img file on your PC and boot into Fastboot mode and then enter the following command:
Fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I will try it since my phone is not here with me yet, it's with the technician. Thanks a lot! I will update you the status when I try to get it.
Anyway, in my situation (phone won't update with .exe RUU file), do you think it will successfully flash recovery..img through fastboot recovery?

cckwan said:
bro! i have exactly same problem here!
i can't install ruu as well as cannot connect to usb
so i have the same question is how to extract rom.zip
and wht's the whole flow doing this?
Click to expand...
Click to collapse
To get the ROM.zip:
1. Run RUU (.exe)
2. Don't continue with the RUU, just have it running, then go to windows explorer and search for ROM.ZIP in all the folders in your PC.
3. It would appear somewhere in a temporary folder, copy the ROM.zip file found.
4. Paste it in any folder.
5. Use Winzip or any compression program to extract the ROM.zip to a folder.
6. You will find the recovery.img there.

tpbklake said:
Can you boot to the HBOOT screen? If so then you should be able to get into fastboot mode and flash a recovery.img file extracted from an official RUU/ROM.zip file using the command:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
When I do this... it says:
FAILED <remote: signature verify fail>
How can I fix this?

gjj1056 said:
When I do this... it says:
FAILED <remote: signature verify fail>
How can I fix this?
Click to expand...
Click to collapse
want to know this too, have the same problem

Anyone? Any solution?

Please help

Hi,
I have same issue - can anyone help?

Restore to factory

I am trying to reinstall the RUU but I believe bc I have CWM installed, it won't work. I tried different things and I am stuck. I know my PC recognizes the device b/c adb devices find the device. Is there a way I can send an image thru fastboot or something to the phone that would install the RUU image and restore my phone to stock form factor? Or is there anything else that I can try?
Thank you.

crazycray said:
I am trying to reinstall the RUU but I believe bc I have CWM installed, it won't work. I tried different things and I am stuck. I know my PC recognizes the device b/c adb devices find the device. Is there a way I can send an image thru fastboot or something to the phone that would install the RUU image and restore my phone to stock form factor? Or is there anything else that I can try?
Thank you.
Click to expand...
Click to collapse
Why not search for a PG58IMG?
Sent from my Sensation using Tapatalk 2

matt95 said:
Why not search for a PG58IMG?
Sent from my Sensation using Tapatalk 2
Click to expand...
Click to collapse
Okay, how do I do that after I find it?
push adb PG58IMG? and where can I find the default one? Thank you

Also, I think when I do a hard factory reset w/ volume down+power, it just loads up an older ROM. Any idea why?

PG58IMG.zip
crazycray said:
Also, I think when I do a hard factory reset w/ volume down+power, it just loads up an older ROM. Any idea why?
Click to expand...
Click to collapse
Is your phone rooted ?
If you put a PG58IMG.zip (make sure it's the right one for your phone), in your SD card, it will automatically flash it in fastboot, before doing enything else.
Just make sure you rename it (or delete it) after the procedure is done, otherwise everytime you go to fastboot it will automatically flash it again, and again...

Yes, it used to be rooted. It might not be anymore..
I believe the PG85IMG.zip file that I have on my microSD is the file for CWM? I can't remember if I replaced it w/ the original after I completed the root.
I can't seem to find the original PG85IMG.zip file anywhere on xda...

Finding your PG85IMG.zip + RUU
Ok, based on your CID, find the right PG85IMG.zip for your phone here
http://forum.xda-developers.com/showthread.php?t=1459767
Then, *if* you have SuperCID, you can download the right RUU from here, and intall the .exe
http://www.filefactory.com/f/c87a2330449af512/

codebr4k3r said:
Ok, based on your CID, find the right PG85IMG.zip for your phone here
http://forum.xda-developers.com/showthread.php?t=1459767
Then, *if* you have SuperCID, you can download the right RUU from here, and intall the .exe
http://www.filefactory.com/f/c87a2330449af512/
Click to expand...
Click to collapse
Okay. I will see if this works. Last time I was trying some fastboot or adb commands, it said "waiting for device" and nothing happened. Any idea what might be causing that?

"waiting for device"
crazycray said:
Okay. I will see if this works. Last time I was trying some fastboot or adb commands, it said "waiting for device" and nothing happened. Any idea what might be causing that?
Click to expand...
Click to collapse
That usually has to do with outdated drivers. Make sure you have the latest HTC Sync installed on your computer. That will also provide the latest drivers for your device.
Then sync your phone with HTC Sync (so that HTC Sync detects it).
Open the terminal, and go to the directory where you use adb.
Then try the adb commands
SuperCID commands in case it's not SuperCID:
(You will need it in case you get a "InvalidID" error while installing a RUU.)
>> adb reboot-bootloader
>> fastboot oem writecid 11111111
>> fastboot reboot-bootloader (Wait for it to reboot)
>> fastboot getvar cid (it should confirm your CID is 11111111)
>> fastboot reboot"

codebr4k3r said:
That usually has to do with outdated drivers. Make sure you have the latest HTC Sync installed on your computer. That will also provide the latest drivers for your device.
Then sync your phone with HTC Sync (so that HTC Sync detects it).
Open the terminal, and go to the directory where you use adb.
Then try the adb commands
SuperCID commands in case it's not SuperCID:
(You will need it in case you get a "InvalidID" error while installing a RUU.)
>> adb reboot-bootloader
>> fastboot oem writecid 11111111
>> fastboot reboot-bootloader (Wait for it to reboot)
>> fastboot getvar cid (it should confirm your CID is 11111111)
>> fastboot reboot"
Click to expand...
Click to collapse
Dude, thanks so much for all the help. I am at work but will try all this stuff out when I get home from work. I hope this works.
Does SuperCID get removed after installing the RUU? I'm certain I did not do that step when I first followed the guide b/c it was kind of over my head at the time

crazycray said:
Dude, thanks so much for all the help. I am at work but will try all this stuff out when I get home from work. I hope this works.
Does SuperCID get removed after installing the RUU? I'm certain I did not do that step when I first followed the guide b/c it was kind of over my head at the time
Click to expand...
Click to collapse
No worries, anytime
No, you SuperCID once, then it stays... till you throw your phone off the window, or , i don't know But it stays

codebr4k3r said:
No worries, anytime
No, you SuperCID once, then it stays... till you throw your phone off the window, or , i don't know But it stays
Click to expand...
Click to collapse
Does that void warranty?

crazycray said:
Does that void warranty?
Click to expand...
Click to collapse
Hmm, i guess no, because you can restore your original CID with the command:
>> fastboot oem writecid xxxxxxxx
(where xxxxxxxx will be your original CID)
Just make sure you make a note of your original CID, before making the whole procedure. Get it again with:
>> fastboot getvar cid

codebr4k3r said:
That usually has to do with outdated drivers. Make sure you have the latest HTC Sync installed on your computer. That will also provide the latest drivers for your device.
Then sync your phone with HTC Sync (so that HTC Sync detects it).
Open the terminal, and go to the directory where you use adb.
Then try the adb commands
SuperCID commands in case it's not SuperCID:
(You will need it in case you get a "InvalidID" error while installing a RUU.)
>> adb reboot-bootloader
>> fastboot oem writecid 11111111
>> fastboot reboot-bootloader (Wait for it to reboot)
>> fastboot getvar cid (it should confirm your CID is 11111111)
>> fastboot reboot"
Click to expand...
Click to collapse
So, I still got the waiting for device message. I was able to writecid 11111111 and i believe it was successful, but when i type the command again, it doesn't work and i get the waiting for device message. I am not able to get HTC Sync b/c I have a non sense ROM installed. Furthermore, I cannot get the RUU to reset the phone. Just says "Rebooting to Bootloader" and then I get an Unknown Error and it says ROM Update Utility cannot update my phone.

crazycray said:
So, I still got the waiting for device message. I was able to writecid 11111111 and i believe it was successful, but when i type the command again, it doesn't work and i get the waiting for device message. I am not able to get HTC Sync b/c I have a non sense ROM installed. Furthermore, I cannot get the RUU to reset the phone. Just says "Rebooting to Bootloader" and then I get an Unknown Error and it says ROM Update Utility cannot update my phone.
Click to expand...
Click to collapse
Hmm, that's sounds confusing :$
Right, you said that command: fastboot oem writecid 11111111 , worked ?
Ok, could you tell me your HBOOT version ? (when you're in the bootloader)

[Q] Stuck in loop, can't boot recovery or normal. Please, help me. :(

Ok, I can boot into Hboot, but when I choose recovery, I get stuck in a loop on the logo with the red disclaimer.(yes I cleared cache) I tried installing a rom and after that I cannot boot into ANYTHING. Just a loop. Hboot 1.14 I just want a working rom at this point. Stock is fine. But I am totally at a loss right now. Am I screwed? Thank you for your time.
I tried CM, Stock Recover, TWRP.....
HTC One X ATT
Rooted
Bricked?

Try to reflash the recovery and try again. Do you have the Evita or endeavor?
Sent from my Carbon-ize Evita using xda-developers app

Need to be more specific, but try this and for future reference
Are you unlocked? Did you fastboot flash boot boot.img (always do this when on hboot 1.14 or higher)?
Give me all the info you can about your phone. Recovery version, rom that was flashed, but failed, what did you do when flashing the rom step by step?
This should be fixable by ruuing heres a link on the basic directions
http://onexroot.com/one-x-unroot/how-to-unrootunbrick-att-one-x/
I think you can't use 2.20, you probably need a later ruu. Hope this works, but don't do this until after you have provided more info
---------- Post added at 01:28 AM ---------- Previous post was at 01:19 AM ----------
And I or someone better than me at this has given you the OK to.

Tried all of the fastboot methods
I have tried reflashing multiple times, multiple versions of TWRP. was trying to follow this youtube vid ((HD) Samsung Galaxy SIII (S3) Touchwiz for HTC One X - Cursed4Eva)
I only got to install the gapps file from the vid, then it failed to flash anything else.
**tampered**
**unlocked**

Grab version 2.3.3.0. It works just fine for me. Also when you get into recovery you need to flash the ROM and then flash the boot image.
Also if you can, open up fast boot and type "fastboot OEM getvars" and paste the results. It could be getvar if the previous does not work.
Sent from my Carbon-ize Evita using xda-developers app

wtf
Herc08 said:
Grab version 2.3.3.0. It works just fine for me. Also when you get into recovery you need to flash the ROM and then flash the boot image.
Also if you can, open up fast boot and type "fastboot OEM getvars" and paste the results. It could be getvar if the previous does not work.
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
Fastboot just displays the menu when I type that... 2048
now it says info[ERR] command error !!!
now that I see it... that tutorial I followed was for endevor.. does that mean I am fcked?
2.3 = failed

joeytortorici said:
Fastboot just displays the menu when I type that... 2048
now it says info[ERR] command error !!!
now that I see it... that tutorial I followed was for endevor.. does that mean I am fcked?
Click to expand...
Click to collapse
download twrp 2.3.3.1 or under.
Fastboot flash recovery nameofrecoverzip.zip
fastboot erase cache
Boot to recovery flash roms for evita, extract the boot.img from the rom and flash that. fastboot flash boot boot.img
Good luck.

been there.
exad said:
download twrp 2.3.3.1 or under.
Fastboot flash recovery nameofrecoverzip.zip
fastboot erase cache
Boot to recovery flash roms for evita, extract the boot.img from the rom and flash that. fastboot flash boot boot.img
Good luck.
Click to expand...
Click to collapse
What is a rom that I can use? confirmed for vita.
I can't even get into recovery.

joeytortorici said:
What is a rom that I can use? confirmed for vita.
I can't even get into recovery.
Click to expand...
Click to collapse
omg, get an iphone.
Any rom in the AT&T one xl sections. Evita is the phone we have, endeavor is the quad core one x, cross flashing has a high chance of bricking your device. Have you done any reading before risking your expensive piece of equipment?

...
exad said:
omg, get an iphone.
Any rom in the AT&T one xl sections. Evita is the phone we have, endeavor is the quad core one x, cross flashing has a high chance of bricking your device. Have you done any reading before risking your expensive piece of equipment?
Click to expand...
Click to collapse
Dude, I'm not an idiot. I am pretty tech savy. especially with linux. But i dont know what I did here... if I can get into hboot does that mean it's not bricked?

joeytortorici said:
Dude, I'm not an idiot. I am pretty tech savy. especially with linux. But i dont know what I did here... if I can get into hboot does that mean it's not bricked?
Click to expand...
Click to collapse
If you're familiar with linux, consider the stickies in this forum man pages and READ.
If your phone can make it to hboot, it's not bricked.

exad said:
If you're familiar with linux, consider the stickies in this forum man pages and READ.
If your phone can make it to hboot, it's not bricked.
Click to expand...
Click to collapse
. I HAVE READ. I joined this forum to get help. My situation is unique. I have tried everything. I just can not boot into recovery or normal os. kind of a bid deal.
I cant even use fastboot oem getvar
I get an error.

I disagree.
Download recovery check md5
Fastboot flash recovery recovery.img
Fastboot erase cache
Make sure the recovery you're downloading is for the right phone too. One xl aka Evita.
Sent from my One X using xda app-developers app

sdfsdfsdfsd
exad said:
I disagree.
Download recovery check md5
Fastboot flash recovery recovery.img
Fastboot erase cache
Make sure the recovery you're downloading is for the right phone too. One xl aka Evita.
Sent from my One X using xda app-developers app[/QUOTE
Literally done that 10 times now
Click to expand...
Click to collapse

joeytortorici said:
. I HAVE READ. I joined this forum to get help. My situation is unique. I have tried everything. I just can not boot into recovery or normal os. kind of a bid deal.
I cant even use fastboot oem getvar
I get an error.
Click to expand...
Click to collapse
First of all you should have done more research before flashing stuff on your phone. Youre lucky your phone is still alive after flashing that international rom buddy.
Second the command fastboot oem getvar is incomplete. THats why you are getting the error. Getvar must be followed by something like fastboot oem getvar cid.
So one more time.
First make sure you have plenty of battery
1 Boot into hboot.
2Select fastboot and press the power button.
3 Open fastboot in command prompt and and type "fastboot devices"
4 If it shows a serial number it is recognizing your phone. If not try different cables and ports
5 IF recognized type "fastboot flash recovery ( navigate back to your fastboot folder and drag the recovery.img into the command window. The recovery.img MUST be in the same folder as the fastboot program!!)"
6 Press enter.
7 Type "fastboot erase cache"
8 Type "fastboot reboot recovery"
If this doesn't work you have another problem. I would suggest running a ruu if your're not super cid. To check super cid boot back into fastboot mode and type "fastboot oem getvar cid" If it shows "11111111" you have super cid and cant run a ruu. If not you can run a ruu.
If the steps above did work and your're now in recovery. Then.
1 Wipe everything. Cache/dalvik cache/system/android secure/ and sdcard.
2 Mount sdcard and transfer your rom to your sd card. MAKE SURE THE ROM IS FOR THE DUAL CORE ONE XL EVITA model. For now just stick with a sense rom. If you want a suggestion I suggest you use this one for now. http://forum.xda-developers.com/showthread.php?t=2181891
3 Once transfered. Safetly unmount sdcard and flash the rom.
4 Select reboot bootloader in recovery.
5 Once in hboot select bootloader.
6 Open the rom you just flashed and copy the boot.img that is in the root of the zip to the folder where you have fastboot.
7 Type "fastboot devices" to see if the pc recognizes the phone.
8 If you see a serial number the pc recognizes your phone.
9 Type "fastboot flash boot (go back to explorer and drag the boot.img from the fastboot folder to the command window."
10 Hit enter
11 Press the vol down button and navigate to power off.
12 Hit the power button.
13 Once phone is completely off press and hold the power button till the phone comes on.
14 If it still boot loops a ruu is your only option.

fmlll
Installed HTC Sync, RUU up and running. Thanks guys. Sorry for so noob. nearly trolling.

[Q] Stuck in the red letters screen on my HTC One X

hello my friends, i need your help to fix my celphone, when i turned on the phone doesnt boot up always saty stuck in the screen with the red letters, i tried changing the kernel, i tried to install another ROM but always stuck in the same point, i wiped the cache, the system even the SD card and doesnt work,
Anyone can help me?
------Updated-----
according with some posts that i read i need to flash the RUU but i tried downloading the stock att ruu 2.20 but doesnt reconize any phone conected exists a way to flash directly over the TWRP?or maybe i missing something and because of that doesnt detect my celphone?

Reboot the phone and hold volume down while it's rebooting, this will take you to the bootloader, from there you can enter recovery and restore a backup or flash ROM.
What ROM were you on and what kernel did you flash?
Sent from my Evita

timmaaa said:
Reboot the phone and hold volume down while it's rebooting, this will take you to the bootloader, from there you can enter recovery and restore a backup or flash ROM.
What ROM were you on and what kernel did you flash?
Sent from my Evita
Click to expand...
Click to collapse
thanks for your help, i tried to flash the JB 4.22 plus sense 5 but i think my problem is the RUU because even if i flash the Rom still stuck in the same point when i tried to turn on the celphone, do you know how i can flash the RUU?

What are your bootloader details please, just the first five lines.
Sent from my Evita

timmaaa said:
What are your bootloader details please, just the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
Tampered
Unlocked
Evita put ship s-on RL
hboot- 1.14.0002
Radio-0.19as.32.09.11_2
openDSP-v29.1.0.45.0622
eMMC-boot

You're s-on so did you flash the boot.img via fastboot after flashing the ROM?
Sent from my Evita

timmaaa said:
You're s-on so did you flash the boot.img via fastboot after flashing the ROM?
Sent from my Evita
Click to expand...
Click to collapse
eehm nop, so how i do that? from where i can get the boot.img and how can flash via fastboot?
Sorry for my noob questions

The boot.img can be found in the root of the ROM zip, unzip it on your pc and you'll see it straight away. You then need to copy the boot.img into the folder where adb and fastboot are. Then open a command prompt from within that folder (shift + right click anywhere in that folder, select open command prompt here), put your phone into bootloader mode and connect it to the pc, then issue this command in the command prompt:
Code:
fastboot devices
It should return your device serial number, this confirms that you're connected properly. If it doesn't return the serial number you need to work out why. If it does return the serial number you can issue this command:
Code:
fastboot flash boot boot.img
Now you can enter recovery on your phone, flash the ROM, and reboot the phone. Now it should boot up.
Sent from my Evita

timmaaa said:
The boot.img can be found in the root of the ROM zip, unzip it on your pc and you'll see it straight away. You then need to copy the boot.img into the folder where adb and fastboot are. Then open a command prompt from within that folder (shift + right click anywhere in that folder, select open command prompt here), put your phone into bootloader mode and connect it to the pc, then issue this command in the command prompt:
Code:
fastboot devices
It should return your device serial number, this confirms that you're connected properly. If it doesn't return the serial number you need to work out why. If it does return the serial number you can issue this command:
Code:
fastboot flash boot boot.img
Now you can enter recovery on your phone, flash the ROM, and reboot the phone. Now it should boot up.
Sent from my Evita
Click to expand...
Click to collapse
Ok, let me try ill keep posted

It works !!!!!1
Thanks so much for your help now i will update the firmware with most recently one

fjej78 said:
It works !!!!!1
Thanks so much for your help now i will update the firmware with most recently one
Click to expand...
Click to collapse
Glad to see it worked
PS. If someone helps you on XDA, press the thanks button :thumbup:
Sent from my Evita

Bricked htc u11 please help!!!

Hey Guys! so recently I purchased Sunshine to S-OFF my SPRINT HTC U11. I changed the CID to unlocked version BS_US001 to flash the unlocked RUU. it kept on failing because the bootloader was unlocked. so then I typed the worst command ever "fastboot oem lock" and now my bootloader is locked, device is S ON, and the worst part is that the bootloader comes up saying that the device is corrupted and cannot be trusted. Now I cannot get into twrp, or my rom. because I changed the CID I can't use my original RUU to revert back. Moreover the android OS version in the download mode comes up as 1.28.651.3 and the unlocked RUU which could work is 1.16.617.6 . The unlocked RUU gives me an error that the android versions either missing or set to 1 and the sprint RUU gives me Invalid Customer ID error. I have access to fastboot. I need a way to change the CID back to SPCS_001. I know I should've used superCID but I panicked while doing all the steps. if anyone could give me or provide me with a way to create a sprint rom.zip which is signed and has a modified android-info.txt including the CID for my phone. I cannot unlock my bootloader as it expects bootloader unlocking to be turned on the android system which unfortunately has been factory reset due to the corruption and is no longer booting. if there is a way to S OFF via fastboot then I can recover. please help me. I have good experience with flashing roms and messing with this stuff but I was out of the android scene for 2 years until recently when I got the U11.

kunalrokz said:
Hey Guys! so recently I purchased Sunshine to S-OFF my SPRINT HTC U11. I changed the CID to unlocked version BS_US001 to flash the unlocked RUU. it kept on failing because the bootloader was unlocked. so then I typed the worst command ever "fastboot oem lock" and now my bootloader is locked, device is S ON, and the worst part is that the bootloader comes up saying that the device is corrupted and cannot be trusted. Now I cannot get into twrp, or my rom. because I changed the CID I can't use my original RUU to revert back. Moreover the android OS version in the download mode comes up as 1.28.651.3 and the unlocked RUU which could work is 1.16.617.6 . The unlocked RUU gives me an error that the android versions either missing or set to 1 and the sprint RUU gives me Invalid Customer ID error. I have access to fastboot. I need a way to change the CID back to SPCS_001. I know I should've used superCID but I panicked while doing all the steps. if anyone could give me or provide me with a way to create a sprint rom.zip which is signed and has a modified android-info.txt including the CID for my phone. I cannot unlock my bootloader as it expects bootloader unlocking to be turned on the android system which unfortunately has been factory reset due to the corruption and is no longer booting. if there is a way to S OFF via fastboot then I can recover. please help me. I have good experience with flashing roms and messing with this stuff but I was out of the android scene for 2 years until recently when I got the U11.
Click to expand...
Click to collapse
sounds like you're in a pickle....someone had a similar issue, read here
you may be able to boot into twrp via fastboot boot twrp-3.1.1-0-ocn.img while in bootloader
then you could try either erasing OS version or changing it
good luck!

OMJ said:
sounds like you're in a pickle....someone had a similar issue, read here
you may be able to boot into twrp via fastboot boot twrp-3.1.1-0-ocn.img while in bootloader
then you could try either erasing OS version or changing it
good luck!
Click to expand...
Click to collapse
Thanks I'll try it out shortly!!

kunalrokz said:
Thanks I'll try it out shortly!!
Click to expand...
Click to collapse
Maybe try to reflash the unlock token again from fastboot and get the bootloader unlocked and reflash twrp

I'm on the same boat as you... Any news?

wranglerray said:
Maybe try to reflash the unlock token again from fastboot and get the bootloader unlocked and reflash twrp
Click to expand...
Click to collapse
The unlock token wont flash gives me a permission error. I will post the exact error in a while.

OMJ said:
sounds like you're in a pickle....someone had a similar issue, read here
you may be able to boot into twrp via fastboot boot twrp-3.1.1-0-ocn.img while in bootloader
then you could try either erasing OS version or changing it
good luck!
Click to expand...
Click to collapse
I tried your recommendation but to no avail. when I boot into the bootloader and send the fastboot command it gives me error "FAILED (remote: GetVar Variable Not found)" and when I do it in download mode it says okay and gets stuck on booting... the phone itself downloads the recovery and displays flash images success (1/1) but nothing else happens.
HOWEVER after sending that command I tried the unlock bootloader command and miraculously it WORKED! I got access to recovery!! I think that being in the download mode explicitly helped the bootloader recognize the unlock token.

zopostyle said:
I'm on the same boat as you... Any news?
Click to expand...
Click to collapse
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
 @wranglerray and @OMJ thank you so much for your help

kunalrokz said:
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
Click to expand...
Click to collapse
I was able to boot to recovery only... Couldn't make any rom boot,don't know where I'm going wrong...

kunalrokz said:
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
Click to expand...
Click to collapse
Good to hear!
Cheers
Your neighbor to the south

kunalrokz said:
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
Click to expand...
Click to collapse
sweet!
zopostyle said:
I was able to boot to recovery only... Couldn't make any rom boot,don't know where I'm going wrong...
Click to expand...
Click to collapse
stock recovery or twrp? you'll need to give more specifics...

OMJ said:
sweet!
stock recovery or twrp? you'll need to give more specifics...
Click to expand...
Click to collapse
With both, I flashed twrp tried to restore a nandroid backup and it stop at the black screen with HTC and powered by android.
I've also tried with stock recovery flash a RUU from SDCard, but I receives Error 14.
What I did was change this:
​(bootloader) mid: 2PZC10000
(bootloader) cid: VODAP110
To this:
​
modelid: 2PZC50000
cidnum: BS_US001
I also tried to change the mainver from ​ 1.27.166.7 to 1.16.617.6, and without it.
RUU from SDCard or PC always give me error 14 or 8.
Oh forgot to mention, when I'm in twrp I always get a message Failed to mount /cota (Invalid Argument)

zopostyle said:
With both, I flashed twrp tried to restore a nandroid backup and it stop at the black screen with HTC and powered by android.
I've also tried with stock recovery flash a RUU from SDCard, but I receives Error 14.
What I did was change this:
​(bootloader) mid: 2PZC10000
(bootloader) cid: VODAP110
To this:
​
modelid: 2PZC50000
cidnum: BS_US001
I also tried to change the mainver from ​ 1.27.166.7 to 1.16.617.6, and without it.
RUU from SDCard or PC always give me error 14 or 8.
Oh forgot to mention, when I'm in twrp I always get a message Failed to mount /cota (Invalid Argument)
Click to expand...
Click to collapse
I would recommend flashing a custom rom. I'm going to take a wild guess and say that you successfully unlocked your bootloader. if that's the case then you just reflashed twrp on an unlocked bootloader. now because you're trying to downgrade your OS you need S OFF.
not sure about the mounting error in twrp. maybe try fastboot -w in download mode. sounds like the file system is corrupt. but once you're able to install a rom, use any custom rom and get sunshine for s off. the s off will allow you to downgrade using RUU mode. make sure you get the new htc_fastboot.exe from the temp folder of the RUU that you want to install.

kunalrokz said:
I would recommend flashing a custom rom. I'm going to take a wild guess and say that you successfully unlocked your bootloader. if that's the case then you just reflashed twrp on an unlocked bootloader. now because you're trying to downgrade your OS you need S OFF.
not sure about the mounting error in twrp. maybe try fastboot -w in download mode. sounds like the file system is corrupt. but once you're able to install a rom, use any custom rom and get sunshine for s off. the s off will allow you to downgrade using RUU mode. make sure you get the new htc_fastboot.exe from the temp folder of the RUU that you want to install.
Click to expand...
Click to collapse
Hum, OK, thanks.
Yes, my bootloader is unlocked and I can flash recovery and boot.img successfully.
I'm at work right now at night I'm gonna try that fastboot -w option.
About the custom rom I've already tried leeDroid and MaximusHD but none of then booted.

What is this?
Failed to mount '/cota' (invalid argument)

AndrzejQ said:
What is this?
Failed to mount '/cota' (invalid argument)
Click to expand...
Click to collapse
An error that I received.
I got it working already.

i have the same problem. had you worked this out ? what's the solution ?

Same issue , but i can't unlock the phone's bootloader , it gives me the message about ticking allow bootloader unlock in developer options but i can't access the OS...

Void tracer said:
Same issue , but i can't unlock the phone's bootloader , it gives me the message about ticking allow bootloader unlock in developer options but i can't access the OS...
Click to expand...
Click to collapse
Same here. It doesn't say that, but o know that's what my error messages mean because when I did this before, I forgot to tick that option in developer options. Now, since after I flashed leedroid, I haven't checked that box again, and now I can't boot. I was simply trying to relock the bootloader to get rid of that annoying message everytime it turned on, then this corrupt error pops up. Please someone lead us in the direction of the fix, even if that fix happens to be get a new phone, just so I have closure, tho I have a hard time giving up and I kinda never believed that a device can be fully "bricked," just super locked.

MSMC said:
Same here. It doesn't say that, but o know that's what my error messages mean because when I did this before, I forgot to tick that option in developer options. Now, since after I flashed leedroid, I haven't checked that box again, and now I can't boot. I was simply trying to relock the bootloader to get rid of that annoying message everytime it turned on, then this corrupt error pops up. Please someone lead us in the direction of the fix, even if that fix happens to be get a new phone, just so I have closure, tho I have a hard time giving up and I kinda never believed that a device can be fully "bricked," just super locked.
Click to expand...
Click to collapse
I can't guarantee this will work, but try the following:
Use the spreadsheet here to find the latest RUU for your phone's CID and MID.
Rename the downloaded RUU to 2PZCIMG.zip
Move 2PZCIMG.zip to the root of your external SD card. If you don't have an external SD card you'll need to get one. If using a PC make sure to format the card as exFAT.
Follow the instructions at 'https://www.the custom droid.com/how-to-restore-htc-u11-stock-firmware/#Method-1-Flashing-RUU-in-Download-Mode' to flash the RUU to your phone.
Good luck!
EDIT: I don't why but XDA forums are filtering the string c u s t o m d r o i d (w/o the spaces)