Database Users

My LG G2 is COMPLETELY bricked.

So after 20 hours of fiddling... I can safely say that this LG G2 D803 is completely done.
Given by a friend, the phone started off by booting straight to fastboot, and had download mode available after he flashed a ROM designed for a tablet.
I attempted the .TOT method described here, where I used LGTools. I then only realized that this method was only suitable for an US device, such as AT&T, T-Mobile, or Verizon (couldn't find a Rogers .TOT). I didn't modify the phone in any way.
I then continued to download the Rogers KDZ file here. Using the method described in the same post above, I performed the upgrade, only to realize that this was method wasn't working either.
I then did some scouring to find a way to boot into TWRP (which was already installed). I found this trick: If you hold the power button down until the phone turns off, you can hold power and down until you see the LG symbol, and then depress and press them again immediately to get into TWRP!
In TWRP... I realized that the partitions were all messed up. It was showing 6GB internal, and countless errors were popping up. Another dead end. ADB was working, but I was unable to push anything.
I then realized I should attempt to flash updated partitions using fastboot. Using the cmd line in Windows, I erased and flashed partitions I downloaded here after putting the phone in fastboot mode.
This is where I did something stupid.
Instead of clicking and downloading on that site, I right-clicked "save-as" and downloaded 8kb corrupted partition files. I continued and flashed them unknowingly... and right after, the phone decided to not boot at all.
Using VMWARE and Ubuntu 14.04, I attempted to reflash the partitions using Linux commands described here. Unfortunately, the device would not show the /sd* partitions. Certainly, the bootloader that communicates with the PC does not allocate the partitions properly anymore.
Alright, the phone wont boot, because I flashed a bad bootloader. No biggie right? I would see the device as Qualcomm hs-usb qdloader 9008.
That's when I scoured for a new method to fix the partitions. I came across QPEST and eMMC Software App to get this device back alive.
I spent hours trying to find the right .hex and .mbn file on Chinese websites. I found 8974_msimage.mbn, MPRG8974.hex, flash.xml, rawprogram0.xml and patch0.xml. I had to create accounts of a bunch of sites to finally download the correct files.
Carefully using QPST, I was able to get the phone in Download Mode (Qualcomm download mode, not LG download mode), and pushed the instructions to the device.
... too bad. I thought I did everything right. The device times out in the process EVERYTIME.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The phone is officially dead, there isn't a way I know of to get it started (at least to fastboot again). It really pays off to check what you're flashing before you do it. The internet is full of crap.

BuffMcBigHuge said:
So after 20 hours of fiddling... I can safely say that this LG G2 D803 is completely done.
Given by a friend, the phone started off by booting straight to fastboot, and had download mode available after he flashed a ROM designed for a tablet.
I attempted the .TOT method described here, where I used LGTools. I then only realized that this method was only suitable for an US device, such as AT&T, T-Mobile, or Verizon (couldn't find a Rogers .TOT). I didn't modify the phone in any way.
I then continued to download the Rogers KDZ file here. Using the method described in the same post above, I performed the upgrade, only to realize that this was method wasn't working either.
I then did some scouring to find a way to boot into TWRP (which was already installed). I found this trick: If you hold the power button down until the phone turns off, you can hold power and down until you see the LG symbol, and then depress and press them again immediately to get into TWRP!
In TWRP... I realized that the partitions were all messed up. It was showing 6GB internal, and countless errors were popping up. Another dead end. ADB was working, but I was unable to push anything.
I then realized I should attempt to flash updated partitions using fastboot. Using the cmd line in Windows, I erased and flashed partitions I downloaded here after putting the phone in fastboot mode.
This is where I did something stupid.
Instead of clicking and downloading on that site, I right-clicked "save-as" and downloaded 8kb corrupted partition files. I continued and flashed them unknowingly... and right after, the phone decided to not boot at all.
Using VMWARE and Ubuntu 14.04, I attempted to reflash the partitions using Linux commands described here. Unfortunately, the device would not show the /sd* partitions. Certainly, the bootloader that communicates with the PC does not allocate the partitions properly anymore.
Alright, the phone wont boot, because I flashed a bad bootloader. No biggie right? I would see the device as Qualcomm hs-usb qdloader 9008.
That's when I scoured for a new method to fix the partitions. I came across QPEST and eMMC Software App to get this device back alive.
I spent hours trying to find the right .hex and .mbn file on Chinese websites. I found 8974_msimage.mbn, MPRG8974.hex, flash.xml, rawprogram0.xml and patch0.xml. I had to create accounts of a bunch of sites to finally download the correct files.
Carefully using QPST, I was able to get the phone in Download Mode (Qualcomm download mode, not LG download mode), and pushed the instructions to the device.
... too bad. I thought I did everything right. The device times out in the process EVERYTIME.
The phone is officially dead, there isn't a way I know of to get it started (at least to fastboot again). It really pays off to check what you're flashing before you do it. The internet is full of crap.
Click to expand...
Click to collapse
there is a lot of crap on the internet but when you start fastbooting or dding partitions without verifying the integrity of the stuff you downloaded you will eventually brick something. Perhaps this experience will goad you into checking md5 or sha1 before you go about flashing things.

DeathmonkeyGTX said:
there is a lot of crap on the internet but when you start fastbooting or dding partitions without verifying the integrity of the stuff you downloaded you will eventually brick something. Perhaps this experience will goad you into checking md5 or sha1 before you go about flashing things.
Click to expand...
Click to collapse
It's very rare that I ensure the md5 is correct. In this case, the file sizes were completely off (8kb rather than 512kb), which is more noticeable than the hash. You're absolutely right. I sent the phone to MobileTechVideos for a JTag repair. I'll post the results when I get it returned.

You made a valiant effort, good luck man.

My hat goes off to you, man. Is it under a warranty that covers accidental damage? A good smashy-smashy would cover your tracks and relieve your stress all at once

I tell you though - fine attempt. Made my day reading this. Never stop at no. Hope you get your phone fixed.
Onward.
Sent from my LG-D802 using XDA Premium HD app

1 LG G2 down
20 million+ units still in combat working the daily grind!

Now phone is dead so go to the warranty method.

BigBoyPL said:
Now phone is dead so go to the warranty method.
Click to expand...
Click to collapse
he did the RIGHT thing and sent it to be repaired at his cost. to do what you are implying is to be a thief.

xlr8me said:
1 LG G2 down
20 million+ units still in combat working the daily grind!
Click to expand...
Click to collapse
make it 2 lg g2 mine is dead too...
mine is back to life finally

Can you not use a fastboot cable and re flash the correct partition images from there. I used that method to recover a completely bricked Kindle fire recently.

ClawOfDoom said:
Can you not use a fastboot cable and re flash the correct partition images from there. I used that method to recover a completely bricked Kindle fire recently.
Click to expand...
Click to collapse
I think this are the cases when the warranty should be used. The phone is not on it's best condition, so that should take care of this.

Any updates on the repair? I have a bricked D801 too...

zPacKRat said:
he did the RIGHT thing and sent it to be repaired at his cost. to do what you are implying is to be a thief.
Click to expand...
Click to collapse
I respectfully disagree. everything described is software related. The hardware is still fine. At least from what I was reading. Which means the phone could be sent back, under warranty and repaired in probably under 5 minutes. It might get a dollars worth of new plastic on it. Repackaged up and sent off to somebody else to replace their broken phone. The losses on the replacement phone would be recouped almost instantly.
Sent from my VS980 4G using Tapatalk

Can you help me.
Dear BuffMcBigHuge!
I have a situation same you, Now my LG G2 L-01F - NTT DOCOMO total Dead, it show Qualcomm HS-USB QDLoader only.
I searched many forum, but havent find out these file.
Can you give me these file for me to try unbrick My G2.
My email: [email protected]
Many thanks you.

dm6939 said:
Dear BuffMcBigHuge!
I have a situation same you, Now my LG G2 L-01F - NTT DOCOMO total Dead, it show Qualcomm HS-USB QDLoader only.
I searched many forum, but havent find out these file.
Can you give me these file for me to try unbrick My G2.
My email: [email protected]
Many thanks you.
Click to expand...
Click to collapse
+1 = I have the same here...

So after sending the device to MobileTechVideos, I was able to get it fully repaired and back into working order! They converted it to a D801, and its back in full working order!
Highly recommended!

BuffMcBigHuge said:
So after sending the device to MobileTechVideos, I was able to get it fully repaired and back into working order! They converted it to a D801, and its back in full working order!
Highly recommended!
Click to expand...
Click to collapse
Fantastic news glad there are still teams that are dedicated to there work and know what they are doing
Danzano's happy place

Danzano said:
Fantastic news glad there are still teams that are dedicated to there work and know what they are doing
Danzano's happy place
Click to expand...
Click to collapse
Any more updates here ? looks like we need 2 important files specific to the G2 . The .hex and the mnb file to enable writing to eMMC.

zathus said:
I respectfully disagree. everything described is software related. The hardware is still fine. At least from what I was reading. Which means the phone could be sent back, under warranty and repaired in probably under 5 minutes. It might get a dollars worth of new plastic on it. Repackaged up and sent off to somebody else to replace their broken phone. The losses on the replacement phone would be recouped almost instantly.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
bc OP stated:
"Given by a friend, the phone started off by booting straight to fastboot, and had download mode available after he flashed a ROM designed for a tablet"
so when a device is broken, (whether it be hardware or software) by the user, that is not a manufacturer defect. That is misuse, nonwarranty. thats why the guy you responded to said "he did the RIGHT thing and sent it to be repaired at his cost. to do what you are implying is to be a thief." and i agree with him. I actually cringe when i see people on here brick their phones, then ask for ways to unroot so they can get it repaired under warranty. Manufacturers are going to continue to make it harder to gain root access bc im sure theyre tired of wasting time on people who broke their phones themselves, then want it repaired for free. sigh...

Back from Repair - Fastboot Flash Mode (Not Secure) and "ENGINEERING"

Hi all,
so after I cracked my Screen I send my device to a service provicer to repair it. The device is back and the display is fine again.
Though there are certain concers on which I'd need advice. Service provider did not react to my E-Mail yet.
So my Style was bootloader unlocked before and had TWRP installed. Though never rooted. Now that the device is back, it seems that the bootloader is locked again and when I boot into Fastboot I see two entries which concern me:
1.)
AP Fastboot Flash Mode (Not Secure)
(in red)
2.)
Device is ENGINEERING
(in yellow)
As well, the IMEI number changed and my Storage doubled. 32 -> 64 gig (which is not bad though ). Not sure why that happened. Probably so much glue that they needed to exchange more.
Another consequence is, that I'm not able to unlock the bootloader again, which bothers me somewhat. I get the key from Motorola, but when I run the fastboot command it fails with a short display flash on the phone.
So, long story. Do you guys know if the two entries mentioned in Fastboot are problematic in some way? Are those keeping me from unlocking again? Can I fix those on my own if necessary?
Best regards
Simon

