Hey all, long time lurker and first(ish) time poster. I have a Nexus 7 (2013) that is great, except for a problem I've been having upgrading from 4.4 to 4.4.2. I am unlocked and rooted, and have the latest version of TWRP installed for the device (flo).
The problem originally started with the OTA. When the OTA would come down and I would click it, it would boot into TWRP and then just restart without installing anything. I attempted this five or six times before trying something else. From there, I downloaded and attempted to install manual update zips for the Nexus to take it from 4.4 to 4.4.2. When I would try and install these, it would say "error executing updater binary in ...". I have tried downloading the updating zip from multiple websites, and I've checked the MD5's, which always match up.
I'm sorry if this is a stupid question, but where can I go from here? I've exhausted my knowledge of what other possibilities are out there, or what could be causing the update to fail.
Thanks!
If the stock finds that any system files have been altered and the md5 check is different from what it should be, a OTA stock update will not go through.
In my personal opinion, flashing a stock root / unrooted image found in the development section of these forums is one of the easier ways of applying an update.
For example if you want a rooted one here's one: http://forum.xda-developers.com/showthread.php?t=2563017
photonate said:
Hey all, long time lurker and first(ish) time poster. I have a Nexus 7 (2013) that is great, except for a problem I've been having upgrading from 4.4 to 4.4.2. I am unlocked and rooted, and have the latest version of TWRP installed for the device (flo).
The problem originally started with the OTA. When the OTA would come down and I would click it, it would boot into TWRP and then just restart without installing anything. I attempted this five or six times before trying something else. From there, I downloaded and attempted to install manual update zips for the Nexus to take it from 4.4 to 4.4.2. When I would try and install these, it would say "error executing updater binary in ...". I have tried downloading the updating zip from multiple websites, and I've checked the MD5's, which always match up.
I'm sorry if this is a stupid question, but where can I go from here? I've exhausted my knowledge of what other possibilities are out there, or what could be causing the update to fail.
Thanks!
Click to expand...
Click to collapse
TheAltruistic is right, that is probably the easiest way to get updated. Another option would be to download the 4.4 factory image and pull the system.img from there and flash that with fastboot then the OTA would work. But really if you go through that you might as well flash the 4.4.2 factory image. I'm not a huge fan of doing the OTA and would rather flash factory images while skipping the userdata image which wipes the device.
wantabe said:
TheAltruistic is right, that is probably the easiest way to get updated. Another option would be to download the 4.4 factory image and pull the system.img from there and flash that with fastboot then the OTA would work. But really if you go through that you might as well flash the 4.4.2 factory image. I'm not a huge fan of doing the OTA and would rather flash factory images while skipping the userdata image which wipes the device.
Click to expand...
Click to collapse
/agreed
from the factory image:
Open flash-all.sh (linux) or flash-all.bat (windows) in a proper text editor (for windows users edit++ is a proper editor- linux people can use their editor of choice):
Find this line:
Code:
fastboot -w update image-razor-kot49h.zip
change it to
Code:
fastboot update image-razor-kot49h.zip
and it will leave your user data intact
oldsoldier2003 said:
/agreed
from the factory image:
Open flash-all.sh (linux) or flash-all.bat (windows) in a proper text editor (for windows users edit++ is a proper editor- linux people can use their editor of choice):
Find this line:
Code:
fastboot -w update image-razor-kot49h.zip
change it to
Code:
fastboot update image-razor-kot49h.zip
and it will leave your user data intact
Click to expand...
Click to collapse
You're right, thanks for pointing that out! I've done that before but I'm so used to flashing the images separately I forgot about it for a minute!
Related
Hi All,
My Nexus 7 LTE is rooted with TWRP.
I've downloaded the OTA for 4.4.3 from one of the posts in the forums. It updates my razorg from KOT49H to KTU84L.
After using adb sideload, the update zip file is transferred successfully to my device, but it fails with the error message
Code:
"/system/bin/surfaceflinger" has unexpected contents.
error excuting updater binary in zip '/data/media/0/sideload.zip
Does anyone have any idea what could be causing the update to fail?
I've already restored to a stock kernel (from franco kernel) as well as uninstalled xposed framework.
Thanks!
Install stock recovery and take ota as normal. Then reinstall twrp and reroot.
If you fail update I have a backup I made with twrp you can use. Just need to extract it to your twrp backup folder and restore. It's 100% stock and was made after wiping data. Can't post a link to my Dropbox right now because of my post count but if you need it I an send it to you by other means.
Thanks for that. I think I might have to flash stock recovery and give it a shot, although I have a feeling even if I do that, it might not work as my tablet is no longer stock, since I've installed apps which made changes, such as FKU as well as CF-Lumen.
endlesstrail said:
Thanks for that. I think I might have to flash stock recovery and give it a shot, although I have a feeling even if I do that, it might not work as my tablet is no longer stock, since I've installed apps which made changes, such as FKU as well as CF-Lumen.
Click to expand...
Click to collapse
To get the OTA to work with either a stock or custom recovery the unexpected contents error will have to be fixed first. Somehow the surfaceflinger file was changed, that's a new one for me so I have no idea what could have changed it. I could upload a copy of mine if you want to try it but I do have the wifi version and don't know if they are the same. Otherwise you will need to fastboot flash the system image for the version you are running now for the update to work. Instead of doing that I would download the 4.4.3 factory image and extract the radio, system, and boot images and fastboot flash those. The bootloader did not change so that does not need to be flashed. Before flashing the images I would download the newest supersu zip and put it in your device storage, then flash the images, once that is done do not reboot, boot into recovery instead and flash the supersu zip then wipe cache and dalvik then reboot. Should take less than 15 minutes. ; )
You could also flash the factory image but that will install the stock recovery, lose root and completely wipe your device. If you are using windows you can open the flash-all.bat with a text editor like notepad and remove the -w from the text, that will prevent the userdata image from being flashed which wipes your device.
Thanks for your reply, wantabe.
I guessed as much, that if I couldn't figure out what changed the surfaceflinger, I might as well do a complete flash back to stock, which was what I did. Now it's just a matter of flashing back TWRP, restoring all the apps and waiting for 4.4.4 :good:
I've downloaded the ota zip and ready to flash it in twrp. But when I flash it, it shows an error saying my device have wrong build number. I'm very sure that i have kitkat ktu84p but when flashing the ota it says i have the previous jelly bean build which makes my flash unsuccessful. I've also checked build.prop and its also listed there its ktu84p. Whats the problem here and if possible show a solution please
ImjuzCY said:
I've downloaded the ota zip and ready to flash it in twrp. But when I flash it, it shows an error saying my device have wrong build number. I'm very sure that i have kitkat ktu84p but when flashing the ota it says i have the previous jelly bean build which makes my flash unsuccessful. I've also checked build.prop and its also listed there its ktu84p. Whats the problem here and if possible show a solution please
Click to expand...
Click to collapse
See it this thread helps
http://forum.xda-developers.com/nex...-qa/flashing-lollipop-ota-twrp-fails-t2939358
jj14 said:
See it this thread helps
http://forum.xda-developers.com/nex...-qa/flashing-lollipop-ota-twrp-fails-t2939358
Click to expand...
Click to collapse
Thanks for the link. Now i can conclude that the ota doesnt work with custom recoveries. Tried twrp and cwm. Twrp shows jelly bean fingerprints but cwm shows another kitkat fingerprint rather than ktu84p thats suppose to be
ImjuzCY said:
Thanks for the link. Now i can conclude that the ota doesnt work with custom recoveries. Tried twrp and cwm. Twrp shows jelly bean fingerprints but cwm shows another kitkat fingerprint rather than ktu84p thats suppose to be
Click to expand...
Click to collapse
Wonder if you are using an outdated TWRP version. Maybe the newer versions have fixed this
jj14 said:
Wonder if you are using an outdated TWRP version. Maybe the newer versions have fixed this
Click to expand...
Click to collapse
I dont think so cause ive just updated it to 2.8.1.0 which is the newest by now
I tried everything and still get wrong build fingerprint when trying to flash the 5.0
ImjuzCY said:
I dont think so cause ive just updated it to 2.8.1.0 which is the newest by now
Click to expand...
Click to collapse
Hello!
Really want to flash the OTA without a total wipe.
First flashed it from TWRP 2.8.1.0 and got the wrong build finger print says I have Flo:4.3/JSS15Q/779366 and it expects KTU84P/1227136
Then using WugFresh 1.9.4 flashed stock recovery so I could sideload then encountered the whole adb disappearing in recovery - eventually solved that and finally managed to adb sideload saw my screen saying it was installing the update using the stock recovery - YAY! It was short lived as the stock recovery screen told me the exact same thing that TWRP had told me.
I looked at my build.prop and it says my ro.build.fingerprint=google/razor/flo:4.4.4/KTU84P/1227136. user/release-keys
Can someone enlighten me? I've wasted so much time on this I would love some keen insight - PLEASE!!
Thanks for any and all help!
Edbogue
Google changed the way OTAs work in 5.0. You will usually not be able to flash a OTA if your OS is modified. Means no custom recovery or root. You will have to flash your tab back to stock kitkat.
Before it would patch individual file blocks, now it patches the whole system partition as a blob. Read more http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
Workaround that helped me upgrade
Following the steps below seems to have done the trick for me. My issue was that Android 5.0 updates the system partition all in one go now, rather than each file separately. Following those steps will unroot your device but will allow you to install the OTA updates.
So follow these steps to refresh your current Android version (e.g 4.4.4) then use OTA or adb sideload to update to, for example, 5.0.
This will not wipe user data or the cache.
Download the Factory Image for your current version of android from google (4.4.4 most likely)
Extract each level of compressed files until you get to a .zip file (inside will be boot.img, recovery.img, and system.img)
Move these files to your ADB directory (optional step, makes the commands shorter)
make sure your device is connected with working drivers and is in bootloader mode ( adb reboot bootloader )
perform the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
Finally, (Re)start the system
After this if you want to root and reinstall a custom recovery , follow the normal steps.
I would post my source, but as I only just joined to say what helped me, I'm not allowed to post links I'll just say Google "flashing-a-stock-android-image-without-wiping-user-data" and (as of 19/11/2014) it's the top result.
Please continue here: http://forum.xda-developers.com/nexus-4/help/android-5-0-0-to-5-0-1-update-t2972371#post57515317
Finally finally!!! A fix!
Raingram said:
Download the Factory Image for your current version of android from google (4.4.4 most likely)
Extract each level of compressed files until you get to a .zip file (inside will be boot.img, recovery.img, and system.img)
Move these files to your ADB directory (optional step, makes the commands shorter)
make sure your device is connected with working drivers and is in bootloader mode ( adb reboot bootloader )
perform the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
Finally, (Re)start the system
After this if you want to root and reinstall a custom recovery , follow the normal steps.
.
Click to expand...
Click to collapse
Thank you Raingram! This worked perfectly!
I'm trying to apply the 5.0.1 LRX22C OTA update file on my Nexus 7 (2013 WiFi), which is currently running 5.0.0 Build LRX21P. I've tried installing the zip through TWRP recovery and by sideloading using the Nexus Root Toolkit from my computer...no luck either way.
Here's the issue I'm running into:
During the OTA zip install process, I get an error saying that the user build on my device is LRX21V, and the update aborts because the package expects build LRX21P. (My device settings say that I'm on LRX21P.) I upgraded to 5.0.0 in the first place by manually installing the OTA zip from build KTU84P. I'm not sure if that has anything to do with the issue, since I did not wait for the OTA to become available when it rolled out to me in the System Update feature (maybe sideloading OTAs triggers my device to load test/interim builds?).
Here's what I get in the TWRP log:
Installing '/sdcard/bc4516eb14461efdfaf309311b1f09328b654012.signed-razor-LRX22C-from-LRX21P.bc4516eb.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
script aborted: Package expects build fingerprint of google/razor/flo:5.0/LRX21P/1570855:user/release-keys or google/razor/flo:5.0.1/LRX22C/1602158:user/release-keys; this device has Android/omni_flo/flo:5.0/LRX21V/dees_troy11241447:eng/test-keys.
Package expects build fingerprint of google/razor/flo:5.0/LRX21P/1570855:user/release-keys or google/razor/flo:5.0.1/LRX22C/1602158:user/release-keys; this device has Android/omni_flo/flo:5.0/LRX21V/dees_troy11241447:eng/test-keys.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/bc4516eb14461efdfaf309311b1f09328b654012.signed-razor-LRX22C-from-LRX21P.bc4516eb.zip'
Error flashing zip '/sdcard/bc4516eb14461efdfaf309311b1f09328b654012.signed-razor-LRX22C-from-LRX21P.bc4516eb.zip'
Click to expand...
Click to collapse
Anyone know how I can get the update to work? I don't want to wipe my device to flash a factory image...it's not that urgent. But if there's a way I can upgrade without waiting for the OTA to rollout to me, that'd be nice.
Thanks for any help!
indiecognition said:
I'm trying to apply the 5.0.1 LRX22C OTA update file on my Nexus 7 (2013 WiFi), which is currently running 5.0.0 Build LRX21P. I've tried installing the zip through TWRP recovery and by sideloading using the Nexus Root Toolkit from my computer...no luck either way.
Here's the issue I'm running into:
During the OTA zip install process, I get an error saying that the user build on my device is LRX21V, and the update aborts because the package expects build LRX21P. (My device settings say that I'm on LRX21P.) I upgraded to 5.0.0 in the first place by manually installing the OTA zip from build KTU84P. I'm not sure if that has anything to do with the issue, since I did not wait for the OTA to become available when it rolled out to me in the System Update feature (maybe sideloading OTAs triggers my device to load test/interim builds?).
Here's what I get in the TWRP log:
Anyone know how I can get the update to work? I don't want to wipe my device to flash a factory image...it's not that urgent. But if there's a way I can upgrade without waiting for the OTA to rollout to me, that'd be nice.
Thanks for any help!
Click to expand...
Click to collapse
Same issue for me, with this strange fingerprint.
I tried to flash it by side load and TWRP 2.8.2.2 with th esame result!:crying:
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom from Scrosler found here http://forum.xda-developers.com/nexu...rx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed (no wipes) the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything. Seriously easy, guys!
FWIW the Factory Images are a super easy way as well.
I went from 4.4.4 to 5.0 with Factory Images and the -w flag in the batch file removed (to prevent wiping data), then rooted with Chainfire Auto Root (CFAR). Whole process took about 10 minutes (less download time).
I then went from 5.0 to 5.0.1 in the same fashion. I tried to sideload the OTA but it failed verification (/recovery and /system (root, I'm guessing)) so rather than mess with flashing both then doing the OTA, I just downloaded the 5.0.1 factory Factory Image, removed the -w flag again, and took the same steps as above. Ran the batch, ran CFAR and I was done.
Edit: for clarifiaction, I did these like two weeks apart, not back to back. I also did an upgrade for a friend on his N7 and went from 4.4.4 to 5.0.1 with Factory Images exactly as above. Although I didn't remove the -w flag for him because his bootloader was locked, so it was already wiping for that. Flashed Factory Images, ran CFAR, done.
indiecognition said:
I'm trying to apply the 5.0.1 LRX22C OTA update file on my Nexus 7 (2013 WiFi), which is currently running 5.0.0 Build LRX21P. I've tried installing the zip through TWRP recovery and by sideloading using the Nexus Root Toolkit from my computer...no luck either way.
Here's the issue I'm running into:
During the OTA zip install process, I get an error saying that the user build on my device is LRX21V, and the update aborts because the package expects build LRX21P. (My device settings say that I'm on LRX21P.) I upgraded to 5.0.0 in the first place by manually installing the OTA zip from build KTU84P. I'm not sure if that has anything to do with the issue, since I did not wait for the OTA to become available when it rolled out to me in the System Update feature (maybe sideloading OTAs triggers my device to load test/interim builds?).
Here's what I get in the TWRP log:
Anyone know how I can get the update to work? I don't want to wipe my device to flash a factory image...it's not that urgent. But if there's a way I can upgrade without waiting for the OTA to rollout to me, that'd be nice.
Thanks for any help!
Click to expand...
Click to collapse
You can flash the 5.0.1 factory image without wipe (did the same and it works well till now). Just extract system and boot.img, flash them via fastboot, wipe cache and reboot, thats it.
I may have a fix
I was having the same issue on my Nexus 5...(valentine edition ) I recieved the OTA 5.0.1 update and tried to install it automatically. (Not manually) It failed, so once it did i went into Recovery Mode and I cleared my data partition cache and wiped my dalvik cache and once i rebooted i got the "Android is upgrading" screen. I'm assuming this should fix it but I havent finished upgrading to check. Try this and let me know!
Clutchisback said:
I was having the same issue on my Nexus 5...(valentine edition ) I recieved the OTA 5.0.1 update and tried to install it automatically. (Not manually) It failed, so once it did i went into Recovery Mode and I cleared my data partition cache and wiped my dalvik cache and once i rebooted i got the "Android is upgrading" screen. I'm assuming this should fix it but I havent finished upgrading to check. Try this and let me know!
Click to expand...
Click to collapse
"Android is upgrading" after clearing the dalvik cache is normal. It is just optimizing the apps for the runtime.
Well since you have recovery installed, you can try a lot of installations. just don't forget to backup.
fury683 said:
"Android is upgrading" after clearing the dalvik cache is normal. It is just optimizing the apps for the runtime.
Click to expand...
Click to collapse
Yea you were right, it ended up doing nothing... :crying:
Nexus 5 manual download solution
indiecognition said:
I'm trying to apply the 5.0.1 LRX22C OTA update file on my Nexus 7 (2013 WiFi), which is currently running 5.0.0 Build LRX21P. I've tried installing the zip through TWRP recovery and by sideloading using the Nexus Root Toolkit from my computer...no luck either way.
Here's the issue I'm running into:
During the OTA zip install process, I get an error saying that the user build on my device is LRX21V, and the update aborts because the package expects build LRX21P. (My device settings say that I'm on LRX21P.) I upgraded to 5.0.0 in the first place by manually installing the OTA zip from build KTU84P. I'm not sure if that has anything to do with the issue, since I did not wait for the OTA to become available when it rolled out to me in the System Update feature (maybe sideloading OTAs triggers my device to load test/interim builds?).
Here's what I get in the TWRP log:
Anyone know how I can get the update to work? I don't want to wipe my device to flash a factory image...it's not that urgent. But if there's a way I can upgrade without waiting for the OTA to rollout to me, that'd be nice.
Thanks for any help!
Click to expand...
Click to collapse
I finally got the install done manually...I took the liberty of writing up some tips to and solutions to all the problems i encountered, check out my thread here: http://forum.xda-developers.com/goo...al-install-t2978147/post57615642#post57615642
I think you should just be able to just tick "Force Flash" in Wug's NRT and this should fixed the mismatch issue when you flash the images. I think he said in another thread that Google hosed something in their Flash-all.bat file which is causing the issue.
For some reason I'm just not able to Google this answer or find it here on XDA.
I'm on 5.0.1 (LRX22C) and want to go to 5.0.2 (LRX22G). I have downloaded an OTA update capture and tried to adb sideload it.
It failed. After a sec I thought, "duh. I'm rooted with franco kernel installed." I then did the following:
* Used SuperSU to unroot
* Booted to bootloader
* Flashed stock recovery and kernel
* Rebooted to recovery
* Attempted adb sideload again
This still gave a failure message.
The only other post I've seen where anyone is attempting the same suggests to use Nexus Root Tookit. I'm running Xubuntu. I've loaded it through wine but all the files it downloads are failing hash checks (though the app).
Can anyone post how to go from rooted 5.0.1 to 5.0.2 (LRX22G from LRX22C) without loosing user land data? I'd really do not want to flash the recovery image.
Notes: When trying to sideload with latest CWM recovery the script says that I'm on 4.0.4 (I think) and with TWRP it says I'm on 4.3. With stock recovery it gives me an error about the recovery script (7) or something similar.
Thanks,
Mike G.
Make sure you have downloaded the proper OTA for Nexus 7(2013).
Hashcheck fails in Nexus Root Toolkit is common.After Hashfails,there will be a dialog box which contains the steps to do it manually with the Link to the files.Download it & follow the instruction.
I hope this helps
I'm having the exact same problem. I'm attaching what's appearing on TWRP.
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
I just used wugfresh's toolbox to do it. A piece of cake. I enjoyed a cup of coffee while I watched being updated.
You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.
yosmokinman said:
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
So I can just ”fastboot flash system system.img" from the 5.0.2 image and not loose data?
That seems like it would be the easiest. I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Sent from my Nexus 7 using XDA Free mobile app
^Yes. It's a good idea to flash boot as well just to get in the habit of it, it didn't change this time I don't think but I could later. Only flash the bootloader if it's a new version no need otherwise.
I simply ran:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
Done, flash su through twrp to get root back.
You probably don't need to format cache but theres no reason not to and it could save you some trouble.
newkydawg said:
You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.
Click to expand...
Click to collapse
that worked perfectly for me. thx
mikejr83 said:
I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Click to expand...
Click to collapse
NRT opens a terminal window (a real-time log) and tells you exactly what it's doing while it does its work.
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
I have a n7 2013 I have already rooted and installed twrp and SuperSU. I'm currently running 4.4.2 and to update to 5.02. Currently I'm getting the ota update msg for 4.4.3 which I've continued to ignore. With google not messaging me to update to 5.02 makes me think it's required to go to 4.4.3,4.4.4,5,5.02 is that correct? Or can one jump directly to 5.02? I want to keep root and twrp and my existing data I see mentioning of restoring stock recovery first. Why would one do that? What's the point of installing a custom recovery in the first place?
Long time ago I read that ota will work when rooted, but you'll lose root which then can be restored with twrp without losing data. Is that no longer true? Or is it only true of KitKat but not lollipop?
I installed the 8.1 dp on my pixel 2 xl and I have decided to go back to android 8.0. I signed out of the beta and the OTA showed up as it was supposed to, from there I tried to install the downgrading OTA but it came up with a generic error (update was not able to be installed) from there I decided to try flashing the factory image and this error came up
writing 'bootb'...
FAILED (remote: No such partition.)
and when I rebooted it booted fine but was still on android 8.1. I also tried manually flashing the system partition as I noticed the script made no mention of flashing system, it came up with the error
sending sparse 'systemb' 1/4 (524284 KB)...
OKAY [ 16.552s]
writing 'systemb' 1/4...
FAILED (remote: No such partition.)
and once again after a reboot it went back to android 8.1. Any help is appreciated, thanks.
Download and flash the entire Factory image from Google's factory image page. That should work. However, this will wipe your phone.
I did flash the factory image which is what resulted in the partition error.
If you updated OTA, you can opt out of the beta, then go back to Software updates on your phone, and it will downgrade you back to 8.0.
Make sure you have the latest version of fastboot and flash the entire factory image using the flashall script. Should work.
Moostafa29 said:
If you updated OTA, you can opt out of the beta, then go back to Software updates on your phone, and it will downgrade you back to 8.0.
Click to expand...
Click to collapse
I already tried downgrading through the OTA, it came up with a generic error.
clnzx2 said:
Make sure you have the latest version of fastboot and flash the entire factory image using the flashall script. Should work.
Click to expand...
Click to collapse
It's been a while since i've updated adb, that might be the issue. I'll try it when i get home.
I think you're missing underscores. The partitions that you are flashing to should be boot_b and system_b. Also, it is crucial to use the latest version of fastboot (adb is not used).
I always open the flash all script to read the text then I do exactly that manually, and of course I skip the -w (which will wipe) through fastboot. Usually works great but I haven't tried yet on the Pixel 2 XL,
TheSt33v said:
I think you're missing underscores. The partitions that you are flashing to should be boot_b and system_b. Also, it is crucial to use the latest version of fastboot (adb is not used).
Click to expand...
Click to collapse
I'll update fastboot, maybe the flash-all script that is provided is incorrectly formatted so I'll try editing it to have underscores.
TheDonXR said:
I always open the flash all script to read the text then I do exactly that manually, and of course I skip the -w (which will wipe) through fastboot. Usually works great but I haven't tried yet on the Pixel 2 XL,
Click to expand...
Click to collapse
I tried doing this somewhat, I'll try going through this all the way but with the underscores as suggested above.
Afriendlytrashcan said:
I'll update fastboot, maybe the flash-all script that is provided is incorrectly formatted so I'll try editing it to have underscores.
I tried doing this somewhat, I'll try going through this all the way but with the underscores as suggested above.
Click to expand...
Click to collapse
I just downloaded the most recent factory image and the flash-all script doesn't mention flashing the boot image at all. It uses the update command to flash all of the necessary images. If you are looking at a script that flashes things differently, it's probably the wrong script.
If I had to take a guess, I'd say that the new version of fastboot knows to flash things differently with the new Pixels than with other devices, so the update command means something different to the old version than it does to the new version. When you tried the flash-all script initially, you were using the old version of fastboot so it tried to flash the image in a way that is not correct for the current pixels. My bet is that if you use the flash-all script with the newer fastboot, things will go better for you.
Afriendlytrashcan said:
I already tried downgrading through the OTA, it came up with a generic error.
It's been a while since i've updated adb, that might be the issue. I'll try it when i get home.
Click to expand...
Click to collapse
That is your problem. Update to latest tools and it will work. :good:
TheSt33v said:
I just downloaded the most recent factory image and the flash-all script doesn't mention flashing the boot image at all. It uses the update command to flash all of the necessary images. If you are looking at a script that flashes things differently, it's probably the wrong script.
If I had to take a guess, I'd say that the new version of fastboot knows to flash things differently with the new Pixels than with other devices, so the update command means something different to the old version than it does to the new version. When you tried the flash-all script initially, you were using the old version of fastboot so it tried to flash the image in a way that is not correct for the current pixels. My bet is that if you use the flash-all script with the newer fastboot, things will go better for you.
Click to expand...
Click to collapse
clnzx2 said:
That is your problem. Update to latest tools and it will work. :good:
Click to expand...
Click to collapse
Sounds good! I'll try it a bit later, my fingers have never been more crossed.
It worked! After updating fastboot the flash-all zip worked perfectly. Thanks everyone for your help!
Hey everyone. Just tried 9 DP1 and wanted to revert to 8.1 and just ran into this.
Since it can be overread easily: for the next one who's searching for this:
Edit the "flash-all.bat" (or .sh on Linux) and delete the "-w" after the fastboot command that flashes the ZIP.
You can wipe with fastboot or within recovery. If the system dows not boot, the Pixel 2 XL starts the recovery automatically and asks if you want to wipe.
Wasten over an hour, it's f*late and I'm tired, it's 1:16 AM here right now.
EDIT: You of course need to unlock and relock twice on the 2 XL
fastboot flashing unlock_critical
fastboot flashing unlock
fastboot flashing lock_critical
fastboot flashing lock
TimeTurn said:
Hey everyone. Just tried 9 DP1 and wanted to revert to 8.1 and just ran into this.
Since it can be overread easily: for the next one who's searching for this:
Edit the "flash-all.bat" (or .sh on Linux) and delete the "-w" after the fastboot command that flashes the ZIP.
You can wipe with fastboot or within recovery. If the system dows not boot, the Pixel 2 XL starts the recovery automatically and asks if you want to wipe.
Wasten over an hour, it's f*late and I'm tired, it's 1:16 AM here right now.
EDIT: You of course need to unlock and relock twice on the 2 XL
fastboot flashing unlock_critical
fastboot flashing unlock
fastboot flashing lock_critical
fastboot flashing lock
Click to expand...
Click to collapse
Sooooo....you were able to get back to 8.1 and then locked then unlocked the bootloader???
Badger50 said:
Sooooo....you were able to get back to 8.1 and then locked then unlocked the bootloader???
Click to expand...
Click to collapse
He said he was tired...
galaxys said:
He said he was tired...
Click to expand...
Click to collapse
Well shucks! ???
so actualy there is option to go back in versions?
that's nice!
I7210I said:
so actualy there is option to go back in versions?
that's nice!
Click to expand...
Click to collapse
It should be possible since the PDP1 is not yet official. More than likely, you'll need to do a full wipe, and clean flash to get back to 8.1 ?
Badger50 said:
It should be possible since the PDP1 is not yet official. More than likely, you'll need to do a full wipe, and clean flash to get back to 8.1 [emoji50]
Click to expand...
Click to collapse
so it's not quite works now?
in nexus it was worked right away
Sent from my Pixel 2 XL using Tapatalk