Memory Bug??? - LG V20 Questions & Answers

Well, it happened... I was browsing XDA on my beautiful V20 when suddenly I'm looking a the boot logo.. and then a black screen. I tried to turn it on a million and one times, various battery pulls, plugging into every PC in the house (and it wasn't detected... at all). The only thing it would do is vibrate one time after holding the power button. I was at a loss.. If my computer couldn't recognize it, I couldn't fix it.
Thankfully, it was still under manufacturer warranty. I sent it in holding my breath, hoping they wouldn't be able to tell that I had Dirty Santa'd the hell out of the bootloader. As luck would have it, not even 24 hours later I received an email saying my phone had been repaired. And what did they do to fix my V20?
... they replaced the flash memory.
LG's track record with memory hasn't been the greatest the past couple of years, so I'm wondering if the memory bug is going to happen to us.
FYI: My V20 was a US Cellular US996 running WETA ROM with barely any tweaks other than what came with the ROM.

I have 2 v20s that I have bricked 3 times for various reasons. When I sent them off for repair, LG replaced the NAND twice, and the entire logic board once.
At the time I thought maybe it was just easier for them to replace the NAND than to re-flash it, but I think you may be on to something. Maybe they know that the NAND they used is flaky, so they don't even try and flash it.
-- Brian

Related

Possibly bricked forever - Stuck at Sumsung logo endless reboot

Stupid thing is that I can do everything to it aside from getting it to boot all the way to work! I tried reflashing OEM roms and I tried custom roms. They all work just fine and it just won't boot all the way. I can turn it on and off, use format option, download mode and magldr. I keep my sim out and memory card. Before this all happened I always used OEM OS. Last thing I did was check my bank account, close the browser and click the power button to turn it into sleep mode. Few weeks ago I did have an issue with it for a day. It kept turning on and off constantly boot to random points. Mostly to the AT&T screen. It would boot all the way rarely and I got it to stay on a couple times for about 10 mins to copy all my stuff from it. Is it possibly something to do with the hardware being a POS and Just crapping out for no reason because cell phones are poorly made expensive bricks?
I've seen this issue across the forum several times. Unfortunately, just one case seemed to "return" to life, without understanding the reasons behind the "lapse".
What I can suggest you can do (and feel free to disagree) is get in touch with Cottula (creator of MAGLDR) and see if you can help you. You can send him the phone, maybe he can analyze it and get something out of it.
GL, mate, and if you find a solution, I'm sure other folks here would be glad to hear it.
Ahhh ok thats what I figured. I browsed a bit, but most of what I saw is people couldn't do anything. I didn't see anyone saying they could do as much as what I can do with it. I'll try your advice and see if maybe he could help. I took apart the phone to see if maybe someone came loose, though I saw nothing. Clean as a whistle. What I think maybe happen is it burnt up finally. I notice at times it would run extremely hot, mostly when I'm talking on it for more then an hour.
Well, for your sake I hope it's not burned out (hardware issue). I hope it has some software component that's screwed and that has a chance of being investigated and maybe fixed.
Also, the getting hot while talking/browsing for periods more than 30 min it's a known issue. It's however supposed to be quite warm, but not actually really hot, if you know what I mean. It it however possible that exposing the phone to higher temperatures to cause hardware issues.
In any case, I wish you good luck. Who knows?
I gave AT&T a call to see what they could do. The software warranty is 6 months past and she wasn't able to override anything that much passed over. Though I was able to get my 2 years wavered and get a early upgrade. So I got myself a Xperia Ion. I'm happy I don't have to put up with a flip phone for another 4 months. lol
I tried working on my focus a bit more playing with zune and other programs I found. Though I don't see it coming back to life trying all the different ROMs. I would think to make it work again is to re-flash the actual phone bios itself. Just like a computer starting it still uses DOS then loads the OS. I don't know how a phone works to much, but I'd assume same process. Something to do with the root-root of the phone telling it to be stupid and not boot properly.
Another note, where is the best place to sell this to get some money out of it? Screen and other pieces of its hardware are 100%. Should I try ebaying it?
I had a similar issue, last thing i did was removing the SD card before re-flashing the MGLDR and custom ROM

