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.
Related
I have Frankensteined some scripts and binaries together with some bash programming and created a linux script that will sticky root and/or overclock your evo 3d.
Just trying to give back to the community.
Hope that all of you linux/MAC users like it...
BTW the defaults for overclocking are 33 for the multiplier and 1375000 for the voltage.
P.S. you have to have adb in your $PATH
Version 1.2 is up and should fix ubuntu and mac issues. Please test and if it works for you press thanks.
Thanks
l33tlinuxh4x0r
Got error:
rootme: 14: Syntax error: "(" unexpected
I'm on Ubuntu 11.04 64bit
vboyz103 said:
Got error:
rootme: 14: Syntax error: "(" unexpected
I'm on Ubuntu 11.04 64bit
Click to expand...
Click to collapse
does Jermey's script work for you?
l33tlinuxh4x0r said:
does Jermey's script work for you?
Click to expand...
Click to collapse
Nope, I tried his as well and didn't work, same error.
vboyz103 said:
Nope, I tried his as well and didn't work, same error.
Click to expand...
Click to collapse
must be something to do with the version of linux that you are running or maybe an enviroment variable that you have set.
Are you using bash or another shell?
simple solution to fix these scripts if you are having that issue
is to open the script in a txt editor and remove every instance of the word "function" from the script.
I added the attached file with it done.
Note: Remove ".txt" from the file and replace it with the other one.
I belive you are missing the command to push the kernel to the tmp folder
tigereyeslalo said:
I belive you are missing the command to push the kernel to the tmp folder
Click to expand...
Click to collapse
You are absolutly right sorry about that... I have attached an updated zip. This should also fix the ubuntu issues with the function command.
mine seems to hang when I do this now.
---------- Running Fre3vo please wait ----------
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
I've used J.ermey's script without any issues.
using on mac
after I hit control-C, seems like it runs through everything.
------------ Setting up directories ------------
--------- Installing su,busybox,sqlite ---------
3430 KB/s (1448982 bytes in 0.412s)
2684 KB/s (22228 bytes in 0.008s)
4633 KB/s (1120536 bytes in 0.236s)
------------- Installing Superuser -------------
5287 KB/s (398990 bytes in 0.073s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
------------------------------------------------
I can get the root shell via adb. But nothing requiring root works on the phone.
I've tried rebooting the phone multiple times
lmbebo said:
mine seems to hang when I do this now.
---------- Running Fre3vo please wait ----------
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
I've used J.ermey's script without any issues.
using on mac
after I hit control-C, seems like it runs through everything.
------------ Setting up directories ------------
--------- Installing su,busybox,sqlite ---------
3430 KB/s (1448982 bytes in 0.412s)
2684 KB/s (22228 bytes in 0.008s)
4633 KB/s (1120536 bytes in 0.236s)
------------- Installing Superuser -------------
5287 KB/s (398990 bytes in 0.073s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
------------------------------------------------
I can get the root shell via adb. But nothing requiring root works on the phone.
I've tried rebooting the phone multiple times
Click to expand...
Click to collapse
It looks like you are killing the fre3vo script which explains why you aren't getting root.
not sure why it doesn't work on mac... I know that macs are unix and this script is mostly copied from J.eremy so if his works so should mine but it is intended for linux not mac so maybe that is why it doesn't work not sure though.
I left the script running for 10 mins which is why I'm killing it. It was just hanging.
On J.ermey's script, it was over very quick.
lmbebo said:
I left the script running for 10 mins which is why I'm killing it. It was just hanging.
On J.ermey's script, it was over very quick.
Click to expand...
Click to collapse
I think that I found the issue... I had "" around the adb command and mac apparently didn't like it... Fixed now should work on mac and linux flawlessly
Check first post for latest version (1.2)
aha! many thanks!
it works now. As does Titanium backup (which I was unable to get to work on other scripts)
How do i run this on a mac? Not sure where to begin.....
Please help. Thanks
Getting error when overclocking.
TURN OFF DISPLAY AND LEAVE IT OFF UNTIL SCRIPT COMPLETES!
Press any key when screen is off...
What multiplier would you like to use to overclock? (press enter for default)
What voltage would you like to use to overclock? (press enter for default)
Overclocking now... (use setcpu to adjust clock speeds)
1173 KB/s (5832 bytes in 0.004s)
insmod: can't insert '/data/local/tmp/8x60_oc.ko': invalid module format
Complete, Press ENTER to go back
k wizzle said:
Getting error when overclocking.
TURN OFF DISPLAY AND LEAVE IT OFF UNTIL SCRIPT COMPLETES!
Press any key when screen is off...
What multiplier would you like to use to overclock? (press enter for default)
What voltage would you like to use to overclock? (press enter for default)
Overclocking now... (use setcpu to adjust clock speeds)
1173 KB/s (5832 bytes in 0.004s)
insmod: can't insert '/data/local/tmp/8x60_oc.ko': invalid module format
Complete, Press ENTER to go back
Click to expand...
Click to collapse
this is not a problem with the script... it has to do with the version of the kernel that you have... the sensation and pre ota evo 3d's need a different kernel module... you can find the different modules here http://forum.xda-developers.com/showthread.php?t=1158951
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 looking up the partition layout of the Galaxy S III while I stumbled upon this problem.
The first time you run a command in 'adb shell' everything is fine, but when you try to run a second command, it just hangs. It doesn't crash, it just hangs.
So, I tried to find out what could be wrong, by doing the following: Instead of going into the shell itself, I just entered a semi-random command 'adb shell mount', which returned the normal result.
Then, I typed 'adb shell' and guess what? It returns a commonly known error: 'error: protocol fault (status 72 6f 6f 74?!)'
The status code is HEX, which translates to: 'error: protocol fault (status root?!)'
So I suppose this has something to do with the fact that my SGS3 is rooted.
I don't feel like unrooting it, but if someone would be so kind to test this on an unrooted SGS3 and report back the results here so we can investigate this further that would be greatly appreciated.
it works without any error.
do you know what to backup which contains kernel and ramdisk ?
Mine is rooted, with Omega Rom V3 and everything works perfect with adb.
Cranck said:
Mine is rooted, with Omega Rom V3 and everything works perfect with adb.
Click to expand...
Click to collapse
Have you tried multiple shell commands? I know adb functions, but it's about using adb shell.
I'm on the stock rom, rooted manually with CF's insecure kernel by the way.
I'm not sure this is related, but there is some very suspicious new functionality in the FactoryTest.apk, called "SysScope". Its some kind of service checking and verifying the authenticity of "something". But I have no idea of what, only that a related java file (ResultCode.class [sysscope.service] contain the following code segment:
Code:
[SIZE=2] arrayOfResultCode[0] = OK;
arrayOfResultCode[1] = ADB_RUNNING_AS_ROOT;
arrayOfResultCode[2] = PARTITION_TAMPERED;
arrayOfResultCode[3] = ROOT_PROCESS_FOUND;
arrayOfResultCode[4] = DANGEROUS_FILE_DETECTED;
arrayOfResultCode[5] = NOT_OFFICIAL_BINARY;
[/SIZE]
Then it looks for SysScope files in the SysScopeVerifyer.class like this:
Code:
[SIZE=2]/data/app/com.sec.android.app.sysscope-1.apk
/data/app/com.sec.android.app.sysscope-2.apk[/SIZE]
I suggest you to back these up, and then replace them, with empty files of the same name, and see what happens.
I have the exact same problem on the GS2, OneX, and OneS. I have no problem shelling into the devices using another system, but on one of my computers I have the same issue. Windows 7 64bit with jdk7 installed.
Also, I enabled adb trace to see what was being returned: set ADB_TRACE=all
-Entering ls three times on the OneX, the first time works correctly
Code:
ls
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): post uni
x_read(fdi=0,...)
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): pre unix
_read(fdi=0,...)
system/core/adb/commandline.c::read_and_dump():read_and_dump(): post adb_read(fd
=101): len=5
ls
system/core/adb/commandline.c::read_and_dump():read_and_dump(): pre adb_read(fd=
101)
system/core/adb/commandline.c::read_and_dump():read_and_dump(): post adb_read(fd
=101): len=32
acct
cache
config
cwkeys
d
system/core/adb/commandline.c::read_and_dump():read_and_dump(): pre adb_read(fd=
101)
system/core/adb/commandline.c::read_and_dump():read_and_dump(): post adb_read(fd
=101): len=318
data
default.prop
dev
devlog
etc
firmware_dsps
firmware_q6
firmware_radio
firmware_wcnss
init
init.elite.rc
init.goldfish.rc
init.qcom.rc
init.qcom.sh
init.rc
init.target.rc
init.usb.rc
mnt
proc
root
sbin
sdcard
sys
system
tombstones
ueventd.goldfish.rc
ueventd.rc
vendor
[email protected]:/ $ system/core/adb/commandline.c::read_and_dump():read_and_dump()
: pre adb_read(fd=101)
ls
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): post uni
x_read(fdi=0,...)
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): pre unix
_read(fdi=0,...)
ls
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): post uni
x_read(fdi=0,...)
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): pre unix
_read(fdi=0,...)
Can anyone advise if the Huawei-U8665 (At&T Fusion 2) can be rooted? It has Android version 2.3.6. I tried with the easy OneSuperClick approach but didn't work-wouldn't recognize device. Thanks.
ptbear said:
Can anyone advise if the Huawei-U8665 (At&T Fusion 2) can be rooted? It has Android version 2.3.6. I tried with the easy OneSuperClick approach but didn't work-wouldn't recognize device. Thanks.
Click to expand...
Click to collapse
Did you ever figure out how to root?
Why don't you Google search other huawei devices and look for root kit running Gingerbread
Sent from my LGL35G using xda premium
903tex said:
Why don't you Google search other huawei devices and look for root kit running Gingerbread
Sent from my LGL35G using xda premium
Click to expand...
Click to collapse
I have, and I haven't been able to find anything. Superoneclick, z4root and unlock root only work for 2.3 and the Fusion 2 is running 2.3.6 and while trying to use those tools to root, it always hangs when trying to gain shell root.
Have to wait til somebody with skills makes a exploit for the fusion.
Sent from my LGL35G using xda premium
Patience is a virtue I supposed. I should've just bought a galaxy player I guess.
I seem to have acquired root, but I had to use fastboot to restore the rom. Sry i cant be more specific because tthis touchscreen took a hard fall..... post later thx -RFE
RFE said:
I seem to have acquired root, but I had to use fastboot to restore the rom. Sry i cant be more specific because tthis touchscreen took a hard fall..... post later thx -RFE
Click to expand...
Click to collapse
i keep posting to the wrong threas. sry
hint hint....... u need the diag drivers which are not posted but i should have a recovery img ready soon (one that re-installs SU on each boot
RFE said:
i keep posting to the wrong threas. sry
hint hint....... u need the diag drivers which are not posted but i should have a recovery img ready soon (one that re-installs SU on each boot
Click to expand...
Click to collapse
these are the right drivers for adb
RFE said:
these are the right drivers for adb
Click to expand...
Click to collapse
hi guys, here is a copy of the latest and greatest adb driver sets. with this driver set (folder called 'Driver' if you don't need adb).
I now HAVE ROOT on the phone by using fastboot and modifying the recovery image. I will post these once I strip it of all my personal info. Please try your own methods as well. I have attached a screenshot of what your (x86) device manager should look like once you correctly installed the drivers.
Best wishes & happy rooting
RFE said:
hi guys, here is a copy of the latest and greatest adb driver sets. with this driver set (folder called 'Driver' if you don't need adb).
I now HAVE ROOT on the phone by using fastboot and modifying the recovery image. I will post these once I strip it of all my personal info. Please try your own methods as well. I have attached a screenshot of what your (x86) device manager should look like once you correctly installed the drivers.
Best wishes & happy rooting
Click to expand...
Click to collapse
Here is a clip of adb working. I am trying to get clockworkmod working, but it is difficult because of all this new 2.3.6 securiy (my last phone was a 2.3.4)
D:\android-sdk-windows\platform-tools>adb tcpip 8888
restarting in TCP mode port: 8888
D:\android-sdk-windows\platform-tools>adb root
error: device not found
D:\android-sdk-windows\platform-tools>adb usb
error: device not found
D:\android-sdk-windows\platform-tools>adb get-state
unknown
D:\android-sdk-windows\platform-tools>adb shell
$ exit
exit
D:\android-sdk-windows\platform-tools>adb reboot-bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
D:\android-sdk-windows\platform-tools>adb root
adbd cannot run as root in production builds
(you must copy certain files to the device via adb push/pull & you can have root too)
---------- Post added at 04:14 PM ---------- Previous post was at 03:46 PM ----------
I dumped the entire phone in user mode and this is what you get:
(let me know if you need anything)
Device connected.
Default pull path saved.
Detailed phone info: RECOVERY ACTIVE
Pulling file or directory from data/app/... successful.
Pulling file or directory from data/app_private/... failed.
Pulling file or directory from data/data/... successful.
Pulling file or directory from data/local/... successful.
Pulling file or directory from data/nv/... failed.
Pulling file or directory from data/system/... successful.
Pulling file or directory from system/app/... failed.
Pulling file or directory from system/bin/... successful.
Pulling file or directory from system/etc/init.d/... failed.
Pulling file or directory from system/fonts/... successful.
Pulling file or directory from system/framework/... successful.
Pulling file or directory from system/media/... successful.
Pulling file or directory from system/usr/keylayout/... successful.
\android-sdk-windows\f2pull1
05 <DIR> .
05 <DIR> ..
56 1,697 7k_handset.kl
56 3,894 7x27a_kp.kl
43,652 abtfilt
51 0 accounts.db-journal
55,168 akmd8962
55,168 akmd8975
191 am
313 am.jar
27,864 am.odex
5,520 amploader
313 android.policy.jar
248,448 android.policy.odex
313 android.test.runner.jar
193,944 android.test.runner.odex
58,132 applypatch
5,720 app_process
71,736 ast-mm-vdec-omx-test7k
17,076 ATFWD-daemon
24,064 athtestcmd
631,588 ath_supplicant
<DIR> audio
56 245 AVRCP.kl
5,504 battery_charging
5,292 bluetoothd
199 bmgr
313 bmgr.jar
13,784 bmgr.odex
23,208 bootanimation
23,192 bootanimationex
313 bouncycastle.jar
778,624 bouncycastle.odex
10,196 brcm_patchram_plus
33,428 bridgemgrd
380,435 btld
5,556 bugreport
5,360 callife
145,156 charge
14,404 CKPD-daemon
6,880 Clockopia.ttf
22,788 cnd
313 com.android.location.provider.jar
7,352 com.android.location.provider.odex
1,671 com.cequint.platform.jar
1,984 com.cequint.platform.odex
313 com.google.android.maps.jar
388,168 com.google.android.maps.odex
313 com.qualcomm.location.vzw_library.jar
46,000 com.qualcomm.location.vzw_library.odex
120,332 compassd
313 core-junit.jar
23,952 core-junit.odex
22,926 core.jar
4,801,784 core.odex
5,520 dalvikvm
109,504 dbus-daemon
18,112 debuggerd
9,796 dexopt
44,612 dhcpcd
102,056 dhd
5,648 diag_klog
5,568 diag_mdlog
108,820 dnsmasq
194,488 DroidSans-Bold.ttf
190,776 DroidSans.ttf
35,880 DroidSansArabic.ttf
3,725,920 DroidSansFallback.ttf
23,076 DroidSansHebrew.ttf
119,380 DroidSansMono.ttf
36,028 DroidSansThai.ttf
185,228 DroidSerif-Bold.ttf
190,304 DroidSerif-BoldItalic.ttf
177,560 DroidSerif-Italic.ttf
172,916 DroidSerif-Regular.ttf
56,468 ds_fmc_appd
34,544 dumpstate
9,812 dumpsys
5,548 dvz
204,900 e2fsck
313 ext.jar
1,393,000 ext.odex
06 60,920,794 fastboot-tools-full-copy-HUAWEI-U8665-EN-NONIG
rar
9,968 filebackup
14,084 fmconfig
360,282 framework-res-hwext.apk
10,368,022 framework-res.apk
12,413 framework.jar
9,007,376 framework.odex
22,640 fsck_msdos
35,028 ftmdaemon
5,604 gzip
27,652 hciattach
5,684 hci_dev_state
277,652 hostapd
22,420 hostapd_cli
5,440 hostapd_wps
9,920 hwvefs
194 ime
313 ime.jar
6,720 ime.odex
201 input
313 input.jar
4,408 input.odex
18,324 installd
133,556 ip
36,052 iperf
216,188 ipth_dua
313 javax.obex.jar
60,848 javax.obex.odex
10,112 keystore
9,692 kmsgcat
39,416 linker
13,952 load_oemlogo
44,484 loc_api_app
14,052 logcat
9,760 logwrapper
5,504 mediaserver
17,408 mm-abl-daemon
13,184 mm-abl-test
18,092 mm-adec-omxaac-test
22,156 mm-adec-omxadpcm-test
22,172 mm-adec-omxamr-test
22,288 mm-adec-omxamrwb-test
22,236 mm-adec-omxevrc-hw-test
26,172 mm-adec-omxmp3-test
22,236 mm-adec-omxQcelpHw-test
22,268 mm-adec-omxvam-test
22,204 mm-adec-omxwma-test
5,532 mm-adspsvc-test
18,108 mm-aenc-omxaac-test
13,852 mm-aenc-omxamr-test
18,252 mm-aenc-omxevrc-test
18,252 mm-aenc-omxqcelp13-test
5,408 mm-audio-alsa-test
15,996 mm-audio-ctrl-test
5,552 mm-audio-mvs-test
88,820 mm-audio-native-test
22,188 mm-jpeg-dec-test
18,096 mm-jpeg-enc-test
5,456 mm-qcamera-daemon
62,308 mm-qcamera-test
10,652 mm-qcamera-testsuite-client
26,464 mm-vdec-omx-test
63,620 mm-venc-omx-test
9,800 modempre
205 monkey
313 monkey.jar
89,864 monkey.odex
18,308 mtpd
5,552 ndc
5,660 netcfg
47,764 netd
76,324 netmgrd
5,520 nl_listener
5,376 oeminfo_test
5,584 oem_rpc_svc
32,616 omx_tests
51 6,374 packages.list
51 111,973 packages.xml
18,692 pand
18,112 pcm-bridge
67,860 pcscd
524,288 Phonesky.apk
2,870,672 Phonesky.odex
11,032 PicoTts.apk
12,640 PicoTts.odex
26,720 ping
5,540 PktRspTest
6,916,572 PlusOne.apk
5,932,352 PlusOne.odex
191 pm
313 pm.jar
28,392 pm.odex
3,757,662 pops_atnt.apk
1,511,304 pops_atnt.odex
18,096 port-bridge
700,557 PotterUnlock.apk
77,128 PotterUnlock.odex
139,540 pppd
56,764 ProjectMenuAct.apk
94,408 ProjectMenuAct.odex
313 qcnvitems.jar
125,648 qcnvitems.odex
313 qcrilhook.jar
12,544 qcrilhook.odex
86,836 qmiproxy
33,652 qmuxd
9,760 qrngd
5,564 qrngtest
56 1,950 qwerty.kl
56 2,601 qwerty_m660.kl
142,516 racoon
26,252 radish
57,140 recEvent
9,856 rild
5,588 rmt_oeminfo
10,220 rmt_storage
59,832 run-as
5,392 schedtest
9,748 sdcard
42,404 sdptool
9,860 service
9,956 servicemanager
313 services.jar
1,732,544 services.odex
6,792,432 Settings.apk
883,048 Settings.odex
33,309 SettingsProvider.apk
65,176 SettingsProvider.odex
974,859 SetupWizard.apk
92,928 SetupWizard.odex
82,840 sh
15,014 ShopMusic.apk
3,264 ShopMusic.odex
23,176 shutdownanima
9,828 sleeplogcat
3,858 SmartcardService.apk
28,064 SmartcardService.odex
1,704,489 SoundRecorder.apk
54,480 SoundRecorder.odex
313 sqlite-jdbc.jar
147,632 sqlite-jdbc.odex
81,284 Stk.apk
67,312 Stk.odex
153,434 Street.apk
323,656 Street.odex
5,456 surfaceflinger
56 1,999 surf_keypad.kl
192 svc
313 svc.jar
8,400 svc.odex
10,239,938 Swype.apk
647,512 Swype.odex
609,667 SystemUI.apk
191,344 SystemUI.odex
5,472 system_server
811,688 Talk.apk
514,136 Talk.odex
35,024 TaskManager.apk
20,472 TaskManager.odex
19,817 TelephonyProvider.apk
165,968 TelephonyProvider.odex
30,452 testpcsc
35,268 test_diag
3,444,531 tn70-android-att-7121044.apk
2,756,552 tn70-android-att-7121044.odex
81,544 toolbox
559,282 ToolBox.apk
24,400 ToolBox.odex
15,030 TtsService.apk
37,544 TtsService.odex
51 58 uiderrors.txt
1,580,748 UNO_DEMO_HUAWEI_U8665_EN_NONIGP_ATT_TS_102.apk
552,136 UNO_DEMO_HUAWEI_U8665_EN_NONIGP_ATT_TS_102.ode
5,440 usbhub
5,520 usbhub_init
13,689 UserDictionaryProvider.apk
16,504 UserDictionaryProvider.odex
27,284 v4l2-qcamera-app
5,552 vdc
1,125,753 Videos.apk
1,392,992 Videos.odex
3,171,658 vlingo.apk
2,772,800 vlingo.odex
91,893 VoiceDialer.apk
87,256 VoiceDialer.odex
1,485,636 VoiceSearch.apk
2,391,016 VoiceSearch.odex
64,100 vold
19,377 VpnServices.apk
32,648 VpnServices.odex
9,792 wiperiface_v01
109,465 WISPr_57_Android22_prepaid.apk
66,824 WISPr_57_Android22_prepaid.odex
9,732 wlan_detect
10,416 wlan_tool
408,520 wl_4330
92,564 wmiconfig
31,284 wpa_cli
372,356 wpa_supplicant
1,937,546 YouTube.apk
1,660,664 YouTube.odex
1,973,436 YPMAndroid-release_preload3_6_2990.apk
1,531,032 YPMAndroid-release_preload3_6_2990.odex
282 File(s) 178,328,187 bytes
Click to expand...
Click to collapse
GOT ROOT? Fusion 2 finally rooted!
RFE said:
hi guys, here is a copy of the latest and greatest adb driver sets. with this driver set (folder called 'Driver' if you don't need adb).
I now HAVE ROOT on the phone by using fastboot and modifying the recovery image. I will post these once I strip it of all my personal info. Please try your own methods as well. I have attached a screenshot of what your (x86) device manager should look like once you correctly installed the drivers.
Best wishes & happy rooting
Click to expand...
Click to collapse
Here is the superuser binary along with a working adb packaged together. Just push the apk to the phone once you have the drivers installed.
I shouldn't have to spell it out for you how to apply this root kit.
Enjoy and don't abuse!
>adb wait-for-device
adb server is out of date. killing...
* daemon started successfully *
>adb shell mount -o rw,remount rootfs /
>adb shell busybox --install -s /vendor/bin
>adb install ./Lib/Superuser.apk
2458 KB/s (196640 bytes in 0.078s)
pkg: /data/local/tmp/Superuser.apk
Success
Looking for the rar password
Thanks for posting, however its asking for a password.
RFE said:
Here is the superuser binary along with a working adb packaged together. Just push the apk to the phone once you have the drivers installed.
I shouldn't have to spell it out for you how to apply this root kit.
Enjoy and don't abuse!
>adb wait-for-device
adb server is out of date. killing...
* daemon started successfully *
>adb shell mount -o rw,remount rootfs /
>adb shell busybox --install -s /vendor/bin
>adb install ./Lib/Superuser.apk
2458 KB/s (196640 bytes in 0.078s)
pkg: /data/local/tmp/Superuser.apk
Success
Click to expand...
Click to collapse
Rar Password?
Will you either release the rar password or post and non encrypted link please?
I thought I mentioned the password is xda-developers.com ... something easy to overlook if you are skimming the forums.
EDIT: attached recovery image
RFE said:
I thought I mentioned the password is xda-developers.com ... something easy to overlook if you are skimming the forums.
EDIT: attached recovery image
Click to expand...
Click to collapse
I got this phone for my daughter and wanted to root to make it seem like an ordinary phone to AT&T. That way they won't charge me for having a smart phone. Anyway, it doesn't seem a lot of folks are rooting the Fusion 2. How has yours behaved since you've rooted? Any problems?
Spurs_Redskins said:
I got this phone for my daughter and wanted to root to make it seem like an ordinary phone to AT&T. That way they won't charge me for having a smart phone. Anyway, it doesn't seem a lot of folks are rooting the Fusion 2. How has yours behaved since you've rooted? Any problems?
Click to expand...
Click to collapse
Even if out root it that won't stop att from seeing it as a smart phone
Batcom2
Whenever I try to push the Superuser.apk into the Fusion 2, it keeps saying that
Code:
"failed to copy 'superuser.apk' : read-only file system
Okay, so I've obtained root, but I bricked my phone using Rom Toolbox Pro. Can someone please backup their /system folder, so I may try to unbrick my device?
Sent from my NookColor using xda app-developers app
yup im a friggin moron flashed that recovery.img to my system out of habit ended up bricking mine too. can someone please upload a stock system.img as well as the original recovery so i can attempt to unbrick this beast I was trying to root for a friend. all I get to is first white at&t screen and it freezes almost like stuck in fastboot mode
can someone help and rip/upload or do I have ne other options?
I Just bought the new Fujitsu Arrows F-04E running android 4.0.4.
For now, there is nothing I could find on how to root it. I already tried the method of Bin4ry (Root MANY ANDROID) but didn't work. I'm now actively searching on Japanese sites, but nothing so far. If by chance someone in this community has some useful information that can help, please don't hesitate to share them. I will also share what I find, if any.
Thanks and hope we can figure the way to do it !
Cheers
The same with this enquire. If anybody enable to root and upgrade new Rom for F-04E, can u pls share for us? Thanks
luyenlt said:
The same with this enquire. If anybody enable to root and upgrade new Rom for F-04E, can u pls share for us? Thanks
Click to expand...
Click to collapse
More : If any one known the way to unlock !
phankhang said:
More : If any one known the way to unlock !
Click to expand...
Click to collapse
Please help if there are any solution . Thank all
root
1. Setup USB drivers on PC
2. Plug in Fujitsu Arrows V F-04E to PC (USB-debugging on)
3. Run root\runme.bat
am getting error
mount: Operation not permitted
Code:
-- F-02E ╥╗╝ⁿroot╣ñ╛▀ --
▒╛╚φ╝■└┤╫╘2ch┬█╠│íú└╢╔½dnxwj╝≥╥╫║║╗»íú
!! ╛»╕µ !!
1íóroot╓«║≤╜½╩º╚Ñ▒ú╨▐ú¼dnxwj║═╫≈╒▀╢╘┐╔─▄▓·╔·╬╩╠Γ▓╗╕║╚╬║╬╘≡╚╬íú
2íó┐¬╩╝root╘≥╩╙╬¬─π═¼╥Γ╫╘╨╨│╨╡ú╖τ╧╒íú
╟δ╫╘╨╨╫÷║├root╟░╫╝▒╕íú
PSú║╚⌠─·▓╗╧δrootú¼╟δ╓▒╜╙╣╪╡⌠╒Γ╕÷┤░┐┌íú
Press any key to continue . . .
╒²╘┌╕┤╓╞SuperUser...
╒²╘┌╚í╡├┴┘╩▒root...
989 KB/s (1283460 bytes in 1.267s)
1136 KB/s (146652 bytes in 0.126s)
867 KB/s (366952 bytes in 0.413s)
911 KB/s (1578585 bytes in 1.692s)
[+] This may take a few minutes.
[-] Failure.
╒²╘┌╜Γ│²LSM...
Mapping kernel memory...
Detected kernel physical address at 0x80008000 form iomem
Attempt fb_mem_exploit...
OK.
Finding kallsyms address in memory...
Segmentation fault (core dumped)
╒²╘┌╣╥╘┌/system╕─╬¬rw...
mount: Operation not permitted
╒²╘┌╠ß╔²SuperUser╚¿╧▐...
/system/xbin/su: cannot open for write: Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
╒²╘┌╓╪╨┬╣╥╘┌/system╬¬rw...
mount: Operation not permitted
╒²╘┌░▓╫░Superuser...
1140 KB/s (1578585 bytes in 1.352s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
╣º╧▓─·ú¼─·╡─F-02E╥╤╛¡│╔╣ªroot┴╦íú
Press any key to continue . . .
---------- Post added at 07:13 AM ---------- Previous post was at 07:08 AM ----------
i do have super user icon in my phone when i press install or recovery install it gives me "there was error installing superuser.please send a log of the error to the developer." but there is no log
also i checked with various apps to see if it was rooted but no it is not
did you got this resolved? USB debugging enabled on your device? did you install the driver correctly first?
m_ghv_geo said:
am getting error
mount: Operation not permitted
Code:
-- F-02E ╥╗╝ⁿroot╣ñ╛▀ --
▒╛╚φ╝■└┤╫╘2ch┬█╠│íú└╢╔½dnxwj╝≥╥╫║║╗»íú
!! ╛»╕µ !!
1íóroot╓«║≤╜½╩º╚Ñ▒ú╨▐ú¼dnxwj║═╫≈╒▀╢╘┐╔─▄▓·╔·╬╩╠Γ▓╗╕║╚╬║╬╘≡╚╬íú
2íó┐¬╩╝root╘≥╩╙╬¬─π═¼╥Γ╫╘╨╨│╨╡ú╖τ╧╒íú
╟δ╫╘╨╨╫÷║├root╟░╫╝▒╕íú
PSú║╚⌠─·▓╗╧δrootú¼╟δ╓▒╜╙╣╪╡⌠╒Γ╕÷┤░┐┌íú
Press any key to continue . . .
╒²╘┌╕┤╓╞SuperUser...
╒²╘┌╚í╡├┴┘╩▒root...
989 KB/s (1283460 bytes in 1.267s)
1136 KB/s (146652 bytes in 0.126s)
867 KB/s (366952 bytes in 0.413s)
911 KB/s (1578585 bytes in 1.692s)
[+] This may take a few minutes.
[-] Failure.
╒²╘┌╜Γ│²LSM...
Mapping kernel memory...
Detected kernel physical address at 0x80008000 form iomem
Attempt fb_mem_exploit...
OK.
Finding kallsyms address in memory...
Segmentation fault (core dumped)
╒²╘┌╣╥╘┌/system╕─╬¬rw...
mount: Operation not permitted
╒²╘┌╠ß╔²SuperUser╚¿╧▐...
/system/xbin/su: cannot open for write: Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
╒²╘┌╓╪╨┬╣╥╘┌/system╬¬rw...
mount: Operation not permitted
╒²╘┌░▓╫░Superuser...
1140 KB/s (1578585 bytes in 1.352s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
╣º╧▓─·ú¼─·╡─F-02E╥╤╛¡│╔╣ªroot┴╦íú
Press any key to continue . . .
---------- Post added at 07:13 AM ---------- Previous post was at 07:08 AM ----------
i do have super user icon in my phone when i press install or recovery install it gives me "there was error installing superuser.please send a log of the error to the developer." but there is no log
also i checked with various apps to see if it was rooted but no it is not
Click to expand...
Click to collapse
Your phone is F-02E. The root tool for F-04E
---------- Post added at 11:11 AM ---------- Previous post was at 11:06 AM ----------
m_ghv_geo said:
am getting error
mount: Operation not permitted
Code:
-- F-02E ╥╗╝ⁿroot╣ñ╛▀ --
▒╛╚φ╝■└┤╫╘2ch┬█╠│íú└╢╔½dnxwj╝≥╥╫║║╗»íú
!! ╛»╕µ !!
1íóroot╓«║≤╜½╩º╚Ñ▒ú╨▐ú¼dnxwj║═╫≈╒▀╢╘┐╔─▄▓·╔·╬╩╠Γ▓╗╕║╚╬║╬╘≡╚╬íú
2íó┐¬╩╝root╘≥╩╙╬¬─π═¼╥Γ╫╘╨╨│╨╡ú╖τ╧╒íú
╟δ╫╘╨╨╫÷║├root╟░╫╝▒╕íú
PSú║╚⌠─·▓╗╧δrootú¼╟δ╓▒╜╙╣╪╡⌠╒Γ╕÷┤░┐┌íú
Press any key to continue . . .
╒²╘┌╕┤╓╞SuperUser...
╒²╘┌╚í╡├┴┘╩▒root...
989 KB/s (1283460 bytes in 1.267s)
1136 KB/s (146652 bytes in 0.126s)
867 KB/s (366952 bytes in 0.413s)
911 KB/s (1578585 bytes in 1.692s)
[+] This may take a few minutes.
[-] Failure.
╒²╘┌╜Γ│²LSM...
Mapping kernel memory...
Detected kernel physical address at 0x80008000 form iomem
Attempt fb_mem_exploit...
OK.
Finding kallsyms address in memory...
Segmentation fault (core dumped)
╒²╘┌╣╥╘┌/system╕─╬¬rw...
mount: Operation not permitted
╒²╘┌╠ß╔²SuperUser╚¿╧▐...
/system/xbin/su: cannot open for write: Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
╒²╘┌╓╪╨┬╣╥╘┌/system╬¬rw...
mount: Operation not permitted
╒²╘┌░▓╫░Superuser...
1140 KB/s (1578585 bytes in 1.352s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
╣º╧▓─·ú¼─·╡─F-02E╥╤╛¡│╔╣ªroot┴╦íú
Press any key to continue . . .
---------- Post added at 07:13 AM ---------- Previous post was at 07:08 AM ----------
i do have super user icon in my phone when i press install or recovery install it gives me "there was error installing superuser.please send a log of the error to the developer." but there is no log
also i checked with various apps to see if it was rooted but no it is not
Click to expand...
Click to collapse
greatslon said:
1. Setup USB drivers on PC
2. Plug in Fujitsu Arrows V F-04E to PC (USB-debugging on)
3. Run root\runme.bat
Click to expand...
Click to collapse
You tried already, and is it successful rooted for F-04E?
Robiche said:
I Just bought the new Fujitsu Arrows F-04E running android 4.0.4.
For now, there is nothing I could find on how to root it. I already tried the method of Bin4ry (Root MANY ANDROID) but didn't work. I'm now actively searching on Japanese sites, but nothing so far. If by chance someone in this community has some useful information that can help, please don't hesitate to share them. I will also share what I find, if any.
Thanks and hope we can figure the way to do it !
Cheers
Click to expand...
Click to collapse
Hi bro,
Fujitsu F-04E rooted full
Pls checking some pictures below in attachment
If any support, feel free to contact me via YM: lethanhluyen
Hi,
I'm a noob at this stuff. I'm trying to root my f-04E. I've downloaded the two zip files, but I don't know how to install the usb drivers. I've tried installing them onto my SDK manager and still nothing happens. I've tried the runme option in the root file, but it says that my device is not detected. Any help would be awesome.
Phangtonpower said:
Hi,
I'm a noob at this stuff. I'm trying to root my f-04E. I've downloaded the two zip files, but I don't know how to install the usb drivers. I've tried installing them onto my SDK manager and still nothing happens. I've tried the runme option in the root file, but it says that my device is not detected. Any help would be awesome.
Click to expand...
Click to collapse
pls contact me for details
luyenlt said:
pls contact me for details
Click to expand...
Click to collapse
Actually I did send you a PM on here. Please check your in box
Is there anyone else with any ideas?
That we can have it posted here and have it documented for others to reference in the future.
Weekend bump.
About to call this one a lost cause bump
Thank you, was able to root no problem on the first try.
Although I did use generic google drivers. Sorry would link where I got them but cannot remember.
*update
Also wanted to mention that I have a EM01f, emobiles equivalent of this device.
*Update
though i was able to install superuser and passed rootchecker test i found I couldnt do a lot of things. So I downloaded the newest version of superuser renamed it to superuser.apk replaced the one in the zip and reran it. Works perfect, so far. Thanks again!
Hello to everyone I had an issue that was my phone restarts during calls and randomly, I just follow the root guide to eliminate all docomo bloatware
I root the phone successful but three days after a lot of app showed errors and restarts
When I restart phone the phone show three errors that are:
Com. Android. Phone process was closed and the Hceviewermaganer process has stopped and that situation is always on start
My phone doesn't work because this apps doesn't permit access to phone menu
Version of my phone is V16R
Question how I can try to reinstall original software, anyone has the recovery files to be uploaded through the recovery
Or any method to access through a Pc
Regards
Sent from my GT-I9300 using xda app-developers app
moku160 said:
Thank you, was able to root no problem on the first try.
Although I did use generic google drivers. Sorry would link where I got them but cannot remember.
*update
Also wanted to mention that I have a EM01f, emobiles equivalent of this device.
Click to expand...
Click to collapse
Hello !
I also have a EM-01F but I've the same problem as mentioned before. SuperUser icon is correctly installed on the device but when it's launched, an error pops to say me it can't install su access...
Which drivers have you used are what root program have you launched ?
Guigui_18892 said:
Hello !
I also have a EM-01F but I've the same problem as mentioned before. SuperUser icon is correctly installed on the device but when it's launched, an error pops to say me it can't install su access...
Which drivers have you used are what root program have you launched ?
Click to expand...
Click to collapse
check out my follow up post. I had to redo it, replacing the given superuser.apk without a newer version. THen it seemed to work correctly.