• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [International] Please help! LG G2 bricked. Tried everything!

What do you think about flashing a D802 4.4.2 Stock ROM (if I can find one) with TWRP? Would doing a nand backup and then flashing the D802 followed by a boot restore from the nand backup work? That is what they other link successed and it seems plausible.

Hmm, well if the kernels are indeed compatible between the d800 and d802, then yes I'd think you could flash a stock rom but remember this...when you ran Autorec, it installed a downgraded aboot and patched kernel in order to maintain working Loki. So, you'd need to install the patched kernel for the D800 directly after flashing the rom.

Rather than trying to restore from Nandroid, you might just install the D800 kernel in TWRP directly afterward. Those can be found in this thread (who's OP is also the author of Autorec):

http://forum.xda-developers.com/showthread.php?t=2680948

Specifically by following the download link at Patched Kernels > White Lines > D800 kernel. Those are flashable zips so that's perfect.

However, I would definitely have a nandroid backup made prior to trying any of this. If it fails to boot, you can always nand restore and regroup.
 
help !!

i have lg g2 d802 32 gb .. tried to flash a cutosm ROM made my phone bricked ... after many uunsuccesfull attemts .. my phone is stuck at lg logo with green and blue leds flashing ...
more problems:
1 imei is null
2 previously flashed wrong ROM
3 phone can enter in download mode (not a problem :) )
 
help !!

i have lg g2 d802 32 gb .. tried to flash a cutosm ROM made my phone bricked ... after many uunsuccesfull attemts .. my phone is stuck at lg logo with green and blue leds flashing ...
more problems:
1 imei is null
2 previously flashed wrong ROM
3 phone can enter in download mode (not a problem :) )

Did you back up your efs at some point in the past? IOroot had that feature built into it way back when or you may have ran into a thread on your own regarding that topic. I assume you've already tried flashing a d802 kdz?

Another question for my own curiosity..how long have you owned this phone and did you buy it new from a brick and mortar store? Used on the internet? Reason for asking is there's been a run of fraudulent d802's lately which actually contain d800/d801 internals.
 
