Bootloop ZF3 - Asus ZenFone 3 Questions & Answers

So I was on mm with unlocked bootloader and i tried to update to nougat through the stock recovery but no luck (error status 7 or something like that) and i was like ehh screw it fastbooted twrp and flash supersu. that's when everything went side ways. bootlooped right after i clicked reboot system. it apeard a message saying that something DRM i didn't may atenction to it and something in red right before the asus image. can anyone help me out?

You skipped a step, you need to flash the no-verity file. You'll still have that DRM bootup screen but it'll be with yellow text.
https://forum.xda-developers.com/showthread.php?t=3569926

Related

[Q] What is the correct installation order of the ICS files via fastboot?

I've gone through all the steps to root, unlock, backup using cwm, but i keep on coming up with issues on bootup after updating via fastboot. any ideas? when it does properly boot up it shows the updated M screen, and the att screen, but then stalls out. also, I've seen 2 android warning screens, one with the android guy and a white triangle with a yellow exlamation point in it, and also have seen the android guy on its back with a red shaded triangle with a black exlamation point in it.
any help would be greatly appreciated.
I have 2 Atrixs, one was at 2.3.4 and the other was 2.3.6, both are experiencing the same problems
android system recovery attempt at applying update failed due to e:signature verification failed
If you're going to flash raw images via fastboot, the order shouldn't really matter. Just make sure you wipe everything before flashing.
wiping down the cache was what i did, at least thats what the cwm instructions were telling me. At that point i rebooted and entered into fastboot, flashed the files in the exact order displayed over at andriod police, rebooted, and stalled out during boot up at the att screen.
Since the files were flashed and should be there on the atrix, what would you suggest i do?

Stuck in bootloop :(

I have unlocked bootloader, flash modified boot.img and recovery but when I boot the device I get 'Your device is corrupt and may not work properly' I then get stuck on the google boot screen. When I go into TWRP recovery it cannot mount anything so I cannot even perform a factory reset.
Please help
did you make a back up?
I didn't unfortunately, I can get into recovery and as long as I leave it as 'Read-Only' it seems to mount everything. I think I need to get a stock image.
Resolved - used a Toolkit to go completely back to stock, kind of scared to try again now.
Follow directions and that won't happen again. Make sure you are on the correct version MDB08K BEFORE you start (you have the OTA), format not wipe in TWRP and you won't get caught in the boot loop.
Failing to do those two things will put you in a boot loop.
What toolkit did you use because i myself have this issue with my nexus 6p
Swatto86 said:
I have unlocked bootloader, flash modified boot.img and recovery but when I boot the device I get 'Your device is corrupt and may not work properly' I then get stuck on the google boot screen. When I go into TWRP recovery it cannot mount anything so I cannot even perform a factory reset.
Please help
Click to expand...
Click to collapse
That warning is normal, and should be ignored if you want unlocked bootloader, custom ROMs, etc.
Here TWRP couldn't mount because you forgot to decrypt after flashing the modified boot.img.
If you have further issues, let me know.
A quick advise - Avoid toolkits. They are handy and easy, but if something goes wrong, it will be hard to track down the cause. On the contrary, doing thing manually, will not only make it easy, but will also help you learn more about your Android, and how it works.

Boot loop after flashing latest Android 7 image

While on a developer preview of Android N with my unlocked rooted phone and TWRP 3.0.2-1, I accidentally ran the September OTA. The OTA failed, but left a mess behind with the phone rebooting 4-5 times a day.
Today, I decided to fix the problem, so I flashed the latest official image (NRD90U). Complete wipe, but since I have backups, I considered it to be no big deal. Turns out it was
The phone is now a boot loop (corrupt warning -> google logo -> corrupt warning -> google logo...). Reflashing changes nothing. Trying to boot (fastboot boot) TWRP (any version) does not work (it just goes into the boot loop). Tried to downgrade back to 6, same problem. Nothing seems to work.
Somehow, something is still ****ed up on the phone, but I have no idea what. This seems to be very similar to this thread (http://forum.xda-developers.com/nexus-6p/help/help-help-help-hard-bricked-6p-t3428225/page3), but there does not seem to be a solution.
Is it definitely bricked or is there anything I can do from fastboot to try and fix this? I am unlocked. I just need a stupid TWRP so I can restore my backup and hopefully get back to a working state from there.
PS: I'm sure I downloaded the right image and flashed it properly.

Device corrupted

So I was trying to install the new Oreo beta, and couldn't get into TWRP, and couldn't get it to flash it either. So I tried to reinstall the stock recovery by using flashall, but during the process I accidentally disconnected my phone. For a while I was stuck in a bootloop, but I've gotten it to the point where I actually get in. But it still says my device is corrupted and cannot be trusted and may not work properly. Does anyone know how to fix this? The phone is functional, but I worry that it will fail to boot when I'm not near a computer.
Edit: Problem solved, realized I needed to flash the full stock.
that message comes up when bootloader is unlocked
For that specific boot message (I believe it's a red screen) you have to use invisiblek's boot fix.
Look at his page https://mata.readthedocs.io/en/latest/ at the very bottom and follow the instructions.
Quick Question
Ellises said:
For that specific boot message (I believe it's a red screen) you have to use invisiblek's boot fix.
Look at his page https://mata.readthedocs.io/en/latest/ at the very bottom and follow the instructions.
Click to expand...
Click to collapse
Do I fastboot flash this boot image then the stock boot image or just over top of the stock boot image? Also the boot fix image is only ~26mb while the stock boot image is ~65mb?

Warning message at boot after flashing B03

Hi,
It's happening something strange with my phone.
After flashing LOS' Oki's EDL with B12 bootstack my phone boots well with no warning.
If I flash B03 stock, or df!nr, the first splash becomes ugly, warning message appears with penguin after.
It's not a big problem as the ROM run well, but it's strange and I'd like to understand what's happening.
I tried lot of things but I never succeeded in removing the warning message and penguin with B03 only. No problems with GSI.
With B03 bootstack by Raysteff, the splash is normal, but warning and penguin are still here.
If I use "del Inscription" in recovery 3.2.1-8, the phone boots in DFU.
I tried revert to Nougat and flashed remove_bl_warning, but same result after becoming back to B03.
I wonder if it could be because of the way I unlocked BL. I used, long time ago, turkey's img.
Relock BL and unlock another way could change things ?
I don't remember if my phone was shipped with MM or Nougat and I'm afraid of hard brick by relocking it if I flash wrong stock firmware before relock.
Thanks.

Categories

Resources