Related
It installed on top of any firmware (except firmware with the build date is higher than installed)(but you can edit updater-script). It can be installed through TWRP. Do not check the current state of the system. Installed without resetting.
https://developers.google.com/android/nexus/ota
what happens to root and xposed after installing them ? and currently i'm on MMB29K can i download MOB30H directly ? also do i lose any data in the process ?
xxqxpxx said:
what happens to root and xposed after installing them ? and currently i'm on MMB29K can i download MOB30H directly ? also do i lose any data in the process ?
Click to expand...
Click to collapse
Just downloaded this and unzipped it, but have not tried it yet. Looks like you just flash in recovery, so you should just be able to flash xposed and supersu after the zip. Only a system file in the ota zip, no userdata so you should be fine to upgrade. As always, back up first
You flash these using adb sideload as you would any other OTA zip. This are just official links from Google as opposed to us having to capture them and post in the OTA thread
EDIT: I would appear to be wrong. Although these are called 'OTA' there are full ROMs, and not incremental updates, that can be flashed via adb sideload as opposed to fastboot images. MUCH better if you don't wanna wipe the phone if you have a locked bootloader
One can't flash these with systemless root right (or modified system)?!
I have downloaded an OTA of OS update for my HTC M7 and saved it in internal memory . Now how can I install that OTA from internal memory ?
PS: Currently I don't have have any Laptop or PC around me .
Thanks
risharaj3 said:
I have downloaded an OTA of OS update for my HTC M7 and saved it in internal memory . Now how can I install that OTA from internal memory ?
PS: Currently I don't have have any Laptop or PC around me .
Thanks
Click to expand...
Click to collapse
If your phone is S-ON the ota update process must be started from Settings ---> Phone ---> About.
To manually install an ota update, your phone must be s-off, save the ota zip file at the root in your phone memory, boot the stock recovery (not twrp or cwm) version matching your firmware number. When the recovery start (red triangle) press volume up and power to enter stock recovery menu, select "apply from phone storage" and select the ota file.
alray said:
If your phone is S-ON the ota update process must be started from Settings ---> Phone ---> About.
To manually install an ota update, your phone must be s-off, save the ota zip file at the root in your phone memory, boot the stock recovery (not twrp or cwm) version matching your firmware number. When the recovery start (red triangle) press volume up and power to enter stock recovery menu, select "apply from phone storage" and select the ota file.
Click to expand...
Click to collapse
But what if I am s-off relocked ... Can I install through settings?
markg546 said:
But what if I am s-off relocked ... Can I install through settings?
Click to expand...
Click to collapse
yes, but in all situations, your /system partition must be 100% stock. Your cid and mid must be correct for the software version and the ota updates must be the right version (can't skip versions, it must be done incrementally).
What is your "fastboot getvar all" output? Might be easier to just flash the latest RUU instead of doing the OTA updates...
alray said:
If your phone is S-ON the ota update process must be started from Settings ---> Phone ---> About.
To manually install an ota update, your phone must be s-off, save the ota zip file at the root in your phone memory, boot the stock recovery (not twrp or cwm) version matching your firmware number. When the recovery start (red triangle) press volume up and power to enter stock recovery menu, select "apply from phone storage" and select the ota file.
Click to expand...
Click to collapse
alray said:
yes, but in all situations, your /system partition must be 100% stock. Your cid and mid must be correct for the software version and the ota updates must be the right version (can't skip versions, it must be done incrementally).
What is your "fastboot getvar all" output? Might be easier to just flash the latest RUU instead of doing the OTA updates...
Click to expand...
Click to collapse
Running XenonHD which kinda supports OTA update...
I also have MultiROM installed
It just sucks having to reflash everytime there is an update
markg546 said:
Running XenonHD which kinda supports OTA update...
I also have MultiROM installed
It just sucks having to reflash everytime there is an update
Click to expand...
Click to collapse
What ota files are you trying to flash (post a link)? I thought you were talking about official ota updates from HTC...
alray said:
What ota files are you trying to flash (post a link)? I thought you were talking about official ota updates from HTC...
Click to expand...
Click to collapse
There are HTC OTA updates??
The OTA updater app just redirects you to the download page
markg546 said:
There are HTC OTA updates??
Click to expand...
Click to collapse
How do you think phone manufacturers are updating their phones? With OTA updates.
Latest ota update from htc (irrc was in 2015) was 7.xx.xxx.51 (android 5.0.2 with HTC Sense 6). Any phone running an older official version than that would receive a notification to download and install the ota update, even in 2017.
Now for custom rom update, refer to your rom thread for instructions. In most cases you only need to flash the zip using twrp. If this is a major update you might need to do a full wipe...
Sorry for the confusion but usually when ppl talk about "ota updates" they are referring official HTC software (there are not that much custom roms supporting ota updates).
I used Xenon a few months ago. iirc i was just flashing the update using twrp without wiping.
alray said:
How do you think phone manufacturers are updating their phones? With OTA updates.
Latest ota update from htc (irrc was in 2015) was 7.xx.xxx.51 (android 5.0.2 with HTC Sense 6). Any phone running an older official version than that would receive a notification to download and install the ota update, even in 2017.
Now for custom rom update, refer to your rom thread for instructions. In most cases you only need to flash the zip using twrp. If this is a major update you might need to do a full wipe...
Sorry for the confusion but usually when ppl talk about "ota updates" they are referring official HTC software (there are not that much custom roms supporting ota updates).
I used Xenon a few months ago. iirc i was just flashing the update using twrp without wiping.
Click to expand...
Click to collapse
woah I am not that dumb ... I thought that HTC still made OTA updates (like new versions)
Last time I flashed without wiping ,I got stuck in a bootloop
alray said:
If your phone is S-ON the ota update process must be started from Settings ---> Phone ---> About.
To manually install an ota update, your phone must be s-off, save the ota zip file at the root in your phone memory, boot the stock recovery (not twrp or cwm) version matching your firmware number. When the recovery start (red triangle) press volume up and power to enter stock recovery menu, select "apply from phone storage" and select the ota file.
Click to expand...
Click to collapse
I tried yesterday and I reached below location :
../
0/
legacy/
obb/
Where are this location ??? Currently my downloaded OTA is in Download folder ??? So exactly what would be my root location ?? Can you please elaborate , as I am new these terms .
Is there any chance that this process would brick my phone ???
risharaj3 said:
I tried yesterday and I reached below location :
../
0/
legacy/
obb/
Where are this location ??? Currently my downloaded OTA is in Download folder ??? So exactly what would be my root location ?? Can you please elaborate , as I am new these terms .
Is there any chance that this process would brick my phone ???
Click to expand...
Click to collapse
the root of your internal storage is /data/media/0 also referred as /sdcard (symlink). For example your download folder is located at /data/media/0/download (or /sdcard/download). Move your ota file one folder up (from /download to /sdcard) and you'll see it when in recovery mode by selecting 0/
So I unlocked my bootloader and installed TWRP on the p20pro. Just received status that there's full update available. I downloaded and try to install, but the phone would boot into recovery and nothing happens. How should I go about updating the firmware on the device with TWRP?
Bump
Sent from my SM-G955F using Tapatalk
twe90kid said:
So I unlocked my bootloader and installed TWRP on the p20pro. Just received status that there's full update available. I downloaded and try to install, but the phone would boot into recovery and nothing happens. How should I go about updating the firmware on the device with TWRP?
Click to expand...
Click to collapse
Either reflash the stock recovery or keep TWRP and use HuRUpdater Tool (search for it here on XDA)
Pretoriano80 said:
Either reflash the stock recovery or keep TWRP and use HuRUpdater Tool (search for it here on XDA)
Click to expand...
Click to collapse
Hi.Same issue. Does reflash stock recover wipe all my datas ?
How to use HuruUpdater as ther current TWRP does not allow to access on local files (no decryption).
THanks
JP
here's the details
- Unlock bootloader from Huawei : http://emui.huawei.com/en/plugin/unlock/index
- (It's still possible to unlock the bootloader. Just send an email to your local support or tweet them (HuaweiUK). They'll ask you for some info and send you the unlock code. Took me two days to get the code)
- TWRP : https://forum.xda-developers.com/hua...2-1-0-t3779400
- hurupdater_0.3.zip https://forum.xda-developers.com/hon...overy-t3769279 also works perfectly for P20 Pro
Magisk file (if you want to get rooted) https://******************/Magisk/Magisk-v16.0.zip
Now, get patient, an old man did it!
In future direct links for our CLT-L29 european(C432)..
http://pro-teammt.ru/firmware-databa...irmware_page=0
Click on FullOTA-MF (only!) and click on filelist I had to click several times on filelist to get the links to the 3.zip files needed (thinks to Tecalote for his patience!)
So, the difficult part was to rename the.zip files( I went to #32, page 4 and renamed exactly like it was : Download firmware files (for official firmware use Huawei Firmware Finder).
1. Put files you want to flash in a seperate folder on sdcard.
Supported zip files to flash are (name must match):
o update.zip (use FullOTA file)
o update_full_hw.zip
o update_data_full_public.zip
2. Optional: Put recovery.img (rename your TWRP downloaded "recovery_ramdisk twrp_clt_0.1.img") in same folder if you want to keep custom recovery.
3. Put HuRUpdater zip in same folder. Example:
4. Select only HuRUpdater to flash in custom recovery.
5. Follow instructions on screen. Flashing can take multiple minutes.
Then I followed exactly step by step.
It didn’t work and I had error messages flashing with hurupdater_0.3.zip:
No update_data_public.zip found in /sdcard/”name of your folder”
No update_all_hw.zip in /sdcard/”name of your folder”
As you can see the name of the .zip files did’nt match #32.
I renamed exactly as asked to get rid of the error messages, and BINGO!
Click to expand...
Click to collapse
Update CLT-L29 8.1.0.128(C432) with TWRP already installed
Update CLT-L29 8.1.0.128(C432) with TWRP already installed
Hello,
Many thanks to all of your for your kind support , so I intend to create a summary of what I did, hoping it could help others !
I had already unlock previsouly my Bootloader (of course, else this topic would not exist) via Unlock bootloader from Huawei :https://emui.huawei.com/en/unlock_detail
I already had TWRP and Magisk installed and wanted to get the latest official firmware for my P20-PRO-CLT-L29(C432) - > CLT-L29 8.1.0.128(C432).
When intending to update (from my phone), it could not work (I allways boot back to TWRP), upgrade failed.
Special credits to : @Pretoriano80
sarichter said:
@sarichter
SpH1nX said:
@SpH1nX
Start with : Do your Backup !
Removed then all security (screen unlock in developper mode =0) , no pin, no pattern, no password, no fingerprint, no faceunlock
Download the following set of files (that I've uploaded and ready to use) : https://mega.nz/#F!pEpRDB7R!pmPDjlqgtdHTs39gyLdJhg
(nota : my upload is quite slow, so please wait some hours before it is available)
It contains : HuRUpdater_0.3.zip, Magisk-v16.4-Beta.zip, twrp_clt_0.1.img, recovery.img
, update.zip, update_all_hw.zip, update_data_public.zip
- On your phone create a folder including all files from the package above.
- Boot in TWRP
- Install : HuRUpdater zip from the folder where you had put all files (no issue with decryption, at least in my case)
Nota : I had almost an heart attack during installation as it did a reference to CLT-09... not CLT-29 but it works and this despite some strange error messages.
When achieved : wipe/cache dalvik.
Phone will reboot and optimize the apps.
In my case, I lost my root access and TWRP, so I've done it again, but normally it was supposed to stay when using HurUpdater
Install TWRP (again if needed) :
- Start your device in fastboot mode
- Install the recovery using the following command : fastboot flash recovery_ramdisk twrp_clt_0.1.img
Restart with this command: fastboot reboot
Important : As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP, so the device will boot to TWRP. This is to avoid that the device boot to OS,overwritting TWRP recovery.
Reboot again in recovery
(re)Install : Magisk-v16.4-Beta.zip
Have fun,
JPh
Click to expand...
Click to collapse
Click to expand...
Click to collapse
You lost twrp because you didn't rename the file as recovery.img
SpH1nX said:
You lost twrp because you didn't rename the file as recovery.img
Click to expand...
Click to collapse
I did...but I might have used the wrong version of twrp.
Hi is there any body who testet the New CLT-029 C432B131 (8.1.0.131) ? Ihave try to download via the Firmware Finder but is Says that the File is no longer availiable on the server.
Is there another source where iam able to download the 3 Firmware files to Update with Huru Updater?
blackst225 said:
Hi is there any body who testet the New CLT-029 C432B131 (8.1.0.131) ? Ihave try to download via the Firmware Finder but is Says that the File is no longer availiable on the server.
Is there another source where iam able to download the 3 Firmware files to Update with Huru Updater?
Click to expand...
Click to collapse
You're OT here, try asking here https://forum.xda-developers.com/hu...lt-l29c432b131-firmware-improvements-t3804068
twe90kid said:
here's the details
Click to expand...
Click to collapse
THANK YOU! THIS WORKED SO PERFECTLY!
Until now, I tried the following:
Back up my data and apps to SD card with EMUI Backup App
Download OTA update (it first downloads the incremental ~100-200MB update) and click install
This doesn't work of course - TWRP tries to execute the update command but dies with error messages
Reboot, try downloading/installing updates again, the downloader then downloads the -FULL update
Extract recovery.img from update.zip>update.app
Flash stock recovery over TWRP
Initiate update again from Update App (System Settings)
Update runs smoothly, but bootloader is locked again afterwards
Restore from backup, flash TWRP again, flash SuperSU again
BUT THIS IS MARVELOUS! I will only lose SuperSU and Xposed, and given that HuRUpdater is provided with the correct filenames including TWRP renamed to recovery.img, I will just have to install SuperSU and Xposed again after updating the firmware.
It worked flawlessly with the stock firmware files from update.hicloud.com, and you'll usually find all the links a few hours after the release somewhere on the internet.
EdRoxter said:
THANK YOU! THIS WORKED SO PERFECTLY!
Until now, I tried the following:
Back up my data and apps to SD card with EMUI Backup App
Download OTA update (it first downloads the incremental ~100-200MB update) and click install
This doesn't work of course - TWRP tries to execute the update command but dies with error messages
Reboot, try downloading/installing updates again, the downloader then downloads the -FULL update
Extract recovery.img from update.zip>update.app
Flash stock recovery over TWRP
Initiate update again from Update App (System Settings)
Update runs smoothly, but bootloader is locked again afterwards
Restore from backup, flash TWRP again, flash SuperSU again
BUT THIS IS MARVELOUS! I will only lose SuperSU and Xposed, and given that HuRUpdater is provided with the correct filenames including TWRP renamed to recovery.img, I will just have to install SuperSU and Xposed again after updating the firmware.
It worked flawlessly with the stock firmware files from update.hicloud.com, and you'll usually find all the links a few hours after the release somewhere on the internet.
Click to expand...
Click to collapse
I have a few questions regarding this method to update :
Do I need to make a new backup using twrp after this update since the system files changed due to the update? (correct if i'm wrong i'm a previous iphone owner this my first android device)
Is the any method to force update 8.0 even it will erase every thing and after that just flash twrp and restore backup (i think all the methods mentioned are complicated for me)
P10 Lite
twe90kid said:
here's the details
Click to expand...
Click to collapse
Hi, I have the same problem but with my Huawei P10Lite WAS L1XA with firmware oreo installed from the phone and on reboot enters twrp mode.
Can I ask you to look for the files for my model?
(I spent three hours looking for those files but I could not find anything) ...
Is it only me who not receive OTA till now?
tanipat said:
Is it only me who not receive OTA till now?
Click to expand...
Click to collapse
Same here, always got day 1 in the past.
Me too, so i had manully sideload it
FlatOutRU said:
Me too, so i had manully sideload it
Click to expand...
Click to collapse
Where can you get it to sideload? Any thread with instructions?
swear0730 said:
Where can you get it to sideload? Any thread with instructions?
Click to expand...
Click to collapse
Lol, google it ?
https://developers.google.com/android/ota
FlatOutRU said:
Lol, google it
https://developers.google.com/android/ota
Click to expand...
Click to collapse
lolol I did google it and downloaded it a couple of days ago. That file is 1.5gb and from what I've read the update size is 9.3mb.
Maybe I've misunderstood the description on the download for the full OTA:
"This page contains full OTA update packages that allow you torestore your Nexus or Pixel device's original factory firmware. You will find these files useful if you have experienced a failure to take an OTA. This has the same effect as flashing the corresponding factory image, [but without the need to wipe the device or unlock the bootloader./I]"
Maybe I'm tripping over the two italicized parts as it doesn't say whether it will wipe or whether it will retain my installed programs and data. Perhaps, "without the need to wipe the device" could mean that it will do it automatically.
Without an available nandroid backup I am reluctant to flash anything that is described as "Full".
Are you saying that flashing the Full OTA image at 1.5gb will not wipe installed programs and data?
At this point I'm pretty sure that is what you're implying. Can you confirm so I can proceed confidently?
TIA
swear0730 said:
lolol I did google it and downloaded it a couple of days ago. That file is 1.5gb and from what I've read the update size is 9.3mb.
Maybe I've misunderstood the description on the download for the full OTA:
"This page contains full OTA update packages that allow you torestore your Nexus or Pixel device's original factory firmware. ou will find these files useful if you have experienced a failure to take an OTA. This has the same effect as flashing the corresponding factory image, [but without the need to wipe the device or unlock the bootloader./I]"
Maybe I'm tripping over the two italicized parts as it doesn't say whether it will wipe or whether it will retain my installed programs and data. Perhaps, "without the need to wipe the device" could mean that it will do it automatically.
Without an available nandroid backup I am reluctant to flash anything that is described as "Full".
Are you saying that flashing the Full OTA image at 1.5gb will not wipe installed programs and data?
At this point I'm pretty sure that is what you're implying. Can you confirm so I can proceed confidently?
TIA
Click to expand...
Click to collapse
Yeah just follow instructions from that link and nothing will be erased
I was also confused about the 1.5gb file vut everything went ok
FlatOutRU said:
Yeah just follow instructions from that link and nothing will be erased
I was also confused about the 1.5gb file vut everything went ok
Click to expand...
Click to collapse
Did you retain root? Or did you have to re-patch the boot.img?
troymz1 said:
Did you retain root? Or did you have to re-patch the boot.img?
Click to expand...
Click to collapse
I don't know the proper way. Just to be sure i flashed stock boot/dtbo ans then sideloaded. Then did root thing again
troymz1 said:
Did you retain root? Or did you have to re-patch the boot.img?
Click to expand...
Click to collapse
This is the full ota file. Because you sideload it you can't retain root (you have to enter recovery - ota file is installed to the other slot). In the ota file you find also the boot.img to patch it and reapply root by flashing the patched boot.img through fastboot. Also i didn't receive the ota through air (even deinstalled magisk before checking for ota). Maybe Google changed something.... Gonna see what happens next month.
I did on Jan. 31. ATT pixel 4XL
I've always had very spotty success receiving and completing OTA updates from Google when on a rooted phone. On my 3a XL, I've been successful taking an OTA update probably 2 out of 8 months. So I have become an expert in sideloading the update. (My family's two other 3a XLs receive updates immediately and have no trouble completing them, so it definitely related to the fact that I'm rooted - even though I uninstall Magisk prior to attempting an update).
I created a thread in the Pixel 3a forum with directions on how to sideload and root your phone, but I will simply post that information here.
To sideload an update, follow these instructions. - This will not factory reset your phone and you will not loose any data or files.
Optional Step 1 - Uninstall Magisk (so that it restores the stock boot.img). If you find yourself unable to boot into recovery, you will have to restore the stock boot.img. I've run into this issue on some Android 10 images, but not all.
Step 2 - Download to your computer the correct OTA image from here
Step 3 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 4 - Boot your phone into recovery (type the command "adb reboot recovery").
Step 5 - The phone will have a green android robot with a red sign over it's open access panel. Press the power button and then the volume up button while still holding down the power button.
Step 6 - Select "Apply update from ADB" using the volume buttons to highlight the choice and the power button to select it to enter the sideload mode.
Step 7 - Using your computer, type "adb sideload ota_file.zip" where ota_file.zip is the name of the OTA file you downloaded in step 2.
Step 8 - Once the update finishes, reboot the phone to complete the update process. (The initial reboot can take some time as it has to optimize the apps behind the scenes, but it does so without the normal "Optimizing Apps" splash screen normally seen when taking an OTA update. Please be patient and let the phone finish the process. The more apps you have, the longer it may take. Do not force a reboot or turn it off during this initial boot).
After sideloading the OTA, you will have to reroot your phone using the magisk boot image patch installation method.
Step 1 - Obtain a stock boot.img file for the OS version/update that you are currently on. The easiest method is probably to download the applicable full stock image directly from Google. Unzip the files and unzip the second folder and you should find the boot.img file inside.
Step 2 - Copy the stock boot.img file to your phone's storage - probably to /sdcard or to /sdcard/downloads
Step 3 - Download and install the Magisk manager app on your phone. (link to the latest version can be found here). At one time early in the Android 10 cycle, users had to use the "Canary" Magisk builds. This is no longer true and you can use the stable version builds as long as it is version 20 or later. Of course users are still able to use the beta or Canary builds if they desire, but it is no longer a requirement.
Step 4 - Using the Magisk manager app, press "Install --> Install --> Select and Patch a File" - select the stock boot.img file that you put on your phone in step 2.
Step 5 - Magisk will modify the stock boot.img file and create a patched boot image file. It will save this modified file at "sdcard/Download/magisk_patched.img"
Step 6 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 7 - Copy the patched boot image from your device to your PC and the adb folder. If you can’t find the file on your phone via MTP or Windows Explorer, you can pull the file by typing the command "adb pull /sdcard/Download/magisk_patched.img"
Step 8 - Boot your phone into the bootloader (type the command "adb reboot bootloader").
Step 9 - Flash the patched boot image to your device using this command, "fastboot flash boot magisk_patched.img"
Step 10 - Reboot (using command "fastboot reboot").
I hope that helps.
I haven't gotten the update on mine (generic Google 4 XL, not carrier tied) yet either for this month. A few days ago if I pressed the "Check for update" button, about every dozen or so tries it would flash for a second or two 'Preparing system update' and then go back to "Your system is up to date", of which it's not since it's on the Jan 2020 update. Is there a particular file or set of files that the local phone and it's OS compares to the 'big updater in the sky' and then if different (local date/time stamp older type thing) the update starts? I'm looking for a way to manipulate a local file to force the OTA so I don't have to mess with the downloading and sideloading of the OTA and rerooting, it's just so nice to have Magisk do all that for me. I've done the sideload plenty of times, I'd just rather not have to do it.
Any ideas or suggestions?
YDBB said:
I haven't gotten the update on mine (generic Google 4 XL, not carrier tied) yet either for this month. A few days ago if I pressed the "Check for update" button, about every dozen or so tries it would flash for a second or two 'Preparing system update' and then go back to "Your system is up to date", of which it's not since it's on the Jan 2020 update. Is there a particular file or set of files that the local phone and it's OS compares to the 'big updater in the sky' and then if different (local date/time stamp older type thing) the update starts? I'm looking for a way to manipulate a local file to force the OTA so I don't have to mess with the downloading and sideloading of the OTA and rerooting, it's just so nice to have Magisk do all that for me. I've done the sideload plenty of times, I'd just rather not have to do it.
Any ideas or suggestions?
Click to expand...
Click to collapse
If your rooted, the system OTA will fail. Your only options are to side load the OTA, try the magisk OTA update method, or fastboot the factory image.
Badger50 said:
If your rooted, the system OTA will fail. Your only options are to side load the OTA, try the magisk OTA update method, or fastboot the factory image.
Click to expand...
Click to collapse
That's not what I've experienced. I had been using an Essential PH-1 (actually have two of them) and Magisk and every month Essential would put out the update as soon as, or frequently even a day or two sooner than google, and I simply did the 'Release Images' in Magisk, did the OTA and then the 'install Magisk to inactive slot' and reboot and I always stayed rooted and up to date. I got the Pixel 4 XL in November sometime and for the first two monthly updates (-> Dec 2019 and Jan 2020) the same process worked fine. Only now with the Feb 2020 update out there it's not taking / recognizing that it's there.
I did about a week ago see there was a Google Play system update that was pending and did it, and did the required reboot after. That didn't 'unroot' me. I'm wondering if that Google Play system update messed something up?
YDBB said:
That's not what I've experienced. I had been using an Essential PH-1 (actually have two of them) and Magisk and every month Essential would put out the update as soon as, or frequently even a day or two sooner than google, and I simply did the 'Release Images' in Magisk, did the OTA and then the 'install Magisk to inactive slot' and reboot and I always stayed rooted and up to date. I got the Pixel 4 XL in November sometime and for the first two monthly updates (-> Dec 2019 and Jan 2020) the same process worked fine. Only now with the Feb 2020 update out there it's not taking / recognizing that it's there.
I did about a week ago see there was a Google Play system update that was pending and did it, and did the required reboot after. That didn't 'unroot' me. I'm wondering if that Google Play system update messed something up?
Click to expand...
Click to collapse
GPS system updtae usually doesn't mess with anything root At least it didn't on my P2XL & 4XL.. Monthly security updates are a diffent story though on pixel devices where root is concerned.
Still no OTA eithers. Don't want to side load either. I'm on QQ1B.200105.004. Anybody on this build get it?
MicroMod777 said:
Still no OTA eithers. Don't want to side load either. I'm on QQ1B.200105.004. Anybody on this build get it?
Click to expand...
Click to collapse
Me neither
I'm currently on the same QQ1B.200105.004 build. They (google) did the same thing (a long delay into the month) this past month, hopefully not a recurring theme.
MicroMod777 said:
Still no OTA eithers. Don't want to side load either. I'm on QQ1B.200105.004. Anybody on this build get it?
Click to expand...
Click to collapse
Same build, no OTA may be this could force me to do sideload update which terrible
I'm asking for help because this has happened for two months now, and I'm wondering if the process has changed with the new unified Magisk.
The March Android 11 update has been posted, so -- just as I did in February::
1. On my computer, I
1a. Downloaded the factory image;
1b. Extracted the boot.img; and
1c. Sent it to my phone's Download folder.
2. On my phone, I
2a. Had Magisk "patch (the) selected file";
2b. Transferred the new patched boot image, magisk_patched_FKPSk.img, back to the computer; and
2c. Put the phone into fastboot mode.
3. Back on my computer, in adb, performed the "fastboot flash boot magisk_patched_FKPSk.img."
adb successfully flashed to boot_a, then I rebooted the phone. It rebooted surprisingly quickly.
Going into "System / Advanced / System Update," it still says
Android security update: January 5, 2021
So, what am I doing wrong? Should I force adb to flash to boot_b instead?
Thanks for any ideas!
NickEspo said:
I'm asking for help because this has happened for two months now, and I'm wondering if the process has changed with the new unified Magisk.
The March Android 11 update has been posted, so -- just as I did in February::
1. On my computer, I
1a. Downloaded the factory image;
1b. Extracted the boot.img; and
1c. Sent it to my phone's Download folder.
2. On my phone, I
2a. Had Magisk "patch (the) selected file";
2b. Transferred the new patched boot image, magisk_patched_FKPSk.img, back to the computer; and
2c. Put the phone into fastboot mode.
3. Back on my computer, in adb, performed the "fastboot flash boot magisk_patched_FKPSk.img."
adb successfully flashed to boot_a, then I rebooted the phone. It rebooted surprisingly quickly.
Going into "System / Advanced / System Update," it still says
Android security update: January 5, 2021
So, what am I doing wrong? Should I force adb to flash to boot_b instead?
Thanks for any ideas!
Click to expand...
Click to collapse
That doesn't have anything to do with Magisk. That's the firmware update you are on. If you want on a newer one you will to flash it. Then follow your previous steps. Magisk doesn't update your firmware for you.
Tulsadiver said:
That doesn't have anything to do with Magisk. That's the firmware update you are on. If you want on a newer one you will to flash it. Then follow your previous steps. Magisk doesn't update your firmware for you.
Click to expand...
Click to collapse
Ah. So then, if I understand correctly, the process is to unroot, sideload the OTA image (not just flash the factory image's boot.img file) via adb, and then perform the above steps to re-root?
NickEspo said:
Ah. So then, if I understand correctly, the process is to unroot, sideload the OTA image (not just flash the factory image's boot.img file) via adb, and then perform the above steps to re-root?
Click to expand...
Click to collapse
Yes, though I normally fastboot the factory images rather than sideload an ota. That update process will lose root, then you patch the boot.img and fastboot it to regain root. I would recommend removing all modules prior to updating as they will survive the update process (unless you wipe) and if not compatible with your update, will bootloop you once you root again.