[xtacocorex]

Not sure of the Fix Boot Loop is working zefie in 12518.4, both phones of mine still get stuck if running off the battery only.

If they are hooked to the computer, powered down, sit for a couple of minutes the phones boot right up. I'm trying to think of what would be different when it's hooked up on the UBS? Haven't tried it yet with the regular AC adapter.

Is the default action for that wipe to not display output to the screen, have the screen go black, and then reboot?

I also noticed that when going to wipe dalvik it came up with an error that a partition was missing /dev/block/mmcblk0p2. Does this have something to do with CyanogenMod or the /dalvik-cache to /cache mod?

[MaXXimus]

I also noticed that when going to wipe dalvik it came up with an error that a partition was missing /dev/block/mmcblk0p2. Does this have something to do with CyanogenMod or the /dalvik-cache to /cache mod?

I just tried this out and got an error too but right under the error it said that the dalvik cache was cleared.

Swyped from my LS670 using Tapatalk

[O.a.T.]

If they are hooked to the computer, powered down, sit for a couple of minutes the phones boot right up. I'm trying to think of what would be different when it's hooked up on the UBS? Haven't tried it yet with the regular AC adapter.

I would like to know this too, both the "hooked up on USB" and "with the regular AC adapter".

[xtacocorex]

Decided to test an LG Factory Wipe from recovery to see if it would fix some issues.

I did have the Xionia Kernel installed when I ran it. I am now stuck at the stock "Android" loading screen.

Steps to recreate:
1 - Select LG Factory Wipe
- Wipe says it is clearing data and cache (does this quickly)
- Phone reboots with all your settings
2 - Power off phone (no reboot)
3 - Long Press Power button until LG Logo
- Recovery goes straight to the LG Factory Wipe
- Clears data, cache, and then performs factory reset
4 - Phone reboots and is stuck in animation boot-loop

Linked a logcat for you, one thing I did notice when I ran it initially was a Fatal Exception in the Power Sequence step.

[zefie]

Not sure of the Fix Boot Loop is working zefie in 12518.4, both phones of mine still get stuck if running off the battery only.

If they are hooked to the computer, powered down, sit for a couple of minutes the phones boot right up. I'm trying to think of what would be different when it's hooked up on the UBS? Haven't tried it yet with the regular AC adapter.

Is the default action for that wipe to not display output to the screen, have the screen go black, and then reboot?

I also noticed that when going to wipe dalvik it came up with an error that a partition was missing /dev/block/mmcblk0p2. Does this have something to do with CyanogenMod or the /dalvik-cache to /cache mod?

Here is what Fix Boot Loop attemps to do

1) Wipe /dev/mtd/mtd7 (bootloader cmds, this tells it to boot-recovery, update-radio, or blank for standard boot)
2) Wipe /dev/mtd/mtd8 (lge bootloader cmds, these are LGE cmds used for Factory Reset (FACT_RESET_3 tells it to wipe, FACT_RESET_6 is what it sets to when its done, no idea what that does. CWMA reads mtd8 and passes control to LGE Recovery if we see FACT_RESET_3, which is how we now support true Factory Reset. lol).
3) Reboot.


It will not fix:
Broken boot partition
Broken /system partition
anything else really lol

Thats not to say I'm discarding your issue. No, in fact I'm intrigued by it.

If you can reproduce this, trigger it again, use the Fix Boot Loop option, then when it reloads recovery run these cmds:

adb shell strings /dev/mtd/mtd7
adb shell strings /dev/mtd/mtd8

As for you running LG Factory Reset, this was not tested on CM7. I do not know what part of the reset process rewrites FACT_RESET_3 but it is NOT the bootloader. Even on ThunderROM, nROM or VCRom you need to wait for the system to boot to the "Welcome to LS670" screen before it will disable the flag and let you boot into recovery again. I don't really have a way to reset it manually unless I can somehow intercept the reboot cmd LGE Recovery issues after it wipes.

