I have my Pixel (obtained from Google) rooted. I have not installed any Kernels or Roms.
I received a notification that there is an Android system update. Is is OK to install this update?
Based on your comments, I assume you are not on Verizon - if that is the case, whether you do an update or not is completely up to you - I have the GOOGLE PIXEL - am using ATT service and I am also rooted - I updated - ultimately I had to re-root - install Twrp and flash the rom I wanted to use - but beyond that - no reason not to - completely up to you. Good luck.
So, if I install the update, I will lose TWRP and root?
You never want to take an OTA update if you have a custom recovery. Can and will brick your phone. As long as you have stock recovery your more than welcome to take an OTA update.
Restored factory boot.img to boot_a and boot_b
When I try to install the update, it says "Installation Problem"
Hey folks,
I just got the notification for a system update. TW Model, currently in Germany. However, I tried capturing the ota link for patching the boot.img, but it gives me an error. Anyone with more luck than me?
Greetings
Update:
I managed to get the OTA.zip off my phone, but the update itself fails at 24%. Restored stock boot.img before of course. Has someone already installed it?
Hong Kong variant still on 1.24.400.03, December 2017 security update [emoji23][emoji23][emoji23]
Sent from my HTC U11 plus using Tapatalk
September 2018 security on latest 1.24.709.93... Can't remember before that... And I couldn't spot any difference between the two, does anybody see anything new?
Inviato dal mio HTC_2Q4D100 utilizzando Tapatalk
I've got it too on my TW model in the Netherlands.
Besides the security patch going from June 1 to September 1 I don't see anything different yet. Then again, there weren't any bugs I'm aware of, that needed fixing. 700MB+ seems like a lot for 3 months of security patches though.
It's nice to get an update and be less behind in security patch date again.
Thanks, HTC!
U11+ from Europe...
Didn't get the june security patch, didn't get this one either...
Tw version in Malaysia. Already updated. Everything okay. Doesn't explore much because going to work. only feel different at the display color. Looked better
UK version, no update available so far and still on 1 December 2017 security patch. I'd settle for them fixing the notification issue.
Sent from my HTC U11 plus using Tapatalk
Some findings
Battery before i go to work, 75%, on airplane mode.
Come back home after 11 hours, 75%
Soooo happy.....
Hmm.... maybe I need to learn how to roll back to stock now
Received today in Belgium with TW version of the phone!
gortys said:
Received today in Belgium with TW version of the phone!
Click to expand...
Click to collapse
Very important question:
Where/in which precise folder is the OTA update saved in HTC U11+ after downloading (I cannot find it...)
Thx a lot!
marusia7 said:
Very important question:
Where/in which precise folder is the OTA update saved in HTC U11+ after downloading (I cannot find it...)
Thx a lot!
Click to expand...
Click to collapse
Ow, sorry, I don't know at all!
gortys said:
Ow, sorry, I don't know at all!
Click to expand...
Click to collapse
found it in root folder:
data/data/com.htc.updater/files/
lillypad_33 said:
Hmm.... maybe I need to learn how to roll back to stock now
Click to expand...
Click to collapse
did you manage to update?
same situation here: although I flashed back to original boot.img (included in the last OTA update end of July 2018 which was later patched by Magisk), the update stucks at 24% with red error. Luckily the phone boots normally without applied update.
Anybody any idea how to proceed? I already tried to flash back the original boot.img from the stock RUU and also to use the boot.img provided in the latest OTA: with both boot.img (although both have very same size) the phone stucks at HTC logo but does not continue to boot.
Currently the HTC U11+ boots only from the boot.img provided with 709.8 OTA, (also booting with the patched_boot.img done by Magisk derived from the same).
I am a bit stuck here: Magisk should not touch the system (so no idea why the OTA stops at 24%) and only 1 out of 3 boot images are working (although all with same size), so currently I am not able to apply the OTA update...
I have read that for OTA updates the integrity (?) of the recovery.img is important ( (although Magisk should also not touch the recovery.img (?)
Any ideas?
best regards, Marusia
Looks like htc forgot people are still buying their phones outside Taiwan, or they don't have enough money to hire a translator!! I am an old loyal customer for 8 years, but here they are doing everything to let us get another brand, it's like they stabbed themselves and slowly turning the knife to feel more pain
marusia7 said:
did you manage to update?
same situation here: although I flashed back to original boot.img (included in the last OTA update end of July 2018 which was later patched by Magisk), the update stucks at 24% with red error. Luckily the phone boots normally without applied update.
Anybody any idea how to proceed? I already tried to flash back the original boot.img from the stock RUU and also to use the boot.img provided in the latest OTA: with both boot.img (although both have very same size) the phone stucks at HTC logo but does not continue to boot.
Currently the HTC U11+ boots only from the boot.img provided with 709.8 OTA, (also booting with the patched_boot.img done by Magisk derived from the same).
I am a bit stuck here: Magisk should not touch the system (so no idea why the OTA stops at 24%) and only 1 out of 3 boot images are working (although all with same size), so currently I am not able to apply the OTA update...
I have read that for OTA updates the integrity (?) of the recovery.img is important ( (although Magisk should also not touch the recovery.img (?)
Any ideas?
best regards, Marusia
Click to expand...
Click to collapse
I also flashed the recovery.img from the latest OTA, but still the red triangle.
Is it possible to flash the whole OTA via fastboot? Maybe thats a possibility.
metaxuss said:
I also flashed the recovery.img from the latest OTA, but still the red triangle.
Is it possible to flash the whole OTA via fastboot? Maybe thats a possibility.
Click to expand...
Click to collapse
I also flashed latest OTA recovery,same result...
I guess the only way is to flash back to stock RUU (which will lead to unrooted phone), install latest OTA via WLAN, then unlock bootloader (via HTCdev website) and root again with Magisk. I never did RUU flashing, so currently backing up everything with Titanium, if I proceed I will let you know the result...
Flashing the latest OTA might brick the phone (the red triangle already indicates that something went seriously wrong, although I have no clue what it could be: never touched the system, Magisk only patches the boot.img), instructions should be in the forum.
Tried another thing: disabling the systemless Xposed (installed via Magisk), reboot, restoring boot.img via Magisk, OTA download & trying to install --> red triangle...
I cannot remember if I disabled Xposed before the last OTA update few months ago. I had there some issues too (after successful OTA install the phone stuck at boot so I had to reflash the OTA-boot.img again via fastboot), maybe this procedure broke the possibility to install current OTA.
Will maybe try to flash selectively restored stock RUU images (without applying first the whole stock RUU) on the weekend (I have been informed by PM that this procedure should be harmless), so reverting to whole stock RUU is still not the last option.
I downloaded OTA from the following link and flash "system.img" with fastboot command. I am now on 1.24.709.93
https://drive.google.com/drive/folders/1wccnIY0NaoelhZQS4uhgP8ZGIn1iXhNX
Link Credit to : nene bear
kenosis said:
I downloaded OTA from the following link and flash "system.img" with fastboot command. I am now on 1.24.709.93
https://drive.google.com/drive/folders/1wccnIY0NaoelhZQS4uhgP8ZGIn1iXhNX
Link Credit to : nene bear
Click to expand...
Click to collapse
These OTA files dont contain system.img (the system.img file should be >4Gb).
1) Did you experience also OTA update issue (red triangle) as described in this thread?
2) Just to clarify: you flashed 1st the system.img derived from the stock RUU and afterwards applied the 709.93 OTA update?
Hi,
I can’t seem to find a post about an S10e. My apologies if one already exists.
I have a g970F with unlocked bootloader, stock rom and magisk installed. Can I now update as I am having trouble installing unsigned apks over the top of original apks.
Thanks.
Hello, once the original firmware is altered, you cannot install OTA updates, only through Odin.
themohd said:
Hello, once the original firmware is altered, you cannot install OTA updates, only through Odin.
Click to expand...
Click to collapse
Many thanks for the advice. I will attempt to locate an updated ASBA version as I’m currently using a security patch from February.
Hello guys!
Something wrong happened with my blujay, I need ur help...
So here's the complete story:
1) since december I didn't have OTA update, I don't know why, and the system was telling me it was outdated everyday but up to date in the update menu. so I decided to download the latest OTA bluejay-ota-tq1a.230205.002-1ec64b58.zip and apply it.
2) that worked nice, it booted up updated to this version. But proposed me another security update to get me to march 2023 security update.
3) Allright, security update done, but without root. So I donwloaded the full image corresponding to the OTA i made, bluejay-tq1a.230205.002-factory-1b04ccc9.zip, extracted the boot.img, patched it with magisk 26.1, then flashed it through fastboot.
4) this is where things get naughty, I had bootloop. I imagine this boot.img was correponding to my OTA update, but then another update was done, and the boot.img was wrong for this one.
5) I tried to reflash the patched and original boot.img, same. I tried to reapply the OTA, same, still bootloop.
6) I just tried to patch the full image, removing the -w from the flash-all.bat to not wipe my data (the whole point is that I can't loose all that), and still the same, I have a screen from android recovery saying it cannot load the system and proposing me to wipe, which I don't want.
What should I do ? Save me please!!
You updated from the Feb 2023 patch to the March 2023 patch in step 2. You then downloaded and patched the Feb 2023 boot.img file and applied it, with the system being at the March 2023 update. This is where the issue is. You need to download the March 2023 image and flash the boot.img from this. It is possible though, that you are at the April 2023 patch if you did this very recently.
Hi folks, I am running a Pixel 6A that I rooted with magisk back in December. I stupidly did not disable OTA updates. Last night the QPR2 update came down and wiped root from my phone.
Bootloader is still unlocked and magisk app is installed.
I am confused about the best way to restore root. I see that the QPR2 beta required the use of the pixel 7 boot image. Does that still hold for the stable QPR2?
Also, the magisk app offers a way to choose and patch an image within the app. Can I get the pixel 7 boot image and patch it in magisk, or do I have to use the ADB/ fastboot method?
Sorry for the trouble. I promise I will disable OTA updates in the future. Thanks for any help.
Hello! I am also root user and if it is true that there was an update with the boot 6a not root and I had to use the pixel 7 or 7 pro (I do not remember which was) but if in doubt I would try only with the 6a just in case, the procedure is to download the full rom of the same version you have now, extract the boot.img, patch it with magisk and flash it by adb from the pc, is the method I use in each update and no problems until today, good luck and greetings!
If you are using Magisk Stable 26.1 or Canary 26101, you can use the Pixel 6a boot image to root as the problems mentioned above have been fixed with these versions of Magisk.
Problem solved. Y'all rock.
I'm having a similar problem. I'm am unable to find the boot.img anywhere in the zip file I'm on Bluejay TQ2A 230305.008E1.
RimWulf said:
I'm having a similar problem. I'm am unable to find the boot.img anywhere in the zip file I'm on Bluejay TQ2A 230305.008E1.
Click to expand...
Click to collapse
Download and open the zip => open "image-bluejay-tq2a.230305.008.e1.zip" => find your boot.img