Been following the instructions to s-off with firewater but coming up with problems. First after reboot, after a little while on the phone it says "Root failed" however after sometime using root checker it says that I have root access. I get shell and su to work. But when I "/data/local/tmp/firewater" I don't get the term or condition screen on command prompt, it's just at "/[email protected]_m8wl:/ #"
Any ideas?
same here:
C:\>adb devices
List of devices attached
FA43ASFxxxxx device (edited for paranoia)
C:\>adb reboot
C:\>adb wait-for-device push firewater /data/local/tmp
895 KB/s (4519496 bytes in 4.929s)
C:\>adb shell
[email protected]_m8wl:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8wl:/ $ su
su
[email protected]_m8wl:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]_m8wl:/ #
Also my device goes offline after pushing firewater to the device. I uncheck and check debugging but device still shows offline. Eventually it finally goes back online but still can't get the terms to come up when trying to use Firewater.
I"m having the same issue. Checked my version numbers and they all match. Firewater does nothing, no terms, no confirmation, nothing.
Same problem
I've tried uninstalling weak sauce and supersu, used other superuser apps (but that's not the issue, I clearly have root), and tried switching the position of the "su" command when attempting to run firewater. The prompt for the script to say yes to just does not pop up. Brand new M8 today. Everything on the bootloader screen seems to match a few photos I've seen of other vzw phones which were granted s-off.
Maybe the last firewater script is bad? I don't know the last date of update for it.
Same Thing
Yep,
Having the exact same issue. Brand new M8 a few days ago. I'm no stranger to adb, have tried multiple computers, multiple factory resets, and every combination of commands.
Firewater won't even try to run... Any ideas?
Electro900k said:
Yep,
Having the exact same issue. Brand new M8 a few days ago. I'm no stranger to adb, have tried multiple computers, multiple factory resets, and every combination of commands.
Firewater won't even try to run... Any ideas?
Click to expand...
Click to collapse
I ended up having to go from my Mac to my Windows machine then it worked. That shouldn't matter, but it was also suggested to me to redownloaded the tool.
Fixed, don't use Chrome to download.
I just got it, gave up on Chrome and redownloaded from firewater site with (the dreaded) Internet Explorer. Replaced the file, script ran as it should.
titanshadow said:
I ended up having to go from my Mac to my Windows machine then it worked. That shouldn't matter, but it was also suggested to me to redownloaded the tool.
Click to expand...
Click to collapse
Did you follow the steps exactly as under the WeakSauce method?
adb reboot <--important!!!!
adb wait-for-device push firewater /data/local/tmp
adb shell
chmod 755 /data/local/tmp/firewater
su
/data/local/tmp/firewater
I'm tried using a VM (usually doesn't work anyway). ADB through my mac, now I'm using 7x64. Still no luck. Have replaced the firewater script twice just in case. I'm downloading the android sdk and reinstalling now trying to figure this out.
---------- Post added at 01:11 AM ---------- Previous post was at 01:07 AM ----------
Electro900k said:
I just got it, gave up on Chrome and re-downloaded from firewater site with (the dreaded) Internet Explorer. Replaced the file, script ran as it should.
Click to expand...
Click to collapse
Right when I posted my last, I saw that. Either it was a corrupted dl using Firefox on mac, or it was my SDK. Either way I followed the instructions verbatim in the order given, replaced the sdk and downloaded using IE. It's currently chugging. Hopefully this thread helps out others. Thank you!
That is unbelievable! Haha. Used IE instead of Chrome too and it worked.
I guess IE is good for ONE thing. Worked for me.
Verizon HTC One (M8)
It took me 5 tries to get Firewater to take.
Sent from my HTC6525LVW using Tapatalk
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?
Root for ZTE z990g aka ZTE Merit
by jcase - [email protected] - http://twitter.com/TeamAndIRC
June 16 2012 - Copyright 2012 CunningLogic
Do Not Distribute or republish without permission. (Sad that this is needed, but people/blogs like to profit off the work of others without credit)
Want to support my work? Donations are always appreciated, but never required:
Paypal: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=LZ62YFU3XCEK8
Amazon Giftcards: [email protected]
Required files:
http://dl.dropbox.com/u/8699733/chainsdd-su.zip
Unzip chaindsdd-su.zip and then get a shell with adb
Code:
adb shell
Set up the dirs, so shell owns them prior to logging. If shell does not own them then we can not control them. If the logs dir already exists, you may have to do a factory reset to remove them. They should not exist unless someone attempted this previously.
Code:
mkdir /data/local/logs
mkdir /data/local/logs/kernel
Open emode's logset activity. First button should be for enabling log set, enable it. Do not exit the activity, but if you do just repeat the below command.
Code:
am start -a android.intent.action.MAIN -n com.zte.emode/.logset
Confirm the log_kernel.txt file exists, if it does not wait a minute and check again.
Code:
ls -l /data/local/logs/kernel/log_kernel.txt
If it exists, delete it and immediately symlink it to /data/local.prop, logset may recreate it, if it does delete and try symlinking again.
Code:
rm /data/local/logs/kernel/log_kernel.txt
ln -s /data/local.prop /data/local/logs/kernel/log_kernel.txt
Now we want to wait for /data/local.prop to be created, it may take a minute or two. Keep checking until it exists.
Code:
ls -l /data/local.prop
Now once /data/local.prop exists, go back to the logset activity and disable logset. If you don't disable it, it will slowly eat away at all the disk space, and possibly overwrite the local.prop before you get root. Now lets set qemu=1 then reboot.
Code:
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
adb reboot
Once you have rebooted, remount, install su.
Code:
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
Clean up your mess!
Code:
adb shell rm /data/local.prop
adb shell rm -r /data/local/logs
Reboot, install the Superuser app from the market and enjoy
Code:
adb reboot
Might Not Work As Expected
I just tried this procedure from JCase at the RootzWiki dot com site with mixed results. The phone is a ZTE Merit Z990G from Straight Talk.
I went through all the steps and everything performed as expected. When I start start an app that requires superuser permissions, the app reports that the device has not been properly rooted. I have repeated the process as outlined four times, including downloading the SU file, and have the same results. Titanium Plus, Busy Box Pro and Root Check Basic report that the device is not rooted.
However, a couple of the Google apps - music, movies and reader seem to think the phone is rooted. Any ideas or suggestions will be very appreciated.
bitshifter52 said:
I just tried this procedure from JCase at the RootzWiki dot com site with mixed results. The phone is a ZTE Merit Z990G from Straight Talk.
I went through all the steps and everything performed as expected. When I start start an app that requires superuser permissions, the app reports that the device has not been properly rooted. I have repeated the process as outlined four times, including downloading the SU file, and have the same results. Titanium Plus, Busy Box Pro and Root Check Basic report that the device is not rooted.
However, a couple of the Google apps - music, movies and reader seem to think the phone is rooted. Any ideas or suggestions will be very appreciated.
Click to expand...
Click to collapse
Sounds like band permissions on su, try
adb shell ls -l /system/xbin/su
if the permissions come out as "-rwsr-sr-x" then you are rooted, try updating su with the suepruser app, or finding a different copy of su.
If the permissions are different or it says it doesnt exist, then you need to repeat the instructions as you missed one or two
jcase said:
Sounds like band permissions on su, try
adb shell ls -l /system/xbin/su
if the permissions come out as "-rwsr-sr-x" then you are rooted, try updating su with the suepruser app, or finding a different copy of su.
If the permissions are different or it says it doesnt exist, then you need to repeat the instructions as you missed one or two
Click to expand...
Click to collapse
Thank you for the fast response. Here are the permissions for the SU file and based on what you are saying they look good:
C:\SDK>adb shell ls -l /system/xbin/su
-rwsr-sr-x root root 22364 2012-06-17 12:47 su
I have located and downloaded a couple of "su" files from XDA and similar sites and the files are identical. I will continue searching for a different "su" file and see if that makes a difference.
---------- Post added at 06:15 PM ---------- Previous post was at 05:43 PM ----------
bitshifter52 said:
Thank you for the fast response. Here are the permissions for the SU file and based on what you are saying they look good:
C:\SDK>adb shell ls -l /system/xbin/su
-rwsr-sr-x root root 22364 2012-06-17 12:47 su
I have located and downloaded a couple of "su" files from XDA and similar sites and the files are identical. I will continue searching for a different "su" file and see if that makes a difference.
Click to expand...
Click to collapse
I looked around and did not find any "su" files that were different than what I downloaded according to the root process. Just for grins I copied the "su" file from my Noot Tablet which is rooted and tried that file. Sadly, it did not make a difference.
Please let me know if there is any other information I can provide or if you would like me to try something else.
What happens when you open the Superuser app (note this is not supersu) and go to settings/options and attempt to update su?
bitshifter52 said:
Thank you for the fast response. Here are the permissions for the SU file and based on what you are saying they look good:
C:\SDK>adb shell ls -l /system/xbin/su
-rwsr-sr-x root root 22364 2012-06-17 12:47 su
I have located and downloaded a couple of "su" files from XDA and similar sites and the files are identical. I will continue searching for a different "su" file and see if that makes a difference.
---------- Post added at 06:15 PM ---------- Previous post was at 05:43 PM ----------
I looked around and did not find any "su" files that were different than what I downloaded according to the root process. Just for grins I copied the "su" file from my Noot Tablet which is rooted and tried that file. Sadly, it did not make a difference.
Please let me know if there is any other information I can provide or if you would like me to try something else.
Click to expand...
Click to collapse
It Worked - But Don't Know Why...
jcase said:
What happens when you open the Superuser app (note this is not supersu) and go to settings/options and attempt to update su?
Click to expand...
Click to collapse
I re-installed Superuser and Superuser Elite and now the phone says it's rooted. I've been in IT for over 35 years and it makes me nervous when software "magically" fixes itself. But now that it's working I won't question it and proceed from here. I appreciate your help and your effort.
Cheers
bitshifter52 said:
I re-installed Superuser and Superuser Elite and now the phone says it's rooted. I've been in IT for over 35 years and it makes me nervous when software "magically" fixes itself. But now that it's working I won't question it and proceed from here. I appreciate your help and your effort.
Cheers
Click to expand...
Click to collapse
Generally you have to run superuser once to get it to work I've found, at least recent builds (or maybe its recent android builds)
Problem.
Hello, i have followed this entirely but at parts it says "Access denied" when im on certain parts when i tryed to check if the Kernel log was there it said "access denied" same with some folders.
root or no root
followed steps, ended up with this...
$ ls -l /system/xbin/su
ls -l /system/xbin/su
-rw-rw-rw- root root 22364 2012-07-15 09:25 su
the superuser app shows all blank under apps and logs, when i try to update it, it says "checking" for a few secs and then nothing... also wondering how to do a factory reset cuz if i didn't screw the phone up yet, i will thx in advance
Has you can see I'm new here. I'm old and retired I would love to root my ZTE Merit 2.3.5 but this is over my head.
I was wondering if there's any accomplished phone rooters in the NC area that would be willing to walk me through this or do this for me
I'd be more than willing to make a donation to make this happen,
custom recovery
I was wondering if someone would make q custom recovery for this phone because the stock recovery is really bad
Not working
I can't even get past step 2, I have the file installed and unzipped on both my computer and my smart phone. The only thing I can find to put in the codes is command prompt which says "error: device not found" when I type in adb shell. My ZTE Merit phone has very low internal memory due to all the retarded system apps that came on the phone, I would very much like some assistance removing them from my phone. I also downloaded superuser elite onto my phone and it doesn't show up with ANYTHING. The first page says
superuse v3.1.3(46)
tap to display changelog
elite installed
su binary not found
a check in the box "outdated binary notification
unchecked box, temp unroot (When tapped it does nothing)
unchecked box ota survival (Again when tapped it does nothing)
I scroll over to the apps section of the program and it says "No apps in list"
What am I doing wrong? This lack of space is quite irritating
Worked!
omg I've wanted to root my phone. Thank you thank you! I thought I would brick my phone at first.
SIM Carrier unlock a ZTE Merit Z990G Straight Talk
I'm currently a T mobile prepaid customer and received the Merit from a friend of mine for doing some painting. I have looked for a month now and had a few unlock websites fail at attempting to unlock the phone via the IMEI (which the phone does have ). I have attempted to put my tmobile sim in the Merit but there is NO place to enter an unlock code. I really DONT wanna change my service to straight talk and would be willing to pay a decent amount to anyone that is capable of unlocking this phone for use with tmobile. If you think you have what it takes PM me and i will give you the IMEI and we can work out a deal. I challenge ANYONE achieve the impossible and get me the unlock code and a way to input it into the phone.
Cannot get local.prop
I have waited 20 minutes after trying to create the local.prop file and it simply won't create it. Any suggestions?
Can't get SU to upload
Hey I'm new to rooting android. I get to the point of installing SU but windows keeps telling me file not found. Would really like some help in fixing this issue. I have installed SU file to C:\Android\android-sdk\SU. Up to this point everything works fine.
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
Any help would be really appreciated.
Thnks
Help getting Started
Hey Anyone and everyone that may be online, I have a real quick and probably REALLY EASY question for ya... I'm trying to get started Rooting my ZTE Merit and I need to find out how to get to or where to find the screen where I type in the commands. I already downloaded the chainsdd zip file. So now I'm supposed to get shell with adb. If someone would be so kind and put me in the right general direction, I sure would
be grateful.
Thanks in advance,
Jason
Not a Damn thing...
Rather sad....I have everything going as it should....all input correct...still no root after final reboot...I followed every step to a T several times -rw-rw-rw- grrr...ive rooted many devices none this big of a pain in tha butt!
Used updated su binary on root just for fun...same result
Help plz!
im a noob to this but have been messing around with ubuntu for some time now can someone show me step by step on how to root my zte merit plz? is there a video tut on how? i tried all the quick methods but they don't work, this one obviously does on this page, can someone help start me out plz, im learning still and love to learn more!
---------- Post added at 08:59 AM ---------- Previous post was at 08:45 AM ----------
Univarseman said:
I can't even get past step 2, I have the file installed and unzipped on both my computer and my smart phone. The only thing I can find to put in the codes is command prompt which says "error: device not found" when I type in adb shell. My ZTE Merit phone has very low internal memory due to all the retarded system apps that came on the phone, I would very much like some assistance removing them from my phone. I also downloaded superuser elite onto my phone and it doesn't show up with ANYTHING. The first page says
superuse v3.1.3(46)
tap to display changelog
elite installed
su binary not found
a check in the box "outdated binary notification
unchecked box, temp unroot (When tapped it does nothing)
unchecked box ota survival (Again when tapped it does nothing)
I scroll over to the apps section of the program and it says "No apps in list"
What am I doing wrong? This lack of space is quite irritating
Click to expand...
Click to collapse
help me, whats the first step then i can get the gearz in motion, i have not a clue on how to start this but if i do i can usually figure it out from them sometimes
Start menu
jjflappy said:
Hey Anyone and everyone that may be online, I have a real quick and probably REALLY EASY question for ya... I'm trying to get started Rooting my ZTE Merit and I need to find out how to get to or where to find the screen where I type in the commands. I already downloaded the chainsdd zip file. So now I'm supposed to get shell with adb. If someone would be so kind and put me in the right general direction, I sure would
be grateful.
Thanks in advance,
Jason
Click to expand...
Click to collapse
Start menu then type CMD hit enter
Hey guys. I just got my HOX and have been trying to root it. The software update keeps popping up and I keep refusing, so no worries there. I've got 1.85 right now and have been attempting the methods found here and here, but they just aren't working. I'd prefer to use the manual method. Someone willing to help a guy get started with all this would be the greatest person ever, just saying!
blinkbomber said:
Hey guys. I just got my HOX and have been trying to root it. The software update keeps popping up and I keep refusing, so no worries there. I've got 1.85 right now and have been attempting the methods found here and here, but they just aren't working. I'd prefer to use the manual method. Someone willing to help a guy get started with all this would be the greatest person ever, just saying!
Click to expand...
Click to collapse
check pm
beaups said:
check pm
Click to expand...
Click to collapse
Could you help me too X( ? I got my HOX last night at 8pm; I traded my rooted S2 Skyrocket for it.
Been looking for the past day through forums and google. It's so different from Samsung's phones, but a nice change indeed.
I'm on 1.85 and tried those two methods also. I'm not very familiar with ADB. From reading all night and this morning, I believe I root, unlock bootloader, flash recovery, flash custom roms?
smartnphone said:
Could you help me too X( ? I got my HOX last night at 8pm; I traded my rooted S2 Skyrocket for it.
Been looking for the past day through forums and google. It's so different from Samsung's phones, but a nice change indeed.
I'm on 1.85 and tried those two methods also. I'm not very familiar with ADB. From reading all night and this morning, I believe I root, unlock bootloader, flash recovery, flash custom roms?
Click to expand...
Click to collapse
Follow the instructions in this link http://forum.xda-developers.com/showthread.php?p=30741993
Sent from my HTC One X using xda premium
abhipati said:
Follow the instructions in this link http://forum.xda-developers.com/showthread.php?p=30741993
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks. I used this for ADB http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
I remember using it for my S2, but I don't quite understand the directions for the http://forum.xda-developers.com/showthread.php?t=1709296 method. Could you dumb it down for this HOX noob?
smartnphone said:
Thanks. I used this for ADB http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
I remember using it for my S2, but I don't quite understand the directions for the http://forum.xda-developers.com/showthread.php?t=1709296 method. Could you dumb it down for this HOX noob?
Click to expand...
Click to collapse
I'll try to help! all of the following is my interpretation of the rooting method described here: http://forum.xda-developers.com/showthread.php?t=1709296
What you need:
HOX on ATT 1.85
su binary from http://dl.dropbox.com/u/don'tusemeimabadsubinary
EDIT: The su binary above has issues. Use this one instead: http://dl.dropbox.com/u/9060692/su
Make sure HTC sync is NOT RUNNING (down in system tray)
Make sure phone is set to "charge only" and usb debugging is enabled!
Download correct su file (assuming you don't have a problem with this step )
Put su in same directory as ADB. Get to adb command prompt and cd into that directory
Quote from Butters619: cd means change directory. It is a windows command prompt command. So you would type "cd C:\adb" if that was where your adb folder was. Folder and directory can be used interchangeably, although directory is more "correct". We only say folder because GUIs use folders to represent directories.
NEW - pull sim card
NEW - do factory reset
NEW - when reset is complete, do not replace sim, do NOT connect to wifi. Go through setup, go to settings, enable USB debugging. When that's done:
Enter these commands in adb:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
(If you get file doesn't exist after the FIRST command don't worry - they may not be there)
Now, on the phone, go to settings and check for software update. It will tell you you need to connect to network. Now, replace the SIM OR connect to wifi. Have it check for software update again. When it's done, do NOT click "yes" or "ok" on the phone. Simply:
Enter these commands in adb:
adb shell ls -l /data/local.prop
IF AND ONLY IF you get "file not exists" or anything like that then set your phone's date 2 days ahead and reboot the phone and start over. If you get file info, you're golden. Proceed...
Enter these commands into adb:
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Reboot via adb by entering this command: adb reboot
After phones reboots
Enter these commands in adb:
adb remount
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
You should be rooted.
A cool username said:
I'll try to help! all of the following is my interpretation of the rooting method described here: http://forum.xda-developers.com/showthread.php?t=1709296
What you need:
HOX on ATT 1.85
su binary from http://dl.dropbox.com/u/don'tusemeimabadsubinary
EDIT: The su binary above has issues. Use this one instead: http://dl.dropbox.com/u/9060692/su
Make sure HTC sync is NOT RUNNING (down in system tray)
Make sure phone is set to "charge only" and usb debugging is enabled!
Download correct su file (assuming you don't have a problem with this step )
Put su in same directory as ADB. Get to adb command prompt and cd into that directory
Quote from Butters619: cd means change directory. It is a windows command prompt command. So you would type "cd C:\adb" if that was where your adb folder was. Folder and directory can be used interchangeably, although directory is more "correct". We only say folder because GUIs use folders to represent directories.
NEW - pull sim card
NEW - do factory reset
NEW - when reset is complete, do not replace sim, do NOT connect to wifi. Go through setup, go to settings, enable USB debugging. When that's done:
Enter these commands in adb:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
(If you get file doesn't exist after the FIRST command don't worry - they may not be there)
Now, on the phone, go to settings and check for software update. It will tell you you need to connect to network. Now, replace the SIM OR connect to wifi. Have it check for software update again. When it's done, do NOT click "yes" or "ok" on the phone. Simply:
Enter these commands in adb:
adb shell ls -l /data/local.prop
IF AND ONLY IF you get "file not exists" or anything like that then set your phone's date 2 days ahead and reboot the phone and start over. If you get file info, you're golden. Proceed...
Enter these commands into adb:
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Reboot via adb by entering this command: adb reboot
After phones reboots
Enter these commands in adb:
adb remount
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
You should be rooted.
Click to expand...
Click to collapse
Thanks. Yeah i've been trying it alld ay but it can't find where my SU is. it's in the same location as the ADB stuff i believe C:\android-sdk-windows. Seem like some of the senior members are willing to go through teamviewer to help the ones who can't do it. I'll try asking them :/
Sorry I couldn't be of any help, but please let me know if/how you get this to work just in case this happens to me when I get my one x.
Sent from my Touch Pro 2 using xda app-developers app
---------- Post added at 08:22 PM ---------- Previous post was at 08:18 PM ----------
blinkbomber said:
Hey guys. I just got my HOX and have been trying to root it. The software update keeps popping up and I keep refusing, so no worries there. I've got 1.85 right now and have been attempting the methods found here and here, but they just aren't working. I'd prefer to use the manual method. Someone willing to help a guy get started with all this would be the greatest person ever, just saying!
Click to expand...
Click to collapse
I wonder if the one who actually started this thread got his/her phone to work...???
Sent from my Touch Pro 2 using xda app-developers app
Someone think they can help me root the phone? I'm on 1.85 and I believe I finally got adb to recognize my device but after that I don't think I'm doing it right
Sent from my SGH-I777 using XDA Premium App
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.
I'll try and be as specific as possible as I hate having to resort to new threads when so many are out there, but I'm really at a loss.
Factory new phone (Verizon m8) or as close too it as possible.
Have tried multiple times installing Weaksauce and SU with the binaries but the binaries never install. Always fail and ask for reboot. The root is activated upon reboot after a minute or so. Rootchecker says root is activated and I have granted permission for a number of apps (Root Checker, Root Explorer, adb shell). I have uninstalled and reinstalled via the instructions and always the same issue of the binaries not installed.
Since the root was activated I have attempted to install firewater anyway.
I was unable to get the push command to work so instead I moved the firewater file into the /data/local/tmp manually with Root Explorer.
I attempt the firewater installation however get the following error when I input the chmod 755 command:
adb shell
[email protected]_m8wl:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
Unable to chmod /data/local/tmp/firewater: Operation not permitted
I have given SU privileges to the adb shell and accepted the prompt on my phone. Upon running the last command in the firewater instructions it executes, chugs, but then states the "whelp, firewater doesn't work on your device, yadadada".
I notice when I do the adb reboot command and the phone reboots the "HTC MTP Device" driver always fails when coming back from an adb reboot. I have installed the HTC Sync for the drivers and removed the Sync program. Could this be a driver issue? Or something else? I'm not sure why the chmod 755 command is not permitted? Is that potentially the issue as well?
I can wipe the phone to new if needed. Any assistance would be appreciated.
going through the same exact thing. I have a fresh verizon device and i checked to make sure everything matched up. and they do. Firmware, HBOOT, RADIO, everything.
I get to chugging and then bam..sorry this wont work on your phone etc. Whats also funny is this phone has a brighter clearer display and has a weird serial id. seomthing like FFA something when my original is HT something. Ive also factory reset 12 times.
Sounds like your phones have the newer boot loader. If that's the case you'll have to use the new root by jcase called sunshine or something like that. It'll cost you though. He started charging $25 for it.
Shadow Death said:
Sounds like your phones have the newer boot loader. If that's the case you'll have to use the new root by jcase called sunshine or something like that. It'll cost you though. He started charging $25 for it.
Click to expand...
Click to collapse
adb reboot bootloader yields the following:
HBoot-3.16.0.0000
Radio-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
Apr 1 2014,00:26:53.0
I'll take a look at this sunshine. Thanks for pointing me in the right direction. Any further info from anyone else would be appreciated
jtbndy said:
adb reboot bootloader yields the following:
HBoot-3.16.0.0000
Radio-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
Apr 1 2014,00:26:53.0
I'll take a look at this sunshine. Thanks for pointing me in the right direction. Any further info from anyone else would be appreciated
Click to expand...
Click to collapse
My phone yields the identical information.. Rooted soff'd and all custom romd up time and time again.
Shadow Death said:
Sounds like your phones have the newer boot loader. If that's the case you'll have to use the new root by jcase called sunshine or something like that. It'll cost you though. He started charging $25 for it.
Click to expand...
Click to collapse
"Sounds like your phones have the newer boot loader" Are you saying Firewater was patched on the newer M8's with updated ones?
S1L3nTShaDoWz said:
"Sounds like your phones have the newer boot loader" Are you saying Firewater was patched on the newer M8's with updated ones?
Click to expand...
Click to collapse
I just exchanged phones with HTC and was still able to use Firewater
Sent from my HTC6525LVW using XDA Premium HD app
jtbndy said:
I'll try and be as specific as possible as I hate having to resort to new threads when so many are out there, but I'm really at a loss.
Factory new phone (Verizon m8) or as close too it as possible.
Have tried multiple times installing Weaksauce and SU with the binaries but the binaries never install. Always fail and ask for reboot. The root is activated upon reboot after a minute or so. Rootchecker says root is activated and I have granted permission for a number of apps (Root Checker, Root Explorer, adb shell). I have uninstalled and reinstalled via the instructions and always the same issue of the binaries not installed.
Since the root was activated I have attempted to install firewater anyway.
I was unable to get the push command to work so instead I moved the firewater file into the /data/local/tmp manually with Root Explorer.
I attempt the firewater installation however get the following error when I input the chmod 755 command:
adb shell
[email protected]_m8wl:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
Unable to chmod /data/local/tmp/firewater: Operation not permitted
I have given SU privileges to the adb shell and accepted the prompt on my phone. Upon running the last command in the firewater instructions it executes, chugs, but then states the "whelp, firewater doesn't work on your device, yadadada".
I notice when I do the adb reboot command and the phone reboots the "HTC MTP Device" driver always fails when coming back from an adb reboot. I have installed the HTC Sync for the drivers and removed the Sync program. Could this be a driver issue? Or something else? I'm not sure why the chmod 755 command is not permitted? Is that potentially the issue as well?
I can wipe the phone to new if needed. Any assistance would be appreciated.
Click to expand...
Click to collapse
Did you follow the instructions here to the letter? http://firewater-soff.com/instructions/
If you could not push firewater to your device, it would indicate that weaksauce root is not working - or you did not wait long enough for it to re-root after the adb reboot. Or you did not catch the root request for an adb shell on your phone because the screen was off....
Make sure you use the second instructions, the Weaksauce method, not the root or temp root method.
berndblb said:
Did you follow the instructions here to the letter?
If you could not push firewater to your device, it would indicate that weaksauce root is not working - or you did not wait long enough for it to re-root after the adb reboot. Or you did not catch the root request for an adb shell on your phone because the screen was off....
Make sure you use the second instructions, the Weaksauce method, not the root or temp root method.
Click to expand...
Click to collapse
The only process I could not complete during the weaksauce root was installing the binaries with SU. It fails every time. I've uninstalled via the weaksauce instructions many times adb rebooted, and still the binaries will never install. Since I can move files around with Root Explorer is there any way to manually install the binaries?
If the root did not take, why does Root Checker say that I have root access a few minutes after reboot? I'm also able to grant SU permissions when asked for it (and approved the SU permission for Root Checker and adb shell).
Seems to me the issue lies with whatever the chmod command does and why that's not permitted or that the MTP drivers fail to install upon reboot.
jtbndy said:
The only process I could not complete during the weaksauce root was installing the binaries with SU. It fails every time. I've uninstalled via the weaksauce instructions many times adb rebooted, and still the binaries will never install. Since I can move files around with Root Explorer is there any way to manually install the binaries?
If the root did not take, why does Root Checker say that I have root access a few minutes after reboot? I'm also able to grant SU permissions when asked for it (and approved the SU permission for Root Checker and adb shell).
Seems to me the issue lies with whatever the chmod command does and why that's not permitted or that the MTP drivers fail to install upon reboot.
Click to expand...
Click to collapse
you can't update binaries till your s-off. Just use weaksauce an download SuperSU from play store don't even open. Then run firewater commands to get s-off then uninstall weaksauce an SuperSU flash twrp an then flash SuperSU for root an you all set.
sent from my red HTC M8 using the free XDA app cause the paid one keeps f/c non stop?
Tigerstown said:
you can't update binaries till your s-off. Just use weaksauce an download SuperSU from play store don't even open. Then run firewater commands to get s-off then uninstall weaksauce an SuperSU flash twrp an then flash SuperSU for root an you all set.
sent from my red HTC M8 using the free XDA app cause the paid one keeps f/c non stop?
Click to expand...
Click to collapse
Without opening SuperSU I still get the same errors (HTC MTP Device Driver fail on adb reboot and the same error for chmod 755 command) as I did before including the firewater whelp message.
jtbndy said:
Without opening SuperSU I still get the same errors (HTC MTP Device Driver fail on adb reboot and the same error for chmod 755 command) as I did before including the firewater whelp message.
Click to expand...
Click to collapse
Fastboot turned off?
Sent from my HTC6525LVW using XDA Premium HD app
Fastboot has been off every attempt.
jtbndy said:
Fastboot has been off every attempt.
Click to expand...
Click to collapse
backup your phone and then do a factory reset then do the process all over again? This might be the way to go. ONce you are back up, install weaksauce then supersu from play store. then go ahead and try the firewater. If no go, then try sunshine but I know its $25 but its easier to use than using firewater.
Can I chime in and ask if this should be done on ART or Dalvik? Or if that even matters
EKnofsky said:
Can I chime in and ask if this should be done on ART or Dalvik? Or if that even matters?
Click to expand...
Click to collapse
Both times I have done it has been on dalvik. Hope that helps.
Sent from my HTC6525LVW using XDA Premium HD app
lucky_strike33 said:
Both times I have done it has been on dalvik. Hope that helps.
Sent from my HTC6525LVW using XDA Premium HD app
Click to expand...
Click to collapse
Thank you very much, I am switching over to Dalvik to test and see if anything works for me.
I have the same bootloader version as was mentioned earlier
HBoot-3.16.0.0000
Radio-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
Apr 1 2014,00:26:53.0
I will report back if firewater works or if SunShine does.
EKnofsky said:
Thank you very much, I am switching over to Dalvik to test and see if anything works for me.
I have the same bootloader version as was mentioned earlier
HBoot-3.16.0.0000
Radio-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
Apr 1 2014,00:26:53.0
I will report back if firewater works or if SunShine does.
Click to expand...
Click to collapse
Try Firewater first since its free. Good luck.
Sent from my HTC6525LVW using XDA Premium HD app
lucky_strike33 said:
Try Firewater first since its free. Good luck.
Sent from my HTC6525LVW using XDA Premium HD app
Click to expand...
Click to collapse
I ran the SunShine app from http://theroot.ninja/ and it allowed me to S-OFF. At what point was I supposed to pay?
EKnofsky said:
I ran the SunShine app from http://theroot.ninja/ and it allowed me to S-OFF. At what point was I supposed to pay?
Click to expand...
Click to collapse
After it says your phone can be s off and unlocked. Then takes you to PayPal to pay
Sent from my HTC6525LVW using XDA Premium HD app