• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root System Recovery Loop - Won't Display Recovery Menu

M

mjstealey

Newbie
I have an LG-OptV that came with 2.2.2 from Virgin Mobile.
Based on what's posted in the forums I used gingerbreak 1.2 to root the phone.
All was fine up until I got stuck in a situation where the phone won't go into the recovery screen, rather it loops through it yielding the following:

Android system recovery...
Do not pull out the battery!!
Formatting Data...
Formatting Cache...
Factory reset...
Rebooting...

I'd post an image, but as this is my first post, so I'm unable to that just yet...

Background:
Followed the steps in the "Guide to Rooting Without a Computer"
gingerbreak 1.2 rooted the phone just fine
Initially flashed Xionia Recovery zip (blue font)
Next flashed CM7.1.0.1-BobZ ROM (2.3.7)
At this point all appeared to work fine
Went back and reflashed the recovery to CWM_3.0.2.4 (orange font) as I figured I'd be playing mostly with 2.3 ROM flavors
Was getting ready to flash BACKside ROM and began going about clearing the cache, etc. and that's when I got myself into the system recovery loop issue.

The primary hangup is that I don't seem to truly have root access anymore.
I can terminal in, and su from $ to # at the prompt, but any command I try results in "permission denied".

At this point I've tried ROMTools, ADB and FastbootRoot with no success. All connect with the device just fine, and will get and show the # at the prompt, but when it comes time to actually flash a new recovery image it doesn't occur. Instead the device reboots, goes through the system recovery as described above, and boots as if it's a brand new install... All previous data on the phone is wiped. The SD card seems to be unaffected by any of this.

I've also tried to reapply gingerbreak to no avail... It installs, makes a superuser request which I allow, and then generates the error "could not extract assets!"

I have searched the forums prior to posting this but have not yet found this same issue. Apologies if I somehow missed something obvious here.

I'm new to android in general and have been learning by trial and error based on perusing the forums.
Any pointers would be greatly appreciated.

Also wanted to add that Rom Manager has also been tried. App installs properly from the market, appears to get all the correct credentials, downloads and states that the recovery ROM is flashed. However upon reboot the same behavior occurs by going through the system recovery loop and erasing all prior data.
 
I don't know much about, it but it is possible you have the V with the S screen. There is a thread around about it. You might try that one.
 
bigsupersquid said:
[How To] Fix "Most" Boot Loop Issues Caused By Factory Reset - Android Forums
you'll need to use the adb commands to format mtd8.
Click to expand...

I had tried this without any success...
It seems my root privileges aren't truly root. Not entirely sure if the su on the phone has become corrupted, or if I'm facing something entirely different.

ADB has the same response as the Terminal Emulator. I can access the device without a problem, I can establish "#" at the prompt, but then any command that gets executed results in "permission denied". This includes even commands like "ls"...

I can still pull through ADB, and have successfully pushed to the sdcard and will read around some more and see what happens.

Thank you for the input!!
 
Open your superuser app and make sure that Terminal Emulator has superuser permission. I had this issue once before.
 
In the end I've opted to get a new Optimus and as luck would have it, it turned out to be the older model that shipped with 2.2.1 on it.

This time around it rooted like a dream, with su, busybox, etc. humming along as they should.

Currently running BACKside moderately overclocked and very happy with the results.

I'll tinker with my original Optimus (v2.2.2) as time permits and post results if I can ever break it from it's "no recovery for you" looping fits...

Thanks to all who contributed thoughts and ideas, it was much appreciated :-)
 
you might try running busybox from the sdcard to do shell commands, if busybox isn't installed terminal and adb will default to toolbox which is very much... not permissive.
also, toolbox will let you use the cat command, you can try this to clear your bootloop...
Code: 
adb shell cat /dev/zero > dev/mtd/mtd8
that command may hang up the adb shell or crash with an 'out-of-memory' error or somesuch; after a minute of so you can close the window with adb if it locks up.
if it works, it'll do the same thing as 'flashall_eraseall' and wipe the FACT_RESET string out of mtd8, which will allow your phone to boot.
 
I was able to get out of the bootloop by using this. Thank you.

Unfortunately, after I installed the stockopv.zip rom, the phone would freeze on the ANDROID while booting. When I wiped the system to try and reinstall, I was greeted with the bootloop problem again.

But... now that I know longer have a "system" I cannot use ADP, or Terminal Emulator. And since I can't get back into recovery... it seems I can't do anything at all.

Is this the Ultimate Brick??

Any ideas or thoughts?
 
Relix said:
I was able to get out of the bootloop by using this. Thank you.

Unfortunately, after I installed the stockopv.zip rom, the phone would freeze on the ANDROID while booting. When I wiped the system to try and reinstall, I was greeted with the bootloop problem again.

But... now that I know longer have a "system" I cannot use ADP, or Terminal Emulator. And since I can't get back into recovery... it seems I can't do anything at all.

Is this the Ultimate Brick??

Any ideas or thoughts?
Click to expand...


I'm not very experienced with this, but I did get out of a boot loop once by removing the battery for a couple of minutes, putting it back and then powering up again. It might be worth a try.
 
Try this here [FIX]Black screen with custom recovery and custom roms - Page 15 - Android Forums at AndroidCentral.com
Follow the instructions to the t. Download the xionia 1.2518.6 first.
You have a Hitachi screen and the recovery you installed was way wrong for it and the V in general. It be nice if things came with a disclaimer-this doesn't work with this model, and so forth, but they usually don''t

If your still having diffeculties shoot me a pm. I'll get a notification ringtone in case I'm on nother page.
 
I decided to post a photo and a link to a video of what the phone does. That way there is no confusion. In addition, know that I cannot use the ADB SHELL.

When I try to use the ADB SHELL, I get the following error:

- exec '/system/bin/sh' failed: No such file or directory (2) -

So, unfortunately, any instructions that include using the ADB SHELL are pretty well useless for me until I am able to fix the recovery.

Here's the video. No matter how I start the phone (pressing the power button or pressing home, vol. down and power button) it does the same thing.

Optimus V Brick? - YouTube

Is there any way to int erupt this without ADB SHELL and without being able to boot the phone into a ROM?

brick.jpg
 
That is the same problem I am having, I just got there a different way. I was useing Xionia recovery to clean out my phone that is formating the caches. Getting it ready to install a new rom (backside IHO) While moveing aroud in the xionia menus I saw a option to format the system with the factory format and because I was useing xionia I assumed it would be alright so I did and now I have what you have. With no hope insite.
 
You must log in or register to reply here.
Back
Top Bottom