Bricked Zenfone, Out of ideas - ZenFone 2 Q&A, Help & Troubleshooting

Hello everyone, need a little help if possible .
The say curiosity killed the cat, well… it killed my phone. To be more precise I wanted to know if my 550ml (with unlocked bootloader and running cm12.1) could run a 551ml firmware so… I did install thru TWRP the superzen firmware and after that the screen turned black. Can’t see anything . Not even in fastbootmode, no logo, no nothing. If I turn it on and plug it to the pc it shows, I see the internal memory and the sdcard. It’s gotta be from the different resolution that 550 and 551 have but how do I change it since I can’t see anything?
I did a userdata reset thru fastboot, wiped cache , reinstalled stock recovery ,boot recovery, tried to install stock firmware, still no change. I even managed to enter stock recovery and did an adb sideload of the latest firmware from the asus site.
As for now the phone boots, the capacitive buttons respond, the led indicates that it charges, the pc sees it but no matter what I do the screen remains black. Most likely I’m on the setup wizard but like I said I don’t see anything.
So… What can I do now? To the Asus service with it or …?
I'm not much of a forum user so go easy on me. Thank you.

Not sure if it's going to make a difference but here is an idea, try sideloading a cm recovery and flash a cm rom and see what it does...

fastmix said:
Not sure if it's going to make a difference but here is an idea, try sideloading a cm recovery and flash a cm rom and see what it does...
Click to expand...
Click to collapse
Unfortunately it does not work, when i try to sideload a rom with twrp it gives this: error closed. Probably because usb debugging is not enabled... and in cwm different error: Device unauthorized...

Are you sure bootloader is unlocked?

It has to be unlocked cause i can flash permanent TWRP and when I enter TWRP recovery i can touch the buttons, even tried to do a restore in the dark... But nothing... Still the black screen persists... Thank you anyways.
PS: Well it looks like I've managed to resolve my problem. Thanx to user helroz i have found in his google drive a Raw firmware and I was able to flash it via fastboot with Asus Flash tool and now the phone booted, no more black screen for me. Lesson learned.

Related

[Q] Help! - Rooted Zenfone 2 (ZE551ML) bricked after OTA accidently

