This TWRP recovery is compiled from source & not official yet
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Prerequisites
1. Unlocked bootloader.
Bugs
1. No bugs
2. If you have found a bug, please consider posting it to my GitHub Issues.
Instructions
1. Go to the fastboot mode.
2. Download the recovery.img and transfer it to the adb folder.
3. Open the cmd/terminal and change directory into the adb folder.
4. Now confirm/check that device is connected by typing:-
Code:
fastboot devices
If you got your device seriel number there then you are ready to continue otherwise try connecting device again and make sure USB debugging is on and you have granted permission to the PC to debug.
5. After that we will flash this TWRP recovery to the recovery partition by below command:-
Code:
fastboot flash recovery twrp-name.img
BooM ! TWRP flashed successfully.
6. Now unplug your device and then hold power button untill the phone turned off,after that press power button while holding vol down(-) button simultaneously and you will boot into TWRP recovery mode.
Enjoy !
Downloads
Official TWRP Website : https://twrp.me/umidigi/onemax.html
GitHub Release : Here (release name : TWRP-UMIDIGI-One_Max)
Version Information
ROM OS Version: 8.1.x Oreo
Source Code: Device Tree
Based On: TWRP
Credits
Omni Team for minimal TWRP source
@chankruze (myself) for device tree and compilation.
SUPPORT
Official Telegram Group
Official Telegram Channel
Hey ! Good job ! I tried building my own TWRP today but then noticed someone already did it ! Does encryption work ? I cant seem to decrypt the partition after flashing your TWRP.
EDIT : Couldn't wait, ended up formatting with encryption disabled via a zip + magisk
I've then proceeded to flash some GSI for Android 9 (even tried Q Beta 3) and if we want 9.0 one day, some heavy work will be needed : Cellular doesn't work; other than that, it all seems fine to me, camera is only 12mpx, front is 13mpx. Haven't tested more, i'm back to stock
EDIT 2: After comparing camera from stock and gsi, GSI wins easily. The camera is not as slow as stock.
Are there any decent ROMs yet for this phone? LineageOS would be fantastic.
@kgoerbig not to my knowledge. Maybe I'll try porting a 9.0 GSI soon.
I'm not sure if this is helpful or not, but Umidigi posts stock ROM on there forum. Can ROMs be ported based on there code? Or is it more complicated then that?
https://community.umidigi.com/m/?a=viewthread&tid=18692
_cab13_ said:
Hey ! Good job ! I tried building my own TWRP today but then noticed someone already did it ! Does encryption work ? I cant seem to decrypt the partition after flashing your TWRP.
EDIT : Couldn't wait, ended up formatting with encryption disabled via a zip + magisk
I've then proceeded to flash some GSI for Android 9 (even tried Q Beta 3) and if we want 9.0 one day, some heavy work will be needed : Cellular doesn't work; other than that, it all seems fine to me, camera is only 12mpx, front is 13mpx. Haven't tested more, i'm back to stock
EDIT 2: After comparing camera from stock and gsi, GSI wins easily. The camera is not as slow as stock.
Click to expand...
Click to collapse
I have tested LineageOS 16.0 GSI Android 9.0 (and many others ...) and it works well, even GSM and Camera.
The only thing I cannot have is a complete root : I install Magisk 19.3 correctly, but applications cannot get root permission (Titanium Backup cannot have su permission)
Hi to all!!!
I've unlocked bootloader, flashed twrp in post but when I power Off and On+Vol - my device doesn't power up...
Also if I make fastboot reboot recovery, my device reboot in fastboot mode again...
What's wrong??? I would test Descendant_ThreeDotZero_arm64_aonly rom!!!!
Pls Help me!!!!
silviuss82 said:
Hi to all!!!
I've unlocked bootloader, flashed twrp in post but when I power Off and On+Vol - my device doesn't power up...
Also if I make fastboot reboot recovery, my device reboot in fastboot mode again...
What's wrong??? I would test Descendant_ThreeDotZero_arm64_aonly rom!!!!
Pls Help me!!!!
Click to expand...
Click to collapse
If you use the stock boot.img with an GSI system image, it will not boot, you must first flash Magisk.zip before reboot!
It will disable dm-verity, and you can boot after.
If it continue reboot in bootloader mode, use spflashtool to flash a stock rom and all will be right
Or if you have a TWRP backup, restore all partitions except boot/recovery/cache/system/data and you can boot
@ dreambo Can you make a writeup of properly unlocking the bootloader/rooting? Or did you use these methods?
https://community.umidigi.com/forum.php?mod=viewthread&tid=17376
https://www.youtube.com/watch?v=xM_M5XP--Z8&t=176s
I should be receiving my Umidigi One Max in a day or so, and do not want to bork anything up! I have SPflash installed both on a Win10 laptop, and on a Ubuntu Linux machine.
dreambo said:
If you use the stock boot.img with an GSI system image, it will not boot, you must first flash Magisk.zip before reboot!
It will disable dm-verity, and you can boot after.
If it continue reboot in bootloader mode, use spflashtool to flash a stock rom and all will be right
Or if you have a TWRP backup, restore all partitions except boot/recovery/cache/system/data and you can boot
Click to expand...
Click to collapse
kgoerbig said:
@ dreambo Can you make a writeup of properly unlocking the bootloader/rooting? Or did you use these methods?
https://community.umidigi.com/forum.php?mod=viewthread&tid=17376
https://www.youtube.com/watch?v=xM_M5XP--Z8&t=176s
I should be receiving my Umidigi One Max in a day or so, and do not want to bork anything up! I have SPflash installed both on a Win10 laptop, and on a Ubuntu Linux machine.
Click to expand...
Click to collapse
You do not need to unlock you phone, mine is rooted with Magisk and have TWRP installed without unlock bootloader.
Just use spflashtool to flash a stock rom, but replace the recovery by TWRP and the boot.img by magisk_patched.img one.
Here how I do exactly:
1- in my running stock rom, I install MagiskManager and install Magisk by choosing the last option (patch existing boot.img)
2- give it your stock boot.img (extracted from stock rom) and it create for you /sdcard/Download/magisk_patched.img
3- use this to replace your stock boot.img and use also TWRP.img to replace stock recovery.img and flash the whole rom with SPFlashTool
Can you backup with TWRP with a locked bootloader? Isn't write access blocked with a locked bootloader?
dreambo said:
You do not need to unlock you phone, mine is rooted with Magisk and have TWRP installed without unlock bootloader.
Just use spflashtool to flash a stock rom, but replace the recovery by TWRP and the boot.img by magisk_patched.img one.
Here how I do exactly:
1- in my running stock rom, I install MagiskManager and install Magisk by choosing the last option (patch existing boot.img)
2- give it your stock boot.img (extracted from stock rom) and it create for you /sdcard/Download/magisk_patched.img
3- use this to replace your stock boot.img and use also TWRP.img to replace stock recovery.img and flash the whole rom with SPFlashTool
Click to expand...
Click to collapse
kgoerbig said:
Can you backup with TWRP with a locked bootloader? Isn't write access blocked with a locked bootloader?
Click to expand...
Click to collapse
If you can run the TWRP with a locked bootloader (and you can in case of umidigi one max) you can do any thing
dreambo said:
If you can run the TWRP with a locked bootloader (and you can in case of umidigi one max) you can do any thing
Click to expand...
Click to collapse
One last question. =)
Which boot file from stock did you use to patch with?
Downloadable from: https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
UMIDIGI One Max V1.0
or
UMIDIGI One Max E V1.0
kgoerbig said:
One last question. =)
Which boot file from stock did you use to patch with?
Downloadable from: https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
UMIDIGI One Max V1.0
or
UMIDIGI One Max E V1.0
Click to expand...
Click to collapse
I have used the European one, UMIDIGI One Max E V1.0
So I just received my One Max today. I was able to patch the boot image, and root the phone. I also, installed TWRP, but I'm running into an issue. From TWRP, I formatted with a normal wipe, It asked "Do you want to do this, it wipes data encryption Etc". I typed yes, and it did it's thing. Rebooted. Setup my basic settings on the phone. I rebooted back into TWRP, and it immediatly asked for a "decryption" password. It also won't allow me to mount internal partitions or sdcard. This even after I rooted via a patched boot file, and verified root access while booted in android (with root verify app). What am I doing wrong for TWRP to gain access to storage?
"Couldn't wait, ended up formatting with encryption disabled via a zip + magisk"
How did you format without encryption? I try to format from TWRP, type 'yes' , to verify, and encryption is still active. I'd like to disable encryption, so that I can properly backup everything from TWRP.
kgoerbig said:
So I just received my One Max today. I was able to patch the boot image, and root the phone. I also, installed TWRP, but I'm running into an issue. From TWRP, I formatted with a normal wipe, It asked "Do you want to do this, it wipes data encryption Etc". I typed yes, and it did it's thing. Rebooted. Setup my basic settings on the phone. I rebooted back into TWRP, and it immediatly asked for a "decryption" password. It also won't allow me to mount internal partitions or sdcard. This even after I rooted via a patched boot file, and verified root access while booted in android (with root verify app). What am I doing wrong for TWRP to gain access to storage?
Click to expand...
Click to collapse
Search in xda forum a zip that you can flash with TWRP before installing the Magisk zip from TWRP.
its name is disable_dm_verity????.zip, it disable in the boot.img the encryption.
After that format the data partition (format and not wipe, it's important!) and reboot normally, and your data partition will not be encrypted
dreambo said:
Search in xda forum a zip that you can flash with TWRP before installing the Magisk zip from TWRP.
its name is disable_dm_verity????.zip, it disable in the boot.img the encryption.
After that format the data partition (format and not wipe, it's important!) and reboot normally, and your data partition will not be encrypted
Click to expand...
Click to collapse
I eventually found all the correct files to remove encryption. I also installed AOSP. I'm kind of torn between the stock and AOSP. AOSP has better performance, but one annoying aspect is that I cannot find anywhere in the settings to switch the navigation buttons in AOSP (Back button is on the far left, I like it on the right side). Seems trivial, but it's annoying. I can now fully backup & restore in TWRP, which makes life a lot easier.
kgoerbig said:
I eventually found all the correct files to remove encryption. I also installed AOSP. I'm kind of torn between the stock and AOSP. AOSP has better performance, but one annoying aspect is that I cannot find anywhere in the settings to switch the navigation buttons in AOSP (Back button is on the far left, I like it on the right side). Seems trivial, but it's annoying. I can now fully backup & restore in TWRP, which makes life a lot easier.
Click to expand...
Click to collapse
Which AOSP ? where do you found it ?
dreambo said:
Which AOSP ? where do you found it ?
Click to expand...
Click to collapse
This thread:
https://forum.xda-developers.com/android/development/umidigi-one-max-custom-rom-modding-t3942521
This Rom
https://github.com/phhusson/treble_experimentations/releases
Do a complete backup of stock from TWRP onto microsd or USB first! System, data, modem, nvram partitions etc. That way you can restore from TWRP, and not lose os, data, or nvram (IMEI).
Specifically, system-arm64-aonly-gapps-su.img.xz
1. Download and extract file you downloaded, onto your phone.
2. Do a format (type yes)
3. Install from TWRP as "image".
Related
Hi. I'm here for help you
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Click to expand...
Click to collapse
1) How to install? If you have stock zenui go to 1C, if you have a custom ROM go to 1A
If you don't backup all your data you lost all.
1A) First do a TWRP backup on sdcard (if you don't have sdcard just do in internal storage and save the backup on pc. Select system, data, recovery and boot. Then go to wipe - advanced wipe, select dalvik, system, data, cache and Swype.
Then reboot in fastboot.
Now your phone don't have any OS installed so don't boot. We are going to install the stock and unmodified firmware and recovery on the phone.
1B) Download Asus flashtool:
https://drive.google.com/file/d/0B9rp3AJHKJXjNmRuRUJMWmtOT3c/view
and android 7 raw firmware for
ZE552KL:
http://www.mediafire.com/file/o12vo...14.2020.1703.28_M3.10.47.3_Phone-user.raw.zip
ZE520KL: http://www.mediafire.com/file/5qrp2...14.2020.1703.28_M3.10.47.3_Phone-user.raw.zip
Now boot your phone in fastboot, connect to pc, install and open Asus flash tool, select raw file and device model and flash the firmware. If the pc don't detect your phone install the drivers.
1C) Download from Asus site the latest nougat update:
WARNING: IF YOU OPEN THE ZIP FILE THE RECOVERY FAIL TO UPDATE
And you must delete this zip and download another
ZE552KL: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE552KL/UL-ASUS_Z012D-WW-14.2020.1712.85-user.zip
ZE520KL:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE520KL/UL-ASUS_Z017D_1-WW-14.2020.1712.85-user.zip
Put in device storage and wait the device to detect the update. Tap on notification and install. If fail try in order:
-put in sdcard and update via STOCK recovery
-sideload the file from your PC via adb
-download the file with another browser and delete the previous
After that, so the same with Android 8.0 update
ZE552KL: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE552KL/UL-ASUS_Z012D-WW-15.0410.1712.31-user.zip
ZE520KL: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE520KL/UL-ASUS_Z017D_1-WW-15.0410.1712.31-user.zip
2) Flash recovery
I know there are another method to flash a recovery but this method is simply:
2A) Download twrp from this thread:
https://forum.xda-developers.com/zenfone-3/development/recovery-twrp-3-2-1-ze520kl-ze552kl-t3742765
Download Zenfone 3 toolkit from this thread:
https://forum.xda-developers.com/zenfone-3/how-to/tool-zenfone-3-one-click-tool-t3507417
2B) Unpack and go to zenfone3_clictool/twrp folder. Delete both recoveries and put the 3.2.1 twrp in folder. If you have ZE552KL rename with " twrp-3.0.2-Z012D ", if you have ZE520KL rename with " twrp-3.0.2-Z017D ". Now boot your phone in fastboot, connect to pc and open the Zenfone 3 click tool, follow the instructions and select flash twrp for your device. Reboot your phone in recovery and see if can read internal storage. If read 0B try another time.
3) Rooting is so simple. Just download Magisk
boot in twrp and flash
Xposed work well, I tested only gravitybox
Substratum works... Meh
Reserved
ExperienceTesla said:
2) Flash recovery
I know there are another method to flash a recovery but this method is simply:
2A) Download twrp: https://www.dropbox.com/s/r9o4a3elbgvg6rj/twrp-3.2.1-0-Z012-20171220-oreotest.img?dl=1
Download Zenfone 3 toolkit from this thread:
https://forum.xda-developers.com/zenfone-3/how-to/tool-zenfone-3-one-click-tool-t3507417
2B) Unpack and go to zenfone3_clictool/twrp folder. Delete both recoveries and put the 3.2.1 twrp in folder. If you have ZE552KL rename with " twrp-3.0.2-Z012D ", if you have ZE520KL rename with " twrp-3.0.2-Z017D ". Now boot your phone in fastboot, connect to pc and open the Zenfone 3 click tool, follow the instructions and select flash twrp for your device. Reboot your phone in recovery and see if can read internal storage. If read 0B try another time.
Click to expand...
Click to collapse
Great job!
However, I have a question. TWRP you mention to in 2A's version is 3.0.2 or 3.2.1?
I'm sorry that my English is bad.
So, just to be sure, I'm currently on ViperOS, I need to follow from 1A step, right? Or anything before that I have to do first?
nyanntaryou said:
Great job!
However, I have a question. TWRP you mention to in 2A's version is 3.0.2 or 3.2.1?
I'm sorry that my English is bad.
Click to expand...
Click to collapse
Is 3.2.1 . It's a beta TWRP so may have some bug. But basic functions works
tkhquang said:
So, just to be sure, I'm currently on ViperOS, I need to follow from 1A step, right? Or anything before that I have to do first?
Click to expand...
Click to collapse
Yes. You need to follow whole thread: first start with backup, save backup to pc, flash stock ecc ecc
ExperienceTesla said:
Is 3.2.1 . It's a beta TWRP so may have some bug. But basic functions works
Click to expand...
Click to collapse
Can it work on both ze520kl and ze552kl?
Thank you in advance for your kind cooperation.
nyanntaryou said:
Can it work on both ze520kl and ze552kl?
Thank you in advance for your kind cooperation.
Click to expand...
Click to collapse
No, it doesn't work on the ZE520KL.
As oreo is finally available on this phone I'll also build a new twrp version for it
(If anyone is wondering: I posted OP's twrp some time ago in the oreo beta leak thread here)
Stay tuned...
planet9 said:
No, it doesn't work on the ZE520KL.
As oreo is finally available on this phone I'll also build a new twrp version for it
(If anyone is wondering: I posted OP's twrp some time ago in the oreo beta leak thread here)
Stay tuned...
Click to expand...
Click to collapse
Thank you for the great work!
The ZE552KL TWRP works fine for flashing the Magisk at my ZE520KL but not much else
I can't wait to get a proper TWRP for my ZE520KL
Will this also work for Z012DC (Canadian 5.5" Zenfone3)? I'm running WW_14.2020.1709.68 with TWRP and rooted, would I start from 1A or 1C?
rdmozero said:
Thank you for the great work!
The ZE552KL TWRP works fine for flashing the Magisk at my ZE520KL but not much else
I can't wait to get a proper TWRP for my ZE520KL
Click to expand...
Click to collapse
Is there any issues when you flashed twrp on your phone ze520kl?
rdmozero said:
Thank you for the great work!
The ZE552KL TWRP works fine for flashing the Magisk at my ZE520KL but not much else
I can't wait to get a proper TWRP for my ZE520KL
Click to expand...
Click to collapse
I really didn't expect this to work - there's always something new to learn
mecoromeo said:
Is there any issues when you flashed twrp on your phone ze520kl?
Click to expand...
Click to collapse
You can find the proper twrp version for your devices here:
https://forum.xda-developers.com/zenfone-3/development/recovery-twrp-3-2-1-ze520kl-ze552kl-t3742765
Ok, so I flash TWRP recovery and everything is OK, but, When I start the phone, it goes to bootloop...What should I do? Am I missing a step?
@Kevinxdfun29
Flash magisk, supersu binary or the no verify file if you don't want root. Then wipe cache and dalvik .
ExperienceTesla said:
Hi. I'm here for help you
1) How to install? If you have stock zenui go to 1C, if you have a custom ROM go to 1A
If you don't backup all your data you lost all.
1A) First do a TWRP backup on sdcard (if you don't have sdcard just do in internal storage and save the backup on pc. Select system, data, recovery and boot. Then go to wipe - advanced wipe, select dalvik, system, data, cache and Swype.
Then reboot in fastboot.
Now your phone don't have any OS installed so don't boot. We are going to install the stock and unmodified firmware and recovery on the phone.
1B) Download Asus flashtool:
https://drive.google.com/file/d/0B9rp3AJHKJXjNmRuRUJMWmtOT3c/view
and android 7 raw firmware for
ZE552KL:
http://www.mediafire.com/file/o12vo...14.2020.1703.28_M3.10.47.3_Phone-user.raw.zip
ZE520KL: http://www.mediafire.com/file/5qrp2...14.2020.1703.28_M3.10.47.3_Phone-user.raw.zip
Now boot your phone in fastboot, connect to pc, install and open Asus flash tool, select raw file and device model and flash the firmware. If the pc don't detect your phone install the drivers.
1C) Download from Asus site the latest nougat update:
WARNING: IF YOU OPEN THE ZIP FILE THE RECOVERY FAIL TO UPDATE
And you must delete this zip and download another
ZE552KL: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE552KL/UL-ASUS_Z012D-WW-14.2020.1712.85-user.zip
ZE520KL:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE520KL/UL-ASUS_Z017D_1-WW-14.2020.1712.85-user.zip
Put in device storage and wait the device to detect the update. Tap on notification and install. If fail try in order:
-put in sdcard and update via STOCK recovery
-sideload the file from your PC via adb
-download the file with another browser and delete the previous
After that, so the same with Android 8.0 update
ZE552KL: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE552KL/UL-ASUS_Z012D-WW-15.0410.1712.31-user.zip
ZE520KL: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE520KL/UL-ASUS_Z017D_1-WW-15.0410.1712.31-user.zip
2) Flash recovery
I know there are another method to flash a recovery but this method is simply:
2A) Download twrp: https://www.dropbox.com/s/r9o4a3elbgvg6rj/twrp-3.2.1-0-Z012-20171220-oreotest.img?dl=1
Download Zenfone 3 toolkit from this thread:
https://forum.xda-developers.com/zenfone-3/how-to/tool-zenfone-3-one-click-tool-t3507417
2B) Unpack and go to zenfone3_clictool/twrp folder. Delete both recoveries and put the 3.2.1 twrp in folder. If you have ZE552KL rename with " twrp-3.0.2-Z012D ", if you have ZE520KL rename with " twrp-3.0.2-Z017D ". Now boot your phone in fastboot, connect to pc and open the Zenfone 3 click tool, follow the instructions and select flash twrp for your device. Reboot your phone in recovery and see if can read internal storage. If read 0B try another time.
3) Rooting is so simple. Just download Magisk
boot in twrp and flash
Xposed work well, I tested only gravitybox
Substratum works... Meh
Click to expand...
Click to collapse
My phone is now WW-15.0410.1712.31
I cant sure that my phone will boot or not after flashed twrp. So I go to fastboot mode, and boot into twrp by command:
fastboot boot twrp-3.2.1-0-Z012-20171220-oreotest.img
downloading 'boot.img'...
OKAY [ 0.786s]
booting...
But nothing happens, my phone still in fastboot mode.
I can boot into twrp with beta oreo previously released.
I think that twrp is not compatible with official oreo now.
sontranngoc said:
My phone is now WW-15.0410.1712.31
I cant sure that my phone will boot or not after flashed twrp. So I go to fastboot mode, and boot into twrp by command:
fastboot boot twrp-3.2.1-0-Z012-20171220-oreotest.img
downloading 'boot.img'...
OKAY [ 0.786s]
booting...
But nothing happens, my phone still in fastboot mode.
I can boot into twrp with beta oreo previously released.
I think that twrp is not compatible with official oreo now.
Click to expand...
Click to collapse
Try install recovery following the instructions in first post. Worked for me
If the "zenfone3 clicktool" method not work try
fastboot flash recovery twrp-3.2.1-0-Z012-20171220-oreotest.img
So reboot in recovery and give me a feedback
ExperienceTesla said:
Try install recovery following the instructions in first post. Worked for me
If the "zenfone3 clicktool" method not work try
fastboot flash recovery twrp-3.2.1-0-Z012-20171220-oreotest.img
So reboot in recovery and give me a feedback
Click to expand...
Click to collapse
Yes. I flashed the twrp successfully. But I cant boot into twrp without flashed it. I need to backup the latest stock recovery, in order to flash a new stock rom in future.
i got bootloop after trying to reboot my phone from twrp recovery. wtf
Flat Bar Indicator
w1040 said:
i got bootloop after trying to reboot my phone from twrp recovery. wtf
Click to expand...
Click to collapse
When does Android 8.0 support the Flat Bar Indicator module?
dzunghooca said:
When does Android 8.0 support the Flat Bar Indicator module?
Click to expand...
Click to collapse
Wrong thread bro
/* *** Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* if you have any concerns about features included in this ROM/KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point your finger at me for messing up your device, I will laugh at you.
* BOOM! goes the dynamite
*/
I have a Moto E5 plus XT1924-5 (rhannah) in my possession. It is the only device in which this guide has been tested. I should serve for the rest of the rhannah and others moto e5 without problems.
My cust LATAM and the compilation version is OPP27.91-25. Do not make the fast route if you do not have exactly the same device with that same compilation number or if you do not know exactly what you are doing.
The guide is divided into parts. First how to backup everything. Then how to root with magisk (for that there is fast and slow way)
What do you need.
- 1 Moto e5 Plus
- 1 Micro Sd card (minimum 4gb)
- Usb Cable
- Adb and fastboot drivers installed
-. Read the complete guide before to understand what they are doing (5 minutes, no bricks)
- 1 Brain.
- Comprehensive reading
FIRST STAGE (COMMON). BACKUP OF EVERYTHING.
Our phone have its own TWRP, works relatively well, except that it does not allow decrypting and therefore mounting the data partition and internal storage.
The steps.
1.- You open the bootloader. Look at any guide to open bootloader in Motorola, it has not science and is common for all motorala phones
2.- Download the Moto e5 play (james) TWRP (https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323)
3.- We put the phone in fastboot. For this, we activate the USB debugging and with the connected phone we write in a CMD "adb reboot-bootloader"
4.- In fastboot we write in our CMD "fastboot boot twrp_james.img". This will start our phone in TWRP without permanently flashing the recovery (for no reason to flash it)
5.- The recovery will take something to start and it will ask us for our key to decrypt data. We need to press cancel as the recovery will fail even with the correct key. DONT MOUNT SYSTEM WITH RW PERMISSION
6.- Go to the backup section, we choose as our destination SD and we backup
ALL except data and cache.
7.- Restart the cell phone and we put our backup in one or more safe place (the misfortunes happen)
With this we already have a backup of boot and system so we will not have problems if we make mistakes later
SECOND STAGE (THE DIFFICULT ROUTE) Patching our own boot.img for magisk
1.- In android we download and install he last magisk manager APK (available in my google drive account https://drive.google.com/open?id=1XD7Q7NXmchTNsSJ-oqt2TOXO8osroVJp)
2.- We open it, we go to setting and in "Update Channel" we activate the beta channel of updates (THE DEVICE WILL ENTER IN BOOTLOOP WITHOUT WITHOUT THIS STEP)
3.- In the main screen of magisk we are going to install, we accept to install the version of magisk 16.7 or superior (by no reason a lower one) and we go to "Patch boot image file", we select the file boot.emmc.win of our backup and We wait for you to patch our boot. (sdcard/TWRP/ Backups /ZL5223F3V8 / DATE /)
4.- Magisk will generate a patched boot in /internalstorage/MagiskManager/patched_boot.img
5.- Copy patched_boot.img to our computer, put the phone in fastboot mode and flash the patched_boot.img with the command fastboot flash boot patched_boot.img, and later restart the phone.
Ready!. Magisk perfectly installed our phone. In my case, safety.net passes without problems.
Second stage. (The easy way). SAFE ONLY in the variants indicated
0- Open bootloader
1.- Make the backups (iam not responsable of this)
2.- put the phone in fastboot mode
3.- Flash my boot.img patched for magisk "fastboot flash boot patched_boot.img"
Moto e5 plus XT1924-5 OPP27.91-25
https://drive.google.com/file/d/1XHtV1rI1cDPQCAw8otuBRxeSzNBzKWQn/view?usp=sharing
Moto e5 plus XT-1924-8 (Thanks Arslan_Rulex)
http://www.mediafire.com/file/zu9mefxd397nr1f/patched_boot.img/file
Moto e5 plus XT1924-7 (MetroPCS) (Thanks theUsualSuspexx)
https://drive.google.com/open?id=1UzP5NEBLD3_ex_zU2EoijVFs1uiGBEMI
Backups TWRP
Moto e5 plus rhannah xt1924-5 (OPP27.91-25.) Include twrp backup of rooted boot partition with system partition, and untouched boot partition (separated)
https://drive.google.com/open?id=1Vu0CvgBc0QeSxWOLyRgcMykvJ9ckgQy_
I hope you send yours, since there is only one fastboot image for this phone.
Thanks a lot, now im root in my e5 plus OPP27.91-41, via THE DIFFICULT ROUTE. the easy route give me a softbrick, :highfive:
folken2003 said:
Thanks a lot, now im root in my e5 plus OPP27.91-41, via THE DIFFICULT ROUTE. the easy route give me a softbrick, :highfive:
Click to expand...
Click to collapse
What rom are you using bike friend e5?
Rodneyy said:
What rom are you using bike friend e5?
Click to expand...
Click to collapse
the stock rom
In case I want to download and install an OTA update, is it possible to undo this by uninstalling Magisk (and its modules, Exposed, etc.) and reinstall the old boot.img via TWRP? Or would that brick the device?
Hinterecke said:
In case I want to download and install an OTA update, is it possible to undo this by uninstalling Magisk (and its modules, Exposed, etc.) and reinstall the old boot.img via TWRP? Or would that brick the device?
Click to expand...
Click to collapse
In theory, reinstalling your unmodified stock boot image will remove all traces of systemless root. On OTA installations with most Moto devices, the update.zip performs a number of checksums in order to verify that certain partitions are unaltered. Your /recovery, /boot, /system, /oem, and /vendor partitions are typically included in these checksums. Even if these partitions have never been altered, an OTA will nevertheless fail if any of the aforementioned partitions have ever been mounted as r/w, even if they were not altered or modified. So, if you've ever mounted any of these partitions as r/w via TWRP, your OTA will fail, but the likelihood of a brick is extremely slim. The best way to prepare your device for an OTA is to flash a full factory firmware package via fastboot or RSD Lite. RELOCKING THE BOOTLOADER IS NEVER NECESSARY ON A MOTO DEVICE FOR INSTALLING AN OTA UPDATE.
Alternatively, you may use a UTF-8 encoding capable file editor to remove checksums from your captured OTA package. Then, you can flash it with TWRP even on a rooted device.
So to fully answer your question, you would want to install stock recovery and boot image via fastboot, not TWRP, since the OTA will fail with a custom recovery. The OTA will need to be installed via stock recovery, not TWRP.
I used @avilav 's rooting method he described over here and didn't install TWRP because it would be useless, I actually read the big warning, so still on stock recovery.
Don't have the factory firmware for my rhannah XT-1924-1 (reteu) either so flashing that is not much of an option. Maybe I should just leave it this way cause most MOTO updates, for the cheaper devices, are mostly just security updates, no new features, software, etc.
MotoJunkie01 said:
In theory, reinstalling your unmodified stock boot image will remove all traces of systemless root. On OTA installations with most Moto devices, the update.zip performs a number of checksums in order to verify that certain partitions are unaltered. Your /recovery, /boot, /system, /oem, and /vendor partitions are typically included in these checksums. Even if these partitions have never been altered, an OTA will nevertheless fail if any of the aforementioned partitions have ever been mounted as r/w, even if they were not altered or modified. So, if you've ever mounted any of these partitions as r/w via TWRP, your OTA will fail, but the likelihood of a brick is extremely slim. The best way to prepare your device for an OTA is to flash a full factory firmware package via fastboot or RSD Lite. RELOCKING THE BOOTLOADER IS NEVER NECESSARY ON A MOTO DEVICE FOR INSTALLING AN OTA UPDATE.
Alternatively, you may use a UTF-8 encoding capable file editor to remove checksums from your captured OTA package. Then, you can flash it with TWRP even on a rooted device.
So to fully answer your question, you would want to install stock recovery and boot image via fastboot, not TWRP, since the OTA will fail with a custom recovery. The OTA will need to be installed via stock recovery, not TWRP.
Click to expand...
Click to collapse
+1 .If you never mount system rw before backup you should not have problems. It is not necessary to do it with this way of rooting, and in theory if you make a backup system-image you should not have problems , since that is a bit-by-bit backup
help me
folken2003 said:
Thanks a lot, now im root in my e5 plus OPP27.91-41, via THE DIFFICULT ROUTE. the easy route give me a softbrick, :highfive:
Click to expand...
Click to collapse
como lo hiciste?
mickeynews said:
como lo hiciste?
Click to expand...
Click to collapse
RTFM
I have the Boost Mobile (Sprint) version which shows as XT1924-8 in the Hardware tab in settings. It has the Snapdragon 435 1.4Ghz octacore w/ 3GB ram 32GB rom. I was able to follow these steps to unlock the bootloader, fastboot into TWRP, did a backup, install magisk manager, patch the boot image and then flash it via fastboot. I might try to get unltd tethering working but for now WOOOOOO-HOOOOOO, this was a rush!
reaper-death said:
I have the Boost Mobile (Sprint) version which shows as XT1924-8 in the Hardware tab in settings. It has the Snapdragon 435 1.4Ghz octacore w/ 3GB ram 32GB rom. I was able to follow these steps to unlock the bootloader, fastboot into TWRP, did a backup, install magisk manager, patch the boot image and then flash it via fastboot. I might try to get unltd tethering working but for now WOOOOOO-HOOOOOO, this was a rush!
Click to expand...
Click to collapse
That's excellent news. You are encouraged to start a rooting tutorial thread for the xt1924-8. By the way, upload me a system image and boot image from a TWRP backup of your device and I'll compile a TWRP flashable stock ROM for the device.
MotoJunkie01 said:
That's excellent news. You are encouraged to start a rooting tutorial thread for the xt1924-8. By the way, upload me a system image and boot image from a TWRP backup of your device and I'll compile a TWRP flashable stock ROM for the device.
Click to expand...
Click to collapse
Sure, I'm uploading the files to mediafire and should be up in a little while.
As for the tutorial basically I did ALMOST everything. I didn't flash twrp and I didn't flash noverity. I did get stuck with no boot when I flashed the patched boot img but figured it out (update channel wasn't set to beta). To fix that boot issue I restarted back to the bootloader then booted twrp and then restored just my boot image from the backup. Then I did the magisk patching and then flashed it and this time I got root.
reaper-death said:
Sure, I'm uploading the files to mediafire and should be up in a little while.
As for the tutorial basically I did ALMOST everything. I didn't flash twrp and I didn't flash noverity. I did get stuck with no boot when I flashed the patched boot img but figured it out (update channel wasn't set to beta). To fix that boot issue I restarted back to the bootloader then booted twrp and then restored just my boot image from the backup. Then I did the magisk patching and then flashed it and this time I got root.
Click to expand...
Click to collapse
Ok. Got it. You basically followed standard protocol based on the tutorial for other variants.
Cool. Once you get me the files I should be able to cook up the ROM and post sometime tomorrow. Thanks for your efforts and your feedback. This will help other members with your variant.
Ok, here is the link:
http://www.mediafire.com/?6862xg60zi8ai
Edit: I also was able to pull the stock recovery img using the XDA TWRP app in android.
c̶a̶n̶ ̶s̶o̶m̶e̶o̶n̶e̶ ̶p̶l̶e̶a̶s̶e̶ ̶u̶p̶l̶o̶a̶d̶ ̶t̶h̶e̶ ̶m̶e̶t̶r̶o̶p̶c̶s̶ ̶o̶r̶ ̶t̶ ̶m̶o̶b̶i̶l̶e̶ ̶T̶W̶R̶P̶ ̶b̶a̶c̶k̶u̶p̶?̶ ̶t̶h̶a̶n̶k̶s̶
hi how do you install the twrp backup you posted
seantello97 said:
hi how do you install the twrp backup you posted
Click to expand...
Click to collapse
Just like any twrp backup. Put it in your twrp/backups/*your phone's serial number*/*put backup here*
Stuck in bootloader
Hi thanks for that. I flashed Magisk on my e5 plus and rebooted but it takes me to bootloader every time. any ideas?
Hi the boot.img isn't showing up where i put it
First version shared was twrp 3.2
New version is 3.3.0
***ORIGINAL TWRP is not my work. Only the porting of it to this device. I take no credit for the source.
*** DISSCLAIMER ALLERT***
I started having issues with encryption coming back to enforcing when using the Ported Team LR TWRP 3.3
Did not have trouble yet with OMFG-Mod version.
Also @ghost45 has made a build of twrp 3.3.1 for F1. It works good as well
https://forum.xda-developers.com/showpost.php?p=79651368&postcount=49
--- all versions give trouble of loosing IMEI when using the remove force encryption patch I suggest below. Left logs with @Zackptg5 .
**May need more testing**
-decryption is broken
-MTP is working
-ADB is working
****--Advanced menu items are not correctly on 3.2 version.
-- Some of the advanced menu was fixed in 3.3.(install root is working)
- Advanced menu has extra features.(all from source twrp)
-- install magisk (currently has V17 on OMFG V19 on LR TEAM)
-- patch dm-verity and force encrypt remove.zip. ( personally I prefer the universal dm-removal patch from xda)
-- Remove system password, (from original dev, I have not tested)
--
--Install (basic directions only)--details may be added later if needed
Open zip and fastboot flash the recovery image if bootloader is unlocked.
or
Open zip , then open scatterfile (scatter file in test 1 has issue, updating it in next test )with sp-flashtool , select download
--First boot into TWRP will give errors for unable to mount /data. This is from the force-encryption.
- When boot into TWRP, select wipe -> format type 'yes' to format data
- When format is done, return to TWRP home page, select reboot -. recovery
--Now Patch device so no longer forces encryption
-- Use built in feature from 'Advanced Menu' or use the following directions--Fails to unpack boot. (current zip used is not compatible with system-as-root boot.img)
-To remove this I use 'Disable_Dm-Verity_ForceEncrypt' from
-- https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt -- currently based on magisk V19.2
-Download from the "Clone or Download" button on the above linked Github Page.
-Unzip the downloaded file. You will have a folder with same name as the zip package. Browse inside this folder, select all files and zip them.
-Put this new zip file onto your phone. ( Hay notice the MTP function on this TWRP works)
- in stall the zip like any normal twrp package.
--Next Install Magisk
--Use Built in Root Option from 'Advanced Menu' to use Magisk V19 or the following direction
- Goto the releases page of magisk github page. ==>LINK
- Download latest Magisk zip , Put file to phone, Install.
-- Download Folder For TWRP Ported from OMFG-Mod
https://www.androidfilehost.com/?w=files&flid=294886
-Screenshots.
- Ported OMFG-MOD gold Button TWRP V3.2
- Ported Team LR TWRP 3.3 standard Button
Attached Below
--Thanks --Mentions
recovery source from [LR TEAM] MIUI
http: //www.miui.com/forum.php?mod=viewthread&tid=19006123&page=1&mobile=2#pid257831639
link is newer version from ported recovery. They updated recently. Next port may use newer base as well.
hello @ColtonDRG. Long time.
I see you posted in umidigi forum that bootloader is not checking signature. So you CAN flash images with flashtool without unlocking. Is that correct.?
I have based the above install guide on that fact that you CAN.
But the first twrp posted by "ghost45" says no it must be unlocked.
edit:
I should be able to verify later today or this weekend, when my order arrives.
OK, verified, when i used flash tool and put twrp on phone before unlocking bootloader, on reboot I was stuck in "RED" status for boot loader. So must unlock
Flash this zip to remove the AdupsFota app
this is the update app. You will not be able to install OTA when rooted and twrp anyway, And if an OTA comes you will get stuck in recovery bootloop. So this flash file will rename the 2 apk related to OTA download and Force reboot that supposed to install that update.
Reserved
Will keep this post for working on issues .
Right now , I discovered after playing with the built in dm verity patch and root install lead imei's getting erased.
Restored the full rom with flash tool fixed, will update process as necessary
Restarted from the top again.
--1 Full stock rom flashed with sp flash tool.
--2 Twrp flashed in flash tool
--3 format /data, reboot recovery
--4 use mtp to copy Disable_Dm-Verity_Forceencrypt to phone
--5 flash the decrypt zip. And at the end of flash the output log showed 'failed to mount /nvdata file not exist'
*** Waiting for input from the Patch dev. Others on his xda thread with MTK have had similar trouble***
--6 use mtp , put stock recovery file on phone. Image flash stock recovery, reboot recovery, do factory reset in stock recovery. This fixed the /nvdata error.
--7 sp flash twrp again, use built in 'install root' option from advanced menu.
Bam all done
New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file
ghost45 said:
New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file
Click to expand...
Click to collapse
Thank you, this one has no displayed errors.
I have question though.
Do you know how to make system be mounted as /system instead of /system/system ?
Hey, buddy. Good to see you on the forums again. When I picked up this device I wondered if anyone from the R1 HD days would also be on it. I seem to have misplaced mine but I'll find it eventually, send me a DM if you wanna talk about it. I'm not 100% sure about this, but the bootloader verifying signatures might have been patched in because I don't remember mine doing that when they first came out. Of course even if it does, SPFT is still useful for unbricking and downgrading, but I really doubt UMIDIGI will patch out the unlock option like BLU did.
Hello again, all. I've been working on my UMIDIGI F1 again and after flashing the most recent firmware update using SPFT and trying to flash TWRP again I realized that something that changed in the latest firmware update has broken all of the existing TWRP images. Now the bootloader screen hangs for a while, sometimes a green bar appears at the top of the screen briefly, and then the phone reboots into Android. It is perhaps worth noting that when I tried to flash the upgrade in download only mode it just complained about the partition layout or something like that and then bailed, telling me to use the Format and Download option instead. I didn't do that because UMIDIGI told me not too and instead opted to try the Firmware Update option, which did work. I'm going to try to downgrade (hopefully I don't get bricked from downgrading preloader, efuses, etc) but I am a bit concerned about what has changed. Stock recovery still boots OK so it would seem to me that the bootloader isn't just completely borked, but either way it's a bit alarming that an OTA caused the custom recoveries we have to go kerplooie.
ColtonDRG said:
Hello again, all. I've been working on my UMIDIGI F1 again and after flashing the most recent firmware update using SPFT and trying to flash TWRP again I realized that something that changed in the latest firmware update has broken all of the existing TWRP images. Now the bootloader screen hangs for a while, sometimes a green bar appears at the top of the screen briefly, and then the phone reboots into Android. It is perhaps worth noting that when I tried to flash the upgrade in download only mode it just complained about the partition layout or something like that and then bailed, telling me to use the Format and Download option instead. I didn't do that because UMIDIGI told me not too and instead opted to try the Firmware Update option, which did work. I'm going to try to downgrade (hopefully I don't get bricked from downgrading preloader, efuses, etc) but I am a bit concerned about what has changed. Stock recovery still boots OK so it would seem to me that the bootloader isn't just completely borked, but either way it's a bit alarming that an OTA caused the custom recoveries we have to go kerplooie.
Click to expand...
Click to collapse
There is a newer twrp that has been released on 4pda.net that supposed to work on newest firmware release.
And downgrading with flashtool should work. Again need to use firmware upgrade option.
mrmazak said:
There is a newer twrp that has been released on 4pda.net that supposed to work on newest firmware release.
And downgrading with flashtool should work. Again need to use firmware upgrade option.
Click to expand...
Click to collapse
Downgrading worked. I couldn't find the newer TWRP version you were referring to and the website you mentioned redirects to a bunch of scammy crap.
ColtonDRG said:
Downgrading worked. I couldn't find the newer TWRP version you were referring to and the website you mentioned redirects to a bunch of scammy crap.
Click to expand...
Click to collapse
We have the twrp file copied to telegram group also. I'm stuck on mobile, or I would just copy the twrp here.
UMIDIGI
UMIDIGI unofficial TG group
https://t.me/UMIDIGI
Disable_Dm-Verity_ForceEncrypt failed
Hello, I'm trying to patch my F1 using the Disable_Dm-Verity_ForceEncrypt, but am stuck with an error "Dumping/splitting image failed. Aborting..." This occurs when I try using the Install from twrp. Has anyone encountered this issue before? I have done a wipe, and also tried installing Magisk (which installs fine).
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery
3. Latest adb & fastboot files
4. Stock ROM ZIP files
5. Stock Recovery [OPTIONAL]
Custom Recovery Method:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_*.zip /sdcard or MTP
3. Wipe data, cache & dalvik (format data if stuck at boot animation)
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip. Your device will have Stock Recovery with Stock ROM. Finally Reboot.
Fastboot Method:
Note: Following process formats internal storage, so backup the internal storage files. If your device is in Stock ROM & somehow system partition is messed up just flash only system.
1. Download required Fastboot files
2. If downloaded 7z files, extract system.img file.
3. Enter
Code:
fastboot -w && fastboot erase system && fastboot flash recovery recovery.img && fastboot flash boot boot.img && fastboot flash vbmeta vbmeta.img && fastboot flash dtbo dtbo.img && fastboot flash system system.img && fastboot reboot
4. It takes a while to flash System partition, have patience.
5. Device reboots to system if everything is flashed successfully.
Stock Recovery Method:
1. Download Stock ROM OZIP Files & Stock Recovery
2. Copy *.ozip to sdcard or internal storage.
2. Goto fastboot & enter fastboot flash recovery recovery.img
3. Reboot to recovery, wipe (1st option). Then go back to main menu Install from storage locate the *.ozip file & install.
I'm sorry, but this doesn't work for me..stuck with the rooted but uninstalled magisk OS.. :'(
ceesiama said:
I'm sorry, but this doesn't work for me..stuck with the rooted but uninstalled magisk OS.. :'(
Click to expand...
Click to collapse
zip isn't installed successfully? can you also send screenshot, so I can help you.
4j17h said:
zip isn't installed successfully? can you also send screenshot, so I can help you.
Click to expand...
Click to collapse
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
ceesiama said:
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
Click to expand...
Click to collapse
ok no problem, so what do you want to know about? Clear data, cache, dalvik after or before flashing stock zip it won't bootloop. Yes, since device is decrypted lock screen doesn't work. Coming to Magisk, yes that method is not reliable. I have figured out 100% working way which works for everyone & doesn't fail anytime. Maybe I will make a new guide soon or ...Mod edit: Link to Telegram removed
4j17h said:
ok no problem, so what do you want to know about? Clear data, cache, dalvik after or before flashing stock zip it won't bootloop. Coming to Magisk, yes that method is not reliable. I have figured out 100% working way which works for everyone & doesn't fail anytime. Maybe I will make a new guide soon or ...Mod edit: Link to Telegram removed
Click to expand...
Click to collapse
I'm sorry I mistyped in the above comment, when i followed your method, zip installed successfully but it bootlooped into stock recovery everytime. I hope that clarifies a bit. I''ll be very grateful if you can help me..
ceesiama said:
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
Click to expand...
Click to collapse
Try install magisk manager, maybe ur device still rooted
haditriw said:
Try install magisk manager, maybe ur device still rooted
Click to expand...
Click to collapse
no that's not how magisk works in Realme 3 Pro, if device is restarted there will be no magisk. You need to goto fastboot then goto recovery, it boots to system. We have magisk. Yes this method tricky. I am going to publish new guide, it will be simple & straight forward.
Bricked/ Bootlooping
4j17h said:
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery or Pitch Black Recovery
3. Latest adb & fastboot files
4. Stock ROM zip files: RMX1851_A15
5. Stock Recovery [OPTIONAL]
Follow the below steps:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_A15.zip /sdcard or MTP
3. Wipe data, cache & dalvik
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip, Reboot to System. You get the stock Recovery & stock ROM.
Previous Firmware: RMX1851_A14 Google Drive || AndroidFileHost || Mega Cloud storage
Note: This guide will be updated in coming days with fastboot flash files & custom recovery flashable files with latest versions.
Click to expand...
Click to collapse
pls help me, im stuck on bootlooop :'(
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
4j17h said:
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery or Pitch Black Recovery
3. Latest adb & fastboot files
4. Stock ROM zip files: RMX1851_A15
5. Stock Recovery [OPTIONAL]
Follow the below steps:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_A15.zip /sdcard or MTP
3. Wipe data, cache & dalvik
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip, Reboot to System. You get the stock Recovery & stock ROM.
Previous Firmware: RMX1851_A14 Google Drive || AndroidFileHost || Mega Cloud storage
Note: This guide will be updated in coming days with fastboot flash files & custom recovery flashable files with latest versions.
Click to expand...
Click to collapse
pls help me, im stuck on bootloop :'(
malakaz27 said:
pls help me, im stuck on bootlooop :'(
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
pls help me, im stuck on bootloop :'(
Click to expand...
Click to collapse
I have seen you have started a new thread of bootloop. Is this because you flashed one of these stock zip? you were going back to stock from los?
this method worked perfectly fine for me. i tried both lineage os roms available and both of them caused bootloop or end up destroying boot. so thanks to developer for making this zip file.
4j17h said:
I have seen you have started a new thread of bootloop. Is this because you flashed one of these stock zip? you were going back to stock from los?
Click to expand...
Click to collapse
hi i am stuck in bootloop after flashing all stuff in fastboot guide
leo77g said:
hi i am stuck in bootloop after flashing all stuff in fastboot guide
Click to expand...
Click to collapse
bootloop to recovery? have you tried fastboot -w usually this should boot to system or else flash stock recovery, wipe full. This should definitely get back the device to system.
4j17h said:
bootloop to recovery? have you tried fastboot -w usually this should boot to system or else flash stock recovery, wipe full. This should definitely get back the device to system.
Click to expand...
Click to collapse
formatting worked and thanx for help )
Moderators' Announcement: I've removed the links to Telegram and references to it. This is not a development thread, and support is to be provided through XDA. Many posts proved this has not been the case!
You may be asking, "Why was my Telegram or Whatsapp thread closed?"
Well, it's just becoming too much.
Going forward, we will only allow one Telegram chat link on a development thread by the ROM's developer and only if thorough support is still provided in the ROM thread on XDA.
All discussion channels, photography channels, whatnot channels will be strongly discouraged and removed with immediate effect. Please reference the forum rules:
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
Also, we now have an official XDA Discord Server. We would encourage you to try it out.
Announcing the Official XDA-Developers Discord Server
FYI
Thanks,
The Moderation Team
Click to expand...
Click to collapse
Need Help
Hi, everybody. Really need help.
There is a phone Realme X Lite. Write that it is Realme 3 Pro for the Chinese market, as well as firmware.
My version was: RMX1851_11_A.05
Tried to flash RMX1851EX_11_OTA_0150_all_2Zfcensdoezk.ozip, recovery gave an error, *_0140_* wrote that the current version is newer.
In depth test APK on the version out of the box wrote that this version of the phone is not supported, so the bootloader could not unlock.
But in the official website came across an offer to join the testing of Android Q
r1.realme.net/general/20190522/1558492614147.pdf
There are two files, the second for rollback.
I installed P2Q, everything went well, but the SnapDragon camera is used and it is terrible if there is not enough light. In depth test is not even installed, apparently not supported in the new version.
I decided to roll back, chose in Recovery Q2P archive, there were no errors, but after rebooting the phone hangs on the initial screen saver and after 10 minutes throws in the recovery with the error "Data error, select wipe data to recovery system". Wipe doesn't help. The same with other archives for Realme 3 Pro.
Also found RMX1851_11_A.12_190423_abecd1fa.ofp for firmware via MsmDownloadTool, but it requires authorization and support refuses to call login details.
Can who faced a similar problem on this or other phone.
Please help, pay for the time spent =)
ResSetOk said:
Hi, everybody. Really need help.
There is a phone Realme X Lite. Write that it is Realme 3 Pro for the Chinese market, as well as firmware.
My version was: RMX1851_11_A.05
Tried to flash RMX1851EX_11_OTA_0150_all_2Zfcensdoezk.ozip, recovery gave an error, *_0140_* wrote that the current version is newer.
In depth test APK on the version out of the box wrote that this version of the phone is not supported, so the bootloader could not unlock.
But in the official website came across an offer to join the testing of Android Q
r1.realme.net/general/20190522/1558492614147.pdf
There are two files, the second for rollback.
I installed P2Q, everything went well, but the SnapDragon camera is used and it is terrible if there is not enough light. In depth test is not even installed, apparently not supported in the new version.
I decided to roll back, chose in Recovery Q2P archive, there were no errors, but after rebooting the phone hangs on the initial screen saver and after 10 minutes throws in the recovery with the error "Data error, select wipe data to recovery system". Wipe doesn't help. The same with other archives for Realme 3 Pro.
Also found RMX1851_11_A.12_190423_abecd1fa.ofp for firmware via MsmDownloadTool, but it requires authorization and support refuses to call login details.
Can who faced a similar problem on this or other phone.
Please help, pay for the time spent =)
Click to expand...
Click to collapse
since your bootloader is locked, all you can do is wipe full data or flash back P2Q then format & then flash Q2P.
4j17h said:
since your bootloader is locked, all you can do is wipe full data or flash back P2Q then format & then flash Q2P.
Click to expand...
Click to collapse
I did Wipe before and after firmware, on P2Q is stitched without problems, but under firmware in Q2P in recovery writes, that not managed wipe userdata. The data was not encrypted, the password is not asked.
do you have video for Fastboot Method ?
[No message]
Unsure if this is the place since its also related to TWRP 3.7, any help is appreicated
Got stuck in a weird situation and wondering if anyone has ideas.
Current State:
Slot_A on OOS 11, can boot TWRP via Fastboot
Slot_B on OOS 12, can only boot into Fastboot
Originally on OOS 11, booted TWRP and made backups of all partitions (data, boot, system image, vendor image, etc.). Forgot to move this to computer so this is all still stored on device.
Proceeded with OOS 12 upgrade (into Slot B). Patched magisk, rebooted, then flashed TWRP 3.7 (FBEv1), direct installed magisk, rebooted. - Everything was functional, but decided to go back to OOS 11.
Thinking I could just use the TWRP backup made on OOS 11, I did the following:
Booted into 3.7 TWRP
Restored the backup for boot, system image, and vendor image
Set active slot to Slot A and reboot
It doesn't allow me to boot into the OS (Presumably because the data was re-encrypted for OOS 12?)
Set active-slot=b and reboot, but it's locked to fastboot.
I've attempted a few things, but I can't boot back into OOS. I would prefer to retrieve my TWRP backups first before doing an MSM reset.
When on Slot_A (older), I can only boot into TWRP 3.6.2 and 3.7. I'm guessing 3.6.2 can't decrypt since it's only configured for A11 and under, but not sure why 3.7 can't decrypt my data.
- It doesn't even ask for pin when TWRP launches; maybe it's reading the System for Slot_A and thinks i'm still on A11?
- running `twrp decrypt {pin}` doesn't seem to work. Unsure if there's something done to my lockscreen pin to be used as the encryption key/password?
When on Slot_A, attempting to boot into either the system or TWRP hangs.
Things I've tried:
Flashing A11 boot.img and magisk-patched boot.img to Slot_A -> Hangs on 1+ Spinning dots
Flashing A12 boot.img and magisk-patched boot.img to Slot_B -> Hangs on 1+ logo (Does show up on ADB though)
Booting Slot_B into TWRP 3.6.2 (Official, and Nebrassy unofficial for A12) and TWRP 3.7 -> Gets stuck on "Fastboot Mode" screen (fastboot cli still responds) or Hangs on snapdragon logo
Edit: Ended up using MSM. Needed device for work
I have a similiar problem to flash twrp to my phone ,
each time i try i get a fastboot loop too and i have to reset/unbrick it with the msm tool back to android 11
i use the OnePlus_7_Pro_Global_OxygenOS_11.0.5.1 package to unbrick the phone , i dont know how long and often i tried now to get twrp to work so that i can flash a custom fw ... i want root and a android 13 based cfw but i dont get it to work :/
I got it working with crdroid. heres some stuff
guacamole - Google Drive
drive.google.com
be carefull
¯\_(ツ)_/¯
------------------------------------
I got stable and decrypted fs RW working on crdroid 9.1 firmware other than some weird bugs
i put it in the 2023-twrp
MissAnthropin said:
I have a similiar problem to flash twrp to my phone ,
each time i try i get a fastboot loop too and i have to reset/unbrick it with the msm tool back to android 11
i use the OnePlus_7_Pro_Global_OxygenOS_11.0.5.1 package to unbrick the phone , i dont know how long and often i tried now to get twrp to work so that i can flash a custom fw ... i want root and a android 13 based cfw but i dont get it to work :/
Click to expand...
Click to collapse
I have the exact same problem! Have you found a fix yet? This seems to happen when I try to install Android 13 based roms, and when I install a rom like Lineage OS, using their recovery, it works just fine.
No, and I don't know why, maybe i do something wrong or it is the Modell that make this trouble.
I thinking to sell my OP7PRO and buy another one ( and then I have the same problem with the new phone )
No no let the jokes aside, it must work, i mailed with OnePlus Support Germany but they only helped me to install A11 w/root and recovery, i thought ok now I can update to A13 so I loaded A13, unpacked the boot.img, Patched the boot.img
Installed A13 w/out errors, rebooted - Fastboot loop
RIP
Started ranting instead
TWRP for guacamole development seems to be fairly scarce, last working recovery I tried was when they started using fastboot boot to enter it. It was pretty hacky even then, currently it seems that nebrassy is the maintainer for twrp for guacamole.
Github: https://github.com/nebrassy Android 12 thread: https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4269551/ Nebrassys Telegram has helpful info as well: https://t.me/NSSFB
last update I found was 2022:10:2 - https://www.pling.com/s/Phones/p/1835156
after a few days of torture I read a thread on here saying if you flashed twrp via magisk like you would if it was a magisk moule it would work normally. It worked on my device so I assume that its universal. I have filled my computer with guacamole related files Im uploading here before im forced to reinstall my os:
guacamole - Google Drive
drive.google.com
Just a fyi from what I have gathered from my experience you can get a stable twrp recovery with persistant / read write access and disabled encryption and basically use it with little error up until you try flashing a newer custom rom. My guess is when flashing a cfw the bootloader gets rewritten causing our boot image to become corrupted. Flashing twrp over / booting to twrp via fastboot or trying to install it via another custom recovery causes boot / recovery failures... meaning you cant really use it for flashing custom roms. I cant find the post with the install instructions I seen that helped me so here is what I think it was,
Found it: https://forum.xda-developers.com/t/how-to-make-twrp-work-in-your-stock-a12.4522667/#post-87985325
~ I have bricked this device constantly while ****ing around so unless youre prepared to go to war with the ****er, Id quit messing with it.
MSM flashing with windows is the only way to recover from the void.
Click to expand...
Click to collapse
using Linux systems for EDL is a bit more difficult to figure out but can be done > EDL https://github.com/bkerler/edl/blob/master/edl | https://github.com/andersson/qdl
Click to expand...
Click to collapse
~If you do brick I created a fastboot flashable A13 Oxygen os recovery rom and uploaded it to my google drive found under recovery_brick_fastboot.zip ~
Click to expand...
Click to collapse
lastly be mindful of a/b partition configuration or youll find yourself lost or bricked
Installation:
1. Obviously unlock the bootloader - OEM Unlock
2. Flash custom recovery (lineage/crdroid/etc)
3. (Personally I root here and again on the active slot so) flash magisk.zip
4. Reboot into installed ROM and install magisk android app and complete setup, reboot system
5. (another thing I like to do before flashing twrp) setup magisk enable all the basic options like prophide, deny list then set root userspace option to global.
6. Flash TWRP .zip (https://dl.twrp.me/guacamolev2/twrp-installer-3.7.0_12-0-guacamolev2.zip) via magisk
Alright! After all that you should be able to reboot into recovery via adb reboot recovery / fastboot or power menu and you find a working twrp recovery installed.
If you need help or want to **** around with the device you can @ me anytime and ill do my best to halp
2600 IRC (cornelius.scuttled.net >Nick captain >channel #guac)
Telegram https://t.me/+pxvpKToFo6pkMGYx
Discord https://discord.gg/MhvWgEfY
Pics
RolandStoner said:
Pics
Click to expand...
Click to collapse
You Confussing me a lot with your Posts before ...
i´m unsure what you mean exactly,
my bootloader is unlocked, with magisk i got a working root but after that i fail
what you mean with flash twrp with magisk ?
after unlocking the bootloader and get root, i tryd to flash twrp like before on other devices but that seems not working because i get then the fastboot loop
on another thread i found here on xda too, the guy wrote dont forget to activate the fastboot loop fix in the advanced options
but i not tried it yet again , so what should i do now ?
for now , i´m back on android11 , with stock oxygen os firmware
i have to do now the things like i did before again , unpack boot.img from the firmware that is installed on the device
patch it with magisk, flash it with "fastboot flash boot boot-patched.img" or is this step senseless ?
i mean you only wrote unlock bootloader and flash a cfw , but i don´t have a chance to flash a custom fw without a custom recovery ??
my recovery on my op7pro have no options for "install zip" or something else
addendum:
like i said you confused me a lot
addendum two:
or i do what i said before .. i sell my op7pro and buy me a one where i havent so much trouble installing twrp and root
i never had a phone before that made so much trouble in installing simple twrp ...
but i don´t found a phone yet that is compatible with kali and the pentest tools or wardriving tools like the oneplus , so i have a problem ,... i think i should drink now my selfmade blackberry liquor ( or blackberry booze ? ) and let the smartphone be a smartphone for now and power off my brain for a while
Yes, you need to patch your boot image via magisk and flash it with fastboot.
After you let magisk do its first time setup and then once it reboots you go to Magisk > Modules and flash the twrp recovery .zip file you got from twrp. link:https://twrp.me/oneplus/oneplus7pro.html just like you would if it was a magisk module.
the password for twrp decryption is your pin. Here are simpler instructions
https://forum.xda-developers.com/t/how-to-make-twrp-work-in-your-stock-a12.4522667/#post-87985325
****... I forgot a step.
after flashing twrp as a module in magisk you dont reboot, you go back to the main screen hit the install button and choose direct install
Now I understand it more, i had before rooted the phone successful with magisk, but then I made a wrong decision and booted into Fastboot and flashed TWRP in Fastboot Mode as I did it before with all my Smarties i had before, coz those way with Fastboot worked before all the time so I never thought that this is the error in the procedure
I give the twrp flashing with magisk a try.
Thx for the help
MissAnthropin said:
Now I understand it more, i had before rooted the phone successful with magisk, but then I made a wrong decision and booted into Fastboot and flashed TWRP in Fastboot Mode as I did it before with all my Smarties i had before, coz those way with Fastboot worked before all the time so I never thought that this is the error in the procedure
I give the twrp flashing with magisk a try.
Thx for the help
Click to expand...
Click to collapse
Thank @yassine2217 because I would never have done so either.... Still many bugs but twrp is twrp