Database Users

Soft bricked Zenfone 3 still have TWRP

I have a Zenfone 3 that while trying to unroot I have soft bricked. I can get into TWRP recovery, but after installing the tizen ROM, I can not boot into it, but can still access the TWRP recovery. Is there a toolkit or any suggestion you might have as to how I could fix this issue.

Canukboy said:
I have a Zenfone 3 that while trying to unroot I have soft bricked. I can get into TWRP recovery, but after installing the tizen ROM, I can not boot into it, but can still access the TWRP recovery. Is there a toolkit or any suggestion you might have as to how I could fix this issue.
Click to expand...
Click to collapse
Do you have an official recovery? If yes, you can recover back your device again. Just use 'adb sideload <filename>' to do this.
I've also trying to unroot my device and end up in boot logo, but after flash the official ROM, it's finally work again. Also my data (/data) isn't formatted.

android_101_ said:
Do you have an official recovery? If yes, you can recover back your device again. Just use 'adb sideload <filename>' to do this.
I've also trying to unroot my device and end up in boot logo, but after flash the official ROM, it's finally work again. Also my data (/data) isn't formatted.
Click to expand...
Click to collapse
I only have the Twrp recovery.

Canukboy said:
I only have the Twrp recovery.
Click to expand...
Click to collapse
TWRP supports adb sideload but there's no point flashing stock recovery, TWRP is superior in every way.
Go into TWRP, plug in your USB cable and it'll mount your sdcard . Copy the firmware onto the sdcard and install it. Perform a wipe cache/dalvik and reboot.
How are you removing root?

wang1chung said:
TWRP supports adb sideload but there's no point flashing stock recovery, TWRP is superior in every way.
Go into TWRP, plug in your USB cable and it'll mount your sdcard . Copy the firmware onto the sdcard and install it. Perform a wipe cache/dalvik and reboot.
How are you removing root?
Click to expand...
Click to collapse
I used a app called KingRoot while I was on the bus, it caused the phone to freeze, after about 10 mins I hard reset the phone and it has not worked since.
I tried to sideload the stock rom, but it will not accept it. I think I may have something to do with the bootloader. I think my TWRP recovery could be in the Android partition, but I am unsure.

Canukboy said:
I used a app called KingRoot while I was on the bus, it caused the phone to freeze, after about 10 mins I hard reset the phone and it has not worked since.
I tried to sideload the stock rom, but it will not accept it. I think I may have something to do with the bootloader. I think my TWRP recovery could be in the Android partition, but I am unsure.
Click to expand...
Click to collapse
Forget sideloading it, edit the update script in the firmware, see this
thread, part 1, step 2-4.
Then copy the firmware to your sdcard (like I mentioned above) and install it. You can use the guide here, tip #4. You should read the entire guide afterwards.
if TWRP loads when you select recovery, it's on the correct partition. You'll have to reinstall TWRP after you flash the stock Rom again as it'll update recovery as well. Then create an nandroid backup, tip #2 and you're set.

Forget sideloading it, edit the update script in the firmware, see this
thread, part 1, step 2-4.
Then copy the firmware to your sdcard (like I mentioned above) and install it. You can use the guide here, tip #4. You should read the entire guide afterwards.
if TWRP loads when you select recovery, it's on the correct partition. You'll have to reinstall TWRP after you flash the stock Rom again as it'll update recovery as well. Then create an nandroid backup, tip #2 and you're set.
Click to expand...
Click to collapse
Hy Wang.. I followed your guide - modified updater-script, but I can't install the stock rom .zip from TWRP.
It says "can't extract updater-binary", I tried few times thinking that the file is corrupt, but the result still same.
FYI, I use stock ROM "UL-ASUS_Z012D-WW-14.2020.1709.68-user.zip", and TWRP 3.1.1.
Please help me if you have experienced it before. Thanks

@rzahunn
I've never had that error before and you're on the latest version of TWRP so I'm going to guess it has to do with your modification of the updater script.
You edited updater-script not updater-binary, correct? There are two files with similar names

There's a detailed guide by @kyle_l88 on how to return to stock.
Here's the link: https://forum.xda-developers.com/zenfone-3/development/how-to-to-stock-rom-recovery-zenfone-3-t3666223
Do note that the original recovery link is dead. The updated link is: https://mega.nz/#F!LIhwiCia!b_pyuHXS9E7f2VbyXcLyXA

