Database Users

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

Help! Help! Help! Please!

Bought a OTG from China, used one, left plugged into the phone as I slept...don't know if it's the cause of my troubles to start happening, or if the Twitter app I installed at the same time is the cause.
The phone became TROUBLE and I eventually decided to try going back to stock. I did manage to get stock on but couldn't use because the phone immediately would display the dreaded "Unfortunately.......", which pops up so often that you cannot do anything. So I decided to do a full wipe from factory recovery. Since then, the phone wont power on at all! I have left it to charge overnight, all day, NO POWER!!!! I have read many similar accounts. I lost as what to do! I had ZERO power issuses before. Saw a vid where a guy says the power switch is faulty. He ordered one from eBay and replaced it. 1) I don't think it's the case. 2) don't think I wanna try soldering, etc.
Any help would be appreciated!!!

I have the 910W8 from Rogers in Canada. ODIN flashed with no problems (used the latest firmware from sammobiles for my phone) but would get that error after the flash, causing it to be unuseable. I flashed a second time and same thing. That's when I decided to do a wipe from recovery. Now it won't boot up.

Wow! NOBODY?!
kojam said:
I have the 910W8 from Rogers in Canada. ODIN flashed with no problems (used the latest firmware from sammobiles for my phone) but would get that error after the flash, causing it to be unuseable. I flashed a second time and same thing. That's when I decided to do a wipe from recovery. Now it won't boot up.
Click to expand...
Click to collapse
Cannot believe nobody has replied. I did get one of the usb things from a very nice member (i have to register myself as someone who now has one) but the phone is still not working.
Having done some confusing reading to try to fix mine but don't think i can.
Wondering if there's a good, reliable, store in the GTA (north end preferrably) that can do repair with JTAG? Wondering if there's any hope in recovering this phone. I get the impression that there's a good chance JTAG repair can bring it back to life.

Sigh.. Bootloop problem out of nowhere

My Nexus 6p was definitely one of the batches that should not have passed QC... soft power button, phone shutting down with plenty of battery left and today all of a sudden, while I was using the phone, phone restarts and get stuck in a bootloop...
Phone is not rooted and the bootloader locked... its out of warranty but I called google support anyway and they directed me to Huawei .. luckily, they will fix it for free..
IF you are having the same problem, call google up and hold them accountable for this bull****

Same deal here but i bought my 6p from best buy along with geek squad protection plan. Rather than send me another 64gb 6p, they've given me a gift card for the price at the time of purchase. At the moment only 32gb versions are available on best buy dot com. I'm not totally opposed to the 32gb version but I'm not excited about it. It took 3 days from the time I submitted my RMA request to get an email telling me this gift card b.s.
I haven't returned anything yet. Not sure what to do. I really liked that phone.

i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps.
phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)

puddi said:
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps. phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
Click to expand...
Click to collapse
I wouldn't be. Sounds like you are unlocked and rooted. Just keep a good backup on your PC (including EFS) and enjoy your phone.

puddi said:
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps.
phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
Click to expand...
Click to collapse
Rooted or not and having a backup or not won't fix this unfixable bootloop. I have one in my possession I'm trying to restore and nothings working. Random reboots a week prior to it going into this bootloop. I've done a bunch of research and it's not good.

thesparky007 said:
My Nexus 6p was definitely one of the batches that should not have passed QC... soft power button, phone shutting down with plenty of battery left and today all of a sudden, while I was using the phone, phone restarts and get stuck in a bootloop...
Phone is not rooted and the bootloader locked... its out of warranty but I called google support anyway and they directed me to Huawei .. luckily, they will fix it for free..
IF you are having the same problem, call google up and hold them accountable for this bull****
Click to expand...
Click to collapse
Do you have the Huawei contact info? I have tried to go through the online support but I have yet to hear anything in a number of days. Same problem here, bootloop out of no where.

galakanokis said:
Do you have the Huawei contact info? I have tried to go through the online support but I have yet to hear anything in a number of days. Same problem here, bootloop out of no where.
Click to expand...
Click to collapse
Call them here 1-888-5HUAWEI

thesparky007 said:
Call them here 1-888-5HUAWEI
Click to expand...
Click to collapse
Thanks, much appreciated.

I just went through the same thing. Waiting on the RMA box to arrive so it can be sent back.
Sent from my Nexus 6 using XDA-Developers Legacy app

