Database Info

[Need Serious Quick HELP!!!]One S stuck.on bootup

im on my one s, found out that my volume wasnt working an so i tried to fix it by reflashing the rom, but by accident i did a factory reset and the rom was gone, i already wiped the davlik and all that then i barely remembered that i already deleted the rom (was flashing T-Mobile noble series 7.5 for USA version) so now i tried to reboot the phone and im stuck on the bootup and it stays there for a GOOD while..im freaking out right now, anyway i can still get into the bootloader and fastboot but i cant get the rom back into my phone, i did no back ups and im really scared, if anyone can help it would be totally awesome. And if it helps I used the hasoon toolkit 1.0 to unlock my phone and Paul o Brian method to root it.

search for adb and push.
You schould be able to push the rom zip via ADB onto the sdcard and afterwards you can normaly flash it via cwm recovery

HighRoIIer said:
search for adb and push.
You schould be able to push the rom zip via ADB onto the sdcard and afterwards you can normaly flash it via cwm recovery
Click to expand...
Click to collapse
can you post a link to get it, i'd look through the whole place but i have to get to school and the last weeks of it are keeping me busy..i would really appreciate it if you could find me a link

Nice descriptive title of this thread...
Anyways http://lmgtfy.com/?q=adb+push+rom if youre in a hurry, and http://www.catb.org/~esr/faqs/smart-questions.html for when you have more time again, good luck m8
Sent from my HTC One S using xda premium

any help making this easier, idk what the hell im doing, im just trying to push my rom into the phone, this is confusing, im going insane!!!! ok i need this alittle easier im a noob at this, i got my phone rooted with cwm and i accidentallly erase the rom now im trying to put it back in. is there a certain adb fastboot that im missing cuz i tried it and it gives me the correct prompt file....this is really starting to irritate me, it doesnt even push the rom in......i would really appreciate some step by step process on how to do this today.this is my first phone and i really dont want it to brick at all.

let's assume you have adb and fastboot files on pc, if not you need to either install them to a folder of your choice ie Android or install android sdk and set them up that way:
These are the files that need to be in that folder--
http://dl.dropbox.com/u/28338566/adb_fastboot_win32.zip
but if you have them on pc and can connect phone and open command window, cd to your folder where the adb and fastboot files are, maybe something like cd/ hit enter then cd android/android-sdk-windows/tools, or whatever the path is
when you are there and right after the whatever your path is type adb devices and you should get your phone id #
you can google some of this stuff and see videos
if you can get that far do this: download the same rom to your pc and extract it with winrar. open it and you should see a system.img and boot.img file. copy them to the folder where you have the adb/fastboot files
then after you have the adb devices command recognizing your phone type this:
adb reboot bootloader which will put you into fastboot, to verify that before you proceed you can type fastboot devices and see the phone ID # again--then
fastboot erase system
fastboot erase boot
fastboot -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
not sure if you need fastboot -w since you already wiped userdata
you should then be able to get rom booted back up and reset things up again--then nandroid and you should always have an sdcard bu also
if you don't have a recovery anymore you can fastboot it same way by typing
fastboot flash recovery "exact name of recovery.img"
fastboot reboot
I am no expert and you can research this stuff till you feel comfortable or someone can confirm

Yes still no.luck, I'm still stuck on boot up...
Sent from my YP-G1 using XDA

You seem to be able to use adb from what you post. So
1) Boot the phone into CWM
2) Put the rom into the same folder on your pc as the adb program
3) Open a command prompt on the pc, and navigate to the folder with the rom and adb in it, eg "cd c:\adb"
4) Push the rom to the phone: "adb push rom.zip /mnt/sdcard" (if it doesn't work, try it again and change "mnt/sdcard" to just "sdcard"
5) In CWM, choose flash zip file. The zip file should be in the root of your sd card.

rugmankc said:
let's assume you have adb and fastboot files on pc, if not you need to either install them to a folder of your choice ie Android or install android sdk and set them up that way:
These are the files that need to be in that folder--
http://dl.dropbox.com/u/28338566/adb_fastboot_win32.zip
but if you have them on pc and can connect phone and open command window, cd to your folder where the adb and fastboot files are, maybe something like cd/ hit enter then cd android/android-sdk-windows/tools, or whatever the path is
when you are there and right after the whatever your path is type adb devices and you should get your phone id #
you can google some of this stuff and see videos
if you can get that far do this: download the same rom to your pc and extract it with winrar. open it and you should see a system.img and boot.img file. copy them to the folder where you have the adb/fastboot files
then after you have the adb devices command recognizing your phone type this:
adb reboot bootloader which will put you into fastboot, to verify that before you proceed you can type fastboot devices and see the phone ID # again--then
fastboot erase system
fastboot erase boot
fastboot -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
not sure if you need fastboot -w since you already wiped userdata
you should then be able to get rom booted back up and reset things up again--then nandroid and you should always have an sdcard bu also
if you don't have a recovery anymore you can fastboot it same way by typing
fastboot flash recovery "exact name of recovery.img"
fastboot reboot
I am no expert and you can research this stuff till you feel comfortable or someone can confirm
Click to expand...
Click to collapse
Yea I'm still stuck and after a long time of seeing a couple of people not being able to fix my issue, I'm wondering of someone can confirm if this works or if it's possible to flash a ROM without putting it in the phone just flash it from adb? Been a while since I got on and I'm just gonna dedicated time on fixing my one s.... I really appreciate the feedback
Sent from my YP-G1 using xda app-developers app

Yes you can push it thru adb as mentioned above
i have to call it a nite. Just google pushing a Rom thru adb for more Info if needed
---------- Post added at 05:21 AM ---------- Previous post was at 05:12 AM ----------
You never mentioned just downloading Rom to pc and copying to sd card. Then thru recovery wipe and flash rom.
---------- Post added at 05:26 AM ---------- Previous post was at 05:21 AM ----------
Never mind guess you can't connect phone pc and mount to copy files

