Hi,
so I rooted my new HDX and Safestrapped it. But the tablet drains more than it should, even if I don't use it at all...
I'm not really ablet to detect the cause of the drain, so I thought you guys might help me to find the problem.
It's very odd, that humblebundle seems to cause wakelocks, but I already stopped the app and greenified it... but still it causes wakelocks dafuq?
Here are some screenshots:
Mine rooted kindle with nexus rom wasnt able to deep sleep.
Battery was draining like hell, also after removing all 3rd party apps.
The only working solution was a clean rom installation.
Yeah but I am using the stock ROM... Since the Nexus ROM doesn't support LTE.
push
Getting insane.
Ty in adv for your possible help. Also, I do apologize if I am posting in the wrong thread, also, English is not my first language, I am from South America.
I am getting crazy trying to root my Kindle device (Amazon KFAPWI (Kindle Fire HDX 8.9) 3rd Gen. I tried kinda all... also, I am some familiar with flashing and rooting, but this is highly advanced, also, I am more or less familiar with ADB and SU stuff, but I do prefeer the scripts (thanks to the developers).
I saw several threads in XDA Developers, I did a lot of stuff but no luck.
This is the result of the rooting process with KFHDX TOOLKIT v0.95:
*************************
Executing Exploit...
Device detected: ()
Try to find address in memory...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x00008000 form iomem
Attempt fb_mem exploit...
Detected kernel physical address at 0x00008000 form iomem
Failed to open /dev/graphics/fb0 due to Permission denied
You need to manage to get remap_pfn_range addresses.
Failed to get prepare_kernel_cred addresses.
Failed to get commit_creds addresses.
Failed to get ptmx_fops addresses.
() is not supported.
Failed to setup variables.
Done!
If this is your first time rooting please install HDXposed and disable ota.
Presione una tecla para continuar . . .
Checking root...
Please grant root on your device!
/system/bin/sh: su: not found
Presione una tecla para continuar . . .
*****************************************
And I tried with Kindle Fire First Aide x64, here is the results:
******************************************
****************************************************************
* Root Failed. Please Run Option 21 Again, Sometimes *
* The Process Need To Be Repeated Several Time Before You Will *
* Successfully Root The Kindle. If This Method Fails More Than *
* 5 Times Try Option 20 Which Uses A Different Method To Root *
* The Kindle. *
****************************************************************
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
***********************************************
* We Are Now Performing A Cleanup Of The Temp *
* Directory. If you See The Following Error *
* The Directory Is Empty. The Error *
* rm failed for *, No such file or directory *
* Is Expected And Can Be Ignored. *
***********************************************
*************************************************
*Finally, If You Loose The Navigation Bars After*
*Rooting The Kindle, There Is A Easy Fix. Please*
*Drop To Command And Enter The Following Command*
* adb shell su -c rm /data/local.prop *
* If You Have To Execute This Command Pay Close *
* Attention To The Kindle For A SuperSU Or *
* Superuser Popup Or Request, Be Sure To Click *
* Allow Or Grant. This Will Solve The Missing *
* Navigation Bars! *
*************************************************
El sistema no puede encontrar la ruta especificada.
/system/bin/sh: busybox: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: busybox: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
mount: Operation not permitted
Presione una tecla para continuar . . .
*************************
If there is any help that will be very appreciated, or if any can show me the link of the proper thread.
Ty nice ppl!!!!
wjgranda said:
Ty in adv for your possible help. Also, I do apologize if I am posting in the wrong thread, also, English is not my first language, I am from South America.
I am getting crazy trying to root my Kindle device (Amazon KFAPWI (Kindle Fire HDX 8.9) 3rd Gen. I tried kinda all... also, I am some familiar with flashing and rooting, but this is highly advanced, also, I am more or less familiar with ADB and SU stuff, but I do prefeer the scripts (thanks to the developers).
I saw several threads in XDA Developers, I did a lot of stuff but no luck.
Click to expand...
Click to collapse
What firmware version do you have?
EncryptedCurse said:
What firmware version do you have?
Click to expand...
Click to collapse
Ty. I do not know how to identify the firmware version, the only that I know is that is running Fire OS 4.5.1.
wjgranda said:
Ty. I do not know how to identify the firmware version, the only that I know is that is running Fire OS 4.5.1.
Click to expand...
Click to collapse
If that's the case, then it's impossible.
At this time, you can only root on 14/13.3.2.6 or below.
EncryptedCurse said:
If that's the case, then it's impossible.
At this time, you can only root on 14/13.3.2.6 or below.
Click to expand...
Click to collapse
Okay, ty then for your info.
Uhhh yeah wrong thread.... This is about battery drain..
Related
this should work for the mini pro also
http://forum.xda-developers.com/showthread.php?t=824788
can anyone test it ??
please notice
if this doesnt work for you
please
replace the adb.exe and the dll s with the ones from the sdk
and it will fall into a loop, please wait 5-10 min
yep works
Yes it does! No need to replace adb files, btw.
yup works a treat
how did you guys run this. please post the step by step... thanks By the way I have x10 mini pro
Mini pro Rooted
Radik_PT said:
Mini pro Rooted
Click to expand...
Click to collapse
I need to root my phone to remap the keyboard since I flashed a Swedish/Finnish firmware.
Rooted. I was able to remap the keyboard to English. Thanks.
oh nice one folks, can't wait to get home tonight and try this on my mrs mini pro
@freya09
how'd you get it to work?
i keep getting stuck on the Running rageagainstthecage... prompt...
should i just wait?
just wait if i have the time i will make a better turial
Rooted! thanks!
@freya09
how did you change the keyboard layout?
Works for me on my mini (not pro) too
ozzy1212 said:
Rooted! thanks!
@freya09
how did you change the keyboard layout?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=8876102#post8876102
X10 Mini - Rooted, thanks
hi i managed to root the mini but can't get root for titanium backup. how is that possible?
X10 mini pro rooted, but taking screenshot bugs. Tryed ShootMe, drocap2 and more. But all screenshot end up like crap, I can really see anything on them?
img638 . imageshack . us / img638 / 1387 / snap20101101114935.png
Cant link to images yet so had to change the url abit
Hope anyone can check the url out anyway and help me, I dont know what todo
Hmm. I am stucked at:
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
337 KB/s (5392 bytes in 0.015s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
ROOTED
Getting mount path...
/dev/block/mtdblock0
OK
Remounting system with read-write access...
OK
Pushing su...
641 KB/s (26264 bytes in 0.040s)
OK
chmod su...
OK
Remounting system with read-only access...
OK
Installing superuser.apk...
Any tips? When I check the phone superuser is already installed.. Am I rooted?
easy
just wait then after <10 mins there will popup a message an it's rooted
For all who cant get the tool to work -
The superOneClick 1.5.1 requires an additional thing to be installed.
You can download 1.5.3 , i used this one and works well
STEPS :
*** Switch off the phone for a Min
*** Turn on and wait a minute so that the Indexing completes
*** Copy the superoneclick folder to C: ( Seems to work without this step but is faster )
*** Go to > settings > Applications > Development > Enable USB debugging
*** Right click on superoneclick.exe
*** Connect USB to Phone
*** Wait for 10 seconds ( Patients is virtue )
*** Click on root
< After this step , go have a coffee >
comeback after 5-10mts and see if its saying waiting for device...
*** Go again to USB debugging and disable and enable quickly
You have root
Additional steps -
If this is not working then all you have to do is , during the continuous loop , disable usb debugging > remove the cable > plug it in (still usb debugging disabled) > plug it out > Enable usb debugging > Connect
This should will work!
Hope this helps...
WARNING : YOU WILL NOT BE ABLE TO TAKE SCREENSHOTS WITH THIS ROOTING , SOME BUG.
pabling19 said:
Hmm. I am stucked at:
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
337 KB/s (5392 bytes in 0.015s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
ROOTED
Getting mount path...
/dev/block/mtdblock0
OK
Remounting system with read-write access...
OK
Pushing su...
641 KB/s (26264 bytes in 0.040s)
OK
chmod su...
OK
Remounting system with read-only access...
OK
Installing superuser.apk...
Any tips? When I check the phone superuser is already installed.. Am I rooted?
Click to expand...
Click to collapse
Which version of superoneclick are you using ? I had the same problem with 1.5.3 ( all i did was replace the superuser.apk from 1.5) ( not 1.5.1 )...
Rooting is complete only when it shows " Testing su" and you get a 'allow/block message from the superuser app on the phone!
I ran the Snowball Mod without a hitch. I then tried to run the update but it won't run for some reason. The window flashes some text quickly but then closes so I'm not even really sure why it's not working. Anyone run into this or have any ideas. Thanks in advance!
I haven't had the time to try out the snowball mod, yet -- so I can't offer any advice. But, I would post the issue in the development thread, that's where the most help will be.
Swyped from my B&N Nook Tablet.
Try running it from a command line to keep it up and be able to read any text.
Also, there is a log.txt, if you post that, it can be more helpful.
Yeah I was goin to but I don't have enough posts. I was hoping someone would see it here.
Well... if you post your log.txt and start it from a command-line window rather than double clicking the update.bat, then we can take a look at what's up.
Log file says:
Snowball is reporting: v2.0.2
NO PACKAGE AVAILABLE
Command line:
Snowball is reporting: v2.0.2
There does not appear to be a package for the version snowball is reporting.
Are you sure you're not reapplying an update?
Perhaps you are accidentally trying to apply an "outdate"?
Thanks a lot!
There is no v2.0.2 update package in the zip folder. I renamed v2.0.1 to v2.0.2 and ran. Not sure if this was a good thing to do or not. Any help or direction would be appreciated. Thanks.
No write permissions
Tried to install snowball mod from a macbook pro by just running the snowball.sh. Started up and the B&N stuff was all there, although it looked like it ran without a hitch.
Looked at the log file in the snowball-mod folder and saw a lot of "Read-only file system" business. The first few lines being:
unzip: can't open nook-update-package.zip, nook-update-package.zip.zip, nook-update-package.zip.ZIP^M
rm failed for nook-update-package.zip, Read-only file system^M
Installing nook-update-package...
cd: can't cd to /mnt/media/nook-update-package^M
sh: Can't open install^M
rm failed for /mnt/media/nook-update-package, No such file or directory^M
Click to expand...
Click to collapse
How do you suggest I get around that?
conundrum768 said:
I haven't had the time to try out the snowball mod, yet -- so I can't offer any advice. But, I would post the issue in the development thread, that's where the most help will be.
Swyped from my B&N Nook Tablet.
Click to expand...
Click to collapse
We need 10 legit posts before we are allowed to post in the dev forum
Robotronik said:
Tried to install snowball mod from a macbook pro by just running the snowball.sh. Started up and the B&N stuff was all there, although it looked like it ran without a hitch.
Looked at the log file in the snowball-mod folder and saw a lot of "Read-only file system" business. The first few lines being:
How do you suggest I get around that?
Click to expand...
Click to collapse
Huh... this is weird... /mnt/media should not be read-only... although, I suppose, perhaps if you had it USB mounted, it might end up read-only.
Ensure that you have Automatic USB mounting turned off before you run the script.
You can actually push this update via wifi if you mod the update.bat (or update.sh for linux users) file.
Just turn on ADB Wifi (I prefer adbWireless app) and add the following to your bat file:
Code:
echo Waiting for device...
[B]adb connect XXX.XXX.XXX.XXX:XXXX[/B]
adb wait-for-device
...
adb shell "chmod 755 /data/local/tmp/update-package.sh ; su -c /data/local/tmp/update-package.sh" >> log.txt
if exist reboot adb reboot
[B]adb connect XXX.XXX.XXX.XXX:XXXX[/B]
echo INSTALLATION SUCCESSFUL
Use your IPort given to you by your ADB Wifi app in place of XXXs. Then just run the .bat!
Run from cmd if you don't want the output to vanish right away.
cfoesch said:
Ensure that you have Automatic USB mounting turned off before you run the script.
Click to expand...
Click to collapse
Okay, that got me a little further. Now:
Extracting nook-update-package...
Archive: nook-update-package.zip
creating: nook-update-package/data/
unzip: can't set permissions of directory 'nook-update-package': Operation not permitted
unzip: exiting
Installing nook-update-package...
sh: Can't open install
Click to expand...
Click to collapse
More permissions issues...
Still posting here because I don't have the 10 total posts to go in the Dev forum...
Anyway, I did the factory reinstall, and reran the snowballmod update. It said the root was still there, so I commented out that check from the snowball.sh, reran the package and everything went swimmingly.
Now, for the update:
The terminal spits out this:
Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
7 KB/s (46 bytes in 0.006s)
Snowball is reporting: v2.0.2
.zipte-package-v2.0.2
There does not appear to be a package for the version snowball is reporting.
Are you sure you're not reapplying an update?
Perhaps you are accidentally trying to apply an 'outdate'?
Click to expand...
Click to collapse
Where the log file gives me:
Snowball is reporting: v2.0.2
NO PACKAGE AVAILABLE
Click to expand...
Click to collapse
The file "update-package-v2.0.2.zip" is in the directory. In the "update.sh" file replaced all instances of "${VERSION}" with "v2.0.2" and it seemed to work fine.
same
Robotronik said:
Still posting here because I don't have the 10 total posts to go in the Dev forum...
Anyway, I did the factory reinstall, and reran the snowballmod update. It said the root was still there, so I commented out that check from the snowball.sh, reran the package and everything went swimmingly.
Now, for the update:
The terminal spits out this:
Where the log file gives me:
The file "update-package-v2.0.2.zip" is in the directory. In the "update.sh" file replaced all instances of "${VERSION}" with "v2.0.2" and it seemed to work fine.
Click to expand...
Click to collapse
I AM HAVING THE SAME PROBLEM.MYBE..I need help some plz make a better howtos for dummies m
The first thing you need to do, if you have no clue what you're doing, is post the contents of the log file in the snowballmod folder.
The ".zipte-package-v2.0.2" seems to be related to adb shell "snowball-ver" returning DOS formatted text, even though you're in a *nix. I really did not expect this to happen with the linux and osx versions of adb, but apparently, they perform the same as cygwin... (cygwin I expected, after all, the adb.exe is a windows program). I will fix the update scripts to take that into account.
Code:
unzip: can't set permissions of directory 'nook-update-package': Operation not permitted
This message is reported by unzip when it is run by a non-root user on the /mnt/media partition.
You do _NOT_ have to run snowball-update though if you've installed snowball-mod fresh with the most recent version.
robtlebel said:
I AM HAVING THE SAME PROBLEM.MYBE..I need help some plz make a better howtos for dummies m
Click to expand...
Click to collapse
The changes made to the script were posted here:
Robotronik said:
Now, for the update:
The terminal spits out this:
Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
7 KB/s (46 bytes in 0.006s)
Snowball is reporting: v2.0.2
.zipte-package-v2.0.2
There does not appear to be a package for the version snowball is reporting.
Are you sure you're not reapplying an update?
Perhaps you are accidentally trying to apply an 'outdate'?
Where the log file gives me:
Snowball is reporting: v2.0.2
NO PACKAGE AVAILABLE
The file "update-package-v2.0.2.zip" is in the directory. In the "update.sh" file replaced all instances of "${VERSION}" with "v2.0.2" and it seemed to work fine.
Click to expand...
Click to collapse
I had the same issue with the name of the update file being called incorrectly: ".zipte-package-v2.0.2". With that output the script is looking for a file of that name and it's not finding it. I just changed the value of the variable ${VERSION} to v2.0.2 (since that was what was being reported by Snowball as my current version) and all worked after that.
Easy to fix temporarily:
-open "update.sh" in a text editor
-go to line 66 and change
VERSION=`awk '//{ print $2 }' snowball.version`
Click to expand...
Click to collapse
to
VERSION=v2.0.2
Click to expand...
Click to collapse
or whatever version yours shows to be running (v2.0.1, etc). Something tells me it might be important to input the correct current version number in
-save and close the file and rerun it.
EDIT: or wait until cfoesch fixes the scripts
Scripts should be updated. I changed the awk program from just "//{ print $2 }" to "//{ sub('\r', '', $2); print $2 }" ... this means that it works both ways... *insert your favorite "both ways" joke here*
It should also detect if you haven't turned off automount, and warn you about it. If the nook ends up rebooting, then it would tear the USB mount and could cause file corruption. I got around it by putting things in /data rather than /mnt/media, but then realized, if it has to reboot, then it could cause trouble. So better, to just warn them that automount was on, and quit out.
It also detects better if something went wrong in the installation process, and should report that installation has failed, rather than successful under all cases.
Things may have gotten broken in the process, so keep up the bug reports.
I just can't stop Nookin' Around.........god i need to sleep
I decided to check out the update.sh script (can only go so far currently since I have the latest update).
At least for me, (Ubuntu Linux 11.10) I figured something out about the $OSTYPE call to set the $adb variable. I could echo $OSTYPE in the terminal and got a response, but could not echo it in any scripts. Ended up finding the "uname -o" call and that seems to have gotten it to work, although the printout is different.
snowball-update# echo $OSTYPE
linux-gnu
snowball-update# uname -o
GNU/Linux
Changed lines 7 & 8 and seems to have worked:
case `uname -o` in
GNU*|linux*|Linux*)
Now this last part is probably something on my end but: update.sh: 62: ./adblinux: Permission denied
Thanks again for the work (and everyone else involved in rooting/hacking these things )
Indeed. $OSTYPE seems to be specific to bash, and not all sh implementations.
If you don't mind could you do this command and give me the output? "ls -l /bin/sh" and "sh --version" Those two commands should explain exactly which implementation of sh you have. (For instance, on the NT with snowball-mod, the sh is a minimal implementation, and does not support $OSTYPE. But on most OSes I've seen sh is actually a statically linked bash, as it is the most widely used shell scripting language.)
The case on that you provided though could be a poor choice, as GNU*) would match GNU/freebsd, or GNU/openbsd, or GNU/anykernel. Sure it is unlikely, but it is possible.
The permissions issue is not entirely your end, but it is an expected artifact of extracting from a zip file. Although, is suppose performing a chmod 755 on it prior to use would be a good idea in general.
I was really happy havin my ROOTED S.ony Tablet S, but unfortunately am not able to root again after a update.
Details:
S.ONY TABLET S 16GB (3G)
Country: India
Android Version: 3.2.1 (Release2)
Baseband Version: R3B01
Kernel Version: 2.6.36.3
Hop I have provided needed info.
Thanks for all the updates from "XDA"
Under "Kernel Version" mine says
2.6.36.3
[email protected] #1
What does it say on yours ?
If you have [email protected] #1 or above you are unable to root at this time.
kryddan said:
Under "Kernel Version" mine says
2.6.36.3
[email protected] #1
What does it say on yours ?
If you have [email protected] #1 or above you are unable to root at this time.
Click to expand...
Click to collapse
Thanks for replying bro:
Mine says :: [email protected] #1
And so i am unable to root right ???
So how can I root again ???
coolfire000 said:
Thanks for replying bro:
Mine says :: [email protected] #1
And so i am unable to root right ???
So how can I root again ???
Click to expand...
Click to collapse
That is correct. As of now you are not able to root your tablet, since you have build10. I guess all you can do now is wait and see if someone root the later builds or what for ICS and hope for root.
Not sure if you could try and flash an older rom with recovery, and therein get root?
kryddan said:
That is correct. As of now you are not able to root your tablet, since you have build10. I guess all you can do now is wait and see if someone root the later builds or what for ICS and hope for root.
Not sure if you could try and flash an older rom with recovery, and therein get root?
Click to expand...
Click to collapse
Ok thanks for the replies bro, will wait the things as am a newbie to all this things.
Hope to get ICS and rooted both.
Please . . . . .
Any idea about ICS ?
kryddan said:
Under "Kernel Version" mine says
2.6.36.3
[email protected] #1
What does it say on yours ?
If you have [email protected] #1 or above you are unable to root at this time.
Click to expand...
Click to collapse
I Have [email protected] #1 and I rooted my device following the instructions of the developers.
This will work on all build?
I have build 10. Thank you so much.
Can you provide me some link
rfreeman said:
I Have [email protected] #1 and I rooted my device following the instructions of the developers.
Click to expand...
Click to collapse
Hi can you please prove some link as am a bit newbie I hope you'll help
When I tried using Root 1.1, I got the following output
[*]
[*] Sony Tablet S root script v1.1 (Windows version)
[*] by Dan Rosenberg (@djrbliss).
[*]
[*] Before continuing, ensure USB debugging is enabled, that ADB
[*] is working properly, and that your tablet is connected via USB.
[*] You've got to have proper MPT driver to root your tab!
[*] (MPT driver - wpdmtp.inf included).
[*]
[*] WARNING: This exploit may result in wiping your /data partition,
[*] causing you to lose any applications and data on your tablet.
[*] There should be no risk of permanent damage to your device, but
[*] by running this script you accept all responsibility.
[*] +small mods/optimizations by Konrad Plaszczykowski (@condi)+
[*]
[*] FULLY AUTOMATIC - ROOT SHOULD TAKE ABOUT ~ 3min 10s.
[*] Press enter to root your tablet...
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] MTP driver has been disabled.
[*] Device found.
[*] Pushing log flooder to device...
failed to copy 'flood' to '/log/flood': Permission denied
Unable to chmod /log/flood: No such file or directory
[*] Preparing to append to packages.list...
link failed File exists
[*] Rebooting device...
[*] Waiting for tablet to reboot...... (~20s)
* daemon not running. starting it now *
* daemon started successfully *
error: protocol fault (no status)
[*] Attempting to move system package library directory...
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
error: device not found
error: device not found
[*] Rebooting device...
error: device not found
[*] Waiting for tablet to reboot...... (~40s)
[*] Attempting to insert fake local.prop entry...
link failed File exists
/log/flood: not found
[*] Rebooting device...
[*] Waiting for tablet to reboot...... (~40s)
[*] Attemping persistence...
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
[*] Cleaning up...
failed on '/data/data/com.google.android.location/lib.bak' - No such file or dir
ectory
[*] Rebooting...... (~35s)
[*] MTP driver has been enabled back.
[*] Exploit complete!
[*] Press any key to exit.
Click to expand...
Click to collapse
coolfire000 said:
Hi can you please prove some link as am a bit newbie I hope you'll help
Click to expand...
Click to collapse
Use S.onlyTablet.S v1.1 it has builtin check if your device is rootable.
condi said:
Use S.onlyTablet.S v1.1 it has builtin check if your device is rootable.
Click to expand...
Click to collapse
Thanks for reply bro, but getting the following error:
[*] Sony Tablet S root script v1.1 (Windows version)
[*] by Dan Rosenberg (@djrbliss).
[*]
[*] Before continuing, ensure USB debugging is enabled, that ADB
[*] is working properly, and that your tablet is connected via USB.
[*] You've got to have proper MPT driver to root your tab!
[*] (MPT driver - wpdmtp.inf included).
[*]
[*] WARNING: This exploit may result in wiping your /data partition,
[*] causing you to lose any applications and data on your tablet.
[*] There should be no risk of permanent damage to your device, but
[*] by running this script you accept all responsibility.
[*]
[*] +small mods/optimizations by Konrad Plaszczykowski (@condi)+
[*]
[*] FULLY AUTOMATIC - ROOT SHOULD TAKE ABOUT ~ 3min 10s.
[*] Press enter to root your tablet...
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] It looks that your device is [for now] not rootable...
[*] In your kernel version exploit vulnerability has been locked down...
[*] You need to wait for DEVs to find another way...
[*] Press any key to exit.
Click to expand...
Click to collapse
Solution to all
Check if u hav enabled usb debugging ... n unknown sources ..in the setting... u cn use tis file ... whch ucn find in the Android development area too..... nt responsible for any damage to ure device ...
coolfire000 said:
Thanks for reply bro, but getting the following error:
[*] It looks that your device is [for now] not rootable...[*] In your kernel version exploit vulnerability has been locked down...[*] You need to wait for DEVs to find another way...
[*] Press any key to exit.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Yep, exactly as it says. No solution for now. You need to wait
T0Tal_N00b said:
Check if u hav enabled usb debugging ... n unknown sources ..in the setting... u cn use tis file ... whch ucn find in the Android development area too..... nt responsible for any damage to ure device ...
Click to expand...
Click to collapse
No need to reupload tool, its available in official S.onyTablet.S thread.
br!
condi
Can build 9 be rooted?
Sent from my E16i using xda premium
mine says
Android Version: 3.2.1 (Release2)
2.6.36.3
[email protected] #1
it just hangs after daemon successful luanch... im using xp on vmware btw.
D00QLE said:
mine says
Android Version: 3.2.1 (Release2)
2.6.36.3
[email protected] #1
it just hangs after daemon successful luanch... im using xp on vmware btw.
Click to expand...
Click to collapse
does the XP on vmware detects ur tablet s?(like: adb devices (does this show u ur tablet? )) i was using Oracle VirtualMachine and i had to passthrough my USB devices to my guest OS. Perhaps u might want to check that(usb passthrough on vmware) out.
Maybe USB 1.1 only ?
I had to disable Oracle VirtualBox USB 2.0 support extension to get the tablet recognized by ADB in a Windows XP VM running under a Linux (Debian Squeeze) host...
Keep checking the build #
I purchased my Tablet S (refurbished) last week. It came with Build10. The first thing I did after turning it on was check to Build#.
However, after restarting a few times it reverted to Build5. I am not sure why that happened, but I was able to root using the All In One. I think someone else here had this happen also.
I *may* have run a Sony update on the previous restart. (It was late and I can't remember)
I guess you got it with FW 3.2 and Kernel build#10
Then you did a update to 3.2.1R2 with kernel build#5.
Could you remember?
zerod78 said:
does the XP on vmware detects ur tablet s?(like: adb devices (does this show u ur tablet? )) i was using Oracle VirtualMachine and i had to passthrough my USB devices to my guest OS. Perhaps u might want to check that(usb passthrough on vmware) out.
Click to expand...
Click to collapse
problem solved, it was the
echo 0x54c >> %HOMEPATH%\.android\adb_usb.ini
Click to expand...
Click to collapse
i though i had to add echo but no
This tool will root your device based on the debugfs root method developed by miloj.
Just download and unzip everything into a directory; then run RootDebugfs.bat from that directory (if you do not currently have the device drivers for your transformer, they are attached to this post, please install them, please use them to install your device before attempting the process).
Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are).
Helpful tip:
Make sure no other Android device is connected to your PC
It should look familiar since I took PrimeTime and gutted it, only keeping the menu options. Thanks to viperboy for that.
Original post is in the TF300 thread, http://forum.xda-developers.com/showthread.php?t=1704209
UPDATE 6/12/2012:
v1.1 - Added donation link for miloj
v1.2 - Fixed bug that caused it to stop while doing "debugfs", to cancel press Ctrl+c
v1.3 - Fixed bug where the id is not returned from the su test
v1.4 - Fixed bug introduced with v1.3
v1.5 - Fixed bug where you don't have to push the apk before calling install
6/13/2012
v1.6 - Fixed messaging (this is a cosmetic change)
v1.7 - Added a remove call on su prior to rooting for those who had root previously and it not longer works
v1.8 - Change the octal permissions to be 6755 instead of 4755
7/2/2012
v1.9 - Update superuser app and binary to the latest version available
XDA uploads are not working currently so I have uploaded the new version to here for now
https://skydrive.live.com/redir?resid=DC89975E3CE960E5!221
8/5/2012
v2.0 - Updated to include a kill for Asus sync as that seemed to be the biggest issue.
I have also made it more generic so that it can root more devices with the same util. This is done by scanning for the system partition automatically, thanks to rightonred for that suggestion. With the attachment labeled "generic" I have removed all asus references and drivers since they were causing issues with me being able to attach the zip to xda. Anybody who needs the drivers can download them from asus or from another xda post.
v2.1 - Added a pause while waiting for the device to restart to alleviate that nuisance.
v2.2 - Added message to ignore "File not found" message when trying to delete old su versions. Also updated message with the generic locations of settings on the tablet.
8/12/2012
v2.3 - Update su binary file (hopefully it may help some of the people with superuser app issues)
ASUS drivers can be downloaded from the ASUS site but some are not provided other than through the sync install. I have extracted out the drivers from that sync install and attached them to this post. These drivers will support most of the Asus Eee Pad family including TF101, TF201, TF300, TF700, ME171(MeMO), A66(Padfone), SL101(Slider), and a couple others.
No longer need a PadFone specific root util as the generic one should work for it as well.
Here is a version I put together for the Gallexy SII (but the generic one attached here should work fine)
http://forum.xda-developers.com/showpost.php?p=27611187&postcount=3
Latest Supported Versions:
v9.2.1.27 for the TF101 (ICS 4.0.3)
v9.2.2.6 for the TF101G (ICS 4.0.3) (3G version)
v9.4.2.28 for the TF201 (ICS 4.0.3)
v9.4.3.30 for the TF300T (ICS 4.0.3)
v9.4.4.40 for the TF300TG (ICS 4.0.3) (3G version)
v9.4.5.30 for the TF700T (ICS 4.0.3)
v9.18.8.41 for the PadFone (ICS 4.0.3)
These are the latest supported versions as far as I know, if I get any further input I will update this post.
Reported UNsupported Versions
v10.4.2.15 for the TF201 (JB 4.1.1)
v10.4.2.9 for the TF300T (JB 4.1.1)
v10.4.4.16 for the TF700T (JB 4.1.1)
v9.20.1.22 for the PadFone (ICS 4.0.4)
any one confirmed? what's the risk, if it doesnt work?
Currently in progress .... sitting at:
Step 2 - Rooting...
debugfs 1.42 (29-Nov-2011)
debugfs: (shows a flashing cursor)
My Prime has rebooted but still sitting at the above. Is this normal?
OK, now I'm getting nervous .... Anybody wanna help a Noob?
Aaronneal said:
any one confirmed? what's the risk, if it doesnt work?
Click to expand...
Click to collapse
The risk if it doesn't would should just be that you wouldn't have root.
We already have confirmation that the method works (so there should be no risk there). We just don't have confirmation that I didn't make a typo or other mistake when putting it all together.
Gremlin001 said:
Currently in progress .... sitting at:
Step 2 - Rooting...
debugfs 1.42 (29-Nov-2011)
debugfs: (shows a flashing cursor)
My Prime has rebooted but still sitting at the above. Is this normal?
Click to expand...
Click to collapse
How long has it been sitting there?
This is one of the points where I wasn't sure about since I had to pass input to debugfs through adb.
sparkym3 said:
How long has it been sitting there?
This is one of the points where I wasn't sure about since I had to pass input to debugfs through adb.
Click to expand...
Click to collapse
Currently 7 minutes...
If my memory serves me correctly, this is the point where it can take 10 - 15 minutes. Is that correct?
---------- Post added at 01:27 PM ---------- Previous post was at 01:12 PM ----------
Nope ... left it stalled at "debugfs:" for 20 minutes.
Ctrl-C'd out of the batch file. Doesn't seem to have hurt the Prime.
Gremlin001 said:
Currently 7 minutes...
If my memory serves me correctly, this is the point where it can take 10 - 15 minutes. Is that correct?
---------- Post added at 01:27 PM ---------- Previous post was at 01:12 PM ----------
Nope ... left it stalled at "debugfs:" for 20 minutes.
Ctrl-C'd out of the batch file. Doesn't seem to have hurt the Prime.
Click to expand...
Click to collapse
Thats what I was going to tell you. I have an update that I will put up. just forgot to put the absolute location. Please stand by.
Standing by ...
Now?
Now?
How 'bout now??
Maybe now?
Please try again. New version is v1.2
Running the updated bat as I type.... stand by
update #1 - sitting at the same spot.
Is it possible some of the files in the zip need to be in the MS-Win system32 folder?
sparkym3- you have a quick link to the win driver installation tutorial? Gonna try this but haven't used Windows in years. Got a lappy with xp on it.
texstar said:
sparkym3- you have a quick link to the win driver installation tutorial? Gonna try this but haven't used Windows in years. Got a lappy with xp on it.
Click to expand...
Click to collapse
Plug your prime into the computer with the Asus usb cable. When the Autoinstall drivers dialogue pops up, tell it you want to select the drivers. when it asks you to browse to the drivers, browse to the location where you unzipped sparky's and select it. WinXP does the rest.
Gremlin001 said:
Running the updated bat as I type.... stand by
update #1 - sitting at the same spot.
Is it possible some of the files in the zip need to be in the MS-Win system32 folder?
Click to expand...
Click to collapse
Can you tell me what the console displays after these lines. That should tell if all the files got copied over to the device.
adb push debugfs /data/local/
adb push debugfsinput /data/local/
Since debugfs actually runs, at least that one is copied over, my main concern is debugfsinput, this is the file that tells debugfs what to do.
Also, would you post a screenshot so I can see exactly what is happening, something might jump out if I can actually see it.
Screen shot won't do any good. Lettering is very dark. Here is a select all/copy of the output.
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Step 1 - Pushing files...
843 KB/s (1862336 bytes in 2.156s)
698 KB/s (22364 bytes in 0.031s)
7 KB/s (119 bytes in 0.015s)
Rebooting...
Step 2 - Rooting...
debugfs 1.42 (29-Nov-2011)
debugfs:
I'm exiting the batch file.
Gremlin001 said:
Screen shot won't do any good. Lettering is very dark. Here is a select all/copy of the output.
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Step 1 - Pushing files...
843 KB/s (1862336 bytes in 2.156s)
698 KB/s (22364 bytes in 0.031s)
7 KB/s (119 bytes in 0.015s)
Rebooting...
Step 2 - Rooting...
debugfs 1.42 (29-Nov-2011)
debugfs:
I'm exiting the batch file.
Click to expand...
Click to collapse
Would you just run this line manually and see if you get the same.
adb shell "/data/local/debugfs -w /dev/block/mmcblk0p1 < /data/local/debugfsinput"
I wish I had my prime i could test, all i have with me is an emulator.
On the emulator i get errors, but it still runs the correct commands then exits
C:\Android\android-sdk\platform-tools>adb shell "/data/local/debugfs -w /dev/block/mmcblk0p1 < /data/local/debugfsinput"
debugfs 1.42 (29-Nov-2011)
/dev/block/mtdblock0: Attempt to read block from filesystem resulted in short read while opening filesystem
debugfs: cd: Filesystem not open
debugfs: write: Filesystem not open
debugfs: set_inode_field: Filesystem not open
debugfs: set_inode_field: Filesystem not open
debugfs: set_inode_field: Filesystem not open
debugfs:
C:\Android\android-sdk\platform-tools>
C:\Documents and Settings\kcr\Desktop\Root>adb shell "/data/local/debugfs -w /de
v/block/mmcblk0p1 < /data/local/debugfsinput"
debugfs 1.42 (29-Nov-2011)
debugfs: debugfs: write: The file 'su' already exists
debugfs: debugfs: debugfs: debugfs:
C:\Documents and Settings\kcr\Desktop\Root>
Then it exits to dos shell
---------- Post added at 02:22 PM ---------- Previous post was at 02:14 PM ----------
Gotta run sparky. I'll be back to try again in about 4 hours. Thanks for giving it a go and setting up the bat. It will likely be something simple messing up - it usually is.
Gremlin001 said:
C:\Documents and Settings\kcr\Desktop\Root>adb shell "/data/local/debugfs -w /de
v/block/mmcblk0p1 < /data/local/debugfsinput"
debugfs 1.42 (29-Nov-2011)
debugfs: debugfs: write: The file 'su' already exists
debugfs: debugfs: debugfs: debugfs:
C:\Documents and Settings\kcr\Desktop\Root>
Then it exits to dos shell
Click to expand...
Click to collapse
if the file already exists, then that may be a problem.
you could try this to remove the existing file:
Code:
adb shell
/data/local/debugfs -w /dev/block/mmcblk0p1
rm /xbin/su
quit
exit
This should clear out any current su file that's in there and then try that line again.
Hopefully somebody else can come in and confirm they are seeing the same because I am useless for trying things without my device.
sparkym3 said:
Latest Supported Versions:
v9.4.2.21 for the TF201
v9.2.1.17 for the TF101
v9.4.3.29 for the TF300
These are the latest supported versions as far as I know, if I get any further input I will update this post.
The latest update for TF201 v9.4.2.28/29 due out within a day or 2 has been reported to not have any of the known root exploits, do NOT upgrade to the latest build prior to rooting or you may be out of luck.
Click to expand...
Click to collapse
I'm already out of luck
so i can't even downgrade either, if I wanted to, huh? .28 blues..lol
Ok I'm in if you are still around sparkym3.
Running v1.3 bat gets me to...
Step 2 -- Rooting...
debugfs 1.42
debugfs: Allocated inode: 1369
debugfs: su: File not found by ext2_loopback
debugfs: su: File not found by ext2_loopback
debugfs: su: File not found by ext2_loopback
debugfs:
Rebooting...
Testing superuser...
/system/bin/sh: /system/xbin/su: not found
uid and gid should both be 0.
Are they? (y/n):
I'm stopped here. not sure how to proceed.
Hello,
I have been struggling to root my new tablet for 2 days now without success.
I also have apple devices and jailbreak them for years without any problem but today I am completly stucked.
I am unable to intall correctly the ADB Interface... It is impossible.
I tried to install, desinstall, reinstall many times the usb drivers. Restart the computer many times...
I tried the SDK android tool with installation of the USB driver package v7.
I tried with PDANet.
I tried with the package of Xboxepert guy who posted a very easy way rooting process on xda developper...
Nothing is working.
I still have an exclamation point on the device !!
When I try to install the drivers, it always tells me (sorry for my translation, I am french !!):
"An error occurs during the hardware installation
A service installation section of the INF file is not valid".
I am under XP 32 bits SP3.
I would be very happy if someone knew what to do or help me to go through...
It is driving me crazy ..
Thank you for your help.
Christophe
Rooting problem
It seems that I succeed to set-up the ADB interface.
I can interact with my device with adb.exe in the command prompt shell, things like "adb shell" ...
But I can not root, using motochopper or the tool form xboxepert..
I tried with SRSRoot tool too.
I have made a complete restore of my device from scratch....
Always the same:
cannot stat 'pwn': No such file or directory
Unable to chmod /data/local/tmp/pwn: No such file or directory
[*] Pushing root tools...
1149 KB/s (91980 bytes in 0.078s)
1823 KB/s (1867568 bytes in 1.000s)
1893 KB/s (969701 bytes in 0.500s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
[*] Rooting device
/system/bin/sh: /data/local/tmp/pwn: not found
[*] Cleaning up...
rm failed for /data/local/tmp/pwn, No such file or directory
[*] Exploit complete. Rebooting device.[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Flashing CWM Touch Recovery!
1740 KB/s (7045120 bytes in 3.953s)
/system/bin/sh: su: not found
[*] All Done! Final reboot!
solved
I don't know how I made it but I tried a last time and it worked.
Envoyé depuis mon M470BSA en utilisant Tapatalk 4 Beta