1st i am new to rooting (n00b)
yesterday i successfuly rooted my x10 mini pro using superoneclick,xrecovery and installed android 2.3.3,i wasnt totally happy (i was trying to get it working as a wifi hotspot using quicksettings and wifi tether to no aveil and every few hours it would blackscreen or reboot) it also has root explorer, titanium backup,buzybox installed.
today i used xrecovery to go back to 2.1 (luckily i backed up whew!) and was going to give 2.3.5 a try (MiniCM7Pro-v6) it was all fine i was using root explorer to move and delete some music files, and the mount r/w r/o was working. at some point i tried running buzybox and it said 'error-root access not detected' i went into superuser clicked forget and restarted app,no change, superuser will not grant root for any prog,i started root explorer and now i cant change the mount to r/w.i read try rerooting,so i did (with same prog) it said phone was already rooted, i tried rerooting,it all went ok until it done a su test 'test failed'..now im at a total loss as what todo, read alot of threads an tried diff methods including running adb mask controller as guided by thread,it's obviously something ive done but what? cannot get back into xrecovery either, any help much appreciated..sorry for the essay but ive been at it all day! il paste a copy of what superoneclick says when i tried rerooting below. thank you for even reading this
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
OK 0.16s
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.1.1
Getting manufacturer...
Sony Ericsson
OK 0.03s
Getting model...
U20i
OK 0.02s
Getting version...
-X_d
OK 0.02s
Checking if rooted...
True
OK 0.04s
Installing BusyBox (temporary)... - Step #1
545 KB/s (1062992 bytes in 1.902s)
OK 1.98s
Installing BusyBox (temporary)... - Step #2
OK 0.02s
Rooting device... - Step #1
538 KB/s (585731 bytes in 1.061s)
OK 1.13s
Rooting device... - Step #2
OK 0.02s
Rooting device... - Step #3
OK 0.01s
Rooting device... - Step #4
property service neutered.
killing adbd. (should restart in a second or two)
OK 0.03s
Rooting device... - Step #5
OK 3.20s
Remounting /system with read-write access...
OK
OK 0.10s
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK 0.01s
Installing su (/system/xbin)... - Step #1
284 KB/s (26264 bytes in 0.090s)
OK 0.22s
Installing su (/system/xbin)... - Step #2
No such user '0:0'
OK 0.02s
Installing su (/system/xbin)... - Step #3
OK 0.03s
Installing SuperUser... - Step #1
479 KB/s (196521 bytes in 0.400s)
OK 0.63s
Checking for busybox
OK 0.02s
Remounting /system with read-only access...
OK
OK 0.10s
Running a SU test...
Test failed!
FAILED
super devz heeelp, i cant stand staying at 2.1 after a taste of 2.3.3 rooted thats just evil! =(
ive been looking at the details from the superoneclick and the last description states 'remounting/system with read-only access OK' then the su test fails....
(excuse my questions but im really new to this.-and ive been up all night 6:15am now!)
anyway so my question now is is there a way to remount with wrie access and how do i go about it? il keep searching tomorrow but would appreciate any input.
thnks Lee :/
smallz2k said:
ive been looking at the details from the superoneclick and the last description states 'remounting/system with read-only access OK' then the su test fails....
(excuse my questions but im really new to this.-and ive been up all night 6:15am now!)
anyway so my question now is is there a way to remount with wrie access and how do i go about it? il keep searching tomorrow but would appreciate any input.
thnks Lee :/
Click to expand...
Click to collapse
just a thought... try reset your phone using SEUS/pc companion..
then try rerooting..
paradorx said:
just a thought... try reset your phone using SEUS/pc companion..
then try rerooting..
Click to expand...
Click to collapse
wow! thank you, i didnt think the phone cld be unrooted by se update..but i used pc companion and did a hard reset, it put the same 2.1 back on and left the phone unrooted so was able to use superoneclick again to re-root, so simple in the end, i was over thinking the whole thing, i guess thats why this site is so awesome, just getting a new fresh brain to look at it! ok now onto flashing and finding a good stable rom to load up,any advice? again thankyou!
There are quite many rom to choose from..
For froyo I personally like minicm6 by slade n cyanocomb by d4
For ginger I like minicm7 by paul, but im looking forward to use gingerdx
Send from my MiniCM7 Pro v6 using Tapatalk
After 2 days no kip aa bit of help a lot of reading! An if I'm honest bucket loads of luck I'm running on froyobread... 2.2.9 and up 2 now its flyin, Big thnx and high fives to xda developers,I'll gt round to thnkin u all
Sent from my U20i using XDA App
SU command test suceeds, but still not rooted.
I have a similar problem. I get the message:
--snipp-----
"Installing su (/system/xbin)... - Step #2
No such user '0:0'
OK 0.02s"
----snap-----
similar to smallz2k, but the su test command finishes sucessfully. But when I check for root access on the phone, there is none. When I tried to unroot via super1click. It couldn't get Android Version nor any other data like device version number etc. Initial test routines.
Then I reset the phone via PC Companion and tried it again with same results.
Where do I go wrong? Any hints? Is my description detailed enough?
SaintBlue
You've dug up a thread That's almost a year old. Start another, someone will help.
My best idea is use flashtool to root. That's what I've done for every U20 I've had to root and it's always worked
X10man
Sent from my Fender Stratocaster to your face via XDA Premium
Thank you,
I'll try flashtool and hope it'll solve my issue.
Related
ok i am on EA28 looking to root tried some many methods and lost i rooted phone jail broke them unlocked them never had this much issues.
i tried z4root, this way..... i see no where it talks about sdk or anything help me please
Dirt_Mcgirt said:
ok i am on EA28 looking to root tried some many methods and lost i rooted phone jail broke them unlocked them never had this much issues.
i tried z4root, this way..... i see no where it talks about sdk or anything help me please
Click to expand...
Click to collapse
Forget about all of it.
Download Shortfuse.
http://forum.xda-developers.com/showthread.php?t=803682
Then open it.
Plug your phone to Computer (Make sure the USB debugging is on)
Then press Root.
When you are done, there should be pop-up saying would you like to test if the root was successful? Click yes, read the msgs if you are rooted.
It's simple as that.
If I helped you, press Thanks button at bottom right.
no go keeps hanging up.....
Getting mount path...
rootfs / rootfs rw 0 0
FAILED
SuperOneClick v1.8.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
Getting OS Version...
OK
Pushing psneuter...
558 KB/s (585731 bytes in 1.025s)
OK
chmod psneuter...
OK
Running psneuter...
ROOTED
Pushing busybox...
394 KB/s (1062992 bytes in 2.631s)
OK
chmod busybox...
OK
Getting mount path...
rootfs / rootfs rw 0 0
FAILED
Is your phone sleeping during the process? I had issues if my screen went off.
If you still can't root you could always just Odin an already rooted image or the CWR....Though if you can't get root to work it might not be the best thing to suggest to you to flash stuff........
eah i rather not flash till i am rooted if i can avoid it lol n my phone isnt sleeping either
why dont you just get an already rooted rom? look for them in the development section, dont worry about rooting it yourself.
jorge3687 said:
why dont you just get an already rooted rom? look for them in the development section, dont worry about rooting it yourself.
Click to expand...
Click to collapse
i can do that but i like to root it myself just for the know how yeah i can use odin right?
Hey guys. I've just bought my Galaxy S II and I'm wondering about the root issue. Now I'm having the XWKE2 firmware but it says on some post about rooting the phone that you need to download the XWKDD firmware. Now I am wondering first about the warranty,will it void, and secondly will it damage my phone if I am trying to change XWKE2 with XWKDD?
Please help guys. I'm kinda new with android and don't know much.
Jokerbest2006 said:
Hey guys. I've just bought my Galaxy S II and I'm wondering about the root issue. Now I'm having the XWKE2 firmware but it says on some post about rooting the phone that you need to download the XWKDD firmware. Now I am wondering first about the warranty,will it void, and secondly will it damage my phone if I am trying to change XWKE2 with XWKDD?
Please help guys. I'm kinda new with android and don't know much.
Click to expand...
Click to collapse
1 - Yes, rooting will void warranty. But fear not, you can unroot.
2 - No, you won't damage your phone.
Everything you need is here:
http://forum.xda-developers.com/showthread.php?t=1075278
And there's some good video tutorials by mattj101101 on youtube if you need further help.
Hi,
I've rooted a XWKE2 successfully.
I flashed to "insecure" XWKDD, rooted and then flashed back the original XWKE2.
The XWKDD is only an older version of the firmware which will not "damage" your phone per se (but maybe if something went wrong while the flashing process).
As far as I understand it, it's hard to really brick the phone. Most of the time you are able to flash back a working system.
I'm new to Android, too. I made sure to have every file prepared and read every page of the rooting guide thread in the development section.
Warranty depends on where you live and what you've done to your phone (like overclocking and what have you).
If something's wrong with my phone (god forbid), I simply flash back every thing to samsung stock files and hope service doesn't notice.
I used
Odin3-v1.85.zip
XWKDD_insecure.tar
SuperOneClickv1.9.1-ShortFuse.zip
KE2_original.zip
Have fun & good luck
Thank you
Thanks guys,that was really really helpful.
kkaster said:
Hi,
If something's wrong with my phone (god forbid), I simply flash back every thing to samsung stock files and hope service doesn't notice.
Or use Check Fus to download your original rom .
http://forum.xda-developers.com/showthread.php?t=1032437&page=5
jje
Click to expand...
Click to collapse
I m trying to root my new galaxy s 2 i9100 with this way.http://forum.xda-developers.com/show....php?t=1075278
i follow all the steps but i have a serious problem.
in step 8. "Click root and wait for it to finish. Install Busybox and all that good stuff." the SuperOneClick bugs.
this is all tha i get in my screen:
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 psneuter...
2820 KB/s (585731 bytes in 0.202s)
OK
chmod psneuter...
OK
Running psneuter...
please help!!
djtas said:
I m trying to root my new galaxy s 2 i9100 with this way.http://forum.xda-developers.com/show....php?t=1075278
i follow all the steps but i have a serious problem.
in step 8. "Click root and wait for it to finish. Install Busybox and all that good stuff." the SuperOneClick bugs.
this is all tha i get in my screen:
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 psneuter...
2820 KB/s (585731 bytes in 0.202s)
OK
chmod psneuter...
OK
Running psneuter...
please help!!
Click to expand...
Click to collapse
Yet again follow the instruction and do it all again .
jje
Hey everyone, so I tried rooting the device with 4zroot and SuperOneClick both methods don't work. With 4zroot, when push root, the program backs out and force closes. With SuperOneClick, the program got stuck at "Waiting for device..." for over 15 minutes. I also gone and double-check every setting is in the correct order. I tried several times with both methods and failed. So do you have any ideas on getting root access on this device. Thank you.
Firmware version: 2.2.2
Kernel version: 2.6.32.9 [email protected]#1
Build number: FROYO.DXKF3
Edit1: Rooted successfully!! After trying about every suggestions i could find, i couldn't connect to kies, it said pc suite mode need to be activated, but there's no option for that in the 5.0 wifi, but after internal memory format and factory setting reset, i connect to pc (pc recognize, but kies didn't) i use the SuperOneClick and BAM! it is rooted!!
You use the program that I want to try some of the root. Now I have a problem with kies it invisible to me to me.
Another rooted Galaxy YP-G70
Device Info:
Model number: YP-G70CW (on the back of the device)
Firmware ver: 2.2.2
Kernel ver: 2.6.32.9 [email protected] #12
Build number: FROYO.ZSKE2
Tools:
1. Install SAMSUNG USB Driver for Mobile Phones
2. SuperOneClick version 2.1.1
i confirm, today i've rooted my galaxy s wifi 5 with super one click in a minute!
i just got this device it's great the screen is huge, so i'm glad it can be rooted. the question is can i restore it to factory state? how do i backup the ROM?
ronnieg said:
i just got this device it's great the screen is huge, so i'm glad it can be rooted. the question is can i restore it to factory state? how do i backup the ROM?
Click to expand...
Click to collapse
in the superoneclick menu there is the voice "unroot", so it's very simple!
root yp-g70
sorry i have this phone i want to rooted but i don´t know ho to do it anyone can help me
josetup123 said:
sorry i have this phone i want to rooted but i don´t know ho to do it anyone can help me
Click to expand...
Click to collapse
You have to use superoneclick. It's so userfriendly, perfect for a newbye.
Don't worry, let's try !
Inviato dal mio YP-G70 usando Tapatalk
WT Ho said:
Device Info:
Model number: YP-G70CW (on the back of the device)
Firmware ver: 2.2.2
Kernel ver: 2.6.32.9 [email protected] #12
Build number: FROYO.ZSKE2
Tools:
1. Install SAMSUNG USB Driver for Mobile Phones
2. SuperOneClick version 2.1.1
Click to expand...
Click to collapse
get give download link for the SAMSUNG USB Driver for Mobile Phones installer? thanks
mustikasakti said:
get give download link for the SAMSUNG USB Driver for Mobile Phones installer? thanks
Click to expand...
Click to collapse
here it is your drivers! http://forum.xda-developers.com/showthread.php?t=961956
Hello everyone I can not rooter my samsung galaxy s wifi YP-5.0 g70 g70
someone can help me thank you
manu17300 said:
Hello everyone I can not rooter my samsung galaxy s wifi YP-5.0 g70 g70
someone can help me thank you
Click to expand...
Click to collapse
what's the problem?
Stuck at Step#1
I can't get my Samsung galaxy S 5 wifi rooted either. First I was getting stuck on detecting the device like the OP. Then I installed the latest drivers from the link tapioco2000 provided (Thanks tapioco2000!). Now I can see the device when I type "adb devices". And Super One Click now progresses to Step #1. But now it's stuck there trying to temporary install busybox. I tried the Shell Root method as well. But there I get stuck at step #1 as well.
Any help would be appreciated. Thanks.
got mine rooted! Now what's the best rom to install?!
Need to be careful about the ROMS, you can download the stock ROM currently and it is easy to root. Don't forget to enable USB debugging.
I bricked mine after some root tweaking, and was able to restore using ODIN and the original firmware.
os2baba said:
I can't get my Samsung galaxy S 5 wifi rooted either. First I was getting stuck on detecting the device like the OP. Then I installed the latest drivers from the link tapioco2000 provided (Thanks tapioco2000!). Now I can see the device when I type "adb devices". And Super One Click now progresses to Step #1. But now it's stuck there trying to temporary install busybox. I tried the Shell Root method as well. But there I get stuck at step #1 as well.
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
So no one else is stuck with rooting the device? Especially at Step #1 where it can't seem to install busybox?
Make sure you are in USB debug mode and have allow non-market installations checked. See if that helps any.
Ishman said:
Make sure you are in USB debug mode and have allow non-market installations checked. See if that helps any.
Click to expand...
Click to collapse
Yes both are set.
problem root my device - superuser will not install to device?
After rooting i can not find superuser from programs list?
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
OK 1,59s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4,06s
Waiting for device...
OK 0,03s
2.2.2
Getting manufacturer...
samsung
OK 0,04s
Getting model...
YP-G70
OK 0,04s
Getting version...
XXKG1
OK 0,04s
Checking if rooted...
True
OK 0,06s
Installing BusyBox (temporary)... - Step #1
708 KB/s (1062992 bytes in 1.465s)
OK 1,51s
Installing BusyBox (temporary)... - Step #2
OK 0,05s
Rooting device... - Step #1
295 KB/s (585731 bytes in 1.937s)
OK 1,97s
Rooting device... - Step #2
OK 0,04s
Rooting device... - Step #3
OK 0,01s
Rooting device... - Step #4
property service neutered.
killing adbd. (should restart in a second or two)
OK 0,06s
Rooting device... - Step #5
OK 8,08s
Remounting /system with read-write access...
OK
OK 0,10s
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK 0,05s
Installing su (/system/xbin)... - Step #1
328 KB/s (26264 bytes in 0.078s)
OK 0,54s
Installing su (/system/xbin)... - Step #2
OK 0,05s
Installing su (/system/xbin)... - Step #3
OK 0,04s
Installing SuperUser... - Step #1
176 KB/s (196521 bytes in 1.089s)
OK 1,32s
Checking for busybox
OK 0,04s
Remounting /system with read-only access...
OK
OK 0,34s
Running a SU test...
Test failed!
FAILED
Did anyone try installing a standard Galaxy S ROM on it? I mean, it seems to be the same hardware sans the phone/3G transmitter, no?
I have tried numerous times to root using the superclick method which gives me the standard ...
SuperOneClick v1.6.5.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 psneuter...
2288 KB/s (585731 bytes in 0.250s)
OK
chmod psneuter...
error: closed
FAILED
..........message.
When I try to copy the Xionia to my root sd directory and rename it to update it says that it failed the e signature when I try to use the in phone method.
Yes, I know you guys have many times rooted your phones but yours were done many days ago. I think it's safe to say that there are not going to be any options for those that had phones before Virgin Mobile closed the loophole to us newer users and nobody appears to want to help.
Have you tried Gingerbreak?
Ostrich Egg said:
Have you tried Gingerbreak?
Click to expand...
Click to collapse
it's available here on xda if you search.
I've read numerous places that superonclick doesn't work on the 2.2.2 ov's. you also cannot use fastboot to root your new 2.2.2 ov, since VM or LG has now locked out access to the bootloader, which fastboot needs to operate.
gingerbreak worked fine on my new 2.2.2 ov. superoneclick worked on my old 2.2.1 ov (which had an accident, unfortunately.)
oh, and this is probably more of a "p500/v general discussion" section question.
All I wanna do is get rid of the bloatware. I'm not interested in possible bugs. I just wanted to root it and get rid of the junk.
i unlocked bootloader with teh asus unlock tool. I then rooted using the debugfsroot method found in the stickies. everything went well Or so i thought. After all rebooting was done i went into app folder and the superuser app was in there so i thought that i was rooted. Went to install twrp through goo manager and it said it couldn't get root permissions adn that i wasn't rooted. So i downloaded titanium backup to backup my apps and when i opened it it too said i wasn't rooted or that busybox wasn't downloaded. I downloaded busy box from the market and tried to install it and same thing....any one know what's up?
try rooting again with the same method and post what the cmd says after you are done with it~
lil-devil said:
try rooting again with the same method and post what the cmd says after you are done with it~
Click to expand...
Click to collapse
ok doing that now
here's what is says...
Installing Superuser.apk...
891 KB/s <843503 bytes in 0.924s>
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Rebooting...
Once your Prime reboots, it will be rooted!
Press any key to continue...
vballrkc said:
here's what is says...
Installing Superuser.apk...
891 KB/s <843503 bytes in 0.924s>
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Rebooting...
Once your Prime reboots, it will be rooted!
Press any key to continue...
Click to expand...
Click to collapse
UPDATE: After the second root now everything i described above is requesting superuser permissions so it appears all is well. If i have problems i will repost. Thank you for your response though i guess it just didn't stick the first time.
i'm glad that it works now
Hello,
i have a litle problem with the method above everything went ok .. i have root acces i think :'(
but the problem is that almost all applications started to crash, force close ro stoped running at all.
everything that was working before the root is broken somehow
any way to fix this ,???
i would suggest you to try unrooting with the root keeper app
if that doesn't work try reseting your tab via the pin hole under the SD card
if that still doesn't solve the problem default the tf201~
Ahem, OP, you do realize your bootloader is unlocked? That your warranty is void? That you no longer can receive otas? It's failing to push superuser.apk because it's already there. seems to me that you may need just to update su binary in superuser app. To start over, you need to uninstall Superuser app (if you can). If chainsdd su binary has been installed correctly with the right permissions, then you should be able to get root through adb, and then remount /system as rw, and remove Superuser.apk from /system/app.
Whats done its done. Stop wasting time. Check out the sticky for nvflash in the dev thread (read the whole thread, seriously) and get some nvflash goodness, better safe than sorry.
After that, continue to learn the ways of fastboot (if you use a toolkit, it's considerably harder to troubleshoot when things go wrong, to see where it failed, that's why you opened this thread, you don't know what went wrong), flash latest cwm or twrp through fastboot, flash a custom rom (after factory reset in cwm/twrp, naturally) with cwm/twrp, which will have root. and a whole lot more good things. if you don't want to go custom rom just yet and stick with modified (pre-rooted!) stock roms (made for unlocked bootloaders). all of this can be found in the dev thread, as you probably know.
If you're unlocked, the whole thing gets easier.
If you really want to stick with an (tweaked) asus stock rom, even unlocked, for some unknown-to-human-race reason, you may just download a superuser/supersu cwm/twrp (flashable) zip, copy it to the internal sdcard, boot a custom recovery (which also has root) through fastboot, flash that zip you copied before, and reboot system. you'll be rooted. an exploit is only needed when device is not unlocked.
# rant
# Damn, being unlocked/with a real safety net software wise feels GOOD!
sent from my tf201
bk201doesntexist said:
Ahem, OP, you do realize your bootloader is unlocked? That your warranty is void? That you no longer can receive otas? It's failing to push superuser.apk because it's already there. seems to me that you may need just to update su binary in superuser app. To start over, you need to uninstall Superuser app (if you can). If chainsdd su binary has been installed correctly with the right permissions, then you should be able to get root through adb, and then remount /system as rw, and remove Superuser.apk from /system/app.
Whats done its done. Stop wasting time. Check out the sticky for nvflash in the dev thread (read the whole thread, seriously) and get some nvflash goodness, better safe than sorry.
After that, continue to learn the ways of fastboot (if you use a toolkit, it's considerably harder to troubleshoot when things go wrong, to see where it failed, that's why you opened this thread, you don't know what went wrong), flash latest cwm or twrp through fastboot, flash a custom rom (after factory reset in cwm/twrp, naturally) with cwm/twrp, which will have root. and a whole lot more good things. if you don't want to go custom rom just yet and stick with modified (pre-rooted!) stock roms (made for unlocked bootloaders). all of this can be found in the dev thread, as you probably know.
If you're unlocked, the whole thing gets easier.
If you really want to stick with an (tweaked) asus stock rom, even unlocked, for some unknown-to-human-race reason, you may just download a superuser/supersu cwm/twrp (flashable) zip, copy it to the internal sdcard, boot a custom recovery (which also has root) through fastboot, flash that zip you copied before, and reboot system. you'll be rooted. an exploit is only needed when device is not unlocked.
# rant
# Damn, being unlocked/with a real safety net software wise feels GOOD!
sent from my tf201
Click to expand...
Click to collapse
So many things to respond to here, how about i just choose that if you would actually read the progression of this thread instead of just reading the first post and then skipping the next 9 posts and proceeding to rant to make yourself feel better then others, you would realize the problem has been fixed and all is good and that really none of what you wrote was A. relevant to my problem and B. helpful at all. Thanks. have a nice day.
vballrkc said:
So many things to respond to here, how about i just choose that if you would actually read the progression of this thread instead of just reading the first post and then skipping the next 9 posts and proceeding to rant to make yourself feel better then others, you would realize the problem has been fixed and all is good and that really none of what you wrote was A. relevant to my problem and B. helpful at all. Thanks. have a nice day.
Click to expand...
Click to collapse
I actually had good intentions, but now I don't freaking care what you think: Don't use sarcasm on me boy. BTW, no sarcasm here: You'll never learn anything if you keep using toolkits.