Related
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
Do you have a custom recovery or flashed a kernel? You must be 100% stock
Sent from my Nexus 5 using XDA Free mobile app
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
eatcyanide said:
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
Click to expand...
Click to collapse
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
rahul9five said:
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
Click to expand...
Click to collapse
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
wantabe said:
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
Click to expand...
Click to collapse
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
rahul9five said:
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
Click to expand...
Click to collapse
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
wantabe said:
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
Click to expand...
Click to collapse
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
rahul9five said:
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
Click to expand...
Click to collapse
Flashing the factory image or a system image will always unroot your device. Lock the bootloader using the sdk. The command is fastboot oem lock.
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Yea, you can't flash the ota through a custom recovery anymore
Sent from my Nexus 9 using XDA Free mobile app
beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
rahul9five said:
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
Click to expand...
Click to collapse
Err... I didn't suggest that you flash a custom ROM. Read what I said.
Hey everyone, I've been lurking around for about two months, from when I picked up this phone. It's still completely stock. Unrooted, S-ON, all that. Well, after the update to Nougat, I've been searching for a way to unlock the bootloader & root. Is it safe for me to use WinDroid Toolkit for the process? Just need a guide for the process, for the most part. I appreciate any help that anyone is willing to offer.
acesavant00 said:
Is it safe for me to use WinDroid Toolkit for the process? Just need a guide for the process, for the most part. I appreciate any help that anyone is willing to offer.
Click to expand...
Click to collapse
Go to http://htcdev.com and make an account, then follow the steps and unlock your bootloader from there. After that you fastboot flash TWRP using ADB, and then use TWRP to flash a root solution. I prefer Magisk.
Alright, just unlocked the bootloader, going through the process of setting up my phone once again. Do you have a link to the Magisk & TWRP programs that I can use? Also, should I put the TWRP file in the same folder as the fastboot files?
I greatly appreciate the assistance you've given me so far, I'm deeply grateful man.
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
acesavant00 said:
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
Click to expand...
Click to collapse
try this step by step.. :good:
1.Flash TWRP 3.0.3-8 via Fastboot.. Do not reboot into system, enter into recovery..
2.Do a factory Reset via TWRP.. Do not reboot into system
3.Now flash SuperSU 2.79 SR3.. Reboot into system..
couple of bootloops are common, do not give up for at least 3 bootloops..
It will take a long time to boot as you have done a factory reset..
So be patient and wait for at least half hour..
acesavant00 said:
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
Click to expand...
Click to collapse
Sorry about this - I updated the TWRP thread with the current/preferred root method: MagiskSU.
You need to flash a stock boot.img and then flash the Magisk zip from the linked thread.
Captain_Throwback said:
Sorry about this - I updated the TWRP thread with the current/preferred root method: MagiskSU.
You need to flash a stock boot.img and then flash the Magisk zip from the linked thread.
Click to expand...
Click to collapse
Aw crap, I wish I would have seen this yesterday. I tried to format data & flash one of the stock rooted roms for marshmallow roms for my sprint one a9... now it just hangs at the HTC One logo. I'm gonna assume that I'm screwed until a stock rooted Nougat rom is released for sprint.
acesavant00 said:
Aw crap, I wish I would have seen this yesterday. I tried to format data & flash one of the stock rooted roms for marshmallow roms for my sprint one a9... now it just hangs at the HTC One logo. I'm gonna assume that I'm screwed until a stock rooted Nougat rom is released for sprint.
Click to expand...
Click to collapse
Can't you just flash the Nougat RUU?
Captain_Throwback said:
Can't you just flash the Nougat RUU?
Click to expand...
Click to collapse
I found the post about the Nougat RUU, but the program won't recognize my phone cause it won't boot. I'm gonna try & flash the firmware through TWRP.
acesavant00 said:
I found the post about the Nougat RUU, but the program won't recognize my phone cause it won't boot. I'm gonna try & flash the firmware through TWRP.
Click to expand...
Click to collapse
You don't flash firmware with TWRP. But you can use the SD card method to flash the RUU, which doesn't require a computer.
Captain_Throwback said:
You don't flash firmware with TWRP. But you can use the SD card method to flash the RUU, which doesn't require a computer.
Click to expand...
Click to collapse
Sorry to bother you again, but you wouldn't happen to know a method of extracting the rom.zip from the exe file, would you?
acesavant00 said:
Sorry to bother you again, but you wouldn't happen to know a method of extracting the rom.zip from the exe file, would you?
Click to expand...
Click to collapse
[TOOL][LINUX|WIN|MAC][64bit][29-SEP-2016]Universal HTC RUU/ROM Decryption Tool 3.1.0
Run the tool with the -z flag to output a zip to the "OUT" folder.
Captain_Throwback said:
[TOOL][LINUX|WIN|MAC][64bit][29-SEP-2016]Universal HTC RUU/ROM Decryption Tool 3.1.0
Run the tool with the -z flag to output a zip to the "OUT" folder.
Click to expand...
Click to collapse
Thank you so much, man. The zip is prepped, just gotta charge my phone again to 30%. But afterwards, will I have to go through the unlock bootloader process? If I do, I don't wanna mess up on the rooting process.
acesavant00 said:
Thank you so much, man. The zip is prepped, just gotta charge my phone again to 30%. But afterwards, will I have to go through the unlock bootloader process? If I do, I don't wanna mess up on the rooting process.
Click to expand...
Click to collapse
Your bootloader will stay unlocked.
Captain_Throwback said:
Your bootloader will stay unlocked.
Click to expand...
Click to collapse
Awesome, I appreciate all of the help, man. Sorry again if I annoyed you with all of my incessant questions. Just didn't wanna mess up my phone even further.
Hello Guys,
I Have an HTC one a9 with 7.0, s-off, bootloader locked
I have some concerns before I root my phone
If I unlock the bootloader and root the phone, Will I have the option of phone encryption as it used to be ?
If I unlock the bootloader with HTCDev and flash the TWRP with SuperSu and boot file, it is a MUST to do a data factory reset? or I`m able to do all the process without loosing my data?
Thank you in advance
rilley said:
Hello Guys,
I Have an HTC one a9 with 7.0, s-off, bootloader locked
I have some concerns before I root my phone
If I unlock the bootloader and root the phone, Will I have the option of phone encryption as it used to be ?
If I unlock the bootloader with HTCDev and flash the TWRP with SuperSu and boot file, it is a MUST to do a data factory reset? or I`m able to do all the process without loosing my data?
Thank you in advance
Click to expand...
Click to collapse
Unlocking your bootloader will wipe the device.
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
sandreas said:
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
Click to expand...
Click to collapse
+1 I`m interested on this question, I have Nougat installed
sandreas said:
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
Click to expand...
Click to collapse
rilley said:
+1 I`m interested on this question, I have Nougat installed
Click to expand...
Click to collapse
Yes, you can root and debloat Nougat. Though you should make a stock system image backup first of you ever want to receive an OTA again. The TWRP thread FAQ has a lot of information about this.
Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!
Dito13 said:
Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048/page63
Alright, thanks! :good: That only leaves the first question unanswered.
Dito13 said:
Alright, thanks! :good: That only leaves the first question unanswered.
Click to expand...
Click to collapse
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually
Thank you kindly!
OMJ said:
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually
Click to expand...
Click to collapse
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...
Dito13 said:
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...
Click to expand...
Click to collapse
twrp will install the ota zip but it wont install the firmware.zip inside, you have to extract & manually install from download mode
grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?
Dito13 said:
grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?
Click to expand...
Click to collapse
list your steps your using to install the ota via twrp....personally, I let the system initiate the install (booted into OS) as if I was 100% stock, once twrp loads, it automatically installs except for the firmware.zip
more details here...
OK, I am a Noob to the HTC world. I am used to easy flashing/rooting/etc. on Nexus devices.
TWRP doesn't do anything after accepting the ota. When I try to install the OTA via TWRP I receive Error 7. I worked my way through a lot of guides here on XDA concerning manual OTA installing. One thing I tried was flashing back to stock recovery which I found in the firmware.zip of the OTA in bootloader mode. That failed also ("FAILED (remote: not allowed on PRODUCTION device).
Edit: The device has obviously an unlocked bootloader, s-on, rooted via magisk and is a DGLU device, software number 1.16.400.5
Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.
schmeggy929 said:
Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.
Click to expand...
Click to collapse
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.
Dito13 said:
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.
Click to expand...
Click to collapse
re-flash twrp and try it again.
schmeggy929 said:
re-flash twrp and try it again.
Click to expand...
Click to collapse
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.
Dito13 said:
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.
Click to expand...
Click to collapse
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.
schmeggy929 said:
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.
Click to expand...
Click to collapse
Thanks again - seems to have worked. It will be interesting to see which problems occur with the Android Oreo update which was announced till the end of the year by HTC
I've always wanted to post one of these
https://developers.google.com/android/images
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
I was looking thru that post and didnt wanna risk wiping the device. I just had to wipe a few days ago due to Edxposed bootloop issue lol
Ha, yeah, I feel your pain there, wiping is way too much of a pain to do that frequently
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
You can also flash the OTA file in stock recovery and not lose data.
spotmark said:
You can also flash the OTA file in stock recovery and not lose data.
Click to expand...
Click to collapse
Will it retain root or do you mean - https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Androider4Life said:
Retain root or have to re-root
Click to expand...
Click to collapse
Have to re-root using the Magisk method. Put stock boot on phone, patch boot with Magisk, put modded boot back on computer, and flash in fastboot. AFAIK, there is no way to retain root. Every time you flash the latest monthly patch, it flashes a new stock boot. Therefore, no root.
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
There's a way with taking the ota through settings I found out how from a user on here which is:
Once received the ota , go to magisk first uninstall/restore images then download/install ota then DONT REBOOT, go back to magisk install magisk to inactive slot from the app then reboot and all should work with new ota update and have root still.
What is this update 4.3mb
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
gettinwicked said:
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
Click to expand...
Click to collapse
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
gm007 said:
What is this update 4.3mb
Click to expand...
Click to collapse
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Jiggs82 said:
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Click to expand...
Click to collapse
You missed the part where I did try flashing the image. I've done this a hundred times, so, I did it right.
Anyway, I got it. I didn't realize my work computer had a USB-C port, so, I grabbed one and tried flashing the image with that. Worked! Thank God... I guess sdk tools doesn't like a USB 1 to C cable, and my phone doesn't like going into recovery...
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Homeboy76 said:
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Click to expand...
Click to collapse
I am starting to feel more and more like a lot of the bootloop issues are being caused by OTAs swapping slots on install. Besides the --slot all patched boot, it might help to run the OTA twice to get it to install to both slots completely. Preferably though, quit using OTAs and work with -w removed flash-all installer (and even then possibly installing to both slots with an active slot swap in between and before rooting). The double install is common when installing custom ROMs, and the process for OTA sideloads is pretty similar.
Performance improvement, feels smooth and responsive. Glad i dont need to root this phone, ppl are having so many problems.
boe323 said:
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Click to expand...
Click to collapse
My download was 1.3 gb and took forever to install. That's more than just the security patch.. Build number is different too.
Sent from my Pixel 3 XL using Tapatalk
Worked exactly the same as the 10 and .C3 builds for me. Flash-all (minus -w) and patched boot in Magisk. No issues. It was not just security this month. See the functional patches in the bulletin.
https://source.android.com/security/bulletin/pixel/2019-10-01
is there new platform tools too?
83.7MB
Installation without any troubles. No major changes. d2tw still not working.
Nothing to say
My device gives an error when i try to install.
Says: Failed to install update, tap here for more information.
When i tap, there is no 'more information' !
Stupid Android!
Install and nothing change, still have problem on sim1, when turn on data on sim1 i lost network.
perfect_ said:
My device gives an error when i try to install.
Says: Failed to install update, tap here for more information.
When i tap, there is no 'more information' !
Stupid Android!
Click to expand...
Click to collapse
Same Problem With My Device.
Anyways, Solution Is Here...
1st We Need To Unlock Bootloader Then Flash Currently Available Stock Rom Through MI Flash Tool.
Thanks,
MUHAMMAD Asif Qasim
perfect_ said:
My device gives an error when i try to install.
Click to expand...
Click to collapse
If the OTA fails, you can find out which partitions it doesn't like from the logcat. If you have a fastboot image, you can reflash the affected partitions. I have had to restore both system.img and vendor.img since 10.0.10.0 (the fact that I've been using a custom bootanim definitely does not help).
Code:
adb logcat | grep update_engine
a1291762 said:
If the OTA fails, you can find out which partitions it doesn't like from the logcat. If you have a fastboot image, you can reflash the affected partitions. I have had to restore both system.img and vendor.img since 10.0.10.0 (the fact that I've been using a custom bootanim definitely does not help).
Code:
adb logcat | grep update_engine
Click to expand...
Click to collapse
Hello Dear,
Can You Guide Stepwise How To Fix Partition ? I Do Not Want To Unlock The Bootloader Or Flashing The Stock ROM. I Just Want To Fix Issue That Causing The Update.
In Addition to That My Device Is Updated aon Last October.
Your Help Will Be Highly Appreciated In This Regards.
Thank You In Advance
aasiaasi said:
Can You Guide Stepwise How To Fix Partition ? I Do Not Want To Unlock The Bootloader Or Flashing The Stock ROM. I Just Want To Fix Issue That Causing The Update.
Click to expand...
Click to collapse
I'm used to flashing from fastboot but I'm pretty sure that only works with an unlocked bootloader. I've read that you can use miflash with a locked bootloader but you need a complete rom and the most recent one is 10.0.13.0
Sorry
a1291762 said:
I'm used to flashing from fastboot but I'm pretty sure that only works with an unlocked bootloader. I've read that you can use miflash with a locked bootloader but you need a complete rom and the most recent one is 10.0.13.0
Sorry
Click to expand...
Click to collapse
Thank You For Time And Reply.
OKay What Should We Do To Fix The (Partition) Problem. ? Complete Stepwise Guide Will Be Beneficial To Us.
One More Question.
Is There A Way To Get Every Month OTA Installed Without Interrupting (Unlock Bootloader , Rooted With Magisk) ? If Yes , So What Could Be The Steps/Guide.
Thanks.
aasiaasi said:
Is There A Way To Get Every Month OTA Installed Without Interrupting (Unlock Bootloader , Rooted With Magisk) ? If Yes , So What Could Be The Steps/Guide.
Click to expand...
Click to collapse
If you just have Magisk, this is all you should need to do.
https://forum.xda-developers.com/mi...ll-magisk-proper-support-ota-t3836952/page100
If you have other stuff that breaks that process (eg. Magisk + TWRP) then you need extra steps.
https://forum.xda-developers.com/mi...to-10-0-7-0-ota-keeping-magisk-t3916863/page9
---------- Post added at 12:23 AM ---------- Previous post was at 12:13 AM ----------
aasiaasi said:
OKay What Should We Do To Fix The (Partition) Problem. ? Complete Stepwise Guide Will Be Beneficial To Us.
Click to expand...
Click to collapse
Previously you said you did not have an unlocked bootloader, but you asked for OTA instructions with Magisk...
Since you don't have backups of the modified partitions, you should backup your data then install 10.0.13.0 from fastboot image. This is the only option if your bootloader is locked (I think that miflash allows this?)
If you are modifying your device I'd suggest backing up the partitions that were rejected by the upgrade (logcat). See the advanced guide I posted for details.
If you have backups you just need to restore the partitions the upgrade is complaining about (logcat).