Hello all
I have been using Magisk/Odin/Sammobile to root my phone and load firmware updates.
I read the advisory that the phone has to be wiped prior to loading 12. I installed the A12 firmware and then used Magisk to create the modified AP file. I then did another wipe and installed Android 12 using ODIN with the modified AP file and standard CSC file.
Whilst the firmware passed I haven't got root.
Can anyone advise what I have done wrong/missed or is there a specific way to obtain root with A12.
Or is it the case that root is not yet possible to obtain on the stable version of Android 12?
Any assistance would be greatly appreciated.
Regards
harjm said:
Hello all
I have been using Magisk/Odin/Sammobile to root my phone and load firmware updates.
I read the advisory that the phone has to be wiped prior to loading 12. I installed the A12 firmware and then used Magisk to create the modified AP file. I then did another wipe and installed Android 12 using ODIN with the modified AP file and standard CSC file.
Whilst the firmware passed I haven't got root.
Can anyone advise what I have done wrong/missed or is there a specific way to obtain root with A12.
Or is it the case that root is not yet possible to obtain on the stable version of Android 12?
Any assistance would be greatly appreciated.
Regards
Click to expand...
Click to collapse
I have the same issue would love to know how to fix it!
You have installed the magisk app? And did you use latest Canary build to Patch AP?
I updated from Android11 to 12 keeping all my data decrypted, and also rooted.
It requires the same procedure as performing minor update keeping data and root.
Magisk aplha is required. Also magisk modules should be disabled before update android version.
The only problem is that hidden magisk app, called proxy app, won't launch. While root functions are working.
sanoayyk said:
Actualicé de Android11 a 12 manteniendo todos mis datos descifrados y también rooteados.
Requiere el mismo procedimiento que realizar una actualización menor manteniendo los datos y la raíz.
Se requiere Magisk aplha. Además, los módulos de magisk deben desactivarse antes de actualizar la versión de Android.
El único problema es que la aplicación de magisk oculta, llamada aplicación de proxy, no se inicia. Mientras las funciones raíz están funcionando.
Click to expand...
Click to collapse
Can you make a little tutorial to explain us the procedure? thanks
sanoayyk said:
I updated from Android11 to 12 keeping all my data decrypted, and also rooted.
Click to expand...
Click to collapse
So I think you used Home_csc instead of Csc file to keep the data intact, am I right?
donkeyman1234 said:
So I think you used Home_csc instead of Csc file to keep the data intact, am I right?
Click to expand...
Click to collapse
Yes. home_csc is required to keep user data.
sanoayyk said:
I updated from Android11 to 12 keeping all my data decrypted, and also rooted.
It requires the same procedure as performing minor update keeping data and root.
Magisk aplha is required. Also magisk modules should be disabled before update android version.
The only problem is that hidden magisk app, called proxy app, won't launch. While root functions are working.
Click to expand...
Click to collapse
Did you perform this on snapdragon variant or the exynos one?
rehannali said:
Did you perform this on snapdragon variant or the exynos one?
Click to expand...
Click to collapse
Exynos. But also snapdragon variant should OK as long as magisk and twrp and multidisabler work.
sanoayyk said:
Exynos. But also snapdragon variant should OK as long as magisk and twrp and multidisabler work.
Click to expand...
Click to collapse
I tried with twrp and multidisabler, it failed to boot and stuck in bootloop. Always comes back to recovery.
rehannali said:
I tried with twrp and multidisabler, it failed to boot and stuck in bootloop. Always comes back to recovery.
Click to expand...
Click to collapse
did you try remove all magisk module? magisk should be alpha version.
sanoayyk said:
did you try remove all magisk module? magisk should be alpha version.
Click to expand...
Click to collapse
I'm doing clean install. Already lost all data.
sanoayyk said:
Magisk aplha is required. Also magisk modules should be disabled before update android version
Click to expand...
Click to collapse
Thanks
Uninstall Magisk, then install the canary -magisk.apk
Use the new Magisk app to patch your boot.tar
Related
Hi all
On the S10e is a problem by the rooting part from magisk. The approach with 'system-as-root' will not work.
It look likes, that the system not load the new ramdisk.packed. The hex-patch for skip_initramfs > want_* works.
The dt.img patch has also an error. This img must be manualy add to the boot.img for the hex-patches.
Has any one a fix?
*On the G970U works the approach.
Are you using Canary magisk ?
https://www.xda-developers.com/magisk-canary-update-support-aonly-system-root-android-pie/
spartanz51 said:
Are you using Canary magisk ?
https://www.xda-developers.com/magisk-canary-update-support-aonly-system-root-android-pie/
Click to expand...
Click to collapse
Yes. On the new s10 are no ramdisks included in the boot.img. So the 'system-as-root' is the way to go.
*On the actual magisk source, is an error for the dtb-patch.
sq_dev said:
Yes. On the new s10 are no ramdisks included in the boot.img. So the 'system-as-root' is the way to go.
*On the actual magisk source, is an error for the dtb-patch.
Click to expand...
Click to collapse
You use Canary or Official Magisk??
Cause on Canary there is a fix for system-as-root support
spartanz51 said:
You use Canary or Official Magisk??
Cause on Canary there is a fix for system-as-root support
Click to expand...
Click to collapse
Yes I have try both.
Now is the kernel available. I will check the functions.
How can you root without custom recovery?
Maybe I'm missing something cos I always root with TWRP + Magisk!
Lord Spectre said:
How can you root without custom recovery?
Maybe I'm missing something cos I always root with TWRP + Magisk!
Click to expand...
Click to collapse
With Odin
spartanz51 said:
With Odin
Click to expand...
Click to collapse
Thank you for reply. Could you please point me to the magisk package I have to flash with odin?
Is it ok the following one?
https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/release.json
Subscribed, wanting to root my 970u
Sent from my SM-G970U using Tapatalk
That's all quite interesting. I wonder if Magisk will also work with my Chinese Snapdragon S10+, or if something specific needs to be done for the particular architecture. I downloaded the zip file that's supposed to be installed and saw in boot_patch.sh that some changes are to be made in binary files. If those binaries are the same for both Exynos and Snapdragon, it should work on both, and if not, then my phone probably wouldn't boot because the binaries would be corrupt.
One of my questions is: were those patches based on compiling the kernel source code released by Samsung, or reverse engineering the binaries? Because if it's based on compiling from source with a couple modifications and then finding the difference with the stock binaries, it's less work than reverse engineering the binaries.
This is the only reason I got Exynos S10. Last year, it took a while for Chinese Snapdragon S10 root. Also Pie update was released first week of this year for Exynos whereas for SD it took them another month and a half.
So I am currently on CN 2.27 ROM from NA Global, I am wondering how and if I can update to version 2.30 because Boot Unlocked TWRP Magisk GAPPS Debloated. Does TWRP currently work on the update? I assume upon updating I will lose everything back to stock, but I want to be able to get phone back to current state...because well CN Rom is much better but this device is so finicky if you know what I'm saying.
SuperDroidMe said:
So I am currently on CN 2.27 ROM from NA Global, I am wondering how and if I can update to version 2.30 because Boot Unlocked TWRP Magisk GAPPS Debloated. Does TWRP currently work on the update? I assume upon updating I will lose everything back to stock, but I want to be able to get phone back to current state...because well CN Rom is much better but this device is so finicky if you know what I'm saying.
Click to expand...
Click to collapse
I have same question like you, my phone has installed CN 2.27 and TWRP with Magisk. How can I update to CN 2.30 without losing TWRP, Magisk and any other data from my phone? Please some advice me....
kotunmobile said:
I have same question like you, my phone has installed CN 2.27 and TWRP with Magisk. How can I update to CN 2.30 without losing TWRP, Magisk and any other data from my phone? Please some advice me....
Click to expand...
Click to collapse
First you have to download 2.27 zip file
Extract it
Flash stock boot and recovery image
And then update to 2.30
After that flash your TWRP and magisk
Just backup ur data with TWRP in case u face any problem
So what exactly do we lose and gain with the CN rom over the EU rom??
Assume CN rom can be set to full English so no Chinese language remains?
Yeah I relocked boot uninstalled Majisk and modules, updated 2.30....then reflashed and installed. Its super smooth and all the game launcher features are great. Totally enjoying this far more than global. Oh and holy crap all the camera features too.
SuperDroidMe said:
Yeah I relocked boot uninstalled Majisk and modules, updated 2.30....then reflashed and installed. Its super smooth and all the game launcher features are great. Totally enjoying this far more than global. Oh and holy crap all the camera features too.
Click to expand...
Click to collapse
So you mean TWRP-3.3.1-0528-NUBIA_REDMAGIC3-CN-wzsx150.img and Magisk-v19.3 still working on v2.30 itsn't?
Where can you download the CN rom from?
Do you have a copy on the china rom? It's not on the Nubia site anymore.
Sent from my Note 9 using XDA Labs
kotunmobile said:
So you mean TWRP-3.3.1-0528-NUBIA_REDMAGIC3-CN-wzsx150.img and Magisk-v19.3 still working on v2.30 itsn't?
Click to expand...
Click to collapse
Yes everything works, it's best to update cleanly then unlock bootloader, twrp flash, and root. Also if you flash gapps Pico in twrp CTS Profile SafetyNet will not pass....don't fret install Magisk Module Safety Patch by hackintosh5 in Magisk phone will reboot and system will Patch optimize on reboot and it will pass. Allowing full access to playstore and downloads.
Mountainmohawk said:
Do you have a copy on the china rom? It's not on the Nubia site anymore.[/QUOTE
http://ui.nubia.cn/rom/detail/62
Listen I have NA Global device, the easiest fail proof way to install CN Rom is in stock recovery, wipe data & cache use otg and FAT32 format pen drive to install...you will have no problems. If you decide to go back to Global do the same thing but with Global Rom on pen drive.
Click to expand...
Click to collapse
SuperDroidMe said:
Mountainmohawk said:
Do you have a copy on the china rom? It's not on the Nubia site anymore.[/QUOTE
http://ui.nubia.cn/rom/detail/62
Listen I have NA Global device, the easiest fail proof way to install CN Rom is in stock recovery, wipe data & cache use otg and FAT32 format pen drive to install...you will have no problems. If you decide to go back to Global do the same thing but with Global Rom on pen drive.
Click to expand...
Click to collapse
If you have a copy, can you upload it somewhere? The download is going incredibly slow and often fails when I try to download it from there.
Click to expand...
Click to collapse
Mountainmohawk said:
SuperDroidMe said:
If you have a copy, can you upload it somewhere? The download is going incredibly slow and often fails when I try to download it from there.
Click to expand...
Click to collapse
https://drive.google.com/open?id=1ACIyuB5_aP3flJLHwmZsfCgCWJSDPEOG
Click to expand...
Click to collapse
11.0.3.0
https://bigota.d.miui.com/V11.0.3.0...EAGlobal_V11.0.3.0.PFGEUXM_6ef58da8bd_9.0.zip
New links will be posted here.
Miui 11 ota?
Enviado desde mi Redmi Note 7 mediante Tapatalk
hi and thanks for the link, how to install this firmware, please.
lohanbarth said:
hi and thanks for the link, how to install this firmware, please.
Click to expand...
Click to collapse
Bonjour, moi perso j'ai utilisé OrangeFox pour flasher la rom par dessus la Miui V10.3.10.0 une fois fait, j'ai fait un wipe cache et voila, apres bien sur si tu veux a nouveau rooter tu flash TWRP et Magisk juste apres
Hello, I personally used OrangeFox to flash the rom over Miui V10.3.10.0 once done, I made a wipe cache and voila, after course if you want to root again you flash TWRP and Magisk just after
Cant update? It says i need to be beta tester? How?
I'm getting a message saying I need to be a beta tester to install this update too, but anyway feedback from people who could install it seems to indicate there's almost none of the anounced new features.
Do I need unlocked bootloader to install or can I install via Ota?
hello for me impossible to install it, it tells me that I must be beta-tester, I do not think we will have the ota by the end of the day, xiaomi is really making fun of us, more to wait.
lohanbarth said:
hello for me impossible to install it, it tells me that I must be beta-tester, I do not think we will have the ota by the end of the day, xiaomi is really making fun of us, more to wait.
Click to expand...
Click to collapse
MIUI11 was released today in India and Russia. Let's cross fingers for EEA, too.
I just received the update
Just received too. I have the terminal unlocked and rooted and I think the way to update without loosing twrp and root is:
- Download from this thread or directly in the update app. 'download last package'
- Reboot in TWRP, delete cache, davilk art
- Install miui 11 package
- Without rebooting, install magisk
- Reboot
Do i miss something?
Thanks in advance
Just received it, too. The changelog seems a little 'poor', doesn't it?
Can anyone help me with a link to miui 11.0.3.0 fastboot tgz file version please?
I got an OTA and tried downloading several times but a message appeared to try in a few minutes. after all there was a message that there was no update. IS OTA INCREASED OR IS IT ANOTHER IN QUESTION?
puntillero said:
Just received too. I have the terminal unlocked and rooted and I think the way to update without loosing twrp and root is:
- Download from this thread or directly in the update app. 'download last package'
- Reboot in TWRP, delete cache, davilk art
- Install miui 11 package
- Without rebooting, install magisk
- Reboot
Do i miss something?
Thanks in advance
Click to expand...
Click to collapse
I was wondering about this, I already posted in the global version thread. I will not update if I lose root.
Take a look at this:
https://forum.xda-developers.com/redmi-note-7/help/ota-update-unlocked-rooted-device-t3963409
Don't lose root if magisk is flashed after the rom without rebooting.
Anyway I'm going to wait. The update disappears suddenly in my mobile, I guess this update is coming with problems,
I receive the update yesterday, first impressions:
I litle bit laggy
more battery consumer
Just now updated manual way, before that I set region to German if you still can't update and get beta tester error.
[BUG]location mode does not allow you to select the three options, does anyone else confirm this BUG
zoko said:
[BUG]location mode does not allow you to select the three options, does anyone else confirm this BUG
Click to expand...
Click to collapse
It is fine for Me.
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
I have unlocked my bootloader, cross flashed to Android 9 and booted TWRP and flashed every LOS i could find in every order possible but thr closet I get is w LOS 18 it boots first time but fails after to reboot.
Has anyone got LOS to work on Sprint V40? The twrp thread mentions meta deta encryption and I have no idea what that means.
Can anyone tell me the order for getting LOS to boot from a fresh /full wipe?
FreeSoftwareServers said:
I have unlocked my bootloader, cross flashed to Android 9 and booted TWRP and flashed every LOS i could find in every order possible but thr closet I get is w LOS 18 it boots first time but fails after to reboot.
Has anyone got LOS to work on Sprint V40? The twrp thread mentions meta deta encryption and I have no idea what that means.
Can anyone tell me the order for getting LOS to boot from a fresh /full wipe?
Click to expand...
Click to collapse
I haven't done a lot with LOS on V40, but there's a few things that are common. One, the newer versions of LOS (like 18), require Android 10 of the original firmware, not Android 9.
Sprint, unfortunately, never came out with A10. Which means you'd have to 'crossflash' to a kdz that is 10 based. Most in your case would use VZW, as their kdz is available.
Metadata encryption is new in LOS (newer versions) and needs twrp that is meta aware. So if you want to run later versions of LOS you need that version of twrp, the 'meta data' version.
cheers