Hi,
I`m the owner of a new Sony Xperia E1.
The phone comes from the Polish distribution of smartphones for Orange mobile, but
had its simlock taken off. I checked its bootloader status and it was locked: Bootloader
unlock allowed: no. Out of curiosity, I launched the ADB console and wrote:
Code:
[email protected]:/ $ reboot bootloader
The phone instantly went into fastboot mode (the blue diode,
the device was found by Windows, drivers were found), which seemed strange
to me. Flashtool shows the device is connected in fastboot mode, while theoretically
this mode should be blocked. Consequently, I have got a question: can I try to unlock
bootloader without running the risk of damaging the phone in any way?
Related
I've bought this phone for 35 € thinking I would put at least android 5.1 on it, but no. I cannot unlock bootloader however I try. The problem is I cannot get into fastboot mode (when LED is blue) only into the other mode when is green. If I hold volume up phone just boots up normally. So is there any fix for this or is it really impossible to do? I have the bootloader unlock key.
Of http://wiki.lineageos.org/devices/huashan/install
Dial *#*#7378423#*#* (*#*#SERVICE#*#*) to launch the service menu.
Go to service info > configuration and check “rooting status” - you can only continue if it says Bootloader unlock allowed: Yes.
If you have No, you can search LBL rom
My bootloader said no so that's probably why I couldn't access fastboot, but thankfully I found some program that installs 3 recoveries from PC and bootloader doesn't need to be unlocked. After that I installed resurrection remix which also doesn't require unlocked bootloader and my phone now runs almost without any problems, the only one is buggy sim card pin verification which doesn't let me use my sim card ever if I enter my pin.
Hi,
I have a P9 here I'm was asked to repair. I think it is kind of bricked and I hope some one can help me to unbrick it.
According to the auto dc-unlocker identification:
Found Phone : EVA-L09
Firmware : EVA-L09C432B386
FB LockState: LOCKED
USER LockState: LOCKED
So, bootloader locked and FRP locked. I don't know if the Firmware version above is right. All I know is that some Update.app files were flashed to the state of the phone now and before there where bootloops while the start animation and stuck boot with black screen.
At the moment I can do:
- turn on to see only the first huawei log with "powered by android", then nothing happens
- I can not enter eRecovery or update for Update.app
- I can only enter fastboot
I have the unlock code for the bootloader. I can not commit any fastboot commands (oem unlock, flash, etc) all is blocked with:
FAILED (remote: Command not allowed)
The locked FRP should be the reason for this.
I think OEM-unlock and usb debug from developer section was not enabled as the phone was usable. adb commands like "adb reboot bootloader" fail with
error: device '(null)' not found
fastboot devices shows the device
I have tried to uncharge the battery and then try to enter other modes than fastboot. No luck with that.
Do I have any chance to unbrick it without paying for the dc-unlocker/phoenix?
Can I do something with SRKTool?
If I have to use unlocker,
- do I have to unlock the bootloader?
- should I flash the same firmware that is now on the phone (B386) and where can I find it? (found only 1000 other versions until now)
Hope for answers
I've gone through that before, but ended up using DC-Phoenix to unbrick it when it's FRP and bootloader locked. Cost me about $15. There is a post on how to do this but I'll have to search for it again.
Here is the post I used:
https://forum.xda-developers.com/showpost.php?p=71767614&postcount=7
I guess you enter fastboot by Vol- and Power?
Not sure if the following method could help you with, but you can analyze before you go for dc-phoenix:
https://forum.xda-developers.com/showpost.php?p=74169408&postcount=7
scammander said:
Hi,
I have a P9 here I'm was asked to repair. I think it is kind of bricked and I hope some one can help me to unbrick it.
According to the auto dc-unlocker identification:
Found Phone : EVA-L09
Firmware : EVA-L09C432B386
FB LockState: LOCKED
USER LockState: LOCKED
So, bootloader locked and FRP locked. I don't know if the Firmware version above is right. All I know is that some Update.app files were flashed to the state of the phone now and before there where bootloops while the start animation and stuck boot with black screen.
At the moment I can do:
- turn on to see only the first huawei log with "powered by android", then nothing happens
- I can not enter eRecovery or update for Update.app
- I can only enter fastboot
I have the unlock code for the bootloader. I can not commit any fastboot commands (oem unlock, flash, etc) all is blocked with:
FAILED (remote: Command not allowed)
The locked FRP should be the reason for this.
I think OEM-unlock and usb debug from developer section was not enabled as the phone was usable. adb commands like "adb reboot bootloader" fail with
error: device '(null)' not found
fastboot devices shows the device
I have tried to uncharge the battery and then try to enter other modes than fastboot. No luck with that.
Do I have any chance to unbrick it without paying for the dc-unlocker/phoenix?
Can I do something with SRKTool?
If I have to use unlocker,
- do I have to unlock the bootloader?
- should I flash the same firmware that is now on the phone (B386) and where can I find it? (found only 1000 other versions until now)
Hope for answers
Click to expand...
Click to collapse
So you can not update via dload method? Did you try booting into recovery (not Recovery)? And you can't update with Update.app, you need to flash update.zip and full_update.zip via TWRP or Recovery. What wanted the owner of this phone to do, that he bricked it ?
Thank you all for your answers. Like I tried to describe: I was not able to access any other mode than fastboot.
"was able": I used DC-Phoenix now and it worked just fine.
Little confusing is that in all tutorials, even the on on the DC site, the UI of the tool is different.
But that's now Problem. The current Version is lot easier. Just "Standard Mode", select Update.app (full), Click Update.
The Phone gets flashed with fastboot, DC will restart it to update mode and will flash again. All automatic.
Really easy.
so you paid 15 USD ?
DallasCZ said:
so you paid 15 USD ?
Click to expand...
Click to collapse
Yes I did, and it worked.
So recently I tried rooting my xperia xp and it has failed horribly. I managed to unlock my bootloader and install twrp recovery but after doing so my phone could not reboot into system without running into a bootloop. I've tried to perform a software repair on my phone with the xperia companion, but as you know my bootloader is unlocked at the moment so that couldn't help me.
The issue with relocking here is that when I enter "./fastboot oem lock" on my terminal it replies as:
"FAILED (remote: unknown command)"
I really do not want to have to purchase a new phone just because of the bootloader, it'd be so so appreciated if somebody could help me out here
Also
I'd also like point out that I've also tried the other two commands I could find:
"./fastboot oem relock" and "./fastboot flashing lock"
There are two ways to relock bootloader:
1. Restore TA partition
2.Use Flashtool to relock
But if you encounter a bootloop after unlocking bootloader, try flash Magisk first.
Sony Xperia XZ Premium (single sim, G8141) owner here.
Is there really no way to relock the bootloader?
I don't have a TA backup. I have flashed a completely stock ROM with flashtool (Emma), I just want to relock a bootloader for a warranty claim (purely hardware, faulty USB connector, took me 20 minutes to get the computer to recognize it, at this point it won't even charge most of the time).
I have tried fastboot oem relock command even with the USB vendor ID that I also had to specify when unlocking it in the first place. New flashtool (Emma) does not seem to have any option to relock (or even unlock) BL, nor does it display any information about it. Old flashtool says TA read fail and that my bootloader cannot be relocked.
The boot screen tells me to please lock my bootloader so I'm assuming there must be a way, I just haven't found it yet.
Phone info
OPPO A74 5G
Model number - CPH2197
Build number - CPH2197_11_A.12
Android 11
Developer Mode enabled
OEM Unlock enabled
USB Debugging enabled
Below are screenshots of all of the above
[Screenshots](https://imgur.com/a/qw0fUAw)
Phone is recognised by ADB but not Fastboot and as such I cannot unlock the Bootloader. Is there something I've done wrong or something else I can try?
When entering "Fastboot devices" in CMD nothing comes up.
When entering command "ADB reboot Bootloader" in CMD the phone restarts instead of loading into Bootloader.
I have tried turning phone off and the pushing power button + vol up - this just keeps restarting phone.
Any help would be much appreciated as I'd really like to root this phone all extra info in images on Imgur. Link above.
DeeSkye said:
Phone info
OPPO A74 5G
Model number - CPH2197
Build number - CPH2197_11_A.12
Android 11
Developer Mode enabled
OEM Unlock enabled
USB Debugging enabled
Below are screenshots of all of the above
[Screenshots](https://imgur.com/a/qw0fUAw)
Phone is recognised by ADB but not Fastboot and as such I cannot unlock the Bootloader. Is there something I've done wrong or something else I can try?
When entering "Fastboot devices" in CMD nothing comes up.
When entering command "ADB reboot Bootloader" in CMD the phone restarts instead of loading into Bootloader.
I have tried turning phone off and the pushing power button + vol up - this just keeps restarting phone.
Any help would be much appreciated as I'd really like to root this phone all extra info in images on Imgur. Link above.
Click to expand...
Click to collapse
Did you find a way? I tried everything but I couldn't get into fastboot
No way to enter fastboot mode for oppo phones. Now I use Oppo A74 4G version. Cannot enter fastboot mode. It's locked by Oppo. And they don't give bootloader code for unlock BL. Only way is to change phone
I've been trying run fastboot too. 4 hours later I find this thread. That explains it
Last Oppo phone I buy I guess.
Did you manage to find a workaround for this by chance?
Has anyone tried rebooting from recovery to then enter fastboor or?
Im gonna look into myself soon...
Ive seen this issue before on a different phone but cant remember how they bypassed it
Perhaps yall can try to find a post where they did so.. maybe it'll work on this phone too.
I was able too get to fastboot mode. The phone labels it "recoveryd mode", however, fastboot commands work.
1st. Connect phone and confirm ADB is connected by using "ADB devices" command.
2nd. Enter "adb reboot fastboot bootloader"
Phone will reboot into "recoveryd mode". It looks exactly like the normal recovery mode except the title displayed after you select the language and fastboot commands will work.
However, I still have not found out how to unlock the bootloader, so it does me no good.
try doing adb reboot fastboot or adb reboot bootloader
fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
guys ,, fails
when trying to boot to fastboot and not fastbootd
Hi I've a pixel5, it was reset to V11 software for compatibility with my son's medical device. Now with added security the app wont work because the bootlaoder is open. When I boot it say sits unlocked and to visit g.co/ABH
I've tried but cannot get it closed
When I go to fastboot I get the 'no command'.. on tring to flash it allows me to see the device and reboot the bootloader BUT then it will not respond to the cmd fastboot devices. when I try fastboot flashing lock it just says <waiting for device>
Any help? !
Billy
Try installing the usb driver https://developer.android.com/studio/run/win-usb
billyedit said:
Hi I've a pixel5, it was reset to V11 software for compatibility with my son's medical device. Now with added security the app wont work because the bootlaoder is open. When I boot it say sits unlocked and to visit g.co/ABH
I've tried but cannot get it closed
When I go to fastboot I get the 'no command'.. on tring to flash it allows me to see the device and reboot the bootloader BUT then it will not respond to the cmd fastboot devices. when I try fastboot flashing lock it just says <waiting for device>
Any help? !
Billy
Click to expand...
Click to collapse
I'm confused about "sits unlocked" and if this means you're stuck on the unlocked bootloader warning screen. If the phone hangs you're better off keeping the bootloader unlocked until that problem is sorted out. If it's starting, on the other hand...
Waiting for device means fastboot isn't communicating with the phone. Could be USB drivers. But if you flashed Android 11 from the same computer, drivers were working then, right?
In Developer options make sure USB debugging is enabled. While there, and while the bootloader is still unlocked, make sure OEM unlock is in the On position; it will flip back to Off when the bootloader is locked again.
Use Platform Tools 33.0.3 when trouble shooting USB to avoid trouble shooting Platform Tools 34.x.x.
As long as you get serial number output from commands adb devices and fastboot devices, fastboot flashing lock should work to re-lock the bootloader. Remember to finalize locking with the phone buttons.
Thank you both is was indeed the USB driver that needed the google update... All is well! thanks