Okay, So I have a Samsung Admire running 2.3.4 and has a kernel of 2.6.35.7. Purchased 3 weeks ago. I rooted the phone and within a day I had lost the ability to make or receive calls. the phone app crashes every time.and I thought that I had deleted some vital file and thus ruined the phone. After a couple days and nights reading and experimenting I believe that that changing the screen density with Rom Toolbox from 160 to 167 is causing the app to fail. Now the problem is my inability to get rooted again, after resetting back to factory. Nothing I have tried will work and what may, seems baffling. I tried multiply times the original method that was successful, Admire_Root_Windows, Super one click, I tried running both from the SD card, I even downloaded a handful of Android Development programs because I read somewhere that I had to, I'm desperate here. I even came across this :
This was successful with: (I bought the phone 3 days ago)
Android: 2.3.4
Kernel: 2.6.35.7
You need a copy of su, and superuser. (If you have superone click, its all there, just run it adb from that directory)
adb shell "rm /data/log/dumpState_app_native.log 2>/dev/null"
adb shell "ln -s /data/local.prop /data/log/dumpState_app_native.log 2>/dev/null"
adb shell "app_process /dev/null"
REM This command may take a while.
adb shell "echo "ro.kernel.qemu=1" > /data/local.prop 2>/dev/null"
adb reboot
REM Device vibrates (kinda pulses) This is good.
adb wait-for-device
adb shell "rm /data/local.prop 2>/dev/null"
adb shell "rm /data/log/dumpState_app_native.log 2>/dev/null"
adb remount
Thats it, your device is rooted. Now to install the goodies...
adb push su /system/xbin/su
adb shell "chmod 4755 /system/xbin/su"
adb shell "ln -s /system/xbin/su /system/bin/su"
adb install Superuser.apk
Now, before anything else happens, I was having issues with full root. (Root checker claimed everything was fine.. titanium backup worked, but could not remove some crapware..) so at this point, you can go into /system/app and remove the Metro apks. I'd recommend clearing Dalvik cache after you're done as well.
adb reboot
That looks great but there are no instructions and in where does that get typed?
I will have to go buy another at some point tomorrow if I dont get this phone fixed. All I need to do is change the screen res back to 160 and I "think" it will be fine. Everything else runs like a champ. BTW, I do have a LG Optimus T / LG P509 running 2.2. maybe I can use it to fix the other. It's inactive and I have no plans to call tmobile and have it turned on. Please make your answers as though you are dealing with someone who's had a lobotomy, seriously.
How can I reroot?
Thanks,
Zeke
Well...Never mind, I managed to get it figured out...
Thanks,
Zeke
Related
Hey guys, this is my first post, and I just wanted to say first off that all of you who have figured out how to root phones are awesome! Because of xda-developers and androidforums, I helped a friend root and put cyanogenmod 6 on his HTC Hero (cdma).
Anyway, I'm trying to put Zefie's CM7 on my LG Optimus V, and I'm stuck. First off I'm trying to root my phone. I'm following this guide: [How-To] Root the LG Optimus V on Android Central (I'd post the link, but the system won't let me since I'm a new user.). Usually I'd follow the instructions step by step, but I had to make some changes. I see this guide is written for Windows, but I'm running Ubuntu 10.10. After doing a lot of searching I was able to figure out that I had to install the Linux version of the Android SDK and use mono to run SuperOneClick.exe. That part was easy since I have a good knowledge of Linux and how it runs. The part that I'm stuck at is performing a Shell Root. When I click on Shell Root, SuperOneClick is stuck at "Waiting for device..." It's been like this for a while. If I click on Root, it gets stuck at "chmod psneuter..." Either way it's stuck and I don't know what to do.
Just to let you guys know, I have USB Debugging turned on, and I'm running Android version 2.2.1.
When I rooted my friend's HTC Hero, all I had to do was run a downloaded apk onto his SD card and run it, and then it would instantly root it. Is there a similar apk for the Optimus V? If not, is there a way I can manually root it via the terminal? Anyway, I'm stuck and would appreciate any suggestions or comments. Don't forget, I'm running Ubuntu 10.10, so some issues may arise since the tutorial was meant to be run on Windows machines.
Later tonight I'm going to try to root my phone at my friend's house since he has a computer running Windows XP. Hopefully I can get some better progress on his computer instead of mine. Thanks in advance for all your help!
Okay, nevermind. I did a little more searching and found a way to root my phone without running SuperOneClick.exe. I'll post if I have any more problems.
Well I spoke too soon. Here are the steps I followed to get to a # prompt in adb:
./adb push psneuter /data/local/tmp
./adb shell chmod 777 /data/local/tmp/psneuter
./adb shell /data/local/tmp/psneuter
I then did the following commands:
adb shell
mount -o remount,rw -t yaffs2 /system /system
exit
adb push su /system/bin
adb push busybox /system/bin
adb shell
cd /system/bin
chmod 4755 su
chmod 555 busybox
exit
adb reboot
After rebooting the phone, I installed Superuser and TitaniumBackup. I opened TitaniumBackup and it gave me an error stating that it could not acquire root privileges. I know for a fact that my phone has su and Busybox installed on it and have the correct permissions.
What bugs me even more is that when I run su via the adb shell root prompt or a terminal emulator on my phone, it returns the following error:
link_image[1997]: failed to link su
CANNOT LINK EXECUTABLE
What's up with that? I did find out that some people have had issues with Android 2.2.1 on their phone, and unfortunately that's what my phone had when I bought it about a month ago.
Okay, I figured it out finally and have my phone rooted. I had to run SuperOneClick.exe on my buddy's Windows computer. Instead of doing a Shell Root, I just clicked Root and it rooted. Now I'm stuck at figuring out how to do a Nandroid backup. I backed up everything using Titanium Backup, but I know I want to make a backup rom in case something goes wrong during the flash. What are the steps to performing a Nandroid backup?
Lol nevermind. I got Zefie's CM7 up and running this morning.
Nandroid is made using recovery. Glad you got it working
Sent from my VM670 using XDA App
bhambalek said:
Okay, nevermind. I did a little more searching and found a way to root my phone without running SuperOneClick.exe. I'll post if I have any more problems.
Click to expand...
Click to collapse
I am having the same problem as you, can you link me the other method?
EDIT: I do see the instructions in the next post, however where did you find them and get the files?
I been looking for an ATT Avail root guide since january, I found this page today and I am wondering if anyone has done this successfully?
if you google "root att avail" it is the top search result link right now and it is at a site called android police.
here is a copy/paste of the article:
New root methods show up all the time, so it's not a huge deal that a rather unknown phone on AT&T is now rooted. So why are we posting about it? Because the root method used is, well... interesting.
It was uncovered by our own Justin Case from TeamAndIRC, and while a big part of the process will look very familiar to some of you, there is one step that induces a wait, what? moment.
Before you get started throwing commands at the little guy, though, you need to grab this file. After that, commence command throwing.
adb shell rm -r /data/local/logs (if this command gives you an error, do not worry, it is precautionary)
adb shell mkdir /data/local/logs
adb shell ln -s /data/local.prop /data/local/logs/loglast1.tar.gz
Dial *983*7668# on your phone. This does a few things, it mounts /system as writable on boot, and creates the loglast1.tar.gz.
Wait about 10 seconds, then continue.
adb shell echo 'ro.kernel.qemu=1' > /data/local.prop (Nod to Rosenberg here)
adb reboot
Once the phone reboots, continue
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm -r /data/local/logs
adb shell rm /data/local.prop
adb shell rm /data/property/persist.sys.ztelog.enable
adb shell rm -r /data/local/rwsystag
Head into the Market and grab the Superuser app.
Done.
Catch that bold part? Looks like someone at ZTE dropped the ball and left seventy-nine developer codes in the retail version of the device. Oops.
Of course, their mistake is your gain. Hell, there's even a code to disable Carrier IQ: *983*24737#. Enter the code, ???, profit.
While this is definitely an unusual and unique find, it's also quite dangerous. This means that any app can mount the system as writable and, from there, basically control everything. As a result, JCase contacted ZTE to let them know of their oversight.
Click to expand...
Click to collapse
if someone could let me know if this is legit, that would be a fantasticism.
yes that is legit.
see my thread:
http://forum.xda-developers.com/showthread.php?t=1437032
Jcase broke it, the loon created a batch file to make it easier
http://forum.xda-developers.com/showpost.php?p=21627136&postcount=37
thats the last version of the batch file
Cool, thanks, for some reason I cannot connect to my avail via usb, I have it in developer mode and unknown sources checked, I ran adb devices command and it does not find my phone and when I try to run or debug in eclipse it does not find my phone there either.
I used it, and now have root. I wish all phones were this easy to root.
I wanted to share my experience with following this thread
http://forum.xda-developers.com/showthread.php?t=1709296
i unfortunatly do not meet the 10 post limit
Following the process i got stuck here
Code:
Now it's time to reboot
adb reboot
After phones reboots
adb remount <-----------------HERE---------------------------
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
ADB told me that i dod not have the correct permissions to push the SU file to the phone. The phone would boot, but would not load the widgets or bottom menu. Attempting to open settings would prompt Android.Core to crash.
Scary stuff
The problem was with the ADB Reboot command. It normally reboots the phone properly, but when i ran ADB Reboot, the phone cut power (off) instead of rebooting. Something did not go as intended and i needed to power on my phone, and reboot it manually without the USB cable connected (lagged too much).
After that, the ADB Remount was successful and the rest of the process ran smoothly. I am happily rooted
Thank you to all
~Can someone copy this into the actual thread? I want to help spread rootsauce.
Update: Friday November 2nd 2012
Fixed a bad upload of the su file, must of become corrupt sorry.
Silly permission bug again, but w/e. LG should know better, from what I am told this is a recently released device. This is a long standing known issue. Lg get your sh*t together.
Directions:
unzip su.zip into the current path (directory) you are in.
adb shell
(while in adb shell)
rm /data/local/tmp/profile_calib_m
ln -s /data/local.prop /data/local/tmp/profile_calib_m
exit
adb reboot
adb wait-for-device shell
(once in the adb shell again)
echo 'ro.kernel.qemu=1' > /data/local.prop
rm /data/local/tmp/profile_calib_m
exit
adb reboot
adb wait-for-device remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
Once rebooted install superuser from the market:
https://play.google.com/store/apps/details?id=com.noshufou.android.su
As usual thanks for all your work for this GREAT community!!! :good:
Thanks for letting me watch you work & getting root for my wife's phone.
Edit: DroidHost of Androidarea51.com has made a OneClick for this phone using Jcase's root. it also installs a recovery & Superuser all at the same time.
androidarea51.com/***-all-things-
root-***-174/
Help Me Please
what do you do when it says permission denied or not permitted when waiting for device, remounting, or pushing su?
lol now all we need is someone to write different roms :>
cyanogen would be nice :> lol
thank you for rooting this phone :>
jcase, i pmd you i need help please
TechManPro said:
what do you do when it says permission denied or not permitted when waiting for device, remounting, or pushing su?
Click to expand...
Click to collapse
run adb shell
make sure your prompt is a # not a $. If it is a $ start over, if it is a # make sure you run adb remount.
jbach44 said:
lol now all we need is someone to write different roms :>
cyanogen would be nice :> lol
thank you for rooting this phone :>
Click to expand...
Click to collapse
No problem.
You actually left out a step. In order to push su to the phone you have to adb remount -o rw. Otherwise it is a read-only filesystem and it cannot be pushed to the phone. Most people would probably get this, but the novices who end up with bricked phones will be angry.
Great work!
iliekandroid said:
You actually left out a step. In order to push su to the phone you have to adb remount -o rw. Otherwise it is a read-only filesystem and it cannot be pushed to the phone. Most people would probably get this, but the novices who end up with bricked phones will be angry.
Great work!
Click to expand...
Click to collapse
Actually no, you are incorrect.
adb remount without the additional parameters is correct, and not possible of bricking a phone with adb remount. No novice would be angry, because there is not possible brick from this guide, as long as it is followed.
I got the LG for my daughter (13 going on 30), and now it works fine. Thanks jcase.
Did not unlock my lgl35g
Yes I am a Noob... nobody likes me
I have exhausted every resource that I could find on this phone. I thought that this post was the answer to my problem, however it did not seem to help at all. Everything seemed as if it was working fine as I went step by step through the process. However, I rebooted my phone and there is no difference then when I started. The "su.zip" file enclosed in this post was not able to extract into the directory of my ADB client. It kept saying root already existed, but I was unable to see it in windows explorer? Is this "su.zip" a modified version of a pre-existing file in the SDK kit? I really need to unlock this phone so that I can clean up the junk. Any help would be greatly appreciated.
jcase said:
Update: Friday November 2nd 2012
Fixed a bad upload of the su file, must of become corrupt sorry.
Silly permission bug again, but w/e. LG should know better, from what I am told this is a recently released device. This is a long standing known issue. Lg get your sh*t together.
Directions:
unzip su.zip into the current path (directory) you are in.
adb shell
(while in adb shell)
rm /data/local/tmp/profile_calib_m
ln -s /data/local.prop /data/local/tmp/profile_calib_m
exit
adb reboot
adb wait-for-device shell
(once in the adb shell again)
echo 'ro.kernel.qemu=1' > /data/local.prop
rm /data/local/tmp/profile_calib_m
exit
adb reboot
adb wait-for-device remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
Once rebooted install superuser from the market:
Click to expand...
Click to collapse
anyone know of a way to SIM unlock this device? I have AT&T and would like to use it om there, i bought it for $30 on clist thinking net 10 would work with an AT&T SIM but was wrong, any help would be appreciated...
anyone know of a way to SIM unlock this device? I have AT&T and would like to use it om there, i bought it for $30 on clist thinking net 10 would work with an AT&T SIM but was wrong, any help would be appreciated...
Click to expand...
Click to collapse
What is weird about that is i put the sim in a iphone and it worked just fine!!! Best bet would be ebay for unlock...
I have the Net10 one that I put a Straight Talk SIM in with no problems if I can get my hands on a AT&T SIM today I'll check it out.
---------- Post added at 07:39 AM ---------- Previous post was at 07:34 AM ----------
NateDoggTN said:
Yes I am a Noob... nobody likes me
I have exhausted every resource that I could find on this phone. I thought that this post was the answer to my problem, however it did not seem to help at all. Everything seemed as if it was working fine as I went step by step through the process. However, I rebooted my phone and there is no difference then when I started. The "su.zip" file enclosed in this post was not able to extract into the directory of my ADB client. It kept saying root already existed, but I was unable to see it in windows explorer? Is this "su.zip" a modified version of a pre-existing file in the SDK kit? I really need to unlock this phone so that I can clean up the junk. Any help would be greatly appreciated.
:
Click to expand...
Click to collapse
Did you push the su binary file or the whole folder? If you pushed the whole folder you will have to remove the directory & start over.
how to run root
Sorry for sounding like a noob, but I am...when it comes to LG. im trying to root my homies LG optimus logic but im not sure where to run the command from. if some one could help me out on to where the zip should actullay be placed and unziped to that would be a big help, thanks. and if there is a thread already for this please hook up a link.
thanks
thanks mate for this
i appreciate your time.
Anyone know of a rooted ROM
I have looked all over, but it doesn't look like a dev has created a ROM for this device. Has anyone come across one? If I knew programming I would give it a shot, but it's a mystery to me. I know that CyanogenMod 9 for the L3 (e400) works, but there is a problem with the radios, hence no cellular, wifi, or bluetooth.
Source code......
http://www.lg.com/global/support/opensource/opensource-detail.jsp
http://forum.xda-developers.com/showthread.php?p=34104009
This guy had some success with CM9, but no radio. Anyone know how to extract the radio? I've never built a rom, but this is tempting.
Hello I have a HOX from att with the 1.85 software number.
I attempted to use this method to root my phone. http://forum.xda-developers.com/showthread.php?t=1709296
I proceeded with the instructions as followed and was sucessfully able to run these commands:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb reboot
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
adb shell ls -l /data/local.prop
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Now it's time to reboot
adb reboot
After phones reboots
adb remount
The command prompt indicated a successful remount. (At this point on the phone only the notification bar was working and nothing else was on the screen and right now that is where my phone is stuck, but i proceeded on)
I entered this command adb push su /system/xbin/su
and recieved a error
failed to copy 'su' to '/system/xbin/su': Read-only file system
At this point I did not know what to do I proceeded to reboot and then remount again.
Now I am stuck with just the notification bar responding and the settings not opening.
I am hoping anyone can help me also please PM me. I would appreciate any help with my situation.
If possible could someone g chat with me as typing and waiting for replies is taking to long.
Sorry if I come off as needy but the possiblity of losing the phone I recently bought is scaring me
sunny342 said:
Hello I have a HOX from att with the 1.85 software number.
I attempted to use this method to root my phone. http://forum.xda-developers.com/showthread.php?t=1709296
I proceeded with the instructions as followed and was sucessfully able to run these commands:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb reboot
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
adb shell ls -l /data/local.prop
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Now it's time to reboot
adb reboot
After phones reboots
adb remount
The command prompt indicated a successful remount. (At this point on the phone only the notification bar was working and nothing else was on the screen and right now that is where my phone is stuck, but i proceeded on)
I entered this command adb push su /system/xbin/su
and recieved a error
failed to copy 'su' to '/system/xbin/su': Read-only file system
At this point I did not know what to do I proceeded to reboot and then remount again.
Now I am stuck with just the notification bar responding and the settings not opening.
I am hoping anyone can help me also please PM me. I would appreciate any help with my situation.
If possible could someone g chat with me as typing and waiting for replies is taking to long.
Sorry if I come off as needy but the possiblity of losing the phone I recently bought is scaring me
Click to expand...
Click to collapse
I ended up just turning off the phone and then opening hboot and doing a factory reset. It got me back to stock so at least I can use my phone
sunny342 said:
I ended up just turning off the phone and then opening hboot and doing a factory reset. It got me back to stock so at least I can use my phone
Click to expand...
Click to collapse
When you try and mount your phone, since you factory reset through Hboot, you'll need to reformat your SD card because you corrupted it. Just some information for you.
Factory reset in bootloader, plug it in to comp, bring up "my computer" on your computer. Right click removable storage and choose "format"
Sent from my One X using Tapatalk 2