Database Users

Turbo Unbrick for Android 4.4.4 - 5.1

There are a few types state of brick of the phone. Let's review two of them:
1. “Softbrick” - the state when the system is not booting, but the PC recognizes the phone as “ADB Device” and the phone can boot to bootloader mode. This state is like a baby's runny nose and can be healed by the simple reflash using RSDLite (the tool avaliable for everybody), or by reflashing the parts of firmware via fastboot.
2. 'Hardbrick' - the hard case that needs a lot of work and knowledge. Sometimes hardware intervention needed in order to fix the phone (test-point contacts closure, battery disconnection, etc). Sometimes the phone could not be repaired without motherboard replacement.
We'll review the phone recovery after the second type of bricking.
The phone in “hardbrick” state is recognized by PC as:
- “Unknown device”. In this case you need to install the Qualcomm USB drivers on PC by hands from the attached file "Qualcomm_USB_Drivers.7z" (download it and unpack to any path you want). The phone will be recognized by PC as “Qualcomm HS-USB Diagnostics 9008” device after the driver's installation. Sometimes it is needed to disconnect the phone and to hold the power button during 20-30 seconds to recognize the phone.
- “Qualcomm HS-USB Diagnostics 9008” (nothing happens when you press the buttons on the phone). No needed installation driver's in this case.
The PC will see your phone as shown on picture.
{
"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"
}
Then the wonderful utility “TURBO-UNBRICK” comes to the rescue. This is a small program but it makes a great job.
Unpack the archive that includes the utility, connect the phone to PC and run “go” file. And you will observe that your brick will become alive! You will see the next picture at your revived phone's screen:
It's almost a win but you need to make some more actions.
Put the files gpt.bin, radio.img, bootloader.img (also attached), to the “C:\adb” folder on your PC and run the next commands in the command line:
Code:
fastboot flash partition gpt.bin
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot reboot
Now you can enjoy! Your friend is alive and greets you by its bootanimation. In that case when you've broken the firmware and the phone is not booting after the bootanimation, you need reboot in bootloader and reflash the firmware by RSDLite.
Android 4.4.4
Link to download the attached files
https://drive.google.com/open?id=0B-o0d4PkVUwBflNNbF96UWx1N1JtVkY5S1JrM25lemIxVFgtTEdwb0lEUmxqYzlqc2VfZzg&authuser=0
Android 5.1
Link to download the attached files
https://drive.google.com/open?id=0B...l3YThKNE5iWkw3eVgtNzl5aXQwTTdCNElBVTd5VWc5V3c

Thanks bud, I wasn't able to register with my gmail account.

Turbo unbrick
Wish I had this a month ago,had to send my phone off to be jtagged.I'm sure I'll need it again.Thank you for your work.

kinglove1211 said:
Wish I had this a month ago, had to send my phone off to be jtagged. I'm sure I'll need it again. Thank you for your work.
Click to expand...
Click to collapse
I also went through it . Therefore, I decided to share this experience. :highfive:

ilia3367 said:
Link to download the attached files
https://drive.google.com/open?id=0B-o0d4PkVUwBflNNbF96UWx1N1JtVkY5S1JrM25lemIxVFgtTEdwb0lEUmxqYzlqc2VfZzg&authuser=0
Click to expand...
Click to collapse
Latest Radio / Firmware ?
Where's the img of recovery, I need?

@ilia3367,
Thank you for the great contribution, it is good to know you are unbrickable with these tools.

Great info should be in android development

arohrmann said:
Latest Radio / Firmware ? Where's the img of recovery, I need?
Click to expand...
Click to collapse
Firmware - 21.44.12
Radio - MDM9625_104351.17.02.71.13R
IMG recovery need not.

Will this technique work on a Droid Maxx?
Sent from my XT1254 using XDA Free mobile app

Too bad we can't use this to reprogram the turbos to be the xt1250 so that the bl can be unlocked.I bricked my phone purposely to try and flash the XML of the moto maxx and it will only let me flash the system for the turbo.It does unbrick your phone though,did it 3 times in a row so it definitely works.

failed to flash gpt.bin
When i try to flash the given files, flashing of gpt.bin results into "remote failure" and says "preflash validation failed". Rest all the files are flashed perfectly. But cannot flash gpt.bin. Please help

chiranjiv97 said:
When i try to flash the given files, flashing of gpt.bin results into "remote failure" and says "preflash validation failed". Rest all the files are flashed perfectly. But cannot flash gpt.bin. Please help
Click to expand...
Click to collapse
This method is intended for Verizone Motorola Droid Turbo. gpt.bin for this phone . What's your phone? Try to flash through motofastboot.

ilia3367 said:
This method is intended for Verizone Motorola Droid Turbo. gpt.bin for this phone . What's your phone? Try to flash through motofastboot.
Click to expand...
Click to collapse
I
Yess I know, I used Motorola droid turbo Verizon xt1254, running on quark 21.44.12. I'm not quite sure about how to use the motofastboot? It'll be great if you can help, thanks a lot

chiranjiv97 said:
I'm not quite sure about how to use the motofastboot? It'll be great if you can help, thanks a lot
Click to expand...
Click to collapse
Download this archive https://drive.google.com/open?id=0B-o0d4PkVUwBR0FiUHNKRUxIXzQ&authuser=0
Unpack it to C: \ drive
Copy this folder gpt.bin
Flash it command - mfastboot flash partition gpt.bin

have you tried the mot dev manager? that should detect a brick and set back to factory. rsdlite could also be used

This happened to my phone and I tired using the TURBO-UNBRICK you provided, but it gets to 'flashing singleimage' and I get 'Target ERROR: 7 - Open multi failed, unkown error FAILED (sdl-transfer-image:send-image:sdl-open-multi:target error)
My phone bricked after I started the Lollipop update. No idea what happened. I started the update, went back to work, checked half an hour later and phone was dead. Any help would be great, this is the closest I've gotten to getting it fixed.
~Zanny

Anybody tried this tools for xt1254 ?

will this work if i bricked it after installing 5.1?

I did everything descripted in this thread, but my device keeps rebooting (I can hear the USB disconnecting and reconnecting) and still shows up as a QDLoader in device manager. Plus the screen is still black. Any toughts?
Edit: is this singleimage (msimage_901_0228_0000) right? Usually it's a .bin file, but this one is a .mbn

ilia3367 said:
Download this archive
Unpack it to C: \ drive
Copy this folder gpt.bin
Flash it command - mfastboot flash partition gpt.bin
Click to expand...
Click to collapse
Hey, sorry was away! but the link is broken, it says removed due to violation of terms :/ and i cannot post the link in the quote coz xda is preventing me -.-

[Q] nexus 7 (2012) tablet, soft bricked, can't flash images, failed, unknown error

i have a Nexus 2012 7inch tablet (Wifi) that is soft bricked. (stuck at the perpetual moving colored dots screen).
when my tablet was still under warranty in 2013 it did have it's motherboard replaced when it wouldn't even turn on. now the problem is different, at least i can power it on and get into the bootloader. since the lollipop update it had been getting progressively laggy before finally 'crashing' and bootlooping.
i've tried the following:
1) first i attempted the tutorial located here: http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
i managed to wipe the device but not flash the images to the device.
2) then i used this tutorial http://forum.xda-developers.com/showthread.php?t=2588979 to install the adb drivers.
3) i have now used Wugs to attempt flash stock + unroot. everything seems to work until it gets to "sending 'system'" then it gives "FAILED <data transfer failure <Unknown error>>, also same error for sending 'userdata'and post-flash factory reset. same Unknown error.
i am also not sure which google images to use. i have tried nakasi 4.3 (JWR66Y), 4.4.4 (KTU84P), and 5.1.1 (LMY47V), and "any build" options.
so i'm not sure if it could be a driver issue or how to fix it further. fastboot seems to recognize the tablet while adb does not. i did not have it set in debugging mode.
i've attached the screen from Wugs...
{
"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"
}

stargirl29 said:
i have a Nexus 2012 7inch tablet (Wifi) that is soft bricked. (stuck at the perpetual moving colored dots screen).
when my tablet was still under warranty in 2013 it did have it's motherboard replaced when it wouldn't even turn on. now the problem is different, at least i can power it on and get into the bootloader. since the lollipop update it had been getting progressively laggy before finally 'crashing' and bootlooping.
i've tried the following:
1) first i attempted the tutorial located here: http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
i managed to wipe the device but not flash the images to the device.
2) then i used this tutorial http://forum.xda-developers.com/showthread.php?t=2588979 to install the adb drivers.
3) i have now used Wugs to attempt flash stock + unroot. everything seems to work until it gets to "sending 'system'" then it gives "FAILED <data transfer failure <Unknown error>>, also same error for sending 'userdata'and post-flash factory reset. same Unknown error.
i am also not sure which google images to use. i have tried nakasi 4.3 (JWR66Y), 4.4.4 (KTU84P), and 5.1.1 (LMY47V), and "any build" options.
so i'm not sure if it could be a driver issue or how to fix it further. fastboot seems to recognize the tablet while adb does not. i did not have it set in debugging mode.
i've attached the screen from Wugs...
Click to expand...
Click to collapse
Try flashing the images individually with fastboot. That's how I always do it. Be sure your platform tools are up to date as well.

