Database Info

Rooting issues - ADB unable to locate phone in fastboot

Hi everyone,
I have looked everywhere on google and have been at this for over 5 hours now. I have tried rooting my phone from 3 different PCs (XP SP3, SP2 and 7). With all of them i have managed to get the drivers for adb installed (after many problems) and got all the way to the fastboot part of the rooting.
Once i get there, i have the same problem on all 3 PCs. ADB can no longer find my phone! Following the instructions, i checked for the device before i powered it off and found it by doing abd devices in cmd prompt. The moment the device is powered off and then back on, bam! No more device!
I am at my wits end at this point and just don't know what else I could possibly do! I would be immensely grateful for ANY advice.
I did check that my device allowed USB debug so that's not it either.
Also, my phone is a Rogers phone and I have just put through the upgrade they sent this morning.

adb cant find your phone in fastboot mode but fastboot can
Try writing fastboot devices instead of adb devices
All the comands in fastboot mode start with fastboot...e.g fastboot flash xxx xxx.img

I ran into this problem as well on my attempt, I forgot to re-enable (or enable) depending on where I was at "usb debugging" which is in:
settings> applications > development > check the usb debugging box.
After that, when you do abd devices in your shell, it should surely list after that. Good luck!
edit-- woops scratch that.. sorry I just read back that you made sure of that.

