Related
first time posting to these forums and would like to contribute my findings i was able to gain root on the uscc htc desire in adb using some other guides for the evo 4g unlock. but now i need some help on how to get the modified su in the right place to make this work for the apps. these are the steps i used to gain temporary root.
1) installed android sdk to get adb
2) set up the phone in debug mode
3) downloaded the rageagainstthecage-arm5.bin file(attached)
4) ran this from the sdk folder containing adb.exe
Code:
adb.exe push C:/PATH/TO/FILE/rageagainstthecage-arm5.bin /data/local/tmp
adb.exe shell
cd /data/local/tmp
chown 0755 rageagainstthecage-arm5.bin
./rageagainstthecage-arm5.bin
5) adb shell will exit retype adb.exe shell and now you have root
this is as far as i have got so far now i need to know where to put su which i could not find in /system/xbin
also i am new to the android scene so sorry if this is a bad question, but if i were to flash a recovery image of the gsm desire to my cdma would this work to enter adb in recovery mode or would this brick my phone, i didnt know if the recovery affected that or if that was the rom.
I think you need to put su and Superuser.apk on you sdcard (adb push file /sdcard/)
Then
in your su shell prompt
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cat /sdcard/Superuser.apk > /system/app/Superuser.apk
cat /sdcard/su > /system/bin/su
chmod 06755 /system/bin/su
Please let us know if this works.
I hope this works out!
Sent from my USCC HTC Desire using XDA App
i found out that this command doesnt actually make the system directory writeable
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
and running it a second time causes the device to reboot.
any sugetions to make it writable, im willing to work on this, but like i said i have no experience with android although i am very familiar linux.
You are aware that while booted into Android the /system is not writeable?
You have to boot into recovery mode to do this.
i am now, i tried the method for the incredible but it seems to not run adb on bootup at least after about 15 tries it didn't work, any suggestions? is there a way to flash the recovery without effecting the radio or rom because there isn't any roms for this phone as of yet, or could you point me in the right direction to start my research on how to write a rom? would it be the same as rolling your own linux distro?
also though this to be worth mentioning there seems to be no su file currently on the phone.
i got some time this morning to dig around in the payload-update.zip files for the incredible and was wondering if i could use this to install su because it looks like it doesn't flash anything (atleast looking at the script it looks like it doesn't, i cant say that for the binary file what does that do?) just wondering if there would be any adverse affects by applying this in recovery.
It might be worth talking to AmonRA, or Koush (I believe he works on Clockwork Mod) for a custom recovery. As for installing superuser, you could try the unrevoked team. (unrevoked.com) I wish I knew more in terms of development to help but I hope this leads you in the right direction.
blitz2190 - Here is a link to Superuser.apk and su. Link
I think you need to put su and Superuser.apk on you sdcard (adb push file /sdcard/)
Then
in your su shell prompt
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cat /sdcard/Superuser.apk > /system/app/Superuser.apk
cat /sdcard/su > /system/bin/su
chmod 06755 /system/bin/su
I am very interested to know how this works out. If you need anyone else to help test things let me know. I am not a linux buff, but i can follow commands...
CreepingDeath said:
I am very interested to know how this works out. If you need anyone else to help test things let me know. I am not a linux buff, but i can follow commands...
Click to expand...
Click to collapse
Do you have a USCC Desire?
northmendo said:
Do you have a USCC Desire?
Click to expand...
Click to collapse
Yes I do, and I am willing to help out where I can.
CreepingDeath said:
Yes I do, and I am willing to help out where I can.
Click to expand...
Click to collapse
A couple q's fof you.
Do you have a Mac or PC?
Do you have adb installed?
I will help if I can. I have the phone and a Mac and don't have adb installed.
Sent from my USCC HTC Desire using the XDA App
dhh93 said:
I will help if I can. I have the phone and a Mac and don't have that apply.
Sent from my USCC HTC Desire using the XDA App
Click to expand...
Click to collapse
Cool first install adb. Follow these instructions to install it on Mac.
HERE
Ok doing that right now.
dhh93 said:
Ok doing that right now.
Click to expand...
Click to collapse
Great. I would start by trying the the method from the first post give me about 5 mins and I will post them in a mac friendly format.
Ok will wait on that
Alright, since i had a couple of problems with adb remount, i decided to do some research.
I'm running the latest OTA (2.10.405.2) rooted with Unrevoked 3.21, using Clockwork Recovery Mod 2.5.0.7.
Now once i go to the adb shell and type adb remount, i get the following error: (do mind, this is fully booted, i dont know if a remount is possible while booted?)
adb devices
List of devices attached
BLA12345 device
adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
Ive read something about figuring out if adb recognizes your device as root, so i tried doing this with getprop ro.secure
It returned the following:
adb shell
$ getprop ro.secure
getprop ro.secure
1
Click to expand...
Click to collapse
This means adb does not recognize my device as root, so i booted into recovery, went to adb again and did the same. This time it returned:
adb devices
List of devices attached
BLA12345 recovery
adb shell
~# getprop ro.secure
getprop ro.secure
/sbin/sh: getprop: not found
Click to expand...
Click to collapse
Now, i can always mount the /system partition manually by going into clockworkmod recovery, but i'd like to be able to use adb remount aswell. Does anyone know what's going on and how to fix this
Thanks in advance!
Up.
10 chars
for starters we cant mount /system as r/w while booted... as it stands we dont even need to use the remount command, as we only have r/w access to system whilst in recovery, if you just use the mount /system command, it will automatically be mounted as r/w
AndroHero said:
for starters we cant mount /system as r/w while booted... as it stands we dont even need to use the remount command, as we only have r/w access to system whilst in recovery, if you just use the mount /system command, it will automatically be mounted as r/w
Click to expand...
Click to collapse
Aaah alright, i get the picture now! Seems they have released S-OFF today tho, time to start using remount?
Lunatic2 said:
Aaah alright, i get the picture now! Seems they have released S-OFF today tho, time to start using remount?
Click to expand...
Click to collapse
i only just noticed that after i replied to your post happy days
I'm not sure what I did but whenever I try to do a backup in ROM manager or use it to reboot into recovery nothing happens. I've tried re flashing clockwork mod and using the fix permissions but it gives me an error message stating that an error occurred while attempting to run privileged commands. I can still do a back up like normal if I do it from recovery but I'm a little nervous since ROM manager isn't working.
Do you have S-OFF?
Yes, running virtuous 3.0.1 and radio 2.15.00.07.28
I have the exact same problem, I can boot into clockwork but when I click on recovery it just reboots into clockwork's main page.
Edit: I tried to reflash an older recovery using ROMmanager and it worked, then I flashed the current one, so that might work.
Recovery versions 2.5.0.5 and 2.5.0.1 are OK. Anything later then that has problems and been pulled for the exact problems quoted here.
I have recovery version 2.5.0.5. I tried to flash 2.5.0.1 but I got a message that said "an error occurred while attempting to run privileged commands!"
Folks, there's been a fix posted for this I believe---and I was one of the posters.
This is what worked for me:
In ROM Manager, go to bottom of screen and select All ClockworkMod Recoveries. Simply select an earlier version of CWM. I selected 2.5.0.0. You should be good to go after selecting and hitting OK. Then, after a reboot, you should be able to reselect the latest CWM recovery.
Good luck!
I've already tried that... flashing any version of clockwork gives me the error message "An error occurred while attempting to run privileged commands!"
Check out this post from adrynalyne and see if it helps. Sounds like your issue.
http://adrynalyne.us/?p=90
Sent from my ADR6300 using XDA App
I've never used adb before, any chance someone could walk me through this or point me to a quick guide to get me started?
Look in the stickies section. There's a thread from AndroidBruce for a "How-to." There's a link covering adb. Once it's installed, it's pretty much typing exactly what's written, unless you're big on using linux.
Sent from my ADR6300 using XDA App
I tried that method but no luck. After I entered the command it gave me a message saying "/sbin/sh: system/bin/e2fck: not found"
NewUserNeedsHelp:) said:
I tried that method but no luck. After I entered the command it gave me a message saying "/sbin/sh: system/bin/e2fck: not found"
Click to expand...
Click to collapse
If your on a sense rom use e2fsck_recvy
Sent from my ADR6300 using XDA App
Again, no luck :/ this is beginning to really frustrate me. This is what I typed and what was returned to me, maybe someone can see something I did wrong with it.
C:\android-sdk-windows\tools>adb shell
~ # system/bin/e2fsck_recvy -p /dev/block/mmcblk0p2
system/bin/e2fsck_recvy -p /dev/block/mmcblk0p2
/dev/block/mmcblk0p2 has been mounted 1137 times without being chec
rced.
/dev/block/mmcblk0p2: 13/51200 files (7.7% non-contiguous), 12120/2
~ # exit
exit
Just tried again and got this:
C:\android-sdk-windows\tools>adb shell
~ # system/bin/e2fsck_recvy -p /dev/block/mmcblk-p2
system/bin/e2fsck_recvy -p /dev/block/mmcblk-p2
system/bin/e2fsck_recvy: No such file or directory while trying to open /dev/bl
ck/mmcblk-p2
/dev/block/mmcblk-p2:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
NewUserNeedsHelp:) said:
Again, no luck :/ this is beginning to really frustrate me. This is what I typed and what was returned to me, maybe someone can see something I did wrong with it.
C:\android-sdk-windows\tools>adb shell
~ # system/bin/e2fsck_recvy -p /dev/block/mmcblk0p2
system/bin/e2fsck_recvy -p /dev/block/mmcblk0p2
/dev/block/mmcblk0p2 has been mounted 1137 times without being chec
rced.
/dev/block/mmcblk0p2: 13/51200 files (7.7% non-contiguous), 12120/2
~ # exit
exit
Just tried again and got this:
C:\android-sdk-windows\tools>adb shell
~ # system/bin/e2fsck_recvy -p /dev/block/mmcblk-p2
system/bin/e2fsck_recvy -p /dev/block/mmcblk-p2
system/bin/e2fsck_recvy: No such file or directory while trying to open /dev/bl
ck/mmcblk-p2
/dev/block/mmcblk-p2:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Click to expand...
Click to collapse
the bolded is not the right command
are you adb shelling in recovery, then mounting system, then unmounting cache?
I'm unmounting chache then mounting system and then adb shelling. Does adb shelling mean starting the shell in cmd?
NewUserNeedsHelp:) said:
I'm unmounting chache then mounting system and then adb shelling. Does adb shelling mean starting the shell in cmd?
Click to expand...
Click to collapse
Do you know how to use adb? Not trying to be rude here....just trying to help
boot to recovery, then adb shell (this is in the cmd window), then mount system, then unmount cache, then run the cmd
Lol, no this is my first experience with adb and I have virtually no clue what I'm doing, I'm just trying to follow instructions the best I can. The guide that I was following had me doing things in a different order so I guess I'll have to try this now. Thanks for your assistance and patience!
NewUserNeedsHelp:) said:
Lol, no this is my first experience with adb and I have virtually no clue what I'm doing, I'm just trying to follow instructions the best I can. The guide that I was following had me doing things in a different order so I guess I'll have to try this now. Thanks for your assistance and patience!
Click to expand...
Click to collapse
you have gtalk? check your pm
In case anyone is following this; I still have not fixed the problem.
how would one add an mp3 file to the read only directory
( system/media/audio/alarms )
the stock ones really don't wake me up
from what i do know the directory is a read only directory and really would like to
put this alarm.mp3 in the that read only folder...
appreciate your help and thanks in advance...
I highly suggest you buy the app "root explorer"
would astro do the same thing?...
Sent from my PC36100 using XDA App
are you fully rooted? if not, i know the answer.
I think I am...how would one confirm?... appreciate your help
Sent from my PC36100 using XDA App
if you have the android sdk set up use "adb remount". It should say something like partition remounted successfully. If you see that then all of your read only directories will be reset to read/write. Afterwards just reboot your phone and it will set everything back to normal.
thank you.....i tried that command and received this error:
remount failed: Operation not permitted
does this mean that I'm not fully rooted? what next?
appreciate your help xHausx ...
1candydick said:
thank you.....i tried that command and received this error:
remount failed: Operation not permitted
does this mean that I'm not fully rooted? what next?
appreciate your help xHausx ...
Click to expand...
Click to collapse
could be, do you have the superuser app in your app drawer? a few more things you can try is typing:
adb shell {enter}
mount system {enter}
at this point you will see either a $ or # sign, the # sign means you have root. If you see the $ type:
su {enter}
if that doesn't change it to a # then try typing
sh0 {enter}
su {enter}
if that still doesn't work then you need to use an exploit to get root. However, if it does work and you see # then type:
mount -t yaffs2 -o remount,rw /dev/block/mtdblock4 /system {enter}
You can put these on your SD card too, you just have to put it in /media/audio/alarms (you can also use "notifications" or "ringtones" instead for those).
mv and chmod should work
Trying to install openvpn, installer fails, have resorted to trying to install it manually, unzipping apk and taking openvpn-2.1.1-static-xbin asset, copying that to system\xbins , but when I try and run it I get the error
error: only position independent executables (PIE) are supported.
Can anyone help with how to fix this?
Loading the OpenVPN settings says all prerequisites are there, but launching any configs (PIA OpenVPN's) produces this error in the log.
Many thanks
Andy
andywuk said:
Trying to install openvpn, installer fails, have resorted to trying to install it manually, unzipping apk and taking openvpn-2.1.1-static-xbin asset, copying that to system\xbins , but when I try and run it I get the error
error: only position independent executables (PIE) are supported.
Can anyone help with how to fix this?
Loading the OpenVPN settings says all prerequisites are there, but launching any configs (PIA OpenVPN's) produces this error in the log.
Many thanks
Andy
Click to expand...
Click to collapse
Check permissions
Enviado desde mi A0001 mediante Tapatalk
andywuk said:
error: only position independent executables (PIE) are supported.
Click to expand...
Click to collapse
Whatever you are trying to run is too old. It needs to be updated for Lollipop. Lollipop started enforcing that all binaries be compiled with PIE.
Thanks for that rbox, it seems it was an old binary, found a newer one on thread
http://forum.xda-developers.com/spr...nvpn-binary-lollipop-s5-t3086672#post64696367
took that, installed manually
adb shell
su
mount -o remount rw /system
cp /sdcard/openvpn /system/xbin/
rm /sdcard/openvpn
chmod 755 /system/xbin/openvpn
mount -o remount ro /system
and it seems to be running now, just an issue with my vpn config left.
andywuk said:
Thanks for that rbox, it seems it was an old binary, found a newer one on thread
http://forum.xda-developers.com/spr...nvpn-binary-lollipop-s5-t3086672#post64696367
took that, installed manually
adb shell
su
mount -o remount rw /system
cp /sdcard/openvpn /system/xbin/
rm /sdcard/openvpn
chmod 755 /system/xbin/openvpn
mount -o remount ro /system
and it seems to be running now, just an issue with my vpn config left.
Click to expand...
Click to collapse
Did you end up being successful in configuring openvpn? I have performed exactly the same steps and cannot get it to work. Cheers