This thread show how to ADB push a file to your phone
http://forum.xda-developers.com/showthread.php?p=26430276

Yea I'm gonna try that today but I was wondering if somehow we can make the computer flash it onto the phone for us (you know technology now a days) for situations like this for people who can't get access to their sd cards since the sd cards are non removable and make it a little more simpler to fix phones in this type of situation....just a thought put out there, I'm just thinking alot of things to make situations like this easier for people who are trying to get the best of their phone.
Sent from my samsung galaxy player

leohdz148 said:
Yea I'm gonna try that today but I was wondering if somehow we can make the computer flash it onto the phone for us (you know technology now a days) for situations like this for people who can't get access to their sd cards since the sd cards are non removable and make it a little more simpler to fix phones in this type of situation....just a thought put out there, I'm just thinking alot of things to make situations like this easier for people who are trying to get the best of their phone.
Sent from my samsung galaxy player
Click to expand...
Click to collapse
Yeah with a removable SD card it would have been as easy to just take the sdcard and stick it in the computer.
Just be patient and learn to use adb. In the long run it will make things easier for you. Plus you earn some valuable info and upgrade from noob status.
Good luck!
Sent from my HTC One S using Xparent ICS Tapatalk 2

ok....I will give this a try until I get my phone restored, most of my time is dedicated to my phone. Will update later on on progress
Sent from my samsung galaxy player

Just go on bootloader, install CWM recovery (adb is working on it) and send a rom by adb : adb push rom.zip /sdcard
copy the rom in adb folder first and replace "rom.zip" by the name of your rom.
Next go to recovery and flash your rom !
I already have he same problem like you, I was scared too, but don't panic you can install a rom

Ok I just got my phone back and it gets stuck on the boot on the way to the bootloader I can't get into Fastboot or the recovery, any ideas?
Nvm I got it back now it's only the recovery it goes to right away I try to go into bootloader but it gets stuck.on the HTC boot with red text displaying on it. Ok another thing I got into the bootloader and flashed the stock recovery but it got stuck on the boot again....ok another edit, I got the other recovery flashed but it won't boot into recovery it stays on the boot screen with red text.
Sent from my samsung galaxy player

I get back into the bootloader and flashed the recovery again and then try to go into recovery but it stays stuck On boot up with red text for a little bit then turns off black then turns on again in bootup with red text and stays there, any clues?
Edit: I'm in recovery now but it won't push the ROM and I keep trying but it says
{
"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"
}
Sent from my samsung galaxy player

Not sure what all you have done by now--so--
First off did you unlock again, as HTC may have locked it--even though you have red letters? (You said you just got it back--assume from HTC)
If unlocked confirmed--
Can you turn phone on and have it just boot into the homescreen
If so, can you connect to pc and have phone with usb debugging on and fastboot off (fastboot is under settings/power). Open command window and cd to your adb/fastboot folder and type adb devices then fastboot devices
if they work put latest cwm recovery image in the adb/fastboot folder and flash it by--
type adb reboot bootloader
then fastboot flash recovery recovery.img of course use exact recovery image name
if adb devices and fastboot devices don't work verify your sdk is set up and drivers are installed--
you may have already done this--sorry, just trying to start at the beginning

Ok so I'm at the point where I'm in recovery and the command prompt is open but idk how to do this...some help would sure be nice this is what I get when. I try to push something
Note: I kinda modified the name to just ROM so I won't have to type so much
Sent from my samsung galaxy player

what is x86 Mac? i just do a cd/ [enter] then cd android/android-sdk-windows/tools [enter]. that is my path. If on windows and sdk, you need the environmental variable path set to that path i just typed, or whatever your's is. not sure on a mac.
on windows I use forward slashes--not sure it matters
at the prompt you show type adb devices, if it doesn't come back with # followed by numbers you are not set up with adb, reinstall htc drivers and make sure whatever you are fastbooting, is in your tools folder

[GUIDE] Nexus Player - How to Unlock Bootloader and Root using USB cable

