There are several references in the bootloader to the /persistent partition. one of which is in very close proximity to the string "failed to erase bootloader unlock key"
Check OEM Unlock : No memory!...mmc read failure /persistent....Partition table doesn't exist...failed to erase partition...failed to erase bootloader unlock key
Click to expand...
Click to collapse
Could anyone dump their /persistent partition and compare its contents with that of their unlock.bin
If the bootloader unlock key is indeed flashed to the /persistent partition then removing it would essentially reverse unlocking the bootloader.
Any Dev's already tried this?
Anyone on the verge of unlocking willing to dump /persistent before and after the unlock procedure?
OllieD said:
There are several references in the bootloader to the /persistent partition. one of which is in very close proximity to the string "failed to erase bootloader unlock key"
Could anyone dump their /persistent partition and compare its contents with that of their unlock.bin
If the bootloader unlock key is indeed flashed to the /persistent partition then removing it would essentially reverse unlocking the bootloader.
Any Dev's already tried this?
Anyone on the verge of unlocking willing to dump /persistent before and after the unlock procedure?
Click to expand...
Click to collapse
If you put the instructions for dump the that partition maybe you catch some attention!
Enviado do meu LG-H815 através de Tapatalk
OllieD said:
There are several references in the bootloader to the /persistent partition. one of which is in very close proximity to the string "failed to erase bootloader unlock key"
Could anyone dump their /persistent partition and compare its contents with that of their unlock.bin
If the bootloader unlock key is indeed flashed to the /persistent partition then removing it would essentially reverse unlocking the bootloader.
Any Dev's already tried this?
Anyone on the verge of unlocking willing to dump /persistent before and after the unlock procedure?
Click to expand...
Click to collapse
This is a nice idea.
This is how to dump the persistent partition:
1. Get inside download mode and follow the following guide:
http://lgviet.com/forum/threads/huong-send-command-tren-lg-g4-android-6-0-marshmallow.53972/
2. Run with Send_Command.exe the following command:
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=23808 count=256 of=/data/media/0/persistent.img
3. Pull out the usb cable and the battery
4. Turn on your phone and connect it to computer
I attached my LOCKED H815L persistent partition
Al0n said:
This is a nice idea.
This is how to dump the persistent partition:
1. Get inside download mode and follow the following guide:
http://lgviet.com/forum/threads/huong-send-command-tren-lg-g4-android-6-0-marshmallow.53972/
2. Run with Send_Command.exe the following command:
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=23808 count=256 of=/data/media/0/persistent.img
3. Pull out the usb cable and the battery
4. Turn on your phone and connect it to computer
I attached my LOCKED H815L persistent partition
Click to expand...
Click to collapse
Thank you for this Al0n,
Now all I need is someone with an unlocked device to send me their persistent partition and a copy of their Unlock.bin.
Hi,
That is great ! I hope it will work so everybody can freely unlock and the relock his bootloader when needed. My phone was unlocked but it went into endless bootloop and now I got it repaired and now I'm afraid to unlock it again.
thewhisper said:
Hi,
That is great ! I hope it will work so everybody can freely unlock and the relock his bootloader when needed. My phone was unlocked but it went into endless bootloop and now I got it repaired and now I'm afraid to unlock it again.
Click to expand...
Click to collapse
I'm dabbling with the idea of unlocking myself.
I have a 506 tied to a 2 year contract, it was an upgrade I took 3 months ago which was about the time the issue became more public.
I would rather test this theory first before I have to argue with Carphone Warehouse that unlocking does not void my warranty as per EU law.
Given that the bootloop is a common hardware fault the Customer should not have such problems getting it resolved, regardless of what we have done software wise.
OllieD said:
I'm dabbling with the idea of unlocking myself.
I have a 506 tied to a 2 year contract, it was an upgrade I took 3 months ago which was about the time the issue became more public.
I would rather test this theory first before I have to argue with Carphone Warehouse that unlocking does not void my warranty as per EU law.
Given that the bootloop is a common hardware fault the Customer should not have such problems getting it resolved, regardless of what we have done software wise.
Click to expand...
Click to collapse
An even simpler test someone could try to relock bootloader is try:
fastboot erase unlock
I will try in a few days
Enviado desde mi LG-H815 mediante Tapatalk
Hi guys,
I checked the serial of my repaired phone and it seems that they changed my motherboard with new IMEI and serial. I checked my imei at imeidata.net and it decoded my IMEI and from there I saw it is with 604 serial, which means it is built in april this year. Can I now feel safe from bootloop again ? I'm still hasitating to unlock my bootloader again as I'm afraid if it bootloops I will not be covered by my waranty anymore. First time my phone was with bootloader unlocked and they repaired it but it was younger than an year. In june it makes it first year so I think after it they will not cover it by waranty if it is unlocked. What you think ? Am I safe from bootloop or not ?
thewhisper said:
Hi guys,
I checked the serial of my repaired phone and it seems that they changed my motherboard with new IMEI and serial. I checked my imei at imeidata.net and it decoded my IMEI and from there I saw it is with 604 serial, which means it is built in april this year. Can I now feel safe from bootloop again ? I'm still hasitating to unlock my bootloader again as I'm afraid if it bootloops I will not be covered by my waranty anymore. First time my phone was with bootloader unlocked and they repaired it but it was younger than an year. In june it makes it first year so I think after it they will not cover it by waranty if it is unlocked. What you think ? Am I safe from bootloop or not ?
Click to expand...
Click to collapse
wrong topic.And mate bootloop full random i think all G4 infected.No joker motherboard number.
My mate 60x moterboard and get bootloop.
I still stick to my thoughts that no device is safe. its luck of the draw.
Your chance of boot loop is simply a case of how badly manufactured your particular device is, how much you stress it and how old it is.
The issue seems to take on average 6 - 9 months before it cripples most devices.
This is a decent amount of time for LG to play the blame game, argue warranties and swap around/fix as few devices as possible until the G4 is end of life.
Most users upgrade their phones every year or two, so they will be hoping the majority of users will upgrade to a G5.
Now that my thread has been completely de-railed,
Any unlocked users willing to help out?
I still need someone to try:
fastboot erase unlock
and someone to dump their /persistent partition and send me it along with their unlock.bin.
OllieD said:
Any unlocked users willing to help out?
I still need someone to try:
fastboot erase unlock
and someone to dump their /persistent partition and send me it along with their unlock.bin.
Click to expand...
Click to collapse
I'm not sure when I will go back to stock or maybe sell my phone. Could be in a couple of days because the cam on CM13 isn't good as expected but then I would try
Just tried that erase command. Result:
Code:
C:\Android-SDK\platform-tools>fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.031s]
writing 'unlock'...
(bootloader) Erase userdata and cache
(bootloader) -----------------------------------------------------------
(bootloader) Bootloader Unlock key flash Success
(bootloader) -----------------------------------------------------------
OKAY [ 2.402s]
finished. total time: 2.449s
C:\Android-SDK\platform-tools>fastboot erase unlock
erasing 'unlock'...
FAILED (remote: cannot erase this partition in unlocked state)
finished. total time: 0.016s
Sadly, I forgot to dump my /persistent partition BEFORE the unlock. Anyway, I've got my dump of /persistent after the unlock and my unlock.bin right here, zipped up and ready. But i can't upload nor post a link yet since i'm new to the forums.
GaryBlack said:
Just tried that erase command. Result:
Code:
C:\Android-SDK\platform-tools>fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.031s]
writing 'unlock'...
(bootloader) Erase userdata and cache
(bootloader) -----------------------------------------------------------
(bootloader) Bootloader Unlock key flash Success
(bootloader) -----------------------------------------------------------
OKAY [ 2.402s]
finished. total time: 2.449s
C:\Android-SDK\platform-tools>fastboot erase unlock
erasing 'unlock'...
FAILED (remote: cannot erase this partition in unlocked state)
finished. total time: 0.016s
Sadly, I forgot to dump my /persistent partition BEFORE the unlock. Anyway, I've got my dump of /persistent after the unlock and my unlock.bin right here, zipped up and ready. But i can't upload nor post a link yet since i'm new to the forums.
Click to expand...
Click to collapse
Can you dump "unlock" partition?
Also, can you attach your unlock.bin file and your device-id?
Al0n said:
Can you dump "unlock" partition?
Also, can you attach your unlock.bin file and your device-id?
Click to expand...
Click to collapse
I'd gladly dump the unlock partition if i knew how. Could you give a few tips how to (or how i can find out the arguments/numbers needed for dd command)
Unfortunately, I can't attach files yet. But i can pm you a link to my unlock.bin.
DeviceID is:
BE4A51BE0E3459D56EE2ED45AC22765A
8849D9523196EB990DBE496426A41945
GaryBlack said:
I'd gladly dump the unlock partition if i knew how. Could you give a few tips how to (or how i can find out the arguments/numbers needed for dd command)
Unfortunately, I can't attach files yet. But i can pm you a link to my unlock.bin.
DeviceID is:
BE4A51BE0E3459D56EE2ED45AC22765A
8849D9523196EB990DBE496426A41945
Click to expand...
Click to collapse
as mentioned above:
dd if=/dev/block/mmcblk0 bs=8192 skip=23808 count=256 of=/data/media/0/persistent.img
Click to expand...
Click to collapse
OllieD said:
as mentioned above:
Click to expand...
Click to collapse
I've done this. It's in the zip file. I thought Al0n was talking about another partition, not /persistent
GaryBlack said:
I've done this. It's in the zip file. I thought Al0n was talking about another partition, not /persistent
Click to expand...
Click to collapse
Sorry I had no notification about your PM.
Just checked the files and was disappointed to see no unlock key in the persistent image...
However the final byte of the partition has been flipped from a 0 to a 1, on the two persistent images I have seen from unlocked devices it was 0.
It would be interesting to see if flipping it back to 0 relocks the boot-loader.
I would try flipping it on my locked device but I no longer have root.
OllieD said:
However the final byte of the partition has been flipped from a 0 to a 1, on the two persistent images I have seen from unlocked devices it was 0.
It would be interesting to see if flipping it back to 0 relocks the boot-loader.
I would try flipping it on my locked device but I no longer have root.
Click to expand...
Click to collapse
Just tried this. Had to flash back to lollipop for Send_Command to work for some reason.
Hex-editied my persistent.img and re-flashed it. No change on the bootloader state. However, I have noticed that the checkbox "Allow OEM unlock" in developer options persists, even over KDZ flashes, but after i flashed the modded persistent.img, the setting was unchecked. Maybe they're related?
OllieD said:
I still stick to my thoughts that no device is safe. its luck of the draw.
Your chance of boot loop is simply a case of how badly manufactured your particular device is, how much you stress it and how old it is.
The issue seems to take on average 6 - 9 months before it cripples most devices.
This is a decent amount of time for LG to play the blame game, argue warranties and swap around/fix as few devices as possible until the G4 is end of life.
Most users upgrade their phones every year or two, so they will be hoping the majority of users will upgrade to a G5.
Now that my thread has been completely de-railed,
Any unlocked users willing to help out?
I still need someone to try:
fastboot erase unlock
and someone to dump their /persistent partition and send me it along with their unlock.bin.
Click to expand...
Click to collapse
here they claim they relocked it... do you think LG can find out .. is it really relocked.?
am afraid to unlock due to the bootloop issue... will this work?
i have h811
http://forum.xda-developers.com/tmobile-g4/help/relock-bootloader-h811-t3372970
Related
Ahh, hind sight is a wonderful thing.
After trying to use kingroot to get root access, it failed. And a few days later after rebooting.
I'm now stuck at bootup with Start Up Failed.
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
I've now tried lot's of different things, over the last few hours.
RSDLite (show device brings no thing up)
Unlock bootloader (request key, but error regarding OEM unlock not being set - no access to now set it LOL)
Downloaded stock X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip, and tried using various guides on fastboot but keep getting remote failed.
I'm on stock recovery (obviously still locked).
Any thoughts, or hope from anyone?
Obviously, not sure what support Motorola would provide for what is essentially my own fault?
Have you tried manually flashing each bit of the stock firmware/image. That might help. There's a good guide here which I followed to unbrick my device. Just follow the instructions http://theunlockr.com/2015/09/22/how-to-unroot-the-motorola-moto-x-play/
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
sharebubbles said:
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
Click to expand...
Click to collapse
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
DTLblaze said:
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
Click to expand...
Click to collapse
I run the unlock command, with my unique key but I get ..
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.013s
And since I can't get into the phone, I can't therefore check the "allow OEM unclock"
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
DTLblaze said:
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
Click to expand...
Click to collapse
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Sickaxis79 said:
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Click to expand...
Click to collapse
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
sharebubbles said:
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Click to expand...
Click to collapse
That really does sound like you bricked the device. If you where on lollipop software you wouldn't have the issue with check bootloader OEM unlock. If it was me I would either contact Motorola or go to a repair shop and have a motd experienced person take a look at it.
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
sharebubbles said:
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
Click to expand...
Click to collapse
Strange. This is the tool I used to unlock my bootloader.
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
I've ben used the latest rom so far why trying to flash (and failing) when I look at recovery I have a LPD23.118-10 number that matches to an earlier 5.1.1 rom (I had been upgraded to 6.0.1 via OTA updates) - do I therefore take that LPD ID to mean that I should actually use the 5.1.1 rom - I'm in the UK, so I'm assuming I'd use the UK one rather than Europe (I'm looking at roms on https://github.com/motoxplay/stock).
Thanks
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
And also never try kingroot.
sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
Most in the threads suggesting using rsdlite or manual flash/root and you decided to use kingroot,haha.
Welcome back.
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
---------- Post added at 05:26 AM ---------- Previous post was at 05:14 AM ----------
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
Tried restoring it, deleted everything and the phone is still on bootloader (LOCKED) and i dont even know how to fix it, I know nothing on how to root, friend suggested it, downloaded it, installed it, didnt work and then i restarted my phone and now its stuck on bootloader screen and the screen has the message "Start up failed: your device didnt start up successfully. Use the software repair assisstant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant." <- Downloaded it, tried it and it was stuck on 6% on repairing, left it over night and it was still on 6%.
ALSO under the message "AP Fastboot Flash Mode(Secure) is there)
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
pravin kkr said:
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
Click to expand...
Click to collapse
Download and flash this firmware
https://mega.nz/#!H5YlDCrD!T8tAAW7nHVS-erizRiqg5-Yp_p23hKParMjjHD4diQA credits @kumeipark
Use RSD lite to flash the firmware
http://rsdlite.com/rsd-lite-download/
Moto drivers
http://motorola-mobility-en-in.custhelp.com/app/answers/detail/a_id/88481
If you have problems installing device drivers using Windows 8.1 or Windows 10 follow this guide
https://www.youtube.com/watch?v=gmw86KplqmU
And don't post your contact no. in public forums for everyone to see.
what is the decryption key for the mega link
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
provide the decryption key
Hello xda,
my cousin owns the P8Lite (PRA-LX1) and gave it to me to attempt unbricking it.
The device is stuck in a permanent bootloop, showing the Huawei logo. When pressing the power button for ~10s, it simply turns itself on again (even when not connected to a PC or the wall socket), which to me is very strange behaviour but I do not own a Huawei device.
I can get to fastboot (https://ibb.co/ixPtAn).
ADB does not recognize the device.
Fastboot does not let me boot a temporary recovery (be it the stock one or twrp), neither does it allow me to flash any file.
I have tried downloading the update.app file onto the root directory of the sd card and force the phone into the update mode (power, vol+, vol- at the same time) but to no avail.
Since it is not my own device and I cannot boot into Android at all, I have no way of getting to the IMEI of the device, which I would need to unlock the bootloader.
Is this device permanently bricked and a lost cause or is there still hope?
dejavecue said:
I have no way of getting to the IMEI of the device, which I would need to unlock the bootloader.
Click to expand...
Click to collapse
Hi,
IMEI should be engraved on the lower SIM tray if it's the original one.
HTH
badhabitsdiehard said:
Hi,
IMEI should be engraved on the lower SIM tray if it's the original one.
HTH
Click to expand...
Click to collapse
Oh yes I got the original one. But since I cannot boot, I cannot get the S/N that is apparently required as well.
Edit: Got the SN through fastboot devices.
Now the phone won't accept the unlock code that I got from huawei's website. It still says
PS C:\Users\*\Downloads\unlock bootloader> fastboot oem unlock ************
...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
PS C:\Users\*\Downloads\unlock bootloader>
Click to expand...
Click to collapse
dejavecue said:
Got the SN through fastboot devices.
Now the phone won't accept the unlock code that I got from huawei's website.
Click to expand...
Click to collapse
Hi, sorry for the delay.
Try this, if not already tried: fastboot oem emmc_diag
It should check the status of emmc and tell you if it's ok.
Does this command: fastboot oem lock-state info work on your phone?
And putting the code Huawei sent you in this one fastboot oem frp-unlock?
Thank you for your comment:
badhabitsdiehard said:
Try this, if not already tried: fastboot oem emmc_diag
It should check the status of emmc and tell you if it's ok.
Click to expand...
Click to collapse
Code:
$ fastboot oem lock-state info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: LOCKED
OKAY [ 0.012s]
finished. total time: 0.014s
badhabitsdiehard said:
Does this command: fastboot oem lock-state info work on your phone?
And putting the code Huawei sent you in this one fastboot oem frp-unlock?
Click to expand...
Click to collapse
Code:
$ fastboot oem frp-unlock {password censored}
...
FAILED (remote: password matching failed!!)
finished. total time: 0.211s
It is definitely the code I got from the Huawei Website.
Hello, i have a serious problem with my U Ultra.... Last night I unlocked the bootloader, I installed TWRP(lastest version from official site), before all this I made backup (with TWRP) of every partition and then I make back-up of system, data, boot I think, I have everything on my laptop.
But I wanted to back on stock (Don't ask me why...) and i restored a back-up, a full back-up of every partitions. Everything great, but google play didn't had Device Certification: Uncertified like in this pic and I tried to do this method and it didn't worked and I don't know why I thought that if I will relock the bootloader, everything will be okay :| and now I don't have TWRP anymore and of course neither stock recovery, but the stock rom boots but the password I have made it, is not working.
Tried to unlock bootloader but this error shows up
Code:
diesel-X550CL Downloads # fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1578400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.006s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
Now how can I solve this problem?
How did you did the bootloader relocking?
For what purpose you need the Google Play certification?
QDT said:
How did you did the bootloader relocking?
For what purpose you need the Google Play certification?
Click to expand...
Click to collapse
Through fastboot with this command:
Code:
fastboot oem lock
I don't need it for a special purpose but some apps don't work and I saw that was the solution, anyways I don't need that no more, I just want the phone to work....
Just go to fastboot mode perform oem unlock and reinstall the twrp
QDT said:
Just go to fastboot mode perform oem unlock and reinstall the twrp
Click to expand...
Click to collapse
Code:
fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1578400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.006s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
I can't because oem unlock is not turned off
kempactick said:
I can't because oem unlock is not turned off
Click to expand...
Click to collapse
You don't need to use the HTC file. Your phone is permanently hardware unlocked since the first flash.
All you now need to do is simple
Code:
fastboot oem unlock
QDT said:
You don't need to use the HTC file. Your phone is permanently hardware unlocked since the first flash.
All you now need to do is simple
Code:
fastboot oem unlock
Click to expand...
Click to collapse
i tried this one too...
Code:
diesel-X550CL Downloads # fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.005s
This error are just because of oem unlock from developer settings.. How can I trick this?
kempactick said:
i tried this one too...
Code:
diesel-X550CL Downloads # fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.005s
This error are just because of oem unlock from developer settings.. How can I trick this?
Click to expand...
Click to collapse
In what mode are you?
QDT said:
In what mode are you?
Click to expand...
Click to collapse
I'm on download mode, bootloader mod ain't for flashing
kempactick said:
I'm on download mode, bootloader mod ain't for flashing
Click to expand...
Click to collapse
Then what I can only advise is getting RUU of your system's current or newer version and force to reflash everything including bootloader.
QDT said:
Then what I can only advise is getting RUU of your system's current or newer version and force to reflash everything including bootloader.
Click to expand...
Click to collapse
Tried to flash RUU but is not working too, i'm trying with htc sync right now
I have the same issue after relocking my phone. Before I decided to lock my phone to downgrade to nougat, I did flash twrp and a rooted stocked oreo rom. After locking my phone using fastboot my phone stuck into download mode bootloop, I was able to get into download mode properly but I couldn't afford to download ruu from easy-firmware to flash in ruu mode
iAlcatrazZ said:
I have the same issue after relocking my phone. Before I decided to lock my phone to downgrade to nougat, I did flash twrp and a rooted stocked oreo rom. After locking my phone using fastboot my phone stuck into download mode bootloop, I was able to get into download mode properly but I couldn't afford to download ruu from easy-firmware to flash in ruu mode
Click to expand...
Click to collapse
I couldn't solve the problem myself, so I went to a gsm service and they couldn't solve it, 1 month of trying and one day my dad told me to go to the warranty service and I didn't, he went there and I don't know how they accepted the phone with the another reason and in a hour they solved the problem. I'm still using the phone and I can't wait to get rid of it.
So... I don't know how to help you, you should go to a gsm service, regards!
kempactick said:
I couldn't solve the problem myself, so I went to a gsm service and they couldn't solve it, 1 month of trying and one day my dad told me to go to the warranty service and I didn't, he went there and I don't know how they accepted the phone with the another reason and in a hour they solved the problem. I'm still using the phone and I can't wait to get rid of it.
So... I don't know how to help you, you should go to a gsm service, regards!
Click to expand...
Click to collapse
I managed to restore my phone :v, I could partially remember how I did it, I'm still gathering resources so that I can write a complete guide for everyone
Posting a new thread was my last resort, so here goes.
I'm looking for a TWRP recovery for a HTC One M9e PCE. It's obviously a rarer model so finding stuff for it is incredibly hard. While searching the forum I came to the conclusion that there once was a file named twrp-3.0.0.2-HIMAR.img hosted on androidfilehost. But all the links are dead.
Does anyone have a copy of that image lying around? I would greatly appreciate if someone would upload it again. If I'm not mistaken the author of that recovery was mars3712, if that helps.
EDIT: I'm aware that there's a repo on github also, though unfortunately it's on a 5.1 base. The device in question is 6.0 MM. Would it matter?
http://www.mediafire.com/folder/2wd1oprpj5ija/HTC_M9_PCE
twrp-3.0.2-0-himar2.img and twrp-3.0.2-1-himar2.img
Click to expand...
Click to collapse
both working perfect on my HTC M9 PCE better use newer
in 10min in folder will be uploaded
2PRGIMG_HIMAR_ML_UHL_M60_SENSE70GP_HTC_Europe_2.32.401.1_Radio_1.1550V70.2508.0304_HU[W.T]_release_488703_combined_signed_2_4.zip
Click to expand...
Click to collapse
to install from sd format sd download rom rename to 2PRGIMG.zip place on sd power and vol- (or + dont remember) and rom should install auto in download mode
Amazing, thanks for the upload. Apparently I need S-OFF to flash this. I've flashed some janky TWRP on this phone before and it never needed S-OFF. Any thoughts? Already running the ROM you posted.
Code:
[email protected]:~/Downloads$ sudo fastboot flash recovery twrp-3.0.2-1-himar2.img
target reported max download size of 134217728 bytes
sending 'recovery' (13544 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) Image verification failed...
FAILED (remote: Err! Stop flashing due to S-ON...
)
finished. total time: 1.395s
You unlock bootloader at htcdev.com right?
I will back home in 2/3 hours and look on problem
GeoEgbA said:
You unlock bootloader at htcdev.com right?
I will back home in 2/3 hours and look on problem
Click to expand...
Click to collapse
Yes, the phone is unlocked.
Sorry just back home 2days away. So you must relock bootloader fastboot oem lock restart phone and again unlock bootloader but may use Unlock_code.bin if you have it from first unlock, if no then again generate it on htcdev
I did 2 tests, install clean rom from sd (2PRGIMGizip) and after try flash recovery and get same error as you, one dev i have s-on seccond s-off in both case after flash rom do
fastboot oem lock
Click to expand...
Click to collapse
then
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
I used old tocken from first unlocking and after this
htc_fastboot flash recovery twrp-3.0.2-1-himar2.img
Click to expand...
Click to collapse
and work perfect in both case
So lock and relock bootloader
Try this and give feedback if all ok, i didnt sleep over 50h so my english grama may be little wrong
Will check here in fiew hs now i go rest.
GeoEgbA said:
Sorry just back home 2days away. So you must relock bootloader fastboot oem lock restart phone and again unlock bootloader but may use Unlock_code.bin if you have it from first unlock, if no then again generate it on htcdev
I did 2 tests, install clean rom from sd (2PRGIMGizip) and after try flash recovery and get same error as you, one dev i have s-on seccond s-off in both case after flash rom do
then
I used old tocken from first unlocking and after this
and work perfect in both case
So lock and relock bootloader
Try this and give feedback if all ok, i didnt sleep over 50h so my english grama may be little wrong
Will check here in fiew hs now i go rest.
Click to expand...
Click to collapse
Hello, do you happen to have the different region (CID HTC__621) RUU for my HTC One M9s (himaruhl)? Thank you very much!
Thanks for the information you provided
---------- Post added at 01:35 PM ---------- Previous post was at 01:28 PM ----------
I have installed twrp data password
Hello....I am getting the following error when trying to unlock the bootloader through fastboot even after I obtained 288bytes unlock.bin file from the OnePlus website. My network is still locked to T-Mobile, but I have heard of people unlocking the bootloader while network is still locked.
Unlocking Bootloader...
Sending 'cust-unlock' (0 KB) OKAY [ 0.000s]
Writing 'cust-unlock' FAILED (remote: 'Error - Verify Failed ! (4:-2)')
fastboot: error: Command failed
FAILED (remote: 'Please flash unlock token first.')
fastboot: error: Command failed
Tried with the bin file in the platform tools folder and same error as below:
PS C:\Users\alvcr\Desktop\platform-tools> fastboot flash cust-unlock unlock.bin
target reported max download size of 805306368 bytes
sending 'cust-unlock' (0 KB)...
OKAY [ 0.015s]
writing 'cust-unlock'...
FAILED (remote: Error - Verify Failed ! (4:-2))
finished. total time: 0.032s
Please help. Thanks.
U have to get unlock token from oneplus. Or have a bypass for it. Which i do. But wont release
I have the bin file as mentioned in my original post. Just don't know what the 'Verify Failed ! (4:-2))' error means.
Alcross888 said:
I have the bin file as mentioned in my original post. Just don't know what the 'Verify Failed ! (4:-2))' error means.
Click to expand...
Click to collapse
It means you have the wrong unlock token. The only workaround I know of is to convert your variant to Europe with the MSM from another thread. That won't require a unlock.bin code and you can just unlock the bootloader simply by fastboot flashing unlock. If I had another bypass, I would share it with you, some people are just not willing to be very helpful.
TheSayaMan said:
It means you have the wrong unlock token. The only workaround I know of is to convert your variant to Europe with the MSM from another thread. That won't require a unlock.bin code and you can just unlock the bootloader simply by fastboot flashing unlock. If I had another bypass, I would share it with you, some people are just not willing to be very helpful.
Click to expand...
Click to collapse
Ohh thank you so very much brother. That was very kind of you to help me. Will a my data be erased if I convert to the EU version and also is there any way or tool to unlock my network that is tied to T-Mobile
Alcross888 said:
Ohh thank you so very much brother. That was very kind of you to help me. Will a my data be erased if I convert to the EU version and also is there any way or tool to unlock my network that is tied to T-Mobile
Click to expand...
Click to collapse
sim unlock is totally different, I can't help you with that, but yes, your phone will be wiped, so back everything up. I had the same problem as you have. I received a unlock token code that won't verify either and EU is the only workaround I know. You can always MSM back to T-Mobile if you decide not to stay with EU but then you will require a unlock token again.
TheSayaMan said:
sim unlock is totally different, I can't help you with that, but yes, your phone will be wiped, so back everything up. I had the same problem as you have. I received a unlock token code that won't verify either and EU is the only workaround I know. You can always MSM back to T-Mobile if you decide not to stay with EU but then you will require a unlock token again.
Click to expand...
Click to collapse
Ohh okay. I heard someone say that
Unlocked bootloader without unlock_token must be done while in OOS11, as OOS12+ ABL will check that a token is needed
I am on Android 12.
Alcross888 said:
Ohh okay. I heard someone say that
Unlocked bootloader without unlock_token must be done while in OOS11, as OOS12+ ABL will check that a token is needed
I am on Android 12.
Click to expand...
Click to collapse
yes but when you MSM to EU, you will be back on 11 so you can. Just do it before you update back to 12.
Oh okay...so I can still unlock the bootloader although Im now on Android 12 since I get downgraded to 11 after the EU conversion right? That's great brother. Thank you so very much for a the help. I greatly appreciate it.
Alcross888 said:
Oh okay...so I can still unlock the bootloader although Im now on Android 12 since I get downgraded to 11 after the EU conversion right? That's great brother. Thank you so very much for a the help. I greatly appreciate it.
Click to expand...
Click to collapse
yes correct, and no problem anytime. When you convert to EU it will put you back on 11. Then unlock bootloader first. Then you can update back to 12 and it won't matter because your bootloader will already be unlocked.
TheSayaMan said:
yes correct, and no problem anytime. When you convert to EU it will put you back on 11. Then unlock bootloader first. Then you can update back to 12 and it won't matter because your bootloader will already be unlocked.
Click to expand...
Click to collapse
Thanks a million for clarifying bro.
Alcross888 said:
Thanks a million for clarifying bro.
Click to expand...
Click to collapse
Your welcome