Database Info

Nexus 5 Stuck In BootLoop After Replacing Power Button

Nexus 5 rebooting loop with dead Recovery mode ! any help ?
Welcome Dears
Before 1 week ago, my nexus 5 went into rebooting loop, it was a hardware issue, and after I replace the power button
still the phone rebooting on Google logo every second, when I connect it to the charger, its charging without problem until get a full charged battery, so I think it is not a battery issue, and I can enter the fastboot mode without rebooting, so I think its not a hardware issue now, it was and its goes out !
the problem also when I enter the recovery mode , "No Command" with android logo appears, then I press the Volume Up button then I get the recovery mode command, but unfortunately my PC can't see the phone, so I can't use the "adb sideload" command to flash my MIUI ROM (Version: 5.8.6) again
Code:
adb sideload MIUI.zip
error: device not found
but in the fastboot my PC can connect with Nexus, so I try to flash the CWM/TWRP recovery , I got these replay from the command,
Code:
C:\adb>fastboot flash recovery hammerhead-cwm-6.0.4.4-unofficial.img
< waiting for device >
sending 'recovery' (10498 KB)...
OKAY [ 0.453s]
writing 'recovery'...
OKAY [ 0.847s]
finished. total time: 1.302s
C:\adb>
but unfortunately when I repeat my nexus to recovery mode I didn't get the new flashed recovery ! still stuck on the dead old one !
when I use from recovery mode the "wipe data/factory reset" I got these three line then flashing on "no command" dead recovery logo
Code:
--wiping data. . .
Formatting/data. . .
Formatting/cache . . .
then go into "no command" dead recovery logo flashing until I force it shutdown by power button !
same result by "wipe cache partition" command
my Next step to flash the factory image by fastbood command but this solution will remove all files & pictures & Videos & my notes isn't it ?!
so if that is right ? do you have any other solution to run up my nexus and avoiding these rebooting loop or flash new recovery / custom ROM without loosing my data ?! " I am not afraid of loos any Apps and data of them" I need my sound files, videos, pictures and notes.
Pictures below for more clarify the issue !
I get "No Command" when I enter the Recovery mode, until I press the Volume Up
http://store2.up-00.com/2015-08/1440196110631.jpg
The pictures of Dead Recovery Mode commands
http://store2.up-00.com/2015-08/1440196110722.jpg
Thank you.

