Database Info

adb reboot download tutorial(Windows)

Okay this is four newbie that can't get there phone into download mode,or if your phone is stuck on the a&tt screen or whatever reason you need to go into download mode
1st thing you are going to need android-sdk if you do not have. You need to put all the files on your C: drive in a folder called android-sdk.There is the link to the sdk site.
http://developer.android.com/sdk/index.html
Step 1 go to setting then to Application I always select mass storage,but i guess ask on connection will work.Then in applications select Development,and them usb debugging.Then plug your phone into your computer
Step 2 open the start window in windows vista and 7 user type cmd into the search.XP you go to run and then type cmd.
Step 3 once inside cmd type cd\ enter.this will bring you to the c drive and should look like this.Now it should look like this.
C:/>
step 4 next type cd then (space) android-sdk\tools\ enter it should look like this.
C:\>cd android-sdk\tools\
Step 5 type adb (space) devices.Now it should look like this.
C:\android-sdk\tools>adb devices
* daemon not running. starting it now on port whatever *
* daemon started successfully *
whatever # your phone is device.
now if it doesn't say this you probably don't have the proper drivers install,but if your are rooted you should.I will include a zip folder anyways.
Step 6 adb (space) reboot (space) download enter.It should look like this.
C:\android-sdk\tools>adb reboot download
After hitting enter your phone will reboot into download mode.
Here is a link for the drivers.
http://www.sendspace.com/file/dbh299
Make sure that you have ADB in the tool folder if not here it is

Actually step 1 would be to enabled usb debugging in settings/applications/development section otherwise none of this will work.
Theres also the adb reboot recovery command.

peachpuff said:
Actually step 1 would be to enabled usb debugging in settings/applications/development section otherwise none of this will work.
Theres also the adb reboot recovery command.
Click to expand...
Click to collapse
Thank dude I always have my phone in debugging i'll edit now

From my experience if you flash a rom it will no longer have usb debugging enabled so if you get boot loop or something adb wont work. I know you don't specifybut I personally have not heard of a device being stuck unless the person was flashing.
This is my captivate. There are many like it buy this one is mine.

You might also consider adding the instructions for adding the tools folder to PATH for those that would use this frequently.

flashman2002 said:
From my experience if you flash a rom it will no longer have usb debugging enabled so if you get boot loop or something adb wont work. I know you don't specifybut I personally have not heard of a device being stuck unless the person was flashing.
This is my captivate. There are many like it buy this one is mine.
Click to expand...
Click to collapse
I have had my phone,Plus my girls virbrant stuck on the att%t screen\t-mobile screen and this as worked for me.I have had a few boot loops, but that was cuz i was changing the framework-res.apk,but was able to go into download mode via the rom I was on. I will look into this and see if i need to update.

Completely unresponsive
I have a galaxy s7 and my phone is completely dead. It does not show up in list of devices connected. I have tried all key combinations to start my phone but it is completely unresponsive. Can anybody help me out please.

Broken screen, need to retrieve files off phone! help please

My screen first cracked and then the LCD completely went now... I have files I need to retrieve off the phone. It is rooted and running some ICS build... I believe the phone is in USB debugging mode, the screen still 'works' I can unlock the phone but nothing is displayed on the screen. Possibly someone could help me out with the adb process for pulling the contents off the /sd
Any help will be GREATLY appreciated, thank you for your time.

ur usb mass storage should still work. can u just plug ur phone to a usb port and get things off the phone ?

As previously stated. I believe the phone was in USB debugging mode. And now the screen is completely black... impossible to navigate to where i need to be.

You'll need adb setup on your computer, and you'll need to cd your way into the folder with adb.exe. Forgive me for hotlinking, but this will make it easier: Download this file, courtesy of NexusSHacks.com (I believe it is Zedomax around here). I would advise to unzip the contents in this file to your C:\Nexus directory, so that adb.exe is at C:\Nexus\adb.exe.
Now, plug in your phone. Open your start menu and search for "cmd" and open up Command Prompt. This is the basic Windows CLI (Command Line Interface).
First, you'll need to open the directory of the Nexus folder you created earlier. To do this, type in the command prompt:
Code:
cd C:\Nexus
Now, you want to make sure adb sees your phone:
Code:
adb devices
The adb service should start and if it sees your phone it will pop up a serial number. If there is no serial number, you can't use adb while inside android and you'll need to tick the option or find an alternative way. Assuming it finds your device, you are good to go.
In order to copy the /sdcard folder of your Nexus S, you will use the pull command. We will throw all of the files into C:\Nexus\sdcard, for reference. So in the command prompt, type:
Code:
adb pull /sdcard .\sdcard
It looks a little confusing but don't stress. Just make sure you type it in exactly (dot, correct slash, etc). This will take a little while since it might transfer up to ~15GB worth. You'll see a new line with "C:\Nexus>" with a flashing cursor when it is done. Then you can view all the contents of your sdcard at C:\Nexus\sdcard and do with them as you please.
Also note, for this you'll need up to ~15GB of free space on your C:\ partition, make sure you have this before you start. Good luck

old post I know, but I just dropped my Samsung Captivate (rooted with debugging on) and internal screen cracked (gorilla glass is perfectly fine!), so I am in the same boat. After DAYS... actually DAYS of trying everything from every forum I FOUND A FIX!!!
Now admittedly, I am unsure which of these two (or both) fixed the issue, but here is what I did:
via Google Play's online "shop", I installed "Auto Mount Your SD Card" by JRTStudio (admittingly, unsure if this did anything as I cannot verify if it installed or anything via the phone)
https://play.google.com/store/apps/...wsMSwxLDEsImNvbS5qcnRzdHVkaW8uYXV0b21vdW50Il0.
then I DL'ed MoboRobo and after a few frustrated phone reboots, usb cable connections and much cursing IT CONNECTED!
http://www.moborobo.com/
I am currently DLing all my files from my broken phone!
I had to pass this along as I said... NOBODY seems to know about this as it has taken me DAYS to do this! Not even ATT (Current carrier) nor Spring (whom I am switching to in a month or so) could help me!