followed a tutorial (Cnncted's youtube clip - How to root the ASUS ZenFone 2 ) to root
Accidentally (very stupid) pressed the update option when an OTA update showed up yesterday (Jul 8 2015), and after that the phone won't start properly - stopped at in search of incredible...
No luck with trying to boot into recovery mode (power + volume up). It just vibrates once and the screen is black. Trying to flash recovery image with ADB and flashtool etc, but the MTP usb connection failed. If I connect it to the PC using the USB cable and then press the power button to turn it on (stuck in that ..."incredible" screen), device manager shows the Z200AD name with a yellow exclamation mark beside, and Asus ZenUI software will automatically start. But it's not really recognized by the PC.
So...if you have any suggestions for me to try, please let me know and that would be greatly appreciated!
Harry
p.s. This is a US version, so the it's the WW sku?
Same problem here. I have a rooted 551ML and on July 6th I received an OTA update. I installed it and I'm stuck in boot loop. I have hundreds of family pictures in the internal memory.
The good news is that I have access to boot loader and recovery.
I could not find any custom recovery for Zenfone 2. They are not out yet, right? Is there any way to copy the internal memory of the phone (that doesnt load the OS) to the SD card? Or to paste a file img.boot taken from a downloaded official rom and copy it over the corrupted one on the phone's memory?
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
joel.maxuel said:
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
Click to expand...
Click to collapse
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
I faced this problem too. All I did was to flash the boot.img of my version using fastboot,
Then I flashed the firmware, without factory reset I started the phone.
I was continiously getting an error "com.android.process has stopped". Ignoring that, I just backed up my whole data. Did a factory reset. Updated
Boom!! Everything was normal... I hope this helps
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
xxmmx said:
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
Click to expand...
Click to collapse
xxmmx said:
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
Click to expand...
Click to collapse
Isn't everyone serial number the same? mine is.
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
GGL-Daz said:
Isn't everyone serial number the same? mine is.
Click to expand...
Click to collapse
xxmmx said:
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
Click to expand...
Click to collapse
Pretty sure rooting didn't affect my fastboot screen at all.
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
dip_anker said:
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
Click to expand...
Click to collapse
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
5ifty1 said:
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
Click to expand...
Click to collapse
i tried it with prerooted as well as the stock rom, it did not work for me. isn't there any way to flash CM12.1 using the fastboot ?

TWRP BOOT LOOP has anyone found a solution (OTA update)

i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
[SOLVED]
went back to stock recovery and side loaded the full 1.4 gb rom i will leave a link for tutorial that i used, i wanted to get back to complete stock and this was the one use
"https://forums.oneplus.net/threads/guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232/"
When you have TWRP you have to install full zip, not simply the eval OTA zip
bob_cheeseman5 said:
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
Click to expand...
Click to collapse
Flash the stock recovery.
Get stock recovery from downloads.oneplus.net
I cant seem to flash the stock recovery. The device is not visible in adb devices or fastboot devices. im facing the same issue.
If you are using TWRP 3.0.4-0 - try a hard boot...hold down the power button for 20s...wait 20s, power it back on.
bob_cheeseman5 said:
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
Click to expand...
Click to collapse
easy solution. Boot into fastboot
download this tool.
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
if newest version isnt working, download an older version with older twrp
than unzip the tool and run the .bat file and install twrp.
Thats it
There are many posts on Nougat not working with official TWRP (based on 6.0 build). Try booting into stock recovery. performing a system settings reset, then booting into fastboot and run the adb command, <fastboot boot TWRP-3.0.2-1.28.img>. From there you can do virtually anything you need to do. I recommend at least using a modified version of TWRP (such as 1.28). This has been posted many times before, please try and do a search for the answers first, it will help tremendously. Thanks
recovery
i had the same problem on my rooted OP3 when i used TWRP 3.0.2-1 , it worked to flash the full 4.0.1 rom but failed for everything else, flashing latest verion of twrp fixed it for me
Got the same problem (unrooted phone + device state locked, cannot access recover, but can access fastboot) with an added "benefit", USB debugging mode was off before it all went crashing and burning.
How to access my phone via PC? (all the guides I've found assume I had USB debugging mode on before the phone got soft-bricked, but as a normal phone user who never installed anything custom, I've never figured it is A MUST BE ON function).
Or simpler question - what tool to use to turn on the USB debugging mode? (if that is at all possible?)
Aislandas said:
Got the same problem (unrooted phone + device state locked, cannot access recover, but can access fastboot) with an added "benefit", USB debugging mode was off before it all went crashing and burning.
How to access my phone via PC? (all the guides I've found assume I had USB debugging mode on before the phone got soft-bricked, but as a normal phone user who never installed anything custom, I've never figured it is A MUST BE ON function).
Or simpler question - what tool to use to turn on the USB debugging mode? (if that is at all possible?)
Click to expand...
Click to collapse
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
bob_cheeseman5 said:
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
Click to expand...
Click to collapse
Noted that you solved your issue, but this post is about the new version of TWRP. Version 3.0.3 is available on twrp.me and it works with Nougat.
bob_cheeseman5 said:
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
Click to expand...
Click to collapse
Gave up trying and booked a session with OP technicians Will see how it goes in a week.

Stuck on team win recovery project please help

I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Did you buy the phone second hand or did you try to flash TWRP yourself? It shouldn't have TWRP installed by default.
Regardless, you can use TWRP to flash the latest update.
Given that you have TWRP, I'm assuming that you have an unlocked bootloader. Did you notice a warning pop up everytime you reboot your phone before? It should say something along the lines of "your device has been unlocked and can't be trusted". If not, you'll have to unlock it (it wipes your phone in the process).
If the bootloader is unlocked, you can simply download and flash the latest zip for OOS 4.0.3 in TWRP. This will update you phone and replace TWRP with the stock recovery (so you don't run into this problem again in the future when installing an OTA). If you don't intend to modify your phone in any way, then this is all you need to do, your phone should be functional.
There are plenty of threads with detailed guides on how to do all of this.
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
sndr1384 said:
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
Click to expand...
Click to collapse
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
This is issue of using a faulty twrp so for that when ur phone us booting up go to fastboot and flash twrp 3.0.4-1 and everything will work
emuandco said:
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
Click to expand...
Click to collapse
Similar Problem here:
just wanted to flash latest OOS 4.0.3, so I flashed back stock recovery with flashify and rebooted into recovery mode to flash the already downloaded OOS 4.0.3. zip. That's when it began to go poop! After rebooting it just went dark with no Chance to power it on again! No dice with power button, Volume up/down + power button, nothing! Not even the LED's are blinking when plugged in. So this one seems to be basically dead!
I got it once booting again after randomly pushing the buttons (after x minutes!?), but everytime I reboot the phone it just shuts off without beeing able to power it on again. At the Moment it's dead!
Any ideas what might happened? If I get it on again, should I immediately reset it to factory Settings?
I am kinda lost here! Any help/ideas would be much appreciated!
Flashify? Never used it and never trusted apps which flash stuff on a running system. Use fastboot and reflash the recovery partition. Link to recovery is in my former post.
fastboot flash recovery PATHTOIMGFILE
Thank you for your advice! Still a lot to learn! Got it up again, will try as you suggested!
It appeared that my stock recovery file was corrupted , but all is fine again! Thank you very much!
Mannycolon85 said:
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Click to expand...
Click to collapse
I may have been the person you traded with to get the OnePlus 3, but I took the phone back and after 5 hours I got it up and running.
The phone would boot to TWRP, but even after wiping the entire system and dragging a ROM zip to the internal storage, reinstalling did nothing. It just kept booting back to recovery.
The solution entailed the following.
Download stock recovery IMG. Flashed through TWRP. Rebooted recovery and now was back to stock recovery.
Download the official OxygenOS ROM zip from the OnePlus website and changed the name to update.zip
Next I downloaded Android studio for access to ADB. I had never used ADB before, but I knew this was needed to push a file to the phone.
Needless to say, ADB kept freezing my computer when I would type in the commands to side load.
I deleted Android studio and installed a minimal ADB/Fastboot I found online. I opened my command prompt, typed the command for sideloading, and immediately got my installation starting. It took about 10 minutes to fully install. When it was finished, I rebooted and had a fully functioning OnePlus 3
Sent from my ONEPLUS A3000 using Tapatalk

I accidentaly deleted my system on my oneplus 5t

I still can get into recovery and fastboot, but when I boot into the system the screen is just black and the led glows white.
I tried sideloading a rom with adb and also installing a rom with twrp, but nothing worked. The unbricking tools also didnt help. Some of them suggest to power the phone off and press the volume up button 5 seconds, while still pressing it to connect the phone to the pc. The following steps dont help, because my pc doesnt recognize my phone.
I am exhausted, what can I do?
So what process did u try for the unbrick tool, BC that should have worked 100%. What errors did u get? Saying it didn't work does not help us.
How TWRP is unable to install a new rom ?? what error messages did you get there ?? which OS you are currently on when system was deleted? and which version ??.
try to provide as much details please
Simply flash the latest oos version.
Nd u done.
Data remain save n safe.
Nothing to Worry.

Extreme Bricked Honor 7X BND-L21

I have completely bricked my phone. It does not have a functional screen or anything anymore. It is stuck in fastboot and wont leave it in any way.
How this happened:
I tried rolling back to an older version via HiSuite DNS spoof to EMUI 8 again, but it failed to boot after that. It has been stuck in fastboot since then.
I DO have the bootloader and FRP unlocked. I already did that via the test point method. Anyone got any ideas what i could do now?
I already tried flashing system, recovery, cust and ramdisk, did not help in any way. I'd appreciate some help.
I have also tried downloading Full OS from TeamMT but it seems to reset after 300MB being downloaded.
I got the screen working again but its constantly rebooting into this screen now
MrRobBoss said:
I got the screen working again but its constantly rebooting into this screen now
Click to expand...
Click to collapse
If you are able to boot into recovery, you could try service rom from here, (OTG cable or adaptor)USB formatted as ExtFAT and dload folder with required content, then 3 button combination. Double check if makes any sense.
hardcorehenry said:
If you are able to boot into recovery, you could try service rom from here, (OTG cable or adaptor)USB formatted as ExtFAT and dload folder with required content, then 3 button combination. Double check if makes any sense.
Click to expand...
Click to collapse
I tried booting into recovery but it keeps on booting into error mode. I have not tried if it fails test point aswell but currently not able to test it.

Categories

Resources