Database Info

unlock state relocks after reboot

Hi all,
I have a friend's nexus 5, that I try to unbrick. Unfortunally, and after dragging all threads about unlocking via fastboot, I'm still unable to fix his device.
The fact is, I'm able to unlock (fastboot oem unlock) , then when I reboot the bootloader, it's back locked.
I've tried to flash stock bootloader (for both nexus 5 bootloaders (HHZ11k, HHZ10x) but without success
The device is locked on a bootloop Google screen, impossible to access to recovery mode (via fastboot or via vol up + power)
Anybody's got an idea ?

here is a sequence of trying to update bootloader, you can see that I must unlock for allmost each step
Code:
./fastboot oem unlock
...
OKAY [ 2.596s]
finished. total time: 2.596s
./fastboot erase boot
erasing 'boot'...
OKAY [ 0.217s]
finished. total time: 0.217s
./fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.215s]
finished. total time: 0.215s
./fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.219s]
finished. total time: 0.219s
./fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.221s]
finished. total time: 0.221s
./fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.493s]
finished. total time: 0.493s
./fastboot flash bootloader bootloader-hammerhead-hhz11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
OKAY [ 0.404s]
finished. total time: 0.691s
./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
./fastboot oem unlock
...
OKAY [ 2.130s]
finished. total time: 2.130s
./fastboot oem unlock
...
OKAY [ 3.665s]
finished. total time: 3.665s
./fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
sending 'radio' (42049 KB)...
OKAY [ 1.514s]
writing 'radio'...
OKAY [ 2.850s]
finished. total time: 4.364s
./fastboot oem unlock
...
OKAY [ 2.999s]
finished. total time: 2.999s
./fastboot -w update image-hammerhead-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ10x
Baseband Version.....: M8974A-1.0.25.0.23
Serial Number........: 02ffc80f08e51d0d
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
FAILED
Device version-bootloader is 'HHZ10x'.
Update requires 'HHZ11k'.
finished. total time: 0.601s

You need to flash the right bootloader first before the rest can go through

yep, the fact is I can't find anywhere a bootloader to flash for my version (HHZ10x).
The only files I found are those from Google.
I've tried both for same result.
I've find updates from this thread but I can't boot in recovery mode (from fastboot mode or with fastboot boot recovery.img).
Maybe there is a way to flash those files (from above thread) but I've tried with files (like bootloader.aboot.img, bootloader.imgdata.img, bootloader.rpm.img, etc, ...) without success (FAILED (remote: invalid bootloader image))

benoit.bds said:
yep, the fact is I can't find anywhere a bootloader to flash for my version (HHZ10x).
The only files I found are those from Google.
I've tried both for same result.
I've find updates from this thread but I can't boot in recovery mode (from fastboot mode or with
Code:
fastboot boot recovery.img
).
Maybe there is a way to flash those files (from above thread) but I've tried with files (like bootloader.aboot.img, bootloader.imgdata.img, bootloader.rpm.img, etc, ...) without success (
Code:
FAILED (remote: invalid bootloader image)
)
Click to expand...
Click to collapse
Looks like you have corrupted memory and nothing is going to work. Time to rma.

jd1639 said:
Looks like you have corrupted memory and nothing is going to work. Time to rma.
Click to expand...
Click to collapse
i agree.

I don't want to come off as alarmist, but I'm starting to see a worrying trend here. If you look at other threads over the past few days, there have been quite a few people with dying flash chips (myself included). There are a few differences in some of the symptoms, but the most common being that 'fastboot oem unlock / lock' fails to stick. It's like the chip is left in some random state of corruption, and unable to be written to. If I were I betting man, I'd say we can expect to see a flood of these posts in coming days.
I would recommend to anyone with an unlocked bootloader, that you get it locked asap and reset the tamper flag too, just in case this same issue occurs with your phone in future, and you need to RMA it.
To the OP, can you confirm whether the device has been previously unlocked, and whether anything was done to the device leading up to the issue? I'm hoping that if this issue is happening to both locked and unlocked devices that Google / LG will have to take the issue seriously should it become an epidemic.

:crying:
My friend has admitted that his n5 had fallen into water...
He gave it for deoxidation + battery replace, but they didn't manage to boot it more than fastboot mode, so I proposed him to give it a try.
To reply to sir_earl, the device was early bought, stock rom and official OTAs.
Anyway, thank you all for your responses !
Regards

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.

MI4c unlocking hell!