An Engineering Bootloader is supposed to be completely unlocked, even more so than regular "bootloader unlock" if the official Moto forums are to be believed, it cannot be changed to locked or unlocked (fails every time), but in the Moto G 3rd gen community here we have several users with an engineering bootloader status and they have very sporadic issues with ROMs. For example RR 5.7.2 works but 5.7.3 fails, CM13 older nightlies work but current ones fail, certain kernels work and others do not, it is very weird.
To my (limited) knowledge, this is the first Engineering bootloader seen on a X Style/Pure here, you are in uncharted waters so proceed with caution...

FYI... Due to the fact that several users have seen this in the Moto G community, and it's started showing up in the Moto X Pure community, I posted in the Lenovo forums for more information on this in this thread.
The response was quite clear from AlphaDog (Moto Sr Moderator):
The phones should not be showing Engineering. If you get a phone back this way, it was not flashed properly and needs to be reflashed - call customer service and make arrangements to have it reflashed.
Click to expand...
Click to collapse

If your storage doubled and IMEI changed, then one if two things happened. 1. They gave you another phone other than your own (very likely), or 2. They seriously borked it when they reinstalled the ROM (which would explain the ENGINEERING status).

aybarrap1 said:
If your storage doubled and IMEI changed, then one if two things happened. 1. They gave you another phone other than your own (very likely), or 2. They seriously borked it when they reinstalled the ROM (which would explain the ENGINEERING status).
Click to expand...
Click to collapse
Due to weird issues that Moto G have... I'm leaning towards #2, or both.
Sent from my Motorola XT1575 using XDA Labs

