Lollipop clean flash blank lit screen on reboot. - G2 Q&A, Help & Troubleshooting

32GB D802 unbranded model (Hong Kong), same inside case on metal strip(D802/805) and plastic inner housing. Bought brand new with JB.
Used LG tool, CSE Flashed 'Hong Kong D80230B_00.kdz' (KitKat 4.4.2) No problems!
Tried Flashing Lollipop Firmware for 32GB D802 from other countries Spain, Germany, even China, but upon reboot after flashing the screen back-light is lit, but there's no picture or logo, stays like that for 20 mins.
Rebooting into Factory Reset I can see the screen again, but that's it.. So is it possible to flash other countries Firmware? There's no LTE option with Hong Kong.
Another thing, I've checked my IMEI thru the dialer and it's '0'. In Hardware mode a bunch of "0000000000000'
But I still have phone signal and no problems at all. Should I concern myself with that?

Are you really sure its a true d802, did you cechk motherboard.? check this thread
http://forum.xda-developers.com/lg-g2/general/warning-to-people-bought-phones-ebay-t2991195

I'm not game enough to dig that far into my phones hardware, but failing all else I could..
However...I have successfully used AutoRec (D802) to install recovery 3 times already, no problem and IOROOT to root it...
And...I didn't buy this from Ebay secondhand. I bought new from a shop.
After flashing another regions Lollipop Firmware(d802) and encountering the blank back-lit screen on reboot, it didn't brick my phone, I could still enter download mode and go into factory reset (which is where the screen actually worked) Actually tried the factory reset after the flash but it didn't help.
After not being able to see anything I just entered download mode and flashed KitKat back again, no problem. I can't see how others are just flashing any regions Lollipop ROMs on their phones and they're working.
Photo's attached showing under casing markings(not so good quality, I used my old Desire S)

twiice said:
I'm not game enough to dig that far into my phones hardware, but failing all else I could..
However...I have successfully used AutoRec (D802) to install recovery 3 times already, no problem and IOROOT to root it...
And...I didn't buy this from Ebay secondhand. I bought new from a shop.
After flashing another regions Lollipop Firmware(d802) and encountering the blank back-lit screen on reboot, it didn't brick my phone, I could still enter download mode and go into factory reset (which is where the screen actually worked) Actually tried the factory reset after the flash but it didn't help.
After not being able to see anything I just entered download mode and flashed KitKat back again, no problem. I can't see how others are just flashing any regions Lollipop ROMs on their phones and they're working.
Photo's attached showing under casing markings(not so good quality, I used my old Desire S)
Click to expand...
Click to collapse
then i guess if it flashed with no problems then it might be a d802, not sure about the imei though.
i cant really help here, i ive never been into jb,kk on my g2. but it shouldnt be aproblem flashing different region i dont think it matters right as long as its your variant.

I'll try flashing a Hong Kong based Lollipop ROM and see what happens.
Thanks for your input!

twiice said:
I'll try flashing a Hong Kong based Lollipop ROM and see what happens.
Thanks for your input!
Click to expand...
Click to collapse
youre welcomed and good luck. reprot back.

The Hong Kong Firmware worked, no problem at all. It has 4G enabled too which is excellent.

Related

device not working after upgrade

