-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Possibly bricked lg optimus v?
- Thread starter Rc1993
- Start date
-
- Tags
- lg optimus v
bigsupersquid
Well-Known Member
you lost the temporary usable recovery when the rom was installed. all that's left is the blacked-out one.
if you have a flashable zip version of the recovery, you could count button presses and install that blind, else you'll have to use adb again.
at least now you can use adb while booted into the rom OR recovery.
you might have gotten an error in terminal because i forgot to mention
before flash_image.
if you haven't used su in terminal before, superuser will ask you for verification you want to allow terminal root privileges. tell it yes.
edit: if, booted into the rom, and adb shell has a $ prompt, you'll have to type su first as well. make sure your screen is on so you can tell superuser to allow adb root privileges when it asks.
if you have a flashable zip version of the recovery, you could count button presses and install that blind, else you'll have to use adb again.
at least now you can use adb while booted into the rom OR recovery.
you might have gotten an error in terminal because i forgot to mention
Code:
suif you haven't used su in terminal before, superuser will ask you for verification you want to allow terminal root privileges. tell it yes.
edit: if, booted into the rom, and adb shell has a $ prompt, you'll have to type su first as well. make sure your screen is on so you can tell superuser to allow adb root privileges when it asks.
brotherswing
Android Expert
facepalm
bigsupersquid
Well-Known Member
glad it's working now.
bob's rom, or Jerry's, or mrg666's, all kick serious a**.
others'll have to help you tweak it now, my idea of that is to leave out the gapps, turn off all sync, and manually remove or kill on reboot email, calendar provider, and such... most people don't like their phones set up my way.
and, now that it's all working, it's very important to make a backup in recovery to save yourself possible hassle later.
bob's rom, or Jerry's, or mrg666's, all kick serious a**.
others'll have to help you tweak it now, my idea of that is to leave out the gapps, turn off all sync, and manually remove or kill on reboot email, calendar provider, and such... most people don't like their phones set up my way.
and, now that it's all working, it's very important to make a backup in recovery to save yourself possible hassle later.
bigsupersquid
Well-Known Member
pros: fast, lots of free memory
cons: no market or other google services, no push notifications (like email), it's basically a little computer with a phone attached.
works for me, but not for social people who use the phone for keeping connected.
for example, i set up my woman's V as a standard Android device (market, sync, and all) with the same rom I'm using (right now an older iho mirage build) because she uses those features.
cons: no market or other google services, no push notifications (like email), it's basically a little computer with a phone attached.
works for me, but not for social people who use the phone for keeping connected.
for example, i set up my woman's V as a standard Android device (market, sync, and all) with the same rom I'm using (right now an older iho mirage build) because she uses those features.
brotherswing
Android Expert
Gapps won't really effect that, but keep in mind, without market access, you're going to be somewhat limited in choices for apps. Just sayin'
brotherswing
Android Expert
Now that's a different question entirely. It all comes down to what you do with your phone.
I'm hoping someone can help me with a similar problem. I was trying to install harmonia on my optimus v and used rom manager. And now I can't get the phone to boot past showing the lg logo. I can get adb to sort of work. I can see my phone when I type ./adb devices and it's listed as recovery. I can't do anything else though. I try ./adb shell and it says - exec '/system/bin/sh' failed: No such file or directory (2) -
when I try pushing busybox it says failed to copy permission denied
when I try remounting it says remount failed: Operation not permitted
How do I proceed? I'm trying to do this:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5
flash_image recovery /sdcard/recovery.img
reboot recovery
so that I can get back to square one and have a working phone at least. Any help would be greatly appreciated!
Jon
when I try pushing busybox it says failed to copy permission denied
when I try remounting it says remount failed: Operation not permitted
How do I proceed? I'm trying to do this:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5
flash_image recovery /sdcard/recovery.img
reboot recovery
so that I can get back to square one and have a working phone at least. Any help would be greatly appreciated!
Jon
brotherswing
Android Expert
You flashed the wrong recovery for your phone (there have been two revisions of the OV). Type "su", then your commands will work. Check these links...
That should have you squared away. If not, we're here to help.
Ok, I'm trying to flash the xionia_cwma file and i can't do anything because i can't get adb to go into the shell. I should mention I'm using OS X and have just been typing adb commands in the adb directory, like: ./adb devices
How do I get the files onto the sdcard if i can't get adb to let me?
How do I get the files onto the sdcard if i can't get adb to let me?
brotherswing
Android Expert
You should probably use this one instead. It's the correct recovery for your phone, and should unbrick you. I'd try connecting the card directly to your Mac, if it has a card reader. That's going to be easiest. I have to admit, I'm not the best one here to help you with this, AndyOpie150 or bigsupersquid know way more than I do about unbricking.
Ah. I was hoping to get that adb working because I'm working out in the field (literally) and won't be anywhere I'll have access to one of those micro-sd adapters for another week. Oh well. If anyone has any suggestions on how to get my adb working I'd appreciate it. Otherwise I'll try those suggestions with the micro-sd adapter when I get home. Thanks!
brotherswing
Android Expert
If you have that kind of patience, then rest assured you'll find the advice you need. And with that, I'm off to bed.
AndyOpie150
<strong> <a href="http://androidforums.com/optimus
When tying to get adb shell to work, in a command prompt you need to get to wherever your established system path to your adb.exe.
My adb.exe was in the SDK/platform-tools. Yours might be in the SDK/tools
I had Windows Vista 32 and once I opened a command prompt I would type in:
cd..(enter)
cd..(enter) this would get me to the root of my C drive were my SDK folder is.
Then I would type in:
cd SDK/platform-tools. I would get SDK/platform-tools>
I would then type in:
adb shell(enter) and would get a # letting me know my device was rooted(there's a little more to it) and could continue.
I would then type in:
su(return). Then I would type in the code.
I hope this will help you even though you have an OS I don't know anything about.
My adb.exe was in the SDK/platform-tools. Yours might be in the SDK/tools
I had Windows Vista 32 and once I opened a command prompt I would type in:
cd..(enter)
cd..(enter) this would get me to the root of my C drive were my SDK folder is.
Then I would type in:
cd SDK/platform-tools. I would get SDK/platform-tools>
I would then type in:
adb shell(enter) and would get a # letting me know my device was rooted(there's a little more to it) and could continue.
I would then type in:
su(return). Then I would type in the code.
I hope this will help you even though you have an OS I don't know anything about.
brotherswing
Android Expert
All the commands you used are compatible with Linux as well. Seeing as how OsX is based on BSD, the same commands ought to work.
Yes, my adb is in ~/android-sdk-macosx/platform-tools/ and I cd to that directory and issue my adb commands as ./adb However when I try ./adb shell I get the "- exec '/system/bin/sh' failed: No such file or directory (2) -" error. I know the device is connected though because when I type ./adb devices it returns "List of devices attached
A10000194377B8 recovery" And I can do the ./adb reboot recovery and the phone reboots. I don't know why ./adb shell won't work though. I've done some searching on google for that error and can't figure out how to fix it.
A10000194377B8 recovery" And I can do the ./adb reboot recovery and the phone reboots. I don't know why ./adb shell won't work though. I've done some searching on google for that error and can't figure out how to fix it.
AndyOpie150
<strong> <a href="http://androidforums.com/optimus
Once your in the proper directory try just typing:
adb shell(return) instead of( ./adb shell) then type:
su(return)
(return) =hit the return key, don't type in.
adb shell(return) instead of( ./adb shell) then type:
su(return)
(return) =hit the return key, don't type in.
Ok quick update... I saw this in a thread on xda-developers by Elegroth "Oh yeah, btw, if the Optimus V ever gets stuck in stock recovery, press the "back" button then "home" button to boot into the rom. Not sure why it works (I was never able to see the screen), but it worked." That worked for me and now I can get into the adb shell with ./adb shell and I get the #. So now I'm trying to push the flash_image and xionia_cwma_12518.6.img but I get "push not found"