[Q] Phone stuck in emergency mode after update - Optimus One, P500, V General

I have a problem with my lg optimus one P500. I had the void #echo custom rom installed and after a week i had tried to make the official update from LG with the LG Mobile Tool.
The problem is that now the phone is stuck in the emergency mode and it not get reconized by the pc. I had tried to use kdz uploader but still not reconized.
The KDZ log :
[R&D Test Tools Log File]
09:30:14 : Launching SW update
09:30:14 : Unpacking KDZ
09:30:16 : KDZ file extraced
09:30:17 : Files were extracted.
09:30:17 : LGMobileDL Load.
09:30:17 : Port = -1
09:30:17 : Connecting to phone
09:30:22 : PHONE WAS NOT FOUND!
09:30:24 : ===FINISHED===
I tried with the combination of keys "wolume up+return+power" and plug the usb cable but the phone still not reconized.
Does anyone know a solution for this problem.

Arrrrghhh , disable in Device manager , under Modems > LGE Virtual Modem . Done

i have the same problem..I already have disabled th lge virtual modem but still nothing happens..help us pls

^^ LGE virtual modem needs to be disabled before flashing.
@OP, status of your mobile? it turns on or shows any activity?

kly91 said:
i have the same problem..I already have disabled th lge virtual modem but still nothing happens..help us pls
Click to expand...
Click to collapse
Dud check the bricked phones thread here on XDA and read it adequately and follow every step .
I recommend you reinstall your phone drivers, delete every other phone driver you have on your pc , use a cleaner ( ccleaner or something ) , disable the modems again and then pray

Remember for the future, read before flashing. And now good luck !!

Related

[Resolved] TYPE_WPARAM_UPGRADE_ERROR in LG Flash Tool