Note 4 wont turn on, "cannot boot normal" and "downlaoding target, dont turn off"

Note 4 wont turn on, "cannot boot normal" and "downlaoding target, dont turn off"
Its a Note 4 SM-N910F, Android 6.0.1, BB N910FXXU1DPE2, kernel 3.10.40-7733605 [email protected] #1
i feel I have tried everything... History:
Phone has been working fine for a year, upgraded to 6.0.1 no problems about 2 or 3 months ago. no new apps installed. Last week it started getting very laggy, keyboard strokes took for ever to register. I thought, ok, time to to a factory reset to blow out any old cobwebs. Did it via the menu. However the phone froze midway thought. I left it for an hour and then pulled out the battery. I popped it back in and it performed the reset without me having to press anything. Cool, thats good I thought.
Now I was going to change the battery, so I powered off as normal and put my other 2 week old original samsung battery in, and it would not power on. After a few reinsertions it powered back on. I though i have to do another reset. So I tried, and it would not reset. It just died. I cant restart the phone, it dies. If I shut it down normally. it wont turn on back on, I have to take out and reinsert the battery multiple times, holding down the powerbutton between to discharge. this can take up to 10 tries now. Sometimes it will go th the unable to bot in normal mode and "downloading , do not turn of target, but it will stay there for ever, more than an hour.
Every 15-20 tries it would turn on, let me get in via pin, only to start freezing up within a min, and then die again. Somewhere I read that a guy hada similar problem, and he used wakelock and that worked, on level 4. I managed to download that and used it, and hey presto, it works!
Now I had to power down the phone for a reason, and it took me about 30 min of battery and powerbuttonholding before it managed to boot up, and I was quick enough to start wakelock on level 4.
It wont boot in to safe mode, it wont boot in to recovery mode, it wont boot in to the factory reset mode. Its the same with either battery, and different cables.
Any ideas what i can do here, or what could be wrong? I havent gotten it wet or banged it.
I am having the same exact issue on a N910A. Phone was functioning correctly and in December it started getting really laggy. Performed various resets, purchased new battery. Still laggy. Up until two weeks ago the phone was slow but now it will not power on . The phone will not charge as well.
Mine did same, 6 months old, not rooted stock firmware. Locked up yesterday, couldn't do anything. Pulled battery and restarted. Samsung logo comes on screen goes black for android boot then it hangs with blue led flashing. Nothing I do gets it past that point. Tried safe boot but it doesn't fully launch with correct button combo and volume up. In the end I re-installed firmware using Keis. All went well, everything as per youtube tutorial. Except one thing, at end of download phone didn't re-start. Still can't get it to boot, any ideas?
Edit: Lock up didn't coincide with any new apps being loaded or updates of existing. Only change was a week ago which was an automatic update of the stock firmware (Lollipop)
armstrongracer said:
Mine did same, 6 months old, not rooted stock firmware. Locked up yesterday, couldn't do anything. Pulled battery and restarted. Samsung logo comes on screen goes black for android boot then it hangs with blue led flashing. Nothing I do gets it past that point. Tried safe boot but it doesn't fully launch with correct button combo and volume up. In the end I re-installed firmware using Keis. All went well, everything as per youtube tutorial. Except one thing, at end of download phone didn't re-start. Still can't get it to boot, any ideas?
Edit: Lock up didn't coincide with any new apps being loaded or updates of existing. Only change was a week ago which was an automatic update of the stock firmware (Lollipop)
Click to expand...
Click to collapse
are you still under warranty? i sent mine to a samsung center, the guy recognized the problem as the motherboard, said I wasnt the first. That was 3 weeks ago, they are STILL waiting for the parts. They say the Samsung factory are way behind with repair parts, etc etc. I am hoping it will go under warranty. Ill update when I know!
I've been having the same problem that started yesterday morning. I've tried a few different solutions but nothings worked, I get the feeling that my phone is dead and I'm not in warranty either. I'm going to approach Samsung but my guess is they will want more than the phone is worth to repair it. I've read about so many people having the same issues, its horrendous engineering on Samsungs part considering how much their phones cost to start with
neils0911 said:
I'm going to approach Samsung but my guess is they will want more than the phone is worth to repair it. I've read about so many people having the same issues, its horrendous engineering on Samsungs part considering how much their phones cost to start with
Click to expand...
Click to collapse
Your guess is probably correct and I totally agree with you. I seriously think manufacturers do not want their devices to be problem free for more than two years. Probably why they have stopped making phones with batteries that simply pop out.
bonfilet said:
Your guess is probably correct and I totally agree with you. I seriously think manufacturers do not want their devices to be problem free for more than two years. Probably why they have stopped making phones with batteries that simply pop out.
Click to expand...
Click to collapse
Definitely...surely it couldn't have been that hard to make a device with a battery that was still removable on the newer phones. It's frightening how many forum posts I've found with people having their phones just brick out of nowhere (and that's just the note 4). I've given up trying to fix mine, I've tried every method I could find and nothings worked. I can only assume that this problem is simply the motherboard of the phone not working anymore. I'm not even sure what phone to buy now but it certainly won't be a Samsung.
neils0911 said:
. I'm not even sure what phone to buy now but it certainly won't be a Samsung.
Click to expand...
Click to collapse
If you do not care about the camera thera are a lot of rather affordable options which can be tossed in the bin when they start malfunctioning and if their warranty has run out. If you care about the camera being as good as the Note 4's than the range of phones you can buy is quite limited.
mymigi said:
I am having the same exact issue on a N910A. Phone was functioning correctly and in December it started getting really laggy. Performed various resets, purchased new battery. Still laggy. Up until two weeks ago the phone was slow but now it will not power on . The phone will not charge as well.
Click to expand...
Click to collapse
If you are able to boot it into Download Mode then you should Download Stock Rom file for Galaxy Note 4 from Sammobile and Flash it through Odin..
Everything will be OK... ?
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
mymigi said:
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
Click to expand...
Click to collapse
You can find here firmware for N910A , 5.1.1 and 6.0.1 : https://simunlockremote.com/firmware-support/
bonfilet said:
If you do not care about the camera thera are a lot of rather affordable options which can be tossed in the bin when they start malfunctioning and if their warranty has run out. If you care about the camera being as good as the Note 4's than the range of phones you can buy is quite limited.
Click to expand...
Click to collapse
I think the camera on the note 4 is absolutley terrible. I might even go so far as to say the pictures are unusable. the applied noise reduction renders everything splotchy, colors are off and its not sharp at all. and Im not talking dark conditions here.
Anyway, my phone was repaired under warranty and is back to working as it should. It was indeed the motherboard, so if you have the same troubles I had, those are your best bets.
I don't think replacement via warranty will be available. I will attempt to power into download mode and verify if I can get it back up and running. If not, a good ole paperweight.
mymigi said:
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
Click to expand...
Click to collapse
You can download the Firmware from here ..
https://www.androidfilehost.com/?fid=24459283995298017
---------- Post added at 05:43 AM ---------- Previous post was at 05:41 AM ----------
mymigi said:
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
Click to expand...
Click to collapse
You can download the Firmware from here. .
https://www.androidfilehost.com/?fid=24459283995298017
Sounds like the problems I have: with my first N910F: started with lagging apps / freezing, then random reboots now and then, eventually giving error messages when booting. Finally, now it will only start after the battery has been out for at least 30 minutes, but hangs on error message. When pulling battery out and putting back in it, wont give a single sign of life. Since I was just out of warranty it has been lying around, and I bought a second hand N910F for replacement, sadly its starting to give the same errors too and is just out of warranty too (its currently still working, but with freezes / reboots / and already a event with boot error).
I read It could be memory chips or some power chip on the motherboard, appears to be a common problem. So.... Last month I bought a new motherboard on ebay (chinese delivery, 80€). Received it last week and put it back in; phone is back to life. (putting it in is a very simple task, with iFixit teardown / guide)
Anyway, I love the Note 4 for performance / size / looks, and have been Samsung fan for a while, but this recent breakdowns and information that it is fairly common, has diminished being a fan fairly quickly and I guess the Note 4 will be the last Samsung device for a while after this new motherboard breaks down as well
onno72 said:
Sounds like the problems I have: with my first N910F: started with lagging apps / freezing, then random reboots now and then, eventually giving error messages when booting. Finally, now it will only start after the battery has been out for at least 30 minutes, but hangs on error message. When pulling battery out and putting back in it, wont give a single sign of life. Since I was just out of warranty it has been lying around, and I bought a second hand N910F for replacement, sadly its starting to give the same errors too and is just out of warranty too (its currently still working, but with freezes / reboots / and already a event with boot error).
I read It could be memory chips or some power chip on the motherboard, appears to be a common problem. So.... Last month I bought a new motherboard on ebay (chinese delivery, 80€). Received it last week and put it back in; phone is back to life. (putting it in is a very simple task, with iFixit teardown / guide)
Anyway, I love the Note 4 for performance / size / looks, and have been Samsung fan for a while, but this recent breakdowns and information that it is fairly common, has diminished being a fan fairly quickly and I guess the Note 4 will be the last Samsung device for a while after this new motherboard breaks down as well
Click to expand...
Click to collapse
My phone is also random Rebooting
It also shuts down at 25% of battery remaining, Have you also faced similar issue?
Download the app "Wake Lock" and run the Partial Wake Lock option. Apparently the updated software impacts the CPU. For the restarting issue, put it in the freezer for a couple minutes. You may have to take the battery out once, but it has worked for me every time.
This looks very much like the issue reported here:
https://forum.xda-developers.com/no...-error-fix-t3434335/post72944466#post72944466
There are temporary fixes (wakelock), but ultimately this is a harware issue, and the fix is a new motherboard.
I think that underlying it is a problem with heat affecting the eMMC chip or its connection to the motherboard.
See also:
https://us.community.samsung.com/t5...ePhones/thread-id/12183/highlight/true/page/1
http://www.classlawdc.com/2017/04/25/investigation-samsung-galaxy-note-4-mmc_read-failed-defect/
Hey can u pls get me the stock firmware for n910gddu1dpb4
You might find this interesting. Since I couldn't get mine to power up at all, I called Samsung tech and they quoted me $75 to fix it and they would pay for shipping. I figured it was better then getting another phone off Swappa. 2-3 weeks later i get an email that they are repairing it under warranty at no cost to me. I got a refurbished phone since i know my IEMI number was different. they didn't explain why. Anyway, I got lucky i guess.