Thanks all for your responses. I'm very sorry for my late reply, gmail hid the subscription emails in some subfolder (=
So an indeed very weird issue. I can confirm that it is at least the original outer frame of my phone. I had one customized from Moto maker and it had some unique scratches So they probably f***** up installation / flash. I'll try to get back with that provider an see what they say about it.
The first response on my question WHY that is, and that I'm now unable to unlock my bootloader was:
"Why are you booting Fastboot instead of normal? And you loose warranty if you unlock!"
...which of course is neither an answer to one of my questions nor helpful in any way.

I also had sent my phone in for repair a few months ago (screen stopped responding to touch, they wouldn't fix it because root, replaced myself, very frustrating ordeal) and have a similar issue.
I don't have the same colored entries as you, but every single time I boot now it goes directly to the bootloader instead of starting up normally. This includes when I reboot while using the phone, as well as when specifically using the advanced reboot menu to go into recovery which basically makes the whole menu pointless.
Very annoying problem when you have to wait for the bootloader to startup and then press the button to get it to start.
Anyone have any ideas on how to fix it?
Sent from my XT1575 using XDA-Developers mobile app

black_valor said:
I also had sent my phone in for repair a few months ago (screen stopped responding to touch, they wouldn't fix it because root, replaced myself, very frustrating ordeal) and have a similar issue.
I don't have the same colored entries as you, but every single time I boot now it goes directly to the bootloader instead of starting up normally. This includes when I reboot while using the phone, as well as when specifically using the advanced reboot menu to go into recovery which basically makes the whole menu pointless.
Very annoying problem when you have to wait for the bootloader to startup and then press the button to get it to start.
Anyone have any ideas on how to fix it?
Click to expand...
Click to collapse
fastboot oem fb_mode_clear
Sent from my Motorola XT1575 using XDA Labs

hdyim said:
Hi all,
so after I cracked my Screen I send my device to a service provicer to repair it. The device is back and the display is fine again.
Though there are certain concers on which I'd need advice. Service provider did not react to my E-Mail yet.
So my Style was bootloader unlocked before and had TWRP installed. Though never rooted. Now that the device is back, it seems that the bootloader is locked again and when I boot into Fastboot I see two entries which concern me:
1.)
AP Fastboot Flash Mode (Not Secure)
(in red)
2.)
Device is ENGINEERING
(in yellow)
As well, the IMEI number changed and my Storage doubled. 32 -> 64 gig (which is not bad though ). Not sure why that happened. Probably so much glue that they needed to exchange more.
Another consequence is, that I'm not able to unlock the bootloader again, which bothers me somewhat. I get the key from Motorola, but when I run the fastboot command it fails with a short display flash on the phone.
So, long story. Do you guys know if the two entries mentioned in Fastboot are problematic in some way? Are those keeping me from unlocking again? Can I fix those on my own if necessary?
Best regards
Simon
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The two entries never gave me any problems I also have an engineering bootloader.
Sent from my XT1572 using XDA-Developers mobile app

[email protected] said:
The two entries never gave me any problems I also have an engineering bootloader.
Click to expand...
Click to collapse
It doesn't give you an problems because your still stock. Moto has officially said this shouldn't happen and anyone with this should contact customer support to get it flashed correctly.
Sent from my Motorola XT1575 using XDA Labs

acejavelin said:
It doesn't give you an problems because your still stock. Moto has officially said this shouldn't happen and anyone with this should contact customer support to get it flashed correctly.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
So then for me no need to worry.. Not planning to flash anything other then stock and as long it doesn't give any problems with rooting and flashing some mods I won't return it ...
Sent from my XT1572 using XDA-Developers mobile app

Bootloop until the battery is dead (unable to boot to fastboot)

Hmm, i was using my Nexus 6p as usual and i don't have any problem with it. One day i woke up because of my alarm rings, i closed the spotify and unplug the headphone. The phone automatically rebooted and does not stop at all until the battery dead. I was thinking about it is bootlooping so i decided to get into recovery and wipe the cache. However, i can't even get into bootloader because when i successful went into bootloader, within 1 second, the device automatically reboot again and start bootlooping. I don't have any chances to boot into recovery. I tried to flash new image but unfortunately does not work.
I asked my friend who is doing phone repair to check whether it is power button stuck or other possible problems to make this thing happen. The results are power button and battery working fine and does not broken or not functioning. I was about to send my Nexus 6p to Huawei Service Center since there is no Google Service Center in my country. Before that, i want to know if anyone has this kind of problem? I would like to fix this myself if possible and if there is any solution for it. Thanks and sorry for my bad english. I have provided a video sample about the situation of my Nexus 6p to show if anyone of you don't know what kind of problem i am facing right now. Please also ignore the sound of my video because of my bad shooting skill.
My Nexus 6p currently on
Android 8.1.0 Beta 1
Some photo sample of how i tried to reflash new image to my Nexus 6p in bootloader below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Video sample of my Nexus 6p situation (seems like the video cannot be played in the post, i will give the link instead. Sorry about that)
https://www.youtube.com/watch?v=uiy-ToOPrP0&

https://forum.xda-developers.com/nexus-6p/general/guide-tutorial-nexus-6p-bootloop-death-t3716330

Exodusche said:
https://forum.xda-developers.com/nexus-6p/general/guide-tutorial-nexus-6p-bootloop-death-t3716330
Click to expand...
Click to collapse
Thanks for your helping. I have a question about that, the post is trying to said that i should flash the 4core patched boot image file right?

yaohui said:
Thanks for your helping. I have a question about that, the post is trying to said that i should flash the 4core patched boot image file right?
Click to expand...
Click to collapse
Yes you need your bootloader unlocked and then fastboot the 4corefix.img for 8.1. I understand you can't keep your phone on long enough to use fastboot. So you will have to sort that out first. Only thing I remember someone being able to do was heating up the back of the phone with hairdryer. That way it would stay on long enough to preform. There might be more ideas how you will have to read through the article.

Exodusche said:
https://forum.xda-developers.com/nexus-6p/general/guide-tutorial-nexus-6p-bootloop-death-t3716330
Click to expand...
Click to collapse
Exodusche said:
Yes you need your bootloader unlocked and then fastboot the 4corefix.img for 8.1. I understand you can't keep your phone on long enough to use fastboot. So you will have to sort that out first. Only thing I remember someone being able to do was heating up the back of the phone with hairdryer. That way it would stay on long enough to preform. There might be more ideas how you will have to read through the article.
Click to expand...
Click to collapse
Thanks, Appreciated. I will try it.

yaohui said:
Thanks, Appreciated. I will try it.
Click to expand...
Click to collapse
Download the appropriate image on your computer and get fastboot ADB all set up. Then heat the back of your phone with hairdryer (just above the battery) until nice and warm. Then try and boot your phone into bootloader mode and see if it stays. Then quickly unlock bootloader then flash modified 4core boot.img. Make sure you download the one for 8.1 .

Exodusche said:
Download the appropriate image on your computer and get fastboot ADB all set up. Then heat the back of your phone with hairdryer (just above the battery) until nice and warm. Then try and boot your phone into bootloader mode and see if it stays. Then quickly unlock bootloader then flash modified 4core boot.img. Make sure you download the one for 8.1 .
Click to expand...
Click to collapse
My bootloader is unlocked at first actually, so now i'm going to try to flash the modified 4core boot.img.

Exodusche said:
Download the appropriate image on your computer and get fastboot ADB all set up. Then heat the back of your phone with hairdryer (just above the battery) until nice and warm. Then try and boot your phone into bootloader mode and see if it stays. Then quickly unlock bootloader then flash modified 4core boot.img. Make sure you download the one for 8.1 .
Click to expand...
Click to collapse
no luck
am i doing the right thing? I did not heat up my Nexus 6p yet because 2am now here. If really need the hairdryer to warm up, i will try it later.

yaohui said:
no luck
am i doing the right thing? I did not heat up my Nexus 6p yet because 2am now here. If really need the hairdryer to warm up, i will try it later.
Click to expand...
Click to collapse
Ok my bad I didn't read correctly your not on latest 8.1 December your on 8.1 beta 1?
Maybe need a different image. Might be easier to first flash latest stable 8.1 but go though the image list and see if yours is there.

Exodusche said:
Ok my bad I didn't read correctly your not on latest 8.1 December your on 8.1 beta 1?
Maybe need a different image. Might be easier to first flash latest stable 8.1 but go though the image list and see if yours is there.
Click to expand...
Click to collapse
Actually, I did perform flash using all of the modified boot.img and all the result are same. I will try to look into it more.

