Can someone do the tutorial for rooting ze553kl after the Oreo update? Can I use the same recovery?
Thank you..
Root with magisk on Android O
You can root Zenfone 3 zoom with magisk on Android O
I tried rooting it by flashing latest super su but it stuck while booting
1. Unlock the bootloader with the asus's official unlock tool(you can get if on there website)
2. Download magisk app from their website
3. Open the app and download the latest magisk zip file
4. Download TWRP recovery for Asus Zenfone 3
Zoom(search on xda for recovery)
5. Flash TWRP recovery via fastboot method .Then
directly reboot to recovery
6. Now install magisk zip file via TWRP
7. Reboot and enjoy root and magisk modules
Thanks man, but my recovery keeps turning to stock.
TaeBR said:
Thanks man, but my recovery keeps turning to stock.
Click to expand...
Click to collapse
Once you have flashed TWRP, reboot straight into recovery rather than back into the system, otherwise the system overwrites with stock recovery. Once you've done it once it should stick. Hope that works for you.
pjcarrmole said:
Once you have flashed TWRP, reboot straight into recovery rather than back into the system, otherwise the system overwrites with stock recovery. Once you've done it once it should stick. Hope that works for you.
Click to expand...
Click to collapse
Thanks man, but now when i flash the supersu i got the error:
-Patching sepolicy
---Failure, aborting
its getting worst
How can i fix the fingerprint with magisk on Oreo?
Related
Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.
Easier thing to do is flash boot.img from the factory image to boot_a and boot_b if you are having issues.
This problem occurs when you flash TWRP if you have root installed. To avoid, remove root before installing TWRP.
Oh, I should mention to get into bootloader from TWRP, simply use the adb command "adb reboot bootloader". Should work, worked for me.
I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.
Nitemare3219 said:
I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.
Click to expand...
Click to collapse
Until it gets a little more stable on the Pixel, this is probably a good idea.
Good idea. But I M sometimes flashing when I am at or on the way to work.
Flash junkie needs his daily dosis
mikaole said:
Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.
Click to expand...
Click to collapse
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
I have this issue and flashing supersu didn't fix my problem. Will go to factory image flashing.
Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
Thanks! This worked for me.
EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
cognitivedissonance said:
EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
Click to expand...
Click to collapse
This is a Pixel XL forum.
Homeboy76 said:
This is a Pixel XL forum.
Click to expand...
Click to collapse
Aren't the two systems (Pixel OG and Pixel 2) extremely similar? If they're not, then my advice should be ignored for anyone using the Pixel OG.
OP2 is stuck at OP logo after the latest OTA. What do I need to do to have it restored it back ..
sguy156 said:
OP2 is stuck at OP logo after the latest OTA. What do I need to do to have it restored it back ..
Click to expand...
Click to collapse
If you have twrp you can flash a full oxygen rom to restore it if you dont you need to Download latest full rom on your pc go in recovery mode connect phone to pc and put the zip in your storage and after that flash it via recovery mode
No it doesn't go into recovery mode it only goes into fastboot mode ..
sguy156 said:
No it doesn't go into recovery mode it only goes into fastboot mode ..
Click to expand...
Click to collapse
Try this zip on your pc while phone connected and on fastboot mode It auto flashes twrp on your phone so you can try to flash oxygen os via it
https://forum.xda-developers.com/devdb/project/?id=13708#downloads
that worked so do I need to flash modified SU 2.79 to root this phone or stay with the TWRP which came with the first aid script
sguy156 said:
that worked so do I need to flash modified SU 2.79 to root this phone or stay with the TWRP which came with the first aid script
Click to expand...
Click to collapse
If you want to root your phone use this file and Flash it via twrp
https://www.androidfilehost.com/?fid=24591000424939898
modified SU is not going to work and have to use seemless SU . Thanks for your help which version of TWRP works without any issues with the newest Oxygen OS..
sguy156 said:
modified SU is not going to work and have to use seemless SU . Thanks for your help which version of TWRP works without any issues with the newest Oxygen OS..
Click to expand...
Click to collapse
Go to Playstore and download twrp app en flash the latest compiatble version
What is needed to re-root OOS 3.5.6 if you did like me and let the OTA update your phone.
TWRP 3.0.2-2 link
OOS3 SuperSu 2.78 link
You can get latest TWRP flashable OOS packages from here.
For future reference.
Oneplus two Rooted stuck on Boot Loop Mode
Hi Guys I need your Help Can anyone Help me as soon as possible
I was Using Resurrection Remix 5.8.5 Nougat 7.1.2 and in Twrp recovery
I was using Resurrection Remix 5.8.5 Nougat 7.1.2 and in Twrp recovery apk a small mistake was done by me
I tick marked as
Allow Flashing to boot partition after that it got stuck in Boot Loop Mode How fix that guys
But Fastboot Mode only Working
Hi it's done with me but not in your way I was realising why it is not boot loading then I came to know maybe TWRP recovery is not installed so I just wanted to flash TWRP recovery in fastboot mode there are so many people trying in different different way to switch on the mobile which got stuck and boot loop mode I found a simple way with all in one tool for Android I am giving you a description or a link below just to flash TWRP recovery and don't forget to select after flash reboot you have to select tick mark it's the best way you can boot load your phone very very simple way to do that
Download Link
https://basketbuild.com/devs/mauronofrio/TOOL
I have been using many custom ROMs in the past months on my phone. I flashed stock Oreo just for fun. Now I lost my TWRP. It got replaced with Stock recovery. The main problem is I am unable to flash a recovery on my phone since then. I set my phone on USB debugging and open powershell & run the command " adb fastboot reboot"
Things get weird here. After flashing the TWRP image using fastboot flash recovery "mytwrpname.img" . Recovery shows a pattern(3×3) and asks me to decrypt. I do it and flash magisk but CTS/ Safety Net keeps failing. I wanted to reflash and again TWRP is gone.
What should I do. Sorry for the long story. Rules wanted me to be descriptive.
Help me out!!
Yeshu_bablu said:
I have been using many custom ROMs in the past months on my phone. I flashed stock Oreo just for fun. Now I lost my TWRP. It got replaced with Stock recovery. The main problem is I am unable to flash a recovery on my phone since then. I set my phone on USB debugging and open powershell & run the command " adb fastboot reboot"
Things get weird here. After flashing the TWRP image using fastboot flash recovery "mytwrpname.img" . Recovery shows a pattern(3×3) and asks me to decrypt. I do it and flash magisk but CTS/ Safety Net keeps failing. I wanted to reflash and again TWRP is gone.
What should I do. Sorry for the long story. Rules wanted me to be descriptive.
Help me out!!
Click to expand...
Click to collapse
Same problem happend to me , what i did
1. After decrypting , i flashed masgisk and lazyflasher
2. Booted to system , opened magisk manager and got root
3. Downloaded official twrp app from playstore
4. Opened official twrp app ,granted the supersu permissions
5. Downloaded and flashed the same twrp recovery from which i decrypted the device(very important to download and flash the same recovery version )
6. Boom you have twrp recovery forever :good:
shibbu18111997 said:
Same problem happend to me , what i did
1. After decrypting , i flashed masgisk and lazyflasher
2. Booted to system , opened magisk manager and got root
3. Downloaded official twrp app from playstore
4. Opened official twrp app ,granted the supersu permissions
5. Downloaded and flashed the same twrp recovery from which i decrypted the device(very important to download and flash the same recovery version )
6. Boom you have twrp recovery forever :good:
Click to expand...
Click to collapse
Is it important to flash lazy flasher?
Yeshu_bablu said:
Is it important to flash lazy flasher?
Click to expand...
Click to collapse
I don't think so. I'm on latest TWRP 3.2.3.1 by just decrypting and flashing Magisk 16.
Sent from my Moto G5 Plus using XDA Labs
Can anybody help me to root this latest version? Is there any special TWRP to boot and then flash latest Magisk?
Use last cosmicdan twrp and last magisk. Easy.
Cheers
I also cannot root my phone after jan updates. after flashing magisk and reboot, there's a black screen in the middle of bootscreen and it restarts the bootscreen and my phone doesnt get rooted.
tonycapuozzo said:
Use last cosmicdan twrp and last magisk. Easy.
Cheers
Click to expand...
Click to collapse
tried the latest twrp and magisk 18.0 .
*UPDATE*
I forgot to enable oem unlocking and USB debugging.
and also mount system in TWRP before flashing magisk.
cheers!
kupuk23 said:
and also mount system in TWRP before flashing magisk.
Click to expand...
Click to collapse
When next OTA arrives, you will know why it fails to install There is absolutely no reason to mount system partition to flash Magisk.
Plz can anybody plz tell me how to root or unlock camera 2 api in ma a1 latest pie june2020 update
it's a simple procedure
just unlock bootloader then boot into TWRP then flash recovery flasher zip and then flash Magisk zip and reboot
I've flashed all stock firmwares and get root with this simple procedure but note I've used TWRP 3.3.1-0 from Giovix92 because TWRP 3.2.1 flasher zip didn't work on latest firmware and i used Magisk19.3 its the most stable Magisk version in my opinion i never faced any problem with this version
fastboot flash recovery OrangeFox-R10.1_1.img
boot in twrp
flash OrangeFox-R10.1_1.zip
rebbot in recovery
flash magisk 20.4
reboot recovery
flash vbmeta.img (FOR RECOVERY)
Clean caches
Reboot
fingerprint, no
Files
https://forum.xda-developers.com/realme-x2-pro/development/orangefox-recovery-x2-pro-t4063301
use vbmeta from this post
Magisk
https://github.com/topjohnwu/Magisk/releases/tag/v20.4
hi, any idea to fix fingerprint?
[email protected] said:
hi, any idea to fix fingerprint?
Click to expand...
Click to collapse
We need to wait for Realme to release a fix, just like what happened on color os when fingerprint wasn't working
On C.27 Bootloader Unlock and Root, Fingerprinter works
How to upgrade from Android 9 Color OS 6 rooted and with magisk 20.4 to new C.27? Is there a tutorial? Thank You
minoccio said:
How to upgrade from Android 9 Color OS 6 rooted and with magisk 20.4 to new C.27? Is there a tutorial? Thank You
Click to expand...
Click to collapse
Uninstall Magisk with the .zip from their site. Github here
Instal stock recovery like you did to install custom recovery.
Next, download the C.27 update and run it from the file manager. Phone will reboot and start updating
After update, just do the whole process to root C.27 version like for Android 9.
deviantor said:
Instal stock recovery like you did to install custom recovery.
Uninstall Magisk with the .zip from their site. Github here
Next, download the C.27 update and run it from the file manager. Phone will reboot and start updating
After update, just do the whole process to root C.27 version like for Android 9.
Click to expand...
Click to collapse
So basically if I'm on c27 already, it's okay to use the same root method?
adsubzero said:
So basically if I'm on c27 already, it's okay to use the same root method?
Click to expand...
Click to collapse
Yea. I was on C27 total stock then followed these tips to root and custom recovery. Its all working well so far and fingerprint works.
deviantor said:
Yea. I was on C27 total stock then followed these tips to root and custom recovery. Its all working well so far and fingerprint works.
Click to expand...
Click to collapse
I tried several thins to install Magisk succesfully with no luck.
I received my Global x2 Pro this thursday and i successfully unlocked the bootloader and flashed twrp recovery. But when I flask the magisk 20.4 zip and reboot my device, i get an error saying that my boot / recovery partition is corrupt. I have to install C27 again from twrp and it boots up.
Can anybody help me how to install Magisk succesfully? It's driving me nuts. Also, i cant download the vbmeta.img from the OP. So i tried to extract the vbmeta.img from the c27 image to flash, but also no lucck
Edit: Finally having it working with the Orangefox recovery with the vbmeta.img. I thought that the link in OneDrive wasnt working, but it was my home networks which was blocking OneDrive. Problem solved!
deviantor said:
Uninstall Magisk with the .zip from their site. Github here
Instal stock recovery like you did to install custom recovery.
Next, download the C.27 update and run it from the file manager. Phone will reboot and start updating
After update, just do the whole process to root C.27 version like for Android 9.
Click to expand...
Click to collapse
Isn't it possible to install ota update from twrp? (I use mauronofrio). Is it mandatory to unroot, install C27 and then re-root?
minoccio said:
Isn't it possible to install ota update from twrp? (I use mauronofrio). Is it mandatory to unroot, install C27 and then re-root?
Click to expand...
Click to collapse
It's possible if someone makes a flashable zip, though I dont know of that can be done for every phone. Otherwise you need a stock recovery to install the OTA.
minoccio said:
Isn't it possible to install ota update from twrp? (I use mauronofrio). Is it mandatory to unroot, install C27 and then re-root?
Click to expand...
Click to collapse
Like @adsubzero said. Unless you have a custom ozip file to flash on TWRP, you need to have stock recovery to install a standard ozip.
ogutolopes said:
fastboot flash recovery OrangeFox-R10.1_1.img
boot in twrp
flash OrangeFox-R10.1_1.zip
rebbot in recovery
flash magisk 20.4
reboot recovery
flash vbmeta.img (FOR RECOVERY)
Clean caches
Reboot
fingerprint, no
Click to expand...
Click to collapse
for recovery mean recovery ka option ckick krna hai..vbmeta krty huay
In the backup options I don't see system, only system image. Does anyone else have this issue?