You are not bricked though but at this point you have to race against time.
When you reboot recovery and Xionia CWMA passes it to LGE Recovery, because it still sees FACT_RESET_3, quicky attempt to run this command: (copy and paste the whole line)

adb shell flash_eraseall /dev/mtd/mtd8; adb reboot recovery

If you are successful you should be able to boot back into recovery.
Then you will have to go back to VCRom, ThundeROM, or nROM because LGE Factory Reset erases provisioning, and we cannot provision in CM7.

[xtacocorex]

Here is what Fix Boot Loop attemps to do

1) Wipe /dev/mtd/mtd7 (bootloader cmds, this tells it to boot-recovery, update-radio, or blank for standard boot)
2) Wipe /dev/mtd/mtd8 (lge bootloader cmds, these are LGE cmds used for Factory Reset (FACT_RESET_3 tells it to wipe, FACT_RESET_6 is what it sets to when its done, no idea what that does. CWMA reads mtd8 and passes control to LGE Recovery if we see FACT_RESET_3, which is how we now support true Factory Reset. lol).
3) Reboot.


It will not fix:
Broken boot partition
Broken /system partition
anything else really lol

Thats not to say I'm discarding your issue. No, in fact I'm intrigued by it.

If you can reproduce this, trigger it again, use the Fix Boot Loop option, then when it reloads recovery run these cmds:

adb shell strings /dev/mtd/mtd7
adb shell strings /dev/mtd/mtd8

When I can get back into the phone, I'll test this out. Think I'm going to have to run the force flash stuff in that other thread back to VC unless you have any other options. I knew I shouldn't have hit the LG Factory Wipe, but it was for the sake of science.

Gotta run to work, if I get time, I'll check in here to see updates, otherwise it won't be until tonight when I can get back online.

[sfhub]

Then you will have to go back to VCRom, ThundeROM, or nROM because LGE Factory Reset erases provisioning, and we cannot provision in CM7.

Curious, is LGE Factory Reset performing the same operations as ##786# reset (from the dialer)?

[zefie]

Curious, is LGE Factory Reset performing the same operations as ##786# reset (from the dialer)?

Yessir. I wouldn't run it on CM7.

[tmeader]

Okay, trying to flash this recovery (already running the previous custom recovery) I seem to be stuck. The first time, I went through the instructions, and accidentally put "yaffs" instead of "yaffs2" in for the first line. Everything seemed to go fine until the the last line to flash the recovery, at which point it came up with a ton of "insufficient memory". So, I scrolled up and saw the error, and just started fresh from the beginning... this time typing everything properly (Terminal App). Seemed to all complete fine, but after "reboot recovery", it seems hung at the LG logo.

Any ideas how to fix this??

[xtacocorex]

Here is what Fix Boot Loop attemps to do

1) Wipe /dev/mtd/mtd7 (bootloader cmds, this tells it to boot-recovery, update-radio, or blank for standard boot)
2) Wipe /dev/mtd/mtd8 (lge bootloader cmds, these are LGE cmds used for Factory Reset (FACT_RESET_3 tells it to wipe, FACT_RESET_6 is what it sets to when its done, no idea what that does. CWMA reads mtd8 and passes control to LGE Recovery if we see FACT_RESET_3, which is how we now support true Factory Reset. lol).
3) Reboot.


It will not fix:
Broken boot partition
Broken /system partition
anything else really lol

Thats not to say I'm discarding your issue. No, in fact I'm intrigued by it.

If you can reproduce this, trigger it again, use the Fix Boot Loop option, then when it reloads recovery run these cmds:

adb shell strings /dev/mtd/mtd7
adb shell strings /dev/mtd/mtd8

As for you running LG Factory Reset, this was not tested on CM7. I do not know what part of the reset process rewrites FACT_RESET_3 but it is NOT the bootloader. Even on ThunderROM, nROM or VCRom you need to wait for the system to boot to the "Welcome to LS670" screen before it will disable the flag and let you boot into recovery again. I don't really have a way to reset it manually unless I can somehow intercept the reboot cmd LGE Recovery issues after it wipes.

