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

Root Intl G2 32Gb S/W D80230B stuck in fastboot

A

aardvarkboy

Lurker
Hi everyone

I'm in a similar but not identical situation to the OP in this thread : http://androidforums.com/threads/in...-international-hong-kong-version-32gb.877957/
.. but with one key difference : my model has the D80230B software, while iowabowtech posted necessary files for D80220B

More specifically, my phone remains in fastboot mode, and is not seen as a device by either Linux or Win PCs other than through the fastboot pc client. Pressing up vol + power briefly moves the display to the 5 dot download, but then it reverts to fastboot. I have reflashed laf.img and TWRP recovery with fastboot but with no visible effect. I bought the phone as new from a Hong Kong dealer & have rooted it, but so far have not successfully got a TWRP up and running.

I'm nervous about flashing aboot and boot from the D80220B files ... so could someone kindly (a) let me know if these would be safe for my device with D80230B? or (b) post the equivalents for D80230B please ?

Many thanks
 
A related question : I was only able to fastboot the laf and TWRP files as sudo - hitting fastboot laf laf.img as regular user resulted in a 'waiting for device' message. Is this situation dangerous / bad and if so how can I fix it ?

Thanks for any advice
 
aardvarkboy said:
Hi everyone

I'm in a similar but not identical situation to the OP in this thread : http://androidforums.com/threads/in...-international-hong-kong-version-32gb.877957/
.. but with one key difference : my model has the D80230B software, while iowabowtech posted necessary files for D80220B

More specifically, my phone remains in fastboot mode, and is not seen as a device by either Linux or Win PCs other than through the fastboot pc client. Pressing up vol + power briefly moves the display to the 5 dot download, but then it reverts to fastboot. I have reflashed laf.img and TWRP recovery with fastboot but with no visible effect. I bought the phone as new from a Hong Kong dealer & have rooted it, but so far have not successfully got a TWRP up and running.

I'm nervous about flashing aboot and boot from the D80220B files ... so could someone kindly (a) let me know if these would be safe for my device with D80230B? or (b) post the equivalents for D80230B please ?

Many thanks
Click to expand...

aardvarkboy said:
A related question : I was only able to fastboot the laf and TWRP files as sudo - hitting fastboot laf laf.img as regular user resulted in a 'waiting for device' message. Is this situation dangerous / bad and if so how can I fix it ?

Thanks for any advice
Click to expand...

Firstly, you can restore the device via fastboot using older partitions. For this reason, I recommend flashing aboot, boot, dbi, laf, rpm, sbl1 and tz. This takes version conflict out of play.

If you have not had success flashing a D802 custom recovery to a D802 device, you may want to be sure that you in fact have a D802 phone. And by that I mean the motherboard. Unfortunately, there are a HUGE amount of devices which have been sold as D802's but in fact they have alternate motherboards...mostly D800's and some D801's. If you attempt to flash a D802 custom recovery to such a device it will fail and result in fastboot if you're lucky and qshusb_bulk (9006) or QDLoader (9008) if you are not quite as lucky. All of the above can be fixed however.

So my recommendation would be to ensure which motherboard your device contains which can be observed via this vid:

It should be noted however that if you were on a lollipop rom at the time of the fastboot screen showing up, you may not have fastboot connectivity. If you issue a fastboot reboot command and the phone accepts the command but does not reboot...this is a lollipop fastboot brick. And the only way I've found out of that is to short the capacitors and end up with either 9006 or 9008. Then you can fix from there. Fastboot seems to be broken in 5.x at least on some devices.
 
iowabowtech said:
Firstly, you can restore the device via fastboot using older partitions. For this reason, I recommend flashing aboot, boot, dbi, laf, rpm, sbl1 and tz. This takes version conflict out of play.

If you have not had success flashing a D802 custom recovery to a D802 device, you may want to be sure that you in fact have a D802 phone. And by that I mean the motherboard. Unfortunately, there are a HUGE amount of devices which have been sold as D802's but in fact they have alternate motherboards...mostly D800's and some D801's. If you attempt to flash a D802 custom recovery to such a device it will fail and result in fastboot if you're lucky and qshusb_bulk (9006) or QDLoader (9008) if you are not quite as lucky. All of the above can be fixed however.

So my recommendation would be to ensure which motherboard your device contains which can be observed via this vid:

It should be noted however that if you were on a lollipop rom at the time of the fastboot screen showing up, you may not have fastboot connectivity. If you issue a fastboot reboot command and the phone accepts the command but does not reboot...this is a lollipop fastboot brick. And the only way I've found out of that is to short the capacitors and end up with either 9006 or 9008. Then you can fix from there. Fastboot seems to be broken in 5.x at least on some devices.
Click to expand...

Thank you - that's reassuring.
On the sudo / non sudo question, is this an issue or not ? Most guides don't mention sudo-ing, but a few do and as above I currently need to sudo in order to flash
 
