This thread was originally for Pixel-specific rooting instructions, but by now the SuperSU ZIP and TWRP are fully supported:
- Fastboot boot TWRP
- Install latest SuperSU ZIP (v2.79-SR3 at the time of writing)
Note that at this time I recommend against fastboot flashing TWRP. With the Pixel's new partition layout, the recovery files are inside the boot partition, and so is SuperSU. If you flash both, SuperSU's internal boot image backup will not be of the original boot image, but of TWRP. This means that neither the 'full unroot' option in SuperSU, nor incremental OTA update through FlashFire, will work as expected.
OR
- Use CF-Auto-Root for Pixel (not released at the time of writing, but should be released soon)
Nice work!
Hell Yeah!!! Thanks @Chainfire, your time as well as others that have made this and the bootloader unlock happen is appreciated very much.
Sent from my Pixel XL using Tapatalk
can we flash another kernel such as elementalX on top of this?
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
How does this relate?
Ker~Man said:
How does this relate?
Click to expand...
Click to collapse
because I attempted to not really thinking about that its systemless and wasnt sure if root would persist. after attempting to flash boot elementalX's kernel my device just powered off so i immediately reflashed root and all is okay now
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
I did read the readme.. so not sure what your getting at
cwalker0906 said:
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
Click to expand...
Click to collapse
chainfire said:
- If you want to use a custom kernel, simply 'fastboot boot' the root image again after flashing the custom kernel. This has been tested with a few custom kernels and found to work well so far.
Click to expand...
Click to collapse
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
lexcyn said:
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
Click to expand...
Click to collapse
okay thanks, so i guess the answer is actually yes
Thanks @Chainfire - booted and working well!
thanks..emoji..root explorer.. viper.. naptime.. titanium.. yes..
if new kernel must boot boot to root again..
Seems I cannot remount /system_root as rw (to copy Emoji font over).
marlin://system_root/system/fonts # mount -o remount,rw /system_root
mount: '/dev/block/bootdevice/by-name/system_a'->'/system_root': Device or resource busy
Edit: Nevermind, used Solid Explorer and granted it SuperUser and seemed to work. Strange.
Does anyone have the stock boot.img for the pixel xl? I don't have the data to download the full factory image.
Life is good!
Thanks to all involved, especially Chainfire.
You Rock!
Worked like a charm. Thanks @Chainfire!
Can't thank you enough. Works perfectly.
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
spunks3 said:
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
Click to expand...
Click to collapse
fastboot boot boot-to-root.img
lexcyn said:
fastboot boot boot-to-root.img
Click to expand...
Click to collapse
what about superSU?
Related
Currently, all official CyanogenMod ROMs use loki tool to install the kernel on the LG G Pad 8.3 v500. Unfortunately, using loki tool causes a benign "secure boot error message" upon startup.
Here are some scripts that can be flashed in the recovery to convert a loki kernel to a bumped (permissive) kernel. The kernel will remain permissive until a new ROM or kernel is flashed again.
When making a kernel permissive, the following commands will be appended to the kernel boot command line:
Code:
androidboot.selinux=permissive selinux=0
Note: Only apply these scripts one time when setting the kernel to permissive mode or the command line above will be appended twice.
Instructions:
1) Flash ROM
2) Flash one of the scripts below, depending on what you want.
1) Convert a loki kernel to a bumped kernel
v500-loki-kernel-to-bumped-kernel-signed.zip
2) Convert a loki kernel to a bumped permissive kernel (turns off selinux)
v500-loki-kernel-to-bumped-permissive-kernel-signed.zip
3) Convert an already bumped kernel to a permissive bumped kernel (turns off selinux)
v500-bumped-kernel-to-bumped-permissive-kernel-signed.zip
Thanks to @Skin1980 for the bash bump code.
Thanks to @aicjofs for the script base.
This is amazing, thanks for your work.
This is really great, we all love what your doing for us - thanks again. I'm gonna take a stab in the dark and guess that its probably a bad idea to use the CM updater due to these having to be flashed along with an update?
annoyingduck said:
This is really great, we all love what your doing for us - thanks again. I'm gonna take a stab in the dark and guess that its probably a bad idea to use the CM updater due to these having to be flashed along with an update?
Click to expand...
Click to collapse
It's fine to use the cm updater, but you will have to reboot into the recovery twice to apply the patch. Also, if you want your Bluetooth pairings to remain intact, then you want to keep the kernel in permissive mode and never let it boot with selinux enabled (at least until the selinux denials are fixed).
@annoyingduck
You can let cm updater download and verify the update and then hit cancel when it asks to install it. Then manually reboot to recovery and install from the cm updater download directory.
Amazing job @Deltadroid! I applied the first patch, rebooted and the warning message was gone!
Thank you very much for your outstanding work!
[]'s
So... This just removes the warning message when booting?
jesuita said:
So... This just removes the warning message when booting?
Click to expand...
Click to collapse
Yes
jesuita said:
So... This just removes the warning message when booting?
Click to expand...
Click to collapse
That is the only visible effect. It provides a cleaner way of mounting the boot.img
Ok thanks
Works fine with last Infected build.
I assume we have to flash this script after each update.
ledabe974 said:
Works fine with last Infected build.
I assume we have to flash this script after each update.
Click to expand...
Click to collapse
Yes, after each rom or kernel you flash.
Yay! thanks to the permissive script, SuperSU works on CM13! =)
nytral said:
Yay! thanks to the permissive script, SuperSU works on CM13! =)
Click to expand...
Click to collapse
That is good to hear.
The reason systemless supersu does not work with our device is because it breaks the signature on our bumped boot image.
If you choose option #1 on the op after flashing supersu, you should be able to keep selinux in enforcing mode and just rebump the boot image to fix the signature that supersu breaks.
Edit: you will need to dirty flash the rom again to put the device back into enforcing mode.. Then flash supersu and finally the script to bump the boot image over again.
Deltadroid said:
That is good to hear.
The reason systemless supersu does not work with our device is because it breaks the signature on our bumped boot image.
If you choose option #1 on the op after flashing supersu, you should be able to keep selinux in enforcing mode and just rebump the boot image to fix the signature that supersu breaks.
Edit: you will need to dirty flash the rom again to put the device back into enforcing mode.. Then flash supersu and finally the script to bump the boot image over again.
Click to expand...
Click to collapse
Well, that's what I thought and what I did first, but actually latest beta SuperSU (2.68) is not breaking the boot sig for some reason (no bootloader error as with previous builds). Looking at logcat during the stuck boot I noticed some zygote process failing because of selinux and that's when I decided to try to disable it -> success! Now a cleaner way would probably be to give the logs to @Chainfire so he can have a look but given the non-popularity of V500 he probably won't care/not be able to fix it without one. Oh well, at least I have something working although not as secure as it should be. So thank you for this :good:
Thank you for this great job!!! I was stuck on the LG logo with the know loki message... I though that my v500 was bricked for good.
I used the first file after cleaning everything in twrp 3.0.0 (not usb and external) and installing a)6.0 mmb29v, b) su v2.65 and c) your 1st file.
2 questions. 1) whenever I flash and update should I flash it through twrp with the above mentioned order? 2) Should I flash other version (older like 2..8.7.x) and philz zip?
Thank you again for your great job!!!
glyrakos said:
Thank you for this great job!!! I was stuck on the LG logo with the know loki message... I though that my v500 was bricked for good.
I used the first file after cleaning everything in twrp 3.0.0 (not usb and external) and installing a)6.0 mmb29v, b) su v2.65 and c) your 1st file.
2 questions. 1) whenever I flash and update should I flash it through twrp with the above mentioned order? 2) Should I flash other version (older like 2..8.7.x) and philz zip?
Thank you again for your great job!!!
Click to expand...
Click to collapse
You did it correctly. Every time you flash SuperSU over again, you will need to flash this script directly after that to bump the kernel over again and fix the boot signature. Any recovery should work, but I recommend using the latest official TWRP.
Deltadroid said:
You did it correctly. Every time you flash SuperSU over again, you will need to flash this script directly after that to bump the kernel over again and fix the boot signature. Any recovery should work, but I recommend using the latest official TWRP.
Click to expand...
Click to collapse
Sorry, but as a nobbie let me ask you something more. Do you have a link for the latest official TWRP. How to flash it? Through TWRP 3.0.0 that I have now, or through sideload? Also I cannot enter TWRP with the combination of the 3 buttons. I get Factory Reset menu.
Thank you.
glyrakos said:
Sorry, but as a nobbie let me ask you something more. Do you have a link for the latest official TWRP. How to flash it? Through TWRP 3.0.0 that I have now, or through sideload? Also I cannot enter TWRP with the combination of the 3 buttons. I get Factory Reset menu.
Thank you.
Click to expand...
Click to collapse
The official TWRP for device is here
http://forum.xda-developers.com/showthread.php?p=61363260
You can flash the new recovery image from within TWRP.
When you use the 3 buttons to get to recovery, it asks to factory reset, but it goes to TWRP instead. It is a hack because our recoveries were never actually unlocked. Just say, yes and TWRP will open.
Deltadroid said:
The official TWRP for device is here
http://forum.xda-developers.com/showthread.php?p=61363260
You can flash the new recovery image from within TWRP.
When you use the 3 buttons to get to recovery, it asks to factory reset, but it goes to TWRP instead. It is a hack because our recoveries were never actually unlocked. Just say, yes and TWRP will open.
Click to expand...
Click to collapse
Maybe I am not doing something good but when using the 3 button method it goes to factory reset and stays there endless if I do not press something .... but power whipes everything (i've re-setup my v500 for about 15 times already....) ... and volume up/down exits the menu and reboots......
This is a stock boot.img I use where I edited ramdisk and sepolicy for regular root. I also changed force encryption to encryptable and permissive Enforcing
I will continue to post new boot.img each update here.
Downloads
NBF26f big thanks for the update was done by @googy_anas
https://drive.google.com/file/d/0B4yuQy7Zn1WSdTFCMEtRbXpSREE/view?usp=drivesdk
NBD91K
https://www.androidfilehost.com/?fid=529152257862678470
NRD90U
https://drive.google.com/file/d/0B6DDdWOgUhVVMFpGTFlTQWVQOW8/view
@holla420 good looks on doing boot.img again.
NPD90G
https://www.androidfilehost.com/?fid=24591023225178833
big shout out to my homie @holla420 for knocking out this boot.img for everyone.
NPD56N
https://www.androidfilehost.com/?fid=24572369242686570
big shout out to my homie @holla420 for knocking out this boot.img for everyone
NPD35K
https://drive.google.com/file/d/0B4yuQy7Zn1WSQmdfZ3dNMW02Z3c/view?usp=drivesdk
Decrypted boot.IMG and no DM check for NPC91K
https://drive.google.com/file/d/0B4yuQy7Zn1WSVVJSbWpGaU1sTlU/view?usp=drivesdk
Decrypted boot.IMG for Android N build NPC56W
https://drive.google.com/file/d/0B4yuQy7Zn1WSZm11VE1KZmx3RG8/view?usp=sharing
Decrypted boot.IMG for Android N build inital release
https://drive.google.com/file/d/0B4VEhClrJEWpekpneFdUWkhBX1E/view
Big thanks to my good friend and co-dev @toknitup420 don't forget to thank him you see him around
works perfect. Good looks @Tigerstown.
Sent from my Nexus 6P using Tapatalk
Tigerstown said:
This is a stock boot.img I use where I edited ramdisk and sepolicy for regular root. I also changed force encryption to encryptable.
Download https://drive.google.com/file/d/0B4yuQy7Zn1WSTnE4bmxNZXRMdGs/view?usp=docslist_api
Click to expand...
Click to collapse
Eli5, What's the point of a normal root when you can just flash the systemless root and be done with it?
floepie said:
Eli5, What's the point of a normal root when you can just flash the systemless root and be done with it?
Click to expand...
Click to collapse
what's the point of systemless root is what you should be asking yourself
Tigerstown said:
what's the point of systemless root is what you should be asking yourself
Click to expand...
Click to collapse
Because you don't have to rely on the generosity of someone modifying the boot image to accommodate the older method, thereby requiring only 1 recovery flash?
floepie said:
Because you don't have to rely on the generosity of someone modifying the boot image to accommodate the older method, thereby requiring only 1 recovery flash?
Click to expand...
Click to collapse
Why are you even in this thread if you have no interest in using traditional root. Stop trolling and leave the thread. If you don't want it, then don't use it. It's been posted for users that want traditional root and don't know how to mod their own boot.img. Also you're incorrect about the amount of flashing in recovery. You still only need to flash one zip. The SuperSU zip. The boot image gets flashed in fastboot. Soooooooo when you're updating to newest software from Google, you simply use this modded boot.img instead of the one from Google. So technically there are absolutely no extra steps taken in order to use this boot.img.
Sent from my Nexus 6P using Tapatalk
Huh? No, really, I think I'm too old to be "trolling". Just curious to know if there are any potential advantages of the traditional method - not from a selfish perspective, but more out a, well, curiosity. Can we just keep this to the level of a civil "discussion"?
Is this still Enforcing? Is it possible to get a stock or close to stock kernel that is Permissive for a project I'm working on? I just need a boot.img. Thanks!
toknitup420 said:
Why are you even in this thread if you have no interest in using traditional root. Stop trolling and leave the thread. If you don't want it, then don't use it. It's been posted for users that want traditional root and don't know how to mod their own boot.img. Also you're incorrect about the amount of flashing in recovery. You still only need to flash one zip. The SuperSU zip. The boot image gets flashed in fastboot. Soooooooo when you're updating to newest software from Google, you simply use this modded boot.img instead of the one from Google. So technically there are absolutely no extra steps taken in order to use this boot.img.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I agree and thank you. as I am traditional root user. thank you for the boot img
Sent from my Nexus 9
floepie said:
Eli5, What's the point of a normal root when you can just flash the systemless root and be done with it?
Click to expand...
Click to collapse
Why do you guys attack the above person for asking "explain like I am 5, why does anyone want this?"
Tigerstown said:
what's the point of systemless root is what you should be asking yourself
Click to expand...
Click to collapse
toknitup420 said:
Why are you even in this thread if you have no interest in using traditional root. Stop trolling and leave the thread. If you don't want it, then don't use it. It's been posted for users that want traditional root and don't know how to mod their own boot.img. Also you're incorrect about the amount of flashing in recovery. You still only need to flash one zip. The SuperSU zip. The boot image gets flashed in fastboot. Soooooooo when you're updating to newest software from Google, you simply use this modded boot.img instead of the one from Google. So technically there are absolutely no extra steps taken in order to use this boot.img.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Would it have been better if the question were phrased: "Why do you need a separate modified boot.img, when you can force system root using any SuperSU above 2.65? It will still patch the boot.img and disable "forceencrypt"?
So, I'll ask....why do you need a modified boot.img and SuperSU, if SuperSU 2.6x will *automatically modify the boot.img for you and can be installed as system or system-less via terminal commands? Is it because you are using the stock rom and SuperSU will not install as system root due to lack of space in /system?
Edit: *automatically modify boot.img when installing as system-less, OR can be forced to install as system root via terminal commands?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Why do you guys attack the above person for asking "explain like I am 5, why does anyone want this?"
Would it have been better if the question were phrased: "Why do you need a separate modified boot.img, when you can force system root using any SuperSU above 2.65? It will still patch the boot.img and disable "forceencrypt"?
So, I'll ask....why do you need a modified boot.img and SuperSU, if SuperSU 2.6x will *automatically modify the boot.img for you and can be installed as system or system-less via terminal commands? Is it because you are using the stock rom and SuperSU will not install as system root due to lack of space in /system?
Edit: *automatically modify boot.img when installing as system-less, OR can be forced to install as system root via terminal commands?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Why use the terminal cmd? I make this for myself. I posted for people that want it. If you don't want it or need it that is cool. I flash this when flashing factory imgs and I can reboot still decrypted then I boot to twrp flash SuperSU zip and I'm done. I'm not a fan of systemless root. Do you know why it was even created??
guitardedhero said:
Is this still Enforcing? Is it possible to get a stock or close to stock kernel that is Permissive for a project I'm working on? I just need a boot.img. Thanks!
Click to expand...
Click to collapse
Yes it's still Enforcing
floepie said:
Because you don't have to rely on the generosity of someone modifying the boot image to accommodate the older method, thereby requiring only 1 recovery flash?
Click to expand...
Click to collapse
This boot.img isn't flashed in recovery so still one flash. This is fastboot when your updating factory imgs.
freddienuxx said:
I agree and thank you. as I am traditional root user. thank you for the boot img
Sent from my Nexus 9
Click to expand...
Click to collapse
no problem I do it for every update. I just decide to start posting them for people like yourself. ??
Hi,
Should I be using this file to update from MMB29P to MMB29Q and still maintain root?
I must flash the file through TWRP?
Touchmetallic said:
Hi,
Should I be using this file to update from MMB29P to MMB29Q and still maintain root?
I must flash the file through TWRP?
Click to expand...
Click to collapse
you can use this as boot.img to update yes. But keep root no. You just need to flash factory imgs with this boot.img then boot up and boot to twrp flash SuperSU 2.67 and you will be updated with regular root.
Flash this boot.img thru fastboot just like you do factory imgs not via recovery.
Tigerstown said:
you can use this as boot.img to update yes. But keep root no. You just need to flash factory imgs with this boot.img then boot up and boot to twrp flash SuperSU 2.67 and you will be updated with regular root.
Flash this boot.img thru fastboot just like you do factory imgs not via recovery.
Click to expand...
Click to collapse
Thanks for your reply.
Sorry if this is a redundant question as I'm not an expert, but is there an easy way to update without losing root?
Touchmetallic said:
Thanks for your reply.
Sorry if this is a redundant question as I'm not an expert, but is there an easy way to update without losing root?
Click to expand...
Click to collapse
No need to be sorry it's all good... Unfortunately no. You can just flash SuperSU zip in twrp after updating to new factory imgs with this modified boot.img and your 100% rooted again.
Touchmetallic said:
Thanks for your reply.
Sorry if this is a redundant question as I'm not an expert, but is there an easy way to update without losing root?
Click to expand...
Click to collapse
I recommend not flashing the userdata.img as that will wipe your internal storage sense it's still 6.0.+ FYI but that's up to you and don't flash the recovery.img either in factory imgs cause that will replace your twrp with stock recovery
Tigerstown said:
Why use the terminal cmd? I make this for myself. I posted for people that want it. If you don't want it or need it that is cool. I flash this when flashing factory imgs and I can reboot still decrypted then I boot to twrp flash SuperSU zip and I'm done. I'm not a fan of systemless root. Do you know why it was even created??
Click to expand...
Click to collapse
Ahh I see. That makes sense given that you are decrypted. Appreciate that.
Having followed SuperSU threads since late November, seems like it was created to make accepting OTAs easier. That, or to work around the limits of Marshmallow and /system rom space. If not that, then no I don't.
Sent from my Nexus 5X using Tapatalk
hi Guys!
I just wanted to share my work with you.
I created a working TWRP recovery for the Pixel on Android O developer preview 4, that can boot and decrypt the /data partition. I don't own a Pixel XL, so I can't test, but @Chainfire did a few quick tests and it seems to be working on his Pixel XL too. So I would say you can try and see if it works for you. Please keep in mind, that I didn't test it, and neither Chainfire, or myself or anyone else can be blamed if it doesn't work, or damages your phone (shouldn't actually, but who knows..).
If you are still not scared enough, please follow this link to the Pixel forums and check out my work:
https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896
Good luck!
I test it on my pixel xl， working well.
Thank you very much.
But it seems to not be able to flash supersu
When I try to flash it via fastboot it says file is not signed. What am I doing wrong here? I wanted to be rooted and I am on Android op4 preview. Please guide me how to root. Thank you everyone.
sahilarora2003 said:
When I try to flash it via fastboot it says file is not signed. What am I doing wrong here? I wanted to be rooted and I am on Android op4 preview. Please guide me how to root. Thank you everyone.
Click to expand...
Click to collapse
Its in the instructions but here is the command and you shouldn't flash it but instead fastboot it.
fastboot boot trwp.img
flash the latest supersu 2.82 sr1
NVM. Mission accomplished. Thank you for help.
feimummy said:
I test it on my pixel xl， working well.
Thank you very much.
But it seems to not be able to flash supersu
Click to expand...
Click to collapse
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
SR2 flash fine
gubacsek said:
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
Click to expand...
Click to collapse
You can try SR2 flash fine.
gubacsek said:
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
Click to expand...
Click to collapse
Thank you for your answer.
Thank Chainfire.
But my phone Pixel XL is at home now,I will try it later.
Is it this one?
https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
feimummy said:
Thank you for your answer.
Thank Chainfire.
But my phone Pixel XL is at home now,I will try it later.
Is it this one?
https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
Click to expand...
Click to collapse
Yes, that should be it!
Although Chainfire has released a new version in zip format, with a lot of pixel (XL) related fixes. You can also try to flash that one using my modded TWRP.
gubacsek said:
Yes, that should be it!
Although Chainfire has released a new version in zip format, with a lot of pixel (XL) related fixes. You can also try to flash that one using my modded TWRP.
Click to expand...
Click to collapse
I have used your modded TWRP to flash SuperSU zip,but there was nothing happened after rebooting the phone.
And I also try "fastboot boot boot-to-root.img" just now,there was still nothing happened...
View attachment 4236828
I mean,it was so strange that SuperSU can not be flashed into my Pixel XL with these two methods.
——————————The final outcome——————————
I have solved the problem with this SuperSU version:
https://forum.xda-developers.com/showpost.php?p=72686197&postcount=10481
Thanks a lot.
feimummy said:
I have used your modded TWRP to flash SuperSU zip,but there was nothing happened after rebooting the phone.
And I also try "fastboot boot boot-to-root.img" just now,there was still nothing happened...
View attachment 4236828
I mean,it was so strange that SuperSU can not be flashed into my Pixel XL with these two methods.
Click to expand...
Click to collapse
Try to flash the original boot.img first.
1. reboot to bootloader
2. fastboot flash boot.img from the factory image zip
3. fastboot boot recovery.img
4. in the recovery, flash supersu
Or you can skip points 3 and 4, and fastboot boot boot-to-root.img
gubacsek said:
Try to flash the original boot.img first.
1. reboot to bootloader
2. fastboot flash boot.img from the factory image zip
3. fastboot boot recovery.img
4. in the recovery, flash supersu
Or you can skip points 3 and 4, and fastboot boot boot-to-root.img
Click to expand...
Click to collapse
Sr2 flash fine!
caballon said:
Sr2 flash fine!
Click to expand...
Click to collapse
Great! Nice to see that everything is working I had this itching, you know, when something is not as it should be, because I wanted to have Android O, but there was no recovery to do what I want... Now this feeling is gone, and I'm relaxed again
The only thing missing is a flashable zip. Is my current "itch"
Very nice. I booted into TWRP with no issue. I had already used boot-to-root so I did not have to flash SR2 in TWRP but nice knowing we have it working for the XL.
Thank you for making this sir.
Work like a charm in Final Android O!!! Thanks man.
caballon said:
Work like a charm in Final Android O!!! Thanks man.
Click to expand...
Click to collapse
Same here!
People have successfully rooted O Final? I used the img but I can't flash zips or access any folders they all have weird names is that due to Encryption?
liam_davenport said:
People have successfully rooted O Final? I used the img but I can't flash zips or access any folders they all have weird names is that due to Encryption?
Click to expand...
Click to collapse
Had this already sometimes on 7.1.2 with twrp rc 1 and 2. Must be an encryption error. Only way for me to use the phone again was to start all over with flashing factory image with flash-all.bat.
liam_davenport said:
People have successfully rooted O Final?
Click to expand...
Click to collapse
Reboot until you get prompted for your PIN in recovery, then flash SuperSU v2.82 SR3 from here.
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
T4gB0t said:
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
Click to expand...
Click to collapse
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Hw4ng3r said:
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Click to expand...
Click to collapse
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
T4gB0t said:
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
Click to expand...
Click to collapse
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Hw4ng3r said:
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Click to expand...
Click to collapse
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
T4gB0t said:
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
Click to expand...
Click to collapse
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Hw4ng3r said:
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Click to expand...
Click to collapse
I downloaded the software from the official website and used payload dumper to extract the boot image. To be sure that I understood everything... you suggested to use "fastboot boot patched.img" instead of "fastboot flash boot patched.img", and once the phone restarted to go to magisk manager and click direct install.
Do I need Magisk Manager canary or the normal version for this to work and do I have to mantain the canary version or can I install the normal version once it is rooted?
Either 22.1 or Canary works for A11
Hw4ng3r said:
Either 22.1 or Canary works for A11
Click to expand...
Click to collapse
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
T4gB0t said:
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
Click to expand...
Click to collapse
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
T4gB0t said:
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
Click to expand...
Click to collapse
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Hw4ng3r said:
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Click to expand...
Click to collapse
So not Magisk v.23 but Magisk canary?
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Hw4ng3r said:
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Click to expand...
Click to collapse
Okay thanks, I'll try with v.23 first and If that does not work than I'll try with the canary one. Thank you very much!!!
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Wacko1805 said:
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Okay thank you, I'll try if the other method does not work
T4gB0t said:
Okay thank you, I'll try if the other method does not work
Click to expand...
Click to collapse
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Hw4ng3r said:
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Click to expand...
Click to collapse
I'm sorry to bother you again, but I tried with "fastboot boot patched.img" and it still did not work. It got stuck while booting again with "unable to parse kernel log" as error message. Do you have any other suggestions?
P.S. I got a full backup with "adb backup -apk -all -shared -f /path/to/location" today and thought about just doing a factory reset, trying to root the phone, restore the backup. Do you think that might actually work? Thank you for your help!
How exactly did you patched your boot.img?
FSadino said:
How exactly did you patched your boot.img?
Click to expand...
Click to collapse
I tried doing it with magisk (both v.23 and canary)
Official TWRP is now available: https://twrp.me/asus/zenfone9.html
IMPORTANT NOTES:
CleanSlate custom kernel is not currently compatible with TWRP for this device (Kirisakura is compatible as of v2.0.6).
This device has a recovery partition (2, in fact), and fastboot boot is disabled in the bootloader. Flashing TWRP to the recovery partition is the only way to use it.
If you attempt to fastboot boot the TWRP image, your device may end up unbootable. YOU'VE BEEN WARNED.
Any questions, comments, feedback, or concerns should always be accompanied by logs (recovery log, logcat, dmesg)
TWRP Trees
Common: https://github.com/TeamWin/android_device_asus_sm84xx-common
Device: https://github.com/TeamWin/android_device_asus_AI2202
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Hermann2306 said:
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Click to expand...
Click to collapse
If you're not on stock kernel, then that's probably the problem. I know the custom kernel situation is different on this device than previous ones. This may be something that @Freak07 & I have to look into together. In the meantime, can you restore back to stock kernel and confirm that TWRP works, and then install Kirisakura and see if everything still works?
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Hermann2306 said:
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Click to expand...
Click to collapse
It doesn't sound like you followed the procedure in the Kirisakura thread FAQ to fully return to stock. Can you confirm exactly what you did?
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Hermann2306 said:
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Click to expand...
Click to collapse
I'm not familiar with that app, sorry. I just know that's not the process mentioned in his thread, so until you do that, I can't really confirm what the problem could be.
ok, im back on stock. flashing following files helped. i will test twrp again later and report. thanks for your replies.
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Hermann2306 said:
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Click to expand...
Click to collapse
From stock, I just flashed the Kirisakura zip in TWRP and my device booted up fine.
EDIT: While the above is true, TWRP no longer functions after installing the kernel, and the device won't reboot again after installing it. So something is definitely wrong somewhere.
For now, I can only suggest not using it with a custom kernel until we figure this out.
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Hermann2306 said:
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Click to expand...
Click to collapse
Yes, there seems to be an issue in the kernel that's preventing TWRP from working. I'm not sure what the issue is, unfortunately.
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
c19932 said:
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
Click to expand...
Click to collapse
Yes.
Quick PSA for anyone using this TWRP that also wants to use a custom kernel:
As of Kirisakura 2.0.6, the custom kernel and TWRP can now co-exist. This is due to the changes that allowed a monolithic kernel build. Presently, CleanSlate has not adopted those changes, but if/when it does, I will remove that disclaimer from the OP.
Thanks to @arter97, @Freak07, & @tbalden for supporting this device!
Is the twrp compatible with android 13?
NisseGurra said:
Is the twrp compatible with android 13?
Click to expand...
Click to collapse
There's a really easy way to find out...
Captain_Throwback said:
There's a really easy way to find out...
Click to expand...
Click to collapse
I getting decrypt errors that why the q
NisseGurra said:
I getting decrypt errors that why the q
Click to expand...
Click to collapse
Then you should post some logs
Will do