You are not bricked though but at this point you have to race against time.
When you reboot recovery and Xionia CWMA passes it to LGE Recovery, because it still sees FACT_RESET_3, quicky attempt to run this command: (copy and paste the whole line)

adb shell flash_eraseall /dev/mtd/mtd8; adb reboot recovery

If you are successful you should be able to boot back into recovery.
Then you will have to go back to VCRom, ThundeROM, or nROM because LGE Factory Reset erases provisioning, and we cannot provision in CM7.

So I tried this out and it failed, I did forget to mention a key piece of data: the phone, when I get it to boot to recovery, starts the LG Wipe. I am not running CM7, just the CWMA recovery, I installed the Xionia kernel.

I have lost my root on the system.

I have tried, when it starts doing the LG Wipe, to run the adb commands you gave, but I get the following error:

$ ./adb shell flash_eraseall /dev/mtd/mtd8; ./adb reboot recovery
error: protocol fault (no status)
error: device not found

I'm a huge winner.

EDIT:
BACK IN MY PHONE! Woo!

Force flash VC update with KP500 Utilities. Maybe that fixed the not powering on shizzle that was happening.

That sucked and now I'm really wary of rooting again.

EDIT 2:
Not out of the woods yet, first power off and then power on hung trying to get into recovery. Used adb and I still have CWMA recovery, interesting, but I guess the updater doesn't touch the recovery partition.

Going to try what you suggested now zefie.

[HondaCop]

I attempted to flash this recovery and am having a problem. I did all the adb commands one by one without a problem. It did give me the "failed on '/system/etc/install-recovery.sh' - No such file or directory" error but I continued as instructed to do so. When the phone rebooted, it went to screen with blue letters that read as follows:

Android system recovery <3e>
Android system recovery utility

reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition


Right below it reads like this in yellow:

Android system recovery...
Do not pullout the battery!!
Finding update package...
E:Can't find command file CACHE:recovery/command
Installation aborted, no valid image in CACHE.


If I choose reboot system now, it will show me a screen with a small android below a big white triangle with a yellow exclamation mark inside it.

What did I do wrong? Can anyone please help? Thanks in advance.

[xtacocorex]

Thats not to say I'm discarding your issue. No, in fact I'm intrigued by it.

If you can reproduce this, trigger it again, use the Fix Boot Loop option, then when it reloads recovery run these cmds:

adb shell strings /dev/mtd/mtd7
adb shell strings /dev/mtd/mtd8

C:\Program Files\Android\android-sdk-windows\platform-tools>adb shell strings /dev/mtd/mtd7
recovery
--wipe_data

C:\Program Files\Android\android-sdk-windows\platform-tools>adb shell strings /dev/mtd/mtd8

C:\Program Files\Android\android-sdk-windows\platform-tools>

[MaXXimus]

Okay, trying to flash this recovery (already running the previous custom recovery) I seem to be stuck. The first time, I went through the instructions, and accidentally put "yaffs" instead of "yaffs2" in for the first line. Everything seemed to go fine until the the last line to flash the recovery, at which point it came up with a ton of "insufficient memory". So, I scrolled up and saw the error, and just started fresh from the beginning... this time typing everything properly (Terminal App). Seemed to all complete fine, but after "reboot recovery", it seems hung at the LG logo.

Any ideas how to fix this??

I got the insufficient memory error too. I ended up pulling the battery, because I was stuck at the lg splash. My phone rebooted alright, then I ran through the ADB commands again and it worked fine. My post is here.

[HondaCop]