I got this TYPE_WPARAM_UPGRADE_ERROR when I try to flash back to Stock rom using LG FlashTool. Below is the error log
wParam : 13, lParam = 46
wParam : 13, lParam = 47
wParam : 100, lParam = 3146241
MODEL DLL Event : (100, 3146241)
Step : TYPE_WPARAM_UPGRADE_ERROR
CleanModelDll() : Free Model.dll
_DetachDLL Call
_DetachDLL Call End
Page_Error ºÎºÐÀÔ´Ï´Ù
¿©±â´Â Retry ºÎºÐÀÔ´Ï´Ù
After many research in Google and inspiration on XDA, I found some many general suggestion as well as my own root cause.
General suggestion:
Turn off Antivirus
Flash in Windows XP
Check the KDZ file size, for G2 stock rom it should be around 2GB. If you downloaded a 900MB KDZ file you know you're 1G short.
Reinstall LG USB Driver, LG Flash Tool etc
Change the LG device in Device manager to COM port 41 or COM port 4 before connecting to PC.
My own root cause:
Mine is Korean version F320L. I previously rooted and flashed to a custom ROM which is based in D802 using CWM. When I try to flash back to Stock rom using LG Flash Tool, I got the "TYPE_WPARAM_UPGRADE_ERROR". In the bootloader screen on my phone it shows rooted. Since I tried all of the F320L/F320K/F320S stock rom and they all failed, I know it is not an corrupt file issue.
So I wonder if I need to unroot my phone in order to get past the error. I started by flashing to another rom which is based on the F320K rom using CWM. Since the F320L rom comes without root, I go back to the bootloader screen and check the status on the phone. Although it still shows rooted, this time the LG Flash Tool can get past the error message and finished flashing the F320K rom.
Conclusion:
The existing Rom installed on the phone can affect LG Flash Tool which seems to compare the version of the Rom you try to flash against the version of the Rom currently installed. I was lucky that I got CWM to flash back to the right type of rom to get the job done.
I do think that the LG Flash Tool really sucks as compared to Samsung Odin (I was a Samsung guy previously owning 3 Galaxy S series phone) which won't even ask what crack you're running on your phone. And from my limited experience flashing Sony Xperia phones it was just a smooth ride without error. LG really need to open up their policy on rooting if they ever want to catch up to their local rival Samsung.
RA017 said:
I got this TYPE_WPARAM_UPGRADE_ERROR when I try to flash back to Stock rom using LG FlashTool. Below is the error log
wParam : 13, lParam = 46
wParam : 13, lParam = 47
wParam : 100, lParam = 3146241
MODEL DLL Event : (100, 3146241)
Step : TYPE_WPARAM_UPGRADE_ERROR
CleanModelDll() : Free Model.dll
_DetachDLL Call
_DetachDLL Call End
Page_Error ºÎºÐÀÔ´Ï´Ù
¿©±â´Â Retry ºÎºÐÀÔ´Ï´Ù
After many research in Google and inspiration on XDA, I found some many general suggestion as well as my own root cause.
General suggestion:
Turn off Antivirus
Flash in Windows XP
Check the KDZ file size, for G2 stock rom it should be around 2GB. If you downloaded a 900MB KDZ file you know you're 1G short.
Reinstall LG USB Driver, LG Flash Tool etc
Change the LG device in Device manager to COM port 41 or COM port 4 before connecting to PC.
My own root cause:
Mine is Korean version F320L. I previously rooted and flashed to a custom ROM which is based in D802 using CWM. When I try to flash back to Stock rom using LG Flash Tool, I got the "TYPE_WPARAM_UPGRADE_ERROR". In the bootloader screen on my phone it shows rooted. Since I tried all of the F320L/F320K/F320S stock rom and they all failed, I know it is not an corrupt file issue.
So I wonder if I need to unroot my phone in order to get past the error. I started by flashing to another rom which is based on the F320K rom using CWM. Since the F320L rom comes without root, I go back to the bootloader screen and check the status on the phone. Although it still shows rooted, this time the LG Flash Tool can get past the error message and finished flashing the F320K rom.
Conclusion:
The existing Rom installed on the phone can affect LG Flash Tool which seems to compare the version of the Rom you try to flash against the version of the Rom currently installed. I was lucky that I got CWM to flash back to the right type of rom to get the job done.
I do think that the LG Flash Tool really sucks as compared to Samsung Odin (I was a Samsung guy previously owning 3 Galaxy S series phone) which won't even ask what crack you're running on your phone. And from my limited experience flashing Sony Xperia phones it was just a smooth ride without error. LG really need to open up their policy on rooting if they ever want to catch up to their local rival Samsung.
Click to expand...
Click to collapse
I have the same issue you had. I have a 320L phone and I tried the Korean Custom Rom which was based on the Mexican D805 model. It flashed fine but was an old software image and I decided to go back to Korean Stock. It's no taking any Korean images, in fact I had to recover this through fastboot using the Mexican laf.img file just to get Download mode back working.
I'll try your method, thanks.
Would you mind sharing a link to the F320K rom you flashed that got you back to normal please?
Actually, I think this will work just fine.
Download Fix KDZ
http://forum.xda-developers.com/showthread.php?t=2511256
Just change the build.prop should make you pass the FlashTool error.
Hello i have D802A and same problem , can you help me? i was try everything, don´t found build.prop in phone.
Has anyone got this working on Win7?
patkitch said:
Has anyone got this working on Win7?
Click to expand...
Click to collapse
The LG flash tool? Yeah. Worked right out of the gate for me. Win7 64 SP1. Far easier than getting the drivers working with my Gnex back when it first came out.
Ugh, It keeps crapping out for me on Win8.1 and Win7 x64 SP1. I'm installing XP on an old laptop now.
Same error on a fresh install of XP. It also seems that I can't get into TWRP now either. Is my phone bricked?
Thank you! I had this same error! Turned out the ROM I had flashed was causing the issues. flashed a rom that wouldn't boot and this allowed me to finish the firmware update. Thanks again!
Any idea how to solve this without recovery access?
I can't really use the fixkdz since I have a D802.
MaXmeOliver said:
Any idea how to solve this without recovery access?
I can't really use the fixkdz since I have a D802.
Click to expand...
Click to collapse
Just a quick update. The reason I got this was that my .kdz file was corrupt. Just downloaded it again and it worked like a charm.
Make sure your work directory is correct in the test tool and don't put your .kdz file on a network drive.
ı don't understand
WHAT DO I AM??? My device is a D802TR (D802)..

