Database Info

[Q] Bricked? By trying to get s-on

Dear xda-community,
as said in the title i dont know if i bricked my device by trying to get s-on again.
At first i read some threads here about getting s-on again and revert to stock.
I was s-off by revelutionary and flashed the ENG-hboot a few days ago (0.98.2000). After that i flashed the stock 1.47 rom and was trying to get s-on and stock again with the 1.47 RUU. I read that if i have the ENG-hboot i can run the RUU and then i get back to stock and s-on. But after i was running the RUU, i get to the bootloader again (on the phone). In the header stands now "*** Security Warning ***" and i'm s-on again like i want it with hboot 0.98.0002.
But the problem is that i cant get out of the bootloader, i can only acsses fastboot and the bootloader. If i click 'recovery', 'reboot' or anything else it only restarts the bootloader. I cant even turn the phone off, only with pulling the battery :/
So i'm stucked in the hboot 0.98.0002 with s-on and i dont know what i can do now or if i bricked my desire s permanently
Can anyone help me please?

are you sure that you have used the right RUU?

amidabuddha said:
are you sure that you have used the right RUU?
Click to expand...
Click to collapse
yes, i used the htc_saga_europe... 1.47 and im on a unbranded phone, so this is the right, isnt it?

Jahai said:
yes, i used the htc_saga_europe... 1.47 and im on a unbranded phone, so this is the right, isnt it?
Click to expand...
Click to collapse
It should be if you bought it in Europe. What happens when you try the RUU again? You should do this when "FASTBOOT USB" is written on your phone screen.

amidabuddha said:
It should be if you bought it in Europe. What happens when you try the RUU again?
Click to expand...
Click to collapse
yes, i bought and use it in germany. if i try it again it get aborted after receiving the information from the phone and tells me something about a error 140: bootloader error and in the manuel isnt an entry for error 140 :S

Jahai said:
yes, i bought and use it in germany. if i try it again it get aborted after receiving the information from the phone and tells me something about a error 140: bootloader error and in the manuel isnt an entry for error 140 :S
Click to expand...
Click to collapse
Ok there is what you can do:
run RUU without a connected phone. Let the screen open. Go to WIndows Explorer, C drive and type in the search box : rom.zip. When you find it copy it to another place and close the RUU window.
Then extract from the rom.zip these images: system.img, boot_signed.img, recovery_signed.img
If you do not have fastboot command use the Guide in my signature. Then in cmd on your PC with phone in "fastboot usb" mode type:
Code:
fastboot flash system {path to the file}\system.img
fastboot flash boot {path to the file}\boot_signed.img
fastboot flash recovery {path to the file}\recovery_signed.img
where {patho to the file}\ should be replaced with the the actual path to the file from your Windows Explorer (like C:\android\images)
then, if the flashing is successful try to reboot to OS (wait several minutes on the white screen it can take some time to load)
This solution is taken from here, credits to degit

amidabuddha said:
Ok there is what you can do:
run RUU without a connected phone. Let the screen open. Go to WIndows Explorer, C drive and type in the search box : rom.zip. When you find it copy it to another place and close the RUU window.
Then extract from the rom.zip these images: system.img, boot_signed.img, recovery_signed.img
If you do not have fastboot command use the Guide in my signature. Then in cmd on your PC with phone in "fastboot usb" mode type:
Code:
fastboot flash system {path to the file}\system.img
fastboot flash boot {path to the file}\boot_signed.img
fastboot flash recovery {path to the file}\recovery_signed.img
where {patho to the file}\ should be replaced with the the actual path to the file from your Windows Explorer (like C:\android\images)
then, if the flashing is successful try to reboot to OS (wait several minutes on the white screen it can take some time to load)
This solution is taken from here, credits to degit
Click to expand...
Click to collapse
thank you for your help!
i will try that and report back in a few minutes

hm
i cant get it to work in this way :/
if i write fastboot flash system C:\android-tools\system.img
it tells me:
"sending 'system' (571388 KB)...
OKAY [93.130s]
writing 'system'...
(bootloader) signature cheking...
FAILED (remote: signature verify fail)
finished. total time: 166.095s"
its the same with boot_signed.img and recovery_signed.img

if i try fastboot getvar version-main i get : 11.10.401.4
think there is a typo, shouldnt it be 2.10.401.4? could it be this and if yes how could i change it?

So you problem maybe sounds the same, but it is not.
Try
Code:
fastboot oem rebootRUU
Your phone will reboot to a black screen with silver HTC logo. Then run the RUU.
Other options is to go to the repair centre and tell them that this happened during OTA update.
Sent from my HTC Desire S using Tapatalk

