[Q] gingerbreak trouble with droid x - General Questions and Answers

I am trying to root my droid x without success. It is stock Gingerbread 2.3.3. Version 4.5.596
I have tried formatting my sd card without benefit.
I have usb debuging enabled.
The logcat seems to indicated the data/data/ directory is not present or readable.
I tried mkdir /data/data from adb shell and I get:
opendir failed, Permission denied
Any suggestions?
rkshack

you have to install the older rom 2.3.3 won't work
Sent from my Xoom using XDA Premium App

Related

need help rooting flipside

i have a motorola flipside with 2.2.2 installed. somehow it lost its root and will not reroot z4root keeps shuting down and giving some odd error saying The application z4root (process com.z4mod.z4root) has stopped unexpectedly. Please try again and leaves only the option to force close the app. i left gingerbreak running all night and when i woke up it was still running not getting anywhere theyed superoneclick it will not finish im getting very fustrated with this phone i even went as far as asuming somthing on the phone went bad and flashed it to a stock att rom and still cannot get the root to finish and apply. is there some way i can mannualy root this phone? also yes usb debuging is on allow unknown aps to install is enabled
anyone please this dam phone is practicaly useless without a root to me id rather be using my stupid windows 7 phone at this rate because at least it had my ringtones and allowed me to use a different backround image than stock att ones.
---------- Post added at 02:09 PM ---------- Previous post was at 01:47 PM ----------
ok i have come accross this but i am a little lost at the steps
wiki.rootzwiki.com/index.php/Motorola_Flipside
it says to download 3 files psneuter busybox and super user unzip the downloads into the same folder. then it says to open a terminal and change to the folder i dont understand this what am i suposed to to? it then says i need android sdk installed and working witch i do i installed it for android screencast. then it says adb devices but does not say how im suposed to enter this command. after that im fairly sure its from the cmd entering the commands shown on that link. can anyone tell me how to get throgh the first few steps please?
copyed from link
Manual Root
[edit] Download
psneuter: Download
Superuser: Download
busybox: Download
Unzip the downloaded files into the same folder
Open a terminal and change to the folder.
You need the android SDK and ADB working. To make sure type:
adb devices
if your device lists, then you are ready to go!
[edit] Gain Root
Run the following commands:
adb push psneuter /data/local/temp/psneuter
adb shell
chmod 755 /data/local/temp/psneuter
./data/local/temp/psneuter
ADB should hang, wait a little while and then type:
adb shell
NOTE: You should have the "#" sign instead of the "$". If you do, you have temporary root, and can continue on.
Type:
exit
adb push busybox /data/local/temp/busybox
adb shell
chmod 755 /data/local/temp/busybox
./data/local/temp/busybox mount -o rw,remount /system
The last command should return nothing
update i learned how to do the procedure and finished sucesfully however the phone is still not rooted. i did reboot the phone after it seems faster now but not rooted.i downloaded the root checker app and scaned the phone it emailed me a log and here is that log
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 2.3.6.3 is installed!
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your MB508 device by Root Checker version 3.7 from joeykrim in the Android Market
is it even posible to root this phone?
i guess im not allowed to be helped or somthing.
i have a procedure here that i had to build up from 2 seperate write ups. i had to use this one http://androidforums.com/droid-all-...oid-without-rsd-lite-up-including-frg83d.html along with this one together http://wiki.rootzwiki.com/index.php/Motorola_Flipside to get it to root properly.
here is what i did. u will need the downloads from both links for this to work i beleive. follow the steps from the second link to gain root once u get to where the number simbole is shown in the command line u need to switch to the instructions in link 1 and start at step 13 and follow to the end. this works to root your flipside when nothing els will work at least for me it did none of the apps that are suposed to root for you worked for me.
thank you me for having to figure this out on my own have fun
Problem rooting
I rooted my Flipside at its stock state and it worked fine. And then I upgraded my software to 2.2.2 Froyo and lost the root so now I am trying to reinstall z4root and re-root the phone but z4root now doesn't work. It gets successfully installed but when I hit PERMANENT ROOT it just stays in that window with the turning wheel and gets stuck there. It doesn't completely root. I've tried the hard reset by pulling the battery, and hitting the back key and forced closing it and then trying it again. Nothing works! HELP!
I once had a flipside. I rooted it the stock rom and then updated to gingerbread and then rooted again. I used superoneclick though. I'm not sure which version, but there is (or was) a flipside forum here on xda with documentation on the entire process.
Edit: here's the forum link: http://forum.xda-developers.com/forumdisplay.php?f=772
jovanphilip said:
I once had a flipside. I rooted it the stock rom and then updated to gingerbread and then rooted again. I used superoneclick though. I'm not sure which version, but there is (or was) a flipside forum here on xda with documentation on the entire process.
Edit: here's the forum link: http://forum.xda-developers.com/forumdisplay.php?f=772
Click to expand...
Click to collapse
Really? I thought the only upgrade I can do to it is from stock to Froyo. How'd you do that? I'm sorry. I am totally untechie. :/

adb push Superuser3-beta1.apk /data/app/ PERMISSION DENIED?

