I'm trying to go NMF26U from NMF26O (rooted, stock rec) and I have the ~48mb OTA file. I boot to recovery, to go apply update from ADB and attempt to sideload. I get to Step 1/2 and then says error applying update 20 kDownloadState InitializationError and then E:unknown volume for path. Installation aborted. What am I missing?
km8j said:
I'm trying to go NMF26U from NMF26O (rooted, stock rec) and I have the ~48mb OTA file. I boot to recovery, to go apply update from ADB and attempt to sideload. I get to Step 1/2 and then says error applying update 20 kDownloadState InitializationError and then E:unknown volume for path. Installation aborted. What am I missing?
Click to expand...
Click to collapse
Just flash the whole image from Google. Edit the flash all bat file and remove -w from the file so you save your data and apps.
Then reroot.
Get the full OTA from here - Full OTA Images for Nexus and Pixel Devices
I had the same issues. Made sure I had the latest ADB/Fastboot executables and correct drivers from Google. Lastly for me I also had to be on a USB2.0 port on my PC since it won't work on a USB3.0 port on my machine.
I ended up doing the full OTA image in the link via ADB. Still rec'd the E:unknown volume error but everything installed correctly and works as expected.
FYI: I have unlocked boot loader but everything else is stock (stock bootloader, stock recovery, stock system, etc.)
TonikJDK said:
Just flash the whole image from Google. Edit the flash all bat file and remove -w from the file so you save your data and apps.
Then reroot.
Click to expand...
Click to collapse
Hmm... Okay I will try this if next method fails. Thanks.
mrZoSo said:
Get the full OTA from here - Full OTA Images for Nexus and Pixel Devices
Click to expand...
Click to collapse
donslade said:
I had the same issues. Made sure I had the latest ADB/Fastboot executables and correct drivers from Google. Lastly for me I also had to be on a USB2.0 port on my PC since it won't work on a USB3.0 port on my machine.
I ended up doing the full OTA image in the link via ADB. Still rec'd the E:unknown volume error but everything installed correctly and works as expected.
FYI: I have unlocked boot loader but everything else is stock (stock bootloader, stock recovery, stock system, etc.)
Click to expand...
Click to collapse
So did you still adb sideload the Zip? Did that wipe the device?
km8j said:
Hmm... Okay I will try this if next method fails. Thanks.
So did you still adb sideload the Zip? Did that wipe the device?
Click to expand...
Click to collapse
Yes and it did not wipe the device.
Here's a nice little walkthrough
Pixel: How to Manually Sideload an OTA Update
mrZoSo said:
Here's a nice little walkthrough
Pixel: How to Manually Sideload an OTA Update
Click to expand...
Click to collapse
That guide says use Minimal Fastboot. That is bad advice. It may work for a sideload, but many of the new fastboot commands are not in it, and it does not support our larger partitions. Or our dual partitions.
So sub the Google versions of fastboot and adb in that guide.
This worked. Thanks all!
TonikJDK said:
That guide says use Minimal Fastboot. That is bad advice. It may work for a sideload, but many of the new fastboot commands are not in it, and it does not support our larger partitions. Or our dual partitions.
So sub the Google versions of fastboot and adb in that guide.
Click to expand...
Click to collapse
True, but the guide was written just for sideloading the OTA, and works at this point.
Moving forward, you can always get the platform tools w/ADB, Fastboot from Google, without having to get the whole SDK or Android Studio.
Latest Platform Tools from Google for Windows
Related
Hey guy's only wanted to do a factory reset but I idiot just wiped everything...
So nothing was anymore on it. I downloaded this file:
OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401
As I have 4.09.401, CID-HTC__102...
So I was very lost and extracted firmware.zip out of it and flashed it over "fastboot oem rebootRUU" - "fastboot flash zip firmware.zip"
It is also now "Relocked" with S-OFF....
I'm stuck, I need my phone the next few days very often...
I dont know what to do anymore if I try to do the same with the OTA zip file it says FAILED (remote: 24 parsing android-info fail)
(When I tried before with TWRP ADB Sideload before I flashed the firmware.zip, it told me "file_getprop failed to stat /system/build.prop"
What can I do now to get my phone working again
Which version of hboot?
Which version of TWRP?
Are you able to connect to your phone via fastboot?
Are you able to connect to your phone via adb (from within TWRP)?
jollywhitefoot said:
Which version of hboot?
Which version of TWRP?
Are you able to connect to your phone via fastboot?
Are you able to connect to your phone via adb (from within TWRP)?
Click to expand...
Click to collapse
- HBOOT 2.22.000
- openrecovery-twrp-2.7.1.0-m4.img (It's the only version where I even can see my devices with "adb devices")
- Yes I am
- Not really I can go with ADB Sideload but using "adb sideload" does not work...
It tells me:
sending: 'rom.zip' 100%
On my phone it's saved under /data/media/sideload.zip but it tells me:
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/data/media/sideload.zip'
Click to expand...
Click to collapse
I had a similar issue. Adb only seemed to work on older version of twrp, except in reality, it wasn't working at all. First thing you need to do is get adb working fully to where you can push a Rom to your phone. The problem is likely your Windows drivers and not your phone, so quit trying to flash firmware to fix your phone. For me, I installed a clean copy of Windows xp on an old computer and then set fastboot and Adb up on it. I've also gotten adb and fastboot working using ubuntu live CD. I'll try and find instructions for that method (it's super easy and will run on your CD drive, so you don't need to format hd out install anything).
Once adb works, you can just push any sense6 Rom and then install in twrp and you'll be good to go.
Edit: read posts 17 & 22 here for information on getting ubuntu live CD to work.
http://forum.xda-developers.com/htc-one-mini/help/help-urgent-os-recovery-t2859034/page2
jollywhitefoot said:
I had a similar issue. Adb only seemed to work on older version of twrp, except in reality, it wasn't working at all. First thing you need to do is get adb working fully to where you can push a Rom to your phone. The problem is likely your Windows drivers and not your phone, so quit trying to flash firmware to fix your phone. For me, I installed a clean copy of Windows xp on an old computer and then set fastboot and Adb up on it. I've also gotten adb and fastboot working using ubuntu live CD. I'll try and find instructions for that method (it's super easy and will run on your CD drive, so you don't need to format hd out install anything).
Once adb works, you can just push any sense6 Rom and then install in twrp and you'll be good to go.
Edit: read posts 17 & 22 here for information on getting ubuntu live CD to work.
http://forum.xda-developers.com/htc-one-mini/help/help-urgent-os-recovery-t2859034/page2
Click to expand...
Click to collapse
The problem is that I cant install the ROM.
I've push'ed it do the ROM but as you can see my post above TWRP only gives me error :/
LuvMyHTC21 said:
Hey guy's only wanted to do a factory reset but I idiot just wiped everything...
So nothing was anymore on it. I downloaded this file:
OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401
As I have 4.09.401, CID-HTC__102...
So I was very lost and extracted firmware.zip out of it and flashed it over "fastboot oem rebootRUU" - "fastboot flash zip firmware.zip"
It is also now "Relocked" with S-OFF....
Click to expand...
Click to collapse
just try to flash not OTA, but ROM
version 2 from here will be Ok
Sweet Jesus, finally after 9 hours (no joke) I got it working, thank you so much !
Long story short, I had an issue with my HTC One X that I received from a friend. It would load up and then immediately restart about 15 seconds after getting to lock screen. I was just stuck in a boot loop.
So I decided to flash a new rom onto the phone, but neither I nor my friend had created a backup so now my OS is wiped.
I can boot into recovery mode, though. I'm not sure what the first screen is called, but it's the one with the skating androids. It tells me:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.45.0622
eMMC-boot
Jun 11 2012,14:36:28
Click to expand...
Click to collapse
When I enter into recovery, it appears that I have TWRP v2.3.1.0.
In here, I cannot install any roms. They appear to fail. Installing says:
Zip Install Complete
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/sdcard/pac.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Error flashing zip '/sdcard/pac.zip'
Updating partition details...
Click to expand...
Click to collapse
Failed
Click to expand...
Click to collapse
I had read somewhere that I need to upgrade my TWRP in order to properly install roms, but at the current moment, running adb devices in a command prompt pointed at my adt bundle folder does not work. It just has a blank list.
Attached is a photo with what I think are the most relevant things I've downloaded/installed so far.
It does look like I can connect my phone to the computer via Mount USB Storage, but sideloader does not work since adb devices is blank.
Any thoughts?
kpxexpress said:
Long story short, I had an issue with my HTC One X that I received from a friend. It would load up and then immediately restart about 15 seconds after getting to lock screen. I was just stuck in a boot loop.
So I decided to flash a new rom onto the phone, but neither I nor my friend had created a backup so now my OS is wiped.
I can boot into recovery mode, though. I'm not sure what the first screen is called, but it's the one with the skating androids. It tells me:
When I enter into recovery, it appears that I have TWRP v2.3.1.0.
In here, I cannot install any roms. They appear to fail. Installing says:
I had read somewhere that I need to upgrade my TWRP in order to properly install roms, but at the current moment, running adb devices in a command prompt pointed at my adt bundle folder does not work. It just has a blank list.
Attached is a photo with what I think are the most relevant things I've downloaded/installed so far.
It does look like I can connect my phone to the computer via Mount USB Storage, but sideloader does not work since adb devices is blank.
Any thoughts?
Click to expand...
Click to collapse
The first screen with the skating Androids is your bootloader, FYI. Adb commands aren't used for flashing a recovery, fastboot commands are used. You do indeed need to update TWRP, the version you currently have installed isn't compatible with any current ROMs. Click the guide link in my signature, there are instructions on anything you need to do there.
Transmitted via Bacon
timmaaa said:
The first screen with the skating Androids is your bootloader, FYI. Adb commands aren't used for flashing a recovery, fastboot commands are used. You do indeed need to update TWRP, the version you currently have installed isn't compatible with any current ROMs. Click the guide link in my signature, there are instructions on anything you need to do there.
Transmitted via Bacon
Click to expand...
Click to collapse
I think I have my phone on Fastboot right now. I have the white screen that has FASTBOOT USB written on it with
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWERDOWN
Click to expand...
Click to collapse
underneath the control options. I've attached a picture below.
I Shift + Right Clicked to open command prompt in the folder with fastboot.exe and my recoveryfilename.img file.
In the command prompt, I enter in the command
Code:
fastboot flash recovery "recoveryfilename.img"
and it just stays on
Code:
< waiting for device >
I still can't figure out how to update my TWRP without an OS.
kpxexpress said:
I think I have my phone on Fastboot right now. I have the white screen that has FASTBOOT USB written on it with
underneath the control options. I've attached a picture below.
I Shift + Right Clicked to open command prompt in the folder with fastboot.exe and my recoveryfilename.img file.
In the command prompt, I enter in the command
Code:
fastboot flash recovery "recoveryfilename.img"
and it just stays on
Code:
< waiting for device >
I still can't figure out how to update my TWRP without an OS.
Click to expand...
Click to collapse
What OS are you running on your PC? Did adb/fastboot work at any point?
timmaaa said:
What OS are you running on your PC? Did adb/fastboot work at any point?
Click to expand...
Click to collapse
I'm running Windows 8.1 Pro. ADB worked once. I was able to get it to detect in recovery. ADB Devices would give me the customary string of numbers followed by "RECOVERY" and then I rebooted the phone for some reason and it stopped working. Oh, during that time I was also able to move stuff to the phone via ADB Sideload, but I would get pretty much the same errors when installing, which I later found out was because my TWRP was too old. I can't seem to get it to connect via ADB/Fastboot anymore. I can, however mount via TWRP.
kpxexpress said:
I'm running Windows 8.1 Pro. ADB worked once. I was able to get it to detect in recovery. ADB Devices would give me the customary string of numbers followed by "RECOVERY" and then I rebooted the phone for some reason and it stopped working. Oh, during that time I was also able to move stuff to the phone via ADB Sideload, but I would get pretty much the same errors when installing, which I later found out was because my TWRP was too old. I can't seem to get it to connect via ADB/Fastboot anymore. I can, however mount via TWRP.
Click to expand...
Click to collapse
There's your problem. Windows 8.1 isn't compatible with fastboot. You'll need to get access to a PC with a lower version of Windows so you can update TWRP.
timmaaa said:
There's your problem. Windows 8.1 isn't compatible with fastboot. You'll need to get access to a PC with a lower version of Windows so you can update TWRP.
Click to expand...
Click to collapse
Oh, really? Will 8 or 7 work?
I used a Windows 7 laptop and was able to update my TWRP to v2.7.0.8!
Seem to still be unable to detect devices via adb devices command.
Ok. Had to update my drivers.
I'm following your instructions on How To Install A ROM with TWRP Recovery, and now my issue is that it is saying
Code:
error flashing zip '/sdcard/pac.zip'
I've included a picture below.
kpxexpress said:
Oh, really? Will 8 or 7 work?
I used a Windows 7 laptop and was able to update my TWRP to v2.7.0.8!
Seem to still be unable to detect devices via adb devices command.
Ok. Had to update my drivers.
I'm following your instructions on How To Install A ROM with TWRP Recovery, and now my issue is that it is saying
Code:
error flashing zip '/sdcard/pac.zip'
I've included a picture below.
Click to expand...
Click to collapse
You're gonna need to get s-off so you can update your firmware. In order to get s-off you'll need to flash the Kickdroid ROM. Once you've flashed Kickdroid you can go to the Rumrunner s-off site and get s-off. Then follow the instructions in my guide thread to update your firmware.
timmaaa said:
You're gonna need to get s-off so you can update your firmware. In order to get s-off you'll need to flash the Kickdroid ROM. Once you've flashed Kickdroid you can go to the Rumrunner s-off site and get s-off. Then follow the instructions in my guide thread to update your firmware.
Click to expand...
Click to collapse
Alright, so I managed to get the Kickdroid ROM working! So right now I at least have a working phone that I can use! Thanks a TON for getting me this far.
Rumrunnner seems to not be working right for me. I'm in ADB recovery and can confirm an ADB connection, but it's still displaying
Code:
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on? Drivers?)
But it's a start. I'll have to make sure I'm following all instructions carefully.
I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.
pds6 said:
I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.
Click to expand...
Click to collapse
What recovery have you got and what file are you sideloading?
All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.
rootSU said:
What recovery have you got and what file are you sideloading?
Click to expand...
Click to collapse
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1
pds6 said:
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1
Click to expand...
Click to collapse
You can't sideload a factory image. You must use fastboot.
zagorteney said:
All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.
Click to expand...
Click to collapse
How can I make my Acer read Nexus 5 to install factory image via command prompt?
It comes up in Device Manager, driver seems to be installed fine, as Android Device but does not connect properly (no devices listed in "adb devices")
You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus
rootSU said:
You can't sideload a factory image. You must use fastboot.
Click to expand...
Click to collapse
Oh okay, my bad. Do I have any options to sideload anything, or is there a way to make phone connect for fastboot? Again, it's visible in Device Manager w/drivers, but not in command prompt. Thank you
will try above suggestions and report back
rootSU said:
You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus
Click to expand...
Click to collapse
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."
pds6 said:
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."
Click to expand...
Click to collapse
Win 7?
rootSU said:
Win 7?
Click to expand...
Click to collapse
8.1
pds6 said:
8.1
Click to expand...
Click to collapse
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Yes uninstalled drivers through Device Manager & did the restart through the settings as outlined there.
Will try to download google usb driver from here http://developer.android.com/sdk/win-usb.html#top
Edit: this driver installed correctly. Device now appears in device manager as Android Bootloader Interface (phone is at Fastboot screen)
rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed
pds6 said:
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed
Click to expand...
Click to collapse
No probs. Glad you're sorted.
So I bought a Chinese OnePlus One, and it came pre-installed with CM 11 version 11.0-XNPH33r.
Connected to wifi, and got the system update for 11.0-XNPH38r Incremental, so I click download and install.
It reboots phone, then it loads ColorOS recovery looking screen with Chinese written on it and a green loading bar, then The CM splash icons comes back and loads. (alien looking guy with an arrow circling around his head)
After all that, I go to check the version and I'm still stuck at 11.0-XNPH33r!
I tried manually doing it from ColorOS recovery with 11.0-XNPH38r Incremental zip file, it installs about 3/4 of the way and then fails.
My Kernel Version is : 3.4.0-cyanogenmod-g0ad30e5
My ColorOS Recovery Version is : 1.2 (Rooted)
I've been looking around the forums, and I see people manually updating using TWRP which I don't have.
Can someone please help me, and if you have a solution can you please give me a step by step direction since I'm new to flashing/rooting and this phone.
I have a guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
It contains instructions on how to unlock your bootloader and install TWRP recovery (sections 1 and 2). Before doing anything though you should check the status of your bootloader because it might already be unlocked. You'll need to follow the instructions at the top of the guide to install your phone drivers and also adb/fastboot via the Android SDK. Once you have done that you can boot your phone into fastboot mode (hold power + volume up), connect your phone to your PC via usb cable, open a command prompt from your fastboot folder (shift + right click anywhere within the foler, then select open command prompt here), and issue this command:
Code:
fastboot oem device-info
Please post the results here.
Thanks man, I'll try that out.
timmaaa said:
I have a guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
It contains instructions on how to unlock your bootloader and install TWRP recovery (sections 1 and 2). Before doing anything though you should check the status of your bootloader because it might already be unlocked. You'll need to follow the instructions at the top of the guide to install your phone drivers and also adb/fastboot via the Android SDK. Once you have done that you can boot your phone into fastboot mode (hold power + volume up), connect your phone to your PC via usb cable, open a command prompt from your fastboot folder (shift + right click anywhere within the foler, then select open command prompt here), and issue this command:
Code:
fastboot oem device-info
Please post the results here.
Click to expand...
Click to collapse
TY for you help. I manage to get a custom recovery (TWRP), but I still can't update past 33R, when I update I get "E:Error executing updater binary in zip '/cache/cm-bacon-3628510d76-to-ac1ccf7921-signed.zip
I also have this phone SuperSU fully rooted I think
TheOneinNeed said:
TY for you help. I manage to get a custom recovery (TWRP), but I still can't update past 33R, when I update I get "E:Error executing updater binary in zip '/cache/cm-bacon-3628510d76-to-ac1ccf7921-signed.zip
I also have this phone SuperSU fully rooted I think
Click to expand...
Click to collapse
Go to section 8 of my guide and flash the stock images. Make sure you remove the -w of the last command though or it'll wipe all your user data.
Transmitted via Bacon
timmaaa said:
Go to section 8 of my guide and flash the stock images. Make sure you remove the -w of the last command though or it'll wipe all your user data.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks man. I actually tried the flashing of 44s on the guide you sent me and it worked. Sorry for my last reply. You've been a great help and my phone is up to date.
Two last question if you don't mind. When the new update comes, can I install through Settings> About Phones> System Updates
or do I have to do something similar to the flashing I just did
after flashing my custom recovery is gone (TWRP) and the Cyanogen Mod Recovery took its place. Should I leave it like that or get TWRP and if TWRP is the answer, do I use the same method I did installing the custom recovery?
You should now have no problems receiving automatic updates through the settings menu. You can leave the stock recovery if you want to, or you can flash TWRP again. If you don't intend on flashing any custom ROMs or mods then the stock recovery should suit you just fine. Flashing a recovery is done via fastboot.
Code:
fastboot flash recovery twrp-2.8.4.1.img
(where the recovery filename is twrp-2.8.4.1.img)
timmaaa said:
You should now have no problems receiving automatic updates through the settings menu. You can leave the stock recovery if you want to, or you can flash TWRP again. If you don't intend on flashing any custom ROMs or mods then the stock recovery should suit you just fine. Flashing a recovery is done via fastboot.
Code:
fastboot flash recovery twrp-2.8.4.1.img
(where the recovery filename is twrp-2.8.4.1.img)
Click to expand...
Click to collapse
Thank you for your time and effort to help.
I appreciate it a lot. Thanks again!
I am trying to use Flashfire v0.53 to update my Google-sourced, rooted Pixel from 7.1.0 (build NDE63X) to 7.1.1 (build NMF26V). I've downloaded sailfish-ota-nmf26v-1988a458.zip to my phone and can see it with a root file browser but when I direct Flashfire to the same directory it lists no files. Any thoughts? If I'm going about updating my phone the wrong way, I'm happy to be pointed in the right direction. Thanks.
FlashFire is not working on this phone last I heard. Flash it with TWRP.
TonikJDK said:
FlashFire is not working on this phone last I heard. Flash it with TWRP.
Click to expand...
Click to collapse
Good to know, thanks.
I've tried pointing TWRP at the OTA zip I got from Google and it fails. Perhaps because I need to unroot first? I was hoping Flashfire would do that for me. `adb sideload` failed, too.
ChrisNelsonPE said:
Good to know, thanks.
I've tried pointing TWRP at the OTA zip I got from Google and it fails. Perhaps because I need to unroot first? I was hoping Flashfire would do that for me. `adb sideload` failed, too.
Click to expand...
Click to collapse
You need to use fastboot. There are a few detailed guides in the "guides" section of both the pixel and pixel xl forums.
Basically you have to edit the flashall.bat file and remove the -w option so that it doesn't wipe. Then you have to fastboot boot into twrp then reflash twrp.zip and SU.zip
All the info is here just look around
aholeinthewor1d said:
You need to use fastboot. There are a few detailed guides in the "guides" section of both the pixel and pixel xl forums.
Basically you have to edit the flashall.bat file and remove the -w option so that it doesn't wipe. Then you have to fastboot boot into twrp then reflash twrp.zip and SU.zip
All the info is here just look around
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187 seems promising. I can adapt to use sailfish vs. marlin. But I'm not sure how to know which image is for Verizon.
ChrisNelsonPE said:
Good to know, thanks.
I've tried pointing TWRP at the OTA zip I got from Google and it fails. Perhaps because I need to unroot first? I was hoping Flashfire would do that for me. `adb sideload` failed, too.
Click to expand...
Click to collapse
Copy the OTA zip you downloaded, from your phone to your computer. Reboot into TWRP. Go to Advanced and choose "ADB sideload"(not sure if that's exactly what it's called). Once the phone is waiting for ADB, go back to your computer and open a command prompt and type "adb sideload OTA.zip". OTA.zip will be the zip you downloaded. Example: if you copied it to C:\ you would type "adb sideload c:\sailfish-ota-nmf26-xxxxxxxx.zip" or whatever the zip is named.
That is how you would sideload an OTA. If you downloaded a full factory image then open "flash-all.bat" in notepad, remove the "-w"(it's towards the bottom), connect your phone, reboot to bootloader, run flash-all.bat.
Both a full image and OTA will remove your root and TWRP. You will need to re flash recovery and reroot after updating. Just follow the same guides you did originally.
fritzgerald said:
Copy the OTA zip you downloaded, from your phone to your computer. Reboot into TWRP. Go to Advanced and choose "ADB sideload"(not sure if that's exactly what it's called). Once the phone is waiting for ADB, go back to your computer and open a command prompt and type "adb sideload OTA.zip". OTA.zip will be the zip you downloaded. Example: if you copied it to C:\ you would type "adb sideload c:\sailfish-ota-nmf26-xxxxxxxx.zip" or whatever the zip is named.
That is how you would sideload an OTA. If you downloaded a full factory image then open "flash-all.bat" in notepad, remove the "-w"(it's towards the bottom), connect your phone, reboot to bootloader, run flash-all.bat.
Both a full image and OTA will remove your root and TWRP. You will need to re flash recovery and reroot after updating. Just follow the same guides you did originally.
Click to expand...
Click to collapse
I don't seem to be able to find the OTA on my phone. Not sure where it gets put.
From your description of using the full image, I imagine I 1) unzip the factory image zip, 2) edit the flash-all.bat in the result, 3) run flash-all.bat (that is, I don't rezip and try to use the package). Right?
ChrisNelsonPE said:
I don't seem to be able to find the OTA on my phone. Not sure where it gets put.
From your description of using the full image, I imagine I 1) unzip the factory image zip, 2) edit the flash-all.bat in the result, 3) run flash-all.bat (that is, I don't rezip and try to use the package). Right?
Click to expand...
Click to collapse
That's correct. If you downloaded the OTA with System Updates then I'm not sure where it gets stored. If you downloaded it from Google then it would be in your downloads folder.
You can try the guide I wrote here to sideload the full ota zip from google.
adb sideload failure
spiller37 said:
You can try the guide I wrote here to sideload the full ota zip from google.
Click to expand...
Click to collapse
That's a great guide. Alas, when I try to sideload the OTA I get:
Code:
PS C:\adb> adb sideload .\sailfish-ota-nmf26u-6ea22a0c.zip
loading: '.\sailfish-ota-nmf26u-6ea22a0c.zip'
error: closed
PS C:\adb> adb sideload .\sailfish-ota-nmf26u-6ea22a0c.zip
loading: '.\sailfish-ota-nmf26u-6ea22a0c.zip'
error: device '(null)' not found
I though the problem might be the old TWRP in my phone so I used the alpha2 I had to install rc1.
ChrisNelsonPE said:
That's a great guide. Alas, when I try to sideload the OTA I get:
I though the problem might be the old TWRP in my phone so I used the alpha2 I had to install rc1.
Click to expand...
Click to collapse
Sounds like the driver isn't recognized. Does ADB devices list your device?
ChrisNelsonPE said:
...
I though the problem might be the old TWRP in my phone so I used the alpha2 I had to install rc1.
Click to expand...
Click to collapse
Now I'm in a boot loop. TWRP -- when it comes up at all -- says it is alpha2 and it doesn't prompt for the code to decrypt my data so the directory listing is gibberish. What do I do now? Reflash 7.0? Flash 7.1?
To recap, I have a Pixel I bought from Google with an unlocked boot loader and TWRP installed but can't boot to Android.
ChrisNelsonPE said:
Now I'm in a boot loop. TWRP -- when it comes up at all -- says it is alpha2 and it doesn't prompt for the code to decrypt my data so the directory listing is gibberish. What do I do now? Reflash 7.0? Flash 7.1?
To recap, I have a Pixel I bought from Google with an unlocked boot loader and TWRP installed but can't boot to Android.
Click to expand...
Click to collapse
Alpha 2 is the wrong TWRP. You want RC1.
ChrisNelsonPE said:
That's a great guide. Alas, when I try to sideload the OTA I get:
Code:
PS C:\adb> adb sideload .\sailfish-ota-nmf26u-6ea22a0c.zip
loading: '.\sailfish-ota-nmf26u-6ea22a0c.zip'
error: closed
PS C:\adb> adb sideload .\sailfish-ota-nmf26u-6ea22a0c.zip
loading: '.\sailfish-ota-nmf26u-6ea22a0c.zip'
error: device '(null)' not found
I though the problem might be the old TWRP in my phone so I used the alpha2 I had to install rc1.
Click to expand...
Click to collapse
That looks like an ADB device driver problem. Do you see your device listed with ADB devices when in TWRP/Advanced/Sideload?
spiller37 said:
That looks like an ADB device driver problem. Do you see your device listed with ADB devices when in TWRP/Advanced/Sideload?
Click to expand...
Click to collapse
Yes.
TonikJDK said:
Alpha 2 is the wrong TWRP. You want RC1.
Click to expand...
Click to collapse
That's fine. But how do I get there from a phone which is in a boot loop running alpha1?
ChrisNelsonPE said:
That's fine. But how do I get there from a phone which is in a boot loop running alpha1?
Click to expand...
Click to collapse
I get into TWRP on my phone an do
Code:
PS C:\adb> fastboot .\twrp-3.0.2-0-RC1-fastboot-sailfish.img
< waiting for device >
on my computer and it waits forever.
ChrisNelsonPE said:
That's fine. But how do I get there from a phone which is in a boot loop running alpha1?
Click to expand...
Click to collapse
Power it down, hold power button and volume down to get it into fastboot.
Fastboot flash TWRPfilename.img
And if that does not work download the full factory image but edit flashall.bat to remove the -w which will save your data and flash the whole thing.
TonikJDK said:
...
And if that does not work download the full factory image but edit flashall.bat to remove the -w which will save your data and flash the whole thing.
Click to expand...
Click to collapse
So, I think I had to do this. `adb` lists my device but when I try to sideload it says the device (null) doesn't exist.
Do I somehow tell `fastboot` to use the factory image .zip file or do I unzip it, edit flashall.bat, then run flashall.bat?
ChrisNelsonPE said:
So, I think I had to do this. `adb` lists my device but when I try to sideload it says the device (null) doesn't exist.
Do I somehow tell `fastboot` to use the factory image .zip file or do I unzip it, edit flashall.bat, then run flashall.bat?
Click to expand...
Click to collapse
Unzip it into your fastboot directory. Then edit and run flashall.