before fanything you will need to enable the tegra drives do the following so your folio is recognised as and adb interface:
you dont need this if your folio is allredy recognised has a adb interface in device manager.
1) Install the Adb driver.
For driver :
- Download the android SDK
- Edit "<your-android-sdk-folder>/usb_driver/android_winusb.inf"
- Add the following after [Google.NTx86] (or [Google.NTamd64] if 64 bits windows)
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
2 now for the flashing
make sure you have the following
adb on your computer
recovery image(recovery.img found inside update.zip from folio mod
folio must be rooted(use superoneclick1.6.5 or over)
and last the app (root explorer)
lets start
step 1. instal root explorer on your folio
step 2. copy the recovery image from foliomod in your computer to a memory card
step 3.with your memory card inserted in your folio using root explorer copy the recovery.img to this directory like this /data/recovery.img note:if found another data folder inside past the recovery.img there aswell
step4. exit root explorer now in your computer type this in comand prom (cmd)
"adb shell" without quotes it should say demon started sucessefuly.and a $ sign should be there
now type this "cat /data/recovery.img >/dev/block/mmcblk0p7" without quotes
if nothing happens it means it worket
now for the flashing do not factorise do it after instaling the mod your trying to install.
alternative way:If you get the permission denied error, type in: "su -" and on your tablet superuser should come up with a permission request. Allow this and you are really "root" as the # shows in the shell window.
note:if you found this guide usefull dont forget to press the thanks button
you dont need this for your folio to be recognised has a adb interface in device manager
1) Install the Adb driver.
For driver :
- Download the android SDK here
- Edit "<your-android-sdk-folder>/usb_driver/android_winusb.inf"
- Add the following after [Google.NTx86] (or [Google.NTamd64] if 64 bits windows)
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
MCLP said:
so what you will need
adb on your computer
recovery image(recovery.img found inside update.zip from folio mod
folio must be rooted
and last the app (root explorer)
lets start
step 1. instal root explorer on your folio
step 2. copy the recovery image from foliomod in your computer to a memory card
step 3.with your memory card inserted in your folio using root explorer copy the recovery.img to this directory like this /data/recovery.img note:if found another data folder inside past the recovery.img there aswell
step4. exit root explorer now in your computer type this in comand prom (cmd)
"adb shell" without quotes it should say demon started sucessefuly.and a $ sign should be there
now type this "cat /data/recovery.img >/dev/block/mmcblk0p7" without quotes
if nothing happens it means it worket
now for the flashing do not factorise do it after instaling the mod your trying to install.
if you are having trouble instaling adb on your computer please tell i dont mind making one tutorial cause for tegra devices u need to modifie the driver file.
Click to expand...
Click to collapse
Looking good, but cant we just fatboot it over, well anyway wich rooting method works? Visionary? z4root? superoneclick?
nickwarn said:
Looking good, but cant we just fatboot it over, well anyway wich rooting method works? Visionary? z4root? superoneclick?
Click to expand...
Click to collapse
the latest superoneclick works like a charm
z4root wont work
visionary aswell
MCLP said:
you dont need this if your folio recognised has a adb interface in device manager
1) Install the Adb driver.
For driver :
- Download the android SDK here
- Edit "<your-android-sdk-folder>/usb_driver/android_winusb.inf"
- Add the following after [Google.NTx86] (or [Google.NTamd64] if 64 bits windows)
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Click to expand...
Click to collapse
hello,
I just install the SDK, but the folder :
"<your-android-sdk-folder>/usb_driver/"
doesn't exist and the .inf is not found ...
any idea ?
thanks for your help ...
abdrx said:
hello,
I just install the SDK, but the folder :
"<your-android-sdk-folder>/usb_driver/"
doesn't exist and the .inf is not found ...
any idea ?
thanks for your help ...
Click to expand...
Click to collapse
Launch the SDK by double-clicking SDK Manager.exe, at the root of your SDK directory.
Expand the Third party Add-ons and Google Inc. add-ons.
Check Google Usb Driver package and click Install selected.
Proceed to install the package. When done, the driver files are downloaded into the <sdk>\google-usb_driver\ directory.
To install the Android USB driver on Windows for the first time:
Connect your Android-powered device to your computer's USB port.
Right-click on Computer from your desktop or Windows Explorer, and select Manage.
Select Devices in the left pane.
Locate and expand Other device in the right pane.
Right-click the device name (such as Nexus S) and select Update Driver Software. This will launch the Hardware Update Wizard.
Select Browse my computer for driver software and click Next.
Click Browse and locate the USB driver folder. (The Google USB Driver is located in <sdk>\google-usb_driver\.)
Click Next to install the driver.
Hi all,
ok, done, back from last Tosh ROM to the last Dexter ROM ...
abdrx said:
Hi all,
ok, done, back from last Tosh ROM to the last Dexter ROM ...
Click to expand...
Click to collapse
if you did not use my methord u can always share how you did yours
Hey, I had a problem, my adb gave me a permission error every time i tried "cat /data/recovery.img >/dev/block/mmcblk0p7", so all what i have done is downloading a terminal emulator and just tap it, it went then perfectly
MCLP said:
if you did not use my methord u can always share how you did yours
Click to expand...
Click to collapse
Yes !!
I follow this one with a MIX of your post :
(start at section BUT for some of you (including me) this will fail and you will see a text on the screen like booting recovery kernel image and the tablet freezes there. )
http://forum.xda-developers.com/showthread.php?t=915894
and with FASTBOOT, it works for me.
abdrx said:
Yes !!
I follow this one with a MIX of your post :
(start at section BUT for some of you (including me) this will fail and you will see a text on the screen like booting recovery kernel image and the tablet freezes there. )
http://forum.xda-developers.com/showthread.php?t=915894
and with FASTBOOT, it works for me.
Click to expand...
Click to collapse
thats too comlex my methord is easier
MCLP said:
if you get permission denied or some kind off error u are better off using terminal emulator
Click to expand...
Click to collapse
If you get the permission denied error, type in: "su -" and on your tablet superuser should come up with a permission request. Allow this and you are really "root" as the # shows in the shell window.
NVM. I solved it.
Great guide! Im now running the foliomod
Ok, I'm an idiot. I've updated my new Folio - spot foliomod too late ;(((
Now I can't root it.
I followed what said here (and others post on xda).
I've installed the driver but 'ADB devices' does not show anything below the list in command prompt.
The latest superoneclick idles (more than an hour) with no result.
Maybe I need to change the text string to make it recognize the driver?
Any hint?
EDIT: solved. I've reinstalled driver (not in fastboot mode and checked adb_usb.ini).
Now it's rooted. Superoneclick rules.
Hi,
Im on the latest original firmware whith a big-ass problem...
My internal storage and SD-card wont get recognized whiles the folio is started up.
Therefor i cannot install root explorer or anything else on my folio.
Is there another way to root my folio?
Thnx
ibila said:
Hi,
Im on the latest original firmware whith a big-ass problem...
My internal storage and SD-card wont get recognized whiles the folio is started up.
Therefor i cannot install root explorer or anything else on my folio.
Is there another way to root my folio?
Thnx
Click to expand...
Click to collapse
thats sounds like an internal error try factorising your folio through recovery and check if it works (it should work otherwise u just meessed ur tabllet)
shidima_101 said:
If you get the permission denied error, type in: "su -" and on your tablet superuser should come up with a permission request. Allow this and you are really "root" as the # shows in the shell window.
NVM. I solved it.
Great guide! Im now running the foliomod
Click to expand...
Click to collapse
if you found this guid usefull dont forget to hit the thanks button
MCLP said:
thats sounds like an internal error try factorising your folio through recovery and check if it works (it should work otherwise u just meessed ur tabllet)
Click to expand...
Click to collapse
Tried factory reset but doesn't help. Nether does flashing the firmware..
Sent from my HTC Desire using XDA App
Thanks done
I think could be useful add this part to the guide on the "how to enable Tegra driver":
Type this in the Run of start menu:
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
This command prompt add a 0x955 line in adb_usb.ini located in C:\Documents and Settings\<name of the user>\.android
Find the folder with " %USERPROFILE%\ " in Run.
I'll try to recover my Folio ASAP and I'll let you know
EDIT: Done! I'm on FolioMod
shidima_101 said:
If you get the permission denied error, type in: "su -" and on your tablet superuser should come up with a permission request. Allow this and you are really "root" as the # shows in the shell window.
Click to expand...
Click to collapse
thanks, yes permission error solved
Hi and thanks for your guide.
I just wanted to ask some questions before, so I dont screw up my brand new tablet
I rooted it and installed Root Explorer. Copied the Recovery.img to "\data" and "\data\data"-folders.
So far so good. But when i connect my tablet with USB-debugging enable, run a command promt, and typ "adb shell" it shows a $-sign but i doesnt say anything else, the "demon started sucessefuly"-part is missing. Is this a problem?
One more thing, when ive successfully flashed this recovery, should i be able to install FolioMod like with old fimwire?
Thanks in advance!
Related
z4root allows you to put the device in usb debugging mode and appears to allow temporary root I didn't try the permenant method. This may be premature so don't get to worked up. Also If your not comfortable with ruining your device don't.
yaggermr said:
z4root allows you to put the device in usb debugging mode and appears to allow temporary root I didn't try the permenant method. This may be premature so don't get to worked up. Also If your not comfortable with ruining your device don't.
Click to expand...
Click to collapse
Great news my friend
That's what I supposed. By the way, with Usb Debugging mode you can use the Kndle fire method for root!
death2all110 said:
So I was messing around with different one clicks since I got ADB going on my kindle fire and I was able to Successfully use SuperOneClick 2.2 to root my kindle fire!
Sorry for the mess. Its late, and I wanted to type this up so I could crash...
To get adb going you must already have the sdk on your machine and used it.
goto: %USERPROFILE%\.android and edit the adb_usb.ini and add this to the end of the file and save:
Code:
0x1949
then go into where you have the sdk at and open the google-usb_driver folder and edit android_winusb.inf and add this to the [Google.NTx86] section and [Google.NTamd64] section:
Code:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
save and close
If you have already plugged your kindle into the usb you may have to open device manager and find "Kindle" under other devices and choose the android_winusb.inf file.
Turn on Installation of apps from unknown sources: tap the top bar>choose more...(+)>device
open a command prompt and run adb kill-server then try adb devices..
you should see a device listed.
go here: http://forum.xda-developers.com/showthread.php?t=803682a
download and run SuperOneClick and choose the "root" option. let it go!
Click to expand...
Click to collapse
thanks for the info im going to try this method.
Beautiful news. Keep it coming
<3 XDA
There doesn't appear to be an adb executable on the nook tablet at all.. hmm..
So far no luck with super oneclick
Well it appears that z4root doesn't even achieve a temporal root but it does allow you to access developer settings. I think the debug mode is important and should allow someone with more skill than myself the ability to root the nook. I also am not positive super one click can't work. Anyway most things I want to work great. Someone is going to crack this nut.
Considering this thing isn't even out yet officially, and all everyone has already done to it, I don't think we have anything to worry about. It'll be rooted in no time.
Sent from my Nook Tablet using Tapatalk
It's worth trying (and copying out the error messages) running zergrush.
Since you have an ADB prompt, you can probably copy files across to /data/local/ on a lot of Android devices - if I remember rightly, that directory has relaxed permissions for creating files.
Zergrush was able to root the Samsung once copied to that directory.
A discussion of zergrush is here:
http://forum.xda-developers.com/show....php?t=1320350
Basically, get the zergrush tool (not the .c file but the executable), copy it to /data/local, and try a
sh zergrush
You'll probably get a bunch of messages followed by it not quite working.
If we're super lucky, it'll just work and give you a # prompt, meaning you've got root.
(and if you already had the # prompt, I'm pretty sure you had root. The non-root adb prompt is $ on most devices.)
This should the right instruction to configure ADB server:
Prerequisite: Android SDK installed.
1) Open with Notepad %USERPROFILE%\.android\adb_usb.ini and add this to the end:
Code:
0x2080
2) Open the google-usb_driver subfolder in sdk folder, edit android_winusb.inf with notepad, find [Google.NTx86] and [Google.NTamd64] section:
Code:
;Nook Tablet
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
[THIS VALUES COME FROM Kindle Fire, SO CAN BE DIFFERENT!]
3) Save and Close.
4) Kill Adb: adb kill-server then adb devices and check if the nook is there.Let me know if worked.
diamond_lover said:
This should the right instruction to configure ADB server:
Prerequisite: Android SDK installed.
1) Open with Notepad %USERPROFILE%\.android\adb_usb.ini and add this to the end:
Code:
0x2080
2) Open the google-usb_driver subfolder in sdk folder, edit android_winusb.inf with notepad, find [Google.NTx86] and [Google.NTamd64] section:
Code:
;Nook Tablet
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
[THIS VALUES COME FROM Kindle Fire, SO CAN BE DIFFERENT!]
3) Save and Close.
4) Kill Adb: adb kill-server then adb devices and check if the nook is there.Let me know if worked.
Click to expand...
Click to collapse
Damn I should have brought mine to work with me... I could have tried this for you.
Nope. That doesn't work. I also tried changing the values in the android_winusb.inf file to 2080 (instead of 1949), but had no luck. My guess is there's something we're missing in the PID section.
It might seem a bit stupid, but maybe others will encounter one of this issues and it will help them. your more than welcome at add to this.
P: computer wont recognize device in debug mode. instead it recognizes "android 1.0" or something else.
S: download HTC sync. it contains the proper drivers.
P: while activating the *.bat file you get the erroe "adb out of date...killing". the script will run all the way, but root access wont be given.
s: you need to close all adb processes from task manager, and the htcsync process as well (on PC)! also, you need to reflash the img file, and try rooting again.
HTC SYNC
after 10 attempts at ROOT, I found this tread. It is CRITICAL that you stop the HTCSync process on you PC or root will not work!
HTC Sync on the tab or on the pc? I killed it on the tab through the running applications. To kill adb processes just close the command window on the pc.
you need to kill it on the PC.
Ok so noob question of the day!
Where are you supposed to input the commands (such as adb reboot bootloader) to start the kernel flash process? I tried in cmd as well as terminal emulator on the tablet with no luck, what am I missing here?
NJFM said:
Ok so noob question of the day!
Where are you supposed to input the commands (such as adb reboot bootloader) to start the kernel flash process? I tried in cmd as well as terminal emulator on the tablet with no luck, what am I missing here?
Click to expand...
Click to collapse
you should have ADB in your c:\android folder, or wherever your sdk is installed.
Do a search for adb with your pc to find out where you installed it.
then using the command prompt under start> programs> accessories> command prompt, go to the corrected directory that ADB is in.
to go to C:\android, for example, type " cd c:\android "
Then you would execute the adb commands, (example: adb reboot bootloader)
Go to youtube and search for a 'how to use ADB' tutorial.
I'm having difficulty hotbooting the insecure kernel.
I've uninstalled HTC Sync on my PC, and I've downloaded the insecure kernel to my SD card's root directory.
I have no problem rebooting the bootloader via adb, and my device is detected. However, when I try to hotboot the kernel, I routinely get a "cannot load" response. I'm typing in "fastboot boot [filename].img."
Suggestions?
Many thanks.
the insecure kernel shouldn't go to the SD card. only the wifi module should.
the *.img file should go to the adb\tools directory,
(maybe you can put it anywhere else and just write the full path while flashing, i'm not sure. i just copy this files to the tools directory and flash them from there. easiest way)
the flash command flashes the file from the directory on the computer to the device.
Thanks very much!
I'm sitting here laughing to myself because I'd tried changing the path in the command to a couple of places I'd placed the insecure kernel in my PC; the c: root directory and a directory I'd created to house downloaded Jetstream files. Obviously, neither worked.
Placing it in the adb\tools directory makes complete sense.
By the way, your mention of the "wifi module" sent me back to DooMLoRD's kernel thread. I see that you flashed the kernel and related wifi module on 1/4. Like others who posted, are you pleased with the kernel?
Thanks, again!
The kernel seems very nice and almost no one complaind.
Sent from my GT-I9000 using XDA App
I've tried following various steps in the AIO thread in the developers section and believe I have a similar problem to pjc007. I have tried foloowing his steps in http://forum.xda-developers.com/showpost.php?p=27548839&postcount=1179 but I'm still stuck on getting the drivers installed when the tablet is in recovery mode. Am I right in trying to install the mtp driver from the AIO/files directory?
I have tried running AIO on two win 7 machines and a virtual xp machine and get the same problem on all machines. Please help
Is anybody able to help at all?
Or if anybody has a UK 16GB Wifi ICS Rom ready to run from recovery, that would be very much appreciated
you mean you háve your tablet already updated or rooted?., and the drivers aren't installed for ICS?
could you be more specific "D
---------- Post added at 09:45 PM ---------- Previous post was at 09:39 PM ----------
1. Update your SDK Manager
- In SDK Manager expand Extras then search for Google usb Driver if not already installed then do this,
2. Open the google-usb_driver folder that you will find inside your Android SDK folder.
- Example C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\
3. Open the android_winusb.inf file in notepad or any text editor to edit it.
- If you can't change this then try to change permissions in that folder
Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections.
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
;SONY Sony Tablet P
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_04D2&MI_01
;SONY Sony Tablet S
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_05B4&MI_01
4. Open a command prompt window and enter this command:
echo 0x054C >> "C:\Users\Cinquk\.android\adb_usb.ini"
5. Make shure you have USB Debugging enabled.
- Menu > Settings > Applications > Development and enable ‘USB Debugging’.
6. Connect your tablet to pc and let the pc install the drivers some will faill but thats okay.
7. Right-click Computer and click Manage and search your device from the list, right-click it and click Update Driver Software.
8. Choose to browse your pc,
- Choose to view all devices.
- Click Have Disk.
- Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
---- It might say that its not compitable but just proceed.
9. Once the drivers have been installed, you should be able to use ADB with your device.
10. to check that,
- Press Windows button + R
- Then type CMD and press enter.
- cd.. back to your Harddiskdrive.
- cd to your Platform-tools folder Example C:\Program Files (x86)\Android\android-sdk\platform-tools
- then type:
adb kill-server
adb start-server
adb devices
- you should see your devices listed ( Serial Number )
and you can comfirm that you have a working adb with you sony tablet s.
Thanks for the above info, my ADB is working fine in normal boot, but not in recovery mode.
I originally had my tablet rooted and updated to the first US ICS rom about a month ago using AIO tool v2.7
All was fine until I started poking around to find out why my titanium backup kept failing and found this was due to the SD card being set to read only. I followed a guide in these forums to enable read/write (before this fix was available in AIO) and somehow managed to wipe my permissions file.
I decided to start from scratch, flash back to hc and start again, but since doing this I have been unable to install an adb driver for when the tablet is in the recovery mode. ADB is working fine in normal operating mode and I could use AIO fine, until the point where it was waiting for a response in recovery mode as no drivers are installed...
I got impatient yesterday and have now updated a stock, non rooted US ICS as I've been going in circles for a couple of weeks trying to make a pre-rooted update file and I've been missing my ICS I would ideally like to be on a proper UK rom, but will live with US version if there's nothing I can do for now.
Alright that means end of this topic
i install sdk manager
and other files which it was mark as default
but to check if adb is installed correctly. i use cmd and enter adb devices
and i got the error " adb is not recognized as internal or external command on windows "
fine then i tried to get some help with device manager, i saw portable devices --> Xperia neo v.
and this is upto date, i stll click on update drivers --> Browse from my computer -- > let me pick manually --> Next
here i get only one compartiable hardware which name as " MTP usb device "
so i click have a disk enter this link " C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver "
The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
http://forum.xda-developers.com/showthread.php?t=1413293
i read this and try to help myself but
and i wont find this thing anywhere
9. Select Show all and click next
10. Click Have Disk, then Browse
11. Go to your extracted folder and go into it, until a file called android_winusb.inf is there. Double click that (NOT android_winusb_old.inf)
12. Click OK and then Next
-Note: If it says not signed, just click next anyway
13. Wait and if it says not signed, click install drivers anyway
14. Wait until it's done, then close all of your programs
15. Press the windows key and R at the same time on your keyboard
16. Type cmd and hit enter (Command prompt will appear)
17. Copy and paste the following code into it:
Code:
echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini
18. Type adb kill-server
19. Type adb devices, and your device should now show up
20. Hit the thanks button below
Please any of the xpert help me....:crying::crying::crying:
I forget to say i am using windows 7 64 bit
with xperia neo v 4.1 upgrated version
Qutub Uddin said:
I forget to say i am using windows 7 64 bit
with xperia neo v 4.1 upgrated version
Click to expand...
Click to collapse
Have a look at the 'basics' link in my signature. It tells you how to install the drivers properly.
Sent from my Galaxy Nexus using Tapatalk 2
I did it, adb installed in xperia neo v....
ITs alryt now....
thanx to veyka :good:
he help me with this
Google : how to add adb to your path...... this thing works for me
and i follow this steps. now adb is working fine after installation. i think people can help others with this link. and you too :good:
Qutub Uddin said:
ITs alryt now....
thanx to veyka :good:
he help me with this
Google : how to add adb to your path...... this thing works for me
and i follow this steps. now adb is working fine after installation. i think people can help others with this link. and you too :good:
Click to expand...
Click to collapse
As with any executable in windows, if you are in a different directory than the executable, you either have to provide the full path when executing it, or add the path of the executable to your windows path. This is not something specific to ADB, it is common for any executable in windows.
Sent from my Galaxy Nexus using Tapatalk 2
Has anyone had a successful root on a plt7602g. I have tried a couple different methods.
Rooting the PLT7602G
sallanm said:
Has anyone had a successful root on a plt7602g. I have tried a couple different methods.
Click to expand...
Click to collapse
Here is a procedure to root the Curtis Proscan PLT7602G tablet (Build number PLT7602G-ANDROID4.2.2-v1.0.0).
1. Install adb on your computer and enable adb on the tablet. http://developer.android.com/tools/help/adb.html
2. Enable ADB on the tablet:
Settings > About Tablet > tap build number 7 times until it says "You are now a developer!"
Developer options > switch On > OK
Check "USB Debugging" > OK
3. Connect USB and wait for ADB drivers to load on the PC. Using the Google drivers installed with ADB, your system may need manual help to find the right drivers: Go into Windows device manager > Update Driver Software > browse My Computer for driver software > 'Let me pick from a list of devices drivers...' > Pick Android ADB Interface from the model list.
4. You will see a notification "USB Debugging Connected" on the tablet.
5. If this is the first time, you will next see a dialog on the tablet asking "Allow USB debugging?" Check "Always allow from this computer" and click OK.
6. At the command prompt on the computer enter "adb devices". You should see the device listed. If not, reboot the PC and repeat steps 1 through 5 as necessary to get everything working together.
C:\Users\entropy>adb devices
List of devices attached
CD1LBROR50 device
C:\Users\entropy>7. Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
8. Unzip "pwn" from the zip file to your windows current directory
9. At the command prompt on the computer enter the following sequence of commands:
C:\Users\entropy> adb push pwn /data/local/tmp/pwn
C:\Users\entropy> adb shell chmod 755 /data/local/tmp/pwn
C:\Users\entropy> adb shell /data/local/tmp/pwn
Beaups and jcase were here
donations may go here, pleaes say what it was for -> [email protected]
10. After a few seconds, you should hear the USB disconnect sound, followed by the USB connection sound again.
11. At the command prompt, enter “adb devices” and ensure the device is listed as before. If not, wait a few seconds and then repeat this step.
C:\Users\entropy> adb devices
12. At the command prompt, enter:
C:\Users\entropy> adb shell
7. At the shell prompt, enter "su". You should now have a root prompt.
[email protected]:/ $ su
[email protected]:/ #
8. Exit back out to the command prompt:
[email protected]:/ # exit
[email protected]:/ $ exit
C:\Users\entropy>
9. On the tablet, go to the play store, download and install the latest SuperSU, or use the Google Play link in this thread: http://forum.xda-developers.com/show....php?t=1538053
10. Open the SuperSU that you just installed. SuperSU will prompt you to install a newer su binary when you run it, so click “Continue” do that, then “Normal”, then “OK”.
11. Reboot the tablet.
The tablet should now be fully rooted. Please let me know if you find any errors or if anything is unclear. I hope you find this useful!
I've downloaded the "Unrevoked" USB driver but the device is not being installed...
Marco Dufal said:
I've downloaded the "Unrevoked" USB driver but the device is not being installed...
Click to expand...
Click to collapse
It has been a while since I got this working and I honestly don't remember exactly what I did to make it work.
Try this... install the official Google driver and reboot:
http://developer.android.com/sdk/win-usb.html
If i still doesn't work, download the adb_usb.ini from here and replace the adb_usb.ini in c:\users\<yourusername>\.android\adb_usb.ini with this one, then reboot and try again. I verified that this adb_usb.ini contains the necessary device ID, so that should definitely do the trick.
https://github.com/apkudo/adbusbini
If you get it working, please post here so others can benefit.
Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'
Marco Dufal said:
Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'
Click to expand...
Click to collapse
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.
maximumentropy said:
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.
Click to expand...
Click to collapse
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
EDIT
I get
`su: not found`
Marco Dufal said:
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
Click to expand...
Click to collapse
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Marco Dufal said:
EDIT
I get
`su: not found`
Click to expand...
Click to collapse
I can't help you if you give me an error message but no hint of what you entered that caused the message.
maximumentropy said:
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Click to expand...
Click to collapse
Thanks I will check it up.
maximumentropy said:
I can't help you if you give me an error message but no hint of what you entered that caused the message.
Click to expand...
Click to collapse
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Marco Dufal said:
Thanks I will check it up.
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Click to expand...
Click to collapse
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su
maximumentropy said:
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su
Click to expand...
Click to collapse
Still negative result :
[email protected]:/ $ /system/xbin/su
/system/xbin/su
/system/bin/sh: /system/xbin/su: not found
127|[email protected]:/ $ ls /system/xbin/
ls /system/xbin/
dexdump
io
[email protected]:/ $
Marco Dufal said:
Still negative result :
Click to expand...
Click to collapse
What is your build number in Settings > About Tablet?
maximumentropy said:
What is your build number in Settings > About Tablet?
Click to expand...
Click to collapse
PLT7602G-ANDROID4.2.2-v1.0.0
Marco Dufal said:
PLT7602G-ANDROID4.2.2-v1.0.0
Click to expand...
Click to collapse
Well, I apologize for being an idiot. That's what I get for trying to document a root procedure I did last year, from memory. I have several similar cheap tablets and I misremembered this one as being pre-rooted as I described.
I just re-flashed from stock and re-rooted it. Fortunately, I had left enough breadcrumbs on my computer that I was able to reconstruct the right procedure.
I will do another full run-through within the next few days as soon as I have some time, to make sure I have everything 100% straight, and will clean this up to update the OP. Meanwhile, if you're feeling brave, here's the notes I took as I did it:
Settings > About Tablet > tap build number until it says you are a developer
Developer options > switch On > OK
USB Debugging > OK
Connect USB
see "USB Debugging Connected" notification
Wait for "Allow USB debugging?" dialog, check "Always allow from this computer" and click OK
adb devices
Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
Unzip "pwn" from the zip file to your windows current directory
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
Hear USB disconnect sound
Wait about 1 minute (may or may not need to disconnect and reconnect USB cable)
adb wait-for-device
adb shell
su (should give a root shell)
exit
Install SuperSU from Play Store
Run it
The SU binary needs to be updated. Continue?
Continue > Normal > OK
Reboot
Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...
Marco Dufal said:
Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...
Click to expand...
Click to collapse
No guts, no glory!
I updated the instructions in post #2 and did another trial run through. Give it a shot at let me know if you run into any trouble. You already have ADB functioning, so you can just skip to step 6 and go from there.
http://forum.xda-developers.com/showpost.php?p=59530490&postcount=2
maximumentropy said:
No guts, no glory!
Click to expand...
Click to collapse
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?
Marco Dufal said:
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?
Click to expand...
Click to collapse
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.
maximumentropy said:
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.
Click to expand...
Click to collapse
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks
Ian1331 said:
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks
Click to expand...
Click to collapse
I don't think it will work in a terminal emulator because you need to run with uid 2000 (shell) for permission on the /data/local/tmp directory.