Develop Bugs

EVO on life support

Dear XDA Community,
This post will be as detailed as possible for those who enjoy detail.
It’s about the problems my EVO has been experiencing over the past 3 months and, after trying to fix the problems though IRC it seems that the attention should be brought to the forums for a larger audience. It was 3 months ago when I flashed a rom ( cannot remember the rom ) and my EVO took a turn for the worst.
What Happened :
When the rom was flashed and booted for the first time everything seemed normal but, the rom started to freeze at random. At first I though it was a normal process due to new ROM’s installs but, it kept repeating it over and over until it went into a boot loop syndrome.
Prior to these problems I did my daily clean/wipe dalvik rituals for ROM consumptions.​
After 15 - 30 boot-loops my battery dies and the crusade begins.
I begin looking for another ROM to flash, to rid the sickness the previous ROM infected my EVO with. I installed my favorite (SalvageMod) and, the problems began to show. Salvage installed perfectly fine (as always) but, my phone started to lag, the speed was reduced to about 35 - 50%. It’s noticeable big time. The camera stopped working and everything seemed to be falling apart.
(RECENT)In panic I started looking for ways to RUU so I can avoid any other problems. This is when I noticed that usb was not accessible. I couldn’t mount my device; [CLICK HERE FOR VIDEO], so I used a SD card reader to RUU my phone and get it back to stock.
Phone is back on stock settings but, no root and, without usb support revolutionary.io is lightyears ahead of my time.


Problems :
Not mountable through usb cable [SD Card Reader option / Software Error]
System lag noticeable slower (BestBuy rep even confirmed its unresponsiveness)
Device will not charge when on [Either mount / Software Error],
Camera problems.
[Click Here For Second Video]
{
"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 can you guys help a member get his EVO back in business, my wallet would greatly appreciate it.
Thanks,
samthewildone
Aspiring Mathematician

​

Well, the easy way out is that now that you're back on stock and a rep has agreed the phone is not working properly and you have no USB, trade it in

I would right click on that device and uninstall the drivers. then hook the phone up to the PC and see if it automatically installs the correct drivers or find better drivers.
This may have been covered, and it looks like there's a lot more going on then just drive issues, but to get this phone into a state in which you can root it and wipe it again, you need to eliminate that variable.
Not saying that the USB drivers are even an issue, but its something worth exploring first and foremost.

Tried that, as in my thread. I uninstalled and reinstalled drivers and, it just keeps showing what that picture shows above. The phone isn't damaged but, the software is borked due to a bad bad kernel or ROM flash.

Not a solution to your problem, but if you are still s-off then you don't need Revolutionary. You can put a PC36IMG of a (reliable, ie Amon Ra) recovery on your SD card. From there you can wipe thoroughly and try flashing something else.
Unfortunately it seems like some sort of hardware failure, so the only fix could be getting a replacement.
Supersonic Evo 4G | MIUI | Tapatalk

Seems like you've gone through the same steps I would've gone through to fix it. Apart from the possible driver issue the phone should still charge when plugged into a wall charger. The fact that it doesn't, in tandem with the inability to access USB via computer, tells me that most likely you've got a hardware failure. Take it to Sprint and get a replacement. Problem solved.

Bricked LG G3 - Need help!

Hi guys, I recently decided that i would root my phone and try and install cyanogenmod (new to me) as my phone seemed quite sluggish with LG's own bloatware on it. I followed the steps from LGG3ROOT and everything seemed to work well, and at the last stage when it asked me to then remove my battery and restart the phone... the phone just stayed on the lg page - never logging into the android system.
Ive tried to plug the device into multiple machines and each time the machines have issues with the device and it says the device has issue starting (10).
Im not really sure what else i can do as the phone seems bricked. Any help would be very much appreciated as i need access to the phone and i assume the warranty is now void.
Thanks in advance.

Walshinho said:
Hi guys, I recently decided that i would root my phone and try and install cyanogenmod (new to me) as my phone seemed quite sluggish with LG's own bloatware on it. I followed the steps from LGG3ROOT and everything seemed to work well, and at the last stage when it asked me to then remove my battery and restart the phone... the phone just stayed on the lg page - never logging into the android system.
Ive tried to plug the device into multiple machines and each time the machines have issues with the device and it says the device has issue starting (10).
Im not really sure what else i can do as the phone seems bricked. Any help would be very much appreciated as i need access to the phone and i assume the warranty is now void.
Thanks in advance.
Click to expand...
Click to collapse
can you post
the guide that you used to root
your phone variant
and whether it boots into download mode
what firmware version you were running

the guide i followed was this (exactly) http://highonandroid.com/android-smartphones/how-to-root-lg-g-flex-2-g2-g3-on-lollipop/
i have a UK D855
I can get it to download mode (but cant get to recovery with the power and down buttons)
unsure exactly which firmware, i hadn't played around with the phone until this happened.
when i let the phone get stuck on the lg page the windows pc seems to recognise the device, if i put it in download mode it comes up with the device error that it is there but cannot be run.
Thanks.

You probably have either
1) A bad usb cable
2) Or your drivers arent properly installed
You are plugging it into a USB2.0 port right?

