Okay here goes....
I have a LG G2 VS980 which I was attempting to downgrade to Kitkat. I used a VS98024a_11.kdz (not exact name, but similar) to downgrade and the LG Flash tool, with the 3 blocks as logo. Now this is on a Windows XP laptop. The flash all went well, but now the phone does not start. When I boot it up, it goes to an erasing screen and stays there. Any help? I can't reflash it, because LG Flash Tool says the phone disconnected. Please help, ASAP, I hope to have it working by Monday, as I greatly need it.
Were you ever able to find out how to downgrade to Kitkat? I have a replacement device running LP 5.0.2 and I am trying to downgrade as well and cannot find any information on how to do so, or if it is even possible. I hope you were able to get your phone straight!
Related
So here's my problem. I think I've bricked my device. Don't know if it's softbrick or hardbrick, but either way my phone just does not boot up. The only instance it works is when I remove the battery and try to charge the phone, it shows a picture that it didn't find a battery. All of this occurred while trying to unlock the bootloader. Something similar already happened to me like a month or two ago, but I was able to flash stock KDZ using the online LG Support Tool. Anyway, the part where it all messed up is probably the aboot.bin file, although I'm quite certain I flashed the right file for my device. Also, installed CWM recovery, and after restarting the device it just won't boot at all, not even the software upgrade mode or anything. So my guess is that something is wrong because of either a wrong aboot.bin file for my D405N or the custom recovery. I tried flashing stock KDZ, but I couldn't get my phone into software upgrade mode. Also, tried doing a hard reset, but an LG logo didn't even come up. The battery is at least half full. So is there anything I can actually do in this case? Any help is appreciated.
P.S. Yeah, I did post in another thread (though I didn't create it), but I'm quite desperate with this. Either I fix it myself somehow, or I'll have to take it to the warranty.
EDIT: Took it to a repair. Should be done in around a week. Got an old Samsung Galaxy Mini as a replacement.
linasj said:
So here's my problem. I think I've bricked my device. Don't know if it's softbrick or hardbrick, but either way my phone just does not boot up. The only instance it works is when I remove the battery and try to charge the phone, it shows a picture that it didn't find a battery. All of this occurred while trying to unlock the bootloader. Something similar already happened to me like a month or two ago, but I was able to flash stock KDZ using the online LG Support Tool. Anyway, the part where it all messed up is probably the aboot.bin file, although I'm quite certain I flashed the right file for my device. Also, installed CWM recovery, and after restarting the device it just won't boot at all, not even the software upgrade mode or anything. So my guess is that something is wrong because of either a wrong aboot.bin file for my D405N or the custom recovery. I tried flashing stock KDZ, but I couldn't get my phone into software upgrade mode. Also, tried doing a hard reset, but an LG logo didn't even come up. The battery is at least half full. So is there anything I can actually do in this case? Any help is appreciated.
P.S. Yeah, I did post in another thread (though I didn't create it), but I'm quite desperate with this. Either I fix it myself somehow, or I'll have to take it to the warranty.
EDIT: Took it to a repair. Should be done in around a week. Got an old Samsung Galaxy Mini as a replacement.
Click to expand...
Click to collapse
Remember Next time Unlock Bootloader before Installing CWM.
OK, this post might be long. Feel free to skim. I just want to let people know everything that I've done.
So, my VS980 was rooted and I was trying to install a new ROM. I was going to try out Cloudy G2, but the installation routine only gave me international variants to choose from. I picked one anyway and my phone has been hosed since. I didn't have any download mode or recovery or anything.
I was able to get download mode back by extracting part of the firmware out with the LG Firmware Extractor and flashing that through fastboot. So, that part worked. I have download mode. I was going to try to restore my 24A firmware with a KDZ file and the old LG flash tool v 1.8.1 (the one where you put the ADB interface on COM41, and you use the updated megaunlock.dll, etc), but that no longer works for me. It keeps giving me the "failed previous load" error. I can't find a fix for that.
So, I've been trying to flash it (or firmware 26) with the LG Flash Tool 2014 (the one where you pick "Republic of Korea"). That will only get to between 25 and 49%, and then crash with an unknown error.
In between trying that option, I found instructions for extracting all of the bits out of the firmware and then flashing them to the phone partitions one by one. That seemed to work except I kept getting a security error on bootup. The only fix I found for that was to flash with the first flash tool I mentioned. Ugh.
The last time I rooted my phone and ran a custom ROM, my desktop USBs couldn't communicate with my phone very well, but my laptop could. This time not even the laptop's working. I even bought a new USB addon card (I needed it anyway, the USB3 ports on this suck). That seemed to get the computer to see the phone better, but it didn't solve my problems.
Can anyone help with this? I've scoured tons of directions already.
Thank you for any help
Wackman
A little bit of progress
So, I finally got the older flash tool v 1.8.1 to start working. I've almost got it to flash the stock .TOT file (the KDZ file keeps giving me the "failed previous load" error). Now, I've kinda hit a new roadblock.
I think I mentioned that I got into this mess by trying to flash the CloudyG2 ROM, but that it's for international variants. When the flash tool tries to flash the firmware for the VS980, it thinks I have an F320S, and says wrong phone. Anyone know a way around this? I still only have access to download mode. No fastboot, no recovery, no ADB.
any luck? I bricked my G2 last night and I'm trying the flashtool to get back to stock 27A right now. Did you update your C++ library? I read somewhere that that can cause issues with flashtool..
Is there anyone out there that could help me fix my issue? While attempting to flash a new boot logo on my Verizon Droid Turbo I ran into some issues... I was running a program for replacing the bootloader unlocked message on a previous Motorola thinking oh hey this thing has got to have a very similar setup... I later realized it is different, very different. The difference is the bootloader, recovery mode, and the logo which shows for the drained battery are all intertwined together. So basically I could take the system dump logo.bin and flash it over the current logo, but the trouble is I have completely lost access to my bootloader menu, absolutely nothing is available, and I cannot use adb commands to access it either. I am totally stumped and with root access now available I am very bummed. Might just have to bring my phone in and tell them, in the famous words of Towley. "I have no idea what's going on..." Any help would be greatly appreciated! My only other option at this point I suspect is to wait until OTA lollipop and hope that the update re-installs my logo.bin file as well.
I have the LG L90 and recently the phone just wont boot past the bootloader. It kept stopping at the T-Mobile boot image. I look up how to reset the phone and that's what i did. Now the phone is stuck at the LG boot logo and wont turn on. Either way the phone was still stuck in a bootloop.
Now I've ever done anything to the phone, no USB Debugging, No rooting, No bootloader unlocking. So could someone please help me to figure this out. I'm trying to figure out how to make this thing work again, whether by flashing or what but the problem is the phone has never been rooted or tampered with.
What did you do? Are you rooted? Talk to Tmobile. They will gladly take it back and give you a new one because it sounds like a defect. They took back mine even when I was rooted
I purchased the H811 off ebay last week because I am finally sick of my old Note 5 with no service at home. The G4 did great until I decided to flash it. The phone was on H81120i.
No big deal unlocking bootloader or installing TWRP. I flashed Lineage OS 14.1. About a minute after booting up, the phone got the error Camera stopped working. After checking more stuff on the device, nothing seems to work - i.e. - The accelerometer, speakers, microphone, flashlight, etc are dead. I installed a sensor test app and it doesn't detect any of the sensors.
After that, I downloaded LGUP and the stock KDZ file to flash back to phone hoping to fix it. Unfortunately, LGUP doesn't recognize the phone. It says unknown model but shows the com port, h81120i on the right hand side. I also tried LG FlashTool to see if that would work but it crashes about 26% into the it.
I have searched the forums up and down and have googled the crap out of this. I did find a thread from last month with a very similar issue a moment ago, https://forum.xda-developers.com/tmobile-g4/help/camera-stopped-audio-flashing-lg-g4-t3620516, and perhaps I should post in that thread, but my issue is that LG Bridge gives me an error stating it can't detect the software version.
If I were using Samsung, I don't think I would have this problem because I have unbricked several Samsung devices. The issue here is I am new to LG and have no idea if files are corrupt, if hardware was screwed, or what the situation is. I would hate to think that it was a $100 wasted.
Any help would be greatly appreciated.
x3n0n907 said:
I purchased the H811 off ebay last week because I am finally sick of my old Note 5 with no service at home. The G4 did great until I decided to flash it. The phone was on H81120i.
No big deal unlocking bootloader or installing TWRP. I flashed Lineage OS 14.1. About a minute after booting up, the phone got the error Camera stopped working. After checking more stuff on the device, nothing seems to work - i.e. - The accelerometer, speakers, microphone, flashlight, etc are dead. I installed a sensor test app and it doesn't detect any of the sensors.
After that, I downloaded LGUP and the stock KDZ file to flash back to phone hoping to fix it. Unfortunately, LGUP doesn't recognize the phone. It says unknown model but shows the com port, h81120i on the right hand side. I also tried LG FlashTool to see if that would work but it crashes about 26% into the it.
I have searched the forums up and down and have googled the crap out of this. I did find a thread from last month with a very similar issue a moment ago, https://forum.xda-developers.com/tmobile-g4/help/camera-stopped-audio-flashing-lg-g4-t3620516, and perhaps I should post in that thread, but my issue is that LG Bridge gives me an error stating it can't detect the software version.
If I were using Samsung, I don't think I would have this problem because I have unbricked several Samsung devices. The issue here is I am new to LG and have no idea if files are corrupt, if hardware was screwed, or what the situation is. I would hate to think that it was a $100 wasted.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
maybe you got a frankenphone .. a supposely H811 and its not .. why not open it and see the actual motherboard and see wich variant you really have .seems like its not a h811 or try uppercut LGUP. see what it finds and downloads.
raptorddd said:
maybe you got a frankenphone .. a supposely H811 and its not .. why not open it and see the actual motherboard and see wich variant you really have .seems like its not a h811 or try uppercut LGUP. see what it finds and downloads.
Click to expand...
Click to collapse
Uppercut found nothing... I opened the phone and found this though... EAX6658501_H810_MAIN_1.0
Of course, the tag on the inside of battery compartment says H811 with a date of 02/2016. Would it be a refurb or what? Anyway, I may be on the right track now.
x3n0n907 said:
Uppercut found nothing... I opened the phone and found this though... EAX6658501_H810_MAIN_1.0
Of course, the tag on the inside of battery compartment says H811 with a date of 02/2016. Would it be a refurb or what? Anyway, I may be on the right track now.
Click to expand...
Click to collapse
maybe yes .. cover h811 and so software easy to edit.. but the only way is that take the motherboard and read the variant.
h810 is att?
I checked out the AT&T forum and found nothing other than stock that, obvious under my current situation, I can't flash because lgup with uppercut nor lg flash tools can flash.
LGUP gives an error code in the log file. PACKET_ERROR code = 1460
The phone internet still works. It has downloaded an update from t-mobile that's 460+MB that I can't install because I'm rooted with TWRP. Is it possible to update the phone with adb and TWRP? If I could find stock recovery, I would flash that and using autoprime's bootloader flash it back, even remove root if the update may revive the device.
After a week, a thought occurred to me and i tried it. I backed up a working h811 ( minus efs partition) with twrp with 20o firmware to an sd card then restored that version to this phone. I immediately wiped and flashed G4 20o with root zip file. It unbricked the phone and I'm currently using it.
Thanks raptorddd for replying and helping me. It seems that somewhere in the flash process something was corrupted and this fixed it.
x3n0n907 said:
After a week, a thought occurred to me and i tried it. I backed up a working h811 ( minus efs partition) with twrp with 20o firmware to an sd card then restored that version to this phone. I immediately wiped and flashed G4 20o with root zip file. It unbricked the phone and I'm currently using it.
Thanks raptorddd for replying and helping me. It seems that somewhere in the flash process something was corrupted and this fixed it.
Click to expand...
Click to collapse
youre welcomed but then phone is H811? or H810 i know that what ever the motherboard says thats your variant. am glad you have back up and running. :good:
It is crazy because the board said 810 but it had h81120i official when i got it. It worked but i have always used custom roms. Oh well, I'm going to stay stock with root. Just need to debloat now.