Same here...happened just this morning. I can't get into recovery and I can ONLY boot into bootloader. I am on full stock with a locked bootloader running 7.1.1. I got off the phone with a Huawei rep and she stated it could be due to a Google update and that they will try and downgrade it on their end. Strange cause I was already running the latest 7.1.1 (unless a new update was released his morning).
Here's what I tried to no avail:
-unlocked bootloader and tried to flash stock rom/recovery
-tried flashing custom recovery (twrp)
-tried booting into temp customer recovery (twrp)
-tried flashing 7.0 stock
I have re-locked the bootloader and will have to send it in. What a real bummer, I have managed to get out of a softbrick (unless this device is truly bricked ???) on many, many device since the T-Mobile G1, but I am at wits end with this device.

Going through the RMA process now, thanks again for the number.
I have heard it mentioned that flashing back to 6.0.1 might work, has anyone tried? I did flash all the way back to 7.0 with no luck.

tried flashing back to 6, 6.01 and 7.0 but it still persists. get it exchanged or repaired

It's now several phones a day... At what point does either Huawei or Google fess up to root cause? The one question I have is are all of these hard bricks on phones running nougat??
Sent from my Nexus 6 using XDA-Developers Legacy app

uzi132 said:
Same here...happened just this morning. I can't get into recovery and I can ONLY boot into bootloader. I am on full stock with a locked bootloader running 7.1.1. I got off the phone with a Huawei rep and she stated it could be due to a Google update and that they will try and downgrade it on their end. Strange cause I was already running the latest 7.1.1 (unless a new update was released his morning).
Here's what I tried to no avail:
-unlocked bootloader and tried to flash stock rom/recovery
-tried flashing custom recovery (twrp)
-tried booting into temp customer recovery (twrp)
-tried flashing 7.0 stock
I have re-locked the bootloader and will have to send it in. What a real bummer, I have managed to get out of a softbrick (unless this device is truly bricked ???) on many, many device since the T-Mobile G1, but I am at wits end with this device.
Click to expand...
Click to collapse
You aren't alone obviously. These phones seem to be little time bombs where the boot loop issue is concerned. Mine goes into bootloops every time I flash an update or new ROM or attempt to restore a backup. I expect to hardbrick this phone at some point. It just hasn't happened yet.

Completely forgot about this thread. Huawei swapped out my motherboard with a 128 Gb (I had sent a 64 Gb). I actually quite happy my phone bricked itself. Haha

My 6p started rebooting last night and no matter what I did, couldn't get it to boot. Only bl mode worked. This thing has been one problem after another, so I went and got an iPhone this morning. Maybe one day Google will finally start making products that last more than one year, but hasn't happened yet and I'm tired of it.

andrewnelson23 said:
My 6p started rebooting last night and no matter what I did, couldn't get it to boot. Only bl mode worked. This thing has been one problem after another, so I went and got an iPhone this morning. Maybe one day Google will finally start making products that last more than one year, but hasn't happened yet and I'm tired of it.
Click to expand...
Click to collapse
On the same boat. Mine's stuck on bootloop, no recovery. 1 year is pretty good considering I've only had the device for 3 months...

Nexus 6p here in the UK, Got the OTA update yesterday and it caused crashes immediately. Had two crashes when it immediately rebooted and seemed ok. A third one soon followed and got stuck in a boot loop, a few minutes after it fixed it self and seemingly working fine. An hour later i was playing a game and it just locked, screenfroze and a buzzing noise from the speakers before going into a boot loop. Left it for a few hours while at the cinema and nothing.
Bought directly from Google and still under warranty. Interestingly though, i bought my 6p in March 2016, I then had to RMA it a few months later as the USB C port randomly broke I will be doing my second RMA in less than a year. When checking my IMEI the google support operative actually stated I was under warranty till August 2018. So a 30 month warranty. Got a new one coming out so if anyone develops this problem give them a ring.

New phone received, sent old one off. Checked it just before i did, still stuck in boot loop.

Narom88 said:
New phone received, sent old one off. Checked it just before i did, still stuck in boot loop.
Click to expand...
Click to collapse
That's way too common with this phone. Thinking about moving on to something else.

Stuck in bootloop on untouched stock rom, unrooted device.

This afternoon my S7 Edge entered a boot loop. All I was doing was reading the news, in the same app I have been for the past couple of months. The device is untouched in terms of modifications since purchase, so unrooted stock rom. I can get into download mode, and occasionally, recovery mode. I wiped the cache as my first attempted fix - no change. Then did a factory reset - no change. I then thought I'd try loading twrp so I could flash a custom rom, but Odin was unable to flash it due to FRP Lock blocking it. I then downloaded the latest stock rom from sammobile, and was able to flash this via Odin. On first boot the device did start to load, and reached 10/19 in optimising the apps, before starting the boot loop again. I am kinda out of ideas now. Any help would be greatly appreciated.

