The franken-phone thing is not mine. Must have seen it somewhere too, I think.
It's taken me a week of solid work to piece things together. I'm a trouble-shooter, not a dev. Yours and sammi's overviews and links made me see I was possibly on the right path. Editing the TOT was critical to get the first D800 on. I'm about to go back to the D80020c TOT again, so be interesting to see if it now requires ID as 802 or 800 for success. I suspect it's anow n 802 again, and will need the edited TOT. Must be checking something in the system partition.
(So much information available, but often unclear if it's restricted to JB or KK or certain versions or there are other constraints around the different countries that have D802s. I really wonder if there are differences beyond the system.img for the different countries. Might unpack and diff a couple of different D802 kdz at same version.
Was surprised that all the boot animation for ATT even is in the system, and not in boot somewhere.
I also don't think the guys 'making these' are putting in a lot of effort. If you can identify the basic hardware - via the recovery? - then more than likely that's the base system that will define the radio and the digitizer.)
Most of the time I've had download mode, but I did get to just flashboot at one stage. There's a good thread on xda about just putting back a relevant LAF to get back to download. Less work than restoring multiple partitions, and from there anything is possible using LG tools - assuming the base files are available.
I had a 'fully working'
D80220c (no touch, no Service, blank baseband and IMEI in About screen) when I tried the D800 baseband. Kind of proved for me that D800 was the hardware. To get the SIM back, and see IMEI re-appear was a bonus! (I did try putting on a D800 kernel at that point, but that killed the whole thing. BUMP/Loci issues amongst others I'm sure)
Flashing the 802 kdz or TOT means you have to use an OTG mouse. Very hard to agree to the ADB prompts though - since I couldn't figure out how to have both mouse and a computer connection at the same time. Patience
I used the generic LGPUP8974.dll that LG 'sent' me with the 80220c update (IIRC). Grabbed it from a tmp file created during the process I think. Had assumed they were all the same. Haven't hexed any to compare. Will check details and can certainly share.
I wanted to regenerate the state mine was supplied in as a starting point- hence D80020k and D80220c combination. D80220c is the latest, and I'm about to try going to D80020y/D80220c.
My D80220c system.img came from a TWRP backup I made after one of the kdz attempts. Also tried my original D80220b system.img and it too worked fine.
I may have been lucky, (no end of problems with drivers on Win7, as you'd know), but the logic is pretty strong.
Keep up the great work.
It's taken me a week of solid work to piece things together. I'm a trouble-shooter, not a dev. Yours and sammi's overviews and links made me see I was possibly on the right path. Editing the TOT was critical to get the first D800 on. I'm about to go back to the D80020c TOT again, so be interesting to see if it now requires ID as 802 or 800 for success. I suspect it's anow n 802 again, and will need the edited TOT. Must be checking something in the system partition.
(So much information available, but often unclear if it's restricted to JB or KK or certain versions or there are other constraints around the different countries that have D802s. I really wonder if there are differences beyond the system.img for the different countries. Might unpack and diff a couple of different D802 kdz at same version.
Was surprised that all the boot animation for ATT even is in the system, and not in boot somewhere.
I also don't think the guys 'making these' are putting in a lot of effort. If you can identify the basic hardware - via the recovery? - then more than likely that's the base system that will define the radio and the digitizer.)
Most of the time I've had download mode, but I did get to just flashboot at one stage. There's a good thread on xda about just putting back a relevant LAF to get back to download. Less work than restoring multiple partitions, and from there anything is possible using LG tools - assuming the base files are available.
I had a 'fully working'
D80220c (no touch, no Service, blank baseband and IMEI in About screen) when I tried the D800 baseband. Kind of proved for me that D800 was the hardware. To get the SIM back, and see IMEI re-appear was a bonus! (I did try putting on a D800 kernel at that point, but that killed the whole thing. BUMP/Loci issues amongst others I'm sure)Flashing the 802 kdz or TOT means you have to use an OTG mouse. Very hard to agree to the ADB prompts though - since I couldn't figure out how to have both mouse and a computer connection at the same time. Patience
I used the generic LGPUP8974.dll that LG 'sent' me with the 80220c update (IIRC). Grabbed it from a tmp file created during the process I think. Had assumed they were all the same. Haven't hexed any to compare. Will check details and can certainly share.
I wanted to regenerate the state mine was supplied in as a starting point- hence D80020k and D80220c combination. D80220c is the latest, and I'm about to try going to D80020y/D80220c.
My D80220c system.img came from a TWRP backup I made after one of the kdz attempts. Also tried my original D80220b system.img and it too worked fine.
I may have been lucky, (no end of problems with drivers on Win7, as you'd know), but the logic is pretty strong.
Keep up the great work.
Last edited:
Upvote
0
Busybox wasn't happy with the root state and wouldn't install. Also couldn't get the SIM card active (unrelated?) so around I went again to end up at 8oo20u - which at least has the Knock-Unlock finally.
