Hello Everyone I have a problem with my LG G3 which I have bought it recently was working nice but it had KitKat so I wanted to upgrade to lollipop but didn't know that LG G3 had different variant.
I've downloaded a wrong flash (LS990 sprint) and flashed it. so I lost the network and I noticed that the imei has changed. and I don't have the original IMEI of the phone ( the sticker on the back of phone is for D855 16GB not for D855 32GB).so I think its not the original IMEI.
After bricking the phone I've opened it and noticed that it was D855 written on the motherboard.
when trying to flash the original D855 rom it doesn't work (flashed it using the crossDLL method and using the Hex Method By changing D855 to LS990 to make the flash tool think Its LS990) the flash pass on both methods but i'm stuck on LG logo.
send it to some repairing services here in my country but they didn't fix it they thought its sprint so they flashed PrimeGSM but still no network.
I think I should change the IMEI before flashing D855 or something.
please Help me I've looked all over the NET but find no solution to this problem.
If you need more informations ask me. Help me as soon as possible this is the only phone that I have.
Did you ever figure out how to fix this? I have a ls990 which was flashed with PrimeGSM and is now detected as a d855... I have been trying to get this working for the last two days with no luck
Reply
Hello
What is the problem that you are facing ?
Is it a network problem or what ?
Primegsm is ported from d855 so i think it will show D855 on any lg g3 that does'nt mean that your phone detected as d855.
Make sure your phone is ls990 or another variant
And which country and carrier ? So i can help you.
I basically have a soft bricked phone - no OS as all. I am in New Zealand running on the Vodafone network.
I was using PrimeGSM and it was working fine but decided to go back to the stock ZV8, when running through LG Flash Tool I noticed Download mode was showing the model as a D855 and would not accept the LS990 DLL - I then made the mistake of using the generic DLL with a D855 image which started a boot loop - then made more mistakes and ended up with no OS and stuck at the LG logo.
At this stage I am able to get to fastboot and use fastboot boot to get into TWRP but cannot do much from there, I also have to use the D855 TWRP image as the LS990 fails with a device tree issue. fastboot will not erase any partitions or flash any images manually. Using terminal in TWRP I am able to browse the partition though but cannot mount the SD card or use adb to push or pull (fails with error closed)
I stuffed up quite a few times along the way but sure I can recover from it since I still have quite a bit of access to the device...
I managed to get my phone going again by following a guide I found in the forum, I am pretty sure it would solve the ops issue as well.
Really quick and easy, I just bridged the points with a needle and copper cable.
Multiple threads little to no replies besides sensless info that ive already tried
CAN TOT METHOD WORK ON TMOBILES VARIANT G4 AND IF SO WHERES THE LINK FOR THE TOT FILE NOT KDZ!
Tmobile g4 forum is helpless after days and 100s views
this is my last hope. I Have a tmobile lg g4 model. I hapened to relock the bootloader while i was still on a rom and rooted with twrp, but i do have download mode and only download mode .I dont have a bootable o.s
Ive tried and tried and tried to get lg UP Tool which is a joke its not really a true unbrick tool cause if you bricked yourself on a rom and not the stock firmware its useless .All you get is device model unknown. This is supposedly cause custom roms are edited. Lg bridge does not work as a brick tool either it just states wether your firmware is up to date . The only hope was lg flash tool 2014 but that im told and seems to be outdated not compatible with any g4 on android 6.0.... Im at a loss here i can get into dload mode thats it the phone charges in download mode also and it also is recognized by pc meaning drivers are installed because lg mobile support tool sees my device and says its up to date.
s
Some members have been in my same scenario relocked bootloader with a rom and twrp with nothing but download mode and swear they fixed it with lg bridge tool using the update recovery error link within the tool.
Can anyone confirm if im screwed or if i am doing something wrong this is day 5 now im ready to toss the g4 in the trash for the sake of my sanity.
Closed at OP's request
Heloo everone i am from INDIA
recently i purchased and refurbished lg lg3 within setting i could se it was D855 but on body it was D850
so i thoguhts its D855 because software it was running was D855 but then i flashed D855 firmware to update it and it is soft bricked i direct goes to download mode and nothing works
I took it to a shop he tried sevelar firmware at once i got it boot up but no camera wifi no modem, so it was not the correct one,
So is thier a way i can get it working?
How could i figure it is sprint at&t or verzion??? because it was an cdma set,
Cm13 or stock rom anything could work for me
Anyone please give me a procedure will b thankful to U.... :crying:
I you are able to access download mode, try and flash the latest marshmallow KDZ for D855. My device also has D850 on the back but it has the D855 software.
youssefkr said:
I you are able to access download mode, try and flash the latest marshmallow KDZ for D855. My device also has D850 on the back but it has the D855 software.
Click to expand...
Click to collapse
an you give me the link u have flashed on your device n tool n procedure you sued to flash it??
will b thank full 2 u
happy3777 said:
an you give me the link u have flashed on your device n tool n procedure you sued to flash it??
will b thank full 2 u
Click to expand...
Click to collapse
First open up your phone,exact model will be on the board.then flash accordingly software.
Jahanzaibawan said:
First open up your phone,exact model will be on the board.then flash accordingly software.
Click to expand...
Click to collapse
I know already tried But it was D855 already tried n that caused soft bricking....
Dear XDA community
I recently bought a LG G4 from an online retailer. According to their website they said it was a UK model, which according to the back of the phone beneath the battery it is: LGH815. But then after booting the phone the ROM being used was: LGH815T. Then I typed in the IMEI number and found out it was a: Verizon US model??
Basically I am having trouble identifying my model. The phone apparently came unlocked and rooted, but the person who sent it must have done something wrong because when I flashed a TWRP recovery image to the phone it comes up saying: secure boot error code: 1002.
The good thing is, is that I can boot into the device and still operate it as per usual. But what I want to do is bring the recovery back to normal. I was searching around and apparently there are some KDZ files that can be used just to flash the recovery? Is this correct? If so could you assist me in what I have to do to fix my issue which is: secure boot error 1002.
I would really appreciate any help regarding the matter. :crying:
Tried posting photos, but forum would not let me, all they showed was the model numbers.
Jesse
Higsley said:
Dear XDA community
I recently bought a LG G4 from an online retailer. According to their website they said it was a UK model, which according to the back of the phone beneath the battery it is: LGH815. But then after booting the phone the ROM being used was: LGH815T. Then I typed in the IMEI number and found out it was a: Verizon US model??
Basically I am having trouble identifying my model. The phone apparently came unlocked and rooted, but the person who sent it must have done something wrong because when I flashed a TWRP recovery image to the phone it comes up saying: secure boot error code: 1002.
The good thing is, is that I can boot into the device and still operate it as per usual. But what I want to do is bring the recovery back to normal. I was searching around and apparently there are some KDZ files that can be used just to flash the recovery? Is this correct? If so could you assist me in what I have to do to fix my issue which is: secure boot error 1002.
I would really appreciate any help regarding the matter. :crying:
Tried posting photos, but forum would not let me, all they showed was the model numbers.
Jesse
Click to expand...
Click to collapse
On the play store there is this https://play.google.com/store/apps/details?id=com.peamoon.phoneproductioninfo
This may help you I'd the device it it is a h815t you may not have the ability to unlock the boot loader......
Also try this *#546386#815#*.
This may also help.......
https://forum.xda-developers.com/tmobile-g4/help/twrp-installation-secure-boot-error-1003-t3168385
Use LGUP-NEW to install/flash ...
Higsley said:
Dear XDA community
I recently bought a LG G4 from an online retailer. According to their website they said it was a UK model, which according to the back of the phone beneath the battery it is: LGH815. But then after booting the phone the ROM being used was: LGH815T. Then I typed in the IMEI number and found out it was a: Verizon US model??
Basically I am having trouble identifying my model. The phone apparently came unlocked and rooted, but the person who sent it must have done something wrong because when I flashed a TWRP recovery image to the phone it comes up saying: secure boot error code: 1002.
The good thing is, is that I can boot into the device and still operate it as per usual. But what I want to do is bring the recovery back to normal. I was searching around and apparently there are some KDZ files that can be used just to flash the recovery? Is this correct? If so could you assist me in what I have to do to fix my issue which is: secure boot error 1002.
I would really appreciate any help regarding the matter. :crying:
Tried posting photos, but forum would not let me, all they showed was the model numbers.
Jesse
Click to expand...
Click to collapse
Use LGUP-NEW ( https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803 ) to install/flash ... the appropriate stock KDZ for your specific model once you ascertain it (LGUP - NEW may recognize your model and you can use that info to find the right KDZ). You will have to re-root the phone if you still wish to have root.
If you do root, suggest you might want to check out steadfasterX's [LOCKED][G4][TWRP][UNOFFICIAL] TWRP-in-FIsH for all locked G4 devices at: https://forum.xda-developers.com/g4/development/locked-twrpinfish-locked-g4-devices-t3573048
It has been tested on locked devices AND unlocked devices. Version 3 Beta 4 and 5 seem very stable and the links are available in the later posts on the site. It works like a charm and has been tested on a quite a number of devices now.
Addendum: I'm wondering if the online retailer may have meant it was carrier unlocked (i.e., so you could use other service provider's sim cards), not bootloader unlocked? That could account for the secure boot error getting TWRP to load.
S.
NB: Don't forget to click the Thanks button when members try to answer your questions and/or solve issues you have encountered.
So I was on Oreo and accidentally flashed back to 7.1.
Didn't brick it but now it doesn't recognize my sim even after flashing back to Oreo.
I tried to fastboot the tmo baseband but no luck there.
Anyone run across this or have any suggestions?
That was one of the 1st thing I ran across in the Oreo update thread. With development just really getting fired up I'll be surprised if you find a fix. If. I was you I would flash the mod that hides the unlocked bootloader warning and take it to TMobile. It's only a 5 dollor charge for defective devices. I've returned a total brick before.
So I am on the same board. The problem is I'm in UK and I cant claim warranty repair. Also my warranty was void in December soon when I generated bootloader unlock key.
SO what have I tried so far?
Hard brick bootloader to state when it is Qualcomm loader- only blank flash and Oreo Flash All is able to bring it back to live.
Ive also tried boot from B slot in twrp but it looks like my B partition is messed up. Fastboot will show red warning about no flashable A/B slot and only oreo flash can get it back to boot because it will oem lock itself.
When I get back fully on unlocked bootloader to 7.1.1 I cant update via adb sideload or update menu in settings. Both will fail.
Sim looks like it is detected on start but when taken out and slided back in it wont show up.
I have QCN area backed up with nv data but it wont help me.
Please note when boot is bricked oreo flash all will flash it on locked bootloader and will not show warning screen at all about botloader. However I was unable to boot to recovery from that point so I had to unlock it and flash 7.1.1 then oreo again.
So if someone could do nandroid backup of clear not set up rom it would be great. I can try restore it. I dont even know if twrp is able to do backup on A/B device.
Also if someone could read NV data from phone and share it ( from phone with working radio of course) would be really appreciated.
Can someone PM me NV backup? I need urgently qcn file. I think my hw partition is messed up. Please don't share it in this post as it can contain IMEI.
this is what i did, and why there is a giant post in caps in the thread that says not to do this. You essentially end up with a bootloader mismatch which hoses the radio. the only solution is a replacement.
and DONT DOWNGRADE !!!
byt3b0mb said:
this is what i did, and why there is a giant post in caps in the thread that says not to do this. You essentially end up with a bootloader mismatch which hoses the radio. the only solution is a replacement.
and DONT DOWNGRADE !!!
Click to expand...
Click to collapse
Sorry but warning isn't clear. I did not enjoy Oreo and was looking for unlock method.
Also bootloader match to my current Oreo rom and radio but still no sim detected so I think it is hw partition messed up. When I flash retail Oreo on it bootloader just change itself to retail Oreo version. Still no sim.
Device is useable as paperweight with WiFi
I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0
Everything about the phone works 100% except the Sim slot. It's like it can't read the Sim. It knows there is a sim in, but it can't access it.
On Oreo oem retail version.
donjuro said:
I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0
Click to expand...
Click to collapse
I'm happy to stay on 8 but need my sim get back to life. All works fine except SIM card is not detected.
My phone boot as normal. When downgraded it won't accept ota's. It won't install it via sideload too. SIM card remain undetected no matter what rom and what version( T-Mobile, retail, etc) when I try to boot from slot B via twrp it won't boot. It will show bootloader screen with unbootable a/B partition.
robdevil said:
I'm happy to stay on 8 but need my sim get back to life. All works fine except SIM card is not detected.
My phone boot as normal. When downgraded it won't accept ota's. It won't install it via sideload too. SIM card remain undetected no matter what rom and what version( T-Mobile, retail, etc) when I try to boot from slot B via twrp it won't boot. It will show bootloader screen with unbootable a/B partition.
Click to expand...
Click to collapse
i got a script that was able to get my tmobile variant back up and running on any version i installed please give this a try and let me know.
just copy all this to the platform tools drectory ans double click the oem flash.bat the oem lock.bat will re-lock your boot-loader if you want that as well.
pm me for a link to my drive since im still under 10 posts
Kaesberg said:
i got a script that was able to get my tmobile variant back up and running on any version i installed please give this a try and let me know.
just copy all this to the platform tools drectory ans double click the oem flash.bat the oem lock.bat will re-lock your boot-loader if you want that as well.
pm me for a link to my drive since im still under 10 posts
Click to expand...
Click to collapse
pm sent. i could use this
Please let us know if it works
Not OP, or guy with a link, but I did a similar bad thing and ended up on the retail Oreo without working SIM. What I did was take the modem file (the one that you fastboot flash to modem) from the tmo oreo zip and replaced the modem file in the retail oreo zip with the tmo one -- just change the name of the tmo modem file to the one that comes in the retail oreo zip and then run the retail flashall.
Still no way to get the latest tmo update that fixes some volte issues, though. Since I purchased within 14 days, I just added insurance and will probably end up drowning the phone to replace it... unless someone has a better idea. :/
breakerfall said:
Not OP, or guy with a link, but I did a similar bad thing and ended up on the retail Oreo without working SIM. What I did was take the modem file (the one that you fastboot flash to modem) from the tmo oreo zip and replaced the modem file in the retail oreo zip with the tmo one -- just change the name of the tmo modem file to the one that comes in the retail oreo zip and then run the retail flashall.
Still no way to get the latest tmo update that fixes some volte issues, though. Since I purchased within 14 days, I just added insurance and will probably end up drowning the phone to replace it... unless someone has a better idea. :/
Click to expand...
Click to collapse
Where did you get this modem?
mattlowry said:
Where did you get this modem?
Click to expand...
Click to collapse
from the tmo oreo zip here (bottom of the OP):
https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932
it's the NON-HLOS file
this is the retail oreo:
https://forum.xda-developers.com/showpost.php?p=75250794&postcount=82
I swapped the NONHLOS file from the tmo oreo into the retail oreo and I currently have working tmo service/SIM on the retail (tmo-less) oreo
donjuro said:
I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0
Click to expand...
Click to collapse
My Moto Z Play is bricked, after downgrade of oreo to nougat, my imei not work. so i decided go to oreo again, when i reboot my phone bricked. help me please!!!
Try this. Updated my Sprint only thread to be a little more universal.
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
bricked moto z2 force tmobile
donjuro said:
I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0
Click to expand...
Click to collapse
guys i tried blank flash oreo on mine bricked tmobile moto z2 force and it isnt working, any help would be great on this , thanks.. and also i have tried many blank flashes some for even other moto phone models none worked so far.. one or two of them got really close the oreo one did but failed at last part... tried about hundred times and yes i even tried holding down power and volume button with no success it didnt work it did though recognize the phone but still failed trying to boot or flash it though... seems to me it needs either up to date or just different blank flash it seems, but i dont know that for sure...