[Q] install bad Flash ROM and return to good

hi,
option is somehow wrong to copy prerecorded FLASH ?
somehow I managed to make the LG E410 LG P700 software and as I wrote in another post can not get any method to the emergency - recovery mode . The only thing that works is the upgrade mode but Windows has completed installing the drivers and everything falls .
I also tried to root via SuperOneClick , different packages of uploads and perhaps all instructions .
I am trying to play either P700 Tu flash any other , best I needed V10C - 00 or even compel even the official or unofficial any program to the phone to flash at least something of what I would get with a normal phone usage.
I do not allow any possibility superuser on your mobile phone .
If it was not my favorite and only mobile Forget him, but the other has not and will not have , so thanks for the advice .
I used to have programs KDZ updater SW - SW updater2014 KDZ - Win7 / 32 - antivirus firewall all off -windows Enabler 1.1 is ON and shttp set according to instructions on the 100 / 9002. also disconnect the LAN and install the offline and using VB script.
am I missing something somewhere .
Fanda.l said:
hi,
option is somehow wrong to copy prerecorded FLASH ?
somehow I managed to make the LG E410 LG P700 software and as I wrote in another post can not get any method to the emergency - recovery mode . The only thing that works is the upgrade mode but Windows has completed installing the drivers and everything falls .
I also tried to root via SuperOneClick , different packages of uploads and perhaps all instructions .
I am trying to play either P700 Tu flash any other , best I needed V10C - 00 or even compel even the official or unofficial any program to the phone to flash at least something of what I would get with a normal phone usage.
I do not allow any possibility superuser on your mobile phone .
If it was not my favorite and only mobile Forget him, but the other has not and will not have , so thanks for the advice .
I used to have programs KDZ updater SW - SW updater2014 KDZ - Win7 / 32 - antivirus firewall all off -windows Enabler 1.1 is ON and shttp set according to instructions on the 100 / 9002. also disconnect the LAN and install the offline and using VB script.
am I missing something somewhere .
Click to expand...
Click to collapse
Is this the right ROOT the phone or not?

[KDZ] [TOT] [L5 II] Stuck at LG Screen

Hello,
I've got a LG L5 II that is stuck at LG screen. This happen because maybe I've deleted the update of google apps in order to have disk space left.
I've done a lot of research before posting a new thread but now, I ask for your help.
Useful Information :
LG L5 II E460, firmware stock, not rooted, firmware V10F
Try on USB 3.0 and USB 2 with cable microUSB -> USB because computer is an ASUS Transformer
Connection information in device manager :
Normal boot : MT65xx Android Phone
Download mode : LG AndroidNet Phone
Recovery mode : Android laying on the floor with red exclamation mark but nothing happen.
Guide used and results :
Official LG method :
Power on : when connected, still waiting for connection in the LG Update window
Download mode : Connection OK but when trying to upgrade from recovery, failed @ 4 or 5 %, phone disconnected
LG Flashtool 2014 :
Download mode : failed @ 4 or 5 %, phone disconnected
TOT Method: Unable to find TOT file but trying with bin and dll from kdz firmware
Download mode : Error at step flashing SCI.
If possible, I'd like to do a normal flash without losing data on the internal. I know I can do it but I need your help, please
If more information wanted, do not hesitate to ask, I'm trying to be the more accurate possible. Sorry for my English, it''s not my native language.
Thanks
I'm trying to get the tot file from my firmware KDZ.
Extracting KDZ give me DLL and bin file.
I don't know what to do with this bin file. Is it possible to convert it in tot file ?
Thanks
Midask said:
I'm trying to get the tot file from my firmware KDZ.
Extracting KDZ give me DLL and bin file.
I don't know what to do with this bin file. Is it possible to convert it in tot file ?
Thanks
Click to expand...
Click to collapse
any luck on recovering, im suffering the same. but i formated my system and now when i flash kdz the phone boots but goes to an android guy with a red triangle over its tummy
Hi !
I was hoping an answer but it isn't the case.
I'll try to help you, I've spent a lot of hours to recover my phone.
Try to follow this How-to :
http://forum.xda-developers.com/showthread.php?t=2409308
-----------------------
About my problem, I think I don't have any possibilities. Even a factory reset fail.
USB debugging not activated --> Trying by ADB --> ADB need to install Superuser.apk in /data/local/tmp --> This directory has been erased because I've tried a complete flash and all my data are gone but my phone is still bricked.
Trying to Root to flash recovery --> USB debugging not activated --> Unable to root my phone
KDZ Updater fail (maybe because of USB debugging not enabled ?)
I think I'm f**ed (sorry for this bad word but I don't see any possibilites ...)
----------
Dear mudster, if I can help you, I will do my best
Midask said:
Hi !
I was hoping an answer but it isn't the case.
I'll try to help you, I've spent a lot of hours to recover my phone.
Try to follow this How-to :
http://forum.xda-developers.com/showthread.php?t=2409308
-----------------------
About my problem, I think I don't have any possibilities. Even a factory reset fail.
USB debugging not activated --> Trying by ADB --> ADB need to install Superuser.apk in /data/local/tmp --> This directory has been erased because I've tried a complete flash and all my data are gone but my phone is still bricked.
Trying to Root to flash recovery --> USB debugging not activated --> Unable to root my phone
KDZ Updater fail (maybe because of USB debugging not enabled ?)
I think I'm f**ed (sorry for this bad word but I don't see any possibilites ...)
----------
Dear mudster, if I can help you, I will do my best
Click to expand...
Click to collapse
thanks bro we need more people like you in the world
I am going nuts. The recovery crashes at 4 - 5%