yaohui said:
Actually, I did perform flash using all of the modified boot.img and all the result are same. I will try to look into it more.
Click to expand...
Click to collapse
See if you can flash the latest 8.1 Stable then go back and flash the first image we tried.

Exodusche said:
See if you can flash the latest 8.1 Stable then go back and flash the first image we tried.
Click to expand...
Click to collapse
it seems like my Nexus 6p remain the same situation after warm up the back of the phone using hairdryer.

yaohui said:
it seems like my Nexus 6p remain the same situation after warm up the back of the phone using hairdryer.
Click to expand...
Click to collapse
Sorry to here that it was a shot in the dark. Are you able to flash stock image through fastboot?

Exodusche said:
Sorry to here that it was a shot in the dark. Are you able to flash stock image through fastboot?
Click to expand...
Click to collapse
I don't think i am able to do that since my Nexus 6p reboot automatically even in bootloader

Besides, i realise one thing that when my phone is on bootlooping, normally you will need to hold power button + volume up + volume down to get into bootloader. but in my case i don't need to. During bootloop, i just need to hold volume down and it will go through bootloader. but the result is still same as previous which is bootlooping still.

yaohui said:
Besides, i realise one thing that when my phone is on bootlooping, normally you will need to hold power button + volume up + volume down to get into bootloader. but in my case i don't need to. During bootloop, i just need to hold volume down and it will go through bootloader. but the result is still same as previous which is bootlooping still.
Click to expand...
Click to collapse
I think your motherboard is fried. The people at repair shop unable to do anything? If you go to the service centre, they'll ask you to replace the motherboard. How old is the phone?

tropical cactus said:
I think your motherboard is fried. The people at repair shop unable to do anything? If you go to the service centre, they'll ask you to replace the motherboard. How old is the phone?
Click to expand...
Click to collapse
Yup, the guy just told me the same thing that i might have to change the motherboard. He asked me to send to the official service centre is the best solution. My phone is around 2 years. I just posted here to see if anyone is facing this kind of problem and looking for solution to fix myself. Since the motherboard is fried, i think i can't do anything for it unless i change the motherboard, so i think i will send to service centre later. Thanks for your reply and @Exodusche your help.

Galaxy S4 Play Edition (GT-I9505G) and Lineage OS 15.1