{
"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"
}
Setup, Preparation and Prerequisites
Open command prompt - Press Window Key + R, type in "cmd" (without the quotes), and hit enter.
USB Debugging - On your nexus player go to Settings > About > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enter bootloader mode - Hold the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
Once you are in fastboot mode, the light below nexus player will be blinking constantly. You can verify by using "fastboot devices"
ADB Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components here
Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.
Show File Extensions - Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Backup (Optional) - Unlocking the bootloader will completely wipe all data from the device. This includes apps, settings and even the contents of the internal storage (pictures, music, etc.). Copy all important files off the nexus player onto a PC or upload them to a cloud.
Driver Installation
Go to Device Manager, find the Android device, and select Update Driver Software.
Select Browse my computer for driver software
Select Let me pick from a list of device drivers on my computer
Selecting show all devices
Clicking have disk
Finally selecting Desktop\android-sdk-windows\extras\google\usb_driver\android_winusb.inf as the driver
Alternative you can also download and install the Universal ADB Driver.
Downloads
Root:
Android 7.X:
- Coming Soon-
Android 6.X:
http://cord-cutters.wonderhowto.com/how-to/root-nexus-player-0160218/
http://androidflagship.com/16765-root-nexus-player-android-6-0-marshmallow
Android 5.X:
Download the SuperSU zip below. Extract the zip file and you will have (root.img) to platform-tools folder located on your desktop within the android-sdk-windows folder.
SuperSU (Forum Thread) or SuperSU (Direct link)
Information
Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 2 main steps: Unlocking the Bootloader and Rooting. Each new step relies on the previous step to have been completed, and a basic summary of each part is:
Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the device in future.
Rooting: You can gain root booting up root.img
1. Unlocking Bootloader
Turn the nexus player off. Then go into bootloader mode by holding the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
Plug nexus player into your PC, then open a command prompt window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your nexus player serial number shows up you are good to go and may continue. If the nexus player is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the nexus player has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
OEM unlock twice
Code:
fastboot oem unlock
Code:
fastboot oem unlock
After you have done, please proceed onto the next section of the guide.
2. Installing a Custom Recovery
http://forum.xda-developers.com/nex...recovery-twrp-2-8-6-0-touch-recovery-t3114717
https://twrp.me/devices/asusnexusplayer.html
3. Rooting
Now that your nexus player has an unlocked bootloader, now this step is to gain root
Android 7.X
- coming soon -
Android 6.X
Require: TWRP, Custom boot.img and flashable supersu
(Refer to above link)
Android 5.0
Warning: This rooting guide is for Android 5.X only!
Boot (not flash) the root image which will give you root with the stock ROM
Confirm that you have downloaded the SuperSU zip from the downloads section above and you have extracted it and it is located in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Make sure the nexus player is in bootloader mode
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot boot root.img
This will install SuperSU on your device, once the command has completed continue.
Open SuperSU and update the binaries.
Keep in mind that the first boot may take longer than usual.
Congrats! Your nexus player now has an unlocked bootloader, and is rooted.
==================================================
How to flash factory image for Nexus Player?
1) Download image file for your nexus player - https://developers.google.com/android/nexus/images
2) Boot your Nexus device into fastboot mode.
3) On your computer, use 7zip to extract the .tgz file you downloaded from the Android Developer website. Use 7zip a second time to extract the .tar file you extracted from the .tgz. When you’re done, you should have a folder with several files in it.
4) Copy all of these files and paste them in the platform-tools folder in the Android SDK on your computer. If you followed the above tutorial, this should be under the C drive, then under Program Files (x86) on Windows. Linux users, you know where you put it.
5) If you have not already done so, connect your Nexus device to your computer. ADB and Fastboot commands should already work at this point if you’ve been following along.
There are two flash-all files. If you’re in Windows, you’ll want to double click the one that has the gear logo and says “Windows Batch File” on the right. If you’re on Linux, you’ll want to double click the flash-all.sh.
At this point a box should pop up and you should see the installation taking place. While this is going on, do not unplug your device for any reason. Let it do its thing.
6) Once the installation process as finished, your device will automatically reboot and you can now safely disconnect your device from your computer.
==================================================
Credits:
- Chainfire (SuperSU and Rooting guide)
- Chromium (Easy to understand and detailed guide format)
- DevinWatson (USB driver guide)
- androidauthority (Flash firmware image guide)

Nice guide.
What about installing BusyBox?

I have a USB OTG cable but the adapter is female on the available USB side...I am not sure how to go about connecting my laptop/PC to the NP in order to perform ADB commands. Do I need a special cable or is there another way?

arecad said:
I have a USB OTG cable but the adapter is female on the available USB side...I am not sure how to go about connecting my laptop/PC to the NP in order to perform ADB commands. Do I need a special cable or is there another way?
Click to expand...
Click to collapse
Don't use the USB OTG cable, use a micro USB cable (same kind of cable that comes with android phones)

I cannot believe I missed that, how embarrassing. Thanks for the response, now I can follow this guide. I was thinking too hard about the OTG cable being a necessary piece of the puzzle.

I am able to get to the bootloader with no problems, I've got ADB and Fastboot installed on my PC, as well as the drivers. However ADB doesn't pick up my NexusPlayer even though fastboot does. Thoughts?
See Attachments
EDIT: Nevermind, I was expecting different responses from adb/fastboot. When in the bootloader adb will not confirm a connection, only fastboot. Sorry for being a noob...

xDragonZ said:
1. Unlocking Bootloader
[*] Turn the nexus player off. Then go into bootloader mode by holding the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
[*] Plug nexus player into your PC, then open a command prompt window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
[COLOR="red"]adb devices[/COLOR]
This command will list the connected devices. If your nexus player serial number shows up you are good to go and may continue. If the nexus player is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under adb devices.
Click to expand...
Click to collapse
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?

midnightzak said:
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?
Click to expand...
Click to collapse
AFAIK ADB is for Android, and Fastboot is for bootloader.
But i have the oposite problem. Mine NP is getting recognized useing ADB when normaly booted, but when i am in fastboot mode, fastboot isent working. I get no output when run 'fastboot devivces'. I have both tried to set the NP in fastboot mode by using the hiod button and plug in power, and with adb rebbot bootloader.
Any one have a clue why adb works, but not fastboot?

Double check to see if you have the latest version of fastboot. I have read that if you don't have the most up to date version the NP is not recognized.

Sleeepy2 said:
Double check to see if you have the latest version of fastboot. I have read that if you don't have the most up to date version the NP is not recognized.
Click to expand...
Click to collapse
+1 this.

goxboxlive said:
AFAIK ADB is for Android, and Fastboot is for bootloader.
But i have the oposite problem. Mine NP is getting recognized useing ADB when normaly booted, but when i am in fastboot mode, fastboot isent working. I get no output when run 'fastboot devivces'. I have both tried to set the NP in fastboot mode by using the hiod button and plug in power, and with adb rebbot bootloader.
Any one have a clue why adb works, but not fastboot?
Click to expand...
Click to collapse
Have you re-installed the Google driver when you are booted in the bootloader? The driver needs to install twice: once when booted into Android, and once when booted into the bootloader

