Develop Bugs

Can't flash RUU after deleting system

I installed TWRP (an older version, as my AT&T M9 is on 5.1 and doesn't support TWRP 3) and I accidentally wiped my system without a backup. Now there's no operating system, and every time I try to flash an RUU TWRP just instantly reboots without flashing anything. AOSP roms don't work as the firmware is out of date. Any idea what I should try next?

Some questions:
- Would you outline the steps you take (boot to download mode?, attempt RUU install?)
- What RUU are you attempting to flash (are you using this one)?
- What version of TWRP are you using?
-- Can you still boot into TWRP?
My initial suggestion is that you flash CM 12.1, which is compatible with the Lollipop firmware of the M9. But ideally you could flash an RUU, update to the latest firmware and then go from there.

computerslayer said:
Some questions:
- Would you outline the steps you take (boot to download mode?, attempt RUU install?)
- What RUU are you attempting to flash (are you using this one)?
- What version of TWRP are you using?
-- Can you still boot into TWRP?
My initial suggestion is that you flash CM 12.1, which is compatible with the Lollipop firmware of the M9. But ideally you could flash an RUU, update to the latest firmware and then go from there.
Click to expand...
Click to collapse
CM 12.1 worked! Thanks a ton

eriklee95 said:
CM 12.1 worked! Thanks a ton
Click to expand...
Click to collapse
Thanks go to the builder of the ROM , adlx.xda, who took the source of CM 12.1 and built it again after the project moved on to CM 13. We're pretty lucky to have dedicated developers here at XDA!

[6045][Bootloader] MM Hybrid Bootstack

Background
As we all know, MM update removed the fastboot commands from the bootloader. The only way to get them back was to flash a zip by @famewolf if you were already on a custom 6.0.1 ROM.
What is this Hybrid Bootstack?
It's a zip containing the following
aboot - LP
boot.img - MM (Stock boot.img modified to work with 5.0.2 bootloader)
hyp - MM
rpm- MM
sbl1- MM
splash.img - LP (Required for bootlogo to show properly
twrp-3.0.0-1
tz- MM
Why use Hybrid Bootstack?
You will keep fastboot commands while taking advantage of the new MM firmware and O.S.
Download
6045I Hybrid Bootstack
Prerequisites
TWRP (Means you must be on 5.0.2 or a custom 6.0.1 ROM)
Installation
If you are on 5.0.2:
1.) Install TWRP
2.) Install your custom 6.0.1 ROM of choice
3.) Install the hybrid bootstack
4.) Install root if you wish (NOTE: you will need to reflash SuperSU if you were rooted before this zip)
If you are on 6.0.1 (Custom ROM not stock)
1.) Reboot to TWRP
2.) Install the hybrid bootstack
3.) Install root if you wish (NOTE: you will need to reflash SuperSU if you were rooted before this zip)

Reserved

Unjustified Dev said:
Background
As we all know, MM update removed the fastboot commands from the bootloader. The only way to get them back was to flash a zip by @famewolf if you were already on a custom 6.0.1 ROM.
What is this Hybrid Bootstack?
It's a zip containing the following
aboot - LP
boot.img - MM (Stock boot.img modified to work with 5.0.2 bootloader)
hyp - MM
rpm- MM
sbl1- MM
splash.img - LP (Required for bootlogo to show properly
twrp-3.0.0-1
tz- MM
Why use Hybrid Bootstack?
You will keep fastboot commands while taking advantage of the new MM firmware and O.S.
Download
6045I Hybrid Bootstack
Prerequisites
TWRP (Means you must be on 5.0.2 or a custom 6.0.1 ROM)
Installation
If you are on 5.0.2:
1.) Install TWRP
2.) Install your custom 6.0.1 ROM of choice
3.) Install the hybrid bootstack
4.) Install root if you wish (NOTE: you will need to reflash SuperSU if you were rooted before this zip)
If you are on 6.0.1 (Custom ROM not stock)
1.) Reboot to TWRP
2.) Install the hybrid bootstack
3.) Install root if you wish (NOTE: you will need to reflash SuperSU if you were rooted before this zip)
Click to expand...
Click to collapse
Good Job as always Best :good::good:

Nice work ! Is 6045Y differ to 6045I boot.img ?

any bugs/reboots so far with this bootstack?
Anyway great work as always.

