[G2 General] devnulldne:
Are you sure you're in "bulk mode"

I'm having a similar issue. No one is responding to me. Either they're arrogant or they simply don't know how to help us. Which LG model do you have? I have an LS980.

---------- Post added at 03:41 PM ---------- Previous post was at 02:58 PM ----------

I have that same variant of the G2 and I also downgraded my aboot, but I forgot to flash the recovery after I did it, so my phone is stuck at the LG boot logo with no recovery and a broken download mode. You think you can help me? The Device Manager in Windows recognizes my device as a HD Audio Bus (whatever that means), and when using the terminal on Linux, it doesn't show at all.

"Bulk Mode" is pretty recognizable because your screen is blank but the backlight is on so the screen actually looks kinda grey (that's what it looks like for me). I have the sprint LG G2 and had the same problem and I could get into bulk mode by first getting into factory reset mode. Once in reset mode I hit the power button a few times and it didn't reset my phone but errored out and went into "bulk mode" but CAUTION: I did have a custom recovery (TWRP 2.7.0.0) installed at this point and so my situation was different from yours so as always YMMV. Also, I can't remember if the screen went blank or not so even if it doesn't, go ahead and plug your phone in and boot Linux and see if it works. Also also, I think the reason my custom recovery did not work is because I installed straight into 2.7.0.0 and I read somewhere you have to start with 2.6.3.3 and then flash to 2.7.0.0 for it to work, or maybe 2.7 just doesn't work for this I don't know.

So once in bulk mode boot into linux and you should have a device with 39 partitions.

NOW FOR THE EXTREME CAUTION:

Back up your partitions before trying any of the dd commands. You can do this by typing:

dd if=/dev/sd?# of=/"wherever you want to backup to.img"

the ? is whichever letter your phone is (i.e. the one 39 partitions) and the # is whichever partition you want to backup.

MORE EXTREME CAUTION:

Also before trying the dd commands make sure you have the right files which are not the ones posted in this thread. There is a link to the right files somewhere in xda and I'll update this post if I ever find it again.

YES EVEN MORE EXTREME CAUTION:

Even with the right files I ended up borking my system even more because dd wasn't writing correctly to these partitions and that is why you really need a backup first.

What I would do if I had to do this over again:

1: backup ( dd if=/dev/sd?# of="whatever you want.img" )

2: run gdisk /dev/sd? (where ? corresponds to your phones letter) to make sure you know which partition number corresponds with the partitions you want to mess with i.e. for me 5 was aboot 15 was recovery etc...

3: never touch the aboot partition until you know dd works right

4: to test dd I'd compare the recovery.img file I know I flashed with what is in my phones recovery partition i.e. ( cmp recovery.img /dev/sd?15 where 15 is your recovery partition that you got from step 2)

* if you don't know the recovery you flashed then I'd just go to 5b

5a: if the cmp doesn't pass then you're probably hosed but you can go ahead and do step 5b if you really want to risk it

5b: If the cmp passes I would copy (using dd) the same recovery.img to the recovery partition and do a cmp again i.e. ( dd if=recovery.img of= /dev/sd?15 )

6: if the cmp passes then celebrate and follow these steps over again to copy whatever images to whatever partitions you want.

6* I think only the right aboot and recovery images need to be flashed but I have not been able to test this so stick with the threads original instructions unless you feel like experimenting

7: if any of the cmp's ever fail then hope that recopying the backup actually works and then try a different computer cause all the distros I've tried have the same dd problem for my phone and my only computer.

---------- Post added at 12:49 PM ---------- Previous post was at 12:26 PM ----------

What dd seems to be doing for me is only writing the first 64k bits. I found this out by doing a compare i.e. cmp aboot.img /dev/sd?5 where ? is the corresponding letter to my phone and the 5 corresponds to the aboot partition. The first bit that was not an exact copy was 65537. I don't know if this dd problem is solvable for me as even dd-ing the original aboot that caused the problem back into the correct partition does not pass the cmp test.

So if anyone knows an alternative to dd I'd appreciate it very much. Also, if someone, with a sprint phone, can send me the backup of there aboot partition from bulk mode I want to see if I can just try to copy that in order to get the right first 64k bits back. Pretty Please :(