ADB fastboot for Mac Quick Question??
Hey guys does anyone have any idea on how this can be done on a Mac....I know I know. When I initially plug in my Nexus player with the micro usb, nothing happens on my mac or the Nexus so i am guessing that the drivers are not installed. How would i go about getting these for the Mac? I have already downloaded the slim version of the ADB and Fastboot files with the platform tools into a folder on my desktop named Andriod, so i have these already. And i know that if you hold the button down on the nexus and plug the power in it brings up the bootloader screen. I just need help with the commands in terminal and where to access the drivers from. Also, on the Nexus the Developer options have already been enabled and USB debugging has been turned on. If anyone can help, It would be much appricated! Just started to use terminal commands so yes i am a noob in this department . Thanks agin in advance.
-Jason

MrBoostinduced said:
Hey guys does anyone have any idea on how this can be done on a Mac....I know I know. When I initially plug in my Nexus player with the micro usb, nothing happens on my mac or the Nexus so i am guessing that the drivers are not installed. How would i go about getting these for the Mac? I have already downloaded the slim version of the ADB and Fastboot files with the platform tools into a folder on my desktop named Andriod, so i have these already. And i know that if you hold the button down on the nexus and plug the power in it brings up the bootloader screen. I just need help with the commands in terminal and where to access the drivers from. Also, on the Nexus the Developer options have already been enabled and USB debugging has been turned on. If anyone can help, It would be much appricated! Just started to use terminal commands so yes i am a noob in this department . Thanks agin in advance.
-Jason
Click to expand...
Click to collapse
http://developer.android.com/sdk/win-usb.html
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. To start developing with your device, read Using Hardware Devices."
http://developer.android.com/tools/device.html

Sleeepy2 said:
http://developer.android.com/sdk/win-usb.html
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. To start developing with your device, read Using Hardware Devices."
http://developer.android.com/tools/device.html
Click to expand...
Click to collapse
Hey Sleepy2, I just did a brief read through and it states this:
Set up your system to detect your device.
If you're developing on Windows, you need to install a USB driver for adb. For an installation guide and links to OEM drivers, see the OEM USB Drivers document.
If you're developing on Mac OS X, it just works. Skip this step.
If that is the case, what would you suggest doing next? Thanks again for helping!

MrBoostinduced said:
Hey Sleepy2, I just did a brief read through and it states this:
Set up your system to detect your device.
If you're developing on Windows, you need to install a USB driver for adb. For an installation guide and links to OEM drivers, see the OEM USB Drivers document.
If you're developing on Mac OS X, it just works. Skip this step.
If that is the case, what would you suggest doing next? Thanks again for helping!
Click to expand...
Click to collapse
Open a terminal, navigate to the directory where you downloaded fastboot and go ahead with the commands shown in the first post. You will probably have to add a "./" in front of the commands given that you are on a mac, e.g.,
Code:
fastboot devices
becomes
Code:
./fastboot devices

I seem to be having the same problem as goxboxlive. I have tried installing the drivers about 100x tried on several computers and rebooted many a time. The only thing I can think of from the posts in here was to update fastboot but I dled the android studio and I would assume that has the latest version in there? Otherwise I couldn't find somewhere to download just fastboot from. Any help or recommendations or where I can dl the latest fastboot?
---------- Post added at 02:28 PM ---------- Previous post was at 01:57 PM ----------
Follow up. Got it to work. In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.

knobbs said:
I seem to be having the same problem as goxboxlive. I have tried installing the drivers about 100x tried on several computers and rebooted many a time. The only thing I can think of from the posts in here was to update fastboot but I dled the android studio and I would assume that has the latest version in there? Otherwise I couldn't find somewhere to download just fastboot from. Any help or recommendations or where I can dl the latest fastboot?
---------- Post added at 02:28 PM ---------- Previous post was at 01:57 PM ----------
Follow up. Got it to work. In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.
Click to expand...
Click to collapse
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7

midnightzak said:
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?
Click to expand...
Click to collapse
knobbs said:
In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.
Click to expand...
Click to collapse
midnightzak said:
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7
Click to expand...
Click to collapse
To avoid further confusion, I've updated the post since the OP hadn't yet.

midnightzak said:
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7
Click to expand...
Click to collapse
efrant said:
To avoid further confusion, I've updated the post since the OP hadn't yet.
Click to expand...
Click to collapse
Thank you, saw your post that time and wanted to change it but keep forgetting.
Currently working on some basic developer app for Nexus Player.

xDragonZ said:
Thank you, saw your post that time and wanted to change it but keep forgetting.
Currently working on some basic developer app for Nexus Player.
Click to expand...
Click to collapse
It's all good, wasn't terrible let to figure out, and if you're developing even more for the Nexus Player, the more power to ya! Keep it up!

Can anyone tell me step-by-step...how can I back-up my android OS + data ?

Gentlemen/ Ladies,
Any Pro here? Can anyone tell me step-by-step...NO-BS...how to back-up my android OS + data, here , please !?
I ran into some difficulties...I am trying to fully backup my Nexus 5 at this stage.
I was told I need a few things, 15-seconds ADB installer, SDK , TWP-3.2.1-1
{
"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"
}
When I typed in DOS, in my computer i got a response:
"adb" is not recognized as in internal or external command operable program or batch file
I am having so much problems with that SDK Android thing, ...Someone here at this forum gave me this :
https://forum.xda-developers.com/go...ide-nexus-5-how-to-unlock-bootloader-t2507905
From the link-ADB and Fastboot Installation
1. Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components(Thanks @El Daddy)
Link removed since it expired
2. Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
3. Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
4. Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
5. To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are ....
What are those SDK Tools/ & Android SDK platform-tools,....? How to get it working for adb error in DOS?
True instructions step by step please.....the above instructions, are no where near from what I saw on screen !
Thank you,

