Hi all, yesterday I updated the bootloader of my OnePlus X and today I accidentally rebooted it into fastboot mode, when I tried to reboot the device it started a bootloop. Now I can't even boot into recovery but only in fastboot. I also tried to flash TWRP with command prompt but it says that the device isn't unlocked (strange i'm sure it was till yesterday) so I tried to unlock it with "fastboot oem unlock" but it says that oem unlock is disabled. Please help me
To unbrick your phone use this
You can then update to 3.1.3 Stock with the default bootloader.
You need to enable OEM-unlock in the developer-settings else patching the new bootloader may lock it again had the same problem.
Nordii said:
To unbrick your phone use this
You can then update to 3.1.3 Stock with the default bootloader.
You need to enable OEM-unlock in the developer-settings else patching the new bootloader may lock it again had the same problem.
Click to expand...
Click to collapse
Thank you! It worked
Hi !
I had rooted my Honor 9 flashing ramdisk file through fastboot so I unlocked the bootloader and FRP and everything was fine. I was on Oreo. Now I wanted to go back to a stock unrooted Oreo phone. I used "fastboot oem relock
Code:
" but now my phone doesn't boot anymore.I didn't flash any unroot file. When I turn it on I have a Google logo and then Huawei eRecovery but it doesn't work. The phone now says in fastboot "Phone Relocked" and "FRP Lock". I'm used to flash samsung phones but I'm a bit confused with Honor/Huawei.
Any help please ?
nobody ?
closed. the phone is now dead...RIP
Hello all,
I have a Mate 10 Pro that I was having trouble updating, I assumed due to having TWRP installed. So, I tried to restore the stock recovery via fastboot flash.
However, the flash would always fail with "remote: Command Not Allowed" error. Googling showed this to be result of locked bootloader, but my phone was indeed unlocked. Indicated on the screen when in Download mode.
Some threads suggested relocking and then unlocking the bootloader again. So I ran fastboot oem relock, which restarted and factory reset the phone. Then I ran fastboot oem unlock and I am now getting the "remote: Command Not Allowed" error, and my phone remains locked and now it will not boot at all but only to the eRecovery screen which wants to connect to wifi and download a package but getting package info always fails. Oh, and since I didn't think to remove my account, the phone is also FRP locked.
I had found a thread before this incident saying to change the DNS in order to get the eRecovery download to work, and at the time it did. Now the only thread I find with that suggestion (81.177.139.39, not sure it's the same one) it still fails to get package info.
So as it stands I have a FRP locked, bootloader locked Mate 10 Pro that will only boot to eRecovery.
Anyone have any suggestions?
Hey guys,
so I got a Nokia 7.1 that has once been returned to the vendor after an upgrade failed.
My plan was to unlock the bootloader and flash TWRP - easy enough.
However I can't check "OEM Unlock" in developer options. It's simply greyed out.
I also can't enter any sort of recovery mode, it gives me the usual background for recovery (the android with its belly opened) and only says "No command". It then proceeds to reboot after ~15 seconds.
I cant enter the bootloader or download mode with hardware keys at all, gotta do it via ADB.
Long story short: I want to flash TWRP but I obviously can't get rid of the flashlock and neither can I wipe cache or data to reset it.
I've read about reasons for the OEM unlock being greyed out. Without going into details I got two Nokia 7.2 where I am able to OEM unlock, so I really don't think locale or vendor is blocking it.
Got any ideas?
Bootloader must be unlocked, see this . OEM Unlock doesn't work on 7.1.
Hello everybody,
My phone's battery died and I charged it. When I tried to turn it on, I saw this screen. I've tried clicking on the options but it's stuck in a loop and I don't understand what's happening.
If anyone has experienced this issue before, I'm reaching out for your help. Please assist me.
Flashing factory firmware in fastboot might be the only option. Doing such will wipe everything on your device though!
aimsjahan said:
Flashing factory firmware in fastboot might be the only option. Doing such will wipe everything on your device though!
Click to expand...
Click to collapse
Can't fastboot anything with a locked bootloader.Android flash tool might be the best way
sylveride08 said:
Hello everybody,
My phone's battery died and I charged it. When I tried to turn it on, I saw this screen. I've tried clicking on the options but it's stuck in a loop and I don't understand what's happening.
If anyone has experienced this issue before, I'm reaching out for your help. Please assist me.
Click to expand...
Click to collapse
Since your bootloader is locked the only way to flash the OS is to sideload the Full OTA via ADB or use Pixel Flasher to sideload it. If you happen to have OEM Unlocking enabled in Developer Options you can use Android Flash Tool as that will unlock your bootloader as long as OEM Unlocking is enabled. If it isn't, sideloading the OTA will be the only way to reinstall your OS to hopefully get you out of this.
shoey63 said:
Can't fastboot anything with a locked bootloader.Android flash tool might be the best way
Click to expand...
Click to collapse
Oops! You are right, mate.
Hello so I am stuck here
When I go to Android Flash Tool it's says :
"Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device. "
And when I tape in CMD the command "faastboot falshing unlock" it says
"FAILED (remote: 'flashing unlock is not allowed')
fastboot: error: Command failed"
Is there a way to unlock the devices states I have seen a video when
when a guy is using a unlock.bin he download at LG offcial site. Does Google have an alternative where can I download this type of file for my Pixel 6.
Google doesn't have an alternative. If you can't flash the OTA, and apparently you can't because OEM unlocking wasn't enabled in developer options, you need to get a hold of Google and explain your situation to them. You'll likely have to send it back to them, if able to do so.
You can't enable OEM unlock by fastboot/recovery.
Can you boot into recovery?
If yes, then this is your only way out!
Link
Use image of OTA, not Full!
aimsjahan said:
You can't enable OEM unlock by fastboot/recovery.
Can you boot into recovery?
If yes, then this is your only way out!
Link
Use image of OTA, not Full!
Click to expand...
Click to collapse
Unfortunately, it is not possible as my phone is showing that it is locked and I am unable to access the settings to unlock the OEM, since I am stuck in fastboot mode. Guess it's dead only if there is a way to unlock the OEM without going to setting.
sylveride08 said:
Unfortunately, it is not possible as my phone is showing that it is locked and I am unable to access the settings to unlock the OEM, since I am stuck in fastboot mode. Guess it's dead only if there is a way to unlock the OEM without going to setting. View attachment 5885311
Click to expand...
Click to collapse
You misunderstood!
You don't get to do anything from fastboot with OEM locked.
I asked if you can enter RECOVERY mode?
If yes, then visit the link I shared.
btw, why on earth you are flashing 'adb'?
aimsjahan said:
You misunderstood!
You don't get to do anything from fastboot with OEM locked.
I asked if you can enter RECOVERY mode?
If yes, then visit the link I shared.
btw, why on earth you are flashing 'adb'?
Click to expand...
Click to collapse
Unfortunately, when I go into recovery mode, it keeps looping back to the original screen in an infinite loop.
I lost hope and went to a repair shop, but they told me to contact Google. The customer service will send me a package to return my phone. I didn't know that the OEM was so important, I will activate it next time. Tanks for your helps ...