TWRP Bootloop
Sorry if my reply is irrelevant, but I need some helps.
I am also using Zenfone 3, but stuck in TWRP bootloop.
I cannot flash using fastboot (not detected on PC), reflashing ROM doesn't help either.
I've tried all the possible methods I found on Google, such as dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota method but still has no luck.
Restoring backup would end me in TWRP too.

@Xytce
Are you factory resetting after you flash? Clearing cache and dalvik? It will take 5-10min to boot up initially after that.
Otherwise, try the guide Rizzed referenced.....as long as you have the correct firmware and TWRP flashes successfully, there's no reason it shouldn't work that I can think of.

wang1chung said:
@Xytce
Are you factory resetting after you flash? Clearing cache and dalvik? It will take 5-10min to boot up initially after that.
Otherwise, try the guide Rizzed referenced.....as long as you have the correct firmware and TWRP flashes successfully, there's no reason it shouldn't work that I can think of.
Click to expand...
Click to collapse
I've managed to fix the bootloop after following the guide. I missed that somehow, thanks for pointing that to me.
I've thanked you (pressed the Thanks button).

dm verity
Canukboy said:
I have a Zenfone 3 that while trying to unroot I have soft bricked. I can get into TWRP recovery, but after installing the tizen ROM, I can not boot into it, but can still access the TWRP recovery. Is there a toolkit or any suggestion you might have as to how I could fix this issue.
Click to expand...
Click to collapse
does it hangs on logo then start again? then reflashing the rom then flashing the dm verity zip again hope it works

Stuck in Boot Animation

