Related
hi all,
just flashed radio 12.41.60.19_26.06.04.14_M in order to flash Android revolution HD using below method:
- Download the zip file in this post and extract it to a folder on your computer
- Copy your "radio.img" into this folder
- Reboot your phone into bootloader mode (poweroff and then Volume- + Power button)
- Select fastboot
- Connect your phone to the computer
- Open "Start here.bat" (don't worry, you can check that it only contains a link to command prompt)
- While in the command prompt issue the following commands:
- "adb reboot bootloader"
- "fastboot flash radio radio.img"
- "fastboot reboot"
- Your phone should now be rebooting as normal, with a newly flashed radio
Click to expand...
Click to collapse
in the CMD there are these lines as result:
C:\Users\...\Desktop\Radio flash>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\...\Desktop\Radio flash>fastboot flash radio radio.img
sending 'radio' (24832 KB)... OKAY [ 4.287s]
writing 'radio'... OKAY [ 23.686s]
finished. total time: 27.974s
C:\Users\...\Desktop\Radio flash>fastboot reboot
rebooting...
finished. total time: 0.151s
Click to expand...
Click to collapse
Also on bootloader mode desired radio number mentioned. According to the red text; was the flashing successful? what' wrong with it?
-----------
I downloaded Android SDK zip file and extracted it then copy radio.img into 'tools' folder. When I try to run 'fastboot flash radio radio.img' it returned error that 'AdbWinApi.dll' is missing. it's the reason I was forced to use above method for flashing radio instead. should I copy 'AdbWinApi.dll' manually to 'C:\sdk\tools' ? (i.e. from EasyS-OFF.zip package) anyone should copy it manually? Why it isn't there by default?
many Thanks in advance
writing 'radio'... OKAY [ 23.686s]
finished. total time: 27.974s
Click to expand...
Click to collapse
seems successful flashed. and yes you need to put AdbWinApi.dll in the same folder with adb.exe or just copy them to x:\windows\system32. then you can directly run adb in cmd.
187j3x1 said:
seems successful flashed. and yes you need to put AdbWinApi.dll in the same folder with adb.exe or just copy them to x:\windows\system32. then you can directly run adb in cmd.
Click to expand...
Click to collapse
Thanks a lot
I am new to android and this is my new first android.
I saw postings yesterday says OTA 4.0.2 rolled out, and people got it already and there are manual way to get it, so I decided try to work on it. I followed the guide how to unlock bootloader and how to root, the first steps went through, but I can get through the last steps because it isays 'waiting for device', i tried everything. somehow I see the bootloader is unlocked.
I installed the stripped 4.0.2 update from here . I used odin mode. now my battery is dropping 1% every few minutes.
I want to flash restore stock image see if I can fix the problem. I trie flash it with odin, but oding crashed.
can anybody help?
Are you running Linux??
Edit:
From Windows or Linux (only tested by myself of Debian Linux) with fastboot in your PATH:
Reboot into bootloader (adb reboot bootloader)
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
windows.
USB driver is installed when phone is normal mode. but in orin the usb driver does not show.
Moved. Please don't post in the wrong forums.
this is GSM version.
where do you get the image files? also why I can't do in orin?
is there a simple way to flash the factory image directory or any gui tool to do it?
Files are here: http://code.google.com/android/nexus/images.html
Make sure to pick the right one: yakju is GSM and mysid is CDMA
Download the tgz file and extract it (might need winrar on windows IDK)
All the Radio,Bootloader,Recovery and system files are included. The only way I know how to flash these files is fastboot, which imo is a safer way than odin - though I have not really used odin before.
can you explain how to use fastboot. I tried vol-up+down+power, it boot into fastboot, I supose it is, on bottom, it says 'unlocked'. what should I do next?
I am really new to this. I don't want to mess with me device like putting custom rom or stuff. I just want keep it original, it looks better that way. I do not want to add any fancy stuff to it unless they are really good. I used to do tweaks with windows mobile, they had better gui tools to work around make things easier.
citrix80 said:
can you explain how to use fastboot. I tried vol-up+down+power, it boot into fastboot, I supose it is, on bottom, it says 'unlocked'. what should I do next?
I am really new to this. I don't want to mess with me device like putting custom rom or stuff. I just want keep it original, it looks better that way. I do not want to add any fancy stuff to it unless they are really good. I used to do tweaks with windows mobile, they had better gui tools to work around make things easier.
Click to expand...
Click to collapse
You need the android sdk installed on your computer. Read this guide:
http://www.xda-developers.com/android/adb-easy-tutorial/
There are also a handful of threads in this very forum answering your same question. A few of which I have given step by step guides myself. Do a quick search.
I downloaded file from
http://groups.google.com/group/android-building/msg/2cd2b16ed56a7e84
and used fastboot, all steps worked out.
here is the log
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-toro-primekj1
0.img
error: cannot load 'bootloader-toro-primekj10.img'
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-maguro-primek
j10.img
error: cannot load 'bootloader-maguro-primekj10.img'
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-maguro-primek
k15.img
sending 'bootloader' (2308 KB)... OKAY [ 0.296s]
writing 'bootloader'... OKAY [ 0.604s]
finished. total time: 0.900s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.007s]
finished. total time: 0.007s
C:\android-sdk\platform-tools>fastboot flash radio radio-maguro-i9250xxkk6.img
sending 'radio' (12288 KB)... OKAY [ 1.545s]
writing 'radio'... OKAY [ 2.375s]
finished. total time: 3.920s
C:\android-sdk\platform-tools> fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.007s]
finished. total time: 0.007s
C:\android-sdk\platform-tools> fastboot update image-yakju-icl53f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEKK15
Baseband Version.....: I9250XXKK6
Serial Number........: 0146882D0601C00A
--------------------------------------------
checking product... OKAY [ 0.007s]
checking version-bootloader... OKAY [ 0.007s]
checking version-baseband... OKAY [ 0.008s]
sending 'boot' (4074 KB)... OKAY [ 0.517s]
writing 'boot'... OKAY [ 0.492s]
sending 'recovery' (4406 KB)... OKAY [ 0.562s]
writing 'recovery'... OKAY [ 0.789s]
sending 'system' (317594 KB)... OKAY [ 39.809s]
writing 'system'... OKAY [ 36.250s]
rebooting...
finished. total time: 78.476s
C:\android-sdk\platform-tools>
the phone reboot automatically after the last step.
the battery is still dropping.
is there a way to reset to 4.0.1? I am not sure what is causing the problem.
I really need someone to help me...Please...im on the verge of suicide here
i unlocked and rooted, dl'd cwm.
i dl'd the SDK package (i dont have platform-tools, i have tools)
i put the cwm image, and the tgz files on the root directory (there no /sdcard)
i turn on usb debugging
i load bootloader
i launch cwm recovery
i navigate to the sdk folder (cd c:/ > cd sdk > cd tools) then type fastboot -w update image-yakju-itl41f.zip and get an invalid command error ..that didnt work so i copied the tgz and cwm file to the folder which contains the adb stuff and try again..same result
PLEASE HELP...i know im an annoying **** n00b thats wasting youre time but ive been at this since 9am PLEASE
You dont put the files on your phone. They go in the same folder on your computer as fastboot.exe
trilogee said:
I really need someone to help me...Please...im on the verge of suicide here
i unlocked and rooted, dl'd cwm.
i dl'd the SDK package (i dont have platform-tools, i have tools)
i put the cwm image, and the tgz files on the root directory (there no /sdcard)
i turn on usb debugging
i load bootloader
i launch cwm recovery
i navigate to the sdk folder (cd c:/ > cd sdk > cd tools) then type fastboot -w update image-yakju-itl41f.zip and get an invalid command error ..that didnt work so i copied the tgz and cwm file to the folder which contains the adb stuff and try again..same result
PLEASE HELP...i know im an annoying **** n00b thats wasting youre time but ive been at this since 9am PLEASE
Click to expand...
Click to collapse
put files in ur tools folder inside sdk and you fastboot -w update image-yakju-itl41f.zip and get an invalid command error ,,,should of been ,,, fastboot flash -w
oh god didnt realize i got any replies.
so ive gotten past that part now i have a more frustrating problem...installed platforms-tools from the sdk manager, that enable me to get this:
c:\sdk\platform-tools>fastboot -w update image-yakju-icl53f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
< waiting for device >
but when i open the image zip the boot recover and system are there.
the waiting for devices deal, in device manager Android Phone is listed with sub Android ADB interface...driver is installed and device is recognized...why does it still say waiting for device...thank you guys so much.
If I get this working today I promise I will make a small donation to both xda and those that help me.
you need open the zip then extra the tar inside it with 7 zip, then copy all 4 extracted file into sdk folder, or same folder with fastboot. then run fastboot. you can use my output in page 1. type exact same thing.
trilogee
How sure are you that the phone is in bootloader mode at the time of flashing? Try executing fastboot devices first to confirm that fastboot can see the phone...Then what the OP has suggested above or do what you were doing.
Hey I think I explained this in another post, not sure where, but fastboot devices initiates a blank command line. Doesn't show anything...which is odd though because I downloaded the right drivers from Samsung, it's recognized on my computer and it worked with ODIN (although updating through odin actually bricked me and forced me to restore)
trilogee said:
Hey I think I explained this in another post, not sure where, but fastboot devices initiates a blank command line. Doesn't show anything...which is odd though because I downloaded the right drivers from Samsung, it's recognized on my computer and it worked with ODIN (although updating through odin actually bricked me and forced me to restore)
Click to expand...
Click to collapse
If fastboot is showing a blank command line, then it means that it can't see your phone. Anything done after that is not going to work. It could then be one of two things, i.e. either your setup is not correct or your phone is not in bootloader mode. Can adb see the phone normally from your PC, i.e. can it see it when you call 'adb devices' or can you see the logcat output?
With the former, I can suggest that you check if the installation is correctly done? As with the latter, I tend to get adb to reboot the phone in bootloader by issuing a 'adb reboot bootloader' and is far quicker than the button-press option.
did you install sdk and driver? when your phone in normal mode, plug in usb to pc, in device manager, you see android driver?
I tried again. whe I get here
C:\android-sdk\platform-tools>fastboot -w update image-yakju-icl53f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
but the files are actually in the zip file.
the process still finished.
did it skip those files?
I think that has something to do with the .sig verification settings
..same thing happened to me but image flashed fine and everything seems to be running smoothly. Crazy how I struggled with this so much at first its actually an extremely simple process.
Sent from my Galaxy Nexus using XDA App
I am so frustrated. I tried rooting the kindle last week and it went into an endless loop of turning on and off. So I ordered a factory cable and when I plugged it in, it stayed on and fastboot recognized the device.
I tried a few commands and now it's turning on and off again! I can no longer get commands to read the device through fastboot.
what the hell do I do?
EDIT: Sorry I forgot to check off "this thread is a question"
Ok so if I leave the tablet unplugged for a while and replug it, I can send a command and have it go through before the tablet resets again.
But I don't know how to get it to stay in fastboot mode, and I don't know what to do once i'm actually IN fastboot mode (I dont have TWRP or whatever installed).
Any help is appreciated
EDIT: I tried this command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot -i 0x1949 boot c:\twrp-fire-2.1.0.img
creating boot image...
creating boot image - 10240 bytes
< waiting for device >
downloading 'boot.img'...
FAILED (command write failed (No such file or directory))
finished. total time: 0.005s
Hmmm did you try the kfu or the kindle fire unbrick utility?
Step-by-step
1) Make sure you have some charge left in your bricked Kindle. (one of my mistakes
2) Download "Kindle Fire Utility" or other utility that has the fastboot.exe command available.
3) Download twrp-blaze-2.0.0RC0.img (just google it)
4) Without connecting anything, run the command:
fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.img
5) Connect the factory cable to your Kindle Fire
6) Connect the factory cable to you PC
7) Wait about 10 seconds.
8) DONE!!!!
all these steps above taken from http://forum.xda-developers.com/showthread.php?p=25113108&posted=1#post25113108
the OP deserves the credit if this works for you
You're doing it wrong. Unlike TWRP 2.0.0RC0, 2.1.0 is not supposed to be loaded into boot and your system is probably panicking. You need a bootloader first.
First you need a bootloader with recovery selection. There are several to choose from at this point.
I would recommend FIREFIREFIRE 1.3 or 1.2
Download one of them and extract the bin somewhere. Lets say c:\firebuild\
Next we need a recovery partition, you already have that in the twrp-fire-2.1.0.img, so you should be set. Copy that to c:\firebuild\ as well.
Now, lets make sure you have the andriod sdk in your path. This way you don't have to be in the C:\Program Files (x86)\Android\android-sdk\platform-tools folder to run commands and your images can be elsewhere.
1. right click on computer and select properties.
2. click on advanced settings on the left of the window.
3. click on environment variables at the bottom right of the window.
4. in the system variables section scroll down until you find path, highlight it, and select edit.
5. paste the following at the end of the line.
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
For example, my path is:
Code:
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;;C:\Program Files\Lucidlogix Technologies\VIRTU;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
Now that your path is set, lets go into the command prompt.
First lets change the directory to c:\firebuild\ :
Code:
cd c:\firebuild
In this folder we should have u-boot.bin and twrp-fire-2.1.0.img.
First lets load your bootloader.
Code:
fastboot -i 0x1949 flash bootloader u-boot.bin
and start your device.
I would recommend rebooting after flashing this, so run
Code:
fastboot reboot
if it does not reboot on its own.
Now lets run
Code:
fastboot flash recovery twrp-fire-2.1.0.img
Note: Because we have the bootloader now the -i 0x1949 is no longer needed.
After running the above, the kindle should automatically start into recovery.
From here you will be able to mount it as an external drive and copy over any rom you would like to use.
Pick something from here Kindle Fire Development *FULL LIST* - 17.04.2012 - under the Custom / Stock Roms section.
three-p-o said:
You're doing it wrong. Unlike TWRP 2.0.0RC0, 2.1.0 is not supposed to be loaded into boot and your system is probably panicking. You need a bootloader first.
First you need a bootloader with recovery selection. There are several to choose from at this point.
I would recommend FIREFIREFIRE 1.3 or 1.2
Download one of them and extract the bin somewhere. Lets say c:\firebuild\
Next we need a recovery partition, you already have that in the twrp-fire-2.1.0.img, so you should be set. Copy that to c:\firebuild\ as well.
Now, lets make sure you have the andriod sdk in your path. This way you don't have to be in the C:\Program Files (x86)\Android\android-sdk\platform-tools folder to run commands and your images can be elsewhere.
1. right click on computer and select properties.
2. click on advanced settings on the left of the window.
3. click on environment variables at the bottom right of the window.
4. in the system variables section scroll down until you find path, highlight it, and select edit.
5. paste the following at the end of the line.
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
For example, my path is:
Code:
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;;C:\Program Files\Lucidlogix Technologies\VIRTU;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
Now that your path is set, lets go into the command prompt.
First lets change the directory to c:\firebuild\ :
Code:
cd c:\firebuild
In this folder we should have u-boot.bin and twrp-fire-2.1.0.img.
First lets load your bootloader.
Code:
fastboot -i 0x1949 flash bootloader u-boot.bin
and start your device.
I would recommend rebooting after flashing this, so run
Code:
fastboot reboot
if it does not reboot on its own.
Now lets run
Code:
fastboot flash recovery twrp-fire-2.1.0.img
Note: Because we have the bootloader now the -i 0x1949 is no longer needed.
After running the above, the kindle should automatically start into recovery.
From here you will be able to mount it as an external drive and copy over any rom you would like to use.
Pick something from here Kindle Fire Development *FULL LIST* - 17.04.2012 - under the Custom / Stock Roms section.
Click to expand...
Click to collapse
Thank you SO MUCH! I was able to get both files on. I don't know how to get into recovery, but here is the output:
c:\firebuild>fastboot -i 0x1949 flash bootloader u-boot.bin
< waiting for device >
sending 'bootloader' (203 KB)...
OKAY [ 0.055s]
writing 'bootloader'...
OKAY [ 0.051s]
finished. total time: 0.106s
c:\firebuild>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.002s
c:\firebuild>fastboot flash recovery twrp-fire-2.1.0.img
sending 'recovery' (6 KB)...
OKAY [ 0.006s]
writing 'recovery'...
OKAY [ 0.045s]
finished. total time: 0.051s
c:\firebuild>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.003s
c:\firebuild>fastboot -i 0x1949 boot twrp-fire-2.1.0.img
creating boot image...
creating boot image - 10240 bytes
downloading 'boot.img'...
OKAY [ 0.006s]
booting...
OKAY [ 0.003s]
finished. total time: 0.010s
When you first turn the kindle on you will get a yellow triangle (FFF 1.2) or a Kundle Fire logo with the Android (FFF 1.3). When in that screen tap the power button until it turns orange. It should then boot you into TWRP.
From there you can goto mount and then click mount usb storage, this will allow you to copy the rom you picked to the SDCard.
After copied, unmount, then goto install and select to install the rom.
Oh, one more thing. Don't forget to wipe cache, dalvik-cache, and factory restore.
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~!
Hey everybody.
So I had my phone rooted for a week now, but I had plenty of problems with root (Magisk 16.4, TWRP 3.2.1.0). Running Android P beta p2.
I wanted to simply restore the phone to it's stock state. Main idea was to get OS reinstalled and stock recovery flashed over TWRP.
When ever I tried to flash the boot.img from the stock image in fastboot I got the error saying "FAILED (remote: Requested download size is more than max allowed".
So mid process I read somewhere I might have to unlock unlock_critical. I tried running that but no response from the phone. I didn't want to interrupt so I left it running for a few minutes, came back and nothing has changed. Except for the phone not being able to boot to Android. And so here I am stuck in a boot loop.
So I read here: https://forum.xda-developers.com/pixel-2-xl/help/hard-bricked-t3770769
And realized maybe I should try this skipsoft toolkit. Well no luck.
This is what I get when I try to use option 9. (Download/Extract/Flash Google Factory Stock Image [Flash Part or Whole Rom]). I choose to flash the whole ROM.
Here is what I got.
Starting Flash Process..
Flashing Bootloader Image..
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.003s
An error occured when flashing the image
Try rebooting the device manually back to fastboot mode:
1. Unplug the usb cable
2. Hold the Power and Volume Down buttons until it reboots to Fastboot Mode.
From the main menu in the Toolkit choose the Download/Extract/Flash menu, then
select Flash previously downloaded image.
Sometimes there is a glitch in the flash process and doing it again will fix it.
Press any key to return to the Main Menu..
I gave Deuces Bootloop tool script a try and this is what I got:
Deuces-flash-all-script-V4.5-Windows
for Taimen or Walleye - Google Pixel 2 / XL
USE AT YOUR OWN RISK
Press any key to continue . . .
Make Sure your Device is in Fastboot Mode
(Power off, hold Volume-Down, hold Power)
Once you are in fastboot,
Press any key to continue . . .
Unlock Bootloader[Y/N]?y
Running Unlock
Look at your device,
press up arrow and Power to confirm
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.002s
This will say "failed" if already unlocked - ignore
Running Unlock_critical
Look at your device,
press up arrow and Power to confirm
FAILED (remote: unknown command)
Finished. Total time: 0.002s
This will say "failed" if already unlocked - ignore
Locating Bootloader and Radio Filenames
Flashing...
it is safe to ignore errors about active partition - there are multiple entries to support multiple versions of platform tools
File Not Found
File Not Found
fastboot: error: Device does not support slots
fastboot: error: Device does not support slots
rebooting into bootloader OKAY [ 0.002s]
Finished. Total time: 0.003s
rebooting into bootloader OKAY [ 0.002s]
Finished. Total time: 0.003s
Slot _b does not exist. supported slots are:
a
b
fastboot: error: Device does not support slots
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.003s
rebooting into bootloader OKAY [ 0.002s]
Finished. Total time: 0.003s
Slot _a does not exist. supported slots are:
a
b
fastboot: error: Device does not support slots
fastboot: error: cannot load 'abl.img': No such file or directory
fastboot: error: cannot load 'aes.img': No such file or directory
fastboot: error: cannot load 'apdp.img': No such file or directory
fastboot: error: cannot load 'boot.img': No such file or directory
fastboot: error: Failed to identify current slot
fastboot: error: cannot load 'cmnlib64.img': No such file or directory
fastboot: error: cannot load 'devcfg.img': No such file or directory
fastboot: error: cannot load 'dtbo.img': No such file or directory
fastboot: error: cannot load 'hyp.img': No such file or directory
fastboot: error: cannot load 'keymaster.img': No such file or directory
fastboot: error: cannot load 'laf.img': No such file or directory
fastboot: error: Failed to identify current slot
fastboot: error: cannot load 'msadp.img': No such file or directory
fastboot: error: cannot load 'pmic.img': No such file or directory
fastboot: error: cannot load 'rpm.img': No such file or directory
fastboot: error: cannot load 'tz.img': No such file or directory
fastboot: error: cannot load 'vbmeta.img': No such file or directory
fastboot: error: cannot load 'vendor.img': No such file or directory
fastboot: error: cannot load 'xbl.img': No such file or directory
Flashing System A
fastboot: error: cannot load 'system.img': No such file or directory
Flashing System B
fastboot: error: cannot load 'system_other.img': No such file or directory
fastboot: error: Device does not support slots
Setting current slot to 'b' FAILED (status read failed (Too many links))
Finished. Total time: 5.871s
< waiting for any device >
Any help would be greatly appreciated.
Thank you in advance.
jan_ruc said:
Hey everybody. So I had my phone rooted for a week now, but I had plenty of problems with root (Magisk 16.4, TWRP 3.2.1.0)...
Click to expand...
Click to collapse
I don't have this device but, your best bet is probably to post this question within the following thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3702418
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.