bro i bought it as genuine product .. i have imei which shows it as genuine ... also shows that it has d802_20c software support ...
During flashing ROMs i lost it(IMEI) .....
at start I was stuck in fastboot mode .. followed ur steps and able to reach download mode ... flashed needed rom and now stuck in lg logo and green led blinks ...
one thing more ... i have deassembled the phone and on board its written d801 (is it a d801 ? but my imei shows it as d802 with support of d802_20c kdz) ..
do help bro .. m fed up :(
 
Did you back up your efs at some point in the past? IOroot had that feature built into it way back when or you may have ran into a thread on your own regarding that topic. I assume you've already tried flashing a d802 kdz?

Another question for my own curiosity..how long have you owned this phone and did you buy it new from a brick and mortar store? Used on the internet? Reason for asking is there's been a run of fraudulent d802's lately which actually contain d800/d801 internals.
NO, I did not backuped Those files ... :(
I was trying to root the device but failed and fallen in this situation ..
as internals shows it as d801 (on mother board) should i flash the 801 rom ?? if yes which one to flash ??
 
NO, I did not backuped Those files ... :(
I was trying to root the device but failed and fallen in this situation ..
as internals shows it as d801 (on mother board) should i flash the 801 rom ?? if yes which one to flash ??

You took it apart all the way to the motherboard? Meaning you removed the uppermost black plastic dust cover to see that? the G2 is also marked with it's model number in the lower left corner of the phone with the rear cover removed. Some "vendors" place a sticker over top of it to hide the real model number. If that shows D801 and your motherboard shows D801, then you do indeed have a D801. In which case, you can try to flash a D801 tot or kdz but I'm worried about the lost IMEI.

Another thing that would give us a clue...when you were fastboot flashing images to restore download mode...did you use D802 partitions or D801 partitions to do that?
 
You took it apart all the way to the motherboard? Meaning you removed the uppermost black plastic dust cover to see that? the G2 is also marked with it's model number in the lower left corner of the phone with the rear cover removed. Some "vendors" place a sticker over top of it to hide the real model number. If that shows D801 and your motherboard shows D801, then you do indeed have a D801. In which case, you can try to flash a D801 tot or kdz but I'm worried about the lost IMEI.

Another thing that would give us a clue...when you were fastboot flashing images to restore download mode...did you use D802 partitions or D801 partitions to do that?


I did used d802 patition images at that time i followed back cover info .. (used ubuntu)
 
I did used d802 patition images at that time i followed back cover info .. (used ubuntu)
Well that's interesting. Most times the D802 partitions will fail to restore download mode. Instead you have to use the partitions that match the internals of the phone. Guess I'm not real sure what you have going on in there. A pic with the rear cover removed would be a good thing.
 
If flashing the stock kdz/tot doesn't clear up your mess, which I'm afraid it won't entirely, you can check out this thread:

http://forum.xda-developers.com/showthread.php?t=2701861

The OP posted a vid near the end that shows the method he used. I've never attempted that so I'm not much help. Just ran across it when searching.


is it possible that due to imei issue m not able to flash complete ROM ??? as when at 80% on PC (flash tool) phone restarts (showing 100% on firmware update ) and then it shpws android bot image showing installation then it stucks at lg logo with leds flashing, on pc side it shows" fboot check ..." then boot error ...
 
Well that's interesting. Most times the D802 partitions will fail to restore download mode. Instead you have to use the partitions that match the internals of the phone. Guess I'm not real sure what you have going on in there. A pic with the rear cover removed would be a good thing.
inside rear cover its written "D3 DS0826 M2" nothing more ....
 
Here's what a D802 should look like. Note the lower left corner:

i.imgur.com/zjGQxE5.jpg

If there is a sticker covering that area, remove it. All models are stamped in that location whether they be D802, D801, D800 etc.
 
is it possible that due to imei issue m not able to flash complete ROM ??? as when at 80% on PC (flash tool) phone restarts (showing 100% on firmware update )

That is normal behavior. Typically LG Flash Tool will report about 80% when it's done. The phone's screen will read 100% at that time and will reboot itself upon completion of flash.
 
You took it apart all the way to the motherboard? Meaning you removed the uppermost black plastic dust cover to see that? the G2 is also marked with it's model number in the lower left corner of the phone with the rear cover removed. Some "vendors" place a sticker over top of it to hide the real model number. If that shows D801 and your motherboard shows D801, then you do indeed have a D801. In which case, you can try to flash a D801 tot or kdz but I'm worried about the lost IMEI.

Another thing that would give us a clue...when you were fastboot flashing images to restore download mode...did you use D802 partitions or D801 partitions to do that?




at the left(not exact left but near to centre :) ) bottom corner of phone its written d800 and on board its written d801 ...
 
also on touch plate strip its written ... "/d800/d801/d8003/d800t" and on other strip its written "EAX65224801_1.0_1d800_F_TOUCH" but not d802 :(
 
also on touch plate strip its written ... "/d800/d801/d8003/d800t" and on other strip its written "EAX65224801_1.0_1d800_F_TOUCH" but not d802 :(

Yes often times they use a marker to edit those 2 cables going up either side of the phone. They originally come marked with multiple model numbers and during assembly, they mark them according to the model that particular phone is supposed to be. Sounds very much like a D800, which is the most common board being sold as a D802 right now. Seeing it on these forums every single day.
 
The fix I've been applying is to use LG Flash Tools to flash a D800 tot. However, that fails due to a wrong model error. So we hexedit the first instance of LG-D800 to instead read LG-D802. Then, we run into a "cross dll" error most times. To bypass that, you can use the generic device dll instead (LGUP_8974.dll) along with the hexedited tot.

That combination has been restoring the phone although it will be a D800 so you cannot update it further. Would need to root, install D800 TWRP and update via custom rom if you decide to go that route.

Your situation may still vary however since you've lost your IMEI. That combo I have not fully seen yet but I'd be willing to try if you are.
 
The fix I've been applying is to use LG Flash Tools to flash a D800 tot. However, that fails due to a wrong model error. So we hexedit the first instance of LG-D800 to instead read LG-D802. Then, we run into a "cross dll" error most times. To bypass that, you can use the generic device dll instead (LGUP_8974.dll) along with the hexedited tot.

That combination has been restoring the phone although it will be a D800 so you cannot update it further. Would need to root, install D800 TWRP and update via custom rom if you decide to go that route.

Your situation may still vary however since you've lost your IMEI. That combo I have not fully seen yet but I'd be willing to try if you are.



lets try ... tell me what to do .. ??
 
please provide the tot file of d80220c (which my imei shows is the update available for me) (as at first attempt i flashed the wrong ROM named D80220b and also provide tot link of both d801(mother board shows this ) and d800 (rear cover removed shows this).
 
Last edited:
The fix I've been applying is to use LG Flash Tools to flash a D800 tot. However, that fails due to a wrong model error. So we hexedit the first instance of LG-D800 to instead read LG-D802. Then, we run into a "cross dll" error most times. To bypass that, you can use the generic device dll instead (LGUP_8974.dll) along with the hexedited tot.

That combination has been restoring the phone although it will be a D800 so you cannot update it further. Would need to root, install D800 TWRP and update via custom rom if you decide to go that route.

Your situation may still vary however since you've lost your IMEI. That combo I have not fully seen yet but I'd be willing to try if you are.


WIll try myself ... searching for tot file and dll ...
one thing more ... iremember my IMEI(thanks to google play :) ) can this be helpfull ??
 
WIll try myself ... searching for tot file and dll ...
one thing more ... iremember my IMEI(thanks to google play :) ) can this be helpfull ??

Well you'd need to know your IMEI if you try that fix from xda to restore it. I'll PM you a link of an already hexedited d800 tot and the LGUP_8794 dll.
 
Sorry bro , but its giving error ....
1."cross dll" when i use LGup_8974.
2."phone model different" when i use other dlls(800 or 802)

do i need to flash partitions qhusb method in ubuntu ???
 
Sorry bro , but its giving error ....
1."cross dll" when i use LGup_8974.
2."phone model different" when i use other dlls(800 or 802)

do i need to flash partitions qhusb method in ubuntu ???

Lol, these pieced together phones are all different. Just yesterday, we revived a phone that seemed to be in your exact situation with that tot and that LGUP_8974.

Well, you could try this one at your own discretion. Even though it's the same filename, it's from a D802 20c:

https://copy.com/ox6c6Unm8LhOONBL

I have no idea what the consequences of that will be as I haven't tried it yet. And no, you don't need to do the qhusb_bulk thing in Ubuntu. You're not in that situation right now.
 
Back
Top Bottom