Database Info

New to Nexus, stuck in Fastboot! Please Help!

Hey guys,
I'm brand new to the Nexus S but I'm not new to flashing/rooting etc. However I am having an issue here.
I successfully unlocked my bootloader today, and flashed CWM Recovery, rooted, and finally flashed CM7. I wanted to try Netarchy's kernel, so I installed Kernel Manager from the market and tried that way (been wanting to try out that app anyways). Well, I got an error, something about insufficient memory. The error message said I should reboot and try again.
So I rebooted.
Well now I am stuck in fastboot menu with "NO BOOT OR RECOVERY IMG" at the top of the screen.
So, I copied CWM recovery back into my AndroidSDK\Tools folder, and did
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
but I just keep getting
Code:
error: cannot load "recovery-clockwork-3.0.2.4-crespo.img"
I reinstalled drivers and tried again. Same error.
I double checked file name, tried renaming the recovery image file name, made sure it was in the same directory as fastboot.exe. If I do
Code:
fastboot devices
it DOES see my phone. I just can't get the recovery image to flash!
Can someone please help me???

Does your computer show the extensions of the files?
E.G. does fastboot appear as "fastboot" or "fastboot.exe" ?
And I'd recommend using 3.0.2.5 rather than 3.0.2.4. 3.0.2.4 is known to have bugs with it working. Your phone needs to be in bootloader mode in order for this command to work. http://forum.xda-developers.com/showthread.php?t=988686

Originally, just fastboot. But I changed the folder view to not hide known extensions so I could double check an make sure I hadn't named it recovery.img.img or something. Unfortunately that doesn't seem to be the issue.

matt2053 said:
Originally, just fastboot. But I changed the folder view to not hide known extensions so I could double check an make sure I hadn't named it recovery.img.img or something. Unfortunately that doesn't seem to be the issue.
Click to expand...
Click to collapse
Hm. thats where I was going towards. Try fastboot flashing the 3.0.2.5 recovery, its also weird that it says no boot img.
What kind of Nexus S do you have? 9020A, 9020T, 9023?

zephiK said:
Hm. thats where I was going towards. Try fastboot flashing the 3.0.2.5 recovery, its also weird that it says no boot img.
What kind of Nexus S do you have? 9020A, 9020T, 9023?
Click to expand...
Click to collapse
9020T
I think maybe Kernel Manager formatted those partitions, tried to flash the kernel, error, but no rollback or backup.....
Trying your link now.