Hi!
I have a A2107G and unlocked it, coming from B04.
Everything worked so far, but I have messed around with bootstack/modem and now I am struggling.
I flashed a new ROM with TWRP (different versions) and the ROM (doesn't matter which one) is stuck in booting animation.
What can I do to bring it back to life?
Also another question: After switching on, directly after the ZTE logo coming up, a black sceen with some infos coming up and stay there for 5 secs.
Is there a way to get rid of this

Sui77 said:
Hi!
I have a A2107G and unlocked it, coming from B04.
Everything worked so far, but I have messed around with bootstack/modem and now I am struggling.
I flashed a new ROM with TWRP (different versions) and the ROM (doesn't matter which one) is stuck in booting animation.
What can I do to bring it back to life?
Also another question: After switching on, directly after the ZTE logo coming up, a black sceen with some infos coming up and stay there for 5 secs.
Is there a way to get rid of this
Click to expand...
Click to collapse
Do you have twrp? If yes, flash stock rom.

WesTD said:
Do you have twrp? If yes, flash stock rom.
Click to expand...
Click to collapse
Yes, I have TWRP.
So i should flash a stock image and start over from scratch (with rooting, ...)
Is the posted screen normal?

Sui77 said:
Yes, I have TWRP.
So i should flash a stock image and start over from scratch (with rooting, ...)
Is the posted screen normal?
Click to expand...
Click to collapse
Yes it is normal. It means you've unlocked bootloader.
Flash stock rom zip. There are some guides.

WesTD said:
Yes it is normal. It means you've unlocked bootloader.
Flash stock rom zip. There are some guides.
Click to expand...
Click to collapse
THX.
Will do so.
Which ROM do you prefer? CarbonRom? LOS?
How do i get the system partition r/w?
I think I screwed up the phone when i tried to make it writable?

Sui77 said:
THX.
Will do so.
Which ROM do you prefer? CarbonRom? LOS?
How do i get the system partition r/w?
I think I screwed up the phone when i tried to make it writable?
Click to expand...
Click to collapse
I use aosp bases.

Sui77 said:
THX.
Will do so.
Which ROM do you prefer? CarbonRom? LOS?
How do i get the system partition r/w?
I think I screwed up the phone when i tried to make it writable?
Click to expand...
Click to collapse
Heh. I don't know if there are flashable stock zips for the A2017G, the way I know of is flashing the stock recovery and using an official zip. But you shouldn't go back to stock if you want to use custom ROMs. Try this:
-Get an SD card, put
~ a custom ROM (RR, LOS,NucleaROM (i prefer NucleaROM, just sayin)),
~a Magisk 13.3 zip or SuperSU 2.82 zip,
~an OpenGApps zip (I use pico), arm64,
~a TWRP 3.1.1-0.img and
~A2017X Universal Bootloader and A2017G modem.
-Wipe system, data, cache and dalvik
-Install the Universal Bootloader, then the Modem, then the ROM and last the GApps and magisk/SuperSU
-If you had something important on the internal storage put it on the SD with the File manager under Advanced
-Go to Wipe -> Format data -> type Yes. This will get rid of the possible encryption from the stock ROM, but it will wipe your internal storage too.
-Reboot to system
You can use the 5 seconds screen to get to TWRP with the Volume buttons. Pretty handy I guess. There's a zip out there that gets rid of that screen, but you risk black-screening your phone with what seems to be no immediate fix (you'd be looking at an RMA)
So, after you use the phone and open TWRP again, you'll have an old version of it (3.0.1N-0 or sth). So go to Install, choose Install image, and select the TWRP 3.1.1-0.img on your SDcard. Then Reboot -> reboot to recovery and you can do whatever you want.

Choose an username... said:
Heh. I don't know if there are flashable stock zips for the A2017G, the way I know of is flashing the stock recovery and using an official zip. But you shouldn't go back to stock if you want to use custom ROMs. Try this:
-Get an SD card, put
~ a custom ROM (RR, LOS,NucleaROM (i prefer NucleaROM, just sayin)),
~a Magisk 13.3 zip or SuperSU 2.82 zip,
~an OpenGApps zip (I use pico), arm64,
~a TWRP 3.1.1-0.img and
~A2017X Universal Bootloader and A2017G modem.
-Wipe system, data, cache and dalvik
-Install the Universal Bootloader, then the Modem, then the ROM and last the GApps and magisk/SuperSU
-If you had something important on the internal storage put it on the SD with the File manager under Advanced
-Go to Wipe -> Format data -> type Yes. This will get rid of the possible encryption from the stock ROM, but it will wipe your internal storage too.
-Reboot to system
You can use the 5 seconds screen to get to TWRP with the Volume buttons. Pretty handy I guess. There's a zip out there that gets rid of that screen, but you risk black-screening your phone with what seems to be no immediate fix (you'd be looking at an RMA)
So, after you use the phone and open TWRP again, you'll have an old version of it (3.0.1N-0 or sth). So go to Install, choose Install image, and select the TWRP 3.1.1-0.img on your SDcard. Then Reboot -> reboot to recovery and you can do whatever you want.
Click to expand...
Click to collapse
Hi!
Thanks for your help and the time you spent on my problem.
I have tried all that stuff already, but maybe not in exact that order. Will try it this evening.
In case i will be able to bring it back to life, I have 2 questions, pls:
1: You mentioned the 5sec-screen and a zip to get rid of it.
Where could I find it (not seen yet) and how do i get into fastboot, when I skip this screen?
2: When I setted up my Axon with a Custom Rom and SU and everything was working as it should do, I was not able to write to /system (or deleting something in system/apps)
How do I get rid of this restriction? I think I have found an instruction once, but I failed and afterwards my device was stuck in animation.
orry for bothering, but the Axon really drive me nuts. Never had such a hassle with my Nexus

Sui77 said:
Hi!
Thanks for your help and the time you spent on my problem.
I have tried all that stuff already, but maybe not in exact that order. Will try it this evening.
In case i will be able to bring it back to life, I have 2 questions, pls:
1: You mentioned the 5sec-screen and a zip to get rid of it.
Where could I find it (not seen yet) and how do i get into fastboot, when I skip this screen?
2: When I setted up my Axon with a Custom Rom and SU and everything was working as it should do, I was not able to write to /system (or deleting something in system/apps)
How do I get rid of this restriction? I think I have found an instruction once, but I failed and afterwards my device was stuck in animation.
orry for bothering, but the Axon really drive me nuts. Never had such a hassle with my Nexus
Click to expand...
Click to collapse
Which file manager you are using?
I'm using Root Explorer and no problem. Be sure you allow to root permission

WesTD said:
Which file manager you are using?
I'm using Root Explorer and no problem. Be sure you allow to root permission
Click to expand...
Click to collapse
Also Root Explorer, root granted.

Sui77 said:
Also Root Explorer, root granted.
Click to expand...
Click to collapse
Can you just leave the 5 sec screen alone? You can kill your phone, and there doesn't seem to be anything you can do really.
If you're insistent, you can find it under Themes Apps and Mods, called "We remove the inscription that the bootloader is unlocked" made by NFound1.
And about the restriction to modify the system, connect your phone to a PC with ADB, fire up ADB and configure it (USB debugging, ADB over network if you have the option, permit the connection) and issue 'adb reboot disemmcwp' (disable emmc write protection, that is. Write it just like that or your phone will reboot and you will still have the protection active).
The phone has its difficulties and all but it's easy to work with once you get the hang of it. And, you know, your big cores don't just die all of a sudden, which is a good thing!