Hello,
Yesterday I got a brand new D802, I can't tell you what kernel it is or baseband because my device isn't working properly.
the problems began after I did an upgrade from D80210B to D80210D using the LG PC Suite.
after the upgrade was done, the touch screen got very erratic and I every place I've touched wasn't the right place (it acted like it wasn't calibrated)
I've tried to flash the stock ROM again using LG Flash Tool 2014 and using both Hong Kong 32GB D80210D_00.kdz and Hong Kong 32GB D80210B_00.kdz files but it didn't do any good.
I can't enter recovery mode, I get only the Factory reset screen (which I did twice and no good either).
one more thing I've noticed is that the device doesn't recognize any SIM card I out in it, at first it recognized my SIM (I have a giffgaff SIM) and after the upgrade the boot screen suddenly showed me the Vodafone logo.
I ever tried to put a Vodafone SIM in it, but the results were the same. If I'm not doing anything, the device boot itself into a loop, I can see the first screen of the initialization but that's it.
I've managed to get it to work one time but I couldn't even operate it on a basic level and the touch was erratic.
many thanks for any help that I would get.
Ice_machinE said:
Hello,
Yesterday I got a brand new D802, I can't tell you what kernel it is or baseband because my device isn't working properly.
the problems began after I did an upgrade from D80210B to D80210D using the LG PC Suite.
after the upgrade was done, the touch screen got very erratic and I every place I've touched wasn't the right place (it acted like it wasn't calibrated)
I've tried to flash the stock ROM again using LG Flash Tool 2014 and using both Hong Kong 32GB D80210D_00.kdz and Hong Kong 32GB D80210B_00.kdz files but it didn't do any good.
I can't enter recovery mode, I get only the Factory reset screen (which I did twice and no good either).
one more thing I've noticed is that the device doesn't recognize any SIM card I out in it, at first it recognized my SIM (I have a giffgaff SIM) and after the upgrade the boot screen suddenly showed me the Vodafone logo.
I ever tried to put a Vodafone SIM in it, but the results were the same. If I'm not doing anything, the device boot itself into a loop, I can see the first screen of the initialization but that's it.
I've managed to get it to work one time but I couldn't even operate it on a basic level and the touch was erratic.
many thanks for any help that I would get.
Click to expand...
Click to collapse
Since the device is brand new as you implied, send it back for warranty. That would be the best thing to do, because chances are that even if you fix it after spending several hours on it, another issue might occur.
BTW factory reset screen is recovery mode. If you insist on keeping the device, let us know which kind of issues you are facing when trying to flash a .kdz.
vPro97 said:
Since the device is brand new as you implied, send it back for warranty. That would be the best thing to do, because chances are that even if you fix it after spending several hours on it, another issue might occur.
BTW factory reset screen is recovery mode. If you insist on keeping the device, let us know which kind of issues you are facing when trying to flash a .kdz.
Click to expand...
Click to collapse
Thanks for the reply, although it's brand new, it was bought on eBay so no can do about activating warranty and stuff.
Anyway, I tried a few more times fixing it, but gave up and put it in a lab.
I'll update next week, after it will return, what was the damage.
once again, thanks
Ice_machinE said:
Thanks for the reply, although it's brand new, it was bought on eBay so no can do about activating warranty and stuff.
Anyway, I tried a few more times fixing it, but gave up and put it in a lab.
I'll update next week, after it will return, what was the damage.
once again, thanks
Click to expand...
Click to collapse
The same like here
http://forum.xda-developers.com/lg-g2/help/strange-touch-behaviour-stock-rom-flash-t2922009
7547
rimaSamir said:
The same like here
http://forum.xda-developers.com/lg-g2/help/strange-touch-behaviour-stock-rom-flash-t2922009
Click to expand...
Click to collapse
I got the phone back from the lab and the technician told me that a screen digitizer is needed to be replaced.
Naturally, I told hime not to do that and I will send the phone back to HK to get a replacement phone.
Many thanks for everyone who tried to help me.
Ice

[Q] flashing Stock UK BTU though on boot polish language shown

Ages ago because i was impatientto update my phone so i flashed the Polish Stock using Odin, since then i have used Odin to flash the UK Stock, though when i wipe and reset the phone it still initially comes up with the polish language, (not a massive issue i know but i want to get UK OTA if it ever comes) also if i go to sell the phone at the end of this year when the Note5 is out im sure the new owner would want to turn it on and see english.
Ive tried
Clearing the EFS cache and resetting the phone from recovery before and after flashing BTU
I made sure reactivation lock was off as I wondered if that would cause an issue though that hasn't helped. does anyone have any other ideas?
Im un-routed as i sometimes use my phone to test out corporate BYOD so cant root of flash a custom rom.
thanks all for any help.
ooMoo said:
Ages ago because i was impatientto update my phone so i flashed the Polish Stock using Odin, since then i have used Odin to flash the UK Stock, though when i wipe and reset the phone it still initially comes up with the polish language, (not a massive issue i know but i want to get UK OTA if it ever comes) also if i go to sell the phone at the end of this year when the Note5 is out im sure the new owner would want to turn it on and see english.
Ive tried
Clearing the EFS cache and resetting the phone from recovery before and after flashing BTU
I made sure reactivation lock was off as I wondered if that would cause an issue though that hasn't helped. does anyone have any other ideas?
Im un-routed as i sometimes use my phone to test out corporate BYOD so cant root of flash a custom rom.
thanks all for any help.
Click to expand...
Click to collapse
Download Phone INFO Samsung from Play and check the CSC.
But it might be you are rebooting into DL mode instead of shutting down the phone then starting it in DL mode. I usually remove the battery for a bit and hold the power button for a few secs to make sure the mainboard is completely discharged. Odin (& other methods) all have problems changing BL and Modem if you just do a reboot into DL.
You might want to take a look at Multiboot and Recovery for the possibility of having the ROM you want, rooted etc. AND still have a stock ROM you can choose to boot into for work purposes.

LG G2 display problem after going back to stock

a few feeks ago bought a second hand lg g2 d802 running kitkat 4.4.2 wich was only detecting 2g when i try to connect to the internet, i tried to solve this problem by entering the hidden menu and selecting the network types it could detect but no luck, so i decided to upgrade to lollipop, i downloaded the lg support tool and went for it, when the update was done i found myself with an almost completly functioning device except it had the "imei=null" problem, meaning no network at all --"
i tried the QPST but it was unable to detect my phone, so i decided to root my phone and go for a custom rom, the cyanogenmod13 nightly (i don't really know what i was thinking at that point :s ) and when done i was stuck in a bootloop, so i tried flashing a stock rom kdz method but the lg flash tool would stop automatically. since then i've been trying to flash stock TOT roms, the process would stop at 94% and the phone reboots. the screen shows random pixels and lines, the start up lg tune is there and i feel vibration when i press the home buttons location, i've tried to reset it to factory settings and i've used theLGUP_8974.dll, selecting the BOARD DL option in the lg flash tool but that didn't solve the problem. i have read somwhere that it could be a kernal problem, i don't know if i should go that way ( am at that point where i don't want to mess up my device anymore xD ) what do you guys think?
thank you for your help
restlessone said:
a few feeks ago bought a second hand lg g2 d802 running kitkat 4.4.2 wich was only detecting 2g when i try to connect to the internet, i tried to solve this problem by entering the hidden menu and selecting the network types it could detect but no luck, so i decided to upgrade to lollipop, i downloaded the lg support tool and went for it, when the update was done i found myself with an almost completly functioning device except it had the "imei=null" problem, meaning no network at all --"
i tried the QPST but it was unable to detect my phone, so i decided to root my phone and go for a custom rom, the cyanogenmod13 nightly (i don't really know what i was thinking at that point :s ) and when done i was stuck in a bootloop, so i tried flashing a stock rom kdz method but the lg flash tool would stop automatically. since then i've been trying to flash stock TOT roms, the process would stop at 94% and the phone reboots. the screen shows random pixels and lines, the start up lg tune is there and i feel vibration when i press the home buttons location, i've tried to reset it to factory settings and i've used theLGUP_8974.dll, selecting the BOARD DL option in the lg flash tool but that didn't solve the problem. i have read somwhere that it could be a kernal problem, i don't know if i should go that way ( am at that point where i don't want to mess up my device anymore xD ) what do you guys think?
thank you for your help
Click to expand...
Click to collapse
Sounds like to me you may not have a D802. You'll need to take the back cover off, and look and see what model #s you see. As if your having screen issues that sounds like your flashing a D802 firmware on a D800 or D801.
Also remember flashing will almost always stop before 99%.. Anything after 85% its done this is normal and will almost always happen.
These D802's have a LONG history (mostly bought referbs) of not being what they are being sold as.
hyelton said:
Sounds like to me you may not have a D802. You'll need to take the back cover off, and look and see what model #s you see. As if your having screen issues that sounds like your flashing a D802 firmware on a D800 or D801.
Also remember flashing will almost always stop before 99%.. Anything after 85% its done this is normal and will almost always happen.
These D802's have a LONG history (mostly bought referbs) of not being what they are being sold as.
Click to expand...
Click to collapse
the problem has been solved, it tuned out to be an ls980, now my G2 is fully back to life :laugh: thanx alot hyelton for your help :good:

Galaxy A500FU - the phone doesnt turn on

Hello, im new to this forum
Ive bought a Samsung Galaxy A5 back in September 2015 to my girlfriend.
At the time i opened the case to see if it was everything ok with it before giving it to her. unfortunately i installed oficial updates in the phone after connecting the device to the internet.
Wanting to give the phone just like ive bought it, i started to making all things wrong. i tried to reset the phone back to the factory reset (using the volume up + home + power buttons) but after that the version that was still installed was the updated one and not the factory one.
Then i tried to download the factory version from here htt p://updato.com/firmware-archive-select-model?r=&v=&q=Galaxy+A5+205 using odin and this guide htt p://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
it was installed but when the phone restarted it never turned back on again. despite being the correct version for my region i believe i installed a variant version and not the factory reset version.
I tried turning the phone on, using recovery mode and download mode keys but the phone never gave any signal again. plugin in the usb in the pc didnt work either.
I ended up buying the same phone since i wasnt able to solve the problem and her anniversary was close and ended up with an extra but damaged phone.
i never tried to get the phone to the warranty because i knew that i was losing the it the moment i tried to use odin.
is there anything else i can try to solve the phones problem? or is this problem unrecoverable?
thanks in advance
I can't tell you if your phone is unrecoverable but I think you had flashed other variant's rom causing your mobile not turning on. I don't see any a500fu on the website you posted. If possible, could you tell me which variant you had flashed. I had ever experienced a hard-brick when my device was accidentally removed while odin was flashing aboot.mbn. The solution was changing the motherboard which didn't cost much. I would recommend you to flash firmware from sammobile and do NOT use 4.4.4 firmware as few friends on this forum had experienced hard-bricks. If you want, try a usb jig.
Try warranty, you can have the chance of getting it repaired.
akil777 said:
I can't tell you if your phone is unrecoverable but I think you had flashed other variant's rom causing your mobile not turning on. I don't see any a500fu on the website you posted. If possible, could you tell me which variant you had flashed. I had ever experienced a hard-brick when my device was accidentally removed while odin was flashing aboot.mbn. The solution was changing the motherboard which didn't cost much. I would recommend you to flash firmware from ="htt p://www .sammobile.com/"]sammobile and do NOT use 4.4.4 firmware as few friends on this forum had experienced hard-bricks. If you want, try a usb jig.
Try warranty, you can have the chance of getting it repaired.
Click to expand...
Click to collapse
It must have been other variant rom.
http s://gyazo. com/7ac9dfe107976eeb802cae50a23b23a1 - here is a screenshot
Samsung Galaxy-A500FU - to get there you need to go to "updato" site (first link), place on the search "Galaxy A5" and select Portugal as "region"
There are 7 options, 6 are for locked phones to the main Portuguese operators and one for unlocked phones (i assume), because it says "Porgugal TPH" - TPH means the phone house witch is a store that sells phones and other electronic equipment.
Despite the phone not being bought at the phone house i assumed it was this rom since there was no other one and the phone is not locked to a particular operator.
Ive checked the site you provided and it as almost the same romĀ“s as updato and the only one that is not locked to a particular operator is TPH one.
So my only option is to use a usb jig to force the phone into download mode? will that work with or without a motherboad change?
please have in mind that the phone does not respond to any other button or combination of buttons comand and trying to charge the phones battery only produces heat at the phone and charger, nothing else happens.

Galaxy S5 (G900I) Occasional Bootloop

Got a slight problem here.
First of all how do I find out the original network / carrier the phone was on?
I stupidly went and flashed the XSA (Australia) firmware without making note of the original carrier. Is there a way I can find out?
Secondly every time I boot the phone up it does a boot loop at least 4 times before it gets into the system.
Any ideas on this?
Thanks
G900i
My device came with Telstra firmware. I have flashed XSA, Optus, Vodafone, Spark NZ and India.
No problems.
Did you use Odin to flash your firmware?
What country are you in?
Hi
Yes I am in Australia and yep I used Odin.
It seems that even flashing TWRP the same issue I encounter but the strange thing is, although it shows up 'Recovery booting' and shows the Samsung Galaxy S5 splash logo I can still press buttons on the phone and I know this because it vibrates. Its almost like TWRP is there and is open in the background but its just not displaying at all. I have honestly tried so much.
I have downloaded (Using Sam Firm) the latest XSA and even found the PIT file to re partition but that made no difference.
The phone has had a total of around 7 LCD screens installed which came from various sellers in China. Due to the constant connection and disconnections of them I would say it may well be responsible for this issue as it has caused no doubt some considerable amount of stress to the motherboard. Maybe I am wrong I am just not sure.
It is a bizarre issue. I have never come across it before.
Standard stock recovery is also behaving the same way... I am getting, in blue, on the top of the screen 'Recovery Booting' then thats it... just that... waiting for ages and nothing happens but I am pretty sure that it is actually open behind the message which says 'Recovery Booting'
The whole things a bit of a mess.... When starting up the OS normally it takes around 5 bootloops for it to actually load up lol
Wow!! That's just crazy. Sounds like your device might have seen better days.
Occasionally I think its good to take the phone back to kitkat then to MM before twrp and custom roms.
I currently run klte version of /e/ pie ROM on my device which works very good. Un-Googled so my tired battery lasts better.
Best of luck with your problem.
Happy New Year mate.

Categories

Resources