Related
getting errors when trying to take the january OTA security update
im using systemless root 2.66
twrp wont install the ota. anyone know how?
With TWRP, you can't take an OTA. You need to have stock Android recovery, unmodified /system, and unmodified boot.img (so no custom kernel). Otherwise the OTA will fail.
ugh i thought one of th ebenefit of systemless root was to be able to easily to ota updates. anyone have a flashable zip?
If you need twrp just boot from it in fastboot and retain stock recovery
Where did you find the OTA update? All I have found is the factory image, which is a different animal, here: https://developers.google.com/android/nexus/images
Chainfire wrote that if you use the SuperSU unroot function you should be able to apply the "real" OTA (i.e. not a sideload of a downloaded OTA, though maybe that might work too) and then reroot.
Alternatively, download the full image, unzip everything including the zip within the zip, copy the system.img, boot.img, and the TWRP for your device to your ADB folder. Copy SuperSU v2.67 to a folder on your phone. Then boot into bootloader, flash system, boot & TWRP, boot into TWRP recovery, and install SuperSU. Job done. No settings, data or apps lost. I know because I did it last night on my Nexus 6 & Nexus 10.
Folks, please correct me if I'm wrong here, but I would think that the installation of the OTA will fail simply because the OTA encounters a custom recovery (TWRP), as opposed to the expected stock recovery. Let alone anything that may or may not have been done to /system.
JimSmith94 said:
Where did you find the OTA update? All I have found is the factory image, which is a different animal, here: https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493/page124
There's the OTA for MMB29S to MMB29Q.
---------- Post added at 11:45 AM ---------- Previous post was at 11:44 AM ----------
Not_A_Dev said:
Folks, please correct me if I'm wrong here, but I would think that the installation of the OTA will fail simply because the OTA encounters a custom recovery (TWRP), as opposed to the expected stock recovery. Let alone anything that may or may not have been done to /system.
Click to expand...
Click to collapse
It will fail if /system has been modified, and if there is a custom boot.img that was installed other than the stock one, plus custom recovery as stated.
RMarkwald said:
http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493/page124
There's the OTA for MMB29S to MMB29Q.
---------- Post added at 11:45 AM ---------- Previous post was at 11:44 AM ----------
It will fail if /system has been modified, and if there is a custom boot.img that was installed other than the stock one, plus custom recovery as stated.
Click to expand...
Click to collapse
Thanks! I have already installed MMB29Q with fastboot, but next time I might try OTA with Chainfire's FlashFire: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
https://plus.google.com/+Chainfire/posts/Q7YYVPwv8Fx
Sent from my Nexus 6 using Tapatalk
Anyone have the ota from mmb29k?
Ok, I'm on MMB29S (January security update), rooted N6, running Xposed.
Here's my plan to update to the February security update without losing TWRP and userdata:
1. Download MMB29Q factory image and extract files.
2. adb reboot bootloader
3. fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
4. fastboot reboot-bootloader
5. fastboot flash radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.img
6. fastboot reboot-bootloader
7. fastboot flash system system.img
8. fastboot flash boot boot.img
9. fastboot flash cache cache.img
10. fastboot reboot-bootloader
11. reflash superSu
12. reflash Xposed
Would this work?
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Not_A_Dev said:
Ok, I'm on MMB29S (January security update), rooted N6, running Xposed.
Here's my plan to update to the February security update without losing TWRP and userdata:
1. Download MMB29Q factory image and extract files.
2. adb reboot bootloader
3. fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
4. fastboot reboot-bootloader
5. fastboot flash radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.img
6. fastboot reboot-bootloader
7. fastboot erase system
8. fastboot flash system system.img
9. fastboot erase boot
10. fastboot flash boot boot.img
11. fastboot erase cache
12. fastboot flash cache cache.img
13. fastboot reboot-bootloader
14. reflash superSu
15. reflash Xposed
Would this work?
Click to expand...
Click to collapse
RMarkwald said:
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Click to expand...
Click to collapse
This method (outlined above) works great. This is exactly the same setup I have (n6 + root + xposed) and is also precisely how I've been applying the monthly updates. Never experienced any issues.
RMarkwald said:
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Click to expand...
Click to collapse
I'll give it a shot. I agree, and thanks for the suggestion.
Edit: Happy to report that the method in post #13 leads to a successful update of the most recent Shamu image. My device is now updated to MMB29Q, still runs TWRP, is rooted, and runs Xposed. 20 minutes tops for the whole project.
RMarkwald said:
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Click to expand...
Click to collapse
Excellent may i knidly ask pls
last two steps:
what are commands for reflash supersu and reflash exposed and where are latest files which are compatible?
Thanks tonnes...I believe my user data is preserved
There are no Fastboot commands for SuperSU or Xposed. Each is available as a flashable zip, installed using TWRP.
Most of the time they don't update bootloader and radio...
90% of the time, you can just fastboot flash only system. Basically the equivalent of dirty flashing your rom.
The above where you clear everything before flashing is basically the equivalent of wiping cache 3x... It wipes the partition when you flash. Think about it, if you flash userdata... you end up with all your data being deleted and a blank userdata partition. It doesn't copy the img on top of what is currently there, it replaces it. You can do extra steps if you want... But you really don't need to.
sunandoghosh said:
Excellent may i knidly ask pls
last two steps: what are commands for reflash supersu and reflash exposed and where are latest files which are compatible?
Click to expand...
Click to collapse
Strephon Alkhalikoi said:
There are no Fastboot commands for SuperSU or Xposed. Each is available as a flashable zip, installed using TWRP.
Click to expand...
Click to collapse
^ This. One step that's also missing above is that once system.img and supersu have been flashed, there is hardly any space on /system to flash xposed (that's just how Google does things these days). So one would have to remove a few non-essential system apps (files, such as Google Books, Google Newsstand or the like) to make some room for xposed.
This thread is turning into a fastboot flash factory image thread rather than an ota thread. That's ok, it's a good thing ...I've been waiting for a thread like this and your posts inspired me to do my first flash to update security for my rooted phone (with xposed) since I initially set it up in December.
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Quote:
Originally Posted by Not_A_Dev
Ok, I'm on MMB29S (January security update), rooted N6, running Xposed.
Here's my plan to update to the February security update without losing TWRP and userdata:
1. Download MMB29Q factory image and extract files.
2. adb reboot bootloader
3. fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
4. fastboot reboot-bootloader
5. fastboot flash radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.img
6. fastboot reboot-bootloader
7. fastboot erase system
8. fastboot flash system system.img
9. fastboot erase boot
10. fastboot flash boot boot.img
11. fastboot erase cache
12. fastboot flash cache cache.img
10. fastboot reboot-bootloader
11. reflash superSu
12. reflash Xposed
Would this work?
Click to expand...
Click to collapse
I roughly followed above steps, but had some comments/questions along the way:
I skipped the first and second erases as suggested above, but I kept the third erase (cache) because it is included in the xda n6 stock flashing tutorial here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I rebooted to android system between steps 10 and 11 because I wanted to make sure everything was ok. But that was a bad idea because:
A- it overwrote my twrp with stock recovery (even though I never flashed recovery)! So I had to fastboot boot twrp later.
B- it took extra time formatting stuff that was probably undone later.
And yet I still have to boot into android at some point in time to clear space before I flash the xposed zip in twrp. Maybe next time I should reboot to clear space between steps 11 and 12?
I was pleasantly surprised to see when completed flashing the xposed zip that I didn't have to reinstall the xposed apk and that the xposed modules were already enabled and configured exactly the way I left them. Good stuff.
UPDATE 11-9-18: I have updated the FlashAll with the October edition of version 27.1.3. Yes, they updated the ROM but kept the same version number lol.
This is a TMO Z2 Force 27.1.3 FlashAll. It does not wipe user data. I created it because the OTA update wouldn't complete, I think because I am rooted. Anyway I took the OTA from https://mirrors.lolinet.com (thank you!), unzipped it, used root junky's script to convert it (thank you!) and made a batch file to flash the partitions. The flashall includes ADB and Fastboot also. The Flashall is for windows. Your bootloader needs to be unlocked. You need to be on an OREO rom already.
Disclaimer: Flash at your own risk. Not responsible for damages if this stuff goes south. If you don't know what a flashall is, or twrp, or fastboot, you may not be ready for this.
Downloads
1. Updated October Flashall https://drive.google.com/open?id=1PczvmaVv19c91iOGhpNmhmfKyvDkz-ob (download to your computer)
2. TWRP Installer (if you are rooted, download this to your phone) https://dl.twrp.me/nash/
3. Magisk (if you are rooted, download this to your phone) https://forum.xda-developers.com/apps/magisk
How To:
Unzip the Flashall into a folder called "TMO Moto z2 force 27.1.3 flashall" Open a command prompt in the folder it created. Connect your phone to your computer via ADB.
Not Rooted?
If you are NOT rooted, just run flashall.bat. It will automatically boot into fastboot mode, update the partitions, reboot, and profit. This does not wipe user data.
Rooted
If you are rooted:
1) run flashall_then_recovery.bat. It will automatically boot into fastboot mode, update the partitions, then automatically reboot into a temp twrp recovery.
2) In TWRP install the twrp installer you downloaded above (if you use recovery).
3) Reboot recovery
4) Install magisk that you downloaded above.
5) Reboot
Not Rooted and want to wipe everything?
Run flashall_erase.bat. It will boot into fastboot mode, update the partitions, and wipe everything.
If this helps you please hit the "Thanks" button. Reply to this post if you have questions or need any assistance.
texasaggie1 said:
This is a TMO Z2 Force 27.1.3 FlashAll. It does not wipe user data. I created it because the OTA update wouldn't complete, I think because I am rooted. Anyway I took the OTA from @xiyl (thank you!), unzipped it and made a batch file to flash the partitions. The flashall includes ADB and Fastboot also. The Flashall is for windows. Your bootloader needs to be unlocked. You need to be on an OREO rom already.
Disclaimer: Flash at your own risk. Not responsible for damages if this stuff goes south.
Downloads
1. Flashall https://drive.google.com/open?id=1HK2zssCGlPTD5m2A_SAD-RjrQDfmZMTR (download to your computer)
2. TWRP Installer (if you are rooted, download this to your phone) https://dl.twrp.me/nash/
3. Magisk (if you are rooted, download this to your phone) https://forum.xda-developers.com/apps/magisk
How To:
Unzip the Flashall. It will create a folder called "NASH_TMO_27.1.3" Open a command prompt in the folder it created.
Not Rooted?
If you are NOT rooted, just run flashall.bat. It will automatically boot into fastboot mode, update the partitions, reboot, and profit.
Rooted
If you are rooted:
1) run flashall_then_recovery.bat. It will automatically boot into fastboot mode, update the partitions, then automatically reboot into a temp twrp recovery.
2) In TWRP install the twrp installer you downloaded above
3) Reboot recovery
4) Install magisk that you downloaded above.
5) Reboot
If this helps you please hit the "Thanks" button. Reply to this post if you have questions or need any assistance,
Click to expand...
Click to collapse
the "flashal link" contains only TWRP3.1.zip with boot.img and META-INF folder. it doesn't contain a flashall_then_recovery.bat nor NASH_TMO_27.1.3.
kendallgreen said:
the "flashal link" contains only TWRP3.1.zip with boot.img and META-INF folder. it doesn't contain a flashall_then_recovery.bat nor NASH_TMO_27.1.3.
Click to expand...
Click to collapse
Sorry! It was late and I linked to the wrong thing. ? Try it now please.
texasaggie1 said:
This is a TMO Z2 Force 27.1.3 FlashAll. It does not wipe user data. I created it because the OTA update wouldn't complete, I think because I am rooted. Anyway I took the OTA from @xiyl (thank you!), unzipped it and made a batch file to flash the partitions. The flashall includes ADB and Fastboot also. The Flashall is for windows. Your bootloader needs to be unlocked. You need to be on an OREO rom already.
Disclaimer: Flash at your own risk. Not responsible for damages if this stuff goes south. If you don't know what a flashall is, or twrp, or fastboot, you may not be ready for this.
Downloads
1. Flashall https://drive.google.com/file/d/1JKu5S7xvy8xvyCodLEt7olr8czP_8FUm/view?usp=drivesdk (download to your computer)
2. TWRP Installer (if you are rooted, download this to your phone) https://dl.twrp.me/nash/
3. Magisk (if you are rooted, download this to your phone) https://forum.xda-developers.com/apps/magisk
How To:
Unzip the Flashall. It will create a folder called "NASH_TMO_27.1.3" Open a command prompt in the folder it created.
Not Rooted?
If you are NOT rooted, just run flashall.bat. It will automatically boot into fastboot mode, update the partitions, reboot, and profit.
Rooted
If you are rooted:
1) run flashall_then_recovery.bat. It will automatically boot into fastboot mode, update the partitions, then automatically reboot into a temp twrp recovery.
2) In TWRP install the twrp installer you downloaded above
3) Reboot recovery
4) Install magisk that you downloaded above.
5) Reboot
If this helps you please hit the "Thanks" button. Reply to this post if you have questions or need any assistance.
Click to expand...
Click to collapse
I downloaded and unzipped the new NASH_TMO_27.1..3. I added the AdbWinApi.dll and AdbWinUsbApi.dll and got the flashall_then_recovery.bat to run. I didn't install the TWRP installer or Magisk but rebooted to recovery and then system. After several restarts due to unlocked bootloader warning, it came back to build number OCXS27.1.2 kernel [email protected]#1 Fri Apr 20 09:21:27 CDT 2018. Android security level May 1, 2018. Android version 8.0.0 However, all of my apps were retained except Messaging .
kendallgreen said:
the "flashal link" contains only TWRP3.1.zip with boot.img and META-INF folder. it doesn't contain a flashall_then_recovery.bat nor NASH_TMO_27.1.3.
Click to expand...
Click to collapse
kendallgreen said:
I downloaded and unzipped the new NASH_TMO_27.1..3. I added the AdbWinApi.dll and AdbWinUsbApi.dll and got the flashall_then_recovery.bat to run. I didn't install the TWRP installer or Magisk but rebooted to recovery and then system. After several restarts due to unlocked bootloader warning, it came back to build number OCXS27.1.2 kernel [email protected]#1 Fri Apr 20 09:21:27 CDT 2018. Android security level May 1, 2018. Android version 8.0.0 However, all of my apps were retained except Messaging .
Click to expand...
Click to collapse
So try it again but this time just do the regular flashall.bat. it should work this time.
It sounds like you are installing this to slot a but your phone is running in slot b. If doing it this way doesn't fix it just look on here for the command to switch your phone from one slot to another.
success. I tried the flashall.bat and got the system updated to 27.1.3. I noticed that when I fastboot --set-active=_a, I had 27.1.2 and with --set-active=_b, I had to restart the phone because it was stuck at the unlocked bootloader warning. thanks.
kendallgreen said:
success. I tried the flashall.bat and got the system updated to 27.1.3. I noticed that when I fastboot --set-active=_a, I had 27.1.2 and with --set-active=_b, I had to restart the phone because it was stuck at the unlocked bootloader warning. thanks.
Click to expand...
Click to collapse
awesome! The whole a/b partition thing can be quite annoying
great job man glad someone did this i was about to try thanks
worked great but i reflashed remove encryption oreo also i didnt know if it was a necessary was being safe you made it easy no fastboot lol great work
My Fellow Texan.....
THANK YOU.
My phone has been in a weird limbo for months. I was on AOSIP ROM but it wasn't rooted, I couldn't use any moto mods and I couldn't install anything because TWRP wasn't installed and it wouldn't let me install it, either. I now have TWRP, but it's showing no baseband. So I'm gonna attempt to fix that but I'm already in a better place than I was. Thanks again, brother.
if you need baseband its easy to fix i had the same issues i was testing kernel its eas fix if you need i can help fix ive bricked and tried everything works easy check last post put on this https://forum.xda-developers.com/z2-force/development/pantheon-kernel-alpha-t3805977
My Tmo box is rooted, presently running the original 27.1 release.. I've been getting the OTA update notifications for 27.1.2.
Do we know if I can skip 27.1.2 and jump straight to the 27.1.3 release? I'd love to be able to do this flash-all and put the update notifications to bed for a while.
dismembered3po said:
My Tmo box is rooted, presently running the original 27.1 release.. I've been getting the OTA update notifications for 27.1.2.
Do we know if I can skip 27.1.2 and jump straight to the 27.1.3 release? I'd love to be able to do this flash-all and put the update notifications to bed for a while.
Click to expand...
Click to collapse
It should be fine to skip revisions.
StonedYoda said:
My Fellow Texan.....
THANK YOU.
My phone has been in a weird limbo for months. I was on AOSIP ROM but it wasn't rooted, I couldn't use any moto mods and I couldn't install anything because TWRP wasn't installed and it wouldn't let me install it, either. I now have TWRP, but it's showing no baseband. So I'm gonna attempt to fix that but I'm already in a better place than I was. Thanks again, brother.
Click to expand...
Click to collapse
If you are on tmobile, flashing the firmware flashall from the aosip thread to get baseband back.
mookiexl said:
If you are on tmobile, flashing the firmware flashall from the aosip thread to get baseband back.
Click to expand...
Click to collapse
If that doesn't work let me know. It should though. You may have to re-root after his suggestion
I'd been avoiding updates because I just didn't want to deal with rooting again and restoring data, etc. This was great!
(bootloader) slot: not found this is what I get with every fastboot command.
I was having the same issue... I was on 27.1.2 and kept getting notified to update, but it kept failing. I'm rooting with Magisk (16.0 initially but then up to 17.1) and it wouldn't update. Thanks to this thread, I ran the flashall_then_recovery.bat and it worked a treat!!! Thank you TexasAggie!
TWRP Installer link is down
The link to the TWRP installer is timing out when loading and comes up with an error message. Is it possible to install the 27.3 update using adb and then flash magisk in the temp twrp? Thanks for your work bro!
UPDATE:
I tried and now I'm stuck in bootloop. I can still get to twrp using adb and did a wipe but it's still stuck in loop land. Do I need to be rebooting in TWRP from slot A or B? This is my first phone that has dual partitions and I am a bit confused by it. Any suggestions? THANK YOU!!
UPDATE:
Tried your flashall update a second time and it worked with no bootloop issue, was able to flash magisk and obtain root again too.
climbhigh77 said:
The link to the TWRP installer is timing out when loading and comes up with an error message. Is it possible to install the 27.3 update using adb and then flash magisk in the temp twrp? Thanks for your work bro!
UPDATE:
I tried and now I'm stuck in bootloop. I can still get to twrp using adb and did a wipe but it's still stuck in loop land. Do I need to be rebooting in TWRP from slot A or B? This is my first phone that has dual partitions and I am a bit confused by it. Any suggestions? THANK YOU!!
UPDATE:
Tried your flashall update a second time and it worked with no bootloop issue, was able to flash magisk and obtain root again too.
Click to expand...
Click to collapse
Glad to hear that!
Hi,
I'm on the latest Magisk, rooted, with Feb 2020 update
My Pixel4XL is carrier unlocked.
I can't seem to get the OTA to work, I clicked check for update, it gave me a prompt of preparing for update, then said my system is up to date.
I tried removing Magisk and restoring boot image in MManager
I can't access a computer for the time being so I can't sideload it
Help would be appreciated!
Cyshot said:
Hi,
I'm on the latest Magisk, rooted, with Feb 2020 update
My Pixel4XL is carrier unlocked.
I can't seem to get the OTA to work, I clicked check for update, it gave me a prompt of preparing for update, then said my system is up to date.
I can't access a computer for the time being so I can't sideload it
Help would be appreciated!
Click to expand...
Click to collapse
Try this: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md/
Homeboy76 said:
Try this: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md/
Click to expand...
Click to collapse
I did, that's what I followed in the first place
Hey, I have this issue too, I tried to click check for updates, then it said preparing system update, and went back to your system is up to date. Have you found a fix?
TY53 said:
Hey, I have this issue too, I tried to click check for updates, then it said preparing system update, and went back to your system is up to date. Have you found a fix?
Click to expand...
Click to collapse
I wish :/
Seems like checking for updates before uninstalling Magisk is a no-no.
Mine worked OK.
The February OTA never arrived, so side-loaded that last week.
Today I un-installed Magisk, checked for OTA, it was found, and completed, than re-installed Magisk.
Seems as so checking for OTA with Magisk installed is tripping something somewhere.
Need help.
I tried to search for the March security update after ... it was not there.. now I have this error. What should I do?
sam1374 said:
Need help.
I tried to search for the March security update after ... it was not there.. now I have this error. What should I do?
Click to expand...
Click to collapse
Reflash your patched boot.img
mushtafa said:
Reflash your patched boot.img
Click to expand...
Click to collapse
Thanks I'll try it
I had this problem too. I reflashed the magisk patched and now screen is not responding, can someone help me?
TY53 said:
I had this problem too. I reflashed the magisk patched and now screen is not responding, can someone help me?
Click to expand...
Click to collapse
Try rebooting the phone; however, if it is a soft brick situation then:
- Download the March stock factory image from Google
- Unzip and modify the flash-all.bat file and remove the "-w" from the script
- Plug phone into the computer with authorized USB debugging
- Reboot the phone into bootloader mode
- Run the flash-all file and wait for the updates to complete
- Let the phone reboot and then copy the boot.img (from March) file to your phone
- Run the Magisk Manager and patch your boot.img
- Copy the magisk_patched file to your computer and reboot into bootloader
- Flash the boot image with magisk_patched image, and reboot the phone
If it is still soft bricked, then add the "-w" back into the flash-all script and go through the process of rooting your phone again (above). Note: "-w" will erase the userdata on your phone (in other words, wipe and do a factory reset).
bb709394 said:
Try rebooting the phone; however, if it is a soft brick situation then:
- Download the March stock factory image from Google
- Unzip and modify the flash-all.bat file and remove the "-w" from the script
- Plug phone into the computer with authorized USB debugging
- Reboot the phone into bootloader mode
- Run the flash-all file and wait for the updates to complete
- Let the phone reboot and then copy the boot.img (from March) file to your phone
- Run the Magisk Manager and patch your boot.img
- Copy the magisk_patched file to your computer and reboot into bootloader
- Flash the boot image with magisk_patched image, and reboot the phone
If it is still soft bricked, then add the "-w" back into the flash-all script and go through the process of rooting your phone again (above). Note: "-w" will erase the userdata on your phone (in other words, wipe and do a factory reset).
Click to expand...
Click to collapse
Thank you so much! I was able to retrieve my phone with your help!
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.
It's been years since I've rooted an Android device so I gotta say it's been fun getting back to it, if a little bit frustrating. This is the first Samsung device I've owned and I can't wait to get another ROM. Here's what I've done, many times, without success.
1. unlock bootloader
2. download Samfw.com_SM-X200_XAR_X200XXU2CWC1_fac (went from Android 11 to 13)
3. flashed above firmware with Odin3 v3.14.1
4. setup device (basic - bypassed Google login, Samsung installs and options)
5. installed Magisk-v26.1 on tablet
5. Extracted boot.img from AP_.tar, copied to tablet, patched with magisk, back to PC, created boot.tar from magisk patch
6. Odin flash again, added BL from firmware, AP was patched boot.tar from magisk, CSC from firmware.
I've read to flash only the patched boot image (.tar), to patch the full AP package, to flash boot image and add back to AP file, and I've tried all three without success.
My first attempt was with X200XXU1AVC1, with the same result, so I flashed the Android 13 for all subsequent steps.
I feel like I've done everything correctly and could use some guidance in resolving why I can't achieve root.
EDIT: resolved, i didn't know about sideloading magisk!
jcunwired said:
It's been years since I've rooted an Android device so I gotta say it's been fun getting back to it, if a little bit frustrating. This is the first Samsung device I've owned and I can't wait to get another ROM. Here's what I've done, many times, without success.
1. unlock bootloader
2. download Samfw.com_SM-X200_XAR_X200XXU2CWC1_fac (went from Android 11 to 13)
3. flashed above firmware with Odin3 v3.14.1
4. setup device (basic - bypassed Google login, Samsung installs and options)
5. installed Magisk-v26.1 on tablet
5. Extracted boot.img from AP_.tar, copied to tablet, patched with magisk, back to PC, created boot.tar from magisk patch
6. Odin flash again, added BL from firmware, AP was patched boot.tar from magisk, CSC from firmware.
I've read to flash only the patched boot image (.tar), to patch the full AP package, to flash boot image and add back to AP file, and I've tried all three without success.
My first attempt was with X200XXU1AVC1, with the same result, so I flashed the Android 13 for all subsequent steps.
I feel like I've done everything correctly and could use some guidance in resolving why I can't achieve root.
EDIT: resolved, i didn't know about sideloading magisk!
Click to expand...
Click to collapse
I don't understand what you mean by "sideloading magisk". Did you read my post #84? That work with the previous version of Android 13, CWA3. I just copied Magisk apk to the SD card and installed it from there.
lewmur said:
I don't understand what you mean by "sideloading magisk". Did you read my post #84? That work with the previous version of Android 13, CWA3. I just copied Magisk apk to the SD card and installed it from there.
Click to expand...
Click to collapse
Select update from adb in recovery, then:
adb devices
adb sideload Magisk-v26.1.zip
jcunwired said:
Select update from adb in recovery, then:
adb devices
adb sideload Magisk-v26.1.zip
Click to expand...
Click to collapse
I know how to do it. I just don't understand what difference it makes. Why not just copy it to the tablet and install it?
lewmur said:
I know how to do it. I just don't understand what difference it makes. Why not just copy it to the tablet and install it?
Click to expand...
Click to collapse
Because I was in ADB and like you said, what difference does it make?
jcunwired said:
Because I was in ADB and like you said, what difference does it make?
Click to expand...
Click to collapse
The difference is that your post said you installed Magisk and used it to patch the boot.img and it didn't work. Then the edit said you solved it by using adb to sideload magisk and that solved the problem. I'm still trying to understand how it did.