How to Root Lenovo A7020a48 & Fix IMEI errors

Hello , Guys
Since you all probably know, Lenovo A7020a48 has Android 6.0 Marshmallow which cannot be rooted because of the following :
1 - We got a locked bootloader, we can't flash or boot into custom recoveries and sadly at the moment I couldn't find a way to unlock it.
2 - We don't even have a custom recovery made for that model yet, I tried different version of TWRP for A7020a40 ~ A7020a46 models and they all crashed upon booting to them.
3 - Kingroot and similiar apps can't root Android 6.0.
So the only way to root your phone would be to downgrade it to Android 5.1 Lolipop which is easy.
Here is download links for the stock roms :
A7020a48_LL_S125_160419_ROW.rar.7z
A7020a48_S259_160721_ROW.7z
When you finish downloading please don't forget that we are going to use the SP Flash Tool provided in the rom as only that version "SP_Flash_Tool_5.1552.00" worked for me with no errors however with latest versions i got problems.
Obviously you are going to install the USB drivers and CDC drivers located at the "DRV_Tools" folder in the rom you downloaded.
after installing the drivers correctly turn off your phone, open SP flash tool, and choose the scatter file located at : "\SW\target_bin\MT6755_Android_scatter.txt" and then choose "Download Mode" then wait for it to finish checking the files, then click on the download button on the top left corner.
Then connect your device and wait for it to detect the device .
Wait until the flashing is complete Then After the green circle appears, simply disconnect your phone and boot into system normally.
Note: You might see a black box in the bottom left corner saying "efuse flash done or similar stuff" don't worry about it" it won't appear again however if you got an error saying "DL image failed" then you did something wrong repeat the previous steps again and make sure you choose everything correct especially your rom.
Now to the last part, finish the first time setup screens by skipping most of them and DO NOT UPDATE YOUR SYSTEM AT ALL
if you got a notification to update, simply ignore it or press cancel, and open google chrome, download king root and wait for it to simply root you phone.
Congratulations that's the first part for rooting your phone.
Now to Fixing Your IMEI
Simply Enable USB debugging in options and enable OEM unlocking.
Then power off your phone.
Download this tool : MauiMETA_v9.1635.23.rar
Yes Again it has to be that specific versions, with other versions i couldn't connect to my device however with this version i could.
Extract it to a random location on your pc and MauiMeta.exe and click on options and enable "enable composite kernel usb (adb)" then click on reconnect.
Now you have to connect your device with usb and turn it on, don't worry MauiMeta will change the boot to META mode automatically after it starts booting leave it as it's and wait for the tool to connect to your phone.
***After it connects simply choose IMEI download and a new window should appear, first click on upload from flash button then click yes to retrieve the modem file from your phone, then simply type your IMEI ( Please note that changing your IMEI is illegal however you should only use this method to fix your IMEI not change it ! , you have been warned)
Note : IMEI numbers should be 15 numbers however with MauiMeta you should only type the first 14 number as the 15th number is only a checksum number and will be added automatically.
After typing the IMEIs and checking them simply click on download to flash.
After it says "flashing is successful" then close the window and click Disconnect, and your phone should turn off automatically and you should start it up again.
*** Note : If you have a corrupted NVRAM file on your phone then you are lucky since that rom comes with the modem db file as well to fix NVRAM issues, simply click "Change NVRAM database file" then click No to choose the file, The file exists in the ROM package you downloaded earlier in the following location : "SW\modemdb\MDDB_InfoCustomApp....etc.EDB" and continue the rest of the steps normally.
Please Note that I won't provide support for this, I have only created this tutorial to save time for other people and I'm not expert yet to fix all the problem you may face however after following these steps i managed to root my device and even fix the invalid imei errors i got.
Also if you found errors in my thread or mistakes Please let me know so i can fix them.
Good luck and Don't hard brick your phone XD
I get this error in SP FLASH TOOL 5.1552.00- STATUS_SEC_PL_VFY_FAIL (-10*****)
Any idea ?
Error coming?
i got the same error in SP FLASH TOOL 5.1552.00- (BROM ERROR : STATUS_SEC_PL_VFY_FAIL (-1073610746))
nishkarshxda said:
i got the same error in SP FLASH TOOL 5.1552.00- (BROM ERROR : STATUS_SEC_PL_VFY_FAIL (-1073610746))
Click to expand...
Click to collapse
Use This Version Of Flash tool enable usb and storage checksum hit download ( Use different usb port better use backside of CPU )
Sp-flash-tool-V5-1548
10000% Working
mobile not getting switched on after downgrading
Hi, I tried to flash my Lenovo vibe K5 note (a7020a48 4 GB RAM). It was done without any error but I couldn't switch on my mobile nor it was detected in my computer. Please help me
Bro i download and flashed successfully but phone cant turn on but i flashed again marshmallow phone will turn on...Why lollipop cant boot... Second link for rom is lollipop or not
Any proof?
Bro where did you get these two rooms from? Tell us the source. Otherwise, how will we know?
after flash mobile no on anybody can u help me to how to flash 5.0 in lenovo k5 note
It worked great thanks .......though minor glitches may occur such as not playing any sound and not supporting JIO sim card. These can be fixed by System Updating your phone to the latest version preferably through a sound wifi connection.