fastboot
Evolution_Tech said:
Try flashing the images individually with fastboot. That's how I always do it. Be sure your platform tools are up to date as well.
Click to expand...
Click to collapse
i'm not really sure how to do that.

stargirl29 said:
i'm not really sure how to do that.
Click to expand...
Click to collapse
Download and unzip the factory image. Unzip two times until you have all the images. I.E. bootloader, radio, boot, system, recovery, userdata, cache.
Put them where fastboot can find them. I.E. platform tools folder.
Hopefully you know how to use fastboot.
Start by flashing bootloader.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
Then flash the rest.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot format cache
fastboot flash cache cache.img
fastboot reboot

fastboot
Evolution_Tech said:
Download and unzip the factory image. Unzip two times until you have all the images. I.E. bootloader, radio, boot, system, recovery, userdata, cache.
Put them where fastboot can find them. I.E. platform tools folder.
Hopefully you know how to use fastboot.
Start by flashing bootloader.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
Then flash the rest.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot format cache
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
no i do not know how to use fastboot. but what you posted sounds exactly like the tutorial that i followed in step #1 that i mentioned above. i did the tutorial again last night and was able to flash the images this time, but it's still stuck in bootloop on startup.

stargirl29 said:
no i do not know how to use fastboot. but what you posted sounds exactly like the tutorial that i followed in step #1 that i mentioned above. i did the tutorial again last night and was able to flash the images this time, but it's still stuck in bootloop on startup.
Click to expand...
Click to collapse
Factory reset from recovery.

Evolution_Tech said:
Factory reset from recovery.
Click to expand...
Click to collapse
if you mean this, https://support.google.com/nexus/answer/4596836?hl=en
yes. that was the first thing i did. and always the first thing i try before using any toolkits or manual repairs.
i ran Wugs again today and FINALLY got it back to the sign in screen to setup the tablet. everything was going great. then i got back into the bootloader to lock the oem. and when it restarted i'm still getting the "optimizing apps x of 99" which is annoying but it seems my tablet is at least usable for now.

Sorry to say your in the same boat as a large number of people. These devices just up and died. Take a look around for #Nexus7Bricked
Google forums will also confirm this. At this time you have a nice paperweight. I've tried all the things you have (and spent probably 10 hours over a few months) and it still won't come up.

fixed it!
vipthomps said:
Sorry to say your in the same boat as a large number of people. These devices just up and died. Take a look around for #Nexus7Bricked
Google forums will also confirm this. At this time you have a nice paperweight. I've tried all the things you have (and spent probably 10 hours over a few months) and it still won't come up.
Click to expand...
Click to collapse
i fixed it with Wugs yesterday, finally! after 5 days of trying.

No OS installed mate 9

Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...

scrutnizing said:
Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...
Click to expand...
Click to collapse
Do you have adb/fastboot drivers installed? If not: https://forum.xda-developers.com/showthread.php?t=2317790
When you have that installed, boot into TWRP then tap on the Reboot button and then on the Bootloader button.
Plug in USB and open a command prompt, type the following command:
fastboot oem get-build-number
Post the result here

i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.

scrutnizing said:
i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.
Click to expand...
Click to collapse
Ah, then you're on Nougat.
The reason I asked about fastboot was to find out what build/fw you were on, then go from there to install stock firmware.
You could update to Oreo using: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108

hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.

scrutnizing said:
hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.
Click to expand...
Click to collapse
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/