Can my Note 4 be saved?

I've got a Note 4 (AT&T SM-N910A) that is having a problem with reboot looping. I've read some of the posts on this issue, but the solutions I've tried so far haven't worked. I'm kind of overwhelmed by the number of posts on this issue and trying to find solutions. I just want to list some of the symptoms I've had and things I've tried, and if anybody can suggest anything else to try I'd really appreciate it.
The phone started rebooting constantly, sometimes it makes to the home screen before rebooting, sometimes it doesn't even make it past the initial Samsung logo.
It rapidly got worse, the phone was completely locking up during various phases of booting up.
Plugging it into the charger doesn't help.
Completely drained and then charged the battery, didn't help.
Removed the microSD and SIM cards.
I just got a new battery, which didn't solve the problem, but improved so at least it is no longer locking up during the boot process.
Booted in safe mode, didn't improve.
I put the phone in the freezer for a couple of hours. This gave me enough time to install Wake Lock and enable the PARTIAL_WAKE_LOCK mode.
After the freezer and wake lock, I had maybe 5 minutes to transfer some files from internal storage before the reboot started up again.
I can get into recovery mode, where it seems stable, but I don't know if that can help me at all.
At this point I'm only hoping to recover some files from internal storage, then it's time to be done with this phone. Kind of sad that a smartphone that was an $800+ "flagship" barely lasts two years. Thanks
thepieguy said:
I've got a Note 4 (AT&T SM-N910A) that is having a problem with reboot looping. I've read some of the posts on this issue, but the solutions I've tried so far haven't worked. I'm kind of overwhelmed by the number of posts on this issue and trying to find solutions. I just want to list some of the symptoms I've had and things I've tried, and if anybody can suggest anything else to try I'd really appreciate it.
The phone started rebooting constantly, sometimes it makes to the home screen before rebooting, sometimes it doesn't even make it past the initial Samsung logo.
It rapidly got worse, the phone was completely locking up during various phases of booting up.
Plugging it into the charger doesn't help.
Completely drained and then charged the battery, didn't help.
Removed the microSD and SIM cards.
I just got a new battery, which didn't solve the problem, but improved so at least it is no longer locking up during the boot process.
Booted in safe mode, didn't improve.
I put the phone in the freezer for a couple of hours. This gave me enough time to install Wake Lock and enable the PARTIAL_WAKE_LOCK mode.
After the freezer and wake lock, I had maybe 5 minutes to transfer some files from internal storage before the reboot started up again.
I can get into recovery mode, where it seems stable, but I don't know if that can help me at all.
At this point I'm only hoping to recover some files from internal storage, then it's time to be done with this phone. Kind of sad that a smartphone that was an $800+ "flagship" barely lasts two years. Thanks
Click to expand...
Click to collapse
You probably have hardware that is failing (most likely the memory chips on the motherboard). On any of the reboots have you seen a screen like this: http://thedroidguy.com/2015/12/could-not-do-normal-boot-mmc_read-failed-error-on-galaxy-note-4-1052795 ? I've been told that the "ddi : mmc_read failed" message is an indication that the memory chips on the memory board are failing.
It's probably time to contact Samsung Customer Support (1-800-SAMSUNG). That's what I finally did and they repaired my Verizon Note 4 for $70.31 to "like new" condition. See my post here: https://forum.xda-developers.com/showpost.php?p=71863607&postcount=310.
Your mileage may vary, however. Someone else took the same approach and it is going to cost them more. See post here: https://forum.xda-developers.com/showpost.php?p=72258958&postcount=313. You don't have to agree to Samsung's repair estimate if you think it is too high. My understanding is that if you refuse they will send the phone back for no charge. Before I sent mine in I had mentally set an upper repair limit of $150 since you can still buy new Verizon Note 4's on Amazon for about $300.
Good luck.
Dwillian said:
You probably have hardware that is failing (most likely the memory chips on the motherboard). On any of the reboots have you seen a screen like this: http://thedroidguy.com/2015/12/could-not-do-normal-boot-mmc_read-failed-error-on-galaxy-note-4-1052795 ? I've been told that the "ddi : mmc_read failed" message is an indication that the memory chips on the memory board are failing.
It's probably time to contact Samsung Customer Support (1-800-SAMSUNG). That's what I finally did and they repaired my Verizon Note 4 for $70.31 to "like new" condition. See my post here: https://forum.xda-developers.com/showpost.php?p=71863607&postcount=310.
Your mileage may vary, however. Someone else took the same approach and it is going to cost them more. See post here: https://forum.xda-developers.com/showpost.php?p=72258958&postcount=313. You don't have to agree to Samsung's repair estimate if you think it is too high. My understanding is that if you refuse they will send the phone back for no charge. Before I sent mine in I had mentally set an upper repair limit of $150 since you can still buy new Verizon Note 4's on Amazon for about $300.
Good luck.
Click to expand...
Click to collapse
Hey thanks for your input. I haven't seen any kind of error screens pop up. $70 to have your phone reconditioned is a really good score for you. I was able to pull my phone from the freezer several times and at least got all of my photos and videos off, which was my primary goal.

