HELP ME, I've lost root!
I ran the X10root v 1.0.8 although i already had root and now i lost root. (X10i 2.1 nordic)
If i try to root it again with the SuperOneClick thing i get the following:
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...
526 KB/s (5392 bytes in 0.010s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
ROOTED
Getting mount path...
/dev/block/mtdblock2
OK
Remounting system with read-write access...
OK
Pushing su...
failed to copy 'su' to '/system/bin/su': Permission denied
OK
Pushing superuser.apk...
2628 KB/s (196521 bytes in 0.073s)
OK
chmod su...
OK
Remounting system with read-only access...
OK
Device was not rooted!
FAILED
Click to expand...
Click to collapse
Please, help me.
EDIT:
Maybe this is also relevant: (adb shell)
# su
su
reloc_library[1245]: 3654 cannot locate '_ZNK7android6Parcel15setDataPositionEj'...CANNOT LINK EXECUTABLE
#
Click to expand...
Click to collapse
2.1 or 1.6?
X10i 2.1 nordic
theeedy said:
X10i 2.1 nordic
Click to expand...
Click to collapse
Factory reset....
:/
Sent from my X10i using XDA App
Try again - http://forum.xda-developers.com/showthread.php?t=824788
I tried it already around 10 times.
EDIT: I had to reflash the firmware -.-
Related
New Method:
Download Flashtool from here:
http://forum.xda-developers.com/showthread.php?t=920746
And follow the instructions!
Regards
Bin4ry
bin4ry you su binary is incorrect and the exe are don't func sometime
i've atached a zip with a running su binary and without the exe
you need to to the manual way but it's verry easy.
you can use bin4ry first part of her manual but in the second he has make some Mistakes. please type in the secon part:
adb shell
-> # cd /data/local/tmp
-> # mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
-> # cat su > /system/bin/su
-> # cat superuser.apk > /system/app/superuser.apk
-> # chmod 06777 /system/bin/su
-> # chmod 777 /system/app/superuser.apk
-> # reboot
after rebooting you have root
wolfilein said:
maybe you should post the manual way without windows
for example mac or linux too
Click to expand...
Click to collapse
Done
Regards
Bin4ry
perfect
only Max should be Mac
Thank you, bin4ry! I will try it as soon as I get my x8, which should be tomorrow.
DerEineDa said:
Thank you, bin4ry! I will try it as soon as I get my x8, which should be tomorrow.
Click to expand...
Click to collapse
Here is a confirmation that it works
http://ip208-100-42-21.static.xda-developers.com/showpost.php?p=8672403&postcount=29
Regards
Bin4ry
Bin4ry said:
Here is a confirmation that it works
Click to expand...
Click to collapse
It does not work for me, unfortunately, this is what I get:
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...
351 KB/s (5392 bytes in 0.015s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
ROOTED
Getting mount path...
/dev/block/mtdblock0
OK
Remounting system with read-write access...
OK
Pushing su...
949 KB/s (26264 bytes in 0.027s)
OK
Pushing superuser.apk...
1279 KB/s (196521 bytes in 0.150s)
OK
chmod su...
OK
Remounting system with read-only access...
OK
Device was not rooted!
FAILED
uhh
try the manually way
but it seems that even if that all wil work
the su binary is incorrect so you become an error after typi ng su
Exactly...
I'm not sure which su binary to use?
Current says this:
$ su
link_image[1665]: 2263 could not load needed library 'libbinder.so' for 'su' (load_library[1011]: Library 'libbinder.so' not found)CANNOT LINK EXECUTABLE
use the one in this zip file:
http://www.mediafire.com/file/73e29s1dwp3fdhu/exploid_x10mini.zip
wolfilein said:
use the one in this zip file:
Click to expand...
Click to collapse
Yes!!!
Now it's rooted
Thanks a million m8!
@all please read post 2
Or use this:
SuperOneClick V1.5 with new SU and SuperUser.apk
Corrected first post. Sorry for errors
It's work, thank you very much guys.
Yes, it works perfectly. Thank you!
how to unroot it in case I want to send for warranty?
to unroot just remove the su and the superuser.apk with rootexplorer or with adb.
Regards
Bin4ry
Is it normal that the root is only temporarely? When I restart the device, I have to run "SuperOneClick.exe" again before I can do "su" on adb shell.
thanks
i just rooted my x8...
thank you guys....
now that its rooted, i tried for wifi tethering...
it is showing "no netfilter"
Is there anyway to overcome this problem......
SuperOneClick v2.1.0.0
Checking drivers...
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
2.2.1
Getting manufacturer...
HTC
OK
Getting model...
T-Mobile myTouch 3G
OK
Getting version...
300801
OK
Checking if rooted...
False
OK
Installing BusyBox (temporary)... - Step #1
868 KB/s (1062992 bytes in 1.195s)
OK
Installing BusyBox (temporary)... - Step #2
OK
Rooting device... - Step #1
660 KB/s (585731 bytes in 0.866s)
OK
Rooting device... - Step #2
OK
Rooting device... - Step #3
OK
Rooting device... - Step #4
property service neutered.
killing adbd. (should restart in a second or two)
OK
Rooting device... - Step #5
OK
Rooting device... - Step #6
False
OK
Getting mount path...
/dev/block/mtdblock3
OK
Remounting /system with read-write access...
OK
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Pushing su-v2...
failed to copy 'C:\Users\Jose\AppData\Local\Temp\Rar$EX84.184\Root\su-v2' to '/system/xbin/su': No space left on device
OK
Installing su... - Step #1
failed to copy 'C:\Users\Jose\AppData\Local\Temp\Rar$EX84.184\Root\su-v2' to '/system/xbin/su': No space left on device
OK
Installing su... - Step #2
Unable to chmod /system/xbin/su: No such file or directory
OK
Installing su... - Step #3
Unable to chmod /system/xbin/su: No such file or directory
OK
Installing SuperUser... - Step #1
failed to copy 'C:\Users\Jose\AppData\Local\Temp\Rar$EX84.184\Root\Superuser.apk' to '/system/app/Superuser.apk': No space left on device
OK
Checking for busybox
[1] Segmentation fault busybox true
OK
Remounting /system with read-only access...
OK
OK
Running a SU test...
Test failed!
FAILED
why i cant root my android? :/
josecleocir said:
SuperOneClick v2.1.0.0
Checking drivers...
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
2.2.1
Getting manufacturer...
HTC
OK
Getting model...
T-Mobile myTouch 3G
OK
Getting version...
300801
OK
Checking if rooted...
False
OK
Installing BusyBox (temporary)... - Step #1
868 KB/s (1062992 bytes in 1.195s)
OK
Installing BusyBox (temporary)... - Step #2
OK
Rooting device... - Step #1
660 KB/s (585731 bytes in 0.866s)
OK
Rooting device... - Step #2
OK
Rooting device... - Step #3
OK
Rooting device... - Step #4
property service neutered.
killing adbd. (should restart in a second or two)
OK
Rooting device... - Step #5
OK
Rooting device... - Step #6
False
OK
Getting mount path...
/dev/block/mtdblock3
OK
Remounting /system with read-write access...
OK
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Pushing su-v2...
failed to copy 'C:\Users\Jose\AppData\Local\Temp\Rar$EX84.184\Root\su-v2' to '/system/xbin/su': No space left on device
OK
Installing su... - Step #1
failed to copy 'C:\Users\Jose\AppData\Local\Temp\Rar$EX84.184\Root\su-v2' to '/system/xbin/su': No space left on device
OK
Installing su... - Step #2
Unable to chmod /system/xbin/su: No such file or directory
OK
Installing su... - Step #3
Unable to chmod /system/xbin/su: No such file or directory
OK
Installing SuperUser... - Step #1
failed to copy 'C:\Users\Jose\AppData\Local\Temp\Rar$EX84.184\Root\Superuser.apk' to '/system/app/Superuser.apk': No space left on device
OK
Checking for busybox
[1] Segmentation fault busybox true
OK
Remounting /system with read-only access...
OK
OK
Running a SU test...
Test failed!
FAILED
why i cant root my android? :/
Click to expand...
Click to collapse
As it says you have not enough space on your device
Sent from my X8 using xda premium
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Hey everyone!
Ive decided to go with SOC because Im not confident to do anything else deeper yet.
Ive been having some trouble with it working. Ive gone to the following places:
http://forum.xda-developers.com/showthread.php?t=993321&highlight=SuperOneClick
http://forum.xda-developers.com/showthread.php?t=982029&highlight=SuperOneClick
http://forum.xda-developers.com/showthread.php?t=972235&highlight=SuperOneClick
When I just plugged it in and tried it this is the result:
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
OK 0.11s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4.14s
Waiting for device...
OK 0.09s
2.2.1
Getting manufacturer...
Dell Inc.
OK 0.05s
Getting model...
Dell Streak
OK 0.03s
Getting version...
14896
OK 0.03s
Checking if rooted...
False
OK 0.09s
Installing BusyBox (temporary)... - Step #1
1619 KB/s (1062992 bytes in 0.641s)
OK 0.75s
Installing BusyBox (temporary)... - Step #2
OK 0.04s
Rooting device... - Step #1
1629 KB/s (585731 bytes in 0.351s)
OK 0.46s
Rooting device... - Step #2
OK 0.04s
Rooting device... - Step #3
OK 0.02s
Rooting device... - Step #4
property service neutered.
killing adbd. (should restart in a second or two)
OK 0.05s
Rooting device... - Step #5
error: protocol fault (no status)
FAILED
When I tried turning off the phone, plugging it in, starting SOC and then turning the phone on when It says waiting for device:
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
OK 0.14s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4.16s
Waiting for device...
OK 26.09s
2.2.1
Getting manufacturer...
Dell Inc.
OK 0.03s
Getting model...
Dell Streak
OK 0.03s
Getting version...
14896
OK 0.03s
Checking if rooted...
False
OK 0.07s
Installing BusyBox (temporary)... - Step #1
3223 KB/s (1062992 bytes in 0.322s)
OK 0.43s
Installing BusyBox (temporary)... - Step #2
OK 0.03s
Rooting device... - Step #1
3091 KB/s (585731 bytes in 0.185s)
OK 0.29s
Rooting device... - Step #2
OK 0.02s
Rooting device... - Step #3
OK 0.02s
Rooting device... - Step #4
property service neutered.
killing adbd. (should restart in a second or two)
OK 0.03s
Rooting device... - Step #5
OK 8.09s
Remounting /system with read-write access...
error: closed
FAILED
Im going to try an earlier version of SOC. I will check back here a little later with results. Thanks in advance!
I HAVE ANSWERED MY OWN QUESTION / PROBLEM!!!!!!!!!!!!!!!!!!!!!!
I ran SOC 1.7 and it was fine. I just had to.......
Turn phone off.
Start SOC 1.7.
clicked rageagainstthecage
clicked root
saw this:
SuperOneClick v1.7.0.0
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...
1053 KB/s (5392 bytes in 0.005s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
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
Pushing busybox...
2227 KB/s (1062992 bytes in 0.466s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mtdblock6
OK
Reading OS Version properties...
Version: 2.2.1
OK
Remounting system with read-write access...
OK
Pushing su-v2...
777 KB/s (26264 bytes in 0.033s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Pushing Superuser.apk...
1230 KB/s (196521 bytes in 0.156s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!
and BAM Im rooted!
Thank God for this forum !!!
Everytime I run the .bat for the my prompt reads Your device is a Nook Tablet meaning we can continue!
[/quote]Now, just making sure you WANT to root it!
[-] Cannot copy boomsh.: Permission denied
Installing superuser and su...
2313 KB/s (843503 bytes in 0.356s)
1819 KB/s (22364 bytes in 0.012s)
failed to copy 'root-files\su' to '/system/bin/su': Read-only file system
Installing and setting up busybox...
failed to copy 'root-files\busybox' to '/system/xbin//busybox': Read-only file s
ystem
1963 KB/s (12066 bytes in 0.006s)
[quote/]
I tried to root when in version 1.4.0 then downgraded back to 1.4.0 when the OTA hit and tried once more only to get the same error. Tried to cmod the entire system folder from both an adb shell and android terminal. any ideas guy?
Do you have USB Debugging enabled (in both boxes)?
Yea, its shows my device in the beginning of the script. =\
I think you need to run the runmefirst. bat then apply the other .bat to root
Sent from my LG GT540 Swift using XDA App
Did the runmefirst.bat.
logoguy said:
Did the runmefirst.bat.
Click to expand...
Click to collapse
ok then if that didn't work then its 100% drivers issue check this its the best step by step tutorial i have found , check step 3 or better the whole tut
Please has anyone gotten root on the mytouch by huawei/
Use a standard mode. If you have the adb drivers use any rooter.
Sent from my RK29 tab...
Bump
Sent from my T-Mobile myTouch using xda app-developers app
superbart007 said:
Bump
Sent from my T-Mobile myTouch using xda app-developers app
Click to expand...
Click to collapse
Sorry for my short answer but I recommend you to try (if you have adb drivers working) z4root or superoneclick.
The root process in Android is not as difficult as it seems. Just use a exploit to adb push files and change to rw system.
Sent from my RK29 tab...
I just attempted both of those root methods and also ZergRush nothing seems to work
darklink528 said:
I just attempted both of those root methods and also ZergRush nothing seems to work
Click to expand...
Click to collapse
Make sure to have the correct Adb drivers, sometimes the google drivers doesn't work with the oems driver...
If it doesn't work try with doomslord method. I'm getting without ideas
Sent from my RK29 tab...
Tried that one too nothing :/
What said the log, you get sucked at waiting for device ? Or were ?
Sent from my RK29 tab...
SferaDev said:
What said the log, you get sucked at waiting for device ? Or were ?
Sent from my RK29 tab...
Click to expand...
Click to collapse
I took a screenshot of where it gets stuck this one is Zergrush but superoneciclick gets stuck at waiting for device on step 7.
http://puu.sh/XigH
^^
Screenshot
darklink528 said:
I took a screenshot of where it gets stuck this one is Zergrush but superoneciclick gets stuck at waiting for device on step 7.
http://puu.sh/XigH
^^
Screenshot
Click to expand...
Click to collapse
Have you enabled USB debugging ?
Sent from my RK29 tab...
Yeah of course
darklink528 said:
Yeah of course
Click to expand...
Click to collapse
Then May be the vendor Id in the drivers !
Sent from my RK29 tab...
I'm having the same problem. I've rooted many Android devices. Yes USB debugging is enabled. Yes I can get adb access to the phone with a user level shell prompt. Yes it shows up in device manager as an Android Composite ADB interface. Yes I've added the PID and VID to android_winusb.inf.
Superoneclick gets stuck at step 7.
This phone seems like a decent phone for my wife (as a replacement for her stolen Samsung Galaxy S 4G), but it's LOADED with bloatware. I really need to figure out how to root this thing.
jb0ne said:
I'm having the same problem. I've rooted many Android devices. Yes USB debugging is enabled. Yes I can get adb access to the phone with a user level shell prompt. Yes it shows up in device manager as an Android Composite ADB interface. Yes I've added the PID and VID to android_winusb.inf.
Superoneclick gets stuck at step 7.
This phone seems like a decent phone for my wife (as a replacement for her stolen Samsung Galaxy S 4G), but it's LOADED with bloatware. I really need to figure out how to root this thing.
Click to expand...
Click to collapse
Try the doomslord method then. This method works pretty fine in lots of unnoficial or non tested devices.
SferaDev said:
Try the doomslord method then. This method works pretty fine in lots of unnoficial or non tested devices.
Click to expand...
Click to collapse
Thanks for the suggestion. Downloaded latest version of it (version 4). No luck.
Here's the output:
[*] Sending 149 zerglings ...
bugreport dir[/data/local/tmp] exist.
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
4038 KB/s (1075144 bytes in 0.260s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
32 KB/s (439 bytes in 0.013s)
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 98% bytes
test: 98%: bad number
--- NOT enough free space on /system!!!
--- making free space by removing Google Maps
rm: can't remove '/system/app/Maps.apk': Read-only file system
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
After that mount error I adb shelled in tried su for the heck of it and got permission denied. Also confirmed normal user can run mount. Checked df and /system is 370M, but only has 7M free. I wonder if that's the problem? How much space is needed for the zergrush method? Obviously I can't remove anything from /system if that is the problem. Also the df output is standard unix output so doesn't look like his bat file does very good error checking or does something odd.
For some problem the exploit doesn't works... Sniff...
make a request in ready2root.com
Sent from my RK29 tab...