DallasCZ said:
any bugs/reboots so far with this bootstack?
Anyway great work as always.
Click to expand...
Click to collapse
None so far besides rebooting from TWRP that's always been a problem though.
murigny64 said:
Nice work ! Is 6045Y differ to 6045I boot.img ?
Click to expand...
Click to collapse
Unless there's a 6045Y MM based ROM it should work just fine. It's for 6045I based ROMs with the June 1st security patch.
Sent from my 6045I using Tapatalk

Unjustified Dev said:
None so far besides rebooting from TWRP that's always been a problem though.
Unless there's a 6045Y MM based ROM it should work just fine. It's for 6045I based ROMs with the June 1st security patch.
Sent from my 6045I using Tapatalk
Click to expand...
Click to collapse
What rebooting problem from TWRP?
So if I understand it corectly it is only for 6045I and will not work on 6045Y because it uses modified boot.img (kernel) for 6045I. If Yes, please mention it in OP, because upon the thread name it looks like it is suitable for any 6045 variant.

DallasCZ said:
What rebooting problem from TWRP?
So if I understand it corectly it is only for 6045I and will not work on 6045Y because it uses modified boot.img (kernel) for 6045I. If Yes, please mention it in OP, because upon the thread name it looks like it is suitable for any 6045 variant.
Click to expand...
Click to collapse
Sometimes it panics on reboot it's a kernel issue with the latest TWRP I made. For 6045Y to boot M you needed the new bootloader so I assume the same 6045I bootloader from 5.0.2 will work as well. The ROMs based on 6045I also use the same boot.img there's no difference in kernels. I just unpacked it so the 5.0.2 bootloader can read it.
Sent from my 6045I using Tapatalk

I ran the 6045Y bootloader on my 6045i for about 3 weeks at one point..never noticed an issue.

Any chance you have the Stock idol 3 5.5 6045O bootstack? I may have corrupted my hyp.

Hello and thanks for this, will this work on the idol 3 6045o ? On Android 5.0.2 ?
Sent from my 6045O using Tapatalk
---------- Post added at 05:49 AM ---------- Previous post was at 05:49 AM ----------
Am going to flash the modified mm zip then this .
Sent from my 6045O using Tapatalk
---------- Post added at 05:56 AM ---------- Previous post was at 05:49 AM ----------
An with this will I be on official 6.1 with fastboot an bootloader unlocked and twrp ?
Sent from my 6045O using Tapatalk

This did not work on my 60450 . After first install over cyanogenmod 13 (android 6 custom rom) , was getting kernel panics. Installed another 6.0 ROM and it fixed the panic but I never got fastboot capability back. After discovering it did not work, I flashed back to twrp-3-2-1 which essentially bricked my device because I cannot access twrp/recovery or fastboot. My device is working and boots into android 6, but does not have root access. I'm severely in need of some sort of rooting method within the android 6 environment. If I can find that hopefully I can get TWRP back. Any suggestions?

Peak5 said:
This did not work on my 60450 . After first install over cyanogenmod 13 (android 6 custom rom) , was getting kernel panics. Installed another 6.0 ROM and it fixed the panic but I never got fastboot capability back. After discovering it did not work, I flashed back to twrp-3-2-1 which essentially bricked my device because I cannot access twrp/recovery or fastboot. My device is working and boots into android 6, but does not have root access. I'm severely in need of some sort of rooting method within the android 6 environment. If I can find that hopefully I can get TWRP back. Any suggestions?
Click to expand...
Click to collapse
Alcatel Flasher can flash an older-version, 5.x-compatible TWRP (3.0.0 in original post, or 3.1.0) back to the recovery partition.
To boot newer roms incompatible with 5.x aboot, use lk2nd to chain-flash boot.img extracted from that custom rom (TWRP 3.2.1 also works that way).

Cant get ROM to boot.

I tried upgrading to 7.1, and have tried 3 different ROM's. I even tried going back to 6. Every single ROM told me error code 7 when I tried to flash it. I went about fixing that. So then I was able to flash the ROM and GApps. But then when it goes to boot into the OS all it does is hang on the white Asus screen, reboot, and go back to the white Asus screen. It does that 3 times then goes into recovery. I even tried fixing it with ZE551ML_Modder V3.3. I am running TWRP-3.0.2-0-Z00A.img. This is a Z00A as well. Any help would be greatly appreciated. Thank you.

