Related
UPDATE: This is now unneeded because threr is a faster way ro unlock bootloader on official MM here, he updated for official MM
Hi, I discovered an unlock method for official MM!! This maybe long but's it totally safe
You need:
Adb and fastboot environment ready PC
LP RAW File
Android 6.0 Beta Unlock tool
Android 5.0 One-Click Unlock tool
First version of beta MM (Z00A) (Z008)
Official MM zip (find it on Asus site)
Thanks to all people upload these links
Just do the following:
Flash the lastest LP via AFT (using raw file given above), wipe all data. If you already on MM, you have to downgrade
Unlock your bootloader using 1 click tool given above
Boot to stock recovery and sideload the first version of beta MM
Unlock the bootloader using MM beta unlock tool above
Boot to stock recovery
Two case here:
Case 1: You can't boot stock recovery
Normally boot your phone (to Android)
Setup it as a new phone
If it shows there is a new firmware, don't update!!!
Enable Developer options, then enable usb debugging
Copy the official MM zip to external sd card
Open command prompt, run adb reboot recovery, accept the adb permission if prompted
After it boots to recovery, select Apply update from SD, then choose the zip file you've copied before
Wait for it to update, it may stuck at flashing splashcreen, don't worry, it's trolling you, may be Asus forgot to update the script
Goto step 7
Case 2: You can boot stock recovery
Sideload the official MM zip (adb sideload <filename>.zip)
Goto step 7
7. Flash this TWRP (fastboot flash recovery <twrp>.img)
8. Root your phone using this method
9. Reboot, if it shows "Your phone has failed verification bla bla..", then you've success. It may reset loop like note 7 in the first time start, don't worry.
9. Enjoy :highfive:
Note: If you're facing with battery problems on MM, factory reset it in Settings > Backup and Reset > Factory Reset > Erase everything
Successfully on my ZE550ML
The warning screen is normal so don't worry and there is no way to fix it for now
Reverse
Reverse #2
Please answer this I have a unlocked Bootloader + twrp Intalled + root, now I am really confused that after upgrading to MM will my Bootloader get automatically lock or what
Sent from my ASUS_Z00A using XDA-Developers mobile app
NiTesh said:
Please answer this I have a unlocked Bootloader + twrp Intalled + root, now I am really confused that after upgrading to MM will my Bootloader get automatically lock or what
Sent from my ASUS_Z00A using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, BL will be relocked once you upgrade to MM.
If you want to unlock MM BL(6.0), refer to this thread.
Or you can downgrade to Lollipop referring to this thread. Then your BL(5.0) is unlocked.
Upgrade to MM
Hello folks!
2 week before MM was released i'ved opted to unlock my ZE551ML BL and therefore install twrp and a MM custom ROM..
so here´s the thing i stayed with the ROM for about 3 weeks and honestly..it works very well..but when i knew that 6.0 official was coming out i decided to go back to stock..i did it following manny tuturials avaliable for me to get my BL Re-Locked..but unsuccessfully..so i followed mr_gourav2000 tuturial (http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526) and reverted to the WW_Z00A-2.20.40.183-to-2.20.40.184 (hopefully i can get the sshot in this post) version...since my BL is unlocked i can´t get no updates..my question is:
Is there anyway to go to MM 6.0 by ASUS with the current status of my phone?
is there anything i can do to revert this??
Cheers to everyone
https://www.dropbox.com/sc/xue7iuqfyvgdvo3/AAATR4mYtcHzM1IhfKbx2a1oa
R3D SoX F4N said:
Hello folks!
2 week before MM was released i'ved opted to unlock my ZE551ML BL and therefore install twrp and a MM custom ROM..
so here´s the thing i stayed with the ROM for about 3 weeks and honestly..it works very well..but when i knew that 6.0 official was coming out i decided to go back to stock..i did it following manny tuturials avaliable for me to get my BL Re-Locked..but unsuccessfully..so i followed mr_gourav2000 tuturial (http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526) and reverted to the WW_Z00A-2.20.40.183-to-2.20.40.184 (hopefully i can get the sshot in this post) version...since my BL is unlocked i can´t get no updates..my question is:
Is there anyway to go to MM 6.0 by ASUS with the current status of my phone?
is there anything i can do to revert this??
Cheers to everyone
https://www.dropbox.com/sc/xue7iuqfyvgdvo3/AAATR4mYtcHzM1IhfKbx2a1oa
Click to expand...
Click to collapse
Just download the update package and rename it to mofd_sdupdate.zip, copy it to internal storage. Then reboot to stock recovery, the update will automatically start. This should work if you have lastest stock recovery
can anyone please upload official recovery for Zenfone 2 ZE551ML, currenty i have twrp installed on Android version 5.0 LP Stock
HungNgocPhat said:
Just download the update package and rename it to mofd_sdupdate.zip, copy it to internal storage. Then reboot to stock recovery, the update will automatically start. This should work if you have lastest stock recovery
Click to expand...
Click to collapse
i have twrp recovery at the moment cause i followed mr_gouvad2000 tuturial..
what do you sugest?
flash WW_ZE551ML_2.20.40.196_20160815.raw?
WW_ZE551ML_2.20.40.194_20160713.raw?
and then go and do what you told?
cheers
hello, i cant find first mm beta for ml551...can you help me? thank you and sorry for my english
tridet18 said:
hello, i cant find first mm beta for ml551...can you help me? thank you and sorry for my english
Click to expand...
Click to collapse
someone correct me if i am worng but....
https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/
Look for this version WW-4.21.40.134
Hello, thank you but this version is official, i need de first beta 6.0
R3D SoX F4N said:
someone correct me if i am worng but....
Look for this version WW-4.21.40.134
Click to expand...
Click to collapse
that version...i can´t find it anywere..maybe someone here knows were to find it?
Updated the first MM beta link in OP
hello , thanks to your tutorial I managed to unlock the bootloader , I have TWRP version 3.0.0.2 with stock installed but when I wanted to install CM13 and gapps I restarted the phone and automatically returns to recovery again. some help?
tridet18 said:
hello , thanks to your tutorial I managed to unlock the bootloader , I have TWRP version 3.0.0.2 with stock installed but when I wanted to install CM13 and gapps I restarted the phone and automatically returns to recovery again. some help?
Click to expand...
Click to collapse
Have you downloaded the correct build? There are build for MM bootloader, if you flash the normal builds, it will fail and reboot to recovery again. Gapps is the same for all builds
After you install that special build, do not update to newer nightlies, it will fail. For updates, check the link i give you and see if there is a new MMBL build.
About that, here is the post: http://forum.xda-developers.com/showpost.php?p=68542370&postcount=8551
hello friend, I tried to install the CM13 ROM that indicated me and I get Error 7 in TWRP 3.0.2.0, I have Android 6.0 (.134) official and if I can change kernel and flash rom SuperSU but change with a new MM Blows I can not (CM13, AICP, beanstalk ....) thanks for your help!
tridet18 said:
hello friend, I tried to install the CM13 ROM that indicated me and I get Error 7 in TWRP 3.0.2.0, I have Android 6.0 (.134) official and if I can change kernel and flash rom SuperSU but change with a new MM Blows I can not (CM13, AICP, beanstalk ....) thanks for your help!
Click to expand...
Click to collapse
Run the script again (i gave you in above post). Download the CM13 in that link, not in the OP of CM13 thread. Flash that CM13 and Gapps (Gapps is universal for MMBL and LPBL).
May be you have corrupt download, I'm currently running CM13 on MMBL
Hello, I have finally found the solution, the problem is the recovery, the TWRP 3.0.0.2 da failure with new builds, I Flashed next on the link you put me through adb and now it works, thank you very much for everything .
hlp
tridet18 said:
Hello, I have finally found the solution, the problem is the recovery, the TWRP 3.0.0.2 da failure with new builds, I Flashed next on the link you put me through adb and now it works, thank you very much for everything .
Click to expand...
Click to collapse
how u unlocked bootloader
Guys.
I made a bit modified version of @russel5 very nice work for our Z3C:
- A bit more colors, nice navbar buttons and new navbar background (fits to main screen background)
- More img flash options (be carefull with img flash because wrong flashes can brick you phone)
- More partition backup and restore options (boot is also included for sure - but not shown on the pic)
- New with 3.1.0-0: Additional partition for backup/restore: mmcblk1p2 ext4 mounted to /sd-ext - This is second partition on external SD Card, if available.
- New with 3.1.1-0: All above mentioned changes and official ones: https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
Too beauty to keep it only for me
Requirements
Only for Unlocked Bootloader (UB)
New Bootloader needed: LA3.0_M_3
Information
Maybe NOT working with 7.x.x ROMs like (LineageOS/Carbon) - Only tested with MM and stock-like ROM (like SLiMM 3.8).
Please visit corresponing threads for help with TWRP and any 7.x.x ROM.
Installation - 2 Options:
a) Flashable zip via TWRP to update existing.
b) Extract twrp-3.x.x-0-z3c_Vxx.img from zip-file and flash via fastboot: fastboot flash recovery twrp-3.x.x-0-z3c_Vxx.img
Start FOTA Recovery:
Shut down phone completely - wait 5-10 secs - Press Power and Vol Down until short vibration - release both keys and wait - done.
UPDATE 18.06.2017
New 3.1.1-0 from Russel5 - Modded by me. Thanks to Russel5 and TWRP-Team.
UPDATE 15.03.2017
New 3.1.0-0 from Russel5 - Big thx again to him! Say thanks to him - not me!
Thanks to @russel5 - This is his work:
https://forum.xda-developers.com/z3-compact/general/d5803-z3c-aries-twrp3-0-t3543113
@fluffi444 I flashed the recovery.img in fota with twrp and recovery is still 3.0.2. Any idea why?
doriandiaconu said:
@fluffi444 I flashed the recovery.img in fota with twrp and recovery is still 3.0.2. Any idea why?
Click to expand...
Click to collapse
Maybe i have an idea.... You know how to start FOTA Recovery correctly?
Shut down phone completely - wait 5 secs - Press Power and Vol Down until short vibration - release both keys and wait - done.
Looks like you still booting your system or kernel recovery....
Otherwise check your bootloader - must be LA3.0_M_3 (Service Menu - Service Info - Software Info - S1 Boot Version)
UPDATE 15.03.2017
New 3.1.0-0 from @russel5 - Big thx again to him! Say thanks to him - not me!
can someone please explain/summarize for me the differences of twrp recoveries that we have on the z3c. if i got it right, there is (1) old bl recovery = kernel 'attached', (2) new bl recovery = seperated img from kernel and (3) fota recovery wich uses an unused partition of unlocked bl.
is that correct?
whats the advantage of fota? can every custom rom use all the different recoveries? can (2) + (3) be flashed both on the same device?
i am really confused wich version i wanna install and keep on my phone...
thanks
filou76 said:
can someone please explain/summarize for me the differences of twrp recoveries that we have on the z3c. if i got it right, there is (1) old bl recovery = kernel 'attached', (2) new bl recovery = seperated img from kernel and (3) fota recovery wich uses an unused partition of unlocked bl.
is that correct?
whats the advantage of fota? can every custom rom use all the different recoveries? can (2) + (3) be flashed both on the same device?
i am really confused wich version i wanna install and keep on my phone...
thanks
Click to expand...
Click to collapse
Yes - this all can be confusing!
I'm trying to be complete as I can be - I will mention only the last dev of the tools - Actually many more are involved and often it's an growing work of many - Especially No 1.
1) For LB - We have recovery (and root) for LB - Here the last (and best) rooting and TWRP method is the one from russel5:
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This installs recovery files to SYSTEM partition folder /system/etc/mm_twrp_recovery
This is file: recovery.twrp.cpio.lzma
2) Only UB - Recovery integrated in Kernel a) and b)
a) Rootkernel (tobias.waldvogel) https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
afaik this was one of the first tools which can integrated automaticly very resource-conserving recovery to kernel - Disadvantage: Hard to change TWRP if new version is out.
b) PoC TA Tool (munjeni) https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893
Great quite new tool which can also integrate TWRP (but here the complete fota recovery.img) to kernel: Advantage easy to change TWRP to new version, because full fota revovery.img is used
3) Only UB - Recovery to FOTA partition (now known as recovery partition) - newer bootloader needed
This is the recovery.img you can download from official TWRP page or from russel5 (img to be flashed via fastboot) or from this thread (flashable.zip).
Those recovery.img's are complete bootable images with zImage and ramdisk (TWRP is in ramdisk).
That all means that it's indeed possible to have THREE recvoerys running on one phone! But this is senseless of course !!!
Option 1 is only recomended if you are on LB! But works also for UB. But its away if you flash complete new ROM (as TWRP is on SYSTEM)
Option 2 is.... for what? Let me say: Only if you really need the function to reboot to recovery directly from system.
Option 3 is my favorite (but only for UB) - this is bootable no matter what you did to system or even with kernel!
It's on his own seperate partionen and save for unwanted modifications, wrong boot or system flashes, etc
Only (and actually not really an) disadvantage is that you have to start this from shutted down phone... Reboot to recovery is not working!
fluffi444 said:
Yes - this all can be confusing!
I'm trying to be complete as I can be - I will mention only the last dev of the tools - Actually many more are involved and often it's an growing work of many - Especially No 1.
1) For LB - We have recovery (and root) for LB - Here the last (and best) rooting and TWRP method is the one from russel5:
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This installs recovery files to SYSTEM partition folder /system/etc/mm_twrp_recovery
This is file: recovery.twrp.cpio.lzma
2) Only UB - Recovery integrated in Kernel a) and b)
a) Rootkernel (tobias.waldvogel) https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
afaik this was one of the first tools which can integrated automaticly very resource-conserving recovery to kernel - Disadvantage: Hard to change TWRP if new version is out.
b) PoC TA Tool (munjeni) https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893
Great quite new tool which can also integrate TWRP (but here the complete fota recovery.img) to kernel: Advantage easy to change TWRP to new version, because full fota revovery.img is used
3) Only UB - Recovery to FOTA partition (now known as recovery partition) - newer bootloader needed
This is the recovery.img you can download from official TWRP page or from russel5 (img to be flashed via fastboot) or from this thread (flashable.zip).
Those recovery.img's are complete bootable images with zImage and ramdisk (TWRP is in ramdisk).
That all means that it's indeed possible to have THREE recvoerys running on one phone! But this is senseless of course !!!
Option 1 is only recomended if you are on LB! But works also for UB. But its away if you flash complete new ROM (as TWRP is on SYSTEM)
Option 2 is.... for what? Let me say: Only if you really need the function to reboot to recovery directly from system.
Option 3 is my favorite (but only for UB) - this is bootable no matter what you did to system or even with kernel!
It's on his own seperate partionen and save for unwanted modifications, wrong boot or system flashes, etc
Only (and actually not really an) disadvantage is that you have to start this from shutted down phone... Reboot to recovery is not working!
Click to expand...
Click to collapse
Wow, thanks a lot @fluffi444!! It's even more complicated than I thaught. WHAT A MESS! :silly:
Well I'am still on Concept Rom --> Bootloader LA3.0_L_Hero_16. I guess that one is close to LA3.0_M_3? Don't remember where I got my TWRP 3.0.0.0 version from, but i flashed it as recovery.img, so it should be fota-type, right? Actually I can reboot from system to recovery ...
I think I'll keep this one as is and see if I need a newer version one day, when i change system to any Nougat rom.
filou76 said:
Wow, thanks a lot @fluffi444!! It's even more complicated than I thaught. WHAT A MESS! :silly:
Well I'am still on Concept Rom --> Bootloader LA3.0_L_Hero_16. I guess that one is close to LA3.0_M_3? Don't remember where I got my TWRP 3.0.0.0 version from, but i flashed it as recovery.img, so it should be fota-type, right? Actually I can reboot from system to recovery ...
I think I'll keep this one as is and see if I need a newer version one day, when i change system to any Nougat rom.
Click to expand...
Click to collapse
Yes - flashing by fastboot goes to FOTA/Recovery partition... Yes - keep it - I don't even know how Concept N or M will react...
Did anyone tried to do backup/restore with this recovery?
I am using it since flashing to LineageOS 14.1 and did multiple backups. Tonight I broken my google account in the ROM, so I wanted to restore to last backup. I already tried four of my backups and all of them are bootlooping, so I am starting to suspect the recovery, as all of those backups were done from perfectly working system.
johny.mnemonic said:
Did anyone tried to do backup/restore with this recovery?
I am using it since flashing to LineageOS 14.1 and did multiple backups. Tonight I broken my google account in the ROM, so I wanted to restore to last backup. I already tried four of my backups and all of them are bootlooping, so I am starting to suspect the recovery, as all of those backups were done from perfectly working system.
Click to expand...
Click to collapse
Yes - fully working here. Even Restore. But I still use 6.0.1.
But sometimes (not recovery version related) its not enough to restore only DATA or only SYSTEM.
It happens to me that only an complete restore of all saved partition did the trick...
But as I said that happens also with older recoverys or/and not modded.
fluffi444 said:
Yes - fully working here. Even Restore. But I still use 6.0.1.
But sometimes (not recovery version related) its not enough to restore only DATA or only SYSTEM.
It happens to me that only an complete restore of all saved partition did the trick...
But as I said that happens also with older recoverys or/and not modded.
Click to expand...
Click to collapse
Then it must be something either with my setup, or with 7.1.1 itself.
I tried everything: partial restore, full restore, new flash with recovering of data partition only... Everything was bootlooping.
I am not sure what finally worked, as I was trying it desperately for hours, but most probably the last mentioned thing without flashing Magisk.
johny.mnemonic said:
Then it must be something either with my setup, or with 7.1.1 itself.
I tried everything: partial restore, full restore, new flash with recovering of data partition only... Everything was bootlooping.
I am not sure what finally worked, as I was trying it desperately for hours, but most probably the last mentioned thing without flashing Magisk.
Click to expand...
Click to collapse
Try twrp 3.0.2.0 or 3.0.3.0. Some said they have problems with 3.1.0.0 an LOS.
UPDATE 18.06.2017
New 3.1.1-0 from Russel5 - Modded by me. Thanks to Russel5 and TWRP-Team.
Hi,
This recovery its amazing because i am trying to have a 6.0.1 With TWRP 3.x.x with Magisk, root and Xposed. At the moment when i ve Magisk and root, i miss Recovery by Magisk mod boot image.
Any idea why screen appear as out resolution or refresh. At least ... it seen enter on Recovery, BUT I CANT reset With Vol+, Vol-, Cam , Power...
at least i can connect by adb and restart.
¿Any idea?
Thanks
zeryors said:
Hi,
This recovery its amazing because i am trying to have a 6.0.1 With TWRP 3.x.x with Magisk, root and Xposed. At the moment when i ve Magisk and root, i miss Recovery by Magisk mod boot image.
Any idea why screen appear as out resolution or refresh. At least ... it seen enter on Recovery, BUT I CANT reset With Vol+, Vol-, Cam , Power...
at least i can connect by adb and restart.
¿Any idea?
Thanks
Click to expand...
Click to collapse
Hi, i know the sad answer... the problem its the screen, Original Screen (broken touch panel) show perfect Recovery but the "new" screen its the problem... its compatible but not 100% :_(
It´s curious a normal Recovery show OK but not FOTA
Hi there,
booting this current version of TWRP from `recovery/fota` is not working for me. The device just reboots but should load TWRP. I flashed it via `fastboot flash recovery [twrp.img]` without any errors.
TWRP is booting if I flash it to `boot` instead of `recovery`. I flashed CarbonROM this way but lost TWRP after that of course. I also tried [russel5's TWRP 3.1.1-0] which is not booting from `recovery/fota` either. However, an older TWRP version by Tomascus I found -> here <- is booting fine from `recovery/fota`.
Maybe this is bootloader related but I am not entirely sure. If so, how can I update the bootloader?
Sony Xperia Z3 Compact D5803
- Bootloader: 1286-7314_S1_Boot_MSM8974AC_LA3.0_52-2
- ROM: CARBON-CR-5.1-MOO-RELEASE-z3c-20170918-1012
TWRP's tried:
- Russel5's TWRP 3.1.1-0 FOTA Recovery MOD by fluffi444
- [D5803,z3c,aries]Twrp_3.1.1-0_img_for_unlocked_bootloader by russel5
- Tomascus TWRP 3.1.0-0
Andi- said:
Hi there,
booting this current version of TWRP from `recovery/fota` is not working for me. The device just reboots but should load TWRP. I flashed it via `fastboot flash recovery [twrp.img]` without any errors.
Click to expand...
Click to collapse
My MOD is technically the same as original one from Russel. So please ask in his thread (you did this already... btw: please do not post the same question in several threads)
I never tried 7.x.x-based ROMs. So I cannot say anything reladed to the compatibility I'm afraid. MM with stock-like ROM is working with 3.1.1.0 (from Russel).
I will make an note in OP...
And note this: https://forum.xda-developers.com/showpost.php?p=71882082&postcount=12
I am trying to install a newer TWRP for Carbon Mod custom rom. I tried:
- install .img with TWRP in TWRP
- flashify
- official app TWRP from google play
- fastboot commands with "platform-tools"
Everywhere I get a message that everything went fine but in TWRP I still have the old version - 3.0.0.2 :/
I am asking for help because I have been fighting this from two days :/
I have Xperia Z3C with unlocked bootloader, stock prerooted firmware .291 + EliteKernel v3.
Piospi said:
I am trying to install a newer TWRP for Carbon Mod custom rom. I tried:
- install .img with TWRP in TWRP
- flashify
- official app TWRP from google play
- fastboot commands with "platform-tools"
Everywhere I get a message that everything went fine but in TWRP I still have the old version - 3.0.0.2 :/
I am asking for help because I have been fighting this from two days :/
I have Xperia Z3C with unlocked bootloader, stock prerooted firmware .291 + EliteKernel v3.
Click to expand...
Click to collapse
To which partition have you installed the TWRP image file? Starting with your phone turned off, f it's been sent to the FOTAKernel partition, hold both the power and the volume down buttons until your phone vibrates (as if it was booting up normally), when you should release the power button. When the screen lights up, release the volume down button.
Otherwise, if you installed TWRP in the recovery partition, boot your phone up as usual. When you see the led lit up, press the volume button.
casouzaj said:
To which partition have you installed the TWRP image file? Starting with your phone turned off, f it's been sent to the FOTAKernel partition, hold both the power and the volume down buttons until your phone vibrates (as if it was booting up normally), when you should release the power button. When the screen lights up, release the volume down button.
Otherwise, if you installed TWRP in the recovery partition, boot your phone up as usual. When you see the led lit up, press the volume button.
Click to expand...
Click to collapse
Thank you very much for the answer. Starting the phone with Power + VolUp does not do anything. The phone shows the Sony logo and the system starts.
I installed the IMG file in recovery / fota and the ZIP version doesn't ask for locations.
OK, so I totally ****ed up somewhere while trying to wipe and flash stock while I could only see half my screen. I now have a fully working screen but no system.
Current situation is if trying to boot phone normally I get stuck on ZTE logo.
If I press volume keys during boot I get to here; https://puu.sh/z7YQa/8de2adc04e.jpg
Selecting recovery takes me to TWRP which immediately asks for a password (that I never set up).
If I attempt to flash RR (which was previously installed) I get error 7. (Lineage OS has the same response) https://puu.sh/z81cA/6371d882cc.jpg
I can successfully flash the latest TWRP (twrp-3.2.1-0-ailsa_ii.img).
I've also tried flashing A2017_N_Modem.zip and ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip which appear to complete successfully.
TWRP ADB Sideload seems to work and my PC can see the phone (adb devices but I've not tried anything with that yet for fear of ****ing up further.
Code:
C:\Users\Fish\Downloads\ADB>adb devices
List of devices attached
e33edd51 sideload
MrGodMan said:
OK, so I totally ****ed up somewhere while trying to wipe and flash stock while I could only see half my screen. I now have a fully working screen but no system.
Current situation is if trying to boot phone normally I get stuck on ZTE logo.
If I press volume keys during boot I get to here; https://puu.sh/z7YQa/8de2adc04e.jpg
Selecting recovery takes me to TWRP which immediately asks for a password (that I never set up).
If I attempt to flash RR (which was previously installed) I get error 7. (Lineage OS has the same response) https://puu.sh/z81cA/6371d882cc.jpg
I can successfully flash the latest TWRP (twrp-3.2.1-0-ailsa_ii.img).
I've also tried flashing A2017_N_Modem.zip and ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip which appear to complete successfully.
TWRP ADB Sideload seems to work and my PC can see the phone (adb devices but I've not tried anything with that yet for fear of ****ing up further.
Click to expand...
Click to collapse
Look, you have an A2017G, right? Error 7 is caused by not flashing the universal bootloader. The password is because you forgot to flash magisk or supersu on the last rom's first boot.
Download 3 things: raystef66's TWRP flashable B09 bootstack and stocksystem zips (from the download center or the dedicated thread, but make sure that it's the TWRP flashable ones) and Magisk 15.2. Install the BOOTSTACK, then the ROM, then Magisk. After that go to Wipe, and FORMAT DATA (not wipe!). You'll lose your internal storage.
Choose an username... said:
Look, you have an A2017G, right? Error 7 is caused by not flashing the universal bootloader. The password is because you forgot to flash magisk or supersu on the last rom's first boot.
Download 3 things: raystef66's TWRP flashable B09 bootstack and stocksystem zips (from the download center or the dedicated thread, but make sure that it's the TWRP flashable ones) and Magisk 15.2. Install the BOOTSTACK, then the ROM, then Magisk. After that go to Wipe, and FORMAT DATA (not wipe!). You'll lose your internal storage.
Click to expand...
Click to collapse
Thank you so much. Got that all done nicely and have a working stock ROM.
How would I now get from here back to RR?
MrGodMan said:
Thank you so much. Got that all done nicely and have a working stock ROM.
How would I now get from here back to RR?
Click to expand...
Click to collapse
Reading instructions is a start :laugh:
For real now: Get the ROM, the B15 universal bootloader (from the Lineage thread), get the latest modem file from the download center (B09 now for example), Magisk 15.2, GApps zip (unless you'll go microG) and be sure that you are on the latest TWRP or update to it.
Flash the bootloader and modem file (you'll have to install the modem as image i think). After you flash the bootloader your phone model becomes 'axon7' instead of 'ailsa_ii'; most custom roms use this to know whether you flashed it or not; and the region will be A2017U which is normal (it is based off of B15 for the U, don't panic). After that, flash the ROM and Magisk and GApps.
Choose an username... said:
Reading instructions is a start :laugh:
For real now: Get the ROM, the B15 universal bootloader (from the Lineage thread), get the latest modem file from the download center (B09 now for example), Magisk 15.2, GApps zip (unless you'll go microG) and be sure that you are on the latest TWRP or update to it.
Flash the bootloader and modem file (you'll have to install the modem as image i think). After you flash the bootloader your phone model becomes 'axon7' instead of 'ailsa_ii'; most custom roms use this to know whether you flashed it or not; and the region will be A2017U which is normal (it is based off of B15 for the U, don't panic). After that, flash the ROM and Magisk and GApps.
Click to expand...
Click to collapse
Perfection.
Everything works!
Hello everyone.
I can't flash any recovery via fastboot, I can only flash two recovery files one is the original twrp and second is the original op5 recovery. those cannot install the new ota.
If I try to flash any other recovery file, it enters the qualcomm boot recovery mode, white led and nothing else on phone and a qual 9008 port on pc.
What should I do? My brain kinda melted, so I might forgot to add more infos.
SweetyVolty said:
Hello everyone.
I can't flash any recovery via fastboot, I can only flash two recovery files one is the original twrp and second is the original op5 recovery. those cannot install the new ota.
If I try to flash any other recovery file, it enters the qualcomm boot recovery mode, white led and nothing else on phone and a qual 9008 port on pc.
What should I do? My brain kinda melted, so I might forgot to add more infos.
Click to expand...
Click to collapse
The questions you need to answer:
Is your bootloader unlocked?
Do you have a custom recovery installed?
Is your storage encryped?
What's your actual rom?
What do you want to do(installing ota from android ota menu isn't working for you or why you don't use that method)?
Please give EXACT file names of the files you're trying to flash!
Is your bootloader unlocked? Yes, although I locked then unlocked again for trying.
Do you have a custom recovery installed? yes, I tried both
Is your storage encryped? probably no, I wiped everything but before it wasn't necessary to enter a unlock code or fingerprint etc.
What's your actual rom? It was on oreo, now I don't have a rom lol
What do you want to do(installing ota from android ota menu isn't working for you or why you don't use that method)?
Installing from Ota wasn't successful, sideload does not work, installing custom recoveries result in qualcomm boot (black screen with white led)
only twrp working is this untouched twrp but it has not able to flash the new pie.. https://twrp.me/oneplus/oneplus5.html
twrp from the clockworkmod not able to boot.
My intent is to flash new pie and root. I can't able to flash the pie's original beta recovery too. https://oxygenos.oneplus.net.s3.amazonaws.com/recovery.img
Also I can't mount vendor too I don't know if this causes the problem or not....
SweetyVolty said:
Also I can't mount vendor too I don't know if this causes the problem or not....
Click to expand...
Click to collapse
Ok, so it seems you have an old Oreo stock oos rom before without vendor partition and trying to flash an pie rom and pie recovery, but still on Oreo firmware that's not possible cause newer recoveries need pie firmware which comes along with oos pie roms and you're missing the vendor partition which comes with 5.1.4.
Your starting point is the same as mentioned here https://forum.xda-developers.com/oneplus-5/help/qa-help-thread-newbies-post-t3624656/post79251968
OOS 5.1.4 then you have a vendor partition, then you can install one of those stock Pie oos roms.
You can install oos 5.1.4 with stock recovery or with siankatabg's or with this one
https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk
Then you just need to follow the instructions for the stock oos or beta rom.
If you have any concerns or further questions, please feel free to ask here
Hey
So my bootloader unlock wait time is coming up tomorrow, but this forum is not giving me much hope as all I can see is problems with TWRP constantly being replaced with the stock recovery and general incompatibility (recovery loops or bootloader loops), no one seems to know which of the 10,000 versions of TWRP and OrangeFox (????) recovery to use.
Can anyone clarify what the situation is with Xiaomi Mi 9T or is this phone doomed and its just worth throwing on eBay (a phone without custom recovery and root is absolutely worthless to me).
Thanks a plenty!
Hi!
"TWRP constantly being replaced with the stock recovery"
=> That's nothing to do about Android version: It's a Xiaomi/MIUI boot protection feature. Some TWRP flash a modified VBMeta image, at first TWRP boot, to disable this protection.
- What you can do:
1) Download latest OrangeFox and put ZIP file in phone storage
2) Download latest Official TWRP, flash it via fastboot then hold "Power" and "Vol+" buttons (both) until TWRP is booted
3) Select OrangeFox ZIP file in TWRP and flash it (phone will automatically restart to OrangeFox Recovery).
4) Done! You can now flash latest Magisk version. ^^
Micdu70 said:
Hi!
"TWRP constantly being replaced with the stock recovery"
=> That's nothing to do about Android version: It's a Xiaomi/MIUI boot protection feature. Some TWRP flash a modified VBMeta image, at first TWRP boot, to disable this protection.
- What you can do:
1) Download latest OrangeFox and put ZIP file in phone storage
2) Download latest Official TWRP, flash it via fastboot then hold "Power" and "Vol+" buttons (both) until TWRP is booted
3) Select OrangeFox ZIP file in TWRP and flash it (phone will automatically restart to OrangeFox Recovery).
4) Done! You can now flash latest Magisk version. ^^
Click to expand...
Click to collapse
Hey there. Thanks for this. Do I need to flash the VBMeta file also when I follow this? Would you mind sending a link to the latest official stuff, just wanna make sure I got the right things!
Annie the Eagle said:
Hey there. Thanks for this. Do I need to flash the VBMeta file also when I follow this? Would you mind sending a link to the latest official stuff, just wanna make sure I got the right things!
Click to expand...
Click to collapse
You normally don't need to flash VBMeta file.
- Official TWRP => https://dl.twrp.me/davinci/
- Latest OrangeFox (actually "R10.1_1" because "R10.1_2" is a broken version) => https://files.orangefox.tech/OrangeFox-Stable/davinci/
EDIT: Flash "R10.1_1" version over bad "R10.1_2" version if you already downloaded/flashed via my previous MEGA link.
Annie the Eagle said:
Hey
So my bootloader unlock wait time is coming up tomorrow, but this forum is not giving me much hope as all I can see is problems with TWRP constantly being replaced with the stock recovery and general incompatibility (recovery loops or bootloader loops), no one seems to know which of the 10,000 versions of TWRP and OrangeFox (????) recovery to use.
Can anyone clarify what the situation is with Xiaomi Mi 9T or is this phone doomed and its just worth throwing on eBay (a phone without custom recovery and root is absolutely worthless to me).
Thanks a plenty!
Click to expand...
Click to collapse
Sorry but this is not teally true - or maybe it's the case for custom roms and/or custom twrps
Using (not alone, you can find several peopke reporting the same):
-QFJEUXM 11m0.4.0 (Global, Stable,v Android 10)
-Official TWRP 3.3.1-0-davinci
Just flash that twrp through fastboot, do not wipe or fornat anything (vbmeta, internal storage, whatever), you will not loose anything and everything will work
And the same holds if twrp is replaced by orangefox (since recently, using R10.1_2)
Eg, when booting to twrp, you will enter your pin/password you use in system for unlocking the screen - and twrp will recognize and work with your encrypted Internal memory (so again, without formatting data, wiping vbmeta or whatever)
However, if you want to use some custom roms whose installation requires to format or wipe something, and/ot to use some custom twrps, that's another story (but not a problem in miui or in the official twrp)