Related
Whenever I try to run the RUU, I get this:
----------
usb
v2.01
upgrade
radio stack
please wait
-----------
Nothing will go, No % from PC and from Device. After some minutes, I get the 114 Error.
I tried to downgrade the boot and Now I ve v1.01 but still I cant manage to get it Upgraded.I tried two Roms with no Lucky.
Any Idea???
Ok, try going into bootloader mode and then try the upgrade. the task 28 55aa formats the ROM(including extended ROM). It however, does not formats the radio ROM
There was no need to downgrade the bootloader unless you're using <v1
What I ll suggest you is flash some OS.nbf first. Then, grapple with the radio stack thingy
kdskamal said:
Ok, try going into bootloader mode and then try the upgrade. the task 28 55aa formats the ROM(including extended ROM). It however, does not formats the radio ROM
There was no need to downgrade the bootloader unless you're using <v1
What I ll suggest you is flash some OS.nbf first. Then, grapple with the radio stack thingy
Click to expand...
Click to collapse
Thanks for the advice.
Boot was 2 before.
I tried to put in the folder one by one the 3 files but still my upgrade bar or flashing % cant run. The device screen will change showing as if the flash is running but no % and ten min or so i will get Error 114.
I tried all reset but still cant get it run. But the Bootloader updater exe can be load in the device .
??? Any other Idea???
I m still facing the same problem.
Can someone explain me this log:
----------------------------------
03:35:02:343 [msg] : Version : [2.11].
03:35:02:343 [msg] : Config Info : [857873],[1],[0],[0],[1],[0],[0],[1].
03:35:06:421 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.
03:35:10:484 [msg] : Disconnect ActiveSync .... [2]
03:35:10:484 [msg] : Start Get Connect Port.
03:35:10:656 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
03:35:32:140 [msg] : Get Device Backup ID.
03:35:32:140 [msg] : Device BL VER : [1.01 ] [].
03:35:32:140 [msg] : Device ID Is Incompatible.
03:35:32:140 [msg] : Update Image. CE : [4], MSystem : [2], Radio : [1]
03:35:34:421 [msg] : Check Ac in BL mode. AC : [1]
03:35:35:921 [msg] : IsBL. BL : [1]
03:35:36:000 [msg] : =============================================
03:35:36:000 [msg] : START UpdateRadio !
03:35:45:000 [msg] : Check Radio Level 0 [704].
03:35:46:578 [msg] : RUpgrade 0 : 0 Start.
03:40:37:312 [err] : RWipe Data Error.
03:40:37:781 [err] : BL UpdateRadio Error.
03:40:37:781 [msg] : START UnInitialization !
03:40:37:796 [msg] : END UnInitialization !
03:40:37:828 [msg] : IsBL. BL : [1]
--------------------------------------------
I m looking also for bootloader 2.01 for the Universal or boot 1.04
Thanks.
blaiseid said:
I m still facing the same problem.
Can someone explain me this log:
----------------------------------
03:35:02:343 [msg] : Version : [2.11].
03:35:02:343 [msg] : Config Info : [857873],[1],[0],[0],[1],[0],[0],[1].
03:35:06:421 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.
03:35:10:484 [msg] : Disconnect ActiveSync .... [2]
03:35:10:484 [msg] : Start Get Connect Port.
03:35:10:656 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
03:35:32:140 [msg] : Get Device Backup ID.
03:35:32:140 [msg] : Device BL VER : [1.01 ] [].
03:35:32:140 [msg] : Device ID Is Incompatible.
03:35:32:140 [msg] : Update Image. CE : [4], MSystem : [2], Radio : [1]
03:35:34:421 [msg] : Check Ac in BL mode. AC : [1]
03:35:35:921 [msg] : IsBL. BL : [1]
03:35:36:000 [msg] : =============================================
03:35:36:000 [msg] : START UpdateRadio !
03:35:45:000 [msg] : Check Radio Level 0 [704].
03:35:46:578 [msg] : RUpgrade 0 : 0 Start.
03:40:37:312 [err] : RWipe Data Error.
03:40:37:781 [err] : BL UpdateRadio Error.
03:40:37:781 [msg] : START UnInitialization !
03:40:37:796 [msg] : END UnInitialization !
03:40:37:828 [msg] : IsBL. BL : [1]
--------------------------------------------
I m looking also for bootloader 2.01 for the Universal or boot 1.04
Thanks.
Click to expand...
Click to collapse
What Rom are you flashing and what device do you have?
It would appear you are flashing the wrong Rom for your device.
If you are sure the Rom is for your device then try either flash from BootLaoder with NO-ID flash tool or SuperCid your device.
Cheers,
Beast
beast0898 said:
What Rom are you flashing and what device do you have?
It would appear you are flashing the wrong Rom for your device.
If you are sure the Rom is for your device then try either flash from BootLaoder with NO-ID flash tool or SuperCid your device.
Cheers,
Beast
Click to expand...
Click to collapse
Thanks for your Support mate.
-The Device is an I-Mate Jasjar.
-It was on NO GSM
-Was switching On fine showing Orange Brand.(Was Longtime Flashed to M5000)
-After Mtty (task 28 55aa) No more Booting but could show Bootloader serial -v2.01 if i put it in that mode. It could enter Hard Reset (press 0 for factory restore or X to exit if i try hard rest "after mtty").
-When trying to upload the Jasjar RUU nothing happens.
** Now the device cant enter bootload mode any more.**
I m confused.
So, long story short - I hard bricked my phone by trying to flash .bin files when they should have been .img files (rookie mistake). Anyways, once i flashed those the screen went black and the phone would not respond to anything. When i plugged the phone in it showed up as Qualcomm 9008 blah blah blah so i followed this method: http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853. I was able to flash some of my partitions but then suddenly the screen changed to this:
http://i.imgur.com/G0n16LP.jpg
I believe it was after flashing tz. Regardless, I could not flash any more partitions.
So i plugged in my battery and reconnected it to my computer and it shows up as this: http://i.imgur.com/zRKaNZC.jpg. For those who can't see it it shows up as LGE AndroidNet USB Serial Port. It also shows up as LGE AndroidNet USB Modem. Any idea on how to fix my phone from this? I've installed the Qualcomm Drivers as well as the ADB universal drivers and the LG Drivers for my phone. Using LG Mobile Support Tool the flashing goes until it says it can't connect to the phone. QPST can't see it, LG Flash Tool gives me "Model Information Check Fail" and any KDZ Flashing tool can not flash it.
I heard talk about shorting capacitors to put it into 9006 mode in order to see the partitions. Does anyone know which capacitors?
Any help would be great considering there is not a whole lot of (free) information out there on this.
Click to expand...
Click to collapse
So I fixed my phone. For everyone wondering how to do it follow this thread: http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091.
If you're stuck in the serial mode you have to short the pins on your emmc. Short then pins as described in the above thread and then plug your usb in. Then follow the steps in the thread and flash.
Man I'm in the same boat as you. I couldn't get the Qualcomm tool to work though.
Nothing seems to be working at the moment and neither flashtool or anything else seem to be finding my device.
I'd like to avoid sending it to LG if I can as I need this phone.
Have you had any luck at all?
Look's like your phone diag port. May need your msl/spc to get qualcomm tool to work.
fergie716 said:
How to Get your MSL/SPC
**NOTE** This will only work if your phone is able to turn on
Make sure you have the LG Drivers Installed on your computer (link is in 1st post for that)
Open up your dialer and enter ##DIAG#
Enable DIAG Mode
Connect your phone to your computer
On your phone change the USB Connection type to Charge Only (pull down your statusbar and click on USB Connected)
Download CdmaDevTerm on your computer(I prefer this version)
Extract the CdmaDevTermZip
Inside the extracted folder double click on the cdmaTerm file to start the application
On the right hand side of the CdmaDevTerm screen select "Scan ports"
Next select the LGE AndroidNet USB Serial Port from the drop down menu (mine was COM6) then click Connect
In the SPC/Lock Options change NV to LG from the drop down menu
Now click Read SPC
Success!
Click to expand...
Click to collapse
This looks like your phone is charging, that might mean your boot or aboot partitions are ok. Or maybe recovery, i'm not sure which one is used for phone off charging.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jcfunk said:
Look's like your phone diag port. May need your msl/spc to get qualcomm tool to work.
This looks like your phone is charging, that might mean your boot or aboot partitions are ok. Or maybe recovery, i'm not sure which one is used for phone off charging.
Click to expand...
Click to collapse
I connected to it (I think) and got the spc number but it doesn't show up in the qualcomm tool/ i don't know what to do with the number haha.
jfedorchuk said:
I connected to it (I think) and got the spc number but it doesn't show up in the qualcomm tool/ i don't know what to do with the number haha.
Click to expand...
Click to collapse
Qualcomm tool, do you mean qpst?
if so you need to add port to server configuration tool. Or maybe try CDMAworkshop.
Have you tried volume + and USB insert?
maybe download or fastboot mode will start
jcfunk said:
Qualcomm tool, do you mean qpst?
if so you need to add port to server configuration tool. Or maybe try CDMAworkshop.
Have you tried volume + and USB insert?
maybe download or fastboot mode will start
Click to expand...
Click to collapse
Ya the qpst. I looked and the port doesn't show up as a phone. It just shows up as the serial port and won't allow me to connect. I'll look for the cdmaworkshop tool though. I'm probably going to just try to short the capactitors to get it into 9006 mode and reflash the partitions. Does anyone know where the specific capacitors are? There was a youtube video of it but the owner flipped out and made it private.... so much for advancing the community.
I tried the volume up and insert but nothing shows up. I'm curious if this were to go in for warranty if the company to fix it would be able to tell if its rooted or if they would be in the same position i am where nothing shows up.
Does it show comm7 , i know there is a box that is checked, in the add port screen, that keeps it from seeing the port. When i get home i'll take a screen shot
I too am having this exact issue.
I'm on the same boat. I don't even know how it happened since I wasn't even trying to flash a ROM. One person told me to look at tablets hard brick but I've had no luck yet. Phone was stuck in a recovery bootloop so I tried to wipe/restore backup which didn't work. Popped the battery, went to download mode, started flashing TOT, got an error (yes I had the right files), popped battery again hoping it was a bad connection but nope. I got it the other week :/ as a replacement because my G2 had hardware issues. There's gotta be a way somewhere. In the mean time, I had my gf call my service provider claiming she got a popup about an upgrade, clicked yes and came back to a black screen. They said to bring it in because it's within 14 days of the refurbished. I'm going to take it in but I'm hoping there's a way to get the phone to not load anything at all (led or the boot error during LG), or do sales reps not know enough and/or don't care enough?
I got it working!!! Somehow I got TWRP'd to boot then restored my backup of 4.4.2 stock. AT&T connecting/dropping and Baseband: "Unknown" before it randomly rebooted into download mode which I'm at now. I tried flashing TOT through COM41 but it wasn't successful. Not sure what to do now.
I had some paragraph typed and it must've not gone through. I got it back to the home screen and AT&T logo once "firmware upgrade" was an option again. I still don't know how I switched it from Qualcomm to LGE Mobile, maybe some files I deleted thinking an app backdoor'd it and injected files. After a fun and exciting 12+ hours straight with errors, bootloops, reading forums, videos, downloading/un-install. I managed a way that worked and booted back into a fresh device.
Flash Tools < BOARD_DL < Booted into Status 2
LG Suite < Restore < Fail
Flash Tools < UPGRADE_DL < Fail at 6%
Flash Tools < BOARD_DL < Fail at download mode
Device Manager < Show Hidden < Portable Devices < Un-install all MTP
Flash Tools < BOARD_DL < got to 8x% < Phone Reboot into AAT < Click < Power+Click on "Normal Boot"
LG Logo < AT&T Logo < Brand new G3
Click to expand...
Click to collapse
Hopefully this method will work for you, and who ever else has the same problem.
Here's part of the log. Not sure if hopeful or not.
[ 9:46:27] == PROPERTY INFO
[ 9:46:27] 1. download cable = USER
[ 9:46:27] 2. battery level = 77
[ 9:46:27] 3. download type =
[ 9:46:27] 4. download speed = 0
[ 9:46:27] 5. usb version = UHS
[ 9:46:27] 6. hardware revision = rev_10
[ 9:46:27] 7. download sw version =
[ 9:46:27] 8. device sw version = D85010d
[ 9:46:27] 9. secure device = S
[ 9:46:27] 10. laf sw version = 1.0
[ 9:46:27] 11. device factory version = LGD850AT-01-V10d-310-410-JUN-19-2014+0
[ 9:46:27] 12. device factory out version = LGD850AT-00-V10d-ATT-US-JUN-19-2014+0
[ 9:46:27] 13. pid = HD58S140925001695
[ 9:46:27] 14. imei = XXXXXXXXXXXXXXXXXXXX
[ 9:46:27] 15. model name = LG-D850
[ 9:46:27] 16. device build type = U
[ 9:46:27] 17. chipset platform = msm8974
[ 9:46:27] 18. target_operator = ATT
[ 9:46:27] 19. target_country = US
[ 9:46:27] 20. ap_factory_reset_status = 2
[ 9:46:27] 21. cp_factory_reset_status = 0
[ 9:46:27] 22. isDownloadNotFinish = 0
[ 9:46:27] 23. qem = 0
[ 9:46:27] 24. cupss swfv = FFFFFFFFFFF-FFFFFFFFFFF-FFFFFFFFFFF-FFFFFFFFFFF-F
[ 9:46:27] 25. is one binary dual plan = 0
[ 9:46:27] 26. memroy size = 61071360
[ 9:46:27] 27. memory_id = 032GE4
[ 9:46:27] 28. bootloader_ver = MiniOS 3.0
[ 9:46:27] LAF : Bin_User_Mode
[ 9:46:27] isValidateSecureImage Device is a qfused.
[ 9:46:27] found sbl1 Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] found aboot Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] found rpm Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] found tz Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] Secure Image Check Success
[ 9:46:27] * Set AP factory_reset= 0
[ 9:46:27] * Set qem_reset= 1
GrayNullFox said:
I'm on the same boat. I don't even know how it happened since I wasn't even trying to flash a ROM. One person told me to look at tablets hard brick but I've had no luck yet. Phone was stuck in a recovery bootloop so I tried to wipe/restore backup which didn't work. Popped the battery, went to download mode, started flashing TOT, got an error (yes I had the right files), popped battery again hoping it was a bad connection but nope. I got it the other week :/ as a replacement because my G2 had hardware issues. There's gotta be a way somewhere. In the mean time, I had my gf call my service provider claiming she got a popup about an upgrade, clicked yes and came back to a black screen. They said to bring it in because it's within 14 days of the refurbished. I'm going to take it in but I'm hoping there's a way to get the phone to not load anything at all (led or the boot error during LG), or do sales reps not know enough and/or don't care enough?
I got it working!!! Somehow I got TWRP'd to boot then restored my backup of 4.4.2 stock. AT&T connecting/dropping and Baseband: "Unknown" before it randomly rebooted into download mode which I'm at now. I tried flashing TOT through COM41 but it wasn't successful. Not sure what to do now.
I had some paragraph typed and it must've not gone through. I got it back to the home screen and AT&T logo once "firmware upgrade" was an option again. I still don't know how I switched it from Qualcomm to LGE Mobile, maybe some files I deleted thinking an app backdoor'd it and injected files. After a fun and exciting 12+ hours straight with errors, bootloops, reading forums, videos, downloading/un-install. I managed a way that worked and booted back into a fresh device.
Hopefully this method will work for you, and who ever else has the same problem.
Here's part of the log. Not sure if hopeful or not.
[ 9:46:27] == PROPERTY INFO
[ 9:46:27] 1. download cable = USER
[ 9:46:27] 2. battery level = 77
[ 9:46:27] 3. download type =
[ 9:46:27] 4. download speed = 0
[ 9:46:27] 5. usb version = UHS
[ 9:46:27] 6. hardware revision = rev_10
[ 9:46:27] 7. download sw version =
[ 9:46:27] 8. device sw version = D85010d
[ 9:46:27] 9. secure device = S
[ 9:46:27] 10. laf sw version = 1.0
[ 9:46:27] 11. device factory version = LGD850AT-01-V10d-310-410-JUN-19-2014+0
[ 9:46:27] 12. device factory out version = LGD850AT-00-V10d-ATT-US-JUN-19-2014+0
[ 9:46:27] 13. pid = HD58S140925001695
[ 9:46:27] 14. imei = XXXXXXXXXXXXXXXXXXXX
[ 9:46:27] 15. model name = LG-D850
[ 9:46:27] 16. device build type = U
[ 9:46:27] 17. chipset platform = msm8974
[ 9:46:27] 18. target_operator = ATT
[ 9:46:27] 19. target_country = US
[ 9:46:27] 20. ap_factory_reset_status = 2
[ 9:46:27] 21. cp_factory_reset_status = 0
[ 9:46:27] 22. isDownloadNotFinish = 0
[ 9:46:27] 23. qem = 0
[ 9:46:27] 24. cupss swfv = FFFFFFFFFFF-FFFFFFFFFFF-FFFFFFFFFFF-FFFFFFFFFFF-F
[ 9:46:27] 25. is one binary dual plan = 0
[ 9:46:27] 26. memroy size = 61071360
[ 9:46:27] 27. memory_id = 032GE4
[ 9:46:27] 28. bootloader_ver = MiniOS 3.0
[ 9:46:27] LAF : Bin_User_Mode
[ 9:46:27] isValidateSecureImage Device is a qfused.
[ 9:46:27] found sbl1 Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] found aboot Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] found rpm Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] found tz Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] Secure Image Check Success
[ 9:46:27] * Set AP factory_reset= 0
[ 9:46:27] * Set qem_reset= 1
Click to expand...
Click to collapse
I appreciate you going through this, but I don't think that you were bricked to the point that we are.
-No Download Mode
-No Recovery
-Black Screen & nothing on it.
-When plugged in via USB it shows up on the pc as: LGE AndroidNet USB Serial Port
-LG Flash Tools will not work.
-When plugged in with no battery, the screen lights up with a symbol with a battery and an exclamation point.
ElectroSh0ck said:
I appreciate you going through this, but I don't think that you were bricked to the point that we are.
-No Download Mode
-No Recovery
-Black Screen & nothing on it.
-When plugged in via USB it shows up on the pc as: LGE AndroidNet USB Serial Port
-LG Flash Tools will not work.
-When plugged in with no battery, the screen lights up with a symbol with a battery and an exclamation point.
Click to expand...
Click to collapse
That's how I was. Secure info boot < red and blue led with black screen, no factory restore. I don't know how I got TWRP to boot. I started messing around with the device manager, deleting any files stored on the computer related to any LG device (AndroidNet, QualComm, MTP, etc) along with popping the battery in with the charge screen and reading a logs.
I hope you guys can get it fixed.
Not even getting a secure info boot here. Black screen no leds
Sent from my SM-N910V using XDA Free mobile app
Same here
After rooting it and installing TRWP, I was getting an Error when rebooting into recovery "Secure Boot error". I found a solution at this page: http://forum.xda-developers.com/lg-g3/help/help-secure-boot-error-trying-to-boot-t3054977 and I was trying to replicate. At the Terminal command step "su" worked, the second line didn't, the third line worked and the final one didn't. I know that the third line bricked my phone.
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot (writes “zeroes” to the partition to “wipe” it out)
Since then the phone is almost dead. No way to wake it up, I've tried every combination of buttons and USB plugin. The only signs that is alive are that when I connect it without the battery to USB it shows the with the phone connected and the yellow triangle with a question mark and that is detected as LGE Androidnet USB and modem in the Device Manager. I tried the TOT method and the KDZ method, nothing worked. In Qpst it is detected as Phone in Download Mode and in QPST Configuration as Sahara Memory Dump (Connected Phone: Q/QCP-XXX).
LGNPST detects it as UNKNOWN, only Emergency active, and doesn't do anything when trying to upload the bin file, gives Error: Could not switch to download mode.
Getting crazy here.
What DLL did you use to get LGNPST to give you that error?
ElectroSh0ck said:
What DLL did you use to get LGNPST to give you that error?
Click to expand...
Click to collapse
The default one... LGNPST_LS970.dll It was the only one that it let me use.
alex_da_fixeru said:
The default one... LGNPST_LS970.dll It was the only one that it let me use.
Click to expand...
Click to collapse
Ah okay that makes sense. We will need a DLL specific to the model of G3 that we have. It is basically telling the program how to interact with the phone in emergency mode. I have tried the DLL's used to flash TOTs, but they will not register in Windows.
ElectroSh0ck said:
Ah okay that makes sense. We will need a DLL specific to the model of G3 that we have. It is basically telling the program how to interact with the phone in emergency mode. I have tried the DLL's used to flash TOTs, but they will not register in Windows.
Click to expand...
Click to collapse
I can't seem to find the correct .dll for LG G3. Anyone has it?
Wouldn't it be the one that came with your firmware file?
Sent from my Nexus 7 using XDA Free mobile app
danmak89 said:
Wouldn't it be the one that came with your firmware file?
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
I would think that was the case, but they will not show up in LGNPST. I can get the ones to work that others have provided specifically for LGNPST, but not the ones used to flash a TOT with LG Flash Tool.
ElectroSh0ck said:
I would think that was the case, but they will not show up in LGNPST. I can get the ones to work that others have provided specifically for LGNPST, but not the ones used to flash a TOT with LG Flash Tool.
Click to expand...
Click to collapse
Ah man. I managed to get my device recognised as LGE AndroidNet USB Serial Port but there's still another driver that won't install and I don't know which one it would need to be.
Device just won't boot in to any mode, no LEDs, nothing. Obvious tools don't work like flashtool, b2bsupport. I'm considering swapping out the main board as they don't seem too expensive but I'm trying to see if I can solve this first.
I refuse to accept that this is 100% bricked.
Sent from my Nexus 7 using XDA Free mobile app
Hi Guys,
Im trying to install factory firmware on my LG G3 D855 i downloaded European 32 tot file
while installing lg flash tools stops are 6% with the following error
Partition Change factory Partition (Phone!=tot)
and in log file i see this
[ 4: 7:46] prog size = 2824, receive size = 2824
[ 4: 7:46] == PROPERTY INFO
[ 4: 7:46] 1. download cable = USER
[ 4: 7:46] 2. battery level = 16
[ 4: 7:46] 3. download type = F
[ 4: 7:46] 4. download speed = 0
[ 4: 7:46] 5. usb version = UHS
[ 4: 7:46] 6. hardware revision = rev_10
[ 4: 7:46] 7. download sw version = D85510e
[ 4: 7:46] 8. device sw version = LGD855-V10x-ISR
[ 4: 7:46] 9. secure device = S
[ 4: 7:46] 10. laf sw version = 1.0
[ 4: 7:46] 11. device factory version = LGD855AT-00-V10x-GLOBAL-COM-OCT-22-2014-32G+0
[ 4: 7:46] 12. device factory out version = LGD855AT-00-V10x-GLOBAL-COM-OCT-22-2014-32G+0
[ 4: 7:46] 13. pid = SM05S141024000528
[ 4: 7:46] 14. imei = 3541530xxxxxxx
[ 4: 7:46] 15. model name = LG-D855
[ 4: 7:46] 16. device build type = U
[ 4: 7:46] 17. chipset platform = msm8974
[ 4: 7:46] 18. target_operator = GLOBAL
[ 4: 7:46] 19. target_country = US
[ 4: 7:46] 20. ap_factory_reset_status = 0
[ 4: 7:46] 21. cp_factory_reset_status = 238
[ 4: 7:46] 22. isDownloadNotFinish = 2
[ 4: 7:46] 23. qem = 0
[ 4: 7:46] 24. cupss swfv = FFFFFFFFFFF-FFFFFFFFFFF-FFFFFFFFFFF-FFFFFFFFFFF-F
[ 4: 7:46] 25. is one binary dual plan = 0
[ 4: 7:46] 26. memroy size = 61071360
[ 4: 7:46] 27. memory_id = 032GE4
[ 4: 7:46] 28. bootloader_ver = MiniOS 3.0
[ 4: 7:46] LAF : Bin_User_Mode
[ 4: 7:46] isValidateSecureImage Device is a qfused.
[ 4: 7:46] found sbl1 Partition for secure image check
[ 4: 7:46] Secure Image
[ 4: 7:46] found aboot Partition for secure image check
[ 4: 7:46] Secure Image
[ 4: 7:46] found rpm Partition for secure image check
[ 4: 7:46] Secure Image
[ 4: 7:46] found tz Partition for secure image check
[ 4: 7:46] Secure Image
[ 4: 7:46] Secure Image Check Success
[ 4: 7:46] * bootloader_ver = MiniOS 3.0
[ 4: 7:46] * Set AP factory_reset= 0
[ 4: 7:46] * Set CP factory_reset= 238
[ 4: 7:46] WebUpgrade flag setting. set to not finish
Ant body knows what is solution?
hushme said:
Hi Guys,
Im trying to install factory firmware on my LG G3 D855 i downloaded European 32 tot file
while installing lg flash tools stops are 6% with the following error
Partition Change factory Partition (Phone!=tot)
and in log file i see this
[ 4: 7:46] prog size = 2824, receive size = 2824
[ 4: 7:46] == PROPERTY INFO
[ 4: 7:46] 1. download cable = USER
[ 4: 7:46] 2. battery level = 16
[ 4: 7:46] 3. download type = F
[ 4: 7:46] 4. download speed = 0
[ 4: 7:46] 5. usb version = UHS
[ 4: 7:46] 6. hardware revision = rev_10
[ 4: 7:46] 7. download sw version = D85510e
[ 4: 7:46] 8. device sw version = LGD855-V10x-ISR
[ 4: 7:46] 9. secure device = S
[ 4: 7:46] 10. laf sw version = 1.0
[ 4: 7:46] 11. device factory version = LGD855AT-00-V10x-GLOBAL-COM-OCT-22-2014-32G+0
[ 4: 7:46] 12. device factory out version = LGD855AT-00-V10x-GLOBAL-COM-OCT-22-2014-32G+0
[ 4: 7:46] 13. pid = SM05S141024000528
[ 4: 7:46] 14. imei = 3541530xxxxxxx
[ 4: 7:46] 15. model name = LG-D855
[ 4: 7:46] 16. device build type = U
[ 4: 7:46] 17. chipset platform = msm8974
[ 4: 7:46] 18. target_operator = GLOBAL
[ 4: 7:46] 19. target_country = US
[ 4: 7:46] 20. ap_factory_reset_status = 0
[ 4: 7:46] 21. cp_factory_reset_status = 238
[ 4: 7:46] 22. isDownloadNotFinish = 2
[ 4: 7:46] 23. qem = 0
[ 4: 7:46] 24. cupss swfv = FFFFFFFFFFF-FFFFFFFFFFF-FFFFFFFFFFF-FFFFFFFFFFF-F
[ 4: 7:46] 25. is one binary dual plan = 0
[ 4: 7:46] 26. memroy size = 61071360
[ 4: 7:46] 27. memory_id = 032GE4
[ 4: 7:46] 28. bootloader_ver = MiniOS 3.0
[ 4: 7:46] LAF : Bin_User_Mode
[ 4: 7:46] isValidateSecureImage Device is a qfused.
[ 4: 7:46] found sbl1 Partition for secure image check
[ 4: 7:46] Secure Image
[ 4: 7:46] found aboot Partition for secure image check
[ 4: 7:46] Secure Image
[ 4: 7:46] found rpm Partition for secure image check
[ 4: 7:46] Secure Image
[ 4: 7:46] found tz Partition for secure image check
[ 4: 7:46] Secure Image
[ 4: 7:46] Secure Image Check Success
[ 4: 7:46] * bootloader_ver = MiniOS 3.0
[ 4: 7:46] * Set AP factory_reset= 0
[ 4: 7:46] * Set CP factory_reset= 238
[ 4: 7:46] WebUpgrade flag setting. set to not finish
Ant body knows what is solution?
Click to expand...
Click to collapse
Is your phone an LGD855-V10x-ISR ? and already rooted ?
i have the same problem
plz share any new info you got
0v3rfl0w said:
Is your phone an LGD855-V10x-ISR ? and already rooted ?
i have the same problem
plz share any new info you got
Click to expand...
Click to collapse
mine is LGD855-V10m-ISR and im stuck in same situation with no help whatsoever. :S
Why don't you guys use a KDZ firmware using LG flash tool?
twisted_twice said:
Why don't you guys use a KDZ firmware using LG flash tool?
Click to expand...
Click to collapse
didn't work for me :crying:
i tried LGUP and LG flashtool . and i couldn't install a twrp recovery image ( fastboot started problem ) !!! weird !!!!
Does anyone found a solution on this?
0v3rfl0w said:
didn't work for me :crying:
i tried LGUP and LG flashtool . and i couldn't install a twrp recovery image ( fastboot started problem ) !!! weird !!!!
Click to expand...
Click to collapse
me too having same problem did you get any solution
---------- Post added at 05:44 PM ---------- Previous post was at 05:43 PM ----------
0v3rfl0w said:
Is your phone an LGD855-V10x-ISR ? and already rooted ?
i have the same problem
plz share any new info you got
Click to expand...
Click to collapse
i am also facing those problems i tried to flash twrp through flashify & its entering into fastboot mode
Since I had the same issue was trying to find a way to get rid of it.
First, the phone was sold as D855 International, but when I opened it on the main board it was saying D851. So I took that version of software but wasn't able to flash even that one...
So I decided to try the procedure where you can boot your phone in some Qualcomm 9008 mode by grounding one of the pins on the board, you can find the procedure on how to get into the same mode.
After getting there I erased the entire flash, flashed each and every image from the unpacked .tot file for D851 one-by-one leaving the sbl1 image for last by using the qualcomm tool and this helped to boot up in fresh Android.
gjoregj said:
Since I had the same issue was trying to find a way to get rid of it.
First, the phone was sold as D855 International, but when I opened it on the main board it was saying D851. So I took that version of software but wasn't able to flash even that one...
So I decided to try the procedure where you can boot your phone in some Qualcomm 9008 mode by grounding one of the pins on the board, you can find the procedure on how to get into the same mode.
After getting there I erased the entire flash, flashed each and every image from the unpacked .tot file for D851 one-by-one leaving the sbl1 image for last by using the qualcomm tool and this helped to boot up in fresh Android.
Click to expand...
Click to collapse
please can u provide links how to you made it worked out
thankx in advanced
prince1995 said:
please can u provide links how to you made it worked out
thankx in advanced
Click to expand...
Click to collapse
How to get into Qualcomm 9008 mode:
http //forum.gsmhosting com/vbb/f494/how-hard-unbricked-lg-g3-all-variants-fix-qhsusb-bulk-_-qualcomm-9008-a-2029025/
For the IMEI recover sort of:
https //www youtube com/watch?v=nwzgs1Cmr9k
There is no step-by-step on what exactly you need to do, but those two links helped me the most.
Whenever i am switching on my Lenovo K8 plus mobile device :
I am getting a blinking screen with this information ---
AP fastboot flashmode
Product/varient :null
serial number :null
IMEI :null
Console : null
battery Status : Ok
Engineering
Software Status : null
transfer mode : cable not connected
Device status : Locked
I tryed installing custom ROM after wiping data/factory reset and wiping cache but my installation is getting aborted with this information :----
Supported API 3.
E : Footer is wrong
E : Signature Verification failed
E: Error 21
Installation aborted
sumit_trivedhi
sumit_trivedi said:
Whenever i am switching on my Lenovo K8 plus mobile device :
I am getting a blinking screen with this information ---
AP fastboot flashmode
Product/varient :null
serial number :null
IMEI :null
Console : null
battery Status : Ok
Engineering
Software Status : null
transfer mode : cable not connected
Device status : Locked
I tryed installing custom ROM after wiping data/factory reset and wiping cache but my installation is getting aborted with this information :----
Supported API 3.
E : Footer is wrong
E : Signature Verification failed
E: Error 21
Installation aborted
Click to expand...
Click to collapse
I had same problem.
Root and repair imei any Qualcomm tool ..
Hi,
I want ask for help with recovery of my One Plus 9 Pro. The smartphone was oryginally in LE2120 (China) version but with India ROM (LE2121). I Wanted change it for EU ROM (LE2123) but that crashesh my phone...
After hours of failed attempts I don;t know what else I can do...
First ROM install attemt ended with errors on first pics. Next I've installed TWRP and now after each start of OnePlus it launches TWRP ant nothing else. I can ewentually go to the fastboot menu.
From TWRP I can't do repair, upload files from my PC, repair filesystem - amost nothing... Errors in another attached pics..
I've try to use MSM Tools and push files using EDL but it also finished with error (another attached pics).
In current state I can't go to the fastbootD menu (only TWRP available and launching automatically). When trying go to fastbootD - getting error (attachement).
I have downloaded many versions of OnePlus ROM's and recovery files with MSM Tolls but with any results - all of them eded with the same eerors like in attachements.
Please help what I should do now to get my Oneplus working again.
Let me think....
Try using the Eu MSM. I've read on oneplus community someone had a similar problem. Google "msmtool for le2120" and it should be one of the first results.
Marffi said:
Hi,
I want ask for help with recovery of my One Plus 9 Pro. The smartphone was oryginally in LE2120 (China) version but with India ROM (LE2121). I Wanted change it for EU ROM (LE2123) but that crashesh my phone...
After hours of failed attempts I don;t know what else I can do...
First ROM install attemt ended with errors on first pics. Next I've installed TWRP and now after each start of OnePlus it launches TWRP ant nothing else. I can ewentually go to the fastboot menu.
From TWRP I can't do repair, upload files from my PC, repair filesystem - amost nothing... Errors in another attached pics..
I've try to use MSM Tools and push files using EDL but it also finished with error (another attached pics).
In current state I can't go to the fastbootD menu (only TWRP available and launching automatically). When trying go to fastbootD - getting error (attachement).
I have downloaded many versions of OnePlus ROM's and recovery files with MSM Tolls but with any results - all of them eded with the same eerors like in attachements.
Please help what I should do now to get my Oneplus working again.
Click to expand...
Click to collapse
In twrp you can goto advanced->adb sideload, to flash roms.
You can also go into twrp fastbootd, if you follow these steps:
normally boot into twrp with "fastboot boot"
in twrp goto reboot->fastboot
while shutting down hold power+vol down (brings you to bootloader)
run fastboot boot twrp.img
For flashing partitions in fastboot you can always use _slot instead of --slot. For example "fastboot flash boot --slot=a boot.img" ->"fastboot flash boot_a boot.img". Same has to be done with slot b.
It could also be a good idea to use LE2120 MSM to go back to a usable state.
Since your original firmware was from India, I can mod you an MSM tool to flash the EU firmware. Give me a couple hours. Have to run an errand in town first...
In the meantime use the IN MSM Tool to revive your phone then wait for my mod MSM Tool to flash EU to phone.
der_akinator said:
In twrp you can goto advanced->adb sideload, to flash roms.
You can also go into twrp fastbootd, if you follow these steps:
normally boot into twrp with "fastboot boot"
in twrp goto reboot->fastboot
while shutting down hold power+vol down (brings you to bootloader)
run fastboot boot twrp.img
For flashing partitions in fastboot you can always use _slot instead of --slot. For example "fastboot flash boot --slot=a boot.img" ->"fastboot flash boot_a boot.img". Same has to be done with slot b.
It could also be a good idea to use LE2120 MSM to go back to a usable state.
Click to expand...
Click to collapse
Unfortunatley not I can't go to fastbootd. When trying do that I'm getting another error:
Marffi said:
Unfortunatley not I can't go to fastbootd. When trying do that I'm getting another error:
Click to expand...
Click to collapse
Use the IN MSM Tool to revive phone... In edl mode.
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
here you go.......
File on MEGA
mega.nz
In EDL mode using new downlod the same error as previous
TheGhost1951 said:
here you go.......
File on MEGA
mega.nz
Click to expand...
Click to collapse
Using moded MSM Tools I've get messages:
1. Try Firehose Communication Handshake
2. Setting Firehose Communication Data trasmi...
3. Get TID Failed
and nothing more.
Log File:
[2472][05-17 16:38:43.843]<4> Set Proc Mode 0
[2472][05-17 16:38:43.996]<2> =========================================================
[2472][05-17 16:38:43.996]<2> | OnePlus DL PID:14264
[2472][05-17 16:38:43.996]<2> | Execute: 2023/05/17 14:38 GMT
[2472][05-17 16:38:43.996]<2> =========================================================
[2472][05-17 16:38:50.359]<4>
========================================================
[2472][05-17 16:39:06.535]<4> MetadataVersion=2,CryptVersion=1,[2472][05-17 16:39:06.535]<4> m_bIsPackImage=1
[2472][05-17 16:39:06.566]<4> Set Proc Mode 1
[2472][05-17 16:39:06.766]<4> ATO element doesn't exist. Skip.
[2472][05-17 16:39:06.782]<4> Project Name: 20857
[2472][05-17 16:39:06.782]<4> Factory ID: 20857IN
[2472][05-17 16:39:06.782]<4> Image Version: lemonadep_22_I.07_210412
[2472][05-17 16:39:06.782]<4> Skip SHA256 Check: No
[2472][05-17 16:39:06.782]<4> HW CHK: No
[2472][05-17 16:39:06.782]<4> RF CHK: No
[2472][05-17 16:39:06.782]<4> PRJ CHK: No
[2472][05-17 16:39:06.798]<4> MDL CHK: Yes
[2472][05-17 16:39:06.798]<4> ATO build: No
[2472][05-17 16:39:06.798]<4> Load upd cfg failed. continue.
[2472][05-17 16:39:06.798]<4> frp: 1
[2472][05-17 16:39:06.798]<4> Tool version verified! (V5.1.77)
[2472][05-17 16:39:06.798]<4> project 20857 not support boot mode feature
[2472][05-17 16:39:06.798]<4> project 20857 enable fuse
[2472][05-17 16:39:06.835]<4> [1] dwMajorVersion=6,dwMinorVersion=2,is_win7_system=0
[2472][05-17 16:39:06.873]<4> Skip multi-image identify: 0
[13140][05-17 16:39:15.492]<4> Device Arrival: \\?\USB#VID_05C6&PID_9008#5&318e2ee3&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[6740][05-17 16:39:19.069]<4> [0] SetComStep: 1
[6740][05-17 16:39:19.069]<4> [0] GetComStep: 1
[6740][05-17 16:39:19.071]<4> CID = -1
[6740][05-17 16:39:19.071]<4> Non TMO group
[6740][05-17 16:39:19.085]<4> [1] Set device as UFS
[6740][05-17 16:39:19.311]<4> [1] [CSerialCommHelper] Buf: 0 (16/10)
[6740][05-17 16:39:19.327]<4> [1] [CSerialCommHelper] No data in buffer to be sent 0
[6740][05-17 16:39:21.514]<4> [1] [SP][195] Check cmd done status failed. 1
[6740][05-17 16:39:21.637]<4> [1] [SP][208] Reset Sahara
[6740][05-17 16:39:21.852]<4> [1] [COM1] AddCpuIDtoIndex cupid(8aeb0289)
[6740][05-17 16:39:25.061]<4> [1] UFS Inquiry Command Output: SAMSUNG KLUEG8UHDB-C2D1 1903
[6740][05-17 16:39:25.061]<4> [1] UFS info Vendor = samsung, TotalLogicalBlocks = 499892224
[6740][05-17 16:39:25.061]<4> [1] [FFU]FWversion 903
[6740][05-17 16:39:25.061]<4> [1] [FFU] UFS Total Active LU 6
[6740][05-17 16:39:25.061]<4> [1] EmmcSizeInGB = 238.367188, TotalLogicalBlocks = 499892224
[6740][05-17 16:39:25.061]<4> [1] Memory size:
[6740][05-17 16:39:25.061]<4> [1] Not in intranet, pass.[6740][05-17 16:39:25.077]<4> [1] [Firehose] HwVersion = 22
[6740][05-17 16:39:25.093]<4> [1] [Firehose] RfVersion = 11
[6740][05-17 16:39:25.124]<4> [1] [Firehose] PrjVersion = 11
[6740][05-17 16:39:25.146]<4> [1] Get SW ID failed.
[13140][05-17 16:40:15.427]<4> Device Remove: \\?\USB#VID_05C6&PID_9008#5&318e2ee3&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[13140][05-17 16:42:34.518]<4> Device Arrival: \\?\USB#VID_05C6&PID_9008#5&318e2ee3&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[18596][05-17 16:42:36.464]<4> [0] SetComStep: 1
[18596][05-17 16:42:36.464]<4> [0] GetComStep: 1
[18596][05-17 16:42:36.466]<4> CID = -1
[18596][05-17 16:42:36.466]<4> Non TMO group
[18596][05-17 16:42:36.470]<4> [1] Set device as UFS
[18596][05-17 16:42:36.704]<4> [1] [CSerialCommHelper] Buf: 0 (16/10)
[18596][05-17 16:42:36.720]<4> [1] [CSerialCommHelper] No data in buffer to be sent 0
[18596][05-17 16:42:38.924]<4> [1] [SP][195] Check cmd done status failed. 1
[18596][05-17 16:42:39.025]<4> [1] [SP][208] Reset Sahara
[18596][05-17 16:42:39.256]<4> [1] [COM1] AddCpuIDtoIndex cupid(8aeb0289)
[18596][05-17 16:42:42.432]<4> [1] UFS Inquiry Command Output: SAMSUNG KLUEG8UHDB-C2D1 1903
[18596][05-17 16:42:42.432]<4> [1] UFS info Vendor = samsung, TotalLogicalBlocks = 499892224
[18596][05-17 16:42:42.432]<4> [1] [FFU]FWversion 903
[18596][05-17 16:42:42.432]<4> [1] [FFU] UFS Total Active LU 6
[18596][05-17 16:42:42.432]<4> [1] EmmcSizeInGB = 238.367188, TotalLogicalBlocks = 499892224
[18596][05-17 16:42:42.432]<4> [1] Memory size:
[18596][05-17 16:42:42.432]<4> [1] Not in intranet, pass.[18596][05-17 16:42:42.447]<4> [1] [Firehose] HwVersion = 22
[18596][05-17 16:42:42.463]<4> [1] [Firehose] RfVersion = 11
[18596][05-17 16:42:42.501]<4> [1] [Firehose] PrjVersion = 11
[18596][05-17 16:42:42.516]<4> [1] Get SW ID failed.
[13140][05-17 16:42:48.489]<4> Device Remove: \\?\USB#VID_05C6&PID_9008#5&318e2ee3&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
and second one:
IA V1.0
FCL V1.2
PL V1.9
MVL V1.3
SID 300 is non enc
Encrytped block of item 20 is incorrect
SID 300 is non enc
Encrytped block of item 20 is incorrect
Marffi said:
Unfortunatley not I can't go to fastbootd. When trying do that I'm getting another error:
Click to expand...
Click to collapse
This error shouldn't be a problem, but you probably have to wait 5-10 seconds to use fastboot. You can also flash boot, vendor_boot and dtbo of any rom and use their fastbootd.
der_akinator said:
This error shouldn't be a problem, but you probably have to wait 5-10 seconds to use fastboot. You can also flash boot, vendor_boot and dtbo of any rom and use their fastbootd.
Click to expand...
Click to collapse
Do you think he could get to recovery from fastboot and factory reset?
Or from fastboot flash update payload.bin?
TheGhost1951 said:
Do you think he could get to recovery from fastboot and factory reset?
Click to expand...
Click to collapse
Yes, should work with all recoveries with "fastboot reboot recovery"
Payload has to be extracted, but after that you can flash all partitions from fastbootd.
One caveat is that MSM payload contains some partitions that are not included in OTA payload.bin
Edit:
MSM payload can be extracted with this: https://github.com/bkerler/oppo_decrypt
But I don't know if the extra MSM partitions are flashable with fastboot.
der_akinator said:
Yes, should work with all recoveries with "fastboot reboot recovery"
Payload has to be extracted, but after that you can flash all partitions from fastbootd.
One caveat is that MSM payload contains some partitions that are not included in OTA payload.bin
Click to expand...
Click to collapse
"
C:\ADB>fastboot reboot recovery
Rebooting into recovery OKAY [ 0.016s]
Finished. Total time: 0.016s
"
Phone just restart and automatically load TWRP. Nothing more.
Marffi said:
"
C:\ADB>fastboot reboot recovery
Rebooting into recovery OKAY [ 0.016s]
Finished. Total time: 0.016s
"
Phone just restart and automatically load TWRP. Nothing more.
Click to expand...
Click to collapse
Yes that's was the answer to @TheGhost1951 question.
TheGhost1951 said:
Or from fastboot flash update payload.bin?
Click to expand...
Click to collapse
"
C:\ADB>fastboot devices
8aeb0289 fastboot
C:\ADB>fastboot flash update payload.bin
error: write_sparse_skip_chunk: don't care size 4211328355 is not a multiple of the block size 4096
Sending sparse 'update' 1/7 (786428 KB) error: write_sparse_skip_chunk: don't care size 4211328355 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 4211328355 is not a multiple of the block size 4096
OKAY [ 19.952s]
Writing 'update' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
"
So failed as well
What was the last MSM tool tried? Did you try the Indian MSM tool?
TMO 9PRO LAST OPTION HARDBRICKED FIX & BACK TO TMO STOCK FIX
Frist off I'm not Responsible for anything that happens to your phone!!! DO NOT FLASH UNLESS YOU TRIED EVERYTHING ELSE FIRST INDIA MSM TOOL TO FIX YOUR HARD BRICKED T-MOBILE 9PR0!!!! DO THIS AT YOUR OWEN RISK!!! DISCLAIMER: THIS WILL...
forum.xda-developers.com