• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root All Root Suggestions and tries here

Status
Not open for further replies.
bmxbubba27 said:
If game theroy's ubuntu mount works why cant we put the files we need for root in the necessary places using that method?
Click to expand...
My mount guide is for accessing the phone in ubuntu like you would in windows. You need write permissions to push the su files to the system directory.
 
Possible root???
For Android 4.0.4

So I found this almost 2 weeks ago and copied it to a document. Now I can't find the website I got it from for the life of me. Was hoping a root guru can eyeball this and rule it out or give it a pass.

I don't feel comfortable trying this not knowing if it will have an adverse effect. Line 8 especially gives me the willies because I think that would send the phone into boot loop.

Being that this is a suggestion thread, I'm only putting this out there.

[HIGH]
adb shell
mv /data/local/tmp /data/local/tmp.bak
ln -s /data /data/local/tmp
adb reboot
adb wait-for-device

adb shell
echo ro.kernel.qemu=1 > /data/local.prop
exit
adb reboot
adb wait-for-device
adb remount

adb push su /system/bin/su


adb shell
chown root.shell /system/bin/su
chmod 06755 /system/bin/su
rm /system/xbin/su

ln -s /system/bin/su /system/xbin/su
exit
adb push Superuser.apk /system/app


adb shell
rm /data/local.prop
rm /data/local/tmp
mv /data/local/tmp.bak /data/local/tmp
exit
adb push busybox /data/local/tmp

adb shell
chmod 755 /data/local/tmp/busybox
/data/local/tmp/busybox mount -o remount,rw /system
dd if=/data/local/tmp/busybox of=/system/xbin/busybox

chown root.shell /system/xbin/busybox
chmod 04755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/xbin
rm -r /data/local/tmp/busybox
sync
exit
adb reboot
[/HIGH]If the first 8 lines don't work replace with these....

[HIGH]
adb shell "cd /data/local && mkdir tmp"
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot

adb wait-for-device
adb shell rm /data/local.prop
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
adb reboot
[/HIGH]By creating a link to from /data to /data/local/tmp, Android will believe you are writing to /data/local/tmp even though you're actually writing to /data. This method is actually used to successfully root many devices, though some have it specifically in the build.prop that /data/tmp is off limits.
 
Has anyone tried lit yet?

If not, here's what I gather from the cryptic Instructions....

---download lit.tar.gz
---extract it and you get folder named lit
---inside that folder there are 2 files (lit & main.c)
---I think you need to place lit on sd of your phone

Then there are no more further instructions....

---filling in blanks I guess you run it from sd
---Then see if you get root shell in ADB

Not sure if these are the steps.

Can this have an adverse effect on the phone if tried?

Here are the files... I have already extracted the files so they're ready to go.

lit
main.c
 
GameTheory said:
Possible root???
For Android 4.0.4

So I found this almost 2 weeks ago and copied it to a document. Now I can't find the website I got it from for the life of me. Was hoping a root guru can eyeball this and rule it out or give it a pass.

I don't feel comfortable trying this not knowing if it will have an adverse effect. Line 8 especially gives me the willies because I think that would send the phone into boot loop.

Being that this is a suggestion thread, I'm only putting this out there.

[HIGH]
adb shell
mv /data/local/tmp /data/local/tmp.bak
ln -s /data /data/local/tmp
adb reboot
adb wait-for-device

adb shell
echo ro.kernel.qemu=1 > /data/local.prop
exit
adb reboot
adb wait-for-device
adb remount

adb push su /system/bin/su


adb shell
chown root.shell /system/bin/su
chmod 06755 /system/bin/su
rm /system/xbin/su

ln -s /system/bin/su /system/xbin/su
exit
adb push Superuser.apk /system/app


adb shell
rm /data/local.prop
rm /data/local/tmp
mv /data/local/tmp.bak /data/local/tmp
exit
adb push busybox /data/local/tmp

adb shell
chmod 755 /data/local/tmp/busybox
/data/local/tmp/busybox mount -o remount,rw /system
dd if=/data/local/tmp/busybox of=/system/xbin/busybox

chown root.shell /system/xbin/busybox
chmod 04755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/xbin
rm -r /data/local/tmp/busybox
sync
exit
adb reboot
[/HIGH]If the first 8 lines don't work replace with these....

[HIGH]
adb shell "cd /data/local && mkdir tmp"
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot

adb wait-for-device
adb shell rm /data/local.prop
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
adb reboot
[/HIGH]By creating a link to from /data to /data/local/tmp, Android will believe you are writing to /data/local/tmp even though you're actually writing to /data. This method is actually used to successfully root many devices, though some have it specifically in the build.prop that /data/tmp is off limits.
Click to expand...

i tried it it didnt work
 
Well, I think I was able to join, but I couldn't even find out how to type in the chat :l

Edit:Hallelujah!! your suppose to click the bottom :laugh:
 
I couldn't figure it out either lol, i logged on through the phone. I'm logging in through pc... hope shabby is still there!
 
No idea... it didn't take 5 minutes to root though. I don't think recovery is installed, but I am just happy to have root and to get rid of MetroPCSeasyWifi! :)
 
So what took us 2 weeks to attempt to do, took 'Bliss' only 5 min? Something tells me he made a pact with an under lord :laugh:
 
Status
Not open for further replies.
Back
Top Bottom