I've tried everything and I just get a bootloop. If anyone has the steps that worked for them I'd love to have my root back. Thanks community!
What exactly have you tried? We can't give you a solution for problems we don't know...
Had the same problem on 118-15-11-2, so I flashed 55-37-7 instead and it rooted fine on Magisk 20.1.
Will 55-37-7 work with Tmobile Moto G6? Haven't tried flashing that one yet.
fireman644 said:
Will 55-37-7 work with Tmobile Moto G6? Haven't tried flashing that one yet.
Click to expand...
Click to collapse
I have a Moto G6 (Ali) xt1925-6 and yes currently on retail ppss29.55-37-7 which has October patch. I've not had any problems flashing the 118 or the 55 retail builds as long as they have same or newer security patches.
Skippy12359 said:
Had the same problem on 118-15-11-2, so I flashed 55-37-7 instead and it rooted fine on Magisk 20.1.
Click to expand...
Click to collapse
Did you install Magisk by patching the recovery.img (recovery mode)? Normal installation through boot.img causes a bootloop, afaik.
https://forum.xda-developers.com/moto-g6/how-to/magisk-twrp-moto-g6-t4006983
WoKoschekk said:
Did you install Magisk by patching the recovery.img (recovery mode)? Normal installation through boot.img causes a bootloop, afaik.
https://forum.xda-developers.com/moto-g6/how-to/magisk-twrp-moto-g6-t4006983
Click to expand...
Click to collapse
After flashing and setting up 55-37-7 stock pie, I booted to twrp and flashed magisk 20.1. It boot fine and then installed magisk manager apk and had root.
Skippy12359 said:
After flashing and setting up 55-37-7 stock pie, I booted to twrp and flashed magisk 20.1. It boot fine and then installed magisk manager apk and had root.
Click to expand...
Click to collapse
Alternate route - I flashed to ALI_RETAIL_9.0_PPS29.118-11-1 (back to July Pie) and used magisk 19.3, DM Verity Disabler from August.
Seems to work fine, but wants to keep updating the system with latest version of Pie from December.
I did try to flash ALI_RETAIL_9.0_PPS29.55-24, but that killed my T-Mobile connection (wouldn't turn on the radio and/or recognize the SIM.)
Can anyone tell us what the difference between 55 and 118 variants are?
PS. My phone is the U.S. G6.
oldguy51 said:
Alternate route - I flashed to ALI_RETAIL_9.0_PPS29.118-11-1 (back to July Pie) and used magisk 19.3, DM Verity Disabler from August.
Seems to work fine, but wants to keep updating the system with latest version of Pie from December.
I did try to flash ALI_RETAIL_9.0_PPS29.55-24, but that killed my T-Mobile connection (wouldn't turn on the radio and/or recognize the SIM.)
Can anyone tell us what the difference between 55 and 118 variants are?
PS. My phone is the U.S. G6.
Click to expand...
Click to collapse
The big question is which variant of the Moto G6 do you have? For example I have XT1925-6 which is the US Unlocked variant. You need to flash the correct firmware for your variant.
https://mirrors.lolinet.com/firmware/moto/ali/official/
Go here once you know your variant to get the exact right firmware. Who is your provider?
I have the XT-1925-6 Tmobile US unlocked bootloader. I had root with PPS29-118-11-1. Now that I have updated to -2 I have lost root and get a bootloop everytime I try and flash Magisk or DM-verity. Could you help? Thanks.
fireman644 said:
I have the XT-1925-6 Tmobile US unlocked bootloader. I had root with PPS29-118-11-1. Now that I have updated to -2 I have lost root and get a bootloop everytime I try and flash Magisk or DM-verity. Could you help? Thanks.
Click to expand...
Click to collapse
Maybe you should try try "retail" firmware. If you havr the xt-1925-6 variant, it will work. US unlocked will accept it. The version is ALI_RETAIL_9.0_PPS29.55-37-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
It worked for many of us. You can use RSDLite, as long as you are connected by a USB 2 port. Do a backup first, because your internal storage will be deleted.
If you truly have an xt-1925-6, it will work
Yeah I tried flashing the firmware but it wouldn't take. Gave me errors at the beginning and wouldn't flash. I'll try again with a USB 2 port and RSDlite. I was using manual commands.
theseeker2654 said:
The big question is which variant of the Moto G6 do you have? For example I have XT1925-6 which is the US Unlocked variant. You need to flash the correct firmware for your variant.
Go here once you know your variant to get the exact right firmware. Who is your provider?
Click to expand...
Click to collapse
I'm connecting to T-Mobile, but I can't remember if the phone is used or a New in Box from Amazon at some point. It is a GSM version.
Here's a pair of questions that might help us noobs:
1. How do you tell which version of the moto g6 phone you have? (if there's a link to another discussion that gives this info, awesome.)
2. Is there a map of the hardware types to appropriate retail images? When I looked in the RETAIL directory for the link above, there appears to be two versions for 9.0 - 29.55 and 29.118 - with my phone functioning in the .118 stream through trial and error.
Thanks!
-og
OK I have used the ALI_RETAIL_9.0_PPS29.55-37-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and the device will boot stock. Wiped it and followed the usual steps to root it. Once I apply Magisk or dm_verity disabler there is a bootloop. Could anyone please provide the steps needed to root and prevent the bootloop. I have tried everything that I can think of. Using Magisk 20.2 and dm_verity 12/27/19. Should I try another version? Thank you.
fireman644 said:
OK I have used the ALI_RETAIL_9.0_PPS29.55-37-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and the device will boot stock. Wiped it and followed the usual steps to root it. Once I apply Magisk or dm_verity disabler there is a bootloop. Could anyone please provide the steps needed to root and prevent the bootloop. I have tried everything that I can think of. Using Magisk 20.2 and dm_verity 12/27/19. Should I try another version? Thank you.
Click to expand...
Click to collapse
According to posts in this thread, one says don't use dm_verity zip and another says edit fstab.qcom. I haven't tired either yet as I'm still on Aug patch with updates "disabled".
Here is how I eventually rooted PPSS29.118-15-11-2:
https://forum.xda-developers.com/showpost.php?p=81229155&postcount=381
I was never able to boot after trying to flash TWRP, so I just didn't bother flashing TWRP. Booting it manually was enough.
I only flashed Magisk-19.4 from TWRP, nothing else. I have no idea if directly flashing a newer Magisk might have worked.
I'm now updated to Magisk-20.3 and everything works.
fireman644 said:
OK I have used the ALI_RETAIL_9.0_PPS29.55-37-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and the device will boot stock. Wiped it and followed the usual steps to root it. Once I apply Magisk or dm_verity disabler there is a bootloop. Could anyone please provide the steps needed to root and prevent the bootloop. I have tried everything that I can think of. Using Magisk 20.2 and dm_verity 12/27/19. Should I try another version? Thank you.
Click to expand...
Click to collapse
For the installation of Magisk I used the .zip v19.3 because the latest (v20.3) caused a bootloop.
Here are the steps that worked for me:
1.) Boot into TWRP and copy the fstab.qcom from /vendor/etc
2.) Edit fstab.qcom like this:
line 9: forceencrypt=/dev/block/bootdevice/by-name/metadata => encryptable=/dev/block/bootdevice/by-name/metadata
This will remove forceencryption and will only work if you format /data!! But you should do this anyway before flashing the magisk.zip
3.) Replace the fstab.qcom in/vendor/etc with the edited one. Be sure the permissions are 0644 (rw-r--r--). To change it open the terminal command and type
Code:
chmod 0644 /vendor/etc/fstab.qcom
4.) Flash the magisk.zip to install Magisk
During the installation process Magisk will remove dm-verity
5.) Reboot and update Magisk Manager + Magisk to v20.3
Related
Okay so this is my first post so don't crucify me but I have a Moto e5 Plus (xt1924-8) on Boost Mobile. I currently have the stock rom on my phone as that has working data. Since this device launched with treble support, I figured I'd try flashing some GSIs. The one I had settled on was Resurrection Remix as it had the most working features. In the thread for the GSI https://forum.xda-developers.com/moto-e5/development/gsi-resurrection-remix-o-6-1-0-t3843928 it says that you should be able to flash on top of the stock rom. However, when I do that, everything works fine except for mobile data. I tried reflashing and editing APN settings all to no avail. It's not the modem firmware as I reflashed that as well. Can anyone tell me what I could try to get mobile data working in RR on the xt1924-8?
Also, I tried to get lineageOS as that might've been needed to get RIL working but I was unable to find one that works with the -8 variant. If someone could link to an image that would be nice.
TinTrapezoid said:
Okay so this is my first post so don't crucify me but I have a Moto e5 Plus (xt1924-8) on Boost Mobile. I currently have the stock rom on my phone as that has working data. Since this device launched with treble support, I figured I'd try flashing some GSIs. The one I had settled on was Resurrection Remix as it had the most working features. In the thread for the GSI https://forum.xda-developers.com/moto-e5/development/gsi-resurrection-remix-o-6-1-0-t3843928 it says that you should be able to flash on top of the stock rom. However, when I do that, everything works fine except for mobile data. I tried reflashing and editing APN settings all to no avail. It's not the modem firmware as I reflashed that as well. Can anyone tell me what I could try to get mobile data working in RR on the xt1924-8?
Click to expand...
Click to collapse
Hey, do you have the method available for how you got root for the boost mobile variant?
shezzy83 said:
Hey, do you have the method available for how you got root for the boost mobile variant?
Click to expand...
Click to collapse
I used the guide for the e5 play. Flash stock, erase data, cache and DDR. Boot, wait for encryption
Then boot twrp don't flash. Flash universal dm verity and encryption remover and then flash magisk 17.1.
That's how I recall it. Probably wrong. Check the thread for the e5 play. Use the difficult route. Sorry :/
shezzy83 said:
Hey, do you have the method available for how you got root for the boost mobile variant?
Click to expand...
Click to collapse
The method that worked for me and my 2 Boost E5 Pluses was to:
Unlock boot loader through Motorola website
Reboot phone into bootloader
Fastboot boot into twrp (the boot image "twrp_james" worked for me)
While in twrp, do a backup onto microsd card.
Boot into android and install Magisk manager
Use Magisk to patch your boot.emmc file from your twrp backup
Find the patched-boot file that it output and copy to your pc
Reboot phone into bootloader
Flash the patched-boot file using fastboot flash boot (file name)
Reboot and enjoy ROOT!!!
Just fyi, I didn't do any dm-noverity kernel flashing or flashing twrp to recovery.
TinTrapezoid said:
Also, I tried to get lineageOS as that might've been needed to get RIL working but I was unable to find one that works with the -8 variant. If someone could link to an image that would be nice.
Click to expand...
Click to collapse
did you find a solution? im in the same boat
JimmyJurner said:
did you find a solution? im in the same boat
Click to expand...
Click to collapse
Naw sorry dude. All the GSI's for lineage bootlooped or didn't have data. Just gave up and reflashed stock with magisk.
Try manually inputting stock apn in gsi
TinTrapezoid said:
Naw sorry dude. All the GSI's for lineage bootlooped or didn't have data. Just gave up and reflashed stock with magisk.
Click to expand...
Click to collapse
I'm assuming there's still no fix right I'm on lineage 15. and have no service for sprint same model
Anyone know a secure procedure and a custom recovery compatible?
marte66 said:
Anyone know a secure procedure and a custom recovery compatible?
Click to expand...
Click to collapse
We don't have TWRP yet, it's not officially out yet for any G7 models and I don't know when ours may be.
Root your G7 with Magisk
I noticed this method without using TWRP on the G7 XDA forum but haven't tried it, and you must unlock the bootloader first. Apparently it's working for a few G7 users so it should on G7+ too if the correct boot.img is used (for G7+/'lake' not G7/'river') according to your release channel. You still wouldn't have a custom recovery but could install Adaway, Magisk modules, and gain full access to the file system.
EDIT:
If anyone tries this method please report back, and don't forget to unlock the bootloader first and use the Lake/G7 Plus firmware from lolinet. No one has reported it not working but only a handful have used it afaik. I'm on RETLA w/Dec security patch so would rather wait until OTA updated and then I might try it because it would give me everything I need from root except nandroid backups and installing ROMs (of which there aren't any yet). I have my unlock code ready to go and have the needed boot.img from my channel-specific firmware but remain fully stock.
The instructions aren't that detailed but I found you can install Magisk Manager as an apk, open it and when you tap on Install Magisk 18.1 (which isn't installed yet) it also gives the option to "patch boot.img" (which I didn't select but assume it'll let you navigate to where you put the one from firmware & not alter the currently booted partition). When finished you put/copy that altered one on your pc (preferably in your Fastboot/ABD folder) and fastboot flash it, then reboot and you should be rooted in Magisk.
EDIT #2:
Tried it, it works!
I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?
washoq said:
I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?
Click to expand...
Click to collapse
If someone on your channel could capture their PPW29.98-66 OTA before installing, otherwise I think you'd have to wait until it appears on lolinet or Motorola's site, or we get TWRP. I realized I'd be in the same boat because my current firmware was also the only one so far on lolinet, so I decided to go ahead because I'd only get January's security patch (on Dec now) and still be a few months behind anyway.
Having done it I can say that Magisk Manager does let you navigate to the stock boot.img file after offering to patch it, then it goes through the same familiar steps as when installing in TWRP, and at the end tells you it's in your Download folder with the name patched_boot.img. After transferring to my pc I renamed it to boot.img and just manually typed in the fastboot flash boot command.
I also want to repeat that although rooted there's still no custom recovery/TWRP so you can't do nandroid backups, and now when my channel's OTA comes along I'll have to disable Magisk & flash back to my original boot.img before taking it, which I hope works but it should. It's great being rooted though on G7+ with Adaway and Youtube vanced background play, also Root Explorer to change my boot animation or debloat or whatever.
Dahenjo said:
If someone on your channel could capture their PPW29.98-66 OTA before installing, otherwise I think you'd have to wait until it appears on lolinet or Motorola's site, or we get TWRP. I realized I'd be in the same boat because my current firmware was also the only one so far on lolinet, so I decided to go ahead because I'd only get January's security patch (on Dec now) and still be a few months behind anyway.
Click to expand...
Click to collapse
Yeah, I thought so. Thanks anyway.
washoq said:
I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?
Click to expand...
Click to collapse
I see there is a PPW29.98-66 RETAIL channel firmware on lolinet:
https://mirrors.lolinet.com/firmware/moto/lake/official/RETAIL/
I'm not sure what difference the boot.img would have between them if any, and the RETAIL channel is more a 'generic' type which might be a safer choice than others of the same build version. I know the G5+ debloated ROMs by NZedPred ended up with just one version (instead of by various channels as he did originally) after finding he didn't need to bother, though I believe he did make other changes. He'd be a good one to ask though if you want to PM him.
After I get updated (revert to full stock etc) I may try the RETAIL one to re-root to see if we can use it for this purpose regardless of channel. My 'international model' from Amazon is actually just the RETLA channel since it wasn't released in the US, so I'd almost rather be on the more generic channel if it works.
EDIT:
Did some experimenting, reverted to full stock then successfully tried it again with the boot.img from the RETAIL firmware (which for my version is still PPW29.98-28), so I believe RETAIL could be used for other channels too.
This process worked for me. Moto G7 Plus, International Unlocked version.
This worked for me, XT1965-2, AT&T mexican version. Also, managed to run Substratum, just needed to compile, reboot and activate each time I changed theme.
Well I am on the same Page...
Also my Channel Islands reteu2, I can only find reteu...
My g7pluswas shipped already with a newer Version than available. Anyone tried the retail bootloader?
Alternatively, can we somehow flash the whole "retail" version on this phone?
shaDNfro said:
Well I am on the same Page...
Also my Channel Islands reteu2, I can only find reteu...
My g7 was shipped already with a newer Version than available. Anyone tried the retail bootloader?
Alternatively, can we somehow flash the whole "retail" version on this phone?
Click to expand...
Click to collapse
I assume you have G7 Plus (not G7) with the build number you showed.
To answer your question:
I successfully fastboot flashed the full RETAIL channel PPW29.98-66 firmware a few days ago. I was on RETLA PPW29.98-28 with the December security patch and now have the January patch, and my channel is still shown as RETLA. I used the batch file posted in this thread which worked perfectly. Everything for my XT1965-2 RETLA model is working as it should on the newer RETAIL firmware, but I don't know if your RETEU2 has anything different that could cause issues.
Enforced Verity, Unlocked Bootloader, rooted Lake OPENMX Not working with Google Pay
"Couldn't finish setup to pay in stores
This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
Did I screw up by not preserving dm/verity when I patched the boot and if so, is there a way to fix it? Reflash oem rom, reinstall magisk, repatch boot, rereflash new rom with dm/verity preserved?
vvarrior said:
"Couldn't finish setup to pay in stores
This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
Did I screw up by not preserving dm/verity when I patched the boot and if so, is there a way to fix it? Reflash oem rom, reinstall magisk, repatch boot, rereflash new rom with dm/verity preserved?
Click to expand...
Click to collapse
I tried everything but its not working stalble for me either.
You can do delete google pay cache+data and google play services cache+data, reboot and then you can configure a payment method (e.g. add credit card). Afterwards I was able to pay exactly one time... next time it refues my card telling me I am not able to pay with that card any more...
(Bye the way, people say the issue might be connected with wifi as well, so I turned off wifi for that procedure I mentioned above)
Anyway I deleted google pay now using my banks own application, which does not detect root using magisk hide
shaDNfro said:
I tried everything but its not working stalble for me either.
You can do delete google pay cache+data and google play services cache+data, reboot and then you can configure a payment method (e.g. add credit card). Afterwards I was able to pay exactly one time... next time it refues my card telling me I am not able to pay with that card any more...
(Bye the way, people say the issue might be connected with wifi as well, so I turned off wifi for that procedure I mentioned above)
Anyway I deleted google pay now using my banks own application, which does not detect root using magisk hide
Click to expand...
Click to collapse
There's a bunch of Google apps that need verity to be enforced I think. I think we need the stock ROM with the stock boot. Maybe the phone has to be rooted to patch the stock boot.img with verity enforced? I'm not sure but I stepped up to the G7 Plus because it finally has NFC so I can use it to pay and it was an unlocked international version that works good with Google Fi (which also needs verity enforced).
Still looking for a solution and will probably just go back to my old phone until I can get Google Fi and Pay working.
Pixel 4 "FLAME" March 2020 QQ2A.200305.003 boot.img - Stock and Magisk v20.4 Patched
Hey all, I just updated my wife's P4 to Magisk 20.4 as of yesterday and have had no issues so far on the new version (nor on my P4XL). Here are the stock and recently newly updated Magisk patched (v20.4) boot images. I couldn't direct install the update on either of the phones via Magisk Manager, so I figured I would share these images.
Stock March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757144
Magisk Patched (v20.4) March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757143
Remember, these are ONLY for those on QQ2A.200305.003 firmware already. Don't flash if you don't know what you're doing.
Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.
Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.
falawefulwaffle said:
Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.
Click to expand...
Click to collapse
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
Spookymyo said:
Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.
Click to expand...
Click to collapse
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.
i5lee8bit said:
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.
Click to expand...
Click to collapse
Thanks for the reply. I ended up getting it to work using the "payload_dumper-win64" method i found in another thread to extract the boot.img from the payload.bin file. Turns out the OTA file was online from google.
To updatePixel 4 xl with "coral-ota-qq2a.200305.003-3b25765d" MAach update OTA software:
- uninstalled Magisk
-updated software
-reinstalled magisk
-patched the boot img from payload.bin
-pushed modified boot to device
-Done
Everything seems to be working well. I got to use python for the first time, so that was kind of fun. I was a flashing machine back around the galaxy s4.
I got root working. Spent so much time trying different things and all I had to do was factory reset my phone. There must have been some file or module interfering with the process. Once I reset my phone the root process went without error. ?*
This thread is for Patched boot image posts. Please don't post boot.img files without having tried them and made sure they work. bootloops are not funny to watch.
Please consider to make sure to state:
Build number: Oxygen OS 11.0.1.1 GM21BA For example
Phone Model: GM1913 For example
Magisk: stable/beta/canary ver: 23.0 For example
this thread is similar to this one Here and intended to group in one place the patched boot.img as not everyone have succeeded in rooting their device with self patched images.
Your contribution is greatly appreciated.
I had mine working with root until yesterday morning that out of nowhere the phone app started giving errors and unable to connect to read the simcards
tascristiano said:
I had mine working with root until yesterday morning that out of nowhere the phone app started giving errors and unable to connect to read the simcards
Click to expand...
Click to collapse
If you have oos native call recording magisk module disable or remove it, you will get back your sim cards working again.
stuntora said:
If you have oos native call recording magisk module disable or remove it, you will get back your sim cards working again.
Click to expand...
Click to collapse
Thank you so much you solved my problem.
Do you know if the problem with this module is temporary or permanent?
tascristiano said:
Thank you so much you solved my problem.
Do you know if the problem with this module is temporary or permanent?
Click to expand...
Click to collapse
This module is not being updated any longer. Sometimes it it works sometimes not especially since android 11. You still can use Call Recorder app with root, it's not free but not overly priced either.
stuntora said:
This module is not being updated any longer. Sometimes it it works sometimes not especially since android 11. You still can use Call Recorder app with root, it's not free but not overly priced either.
Click to expand...
Click to collapse
Edit: just download this from play store and enable recording service, and disable the persistent notification. This will enable the native call recording again.
stuntora said:
Edit: just download this from play store and enable recording service, and disable the persistent notification. This will enable the native call recording again.
Click to expand...
Click to collapse
Awesome thank you
i recently discovered that you can just flash the apk and it does everything for you
Could U plz share a patched root.img from 11.0.5.1.GM21BA?
Frodolo said:
Could U plz share a patched root.img from 11.0.5.1.GM21BA?
Click to expand...
Click to collapse
Here you go
File on MEGA
mega.nz
Thank you a lot!!
Anyone happen to have the patched boot.img for 11.0.5.1 on GM21AA? I'm on the Global/US Unlocked version (GM1917). Needing that to fully update to Magisk 24.1. I highly appreciate it!
hx3 said:
Anyone happen to have the patched boot.img for 11.0.5.1 on GM21AA? I'm on the Global/US Unlocked version (GM1917). Needing that to fully update to Magisk 24.1. I highly appreciate it!
Click to expand...
Click to collapse
Dropbox - File Deleted - Simplify your life
www.dropbox.com
Thank you very much!
Can someone share their original patched boot please. My original is attached
Build number: Oxygen OS 11.0.6.1.GM21BA
Phone Model: GM1913
Magisk: stable ver: 23.0
Thank you in advance
NVM, I had to use Magisk 24.1 to be compatible with the new update.
Please, is there anyone having a boot.img from the latest firmware for OnePlus 7 Pro?
Build number: 11.0.9.1.GM21BA
Thank you in advance!
Finally installed A12 on my OP7Pro.. Unfortunatelly i could not install any recoverys (are there no compatible recoverys for A12 ?), so i had to take the non recovery method for rooting.
Attached the default one and the magisk patched. A12 OB2...
Edit:
Install it via:
fastboot flash boot_a magisk_patched-25100_AJanL.img
fastboot flash boot_b magisk_patched-25100_AJanL.img
After that you are rooted
FilePost
filepost.io
Anyone has Android 12 Beta patched boot img?
onkel_Andi said:
Finally installed A12 on my OP7Pro.. Unfortunatelly i could not install any recoverys (are there no compatible recoverys for A12 ?), so i had to take the non recovery method for rooting.
Attached the default one and the magisk patched. A12 OB2...
Edit:
Install it via:
fastboot flash boot_a magisk_patched-25100_AJanL.img
fastboot flash boot_b magisk_patched-25100_AJanL.img
After that you are rooted
FilePost
filepost.io
Click to expand...
Click to collapse
I need Android 12 Beta 2 patched boot
This is Android 12 Beta 2 patched boot img and original boot img..
✓Root done
✓Dolby Atmos done
✓Shamiko done
✓Ad away done
Boot patched and original img
Hi, I have decided to gather boot images and magisk patched images to one thread for now. I will try to edit this thread to be up-to-date. You can let me know what could you want next or if anything is wrong etc.
Stock boot.img files (direct links):
EU NE2213_11_A.12
Stock boot.img - link
EU NE2213_11_A.10
Stock boot.img - link
Magisk patched boot.img are here a file that can be downloaded (I am using magisk canary usually, but in Magisk, you can change the channel from the canary to stable etc.) - names as the versions come.
Below this there are those magisk patched files which you just flash (or boot and then flash directly from the Magisk app) via fastboot
Reserved
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
HessNL said:
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
Click to expand...
Click to collapse
Apparently not. I have patched that stock boot via magisk, then via fastboot boot <patchedimage.img> booted (and also tested if it actually boots) and when it booted, via magisk app I did "Direct install (recommended)", rebooted and done.
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
HessNL said:
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Click to expand...
Click to collapse
Yes, because this is probably and currently the most secure option to root it as we haven't got twrp available yet.
BuBbLeFIZzY said:
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
Click to expand...
Click to collapse
That's not that you have it early. The phone itself is early in spite of rooting and doing things like rooting, custom recoveries, ROMs etc. I currently can't find boot img for your model, but once I do, I will post it here for you with patched one.
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
fozzy056 said:
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
Click to expand...
Click to collapse
You're really welcome, I wanted to unite those currently quite hard rooting stuff!
And yes, I can't wait to see twrp too!
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
GeekMcLeod said:
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
Click to expand...
Click to collapse
Not yet unfortunately. Or I don't know about it yet. :/
kouzelnik3 said:
Not yet unfortunately. Or I don't know about it yet. :/
Click to expand...
Click to collapse
Yeah.. I googled a lot last night once I got my phone trying to find it to root it. I need me that extra bit of customization.
Is there a way I can get it from my phone?
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Johnstan725 said:
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Click to expand...
Click to collapse
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Johnstan725 said:
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Click to expand...
Click to collapse
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
g96818 said:
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
Click to expand...
Click to collapse
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Johnstan725 said:
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Click to expand...
Click to collapse
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
g96818 said:
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
Click to expand...
Click to collapse
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Johnstan725 said:
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Click to expand...
Click to collapse
Hmmm. Well you should be fine if you patched the boot and let magisk do the install. I only suggested wiping since you said you flashed the img from the bootloader.
You might run into the same problem I have with the 9RT. I too upgraded from color to oos and couldn’t update at all, even though I rooted from the magisk app. I had to wait for someone to make a fastboot rom. I had no problems updating color following my method, but not oos after switching. Hopefully that’s not the case for you.