Applied for unlocking at http://en.miui.com/unlock/ and got this:
Apply for unlocking permissions
Sorry, your application has been rejected.
The more active your Mi Account is, the more likely your application will get approved.
Reapply​>>
So no way to get unlock code!
Then tried: https://forum.xda-developers.com/mi-4c/general/guide-unlocking-mi4c-bl-verification-t3336779
And it seemed to work, could flash TWRP and CM 13.1
Had problems with radio, tried flashing radio, now I'm stuck in fastboot, can't boot to recovery or anything else, loops back to fastboot.
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.062s]
finished. total time: 0.063s​
Any attempt to flash I get: "Partition flashing is not allowed"
Any ideas or should I just enter the "How far can you toss your Xiaomi MI4c contest"?

Your bootloader is re-locked. Follow the unlock procedure again, maybe you flashed the new bootloader.
BTW you don't have to flash the whole rom to change the bootloader, you can just extract it from firmware in zip and run:
fastboot flash aboot emmc_appsboot.mbn

Ydraulikos said:
Your bootloader is re-locked. Follow the unlock procedure again, maybe you flashed the new bootloader.
BTW you don't have to flash the whole rom to change the bootloader, you can just extract it from firmware in zip and run:
fastboot flash aboot emmc_appsboot.mbn
Click to expand...
Click to collapse
Thank you friend Ydraulikos, I have tried flashing boot and recovery before, but I have not tried your version.
Unfortunately this was the result:
C:\adb\images>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (469 KB)...
OKAY [ 0.036s]
writing 'aboot'...
FAILED (remote: Critical partition flashing is not allowed)
finished. total time: 0.083s​

SOLVED!
Things looked pretty hopeless, two days without a phone, but managed to return to MIUI 7.1.6.7 and can proceed from here. I'm not saying this is the righ method, it worked for me and perhaps can help others in a similar situation. Have read a lot of posts in the last two days so please forgive me if I can not give credit to all the people whose advice helped, so thank you xda!
Installed QDLoader HS-USB Driver_64bit_Setup recommended in one of the posts and rechecked my drivers in general.
One command that seemed to be promising was "fastboot oem edl"
However, when my phone went to edl mode it was no longer accessible for fastboot <waiting for device>
On advice of another post I downloaded MiFlash2015.10.28.0 and libra_images_6.1.7_20151221.0000.11_5.1.*.tar.gz
From the command line typed "fastboot oem edl" and with MiFlash flashed MIUI 6.1.7, had to choose the "Flash all except data and storage" option as other options gave me a memory error message. Flashing went okay!
So my phone is back in business now!

OnePlus One bricked - Bootlooder locked unable to unlock - system partition lost

Please help!!
I have messed up my oneplus one bacon
I was using lineageos 16 and all was fine. For some dumb reason like getting 'Screen mirroring' feature, I decided to go back to lineageos 15.1. Somewhere in the instructions I [mis]read, a clean wipe is recommended to go back to previous release.
I wiped all my partitions from twrp. That's why, my system partition is gone.
I tried a bunch of things after searching on these forums for similar symptoms, but no luck as of yet.
I tried to flash the stock recovery and stock ROM
Recovery flash was successful and so I am on CWM, but the ROM failed as the system partition could not be mounted/unmounted
Now, my phone's state -- I have Cyanogen recovery
ADB devices does not work.
> adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Fastboot works, but am unable to unlock my bootloader, not sure how it got locked.
>fastboot oem unlock
OKAY [ 0.009s]
Finished. Total time: 0.019s
It simple reboots to the recovery without unlocking
>fastboot oem device-info
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.021s]
Finished. Total time: 0.028s
I tried sideload to upload files like stock ROM, I get verification errors.
I was hoping this thread would help me. But not sure how to apply this fix
I am unable to flash or boot as I get the following error
> fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (9968 KB)...
OKAY [ 0.317s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.318s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.339s
Please help!!!

Mate 20 X EVR-L29 Flashing Cust and Preload partitions using fastboot

My phone is Mate 20 X EVR-L29 C636. Like many of us, I received an OTA EMUI10 update 10.0.0.180. It resulted in Soft brick. I have access to erecovery and fastboot.
Thanks to efforts of lot of people on this forum, many people successfully unbricked their phone using dload method with recently released 10.0.0.180 build. I have family pictures on phone, which I do not want to lose using dload method.
I checked my build number using fastboot and it says EVR-L29 9.1.0.347(C636E3R1P11). Thanks to @thunderbolt128. He thinks that my phone's CUST and vendor partitions are still 9.1. May be the other partitions upgraded to EMUI 10. My question is it possible to flash CUST and vendor partitions using any method (may be fastboot flash?) without erasing user data? I can perhaps using "EMUI extractor" to extract images and try flashing them. My problem is that I always had Samsung Notes and I do not know the partition layout of Huawei Mate 20 x. Any help and suggestions are welcome.
PS C:\platform-tools> .\fastboot.exe oem get-build-number
(bootloader) :EVR-L29 9.1.0.347(C636E3R1P11)
OKAY [ 0.016s]
Finished. Total time: 0.033s
PS C:\platform-tools> .\fastboot.exe getvar vendorcountry
vendorcountry: hw/spcseas
Finished. Total time: 0.020s
PS C:\platform-tools> .\fastboot.exe oem get-bootinfo
(bootloader) locked
OKAY [ 0.004s]
Finished. Total time: 0.018s
PS C:\platform-tools> .\fastboot.exe getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: 'FAIL:need all image flashed!')
Finished. Total time: 0.033s
PS C:\platform-tools>