Hello folks,
I have Galaxy S4, Play Edition, GT-I9505G, currently running SlimROM 7.1.2 build 1.17 (dated 20180115) and baseband version I9505GUEUDNL3.
Last stock I had on this phone was Android 5.0. If there was any OTA after that, I didn't install it.
(Sam Mobile does not list this device, hence no way of knowing firmwares, but https://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4/GT-I9505G lists mine as the last firmware.)
I have been trying to install Lineage 15/Oreo ROMs and with every ROM I am getting Error 7, which is supposedly Recovery error but every time I have used the recovery recommended by the ROM administrator. So its definitely not a recovery issue in my case.
I was wondering, those with same device, managed to install Oreo ROM, what is your baseband version? Most likely, this is the culprit, but to be sure, I would like to know at least one person with same device and different baseband version that managed to install Oreo ROM.
This page (https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624) list a lot of stock ROMs. Mine is half way through. Hence, I would like to see someone with newer baseband running Oreo ROM.
Many thanks in advance.

Did you check the updater script to ensure the phone's model # is included?

audit13 said:
Did you check the updater script to ensure the phone's model # is included?
Click to expand...
Click to collapse
Yes. All the ROMs I tried were for I-9505 of which I-9505G is a variant. I also removed that part of the script, just in case, but the same error occurred.

fuzzychicken said:
Yes. All the ROMs I tried were for I-9505 of which I-9505G is a variant. I also removed that part of the script, just in case, but the same error occurred.
Click to expand...
Click to collapse
Maybe you need to add the gt-i9505g to the list rather than removing it.

audit13 said:
Maybe you need to add the gt-i9505g to the list rather than removing it.
Click to expand...
Click to collapse
It was already there, so the ROMs were compatible but I removed just in case, thought if it is not working with the model number in it, maybe I can try without it, as recommended on some other blog posts on the web.

I guess the only other thing would be to try different versions of TWRP.

audit13 said:
I guess the only other thing would be to try different versions of TWRP.
Click to expand...
Click to collapse
I am sorry, thats what I said in the OP. I have tried every possible version of TWRP that was recommended for those ROMs and the error keep showing up. That indicates that its not recovery that is causing the problem.

Only thing left I can think of would be to flash the latest stock ROM, factory wipe, flash twrp, then wipe, and then flash the custom ROM.

audit13 said:
Only thing left I can think of would be to flash the latest stock ROM, factory wipe, flash twrp, then wipe, and then flash the custom ROM.
Click to expand...
Click to collapse
That is what I am thinking but I am not too sure which is the latest stock ROM.
https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 On this page, there are loads of stocks. Mine is half way through. Its I9505GUEUDNL3_FULL. Assuming that the list goes down as newer stocks, esp looking at the last 3 alpha-numerics, should I be flashing I9505GUEUDPF1_FULL?
If I flash, I9505GUEUDPF1_FULL will it write new bootloader and baseband? If yes, do I have to go through whole unlock bootloader thing? or just flash twrp via Odin and go ahead with newer ROM? This is the most sticky part as I don't remember how I did it in the past. I just don't touch something I am not very clear understanding on, but this time I would like to update to Oreo, primarily for security purpose and the cash is tight so if I brick this, I wouldn't be very happy to buy another device. Hence trying to dot all i's and cross all t's.
Thanks for all help in advance.

Flashing a stock ROM with Odin will update the bootloader and modem.
The bootloader is not locked and has never been locked on the gt-i9505.

audit13 said:
Flashing a stock ROM with Odin will update the bootloader and modem.
The bootloader is not locked and has never been locked on the gt-i9505.
Click to expand...
Click to collapse
Thank you.
Let me put it in steps, pls correct me if I am wrong.
1. Flash I9505GUEUDPF1_FULL using Odin. Once rebooted, confirm if newer baseband is present. Check if the calls and data works.
2. Flash TWRP recovery using Odin (it will revert to stock recovery, right?) If not, alls good as it is.
3. Install ROM of choice.
There is no data on the phone, I reflashed SlimROM after all attempts of Oreo failed.
Anything tricky stuff in between?
Thanks in advance.

To prevent the stock recovery from overwriting twrp, uncheck everything in Odin except for reset time, flash twrp, when you see the word "reset" in the status window, remove the usb cable from phone, remove the battery, replace the battery, boot into twrp.

audit13 said:
To prevent the stock recovery from overwriting twrp, uncheck everything in Odin except for reset time, flash twrp, when you see the word "reset" in the status window, remove the usb cable from phone, remove the battery, replace the battery, boot into twrp.
Click to expand...
Click to collapse
I am very sorry to be a PITA, mate, but I really need help here.
As per the suggestions, I tried flashing various images. In every image I flashed, the calling and wifi worked but cell data didn't work in any of those versions. Still I tried flashing Oreo with them but the error persisted. So probably, its something beyond I can do it with my little knowledge.
So finally, to give up I tried going to back to where I was before all this, to baseband version, I9505GUEUDNL3. I flashed NL3 image linked in the post https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 through Odin. While the OS shown in about phone is 5.0, the baseband version is stuck at OJ1, where the data does not work.
Any idea how I can go back to NL3 where data worked flawlessly?
Many thanks in advance.
Edit: I flashed NL3 modem from https://forum.xda-developers.com/showthread.php?t=2452034 but still the issue persists. I have nandroid backups from the very first time when I flashed another ROM. If I use that to restore, will it restore all the issues?

The bootloader and modem should be flashed in tandem to maintain compatibility with each other. Data may not be working due to a mismatch.
Flash the latest stock ROM from sammobile.com, updato.com, or samsung-firmware.org.

audit13 said:
The bootloader and modem should be flashed in tandem to maintain compatibility with each other. Data may not be working due to a mismatch.
Flash the latest stock ROM from sammobile.com, updato.com, or samsung-firmware.org.
Click to expand...
Click to collapse
Thank you.
Can you pls take a look at this thread? https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 Supposedly, these are factory images. I tried these images and my best guess is, they have right bootloader and modem. None of the sites you suggested carry stock images for GT-I9505G (Play Edition). They have GT-I9505 though.
What I tried so far.
- Flashed images linked above. Didn't work
(at one point, I even got OTA, when I was on OE1 baseband, it updated to OJ1. So in theory, in this OTA, it should fix this mismatch bootloader and modem, right?) When things didn't change after this update. I tried to flash NL3 image.
- Flashed NL3 image which I had. The baseband remained at OJ1. This was odd to me. So flashed NL3 modem. The issue persisted.
- I had taken nandroid backup before I started flashing custom ROMs. I tried to restore that back up through a custom recovery, TWRP. No help.
Screenshot of that backup, if it tells you anything
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- I have EFS Backups, but I don't quite remember how I took that backup.
Screenshot attached. Any idea if this can be used to restore everything in one shot. I don't know if EFS contains bootloader as well.
You mentioned I should flash stock ROM. Assuming that ROM images linked on the XDA thread above are untouched, shouldn't that fix the issue? If not, is there any possibility one can find bootloader images (if such thing exists) because modem images are available in another thread. One can pick and choose a combination to flash. I am just speculating. I have no idea if such a thing can be done.
Thank you so much. Really appreciate you sticking around to share the ideas.
P.S. - Is there any option where you can delete both bootloader and modem just before flashing the stock ROM via Odin or TWRP?

There is no need to deal with the EFS at this moment as long as the phone is showing the correct IMEI and MAC address.
Yes, those look like factory images and you should try the latest ROM which is PF1. It's possible that the phone was running a newer bootloader than the one found in the NL3 ROM. Some boot loaders cannot be downgraded.
You cannot delete the bootloader from the phone. Without a bootloader, the phone would function. It's similar to the BIOS of a PC.

It is not TWRP that's the problem - it's the size of your system / user partitions on the 9505g.
@side said he would have a fix in version 4 OptLos for this.
His solution is not something I will be implementing in Resurrection Remix however.

audit13 said:
There is no need to deal with the EFS at this moment as long as the phone is showing the correct IMEI and MAC address.
Yes, those look like factory images and you should try the latest ROM which is PF1. It's possible that the phone was running a newer bootloader than the one found in the NL3 ROM. Some boot loaders cannot be downgraded.
You cannot delete the bootloader from the phone. Without a bootloader, the phone would function. It's similar to the BIOS of a PC.
Click to expand...
Click to collapse
So I flashed PF1 stock ROM, both bootloaders and modems are PF1. Made sure over the full day yesterday, there is no update and the problem persists. Can't flash Oreo and no cell phone data. Now, my interest in Oreo has pretty much died and only hoping to find a tweak to fix cell phone data. Fixed APN, made a factory reset just to be sure that its not the issue, tried SIM card in the different phone and other SIM in my phone that its not the SIM or the network thats the cause. So far I have not managed to find out what made the phone lose cell phone data.
Buff99 said:
It is not TWRP that's the problem - it's the size of your system / user partitions on the 9505g.
@side said he would have a fix in version 4 OptLos for this.
His solution is not something I will be implementing in Resurrection Remix however.
Click to expand...
Click to collapse
Dang man, your comment came a little late after I managed to fcuk up my phone very well trying to install Oreo. It will be great if you folks can make this comment in OP of the respective ROMs so that next I9505G user won't mess it up royally the way I did. If I remember correctly, I read both the threads start to the end and I didn't find any comment on this issue of I9505G.
Thanks both of you for chiming in and trying to help. If there is any idea to fix the loss of cell phone data, that will be of great help.

No possible way of getting into download mode. Please help. LG V20 H918 T-Mobile

I was able to root my phone and use it for a while but then it started reboot for no reason. It is currently running Oreo, H91820h.
I tried to restore to different earlier back up but same issue and a whole bunch of apps complain and terminate itself. Tried to flash Lineage OS and same problem.
So I tried to use LGUP to restore it to stock image but cannot get the phone into download mode.
When I hold the volume down button and plug in the USB cable, I get the fastboot screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I hold the volume up button and plug in the USB cable, I get the "Download Mode" icon for about 2 second and then it switches to TWRP screen.
I remember when I first tried to install TWRP, it was version 3.2.1-3. Then I tried to flash twrp version 3.3.1-0 but for some reason, sometime it boots up with version 3.3.1-0 and sometime it boots up with version 3.2.1-3.
I cannot flash anything in fastboot or adb since it always come back with "FAILED (remote: 'unknown command')".
I have tried for over a week, read everything I could on the internet and tried everything but without success in getting into download mode to reload the stock image with LGUP.
Could anybody provide any suggestion or an alternate way of restoring the stock image without requiring going to download mode? May be re-flash with a different twrp version or remove twrp completely so it doesn't show up when I press volume up and plug in the USB cable.
Please, I am desperate. I can even send you the phone if you think you can fix it.
Thanks.

bqbase said:
I was able to root my phone and use it for a while but then it started reboot for no reason. It is currently running Oreo, H91820h.
I tried to restore to different earlier back up but same issue and a whole bunch of apps complain and terminate itself. Tried to flash Lineage OS and same problem.
So I tried to use LGUP to restore it to stock image but cannot get the phone into download mode.
When I hold the volume down button and plug in the USB cable, I get the fastboot screen.
When I hold the volume up button and plug in the USB cable, I get the "Download Mode" icon for about 2 second and then it switches to TWRP screen.
I remember when I first tried to install TWRP, it was version 3.2.1-3. Then I tried to flash twrp version 3.3.1-0 but for some reason, sometime it boots up with version 3.3.1-0 and sometime it boots up with version 3.2.1-3.
I cannot flash anything in fastboot or adb since it always come back with "FAILED (remote: 'unknown command')".
I have tried for over a week, read everything I could on the internet and tried everything but without success in getting into download mode to reload the stock image with LGUP.
Could anybody provide any suggestion or an alternate way of restoring the stock image without requiring going to download mode? May be re-flash with a different twrp version or remove twrp completely so it doesn't show up when I press volume up and plug in the USB cable.
Please, I am desperate. I can even send you the phone if you think you can fix it.
Thanks.
Click to expand...
Click to collapse
I'm not that familiar with the 918 ( I have 2 H910 )
But from the symptoms you described
I would guess that your MB is shot.
Even if you do manage to get into download mode you'll likely have errors flashing anything. I can look at the phone but it sounds like you need a replacement MB.
Sent from my Mi MIX 2S using Tapatalk

clsA said:
I'm not that familiar with the 918 ( I have 2 H910 )
But from the symptoms you described
I would guess that your MB is shot.
Even if you do manage to get into download mode you'll likely have errors flashing anything. I can look at the phone but it sounds like you need a replacement MB.
Sent from my Mi MIX 2S using Tapatalk
Click to expand...
Click to collapse
Not sure what you mean by "MB". I don't think it means "motherboard" so my best guess is "master boot".
Where can I get a replacement MB and how to replace it?

bqbase said:
Not sure what you mean by "MB". I don't think it means "motherboard" so my best guess is "master boot".
Where can I get a replacement MB and how to replace it?
Click to expand...
Click to collapse
Yes you need a motherboard
Or another phone
Sent from my Mi MIX 2S using Tapatalk

clsA said:
I'm not that familiar with the 918 ( I have 2 H910 )
But from the symptoms you described
I would guess that your MB is shot.
Even if you do manage to get into download mode you'll likely have errors flashing anything. I can look at the phone but it sounds like you need a replacement MB.
Sent from my Mi MIX 2S using Tapatalk
Click to expand...
Click to collapse
bqbase said:
Not sure what you mean by "MB". I don't think it means "motherboard" so my best guess is "master boot".
Where can I get a replacement MB and how to replace it?
Click to expand...
Click to collapse
Hold the phone here, the H918 can NEVER use fastboot to flash, thats why the lafsploit is used to replace download mode with a copy of twrp, leading many H918 users to have two different twrp installs.
To get download mode back flash this from the original lafsploit thread.
Rebooting for no reason is a bad sign (maybe see about replacing your battery if its the original one). Everything else (fastboot not working, download mode replaced by twrp)? Normal.

Phoenix591 said:
Hold the phone here, the H918 can NEVER use fastboot to flash, thats why the lafsploit is used to replace download mode with a copy of twrp, leading many H918 users to have two different twrp installs.
To get download mode back flash this from the original lafsploit thread.
Rebooting for no reason is a bad sign (maybe see about replacing your battery if its the original one). Everything else (fastboot not working, download mode replaced by twrp)? Normal.
Click to expand...
Click to collapse
OMG, OMG, OMG, I got my download mode back. I am so appreciate your help. I wish I can send you a beer.
I must have gone through this lafsploit thread a hundred times but never paid attention to this "OPTIONAL" note and I wasted sooo much time refusing to post a question on this forum thinking I can find the answer just buy combing through the internet.
I believe you are dead on with reboot issue too. I got more than a few times with the phone complaining that wrong battery was inserted and need to shutdown. But I thought my un-experienced flashing of all the junks I did on the phone are causing it.
"OPTIONAL
If you would like to restore download mode onto your laf partition AFTER you have installed TWRP onto recovery:
Boot to TWRP that is on recovery
Flash this zip: laf_restore.zip
This can be done at any time after you are rooted. About the only reason you would want to flash laf back is if you use LG Backup.
TWRP has the ability to backup your phone, so I am not sure why someone would want this (maybe you are more comfortable with it?).
Also, flashing back to 100% unrooted stock can be accomplished by flashing a zip in TWRP, you don't NEED to flash a KDZ, but again, maybe you are more comfortable doing it that way.
The bottom line is TWRP on both laf and recovery is FAR FAR more useful than flashing laf back. You can test new versions of TWRP while keeping your old known working version (for example)."

clsA said:
I'm not that familiar with the 918 ( I have 2 H910 )
But from the symptoms you described
I would guess that your MB is shot.
Even if you do manage to get into download mode you'll likely have errors flashing anything. I can look at the phone but it sounds like you need a replacement MB.
Sent from my Mi MIX 2S using Tapatalk
Click to expand...
Click to collapse
I just want to say thank you to clsA and Phoenix591 for the help. I found the answer and was able to successfully restore my phone to 100% stock. I know it's hard to pinpoint the issue while trying to understand all the craps that people post on their question. Hit or miss, right or wrong, work or not, I really appreciate all the effort that you did to help me figure out the solution.

bqbase said:
I just want to say thank you to clsA and Phoenix591 for the help. I found the answer and was able to successfully restore my phone to 100% stock. I know it's hard to pinpoint the issue while trying to understand all the craps that people post on their question. Hit or miss, right or wrong, work or not, I really appreciate all the effort that you did to help me figure out the solution.
Click to expand...
Click to collapse
Guess I missed it on this one
V20 does have a lot of motherboard issue over the years. Apps crashing and phone rebooting randomly are 2 of them.
Glad you got it sorted and back to stock
Sent from my Mi MIX 2S using Tapatalk

Phoenix591 said:
Hold the phone here, the H918 can NEVER use fastboot to flash, thats why the lafsploit is used to replace download mode with a copy of twrp, leading many H918 users to have two different twrp installs.
To get download mode back flash this from the original lafsploit thread.
Rebooting for no reason is a bad sign (maybe see about replacing your battery if its the original one). Everything else (fastboot not working, download mode replaced by twrp)? Normal.
Click to expand...
Click to collapse
Thank you very much, i can Relock and unroot my device with this, thank you so much

Phoenix591 said:
Hold the phone here, the H918 can NEVER use fastboot to flash, thats why the lafsploit is used to replace download mode with a copy of twrp, leading many H918 users to have two different twrp installs.
To get download mode back flash this from the original lafsploit thread.
Rebooting for no reason is a bad sign (maybe see about replacing your battery if its the original one). Everything else (fastboot not working, download mode replaced by twrp)? Normal.
Click to expand...
Click to collapse
Hi I've happened to run into the same mistake however the link is broken. If you still have the file I would really appreciate the help.
I'm usually very careful when it comes to flashing but I made the mistake of trusting someone to unlock my V20 for global use, vendor told me they didn't know if they could do it since it was rooted and their unlocking software detected the root. He needed to remove the root and charge me extra. I trusted him into removing the root and pushed back the agreed upon date like three times. He kept saying he could not remove twrp. Long story short he told me he wasn't able to do it and gave me a discount, he said he was able to unlock it but was not able to power it on as it was bootlooping. I assume it was because he locked the bootloader and once I unlocked it again when I try to go into download mode to restore into LGUP it boots me into twrp instantly. Thanks in advance