So I'm trying to figure out why my phone still ceases to be recognized by LGNPST as the E970 device it is. I'm trying to complete the N4 conversion and it just doesn't recognize the device and only lets you into the Emergency tab of LGNPST. I did flash the Snow JB v1.1 ROM onto it, could that be part of my problem? I don't see why It would matter, but It might. Any help would be wonderful!
Related
Good day fellow XDA users!
I've been playing with my Lg v410 and as you could have guessed - bricked it (while trying to install a rom
The problem: The phone is not booting further the LG logo and the android install
I've tried:
1. Doing a hard-reset, didn't work. After getting to the hard-reset screen - I double-confirm the reset and then nothing happens (waited for about an hour and a half).
2. Entering download-mode, didn't work. It shows the "download mode" logo but nothing happens.
3. Connecting to PC, fast-boot, adb of LG Tool can't "see" the device.
Any suggestions?
Thanks in advance
There is no .kdz released for the V410 (thanks AT&T) so download mode is kind of useless. People have tried the LG mobile support tool with the tablet in download mode, some report it is detected. However, the support tool just says you have the most recent firmware and won't restore the tablet; it is worth a try but unlikely to help.
The only way I've heard of anyone recovering from breaking the V410 to the point where all you have working is download mode is by sending the tablet to LG and having them reflash it.
You can't blame LG for this, they've released firmware for the V400 and by all accounts support it fairly well. It is some kind of AT&T thing; same with some other AT&T branded devices I have. They won't let OEMs release the firmware for devices they peddle.
Your best bet to support this tablet yourself is to nuke the laf partition and enable fastboot (since download mode is useless). At least that way you have a shot at flashing a new recovery or other stuff if something goes wrong.
Good luck. Sorry I don't have any better ideas. At one point I researched a method to create a .kdz from images of a working tablet to deliver with the LG tools, but if it is possible at all, it is beyond my developer skills.
Om it's way to LG for a reflash.
Bricked my LG Gpad 7.0 pretty badly. Here are the steps I did
First I found the KDZ for a test version for the LGV410, worked but when I tried using Cygenmod root and recovery, the boot screen became washed out. Once the tablet booted up, the screen was okay, but the washed out boot screen was bugging me.
Next I went into fastboot mode and erased EVERYTHING.
Now I couldn't get anything to work, every time I tried flashing an .img via ubuntu, it would just reset.
Last, oops, I formatted the EMMC ya ya I know dumb.
Anyways, got my hands on the LG Smart Boot Diagnosis Tool, this appears to work, only if I had the correct rom, which by the way also is the same AP Chip ROM for the LG G Pad 10.1 (MSM8226 Snapdragon Qualcomm 400 Chipset)
So my question is, does anybody know how I can get this or do they have themselves. The directory structure looks like this:
View attachment 3518793
Help?
Like a lot of people I have the eu version of the h815 and managed to bootloop it after following the garbage methods online for rooting .. I came here for help and found all the methods listed... lg up, lg flashtool 2014 etc.. the problem was that my phone just wasn't recognized by the computer, it charged well but that was it, lg bridge, lg up, lg flashtool.. none could find my phone.. I thought I was doomed to a soft bricked paperweight and even began contemplating the hundreds of pounds needed to purchase a new phone.. however after hours and hours of tinkering I cracked it and now have a working lg g4 again.
first off download and install lg up dll file
then install lg up but don't open yet
find and make sure u download the correct kdz firmware file ( I needed the h81520d file which I downloaded from storage cow as devtesters didn't work for me)
now head to your computer control panel and delete(uninstall) any lg mobile drivers that you see.
connect your phone through usb into download mode and leave connected
once that's done download the old drivers (4.0.4 I believe) and not the newest 4.1.1 or whatever it is now.
then open lg up and hopefully like me you see your recognized phone.
click upgrade (not refurbish) and click bin.. right of bin is the ... symbol.
hit that, choose your kdz file and voila.. let it work its magic..
DAMN IM HAPPY. HOPE THIS CAN HELP SOME OF YOU LIKE IT DID ME.
LG G4 H815L running v20d.
Since V20D is crap, I want to move to V20h (its not my first time going back and forth).
The problem is, this time, that for some reason, when i put my lg g4 into download mode and enter LG UP, its detected, but shows instead of READY or something like that "STANDBY".
And there is no functionality from there. I can't really do anything.
Please help!
Good day, all
I need help to hopefully restore any working ROM to my LG G4.
Album of screenshots: https://imgur.com/a/3afkFbl
The short story is, I originally saw a slightly newer firmware on the LG site https://lg-firmwares.com/. But I may have installed the wrong one since I now cannot get 4G LTE and I now have a 'US Cellular' splash screen at bootup (as opposed to the original LG splash screen). So I got a new LG V20 and it is now having issues. So I decided to try to go back to the LG 4G IF I can get the right firmware on the phone.
I attempted to enable USB debugging, install the LG drivers, DLL and boot into download mode and use the LG UP software to install the firmware US99125a_00_0317.kdz (not SURE if this is the correct firmware or not but I’m frustrated and starting to not care). However, the LG UP software won't recognize my phone (please see screenshots at link below). I also tried the LG Flash Tool and Uppercut (with the request LG UP version) and neither worked (also see screenshots). The phone looks to be kind of messed up when looking at the status section of ‘settings’ and the fact that it won’t connect to 4G LTE and has the ‘us celluar’ splash screen.
Can anyone guide me on how to fix this (hopefully)?