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
Related
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
Hi, I am new to rooting my tablet. I manage to unlock my tablet "asus tf700" but i cannot for the life of me understand how to root this. I have read all the threads/posts regarding this issue but since its my first time i dont understand what "flashing" means or "bootloader". Please any step by step advice is greatly appreciated.
I have the ASUS TF700T Infinity Jellybean Android 4.1.1 I believe it is unlocked because I am able to go into that screen and theres four Icons.
Pms or a step by step guide for this noob because i dont understand any of these terms =(
Sorry for the trouble and thanks in advance
Cheers,
deocare
deocare said:
Hi, I am new to rooting my tablet. I manage to unlock my tablet "asus tf700" but i cannot for the life of me understand how to root this. I have read all the threads/posts regarding this issue but since its my first time i dont understand what "flashing" means or "bootloader". Please any step by step advice is greatly appreciated.
I have the ASUS TF700T Infinity Jellybean Android 4.1.1 I believe it is unlocked because I am able to go into that screen and theres four Icons.
Pms or a step by step guide for this noob because i dont understand any of these terms =(
Sorry for the trouble and thanks in advance
Cheers,
deocare
Click to expand...
Click to collapse
also tried reverting back to ICS to do that auto root but had no idea what "fastlooader" was..
sorry im a total noob at this
deocare said:
also tried reverting back to ICS to do that auto root but had no idea what "fastlooader" was..
sorry im a total noob at this
Click to expand...
Click to collapse
Not too worry, it's very simple, just download the zip, then unzip and double click on the bat file, then follow on screen instruction.
Here is a nice instruction for rooting:
http://tutznet.com/root-tf700t-asus-...-infinity.html
this will work with the specs for my tablet? jellybean etc..?
does not work... i tried this debug already it says failed i think because it doesn't support jellybean.
deocare said:
does not work... i tried this debug already it says failed i think because it doesn't support jellybean.
Click to expand...
Click to collapse
no, it's for ics only, I thought you are on ICS? well you downgrade back to .30 then use my method above, If you don't want to downgrade, then you must unlocked first then follow this method:
http://forum.xda-developers.com/showthread.php?t=1916762
You put your device in fastboot mode, by turn off your device, hold volume down and power button, when you will see white text appeared on the screen release both, hit volume down to navigate to the USB icon, then hit volume up to select and now you are fastboot. plug in your usb cable then open fastboot command on your pc and do your thing.
buhohitr said:
no, it's for ics only, I thought you are on ICS? well you downgrade back to .30 then use my method above, If you don't want to downgrade, then you must unlocked first then follow this method:
http://forum.xda-developers.com/showthread.php?t=1916762
You put your device in fastboot mode, by turn off your device, hold volume down and power button, when you will see white text appeared on the screen release both, hit volume down to navigate to the USB icon, then hit volume up to select and now you are fastboot. plug in your usb cable then open fastboot command on your pc and do your thing.
Click to expand...
Click to collapse
sorry i dont understand that concept of flashing can you go through it with me on how to do it
deocare said:
sorry i dont understand that concept of flashing can you go through it with me on how to do it
Click to expand...
Click to collapse
Not a problem, but I need to verify what your setup first.
1. Are you on Jelly Bean?
2. Are you unlocked? (when you turn on your device, it should displays "device is unlocked"
3. Do you have SDK and fastboot/ADB tool installed on your device?
Once you answered all 3 questions, I will recommend the easiest way to root.
buhohitr said:
Not a problem, but I need to verify what your setup first.
1. Are you on Jelly Bean?
2. Are you unlocked? (when you turn on your device, it should displays "device is unlocked"
3. Do you have SDK and fastboot/ADB tool installed on your device?
Once you answered all 3 questions, I will recommend the easiest way to root.
Click to expand...
Click to collapse
1.yes
2.yes
3. maybe? not sure i have been trying alot of random things trying to root it so im not sure if its installed on my device
deocare said:
1.yes
2.yes
3. maybe? not sure i have been trying alot of random things trying to root it so im not sure if its installed on my device
Click to expand...
Click to collapse
OK, we need to verify if your fastboot is working or not. Put your device in fastboot mode (see my thread above..how to select the usb icon). On your pc, go to the folder that you have fastboot command (should be fastboot.exe). Open window command prompt, navigate to the folder where "fastboot.exe" located (usually located in "platform-tools" folder), then execute this :
type in:
fastboot devices
hti enter, you should be device ID show up
again type:
fastboot reboot
then hit enter
Your device should reboot. If it does, your fastboot is working.
buhohitr said:
OK, we need to verify if your fastboot is working or not. Put your device in fastboot mode (see my thread above..how to select the usb icon). On your pc, go to the folder that you have fastboot command (should be fastboot.exe). Open window command prompt, navigate to the folder where "fastboot.exe" located (usually located in "platform-tools" folder), then execute this :
type in:
fastboot devices
hti enter, you should be device ID show up
again type:
fastboot reboot
then hit enter
Your device should reboot. If it does, your fastboot is working.
Click to expand...
Click to collapse
i dont know where this fastboot.exe is
is there a link i can get it from
deocare said:
i dont know where this fastboot.exe is
is there a link i can get it from
Click to expand...
Click to collapse
Here you go, instruction and fastboot download.
http://forum.xda-developers.com/showpost.php?p=27218675&postcount=20
okay i have no idea it does not work i opend cmd prompt got the bootloader but the commands dont work heres a Screen
{
"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"
}
@deocare
first you have to "cd" into the path wehre you store the fastboot.exe.Ideally you've installed a full android sdk with adb, etc. After setup your android sdk and fastboot, make sure that you're tablet is booted in fastboot mode and you've installed the fastboot drivers, e.g. from universal naked driver package. After this you can send fastboot commands to your tablet but please note that it doesn't answer to fastboot devices.
Here are some threads explaining how to setup fastboot and how to after flashing jellybean, e.g. chainfires SU.
thunderger said:
@deocare
first you have to "cd" into the path wehre you store the fastboot.exe.Ideally you've installed a full android sdk with adb, etc. After setup your android sdk and fastboot, make sure that you're tablet is booted in fastboot mode and you've installed the fastboot drivers, e.g. from universal naked driver package. After this you can send fastboot commands to your tablet but please note that it doesn't answer to fastboot devices.
Here are some threads explaining how to setup fastboot and how to after flashing jellybean, e.g. chainfires SU.
Click to expand...
Click to collapse
I installed the drivers already i believe i checked under portable devices and it says "TF700t transfomer pad.." and I am in booted in fastboot mode with the power+volume down key and went over to the USB icon then opened cmd prompt
deocare said:
I installed the drivers already i believe i checked under portable devices and it says "TF700t transfomer pad.." and I am in booted in fastboot mode with the power+volume down key and went over to the USB icon then opened cmd prompt
Click to expand...
Click to collapse
Based on your screen shot, you put the "fastboot folder" on your desktop. Do this.
open cmd
type:
cd\ then hit enter
you should see:
c:\
now type:
cd users\david\desktop\fastboot then hit enter
you should see
c:\users\david\desktop\fastboot>
now type:
fastboot devices then hit enter
you should see device ID
now type:
fastboot reboot then hit enter
your device should reboot.
buhohitr said:
Based on your screen shot, you put the "fastboot folder" on your desktop. Do this.
open cmd
type:
cd\ then hit enter
you should see:
c:\
now type:
cd users\david\desktop\fastboot then hit enter
you should see
c:\users\david\desktop\fastboot>
now type:
fastboot devices then hit enter
you should see device ID
now type:
fastboot reboot then hit enter
your device should reboot.
Click to expand...
Click to collapse
i am gonna assume it is not installed properly doesn't show devices and it says rebooting but doesn't.
deocare said:
i am gonna assume it is not installed properly doesn't show devices and it says rebooting but doesn't.
Click to expand...
Click to collapse
Do you have your table booted in fastboot mode and usb cable plug into your PC?
i doo
deocare said:
i doo
Click to expand...
Click to collapse
OK, you problably don't have android sdk instalaled. Here is the link to install SDK. When you run the sdk installation, only select anything with android packages and install, don't install everything.
http://forum.xda-developers.com/showthread.php?t=1616059
Another question is are you planing to install custom ROM??? or you just want root?
I have an acer a700,but i updaded to jeally bean,please help me root this device.thanks .
cuibapngo said:
I have an acer a700,but i updaded to jeally bean,please help me root this device.thanks .
Click to expand...
Click to collapse
First I think you need to learn to post in the right section.
Then Learn to READ in the right section!
See it's EasyRoot
Vorbeth said:
First I think you need to learn to post in the right section.
Then Learn to READ in the right section!
See it's EasyRoot
Click to expand...
Click to collapse
So,i just want to root,i҆m happy with romstock,not romcook.i want root to install apps that requires to root such as:titanium back up,root explorer....
Here information my device:
Model number: a700
Android vesion: 4.1.1
Kenel vesion: 3.1.10+
Image vesion: acer av501-pa-a700-rv18rc01-pa-cus1
Build number: 1.502.00-pa-cus1
Image p/n: fm.s1ma0.04a
Is this successful?i҆m newbie,so i҆m a little scared if unsuccessful
Later i want use romcook,still can be up to normal or not?
thanks for bothering you
Sorry my english
cuibapngo said:
So,i just want to root,i҆m happy with romstock,not romcook.i want root to install apps that requires to root such as:titanium back up,root explorer....
Here information my device:
Model number: a700
Android vesion: 4.1.1
Kenel vesion: 3.1.10+
Image vesion: acer av501-pa-a700-rv18rc01-pa-cus1
Build number: 1.502.00-pa-cus1
Image p/n: fm.s1ma0.04a
Is this successful?i҆m newbie,so i҆m a little scared if unsuccessful
Later i want use romcook,still can be up to normal or not?
thanks for bothering you
Sorry my english
Click to expand...
Click to collapse
Just run Vorbeth's EasyRoot. You won't mess anything up.
MD
Moscow Desire said:
Just run Vorbeth's EasyRoot. You won't mess anything up.
MD
Click to expand...
Click to collapse
thank you.i will try: Ngón tay vượt qua:,but please guide supplied by one of the images?because
i may not post new threads, may not post replies, may not post attachments
i may edit my posts: Khóc:
here is one of the questions?
You need:
-Acer Iconia Tab A700 with unlocked bootloader & already be running Jelly Bean(this is whehe i have to download?)
-ClockworkMod Recovery - 6.0.1.5 or newer(i have downloaded 2files.1 is recovery a700 6015. 1 is recovery a700 6015 touch.so spend what?)
Download:
A700 EasyRoot 2.0 md5: 8876aca04e29fe69d7368bc02006359c(there to 12files.down all always?down to set in place?it is not a zip file?
-How to flash:
Download zip and place it on your virtual or external SD card
Boot your phone into ClockworkMod Recovery (via adb or with a key combo)
In main menu, select "install zip from sdcard"
Select "choose zip from sdcard" and browse to the location of zip
After flashing process is complete, reboot the device
Alternative install for Stock patched kernel ONLY:
Reboot to bootloader
Extract boot.img from the zip
Flash boot.img via fastboot
How to get root:
Install SuperSu via CWM
Install BusyBox from Play(these steps can you give me one of the images?)
-Download:
Stock patched kernel md5: 4638ffe2bcb00352ccc702fdfab1d8cb(link die)
iconiaN source built kernel md5: 76b8e1020c6054debedf60efffdca609(link die)
please guide me in detail,thanks for bothering
No one to guide me out?
cuibapngo said:
No one to guide me out?
Click to expand...
Click to collapse
Dude, it's pretty easy.
1. Unlock your bootlooader. To do this, go into tablet /Settings/Development Options and select USB Debugging.
2. Plug your tab into PC (your Acer USB drivers must be installed first)
3. Open a Command Window in the folder you downloaded all those files. (shift & right mouse click)
4. Check to make sure ADB is working by typing adb devices (you should get some numbers) if not, you have a windows driver issue.
5. Type adb reboot bootloader (tab should reboot to bootloader)
6. Type fastboot OEM unlock (you should get a couple of images. One with an unlock, and one with a lock door) Use Vol - to switch between the 2. Use vol + to select. You have to be quick, as it times out after 5 seconds or so.
When you reboot, it should say bootloader version number (unlocked mode) or something similar.
Go back to the Command window, and run the batch file. "easyroot.bat" by typing in easyroot.bat , then hit the Enter button. The batch file should install all you need, You may need to select things that it prompts you for.
No, there's not a video, as it ain't rocket science. If you can't understand these instructions, perhaps it is better if you do not root your tablet. Doing this, is not for everybody.
Also note, once you unlock your bootloader, you can no longer get OTA from Acer. And, once you unlock it, you cannot lock it back. Not without installing a whole new stock rom.
Also, next time, post your questions in the Q&A forum. Otherwise, nobody will answer them.
MD
help me
grigaman said:
Help please. I tried to establish root on the A700 in the second way. But I didn't notice that this way is available for 4.0.4, and on my tablet was established 4.1.1. At me at inclusion gives out here such and more than anything. The debugging mode joins and determined by USB by the computer, but I don't know what to do, prompt please! And still it doesn't load updating with SD the card. And before doing root I unblocked the loader
Click to expand...
Click to collapse
please help me
{
"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"
}
Moscow Desire said:
Dude, it's pretty easy.
1. Unlock your bootlooader. To do this, go into tablet /Settings/Development Options and select USB Debugging.
2. Plug your tab into PC (your Acer USB drivers must be installed first)
3. Open a Command Window in the folder you downloaded all those files. (shift & right mouse click)
4. Check to make sure ADB is working by typing adb devices (you should get some numbers) if not, you have a windows driver issue.
5. Type adb reboot bootloader (tab should reboot to bootloader)
6. Type fastboot OEM unlock (you should get a couple of images. One with an unlock, and one with a lock door) Use Vol - to switch between the 2. Use vol + to select. You have to be quick, as it times out after 5 seconds or so.
When you reboot, it should say bootloader version number (unlocked mode) or something similar.
Go back to the Command window, and run the batch file. "easyroot.bat" by typing in easyroot.bat , then hit the Enter button. The batch file should install all you need, You may need to select things that it prompts you for.
No, there's not a video, as it ain't rocket science. If you can't understand these instructions, perhaps it is better if you do not root your tablet. Doing this, is not for everybody.
Also note, once you unlock your bootloader, you can no longer get OTA from Acer. And, once you unlock it, you cannot lock it back. Not without installing a whole new stock rom.
Also, next time, post your questions in the Q&A forum. Otherwise, nobody will answer them.
MD
Click to expand...
Click to collapse
so,i haved I downloaded the usb driver and sdk on my pc and then
First, i install usb driver.sau I plug my A700 to the PC, I did not see what happened. do not know my tab has been updated to the new driver?
*I download the sdk for it in the c drive (because when I extract it, do not see the files installed)
Unlock Your Bootloader: (codes from alx5962)
1. Open a command prompt in windows and navigate to the directory where adb is stored. For the sake of conversation, I’m going to call it “C:\SDK\platform-tools”
2. Plug your tablet into your computer through USB. It should automatically mount because you’ve installed the Acer USB Drivers and didn’t skip that step above. J
3. At the command prompt, enter the following:
I do not know to type the path to the sdk, it's all wrong! I to the sdk folder in c / program files/adt-bundle-windows-x86 .đặt thư mục sdk ở program files có đúng không?
cuibapngo said:
so,i haved I downloaded the usb driver and sdk on my pc and then
First, i install usb driver.sau I plug my A700 to the PC, I did not see what happened. do not know my tab has been updated to the new driver?
*I download the sdk for it in the c drive (because when I extract it, do not see the files installed)
Unlock Your Bootloader: (codes from alx5962)
1. Open a command prompt in windows and navigate to the directory where adb is stored. For the sake of conversation, I’m going to call it “C:\SDK\platform-tools”
2. Plug your tablet into your computer through USB. It should automatically mount because you’ve installed the Acer USB Drivers and didn’t skip that step above. J
3. At the command prompt, enter the following:
I do not know to type the path to the sdk, it's all wrong! I to the sdk folder in c / program files/adt-bundle-windows-x86 .đặt thư mục sdk ở program files có đúng không?
Click to expand...
Click to collapse
Dude. Why are you messing with the Android SDK? When you mess with the SDK, you also have to install the Java JRE kit as well. Then, you have to modify your PATH and CLASSPATH on windows, or else you'll get the messages you got.
I thought you just wanted to get Root on your tablet. Everything you need is in the package that Vorbeth has for easyRoot. His package contains adb.exe, fastboot.exe, and the windows dll's necessary to do it from the folder you saved them all too. Leave the SDK alone unless you know what you are doing.
Moscow Desire said:
Dude. Why are you messing with the Android SDK? When you mess with the SDK, you also have to install the Java JRE kit as well. Then, you have to modify your PATH and CLASSPATH on windows, or else you'll get the messages you got.
I thought you just wanted to get Root on your tablet. Everything you need is in the package that Vorbeth has for easyRoot. His package contains adb.exe, fastboot.exe, and the windows dll's necessary to do it from the folder you saved them all too. Leave the SDK alone unless you know what you are doing.
Click to expand...
Click to collapse
wow.not need unlock boadloader that still root?thanks.i try.
cuibapngo said:
wow.not need unlock boadloader that still root?thanks.i try.
Click to expand...
Click to collapse
You still have to unlock bootloader.,
But run your commands in the package you downloaded. (adb and fastboot). You don't need the SDK for this.
MD
Moscow Desire said:
You still have to unlock bootloader.,
But run your commands in the package you downloaded. (adb and fastboot). You don't need the SDK for this.
MD
Click to expand...
Click to collapse
xin please guide me add a few more, i open test adb và fastboot is it to open but it running very fast and auto closed back.is it wrong?
so, run easy root first or run adb with fastboot first?
cuibapngo said:
xin please guide me add a few more, i open test adb và fastboot is it to open but it running very fast and auto closed back.is it wrong?
so, run easy root first or run adb with fastboot first?
Click to expand...
Click to collapse
I'm having a little trouble with adb and fastboot.i can not to open it.i open with right click and run as administrator, it runs fast and close automatically. above my tab do not see anything.i`ve tried turning off my the computer and tab and then do it again but still does not work. How can I do?
can i run the easy root without running adb command and fastboot?
at run adb and fastboot commands to shutdown tab? think is not it.
cuibapngo said:
I'm having a little trouble with adb and fastboot.i can not to open it.i open with right click and run as administrator, it runs fast and close automatically. above my tab do not see anything.i`ve tried turning off my the computer and tab and then do it again but still does not work. How can I do?
can i run the easy root without running adb command and fastboot?
at run adb and fastboot commands to shutdown tab? think is not it.
Click to expand...
Click to collapse
You MUST open a CMD (command) Window first.
In the folder you downloaded all the stuff to, find a nice empty place (DO NOT SELECT A FILE),
Hold your SHIFT key, and then do a RIGHT MOUSE CLICK
Then, select Open Command Window
You should have a black window, with the directory path. If you don't, then you have issues with your PC.
Next, (where you see the little flashing curser) type in adb devices then hit ENTER
(make sure the pc recognizes your tablet. You should see something like, killing dameon server :devices attached with several numbers)
Type adb reboot bootloader then hit ENTER
(tab reboots to bootloader)
use your left VOL- key to navigate between locked and unlocked. Use VOL+ to select
Reboot your tab. Should say unlocked mode on boot.
Then go back to that black Command Window, and type in adb devices and hit ENTER (once again, you should see your device like the first time)
Then type in 701easyroot.bat and hit ENTER
Should see some stuff, mostly warnings. But at this point, it will ask you to;
1. Keep your stock Recovery
2. Install the CWM Recovery
if you select 1, program quits, and you can just reboot your tab, because as soon as you ran the bat file, it rooted it.
MD
help!!!!did come here.and began restart my tab and it is the following message:
BOOTLOADER VJB-653B3D3 STARTING USB DOWNLOAD PROTOCOL
it stood like that for 20 minutes without seeing anything like couple of images.....lock or unlock
ell.i fear brick my tab, but luckily I power off and then turn it back to normal
type in 701easyroot.bat or easyroot.bat?
what can i do next?
well well, missing the fastboot oem unlock command to unlock
hen I opened the lock, I run orders easy root.bat.and I choose number 1.My tab runs report success, but I do not see superuser file on my tab?I tested the software files explorer, it says your device is not root?
What do I do next?
help help help!!!!!!!!!
can anyone here help me?MOSCOW DESIRE, where are you?
I tried to go back to work 3 times, but the result is the same.said root successful.including selecting the number 2 to do all over again the next time I do look closely and see the following message:
can not load root / boot.img
and then:
can not load root / recovery.img
I press continue and it indicates a successful root as shown. but there is not anything
what's wrong?
no one to help me?:crying::crying::crying:
{
"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!
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.