I have an LG Stylo V2 plus and I unlocked the bootloader a few years ago to play around with it as it was a spare phone. I pulled it out a few days ago and found a warning about it being corrupt and could not be trusted. I am now stuck in a boot loop where it will load to the Verizon loading but then spin there forever.
I installed all of the necessary software and tried to dl the firmware flash files that are suggested on all guides but LGUP throws an error either that the file is bad or that there was an issue with the update/refurb.
I installed LG Bridge but it was pretty useless without a restore file to restore the phone to (not to mention it could not detect the phone where LGUP did).
Also the only source of the firmware kdz files (the only source I can find lg-firmwares.com) seem to have a limit of like 90 KB/s dl rates so these 1.5 GB files take all day to dl and then don't work.
Every guide I can find here on xda for the boot loop says it can definitely be fixed and that its a soft brick (since I can still boot to the download mode). But then they don't seem to actually guide you in any logical path to fixing it other than doing the same LGUP that seems to not work.
I went to reddit to see if I could talk to anyone about the issue and was sent here by a bot and my post was removed.
I hope someone can help. If you need any more information I am happy to provide. All I am wanting is to just factory reset the phone so it works again.
Related
I can get into download mode, but have a secure boot error and cant use ADB or fastboot. I've been reading every thread I can find.
I tried the LG tool, it never downloads the firmware, just hangs at 12%. Tried different drivers etc. Let it run overnight just in case it was a slow download - nada.
Tried the LG tool by entering the imei number first, but the tool reports a low battery and won't load the firmware. Phone is fully charged, i assume that battery level reporting is not working correctly.
Tried to load the kdz with the R&D tool, it errors out at 49%.
Tried to do the offline process with shttp from the unbrick any phone thread. It uses an older version of the LG tool and won't recognize that the phone is plugged in. If i install the newer tool that sees the phone, the process crashes the tool.
it all started when i tried to flash twrp and used the one for a different model g2. Dumb, I know. this is my first time soft-bricking a device.
Can anyone please point me in another direction?
UPDATE: phone was reporting that it was an 802. Downloaded and flashed an 802 kdz file and the phone booted! First time it was able to get past 49%. Nothing really works on the phone, but now i'm able to use the LG Mobile support tool to flash the correct firmware. The program is downloading the sofware now.
When you say LG tool I'm assuming you're talking about the official program you can download from their site?
I have the Verizon G2 and promptly erased everything on it the first night I got it.. Don't flash / wipe files at 4 AM when you've been up all day and night.
Anyway this thread http://forum.xda-developers.com/showthread.php?t=2432476 really saved my rear. Maybe the T-Mobile version will work to get yours back to stock.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM.
Vepaot said:
When you say LG tool I'm assuming you're talking about the official program you can download from their site?
I have the Verizon G2 and promptly erased everything on it the first night I got it.. Don't flash / wipe files at 4 AM when you've been up all day and night.
Anyway this thread http://forum.xda-developers.com/showthread.php?t=2432476 really saved my rear. Maybe the T-Mobile version will work to get yours back to stock.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM.
Click to expand...
Click to collapse
works at the start and hangs at 49%. There is one bit that needs to be switched and this would work.
okay, looks like the phone is reporting that it is a d802 from my first f'd up flash. I think this may be causing the problems with flashing the 801 kdz.
Can i flash an 802 kdz onto an 801? then possibly later go back to 801?
So I bricked it good.
This isn't working.
https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903
I successfully went from 14b to 12a, started the root and ended up getting stuck at a static screen, after wiping with twrp and rebooting. Followed some steps to hopefully eliminate the static but in doing so I was at 30 mins no boot. (3 times) I decided why not start over and went to flash the 12a kdz again, and now everything I do gets me back into "Firmware Update" I can get to stock recovery, which doesn't make sense as I had TWRP, flashed.
Every option in the stock recovery, sends me back to the "firmware update screen" I've tried countless times to kdz flash with LGUP, everything is detected no issues, just fails usually at 11-13%
Here's a picture of LGUP errors
http://imgur.com/a/p9v5g
I was thinking of trying to use either 13a or 14b kdz but I've hit my download limit for the day from the site (its 2 by the way) the 14b download failed as my internet kicked out.
I have the 12a .kdz, and a 12a.dz and the ability to extra the .dll (that method also didnt work) I've got to missing something here. I've had the phone for 4 days and its a paper weight now. (A free paper weight but that doesn't make it any better)
Please help... thank you
I have used lg up twice months ago. Never had any issues with it. Try running it as admin.
Datblkbro said:
I have used lg up twice months ago. Never had any issues with it. Try running it as admin.
Click to expand...
Click to collapse
I'm running uppercut as admin to no avail. Do you think because its on 12a, and I'm trying to flash 12a?
Edit :
Apparently you cant flash the same kdz, as the version youre on. The14b finally finished downloading anmd it worked first time. This can get closed now. Thanks!
I'm in a bit of a pickle with my stylo 2 plus (tmobile k550)
back in 2016 sometime i rooted my phone and everything was fine and working properly, i was able to do everything i wanted to do. For a while now i've been wanting to restore my my phone back to it's original de-rooted state but the thread i went to for the rom indicated that if i used a tmobile phone it may sim lock it to metro pcs which i didn't mind and i took a gamble on it and followed the instuctions i used LGUP and installed it and everything was going fine even shows me the metropc logo/animation on startup but it gives me an error with the IMS that it was unable to start and i'd close the message and it would just pop back up and i was not able to do anything else. on top of that when i installed the rom i opted to not keep twrp installed . that was a mess that took me a better part of the day to figure how to get back on the phone but i cannot use LGUP with a proper KDZ file as every time i try to run it it tells me that my phone is a MS550 and won't install because the KDZ file is for a K550, i also tried LG Flash Tool 2014 and it analyzes the phone go up to 30% jumps back to 25% then says "Required info cannot be found." and just below that it says "Contact the system administrator.."
I've tried practically every suggestion i could find via google and youtube (man alot of those videos were repetitive broken records to boot)
if someone could please help me with this problem i'd greatly like to restore my phone back to it being seen as a k550. (i really cannot afford to buy a new phone at the moment and really like this one)
thanks for taking the time to read this.
Edit: I went into twrp and did a wipe and the IMS error is now gone and i can access the metropcs version of this phone but i'd still love to get the tmobile rom back on here if possible.
Edit2: After a little more searching I realized i am blinder than i thought and found another non-kdz stock installer for the k550 was able to restore my phone fully. thanks for anyone that stopped by and took time to read this.
I got LS997 that was not completely unlocked (Sprint support confirms unlock status but phone did not receive unlock command, and i got no sim card and no previous owners name to re-initiate ota-unlocking process)
First thing i did - i used pathed LGUP and dirtysanta rooted my phone.
Suggested 995 kdz rom was vibrating like crazy (as described in dirtysanta guide) but i got root and started experimenting further.
Than i flashed rootable 996 kdz, rooted, had no vibration problem but got static boot issue, ok, installed mk2000 kernel, no static - all good but still not enough.
LOS16 = gsm/lte unlocked but battery was drained in 5 hours with screen turned off and no camera, got back to 996, rooted, super rom, all good but LTE not operating for some reason. Really enjoyed stock functionality (camera, seconds screen) and decided to get back to stock system.
HOWTO: Root LS997 up to ZV7, did it all, started flashing available 'stockish' roms one by one [this, and this], so there goes bad stuff.
At this moment i was still being able to boot into twrp, so i didn't really notice that phone was bricked, those stockish systems was just hanging in LG logo for hours without any progress. ok, found another one stock ls997 rom in dirtysanta root post, flashed it - and nothing, phone still stuck at lg logo.
LGUP flashing routine that was always helping me recover, now if fully completes partition_dl process but results are the same - lg logo for hours without anything happening, except vibrator motor starting to work on power up on Verizon firmware version and no vibro on 996 variant (as it sould):
996 kdz - stuck on logo
996 kdz- stuck on logo
flashing everything i got from lg-firmwares.com:
US99610g_00_1216 - stuck on logo
US99610f_00_1205 - stuck on logo
US99620f_00_1120 android 8.0 - stuck on logo
VS99512A_06_1114_ARB00 - stuck on logo
download couple more variants and still nothing, phone stucking in lg logo
so how badly i bricked it? is there any method of recovering that i am not aware of?
There is an older thread on returning the LS997 back to stock that may help.
C D said:
There is an older thread on returning the LS997 back to stock that may help.
Click to expand...
Click to collapse
Yeah, thanks, been there.
Unfortunately i'm not meeting 2 of 3 prerequisites:
- Your device needs to be able to boot into TWRP and fastboot mode
- You need access to a computer to run ADB commands to the phone
There are no more twrp presents on device because of kdz uploads from LGUP, i was thinking that it was recovery and aboot partitions that was messing up my system.
And there is no bootable system on device to turn on usb debbuging to run ADB commands as only thing i get is boot logo, fastboot are also locked to 995 or 996 (whatever version i've uploaded last from LGUP, and they are not unlockable because LG recognizes original LS997 hardware identification and refuses to give me unlock.img.
As i get it - the only thing that can tinker with my device is something that can get same hardware access as LGUP (laf is still operational or idk, maybe not, but it should be getting everything up and running but that is not the case anymore for some reason)
So you are saying that LGUP can still see the phone but ADB can't. Did you by any chance do a full system dump of the phone on LGUP before the whole DirtySanta procedure in the beginning? I wonder if those files can help getting things back on track. Not sure if they are device-specific, but I did make a dump of my own LS997, so if you think there's something useful there, let me know, and I can upload the files somewhere.
C D said:
So you are saying that LGUP can still see the phone but ADB can't. Did you by any chance do a full system dump of the phone on LGUP before the whole DirtySanta procedure in the beginning? I wonder if those files can help getting things back on track. Not sure if they are device-specific, but I did make a dump of my own LS997, so if you think there's something useful there, let me know, and I can upload the files somewhere.
Click to expand...
Click to collapse
Yes i did full LGUP backup at first system state, but nature of this backups makes them pretty useless in this system state - because they are just images of partitions.
Only software that can write directly to those partition may be able to utilize those backups, there are a lot of post on this forum describing TWRP routine for making update packages based on LGUP backups.
So unfortunately there is only LGUP, but it only can make backups but can not restore them as it uses some special file format (KDZ) that containing some dll's and data files (like glued partition images with special info of where to put what) and i didn't find a way to make my own KDZ files from backup images.
I'm now getting another idea - that this can be a blowed fuse in CPU ARB protection mechanism, if anyone has experienced ARB 1 please confirm that system should be in this state in case of ARB error
Hello XDA. I recently revived my G6 after it sat in my drawer for years and was delighted to see HavocOS on Oreo still running on it. I popped in my T-Mobile SIM and voila, service. My only issue was horrible data speeds. I tried every network settings and apn fix that is relevant to my device but I was still stuck with virtually no 4G data. So, my last resort was to flash back to stock. Now, I dont know if there is a specific method for this device as I forgot how complicated the root exploit was. But I went ahead and downloaded the latest stock .kdz (20g), LGUP and the drivers and proceeded as normal to flash the kdz over. I had SEVERAL issues getting my device model to be recognized and finally grabbed the right LGUP version that worked. I proceeded to flash the kdz when it gave me an error round 31%. I did much troubleshooting research and came up empty, finally decided to try flashing the stock version it was on (20a) to just restore it.
This worked. I thought I was saved until the phone froze on the T-Mobile logo while booting and didnt budge for an hour. Much more googling and I found a thread that looked promising and seemed to help. At first. It flashed the kdz, gave me the error, and when I tried to flash the dz, nothing. I retried LGUP with 20a stock, unknown model. I tried to go back through the whole rooting process again and stick it out with minimal service. The FWUL/lglaf portion of the guide is where I got stuck. My device would not be recognized in FWUL, I couldnt get wifi so plugged in my ethernet. And then I kept getting "USB configuration not set" and "input/output" errors, and I noticed that while booting FWUL, the step "Loading Kernel Modules" fails. So I assumed that FWUL was not loading any modules, including USB's (which explained the errors), so I booted up my own Manjaro install and cloned the same project there. Knowing all my modules work now, I still get the "Input/Output" error.
So now I'm led to believe this phone is hard-bricked. It registers as a port in Window's Device Manager, "LG AndroidUSB SerialNet" or something like that. I tried following the unknown model guide again to no avail. I'm at a loss. Whatever info is needed for debugging I'll provide. I'm dualbooting Win10 and Manjaro so any methods are viable.
Which specific stock KDZ(s) did you try to flash on your phone (full kdz name)? You need to seperate flashing and rooting as two separate tasks because from your post I can't tell if you are able to boot after flashing stock kdz or not. First, if your phone is not booting, you gotta recover from that and flash a stock kdz.
Also, try using the Dev patched LG UP from this post (thank the dev while you are there): https://forum.xda-developers.com/lg...ssflashing-t3780969/post76510671#post76510671
Try the 'Partition DL' option when you flash and select all partitions in the next window.
Once you are able to boot a stock rom, you can try using a VMWare such as virtual box, install/mount FWUL in a virtual environment and use that to root the phone. I think the process is somewhere here on the runningnak3d's guide or on another post, I will try find a link later.