Database Info

Bootloop! Unable to flash stock rom or lock bootloader (Help)

Hi. I can't get passed the google splash screen on a Nexus 5 D821 and could use some help.
Here are the facts:
* The owner of the device told me it bricked after an update.
* The Bootloader is unlocked. When i tried to lock i got the following message:
Code:
fastboot oem lock
...
OKAY [ 0.041s]
finished. total time: 0.041s
But it wasnt persistent. When given reboot comand the phone switched OFF instead. I turned it on to bootloader again and it was still unlocked.
* I tried flashing stock rom LRX22c manually after a failed attempt with the flash-all script. I got the following error for bootloader, radio, boot and recovery:
Code:
FAILED (remote: flash write failure)
* I tried erasing cache and flashing userdata but the after over 60 minutes waiting i came to the conclusion that i wasnt going anywhere and just rebooted the phone.
*The only thing im actually able to flash without an error message is system.img:
Code:
fastboot flash system ~/Downloads/hammerhead-lrx22c/image-hammerhead-lrx22c/system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.127s]
sending 'system' (981472 KB)...
OKAY [ 30.934s]
writing 'system'...
OKAY [ 62.705s]
finished. total time: 93.767s
* I tried booting TWRP, but i was unable to mount the file system (perhaps because i wasnt able to flash it. i used "fastboot boot twrp.img").
Are phones technically able to get to splash screen or bootloader with a damaged NAND or EEMC chip? Im starting to consider the possibility of a hardbrick. Why would i be able to write system.img if that was the case though? Any help is welcome
===============================================
alright so im pretty sure its a hard brick. The emmc is dead. its a shame :/ guess ill just try to sell it for parts. I would delete this thread because its pretty useless, but i have created my account a few days ago, and i ddont know how to.

You've only flashed the system img?
Do all the img's one by one. Recovery, boot, system, radio, userdata. Then fastboot reboot
Sent from my Nexus 5 using Tapatalk

Ben36 said:
You've only flashed the system img?
Do all the img's one by one. Recovery, boot, system, radio, userdata. Then fastboot reboot
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have tried all of the imgs in their respective order. they all failed. i got the error
Code:
FAILED (remote: flash write failure)
. system.img was the only .img i was able to write, and i was wondering why. Also, when i try fastboot reboot the phone switches off. It doesnt reboot.

[SOLVED] Needed Stock Recovery for EVA-L19

