I've looked all through the forums and haven't found a clear tutorial on how to do this, if it can even be done.
I have a Verizon bought, bootloader unlocked, Magisk rooted Pixel 2 with TWRP and a custom kernel (Flash 2.06) installed running 8.1.0 with the December security patch.
How would I go about updating to future monthly patches (e.g. January's)?
I'd prefer to not lose all data (i.e. OTA-like), but am willing to start clean. Definitely do not want to risk losing the unlocked bootloader.
Is it possible? Willing to try if there is a semi-reasonable assurance of success.
Thanks.
If you're familiar with fastboot you can pull out the image.zip from the factory image and fastboot it with the command
Code:
fastboot update whateverthelongassimagename.zip
Leaving out the -w in that command won't wipe anything. If not, you'll have to get the stock boot image and take the OTA. Either way you'll have to temp flash TWRP again, installer to keep it there and your kernel and Magisk.
When we get an update that requires a new bootloader, that will have to be via OTA or adb sideload. VZW seems to have blocked us from fastbooting that.
JRJ442 said:
When we get an update that requires a new bootloader, that will have to be via OTA or adb sideload. VZW seems to have blocked us from fastbooting that.
Click to expand...
Click to collapse
I'm guessing on Verizon you wouldn't want to update the bootloader anyways since that would likely fix the current method of unlocking those phones.
clcdev said:
I'm guessing on Verizon you wouldn't want to update the bootloader anyways since that would likely fix the current method of unlocking those phones.
Click to expand...
Click to collapse
They most likely will patch the unlock yes, but they're not going to send an update that will relock the bootloaders that have been unlocked. So I wouldn't see an issue with updating it. Unless for some reason you need to lock it back. The bootloader in this months security update is still the same as last months. Version number is the same.
Related
So i held out taking the otas for a while to avoid losing root and am still on 4.2.2 post camera update. I know, it's sad, but I have root so i haven't been dying to update.
However, i just saw that sunshine will unlock my bootloader, which I'm going to do. What I'm confused about though is once i unlock my bootloader, how do I get to 4.4.4? Can I just revert everything to stock and take all of the otas (and then flash twrp to get root)? I heard that something in one of the otas changed something with the bootloader, so i don't know if taking that would cause problems with an unlocked bootloader or make me lose my unlocked status. Either way, could i just flash a 4.4.4 image directly from 4.2.2? If so where do i get a stock image to flash? Thanks for any help!
Once you have successfully unlocked, make sure you are status 3 unlocked in fastboot.
Once confirmed, you can use the rsd lite, and use the stock firmware from:
http://sbf.droid-developers.org/
Next, flash twrp for the ghost from their website.
Lastly if you want root flash supersu.
So can I flash a different OS version from the site that you linked? Or is that just to return to stock in anticipation of flashing TWRP and using that to flash a later android version?
rule of thumb is you cannot downgrade, only upgrade or revert to the same version you are already on
This seemed like the easiest route to a rooted 4.4.4... Unlock bootloader via Sunshine, and proceed as instructed here: http://forum.xda-developers.com/droid-ultra/general/unlocked-boot-xt-1080-restore-4-4-4-pre-t2883131
Data remains intact, unlocked bootloader warning on boot logo fixed, and TWRP (or Philz) flashed as recovery. Super easy. Good times.
Deleted. Redundant post.
Sent from my DROID Maxx
I'm in the same situation. I'm currently rooted on the post camera update and held off on the new ota's for a while. I want to do the sunshine unlock. My question is should I do the sunshine unlock, upgrade to the newest 4.4.4 then install twrp to root? This youtube.com/watch?v=_xVyJMtLDPgvideo gives pretty good instructions but I also want to take future OTA's. I understand you won't be able to unless you put the recovery back to stock.
Thanks in advanced
rcji said:
I'm in the same situation. I'm currently rooted on the post camera update and held off on the new ota's for a while. I want to do the sunshine unlock. My question is should I do the sunshine unlock, upgrade to the newest 4.4.4 then install twrp to root? This youtube.com/watch?v=_xVyJMtLDPgvideo gives pretty good instructions but I also want to take future OTA's. I understand you won't be able to unless you put the recovery back to stock.
Thanks in advanced
Click to expand...
Click to collapse
Yep true. Can't take OTAs with out stock recovery. But it is easy to flash Stock Recovery then back to TWRP after the OTA. Of course safest option is to flash stock fxz without wiping data before taking OTAs.
Personally have my own recovery and logo.bin script I keep for just this reason. Run RSDlite with the stock software take OTA (if no fxz yet for the OTA) then full bit and setup and finally flash the recovery and logo.bin I use.
Many ways of doing it just find its easier for me this way probably cause this is how I learned from trial and error is all. Probably an easier way though.
Hi,
I have an LG Nexus 5 (KTU84P, or "hammerhead") running Android KitKat 4.4.4. It is rooted using Chainfire's AutoRoot for the Nexus 5 for Android 4.4.4, and I have no custom ROM, simply Vanilla Android but with SuperSU. I am looking to update to Android L, version 5, and I have received a notification for the OTA update.
I understand that with OTA updates, your data will not be wiped, but you will lose root access. I have researched ways to keep the root, but they only appear to be for older versions of Android. I understand that I will lose root.
My question is, will I have to run the "oem unlock" (which I understand is the part of the whole rooting process which actually wipes your device), or will I just have to load Chainfire's AutoRoot? If I go through with it, I will use his AutoRoot for hammerhead for Android L, but basically my end goal is to root and update and not lose any data.
Thanks, if you need more info, let me know?
Autoroot will not wipe your data if your bootloader is already unlocked. Only if your bootloader was locked to begin with.
Nope. Once unlocked it stays unlocked unless you lock it yourself
frenziedfemale said:
Autoroot will not wipe your data if your bootloader is already unlocked. Only if your bootloader was locked to begin with.
Click to expand...
Click to collapse
musclehead84 said:
Nope. Once unlocked it stays unlocked unless you lock it yourself
Click to expand...
Click to collapse
Thank you both very much!
Of course with L you can no longer get the OTA if you have custom recovery. Just incase you weren't aware
rootSU said:
Of course with L you can no longer get the OTA if you have custom recovery. Just incase you weren't aware
Click to expand...
Click to collapse
I have updated OTA, and I kept EVERYTHING, even my root apps, but when I open up SuperSU I get a notification explaining that the Su binary is not installed, which is obviously removed when updating. Now, I'm just backing up my data. Another thing I would like to confirm is, if I use Chainfire's Auto Root for the Nexus 5 running Android 5.0, will it run OEM unlock again, and if it does, will I be affected considering my bootloader is already unlocked?
AudaxNovus said:
I have updated OTA, and I kept EVERYTHING, even my root apps, but when I open up SuperSU I get a notification explaining that the Su binary is not installed, which is obviously removed when updating. Now, I'm just backing up my data. Another thing I would like to confirm is, if I use Chainfire's Auto Root for the Nexus 5 running Android 5.0, will it run OEM unlock again, and if it does, will I be affected considering my bootloader is already unlocked?
Click to expand...
Click to collapse
If its unlocked, it can't be unlocked again.
Just a little info, afaik, if you update from KK to L and had an unlocked bootloader ('oem unlock'), like I did, your bootloader will get locked again after update, as it did with me.
So that "if it was unlocked it'll stay unlocked" is not correct.
D3abL3 said:
Just a little info, afaik, if you update from KK to L and had an unlocked bootloader ('oem unlock'), like I did, your bootloader will get locked again after update, as it did with me.
So that "if it was unlocked it'll stay unlocked" is not correct.
Click to expand...
Click to collapse
Odd. Hasn't locked for anyone else afaik
D3abL3 said:
Just a little info, afaik, if you update from KK to L and had an unlocked bootloader ('oem unlock'), like I did, your bootloader will get locked again after update, as it did with me.
So that "if it was unlocked it'll stay unlocked" is not correct.
Click to expand...
Click to collapse
There's a REALLY easy way to test that theory.
Open the factory image archives and check the script. Unless it runs 'fastboot oem lock' it isn't relocking it.
#stayparanoid
Don't you think this makes the trick?
"fastboot flash bootloader bootloader-hammerhead-hhz12d.img"
Hello.
Just got the news about 7.0 being released for this phone, and thought I would give it a shot. However, I have a few questions before I update . These are not in any particular order and I would love any help people can provide, even if you can't answer all the questions.
Since I got this phone, I unlocked the bootloader (I bought the unlocked version) and got TWRP, then installed SuperSU binary in order to use a few root apps on my phone. Then along came an OTA update. When I went to install it, I got a message informing me that the update couldn't be installed due to my system being modified, which was fair enough as I had installed SuperSU. I stopped bothering with OTA updates.
Now it's been a while and the Nougat update is out and apparently available over OTA. Is there a way for me to return to normal system and get this OTA without losing all of my personal data already on the phone? I understand that I'd probably have to get TWRP again, and what is recommended for root now? Can I "re-lock" my bootloader in order to get the OTA?
Basically: How can I get Nougat without losing my data?
Cheers, and thanks for reading! Quick answers would be appreciated.
DuoDex said:
Basically: How can I get Nougat without losing my data?
Click to expand...
Click to collapse
backup your data and then flash a ruu, either the nougat version if its available for your version or flash the marshmallow ruu then take the ota update.
What is your "fastboot getvar all" ?
alray said:
backup your data and then flash a ruu, either the nougat version if its available for your version or flash the marshmallow ruu then take the ota update.
What is your "fastboot getvar all" ?
Click to expand...
Click to collapse
I was able to get it by poking around in the forums, first got the RUU for 1.57, relocked bootloader, and am now OTAing the Nougat version (fingers crossed it all works). Thank you so much for replying!
Question: If I install TWRP (like I had before) and then Magisk, will I continue to be able to receive OTA updates? Backing up and reinstalling is such a pain and I'm afraid I will break something. Some people say you need to mount system read-only - how is this accomplished via TWRP exactly?
Thanks again!
DuoDex said:
I was able to get it by poking around in the forums, first got the RUU for 1.57, relocked bootloader, and am now OTAing the Nougat version (fingers crossed it all works). Thank you so much for replying!
Question: If I install TWRP (like I had before) and then Magisk, will I continue to be able to receive OTA updates? Backing up and reinstalling is such a pain and I'm afraid I will break something. Some people say you need to mount system read-only - how is this accomplished via TWRP exactly?
Thanks again!
Click to expand...
Click to collapse
I just went thru the process or putting magisk on nougat. You'll want to use twrp 3.0.3-4 for it. From what I understood from the user who clued me into it, magisk will let you take OTA's and use android pay since it won't mess with dm-verity, SELinux or safetyNet. I can definately confirm the Android pay part at least. I did notice however i had to turn on magisk hide in the settings to get it to pass the safetynet check.
as for mounting the system as read only, the first time i booted into twrp it asked me to either slide the lock to modify /system or check a box to mount it as read only and that was it.
txag2011 said:
I just went thru the process or putting magisk on nougat. You'll want to use twrp 3.0.3-4 for it. From what I understood from the user who clued me into it, magisk will let you take OTA's and use android pay since it won't mess with dm-verity, SELinux or safetyNet. I can definately confirm the Android pay part at least. I did notice however i had to turn on magisk hide in the settings to get it to pass the safetynet check.
as for mounting the system as read only, the first time i booted into twrp it asked me to either slide the lock to modify /system or check a box to mount it as read only and that was it.
Click to expand...
Click to collapse
I was mistaken, Magisk now patches dm-verity and forced encryption. You should be able to take an OTA by flashing the stock recovery though, and failing that by also restoring the system image backup you make in TWRP before modifying or mounting system.
According to the Verizon Galaxy S5 Update Page:
Android® Security Patch Level: 2017–08-01
The current software update gives you the most up to date Android security patches on your device.
Click to expand...
Click to collapse
This is basically the same thing they are doing with other devices. Since Samsung never released their September Security patch due to them addressing the BlueBorne problem, they have been re-releasing the QH* updates as QI* but they include the BlueBorne patch. For some reason, Verizon didn't include the BlueBorne patch in the changelog like they have been for every other phone.
For example. The Galaxy S6, Galaxy S8, and Galaxy S8+ updates all say
Includes: Blueborne security patch
The current software update gives you the most up to date Android® security patches on your device.
Click to expand...
Click to collapse
Who knows why they chose to include the exact same changelog as the prior update with the same security patch. Whatever. Verizon sucks. We all know it.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_Aboot.tar.md5.zip
Also, I'm not sure how much longer I'll be doing this though because the screen on my S5 is going bad (flickering and flashing green whenever I bring it out of sleep) so this weekend I'm getting an S8+.
so its safe to say that the new modem ql2 is pretty much the same sa the previous update?
Updated to this build from QH2, flashed in odin, then booted up, reflashed TWRP and SU, froze system updater all good. If you do end up leaving, this will just be another loss for this model as no one else is updating the stock images anymore.
Thank you for your work on this. Does this have root, and if not, do those of us with locked bootloaders have a way to keep root and safestrap?
Tell us how the S8+ goes and if you can unlock the bootloader and root that. Thanks again!
Dudash said:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_Aboot.tar.md5.zip
Also, I'm not sure how much longer I'll be doing this though because the screen on my S5 is going bad (flickering and flashing green whenever I bring it out of sleep) so this weekend I'm getting an S8+.
Click to expand...
Click to collapse
For the record, this loses root, and loses safestrap. I'm too dumb to know how to root this since I can't get TWRP on this phone, so I'm going to hope the way back to root and safestrap is get back Kitkat and then up to PB1 starting over using these steps.. This will probably be better for someone who knows what they're doing or just wants to upgrade for the security updates and doesn't care about root.
androidman807 said:
Thank you for your work on this. Does this have root, and if not, do those of us with locked bootloaders have a way to keep root and safestrap?
Tell us how the S8+ goes and if you can unlock the bootloader and root that. Thanks again!
Click to expand...
Click to collapse
I have a 15 Emmc chip and unlocked the bootloader via this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
I flashed EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip to my phone. I also have TWRP installed.
Now, if I understand all this correctly, I can simply flash your Developler Boatloader friendly version via TWRP? This will upgrade my OS to the latest update? Then flash Magisk to get root back?
This all seems too simple.
You will also have to re-flash TWRP via Odon.
kevin98208 said:
I have a 15 Emmc chip and unlocked the bootloader via this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
I flashed EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip to my phone. I also have TWRP installed.
Now, if I understand all this correctly, I can simply flash your Developler Boatloader friendly version via TWRP? This will upgrade my OS to the latest update? Then flash Magisk to get root back?
This all seems too simple.
Click to expand...
Click to collapse
HolyHog said:
You will also have to re-flash TWRP via Odon.
Click to expand...
Click to collapse
I too followed the instructions in the thread above for a CID 15 eMMC.
I was unable to flash the "G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_ Aboot.tar.md5.zip" from the OP using TWRP, but was able to do it no problem using Odin 3.12 (AP option).
After flashing that I then used Odin again (AP option) to flash the latest TWRP (https://dl.twrp.me/klte/twrp-3.1.1-0-klte.img.tar.html). I then did another factory reset on the phone (since I had already just wiped my data following the bootloader instructions) and reinstalled Magisk from TWRP and MagiskManager.
Everything looks great so far. Thanks for this update OP and for those of you providing guidance.
I have G900VVRU2DPD1 with unlocked bootloader and twrp 3.0.0-0.
Can I flash the
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_ Aboot.tar.md5.zip ?
If yes, after flashing, will my bootloader remain PD1 unlocked? Is it OK to have unlocked PD1 bootloader with DQI2 firmware?
Will the TWRP and root be lost? And how I can get back TWRP? Using ODIN? If root is lost then can not use flashify to flash TWRP.
If using odin to flash TWRP, then I can just flash supersu zip in zip to get root back, right?
Thanks.
I guess this is slightly off topic since it's not about this specific firmware version, but here goes ~
How do you guys go about extracting firmware/modems from stock ROM updates?? It boggles my mind lol. I'm running a OP3T now, but am working on an old device (and I still have my old S5 too). Over the years it appears people are now able to do this process for most devices and make it flashable one way or another.
I wish I understood how this gets done (and possibly figure out how to do it myself). Would love a guide / video / brief explanation with terms I could look up if it's long & involved??
Thanks for the work!
purplepenguin said:
How do you guys go about extracting firmware/modems from stock ROM updates??
Click to expand...
Click to collapse
Stock ROM update is just a tar archive with files inside.
The names of the files are mostly self-explaining.
Use some tool to access the archive, like Total Commander or 7zip archiver.
bbsc said:
Stock ROM update is just a tar archive with files inside.
The names of the files are mostly self-explaining.
Use some tool to access the archive, like Total Commander or 7zip archiver.
Click to expand...
Click to collapse
Hmmm and then to make flashable??
purplepenguin said:
Hmmm and then to make flashable??
Click to expand...
Click to collapse
Just pack what you want into tar archive and it will be flashable.
No need to attach checksum.
But it's possible too.
Say, this tar-file is flashable:
Missing apps
TraderJack said:
and reinstalled Magisk from TWRP and MagiskManager.
Click to expand...
Click to collapse
Can I reuse the same Magisk from the "EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip" file from the other thread on how to unlock bootloader and root, or should I download the latest Magisk and MagiskManager?
Edit 1: Okay, I installed Magisk after updating to the latest QI2 and am rooted. However, I found that I'm missing busybox and safestrap. Do I have to reinstall both of those as well or can I just reinstall busybox?
Also, QI2 lost tether/hotspot capability as it reverted back to asking to purchase the service (I'm also on the old grandfathered unlimited plan)...is there a way to get it back as when on rooted QB2?
Edit 2: Did some more research while hiding at work...so now I know, having TWRP recovery is enough and just need to reinstall busybox.
Now still need to find a way to get hotspot capability back like when on the rooted magisk QB2...
Thanks
Hi,
My Pixel 3a as an unlocked bootloader and is rooted.
Usually, when I update my system every month, I get the OTA update zip on google website to do the update and only patches the boot.img from the factory image with magisk to keep the root.
But this month, we get Android 12 and I saw on this thread : https://www.xda-developers.com/how-to-install-android-12/ that it was recommended not to use the OTA update for updating to Android 12 on unlocked bootloader.
As I don't know why, can you explain me if it is or not dangerous or impossible, and eventually why I have to use the factory image to install this new system ?
I know that every time i made a wipe data (even if i know there's a way to delete the -w in the bat file but it's not recommended) it made me a day to restore all my apps and configurations... So if i can avoid this, I'd prefer.
Thanks in advance
oldbear3 said:
But this month, we get Android 12 and I saw on this thread : https://www.xda-developers.com/how-to-install-android-12/ that it was recommended not to use the OTA update for updating to Android 12 on unlocked bootloader.
Click to expand...
Click to collapse
I don't see this warning on that page?
The point of the full OTA sideload is that works with both locked and unlocked bootloaders.
The factory image only works with unlocked bootloaders.
I have a 4a with unlocked bootloader and just upgraded using the OTA and it was fine. I normally use the factory image (removing the -w arg) but found warnings on the internet that this would break when upgrading to Android 12 so I did the OTA instead.
I was even able to re-root with Magisk 23 as normal, which is apparently not possible for newer devices (eg. Pixel 5 guide: https://forum.xda-developers.com/t/guide-update-to-and-re-root-android-12.4345627/).
a1291762 said:
I don't see this warning on that page?
The point of the full OTA sideload is that works with both locked and unlocked bootloaders.
The factory image only works with unlocked bootloaders.
I have a 4a with unlocked bootloader and just upgraded using the OTA and it was fine. I normally use the factory image (removing the -w arg) but found warnings on the internet that this would break when upgrading to Android 12 so I did the OTA instead.
I was even able to re-root with Magisk 23 as normal, which is apparently not possible for newer devices (eg. Pixel 5 guide: https://forum.xda-developers.com/t/guide-update-to-and-re-root-android-12.4345627/).
Click to expand...
Click to collapse
Great, thanks a lot. Made just right now and it works perfectly. The root also worked for me.
a1291762 said:
I don't see this warning on that page?
Click to expand...
Click to collapse
About this question, it's written for OTA Updates :
"To install the stable build, you need to sideload the appropriate OTA package for your device from Recovery through ADB. This method will also work for Google Pixel devices with a locked bootloader"(but as I re-read it, I see that it's written that it "also work" with locked bootloader"). For the full update, it's written "If you have an unlocked bootloader on a Google Pixel device, you need to flash the full factory image of the Android 12 via Fastboot"...so I thought it was the only option.
But you're right, it's not exactly what's written.