Original Post by : j1505243 at Mi A2 Forum
V9.6.4.0.ODLMIFF
OTA link:
https://android.googleapis.com/packa...fe5e120388.zip
System dump link:
https://github.com/TadiT7/xiaomi_daisy_dump
If someone wants to keep things in one thread, it may be the one if you provide more content/links to me.
Patched boot.img for Mi A2 Lite
Here is the patched boot.img to use with Magisk.
http://www.mediafire.com/file/g83o7n2bradet7a/patched_boot.img/file
Made from this system dump, a big thanks to @guangie for his hint about flashing A&B partiton, cause I was not able to do it by just flashing A partition and saw afterwards his tutorial.
You can follow the same tutorial to flash your Mi A2 Lite, just make sure to use my image and not his image, which is for Mi A2. : https://github.com/guangie88/xiaomi-jasmine-magisk-boot
Use at your own risks. I flashed it on my Mi A2 Lite 4/64 GB) and it worked perfectly. Please not that 1st time system didnt boot up, but 2nd boot was ok. Afterwads, no problems. Magisk Installed, Xposed installed, everything running perfectly. Again, I'm not responsbile if you brick your device. Go with caution, this is early development.
kidoucorp said:
Here is the patched boot.img to use with Magisk.
http://www.mediafire.com/file/g83o7n2bradet7a/patched_boot.img/file
Made from this system dump, a big thanks to @guangie for his hint about flashing A&B partiton, cause I was not able to do it by just flashing A partition and saw afterwards his tutorial.
You can follow the same tutorial to flash your Mi A2 Lite, just make sure to use my image and not his image, which is for Mi A2. : https://github.com/guangie88/xiaomi-jasmine-magisk-boot
Use at your own risks. I flashed it on my Mi A2 Lite 4/64 GB) and it worked perfectly. Please not that 1st time system didnt boot up, but 2nd boot was ok. Afterwads, no problems. Magisk Installed, Xposed installed, everything running perfectly. Again, I'm not responsbile if you brick your device. Go with caution, this is early development.
Click to expand...
Click to collapse
Thanks can you explain so i flash the patch file and the phone reboot but no thing happened
Sent from my iPhone using Tapatalk
---------- Post added at 07:44 PM ---------- Previous post was at 06:57 PM ----------
Test it every thing work fine
Sent from my iPhone using Tapatalk
kidoucorp said:
Here is the patched boot.img to use with Magisk.
http://www.mediafire.com/file/g83o7n2bradet7a/patched_boot.img/file
Made from this system dump, a big thanks to @guangie for his hint about flashing A&B partiton, cause I was not able to do it by just flashing A partition and saw afterwards his tutorial.
You can follow the same tutorial to flash your Mi A2 Lite, just make sure to use my image and not his image, which is for Mi A2. : https://github.com/guangie88/xiaomi-jasmine-magisk-boot
Use at your own risks. I flashed it on my Mi A2 Lite 4/64 GB) and it worked perfectly. Please not that 1st time system didnt boot up, but 2nd boot was ok. Afterwads, no problems. Magisk Installed, Xposed installed, everything running perfectly. Again, I'm not responsbile if you brick your device. Go with caution, this is early development.
Click to expand...
Click to collapse
Sadly, this thread is duplicated from my own, so be ready for it to be closed and post in the one made by me. OP wanted to be helpful by copying into the A2 Lite forum, while the only thing to be done was to move it (because when I originally posted, there were none)...
j1505243 said:
Sadly, this thread is duplicated from my own, so be ready for it to be closed and post in the one made by me. OP wanted to be helpful by copying into the A2 Lite forum, while the only thing to be done was to move it (because when I originally posted, there were none)...
Click to expand...
Click to collapse
sorry man. wasnt my intention to create confusion . how do i close this thread / let mod close it.?
mytowyn said:
sorry man. wasnt my intention to create confusion . how do i close this thread / let mod close it.?
Click to expand...
Click to collapse
Use the report button, select maintenance and write the details like "duplicated by mistake".
j1505243 said:
Use the report button, select maintenance and write the details like "duplicated by mistake".
Click to expand...
Click to collapse
thanks man. i have reported this
kidoucorp said:
Here is the patched boot.img to use with Magisk.
http://www.mediafire.com/file/g83o7n2bradet7a/patched_boot.img/file
Made from this system dump, a big thanks to @guangie for his hint about flashing A&B partiton, cause I was not able to do it by just flashing A partition and saw afterwards his tutorial.
You can follow the same tutorial to flash your Mi A2 Lite, just make sure to use my image and not his image, which is for Mi A2. : https://github.com/guangie88/xiaomi-jasmine-magisk-boot
Use at your own risks. I flashed it on my Mi A2 Lite 4/64 GB) and it worked perfectly. Please not that 1st time system didnt boot up, but 2nd boot was ok. Afterwads, no problems. Magisk Installed, Xposed installed, everything running perfectly. Again, I'm not responsbile if you brick your device. Go with caution, this is early development.
Click to expand...
Click to collapse
It doesn't seems to work well. I also have the 4/64 version.
Magisk Manager can't install any modules, and on the SafetyNet check, both ctsProfile and basicIntegrity result false.
EDIT 1: I suspect that the lack of busybox binary is the cause of the error when installing modules (it says "unable to extract zip file").
EDIT 2: Confirmed. I installed busybox from the playstore and it works now. There is a busybox module on Magisk, it should be included in the boot image to fix this. As ctsProfile and basicIntegrity are already triggered, it's not important at the moment, but if you (we) can keep both checks true, busybox must be included in the boot image.
EDIT 3: probably, because of the A/B partitions scheme, the modifications I do to the system (like installing busybox) are not effective. The system goes to black screen, I have to force reboot and after busybox or Magisk modules are not installed anymore (recovered from the other twin partition)
I think it's because only starting with version 16.7 Magisk is compatible with the A/B partitions, and the version integrated in this boot image is 16.0
If you can, please update the boot image with Magisk 16.7 (the latest at the moment).
EDIT 4: Ok, I managed to create a patched boot.img with Magisk 16.7, now everything works fine, SafetyNet totally ok. Except for the lack of unzip/busybox needed to install the Magisk modules, but I'm working on it too.
Thread closed at OP request.
Related
Good evening guys
I have a Xiaomi 5s stock rom MIUI9 with TWRP 3.2 (capricorn)
I was using the old supersu.apk to have root privilegs. I remove it completly to install the Magisk but I'm getting error 1
Follow the pictures...
As you can see I have the unlock boot, twrp, stock rom and not rooted... Tried others topics and tips to install the Magisk but It wont work...
What should I do?
(Xiaomi forum I saw a guy he installed the stock rom and full restored and he continues with error:1)
Resolution:
Change TWRP 3.2.1-1 to TWRP ZCX
Download stock rom (same as you're using)
Open the .iso with winrar or other software
Get the boot.img and put it in smartphone sdcard
Reboot in the recovery mod
Select install and change to install a IMG
Select boot.img and the partition BOOT
Install the magisk (feel free to put any version, I used v14)
Reboot and enjoy! :laugh:
PS: You dont need to unistall first your root because it'll be replaced when you install the stock boot.
Use magisk 15.2, make sure zip file not corrupt.
Even better use TWRP 3.2.1.1 and flash Magisk 16. That combination has some serious bugs ironed out.
BajinganTengik said:
Use magisk 15.2, make sure zip file not corrupt.
Click to expand...
Click to collapse
I tried with Magisk 15.3 and failed, same error. (ERROR:1)
8166uy said:
Even better use TWRP 3.2.1.1 and flash Magisk 16. That combination has some serious bugs ironed out.
Click to expand...
Click to collapse
I'm using the TWRP 3.2.1-1 is the same thing, I saw in Xiaomi Forum about the TWRP ZCX but I dont know what is the difference...
Does anyone have a fix to it?
Resolved, tip in the first post.
You could try the Xiaomi.eu ROM which has better support for rooting and adds some polish to MIUI (and also implements every weekly beta release of the official repo). Does require a clean install though.
8166uy said:
You could try the Xiaomi.eu ROM which has better support for rooting and adds some polish to MIUI (and also implements every weekly beta release of the official repo). Does require a clean install though.
Click to expand...
Click to collapse
Thank you for your advise, but I prefer the stock rom, btw I already fixed it too xD
After using this phone for a while I decided to root it.
I unlocked bootloader, installed TWRP and flashed Magisk, but all I get is bootloop or stuck on bootlogo (your device has been unlocked.....)
SOLUTION
https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
Applicable also for moto Z2 Play, just with appropriate recovery, of course
Please note the updates to the first post. It may be necessary to do the procedure twice.
I tried these TWRPs:
3.2.3.0
64bit 3.2.1
and TWRP and modified magisk from https://forum.xda-developers.com/z2-play/how-to/guide-twrp-root-t3667769
I tried all TWRPs with both modified magisk and official v18.
I have XT1710-09 with Oreo and October security patch
Is there a way to root this lastest firmware?
Thanks
Klen2 said:
I tried these TWRPs:
3.2.3.0
64bit 3.2.1
and TWRP and modified magisk from https://forum.xda-developers.com/z2-play/how-to/guide-twrp-root-t3667769
I tried all TWRPs with both modified magisk and official v18.
I have XT1710-09 with Oreo and October security patch
Is there a way to root this lastest firmware?
Thanks
Click to expand...
Click to collapse
I did 3.2.3-0 TWRP method (by Junior Passos) on my XT1710-06 device with 8.0 on August 1 security patch (purposefully neglected updating any further cause method was tested exactly up to August patch according to Passos) and everything seems working pretty fine for a month now. Think I've installed no Magisk modules other than Xposed systemless yet and I've no interest in SafetyNet as well, so not deeply tested either. Don't know for sure, but I guess there's a good chance for such method to work on October patch too. Just be sure to perform every step as it is now in the 3.2.3-0 OP. One word of advice: after performing TWRP backup, look for it in /system/media and move it to both external and internal SDcards just in case something goes wrong (usually because of a missed step, I can say)... Also: I recommend to install Magisk v17.1 first time; then, if you want, update to v18 but right from the installer...
Sent from my Moto Z2 Play using XDA Labs
Strange, I have zero magisk problems when using the latest stock rom. Flash in twrp, done, no issues. However, it could be because I first back up boot and system and then restore them with twrp before rooting(this removes encryption).
Have these steps worked for me...
1.)Flash TWRP using Fastboot
2.)Go to TWRP/Settings and open Terminal.
3.)Run both of following commands:
echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk
Click to expand...
Click to collapse
4.)Flash Magisk-v17.1.zip
5.)Repeat step 2 and 3 dont wipe.
6.)Start
NOTE: before Reinstall stock or uninstall Magisk.
I did the Junior Passos method of doing the backup, and everything is working like a charm.
Cupcake 1.5 said:
Strange, I have zero magisk problems when using the latest stock rom. Flash in twrp, done, no issues. However, it could be because I first back up boot and system and then restore them with twrp before rooting(this removes encryption).
Click to expand...
Click to collapse
Hi, Could you please, tell me which stock ROM you are using and where is possible to get it?
First time I am having problem with Magisk, never had on other phones.
Problem = Bootlop
OldUncle said:
Hi, Could you please, tell me which stock ROM you are using and where is possible to get it?
First time I am having problem with Magisk, never had on other phones.
Problem = Bootlop
Click to expand...
Click to collapse
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.
Cupcake 1.5 said:
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.
Click to expand...
Click to collapse
Perfect!
Thank you very much!
The only solution which worked!
Finally I got full control on my Z2 Play.
Cupcake 1.5 said:
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.
Click to expand...
Click to collapse
Regarding backup, this is done through the stock ROM correct (Settings --> System --> Backup to Google Drive).
Thanks,
smithmal
Cupcake 1.5 said:
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.
Click to expand...
Click to collapse
This worked perfectly on my Moto Z2 XT1710-06 with Oreo 8.0 when no other options worked.
Flash or Boot into TWRP
Backup System and Boot partitions in TWRP
Restore System and Boot Partitions in TWRP (note I had to enable R/W access in TWRP to restore the system partition)
Flash Magisk-v19.3.zip
Reboot
That is it. Now Rooted and passes all SafteyNet test. No more restricted apps. Even Google Pay now works.
Thank You.
sick
Cupcake 1.5 said:
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.
Click to expand...
Click to collapse
your method worked like charm, thanks alot man
So today with some testers i managed to make root on OnePlus 7T, I want to specify that 95% of the work was done by @topjohnwu (Magisk creator). For now you should use only Magisk Canary files
I will explain 2 different guides:
First Root Guide:
This guide is for a specific rom version, so you will need to use a specific patched boot.img
- Download the patched_boot.img
- Reboot your device in bootloader-fastboot mode
- Flash the patched_boot.img in the boot partition:
Code:
fastboot flash boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
Second Root Guide:
This guide is more generic than the first one, you should use this one if you are unable to find a specific patched boot.img
- Download a patched_boot.img (you should try with the latest one)
- Reboot your device in bootloader-fastboot mode
- Boot the patched_boot.img:
Code:
fastboot boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
- Click on Install, then direct install and wait the end of the process
- Reboot the device
Third Root Guide:
Guide by @gpz1100
TIPS:
Actually you should use only Magisk canary files Magisk 20.3
You can get the stock boot images from the fastboot rom: https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
Actually i'm using magisk manager canary and magisk canary debug to patch the boot.img, I don't recommend updating magisk, if you don't want to see the updates install the normal magisk manager
Magisk 20.3 fully support OnePlus 7T and 7T Pro
HOW TO UPDATE a ROM and KEEP ROOT:
Before all Disable all magisk modules
Be sure to use Canary Magisk Manager and Canary Magisk (debug)
You can update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Download:
Patched/Stock Boot Images: https://www.androidfilehost.com/?w=files&flid=300177
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Donations:
Credits:
@RohanAJoshi
Flashed and working flawless.
Really thanks for this.
Awesome work bro.
Can you please upload the patched boot.img please? I dont see it in the above folder at all.
nick_22 said:
Can you please upload the patched boot.img please? I dont see it in the above folder at all.
Click to expand...
Click to collapse
Done, i uploaded them using ftp and i forgot to move the files in the right folder
Working, thanks a lot @mauronofrio
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
See OP, its clearly mentioned there. You have to flash this via fastboot and not any custom recovery. Firstly setup adb on your PC and then check the commands. Its very easy. Do some googling and still if its difficult for you, come back and ask.
jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
Welcome to the android scene, reminds me of the old psx scene
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
Get your stock boot.img from 1st post.
Reboot to bootloader.
And do this command
fastboot flash boot boot.img
fastboot reboot
Device will boot unrooted.
---------- Post added at 05:58 AM ---------- Previous post was at 05:55 AM ----------
jesrani;80464121 [user=4712355 said:
@mauronofrio[/user], thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.
RohanAJoshi said:
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.
Click to expand...
Click to collapse
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
jesrani said:
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
In older devices like OP5T it happens like this, not in newer devices. OP7T has seamless updates, its installs while device is turned on in second partition.
nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
jesrani said:
@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
jesrani said:
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
Canary debug, don't update it
Help please. I have returned to Android after 5years with OnePlus 7t and trying to root it. I am trying this method but not being able to successfully root it. Steps I have tried
Went to fastboot mode by restarting the phone but I don't get an option to install the patched image file. And even boatloader is locked. Do I need to unlock the bootloader. And I unlock will I loose my data. Sorry for silly question I have completely forgot about Android.
Thanks, rooted successfully
?
To be honest need video tutorial asap?
mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Ok. Got it. So, I have already booted back to unrooted mode now. And I cant wipe my data again. Thanks for your response.
Hello i found a little way for have root & and working xposed with no bug on last firmware WW_17.1810.1910.73 & WW_17.1810.1911.110
Stock Recovery
You need adb drviers and unlocked ZenFone 6 on WW_17.1810.1910.73 or WW_17.1810.1911.110
First install last Magisk Manager
Open setting of Magisk and add custom update channel https://github.com/solohsu/magisk_files#custom-update-channel
Download ZenFone6RootXposed-10.73.img or ZenFone6RootXposed-11.110 (i have add stock boot11.110.img, we will need it for next update)
http://www.mediafire.com/folder/skzceszqu8d3j/AsusZenFone6
Now reboot device to bootloader
Code:
adb reboot bootloader
And boot with ZenFone6RootXposed-10.73.img or ZenFone6RootXposed-11.110 (not flash it, your device have a chance to bootloop)
Code:
fastboot boot ZenFone6RootXposed-10.73.img
Code:
fastboot boot ZenFone6RootXposed-11.110.img
The devices reboot automaticly
Go to Magisk and install Magisk, choose direct install
Reboot and Enjoy root
if you want Xposed flash it with magisk :
Riru Core
I use YAHFA
Android 10 ElderDrivers Xposed
And the manager
Xposed Installer
Good morning
I have tried several times root for Android 10
The Magisk part works smoothly, but the Xposed part never works, producing a bootloop
I have extracted the boot and applied magisk, loaded the Riru Core module, but when loading ElderDrivers, the phone stays in bootloop
Do you know what the reason may be?
Works splendid, great guide!
Tried to use Sandhook first, but ended up with YAHFA instead due some xposed problems (xposed not detected).
Had an old version of Android 9, so i first upgraded it to "UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1" (only supported upgrade path - 9 to 10), then to "UL-ASUS_I01WD-ASUS-17.1810.1910.73-1.1.1-user" (your specified .73)
- Later patching with your img
Thanks
it is impossible
Starting with .73 stock
at the moment I install Riru Yahfa, following the manual, it does not start again, unless install the official boot
the device stays on the Zenfone boot screen without doing anything else
I have tried the version supplied by Magisk, I don't know if you have tried another version
Why will we need the stock boot for the next update? We can't make menully update after root? I just want to make root not install xposed.
Sent from my ASUS_I01WD using Tapatalk
thanks a lot, this a really easy way to get root, but i have a little issue, i had my phone with NO pin code or fingerprint before using this method, and now if i want to ad a pin, password or gesture it simply does not get saved, every time i do the procedure to set the pin it does like if i did nothing, anyone has this issue, or know how to fix it, is there a problem if i hard reset?
any help will be good
In the latest build .110 ctsprofile is false while basicintegrity is true. Is it due to the root or the rom has not been signed by google?
Rom1995 said:
In the latest build .110 ctsprofile is false while basicintegrity is true. Is it due to the root or the rom has not been signed by google?
Click to expand...
Click to collapse
https://zentalk.asus.com/en/discussion/comment/35355/#Comment_35355
baster72 said:
Why will we need the stock boot for the next update? We can't make menully update after root? I just want to make root not install xposed.
Sent from my ASUS_I01WD using Tapatalk
Click to expand...
Click to collapse
just flash ZenFone6RootXposed-10.73 or ZenFone6RootXposed-11.110 and you willl have it
hdsporty50 said:
Good morning
I have tried several times root for Android 10
The Magisk part works smoothly, but the Xposed part never works, producing a bootloop
I have extracted the boot and applied magisk, loaded the Riru Core module, but when loading ElderDrivers, the phone stays in bootloop
Do you know what the reason may be?
Click to expand...
Click to collapse
hdsporty50 said:
it is impossible
Starting with .73 stock
at the moment I install Riru Yahfa, following the manual, it does not start again, unless install the official boot
the device stays on the Zenfone boot screen without doing anything else
I have tried the version supplied by Magisk, I don't know if you have tried another version
Click to expand...
Click to collapse
Don't flash Xposed using Magisk Download, flash it manualy :
EdXposed v0.4.6.0_beta
You will always get bootloop with v0.4.5.1_beta
_______________________________________
UPDATE for 11.110
flash boot.10.73.img for update safe
And do the same with 11.110 files.
Don't forget to add custom update channel in Magisk
And use v0.4.6.0_beta for xposed
Why can't we have any YouTube guides for anything related to this phone?
vernj123 said:
Why can't we have any YouTube guides for anything related to this phone?
Click to expand...
Click to collapse
I want to do it but I don't have another device to record.
Someone try this method to install xposed? I afraid to get bootloop.
Sent from my ASUS_I01WD using Tapatalk
Hi everyone, I hope somebody can help me out to solve an issue I just got with my zenfone,
After using an advise from DaConcho for getting back screen lock after unlocking bootloader I got in another situation.
I followed the instructions from the post and everything was going fine, I boot thought adb with the provided patched boot for Q .110 and that far no issues , when I open magisk manager to download magisk from the alternative source magisk manager prompt to complete the installation downloading some necessary files, not the magisk version, just said some files, and I click yes, then it installed something and reboot, phone started fine, but when I wanted to start the process again I found out that I loose PC connectivity.
I have no connection at all, even if I manually boot in bootloader I can't connect to PC, so no adb commands,
Please can someone help
does someone has the patched boot image for new .119 firmaware, i updated and losee magisk
baster72 said:
Someone try this method to install xposed? I afraid to get bootloop.
Click to expand...
Click to collapse
Don't be afraid just flash stock boot if you get bootloop
joesa said:
does someone has the patched boot image for new .119 firmaware, i updated and losee magisk
Click to expand...
Click to collapse
I update my links you can get stock boot here Boot & RootedBoot ZenFone6
MystikMan97130 said:
Don't be afraid just flash stock boot if you get bootloop
I update my links you can get stock boot here Boot & RootedBoot ZenFone6
Click to expand...
Click to collapse
Thanks a lot !!! You really help a lot with this method
MystikMan97130 said:
Don't be afraid just flash stock boot if you get bootloop
I update my links you can get stock boot here Boot & RootedBoot ZenFone6
Click to expand...
Click to collapse
can you please check link, it is not working, i can see folder but can not download
Hello, direct link:
ZenFone6RootXposed
Nice, thanks a lot for this! Rooting on stock with unlocked bootloader worked for me perfectly (did not check xposed)!
est-ce que l'on perd ses données en faisant le root ?
merci!
If it can, how? I'm having bootloop issues trying to do that. Thank you.
Bootloop in logo S9
RpRAUC said:
Bootloop in logo S9
Click to expand...
Click to collapse
follow up
Piereligio said:
If it can, how? I'm having bootloop issues trying to do that. Thank you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s9/how-to/one-ui-2-beta-rooting-installing-twrp-t4012961
https://forum.xda-developers.com/ga...rooting-installing-twrp-t4012961/post81084623
The patched kernel contained here was the solution for me
S9 ROOT
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q
viktorvlahov11 said:
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q
Click to expand...
Click to collapse
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.
it stucks for me on the samsung logo
aidenpearce296 said:
it stucks for me on the samsung logo
Click to expand...
Click to collapse
Try flashing the twrp flashable firmware it may fix your problem
---------- Post added at 08:41 AM ---------- Previous post was at 08:37 AM ----------
viktorvlahov11 said:
Try flashing the twrp flashable firmware it may fix your problem
Click to expand...
Click to collapse
Piereligio said:
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.
Click to expand...
Click to collapse
I got it to work on a Bulgarian unlocked model
Maybe try flashing the twrp flashable firmware after the mod
omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it
viktorvlahov11 said:
omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it
Click to expand...
Click to collapse
I done that, but still stuck on SAMSUNG logo, no boot loop or what. I was waiting 10min, nothing happened.
Any advice?
Hi there,
after having tried different methods to root my S9, which has updated to Android 10 One UI 2.0 this morning, maybe the solution that finally worked for me will help you too.
First I tried to root just like in Pie, as found on the net: flashed TWRP 3.2.3 via Odin, then flashed Magisk with TWRP plus this no-verity-opt-encrypt. Got stuck in bootloop, tried different no-verity/dm-verity versions, Magisk 18.x and Magisk 20.1. Nothing worked, got stuck again every time i rebootet the system again.
Then, after realising that I CANT get back to Android 9 (old rom wasnt Odin flashable anymore, phone didnt boot, BSoD), I first downloaded the new stock rom and bootloader as zip, got it from here:
https://forum.xda-developers.com/showpost.php?p=81615561&postcount=1830.
You have to check if that fits with your version / phone. Once downloaded, I copied both onto my SD card. So now I was able to install at least the new clean stock rom. Oh, and now I used the TWRP version 3.3.1.
Then I found this:
https://forum.xda-developers.com/galaxy-s9/development/root-s9plus-exynos-android10-t4065343
At first I tried to root without the SoLdieR9312's mod, only with MAGISK 20.3 and no-verity. Stuck again, it only bootet to download mode, nothing else. So flashed again the clean stock rom, and after first not keeping the right order (I suppose) I finally followed EXACTLY the instructions 1 - 4 in above manual including SoLdieR9312's mod (I highly recommend first a complete Wipe, format data, and then flash the clean new Rom with Android 10 and bootloader from above link).
Now, to save you the time I spent today: once your phone is bootet (and succesfully rooted via Magisk 20.3, which will happen automatically due to the SoLdieR9312's mod), DONT LET MAGISK UPDATE TO VERSION 20.4!!!! Magisk Manager asks you to update, but when I did update to 20.4, everything fell apart again, it only bootet to download mode.
Now I seem to have it stable and running with 20.3 and the [email protected]. I rebootet 5 times so far just for the sake of it, and it works fine and rootet.
If I can be of further help, please let me know. I spent the last 12 hours on this matter, so dont hesitate.
Greetz from me minus a bunch of nerves
PS: After I wrote the above, I deleted the Knox family in the rootet system, and then it collapsed again and, after BSoD, it only rebootet into download mode. I can not exclude the possibility, that this might have been the reason for some system breakdowns before, as I had to re-do the wipe-clean-install-then-root-then-customize worksteps aroung 8 times yesterday before it was stable as it is now. Now I´ll leave Knox on it, though that itches me a bit. But I´m exhausted for now
PPS: IMPORTANT when I try to create a PIN or a pattern for the lock screen, phone reboots to SIM card PIN screen and then keeps rebooting and rebooting. It looks like there are some interferences with root and PIN / security. I did NOT create a Samsung account, only a google one, cause in the beginning i suspected it might have been a Sam acct problem (I constantly couldnt log into it on the phone). Turns out that might not have been the case, rather a prob between root and setting a lock screen security.