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.
Related
On a mac here. I think I got a bit over my head here with the 2.20 root. I did all of the bootloader unlocking successfully, installed TWRP, and then downloaded CM10, and flashed the boot.img.
Now when trying to boot the phone I get stock on the screen with "This Build is for development only."
I can get into recovery, but don't really know what to do from there. I'm trying to mount, but can't get the computer to recognize the device. Tried a factory reset and it failed. I'm not quite bricked, but sort of stuck and don't know what to do. I'd love to get CM10 working, but at least I want to be able to use my phone.
I'm pretty new to Android so sorry for newbishness.
Thanks anyone for your help.
Just to add, I'm getting the message "no OS installed" when trying to reboot in recovery.
ul49 said:
On a mac here. I think I got a bit over my head here with the 2.20 root. I did all of the bootloader unlocking successfully, installed TWRP, and then downloaded CM10, and flashed the boot.img.
Now when trying to boot the phone I get stock on the screen with "This Build is for development only."
I can get into recovery, but don't really know what to do from there. I'm trying to mount, but can't get the computer to recognize the device. Tried a factory reset and it failed. I'm not quite bricked, but sort of stuck and don't know what to do. I'd love to get CM10 working, but at least I want to be able to use my phone.
I'm pretty new to Android so sorry for newbishness.
Thanks anyone for your help.
Click to expand...
Click to collapse
Did you flash the boot.img first, then the ROM?
Can you wipe System?
Sorry, what's the difference betwwen boot.img and the rom itself? I only flashed boot.img. I did wipe the system.
ul49 said:
Sorry, what's the difference betwwen boot.img and the rom itself? I only flashed boot.img. I did wipe the system.
Click to expand...
Click to collapse
The boot.img has the kernel in it. If you didn't flash the CM10.zip you have no operating system.
Wipe System, and Factory Reset
Flash boot.img
Flash the CM10.zip, flash google apps, and you should be good after that
Now flash the rom zip from recovery (twrp)
Sent from a slithery smooth phone!
So to flash the zip file for the ROM and gapps, I just enter fastboot flash boot 'rom.zip' or 'gapps.zip'?
Also, what do I do after I've flashed them?
Thanks so much for your help
ul49 said:
So to flash the zip file for the ROM and gapps, I just enter fastboot flash boot 'rom.zip' or 'gapps.zip'?
Also, what do I do after I've flashed them?
Thanks so much for your help
Click to expand...
Click to collapse
no,you flash the boot.img in fastboot, and then you flash the rom.zip and gapps.zip from recovery (twrp)
ul49 said:
So to flash the zip file for the ROM and gapps, I just enter fastboot flash boot 'rom.zip' or 'gapps.zip'?
Also, what do I do after I've flashed them?
Thanks so much for your help
Click to expand...
Click to collapse
No, do a clean wipe.
boot your phone into fastboot
download the fastboot files http://www.mediafire.com/?4dx982z93w8z7wk and extract them to your desktop
on your computer, open up cmd and type
cd desktop
cd foldername (the folder that has fastboot.exe)
fastboot flash boot boot.img
reboot into recovery
flash CM10, flash gapps, reboot
I see. The problem is that I seem to be unable to mount my phone and sd card through recovery.
Trying to push the zips using adb using './adb push cm10.zip/sdcard' but when I enter this command in terminal it seems to just reload adb, and not push the file.
ul49 said:
Trying to push the zips using adb using './adb push cm10.zip/sdcard' but when I enter this command in terminal it seems to just reload adb, and not push the file.
Click to expand...
Click to collapse
I think you are typing the command wrong
./adb push file /destination
or ./adb push cm10.zip /mnt/sdcard
./adb push cm10.zip /sdcard
whatever the mount point is for the sdcard
Tried that too. It just reloads the opening adb dialogue.
ul49 said:
Tried that too. It just reloads the opening adb dialogue.
Click to expand...
Click to collapse
does ./adb devices return your phone as connected?
Well, now it doesn't. Instead of reloading the adb dialogue now, when I try the push command it says device not found. Just came out of nowhere. How do I make it recognize the phone again?
Thanks for bearing with me here. I think I'm really close.
ul49 said:
Well, now it doesn't. Instead of reloading the adb dialogue now, when I try the push command it says device not found. Just came out of nowhere. How do I make it recognize the phone again?
Thanks for bearing with me here. I think I'm really close.
Click to expand...
Click to collapse
I'm not familiar with OS X and android, are there any specific drivers you may need to install?
Are you in your bootloader or recovery?
All necessary drivers were installed. The device was being recognized before, but for some reason isn't now. I'm stuck on the "This build is for development purposes only" screen now since I can't get into recovery or bootloader using adb now since the device isn't recognized...
Ok, I'm connected again somehow. Now just trying to figure out this pushing issue. Entered this command './adb push /android/cm10.zip /sdcard and it looked like it was working then said "failed to copy to /sdcard"
ul49 said:
Ok, I'm connected again somehow. Now just trying to figure out this pushing issue. Entered this command './adb push /android/cm10.zip /sdcard and it looked like it was working then said "failed to copy to /sdcard"
Click to expand...
Click to collapse
because it is probably at /mnt/sdcard
Successfully pushed the files. Of course, I've hit another problem. Trying to install the ROM through TWRP and it's failing. Same with Gapps. I'm seeing "unable to mount /sdcard" and unable to mount storage. I've already cleared cache, wiped system, factory reset/
[Q] 2 Issues when rooting: No SU binary installed, & red triangle on dead android.
This is my second root ever, I am still very new to this process but my first root went smoothly.
So basically the problem started when I copied the SuperSU file onto my phone using the command
adb push UPDATE-SuperSU-vX.XX.zip /sdcard/
Click to expand...
Click to collapse
After that, I tried finding the zip file through the TWRP recovery screen but I couldn't. I figured I'd go reboot my device. Once I pressed on reboot, a screen popped up asking if I wanted to install SuperSU, "ok cool" I thought and swiped to the right to install. At this point I thought my phones rooted.
I open up SuperSU and I get the error message:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!
Click to expand...
Click to collapse
I'm on 4.2.2
I decided to go back to recovery mode and that's when I saw the red triangle over the dead android. I thought I had bricked my phone but i'm back to my regular home screen.
Can anyone help me please?
How did you apply TWRP? Did you boot it or flash it. If you chose to boot it, the custom recovery won't stick.
The dead android you are seeing is the stock recovery.
My advice is to boot back into the bootloader and flash the recovery, then flash the SU,zip
FrostedFluke said:
This is my second root ever, I am still very new to this process but my first root went smoothly.
So basically the problem started when I copied the SuperSU file onto my phone using the command
After that, I tried finding the zip file through the TWRP recovery screen but I couldn't. I figured I'd go reboot my device. Once I pressed on reboot, a screen popped up asking if I wanted to install SuperSU, "ok cool" I thought and swiped to the right to install. At this point I thought my phones rooted.
I open up SuperSU and I get the error message:
I'm on 4.2.2
I decided to go back to recovery mode and that's when I saw the red triangle over the dead android. I thought I had bricked my phone but i'm back to my regular home screen.
Can anyone help me please?
Click to expand...
Click to collapse
The red triangle with the android is just the stock recovery. What commands are you using to flash TWRP? I'm assuming you unlocked the boot loader.
You should type in "fastboot flash recovery name_of_twrp_file.img"
Download the supersu.zip from http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip and put it on your phone while the phone is on and connected to a computer. (Just drag it in)
Then reboot into TWRP and flash that file.
Say NO..again NO to the part when it asks you if you want to root. It shouldn't ask you, but if it does, say no.
El Daddy said:
How did you apply TWRP? Did you boot it or flash it. If you chose to boot it, the custom recovery won't stick.
The dead android you are seeing is the stock recovery.
My advice is to boot back into the bootloader and flash the recovery, then flash the SU,zip
Click to expand...
Click to collapse
I used this guide http://forum.xda-developers.com/showthread.php?t=2507905
and by flashing the recovery, you mean by reflashing it? using "flashboot flash recovery recovery.img" as the command?
aooga said:
The red triangle with the android is just the stock recovery. What commands are you using to flash TWRP? I'm assuming you unlocked the boot loader.
You should type in "fastboot flash recovery name_of_twrp_file.img"
Download the supersu.zip from http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip and put it on your phone while the phone is on and connected to a computer. (Just drag it in)
Then reboot into TWRP and flash that file.
Say NO..again NO to the part when it asks you if you want to root. It shouldn't ask you, but if it does, say no.
Click to expand...
Click to collapse
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905
FrostedFluke said:
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
Maybe, try using the new zip. Flash TWRP again. It shouldn't be going back to the stock recovery when you reboot unless you chose to just boot it and not flash it.
FrostedFluke said:
I used this guide http://forum.xda-developers.com/showthread.php?t=2507905
and by flashing the recovery, you mean by reflashing it? using "flashboot flash recovery recovery.img" as the command?
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
Yep, that is the correct command. I would recommend using the most recent SU.zip as well.
aooga said:
Maybe, try using the new zip. Flash TWRP again. It shouldn't be going back to the stock recovery when you reboot unless you chose to just boot it and not flash it.
Click to expand...
Click to collapse
I'll install the SuperSU you linked to me thanks! would you mind explaining to me how to flash it again?
I just open bootloader, command window then flash the recovery file once more?
FrostedFluke said:
I'll install the SuperSU you linked to me thanks! would you mind explaining to me how to flash it again?
I just open bootloader, command window then flash the recovery file once more?
Click to expand...
Click to collapse
Yeah just download THIS FILE first then boot into the bootloader and type in "fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img" without the quotes in a CMD window.
After it says finished, use the volume keys to select "Recovery Mode" and press the power button to go into it. Then flash the supersu file that you transferred earlier. (the new version).
aooga said:
Yeah just download THIS FILE first then boot into the bootloader and type in "fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img" without the quotes in a CMD window.
After it says finished, use the volume keys to select "Recovery Mode" and press the power button to go into it. Then flash the supersu file that you transferred earlier. (the new version).
Click to expand...
Click to collapse
I'm in Recovery mode and I still can't find the SuperSU zip file even after i've used the command "adb push"
FrostedFluke said:
I'm in Recovery mode and I still can't find the SuperSU zip file even after i've used the command "adb push"
Click to expand...
Click to collapse
Try adb sideloading it.
Put the Su.zip on your computer in the same folder as your adb.exe
Choose adb sideload on twrp.
Then the command: adb sideload SU.zip
El Daddy said:
Try adb sideloading it.
Put the Su.zip on your computer in the same folder as your adb.exe
Choose adb sideload on twrp.
Then the command: adb sideload SU.zip
Click to expand...
Click to collapse
you mean "adb sideload UPDATE-SuperSU-v1.89.zip"? (sorry I just want to be 100% sure so I make no mistakes)
FrostedFluke said:
you mean "adb sideload UPDATE-SuperSU-v1.89.zip"? (sorry I just want to be 100% sure so I make no mistakes)
Click to expand...
Click to collapse
Yep! I didn't know what the file was named so I just shortened it up to SU.zip
Pro-tip: You can rename files to something shorter such as SU.zip to make it quicker to type in command and eliminate the possibility of mistakes.
El Daddy said:
Yep! I didn't know what the file was named so I just shortened it up to SU.zip
Pro-tip: You can rename files to something shorter such as SU.zip to make it quicker to type in command and eliminate the possibility of mistakes.
Click to expand...
Click to collapse
I get this on my command prompt: "error: closed"
FrostedFluke said:
I get this on my command prompt: "error: closed"
Click to expand...
Click to collapse
run the command: adb usb
Then try sideloading
El Daddy said:
run the command: adb usb
Then try sideloading
Click to expand...
Click to collapse
same error.
I have the option to "swipe to start sideloading" should I swipe first? then run the command?
FrostedFluke said:
same error.
I have the option to "swipe to start sideloading" should I swipe first? then run the command?
Click to expand...
Click to collapse
yes
El Daddy said:
yes
Click to expand...
Click to collapse
It worked, thanks so much man I appreciate the help! you're a lifesaver!
one other quick question. Just to be sure, is there anyway of knowing whether or not my device has been rooted? how will I know for sure?
FrostedFluke said:
It worked, thanks so much man I appreciate the help! you're a lifesaver!
one other quick question. Just to be sure, is there anyway of knowing whether or not my device has been rooted? how will I know for sure?
Click to expand...
Click to collapse
You are welcome. I am always glad to help someone doing things the right way!
Run an app that requires root. If SuperSu requests access, you are rooted.
El Daddy said:
You are welcome. I am always glad to help someone doing things the right way!
Run an app that requires root. If SuperSu requests access, you are rooted.
Click to expand...
Click to collapse
Yup! it's rooted :victory:
FrostedFluke said:
Yup! it's rooted :victory:
Click to expand...
Click to collapse
Congrats!
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.
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
So I rooted my OnePlus 6 through magisk using the command prompt method. And for some odd reason whenever I go to flash the TWRP image it just comes up " the image file is corrupt". I don't know if it's the TWRP download link on there website. But I've tried it on my laptop and another laptop. I keep getting corrupt image file. Anybody know a way to get TWRP without PC or a different method.
did you try downloading the file again
RootJunky J.R said:
So I rooted my OnePlus 6 through magisk using the command prompt method. And for some odd reason whenever I go to flash the TWRP image it just comes up " the image file is corrupt". I don't know if it's the TWRP download link on there website. But I've tried it on my laptop and another laptop. I keep getting corrupt image file. Anybody know a way to get TWRP without PC or a different method.
Click to expand...
Click to collapse
Use this link.
https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
Ajaykumar21066 said:
did you try downloading the file again
Click to expand...
Click to collapse
Yeah I have tried multiple times. Downloaded on my laptop. Another laptop. Downloaded it on my phone and transfered . Just keeps coming up corrupt.
mikex8593 said:
Use this link.
https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
Click to expand...
Click to collapse
This download link just leads to the TWRP page.
You don't flash that img file, you fastboot boot it. The zip installer is what you flash in twrp.
iElvis said:
You don't flash that img file, you fastboot boot it. The zip installer is what you flash in twrp.
Click to expand...
Click to collapse
Yeah when I fastboot the image to the phone it just keeps coming up corrupt
iElvis said:
You don't flash that img file, you fastboot boot it. The zip installer is what you flash in twrp.
Click to expand...
Click to collapse
fastboot flash boot_a twrp.img
fastboot flash boot_b twrp.img
Where twrp.img is the img file from TWRP. You can drag and drop or manually change directory to install your TWRP. It works either way.
Yeah ive been reading forums and apparently it's nothing to do with what I'm doing. It's a security update on windows. I just uninstalled it. Gonna try to mount an img file see if it works.
Update that wasn't the issue... I'm sure it's something to do with windows 10.
RootJunky J.R said:
Update that wasn't the issue... I'm sure it's something to do with windows 10.
Click to expand...
Click to collapse
Just to confirm, you're following this procedure exactly? Particularly the part in red? I just ask because I've see so many people convinced they're doing it right only to realize they had one thing wrong.
lollyjay said:
TWRP download https://dl.twrp.me/enchilada/
Download twrp-3.2.1-0-enchilada.img from twrp.me site to your pc
Download twrp-installer-enchilada-3.2.1-0.zip from twrp.me to your phone
Hook phone to pc USB with factory red cable (or other usb-c cable that you have tested)
Reboot phone into bootloader
On your pc, go to the location where you downloaded the twrp-3.2.1-0-enchilada.img image
Type fastboot devices to make sure that you get a response showing your phone and serial number
Type fastboot boot twrp-3.2.1-0-enchilada.img
Your phone will boot into twrp YOU WILL BE ASKED TO ENTER YOUR PIN/PATTERN/PASSWORD. IF YOU MAKE A MISTAKE, TWRP WILL LOCK UP; YOU MUST GO BACK TO THIS STEP: "Reboot phone into bootloader"
From twrp, install the twrp-installer-enchilada-3.2.1-0.zip that you downloaded on your phone
Disconnect your phone from the pc
Reboot twrp back into recovery. You should now be rebooted to the official twrp.
If you had magisk installed, then flash magisk or you will bootloop back to twrp
Click to expand...
Click to collapse
If that's not the issue, you might try using another cable or another port.
Yes those exact steps. And I'm using the factory red cable it came with . I just reinstalled windows 10. So I'll see if that fixed the issue
Update:that didn't fix the issues either.
RootJunky J.R said:
So I rooted my OnePlus 6 through magisk using the command prompt method. And for some odd reason whenever I go to flash the TWRP image it just comes up " the image file is corrupt". I don't know if it's the TWRP download link on there website. But I've tried it on my laptop and another laptop. I keep getting corrupt image file. Anybody know a way to get TWRP without PC or a different method.
Click to expand...
Click to collapse
You CAN NOT flash TWRP from your PC
You must BOOT TWRP. . When you type fastboot devices what does the computer show?
The command is fastboot boot (name of file) but whenever I do that it comes up corrupted. It's an issue with my laptop I guess.
RootJunky J.R said:
The command is fastboot boot (name of file) but whenever I do that it comes up corrupted. It's an issue with my laptop I guess.
Click to expand...
Click to collapse
When you type fastboot devices, what is the return?
lollyjay said:
When you type fastboot devices, what is the return?
Click to expand...
Click to collapse
It shows that my device is attached
I do the steps
Adb devices
Fastboot devices
RootJunky J.R said:
Update that wasn't the issue... I'm sure it's something to do with windows 10.
Click to expand...
Click to collapse
I did all my flashing with Windows 10 no problems
dgunn said:
I did all my flashing with Windows 10 no problems
Click to expand...
Click to collapse
Well then. IDK what my problem is then
RootJunky J.R said:
Well then. IDK what my problem is then
Click to expand...
Click to collapse
Damn that is a real bummer. Are you on 5.1.8?
lollyjay said:
Damn that is a real bummer. Are you on 5.1.8?
Click to expand...
Click to collapse
Yes I am . I'm currently installing Windows 7. So I can deal boot my laptop. I have windows 10 all these problems