I got S-off and unlocked bootloader. I have install Custom Recovery. I install a RUU without locking bootloader. After RUU complete, I go into bootloader again. Now the status of bootloader is unknown, meaning it doesn't say Lock or Unlock on the top of the screen but it does say S-OFF. I try to fastboot flash a custom recovery, it doesn't work. I try relock, it doesn't work either.
It give me this error, FAILED (remote: not allowed)
I try upgrade and downgrading, doesn't help.
How can I fix this problem?
seems like I can't use fastboot command anymore. I want to install custom recovery and I can't do fastboot flash recovery.
I am having this same exact issue with my Xperia Z Ultra. It is really hard to find any information on this. Anyone have some input on this?
I know this is the wrong forum for me, but the error is exactly the same. Thanks.
Related
I have great problem. i unlock the bootloader and root the phone. then i try to install new ota upgrade but doesn't work. i tried to lock the bootloader but nuw appears "tampered" and "security warning" and the phone do not enter in recovery. tried to flash stock recovery but nothing. i can't unlock the bootloader else. stuck cmd on "sending unlocktoken". Any ideas?
I´ve the same problem, currently i am trying other RUU out because i suppose that I ´ve flashed the wrong one.
I solve the probelm for me, this problem appears because i deffenetly installed the wrong RUU.
I used the folowing RUU: RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed.exe
franzyx said:
I have great problem. i unlock the bootloader and root the phone. then i try to install new ota upgrade but doesn't work. i tried to lock the bootloader but nuw appears "tampered" and "security warning" and the phone do not enter in recovery. tried to flash stock recovery but nothing. i can't unlock the bootloader else. stuck cmd on "sending unlocktoken". Any ideas?
Click to expand...
Click to collapse
What method did you use to unlock / install recovery?
Whenever I try unlock bootloader bug out FAILED (remote: Command did not allowed).
I have Bootloader unlock allowed.
I tried in CMD - Fastboot and Flashtoo and out this same problem.
When I tried twice unlock bootloader I get OKAY and I try turn on my phone, I walk in bootloop.
Where is problem?
Hi! So actually you did unlocked your bootloader (as i understand), and when you turn on your device after the unlock you go into bootloop. This is something normal. You need to flash the stock .ftf with flashtool (i recommend you to use old versions like 0.9.11.0). Have a look here:
http://forum.xda-developers.com/xperia-l/help/bootloop-unlocking-bootloader-t2675892 ! Good luck!
What firmware version did you flashed. I have flashed firmware for c2104 and i got this bootloop. Make sure you flash the propper firmware verison for your device.
noobp said:
Hi! So actually you did unlocked your bootloader (as i understand), and when you turn on your device after the unlock you go into bootloop. This is something normal. You need to flash the stock .ftf with flashtool (i recommend you to use old versions like 0.9.11.0). Have a look here:
http://forum.xda-developers.com/xperia-l/help/bootloop-unlocking-bootloader-t2675892 ! Good luck!
What firmware version did you flashed. I have flashed firmware for c2104 and i got this bootloop. Make sure you flash the propper firmware verison for your device.
Click to expand...
Click to collapse
When I tried it, in Service Menu I have "Rooting status: Unkown".
I have bad code in Bootloader unlock Wizard and I can't change it, field is inactive.
I have firmware C2104, I don't have any branding.
Hello everyone,
I tried unlocking my bootloader with HTCdev. It seemed to be a success, I had the screen which asked me if I really want to unlock, I said yes and my data has been wiped, so I thought that it was good and tried turning S-OFF. However, it seems that my bootloader is still locked because of these three reasons:
- Rumrunner wasn't able to do S-OFF.
- I can't flash a custom recovery (it says "signature verify failed").
- When I am on the Hboot screen (version 2.22), it is still written ***LOCKED***...
I also tried to lock and re-unlock with a new key but it had the same result, and most of the time the unlocking screen doesn't even show up when I type fastboot flash unlocktoken Unlock_code.bin
Did you have similar issues, or do you have any ideas how to arrange this?
Thank you
I tell them what happened to me, my U11 phone had it with the European version and I did s-off with sunshine without problems, I changed cid BS_US001 and mid 2PZC50000 without any problem, but try to load the ruu that you download from htc 1.28.617.3 and came out error 155 that the image was not correct, then what I did was to close the bootloader with the command fastboot oem lock, reset the phone and send me to the bootloader screen, when entering download it appeared and s-on and Bootloader Relocked , try to load the ruu again but it tells me that the image does not correspond, try to install recovery stock, TWRP, and firmware 1.28.617.3 but it does not let me do anything, when trying to enter recovery it sends me to bootloader and if I try to unblock bootloader I gives frp error, it is clear that despite being relocked the bootloader I keep appearing the screen that has been modified the phone, when entering download I appears in OS 1.28.401.7 and putting fastboot getvar all if I see the c id and mid of the American version, but I do not do anything.
Do you think it has a solution?
Waiting answer ...
Thank you ...
Hi.
There are no answers yet, because, honestly, it is difficult to understand what happened. You wrote one single phrase that is 10 lines long. Try to reformulate, using listed items, paragraphs and so on.
Just a friendly suggestion, no offense.
valvaher said:
I tell them what happened to me, my U11 phone had it with the European version and I did s-off with sunshine without problems, I changed cid BS_US001 and mid 2PZC50000 without any problem, but try to load the ruu that you download from htc 1.28.617.3 and came out error 155 that the image was not correct, then what I did was to close the bootloader with the command fastboot oem lock, reset the phone and send me to the bootloader screen, when entering download it appeared and s-on and Bootloader Relocked , try to load the ruu again but it tells me that the image does not correspond, try to install recovery stock, TWRP, and firmware 1.28.617.3 but it does not let me do anything, when trying to enter recovery it sends me to bootloader and if I try to unblock bootloader I gives frp error, it is clear that despite being relocked the bootloader I keep appearing the screen that has been modified the phone, when entering download I appears in OS 1.28.401.7 and putting fastboot getvar all if I see the c id and mid of the American version, but I do not do anything.
Do you think it has a solution?
Waiting answer ...
Thank you ...
Click to expand...
Click to collapse
Ok i may be way off base, but if the phone can boot into the OS go to developer enable usb debug and
Oem unlocking then follow the htc guide to unlock bootloader again ( not positive on that part never relocked a bootloader then unlocked) once that is done redownload the correct ruu per your cid and retry. Just my 2 cents. Hth.
you only flash full ruu 1.28.401.7
try to find in https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048
Hey guys,
I am trying to unlock my bootloader but it doesnt work, everytime I do the "Fastboot oem get_unlock_data" command, it says it failed to get unlock data.
I have unlock bootloader option in dev settings enabled and all drivers properly installed along with fully working sdk and fastboot tools etc. I have a couple xiaomi devices with different custom roms.
Previously I installed RETLA using tiny fastboot script cus i bought the phone in latin america but software channel says RETAR... Is this discrepancy the problem?
If not, anyone know why even though bootloader unlock option is on, the fastboot command to get the data fails?
Using getvar all i see the cid is 0x0000, i've read that having cid: 0x0000 is the problem, might installing the proper firmware: RETAR change this?
Ty
Hpotersept2 said:
cid is 0x0000
Click to expand...
Click to collapse
Most likely you will have to forget about unlocking the bootloader.
Reflashing will not help you in any way.
ilia3367 said:
Most likely you will have to forget about unlocking the bootloader.
Reflashing will not help you in any way.
Click to expand...
Click to collapse
Do you know why the cid is like that? Idk what has been done to it cus I bought it used. Any ideas?
Ty
The boot loader on your phone was blocked incorrectly and the system stopped starting.
cid: 0x0000 is a consequence of the boot loader working state recovery software.
It is now in a state oem-locked" as it was originally from the factory. But you cannot unlock the bootloader now. But, if I'm not mistaken, you can install firmware for any update region without having to unlock the bootloader.