LG G6 Bootloop -- Don't Know What Else to Do! -- Please Help!

I have an LG G6, international version (H870DS) that has been having bootloop issues for a while now. For the first few months it would come and go -- sometimes it would be a week between issues, sometimes just a few minutes. I tried many things, multiple factory resets, removed the SD card, deleted possible troubles apps, basically anything I could find online to try. But, for a while the phone would work pretty much normally until it decided to restart and loop.
But... about two weeks ago the phone got into its bootloop and never came out -- I can't get past the LG logo screen anymore. If I let the phone go for a while eventually it gets to a green screen talking about a RAM dump. One time I managed to get it to a screen talking about unlocking the bootloader but that part got a bit over my head. Basically, I can let the batter die but as soon as I plug it in, the phone starts lopping again for 15 minutes or so, eventually ending at that green screen.
Over the last few days I have tried downloading a stock KDZ file to try to flash stock ROM back onto the phone. The problem is, I can't get the phone to communicate with my computer no matter what I do. I've downloaded LGUP, installed all the drivers, tried the LG Flash Tool and pretty much anything else I could find -- but I just can't get anything to recognize the phone, even when I get it into download mode. I know the problem isn't with drivers because when I try my wife's identical G6 on my computer it gets recognized right away.
I should mention that I never tried to tweak anything with the phone -- the issue has been occurring since it was basically brand new. I am by no means an idiot when it comes to tech but also far from an expert, but I have done my research and tried everything I could.
So -- basically I am out of options and appealing to anyone who can help. I currently live in Africa and have no access to LG service centers. I have spent upwards of 10 hours trying to figure this out now and I just don't know what else to try. Any tips or advice would be incredibly appreciated. Thank you!
This looks like a hardware failure. if you have warranty, you should send it back to them. The seller can't take care of the warranty ?

