Root [International] D802 Stuck on fast boot - custom fix? HELP

[Harris Naught]

As all these fastboot issues start, I flashed the wrong ROM version for my D802 - and I'm now stuck in fastboot mode.

I've looked at various fixes and have all the files/drivers.

So through adb I'm going to do the following:
fastboot erase recovery
fastboot erase laf
fastboot flash laf laf.img
fastboot reboot

So this should potentially get me into download mode where I can flash a stock kdz - BUT - I was thinking
Is it possible to somehow:
flash a custom recovery and boot directly to it
push a custom rom onto the sdcard (adb)
flash the rom through the custom recovery
and boot to the custom rom

INSTEAD of flashing a kdz - having a stock phone - and losing all your backed up stuff (Titanium backups etc.)

Is this possible? And if yes could anyone write some brief instructions?

Appreciate it!

 

[Harris Naught]

UPDATE:

I'm out of fastboot and now into Download Mode.

Is it now possible to flash a custom rom / recovery? - or is this too ambitious?

 

[iowabowtech]

I would highly recommend that you flash a kdz or tot in order to ensure all your partitions are from a matching firmware version. If not, the boot chain could be broken and it could give you fits.

 

[Harris Naught]

Thanks for responding @iowabowtech,

I'm currently downloading one of the zips from here which i believe is a .tot:
http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware

Would flashing a tot overwrite existing data on the sdcard partition?

The reason for getting into fastboot in the first place was due to flashing Cloudyfa (one of the Korean) versions by mistake. Surprisingly the same issue as this http://androidforums.com/threads/unbrick-lg-g2.898544/

Is it necessary to hex edit the .tot? or can I just flash the downloaded one? Surely any changes made by the custom rom on the current .tot would be over written by the new .tot?

 

[iowabowtech]

Correct it will be overwritten and yes sdcard will be wiped. If the phone is perceived by lg flash tools as something other than a d802, then you'll have to hexedit the tot to whatever the cloudfya rom would have called the model, in addition to using a generic device dll in lieu of the standard d802 lgflash dll. Its critical to ensure the tot you're using is for the same size internal storage your phone contains (16/32 GB)

 

[Harris Naught]

Ah crap - I'm not sure what Korean version I clicked on in the aroma installer (choice of 3). So I wouldn't know what to replace the d802 with in the hex editor!

Instead, would it be worth following the .kdz method using "Normal" flash (as opposed to CSE) in flash tools? (obv - to preserve data as a priority if possible)

Regarding your initial reply, I flashed all the partitions in fastboot as below:
(from 10b_EUR_16G_partitions)
fastboot flash boot boot.img
fastboot flash aboot aboot.img
fastboot flash recovery recovery.img
fastboot flash laf laf.img
fastboot flash dbi dbi.img
fastboot flash modem modem.img
fastboot flash persist persist.img
fastboot flash PrimaryGPT PrimaryGPT.img
fastboot flash rpm rpm.img
fastboot flash sbl1 sbl1.img
fastboot flash tz tz.img

fastboot reboot

 

[Harris Naught]

Ok through the .kdz method - I can see that I've installed F320L.

So I'm trying via the .tot method but receiving the following error:

 

[Harris Naught]

RIGHT - I flashed the F320L dll - with a NON hex edited .tot - and it worked fine!

Software Info:
Android version: 4.2.2
Software version: D80210b-EUR-XX

Can't seem to find any trace of the Korean F320L? I guess that's a good thing?

Thanks to @Inferi 's post this has worked. Also cheers to @iowabowtech !

Time to re-root and get flashing again - hopefully the right rom this time.