try this (maybe you just missed the second command - afaik without the bootloader reboot the flashed recovery won't stick):
Code:
fastboot flash recovery /path/to/recovery.img
fastboot reboot-bootloader
and then try to reboot into recovery on your phone
if this doesn't work:
just download stock image, unpack it, open the flash-all.xxx (bat for windows / sh for linux) and remove the "-w" from the last line.
(this will prevent the script from wiping all of your data.)
then just execute the script.
afterwards you can flash the recovery (see above - and don't forget the reboot-bootloader thingy ^^).
and in custom recovery you can install your zips (custom rom and supersu).

Hi b666m
Thank you for your support & teach me new info & steps
I tried your first idea with the two commands, but unfortunately still the recovery stuck on the old one, I tried with three files of recovery image !
I will try your 2th solution but I have to ask you again and double check if I got it correctly to avoid any missing of my important files & Pictures.
as my OS Windows, you mean I have to open "Flash-all.bat" file and delete the "-W" from the flashing command
"fastboot -w update image-hammerhead-ktu84p.zip"
picture bellow for more clear
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is it like that ? and that will not delete my files after I double click the flash-all.bat file ?
Thank you again for your support. :good:

The last command which contained "-w"
Code:
"fastboot update image-hammerhead-ktu84p.zip"
will flash the "image-hammerhead-ktu84p.zip" file ,
which is already has a "userdata.img" file inside it , I think this is will formatting the userdata also and write new data isn't it ?
as that is mentioned in this link:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Code:
fastboot flash userdata C:\image-hammerhead-krt16m\userdata.img
(Note: this command will wipe your device (including \sdcard), EVEN if your bootloader is already unlocked.)
is that right ?

Yes that is right. Not to change tactics here... But one use twrp recovery because support for cwm ended over a year ago. If you after going to flash factory images I would unzip and flash them all individually except for the userdata.img which would wipe your sd.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 10:18 PM ---------- Previous post was at 10:16 PM ----------
Follow method two in the how to flash factory images thread you linked. What was suggested before was to open and edit the flash-all.bat script by removing the -w in the script which would wipe. The flash-all has given people issues in the past and by doing each one individually you can see them succeed individually.
Sent from my Nexus 5 using Tapatalk

The best way to solve your problem . it will 100% work I can assure you . download nexus root tool kit on you PC and once downloaded install and then open the application then .. Put your nexus 5 into bootloader if possible and connect the phone to you PC with the OEM USB cable . in the application on the PC you will see unroot and below that an option (soft brick ) chose that and press unroot follow the step and your phone will be fine . I hope I will get a positive feedback from you . enjoying using your nexus 5
Sent from my A0001 using Tapatalk

Dear @jwhyte : Thank you very much for your support and clarify the issue of flashing the userdata.img , I will go with your idea to flash every file individually except the userdata.img file.
Dear @adarshdeep : thank you very much for you support, the nexus root tool kit App was very great, and the "flsh stuck + unroot" with "soft brick" has an a good choosing with "No Wipe Data", but unfortunately my Nexus still in Bootloop after I applied this good idea,
The nexus tool kit succeed to flash the
bootloader, radio, recovery, system and I leaved the Nexus for 30 minutes after I read these info but still same issue
Code:
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
any advice please ?

The new update of my trials also:
I got a connection between my Nexus and My Work PC by ADB sideload mode,
and I applied this command to flash the ROM:
Code:
adb sideload Rom.zip
and the adb uploaded reach the 100%
and the Nexus 5 start to flashing the ROM, but it didn't complete and this is the output messages on the nexus screen:
Code:
Now send the package you want to apply
to the device with "adb sideload <filename>" ...
Restarting adbd ...
Finding update package ...
Opening update package ...
Verifying update package ...
Installing update ...
symlink: some symlinks failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
what is the symlinks failed and (Status 7 Error) ? there is any solution for this error message ?
Thank you for support to recover my Nexus and files, I have tried for one week now, and I am sure I will get the solution with your support :highfive:

unfortinatily when I tried to flash every file as individual, the adb tools replay with FAILED message (FAILED (remote: flash write failure))
even if I used these three commands before
fastboot erase system
fastboot erase cache
fastboot erase boot
the messages replay by adb
Code:
C:\adb>fastboot flash bootloader bootloader-hammerhead-hhz11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.299s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.499s
C:\adb>fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
sending 'radio' (45409 KB)...
OKAY [ 1.617s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 1.797s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
C:\adb>fastboot flash system system.img
erasing 'system'...
OKAY [ 0.119s]
sending 'system' (721400 KB)...
OKAY [ 23.172s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 23.473s
C:\adb>fastboot flash boot boot.img
sending 'boot' (8700 KB)...
OKAY [ 0.387s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.567s
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (9284 KB)...
OKAY [ 0.417s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.591s
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.213s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
is that means the mobile is hard break ?!

When I tried to Flash Stuck by the "nexus root tool kit" without wiping data, I got failed in this log for:
bootloader + radio + system, and pass for boot + recovery
Code:
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3119 KB)...
OKAY [ 0.305s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.513s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
sending 'radio' (45425 KB)...
OKAY [ 1.611s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.839s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
sending 'boot' (8980 KB)...
OKAY [ 0.487s]
writing 'boot'...
OKAY [ 0.746s]
finished. total time: 1.241s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
sending 'recovery' (9696 KB)...
OKAY [ 0.506s]
writing 'recovery'...
OKAY [ 0.795s]
finished. total time: 1.307s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
erasing 'system'...
OKAY [ 0.115s]
sending 'system' (1021840 KB)...
OKAY [ 32.279s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 32.587s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.006s
Post-Flash Factory Reset...
downloading 'boot.img'...
OKAY [ 0.420s]
booting...
OKAY [ 0.107s]
finished. total time: 0.537s
You should now see an android on its back with an exclamation point.
This is the 'Pre-screen' to stock android recovery. It requires a button
combination to bring up the menu:
1. While holding down Power, press Volume Up
2. Using the volume buttons highlight 'wipe cache partition'
3. Use the power button to select it.'
4. Wait while it formats 'cache'....
4. Select 'reboot system now'
Press any key to cotinue...
any help to understand why the flashing of bootloader + radio + system were failed ?!

@M_Nexus5. Out of curiosity what happens if you try locking your bootloader in fastboot and rebooting? Does the bootloader stay locked?
fastboot oem lock
fastboot oem device-info
Sent from my Nexus 9 using XDA Free mobile app

Dear @jd1639 : thank you very much for your support, I will try your idea and submit the result here, but if the bootloader be lucked and can't be unlock again we will loos this feature of unlocked bootloader isn't it ?
Now I have a good news I got & copy all my files, :highfive:
I play with some features of Nexus root kit tool and try to flash stock Rom and there were a failed as I mentioned that in my last posts,
I flashed each failed X.img, individually under "Fastboot Flash" menus in "Advanced Utilities" Section,
Then I press Custom recovery Under "Fastboot Boot" in "Advanced Utilities" Section, I think this option is the key because it forced the Nexus to run into TWRP recovey mode :good: "but without flash it, because when I reboot by device to recovery mode again I got the dead old one !!
and this recovery "TWRP" support the "Enable MTP" protocol, so after that I got a connection for my nexus as a storage with my PC and copy All files & Pictures,
I Can copy from the device, but I con't copy from my PC to it.
but there are some Error message in the log of TWRP recovery mode:
Code:
Updating partion details
[COLOR="Red"]E: Unable to mount '/Persist'[/COLOR]
...done
Full SELinux support is present.
[COLOR="Red"]E: Unable to open '/cach/recovery/.version'.[/COLOR]
MTP Enable
also when I tried to flash the slim Rom by install option I got some error message , the TWRP can't flash the Rom here are the messages:
Code:
when I tried to flash a ROM.zip file I got some error messages like this:
Format and Mount System, Mount Data ...
Symlinks and Permissions ...
symlink: some symlinks faild
[COLOR="Red"]E: Error executing updater binary in zip '/sdcard/Zip File sh Update File/Slim-4.4.4.zip[/COLOR]
Error flashing zip 'sdcard/Zip flash Update File/Slim-4.4.4.zip'
Updating partition details...
[COLOR="Red"]E: Unable to mount '/persist'[/COLOR]
...done
also I tried to flash the same my Nexus ROM, (MIUI 4-4-4), but I got same result & Error messages, all Rom already on my sdcard before 4 months maybe.
When I tried "Cache & Dalvik Wipe Complate", I got same error.
Code:
Wiping Dalvik Cach Directories...
Cleaned: /data/dalvik-cach...
-- Dalvik Cach Directories Wipe Complete!
Updating partition details...
[COLOR="Red"]E: Unable to mount '/persist'[/COLOR]
Now may if I flash the stock factory image with wiping all data "its default" solve the problem ?!
or the error message above shown something wrong with device ? or need a certain tool to fix it ?!
or I can fix this issue by "Mount" option in the TWRP Recovery ?! I never used this option !
I will try to flash the stock factory image when I come back to the home.
The big important thing was my files and I got them now by your support, Thaaaanks :fingers-crossed:
the next step, am I get my device back or need to buy new one ?! :cyclops:
Thank you again for your support and I hope the log error messages will give more help to explain the real issue for you.

Well it sounds like you got what you wanted... However from what I've been able to find the errors you are running up against is not good. It sounds like the failed to flash errors and if you boot into twrp which you did and you get mount problems there is a very good chance your sd is fried.
The reason @jd1639 asked about the OEM lock I believe is if it won't stay locked or unlocked it is sd issue.
You can try contacting Google about an RMA however by you replacing there power button they most likely won't accept it.
Good luck glad you got your files.
Sent from my Nexus 5 using Tapatalk

@jd1639 this is the result of the commands, the bootloader is locked now, but return back when I restart the device !
Code:
C:\adbToolsss>fastboot oem lock
...
OKAY [ 0.037s]
finished. total time: 0.037s
C:\adbToolsss>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) off-mode-charge: true
OKAY [ 0.004s]
finished. total time: 0.004s
C:\adbToolsss>
after restarting the device:
Code:
C:\adbToolsss>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) off-mode-charge: true
OKAY [ 0.004s]
finished. total time: 0.005s
C:\adbToolsss>
Dear @ jwhyte , yes it was a good luck when I got a copy of my files, but do you mean that is the error message of "Unable to mount" is the sdcard/storage of devices damaged and can't be fix ?!
about the RMA, my devices already out of warranty, I bought it more than one year ago.
so now go ahead to choose & buy a new device ?

Update:
 @D1639
may I got it here in the link of your post
http://forum.xda-developers.com/showpost.php?p=50142493&postcount=14
now the emmc of device is damaged , and I have to buy new device no other solution for this damage whatever software/hardware ?

M_Nexus5 said:
Update:
@D1639
may I got it here in the link of your post
http://forum.xda-developers.com/showpost.php?p=50142493&postcount=14
now the emmc of device is damaged , and I have to buy new device no other solution for this damage whatever software/hardware ?
Click to expand...
Click to collapse
If you can't lock/unlock your bootloader there probably isn't anything you can do. But I'd give this a try, http://forum.xda-developers.com/showthread.php?p=59154061
Sent from my Nexus 5 using XDA Free mobile app

Have a look at this thread: http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Sent from my Nexus 5 using Tapatalk

@jd1639 after I tried that idea still the device into Bootloop, and I checked the EMMC by "BoardDiag" tool, and I got failed , so may as you said nothing can I do with that issue, but I didn't given up yet, I already bought new OnePlus Two,because no more time for new trials, may I have to try new ideas again next week or after that, Thank you very much my dear, you are very helpful.
@efrant thank you for this link, this is a good idea too, I tried it but faced an issue with using & installing Universal Naked driver, some times the Adb tools can't connect with device in recovery mode, I will try it again and again next week when I have a time and using new PC to install the Universal Naked Driver for recovery only to avoid any other drivers for android.
All dears helpers , thank you very much for your helping,
when I have more time next week I will try some of new idea,
if I get any solution I will submit here the link to be a reference for other
who may face same issue,
Thank you again.

M_Nexus5 said:
[snip]
@efrant thank you for this link, this is a good idea too, I tried it but faced an issue with using & installing Universal Naked driver, some times the Adb tools can't connect with device in recovery mode, I will try it again and again next week when I have a time and using new PC to install the Universal Naked Driver for recovery only to avoid any other drivers for android.
Click to expand...
Click to collapse
It seems you are trying to solve too many issues at once.
The first thing you need to do is make sure your drivers are installed properly, which doesn't seem to be the case. You shouldn't have to mess around with any unofficial drivers. Just install the drivers from Google's website: whttp://developer.android.com/tools/extras/oem-usb.html. That is the first thing you need to make sure is done properly.
The next is to make sure you have the latest version of the four files you need (fasboot.exe, adb.exe, & the 2 dll files) to connect with your device.
Only then should you try to troubleshoot / fix your device.
Sent from my Nexus 5 using Tapatalk

You definitely need to fix your persist partition. Your phone will not boot until you do that.
For this to work you need adb to connect to the phone in normal mode (not bootloader).
Installing the naked driver can be problematic, if another driver is already installed. The easiest way is to install it another PC that has not had an Android phone connected to it. You need to disable internet when you connect the phone, and try to cance windows installation of the driver. Then you will have a device with an error in device manager, you right click on it and choose update driver, and choose manual install from the naked driver folder.
If you can't do that, see if you can use the custom recovery to change the phone to connect usb as a camera.
Now open device manager: if you see Android device >Android Composite ADB Interface then adb should work. Try adb devices command. If you see a device you are connected. Then follow bitdomo's guide to fixing the persist partition. You need to be rooted for this to work. You can skip the wifi and BT foe now - you don't need that to boot into the OS. You can do this later.
Once you fix the persist partiton you should be able to boot. Perhaps it will be a good idea to flash stock, but make sure to enable usb debugging, in case you have future problems.
You can see my guide here http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632

Bricked? I'm out of options

Hello, on March 10th I received a new update on my N5. After update, which finished with no problems as usual, my phone was normally working or about two more hours. In that time no new apps were installed. Then it just shut down, and can't be properly turned on.
It always stuck at Google logo and that is all that it does. I'm able to get to the fastboot mode by holding Power+Volume Up+Volume Down buttons, but I can't get into Recovery Mode option to hard reset it. Nothing show up after selecting that option and Power+Volume Up does nothing. Ok, bad luck, time to flash it nice and clean.
Haha, nice try.
I'm not sure if I had USB debugging on or off, but I think off. Obtained ROM from Google + newest platform tools from SDK and followed all possible manual I could get from Internets, results:
Code:
adb devices
List of devices attached
*nothing*
Code:
adb reboot bootloader
error: no devices found
Drivers are newest from Google, reinstalled several times, device is visible in Windows as Android Bootloader Interface and seem working fine. adb just do not see phone.
Code:
fastboot oem unlock
...
OKAY [ 46.402s]
finished. total time: 46.403s - WORKS!
But rest is just no go:
Code:
fastboot erase boot
erasing 'boot'...
FAILED (remote: failed to erase partition)
finished. total time: 0.219s
Code:
fastboot erase cache
********Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.217s
Code:
fastboot erase recovery
erasing 'recovery'...
FAILED (remote: failed to erase partition)
finished. total time: 0.219s
Code:
fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.218s
I tried several more commands, like to install twrp, but all with same results.
Code:
fastboot flash recovery twrp.img
sending 'recovery' (14314 KB)...
OKAY [ 0.653s] writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.835s
I also tried "fastboot boot twrp.img" and it worked but didn't helped much. Internal storage is showing size 0 MB an when I try to do anything it ends with wall of red text about how it's unable to find partitions or mount images, first line:
Code:
E:Primary block device '/dev/block/platform/msm_sdcc.1/by-name/userdata' for mount point '/data' is not present!
Also when I reboot bootloader, it get stuck and when I get it back with buttons, it is back in its locked state. So my guess is that eMMC went to Silicon Heaven.
Do you guys have any advices? Or is my phone just fancy mirror now?

When the phone is in fastboot mode, does the bootloader state remain "unlocked" after a reboot?
If the bootloader is unlocked, have you tried relfashing a stock ROM?

audit13 said:
When the phone is in fastboot mode, does the bootloader state remain "unlocked" after a reboot?
If the bootloader is unlocked, have you tried relfashing a stock ROM?
Click to expand...
Click to collapse
Like i wrote, it get back to locked state.

The emmc chip is defective and cannot be fixed. This is clearly indicated when the bootloader relocks itself at reboot.

Thought so, but wanted confirmation . Thank you.

fastboot: FAILED (remote: image verification error) after DC Phoenix unbrick

Hello
after i succesfully used DC Phoenix to recover Huawei Mate 8 (NXT-L29C432) i cannot flash TWRP or anything on my phone , as im still getting the "FAILED (remote: image verification error)" from fastboot. So i also cannot root and use the device as before
Im sure im not alone with this issue, but i cannot find any clear solution for this. Can you please help or advice me further??
I spent 15€, recovered the phone, but with this, its still partial success.
I basicaly followed https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
Here some outputs:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.0-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22140 KB)...
OKAY [ 0.530s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.562s
Before the use of DC Phoenix, i always get this number.
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
QHC0216327001941 fastboot
Now:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
0123456789ABCDEF fastboot
In Fastboot mode, on phone screen i see:
PHONE Unlocked
FRP Lock
DC - Unlocker 2 Client 1.00.1308 reports:
FB LockState: UNLOCKED
USER LockState: LOCKED
unlocked
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-lockstate
...
(bootloader) locked
OKAY [ -0.000s]
finished. total time: -0.000s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
In Developer menu i have the
"Allow OEM unlock" grayed & disabled, im unable to swich it on..
Can you please explain what happend and how to fix this?
Thank you for further help.

Solved with mighty HCU client, i was able to import the just the SN back without problems. Then as usual.. unlock the bootloader, TWRP, SU... and now the phone is back in shape

I hope I can recover my Mate 9 Pro.
Maybe 15€ is have to spend but FunkyHuawei is more expensive.

Hi. I have same problem., I unlocked Huawei WAS-AL00 bootloader via Miracle Huawei Tool, it unlocked successfully. But, I can't flash TWRP, it says-FAILED (remote: image verification error)
Whent type fastboot oem lock-state info in CMD, it shows:
FB LockState: UNLOCKED
USER LockState: LOCKED
There is not FRP or OEM lock option in settings, becuse this is China version model and doesn't support Google Play.
What is USER LOCK STATE? Please help me. Thanks.

Remote:image verification error.
When i try to flash Mate 8 nxt l29 twrp recovery its says remote:image verification error..the phone fastboot is unlocked .i tried many twrp images but still the same problem

[need help]Try to root pixel 2 but can't unlock the oem lock

I bought pixel 2 a month ago.
It version is
8.0.0 (OPD3.170816.012, Sep 2017, Verizon)
And updated 8.0 to 8.1
8.1.0 (OPM1.171019.019, Feb 2018)
Bootloader: mw8998-002.0067.00
Product Revision: walleye MP1
boot-slot: a
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
adb version
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
fastboot version
fastboot version eac51f2bb6a8-android
-------------------
I turn on the develop mode ,debug mode
OEM lock grayed
TRY to fastboot unlock
C:\Users\User\Downloads\pixel 2root\fastboot>adb devices
List of devices attached
HT7B41A03550 device
C:\Users\User\Downloads\pixel 2root\fastboot>adb reboot bootloader
C:\Users\User\Downloads\pixel 2root\fastboot>fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.008s
C:\Users\User\Downloads\pixel 2root\fastboot>fastboot oem unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.009s
C:\Users\User\Downloads\pixel 2root\fastboot>fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [ 0.006s]
finished. total time: 0.015s
C:\Users\User\Downloads\pixel 2root\fastboot>fastboot flashing lock_critical
...
FAILED (remote: unknown command)
finished. total time: 0.004s
TRY the recovery mode ,to rollback the 8.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
imgur.com/a/2RCVp
i.imgur.com/PhsS42u.jpg
Also TRY this page the apk diidn't work
https://forum.xda-developers.com/pixel-2-xl/how-to/exp-verizon-pixel-pixel-2-xl-potential-t3750795
Somebody know how to root it ,am i miss something ?
please help me ,i am no idea what wrong is it...

am i post in the wrong page ,how to delete post (sorry i am new here
am i post in the wrong page ,how to delete post (sorry i am new here

zavke said:
I bought pixel 2 a month ago.
It version is
8.0.0 (OPD3.170816.012, Sep 2017, Verizon)
And updated 8.0 to 8.1
8.1.0 (OPM1.171019.019, Feb 2018)
Bootloader: mw8998-002.0067.00
Product Revision: walleye MP1
boot-slot: a
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
adb version
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
fastboot version
fastboot version eac51f2bb6a8-android
-------------------
I turn on the develop mode ,debug mode
OEM lock grayed
TRY to fastboot unlock
C:\Users\User\Downloads\pixel 2root\fastboot>adb devices
List of devices attached
HT7B41A03550 device
C:\Users\User\Downloads\pixel 2root\fastboot>adb reboot bootloader
C:\Users\User\Downloads\pixel 2root\fastboot>fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.008s
C:\Users\User\Downloads\pixel 2root\fastboot>fastboot oem unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.009s
C:\Users\User\Downloads\pixel 2root\fastboot>fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [ 0.006s]
finished. total time: 0.015s
C:\Users\User\Downloads\pixel 2root\fastboot>fastboot flashing lock_critical
...
FAILED (remote: unknown command)
finished. total time: 0.004s
TRY the recovery mode ,to rollback the 8.0
imgur.com/a/2RCVp
i.imgur.com/PhsS42u.jpg
Also TRY this page the apk diidn't work
https://forum.xda-developers.com/pixel-2-xl/how-to/exp-verizon-pixel-pixel-2-xl-potential-t3750795
Somebody know how to root it ,am i miss something ?
please help me ,i am no idea what wrong is it...
Click to expand...
Click to collapse
Did you purchase your phone from Google or Verizon? If you purchased it on Verizon, you can no longer unlock the bootloader using the lock_critical command anymore as it has been fixed in this version. Also I do not believe it is possible to roll back to 8.0 but I could be wrong. I haven't had a reason to try.
zavke said:
am i post in the wrong page ,how to delete post (sorry i am new here
Click to expand...
Click to collapse
Should've posted in the questions section.

Try a factory reset. Skip the setup wizard; the OEM Unlock toggle should be available. It was greyed out on mine until I wiped /data.

socal87 said:
Try a factory reset. Skip the setup wizard; the OEM Unlock toggle should be available. It was greyed out on mine until I wiped /data.
Click to expand...
Click to collapse
Can anyone confirm this
Did you have SIM card in? WiFi on? any specifics?

Jmaniac55 said:
Can anyone confirm this
Did you have SIM card in? WiFi on? any specifics?
Click to expand...
Click to collapse
It's been confirmed. Yes, SIM was in, and WiFi was on. I factory reset, and skipped the setup wizard (didn't connect to wifi). Immediately went to Settings > System > About Phone and enabled developer mode, and OEM unlocking was available. It was greyed out before I reset, when I had user data on the device.

socal87 said:
It's been confirmed. Yes, SIM was in, and WiFi was on. I factory reset, and skipped the setup wizard (didn't connect to wifi). Immediately went to Settings > System > About Phone and enabled developer mode, and OEM unlocking was available. It was greyed out before I reset, when I had user data on the device.
Click to expand...
Click to collapse
Nope it sure does not work, tried it and it's still greyed out

MHA-L29: "Func NO : 11 (recovery image)"

Hello,
I need some help, my MHA-L29C636 doesn't boot to system, go into TWRP recovery or into eRecovery anymore, I have access to fastboot tho.
What happened:
I was on stock clean slate Oreo (MHA-L29 8.0.0.375(C636))
Unlocked bootloader and FRP
Tried to restore TWRP backup I've made earlier when I was on Nougat because I wanted my settings/data back.
Restoration was complete but I could not boot to system, so I used files from https://forum.xda-developers.com/showpost.php?p=75725964&postcount=5 to go back to Oreo (MHA-L29 8.0.0.375(C636)), so I flashed the hwota7_update.zip phone rebooted and since then I can not got into either system, TWRP recovery or eRecovery anymore.
I get this error screen:
"ERROR MODE"
Attention!
Please Update system again.
[Green Android]
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried to flash with Fastboot TWRP recovery from https://forum.xda-developers.com/mate-9/development/recovery-twrp-huawei-mate-9-hi3660-t3834796 or https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-oreo-t3734967
But I still get the error screen on boot (normal boot and boot holding Power + Vol Up)
I have unlocked bootloader/FRP and access to fastboot how can I get a working phone back?

_A.T.Omix_ said:
Hello,
I need some help, my MHA-L29C636 doesn't boot to system, go into TWRP recovery or into eRecovery anymore, I have access to fastboot tho.
What happened:
I was on stock clean slate Oreo (MHA-L29 8.0.0.375(C636))
Unlocked bootloader and FRP
Tried to restore TWRP backup I've made earlier when I was on Nougat because I wanted my settings/data back.
Restoration was complete but I could not boot to system, so I used files from https://forum.xda-developers.com/showpost.php?p=75725964&postcount=5 to go back to Oreo (MHA-L29 8.0.0.375(C636)), so I flashed the hwota7_update.zip phone rebooted and since then I can not got into either system, TWRP recovery or eRecovery anymore.
I get this error screen:
"ERROR MODE"
Attention!
Please Update system again.
[Green Android]
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Tried to flash with Fastboot TWRP recovery from https://forum.xda-developers.com/mate-9/development/recovery-twrp-huawei-mate-9-hi3660-t3834796 or https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-oreo-t3734967
But I still get the error screen on boot (normal boot and boot holding Power + Vol Up)
I have unlocked bootloader/FRP and access to fastboot how can I get a working phone back?
Click to expand...
Click to collapse
Ah, you use my Nougat only hwota zip... You can try extracting and flashing: ramdisk, kernel, recovery_ramdisk, recovery_vbmeta, recovery_vendor from Update.app of MHA-L29C636B375.
But we'll see if that works.
That zip you flashed dd's /dev/block devices directly. On Nougat you have recovery and erecovery on sdd30 and sdd33.
On Oreo that's erecovery_vendor and teeos...
Also, restoring /data from Nougat on Oreo will most likely not work (as you saw). When you can get back into TWRP, flash stock recovery and Factory reset from there.

ante0 said:
Ah, you use my Nougat only hwota zip... You can try extracting and flashing: ramdisk, kernel, recovery_ramdisk, recovery_vbmeta, recovery_vendor from Update.app of MHA-L29C636B375.
But we'll see if that works.
That zip you flashed dd's /dev/block devices directly. On Nougat you have recovery and erecovery on sdd30 and sdd33.
On Oreo that's erecovery_vendor and teeos...
Also, restoring /data from Nougat on Oreo will most likely not work (as you saw). When you can get back into TWRP, flash stock recovery and Factory reset from there.
Click to expand...
Click to collapse
Hello, thanks for the reply, so I need to
Code:
fastboot flash ramdisk RAMDISK.img
fastboot flash kernel KERNEL.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
fastboot flash recovery_vendor RECOVERY_VENDOR.img
Correct? How can I know the exact name each img should go to?

_A.T.Omix_ said:
Hello, thanks for the reply, so I need to
Code:
fastboot flash ramdisk RAMDISK.img
fastboot flash kernel KERNEL.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
fastboot flash recovery_vendor RECOVERY_VENDOR.img
Correct? How can I know the exact name each img should go to?
Click to expand...
Click to collapse
They are named the same as the partitions, so your code is correct.

Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash ramdisk RAMDISK.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.401s]
writing 'ramdisk'...
OKAY [ 0.169s]
finished. total time: 0.570s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.602s]
writing 'kernel'...
OKAY [ 0.386s]
finished. total time: 0.988s
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 0.802s]
writing 'recovery_ramdisk'...
OKAY [ 0.339s]
finished. total time: 1.141s
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
target reported max download size of 471859200 bytes
sending 'recovery_vbmeta' (6 KB)...
OKAY [ 0.000s]
writing 'recovery_vbmeta'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_vendor RECOVERY_VENDOR.img
target reported max download size of 471859200 bytes
sending 'recovery_vendor' (16384 KB)...
OKAY [ 0.400s]
writing 'recovery_vendor'...
OKAY [ 0.179s]
finished. total time: 0.594s
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Same error as before.

i have the same problem bit i went on and flashed something wrong and i cant even acceces fastboot or anything. Dont do anything just go to a nearby servis center and let them flash the system. There is no way of recocering your phone now. And dont try to relock the bootloader or your phone will be gone for good.

ante0 helped me get back to stock Oreo, so it's possible if you have bootloader unlocked

I stuck with my Mate 9 Error mode numbers 11 and 2
ante0 said:
Ah, you use my Nougat only hwota zip... You can try extracting and flashing: ramdisk, kernel, recovery_ramdisk, recovery_vbmeta, recovery_vendor from Update.app of MHA-L29C636B375.
But we'll see if that works.
That zip you flashed dd's /dev/block devices directly. On Nougat you have recovery and erecovery on sdd30 and sdd33.
On Oreo that's erecovery_vendor and teeos...
Also, restoring /data from Nougat on Oreo will most likely not work (as you saw). When you can get back into TWRP, flash stock recovery and Factory reset from there.
Click to expand...
Click to collapse
Try the method with DC Phoenix in my case works with the same problem.

Still no solution to this?

DC PHOENIX fix this error mode .. ?

I kinda have the same issue as OP.
I bricked my phone. Neither TWRP Recovery nor ERecovery is working currently. The only thing that works for now is fastboot and it shows me that my bootloader aswell as FRP is unlocked.
I tried flashing ramdisk, kernel, recovery_ramdisk, recovery_vbmeta, recovery_vendor from Update.app.
It's a Mate 9 Dual Sim Europe so it should be MHA-L29C432. I was on an unlocked and rooted nougat before and tried to update today to Oreo via TWRP. Somewhen during installation it restarted and now I am in this state and can't enter any recovery anymore.
Anybody know how to get it to work again?

_A.T.Omix_ said:
ante0 helped me get back to stock Oreo, so it's possible if you have bootloader unlocked
Click to expand...
Click to collapse
Hi
could you (PLEASE ) elaborate further what you or ante0 did to make it work again?
I am in the same situation.
What I don't understand is do I have to fastboot flash the oreo rom files or the nougat ones? And what should happen then? Will it automatically install HWOTA folder from sd card? Or when should I try to install twrp again?
Would be great to get my phone working again.

Mha-l29 (c185)
I was able to revive the mentioned model using fastboot and service ROM mentioned somewhere in XDA forum.
First of all you have to unlock the bootloader and I did buy unlock code from DC Unlocker costed me almost 5 bucks
before you unlock the bootloader you have to enable "OEM Unlocking" option in-order to proceed, then unlock the bootloader.
there are "recovery" and "recovery2" partitions names you have to flash them with correct files.
Then you have the option to flash the whole firmware using Fastboot or Huawei eRecovery

I got my mate 9 on the same situation can you please tell me what you did to go back to normal?
I can't enter erecovery or twrp
I got the same errors 11 and 2