STDupont said:
Gentlemen/ Ladies,
Any Pro here? Can anyone tell me step-by-step...NO-BS...how to back-up my android OS + data, here , please !?
I ran into some difficulties...I am trying to fully backup my Nexus 5 at this stage.
I was told I need a few things, 15-seconds ADB installer, SDK , TWP-3.2.1-1
When I typed in DOS, in my computer i got a response:
"adb" is not recognized as in internal or external command operable program or batch file
I am having so much problems with that SDK Android thing, ...Someone here at this forum gave me this :
https://forum.xda-developers.com/go...ide-nexus-5-how-to-unlock-bootloader-t2507905
From the link-ADB and Fastboot Installation
1. Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components(Thanks @El Daddy)
Link removed since it expired
2. Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
3. Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
4. Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
5. To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are ....
What are those SDK Tools/ & Android SDK platform-tools,....? How to get it working for adb error in DOS?
True instructions step by step please.....the above instructions, are no where near from what I saw on screen !
Thank you,
Click to expand...
Click to collapse
Using TWRP custom recovery is the best option.
I have a N5 also.
Install adb/fastboot on PC, download TWRP for your device in .img format, rename the TWRP file to "recovery.img", place the recovery.img in your fastboot folder on PC, boot your device into fastboot mode, connect your device to PC, open a cmd terminal on PC.
Then type:
fastboot devices
Then press enter, it should return a serial number, then type:
fastboot flash recovery recovery.img
Then press enter, it should flash the recovery, then type:
adb reboot recovery
Then press enter, it should reboot device into TWRP. Then select the "Backup" option in TWRP, on the next screen, select the partitions you want to backup, then swipe the slider, then you'll have a backup of everything you want to backup. To restore the backup, boot into TWRP and select "Restore" then find your backup and restore it.
Side note: after creating the nandroid backup in TWRP, it will store the backup on internal storage, to ensure that the backup does not get lost, corrupted or wiped accidentally, I recommend storing a copy of the backup on PC or some other external storage(flash drive, external hard drive, etc..).
Sent from my LGL84VL using Tapatalk

Droidriven said:
Using TWRP custom recovery is the best option.
I have a N5 also.
Install adb/fastboot on PC, download TWRP for your device in .img format, rename the TWRP file to "recovery.img", place the recovery.img in your fastboot folder on PC, boot your device into fastboot mode, connect your device to PC, open a cmd terminal on PC.
Then type:
fastboot devices
Then press enter, it should return a serial number, then type:
fastboot flash recovery recovery.img
Then press enter, it should flash the recovery, then type:
adb reboot recovery
Then press enter, it should reboot device into TWRP. Then select the "Backup" option in TWRP, on the next screen, select the partitions you want to backup, then swipe the slider, then you'll have a backup of everything you want to backup. To restore the backup, boot into TWRP and select "Restore" then find your backup and restore it.
Side note: after creating the nandroid backup in TWRP, it will store the backup on internal storage, to ensure that the backup does not get lost, corrupted or wiped accidentally, I recommend storing a copy of the backup on PC or some other external storage(flash drive, external hard drive, etc..).
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hello,
Thank you so much for yr reply, I truly appreciated, I MEAN IT !
Just a few things for confirmation:
-"place the recovery.img in your fastboot folder on PC"..........I take it after I download &installation TWRP on my PC, there will be a fastboot folder on my PC, right?
-"Side note: after creating the nandroid backup in TWRP, it will store the backup on internal storage"......
Thank you very much !

STDupont said:
Hello,
Thank you so much for yr reply, I truly appreciated, I MEAN IT !
Just a few things for confirmation:
-"place the recovery.img in your fastboot folder on PC"..........I take it after I download &installation TWRP on my PC, there will be a fastboot folder on my PC, right?
-"Side note: after creating the nandroid backup in TWRP, it will store the backup on internal storage"......
Thank you very much !
Click to expand...
Click to collapse
You will not be installing TWRP on your PC, you will only be downloading the TWRP recovery.img and storing it in your fastboot folder. Renaming the file to "recovery.img" as well as storing it in your fastboot is not "required", but it does simplify things to make it easier. Otherwise, when you type the fastboot command to flash the recovery, you would have to use the specific file name that you downloaded and the exact path to where it is stored on your PC. Renaming the file and storing it in your fastboot folder simplifies the command to
fastboot flash recovery recovery.img
Instead of
fastboot flash recovery (specific name of the file you downloaded)(exact path to the file on your PC)
Whereas renaming to recovery.img and storing in your fastboot folder removes the need to be specific and flashes recovery.img from fastboot folder by default without having to be specific.
When you install adb/fastboot on PC, you will have a fastboot folder. You can get the installer from the link below.
https://androidmtk.com/download-15-seconds-adb-installer
As for the part about TWRP storing the backup on internal. What I mean is, the N5 doesn't have an sdcard slot for external sdcard, this means that TWRP will store the backup that it creates on your internal storage by default, you'll find the backup in your TWRP folder on your phone. Copy it from your TWRP folder on your device and move it to your PC or some other storage location other than on your phone.
Storing backups on internal can be risky, sometimes your device can get corrupted or can even accidentally get wiped for no apparent reason, if either of these issues happens, the data that you had stored on internal will not be accessible, if this happens, you may not be able to restore that backup. To ensure that you don't screw yourself out of being able to use the backup, you can store it on a flashdrive. If your copy on the phone gets corrupted or if your phone gets soft bricked or accidentally wiped, you won't be able use the copy that is on your internal storage in your device. If that happens, you will have to connect the flashdrive to your phone via OTG cable, then you can boot into TWRP and use the restore option, once you have the restore feature open, you can choose which storage you restore from, choose the OTG flashdrive and you can restore the copy that is on the flashdrive instead of the copy that is stored on your phone.
Did you understand that this time?
I also recommend backing up your personal data(such as contacts and photos and such using some other means other than TWRP), then, after flashing your custom ROM, you can restore that personal data back to your phone so that you have it available in your new ROM. You can back your contacts up to Google and your photos to Google Photos or just copy the photos to PC using Windows file manager. Other types of data must be backed up by other means depending on what type of data is in question, such as using adb to backup your apps and app data then using adb to restore your apps and app data.
Sent from my LGL84VL using Tapatalk

