Related
Hi I this is my first post in xda so pardon me for any mistake.
I am facing some issues while rooting my phone with magisk
I have Micromax q372 unite 3 (2015) running android lollipop v5.0 and I am trying to root with magisk v6.0.
So first I tried to flash magisk zip directly with twrp 3.0.2-0 recovery but it showed an error- unable to unpack boot.img
So I patched boot.img file using magisk manager and then tried flashing it with twrp and my phone went into boot-loop (i was unable to use adb method)
so I renamed patched_boot.img to boot.img and replaced this with an original boot.img file in my firmware and flashed the whole firmware using sp flash tool
and I got into boot-loop again. (I know how to solve boot loop.)
So how to root with magisk now.
- there is no new version of twrp available for my device.
- adb method not working.
- flashing original boot image also not working.
Please help me.
Hi there,
I've been rooting phones since Android 2, but lately it has been quite a challenge.
What I did so far:
Unpack new Xiaomi MI A2 (jasmine) device
Enabled Developer, USB debugging, OEM unlock in Android settings
Code:
fastboot oem unlock
Code:
fastboot flash boot_b TWRP-3.2.3-jasmine-20180804.img
TWRP ran fine. However, started with boot_a again.
OTA updated (about 6 times) to the newest version (Android 10, QKQ1.190910.002 V11.0.12.0.QDIMIXM)
Code:
fastboot flash boot_b twrp-3.4.0-0-jasmine_sprout.img
TWRP started only to the splash screen (showing "teamwin" and "Recovery Project 3.4.0-0"). Why is TWRP not starting properly?
Downloaded the stock fastboot image V11.0.12.0.QDIMIXM from https ://xiaomifirmwareupdater.com/archive/miui/jasmine/ and flash the stock boot.img via
Code:
fastboot flash boot_b jasmine_global_images_V11.0.12.0.QDIMIXM_10.0/images/boot.img
(my goal is to later patch it with Magisk and then install the patched version). However, the stock boot.img just hangs forever on the androidone screen. Why is the stock boot.img not starting properly?
I haven't used the Mi Unlock app and I didn't do an "fastboot flashing unlock_critical" yet. Is this necessary? What do I have to do to make the boot images work?
floydsen said:
Hi there,
I've been rooting phones since Android 2, but lately it has been quite a challenge.
What I did so far:
Unpack new Xiaomi MI A2 (jasmine) device
Enabled Developer, USB debugging, OEM unlock in Android settings
TWRP ran fine. However, started with boot_a again.
OTA updated (about 6 times) to the newest version (Android 10, QKQ1.190910.002 V11.0.12.0.QDIMIXM)
TWRP started only to the splash screen (showing "teamwin" and "Recovery Project 3.4.0-0"). Why is TWRP not starting properly?
Downloaded the stock fastboot image V11.0.12.0.QDIMIXM from https ://xiaomifirmwareupdater.com/archive/miui/jasmine/ and flash the stock boot.img via (my goal is to later patch it with Magisk and then install the patched version). However, the stock boot.img just hangs forever on the androidone screen. Why is the stock boot.img not starting properly?
I haven't used the Mi Unlock app and I didn't do an "fastboot flashing unlock_critical" yet. Is this necessary? What do I have to do to make the boot images work?
Click to expand...
Click to collapse
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off
KevMetal said:
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off
Click to expand...
Click to collapse
Ok. So I'm back to Stock image jasmine_global_images_V11.0.12.0.QDIMIXM_10.0 by executing "flash_all.sh". You are saying I should "simply boot". You mean:
Code:
fastboot boot TWRP-3.4.0-0-jasmine_sprout-for_V11.0.12.0.img
right? That doesn't work, it won't boot. How do I overcome secure boot and force encryption?
floydsen said:
Ok. So I'm back to Stock image jasmine_global_images_V11.0.12.0.QDIMIXM_10.0 by executing "flash_all.sh". You are saying I should "simply boot". You mean:
right? That doesn't work, it won't boot. How do I overcome secure boot and force encryption?
Click to expand...
Click to collapse
yes im saying that but post a pic of the error ...why or how doesn't it boot ..
if it is the official twrp just dump it and look for the unofficial Russian one or one modified by Nebrassy or use Orange fox and or Pitch black ..official is broken last time i checked
also the name of that looks like one hell of a job ..shorten it to
recovery.img or twrp.img
fastboot boot recovery.img
but first run
fastboot getvar all
& also run fastboot flashing unlock_critical
but most importantly get another recovery
& i don't want to insult your intelligence but after flashing stock did you check to make sure bootloader was still unlocked and that dev settings was activated and that adb was toggled to on and that you authorised adb again
basicall after stock boot device and do the above ..plug in usb ..toggle adb ..authorise ..run adb devices ..if you see your device ..adb reboot bootloader ..fastboot devices ..see your device ..fastboot getvar all ..see bootloader is unlocked ..fastboot flashing unlock_critical if not done yet ...make sure to do ALL the above again after data gets wiped.....put twrp in adb folder ( MUST BE UNOFFICIAL RUSSIAN OR MODUFIED BY NEBRASSY ..rename to revovery.img ...fastboot boot recovery.img .. use file manager to put magisk.zip on internal then flash ..then reboot to rooted phone with stock recovery ...
Sent from my wayne using XDA Labs
KevMetal said:
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off
Click to expand...
Click to collapse
KevMetal said:
yes im saying that but post a pic of the error ...why or how doesn't it boot ..
if it is the official twrp just dump it and look for the unofficial Russian one or one modified by Nebrassy or use Orange fox and or Pitch black ..official is broken last time i checked
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Of course it is the official one. OMFG twrp-3.4.0-0-jasmine_sprout.img is broken (freezes on the TWRP splash screen), but version 3.3.1 seems to work. That's a relief, so I will try to flash magisk now. Although, I think I will need to do the decryption thing for jasmine first, but I guess I'll follow https://www.the***********.com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/ mostly
floydsen said:
Of course it is the official one. OMFG twrp-3.4.0-0-jasmine_sprout.img is broken (freezes on the TWRP splash screen), but version 3.3.1 seems to work. That's a relief, so I will try to flash magisk now. Although, I think I will need to do the decryption thing for jasmine first, but I guess I'll follow https://www.the***********.com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/ mostly
Click to expand...
Click to collapse
jajaja well now you know ...be careful ...some "official" roms are also more buggy than unofficial ones for Jasmine/Wayne..
LOS is an example ..so be forewarned .. if you like android 1 i guess stock rooted is a smart option to keep updates and keep device certified for google stuffs . .
alternativeky go FULL custom rom because stock and custom recovery is just a pain and not worth the hassle on an A/B treble device flashable by fastboot ..just boot the recovery when if ever needed
fyi ..you can flash magisk and it will boot ...if you don't try changing the recovery ..so you can have stock rooted with magisk without rcustom recovery...* recommended by me if you only wamt stock with root
Sent from my wayne using XDA Labs
All good now, thanks for your help! I just flashed Magisk (and also TWRP) and everything works nicely! I will need to get some experience, but I'll keep in mind that I maybe want to get rid of the TWRP recovery. Finally security testing is fun again. Thx!
OnePlus 7T Pro HD01AA Global 11 Open Beta 1
Magisk Patched Boot Image v21.4 Patched Manager v8.0.7
https://www.androidfilehost.com/?fid=17248734326145719979
May need to install Magisk Manager manually
Stock Boot Image
https://www.androidfilehost.com/?fid=17248734326145719978
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=17248734326145719976
Stock Recovery Image
https://www.androidfilehost.com/?fid=17248734326145719977
Combined Folder
https://www.androidfilehost.com/?w=files&flid=322189
OnePlus 7T Pro HD01AA India 11 Open Beta 1
Magisk Patched Boot Image v21.4 Patched Manager v8.0.7
https://www.androidfilehost.com/?fid=17248734326145719991
May need to install Magisk Manager manually
Stock Boot Image
https://www.androidfilehost.com/?fid=17248734326145719989
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=17248734326145719993
Stock Recovery Image
https://androidfilehost.com/?fid=17248734326145719992
Combined Folder
https://www.androidfilehost.com/?w=files&flid=322190
OnePlus 7T Pro HD01AA Global 10.0.13
Magisk Patched Boot Image
https://www.androidfilehost.com/?fid=10763459528675591747
May need to install Magisk Manager manually
Full ZIP OxygenOS HD01AA 10.0.13
https://www.androidfilehost.com/?fid=10763459528675591755
Stock Boot Image
https://www.androidfilehost.com/?fid=10763459528675591746
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=10763459528675591748
Stock Recovery Image
https://www.androidfilehost.com/?fid=10763459528675591745
Combined Folders
https://www.androidfilehost.com/?w=files&flid=320328
OnePlus 7T Pro HD01AA India 10.3.7
Magisk Patched Boot Image
https://www.androidfilehost.com/?fid=10763459528675592073
Full ZIP OxygenOS HD01AA 10.3.7
https://www.androidfilehost.com/?fid=10763459528675592086
Stock Boot Image
https://www.androidfilehost.com/?fid=10763459528675592074
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=10763459528675592075
Stock Recovery Image
https://www.androidfilehost.com/?fid=10763459528675592076
Combined Folders
https://www.androidfilehost.com/?w=files&flid=320346
Usage (Unlocked Bootloader)
adb devices (give permission on device)
adb reboot fastboot
fastboot devices (to confirm that device is being detected)
fastboot flash boot path/to/patched_boot.img or fastboot flash recovery path/to/patched_recovery.img
fastboot reboot
Wifi issue?
Thanks for this! Forgive me if this is a stupid question, but last time I tried to root my OP7T, months ago, my wifi broke and I had to hard reboot. Is that still a possibility with this?
isellmidgets said:
Thanks for this! Forgive me if this is a stupid question, but last time I tried to root my OP7T, months ago, my wifi broke and I had to hard reboot. Is that still a possibility with this?
Click to expand...
Click to collapse
Make sure you flash the right boot for your model number.
Settings>About phone>Build number should end HD01BA or HD01AA so make sure it's the right one.
If you want to test that your Wi-Fi works with one of the boot images.
Instead of 'fastboot flash boot patched_file_name.img' do 'fastboot boot patched_file_name.img'
I have the same problem with wifi and network issue, only have data network 4g.
I'm flashing the right boot for my model, also i dump the OTA zip, dumpped the boot.img tried patching on magisk and flash and i got the same wifi and mobile network issue.
Mu Model is HD01BA.
Any one have the same issue?
Thanks
=== EDIT ===
After this i tried flash the original boot.img and the problem doesn't have solved, i need reflash all the system again
isellmidgets said:
Thanks for this! Forgive me if this is a stupid question, but last time I tried to root my OP7T, months ago, my wifi broke and I had to hard reboot. Is that still a possibility with this?
Click to expand...
Click to collapse
I unlocked my OP 7t pro's bootloader, and every time there is an update I download the stuff mirrored by digidude512 ... I grab the magisk patched boot and the updated system pack.
I go to updates, update manually with having the update pack in the root of the storage.
When the update is done, I do not restart using the update reboot button - I use the boot to bootloader option at the power button menu (which can be enabled at the dev settings).
Then going to fastboot directly I flash the patched boot image using fastboot on windows cmd: fastboot flash boot boot_blabla.img --slot all
Reboot, go to magisk manager, update magisk using recommended direct install. Update magisk manager. Done.
Never had any problem (no wifi f*ery, nothing) and there is no need for TWRP at all. Open bootloader, magisk root and modules, adaway, stock ROM. Decent and clean.
Thanks a lot @digidude512 once again for this. Pretty convenient for others this way.
[zozi] said:
I have the same problem with wifi and network issue, only have data network 4g.
I'm flashing the right boot for my model, also i dump the OTA zip, dumpped the boot.img tried patching on magisk and flash and i got the same wifi and mobile network issue.
Mu Model is HD01BA.
Any one have the same issue?
Thanks
=== EDIT ===
After this i tried flash the original boot.img and the problem doesn't have solved, i need reflash all the system again
Click to expand...
Click to collapse
If you're rooting for the first time, use fastboot boot patched_boot.img and perform a direct install from within Magisk Manager to avoid potential headaches.
If you are doing an OTA update and want to retain root, you should not be fastboot flashing anything (you're not following the right guide).
[zozi] said:
I have the same problem with wifi and network issue, only have data network 4g.
I'm flashing the right boot for my model, also i dump the OTA zip, dumpped the boot.img tried patching on magisk and flash and i got the same wifi and mobile network issue.
Mu Model is HD01BA.
Any one have the same issue?
Thanks
=== EDIT ===
After this i tried flash the original boot.img and the problem doesn't have solved, i need reflash all the system again
Click to expand...
Click to collapse
Sorry for the late reply, I couldn't sign in while XDA was changing format.
For HD01BA you want this thread.
[OOS] [11] Open_Beta_2_HD01BA [EU] [Stock/Patched boot.img] [Stock/ADB Recovery] [Full ZIP] [OOS 10.0.13]
@digidude512 Every Update needs a new Thread... interesting. Stop this sh!t.
forum.xda-developers.com
can someone please provide me with batched boot image for OnePlus 7T (India), i extracted the boot.img by using payload dumper then i batched it using magisk 8.0.5 but unfortunately when i flash it using fastboot it loops at the OnePlus animation logo
Thread updated with files for OxygenOS 11 Open Beta 1 including both Global and India Variants.
hello guys,
i want to root my redmi 9 with magisk. i tried to use the "patched boot.img method", but everytime i land in a bootloop.
im on miui global 12.5.3 stable, android 11. bootloader unlocked!
i took that magisk version: https://github.com/topjohnwu/Magisk/releases/tag/v23.0 (v23.0 - as apk)
than i was on that page: https://c.mi.com/oc/miuidownload/detail?device=1900381
on that page i took on the left "redmi 9 global" - which calls:
Code:
Stable ROM
Author: MIUI Official Team
Version: V12.5.3.0.RJCMIXM (MIUI11)
Size: 2.2G
i extracted the archive and copied magisk.apk and boot.img to my download-folder on my smartphone. patched the boot.img with magisk. than copied the patched boot.img to my pc.
after that i bootet the phone into fastboot mode. than i flashed the patched boot.img with fastboot flash boot patchedboot.img - used than fastboot reboot and than im in the bootloop.
can someone tell me, what i am doing wrong?
(ps: when i flash the unpatched boot.img i get no bootloop and my phone is starting again - but of course with no root )
thanks
taker-`
If I understood correctly, as well as you don't mention about that, you didn't deactivate the AVB mechanism by flashing the stock vbmeta image with the command fastboot --disable-verity --disable-verification flash vbmeta [your vbmeta.img file], which is documented that if Magisk is installed without that procedure, the device is bootlooping (see this guide).
oh, i see. yes, i didnt use that command. but now i got it working. i read that twrp isnt really compatible with the redmi9 and i need another recovery.
i used that now: https://sourceforge.net/projects/shrp/
vbmeta from post #4: https://forum.xda-developers.com/t/dont-use-twrp-on-redmi-9-use-shrp.4334123/
than i did that:
fastboot flash recovery *.img
fastboot --disable-verity --disable-verification flash vbmeta *.img
fastboot reboot recovery
from there i installed integrated magisk v23.0
phone reboot...got root.
I have read that there are issues with TWRP and Magisk (as far as I know, even its developer mentions that). Although I never got SHRP to work properly on my device and I always get bootloop issues with that. Do you know if it's because of the version I run? I currently run MIUI 11.0.2.0, which I think it's the device's original version.
uh im sorry. im also new to the shrp recovery. i had only used twrp so far.
did you try to flash this version i linked? if its not working you can fast flashback ur twrp. maybe just give it a try?
taker-` said:
uh im sorry. im also new to the shrp recovery. i had only used twrp so far.
did you try to flash this version i linked? if its not working you can fast flashback ur twrp. maybe just give it a try?
Click to expand...
Click to collapse
I don't think I have tried that. I think at the worst case, because I run MIUI I'll just roll back to it's original recovery image. I'm just asking because I don't see mentions of software versions.
what smartphone do you own?
When getting a custom ROM and wanting to root it with Magisk, should I patch and flash the boot.img of the specific ROM or the boot.img of the factory FW
hazoky01 said:
When getting a custom ROM and wanting to root it with Magisk, should I patch and flash the boot.img of the specific ROM or the boot.img of the factory FW
Click to expand...
Click to collapse
Flash TWRP or orange fox and then Magisk zip in the recovery
That's it
But of course the bootloader has to be unlocked
The boot img of the current ROM you're using like example boot img of Pixel Experience if you're using that. Usually the boot img is inside the ROM zip when you installed it. But this method is for devices without custom recovery. Of course it will work but I suggest to follow what Laptapper suggested to flash a custom recovery (orange fox r12.1_2 or twrp 3.7.0) and just flash magisk.zip.