Has anyone updated to Android 12 and successfully rooted again with magisk? It seems from the Pixel 5 thread that there are problems with this..
I have removed root and restored stock boot + updated to Android 12. Have downloaded the factory image and am ready to patch + flash magisk patched boot, but I am reluctant to try after reading the Pixel 5 thread.
Sure, I've done it already.
Check here.
Worked for me too.
I'm starting to think that the 4a 5G and 5 (and presumably all newer models) have this restriction. Not sure why the 4a does not.
a1291762 said:
Worked for me too.
I'm starting to think that the 4a 5G and 5 (and presumably all newer models) have this restriction. Not sure why the 4a does not.
Click to expand...
Click to collapse
I have a Pixel 5 running official Android 12. I upgraded from a magisk rooted Android 11. When I flash the patched boot image in fastboot mode, restarting the device only takes me back to fastboot mode. The only way I can get past fastboot mode into Android 12 is to reflash the stock boot image.
Do I need to disable dmverity, etc.?
Skeetch79 said:
I have a Pixel 5 running official Android 12. I upgraded from a magisk rooted Android 11. When I flash the patched boot image in fastboot mode, restarting the device only takes me back to fastboot mode. The only way I can get past fastboot mode into Android 12 is to reflash the stock boot image.
Do I need to disable dmverity, etc.?
Click to expand...
Click to collapse
I haven't been flowing this thread since it doesn't apply to me but the last thing I saw seemed to suggest upgrading and then trying to figure it out didn't work. Check it out, maybe they got further.
[Closed] Android 12 Update and Root ***Obsolete***
Update 12-16: I am closing this thread as it is no longer relevant. Please refer to this guide.
forum.xda-developers.com
Related
I'm trying to install LOS 16.0 but it just won't work. I've tried using the TWRP 3.3.1-16 Q Unofficial by mauronofrio and it works that I can get into TWRP and can flash the rom and GApps, but then after that process once I try to boot into the OS it is just forever stuck in either fastboot or stuck on the bootloader unlocked warning screen. I did realize that I had to use fastboot flash boot twrp*.img because they disabled fastboot boot twrp*.img in the Android 10 update, but then am I supposed to reflash something on that boot partition now? The whole process is very confusing and the instructions from the LineageOS seem to not work at all. Is there anything I can do right now or is it just not possible to install this until TWRP, or OOS, or something I'm not knowledgeable enough to know about updates?
It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.
TheSproker said:
It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.
Click to expand...
Click to collapse
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.
remewer said:
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.
Click to expand...
Click to collapse
I tried this. I downgraded to 9.0.9 and still the fastboot boot command is not working. Apparently this has something to do with the bootloader image itself not being downgraded?
I give up now, my temp phone I was using for holding backups for chat data just randomly wiped itself on havocOS and I've just lost years of chats and stuff and it's got me really down right now. They did fix the fastboot boot issue with today's 10.3.0 update but still nothing is working from any tutorial to get this thing to work on lineage, it just won't boot to it and twrp keeps having errors during flashing. This used to be so much easier on my older phones and I've installed this OS on about 5 phones now but OnePlus 6 just doesn't seem to work no matter what. I'm just going to go back to OOS and hope LineageOS 17.0 will get these issues ironed out by the time it releases. Severely disappointing and a waste of 3 days now but oh well
In my opinion, this is the easiest way to downgrade everything to OOS 9, including bootloader https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
After that, just unlock the bootloader again like usual and follow the LOS16/17 page's install instructions and you should be good to go.
I tried to install Havoc 3.5 while i was on 10 Ob2, unlocked bootloader and installed patched twrp, then rom. Got stuck in fastboot mode. **** hell i messed everything, later i found fastboot recovery rom from xda, flashed it, thank god it saved me. For me, msm tool was not getting connected, got an error like sahara xyz something... Then after refering to multiple xda threads came to know that most of the present 10 custom roms are based on oos android 9. Then again i used downgrade package from community, reverted back to ob 25 oos (pie), then as usual installation process. So if you are interested in custom roms, downgrade to pie. And again i wanted to go back to complete stock from havoc but unfortunately msm was not responding and fastboot roms wont support upgradation (im not sure), i went to twrp and installed stable 9.0.9 to both partitions + twrp installer. Then 10 oos stable to both partitions + twrp. Then booted up and installed Ob2 again from system updater, lost twrp on that process, then locked bootloader, so mow completely stock ? lot of work for nothing ? oos is better for me.. infact i got used to that. maybe i should purchase another phone to continue the momentum of getting latest updates. crazy oos influence ?
I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
I had to make a new patched boot for 10.0.18.0 with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.18.0_204.img.gz
The March update is 10.0.20.0. I have a patched boot with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.20.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_10.0.20.0.img.gz
According to the update screen, March update is for Pie only. Android Q users must wait
Thank you :fingers-crossed:
I'm still on Android 8.1 and waiting stable Android 10
a1291762 said:
I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
I had to make a new patched boot for 10.0.18.0 with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.18.0_204.img.gz
The March update is 10.0.20.0. I have a patched boot with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.20.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_10.0.20.0.img.gz
According to the update screen, March update is for Pie only. Android Q users must wait
Click to expand...
Click to collapse
can i use this patch update is 10.0.20.0. with new magisk without ubl n twrp, it just install magisk manager 2.04 and select this image for root acces thanks before.
ony89 said:
can i use this patch update is 10.0.20.0. with new magisk without ubl n twrp, it just install magisk manager 2.04 and select this image for root acces thanks before.
Click to expand...
Click to collapse
If you have a locked bootloader, you can't do anything.
Magisk and root is separate to TWRP on this phone. This image will help you get Magisk installed.
Instructions here
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626
a1291762 said:
I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
I had to make a new patched boot for 10.0.18.0 with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.18.0_204.img.gz
The March update is 10.0.20.0. I have a patched boot with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.20.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_10.0.20.0.img.gz
According to the update screen, March update is for Pie only. Android Q users must wait
Click to expand...
Click to collapse
Hi a1291762, as a noob could I ask you a few questions please?
Wanting to downgrade from Q to Pie, could I used your 10.0.20.0 vanilla boot with the Mi Flash Tool using the steps here, and then if I wanted to add root I could use the 10.0.20.0 patched boot with the guide here?
Thank you!
wassupjg said:
Hi a1291762, as a noob could I ask you a few questions please?
Wanting to downgrade from Q to Pie, could I used your 10.0.20.0 vanilla boot with the Mi Flash Tool using the steps here, and then if I wanted to add root I could use the 10.0.20.0 patched boot with the guide here?
Click to expand...
Click to collapse
You might want to check that people have been able to downgrade. I know that pie-oreo caused a modem issue.
You need a fastboot image to downgrade. Unless MiFlash has magic (I have never used it).
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Looks like you'll have to downgrade to 10.0.18.0 and then apply the 10.0.20.0 update, since I do not see a fastboot for 10.0.20.0.
You won't need the vanilla boot image because it is in the fastboot image.
One you have 10.0.20.0 installed you can use the 10.0.20.0 patched boot to install Magisk.
a1291762 said:
You might want to check that people have been able to downgrade. I know that pie-oreo caused a modem issue.
You need a fastboot image to downgrade. Unless MiFlash has magic (I have never used it).
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Looks like you'll have to downgrade to 10.0.18.0 and then apply the 10.0.20.0 update, since I do not see a fastboot for 10.0.20.0.
You won't need the vanilla boot image because it is in the fastboot image.
One you have 10.0.20.0 installed you can use the 10.0.20.0 patched boot to install Magisk.
Click to expand...
Click to collapse
Much appreciated, I had thought your vanilla boot and the fastboot images were the same things, once I downgrade to 10.0.18.0, how would I apply the 10.0.20.0 update as I assume the next xiaomi system update would skip straight to the latest Q build?
wassupjg said:
Much appreciated, I had thought your vanilla boot and the fastboot images were the same things, once I downgrade to 10.0.18.0, how would I apply the 10.0.20.0 update as I assume the next xiaomi system update would skip straight to the latest Q build?
Click to expand...
Click to collapse
I'm not totally sure...
There are links to the OTA zips around. A thread about Android 10 showed how to install one using the stock recovery... I guess the same works for 10.0.20.0?
As a Linux user I would be inclined to try and use command line tools to install the OTA zip... But I don't even know if that's a thing
wassupjg said:
...
Click to expand...
Click to collapse
Apparently there was a 10.0.20.0 fastboot, but it's not on the fastboot thread
I don't know where I got this URL from but 10.0.20.0 is http://bigota.d.miui.com/V10.0.20.0...0.PDLMIXM_20200327.0000.00_9.0_2baf524aaf.tgz
a1291762 said:
Apparently there was a 10.0.20.0 fastboot, but it's not on the fastboot thread
I don't know where I got this URL from but 10.0.20.0 is http://bigota.d.miui.com/V10.0.20.0...0.PDLMIXM_20200327.0000.00_9.0_2baf524aaf.tgz
Click to expand...
Click to collapse
Thanks dude, I did find it here in the posts, I guess the OP isn't updated anymore, I've just had too many problems with Q, it sucks imo, once I back up everything I'll give it a go, by any chance do you know any good app and general backup apps that make things easy?
wassupjg said:
by any chance do you know any good app and general backup apps that make things easy?
Click to expand...
Click to collapse
I bought titanium backup pro a long time ago and still use it. Back in the day, the free version was annoying for whole device restore. But it's let me move across 5 devices and saved me from losing data on many occasions so I consider it money well spent.
I backup and then rsync /sdcard to a computer daily (CLI tools from cron). For restore I copy the files back (if needed) and then restore.
I only backup user apps, call history and SMS. System apps don't restore properly these days.
TLDR
anyone get twrp 3.4 working with android 10? twrp released version 3.4 which supposedly supports android 10 and pixel 3a is a supported device. i flashed twrp and now twrp boots but nothing else does. its not a problem i can give it a try again just wondering how other people flashed it and got it to work.
long version:
TWRP released version 3.4 which supports android 10! yay im all happy and crap because pixel 3a is supported so i flash a kernel that supports LZMA compression. (i installed elemental x for android 10) and now i meet all the requirements. go to boot the .img file like they say using fastboot. i typed into ubuntu terminal "fastboot boot twrp3.4sargo.img" i get "error verifying the received boot.img: invalid parameter" this is the same exact error when booting older twrp recoveries because they arent compatible with android 10. not a problem though i thought! i have ex kernel manager so i can flash the twrp zip file through there! (thats what twrp website tells you to do if twrp had booted anyways so i thought well maybe i can skip that step since it isnt booting anyway and just flash the damn file) so i open ex kernel manager and flash the zip file! twrp boots im all happy and then i go to reboot and S#!+. nothing boots except twrp. anyone have any ideas on getting this to work since supposedly pixel3a android 10 is supported now?
Whenever Ive seen that error it means its not recognizing the partition youre trying to flash. Try adding the "a" or "b" after boot. So fastboot boot boot_a or boot_b depending on which is the active partition.
All this said, what are you trying to flash? A patched boot image or TWRP? If TWRP then you dont want to flash it to the boot partition, that goes to recovery.
Have you ever had to flash a full factory image of Android 10 (not just an OTA update)? TWRP will only work on Android 10 if the device was updated from Android 9 and still retains it's Android 9 file structure. I'm wondering if the file structure gets changed to the regular Android 10 file structure when you flash a full factory image vs an OTA update from Android 9 to Android 10 - I'm betting that it does. This would mean that TWRP would not work.
I honestly didn't even know this was released and I will try to install it on my 3A XL later today. I have flashed an Android 10 factory image since I moved from 9 to 10 via an OTA update, so I guess I will be able to test my hypothesis.
ctfrommn said:
Whenever Ive seen that error it means its not recognizing the partition youre trying to flash. Try adding the "a" or "b" after boot. So fastboot boot boot_a or boot_b depending on which is the active partition.
All this said, what are you trying to flash? A patched boot image or TWRP? If TWRP then you dont want to flash it to the boot partition, that goes to recovery.
Click to expand...
Click to collapse
Sorry been busy didn't have time to check this. I did try to flash to recovery. Flashing to boot was a typo. Same error result though. I'll try the a b partition thing later.
sic0048 said:
Have you ever had to flash a full factory image of Android 10 (not just an OTA update)? TWRP will only work on Android 10 if the device was updated from Android 9 and still retains it's Android 9 file structure. I'm wondering if the file structure gets changed to the regular Android 10 file structure when you flash a full factory image vs an OTA update from Android 9 to Android 10 - I'm betting that it does. This would mean that TWRP would not work.
I honestly didn't even know this was released and I will try to install it on my 3A XL later today. I have flashed an Android 10 factory image since I moved from 9 to 10 via an OTA update, so I guess I will be able to test my hypothesis.
Click to expand...
Click to collapse
Did you ever get it to work?
AudibleDruid said:
Did you ever get it to work?
Click to expand...
Click to collapse
I haven't tried yet. Honestly I'm not very motivated either. I'm 99.9% sure it won't work (because I have flashed a full factory image of Android 10 since taking the OTA update) and I don't feel like getting myself into a situation where I might have to reset my phone. I realize it shouldn't go that far, but the "reward" simply isn't worth the risk for me right now.
The Pixel-3a partition scheme was updated when upgraded to Android 10, i.e. the Pixel-3a is an exception to the rule that a device launched with Android 9 is compatible with TWRP 3.4. The Pixel-3a having Android 10 has the same structure like a device directly launched with Android 10 and so TWRP 3.4 will not work.
Hi,
After ignoring the notification to update to Android 11 for over a month, I finally gave in an tried the update today.
I normally run stock OOS ROM with TWRP and Magisk, and updates are always fairly simple, let the OS update, overwriting the recovery and losing root, plug in to the PC and just `fastboot boot` the TWRP image, and then flash TWRP and Magisk on the phone itself, and bobs your teapot.
Alas, Android 11 shat all over those plans. With all the news out about Android 12 being in Beta, I had forgotten that Android 11 was so new to OP7Pro. Correct me if I wrong, but TWRP doesn't seem to work, which was my first mistake, but now Magisk has moved to a "need to patch the boot.img" model, which I hadn't seen before?
Anyways, after attempting to patch my own boot.img, I can no longer boot anything; phone just gets past the bootloader unlocked warning, then reboots into recovery.
I panicked then and attempted to flash one of the flashable Android 10 images from Mauronofrio's thread, which I think made things worse; now it just reboots repeatedly.
Any help appreciated, thanks!
Woops, I actually have a Oneplus 7 Pro (not a 7T). Can I move a thread myself?
I managed to use the MSM Download Tool from the last time I bricked my phone, which got me back to a bootable Android 10. Not much worse in life than losing all my data but better than a brick.
mc_teo said:
Woops, I actually have a Oneplus 7 Pro (not a 7T). Can I move a thread myself?
(...)
Click to expand...
Click to collapse
You cannot
But we gladly do this for you (as I just did)! Remember that you can always report your own posts for any type of forum maintenance you may need.
At your service and stay safe!
Timmy
Forum Moderator
A fix for your failed patched boot.img is just flashing the stock boot.img.
For upgrading (official OTA) and keep root, after installation finishes don't reboot and go to magisk, select install to the inactive slot and reboot, after reboot your phone will have the lastest update without loosing root.
And the best way to restore your phone is using msmtool
Hi, today i flash the december update in my pixel 6a, now i can´t root, magisk patch the image but when i flash it (fastboot flash boot magisk-patched.img) the phone join in a bootloop and need to reinstall the rom, any help?
I have seen below another thread with the same problem but they talk about the QPR2 beta and I don't know if the same procedure applies with the December update.
Thanks!
What do you mean? If bootloader is unlocked and you run 'fastboot flash boot "file" ' will it work fine.
You can also check the magic managers logs on /cache.
dannyzamora said:
Hi, today i flash the december update in my pixel 6a, now i can´t root, magisk patch the image but when i flash it (fastboot flash boot magisk-patched.img) the phone join in a bootloop and need to reinstall the rom, any help?
I have seen below another thread with the same problem but they talk about the QPR2 beta and I don't know if the same procedure applies with the December update.
Thanks!
Click to expand...
Click to collapse
Make sure you don't have any Magisk mods that may need disabling and updating.
And no, the same procedure does not apply for the stable December update as it does for QPR2 Beta 1.
JonasHS said:
What do you mean? If bootloader is unlocked and you run 'fastboot flash boot "file" ' will it work fine.
You can also check the magic managers logs on /cache.
Click to expand...
Click to collapse
Yes, that is the procedure I am referring to, the one I have always used, it is strange, as I said, I have followed the same steps as always:
1. Download Factory image of december for Pixel 6a (the last one available in the web).
2. Extract boot.img
3. Patch it with latest magisk app (25.2)
4. Reboot to fastboot
5. Use command "fastboot flash boot magisk-patched.img"
The command is applied correctly but when rebooting the terminal stays in the "Google" logo and after a while it reboots and returns to the same "Google" screen, so in a loop.
Lughnasadh said:
Make sure you don't have any Magisk mods that may need disabling and updating.
An no, the same procedure does not apply for the stable December update as it does for QPR2 Beta 1.
Click to expand...
Click to collapse
I don't have any modules installed, it's a clean install of everything.
It will sound stupid but... I did the steps indicated in the other thread and I have solved the problem, I have root.
I downloaded the december image of the Pixel 7 Pro, extracted the boot.img, patched it with magisk and flashed it with the usual command "fastboot flash boot magisk-patched.img" and it let me boot without problems and working root.
thats crazy, Im on december update A13 and I had no issues whatsoever.
booted the image and then flashed through magisk instead of flashing it directly but still... if it were broken that wouldnthave worked
G5-User7080 said:
thats crazy, Im on december update A13 and I had no issues whatsoever.
booted the image and then flashed through magisk instead of flashing it directly but still... if it were broken that wouldnthave worked
Click to expand...
Click to collapse
I know, the truth is that it makes no sense that I have given me this problem because I did not see anyone else with the December update talking about this particular problem, the closest thing was the post I mentioned with the beta, the phone had just arrived from the SAT but I do not think this influenced the problem, it came with the November update and I updated it to the December update.
You mentionned you downloaded the image for the Pixel 7 pro. I assume you made a type and are not flashing a pixel 7 pro image to a pixel 6a? If not then get the right image file.
Otherwise I suggest using the Pixel Flasher software posted in this forum. It's a really good piece of software.
No hassle with manual flashing anymore.
With Pixel Flasher I even update to new security patches with keeping root in like 4-10 minutes, by just downloading the image and then clicking a couple buttons