Related
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
Greetings. I was trying to root my Nexus 9 and was hoping to make it faster by flashing a custom ROM on it (PureNexus).
I failed with everyone now it's stuck on a bootloop (Google logo), and when I try the Power + Vol Down button and go to Recovery (OpenRecoveryScript loop on TWRP 3.0 happens)
I have no idea on what to do first, I've tried installing ADB drivers but I can't seem to get into Recovery long enough to install fastboot + adb.
I was using Nexus Root Toolkit when this all happened. Any professional people that root here? Mind helping me with my problem? Thank you!
I'm no dev but you need to boot power+vol up for fastboot
And extract the factory image from google and press the flashall.bat/sh (win/Linux) to get back to stock.
whowatchlist said:
I'm no dev but you need to boot power+vol up for fastboot
And extract the factory image from google and press the flashall.bat/sh (win/Linux) to get back to stock.
Click to expand...
Click to collapse
I will try this out when I get home. Thank you!
Start with this, http://forum.xda-developers.com/nex...ader-flash-t3035153/post58956577#post58956577
It's best to learn how to flash factory images without the use of a tool kit. That way when you run into problems you'll know what to do.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Start with this, http://forum.xda-developers.com/nex...ader-flash-t3035153/post58956577#post58956577
It's best to learn how to flash factory images without the use of a tool kit. That way when you run into problems you'll know what to do.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Currently doing this as we speak. I'll let you know what happens. Thanks a bunch
jd1639 said:
Start with this, http://forum.xda-developers.com/nex...ader-flash-t3035153/post58956577#post58956577
It's best to learn how to flash factory images without the use of a tool kit. That way when you run into problems you'll know what to do.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I did this step by step and I fixed it! Though I want to flash to Pure Nexus. Do you have any tips?
You'll want to flash the latest twrp using fastboot. (Google teamwin nexus 9) Then download pure nexus Rom and gapps of your choice to your phone. Boot into twrp and do a wipe first. The default wipe is fine. Flash the rom and then flash gapps. Also, read the faq on the pure nexus thread. I believe there is something there about the vendor.img
Sent from my Nexus 9 using XDA-Developers mobile app
papaketchup said:
I did this step by step and I fixed it! Though I want to flash to Pure Nexus. Do you have any tips?
Click to expand...
Click to collapse
You'll want the latest vendor image, extract it from the latest stock image found here:
https://developers.google.com/android/nexus/images
You can flash it using TWRP
I fixed all the problems. Thank you everyone!
I followed the steps given in a post ( not able to post url) and after installing the Supersu the phone is stuck on the boot loop.
I saw posts where the users want to go back to the stock image however i need the phone to be rooted, any suggestions what might be causing the boot loop and how i can fix it.
PS: I have twrp backup and last resort will be to give up rooting and restrore from it. Appreciate your expertise in advance!
Atul Chadha said:
I followed the steps given in a post ( not able to post url) and after installing the Supersu the phone is stuck on the boot loop.
I saw posts where the users want to go back to the stock image however i need the phone to be rooted, any suggestions what might be causing the boot loop and how i can fix it.
PS: I have twrp backup and last resort will be to give up rooting and restrore from it. Appreciate your expertise in advance!
Click to expand...
Click to collapse
URL: http://www.androidinfotech.com/2016/12/root-huawei-honor-7-marshmallow-twrp.html
Atul Chadha said:
URL: http://www.androidinfotech.com/2016/12/root-huawei-honor-7-marshmallow-twrp.html
Click to expand...
Click to collapse
That is way outdated man. And avoid following guides from 3rd party sites. Always search here in XDA. You flashed an outdated TWRP. Flash THIS latest version. Restore your backup for the moment, then flash the latest SuperSU. 2.82. The site you gave both give outdated TWRP and SuperSU.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
That is way outdated man. And avoid following guides from 3rd party sites. Always search here in XDA. You flashed an outdated TWRP. Flash THIS latest version. Restore your backup for the moment, then flash the latest SuperSU. 2.82. The site you gave both give outdated TWRP and SuperSU.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Lemme try the above, will keep you posted.
Atul Chadha said:
Lemme try the above, will keep you posted.
Click to expand...
Click to collapse
Alright.
Sent from my Honor 8 using XDA Labs
Atul Chadha said:
Lemme try the above, will keep you posted.
Click to expand...
Click to collapse
I was able to run the supersu however the phone is not booting and says "Attention, please update system again"
Error!
Func No: 10 ( Boot image)
Error No: 2 (load Failed)
adriansticoid said:
Alright.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
I was able to run the supersu however the phone is not booting and says "Attention, please update system again"
Error!
Func No: 10 ( Boot image)
Error No: 2 (load Failed)
Atul Chadha said:
I was able to run the supersu however the phone is not booting and says "Attention, please update system again"
Error!
Func No: 10 ( Boot image)
Error No: 2 (load Failed)
Click to expand...
Click to collapse
Did you restore your backup first?
adriansticoid said:
Did you restore your backup first?
Click to expand...
Click to collapse
I restored my backup and then put the new supersu package in sd card. I have a backup however now i am not able to access TWRP.
Atul Chadha said:
I restored my backup and then put the new supersu package in sd card. I have a backup however now i am not able to access TWRP.
Click to expand...
Click to collapse
To add: I also cleared the cache and data and it was successful. The Supersu mentioned something about writing on boot loader and said it would reboot the phone.
After that, the phone didnt came up
Atul Chadha said:
To add: I also cleared the cache and data and it was successful. The Supersu mentioned something about writing on boot loader and said it would reboot the phone.
After that, the phone didnt came up
Click to expand...
Click to collapse
i think you flashed wrong su ,
venugopalu007 said:
i think you flashed wrong su ,
Click to expand...
Click to collapse
How can i get the right one ( How do i decide the correct version, i am using honor 7 running B360 version bought from flipkart if it makes any difference)
Atul Chadha said:
How can i get the right one ( How do i decide the correct version, i am using honor 7 running B360 version bought from flipkart if it makes any difference)
Click to expand...
Click to collapse
I installed SuperSU-v2.82-201705271822
Atul Chadha said:
I installed SuperSU-v2.82-201705271822
Click to expand...
Click to collapse
Still in bootloop? Dafuq.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
Still in bootloop? Dafuq.
Click to expand...
Click to collapse
So i restored the backup i had because i needed my phone. Is there a specific version of twrp and supersu i need for honor 7.
Here is what i am trying:
I have my supersu on sd card.
I restart phone to goto twrp
i go-to wipe>advanced>wipe the cache
Go back to twrp main menu and hit install
Locate supersu and install it
reboot
Am i missing any step ?
EDIT: I tried using "SuperSU-v2.82-201705271822" latest version and same results. The phone is in rescue mode with error
Error! Func No: 10 ( Boot image) Error No: 2 (load Failed)
Atul Chadha said:
So i restored the backup i had because i needed my phone. Is there a specific version of twrp and supersu i need for honor 7.
Here is what i am trying:
I have my supersu on sd card.
I restart phone to goto twrp
i go-to wipe>advanced>wipe the cache
Go back to twrp main menu and hit install
Locate supersu and install it
reboot
Am i missing any step ?
EDIT: I tried using "SuperSU-v2.82-201705271822" latest version and same results. The phone is in rescue mode with error
Error! Func No: 10 ( Boot image) Error No: 2 (load Failed)
Click to expand...
Click to collapse
EDIT2: I flashed the stock ROM and tried the same thing again.
Same results, either i am doing something wrong or its sheer luck i guess!
Atul Chadha said:
EDIT2: I flashed the stock ROM and tried the same thing again.
Same results, either i am doing something wrong or its sheer luck i guess!
Click to expand...
Click to collapse
Actually man I have no idea why it doesn't boot when it should. How about Magisk? Can you try that?
adriansticoid said:
Actually man I have no idea why it doesn't boot when it should. How about Magisk? Can you try that?
Click to expand...
Click to collapse
Trying it now.
Atul Chadha said:
Trying it now.
Click to expand...
Click to collapse
No luck , same results. I guess i should try to restore the backup and give in for now. There is something wrong with the boot sequence which i cant seem to figure.
The rooting apps write on the boot sequence and then it gives the error i mentioned. I really appreciate your help though, if you find something interesting please update here.
Atul Chadha said:
No luck , same results. I guess i should try to restore the backup and give in for now. There is something wrong with the boot sequence which i cant seem to figure.
The rooting apps write on the boot sequence and then it gives the error i mentioned. I really appreciate your help though, if you find something interesting please update here.
Click to expand...
Click to collapse
I will man. I'm really sorry for this.
Sent from my Honor 8 using XDA Labs
Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/sho....php?t=2073775
The first method was developed by osm0sis and removes magisk and all modules.
1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking 8mg
This method is an offshoot of osm0sis version but boots core-only mode. Afterwards, remove the .disable-magisk file from the /cache folder for modules to work. Dot files are hidden files so if your root explorer can't see hidden files, run the "Remove disable_magisk" bat file in ADB.
1. Same as above but use the overlay.dcoreonly1.zip
For both methods you must be rooted for it to work. These are not cure all's for all bootloops.
Remove .disable_magisk bat file
https://www.androidfilehost.com/?fid=4349826312261684994
****************************************
Here is a fastboot bootable image to boot you into Magisk core-only mode in case you bootloop due to flashing a bad module and TWRP is not enough.
Once in fastboot:
fastboot boot image-newpixel3.img
You will boot with root but modules disabled. After you remove the offending module you will need to go to /cache folder and delete the .disable_magisk file before your modules will work.
fastboot boot image-newpixel3Remove.img
This one should remove magisk and all modules, then reboot and magisk should reinstall itself (ask to install necessary binaries). This is what osm0sis uses to recover from failed flashes. See this post:
https://forum.xda-developers.com/pi...odules-disabler-booting-magisk-t3976625/page2
Images are in this common folder. Pick the appropriate image for your phone.
6-4-20
https://www.androidfilehost.com/?w=files&flid=313291
Amazing! Thanks
I can confirm this worked on Android 10/Q. I can't use the canary patch method for magisk because I forgot to remove the modules before upgrading to Android 10. This method works like a charm, it removed the incompatible modules allowed me to by pass the bootloop.
Thank you so much for sharing!
For those who are wondering, these are the steps:
adb reboot bootloader
fastboot flash boot image-new.img
fastboot reboot
Done!
wao20 said:
For those who are wondering, these are the steps:
adb reboot bootloader
fastboot flash boot image-new.img
fastboot reboot
Done!
Click to expand...
Click to collapse
Second step should be:
fastboot boot image-new.img
Tulsadiver said:
Here is a fastboot bootable image to boot you into Magisk core-only mode. If you bootloop due to flashing a bad module, in fastboot:
fastboot boot image-new.img
You will boot with root but modules disabled.
Tested by me and @123SIT whom contributed on the project.
Made from Pixel 3 XL but should work on the Pixel 3 also.
Image
https://mega.nz/#!NE5yGaBA!0HLSWvdD4x4cOmo35HrDGrGNxTAUGW4LpkpVv1ygwVI
Thanks to @ApeironTsuka for his guide and everyone on the Magisk support thread like @jcmm11 for their patience and help.
Click to expand...
Click to collapse
Any idea if this works on the Pixel 2 and 2XL?
Sent from my Pixel C using Tapatalk
Alxoom33 said:
Any idea if this works on the Pixel 2 and 2XL?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
No, but you have TWRP. You don't need it.
P3 doesn't have TWRP? Wow!!! I knew I didn't like that phone.
Sent from my Pixel 2 XL using Tapatalk
Alxoom33 said:
P3 doesn't have TWRP? Wow!!! I knew I didn't like that phone.
Click to expand...
Click to collapse
Only since the update to android 10
Alxoom33 said:
P3 doesn't have TWRP? Wow!!! I knew I didn't like that phone.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I just came across a time when I couldn't even boot TWRP on my Pixel 2. Here is a boot with root, core-mode Magisk image for Pixel 2 XL.
https://www.androidfilehost.com/?fid=1899786940962594367
Tulsadiver said:
I just came across a time when I couldn't even boot TWRP on my Pixel 2. Here is a boot with root, core-mode Magisk image for Pixel 2 XL.
https://www.androidfilehost.com/?fid=1899786940962594367
Click to expand...
Click to collapse
Yeah, I remember those days. Thanks for the image. Can it be flashed in TWRP or strictly adb/fastboot?
Sent from my Pixel 2 XL using Tapatalk
Alxoom33 said:
Yeah, I remember those days. Thanks for the image. Can it be flashed in TWRP or strictly adb/fastboot?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I've only used fastboot.
Tulsadiver said:
Here is a fastboot bootable image to boot you into Magisk core-only mode. If you bootloop due to flashing a bad module, in fastboot:
fastboot boot image-new.img
You will boot with root but modules disabled.
Tested by me and @123SIT whom contributed on the project.
Made from Pixel 3 XL but should work on the Pixel 3 also.
Image
https://mega.nz/#!NE5yGaBA!0HLSWvdD4x4cOmo35HrDGrGNxTAUGW4LpkpVv1ygwVI
Thanks to @ApeironTsuka for his guide and everyone on the Magisk support thread like @jcmm11 for their patience and help.
Click to expand...
Click to collapse
can't reach the mega link, can you guys please upload it somewhere else please? I am stuck on bootloop as I 'm typing...
FcukBloat said:
can't reach the mega link, can you guys please upload it somewhere else please? I am stuck on bootloop as I 'm typing...
Click to expand...
Click to collapse
Here is a link to it on my GDrive. Can you please let me know when you've got it so I can delete it?
https://drive.google.com/file/d/1rg5wENhILz8ah8jSdLne2OtaLYGOhdBI/view?usp=sharing
sliding_billy said:
Here is a link to it on my GDrive. Can you please let me know when you've got it so I can delete it?
https://drive.google.com/file/d/1rg5wENhILz8ah8jSdLne2OtaLYGOhdBI/view?usp=sharing
Click to expand...
Click to collapse
got it! thanks this time too!
FcukBloat said:
got it! thanks this time too!
Click to expand...
Click to collapse
No problem. It's good to be a pack rat. I hope it worked.
FcukBloat said:
can't reach the mega link, can you guys please upload it somewhere else please? I am stuck on bootloop as I 'm typing...
Click to expand...
Click to collapse
Mega link seems to be working. Open with chrome, not mega app.
Edit: I've added a AFH download link.
i tried with chromium based browser (vivaldi) from both phone and pc and link didn't work, probably it was a WiFi problem, thanks for adding alternative link though. and your core mode image worked like a charme! and thanks again also to sliding billy for initial mirror support
Just what I needed. Thank you
How did you create it? I want to make sure I have one of these images on hand in the future when I need to fix things
Simply works, thank you!
Holy cow, thanks man. I can't believe @topjohnwu let this slide through. Without TWRP wtf are you supposed to do, reflash the whole OTA/factory image?!
EDIT: Wait, now I can boot and apparently have root but I can't access any of my rooted apps. It says "waiting for root". Magisk Manager gives me an "app not installed" error but it is installed on the device. When I click it it says "upgrade to full Magisk Manager" and does nothing. How am I supposed to delete the module folder?
EDIT: Can't access terminal, can't do anything. Permission denied via ADB as well.
EDIT: DO NOT DELETE MAGISK MANAGER OR ALTER IT IN ANY WAY WHEN USING CORE MODE. You will be stuck like me. I had to nuke my phone and reflash everything. PIA
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)