After flashing magisk through TWRP- System reboot doesn't work and it directly goes to fastboot screen.
If i patch magisk in stock boot.img and flash it, no signal is found in both SIM Cards.
Android Version: 10.0
OOS: 10.0.2
Anyone can suggest me any solution?
aborshon said:
Anyone can suggest me any solution?
Click to expand...
Click to collapse
Yes, you flashed the wrong boot.img. That's why you get fastboot loop and no IMEI number. There are a couple of different phone versions out there, so please aware.
Are you sure you flashed the TWRP from the thread below and not the one from twrp.me? The version from twrp.me doesn't support Android 10.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3932943
Skickat från min GM1913 via Tapatalk
Related
So i flashed twrp on top of the stock rom and it just keeps bootlooping it not even getting to the samsung logo just the galaxy s6 splash screen
Heres a odin screenshot http://prntscr.com/h13jdx
Flash Magisk. It' s dm-verity
arkasha17 said:
Flash Magisk. It' s dm-verity
Click to expand...
Click to collapse
its need to flash magisk when you are on stock and flash twrp recovery?
what cause the dm-verity and what is that ?
paul222008 said:
its need to flash magisk when you are on stock and flash twrp recovery?
what cause the dm-verity and what is that ?
Click to expand...
Click to collapse
Just search. From twrp flash Magisk.
Inviato dal mio SM-G920F utilizzando Tapatalk
DON'T FLASH MAGISK v14.0
Like the others said, you need to flash magisk but don't flash magisk v14.0. I had huge issues with my SM-G920F with magisk v14.0 (I kept on losing root, modules didn't work correctly...) so I just went back to the last working version, which was v13.3. You can still install the same modules (by manually flashing them through apps like flashify), but you will never lose root (or at least I haven't). I lost root after 3 minutes of use on average on v14.0 and never lost it once on v13.3. However, the best way to do so it to run the uninstall script in twrp if you had magisk previously installed and then flash the older versions. The older versions can be found on the original magisk developer section right at the bottom where it says downloads.
Hello everyone,
if u want to install Magisk without flashing unoffical TWRP here are the steps. U still need to have unlocked Bootloader:
Seems only Global Version works ... Have a try:
1. Download Systemupdate via OTA
2. Copy it to Computer (located InternalStorage/downloaded_rom)
3. Extract "boot.img"
4. Copy it back to your Mix 2s
5. Install Magisk Manager 5.7.0
6. Open Magisk Manager and click install & install
7. select patch Boot-Image
8. Open "boot.img" with Filemanager
9. After Magisk is finished copy "patched_boot.img" (located InternalStorage/MagiskManager) to PC
10. Boot into Fastboot
11. Flash with "fastboot.exe flash boot patched_boot.img" without ""
12. Reboot Mi Mix 2s and u're rooted now
This Boot-Image is for 9.5.19.0 Global:
https://drive.google.com/file/d/1OPvkYbl5rHRMhb7naJPSEzkQSdAvg1VD/view?usp=sharing
This Boot-Image is for 9.5.20.0 Global:
https://drive.google.com/file/d/1r1Gva4DwVmzgyQB5AYK9mB2hwAXLGedK/view?usp=sharing
Try at your own Risk
MainderX said:
Hello everyone,
if u want to install Magisk without flashing unoffical TWRP here are the steps. U still need to have unlocked Bootloader:
1. Download Systemupdate via OTA
2. Copy it to Computer (located InternalStorage/downloaded_rom)
3. Extract "boot.img"
4. Copy it back to your Mix 2s
5. Install Magisk Manager 5.7.0
6. Open Magisk Manager and click install & install
7. select patch Boot-Image
8. Open "boot.img" with Filemanager
9. After Magisk is finished copy "patched_boot.img" (located InternalStorage/MagiskManager) to PC
10. Boot into Fastboot
11. Flash with "fastboot.exe flash boot patched_boot.img" without ""
12. Reboot Mi Mix 2s and u're rooted now
This Boot-Image is for 9.5.19.0 Global:
h**ps://drive.google.com/file/d/1OPvkYbl5rHRMhb7naJPSEzkQSdAvg1VD/view?usp=sharing
Click to expand...
Click to collapse
Nice workaround, didn't try yet, but i'm tempted to do this way....
So with thsi patched_boot image, it's just follow steps 10, 11 and 12
ruicc said:
Nice workaround, didn't try yet, but i'm tempted to do this way....
So with thsi patched_boot image, it's just follow steps 10, 11 and 12
Click to expand...
Click to collapse
Yes you just need to flash ist with Fastboot and install Magisk Manager
It's very helpful , thanks much .
MainderX said:
Hello everyone,
if u want to install Magisk without flashing unoffical TWRP here are the steps. U still need to have unlocked Bootloader:
1. Download Systemupdate via OTA
2. Copy it to Computer (located InternalStorage/downloaded_rom)
3. Extract "boot.img"
4. Copy it back to your Mix 2s
5. Install Magisk Manager 5.7.0
6. Open Magisk Manager and click install & install
7. select patch Boot-Image
8. Open "boot.img" with Filemanager
9. After Magisk is finished copy "patched_boot.img" (located InternalStorage/MagiskManager) to PC
10. Boot into Fastboot
11. Flash with "fastboot.exe flash boot patched_boot.img" without ""
12. Reboot Mi Mix 2s and u're rooted now
This Boot-Image is for 9.5.19.0 Global:
h**ps://drive.google.com/file/d/1OPvkYbl5rHRMhb7naJPSEzkQSdAvg1VD/view?usp=sharing
Click to expand...
Click to collapse
I'm try but it not work for me. my mi mix 2s not boot
heobanhki said:
I'm try but it not work for me. my mi mix 2s not boot
Click to expand...
Click to collapse
Did you use my patched_boot Image or created you're own?
MainderX said:
Did you use my patched_boot Image or created you're own?
Click to expand...
Click to collapse
I used both, use boot.img patched download from your link and patch my boot by magick.
Reflash boot.img (original) device is good boot.
Sorry for my English.
heobanhki said:
I used both, use boot.img patched download from your link and patch my boot by magick.
Reflash boot.img (original) device is good boot.
Sorry for my English.
Click to expand...
Click to collapse
Anyone else with this problem?
MainderX said:
Anyone else with this problem?
Click to expand...
Click to collapse
The model m1803d5xe version( known as 6GB ram black color version in China, have limited bands) probably has a limit on flashing root( magisk) in the Global rom. It will cause bootloop and currently have no solution. The m1803d5xa version( Global version) works well.
simonsmh said:
The model m1803d5xe version( known as 6GB ram black color version in China, have limited bands) probably has a limit on flashing root( magisk) in the Global rom. It will cause bootloop and currently have no solution. The m1803d5xa version( Global version) works well.
Click to expand...
Click to collapse
Could be possible. I got the m1803d5xa and it works well. Added it to my First Post
simonsmh said:
The model m1803d5xe version( known as 6GB ram black color version in China, have limited bands) probably has a limit on flashing root( magisk) in the Global rom. It will cause bootloop and currently have no solution. The m1803d5xa version( Global version) works well.
Click to expand...
Click to collapse
Oh yes yes, this maybe!!!! My model m1803d5xe
So if m1803d5xa works and m1803d5xe doesn't it's exactly the same problem as when flashing Magisk 16.4 with TWRP:
All devices with xe will bootloop. The only difference is, your variant without TWRP doesn't work on Chinese ROMs, only global. But flashing 16.4 on xa model and Chinese ROM works
underlines said:
So if m1803d5xa works and m1803d5xe doesn't it's exactly the same problem as when flashing Magisk 16.4 with TWRP:
All devices with xe will bootloop. The only difference is, your variant without TWRP doesn't work on Chinese ROMs, only global. But flashing 16.4 on xa model and Chinese ROM works
Click to expand...
Click to collapse
You can install Magisk on m1803d5xe with Chinese ROM. It works fine, but gpay don't works.
So basically magisk only works if you are running native rom for your phone model? What about 256gb version?
I am very confused about which method can be used on which model and ROM. I try to read again through the different threads.
I tried to come up with a matrix that shows all working and non working ways. Can anyone help me to correct and complete this please?
View attachment 4518265
underlines said:
I am very confused about which method can be used on which model and ROM. I try to read again through the different threads.
I tried to come up with a matrix that shows all working and non working ways. Can anyone help me to correct and complete this please?
Click to expand...
Click to collapse
I have a d5xa and it works with patched boot image. I'm on global rom
underlines said:
I am very confused about which method can be used on which model and ROM. I try to read again through the different threads.
I tried to come up with a matrix that shows all working and non working ways. Can anyone help me to correct and complete this please?
View attachment 4518265
Click to expand...
Click to collapse
I don't know if i can help, but i have the XE Model (chinese version).
I'm using the last Xiaomi.eu rom (8.5.17), it's rooted with Magisk 16,4 and 'ive installed TWRP from notsyncing. No problems so far.
If you need some screenshots, i'll post them.
XE model. Magisk work's fine if install via TWRP on developer, global, xiaomi.eu chinese rom.
Thanks for the tuto but it don't work, i'm in France with a global 9..5.4.0, the tuto was fine but when i did the fastboot, it wrote FAILED Flashing is not allowed in lock status. I unlock my phone but i have to wait the famous 360 hours. Do you think it's for that it don't work ?
Thanks again for the tuto
bazochien said:
Do you think it's for that it don't work ?
Click to expand...
Click to collapse
OP: "U still need to have unlocked Bootloader"
This is the answer to your question.
You need patience and wait the infamous 360 hours (so do I, sadly).
Can anyone upload a Magisk patched boot image for 10.0.1GM57AA? The model that I have is GM1900. When I try to patch it myself on Magisk, I get an error saying "process error"
Anyone able to help?
Heelixx said:
Anyone able to help?
Click to expand...
Click to collapse
Hi.
magisk-patched 4.14.117-perf+ with twrp: https://ufile.io/3ieksyfx
flash with fastboot flash boot 4.14.117-perf+.img
meltbanana said:
Hi.
magisk-patched 4.14.117-perf+ with twrp: https://ufile.io/3ieksyfx
flash with fastboot flash boot 4.14.117-perf+.img
Click to expand...
Click to collapse
Thanks a lot for uploading this! I managed to flash it and root my device but now the wifi isn't working. I cleared the cache with TWRP but that didn't resolve the issue. Flashing back the original boot image made the wifi work again.
Heelixx said:
Thanks a lot for uploading this! I managed to flash it and root my device but now the wifi isn't working. I cleared the cache with TWRP but that didn't resolve the issue. Flashing back the original boot image made the wifi work again.
Click to expand...
Click to collapse
ok, perhaps it depends on BA (EU) or AA (global) ROM version? however you can boot the rooted one, install a downloaded version of magisk20 via magisk manager to patch your own kernel directly.
meltbanana said:
ok, perhaps it depends on BA (EU) or AA (global) ROM version? however you can boot the rooted one, install a downloaded version of magisk20 via magisk manager to patch your own kernel directly.
Click to expand...
Click to collapse
I flashed the 4.14.117-perf+.img that you uploaded and then I booted in TWRP and flashed my original stock boot image. While still in TWRP, I flashed the zip of Magisk and then I rebooted. That got it working. So I'm rooted now. Thanks for sending me the image. I appreciate it!
@Heelixx
Can you explain to me how important a magisk boot patched is? Did you leave Pie for 10? What's the procedure?
lvints said:
@Heelixx
Can you explain to me how important a magisk boot patched is? Did you leave Pie for 10? What's the procedure?
Click to expand...
Click to collapse
I was rooted on 10.0 and then I upgraded to 10.0.1
There is a procedure for upgrading to 10.0.1 and still keeping root. I wasn't aware of this and after I got the update, I restarted my device and ended up without root access.
A Magisk patched boot image is important for getting your device rooted.
If you're asking for the procedure to root your device, then you can follow this link which explains it, https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
Hey guys,
got a OP6 for years. Stay on Stock OS with root. Never flashed any CustomRom or OS.
Bootet with fastboot boot twrp-version.img and flashed Magisk in twrp.
Works absolut fine until now. I installed the OTA and now i cant enter any twrp.
Information about my device:
Device: OnePlus6 A6003
OSS: 10.3.3
Android: 10
Build-Number: A6003_22_200414
USB-Debuggin: Enabled
OEM-Unlock: active
I tried all .img files from here:
eu.dl.twrp.me/enchilada/
and
twrp-3.2.3-x_blu_spark_v9.91_op.img
twrp-3.2.3-x_blu_spark_v9.86_op.img
No version working.
After flashing the 3.2.x versions i get a screen with
"qualcom crashdum mode
-------------"
With the newer 3.3x versions the screen just switch to "fastboot mode" and stay there forever.
How can i just boot into twrp with the new version? I wont twrp forever (flash). Just need to flash root after every OTA.
Thx for help!
Hilzerak said:
Just need to flash root after every OTA.
Click to expand...
Click to collapse
You could do that without TWRP. You just need to use Magisk's "Install to inactive slot" feature after installing OTA but before rebooting.
Hilzerak said:
Hey guys,
got a OP6 for years. Stay on Stock OS with root. Never flashed any CustomRom or OS.
Bootet with fastboot boot twrp-version.img and flashed Magisk in twrp.
Works absolut fine until now. I installed the OTA and now i cant enter any twrp.
Information about my device:
Device: OnePlus6 A6003
OSS: 10.3.3
Android: 10
Build-Number: A6003_22_200414
USB-Debuggin: Enabled
OEM-Unlock: active
I tried all .img files from here:
eu.dl.twrp.me/enchilada/
and
twrp-3.2.3-x_blu_spark_v9.91_op.img
twrp-3.2.3-x_blu_spark_v9.86_op.img
No version working.
After flashing the 3.2.x versions i get a screen with
"qualcom crashdum mode
-------------"
With the newer 3.3x versions the screen just switch to "fastboot mode" and stay there forever.
How can i just boot into twrp with the new version? I wont twrp forever (flash). Just need to flash root after every OTA.
Thx for help!
Click to expand...
Click to collapse
You should you twrp by
remewer said:
You could do that without TWRP. You just need to use Magisk's "Install to inactive slot" feature after installing OTA but before rebooting.
Click to expand...
Click to collapse
Try to in to recovery mode,if not,you try to flash twrp by mau.....
remewer said:
You could do that without TWRP. You just need to use Magisk's "Install to inactive slot" feature after installing OTA but before rebooting.
Click to expand...
Click to collapse
Thx for the info, helps for future.
But know i rebootet.
soihuvuontrang said:
You should you twrp by
Try to in to recovery mode,if not,you try to flash twrp by mau.....
Click to expand...
Click to collapse
Thx for reply but i dont know what excactly do you try to say me.
"You should you twrp by"? What should i try in recovery mode? And im looking forward for an solution without permanent flash, as i sayn above.
Hilzerak said:
Hey guys,
got a OP6 for years. Stay on Stock OS with root. Never flashed any CustomRom or OS.
Bootet with fastboot boot twrp-version.img and flashed Magisk in twrp.
Works absolut fine until now. I installed the OTA and now i cant enter any twrp.
Information about my device:
Device: OnePlus6 A6003
OSS: 10.3.3
Android: 10
Build-Number: A6003_22_200414
USB-Debuggin: Enabled
OEM-Unlock: active
I tried all .img files from here:
eu.dl.twrp.me/enchilada/
and
twrp-3.2.3-x_blu_spark_v9.91_op.img
twrp-3.2.3-x_blu_spark_v9.86_op.img
No version working.
After flashing the 3.2.x versions i get a screen with
"qualcom crashdum mode
-------------"
With the newer 3.3x versions the screen just switch to "fastboot mode" and stay there forever.
How can i just boot into twrp with the new version? I wont twrp forever (flash). Just need to flash root after every OTA.
Thx for help!
Click to expand...
Click to collapse
The version you tried to boot is not for android 10.
Versions for android 10 are blu_spark 9.108 and 9.109. Unfortunately, i think @eng.stk stopped providing img, but you can download lastest @mauronofrio TWRP and then flash @mauronofrio or blu_spark TWRP
Hilzerak said:
Thx for the info, helps for future.
But know i rebootet.
Thx for reply but i dont know what excactly do you try to say me.
"You should you twrp by"? What should i try in recovery mode? And im looking forward for an solution without permanent flash, as i sayn above.
Click to expand...
Click to collapse
After fashing twrp.img you boot into recovery and flash the file twrp.zip(the same series and name with file twrp.img)then reboot recovery.
Hello everyone.
I was wondering if anyone has found a work around to get a custom recovery to work on the oos 11 beta one for op7p gm1917.
I've tried msm tool and have working TWRP untill I install ops 11.
Once I install the beta 1 and TWRP booting to recovery is stuck in a flashing TWRP logo. Only way to recover from this is to flash stock boot image.
I do have root as I patched the stock boot.img with magisk 8.0.4 then flashed the boot image with fastboot.
If anyone could help me get this TWRP up and running I would definitely appreciate it.
Thank you...
mrhodes19904 said:
If anyone could help me get this TWRP up and running I would definitely appreciate it.
Thank you...
Click to expand...
Click to collapse
TWRP is not available for Android 11 yet, so you will have to wait.
nabril15 said:
TWRP is not available for Android 11 yet, so you will have to wait.
Click to expand...
Click to collapse
At least I have root that's all that matters
pcould you please put the modified boot here?
RicoMartins said:
pcould you please put the modified boot here?
Click to expand...
Click to collapse
magisk.img
Shared with Dropbox
www.dropbox.com
Thanks, buddy.
You guys can flash a zip of twrp like orangefox dual boot. Right after the ota in twrp. With a pen drive to get twrp in OS11. No need to actually use a dualboot its just a really nice build I use it.
Anyone tried this method? https://www.droidwin.com/update-oneplus-to-android-11-oxygenos-11-via-twrp-without-losing-root/