I would try to be as descriptive as possible.
Check if BLU allowed:
Dial *#*#7378423#*#*
Service info > Configuration > Rooting Status. It says Bootoader unlock allowed: yes
Go to SONY official webpage to get the unlock key. http://unlockbootloader.sonymobile.com/instructions
Enter the IMEI code and get the KEY in mail.
Put the phone in fastboot mode.
Code:
D:\>fastboot -i 0x0fce getvar version
version: 0.5
finished. total time: 0.002s
D:\>fastboot -i 0x0fce oem unlock 0xMYKEYINRIGHTCASE
...
FAILED (remote: Command did not succeed)
finished. total time: 0.036s
Curiously if I run the second command again, it succeeds.
Code:
D:\>fastboot -i 0x0fce oem unlock 0xMYKEYINRIGHTCASE
...
OKAY [ 0.171s]
finished. total time: 0.172s
Now if my bootloader is not supposed to be unlocked or the key is wrong then I believe the behavior should be consistent and should always FAIL. Unfortunately that is not the case. What is worse is that when now I do
Code:
D:> fastboot reboot
rebooting...
finished. total time: 0.002s
It does not reboot anymore and goes into boot loop. The only way out is to flash the stock ROM using flashtool and get it back.
What I really want to do:
Build and flash AOSP 4.3 onto the device. I have already build it and also downloaded pre-build img from one of the threads. Using fastboot flash works for boot, system and userdata on second attempt just like bootloader. However fastboot flash cache fails consistently. Rebooting again put me back into boot loop.
Is there any way to find out if the bootloader is actually unlocked or not?
I would appreciate any help in debugging/troubleshooting this problem. Looking forward.
P.S.: Not sure if this belongs here or in development forum.
bump up.
Any help would be appreciated from devs.
Go to configuration again and check rooting status. If you are truly unlocked, it will say:-
Bootloader unlocked: Yes
Sent from my C6603 using xda app-developers app
shoey63 said:
Go to configuration again and check rooting status. If you are truly unlocked, it will say:-
Bootloader unlocked: Yes
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Thanks for responding. But unfortunately for me as soon as I run the oem unlock command twice, it does not boot anymore and I have to reflash it again. Post reflash when I go back I still see the previous status.
Adding some background:
This issue occurred only after I reflashed the stock ROM using SONY companion. This might have locked the bootloader again and corrupted the process of unlocking it. Is this a possibility? Any body who had similar problem?
Could you reflash to stock and check the bootloader unlock status? If you can reflash via PC Companion, it usually means that your bootloader was not unlocked. If yours was unlocked, it would fail and you would have to use Emma instead.
pandaball said:
Could you reflash to stock and check the bootloader unlock status? If you can reflash via PC Companion, it usually means that your bootloader was not unlocked. If yours was unlocked, it would fail and you would have to use Emma instead.
Click to expand...
Click to collapse
I can reflash to stock using flashtool, does that mean anything?
Sent from my Nexus 4 using xda app-developers app
nivarp said:
I can reflash to stock using flashtool, does that mean anything?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No. If you can repair your phone via PC Companion, your bootloader is locked. Only if you are unable to do that with an error code along the lines of "This phone's software has been modified" then your bootloader is unlocked. Flashtool works regardless of bootloader unlock status.
pandaball said:
No. If you can repair your phone via PC Companion, your bootloader is locked. Only if you are unable to do that with an error code along the lines of "This phone's software has been modified" then your bootloader is unlocked. Flashtool works regardless of bootloader unlock status.
Click to expand...
Click to collapse
I can repair which essentially means that the bootloader is locked. However I still see the configuration saying bootloader unlock allowed to be yes. Strange that i am not able to unlock it.
Related
Hi all.
Somehow I managed to feel like a noob. So as follows:
Model: C5303
ROM: Stock
BL: Locked
TA partition: untouched
It bootloops and goes to the sony repairscreen
I can detect it with fastboot, but not write to (ie fastboot oem unlock hangs and doesn't give any error response)
I can detect it with flashtool in S1boot mode, but again cannot write to it. It hangs/fails when trying to write to it both from Androxyde's Flashtool and with SUS
I feel like there must be something very obvious that I'm missing, as I cannot see what I'm doing wrong.
Any ideas?
Orkeren said:
Hi all.
Somehow I managed to feel like a noob. So as follows:
Model: C5303
ROM: Stock
BL: Locked
TA partition: untouched
It bootloops and goes to the sony repairscreen
I can detect it with fastboot, but not write to (ie fastboot oem unlock hangs and doesn't give any error response)
I can detect it with flashtool in S1boot mode, but again cannot write to it. It hangs/fails when trying to write to it both from Androxyde's Flashtool and with SUS
I feel like there must be something very obvious that I'm missing, as I cannot see what I'm doing wrong.
Any ideas?
Click to expand...
Click to collapse
If you did OEM unlock did you use the key you got from Sony's website?
The code is fastboot OEM unlock 0xKEY
Sent from my Xperia SP using XDA Free mobile app
noahvt said:
If you did OEM unlock did you use the key you got from Sony's website?
The code is fastboot OEM unlock 0xKEY
Sent from my Xperia SP using XDA Free mobile app
Click to expand...
Click to collapse
yes I did. I've unlocked quite a few phones by now.
What happens is, that it seems to accept the fastboot command and then hangs.
First time success unlock & use TWRP,
then install SU.zip in TWRP but the phone cannot normal boot in;
therefore flash FTF, now can use the phone but cannot use TWRP again ( fastboot boot recovery.img).
Unlock status is unknown.
Can flash FTF.
What the driver is used in fastboot in Windows?
How can I know the phone is connecting correctly?
Any solution to use TWRP & root?
smallerstone said:
First time success unlock & use TWRP,
then install SU.zip in TWRP but the phone cannot normal boot in;
therefore flash FTF, now can use the phone but cannot use TWRP again ( fastboot boot recovery.img).
Unlock status is unknown.
Can flash FTF.
What the driver is used in fastboot in Windows?
How can I know the phone is connecting correctly?
Any solution to use TWRP & root?
Click to expand...
Click to collapse
http://developer.sonymobile.com/downloads/drivers/fastboot-driver/
Installed the above driver, pc shows Android Phone> Sony Fastboot Interface
fastboot -i 0x0fce oem unlock 0x(unlock code)
FAILED (remote: Command not allowed)
fastboot boot recovery.img
downloading 'boot.img'...
OKAY
booting...
FAILED (status read failed (Too many links))
Still canbot use TWRP...
Help... :crying:
Is your bootloader actually unlocked? Go to dialpad on phone, enter service menu *#*#7378423#*#*, go to Configuration and check if bootloader unlocked...What does it say in the Configuration screen?
Rooting status unknow :crying:
smallerstone said:
Rooting status unknow :crying:
Click to expand...
Click to collapse
You didn't by any chance activate the MyXperia security function after unlocking your bootloader?
dl12345 said:
You didn't by any chance activate the MyXperia security function after unlocking your bootloader?
Click to expand...
Click to collapse
Need wait for an OTA update that fixes this issue?!!
Oh no, that mean nothing can do if activated the MyXperia security in unlocked Z3 plus?! :crying:
Then now just use the phone in unlock & cannot root status?!!!
smallerstone said:
Need wait for an OTA update that fixes this issue?!!
Oh no, that mean nothing can do if activated the MyXperia security in unlocked Z3 plus?! :crying:
Then now just use the phone in unlock & cannot root status?!!!
Click to expand...
Click to collapse
If you activated MyXperia with the phone in an unlocked state then you have permanently damaged your phone
dl12345 said:
If you activated MyXperia with the phone in an unlocked state then you have permanently damaged your phone
Click to expand...
Click to collapse
Oh... hope Sony will fix the problem :crying:
Hi everybody, I have a little question regarding my P10.
The model of my phone is VTR-L09C521B101
Is there a way to flash this phone with VTR-L09C432 version?
or i need to flash with same model version (VTR-L09C521)?
Thnks
Yes, it is possible to 'rebrand'. The procedure is explained in the Mate 9 forum. It is not so easy and involves unlocking the bootloader.
Updating can be done with the Firmware Finder (Playstore).
M1chiel said:
Yes, it is possible to 'rebrand'. The procedure is explained in the Mate 9 forum. It is not so easy and involves unlocking the bootloader.
Updating can be done with the Firmware Finder (Playstore).
Click to expand...
Click to collapse
thanks for the answer!!
regarding bootloader, the phone shows this:
PHONE RELOCKED
FRP LOCK
ADB shows me that the phone is unlocked, the problem is when I try to send something to phone it shows:
Error Remote command not allowed.
any ideas?
thanks!
I've tried to reword the mate 9 instructions for the p10 here: https://forum.xda-developers.com/p10/help/rebrand-firmware-finder-t3685951
As for adb, what command are you trying? Do you see your phone if you type ADB Devices?
Quintman said:
I've tried to reword the mate 9 instructions for the p10 here: https://forum.xda-developers.com/p10/help/rebrand-firmware-finder-t3685951
As for adb, what command are you trying? Do you see your phone if you type ADB Devices?
Click to expand...
Click to collapse
Quintman, no the phone is not listed with adb devices command. I can only enter with fastboot.
Let me paste the commands that I have tried:
C:\adb>fastboot devices
WPG7N17320000978 fastboot
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
C:\adb>fastbot oem lock <my_unlock_code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot oem unlock <my_unlock_code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot oem relock <my_unlock_code>
...
FAILED (remote: stat not match)
finished. total time: 0.016s
The Strange thing is that in the phone shows PHONE RELOCKED, not unlocked as ADB shows.
Since I uploaded boot img of another version (C432) full OTA, could this be the problem? in this case what can I do?
thanks for your help!!
Could this be happening because of FRP Lock?, none of the software I have tried (DC-phoenix, chimera and Unlocker v2) worked. Im this close to throw this f*ckin phone to trash u.u
fmm1977 said:
Could this be happening because of FRP Lock?, none of the software I have tried (DC-phoenix, chimera and Unlocker v2) worked. Im this close to throw this f*ckin phone to trash u.u
Click to expand...
Click to collapse
edit: just found this in another thread "FRP Lock occurs when the phone has a firmware mismatch and or oem unlocking is not on in developer options"
Hmm, i've just checked my phone and in fastboot it says PHONE Locked, and FRP Unlock. I think that may be your issue. What exactly did you do to flash your phone with the other version? put an UPDATE.APP into a \Dload folder and 3 button update?
is your phone booting (guessing not). my guess is that you need to get a hold of your stock firmware file an flash that first.
Quintman said:
edit: just found this in another thread "FRP Lock occurs when the phone has a firmware mismatch and or oem unlocking is not on in developer options"
Hmm, i've just checked my phone and in fastboot it says PHONE Locked, and FRP Unlock. I think that may be your issue. What exactly did you do to flash your phone with the other version? put an UPDATE.APP into a \Dload folder and 3 button update?
is your phone booting (guessing not). my guess is that you need to get a hold of your stock firmware file an flash that first.
Click to expand...
Click to collapse
Ok, this is what I've done step by step:
1.- With the unlock code provided by huawei, I have unlocked my phone (my version is VTR-L09C521B101 stock)
2.- Once unlocked, I have downloaded another ROM version (VTR-L29C605B151) in the web page says this rom is for latin america), so with the Huawei Update Extractor, I have extracted all files.
3.- Via ADB/FASTBOOT, I sent the files to my phone, boot.img first and then the others. (big big mistake!)
4.- Rebooted the phone, and then keeps restarting at huawei logo.
5.- Seeing that it did´t worked, what I did was to lock the phone again thinking to send it to Huawei (at this point the phone shows as "unlocked" via fastboot commands, however when I start the phone in fastboot mode, in the screen shows "PHONE RELOCKED, FRP LOCK"
6.- Sent to huawei's service, they said that they cannot fix my phone because it was tampered/rooted.
7.- Right now all I need to fix my phone is to LOCK/UNLOCK again in order to rebrand it to L29 version, since the original stock rom dont exist (not as FULL OTA).
And that´s what I did so far my friend.
Questions:
1.- Is there a way to connect to my phone and change the oem info file? or something?
2.- Do I need to wait the stock rom to be released in order to reflash via Dload method?
3.- What if the stock ROM version of my phone is never released?
thank you for your answer my friend!!
Hmm ok. I am just not sure on your step 3, I've never heard of a method that involves a boot.img... what I would suggest, is to try and download the stock firmware files (need the larger full ota files), extract the update.app file and put on sd card in \dload.
Then hold down both volume up and down and power (3 button method)
It will try and flash the stock image back to the phone.
I just tried the Dload method and nothing happened (always stuck in 5%), now im going to try to use a smaller memory card (mine is 64 Gb). lood
U have disconnected the USB cable when u try 3 button update
berka38 said:
U have disconnected the USB cable when u try 3 button update
Click to expand...
Click to collapse
Yes sr!!
My screen keep on showing "System Has Been Destroyed". The best I can do is to be at fastboot. When in fastboot mode I try to unlock the phone using CMD yet unsuccessfull. I can't get into developer option because it's stuck at "System Has Been Destroyed" screen.
Here's the message after input "fastboot oem device-info"
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.011s]
Finished. Total time: 0.015s
Have you flashed a rom with miflashtool? Probably you've not unchecked "clean all and lock".
I think you're phone is hard bricked
Sounds like hard brick indeed. Check this out: https://forum.xda-developers.com/showpost.php?p=80029403&postcount=22
overcustom said:
Have you flashed a rom with miflashtool? Probably you've not unchecked "clean all and lock".
I think you're phone is hard bricked
Click to expand...
Click to collapse
I have tried to flashed a rom with miflash tool. I've checked clean all only. And it showed "error FAILED (remote : Erase is not allowed in Lock State)".
Brays88 said:
I have tried to flashed a rom with miflash tool. I've checked clean all only. And it showed "error FAILED (remote : Erase is not allowed in Lock State)".
Click to expand...
Click to collapse
It means bootloader was already Locked.
On which rom were you before?
overcustom said:
It means bootloader was already Locked.
On which rom were you before?
Click to expand...
Click to collapse
I've forgot which rom i've been. Any idea how to unlock the bootloader?
Brays88 said:
I've forgot which rom i've been. Any idea how to unlock the bootloader?
Click to expand...
Click to collapse
Unfortunately you have to flash a rom using EDL mode with an authorized account, hard brick is a very awful thing.
Thats why you need to read before doing anything with your phone. Almost every thread has flashing guides and all say that you have to unlock bootloader first to flash with miflash or to flash with twrp to avoid hardbricks. Edl is the way to go, good luck mate
ef1x said:
Thats why you need to read before doing anything with your phone. Almost every thread has flashing guides and all say that you have to unlock bootloader first to flash with miflash or to flash with twrp to avoid hardbricks. Edl is the way to go, good luck mate
Click to expand...
Click to collapse
i m having same problem this morning after OTA update!!! my systeme was unlocked and everything goes well, they asked my to update i said yes as ever, but now i have screen Systeme as been Destroyed, i did everythings that i know but nothings worked, i m always blocked because any method i used to flash said can't flash, bootloader locked... WHO the [email protected]#K LOCKED MY BOOTLOADER,,,,, please help i m crying now, it's a 800 $phone useless now, my wife gonna killed me!!!! LOL
Hey!
I got a Zenfone 8 from a friend, and he told me that he tried to flash Lineage OS once, for some reason he got some errors and ended up going back to the stock ROM and relocking the bootloader.
Now I'm trying to unlock the bootloader again through the ASUS app, but it doesn't work. He tried to help me with some commands through fastboot mode and it also didn't work. There is any way to unlock it again after relocking it once?
He said he used the command 'fastboot oem asus-csc_lk' to relock it, don't know if it is hepful.
edit: We tried 'fastboot oem unlock' 'fastboot flashing unlock' (failed with permission error) and 'fastboot oem asus-unlock' (which resulted in FAILED (remote: 'Verify unlock token fail.')
Also AsusUnlock apk installs succesfully through ADB but fails to unlock with error 24802. Trying to install it through the phone doesn't work and gives me an error.
give more information please, from what build did your friend flash the lineageos? to what build did he go back to? did you install latest working ADB? are the drivers for the fastboot installed correctly? are you connected to the internet when trying to run the app on the phone?
AJ205 said:
give more information please, from what build did your friend flash the lineageos? to what build did he go back to? did you install latest working ADB? are the drivers for the fastboot installed correctly? are you connected to the internet when trying to run the app on the phone?
Click to expand...
Click to collapse
He said he followed what was on the guide he found, first updated to Android 12, the latest on on asus website (WW-31.1004.0404.107), and then tried to flash LineageOS ROM, then he got some errors and went back to Android 12 and relocked the bootloader. He said he never tried anything again. When I got the phone it was on Android 12, I tried unlocking it as I said and it didn't work. Then I downgraded it to 11 using the firmware from asus website (Version Android 12 to Android 11), and tried to unlock it again using Android 11. Also didn't work.
About ADB and Fastboot drivers, they are correctly installed, tried some "standalone" versions and also the one that come with android SDK Platform Tools. Tested it on other devices and it worked well. And the phone was connected to the internet when I tried using the app, I'm sure because I downloaded it on the phone aswell, using the browser.
edit: Actually I'm not sure about the fastboot drivers, I've just downloaded the sdk tools from google website.
what lineageos did he flasah? if its 18.1 thats android 11... propably why he got the errors.
AJ205 said:
what lineageos did he flasah? if its 18.1 thats android 11... propably why he got the errors.
Click to expand...
Click to collapse
That's probably it. But there's any way to unlock the bootloader again so I can give it another try?
Aodh said:
That's probably it. But there's any way to unlock the bootloader again so I can give it another try?
Click to expand...
Click to collapse
are you sure you are locked? do you get the warning screen when you boot up?
AJ205 said:
are you sure you are locked? do you get the warning screen when you boot up?
Click to expand...
Click to collapse
I do get the warning screen, but also when checking with fastboot oem device-info it returns this:
C:\Users\delci\Desktop\platform-tools>fastboot oem device-info
(bootloader) Device unlocked: false
Aodh said:
I do get the warning screen, but also when checking with fastboot oem device-info it returns this:
C:\Users\delci\Desktop\platform-tools>fastboot oem device-info
(bootloader) Device unlocked: false
Click to expand...
Click to collapse
let me get this straight, your device is unlocked and you want to lock it? because:
Aodh said:
That's probably it. But there's any way to unlock the bootloader again so I can give it another try?
Click to expand...
Click to collapse
what are you trying to do? your device is unlocked. you cant unlock it again.... you can try to lock with : fastboot oem asus-csc_lk
AJ205 said:
let me get this straight, your device is unlocked and you want to lock it? because:
what are you trying to do? your device is unlocked. you cant unlock it again.... you can try to lock with : fastboot oem asus-csc_lk
Click to expand...
Click to collapse
The warning appears, but it is not unlocked. Every command fails, device-info says that my device is not unlocked., it is locked.
What I'm trying to do is unlock it.
Let me try to explain what happened again.
The phone has been unlocked to install LineageOS. It didn't work. The past owner then installed the stock rom and locked it using this command: 'fastboot oem asus-csc_lk'.
Then I bought the phone from him, and now I'm trying to unlock it again, but it doesn't work.
The question then is: Is it possible to unlock a phone that has previously been unlocked and then relocked?
Hey, did you got it to work ?