You save my life with that "moborobo". Thank you very much.

Glad I could help!!!

Thanks went to both of u, quit important piece of knowledge.
One question; r u downloading "moborobo" on ur Android, on your pc or on both of them?

just on PC, not needed on the phone unless you want to go via WiFi

Harbb said:
If there is no serial number, you can't use adb while inside android and you'll need to tick the option or find an alternative way.
Click to expand...
Click to collapse
What do you mean by this?
My adb service doesn't detect my phone, I used Droidzone's tutorial. I believe usb debugging needs to be on for adb to work, which in my case is useless cause my screen is broken so can't turn on usb debugging.
This is what happens:
---------------------------
C:\>adb devices
List of devices attached
C:\>
---------------------------
---------- Post added at 11:31 PM ---------- Previous post was at 11:23 PM ----------
^when I say broken, I mean the whole screen is distorted, I cannot see anything

droidoidoid said:
What do you mean by this?
My adb service doesn't detect my phone, I used Droidzone's tutorial. I believe usb debugging needs to be on for adb to work, which in my case is useless cause my screen is broken so can't turn on usb debugging.
This is what happens:
---------------------------
C:\>adb devices
List of devices attached
C:\>
---------------------------
---------- Post added at 11:31 PM ---------- Previous post was at 11:23 PM ----------
^when I say broken, I mean the whole screen is distorted, I cannot see anything
Click to expand...
Click to collapse
Reboot to recovery. Bam, working ADB. You can navigate there pretty easily. Pull battery, then re-insert. VOL + & PWR, two click on VOL -, PWR button once. You're in recovery now.

QtADB also can be used is this case
http://qtadb.wordpress.com/download/

paskalion said:
QtADB also can be used is this case
http://qtadb.wordpress.com/download/
Click to expand...
Click to collapse
No go on this either.
Downloaded QtADB, ran the .exe
Pointed to the folder with the aapt and adb binaries, program opened up
Phone's connected and on (I can hear texts coming through), hit refresh a few times, still not detecting

polobunny said:
Reboot to recovery. Bam, working ADB. You can navigate there pretty easily. Pull battery, then re-insert. VOL + & PWR, two click on VOL -, PWR button once. You're in recovery now.
Click to expand...
Click to collapse
That's a little tough. I'm using a Galaxy S so I'm following instructions for that, but it's hard to know if I'm in recovery mode or not. Since adb doesn't detect the device, it's hard to know whether the phone went into recovery mode, or whether adb is setup correctly. It would be handy for a voice sample to play "recovery mode" once the phone boots into it.

droidoidoid said:
That's a little tough. I'm using a Galaxy S so I'm following instructions for that, but it's hard to know if I'm in recovery mode or not. Since adb doesn't detect the device, it's hard to know whether the phone went into recovery mode, or whether adb is setup correctly. It would be handy for a voice sample to play "recovery mode" once the phone boots into it.
Click to expand...
Click to collapse
You're in the wrong forum, then.
And whether or not adb is installed properly, you would know in your device manager under Windows. Appears as a device.