V20 VS995 Bootloop (no root, 1CA update)

Today on my way to work I was playing music through my bluetooth and the music stopped. I went to reset bluetooth and it took almost 3 mintues to turn off. When I went to turn it back on, it wouldn't. I powered off and reset the phone. After, it got stuck in a bootloop. LG logo for about 7-8 secs and restarts.
Before the bootloop, I was noticing a few weird things: A notification of USB Options was always up, was saying I was using my phone as a USB Power Supply. If I changed the options it would revert back to USB PwrSply. I noticed the battery life was getting a lot worse. Also, when plugged into Quick Charge it would not say "Quick Charging" anymore.
I can get into the Recovery menu, but all options revert to the bootloop.
I can get to the Download menu. After about a few seconds of sitting on the Download menu, it starts the LG logo bootloop.
I have not tried to flash another stock ROM. I have downloaded the LGUp program, Uppercut, LG Mobile Support Tool, and LG Mobile Driver. I also downloaded the previous 1BA firmware kdz file.
I believe I have the knowledge to reflash properly, but I do not want to make the phone worse or lose my data. Plus, I don't want to void the warranty.
TL;DR I have bootloop and want to save my data!
Any suggestions would be very much appreciated! Thank you!
Flashing won't help you, this is a hardware problem. You can try freezing then phone, seeing if it will boot, and then backing up your files a fast as you can. Alternatively, if that doesn't work, you can take a hair dryer and heat the phone up.
Either way, LG will definitely take care of it under warranty since those morons can't seem to make a decent heat sink that lasts. Every LG flagship phone since the G4 has had this problem. I am sure the V30 and G7 will be no different -- they just haven't been out long enough yet.
-- Brian
runningnak3d said:
Flashing won't help you, this is a hardware problem. You can try freezing then phone, seeing if it will boot, and then backing up your files a fast as you can. Alternatively, if that doesn't work, you can take a hair dryer and heat the phone up.
Either way, LG will definitely take care of it under warranty since those morons can't seem to make a decent heat sink that lasts. Every LG flagship phone since the G4 has had this problem. I am sure the V30 and G7 will be no different -- they just haven't been out long enough yet.
-- Brian
Click to expand...
Click to collapse
I was hoping that this wasn't the issue. I was hoping that it was from the 1CA update, because the other random problems seemed to have started when it updated. Should I at least try to reflash? Would reflashing to a stock/OEM ROM (the one i mentioned above) void the warranty?
Also, when I restarted the phone today, that was the first restart that I have done since the update. Not sure if that means anything, but maybe??? lol
No, flashing a KDZ does not void the warranty even by LGs terms.
In the US rooting your phone doesn't void the warranty either .. no matter what OEMs will have you believe.
-- Brian
runningnak3d said:
No, flashing a KDZ does not void the warranty even by LGs terms.
In the US rooting your phone doesn't void the warranty either .. no matter what OEMs will have you believe.
-- Brian
Click to expand...
Click to collapse
Awesome! That's definitely good to know. Thanks.
I'm going to attempt to downgrade flash it. If it doesn't work, I'll contact LG. I dont really care about buying a new phone. My data on it is worth WAY more to me than the phone. (Guess I really should start backing up my stuff XD )
If you have any suggestions as to recovering my data, even if it kills the phone, I'm all ears!
Update: I attempted to flash or just access the phone as storage using many different ways. While I was browsing for new answers, I kept the phone connected to my computer and left it bootlooping. Eventually, the phone battery died and booted up properly. The battery was at 1%, but everything loaded just fine. I was able to recover all my data and save it to my PC.
Thinking that this was a soft-brick due to the phone actually fully booting, I was going to attempt to root and flash. I let the phone charge to 100%. When I reset the phone to implement the root, the phone got stuck in a BOOTLOOP AGAIN.
Any ideas in why this would happen? Does this mean it's a software based bug, or hardware?
Dart_Fur said:
Update: I attempted to flash or just access the phone as storage using many different ways. While I was browsing for new answers, I kept the phone connected to my computer and left it bootlooping. Eventually, the phone battery died and booted up properly. The battery was at 1%, but everything loaded just fine. I was able to recover all my data and save it to my PC.
Thinking that this was a soft-brick due to the phone actually fully booting, I was going to attempt to root and flash. I let the phone charge to 100%. When I reset the phone to implement the root, the phone got stuck in a BOOTLOOP AGAIN.
Any ideas in why this would happen? Does this mean it's a software based bug, or hardware?
Click to expand...
Click to collapse
I'm not sure to be honest, your situation seems strange
Was it hot and was your phone in the sun during your trip to work? Overheating can make weird things happen.
lakingslayer said:
Was it hot and was your phone in the sun during your trip to work? Overheating can make weird things happen.
Click to expand...
Click to collapse
It wasn't hot at all, I had the A/C in my car on and it sets on a car mount that mounts to the air vent. It gets direct A/C. I didn't have it charging either.
All I did was connect my phone to Bluetooth, play a mix, and drive 15mins to work at 6am in the morning. It was still dark and cool out. The music stopped and I tried to reset bluetooth. It took forever to turn off and wouldnt turn back on. I reset phone and BOOTLOOP. ???
There is no damage to the phone physically. I don't think I've ever dropped it ever. It's gotten hot a couple times, but that was months and months ago.
I've never had a problem with this phone since I got it almost 2 years ago, since the 1CA update, I had a couple bugs, now this bootloop.
Dart_Fur said:
Update: I attempted to flash or just access the phone as storage using many different ways. While I was browsing for new answers, I kept the phone connected to my computer and left it bootlooping. Eventually, the phone battery died and booted up properly. The battery was at 1%, but everything loaded just fine. I was able to recover all my data and save it to my PC.
Thinking that this was a soft-brick due to the phone actually fully booting, I was going to attempt to root and flash. I let the phone charge to 100%. When I reset the phone to implement the root, the phone got stuck in a BOOTLOOP AGAIN.
Any ideas in why this would happen? Does this mean it's a software based bug, or hardware?
Click to expand...
Click to collapse
I hope you got your data off before you started messing with it.. your phone is dead.. Runningnak3d gave you a clear warning
Flashing won't help you, this is a hardware problem. You can try freezing then phone, seeing if it will boot, and then backing up your files a fast as you can. Alternatively, if that doesn't work, you can take a hair dryer and heat the phone up.
Click to expand...
Click to collapse

Categories

Resources