Toolkit Rooting Question FAILInvalid Command" - Samsung Galaxy Nexus

I'm confused.... I'm following all the instructions using the toolkit v10.
I was able to unlock the bootloader without an issue, but when it comes to rooting, I'm having problems.
I use option 16 for the build, then option 4 to root. In the fastboot screen, the bottom Fastboot status says FAILInvalid Command as soon as it pulls up, then it goes to "reboot" after the 30 second wait.
It doesn't reboot automatically, so I press the power button to reboot it myself. then it reboots and then goes back into fastboot with the fail invalid command. Then this comes up:
downloading 'boot.img'
FAILED (remote: Invalid Command)
finished. total time: 0.006s
Waiting for device.
I'm at a loss. I feel like last time did this, I had to get the factory image and the boot.img file from somewhere and place them in the folders within the c:/galaxy nexus toolkit folder.
Any help would be greatly appreciated!
Thanks,
Nick

put on your big boy pants and root your phone this way:
http://forum.xda-developers.com/showthread.php?t=1529058

I have tried that... i get a similar message:
sending 'recovery' (5990 KB)
FAILED (remote: Invalid Argument)
finished. total time: 0.006s
then the fastboot status on the phone changes to "download 005d9800"
not sure what to make of that either.

is the cwm/twrp image actually named recovery? and is it in the fastboot.exe directory?
are you typing the command correctly? ( fastboot flash recovery nameofrecovery.img

It's in the same "platform-tools" folder that the fastboot.exe file is in. it's called recovery-clockwork-touch-6.0.2.3-toro.img, so i type fastboot flash recovery recovery-clockwork-touch-6.0.2.3-toro.img and hit enter. That's what made sense to me in reading that post.

waldo22 said:
It's in the same "platform-tools" folder that the fastboot.exe file is in. it's called recovery-clockwork-touch-6.0.2.3-toro.img, so i type fastboot flash recovery recovery-clockwork-touch-6.0.2.3-toro.img and hit enter. That's what made sense to me in reading that post.
Click to expand...
Click to collapse
Yep that's it
Sent from my Galaxy Nexus using Tapatalk 2

I'm guessing you mean that that's the correct way to do it and not, "yep that's you're problem." Any ideas where to go from there?

crazy... I switched to a different computer, and used the most up to date pdanet drivers, and it's going like a champ.

Related

Gaining Root Access - Stuck at sending recovery

I'm stuck trying to flash custom recovery. Keep getting stuck at sending recovery. I get:
"sending 'recovery' (6504 KB)...
FAILED (remote: Invalid Command) finished.
total time: 0.001s"
Phone is already unlocked. I'm on a Verizon Nexus. Didn't have this much trouble with my last Nexus.
what command are you typing?
Zepius said:
what command are you typing?
Click to expand...
Click to collapse
I've tried several different methods. The traditional way which I found via XDA, GalaxyNexusRootNew. It just fails when sending recovery.
fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
type fastboot devices and let me know if it finds anything.
Zepius said:
type fastboot devices and let me know if it finds anything.
Click to expand...
Click to collapse
You mean adb devices? adb devices lists my phone.
fastboot devices doesn't say anything.
no, i meant fastboot devices.
sounds like you're not in fasboot mode.
power off the phone, press and hold vol up, vol down, and power button. once there should see a android on its back with its front open and green text saying start. that is fastboot mode, then type the fasboot command you had tried previously.
Zepius said:
no, i meant fastboot devices.
sounds like you're not in fasboot mode.
power off the phone, press and hold vol up, vol down, and power button. once there should see a android on its back with its front open and green text saying start. that is fastboot mode, then type the fasboot command you had tried previously.
Click to expand...
Click to collapse
0146882A07009009 fastboot
This is what I got.
Now I get:
sending 'recovery' (5140 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.655s
does the phone say its lock status is unlocked?
might try and redownload the file and make sure its where the fastboot executable is (or you can type the full path where the file is)
Zepius said:
does the phone say its lock status is unlocked?
might try and redownload the file and make sure its where the fastboot executable is (or you can type the full path where the file is)
Click to expand...
Click to collapse
Yep. Red font - says "Lock State - UNLOCKED"
try my other suggestion. redownload the file and make sure its in the folder where the fastboot.exe is.
c:\fastboot>fastboot flash recovery openrecovery-toro-2.1.2.img
sending 'recovery' (5400 KB)... OKAY
writing 'recovery'... OKAY
this is what it should look like (i flashed twrp instead of CWm, but you get the idea). the file is in my fastboot folder.
Zepius said:
try my other suggestion. redownload the file and make sure its in the folder where the fastboot.exe is.
Click to expand...
Click to collapse
I'm gonna do that too. I re-locked my bootloader and then re-unlocked it again.
Maybe there was a problem with the unlocking.
CanesDrew said:
I'm gonna do that too. I re-locked my bootloader and then re-unlocked it again.
Maybe there was a problem with the unlocking.
Click to expand...
Click to collapse
i edited my previous post to give you an idea of what you are looking for.
Zepius said:
i edited my previous post to give you an idea of what you are looking for.
Click to expand...
Click to collapse
Same thing. I did notice after I did "adb reboot bootloader". At the Android Screen there was a little blue bar that said "FASTBOOT STATUS - Invalid Command"
Success! Used another computer and used Wug's toolkit. Worked!!
Sent from my rooted Galaxy Nexus using xda premium
Its all about THE U
Sent from my Galaxy Nexus using xda premium
colts187 said:
Its all about THE U
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Everyday. Or as my friends in Memphis would say, Errrday.
Sent from my Galaxy Nexus using xda premium

how to flash pd98img.zip through adb

Anybody know if its poissible to flash the Stock pd98img.zip by using adb shell, i want to return to stock but my volume up key isnt working so is there any way that i can use the adb instead of my volume up key
adilrenzu said:
Anybody know if its poissible to flash the Stock pd98img.zip by using adb shell, i want to return to stock but my volume up key isnt working so is there any way that i can use the adb instead of my volume up key
Click to expand...
Click to collapse
plug the phone in fastboot, you should see fastboot usb in red.
Open a cmd as admin or terminal as root in the pc
type: fastboot oem rebootRUU (you will get a black splash with silver htc)
fastboot flash zip "nameoffile.zip" (no quation marks)
Once it is done (it says OKAY. finished in the CMD session)
fastboot reboot
Make sure that u are in the same folder (in CMD) where the zip file is...This will only be feasible for a RUU...not a rom. It also works for radios and CWM recovery....:good:
glevitan said:
plug the phone in fastboot, you should see fastboot usb in red.
Open a cmd as admin or terminal as root in the pc
type: fastboot oem rebootRUU (you will get a black splash with silver htc)
fastboot flash zip "nameoffile.zip" (no quation marks)
Once it is done (it says OKAY. finished in the CMD session)
fastboot reboot
Make sure that u are in the same folder (in CMD) where the zip file is...This will only be feasible for a RUU...not a rom. It also works for radios and CWM recovery....:good:
Click to expand...
Click to collapse
Hey there, im in this part of the process. Right now is in writing "ZIP"... since around 1 hour. it is normal? how long it will take?
Thank you
fefetron said:
Hey there, im in this part of the process. Right now is in writing "ZIP"... since around 1 hour. it is normal? how long it will take?
Thank you
Click to expand...
Click to collapse
It shouldn´t take that long. Make sure that you are using the oem cable. That USB ports are working fine and there´s no other stuff connected to your USB ports.
glevitan said:
It shouldn´t take that long. Make sure that you are using the oem cable. That USB ports are working fine and there´s no other stuff connected to your USB ports.
Click to expand...
Click to collapse
I only have the mouse in the usb port. im using the HTC cable. i have a htc inspire 4g
fefetron said:
I only have the mouse in the usb port. im using the HTC cable. i have a htc inspire 4g
Click to expand...
Click to collapse
ok, do the following. Eject the sdcard and try again without the sdcard. Report back please. :good:
glevitan said:
ok, do the following. Eject the sdcard and try again without the sdcard. Report back please. :good:
Click to expand...
Click to collapse
Just Waiting for the device.. nothing more
im traying to install new drivers.
i´ll back
glevitan said:
plug the phone in fastboot, you should see fastboot usb in red.
Open a cmd as admin or terminal as root in the pc
type: fastboot oem rebootRUU (you will get a black splash with silver htc)
fastboot flash zip "nameoffile.zip" (no quation marks)
Once it is done (it says OKAY. finished in the CMD session)
fastboot reboot
Make sure that u are in the same folder (in CMD) where the zip file is...This will only be feasible for a RUU...not a rom. It also works for radios and CWM recovery....:good:
Click to expand...
Click to collapse
Many thanks!
I too had this boot problem on a bad flash through the Hack Kit
(my fault by the way). From power on it took 20 mins to get to the first white HTC screen . Then a further 10 mins to start normal boot.
Apart from the LONG boot, everything worked perfectly. Using TermEm I could boot into bootloader and recovery. The rom, IceColdSandwich worked perfectly in every respect but the corrupted boot was doing my head in.
Using your tutorial, I managed to flash the correct bootloader and now all is good.
hboot before was 0.85.2007
hboot after is 0.85.0024
Sorry if this is a long post but I think it is worth it. Here is a log of the fastboot process:
F:\Android\DHD\Bootloader Image\Fastboot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT11BRX11244 device
F:\Android\DHD\Bootloader Image\Fastboot>fastboot oem rebootRUU
... OKAY [ 0.375s]
finished. total time: 0.376s
F:\Android\DHD\Bootloader Image\Fastboot>fastboot flash zip PD98IMG.zip
< waiting for device >
sending 'zip' (227 KB)... OKAY [ 0.056s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,100
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
OKAY [6586.776s]
finished. total time: 6586.834s
F:\Android\DHD\Bootloader Image\Fastboot>fastboot reboot
rebooting...
finished. total time: 8.532s
F:\Android\DHD\Bootloader Image\Fastboot>
I have to say that the timings, because of the LONG boot, are completely wrong, . I was tempted to pull the plug on a number of occasions but I gave myself a talking to and went for a coffee.
The whole process took about 2 hours and I am now the delighted owner of a normal booting DHD.
To anyone who wants to attempt this procedure, the watchword is patience. Whenever you think nothing is happening, DO NOTHING!
The different stages will eventually happen just as laid out as per Glevitan. Good luck with your attempt.
Once again, many thanks.
Edit: Just an afterthought, at one stage Windows had a failed attempt at installing usb drivers that ended up as an 'Unknown Device'. Just ignore it and keep going.
Edit: I just tried again and it worked, nevermind!
Just fyi: if you get an error after flashing the ZIP, just flash it again.
Thanks! This was helpful.
glevitan said:
plug the phone in fastboot, you should see fastboot usb in red.
Open a cmd as admin or terminal as root in the pc
type: fastboot oem rebootRUU (you will get a black splash with silver htc)
fastboot flash zip "nameoffile.zip" (no quation marks)
Once it is done (it says OKAY. finished in the CMD session)
fastboot reboot
Make sure that u are in the same folder (in CMD) where the zip file is...This will only be feasible for a RUU...not a rom. It also works for radios and CWM recovery....:good:
Click to expand...
Click to collapse

[Q] TIFU going from GPE5.1 Back to Sense, Please help :)

So, the instructions are below pulled out of the Back to Sense thread.(http://forum.xda-developers.com/showthread.php?t=2733523) got to the end of what i've pasted no problems......
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Everything went well until the after that... I stuffed up royally.. my failure is below...
PS C:\adb> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.014s
PS C:\adb> fastboot flash recovery TWRP_Recovery_2.8.6.2_M8_CPTB.img
target reported max download size of 1830711296 bytes
sending 'recovery' (16804 KB)...
OKAY [ 1.515s]
writing 'recovery'...
OKAY [ 0.940s]
finished. total time: 2.455s
fastboot boot TWRP_Recovery_2.8.6.2_M8_CPTB.img
I realize i skipped the below steps...
Boot into stock recovery
Factory reset
Reboot into bootloader
It would seem that what i've gone and done is flashed TWRP into the Boot Partition or something? now whenever i boot up, it won't show the fastboot screen, it goes straight to "entering recovery" and sits there forever.... one thing worth noting, i can see the internal storage(well some of it) the device is recognized in windows and then internal storage is 10.5gb free out of 10.6gb, Navigating to the internal directory shows 3 directories: 0, obb, and TWRP. 0 is a neverending folder. every 3rd layer deep click it shows the root directory again...
Help would be very very much appreciated!
cheers!
EDIT: Sorted! It turns out i'm an idiot and wasn't pushing volume down fast enough to get into bootloader. Sorry guys!!!!
Cameltoemcgee said:
It would seem that what i've gone and done is flashed TWRP into the Boot Partition or something? now whenever i boot up, it won't show the fastboot screen, it goes straight to "entering recovery" and sits there forever....
EDIT: Sorted! It turns out i'm an idiot and wasn't pushing volume down fast enough to get into bootloader. Sorry guys!!!!
Click to expand...
Click to collapse
If the bootloader was overwritten, damaged or corrupted, the phone would be bricked, and the screen would not come on at all.
This is the second post on the first page where the OP solved their own issue. You guys are getting good at fixing your own problems.

Install TWRP and then to root.

Hello please can anyone advise me and forgive any wrong terms..
I am trying to push twrp to my lg g4 H815 20g using adb and fastboot but everytime it comes back with
error: cannot load 'twrp.img': No such file or directory
PS C:\Users\Anthony\Desktop\ADB>
i have tried renaming twrp file to various things and changing the command fastboot flash twrp.img or fastboot flash recovery.img
but i keep getting errors of one discription or the other..
I have followed guild after guild but still not made the magic happen..
Bootloader is officially unlocked via LG and twrp for lg g4 downloaded from twrp site.
Been trying for two days to install a recovery so i can also root but having no luck.
please any help or advise would be appreciated..
you must put the "twrp.img" into to your "ADB" folder and then exec this:
Code:
fastboot flash recovery twrp.img
Hi thanks for your help
yes I have the img file in adb/fastboot folder and been doing this and still comes back in cmd as no such file etc..
Tried renaming twrp img file and changing fastboot flash line to match but still no joy..
Tried earlier g4 twrps same outcome it’s as if downloaded recovery’s are corrupt or something as they don’t appear to be being seen..
What is best name for the twrp image or do you leave it as it came downloaded and run the
fastboot flash recovery twrp.img Regardless of what twrp called when downloaded..
Thanks
Have you changed directory to the sdk folder? Or shift + right clicked in folder "open cmd here"?
The command is "fastboot flash *whatever recovery is called in adb folder*"
I ended up changing the name to "twrp3.1.1" or whatever cause it had a hell of a name when downloaded. Just name whatever you want as long as you call it same thing when flashing.
Make sure you also have a copy of it on your SD too because it wont stick and when you reboot to the recovery you then need to reflash the image from in there.
Hi I think it was successful i changed name of twrp on second attempt and it seemed to work..
only problem was when i tried to manually boot into recovery via volume down and power i did something wrong and accidentally reset the dam thing instead of booting into twrp......will have to do it all over again but hopefully i have it sorted..
PS C:\ADB> adb reboot-bootloader
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
PS C:\ADB> fastboot flash recovery twrp.img
error: cannot load 'twrp.img': No such file or directory
PS C:\ADB> fastboot flash recovery twrp-3.1.1-1-g4.img
target reported max download size of 536870912 bytes
sending 'recovery' (33952 KB)...
OKAY [ 0.781s]
writing 'recovery'...
OKAY [ 0.422s]
finished. total time: 1.219s
PS C:\ADB> fastboot reboot
rebooting...
finished. total time: 0.031s
PS C:\ADB>
Hello! I reopen this tread.. I have an issue with flashing twrp, via adb I start into bootloader, but when i put the command to flash it.. <waiting for device>. Why?

Completely Bricked?

All know is I can only boot into Fastboot Mode and Stock Recovery mode, but every way I try to get the flash the stock rom or TWRP won't work.
Device state is unlocked.
Reinstalled Google Drivers.
I will use taimen-opm1.171019.013-factory-6d9954c3
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
fastboot version eac51f2bb6a8-android
Unified Android Toolkit:
Booting TWRP recovery-twrp-3.2.1.0-taimen.img ..
downloading 'boot.img'...
FAILED (remote: unknown command)
finished. total time: 0.007s
Click to expand...
Click to collapse
Cannot flash TWRP
PS C:\adb> fastboot devices
711KPVH0902199 fastboot
PS C:\adb> fastboot flash recovery twrp.img
sending 'recovery' (40960 KB)...
FAILED (remote: Requested download size is more than max allowed)
finished. total time: 0.009s
Click to expand...
Click to collapse
ADB sideload
PS C:\adb> adb sideload C:\taimen\taimen-opm1.171019.013-factory-6d9954c3.zip
loading: 'C:\taimen\taimen-opm1.171019.013-factory-6d9954c3.zip'
* cannot read 'C:\taimen\taimen-opm1.171019.013-factory-6d9954c3.zip' *
Click to expand...
Click to collapse
If I use flash-all.bat:
sending 'bootloader' (36344 KB)...
FAILED (unknown status code)
finished. total time: 343.328s.
Click to expand...
Click to collapse
If I use flash-all command in cmd:
PS C:\Users\tiger\Desktop\tamien> flash-all
error: cannot load 'bootloader-taimen-tmz10n.img'
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.007s
error: cannot load 'radio-taimen-g8998-00122-1708311414.img'
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.007s
W/ ( 9820): Unable to open 'image-taimen-opd1.170816.025.zip': No such file or directory
error: failed to open zip file 'image-taimen-opd1.170816.025.zip': I/O Error
Click to expand...
Click to collapse
Do you have the latest adb downloaded from Google?
Also, there is no recovery partition any longer, it's built in to the boot partition.
You can try the command "fastboot boot TWRP.img" to boot to TWRP.
azntiger said:
All know is I can only boot into Fastboot Mode and Stock Recovery mode, but every way I try to get the flash the stock rom or TWRP won't work. Device state is unlocked.
Unified Android Toolkit:
Cannot flash TWRP
ADB sideload
If I use flash-all.bat:
If I use flash-all command in cmd:
Click to expand...
Click to collapse
First, have you read this? https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Second, are your SDK platform-tools up to date??
Have you taken an OTA?
Your twrp command is wrong like the post after yours stated.
Did you give both bootloader unlock commands?
fastboot flashing unlock
And
fastboot flashing unlock_critical
ilal2ielli said:
Do you have the latest are downloaded from Google?
Also, there is no recovery partition any longer, it's built in to the boot partition.
You can try the command "fastboot boot TWRP.img" to boot to TWRP.
Click to expand...
Click to collapse
Yes. I reinstalled Google Drivers. I'm using taimen-opd1.170816.025-factory-907c4030.
I tried boot twrp.img, but it just hangs during the downloading boot.img.
PS C:\adb> fastboot devices
711KPVH0902199 fastboot
PS C:\adb> fastboot boot twrp.img
downloading 'boot.img'...
Click to expand...
Click to collapse
azntiger said:
Yes. I reinstalled Google Drivers. I'm using taimen-opd1.170816.025-factory-907c4030.
I tried boot twrp.img, but it just hangs during the downloading boot.img.
Click to expand...
Click to collapse
Why are you trying to flash the November build?
Badger50 said:
Why are you trying to flash the November build?
Click to expand...
Click to collapse
8.1 causes my proximity sensor to malfunction. The screen wouldn't turn on back on after a call. Alway-on didn't work because it thought the proximity sensor was blocked.
azntiger said:
8.1 causes my proximity sensor to malfunction. The screen wouldn't turn on back on after a call. Alway-on didn't work because it thought the proximity sensor was blocked.
Click to expand...
Click to collapse
That's a phone app problem. Either uninstall the phone app update, or find the phone app 16.0 on apk mirror. However, if you want to downgrade, look here.
https://www.google.com/amp/s/forum....-2-xl/help/downgrade-8-1-to-8-0-t3726641/amp/
Badger50 said:
That's a phone app problem. Either uninstall the phone app update, or find the phone app 16.0 on apk mirror. However, if you want to downgrade, look here.
https://www.google.com/amp/s/forum....-2-xl/help/downgrade-8-1-to-8-0-t3726641/amp/
Click to expand...
Click to collapse
I'll take a look if I can get my phone working again lol.
Badger50 said:
First, have you read this? https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Second, are your SDK platform-tools up to date??
Have you taken an OTA?
Your twrp command is wrong like the post after yours stated.
Did you give both bootloader unlock commands?
fastboot flashing unlock
And
fastboot flashing unlock_critical
Click to expand...
Click to collapse
SDK is up to date.
Not sure what you mean by "taken" an OTA.
So now I have a device null, but fastboot devices is seen.
"fastboot flashing unlock" hangs, but I imagine that's because no device was found?
PS C:\Users\tiger\Desktop\Pixel> fastboot devices
711KPVH0902199 fastboot
PS C:\Users\tiger\Desktop\Pixel> adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device '(null)' not found
PS C:\Users\tiger\Desktop\Pixel> fastboot flashing unlock
...
Click to expand...
Click to collapse
azntiger said:
I'll take a look if I can get my phone working again lol.
SDK is up to date.
Not sure what you mean by "taken" an OTA.
So now I have a device null, but fastboot devices is seen.
"fastboot flashing unlock" hangs, but I imagine that's because no device was found?
Click to expand...
Click to collapse
You may have to use this to get back on track my friend.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
I'm not entirely sure what the issue is (it could be a couple of things), but here are some issues that I see to help you troubleshoot:
1. Adb commands don't work in bootloader mode, only fastboot commands, which is why your device is visible to fastboot and not adb.
2. The file that you tried to adb sideload was a factory image, not an OTA. Adb sideload can only be used with OTA images. And even if you were using an OTA image, OTA images cannot be used to downgrade to a previous firmware version.
3. The latest version of adb is 1.0.39. You are using an older version. That fact itself doesn't really matter since adb will not help you in this situation, but fastboot will and if your adb is obsolete, I'd be willing to bet that your fastboot is too. Pixel 2 support was added in the October 2017 release of adb and fastboot. If yours is older than that, you're gonna have a bad time.
4. "Unable to open 'image-taimen-opd1.170816.025.zip': No such file or directory." Fastboot can't find your firmware files. Try placing the entire contents of the factory image, including the .zip file listed here, into the same directory as fastboot.exe (based on your post, it seems like the folder you want is C:\adb). Then rerun flash-all.bat. The script is assuming that fastboot.exe and all of the firmware files are in the same folder and if they're not, that could be a problem.
5. You do not have driver issues. The fact that fastboot devices worked means that your drivers/connection are/is working fine.
PS: Get the latest adb and fastboot here: https://developer.android.com/studio/releases/platform-tools.html
UPDATE: I did a Google search for adb/fastboot version eac51f2bb6a8-android. I found a reference to it in a forum post dated mid-2016. There's your problem. Or one of them, anyway. If you do adb --version or fastboot --version on the latest releases, they will tell you that they are version 0.0.1-4500957.
TheSt33v said:
4. "Unable to open 'image-taimen-opd1.170816.025.zip': No such file or directory." Fastboot can't find your firmware files. Try placing the entire contents of the factory image, including the .zip file listed here, into the same directory as fastboot.exe (based on your post, it seems like the folder you want is C:\adb). Then rerun flash-all.bat. The script is assuming that fastboot.exe and all of the firmware files are in the same folder and if they're not, that could be a problem.
Click to expand...
Click to collapse
I updated adb and fastboot:
Android Debug Bridge version 1.0.39
fastboot version 0.0.1-4500957
All of taimen-opm1.171019.013-factory-6d9954c3 & all contents of image-taimen-opm1.171019.013.zip were placed into C:\adb which has the adb and fastboot. After running flash-all.bat, this is what I got:
Code:
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.007s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.395s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
azntiger said:
I updated adb and fastboot:
Android Debug Bridge version 1.0.39
fastboot version 0.0.1-4500957
All of taimen-opm1.171019.013-factory-6d9954c3 & all contents of image-taimen-opm1.171019.013.zip were placed into C:\adb which has the adb and fastboot. After running flash-all.bat, this is what I got:
Click to expand...
Click to collapse
Open up your SDK and look for a file named "platform-tools" that is where all your files should be placed.
Badger50 said:
Open up your SDK and look for a file named "platform-tools" that is where all your files should be placed.
Click to expand...
Click to collapse
All the platform-tools and the stock rom are together in folder.
azntiger said:
All the platform-tools and the stock rom are together in folder.
Click to expand...
Click to collapse
Did you extract the factory image first, or just put the whole zip file in platform-tools?
azntiger said:
I updated adb and fastboot:
Android Debug Bridge version 1.0.39
fastboot version 0.0.1-4500957
All of taimen-opm1.171019.013-factory-6d9954c3 & all contents of image-taimen-opm1.171019.013.zip were placed into C:\adb which has the adb and fastboot. After running flash-all.bat, this is what I got:
Code:
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.007s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.395s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
Click to expand...
Click to collapse
Hmm. Fastboot is definitely having issues communicating with your phone. "Failed to identify current slot" is a bad sign. If I were you, I would try flashing the most recent factory image (not the November 8.0 image you're trying to flash) first just to see if you can get everything up to date again and clear out any mismatched files that may have been flashed during your attempts. Once you manage that, then try to downgrade. If you can, try a different computer too, preferably one with a type C input that you can use the stock USB cable with.
---------- Post added at 04:03 PM ---------- Previous post was at 04:01 PM ----------
Badger50 said:
Did you extract the factory image first, or just put the whole zip file in platform-tools?
Click to expand...
Click to collapse
The fact that he's not getting "not found" errors means that all the expected files are found by fastboot.
The fact that he's not getting "not found" errors means that all the expected files are found by fastboot.[/QUOTE]
Thanks man. I learned something new today :good:
Wonder if his transfer cable. I've seen that cause headaches as well ?
It was definitely an issue between my laptop and my phone. I was able to easily use flash-all.bat on a different computer.
I really appreciate both of your help! I was stressed out.
azntiger said:
It was definitely an issue between my laptop and my phone. I was able to easily use flash-all.bat on a different computer.
I really appreciate both of your help! I was stressed out.
Click to expand...
Click to collapse
Oh nice! Glad you got it figured out. This stuff can be a bit tricky at times. I know I've lost some hair from pulling it out when things didn't go right! ?
azntiger said:
It was definitely an issue between my laptop and my phone. I was able to easily use flash-all.bat on a different computer.
I really appreciate both of your help! I was stressed out.
Click to expand...
Click to collapse
I was on edge just reading this! I would also look into Deuce's script. It can save the 'device can't boot' issue once and for good.
Kudos on not having a faulty device~!

Categories

Resources