polobunny said:
You're in the wrong forum, then.
And whether or not adb is installed properly, you would know in your device manager under Windows. Appears as a device.
Click to expand...
Click to collapse
Ok... Galaxy S i9000 stuff goes in the Galaxy S i9000 forum.... that's probably why my other post got deleted! :laugh:
As for adb... it appears as a process in task manager, so it's running - I know that much. It's not appearing as a device in device manager (why would it if it's a process? or are you referring to my phone appearing as a device?)
Only areas I can think of that aren't correct are the environment variable and the way I'm doing recovery mode. Since I can't see the screen, I don't know which one is causing the issue! :crying:

Samsung broken??
Contact this guy in Paris , he's very good and friendly!! he repairs my blue Galaxy S3 in front of me
Tel: 0950 850 500 Direct Technique
repare-galaxy com
don't hesitate to call them because i know their skills and it's very good!!
tell them that u call from Mike ciao guys!!

Problem!
Harbb said:
Code:
adb pull /sdcard .\sdcard
It looks a little confusing but don't stress. Just make sure you type it in exactly (dot, correct slash, etc). This will take a little while since it might transfer up to ~15GB worth. You'll see a new line with "C:\Nexus>" with a flashing cursor when it is done. Then you can view all the contents of your sdcard at C:\Nexus\sdcard and do with them as you please.
Click to expand...
Click to collapse
Hey, I got to this problem and I got stuck. I also have a Nexus S with a cracked screen. When I put in the final phrase into the command window it just told me that 0 filles were pulled! Why didnt it pull my files?
What I am trying to do is get all of my pictures and others off the phone.
Please help!

SkullMblem said:
Hey, I got to this problem and I got stuck. I also have a Nexus S with a cracked screen. When I put in the final phrase into the command window it just told me that 0 filles were pulled! Why didnt it pull my files?
What I am trying to do is get all of my pictures and others off the phone.
Please help!
Click to expand...
Click to collapse
This happened to me as well. You have to make sure that your phone has its sdcard folder mounted. Type "adb shell" to get access to the phones command terminal. Then type in "mount /sdcard" I think, or maybe it was "mount sdcard". Either way will probably work so long as you are in the root directory of the phone. You can navigate around in the phone just like a normal linux terminal. "ls" shows list of files and folders in the current directory, "cd foldername" moves into a folder, "cd ../" moves back, "cd /" goes to root directory, etc. Anyhow, once you have mounted the sdcard, you can type exit to leave the shell terminal, and then issue the command "adb pull /sdcard .\sdcard" to get the files. I had a custom rom image in the root of my sdcard so the move took quite a while ~15 minutes. On success of the pull command you should see a bunch of statuses like:
pull: sdcard/data/somefile -> .\sdcard/data/somefile
pull: sdcard/DCIM/somefile -> .\sdcard/DCIM/somefile
.
.
.
XXXX files pulled. 0 files skipped
(Some more transmission stats)
Hope it works out for who ever reads this.
Side note:
On my phone the screen was smashed. I replaced it and it still would not turn on, but it was still running. I had a rooted phone with CM10 rom on it. ADB debugging was one (if its off your pretty much screwed). I started up the phone, and plugged in the usb cable. I tried to use both adb and fastboot from windows terminal. "fastboot devices" would echo back nothing, and "adb devices" would echo back my phone's device number but state it was offline. So to get it online I did the following:
1.) pull batttery.
2.) boot into bootloader (hold power and volume up) the phone shouldn't vibrate if it does you have just normally powered it on. It took me quite a few times to get this to go into the bootloader. To make sure you get in the bootloader type "fastboot devices". If nothing comes up you not there.
3.) once verified you are in the bootloader you need to go into recover mode. Press volume down twice and then hit power (this would normally move the cursor on your phone down to recovery and select it if you could see whats happening on the screen).
4.) wait a bit for it to load into recovery, try typing "adb devices". You should eventually see you device show up as online. At this point you may enter the shell as above, mount the sdcard, exit the shell and pull your files.
Windows instuctions:
Prerequisites are installing adb.exe and fastboot.exe via installing the Android SDK on your computer. They will show up in the platform-tools folder of the install location. Add that folder to your environmental path variable so you can run the ADB and fastboot commands from any folder. Install the ADB driver for your phone (allows you to issue adb commands to your phone when USB is plugged in) by plugging in your phone and going to device manager, find your phone which should show up as a exclamation point, right click update driver, click "browse...", then "let me pick...", click top entry something like "show all", and then let the list populate. On the left look for "samsung" and then select the first one that is something like "samsung adb driver interface". And you should be good to go.
Sorry for the long winded post, I just like to try and explain as much as possible.

Successfully Recoverd data
Well My Samsung S2's Screen broke down few days ago.. Now i have retrieved the data by following the 2nd method in the following article..! I Hope this works for you aswell...
I can not Post the link here.. PM me if you want the link...!

[Q] [HELP BRICK] power button broken bootloop

nexus s i9023 with ics offical rom rooted and unlocked but power button suddenly stopped working so i flashed a jb volume wake zip to enable this feature but it gave me a bootloop now i cant even recover because of the power button i managed to get in the fastboot mode by putting the battery and quickly press volume up but in fastboot the device is not even detected by the usb (original) i have sdk and usb drivers but the problem is i put my phone in usb its like ive put a potato nothing happens and the sentences usb control init and usb control init end have disappeared in fastboot mode so i cant send commands to the phone through adb is there a way to make my phone detectable although when my phone is in the bootloop process its detected by the computer normally but no response of course.
THANKS in ADVANCE