Choose an username... said:
Heh. I don't know if there are flashable stock zips for the A2017G, the way I know of is flashing the stock recovery and using an official zip. But you shouldn't go back to stock if you want to use custom ROMs. Try this:
-Get an SD card, put
~ a custom ROM (RR, LOS,NucleaROM (i prefer NucleaROM, just sayin)),
~a Magisk 13.3 zip or SuperSU 2.82 zip,
~an OpenGApps zip (I use pico), arm64,
~a TWRP 3.1.1-0.img and
~A2017X Universal Bootloader and A2017G modem.
-Wipe system, data, cache and dalvik
-Install the Universal Bootloader, then the Modem, then the ROM and last the GApps and magisk/SuperSU
-If you had something important on the internal storage put it on the SD with the File manager under Advanced
-Go to Wipe -> Format data -> type Yes. This will get rid of the possible encryption from the stock ROM, but it will wipe your internal storage too.
-Reboot to system
You can use the 5 seconds screen to get to TWRP with the Volume buttons. Pretty handy I guess. There's a zip out there that gets rid of that screen, but you risk black-screening your phone with what seems to be no immediate fix (you'd be looking at an RMA)
So, after you use the phone and open TWRP again, you'll have an old version of it (3.0.1N-0 or sth). So go to Install, choose Install image, and select the TWRP 3.1.1-0.img on your SDcard. Then Reboot -> reboot to recovery and you can do whatever you want.
Click to expand...
Click to collapse
Tried exactly the steps you descriped, but no luck ---- still stuck in animation
Will try it tomorrow with Magist.
How can I go back to total stock.
Tried anything I found on xda, but no luck.
When I flash the ZTE B05 zip, I don't even get the boot animation.

Sui77 said:
Tried exactly the steps you descriped, but no luck ---- still stuck in animation
Will try it tomorrow with Magist.
How can I go back to total stock.
Tried anything I found on xda, but no luck.
When I flash the ZTE B05 zip, I don't even get the boot animation.
Click to expand...
Click to collapse
How do you flash the B05 zip? Did you try to flash the official zip?? lol
Follow my guide on the Guides section ("back to stock safely" or sth), it works...

Choose an username... said:
How do you flash the B05 zip? Did you try to flash the official zip?? lol
Follow my guide on the Guides section ("back to stock safely" or sth), it works...
Click to expand...
Click to collapse
I tired to flash a B5 an B5 bootstack with TWRP 3.1.1 -> not able to boot
Then i flashed, according to your guide, the stock recovery and now the device seems to be really bricked.
After the ZTE logo a lying robot appears for half a second and after that, the device is dead.
Can't boot into TWRP, can't use adb, EDL, ...

Ok, managed to get back TWRP.
But I really don't know how so solve my issue of how to come back to stock :crying:
Flashed a B05 stock (zip) and B05 bootstack and Magist....stuck in boot animation (AXON picture collage).
Fu....

Update:
Managed to flash this files:
ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip
ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
TWRP 3.1.1.0
Phone is up and running with A2017GV1.0.0B09
How can I upgrade to the B05 bootstack and the B05 ROM

Sui77 said:
Update:
Managed to flash this files:
ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip
ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
TWRP 3.1.1.0
Phone is up and running with A2017GV1.0.0B09
How can I upgrade to the B05 bootstack and the B05 ROM
Click to expand...
Click to collapse
to go back to stock, download the full zip of any version you want, and download stock recvovery from b08, you have flashed it.
from twrp, format data, and try to boot, if you cannot, reflash b09 recovery from twrp, select image and the recovery you download, then go to stock recovery and update from sdcard. it allways work for me, if you stuck in boot animation again, reboot recovery and wipe data.
after you succesfully boot, reboot edl, and reflash twrp, the version you were using before witn axon7tool, thats all

Sui77 said:
Update:
Managed to flash this files:
ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip
ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
TWRP 3.1.1.0
Phone is up and running with A2017GV1.0.0B09
How can I upgrade to the B05 bootstack and the B05 ROM
Click to expand...
Click to collapse
Just follow my guide for that. If you flash the B04 recovery (the one i provided) you shouldn't have any trouble

