Related
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!
Sent from my ARCHOS 80G9 using xda app-developers app
Afaik, no. We must wait archos to release now official. Or maybe you can downgrade by formatting device and flasing 4.0.7 update.
eyco said:
Sent from my ARCHOS 80G9 using xda app-developers app
Click to expand...
Click to collapse
Hi !
I uninstalled SDE by mistake yesterday !
...so, you can enable (install) unofficially SDE following this path ( work 100% on firmware 4.0.25 ) :
On your tablet :
check on Settings-> Developer options -> USB debugging on !
connect USB cable ( PC to tablet )
On your PC :
> adb push 1 /data/local
> adb push 2 /data/local
> adb shell
$ chmod 0755 /data/local/*
$ ./data/local/1
$ exit
> adb reboot
> adb shell
$ ./data/local/2
$ exit
> adb reboot
> adb push zimage /data/local/tmp
> adb push initrd.cpio.lzma /data/local/tmp
> adb push abcbox /data/local/tmp
> adb shell chmod 755 /data/local/tmp/abcbox
> adb shell /data/local/tmp/abcbox kd_flasher -k /data/local/tmp/zimage -i /data/local/tmp/initrd.cpio.lzma
( now you have installed unofficially SDE ! )
Flash Root version or other Custom Rom :
> adb reboot
> adb shell rm /data/local.prop
> adb push archos.ext4(.update) /mnt/storage
Go to SDE -> ( check "Reboot" on power off menu , and after a while press & keep volume down until you see SDE menu !)
Go to Recovery System -> Developer Edition Menu -> Remove Android Kernel -> I Undestand -> OK -> Developer Edition Menu -> Flash Kernel & Initramfs -> copy here zImage and initramfs.cpio.lzo appropriate archos.ext4(.update) -> OK -> wait to boot !
Now you have Rot version installed !
Here you will find the necessary files : Enable_SDE.zip
surdu_petru said:
Hi !
I uninstalled SDE by mistake yesterday !
...so, you can enable (install) unofficially SDE following this path ( work 100% on firmware 4.0.25 ) :
Click to expand...
Click to collapse
I put your guide to my collection. With proper credits OFC. If you have something against it, please post here
Sent from my GT-I9100 using xda app-developers app
julle131 said:
I put your guide to my collection. With proper credits OFC. If you have something against it, please post here
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Ok !
Very well , thanks !
....not more ....
Thanks, will try it tomorow
Sent from my ARCHOS 80G9 using xda app-developers app
ok need some help here.. where in the pc to put all this input?
eyco said:
ok need some help here.. where in the pc to put all this input?
Click to expand...
Click to collapse
Hi !
... does not matter as long as adb it works ! if adb do not recognized your device , than you need to put all files ( without adb and *.dll ) in .../Android/android-sdk/platform-tools/
This requires that you already have installed SDK & drivers from Archos ( need for adb recognized your device ! ) in your PC !
( also you need cmd command for run all commands on tour PC - available for Windows PC ) <- you can find cmd in my archive Enable_SDE.zip !!! =>"Command Prompt.lnk"
Good luck ! :good:
surdu_petru said:
Hi !
... does not matter as long as adb it works ! if adb do not recognized your device , than you need to put all files ( without adb and *.dll ) in .../Android/android-sdk/platform-tools/
This requires that you already have installed SDK & drivers from Archos ( need for adb recognized your device ! ) in your PC !
( also you need cmd command for run all commands on tour PC - available for Windows PC ) <- you can find cmd in my archive Enable_SDE.zip !!! =>"Command Prompt.lnk"
Good luck ! :good:
Click to expand...
Click to collapse
hi
i guess the adb didnt recognized the device.... :/
eyco said:
hi
i guess the adb didnt recognized the device.... :/
Click to expand...
Click to collapse
Ok!
Than, install SDK and drivers for your tablet from Archos ! :good:
i give up lol... i installed the sdk but have no idea what to do...
there is no software like on iOs that do it automatic?
eyco said:
i give up lol... i installed the sdk but have no idea what to do...
there is no software like on iOs that do it automatic?
Click to expand...
Click to collapse
Ok!
Put all the files from archive in /android-sdk/platform-tools/ ( without adb and all.dll)
& run cmd!
( also you need to install driver for your device from Archos- to recognized adb)
Good luck !
surdu_petru said:
Ok!
Put all the files from archive in /android-sdk/platform-tools/ ( without adb and all.dll)
& run cmd!
( also you need to install driver for your device from Archos- to recognized adb)
Good luck !
Click to expand...
Click to collapse
thanks i installed the drivers from archos, and will try to do like you said.
SdE installation.
eyco said:
thanks i installed the drivers from archos, and will try to do like you said.
Click to expand...
Click to collapse
I try to follow your explanation. I thinks I arrive to install asdk & driver, I click on command prompt.
I have this ... androis-sdk\platform-tools>
I put the first line adb push 1 /data/local, I have this message "error: more than one device and emulator "
You known that ?
Thanks by advance for your explanation
please give me an answer ?
---------- Post added at 06:40 PM ---------- Previous post was at 06:23 PM ----------
Can you help me?
I try to follow your explanation. I thinks I arrive to install asdk & driver, I click on command prompt.
I have this ... androis-sdk\platform-tools>
I put the first line adb push 1 /data/local, I have this message "error: more than one device and emulator "
You known that ?
Thanks by advance for your explanation
surdu_petru said:
Ok!
Put all the files from archive in /android-sdk/platform-tools/ ( without adb and all.dll)
& run cmd!
( also you need to install driver for your device from Archos- to recognized adb)
Good luck !
Click to expand...
Click to collapse
nico21311 said:
I try to follow your explanation. I thinks I arrive to install asdk & driver, I click on command prompt.
I have this ... androis-sdk\platform-tools>
I put the first line adb push 1 /data/local, I have this message "error: more than one device and emulator "
You known that ?
Thanks by advance for your explanation
Click to expand...
Click to collapse
Hi !
After installation SDE , you need to update your SDK , and also check driver !
Put all the files from archive without ( adb and all files .dll ) in directory /android-sdk/platform-tools/
Restart your PC , click on cmd and run all commands !
Good luck !
Thank you very much for your help.
You make a very good job .I hope to continue to support us
surdu_petru said:
Hi !
After installation SDE , you need to update your SDK , and also check driver !
Put all the files from archive without ( adb and all files .dll ) in directory /android-sdk/platform-tools/
Restart your PC , click on cmd and run all commands !
Good luck !
Click to expand...
Click to collapse
finely did it... thanks! and if i want to return to the original, i just flash the oem rom?
http://matthill.eu/android/root-transformer-prime-jellybean-update/
IT WORKS REALLY!!!! Simple & Easy with the Xperia Tablet S and Jelly Bean 4.1.1
I have tested with my Tablet SGPT122DE/S and i have really Root!
This, I note that this tool is not from me! The tool was written by @djrbliss.
If you want to thank someone then do that after your feeling - at least I thank everyone here on Meaningful information and applications ...
Thanks @xda-Community!
Greets from Germany Leipzig/Schkeuditz
(Download the Motochopper and run the run.bat)
Are you sure?
I just get *daemon started successfully*
ADB Driver
Ah there it occurs to me I'm so another ADB Driver tested ... it comes with the need to see if I still have the locally then I'll post times with the times here ...
Do not forget to turn on USB debugging
I Have a Adb Driver Interface Version 2.0.10.2 from 11.08.2009 (not digitaled signed)....
SWFlyerUK said:
Are you sure?
I just get *daemon started successfully*
Click to expand...
Click to collapse
same here
It appears to be an ADB issue - Just need to install the drivers.
*EDIT* -> Wow, it actually worked! I'm rooted!
sag ich doch das es wirklich funktioniert
I say but that it really works
SWFlyerUK said:
It appears to be an ADB issue - Just need to install the drivers.
*EDIT* -> Wow, it actually worked! I'm rooted!
Click to expand...
Click to collapse
what drivers did you install, these on the link?
thank u
Check this link mate;
http://forum.xda-developers.com/showthread.php?t=1883808
USB Driver
Here the Usb Driver for Adb Interface...
xxliftsupxx said:
http://matthill.eu/android/root-transformer-prime-jellybean-update/
IT WORKS REALLY!!!! Simple & Easy with the Xperia Tablet S and Jelly Bean 4.1.1
I have tested with my Tablet SGPT122DE/S and i have really Root!
Please Push the Thanks Button when it works for your Tablet
Greets from Germany Leipzig/Schkeuditz
(Download the Motochopper and run the run.bat)
Click to expand...
Click to collapse
GREEEEEEEEEEEEEEEEEEEAAAAAAAAAAAAAAAAAATTTTTTTTTTTT man and many thanks it worked for me :laugh:
Is this after been locked out before from 4.0.3 release6b to 4.1.1 aka the 4.1.1 that everyone have can get rooted if so awesome
Having root has totally transformed the way I use this device.
I can now remove adverts, I have the Xperia Tablet Z keyboard and Home Launcher, tried MB2 but it doens't work, grr!
SWFlyerUK said:
Having root has totally transformed the way I use this device.
I can now remove adverts, I have the Xperia Tablet Z keyboard and Home Launcher, tried MB2 but it doens't work, grr!
Click to expand...
Click to collapse
This is great took all of three mins to root ha ha where did you get the keyboard and home launcher can you post a link
also did you delete the old home launcher
Sent from my SGPT12 using xda app-developers app
works on SGPT132/CN, thank you thank you thank you. I can finally install google play on my stupid tablet
can this be done on a 4.1.1. never rooted xperia tablet or does it have to be a pre-rooted before updating to 4.1.1.??
has anybody tried this and or can confirm this is possible.
sengoku said:
can this be done on a 4.1.1. Never rooted xperia tablet or does it have to be a pre-rooted before updating to 4.1.1.??
Has anybody tried this and or can confirm this is possible.
Click to expand...
Click to collapse
never rooted!!!!! :d yay
Greetings guys ,
I installed the drivers also on a new pc but i am getting stuck at :
* daemon not running . starting it now on port 5037 *
* daemon started successfully *
Nothing happens after , as i wrote i tested on 2 pcs
Any help pls ?
Vatis
Great scott, it worked! So elegant root and wayyyyy sooner than I expected!
To the fokls having problems; I found out, that adb.exe in motochopper.zip did not want to play together with my Xperia. So I deleted it, killed adb.exe and copied latest adb.exe from android sdk to motochopper directory. Blam, no problems and I have root.
You may also manualy debug (and even root) by starting cmd.exe and calling commands manually, ie.
C:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
XXXXX device
If this don't show you device, you have no changes to root. If your device shows up, there should be no problems. If you devices is not showing, kill all adb.exe processes and use adb.exe from latest android sdk. Then you can even root manually and see waht step does what:
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb push su /data/local/tmp/su
adb push busybox /data/local/tmp/busybox
adb install Superuser.apk
adb shell /data/local/tmp/pwn
adb shell rm /data/local/tmp/pwn
adb shell rm /data/local/tmp/su
adb shell rm /data/local/tmp/busybox
And then manually reboot. Run each command manually one per one, do not copy paste every command as batch. This will teach you a lot But .bat should work.
Kudos to authors of motochopper!
vatis24 said:
Greetings guys ,
I installed the drivers also on a new pc but i am getting stuck at :
* daemon not running . starting it now on port 5037 *
* daemon started successfully *
Nothing happens after , as i wrote i tested on 2 pcs
Any help pls ?
Vatis
Click to expand...
Click to collapse
If you under windows 8
1st :
From the Metro Start Screen, open Settings,
Click "Change PC Settings".
Click "General".
Scroll down, and click "Restart now" under "Advanced startup".
Click "Troubleshoot".
Click "Advanced Options".
Click "Startup Settings".
Click [Restart].
Choose "Disable driver signature enforcement" (Usually #7)
2nd
Install device drivers either through the automated (not manualy use the : Install ADB Drivers.exe)
http://www.mediafire.com/?msn16sd5wrb1sdh
3rd
Run as administrator run.bat from motochopper
Normally this should work
Thank you very much for your replies mates.
Worked perfectly.
What i did :
Disabled the Disable driver signature enforcement as jimbxl said ,
installed the Sony tablet ADB driver.
Copy from inside the folder of Sony tablet ADB the adb.exe and the .dll (2 files ) and paste it to motochopper folder.
Cheers all
jimibxl said:
If you under windows 8
1st :
From the Metro Start Screen, open Settings,
Click "Change PC Settings".
Click "General".
Scroll down, and click "Restart now" under "Advanced startup".
Click "Troubleshoot".
Click "Advanced Options".
Click "Startup Settings".
Click [Restart].
Choose "Disable driver signature enforcement" (Usually #7)
2nd
Install device drivers either through the automated (not manualy use the : Install ADB Drivers.exe)
http://www.mediafire.com/?msn16sd5wrb1sdh
3rd
Run as administrator run.bat from motochopper
Normally this should work
Click to expand...
Click to collapse
---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------
SWFlyerUK said:
Having root has totally transformed the way I use this device.
I can now remove adverts, I have the Xperia Tablet Z keyboard and Home Launcher, tried MB2 but it doens't work, grr!
Click to expand...
Click to collapse
How we can install the new home Launcher swift ?
Cheers
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.
Hello everyone,
it's been over 20 hours I'm trying to root a Polaroid MID2407 tablet that my mother received to be able to use a USB 3G Vodafone Mobile Broadband dongle and I immediately understood that it was necessary to root the tablet...
Information about my tablet:
Polaroid 7 " MID2407PCE02
Hardware: gs702c
Model: MID2407
Build number: MID2407-user 4.4.2 KOT49H eng.cx.20140623.100409 release-keys
Build UTC date: 20140821-100653
Android v 4.4.2
Baseband v: Haier
Kernel v: 3.4.0+ (huangyingyuan @ srv-fw-compile3) (gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-70)) # 1 SMP Mon Jun 16, 2014 2:15:58 p.m. CT
SYSTEM (Android 4.4.2)
Model: MID2407
Manufacturer: POLAROID
Device: MID2407
Product: MID2407
Brand: Haier
Android Version: 4.4.2 (Kit Kat)
API Level: 19
Build ID: KOT49H
Fingerprint: Haier/MID2407/MID2407:4.4.2/KOT49H/eng.cx.20140623.100409:user/release-keys
PROCESSOR (ARMv7)
Processor: ARMv7 Processor rev 1 (v7l)
Cores: 2
Max Frequency: 1308 Mhz
Instruction Sets: armeabi-v7a, armeabi
SIMD Instructions: NEON
I already tested without success (and after ten malware!):
- All "onle Click Root App" as Kingo & co.
- RootGenius
- Impactor
- Bin4ry
- CF-Auto-Root (*)
- VRoot
- Odin (*)
- towelroot
- ...
(*) I have not found a file that works on my tablet model.
What works: adb, but I have that as a result of a "adb shell id"
Code:
uid = 2000 (shell) gid = 2000 (shell) ...
And then I don't know what to do .... ?script? where find script?
Mtk Droid Tools gives me this:
"In system already available: Android Debug Bridge Version 1.0.32
Code:
--- >>> <<< --- Connect to device
--- ERROR: --- TotalBytesPerChunk Not Found. Set default page / Spare = 2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
Again I am lost ...
I ask not fit all, but just tracks on where and what to look for to keep moving forward...
All suggestions are welcome, thank you!
Note: I'm on Windows, but I've also Linux, so if there are tools for Linux, I'm interested also ...
*edit*
Important note: I do not know how to access to the boot menu of my tablet ... I have a power button and a large volume +/- button, but nothing happens unless a "reset"! And I also have in the back a small hole but it's just a "reset" and there is no information on the website of polaroid.
Updates:
iRoot V1.7.9.2 => Fail
SRS One Click Root 4.7 => Fail
Root Genius 1.8.7 => Fail
But with SRS there is an ADB utility with I can reboot in recovery mode! So, I continue to search...
worked for me same tablet
androidxda com/download-root-genius
GolgothBe said:
Updates:
iRoot V1.7.9.2 => Fail
SRS One Click Root 4.7 => Fail
Root Genius 1.8.7 => Fail
But with SRS there is an ADB utility with I can reboot in recovery mode! So, I continue to search...
Click to expand...
Click to collapse
otij said:
worked for me same tablet
androidxda com/download-root-genius
Click to expand...
Click to collapse
Hello,
Fail for me :crying:
With me, at 27%, 47%, 50%, 80% ... My tablet reboot each time... Same for you?
Wich drivers use you? I use AdbDriverInstaller (Windows 7) and I have in device management:
Android Phone
---- Android Composite ADB Interface
It's strange that don't work for me
GolgothBe said:
Hello,
Fail for me :crying:
With me, at 27%, 47%, 50%, 80% ... My tablet reboot each time... Same for you?
Wich drivers use you? I use AdbDriverInstaller (Windows 7) and I have in device management:
Android Phone
---- Android Composite ADB Interface
It's strange that don't work for me
Click to expand...
Click to collapse
you must first remove /uninstall kinguser ( kingroot) from your phone
or the combination of two make it reboot perhaps? .
verify your removed any other thing that installed root (busybox supersu?) .
then retry .
i don't have reboot problem only with other tools like foldermount
that is not really fit to this kitkat 4.4.2 ...
you need let windows install the drivers hit start in windows then in the search field
type exactly
device installation settings
(if your windows is in another language you need to find out how to let windows
install drivers automatically) .
click on top result and let windows install drivers automatically
otij said:
you must first remove /uninstall kinguser ( kingroot) from your phone
or the combination of two make it reboot perhaps? .
verify your removed any other thing that installed root (busybox supersu?) .
then retry .
i don't have reboot problem only with other tools like foldermount
that is not really fit to this kitkat 4.4.2 ...
you need let windows install the drivers hit start in windows then in the search field
type exactly
device installation settings
(if your windows is in another language you need to find out how to let windows
install drivers automatically) .
click on top result and let windows install drivers automatically
Click to expand...
Click to collapse
It does not work with my tablet (are they really the same, I have a European model based on ARMv7) when installing drivers on Windows, I have an error "invalid data.".
It is certainly the problem, I'll try to find a solution without going through the ADB drivers ...
Thank you anyway
GolgothBe said:
It does not work with my tablet (are they really the same, I have a European model based on ARMv7) when installing drivers on Windows, I have an error "invalid data.".
It is certainly the problem, I'll try to find a solution without going through the ADB drivers ...
Thank you anyway
Click to expand...
Click to collapse
YEs our tablet are slightly different (mid2407cje01.133)
named "polaroid infinite" 7 inches
i am using win7 64 bits
but i think 32 will do same result.
you are using the wrong drivers.
(under android phone)
you need "ROMaster composite adb interface"
look in settings/storage/ 3 dots on top right /usb computer connection
if you are in usb large storage you need see 2 drives letters
if you are in mtp then you need see (under portable devices) mid2x07pj
(you can try change to MTP to root but
first let windows install the good drivers
As mentioned before)
the "root genius" here it goes to 15% then reboot then finish to
root .
= reboot only one time.
remove all drivers set windows to install drivers auto .
then plug tablet to a new usb port.
good luck
otij said:
YEs our tablet are slightly different (mid2407cje01.133)
named "polaroid infinite" 7 inches
i am using win7 64 bits
but i think 32 will do same result.
you are using the wrong drivers.
(under android phone)
you need "ROMaster composite adb interface"
look in settings/storage/ 3 dots on top right /usb computer connection
if you are in usb large storage you need see 2 drives letters
if you are in mtp then you need see (under portable devices) mid2x07pj
(you can try change to MTP to root but
first let windows install the good drivers
As mentioned before)
the "root genius" here it goes to 15% then reboot then finish to
root .
= reboot only one time.
remove all drivers set windows to install drivers auto .
then plug tablet to a new usb port.
good luck
Click to expand...
Click to collapse
Thank you so much! You gave me some good information!
1. I do not know why, but in my mind, when I put in "debuging" mode, I desactived systematically the MTP mode ... So I left the MTP activated with the debugging mode.
2. I have uninstalled all the drivers ...
3. I have downloaded "ROMaster composite adb interface" ...
4. I connected my tablet and Windows has recognized the MTP mobile devices ... but not for the "Android Phone / Tablet", then I have not found how to install the downloaded drivers ... I 've tested RootGenius 1.8.7, but has not found the right drivers ... I tested iRoot V1.7.9.2 (ex VRoot) and there it automatically installed the drivers ROMaster ... But the root procedure failed again ... I uninstalled the apps added by iRoot and rebooted my tablet.
5. I then launched RootGenius 1.8.7, reboot @ 34% @ ... Installation complete reboot ... 37% ... 41% ... 44% ... 63% ... reboot @ 67 % .... 70% ... 73% ... 76% ... 83% ... reboot ... what a thrill! Failed Root ... ... ... :crying:
I do not despair! I would have even if it takes me a year!
Note: in devices manager (with MTP + Debugging), I have:
- Android Phone
+ ROMaster Composite ADB Interface
- Mobile devices
+ MID2407
MID2407 give me access to SD in my tablet...
But with "ROMaster Composite ADB Interface", ADB doesn't work anymore... :silly:
once again do not try download drivers yourself .
let windows do it automatically .
Open Devices and Printers by clicking the Start button Picture of the Start button, and then, on the Start menu, clicking Devices and Printers.
Right-click the name of your computer, and then click Device installation settings.
Click Yes, do this automatically (recommended), and then click Save changes. Administrator permission required If you're prompted for an administrator password or confirmation, type the password or provide confirmation.
If Yes is already selected, click Cancel to close the dialog box.
A friend of mine has a tablet very similar to this and asked me to help root it because it has only 1.3ish gb of internal storage and because it has kitkat 4.4.2 apps cannot be installed on the sdcard... so please help us. rootgenius and towelroot can't root it so what should i try next?
Gracias