osos96 said:
nexus s i9023 with ics offical rom rooted and unlocked but power button suddenly stopped working so i flashed a jb volume wake zip to enable this feature but it gave me a bootloop now i cant even recover because of the power button i managed to get in the fastboot mode by putting the battery and quickly press volume up but in fastboot the device is not even detected by the usb (original) i have sdk and usb drivers but the problem is i put my phone in usb its like ive put a potato nothing happens and the sentences usb control init and usb control init end have disappeared in fastboot mode so i cant send commands to the phone through adb is there a way to make my phone detectable although when my phone is in the bootloop process its detected by the computer normally but no response of course.
THANKS in ADVANCE
Click to expand...
Click to collapse
EDIT/UPDATE 1: i managed to get into recovery mode :victory:
HOW? NOTICE: IM NOT RESPONSIBLE FOR ANY DAMAGE OF ANY KINND YOU DO TO YOUR PHONE USE AT YOUR OWN RISK
1. keep phone plugged in usb
2.download SDK Manager from (http://developer.android.com/sdk/index.html)
3.install it in root path in Windows 7>>>>>C:/Users/[yourusername]/SDK
4.boot your phone NORMALLY in boot loop
5.connect your phone in usb if you neglected step one
6.your computer should detect it
7.open command promote (CMD) (shortcut windows flag+R) type cmd
8.a black screen will appear type in it "cd SDK/sdk/platform-tools" and press enter
9.path now should be C:\users\[your user name] \SDK\sdk\platform-tools>adb shell second line [email protected]:/ #
10.now type this (copy and paste is recommended) "mount -o remount,rw -t yaffs2 /system /system"
11.now simply type reboot recovery and your phone should reboot in recovery img
12.wipe factory settings now you should be good

osos96 said:
EDIT/UPDATE 1: i managed to get into recovery mode :victory:
HOW? NOTICE: IM NOT RESPONSIBLE FOR ANY DAMAGE OF ANY KINND YOU DO TO YOUR PHONE USE AT YOUR OWN RISK
1. keep phone plugged in usb
2.download SDK Manager from (http://developer.android.com/sdk/index.html)
3.install it in root path in Windows 7>>>>>C:/Users/[yourusername]/SDK
4.boot your phone NORMALLY in boot loop
5.connect your phone in usb if you neglected step one
6.your computer should detect it
7.open command promote (CMD) (shortcut windows flag+R) type cmd
8.a black screen will appear type in it "cd SDK/sdk/platform-tools" and press enter
9.path now should be C:\users\[your user name] \SDK\sdk\platform-tools>adb shell second line [email protected]:/ #
10.now type this (copy and paste is recommended) "mount -o remount,rw -t yaffs2 /system /system"
11.now simply type reboot recovery and your phone should reboot in recovery img
12.wipe factory settings now you should be good
Click to expand...
Click to collapse
I will try it now! If this works, then you are superman for me :good:
Edit:
1. should I type "adb shell second line [email protected]:/ #" after the new path is set and press enter?
2. if I do it, i always get the message "the command mount is wrong or can not be found"

!Lür said:
I will try it now! If this works, then you are superman for me :good:
Edit:
1. should I type "adb shell second line [email protected]:/ #" after the new path is set and press enter?
2. if I do it, i always get the message "the command mount is wrong or can not be found"
Click to expand...
Click to collapse
Was much easier for me, don´t know why.
Solution for me:
1. Turn device into Bootloop
2. Connect it via USB (PC founds it)
3. type in CMD "adb reboot recovery"
4. device is in recovery
Requirement is a working Android-SDK.

!Lür said:
Was much easier for me, don´t know why.
Solution for me:
1. Turn device into Bootloop
2. Connect it via USB (PC founds it)
3. type in CMD "adb reboot recovery"
4. device is in recovery
Requirement is a working Android-SDK.
Click to expand...
Click to collapse
yup i just made it a step by step tut for noobs and your welcome

Root Nvidia Shield clarification

Hi after reading through the post on GitHub on how to simply root your shield I have a few questions that the tutorial doesn't make clear:
1)There are a ton of files at the top and not sure what to do with them...
2) There is a bit where it explains "On your computer, navigate into the directory containing this file and enter the following command:
fastboot boot zImage_dtb ramfs.img.gz"
But it doesn't say that after you open the directory what you do with it?
Do you keep the window open and that's fine?
Do you type in it's location into command prompt before you type in: fastboot boot zImage_dtb ramfs.img.gz?
Just a bit confused as to what all the files are and where I put them and how they have to be utilised etc
Just need clarification for peace of mind
wanted to post the link but forum won't let me yet

Root explanation
Hi here is the main walkthrough from github but as I said there are a few plot holes for people who are new.
If your SHIELD is already unlocked, you can skip this section.
SHIELD ships with an unlockable bootloader. The bootloader is locked by default, which prevents anyone (including yourself) from booting custom OSes and changing system partitions to potentially obtain extra privileges. This is a significant security feature: in the event that your device gets stolen, an attacker will not be able to retrieve your personal data or use your device if your lock screen has a password set.
By unlocking the bootloader, you allow anyone with physical access to your SHIELD to boot custom images and flash system partitions. This opens the way for an attacker to access your personal information or physically damage your device. For this reason, unlocking the bootloader will erase all your personal data like a factory reset does (so a potential thief cannot get it) and will also void your warranty.
If you know you really, really want to take these risks, here is how you unlock SHIELD's bootloader.
Switch your SHIELD off (long press the NVIDIA logo button and select Power off).
Power your SHIELD on while maintaining the back and home buttons pressed (these are the two buttons that lie under the big NVIDIA-logo button, on its left and right). Release them once you see the bootloader screen.
Connect your SHIELD to your computer using a USB cable.
On your computer, enter the following command:
fastboot oem unlock
This will display the unlock menu. Read the disclaimer and think one last time about what you are doing. This is your last chance to stop.
Use the back and home buttons to select your option. If you decide to continue, select Unlock and press the NVIDIA-logo button to validate. Your personal data will be erased and your device marked as warranty-void permanently.
Regardless of your choice, you will be back to the bootloader screen. Using the same buttons, navigate to Poweroff and select this to power your SHIELD off.
Rooting SHIELD
Now your bootloader is unlocked, but you still don't have root access. For this, we need to install SuperSU, and we will do so by booting a custom Linux image that will do this for us.
Power your SHIELD on while maintaining the back and home buttons pressed (these are the two buttons that lie under the big NVIDIA-logo button, on its left and right). Release them once you see the bootloader screen.
Connect your SHIELD to your computer using a USB cable
On your computer, navigate into the directory containing this file and enter the following command:
fastboot boot zImage_dtb ramfs.img.gz
The kernel and ramdisk will be downloaded and started. You will see 4 penguins on your screen, and the message ROOTING SHIELD will appear. Shortly after, your device will reboot. Congratulations, you are rooted!
For some unknown reason USB debugging in Developer options might become unchecked after rooting. You will need to re-check it if you want to use ADB.
It is safe to perform the rooting operation as many times as you want (e.g. after an OTA). Your user data will not be erased by rooting itself, it is the act of unlocking the bootloader that does.
Is there anyone who can add a little to this to make it more simple for a noob like me?
I understand there is a file set that is at the top of the page and I downloaded the files which include zImage_dtb ramfs.img.gz
but don't know how to utilise them etc
There are no videos on youtube of how to do it and if anyone can add just a few more steps so that I know where I'm going with this (don't want to brick my system).
I just want controller support installed like Tincore or gamekeyboard so I can unlock the potential of the games library on GooglePlay.
Thanks for reading.