re: bootloops
whitebloodcell said:
This afternoon my S7 Edge entered a boot loop. All I was doing was reading the news, in the same app I have been for the past couple of months. The device is untouched in terms of modifications since purchase, so unrooted stock rom. I can get into download mode, and occasionally, recovery mode. I wiped the cache as my first attempted fix - no change. Then did a factory reset - no change. I then thought I'd try loading twrp so I could flash a custom rom, but Odin was unable to flash it due to FRP Lock blocking it. I then downloaded the latest stock rom from sammobile, and was able to flash this via Odin. On first boot the device did start to load, and reached 10/19 in optimising the apps, before starting the boot loop again. I am kinda out of ideas now. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Go into settings>developer's options and ENABLE OEM UNLOCK then
go into settings>general management>reset>factory data reset and
reset the phone.
Once you have done that the phone will work properly without rebooting
provided that you have successfully odin flashed the official samsung
G935F S7 Edge firmware prior to doing a factory data reset.
Good luck, have a great day!

Thanks for replying. Unfortunately I can't get into the phone at all. Only screen I have access to a recovery and downloader.

So I left the phone alone for a while and tried booting into safemode. This time it worked - sort of. It is asking me for a password, but I have never set one. I only ever set a pin and fingerprints. But since wiping everything that doesn't seem to apply anymore. What is the default password? I am referring to the phone password, rather than a google account obviously. I am not at that stage of the boot up.
Update: found the password (default_password), still boot looping on the optimising apps screen.

If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.

vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
I have flashed stock rom (initially the version that matches my carrier, although my phone was bought sim free and unlocked, and then the version for unlocked phones (BTU in sammobile I think)) but it still just boot loops. The phone can remain in download mode as long as it wants, and previously, when it was asking for the password, it was able to remain on that screen indefinitely. I would have thought if it was a hardware problem the boot looping would happen regardless of the action on screen. Immediately after flashing the stock rom, it did start to load before ooting. Now it just boots immediately at the Samsung Logo.

vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
Just to be clear, do you mean repartition here? I have not checked that option before, will try it.

Even without the PIT file. Flashing stock rom should have fixed you... which carrier do you have? If Verizon, they have a recovery assistant software that works in these situations. Or if not try "samsung kies". If all else fails I'd give Sammy a call.

vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
vsn4 said:
Even without the PIT file. Flashing stock rom should have fixed you... which carrier do you have? If Verizon, they have a recovery assistant software that works in these situations. Or if not try "samsung kies". If all else fails I'd give Sammy a call.
Click to expand...
Click to collapse
I am in the UK, and my carrier is Three, although the phone was purchased sim free. I tried samsung kies (phone not compatible apparently), samsung switch (phone does not support initialization). I may have to call Samsung, but I purchased the phone on eBay, so no warranty (never doing that again!), so I guess it'll be expensive to get them to sort it. I've taken it to a phone repair shop this afternoon and the guy reckoned he could fix it based on what I said. We shall see. I don't have to pay unless he fixes it, so worth a shot.

You can wipe your phone by entering recovery. Default recovery has the wipe option.

alehawk said:
You can wipe your phone by entering recovery. Default recovery has the wipe option.
Click to expand...
Click to collapse
Was the first thing I tried. Didn't help.

I got the bootloop thingy and was the cache, I wiped and the phone booted up

alehawk said:
I got the bootloop thingy and was the cache, I wiped and the phone booted up
Click to expand...
Click to collapse
Thanks for trying to help, but, again, already tried that.

whitebloodcell said:
I am in the UK, and my carrier is Three, although the phone was purchased sim free. I tried samsung kies (phone not compatible apparently), samsung switch (phone does not support initialization). I may have to call Samsung, but I purchased the phone on eBay, so no warranty (never doing that again!), so I guess it'll be expensive to get them to sort it. I've taken it to a phone repair shop this afternoon and the guy reckoned he could fix it based on what I said. We shall see. I don't have to pay unless he fixes it, so worth a shot.
Click to expand...
Click to collapse
Hope all goes well, let us know if you get it sorted out.

Hi
Just curious...why do u say u don't have warranty just because u brought from eBay?
Surely it doesn't matter where u brought it and it still has warranty.
Have u tried contacting Samsung?

AnubuRe said:
Hi
Just curious...why do u say u don't have warranty just because u brought from eBay?
Surely it doesn't matter where u brought it and it still has warranty.
Have u tried contacting Samsung?
Click to expand...
Click to collapse
Pretty much all warranties (including Samsung - I checked) are contracts with the original purchaser only. Even if you have proof of purchase, you then need to match the records they have of the identity of the original purchaser. Whilst some manufacturers will be more lenient, others will follow the official policy strictly. Speaking from experience here.