Droidriven said:
You will not be installing TWRP on your PC, you will only be downloading the TWRP recovery.img and storing it in your fastboot folder. Renaming the file to "recovery.img" as well as storing it in your fastboot is not "required", but it does simplify things to make it easier. Otherwise, when you type the fastboot command to flash the recovery, you would have to use the specific file name that you downloaded and the exact path to where it is stored on your PC. Renaming the file and storing it in your fastboot folder simplifies the command to
fastboot flash recovery recovery.img
Instead of
fastboot flash recovery (specific name of the file you downloaded)(exact path to the file on your PC)
Whereas renaming to recovery.img and storing in your fastboot folder removes the need to be specific and flashes recovery.img from fastboot folder by default without having to be specific.
When you install adb/fastboot on PC, you will have a fastboot folder. You can get the installer from the link below.
https://androidmtk.com/download-15-seconds-adb-installer
As for the part about TWRP storing the backup on internal. What I mean is, the N5 doesn't have an sdcard slot for external sdcard, this means that TWRP will store the backup that it creates on your internal storage by default, you'll find the backup in your TWRP folder on your phone. Copy it from your TWRP folder on your device and move it to your PC or some other storage location other than on your phone.
Storing backups on internal can be risky, sometimes your device can get corrupted or can even accidentally get wiped for no apparent reason, if either of these issues happens, the data that you had stored on internal will not be accessible, if this happens, you may not be able to restore that backup. To ensure that you don't screw yourself out of being able to use the backup, you can store it on a flashdrive. If your copy on the phone gets corrupted or if your phone gets soft bricked or accidentally wiped, you won't be able use the copy that is on your internal storage in your device. If that happens, you will have to connect the flashdrive to your phone via OTG cable, then you can boot into TWRP and use the restore option, once you have the restore feature open, you can choose which storage you restore from, choose the OTG flashdrive and you can restore the copy that is on the flashdrive instead of the copy that is stored on your phone.
Did you understand that this time?
I also recommend backing up your personal data(such as contacts and photos and such using some other means other than TWRP), then, after flashing your custom ROM, you can restore that personal data back to your phone so that you have it available in your new ROM. You can back your contacts up to Google and your photos to Google Photos or just copy the photos to PC using Windows file manager. Other types of data must be backed up by other means depending on what type of data is in question, such as using and to backup your apps and app data then using adb to restore your apps and app data.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hello,
Yes, I understand and know a few things about Windows OS, but when it comes to Android OS, bootloader, fast boot, TWRP...I am a 101-stupid ! But yes, what you are telling me are very similar to Windows OS backup onto external device, which I need....I am going to do tonight,....if I run into any difficulties, sure will keep you informed,....
Once again, I truly appreciated your help, I MEAN IT !

Droidriven said:
You will not be installing TWRP on your PC, you will only be downloading the TWRP recovery.img and storing it in your fastboot folder. Renaming the file to "recovery.img" as well as storing it in your fastboot is not "required", but it does simplify things to make it easier. Otherwise, when you type the fastboot command to flash the recovery, you would have to use the specific file name that you downloaded and the exact path to where it is stored on your PC. Renaming the file and storing it in your fastboot folder simplifies the command to
fastboot flash recovery recovery.img
Instead of
fastboot flash recovery (specific name of the file you downloaded)(exact path to the file on your PC)
Whereas renaming to recovery.img and storing in your fastboot folder removes the need to be specific and flashes recovery.img from fastboot folder by default without having to be specific.
When you install adb/fastboot on PC, you will have a fastboot folder. You can get the installer from the link below.
https://androidmtk.com/download-15-seconds-adb-installer
As for the part about TWRP storing the backup on internal. What I mean is, the N5 doesn't have an sdcard slot for external sdcard, this means that TWRP will store the backup that it creates on your internal storage by default, you'll find the backup in your TWRP folder on your phone. Copy it from your TWRP folder on your device and move it to your PC or some other storage location other than on your phone.
Storing backups on internal can be risky, sometimes your device can get corrupted or can even accidentally get wiped for no apparent reason, if either of these issues happens, the data that you had stored on internal will not be accessible, if this happens, you may not be able to restore that backup. To ensure that you don't screw yourself out of being able to use the backup, you can store it on a flashdrive. If your copy on the phone gets corrupted or if your phone gets soft bricked or accidentally wiped, you won't be able use the copy that is on your internal storage in your device. If that happens, you will have to connect the flashdrive to your phone via OTG cable, then you can boot into TWRP and use the restore option, once you have the restore feature open, you can choose which storage you restore from, choose the OTG flashdrive and you can restore the copy that is on the flashdrive instead of the copy that is stored on your phone.
Did you understand that this time?
I also recommend backing up your personal data(such as contacts and photos and such using some other means other than TWRP), then, after flashing your custom ROM, you can restore that personal data back to your phone so that you have it available in your new ROM. You can back your contacts up to Google and your photos to Google Photos or just copy the photos to PC using Windows file manager. Other types of data must be backed up by other means depending on what type of data is in question, such as using adb to backup your apps and app data then using adb to restore your apps and app data.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hello,
I am getting the same thing ! I copied that TWRP-3.2-1 Hammerhead, and renamed the copy as you said as recovery.img, and moved it to 15 second ADB installer folder.
Started my phone as you said, also in developer's mode, with USB scanning for device error. Then I tried in Recovery mode, same thing.
Any suggestion ? Was it something I did wrong ?? Million thanks ,