you copy those two files "zImage_dtb" & "ramfs.img.gz" to the same directory your adb and fastboot executeables are (same directory you issued the oem unlock command from)
then navigate to the same directory you did the oem unlock from via command line then issue the command "fastboot boot zImage_dtb ramfs.img.gz"
it's pretty simple but I can run you through a simple example of what I did
1)download android sdk
2)copy platform tools folder to a directory on c drive (exp c:\tools\ )
3)copy the 2 files above to the same folder along with cwm recovery(optional)
4)boot shield into fastboot mode (home+back+power)
5)navigate to the folder with adb, fastboot, and the above files in it.
Code:
cd c:\tools
6)detect if fastboot driver is installed with "fastboot devices" if result, then continue, if no result, then check if correct driver and check connection
7)issue oem unlock command and follow the onscreen prompts
Code:
fastboot oem unlock
8)restart device, after a full boot cycle(wipes data), power back into fastboot
9)issue the "rooting image" command, device with automatically reboot
Code:
fastboot boot zImage_dtb ramfs.img.gz
*10) optionally reboot back into fastboot and install cwm recovery
Code:
fastboot flash recovery recovery.img
pretty simple

thanks for fast reply.
Ok so I have Two different versions of Android SDK (32 bit and 64 bit) which one do I use?
"copy platform tools to a directory on C drive (exp C:\TOOLS\)"
What are platform tools?
"copy the two files above to the same folder along with cwm recovery"
What two files? do you mean the zImage_dtb and ramfs.img.gz? Do they go into the C:\TOOLS\ folder?
"navigate to the folder with adb, fastboot, and the above files in it"
What do you mean by navigate? Do you simply mean open the folder or do I use a program to do this?
"Detect if fastboot driver is installed with "fastboot devices" if result, then continue, if no result, then check if correct driver and check connection"
What's fastboot devices? What does result and no result mean? What does Check driver and check connection mean? how dod I do that?
I'm confused by all the lingo, what applications I should be using and when exactly do I start using command lines etc
Thanks for help so far been great but I need step by step instructions eg
open folder, copy and paste file1 and file 2 to this folder
open application X
click import file 1 and file 2
type XXXXXX\root\cdrive into command
press enter
see?
I do not know what some of the words mean and how to do some of the stuff the tutorial says. It's jargon and I have all these files, in all these folders with no idea how to do this from start to finish.
Appreciate the help so far but you are dealing with a novice. I know the work won't take long but I need all the relevant info, in one list, with consistent language to ensure I do everything as it should be done.
Bless you sir and...
Good luck

If your confused by my instructions you need to wait for a "one click" installer, sorry.

gogul1 said:
Ok so I have Two different versions of Android SDK (32 bit and 64 bit) which one do I use?
"copy platform tools to a directory on C drive (exp C:\TOOLS\)"
What are platform tools?
"copy the two files above to the same folder along with cwm recovery"
What two files? do you mean the zImage_dtb and ramfs.img.gz? Do they go into the C:\TOOLS\ folder?
"navigate to the folder with adb, fastboot, and the above files in it"
What do you mean by navigate? Do you simply mean open the folder or do I use a program to do this?
"Detect if fastboot driver is installed with "fastboot devices" if result, then continue, if no result, then check if correct driver and check connection"
What's fastboot devices? What does result and no result mean? What does Check driver and check connection mean? how dod I do that?
I'm confused by all the lingo, what applications I should be using and when exactly do I start using command lines etc
Thanks for help so far been great but I need step by step instructions eg
open folder, copy and paste file1 and file 2 to this folder
open application X
click import file 1 and file 2
type XXXXXX\root\cdrive into command
press enter
see?
I do not know what some of the words mean and how to do some of the stuff the tutorial says. It's jargon and I have all these files, in all these folders with no idea how to do this from start to finish.
Appreciate the help so far but you are dealing with a novice. I know the work won't take long but I need all the relevant info, in one list, with consistent language to ensure I do everything as it should be done.
Bless you sir and...
Good luck
Click to expand...
Click to collapse
Step by step instructions like that would take quite a long time to write. Its basically assumed that navigate is a straight forward instruction, namely, open My Computer, click C:\, click something else, etc etc. 32 bit vs 64 bit, again, you should know what your computer is running and use the correct one respectively.
The reason they dont issue novice instructions is for 1 reason only. People who such as yourself claim to not understand the "jargon" are also those who are more likely to make a mistake when rooting. This can lead to a completely bricked device, ie one that will no longer turn on and load up android, totally dead device. As far as the manufacturer is concerned, a bricked device unless bricked by one of their own updates on a non rooted shield installed correctly, is not covered by warranty. This leads said novice to accuse the tutorial writer of having something wrong in the tutorial when in reality they have clicked the wrong thing etc.
Either way, end result: dead device.
Rooting is not aimed at the novice. It is aimed at the advanced user.

