I tried to flash TWRP using this guide: https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/
I do everything step by step, but every time after rebooting to recovery there is not TWRP but only stock recovery. I have unlocked bootloader. The device is active using the "fastboot devices" command. USB debugging mode is ON. Please help me solve this problem
install Magisk then official twrp app and flash twrp from the app to recovery
PanRyba said:
I tried to flash TWRP using this guide: https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/
I do everything step by step, but every time after rebooting to recovery there is not TWRP but only stock recovery. I have unlocked bootloader. The device is active using the "fastboot devices" command. USB debugging mode is ON. Please help me solve this problem
Click to expand...
Click to collapse
The only way it worked for me was to install official twrp app, and flash twrp-3.3.1-0-Armor_6.img from the app to recovery, then click on reboot to rrcovery also in the app.
Twrp will only be available one time after the reboot (so it is not really flashed)
(Adb flash recovery doesn't work for me)
In order to use official twrp app, i rooted with magisk
U welcome
I'm confused now. How did you root with magisk without TWRP. The Magisk installation was basically the only reason for me to flash TWRP
PanRyba said:
I'm confused now. How did you root with magisk without TWRP. The Magisk installation was basically the only reason for me to flash TWRP
Click to expand...
Click to collapse
Same as twrp
Install magisk app and do it from there:
Go to github website and download MagiskManager-v7.3.4.apk
https://github.com/topjohnwu/Magisk/releases
From the apk you will be able to flash your boot partition with magisk (it will save a boot image flashed with magisk on your phone)
The second step is simply to transfer that .img on your computer, install platform tools (in order to use adb command line)
Launch cmd.exe in platform tools folder
Connect your phone to computer via a usb cable and usb debug enabled
Type the command "adb devices" to check if your device is recognised (if a window appear on your phone to enable connection click ok)
Then type "adb reboot bootloader" (you are now in fastboot mode)
Then type "fastboot flash boot (then the name of your flashed with magisk boot image.img that you previously put in platforms tool folder in order to not search for the path)"
Then type "fastboot reboot"
Then from magisk manager app update magisk
That's it
No need for a recovery in the first place to root with magisk
finally works. thanks you dude. I really appreciate your help
PanRyba said:
finally works. thanks you dude. I really appreciate your help
Click to expand...
Click to collapse
You're welcome
Glad to help
PanRyba said:
I tried to flash TWRP using this guide: https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/
Click to expand...
Click to collapse
I also used that guide and couldn't get TWRP or Magisk to install on my new Armor 6E. I was able to use "Method 2" and SP Tool to flash TWRP 3.3.1-0, then I was able to flash Magisk using TWRP recovery.
I flashed Magisk-v20. 0(20000).zip
MD5 checksum: 56f82549e9f3c659a11f1f459e56489f
Now I seem to be stuck with the "Orange State" message at boot.
When I attempt to use TWRP to flash "no-verity-opt-encrypt-6.0.zip" I get the following :
-----
Installing zip file '[file path]'
Checking for Digest file...
Verifying zip signature...
Zip signature verified successfully.
##dm-verity and forced encryption disabler by jcadduono version 6.0##
Unpacking the installer...
Updater process ended with ERROR: 1
Error installing zip file' no-verity-opt-encrypt-6.0.zip'
Updating partition details...
... done
-----
The file has this MD5 checksum:
caea927e96c755f3568e85dbded88923
When I attempt to use TWRP to flash "orange_state_disabler_MTK Only.zip" I get the following:
-----
Installing zip file '[pathname]'
Checking for Digest file...
Verifying zip signature...
Zip signature verification failed!
Error installing zip file 'orange_state_disabler_MTK Only.zip'
Updating partition details...
... done
-----
That file has this MD5 hash:
30b01bb314d26643b6cc1dfce1d81cf5
I get nearly the same result when I attempt to install "ROMProvider.COM_orange_state_disabler 0.3.zip"
(Zip signature verification failed!)
That file also has the same MD5 hash:
30b01bb314d26643b6cc1dfce1d81cf5
TWRP asks for a password when I first boot into recovery. I also tried to contact them at the unofficialtwrp.com website (where I downloaded the zip files), but their contact page seems to loop back on itself.
Has anyone else run into this (and stuck with Orange State warning at boot)?
ndt44 said:
Now I seem to be stuck with the "Orange State" message at boot.
Click to expand...
Click to collapse
I was finally able to use TWRP 3.3.1 Install to flash file "ROMProvider.COM_orange_state_disabler_v0.3.zip" this morning and rid myself of the Orange State warning every single boot. NOTE: I had to UNCHECK zip file verification in TWRP Install in order to get it to work this time!!
This was my output:
-------------------------------
Installing zip file '[pathname]'
Checking for Digest file...
--- 'Orange State' disabler v0.3 - - -
##### Created by XopmoH97 #####
Current zip - > 'ROMProvider.COM_orange_state_disabler_v0.3.zip'.
Unzipping binaries to '/tmp'...
Success!
Set execute flag to 'tmp/sed-arm'.
Set execute flag to 'tmp/xxd-arm'.
Checking CPU architecture...
CPU architecture 'arm64-v8a' is supported!
Searching 'lk' block in GPT...
Success! 'lk' block = '/dev/block/mmcblk0p27'
Saving '/dev/block/mmcblk0p27' to '/tmp/lk.img'...
Testing NEW algorithm...
NEW algorithm is available!!!
Patching '/tmp/lk.img'...
Success!
Writing '/tmp/lk.img' to '/dev/block/mmcblk0p27'...
Success!!! Please reboot your device!
Updating partition details...
... done
-----------
Unfortunately, the no-verity.ZIP still will not flash!
ndt44 said:
I was finally able to use TWRP 3.3.1 Install to flash file "ROMProvider.COM_orange_state_disabler_v0.3.zip" this morning and rid myself of the Orange State warning every single boot. NOTE: I had to UNCHECK zip file verification in TWRP Install in order to get it to work this time!!
This was my output:
-------------------------------
Installing zip file '[pathname]'
Checking for Digest file...
--- 'Orange State' disabler v0.3 - - -
##### Created by XopmoH97 #####
Current zip - > 'ROMProvider.COM_orange_state_disabler_v0.3.zip'.
Unzipping binaries to '/tmp'...
Success!
Set execute flag to 'tmp/sed-arm'.
Set execute flag to 'tmp/xxd-arm'.
Checking CPU architecture...
CPU architecture 'arm64-v8a' is supported!
Searching 'lk' block in GPT...
Success! 'lk' block = '/dev/block/mmcblk0p27'
Saving '/dev/block/mmcblk0p27' to '/tmp/lk.img'...
Testing NEW algorithm...
NEW algorithm is available!!!
Patching '/tmp/lk.img'...
Success!
Writing '/tmp/lk.img' to '/dev/block/mmcblk0p27'...
Success!!! Please reboot your device!
Updating partition details...
... done
-----------
Unfortunately, the no-verity.ZIP still will not flash!
Click to expand...
Click to collapse
The Orange State disabler zip is news to me, and it sounds worthwhile to flash.
I successfully flashed the DM-Verity zip from an OTG USB drive after using TWRP to format the system and data partitions to EXT4. No success with ROMs yet.
Pergmen said:
The Orange State disabler zip is news to me, and it sounds worthwhile to flash.
I successfully flashed the DM-Verity zip from an OTG USB drive after using TWRP to format the system and data partitions to EXT4. No success with ROMs yet.
Click to expand...
Click to collapse
mvyrmnd said:
The 6 and 6E are very similar devices. The TWRP listed here works on the 6E. Magisk also works as described.
I cannot confirm for the 6 (but is likely), but the 6E works with all phh-based GSI ROMs.
These phones use A/B images.
Click to expand...
Click to collapse
Can't post links even when quoting so you just have to google "treble project github"
I have gotten roms to work (use A/B even if treble check says its only A for somereason).
I wasn't able to get liniageOS to work (from the pie roms, i think everyting else seems to work) and android Q ones even thou it should be able to from what i have gathered.
IMPORTANT! It seems like every rom is missing basic features like gestures, i dont know if it has to do with the kernel maybe? Im nubie.
VERY IMPOTANT!! Lost my IMEI number from messing around with the phone so be careful! Im not responsible.
Pergmen said:
The Orange State disabler zip is news to me, and it sounds worthwhile to flash.
I successfully flashed the DM-Verity zip from an OTG USB drive after using TWRP to format the system and data partitions to EXT4. No success with ROMs yet.
Click to expand...
Click to collapse
Would it be possible to get an MD5 checksum and filename which worked for you so that I might compare them? Did you get that file from the unofficial twrp page linked above then? Also were the "system and data EXT4 partitions" on the phone Internal Storage or the USB OTG?
ndt44 said:
I was finally able to use TWRP 3.3.1 Install to flash file "ROMProvider.COM_orange_state_disabler_v0.3.zip" this morning and rid myself of the Orange State warning every single boot. NOTE: I had to UNCHECK zip file verification in TWRP Install in order to get it to work this time!!
Click to expand...
Click to collapse
I obtained this file here:
https://www.google.com/amp/s/rompro...ange-state-fixer-fix-orange-state/amp/?espv=1
I just ordered this armor 6e phone. I will be able to answer my own question next week, I suppose. Bit, in the armor 6 thread it is mentioned few times that there twrp works on 6e, now I found this thread, which says twrp will not stay flashed to phone.
Which one is correct?
If the armor 6 twrp does work, does it work to flash gapps? Because the y is not pie, and as such is not system-as-root, which from other devices, I know that makes recovery see the phone file structure different
Ie : /system_root/system not just /system
This difference needs different build of twrp.
I will give it a try when I receive it I suppose.
mrmazak said:
I just ordered this armor 6e phone. I will be able to answer my own question next week, I suppose. Bit, in the armor 6 thread it is mentioned few times that there twrp works on 6e, now I found this thread, which says twrp will not stay flashed to phone.
Which one is correct?
If the armor 6 twrp does work, does it work to flash gapps? Because the y is not pie, and as such is not system-as-root, which from other devices, I know that makes recovery see the phone file structure different
Ie : /system_root/system not just /system
This difference needs different build of twrp.
I will give it a try when I receive it I suppose.
Click to expand...
Click to collapse
I have found a TWRP that stays on. And i have seen some that dont stay. Im able to flash gapps with it to my 6e.
poohju said:
I have found a TWRP that stays on. And i have seen some that dont stay. Im able to flash gapps with it to my 6e.
Click to expand...
Click to collapse
Thanks. Do you have links?
mrmazak said:
Thanks. Do you have links?
Click to expand...
Click to collapse
First maybe try out the unofficial TWRP (https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/) maybe it works. I think i didnt get it to stick but its worth a shot ig and you can also try with the TWRP app (havent tried the app way). Sadly i dont remember where i got the file that sticks for me. If unofficial dosent work i can upload it to somewhere. I used ADB tools to download TWRPs. If you use SP tools to flash it while like doing a fresh install. It will go to RED state. You can use SP tools if you first install stock then unlock bootloader and flashing then only installing the recovery. You can install gapps mostly but u cant use dm veryeti disabler it messes with the IMEI at least for me. Im not that savy to know how to fix it. Its my first phone ever messing with. MAGISK works.
poohju said:
First maybe try out the unofficial TWRP (https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/) maybe it works. I think i didnt get it to stick but its worth a shot ig and you can also try with the TWRP app (havent tried the app way). Sadly i dont remember where i got the file that sticks for me. If unofficial dosent work i can upload it to somewhere. I used ADB tools to download TWRPs. If you use SP tools to flash it while like doing a fresh install. It will go to RED state. You can use SP tools if you first install stock then unlock bootloader and flashing then only installing the recovery. You can install gapps mostly but u cant use dm veryeti disabler it messes with the IMEI at least for me. Im not that savy to know how to fix it. Its my first phone ever messing with. MAGISK works.
Click to expand...
Click to collapse
Thanks. I looked at unofficial, and unpacked there image. It is set to terrible enabled = no, and is not setup for system-as-root.
Also the prop file says it is for armor 6 not 6e, so I will just build fresh one and use that.
mrmazak said:
Thanks. I looked at unofficial, and unpacked there image. It is set to terrible enabled = no, and is not setup for system-as-root.
Also the prop file says it is for armor 6 not 6e, so I will just build fresh one and use that.
Click to expand...
Click to collapse
Good luck to you maybe you can share it when your done
poohju said:
Good luck to you maybe you can share it when your done
Click to expand...
Click to collapse
My phone is still not delivered. But I did compile twrp from source, using the September update files from ulefone site.
I started with the device tree from the armor 6, and made few changes that I have found to work for treble devices and system as root on other recent mtk phones I have.
But I can't confirm the build works. If you want to beta test it, let me know.
Related
Hello, im new so please dont cut my head off if i am not posting in the correct area, i was in the PPH's SU/SafetyNet thread in which is marked as a DEV ONLY area, so i could not ask my question there.
http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394/post68969947#post68969947
So, my question... quoted from: (thread)
http://forum.xda-developers.com/showpost.php?p=68999657&postcount=352
Major thanks to .NetRoller 3D. Here are my steps. DISCLAIMER. Not responsible for any problems. I have a STOCK HTC 10 ROM. Not a custom ROM. These steps could result in problems if you have any non-STOCK ROM because it's a Stock Boot.img that gets flashed. I recommend NOT doing this on a Custom ROM (If anyone knows for sure, please correct me)
My Device: HTC 10 Unlocked
Previous Setup:
Magisk V7
PHH SuperUser Magisk version
No Xposed Installed as it never worked for me with PoGo
I used:
PHH Superuser-hideSU (.NetRoller 3D linked to it in his post) Edit: Here's his link
http://forum.xda-developers.com/andr...7#post68969947
Steps:
1. Reboot into TWRP.
2. Flash LATEST Magisk Uninstall zip in the Magisk Thread.
3. Reboot
4. Wait for Android to Upgrade...
5. Reboot into TWRP
6. Flash boot.img from a non-rooted nandroid backup. I didn't wipe data, I just unchecked everything but "boot"
7. Reboot to System.
8. My PHH Superuser App was uninstalled already, but if yours isn't, wait and then Uninstall it like a Normal App. Check Safetynet, and it should pass at this point. If not Reboot, and check again.
9. Reboot into TWRP
10. Flash PHH-SuperUser-HideSU (NOTE: You shouldn't need a separate SuperUser Zip. This has SU and HideSU in one)
12. Reboot
13. Re-install PHH Superuser from PlayStore. Grant your root priveleges as needed. SafetyNet should pass and you should have full Root AND PoGo/Android Pay
Click to expand...
Click to collapse
Click to expand...
Click to collapse
My device is a Samsung Note 5 (920T) that was running magiask systemless root, but since the recent SafetyNet updates ive been forced to stop playing PoGO, and just been following all the threads here about the lockout. I was excited to read this news and decided to prep my device by removing Magiask Systemless root and reflashing the stock rom, which is all works fine.
Ive even downloaded PoGO, Snapchat etc. (Apps the flag rooted devices) and they all work fine, passing Safety Nets check meaning i am 100% non rooted..... now im ready to mount the PPH's SU-r66.zip, and for some reason I seem to be the only person experiencing bootloop on the Samsung Galaxy Note 5 start up screen. My steps:
1. Reboot into TWRP..................... {OK}
2. Flash LATEST Magisk Uninstall zip in the Magisk Thread................{OK}
2a. FLASH "N920TTMB3DPG1" {MY STOCK ROM ver.} via ODIN.........{OK}
3. Reboot................{OK}
4. Wait for Android to Upgrade............{OK}
4a. FLASH "twrp-3.0.2-0-nobleltetmo.img.tar" via ODIN (because 2a. resets my recovery to stock)..........{OK}
5. Reboot into TWRP...............{OK but NOTE ***** at bottom}
6. Flash boot.img from a non-rooted nandroid backup. I didn't wipe data, I just unchecked everything but "boot"
^By this im assuing the file "superuser-r266-hidesu.zip"
{ERROR} ~ Flashing in TWRP
Click to expand...
Click to collapse
LOG from INSTALL in TWRP:
...Updating Partition details...
...done
Full SELinux support is present
MTP Enabled
INSTALLING - superuser r266 etc.. zip file
checking for MD5 file
skipping md5 check: no md5 file found
installing seSUperuser
sesuperuser found: booting img @ dev/blockplatform
15570000.ufs/by-name/boot
sesuperuser: generated /new-boot.img
{RED}UPDATED PROCESS ENDED WITH AN ERROR
ERROR INSTALLING ZIP FILE SUPERUSER R266.ZIP
{WHITE}updating partition details
...done
Click to expand...
Click to collapse
7. Reboot back to TWRP main options by pressing home button.
7a. RE-Flash same boot.img from a non-rooted nandroid backup from step 6.)...
{NEW MESSAGE}
LOG:
...Updating Partition details...
...done
Full SELinux support is present
MTP Enabled
INSTALLING - superuser r266 etc.. zip file
checking for MD5 file
skipping md5 check: no md5 file found
installing seSUperuser
sesuperuser found: booting img @ dev/blockplatform
15570000.ufs/by-name/boot
sesuperuser: generated /new-boot.img
sesuperuser: Successfully flashed root-ed boot.img
Updating partition details
....done
Click to expand...
Click to collapse
8. Reboot to System..............{BOOTLOOP}
...now one thing i noticed is that i am getting a bootloop when i first flash to TWRP to my stock rom. Ive tried with two different versions (twrp-3.0.2-1-noblelte.img; my pre existing and twrp-3.0.2-0-nobleltetmo.img.tar) which i downloaded today just to test and see if im still getting the first bootloop at step 5.) NOTE **** suggest.
and briefly what i mean by that is at that step, if i dont go to TWRP recovery immediately from the initial FLASH of TWRP and reset from step 4a.), it bootloop there already. I want to note that because as you can see in the logs the first time in Flash the PPH zip file i get a {RED} error code in TWRP's INSTALL console log, but the 2nd time always passes with a successful root-ed img in INSTALL console...
so... i dont know what to be or if anyone is have similar problems as ive heard that its a bit problematic for Samsung devices.
Any help family? Thanks for the reading, patience and understanding.
Hi to all. I'm new in Honor world and I've stopped my Android experience with KitKat so I'm a little bit confused ...
I've read several guides (on XDA too) that that three steps to obtain root are unlock bootloader, flash TWRP via ADB and then install Magisk or SuperSU via TWRP. But in the thread on TWRP is clearly written that to install Magisk decryption is needed and to have decryption we must flash a kernel with encryption disabled in fstab. But no guide says anything about this step. Can someone explain me how encryption/decryption work doing a standard installation of TWRP ? Is needed a flash of a modified kernel ? And where find it ?
And another question (if it's not too much ). Since I don't need to install custom rom (I want root only to use some apps like Titanium) how can I make a backup of stock rom, boot.img, efs partition and all that can be useful to restore phone to the starting point if, by chance, I need Huawei warranty ?
Thanks a lot
Hi, apparently there's a way to get root on an encrypted system. Follow the rebrand guide and then flash supersu in TWRP via ADB sideload. It worked for me and a few others, there is no comment from the developers as of right now.
So basically in short follow this guide until you are finished with the TWRP section:
https://forum.xda-developers.com/honor-9/how-to/one-guide-recovery-os-roms-t3661829
Then
- enter twrp
- adb sideload supersu
Afterwards follow the "rooting!" section with point 2
Thank for your answer... I'd like to try to install Magisk instead of SuperSU. In several places is written that this should be right. I'll try....
unvisigoth said:
Thank for your answer... I'd like to try to install Magisk instead of SuperSU. In several places is written that this should be right. I'll try....
Click to expand...
Click to collapse
The method is also working fine with Magisk. Let me know if you need help
zxz0O0 said:
The method is also working fine with Magisk. Let me know if you need help
Click to expand...
Click to collapse
Finally done with a couple of hours of panic. This is the story if can be useful to someone...
Unlock bootloader....done TWRP install... done. Copy magisk (apk and zip) on phone than install apk without opening it. Reboot to recovery wipe all, factory reset. Trying to boot.....BOOTLOOP But I don't have installed Magisk zip. Only apk without opening it.
Nothing to do. Bootloop and then erecovery. I try to restore the backups previously done with TWRP. I restore boot and system partition. All wipes ...no luck. I don't know what has happened. While downloading full firmware to try to reinstall it I try to install magisk.zip. Install via TWRP. All wipes and then magically (it's such a case ) phone boots. Powered off and on several times no problem. Root (verified with root checker) ok.
I habe b100 release but I don't think to update to b130. I wait for Oreo...
The only two things that I can say are these: first TWRP even after flashing magisk gave an error (unable to mount system). Two while installing magisk it seems that magisk itself has patched something.
If someone has an explanation is welcome...
unvisigoth said:
Finally done with a couple of hours of panic. This is the story if can be useful to someone...
Unlock bootloader....done TWRP install... done. Copy magisk (apk and zip) on phone than install apk without opening it. Reboot to recovery wipe all, factory reset. Trying to boot.....BOOTLOOP But I don't have installed Magisk zip. Only apk without opening it.
Nothing to do. Bootloop and then erecovery. I try to restore the backups previously done with TWRP. I restore boot and system partition. All wipes ...no luck. I don't know what has happened. While downloading full firmware to try to reinstall it I try to install magisk.zip. Install via TWRP. All wipes and then magically (it's such a case ) phone boots. Powered off and on several times no problem. Root (verified with root checker) ok.
I habe b100 release but I don't think to update to b130. I wait for Oreo...
The only two things that I can say are these: first TWRP even after flashing magisk gave an error (unable to mount system). Two while installing magisk it seems that magisk itself has patched something.
If someone has an explanation is welcome...
Click to expand...
Click to collapse
So do you have some step-by-step instructions for someone who wants to unlock and root the phone with magisk?
shiboby said:
So do you have some step-by-step instructions for someone who wants to unlock and root the phone with magisk?
Click to expand...
Click to collapse
Here what I have done:
Unlock bootloader
install adb drivers (find something that is right for your PC. For example minimal ADB found on XDA weren't suitable for me. Google adb drivers...). Open a command windows (shift+right click). If typing "adb devices" your phone is found that's ok
Enable usb debugging and oem unlock (or in other words disable FRP, factory reset protection)
Put the phone in fastboot mode ("adb reboot bootloader"). If all ok typing "fastboot devices" your phone is found
Type "fastboot oem unlock xxxxxxxx" (xxxxxxxx is the code provided by Huawey)
Bootloader unlocked
Flash TWRP
Download TWRP recovery for Honor 9 (link found on other thread on this forum)
Put the phone in fastboot mode
Type "fastboot flash recovery xxxxx.img" (where xxxx.img is the recovery downloaded)
Reboot phone directly in Recovery to avoid erecovery overwrite TWRP. Booting on TWRP let TWRP patch to avoid erecovery booting
Now here I've had some issues as said (read previous post). My tip is the following:
after rebooting in TWRP make all wipes then reboot again in TWRP
Install Magisk.zip (for me download here https://geekaxe.com/root-honor-9-twrp-bootloader-unlocking/)
Reboot recovery
All wipes
Reboot to system
If it's all OK you can install magisk.apk and you are rooted
I suggest after flashing TWRP to make backup of all partitions on external SD (for some reasons, maybe encryption, backup on internal storage gives error). Again I suggest to copy all files that you need (i.e. magisk files) on external sd before starting all.
Pay attention that if you update firmware after this procedure I think that you must repeat all. For me I remain on original firmware found on phone (B100). B130 seems to have some bugs, B120 doesn't seem improve much. Moreover all releases are 7.0 based. I wait for Oreo, hopefully in some custom rom!
To add to this, a bootloop or two might be normal. Let it sit for a few minutes before considering re-flashing everything.
Thanks for your guide!
Zuzler said:
To add to this, a bootloop or two might be normal. Let it sit for a few minutes before considering re-flashing everything.
Thanks for your guide!
Click to expand...
Click to collapse
You're right. But after 20 minutes of bootlops I've chosen another way....:laugh::laugh:
unvisigoth said:
You're right. But after 20 minutes of bootlops I've chosen another way....:laugh::laugh:
Click to expand...
Click to collapse
So is it fixed?
Sent from my Honor 8 Pro using XDA Labs
adriansticoid said:
So is it fixed?
Sent from my Honor 8 Pro using XDA Labs
Click to expand...
Click to collapse
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
unvisigoth said:
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
Click to expand...
Click to collapse
Observe and be careful man.
Sent from my Honor 8 Pro using XDA Labs
unvisigoth said:
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
Click to expand...
Click to collapse
Which TWRP version did you use?
I had a similar problem after formatting all data with the OpenKirin TWRP 3.1.1 Perhaps its an issue with this TWRP release?
I was able to recover in similar circumstances by flashing a stock boot.img over fastboot. Based on this, it's looking like Magisk is really the way to go for rooting atm. Making sure to pull my twrp backup with adb this time though.
If I'm lucky enough to install magisk and not get a bootloop the safetynet always fails. Anyone got a valid method of actually getting magisk working fully?
This is basically a copy of my Z380M TWRP thread adopted for the ZenPad 10. I decided to start a new one since the OP of justshaun's original recovery/rooting thread has gone stale, even as I had posted several new releases of TWRP over the months. Its instructions are also a little outdated. I've also compiled a version for the new Z301M(F) models and needed a place to post it. This is where I will be posting TWRP updates from now on.
In addition to this thread, referring to the Z380M TWRP thread and the original Z300M thread (links above) may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the others.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows or Linux PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)
MediaTek VCOM drivers (available through Windows Update)
ZenPad 10 scatter file for SPFT, attached (choose the one for your tablet)
Recovery image, attached (choose the one for your tablet)
ZenPad Z300M, Z301M or Z301MF tablet upgraded to Android N
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 10.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image for your device (twrp-3.2.1-0-z30*m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z30*m.img
Once inside TWRP, flash twrp-3.2.1-0-z30*m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". On the Z301M/Z301MF, that option is labeled Factory Reset. Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
WARNING 2: Make sure you use the correct scatter file for your device (i.e. don't mix up the Z300 and Z301 files). For the initial flash, there is no check for scatter file correctness. If you use the wrong one, SP Flash Tool will alter and lock your GPT to that scatter file layout, possibly bricking your device. It will not be easy to restore it. Flashing with the correct scatter file later on will not work because Flash Tool will not allow you to use a different file than the one you used initially.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
SP Flash Tool v5.1532
Z300M Scatter file for all storage sizes (right click, Save link as...) -- do not use for other models
Z300M TWRP 3.2.1-0 image -- updated March 15, 2018
Z301M(F) series Scatter file for all storage sizes (right click, Save link as...) -- do not use for Z300M or other devices
Z301M TWRP 3.2.1-0 image -- updated March 13, 2018
Z301MF TWRP 3.2.3-0 image -- updated August 29, 2018
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Heya, thanks for the new thread..
Stupid question(coming from Samsung flashing)
Ive got Zenpad S3 10 P027, is this TRWP not ideal for this?
Currently, have some su (root) issues. Recovery shows Android icon chest with ! and says "No Command"
When running su in Terminal ADB via PC, says command not recognized.
Looks like I need to reflash recovery. When in TRWP (launched via fastboot boot twrp on PC) I flashed stock recovery but had system mounted read only. Could that be the problem?
Bro, I think you need to do some more homework on root, su, dm-verity, mods, etc. and read the instructions more carefully before applying these hacks. You are making a lot of simple mistakes and ending up shooting yourself in the foot for it. I don't think there's anything wrong with the Z500 TWRP. It can handle installing the stock firmware just fine. The problem is elsewhere. The unlock tool also works fine in TWRP as well in my testing.
The No Command screen is normal. That's been answered many times... you need to hold power+vol. up (or down) to get to the menu. There is no way the stock recovery image can be broken and still boot up.
The su thing, IDK what the problem is, but I'm sure if you install Magisk Manager and make your own patched image from your currently installed firmware, and fastboot-boot with it, you will have su functionality. Just like what it says in the unlock tool instructions.
Lastly and most important, never mount system in read-write mode, as I've repeated several times and exactly as it says in the directions:
7. At the TWRP welcome screen, do not select to modify the system partition and touch Keep System Read-only instead. Doing otherwise will render your tablet unbootable.
8. Mount system in TWRP (in read-only mode)
Click to expand...
Click to collapse
The only time you can mount it in read-write mode is when you are absolutely sure you have disabled dm-verity in your boot image.
I've successfully installed TWRP on Z301M using the instructions from the first post, but then I somehow managed to lose the system. Yes, I should have backed up like the OP suggests.
I thought I should be able to reinstall the original firmware downloaded from Asus (e.g. UL-ASUS_P028_1-WW-3.3.12.0-user.zip) but both the 'adb sideload' method and the TWRP failed to install that firmware zip. My device looks bricked. The only thing I can do is to boot into TWRP (I actually need to select Factory Reset on the bootloader screen to get into TWRP). The folder 'system' is empty.
Can anyone suggest what I am doing wrong when trying to restore the Asus firmware?
When I try to sideload the zip, setting TWRP in the sideload mode, the computer begins uploading but after a few seconds gives the message "Total xfer: 0.01x" and stops, while Android errors with "set boot part fail. can not open misc-sd".
When I install the firmware zip from TWRP it also starts installing fine but shortly gives the same error "set boot part fail. can not open misc-sd".
Thanks
@ahacker, first of all, thank you for the feedback on the Z301M platform. You are literally the first person to have said anything about that version of TWRP.
To see the files on system, you first have to mount the system partition. Did you do that? If not, I suggest mounting it read-only. If there was any corruption on it, then reinstalling the firmware should have fixed it. The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
At which point did it stop booting? Also, did you use the scatter file from first post? And can you tell me if the touch screen works fine in TWRP on your tablet?
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
diplomatic, thanks for replying!
diplomatic said:
[MENTION=4776997]
To see the files on system, you first have to mount the system partition. Did you do that?
Click to expand...
Click to collapse
I do mount the system partition. It appears empty. When I reboot into system TWRP says that the OS is not installed.
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
I would indeed try to mount the system read only. This is not the first Android system I rooted (maybe fifth), and I was always able to restore the system either from sideload or recovery. But here it seems Asus is making us jump extra hoops to do that.
diplomatic said:
[MENTION=4776997]
Reinstalling the firmware should have fixed it.
Click to expand...
Click to collapse
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
diplomatic said:
[MENTION=4776997]
The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
Click to expand...
Click to collapse
Thank you for the information.
diplomatic said:
[MENTION=4776997]
Also, did you use the scatter file from first post? Does the touch screen work fine in TWRP on that tablet?
Click to expand...
Click to collapse
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
diplomatic said:
[MENTION=4776997]
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
Click to expand...
Click to collapse
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
---------- Post added at 01:19 AM ---------- Previous post was at 12:57 AM ----------
Now system refuses to mount
ahacker said:
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
Click to expand...
Click to collapse
Er, the password should have been for decrypting your userdata. If you didn't have one set up, there might be something wrong there.... Or possibly just unformatted.
ahacker said:
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
Click to expand...
Click to collapse
Yeah, that has to be the right one. The installation script has to match the model name reported by the recovery. Otherwise it would simply abort.
ahacker said:
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
Click to expand...
Click to collapse
Great! Guess my kernel patch was on the dot and the partition layout has not changed from the Z300.
ahacker said:
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
Click to expand...
Click to collapse
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
diplomatic said:
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
Click to expand...
Click to collapse
I've tried both ways, with and without system mounted, a few times. The installation would fail after something like 5 seconds.
diplomatic said:
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
Click to expand...
Click to collapse
I think I am giving up on this cheap tablet. I cannot even format it in the Flash Tool: it says "To format code area is forbidden on this phone". Asus is forbidding too much for me to ever buy it again. Attached the logs.
Thanks, diplomatic
OK, found the problem. Check your PMs, ahacker.
diplomatic said:
OK, found the problem. Check your PMs, ahacker.
Click to expand...
Click to collapse
I have replied (twice), but the reply does not appear in my Sent Items. I hope it has reached you. If not, I'll paste the reply here, if you don't mind.
i not understand... i have Asus ZenPad 10 LTE Z301MFL.. a root method has been released ???
@diplomatic
Would this be compatible with Z0310M ? can't find anything for this damn model...
Hi, NeBouse,
Are you sure you have the correct information? It looks like just a misspelling of Z301M, aka P028....
I have z301m.
One thing that was a surprise for me is that the TWRP recovery flashed with the method described in the original post does not stick. You have to flash it each time you use it. If you are like me this information is important, because the original recovery plainly wipes your data without asking or warning.
After you have flashed TWRP on the device, to go to the recovery mode you have to chose "Factory Reset" in the bootloader. Then it will complain about wrong OS, which is the sign that flashing TWRP worked; choose 'yes'. The first thing you should do in TWRP is a ful nandroid backup. (Not listening the OP's advice about backing up when Installing TWRP with a wrong scatter file almost cost me the device. Thankfully diplomatic managed to remotely fix my problem, probably spending a lot of his personal time. The scatter file in the original post is a correct one now.)
Creating a nandroid backup in TWRP takes unusually long time, I even once decided that it hanged. Taking long time, like 10-30 minutes, for a full backup is normal.
Asus Z300M , Magisk 16.3 (beta) and FW 5.3.19 WW now works!
z301m, WW-3.3.12.0 firmware
For rooting I've installed in TWRP Magisk v15.3 (diplomatic warned against 16.x, someone else against 15.4) - link.
Installed in TWRP xPosed framework 88.2 - link, and xPosed Installer apk from within Android - link.
So far, so good.
What I've found is that TWRP seems to have problems with external sd cards (lots of fs corruption). I found it safer to unmount by hand by unticking the sd card checkbox in "Mount". Not very conclusive about this though.
Thanks, ahacker. Good feedback. Although to be fair, I didn't say to avoid Magisk 16.x. I said 16.0. I'm pretty sure whatever bug it had is already fixed in the latest version.
Now that you've installed root, TWRP will stick around on the emmc. The stock recovery only gets installed if you have the original unpatched boot image on it. I mean, this is not unique to these devices. That's been standard Android functionality since some 4.x or 5.x version. And this is essentially what's in the warning on the OP.
The backup I'm talking about in the installation method is done with the SP Flash Tool readback function. That will pull the partition tables and your device's "metadata" that's unique to your unit. I don't think nandroid covers that...
Oh, and what is this SD corruption you're talking about? What file system is it formatted in? Have you checked your card for errors in Windows?
Asus releases so many difference Z301M model, so I am curious if this also works on Z301MF model?
Notice Z300MF has the MTK8163BA (or MTK8163A?) CPU model while Z301M uses : 8163B
Anyone tested that already? Thanks.
my zenpad 10 has frp lock. it this a solution to remove the frp lock?
Pls help how i flash original software via fastboot ?????
Requirements / Downloads
Honor 10 view BKL-09 with unlocked bootloader (I not tested in other version)
Minimal ADB & Fastboot
Patched Recovery_Ramdisk BKL
Rooting your device
1. Unzip Minimal ADB & Fastboot to any folder of your PC
2. Download the patched file for your device and copy it to Minimal ADB & Fastboot folder.
3. Start your smartphone in fastboot mode pressing [Vol-]+[Power] and connect it to your PC.
4. Open a Powershell window in your Minimal ADB & Fastboot folder by [Shift]+[Rightclick].
5. Flash the Recovery_Ramdisk:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
Adjusting Magisk Manager and patching files by yourself
1. Download Magisk Manager canary build to your phone and install.
2. Change in Magisk settings the update channel to "custom" inserting this URL. https://t2m.io/wuAFCrwO
Magisk Manager now will find the canary builds.
3. Check "force encryption" and "AVB 2.0" boxes.
To patch yourself recovery_ramdisk:
4.a) Patch your *.img, that you have copied in any folder to your smartphone by pressing "Install" --> "Install" --> "Patch boot image" in Magisk Manager.
ORIGINAL RECOVERY_RAMDISK BKL-09 PIE version 9.0.0.162 C432
5. Transfer the patched file (You will find it in your download folder of your smartphone. It will be called "patched_boot.img".) to your PC, start Smartphone in fastboot mode and flash:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
(You must adapt the file name to the real name of your file, e.g. patched_boot.img)
To actualize Magisk:
4.b) Choose in Magisk Manager: "Install" --> "Install" --> "Direct Install (Recommended)" --> Restart
Thanks
Thanks a lot for this great guide!
Hello, will this also be on my bkl-l09c432? I have rom
blazios said:
Hello, will this also be on my bkl-l09c432? I have rom
Click to expand...
Click to collapse
If your device is on pie ?, yes
What should I use twrp?
blazios said:
What should I use twrp?
Click to expand...
Click to collapse
OP never mentioned anything about twrp. That is not needed
I Have same version as you Android Pie and everythin firmware and region... But no matter how i try i get UNABLE TO UNPACK BOOT IMAGE... Instalation failed... why is that? i have TWRP installed... and everything as is your phone firmware and version 9.0.0.162 C432...
BlueMan_86 said:
I Have same version as you Android Pie and everythin firmware and region... But no matter how i try i get UNABLE TO UNPACK BOOT IMAGE... Instalation failed... why is that? i have TWRP installed... and everything as is your phone firmware and version 9.0.0.162 C432...
Click to expand...
Click to collapse
Flash in bootloader mode. Not in twrp.
Android pie not work with twrp for now.
I am on ROOTED EMUI 8.0 (BKL-L09 8.0.0.130). How do I update to pie and then root? First unroot than update than root? or just update and root with the instructions in post#1?
Sadly it does not work for me. Tried it with your patches bootimage and with my own. Flashing the ramdisk works fine but after restart I don't have root.
I dont need Magisk installed if I use the pre patches bootimage right? Nevertheless I tried with Magisk installed and without. In the Huawei Mate Forum I read that one might need to shutdown the phone after flashing and then to start it with Volume Up and Power Button pressed. But this also does not work. Or any Idea how exactly to start with this Key combination?
Any other suggestions?
Today I updated from OREO with root to PIE same version as you have in pictures 9.0.0.162(C432E4R1P9). Tried both steps (with your patched file and me patching file) to root my phone but even I always got OK in fastboot mode I still have no root
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
resdano said:
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
Click to expand...
Click to collapse
I get the same error
any advise ?
Worked like a breeze for me. Shoutout to @ante0 and @shashank1320 who kept their calm in guiding me through and suggesting me this method.
@ante0 made things easier for me and it worked excellently for me. The steps are-
Download and install Magisk canary builds from the mentioned link. Change in Magisk settings the update channel to "custom" inserting*this*URL.*https://t2m.io/wuAFCrwO
Magisk Manager now will find the canary builds.
Check "force encryption" and "AVB 2.0" boxes.
Transfer stock recovery ramdisk to phone, open Magisk Mnager and hit install - > patch boot image, select recovery_ramdisk.img. Take patched_boot.img from /sdcard/Download/ and transfer to computer, reboot to fastboot and flash patched_boot.img to recovery_ramdisk. Unplug USB, holv vol up + power to reboot to recovery, which will now boot phone with Magisk. If you reboot and don't hold vol up it will boot to system without root.
---------- Post added at 02:08 PM ---------- Previous post was at 02:01 PM ----------
Huge thanks @fabio84
Finally have root privileges on Pie.
resdano said:
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
Click to expand...
Click to collapse
davidsiv said:
I get the same error
any advise ?
Click to expand...
Click to collapse
Emui9 doesn't have a ramdisk partition. You flash to recovery_ramdisk, then when you reboot hold volume up to get to recovery (unplug USB as it will take you to erecovery if you have it plugged in).
This is the only way to get root on Emui9, currently.
It will not boot to recovery, it will boot to system with Magisk.
Not flash ramdisk. Need flash recovery_ramdisk!
worked, thanks
fabio84 said:
Not flash ramdisk. Need flash recovery_ramdisk!
Click to expand...
Click to collapse
@ante0 has been helping me get root access and we still are working on it.
@fabio84 did you by a chance experience issues in using root applications especially root explorer or root Uninstaller? For some reason they won't just work for me, just titanium and root checker works. On further scrutinising, I found the su binary files missing probably why the applications won't load for me. Any help?
ankan1993 said:
@ante0 has been helping me get root access and we still are working on it.
@fabio84 did you by a chance experience issues in using root applications especially root explorer or root Uninstaller? For some reason they won't just work for me, just titanium and root checker works. On further scrutinising, I found the su binary files missing probably why the applications won't load for me. Any help?
Click to expand...
Click to collapse
Update: @ante0 helped me yet again to figure it out. Apparently was because of pie's aggressive background restrictions. Root is now working full fledgedly. Thanks everyone. Big cheers to @ante0
Hello,
It finally worked for me. Thank you so much!
ante0 said:
Emui9 doesn't have a ramdisk partition. You flash to recovery_ramdisk, then when you reboot hold volume up to get to recovery (unplug USB as it will take you to erecovery if you have it plugged in).
This is the only way to get root on Emui9, currently.
It will not boot to recovery, it will boot to system with Magisk.
Click to expand...
Click to collapse
Here's how to root the Pixel 3 running on official and stock Android 10 release, step by step :
(not tested on Pixel 3 XL but it might work the same, just use the right firmware for your device)
What do you need :
> Pixel 3 phone with Android 10
> Unlocked bootloader on your Pixel device
> Latest ADB and FASTBOOT tools on your computer
1 ) Download the latest Android 10 factory image for your device ("Blueline" is the regular Pixel 3) :
Link > Android 10 factory image
2 ) Extract the "boot.img" file on your phone
3 ) Download latest Magisk Manager application on your phone and install it :
Link > https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched
5 ) Enable adb debugging on your Pixel phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
9 ) When i'ts done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings and rebooting your phone.
Note that this guide is actually for using adaway. I don't know if it will work for any other root related feature on your phone.
Great guide, thanks!
ibolito said:
11 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings.
Click to expand...
Click to collapse
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
bafforosso said:
Great guide, thanks!
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
Click to expand...
Click to collapse
Thanks its done!
I get a "This site can't be reached" message when I click the link for magisk manager in step 3. Not sure if anyone else sees it.
Thank you for making this guide!
Thanks, works perfectly!
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Oberbergler said:
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Click to expand...
Click to collapse
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
If I updated via ota adb side load to 10. But used the boot.img from the factory image, would this explain why it did boot, however not one app would start. The system ui would then crash. Just trying to figure out where I screwed up. Thank you.
ibolito said:
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
Click to expand...
Click to collapse
Thanks man Everything was right but I forgot to update adb and fastboot. Now I have root
ignore me -- im idiot.
i am not sure if my pixel 3 is really rooted. all the apps requiring root says they are granted root access, but, for example, i cannot modify system files with a root file manager at all unlike i could with android 9. how can i confirm it is surely rooted?
So I have a problem, maybe someone can help me with.
Back in March I made the following post:
"I was running on the original September Update since I got the phone, I used this guide when I first rooted https://www.xda-developers.com/googl...r-root-magisk/
Today I decided it was time to update so I used this guide https://www.xda-developers.com/flash...-google-pixel/
Then I wanted to reroot my phone. So I bootet the TWRP image and flashed the magisk 18.1 zip. But after that I softbricked my phone and it wouldn't boot anymore.
So in my panic I flashed the TWRP zip and my phone worked again, but now everytime I try to flash the magsik zip the same thing happens, bootloop and back to flashing twrp.zip. "
After that didn't work, I tried flashing the magisk uninstaller, through twrp, but it exited with "Error 1" everytime. (Running TWRP 3.3.0)
So i decided to give up, because I had some personal stuff to take care of, but after Android 10 came out yesterday, I decided to give this another go.
I flashed the factory image without "-w" and everything is working fine. So today I followed this guide, double checked everything but after I flash the patched boot image I get stuck with a bootloop again... I can flash back the original boot image and everything works so it's not a huge deal, but right now I can't use google pay, because it says I'm rooted.
Any idea what I could do? Can't run the uninstaller and can't reroot... ???
thanks!
Have you checked if your patched boot.img matches the firmware on your phone?
Well it's the same one I used to flash the firmware.
I flashed yesterday without an issue and today I loaded that boot.img onto my phone, used the canary magisk manager to patch it and then transfered it back to my PC to flash it.
Edit: I'm thinking this might have to do with the fact that I couldn't uninstall magisk before.
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
GohanBurner said:
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
Click to expand...
Click to collapse
I had it working before I bodged a magisk module install
No luck here. The steps SEEM to work perfectly. Flashed the modified boot image, booted up fine, but magisk says it's still not installed. No root.
- Latest magisk canary
- Used the same firmware
- No errors anywhere along the way
Hey Mac users, I had to use the command fastboot flash boot_b magisk_patched.img
To get the patched image over to my phone. It worked out great. I was able to reboot,
and see the root in Magisk Manager.
YMMV
Thanks, worked like a charm on Linux with latest platform-tools! I thought I'd have to wait a lot longer to get root back on my device.
I have also tried this multiple times. No errors, but I can't edit system files or add modules.