ante0 said:
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/
Click to expand...
Click to collapse
@ante0
{
"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"
}
Can you give a hand, please ?
I unlocked the bootloader and flashed the recovery, the system booted successfully.
I tried to flash a ROM after that, it showed errors and didn't complete the flashing. since that time the phone has bootloop.
Unlocked bootloader and FRP
fastboot oem get-build-number : MHA-L29 8.0.0.374(C185)
I can access the TWRP recovery and erecovery and bootloader&fastboot
what I have already tried :
1-Fastboot flash ramdisk and kernel .
2-Tried to flash the stock firmware via TWRP.
3-Tried HurUpdater0.3
4- Extract update.app & HOWTA
5-Flash ramdisk and kernel from inside TWRP

is possible unbrik Mate9 Oreo , using only fastboot method ?
can help umbrik only commands fastboot?

Bricked Zenfone 3 ZE552KL - This package is for "WW_Phone" device. This is a ""

Bricked Zenfone 3 ZE552KL - This package is for "WW_Phone" device. This is a ""
I'm handling a bricked Zenfone 3 ZE552KL WW model, but I am unable to flash the stock rom back into the device.
For context, this device has never been unlocked, rooted, and always worked under its original factory Android. As told by the owner, he received an OTA update notification last week and confirmed all prompts to initiate the update. As instructed, he plugged the device to its original charger, left the update running and went by with his day doing other stuff. When he returned, the device was completely OFF with 0% battery. We figured the charging cable disconnected due to a bad connector endpoint, and the phone ran out of juice while the update was running!
The result is a bricked Zenfone unable to boot beyond the ASUS logo. It keeps crashing and gets into a boot loop.
I have tried most of the basic tech support I can give him.
I have downloaded a fresh copy of the official ZE522KL firmware from the ASUS website.
I can boot the phone into recovery, which is still the original ASUS recovery. But as I try to flash the firmware, I get this lovely error message:
{
"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"
}
ERROR: This package is for "WW_Phone" device. This is a "".
I know for a fact this is a WW_Phone device because when I try to flash the JP firmware, the error message is different.
ERROR: This package is for "JP_Phone" device. This is a "WW_Phone".
Already tried "Wipe data/factory reset" and "Wipe cache partition" from the recovery menu, but that didn't help.
Already tried pushing the firmware via "adb sideload" and placing it in a SD card. Those didn't help either.
I am also willing to flash a community ROM, like LineageOS or Mokee, but I first need to unlock the bootloader. I'm running adb and fastboot from Linux, and I can't find a descent tool to unlock using Linux is proving to be a real pain. Every tool seems to be made for Windows only.
So, I'm resorting to anyone here, hoping anyone could give me a light before we send this phone directly to ASUS tech support, not available in our region (we'll need to ship it to another city).
Anything I can try before that? I'm running out of ideas.
Best regards and thanks in advance for any help.

Trying to post a screenshot of the error:
https://i.imgur.com/5RHXM3c.jpg

Flash the latest stock recovery thru fastboot and then flash the latest raw firmware.
Otherwise try launching, not flashing, twrp thru fastboot and then flash any raw firmware with the updater script edited.

wang1chung said:
Flash the latest stock recovery thru fastboot and then flash the latest raw firmware.
Otherwise try launching, not flashing, twrp thru fastboot and then flash any raw firmware with the updater script edited.
Click to expand...
Click to collapse
Since his phone is locked, he can't flash anything except RAW firmware.
---------- Post added at 11:52 AM ---------- Previous post was at 11:41 AM ----------
juliohm said:
Trying to post a screenshot of the error:
https://i.imgur.com/5RHXM3c.jpg
Click to expand...
Click to collapse
Hey juliohm,
Just follow these steps & your device will operate normally
1) Download and install ASUS Flash Tool :
2) Download Latest Oreo RAW
ZE520KL:
ZE552KL:
3) Enter Fastboot Mode (Power + Volume Up)
4) Open ASUS Flash Tool
5) Select device & select firmware (select YES on wipe data tab too)
6) Connect phone to PC
7) Hit Start and wait 10-15 minutes (ignore the error 5 [FRP])
MOD EDIT: PAY-PER-CLICK LINKS REMOVED

Thank you, Saktis_STi. But these are Windows tools and I'm running Ubuntu on my local system. No Linux tools available for this task?

juliohm said:
Thank you, Saktis_STi. But these are Windows tools and I'm running Ubuntu on my local system. No Linux tools available for this task?
Click to expand...
Click to collapse
Check PM

