Related
This thread contains a tutorial on how to patch boot.img on Samsung Lollipop devices and achieve root with a stock firmware. The tutorial is intended for those who wish to make their own boot.img for their specific firmware. For the rest, a patched boot.img for each device variant is attached. Simplified instructions for flashing with these patched images is first, followed by the tutorial.
NOTES!
1: YOU MUST EXTRACT THE .IMG FILE FROM THE TAR AND FLASH WITH TWRP. For some reason flashing with ODIN does NOT work with the images attached to this thread.
2: To make ODIN tars, look at @drExel's post here.
3: In most variants, TWRP 2.8.7.0 appears to work, though there are some issues. On some devices, it takes a REALLY long time to boot into TWRP, making you believe the device has frozen, but just give it time and it will load eventually. On other devices, TWRP loads, but touch does not work. In these cases, the S-Pen works without any problems (but is very sensitive). Some users have posted alternate TWRPs that work properly; search the thread for this. I am not including it here because I have not personally tried these versions myself.
4: Since this issue came up multiple times, though it is mentioned in the instructions below, I am stressing this once again. DO NOT ALLOW TWRP TO AUTOMATICALLY INSTALL SUPERSU WHEN YOU HIT REBOOT. THIS WILL CAUSE A BOOTLOOP, GUARANTEED! YOU MUST FLASH THE BETA 2.52 SUPERSU MANUALLY AFTER FLASHING THE PATCHED BOOT.IMG AND CONFIRMING THE DEVICE WORKS PROPERLY!
5: If you take the time to read the entire thread, you will find redirects to other kernels, firmwares and more. I am sure they are excellent, but having not used any of them, I cannot vouch for the outcomes if you flash them. All information related to the other firmwares and any questions you have about them are best served by going to their dedicated threads. This thread is ONLY for a pure stock firmware with only the boot.img patched to permit root, and nothing else touched.
6: XPosed Framework does not work yet for TW LL, but @wanam has an unofficial version here that various members have reported works quite well.
7: Knox WILL be tripped. If you care about Knox, leave now and do not come back!
Simplified Instructions
The thread originally began as a pure tutorial, with only the P607T image. But given the requests others had, and my need to confirm that this works on all variants, I made more patched images. No 'simple instructions' were available earlier because this was not intended for end-users who might flash and find that it does not work. Now that all the images are confirmed working, and we have tested on all variants, here is a simplified set of instructions for those who just wish to flash and do not care what they are flashing.
1: Update to fully stock 5.1.1 for your device. Whether it is OTA or ODIN flash using a firmware from sammobile or elsewhere does not matter. You start with a fully stock device running 5.1.1.
2: Download the appropriate patched_boot.img for your device. They are attached as tar files due to XDA size restrictions, so you must untar and then save the .img file to your device. Also download SuperSU Beta 2.52.zip and save it as is to the same folder on your device where you put the .img file.
3: Download TWRP 2.8.7.0 for your device and flash it with ODIN. To get TWRP to stick, when the device reboots, you must go directly into recovery. If the device reboots normally, TWRP will be replaced by the stock recovery. There are guides on how to flash TWRP and you should go look at them if you are unsure how to do this.
4: Once you are in TWRP, go the Install area. The default is for installing .zip files. At the bottom right of the screen, you will see a button to change to Images. Hit this. Then select the patched_boot.img file that you saved on your device in the previous step. When you hit install, TWRP will ask you whether this is a boot image or a recovery image. Select Boot. Let TWRP do its thing. When done, go back and hit reboot. TWRP will volunteer to install SuperSU for you now. SAY NO TO THIS. If you accept this install, your device will bootloop and you have start all over again!
5: Make sure the device rebooted without any problems. You will see a red "Kernel SEAndroid Not Enforcing" message when you reboot. Ignore it, it just means that the patched boot.img is working. Once you have confirmed that the device is able to boot properly with the patched boot.img, reboot into recovery again. Go back to Install, this time, stick with Zip mode and install the Beta SuperSU 2.52.zip that you saved to your device. Reboot.
6: If you followed instructions properly, you will reboot without any problems. Run SuperSU, allow it to update if it wants to, and to disable knox if you want to. You have a rooted device now with a virgin firmware.
7: This process has worked for enough people now that any errors are user errors. If you are bootlooping after following these instructions to the letter, you should do a full factory reset and try from scratch. A previous incorrect flash of SuperSU that caused a bootloop seems to persist even if you reflash the stock firmware and messes things up. Always perform a clean install!
Tutorial to patch your own boot.img
This section is NOT meant for the non-technical end-user who "... just wants root ... "
So far, it seems the only way to get root on the 5.1.1 Firmware was to flash a permissive kernel that disabled SEAndroid completely. This is a bit like killing the patient to cure the disease. @Chainfire describes a 'trick' to get root with a fully stock kernel on this thread. Special Thanks to @garyd9 and @SHM for helping me get everything working properly.
Part 1:
1) Extract boot.img from your device's stock firmware.
2) Unpack the boot.img to get access to the ramdisk.
3) Copy the sepolicy file from the ramdisk. You will be patching this file to make the usual SuperSU method work again.
The stock image can be extracted from the firmware using any archive tool. To unpack the boot.img, you can take a look at the following threads for tools and instructions.
Carliv's Kitchen : Windows, very beginner friendly.
SHM's Toolset : I used this on Linux.
copy sepolicy from the ramdisk folder to your adb folder (If you are on Windows and using Minimal ADB and Fastboot; I am assuming linux users don't need to be told what to do here )
Part 2:
1) Connect an already rooted device running 4.4+ firmware & SuperSU Beta 2.50+ to your system. Make sure you have adb access.
2) Push the sepolicy file to the device.
3) Run supolicy on the sepolicy file to patch it.
4) Pull the sepolicy file back to your computer.
I used my rooted Note 2 to get the job done. ANY rooted device that permits adb should do the trick, but it needs to be on 4.4+ firmware and running SuperSU Beta 2.50+.
Once you have an adb connection established, do the following (this is from Chainfire's thread referenced at the beginning):
Code:
adb push sepolicy /data/local/tmp/sepolicy
adb shell su -c "supolicy --file /data/local/tmp/sepolicy /data/local/tmp/sepolicy_out"
adb shell su -c "chmod 0644 /data/local/tmp/sepolicy_out"
adb pull /data/local/tmp/sepolicy_out sepolicy_out
Part 3:
1) Replace the sepolicy file in the stock ramdisk with the newly patched sepolicy file.
2) Repack the ramdisk.
3) Make a new boot.img with the stock kernel and repacked ramdisk.
4) Flash new boot.img on your Note 10.1. Reboot, make sure everything is working.
Replace the sepolicy in the ramdisk with the sepolicy_out file that you pulled from your reference device. This means RENAME sepolicy_out and overwrite the original sepolicy file.
Repack the ramdisk using the instructions that came with your tool.
Make a new patchedboot.img file using the instructions that came with your tool.
Copy this patchedboot.img file to your Note 10.1, reboot into TWRP, go to the install zip section, toggle image mode, flash the patchedboot.img file and reboot the device. DECLINE TWRP's friendly offer to install SuperSU for you. This will cause a bootloop!If the device reboots successfully, pat yourself on the back. At this point, all you have done is patched the sepolicy to allow rooting, but you have not yet rooted the device.
Part 4:
1) Use TWRP to install SuperSU Beta 2.50+ (I used 2.52)
2) Reboot
Copy SuperSU Beta 2.50+ (I used 2.52) to the device, reboot into TWRP and install SuperSU. Reboot for rooted Note 10.1 running a Stock Kernel and no compromised SEAndroid. Of course, it goes without saying, this will trip knox. Also, please note that XPosed is not out for 5.1.1 yet, at least not officially. @wanam has an unofficial version here that various members have reported works well.
Hey, So at what step in this do I start if I dl'ed the Patched boot img? Thanks in advance.
icemanscion said:
Hey, So at what step in this do I start if I dl'ed the Patched boot img? Thanks in advance.
Click to expand...
Click to collapse
Part 3, Step 4:
Flash new boot.img on your Note 10.1. Reboot, make sure everything is working.
Copy this patchedboot.img file to your Note 10.1, reboot into TWRP, go to the install zip section, toggle image mode, flash the patchedboot.img file and reboot the device. If the device reboots successfully, pat yourself on the back. At this point, all you have done is patched the sepolicy to allow rooting, but you have not yet rooted the device.
Click to expand...
Click to collapse
In TWRP, when you hit Install, on the bottom right, you will see an option for Images. Select that and when you goto the folder with your img, you should see the new img you copied on to your device. Continue with Part 4 for full root.
IF the device does not boot, you want to flash the stock boot.img again, so make sure you have a copy of that on your device as well, so you can recover easily!
karthikrr said:
Part 3, Step 4:
In TWRP, when you hit Install, on the bottom right, you will see an option for Images. Select that and when you goto the folder with your img, you should see the new img you copied on to your device. Continue with Part 4 for full root.
IF the device does not boot, you want to flash the stock boot.img again, so make sure you have a copy of that on your device as well, so you can recover easily!
Click to expand...
Click to collapse
I have issues with TWRP since it wont work properly for me, so I'm going to try it with Philz CWM. Thank you again.
icemanscion said:
I have issues with TWRP since it wont work properly for me, so I'm going to try it with Philz CWM. Thank you again.
Click to expand...
Click to collapse
Good luck Just make sure you have the stock boot.img around, in case there are any problems. You are the first one trying it on the P600, or at least the first who cared to write in this thread, so this is uncharted territory!
So to get the patches boot.img, we unpack the tar file posted in the OP?
Sent from my SM-P600 using Tapatalk
iridaki said:
So to get the patches boot.img, we unpack the tar file posted in the OP?
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Yes. xda does not allow me to post an image file greater than 8mb, but the P607T image is 10.5mb, so had to tar it. Decided to be consistent with all the images.
Technically, you can try to flash that .tar with ODIN, but in my case, it would not work. Only flashing the .img through TWRP did.
karthikrr said:
Yes. xda does not allow me to post an image file greater than 8mb, but the P607T image is 10.5mb, so had to tar it. Decided to be consistent with all the images.
Technically, you can try to flash that .tar with ODIN, but in my case, it would not work. Only flashing the .img through TWRP did.
Click to expand...
Click to collapse
Thank you! And thank you for providing us with a patched kernel!
I'll try rooting and installing Xposed tonight and report back!
iridaki said:
Thank you! And thank you for providing us with a patched kernel!
I'll try rooting and installing Xposed tonight and report back!
Click to expand...
Click to collapse
Technically its just a patched boot image with a STOCK kernel, but yea, glad to help The real work was done by Chainfire and garyd9 and SHM helped me put this thing together, so they deserve the thanks!
If you get Xposed on it, let me know which version. The official one does not work on TW LL yet, but I believe Wanam has another version out that does. I haven't had the time to install it and test it, so your review will be helpful.
karthikrr said:
Technically its just a patched boot image with a STOCK kernel, but yea, glad to help The real work was done by Chainfire and garyd9 and SHM helped me put this thing together, so they deserve the thanks!
If you get Xposed on it, let me know which version. The official one does not work on TW LL yet, but I believe Wanam has another version out that does. I haven't had the time to install it and test it, so your review will be helpful.
Click to expand...
Click to collapse
Any contribution is a worthy contribution!
Wanam Xposed works perfectly on my Note 4 and I think it will work on the 10.1 as well. I'll report back soon!
SM-P600-TWRP 2.8.7.0 touch input doesn't work, but stylus input does
Hi!
Thanks for your posts, I'm sifting through is now. I was reflashing TWRP 2.8.7.0 (for SM-P600) and discovered that it wasnt responding to touch input. But I quickly discovered that it's UI does respond to the s-pen
I'll share my rooting experience as soon as possible.
V
Hey !! Can you give me the ROM of Darkdroid for Micromax A177. Thanks
Vasishtha said:
Hi!
Thanks for your posts, I'm sifting through is now. I was reflashing TWRP 2.8.7.0 (for SM-P600) and discovered that it wasnt responding to touch input. But I quickly discovered that it's UI does respond to the s-pen
I'll share my rooting experience as soon as possible.
V
Click to expand...
Click to collapse
How do you make it? I cannot flash the twrp successfully, there is always an error saying ''Recovery is not SEAndroid Enforcing''.
iopxiang said:
How do you make it? I cannot flash the twrp successfully, there is always an error saying ''Recovery is not SEAndroid Enforcing''.
Click to expand...
Click to collapse
You should wait a few moments. TWRP will open.
Flashing the SU.zip ends up in Bootloop for me._.
Fabi7775 said:
You should wait a few moments. TWRP will open.
Flashing the SU.zip ends up in Bootloop for me._.
Click to expand...
Click to collapse
Did you flash the boot.img before flash SU?
iopxiang said:
Did you flash the boot.img before flash SU?
Click to expand...
Click to collapse
Actually not, sorry.
I just thougt it is worth a try.
The SM-P600 rooting(with your patched boot) was a success! I encountered no problems at all. Only the lack of touch responsiveness of twrp 2.8.x had me worried, but thankfully the s-pen had my back and I was able to browse the twrp UI with it.
I'm now restoring all my apps with titanium backup, I'll try out xposed later this afternoon.
Regarding the LL update: wow this tablet completely feels like a new device, the fluidity is just stunning. 60 fps animations
Vasishtha said:
The SM-P600 rooting(with your patched boot) was a success! I encountered no problems at all. Only the lack of touch responsiveness of twrp 2.8.x had me worried, but thankfully the s-pen had my back and I was able to browse the twrp UI with it.
I'm now restoring all my apps with titanium backup, I'll try out xposed later this afternoon.
Regarding the LL update: wow this tablet completely feels like a new device, the fluidity is just stunning. 60 fps animations
Click to expand...
Click to collapse
Finally, a confirmation Thanks for letting us know!
As for TWRP, I believe the 2.6.3.3 (or something else in the 2.6 series) works without any problems on the P600.
XPosed is officially not out for Samsung LL, BUT Wanam has a version in development that works well, according to @iridaki on this thread. If you switch TWRP or try Wanam Xposed, post an update here as well!
And yes, the LL update actually made the device feel so damn good, its practically a Note 10.1 (2015 Edition)!
karthikrr said:
Finally, a confirmation Thanks for letting us know!
As for TWRP, I believe the 2.6.3.3 (or something else in the 2.6 series) works without any problems on the P600.
XPosed is officially not out for Samsung LL, BUT Wanam has a version in development that works well, according to @iridaki on this thread. If you switch TWRP or try Wanam Xposed, post an update here as well!
And yes, the LL update actually made the device feel so damn good, its practically a Note 10.1 (2015 Edition)!
Click to expand...
Click to collapse
Twrp 2.6.x does work, however there is no option to flash .img files on those versions.
So you either have to use heimdall or something else in order to flash that boot.
The unofficial xposed 5.1.x on my nexus 5 worked without any problems, so I expect the same for the LL variant. But I'll keep you posted.
The multiwindow transitions now have fade in/out effects <3 and we now can snap floating windows to either the left or right sides D:
karthikrr said:
Update 3: The patched P600 image has been confirmed to work by @Vasishtha, who also says TWRP 2.8.7.0 works with the S-Pen, but no touch input.
Click to expand...
Click to collapse
Can we use Temasek's 2.8.7.0 TWRP that has touch working?
Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)
You don’t unzip the .tar files. Keep them as is.
secretwolf98 said:
You don’t unzip the .tar files. Keep them as is.
Click to expand...
Click to collapse
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5
My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.
fountainb234 said:
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5
Click to expand...
Click to collapse
Just rename the file cutting off the .md5.
is it possible to downgrade from sk5 to sk1? you cannot upgrade to a later version, and I know downgrading can have reverse effects on the tablet. I have same tablet I would like to know. if I flash sk1 is there a way to fix it if it bricks?
Magendanz said:
My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.
Click to expand...
Click to collapse
fountainb234 said:
Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)
Click to expand...
Click to collapse
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!
framC0 said:
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?
framC0 said:
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?
Click to expand...
Click to collapse
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.
lewmur said:
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.
Click to expand...
Click to collapse
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
EDIT: i dont have OEM unlock option in DEV but its unlocked, i checked when in downloaded mode it says "lock device and..." so its unlocked.
framC0 said:
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
Click to expand...
Click to collapse
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.
lewmur said:
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.
Click to expand...
Click to collapse
YES!!!!!! YOU ARE THE BEST!!!! Done! It booted directly to TWRP!!! THANK YOU!!!! So now will flash Magisk with twrp right? Alawys rooted my devices but this 510 wow...never saw a thing like this
Edit: The fight continues - So i did wipe and format data in TWRP and reboot system and im IN. Installed Magisk 23.0.apk and noticed that im still with "RAMDISK: no"... Searching how to do next to root! Im very near of the goal!!!! Finally! Big thanks to lewmur!
lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file.
Click to expand...
Click to collapse
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
EDIT: Since an older version dont know witch, Magisk Manager and Magisk are joined in apk so i just flashed Magisk 23.0.apk in TWRP...rooted!!! DONE!!!! FINALLY
framC0 said:
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
Click to expand...
Click to collapse
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.
lewmur said:
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.
Click to expand...
Click to collapse
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!
framC0 said:
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!
Click to expand...
Click to collapse
USB cables are notorious for being flaky. Sometimes it helps to just turn the cable over and plug it back in. I always keep several on hand so that if I have connection problems I can try another cable.
I have Moto G7 (River, XT1962-4) with the bootloader unlocked by fastboot ("fastboot oem unlock <unlock code>"). I am ready to install LineageOS, and I haven't yet installed a recovery package.
However, it appears that the A/B slots (partitions?) are still causing a lot of ROM install difficulty. especially with the moto g7. So, it's a bit concerning.
The problem seems to stem from the fact that, when slot A is active and one flash esLineage OS using TWRP (or Lineage recovery), the image is written to slot B and and the phone switches to booting from slot B. Then, rebooting fails because there is no bootloader in slot B. Is my understanding correct?
It seems that most favor TWRP over the LineageOS recovery package. So, I would like to install TWRP.
The LineageOS instructions for temporarily booting and installing TWRP differ from the install instructions given on the TWRP Moto G7 page.
The Lineage page directs the user to employ fast boot ("fastboot flash boot <twrp_filename>.img") with "a boot__a" or "boot__b" flag, to install TWRP to the desired slot. Unfortunately, these instructions don't tell how/where to use that flag in the fastboot command syntax.
On the other hand, the TWRP page instructs users to install TWRP via their installer. That TWRP installer puts TWRP in both the A and B slots.
It seems that the TWRP procedure is more foolproof, but does that method bork the later steps given in the LineageOS instructions?
The next step is given in the "Pre-install instructions" on the LineageOS page. It says to sideload the copy-partitions.zip package with TWRP booted (and already installed).
The copy-partitions.zip package copies slot A to slot B (or vice versa), so that it exists in whichever slot the phone chooses. This process is explained in the LineageOS install page for the Moto G7. This process seems easy, but, again, will it be borked by the previous TWRP installer that addressed both slots?
The rest of the procedure seems fairly straightforward, but will my phone be rooted automatically? If not, how does one root the phone (what app/package should I use)?
Also, in most ROM install tutorials on the Interwebs, there usually comes a point in which certain things are "wiped," such as "Dalvic/ART cache," "cache" and "data." I see that there is a "Wipe" step and a "Format" step in the "Installing LineageOS from recovery" section of the Lineage instructions, but neither step specifies "Dalvic/ART cache," "cache" nor "data." Are those the things that are being wiped?
Thanks very much!
go on telegram and get instructions there as XDA is outdated
HueyT said:
go on telegram and get instructions there as XDA is outdated
Click to expand...
Click to collapse
Thank you for the reply!
I am not familiar with Telegram. Does one have to give their phone number and other sensitive information to sign up there?
What do you mean by "XDA is outdated?" I see lots of recent posts on this forum, with one or two that specifically pertain to the problems regarding attempting a LineageOS install on a Moto G7.
Hopefully, somebody here has experience dealing with A/B partitions and can give me a quick answer as to whether or not using the TWRP installer will bork things, when I later try to copy the bootloader to the inactive slot by sideloading "copy-partition.zip."
Thanks!
tuppb said:
Thank you for the reply!
I am not familiar with Telegram. Does one have to give their phone number and other sensitive information to sign up there?
What do you mean by "XDA is outdated?" I see lots of recent posts on this forum, with one or two that specifically pertain to the problems regarding attempting a LineageOS install on a Moto G7.
Hopefully, somebody here has experience dealing with A/B partitions and can give me a quick answer as to whether or not using the TWRP installer will bork things, when I later try to copy the bootloader to the inactive slot by sideloading "copy-partition.zip."
Thanks!
Click to expand...
Click to collapse
Installation instructions on LOS page are not good. If you go to the AEX rom here on XDA, those instructions are better. The thing is XDA is not really used by the devs too much. Its better to go to the telegram group. The only info telegram uses is your phone number to sync up.
http://t.me/motog7river
Also, telegram group has many more roms, and if you have problems its much easier to get help there.
JAS_21 said:
Installation instructions on LOS page are not good. If you go to the AEX rom here on XDA, those instructions are better. The thing is XDA is not really used by the devs too much. Its better to go to the telegram group. The only info telegram uses is your phone number to sync up.
Also, telegram group has many more roms, and if you have problems its much easier to get help there.
Click to expand...
Click to collapse
Thank you!
I searched for a specific AEX (aosp extended) rom section on this forum, and I couldn't find one. I did find a few threads regarding releases, but no official install instructions. Couldn't find anything on the AEX site, too. Do you have a link to those instructions?
I am unable to get on Telegram -- can't give out my phone number and online SMS sites seem to be useless.
It's a shame that folks don't use open forums such as this one.
Thanks!
UPDATE: I am happy to report that _Clon_'s guide to installing Lineage 17.1 worked on my Moto G7!
If you get an error message when using fastboot to set the active slot to "_a" in step 1.4, move on, because setting the active slot to "_a" can wait until step 1.6 whne it is set with TWRP.
By the way, when I ran the "fastboot getvar all" (in step 1.3), it showed that my current slot was "_b" and that slot "_a" was not bootable. Slot "_a" became bootable when I ran the TWRP installer (in step 4.1). My LineageOS 17.1 install runs from slot "_a".
In addition, it seems that Lineage Recovery has some advantages over TWRP. I have seen posts in other forums suggesting that LOS OTA updates will install Lineage Recovery over the installed TWRP (which is what I want).
Thanks, _Clon_!
Was running older version of Magisk+Manager all 100% fine, trying to update to the new Magisk v22 apk.
reading guide here: https://topjohnwu.github.io/Magisk/install.html
it seems the device does NOT have a randisk (says NO), which means, one takes the *recovery* path (in the steps)
I have the TWRP recovery image used, and patched it using the Magisk that was on the phone, selected 'recovery method', selected the file, and it wrote:
/sdcard/Download/magisk_patched_f7KJH.img
Click to expand...
Click to collapse
so, pulled the file to PC:
adb pull /sdcard/Download/magisk_patched_f7KJH.img
Click to expand...
Click to collapse
then rebooted into FASTBOOT mode, and flashed that recovery image using:
fastboot flash recovery magisk_patched_f7KJH.img
Sending 'recovery' (65536 KB) OKAY [ 2.079s]
Writing 'recovery' OKAY [ 5.316s]
Finished. Total time: 7.408s
Click to expand...
Click to collapse
However, phone boots showing magisk is not installed, well, there is an icon Magisk, but it says v22 needs to be installed, but using that install button does not work, it appears to succeed, but doesn't do anything
Read on that page above , that one can RENAME the magisk v22 .apk to .zip, and FLASH the ZIP file from TWRP!!!
So, did that , renamed Magisk-22.0(22000).apk to .zip, when when booted into TWRP to flash this zip it says:
Checking for Digest file...
Zip file is corrupt!
Error installing zip file '/external_sd/Download/Magisk-22.0(22000).zip
Click to expand...
Click to collapse
So, it's a bit confusing.. Does anyone have steps for Redmi 7a? which does not appear to have ramdisk...
I thought it would imply be to patch the TWRP image file to using Magisk, then flashing the recovery image on to the recovery partition..
Corrections welcomed.
Stormy.
EDIT: ROM MIUI Global 10.2.5 | Stable 10.2.5.0 (PCMMIXM)
The error flashing comes from:
Installation
The Magic Mask for Android
topjohnwu.github.io
Download the Magisk APK
Rename the .apk file extension to .zip, for example: Magisk-v22.0.apk → Magisk-v22.0.zip. If you have trouble renaming the file extension (like on Windows), use a file manager on Android or the one included in TWRP to rename the file.
Flash the zip just like any other ordinary flashable zip.
Click to expand...
Click to collapse
Rename was easy, but flashing the zip from TWRP claimed it is corrupted. also read the "Magisk in recovery", however, trying this gets me to recovery mode (TWRP):
(Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
Click to expand...
Click to collapse
A bit confusing on how the new magisk works, the over-use of the term 'magisk' causes it to be incredibly hard to understand what is new/old/what/where/how things are laied out. Anythanks, thanks for any tips.
Stormy.
stormy1777 said:
Was running older version of Magisk+Manager all 100% fine, trying to update to the new Magisk v22 apk.
reading guide here: https://topjohnwu.github.io/Magisk/install.html
it seems the device does NOT have a randisk (says NO), which means, one takes the *recovery* path (in the steps)
I have the TWRP recovery image used, and patched it using the Magisk that was on the phone, selected 'recovery method', selected the file, and it wrote:
so, pulled the file to PC:
then rebooted into FASTBOOT mode, and flashed that recovery image using:
However, phone boots showing magisk is not installed, well, there is an icon Magisk, but it says v22 needs to be installed, but using that install button does not work, it appears to succeed, but doesn't do anything
Read on that page above , that one can RENAME the magisk v22 .apk to .zip, and FLASH the ZIP file from TWRP!!!
So, did that , renamed Magisk-22.0(22000).apk to .zip, when when booted into TWRP to flash this zip it says:
So, it's a bit confusing.. Does anyone have steps for Redmi 7a? which does not appear to have ramdisk...
I thought it would imply be to patch the TWRP image file to using Magisk, then flashing the recovery image on to the recovery partition..
Corrections welcomed.
Stormy.
EDIT: ROM MIUI Global 10.2.5 | Stable 10.2.5.0 (PCMMIXM)
Click to expand...
Click to collapse
You need to patch the file: boot.img
VD171 said:
You need to patch the file: boot.img
Click to expand...
Click to collapse
Why do you write that? Reading here:
Installation
The Magic Mask for Android
topjohnwu.github.io
says:
Patching ImagesIf your device has boot ramdisk, you need a copy of the boot.img
If your device does NOT have boot ramdisk, you need a copy of the recovery.img
Click to expand...
Click to collapse
The Redmi 7A says RAMDISK *NO* on the Magisk app, which reads to me as I have to patch the recovery.img, in my case recovery is TWRP, so that is the image I gave it.
Has anyone managed to get Magisk v22 on Redmi 7a? any steps? if not, may have to revert back to the prior set up which worked, until this is sorted out.
Thanks for any specific tips to devices withOUT ramdisk=yes, like Redmi 7A.
Stormy.
Yes, I read.
You can't patch TWRP using magisk.
If you want to apply magisk patched to the recovery, then patch the boot.img and then flash it to recovery.
You can ignore the info about ramdisk, just patch the stock boot.img and then flash it to the boot partition.
Good luck
Thanks, quick update from a "naive-end user" Before your second reply, re-read and noticed using the TWRP recovery image, and not the STOCK/ROM, so, pulled stock recovery.img, patched it, flashed to recovery partition.. all OK..
Now, on normal boot, no Magisk or root; on boot through recovery it goes into stock recovery, even leaving the up-vol key immediately when logo disappears does not do it, it simply boots normally without root/magisk installed
This is how easy one can take a perfectly working env to no root, no TWRP
Now, taking your advise and patch using magisk 22 the stock boot.img, here goes:
cksum:
Code:
4261103684 33554432 boot-stock1025.img
(after patching w/Magisk v22):
Code:
245310758 33554432 magisk_patched_U6lEU.img
flash in fastboot:
Code:
c:> fastboot flash boot magisk_patched_U6lEU.img
target reported max download size of 535822336 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.034s]
writing 'boot'...
OKAY [ 0.886s]
finished. total time: 1.924s
it boots OK, but, magisk v22 says "no magisk installed"
I now recall that no matter which version of Magisk, the self-patching , i.e. on the actual device, NEVER WORKED, I've reported that many times in the past on this forum, but no clear answer. The only way I could root in the first place was to download an already patched boot.img that I use till yesterday.. that was posted on the forum here.
So, does anyone have a dump of boot.img patched to magisk v22 for Redmi 7A?
Or, alternatively, knows why patching of boot.img using v22 does not work?
Thanks.
Stormy.
Searching online, seems others w/Xiamoi devices having similar issues/confusions, this thread claims to RESOLVE:
Invalid - Magisk v22.0 issue [RESOLVED]
hi every one could anyone explain how we could update the latest magisk 22 because the magisk manager is no longer available....i turned the apk to zip file and it didnt want to be installed at all it gives you an error message THE DEVICE IS NOT BOOTING TO SYSTEM IT DIRECTS TO FASTBOOT....any...
xiaomi.eu
but does not say exactly HOW.. I've patched the Magisk uninstaller
https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip
so, no magisk at all, but when renaming magisk 22.img to magisk22.zip and trying to flash in TWRP, it says zip file is corrupted in red and flashing stops.
One more tip found these errors in the magisk patching log!!
Code:
Output file is written to
/storage/emulated/0/Download/magisk_patched_35S0f.img
****************************
cp: can't preserve ownership of 'busybox': Operation not permitted
cp: can't preserve ownership of 'magisk32': Operation not permitted
cp: can't preserve ownership of 'magisk64': Operation not permitted
cp: can't preserve ownership of 'magiskboot': Operation not permitted
cp: can't preserve ownership of 'magiskinit': Operation not permitted
- All done!
don't know how to resolve, found on:
Bootloop on Xiaomi Redmi 9 · Issue #3985 · topjohnwu/Magisk
Hi there, I'm trying to root my Redmi 9, alas it doesn't seem to be working. MIUI version: 12.0.1.0 (QJCEUXM) Android Version 10 QP1A.190711.020 I have unlocked the bootloader (open padlock icon on...
github.com
mention to flash *vbmeta*, so did that as well as patched v22 boot.img, and still it no root, magisk says it is not installed.
After full day downtime, and 50+ attempts most before posting, decided to revert back to Magisk v21.4/manager 8.0.7, installed riru/riru-edxposed within 5 minutes, phone is rooted all is fine. will re-try once someone announces success on Redmi 7A or someone provides a working pre-patched boot.img debug is also possible, more time for that path in 2 weeks.
Thanks Stormy.
@stormy1777
For the Redmi 7A you must have a patched boot.img to install Magisk with TWRP.
The problem is, the boot.img is a 32 bit img with a fake Ramdisk for a 64 bit processor.
Please look here: Install Magisk 22
MOFI69 said:
@stormy1777
For the Redmi 7A you must have a patched boot.img to install Magisk with TWRP.
The problem is, the boot.img is a 32 bit img with a fake Ramdisk for a 64 bit processor.
Please look here: Install Magisk 22
Click to expand...
Click to collapse
Incredible! If i read this right, you seem to say that Magisk can NOT patch the boot.img on the Redmi 7A due to the 32/64 bit issue relating to ramdisk?
I felt that all along, just couldn't prove it, used a pre-existing patched boot.img from day1, and never managed to patch directly on the phone Was that reported to Magisk team? or they can't fix it from a technical perspective?
will find the time (in few days) to play with this patching, if it works will post patched MIUI Global 10.2.5 | Stable 10.2.5.0 (PCMMIXM) image
Thanks.
Completely correct, Xiaomi installed a 32-bit operating system because the smartphone only has 2 GB of RAM. Not enough to work properly with a 64 bit operating system. Topjohnwu published the information on its Github page and criticized Xiaomi very much for this behavior. The original boot.img contains a ramdisk, but only as a placeholder, so when repackaging it is added with 0 MB to the boot.img. Therefore the image is smaller (approx. 15 MB) than the original.
Why don't you update to 12.xx.xx right away?
MOFI69 said:
Completely correct, Xiaomi installed a 32-bit operating system because the smartphone only has 2 GB of RAM. Not enough to work properly with a 64 bit operating system. Topjohnwu published the information on its Github page and criticized Xiaomi very much for this behavior. The original boot.img contains a ramdisk, but only as a placeholder, so when repackaging it is added with 0 MB to the boot.img. Therefore the image is smaller (approx. 15 MB) than the original.
Why don't you update to 12.xx.xx right away?
Click to expand...
Click to collapse
Dear Mofi69 in a small town by Berlin
Thank you SOOO much for such nice explanations, goes a long way to "trickle" down information to lowly people
Not moving to ROM 12, due to lack of time to "play with this", have several phones, and it would mean more time spent on it, for no "visible" significant benefit. I don't work for CIA or have anything secret, phone is not used in public places, mostly home, and wifi, so, security is not really an issue as they make it.. switching ROM sounds too many moving-parts and there are TONS of old apps that are already working, many not from app store we live with it fine. on a new phone, we'll upgrade, I'm certain ...
in next few days will try the magisk patching again (I was selecting "recovery" due to the ramdisk=no confusion), MAYBE they fixed it, and will produce a valid image, I can't think that the magisk binary would not have full control of their output, so as to make it exactly the right size/layout.. if it fails, will try the python patcher. Thanks so much for this info!!
Stormy.
stormy1777 said:
Dear Mofi69 in a small town by Berlin
Click to expand...
Click to collapse
Oh, oh, what kind of garbage did I write there, it comes from when you are not careful in English class ...
Only for you...
there is now the "OLD" boot.img, ready pached with the oss-patcher. Please install Magisk via TWRP (magisk.zip), boot.img from
miui_PINEGlobal_V10.2.5.0.PCMMIXM_7380681456_9.0
Important: I cannot test it! Please let me know if it works.
Best regards
Michael
Thanks friend for the help!!! Spent few more hours, eventually managed to get it, but not sure HOW
Starting point, Magisk 21.4/Manager 8.0.4 (not hidden), rooted, boot into TWRP, and flash:
1) patched boot.img from you
2) flash Magiskv22.zip confirmed md5sum:
Code:
e14132835b4cc0878639fcf645db479c Magisk-v22.0.zip
noticed that this flashing of zip appears to overwrite the boot.img, ignored it for the time being.
booted OK, said Magisk 22 is installed on the TOP part of the app, BUT, on the bottom, it showed Latest v22, and installed 8.0.4, and said, your device needs more updates, it will now download v22 and install, click ok,
rebooting in 5 seconds, and it comes back to the same spot, again, your machine needs more updates , click OK, again, download, rebooting in 5 seconds, and no change. Clicking CANCEL allows pressing the UPDATE button.. that doesn't help either.
Went to TWRP again, flashed your boot-patched.img , it then appear to not have any Magisk installed at all
so, installed v22 APK from the running phone, it then showed app/manager v22, but no magisk installed, so recalling that flashing the ZIP made it appear that magisk v22 IS installed, so flashed the ZIP in TWRP and it booted ok, and appears to have v22 installed on both parts of the app.
I'm thinking the steps should be:
1) Install Magisk v22 APK from phone
2) reboot into TWRP and flash the patched boot.img
3) if does not work, flash magisk v22 from twrp..
Sorry for "reinventing" what is known to all just couldn't find a "guide" with correct order for Redmi 7a...
Stormy.
PS: @MOFI69 , after an hour or so, got a pop up with long hex value and it said to send 1 BTC there to continue using the phone, I did that, then same message appeared on Android TV, did that, now on the Android Dog Collar do you think it has anything to do w/that boot.img u patched
Just kidding friend, have fun!!
Since the phone was already rooted (with a manipulated boot.img unknown to me) it can lead to strange malfunctions.
The best and easiest way is to uninstall Magsik (from the manager); REBOOT TO TWRP; INSTALL THE ORIGINAL boot.img and immediately afterwards my leased and immediately magisk V22, no reboot in between.
Then reboot into the system and install the magisk V22.apk, sometimes it is already there as a "shadow", then just start, it installs itself.
ok, may try that, only thing is that uninstalling magisk mgr, will lose all the "settings", like which app is granted root, and modules installed?
the way i did seems to work (i don't know exactly the steps yet), but it kept all settings/permissions, of all rooted apps...
Strange is that flashing magisk v22 appear to patch the boot.img, so question is why your boot.img is needed if it gets flashed later... not doubting it is, just asking.. ok, will try another phone and see...
S
Yes, the settings of Magisk have to be recreated again, as with a first-time installation. All possibly installed modules must be removed beforehand!
The boot.img is always pached by magisk, which is not possible without a boot.img edited with oss-patcher. The 32 bit ramdisk is missing (the operating system is recognized as this by magisk), so it cannot be installed. The patch only adds an interface so that magisk can install "redirection" for root access.
I think the boot.img you have used so far already contains a permanently installed magisk version, is often done this way on other chinese telephones, it works, but an update of magisk is mostly not possible, hence your problems.
In "my" boot.img there is no magisk preinstalled and updates are possible at any time. Unfortunately, I can't tell you whether your type of installation will work in the long term, you'll notice that with the next update ;-)
Thanks for the GREAT explanation!! yes, current boot.img I could not apply magisk updates smoothly, had to always flash from recovery, and that worked fine.
Manage to update without having to reinstall all modules, all remained, vanced, etc. so far leaving it.. I used to have 5 days to play with such things, now, 5 hours is hard to get, naively I expected it to be 5-min
Also managed to root a totally brand new phone using your boot.img + magisk v22, here one must add vbmeta.img as well as Permissiver_v4.zip, not entirely clear on right order, eventually it worked
Thanks much to @MOFI69
Stormy.
Super that makes me happy!
Then have fun with your Redmi
Best wishes
Hey,
I've installed https://forum.xda-developers.com/t/...g-galaxy-tab-a-7-0-sm-t280-gtexswifi.4158061/ on a SM-T280 that has TWRP 3.2.1-1 recovery installed, using TWRP zip install.
It had been rooted before with SuperSU, so I wanted to root it again with SuperSU (I have reasons for not trying Magisk).
I've tried SuperSU v2.82 and v2.78 from https://forum.xda-developers.com/t/...amsung-galaxy-tab-a6-sm-t280-sm-t285.3475381/ also by installing the zip in TWRP.
When the zip installs, it chooses systemless root. The logs seem fine, no errors, it patches the boot partition.
However, the tablet won't boot. It stays in the "Galaxy Tab A6" screen forever.
When I restore a backup of the previous boot partition, it boots fine again. So I guess it produces a bad boot image when trying to patch it.
Am I missing something obvious here or should it work that way?
RFZ said:
Hey,
I've installed https://forum.xda-developers.com/t/...g-galaxy-tab-a-7-0-sm-t280-gtexswifi.4158061/ on a SM-T280 that has TWRP 3.2.1-1 recovery installed, using TWRP zip install.
It had been rooted before with SuperSU, so I wanted to root it again with SuperSU (I have reasons for not trying Magisk).
I've tried SuperSU v2.82 and v2.78 from https://forum.xda-developers.com/t/...amsung-galaxy-tab-a6-sm-t280-sm-t285.3475381/ also by installing the zip in TWRP.
When the zip installs, it chooses systemless root. The logs seem fine, no errors, it patches the boot partition.
However, the tablet won't boot. It stays in the "Galaxy Tab A6" screen forever.
When I restore a backup of the previous boot partition, it boots fine again. So I guess it produces a bad boot image when trying to patch it.
Am I missing something obvious here or should it work that way?
Click to expand...
Click to collapse
Try this link.
lewmur said:
Try this link.
Click to expand...
Click to collapse
Thx, I'll try it, but I don't understand it.
It requires me to download and flash a kernel (boot.img) at the end. This will overwrite any changes the SuperSU installer made to the boot partition during its install. And if I understand system-less root correctly, it will essentially undo everything the installer did. Also, one kernel can't just run any Android version - usually it's tied to a specific Android version?
I'll report if it works. If it does, someone needs to explain to me how.
lewmur said:
Try this link.
Click to expand...
Click to collapse
Didn't work. To be fair, even https://forum.xda-developers.com/t/...amsung-galaxy-tab-a6-sm-t280-sm-t285.3475381/ mentions this step (I kinda missed it).
Instead of freezing at "Galaxy Tab A6" it boot-loops. It even enumerates on USB after 20s of booting and provides adb, but shell commands available are limited. It doesn't even know `ls`. 10s later it reboots.
As said before, I do not understand this procedure. My impression was that systemless root only modifies the kernel / boot.img. So flashing another boot.img after that seems strange.
RFZ said:
Didn't work. To be fair, even https://forum.xda-developers.com/t/...amsung-galaxy-tab-a6-sm-t280-sm-t285.3475381/ mentions this step (I kinda missed it).
Instead of freezing at "Galaxy Tab A6" it boot-loops. It even enumerates on USB after 20s of booting and provides adb, but shell commands available are limited. It doesn't even know `ls`. 10s later it reboots.
As said before, I do not understand this procedure. My impression was that systemless root only modifies the kernel / boot.img. So flashing another boot.img after that seems strange.
Click to expand...
Click to collapse
At what point did it fail? Did you boot to TWRP recovery after flashing it. IOW, before doing anything with SU?
lewmur said:
At what point did it fail? Did you boot to TWRP recovery after flashing it. IOW, before doing anything with SU?
Click to expand...
Click to collapse
What I did:
I booted TWRP and restored a boot.img I backuped yesterday (working LineageOS).
I rebooted to confirm it works. It did.
I booted into TWRP, copied "SR1-SuperSU-v2.78-SR1-20160915123031.zip" and "boot.img" (extracted from "supersu_2.78_SR1_systemless_boot_t280.tar") to the device.
Then installed "SR1-SuperSU-v2.78-SR1-20160915123031.zip" (install zip) and installed "boot.img" as "boot".
Then I rebooted.
Now it shows "Galaxy Tab A6" for 30s and the reboots. Over and over again.
I watched it many times, then booted TWRP again, restored the backup boot.img and it is back.
RFZ said:
What I did:
I booted TWRP and restored a boot.img I backuped yesterday (working LineageOS).
I rebooted to confirm it works. It did.
I booted into TWRP, copied "SR1-SuperSU-v2.78-SR1-20160915123031.zip" and "boot.img" (extracted from "supersu_2.78_SR1_systemless_boot_t280.tar") to the device.
Then installed "SR1-SuperSU-v2.78-SR1-20160915123031.zip" (install zip) and installed "boot.img" as "boot".
Then I rebooted.
Now it shows "Galaxy Tab A6" for 30s and the reboots. Over and over again.
I watched it many times, then booted TWRP again, restored the backup boot.img and it is back.
Click to expand...
Click to collapse
The only thing I see that doesn't match the instructions is restoring the backup boot.img prior to installing SR1.
lewmur said:
The only thing I see that doesn't match the instructions is restoring the backup boot.img prior to installing SR1.
Click to expand...
Click to collapse
Sure. But the instructions ask me to replace my entire boot partition with a static file I downloaded from the internet. Everything I did to the boot partition before is meaningless.
Clearly the kernel in the patched boot.img is not designed for the Android Version LineageOS 14.1 uses. You can't just boot any android with any random kernel, right?
RFZ said:
Sure. But the instructions ask me to replace my entire boot partition with a static file I downloaded from the internet. Everything I did to the boot partition before is meaningless.
Clearly the kernel in the patched boot.img is not designed for the Android Version LineageOS 14.1 uses. You can't just boot any android with any random kernel, right?
Click to expand...
Click to collapse
By your own reasoning, you can't use just any boot.img with what superSU file you're installing. You have to use the one TWRP installed. All I know is that every time someone reports a boot loop it is because they failed to follow the EXACT steps in the instructions.
lewmur said:
By your own reasoning, you can't use just any boot.img with what superSU file you're installing. You have to use the one TWRP installed. All I know is that every time someone reports a boot loop it is because they failed to follow the EXACT steps in the instructions.
Click to expand...
Click to collapse
My guess is that whoever wrote these instructions knew that the SuperSU install script isn't compatible with the device and will corrupt its boot partition. He probably fixed it or rooted it manually on his own and provided a rooted version of his boot.img instead. He still asks you to perform the regular setup as it not only will corrupt the boot partition but also install SuperSU.apk to the data partition.
However, this means it will only work with the Android version he used when he created the boot.img. So probably the most recent available stock ROM when the instructions were written. But not Android 7.1.
RFZ said:
My guess is that whoever wrote these instructions knew that the SuperSU install script isn't compatible with the device and will corrupt its boot partition. He probably fixed it or rooted it manually on his own and provided a rooted version of his boot.img instead. He still asks you to perform the regular setup as it not only will corrupt the boot partition but also install SuperSU.apk to the data partition.
However, this means it will only work with the Android version he used when he created the boot.img. So probably the most recent available stock ROM when the instructions were written. But not Android 7.1.
Click to expand...
Click to collapse
That may be true but you won't get an answer here. Post the question in that thread. But the dev may well have move on to a later device. The 280 dates back to 2016.
lewmur said:
That may be true but you won't get an answer here. Post the question in that thread. But the dev may well have move on to a later device. The 280 dates back to 2016.
Click to expand...
Click to collapse
Yep, confirmed my theory. I compared the original LineageOS 14.1 boot partition (from my backup) with the one the SuperSU installer creates that won't boot at all using a Hex-Editor. The one SuperSU installer created is missing an additional 0x200 bytes header that the original one had. I simply copied the first 0x200 bytes from the original into the one SuperSU installer created, removed the last 0x200 bytes of the image so the size fits, and flashed it.
And it works.
So I guess the SuperSU installer works with every Android Version on the SM-T280, but you have to add the additional 0x200 bytes from the original partition. (Probably also something one could simply patch in the SuperSU installer)
I've attached the image that works with LineageOS 14.1 on the SM-T280 and SuperSU installer 2.78.
Procedure is the same as:
1) Install SuperSU 2.78.zip in TWRP
2) Flash attached image (extracted from zip) to "boot" using TWRP
EDIT:
removed the attached image. See https://forum.xda-developers.com/t/...sm-t280-sm-t285.3475381/page-13#post-87442015
RFZ said:
Yep, confirmed my theory. I compared the original LineageOS 14.1 boot partition (from my backup) with the one the SuperSU installer creates that won't boot at all using a Hex-Editor. The one SuperSU installer created is missing an additional 0x200 bytes header that the original one had. I simply copied the first 0x200 bytes from the original into the one SuperSU installer created, removed the last 0x200 bytes of the image so the size fits, and flashed it.
And it works.
So I guess the SuperSU installer works with every Android Version on the SM-T280, but you have to add the additional 0x200 bytes from the original partition. (Probably also something one could simply patch in the SuperSU installer)
I've attached the image that works with LineageOS 14.1 on the SM-T280 and SuperSU installer 2.78.
Procedure is the same as:
1) Install SuperSU 2.78.zip in TWRP
2) Flash attached image (extracted from zip) to "boot" using TWRP
Click to expand...
Click to collapse
Glad you got it working. Did you post this info in the other thread? That is probably where someone else would look for the info.
lewmur said:
Glad you got it working. Did you post this info in the other thread? That is probably where someone else would look for the info.
Click to expand...
Click to collapse
Not yet. I will try to fix the SuperSU installer and also try it with SuperSU 2.82. Supplying a boot.img is really not the best idea and a fixed installer would be a far better solution.
It's just an additional offset of 0x200 when writing the modified image. Can't be hard to fix. I'll look into it tomorrow.
Edit: Posted a patched SuperSU installer here:
[RECOVERY][ROOT][TWRP 3.2.1-1][Magisk v14] Samsung Galaxy Tab A6 SM-T280/SM-T285
TWRP custom recovery for the Tab A SM-T280/T285. Latest build is 3.2.1-1 Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised. NOTE: BEFORE MAKING MODIFICATIONS, ON SOME...
forum.xda-developers.com
Didn't work for 2.82 though, just for 2.78
Edit: Got it working for 2.82 too, see link above.