Does anybody know how I can flash a custom recovery to this device? I have already gotten it rooted with the method for the Optimus. However any attempt to flash a recovery sets it back to default, it retains root, after the reset, but will not allow for a custom recovery. I know this isn't an awesome phone and I have a D1 that I use, but have been given this as a work phone and would love the same freedom with this device.
bump! I've had the phone for a month now, and am looking to try some custom roms now. doesn't appear as though cyanogen or clockworkmod support the lg, or do they?? It looks like the first stumbling block is the recovery image. Anybody know a way to backup the ROM on this phone??
what did you do to get you LG VORTEX rooted? i have tried several different ways to no avail. also my phone updated to android 2.2.1 is there any way to roll it back to 2.2 so that rooting may be easier?
mike9064 said:
what did you do to get you LG VORTEX rooted? i have tried several different ways to no avail. also my phone updated to android 2.2.1 is there any way to roll it back to 2.2 so that rooting may be easier?
Click to expand...
Click to collapse
Rooting hasn't really happened for 2.2.1 on the LG Vortex. You have to roll back to 2.2 to root (use the z4root, search the forums on how to use it). To roll back, check out the downgrading tutorial on breakneckmod dot co dot cc (I can't post links yet, but I feel like this one is necessary and doesn't constitute spam). If that seems a little hard to follow, or if you don't feel as advanced a user, there's an updated, more step-by-step, hold-your-hand kinda thing (which will take longer if you already know what you're doing), check the latest post on technoheads dot org.
You don't need to roll back to 2.2 to root this phone. I rooted it with no problems using Super One Click with rageagainstthecage. You may need to turn the usb debug mode on and off a couple times to get it to take during the process. After you see the message that you have succeeded you need to reboot your phone. Then you're good to go.
I just rooted with the latest update.
Unzip the SuperOneClick archive
Put the phone in debug mode (I had it in modem mode and enabled debugging)
using adb push psneuter to /data/local/tmp
then do
Code:
adb shell
cd /data/local/tmp
chmod 0777 ./psneuter
./psneuter
adb shell
id
if the last command says uid=0(root) then you are temp rooted
close out of the shell and do
Code:
adb remount
adb push su-v3 /system/bin
adb push Superuser.apk /system/app
adb shell sync
And you are rooted
Looking for a rom for the lg vortex
i need a stock ROM that i can use ROM Manager to install that will let me use the wifi hotspot i have it rooted
I used ARoot
Just rooted my Vortex running 2.2.2bFRG83G, using SOC. Apparently LG made it easy with their modem drivers available on their website. The only "trick" that i did (and was not documented in rooting procedures) is to enable modem mode in the USB connection chooser menu (with USB debugging of course).
I rooted my LG Vortex using Gingerbreak, but I had issues flashing the recovery. However, I did it using ADB and it worked wonders for me. I even have a custom ROM on the device now. I tried CM7 on it, but I kept getting random force closes, especially when going into the settings to try to change some things. I did find another one (Lightning) and it seems to be pretty stable right now.
seejay1120 said:
Just rooted my Vortex running 2.2.2bFRG83G, using SOC. Apparently LG made it easy with their modem drivers available on their website. The only "trick" that i did (and was not documented in rooting procedures) is to enable modem mode in the USB connection chooser menu (with USB debugging of course).
Click to expand...
Click to collapse
Thank you Thank you Thank you! I have been pulling my hair out trying to get this to work, and that was all that was needed!
i rooted my vortex
i rooted my vortex but thats about as far as i got.
is there any way to do this that works?
LG Vortex root
I root my phone using SuperOneClick and then using something else (I forgot) to automatically install SU. I did have problems to start with using ADB but by reading and RE-reading the forums, I learned how to use it correctly. I then started deleting unwanted apps using this thread (http://forum.xda-developers.com/showthread.php?t=617026). Now some of you may have noticed that I didn't say anything about doing a backup.... that's because in my hurry to kill those few apps, I didn't do a backup. Well, now I want to start over from scratch because my home screen freezes and force-closes way too often. Where can I get a backup from?
tia...
Winston
check out the GNM recovery on android forums
Related
I take absolutely no credit for anything in here. I am simply re-posting the guide developed by Paul O'Brien at Modaco since I figured it will be a valuable resource for new and old members alike. Without further ado, I give you Paul's Streak Rooting Guide:
Introducing.... Superboot!
Superboot is a boot.img that when flashed, will root your device the first time you boot (installing su and the superuser APK by ChainsDD). No need to flash the system partition, no need to use ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just flash the boot image using the instructions below and you're done!
The story behind this superboot is a little bit different to what has gone before... normally a Superboot is created based on a leaked ROM, but this wasn't possible on the Streak. What happened in this case is that I managed to find an exploit to give me root, which in turn allowed me to dump the device to images and create a Superboot image. This can be flashed because the Streak has a relatively open bootloader. This is pretty handy because it means that I don't have to reveal the root exploit... potentially saving it for further down the line if Dell choose to lock down the device a bit more.
APPLY THIS AT YOUR OWN RISK!
Before download, you should check your device 'about' screen to determine which build number you are running. Although the Superboot may work on other builds than that for which it was designed, I cannot guarantee that!
Superboot (tested on build 3883) - DOWNLOAD (MediaFire Pro) / MIRROR (ROMraid / CoBlitz) - MD5: 110e69808dc5145d1d0fca80f0d9ecb5
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Unplug the device from your PC, remove the device battery, then replace it and turn device on with the camera button pressed. Select the 'fastboot' text on the top right, wait around 10 seconds then plug the device into your PC. The screen display should change to 'FASTBOOT MODE'. If it doesn't, repeat and retry (it's a bit temperamental!)
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
Note: Be careful what you do now you have root! We don't as yet have a recovery image or recovery flash (but will soon), so if you badly break it, you might have to wait for a bit.
That's it, job done! Enjoy!
P
PS Although the Superboot image is 'insecure', the Streak seems to be blocking 'adb remount'. I am looking into this now, but in the interim you can remount system by using 'adb shell, 'su' then 'mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system'.
Click to expand...
Click to collapse
Cheers for the post bra!
Fantastic
Glad this root was nothing like the X10, Paul got it within a day I think.
Looking forward to flashing new ROMs!
Can some one in laymans terms explain what root is. Is it like HARDSPL on a Windows mobile device i need to know a bit more and why i would need it
thanks new to android
lufc said:
Can some one in laymans terms explain what root is. Is it like HARDSPL on a Windows mobile device i need to know a bit more and why i would need it
thanks new to android
Click to expand...
Click to collapse
no..
you need to get your head around how linux works really to understand this.
there's various degrees of permission granted to "users" to do various things (such as access parts of the operating system or file system)
Root is the boss, or "superuser" and has access to all these.
most devices don't come "rooted" because of a)potential security breaches b)you can mess up the device if you start mucking about too much
this is from the first g1 so is a bit old now, but the theory is relevant
http://android-dls.com/wiki/index.php?title=Why_Root
fards said:
no..
you need to get your head around how linux works really to understand this.
there's various degrees of permission granted to "users" to do various things (such as access parts of the operating system or file system)
Root is the boss, or "superuser" and has access to all these.
most devices don't come "rooted" because of a)potential security breaches b)you can mess up the device if you start mucking about too much
this is from the first g1 so is a bit old now, but the theory is relevant
http://android-dls.com/wiki/index.php?title=Why_Root
Click to expand...
Click to collapse
Thanks for that now its starting to make sense
edit. sorted
I must do root for my streak.because i ned to use barnacle.i wait next update to froyo or i go to root?
SuperBoot - SuperQuick
This is an awesome root method, by far the fastest root i have done on any of my devices. I think the most difficult was trying to root my Magic [with perfect SPL on 1.6] which took me around 6 weeks of trying. This method took around fifteen minutes to make sure I had the correct drivers then 'click' and youre rooted.
Looks like this still isnt in the states yet so rom production will be slow to start with.
But hey - ROOT!!
If i root the dell streak will i loose OTA updates?
RiNo808 said:
If i root the dell streak will i loose OTA updates?
Click to expand...
Click to collapse
Hmmm, thats a good question. There is an option to check for updates in the 'about' section of the settings and it seems to work still. Working as in its telling me my device us still running dated firmware.
Sent from my Dell Streak using XDA App
RiNo808 said:
If i root the dell streak will i loose OTA updates?
Click to expand...
Click to collapse
If this is the same as the Nexus One... if you have a modified recovery then you wont be able to install the OTA update.
cue_32 said:
If this is the same as the Nexus One... if you have a modified recovery then you wont be able to install the OTA update.
Click to expand...
Click to collapse
So when we hear that an OTA update is coming we need to go back to stock recovery? Or stock recovery and stock [unrooted] ROM?
Confirming Dell Streak US [AT&T] Works!!!
Guys,
Just wanted everyone to know that I have successfully rooted my AT&T Dell Streak [US] using the method posted at the begining of the thread. However, I used the r2-4399-streak-superboot.zip found here: http://android.modaco.com/content/d...-4399-how-to-root-your-dell-streak-superboot/
Now all I need to do is figure out how to get 2.1 working on my Streak
mistadman said:
Guys,
Just wanted everyone to know that I have successfully rooted my AT&T Dell Streak [US] using the method posted at the begining of the thread. However, I used the r2-4399-streak-superboot.zip found here: http://android.modaco.com/content/d...-4399-how-to-root-your-dell-streak-superboot/
Now all I need to do is figure out how to get 2.1 working on my Streak
Click to expand...
Click to collapse
Nice work and welcome to the streak family
LED Always On
Rooted my Streak as above. The LED behavior has changed. The LEDs now flash during activity and the menu LED remains on even when on battery and the display shut off. Any one else see this one and/or have suggestions? Thanks!
Also experiencing light flashing after rooting
The button illumination has changed to oscillate between the middle and bottom buttons when there's activity.
Anyone else seeing this after rooting?
For those of you who are rooted and have the us att dell streak, how did you get the drivers downloaded to your pc? I'm running windows 7 and have not been able to find a solution after looking at this pc screen and searching for seven hours straight. I just want to root this streak and be able to enjoy 2.1, thanks in advance for the help
Rooting the US Streak
STILLSPRINTIN said:
For those of you who are rooted and have the us att dell streak, how did you get the drivers downloaded to your pc? I'm running windows 7 and have not been able to find a solution after looking at this pc screen and searching for seven hours straight. I just want to root this streak and be able to enjoy 2.1, thanks in advance for the help
Click to expand...
Click to collapse
I found a post (search with Dogpile for "rooting the us streak") which detailed how to open device manager, select update driver, and select options to change the driver. This driver may be in the superboot file you have already downloaded. Anyway, once I changed the driver, it worked. (although I have the changed LED behavior detailed above. Do the web search and you'll find the post quickly. Hope this helps!
I recently returned my phone to Gingerbread EH03 and am wanting to root and install a new custom ROM.
I have rooted before but as you can tell am currently unrooted, I have tried both the one-click and the usual command prompt rooting process but neither works.
After I type "./rage.bin" and it restarts adb my phone is no longer recognized when I type "adb devices". I've tried unplugging it and plugging it back in but then it wont be recognized and I have to pull my battery out but this happens each time and I can't find a way around it. Debugging was on, current drivers, etc.
And help?
if your flashing a custom rom there is no need to root. But if you insist on rooting, try this method in section5 of my guide.
http://forum.xda-developers.com/showthread.php?t=1238070
codylicious9 said:
I recently returned my phone to Gingerbread EH03 and am wanting to root and install a new custom ROM.
I have rooted before but as you can tell am currently unrooted, I have tried both the one-click and the usual command prompt rooting process but neither works.
After I type "./rage.bin" and it restarts adb my phone is no longer recognized when I type "adb devices". I've tried unplugging it and plugging it back in but then it wont be recognized and I have to pull my battery out but this happens each time and I can't find a way around it. Debugging was on, current drivers, etc.
And help?
Click to expand...
Click to collapse
Why are you trying to eat pizza with chop sticks?
superclean eh03, TKSGB1118
laureanop said:
Why are you trying to eat pizza with chop sticks?
superclean eh03, TKSGB1118
Click to expand...
Click to collapse
it look like he might be trying to demonstrate chop stick skills.
You only need root on stock roms if you are keeping them OR if you are trying to install recovery via Clockworkmod app. Other than that, most ROMs come with superuser already enabled. The MIUI is the only one I know that you have to actually enable the superuser ability in the settings.
But with these phone's it looks like all you need is a good recovery .tar file and odin. Now, i'm kinda new with this phone, but I have been through at least 10 droids. So I'm not quite sure. I keep asking everyone but I will get a new answer for each person I ask.
So the basic message I'm trying to convey is USE ODIN TO FLASH A RECOVERY and then you can load any rom you want which will have superuser. But recovery is what u want bro, i just dont know how to go about it.
I have Alcatel OT-910, but i cant find anything about root & rom for this model here on xda-developers forum. I found threads for other Alcatel models (OT-908, OT-980, OT-990) and i was wondering is anyone working on this particular model? Is it possibile to have root access? stock ROM for OT-910? Thanks.
Alcatel OT-910
CPU 600 MHz
OS Android OS, v2.2 (Froyo)
Keyboard QWERTY
root
i have tried to root my OT-910 with SuperOneClick 2.3.3, but it doesn't work.
Keeps stuck at Step #7 Waiting for Device.
also tried to unplug and replug it at this part, but no chance.
any other ideas how to get root? Some of the installed apps are useless for me and eat up my memory, want to get rid of them
rooting problem
I've got OT910 too, tried several ways to root with steps, provided for other Alcatel android phones - no luck.
Try with different versions os superoneclick. Aso you should install Pdanet on your phone and your computer to and try again with superoneclick.
Sent from my ALCATEL one touch 990
No luck still
I tried all SuperOneClick releases, z4root, GingerBreak - nothing really works. The phone is hardly operable without root - too much garbage preinstalled.
Hey, i have an Alcatel OT-909a (which is the same as Alcatel OT-910 but with a lower px camera) and i also am unable to get root access, i already know that there is a stock busybox, and have seen some files of the internal memory but still not having luck, i also flashed some CWM and RA recoveries but i just got stuck while trying to access recovery, so i have to get back to stock recovery, i think there must be a way to do at least a nandroid backup and try to root the backup and flash again, but i dont know, the CWM recovery just boot the android logo, after there is nothing in the screen, but the QWERTY keys are on like if the phone was in recovery, i had tried Super One Click 1.9.2 and 2.3.3 and got stuck in step #7 too, zergRush and GingerBreak doesnt work also, something extrange for me is that the last time i try CWM, it didnt boot into recovery but into fastboot, as far as i know internal memory is read-only except for the installation of apps and some folders (or somehow i push GingerBreak and zergRush to the internal memory isn't?), i can't push su to the xbin or bin folders, but i already saw what is inside xbin an bin (as i said memory is read-only and there are some folders that requires permissions to access), there must be a way to push su to xbin folder (or at least maybe access su in another location?) but i still seeing how?
PD: sorry for my possible bad english speaking
PD2: yes i'm a noob and i hate myself but please some of you that know of this, help us?
Edit: just curious i just push su to "/data/local/tmp" then i just tipe ./su and it appeared on the phone "shell has been granted superuser permissions"
Alcatel_OT_909a /909s /910
OS: Android Gingerbread 2.3.4 / 6180
Kernel: 2.6.35.7-perf [email protected] #3
Here an idea: Custom Rom
hey guys, if some of you (someone, anyone who might wanna help?) are still maybe reading this thread, i wonder, i have played with the phone a little (unluckly i really messed up breaking the cellphone and luckily for me, the motherboard was replaced at service center), and i have been able to pull out most of the system partition, custpack and others, (except for the recovery partition) and i was wondering if maybe there is a way to create a custom rom with those files?, maybe we could create our custom rom and flash it, after seeing around the files, i got that 909a it's using what it's looks like at least the same kernel than ot910, (actually some information is from the ot910, in the manual it refers to ot909a-s ot910 as same cellphone but with different px in camera), so maybe we could create a custom GB rom based on the files from the stock system partition, and as alcatel has relased the kernel sourcecode maybe we could even do a custom kernel?, i was just wondering if someone can try to do a custom rom with those files, as i have tried flashing some GB roms replacing files and the phone doesn't boot up to android, but in recovery you get su access and pull the other files, but when replacing files, there is a moment when the system lose adb shell access, so maybe someone with more knowleadge (as i'm new to both android and linux) can help?
Rooting -- any news?
Has anyone succeeded in rooting the device in the meantime? I had no luck with either psneuter, zergrush, or gingerbreak ...
OT-910 successfully rooted!
Hi,
thank's to the great work of giantpune over at Phandroid, the Alcatel OT-910 has been successfully rooted (see the attached screenshot)!
For instructions, cf. the thread "Optimus Elite root with an apk" at Phandroid's LG Optimus Elite forum. Put in a nutshell, you have to install the following two APK's:
1. the Poot-debug.apk tailor-made for this phone, and
2. Ministro II.apk.
Both files are linked at the end of giantpune's original post at the LG Optimus Elite forum.
Note that Superuser, but not SuperSU, will grant root access on the OT-910.
Have fun!
Any Rom for OT 910
nolda said:
Hi,
thank's to the great work of giantpune over at Phandroid, the Alcatel OT-910 has been successfully rooted (see the attached screenshot)!
For instructions, cf. the thread "Optimus Elite root with an apk" at Phandroid's LG Optimus Elite forum. Put in a nutshell, you have to install the following two APK's:
1. the Poot-debug.apk tailor-made for this phone, and
2. Ministro II.apk.
Both files are linked at the end of giantpune's original post at the LG Optimus Elite forum.
Note that Superuser, but not SuperSU, will grant root access on the OT-910.
Have fun!
Click to expand...
Click to collapse
Can you please suggest any ROM for OT 910.
Help need...
Hi guys,
I need your help man, I had just rooted successfully and I don't know what have I done now it is just stuck at TCL logo and restarting.
please please please help...
May be flashing it solve the problem I have sent email to alcatel but they didn't have the rom so some one help me and also I had flash recovery but didn't back up original one so also give me that or any working CWM recovery.
plzzzzzzzzzzzzzzzz
my last hope is xda...
smkamranqadri said:
Hi guys,
I need your help man, I had just rooted successfully and I don't know what have I done now it is just stuck at TCL logo and restarting.
please please please help...
May be flashing it solve the problem I have sent email to alcatel but they didn't have the rom so some one help me and also I had flash recovery but didn't back up original one so also give me that or any working CWM recovery.
plzzzzzzzzzzzzzzzz
my last hope is xda...
Click to expand...
Click to collapse
If your last hope is xda... then maybe you will not have that much luck, if you're stuck at TCL logo, maybe you could try using the "OTU Upgrade Tool" (by means "OTU = Alcatel/TCL Flasher") and maybe that will do the trick and then you get your phone back to stock, if not (or if you already did that), then you're a little out of luck, as far as I know, there is no stock recovery around, and also as far as I know, there is no CWM recovery, now, in case you did use OTU Tool, and failed flashing the phone, then is almost sure that your nand is bricked, if you used OTU Tool and that didn't get your phone back, then you should see if you can still flash Android Images (more accurately 2.3.3 (since 2.3.4 did brick my phone twice)), at least with a non-functional 2.3.3 image, maybe you could flash from there with OTU again, or try to modify 2.3.3 system to work with your phone, if nothing of that did result for you, then you're out of luck, because I'm almost sure that would mean that you are in a nand brick, and the only way to solve it, is sending it to Service Repair (at least for now)
now, for using OTU Upgrade Tool, you can download it from TCL/Alcatel website ( www2.alcatelonetouch.com/global-en/support/download.html ) in the download section, select your phone model, and from there download the OTU Upgrade Tool, after downloading, install it and follow the instructions for getting the phone in "Download Mode" (in OT910 = (pressing "Q" key with the phone totally off, and after pressing the "Q" key for 30sec. or a minute, then (still pressing the "Q" key) connect it to the pc and follow the onscreen steps (that means, choosing your mobile and getting in to look for the firmware and download it)
I have a kind of "backup" of the system (I mean, every file that is in /system) but sadly, it doesn't have the properly permissions set, and so, it gives also a boot loop (also I bricked my phone once again and for worse, when it was out of warranty), so if you still in warranty maybe you should send it to service :/
that's the sad of life when your mobile is not the one that is being developed by expert developers (not even a beginner one )
Hope you can fix your phone
thanks for help
thanks man you are my captain...
I recheck the upgrade tool it just say that you have latest software.
So if you have 2.3.3 then please give me that i will update it via adb shell as i can still access it as su.
smkamranqadri said:
thanks man you are my captain...
I recheck the upgrade tool it just say that you have latest software.
So if you have 2.3.3 then please give me that i will update it via adb shell as i can still access it as su.
Click to expand...
Click to collapse
I will, but before, what version of upgrade tool are you using? (mine has a kind of strange bug that the rom is never ever able to get the last update (as always download saying there is a new update (it's a fake but anyway)), that would be kind of a problem since maybe after you flash 2.3.3 the upgrade tool will state that you're still in latest firmware (even through upgrade tool is supposed to be a service tool, funny isn't?), anyway, since you have nothing to lose (since apparently you flashed a custom recovery that didn't work for you), but, there are this two things you should try before, first (and pretty much the must obvious one) if you have warranty (as long as you're in warranty and never tried to see what's inside the phone), and two, there is a little possibility that maybe you can access adb via the recovery you flashed, even, when the tcl logo appears, try to do "adb shell" or "adb devices", so maybe you can recover your phone without the need of flashing android 2.3.3.
now, if nothing of that worked, then there is nothing to loose, if you have the android sdk, from there you can download a 2.3.3 image, that will boot, but display nothing in the screen (still you can do adb shell with su, and try to properly install libraries maybe?), if not, then i'll check if I can do one system image for you, and see what it does
by the way, if somehow you can access adb , try to do "adb pull" and pull the " /system" partition
it's really sad that we can't (at least not me) figure out, how to use the files that the upgrade tool uses ( 570mb of 10 - 520kb files)
Help me... alcatel 909
Azuruw said:
I will, but before, what version of upgrade tool are you using? (mine has a kind of strange bug that the rom is never ever able to get the last update (as always download saying there is a new update (it's a fake but anyway)), that would be kind of a problem since maybe after you flash 2.3.3 the upgrade tool will state that you're still in latest firmware (even through upgrade tool is supposed to be a service tool, funny isn't?), anyway, since you have nothing to lose (since apparently you flashed a custom recovery that didn't work for you), but, there are this two things you should try before, first (and pretty much the must obvious one) if you have warranty (as long as you're in warranty and never tried to see what's inside the phone), and two, there is a little possibility that maybe you can access adb via the recovery you flashed, even, when the tcl logo appears, try to do "adb shell" or "adb devices", so maybe you can recover your phone without the need of flashing android 2.3.3.
now, if nothing of that worked, then there is nothing to loose, if you have the android sdk, from there you can download a 2.3.3 image, that will boot, but display nothing in the screen (still you can do adb shell with su, and try to properly install libraries maybe?), if not, then i'll check if I can do one system image for you, and see what it does
by the way, if somehow you can access adb , try to do "adb pull" and pull the " /system" partition
it's really sad that we can't (at least not me) figure out, how to use the files that the upgrade tool uses ( 570mb of 10 - 520kb files)
Click to expand...
Click to collapse
First of all my update tool version is 1.2.0.10.
Second i got second hand set from local market at karachi, pakistan so no warranty where i exchange some email from alcatel support for rom but said that they didn't have.
third i can access adb shell with couple of reentering su i got super user so what to do to recover.
i will pull system partition and give you the link soon also downloading sdk for image.
thanks alot...
may we could chat live for better working. find me smkamranqadri at any platform except google kami.genius.
Got ROM/ RECOVERY
smkamranqadri said:
First of all my update tool version is 1.2.0.10.
Second i got second hand set from local market at karachi, pakistan so no warranty where i exchange some email from alcatel support for rom but said that they didn't have.
third i can access adb shell with couple of reentering su i got super user so what to do to recover.
i will pull system partition and give you the link soon also downloading sdk for image.
thanks alot...
may we could chat live for better working. find me smkamranqadri at any platform except google kami.genius.
Click to expand...
Click to collapse
I had got rom & recovery and every partions so any one need have do chat with me at fb - Muhammad Kamran qadri
Hey everyone, (It's a long story: But I would really appreciate any help...)
[I know the easy solution: Boot into RECOVERY MODE and factory reset the phone and if all goes well...DONE.]
I'm running on Android 4.4.(the latest I think its '2'), Stock Firmware, 4G LTE form MetroPCS, and able to get into a so called 'recovery mode' (you can only factory reset the phone) and download mode. I can't get into safe-mode. and I'm Currently stuck in a bootloop or a 'soft-brick'.
Here's what happened:
I've recently been messing around with the tether_dun_required on my LG in order to get it be able to tether WiFi to my laptop.
The phone was rooted using this method: [GUIDE] New Root Method for LG Devices
[ROOT was successful]
I tried various SQLite3 editing apps to try and change the tether_dun_required record in settings.db in data/data/com.android.providers.settings/databases but after looking ant the SuperSU logs I got this error: Cannot [mount or chmod] ... because the filesystem is Read-Only...
So, I decided to use ES-File Explorer to pull the settings.db file to my computer and modified it using SQLite Studio then I copied the files to sdcard and renamed the old settings.db to settings_old.db using ES-File Explorer. (all over WiFi) Then I ran ADB shell and got root using 'su'. I remounted '/' , '/data', and '/system' as RW using "mount -o rw,remount /" and etc... Then, I used the "cp" command to copy the files from "/sdcard/settings.db" to "/data/data/com.providers.settings/databases". I assumed you needed to reboot. So I rebooted the phone. AND....bootloop.
I was going to make a nandroid backup or atleast copy anything important out of the phone but: being a noob... I didn't.
I can't get ADB to run either of the Download or Recovery modes.
I know (have a feeling...) I can fix the phone if I can rename the settings.db to something else and the settings_old.db to settings.db but I don't have access to the filesystem because I can't start ADB.
Ophidian_DarkCore said:
if your savvy with the shell, aroma fm has a built in terminal.
flash this in recovery http://forum.xda-developers.com/showthread.php?t=1646108
then cd to the directory.
rm settings.db
mv settings_old.db settings.db
Click to expand...
Click to collapse
Thanks you for you reply. I have one question though, I have no idea if my bootloader or my kernal or any of that is 'unlocked' I only rooted my phone. If I try to flash aroma fm and they are locked or something would that actually really brick my phone?
ALSO: I don't have an SDCARD... I don't think it's possible to flash anything then? Because flashing from the Internal Storage might brick the device. right?
ALSO: I don't think the LG Optimus F60 has ARM Neon support... & the "Recovery mode" doesn't have any flashing support. It's all STOCK.
LG Optimus F60 Specifications
Any Ideas?
Ophidian_DarkCore said:
well damn, if you have a custom recovery usb-otg you can make a flashable zip that runs some shell commands.
flashing wont brick a device. putting unsigned boot/recovery imgs usually bricks locked devices.
as with all lg devices, there is download mode to load stock firmware/updates. [LOL apparently I can't post outside links yet even, if their a quote...]
Click to expand...
Click to collapse
That's RIGHT! But, sorry for the noob question: What is a custom recovery usb-otg and how do I make a flashable zip that runs some commands? (For example: maybe one that just runs the commands but doesn't actually change the recovery software or the boot just one that can rename the files?)
Also, I don't think it would work but, would flashing the recovery to stock not delete any data, and have the phone be able to boot?
If it's too much to explain that's okay just show me some related posts that can show me how.
Thanks again for your time.
Ophidian_DarkCore said:
maybe try this http://forum.xda-developers.com/showpost.php?p=59637778&postcount=62
EDIT: Disregard below
you need a custom recovery before anything. and apparently your device supports fastboot.... so give this a go http://forum.xda-developers.com/and...8-5-0-touch-recovery-lg-t3049800#post59310323
and later you might get android L
Click to expand...
Click to collapse
I'm not sure, because the phone already has the factory boot and I haven't flashed anything into the Boot Partition. It's probably an error that happens when it tries to validate the settings.db or the permissions it has [chmod or that its mounted read write]. [To my understanding] what TWRP boot loop fix does is install fastboot then the custom recovery and the stock boot again. Which should do about the same thing because the phone is already stock. Right?
Would installing a custom recovery then allow me to access adb or the filesystem? (If so any recommendations?) Or how would I run a script from download mode?
Thanks for your time.
Ophidian_DarkCore said:
you only need to flash the recovery. not the boot img.
installing a custom recovery will either give you adb, or an on device shell.
Click to expand...
Click to collapse
That's right, Thank you. I'm going to try flashing one right now. Do you know of any that give you access to adb? (and maybe have low risk of bricking LG phones?)
Ophidian_DarkCore said:
the one in that thread should work.
fyi, recoveries, roms, and kernels are specialised software usually only compatible with one model. so no mixxy matchy
i guess using those instructions you could try the img from here http://forum.xda-developers.com/and...8-5-0-touch-recovery-lg-t3049800#post59310323
Click to expand...
Click to collapse
How would I install the img? I would need to install fastboot, right? Then run fastboot ****.img?
Is fatboot run from adb or from SendCommand.exe?
Thanks again for all your help.
Ophidian_DarkCore said:
yea, just grab a fastboot binary, the lg driver, go into whatever mode in that thread and
Code:
fastboot flash *.img
edit: fastboot is it's own binary. so it's run in a command shell on your pc like adb is.
Click to expand...
Click to collapse
One last question (Need to make sure...): I have fastboot.exe from the SDK tools, so all I need to do is:
1. Connect the USB
2. Boot into Download Mode
3. Run fastboot flash *.img
4. When finished unplug the USB and take the battery out.
5. Then boot back into Download mode or Recovery Mode to get TWRP?
6. Then try to see if I can get ADB to work?
Also, sorry for all the questions: But If I ever needed to, will a factory reset delete TWRP or will I need to flash it again with the Stock recovery?
Thanks for your time. You are awesome.
Hi, thank you for using XDA Assist. Unfortunately there is no device specific forum for your device. I'm going to ask a moderator to move your thread here, http://forum.xda-developers.com/android/help
Solved it.
I used an exploit to access the filesystem and fix the corrupt db.
crazy_code said:
Hey everyone, (It's a long story: But I would really appreciate any help...)
[I know the easy solution: Boot into RECOVERY MODE and factory reset the phone and if all goes well...DONE.]
I'm running on Android 4.4.(the latest I think its '2'), Stock Firmware, 4G LTE form MetroPCS, and able to get into a so called 'recovery mode' (you can only factory reset the phone) and download mode. I can't get into safe-mode. and I'm Currently stuck in a bootloop or a 'soft-brick'.
Here's what happened:
I've recently been messing around with the tether_dun_required on my LG in order to get it be able to tether WiFi to my laptop.
The phone was rooted using this method: [GUIDE] New Root Method for LG Devices
[ROOT was successful]
I tried various SQLite3 editing apps to try and change the tether_dun_required record in settings.db in data/data/com.android.providers.settings/databases but after looking ant the SuperSU logs I got this error: Cannot [mount or chmod] ... because the filesystem is Read-Only...
So, I decided to use ES-File Explorer to pull the settings.db file to my computer and modified it using SQLite Studio then I copied the files to sdcard and renamed the old settings.db to settings_old.db using ES-File Explorer. (all over WiFi) Then I ran ADB shell and got root using 'su'. I remounted '/' , '/data', and '/system' as RW using "mount -o rw,remount /" and etc... Then, I used the "cp" command to copy the files from "/sdcard/settings.db" to "/data/data/com.providers.settings/databases". I assumed you needed to reboot. So I rebooted the phone. AND....bootloop.
I was going to make a nandroid backup or atleast copy anything important out of the phone but: being a noob... I didn't.
I can't get ADB to run either of the Download or Recovery modes.
I know (have a feeling...) I can fix the phone if I can rename the settings.db to something else and the settings_old.db to settings.db but I don't have access to the filesystem because I can't start ADB.
Maybe it's the fact the system was still mounted as Read-Write when I rebooted and the stock firmware just doesn't like that...
I'm new to android but love to code C, C++, and C#. Does anybody know of any API's that might help me access the filesystem in download mode. Because I'm almost certain the root method I used, used that as an exploit to root the phone.
Or can someone at least point me in the right direction as to how to UN-softbrick the phone without 'factory-resetting' it. I would really love to be able to recover my contacts and pictures.
Click to expand...
Click to collapse
I did the same thing, you installed the wrong model FW. just install the base rom and start over.
crazy_code said:
Hey everyone, (It's a long story: But I would really appreciate any help...)
[I know the easy solution: Boot into RECOVERY MODE and factory reset the phone and if all goes well...DONE.]
I'm running on Android 4.4.(the latest I think its '2'), Stock Firmware, 4G LTE form MetroPCS, and able to get into a so called 'recovery mode' (you can only factory reset the phone) and download mode. I can't get into safe-mode. and I'm Currently stuck in a bootloop or a 'soft-brick'.
Here's what happened:
I've recently been messing around with the tether_dun_required on my LG in order to get it be able to tether WiFi to my laptop.
The phone was rooted using this method: [GUIDE] New Root Method for LG Devices
[ROOT was successful]
I tried various SQLite3 editing apps to try and change the tether_dun_required record in settings.db in data/data/com.android.providers.settings/databases but after looking ant the SuperSU logs I got this error: Cannot [mount or chmod] ... because the filesystem is Read-Only...
So, I decided to use ES-File Explorer to pull the settings.db file to my computer and modified it using SQLite Studio then I copied the files to sdcard and renamed the old settings.db to settings_old.db using ES-File Explorer. (all over WiFi) Then I ran ADB shell and got root using 'su'. I remounted '/' , '/data', and '/system' as RW using "mount -o rw,remount /" and etc... Then, I used the "cp" command to copy the files from "/sdcard/settings.db" to "/data/data/com.providers.settings/databases". I assumed you needed to reboot. So I rebooted the phone. AND....bootloop.
I was going to make a nandroid backup or atleast copy anything important out of the phone but: being a noob... I didn't.
I can't get ADB to run either of the Download or Recovery modes.
I know (have a feeling...) I can fix the phone if I can rename the settings.db to something else and the settings_old.db to settings.db but I don't have access to the filesystem because I can't start ADB.
Maybe it's the fact the system was still mounted as Read-Write when I rebooted and the stock firmware just doesn't like that...
I'm new to android but love to code C, C++, and C#. Does anybody know of any API's that might help me access the filesystem in download mode. Because I'm almost certain the root method I used, used that as an exploit to root the phone.
Or can someone at least point me in the right direction as to how to UN-softbrick the phone without 'factory-resetting' it. I would really love to be able to recover my contacts and pictures.
Click to expand...
Click to collapse
i need to restore my lg f60 (i'm in the us and the carrier it supports is metropcs). i have TWRP recovery on it. can someone link to stock firmware/rom (whatever the terminology is...basically the operating system that the phone came w/), usb drivers, software tool to install the firmware, and everything i need to restore my phone back to how it was when i bought it.
i was curious and tried lollipop (i think i tried both 5.0 something or 5.1 something or just one of them ended up working) but the camera was completely non-functional so now i need to go back to the phone being how it was when i bought it.
the firmware i've installed on the phone right now is MS39510G_00 (i think "MS39510G" is the actual identifier of the firmware, and the 00 is probably not useful for anything; the site i got it from maybe just appends it for some reason). but this firmware doesn't seem like what the phone came with or i'm not using/not doing everything i need to to restore it back to normal.
couple of things that strike me as odd and make me think that i don't have the right firmware or just didn't do something right:
there's a weird white area at the bottom, which i think was transparent and took on the color of the wallpaper on the phone when you just bought it & didn't mess around w/it
some of the icons are just the generic green android icon. a lot of apps have this same icon instead of different icons of their own
the lock screen seems also seems kind of different. it doesn't look like the lock screen of a new lg f60. maybe i was using a custom lock screen (i doubt it, but it's possible) but still it doesn't look like the standard lock screen to me
how do i restore my us metropcs lg f60 phone back to stock?
i need to restore my lg f60 (i'm in the us and the carrier it supports is metropcs). i have TWRP recovery on it. can someone link to stock firmware/rom (whatever the terminology is...basically the operating system that the phone came w/), usb drivers, software tool to install the firmware, and everything i need to restore my phone back to how it was when i bought it
i was curious and tried lollipop (i think i tried both 5.0 something or 5.1 something or just one of them ended up working) but the camera was completely non-functional so now i need to go back to the phone being how it was when i bought it.
the firmware i've installed on the phone right now is MS39510G_00 (i think "MS39510G" is the actual identifier of the firmware, and the 00 is probably not useful for anything; the site i got it from maybe just appends it for some reason). but this firmware doesn't seem like what the phone came with or i'm not using/not doing everything i need to to restore it back to normal.
couple of things that strike me as odd and make me think that i don't have the right firmware or just didn't do something right:
there's a weird white area at the bottom, which i think was transparent and took on the color of the wallpaper on the phone when you just bought it & didn't mess around w/it
some of the icons are just the generic green android icon. a lot of apps have this same icon instead of different icons of their own
the lock screen also seems kind of different. it doesn't look like the lock screen of a new lg f60. maybe i was using a custom lock screen (i doubt it, but it's possible) but still it doesn't look like the standard lock screen to me
Help Help
Help anyone, i have LG f60 (390n) running with 5.0.1 lollipop. I wanted to instal custom recovery and install custom rom CM. But i have two problems:
1. If i want to boot to download mode - i have error "SECURE BOOT ERROR" (but it boots up normally, and work normally)
2.If i want to boot to recovery mode - i have error "LOADING KETSTORE FAILED STATUS 5"
Please help.
I am not able to flash it trough LG Flash tool, and i am not able to boot into custom recovery.
Hi all,
I have been through douzens of threads and forums looking for a solution to this.
I followed some instructions to modify the build.prop file on my Huawei G535-L11 to disable Huawei theme manager in order to get Xsposed working fully (changed ro.config.hwtheme: 0). I did a backup of my original build.prop before hand, and my phone was rooted and unlocked but running the stock rom.
Unfortunately, it rebooted but won't go past the first 'EE' splash screen (just turns off again).
I can inconsistently get in to both fastboot and Android recovery, so I have been trying to use adb to push the original build.prop to /system/ on the phone.
However, this fails as /system/ is apparently RO. I have now discovered that I can't get SU permissions despite my phone being rooted.
If I try:
adb shell
$ su
nothing happens and it goes back to a $ prompt.
If I try:
adb root
I get the message (paraphrased):
adb cannot run as root in production builds.
So I can't push or do any adb method of restoring the build.prop file?! I don't understand why it is acting as if it is not rooted. I had Link2sd, Gravity Box, No Frills Cpu Controller all set up and working before, so I'm fairly sure I did truly have root.
I have also tried flashing a TWRP recovery, which apparently is successful, but when I go in to recovery it is still the Android Recovery.
Does anyone have any ideas what I could do to get my phone working again please?! This is my last gasp before the phone gets filed under 'B' in the cylindrical cabinet in the corner of the room!
Any assistance greatly appreciated!
Some systems are very finicky with modded build.props, or you didn't set the file's permissions correctly. I'm afraid without being able to boot or a working custom recovery, then adb won't work, much less root enabled adb functions. adb works in some stock recoveries, but only for sideloading files directly signed by the manufacturer. In regards to TWRP, is the bootloader unlocked? If not, that would explain why it didn't work. Other than that, I don't believe you'll have any other options besides reloading the stock firmware.
Hi,
Thanks for the reply. Yes, the bootloader was / is unlocked.
Unfortunately, there isn't any stock firmware available anywhere. Unless someone out there has a backed up rom image from the EE Kestrel?
This is supposed to be a working TWRP for your device http://forum.xda-developers.com/showpost.php?p=58522448&postcount=117 - if you get it loaded, there might be a chance to push the working build.prop back to the phone. I would read that thread too and see if there isn't more useful info there or another member with your phone that could make a backup for you. Good luck.
Thanks.
Unfortunately, I'm pretty sure that is the TWRP I've tried. I'll double check when I'm on my PC.
I might try requesting a rom image on that thread, but the community for this phone seems to be pretty dead :/
I've just gone and ordered a new phone anyway, but it seems like a waste of a good phone just for the sake of one line of bad code!
Thanks for your help. I'll post again if I have any success.