Phone bricked after trying to update to android 6 - T-Mobile LG G4

Hello, I have the LG G4 H811 (S/W: V10d, written on back of the phone) version. After buying the phone, I tried to update to marshmallow from lollipop using LG Bridge as the automatic update wasn't coming to my phone. After the process was apparently completed my phone isn't turning on anymore. Tried power button, volume up+down+power etc. But not working. no charging sign.
When connecting the phone to pc through usb, most of the times it doesn't find anything ("unknown usb device" or something). Once in a while it finds as "Qualcomm HS-USB QDLOADER 9008" in device manager. ( P.S. It finds as "Qualcomm HS-USB QDLOADER 9008" if I remove and insert the battery for the first time)
Now I've surfed the net for a few hours and found various potential solutions. Was trying this solution first: boycracked dot com/2016/08/04/how-to-unbrick-updates-firmware-flashing-any-lg-android-devices-using-kdz-updater-tools/
(Can't copy direct link being a new member. please replace the "dot")
But the method is not working. Showing "extract file error" when i select the .kdz file and click "launch software update"
Should I try this method: androidmtk dot com/use-qualcomm-flash-image-loader-qfil
By the way, Do I need a specific .kdz file (stock firmware) for the V10d variant? If so, I haven't found it after searching for hours and was trying different .kdz files (all for H811 though). If I need the specific file please give me some link where I can find it. So far the model number(H811) isn't matching when i find a V10d version.
I'll try to use the SD card fix once I manage a card and card reader: forum dot xda-developers.com/tmobile-g4/general/lg-g4-h811-complete-unbrick-guide-100-t3461629
Still I would need the specifc .kdz file I guess for V10d version??
Also if possible please give me the link to a method which is apparently most successful as it seems to be a old problem.
My phone is virtually brand new and am feeling a bit helpless. Please help me by giving some effective solutions. Thanks in advance.
Update: FWIW I followed this link: forum dot gsmhosting.com/vbb/f779/unbrick-lg-g4-brick-hs-usb-qdloader-9008-without-box-2211744/
I apparently succeeded in finishing the operation (didn't use jumper method. Pressed volume up+down method)
But after it showed "succeed", nothing seems to have changed. But seems like the phone is shown as "Qualcomm HS-USB QDLOADER 9008" every time I connect it to PC. Before doing this operation, I had to remove battery and insert again to show it that way. Otherwise it showed "unknown usb device"
But seeing that nothing substantial happening, i tried to follow the same process again. But this time it showed error "Unable to download flash programmer using Sahara protocol"
I don't know what's happening, but just describing the process so that it might be easier for experienced guys to understand.

Why not just use LGUP to flash the Android 6.0 Marshmallow .kdz as a "Referb" and be done with it?
Get the Android 6.0 Marshmallow .kdz for your phone model here:
http://storagecow.eu/index.php?dir=Xda/LG+G4/
Look for T-Mobile H811.
Get LGUP here. LGUP is better than the LG Flash Tool (IMO) and it's easier to use. Don't let the instructions deter you. It's simpler than it looks.
https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Instructions:
1. Connect USB cable to PC.
2. Power off phone and then hold Vol. Up while connecting the USB cable to phone.
3. Your LG G4 should now be in Download Mode.
4. Start LGUP.
5. It should detect your phone. If it does, you will see something like this:
{
"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"
}
6. Select "Upgrade" and then use the "...." to select the .kdz for your phone.
7. Now decide if you want to do a full wipe and flash (Refurbish), or upgrade to a higher version of Android (Upgrade) and keep all of your files and settings.
8. Hit "Start" and wait for it to finish. It may restart your phone a few times. Be patient.
9. You can check the percentage under "Progress".
10. It will let you know when it's done.

Gurren Lagann said:
Why not just use LGUP to flash the Android 6.0 Marshmallow .kdz as a "Referb" and be done with it?
Get the Android 6.0 Marshmallow .kdz for your phone model here:
http://storagecow.eu/index.php?dir=Xda/LG+G4/
Look for T-Mobile H811.
Click to expand...
Click to collapse
Which H811 version should I use? As I asked do I need to use the specific version my phone had before being bricked? (I don't remember which but the default version written on the back of the phone is V10d)
Gurren Lagann said:
Get LGUP here. LGUP is better than the LG Flash Tool (IMO) and it's easier to use. Don't let the instructions deter you. It's simpler than it looks.
https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Click to expand...
Click to collapse
LGUP couldn't detect my phone. I can't remember if I used volume up when connecting but I've tried similar things when trying to different softwares and it wasnt working.
I've given it to a repair shop. After they removed the battery and plugged in two wires from some device to the back of the phone it did turn on but the lg logo came and showing probably error 1006. The repaired said the phone isn't coming to the 'download mode'.
Then they initally tried downloading some h811 dump file and installing it. But failed. Now they're saying they'll need to use JTAG box to fix it.

I just remember now, after buying the phone from some guy, I factory reset it. Now when I opened chrome, some att dot com website was showing as default homepage. That website started loading by default. What does it mean???
Does it mean the phone already had at&t(H810) firmware installed? But when powering on the phone it shows T-mobile logo and H811 is written on the back of the phone(after popping out the back cover) multiple places.
The repairer says the phone is refurbished( (I also think so). So two things can happen:
1. The motherboard was originally H811 but a H810 motherboad and H810 firmware were installed on the phone upon refurbishment. In that case why would it show the T-mobile logo when the phone starts?? Also it showed "H811" in Android (About Phone>>Model number)
2. The motherboard is still H811, but somehow H810 firmware was installed on the phone. Is it possible??? If it is then when I tried to do official update using LG Bridge, maybe LG Bridge thought the phone firmware is H811 and tried to install H811 firmware over a H810 one and the phone got bricked.
What do you think guys?? Any expert suggestion will be highly helpful... As I do feel like knowing which installing the proper firmware(H810 or H811) will take the phone back to life.

Sounds like a Frankenstein device. You can't recover it with using the wrong files. Jtag or not.
Identify the real model first (mainboard FRONT)
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Sounds like a Frankenstein device. You can't recover it with using the wrong files. Jtag or not.
Identify the real model first (mainboard FRONT)
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
So I've to install the firmware(.kdz) according to the model no. written on the motherboard, no matter what other firmware was installed when the phone was running?
Another question, when running normal, it showed "H811" as model number in "About phone" section. Is it possible that the motherboard is NOT H811 but a H811 firmware was installed on it during refurbishment?
Btw, where is the model no. written on the mainboard? Here's a link of the phone teardown: https://www.ifixit.com/Teardown/LG+G4+Teardown/42705
Please give me the link of the picture where it's showing the model no.

onikett said:
So I've to install the firmware(.kdz) according to the model no. written on the motherboard, no matter what other firmware was installed when the phone was running?
Another question, when running normal, it showed "H811" as model number in "About phone" section. Is it possible that the motherboard is NOT H811 but a H811 firmware was installed on it during refurbishment?
Btw, where is the model no. written on the mainboard? Here's a link of the phone teardown: https://www.ifixit.com/Teardown/LG+G4+Teardown/42705
Please give me the link of the picture where it's showing the model no.
Click to expand...
Click to collapse
Frankenstein is what we call a device which is refurbished in a hackish way:
https://forum.xda-developers.com/g4/general/unlock-unlock-lg-g4-device-usu-t3760451/post75817533
---> FAQ 21
So yes I can even let your device say it's an iPhone in android settings, download mode or almost anywhere. It's just code. And yes it's easy.
You can also just flash parts of another ROM if you know how and what so it does not brick or blow fuses. Dangerous when you don't understand how the g4 works internally but the refurbish ppl know what they do to fake the device enough so the average one do not see a diff.
You just have to follow that link in the above FAQ 21 and disassemble the mainboard and on the front you will see it.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Frankenstein is what we call a device which is refurbished in a hackish way:
https://forum.xda-developers.com/g4/general/unlock-unlock-lg-g4-device-usu-t3760451/post75817533
---> FAQ 21
So yes I can even let your device say it's an iPhone in android settings, download mode or almost anywhere. It's just code. And yes it's easy.
You can also just flash parts of another ROM if you know how and what so it does not brick or blow fuses. Dangerous when you don't understand how the g4 works internally but the refurbish ppl know what they do to fake the device enough so the average one do not see a diff.
You just have to follow that link in the above FAQ 21 and disassemble the mainboard and on the front you will see it.
Click to expand...
Click to collapse
Thanks.
1. Do I have to use the .kdz compatible with the actual model number written on the mainboard?
2. Should I use LGUP procedure mentioned in an above post (by Gurren Lagann)?
2. How to know what version of .kdz do I have to install? I heard if the installed version is a downgrade from the actual version (before the phone was bricked), it will not work.
3. If LGUP can't detect my phone due to it being totally hard bricked, what procedure should I follow to install the new .kdz?
I'm not an expert on the intricacies of Android OS. So please answer the questions elaborately.

Dont Try to Update 6.0, if dont wont bricked 9008 mode

Related

Unbricking "Service Required Code Corrupt"

If you use "xFSTK-SoC-Driver-Setup" and "unbrick.bat" to "Unbrick your phone, and you got the "Service code corrupt" error..., This method is untested but i think it is the problem...​You need This:
Original ICS FIRMWARE that come with your phone.
xFSTK-SoC-Driver-Setup Installed (read How Install "xFSTK-SoC-Driver-Setup")
Unbrick.bat and respective folders.
Motorola Handset USB Drivers (x86 or x64).
ADB/ FASTBOOT or SDK.
Steps to revive:
Extract Unbrick.zip in "C:\atomSOC"
Go to unbrick folder. "C:\atomSOC\unbrick"
Go to your firmware folder and copy this files (dnx; ifwi)
Replace this files in "C:\atomSOC\unbrick".
Press CAMERA button and Plug in the USB to your phone (MEDFIELD FLASH)
Run unbrick.bat in "C:\atomSOC"
How Install "xFSTK-SoC-Driver-Setup":
Run Setup
When Say "Intel Soc Is about to begin" Click OK
When Say "In Order to Complete (...) Will a device be attached (...)" Press Yes.
When Say "Step 1 (...)" Plug In your USB Cable to the pc. and click ok
When Say "Step 2 (...)" Press CAMERA button and Plug in the USB to your phone (MEDFIELD FLASH)
¿How know if my phone go to the medfield flash method?
release the camera button, your phone will stay in a black screen with the green led.
And your pc says "New hardware recognized"
Name of hardware: MEDFIELD
Before the driver install:
{
"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"
}
Downloads:
Unbrick.bat + xFSTK-SoC-Driver-Setup Download
If it works.. please, let me know​
Nope.
I just tried it, and it starts the download says a few numbers then carries on downloading.
Then the phone reboots and goes to the service required code corrupt screen
1994deano said:
I just tried it, and it starts the download says a few numbers then carries on downloading.
Then the phone reboots and goes to the service required code corrupt screen
Click to expand...
Click to collapse
Try again, your phone is not going to medfield flash mode correctly
I did not get the part - Go to your firmware folder and copy this files (dnx; ifwi)
How to go to firmware folder?,
I do not understand how to copy
i just re tried it and its got rid of the service required screen but now the screen is just black with the green led on
Me too samething, any sugestion?
gmpdri said:
Me too samething, any sugestion?
Click to expand...
Click to collapse
csn you boot to bootloader?? (power+vol.down)?
Nope
pangyaaaaaa said:
csn you boot to bootloader?? (power+vol.down)?
Click to expand...
Click to collapse
no that is why we are trying to use the medfield flash, as the bootloader is screwed up
1994deano said:
no that is why we are trying to use the medfield flash, as the bootloader is screwed up
Click to expand...
Click to collapse
I found some tools for intel lenovo pad, im trying to found how work, im think i can use it on razr i...
Boss442 said:
I found some tools for intel lenovo pad, im trying to found how work, im think i can use it on razr i...
Click to expand...
Click to collapse
ooh nice, let us know how you get on with it
S***, REALLY GOOD NEWS.....
RDS recognizes your phone on Medfield Mode...
Someone try to flash a firmware
Flashing Firmware dont work... ¿Maybe a custom XML Work?
HELP
For that ADB / Fastboot or SDK.?
Copying pro firmware?
saiko.sensei said:
For that ADB / Fastboot or SDK.?
Copying pro firmware?
Click to expand...
Click to collapse
if i found a way for bypass the "service required" error.. maybe you need fastboot... I am working with a lenovo pad (Intel SoC) maybe can use his flash tool to work (need fastboot). But dont recognize my phone, ¿Maybe need a custom driver? i am working in that
Yes, RSD lite recognises bricked phones, but it tries to enter fastboot mode to flash anything, so we're stuck...
Good luck!
Bricked while flashing JB Radio to ICS
hy,
i did the stupid error of flashing a jb radio fw to a ics phone, now also with this tool i only get the message "service required / code corrupt"
anny idea?
btw.: i found a gui tool that does the same thing, there you can not only upload the firmware but also an operating system (you need a fw dnx and ifwi file and a os dnx and image file) anny idea where we could get the os files? i suppose flashing both (fw and dns) would unbrick the phone in all bricking cases.
i know it has already been said, but turn off your phone and keep the camera button pressed while connecting it (if you get the service required error). if the screen stays black just run the tool.
in my case flashing an ics fw dnx leads to the device corrupt message, and flashing a jb fw dnx leads to the black screen.
Boss, you are a good man for trying to help other people. Getting something like this working in the community would be brilliant, as I've tried to communicate to others. The most help I got was from outside the RAZR i forum, most here just don't give a sh1t in helping others. I have created 2 help threads to guide people - information to help prevent further cases.
I have concluded the same - that 'unbrick.bat' fixes some problems and creates a far bigger one - the service required, code corrupt problem. I wasn't sure if I could say that directly but I've a lot of messages in my inbox about this and almost everyone arrived at that after using that unbrick. How that is still available is incredible, since it's the biggest brick-creator on here that I know.
mercurio. said:
hy,
i did the stupid error of flashing a jb radio fw to a ics phone, now also with this tool i only get the message "service required / code corrupt"
anny idea?
btw.: i found a gui tool that does the same thing, there you can not only upload the firmware but also an operating system (you need a fw dnx and ifwi file and a os dnx and image file) anny idea where we could get the os files? i suppose flashing both (fw and dns) would unbrick the phone in all bricking cases.
i know it has already been said, but turn off your phone and keep the camera button pressed while connecting it (if you get the service required error). if the screen stays black just run the tool.
in my case flashing an ics fw dnx leads to the device corrupt message, and flashing a jb fw dnx leads to the black screen.
Click to expand...
Click to collapse
You can found Ifwi and dnx in your firmware folder... download a rds firmware and you found the two files. Upload and send me the gui-tool please!
So.. You cannot downgrading ifwi and dnx, but if you use ifwi and dnx (JB) with a ICS system, you got the black screen... so the black screen brick and "service required"brick are the same brick
SharpnShiny said:
Boss, you are a good man for trying to help other people. Getting something like this working in the community would be brilliant, as I've tried to communicate to others. The most help I got was from outside the RAZR i forum, most here just don't give a sh1t in helping others. I have created 2 help threads to guide people - information to help prevent further cases.
I have concluded the same - that 'unbrick.bat' fixes some problems and creates a far bigger one - the service required, code corrupt problem. I wasn't sure if I could say that directly but I've a lot of messages in my inbox about this and almost everyone arrived at that after using that unbrick. How that is still available is incredible, since it's the biggest brick-creator on here that I know.
Is your phone bricked in this condition right now? If it is, feel free to PM me.
Click to expand...
Click to collapse
My phone isn't bricked, i know people that unbrick.bat work right, but some people brick your phone, so i know this is a "Most devices problem" (Firmware problem, work for people that IFWI and dnx are extracted from the same firmware that are using)
Unbrick.bat provides a tool can flash some files (IFWI & DNX) to the phone (These files are responsible for the brick) and i only im working with the same tool that can solve the problem, unbrick.bat (or xFSTK-Downloader) is a good tool, but the use brick the phone, example: if i solve my downgrading brick , and i upload my files (Unbrick.bat with ifwi and dnx) this work only for people with use my firmware (example: Orange ICS), for other people that uses other firmware (Claro Argentina) the phone bricks and show "Service required blah blah blah" im trying to go back to the original "ifwi and dnx" files, some people on other forums says that the phone dont show anymore the "service required" error... but the phone only shows a green led (same thing that downgrading brick).
xFSTK-Downloader is used to update the Orange sandiego (First Intel Atom android, dont use fastboot) and Ienovo pad (Use xFSTK-Downloader-GUI, and a "Flashtool").
xFSTK-Downloader is like a Odin for intel phones. sorry for my english but if you know spanish pm me and can explain more
I read 80 pages in modaco for intel san diego and 40 for Ienovo pad, and they uses xFSTK-Downloader to update the phones.
Boss442 said:
You can found Ifwi and dnx in your firmware folder... download a rds firmware and you found the two files. Upload and send me the gui-tool please!
So.. You cannot downgrading ifwi and dnx, but if you use ifwi and dnx (JB) with a ICS system, you got the black screen... so the black screen brick and "service required"brick are the same brick
My phone isn't bricked, i know people that unbrick.bat work right, but some people brick your phone, so i know this is a "Most devices problem" (Firmware problem, work for people that IFWI and dnx are extracted from the same firmware that are using)
Unbrick.bat provides a tool can flash some files (IFWI & DNX) to the phone (These files are responsible for the brick) and i only im working with the same tool that can solve the problem, unbrick.bat (or xFSTK-Downloader) is a good tool, but the use brick the phone, example: if i solve my downgrading brick , and i upload my files (Unbrick.bat with ifwi and dnx) this work only for people with use my firmware (example: Orange ICS), for other people that uses other firmware (Claro Argentina) the phone bricks and show "Service required blah blah blah" im trying to go back to the original "ifwi and dnx" files, some people on other forums says that the phone dont show anymore the "service required" error... but the phone only shows a green led (same thing that downgrading brick).
xFSTK-Downloader is used to update the Orange sandiego (First Intel Atom android, dont use fastboot) and Ienovo pad (Use xFSTK-Downloader-GUI, and a "Flashtool").
xFSTK-Downloader is like a Odin for intel phones. sorry for my english but if you know spanish pm me and can explain more
I read 80 pages in modaco for intel san diego and 40 for Ienovo pad, and they uses xFSTK-Downloader to update the phones.
Click to expand...
Click to collapse
I found out that the tool I ment is the xFSTK-Downloader ( rghost.net/44421368 ) that was alreaddy linked here at xda by U1138 in: http://forum.xda-developers.com/showthread.php?t=2184877
And yes, i suppose the black screen only and the service required brick are the same. they probably are due to a not working combination of firmware (ifwi & dnx) and flashed OS (i suppose the fastboot, no idea how where to get the dnx file needed for flashing it). you can try different ifwi and dnx files and get different results (so far i think there are only two types, the ones for JB fw and the others for ICS).
If you flash your rom with RSD going from JB to ICS you also flash the ifwi & dnx files, but not the bootloader. Therefore you end up with a non working combination of firmware (ifwi) and OS (fastboot) => nothing starts at all.
This problem was easy to fix for me flashing the appropriate JB firmware.
Then I did the mistake of flashing the JB radio before flashing a JB rom. This lead to a situation where neither the JB (leads to service required warning) nor the ICS (black screen, green led on) firmware works anymore and I have no idea how i could change the situation.
Anyone has some ideas how to flash the fastboot with the xFSTK-Downloader?
mercurio. said:
Anyone has some ideas how to flash the fastboot with the xFSTK-Downloader?
Click to expand...
Click to collapse
+ 1
Everything else I was try with U 1138`s help - without result
St.Noigel said:
+ 1
Everything else I was try with U 1138`s help - without result
Click to expand...
Click to collapse
I read more than 120 pages in forums, and... NOTHING!
But i'm triyng to port a "flash tool" from lenovo pad... :silly:

[REF] [TOT] Stock Firmware Collection for Nexus 5 (D820 & D821)

I've decided to try and compile a list of the available stock firmware files for the Nexus 5 so that people have a "one-stop" for all of them.
Notes:
1) If you don't know what they are for, don't try to flash these files. For those that want to flash them, see the thread here by @bitdomo
2) If you are looking for Google's factory images for the Nexus 5, look here instead.
3) MD5s located on Dev-Host download page (when you click the link).
Standard disclaimer: I take no responsibility if you mess up your device by flashing any of these files.
Stock Firmware List (in order -- newest on top):
BIN_LGD821AT-00-V10b-NXS-XX-OCT-31-2013-KRT16M-USER-16G-0.zip - 438.69 MB
BIN_LGD820AT-00-V10a-NXS-XX-OCT-09-2013-KQS81M-USER-16G-0.zip - 414.01 MB
BIN_LGD820AT-00-V10a-NXS-XX-OCT-01-2013-KFS78N-USER-16G-0.zip - 418.25 MB
Mirrors are provided here courtesy of @hyelton
Credits & Thanks
houstonn
bitdomo
Reserved
Code:
BIN_LGD820AT-00-V10b-NXS-XX-OCT-31-2013-KRT16M-USER-16G+0.zip
Dont ask me how to get it, I wouldn't know
Someone just made me aware of these:
Code:
BIN_LGD821AT-00-V10a-NXS-XX-OCT-01-2013-KFS78N-USER-16G+0.zip
BIN_LGD821AT-00-V10b-NXS-XX-OCT-31-2013-KRT16M-USER-32G+0.zip
BIN_LGD821AT-00-V10b-NXS-XX-OCT-31-2013-KRT16M-USER-16G+0.zip
I only have filenames so i cant confirm they actually exist, but if they do then presumedly both 16/32gb versions exist along with D820/D821 versions.
Formally the D820/D821 are the same device as far as roms go, since the otas to KRT16M are the same for either model.
The filenames make it easy to fill in the blanks if there are others that exist though.
Any files for D821? We need a DLL file as well then we can flash it with LGNPST
Any news on a working LGNPST .DLL file for the N5?
pogi1100 said:
Any news on a working LGNPST .DLL file for the N5?
Click to expand...
Click to collapse
On this site there are rom files for D821 (non amercan modell of nexus5), and on this page there are the DLL files we need. (Maybe we can use DLL file for LG G2)
To download anything you have to register, but you need an invitation code from someone. You can buy invitation code, but you need a chinese credit card.
All DLL free!!
http://lgfirmwares.com/download/LG/DLL/
I downloading with "wget -r http://lgfirmwares.com/download/LG/DLL/" on Terminal
bitdomo said:
On this site there are rom files for D821 (non amercan modell of nexus5), and on this page there are the DLL files we need. (Maybe we can use DLL file for LG G2)
To download anything you have to register, but you need an invitation code from someone. You can buy invitation code, but you need a chinese credit card.
Click to expand...
Click to collapse
David_Vaz said:
All DLL free!!
http://lgfirmwares.com/download/LG/DLL/
I downloading with "wget -r http://lgfirmwares.com/download/LG/DLL/" on Terminal
Click to expand...
Click to collapse
Any idea which one the LG G2 uses?
EDIT: So the DLL is on this site. The name of the zip file is LGD820_20131023_LGFLASHv170.zip, can't find it anywhere else. Apparently it's only exclusive to that site. As far as I can tell, each download needs payment T_T. The signup itself is $10 from what I can tell. And the picture shows a special cable... I wonder if you need that as well...
pogi1100 said:
Any idea which one the LG G2 uses?
EDIT: So the DLL is on this site. The name of the zip file is LGD820_20131023_LGFLASHv170.zip, can't find it anywhere else. Apparently it's only exclusive to that site. As far as I can tell, each download needs payment T_T. The signup itself is $10 from what I can tell. And the picture shows a special cable... I wonder if you need that as well...
Click to expand...
Click to collapse
Actually we don't need that special cable. I testet that lg flash tool with my lg optimus 2x with an ordenary usb cable to flash firmware. If you look around the lg g2 forum you can see a topic about that how to go back stock with lg flash tool.
What we need is a dll file for d820 or d821 (maybe we can use an lg g2 dll file like in the case of nexus 4 and lg optimus g) and a firware file for both wariant. And we have to figure out which buttons have to be pressed on our turned off nexus 5 while we connect the usb cable to enter Download Mode.
Note that if you use lgflash tool you may loose your imei since that tool reformats everything, it is better to do an efs backup before you do anything.
Last thing. Don't try it if you can go to fastboot, because we don't know that will it work or just end up in a totalbrick. Only use it if you have no other options. Your phone does not turn on, you cant even go to recovery or fastboot. You may can go to Download mode and try to recover your phone with lg flash tool or lgnst. Then if it does not work you can send back to google to ask for a replacement device. Lie to google that you just left your phone on the charger and when you came back to your phone it was bricked.
Sent from my LG-P990 using xda app-developers app
bitdomo said:
Actually we don't need that special cable. I testet that lg flash tool with my lg optimus 2x with an ordenary usb cable to flash firmware. If you look around the lg g2 forum you can see a topic about that how to go back stock with lg flash tool.
What we need is a dll file for d820 or d821 (maybe we can use an lg g2 dll file like in the case of nexus 4 and lg optimus g) and a firware file for both wariant.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
That Chinese website I just linked has both firmware files for the 16GB/32GB D820 as well as another thread for the D821. It also has the DLL that we need (LGD820_20131023_LGFLASHv170.zip).
@pogi1100 and @efrant I managed to get the DLL for D820 from a firend (I think it should work for D821 as well). Maybe it works with LGNPST, but it definitely works with LG Flash Tool 1.8.1
bitdomo said:
@pogi1100 and @efrant I managed to get the DLL for D820 from a firend (I think it should work for D821 as well). Maybe it works with LGNPST, but it definitely works with LG Flash Tool 1.8.1
Click to expand...
Click to collapse
NICE. I will try this. Too bad my replacement device has already been shipped.
EDIT: Weird, not working for some reason. All I'm getting is "Device: Unknown mode" when I try to use the HS-USB QDLOADER mode on the device. I think we need the special cable outlined in this picture to put it into a special kind of download mode in order to flash it. Maybe soldering a 910K resistor to a microUSB cable would work, I just don't know which wire requires the resistor. I would try it, but my replacement device has arrived so I will leave it to someone else. This cable SHOULD work.
pogi1100 said:
NICE. I will try this. Too bad my replacement device has already been shipped.
Click to expand...
Click to collapse
I would not recommend it just if you dont have no other choice (including you can't RMA) to bring back your phone to life, but if you want to try it, then you are the only one who responsible for teh damagaes you cause .
Here is a tutorial how to use LG flash tool with lg g2. It does not mention the usb cable with 910kOhm resistor. Do the same just for the nexus 5 files , !!!BACKUP YOUR EFS!!!
If it works share your experiences, if it ends up a brick, then take my deepest sorry
Edit: @pogi1100 you have to put your phone into download mode by pressing and holding certain buttons and connecting usb cable maybe. (in case of nexus 4 you have to press and hold volume up and volume down and power button, maybe the same applies for nexus 5), and you also need to install lg drivers
bitdomo said:
I would not recommend it just if you dont have no other choice (including you can't RMA) to bring back your phone to life, but if you want to try it, then you are the only one who responsible for teh damagaes you cause .
Here is a tutorial how to use LG flash tool with lg g2. It does not mention the usb cable with 910kOhm resistor. Do the same just for the nexus 5 files , !!!BACKUP YOUR EFS!!!
If it works share your experiences, if it ends up a brick, then take my deepest sorry
Edit: @pogi1100 you have to put your phone into download mode by pressing and holding certain buttons and connecting usb cable maybe. (in case of nexus 4 you have to press end hold volume up and volume down and power button, maybe the same applies for nexus 5).
Click to expand...
Click to collapse
Download mode doesn't work for it with a regular cable. It needs that special cable since it's a newer LG phone. When I try to press all volume buttons while turning it on, my computer recognizes the phone as "Qualcomm HS-USB QDLoader 9008 (COM41)" which does no good in LG Flash Tool. LG has that special cable (extra resistance) so that it triggers the download mode on the N5 and allows for flashing TOT files through LG Flash Tool as seen here:
{
"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"
}
pogi1100 said:
Download mode doesn't work for it with a regular cable. It needs that special cable since it's a newer LG phone. When I try to press all volume buttons while turning it on, my computer recognizes the phone as "Qualcomm HS-USB QDLoader 9008 (COM41)" which does no good in LG Flash Tool. LG has that special cable (extra resistance) so that it triggers the download mode on the N5 and allows for flashing TOT files through LG Flash Tool as seen here:
Click to expand...
Click to collapse
Method used to achive download mode onnexus 4:
Hold down the volume up and down buttons for 2 (two) seconds on your Nexus, and continue to hold the volume up and down buttons while pluging in the USB cable which is connected to your PC. Continue to hold the buttons until the download mode screen appears.
Click to expand...
Click to collapse
maybe we dont need to push the power key
bitdomo said:
Method used to achive download mode onnexus 4:
maybe we dont need to push the power key
Click to expand...
Click to collapse
I've actually already tried that. I held the buttons for 2 minutes and all I saw was a black screen. The N4 is one year old so maybe LG decided that they didn't need special cables to put it into download mode back then.
pogi1100 said:
I've actually already tried that. I held the buttons for 2 minutes and all I saw was a black screen. The N4 is one year old so maybe LG decided that they didn't need special cables to put it into download mode back then.
Click to expand...
Click to collapse
I see... , then we have to make cables or buy it from ebay, but it is good thing that you could not brick your phone yet
Edit: @pogi1100 maybe you could try turning off the phone, then press only the volume up while you connect the cable, you could try do the same but with the volume down key. If LG G2 has the option enter download mode, then why should it be missing from nexus 5?
Hey guys, sorry I haven't kept up with this thread. For some reason, I got unsubscribed.
@bitdomo thanks for posting the files. I'm not entirely sure if the DLL for ht LG Flash Tool is the same as for LGNPST, but it doesn't hurt to try!
For everyone, yes, to enter download mode, hold volume up, and plug the device into your computer (not the ac charger). You should see a screen that says "download mode", and then shortly after, the screen will change to "Firmware update". Now you are in download mode. You should not need any other cables. The only thing is we need to find out if LGNPST can see the device using the LG Flash Tool DLL.
I personally don't have time to be testing all of this stuff out, so if you plan on doing it yourself, make sure you know the risks.
efrant said:
Hey guys, sorry I haven't kept up with this thread. For some reason, I got unsubscribed.
@bitdomo thanks for posting the files. I'm not entirely sure if the DLL for ht LG Flash Tool is the same as for LGNPST, but it doesn't hurt to try!
For everyone, yes, to enter download mode, hold volume up, and plug the device into your computer (not the ac charger). You should see a screen that says "download mode", and then shortly after, the screen will change to "Firmware update". Now you are in download mode. You should not need any other cables. The only thing is we need to find out if LGNPST can see the device using the LG Flash Tool DLL.
I personally don't have time to be testing all of this stuff out, so if you plan on doing it yourself, make sure you know the risks.
Click to expand...
Click to collapse
I dont have to phone yet, but if the phone really can go to Download mode by the key combination you mentioned, then it shoud work with LGflash tool. (At least it worked with Lg optimus 2x, I tried it yesterday. Firmware flashed correctly. So we dont need that 910kOhm cable to use lgflash tool)

[GUIDE] [ROOT] root LG L90 running D41510e or higher WORKS WITH LOLLIPOP AS WELL

Yah, so as the title says, ima show you how to root ur lg l90! The only reason im doin this is because @gdjindal's guide didn't work fer me. That runs v10e or higher WITHOUT DOWNGRADING. I'm not really sure if this works on previous firmwares, but let me know if it does :good:.
Firstly, the original tutorial is here: 1x1a.com/how-to-root-a-lg-optimus-l90-d415-10e.html
Code:
WARNING
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app
failed. Please view the original guide BEFORE looking at this
abridged version! YOU are choosing to make these
modifications, and if you point the finger at me
for messing up your device, I will laugh at you.
Download the files attached.
First things first: make sure you have USB debugging enabled (can be found in dev options in settings app) Install the drivers you downloaded.
Then, you should connect your phone to your PC/laptop (must be able to run batch files) in MTP (or your PTP equivalent) If prompted for USB debugging permissions on your phone, hit allow.
Now for the actual rooting.
Open the root script zip file, and extract it wherever you like. Extract the Drivers in this zip file and run the exe within. Then, open the folder and select the LG Root Script Batch file. Now just sit back and relax.
If you get a message saying that the serial port could NOT be found, then disconnect your phone and turn it off. Then WITHOUT TURNING IT ON, hold up the volume button and push in the USB cord. This should fix the problem. Once the process completes restart your phone manually.
Worked for me on a LG L90 D514 v10e . Thank you, as no other method would work.
I can confirm that this works as well, for D41510e firmware. Huge thanks, even though I jumped through all kinds of circles to get this device rooted lol(mainly due to the fact that none of my PC's run windows) Needless to say, I couldn't get the batch file to work via cmd prompt and WINE, so I had to do a fresh windows install. I'm going to try to write a shell script for any linux users out there that might run into the same problems as I did. If I have any success, I'll upload for the OP to include in original post. Thanks again!
Confirmed working on LG L90 D145 TMOBILE running official lollipop, with a tiny amount of editing to the batch file.
Nice !!!
CaptivateKing said:
I can confirm that this works as well, for D41510e firmware. Huge thanks, even though I jumped through all kinds of circles to get this device rooted lol(mainly due to the fact that none of my PC's run windows) Needless to say, I couldn't get the batch file to work via cmd prompt and WINE, so I had to do a fresh windows install. I'm going to try to write a shell script for any linux users out there that might run into the same problems as I did. If I have any success, I'll upload for the OP to include in original post. Thanks again!
Click to expand...
Click to collapse
Your very welcome on the guide. Never really superused linux before, got it on an old computer to make it run faster after xp got discontinued. Hope you can write the shell script and send me the modified files. The best of luck! :highfive:
silentpoke said:
Confirmed working on LG L90 D145 TMOBILE running official lollipop, with a tiny amount of editing to the batch file.
Nice !!!
Click to expand...
Click to collapse
Please sent me the edited batch file! Thanks in advance! :fingers-crossed:
Confirmed for D415 Lollipop
This method also worked to root the Lollipop update. Thank you. (I hate bloatware.) Anyone who is looking for a how and is already rooted with a custom recovery, just use Rashr or Flashify to flash the laf.img file again and use LG Flash Tool (2014 at least) to flash the D41520b_00.kdz to update to Lollipop, then use this method to root.
View attachment 3258647 View attachment 3258648
can someone help
can someone help me i did the script and im on lollipop i can acess supersu but i cant verify the root via root checker pro or use SCR pro. and my phone reboots to the tmobile logo
G33KSQUAD said:
Please sent me the edited batch file! Thanks in advance! :fingers-crossed:
Click to expand...
Click to collapse
1 thing edited because it couldn't find my phone
I had to manually enter in what com port my phone was on, I used lg flash tools to determine, I edited the com ports while script was running and hit save, and boom phone rooted in like 30 sec.
I Don't have Developer Options !
Errrrr, uhh ... sorry. Ahem ... I meant to say I don't have 'Developer Options or a Debugging defeat switch in my D415's settings.
Thanking you in advance,
New Guy
{
"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"
}
CaseyRockStar said:
I Don't have Developer Options !
Errrrr, uhh ... sorry. Ahem ... I meant to say I don't have 'Developer Options or a Debugging defeat switch in my D415's settings.
Thanking you in advance,
New Guy
Click to expand...
Click to collapse
Just go to about phone, software info, then repeatedly click on build # 7 times. It should say, congrats, you're a dev now!. Then go back to the main settings page and open the dev options. Icon should be like {} symbols. Then enable usb debugging, and click yes if it asks for authorisation when run the batch!
Keep an eye on Windows driver updates
Thanks for this! Just a note to keep an eye on the Windows driver notification in the taskbar. A lot of the hangups were that you had to stop checking Windows Updates for Drivers. Once I clicked that, the downloaded drivers were installed quickly and the script moved along.
Works!
At first I started to get scared because i had to retry the manual download and it says 0% and the computer is trying to connect and for the longest time i thought i did something wrong but it seems to be working!
I keep getting stuck at the Download screen. It doesn't ever seem to detect a com port. I guess I'll keep trying to see if something magically starts working lol
cliemonster said:
I keep getting stuck at the Download screen. It doesn't ever seem to detect a com port. I guess I'll keep trying to see if something magically starts working lol
Click to expand...
Click to collapse
Does it not detect it when you disconnect the USB, put phone in DL mode, and reconnect to USB? Should automatically detect the com port when you do that
Sent from my LG-D415 using XDA Free mobile app
cliemonster said:
I keep getting stuck at the Download screen. It doesn't ever seem to detect a com port. I guess I'll keep trying to see if something magically starts working lol
Click to expand...
Click to collapse
You may have to manually select your com port. Typically it's COM 41, sometimes 23, though.
xanscorp said:
You may have to manually select your com port. Typically it's COM 41, sometimes 23, though.
Click to expand...
Click to collapse
Thanks for the advice. I'll give that a try!
Nope... it just does not want to recognize it. As soon as I put it into download mode my computer just refuses to see it. I tried putting those com ports in manually and nothing. Maybe its a cable problem. I'll see if anything changes with a different cable.
Figured it out... it was the drivers. I thought I had the right set, but when I installed the drivers again from this post, all worked like a charm. I am now happily rooted, and thanks for all the good advice.
Successfully rooted today. It didn't detect the port automatically for me either, but following the instructions to hold volume up during boot got it there. I posted screen shots of the script and my phone. I thought the script failed because you can see where it says Special command ##, it was stuck there for several minutes and my phone showed no progress but it showed rooted in red letters. This might have been because I ran this script at a different time thinking it failed (originally from this guide http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951), but I forgot to run the supersu app once the phone rebooted.
Quick question. I ran it and it was fine up until it looked for a COM port. I manually put it in download mode, and it told me it was missing MSVCR100.dll
I downloaded it, I used one in Sys32, and I get an error when Send_Command.exe gets executed. Any help would be appreciated. This is a clean install of Win7 and I only used the attached drivers.
This work on lg g4?

Help needed, 'Your device has failed a routine safety check and will not boot.' after relocking BL

Hello everyone,
so I'll try and explain step by step what I, inexperienced guy, did, because from what I see I did absolutely everything to brick my V40... BUT maybe someone know what can I do to avoid having beautiful red paperweight.
I wanted to get HavocOS 3.5 on my phone. Until today I had stock Android 10, flashed by LGUP.
So in order to get the Havoc, I unlocked the bootloader the official way, thru LG developers site. Then I tried to get TWRP working and it might be the problem (more on that later). So, in order to get TWRP one of the steps was to fastboot boot TWRP-judypn-boot.img. I did that but didn't know that to do next (cause when I did it the phone booted normally and I didn't fully understood what now), so I abandoned the idea and just loaded the backup from LG Mobile Switch. But, then I realized that with having unlocked bootloader I won't be able to use google pay, so after some reading I found out that Magisk might be the answer (it wasn't) so I managed to get Magisk root on my device. When I found out that it didn't help with google pay i tried to do what others on forum warned me not to - RElock the bootloader using 'fastboot oem lock'. And now it has locked bootloader. But also now of course the phone is rather bricked in a way that: I can enter both fastboot mode and download mode but: trying fastboot something I get the info that it is not possible in Lock State, and when trying to just flash kdz of that stock android 10 that I started with, the LGUP says error 'error 0x6004 crossDL' and below that it mentions 'judypn_lao_eea>@judypn_lao_co' so probably that first fastbooted img now prevents it from beign flashed. So now I cannot fastboot or flash anything, and trying to boot the phone gives me error "Your device has failed a routine safety check and will not boot." and also sometimes, below 'All slots are unbootable'.
I know that I screw up multiple times, first time not recognizing that unlocking BL would cut off a function crucial for me, but is there a way to fix all this?
AnDevil said:
Hello everyone,
so I'll try and explain step by step what I, inexperienced guy, did, because from what I see I did absolutely everything to brick my V40... BUT maybe someone know what can I do to avoid having beautiful red paperweight.
I wanted to get HavocOS 3.5 on my phone. Until today I had stock Android 10, flashed by LGUP.
So in order to get the Havoc, I unlocked the bootloader the official way, thru L<brevity>imes, first time not recognizing that unlocking BL would cut off a function crucial for me, but is there a way to fix all this?
Click to expand...
Click to collapse
Sounds kind of messy. Two things to know; 1) u most certainly can have google pay working on v40 w/10. I just added it on my (orig at&t) korean 10 30e / rooted / magisk / twrp. And 2) u should never ever try to relock the bootloader unless you just flashed a stock kdz to the device (completely unmodified, don't even choose language when it boots).
So the prob is what to do now. I'd first try to use fastboot to switch slots and see if the other side boots? And if that doesn't work / achieve what you want, then use lgup with dll version 1.14 to do the 'cross flash' (the 1.16 version doesn't work for that). Be sure to do a part DL (if u do the crossflash), then do a refurbish with the same kdz just after the part DL (of course you let the part DL complete, just shut it off after it boots all the way), then do refurb.
Ideally, what are u trying to accomplish?
cheers
Well, for now I would want to have bootloader locked, stock Android 10 on there. I'm probably going to leave the modding cause of the mess I've made - especially that I don't have much free time to tinker with phone when things go bad (and also as You can see I don't have enough experience to do so).
Right, so back to the point. How do you switch slots in fastboot? If by 'fastboot set_active a' (or b), then the result is 'not possible in lock state'. And for the other part (with LGUP and crossflashing), can You provide some kind of idiot-proof tutorial for that? Which files should I download and try to flash on the phone?
OK, i *think* that I partly know what to do. Unlike You wrote, the 1.14 LGUP doesn't let me do anything with phone, saying that it needs at least 1.16 to work. When I downloaded 1.16 (the one with which I flashed the android 10 back in september, from the topic https://forum.xda-developers.com/t/guide-lgup-for-all-no-root-needed.3967858/unread) I click on the 'PARTITION DL' option and after 4% it asks me to select a partition. And here I don't know that to select, because there are so many options and I'm afraid to move with any of them to not screw things up even more.
Oh, and the file which I try to flash is stock european android 10, 30b.
AnDevil said:
OK, i *think* that I partly know what to do. Unlike You wrote, the 1.14 LGUP doesn't let me do anything with phone, saying that it needs at least 1.16 to work. When I downloaded 1.16 (the one with which I flashed the android 10 back in september, from the topic https://forum.xda-developers.com/t/guide-lgup-for-all-no-root-needed.3967858/unread) I click on the 'PARTITION DL' option and after 4% it asks me to select a partition. And here I don't know that to select, because there are so many options and I'm afraid to move with any of them to not screw things up even more.
Oh, and the file which I try to flash is stock european android 10, 30b.
Click to expand...
Click to collapse
Okay, just so that it's clear, you do want to use 1.14 when going from 8 or 9 to 10. 1.16 won't recognize the older OS.
But, if you'd have done 1.16 Part DL from the beginning, it would have worked, as you've discovered. When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them).
Because you want to flash ebw 30b, there shouldn't be any reason to select all partitions. But I'd suggest (again), after doing the part DL, let the phone reboot of course, to complete. Then just shut it off and go back to LGUP and do a refurbish this time of the exact same kdz.
good luck
Ok, now I'm confused
I always used the 1.16, never the 1.14. And before I had tinker with phone I already had Android 10 installed (which I installed via 1.16). I Think that someone made a patch for 1.16 to work with Android 9 when I made that transition.
Ok so You wrote that
"When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them)"
and below that You wrote
"there shouldn't be any reason to select all partitions"
so that part I don't understand.
Is it:
1. Connect phone in download mode to LGUP 1.16
2. Choose 'partition DL' And select all of them
3. Let it finish and the phone will reboot
4. Right when it boots to welcome screen shut it off
5. Enter download mode once again
6. Flash with 'refurbish' the 30b software
Are these steps correct?
AnDevil said:
Ok, now I'm confused
I always used the 1.16, never the 1.14. And before I had tinker with phone I already had Android 10 installed (which I installed via 1.16). I Think that someone made a patch for 1.16 to work with Android 9 when I made that transition.
Ok so You wrote that
"When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them)"
and below that You wrote
"there shouldn't be any reason to select all partitions"
so that part I don't understand.
Is it:
1. Connect phone in download mode to LGUP 1.16
2. Choose 'partition DL' And select all of them
3. Let it finish and the phone will reboot
4. Right when it boots to welcome screen shut it off
5. Enter download mode once again
6. Flash with 'refurbish' the 30b software
Are these steps correct?
Click to expand...
Click to collapse
Sorry yes, that should have been 'there shouldn't be any reason NOT to select all partitions' (I think that's what the 'context' of the whole comment implied').
Yes, those steps are correct.
I think the confusion about lgup is around this; 1.14 is used if u need to 'cross flash' (going to diff OS). If you're not cross flashing then 1.16 will work. I think most people are cross flashing due to desire to get rid of bloatware and / or wanting to move to A10 when their OS doesn't have it or the kdz is unavailable.
you are in a somewhat unusual circumstance, having the only version of v40 that lg actually allows legit unlocking. So you never cross flashed (had to re read to realize that, it's that uncommon).
good luck
OK, so unfortunately it didn't help, giving the same error as when I try to 'refurbish'.
{
"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"
}
So it has to do something with me fastbooting the TWRP img (it's indicated by the name of it).
Seems to me that I should change the img for a stock one (if there is one that's stock) but then again, fastboot probably will end in error 'not possible in lock state' as I tried to fastboot other img's and it gave me that error.
AnDevil said:
OK, so unfortunately it didn't help, giving the same error as when I try to 'refurbish'.
View attachment 5190441
So it has to do something with me fastbooting the TWRP img (it's indicated by the name of it).
Seems to me that I should change the img for a stock one (if there is one that's stock) but then again, fastboot probably will end in error 'not possible in lock state' as I tried to fastboot other img's and it gave me that error.
Click to expand...
Click to collapse
So here's what I'd suggest, because you have an ebw version, which I believe has dual sim, and many many have had issues with those and losing the dual sim capability (very frustrating and difficult to get back).
Go to the v40 rom forum and Markus (los developer), put in the first post of his lineage rom an invite to the lgv40 tele gram group. Use that and join tele group and there are a lot of international users there, they can guide you with this problem (they have and use that specific device, among others).
If you want to do more reading on this, follow this link. It's the lg firmware dl page and do a search from the top for 'judy'. You'll see others have had the same error you're getting, and used lgup 1.15 command line to get around it.
I don't think it's because of what u flashed with fastboot (twrp), judypn is the name of the device, not specific to twrp.
So join the tele group and also (here on xda) look in the thread about 'unlocking all devices - except t-mo'. Not to unlock it, but to learn to use qfil. You will probably need that.
cheers
Ok, definitely will do that. Thank You very much for Your help

Question Cannot register a new fingerprint in OnePlus 10 PRO

Hi
I bought a new OnePlus 10 PRO from Aliexpress. Its a CH version that the seller installed on it a global rom.
In the first setup of the phone, When I get to setting the fingerprint, I am unable to set it. I get the following:
{
"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"
}
I tried updating the phone, I tried factory reset... its always the same.
Any idea?
Thanks !
Are you sure that he installed the global rom? With model is yours NE2213 ? I bought from them also but I don't have this issue.
Anyway, you can try to use Oxygen Updater, to check if there is an update for your device or since your device is reseted, you can install ColorOS back
Hi,
I am on NE2215. Using Oxygen Updater I see that I have the most up to date version.
Not sure exactly how to install ColorOS.. I do want to have the regular OS that I would have as if I bought the global version (which i guess this is what the global rom mean..)
Right, I agree with you. I recommended to install the coloros just to check if it's a compability issue.
You can try to reinstall you version and see what happens, just download it and flash it again.
ok, and now for someone that have no idea how to do it?
If yours is NE2215 A13 you can download the ota file from this link: https://android.googleapis.com/packages/ota-api/package/7548d30abac02bde85a403bcc3a218df868e1910.zip
Then put it in your phone root and from your device Settings -> About the device -> Click on the option to check for the update -> 3 dots menu -> local installation and chose this package. It will start the installation.
Thank you for your help !
Downloaded and copied into my device files.
However - When I go to "About device" and click on the "up to date" button to search for updates, it just tells me I have no updates and i see no 3 dots to go for local installation:
What am I missing?
I think it's obvious that something went wrong during the region change, this issue was prevalent on the 8 pro and was extremely difficult to fix.
Check out the 8 pro threads you'll be sure to see it. It's a partition iirc and if it's borked then it simply will not work..
I can't remember the name of it off hand but have a look and I'm sure you can get an idea of what may be wrong, specifically that partition.
Overall it's difficult to say as you've got a region changed phone, have you asked the seller what they did? If it is indeed as difficult as it was on the 8 pro to fix and seeing as you may be the only person experiencing this (far as I know) then I'd consider returning it.
You could re-flash the entire OS via fastboot enhance but that would also bring with it inherent problem's, if it's new then I guess the question you need to ask yourself is it worth it?
Did you save much money getting that converted variant?
dkaro said:
Thank you for your help !
Downloaded and copied into my device files.
However - When I go to "About device" and click on the "up to date" button to search for updates, it just tells me I have no updates and i see no 3 dots to go for local installation:
View attachment 5624305
What am I missing?
Click to expand...
Click to collapse
This page is from android play services. You need to click on the first banner
@dladz TBH I bought it for around 70% of the price I would pay locally.. So yea, it was much cheaper. I also had before OP9 global rom and had no issues with it.
Maybe indeed as last step its worth trying to reinstall everything again.. I'm just not sure how to do it. I cannot find the local upgrade option as advised above, and after googling a bit how to do it using ADB, when i try to run fastboot oem unlock - the CMD will just show me forever "< waiting for any device >" (and this is although I was able to communicate with my device using "adb devices" and I got back my device id.
@zopostyle I did click on that banner you're showing and I got to the page I showed you before..
I'm clueless
If that is the page showing I'm assuming you're on a gsi ROM and not oxygen os.
Now it's better to reinstall OxygenOS completely because it doesn't seem to be the ROM you're running.
Search here on xda to unlock your bootloader and then you need to find the zip with the full ROM for you device and install it from fastboot as mentioned.
OK, i'm trying to unlock my bootloader but as I mentioned:
dkaro said:
and after googling a bit how to do it using ADB, when i try to run fastboot oem unlock - the CMD will just show me forever "< waiting for any device >" (and this is although I was able to communicate with my device using "adb devices" and I got back my device id.
Click to expand...
Click to collapse
Any idea what am I doing wrong?
I tried several tutorials online and so far I found no tutorial that will actually give me step by step that each step is actually working..
Maybe it's missing the drivers. Try this https://gsmusbdriver.com/oneplus-10-pro
dkaro said:
@dladz TBH I bought it for around 70% of the price I would pay locally.. So yea, it was much cheaper. I also had before OP9 global rom and had no issues with it.
Maybe indeed as last step its worth trying to reinstall everything again.. I'm just not sure how to do it. I cannot find the local upgrade option as advised above, and after googling a bit how to do it using ADB, when i try to run fastboot oem unlock - the CMD will just show me forever "< waiting for any device >" (and this is although I was able to communicate with my device using "adb devices" and I got back my device id.
@zopostyle I did click on that banner you're showing and I got to the page I showed you before..
I'm clueless
Click to expand...
Click to collapse
I feel you buddy.
You can use the app in my Magisk guide to do local installs.
Unlocking the bootloader you need to type fastboot flashing unlock
I haven't had to change region myself, but I did make a thread for someone else where the process was listed, think I called it changing Chinese firmware iirc.
If it's just a case of a re-flash of the firmware you're on, it's not that difficult.
Just use oxygen updater and grab the full firmware then do the local update using the app I mentioned above (listed in my Magisk/root guide)
I've never done this when not having the bootloader unlocked personally, but you can unlock and that'll wipe your phone with the recovery already on your device.
Only issue I have going down these routes is what else is missing? Do any of these processes stand up if we can't rely on the integrity of the OS that someone has put on and made a balls of it?
Sorry I know you may not agree but 30% is a small price to pay to avoid a brick and bring stability..
But that's me
zopostyle said:
Right, I agree with you. I recommended to install the coloros just to check if it's a compability issue.
You can try to reinstall you version and see what happens, just download it and flash it again.
Click to expand...
Click to collapse
That is a seriously good shout and would explain the fingerprint.
Hi guys, thank you again for helping me.
I tried installing again the uSB drivers, and ran again "fastboot flashing unlock" - it still telling me:
As far as I understand I have to unlock it for next step, right? (either for resetting back to colorOS or reinstalling oxygen)
I will try later tonight the other method (this magisk thing) - is this the link you're talking about?
Can you please also give me a link to download the full most up to date global Oxygen version and the CH Color one? i'll try both
Thanks !
For OxygenOS there is no A13 full yet...so you have to download A12 from this link: https://gauss-componentotacostmanua...22/03/24/a9f9e7ec682744c2ba606a366df587ac.zip
Source: https://www.xda-developers.com/oneplus-oxygenos-12-android-12-update-tracker/#oneplus10pro
The chinese one is hard to find, if I find it I post the link here...
Also this thread might help you: https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585
zopostyle said:
For OxygenOS there is no A13 full yet...so you have to download A12 from this link: https://gauss-componentotacostmanua...22/03/24/a9f9e7ec682744c2ba606a366df587ac.zip
Source: https://www.xda-developers.com/oneplus-oxygenos-12-android-12-update-tracker/#oneplus10pro
The chinese one is hard to find, if I find it I post the link here...
Also this thread might help you: https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585
Click to expand...
Click to collapse
Really is odd about them not being full... They're massive compared to conventional incremental updates. 4.05GB that's a hell of an incremental.
Haven't had to do it myself and it's sightly off topic but is the full version you'd use to recover a phone albeit without a functional MSM?
So fastboot flashing?
Cheers
Hi again,
So, i'm trying to follow the tutorial here. I got stuck already in the first step - I cannot extract the boot file using Fastboot Enhance:
This is although in this link I have downloaded a full version (EU version (NE2213_11.A.13)).
What should I do next please?
dkaro said:
Hi again,
So, i'm trying to follow the tutorial here. I got stuck already in the first step - I cannot extract the boot file using Fastboot Enhance:
View attachment 5624521
This is although in this link I have downloaded a full version (EU version (NE2213_11.A.13)).
What should I do next please?
Click to expand...
Click to collapse
As @zopostyle said earlier.. you'd need to use 12 mate. As that's the only full version available...13 won't cut it...you can extract the images using the button that says allow incremental, that's useful for extracting boot images for rooting.
But there's a reason why that's there, it's so you don't go ahead and flash it.... According to @zopostyle 12 is the only full version so that's what you would need.
Again I've not done this myself so perhaps wait for someone else to chime in what to do next.

Categories

Resources