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

Root [Virgin Mobile] [BETA] [4.4.4] Cyanogenmod 11 Unofficial

wladmcd said:
hey guys could help me? I know that is not the area nor the right post to ask, but recently my lg optimus of nowhere f3 gave brick, and when I try to flash a stock rom the KDZ of the following error:
[R&D Test Tools Log File]

18:34:07 : Start fn_StartUpgrade
18:34:07 : Extract kdz file
18:34:51 : kdz decrypt Success
18:35:25 : Extract file Success.
18:35:25 : LGMobileDL Load.
18:35:25 : Port = -1
18:35:25 : Connection check start.
18:35:40 : Check Phone mode = 2
18:35:40 : Phone type check.......
18:35:41 : LGMobileDL.DLL Loading....
18:35:41 : _SetAuthMark Fail
18:35:42 : _SetAuthMark Ok : wAuthMark(65535)
18:35:42 : _DetachDLL Call
18:35:47 : _DetachDLL Call End
18:35:47 : Param : Path = C:\ProgramData\LGMOBILEAX\Phone\P655H10B_Develop.wdb
18:35:47 : Param : moduleDir =
18:35:47 : Param : waitTime = 25496712
18:35:47 : Param : UsbHighSpeed = 1
18:35:47 : Param : PhoneMode = 2
18:35:47 : Param : BinVersion = P655H10B_vivo
18:35:47 : Param : AuthMark = 65535
18:35:47 : Call fn_StartUpgrade
18:38:57 : 3GQCT : wParam = 100, lParam = 0
18:38:57 : Step : Upgrade Error error code = 0
18:38:57 : ResetStartInfo() Call
18:38:57 : _DetachDLL Call
18:39:02 : _DetachDLL Call End
18:39:02 : FreeLibrary Call
18:39:02 : FreeLibrary Call End
18:39:02 : ResetStartInfo() Call End
18:39:02 : 3GQCT : wParam = 100, lParam = 64
18:39:02 : Step : Upgrade Error error code = 64
18:39:02 : ResetStartInfo() Call
18:39:02 : ResetStartInfo() Call End
18:39:02 : Finish All test

have access to cwm, already I tried installing a custom ROM, but the error in the mounting system, this taking to enter the cwm,
the error of cwm: mounting / cache /
mounting / data /
and mounting / system
already tried to do hardreset and install a custom rom, but is locked in the boot screen, I insert an attachment here the log LGMObilesupporttool, tried to use two laptops and nothing, tried reinstalling drivers and msxml and nothing.
Click to expand...

Edit: I was a bit hasty assuming that something was wrong with aboot...

Try:
Code: 
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/cache
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/data
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/system

If that doesn't help, you could try:

Use ADB in CWM to push aboot.img to /tmp
Code: 
adb push aboot.img /tmp/aboot.img
Then do
Code: 
dd if=/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
 
Last edited:
upload_2015-8-16_18-33-30.png


above is the log adb, I tried to move the aboot, but it did not work, the error persisted
the recovery screen is only:
E: Can't open \cache\recovery\log
E: Can't mount \cache\recovery\last_log
E: Can't open\last_install
(but i can use the options of CWM)
and when i reboot still is in bootloader screen: / but the LEDs light up.

#Edit i try this too:
upload_2015-8-16_19-23-35.png
 
Last edited:
daemon32 said:
Edit: I was a bit hasty assuming that something was wrong with aboot...

Try:
Code: 
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/cache
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/data
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/system

If that doesn't help, you could try:

Use ADB in CWM to push aboot.img to /tmp
Code: 
adb push aboot.img /tmp/aboot.img
Then do
Code: 
dd if=/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Click to expand...
I try this and i get:
upload_2015-8-16_18-51-0.png


#Edit thanks for you reply, but nothing work's so far, I tried to reboot into the bootloader, but the fastboot does not detect the phone.
 
Last edited:
No, its just a file to verify it was not tampered with. If its not something your familiar with, I wouldn't worry about downloading it.
 
I only use twrp, I just don't reboot from cm into recovery or it factory resets, I do the button presses on boot to get into recovery. Hey xclusive, just letting you know that, for me, superuser stays with cm11, but with carbon rom I loose it after every boot. I actually used kingroot for a while, but I'm back on cm, I love it! Thank you for all your hard work.

btw, what is sboot? I've never used aboot, zboot, sboot or anything like that. Guess i'm lucky
 
I can't give you a description of what the aboot image (partition) is. I don't know but i'm sure you can look it up on the internet. But what I do know is that it's apart of the boot process and is necessary to boot.

I can't help you with root using carbonrom. It worked for me, not sure why it wouldn't work for anyone else. Root is not enabled in it by default.
 
xclusive36 said:
I can't give you a description of what the aboot image (partition) is. I don't know but i'm sure you can look it up on the internet. But what I do know is that it's apart of the boot process and is necessary to boot.

I can't help you with root using carbonrom. It worked for me, not sure why it wouldn't work for anyone else. Root is not enabled in it by default.
Click to expand...

oh, ok, no problem. I installed towelroot in it, then installed supersu, then busy box, but lost su after everyboot. Kingroot worked fine though, but I had to root it through the windows desktop application, because the android app would crash the OS with a kernel panic.
 
You must log in or register to reply here.
Back
Top Bottom