Hi,
after having TWRP, the factory reset function won't work since the data partition isn't recognized yet. Does anyone have the stock recovery version for this?
i already tried downloading from http://huaweidevices.ru/huaweiserviceworkarchivehuawei/eva-l19/recovery.img but it fails with the below message:
fastboot.exe flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (35180 KB)...
OKAY [ 1.318s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.318s
edit: found out the issue was related to the allow OEM unlock as turned off

is your bootloader still unlocked?

4Fighting said:
is your bootloader still unlocked?
Click to expand...
Click to collapse
Yups, still unlocked bootloader and currently on twrp recovery, but will need stock recovery if any operations like upgrade or factory reset needs to be done.

Can't install TWRP

Hi,
I recently want to root my Honor 8 FRD-L09 on N 7.0.
So i unlock the bootloader, and flash the recovery.
But i never could do it, I always got an error with fastboot
C:\Users\Hugo\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.386s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.392s
I don't know what to do.

are you sure you dont have FRP lock activated?
well thats why it wont flash. BL unlocked means nothing if you're FRP locked. you have 2 choices. try removing all security options and accounts / factory reset and hope FRP lock is removed, or use dload method to reflash stock rom. you wont be able to flash twrp otherwise, well, unless u use some of those "pay to remove FRP lock" tools

hypnotik8systeme said:
are you sure you dont have FRP lock activated?
well thats why it wont flash. BL unlocked means nothing if you're FRP locked. you have 2 choices. try removing all security options and accounts / factory reset and hope FRP lock is removed, or use dload method to reflash stock rom. you wont be able to flash twrp otherwise, well, unless u use some of those "pay to remove FRP lock" tools
Click to expand...
Click to collapse
Yes i got frp lock i will try To see tomorrow

ImEraaz said:
Yes i got frp lock i will try To see tomorrow
Click to expand...
Click to collapse
Did it work? If, can you tell me how you did it?

ImEraaz said:
Hi,
I recently want to root my Honor 8 FRD-L09 on N 7.0.
So i unlock the bootloader, and flash the recovery.
But i never could do it, I always got an error with fastboot
C:\Users\Hugo\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.386s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.392s
I don't know what to do.
Click to expand...
Click to collapse
FRP lock and system security triggers in bootloader itself cause that some partition/blocks are unaccessible even when there is a "full" unlocked bootloader, but full unlocked bootloader option is not as it should be.
Security options while flashing some partition and the system flashing boot loops security option enables this well known security feature.

ImEraaz said:
Hi,
I recently want to root my Honor 8 FRD-L09 on N 7.0.
So i unlock the bootloader, and flash the recovery.
But i never could do it, I always got an error with fastboot
C:\Users\Hugo\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.386s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.392s
I don't know what to do.
Click to expand...
Click to collapse
Enable OEM unlock.... In developer setting

Hard Bricked FRD-L14 "FAILED (remote: Command not allowed)

So for the past week, my phone has been bricked. Bricked by flashing the wrong firmware, so now not able to access the whole phone, and making matters worse by flashing the wrong recovery for the phone. The phone being an Honor 8, FRD-L14, 64GB.
I'm not able to use dload to rollback anything, or use that option at all, since the recovery isn't eRecovery, and doesn't even have any recovery in itself.
The problem is that I'm able to boot into "download mode" my phones unlocked, and when I type in "fastboot oem get-bootinfo", the response is:
(bootloader) unlocked
OKAY [ 0.008s]
finished. total time: 0.010s
But when trying to flash anything through fastboot in the cmd, like the command "fastboot flash recovery recovery.img" to flash a recovery on the phone, the response would then be:
target reported max download size of 471859200 bytes
sending 'recovery' (29378 KB)...
OKAY [ 0.803s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.814s
My phone is unlocked, and on the download mode screen, is shows:
PHONE Unlocked
FRP Unlock
My drivers are installed, as well as the device being shown in fastboot when typing in the command "fastboot devices"
I haven't been able to do a single thing to the phone, and have searched up a countless amount of hours to find the fix for the phone, if anyone can, please look into the problem and assist me, thanks .

Kc4k12 said:
So for the past week, my phone has been bricked. Bricked by flashing the wrong firmware, so now not able to access the whole phone, and making matters worse by flashing the wrong recovery for the phone. The phone being an Honor 8, FRD-L14, 64GB.
I'm not able to use dload to rollback anything, or use that option at all, since the recovery isn't eRecovery, and doesn't even have any recovery in itself.
The problem is that I'm able to boot into "download mode" my phones unlocked, and when I type in "fastboot oem get-bootinfo", the response is:
(bootloader) unlocked
OKAY [ 0.008s]
finished. total time: 0.010s
But when trying to flash anything through fastboot in the cmd, like the command "fastboot flash recovery recovery.img" to flash a recovery on the phone, the response would then be:
target reported max download size of 471859200 bytes
sending 'recovery' (29378 KB)...
OKAY [ 0.803s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.814s
My phone is unlocked, and on the download mode screen, is shows:
PHONE Unlocked
FRP Unlock
My drivers are installed, as well as the device being shown in fastboot when typing in the command "fastboot devices"
I haven't been able to do a single thing to the phone, and have searched up a countless amount of hours to find the fix for the phone, if anyone can, please look into the problem and assist me, thanks .
Click to expand...
Click to collapse
You're in a tough situation my friend, what do you get when you try the dload method? In my opinion this is the only thing you can do. However i heard about a thing called "DC Unlocker" . It can flash a clean ROM and other good stuff for bricked Huawei phones, but you have to pay, and i don't know what the prices are. Hope you'll make it

Unable to restore Pixel 2 to Factory

Hey everyone!
I'm a long time reader, but never had the occasion to post until now. I have somewhat recently started tinkering with my phones. I'm a programmer by trade so I'm not at all seperated from technology, however, I fear I may have gotten myself into a but of a ?.
So, here's what I broke: I have a Verizon Wireless Pixel 2. A few weeks ago I read that there was a boot loader unlock for it. As such, I rebooted to the boot loader, ran the "fastboot flashing lock_critical" command. After being unlocked I then proceeded to flash TWRP and then Magisk Manager. All was well until my phone had an unrelated warranty issue. As such, I filed a claim, and got my new phone.
Today I was trying to recover my phone to factory and am getting a few errors. I downloaded this Image from Google "8.0.0 (OPD3.170816.023, Nov 2017, Verizon) - https://dl.google.com/dl/android/aosp/walleye-opd3.170816.023-factory-f269631e.zip"). I extracted it, and ran "flash_all.bat". Througout the process I get an error stating that it can't find a recovery.img. I looked in the .zip and found that to be true. I downloaded the standard stock .zip and noticed it doesn't have one either. In addition, when it gets to the part about flashing the system image I get the following error:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: REMOVED
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ -0.000s]
sending 'boot' (32768 KB)...
OKAY [ 0.744s]
writing 'boot'...
OKAY [ 0.000s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.589s]
writing 'system'...
OKAY [ -0.000s]
sending sparse 'system' (524284 KB)...
FAILED (remote: No such partition.)
finished. total time: 13.631s
Anyone have any idea how to remedy this? I'm simply trying to get it back to stock. In addition, if I can get it returned to stock is relocking the bootloader even possible?
Thanks in advance for any help!
-Sofie

is your phone currently on 8.0.0 or have you been updated to at least 8.1?
you can't flash to a lower version than what you already have. i have verizon and i plan on flashing back to stock and you should be flashing to the 013 version from January.

iridium7777 said:
is your phone currently on 8.0.0 or have you been updated to at least 8.1?
you can't flash to a lower version than what you already have. i have verizon and i plan on flashing back to stock and you should be flashing to the 013 version from January.
Click to expand...
Click to collapse
It was on 8.1. Makes sense, I'll download the latest and try that. I just chose that because it says "VZW" in the name.

iridium7777 said:
is your phone currently on 8.0.0 or have you been updated to at least 8.1?
you can't flash to a lower version than what you already have. i have verizon and i plan on flashing back to stock and you should be flashing to the 013 version from January.
Click to expand...
Click to collapse
SweetSofie said:
It was on 8.1. Makes sense, I'll download the latest and try that. I just chose that because it says "VZW" in the name.
Click to expand...
Click to collapse
Well, that didn't help at all. :crying:

SweetSofie said:
Well, that didn't help at all. :crying:
Click to expand...
Click to collapse
try everything over and start clean:
1) delete all your stuff from your comp (all previous tools and images)
2) download the fresh set of latest adb tools from google
3) download the latest walleye stock image from google
4) put all those things in the same directory and uncompress them there (so flash-all.bat is in the same folder as adb, along with the img and zip files for walleye).
5) adb reboot bootloader
6) flash-all
are those similar to the steps that you did before?