hsarao said:
My phone is Mate 20 X EVR-L29 C636. Like many of us, I received an OTA EMUI10 update 10.0.0.180. It resulted in Soft brick. I have access to erecovery and fastboot.
Thanks to efforts of lot of people on this forum, many people successfully unbricked their phone using dload method with recently released 10.0.0.180 build. I have family pictures on phone, which I do not want to lose using dload method.
I checked my build number using fastboot and it says EVR-L29 9.1.0.347(C636E3R1P11). Thanks to @thunderbolt128. He thinks that my phone's CUST and vendor partitions are still 9.1. May be the other partitions upgraded to EMUI 10. My question is it possible to flash CUST and vendor partitions using any method (may be fastboot flash?) without erasing user data? I can perhaps using "EMUI extractor" to extract images and try flashing them. My problem is that I always had Samsung Notes and I do not know the partition layout of Huawei Mate 20 x. Any help and suggestions are welcome.
PS C:\platform-tools> .\fastboot.exe oem get-build-number
(bootloader) :EVR-L29 9.1.0.347(C636E3R1P11)
OKAY [ 0.016s]
Finished. Total time: 0.033s
PS C:\platform-tools> .\fastboot.exe getvar vendorcountry
vendorcountry: hw/spcseas
Finished. Total time: 0.020s
PS C:\platform-tools> .\fastboot.exe oem get-bootinfo
(bootloader) locked
OKAY [ 0.004s]
Finished. Total time: 0.018s
PS C:\platform-tools> .\fastboot.exe getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: 'FAIL:need all image flashed!')
Finished. Total time: 0.033s
PS C:\platform-tools>
Click to expand...
Click to collapse
wait, if you have fastboot and adb access, why dont u just use the command line in order to manually copy over all the data from your phone to your pc/laptop?
Sent from my Huawei Mate 20 X EVR-AL00 using Tapatalk

I only have erecovery and fastboot access. The emergency backup option in erecovery does not work neither does the safe mode boot.
Is there a way to copy data using fastboot ?

hsarao said:
I only have erecovery and fastboot access. The emergency backup option in erecovery does not work neither does the safe mode boot.
Is there a way to copy data using fastboot ?
Click to expand...
Click to collapse
hmmmm ok, it seems like fastboot is write to device only, unfortunately. can u check if you have ADB access when ure in erecovery?
Sent from my Huawei Mate 20 X EVR-AL00 using Tapatalk

jbmc83 said:
hmmmm ok, it seems like fastboot is write to device only, unfortunately. can u check if you have ADB access when ure in erecovery?
Sent from my Huawei Mate 20 X EVR-AL00 using Tapatalk
Click to expand...
Click to collapse
No, ereceovery does not provide access to ADB. Has anyone checked if the EMUI 10 is available using erecovery? Some one was saying, EMUI 10 will only be available in erecovery after the stable release.
Thanks

hsarao said:
No, ereceovery does not provide access to ADB. Has anyone checked if the EMUI 10 is available using erecovery? Some one was saying, EMUI 10 will only be available in erecovery after the stable release.
Thanks
Click to expand...
Click to collapse
yes thats true. depending on region/cust, stable release will pop up starting in december, but can potentially take until february/march....
Sent from my Huawei Mate 20 X EVR-AL00 using Tapatalk