I installed the drivers from the universal LG driver tool from their site, it worked find with the phone (or so it showed) before this issue, i've also tried a different cable and a different machine for it to come up with that same driver problem (10). Ive also tried uninstalling the driver software and reinstalling, is there a way to get rid of all traces of the bad drivers? thanks again for replying

Error Image
{
"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"
}

Working Fine
This is when the device isn't put into download mode and instead is left to try and boot (where it is stuck on the LG 'life's good' page).

Any idea guys? Im having no luck with any info im getting online at the moment and i'm really in need of this phone to work.
Thanks in advance.

Can you expand the "android device" section.
See if it's android adb

sorry, i think i quite understand. Which part should i expand on?
Thanks

In
device manager, look up Android device.

Update
The phone will now only go straight to firmware update and will never go or show the download mode as it has before. This is causing my LG Flash Tool to come up with 'cant change to download mode' and im not sure why or how this has happened.

The phone is now appearing fine on the device list. Its just the last of download mode. Is there a way to force it in cmd?

Please some screenshot again. The one I linked would be fine for adb

I see you can boot on download mode, so you can restore your G3 by applying a kdz firmware with flashtool2014: http://forum.xda-developers.com/showthread.php?t=2785089
On download mode the G3 is recognized only in ports (com&lpt)

I bricked my G4 H812. No download mode, nothing on screen, only QHSUSB__BULK.

