Anyone else having this issue after fastboot the March factory image, I was rooted with Magisk on the January firmware.
tatico28 said:
Anyone else having this issue after fastboot the March factory image, I was rooted with Magisk on the January firmware.
Click to expand...
Click to collapse
Did you uninstall Magisk or disable the magisk modules before you flashed the March 2020 factory image?
Homeboy76 said:
Did you uninstall Magisk or disable the magisk modules before you flashed the March 2020 factory image?
Click to expand...
Click to collapse
No, I did not, is there a workaround?
tatico28 said:
No, I did not, is there a workaround?
Click to expand...
Click to collapse
No it is not a workaround, strange things happen when you don't at least disable all magisk modules before you flash a Factory update. Why some modules must be updated to work with the March Factory image. Use this Guide: Do #4 'keep data' then do #9 to root.
Homeboy76 said:
No it is not a workaround, strange things happen when you don't at least disable all magisk modules before you flash a Factory update. Why some modules must be updated to work with the March Factory image. Use this Guide: Do #4 'keep data' then do #9 to root.
Click to expand...
Click to collapse
Thanks for your response, updating the Tools module made the difference, since I`ve tried to fastboot flash the factory image twice with the old tools version, I did not know that the March update came with this bag of treats lol.
tatico28 said:
Thanks for your response, updating the Tools module made the difference, since I`ve tried to fastboot flash the factory image twice with the old tools version, I did not know that the March update came with this bag of treats lol.
Click to expand...
Click to collapse
Hi, what do you mean updating the tools module? tnks
davidvd102dvd said:
Hi, what do you mean updating the tools module? tnks
Click to expand...
Click to collapse
I think he's referring to SDK platform-tools.
Homeboy76 said:
I think he's referring to SDK platform-tools.
Click to expand...
Click to collapse
i though the same but tried without success
davidvd102dvd said:
i though the same but tried without success
Click to expand...
Click to collapse
Ok, then this must be what he is talking about: https://pixelrepair.withgoogle.com/carrier_selection
Yes the SDK Platform- tools, also I had to fastboot flash the boot.img to both a,b slots.
Homeboy76 said:
No it is not a workaround, strange things happen when you don't at least disable all magisk modules before you flash a Factory update. Why some modules must be updated to work with the March Factory image. Use this Guide: Do #4 'keep data' then do #9 to root.
Click to expand...
Click to collapse
bro just disable the modules is enough or do we have to flash the stock boot too? @tatico28
alwynjoshy said:
bro just disable the modules is enough or do we have to flash the stock boot too? @tatico28
Click to expand...
Click to collapse
If you are going to do #4 and you are rooted, do this first:
- Open Magisk Manager
- Tap modules uncheck all the modules that have a checkmark (tap the ✓).
- Reboot to deactivate the modules
- Open Magisk Manager
- Tap Uninstall
- Tap Restore images (unroots your phone by restoring/flashing stock boot images).
- Do #4 'keep data'
Homeboy76 said:
If you are going to do #4 and you are rooted, do this first:
- Open Magisk Manager
- Tap modules uncheck all the modules that have a checkmark (tap the ✓).
- Reboot to deactivate the modules
- Open Magisk Manager
- Tap Uninstall
- Tap Restore images (unroots your phone by restoring/flashing stock boot images).
- Do #4 'keep data'
Click to expand...
Click to collapse
Restore images failed says no image found. So i disabled all modules and rebooted then flashed stock image booted up. The i went bootloader and flashed march OTA. Booted up But still touch is not responsive
alwynjoshy said:
Restore images failed says no image found. So i disabled all modules and rebooted then flashed stock image booted up. The i went bootloader and flashed march OTA. Booted up But still touch is not responsive
Click to expand...
Click to collapse
A factory reset may be your only option then. Have you tried switching your slots and then fastboot the factory image without the -w so as not to loose data?
Badger50 said:
A factory reset may be your only option then. Have you tried switching your slots and then fastboot the factory image without the -w so as not to loose data?
Click to expand...
Click to collapse
I only use a slot only, didn't try swift slots but i try to go recovery mode to sideload the zip. A error state "NO COMMAND FOUND" AND SHOWS A DEAD ANDROID WITH STOMACH OPENED
alwynjoshy said:
I only use a slot only, didn't try swift slots but i try to go recovery mode to sideload the zip. A error state "NO COMMAND FOUND" AND SHOWS A DEAD ANDROID WITH STOMACH OPENED
Click to expand...
Click to collapse
Update the SDK Platform Tools, flash March factory img. without -w if you don`t want to erase your data, extract boot.img from image.zip, fastboot flash boot.img to both slots and you should be ok.
tatico28 said:
Update the SDK Platform Tools, flash March factory img. without -w if you don`t want to erase your data, extract boot.img from image.zip, fastboot flash boot.img to both slots and you should be ok.
Click to expand...
Click to collapse
I tried the way you said but same result. The only thing i didn't do is i flashed only slot A only. But my active slot is A so i think that is not the issue
alwynjoshy said:
I only use a slot only, didn't try swift slots but i try to go recovery mode to sideload the zip. A error state "NO COMMAND FOUND" AND SHOWS A DEAD ANDROID WITH STOMACH OPENED
Click to expand...
Click to collapse
Thats just the stock recovery screen. Hold the power button down, and then tap the volume up button once. Then you'll be stock recovery :good:
Badger50 said:
Thats just the stock recovery screen. Hold the power button down, and then tap the volume up button once. Then you'll be stock recovery :good:
Click to expand...
Click to collapse
Is both sideload and run flash-all.bat give the same functionality to flash or it will be different way to flash the OTA
alwynjoshy said:
Is both sideload and run flash-all.bat give the same functionality to flash or it will be different way to flash the OTA
Click to expand...
Click to collapse
It's a matter of choice really. Many, like myself, like to fastboot the factory images every month to update. Others like the OTA. Functionality is pretty much the same as far as I've seen. However, you can't fastboot an OTA, likewise you can't side load a factory image, and of course, you have to be bootloader unlocked to fastboot the factory images, so keep that in mind as well. I also like using fastboot because you can switch slots to sometimes get rid of errors that occasionally pop up. Good luck with finding your solution whichever way you choose to go. :good:
Related
There Is No TWRP Until Now As Its Been Just 4 Days. But We Don't Need TWRP When We Have Magisk . What I Did :-
1:- Downloaded The Stock Boot Image From Github
2:- Downloaded Latest Magisk Manager And Installed.
3:- Patched Stock Boot Image With Magisk.
Download Here
4:- Flashed The Boot Image Using
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
5:- Rebooted. Dang Its Done:laugh:
Credits :- acervenky for stock image.
Xposed
1:- Download Riru-Core From Here
2:- Download EdXposed From Here
3:- Goto Magisk Click On Modules Click On + Button Than Choose Riru And Do Same From EdXoosed.
4:- Reboot And Install EdXposed Apk From Here
Enjoy
Works.
Installed GravityBox. Running smoothly.
Has anyone tried the european Variant gm1913?
jatinarora said:
Works.
Installed GravityBox. Running smoothly.
Click to expand...
Click to collapse
Which version of gravitybox did you install? I can't find a version for Android P.
sippi90 said:
Has anyone tried the european Variant gm1913?
Click to expand...
Click to collapse
Don't do it, I did and now my device is messed up until I can find a full stock zip. Didn't think to backup my stock boot image unfortunately, with the patched boot image I got here wifi won't work anymore and the settings app became very unstable.
Does anyone have a stock 9.5.4 boot image for GM1913? Or a flashable zip for GM1913? Any help would be much appreciated..
Does this work with a T-Mobile variant that's bootloader unlocked?
ScottOtis said:
Does this work with a T-Mobile variant that's bootloader unlocked?
Click to expand...
Click to collapse
I don't think so - or it will but you can't use the patched boot image posted by others here. If I understand correctly you'll need to patch your own rom's boot image. I think the T-mobile version is its own model (not the GM1917 that most people here have).
I used the patched boot image for GM1917 on a GM1913 and now my wifi and most settings are broken. And unfortunately I can't find a stock zip flash file to recover anywhere... I guess that's how it is buying the phone on launch day in Europe.
gururoop said:
Which version of gravitybox did you install? I can't find a version for Android P.
Click to expand...
Click to collapse
https://github.com/GravityBox/GravityBox/releases/tag/v9.0.0-beta-11_p
unixunderground said:
Don't do it, I did and now my device is messed up until I can find a full stock zip. Didn't think to backup my stock boot image unfortunately, with the patched boot image I got here wifi won't work anymore and the settings app became very unstable.
Does anyone have a stock 9.5.4 boot image for GM1913? Or a flashable zip for GM1913? Any help would be much appreciated..
Click to expand...
Click to collapse
Did you solve your issue ?
I got the same when I try, no wifi on the patched boot.
And unfortunately like you I suppose, I wiped and erased the system..... Spend 4h30 trying to solve it ahah
I did find and download the OTA 9.5.4 from XDA dev named
9.5.4-GM21BA-OnePlus7ProOxygen_21.E.08_OTA_008_all_1905150058_12457a8b-FASTBOOT
Click to expand...
Click to collapse
, if you copy and past this name on Google you will find a download link, and I used the All-In-One tools to flash it, you can here this software : here
Because when I tried to flash with the fastboot command, my device was stucked in the Fastboot Mode and could not do anything for 4h30 until I use the All-in-one tools
Hope it can help
How do we keep root if the when there's an OOS update?
After installing Edxposed it fails safetynet check
A.Priori said:
After installing Edxposed it fails safetynet check
Click to expand...
Click to collapse
I'm on gm1917 with patched 9.5.3 (from rom page here) and followed instructions. With gravitybox it has worked well and passes safetynet...
A.Priori said:
After installing Edxposed it fails safetynet check
Click to expand...
Click to collapse
I also faced this, for me not an issue, would be nice if it passed, but I never use no apps that require it. I'd rather the customization than SafetyNet personally, but fair warning.
ERIC
jatinarora said:
Works.
Installed GravityBox. Running smoothly.
Click to expand...
Click to collapse
Yep running fine on my phone with 9.5.4, Magisk 19.2.
Phone is a GM1917
I thought gm1917 is US version which only has 9.5.3 as latest ?
Are you sure you are gm1917?
---------- Post added at 01:49 PM ---------- Previous post was at 01:48 PM ----------
tech_head said:
Yep running fine on my phone with 9.5.4, Magisk 19.2.
Phone is a GM1917
Click to expand...
Click to collapse
thought gm1917 is US version which only has 9.5.3 as latest ?
Are you sure you are gm1917?
unixunderground said:
Don't do it, I did and now my device is messed up until I can find a full stock zip. Didn't think to backup my stock boot image unfortunately, with the patched boot image I got here wifi won't work anymore and the settings app became very unstable.
Does anyone have a stock 9.5.4 boot image for GM1913? Or a flashable zip for GM1913? Any help would be much appreciated..
Click to expand...
Click to collapse
From the other thread, that's a sign the wrong boot image was flashed
I am European with GM1913 with patched 9.5.4 and works flawless! Used the image in here:
forum.xda-developers.com/oneplus-7-pro/how-to/guide-root-oneplus-7-pro-patched-boot-t3931205
Noob question: Can someone point me in the right direction on how to update to the recently released 9.5.4 if I am rooted with this method?
Sent from my GM1911 using Tapatalk
Aren't we missing the command of "fastboot oem unlock"? Actually aren't we missing several steps from the instructions? Like these:
1) Become a "Developer" by clicking on "About Phone" from the settings menu.
2) Click on "Build Number" over and over until it says you are now a developer.
3) Go to the "Developer Options" from within the "System" section.
4) Turn ON "OEM Unlocking".
5) Boot into FastBoot menu through one of three methods. The easiest is turning ON "Advanced Reboot", holding the power button until the menu pops up and selecting "Bootloader".
6) Once rebooted, type "fastboot OEM Unlocking" to fully unlock the device. (The device will now wipe everything).
Mix some of the instructions from Kingmohdarif in here at the end or somewhere in there.
Munk0 said:
Aren't we missing the command of "fastboot oem unlock"? Actually aren't we missing several steps from the instructions? Like these:
1) Become a "Developer" by clicking on "About Phone" from the settings menu.
2) Click on "Build Number" over and over until it says you are now a developer.
3) Go to the "Developer Options" from within the "System" section.
4) Turn ON "OEM Unlocking".
5) Boot into FastBoot menu through one of three methods. The easiest is turning ON "Advanced Reboot", holding the power button until the menu pops up and selecting "Bootloader".
6) Once rebooted, type "fastboot OEM Unlocking" to fully unlock the device. (The device will now wipe everything).
Mix some of the instructions from Kingmohdarif in here at the end or somewhere in there.
Click to expand...
Click to collapse
Well yeah OP makes some assumptions.
I typed "fastboot flashing unlock" instead of what you said but maybe both works.
Anyways, as OP said, we don't have TWRP yet so we must do more ourselves. I've extracted the lastest STOCK boot image from version 9.5.5.GM21BA (at the time of writing the last on downloads.oneplus.com and also what my 7 Pro is running right now). I patched it with Magisk 19.2 and flashed it using "fastboot flash boot magisk_patched.img".
Result was successful, latest firmware, Magisk rooted :good:
The patched boot image was too large to include so I uploaded it to some random file hosting site: https://www.file-up.org/z8ka0weyftcv
To extract the stock boot image I used this nice tool: https://github.com/cyxx/extract_android_ota_payload
How to root any version of the OnePlus 7T Pro!
1. Make sure your bootloader is unlocked!
2. Once you're unlocked enter the following ADB commands to extract your current boot image (Your phone needs to be on)
adb shell dd if=/dev/block/bootdevice/by-name/boot_a of=/boot_a.img
adb pull /boot_a.img pathinyourpc
Click to expand...
Click to collapse
3. Download & install Magisk Manager on your phone
4. Put the boot_a.img file on your phone
5. Open the magisk manager app and click the "Advanced Settings" button, then enable "Prserve AVB 2.0/dm-verity & Preserve force encryption", then select the top "Install" button and select "Patch to boot image" and select the boot_a.img
6. Now magisk will create a magisk patched boot image file, put that on your computer
7. Now enter the following ADB command
adb reboot fastboot
fastboot --set-active=a
fastboot boot pathtomagiskpatched.img
Click to expand...
Click to collapse
8. Now you'll boot into the system, reopen the magisk app and click the top install button again and select "Direct install", then reboot
Congratulations you've now successfully rooted your phone!
EDIT: This guide is wrong.
Check these references for the proper guide to root. OP refuses to acknowledge it's wrong even when I pointed it out to him with proof.
https://forum.xda-developers.com/showpost.php?p=81023631&postcount=144
^^^
Mainly this one.
https://forum.xda-developers.com/showpost.php?p=81105485&postcount=171
https://forum.xda-developers.com/showpost.php?p=81106827&postcount=173
-----
Now I have something so do for the weekend, thanks
Just a question, have you tried Viper4Android (if your use it)?: Use 2.7.1.6 stable version.
hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.
Dukynuky said:
hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.
Click to expand...
Click to collapse
Yes it says its installed thats correct but you need to install it again in the magisk app so it stays after restarting the phone. I don't know about WLAN tho
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
I can confirm I have successfully rooted using this method, and WIFI is working fine. Thank you very much, OP and everyone involved, no wits time to set up my device
Ah! Will do this immediately when I get home.
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left
Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
Click to expand...
Click to collapse
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...
Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!
Dukynuky said:
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...
Click to expand...
Click to collapse
please see my edited reply, i installed directry through viper4android app, no the module
Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
got ist working.. layer 8 error.. didnt had the ota update installed.
Updated oxygen os.. then wifi is working. also used canary magisk files.. works perfekt.. thanks
Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
my wifi works perfectly fine, I have the EU version too.
I attached screenshots of what to do with the installed, please select the direct install option and then reboot!
droidvark said:
Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!
Click to expand...
Click to collapse
I have a warning above the instructions already, I think you might have missed it
Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left
Click to expand...
Click to collapse
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!
Lossyx said:
please see my edited reply, i installed directry through viper4android app, no the module
Click to expand...
Click to collapse
Use the module next time!
HolyChickenGuy said:
I have a warning above the instructions already, I think you might have missed it
Click to expand...
Click to collapse
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!
droidvark said:
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!
Click to expand...
Click to collapse
Oh sorry, yeah I rewrote it to make it clearer. Unlocking the bootloader will wipe your data
Sent from my HD1913 using Tapatalk
HolyChickenGuy said:
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!
Click to expand...
Click to collapse
Damn, you are my hero. Did a factory reset and followed the OP again, now everything is fine and I'm rooted. Thank you again.
edit: also, for safety precaution, disable automatic updates in Developer options
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Great, I'll check back in on this tomorrow and see how everyone is getting on before I try. Had a skim through here this morning before mine arrived and didn't see anything so set up as is.
I've read about updating to the latest OTA and keeping root from several places including from topjohnwu himself but still a little unclear about this and don't want to mess it up. So in the manager I click uninstall and then press restore images. Then apply the system update? I'm not understanding if I have to download the new boot.img to re-root? That's where I am confused.
1. Uninstall and restore images
2. Install OTA (Do not reboot)
3. Install Magisk --> Install to inactive slot. This works because magisk is still running as root and can patch the flashed boot.img.
4. Reboot
Pixeling said:
1. Uninstall and restore images
2. Install OTA (Do not reboot)
3. Install Magisk --> Install to inactive slot. This works because magisk is still running as root and can patch the flashed boot.img.
4. Reboot
Click to expand...
Click to collapse
Ok thank you. Unhiding magisk is not necessary?
qman66 said:
Ok thank you. Unhiding magisk is not necessary?
Click to expand...
Click to collapse
I don't think so
Pixeling said:
1. Uninstall and restore images
2. Install OTA (Do not reboot)
3. Install Magisk --> Install to inactive slot. This works because magisk is still running as root and can patch the flashed boot.img.
4. Reboot
Click to expand...
Click to collapse
Is this pixel specific? Or do you think this would work on the 7T as well
In theory it should work with any phone that has A/B (dual partitions) support.
Pixeling said:
1. Uninstall and restore images
2. Install OTA (Do not reboot)
3. Install Magisk --> Install to inactive slot. This works because magisk is still running as root and can patch the flashed boot.img.
4. Reboot
Click to expand...
Click to collapse
One question. I have viper4android installed and I'm wondering when I uninstall and restore images, then update, will I lose viper and have to reinstall and redo all of my settings when I reinstall magisk?
rellomar said:
One question. I have viper4android installed and I'm wondering when I uninstall and restore images, then update, will I lose viper and have to reinstall and redo all of my settings when I reinstall magisk?
Click to expand...
Click to collapse
I don't know what will happen via the OTA method, however, I can speak from experience that if you do your updates via fastboot and factory images, you will retain your V4A settings. I simply disable all of my modules, reboot, patch the updated boot.img, remove my face ID, fastboot the factory image with the -w removed, let it boot up, then fastboot the patched boot.img, boot up, enable my modules, reboot, and everything is as it was :good:
Badger50 said:
I don't know what will happen via the OTA method, however, I can speak from experience that if you do your updates via fastboot and factory images, you will retain your V4A settings. I simply disable all of my modules, reboot, patch the updated boot.img, remove my face ID, fastboot the factory image with the -w removed, let it boot up, then fastboot the patched boot.img, boot up, enable my modules, reboot, and everything is as it was :good:
Click to expand...
Click to collapse
delete
Badger50 said:
I don't know what will happen via the OTA method, however, I can speak from experience that if you do your updates via fastboot and factory images, you will retain your V4A settings. I simply disable all of my modules, reboot, patch the updated boot.img, remove my face ID, fastboot the factory image with the -w removed, let it boot up, then fastboot the patched boot.img, boot up, enable my modules, reboot, and everything is as it was :good:
Click to expand...
Click to collapse
Could you possibly give me little more detailed instructions? I'm just coming back to Android after using an iPhone for a few years so I'm a little out of the loop with flashing. Mainly, I'm confused when you said fastboot flash the the factory image with the -w removed.
rellomar said:
Could you possibly give me little more detailed instructions? I'm just coming back to Android after using an iPhone for a few years so I'm a little out of the loop with flashing. Mainly, I'm confused when you said fastboot flash the the factory image with the -w removed.
Click to expand...
Click to collapse
After you download and extract the factory image, you will see a file named, flash-all.bat. Within that file, toward the end of the script, you'll see the -w flag which tells the script to wipe your device. By removing that flag, your are essentially updating your OS without loosing any internal data kinda like an OTA does :good:
with magisk installed how we can check whether we have update on the road, simply check in settings work?
Badger50 said:
After you download and extract the factory image, you will see a file named, flash-all.bat. Within that file, toward the end of the script, you'll see the -w flag which tells the script to wipe your device. By removing that flag, your are essentially updating your OS without loosing any internal data kinda like an OTA does :good:
Click to expand...
Click to collapse
That worked. Thanks for the advice....makes updating very easy :good:
I tried re-rooting after updating and now it says Your device is corrupt. It cant be trusted and may not work properly.
It freezes on the Google if I continue. Not sure what happened.
Any remedy for this?
features99 said:
I tried re-rooting after updating and now it says Your device is corrupt. It cant be trusted and may not work properly.
It freezes on the Google if I continue. Not sure what happened.
Any remedy for this?
Click to expand...
Click to collapse
Need more specific details, like specific method of rooting, version of Magisk, updating to what?, etc...
Unfortunately you may have to flash the factory image and start all over again if no one else can help you with it. At least you have the option. Sucks when that happens.
I mean... the first message just sounds like the bootloader unlocked message which would show up even if you could fully boot in.
I wouldn't factory reset over just this though. Flash the factory image without the -w parameter in flash-all.bat
jljtgr said:
I mean... the first message just sounds like the bootloader unlocked message which would show up even if you could fully boot in.
I wouldn't factory reset over just this though. Flash the factory image without the -w parameter in flash-all.bat
Click to expand...
Click to collapse
I agree. Flashing the factory image without the -w would likely allow him to boot up again. But it would be helpful for that person to tell us exactly what they did so we can help them avoid it in the future, e.g. maybe they flashed the stable version of Magisk instead of Beta or Canary, or maybe they tried a direct install instead of patching the boot image, etc...
Ok guys sorry for not giving more details.
So I rooted awhile back when I got the phone, havent updated in a long time so I thought it was time.
I updated to Android 11 with the latest security updates and tried to re-root.
I updated Magisk to the latest version and patched the matching boot image, but Im pretty sure I used the stable version.
I should of researched it more as Im reading the beta method is the way to go.
I opened the command prompt with the following commands:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
fastboot reboot
Seems like everything went ok...
Then afterwards got the corrupted message and Google hang.
I can still load to fastboot but recovery or rescue doesnt work.
So where can I go from here? I only rooted a few phones in the past so Im still learning and reading lots of posts.
Also I didnt modify my own boot image, but one I downloaded from a matching build.
I really appreciate the help
features99 said:
Ok guys sorry for not giving more details.
So I rooted awhile back when I got the phone, havent updated in a long time so I thought it was time.
I updated to Android 11 with the latest security updates and tried to re-root.
I updated Magisk to the latest version and patched the matching boot image, but Im pretty sure I used the stable version.
I should of researched it more as Im reading the beta method is the way to go.
I opened the command prompt with the following commands:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
fastboot reboot
Seems like everything went ok...
Then afterwards got the corrupted message and Google hang.
I can still load to fastboot but recovery or rescue doesnt work.
So where can I go from here? I only rooted a few phones in the past so Im still learning and reading lots of posts.
I really appreciate the help
Click to expand...
Click to collapse
I would try fastboot flashing the stock boot image first.
If Magisk says you're on a version before 21.0, the patched image won't work for Android 11. Stable is currently 20.4 released in March.
Lughnasadh said:
I would try fastboot flashing the stock boot image first.
Click to expand...
Click to collapse
tried that..it didnt work
features99 said:
tried that..it didnt work
Click to expand...
Click to collapse
Then I would flash the December factory image using fastboot but with the -w removed from the flash-all.bat file so it won't erase your data.
Lughnasadh said:
Then I would flash the December factory image using fastboot but with the -w removed from the flash-all.bat file so it won't erase your data.
Click to expand...
Click to collapse
Yes that worked, didn't know about edited the .bat to remove the the -w and saving all data. Back in business for now...
Thank you all for expertise, much appreciated!
features99 said:
Yes that worked, didn't know about edited the .bat to remove the the -w and saving all data. Back in business for now...
Thank you all for expertise, much appreciated!
Click to expand...
Click to collapse
No problem. Glad you got it going. As I see you've already found out, Magisk Beta 21.1 is a good way to go. Canary as well but then you may run into problems in the future when Canary gets updated since those are "cutting edge" builds.
I have a rooted 4a 5G that's still on the January 5, 2021 version. Whenever I go to the phone's settings to check for updates, it keeps saying that the device is up to date. I went to https://developers.google.com/android/images#bramble but I am unsure how to update my device. Am I supposed to use Factory Image, or Full OTA Image?
WhiteAsIce said:
I have a rooted 4a 5G that's still on the January 5, 2021 version. Whenever I go to the phone's settings to check for updates, it keeps saying that the device is up to date. I went to https://developers.google.com/android/images#bramble but I am unsure how to update my device. Am I supposed to use Factory Image, or Full OTA Image?
Click to expand...
Click to collapse
I always use factory images. Just remember to remove the -w from the flash all .bat or .sh
Edit: See below.
Tulsadiver said:
I always use factory images. Just remember to remove the -w from the flash all .bat or .sh
Click to expand...
Click to collapse
So I removed the -w lines from the flash-all files, flashed the June OTA, then flashed the Magisk patched boot img. My phone cannot boot past the fastboot screen, meaning I don't have a phone until I fix this. Any help?
WhiteAsIce said:
So I removed the -w lines from the flash-all files, flashed the June OTA, then flashed the Magisk patched boot img. My phone cannot boot past the fastboot screen, meaning I don't have a phone until I fix this. Any help?
Click to expand...
Click to collapse
Did you leave any modules on your phone?
Tulsadiver said:
Did you leave any modules on your phone?
Click to expand...
Click to collapse
What are modules?
Anyway, it's too late, I ran the flash-all file with the -w lines to try to recover my phone, but it ended up WIPING my entire phone. Everything is gone, downloads and pictures and all.
WhiteAsIce said:
What are modules?
Anyway, it's too late, I ran the flash-all file with the -w lines to try to recover my phone, but it ended up WIPING my entire phone. Everything is gone, downloads and pictures and all.
Click to expand...
Click to collapse
You are rooted with magisk but don't know what magisk modules are?
Tulsadiver said:
You are rooted with magisk but don't know what magisk modules are?
Click to expand...
Click to collapse
The only one I had was a mod to allow safetynet to pass.
My phone is rooted with magisk, so I need to do the monthly updates manually. In order to do this, I download both the OTA and the factory image. I update the phone using the OTA. I extract the boot.img file from the factory image, put it on the pixel after updating and patch it with magisk. Then I copy it to my computer and flash it to the active boot slot as described below.
Too late to help now, but the issue was probably that the pixel has two boot slots, boot_a and boot_b, and it was booting from the wrong one. The -w you used finally is the wipe option and it's done by default unless you remove it, so that's why the phone was wiped.
In my case, I used the following commands to make sure that I flashed to the correct slot and/or booted from the correct slot that had the magisk patched kernel:
fastboot getvar current-slot
fastboot flash boot_a magisk_patched.img
If it's ever necessary, you can manually change the active boot slot: fastboot --set-active=a
If you flash the correct magisk-patched kernel to either slot and set the phone to boot from that slot, your phone will boot up. I learned about this the hard way and now, every month, I just make sure that I flash to the currently active slot and have not had a problem since. One of the nicest things about having a pixel is that they are just about impossible to brick - it's just a matter of redoing things properly.