aardvarkboy said:
Thank you - that's reassuring.
On the sudo / non sudo question, is this an issue or not ? Most guides don't mention sudo-ing, but a few do and as above I currently need to sudo in order to flash
Click to expand...

Sudo if you need to. I'm guessing that's more of an issue on how your fastboot is set up on your local machine. Bottom line, we are taking executive actions here regardless so sudo is only some extra typing in this case, not much else. ;)
 
iowabowtech said:
Sudo if you need to. I'm guessing that's more of an issue on how your fastboot is set up on your local machine. Bottom line, we are taking executive actions here regardless so sudo is only some extra typing in this case, not much else. ;)
Click to expand...

Hi again

I've flashed the V20B aboot, boot, dbi, laf, rpm, sbl1 and tz images as you suggested. I then flashed TWRP recovery, also from fastboot. The good news is that phone is out of fastboot mode and now is recognised by adb . The bad news is (a) I can't boot into recovery or download modes, and (b) the stock rom UI is visible but touch is behaving weirdly, almost as if it thinks it has a differently sized screen - ie touch inputs land in the wrong place

When trying adb recovery, there was a brief message along the lines of boot certification error and mentioned secure boot. Is this related to what the loki tool helps overcome - and can you give some guidance on what to do next please ? (All the guides to loki I've seen online refer to 'loki flash', this has been replaced by loki_tool)

Many thanks

Steve
 
Firstly, I do not recommend flashing twrp recovery or any other recovery for that matter including the stock recovery. If you flash only the partitions I listed, then possibly download mode would have worked.

Also, do you truly know what model motherboard your phone contains? If you are flashing D802 partitions, its entirely likely that is not the correct choice. Did you follow the video I posted above to verify your model? If not, you may end up working in circles for a very long time.
 
hi everyone.
i watch the video and remove the cover.there on mother board. d800AT&T is written but before i update it to lollipop inside my phone contain d802 ROM which was working perfectly with every sim card mean it was open.so what i should do i have flash d80230B img files and now got download mode and recovery but unable to flash ROM. kdz method of flashing ROM stops auto at 2% on d80230b.

so what should i do.have i override partition tables?
and how can i go back to original rom. so mobile should start work?
thank you.
 
Not as many G2 people left these days. If you have download mode, flash a D800 tot. You'll have to hexedit the tot to read model D802 to bypass model check in LG Flash Tools. Also, you must use the 8974 dll I've posted in these forums several times to avoid cross dll error.
 
which framework version i should use?
currently my lg g2 got download mode and recovery by using d80230b.
but unable to run fastboot commands and when i check imei of my device online.it show me d802 on one site and d800 on another site. and HKG (hongkong ) region.
 
heart2hack said:
which framework version i should use?
currently my lg g2 got download mode and recovery by using d80230b.
but unable to run fastboot commands and when i check imei of my device online.it show me d802 on one site and d800 on another site. and HKG (hongkong ) region.
Click to expand...

You've already verified you have a D800 board per your earlier post. So as I mentioned, you use the D800 tot hexedited to read model d802. Along with 8974 dll. You flash that via download mode using the LG Flash Tools software. Fastboot mode is not an option in your current state. From here forward, you'll need to treat your phone as though it's a D800 in every way, because it is. It's the motherboard that matters.

What happened here is that whoever sold the phone likely flashed a D802 system.img so they could sell it as a D802. Very common situation, but as soon as one tries to modify/update the firmware to a newer D802 version, it fails because the partition tables don't match on the D800 vs D802. So what you had was the illusion of a D802 and that's why it shows up sometimes as a D802 when checking against the IMEI...it acquires that info from the last system it detected on the device. They get by with it because the D800 radios work internationally.
 
Last edited:
currently i have flashed D80230b img files and i have gotten download mode and other mode but stuck on logo.and when i try to flash the same rom on lg flash tool (kdz) than it stuck's at 2%.and when i try to flash another 802 rom using tot method.it give me an error partition error.
now i have downloaded d80020c rom and flash all the img files to the device but no download mode and it directly goes to fastboot and fastboot is unable to flash or erase any partition.

so what i do to solve this problem?
d80230b (download mode and other mode correct but unable to flash ROM)
d80020c (no download, fastboot not working mean unable to flash)
what i should do?
can you connect with me on team viewer and look at the problem?what's going on?
 
after doing the method of tot changing hexa code in tot file.after that when flash tool reach 6% it show me this error.
LAF_READ_GPT_FAILED
what i should do?
thank you.
 
Which specific partitions are you flashing to the phone? For a D800 board, recommend you flash the D800 img's for aboot, boot, dbi, laf, rpm, sbl1 and tz. That should get download mode. If it does not, then you may have to disassemble the phone further. Occasionally, even though it says D800 inside the phone, the actual board can be something else. The only way to know 100% is to remove the motherboard, the model # is stamped on the underside of the board.

I can't connect with you right now as I'm at work. Also, I have a new machine and its not yet set up for remote assistance. You might check with @James L to see if he's available if you need faster assistance. I believe he's done some of these as well.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom