Related
Hi all, I posted this in the 6P bootloop thread, but didn't get a response. As that is a pretty LONG thread, i'm thinking my question may have gotten lost in the jumble.
Quick run down.
A few months back my 6P started the BLOD. I found the fix listed on these pages, applied it, and have been happily using my phone ever since. Phone is bone stock 7.1.2 other than the TWRP recovery and the modified EX kernel for 4 cores.
Since the fix, my phone FINALLY got the OTA update to go to Android 8.0 and i obviously want to get it done. My concern is HOW to do this without causing more headache.
Can anyone point me in the right direction? Should i use the OTA update or download the factory image from Google?
I've got some knowledge as i used to be into the "rooting" scene back in the day, but haven't for a while, so i feel a little lost.
Thanks for any help.
johnnyphive said:
Hi all, I posted this in the 6P bootloop thread, but didn't get a response. As that is a pretty LONG thread, i'm thinking my question may have gotten lost in the jumble.
Quick run down.
A few months back my 6P started the BLOD. I found the fix listed on these pages, applied it, and have been happily using my phone ever since. Phone is bone stock 7.1.2 other than the TWRP recovery and the modified EX kernel for 4 cores.
Since the fix, my phone FINALLY got the OTA update to go to Android 8.0 and i obviously want to get it done. My concern is HOW to do this without causing more headache.
Can anyone point me in the right direction? Should i use the OTA update or download the factory image from Google?
I've got some knowledge as i used to be into the "rooting" scene back in the day, but haven't for a while, so i feel a little lost.
Thanks for any help.
Click to expand...
Click to collapse
Well, for starters do NOT take the OTA. It will either fail or boot loop your phone. Due to the fact you have a modified boot.img you will need to update manually using fastboot with the full image. Re-apply the modified kernel after you finish updating the partitions, but BEFORE booting the first time. You can follow most guides on how to manually update a full image using fastboot, just add the step of flashing the modified kernel before booting.
Thanks for the reply and the help. If i could ask for a little more help, as this is my only phone.
Can you explain the difference between the modified boot.img and the modified kernel?
If i download the factory image from here (https://developers.google.com/android/images) is it ok to the get the latested one (Nov 2017) or do i need to get the original one (Sep 2017 as i'm on Fi)
Once i flash the factory image, is it going to replace the modified boot image as well as the modified kernel?
Follow the OP on this thread (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) in the downloads section there appear to be 2 files i would need, the "Boot.img from stock 6.17, 8.0 firmware" and "EX kernel version 5.03". Am i understanding that correctly?
Like i said, this is my only phone, and i'm probably just being overly paranoid about bricking it, but any clarification would be greatly appreciated.
johnnyphive said:
Thanks for the reply and the help. If i could ask for a little more help, as this is my only phone.
Can you explain the difference between the modified boot.img and the modified kernel?
If i download the factory image from here (https://developers.google.com/android/images) is it ok to the get the latested one (Nov 2017) or do i need to get the original one (Sep 2017 as i'm on Fi)
Once i flash the factory image, is it going to replace the modified boot image as well as the modified kernel?
Follow the OP on this thread (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) in the downloads section there appear to be 2 files i would need, the "Boot.img from stock 6.17, 8.0 firmware" and "EX kernel version 5.03". Am i understanding that correctly?
Like i said, this is my only phone, and i'm probably just being overly paranoid about bricking it, but any clarification would be greatly appreciated.
Click to expand...
Click to collapse
Use the latest November image. The boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. When you flash the new boot.img contained in the Google image, it will overwrite the patched kernel. You then need to re-patch it by installing EX kernel before booting. EX writes to (modifies) the stock boot.img. There are also pre-modifed boot.img files floating around. You will probably get more detailed help in the dedicated thread. Learning to flash manually (or remember how) is not really a big deal and a necessary skill for modding (and for getting yourself out of trouble). Good luck. :good:
v12xke said:
Use the latest November image. The boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. When you flash the new boot.img contained in the Google image, it will overwrite the patched kernel. You then need to re-patch it by installing EX kernel before booting. EX writes to (modifies) the stock boot.img. There are also pre-modifed boot.img files floating around. You will probably get more detailed help in the dedicated thread. Learning to flash manually (or remember how) is not really a big deal and a necessary skill for modding (and for getting yourself out of trouble). Good luck. :good:
Click to expand...
Click to collapse
Ok, so 1 last time (sorry)
1 - Downloaded the latest 8.0.0 factory image from google (this contains the bootloader, radio, and partitions (.zip).
2 - Get phone to fastboot and apply the above 3 new images
3- before rebooting, flash oreo4core (new, modified boot.img), TWRP recovery.img
4- reboot to recovery (TWRP) and apply the modified EX kernel
5 - reboot and (hopefully) profit
Am i missing anything, or doing anything that isn't needed?
johnnyphive said:
Ok, so 1 last time (sorry)
1 - Downloaded the latest 8.0.0 factory image from google (this contains the bootloader, radio, and partitions (.zip).
2 - Get phone to fastboot and apply the above 3 new images
3- before rebooting, flash oreo4core (new, modified boot.img), TWRP recovery.img
4- reboot to recovery (TWRP) and apply the modified EX kernel
5 - reboot and (hopefully) profit
Am i missing anything, or doing anything that isn't needed?
Click to expand...
Click to collapse
<<Disclaimer: I don't use the 4 core kernel, so I don't know if it comes with installer script or someone has just modified the latest boot.img>> Unzip the "partitions" zip you refer to and extract those image files to the same folder as bootloader and modem. For example, you can keep TWRP recovery if you don't flash the recovery.img. That is how you preserve your custom recovery. So in other words you'll now have a folder (your ADB folder?) with 5 image files.... bootloader, radio, boot, system, and vendor all in one folder. <<Note: it is my understanding you just substitute the latest oreo4core file (should be boot.img?) If this is true, copy that file into your ADB folder and let it overwrite the stock boot.img. Stop. Copy over flash-all.bat, change the *.bat extension to *.txt and open in notepad. You will see (and can copy/paste) the fastboot commands to get you started with bootloader and radio. Then flash the last 3 (boot, system, vendor). At this point you can reboot into the OS. Since you substituted the oreo4core boot.img file for the stock boot.img there is no need to use TWRP to flash anything. That and since you skipped flashing the recovery.img, TWRP is still there.
v12xke said:
<<Disclaimer: I don't use the 4 core kernel, so I don't know if it comes with installer script or someone has just modified the latest boot.img>> Unzip the "partitions" zip you refer to and extract those image files to the same folder as bootloader and modem. For example, you can keep TWRP recovery if you don't flash the recovery.img. That is how you preserve your custom recovery. So in other words you'll now have a folder (your ADB folder?) with 5 image files.... bootloader, radio, boot, system, and vendor all in one folder. <<Note: it is my understanding you just substitute the latest oreo4core file (should be boot.img?) If this is true, copy that file into your ADB folder and let it overwrite the stock boot.img. Stop. Copy over flash-all.bat, change the *.bat extension to *.txt and open in notepad. You will see (and can copy/paste) the fastboot commands to get you started with bootloader and radio. Then flash the last 3 (boot, system, vendor). At this point you can reboot into the OS. Since you substituted the oreo4core boot.img file for the stock boot.img there is no need to use TWRP to flash anything. That and since you skipped flashing the recovery.img, TWRP is still there.
Click to expand...
Click to collapse
Thank for the help! Everything seems to be up and running. I know you said you don't use the "4 cores" (can only assume your either on a different phone or yours isn't affected by the BLOD), but do you know if i still need to apply the EX kernel update, or know of a way to tell if it's already been applied?
Thanks again for all the help. I was pretty much in the right direction, but being as how i'd been away from it for a while, i wanted some backup
johnnyphive said:
Thank for the help! Everything seems to be up and running. I know you said you don't use the "4 cores" (can only assume your either on a different phone or yours isn't affected by the BLOD), but do you know if i still need to apply the EX kernel update, or know of a way to tell if it's already been applied? Thanks again for all the help. I was pretty much in the right direction, but being as how i'd been away from it for a while, i wanted some backup
Click to expand...
Click to collapse
I don't think you can flash EX kernel from now on. I think you have to use a modded boot.img that will contain his kernel/ramdisk. This is my guess. You really should be getting your information in the dedicated thread where everyone is actually installing and using it. Google "oreo 4 core" and you will find the XDA thread is the first hit. Good luck. :good:
Hello All,
Is there an existing working TWRP for Nova 3i? I tried searching, I found one image that claims to be for Nova 3i from the site stupdroid . com.
I was able to flash it, but once I'm inside TWRP, the phone just restarts in maybe 5-10 seconds and just doesn't allow me to do anything.
So now I have an unlocked bootloader with no way to root
I hope someone can help.
P.S. I've asked Supersonic27543 but unfortunately, he/she doesn't have the copy anymore.
june.castillote said:
Hello All,
Is there an existing working TWRP for Nova 3i? I tried searching, I found one image that claims to be for Nova 3i from the site stupdroid . com.
I was able to flash it, but once I'm inside TWRP, the phone just restarts in maybe 5-10 seconds and just doesn't allow me to do anything.
So now I have an unlocked bootloader with no way to root
I hope someone can help.
P.S. I've asked Supersonic27543 but unfortunately, he/she doesn't have the copy anymore.
Click to expand...
Click to collapse
If you only want to root you can do that without TWRP. If you want to do that let me know in this thread.
how can i root the huawei nova 3i , modele ine-lx2, can i have help please
Supersonic27543 said:
If you only want to root you can do that without TWRP. If you want to do that let me know in this thread.
Click to expand...
Click to collapse
need to know how please
zenosteam said:
need to know how please
Click to expand...
Click to collapse
Has there been any further development on this?
I'm finding it quite hard to find a suitable TWRP image.
zenosteam said:
need to know how please
Click to expand...
Click to collapse
Sorry for the delay. Here's how, (Remember to unlock the bootloader before this!)
First, download the update.zip for this device (you can find it in Huawei Firmware Finder, remember to download the Full OTA)
Extract the update.zip, you'll see a file named update.app. Download "Huawei Update Extractor", and open the update.app with it.
Now you'll see a list of partitions. Extract the "ramdisk" partition (an . IMG file), and copy it to the Internal Storage of your device.
Download and Install Magisk Manager on your device. Open it, and press Install>Install>Patch Boot Image. Select the ramdisk image you copied to your Internal Storage. Magisk will save a patched image to /sdcard/Download/patched_boot.img.
Now install that image in Fastboot, by "fastboot flash ramdisk patched_boot.img".
Now your device should be rooted with Magisk. If for some reason your device doesn't boot, you can flash the stock ramdisk (before patching) by using the same command as above. (replace patched_boot. img with the image name) That'll cause loss of root.
Good luck!
june.castillote said:
Hello All,
Is there an existing working TWRP for Nova 3i? I tried searching, I found one image that claims to be for Nova 3i from the site stupdroid . com.
I was able to flash it, but once I'm inside TWRP, the phone just restarts in maybe 5-10 seconds and just doesn't allow me to do anything.
So now I have an unlocked bootloader with no way to root
I hope someone can help.
P.S. I've asked Supersonic27543 but unfortunately, he/she doesn't have the copy anymore.
Click to expand...
Click to collapse
How did you unlock bootloader?!?! which service???
I really need your help now..
---------- Post added at 07:44 AM ---------- Previous post was at 07:42 AM ----------
How did you unlock bootloadr?!?!? which service?
I really need your help now..
Supersonic27543 said:
Sorry for the delay. Here's how, (Remember to unlock the bootloader before this!)
First, download the update.zip for this device (you can find it in Huawei Firmware Finder, remember to download the Full OTA)
Extract the update.zip, you'll see a file named update.app. Download "Huawei Update Extractor", and open the update.app with it.
Now you'll see a list of partitions. Extract the "ramdisk" partition (an . IMG file), and copy it to the Internal Storage of your device.
Download and Install Magisk Manager on your device. Open it, and press Install>Install>Patch Boot Image. Select the ramdisk image you copied to your Internal Storage. Magisk will save a patched image to /sdcard/Download/patched_boot.img.
Now install that image in Fastboot, by "fastboot flash ramdisk patched_boot.img".
Now your device should be rooted with Magisk. If for some reason your device doesn't boot, you can flash the stock ramdisk (before patching) by using the same command as above. (replace patched_boot. img with the image name) That'll cause loss of root.
Good luck!
Click to expand...
Click to collapse
Has anyone tried this? Also, will this kill off OTA?
Currently running EMUI 9.0.1.130
I tried rooting my OP6T on Android 10, and was up half the night. Recovered from a hard brick twice, using the Qualcomm serial flash tool thing. I was trying to flash Majisk, and read that it had to be done via a custom recovery like TWRP. All the guides said that it to boot TWRP, then basically flash TWRP using itself so that it says. Fastboot kept saying "Remote Unknown Command" when using "fastboot boot" like all the guides said. Then someone told me to run "fastboot flash boot twrp.img". This caused the first hard brick. I guess because I wrote the recovery over the boot partition. I then found a post somewhere where someone said that Oneplus Devs removed the boot command from Fastboot for some reason. No idea why!! But no one else in the OP6T TWRP thread reported issues. Maybe they were all installing TWRP on an Android 9.x build that diden't have this issue? Eventually after recovering and flashing several layers on OTA updates through the local upgrade option, I was back on A10 OB2. But I still wanted root and hadn't got TWRP working yet. Then I found a random post buried in a random thread somewhere saying that custom recoveries on A10 are useless at this point period because TWRP can't flash the system partition, as it's read only. Not sure if this only applies to OP devices?
I am now back to where I started. I would still like twrp for backups, but since it's not cooperating, I try the alternative option for Masisk, involving the patched boot.img file. I download the patched the patched boot file in this thread. Flashed it with "fastboot flash boot boot.img", and got my 2nd hard brick. It would get stuck at the bootloader warning screen and no fastboot.
Now i've lost my data, 6+ hour of time, and no closer than I was before.
I am going to take a break now, cause I need an operational phone this week. Word of advice: If you're not a developer that knows exactly what they are doing, don't even attempt to get root on an Android 10 build!
You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.
I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.
It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.
Sh4d0wk1ng said:
It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.
Click to expand...
Click to collapse
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
Bhamilton0347 said:
I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.
Click to expand...
Click to collapse
How did you achieve this? Do you have to start with A9 with TWRP, and then somehow upgrade to A10 without overwriting it with stock recovery?
I found this guide, but step 2 does not make sense to me. How could you flash TWRP inside of the Masisk Manager app?
I imagine you still can't flash system with TWRP, but everything else works?
Thank you
roman gabriel said:
You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.
Click to expand...
Click to collapse
I think the issue was that I flashed to the wrong place. See above. Thank you.
I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.
Bhamilton0347 said:
I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.
Click to expand...
Click to collapse
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.
flyoffacliff said:
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.
Click to expand...
Click to collapse
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)
Bhamilton0347 said:
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)
Click to expand...
Click to collapse
Great. Thank you. I might wait for the next stable build though. It just came out on H2OS, so shouldn't be too long now.
Man it just worked smooth for me. I was already on OB2 and I followed this below link. Half way down, I realised it was for OP6 and not 6T. However I had proper twrp and I just followed the procedure.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213
EDIT: I faced problems with wifi connectivity. So I had rebooted to TWRP and reflashed OB2, TWRP and Magisk again to get it working. An issue with
"fastboot flash boot" command I guess.
flyoffacliff said:
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
I wasn't sure either but I know that the boot on the oneplus 6t android 10 it has two partitions. I just flashed it on boot_a and it works. I could attempt to install twrp on the other partition but I don't really needed it. good luck and let us know how it went.
Click to expand...
Click to collapse
I had a bit more luck with the adventure this time! Successfully flashed TWRP and Magisk, but then Emojis were completely broken at the OS level. Apparently this is caused by a partition issue, but not sure how this happened. I tried a script to fix it that someone posted and it did not work. So I took this as an opportunity to flash the latest ROM to fix it.
I went into TWRP, ran the full update ZIP, then the TWRP installer, then the Magisk installer (all without rebooting). Apparently it does not switch slots automatically when you run it from recovery instead of the "local update" option? TWRP was fine after the update, but Masisk was not, despite me flashing the ZIP. No idea why! But I switched back to the other slot that was still rooted, used Magisk Manager to flash it to inactive slot, and switched slot back to one with new OS. Success! Funny how different methods work/fail with different people. Thanks for the help everyone. I just noticed 10.3.1 is no longer posted on the OnePlus website download page, hope it didn't get pulled again!
EDIT: Does each slot just have its own system and cache partition? Everything else is like data and modem is combined, right?
https://forum.xda-developers.com/oneplus-6t/how-to/root-oneplus-6t-loosing-data-android-10-t4041865
follow this guide.. work 100%. Tested.
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
Hi,
Lost root access after updating my OnePlus 6T to Android 11 a few days back, hence decided to flash magisk_patched image that I had created around 2 months back. Phone didn't like it ofcourse and gave me a QualComm Crash Dump error.
After searching, managed to boot into bootloader, however wondering how do I now boot my phone - I have downloaded and installed latest recovery (3.5.2_9.0-fajita.img) and am able to boot into recovery as well as bootloader/ fastboot.
Have also downloaded the zip file for Android 11 stable version - OnePlus6TOxygen_34.J.60_OTA_0600_all_2108052232_8c516d0cce8795.zip
Question - What do I need to flash this? adb commands don't seem to be working, only fastboot commands seem to. Can I just "push" this zip file in fastboot or is that only for img files?
Any help woud be massively appreciated!
The update to 11 does not agree with Magisk which causes it to either fail to complete the update or to die at early boot depending on how bad things were messed up. You can reapply root once the update to 11 is finished though, so you can still have root.
In your case manually upgrading to 11, letting it finish the upgrade, and then installing Magisk again is your best bet, in which case you would either have to find something that understands the update format or manually extract the updated partitions from the payload, iirc
Extracted boot.img and used fastboot command : fastboot boot boot.img, but this doesn't seem to have worked as well. Just thinking aloud what else can be done?
Edit - It now tries to boot, but then seems to go into OnePlus Recovery (from the chinese characters displayed along with an option to choose English language)
sam_htc_touch said:
Have also downloaded the zip file for Android 11 stable version - OnePlus6TOxygen_34.J.60_OTA_0600_all_2108052232_8c516d0cce8795.zip
Question - What do I need to flash this? adb commands don't seem to be working, only fastboot commands seem to. Can I just "push" this zip file in fastboot or is that only for img files?
Click to expand...
Click to collapse
Masamune3210 said:
The update to 11 does not agree with Magisk which causes it to either fail to complete the update or to die at early boot depending on how bad things were messed up. You can reapply root once the update to 11 is finished though, so you can still have root.
In your case manually upgrading to 11, letting it finish the upgrade, and then installing Magisk again is your best bet, in which case you would either have to find something that understands the update format or manually extract the updated partitions from the payload, iirc
Click to expand...
Click to collapse
Hi, thanks for responding. I am not even concerned about root right now, just want my phone to boot up first Any suggestions on what can I try?
sam_htc_touch said:
Hi, thanks for responding. I am not even concerned about root right now, just want my phone to boot up first Any suggestions on what can I try?
Click to expand...
Click to collapse
For the benefit of others, all sorted finally y'day evening. Plenty of helpful tips in this thread
(Well I was able to boot into Android 11.1.1.1 - no root as yet, but I will perhaps look into that later, can't stand those annoying ads :-D )