Thank you
I understand that and appreciate the explanation. I can work my laptop and I know that my laptop is 32bit or 64bit but it did not say at any point that it was referring to my computer. It just said download the 32 or 64 bit version. Well I have to make sure what they are talking about before I go and try to root my device as I like clarification on everything I do so that I get it right (and don't brick it). At the moment the explanations are all over the place, some info here, another bit there and was hoping somebody could link it all for me and make sense of the order in which I would do things. I have installed graphic cards in my laptop, put custom firmware on to ipods, psp's, computer etc but this is my first foray into android territory and would like to get it right. I am trying to follow a video tutorial but my computer's reaction to driver updates for the ADB/Fastboot drivers is telling me my drivers are up to date and I'm not getting the error message his is. This means I'm not sure where to go as the situation is diffferent s He is trying to get motochopper working for shield so it will root the device and hoped it would do the same for me.
Hopefully some clarification will come sooner rather than later but won't venture fourth until I'm absolutely sure of what needs to be done.
Again, thanks for the help it is appreciated.:laugh:

Sorry for being so abrupt, it wasn't my intension, you are trying to learn. I will not give a step by step which I feel would be the best, yet potentially more dangerous option for you though.
The parts written in the "code" blocks are what you copy and paste into the command line. When I say navigate I mean by changing directory via command line. You can copy files with a graphical file manager as it's quicker but navigate could also mean graphically.
Google search how to tell if you are running 32 or 64 bit windows, there are better guides and videos than I would be able to describe in a few lines. I was assuming you had already unlocked your bootloader as it is required before root, I covered it as point of reference only.
Platform tools is a folder in the SDK, if you install the SDK you will see that folder where you install it.
Fastboot is the utility also in the SDK that you run from command line that's in the code blocks I posted. If you run the command it will either give a result saying a device is detected or it won't show anything (no result) and you have an issue. If you have a driver issue then that's a whole other problem with a specific forum topic for, but I also assumed you unlocked your bootloader which would require you have fastboot and driver issue resolved.
Main cause of my snappiness is it says the requirement (first line of what you quoted) is unlocked bootloader and you are asking questions about rooting (step two after unlocking bootloader) didn't realize you were stuck in step 0, trying to figure out where to start.

gogul1 said:
I understand that and appreciate the explanation. I can work my laptop and I know that my laptop is 32bit or 64bit but it did not say at any point that it was referring to my computer. It just said download the 32 or 64 bit version. Well I have to make sure what they are talking about before I go and try to root my device as I like clarification on everything I do so that I get it right (and don't brick it). At the moment the explanations are all over the place, some info here, another bit there and was hoping somebody could link it all for me and make sense of the order in which I would do things. I have installed graphic cards in my laptop, put custom firmware on to ipods, psp's, computer etc but this is my first foray into android territory and would like to get it right. I am trying to follow a video tutorial but my computer's reaction to driver updates for the ADB/Fastboot drivers is telling me my drivers are up to date and I'm not getting the error message his is. This means I'm not sure where to go as the situation is diffferent s He is trying to get motochopper working for shield so it will root the device and hoped it would do the same for me.
Hopefully some clarification will come sooner rather than later but won't venture fourth until I'm absolutely sure of what needs to be done.
Again, thanks for the help it is appreciated.:laugh:
Click to expand...
Click to collapse
Download 64 bit software for 64 bit windows and 32 bit on 32 bit windows. Only notable exceptions are where a guide explicitly says to get 32 bit for some particular reason (in my case the only time I have come across this is MSI afterburners screen recording facilities only functioning on a 32 bit program for some reason, no 64 bit version) or if you are running 32 bit windows and physically cannot run 64 bit software even though a guide says "use 64 bit java etc etc".
rather interested in installing a graphics card in a laptop seeming as laptops use graphics cards that are soldered down to the motherboard not on a seperate removable card in all with very few (but existant) exceptions.... I think asus, dell and someone else did offer them at one point, its actually what the MXM connector was invented for (but its used for a few other things now instead).
Anyway. Its always good to have clarification. I think the post above me gives a few starting points and as always: google is your friend (so are bing and yahoo, but they are those friends where once you leave your job or school or whatever you probably wont ever see again).

boot achieved
I boot loaded the Shield through dab and boot loader.
Shield restarted once I chose to unlock the shield. I lost all my stuff (as expected) and it restarted. The drivers then reinstalled on my laptop.
I restarted my laptop and the shield again and tried to reinstall the drivers that were made for the ADB but sadly I get this message now...
"Windows has determined that your driver software is up to date MTP USB DEVICE"
So I restarted everything and the device is now showing up in the Andriod Device driver list.
I am using minimal adb and Fastboot application. It opens the command menu
I type in
adb reboot bootloader and I get the reply "error:device not found"
any ideas?
Sigh!

gogul1 said:
I boot loaded the Shield through dab and boot loader.
Shield restarted once I chose to unlock the shield. I lost all my stuff (as expected) and it restarted. The drivers then reinstalled on my laptop.
I restarted my laptop and the shield again and tried to reinstall the drivers that were made for the ADB but sadly I get this message now...
"Windows has determined that your driver software is up to date MTP USB DEVICE"
So the shield is now showing up in my computer manager under Portable Devices and not under the Android Devices like it did when I installed the custom drivers the first time.
Will this be an issue when I come to root?
Sigh!
Click to expand...
Click to collapse
the MTP driver is for plugging the shield in and viewing the file system. If the device isn't under android devices in device manager then you may need to reinstall the ADB drivers or just double check that the ADB can see the device (it may).
Open a command prompt. type "cd [path to the android sdk]\platform-tools"
Then type "adb devices".
It should list all the android devices it can make a debug connection to. If the Shield is in that list your good, otherwise don't proceed any further until you can rectify that.
The other solution is that you dont need ADB drivers on a linux system for some reason. Don't ask why. I havent a clue. But that would necessitate installing linux.
And something that is useful for finding the adb on the command line again in future for windows. You don't want to "cd" into the correct folder every time (the command line equivalent of opening folders). Sometimes you just want to be able to open the command prompt, type "adb devices" and it to just work. That's doable by altering your system PATH variable.
Open my computer. Right click > Properties, should open the System window.
Left side there should be a button saying "Advanced system settings".
It will open the "System Properties" window to the "Advanced" tab (if it isnt on that tab just switch).
Bottom of the window should be a button saying "Environment Variables...". Click it.
Now the window that appears will be split in 2. User variables and System variables. There is a PATH entry in both, it is best that you only change 1. If you are the only user or you only want your user to be able to access the adb, you can change the User variable. Otherwise you can change the system variable for the adb to work on all users. For me I had to add python to my path once but I wanted to do this for all users so I changed the system one, the PSP SDK I installed however altered the User variable by default. Make your choice and find the variable "PATH" in either one.
Click Edit. A window will appear with Variable name and Variable Value. At this point what I recommend doing is copying the entire contents of value into a notepad file and saving them as a backup. Then cancel and go back into it.
Code:
C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Lua\5.1;C:\Program Files (x86)\Lua\5.1\clibs;C:\Python27;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\
That is my Path variable.If you look the path variable is mostly a series of filepaths (or other variables too) which are seperated with ";". When you type a command such as "adb" into a command prompt what windows does is searches the current command prompt directory for a file it can execute which is called "adb" (it ignores extensions unless explicitly given one), if it doesnt find it in the current directory it searches each folder in the system path variable for the same executable (it ignores sub directories, it will only search the folders above on my system). So if we want to be able to type adb from any folder, we need the folder the adb is in to be added to the system path variable.
Simply add this to the end of it
Code:
;[whatever the path to the adb folder on your system is]
It will be whatever you had to add after "cd" to get to the adb earlier (must not leave out the C:\Users etc etc if its stored in your documents, cd will let you get away with ignoring that, the variable requires the FULL filepath).
Save the variable. Open a command prompt. Type adb, should work. If not, QUICKLY RESTORE THE BACKUP BEFORE WORKING OUT WHAT WENT WRONG. Should be safe with the broken variable to be fair, but you don't want to risk anything. If you dont think your going to use the adb often then simply dont bother updating the path variable rather than taking the (minimal) risk.
Wow my path variable is beginning to get a bit long now I only manually added python and lua to it. The rest will be the default entries and the SQL server stuff appears to be from installing visual studio. Yours probably wont match.

hehe you're going to hit me in a minute...
message deleted as I was being a moron....

ok I should be entirely clear as you guys are trying to help
ok I should be entirely clear as you guys are trying to help me so it's best i let you know what I have done up until this point.
Ok so I boot loader my shield.
I downloaded minimal ADB and Fastboot. I also downloaded the drivers you recommended in the forum.
I installed the drivers:
My shield showed up in the computer Manage list as a Portable device.
I chose to install the new drivers, it asked if I still wanted to go ahead as the drivers could not be verified and I said yes.
The drivers installed and the Shield changed from being in the portable list to showing up as an Android device.
Success I believe.
I then opened ADB BOOTLOADER and booted my Shield Manually.
I then typed in the relevant prompts in the command and a list of options showed up on the shield.
It showed my device number in the command prompt which was the one on my shield screen.
I then command the unlock function and the shield offered me the option to lock or unlock.
I chose Unlock and it then rebooted.
When it restarted, my computer reinstalled the device drivers and my shield had reset to factory settings (as it should).
I then looked in the Computer Manage list and my Shield had reverted back to being in the Portable Devices list.
I restarted both again and the Shield then showed up under Android Devices like it did when I installed the custom drivers the first time.
But the name of the device is Nvidia Shield - not Nvidia Shield ADB like in the tutorial video... not sure it that helps.
I enabled USB Debugging,
put the Superuser.apk and Su bin file into the minimal AADB and Bootloader folder.
I then put the Thor-insecure-boot.img in the Minimal ADB and Bootloader folder too.
I started up the command prompt from the minimal ADB and Bootloader.
I then saw this
C:\Program files <X86>\Minimal ADB and Fastboot>
I then typed in adb reboot boot loader and pressed enter
I got
error: device not found
So I decided to take the above advice and opened a command prompt
I typed in cd C:\tools\adt-bundle-windows-x86_64-20130729\sdk\platform-tools
and pressed enter:
It repeated what I typed and I then put in adb devices.
It then came back with:
List of Devices attached
but nothing was listed....
doh!

Progress!
Ok so I uninstalled my drivers to start again, plugged in the shield and it reinstalled my drivers and now under Android Devices it shows NVIDIA SHIELD ADB
Result!
Now I opened the dab cmd prompt
typed in
adb reboot fastboot
and it booted my shield! jolly good
But then I typed in
fastboot boot thor-insecure-boot.img
I then had
<waiting for device>
show up in the command window.
This is where it stayed.
On the screen of my shield I have options:
continue
restart bootloader
recovery mode
poweroff
Do I have to choose one of these in order for it to begin the thor img command?

C:\tools\adt-bundle-windows-x86_64-20130729\sdk\platform-tools Just incase you didnt get it earlier. That would be the path required for the variable change above. Just whack a ; on the end of the existing variable and throw that new path on the end and done.
But yes, adb devices not listing shield is not a good thing. Try reinstalling the ADB driver for the shield manually (you cant do it via device manager etc).

cool
I'm past that and now <waiting for device> problem to rectify. Am looking online now but there isn't much on there so far...
looking under device manager it shows up under Android Device as Nvidia Shield ADB but it also shows up under portable devices as SHIELD.
Whilst in boot mode the device only shows up in portable devices with a exclamation mark next to the device.
*UPDATE*
I uninstalled the portable device driver because I think it may have been causing confusion.
I then typed adb devices into CMD and a list of devices showed the serial number of the nvidia Shield.
I then typed in adb reboot bootloader in and it booted.
I then tried adb devices again and nothing showed up.
When I go into bootloader The Android Device: Nvidia Shield ADB driver disappears in manager once I go into bootloader mode. Is this normal?
Hmmmmmmm
definetly something to do with the drivers.
I'm on windows 7 64bit by the way.
Going back into device manager I noticed that there is another device under Other devices, upon looking at it it is Fastboot and has an exclamation mark in a yellow triangle next to it (Minimal dab and fast boot is open though).
Such a bummer as I'm so close yet so far

picture
ok so here is a pic of my devices list fastboot is there

before boot
This is the devices it can see before I put the shield in boot mode

devices seen after shielf in boot mode
the are the devices seen after I put the Shield in boot mode. It can't see any devices

waiting for devices
This is the screen on the shield in boot mode. The CMD screen says "Waiting for Devices"

[ROOT] Coolad Modena 2 / Sky 2 (E502)

Recently, I successfully ported TWRP from Coolpad Note 3 Lite to Modena 2. After testing, everything works fine, on both devices. Since this device has locked bootloader, we need to bypass this by enabling fastmmi mode and factory mode to enable temporary root access and make initial backup and flashing. So, let´s get started.
Remember to read this post carefully. I am not resposible for any damage to your device. If you brick your device while flashing the TWRP you can *almost* always recover it using SP Flash Tool and YGDP Tool
IF YOU ACCIDENTALY BRICK YOUR DEVICE AND YOU WANT TO FLASH IT VIA SPFT, DO NOT FORMAT THE DEVICE IN SPFT!!! If you´ll format partitions in TWRP, that´s fine, but don´t do FORMAT ALL + DOWNLOAD or FIRMWARE UPGRADE! This will brick your device, like mine This tutorial will not (hopefully) brick it, but just in case something goes wrong, now you know what not to do.
Preparing the environment on your computer
Windows
Download ADB and Fastboot from this link
Open it
Install it system-wide
Also, install the drivers
GNU/Linux (Ubuntu / Debian based distros)
Open terminal
Type "sudo apt install adb fastboot libusb-dev" without the quotes (")
Other things, that are required
Since the file size of the recovery exceeds the maximum 8MB of allowed upload size, you can download it from DataFileHost.
Preparing the device
First, you need to remeber that this could render your device unbootable and will void warranty.
Enable developer options
Go to Settings -> About phone
Tap the build number 7 times
Go back
Go to Developer options
Make sure OEM unlocking and USB Debugging is enabled
Enabling factory mode
Open dialer app
Dial *#9527*#
Click on "DM"
You will be prompted to insert RD personnel password. Enter: 54321
Click cancel button
DM button should change colour to RED
Exit the app by clicking home button
Installing and setting up openrp app
Open terminal / command prompt
Type:
Code:
adb start-server
Type:
Code:
adb devices
Now, click on your phone allow debugging and make sure to tick the radiobutton to remember / always trust this computer
Type:
Code:
adb install
Press spacebar after the install word and drag and drop the downloaded openrp.apk file to terminal
Hit enter
After it´s done, type:
Code:
adb shell monkey -p com.yulong.openrp -v 500
Now, the fun part. ROOTING the device
But before that, BACKUP
Now, keep your phone plugged in, and do a normal reboot by pressing and holding the power button and clicking reboot
When it vibrates, press and hold the Volume down key (Vol-)
You will see these lines on the screen:
Code:
=>[Factory mode]
Code:
=>VolumeDown key is pressed
Code:
=>[fastmmi mode]
After that, you´ll see the LED turns green and "Up Down" text on the screen
Now, back to your computer, type in the command prompt
Code:
adb devices
You should see XXXXXXXXXXXXXX device listed (where XXXX... is the serial number)
Type in the command prompt:
Code:
adb shell dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery of=/storage/self/primary/stock_recovery.img
and
Code:
adb shell dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot of=/storage/self/primary/stock_bootimg.img
Flashing the TWRP Image
Type in the command prompt:
Code:
adb push (drag and drop the recovery image file here, like you did with the openrp.apk file) /storage/self/primary/
Type:
Code:
adb reboot
Press and hold VolumeDown key (Vol-) to boot to fastmmi mode
Type:
Code:
adb shell dd if=/storage/self/primary/recovery_twrp_e502.img of=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery
Type
Code:
adb reboot
Press and hold the VolumeUp key (Vol+) to boot into recovery. If you see white screen with "Recovery" text in it, congrats. Everything is working. If not, try again.
Flashing the SuperSU package
Download the zip from SuperSU website
Copy the zip over to the device, with TWRP running
In TWRP, click install, click the zip and confirm the installation.
Factory reset is not required, but you should at least wipe the cache
If this post was useful for you, hit the thanks button

RESERVED

Hi i have a problem here. at the part to drag and drop the openrp file. When i have downloaded the file a drag it and drop it after the install word. The problem is that if I want to drop it there it will do nothing, nothing there shows or anything. Please respond.

I guess you can type the path to the installation file instead of dragging.

Hello,
Very helpful thread, my coolpad Modena 2 (E502) is now rooted.
Don't forget to disable the factory mode once everything is done, or you won't be able to access the storage to usb anymore.
Thanks.

helo, can i get help, when i try to install openrp on abd and fastboot, it printed this message "Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE]"
can anyone help me on that step, so i can root my e502

TCRakt said:
Hello,
Very helpful thread, my coolpad Modena 2 (E502) is now rooted.
Don't forget to disable the factory mode once everything is done, or you won't be able to access the storage to usb anymore.
Thanks.
Click to expand...
Click to collapse
how to disable the factory mode ?? :crying:

Firefa23 said:
how to disable the factory mode ?? :crying:
Click to expand...
Click to collapse
Hello,
If I recall correctly (I don't have the phone anymore, just touched it once to root it at the time), you basically undo the "Enabling factory mode" step.
I think if you dial the number, you'll be back in the menu where you have the option to disable the factory mode.
Factory mode should be disabled when 'DM' is green.
Good luck

very good

Need Custom rom please
nougat / pie

Hello, could you resend the twrp recovery file for this phone again?. old links not work!.
(sorry for my bad english)