matt2053 said:
9020T
I think maybe Kernel Manager formatted those partitions, tried to flash the kernel, error, but no rollback or backup.....
Click to expand...
Click to collapse
I personally flash kernels manually. I'm going to upload this bootloader, I couldn't find it on XDA anymore but its a bootloader img that was from 2.3.3. it's the I9020XXKA3 bootloader
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90
(verify its MD5 hash.. if you don't know how, google HashTab)
place the file in /sdk/tools/
assure your phone is in bootloader mode (with android in the back)
fastboot flash bootloader bootloader.img
what happens? BE SURE that your phone is indeed 9020T before flashing this (incase anybody else with another model attempts this)

zephiK said:
I personally flash kernels by myself. I'm going to upload this bootloader, I couldn't find it on XDA anymore but its a bootloader img that was from 2.3.3. it's the I9020XXKA3 bootloader
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90
(verify its MD5 hash.. if you don't know how, google HashTab)
place the file in /sdk/tools/
assure your phone is in bootloader mode (with android in the back)
fastboot flash bootloader bootloader.img
what happens? BE SURE that your phone is indeed 9020T before flashing this (incase anybody else with another model attempts this)
Click to expand...
Click to collapse
I usually flash them myself too. I was just interested in trying out the app because I've used some very cool stuff from the dev (shinzul) in my HTC Evo days.
I got the same error on the CWM 3.0.2.5.
I will try flashing the bootloader now. Thanks for taking the time.

matt2053 said:
I usually flash them myself too. I was just interested in trying out the app because I've used some very cool stuff from the dev (shinzul) in my HTC Evo days.
I got the same error on the CWM 3.0.2.5.
I will try flashing the bootloader now. Thanks for taking the time.
Click to expand...
Click to collapse
I just found it awkward that your phone said:
"NO BOOT OR RECOVERY IMG"
Click to expand...
Click to collapse
Let me know the results.
my bootloader appears as:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020XXKB3
CARRIER INFO - TMB
SERIAL NUMBER - <removed>
LOCK STATE - UNLOCKED
and the navigational stuff
Click to expand...
Click to collapse

Hmmmmm well I got "error: cannot load 'bootloader.img'."
I'm beginning to wonder if the problem is on my PC side, with fastboot or something.

matt2053 said:
Hmmmmm well I got "error: cannot load 'bootloader.img'."
I'm beginning to wonder if the problem is on my PC side, with fastboot or something.
Click to expand...
Click to collapse
you're placing it in /sdk/tools right? The Android SDK has to be matched up with 2.3.X.
Try starting all over. Uninstall drivers for your phone. Redownload the Android SDK.
As a last resort, you can try Odin but I haven't had any experience with it on the Nexus S so I can't help you with that but if you want to try Odin thats your choice.
Part 1 will get you started: http://forum.xda-developers.com/showthread.php?t=895545
It's very possible you have a bad version of the SDK. So try this, if it doesn't work try Odin imo.

zephiK said:
you're placing it in /sdk/tools right? The Android SDK has to be matched up with 2.3.X.
Try starting all over. Uninstall drivers for your phone. Redownload the Android SDK.
As a last resort, you can try Odin but I haven't had any experience with it on the Nexus S so I can't help you with that but if you want to try Odin thats your choice.
Part 1 will get you started: http://forum.xda-developers.com/showthread.php?t=895545
It's very possible you have a bad version of the SDK. So try this, if it doesn't work try Odin imo.
Click to expand...
Click to collapse
yes that was where I placed it.
I'm reinstalling SDK and drivers. I don't think we'll need Odin. I think my fastboot was just wonky. I had installed/moved/reinstalled/uninstalled the SDK several times today trying to get the stoopid drivers installed. PDANet was the only thing that ever worked!

matt2053 said:
yes that was where I placed it.
I'm reinstalling SDK and drivers. I don't think we'll need Odin. I think my fastboot was just wonky. I had installed/moved/reinstalled/uninstalled the SDK several times today trying to get the stoopid drivers installed. PDANet was the only thing that ever worked!
Click to expand...
Click to collapse
if anything... if you have another system, you could try it on that system. you could also try it in another USB socket.
i mean, i dont think its your drivers but it doesnt hurt to see if it thats the problem.. your device was detected.
so your phone is unable to start up (get past google) and not able to get into recovery?

Holy **** I finally got it.
I had to enter the filepath and file. Derp.
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Not Work ^^^^^
Code:
fastboot flash recovery c:\android\tools\recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Work ^^^^^
Whew, I was scared there for a bit!
THANKS for your help dude!!!

matt2053 said:
Holy **** I finally got it.
I had to enter the filepath and file. Derp.
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Not Work ^^^^^
Code:
fastboot flash recovery c:\android\tools\recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Work ^^^^^
Whew, I was scared there for a bit!
THANKS for your help dude!!!
Click to expand...
Click to collapse
... WOW! i thought you knew that.
if you want the first command to work you have to do:
cd C:\android\tools\
fastboot flash recovery recovery.. blah blah blah
Click to expand...
Click to collapse
but congrats it was all you!

Yeah I must have had a brain fart. I obviously did it correctly earlier in the day when I flashed Clockwork originally. I was thinking the environment variable editing I did handled the need for the directory but I guess that's only for the command not the file.
Well, all is good now anyway!
Sent from my Nexus S using XDA App

Trying to update to 4.4.2 via TWRP Flash getting error

I'm new to rooting and android in general. I'm currently running 4.4 rooted with stock I believe. Says ponury kernal in my settings.
I'm trying to flash the update for 4.4.2 via the TWRP install. I get a failed error: error executing updater binary in zip.
I've made sure my zip is the 4.4 to 4.4.2 but still no luck. Any ideas what I can do? Do I need to wipe something before I can put it on there?

On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful

tom1807 said:
On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful
Click to expand...
Click to collapse
The error was : error executing updater binary in zip. I will look into getting back to stock.

matthewordie said:
The error was : error executing updater binary in zip. I will look into getting back to stock.
Click to expand...
Click to collapse
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update

jd1639 said:
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update
Click to expand...
Click to collapse
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.

matthewordie said:
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.
Click to expand...
Click to collapse
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format

jd1639 said:
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format
Click to expand...
Click to collapse
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.

matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.

matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
Flashing the system image won't wipe anything

http://forum.xda-developers.com/showthread.php?p=14
Sent from my Nexus 5 using Tapatalk

Zepius said:
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.
Click to expand...
Click to collapse
Well I really don't know the exact steps involved in "flashing the image". That's what I'm asking.

jd1639 said:
Flashing the system image won't wipe anything
Click to expand...
Click to collapse
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?

matthewordie said:
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?
Click to expand...
Click to collapse
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it

jd1639 said:
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it
Click to expand...
Click to collapse
Ah, I was close I actually did method 1. Yeah I did leave it unlocked since i'm going to root again right away. Thanks

Wiped N5 now NO OS! Have TWRP

Hello,
I meant to factory restore my rooted N5 and on the advanced TWRP option I chose wipe data. Now I have no OS. I'm not finding a guide on how to install the stock 4.4.2 onto my N5 using a Mac. Is there a process that shows how to do that exactly for a Mac?
thx,
Mark

Install windows on your mac using bootcamp or VMware. just use windows 7/8 trial.
Sent from my Nexus 5 using Tapatalk

+1 i think thts your best bet.. :good:
lesp4ul said:
Install windows on your mac using bootcamp or VMware. just use windows 7/8 trial.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse

eodchn said:
+1 i think thts your best bet.. :good:
Click to expand...
Click to collapse
Yes, I have VMWare and Windows 7 installed. But, what is the process to get the stock rom back onto my phone? I've got TWRP and able to get into Bootloader mode.

s1w999 said:
Yes, I have VMWare and Windows 7 installed. But, what is the process to get the stock rom back onto my phone? I've got TWRP and able to get into Bootloader mode.
Click to expand...
Click to collapse
Look in the general section and at the top is the guide you need to get sorted, good luck and dont panic you haven't killed it.

You don't have to do all that just sideload a stock rom onto the phone

lesp4ul said:
Install windows on your mac using bootcamp or VMware. just use windows 7/8 trial.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Lol
Mac is fully supported by Android tools
Sent from my Nexus 5

Jables2915 said:
You don't have to do all that just sideload a stock rom onto the phone
Click to expand...
Click to collapse
Afaik know you can`t sideload a stock image, only flash in fastboot. Correct me if i`am wrong though. OP can sideload a custom rom and from there return to stock or as @Pirateghost said just use the sdk to flash the image straight away.

gee2012 said:
Afaik know you can`t sideload a stock image, only flash in fastboot. Correct me if i`am wrong though. OP can sideload a custom rom and from there return to stock.
Click to expand...
Click to collapse
100% Correct, OP can choose to do it that way or flash stock image in fastboot there's no need to use Windows at all.

Not working
Jables2915 said:
You don't have to do all that just sideload a stock rom onto the phone
Click to expand...
Click to collapse
Well, I have the Nexus Android Toolkit for oneclick root etc. I don't believe I have USB debugging "on" and I have no OS on the phone to set it to "on". The toolkit will not install the Stock rom is downloaded because is says there's a name mismatch. I choose the option to change name etc and install anyway and it just loops with the same mismatch issue.
Really frustrating. How do I download a .zip file of the rom so I can flash it. All I get are .tgz files when I download the stock rom.
Any ideas?

s1w999 said:
Well, I have the Nexus Android Toolkit for oneclick root etc. I don't believe I have USB debugging "on" and I have no OS on the phone to set it to "on". The toolkit will not install the Stock rom is downloaded because is says there's a name mismatch. I choose the option to change name etc and install anyway and it just loops with the same mismatch issue.
Really frustrating. How do I download a .zip file of the rom so I can flash it. All I get are .tgz files when I download the stock rom.
Any ideas?
Click to expand...
Click to collapse
Just put your faith in toolkits, why don`t you post your question in the toolkits thread. Let them clean up the mess Sorry if i sound a wee harsh but i HATE toolkits, they cause more problems for uneducated users than they do good.

gee2012 said:
Afaik know you can`t sideload a stock image, only flash in fastboot. Correct me if i`am wrong though. OP can sideload a custom rom and from there return to stock or as @Pirateghost said just use the sdk to flash the image straight away.
Click to expand...
Click to collapse
there are stock roms, zipped, floating around xda now. those can be pushed to recovery and flashed.

simms22 said:
there are stock roms, zipped, floating around xda now. those can be pushed to recovery and flashed.
Click to expand...
Click to collapse
Yes i know, but OP wanted to flash back to stock and the android-sdk supports Mac computers.

gee2012 said:
Yes i know, but OP wanted to flash back to stock and the android-sdk supports Mac computers.
Click to expand...
Click to collapse
ah, i missed that :angel:

simms22 said:
there are stock roms, zipped, floating around xda now. those can be pushed to recovery and flashed.
Click to expand...
Click to collapse
I'm downloading a zip now to push/flash. It's a stock rom. Just hoping it works. Next option is I'm glad to hire someone to remote in and fix it. Let me know if you're interested.
thx

s1w999 said:
I'm downloading a zip now to push/flash. It's a stock rom. Just hoping it works. Next option is I'm glad to hire someone to remote in and fix it. Let me know if you're interested.
thx
Click to expand...
Click to collapse
Here is a tutorial for how to setup adb on Mac http://www.youtube.com/watch?v=V0MyTvgfO7s, and here is a how to use it http://forum.xda-developers.com/showthread.php?t=1917237 and restore to stock .

gee2012 said:
Here is a tutorial for how to setup adb on Mac http://www.youtube.com/watch?v=V0MyTvgfO7s, and here is a how to use it http://forum.xda-developers.com/showthread.php?t=1917237 and restore to stock .
Click to expand...
Click to collapse
Excellent, I'm headed there right now.
Thank you!

s1w999 said:
Excellent, I'm headed there right now.
Thank you!
Click to expand...
Click to collapse
OK, got that set up and ./fastboot devices shows my device serial #.
Now, as long as my USB debugging is "on" (I have no way to toggle that since I have no OS, only recovery. Does the fastboot devices command working verify that USB debugging is "on"?
Now to find instructions on how what the flash commands are.
ty

s1w999 said:
OK, got that set up and ./fastboot devices shows my device serial #.
Now, as long as my USB debugging is "on" (I have no way to toggle that since I have no OS, only recovery. Does the fastboot devices command working verify that USB debugging is "on"?
Now to find instructions on how what the flash commands are.
ty
Click to expand...
Click to collapse
Download the factory image and extract with 7-zip and find a Mac flash.all command in the fastboot folder which you can select i guess. Haven`t had a Mac ever so no xperience. Make sure you have the following img files :radio, boot, bootloader, system.img zip, cache and userdata placed in the fastboot folder.
Look here for a tutorial http://au.ibtimes.com/articles/526920/20131203/flash-factory-image-nexus-complete-stock-return.htm.

gee2012 said:
Download the factory image and extract with 7-zip and find a Mac flash.all command in the fastboot folder which you can select i guess. Haven`t had a Mac ever so no xperience. Make sure you have the following img files :radio, boot, bootloader, system.img zip, cache and userdata placed in the fastboot folder.
Look here for a tutorial http://au.ibtimes.com/articles/526920/20131203/flash-factory-image-nexus-complete-stock-return.htm.
Click to expand...
Click to collapse
Well, I've got everything in place, ./fastboot devices sees my N5 but the flash command doesn't do anything when executed.
Any ideas?
Here's what terminal shows:
Marks-Air:android tools Mark$ ./fastboot devices
0591a238002ead35 fastboot
Marks-Air:android tools Mark$ ./flash-all.sh
./flash-all.sh: line 17: fastboot: command not found
./flash-all.sh: line 18: fastboot: command not found
./flash-all.sh: line 20: fastboot: command not found
./flash-all.sh: line 21: fastboot: command not found
./flash-all.sh: line 23: fastboot: command not found
Marks-Air:android tools Mark$

[Help] Trying to flash factory image

I was running the latest Beta version, DP3 ut I was having all sorts of issues. Went to opt out of beta program, but did not receive an OTA for over a week, so I decided to revert back to 7.1.2 manually. I went through the whole process, unlocked my bootloader, flashed the bootloader.img file, flashed the radios, but when I got to flashing the factory image zip file, I'm getting an Error. Falied to load [name of file]. Not Enough Space.
What could be wrong here? How can I get the factory image to flash? Any help would be appreciated.

NickPorter said:
I was running the latest Beta version, DP3 ut I was having all sorts of issues. Went to opt out of beta program, but did not receive an OTA for over a week, so I decided to revert back to 7.1.2 manually. I went through the whole process, unlocked my bootloader, flashed the bootloader.img file, flashed the radios, but when I got to flashing the factory image zip file, I'm getting an Error. Falied to load [name of file]. Not Enough Space.
What could be wrong here? How can I get the factory image to flash? Any help would be appreciated.
Click to expand...
Click to collapse
Now, relock the bootloader, unlock it again.
Download full 7.12 image
Unzip to where Android SDK locates
Run fastboot flash-all
Wait to end

bush911 said:
Now, relock the bootloader, unlock it again.
Download full 7.12 image
Unzip to where Android SDK locates
Run fastboot flash-all
Wait to end
Click to expand...
Click to collapse
Is this something I would be able to do from a command prompt? That's what I have been doing. I am able to access fastboot, i.e. I can [fastboot reboot-bootloader] and it works on my device. Thanks.

Damn, you shouldn't relock the bootloader. ??
You don't even need to opt in/out, just flash all
Sent from my Pixel using XDA-Developers Legacy app

piperx said:
Damn, you shouldn't relock the bootloader. ?
You don't even need to opt in/out, just flash all
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
I just attempted the flash-all method, everything seemed to go smoothly but, once again, when it came to flashing the system image, Error: not enough space...

NickPorter said:
I just attempted the flash-all method, everything seemed to go smoothly but, once again, when it came to flashing the system image, Error: not enough space...
Click to expand...
Click to collapse
You are using the wrong version of fastboot. Get it from google.
https://developer.android.com/studio/releases/platform-tools.html
And yea, NEVER relock the bootloader unless you are about to put it in a box and send it in for warranty. That is horrible advice.

TonikJDK said:
You are using the wrong version of fastboot. Get it from google.
https://developer.android.com/studio/releases/platform-tools.html
And yea, NEVER relock the bootloader unless you are about to put it in a box and send it in for warranty. That is horrible advice.
Click to expand...
Click to collapse
I'm not familiar with Android SDK much at all, I have it installed. Where do I begin? Any help would be great.

I don't know about windows, but in linux you don't need android sdk, or driver's, it just works, someone that uses that other operating system will chime in
Sent from my Pixel using XDA-Developers Legacy app

Does anyone have a way I can back out of this process at the very least? My bootloader is unlocked and bootloader.img and radios have been flashed to my device. Since I cannot flash the system image, I know the phone will not boot if I leave the bootloader menu.

cannot flash Bootloader on unlocked Pixel 2

I have a Google version Pixel 2 and have unlocked the bootloader (unlocked/relocked multiple times) and cannot flash any bootloader. I have tried flashing the "production" BL and the Dev Preview BL. I get the same error each time.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38728 KB)...
OKAY [ 0.110s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.125s
I have tried using the fastboot flashing unlock and fastboot flashing unlock_critical commands. I have relocked the BL then booted into the OS and used ADB to reboot to the BL, I still get the same error. I have tried changing the active slot to with no change.. I have tried the google version of platform tools, minimal adb, and another adb version I had from previous phones. I have downloaded the latest drivers from google no change.. I can flash and format other partitions, just not the BL (although I haven't tried format/erase bootloader, and I don't plan to)
I have tried different USB C cables, Google OEM, Samsung OEM, AUKEY .. different USB ports, different computers (although both with Windows 10 64bit).
Any suggestions?

lazarus2297 said:
I have a Google version Pixel 2 and have unlocked the bootloader (unlocked/relocked multiple times) and cannot flash any bootloader. I have tried flashing the "production" BL and the Dev Preview BL. I get the same error each time.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38728 KB)...
OKAY [ 0.110s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.125s
I have tried using the fastboot flashing unlock and fastboot flashing unlock_critical commands. I have relocked the BL then booted into the OS and used ADB to reboot to the BL, I still get the same error. I have tried changing the active slot to with no change.. I have tried the google version of platform tools, minimal adb, and another adb version I had from previous phones. I have downloaded the latest drivers from google no change.. I can flash and format other partitions, just not the BL (although I haven't tried format/erase bootloader, and I don't plan to)
I have tried different USB C cables, Google OEM, Samsung OEM, AUKEY .. different USB ports, different computers (although both with Windows 10 64bit).
Any suggestions?
Click to expand...
Click to collapse
Your not the only one there are others that have had similar issues, though i don't know the fix.
There is a script somewhere on another thread that might help. I will link.
---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------
Hey you go.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Hopefully something in that will help

Just to be clear, are you using the latest fastboot? That's often an issue.
Some have had trouble with computers with usb-c ports. Have you tried a computer with usb-a and, of course, a usb-a to usb-c cable.

razrlover said:
Your not the only one there are others that have had similar issues, though i don't know the fix.
There is a script somewhere on another thread that might help. I will link.
---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------
Hey you go.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Hopefully something in that will help
Click to expand...
Click to collapse
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
foosion said:
Just to be clear, are you using the latest fastboot? That's often an issue.
Some have had trouble with computers with usb-c ports. Have you tried a computer with usb-a and, of course, a usb-a to usb-c cable.
Click to expand...
Click to collapse
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..

lazarus2297 said:
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
Click to expand...
Click to collapse
I'm not sure if this question will help, are you flashing the bootloader into the correct slot? I had issue early on with this and found that I needed to direct the flash to the correct slot. Just a thought

phonefreedom said:
I'm not sure if this question will help, are you flashing the bootloader into the correct slot? I had issue early on with this and found that I needed to direct the flash to the correct slot. Just a thought
Click to expand...
Click to collapse
Not exactly sure but I have tried changing the active slot to a or b.
I am using the command Fastboot flash bootloader "filename.img" (no quotations) I don't know how I would tell it to flash a specific slot other than whatever is the current active slot..

lazarus2297 said:
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
Click to expand...
Click to collapse
lazarus2297 said:
Not exactly sure but I have tried changing the active slot to a or b.
I am using the command Fastboot flash bootloader "filename.img" (no quotations) I don't know how I would tell it to flash a specific slot other than whatever is the current active slot..
Click to expand...
Click to collapse
+Natahranta had shared the following with me and I hope it helps in your case...
"Download factory image from Google, unpack it, insidebis another zip, there is boot.img file
Flash it to both slots A and B. It must be the same version/update your phone was on.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
If you're not sure which exactly stock rom build your phone is on, use the flash_all.bat to flash the whole image on your phone, to be sure you have no mismatch between system and boot. Just remove "-w" from the bat file so it doesn't erase your user data"

So i got it working here is what I did..
I used the factory image to flash back 100% stock and relocked the bootloader, I then signed my device up for the Dev Preview, and surprisingly I got the notification to install DP pretty quickly. After DP installed I rebooted into the bootloader and noticed that my bootloader version had changed to the DP BL version. I then unlocked with the standard Fastboot Flashing Unlock command and unlocked the bootloader. After the phone rebooted I shut it down and booted into the BL and flashed the stock BL (a downgrade) it was successful, so i flashed the DP BL version and it was successful as well. Rebooted normally into the OS and all is well.
Hopefully this will help anyone else having the same problem.

lazarus2297 said:
I have relocked the BL then booted into the OS
Click to expand...
Click to collapse
I don't have any suggestions for your issue. But don't relock it, ever. You are playing with fire, if it goes bad and it's locked you are done.

lazarus2297 said:
So i got it working here is what I did..
I used the factory image to flash back 100% stock and relocked the bootloader, I then signed my device up for the Dev Preview, and surprisingly I got the notification to install DP pretty quickly. After DP installed I rebooted into the bootloader and noticed that my bootloader version had changed to the DP BL version. I then unlocked with the standard Fastboot Flashing Unlock command and unlocked the bootloader. After the phone rebooted I shut it down and booted into the BL and flashed the stock BL (a downgrade) it was successful, so i flashed the DP BL version and it was successful as well. Rebooted normally into the OS and all is well.
Hopefully this will help anyone else having the same problem.
Click to expand...
Click to collapse
I had this problem and created a thread about it a month ago: https://forum.xda-developers.com/pixel-2/help/failed-remote-command-flash-error-t3701929. A couple other people in that thread are now also reporting the problem.
No one seemed to know what the " FAILED (remote: Command Flash Error)" means. I never figured it out.
At the time of the November update, however, I was able to sideload OTA images with adb without problem. I assume that the OTA method also updates the bootloader, like the Dev Preview did for you. I couldn't tell with the November update, though, because it had the same version of the bootloader in it as the one that shipped with the phone.
So I'm wondering if simply sideloading the current December OTA image with adb would accomplish the same thing you did, without having to lock the bootloader, unlock it again, and go through the pain of wiping the device. I wonder if there was just something weird about the original version of the bootloader. Weirdness like this was discussed early on with the Pixel 2 in this XDA article: https://www.xda-developers.com/pixel-2-failing-flash-factory-images/ If I'm right, then once one sideloads the December OTA image and gets a new bootloader, there may not be an issue flashing bootloaders with fastboot in the future. I assume that the Dev Preview also used the OTA method to update the device.
In other words, I'm wondering if the step of unlocking and relocking the bootloader was not necessary. You just had to do it to get the Developer Preview (right?).
Just guessing here. I haven't had time yet to try this.

Okay, I tried my idea above and I was correct. Simplying sideloading the December OTA image updates the bootloader. After that the problem is solved. I can successfully flash the bootloader .img file directly (from the factory image zip) using fastboot. So I assume going forward there should not be any problems flashing factory images, instead of sideloading OTA images.
This solution also avoids having to lock and unlock the bootloader and wipe the whole device in the process.

cb474 said:
Simplying sideloading the December OTA image updates the bootloader.
Click to expand...
Click to collapse
My problem is that I have TWRP installed and it won't sideload nor flash the OTA file. I am trying to figure out how to flash the factory recovery. Unlike the factory images of before, there is no obvious recovery image in the zip.
-----------
Nevermind. I figured out that recovery is part of boot now. I flashed the factory boot and flashing OTA now.

snovvman said:
My problem is that I have TWRP installed and it won't sideload nor flash the OTA file. I am trying to figure out how to flash the factory recovery. Unlike the factory images of before, there is no obvious recovery image in the zip.
Click to expand...
Click to collapse
I'm not really sure how to solve that problem. Perhaps you should ask in the TWRP thread. I thought that when you install TWRP it backs up the recovery and has a way to restore it. But I could be wrong about that. You're correct that the recovery image does not seem to be included in the factory image zip like it used to be. I have seen other people mention that.

cb474 said:
I'm not really sure how to solve that problem. Perhaps you should ask in the TWRP thread. I thought that when you install TWRP it backs up the recovery and has a way to restore it. But I could be wrong about that. You're correct that the recovery image does not seem to be included in the factory image zip like it used to be. I have seen other people mention that.
Click to expand...
Click to collapse
Thanks for replying. Silly me, I was thinking the old way of doing business, where the recovery had its own image/partition. I figured out that recovery is part of boot, so I flashed boot and got the factory recovery back. I'm on 8.1 now.

snovvman said:
Thanks for replying. Silly me, I was thinking the old way of doing business, where the recovery had its own image/partition. I figured out that recovery is part of boot, so I flashed boot and got the factory recovery back. I'm on 8.1 now.
Click to expand...
Click to collapse
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.

cb474 said:
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
Click to expand...
Click to collapse
So you know, TWRP for the first gen Pixels never left beta. They worked well enough... For Pixel 2s, I use the current beta for backups and they are handy for certain things. For now I am booting to TWRP to flash Magisk. For me, it is more convenient than patching.

cb474 said:
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php

kendong2 said:
https://forum.xda-developers.com/showpost.php
Click to expand...
Click to collapse
That link leads to nothing.
---------- Post added at 01:13 AM ---------- Previous post was at 01:11 AM ----------
snovvman said:
So you know, TWRP for the first gen Pixels never left beta. They worked well enough... For Pixel 2s, I use the current beta for backups and they are handy for certain things. For now I am booting to TWRP to flash Magisk. For me, it is more convenient than patching.
Click to expand...
Click to collapse
Yeah, I saw that. I'm just hoping with what was learned from the original Pixel and given that supposedly most phones will eventually use the A/B partition scheme that maybe TWRP will advance further on the Pixel 2. I really miss nandroid backups. I miss LineageOS too. Everything was so much simpler on my old Nexus 4. And I wasn't constantly feeling like I was going to brick my device every time I tried to do something.

cb474 said:
That link leads to nothing.
Click to expand...
Click to collapse
Sorry, did that on the phone. Was supposed to go here: https://forum.xda-developers.com/showpost.php?p=74704694&postcount=155
TWRP 3.2.0.0 final release (as I understand it) has been announced a few days ago. Don't know why the thread title still says beta.

This is freaking weird. Anyway, followed post #11 to sideload DEC OTA zip in stock recovery, and now finally I have a bootloader that is 0066 on both slot a and b. Thanked @cb474 !