Jahai said:
if i try fastboot getvar version-main i get : 11.10.401.4
think there is a typo, shouldnt it be 2.10.401.4? could it be this and if yes how could i change it?
Click to expand...
Click to collapse
Hmm that's new. Have you flashed a new radio recently? Anyway try the latest RUU 2.10.401.8.
Sent from my HTC Desire S using Tapatalk

amidabuddha said:
Hmm that's new. Have you flashed a new radio recently? Anyway try the latest RUU 2.10.401.8.
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
will try it with that. since now i tried it until 2.10.401.4
Edit: it took me ages to download that ruu from filefacrtory :/

i got the same error 140 with the last 2.10.401.8 RUU
looks like it is stucked in that bootloader for ever

Jahai said:
i got the same error 140 with the last 2.10.401.8 RUU
looks like it is stucked in that bootloader for ever
Click to expand...
Click to collapse
Go to repair center and say that the OTA update did this (it is the same as RUU) They should repair it for free
Sent from my HTC Desire S using Tapatalk

maybe there is any way to get s-off from fastboot or bootloader?

got to new hboot with this instruction: http://forum.xda-developers.com/showpost.php?p=20850548&postcount=22
managed to get the unlocktoken from htcdev but if i flash it everything themes fine, but i cant choose the option yes (unlock bootloader).
if i choose "no" and press the power button it reboots like it should but if i choose "yes" and press the power button nothing happens. i can still choose between the options but nothing happens :/
anyone know how i can get it working to unlock this bootloader and flash a custom recovery?

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] 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.

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)

Question [Question] Unroot + Relock Bootloader?

Hi,
I have an ROG Phone 5 that I unlocked and rooted using https://forum.xda-developers.com/t/asus-rog-phone-5-unlock-bootloader-and-root-guide.4261151/
I've realized I'm in a little bit over my head and I want to go completely back to a fresh start as if I'd just gotten the phone etc. I uninstalled Magisk but I don't know how to go about restoring the phone back to factory and relocking the bootloader. I know that re-locking the bootloader means I can't unlock it again and I'm okay with that, I just want to start fresh.
Let me know if you need any extra information.
Thanks!

Flash a stock boot image or install Magisk and use the restore include in that before deleting it again. After that, there is a fastboot command to lock the bootloader. I can't remember it off the top of my head, but the fastboot commands thread should help.

Isn't ASUS a special command?
It depends on your local
Only the Chinese version and the WW version have RAW files to be reinstalled.
Depending on your local, you can't restore it unless you create a raw file yourself.
It is presumed that local is different because the command does not pass.

twistedumbrella said:
Flash a stock boot image or install Magisk and use the restore include in that before deleting it again. After that, there is a fastboot command to lock the bootloader. I can't remember it off the top of my head, but the fastboot commands thread should help.
Click to expand...
Click to collapse
I flashed the stock rom but I can't figure out how to lock the bootloader again. I've tried;
fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot oem asus-lock
FAILED (remote: 'Command not supported in default implementation')
fastboot oem lock
FAILED (remote: 'Command not supported in default implementation')
fastboot oem asus-csc_lk
FAILED (remote: 'Command not supported in default implementation')
Any ideas?

Just in case you didn't know: once you lock the bootloader you cannot unlock it anymore. If there is no advantage (and I don't know any real good advantage, especially when you want to sell it) you should not do that.

EliseBelle said:
I flashed the stock rom but I can't figure out how to lock the bootloader again. I've tried;
fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot oem asus-lock
FAILED (remote: 'Command not supported in default implementation')
fastboot oem lock
FAILED (remote: 'Command not supported in default implementation')
fastboot oem asus-csc_lk
FAILED (remote: 'Command not supported in default implementation')
Any ideas?
Click to expand...
Click to collapse
If none of those work, then I have no idea.
Anubarak16 said:
Just in case you didn't know: once you lock the bootloader you cannot unlock it anymore. If there is no advantage (and I don't know any real good advantage, especially when you want to sell it) you should not do that.
Click to expand...
Click to collapse
EliseBelle said:
I know that re-locking the bootloader means I can't unlock it again and I'm okay with that, I just want to start fresh.
Click to expand...
Click to collapse

Gosh, for whatever reason I totally overlooked that
Let's pretend it never happened

