Database Info

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

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

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

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

THANK YOU this was very helpfull

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

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

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

So far this is only for Rogers version

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

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

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

Peter said change the file name to CWM

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

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

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

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

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

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

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

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

problem with recovery

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Q] help!!¡!!!!!!root for acer a700

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:

[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!

[GUIDE] Install Android SDK Standalone [ADB][30 Dec 2015]

Android SDK - Powerful tool and easy to set up for use with your Android Device
{
"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"
}
I am putting this together for some who may be confused on how to set this up. I love Android SDK, have been using it for ever and once it is setup, maintenance is extra easy. There are 100 ways to skin a cat with ADB tools and development tools. This is my personal choice, go about it how ever you want. This tool is well maintained and always updated so its a big reason I use it. Great support and a great and powerful tool
Click to expand...
Click to collapse
Part 1. Follow These Steps Below - (Preparation)
Download Links For Tools
1. Java SE Development Kit (JDK)
2. Android SDK Tools Only - Download Only, Do Not Install yet
If You Choose Windows for example
3. Universal ADB Drivers - Instructions Here
Click to expand...
Click to collapse
How to Install and Set-up
1. Install Java SE Development Kit (JDK) from Start Here section if you have not yet
2. Launch Android SDK installer you downloaded up above in Download Links
3. During install - Set Installation Path to
Code:
C:\Android\
4. After Installation is Complete, run SDK Manager.exe
5. Install 5.1.1 and 6.0 since these are the APIs for all current Devices. Should not really see anything less than 5.1.1
Note* - Just put a check box where you see the red circles in the picture. The reason I have Tools (Preview Channel) is because I updated to the 25.0.1 RC2 SDK Tools, however, that is not required. You can choose 24.4.1 and it will be fine. It will say installed where as mine does not in the picture because I chose to use 25.0.1 RC2
6. Let all updates install to completion - This could take a while depending on your internet connection
Click to expand...
Click to collapse
The Computer and Phone are now prepped for you to start the whole ADB Process
Click to expand...
Click to collapse
Part 2. Verifying ADB is set up properly and Working
IMPORTANT - Make sure you have already enabled developer options and USB Debugging or you will not see the below results
1. Open Command Prompt and Change directories to your platform-tools folder. This is where all the adb files are located. See Below
In Command Prompt Type - Refer to Part 3 so you no longer need to Change Directory
Code:
cd c:\Android\platform-tools
2. In Command prompt type
Code:
adb devices
You Should get Prompted to Allow USB debugging - Ignore if You Already Have Done This
3. If your output shows your device attached like below, then you are good to go!!!
and
YOU ARE FINISHED!!! Below is a command to get into the bootloader if interested!! Good Luck
Click to expand...
Click to collapse
Part 3. Environment Variables - No need to Change Directory in Command Prompt Anymore (This is if you want to - Not Required)
1. Press Win+R, then type
Code:
sysdm.cpl
2. Click Advanced Tab
3. Click Environment Variables Button
4. Under System Variables, find Path, click to highlight it and then hit the edit button
Windows 8
Windows 10
5. Go to the end of the Variable Value and add the following exactly as you see it in the code box below
Code:
;C:\Android\platform-tools
Windows 8
Windows 10
6. Click OK to accept the changes you just added
7. Open Command Prompt again to verify by pressing Win+R and type cmd and hit enter
8. Once Command Prompt is open -> Simply type adb devices with your device connected with USB Debugging already enabled
9. If you did everything correctly, there is no need to change paths anymore
Click to expand...
Click to collapse
Getting into the Bootloader
In Command Prompt Type:
Code:
adb reboot bootloader
Thanks To:
@Ashraf - Images used for Environment Variables - Not all were his since the guide was modified
@[B]Snoop05[/B] - ADB Drivers and Fastboot

Reserve if Needed

Thank you so much for this - can i ask what's the size of the SDK manager files which we are supposed to download? For some reason it downloads in 86 kb/s speed (normaly 5-6 mb/s) so I just wanted to know if i'm going to wait a long time

Peccoskaify said:
Thank you so much for this - can i ask what's the size of the SDK manager files which we are supposed to download? For some reason it downloads in 86 kb/s speed (normaly 5-6 mb/s) so I just wanted to know if i'm going to wait a long time
Click to expand...
Click to collapse
Hey the installer size is 145mb. I was able to download it in 15 seconds
Updating sdk manager will take a while. I am not sure of the file size... It will take a while... You only have to do this once. Updates after this will be quick
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Hey the installer size is 145mb. I was able to download it in 15 seconds
Updating sdk manager will take a while. I am not sure of the file size... It will take a while... You only have to do this once. Updates after this will be quick
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
I've tried it many times.... i have enough space on my drive, but everytime i try to download this one and only part, prints out this error message....why do i always have so many problems with it

Peccoskaify said:
I've tried it many times.... i have enough space on mi drive, everytime i try to download this one and only part it prints out this error message....why do i always have to have so many problems with it
Click to expand...
Click to collapse
Lol you and me both bro, but you don't have to install that, that is optional, the rest looks good. You should be able to use it now
Edit: looks like a network issue or the repository is down... That will work itself out.. Right now, it is not required
Sent from my LG-H901 using Tapatalk

This is seriously getting ridicolous - Now everything is downloaded, cmd sees the device I have every stupid thing set-up and still....phone only reboots when i type - adb reboot bootloader -
Shell I record it for you?
Edit:
I did record it -

Peccoskaify said:
This is seriously getting ridicolous - Now everything is downloaded, cmd sees the device I have every stupid thing set-up and still....phone only reboots when i type - adb reboot bootloader -
Shell I record it for you?
Edit:
I did record it -
Click to expand...
Click to collapse
Sounds like your bootloader is borked, you should always be able to get into...Were you able to flash TWRP successfully? Not sure where you went wrong, I would try to push boot.img again, you should have a recovery
Go Here

bdorr1105 said:
Sounds like your bootloader is borked, you should always be able to get into...Were you able to flash TWRP successfully? Not sure where you went wrong, I would try to push boot.img again, you should have a recovery
Go Here
Click to expand...
Click to collapse
I followed steps till the one i got stuck in, so no i did not flash TWRP :/ or anything else. - It's weird that it is broken because it's new phone and i did not do anything to it, expect for right now :/ But sure I'll try

Peccoskaify said:
I followed steps till the one i got stuck in, so no i did not flash TWRP :/ or anything else. - It's weird that it is broken because it's new phone and i did not do anything to it, expect for right now :/ But sure I'll try
Click to expand...
Click to collapse
I think your bootloader may still be locked
Have you done this? Make sure USB Debugging is enabled, OEM Unlock is checked, You are in PTP, type adb devices and verify it sees your device then do the following Next:
nvm edited out got ahead of myself

bdorr1105 said:
I think your bootloader may still be locked
Have you done this? Make sure USB Debugging is enabled, OEM Unlock is checked, You are in PTP, type adb devices and verify it sees your device then do the following Next:
nvm edited out got ahead of myself
Click to expand...
Click to collapse
If you look at the video you can see that i have both on and PTP too - without PTP cmd won't see my device...i think
oh sorry

Peccoskaify said:
If you look at the video you can see that i have both on and PTP too - without PTP cmd won't see my device...i think
oh sorry
Click to expand...
Click to collapse
Have you had any luck?
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Have you had any luck?
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Nope :/

Is there way to flash some LG stock android in my phone so it will have bootloader? :/ - I'm not very good in english so i don't even know what to search for :/

Peccoskaify said:
Is there way to flash some LG stock android in my phone so it will have bootloader? :/ - I'm not very good in english so i don't even know what to search for :/
Click to expand...
Click to collapse
Yea I am looking into it the v10 is hard to find anything
Sent from my LG-H901 using Tapatalk

Peccoskaify said:
Is there way to flash some LG stock android in my phone so it will have bootloader? :/ - I'm not very good in english so i don't even know what to search for :/
Click to expand...
Click to collapse
Ok try this
1. Power phone off
2. Hold volume down and power together 3. Once LG Logo appears, let go of power for 1 second and press power again.. Never let go of volume down
4. Then chose to factory reset
This may resolve the issue so you can retry again
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Ok try this
1. Power phone off
2. Hold volume down and power together 3. Once LG Logo appears, let go of power for 1 second and press power again.. Never let go of volume down
4. Then chose to factory reset
This may resolve the issue so you can retry again
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Did it, nothing changed, is this reason for refund?

Peccoskaify said:
Did it, nothing changed, is this reason for refund?
Click to expand...
Click to collapse
Ok another method
1. Install Terminal Emulator
2. Open the Terminal
3. Type# su
4. Type# reboot-bootloader
This should go straight to the bootloader, if it doesn't, I am at a loss

bdorr1105 said:
Ok another method
1. Install Terminal Emulator
2. Open the Terminal
3. Type# su
4. Type# reboot-bootloader
This should go straight to the bootloader, if it doesn't, I am at a loss
Click to expand...
Click to collapse
I just can't anymore - so far thank you for your help, even though it's never year you are willing to help, not many people would waste time with me

Peccoskaify said:
I just can't anymore - so far thank you for your help, even though it's never year you are willing to help, not many people would waste time with me
Click to expand...
Click to collapse
Thats not correct, su did not work, you should have a # symbol before the command, guess not being rooted doesn't help
edit: connect your phone to the computer and type the same command
I think strangely it is just recognizing adb reboot and omitting the bootloader, so try adb reboot-bootlader when connected to the computer