SweetSofie said:
Hey everyone!
I'm a long time reader, but never had the occasion to post until now. I have somewhat recently started tinkering with my phones. I'm a programmer by trade so I'm not at all seperated from technology, however, I fear I may have gotten myself into a but of a ?.
So, here's what I broke: I have a Verizon Wireless Pixel 2. A few weeks ago I read that there was a boot loader unlock for it. As such, I rebooted to the boot loader, ran the "fastboot flashing lock_critical" command. After being unlocked I then proceeded to flash TWRP and then Magisk Manager. All was well until my phone had an unrelated warranty issue. As such, I filed a claim, and got my new phone.
Today I was trying to recover my phone to factory and am getting a few errors. I downloaded this Image from Google "8.0.0 (OPD3.170816.023, Nov 2017, Verizon) - https://dl.google.com/dl/android/aosp/walleye-opd3.170816.023-factory-f269631e.zip"). I extracted it, and ran "flash_all.bat". Througout the process I get an error stating that it can't find a recovery.img. I looked in the .zip and found that to be true. I downloaded the standard stock .zip and noticed it doesn't have one either. In addition, when it gets to the part about flashing the system image I get the following error:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: REMOVED
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ -0.000s]
sending 'boot' (32768 KB)...
OKAY [ 0.744s]
writing 'boot'...
OKAY [ 0.000s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.589s]
writing 'system'...
OKAY [ -0.000s]
sending sparse 'system' (524284 KB)...
FAILED (remote: No such partition.)
finished. total time: 13.631s
Anyone have any idea how to remedy this? I'm simply trying to get it back to stock. In addition, if I can get it returned to stock is relocking the bootloader even possible?
Thanks in advance for any help!
-Sofie
Click to expand...
Click to collapse
Just so you know, those "archive does not contain" errors are normal. I get them all the time. Always did on the original Pixel too. I'm not sure about the one at the end. Can't say I've ever seen that on either the Pixel 1 or 2.