STDupont said:
Hello,
I am getting the same thing ! I copied that TWRP-3.2-1 Hammerhead, and renamed the copy as you said as recovery.img, and moved it to 15 second ADB installer folder.
Started my phone as you said, also in developer's mode, with USB scanning for device error. Then I tried in Recovery mode, same thing.
Any suggestion ? Was it something I did wrong ?? Million thanks ,
Click to expand...
Click to collapse
Did you actually install adb as this thread says to do?
https://forum.xda-developers.com/showthread.php?t=2588979
Once you actually have it installed, open Windows file manager and select your C drive, then you'll see the adb folder instead of a fastboot folder(this folder will have the adb and fastboot .exe files), place the recovery.img in that folder.
On your device, go to system settings>developer options and make sure you have the USB debugging option enabled. If you don't have the developer options setting, go to system settings>about phone, scroll down until you see "build number", tap the build number 10 times quickly until you see a message telling you that you have enabled developer options, then go to developer options and enable USB debugging.
Then open the Windows cmd terminal, boot your device into fastboot mode, connect device to PC, open a Windows cmd terminal, type the command:
fastboot devices
Press enter, if it returns the serial number, you're connected. Then continue with the command:
fastboot flash recovery recovery.img
Then press enter, it should flash the recovery, then type the command:
adb reboot recovery
Press enter and it should reboot the device into TWRP. Then continue on with using the Backup option in TWRP to create your n android backup.
There are plenty of threads here at XDA that completely explain how to flash TWRP via fastboot and plenty of threads here that describe how to create backups using TWRP. Try reading some of those threads and you'll understand it much better and it will probably answer any other questions that you have.
Just do a Google search for:
"How to flash TWRP via fastboot Nexus 5"
Use those instructions.
Then do a Google search for:
"How to create android backup via TWRP"
Those two searches should tell you what you need to know.
If you can't understand these simple instructions that I've given as simple as I can make them or if you can't understand the information that you find with these two searches that I've described, then, you should forget about flashing any kind of ROMs on your device because you'll probably brick your device due to your lack of understanding.
I don't know why you haven't already tried Google searching about this process to understand it. Don't be lazy, do your research.
Sent from my LGL84VL using Tapatalk
---------- Post added at 10:59 PM ---------- Previous post was at 10:31 PM ----------
STDupont said:
Hello,
I am getting the same thing ! I copied that TWRP-3.2-1 Hammerhead, and renamed the copy as you said as recovery.img, and moved it to 15 second ADB installer folder.
Started my phone as you said, also in developer's mode, with USB scanning for device error. Then I tried in Recovery mode, same thing.
Any suggestion ? Was it something I did wrong ?? Million thanks ,
Click to expand...
Click to collapse
One more thing that I forgot to add, you have to unlock your bootloader before you can flash TWRP on the device. To do this, verify that you have enabled the "OEM unlock" option in developer options, then open a Windows cmd terminal and type
fastboot oem unlock
Press enter, it will unlock bootloader but it will also wipe a personal data when you unlock the bootloader so make sure you have your important personal stuff backed up before you unlock the bootloader.
Then you can continue with flashing TWRP.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Did you actually install adb as this thread says to do?
https://forum.xda-developers.com/showthread.php?t=2588979
Once you actually have it installed, open Windows file manager and select your C drive, then you'll see the adb folder instead of a fastboot folder(this folder will have the adb and fastboot .exe files), place the recovery.img in that folder.
On your device, go to system settings>developer options and make sure you have the USB debugging option enabled. If you don't have the developer options setting, go to system settings>about phone, scroll down until you see "build number", tap the build number 10 times quickly until you see a message telling you that you have enabled developer options, then go to developer options and enable USB debugging.
Then open the Windows cmd terminal, boot your device into fastboot mode, connect device to PC, open a Windows cmd terminal, type the command:
fastboot devices
Press enter, if it returns the serial number, you're connected. Then continue with the command:
fastboot flash recovery recovery.img
Then press enter, it should flash the recovery, then type the command:
adb reboot recovery
Press enter and it should reboot the device into TWRP. Then continue on with using the Backup option in TWRP to create your n android backup.
There are plenty of threads here at XDA that completely explain how to flash TWRP via fastboot and plenty of threads here that describe how to create backups using TWRP. Try reading some of those threads and you'll understand it much better and it will probably answer any other questions that you have.
Just do a Google search for:
"How to flash TWRP via fastboot Nexus 5"
Use those instructions.
Then do a Google search for:
"How to create android backup via TWRP"
Those two searches should tell you what you need to know.
If you can't understand these simple instructions that I've given as simple as I can make them or if you can't understand the information that you find with these two searches that I've described, then, you should forget about flashing any kind of ROMs on your device because you'll probably brick your device due to your lack of understanding.
I don't know why you haven't already tried Google searching about this process to understand it. Don't be lazy, do your research.
Sent from my LGL84VL using Tapatalk
---------- Post added at 10:59 PM ---------- Previous post was at 10:31 PM ----------
One more thing that I forgot to add, you have to unlock your bootloader before you can flash TWRP on the device. To do this, verify that you have enabled the "OEM unlock" option in developer options, then open a Windows cmd terminal and type
fastboot oem unlock
Press enter, it will unlock bootloader but it will also wipe a personal data when you unlock the bootloader so make sure you have your important personal stuff backed up before you unlock the bootloader.
Then you can continue with flashing TWRP.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hello,
I have it installed. Actaully I was encountering errors but don't want to waste yr time here either.
I will take a close look of the links you provided. I understood what you said, it makes perfect sense. And I know a lot about Windows OS and other stuff, just NOT Android OS and all these.
I also mentioned the developer's mode was ON and USB error detecting was ON, as well. And you are RIGHT ON, ....
Thanks again,
It just when it comes to execution,

