Database Develop

BRICK? Stuck at bootanimation

Hi folks, saw the bootloop thread that is ongoing, but have a different issue and dont want to hjack.
I was unlocked and rooted, but then started having some constant cell signal issues.
I loaded of the toolkit, tried flashing back to stock (flash stock / unroot) > then OEM lock.
Now I cant get past the boot animation.
Can get to bootloader, fastboot works, device is LOCKED, just cant boot into the system. have left it for about 30 minutes.
I cant flash any images because I am locked, but cant unlock because I cant get into the system.
any thoughts here?

jewnersey said:
Hi folks, saw the bootloop thread that is ongoing, but have a different issue and dont want to hjack.
I was unlocked and rooted, but then started having some constant cell signal issues.
I loaded of the toolkit, tried flashing back to stock (flash stock / unroot) > then OEM lock.
Now I cant get past the boot animation.
Can get to bootloader, fastboot works, device is LOCKED, just cant boot into the system. have left it for about 30 minutes.
I cant flash any images because I am locked, but cant unlock because I cant get into the system.
any thoughts here?
Click to expand...
Click to collapse
Locked bootloader? That may be a bad situation. What happens when you try to issue: fastboot oem unlock from command prompt?

Evolution_Freak said:
Locked bootloader? That may be a bad situation. What happens when you try to issue: fastboot oem unlock from command prompt?
Click to expand...
Click to collapse
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
just saw your thread.. ugh

formatted cache and userdata from fastboot and got to setup.. THANK LORD JEBUS
CLOSE THREAD

jewnersey said:
formatted cache and userdata from fastboot and got to setup.. THANK LORD JEBUS
CLOSE THREAD
Click to expand...
Click to collapse
Glad you're OK. :good:

jewnersey said:
formatted cache and userdata from fastboot and got to setup.. THANK LORD JEBUS
CLOSE THREAD
Click to expand...
Click to collapse
Good job:good:

Nexus 6 bricked after November Security OTA update?

Hello,
I have a stock Nexus 6, not rooted, with apps only from Google Play. Today I received the November security patch and was asked to reboot. After that the phone worked fine for 2 hours, and then froze. Unfortunately I was not able to boot it. Fastboot is loading but is unable to load the recovery image: "failed to validate recovery image: ret=-1" or "failed to validate boot image: ret=-1".
I then installed fastboot and adb. fastboot detects the phone, but I'm unable to unlock it:
Code:
$ fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.044s
adb is not detecting any device, so I don't know how to check the "Allow OEM Unlock" option - which is for some reason unchecked by default.
Is there any way around this or should I just give up?
Thanks!

Tomer Morad said:
Hello,
I have a stock Nexus 6, not rooted, with apps only from Google Play. Today I received the November security patch and was asked to reboot. After that the phone worked fine for 2 hours, and then froze. Unfortunately I was not able to boot it. Fastboot is loading but is unable to load the recovery image: "failed to validate recovery image: ret=-1" or "failed to validate boot image: ret=-1".
I then installed fastboot and adb. fastboot detects the phone, but I'm unable to unlock it:
Code:
$ fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.044s
adb is not detecting any device, so I don't know how to check the "Allow OEM Unlock" option - which is for some reason unchecked by default.
Is there any way around this or should I just give up?
Thanks!
Click to expand...
Click to collapse
you have to boot up, then enable the developer options(tap omn build number in about phone three times), then head back into system options, scroll down to developer options, then enable oem unlocking. now, boot into your bootloader, connect your phone via usb to your computer, start fastboot on your computer, then fastboot oem unlock. notice i never said adb? thats because adb is not involved here, fastboot is involved.

simms22 said:
you have to boot up, then enable the developer options(tap omn build number in about phone three times), then head back into system options, scroll down to developer options, then enable oem unlocking. now, boot into your bootloader, connect your phone via usb to your computer, start fastboot on your computer, then fastboot oem unlock. notice i never said adb? thats because adb is not involved here, fastboot is involved.
Click to expand...
Click to collapse
I think he is saying that the phone will not boot up. So he can't get to the dev options.

