My one plus 3t no longer boots to the home screen. Just got stuck in the one plus logo then goes black screen. Tried resetting and all but no luck. I enter recovery mode and shows device state - locked. Tried unlocking bootloader using different tools but got error "remote " oem unlock is not allowed" . I need help.
You should use the usual qualcomm emergency recovery option found in this forum.
Related
I'm stuck.
My phone boots to the welcome screen all the way to the wifi selection but stops after that saying the setup wizard cannot launch. So I cannot go into phone settings to "enable OEM unlocking" to follow the official HTC procedure for the bootloader unlock (which was once unlocked but is now relocked).
I looks like I have no recovery, because I cannot boot into recovery, it just fails.
If I go to (what I thought was) Download/Fastboot mode and try to Fastboot flash twrp for example, it says: FAILED (remote: cannot flash this partition in s-on state) ----> but I then read that this was because I was NOT actually in Download Mode.
So I think I managed to get to Download mode and tried the Fastboot command to flash TWRP again and now it says: FAILED (remote: 9: SD_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCK).
I suppose it means that my Bootloader isnt unlocked...but as mention initially, I cannot access the OS and enable the OEM unlocking toggle.
Since Fastboot isnt working, I dont know if an RUU would work.... And look like I will never know because everytime I launche the EXE file, it extracts, asks me to to accept the conditions, then nothing happens...
Please help!!
maximepull said:
I'm stuck.
My phone boots to the welcome screen all the way to the wifi selection but stops after that saying the setup wizard cannot launch. So I cannot go into phone settings to "enable OEM unlocking" to follow the official HTC procedure for the bootloader unlock (which was once unlocked but is now relocked).
I looks like I have no recovery, because I cannot boot into recovery, it just fails.
If I go to (what I thought was) Download/Fastboot mode and try to Fastboot flash twrp for example, it says: FAILED (remote: cannot flash this partition in s-on state) ----> but I then read that this was because I was NOT actually in Download Mode.
So I think I managed to get to Download mode and tried the Fastboot command to flash TWRP again and now it says: FAILED (remote: 9: SD_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCK).
I suppose it means that my Bootloader isnt unlocked...but as mention initially, I cannot access the OS and enable the OEM unlocking toggle.
Since Fastboot isnt working, I dont know if an RUU would work.... And look like I will never know because everytime I launche the EXE file, it extracts, asks me to to accept the conditions, then nothing happens...
Please help!!
Click to expand...
Click to collapse
I am replying to myself. After trying several things on the phone, I went back to the OS's setup wizard. The second step (2 steps before the crash), has some text and one has a clickable link saying "learn more". It actually opens some phone settings, and from there, you can access all of the phone settings. So I was able to activate Dev mode, OEM unlock and debugging without going through the Wizard!!
Followed the BL unlock procedures on HTC website and as soon as it was unlocked, phone rebooted and TWRP reappeared! I'm saved!!
Thought I would share my discovery in case this ever happens to you too.
I also discovered another possible course of action. When accessing the same "link" to get to settings, go to the network settings and put the phone on Airplane mode. Go back to the setup wizard and skip the connection to wifi. I think it will skip the part of the Setup that made the OS crash.
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.
Hi guys,
I've a leeco le2, it's in some sort of bootloop. I now have a phone which I hope is not actually bricked.
To cut to the chase:
The phone boot loops - it shows the "Leeco" on the black background for less than a second, then reboots, after 2 seconds, it comes back up with the "Leeco" and reboots, and so on.
I can get into fastboot mode. Interestingly, the status shows "Device is LOCKED"
I cant get to recovery mode. It just goes into the boot loop again.
Using the adb tools, I cant issue the "fastboot flashing unlock" or "fastboot oem unlock" commands because it returns: "FAILED (remote: 'oem unlock is not allowed')"
I am unable to get into the phone OS to change the settings because the phone is boot looping
. I am flashed several time in flashone,qfil and Miracle thunder but problem is same.
Given the fact I am unable to get to recovery, I am unable to sideload an OTA zip. And given the fact that I cant boot into the OS, I cant enable oem unlocking.
Do I have any hope at resurrecting this phone in any way? please help me
Check this : https://forum.xda-developers.com/t/...-le-2-s3-noob-friendly.3515555/#post-69996355
I seem to be stuck in a boot loop. I can hit power button and volume up options to reboot, safe mode etc - tried all of them and unable to get past the MIUI logo - It just sits on the logo until the battery runs out. I can get into fastboot but unable to do anything once there - the bootloader is locked, and it seems the only way to unlock it is to allow it by going into developer mode on the phone - which I can't do because I'm stuck at the MIUI logo!
I have tried to use MIPCSuite, ADB/Fastboot tools - but like I say all commands fail as unable to unlock bootloader.
I don't mind losing any data - but is there any way to unbrick this? Thanks in advance!
Hey folks! I have an OG Pixel XL - Stock ROM and locked bootloader.
Yesterday my phone just rebooted - no warning, and is now stuck on the Google logo screen. I can get the bootloader up by holding PWR + Volume Down, but when I go into recovery mode, I just get the Google Logo again - not what is expected with the broken Android icon, and the "No command" message.
I'd love to be able to flash the ROM back onto it - either stock or third-party since the phone is still in good condition from a hardware perspective.
Any other ways to flash a phone that seems to be soft-bricked?
Thanks!
UPDATE: When I try to use fastboot flashing unlock or similar commands, I get an error "FAILED (remote: 'oem unlock is not allowed')"
Kevingwpg said:
Hey folks! I have an OG Pixel XL - Stock ROM and locked bootloader.
Yesterday my phone just rebooted - no warning, and is now stuck on the Google logo screen. I can get the bootloader up by holding PWR + Volume Down, but when I go into recovery mode, I just get the Google Logo again - not what is expected with the broken Android icon, and the "No command" message.
I'd love to be able to flash the ROM back onto it - either stock or third-party since the phone is still in good condition from a hardware perspective.
Any other ways to flash a phone that seems to be soft-bricked?
Thanks!
UPDATE: When I try to use fastboot flashing unlock or similar commands, I get an error "FAILED (remote: 'oem unlock is not allowed')"
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3730229/
spiral777 said:
https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3730229/
Click to expand...
Click to collapse
Doesn't seem to work. I get the same error that OEM Unlock is not allowed - I cannot flash TWRP