Blue Handle Error on Rogers LG EVE

[GoogleCodeExporter]

Hi 

Sorry to post this again, but i can not find a solution on any other post.  I 
am getting the Blue Error Handler on my LG EVE.  I have read through all the 
forums that i could find on this site.  All the solutions i can find do not 
work.  The error comes up 8-10 seconds after i see the Openetna screen.

I have a Rogers LG EVE.  It was version 1.5 

After loading boot 2.4.4 and systemV6.1-rc5 i get the Blue Error Handler 
(listed at the bottom)

I can access the phone through ADB if i use the everecovery01a.img file.  I 
have tried manually clearing the cache, userdata, boot, system. using fastboot 
erase and cat /dev/zero > /dev/mtdx (x=3,4,6) I had a file /lgdrm/system.id 
that had my IMEI number, but no device.id so i copied it to a file called 
device.id (didn't help)

The only thing that i can not clear is in /userdata there is a folder called 
"misc" with the following file(s) i can not delete.  Are they links?

/userdata/misc # ls -l
ls -l
ls: ./akmd_set.txt: No such file or directory
ls: ./akmd_set.txt: No such file or directory
ls: ./akmd_set.txt: No such file or directory
ls: ./akmd_set.txt.tmp: No such file or directory
ls: ./akmd_set.txt: No such file or directory
ls: ./akmd_set.txt.tmp: No such file or directory
ls: ./akmd_set.txt: No such file or directory
ls: ./akmd_set.txt.tmp: No such file or directory
ls: ./akmd_set.txt: No such file or directory
ls: ./akmd_set.txt: No such file or directory
ls: ./akmd_set.txt.tmp: No such file or directory
ls: ./akmd_set.txt: No such file or directory
ls: ./akmd_set.txt.tmp: No such file or directory

Outside of that i do not know what else i can try.  Of course i did not backup 
my phone because i read that only linux could run the backup (i have win7), i 
found the process after.

in recovery how do you select the wipe data/factory reset?  I can move to it in 
the list with the volume buttons but any key i push on the eve does not seem to 
select it.  There is no ALT key to do ALT + W

Does Rogers have something loaded that is affecting this?  Does anyone have a 
link to download 1.5 with boot?? So i can try to go back? I can not find it...

[Blue Error Handler] Arm11 is Crashed!!
[Press Volume up key] To get Ramdump!!
[Press Volume down key] Reboot&savelog!!
-----------
Linux Kernel Panic
Process akmd2 (pid: 1252)
-----------
PC : yaffs_rename+0xec/0x168
LR : _spin_unlock_irqrestore+0x30/0x50
pc : [<c0152354>]    Ir : [<c034e6e0>]
psr: a0000013    sp : ca485e58
ip : ca485e10    fp : ca485e84
r10: 00000001    r9 : ca484000
r8 : cb2f1000    r7 : cad42c10
r6 : cab34f80    r5 : cad68358
r4 : cad42c10    r3 : 00000000
r2 : ca485e10    r1 : 00000007
r0 : 00000000
------<Call Stack>-------
[<c0152268>] yaffs_rename+0x0/0x168
[<c00e0024>] vfs_rename+0x0/0x378
[<c00e1a88>] sys_renameat+0x0/01d8
[<c00e1c60>] sys_rename+0x0/0x28

Original issue reported on code.google.com by laser...@gmail.com on 14 Jan 2011 at 1:56

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

One thing i have also noticed is if i do a fastboot -w command and then try to 
load the boot.img and system.img after, they both fail.  If i reboot the phone 
and do not run the -w command, i have no problem flashing the image files...

Original comment by laser...@gmail.com on 14 Jan 2011 at 2:48

[GoogleCodeExporter]

You can try reflashing an official firmware with lg tools, and then retrying 
with openetna. It's possible tha the error is somewhere we can't reach with 
fastboot... you could probably get more help in the forum though.

Original comment by GiorgioM...@gmail.com on 14 Jan 2011 at 10:18

[GoogleCodeExporter]

I got it working late last night.  The Amon RA recovery might have fixed it, i 
found the below solution that worked for me.  

fastboot phone
fastboot boot everecovery01a.img 
adb shell
cat /dev/zero > /dev/mtd1
cat /dev/zero > /dev/mtd2
cat /dev/zero > /dev/mtd3
cat /dev/zero > /dev/mtd4
cat /dev/zero > /dev/mtd6
reboot phone into fastboot
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache clean.img (i got the clean.img from another post.)

After that process the phone sat at the Cyanogen(mod) screen for over 30 
minutes.  I powered it off.

Powered the phone back into fastboot
fastboot erase cache
fastboot -w

rebooted the phone and it boot up without any errors or issues.

Original comment by laser...@gmail.com on 14 Jan 2011 at 1:58

[GoogleCodeExporter]

Original comment by GiorgioM...@gmail.com on 14 Jan 2011 at 5:26

• Changed state: Invalid