I'm afraid you'll need to send to the repair centre your mobile phone.
If you can't enable OEM UNLOCK option in the Developer Settings in android, you won't be able to unlock te bootloader.

Rektifying said:
I think he is saying that the phone will not boot up. So he can't get to the dev options.
Click to expand...
Click to collapse
Quetzalcoalt_Lp said:
I'm afraid you'll need to send to the repair centre your mobile phone.
If you can't enable OEM UNLOCK option in the Developer Settings in android, you won't be able to unlock te bootloader.
Click to expand...
Click to collapse
i wasnt even going to say repair center, as there isnt much they can try. an rma(factory replacement) might be your only option.

Yes, but what I mean is that he can't do anything. He is going to need to use his warranty.

Quetzalcoalt_Lp said:
Yes, but what I mean is that he can't do anything. He is going to need to use his warranty.
Click to expand...
Click to collapse
well, chances are that he bought the phone after it was released on oct 29 2014, so his phone should still be under warranty. so yup, and i wish him luck

simms22 said:
well, chances are that he bought the phone after it was released on oct 29 2014, so his phone should still be under warranty. so yup, and i wish him luck
Click to expand...
Click to collapse
Indeed I haven't found any key or menu combination that would allow me to boot and change this option
I hope T-Mobile will replace it under the warranty.
Thanks for the replies!

I know it doesn't help now... But for anyone reading this...
Unless your never going to attempt to fix anything, and will always just RMA...
ALWAYS ALWAYS ALWAYS unlock and leave your bootloader unlocked. By the time you decide otherwise, it may likely be too late.

Try plugging into the charger and leaving it for like 5 to 10 minutes then try and get to recovery to do a reset from there?

While it would stuck to set it up again, I'd try to factory reset and get the phone to start up before sending it in. It'll take 5 minutes at most, and may get you a working phone again.
Sent from my Nexus 6

MysticKing32 said:
Try plugging into the charger and leaving it for like 5 to 10 minutes then try and get to recovery to do a reset from there?
Click to expand...
Click to collapse
Hi, I tried what you suggested and it had no effect - I still can't enter recovery mode (image is unverified).

imnuts said:
While it would stuck to set it up again, I'd try to factory reset and get the phone to start up before sending it in. It'll take 5 minutes at most, and may get you a working phone again.
Sent from my Nexus 6
Click to expand...
Click to collapse
I would have loved to be able to do that, but I can't run any image on the device. I can't leave the fastboot menu.

Try a factory reset in the stock recovery: https://support.google.com/nexus/answer/4596836?hl=en

TWRP Fastboot Command not allowed (P10)

Hi!
I'm trying to install TWRP on my P10. I've unlocked bootloader on Huawei website.
Whenever I'm typing in fastboot "flash recovery twrp.img" it goes through and everything says OK
But when i try to "fastboot boot twrp.img" I get FAILED (remote: command not allowed)
"fastboot oem device-info" gives me the same error too and "fastboot oem unlock" gives me already fastboot unlocked

What do you thing "fastboot boot twrp.img" should do? This command isn't allowed because it does not exist.
If you want to boot into your flashed TWRP recovery, you have to enter "fastboot reboot" and press volume up while booting - the USB cable has to be disconnected.
Instead of "fastboot oem device-info" try "fastboot Gevtvar unlocked".

or use adb when the phone is running.
"adb reboot recovery"
you can't go direct from fastboot to recovery simply by a command

Yeah, the command was wrong, sorry xD
Anyway I thinks it's fixed now and I'm able to boot manually to recovery from phone now!

jejeje i was coming here to tell you about wrong command

I have the same problem with FAILED (remote: command not allowed). When I try to install or flash anything I see the info about FAILED (remote: command not allowed). I have FRP locked and I can't enable OEM developing option (it is inactive). I can't relock bootloader, can't instal TWRP, I have only simply erocevery where I can't wipe - only reboot and shutdown device.
I tried do update via dload, hwota - all with defeat
In ADB and Fastboot I can see my device connected.
Does anyone have any idea?