[SOLVED] Need help to unbrick an Archos 50 Diamond (ac50da)

Hi all,
I recently got my hands on a screen-damaged Archos 50 Diamond (ac50da) running the latest stable stock Android 4.4.4 ROM (I didn't know that an Android 5.1 preview was available here : https://blog.archos.com/fr/lollipop-en-version-beta-sur-le-50-diamond/).
I bricked it by doing the following :
- Trying to install @phhusson TWRP from here : https://twrp.me/archos/archos50diamond.html, without upgrading to 5.1 first (as explained here : https://forum.xda-developers.com/ar...ment/twrp-support-thread-archos-twrp-t3468677).
This did not work, as when trying to enter recovery mode by holding VolumeUp while powering up the phone would now bring up a totally green, then totally red screen, but nothing else. No device is detected if I plug it in a computer (either Linux or Windows).
- Booting (not flashing yet) CWM from here : http://www.arctablet.com/blog/forum...50-diamond-root-procedure-recovery-cwm-v6051/
For some reason, I ended up rebooting (without installing CWM or anything else). But before rebooting, CWM warned me that my ROM wasn't rooted, and offered to install the su binary in /system/xbin/su. That's were I met my doom, because the device would then no longer boot.
- If I power up the device, the Archos logo shows up, then a black screen. Plugging the device on a Windows computer shows a dozen data drives, and the devices itself identified as QHSUSB_BULK.
- I thought of using QFIL (Qualcomm File Image Loader) to re-image the device : https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
I managed to get my hands on a stock firmware image (prog_emmc_firehose_8936.mbn or validated_emmc_firehose_8936.mbn) by paying here : https://firmware.gem-flash.com/index.php?a=browse&b=file-info&id=110067 but QFIL won't flash it as I don't have a driver for QHSUSB_BULK.
- However, I'm unable to find a proper driver for that device. I found several Qualcomm drivers, either for QHSUSB_BULK or the (apparently older) QDLOAD, but none of them include definitions for the Archos 50 Diamond.
- The device's USB identification is the following : USB\VID_05C6&PID_9057&MI_00
VID (Vendor ID) 05C6 = Qualcomm
PID (Product ID) 9057 = ??? (should be the Archos 50 Diamond but is not referenced anywhere)
MI (Master Interface) = ??? (no idea what that means)
- Other findings :
The .mbn files refer to a Qualcomm Snapdragon 610 MSM8936
Inside the stock image is an android-info.txt file that reads "board=msm8916"
So, can you guys help me out here ?
I think that finding a proper QHSUSB_BULK driver for VID_05C6&PID_9057 should be enough, but I'm open to any suggestion.
Thanks !
I think I found a driver for that device here : https://driverpack.io/fr/hwids/USB\VID_1D9C&PID_9057&MI_04
It's for a "Sonim XP5 HS-USB NMEA 9057", but whatever.
However, after installing the driver (just uncompress it using 7-zip), QFIL fails when trying to download the firmware image with "failed to switch to EDL mode" (EDL = emergency download).
Anyone has a better idea*?
VICTORY !!!
When trying to power off/reboot the device, I noticed that it could still boot in fastboot mode, by holding VolumeUp + power until the screen turns green, then release the buttons before the screen turns red.
I could then boot again in CWM (still unable to flash it though), and re-install a stock ROM from the manufacturer site : https://www.archos.com/us/support/support_tech/downloads.html?type=s&rlist=1&devid=240
Phew ! At last !
And now to try and install the 5.1 beta update…
Hello! I have Archos diamond 50 in qd 9008 mode always. Can you upload firmware that you download from gemflash? I want try unbrick device.
IDLeon said:
Hello! I have Archos diamond 50 in qd 9008 mode always. Can you upload firmware that you download from gemflash? I want try unbrick device.
Click to expand...
Click to collapse
Do you have any place I can upload it to ?
Hi.
I have the same problem and I cant find the flash file.
Can you please give me the .mbn flash file (prog_emmc_firehose_8936.mbn or validated_emmc_firehose_8936.mbn) ?
Thank you
karim-ps said:
Hi.
I have the same problem and I cant find the flash file.
Can you please give me the .mbn flash file (prog_emmc_firehose_8936.mbn or validated_emmc_firehose_8936.mbn) ?
Thank you
Click to expand...
Click to collapse
Do you have any place I can upload it to ?
Maybe Google drive or wetransfer.com
Thank you
karim-ps said:
Maybe Google drive or wetransfer.com
Thank you
Click to expand...
Click to collapse
If you can give me access to one of yours, I'll do it ASAP. I don't have one myself and don't plan to.
breversa said:
If you can give me access to one of yours, I'll do it ASAP. I don't have one myself and don't plan to.
Click to expand...
Click to collapse
I sent it through a private message.
Thank you
For anyone interested : I have some stock firmware files, but nowhere to store them (I'm not looking to register to yet another service). If you're willing to host them, please send me a private message. Thanks !
Thank you
breversa said:
For anyone interested : I have some stock firmware files, but nowhere to store them (I'm not looking to register to yet another service). If you're willing to host them, please send me a private message. Thanks !
Click to expand...
Click to collapse
I'm in the process of uploading the 50_Diamond.rar stock firmware to https://androidfilehost.com/
I'll give the link when it's done. Feel free to ping me if I forget !
Okay, here it is : https://www.androidfilehost.com/?w=files&flid=319661

Categories

Resources