I made a terrible mistake by repeating on my P760 steps shown on youtube: How To Fix Status 7 Error with CWM Recovery on Rooted Android! http://www.youtube.com/watch?v=QW1znjDLe-k
Phone was downgraded with V10A_00.kdz and then successfully rooted. Next I was receiving status 7 in clockwork when trying to install latest CM 10.2. So removed line from file META_INF/co/google/android/updater-script
Code:
assert(getprop("ro.product.device") == "p760" || getprop("ro.build.product") == "p760");
After installation I had LG Security Error. Manage to remove it using fastboot x-loader.img, recovery.img, boot.img (files from: http://forum.xda-developers.com/showpost.php?p=39716305&postcount=7), battery is charging after this and standard animation appears again.
But still not possible is to install previous ROMs using Factory ICS/JB ROM WITH OFFLINE FIX as I getting problem with (_CheckPhoneType() Error) (checked on: V10A_00.kdz and P760_Orange(Poland)_V20I_00.kdz) in UpTestEX_mod2_marwin.exe
That is only log I have at the moment:
Code:
23:32:09 : [C:\LGMobileUpgrade] Try to delete folder
23:32:09 : RemoveDirectory1 Error(2):C:\LGMobileUpgrade
23:32:09 : Start Date : 2013-11-05 23:32:09
23:32:09 : ---------- QM Testmode ---------
23:32:09 : ***** Check Tool Version *****
23:32:09 : Tool version : 1.5.4.8
23:32:09 : UpgradeDLL version : 1.2.6.7
23:32:09 : Current Dir : C:\ProgramData\LGMOBILEAX\B2C_Client
23:32:09 : LGE USB Driver Version :
23:32:09 : Android PDLV Version :
23:32:09 : Android NDLV Version :
23:32:09 : ******************************************
23:32:09 : [C:\ProgramData\LGMOBILEAX\Phone] Try to delete folder
23:32:09 : RemoveDirectory1 Error(2):C:\ProgramData\LGMOBILEAX\Phone
23:32:09 : SetEmerModeAT()
23:32:09 : _IsConnectedPhone Call
23:32:25 : _IsConnectedPhone(1)
23:32:25 : 0 - NotConnected.
23:32:25 : 1 - Normal connect success
23:32:25 : 2 - Emergency connect success
23:32:27 : _IsConnectedPhone Call for SmartPhone
23:32:27 : _IsConnectedPhone(0)
23:32:27 : 0 - NotConnected.
23:32:27 : 1 - Normal connect success
23:32:27 : 2 - Emergency connect success
23:32:27 : *****CheckOS Start********
23:32:27 : Microsoft_Windows7_Professional_Service Pack 1
23:32:27 : *****CheckPCSyncPrograms Start*****
23:32:27 : PCSyncPrograms Not Found - OK and ready to upgrade
23:32:27 : Checking the connection with the cell phone...
23:32:27 : dwWaitResetTime(40000 ms)
23:32:28 : _IsConnectedPhone Call
23:32:33 : _IsConnectedPhone(1)
23:32:33 : 0 - NotConnected.
23:32:33 : 1 - Normal connect success
23:32:33 : 2 - Emergency connect success
23:32:33 : Phone Mode(1)
23:32:33 : *****GetPhoneType Start*****
23:32:34 : [011,700,147,062,092]Updating is not possible any longer due to a fatal error.\n\n[009,400,102,102,102]Disconnect from and connect the cable into your phone again and remove \nand install the battery and press the [009,700,102,102,102]'Restart'[009,400,102,102,102] button. This will resume the \nupgrade.\n\n\n\n\n\n\n\n\n\n\n\n\nPress the [009,700,102,102,102]Quit[009,400,102,102,102] button to stop the update. (_CheckPhoneType() Error)
23:32:34 : !pUpgrade->StartProcessing ... PostMsg STEP_TYPE_ENV_ERROR
23:32:34 : Page_Error şÎşĐŔÔ´Ď´Ů
23:32:34 : ż©±â´Â Retry şÎşĐŔÔ´Ď´Ů
23:32:34 : OnStepMsg STEP_TYPE_ENV_ERROR delete m_pLGCyonUpdate
Anyone have any idea about this problem and how to resolve it?
Galegor said:
Anyone have any idea about this problem and how to resolve it?
Click to expand...
Click to collapse
Is there anything I could do to resolve this?
Maybe in some manual way phone configuration can by restored?
Your phone is not recognized by the lg software. Try reflashing ICS xloader and uboot, put phone in SW mode and kdz flash
Sent from my LG-P768 using xda app-developers app
shucrut said:
Your phone is not recognized by the lg software. Try reflashing ICS xloader and uboot, put phone in SW mode and kdz flash
Sent from my LG-P768 using xda app-developers app
Click to expand...
Click to collapse
you need to restore your device using LG Tool, the original one from LG site, not the modded one for off-line update.
Download it from LG, put the device in software update and use the recovery option.
Remenber to modify your "hosts" file first, otherwise the tool cannot connect to LG database
- shifu - said:
Download it from LG, put the device in software update and use the recovery option.
Click to expand...
Click to collapse
Shifu, Shucrut thank you for response!
:laugh: I manage to bring my phone back to life as Shifu said, using standard LG tool.
Original LG Mobile Support Tool and phone in recovery mode has been stopping installation on a very beginning with info that phone requires restart- I also tried this before as one of options without success. Now I give it a tray using and S/W Upgrade mode and that worked for me.
Hello, I shall do my best to shortly and concisely lay out my difficulties. (It was a bad decision to try to install a custom ROM on the Monday before finals)
I was looking to put a custom ROM on my phone, and was following this guide. I put CWM on my phone via this method. I had the ROM I wanted on my SD card. I boot into CWM, wipe the davlek cache like a good little boy, wipe the system (yikes), and select the .zip I want. Nope, status 7 error, abort! Heart racing slightly, I quickly Google and find a nice solution. Problem! When I reboot back into CWM... there is no CWM, and I'm stuck with the useless stock recovery mode that literally does nothing but show a picture of a dead android on its side.
I'm having issues with the offline installer. I've tried both the automated method and doing it myself but really nothing seems to be getting around the fact that my computer doesn't want to talk to my windows 8 computer, or my friend's windows 7 computer.
Here's some log output:
Code:
16:09:25 : [C:\LGMobileUpgrade] Try to delete folder
16:09:25 : RemoveDirectory1 Error(2):C:\LGMobileUpgrade
16:09:25 : Start Date : 2014-03-10 16:09:25
16:09:25 : ---------- QM Testmode ---------
16:09:25 : ***** Check Tool Version *****
16:09:25 : Tool version : 1.5.4.8
16:09:25 : UpgradeDLL version : 1.2.6.7
16:09:25 : Current Dir : C:\ProgramData\LGMOBILEAX\B2C_Client
16:09:26 : LGE USB Driver Version :
16:09:26 : Android PDLV Version :
16:09:26 : Android NDLV Version :
16:09:26 : ******************************************
16:09:26 : [C:\ProgramData\LGMOBILEAX\Phone] Try to delete folder
16:09:26 : RemoveDirectory1 Error(2):C:\ProgramData\LGMOBILEAX\Phone
16:09:26 : SetEmerModeAT()
16:09:26 : _IsConnectedPhone Call
16:09:35 : _IsConnectedPhone(0)
16:09:35 : 0 - NotConnected.
16:09:35 : 1 - Normal connect success
16:09:35 : 2 - Emergency connect success
16:09:35 : *****CheckOS Start********
16:09:35 : Microsoft_Windows7_Home Edition_
16:09:35 : *****CheckPCSyncPrograms Start*****
16:09:36 : PCSyncPrograms Not Found - OK and ready to upgrade
16:09:36 : Checking the connection with the cell phone...
16:09:36 : dwWaitResetTime(40000 ms)
16:09:37 : _IsConnectedPhone Call
16:09:44 : _IsConnectedPhone(0)
16:09:44 : 0 - NotConnected.
16:09:44 : 1 - Normal connect success
16:09:44 : 2 - Emergency connect success
16:09:45 : _IsConnectedPhone Call
16:09:52 : _IsConnectedPhone(0)
16:09:52 : 0 - NotConnected.
16:09:52 : 1 - Normal connect success
16:09:52 : 2 - Emergency connect success
16:09:53 : _IsConnectedPhone Call
16:10:01 : _IsConnectedPhone(0)
16:10:01 : 0 - NotConnected.
16:10:01 : 1 - Normal connect success
16:10:01 : 2 - Emergency connect success
16:10:01 : [009,400,102,102,102]The USB cable and your cellphone are not connected.\nPlease connect your phone and wait for connecting \nthe USB port for a while and press the [009,700,147,062,092]'Restart'[009,400,102,102,102] button.
16:10:11 : _IsConnectedPhone Call
16:10:11 : _IsConnectedPhone(0)
16:10:11 : 0 - NotConnected.
16:10:11 : 1 - Normal connect success
16:10:11 : 2 - Emergency connect success
16:10:11 : [009,400,102,102,102]The USB cable and your cellphone are not connected.\nPlease connect your phone and wait for connecting \nthe USB port for a while and press the [009,700,147,062,092]'Restart'[009,400,102,102,102] button.
16:10:17 : _IsConnectedPhone Call
16:10:24 : _IsConnectedPhone(0)
16:10:24 : 0 - NotConnected.
16:10:24 : 1 - Normal connect success
16:10:24 : 2 - Emergency connect success
16:10:24 : [009,400,102,102,102]The USB cable and your cellphone are not connected.\nPlease connect your phone and wait for connecting \nthe USB port for a while and press the [009,700,147,062,092]'Restart'[009,400,102,102,102] button.
16:11:02 : _IsConnectedPhone Call
16:11:02 : _IsConnectedPhone(0)
16:11:02 : 0 - NotConnected.
16:11:02 : 1 - Normal connect success
16:11:02 : 2 - Emergency connect success
16:11:02 : [009,400,102,102,102]The USB cable and your cellphone are not connected.\nPlease connect your phone and wait for connecting \nthe USB port for a while and press the [009,700,147,062,092]'Restart'[009,400,102,102,102] button.
16:11:04 : Check Cancel button active..
16:11:04 : Check Cancel button active..
16:11:04 : !pUpgrade->StartProcessing ... PostMsg STEP_TYPE_ENV_ERROR
16:11:04 : Page_Error ºÎºÐÀÔ´Ï´Ù
16:11:04 : [011,700,147,062,092]LG Mobile Phone Software Update was canceled\n\n[009,400,102,102,102]To quit LG Mobile Phone Software Update, please press the [009,700,147,062,092]Exit[009,400,102,102,102] button below.
16:11:04 : OnStepMsg STEP_TYPE_ENV_ERROR delete m_pLGCyonUpdate
And screenshots attached.
Listed in Device Manager:
ADB Interface > Android Platform Sooner Single ADB Interface
Modems > LGE Android Platform USB Modem
> LGE Mobile USB Modem
> LGE Mobile USB Modem #2
Other Devices > Unknown device (I installed the fastboot drivers to this, had to get around the driver signature stuff)
Ports (COM & LPT) > LGE Android Platform USB Serial Port (COM7)
> LGE Mobile USB Serial Port (COM4)
> LGE Mobile USB Serial Port (COM6)
Universal Serial Bus Controllers > LGE Mobile Composite USB Device
> LGE Mobile Composite USB Device
Please help if you can. Thank you.
Hi not_so_optimustic, you could try this way: http://forum.xda-developers.com/showthread.php?p=50729855
Cheers. Good luck.
Sent from my LG P76020L-EUR-XX unlocked and rooted
BajoPrimate said:
Hi not_so_optimustic, you could try this way: http://forum.xda-developers.com/showthread.php?p=50729855
Cheers. Good luck.
Sent from my LG P76020L-EUR-XX unlocked and rooted
Click to expand...
Click to collapse
Thank you for the reply.
What happens: I hold power and volume up after plugging in. Immediately I get a "USB device no recognized" in a bubble in the bottom right. A second later I get the S/W screen. I put the battery in. Start the program. If I switch windows it hangs. It gives me this:
Code:
[R&D Test Tools Log File]
20:28:06 : Launching SW update
20:28:06 : Unpacking KDZ
20:29:00 : KDZ file extraced
20:29:18 : Files were extracted.
20:29:18 : LGMobileDL Load.
20:29:19 : Port = 0
20:29:19 : Connecting to phone
20:29:42 : PHONE WAS NOT FOUND!
20:29:44 : ===FINISHED===
Hi not_so_optimustic, did you do this?
**Navigate to Update/Tools and there select upgrade recovery.
Click to expand...
Click to collapse
Just in case:
In the own tool you have an option for install the drivers, you could try it.
Cheers . Good luck.
Sent from my LG P76020L-EUR-XX unlocked and rooted
BajoPrimate said:
Hi not_so_optimustic, did you do this?
Just in case:
In the own tool you have an option for install the drivers, you could try it.
Cheers . Good luck.
Sent from my LG P76020L-EUR-XX unlocked and rooted
Click to expand...
Click to collapse
Sorry for the delay. I have found some more time to try to fix it this weekend.
I am not sure what this part refers to:
**Navigate to Update/Tools and there select emergency recovery software.
Click to expand...
Click to collapse
There is no such menu visible in B2CAppSetup.exe that I can see.
Other oddities:
I was wrong about my phone model. it is actually an LG L9 MS769, not a P769. I don't know if that matters.
The B2CAppSetup.exe interface looks VERY different on my friends computer as opposed to mine. (see the attached screenshot) I am in the process of going through the motions on her computer to see if I get different results. However after opening the app and selecting my phone model and letting it install the drivers, I unplug and plug the USB cable again (staying in S/W mode), and nothing interesting happens beyond the circling "connecting" icon.
Let me know what you think. I'll keep trying.
I feel like I'm getting close! After installing the drivers, both the "Start Upgrade" and "Install USB Driver" buttons are greyed out. A message assures me that "Your device has the latest software available from the LG Mobile Support Tool", although this is clearly not true.
After clicking on the dropdown menu in the top right and selecting "Upgrade Recovery" it pops open the window pictured in the screenshot and attempts to download the software. This window stops progress at the download stage where the timer is frozen at 15 seconds.
Reinstall recovery image through fastboot
I managed to mess my L9 up several times before getting the bootloader unlocked, and one of the ways I got out of it was getting into fastboot using this method: http://forum.xda-developers.com/showthread.php?t=2119090 and then using fastboot commands to re-flash recovery, as described here: http://wiki.cyanogenmod.org/w/Template:Recovery_install_fastboot (step 6). You can find recovery img files in the second post on this thread: http://forum.xda-developers.com/showthread.php?t=2623222
If you can get into recovery again then you can flash a new rom, if I've understood your problem correctly. Good luck!
Try This one work if you install JB before [Need s/w update mode only]
not_so_optimustic said:
Hello, I shall do my best to shortly and concisely lay out my difficulties. (It was a bad decision to try to install a custom ROM on the Monday before finals)
I was looking to put a custom ROM on my phone, and was following this guide. I put CWM on my phone via this method. I had the ROM I wanted on my SD card. I boot into CWM, wipe the davlek cache like a good little boy, wipe the system (yikes), and select the .zip I want. Nope, status 7 error, abort! Heart racing slightly, I quickly Google and find a nice solution. Problem! When I reboot back into CWM... there is no CWM, and I'm stuck with the useless stock recovery mode that literally does nothing but show a picture of a dead android on its side.
I'm having issues with the offline installer. I've tried both the automated method and doing it myself but really nothing seems to be getting around the fact that my computer doesn't want to talk to my windows 8 computer, or my friend's windows 7 computer.
Here's some log output:
Code:
16:09:25 : [C:\LGMobileUpgrade] Try to delete folder
16:09:25 : RemoveDirectory1 Error(2):C:\LGMobileUpgrade
16:09:25 : Start Date : 2014-03-10 16:09:25
16:09:25 : ---------- QM Testmode ---------
16:09:25 : ***** Check Tool Version *****
16:09:25 : Tool version : 1.5.4.8
16:09:25 : UpgradeDLL version : 1.2.6.7
16:09:25 : Current Dir : C:\ProgramData\LGMOBILEAX\B2C_Client
16:09:26 : LGE USB Driver Version :
16:09:26 : Android PDLV Version :
16:09:26 : Android NDLV Version :
16:09:26 : ******************************************
16:09:26 : [C:\ProgramData\LGMOBILEAX\Phone] Try to delete folder
16:09:26 : RemoveDirectory1 Error(2):C:\ProgramData\LGMOBILEAX\Phone
16:09:26 : SetEmerModeAT()
16:09:26 : _IsConnectedPhone Call
16:09:35 : _IsConnectedPhone(0)
16:09:35 : 0 - NotConnected.
16:09:35 : 1 - Normal connect success
16:09:35 : 2 - Emergency connect success
16:09:35 : *****CheckOS Start********
16:09:35 : Microsoft_Windows7_Home Edition_
16:09:35 : *****CheckPCSyncPrograms Start*****
16:09:36 : PCSyncPrograms Not Found - OK and ready to upgrade
16:09:36 : Checking the connection with the cell phone...
16:09:36 : dwWaitResetTime(40000 ms)
16:09:37 : _IsConnectedPhone Call
16:09:44 : _IsConnectedPhone(0)
16:09:44 : 0 - NotConnected.
16:09:44 : 1 - Normal connect success
16:09:44 : 2 - Emergency connect success
16:09:45 : _IsConnectedPhone Call
16:09:52 : _IsConnectedPhone(0)
16:09:52 : 0 - NotConnected.
16:09:52 : 1 - Normal connect success
16:09:52 : 2 - Emergency connect success
16:09:53 : _IsConnectedPhone Call
16:10:01 : _IsConnectedPhone(0)
16:10:01 : 0 - NotConnected.
16:10:01 : 1 - Normal connect success
16:10:01 : 2 - Emergency connect success
16:10:01 : [009,400,102,102,102]The USB cable and your cellphone are not connected.\nPlease connect your phone and wait for connecting \nthe USB port for a while and press the [009,700,147,062,092]'Restart'[009,400,102,102,102] button.
16:10:11 : _IsConnectedPhone Call
16:10:11 : _IsConnectedPhone(0)
16:10:11 : 0 - NotConnected.
16:10:11 : 1 - Normal connect success
16:10:11 : 2 - Emergency connect success
16:10:11 : [009,400,102,102,102]The USB cable and your cellphone are not connected.\nPlease connect your phone and wait for connecting \nthe USB port for a while and press the [009,700,147,062,092]'Restart'[009,400,102,102,102] button.
16:10:17 : _IsConnectedPhone Call
16:10:24 : _IsConnectedPhone(0)
16:10:24 : 0 - NotConnected.
16:10:24 : 1 - Normal connect success
16:10:24 : 2 - Emergency connect success
16:10:24 : [009,400,102,102,102]The USB cable and your cellphone are not connected.\nPlease connect your phone and wait for connecting \nthe USB port for a while and press the [009,700,147,062,092]'Restart'[009,400,102,102,102] button.
16:11:02 : _IsConnectedPhone Call
16:11:02 : _IsConnectedPhone(0)
16:11:02 : 0 - NotConnected.
16:11:02 : 1 - Normal connect success
16:11:02 : 2 - Emergency connect success
16:11:02 : [009,400,102,102,102]The USB cable and your cellphone are not connected.\nPlease connect your phone and wait for connecting \nthe USB port for a while and press the [009,700,147,062,092]'Restart'[009,400,102,102,102] button.
16:11:04 : Check Cancel button active..
16:11:04 : Check Cancel button active..
16:11:04 : !pUpgrade->StartProcessing ... PostMsg STEP_TYPE_ENV_ERROR
16:11:04 : Page_Error ºÎºÐÀÔ´Ï´Ù
16:11:04 : [011,700,147,062,092]LG Mobile Phone Software Update was canceled\n\n[009,400,102,102,102]To quit LG Mobile Phone Software Update, please press the [009,700,147,062,092]Exit[009,400,102,102,102] button below.
16:11:04 : OnStepMsg STEP_TYPE_ENV_ERROR delete m_pLGCyonUpdate
And screenshots attached.
Listed in Device Manager:
ADB Interface > Android Platform Sooner Single ADB Interface
Modems > LGE Android Platform USB Modem
> LGE Mobile USB Modem
> LGE Mobile USB Modem #2
Other Devices > Unknown device (I installed the fastboot drivers to this, had to get around the driver signature stuff)
Ports (COM & LPT) > LGE Android Platform USB Serial Port (COM7)
> LGE Mobile USB Serial Port (COM4)
> LGE Mobile USB Serial Port (COM6)
Universal Serial Bus Controllers > LGE Mobile Composite USB Device
> LGE Mobile Composite USB Device
Please help if you can. Thank you.
Click to expand...
Click to collapse
Try This one work if you install JB before [Need s/w update mode only]
http://forum.xda-developers.com/show....php?t=2686746
davidxd said:
I managed to mess my L9 up several times before getting the bootloader unlocked, and one of the ways I got out of it was getting into fastboot using this method: http://forum.xda-developers.com/showthread.php?t=2119090 and then using fastboot commands to re-flash recovery, as described here: http://wiki.cyanogenmod.org/w/Template:Recovery_install_fastboot (step 6). You can find recovery img files in the second post on this thread: http://forum.xda-developers.com/showthread.php?t=2623222
If you can get into recovery again then you can flash a new rom, if I've understood your problem correctly. Good luck!
Click to expand...
Click to collapse
I flashed the recovery (successfully?). My next confusion is how to boot into it. My device now shows the LG logo at boot and "Security Error" underneath.
Code:
C:\omap4boot-for_optimus-v1.21>start_fastboot.bat
--------------------------------------------
OMAP4boot for P920/P720/SU540/SU760/SU870
--------------------------------------------
by wkpark at gmail dot com
[1] cx2 - Optimus 3D Cube (SU870/P720)
[2] p920 - Optimus 3D (P920)
[3] p940 - Prada 3.0 (P940)
[4] su540 - Prada 3.0 (SU540/KU5400)
[5] su760 - Optimus 3D (SU760)
[x] exit
-------------------------------------------
Select device and <ENTER> 3
p940 selected
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x4
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 5fd90f8f47e3dafb559b8cc604f1b59164668513
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 9c669ad9
CRC1: 682adccf
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-seconds...
[*] msg size = 4
usb_write 21552
[*] data size = 21552
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
------------------------------
Please remove USB cable
and wait until LG Logo on
then reconnent USB cable again
------------------------------
fastboot devices (y/N) ? and press <ENTER> n
ls: resigned/p940-MLO*.bin: No such file or directory
Do you want to replace u-boot (y/N) ?n
ls: cwm/p940-*.img: No such file or directory
Press any key to continue . . .
0163953A1401F010 fastboot
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\omap4boot-for_optimus-v1.21>fastboot flash recovery recovery-clockwork-6.0.3.
1-p760.img
sending 'recovery' (5894 KB)...
OKAY [ 3.020s]
writing 'recovery'...
OKAY [ 1.538s]
finished. total time: 4.559s
C:\omap4boot-for_optimus-v1.21>fastboot reboot
rebooting...
finished. total time: 0.003s
C:\omap4boot-for_optimus-v1.21>
Oh ****. My phone does not boot, period. It still goes into fastboot mode when connected to the computer. I tried following the steps a few more times, and during my last attempt, after
Code:
At the other prompts answer always "N", this could be important.
I pressed "y" and it replaced "u-boot." Currently hitting myself over the head. How do I reflash the stock u-boot?
Hi not_so_optimustic, you could try this http://forum.xda-developers.com/showthread.php?p=48834061.
Cheers. Good luck
Sent from my LG P76020L-EUR-XX unlocked and rooted
u-boot
This post might help you there:
http://forum.xda-developers.com/showpost.php?p=40121966&postcount=7
davidxd said:
This post might help you there:
http://forum.xda-developers.com/showpost.php?p=40121966&postcount=7
Click to expand...
Click to collapse
I didn't manage to get that fix to work as I got errors of "The program can't start because AbdWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem."
HOWEVER
BajoPrimate said:
Hi not_so_optimustic, you could try this http://forum.xda-developers.com/showthread.php?p=48834061.
Cheers. Good luck
Sent from my LG P76020L-EUR-XX unlocked and rooted
Click to expand...
Click to collapse
This worked pretty perfectly to fix the u-boot problem. After flashing the three attached images for u-boot, boot, and recovery, the boot process was back to "normal." So I then used "fastboot flash recovery [my cwm file]" and it flashed successfully again, and I'm back to the LG logo with the security error, and not really sure how to get to CWM.
The guide you linked to recommends the offline fix, which is the method I've been having issues with. My goal at this point is to get CWM to start properly so I can flash my ROM from the SD card. However the method to fix the security error involves installing a different recovery (not CWM). So that's where I stand at this point.
I'll do some more research and be back here to report whatever my next screwup happens to be.
EDIT: So I think my security error is due to my bootloader not being unlocked. I will attempt to follow this guide and we'll see how it goes. http://forum.xda-developers.com/showthread.php?t=2221102
EDIT2: The first link says to go here for p769. Unfortunately that method requires my device to already be working -_- the search goes on.
not_so_optimustic said:
I didn't manage to get that fix to work as I got errors of "The program can't start because AbdWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem."
HOWEVER
This worked pretty perfectly to fix the u-boot problem. After flashing the three attached images for u-boot, boot, and recovery, the boot process was back to "normal." So I then used "fastboot flash recovery [my cwm file]" and it flashed successfully again, and I'm back to the LG logo with the security error, and not really sure how to get to CWM.
The guide you linked to recommends the offline fix, which is the method I've been having issues with. My goal at this point is to get CWM to start properly so I can flash my ROM from the SD card. However the method to fix the security error involves installing a different recovery (not CWM). So that's where I stand at this point.
I'll do some more research and be back here to report whatever my next screwup happens to be.
EDIT: So I think my security error is due to my bootloader not being unlocked. I will attempt to follow this guide and we'll see how it goes. http://forum.xda-developers.com/showthread.php?t=2221102
EDIT2: The first link says to go here for p769. Unfortunately that method requires my device to already be working -_- the search goes on.
Click to expand...
Click to collapse
What problem are you having with the offline flash? If the problem was that it stops at 15%, that's because you had a jellybean u-boot. The offline should work now.
Sent from my LG-P769 using XDA Premium 4 mobile app
I
kuma82 said:
What problem are you having with the offline flash? If the problem was that it stops at 15%, that's because you had a jellybean u-boot. The offline should work now.
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh! Well. Is it safe to flash CM11 when I have an Ice Cream Sandwich u-boot?
not_so_optimustic said:
I
Oh! Well. Is it safe to flash CM11 when I have an Ice Cream Sandwich u-boot?
Click to expand...
Click to collapse
No
You will get a security error even if your bootloader is unlocked.
Sent from my LG-P769 using XDA Premium 4 mobile app
I installed the stock ROM via the offline fix successfully! It immediately went into a nonstop boot loop of the LG logo, so I turned it off and did a hard reset (volume up + home + power, let go of power after it starts up), which then allowed me to boot into the system.
THANK YOU so much! I am now the happiest person on the planet. Can I buy any of you a beer?
not_so_optimustic said:
I installed the stock ROM via the offline fix successfully! It immediately went into a nonstop boot loop of the LG logo, so I turned it off and did a hard reset (volume up + home + power, let go of power after it starts up), which then allowed me to boot into the system.
THANK YOU so much! I am now the happiest person on the planet. Can I buy any of you a beer?
Click to expand...
Click to collapse
Glad you got it fixed
Sent from my LG-P769 using XDA Premium 4 mobile app
Hi not_so_optimustic, happy to help!
Cheers. Good luck.
Sent from my LG P76020L-EUR-XX unlocked and rooted
I can't repair it by Manufacturing Flash Tool. At 15% near button i see "IFWI successfully flashed... REBOOT" and after 3 mins "[FAILURE] OS flash failure ADB ENUM failed". I tried all of firmvare from asus web, and tried files from this video called zenfone4.5 in comments:
In youtube can find: "zenfone unbrick stuk on usb logo".
MFT LOG:
04/01/15 16:40:19.305 INFO : Manufacturing Flash Tool V 6.0.2 (build on Fri Feb 15 12:04:32 MST 2013)
04/01/15 16:40:19.315 INFO : Loading settings from C:/ProgramData/INTEL/Manufacturing Flash Tool.ini
04/01/15 16:40:19.355 INFO : Using Qt version: 4.8.1
04/01/15 16:40:19.355 INFO : Using XFSTK version: 1.3.6
04/01/15 16:40:19.445 WARNING: Please select a flash file...
04/01/15 16:40:23.811 INFO : Loading Flash file (C:/Users/Mazi/Desktop/gggggg/UL_ASUS_T00Q_WW_4_3_4/zenfoneflash.xml)
04/01/15 16:40:23.811 WARNING: Fail to parse fastboot sequence xml file, now fastboot sequence is restored to default!
04/01/15 16:40:23.811 INFO : Ready to flash!
04/01/15 16:40:37.747 INFO : Port 0/0/1 #0: IFW flash started - SN : FA7C15FFB6325965
04/01/15 16:40:37.747 INFO : Disabling xFSTK wipe out ifwi option
04/01/15 16:40:37.747 INFO : Disabling xFSTK Misc DnX
04/01/15 16:41:13.600 INFO : Port 0/0/1 #0: XFSTK-STATUS SN: FA7C15FFB6325965 Unknown Ack code:baadf00d, aborting ...
04/01/15 16:41:13.600 INFO : Port 0/0/1 #0: XFSTK-STATUS SN: FA7C15FFB6325965 FAIL
04/01/15 16:41:13.600 INFO : Port 0/0/1 #0: XFSTK-STATUS SN: FA7C15FFB6325965 Errors encounter during download. Aborting...
04/01/15 16:41:13.600 INFO : Port 0/0/1 #0: IFW flash success - SN : FA7C15FFB6325965
04/01/15 16:43:39.593 ERROR : Port 0/0/1 #0: Device on port 0/0/1 #0 timeout to enum adb (TIMEOUT = 180)
Please, help me.
mazi1989 said:
I can't repair it by Manufacturing Flash Tool. At 15% near button i see "IFWI successfully flashed... REBOOT" and after 3 mins "[FAILURE] OS flash failure ADB ENUM failed". I tried all of firmvare from asus web, and tried files from this video called zenfone4.5 in comments:
In youtube can find: "zenfone unbrick stuk on usb logo".
MFT LOG:
04/01/15 16:40:19.305 INFO : Manufacturing Flash Tool V 6.0.2 (build on Fri Feb 15 12:04:32 MST 2013)
04/01/15 16:40:19.315 INFO : Loading settings from C:/ProgramData/INTEL/Manufacturing Flash Tool.ini
04/01/15 16:40:19.355 INFO : Using Qt version: 4.8.1
04/01/15 16:40:19.355 INFO : Using XFSTK version: 1.3.6
04/01/15 16:40:19.445 WARNING: Please select a flash file...
04/01/15 16:40:23.811 INFO : Loading Flash file (C:/Users/Mazi/Desktop/gggggg/UL_ASUS_T00Q_WW_4_3_4/zenfoneflash.xml)
04/01/15 16:40:23.811 WARNING: Fail to parse fastboot sequence xml file, now fastboot sequence is restored to default!
04/01/15 16:40:23.811 INFO : Ready to flash!
04/01/15 16:40:37.747 INFO : Port 0/0/1 #0: IFW flash started - SN : FA7C15FFB6325965
04/01/15 16:40:37.747 INFO : Disabling xFSTK wipe out ifwi option
04/01/15 16:40:37.747 INFO : Disabling xFSTK Misc DnX
04/01/15 16:41:13.600 INFO : Port 0/0/1 #0: XFSTK-STATUS SN: FA7C15FFB6325965 Unknown Ack code:baadf00d, aborting ...
04/01/15 16:41:13.600 INFO : Port 0/0/1 #0: XFSTK-STATUS SN: FA7C15FFB6325965 FAIL
04/01/15 16:41:13.600 INFO : Port 0/0/1 #0: XFSTK-STATUS SN: FA7C15FFB6325965 Errors encounter during download. Aborting...
04/01/15 16:41:13.600 INFO : Port 0/0/1 #0: IFW flash success - SN : FA7C15FFB6325965
04/01/15 16:43:39.593 ERROR : Port 0/0/1 #0: Device on port 0/0/1 #0 timeout to enum adb (TIMEOUT = 180)
Please, help me.
Click to expand...
Click to collapse
try erasing the system flashing the whole system through fastboot
as explained below
install:
1) adb link
2) intel usb driver link
3) system.img.gz (v4.3.4) link
steps:
1) download above resources and install intel usb driver,extract adb zip, and put system.img.gz in the 'adb'extracted folder
2) turn off phone and start in droid boot mode(power and+)
3)connect phone to pc
4) run cmd.exe as admin and move to adb extracted folder and type as below
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot reboot-bootloader
fastboot flash system system.img.gz
fastboot flash boot boot.img
fastboot reboot-bootloader
5) factory reset the phone and restart
hit thanks if it helped:good::good::good::good:
I can't do it, because i don't have Droidboot, i have only USB LOGO.
mazi1989 said:
i can't do it, because i don't have droidboot, i have only usb logo.
Click to expand...
Click to collapse
explain what all lead you to this
Ok, I sent my phone to the ASUS service. Admin can close the topic.
Hi everyone!
Just wanted to share some steps in case you brick your Realme.
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANY DAMAGES
Some prerequisites you will need:
mtkclient + python
spft (sp flash tool)
ofp extractor
Your stock rom in OFP format.
Step 1. Download all of the things mentioned above.
Step 1a. Make sure your device is turned off. DO NOT PLUG IT IN.
Step 2. Install mtkclient using the guide on GitHub.
Step 3. Run
Bash:
$ py mtk payload
in your terminal.
Step 3a. When it says ***waiting for device*** hold both volume buttons and plug in your device.
This will enter BROM mode.
Step 4. Extract and open ofp extractor and extract your ofp.
Step 5. Open SPFT and click DOWNLOAD ONLY (do not I MEAN DO NOT PRESS FORMAT ALL.)
Step 6. In scatter, look for your scatter file. It should be (MTxxxxScatter.txt etc) Then select it.
Step 7. Select your auth file if you have one.
Step 8. Press Download and if the progress bar starts going the flash is going. DO NOT UNPLUG.
Step 9. Reboot after it says 'Download Ok'
Step 10. Enjoy your unbricked device!
NOTE In most cases the rom will be for android 10. Update if required through OZIP.
I cannot download with SPFlash. Error 0xC0060001. I'm sure that I have done all steps correctly including this tutorial:
Realme 7 Unbrick
Of corse I'm doing everything with Realme 7 5G RMX2111EU.
I had problems with disabling protection as follows but I think it finally succeeded.
1. bypass_utility-v.1.4.2 gives error
Code:
[2022-05-10 22:53:51.684562] Waiting for device
[2022-05-10 22:53:59.780976] Found port = COM4
[2022-05-10 22:53:59.921376] Device hw code: 0x996
[2022-05-10 22:53:59.921376] Device hw sub code: 0x8a00
[2022-05-10 22:53:59.921376] Device hw version: 0xca00
[2022-05-10 22:53:59.921376] Device sw version: 0x0
[2022-05-10 22:53:59.921376] Device secure boot: True
[2022-05-10 22:53:59.921376] Device serial link authorization: False
[2022-05-10 22:53:59.921376] Device download agent authorization: True
[2022-05-10 22:53:59.921376] Disabling watchdog timer
[2022-05-10 22:53:59.936976] Disabling protection
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win
error: A device attached to the system is not functioning.\r\n\n'
[2022-05-10 22:54:01.028978] Payload did not reply
Press any key to continue . . .
2. mtk-client gives error:
Code:
....Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
3. MTK Meta Utility v37 success
Code:
Waiting for mtk usb device... ok
BootMode : BootRom[COM4]
DriverName : MediaTek USB Port_V1633
DriverPath : usb\vid_0e8d&pid_0003\5&278a3c80&0&2
DriverID : wdm_usb
DriverVersion : 3.0.1504.0
DriverDate : 1-22-2015
InfPath : oem28.inf
ProviderName : MediaTek Inc.
Connecting to BootROM......
● Chipset MT6853
● Identifier Dimensity 720/800U 5G
● Info 8A00_CA00_0000_Mouton
● MEID:3EFFEA531AB22A57AB0240D8421E92B4
● SecCFG SBC+SDA
Disable BRom protection...
MTK Auth Disable(SLA/DAA) success!
now you can use SP Flash Tool or any MTK Tool
4. MTK Auth Byoass Tool v6.0.0.1 success
Code:
Waiting for mtk usb device... ok
BootMode : BootRom[COM4]
Sync with bootrom started...
● Chipset MT6853:Dimensity 720/800U 5G
● Code Mouton
● Hw Sub 8A00
● HW Ver CA00
● SW Ver 0000
● SecCFG SBC+SDA
Disable brom protection.
Bypass Payload ACK = 0xa1a2a3a4
MTK Secure Boot Bypasss success!
now you can use SP Flash Tool or any MTK Tool
czaroslaw said:
I cannot download with SPFlash. Error 0xC0060001. I'm sure that I have done all steps correctly including this tutorial:
Realme 7 Unbrick
Of corse I'm doing everything with Realme 7 5G RMX2111EU.
I had problems with disabling protection as follows but I think it finally succeeded.
1. bypass_utility-v.1.4.2 gives error
Code:
[2022-05-10 22:53:51.684562] Waiting for device
[2022-05-10 22:53:59.780976] Found port = COM4
[2022-05-10 22:53:59.921376] Device hw code: 0x996
[2022-05-10 22:53:59.921376] Device hw sub code: 0x8a00
[2022-05-10 22:53:59.921376] Device hw version: 0xca00
[2022-05-10 22:53:59.921376] Device sw version: 0x0
[2022-05-10 22:53:59.921376] Device secure boot: True
[2022-05-10 22:53:59.921376] Device serial link authorization: False
[2022-05-10 22:53:59.921376] Device download agent authorization: True
[2022-05-10 22:53:59.921376] Disabling watchdog timer
[2022-05-10 22:53:59.936976] Disabling protection
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win
error: A device attached to the system is not functioning.\r\n\n'
[2022-05-10 22:54:01.028978] Payload did not reply
Press any key to continue . . .
2. mtk-client gives error:
Code:
....Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
3. MTK Meta Utility v37 success
Code:
Waiting for mtk usb device... ok
BootMode : BootRom[COM4]
DriverName : MediaTek USB Port_V1633
DriverPath : usb\vid_0e8d&pid_0003\5&278a3c80&0&2
DriverID : wdm_usb
DriverVersion : 3.0.1504.0
DriverDate : 1-22-2015
InfPath : oem28.inf
ProviderName : MediaTek Inc.
Connecting to BootROM......
● Chipset MT6853
● Identifier Dimensity 720/800U 5G
● Info 8A00_CA00_0000_Mouton
● MEID:3EFFEA531AB22A57AB0240D8421E92B4
● SecCFG SBC+SDA
Disable BRom protection...
MTK Auth Disable(SLA/DAA) success!
now you can use SP Flash Tool or any MTK Tool
4. MTK Auth Byoass Tool v6.0.0.1 success
Code:
Waiting for mtk usb device... ok
BootMode : BootRom[COM4]
Sync with bootrom started...
● Chipset MT6853:Dimensity 720/800U 5G
● Code Mouton
● Hw Sub 8A00
● HW Ver CA00
● SW Ver 0000
● SecCFG SBC+SDA
Disable brom protection.
Bypass Payload ACK = 0xa1a2a3a4
MTK Secure Boot Bypasss success!
now you can use SP Flash Tool or any MYKI Tool
Click to expand...
Click to collapse
What more.info about the error code do you have? Also are you on windows because spft buggy on linux
BROM ERROR : STATUS_BROM_CMD_STARTCMD_FAIL (0xC0060001)
Windows 7
SP_Flash_Tool_v5.2208_Win
czaroslaw said:
BROM ERROR : STATUS_BROM_CMD_STARTCMD_FAIL (0xC0060001)
Windows 7
SP_Flash_Tool_v5.2208_Win
Click to expand...
Click to collapse
Then you haven't bypassed brom, try mtkclient again and don't unplug your device
Mtk client gives error: Preloader - [LIB]: ←[31mStatus: Handshake failed
Install mtk drivers and Libusb, also pyserial
All above mentioned was installed. I tried different pack from droidwin and I get this:
Code:
Port - Device detected :)
Preloader - CPU: MT6853(Dimensity 720 5G)
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - CQ_DMA addr: 0x10212000
Preloader - Var1: 0xa
Preloader - Disabling Watchdog...
Preloader - HW code: 0x996
Preloader - Target config: 0xe5
Preloader - SBC enabled: True
Preloader - SLA enabled: False
Preloader - DAA enabled: True
Preloader - SWJTAG enabled: True
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: True
Preloader - Mem write auth: True
Preloader - Cmd 0xC8 blocked: True
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca00
Preloader - SW Ver: 0x0
Preloader - ME_ID: 3EFFEA531AB22A57AB0240D8421E92B4
Preloader - SOC_ID: DAA82CB9D5E03916132A0BE2A479C0CC0FFD2B10
1E00173F9EA9FCB44C88FC8E
PLTools - Loading payload from mt6853_payload.bin, 0x264 bytes
PLTools - Kamakiri / DA Run
Kamakiri - Trying kamakiri2..
Kamakiri - Done sending payload...
PLTools - Successfully sent payload: D:\Apk\MTK Bypass Tools\mtkclient-main\mtkc
lient\payloads\mt6853_payload.bin
Be sure to use in SPFT, in connection check USB full speed, and in general settings, uncheck the options Check LIB DA Match and Storage Life Cycle Check.
If this doesn't work, try to flash only preloader firstly, and then flash the rest, upload some screenshot if the error persists.
That means it worked
Ok. Bootloader is unlocked but now I have dm-verity corrupted.
I cannot enter recovery mode. Some error flashes on screen and immediately reboot. I cannot even read this. I have found that it might be:
the serial is not matched
fastboot_unlock_verify failed
I cannot enter fastboot mode. It gives:
Orange state
The device is unlocked and cannot be trusted
and then restarts
Normal boot gives:
dm_varity corruption
Your device is corrupted
It won't be trusted and may not work properly
Press power button to continue
Then pressing power button boots into system correctly and the phone is working.
How to get rid of these errors? How to recover access to recovery and fastboot mode? Should I flash some partitions again from stock formware?
Should I install PBRP using mtkclient as in this guide?
Install TWRP Recovery without using Fastboot Mode [MediaTek]
And then should I root it using patched Magisk as follows?
Root MediaTek Devices without using Fastboot Mode [via MTK Client]
There is some info about patched version of Magisk for MTK devices. Should I use it?
do
Code:
fastboot flash --disable-verity --disable-verification vbmeta {your vbmeta.img}
czaroslaw said:
Ok. Bootloader is unlocked but now I have dm-verity corrupted.
I cannot enter recovery mode. Some error flashes on screen and immediately reboot. I cannot even read this. I have found that it might be:
the serial is not matched
fastboot_unlock_verify failed
I cannot enter fastboot mode. It gives:
Orange state
The device is unlocked and cannot be trusted
and then restarts
Normal boot gives:
dm_varity corruption
Your device is corrupted
It won't be trusted and may not work properly
Press power button to continue
Then pressing power button boots into system correctly and the phone is working.
How to get rid of these errors? How to recover access to recovery and fastboot mode? Should I flash some partitions again from stock formware?
Should I install PBRP using mtkclient as in this guide?
Install TWRP Recovery without using Fastboot Mode [MediaTek]
And then should I root it using patched Magisk as follows?
Root MediaTek Devices without using Fastboot Mode [via MTK Client]
There is some info about patched version of Magisk for MTK devices. Should I use it?
Click to expand...
Click to collapse
If it says DM-verity error, reflash with spft and on mtkclient, relock BL by using
Code:
Py mtk da seccfg lock
I cannot enter fastboot mode so I cannot use fastboot flash.
Second advice: I do not want to lock bootloader.
If you are able to boot to stock, do ADB reboot fastboot
Does not work. It gives the same as VolUP+PWR. Orange state message and reboot.
I cannot enter fastboot in any way.
Should I flash something in brom mode? Recovery partition? Something else to get rid of dm_varity?
Reflash firmware then try, idk this hasn't happened to me
Also send the link of the firmware U got
I have RMX2111_11_C.11. Updated via OTA. I cannot find such version firmware file.
The newest I found is:
RMX2111GDPR_11_C.09 EDL mode
czaroslaw said:
I have RMX2111_11_C.11. Updated via OTA. I cannot find such version firmware file.
The newest I found is:
RMX2111GDPR_11_C.09 EDL mode
Click to expand...
Click to collapse
Relock bootloader and try using this to reunlock bl