jaed.43725 said:
I tried upgrading to 7.1, and have tried 3 different ROM's. I even tried going back to 6. Every single ROM told me error code 7 when I tried to flash it. I went about fixing that. So then I was able to flash the ROM and GApps. But then when it goes to boot into the OS all it does is hang on the white Asus screen, reboot, and go back to the white Asus screen. It does that 3 times then goes into recovery. I even tried fixing it with ZE551ML_Modder V3.3. I am running TWRP-3.0.2-0-Z00A.img. This is a Z00A as well. Any help would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
Did you upgraded the bootloader? I would just retrace steps, if not factory reset and try again.

lordpipa said:
Did you upgraded the bootloader? I would just retrace steps, if not factory reset and try again.
Click to expand...
Click to collapse
The bootloader is the recovery right? (At least thats what I always thought). If so then I am running the newest TWRP for it.

http://theflamingskull.com/zenfone2.html
Upgrade your bootloader following the instructions on the .zip package.
This will upgrade your bootloader and flash a compatible TWRP recovery.

lordpipa said:
http://theflamingskull.com/zenfone2.html
Upgrade your bootloader following the instructions on the .zip package.
This will upgrade your bootloader and flash a compatible TWRP recovery.
Click to expand...
Click to collapse
I did all that. Now I am stuck with CM Recovery. I tried using the tool to get TWRP back but its not working. I have to figure out how to push TWRP using ADB.

In modder, return to stock option , flash stock recovery and boot img.
Unlock bootloader in modder, just incase.
Flash twrp, root in modder ..reboot to twrp...install 7.1 and pico gapps

I finally had to go to Ubuntu, run ADB as SU and ADB Sideload an older version of Cyanogenmod. Not a single factory image would work. And not a single one of those Android 7 ROM's would work. They are all broken. I would like to see real proof of one working. That little escapade cost me a lot of time. So until someone comes out with a real CM14 version for the Z00A do not attempt to boot one.

jaed.43725 said:
I finally had to go to Ubuntu, run ADB as SU and ADB Sideload an older version of Cyanogenmod. Not a single factory image would work. And not a single one of those Android 7 ROM's would work. They are all broken. I would like to see real proof of one working. That little escapade cost me a lot of time. So until someone comes out with a real CM14 version for the Z00A do not attempt to boot one.
Click to expand...
Click to collapse
You may have really misunderstood the processes and yes they are allover the place.
i am running CM14.1 lots of people are !
What you probobaly have is LP based CM 13 on WW-4.20 blah blah.165
Then there was a CM13 with MM blobs based on WW-4.21 blah blah .135 MM
I think where you have gone wrong is not unlocking bootloader in 5 LP and upgrading bootloader and unlocking.
if you are on .165 - you could flash stock recovery for .165 -- upgrade to .184 -- unlock bootloader and upgrade to MM then unlock bootloader in MM with modder
Then use the modder to install 7.1 14.1 CM
But judging by the probs you have haD already - just leave it alone :good:

What is WW?

jaed.43725 said:
What is WW?
Click to expand...
Click to collapse
WW is world wide
CN china
JP japan
relating to stock FW from official site .
You know what you are doing re using ubuntu to adb but have the procedure all messed up.
Would you like to get to MM and 7.1 CM14.1 and have a windows PC ? ?
Post a screen shot of build number info you are presently on :good:

[Help me!] My Zenfone 2 always brick when I try to install a ROM