Thank you for that!
Now, i see it in fastboot, but when i try typing fastboot boot recovery.img i get a "cannot load recovery.img"
Sorry, apparently i need a lot more hand holding than i though!
(this is where I am getting the instructions from HowardForums. I'd post the link but I can't do that yet on this forum...
Basically, these are the instructions i am following:
If the phone you have is an HTC Magic (no hardware keyboard), the method is pretty much the same. I modified Haykuro's zip with files that were meant for the Magic. You can grab it here:
*link*
Again, open another command prompt as steps 2, and 6-8 are entered in the command prompt.
Quote:
Originally Posted by Haykuro-ish
0. Place update.zip on SD card.
1. power off the phone and boot into fastboot (hold back and power)
2. fastboot boot recovery.img
3 [optional]. make a backup with nandroid
3. apply update. (LET IT FINISH, DO NOT TOUCH ANYTHING UNTIL YOUR PHONE IS COMPLETELY IDLE. DO NOT TOUCH AFTER FIRST REBOOT (WHEN CHIP APPEARS) UNLESS YOU LIKE A BRICK. )
4. reboot out of recovery mode.
5. power off phone, hold back button and power to boot into fastboot again
6. fastboot flash boot boot.img
7. fastboot flash recovery recovery.img
8. fastboot reboot
enjoy!
These are pretty much the Haykuro instructions for the Dream, which I modified to apply to the Magic. The boot and recovery images were made by Amon_RA. Happy Rooting!
Just like with the Dream, the first part flashes a good SPL, the second flashes a rooted boot and recovery. The easiest way to test if the device is rooted is to open another command prompt in the tools dir and type
Code:
adb root
If it returns that adb is already running in root, then you're all set.
Click to expand...
Click to collapse
Am i doing something wrong?
Thanks so much!

You need to navigate to the folder where you saved your recovery.img
For example if you put it on d:/Android dev. you will need to do (inside cmd)
d: (switches to drive d
cd d:/Android dev. (changes the folder to android dev.)
and then issue the fastboot command
without the brackets of course...

eyegor said:
You need to navigate to the folder where you saved your recovery.img
For example if you put it on d:/Android dev. you will need to do (inside cmd)
d: (switches to drive d
cd d:/Android dev. (changes the folder to android dev.)
and then issue the fastboot command
without the brackets of course...
Click to expand...
Click to collapse
Again, thank you so much! It seems I am still having issues as now I'm being told that "remote not allow".... is this a rogers thing?
Again i do apologize for all the hand-holding necessary here

yes, i am getting this <remote:not allow> message too. I was able to fix my other magic (purchased in october) via fastboot boot recovery.img but not this new one i have (purchased in Dec).
Anyone have any ideas how to bypass this block of 'remote, not allowed"?

[TIP] How to install Clockworkmod Recovery (detailed instructions)

Moderator Edit 12/8/12
Do not use this this method twrp is officially supported for the one x. Download goo manager from the market or check the dev section.
It is not my intention to step on the toes of other people who have been more than helpful when it comes to questions relating to the installation of this or that.
Although I am reasonably familiar with many of the installation procedures when it comes to ROMs and Kernels, including Clockworkmod Recovery, etc., I am still a bit hesitant because I simply want to make sure that I am not making a mistake. After all, we spend lots of money on our phones, and the slightest error can be permanent.
I respect and admire all the developers who work tirelessly to make our lives a little bit better, and who often fulfill our ongoing need to “fiddle” with our phones. Thank you!
That being said, here is a detailed explanation of how to install Clockworkmod Recovery.
First, your bootloader must be unlocked. It doesn’t matter if you have the “TAMPERED” entry; this procedure will still work. Second, you must also have all necessary mobile phone drivers installed, including ADB, ADB drivers, and fastboot. From this point forward, I will call all these files your “Fastboot” files. If you don’t have these files, you can download them by clicking on the link at the end of this post.
At this point I’m assuming you’ve placed your Fastboot files in a separate folder within the root directory of your PC (the “C” drive?). I put these files in a folder called fastboot, but it really doesn’t matter, as long as you remember the location.
Here’s an image from my Windows Explorer screen to give you an idea of what I did:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, here we go …
Download the Clockworkmod Recovery image file and change the name to CWM.img. This is an easy name to remember, which will help further along in these instructions.
Place your newly-named CWM.img file in the directory where your Fastboot files are located.
Power down your device.
While holding VOLUME DOWN, press and hold the POWER button for a few seconds. Continue to hold VOLUME DOWN until your bootloader screen appears.
Somewhere in the middle of your bootloader screen will be seven entries entitled FASTBOOT, RECOVERY, FACTORY RESET, CLEAR STORAGE, SIMLOCK, IMAGE CRC, and POWER DOWN.
Using your VOLUME keys, make sure FASTBOOT is highlighted, and then press the POWER button once.
You should now be in the FASTBOOT Bootloader screen. On my ONE X, and I’m assuming the same for everyone, the word FASTBOOT will be highlighted with a RED background. Either way, it should be highlighted.
Connect device to your PC via USB cable.
If all is going well, the word FASTBOOT should now say FASTBOOT USB. From this point forward, do not touch the device.
Open a Command Prompt window on your PC (Press the Start button, and in the search field type cmd, and then press Enter). Here’s an example of how your Command Prompt window may look:
You must now change the directory to where your Fastboot files are located. As I mentioned above, mine are in the directory c:\fastboot. Therefore, I would need to type the following command in the Command Prompt window: cd c:\fastboot
The “cd” refers to “change directory,” while the rest is where your Fastboot files are located. Here’s how your Command Prompt window will look like after you’ve typed the above, and BEFORE you press the Enter key.
Here’s an example of how your Command Prompt window will appear AFTER you press the Enter key:
Next you need to type the following: fastboot flash recovery CWM.img
Renaming the file to CWM.img simplifies the above entry because this name is easy to remember.
Here’s how your Command Prompt window will appear BEFORE you press the Enter key:
Now press the Enter key and let the program run.
The entire installation/flash will take only a few seconds. When complete, your Command Prompt window will return to your fastboot directory (see image below).
Ignore the error in my image above, the line called error: cannot load ‘CWM.img’
This error message appeared ONLY because I didn’t want to install Clockworkmod Recovery on my device a second time. Hey, if it ain’t broke, don’t fix it, right?
Reboot your device.
DONE! You now have Clockworkmod Recovery on your phone.
These instructions are available in PDF format by clicking on the link at the end of this post.
Peter
Here's the link to the Clockworkmod Recovery file:
Clockworkmod Recovery Image
Detailed Instructions
Fastboot Files

Thanks for the excellent guide, Peter!
We were all hardcore newbies at one point and while it's annoying to see them ask redundant questions or ones that have been answered in the first post of a thread, you have to have some sympathy for them. Especially when they do something like get a soft-bricked device and begin to panic.

Thanks a lot for this!!
Would this work similarly on Linux or Mac?
Cheers!

THANK YOU this was very helpfull

Mac or Linux, I simply don't know ...
zmanw330 said:
Thanks a lot for this!!
Would this work similarly on Linux or Mac?
Cheers!
Click to expand...
Click to collapse
Regretfully, I have little to no knowledge concerning Mac and Linux, so I don't know if it would work. Sorry.
Perhaps others can answer this question.
Peter

zmanw330 said:
Thanks a lot for this!!
Would this work similarly on Linux or Mac?
Cheers!
Click to expand...
Click to collapse
Almost identical. On my Ubuntu machine I just need to type "sudo fastboot flash recovery xxx.img" and boom!
I can't see Macs being too different.

PeterHTC said:
First, your bootloader must be unlocked.
Click to expand...
Click to collapse
has this been done? have I missed something in the past day?

So far this is only for Rogers version

Peter i am following your instructions to a tee but when i try to push cwm i get the same error that shows up on your screen, i am rooted and bootloader unlocked. Can someone help
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott> cd c:\fastboot
c:\fastboot>fastboot flash recovery CWM.img
error: cannot load 'CWM.img'
c:\fastboot>

fastboot flash recovery recovery.img
Sent from my HTC One XL using xda premium

No, you didn't miss anything ... so far
fionic said:
has this been done? have I missed something in the past day?
Click to expand...
Click to collapse
No, you didn't miss anything so far. The bootloader on AT&T units cannot yet be unlocked, but I'm sure it's only time. Once unlocked, then you can follow the installation instructions.
Peter

Peter said change the file name to CWM

I hope I'm not patronizing, but ...
sm625614 said:
Peter i am following your instructions to a tee but when i try to push cwm i get the same error that shows up on your screen, i am rooted and bootloader unlocked. Can someone help
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott> cd c:\fastboot
c:\fastboot>fastboot flash recovery CWM.img
error: cannot load 'CWM.img'
c:\fastboot>
Click to expand...
Click to collapse
I hope I don't insult you, but did you connect the phone to your PC via USB? The reason I ask is that I got my error message because I disconnected my phone prior to hitting the Enter key. As I mentioned, I didn't want to install it a second time and risk doing something harmful.
Did you also get FASTBOOT USB highlighted on your device after you plugged it in?
Peter
Addendum: Don't forget that these entries in your Command Prompt are case sensitive. Capital letters must remain as capitals, and small letters as small ... exactly as shown in my instructions. Again, I hope I'm not patronizing anyone. That's not my intention.

Of course your not insulting me, your just being detailed lol. The phone is 100% connected to the computer via USB. I am in fastboot mode with FASTBOOT USE highlighted in red. I am following you instructions perfectly and i got the same error. Do you think i should reinstall htc sync to reinstall the drivers. I am quite lost here on why this is not working.

Did you ...
sm625614 said:
Of course your not insulting me, your just being detailed lol. The phone is 100% connected to the computer via USB. I am in fastboot mode with FASTBOOT USE highlighted in red. I am following you instructions perfectly and i got the same error. Do you think i should reinstall htc sync to reinstall the drivers. I am quite lost here on why this is not working.
Click to expand...
Click to collapse
One thing I should have included in my first post (I will amend it shortly), is a link to the actual Clockworkmod Recovery file, which is currently available on another thread.
Did you download THAT file?
Peter
Addendum: Clockworkmod Recovery Files link now included in original post
Addendum 2: Re-installing HTC Sync might be helpful. It's what I would eventually do.

YES i have that file and i renamed it to the CWM.img name that you recommended. What do you think i should do?

I changed the first image in the original post ...
I changed the first image in the original post. It now includes the Clockworkmod Recovery file, marked as CWM.
Peter

Hmm, I would ...
sm625614 said:
YES i have that file and i renamed it to the CWM.img name that you recommended. What do you think i should do?
Click to expand...
Click to collapse
Well, I'm not entirely sure. What I would do is start all over again after restarting your PC and Phone. If it does not work then, uninstall and reinstall HTC sync. After that, I'm stumped. Sorry.
Peter

sm625614 said:
Of course your not insulting me, your just being detailed lol. The phone is 100% connected to the computer via USB. I am in fastboot mode with FASTBOOT USE highlighted in red. I am following you instructions perfectly and i got the same error. Do you think i should reinstall htc sync to reinstall the drivers. I am quite lost here on why this is not working.
Click to expand...
Click to collapse
Do you have a file named "CWM.img" in the same folder as fastboot? That part of the command is telling fastboot which file to install. Make sure the image file is named correctly, or you can alter the command to reflect the name of the file.

I think you should write it into the title and the post saying for now this is only for Rogers users. It might cause a problem bbecause you said even if the bootloader ssays tampered it'll work. And I'm on att and it says tampered bbut this won't work for ATT HOX.
Just a precaution
Sent from my HTC Vivid 4G LTE using Tapatalk 2

problem with recovery

Hi guys,
I have a problem with install recovery on my Nexus S. When I'm in the command promt and I typed cmd. Then when I must type ""fastboot flash recovery ...img" it don't work anymore. I've downloaded the newest recovery from here: http://forum.xda-developers.com/showthread.php?t=988686
The file is in my download folder and called "5023-green.img". When I'm in the command promt and go into the download folder and then type "fastboot flash recovery 5023-green.img" it gives an error. It don't recocnize the file
I hope it is clear to understand because it's hard to explain My phone is unlocked and is in fastboot.

giganielsie said:
Hi guys,
I have a problem with install recovery on my Nexus S. When I'm in the command promt and I typed cmd. Then when I must type ""fastboot flash recovery ...img" it don't work anymore. I've downloaded the newest recovery from here: http://forum.xda-developers.com/showthread.php?t=988686
The file is in my download folder and called "5023-green.img". When I'm in the command promt and go into the download folder and then type "fastboot flash recovery 5023-green.img" it gives an error. It don't recocnize the file
I hope it is clear to understand because it's hard to explain My phone is unlocked and is in fastboot.
Click to expand...
Click to collapse
put both fastboot.exe and the recovery.img file in the same folder (for example c:/flash) then open cmd and navigate to that folder, you should see in the command line something like c:/fash/. Now you can do fastboot flash recovery recoveryname.img
Probably you don't have fastboot added to the path or you're not pointing to the correct folder where the recovery image is.

DeuXGod said:
put both fastboot.exe and the recovery.img file in the same folder (for example c:/flash) then open cmd and navigate to that folder, you should see in the command line something like c:/fash/. Now you can do fastboot flash recovery recoveryname.img
Probably you don't have fastboot added to the path or you're not pointing to the correct folder where the recovery image is.
Click to expand...
Click to collapse
Thanks for youre reply but still get the error. I've downloaded a tool package from here: http://www.mediafire.com/?wj0kbm0dooa5wsd
In this package is a fastboot.exe file. I put this file with the 5023-green.img in the same folder but still get error

giganielsie said:
Thanks for youre reply but still get the error. I've downloaded a tool package from here: http://www.mediafire.com/?wj0kbm0dooa5wsd
In this package is a fastboot.exe file. I put this file with the 5023-green.img in the same folder but still get error
Click to expand...
Click to collapse
I use the Android SDK, it has the updated fastboot tool. Anyway are you rooted already? If you're just get the Rom Manager from the market and install CWM from there. If not, try to get the android SDK from here:
http://developer.android.com/sdk/index.html
Install it (make sure that you also have java SE installed) to, let's say, C:/androidsdk
It will prompt you to open the Android SDK manager, say yes, select platform tools and hit download
Now in c:/androidsdk/platform-tools you will have fastboot.exe
Download the recovery from http://www.clockworkmod.com/rommanager to the platform-tools folder
Put your phone in fastboot (volume up+power on)
then open the cmd, navigate to c:/androidsdk/platform-tools and do fastboot devices, it should show you the SN from your nexus. If it doesn't show, then you need to update your ADB driver. You can get it from the Android SDK Manager in the extras.
Now do fastboot flash recovery recoveryname.img
Should work now

DeuXGod said:
I use the Android SDK, it has the updated fastboot tool. Anyway are you rooted already? If you're just get the Rom Manager from the market and install CWM from there. If not, try to get the android SDK from here:
http://developer.android.com/sdk/index.html
Install it (make sure that you also have java SE installed) to, let's say, C:/androidsdk
It will prompt you to open the Android SDK manager, say yes, select platform tools and hit download
Now in c:/androidsdk/platform-tools you will have fastboot.exe
Download the recovery from http://www.clockworkmod.com/rommanager to the platform-tools folder
Put your phone in fastboot (volume up+power on)
then open the cmd, navigate to c:/androidsdk/platform-tools and do fastboot devices, it should show you the SN from your nexus. If it doesn't show, then you need to update your ADB driver. You can get it from the Android SDK Manager in the extras.
Now do fastboot flash recovery recoveryname.img
Should work now
Click to expand...
Click to collapse
Thanks for youre explanation!
I think my ADB driver must have an update because when I type in the command promt c"/androidsdk/platform-tools>fastboot devices he says: "can not find the specified path".
In the Android SDK manager in extras is not shows any ADB driver? I have installed the Google USB Driver and the Google Web Driver in extras but which other file must I download?

giganielsie said:
Thanks for youre explanation!
I think my ADB driver must have an update because when I type in the command promt c"/androidsdk/platform-tools>fastboot devices he says: "can not find the specified path".
In the Android SDK manager in extras is not shows any ADB driver? I have installed the Google USB Driver and the Google Web Driver in extras but which other file must I download?
Click to expand...
Click to collapse
The google USB driver is the ADB driver. If you go into your Device manager in windows, with your Nexus in fastboot and connected to the PC, can you see a ADB device? Or do you see a yellow exclamation mark? You sure you're in the androidsdk folder in the command prompt?
Let's try a different thing. Copy adb.exe, fastboot.exe and AdbWinApi.dll to C:/windows/system32
Reboot just in case and try to do again fastboot devices from the cmd
Should work now

DeuXGod said:
The google USB driver is the ADB driver. If you go into your Device manager in windows, with your Nexus in fastboot and connected to the PC, can you see a ADB device? Or do you see a yellow exclamation mark? You sure you're in the androidsdk folder in the command prompt?
Let's try a different thing. Copy adb.exe, fastboot.exe and AdbWinApi.dll to C:/windows/system32
Reboot just in case and try to do again fastboot devices from the cmd
Should work now
Click to expand...
Click to collapse
Also don't work
This is the error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In that folder are all of the files I needed so it should work though he don't work
And my phone also recognize as Android ADB Interface.
Edit: It's working!!! My brother fixed it! Thanks for the replies!!!:good::victory:

Now I have recovery but now I have another problem. When I reboot my phone, I can't go anymore to recovery. I see then a green android with a open stomach. Anybody a solution? It looks like there is something went wrong with the install of the recovery but what?
And I have root permission now but with rom manager I can install recovery but when I reboot into recovery, the green android with open stomach come back...

Stock ROM? Delete /system/etc/install-recovery.sh, flash CWM again and that's it.
Sent from my Nexus S using xda app-developers app

DeuXGod said:
Stock ROM? Delete /system/etc/install-recovery.sh, flash CWM again and that's it.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Thanks!!! It looks like it works! Thanks for youre fast replies:good::good:

I didn't want to create another thread because I am somewhat having the same problem and I really don't know what to do. I have an M200 version on T-Mobile USA and I got the JB OTA yesterday and everything was running fine until, about 30 mins ago. The phone slowed down and the started to reboot and it keeps rebooting sometimes into safe mode. I took out the battery and tried the recovery mode, but this is what I get.

GripR said:
I didn't want to create another thread because I am somewhat having the same problem and I really don't know what to do. I have an M200 version on T-Mobile USA and I got the JB OTA yesterday and everything was running fine until, about 30 mins ago. The phone slowed down and the started to reboot and it keeps rebooting sometimes into safe mode. I took out the battery and tried the recovery mode, but this is what I get.
Click to expand...
Click to collapse
Do you have unlocked bootloader? If you have just flash CWM from the fastboot, enter in recovery and do a full wipe and install another ROM or even the stock image. Don't forget to remove the system/etc/install-recovery.sh file if you flash the stock ROM so CWM won't be overwritten every time you do a reboot.

DeuXGod said:
Stock ROM? Delete /system/etc/install-recovery.sh, flash CWM again and that's it.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
from the dead droid reboot with power+ vol up
enter jb and with a file manager (like es file..or something else) delete both:
-/system/recovery-from-boot.p
-/system/etc/install-recovery.sh
reboot and reinstall cwm via fastboot

Only problem with that is he will require root access to do that.
Which I am assuming he currently doesn't have.
Anyways as someone already stated. Unlock bootloader if it isn't already. That will wipe your data off the phone.
Boot or flash a custom recovery.
Flash su.zip or supersu etc to get root
Boot up and make sure you actually have root.
Do as above poster said and remove those files.
Either flash recovery from a app like goo manager or rom manager. Hell now that that I think about it. I think rom manger has the option to remove those files for you when it flashes cwm. Or reboot into the bootloader and flash the recovery with fastboot. It will stick. Keep in mind that you need to download the fastboot version of the recovery if you go that route. It will be a .img. the others will be a .zip .
If you don't know how to use fastboot. Read the quides/stickies etc.

I'm lost installing CMW

OMG yes i know im a newb but there is a first time for everybody for anything.
So i'm trying to unlock, root, install cwm and install custom roms but ive looked at all the instruction from many thread and a lot of them had missing steps
Anyways, i've downgraded from JB to 4.0.3, rooted, unlocked and now i'm trying to install CWM. So i installed android SDK and all tools, i've put recovery image in same folder as fastboot.exe, i've booted the tablet and selectied USB icon but wtf do i do now??
I'm basically here:
** FastBoot Method **
1) Install Android SDK
2) Download CWM Recovery image from the original thread and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Copy the downloaded file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot into fastboot mode (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
Where do i get this command line?? is it command line from windows such as CMD?? cause if it is, i've tried it and nothing. Do i have to point to where is the recovery image?? Its in C:\Users\Patrick\AppData\Local\Android\android-sdk\platform-tools but i'm lost from that point, i'm not sure what command line i have to use, and how to set it up so i can tell it where to look.
Can anybody help me please?

polish_pat said:
OMG yes i know im a newb but there is a first time for everybody for anything.
So i'm trying to unlock, root, install cwm and install custom roms but ive looked at all the instruction from many thread and a lot of them had missing steps
Anyways, i've downgraded from JB to 4.0.3, rooted, unlocked and now i'm trying to install CWM. So i installed android SDK and all tools, i've put recovery image in same folder as fastboot.exe, i've booted the tablet and selectied USB icon but wtf do i do now??
I'm basically here:
** FastBoot Method **
1) Install Android SDK
2) Download CWM Recovery image from the original thread and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Copy the downloaded file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot into fastboot mode (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
Where do i get this command line?? is it command line from windows such as CMD?? cause if it is, i've tried it and nothing. Do i have to point to where is the recovery image?? Its in C:\Users\Patrick\AppData\Local\Android\android-sdk\platform-tools but i'm lost from that point, i'm not sure what command line i have to use, and how to set it up so i can tell it where to look.
Can anybody help me please?
Click to expand...
Click to collapse
change directory to the folder the recover/fastboot is in, using the CMD on windows. So:
"cd C:\Users\Patrick\AppData\Local\Android\android-sdk\platform-tools"
make sure the recovery is called "recovery.img" and that its in the "platform-tools" folder alongside the fastboot.exe, then run the commands:
"fastboot -i 0x0B05 flash recovery recovery.img"
and
"fastboot reboot"

polish_pat said:
OMG yes i know im a newb but there is a first time for everybody for anything.
So i'm trying to unlock, root, install cwm and install custom roms but ive looked at all the instruction from many thread and a lot of them had missing steps
Anyways, i've downgraded from JB to 4.0.3, rooted, unlocked and now i'm trying to install CWM. So i installed android SDK and all tools, i've put recovery image in same folder as fastboot.exe, i've booted the tablet and selectied USB icon but wtf do i do now??
I'm basically here:
** FastBoot Method **
1) Install Android SDK
2) Download CWM Recovery image from the original thread and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Copy the downloaded file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot into fastboot mode (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
Where do i get this command line?? is it command line from windows such as CMD?? cause if it is, i've tried it and nothing. Do i have to point to where is the recovery image?? Its in C:\Users\Patrick\AppData\Local\Android\android-sdk\platform-tools but i'm lost from that point, i'm not sure what command line i have to use, and how to set it up so i can tell it where to look.
Can anybody help me please?
Click to expand...
Click to collapse
Yes, command line is in your PC. The location of the fastboot.exe located in c:\android-sdk\platformtools (if you install from sdk).
On your PC, open CMD and navigate to the above directory where fastboot.exe is. Make sure your recovery.img in also copied to this same folder. Now you can execute the fastboot comand:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
---------- Post added at 05:52 PM ---------- Previous post was at 05:48 PM ----------
buhohitr said:
Yes, command line is in your PC. The location of the fastboot.exe located in c:\android-sdk\platformtools (if you install from sdk).
On your PC, open CMD and navigate to the above directory where fastboot.exe is. Make sure your recovery.img in also copied to this same folder. Now you can execute the fastboot comand:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
I think it's easier for you to download Voodoo OTA root keeper to preserve root, then upgrade to JB, then use OTA root keeper to restore root. After this you can install TWRP recover by download goomanager from the play store and install it, once you have twrp, you're home free.
Currently you are on ICS, becareful if you use a wrong version of cwm you could brick your device. Many ppl installed ICS cwm version then upgrade to JB without the right version and they bricked.

buhohitr said:
Yes, command line is in your PC. The location of the fastboot.exe located in c:\android-sdk\platformtools (if you install from sdk).
On your PC, open CMD and navigate to the above directory where fastboot.exe is. Make sure your recovery.img in also copied to this same folder. Now you can execute the fastboot comand:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
---------- Post added at 05:52 PM ---------- Previous post was at 05:48 PM ----------
I think it's easier for you to download Voodoo OTA root keeper to preserve root, then upgrade to JB, then use OTA root keeper to restore root. After this you can install TWRP recover by download goomanager from the play store and install it, once you have twrp, you're home free.
Currently you are on ICS, becareful if you use a wrong version of cwm you could brick your device. Many ppl installed ICS cwm version then upgrade to JB without the right version and they bricked.
Click to expand...
Click to collapse
Thanks but I've already downgraded. I'll try what the guy above said thank you for the help
Sent from my SGH-I747M using Tapatalk 2

when you are in the fastboot folder, you have to press control & right click inside the folder, and you will see the option to open a terminal.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Pat,
If it makes you feel any better I had a heck of a time with this myself.
Once I realized I had platform tools in a folder on my PC desktop with the command prompt
in it I was able to flash.
Gotta say it wasn't easy to figure out in bits and pieces.
Sent from the inside out...

Thanks guys, you've been REALLY helpful! I completely forgot about the shortcut to open cmd in a folder, and i'm not sure if you were wrong or its because im on windows 8 but its ctrl + shift + right click
EDIT: now i get a problem, it do all this and i get "waiting for device"
i tried different USB ports, same deal...any ideas?
EDIT: EDIT: tried all USB port but one, the last one i used did the trick, thanks for all!

I'm having this exact same problem but changing USB ports is not working for me and I tried everything else. Would it help if I tried a different computer?
Sent from my Galaxy Nexus using xda app-developers app

mnk0ota said:
I'm having this exact same problem but changing USB ports is not working for me and I tried everything else. Would it help if I tried a different computer?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
try to open CMD as Administrator.

buhohitr said:
...
I think it's easier for you to download Voodoo OTA root keeper to preserve root, then upgrade to JB, then use OTA root keeper to restore root. After this you can install TWRP recover by download goomanager from the play store and install it, once you have twrp, you're home free.
Currently you are on ICS, becareful if you use a wrong version of cwm you could brick your device. Many ppl installed ICS cwm version then upgrade to JB without the right version and they bricked.
Click to expand...
Click to collapse
I don't mean to threadjack, but this portion of your post caught my attention.
I just swapped a prime for an infinity. I rooted, installed rootkeeper, preserved root, upgraded to JB and restored root.
Are you saying I can install goomanager and update recovery without unlocking via the Asus tool?
If so, sweet!
Sent from my MB855 using Tapatalk 2

John Kotches said:
I don't mean to threadjack, but this portion of your post caught my attention.
I just swapped a prime for an infinity. I rooted, installed rootkeeper, preserved root, upgraded to JB and restored root.
Are you saying I can install goomanager and update recovery without unlocking via the Asus tool?
If so, sweet!
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
No. You will still have to unlock the bootloader to install a custom recovery, unfortunately.

Firebrazer said:
No. You will still have to unlock the bootloader to install a custom recovery, unfortunately.
Click to expand...
Click to collapse
Thanks... if it seems too good to be true it probably is.
Sent from my MB855 using Tapatalk 2

Did I brick my Pixel 3 trying to bring it back to stock?

Hello guys,
I needed to send in my Pixel 3 for repair and wanted to bring it back to stock. So I thought that I flash a factory Image and lock the bootloader afterwards.
But It did bug and give me errors like boot.img not in archive etc. even though I completly upacked the zip inside that path.
Anyways, now my adb doesnt find any devices and I cant boot. On the Fastboot screen it says the following:
boot slot: b
Enter reason: error booting boot.img
thanks in advance!

Try to factory reset your phone from recovery.

levibuko said:
Hello guys,
I needed to send in my Pixel 3 for repair and wanted to bring it back to stock. So I thought that I flash a factory Image and lock the bootloader afterwards.
But It did bug and give me errors like boot.img not in archive etc. even though I completly upacked the zip inside that path.
Anyways, now my adb doesnt find any devices and I cant boot. On the Fastboot screen it says the following:
boot slot: b
Enter reason: error booting boot.img
thanks in advance!
Click to expand...
Click to collapse
Do you have the latest sdk platform tools (fastboot)? Run the flash-all batch file you find in the extracted factory image. When you boot into the bootloader run fastboot devices from your pc. Is your device reconized?

Did you download the right image for the current build your on??

anasmhds said:
Try to factory reset your phone from recovery.
Click to expand...
Click to collapse
If I try to acces recovery it just reboots back to fastboot or I get the android logo with no command error
jd1639 said:
Do you have the latest sdk platform tools (fastboot)? Run the flash-all batch file you find in the extracted factory image. When you boot into the bootloader run fastboot devices from your pc. Is your device reconized?
Click to expand...
Click to collapse
I updated from the google webpage . Yes, fastboot devices gives me a a device ID. But with adb it says waiting for devices.
thatsupnow said:
Did you download the right image for the current build your on??
Click to expand...
Click to collapse
I did download android 10, before I was on android 9. Was that my mistake?

levibuko said:
If I try to acces recovery it just reboots back to fastboot
. Yes, fastboot devices gives me a a device ID. But with adb it says waiting for devices.
Click to expand...
Click to collapse
ADB only works when booted in to recovery or system. You need fastboot when booted in to the bootloader. That's why you don't get anything from adb.

Are you sure anything happened when you tried to relock? Since you can get fastboot to recognize the device, try a flash-all.

sliding_billy said:
Are you sure anything happened when you tried to relock? Since you can get fastboot to recognize the device, try a flash-all.
Click to expand...
Click to collapse
I didnt relock yet. If i try the flash all script now it does some more than before but it restarts and shows me the no command (android logo) error. and then the script finishes and says waiting for other devices.

levibuko said:
I didnt relock yet. If i try the flash all script now it does some more than before but it restarts and shows me the no command (android logo) error. and then the script finishes and says waiting for other devices.
Click to expand...
Click to collapse
The no command with the dead andriod is the stock recovery. Hold power button and press and release the vol up key, timing can be tricky. If it gets into recovery try a factory reset.

jd1639 said:
The no command with the dead andriod is the stock recovery. Hold power button and press and release the vol up key, timing can be tricky. If it gets into recovery try a factory reset.
Click to expand...
Click to collapse
Allright, I will try it as soon as I am back home tomorrow.

jd1639 said:
The no command with the dead andriod is the stock recovery. Hold power button and press and release the vol up key, timing can be tricky. If it gets into recovery try a factory reset.
Click to expand...
Click to collapse
levibuko said:
Allright, I will try it as soon as I am back home tomorrow.
Click to expand...
Click to collapse
What JD said. You aren't bricked most likely. Lots of things can be done from stock recovery. Once you are at the recovery command page, you will likely have ADB recognition as well.

sliding_billy said:
What JD said. You aren't bricked most likely. Lots of things can be done from stock recovery. Once you are at the recovery command page, you will likely have ADB recognition as well.
Click to expand...
Click to collapse
I am glad to hear that. So could you recap what I gotta do now?
As far as I understand I need the stock image (any particular one?) and just need to run the flash-all script while in fastboot mode ?
What if it reboots and I am at the no command screen? Do I need to do sth with the phone or wait?

So I tried it again, I still get some "archive does not contain" errors but after the script ended I was able to get to recovery and factory reset. sadly I still cant boot and I get to the same screen. I dled the factory img from googles webpage so I dont understand why so much files are missing. the scipt also only runs for a few secs.

levibuko said:
So I tried it again, I still get some "archive does not contain" errors but after the script ended I was able to get to recovery and factory reset. sadly I still cant boot and I get to the same screen. I dled the factory img from googles webpage so I dont understand why so much files are missing. the scipt also only runs for a few secs.
Click to expand...
Click to collapse
There are archives (images) that the device doesn't use and aren't contained in the factory image so that's normal, fastboot tries to run them anyway. But only running a few seconds is not normal. Do you remember, or can try to run the script again, what images it does try to run and what the last thing that it did flash? And it doesn't show any errors? If you see that it doesn't contain certain sig files, that's also normal.
Edit, one other thing. Try downloading the factory image again. Only extract the factory image zip file, don't extract the other zip file you find in it. Then run the flash-all script from within the extracted factory image.

levibuko said:
So I tried it again, I still get some "archive does not contain" errors but after the script ended I was able to get to recovery and factory reset. sadly I still cant boot and I get to the same screen. I dled the factory img from googles webpage so I dont understand why so much files are missing. the scipt also only runs for a few secs.
Click to expand...
Click to collapse
First, the "errors you are seeing about "not containing" are not errors but part of the script. Are you getting to fastbootd after what seemed like a reboot into recovery? Are you doing something there? You shouldn't as it is part of the script that started that way with Android 10. If you watch command prompt, you will see that it is still running and will eventually finish and reboot properly into system. For the Pixel 3 (not 3XL since you are in the P3 forum), you should be using 10.0.0 (QQ1A.191205.008, Dec 2019) https://dl.google.com/dl/android/aos...y-bc480ac4.zip. Be sure to check the SHA-256 of the file before you flash. As for flashing, extract the DL either right into your ADB/Fastboot folder or wherever if you have your PATH set properly. Current platform tools are 29.05 available for Windows at https://dl.google.com/android/reposi...st-windows.zip. Then, just run flash-all from command prompt. The next thing you should see after a fairly lengthy reboot through the G screen is your device ready to be setup with Google.
If you can take some pictures with a camera or something and post, that would help with anything you might be seeing. The other thing you could do since you can get into recovery is to run the actual OTA install. Follow the directions here and use 10.0.0 (QQ1A.191205.008, Dec 2019) https://dl.google.com/dl/android/aos...8-7a817e0d.zip. Same thing about checking the SHA-256.
This last line in your post "the scipt also only runs for a few secs" leads me to believe you are not letting it run through the fastbootd half.

sliding_billy said:
First, the "errors you are seeing about "not containing" are not errors but part of the script. Are you getting to fastbootd after what seemed like a reboot into recovery? Are you doing something there? You shouldn't as it is part of the script that started that way with Android 10. If you watch command prompt, you will see that it is still running and will eventually finish and reboot properly into system. For the Pixel 3 (not 3XL since you are in the P3 forum), you should be using 10.0.0 (QQ1A.191205.008, Dec 2019) https://dl.google.com/dl/android/aos...y-bc480ac4.zip. Be sure to check the SHA-256 of the file before you flash. As for flashing, extract the DL either right into your ADB/Fastboot folder or wherever if you have your PATH set properly. Current platform tools are 29.05 available for Windows at https://dl.google.com/android/reposi...st-windows.zip. Then, just run flash-all from command prompt. The next thing you should see after a fairly lengthy reboot through the G screen is your device ready to be setup with Google.
If you can take some pictures with a camera or something and post, that would help with anything you might be seeing. The other thing you could do since you can get into recovery is to run the actual OTA install. Follow the directions here and use 10.0.0 (QQ1A.191205.008, Dec 2019) https://dl.google.com/dl/android/aos...8-7a817e0d.zip. Same thing about checking the SHA-256.
This last line in your post "the scipt also only runs for a few secs" leads me to believe you are not letting it run through the fastbootd half.
Click to expand...
Click to collapse
Hello,
first of all thank you for the detailed answer!
I did as you told me and got so far:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Another question: I just click on the flash-all script and let it run. do i have to open he power shell in w10 and do it within there?
EDIT: I think I dont know how to properly add images. Phone stays at the fastbootd screen and I get the error fastboot error: command failed.

levibuko said:
Hello,
first of all thank you for the detailed answer!
I did as you told me and got so far:
Another question: I just click on the flash-all script and let it run. do i have to open he power shell in w10 and do it within there?
EDIT: I think I dont know how to properly add images. Phone stays at the fastbootd screen and I get the error fastboot error: command failed.
Click to expand...
Click to collapse
Yes, you need to run it from command prompt or PowerShell. There are some differences between the two, but if you just type cmd in PowerShell, it will put it in command prompt mode. Make sure to hold down shift and right click and open power shell widow from here so that the open directory is in the command line when you run flash-all. Withe a batch file in windows in the actual directory, you can just type run-all with no .bat or .\ or anything. Your pics are not showing, but something like what I am showing. BTW, sideloading the OTA needs done from command prompt as well. Like I said, easy way is just to extract the image into the same directory where you have Platform Tools extracted so you don't need to worry about the path.

levibuko said:
Another question: I just click on the flash-all script and let it run.
Click to expand...
Click to collapse
You should be able to just double click the flash all batch file. You don't need to run it in a power shell. It'll open one up to run the fastboot commands.

sliding_billy said:
Yes, you need to run it from command prompt or PowerShell. There are some differences between the two, but if you just type cmd in PowerShell, it will put it in command prompt mode. Make sure to hold down shift and right click and open power shell widow from here so that the open directory is in the command line when you run flash-all. Withe a batch file in windows in the actual directory, you can just type run-all with no .bat or .\ or anything. Your pics are not showing, but something like what I am showing. BTW, sideloading the OTA needs done from command prompt as well. Like I said, easy way is just to extract the image into the same directory where you have Platform Tools extracted so you don't need to worry about the path.
Click to expand...
Click to collapse
I tried everything exactly the way you told me but its the same result. So I tried sideloading the OTA it switches to the no command error na d I get this:
adb sideload blueline-ota-qq1a.191205.008-7a817e0d.zip
serving: 'blueline-ota-qq1a.191205.008-7a817e0d.zip' (~0%) * failed to read command: No error
Edit: If I try to boot to recovery via combo keys I get the no command with the android logo too. Is my recovery dmged?
If I try to flash teh image I get to fastbooted and from there I can get into recovery mode. I tried OTA again and now I got this error:
>adb sideload blueline-ota-qq1a.191205.008-7a817e0d.zip
serving: 'blueline-ota-qq1a.191205.008-7a817e0d.zip' (~0%) * failed to read command: Invalid argument
and the error when I flash the image:
Resizing 'product_b' OKAY [ 0.007s]
Sending sparse 'product_b' 1/4 (524284 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Press any key to exit...

levibuko said:
I tried everything exactly the way you told me but its the same result. So I tried sideloading the OTA it switches to the no command error na d I get this:
adb sideload blueline-ota-qq1a.191205.008-7a817e0d.zip
serving: 'blueline-ota-qq1a.191205.008-7a817e0d.zip' (~0%) * failed to read command: No error
Edit: If I try to boot to recovery via combo keys I get the no command with the android logo too. Is my recovery dmged?
If I try to flash teh image I get to fastbooted and from there I can get into recovery mode. I tried OTA again and now I got this error:
>adb sideload blueline-ota-qq1a.191205.008-7a817e0d.zip
serving: 'blueline-ota-qq1a.191205.008-7a817e0d.zip' (~0%) * failed to read command: Invalid argument
Click to expand...
Click to collapse
The no command is not recovery yet. You need to do the step listed in the OTA instructions --To access the recovery menu, hold the Power button and press Volume Up once. The recovery text menu will appear. You can't start the sideload from anywhere besides that menu that you seem to not be at yet. I was just about to recommend the OTA sideload since that is a little more reliable. Fastbootd cannot be used for all things. Just start from scratch using the OTA instructions here: https://developers.google.com/android/ota Also, make sure you are getting a 'fastboot devices' devices recognition (for image flash) or an 'adb devices' recognition once in recovery for sideload. Also, be sure to try different cables and ports. Reboot computer, etc to make sure the daemon is completely reset. There is something missing in your steps. Image instructions are here, BTW: https://developers.google.com/android/images. If you can get fastboot devices to recognize the device, you aren't hard bricked. Soft bricked of course, but not hard.
That product error is one that nobody seems to have figured out a reason for. Get yourself to that error, stay connected and in command prompt (I thionk you do have to do a press any key to continue to get back to a prompt once the error happens, but I'm not sure). Just don't close anything. Then do the sideload from fastbootd. Yes, you are using half of the image install and half of the OTA install with different files.