Related
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
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, 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.
So I'm in the process of getting my phone back to original to so I can edge up my phone. I accident relocked the bootloader with oem relock, and now I'm stuck with S-OFF and "relocked." I'm not quite sure what to do now, as I also uninstalled SU. How do I go about getting "Locked" and S-ON. I tried the sdb shell and all that stuff, but when you type SU I can't since it is no longer installed. Also if I try to push a recovery it fails.
Code:
C:\ADB>fastboot flash recovery cwm_v6.0.4.8_m8vzw-3.img
target reported max download size of 1830612992 bytes
sending 'recovery' (12564 KB)...
OKAY [ 1.175s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.193s
CinemaGFX said:
So I'm in the process of getting my phone back to original to so I can edge up my phone. I accident relocked the bootloader with oem relock, and now I'm stuck with S-OFF and "relocked." I'm not quite sure what to do now, as I also uninstalled SU. How do I go about getting "Locked" and S-ON. I tried the sdb shell and all that stuff, but when you type SU I can't since it is no longer installed. Also if I try to push a recovery it fails.
Code:
C:\ADB>fastboot flash recovery cwm_v6.0.4.8_m8vzw-3.img
target reported max download size of 1830612992 bytes
sending 'recovery' (12564 KB)...
OKAY [ 1.175s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.193s
Click to expand...
Click to collapse
So what you need to do is. Supercid your phone to 11111111 an go to htcdev.com an unlock your bootloader. Then once that is done. You need to downgrade to 1.55 so then you can lock your bootloader turn s-on an ruu the encrypted ruu that posted. Do NOT TURN S-ON till you find this ruu that's posted an understand it completey an ask dottat any question in that thread. Once you r downgraded locked an s-on an run the encrypted ruu your phone should be all stock an lock an s-on no tampered no nothing.
I was able to get back to stock except I have the tampered flag. I did this last night so I was unable to follow your steps. What should I go about now, as I have S-ON, locked bootloader, no root and a tampered flag?
CinemaGFX said:
I was able to get back to stock except I have the tampered flag. I did this last night so I was unable to follow your steps. What should I go about now, as I have S-ON, locked bootloader, no root and a tampered flag?
Click to expand...
Click to collapse
I think he specifically said do NOT turn s on. You cannot do anything unless you s off again. What Rom do you have loaded? Turning s off is the LAST step because it's like locking the door and throwing away the keys
I actually did that stuff before I saw his message, I followed: http://www.bane-tech.com/how-to-ret...on-relock-bootloader-unrootuninstall-supersu/
Guess now I'm going pay to get the s back off...
CinemaGFX said:
I actually did that stuff before I saw his message, I followed: http://www.bane-tech.com/how-to-ret...on-relock-bootloader-unrootuninstall-supersu/
Guess now I'm going pay to get the s back off...
Click to expand...
Click to collapse
Well. We got something else to try. What version os are you on?
so my phone froze today so I took out battery and turned it on and all it does is go to the boot loader.
So I decide to try recovery all this does is flash android logos and then back to same screen,
Next I try factory reset and same flashes to android logos and back to same screen
After reading this forum
I then go through the process of unlocking my boot loader via htc dev the process goes great I receive email etc etc
The final process should bring up a disclaimer on my screen but nothing
So my question is wtf what do I do?
Please help me
Check the guide at HTC side if you have done everything correctly, all is written how it should or copy and paste.
Without unlocked bootloader, there is no chance to rescue your phone.
Any information about your phone model and exactly the step it fails is important, too.
this problem has such a friend, and it does not solve constantly locked bootloader ...
Does anyone solved this problem?The same situation of my phone?Please help!
Hi,
i flash 2.8.4.0twrp, then make backup, after that (whit in recovery options) try to make factory reset, and after that my one sv is messed up like hell...
It is not booting...stuck for a while at htc logo, screen goes black, then loads bootloader, I am able to go to twrp (I have fresh backup of complete phone, did it with twrp above), but not able to flash anything...it fails every time, saying that is unable to mount cache...try advance wipe, but it is not able to mount any thing...
Since my phone was S-off, unlocked bootloader, superCID (it is k2ul), hboot2.0, I tryed with fastboot oem relock (to lock bootloader, and flash stock pl80img.zip) but that fails too, ends up with to many links message...and bootloader stays with tampered and unlocked sign...before flashing 2.8.4.0twrp phone was working great, but after factory reset it is not able to mount anything, and running pl80img.zip gives me all so only fail...fail...fail...
So..now i have latest twrp and totaly messed up phone...
How can U help me, anny advice???
THX in advance!
danrock1984 said:
so my phone froze today so I took out battery and turned it on and all it does is go to the boot loader.
So I decide to try recovery all this does is flash android logos and then back to same screen,
Next I try factory reset and same flashes to android logos and back to same screen
After reading this forum
I then go through the process of unlocking my boot loader via htc dev the process goes great I receive email etc etc
The final process should bring up a disclaimer on my screen but nothing
So my question is wtf what do I do?
Please help me
Click to expand...
Click to collapse
I have the same problem!!
The phone details:
Locked Bootloader
K2_UL XA SHIP S-ON RL
HBOOT 2.00.0000
T-mobile network lock
NO SuperCID
The phone doesn't boot up!
It boot to bootloader fastboot mode always!
The notification led blinks constantly!
When I wanted run the RUU (K2_UL_ICS_EUROPE...etc) the phone doesn't reboot black HTC Screen it goes back to bootloader, and it doesn't working
After I downloaded this:
https://www.androidfilehost.com/?fid=23212708291675772
After I download it rename to PL80IMG.zip and it loading after checking, and goes back to bootloader, no volume up to update option!
After I downloaded OTA_K2_UL_JB_45_S_Voda-Hutch_AU_2.14.862.9-1.17.862.9_release_3136147vue6nb55rwgyw0d.zip
After I extracted the firmware zip from it, edited the android-info.txt CID number to HTC__032 and place it to SD, rename to PL80IMG.zip after I get the same problem!
After these problems are try another method with fastboot!
fastboot flash zip flash firmware zip and I got this:
C:\Users\Erkaft\Desktop\Új mappa>fastboot flash zip firmware.zip
sending 'zip' (33772 KB)...
OKAY [ 2.668s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 5.264s
C:\Users\Erkaft\Desktop\Új mappa>
And when i want to erase all with fastboot I got this:
C:\Users\Erkaft\Desktop\Új mappa>fastboot erase all
erasing 'all'...
FAILED (remote: not allowed)
finished. total time: 0.000s
C:\Users\Erkaft\Desktop\Új mappa>fastboot erase boot
erasing 'boot'...
FAILED (remote: not allowed)
finished. total time: -0.000s
C:\Users\Erkaft\Desktop\Új mappa>fastboot erase system
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: -0.000s
I also tried bootloader unlock but the last message didn't appear on the phone and it stay locked
Any idea to ressurection this phone?
You need ti unlock your phone,otherwise you can't do anything.