Try unlocking your bootloader using the unofficial way located in the Zenfone 3 forum. It should be doable because you only have to boot into your bootloader. You can then flash a custom recovery, such as TWRP, and go in and wipe data, cache + dalvik, and then install a custom ROM. In your case, it looks like the stock recovery can't detect the device model (WW_Phone), so it's most likely that something is wrong with the system partition.

GrenadeofTacos said:
Try unlocking your bootloader using the unofficial way located in the Zenfone 3 forum. It should be doable because you only have to boot into your bootloader. You can then flash a custom recovery, such as TWRP, and go in and wipe data, cache + dalvik, and then install a custom ROM. In your case, it looks like the stock recovery can't detect the device model (WW_Phone), so it's most likely that something is wrong with the system partition.
Click to expand...
Click to collapse
No need. Flash RAW firmware is enough.

Just a quick follow up.
The owner decided to take it a local assist shop. I don't know what method they used, but they managed to reflash the stock firmware back into the device, and it's working fine again.
Thank you all for the tips. If this was my own device, I would be tinkering a lot more. But the owner decided to play safe and pay for repair in some authorized assistence shop.
Best regards all!

[Z00T/ZE551KL] Frustrating Bootloops -- Hardware issue?

Update: Someone suggested battery replacement. I installed my brother's phone "good" battery and it didn't fix the problem.
Having a weird situation with bootloops that worsened over time. I'm thinking it could be due to failed hardware? Maybe someone has experienced this and we can all benefit from this.
So, I kept going into random bootloops for the last 6 months. Happens during normal usage on lineage ROM AND stock ROM.
It boots into first boot screen, after ~10 seconds it blinks blue screen and reboots again.
Video:
https://youtu.be/4yCeb1J7jcs
I was sometimes able to get out of bootloop by placing phone in charger until the bootloop stops and the phone boots.
When this failed sometimes, I would go back to stock by either back2stock.zip by the great LuK1337 and sometimes from fastboot by doing the following:
While in fastboot I would boot into TWRP from adb >> wipe everything then flash stockrecovery.img >> boot into stock recovery >> while in stock recovery I flash oldest stockfirmware zip from there >> perform factory reset from within recovery then reboot.
It would always boot successfully.
Now my bootloop has worsened and no method is working out for me.
Is my phone defective? Any idea what part would be defective?
Note that it suffered from excessive heat in its recent months.
I can get into fastboot/TWRP/stockrecovery. But that's it.
Bootloader is apparently still unlocked:
{
"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"
}
Thanks a lot.

Have you flash back to original Asus image & slowly up the firmware versions?
Procedures:
1st
Phone (old firmware) > unlock bootloader > install TWRP > install custom rom > issues/unstable/more issues.
2nd
Phone (latest firmware) > unlock bootloader > install TWRP > install custom rom >
If 1st step was performed you need to go back & lock up the bootloader in order to update the firmware to the latest.
Asus firmware updates security/unstable & another issues...after that, you can them use custom roms to your pleasing.
Good place to start.
https://www.asus.com/Phone/ZenFone_Selfie_ZD551KL/HelpDesk_BIOS/

TroyBar said:
Have you flash back to original Asus image & slowly up the firmware versions?
Asus firmware updates hardware issues...after that you can them using custom roms to your pleasing.
Good place to start.
https://www.asus.com/Phone/ZenFone_Selfie_ZD551KL/HelpDesk_BIOS/
Click to expand...
Click to collapse
Which version should I install? I've tried it before and it didn't work.
Also should I install it via TWRP or via Stock Recovery?
Thanks very much!

Install latest TWRP
https://dl.twrp.me/Z00T/
A good start is follow the link of the back2stock.zip you posted, follow the instructions, zip it back up to back2stock.zip with the files mention & then flash it in TWRP.
https://asus.kremowka.xyz/categories/show/2
Zenfone 2 Selfie — ZD551KL
This will rule out any issues you have, as you will have the latest firmware from Asus.