Anubarak16 said:
Gosh, for whatever reason I totally overlooked that
Let's pretend it never happened
Click to expand...
Click to collapse
I agree, though. The nag screen and manual updates are a small price for being able to restore from home. Someone may even come up with a way to fix OTA eventually.

EliseBelle said:
I flashed the stock rom but I can't figure out how to lock the bootloader again. I've tried;
fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot oem asus-lock
FAILED (remote: 'Command not supported in default implementation')
fastboot oem lock
FAILED (remote: 'Command not supported in default implementation')
fastboot oem asus-csc_lk
FAILED (remote: 'Command not supported in default implementation')
Any ideas?
Click to expand...
Click to collapse
How did you enter Fastboot mode? Volume up + Power or through the stock recovery menu?

I have the same problem. If I enter Fastboot from TWRP, the "default implementation" error happens.
If I enter FastBoot mode by Volume Up+Power, the Tool does not recognize my device, so the command waits for a device...
Is it caused by configuration of the Tool? Or drivers? Please halp!

Hectorim said:
I have the same problem. If I enter Fastboot from TWRP, the "default implementation" error happens.
If I enter FastBoot mode by Volume Up+Power, the Tool does not recognize my device, so the command waits for a device...
Is it caused by configuration of the Tool? Or drivers? Please halp!
Click to expand...
Click to collapse
There is no TWRP for this device, so that is probably part of it.
It also sounds like you don't have drivers and / or fastboot installed properly.

So lemme get this straight...
When I boot into FastBoot, either by VolumeUp or by Tool-all-in-one, the phone SHOULD be picked up by the tool/PC? I mean when the phone is on the screen with "Fastboot Mode" in red lettering.
If it's a driver fault, how can I wipe them off my PC to try to start anew? Is there a step-by-step guide for dummies?

Hectorim said:
So lemme get this straight...
When I boot into FastBoot, either by VolumeUp or by Tool-all-in-one, the phone SHOULD be picked up by the tool/PC? I mean when the phone is on the screen with "Fastboot Mode" in red lettering.
If it's a driver fault, how can I wipe them off my PC to try to start anew? Is there a step-by-step guide for dummies?
Click to expand...
Click to collapse
I'm sure you could google fastboot and find 50.

Turns out my device isn't visible because Windows doesn't recognize it properly - it sees it as "Android" with an exclamation mark.
I have installed fastboot and adb drivers, Asus ROG specific USB drivers manually (as legacy), so I have no idea why it isn't recognized.

Hectorim said:
Turns out my device isn't visible because Windows doesn't recognize it properly - it sees it as "Android" with an exclamation mark.
I have installed fastboot and adb drivers, Asus ROG specific USB drivers manually (as legacy), so I have no idea why it isn't recognized.
Click to expand...
Click to collapse
For me the solution is to connect the device to the pc, boot into fastboot, then do the manual steps to install the adb drivers. If I install the drivers manually without the device already in fastboot, it will not recognize the device properly.
Good luck!

For what reason u want to re-roll from rooted phone?

aldomuwsa said:
For what reason u want to re-roll from rooted phone?
Click to expand...
Click to collapse
Because you didn't get an SSR.
Jokes aside, it's only really for warranty repair or in hopes it will enable OTA. You really shouldn't do it just for fun, though.

twistedumbrella said:
Because you didn't get an SSR.
Jokes aside, it's only really for warranty repair or in hopes it will enable OTA. You really shouldn't do it just for fun, though.
Click to expand...
Click to collapse
What kind u get from rooted phone by the way? Special hacking tools? Mod SSR Generate, or what?
Sorry for my newbie questions

aldomuwsa said:
What kind u get from rooted phone by the way? Special hacking tools? Mod SSR Generate, or what?
Sorry for my newbie questions
Click to expand...
Click to collapse
If its what u get, surely im gonna root my phone right now

aldomuwsa said:
What kind u get from rooted phone by the way? Special hacking tools? Mod SSR Generate, or what?
Sorry for my newbie questions
Click to expand...
Click to collapse
For the typical user, root is unnecessary for day to day life.
The biggest reasons people used to root were for ad blocking, sound enhancement, mobile hotspot functionality, and to modify the build.prop with values for another device (to bypass restrictions).
Of the previously mentioned uses, modifying the build.prop still requires root. Sound enhancement is a bit obsolete and mobile hotspot functionality or ad blocking can be achieved without root.
Unlike years ago, rooting is less of a "do not update or you miss the chance" process if you aren't using a Samsung. You don't have to jump into it if you don't have a reason and can always do it later if you find one.