Managed to flash the B05 and phone is up and running.
Made a backup by using TWRP 3.1.1.0 and flashed CarbonRom, which also worked nicely.
However, I'm not able to flash LOS by using the B05 bootstack.
I'm too dumb for this phone

Sui77 said:
Managed to flash the B05 and phone is up and running.
Made a backup by using TWRP 3.1.1.0 and flashed CarbonRom, which also worked nicely.
However, I'm not able to flash LOS by using the B05 bootstack.
I'm too dumb for this phone
Click to expand...
Click to collapse
What B05 bootstack? You have to use the universal bootstack and the A2017G modem file...
Both are on the LOS thread. It seems weird that carbonROM would even boot without the universal bootstack though

Stuck in bootloop trying to flash 7.1 custom rom

My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
I had an older version of twrp so I just updated it to the latest one before attempting this ofc...
I tried flashing the latest RR and AICP and both give me boot loops and I always get this one problem where it says
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
I'm not sure if this has anything to do with the bootloop though...
Going to recovery after seeing the bootloop I always get the "keep system read only?" prompt where i swipe to allow modification but i usually just restore back to my backup from there... i dont think allowing it and trying to boot again will get rid of the bootloop...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..

OppaiHeroStar said:
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
Click to expand...
Click to collapse
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36

dzidexx said:
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
Click to expand...
Click to collapse
The first 3 steps I've already done that since the beginning
Where can i get the nougat modem/is it possible to update to it? I guess that's the reason every single 7.1 custom rom I tried in the android development section gave me boot loops...
And could you link the 21.11.2017 version of RR? I'm looking at the download links for RR and I dont see one with that exact date
edit-just saw your edit

Custom roms for MM modem works better.

I fully wiped using TWRP, checked everything I possibly could except my micro SD card and I flashed RR-N-v5.8.5-20171121-clark-Final.zip then gapps arm64, 7.1 nano and it's still giving me boot loops. I'm using TWRP 3.2.1-0
im gonna try using gapps arm64 7.1 mini really quick since you said I should use that one and see if it boot loops... - Edit guess I was too optimistic thinking this would fix it

Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.

dzidexx said:
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
Click to expand...
Click to collapse
changed to 3.1.1-0 and did everything you said, still have boot loop...
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"

OppaiHeroStar said:
changed to 3.1.1-0 and did everything you said, still have boot loop...
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs

dzidexx said:
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
Click to expand...
Click to collapse
I tried crDroidAndroid-7.1.2-20171119-clark-v3.8.3.zip and it still boot loops :\ I also already tried LineageOS and AICP before we started talking
I went back to my backup and it put me in a bootloop which never happened before but changing cache back to ext4 instead of f2fs fixed it..