I have adb set up properly and I am running this command in the root shift kit and I get this : C:\adb>adb push Superuser3-beta1.apk /data/app/
failed to copy 'Superuser3-beta1.apk' to '/data/app//Superuser3-beta1.apk': Perm
ission denied
What am I doing wrong? USB Debugging is on and the phone is set to charge only all the correct files are where they need to be?
MJ
What Android Version were you on when you began the process? Also what method did you use to start the Downgrade process?
It actually worked I pulled battery restarted the computer changed ports this was the old method in adb
Sent from my SPH-D710 using XDA
Well glad to hear you got it sorted out.

[Q] Please help me for rooting AT&T One X

Hi guys, I'm in Turkey and my friend went to USA 4 months ago. He promise bought me a HTC One X, when he bought my htc one x in amazon, amazon sent my friend a AT&T One X. This is not intentionally, and we sent message to amazon. And they sent me network pin to unlock my network. And I want to root, unlock bootloader, super cid . But I can't make this at the moment. I installed over and over htc drivers, and opened usb debugging mode, and opened root exploid. but this exploid says:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
failed to copy 'busybox' to '/data/local/busybox': Permission denied
failed to copy 'su' to '/data/local/su': Permission denied
failed to copy 'Superuser.apk' to '/data/local/Superuser.apk': Permission denied
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/su: No such file or directory
Unable to chmod /data/local/Superuser.apk: No such file or directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
REBOOT
/system/bin/sh: cannot create /data/local.prop: Permission denied
AGAIN REBOOT
I can't unlock bootloader, and I can't root and I cant make super cid.
Please help me and I am sorry my English
What method are you attempting to use?
Sent from my HTC One XL using Tapatalk 2
I used to root-one-x exploit, hasoon exploit,..... I used all methods
Sent from my HTC One X using xda app-developers app
xenonflash7 said:
I used to root-one-x exploit, hasoon exploit,..... I used all methods
Click to expand...
Click to collapse
You need to figure out what hboot and firmware version you're on first. Different root methods for each.
Check your Settings>About>Software information and see what it says under Android version and Software number.
Then reboot to bootloader and see what it says next to HBOOT.
2.20.502.7 710RD my software number and 4.0.4 my android build
Sent from my HTC One X using xda app-developers app

Is it impossible?

Hi guys, I'm in Turkey and my friend went to USA 4 months ago. He promise bought me a HTC One X, when he bought my htc one x in amazon, amazon sent my friend a AT&T One X. This is not intentionally, and we sent message to amazon. And they sent me network pin to unlock my network. And I want to root, unlock bootloader, super cid . But I can't make this at the moment. I installed over and over htc drivers, and opened usb debugging mode, and opened root exploid. but this exploid says:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
failed to copy 'busybox' to '/data/local/busybox': Permission denied
failed to copy 'su' to '/data/local/su': Permission denied
failed to copy 'Superuser.apk' to '/data/local/Superuser.apk': Permission denied
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/su: No such file or directory
Unable to chmod /data/local/Superuser.apk: No such file or directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
REBOOT
/system/bin/sh: cannot create /data/local.prop: Permission denied
AGAIN REBOOT
I can't unlock bootloader, and I can't root and I cant make super cid.
2.20.502.7 710RD my software number and 4.0.4 my android version
Sent from my HTC One X using xda app-developers app
Can you post a link to the exploit you are using?
Sent from my HTC One X using Tapatalk 2
I think you're using the wrong exploit. You need this one:
http://forum.xda-developers.com/showthread.php?t=1952038
I used x factor exploit, it says "failed" and it didn't continue
Sent from my HTC One X using xda app-developers app

[Q] Have I bricked the thing?

So I went to replace libaudioflinger.so in /system/lib with one I'd built myself, but unfortunately something obviously went wrong and when I rebooted the device, it just hangs on the loading screen.
The good thing is that the original file is in /sdcard named '_libaudioflinger.so_', and I can connect via adb there. If i run 'su' which gives me some sort of root access, but when I try 'mount -o remount rw /system', it shows up as "Operation not permitted". If I'm able to get that filesystem mounted, I just need to run "mv /sdcard/_libaudioflinger.so_ /system/lib/libaudioflinger.so", anybody any ideas how I might be able to recover this?
seaders said:
So I went to replace libaudioflinger.so in /system/lib with one I'd built myself, but unfortunately something obviously went wrong and when I rebooted the device, it just hangs on the loading screen.
The good thing is that the original file is in /sdcard named '_libaudioflinger.so_', and I can connect via adb there. If i run 'su' which gives me some sort of root access, but when I try 'mount -o remount rw /system', it shows up as "Operation not permitted". If I'm able to get that filesystem mounted, I just need to run "mv /sdcard/_libaudioflinger.so_ /system/lib/libaudioflinger.so", anybody any ideas how I might be able to recover this?
Click to expand...
Click to collapse
Hopped on #android-root and they got me all sorted. Basically just had some sort of a bad root/su which wasn't giving me the correct access. All back up and running 100% now, though.
If it boots into the bootloader you can always flash the factory image
Sent from my Nexus 5 using XDA Free mobile app
You can't brick a device by swapping system files.
Sent from my Nexus 5 using Tapatalk

Categories

Resources