Related
Hi guys,
I'm running my Moto G 16GB on Kitkat 4.4.2 system version 175.44.1.falcon_umts.Retail.en.DE. Today it offered to download and install the latest OTA update (called 176.44.1.en.DE). I started the download and tried to install it.
After downloading the update was placed in /cache. The file name was 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE.zip', which surprised me. I was expecting something like 'Blur_Version.176.44.1.falcon_umts.Retail.en.DE.zip'.
When I tried to install it without removing root and without going back to stock recovery it ended with a signature error in CWM. Installing the untrusted zip manually didn't work as well - as expected.
Then I tried to follow advise from other threads and went back to stock recovery (extracted from a full install package 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE' - 444MB) That seemed to work and the install of the OTA update went fine before getting stuck on the boot animation on the first boot. It sat there for 10 minutes before I rebooted and restored a CWM backup.
I'm running out of ideas. Some say it's sufficient to go back to stock recovery temporarily. Others say you need to go back to full stock.
I have to repeat that I'm rooted and that I've de-activated a few unused apps (mainly harmless google stuff (hangout, search, music and so on) and Motorola Assist, Migrate and 'Context Services') .
Are there further findings about what stops the OTA from succeeding?
Many thanks in advance,
Kleo2
Kleo2 said:
Hi guys,
I'm running my Moto G 16GB on Kitkat 4.4.2 system version 175.44.1.falcon_umts.Retail.en.DE. Today it offered to download and install the latest OTA update (called 176.44.1.en.DE). I started the download and tried to install it.
After downloading the update was placed in /cache. The file name was 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE.zip', which surprised me. I was expecting something like 'Blur_Version.176.44.1.falcon_umts.Retail.en.DE.zip'.
When I tried to install it without removing root and without going back to stock recovery it ended with a signature error in CWM. Installing the untrusted zip manually didn't work as well - as expected.
Then I tried to follow advise from other threads and went back to stock recovery (extracted from a full install package 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE' - 444MB) That seemed to work and the install of the OTA update went fine before getting stuck on the boot animation on the first boot. It sat there for 10 minutes before I rebooted and restored a CWM backup.
I'm running out of ideas. Some say it's sufficient to go back to stock recovery temporarily. Others say you need to go back to full stock.
I have to repeat that I'm rooted and that I've de-activated a few unused apps (mainly harmless google stuff (hangout, search, music and so on) and Motorola Assist, Migrate and 'Context Services') .
Are there further findings about what stops the OTA from succeeding?
Many thanks in advance,
Kleo2
Click to expand...
Click to collapse
If your phone is rooted or there is a CWM installed or there is any change in system files then ota will fail till you flash stock rom. You can't just bring back stock recovery. You have to "delete" root as well.
There is some info http://forum.xda-developers.com/showpost.php?p=47495650&postcount=6
I will post my case here, I had the same problem, I had CWM and root and when I rebooted to update I get installation failed and boot loop.
Then I just flashed stock recovery (only) rebooted and now I already have the update installed
CromoPT said:
I will post my case here, I had the same problem, I had CWM and root and when I rebooted to update I get installation failed and boot loop.
Then I just flashed stock recovery (only) rebooted and now I already have the update installed
Click to expand...
Click to collapse
Hi, thanks for your replies. Because of your report and others, who state the same (installing stock recovery only to get the update working) I was hoping to get around going back to full stock. It always takes a lot of time to configure the phone the way it was configured before essentially wiping.
Just to repeat what I did: when I try to install the OTA while CWM is installed there's just an error message in CWM, the update fails, but the phone is working normally afterwards. It's just not updated.
When I try with stock recovery the update process finishes without errors, but the phone get stuck during the boot animation.
Maybe there's a way to fix the boot loop?
Looking forward to any suggestions
Cheers, Kleo2
I tried again and found a way without going back to full stock.
1. flashed stock recovery from full 175.44.1 image
2. let the phone download the OTA and restart to install it
3. ota install in stock recovery went fine
4. reboot -> stuck on boot animation again
5. flashed CWM and wiped cache AND dalvik cache
6. next boot took longer than normal but got past the boot animation
7. android optimized/cached my apps and then started normally
8. version is now 176.44.1 and the phone seems to work normally (after 30 minutes of usage)
Hope that helps someone and that I won't have issues going forward because I did it this way.
Cheers, Kleo2
Kleo2 said:
I tried again and found a way without going back to full stock.
Click to expand...
Click to collapse
Thanks. :good: Did 1 to 3 and phone booted just fine (not stuck on boot animation)
My phone: No logo fix, root, Xposed Framework
After update root was still there, Xposed needed a new install
total noob
i would so much like to update my rooted moto g.. because of my card reader.
does anyone know a step-by-step-for-complete-noobs-post and could provide a link?
i'm just starting.. and so happy and proud that i got my phone rooted.. and that i got rid of this rebooting problem by erasing the cache.
but i'm already lost when i read "flashed stock recovery".. yeah i know: that much noob!
help would be much appreciated!
Papshmir
Papshmir said:
i would so much like to update my rooted moto g.. because of my card reader.
does anyone know a step-by-step-for-complete-noobs-post and could provide a link?
i'm just starting.. and so happy and proud that i got my phone rooted.. and that i got rid of this rebooting problem by erasing the cache.
but i'm already lost when i read "flashed stock recovery".. yeah i know: that much noob!
help would be much appreciated!
Papshmir
Click to expand...
Click to collapse
I UPDATED my rooted Kitkat Tesco version SUCCESFULLY! and still rooted.
What I did:
1. install Motorola Device Manager (RESTART computer and telephone)
2. downloaded MotoTool
3. Made a Nandroid backup in CMW, made a backup with MotoTool too. Just in case
And deactived (did not uninstall) my Xposed framework modules (if you dont have it, you dont need to)
I have some system apps disabled, but didnt re-activate it. (was too lazy haha)
4. downloaded the correct ROM from: http://sbf.droid-developers.org/phone.php?device=14 (Tesco UK 4.4.2)
5. unzipped the ROM and rename and overwrite the recovery.img to the exact name as in the MotoTool All In One 2.6\Data\KitKat\StockKitKatrecovery.img (Just for sure it's the same as my ROM, I dont know if all the ROMs have the same recovery sooo )
6. started MotoTool, unplug&replug device. Checked KitKat option in the program, did a connection check, it was okay. Did a NORMAL restart via progam. You have to grant permisson on your phone.
7. after reboot, rebooted the phone to FASTBOOT.
8. Checked Stock Fastboot in the program, it flashed succesfully. Then I went into recovery (1×down volume, then 1× up volume) checked if the recovery was working. It was working (android logo+ no command error message)
9. reboot (long press power button)
10. Updeted OTA, settings/inf./update.. blabla okay okay next next. Wait until it downloads (only 7.9 MB )
11. wait for the update to be done, then it reboots, then apps are being updated. Everything looks fine and working
+1 flash CMW or other recovery again.
Hope this helps! I was afraid to do it too. I'm not used to MotoTool and other Motorola stuff because I had a HTC Desire, it was much simplier with that. But no risk here either! Good luck!
So I am trying to put back my stock recovery so I can take the OTA, but after I flash the recovery and try to reboot to it, it says "No Command". I have reflashed TWRP and then the stock recovery again with the same result. The phone itself will boot fine, but I can't install the OTA as it gets an error part of the way into the install. Any ideas? I have the 1034.
EDIT: Well I remembered I did the H+ mod, so after reverting that the OTA flashed I had Faux Kernel before hand, but after reflashing it my wi-fi wont enable, any ideas?
Thanks!
Kleo2 said:
I tried again and found a way without going back to full stock.
1. flashed stock recovery from full 175.44.1 image
2. let the phone download the OTA and restart to install it
3. ota install in stock recovery went fine
4. reboot -> stuck on boot animation again
5. flashed CWM and wiped cache AND dalvik cache
6. next boot took longer than normal but got past the boot animation
7. android optimized/cached my apps and then started normally
8. version is now 176.44.1 and the phone seems to work normally (after 30 minutes of usage)
Hope that helps someone and that I won't have issues going forward because I did it this way.
Cheers, Kleo2
Click to expand...
Click to collapse
Thanks,
Wiping cache and dalvik cache did the trick for me. You saved my day
Please please help
I have the same problem. I've tried to update the new OTA and failed. After restoring full stock rom, the system simply doesn't boot!
I had Faux Kernel and GravityBox but I didn't revert anything. I thought that a full stock rom would clear all system settings.
This is my version of stock (Blur_Version.174.44.9.falcon_umts.Retail.en.GB) and I tried to flash it several times now. No success. I get stuck on the boot logo.
I tried to downgrade to 4.3 using version Blur_Version.14.71.8.falcon_umts.Retail.en.GB. I was able to boot and see the initial setup but I have no WIFI! I was trying to install 4.3 then try to update via OTA but OTA only works with WIFI so I'm stuck.
I also tried installing the 24th Feb nightly build of Cyanogen and the device also booted but with no WIFI.
I really don't know what to do! Please help me. I've tried other stock images out of despair but none with sucess.
Does anyone have a clue to what might be to problem and how to revert it?
Thank you
draco259 said:
So I am trying to put back my stock recovery so I can take the OTA, but after I flash the recovery and try to reboot to it, it says "No Command". I have reflashed TWRP and then the stock recovery again with the same result. The phone itself will boot fine, but I can't install the OTA as it gets an error part of the way into the install. Any ideas? I have the 1034.
EDIT: Well I remembered I did the H+ mod, so after reverting that the OTA flashed I had Faux Kernel before hand, but after reflashing it my wi-fi wont enable, any ideas?
Click to expand...
Click to collapse
Before flashing stock ROM try to clear/format all your partitions with a custom recovery!
Sent from my XT1032 using xda app-developers app
I installed the OTA update using the CWM recovery but not root, I changed the update-script to not give error during installation
Hui91 said:
I UPDATED my rooted Kitkat Tesco version SUCCESFULLY! and still rooted.
What I did:
1. install Motorola Device Manager (RESTART computer and telephone)
2. downloaded MotoTool
3. Made a Nandroid backup in CMW, made a backup with MotoTool too. Just in case
And deactived (did not uninstall) my Xposed framework modules (if you dont have it, you dont need to)
I have some system apps disabled, but didnt re-activate it. (was too lazy haha)
4. downloaded the correct ROM from: http://sbf.droid-developers.org/phone.php?device=14 (Tesco UK 4.4.2)
5. unzipped the ROM and rename and overwrite the recovery.img to the exact name as in the MotoTool All In One 2.6\Data\KitKat\StockKitKatrecovery.img (Just for sure it's the same as my ROM, I dont know if all the ROMs have the same recovery sooo )
6. started MotoTool, unplug&replug device. Checked KitKat option in the program, did a connection check, it was okay. Did a NORMAL restart via progam. You have to grant permisson on your phone.
7. after reboot, rebooted the phone to FASTBOOT.
8. Checked Stock Fastboot in the program, it flashed succesfully. Then I went into recovery (1×down volume, then 1× up volume) checked if the recovery was working. It was working (android logo+ no command error message)
9. reboot (long press power button)
10. Updeted OTA, settings/inf./update.. blabla okay okay next next. Wait until it downloads (only 7.9 MB )
11. wait for the update to be done, then it reboots, then apps are being updated. Everything looks fine and working
+1 flash CMW or other recovery again.
Hope this helps! I was afraid to do it too. I'm not used to MotoTool and other Motorola stuff because I had a HTC Desire, it was much simplier with that. But no risk here either! Good luck!
Click to expand...
Click to collapse
At part 8, I am getting an image of the android guy with his stomach open with a big red '!'. That's 'no command' right?
Any ideas? I have no idea what I am doing
Guys, a really easy way to update is:
1. Install Philz recovery - http://forum.xda-developers.com/showthread.php?t=2639583
2. Reboot and then download the OTA update when prompted - select Install when prompted
3. It will now reboot into Philz recovery, install the update and reboot
4. You'll see Android is Upgrading...
5. Re-boot back into recover and re-install faux kernel
I have just upgraded my XT1032 on 174.44.9 en GB (rooted + faux008) to 176.44.1 using this... worked like a dream! All I had to do was re-install faux kernel as that was overwritten by the OTA, but Root was in-tact...
i have root, twrp recovery and faux kernel, the problem is only faux kernel? Or I must remove all? (root recovery etc)
Hey people.
I have i simingly small problem but a very real one with my Z3 D6603
What i have done:
1. Unlocked bootloader with unlock code from sony dev site and adb in fastboot mode. Succsessfuly, checked service meny. All Ok so far.
2. I realized that i should haved backed up my drm keys when i upon next boot noticed i lost a couple sony stock features i like.
3. I followed this thred to the letter with a little reasonable thinking.
I used "D6603_23.0.1.A.5.77_IT.ftf" for TA partition restore. and "D6603_23.1.A.0.690_CentralEurope.ftf" for LP Stock.
4. I Used "Z3_ADV_stock_LP_v2" as kernel flashed in adb as fastboot. Everything else is flashed in Sony flash tool in flash mode on Z3.
5. Finally flashed "DRM Function Restoration for Xperia Lolipop V2.zip" in twrp.
6. Rebooted - Back to twrp flashed Chainfire Root zip 2.46 - rebooted.
All fine till this Point.
All working twrp 2.8.5.0 plus root.
Time for Xposed. Recovery - flashed "arm 15-03-08" rebooted. Install apk xposed alpha 2.
Download module "Xperia/AOSP NavBar Buttons" - check it for activation - reboots and NOW the problem beggins!!!
It get completely stuck at "SONY text in the beginning. I force shut it down by Power + Volume Up.
I dont remember exactly but the last can have been done Before i did a complete reflash for restoring sony orig features. (step 3)
7. Fresh install with root, sony orig features and twrp.
8. Install Xposed no problem. Installing "gravetyBox LP 5.0.6 Alpha.
9. Rebooting and starting to load bootanimation 5-6 seconds later it gives an ugly best described as hardware fail sound Sharp but dim tone and starts to bootlooping.
10. At this poing i can only get up and running by booting in to twrp - whipe - advanced wipe - chache and dalwik chache - reboot system it "optimizing 306 apps of about 15 minutes each time. Then its alive with everything working again. Root, Xposed, modules system and so on.
I have tried Another kernel "Z3_AndroPlusKernel_v51.zip" flashed via adb and fastboot. This resulted in a brick phone, not a Life sign at all.
adb and fastbooted z3. Flashed this kernel resulting in working phone with twrp 2.8.6.0 after Another step 10 procedure again.
Please, Please help! It would be fun to be able to shut down or rebooting my Z3 without this huge hang-bootloop problem. I finally got Everything working exept for above issue.
Im basicly stuck right now and just avoiding turning it off.
Come on all great xda people, help a fella in need!
OK, so I've got the original shield tablet. I have lost root, and whenever I try to boot to recovery, the system attempts, goes to a black screen, then proceeds to normal system boot. Environment:
stock 6.0
non-rooted (not since updating to 6.0)
shield version 4.0
build MRA58K.41524_664.1902
previously had TWRP
I understand loss of root/recovery w/that last update is normal. However, I've tried:
flashing the new TWRP via fastboot w/o success (3.0.2)
flashing the rooted boot img w/o success
even flashing the stock recovery w/o success
ADB & fastboot commands chug happily along, & I'm left with the same behavior. Flashing the stock recovery actually gave me the dead android at the recovery screen (was this b/c I flashed the one for 4.0.1 & I need the one for 4.0?). So, what's my next move here?
Aaaaaaannnnnd.... I've also completely lost my WiFi. Says that it's on, but it's got the slash through it in quick settings & doesn't find any networks.
t-readyroc said:
OK, so I've got the original shield tablet. I have lost root, and whenever I try to boot to recovery, the system attempts, goes to a black screen, then proceeds to normal system boot. Environment:
stock 6.0
non-rooted (not since updating to 6.0)
shield version 4.0
build MRA58K.41524_664.1902
previously had TWRP
I understand loss of root/recovery w/that last update is normal. However, I've tried:
flashing the new TWRP via fastboot w/o success (3.0.2)
flashing the rooted boot img w/o success
even flashing the stock recovery w/o success
ADB & fastboot commands chug happily along, & I'm left with the same behavior. Flashing the stock recovery actually gave me the dead android at the recovery screen (was this b/c I flashed the one for 4.0.1 & I need the one for 4.0?). So, what's my next move here?
Click to expand...
Click to collapse
1) the twrp you linked to is for lollipop, states that in the notes section half way down the page.
2) to get root with this method you also have to install phh superuser
3) that dead Android IS the stock recovery
Now for help: flash this recovery(there are two here read and find the one for MM)
https://r.tapatalk.com/shareLink?ur...share_tid=2877117&share_fid=3793&share_type=t
[RECOVERY] [unofficial] TWRP 3.0.2-0 (2.8.7.1 for Lollipop) [2016-04-05]
Sent from my SHIELD Tablet K1 using Tapatalk
Thanks Exile. I've got TWRP installed ok now, but it doesn't seem to be able to wipe anything - just kinda hangs there (trying to wipe dalvik & cache - just sits at "formatting cache using make_ext4fs"). It's also weirdly unresponsive with UI lag on button presses; not sure if that's a known thing. I'm assuming that the "E: Failed to mount decrypted adopted storage device" is in reference to my external SD card.
I also still don't have my WiFi. I've grabbed the WiFi full OTA from this post & adb pushed it. TWRP was able to successfully flash it, but then couldn't do the ensuing dalvik/cache wipe. I let it sit for a good 10mins just to see if it would finish, but it still sat at the same point. Force power-cycling booted it into the new 4.1/6.0.1 version, and I do have my WiFi back
So, how to get root back? Can I just flash the SU 2.65 I have from TWRP? Or do I have to flash the rooted boot img again? I do already have the Superuser app installed...
t-readyroc said:
Thanks Exile. I've got TWRP installed ok now, but it doesn't seem to be able to wipe anything - just kinda hangs there (trying to wipe dalvik & cache - just sits at "formatting cache using make_ext4fs"). It's also weirdly unresponsive with UI lag on button presses; not sure if that's a known thing. I'm assuming that the "E: Failed to mount decrypted adopted storage device" is in reference to my external SD card.
I also still don't have my WiFi. I've grabbed the WiFi full OTA from this post & adb pushed it. TWRP was able to successfully flash it, but then couldn't do the ensuing dalvik/cache wipe. I let it sit for a good 10mins just to see if it would finish, but it still sat at the same point. Force power-cycling booted it into the new 4.1/6.0.1 version, and I do have my WiFi back
So, how to get root back? Can I just flash the SU 2.65 I have from TWRP? Or do I have to flash the rooted boot img again? I do already have the Superuser app installed...
Click to expand...
Click to collapse
Ok, from here just flash the supersu.zip and you should be good. I can't remember if 2.65 works or not but I know you can find a copy of 2.71. someone else has a problem with 2.72 so it may or may not work.
As for twrp it has touch screen lag issues, I don't think any of the mm compatible versions have been able to fully fix this. I've had the same problem with dalvik cache and cache wipe, it is slow as molasses but will complete eventually. Once you have root I would suggest using a program called flashfire to flash zips and do things like cache wipe. It works like a charm.
https://r.tapatalk.com/shareLink?ur...share_tid=3075433&share_fid=3793&share_type=t
[Android 4.2+][ROOT][2016.05.11] FlashFire v0.33 - Play BETA
Sent from my SHIELD Tablet K1 using Tapatalk
Thanks again, Exile. I actually had to re-flash TWRP, oddly, but after some searching, I found a mirror for su2.71, & adb pushed it. Once I had TWRP back in order, I was able to then flash it & my root is back together.
Glad you got it working. Have fun and be safe
Sent from my SHIELD Tablet K1 using Tapatalk
Google Play Store Pixel, stock feb update (nof26v), unrooted, unlocked bootloader. There's a longer back story to this issue I've encountered, but to cut to the chase:
I can successfully flash TWRP 3.0.2 RC1 and 2.79 SR3. I can boot into system and enjoy benefits of root. However, I've noticed that whenever I try to reboot SYSTEM, it only boots into recovery. Even when I boot into bootloader and flash stock boot.img, it'll just reboot into stock recovery, but never into system. My way out of this quasi soft-brick state is to flash stock boot.img and sideload ota and I'm good to go with all my settings/data intact, I'll just be unrooted (as expected). I can verify it survives reboot in this state.
Has anyone else encountered this before? Is there something in the latest SU that won't let it reboot properly? Is there a way I can force it to reboot a certain slot to somehow avoid this issue?
The way Android handles memory now, I don't ever feel the need to reboot. But one of the things that's essential for me is to edit build.prop to enable wifi tether and miracast. Thing is, it requires a reboot for those changes to apply, but as soon as I reboot...
I've had this all working before on the dec update and SuperSU-v2.79-201612051815.zip but then something really strange happened (long backstory referenced above) and it required me to have to re-root, only now it won't survive reboot.
Any insight is greatly appreciated!
I have never encountered this issue as a result of flashing Super SU. I have come across this when I updated to the latest image by just flashing a few components.. IE: i didnt flash the whole factory image.
Flashing the latest factory image to both slots and starting over fixed the issue for me.
Flash the image (flash_all.bat) then fastboot boot twrp and switch slots, flash factory image again.
Just my two cents.
k.s.deviate said:
Flashing the latest factory image to both slots and starting over fixed the issue for me.
Flash the image (flash_all.bat) then fastboot boot twrp and switch slots, flash factory image again.
Just my two cents.
Click to expand...
Click to collapse
Thanks for your input! Should I remove -w while flashing, or when you said starting over do you mean full wipe?
Was hoping to avoid going that route... Is there any way to salvage without wipe?
Let me also share the strange event I encountered which led me to this point:
As stated, I had December update with stable 2.79 and TWRP 3.0.2. I skipped Jan update and was planning to do the same for the Feb update, but for whatever reason, I went to check updates (knowing full well it wouldn't take since I'm not on stock recovery). It gave me the standard "downloading, installing..Oops, there's a problem" prompt and I went on my merry way.
A week or so later, I decided to manually reboot and upon boot, I noticed it said "Android is starting/configuring" something along those lines. Then I tried double tap to lock (Nova gesture) and it says phone wasn't rooted. I check and sure enough, no SU icon. Checked Android version and now it says I'm on Feb update.
Attempt to install latest from chainfire on play store and no dice. Decide to flash it instead. Downloaded 2.79 SR3. Booted temporary TWRP and flashed the install and SU and then I found that phone won't boot to anything but recovery. Now anytime, I modify the boot image in any way, I'm bricked on subsequent reboots until I flash stock boot image and sideload OTA.
How do you think the Feb update installed when it shouldn't have? Did it install to one slot while my other slot was TWRP+root?
I would guess that it may have installed onto the inactive slot, but it doesn't sound like it should have if you had TWRP and Su installed. However we are all still learning new things about the pixel every day.
I would recommend clean flashing the factory image to both slots and starting over. Sounds like something became corrupt.
What version of ADB and Fastboot are you running? This reboot to bootloader happened to me when I unknowing using an older version.
Try wiping the device completely push your factory image via ADB and fastboot and installed of TWRP RC1 use alpha 2 never had a issue with alpha 2 after flashing TWRP boot into stock then go back into TWRP then flash SuperSU
jamespark said:
How do you think the Feb update installed when it shouldn't have?
Click to expand...
Click to collapse
People have reported automatic OTA updates on rooted Pixel phones. You can shut off automatic OTA updates by following the following link. People report still getting a notification for updates after the setting change, but updates no longer happen automatically. The site below also lists a way to entirely shut off OTA notifications, yet that change causes my phone to stay awake constantly and never go into deep sleep, so I only recommend the link. There's a thread or two about FlashFire, which I may eventually get around to trying.
https://www.androidexplained.com/pixel-disable-ota-updates/
Are you okay with losing data? I can post the links I used to download SuperSU and a little guide to flash to stock and reroot. Maybe you'll be able to figure what you're doing wrong or just doing what I do step by step might fix it.
mngdew said:
What version of ADB and Fastboot are you running? This reboot to bootloader happened to me when I unknowing using an older version.
Click to expand...
Click to collapse
Definitely using an older version of adb and fastboot. I'll update and retry with the latest, thanks for the suggestion!
alluringreality said:
People have reported automatic OTA updates on rooted Pixel phones. You can shut off automatic OTA updates by following the following link. People report still getting a notification for updates after the setting change, but updates no longer happen automatically. The site below also lists a way to entirely shut off OTA notifications, yet that change causes my phone to stay awake constantly and never go into deep sleep, so I only recommend the link. There's a thread or two about FlashFire, which I may eventually get around to trying.
https://www.androidexplained.com/pixel-disable-ota-updates/
Click to expand...
Click to collapse
Thanks for the heads up! I had this setting enabled and I have since disabled it.
I really appreciate the community and all your help!
SOLVED
I'm pleased to report that I now have root that survives reboot!
- From stock: flashed TWRP and SU. verified root, edited build.prop and reboot system..... boots into recovery (the usual problem)
- switched active slots and flashed SU, reboot
- SU icon in app drawer but when launched: "supersu binaries not installed"
- reboot into recovery and flashed su, reboot
- su is installed, but build.prop changes didn't stick. edited build.prop, reboot system
- boots into recovery.
- flashed su, did NOT reboot, backed out, switched slots, flash SU to the other slot, reboot
- huzzah!
is it verified that android will alternate active slots upon each subsequent reboot (i.e. A/B/A/B/...)?
it would seem I was making changes and rebooting to the other slot which was jacked up, so I had to finally apply the same changes to both slots and now everything is working!
I honestly don't know what I just did, and I guess sometimes it's better to be lucky than smart lol but, boy, this two-system partition is a piece of work...
Thanks again to everyone for all your help!!
Wondering if many others of you have run across this, what causes it, and how to avoid it. Basically, I download the factory image from google's image page, flash-all using adb/fastboot. All looks good, every part of installation says OKAY, no fails. Then upon reboot it goes back to bootloader, but now with a yellow banner at the bottom - ERROR: LoadImageAndAuth Failed: Load Error. Sometimes the banner reads ERROR: Slot Unbootable: Load Error. (see attached pictures)
There's no way out of it, flashing images, bootloader or boot.img or whatever separately, flashing twrp, switching between a/b partitions, nothing changes it. Adb/fastboot is current. It's happened after regular flash-all, it's happened when "-w" is removed. It's happened with and without twrp installed. This last time I tried to avoid it by updating without flashing the image, removed twrp and tried to sideload the OTA in stock recovery, which also landed me in the same spot, in the bootloader with that yellow banner of death. Been hit by this using Dec., Feb., and March updates. I stayed on the Dec. update for a while because I've been afraid of it happening again... sure enough it did.
I've replaced a few pixel 2's because of this, every time Google willingly stands by their product and replaces it. One google worker told me this is a known issue they were working on, others said it isn't, and none have provided an explanation for why it happens or how to avoid it. I assume it's some kind of instability with the a/b partition system. I did the same process with my N5x a couple days ago (flashed image then added twrp, magisk, all that stuff) and as usual everything went swimmingly. Tried just flashing current image on p2 the next day and another one bit the dust. Another replacement is on its way now.
So I turn to you. Any of you run into this? What causes it? How can I flash updates without this happening again?
As you know, this happened to me partially. One of my bootloader slots is messed up. Just remember that you can always plug into USB and skip the bootloader and just boot using the boot.img directly.
fastboot boot boot.img
OR if you use Magisk...
fastboot boot patched_boot.img
This of course gets you booted up, so you can get your data backed up or whatever. You're basically tethered to a computer if you ever have to reboot or get back up after a power off.
I think I'll wait another month before having Google replace mine.
deepdvd said:
As you know, this happened to me partially. One of my bootloader slots is messed up. Just remember that you can always plug into USB and skip the bootloader and just boot using the boot.img directly.
fastboot boot boot.img
OR if you use Magisk...
fastboot boot patched_boot.img
This of course gets you booted up, so you can get your data backed up or whatever. You're basically tethered to a computer if you ever have to reboot or get back up after a power off.
I think I'll wait another month before having Google replace mine.
Click to expand...
Click to collapse
Tried boot.img but not working for me, still stuck in bootloader. But good to know, I didn't realize that was a possibility. Sucks having to be tethered like that though. I backed up double before messing with it, both nandroid and titanium, expecting I might run into this again.
The replacement process is relatively painless, only takes like 3 days to get a new one. Just be sure to do it while covered under warranty.
Hope it works out. To have this happen to several replacements is either extremely bad luck, or some unknown external factor.
clcdev said:
Hope it works out. To have this happen to several replacements is either extremely bad luck, or some unknown external factor.
Click to expand...
Click to collapse
Thanks man, seems like it since not many people are experiencing this. Can't think of what external issue it could be other than something with my computer, but im sure not having any troubles doing the same stuff and more on my nexus.
@trhacker01, have you tried flashing the latest full OTA image through recovery twice first (so that both partitions are updated) and then using the factory image? I had a similar (not same) issue where is displayed an empty yellow warning bar and did not let me update the bootloader, but after doing this, I no longer have this issue.
craigacgomez said:
@trhacker01, have you tried flashing the latest full OTA image through recovery twice first (so that both partitions are updated) and then using the factory image? I had a similar (not same) issue where is displayed an empty yellow warning bar and did not let me update the bootloader, but after doing this, I no longer have this issue.
Click to expand...
Click to collapse
Well I tried flashing the ota in recovery and that's what triggered it this last time. But I didn't try doing each partition, maybe that's where it went wrong
Every update bricks me when I try flashing an OTA.
Pretty sure I had both of those errors. One for Feb, other for March.
Fastboot full factory image -w and back to normal, then reinstall twrp.
Going forward I will just plan on using the full factory image.
COMpulse said:
Every update bricks me when I try flashing an OTA.
Pretty sure I had both of those errors. One for Feb, other for March.
Fastboot full factory image -w and back to normal, then reinstall twrp.
Going forward I will just plan on using the full factory image.
Click to expand...
Click to collapse
That's what gets me, can't simply fastboot the image to recover, that fail-safe isn't reliable for me.
Got the replacement and set it up so I can update normally. Just booted twrp but didn't install, so I could flash magisk. With no twrp and easily uninstall magisk I can just update via regular OTA when it shows up. Then temporarily boot twrp again to reinstall magisk. Just did that for the March update and worked fine.
A little inconvenient of a workaround but I'm updating without concern about this image flashing problem.
I have the exact same problem as first post, even same picture yellow banners. I have tried everything too.
I removed using automatically remove Magisk rooted through Magisk Manager. I liked the edge plus modules.
I was going to Android P with alt flash bat/All and (-W) edit to keep the perfectly working Jan updates.
First of above troubles.
I then went back and tried all updates of 2018.
Same steps as above, re updated everything, different USB port, cable a no go.
The load boot from Fastboot is a no go. Deuce's scripts no go. Manual install of all files (instead of) bat file commands no go.
I bought device through Project Fi, so first go around for return is now escalated and awaiting further return of device.
Looking at web searches used what I could find for return to normal complete image install, NO GO.
Maybe I have the early reports of Flashing Factory Image files =return device= that a few users had back in Nov 2017.
kkjb said:
I have the exact same problem as first post, even same picture yellow banners. I have tried everything too.
I removed using automatically remove Magisk rooted through Magisk Manager. I liked the edge plus modules.
I was going to Android P with alt flash bat/All and (-W) edit to keep the perfectly working Jan updates.
First of above troubles.
I then went back and tried all updates of 2018.
Same steps as above, re updated everything, different USB port, cable a no go.
The load boot from Fastboot is a no go. Deuce's scripts no go. Manual install of all files (instead of) bat file commands no go.
I bought device through Project Fi, so first go around for return is now escalated and awaiting further return of device.
Looking at web searches used what I could find for return to normal complete image install, NO GO.
Maybe I have the early reports of Flashing Factory Image files =return device= that a few users had back in Nov 2017.
Click to expand...
Click to collapse
Added: found I my bootloader was failing on updating. Fastboot message= (bootloader) Updating partition=0 Failed
(remote:Command Flash Error).
Some how thought to look over deuce flash all scrip instructions and followed exactly, which seemed strange to add script to expanded image file. Well even with lot's of error returns from running. Used same image that was installed Jan 1.17xx019.013 fixed bootloader and worked.
Odd that was not the usual process, but it WORKED.
kkjb said:
Added: found I my bootloader was failing on updating. Fastboot message= (bootloader) Updating partition=0 Failed
(remote:Command Flash Error).
Some how thought to look over deuce flash all scrip instructions and followed exactly, which seemed strange to add script to expanded image file. Well even with lot's of error returns from running. Used same image that was installed Jan 1.17xx019.013 fixed bootloader and worked.
Odd that was not the usual process, but it WORKED.
Click to expand...
Click to collapse
Wow great to hear it worked! I tried the deuce script but couldn't get it to work either. I heard there was an issue with the bootloader in December and was supposed to have been fixed in January. But that bootloader error was one that I was also getting after the yellow banner started showing up, even on this last go around. Just before the initial bricking fastboot was reporting all successful on the flash.
More of my troubles
I have twrp 3.2.1-2, Magisk v16.1(1610) Jan 18 8.1.0. The device is working as before. So to recap...first post is what I HAD. My bootloader is stuck on 002.0059.00 this is the one from opd1.170816.025 which is 8.0.0 Nov 17. This some how flashed through Deuce's script and stuck. Now of course nothing will flash with Factory images because I have a botched up Boot.img. From looking back the trouble started with going to update to P. Removed Magisk through manager. It "patched" boot but some how on mine (with flashed twrp) recovery caused a flag I guess to set.
So some point I'm going to get Magisk to patch current Factory Boot.img 002.0067.00 which is in Feb, Mar 18 and P.
Need time to read though Magisk or wait for others to experience. I believe this is the warning message of TWRP and Pixel 2 A/B slots.
update to my troubles
If you have watching as myself to correct the troubles I'm having: recap: Bootloader is not flashing to current one
I'm stuck on 0059. I get a flash fail message (bootloader) ( remote:Command Flash Error ) Bootloader A 200002000 SZ=0000B000. Stuck on bootloader screen only.
Corrected back to before still broken flashable bootloader 0059. Used install TWRP and Magisk. Which I had before trying to update from Jan 18 update. So works as before..
I tried a path to some how get back to correct. So flash current tdbo and boot.img and bootloader. WRONG white G screen only.
So fastboot back into twrp.img use install script zip, install Magisk nogo.
So caution DON'T do it my way.
I was lucky I had a back up twrp file from a month ago. Now at least back to "working"
opm1.171010.013. again that is bootloader 0066 but mine is 0059....
kkjb said:
If you have watching as myself to correct the troubles I'm having: recap: Bootloader is not flashing to current one
I'm stuck on 0059. I get a flash fail message (bootloader) ( remote:Command Flash Error ) Bootloader A 200002000 SZ=0000B000. Stuck on bootloader screen only.
Corrected back to before still broken flashable bootloader 0059. Used install TWRP and Magisk. Which I had before trying to update from Jan 18 update. So works as before..
I tried a path to some how get back to correct. So flash current tdbo and boot.img and bootloader. WRONG white G screen only.
So fastboot back into twrp.img use install script zip, install Magisk nogo.
So caution DON'T do it my way.
I was lucky I had a back up twrp file from a month ago. Now at least back to "working"
opm1.171010.013. again that is bootloader 0066 but mine is 0059....
Click to expand...
Click to collapse
That's pretty slick that you got it working again, especially with the bootloader error. I didn't think you could get the current OS working with an old bootloader at all. Hopefully at some point you will be able to update it all the way.
I soft bricked it..so don't do this.
See previous to catch up. Since I pulled the plug and had a Google Warranty phone in hand...21 hours later!
I decided to do all the things NOT TO DO.
Pulled factory Image file from last bootloader with 0059 bootloader.. Nov 17
Flashed tdbo.img, boot.img.
Didn't change same Flash failure device return message. Had to boot TWRP, flash twrp to get working again. Since phone needs to return for credit.
Nothing to lose, I have been on slot = A always. Moved to slot = B....
Now it is a brick.
First couple of power cycles, one line flash, vibrate. Then after 3-4 more cycles no more vibration. longer time to one line flash.
Warm to touch, overnight charge. Same.
So message is to keep backup of files used in first portion of Magisk and twrp installs. Must follow instructions if want to remove Magisk root.
Somehow my problem is a weird one off with the bootloader oddity.