So I messed up flashing the rooted system.img:
Code:
dd if=/data/media/0/system.rooted.img bs=8192 skip=65536 count=548352 of=/dev/block/mmcblk0
I used skip instead of seek
{
"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 I've wiped out the partition table and pretty much everything.
The good news is I have a backup of the entire /dev/block/mmcblk0 that I made before attempting to modify anything, so hopefully it's possible to recover, if I knew how...
When plugging the cable in, the phone appears as QHSUSB__BULK device in Windows, and "qcserial ttyUSB0: Qualcomm USB modem converter" in Linux. Otherwise, nothing happens. Whether I have battery/SD card inserted or not, holding volume up or any other buttons, there's no response at all. Blank screen, no LED, no vibrate, it does absolutely nothing. The only thing it will do is reconnect if I hold the power button for several seconds. fastboot.exe doesn't detect any devices. Windows device manager doesn't list any disks except the computer's actual hard drive.
I'm sure there must be some way to recover it using this QHSUSB__BULK mode, but I haven't found anything.

I'm in the same boat as you, but with H815. With proper drivers your device will be recognized as a Qualcomm 9008, I think. I have very heavily researched this, and unfortunately, there is no available way to recover. For G2 and G3, there was a tool called BoardDiag. Perhaps this will at some point be made compatible with G4.

I've heard about these drivers and BoardDiag but haven't found them. Maybe tomorrow I'll look for them more... otherwise I can probably take it to the shop under warranty, but I worry they'll give me back a new one with a new firmware and I'll have to wait for another root exploit... :|

Silly question that won't help you fix your problem but... Why did you type out that? Why not just copy paste?
Sent from my Nexus 7 using Tapatalk

Try this no promises
I did the same thing with my G2 and followed this guide to restoring it.. It may work for the G4 as well if you have or can get the image files for your device...
http://forum.xda-developers.com/showthread.php?t=2582142

tobesedated said:
I did the same thing with my G2 and followed this guide to restoring it.. It may work for the G4 as well if you have or can get the image files for your device...
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
No good. I don't get any /dev/sd* when I plug it in. Only /dev/ttyUSB0. Unless that serial port somehow is actually a storage device, but that seems unlikely...
Copy/paste would have been a good idea!

RenaKunisaki said:
No good. I don't get any /dev/sd* when I plug it in. Only /dev/ttyUSB0. Unless that serial port somehow is actually a storage device, but that seems unlikely...
Copy/paste would have been a good idea!
Click to expand...
Click to collapse
Stupid question but you are using linux to try this right? I don't know that it will work in Windows

Yes, I'm using Linux, and I also have a Win7 box to play with.
Anyway I took it in for repair under warranty, so just have to hope there's no problem...

RenaKunisaki said:
Yes, I'm using Linux, and I also have a Win7 box to play with.
Anyway I took it in for repair under warranty, so just have to hope there's no problem...
Click to expand...
Click to collapse
lemme know how that goes, im sitting on a brick too. i just figured id wait a few weeks see if any fixes pop up before i send back to lg. i meant to zero out laf.img to access fastboot mode to try oem unlock on ls991, but im a dummy and got way in over my head and deleted aboot by accident. my windows xp netbook doesn't even see a qualcomm device. i havent tried on the raspberry pi yet. the only response i can get from the phone is a battery symbol with a ? , and onlyif i plug in usb from pc with no battery in the phone

Yeah, I heard some people wouldn't get the Qualcomm device popup, but would get the question mark battery icon. For me it was the opposite; the device shows up (as QHSUSB__BULK in Windows and ttyUSB0 in Linux) but absolutely nothing on the screen no matter what I do.
My guess is because some people only wiped out laf or aboot or a couple other things that are used later in the boot process (so it will boot, but fail quickly when it can't find them), whereas I wiped out the entire partition table, so the very first step fails; probably the hardware itself (the modem, CPU, or who knows), upon not finding a bootable partition, goes into some backup mode where it can be flashed over USB. (Just nobody seems to know how to flash it from there...) Or the very first sectors of the MMC contain the actual stage 1 bootloader (I noticed partition 1 starts at sector 32768, so some 16MB at the beginning is unaccounted for), and that code is responsible for disabling the QHSUSB__BULK mode, but having wiped out even that, it stays enabled. (Possibly another way for root/unlock if someone examined it closer...)

Yeah no easy way you need a direct flashing eMMC tool

I'm guessing no one managed to fix their brick? Same thing happened to me after attempting to revert to an earlier version bootstack.zip.
From my reading of G3 unbricking, the attempted-downgrade flag got tripped and so it's in the same 9008 state. Without access to the LG supplied .mbn files, there's no way to do any sort of fix. i.e. this problem could be easily fixable, just not by anyone without LG tech tools.

Contact @vn_mobile

Has a system image been posted? I'm kinda in the same boat...

dd if=/data/media/0/system.rooted.img bs=8192 skip=65536 count=548352 of=/dev/block/mmcblk0
Click to expand...
Click to collapse
mean 3955228672 byte (~ 3.9GB) of eMMC (mmblk0) is CLEAR
If can go to my country i can recovery for you or

Hi,
Read this web pages.
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/
http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/
http://www.androidbrick.com/lg-g3-hs-usb-qdloader-9008-unbrick/
http://www.androidbrick.com/unbrick...oader-9008-if-you-have-the-right-kind-of-rom/

Looking at some of the other posts on here, I think the only thing to do at this point is hope you still have warranty.
(Not really sure how I'll fare though, I just got this one as a replacement for a bootlooping G4 yesterday)

I did the same thing to my g4... I still can't find any solutions to unbrick it. Luckily I found another one on craigslist for cheap so I went ahead and bought it... Not ****ing around with it though I learned my lesson the hard way ... At the mean time I'll probably end up selling my bricked one for parts on ebay

xxxwalo said:
I did the same thing to my g4... I still can't find any solutions to unbrick it. Luckily I found another one on craigslist for cheap so I went ahead and bought it... Not ****ing around with it though I learned my lesson the hard way ... At the mean time I'll probably end up selling my bricked one for parts on ebay
Click to expand...
Click to collapse
This phone isnt even a year old yet... why would you buy another instead of sending it off to LG for Warranty repair. There are a lot of these that have bricked from OTA update.

If someone simply post the AP Chipset driver for BoardDiag.exe to start, it will be solved....
I solve my G3 with BoardDiag.exe and flashing all original image partition extracted from TOT file.... But I can't find any AP CHipset that support G4 yet.

LG-H815T S/N 512xxx won't boot (but not in bootloop) - all stock, no modifications

I was just using the phone normally for browsing when it rebooted and after the LG boot splash the phone died (no screen, no lights). I have to take the battery out in order to boot it again but it goes to black screen after splash screen - its not in a boot loop however. I can get into LG's recovery but the only option is to factory reset which I don't want to try yet in case I can recover my data. After searching around for other things to try, I found I can get into Download Mode, however its not detected by LG Mobile Support Tool at this point. When the phone appears dead it actually shows up in windows as 'qualcomm hs-usb qdloader 9008' (not much I can do with this as far as I can tell).
There are lots of threads about the bootloop problem that affected 505xxx serial number devices but mine is 512xxx - only about a year old, so I'm not sure this will be the same thing.
If anyone thinks there is anything I can try to recover files please reply back. I'm going to get in touch with LG support and put the phone in the freezer in the mean time to see if I can boot it after...

Its a hardware issue. They all are.
Every one is its own story but in the end she just wont boot

zeroid said:
I was just using the phone normally for browsing when it rebooted and after the LG boot splash the phone died (no screen, no lights). I have to take the battery out in order to boot it again but it goes to black screen after splash screen - its not in a boot loop however. I can get into LG's recovery but the only option is to factory reset which I don't want to try yet in case I can recover my data. After searching around for other things to try, I found I can get into Download Mode, however its not detected by LG Mobile Support Tool at this point. When the phone appears dead it actually shows up in windows as 'qualcomm hs-usb qdloader 9008' (not much I can do with this as far as I can tell).
There are lots of threads about the bootloop problem that affected 505xxx serial number devices but mine is 512xxx - only about a year old, so I'm not sure this will be the same thing.
If anyone thinks there is anything I can try to recover files please reply back. I'm going to get in touch with LG support and put the phone in the freezer in the mean time to see if I can boot it after...
Click to expand...
Click to collapse
If you like give this test a try. I don't know if it works with a defective mainboard but testing costs nothing..
Download FWUL and boot it (https://tinyurl.com/FWULatXDA).
Then go into the download mode on your g4.
Then open the folder LG in FWUL and open a LGlaf shell.
If you see the prompt in a black terminal ok. If not use the other shortcut with auth in its name. You may have to start the LG laf shell 2 or 3 times sometimes...
If you see the black terminal prompt type in the command:
ls
It should give you a list of files and folders. If not there's something wrong.
If you have luck you can then backup your data.
You need an external SD card to store your data.
I have no access to download mode atm but if you want to test this let me know and I can prepare the rest in a day or 2.
.
Sent from my LG-H815 using XDA Labs

Ok thanks for the offer. I should be able to have a go later today. After I froze the phone for 20 mins it got a bit further - the jingle you get at boot occurred but unfortunately it all died before it got anywhere near my homescreen. Its back in the freezer now.
I'm amazed it can go from working perfectly to a brick instantly, but I guess ifs its a physical connection that is broken on the motherboard...

zeroid said:
Ok thanks for the offer. I should be able to have a go later today. After I froze the phone for 20 mins it got a bit further - the jingle you get at boot occurred but unfortunately it all died before it got anywhere near my homescreen. Its back in the freezer now.
I'm amazed it can go from working perfectly to a brick instantly, but I guess ifs its a physical connection that is broken on the motherboard...
Click to expand...
Click to collapse
You can't fix the mainboard issue by your own. The only chance is getting a replacement by LG.
The freezer method is good for a last backup of your files but don't do it often it is not good for your phone.
.
Sent from my LG-H815 using XDA Labs

Yeah I know, was just hoping to backup a fews things I don't have, SMS messages, some apps configuration that don't sync settings online already....

zeroid said:
Yeah I know, was just hoping to backup a fews things I don't have, SMS messages, some apps configuration that don't sync settings online already....
Click to expand...
Click to collapse
Well then try it with FWUL.
I just need to test the right commands first..
.
Sent from my LG-H815 using XDA Labs

So I got FWUL booted but can't find an LG folder nor LGlaf Shell?
adb devices is working in a terminal.

zeroid said:
So I got FWUL booted but can't find an LG folder nor LGlaf Shell?
adb devices is working in a terminal.
Click to expand...
Click to collapse
Do you have downloaded the latest version? Directly on the desktop?!
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Do you have downloaded the latest version? Directly on the desktop?!
Click to expand...
Click to collapse
I downloaded from the main Androidfilehost link.
Here's the desktop when I boot:
{
"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"
}

Sorry but you haven't downloaded the latest version.
Tbh the sort order by AFH is really misleading and irritating.. so I have just re-ordered the androidfilehost structure so you may find the latest release better now.
The latest one is v1.3 btw.
Go to: https://www.androidfilehost.com/?w=files&flid=142115
Find the folder LATEST
Download FWUL from there
.

OK tried that version, no luck getting the LG LAF terminal window up for the short time the phone stayed in download mode. Even download mode is not stable any more, and just after that it wasn't switching on at all so kind of lost all hope of recovering anything from it now.
Thanks for the link to FWUL - could prove useful in the future.

Question Bricked phone - Need help ASAP

Hi.
So.... I ****ed up. I have accidently deleted all internal data on my phone, and I can't use MSMDownloadTool for resetting the phone. As I get the "Sahra Communication error".
I can get into fastboot.
Anyone who has some tips?

zXDexusXz said:
Hi.
So.... I ****ed up. I have accidently deleted all internal data on my phone, and I can't use MSMDownloadTool for resetting the phone. As I get the "Sahra Communication error".
I can get into fastboot.
Anyone who has some tips?
Click to expand...
Click to collapse
I did something similar with the non pro and oneplus replaced the phone, didn't even pay for shipping. Tried every msm tool available. My advice is to open a ticket with oneplus and see what they can do. That being said, my situation was different as it happens weeks after the phone was available (I think I broke it was even available in retail)
So that may have played a huge part of their generosity. I am in the US (may be applicable as well)
That being all said, I never lied to them nor was I looking for a replacement, I just wanted it fixed and assumed I was missing a step that the new phone may have added. I went through every trouble shooting suggestion and even scheduled a remote technician spot.
The technician refused to connect, though, because I downloaded the MSMToolkit he linked to me and said to download and install for it to be available when he remotely connected later. I noticed this technician (who was from germany, oddly enough) sent me a cracked MSMtoolkit (no sign in required like the official one I assumed they would use) the only difference being it was. answer variant the one available to us. So seeing I didn't have to wait for him to initiate it, all I did was attempt it, hoping into at least verify my system drivers were working and that I wouldn't be wasting his time. I replied to him his version was also giving me the error, only in hope he would be better prepared, like maybe it would let him know I needed some special driver or opened port on my network (but it was cracked anyhow)
He replied back in anger " who told you to try? I said to just extract and be ready. we will not assist you further and you are on the hook for any cost of repairs" and then closed my ticket.
I reopened the ticket asking why a technician, who from what I could gather, was a 3rd party service, making such statements on behalf of one plus? I also asked why the same technician was telling me to utilize cracked MSMtoolkits. Next thing I knew I had a next day FedEx label in my inbox to print and ship my phone out.
Maybe it was the timing, the the tech and me calling them out or maybe oneplus can easily fix the problem in house and decided to go that route.
Either way, there's no cost to opening a ticket with one plus, beyond language barriers and tedious preliminary troubleshooting. If you bought it at launch, id be concerned about the length of time and their desire to be as helpful. Not suggesting you lie but maybe just dont over share information.

If you searched, you'd see this :
Completely Bricked! Someone help
One plus 9pr complete brick. Cannot access fastboot or recovery. Will not turn on and when I plug in only shows a connect a chargwer screen. It is charged. I cannot get msm tool to connect either.
forum.xda-developers.com
Make sure you connect the USB cable directly to your computer, preferably in a USB 2.0 port, not via a hub.
Check the other stuff I mentioned in that post too. If you see the sahara communication failure, try rebooting the phone into EDL mode again while the software is running, it'll likely see it the next time. Also make sure you've selected your region in the top dropdown menu in MSM tool.
More info on EDL here : https://www.getdroidtips.com/5-methods-to-enter-edl-mode-on-any-xiaomi-smartphones-qualcomm/

djsubterrain said:
If you searched, you'd see this :
Completely Bricked! Someone help
One plus 9pr complete brick. Cannot access fastboot or recovery. Will not turn on and when I plug in only shows a connect a chargwer screen. It is charged. I cannot get msm tool to connect either.
forum.xda-developers.com
Make sure you connect the USB cable directly to your computer, preferably in a USB 2.0 port, not via a hub.
Check the other stuff I mentioned in that post too. If you see the sahara communication failure, try rebooting the phone into EDL mode again while the software is running, it'll likely see it the next time. Also make sure you've selected your region in the top dropdown menu in MSM tool.
More info on EDL here : https://www.getdroidtips.com/5-methods-to-enter-edl-mode-on-any-xiaomi-smartphones-qualcomm/
Click to expand...
Click to collapse
Not OP, and I truely hope this helps him fix the issue but when this happens to me, I know it wasn't in EDL, as did Oneplus. Thankfully they were open to replacing it for me, but that is nothing to assume ever happening again.

Also had this sahara communication error. Turns out it was just the method of connecting it for me.
What I did was put it into EDL mode with vol up and down for 15s and while holding the keys connect the USB with the software already running, and set to start. I don't remember the message but it said "waiting for communication" or similar, and it would immediately start the recovery when connecting the USB
I recommend this page with some more tips too.. https://www.droidwin.com/fix-sahara-communication-failed-error-msm-download-tool/

Hi
Try to use this tool (credit to craznazn, the developer):
lemonadep_22_I.07_210412.zip | by craznazn for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Set the "Target" button to India, connect your dead phone using vol-up + vol-down + plug in USB, click Start...
I did unbricked LE2120, LE2125 well, using this tool you will get 11.2.4.4, then easily you can find the correct OTA firmware on your choice to be updated locally.
Regards,
xe
{
"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"
}