Ok I'm new to this so please be patient. I bought an Eris last month and got the update for 2.1 within a few hours. I go to perform the root instructions on theunlockr website. Everything goes fine until the last step. I get an error message after entering this step. Is there anything else I can do
adb shell flash_image recovery /sdcard/recovery-
ra-eris.img
-------------------------------------
Sent via the XDA Tapatalk App
Try remounting. Worked for me
I have been told that stock 2.1 couldn't be rooted but I wanted to try for myself. Do I run the commands with the phone in the just charged state or do I have it in disk drive mode? I just mean, at what point do I remount Thanks
-------------------------------------
Sent via the XDA Tapatalk App
Related
I have tenfars CWM recovery downloaded onto my phone but when ever i try to boot into recovery mod, nothing happens. When ever i run the app there is an orange loading circle in the middle of the screen. Not sure what to do but i need to get into recovery mode to flash gingerblur.
Are you plugged into AC?
Sent from my MB860 using XDA Premium App
You must plug into AC (usb wont do it)
Even when I plug into ac power nothing happens. The orange circle keeps spinning.
Sent from my MB860 using XDA App
You have to click install recovery THEN click recovery mode, with the AC charger plugged in. Just installing recovery won't work.
Sent from my Greyblurred Atrix
I did both of those and no response
Sent from my MB860 using XDA App
Try to root again. It sounds like what happened to me the first time I tried and had missed a step in the rooting process.
Sent from my MB860 using XDA App
lauterm said:
Try to root again. It sounds like what happened to me the first time I tried and had missed a step in the rooting process.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
What they said! Re-root.
Sent from WinBorg 4G using XDA Premium App
I rooted with superoneclick because I wasn't sure how to do it with gingerbreak because adb commands confuse me. Ill try to figure it out but if that doesn't work then im not sure what's wrong.
Sent from my MB860 using XDA App
I believe the recommended root methods are Gladroot or Gingerbreak. I seem to remember something about SuperOneClick being messy as it installs a second instance of busybox
The moderators should obliterate all mention of SuperOneClick. Seems like people still keep using it despite all the warnings not to...
Dimes on dollars says you aren't rooted. Superoneclick DOES install a second busybody and should avoided. If you are on 1.5.7, you cannot root with GladRoot until you sbf back to 1.2.6. You may, however, use Gingerbreak directly.
Well i couldn't unroot with superoneclick so I just rerooted with gingerbreak and then everything worked fine and I was successful in installing system recovery and gingerblur
Sent from my MB860 using XDA App
Hey
Im on the Lates 1.83 update and i had root before i updated so i still have root according to titanium backup
How do i enable sideloading? i tried glad root and superoneclick but they all get stuck at finding device or psneuter failed even though im on usb device setting 'none' and usb development mode
Try gingerbreak or afterupdate.bat from mr Riral
Sent from my GT-I9100 using XDA Premium App
nvm i was just being a moron and missed a important step
Can anyone help me find a site with stock roms for lg e739 or the lg mytouch 4g? I need it to flash my phone back to stock. Any help would be greatly appreciatied.
Tsk Tsk Tsk, on you for not backing up your stock.
You could always try the LG Mobile Support Tool
www[DOT]lg[DOT]com/us/support/mobile-devices/phone-support
I havent tried to use this method yet so I'm not 100% sure it puts you back to stock, as it came out of box.
Download and install LG mobile support tool, run LG Mobile Update. Click on Customer Support in the menu, then click recovery. Remember to have your e739 connected via usb.
I did make a backup. It just won't restore. Even tried removing the Android secure file from my backup and got a md5 sum mismatch. Downloaded someone else's backup and it shut my phone off before the restore was complete just like my backup before I removed the Android secure file. Now I'm stuck wit cm7.2. Should I flash cwm before I restore like I did when I installed cm7 the first time?
Sent from my LG-E739 using xda premium
You got the md5 error because you removed something from the nandroid...thus changing the ckecksum.
I would say try flashing that nandroid that you downloaded. Makin sure its named correctly. Without removing any files from it.
Also try to redownload that stock nandroid backup n try again. Btw which one was it?
Did you wipe cache system and data partitions before flashing nandroid?
Do not wipe sd card.thats where nandroid would be.
On my e739 during flashing nandroids Ive had it get stuck at lg logo once or twice. All I did then was use adb reboot-restore...then tried reboot from cwm again...if that didnt work then do adb again to get to recovery and flash nandroid again...dont give up. If you want stock keep trying.
You could flash ur cm again to get working on ur phone again but thats not what you want is it?
Sent from my LG-P999 using XDA
If you cant boot into an android you can use adb to push files to ur sd card...If you dont want to do that then ull have to flash cm n use file manager of choice.
Sent from my LG-P999 using XDA
I would offer my e739 stock backup...but i got it from a third party..and it has extra bloat and carrier iq on it. so im keeping it in a safe place.
Sent from my LG-P999 using XDA
Id trade you LOL... mine wont root
Sent from my LG-E739 using xda premium
I don't know how to get adb to work. I downloaded the sdk and jdk but don't know how to set the path. I wiped data, cache, dalvik, and battery stats before I tried to restore. Still running cm7 but upgraded to the RC. It's quite smooth. Scared to try another restore since each time it stops I get a bootloop and have to hard reset to get back into recovery. And Odin doesn't support my lg. :-( any other suggestions?
Sent from my LG-E739 using xda premium
If you lived close enough I would willingly trade. No lol. Real talk! But have you tried unlock root? Our worked like a charm on my e739.
Sent from my LG-E739 using xda premium
To get adb working put phone in debugging mode
applications>development>tick debugging mode
Connect via usb..start>run>cmd type: cd c:\androidSDK\platform-tools
press enter
you can now type adb commands
type: adb devices hit enter that will show you connected devices
to get into recovery type: adb reboot recovery
device should now reboot into recovery
Sent from my LG-P999 using XDA
Well still not able to get adb for ask to work but on a brighter note, I finally got my phone to restore to stock. Wiped everything 3x's factory/data reset, cache, and dalvik. Then I formatted my system,hit restore, and voila! It went back. Back to cm7.2 RC since TMobile now wants to charge extra to tether. Even tried ICS or cm9 but think I'm gonna wait till there is a more stable version
Sent from my LG-E739 using xda premium
well have you tryed one of many of the apps on the market to unroot it, but i cant help you with the restoring your backup if you cant restore it from cwm without problems because i have a galaxy s gt i9000
I already know how to unroot was having a prob restoring tmobiles software but its all good now!
Sent from my GT-P7510 using xda premium
I was just wiping my tablet to get it ready to turn in to best buy so they can exchange me for the Infinity, and I'm just doing my final data wipes of the tablet and I chose to wipe it from the settings menu. Since I'm rooted and have CWM Recovery, when I wiped, the tablet was probably looking for the stock recovery and won't boot back into the ROM anymore it just continually boots back into recovery. I followed the unbrick guide in the Dev section. But only issue is that. ADB won't recognize my prime. Also, I have nothing in my internal storage, so I can't flash a ROM...
Any advice?
Sent from my Nexus 7 using xda premium
speedygonzo said:
I was just wiping my tablet to get it ready to turn in to best buy so they can exchange me for the Infinity, and I'm just doing my final data wipes of the tablet and I chose to wipe it from the settings menu. Since I'm rooted and have CWM Recovery, when I wiped, the tablet was probably looking for the stock recovery and won't boot back into the ROM anymore it just continually boots back into recovery. I followed the unbrick guide in the Dev section. But only issue is that. ADB won't recognize my prime. Also, I have nothing in my internal storage, so I can't flash a ROM...
Any advice?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Try installing universal naked drivers on the PC and try ADB again.
Ok, I'll try that. Thanks for the reply!
Sent from my Nexus 7 using xda premium
I ran into the issue...took me 3 days to get my PC to recognize the prime....tried universal drivers, 3 different computers...and then one day it magically appeared
Sent from my ADR6425LVW using xda premium
Dang, well hopefully I can fix it before my mom leaves to Chicago on Friday. (I'm passing down my Prime to her since she got me the Nexus 7)
Thanks for the info though!
Sent from my Rooted Nexus 7 using xda premium
So i tried to work on my prime earlier today, and i drained my battery on purpose (it only had like 20% left)
And when I went to power it on after charging it for like 20 minutes, it does not turn on. The only feedback I get is the LED on the power button blinking 3 times.
Sent from my Rooted Nexus 7 using xda premium
I had the same thing happen to me. Once you get your drivers installed and adb recognizes it you'll be fine. Its literally a 5 minute fix. What recovery are you running btw?
Edit. Saw in op you're running CWM.
Sent from my SCH-I535 using xda premium
Now, when I do get the drivers installed and ADB does recognize my Prime, what commands do need to type? I'm assuming "adb push" and push a ROM? I'm not that great with ADB
Sent from my Rooted Nexus 7 using xda premium
Yea, the command is
Adb push directorywhereromislocated\rom.zip /sdcard/rom.zip
You may have to use /system/data if you get an error though
Also, i put the rom @ C:\ because for some reason, it wouldn't push from the adb folder, so my command looked like this
adb push C:\rom.zip /sdcard/rom.zip
Edit: If you're using windoze
Sent from my Transformer Prime TF201 using Tapatalk 2
speedygonzo said:
Now, when I do get the drivers installed and ADB does recognize my Prime, what commands do need to type? I'm assuming "adb push" and push a ROM? I'm not that great with ADB
Sent from my Rooted Nexus 7 using xda premium
Click to expand...
Click to collapse
Save yourself a lot of grief, put the rom in the same folder on the computer as your adb.exe is, this eliminates the need to put in the proper path. So then it is adb push [name of rom].zip /sdcard/
or
adb push [name of rom].zip /sdcard/media/
If this is the first time you are trying this, I would suggest trying to push a small text file first, this way you are not wait 5 minutes to find out it failed.
Note do not use the brackets, and for ease of use, right click the rom file, go to properties and copy the name of the file then right click and paste it in the command window, this way you won't mistype it.
Also proper use of the cmmand window is go to the folder where adb.exe is, press and hold the shift button then right click in the window and select open command propmt here.
I took the OTA from last week and rooted it. Yesterday, it seems I've lost root possibly. When I open Titanium Backup, I get the message "sorry, I could not acquire root priveleges...........this attempt was made using the " /system/xbin/su" command". So, what's going on?
ycats said:
I took the OTA from last week and rooted it. Yesterday, it seems I've lost root possibly. When I open Titanium Backup, I get the message "sorry, I could not acquire root priveleges...........this attempt was made using the " /system/xbin/su" command". So, what's going on?
Click to expand...
Click to collapse
Some programs that you install are not KK friendly, it has happened to me a couple times, did you do a backup, if so, flash it, if not, just Odin the root tar again.
Sent from my SM-N900P using Tapatalk
I believe I still have root (Adaway and Root Explorer apps still work), but all of a sudden, TB isn't working.
Well, I found a thread about adding a line to a particular .xml file for writing to sdcard........rebooted and TB is working fine.
Also sometimes this happens depending what recovery you are using when you wipe everything. You can boot into your recovery and hit reroot and usually this will fix it also.
That's good to know, thanks.
Sent from my SM-N900P using xda app-developers app