Is anyone on the Three network in the UK and have tried rooting or ROMming their phone??
I have been trying for a week now to access the bootloader (using 'adb reboot-bootloader') so i can use fastboot but the phone just restarts and boots up like normal. This to me suggests a locked bootloader.
After several calls to Three and an official complaint made, they insist the bootloader is unlocked yet when i went to the Three store the other day they say it is locked. Someone is lying!
Can anyone else on Three confirm if its locked or not??
All i want is to boot temporarily into TWRP and create a nandroid backup. Ive done this at work plenty of times yet I cannot do it on my own phone!! :/
You need to set the OEM lock to off in developer mode.
Sent from my SM-G935F using Tapatalk
alchopop said:
You need to set the OEM lock to off in developer mode.
Click to expand...
Click to collapse
I have set OEM Unlock and USB debugging and still no joy.
Someone at Samsung told me my phone is locked but Three still claim its not locked.
I have been able to get ODIN to see the phone but i cant risk flashing anything as Samsung have told me they wont repair my phone if i do.
All i want to do is boot the phone with a temporary recovery. For that i need fastboot but i cant get fastboot no matter what i do. Its should be so simple!
Related
So tonight my phone randomly froze and restarted itself, and is now perpetually stuck on the black screen with the white Google text. Every so often it restarts itself back to that point and stops. I was running Nougat from the beta program workaround.
I have done tons of research and am at a loss. So far I have:
-Booted into fastboot mode and attempted Recovery Mode. I can navigate using the volume keys until Recovery Mode shows up in red, but when I hit the Power button to select it the phone immediately boots back to the normal Google logo loop.
-Tried to flash a stock image via command line, no luck because of bootloader I think.
I might not be using all the right terminology, but it seems to me that I am stuck because I never enabled USB Debugging or Unlocked my Bootloader while the phone was working?
-If I go to CMD and type 'ADB devices' I just get a message saying "List of devices attached" and nothing else.
-If I type 'Fastboot Devices' then my phones serial number appears and it says fastboot next to it.
-If I type 'fastboot flashing unlock' it says "FAILED (remote: oem unlock is not allowed)
Does anyone have any ideas on how to fix this and get my phone working again?
Thanks in advance!
Galrash said:
So tonight my phone randomly froze and restarted itself, and is now perpetually stuck on the black screen with the white Google text. Every so often it restarts itself back to that point and stops. I was running Nougat from the beta program workaround.
I have done tons of research and am at a loss. So far I have:
-Booted into fastboot mode and attempted Recovery Mode. I can navigate using the volume keys until Recovery Mode shows up in red, but when I hit the Power button to select it the phone immediately boots back to the normal Google logo loop.
-Tried to flash a stock image via command line, no luck because of bootloader I think.
I might not be using all the right terminology, but it seems to me that I am stuck because I never enabled USB Debugging or Unlocked my Bootloader while the phone was working?
-If I go to CMD and type 'ADB devices' I just get a message saying "List of devices attached" and nothing else.
-If I type 'Fastboot Devices' then my phones serial number appears and it says fastboot next to it.
-If I type 'fastboot flashing unlock' it says "FAILED (remote: oem unlock is not allowed)
Does anyone have any ideas on how to fix this and get my phone working again?
Thanks in advance!
Click to expand...
Click to collapse
Lesson #1: always keep your bootloader unlocked.
Don't bother trying any fastboot commands, they will never work because your bootloader is locked. Don't bother trying any adb commands either, they won't work in fastboot/bootloader mode (they only work while booted into Android and in recovery). I hate to say it but you're basically screwed. With no access to fastboot, no access to recovery, and no access to there's literally zero you can do. This should be covered under warranty, though. When you say the Nougat "beta program workaround" what exactly do you mean?
Heisenberg said:
Lesson #1: always keep your bootloader unlocked.
Don't bother trying any fastboot commands, they will never work because your bootloader is locked. Don't bother trying any adb commands either, they won't work in fastboot/bootloader mode (they only work while booted into Android and in recovery). I hate to say it but you're basically screwed. With no access to fastboot, no access to recovery, and no access to there's literally zero you can do. This should be covered under warranty, though. When you say the Nougat "beta program workaround" what exactly do you mean?
Click to expand...
Click to collapse
Where if you got impatient for an OTA you could sign up for the android beta program to get Nougat (once it was officially released) and then opt out of the program without having to downgrade back to Marshmallow.
I was worried I might be screwed. I will call google tomorrow and see what can be done, although I am a little worried since I bought the phone from Best Buy instead of from the Google Play store
Galrash said:
Where if you got impatient for an OTA you could sign up for the android beta program to get Nougat (once it was officially released) and then opt out of the program without having to downgrade back to Marshmallow.
I was worried I might be screwed. I will call google tomorrow and see what can be done, although I am a little worried since I bought the phone from Best Buy instead of from the Google Play store
Click to expand...
Click to collapse
I'm not entirely sure how it works but I believe you'll need to contact Best Buy. Even so it should be covered by warranty.
Galrash said:
Where if you got impatient for an OTA you could sign up for the android beta program to get Nougat (once it was officially released) and then opt out of the program without having to downgrade back to Marshmallow.
I was worried I might be screwed. I will call google tomorrow and see what can be done, although I am a little worried since I bought the phone from Best Buy instead of from the Google Play store
Click to expand...
Click to collapse
In my experience, Best Buy will not honor manufacturer warranties on smartphones; So unless you bought their Geek Squad coverage, they will tell you to contact Huawei for a warranty RMA.
Contact Info for Warranty RMA:
Huawei Device USA
1-888-548-2934 (1-888-5HUAWEI)
Got ahold of Huawei and it was surprisingly easy and fast. They emailed me a shipping label I just have to drop my phone in the mail and send it to them and it will be covered under warranty. Luckily I have my old Nexus 6 to use until they get it back to me
Hi, I have a moto x style pure and it is on a bootloop. I have tried to send the fastboot codes for reset (erase userdata, erase cache) but keeps rebooting. So I tried to reinstall the complete system, but there is no software avaliable for the nphs 25.200.23 version I could only find the 25.200.22 version. If somebody could help me I would really appreciate.
Pdta: I could not enable oem unlock before the bootloop so I can´t reinstall a lower version of the software because of the locked bootloader. If somebody knows a way to unlock the bootloader (I have already did the test on the motorola web page but when I put the unlock code on fastboot it asks me to enable oem ulock via software) Sorry for my english is not my mother tongue.
Thanks in advance
vladimir1909 said:
Hi, I have a moto x style pure and it is on a bootloop. I have tried to send the fastboot codes for reset (erase userdata, erase cache) but keeps rebooting. So I tried to reinstall the complete system, but there is no software avaliable for the nphs 25.200.23 version I could only find the 25.200.22 version. If somebody could help me I would really appreciate.
Pdta: I could not enable oem unlock before the bootloop so I can´t reinstall a lower version of the software because of the locked bootloader. If somebody knows a way to unlock the bootloader (I have already did the test on the motorola web page but when I put the unlock code on fastboot it asks me to enable oem ulock via software) Sorry for my english is not my mother tongue.
Thanks in advance
Click to expand...
Click to collapse
As you wrote - with locked BL you can do... nothing.
Only You can wipe all in recovery mode - u can find "how to" with google.
Yeah I'm curious how come you didn't do a recovery in fast boot mode? I don't think you muffed any during a flash when your boot loader is locked.
dzidexx said:
As you wrote - with locked BL you can do... nothing.
Only You can wipe all in recovery mode - u can find "how to" with google.
Click to expand...
Click to collapse
The problem is that even wiping everything in recovery or via fastboot, the phone is still on a bootloop. So, thats why I am asking for help, or maybe somebody has the ota in a zip format or a full flash.
StankFiss said:
Yeah I'm curious how come you didn't do a recovery in fast boot mode? I don't think you muffed any during a flash when your boot loader is locked.
Click to expand...
Click to collapse
I tried to, and when it is done, keeps rebooting
You are locked... there is NOTHING we can do at this point other than a factory reset in recovery, if that fails to get the device booting and you cannot get it unlocked again (unlikely since OEM Unlocking gets turned off again when you re-lock), then the device is probably bricked.
I am a little curious how you got to this state... the only way you could have relocked the bootloader was on 200.22, so it must have booted then in order to take .23 OTA update... or what exactly happened? I doubt it would make a difference to help you, but the information might help others from bricking.
acejavelin said:
You are locked... there is NOTHING we can do at this point other than a factory reset in recovery, if that fails to get the device booting and you cannot get it unlocked again (unlikely since OEM Unlocking gets turned off again when you re-lock), then the device is probably bricked.
I am a little curious how you got to this state... the only way you could have relocked the bootloader was on 200.22, so it must have booted then in order to take .23 OTA update... or what exactly happened? I doubt it would make a difference to help you, but the information might help others from bricking.
Click to expand...
Click to collapse
Sure I can tell you my history.
My sister came with this phone she bought on the web. The problem was the data cable. It was faulty. And the battery was at 2%.
While I was looking for usb cable, the phone went off. So I did not thought in another thing just than let it charge for a while. After let it charge for 30 minutes, I tried to turn it on and it was only rebooting. So a said to myself: "Lets send fastboot commands for erasing userdata and cache, and then she can put her google account and using it" I have reset a lot of motorola phone before with this same method. After rebooting, the phone kept rebooting. Then I said: " Ok lets full flash the phone" But when I was searching for the firmware I could not find the same or higher version of the phone. There is only 25.200.22 on every website I have visited. And I cant unlock the bootloader because nobody actived the oem unlock when it was booting properly.
This is basically how my nightmares started. I was talking with some technitians and they say they need to replace the mainboard because when they try to flash it fails, of course cause they have an older version, and it is a hardware issue.
vladimir1909 said:
Hi, I have a moto x style pure and it is on a bootloop. I have tried to send the fastboot codes for reset (erase userdata, erase cache) but keeps rebooting. So I tried to reinstall the complete system, but there is no software avaliable for the nphs 25.200.23 version I could only find the 25.200.22 version. If somebody could help me I would really appreciate.
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-x-style/general/official-firmware-moto-x-purestyle-t3737472
Hey guys,
So the USB cable I was using to flash my fiance's ph-1 to an Oreo beta came unplugged halfway through the flash.
The phone is now in a bootloop. I can't get to recovery mode via VU+pwr or through the fastboot menu. I can use fastboot and my PC recognizes the phone. However, I forgot to tick allow bootloader unlock in Dev setting so I am unable to flash anything to the phone.
Edit: Wondering if there is still a way to get the phone recognized in QFIL with HS-USB mode... I have tried every button combination I can think of with no luck :/
Am I screwed?
Any help is greatly appreciated..
Cj250mills
cj250mills said:
Hey guys,
So the USB cable I was using to flash my fiance's ph-1 to an Oreo beta came unplugged halfway through the flash.
The phone is now in a bootloop. I can't get to recovery mode via VU+pwr or through the fastboot menu. I can use fastboot and my PC recognizes the phone. However, I forgot to tick allow bootloader unlock in Dev setting so I am unable to flash anything to the phone.
Am I screwed?
Any help is greatly appreciated..
Cj250mills
Click to expand...
Click to collapse
Ask essential for help, they should be able to sort this out. I think you'll have to send it back to them. In any case, please let us know how you manage to solve it.
Good luck
Sent from my PH-1 using Tapatalk
No luck from essential, they told me all they can do is offer an out of warranty replacement for 200 bucks. I really expected better from a company that actively promotes participating in their beta's so frequently online. :/
Doesn't make sense you must be leaving something out??
You couldn't have been flashing OB with a locked bootloader it would have just failed.
use fastboot getvar to check your bootloader status. if it is unlocked then unlock critical and flash the back to stock zip on this thread.
That will correct your issue they even have the OB3 out https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
You could even flash it through TWRP recovery as long as you bootloader is unlocked.
Hello I am posting in Q&A because I'm a new XDA user, I was not allowed to post in the dev channel.
I have an Essential phone that has been working great for the past few years, no issues, and it was running standard build receiving OTA updates, until the very last update, which soft bricked the phone.
The phone was never enabled in developer mode while in Android, and now, I can't boot the phone into android at all. The only thing I can do is get into fastboot.
Fastboot state shows DEVICE STATE - locked
Any commands I try to unlock flashing, or change slots, anything at all, I get the error that the device is locked so all commands to unlock fail.
Is there any way to unlock device state from fastboot? I saw a youtube video showing a way to use a chopped USB cable to enter emergency / EDL mode for Qualcomm-based Android devices, but have not seen anyone post that this was successful with the Essential
Does anyone know of any method to be able to unlock flashing from fastboot? Or any other method to un-brick an essential? I've attempted everything, on both Mac and PC, nothing works.
On mac or PC, I can query the device in fastboot and get a response, I just can't do anything to unlock anything!!
Many thanks in advance for any suggestions!
Same problem
Same thing happened to me. Same day as you. I can get fastboot but not adb but since the device is locked I can't flash. I've only had the phone about 6 months so I contacted customer support and they offered to replace the phone.
It might be a known issue because they didn't even try to address the fact that I could get fastboot connected but not adb. They just offered to replace.
Thanks for the info! I am -at least in this case- unfortunately an early adopter. I bought two essentials at the beginning of the pre-release.
Essential support checked my serial number and said the phone was out of warranty.
Has anyone been able to force the Essential into EDL mode to recover that way? It looks like you have to latch one of the USB pins to ground, or 5V, but I haven't found any detailed instructions on how to make this work on the essential...
Thanks again
Justin
I'm sure things have changed and I'm wrong, but if you can get into the fastboot menu can't you just cycle through the options until you get to recovery and then flash an official release from Essential?
I may be thinking of LG or something but this should be possible as long as it's newer than the current software installed because it will see it as an official update and allow the flash.
Thanks but unfortunately, when I try and do that, the phone just does the same thing, it hangs forever on the initial boot screen white Android text with the circle/square logo...
That's why I've been looking into the more direct hardware version of forcing the phone into EDL mode, which is supposed to be possible with all Qualcomm based phones.
I've just not found the time yet to find a USB-C cable I'd be happy to cut in half and short the pins on! Which is why I was hoping someone might have tried this with an essential before to know if it was successful before I start trashing good cables
Thanks again for your reply!
JB
justinbaird said:
Hello I am posting in Q&A because I'm a new XDA user, I was not allowed to post in the dev channel.
I have an Essential phone that has been working great for the past few years, no issues, and it was running standard build receiving OTA updates, until the very last update, which soft bricked the phone.
The phone was never enabled in developer mode while in Android, and now, I can't boot the phone into android at all. The only thing I can do is get into fastboot.
Fastboot state shows DEVICE STATE - locked
Any commands I try to unlock flashing, or change slots, anything at all, I get the error that the device is locked so all commands to unlock fail.
Is there any way to unlock device state from fastboot? I saw a youtube video showing a way to use a chopped USB cable to enter emergency / EDL mode for Qualcomm-based Android devices, but have not seen anyone post that this was successful with the Essential
Does anyone know of any method to be able to unlock flashing from fastboot? Or any other method to un-brick an essential? I've attempted everything, on both Mac and PC, nothing works.
On mac or PC, I can query the device in fastboot and get a response, I just can't do anything to unlock anything!!
Many thanks in advance for any suggestions!
Click to expand...
Click to collapse
I have the exact same problem,
My phone is stuck on Essential log when I turned it on,
I can access Bootloader normally but the device is locked so I cannot flash it,
Recovery is corrupted, when I try to star it, it shows only the the Essential log and freeze so I can not format or wipe or sideload.
OEM Locked and unchecked
USB Debugging is unchecked
and I can't flash anything,
Did you managed to unlock it through Fastboot command or any other way ?
I wish I can just login to the recovery or unlock it so I can flash it clean,
Kindly help me if you found a way out
Thank you
Hi, I need help with my evice, I used a script founded in a thread here to flash stock rom 8.0 oreo, but that locked the bootloader now I cant unlock it because when phone starts im stuck on oreo wizard with no wifi or data to acces oem unlock in developer settings, is there any way to skyp this wizar or to flash with locked bootloader, wherever i tried to flash another frimware i have the error mesage, Bootloader "Permission Denied".
Thanks in advance!
sorry bad spelling, is not my native lenguage.
You can skip the wizard with just giving it ok everywhere and it will eventually end
For the unlocking here's a tool to share internet from pc to your phone
https://github.com/Genymobile/gnirehtet
juampapo546 said:
You can skip the wizard with just giving it ok everywhere and it will eventually end
For the unlocking here's a tool to share internet from pc to your phone
Click to expand...
Click to collapse
Can't pass the wizard cuase it ask for internet and I can't use that tool cause it need debug to work wich I can't activate without passing the wizar, is there another way?
Thanks!
coredeing said:
Can't pass the wizard cuase it ask for internet and I can't use that tool cause it need debug to work wich I can't activate without passing the wizar, is there another way?
Thanks!
Click to expand...
Click to collapse
Did you try to unlock the bootloader via fastboot?
WoKoschekk said:
Did you try to unlock the bootloader via fastboot?
Click to expand...
Click to collapse
Yes but it says that I need to turn oem unlock on the developer options since I cannot pass the wizard I cant tur the option on. =c
Coredesing said:
Hi, I need help with my evice, I used a script founded in a thread here to flash stock rom 8.0 oreo, but that locked the bootloader now I cant unlock it because when phone starts im stuck on oreo wizard with no wifi or data to acces oem unlock in developer settings, is there any way to skyp this wizar or to flash with locked bootloader, wherever i tried to flash another frimware i have the error mesage, Bootloader "Permission Denied".
Thanks in advance!
sorry bad spelling, is not my native lenguage.
Click to expand...
Click to collapse
Even if you get past the wizard, you still wouldn't be able to re-unlock the bootloader. It would stay gray forever. The only solution now is to get your phone hard bricked so you can enter edl mode and re-unlock it. You need either a deep flash cable, or short the 2 connection JTAG points from the motherboard. I'm on the same boat, but never got to do this to confirm if it works.
mrsiri said:
Even if you get past the wizard, you still wouldn't be able to re-unlock the bootloader. It would stay gray forever. The only solution now is to get your phone hard bricked so you can enter edl mode and re-unlock it. You need either a deep flash cable, or short the 2 connection JTAG points from the motherboard. I'm on the same boat, but never got to do this to confirm if it works.
Click to expand...
Click to collapse
NO, you can pass the wizard with no internet connection, I did it several times on my evert, just keep saying yes to everything (unless you frp locked which would be weird since is not by default enabled) Once you pass the wizard use the tool I provided previously to unlock bl