SweetSofie said:
Well, that didn't help at all. :crying:
Click to expand...
Click to collapse
Were you able to sort out your issue?
If not, I have heard good things about using this tool to install the latest factory image. Just download this script and follow the instructions in that thread.
If that goes well, then you should be able to boot to the latest build and ready to lock the bootloader, which will factory reset the phone as part of the process.
adb reboot bootloader
fastboot flashing lock
If that process makes you feel uncomfortable, I found this post from another thread doing a similar method (but not using the script above)
Good Luck!

robocuff said:
Just so you know, those "archive does not contain" errors are normal. I get them all the time. Always did on the original Pixel too. I'm not sure about the one at the end. Can't say I've ever seen that on either the Pixel 1 or 2.
Click to expand...
Click to collapse
Thanks for the re-assurance. I did notice that the zips literally dont contain a recovery.img. Is that normal for the Pixel 2?

SweetSofie said:
Thanks for the re-assurance. I did notice that the zips literally dont contain a recovery.img. Is that normal for the Pixel 2?
Click to expand...
Click to collapse
Yes. The recovery is in the boot.img now.

Duhman72 said:
Were you able to sort out your issue?
If not, I have heard good things about using this tool to install the latest factory image. Just download this script and follow the instructions in that thread.
If that goes well, then you should be able to boot to the latest build and ready to lock the bootloader, which will factory reset the phone as part of the process.
adb reboot bootloader
fastboot flashing lock
If that process makes you feel uncomfortable, I found this post from another thread doing a similar method (but not using the script above)
Good Luck!
Click to expand...
Click to collapse
I tried this tool and had no luck either. I ultimately just locked the bootloder, as-is, and sent it back. ? Hopefully the think it's just a component level failure since the boot loader is locked. I guess we will see... ?

SweetSofie said:
I tried this tool and had no luck either. I ultimately just locked the bootloder, as-is, and sent it back. ? Hopefully the think it's just a component level failure since the boot loader is locked. I guess we will see... ?
Click to expand...
Click to collapse
They won't even check, they don't care. They will inspect it for physical abuse and water damage. That is all.

TonikJDK said:
They won't even check, they don't care. They will inspect it for physical abuse and water damage. That is all.
Click to expand...
Click to collapse
I think you're right! So far so good. I haven't had any backlash from Verizon so far. Thanks!