Asus ZenFone 2 Laser 551KL Z00TD soft-bricked in bootloop - Zenfone 2 Laser Q&A, Help & Troubleshooting

Hi XDA Community,
I'm in a bit of a pickle. Yesterday my Zenfone started to bootloop and I tried to reset to fabric settings in bootmode but it didn't do anything. Afterwards I put the stockrom (Lollipop) and the latest rom (Marshmallow) and installed them. No errors, but it is stuck in bootloop and I can only enter fastboot mode now and it gets stuck there.
Tried Intel SoC solution, no results and also QFil but it isn't shown under ports.
How can I unbrick it?
Thank you very much.

The way I did it
If you install the latest version of twrp it should automatically boot correctly as if nothing happened. it's strange, but every brick I have had has been fixed that way.

utahja1 said:
If you install the latest version of twrp it should automatically boot correctly as if nothing happened. it's strange, but every brick I have had has been fixed that way.
Click to expand...
Click to collapse
Tried it.
This is the error that it gives me.
g:\adb and recovery>fastboot boot twrp-3.1.1-0-Z00T.img
downloading 'boot.img'...
OKAY [ 0.944s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.953s

So, I finally managed to install the latest version of TWRP and SuperSU (don't know which version, tried two of them and thee TWRP install and finally one of the stuck).
I tried back2stock with 1.14 and 1.17 firmware, but the same problem happened. Bootloop and bootloop, on and on and on. The curious thing is that I didn't encounter any error message during installations so what could be the problem. Is there a log I can see to disover what could be the solution.
Thank you.
adriantamas said:
Tried it.
This is the error that it gives me.
g:\adb and recovery>fastboot boot twrp-3.1.1-0-Z00T.img
downloading 'boot.img'...
OKAY [ 0.944s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.953s
Click to expand...
Click to collapse

Related

Help for bricked Device[Solved]

Hi,
i was running on MIUI 7 on Lenovo A6000 by Sourav_8434 and it was working fine.For my mistake i have updated weekly update i thought it will be normal.But after that my phone is showing a black screen.I can get in to fastboot and i have flashed twrp using 'fastboot flash recovery recovery.img' and when i tried to boot in to twrp(using fastboot flash recovery recovery.img) its giving me an error.
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.756s
I have send a personal message to Sourav_8434 and he replied me with some suggestions.He told me he also got the same problem and fix this issue by flashing twrp and pressing 3 buttons same at a time(vol+,Vol-,Power button).But i have tried this several times but its not working for me.If anyone got this situation before please help me. I dont want to go to service center for this problem.
Thanks
bijilidk said:
Hi,
i was running on MIUI 7 on Lenovo A6000 by Sourav_8434 and it was working fine.For my mistake i have updated weekly update i thought it will be normal.But after that my phone is showing a black screen.I can get in to fastboot and i have flashed twrp using 'fastboot flash recovery recovery.img' and when i tried to boot in to twrp(using fastboot flash recovery recovery.img) its giving me an error.
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.756s
I have send a personal message to Sourav_8434 and he replied me with some suggestions.He told me he also got the same problem and fix this issue by flashing twrp and pressing 3 buttons same at a time(vol+,Vol-,Power button).But i have tried this several times but its not working for me.If anyone got this situation before please help me. I dont want to go to service center for this problem.
Thanks
Click to expand...
Click to collapse
This happens when you flash wrong version. You must be using the twrp for KK, while MIUI is LP.
So try this one
https://userscloud.com/a25aszfwkn2z
Tried but not working same error is showing.
[email protected]:~/Desktop/TWRP/img$ sudo fastboot flash recovery twrp.img
[sudo] password for user:
Sorry, try again.
[sudo] password for user:
target reported max download size of 268435456 bytes
sending 'recovery' (13204 KB)...
OKAY [ 0.416s]
writing 'recovery'...
OKAY [ 2.022s]
finished. total time: 2.438s
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.417s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.449s
Once i did this before 'fastboot erase recovery.img' is that a problem?
bijilidk said:
Tried but not working same error is showing.
Once I did this before 'fastboot erase recovery.img' is that a problem?
Click to expand...
Click to collapse
Give these a try too
Twtp 3.0.2 http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=55585
Twrp 2.8.6 https://userscloud.com/m4jy6u5chkkp
Cwm http://www15.zippyshare.com/v/j9lHGdJf/file.html
sasukay said:
Give these a try too
Twtp 3.0.2 http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=55585
Twrp 2.8.6 https://userscloud.com/m4jy6u5chkkp
Cwm http://www15.zippyshare.com/v/j9lHGdJf/file.html
Click to expand...
Click to collapse
No hope tried everything..same error.
bijilidk said:
No hope tried everything..same error.
Click to expand...
Click to collapse
Extract "boot.img" from the root of MIUI rom zip and flash that with "fastboot flash boot boot.img"
Then flash the twrp for lollipop
Otherwise, you'll need to flash the firmware through QFIL Downloader
bijilidk said:
Tried but not working same error is showing.
[email protected]:~/Desktop/TWRP/img$ sudo fastboot flash recovery twrp.img
[sudo] password for user:
Sorry, try again.
[sudo] password for user:
target reported max download size of 268435456 bytes
sending 'recovery' (13204 KB)...
OKAY [ 0.416s]
writing 'recovery'...
OKAY [ 2.022s]
finished. total time: 2.438s
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.417s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.449s
Once i did this before 'fastboot erase recovery.img' is that a problem?
Click to expand...
Click to collapse
It seems you successfully flashed the twrp recovery...............
If your recovery is right i.e.according to your previous os
Then just u need to enter into recovery by pressing 3 buttons at the same time....
if not worked then flash another twrp version....
-Sourav_8434
Thanks for the support @sasukay @Sourav_8434 Revert back to Stock lolipop via Lenovo firmware software.
bijilidk said:
Thanks for the support @sasukay @Sourav_8434 Revert back to Stock lolipop via Lenovo firmware software.
Click to expand...
Click to collapse
Please explain how you did it. I'm also stuck with blank screen and only vibration
neerut said:
Please explain how you did it. I'm also stuck with blank screen and only vibration
Click to expand...
Click to collapse
Refer this link. I used the ( THIRD METHOD )Installing the firmware using Lenovo Downloaders.
https://boycracked.com/2015/06/03/unbrick-lenovo-a6000/
So everything is solved here right ? you can close this thread now i think !

my divece is being hard brick. what do i do now?

Hi,
i was running on MIUI 7 on Lenovo A6000 by Sourav_8434 and it was working fine.For my mistake i have updated weekly update i thought it will be normal.But after that my phone is showing a black screen.I can get in to fastboot and i have flashed twrp using 'fastboot flash recovery recovery.img' and when i tried to boot in to twrp(using fastboot flash recovery recovery.img) its giving me an error.
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.756s
I have send a personal message to Sourav_8434 and he replied me with some suggestions.He told me he also got the same problem and fix this issue by flashing twrp and pressing 3 buttons same at a time(vol+,Vol-,Power button).But i have tried this several times but its not working for me.If anyone got this situation before please help me. I dont want to go to service center for this problem.
throw it out of the window.You're welcome. Sorry.coudn't help it.You should provide a bit more details
sonhg said:
thanks!
Click to expand...
Click to collapse
Follow this tutorial and first try the third method. If that doesn't work then try the second one :silly:
thanks
MASK10101012 said:
throw it out of the window.You're welcome. Sorry.coudn't help it.You should provide a bit more details
Click to expand...
Click to collapse
Hi,
i was running on MIUI 7 on Lenovo A6000 by Sourav_8434 and it was working fine.For my mistake i have updated weekly update i thought it will be normal.But after that my phone is showing a black screen.I can get in to fastboot and i have flashed twrp using 'fastboot flash recovery recovery.img' and when i tried to boot in to twrp(using fastboot flash recovery recovery.img) its giving me an error.
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.756s
I have send a personal message to Sourav_8434 and he replied me with some suggestions.He told me he also got the same problem and fix this issue by flashing twrp and pressing 3 buttons same at a time(vol+,Vol-,Power button).But i have tried this several times but its not working for me.If anyone got this situation before please help me. I dont want to go to service center for this problem.
sonhg said:
Hi,
i was running on MIUI 7 on Lenovo A6000 by Sourav_8434 and it was working fine.For my mistake i have updated weekly update i thought it will be normal.But after that my phone is showing a black screen.I can get in to fastboot and i have flashed twrp using 'fastboot flash recovery recovery.img' and when i tried to boot in to twrp(using fastboot flash recovery recovery.img) its giving me an error.
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.756s
I have send a personal message to Sourav_8434 and he replied me with some suggestions.He told me he also got the same problem and fix this issue by flashing twrp and pressing 3 buttons same at a time(vol+,Vol-,Power button).But i have tried this several times but its not working for me.If anyone got this situation before please help me. I dont want to go to service center for this problem.
Click to expand...
Click to collapse
My friend,this is no hard brick.sometimes this error happens because because your recovery.img file is corrupted.Check that your recovery.img is found in the cmd folder...And use command 'fastboot boot recovery.img' << this one surely will work.Otherwise,please follow my own thread where I faced an identical problem..>>http://forum.xda-developers.com/lenovo-a6000/help/problem-flashing-rom-soft-brick-t3353665 Oh,and calm down, not that serious of a problem,you wont have to go to the dreaded service center.
sonhg said:
Hi,
i was running on MIUI 7 on Lenovo A6000 by Sourav_8434 and it was working fine.For my mistake i have updated weekly update i thought it will be normal.But after that my phone is showing a black screen.I can get in to fastboot and i have flashed twrp using 'fastboot flash recovery recovery.img' and when i tried to boot in to twrp(using fastboot flash recovery recovery.img) its giving me an error.
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.756s
I have send a personal message to Sourav_8434 and he replied me with some suggestions.He told me he also got the same problem and fix this issue by flashing twrp and pressing 3 buttons same at a time(vol+,Vol-,Power button).But i have tried this several times but its not working for me.If anyone got this situation before please help me. I dont want to go to service center for this problem.
Click to expand...
Click to collapse
When you can't even enter to bootloader (or fastboot), that situation is called hard brick. The problem you are facing is due to the wrong recovery version. Try this latest twrp 3.0.2 by sevenmax.
And yah, if "fastboot flash recovery recovery.img" doesn't work, then try "fastboot boot recovery.img"
sasukay said:
Follow this tutorial and first try the third method. If that doesn't work then try the second one :silly:
Click to expand...
Click to collapse
This method alsi not gud. Try this method.
https://boycracked.com/2016/02/12/e...rmware-any-android-devices-via-fastboot-mode/
I did it & saved from hardbrick. Just do whatever files u have. But dont forget ti erase boot. Erase boot then flash boot* this is main step. Then flash twrp and instll any backup or new rom.
Follow these instruction.... main files are in stock firmware file. Recovery alone flash ur own custom recovery of ur choice
rule breaker sarath said:
This method alsi not gud. Try this method.
https://boycracked.com/2016/02/12/e...rmware-any-android-devices-via-fastboot-mode/
I did it & saved from hardbrick. Just do whatever files u have. But dont forget ti erase boot. Erase boot then flash boot* this is main step. Then flash twrp and instll any backup or new rom.
Click to expand...
Click to collapse
Bhai, This method is for soft- bricked device, when you can enter bootloader.
In case of hard brick you can' t even enter in bootloader, and can't run these commands. The link I posted is for hard bricked devices.
And, you don't actually need to go through these complicated steps in case of soft brick.
Just flash any recovery through bootloader and then flash any ROM. You don't need to extract and flash each file separately.

Downgraded from latest N beta to MM by OTA, now stuck...

Hello guys.
Today I wanted to go back to MM, since I had some apps that didn't work on N.
I did this my unsigning my 6P from the Beta program, and then got the OTA to return to MM.
When I rebooted, I got the well-known 'Error' screen with a droid laying on it's back.
I tried fastboot flashing the 6.0.1 mtc19v factory image, but it gave me this result:
Code:
error: cannot load 'bootloader-angler-angler-03.51.img'
rebooting into bootloader...
OKAY [ 0.013s]
finished. total time: 0.013s
error: cannot load 'radio-angler-angler-03.61.img'
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.014s
W/ (64495): Unable to open 'image-angler-mtc19v.zip': No such file or directory
error: failed to open zip file 'image-angler-mtc19v.zip': I/O Error
I also tried flashing TWRP trough fastboot, but for some reason, it hangs at the TWRP start-up screen.
Can someone tell me what's the best way to workaround this problem? I'm quite skilled at fastboot, adb, recovery and flashing all together, so I just need to know what I overlooked.
UPDATE: Flashing TWRP was possible after flashing a modified boot.img. But now I constantly get a ERROR: 7 when trying to flash or sideload the factory image...
UPDATE2: Seems it's only a STOCK problem. Dirty Unicorns v10.3 flashed normally.
markvann said:
Hello guys.
Today I wanted to go back to MM, since I had some apps that didn't work on N.
I did this my unsigning my 6P from the Beta program, and then got the OTA to return to MM.
When I rebooted, I got the well-known 'Error' screen with a droid laying on it's back.
I tried fastboot flashing the 6.0.1 mtc19v factory image, but it gave me this result:
Code:
error: cannot load 'bootloader-angler-angler-03.51.img'
rebooting into bootloader...
OKAY [ 0.013s]
finished. total time: 0.013s
error: cannot load 'radio-angler-angler-03.61.img'
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.014s
W/ (64495): Unable to open 'image-angler-mtc19v.zip': No such file or directory
error: failed to open zip file 'image-angler-mtc19v.zip': I/O Error
I also tried flashing TWRP trough fastboot, but for some reason, it hangs at the TWRP start-up screen.
Can someone tell me what's the best way to workaround this problem? I'm quite skilled at fastboot, adb, recovery and flashing all together, so I just need to know what I overlooked.
UPDATE: Flashing TWRP was possible after flashing a modified boot.img. But now I constantly get a ERROR: 7 when trying to flash or sideload the factory image...
UPDATE2: Seems it's only a STOCK problem. Dirty Unicorns v10.3 flashed normally.
Click to expand...
Click to collapse
UPDATE3: After this, Stock MM could get installed normally. Problem solved.
markvann said:
UPDATE3: After this, Stock MM could get installed normally. Problem solved.
Click to expand...
Click to collapse
Which modified boot image did you flash? And where did you get the modified boot image from? Im working on another issue and think this might help me.
Sent from my Nexus 6 using XDA-Developers mobile app

Bricked OnePlus 6T

Don't want to talk that much, because I've not much time.
I booted the twrp recovery from bluespark on my 6T, accidentally wiped everything and now I'm bricked. How can I recover? I can no longer boot the recovery because I get an error "downloading 'boot.img'...
OKAY [ 0.819s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.834s"
Gretting yNEX
Maybe installing twrp from adb again, download Oxygen OS full rom, transfer it to your phone and flash it?
yNEXplays said:
Don't want to talk that much, because I've not much time.
I booted the twrp recovery from bluespark on my 6T, accidentally wiped everything and now I'm bricked. How can I recover? I can no longer boot the recovery because I get an error "downloading 'boot.img'...
OKAY [ 0.819s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.834s"
Gretting yNEX
Click to expand...
Click to collapse
Hi,
had the same problem. This helps me.
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
enzzo28 said:
Maybe installing twrp from adb again, download Oxygen OS full rom, transfer it to your phone and flash it?
Click to expand...
Click to collapse
Well, I'm not planning to install (flash) TWRP. I just want to boot TWRP. But that's where the problems begin...
Camel00000 said:
Hi,
had the same problem. This helps me.
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
Thanks for your reply. I'm wondering why I haven't seen this Post. I'm currently downloading the files and will test it. If it works... damn! I will have to thank you somehow!!
No problem, glad that i can help.
Camel00000 said:
No problem, glad that i can help.
Click to expand...
Click to collapse
Dude! You're mah boyy!
All I can say is: Welcome back among the living, OnePlus 6T! <3
yNEXplays said:
Dude! You're mah boyy!
All I can say is: Welcome back among the living, OnePlus 6T! <3
Click to expand...
Click to collapse
Bricking phone with an unlocked BL is kind of hard.
Even if you wipe the device, you should be able to recover by writing the correct files.
The only way I know of killing a phone like this, is if you can't get into the bootloader to do fastboot.

[RESOVLED] OS doesn't boot and TWRP is stuck on a black screen

Hi all, I have a Sony Xperia X Compact which still worked perfectly fine.
Today I tried to install Lineage OS but had trouble making it work properly - see the thread.
I managed once to successfully install TWRP but then it got removed during the formatting. I tried many times to reinstall it but it didn't work:
$fastboot flash recovery twrp-3.7.img Sending 'recovery' (27424 KB)
OKAY [ 0.863s] Writing 'recovery'
OKAY [ 0.340s] Finished. Total time: 1.214s
$ fastboot getvar recovery
recovery:
Finished. Total time: 0.002s
Click to expand...
Click to collapse
Strange... So instead, I boot to recovery through the fastboot. It always worked, I've done it 10+ times today
fastboot boot twrp-3.7.img
Click to expand...
Click to collapse
But after my last install of Lineage OS, I can't boot anymore to TWRP and get stuck on a black screen. I tried other versions of TWRP and it's the same result.
Now I have
- a buggy Lineage OS which crashes while accepting the Google terms, which means I cannot activate the debugger mode and cannot use adb
- a buggy TWRP which doesn't load
-----
Solution: install the Sony flash tool and flash the original firmware.

Categories

Resources