TroyBar said:
Install latest TWRP
https://dl.twrp.me/Z00T/
A good start is follow the link of the back2stock.zip you posted, follow the instructions, zip it back up to back2stock.zip with the files mention & then flash it in TWRP.
Once done, check if your bootloader is still unlock if so you need to find out how to lock it to install Asus official firmware.
Continue the next firmware version above Version WW-21.40.1220.2056 2017/03/16 (from the posted link) located at above Asus website.
This will rule out any issues you have as you have the latest firmware from Asus.
Click to expand...
Click to collapse
The ROM you mentioned does not exist in the link you shared, maybe it's a regional effected page.
Screen of the webpage:
https://i.imgur.com/3WaSs5G.png
However, I downloaded the latest available ROM [Version WW_21.40.0.2214] from November 2017,,
I applied the back2stock steps and flashed via TWRP successfully.
After that I checked my bootloader via fastboot and it was still unlocked.
I could not re-lock it using any of the following commands:
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Always gives me a "FAILED" message.
Also found this thread about "relocking" the bootloader:
https://forum.xda-developers.com/ze...guide-ze500kl-bootloader-unlock-lock-t3655340
I flashed "relock_bootloader.zip" via TWRP and it didn't lock bootloader.
Then I thought maybe it will would work if I flashed RAW rom via Asus Flasher [from same thread].. So I googled for a ZE551KL RAW firmware and found it here:
https://drive.google.com/file/d/0B43Ue6xY9MmdRVdDRWtSSVNUdDg/view
Tried flashing it via the Asus Flash Tool and got an error "Phone is protected". See screenshot:
What do you suggest we should try next?
The phone is still having the same bootloop.

So after a little digging, it appears that my Bootloader is *NOT* unlocked.
But how come it gives an *unlocked* result for the command "fastboot oem device-info" ???
Is it possible to have a "locked" Bootloader in reality and showing otherwise in fastboot checking command??
To add, I can't install TWRP from fastboot using:
fastboot flash recovery twrp.img
I can boot the img, then install it as recovery from within TWRP.
Is this also "locked" bootloader behavior?
So many questions.

Sorry was tired last night, not the below version as it is for ZE551KL
Version WW-21.40.1220.2056 2017/03/16
You need the one(s) for Zenfone 2 Selfie — ZD551KL
Procedures:
1st
Phone (old firmware) > unlock bootloader > install TWRP > install custom rom > issues/unstable/more issues.
2nd
Phone (latest firmware) > unlock bootloader > install TWRP > install custom rom >
If 1st step was performed you need to go back & lock up the bootloader in order to update the firmware to the latest.
Asus firmware updates security/unstable & another issues...after that, you can them use custom roms to your pleasing.

TroyBar said:
Sorry was tired last night, not the below version as it is for ZE551KL
Version WW-21.40.1220.2056 2017/03/16
You need the one(s) for Zenfone 2 Selfie — ZD551KL
Procedures:
1st
Phone (old firmware) > unlock bootloader > install TWRP > install custom rom > issues/unstable/more issues.
2nd
Phone (latest firmware) > unlock bootloader > install TWRP > install custom rom >
If 1st step was performed you need to go back & lock up the bootloader in order to update the firmware to the latest.
Asus firmware updates security/unstable & another issues...after that you can them using custom roms to your pleasing.
Click to expand...
Click to collapse
So, I should install latest ZD551KL stock firmware on my ZE551KL ? Is that correct?
Could you please message me on Telegram? I have the same username.

shmaiz3r said:
So, I should install latest ZD551KL stock firmware on my ZE551KL ? Is that correct?
Could you please message me on Telegram? I have the same username.
Click to expand...
Click to collapse
Sorry is your phone ZD551KL (ZOOT) or ZE551KL, choose the one that is yours, mine is ZD551KL (ZOOT).

I have tried the above back2stock method, placed the files inside & also outside the meta-inf folder, re-zipped it up to back2stock.zip (2 separated folder zips (one for inside & other outside)) & flashed it (inside zip errors out, will outside zip works with update system, but is stuck there.
Another possibility below for an unlock bootloader, but requires you to have the stock OS installed, this has not work for me with a custom rom. I will need to find my ZD551KL (ZOOT) stock OS to try.
https://www.asus.com/support/FAQ/1009748?SearchKey=ota/

TroyBar said:
I have tried the above back2stock method, placed the files inside & also outside the meta-inf folder, re-zipped it up to back2stock.zip (2 separated folder zips (one for inside & other outside)) & flashed it (inside zip errors out, will outside zip works with update system, but is stuck there.
Another possibility below for an unlock bootloader, but requires you to have the stock OS installed, this has not work for me with a custom rom. I will need to find my ZD551KL (ZOOT) stock OS to try.
https://www.asus.com/support/FAQ/1009748?SearchKey=ota/
Click to expand...
Click to collapse
I tried flashing back2stock with both the New stock ROM and the Old stock ROM. No dice.
Thanks for your time.