STDupont said:
Hello,
I have it installed. Actaully I was encountering errors but don't want to waste yr time here either.
I will take a close look of the links you provided. I understood what you said, it makes perfect sense. And I know a lot about Windows OS and other stuff, just NOT Android OS and all these.
I also mentioned the developer's mode was ON and USB error detecting was ON, as well. And you are RIGHT ON, ....
Thanks again,
It just when it comes to execution,
Click to expand...
Click to collapse
It takes some getting used to, but with proper research based on your device model number and the thing you want to do on that model, it is easily overcome.
Sent from my LGL84VL using Tapatalk

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.

"Cannot load Android system" after failed update - HELP!

My Android phone (Motorola Edge) can no longer start properly after a failed system update. The message I get is: "Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device."
I've tried restarting it in recovery mode which didn't work. I've read that I may be able to install some software via USB and rescue the system but I have no idea how that's done. I've looked at some different rescue software such as Rescue and Smart Assistant (which would only let me rescue the phone which will erase all data) and Dr.Fone but the reviews aren't convincing and the unofficial software programs generally don't support Motorola phones. Does anyone know how to fix my phone without losing my data?? Any help is much appreciated.
Also; I'm in no way a developer so I need everything explained to me like I'm 12 years old.

hi, kid welcome to xda.
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.

[email protected] said:
hi, kid welcome to xda.
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.
Click to expand...
Click to collapse
Thank you so much for your input. Unfortunately I can't make it work. When I type 'adb devices', I get this text:
List of devices attached
ZY227HQ2BX sideload
I've attached more info. Not sure if this has something to do with "USB debugging"?

all things right,
that sideload appears because you have stock recovery {no need to worry}
you don't need to erase system, (it is like optional)
and the error ANDROID_PRODUCT_OUT....... is because as i said earlier you have to copy the path of the file not file name.
how to copy path of the file ?
well, simple on windows, open the folder in which system file is present. and again open command prompt type (remember to be in fastboot mode in mobile phone)
fastboot flash {drag and drop system file from folder to command prompt}.
it should look like (but not the same, it is an example)
fastboot flash E:/newfolder/nexus/files/system.img
tell me if you face any problem (also include screenshots like you did, great right?)

What file is the system file in this folder?

[email protected] said:
all things right,
that sideload appears because you have stock recovery {no need to worry}
you don't need to erase system, (it is like optional)
and the error ANDROID_PRODUCT_OUT....... is because as i said earlier you have to copy the path of the file not file name.
how to copy path of the file ?
well, simple on windows, open the folder in which system file is present. and again open command prompt type (remember to be in fastboot mode in mobile phone)
fastboot flash {drag and drop system file from folder to command prompt}.
it should look like (but not the same, it is an example)
fastboot flash E:/newfolder/nexus/files/system.img
tell me if you face any problem (also include screenshots like you did, great right?)
Click to expand...
Click to collapse
Hi again, I've spent all weekend trying to figure it out but so far no luck.
I don't know where to find the system file in the folder I downloader (see attached photo in my reply above this). I also tried making a service-batfile with guidance from YouTube but it seems my phone is locked so it doesn't work.

well sorry i was quite busy so i was not able to reply.
first thing first do you need your data
if so boot into twrp. find twrp image for your phone then use command in fastbootmode
fastboot boot and drag and drop twrp file.
after successfully booting into twrp use option to backup and backup your data in any external storage like sd card.
after that run flash all.bat inside your downloaded folder.
i will completely wipe and reinstall your firmware.
then after it again in fastboot mode boot into twrp and restore your backup that's it.

[email protected] said:
well sorry i was quite busy so i was not able to reply.
first thing first do you need your data
if so boot into twrp. find twrp image for your phone then use command in fastbootmode
fastboot boot and drag and drop twrp file.
after successfully booting into twrp use option to backup and backup your data in any external storage like sd card.
after that run flash all.bat inside your downloaded folder.
i will completely wipe and reinstall your firmware.
then after it again in fastboot mode boot into twrp and restore your backup that's it.
Click to expand...
Click to collapse
I tried doing it but no success (I really want to keep my data). See attached photo

bro first try fastboot oem unlock then try this command
note. if some pop up ask to click ok in phone click to conform unlocking phone to flash other files (twrp)

[email protected] said:
bro first try fastboot oem unlock then try this command
note. if some pop up ask to click ok in phone click to conform unlocking phone to flash other files (twrp)
Click to expand...
Click to collapse
I get this message:
(bootloader) usage: fastboot oem unlock < unlock code >
FAILED (remote failure)
finished. total time: 0.061s
Will unlocking the device delete my data?

SirOinksalot said:
I get this message:
(bootloader) usage: fastboot oem unlock < unlock code >
FAILED (remote failure)
finished. total time: 0.061s
Will unlocking the device delete my data?
Click to expand...
Click to collapse
try some windows app to recover it.
sorry unocking will delete data

[email protected] said:
try some windows app to recover it.
sorry unocking will delete data
Click to expand...
Click to collapse
What about your original suggestions - will they not work on a locked device? Fx this:
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.

SirOinksalot said:
What about your original suggestions - will they not work on a locked device? Fx this:
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.
Click to expand...
Click to collapse
it will work but need to be modified as your frimware is different i mean hybrid which does not contain system image.
try to clear caches using fastboot : fastboot clear cache
and try to reboot hope it will work. acctuly i have exams so i am a quite busy now a days sorry

SirOinksalot said:
What about your original suggestions - will they not work on a locked device? Fx this:
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.
Click to expand...
Click to collapse
How did you resolve your issue ?

[email protected] said:
it will work but need to be modified as your frimware is different i mean hybrid which does not contain system image.
try to clear caches using fastboot : fastboot clear cache
and try to reboot hope it will work. acctuly i have exams so i am a quite busy now a days sorry
Click to expand...
Click to collapse
Hello buddy,hope your exams are over and you passed them all with wonderful grades!
I am facving the similar problem and unable to find a solution.Would you mind having a look at this ? Thank you!