So basically as the title says. I run beaups exploit. Gets to the point it wants to write super user and busybox but gets several "permission denied" tags telling me that it is a "read only file system". Is that in regards to the laptop I am using or my HOX? Is there a step I am missing? Thanks.
UPDATE: Now I am getting something different. Looks good until the phone starts rebooting. Says it cannot find Package Manager and will not complete the root process. Strange?
UPDATE #2: Disregard. It did finish rooting. Successful.
Related
I have searched google far and wide, found a few cases of similar issues but haven't found a solution yet. Got my T-mobile g2 /DZ about 2 months ago, love the hardware and the form factor, but I cannot stand stock froyo. First of all:
Phone build/firmware (?) number is: 1.22.531.8
Release keys: cl277427
I initially tried rooting the phone with visionary r14, which gave me a temp root, then rebooted when I tried perm-root. Ever since then, the program hangs when trying to even temp root (I have tried visionary r11,12,13, and 14, as well as uninstalling and reinstalling countless times [not to mention downloading from different sources]).
After a bit of searching, decided to try rage method - again it didnt work (terminal emulator > /data/local/tmp/rage - permission denied) no matter how many times I tried it.
Tried rage method with gfree (both .02 and .04), which is where I had the most success. I managed to get s-off, but still no superuser access. The problem occurs when I enter the code /data/local/tmp/root
described in this page: http://forum.xda-developers.com/wik...Subsidy_Unlock.2C_SuperCID.2C_and_Radio_S-OFF where it tells you how to 'lock in' the root.
After entering the '/data/local/tmp/root' code, I get an error message that reads something like:
mkdir failed for /system/xbin/, File exists
cp: can't stat `/system/xbin/busybox': Not a directory
Unable to chmod /system/xbin/busybox: Not a directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
I have checked, double-checked, and triple-checked that I have pushed busybox etc correctly, and they definitely write to the folder as I am not getting any error messages in CMD.
I would greatly appreciate anyone who can give me a straight answer as to what to look for (somebody said you can't have a file/folder on SD card called 'su' so I have checked that). This is driving me crazy - I bought the G2 thinking froyo would be so much better than Symbian/Motoblur, but I am really disappointed. Even Launcherpro etc are pretty lame compared to some of the custom roms out there.
Please help me!
Alternatively, seeing as I have s-off, any way to flash a rom without superuser? Sorry for the noob question
s-off and gfree ? i don't have g2 version, only desire z. but you can always flash clockwork recovery from adb fastboot. using that, you can switch to other ROM or backup the current one...
fajarep said:
s-off and gfree ? i don't have g2 version, only desire z. but you can always flash clockwork recovery from adb fastboot. using that, you can switch to other ROM or backup the current one...
Click to expand...
Click to collapse
Can you give me a bit more detail? About to try and flash a pre-rooted modaco rom. Will probably have to wipe the phone so if it doesnt work I will try gfree again on the wiped phone
Bumping bump
Anybody?...
Still needing help on this
Hey folks
Small problem here:
Every time I attempt to fix permissions using ROM manager I get an error message:
'an error occurred while trying to run privileged commands'
When I type 'su' into terminal, superuser wants to grant root access so I guess that I'm rooted properly.
It's not a huge deal but it is kinda annoying
Running stock ICS on gt19020 UK 3G version.
Thanks for your time in reading this,
All the best
casmael said:
Hey folks
Small problem here:
Every time I attempt to fix permissions using ROM manager I get an error message:
'an error occurred while trying to run privileged commands'
When I type 'su' into terminal, superuser wants to grant root access so I guess that I'm rooted properly.
It's not a huge deal but it is kinda annoying
Running stock ICS on gt19020 UK 3G version.
Thanks for your time in reading this,
All the best
Click to expand...
Click to collapse
Fix permissions in recovery!
Can someone walk me through the steps to root this One X? I tried rooting it last night with no luck, I couldn't get the 1.85 script to work--it installed Superuser and when I opened superuser it force closed and then said something like: "No binary installed, blah blah blah." If anyone is willing to help me just PM me and say which IM you'd like to use. Thanks a lot!
Kelton Rivas said:
Can someone walk me through the steps to root this One X? I tried rooting it last night with no luck, I couldn't get the 1.85 script to work--it installed Superuser and when I opened superuser it force closed and then said something like: "No binary installed, blah blah blah." If anyone is willing to help me just PM me and say which IM you'd like to use. Thanks a lot!
Click to expand...
Click to collapse
use this http://forum.xda-developers.com/showthread.php?t=1709296
seems to work every time to root 1.85
After going to the manual route and typing in the first command I get: C:\Users\Kelton\Downloads>adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
C:\Users\Kelton\Downloads>
It completely ignored my command. .what did I do wrong? I dragged the SU file into downloads, which is where my "adb files, busy box, and root" root option are. :c
Edit 1: http://imageshack.us/photo/my-images/232/htcpic.png/ ---made a new folder where I extracted the auto-root script materials and included a screen shot showing it ignores my attempts at the manual method. Help.
Edit 2: Throughout this process somehow the OTA update got downloaded, *but* I didn't push it, I postponed it and did a factory reset. My firmware is still 1.85, so I should be good. However, now when I run the auto script and go to the phone and select "AT&T check for update" it says "continue update" instead of "check." Does that mean I can't run the script now? Is there anyway I could delete the update file off my SD card?
Edit 3: I ran the script after another factory reset and got a different result: http://imageshack.us/photo/my-images/705/htcpic.png/ I now have supersu on my phone, but when I try and open it I get: "There is no su binary isntalled, and SuperSU cannot install it. This is a problem!" Did I mess up? Should I factory reset again and try to do the manual method (which I've had no luck with)?
Edit 4: I downloaded Root Checker thinking I would have root access since I have SU in the app drawer, but I don't. Root checker said "This device does not have proper root access."
Pp
Kelton Rivas said:
Can someone walk me through the steps to root this One X? I tried rooting it last night with no luck, I couldn't get the 1.85 script to work--it installed Superuser and when I opened superuser it force closed and then said something like: "No binary installed, blah blah blah." If anyone is willing to help me just PM me and say which IM you'd like to use. Thanks a lot!
Click to expand...
Click to collapse
Dude ... Follow these stepshttp://forum.xda-developers.com/showthread.php?p=27379847 I have rooted my device successfully last night
When I used root checker I too got same message " your device not rooted properly" push your phone date forward to two days and try it will work
Sent from my HTC One X using xda premium
abhipati said:
Dude ... Follow these stepshttp://forum.xda-developers.com/showthread.php?p=27379847 I have rooted my device successfully last night
When I used root checker I too got same message " your device not rooted properly" set ur phone
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I've been following steps from every-which-way, haha. Nothing seems to work. Set my phone? What does that mean?
Kelton Rivas said:
I've been following steps from every-which-way, haha. Nothing seems to work. Set my phone? What does that mean?
Click to expand...
Click to collapse
Updated my post
Sent from my HTC One X using xda premium
Now fixed, Solution grab the fixed batch from my second post, run it choose 1(normal), then run it again choose x(unroot), then run it for the final time and choose 1(normal), if all goes well titanium backup should allow you to use it(ofc you could check superSU and Superuser).
Original Post
Tried to root my Virgin Mobile Kyocera Rise C5155 on ICS 4.0.4 with Root Many Android, first try yielded a mount: permission denied (are you root) error, second try said it was successful but SuperSu didn't install, third try I chose charge only instead of mass storage and SuperUser instead of SuperSu but it didn't install. So I installed SuperSU from the play store and it said it needed to install the su binary but SuperSu couldn't do this, so I tried Superuser it could install the su binary but was given a permission denied by ICS.
So it appears this phone is no longer rootable with RMA. I had Usb debugging turned on and mass storage is my normal choice for connecting to pc, I have the proper adb drivers for the kyocera rise from their website, so from what I've gathered I've done everything to a T. went back an looked at the terminal saw it couldn't replace /system/bin/.ext (because it already existed) and I don't know why for the life of me that su is in /system/bin/.ext/.su but its there.
I used RMA v25. Any Advice or Suggestions would be appreciated.
Click to expand...
Click to collapse
Fixed See my Post Below for the Attached Fixed Bat File.
There was an oversight in the bat that neglected to clean up properly upon repeated root attempts, it didn't remove the /system/bin/.ext folder and the /system/bin/.ext/.su binary. I've fixed it to where it will remove those first (rm will exit cleanly(by this i mean it will exit returning control of the application to the bat, it will still generate an error ) even if the files aren't found which Means if they're not there it doesn't really matter)
Xecantur said:
Tried to root my Virgin Mobile Kyocera Rise C5155 on ICS 4.0.4 with Root Many Android, first try yielded a mount: permission denied (are you root) error, second try said it was successful but SuperSu didn't install, third try I chose charge only instead of mass storage and SuperUser instead of SuperSu but it didn't install. So I installed SuperSU from the play store and it said it needed to install the su binary but SuperSu couldn't do this, so I tried Superuser it could install the su binary but was given a permission denied by ICS.
So it appears this phone is no longer rootable with RMA. I had Usb debugging turned on and mass storage is my normal choice for connecting to pc, I have the proper adb drivers for the kyocera rise from their website, so from what I've gathered I've done everything to a T. went back an looked at the terminal saw it couldn't replace /system/bin/.ext (because it already existed) and I don't know why for the life of me that su is in /system/bin/.ext/.su but its there.
I used RMA v25. Any Advice or Suggestions would be appreciated.
Click to expand...
Click to collapse
I fixed it there was an oversight in the RMA bat file, I attached the fixed bat ONLY you'll have to visit the RMA thread and download the full environment.
Xecantur said:
I fixed it there was an oversight in the RMA bat file, I attached the fixed bat ONLY you'll have to visit the RMA thread and download the full environment.
Click to expand...
Click to collapse
Fixed yet again, titanium backup now reports Rooted, fix was to run the fixed bat choose 1(normal) let it reboot, then run the bat again choose x(unroot) then run one last time and choose 1(normal). this should clear any polluted data in /data for the flash and then root normally
Use this way instead
This is a much quicker and less messy way to root your rise. It says for hydo but works for rise too. This is how I did mine.
http://www.cricketusers.com/content/646-root-cricket-wireless-kyocera-hydro-tutorial.html
i am hopeing someone can help me out here.
s4 mk2 build#
it seems i cannot update binaries on supersu that is stopping me from rooting my phone
Saferoot seemed like a no brainer just hit a couple keys and command prompts do everything so
I tried the saferoot way which i think half worked. the issue i am having is it seems i am stuck on trying to update supersu binaries. nomatter what i try it wont update.
i have tried thru the play store and downloading to my sd card. although on my card i must admit that i just didn't know which file to load being new to this.
in case those pictures dont show up
i downloaded root checker and it says
Check Command: ls-l ?system?bin?su:
Result: rwsr-sr-x root root 46596 2014-02-19 15:22su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can gain root access!
this leads me to believe i am pretty damn close right?
anyway could you give me a hint as to the way you rooted your phone?
or to someone else that doesn't mind noob questions like this.
Thank you for reading my breakdown and responding if you can.
Chris
Hi
cfh1030 said:
i am hopeing someone can help me out here.
s4 mk2 build#
it seems i cannot update binaries on supersu that is stopping me from rooting my phone
Saferoot seemed like a no brainer just hit a couple keys and command prompts do everything so
I tried the saferoot way which i think half worked. the issue i am having is it seems i am stuck on trying to update supersu binaries. nomatter what i try it wont update.
i have tried thru the play store and downloading to my sd card. although on my card i must admit that i just didn't know which file to load being new to this.
in case those pictures dont show up
i downloaded root checker and it says
Check Command: ls-l ?system?bin?su:
Result: rwsr-sr-x root root 46596 2014-02-19 15:22su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can gain root access!
this leads me to believe i am pretty damn close right?
anyway could you give me a hint as to the way you rooted your phone?
or to someone else that doesn't mind noob questions like this.
Thank you for reading my breakdown and responding if you can.
Chris
Click to expand...
Click to collapse
●●You have Knox Avoid Warranty?