Hey! I have a Zenfone 2 ZE551ML (Z00A) which always brick when I try installing a new rom. The first time I tried installing RR and so, I downgraded to Lollipop so that could use Asus official tool to unlock my bootloader, then I flashed a TWRP recovery (I'll post the file here) through fastboot and booted to recovery mode. I used the TWRP recovery to then install ASUS rom for Android 6.0 (because the RR thread says I must have Android 6 previously installed) then I restarted and.... got bricked. To unbrick, I used this tutorial from here (one that teached me how to use xFSTK and fastboot to bring my phone back to life) and then unlocked the bootloader and flashed the TWRP recovery, did the update to 6.0 then when I tried to flash RR TWRP says I can't install it (I got error 7) the I reboot and got bricked again. Can someone here please help me?

onetimelord said:
Hey! I have a Zenfone 2 ZE551ML (Z00A) which always brick when I try installing a new rom. The first time I tried installing RR and so, I downgraded to Lollipop so that could use Asus official tool to unlock my bootloader, then I flashed a TWRP recovery (I'll post the file here) through fastboot and booted to recovery mode. I used the TWRP recovery to then install ASUS rom for Android 6.0 (because the RR thread says I must have Android 6 previously installed) then I restarted and.... got bricked. To unbrick, I used this tutorial from here (one that teached me how to use xFSTK and fastboot to bring my phone back to life) and then unlocked the bootloader and flashed the TWRP recovery, did the update to 6.0 then when I tried to flash RR TWRP says I can't install it (I got error 7) the I reboot and got bricked again. Can someone here please help me?
Click to expand...
Click to collapse
There's a lot going on here. You need to spend some time reading through the threads. Basically, you can't flash the official asus rom with twrp. It requires stock recovery. And you need to be sure to have the correct bootloader for the custom rom you are installing. Basically, Lollipop roms based on stock rom and Cm13 based roms need Lollipop bootloader. Marshmallow roms based on stock mm rom and LinOS 14.1 based roms need the Marshmallow bootloader. That's where your error 7 was coming from.
Again, read the first post of the Rom you want to install carefully. It should tell you what you need.
Sent from my ASUS_Z00A using Tapatalk

kenbo111 said:
There's a lot going on here. You need to spend some time reading through the threads. Basically, you can't flash the official asus rom with twrp. It requires stock recovery. And you need to be sure to have the correct bootloader for the custom rom you are installing. Basically, Lollipop roms based on stock rom and Cm13 based roms need Lollipop bootloader. Marshmallow roms based on stock mm rom and LinOS 14.1 based roms need the Marshmallow bootloader. That's where your error 7 was coming from.
Again, read the first post of the Rom you want to install carefully. It should tell you what you need.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
The RR rom tells me I need Android 6 but the Official way to unlock the bootloader doesn't work with Android 6. How am I supposed to unlock it? If it helps, here is the link to rom I'm trying to install: https://forum.xda-developers.com/zenfone2/development/rom-resurrection-remix-m-5-8-0-t3507247.

onetimelord said:
The RR rom tells me I need Android 6 but the Official way to unlock the bootloader doesn't work with Android 6. How am I supposed to unlock it? If it helps, here is the link to rom I'm trying to install: https://forum.xda-developers.com/zenfone2/development/rom-resurrection-remix-m-5-8-0-t3507247.
Click to expand...
Click to collapse
download modder tool and use that

onetimelord said:
The RR rom tells me I need Android 6 but the Official way to unlock the bootloader doesn't work with Android 6. How am I supposed to unlock it? If it helps, here is the link to rom I'm trying to install: https://forum.xda-developers.com/zenfone2/development/rom-resurrection-remix-m-5-8-0-t3507247.
Click to expand...
Click to collapse
Like I said, you need to read through the threads. Go to the resources and the index threads in the general section. And look at the first posts there. Also find the modder tool thread. It's a very useful multipurpose tool for all kinds of things.
Sent from my ASUS_Z00A using Tapatalk
---------- Post added at 04:05 AM ---------- Previous post was at 04:01 AM ----------
Also see this post on the bootloader situation. The tools in that post will help too. https://forum.xda-developers.com/showthread.php?p=68542370
Sent from my ASUS_Z00A using Tapatalk

How to find base/stock android version ?

Hi.
1. Most of custom ROMs require 10.0.13.0/10.0.18.0 as base ? How I can find out my Android version ? For me it types just Android 10
2. Is it mandatory to EDL flash a stock/base ROM before installing custom ROM ? I never flash any ROM, I have a stock build like I bought phone from store and I just unlock bootloader so my system done something like a factory reset. Do I need to EDL flash my phone or I need to EDL flash only if I have a custom ROM ?

At the bottom of Settings -> About is the build number, which is long and ends in a number like 10.0.x.0 (Android 9) or 11.0.x.0 (Android 10).
10.0.20.0 was the last Android 9 release, so I guess the custom ROMs want the Android 9 vendor partition rather than the Android 8 or 10 vendor partitions.
If you are already on stock, you shoudn't need to do any kind of special flashing. MiFlash or the flash_all script (uses fastboot) should be fine to get your device to the appropriate base version to install a custom ROM from.