do you have instaled driver for P10, does computer recognice device like P10 ?

DiMeteo24 said:
I have the same problem with FAILED (remote: command not allowed). When I try to install or flash anything I see the info about FAILED (remote: command not allowed). I have FRP locked and I can't enable OEM developing option (it is inactive). I can't relock bootloader, can't instal TWRP, I have only simply erocevery where I can't wipe - only reboot and shutdown device.
I tried do update via dload, hwota - all with defeat
In ADB and Fastboot I can see my device connected.
Does anyone have any idea?
Click to expand...
Click to collapse
Any news? My p10+ it's in the same case

same problem im already unlock but the twr not install what is propper command

Hey guys, for all of you with "command not allowed" problem, you have to check OEM unlock setting on developer options but if you have a greyed out button, you need to flash again your stock room with a tool like dc-phoenix unlocker and bypass frp lock (on YouTube you will find tons of videos regarding this matter). Also, you can check if your Fastboot is protected (frp locked) on Fastboot screen...

There you go---> https://forum.xda-developers.com/hu...ution-bl-unlockedfrp-locked-fastboot-t3684302
PS READ the post to the END!! don't make mistakes it's really easy and fast. It works!

Hi guys.
I know this thread is pretty old but I'm getting the exact same problem as the OP except on my P20 Pro: I can flash a recovery but not boot one from fastboot.
The biggest difference is that my bootloader is unlocked and I have FRP Unlock, so according to every post I've seen it SHOULD be working.
My fastboot log:
PS C:\adb> fastboot devices
LCL0218415002142 fastboot
PS C:\adb> fastboot boot twrp-3.2.1-0-charlotte.img
downloading 'boot.img'...
OKAY [ 0.187s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.187s

Armand Bernard said:
Hi guys.
I know this thread is pretty old but I'm getting the exact same problem as the OP except on my P20 Pro: I can flash a recovery but not boot one from fastboot.
The biggest difference is that my bootloader is unlocked and I have FRP Unlock, so according to every post I've seen it SHOULD be working.
My fastboot log:
PS C:\adb> fastboot devices
LCL0218415002142 fastboot
PS C:\adb> fastboot boot twrp-3.2.1-0-charlotte.img
downloading 'boot.img'...
OKAY [ 0.187s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.187s
Click to expand...
Click to collapse
Have you try this command fasboot reboot recovery_ramdisk?

I get:
PS C:\adb> fastboot reboot recovery_ramdisk
fastboot: usage: unknown reboot target recovery_ramdisk
with "fastboot boot recovery_ramdisk" I get
error: cannot load 'recovery_ramdisk': No such file or directory

I sorted out my problem from a different angle so I no longer need to boot to TWRP from fastboot. Thanks for your help!

Question
Armand Bernard said:
I sorted out my problem from a different angle so I no longer need to boot to TWRP from fastboot. Thanks for your help!
Click to expand...
Click to collapse
Could you please tell me how did u solve this problem. thx

darkdante13 said:
Could you please tell me how did u solve this problem. thx
Click to expand...
Click to collapse
This was quite some time back so I don't remember all that well, but I think I just used the built in Huawei recovery, erecovery, to restore my whole phone and then I was able to reinstall my custom recovery and boot to it normally. I can't guarantee this as I don't remember the whole context of this. Using erecovery I didn't lose my locally stored files, only my apps and app data. Hope this helps.

Huawei P9 stuck In bootloop

what I have done is this:
Rooted phone
Installed TWRP
than I updated (stupid)
Lost root than I wanted to install Custom frimware what didnt work
Factory resetted phone, phone doesnt boot anymore now.
I can only access fastboot but I can not get fastboot to work on pc installed many different drivers just dont work.

lucmaas99 said:
what I have done is this:
Rooted phone
Installed TWRP
than I updated (stupid)
Lost root than I wanted to install Custom frimware what didnt work
Factory resetted phone, phone doesnt boot anymore now.
I can only access fastboot but I can not get fastboot to work on pc installed many different drivers just dont work.
Click to expand...
Click to collapse
Every two or three days people report here they bricked phones by forcing update or Factory reset (or relocking Bootloader) from custom or rooted phones (or by having TWRP) - one must first go back to the original stock firmware he had, before upgrading/resetting/relocking...
And this thread will also not help to somebody else -
since 'somebody' will not read (before bricking the phone) ;(
---
Do you still have TWRP - use HWOTA to flash stock
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
If you have no TWRP but Fastboot is showing Bootloader unlocked, you should be able to flash TWRP.
If Fastboot is showing Bootloader locked but FRP unlocked, you should be able to unlock Bootloader.
But if there is no more TWRP and Fastboot is showing FRP and Bootloader locked - maybe DC Phoenix can help you
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial

I used this command in fastboot: fastboot oem device-info
But I get this error: FAILED (remote: Command not allowed)
On my phone it says: Phone: unlocked and FRP: Lock

lucmaas99 said:
I used this command in fastboot: fastboot oem device-info
But I get this error: FAILED (remote: Command not allowed)
On my phone it says: Phone: unlocked and FRP: Lock
Click to expand...
Click to collapse
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick

zgfg said:
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
Click to expand...
Click to collapse
I cannot get into to recovery but when I let the phone die and than it starts normally,
but everytime it turns off its get back stuck in bootloop I got my oem key when it booted back but now I tried unlocking it agian but it says this:
C:\adb>fastboot oem unlock <code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.024s

lucmaas99 said:
I cannot get into to recovery but when I let the phone die and than it starts normally,
but everytime it turns off its get back stuck in bootloop I got my oem key when it booted back but now I tried unlocking it agian but it says this:
C:\adb>fastboot oem unlock <code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.024s
Click to expand...
Click to collapse
I cannot flash anything because I cannnot enable USB debugging in developers options

zgfg said:
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
Click to expand...
Click to collapse
What can I do I can access phone but cannot unlock bootloader because cannot use remote commands and I can not get into any recovery menu I am out of idea's

lucmaas99 said:
I cannot flash anything because I cannnot enable USB debugging in developers options
Click to expand...
Click to collapse
You can boot to system?
Which (full name) build it shows in About?
Can you enable Developer options - then why cannot you enable USB debugging?!
You must first enable Allow ADB debugging in charge... and only then USB debugging -otherwise USB debugging switches off

zgfg said:
You can boot to system?
Which (full name) build it shows in About?
Can you enable Developer options - then why cannot you enable USB debugging?!
You must first enable Allow ADB debugging in charge... and only then USB debugging -otherwise USB debugging switches off
Click to expand...
Click to collapse
Modelnumber: EVA-L19
Build: NRD90M test-keys
I think I should not supposed to have test-keys doesnt seem correct?

So I got my phone to boot but everytime I want to do something in recovery or something else It wont boot anymore and than I need to make the battery run out of juice. are there anyfix without needing root recovery or fastboot.

ADB wont work because usb debugging wont turn on (tried many things), Fastboot kinda works but gives the error (remote command not allowed)
Cannot get into any Recovery I can boot to OS

Can't erase via fastboot, even with unlocked bootloader.

I've been having connectivity issues with my phone ever since I flashed LineageOS. I've tried a ton of fixes, but none of them have solved it. I want to try the fix outlined here:
Go-to your phone bootloader mode connect pc adbfastboot command mode then type command.
Mfastboot erase modemst1
Enter
Mfastboot erase modemst2
Enter
Then reboot
Click to expand...
Click to collapse
But I can't get it to work. When I try to erase modemst1, I get this message:
FAILED (remote: 'Erasing is not allowed for partition')​
I thought perhaps I had relocked my bootloader, so I tried to unlock it again, but got this message:
FAILED (remote: 'Device already unlocked')​
Then I thought Magisk might be interfering with this, so I unstalled Magisk. But the message was the same.
What's causing this, and how do I fix?

Remove the "M" from the start of the command.

SXUsr said:
Remove the "M" from the start of the command.
Click to expand...
Click to collapse
Oh yeah, did that. I'm on a Mac so it's ./fastboot