Hi,
I am new to Android. I have downloaded and installed every necessary component in order to start working with Android. The issue I am having is that in Command Prompt, anything I type in related to the Android SDK (for example: adb, or even just android) comes back with "Java was not found in your path". Now, I have changed all my PATH variables under "User" to the EXACT locations of where these folders are, but no dice. It keeps telling me to go and edit my PATH variables. Even running SDK Setup, gives me the same error, and tells me to add where Java was found (even though I have!).
I am starting to get really fed up with this, because Eclipse can't find the "jre" folder inside the Java JDK, either (that is, of course, until I copy the entire jre folder inside of the eclipse folder, or put eclipse inside of the JDK folder)...
I just know it shouldn't have to be this tedious to set everything up and I would really appreciate it if someone can help with this
I am running Java JDK 1.6.0_21 (x64), Eclipse Helios (3.6) IDE for Java EE Dev., Android SDK Revision 6, all on Windows 7 Ultimate x64.
Something to note: I have not encountered any problems with Eclipse Helios and the ADT plugin as stated on the Android Developers website. I can use Eclipse and the SDK to create and run the"Hello, Android!" application on the emulators without issues. I just want to be able to run everything from the command prompt, too. Now, if I can only get my phone to be recognized after I get this resolved.
I also need this for rooting and unlocking the phone.
Bazz44 said:
Hi,
I just know it shouldn't have to be this tedious to set everything up and I would really appreciate it if someone can help with this
I am running Java JDK 1.6.0_21 (x64), Eclipse Helios (3.6) IDE for Java EE Dev., Android SDK Revision 6, all on Windows 7 Ultimate x64.
Click to expand...
Click to collapse
In the SDK tools folder go to libs and edit find_java.bat.
Change all instances of %PROGRAMFILES% to %PROGRAMFILES(X86)% .
I had to do this for my SDK.
Your java will probably still resides in c:\program files (x86)\java or the likes.
To test if it works open DDMS.bat(May need to open twice).
I ran "ddms.bat" before changing the "find_java.bat", and it just came up that it could not find the path > checking if it is installed elsewhere. I did what you suggested (I found three instances of where I needed to add the (x86)), ran "ddms.bat", and got the same error. However, this time it also opened the Dalvik Debug Monitor. Eclipse still won't run without its own copy of the "jre" folder from the JDK at the same folder level as the "eclipse.exe"...
any luck with this? I'm also having same trouble in Win7x64
Gonna give in otherwise n reboot my ubuntu system see if thats any easier
i know i can't use OpenJDK or something so ill have to swap that but fingers crossed
=]
Solution
Install any JRE Java, Copy the java folder at program files/Java/jre6 Paste it inside MOTODEV´s folder program files/Motorola/MOTODEV Studio for Android 1.2/ and rename it to jre
Done
Edited the eclipse .ini works a treat now wi java x64...
time to whip out the olde java books from college an see if any of it comes back to me
Is it possible to install the android sdk platforms & extras offline manually, my only net atm is my desire tethered, unlimited data but I don't wanna push my luck
I'm not sure if it may be related or not but according to the android dev page, you should be using eclipse 3.5 because they have been having problems with 3.6
May or may not be related but worth a shot.
I'm not sure if it may be related or not but according to the android dev page, you should be using eclipse 3.5 because they have been having problems with 3.6
May or may not be related but worth a shot.
i need help http://forum.xda-developers.com/showthread.php?p=24028502#post24028502
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Make nu system path
Try making new system path named PATH (all caps). its an issue with Win7 64. Hope it helps. and yes Installing the Android sdk is a giant head****. I have it all put as fare as the link to abandroid put it doesn't make plug-in available in the plug-in list. I'm at a loss...
As i said, hope it works.
Having just had this issue myself on a new install of eclipse, the sdk and adt, here's what finally helped me: making sure the java\sdk1.6.x.x\bin directorywas in front of the windows\sys32 directory in the PATH statement of the environmental variables.
I did already add the JAVA_HOME and such, but the above was the step that finally allowed me to finish the setup.
Fix for Win7 64bit and Android SDK/Java install
MacDegger said:
Having just had this issue myself on a new install of eclipse, the sdk and adt, here's what finally helped me: making sure the java\sdk1.6.x.x\bin directorywas in front of the windows\sys32 directory in the PATH statement of the environmental variables.
I did already add the JAVA_HOME and such, but the above was the step that finally allowed me to finish the setup.
Click to expand...
Click to collapse
I had to finally use JAVA_HOME C:/PROGRAM FILES/JAVA/JDK1.7.0_05 That finally allowed me to instal the Android SDK
best answer
rowdyvc said:
I had to finally use JAVA_HOME C:/PROGRAM FILES/JAVA/JDK1.7.0_05 That finally allowed me to instal the Android SDK
Click to expand...
Click to collapse
Thank you you solve my prob man
Hey guys, Ive just purchased a new x64 windows7 computer and am having difficulty getting the SDK installed.. I had it on my xp 32bit just fine, but the installer for android sdk wont recognize that I have the Java SE JDK installed and is telling me to set an environment variable to point to it. I am not all that familiar with setting Environment variables, or the new OS, any help would be greatly appreciated thanks. Just looking to get adb running for GB and above for ODIN, not looking to develop.
To install Odin3 and flash roms you don't use adb.exe for any task.
But the answer to your trouble is your path.
I wish that i knew more about ADB, and the SDK...
I did manage to establish a working development environment last spring, but the system I use is only a 32 bit environment.
The time since my setup has been so long ago now, that I have forgotten the particulars of the build. But I did learn a great deal from the guides posted here:
http://www.xda-developers.com/android/all-in-one-guide-to-adb/
Forgive my limited reply, as I desire to help you, but its quite clear that your knowledge of the android SDK exceeds that of mine.
And if you dont mind, I wish ask a question of you.
As you have used the 32 bit SDK successfully in the past, is it possible to copy and transfer all of the files needed to produce a working environment by simply loading said files from one PC to another ??
Or is the environment an individual set of parameters that must be created for use on each machine ??
I have never been successful in my search for an answer to that question.
Im sorry that its such an off topic request, but I truly wish to learn more in my old age....tbank you...g
rangercaptain said:
To install Odin3 and flash roms you don't use adb.exe for any task.
But the answer to your trouble is your path.
Click to expand...
Click to collapse
Thanks for the quick response, yea i gathered that much with the path , just dont know which field to put it in under environment variables or the proper format.. my question is how to properly set environment variables for the sdk to install.. Or just even a workaround for getting ADB up on windows 7.. Had no issues whatsoever on XP.. I Extracted the java.exe to the path the sdk software is looking, and still no luck (i like having ADB to push apks, root or recoveries n such when not looking to ODIN etc) I've tried several different tutorials and can't seem to get past the install of the sdk verifying i have the java se installed. ..
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
gregsarg said:
I wish that i knew more about ADB, and the SDK...
I did manage to establish a working development environment last spring, but the system I use is only a 32 bit environment.
The time since my setup has been so long ago now, that I have forgotten the particulars of the build. But I did learn a great deal from the guides posted here:
http://www.xda-developers.com/android/all-in-one-guide-to-adb/
Forgive my limited reply, as I desire to help you, but its quite clear that your knowledge of the android SDK exceeds that of mine.
And if you dont mind, I wish ask a question of you.
As you have used the 32 bit SDK successfully in the past, is it possible to copy and transfer all of the files needed to produce a working environment by simply loading said files from one PC to another ??
Or is the environment an individual set of parameters that must be created for use on each machine ??
I have never been successful in my search for an answer to that question.
Im sorry that its such an off topic request, but I truly wish to learn more in my old age....tbank you...g
Click to expand...
Click to collapse
My apologies if i sounded sassy in my response, i didn't mean to offend and am very thankful for all that u contribute here on xda and ur response. As for your question, i believe IMO due to the heavy reliance on drivers for the SDK to run for "X" device(s) development is being implemented on, it would more than likely need to be created specific to each machine during the install of each runtime ..but would imagine certain elements could be transferred or copied across. . But again just my guess, for i have not tried. I am new to win 7 and a NEWB to XDA. .. You sir are the mentor in this happenstance. Thanks again for the link and advice.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Make sure you installed 64bit java. I had the same problem and it turned out I kept installing the 32bit java. Their downloads can be very confusing.
Right click on "computer" on the start menu or in Windows explorer. Then go to properties.
On the left you will see an option that says "advanced system settings"click on that.
In the new window there will be 5 tabs up top, go to the "advanced" tab which is in the middle.
Once there, at the bottom is a button that says "environmental variables"
Click on that and there will be a new window broken into 2 sections: user variables, and system variables.
Go down to system variables till you see one named "path" select it and choose edit.
Now, you should have the java jre installed.
I have a 64 bit environment with 32 bit java,.That's fine.
The path that is installed to, and what you want to enter into your variable is:
;C\program files (x86)\java\jre7\bin
Close that out.
Now open a command prompt and simply type java, if you get a long list of details that tell you the commands you can use, congratulations java is now in your path.
If it says "java is an unknown command" you have messed up somewhere.
Ok, now that you have adb installed, go to the platform-tools folder.
Copy:
Aapt.exe
Adb.exe
Adbwinapi.dll
Adbwinusbapi.dll
And paste those into your main Windows folder.
Now, you can enter adb command from any directory, you do not have to cd to the platform-tools folder first.
Excellent ....
Many thanks !!.....g
studacris said:
Right click on "computer" on the start menu or in Windows explorer. Then go to properties.
On the left you will see an option that says "advanced system settings"click on that.
In the new window there will be 5 tabs up top, go to the "advanced" tab which is in the middle.
Once there, at the bottom is a button that says "environmental variables"
Click on that and there will be a new window broken into 2 sections: user variables, and system variables.
Go down to system variables till you see one named "path" select it and choose edit.
Now, you should have the java jre installed.
I have a 64 bit environment with 32 bit java,.That's fine.
The path that is installed to, and what you want to enter into your variable is:
;C\program files (x86)\java\jre7\bin
Close that out.
Now open a command prompt and simply type java, if you get a long list of details that tell you the commands you can use, congratulations java is now in your path.
If it says "java is an unknown command" you have messed up somewhere.
Ok, now that you have adb installed, go to the platform-tools folder.
Copy:
Aapt.exe
Adb.exe
Adbwinapi.dll
Adbwinusbapi.dll
And paste those into your main Windows folder.
Now, you can enter adb command from any directory, you do not have to cd to the platform-tools folder first.
Click to expand...
Click to collapse
Thank you very much sir for the indepth instructions. . Between your directions and gregsarg's link i was able to get adb up by using the 32bit ver download instead of the 64bit even though my machine is 64bit... Guess there is at least a little functional backwards compatibility left in win 7 afterall. ..:thumbup::thumbup:
Please re-edit your title so you have [solved]Original Question so others having the same issue can enjoy the given solution. Thank you.
I have used many different methods to root phones even a few tablets for friends. But I have bought a HKC 7 inch tab from walmart. Great starter tablet by the way. I have found no information what so ever on any forum about this model. It has decent processor power and runs rather smooth. Alas there is no way to root this thing to reach its full potential. I checked around on the net and found nothing, none of the one click apps work on this model. Adb does not recognize the tablet either. I've put in the tablet ID into the adb_usb.ini still no device found. I'm not looking for anyone to just hand me the root process on a silver plater, though that would be nice, but any help moving me in the right direction would be appreciated.
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment Rockusb.rar
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Krytical said:
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment 1468367
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Click to expand...
Click to collapse
Thanks for the info. Will be giving it a go later today
Krytical said:
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment 1468367
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Click to expand...
Click to collapse
when in doubt go back to the forums. I can not get the inf in the rockusb to install. "Installation for this file type not permited" . So I'm stuck, the program will not complete. I'm on windows 7 so maybe the driver is for another system. If you can provide futher help, Thanks in advance.
New approach
Ok I cannot get the drivers to install on my computer. Window 7 seems to default to its own driver and will not let me install the rockusb drivers.
With that said, I have the system Update.img and was wandering if the img itself can be rooted and then updated to the tablet. If this is possible and anyone with the knowledge is willing I will upload it. Or if someone is really patient and would like to walk me through the process and I will attempt to do this myself
No Help
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
tannerjames said:
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
Click to expand...
Click to collapse
Can't tell your level of PC knowledge so if you already know this don't get offended. The .inf is editable and there are areas in there that allow manufacturers to prevent installation on some OS's to prevent conflicts. Make a system restore point or better yet a backup and then post the contents of the INF somewhere and point the folks here to it and they may be able to help you edit it to install. Regardless, you'll have to use the "have disk" option instead of letting windows search for a driver even if you get the edits right. And the usual disclaimers about me not being responsible for any issues with your equipment as a result of this are in effect.
tannerjames said:
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
Click to expand...
Click to collapse
I was able to root using the instructions above although i don't think you need the rockusb drivers. You just need the usb drivers that come with the android sdk. I am on Win 7. Thanks for the above info for rooting.
I was able to install ROM manager and now proceeding to backup ROM and upgrade using this guide: cant post link as forum is preventing, but search for rom flash guide on androidpolice com.
Hope this helps.
Big thanks to this thread to get me going...!!!
?
could someone please, Barney style, Explain how I am supposed to select the android_winusb.inf because my steps are as follows. Right click on device p771a in device manager, browse my computer, let me pick from a list of device drivers, have disk, point to the google usb driver (C:/Android/android-sdk/extras/google/usb_driver) select the android_winusb.inf open. Hit ok, (The folder you specified doesn't contain a compatible software driver for you device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems). Hope this helps explain my troubles. Glad that my thread is helping others to root this device but it does not work for me.
Could it really be that simple?
Found in another forum about the nexus 7 when connected to the pc there is a presistent notification that allows you to change the connection type from mpt to camera which will give you adb access and the tool from this thread works great. Thanks for the help guys, got my root on
tannerjames said:
Found in another forum about the nexus 7 when connected to the pc there is a presistent notification that allows you to change the connection type from mpt to camera which will give you adb access and the tool from this thread works great. Thanks for the help guys, got my root on
Click to expand...
Click to collapse
Glad you could figure it out...
I was not able to use the ROM Manager to backup the ROM since the device is not supported on this tool, but see below for how you can obtain the stock image.
I've tried to flash multiple different ROMs using RKAndroid to the tablet, spending days on this, with no success. The tool itself works great and I am able to flash the ROMs since it supports the RK29 chipset which I believe this tablet has. The stock ROM for this device is available from the manufacturers web site (the link is available when you go to Settings => About Device => System Update, hkcdigital dot com slash update slash update.img), if anyone would like to take the stock rom and upgrade it to Android 4.2/JB.
I was able to unpack/repack the stock image using the wendal image tools and modify / cook the ROM using Android kitchen method described elsewhere in this forum. Rockchip Batch Tool is another great utility to flash custom ROMs to this device. Also, If you put the ROM as update.zip or update.img file on the microSD card, the tablet will take it and flash the image as long as it is in the right format. Ofcourse you can put the tablet into recovery and restore from there as well. I've found that the stock image (update.img) has the following file/folder format when unpacked: /RK29xxLoader(L)_V2.27.bin, /package-file, /parameter, /recover-script, /update-script, /Image/boot.img, /Image/system.img, /Image/recovery.img and /Image/misc.img.
Is it possible to upgrade this tablet to Android 4.2 or atleast Jelly Bean? Would be very helpful if someone is able to do this. The most success I've had so far is with the custom ROM Oma_Odys_Loox_JB_4.1.1_v1.2.2a flashed using RKAndroid. It flashed the tablet fine, updated the boot etc. On tablet boot I am able to see the new logo, but then the it doesn't go anywhere from there. I think customizing this ROM or the stock ROM we should be able to get the new OS on to the HKC tablet. I've given up for now since I don't have the time to spend on this anymore. If someone is able to do this, please post the instructions or upload the custom ROM, as I am sure it will benefit a lot of people and will be much appreciated. Happy cooking!
Thanks!
jawadshaik- rom manager
If you have successfully flashed rom manager on this device could you post the steps you took to do so. What version? Manual flash? The program itself says there is no recovery for this device.
Sorry jumped the gun on that last post. Thanks for the info
What's the secret to keeping the battery from draining so quickly while it's idle? I just got this and see it drained about 40% in about 2 hours I think and I wasn't using it.
tannerjames said:
I have used many different methods to root phones even a few tablets for friends. But I have bought a HKC 7 inch tab from walmart. Great starter tablet by the way. I have found no information what so ever on any forum about this model. It has decent processor power and runs rather smooth. Alas there is no way to root this thing to reach its full potential. I checked around on the net and found nothing, none of the one click apps work on this model. Adb does not recognize the tablet either. I've put in the tablet ID into the adb_usb.ini still no device found. I'm not looking for anyone to just hand me the root process on a silver plater, though that would be nice, but any help moving me in the right direction would be appreciated.
Click to expand...
Click to collapse
@jawadshaik
Just out of curiosity, when you were flashing that Rom that brought up the boot screen, did you do a wipe/factory reset from recovery mode before flashing? I have no idea if that would help or not, but most if not all roms require a data wipe before flashing... Just curious if you had tried this as I have heard of this happening on other devices because a data wipe wasn't done first. Might be worth a shot if you haven't tried it already, just a thought
Sent from my Huawei u8651s using xda app-developers app
Krytical said:
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment 1468367
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Click to expand...
Click to collapse
So after doing working on this a while, I've finally figured it out. Here are some caveats:
1. You can't do this on a Mac or Linux box. Don't ask me why, you just cant.
2. You have to turn on USB debugging, change the Security to allow Unknown sources and MOST IMPORTANT: when you plug it in, you have to change it to "Connected as a Camera". Putting it in storage mode doesn't work!
HOW TO INSTALL THE PROPER DRIVER & ROOT THE DEVICE:
1. Follow the steps quoted above and download the Google Android SDK, and the Java JDK (from oracle.com/java).
2. When you first plug it in (use the USB plug labeled USB not the HOST one), it complains and will discover a P771A device. When it does, right click on your computer, choose Manage my computer, go to the device manager and then right click on the P771A device. Click "Update Device Driver". Choose "Browse my computer for Driver software". Then choose, "Let me pick from a list of drivers on my computer". Browse to the \adt-bundle-windows-x86_64\sdk\extras\google\usb_driver folder which you would have if you had downloaded and installed the Google Android SDK. A list of 3 drivers will appear when you click OK. CHOOSE THE "ANDROID BOOTLOADER INTERFACE" as the driver. None of the others work.
3. Run the root script batch file mentioned above which can be found here at: sourceforge.net/projects/androidroot
4. The root script isn't really great at explaining so I'll try. When you first run it, make sure your device is unlocked and on the home screen.
5. The first thing it will do is reboot your machine. Don't press enter until your machine comes back up.
6. After your machine boots unlock it and then press Enter again. Your machine will reboot. This time it won't seem to come up but the backlight will remain on.
7. Wait about 30-45 seconds then press enter again. You should get: uid=0(root) gid=0(root) in the command prompt window.
8. Press Enter. You should get:
remount succeeded
727 KB/s (22364 bytes in 0.030s)
Removing changes except ROOT...
Installing superuser...
2288 KB/s (843503 bytes in 0.360s)
9. After about 30-60 seconds, your device should reboot. You'll see a box briefly saying "Android is Upgrading" and you'll arrive at the lock screen. Press Enter to exit the command prompt.
Your device is now rooted and you should see "SuperUser" installed. I promptly installed "root uninstaller" to get rid of Facebook, Skype, and Youtube which my little kids don't need access to. This device doesn't have a bootloader or recovery mode so rooting it doesn't get you much besides the ability to uninstall the system software. Have fun.
This may help someone but on step 2 of the guide on the second page, after you right click your device and go to "Let me pick from a list of drivers on my computer". You then click "Show All Devices" then "Have Disk..." Direct it to the root of the adt-bundle folder you downloaded then you can select from the three drivers. I'm on windows 7 32bit and the drivers didn't show up for me like how it was suppose to..
I also could NOT get any of the drivers in the "manufacturer USB" packet to install... I WAS able to install the google drivers, but that also would not allow ADB to see the device... So still stuck with everyone else...
P771A possible problem
I'm having a similar problem where the USB driver downloaded through Android SDK's -> Extras -> Google USB Driver, tells me that the file contains no information about my device. I noticed in the Sources of SDK, there wasn't an API for 4.0.4, only 4.0.3 then 4.1, so i downloaded 4.0.3 repo.
============================================
my devices is on 4.0.4, and my Kernal is as follows:
3.0.8+
[email protected] #8
Wed Aug 29 09:59:19 PDT 2012
Build Number:
P771A-user 4.0.4 IMM76D user.v402.007 release-keys
============================================
I've also made sure weather Unknown Sources is on, as well as USB debugging.
Might the Kernal be the problem? Also, does it matter weather its MTP or CTP?
Now HKC is telling me that they don't support the ability to jail break their devices
Sent from my P771A using xda app-developers app