Related
So I have a rooted Pixel 3 through Magisk that I have been updating monthly up until this point via flashing the factory image with the flash.bat edited to remove "-w" from it to ensure that my phone does not become wiped after flashing each month's update. Afterwards, I would boot up the temporary TWRP image to then install the Magisk zip to re-root it. This had worked well up until this point. However, this month with the Android 10 update, this method has failed me. For this month, I did the exact same thing...download the factory image extract the image and other parts (including the flash.bat file), edit the flash.bat file and run. The issue was after flashing, the phone would try to boot and then get stuck at the G-logo with the loading bar under. It would use up about 5-10 mins to try and boot up, then fail, and then reboot again, fail again a second time and then just go fastboot mode. I tried this with both the .019 and .020 firmware and both failed me. In order to fix my phone, I'd just install the factory image of the August update instead, which had no issue.
I next attempted to ADB sideload the OTA update. I made sure to start with an unrooted install of the August update (by doing what I said above), and then using stock recovery would use ADB sideload with the new Sept OTA update. After sideloading, when trying to boot up the phone would attempt to boot around 7-9 times and just fail as it kept trying and trying to load up. Again, needed to fix it by flashing the August update.
I've done a bit of reading and it seems people have done factory resets and wipes of the phone before finally having success updating their phone to Android 10. I'm really hoping a method to fix this WITHOUT needing to do a factory wipe of my phone....
if you haven't already, try downloading the latest fastboot binaries from google.
Also FYI rooting Android Q on Pixel 3 is still difficult because TWRP doesn't support Android Q yet.
guest12233213113 said:
if you haven't already, try downloading the latest fastboot binaries from google.
Also FYI rooting Android Q on Pixel 3 is still difficult because TWRP doesn't support Android Q yet.
Click to expand...
Click to collapse
Are you referring to the SDK Platform tools? I was using version 29.0.2 from July for the past week until I recently saw 29.0.3 popup in the last day or so (was released a few days AFTER the factory images for Android 10 were released). Have tried with 29.0.3 and still not working. I get the issue "no valid slot to boot".
You might have already tried it but if not you could try flash without -w both slots just to make sure everything is synced up? I've had to do this once in a while to correct weird stuff. There may be better ways but when I remove -w I then add --skip-reboot. Then you can change slots with 'fastboot set_active SLOT' after the flash without rebooting and then simply run the flash again.
ktdt00 said:
You might have already tried it but if not you could try flash without -w both slots just to make sure everything is synced up? I've had to do this once in a while to correct weird stuff. There may be better ways but when I remove -w I then add --skip-reboot. Then you can change slots with 'fastboot set_active SLOT' after the flash without rebooting and then simply run the flash again.
Click to expand...
Click to collapse
Just tried your suggestion of flashing to both slots. Unfortunately, same result.
Toronadian said:
Just tried your suggestion of flashing to both slots. Unfortunately, same result.
Click to expand...
Click to collapse
What version of magisk manager are you using? You need the canary build. Then modify the boot image with it and flash that thru fastboot. You can't flash the magisk zip in twrp anymore, at this time.
jd1639 said:
What version of magisk manager are you using? You need the canary build. Then modify the boot image with it and flash that thru fastboot. You can't flash the magisk zip in twrp anymore, at this time.
Click to expand...
Click to collapse
Since attempting to switch to Android 10, I've been using the latest Canary build of Magisk Manager, currently 7.3.3-f383d11d (234).
The thing though is that it's bootlooping before I even attempt to root. Like after attempting to update the firmware on it's first attempt the device is bootlooping. It's happening when it's stock (no patched boot image. I've tried it with both the stock firmware, and also flashing the patched boot image before it's first boot up after the update and both cases there's a bootloop.
Toronadian said:
Since attempting to switch to Android 10, I've been using the latest Canary build of Magisk Manager, currently 7.3.3-f383d11d (234).
The thing though is that it's bootlooping before I even attempt to root. Like after attempting to update the firmware on it's first attempt the device is bootlooping. It's happening when it's stock (no patched boot image. I've tried it with both the stock firmware, and also flashing the patched boot image before it's first boot up after the update and both cases there's a bootloop.
Click to expand...
Click to collapse
You possibly need to completely uninstall magisk. But of course twrp is not working on 10 so that's a non- starter. See the last 3 or 4 pages of the twrp thread for the 3xl. @Tulsadiver has a boot image file that i think will work for you.
jd1639 said:
You possibly need to completely uninstall magisk. But of course twrp is not working on 10 so that's a non- starter. See the last 3 or 4 pages of the twrp thread for the 3xl. @Tulsadiver has a boot image file that i think will work for you.
Click to expand...
Click to collapse
Are you referring to uninstalling Magisk on Android Pie before trying to flash Android 10?
Toronadian said:
Are you referring to uninstalling Magisk on Android Pie before trying to flash Android 10?
Click to expand...
Click to collapse
No, i think you need to do it now. You have some half installed magisk and it's not letting you boot. You need a work around that to get it to boot. If i read correctly, you've already tried to flash the stock firmware with the - w in the flash all batch file. But check out that thread in the 3xl forum and see if others have been successful with it.
jd1639 said:
No, i think you need to do it now. You have some half installed magisk and it's not letting you boot. You need a work around that to get it to boot. If i read correctly, you've already tried to flash the stock firmware with the - w in the flash all batch file. But check out that thread in the 3xl forum and see if others have been successful with it.
Click to expand...
Click to collapse
If you're talking about right now, I'm back on August update, so still Android 9, with my phone rooted via Magisk and everything is currently functional. So use TWRP, flash the latest Magisk Uninstaller?
Afterwards what should I do after? I'm looking in the TWRP thread for the 3XL, is THIS the boot image you would like me to try? Should I be flashing that boot image AFTER updating to Android 10 (if it works)?
Toronadian said:
Are you referring to uninstalling Magisk on Android Pie before trying to flash Android 10?
Click to expand...
Click to collapse
Try fastboot boot image-new.img, this image. It should boot core-only mode and you can then see if you have some modules installed that need to be removed (/data/ADB/modules). It is not zipped. Just rename it as image-new.img
https://www.androidfilehost.com/?fid=1899786940962585361
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
Toronadian said:
If you're talking about right now, I'm back on August update, so still Android 9, with my phone rooted via Magisk and everything is currently functional. So use TWRP, flash the latest Magisk Uninstaller?
Afterwards what should I do after? I'm looking in the TWRP thread for the 3XL, is THIS the boot image you would like me to try? Should I be flashing that boot image AFTER updating to Android 10 (if it works)?
Click to expand...
Click to collapse
Yes, flash uninstaller if you can or maybe in magisk manager click uninstall. Modules survive updates and you might have pie modules that obviously aren't meant for Android 10.
Tulsadiver said:
Try fastboot boot image-new.img, this image. It should boot core-only mode and you can then see if you have some modules installed that need to be removed (/data/ADB/modules). It is not zipped. Just rename it as image-new.img
https://www.androidfilehost.com/?fid=1899786940962585361
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
Yes, flash uninstaller if you can or maybe in magisk manager click uninstall. Modules survive updates and you might have pie modules that obviously aren't meant for Android 10.
Click to expand...
Click to collapse
Alright I'll try running the magisk uninstaller zip in twrp later tonight.
I haven't installed any modules but I did use the systemless hosts setting (for Adaway) and I do see it in my "modules" tab. Wonder if that's the culprit.
The boot image you have posted, is that to be flashed after/if Android 10 boots up successfully after flashing the factory image?
Toronadian said:
Alright I'll try running the magisk uninstaller zip in twrp later tonight.
I haven't installed any modules but I did use the systemless hosts setting (for Adaway) and I do see it in my "modules" tab. Wonder if that's the culprit.
The boot image you have posted, is that to be flashed after/if Android 10 boots up successfully after flashing the factory image?
Click to expand...
Click to collapse
Curious, how do you run the uninstaller in TWRP without a working TWRP?
The image I posted is to recover from bootloop caused by bad modules. Phone should boot up with modules disabled.
Tulsadiver said:
Try fastboot boot image-new.img, this image. It should boot core-only mode and you can then see if you have some modules installed that need to be removed (/data/ADB/modules). It is not zipped. Just rename it as image-new.img
https://www.androidfilehost.com/?fid=1899786940962585361
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
Yes, flash uninstaller if you can or maybe in magisk manager click uninstall. Modules survive updates and you might have pie modules that obviously aren't meant for Android 10.
Click to expand...
Click to collapse
Tulsadiver said:
Curious, how do you run the uninstaller in TWRP without a working TWRP?
The image I posted is to recover from bootloop caused by bad modules. Phone should boot up with modules disabled.
Click to expand...
Click to collapse
I boot the temporary TWRP image for Android 9 as it works on that. I'd assume I would use the install option with the uninstaller zip? Keep in mind currently I'm on Android 9 right now (every time I bootloop due to the Android 10 flashing not working, I run the flash.bat script to reinstall the August firmware).
And speaking of nonworking TWRP on Android 10...if for some reason magisk causes bootloop, in order to uninstall magisk, would I need to adb sideload it then?
OK seriously....really have no idea what the issue is. In TWRP on Android 9, I flashed the Magisk Uninstaller zip then attempted to run the flash.bat file to try and flash Android 10. Exact same issue before with the bootloop. Before that, I also tried flashing Android 10 after I had removed the Systemless Hosts "module" that was there (yes, I did restart the phone first after removing it), same thing with the bootloop. I have no clue.
Update Sept. 24:
Whelp, seems like people are just as out of ideas as I am. I tried today the NEW firmware Google just released (.20.C3, differs from the one released earlier in the month) as well as the newest SDK Platform Tools (29.0.4, a second update that was released in September), still not working. I installed the factory image using the edited flash-all.bat file (removing "-w") and again, device tries to boot up twice and then restart back in fastboot mode, with the issue being "no valid slot to boot".
EDIT: Re-flashed August firmware back onto the phone, and then tried to sideload the new .20.C3 firmware as a OTA (yes, I made sure to use the OTA zip and not the factory image), now just continuously bootlooping. I think I'm on bootloop #5 or 6 right now.
FINALLY have a positive update. I have Cerberus, an anti-theft app on my phone that I tried to uninstall just for the sake of trying to see if some apps were causing compatibility issues. I was trying this after reading one of the really long threads on the Google support threads that someone managed to get the Android 10 update to work AFTER removing some apps. After taking some time to finally remove Cerberus for the time being, I once again tried to flash the factory image for Android 10 (the newest one, .20.C3) and it ACTUALLY managed to work. I'm now finally on Android 10.
With my own device finally figured out, I think I may give my wife and dad's devices a try to update to Android 10 (they're on Pixel 2 and 2XL respectively). I installed Cerberus on their devices as well and I think I'm gonna try removing that first and seeing if that manages to allow me to update the Pixel 2 and the 2XL to Android 10.
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots? I wish I could check but since my touch screen doesn't work in TWRP..
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
kerelberel said:
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, where do I download it, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots?
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
Click to expand...
Click to collapse
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
vinoxflame said:
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
Click to expand...
Click to collapse
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
then try another version of twrp or the unofficial orangefox recovery for our device
vinoxflame said:
then try another version of twrp or the unofficial orangefox recovery for our device
Click to expand...
Click to collapse
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
kerelberel said:
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
Click to expand...
Click to collapse
it's on the telegram group
vinoxflame said:
it's on the telegram group
Click to expand...
Click to collapse
No it is not. There's no mention of G7 Power in the search results. Only E5.
kerelberel said:
No it is not. There's no mention of G7 Power in the search results. Only E5.
Click to expand...
Click to collapse
deleted
vinoxflame said:
https://t.me/mG7Power
tell me if it is not!!!!
Click to expand...
Click to collapse
From the desktop search in this one I couldn't find it: https://t.me/OrangeFoxRecovery I didn't know there was a separate chat for each device. But thanks.
FWIW when this happened to me I did the blankflash thing to get it back to bootloader. Then I used the LMSA tool from Motorola to do a rescue/restore.
I also used LMSA to force the update to the most recent security update. In general, it seems a very useful utility.
https://www.motorola.com/us/lenovo-motorola-smart-assistant
I had this issue after blankflashing this temperamental device out of a brick. While in twrp you can do "adb shell" then "twrp install /path/to/zip" I think this has to do with new twrp versions on older firmwares
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done.
---------- Post added at 06:06 PM ---------- Previous post was at 05:58 PM ----------
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done. The latest stock RETUS build i can find is here https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip but if i do that i will lose all my apps AGAIN etc I am trying to just get the stock recovery img from previous version so I can install the ota in magisk you just tap uninstall tap restore images to get stock boot as well then ota should work once its done go back into magisk and install to inactive slot but you will or could need TWRP A/B retention script so that you keep it even after ota...which you will first go in magisk tap uninstall restore images, but must have stock recovery not twrp installed at this time either from what i can tell, once ota is successful install the TWRP A/B Retention script but do this before you install magisk to inactive slot from magisk manager after that it should work. But I cannot locate a stock recovery.img thus far.... and I dont wanna redownload my apps right now, so I may just wait til I see a rom i really think ill like and say screw it.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
s33b said:
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
Click to expand...
Click to collapse
I've flashed another stock rom (https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138) and it worked with twrp-3.3.1-0-ocean.img not with the newest.
kerelberel said:
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
Click to expand...
Click to collapse
You use fastboot commands in the bootloader.
The firmware contains a flash file with all fastboot commands you'll need.
kerelberel said:
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
Click to expand...
Click to collapse
TWRP has adb enabled by default. So instead of TWRP you can use
Code:
abd shell twrp --help
So you can use the basic functions like backup, install, and so on.
I had the same issue...
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
TheGuysGuysGuy said:
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
Click to expand...
Click to collapse
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
roadkill42 said:
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
Click to expand...
Click to collapse
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
TheGuysGuysGuy said:
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
Click to expand...
Click to collapse
The problem with the touch is the right driver needs to b installed that kernel I shared makes it work and stick I'm on it now go to tellagram group Moto g7 power support group both twrp and ofox there that works not the one from twrp it's self and the twrp there has some other features that one from official one has that don't work
This boot image gave me a touchscreen and allowed me to flash a regular twrp: hxxps://f.emvn.me/android-roms-and-stuff/twrp.3.4-kakarot.boot.img
Thanks to whoever made it.
[UPDATE/KEEP ROOT GUIDE] Jun 2020 (QQ3A.200605.001) "CORAL" Magisk-Patched Boot Image
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
Hey guys, yup, I'm still furloughed... ;_;
So anyway, here are the factory and Magisk Patched (v.24 is still the latest as of typing this) boot images for the June 2020 (QQ3A.200605.001) update.
ALL FILES BELOW ARE FOR JUNE 2020 QQ3A.200605.001!
Magisk v20.4 Patched Boot Image: https://www.androidfilehost.com/?fid=4349826312261824138
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=4349826312261824136
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=4349826312261824137
THESE FILES ARE FOR "10.0.0 (QQ3A.200605.001, Jun 2020)" ONLY! PLEASE ONLY FLASH IF YOU KNOW WHAT YOU'RE DOING!
Everything seems to work fine so far. Magisk v.24 and EdXposed 5.0.0 (4548 YAHFA). SafetyNet Passing for now... Kirisakura 4.7.5 (just released today!) works great too!
If these files and/or guides are helpful, please drop a thanks and let me know. Thanks! =)
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide exactly if coming EXACTLY from build qq2a.200501.001.b2, May 2020. But the general idea is the same for other builds, you just need the correct files for your device.
coral-qq2a.200501.001.b2-factory-dtbo.img: https://www.androidfilehost.com/?fid=4349826312261824163
coral-qq2a.200501.001.b2-factory-boot.img: https://www.androidfilehost.com/?fid=4349826312261796399
June 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-qq3a.200605.001-3b5bb1bd.zip
I DID NOT BOOT BACK INTO O/S UNTIL ALL STEPS WERE COMPLETED - I DID THIS TO ENSURE EVERYTHING WOULD BOOT BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-qq2a.200501.001.b2-factory-boot.img
3. fastboot flash dtbo coral-qq2a.200501.001.b2-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-qq3a.200605.001-3b5bb1bd.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-qq3a.200605.001-magisk_patched-20.4.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it. I've only personally tested with Kirisakura though.)
This was a 100% seamless update that required no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
...More details and guide / cleanups to come. I'm home alone today and taking care of our 5 month old, and he just woke up!!!
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
Doesn't work. Even recreating all the patched img files on my own, after a full factory reset, results in a boot to black screen with only the power menu available.
No clue why, unrooted with stock boot.img works fine
edit: should note that this is even without any modules
Shayded said:
Doesn't work. Even recreating all the patched img files on my own, after a full factory reset, results in a boot to black screen with only the power menu available.
No clue why, unrooted with stock boot.img works fine
Click to expand...
Click to collapse
Weird that it wouldn't work even after a full factory reset. Unfortunately I don't have a means of testing that. I edited my 3rd post with some troubleshooting instructions, sort of copied and pasted from my previous thread. You said you already factory resetted and it still doesn't work, but I would have otherwise recommended checking Tulsadiver's thread (he has an updated pre-made Magisk Core-Only mode boot image on his thread) in order to find and disable the bad module. Again, since you already tried factory reset, that wouldn't really apply and that's very strange.
I attached screenshots to the OP that shows it working... Sorry I can't help much more. The baby needs to be fed now...!! Typed all this while warming up the milk bottle...
i5lee8bit said:
Weird that it wouldn't work even after a full factory reset. Unfortunately I don't have a means of testing that. I edited my 3rd post with some troubleshooting instructions, sort of copied and pasted from my previous thread. You said you already factory resetted and it still doesn't work, but I would have otherwise recommended checking Tulsadiver's thread (he has an updated pre-made Magisk Core-Only mode boot image on his thread) in order to find and disable the bad module. Again, since you already tried factory reset, that wouldn't really apply and that's very strange.
I attached screenshots to the OP that shows it working... Sorry I can't help much more. The baby needs to be fed now...!! Typed all this while warming up the milk bottle...
Click to expand...
Click to collapse
yeah it's very odd. The second I try to boot even a clean factory image with a patched boot.img it just gives the black screen.
You guys still have motion sense ?
i can't make it work with magisk....
i tryed factory reset, it worked but once magisk is installed no more motion sense for me..( safetynet is ok...just in case )
any help please ?
i tryed a few things with props edit but no luck
Used this guide to come from the April update, everything seems to be working without issue.
****EDIT
So was bored and wanted to do some testing and it seems to be magisk modules that are most likely causing the majority of the issues
I flashed via fastboot then booted from the 6-2-20 image of this post and disabled all of the modules except the riru core and edxposed
Then rebooted to fastboot and flashed the patched boot image from OP works like a charm for anyone having issues.
EDIT***
Really strange outcome after doing this method for this month's update.
I'm on the smaller Pixel 4 but having been using your threads as a cheat sheet for a while. After the update was installed and magisk-patched boot images was flashed, it booted but I couldn't pull down my notification bar the second time to get into settings, couldn't enable mobile data, couldn't access storage from PC (notification to select USB options wasn't there), no notifications where shown but sounds were still coming in, no developer options, and a ton of other weird stuff. Overall, it seemed like it somehow only installed half the system since it felt like it was missing a lot of options and features. Tried reflashing the full factory image which did not seem to help. Only was able to get it functioning again through a clean install. No clue as to what could've happened this time around.
Copy and pasted method, just as you did in previous month. Your EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS is flawless for me.
baleskoil said:
You guys still have motion sense ?
i can't make it work with magisk....
i tryed factory reset, it worked but once magisk is installed no more motion sense for me..( safetynet is ok...just in case )
any help please ?
i tryed a few things with props edit but no luck
Click to expand...
Click to collapse
That's weird. I just tested it and it worked fine. I only have it enabled for alarms, and that's all I tested for though.
edit: I just tested on my wife's phone which I just updated (it's a Pixel 4, non-XL) and she uses the pause / skip motion sense, and it all works fine after updating... sorry man.
xxxtncxxx said:
****EDIT
So was bored and wanted to do some testing and it seems to be magisk modules that are most likely causing the majority of the issues
I flashed via fastboot then booted from the 6-2-20 image of this post and disabled all of the modules except the riru core and edxposed
Then rebooted to fastboot and flashed the patched boot image from OP works like a charm for anyone having issues.
EDIT***
Click to expand...
Click to collapse
I'm attaching a list of all of my Magisk and EdXposed modules being used to this post. So far, I haven't had any issues whatsoever. Not sure if it'll be helpful, but seems ppl are having scattered issues with this update. Tbh, I don't have a huge number of modules, at least I think relatively.
tysj said:
Really strange outcome after doing this method for this month's update.
I'm on the smaller Pixel 4 but having been using your threads as a cheat sheet for a while. After the update was installed and magisk-patched boot images was flashed, it booted but I couldn't pull down my notification bar the second time to get into settings, couldn't enable mobile data, couldn't access storage from PC (notification to select USB options wasn't there), no notifications where shown but sounds were still coming in, no developer options, and a ton of other weird stuff. Overall, it seemed like it somehow only installed half the system since it felt like it was missing a lot of options and features. Tried reflashing the full factory image which did not seem to help. Only was able to get it functioning again through a clean install. No clue as to what could've happened this time around.
Click to expand...
Click to collapse
Oh no, please don't tell me you flashed any of the files from this thread? They're very different phones in that sense and you need to use the correct files. We just put the little guy down to sleep so I'll write up that thread really quick on the P4 forums. Flashing a full factory image is pretty much the same as a clean install though? Are you sure you were using the correct files? Anyway, the post for P4 will be up in just a few min. (I'm actually updating my wife's phone as I type this, lol)
edit: here ya go: https://forum.xda-developers.com/pixel-4/how-to/update-root-guide-jun-2020-qq3a-200605-t4109307
onlyguynamedniles said:
Copy and pasted method, just as you did in previous month. Your EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS is flawless for me.
Click to expand...
Click to collapse
Thanks for the feedback, you're welcome!
i5lee8bit said:
Oh no, please don't tell me you flashed any of the files from this thread? They're very different phones in that sense and you need to use the correct files. We just put the little guy down to sleep so I'll write up that thread really quick on the P4 forums. Flashing a full factory image is pretty much the same as a clean install though? Are you sure you were using the correct files? Anyway, the post for P4 will be up in just a few min. (I'm actually updating my wife's phone as I type this, lol)
Click to expand...
Click to collapse
No worries, mate. I used my own files. Downloaded many times just to make sure I had the right package. Still not really sure what happened as flashing the factory images should have fixed whatever was going on. Not an ideal situation, but works out since I had to do a factory reset to fix a separate backup issue anyway.
tysj said:
No worries, mate. I used my own files. Downloaded many times just to make sure I had the right package. Still not really sure what happened as flashing the factory images should have fixed whatever was going on. Not an ideal situation, but works out since I had to do a factory reset to fix a separate backup issue anyway.
Click to expand...
Click to collapse
Lol, I edited the post with the link to the other thread right after you responded I guess. Anyway, yeah, that's weird. Could be the cable, corrupt files, or a big number of things. Glad you got it sorted out though! :good:
Thanks for this. I've been following your guide the last few months since its brainless work for me. I checked for your thread yesterday but it wasn't up yet so didn't bother updating. I will tonight but thought I'd say thank you for the guide in advanced - its much appreciated
@i5lee8bit
Thx for your answer i ll try a bit more on my own
baleskoil said:
@i5lee8bit
Thx for your answer i ll try a bit more on my own
Click to expand...
Click to collapse
Hey what modules are you using? Try booting up in Magisk Core Only Mode (or just try disabling all modules and reboot). You can easily boot in core mode if you're not bootlooping by just going to Magisk Manager settings and toggling core only mode. The only thing I could think of is a module not playing nicely, especially if it works when stock. Either that, or maybe there's something you need to Magisk Hide. The only things I have hidden are the stuff recommended in eg1122's thread (https://forum.xda-developers.com/pixel-4-xl/how-to/xposed-discussion-thread-t3992607) plus a few extra things like Netflix and some banking apps. But seeing as how it works when stock for you, it's definitely not hardware related so I would suspect another tweak messing with it. Good luck!
Edit/PS: I got curious this morning and tried on my own phone, and all motion sense functions still work, btw
ouch ...dumb mistake.... I was so focused on passing safetynet i forgot about magisk hide ^^
thx for your help ^^
"** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images"
Does this mean I only need to flash the boot.img and not the dtbo.img if I'm using the stock kernel?
knudsen83 said:
"** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images"
Does this mean I only need to flash the boot.img and not the dtbo.img if I'm using the stock kernel?
Click to expand...
Click to collapse
Correct, I'm guessing you already got it sorted out by now but in case you're wonderinf it wouldn't hurt to flash stock dtbo over stock dtbo either.
Got a brand new KB2005
I haven't put in a SIM Card yet; haven't even connected it to my Google account (I want to get everything set up first)
So, my first actions were to unlock the bootloader, and root the phone using Magisk.
Build number Oxygen OS 11.0.8.13.KB05AA
My phone won't connect to wifi.
If I go to Wifi Settings, Wifi is off.
If I turn it on, it shuts itself off again.
Wifi was working before I rooted, because it has 1 saved network.
Is this a known issue - no wifi without a Sim - or is something wrong?
Any troubleshooting tips?
Thanks in advance!
sounds similar to this
solved: lost wifi while rooting, can I reflash modem and get it back?
So I updated to 11.0.08.14.KB05BA. I then rooted using the guide here, via Magisk Rooted, everything works, except: My wifi connection will not turn on (let alone connect). I hit the wifi icon, it "turns on" and then "turns off" I go to the wifi...
forum.xda-developers.com
Darn.
I tried to be extremely careful to match the version/build.
So how do I revert/repair it?
Better use "dd" command in modified recovery or use Payload Dumper get boot.img directly form your system or full update.zip.
Otherwise very easy got mistake, the source may be wrong in the first place.
You can use same version full update.zip update again, or fastboot flash the correct boot.img.
My magisk patched boot.img from 11.0.8.13 KB05AA.
img MD5: 8d:60:d9:38:6d:f4:f1:2d:16:59:a6:a1:e0:4d:13:70
ULTRAJC said:
My magisk patched boot.img from 11.0.8.13 KB05AA.
img MD5: 8d:60:d9:38:6d:f4:f1:2d:16:59:a6:a1:e0:4d:13:70
Click to expand...
Click to collapse
Thank you VERY much - that worked!
cheshyre said:
Thank you VERY much - that worked!
Click to expand...
Click to collapse
If you have to use online source patched boot.img, don't flash, only do "fastboot boot boot.img", if it can successfully boot into the system, then use magisk patch current system boot.img and reboot.
ULTRAJC said:
If you have to use online source patched boot.img, don't flash, only do "fastboot boot boot.img", if it can successfully boot into the system, then use magisk patch current system boot.img and reboot.
Click to expand...
Click to collapse
Sorry, saw this too late.
Was about to post a new Q because I can't install the OTA update, but maybe you know the answer?
Download and install update returns "Installation problem"
In Magisk, Uninstall Magisk > Restore Images says "Stock backp does not exist"
Help me, Obi-Wan Kenobi...
fwiw, I haven't yet done much customizing of my device, so if it's easiest to just wipe everything and start fresh, I can do that.
cheshyre said:
Sorry, saw this too late.
Was about to post a new Q because I can't install the OTA update, but maybe you know the answer?
Download and install update returns "Installation problem"
In Magisk, Uninstall Magisk > Restore Images says "Stock backp does not exist"
Help me, Obi-Wan Kenobi...
Click to expand...
Click to collapse
Incremental update requires the system has not been modified, and little tricky, do not directly patch inactive slot befor reboot, let upgrade process boot up system say successful, then patch.
Original boot.img (11.0.8.13 KB05AA):
MD5: 75ba083950c2a75c6b423442ef2dfc37
Thank you very very VERY much for all your help.
Finally got the phone rooted, and while I'm still configuring some of my apps & settings, I couldn't've gotten this far without your assistance.
I'm not sure why i have Magisk installed in a way that it cannot find the stock boot image, but that seems to be the case.
a quick search didn't turn up the stock boot image for my existing ROM version (IN2025_11_f.15)
I figure it may be easier to just update and lose root, then re-root with the new boot image, but I've had some issues doing what I thought would be easy, but turned into big issues, so before I start down this path, I wanted to ask what may be the best way to go from where I am...
(rooted with Magisk, but no stock boot.img, running build number IN2025_11_F.15, Baseband version Q_V1_P14)
...to getting onto the latest version my phone is offering (IN2025_11.F.62_2620_202301162204) and get Magisk fixed so that it then has a stock boot image, so I can update later by just uninstalling/restoring images, installing the update, then rebooting to the inactive slot, which worked fine for years.
Thanks in advance for any help/guidance doing so.
JustinChase said:
I'm not sure why i have Magisk installed in a way that it cannot find the stock boot image, but that seems to be the case.
a quick search didn't turn up the stock boot image for my existing ROM version (IN2025_11_f.15)
I figure it may be easier to just update and lose root, then re-root with the new boot image, but I've had some issues doing what I thought would be easy, but turned into big issues, so before I start down this path, I wanted to ask what may be the best way to go from where I am...
(rooted with Magisk, but no stock boot.img, running build number IN2025_11_F.15, Baseband version Q_V1_P14)
...to getting onto the latest version my phone is offering (IN2025_11.F.62_2620_202301162204) and get Magisk fixed so that it then has a stock boot image, so I can update later by just uninstalling/restoring images, installing the update, then rebooting to the inactive slot, which worked fine for years.
Thanks in advance for any help/guidance doing so.
Click to expand...
Click to collapse
Does it work if you try to update without unrooting?
JustinChase said:
I'm not sure why i have Magisk installed in a way that it cannot find the stock boot image, but that seems to be the case.
<snip>
Click to expand...
Click to collapse
That happens if you flash a Magisk patched boot image instead of booting it and then using direct install.
TheNewHEROBRINE said:
Does it work if you try to update without unrooting?
Click to expand...
Click to collapse
No. I think the update isn't a full ROM. I believe read somewhere that works when the update is a full ROM
I'm just not sure how to 'start over' to get a stock image saved so Magisk will let me restore again, without having to wipe the phone.
JustinChase said:
No. I think the update isn't a full ROM. I believe read somewhere that works when the update is a full ROM
I'm just not sure how to 'start over' to get a stock image saved so Magisk will let me restore again, without having to wipe the phone.
Click to expand...
Click to collapse
White don't you ask in the 8/8 Pro (I'm assuming that's what you have) forums if someone can provide you with a stock boot image for your current OOS version?
Note that this is an 8T forum so you don't get people here providing you with a copy.
BillGoss said:
White don't you ask in the 8/8 Pro (I'm assuming that's what you have) forums if someone can provide you with a stock boot image for your current OOS version?
Note that this is an 8T forum so you don't get people here providing you with a copy.
Click to expand...
Click to collapse
Oh, sorry.
I did think this was an 8 Pro forum
I'll find that and repost
Thanks