whitebloodcell said:
Pretty much all warranties (including Samsung - I checked) are contracts with the original purchaser only. Even if you have proof of purchase, you then need to match the records they have of the identity of the original purchaser. Whilst some manufacturers will be more lenient, others will follow the official policy strictly. Speaking from experience here.
Click to expand...
Click to collapse
For those perhaps in similar situation in the future, Samsung didn't care that it was purchased second hand, despite what the fine print says. They just looked at the serial number. In the course of trying my own repairs I flashed a custom rom, which of course tripped the knox warranty void bit. When I took it into the service centre they saw this and then wanted to charge £225 for an out of warranty repair. I refused at the time. I later called Samsung support and explained the situation (I said a phone repair shop must have done the flashing). Again on the phone I was told it would be an out of warranty repair, and this time I agreed. They collected my phone and returned it to me today however, with no invoice or mention of charges, so it looks like they just did the repair no questions asked.

I have the same issues, so far I'm getting by with flashing a stock rom with pit file and doing repartition and nand erase, normal cache/ factory reset doesn't help, it sometimes even boot loops while in twrp.
Somehow Odin flashing helps for a random amount of time, but it has thus far, crashed after a month, or a couple weeks since the last flash, etc. So far it's been my 5th boot loop event in the last 6 months
It sucks but as I got mine from another country (/win), didn't get the warranty ;( plus I tripped Knox by rooting.

sounds hardware related to me..
i had a friend with a note 4 who had similar problems it would hardly ever boot sometimes boot straight into download mode..
if by chance it did boot it would boot once the device was locked for a short time it would reboot and start over again bootlooping..
it was the emmc flash memory that was failing...
a workaround i found for this was the first thing i did when finally getting it to boot was install "Wake Lock - CPU Awake" and set it to never let the device sleep and to startup on boot...
this "fixed" it as long as your phone does not turn off... he had insurance though and sent it off and they sent him a new refirb
again this note 4 was untouched never rooted or anything

vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
im having pretty much the exact same problem except ive been unsuccesful at flashing the stock firmware for my galaxy s7 active (SM-G891A). the active series isnt the most saute after, so finding the right firmware is alil more difficult. which im pretty sure is how i got into this situation! my question is what exacly does checking the "reparation" option do. i read to leave to leave it unchecked/unticked. maybe thats why ive been unsuccessful. and someone told me awhile ago not to fill in the "bt" box becuz i have a locked bootloader. this correct or no?

Samsung S8+ Stuck in the boot loop, I think

Hi guys and gals
I am probably duplicating a thread for which I apologise in advance, but I have no clue for what key words I should be using to search for to find an existing answer, assuming there is one!?
I have the s8+ (SM-G955f) purchased in the UK via Vodafeon.
The battery died some weeks ago and I've had no money to be able to buy a replacement until now. I did try to use it now and again, but it last no more than a minute, but what did seem to happen is what is referred to as the boot loop saga.
I have followed other threads for instructions and downloaded Odin v.3.13 along with the varoius files (BL,AP,CP,CSC) from a zip file (G955FXXU9DTF1_G955FOVF9DTF1_VOD.zip) I was doing this late last night and do no remember which website I got it from, it took sooo long to download.
I am now at the point where I have connected the phone via USB and I have run the program and the status went to green, said 'pass' and the phone rebooted, however it is back to the Samsung welcome screen and sometimes keeps rebooting, other times, just stays there.
Where do I go from here? would it be that I have used the wrong firmware? I have never done this stuff before and have no clue, but am desperate to have a working phone as I have no money to replace it
Any advice, very welcome

If the battery went bad why flash firmware. Replace the battery

TheMadScientist said:
If the battery went bad why flash firmware. Replace the battery
Click to expand...
Click to collapse
I guess the issue was when the battery had issues, it would last maybe a minute or 2 before shutting down and then having to wait a full day before trying again. I did this for about a week as needed to get phone numbers from the phone along with some other info.
On the last occassion the phone turned on before the battery finally gave up, it seemed to go into the bootloop.
So now, I have tried various versions of Firmware via Frija and using Odin 3.13 to instal, but the phone doesn't seem to want to accept it.
The phone was originally purchase via Vodafone in the UK. I have tried VOD and BTU.
I am now in Asutralia, so have also tried TEL and VAU as have had sims from them also.. if that makes a difference?
I cannot get into the recovery mode at the moment, no clue why, just the download screen. The last time it went into recovery it kept mentioning about ATT which I don't understand as the phone has never had an AT&T connection which I think is in the USA and the phone has not been there..
Does anyone have any other suggestions? Would it be crazy to try and instal a custom OS and then revert back, or does the phone always remember the original firmware? I hope this all makes sense as this is all new to me..
Thanks in advance.