-
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!
iowabowtech
root@android:/ #
By using flash tool 2014 I somehow able to communicate with the cellphone but when I want to push a .TOT file it give me an error message like:
Error: fota partition was changed
LAF retrieve GTP failed
Partition Change fota
Any idea?
Flash tool 2014 is only compatible with kdz's correct? You would need to use LG Flash Tools to flash a tot. However, if the device is not recognized in download mode, then you wouldn't be able to use that tool as it needs to verify model ID and have an active connection.
OTA's are stored in /cache/fota so if you had a failed OTA flash due to being rooted/custom recovery, the above fail messages aren't particularly surprising though I have not seen that error before.
I just don't know how you can interface the phone in it's current state in such a way that you can repair it.
iowabowtech
root@android:/ #
this is like Lg FlashTool looks like once I flash the .TOT file (it only accept the TOT file not the KDZ)
To me it seems it can recognyze my phone (IMEI it s correct) ...
Could you perhaps post a screenshot of the tool and error message?
iowabowtech
root@android:/ #
I edited your post to remove the IMEI so it's not visible to others. I believe your phone actually originates from Singapore. For that reason, my best guess is that you will need a southeast Asia (SEA) kdz or tot to repair. Also, if you're using the 2014 kdz tool, you'll want to use the "CSE Flash" option to get a clean install.
It may be more ideal to try a tot file if all kdz's are failing, including one for SEA. We have an old tot HERE. It is the 10b_SEA tot. It is also for a phone with 32 GB storage size so if yours is not 32 GB, do not use it. If that works for you and you get OTA's, you should be able to update your way forward.
The D802's are tricky because there are many regions and countries involved and at least in some cases it DOES seem to matter which firmware you are applying to the phone even though some people say it doesn't matter...I do not believe that to be the case. So I've offered my best guess as to which firmware you need.
For the tot method, you would use LG Flash Tools instead of the KDZ tool. Instructs for that can be found here:
LG G2 Stock Firmware (Go Back to Stock) | LG G2 | XDA Forums
(the 2nd method for tot files)
iowabowtech
root@android:/ #
I have to say, I've never seen that error before. And I still can't figure out how you could fix it. If only you could get fastboot mode back. Or even adb shell to zero the laf partition. But with neither of those options...
iowabowtech
root@android:/ #
They probably would. I have no idea what they would charge for it and it may depend on how they diagnose it. If they don't have tools (better than our tool options) to access the nand, they might opt to replace the motherboard. I'm not at all sure what something like that would cost to be honest.
Yeah I figured Linux wouldn't work in this case. That only works in bulk mode and it's clear you don't have that.
I brought it into a shop .. let s see what they says.
Meantime, if they demand lots of money I have found this guide (sharing for others) LG G2 is UNBRICKABLE NOW! [FIX REAL HARD BRI
Meantime, if they demand lots of money I have found this guide (sharing for others) LG G2 is UNBRICKABLE NOW! [FIX REAL HARD BRI
amanvarma1203
Lurker
iowabowtech
root@android:/ #
Wish I had some advice for you guys but I haven't seen that failure and it seems there's not much info out there in regard to that.
My only idea would be to try a newer tot if you can locate one. It's tricky to know which one to get though. SEA (southeast asia) or HKG (Hong Kong)? The D802's certainly make it difficult. Some say any D802 firmware should work but that doesn't seem to be the case in my experience.
amanvarma1203
Lurker
I'm so screwed man. Is it possible to get fastboot back so I can flash the laf file again? Also, is there any any any other possible way? The link that mata posted with the hardware repair, does that work?
iowabowtech
root@android:/ #
Have you lost download mode?
amanvarma1203
Lurker
Yes I have download mode.
did I install the android missed in my lg g2 d802t, then, I entered in abd mode, and let erase in boot, aboot, laf, in everything, and when I was going flash the android extracted of the kdz, for kz, for.img, one to one, to restore way of download, the cellphone turn off, now I have not any type of communication with the cellphone, you punish as if he was one pen drive of reading, blockaded for carving, will be that with himself swindling this blockade in a linux, you see some form of helping me?
RAVI RAMCHANDANI
Lurker
I HAVE ONE BIG PROBLEM PLZ FRIENNDS HELP ME..MY NEW BRAND LGG2 IS HANG AT FAST BOOT MODE NO DOWNLOAD MODE,NO RECOVERY MODE..I WANT SOME PARTATION FILE FOR LG G2 D802 32GB PLZ HELP ME..
iowabowtech
root@android:/ #
I'm assuming you already have the Android sdk installed and know how to issue fastboot commands. If you need help with that, let us know.
Theoretically, you should only need to flash aboot, boot and laf. However, that doesn't seem to be working for most D802's anymore so if it were me, I'd use fastboot to flash the entire bootstack. Here's my own link for the D802 20B partitions:
https://dl.dropboxusercontent.com/u/7460142/D802_20B.zip
fastboot flash aboot aboot.img
fastboot flash boot boot.img
fastboot flash dbi dbi.img
fastboot flash laf laf.img
fastboot flash rpm rpm.img
fastboot flash sbl1 sbl1.img (that's S-B-L-the number one)
fastboot flash tz tz.img
Get rid of any other img files you have (if any) or move them to a different spot so you don't get them confused with the files I provided. You do not want to mix and match these files when flashing. They all need to be from the same firmware version.
At that point you should have download mode. If you just so happen to own a Southeast Asia (SEA) variant, you can get the 32 GB tot file here:
Otherwise, locate your region's KDZ and use that by following the instructs HERE. Good luck.
Sammy13579
Lurker
I've been following this closely because my phone was in the same exact state as matata85
Tonight I've tried all sorts of crazy things - most of which resulted in no change. However, I just found that performing the following got the phone back up and running with an AT&T ROM (and the phone now thinks it is a D800 when previously it knew it was a D802).
1. Download the KitKat file from this forum post (first big link). http://forum.xda-developers.com/showthread.php?t=2663369 Note: After the initial 'set up' which extracts some files, you can cancel the others if you already have the LG Flash Tool set up with MegaLock.dll, etc. You won't need the patch either - because all it does if put in MegaLock.dll for you.
2. Download the Generalized model dll from http://forum.xda-developers.com/attachment.php?attachmentid=2611295&stc=1&d=1393872094
3. When usng the LG Flash Tool (I'm aware that you've used this a lot already so I won't elaberate unless you request me to)...ensure you select the generalized dll instead of the one in the exe package file. Then select the rom that the exe extracted.
4. Leave all other settings, press ok and then press the yellow arrow. Boot phone into download mode and leave it to flash.
5. Once the computer reaches 80% it will reboot and then the phone after some time will come up with the AT&T logo. It should after about another minute go to the new phone set up wizard screen.
Anyway - it's not exactly what I want but...I'm thrilled to have a way to get the phone to do something again. I'm hoping iowabowtech might be able to offer insight into how to move from here to a rooted D802 ROM (preferably with TWRP as well). I just tried to re-flash a D802 ROM using a similar method as what I did for the D800 and it won't flash because it says it is a cross version from D800 -> D802...but technically the generalized DLL is supposed to prevent this error - but not in this case for some reason. I might try upgrading with the LG Flash Tool 2014 next and see if it will let it go through.
Oh - and when in download mode, it now says the phone is 'unrooted' - previously it always said 'rooted'. Just a random note - wanting to place everything I've noticed here.
Tonight I've tried all sorts of crazy things - most of which resulted in no change. However, I just found that performing the following got the phone back up and running with an AT&T ROM (and the phone now thinks it is a D800 when previously it knew it was a D802).
1. Download the KitKat file from this forum post (first big link). http://forum.xda-developers.com/showthread.php?t=2663369 Note: After the initial 'set up' which extracts some files, you can cancel the others if you already have the LG Flash Tool set up with MegaLock.dll, etc. You won't need the patch either - because all it does if put in MegaLock.dll for you.
2. Download the Generalized model dll from http://forum.xda-developers.com/attachment.php?attachmentid=2611295&stc=1&d=1393872094
3. When usng the LG Flash Tool (I'm aware that you've used this a lot already so I won't elaberate unless you request me to)...ensure you select the generalized dll instead of the one in the exe package file. Then select the rom that the exe extracted.
4. Leave all other settings, press ok and then press the yellow arrow. Boot phone into download mode and leave it to flash.
5. Once the computer reaches 80% it will reboot and then the phone after some time will come up with the AT&T logo. It should after about another minute go to the new phone set up wizard screen.
Anyway - it's not exactly what I want but...I'm thrilled to have a way to get the phone to do something again. I'm hoping iowabowtech might be able to offer insight into how to move from here to a rooted D802 ROM (preferably with TWRP as well). I just tried to re-flash a D802 ROM using a similar method as what I did for the D800 and it won't flash because it says it is a cross version from D800 -> D802...but technically the generalized DLL is supposed to prevent this error - but not in this case for some reason. I might try upgrading with the LG Flash Tool 2014 next and see if it will let it go through.
Oh - and when in download mode, it now says the phone is 'unrooted' - previously it always said 'rooted'. Just a random note - wanting to place everything I've noticed here.
iowabowtech
root@android:/ #
My findings have been similar to your own. Unfortunately in at least one case though, using the generic DLL resulted in a non booting phone and the loss of both download mode and fastboot...which is really bad. So currently, I'm only recommending this as a last ditch effort. However, I'm happy to hear it worked for you.
Technically, you should still be able to root, install TWRP, and then flash a custom rom in order to update. You'd just want to use the TWRP which matches your phone's internals.
iowabowtech
root@android:/ #
@Sammy13579: I didn't realize this thread lacked some of the realizations I've mentioned in other threads so here's what's been going on with the D802's...
Many of the D802's being sold via the web today are not D802's at all. The are in fact D800's and D801's (internal hardware). When people remove the rear covers from their phones, they are seeing the alternate model numbers stamped on the phone and on hardware within. So what we've found is that flashing the D800 aboot, boot and laf img's has worked to restore download mode if the D802 files fail. Then, it's been tricky to restore the firmware. In most cases, D802 firmware is not working. In some cases the D800 firmware does work but as you found, there is sometimes a need to flash the generic DLL when using LG Flash Tools. Again though, that doesn't work in all cases and may result in a non booting phone with no recourse.
My theory as to how the sellers are doing this (not yet verified):
I think they are flashing D800 firmware EXCEPT the system.img which is being swapped with a D802 system.img from a matching OS version (JB for JB or KK for KK, etc). That would explain why everything else would be compatible with the D800 internals while still running a D802 "rom" if you will.
Many of the D802's being sold via the web today are not D802's at all. The are in fact D800's and D801's (internal hardware). When people remove the rear covers from their phones, they are seeing the alternate model numbers stamped on the phone and on hardware within. So what we've found is that flashing the D800 aboot, boot and laf img's has worked to restore download mode if the D802 files fail. Then, it's been tricky to restore the firmware. In most cases, D802 firmware is not working. In some cases the D800 firmware does work but as you found, there is sometimes a need to flash the generic DLL when using LG Flash Tools. Again though, that doesn't work in all cases and may result in a non booting phone with no recourse.
My theory as to how the sellers are doing this (not yet verified):
I think they are flashing D800 firmware EXCEPT the system.img which is being swapped with a D802 system.img from a matching OS version (JB for JB or KK for KK, etc). That would explain why everything else would be compatible with the D800 internals while still running a D802 "rom" if you will.
Sammy13579
Lurker
@iowabowtech: Thanks - that was a very informative post. If I pop the cover off mine, here is what I can see:
As for the system.img swapping - that is very interesting. In theory it would be pretty safe to test this theory wouldn't it? I mean if I'm running all D800 right now and I add a system.img that is D802 wouldn't I in theory have download mode regardless? Maybe I'm missing something. Of course I don't know how I'd re-package a .tot anyway. Interesting idea and sounds quite right actually.
So tonight I might try to root and flash the D800 TWRP because it sounds like I have a D800. I'll keep you posted. If that works, could I flash a D802 modified stock ROM using TWRP? Could anything not work out in doing this? I actually really liked the stock D802 ROM that was on the phone (it was pre-rooted). The reason I tried to use AutoRec was just so I could back up the stock as it was in case some of the apps I was looing at (Xposed being one of them) messed up the ROM. Ironically the phone never booted the ROM again and I now don't have it lol!
Interesting link I just found taking your post into consideration: http://forum.xda-developers.com/showthread.php?t=2522808
- On the plastic at the bottom (ironically under a sticker that says XD), the phone reads D801/803 (my wife's says D800 - same supplier, purchased 2 months apart)
- The gold strips either side of the battery reads D800
- The connector for the Digitizer matches the D800 (I know this because my wife has one of these too and the screen cracked so I replaced it and discovered it wasn't a D802 digitizer but a D800. I just checked my phone for the same thing and sure enough, it is a D800 connector). If anyone is curious - D802 has a connector twice as long at one side as the other side. The D800 has a connector of equal size at each side.
- Back cover reads D802
As for the system.img swapping - that is very interesting. In theory it would be pretty safe to test this theory wouldn't it? I mean if I'm running all D800 right now and I add a system.img that is D802 wouldn't I in theory have download mode regardless? Maybe I'm missing something. Of course I don't know how I'd re-package a .tot anyway. Interesting idea and sounds quite right actually.
So tonight I might try to root and flash the D800 TWRP because it sounds like I have a D800. I'll keep you posted. If that works, could I flash a D802 modified stock ROM using TWRP? Could anything not work out in doing this? I actually really liked the stock D802 ROM that was on the phone (it was pre-rooted). The reason I tried to use AutoRec was just so I could back up the stock as it was in case some of the apps I was looing at (Xposed being one of them) messed up the ROM. Ironically the phone never booted the ROM again and I now don't have it lol!
Interesting link I just found taking your post into consideration: http://forum.xda-developers.com/showthread.php?t=2522808
Sammy13579
Lurker
Oh, another note, I'm pretty sure (it was a few days ago now), I tried the D800, D801, D802 and D803 recovery and download mode img files from fastboot (back when I could get to it) and only the D800 worked.
Sammy13579
Lurker
Rooted successfully (actually ended up doing TowelRoot and ioroot - not that I probably needed both but I did TowelRoot and then realised ioroot had busybox which I'd prefer on there). AutoRec D800 then successfully installed TWRP as well.
Guess I have a D800! If you can let me know any physical signs still, that would be great as I have a friend with one and he was wondering how to know as well.
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.
Anyway - I'm leaving it there for tonight. Midnight here now. Thanks for all your help. Hope some of this will help others too!
Guess I have a D800! If you can let me know any physical signs still, that would be great as I have a friend with one and he was wondering how to know as well.
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.
Anyway - I'm leaving it there for tonight. Midnight here now. Thanks for all your help. Hope some of this will help others too!