Okay so i was attempting to relock my bootloader to RUU 1.85 agian and i ran the "fastboot oem lock" and this is the cmd output:
C:\Users\kenny>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Too many links))
finished. total time: 0.936s
but now on my bootloader at the top it reads
*** Security Warning ***
is this something i should worry about??
im new to the phones with bootloaders bc none of my previous ones had them, if someone could tell me what is going on i would greatly appreciate it!!
I dont want a BRICK! :/
android4ever91 said:
Okay so i was attempting to relock my bootloader to RUU 1.85 agian and i ran the "fastboot oem lock" and this is the cmd output:
C:\Users\kenny>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Too many links))
finished. total time: 0.936s
but now on my bootloader at the top it reads
*** Security Warning ***
is this something i should worry about??
im new to the phones with bootloaders bc none of my previous ones had them, if someone could tell me what is going on i would greatly appreciate it!!
I dont want a BRICK! :/
Click to expand...
Click to collapse
I saw that on my phone too. Once I flashed the RUU it went away. In my case I think I had it because I was running Clean Rom which I THINK has an unsecured boot image.
gunnyman said:
I saw that on my phone too. Once I flashed the RUU it went away. In my case I think I had it because I was running Clean Rom which I THINK has an unsecured boot image.
Click to expand...
Click to collapse
thanks for the info man, i too was running clean rom so thats probably why! ha also before i even booted back up i rebooted bootloader again and it went away!
same thing happened to me but when I was attempting to relock to downgrade and now i cant get back into my phone or recovery. it keeps going straight to the bootloader.. do i have to rerun the ruu? please heeellpp
bryyte said:
same thing happened to me but when I was attempting to relock to downgrade and now i cant get back into my phone or recovery. it keeps going straight to the bootloader.. do i have to rerun the ruu? please heeellpp
Click to expand...
Click to collapse
yes you need to run the RUU just choose fastboot from the bootloader screen and it should work just fine
Related
Hi
I was trying for root
http://forum.xda-developers.com/showthread.php?t=1583427
but I ended on point 2.
I tried flash all recovery from CWM and from Paul too, but nothing heppend, recovery don't work. It write:
This build is for development purposes only Do not distribute outside of HTC without HTC´s written permission. Failure to comply may lead to
legal action.
and that is all, ONE S not respond, only restart to HBOOT and bootloader. Probably I can't flash CWM.
I have new model :
***UNLOCKED***
VILLEC2 PVT SHIP S-ON RL
HBOOT-2.09.0001
RADIO-16.05.20.16_M2
OpenDSP-v05.6.0.2226.00.0418
eMMC-boot
May 10 2012, 17:19:49
I flashed the kernel with program "One_S_All-In-One_Kit_v1.0" and I just stayed in HBOOT, system isn't work.
When I was trying flash original "RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.109_Radio_16.12.20.02U_16.05.20.16_M2_release_263131_signed.exe"
it reported error 155 -it means little memory in internal storage, and nothing heppend
When I was trying flash ramdisk with fastboot, it wrote:
c:\Program Files\Android\android-sdk\platform-tools>fastboot boot ramdisk.img
creating boot image...
creating boot image - 307200 bytes
downloading 'boot.img'...
OKAY [ 0.240s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 0.257s
I have worked on it for two day
Please, HELP me! Thx
**Sorry for my english**
error 155 can mean several things.
Try to run the RUU from fastboot, That usually clears up the 155 error
If not, let us know and we will find some other solution.
If you think, launched the phone in fastboot and on PC run RUU so it's the same, error 155.
ICS doesn't work so device stay in HBOOT and fastboot.
Have you relocked the bootloader before running the RUU ??
RUU's wont work unless bootloader is locked, To lock it open a command window, navigate to the location of all your adb / fastboot files and type:
fastboot oem lock
Then run the RUU again
I do it but fastboot in PC wrote:
c:\Program Files\Android\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 268303736 (0xFFDFD78)
FAILED (status read failed (Too many links))
finished. total time: 0.936s
And on phone is:
*** RELOCKED ***
*** Security Warning ***
flash ruu rom instaled ok THANKS YOU i am happy
and one question: how i made bad under root my device?
i need make root my phone. not like made bad think my device
thx
unlock bootloader, Flash CWM in fastboot https://dl.dropbox.com/u/69014495/cwmrecovery.img
Boot into recovery and flash root package twice https://dl.dropbox.com/u/69014495/CWN-SuperSU-v0.87.zip
Then all done you are rooted, Enjoy flashing some customs ROMs
so all make for guide but device show error after flash cwmrecovery.img under fastboot adb
writhing this:
This build is for development purposes only Do not distribute outside of HTC without HTC´s written permission. Failure to comply may lead to legal action.
what next?
ICS is running
recovery not running
This way works?
http://forum.xda-developers.com/showthread.php?t=1577831
I have tried does not work
thx
So i dont know what happend, i succesfully make my hox S-OFF, use the phone and everything was working fine, then a try to downgrade my bootloader with Jet but everything went wrong from there, the process didnt finish, i try to relocked my bootloader to install the 2.20 RUU thinking it would fix it but know the RUU procesos finishes with a 131 error because my cid is diferent, this is what i have:
******tampered*****
******relocked******
jewel pvt ship s-off rl
cid-spcs_001
hboot-1.14.0002
radio-0.19as.32.09.11_2
opendsp-v29.1.0.45.0622
emmc-boot
I can put fastboot commands but its shows FAILED (remote: not allowed), i cant go into recovery, also on jet i cant go into QHSUSB_DLOAD anymore.
You really didn't need to downgrade being you were s-off.............
Sent from my HTC One X using Tapatalk 2
Did you try this command to unbrick?: sudo ./jet -u
Edit: hmm just noticed your cid changed to stock. Sorry idk where to go from there
Sent from my HTC One X using xda premium
Yes i did try the ./jet -u command but i cant get in to QHSUSB_DLOAD anymore that is the stock cid for the one x ? if thats the case maybe i can run de 1.85 RUU?
pikul said:
i cant get in to QHSUSB_DLOAD anymore
Click to expand...
Click to collapse
Did you try the hardware key way? Same as bootloader, but power and vol +
Practically gave myself a heart attack yesterday. Someone here was having trouble getting into bootloader, and mentioned power and vol +. I couldn't remember what that did (knew it wasn't bootloader) so I did it, and put the phone in Qualcomm download mode!
I was able to get back to bootloader, recovery, and reflashed the ROM that happened to be on my phone.
No. What I meant was your cid isn't supercid anymore. And I wouldn't use that RUU since your hboot is 1.14; wait till someone more experienced helps you out
Sent from my HTC One X using xda premium
redpoint73 said:
Did you try the hardware key way? Same as bootloader, but power and vol +
Practically gave myself a heart attack yesterday. Someone here was having trouble getting into bootloader, and mentioned power and vol +. I couldn't remember what that did (knew it wasn't bootloader) so I did it, and put the phone in Qualcomm download mode!
I was able to get back to bootloader, recovery, and reflashed the ROM that happened to be on my phone.
Click to expand...
Click to collapse
I guess i could run the ./jet -u command and press those keys, its that what you mean?
panda_mode said:
No. What I meant was your cid isn't supercid anymore. And I wouldn't use that RUU since your hboot is 1.14; wait till someone more experienced helps you out
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
ooooooooo :good: at least i can get into bootloader and put fastboot commands, i guess thats something
pikul said:
I guess i could run the ./jet -u command and press those keys, its that what you mean?
Click to expand...
Click to collapse
I've actually never used JET, and not quite sure how it works.
But power and vol + will put the phone in QHSUSB_DLOAD in most situations (nothing to do with JET), if that is all you are trying to do. Similar to how power and vol - boots into bootloader. Just curious if it would still worked in your "bricked" condition.
Are you able to get into fastboot? If so just use stock RUU to get back to stock,
thats the thing, i can get in to fastboot, try to run the 2.20 RUU starts and maybe 1 minute later it fails, and gives a ERROR [131] i google it and it seems to be because the cid its not the correct one anyone knows if there its a way to bypass the cid verification?
pikul said:
thats the thing, i can get in to fastboot, try to run the 2.20 RUU starts and maybe 1 minute later it fails, and gives a ERROR [131] i google it and it seems to be because the cid its not the correct one anyone knows if there its a way to bypass the cid verification?
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/HTC_One_X
Try this thread. I think there is a way to use the stock recovery and the cid you used to unlock it. May give you some ideas.
AT&T HTC OneX
Andriod 4.1.1
ViperXL
i check all of them, but i just cant get to unlock my bootloader again or flash a different cid, not even flash the recovery, y guess its because i relock my bootloader
pikul said:
i check all of them, but i just cant get to unlock my bootloader again or flash a different cid, not even flash the recovery, y guess its because i relock my bootloader
Click to expand...
Click to collapse
Have you tried to get a new identifier token and unlock the phone to get TWRP again?
http://onexroot.com/one-x-root/how-to-unlock-bootloader-and-root-att-htc-one-xhtc-one-xl/
AT&T HTC OneX
Android 4.1.1
ViperXL
is it posible to get it in bootloader mode? cause thats all i can access :/
Everytime i try to flash a file in fastboot it shows FAILED (remote: not allowed)
pikul said:
is it posible to get it in bootloader mode? cause thats all i can access :/
Click to expand...
Click to collapse
download a ROM.. put it in your fastboot folder,
boot into fastboot and try this
fastboot flash zip name_of_rom.zip <-- this works with HTC RUUs, may work with an actual ROM.. Use at your own risk, I have never tried it with a custom ROM.
mirGantrophy said:
download a ROM.. put it in your fastboot folder,
boot into fastboot and try this
fastboot flash zip name_of_rom.zip <-- this works with HTC RUUs, may work with an actual ROM.. Use at your own risk, I have never tried it with a custom ROM.
Click to expand...
Click to collapse
I took the .img files from the rom.zip that you get from the RUU, but it doesnt work.
C:\Programas\Fastboot>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.966s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.000s
C:\Programas\Fastboot>fastboot flash system system.img
sending 'system' (1048572 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.309s
pikul said:
I took the .img files from the rom.zip that you get from the RUU, but it doesnt work.
C:\Programas\Fastboot>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.966s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.000s
C:\Programas\Fastboot>fastboot flash system system.img
sending 'system' (1048572 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.309s
Click to expand...
Click to collapse
If you have the RUU.zip, do this then:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip rom.zip
see if that works..
This is what i get:
C:\Programas\Fastboot>fastboot flash zip rom.zip
sending 'zip' (576544 KB)...
OKAY [ 24.368s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 26.975s
this sucks, i have to go to work and i dont have another cellphone :/
pikul said:
this sucks, i have to go to work and i dont have another cellphone :/
Click to expand...
Click to collapse
You can try to find the cidnum for the htc onexl and see if you can trick it by editing android-info.txt file to match cid num.
Example:
edited android-info file
modelid: PG3213000
cidnum: KT___901
cidnum: HTC__004(this edited file only)
mainver: 2.32.1010.1
hbootpreupdate:13
boot again into fastboot
AT&T HTC OneXL
Android 4.1.1
ViperXL
Hi all
I was S-Off and SuperCID, but wanted to try the OTA update. So, I changed my CID back to T-MOB010, I ran the RUU and then tried flashing the OTA through stock recovery. That didn't work, so I relocked the bootloader (still S-off). Tried doing the OTA again through stock recovery, no luck.
Now I want to unlock the bootloader again, but when when try the get_identifier_token I get this message:
<bootloader> [ERR] Comand error !!!
Okay [0.016s]
finished. total time: 0.017s
Any suggestion to be able to unlock again?
***Solved***
Ran RUU and was able to unlock again
Hi, I am trying to install the stock RUU. But when I do the command "Fastboot oem lock" it gives an error message:
Code:
C:\Users\Rikard\Desktop\ADB + Fastboot . Drivers>fastboot oem lock
... INFO[ERR] Command error !!! [COLOR="Red"]<---- why this?[/COLOR]
OKAY [ 0.013s]
finished. total time: 0.013s
C:\Users\Rikard\Desktop\ADB + Fastboot . Drivers>
Why do I get a error message?
(My Bootloader don't say **UNLOCKED** at the top)
HTC Desire s
Unlocked
Saga PVT ENG S-OFF
HBOOT-0.98.2000 (PG8810000)
The bootloader lock/unlock procedure wasn't introduced until hboot 2.x
If you're on a 0.x hboot, you don't need to lock.
Aquous said:
The bootloader lock/unlock procedure wasn't introduced until hboot 2.x
If you're on a 0.x hboot, you don't need to lock.
Click to expand...
Click to collapse
But I can't install the stock RUU. It gives me an error 155
hej2010 said:
But I can't install the stock RUU. It gives me an error 155
Click to expand...
Click to collapse
You really need to search - you're not exactly the first person to get this error message and it has been covered many, many times.
SimonTS said:
You really need to search - you're not exactly the first person to get this error message and it has been covered many, many times.
Click to expand...
Click to collapse
I have searched and can't find anything. That's wy I asked here.
Hello All,
Please can someone help, I successfully rooted my htc u11 and put a custom rom on to phone . I decided to go back to stock and restore my phone as new. I had unlocked and locked my bootloader all ok.
Now I have the problems, my phone cant seem to unlock bootloader, everytime I try and fastboot recovery or roms. I get this message 9 ru security fail recovery and bootloader isn't bl-unlocke.
Im stuck ,plus when I boot the phone I get the message, your phone is not to be trusted . Please can anyone help.
mackenzie121 said:
Hello All,
Please can someone help, I successfully rooted my htc u11 and put a custom rom on to phone . I decided to go back to stock and restore my phone as new. I had unlocked and locked my bootloader all ok.
Now I have the problems, my phone cant seem to unlock bootloader, everytime I try and fastboot recovery or roms. I get this message 9 ru security fail recovery and bootloader isn't bl-unlocke.
Im stuck ,plus when I boot the phone I get the message, your phone is not to be trusted . Please can anyone help.
Click to expand...
Click to collapse
Hi, let's see if there's any chance...
Enter the download mode and connect it to the PC then type fastboot devices to make it recognize.
If you recognize it, try typing fastboot oem get_identifier_token and see what happens...
paulpier007 said:
Hi, let's see if there's any chance...
Enter the download mode and connect it to the PC then type fastboot devices to make it recognize.
If you recognize it, try typing fastboot oem get_identifier_token and see what happens...
Click to expand...
Click to collapse
yeah fastboot devices sees it and recongnizes it biut when I do oem get identifier I get
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.012s]
finished. total time: 0.012s
mackenzie121 said:
yeah fastboot devices sees it and recongnizes it biut when I do oem get identifier I get
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.012s]
finished. total time: 0.012s
Click to expand...
Click to collapse
Did you try running a RUU
thicklizard said:
Did you try running a RUU
Click to expand...
Click to collapse
as in putting the rom on memory card and booting into download mode? and pressing up on the volume. yes I have tried many , but they all say mismatch. Unless im doing something wrong?
cant seem to find the right RUU.
this is what I have on my phone
****relocked***
***production***
htc_ocnuhl pvt s-on
LK-1.0.0.0000
radio-8998-002772tov-1802241313
openDSP-v11.6.00.347.cb8998_0711
os - 2.33.206.9
You can find RUU files here(in thread search):
https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048
mackenzie121 said:
as in putting the rom on memory card and booting into download mode? and pressing up on the volume. yes I have tried many , but they all say mismatch. Unless im doing something wrong?
cant seem to find the right RUU.
this is what I have on my phone
****relocked***
***production***
htc_ocnuhl pvt s-on
LK-1.0.0.0000
radio-8998-002772tov-1802241313
openDSP-v11.6.00.347.cb8998_0711
os - 2.33.206.9
Click to expand...
Click to collapse
i had same problem,
start unlocking your bootloader on htcdev website and take new token: (fastboot oem get_identifier_token) until you save NEW "Unlock_code.bin” in fastboot directory then : (fastboot flash unlocktoken Unlock_code.bin)
just start all from the beginning and everything should go right
Or
copy RUU to your external sd card and rename to 2PZCIMG (leave the .zip extension untouched); reboot to download mode and it will ask you (in yellow) to choose UP to start the RUU flash (previously copied to the External SD card) or DOWN to cancel flash and make a normal boot.