ARGGGGGG!!! I did all the commands on the first post but I did NOT UNZIP the flash and img files! I simply placed the zip files on the sdcard root folder. =( This is what screwed me up! Is there any way to fix my problem? I am stuck at the LG recovery screen. Phone will not boot.

[tmeader]

I got the insufficient memory error too. I ended up pulling the battery, because I was stuck at the lg splash. My phone rebooted alright, then I ran through the ADB commands again and it worked fine. My post is here.

Saw your post earlier and actually tried redoing it with all the commands four times now... still the stuck LG splash screen if I try to go into recovery. Tried IM'ing beezy,Nick7 and KSmithInNY, so waiting hopefully for some more suggestions from the pros on here. At the very least I'd like to get back to the other recovery for the time being.

[MaXXimus]

Hmmm. Are you getting the really long string of errors? That's exactly what happened to me.

I had to also restart ADB. I think what happened with me was that the tools updated at the same time I was putting in the ADB commands and the interface got corrupted. Once I restarted everything it finally worked. It's worth a shot at least.

[MaXXimus]

ARGGGGGG!!! I did all the commands on the first post but I did NOT UNZIP the flash and img files! I simply placed the zip files on the sdcard root folder. =( This is what screwed me up! Is there any way to fix my problem? I am stuck at the LG recovery screen. Phone will not boot.

I don't think running the ADB commands would make it so you couldn't fully boot unless you are still trying to boot into recovery. Try pulling the battery and waiting a minute then just starting up normal. If you reboot completely, then unzip the files and run through the ADB commands.

[tmeader]

Hmmm. Are you getting the really long string of errors? That's exactly what happened to me.

I had to also restart ADB. I think what happened with me was that the tools updated at the same time I was putting in the ADB commands and the interface got corrupted. Once I restarted everything it finally worked. It's worth a shot at least.

Yeah, I've given it 4 tries Still no luck. Ugh.

[HondaCop]

I don't think running the ADB commands would make it so you couldn't fully boot unless you are still trying to boot into recovery. Try pulling the battery and waiting a minute then just starting up normal. If you reboot completely, then unzip the files and run through the ADB commands.

I've tried pulling battery, emergency mode, unbricking methods and nothing helps. Now the phone will start up to the black and white LG logo screen and just sit there. =( I can't no longer access the LG recovery either or emergency mode.

PS. My name is HondaCop and I approve this message.

[tmeader]

Okay, so, for the hell of it I tried flashing the Thunder-c recovery back onto the phone, using the exact same steps. That one flashed completely fine and my phone boots into that recovery again with no problem. Tried again after that following the steps here EXACTLY (copy and pasted even), and my phone just boots up to the LG prompt and sits there if you try to go into recovery. Ugh. How are people getting this one to flash correctly??

Side note: I noticed that the "flash_image" file in this recovery vs the Thunder-c recovery is VERY different in size. Is that also tied to the actual .img file, or could I attempt to flash this one using the flash_image that works well with the Thunder-c recovery? I noticed when I flashed back to Thunder-c that there is an (expected) pause after you enter the command to actually flash the recovery image, assuming from it being copied and applied. Executing that last command with the flash_image and xionia recovery included in this post produces no such pause. As soon as you hit enter, the prompt pops right back up. Odd. There's no errors or anything, but every time I try to reboot into recovery, it just hangs at the LG screen. Something tells me it's not actually flashing the image in that last step.

Any ideas? I'd like to try this one, since I love having the sub folder navigation like in the 1.2 version of the Thunder-c recovery... but for some reason that one appears to be "un-official" still from the dev, so not sure if that's cool?

[MaXXimus]

You may have a corrupt download. I wouldn't swap the flash image because I think that's tied to the recovery. Re-download both files and unzip them to the root of your SD and try again. That may do the trick. Fingers crossed.

[tmeader]

You may have a corrupt download. I wouldn't swap the flash image because I think that's tied to the recovery. Re-download both files and unzip them to the root of your SD and try again. That may do the trick. Fingers crossed.

Tried that three times now as well. Oh well, I'd like to give it a shot, but I guess I'll live with the other recovery for now. Hate not knowing what's "wrong" with it though... frustrating.

[blackdroid43]

I want to flash this custom recovery, but my original recovery has beed deleted by "ROM Manager"... Will this method still work?

[blackdroid43]

Is there a way to load xionia_cwma_12518.4.img in E-mode?

[zefie]

Is there a way to load xionia_cwma_12518.4.img in E-mode?

No, not yet