Related
I got update from oero to pie via OTA today,
I tried many patched boot.img and root maunally by patching stock img but its stuck on boot screen.. Any idea??
Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.
Hakkinan said:
Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.
Click to expand...
Click to collapse
What's mean " in both slots " ?
I tried to patch boot.img maunally but my device stuck on boot animations, So I flashed back stock boot.img into fastboot without root agian..
This is an A/B device which means that it has two slots for every partition (A and B). You need to flash the stock boot in the same partirion that it currently being used, flashing It in both is just to be safe in future updates.
Oh hey try this one: https://drive.google.com/file/d/1dBX2dZV_wWgSip8d9lk0lrO_JHfxGdKU/view?usp=sharing
Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.
FRibeiro1400 said:
Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.
Click to expand...
Click to collapse
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?
FRibeiro1400 said:
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?
Click to expand...
Click to collapse
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"
Hakkinan said:
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"
Click to expand...
Click to collapse
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?
HaN5aR said:
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?
Click to expand...
Click to collapse
Wait, did you try to flash the whole OTA?
Hakkinan said:
Wait, did you try to flash the whole OTA?
Click to expand...
Click to collapse
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations
Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?
HaN5aR said:
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations
Click to expand...
Click to collapse
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
FRibeiro1400 said:
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?
Click to expand...
Click to collapse
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.
Hakkinan said:
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.
Click to expand...
Click to collapse
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.
FRibeiro1400 said:
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.
Click to expand...
Click to collapse
Doesn't matter if you had 10.0.1.0 previously or not. You can download it and install it without losing data.
I just flashed the full image (flashall removed the -w) and attempted the magisk boot.img patch that I've been doing since the phone was released for months now. I'm on Magisk canary up to date (7.4.1-72edbfc4 (260)). When I patch the boot.img and reflash it as magisk_patched.img I just get a bootlooping Google logo. I flashed back to stock boot.img and tried again...... Same thing.
Is anyone else able to root via Magisk patching the boot.img file?
DriveEuro said:
I just flashed the full image (flashall removed the -w) and attempted the magisk boot.img patch that I've been doing since the phone was released for months now. I'm on Magisk canary up to date (7.4.1-72edbfc4 (260)). When I patch the boot.img and reflash it as magisk_patched.img I just get a bootlooping Google logo. I flashed back to stock boot.img and tried again...... Same thing.
Is anyone else able to root via Magisk patching the boot.img file?
Click to expand...
Click to collapse
Hello could u give me boot.img plz already installed but via OTA so i dont have the file i want to patch it wih magisk for root :crying:
rafik25 said:
Hello could u give me boot.img plz already installed but via OTA so i dont have the file i want to patch it wih magisk for root :crying:
Click to expand...
Click to collapse
https://developers.google.com/android/images
Download the factory image from here. Extract out the boot.img file.
DriveEuro said:
https://developers.google.com/android/images
Download the factory image from here. Extract out the boot.img file.
Click to expand...
Click to collapse
Bro for december ? i see only November
rafik25 said:
Bro for december ? i see only November
Click to expand...
Click to collapse
10.0.0 (QQ1A.191205.011, Dec 2019)
Listed right at the bottom for bonito section.
DriveEuro said:
10.0.0 (QQ1A.191205.011, Dec 2019)
Listed right at the bottom for bonito section.
Click to expand...
Click to collapse
Thx boot.img already patched :good:
I ended up wiping my device and flashing stock Dec image. :-/
DriveEuro said:
I just flashed the full image (flashall removed the -w) and attempted the magisk boot.img patch that I've been doing since the phone was released for months now. I'm on Magisk canary up to date (7.4.1-72edbfc4 (260)). When I patch the boot.img and reflash it as magisk_patched.img I just get a bootlooping Google logo. I flashed back to stock boot.img and tried again...... Same thing.
Is anyone else able to root via Magisk patching the boot.img file?
Click to expand...
Click to collapse
I've had this happen to me before. However it was always when I moved the wrong file patched file from the phone to the computer and therefore I flashed the wrong file to the phone which obviously causes a bootloop.
For some reason when this happened, the patched file didn't immediately show up in the Android. I know this because I checked the file and it had a modified date of a month earlier (from the last update). After a while (perhaps a reboot), the new file showed up (overwriting the old file), but with the correct modified date. I took that file and moved it to the computer and flashed it without any issues.
I can't tell you why this occurred, but I am 95% positive you experienced the same thing. You followed the directions correctly and thought you were flashing the latest modified boot image, but I bet it was really the old file.
sic0048 said:
I've had this happen to me before. However it was always when I moved the wrong file patched file from the phone to the computer and therefore I flashed the wrong file to the phone which obviously causes a bootloop.
For some reason when this happened, the patched file didn't immediately show up in the Android. I know this because I checked the file and it had a modified date of a month earlier (from the last update). After a while (perhaps a reboot), the new file showed up (overwriting the old file), but with the correct modified date. I took that file and moved it to the computer and flashed it without any issues.
I can't tell you why this occurred, but I am 95% positive you experienced the same thing. You followed the directions correctly and thought you were flashing the latest modified boot image, but I bet it was really the old file.
Click to expand...
Click to collapse
I checked the time/date stamps each time and they were definitely from today. Doesn't matter much at this point because I already flashed back to stock rom. Was able to room there. Have no clue why I had this problem. I've been on the 3a since the week it came out and I've been flashing pactched boot images nearly just as long too. Oh well.
DriveEuro said:
I checked the time/date stamps each time and they were definitely from today. Doesn't matter much at this point because I already flashed back to stock rom. Was able to room there. Have no clue why I had this problem. I've been on the 3a since the week it came out and I've been flashing pactched boot images nearly just as long too. Oh well.
Click to expand...
Click to collapse
Weird. At least you got it fixed. That's why I love the Pixel phones. They are virtually impossible to brick (as long as the bootloader is unlocked).
DriveEuro said:
I just flashed the full image (flashall removed the -w) and attempted the magisk boot.img patch that I've been doing since the phone was released for months now. I'm on Magisk canary up to date (7.4.1-72edbfc4 (260)). When I patch the boot.img and reflash it as magisk_patched.img I just get a bootlooping Google logo. I flashed back to stock boot.img and tried again...... Same thing.
Is anyone else able to root via Magisk patching the boot.img file?
Click to expand...
Click to collapse
Patching the boot IMG with magisk worked for me no problem
I am having the same issue. I was able to root with a magisk patched boot.img from the November update, but I go into a bootloop when using a magisk patched boot.img from the December update. I have reverted back to the non patched root.img for December. I would love to have it patched though.
Can someone share a patched boot.img for december?
Not sure if youre interested in a custom kernel but youre welcome to to my latest build which is pre-rooted.
mxrodriguez said:
I am having the same issue. I was able to root with a magisk patched boot.img from the November update, but I go into a bootloop when using a magisk patched boot.img from the December update. I have reverted back to the non patched root.img for December. I would love to have it patched though.
Can someone share a patched boot.img for december?
Click to expand...
Click to collapse
You must be doing something wrong because it worked for me no problem. I have the December boot.img patched on my computer. I can upload it if you want?
thatsupnow said:
You must be doing something wrong because it worked for me no problem. I have the December boot.img patched on my computer. I can upload it if you want?
Click to expand...
Click to collapse
That would be great.
I can give it a try and flash your patched boot.img.
Im using Magisk 20.1 right now but it doesnt seem to be working
mxrodriguez said:
That would be great.
I can give it a try and flash your patched boot.img.
Im using Magisk 20.1 right now but it doesnt seem to be working
Click to expand...
Click to collapse
Here you go https://drive.google.com/file/d/1253hD26lHFQMhUJZ5_Fu6rLZLr1tLq7k/view?usp=drivesdk
I was able to root the December update but I wipe and flash the whole image, not just the ota
thatsupnow said:
Here you go https://drive.google.com/file/d/1253hD26lHFQMhUJZ5_Fu6rLZLr1tLq7k/view?usp=drivesdk
Click to expand...
Click to collapse
Tried my patched file and yours still getting the looped google logo. Been sitting there for about 10 minutes and nothing. Reflashing the stock boot allows the phone to boot but its unrooted and with TWRP unsupported this is the only method.
I had no idea the android Q update downloaded and would automatically install when I rebooted my phone. I just want my root back. Looks like I'll have to flash stock and retry. Since I dont have root and can't use Titantium Backup any one know any decent alternatives?
thatsupnow said:
Here you go https://drive.google.com/file/d/1253hD26lHFQMhUJZ5_Fu6rLZLr1tLq7k/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks @thatsupnow
I finally got around to trying your patched file and I continue to get into the G-logo bootloop.
Not sure why I cant patch the December update. I was able to patch the Nov update and get root so hopefully it will work on the the Jan update. At least I know Im not crazy since I dont seem to be the only one with this problem. I have not tried wiping everything and trying to apply the patched boot img since it shouldnt be needed.
Im back to stock non-root on this December patch.
Hopefully the next one will work for me.
Thanks
mxrodriguez said:
Thanks @thatsupnow
I finally got around to trying your patched file and I continue to get into the G-logo bootloop.
Not sure why I cant patch the December update. I was able to patch the Nov update and get root so hopefully it will work on the the Jan update. At least I know Im not crazy since I dont seem to be the only one with this problem. I have not tried wiping everything and trying to apply the patched boot img since it shouldnt be needed.
Im back to stock non-root on this December patch.
Hopefully the next one will work for me.
Thanks
Click to expand...
Click to collapse
Yes its quite frustrating I think I may also wait.
so i updated to OOS 10.0.9 Global on HD1900(China), but there is no patched boot or fastboot rom yet, so i patched it with his guide: guide by @gpz110
Boot.img patched with MAGISK 20.4 on OOS 10.0.9 HD65AA (GLOBAL)
Only for OOS 10.0.9 Global!!!!
Enjoy!
Instructions:
reboot to fastboot
Code:
adb reboot bootloader
Code:
fastboot boot magisk_patched_10_0_9.img
let it boot and check if u have root
if u got root then reboot to fastboot again
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched_10_0_9.img
patched boot.img download: https://drive.google.com/file/d/1mHbDV0t_TKrhV2XqT7YySoHsl8623Bc4/view?usp=sharing
stock boot.img download: https://drive.google.com/file/d/1RzUHNfp0Zns2FrfOHA9mwoDW9BKKeZVH/view?usp=sharing
My model is an HD 1905 but my current build number is 10.0.9 HD65AA... I bought it directly from OnePlus it's a 7T. Is this the boot image I need? I spent hours looking all over in different boot images patched with magisk. I haven't even unlocked my bootloader yet because I'm not sure what my options are... Lol also I noticed you have the patched boot image and a stock boot image I said just in case something goes wrong?
Sent from my OnePlus7T using XDA Labs
groovemetal81 said:
My model is an HD 1905 but my current build number is 10.0.9 HD65AA... I bought it directly from OnePlus it's a 7T. Is this the boot image I need? I spent hours looking all over in different boot images patched with magisk. I haven't even unlocked my bootloader yet because I'm not sure what my options are... Lol also I noticed you have the patched boot image and a stock boot image I said just in case something goes wrong?
Sent from my OnePlus7T using XDA Labs
Click to expand...
Click to collapse
it should work, but first u need an unlocked bootloader...
u can test it as described with the first and second step("fastboot boot" command only boot once, if u get bootloop, just restart and your device will boot as usual) , if it boot and u got root with no problems, then u can finish the process with the third and fourth step
boot image patched for EU version is possible 10.0.9.HD65BA ?
Yeah I just upgraded from a 6t and that was capable of a custom recovery but I'd run into trouble all the time because of the dual partition.. so that patched boot image with magisk all's I need is the APK file 7.51 correct I shouldn't need the magisk 24 .0zip
Sent from my OnePlus7T using XDA Labs
EmiRap said:
boot image patched for EU version is possible 10.0.9.HD65BA ?
Click to expand...
Click to collapse
check my tool here
Thx Thx Thx it worked properly
Thanks. Worked like a charm. The only thing is that I cannot find Advanced option and SafetyNet check is missing in Magisk Manager like I had previously in my OP6T. Also, with this root Google Pay and the likes work, as I also do not see Magisk Hide, but did enalbe in Settings. Thumbs up.
Update: Seems like WiFi is not working now! Any tips?
EazyVG said:
Thanks. Worked like a charm. The only thing is that I cannot find Advanced option and SafetyNet check is missing in Magisk Manager like I had previously in my OP6T. Also, with this root Google Pay and the likes work, as I also do not see Magisk Hide, but did enalbe in Settings. Thumbs up.
Update: Seems like WiFi is not working now! Any tips?
Click to expand...
Click to collapse
Are you sure, that you are on OOS 10.0.9 Global?
To revert back to stock boot image, grab the boot image from a fastboot rom here
be sure to grab the right one!
Definitely it is 10.0.9 HD65AA (GLOBAL) which I got over OTA. But I'll download the one from link again and update locally and then again re-run the steps for root.
Update: Reinstalled 10.0.0.9 and the steps ... all working, no above mentioned issues now. Thanks!
I did the whole steps but the phone application continues to stop and then the data network does not work What is the problem I have updated wirelessly to 1009
AboNaya said:
I did the whole steps but the phone application continues to stop and then the data network does not work What is the problem I have updated wirelessly to 1009
Click to expand...
Click to collapse
Did you already flashed or just booted the image?
HD1905BA Europe Patched boot
10.0.9 HD1905BA (Europe)
Stock boot : drive.google.com /file/d/1yyfzh6HbjrdZG3WDeyTv1d04fBgX3yzl/view?usp=sharing[/url]
Patched boot: drive.google.com /file/d/1ZCX7CWpRX-sZrb_ICOg64q2Abdumynmf/view?usp=sharing
guys!
Just a quick question: does this method pass the safetyNet check?
KyoshiDev said:
Did you already flashed or just booted the image?
Click to expand...
Click to collapse
I think I'll second his problem. I did first couple steps, confirmed root, everything seemed ok. Reboot and performed remaining steps. Now I have major stability problems. System UI eventually FCs then phone restarts. I'm able to get to settings and check version, still shows OOS 10.0.8 HD65AA. The signal bars showed no bars but LTE+ logo. Running another app called Signal Check Pro I confirmed that I had data. It seemed to get more stable the more it booted. The updater still wants to do a full update and wipe, it detects root and says that doing the full upgrade will lose root. I'm probably going to let mine do the full update and then reroot.
How did you patch the image? I get a non working patched boot.img when using the latest version of Magisk Manager.
AboNaya said:
I did the whole steps but the phone application continues to stop and then the data network does not work What is the problem I have updated wirelessly to 1009
Click to expand...
Click to collapse
im having a similar problem, after full ota update (2.6gb) from rooted 10.0.8 im losing mobile network (two SIM icon, greyed out, with a slash sign over it and no baseband infromation) after booting/flashing this boot, even creating mine. Mobile network restores after returning to stock. any clue? Im on 10.0.9.HD65AA
Sacob said:
guys!
Just a quick question: does this method pass the safetyNet check?
Click to expand...
Click to collapse
Yes
Nice Work with that .bat file
It works on Oneplus 7t 10.0.9Hd65BA. EU
Thanks for that super cool tool
To others that need to root a Oneplus 7t 10.0.9Hd65BA. EU i share my magisk boot file whit you all
#drive.google.com/open?id=1vGlNWrw2JAXmtb2ibst2BEQhKCM5ceMl #
Download the file an follow the guide in #1
Hi, I've just received my OP7t Global HD1900.
I installed OTA 10.0.9 and already unlocked the bootloader.
Please, does TWRP recovery work on this phone with 10.0.9? If not, which recovery should I use?
Do I have to flash a patched boot.img to get the phone rooted?
I used the boot image and it rooted my phone..great and many thanks!
Now...which recovery should I flash?
Thanks..
Hi,
I use a RMX2063 since last month, rooted with the TWRP method I found in this forum since day 0. I tried to install the lastest OTA update, that was released last week (RMX2063 _11_A.22), but I have issues to keep magisk working.
Either I do a clean install or a dirty flash, I enter into a bootloop every time I flash lastest magisk version (20.4). Otherwise, the phone works OK if I reflash the OTA and use it without rooting.
Any solutions to that, so I don´t have to downgrade the phone?
Jpigas said:
Hi,
I use a RMX2063 since last month, rooted with the TWRP method I found in this forum since day 0. I tried to install the lastest OTA update, that was released last week (RMX2063 _11_A.22), but I have issues to keep magisk working.
Either I do a clean install or a dirty flash, I enter into a bootloop every time I flash lastest magisk version (20.4). Otherwise, the phone works OK if I reflash the OTA and use it without rooting.
Any solutions to that, so I don´t have to downgrade the phone?
Click to expand...
Click to collapse
It doesn't work. In order for me to get root afterwards is to flash the latest for rmx2061, extract the boot.img, modify it with magisk and flash the modified boot.img afterwards
mepadiernos said:
It doesn't work. In order for me to get root afterwards is to flash the latest for rmx2061, extract the boot.img, modify it with magisk and flash the modified boot.img afterwards
Click to expand...
Click to collapse
First of all, thx for the quick response.
I think I already tried that, you mean flashing the modified boot.img via TWRP? (install -> install image -> "boot")?
After that I had another bootloop ("system image is destroyed" realme message)
Jpigas said:
First of all, thx for the quick response.
I think I already tried that, you mean flashing the modified boot.img via TWRP? (install -> install image -> "boot")?
After that I had another bootloop ("system image is destroyed" realme message)
Click to expand...
Click to collapse
I was actually referring to flashing via fastboot.
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
mepadiernos said:
I was actually referring to flashing via fastboot.
Click to expand...
Click to collapse
The phone enters bootloop anyway (system destroyed), but thank you anyway @mepadiernos. Any other idea?
Jpigas said:
The phone enters bootloop anyway (system destroyed), but thank you anyway @mepadiernos. Any other idea?
Click to expand...
Click to collapse
Hmmm, I do remember that the twrp provided here for the Realme 6 Pro breaks encryption after I upgraded to .27 so I had to flash the .20 for rmx2061 via stock recovery. I had to put the ozip in the microsd. I believe that will factory reset the phone. When it does I went through the process of setting up my phone sans root. I installed magisk manager and proceeded to patch the extracted boot image from the ozip, the update for the rmx2061, and flashing via fastboot. So, I have root but no twrp.
mepadiernos said:
Hmmm, I do remember that the twrp provided here for the Realme 6 Pro breaks encryption after I upgraded to .27 so I had to flash the .20 for rmx2061 via stock recovery. I had to put the ozip in the microsd. I believe that will factory reset the phone. When it does I went through the process of setting up my phone sans root. I installed magisk manager and proceeded to patch the extracted boot image from the ozip, the update for the rmx2061, and flashing via fastboot. So, I have root but no twrp.
Click to expand...
Click to collapse
It doesn´t worked for me, buy, anyway, I´m planning to downgrade due to the very high power consumption. Nowadays the phone struggles to reach 3-4h screen on, versus the 6h I managed to reach on previous version. What do you guys think about it?
Just got the march security update. 490mb.
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
swieder711 said:
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
Click to expand...
Click to collapse
My phone went into bootloop today after updating Magisk (magisk update prompt), BEFORE march update. That was a bit odd. Maybe your bootloop has nothing to do with March update, but with the new magisk version being flashed is incompatible to certain modules.
Well hell, I am failing.....and understand the message, but dont understand why or what transpired....and not sure what bootloader the message refers to.....this is a factory flash....
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'slider-1.0-8062051'.
Update requires 'slider-1.1-8118264'.
fastboot: error: requirements not met!
Hmm, now not exactly sure what to do....8062051 is the bootloader from the 2nd February image, so not sure where to get 8118264 so I can update.......very odd.
***EDIT: OK I see thats the bootloader from A12L not from A12.......wtf!!!!
****RE-EDIT: PEBCAK here on my end.....doh! Working now
Same here, just checked and it showed up.
I was running into issues flashing the Factory image via Fastboot so I decided to try the FLASH method from the Android Flash Tool. That worked. But when I try to install the Magisk patch file, it fails and then I get stuck in a bootloop. So there you have it. I'm going to have to deal with no root until someone figures out what's going on.
swieder711 said:
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
Click to expand...
Click to collapse
Once I disabled the Typhus ROM Control module in Magisk then my phone booted with root enabled with 24.304. Magisk stable probably works too.
TimFlex said:
Just got the march security update. 490mb.
Click to expand...
Click to collapse
This in more in line with the following thread which is where you need to bring this discussion. We really don't need another misleading thread that is merely a Magisc "how do I...?"
April 10, 2023 TQ2A.230405.003.E1 Global - Root Pixel 6 Pro [Raven] / all relevant links
Pixel 6 Pro [Raven] March 9, 2023 I recommend sticking with 33.0.3. Note that two users in my Pixel 7 Pro thread have said that 34.0.1 did not work correctly for them. Someone reported it to Google (added a comment about 34.0.1 to the existing...
forum.xda-developers.com
Same issue here. Flashed March factory image. No wipe flag. Flashed Magisk patched file. Stuck in bootloop.
Reflashed factory image and didn't flash boot image and I can boot up. I guess no root until this is fixed.
I downloaded the March Factory zip and transferred the boot.img to my phone and then patched it with Magisk Stable v24.3 (I transferred the patched boot.img back to Platform TooIs Folder on PC) I tried to fastboot flash the March OTA (would only get to 48% and fail) So I used the Android Flash Tool and let it install the factory image without wiping. Now on March build with no data loss I then fastboot flashed the patched boot.img and have root
I had the same problem with Feb v2 OTA sideload (Maybe because I had a custom kernel?) anyway, I think the Android Flash Tool will be my go to for future updates
jcp2 said:
I downloaded the March Factory zip and transferred the boot.img to my phone and then patched it with Magisk Stable v24.3 (I transferred the patched boot.img back to Platform TooIs Folder on PC) I tried to fastboot flash the March OTA (would only get to 48% and fail) So I used the Android Flash Tool and let it install the factory image without wiping. Now on March build with no data loss I then fastboot flashed the patched boot.img and have root
I had the same problem with Feb v2 OTA sideload (Maybe because I had a custom kernel?) anyway, I think the Android Flash Tool will be my go to for future updates
Click to expand...
Click to collapse
Can you upload your patched file by any chance?
tonyfiore75 said:
Can you upload your patched file by any chance?
Click to expand...
Click to collapse
This is for Magisk Stable - Not Canary!!
Thesis so much @jcp2 !
Does the uninstall Magisk, OTA, and then reinstall Magisk work with this update? If so, what version of Magisk do we know that works?
Last time I lost everything on my phone. Not trying to do that again.
mkhcb said:
Does the uninstall Magisk, OTA, and then reinstall Magisk work with this update? If so, what version of Magisk do we know that works?
Last time I lost everything on my phone. Not trying to do that again.
Click to expand...
Click to collapse
Edit>>>> As long as you're on stock kernel, Canary is fine.
jcp2 said:
IDK but 100% sure to stay on Magisk Stable and not Canary --- Canary will cause bootloops!
Click to expand...
Click to collapse
I rolled back to Stable and still cannot gain back root....
I sideloaded the March OTA then rooted successfully with 24.3, but I didn't do the magisk uninstall.
jcp2 said:
IDK but 100% sure to stay on Magisk Stable and not Canary --- Canary will cause bootloops!
Click to expand...
Click to collapse
Not accurate. Using latest Canary (24304) and updated fine. Sideloaded ota in recovery, reboot to let system update complete, reboot to bootloader and flashed patched boot.img. All is fine.
did you try the patched boot.img I uploaded a few posts back? Make sure you're on March update with Magisk 24.3 stable before flashing.