OppaiHeroStar said:
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
A little late to chime in and this does not help with your current situation, but here's a little advice. I flash a lot of ROMs (how else am I going to test builds right?). This error happens all the time, BUT if you flash a ROM twice it should not show on the 2nd flash.
So flash order goes:
Wipe/Factory reset
Format data x3 (yes I format my data 3 times for every ROM)
Reboot
Wipe/Factory reset
ROM
ROM again
GAPPS
Wipe caches
Reboot
Do the Initial setup
Reboot before use
OPTIONAL Kernel (if its not already build in)
OPTIONAL Magisk (I never flash Magisk on a clean build but heck I'm expecting a NON boot most of the time anyways)

At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.

acejavelin said:
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
Click to expand...
Click to collapse
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.

OppaiHeroStar said:
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
Click to expand...
Click to collapse
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.

acejavelin said:
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
Click to expand...
Click to collapse
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?

OppaiHeroStar said:
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
Click to expand...
Click to collapse
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.

acejavelin said:
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
Click to expand...
Click to collapse
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it

OppaiHeroStar said:
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
Click to expand...
Click to collapse
What custom did you flashed?

dzidexx said:
What custom did you flashed?
Click to expand...
Click to collapse
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now

OppaiHeroStar said:
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
Click to expand...
Click to collapse
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.

dzidexx said:
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
Click to expand...
Click to collapse
I'm using t-mobile and I've checked the access points, clicking on the one im using and hitting save doesn't fix it. Always getting a notification telling me to sign in to network. Not sure what else I can do. I'll give it a day since I had this kind of problem before when I switched sim cards and data didn't work until the next day
Edit - just went back to stock and my data doesn't work now either... just going to stay at RR now and hope my data fixes itself because my access point settings for tmobile should be correct since I looked it up on the official website..

Max pro m1 bootloop? Please help

Hello, so im stuck now on startup. I actually rooted my phone a week ago and everything's fine until I've downloaded some cracked apks online and restarted my phone. Please help what would i do now
imgur.com/a/07UWA4l

Did you installed Twrp...if yes then you might want clear cache and restart the phone or you could just reflash the rom or any other custom rom....and if you havn't then i am afraid you will have to lose your data..

Paramvir Singh said:
Did you installed Twrp...if yes then you might want clear cache and restart the phone or you could just reflash the rom or any other custom rom....and if you havn't then i am afraid you will have to lose your data..
Click to expand...
Click to collapse
yes yes i've installed twrp, i've actually tried formatting my data, clearing dalvik cache (thru twrp) then restarted it but still stuck at loading zenfone logo. i dont care bout my data on phone, just wanna get my phone back to normal.
can u please elaborate bout reflashing rom? i've never done flashing any rom before , stock or custom,

Never done this on my M1 but on my note edge,
When i got a bootloop, i simply reinstall stock rom, or just clean install custom rom

abcnormal said:
yes yes i've installed twrp, i've actually tried formatting my data, clearing dalvik cache (thru twrp) then restarted it but still stuck at loading zenfone logo. i dont care bout my data on phone, just wanna get my phone back to normal.
can u please elaborate bout reflashing rom? i've never done flashing any rom before , stock or custom,
Click to expand...
Click to collapse
Ok so it's good opportunity to try something new...first you need to download custom rom and gapps package to sd card (always a better option)or internal storage...do the downloads on pc or somewhere else...
1. Wipe cache, dalvik cache, system, vendor, data, internal storage(this one is optional)
2. Mount extsd card
3. Install Rom package...(i personally use xenonhd based on pie) from here https://mirrors.c0urier.net/android...tal/X00T/XenonHD-181007-Experimental-X00T.zip
You can try any other of your choice
4. Install Gapps package from here..http://download2264.mediafire.com/r0vq21tabscg/m1u4llu62bdwyos/BiTGApps-arm64-9.x.x-0.1-unsigned.zip
5. This step is optional if you want root access then flash magisk package from here..https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip and uninstall package from https://github.com/topjohnwu/Magisk/releases/download/v17.2/Magisk-uninstaller-20180921.zip ......after tge rom boot up install magisk manager from https://github.com/topjohnwu/Magisk/releases/download/manager-v6.0.0/MagiskManager-v6.0.0.apk
6. Reboot to system..first boot up will take 4-5 minutes...ENJOY

so i tried flashing the stock rom but i got an error
Code:
[B] This package is for "ASUS_X00TD" devices; this is a "X00TD"[/B]
i got the rom at asus.com/ph/Phone/ZenFone-Max-Pro-ZB602KL/HelpDesk_BIOS/
i guess i'll try flashing with a custom rom instead?
also a follow up question: is it safe to reboot to recovery with twrp even my phone has no OS installed (already wiped it for flashing a new rom)

abcnormal said:
so i tried flashing the stock rom but i got an error
Code:
[B] This package is for "ASUS_X00TD" devices; this is a "X00TD"[/B]
i got the rom at asus.com/ph/Phone/ZenFone-Max-Pro-ZB602KL/HelpDesk_BIOS/
i guess i'll try flashing with a custom rom instead?
also a follow up question: is it safe to reboot to recovery with twrp even my phone has no OS installed (already wiped it for flashing a new rom)
Click to expand...
Click to collapse
Stock rom available at asus website is not flashable through twrp...u need twrp flashable zip...download this file...
https://forum.xda-developers.com/showpost.php?p=77671149&postcount=83
And also decrypt file from here.... https://forum.xda-developers.com/asus-zenfone-max-pro-m1/how-to/mod-decrypt-data-t3787311
After flashing the rom...flash decrypt zip
And remember to wipe internal storage after flashing these two zips!

Hello sir i got stuck in bootloop in asus max pro m1
Actually its not showing anything screen is blinking as i try to turn it on. I was on custom rom and suppose to install stock rom and i followed every step but my phone doesn’t start its just reboot and nothing displays anything. Please can anyone tell me the solution of this issue.

did u solved issue
how did u soolves issue ??

Phone stuck at Decryption unsuccessful :crying:

I am stuck at encryption failed when I flash stock oreo rom. I tried formatting data using twrp and flashed no encryption file as well but nothing works.:crying::crying::crying:
I just want to use the stock oreo rom again with root.
Pls help:crying:

Which ROM did you try and flash / install?
Try upgrading your TWRP to the latest version too.

jl10101 said:
Which ROM did you try and flash / install?
Try upgrading your TWRP to the latest version too.
Click to expand...
Click to collapse
I used partition dl mode to flash the stock oreo rom over 7.0 to keep the root. Then i flashed custom kernal for stock 8.0 but it didnt work. I have done the same procedure before and it has worked like a charm. But it keeps on giving the encrytion error when i try it now

Deadmeat03 said:
I used partition dl mode to flash the stock oreo rom over 7.0 to keep the root. Then i flashed custom kernal for stock 8.0 but it didnt work. I have done the same procedure before and it has worked like a charm. But it keeps on giving the encrytion error when i try it now
Click to expand...
Click to collapse
Odd. If I had to guess anything, it would be that not all the partitions were flashed when going from Nougat to Oreo.
I once flash a Nougat ROM from an Oreo ROM and I had the same encryption issue and lost everything.
That was the last time I would trust myself again and not do a backup.

Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track...

Prowler_gr said:
Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track...
Click to expand...
Click to collapse
I tried that as well. With stock recovery is says data is corrupted and doesn't do anything. I think it might be a problem with patched lg up because when i use normal lg up to flash oreo it works. But I cant root then.

I would try changing to 3.2.3-4 TWRP and then trying the procedure again. It seems that the 3.3.0 TWRP does not decrypt properly sometimes.

In the same boat as OP
scottyrick said:
I would try changing to 3.2.3-4 TWRP and then trying the procedure again. It seems that the 3.3.0 TWRP does not decrypt properly sometimes.
Click to expand...
Click to collapse
Hi
Looking for a way to keep TWRP and root ... any help appreciated
I've got a US996 with the same issue as the op. I have the latest TWRP 3.3.1-0. The phone was working fine until I upgraded twrp but I might have done a mistake resetting phone outside of twrp.
I can still get back into twrp but I haven't been able to install zip files without getting that decryption unsuccessful message when booting to system.
When getting back into TWRP using hardware buttons sometimes there is a prompt asking "keep system read only?" which I never chose and swipe to allow modification. I think this happens after
I pull the battery after getting the decryption unsuccessful message. There is a reset system that I could chose under the decryption unsuccessful message but I'm assuming that will make me lose twrp
...but if my phone is a us996 and is still
unlocked, would it matter if I did select it? Wouldn't I be able to reinstall twrp using adb again on a computer after Oreo is reinstalled?
To do Prowler_gr's suggestion which guide do I follow (sounds like I should do the second option)
"Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track... "
1-[GUIDE][UNBRICK] Patch LGUP to unlock features & unbrick V20 (Variant mismatch fix) to use lgup
or this guide
2-Ultimate guide to unbrick LG V20(Only Variants with .KDZ)[No OS Firmware Update Loop]
Thank you for any guidance on this...

There is a reset system that I could chose under the decryption unsuccessful message but I'm assuming that will make me lose twrp
Click to expand...
Click to collapse
Don't blame me if this goes wrong but I'm pretty much 100% certain that you mush press the rest button. This has happened to me a few times I'm sure. You won't loose twrp. Whatever resetting goes on in the background I don't think it's an actual Factory Reset.
Edit: Just to be clear you taking about a white screen with I think in dark blue or black text ENCRYPTION UNSUCCESSFUL and something like "reset phone" option directly under it, on the upper half of the screen?

Hi ezzony
Yes you are thinking of the right decryption unsuccessful page. I get it when booting to system
after installing Oreo and magisk 19 and having wiped everything (format data too). I will get the exact wording of it tonight
Thanks!

downgrade twrp i has same prob twrp 3.3.1 gives issues

ghet2rockuu said:
downgrade twrp i has same prob twrp 3.3.1 gives issues
Click to expand...
Click to collapse
Hi ghet2rockuu
I downgraded twrp and that got it working Thank You! see also Phoenix591 thread [Recovery][Unofficial for the moment]TWRP 3.3.1-0 : 2019-05-17 #625
Thank You !