So my phone will randomly not boot fully, just get stuck on the animation. I'm running Rapture 2.3. It just keeps playing the animation over (not a full bootloop, just freezes) and I have to pull the case off, carefully remove the back cover, and take the battery out (as holding the power button does nothing). I've tried clearing my cache and even another ROM (FireKat did the same thing), but this problem pops up so arbitrarily it seems. Whether I'm doing a full reboot, a 'hotboot' or 'fast reboot', or even turning the device on from dead off after charging, sometimes it works just fine, sometimes I have to pull the phone apart and try again.
Anybody else have this problem?
I'm having the same issue and I can't figure it out for the life of me. I just live with it the way it is. Let us know if you figure out something.
---------- Post added at 05:46 AM ---------- Previous post was at 05:44 AM ----------
falsepr0phet said:
So my phone will randomly not boot fully, just get stuck on the animation. I'm running Rapture 2.3. It just keeps playing the animation over (not a full bootloop, just freezes) and I have to pull the case off, carefully remove the back cover, and take the battery out (as holding the power button does nothing). I've tried clearing my cache and even another ROM (FireKat did the same thing), but this problem pops up so arbitrarily it seems. Whether I'm doing a full reboot, a 'hotboot' or 'fast reboot', or even turning the device on from dead off after charging, sometimes it works just fine, sometimes I have to pull the phone apart and try again.
Anybody else have this problem?
Click to expand...
Click to collapse
I'm having the issue and I can't figure it out for the life of me. I just live with the way it is. Let us know if you figure out something.
I'd do a factory reset, Odin back to stock, and start the rooting process over.
Android_Monsters said:
I'd do a factory reset, Odin back to stock, and start the rooting process over.
Click to expand...
Click to collapse
Okay you win, I'll give it a try. Just did the reset, Odin-ing back to stock now. Will update.
UPDATE: On stock, rooted and recovery. Installed xposed and gravity box to give me advanced reboot options. Did several fast reboots, regular reboots, and full power down and back ups. No freezes. Going to clean install Rapture now.
chrispyutec said:
I'm having the same issue and I can't figure it out for the life of me. I just live with it the way it is. Let us know if you figure out something.
Click to expand...
Click to collapse
What (if any) Xposed modules do you have installed? After a few hundred reboots after installing things one by one and doing several reboots between each install, I'm pretty sure I've narrowed it down slightly.
I can tell you that Wanam and Xposed Torch are not looking like the causes.
Currently I'm not running xposed or wanam and it still does the same. I'm pretty much used to living with it. Luckily I go naked and not rock a case that's tough to remove which helps for battery pulls.
chrispyutec said:
Currently I'm not running xposed or wanam and it still does the same. I'm pretty much used to living with it. Luckily I go naked and not rock a case that's tough to remove which helps for battery pulls.
Click to expand...
Click to collapse
Interesting. I think I've figured it out. It did it as soon as I restored Gravitybox. So I uninstalled it, did several reboots and had no freezes. I did a fresh install, and did not restore the data but rather set all the settings manually, and so far have had no freezes. I wonder if it has something to do with restoring data using Titanium Backup from a completely different device (individually restored a lot of data from my Galaxy S4).
EDIT: Nevermind, it just froze again :/
falsepr0phet said:
Interesting. I think I've figured it out. It did it as soon as I restored Gravitybox. So I uninstalled it, did several reboots and had no freezes. I did a fresh install, and did not restore the data but rather set all the settings manually, and so far have had no freezes. I wonder if it has something to do with restoring data using Titanium Backup from a completely different device (individually restored a lot of data from my Galaxy S4).
EDIT: Nevermind, it just froze again :/
Click to expand...
Click to collapse
Dang it! Was hoping you were on to something.
chrispyutec said:
Dang it! Was hoping you were on to something.
Click to expand...
Click to collapse
Do you use a custom ROM or are you rooted at all? This is so frustrating. Sometimes I feel like I get it, then it happens again.
falsepr0phet said:
Do you use a custom ROM or are you rooted at all? This is so frustrating. Sometimes I feel like I get it, then it happens again.
Click to expand...
Click to collapse
I'm running a clean install of Rapture with no other mods except for what's already baked into the ROM.
---------- Post added at 06:54 PM ---------- Previous post was at 06:50 PM ----------
chrispyutec said:
I'm running a clean install of Rapture with no other mods except for what's already baked into the ROM.
Click to expand...
Click to collapse
I only get stuck on reboot when I either restart or shutdown. I never have random reboots and what's weird is my stuck on reboot issue doesn't happen every time I restart or shutdown......it's totally a flip of the coin if it will get stuck or not.
Have you tried a different rom? Of course, with a factory reset + Odin to stock first.
chrispyutec said:
I'm running a clean install of Rapture with no other mods except for what's already baked into the ROM.
---------- Post added at 06:54 PM ---------- Previous post was at 06:50 PM ----------
I only get stuck on reboot when I either restart or shutdown. I never have random reboots and what's weird is my stuck on reboot issue doesn't happen every time I restart or shutdown......it's totally a flip of the coin if it will get stuck or not.
Click to expand...
Click to collapse
I'm also having this issue on occasion. I am thinking I may not have flashed the proper baseband and firmware to match the rom I was using. Is this possible with anyone else?
chrispyutec said:
I only get stuck on reboot when I either restart or shutdown. I never have random reboots and what's weird is my stuck on reboot issue doesn't happen every time I restart or shutdown......it's totally a flip of the coin if it will get stuck or not.
Click to expand...
Click to collapse
After 3 days, 5 ROM installs, and what seemed like well over 1000 reboots, I've finally.. given up. I tried flashing the "Baseband" and "Bootloader" from the Rapture post, still freezes. I'm at the point where I can actually tell when it's going to do it because the boot animation isn't as bright as normal. It always get's darker right before it shows the lockscreen, but if it's going to freeze, the boot animation starts dark.
Related
Ok, so i've spent a few hours at this already but let me give as much info as I can. I have read through many threads searching for info. I am no expert but I have had OG Droid, Incredible, and currently Thunderbolt all rooted so I am a novice.
This is my GFs phone and was previously bone stock, never rooted, no Roms nothing. So she gets the update recently and clicks yes and that is where the trouble began, phone constantly reboots and will not go past the language/activation screen. It never once went past that first screen, and she tried the hard reset and the battery pull.
So this is where I took over. I retried the hard reset (power + vol down) and also the battery pull. I also tried to activate in numerous other languages, all cause a reboot.
As per
http://forum.xda-developers.com/archive/index.php/t-1208713.html
I was finally able to get past the activation screen and make some progress. However after about a minute the phone always reboots, no matter what it is doing. I hard reset in the settings menu and that did nothing.
I next followed
http://forum.xda-developers.com/showthread.php?t=1326347
and got the phone rooted.
Installed
http://forum.xda-developers.com/showthread.php?t=1144951
and than installed CWR 4.0.0.4 ? (not sure the version whatever it comes with) Tested recovery and it it seems to stick even after rebooting several times, which the phone automatically does (maybe its a feature and not a flaw?) So I was unsure of what version of Android was even running because the phone will not allow me to go into about phone it always force closes *com.android.settings* but I figure what the heck and try my luck with a new Rom. I decided on
http://forum.xda-developers.com/showthread.php?t=1326542&page=11
So I did the usual. Rebooted into recovery, made a nandroid backup, wiped data, cache, davlik and even did /system for good measure. Than did the install and upon first boot all the same problems are there. It will not activate from the screen, it just reboots the phone eventually. I used the same method above to avoid the screen and now it will boot up and the phone is in fact running an AOSP Rom but it still reboots after about a minute. Oddly enough it also continues to refuse to let me open About Phone, in the settings menu. I also for good measure went into recovery and wiped everything again and also tried fixing permissions in recovery, all to no avail.
At this point I am thinking it is perhaps just a hardware issue, although the phone does not reboot itself in recovery. I would be willing to try a different Rom, however I don't think it would work. I am wondering if anyone has any other suggestions? Should I try this?
http://forum.xda-developers.com/showthread.php?t=1120062
Other info:
What does work is wifi, so i can get on the internet briefly. I can connect to google and get apps from the market.
I am leaving this for a few hours or I may have to re-title the thread "How do you put the LG Revolution back together after throwing it against a wall?"
Currently I'm sad face that you rooted and installed cwm but I think the update bricked it personally. Hopefully S.Meezy will see this as he has stock recovery. I would say just get back to bone stock and get it replaced. If anyone else knows how to get it fixed, my best guesses would be mt or S.Meezy, though adb that might work. I hope it all gets figured out. Someone needs to post stock GB without data or anything for people to flash to if need be. That might fix your issue.
My suggestion is to get the recover the whole phone...
http://forum.xda-developers.com/showthread.php?t=1211295
follow that but use the v6 TOT file. That will revert the phone to out of factory new, with updated radios. If you still have the issue then I would contact Verizon.
If everything works then you can re-run the update to Gingerbread.
Could be a long shot but I remember seeing something a little way back in another forum where a user w the same problem accidentially resolved his issue by restarting w the sd card out. For him it turned out to be a bad or incompatible sd card at the root of the problem.
If you have one in, pull it and restart. Hope thats it for you...
Sent from my VS910 4G using XDA App
Well i'm a glutton for punishment so i'm back.
I didn't want to bother with rooting it honestly but I did it out of desperation, figured a total wipe + brand new Rom would surely fix things.
Going to attempt the full recovery.
Tried pulling the SD card, than just the Sim card and finally without anything and none of the combinations worked.
Have you tried downloading a stock ROM to your PC/Mac and dropping that on your SD card and then flashing that ROM, after checking the md5? To me it sounds like your gf just had a bad download.
I think the issue is that you keep trying to flash the bad bits. Just my two cents...
Sent from my Dell Streak 7 using Tapatalk
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Haxcid said:
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Click to expand...
Click to collapse
What he said.
Remember: Absolutely do not, under any circumstance, unplug/turn off your phone once you start that process. It can take awhile, and might look like it froze, but just let it do it's thang.
I have a note 3 that I'm trying to get Cyanogenmod 11 on to. I should note that I got this working with my Droid Razr earlier today using the exact same process. I get to the point where I flash the rom and it only takes like 5 seconds then says "successful". When I boot the rom I just get a black screen that I have to hold the power button down to get out of. My note 3 is running 4.4.2 I have root and busybox is installed. I've tried safestrap 3.72 and 3.75. I've even tried the stock slot (and then reverted back when it didn't work). I'm out of things to try and I can't find anyone else who has had a similar issue. Anyone got any ideas?
If its an N900A or N900V, you can only run TW based roms because the bootloader is locked.
andygev35 said:
If its an N900A or N900V, you can only run TW based roms because the bootloader is locked.
Click to expand...
Click to collapse
How are people getting cyanogenmod 11 on their att note 3s if not through safestrap?
I don't know of anyone with an at&t note 3 running CM. It's possible they're using an N900T, or an N9005 Note 3 on at&t.
andygev35 said:
I don't know of anyone with an at&t note 3 running CM. It's possible they're using an international note 3 on at&t.
Click to expand...
Click to collapse
Well that's sad. I'm assuming any of these will work in the meantime? http://forum.xda-developers.com/note-3-att/#romList
They should, just make sure if you're on KK to choose a KK rom.
noob over here needing help
i have the ATT Note 3 with the locked bootloader. i cant rememeber the model name but i think its like I900A. anyway i have had it rooted for about 5 months or so and i have had safestrap and busybox and use Xposed wanam. also using twrp and titanium backup. well i have never flashed anything on it cuz ive always been sketched out with the locked bootloader and not being able to flash kernals and all that. so yesterday i figured i would try one out and see if i could get it. i used the "S5 Experience" rom and i downloaded it from MEGA onto my ext. SD under a new folder i made called "s5 experience". i then went into recovery mode through safestrap and went to "backup" and then made a backup of data, cache, and system. after that i went to "wipe" and did a factory reset/wipe. when that was done i went to "install" and found my "s5 experience" on my ext. SD and installed it. when that was done i rebooted my device and it popped up with the samsung note 3 emblem and under it the little lock underneath it in the unlocked position just like it always has. then went to safestrap with the little red robot and "safestrap: disabled" like always. so i hit continue and from there is when my problem started. the blue LED light on the top left turned on and stayed on but the screen stayed black. this is the problem i am still having right now. if i press the power button it will vibrate or double vibrate and eventualy if i hold it down i can get it to restart. after that i went into recovery again and tried to restore from my backup i had made just earlier. when i try that it goes for a while and then will eventually say that restore has failed. ive mesed with some of the settings and stuff in the twrp recovery interface but not much because im new and not sure what i should and should not be doing. so i started looking here. i didnt find any help on the S5 Experience forum and i havent found and other forums that have this problem except maybe this one. so i am asking for help, if someone would be so kind as to walk me through how to fix my phone and what i did wrong it would be greatly greatly appreciated. if at all possible i would love to keep all of my pics and apps and stuff but if that is not possible then i wont complain if i have to lose it all. i would be happy just to have a working phone again. thanks in advance and sorry if i have posted this in the wrong place.
sethers said:
i have the ATT Note 3 with the locked bootloader. i cant rememeber the model name but i think its like I900A. anyway i have had it rooted for about 5 months or so and i have had safestrap and busybox and use Xposed wanam. also using twrp and titanium backup. well i have never flashed anything on it cuz ive always been sketched out with the locked bootloader and not being able to flash kernals and all that. so yesterday i figured i would try one out and see if i could get it. i used the "S5 Experience" rom and i downloaded it from MEGA onto my ext. SD under a new folder i made called "s5 experience". i then went into recovery mode through safestrap and went to "backup" and then made a backup of data, cache, and system. after that i went to "wipe" and did a factory reset/wipe. when that was done i went to "install" and found my "s5 experience" on my ext. SD and installed it. when that was done i rebooted my device and it popped up with the samsung note 3 emblem and under it the little lock underneath it in the unlocked position just like it always has. then went to safestrap with the little red robot and "safestrap: disabled" like always. so i hit continue and from there is when my problem started. the blue LED light on the top left turned on and stayed on but the screen stayed black. this is the problem i am still having right now. if i press the power button it will vibrate or double vibrate and eventualy if i hold it down i can get it to restart. after that i went into recovery again and tried to restore from my backup i had made just earlier. when i try that it goes for a while and then will eventually say that restore has failed. ive mesed with some of the settings and stuff in the twrp recovery interface but not much because im new and not sure what i should and should not be doing. so i started looking here. i didnt find any help on the S5 Experience forum and i havent found and other forums that have this problem except maybe this one. so i am asking for help, if someone would be so kind as to walk me through how to fix my phone and what i did wrong it would be greatly greatly appreciated. if at all possible i would love to keep all of my pics and apps and stuff but if that is not possible then i wont complain if i have to lose it all. i would be happy just to have a working phone again. thanks in advance and sorry if i have posted this in the wrong place.
Click to expand...
Click to collapse
If you can boot to stock recovery (power+home+volume up) NOT safestrap recovery do a factory reset from there. That'll reflash stock rom and you can reroot + busybox + SS. Make sure to check what build you are on as well - if you are on NC2 kitkat you can only flash kitkat-based roms.
Sethers, please do not hijack and do not double post your questions in multiple threads.
graydiggy said:
Sethers, please do not hijack and do not double post your questions in multiple threads.
Click to expand...
Click to collapse
sorry graydiggy. this seemed like a thread that had something to do with the same black screen i was getting. besides this one i only posted it on the stupid questions thread.
---------- Post added at 01:56 PM ---------- Previous post was at 01:51 PM ----------
brisinger08 said:
If you can boot to stock recovery (power+home+volume up) NOT safestrap recovery do a factory reset from there. That'll reflash stock rom and you can reroot + busybox + SS. Make sure to check what build you are on as well - if you are on NC2 kitkat you can only flash kitkat-based roms.
Click to expand...
Click to collapse
brisinger08, thanks for the input. i was running kit kat. i figured the s5 experience would be based off of kitkat too but i guess i should have checked first. i just tried that. when i got into the recovery boot the little android guy falls over. then i went to factory wipe and let it wipe. after that i went to reboot. when it rebooted it still had the little lock under the Samsung logo and after that screen it went straight to safestrap again. it hasn't seemed to change anything as far as i can tell. any other ideas?
sethers said:
sorry graydiggy. this seemed like a thread that had something to do with the same black screen i was getting. besides this one i only posted it on the stupid questions thread.
---------- Post added at 01:56 PM ---------- Previous post was at 01:51 PM ----------
brisinger08, thanks for the input. i was running kit kat. i figured the s5 experience would be based off of kitkat too but i guess i should have checked first. i just tried that. when i got into the recovery boot the little android guy falls over. then i went to factory wipe and let it wipe. after that i went to reboot. when it rebooted it still had the little lock under the Samsung logo and after that screen it went straight to safestrap again. it hasn't seemed to change anything as far as i can tell. any other ideas?
Click to expand...
Click to collapse
If you're on the A3 bootloader then reflashing NC2 with odin will clear this up, (double-check in download mode) then follow the instructions in this thread. If you're on A2 you can still do this but it will overwrite your bootloader and lock you into NC2 so if that's the case you might want to read through that thread to make sure you're ok with that!
Delete
Peeptastic said:
I think this might fix the issues I have. If I can sideload the latest update, wouldn't that unfreeze previously frozen apps? Thanks.
Click to expand...
Click to collapse
It will not unfreeze them. You will need to factory reset.
Delete
Peeptastic said:
Okay, thanks. Factory reset is what got me in this in the first place. (Well, not the first place, but it's what I can't get out of!) is not changing anything. I still can't get any further in setup than one screen past wifi (it just continues to check whatever it is it's checking. It's not frozen and it doesn't loop, it just doesn't move on. Pressing next/skip produces a sound/feedback but doesn't move on) Oh well, it was worth a try.
Click to expand...
Click to collapse
If you're rooted, factory reset will not work. You will need the KDZ file to wipe your phone, which is currently in the works.
If you actually got it to boot, then you're fine. That "activating" screen sometimes takes several minutes. Just be patient.
Delete
Peeptastic said:
Thank you for helping. I don't actually make it to an activating screen. I just get one step past wifi (if I keep wifi on it gets caught in updating system. If I turn wifi off it gets caught in just a sec). It will "load" (lack of better term) for 1-3 hours. I did discover that I can receive phone calls while stuck in the screen. And I can hear when I get a text message, although I can't check it. But that makes sense if I can't factory reset a rooted phone....
Click to expand...
Click to collapse
Try removing battery and trying to boot again. If your phone was rooted, that''s possibly your problem.
Delete
Peeptastic said:
I'm not sure if the batter y is supposed to be out for an extended period of time. Or plugged in(?) I have done that as well as remove the sim card. No progress.
Oh and data works as well though I don't always have good reception where I'm at.
Click to expand...
Click to collapse
So what you're saying is that you're still stuck on that screen, but all of the phones functions work? Hm, that is very strange.
Sent from my LGLS991 using Tapatalk
Delete
Peeptastic said:
Yep! Sprint connections optimizer popped up. I was able to hit a link from there and access chrome. I wasn't signed in to wifi though. Also, whenever something closes, the screen goes back to setup. I don't have access to the task bar or the soft keys (besides back). Someone else on the forum had a similar problem and looks like it was solved with kdz. So there is hope.
Click to expand...
Click to collapse
I suppose you'll just have to wait for the KDZ. I have never heard of anything like that before. I'm sorry that happened.
Sent from my LGLS991 using Tapatalk
ironbesterer said:
I suppose you'll just have to wait for the KDZ. I have never heard of anything like that before. I'm sorry that happened.
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
You and me both, you and me both....
Peeptastic said:
You and me both, you and me both....
Click to expand...
Click to collapse
I'm just waiting for that bootloader unlock and custom recovery ?
Sent from my LGLS991 using Tapatalk
Delete
Peeptastic said:
Thank you for helping. I don't actually make it to an activating screen. I just get one step past wifi (if I keep wifi on it gets caught in updating system. If I turn wifi off it gets caught in just a sec). It will "load" (lack of better term) for 1-3 hours. I did discover that I can receive phone calls while stuck in the screen. And I can hear when I get a text message, although I can't check it. But that makes sense if I can't factory reset a rooted phone....
Click to expand...
Click to collapse
I think I may be seeing something related to what you're seeing (though I'm not starting over from a Factory Reset). Ever since taking the root flash, my wifi isn't connecting to my home router anymore.
I was just about ready to do a Factory Reset to see if that fixed it, but now it doesn't look like that'll help.
Delete
Peeptastic said:
I wouldn't recommend resetting unless your device has kdz or a custom recovery access. What carrier are you on?
Click to expand...
Click to collapse
Sprint.
---------- Post added at 09:16 AM ---------- Previous post was at 09:08 AM ----------
Peeptastic said:
Okay, thanks. Factory reset is what got me in this in the first place. (Well, not the first place, but it's what I can't get out of!) is not changing anything. I still can't get any further in setup than one screen past wifi (it just continues to check whatever it is it's checking. It's not frozen and it doesn't loop, it just doesn't move on. Pressing next/skip produces a sound/feedback but doesn't move on) Oh well, it was worth a try.
Click to expand...
Click to collapse
During the initial setup after factory reset, when you get to the wifi setup screen can you just skip over the wifi setup? Is it possible your wifi isn't working (mine isn't either) and as long as you keep attempting to connect you'll never get past that step in the initial setup process?
i need zv4 rooted system file, i'll root the phone using the zv4 file and will do OTA , thn will get the update.zip for ZV5.
if any one have zv4 rooted system file pl share.
Delete
Peeptastic said:
I've tried that. It just hangs on that screen as well. It's a google services error. Can't be fixed without more resources. (That I know of). It connects to data and still won't move on. Though my data is really slow here so who knows if there was any progress....
As for your phone, I wouldn't try factory reset until we get that tot file.... Otherwise, you might be joining the rest of us with Sprint bricks :highfive:
Click to expand...
Click to collapse
Roger that, sir.
What's a "tot" file?
[QUOTE=oldjackbob;621036
Delete
Hey there everyone, here to report unfortunate news about my g4 has died all out. Was using it to navigate using maps to a job yesterday, when suddenly my phone reboots and gets in boot loop. I take off battery to boot up phone back on, but turns out it doesn't at all respond to turn on, I try the hard master reset buttons to then boot to twrp but not even that responds. Weird cuz I had 40 percent battery left, connected phone to my charger and three more and no response at all in boot up or even sign of life. What can I do?
I have the same problem, phone wont respond at all and it was doing a boot loop, now it just wont turn on or respond to charging/no led light, nothing.
What are my options?
Rooted/No Insurance.
ExhumedWolf said:
I have the same problem, phone wont respond at all and it was doing a boot loop, now it just wont turn on or respond to charging/no led light, nothing.
What are my options?
Rooted/No Insurance.
Click to expand...
Click to collapse
That's weird how this has happened when i was running completely stock rom 10n rooted. Sucks that my screen has a very thin hairline crack which T-Mobile told me that LG won't accept it for warranty since it has physical damage.
Is there a way to restore the phone to complete stock using download mode? I'm in the same boat and now need to research a solution before returning to T-Mobile. This happened to a friend, too.
In my case, I was playing Fallout Shelter, the phone froze, so I did a battery pull. Now it won't boot up. Sometimes I can get it to go as far as the "Android is upgrading screen, " but then it either freezes again or goes into a bootloop. Tried booting into TWRP, but it either won't, or it'll freeze while inside before I can attempt to restore a backup or anything.
partylikeaninjastar said:
Is there a way to restore the phone to complete stock using download mode? I'm in the same boat and now need to research a solution before returning to T-Mobile. This happened to a friend, too.
In my case, I was playing Fallout Shelter, the phone froze, so I did a battery pull. Now it won't boot up. Sometimes I can get it to go as far as the "Android is upgrading screen, " but then it either freezes again or goes into a bootloop. Tried booting into TWRP, but it either won't, or it'll freeze while inside before I can attempt to restore a backup or anything.
Click to expand...
Click to collapse
Tried to boot in download mode and haven't been able since this occured. Nothing at all works for me in booting up to anything through the buttons, hopefully you can get DL mode working so you can get your g4 working back to normal.
wadamean said:
Tried to boot in download mode and haven't been able since this occured. Nothing at all works for me in booting up to anything through the buttons, hopefully you can get DL mode working so you can get your g4 working back to normal.
Click to expand...
Click to collapse
When I tried, I was able to boot into download mode, I didn't have any KDZ or whatever downloaded already or the flash tool in order to actually do anything so it was pointless, but it appears to boot into DL mode with no issue. For all I know, though, even though it booted into DL mode, it could have been completely frozen and unresponsive.
I think I found a thread with instructions and a link to the KDZ I need to download. Going to give this a try when I get home from work in twelve hours. If that fail, it's off to T-Mobile I go....
I have the same issue. I was browsing G+ then the phone just froze and now I can't get it to boot up or get into twrp. It will only boot loop.
Edit 1: I got my phone to boot and did a factory reset but it just ended up freezing and rebooting just like before. I'm going to try and get into twrp and flash the 10n stock then go to t-mobile to try and get them to get me a new one. I have insurance but the phone just randomly died, no dropping, didn't get it wet, so I don't want to have to pay a deductible.
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
mr turtle droid said:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
Click to expand...
Click to collapse
Thanks for the reminder. That's the thread I found and I also already made a mental note to flash the right image. My friend had this same problem and the person she tasked with fixing her phone flashed the wrong image and perma bricked her. Fortunately, T-Mobile still replaced her phone, though.
Sent from my LG-D851 using Tapatalk
mr turtle droid said:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
Click to expand...
Click to collapse
That's true and I have not flashed nothing at all and only remained all on 10n rom and bootloader and modem. Yet this still happened to me.
My phone lives!
partylikeaninjastar said:
My phone lives!
Click to expand...
Click to collapse
That's amazing news!!!!
Actually, I take it back. It stopped working after an hour and started doing the same thing. On my way to T-Mobile in a bit.
Sent from my LG-D851 using Tapatalk
partylikeaninjastar said:
My phone lives!
Click to expand...
Click to collapse
partylikeaninjastar said:
Actually, I take it back. It stopped working after an hour and started doing the same thing. On my way to T-Mobile in a bit.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
WillDeC said:
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
Click to expand...
Click to collapse
No hassle at all. Surprisingly. He just asked me what happened, then ordered my replacement to be delivered. Will have a new phone on Tuesday.
Sent from my LG-D851 using Tapatalk
WillDeC said:
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
Click to expand...
Click to collapse
I have great news everyone! Today I was cleaning my room. And just moved my g4 around onto my bed and then I see that the screen comes on saying I need to charge it. Which then I plug in and it charges now. I then wait a good while, get it to magically boot onto twrp. So excited and only option was to wipe all except the storages. I did, then flashed 10n rom again, not its back to life with no issues. Need to go to T-Mobile to connect it back on.
partylikeaninjastar said:
No hassle at all. Surprisingly. He just asked me what happened, then ordered my replacement to be delivered. Will have a new phone on Tuesday.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Good to hear. I just want to try and get it to stock. Sometime I can get to boot twrp and don't want to have to deal with them questioning about if they try and factory reset it or something.
WillDeC said:
Good to hear. I just want to try and get it to stock. Sometime I can get to boot twrp and don't want to have to deal with them questioning about if they try and factory reset it or something.
Click to expand...
Click to collapse
Reason why this issue has occurred is most likely in my opinion because of xposed. There is versions that work and those that aren't so stable in certain devices. What I advise you to do is boot into twrp when you get the chance, wipe all except the storages. You will notice how stable the phone gets and won't be bootlooping, which is what I noticed. Then flash whatever rom you have. Boot up, skip all intro steps, download the zip to get it to stock so you get the replacement. Keep telling T-Mobile that maybe at the moment it seems stable but it does this and you have gotten so fed up with it and won't be leaving until a replacement takes place. Either warranty or at store.
wadamean said:
Reason why this issue has occurred is most likely in my opinion because of xposed. There is versions that work and those that aren't so stable in certain devices. What I advise you to do is boot into twrp when you get the chance, wipe all except the storages. You will notice how stable the phone gets and won't be bootlooping, which is what I noticed. Then flash whatever rom you have. Boot up, skip all intro steps, download the zip to get it to stock so you get the replacement. Keep telling T-Mobile that maybe at the moment it seems stable but it does this and you have gotten so fed up with it and won't be leaving until a replacement takes place. Either warranty or at store.
Click to expand...
Click to collapse
I've never put xposed on this phone. I put twrp, rooted and was using a debloated rom. I had actually removed root so I could use android pay. It was working fine then just froze and constant reboots and freezing. I've only been able to get into twrp once without it freezing and rebooting,
WillDeC said:
I've never put xposed on this phone. I put twrp, rooted and was using a debloated rom. I had actually removed root so I could use android pay. It was working fine then just froze and constant reboots and freezing. I've only been able to get into twrp once without it freezing and rebooting,
Click to expand...
Click to collapse
You shouldn't have removed root and just used root cloak so that android pay thinks your unrooted. That's what I have been using. Because debloated roms always come injected with root and at times it becomes their core use within to function. When you get the chance to boot into twrp. Wipe all except storages and then reflash.
So I was running the hyperdrive 4.4.4 for for well over a year with no issues. Then about 2 weeks ago, it randomly shut down and bootlooped. Once it finally booted back into the rom, it would lag, freeze, bootloop, and then randomly boot into download mode, or Recovery. So after going back to a clean install of hyperdive, it would still act erratic. So I went back to stock, same problems. I then changed recoveries (from twrp to philz) and it stopped freaking out for a bit, then started again. So i clean installed 4.4.4 and still problems. So I clean install hyperdrive with philz (after the appropriate steps) and still have problems. So then I odin'd to official 5.1.1 (which might have acted as an in place upgrade)and I'm still having freezing problems. Sometimes I have to go into download mode and reboot from there just to boot into the os.
Help please?
EDIT: when it fails to boot, and goes into download mode it says "ddi : mmc_read failed."
the phone is also carrier unlocked and being used on cricket.
internal memory issue?
From the mmc_read error it sounds like the internal memory in your device is maybe starting to go out. That's the only thing I could think of. It is curious though that it will randomly boot the recovery and download partitions which I am fairly certain reside on the same internal memory. Maybe blocks in your system partition are going bad causing it to not read and boot to your 2 repair partitions to fix the problem.
---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------
Though if the flash memory is going bad there's not much to be done about it
Ended up buying a v10 until I could figure out this problem.
long story short - you're screwed.
MRguyandhis2 said:
Ended up buying a v10 until I could figure out this problem.
Click to expand...
Click to collapse
Try this:
Step 1. Download Wake Lock from the Play Store
Step 2. Enable Partial_Wake_Lock (number 4)
Step 3. Enable Auto-Start
Just found this, thought you might find some use from it. Good luck. http://forum.xda-developers.com/note-4-tmobile/help/fix-mmcfailed-internal-memory-yes-t3277144
TardisJacker said:
Just found this, thought you might find some use from it. Good luck. http://forum.xda-developers.com/note-4-tmobile/help/fix-mmcfailed-internal-memory-yes-t3277144
Click to expand...
Click to collapse
Unfortunately the solution in that thread doesn't work. it's just working on the SD card partition, not the internal memory itself.
OP is screwed, just like I was, just like plenty of others here. **** samsung and their ****ty quality control on an otherwise brilliant phone
dtrinh4000 said:
Unfortunately the solution in that thread doesn't work. it's just working on the SD card partition, not the internal memory itself.
OP is screwed, just like I was, just like plenty of others here. **** samsung and their ****ty quality control on an otherwise brilliant phone
Click to expand...
Click to collapse
ive had the s3, s4. s5, note 2. note 3, and note 4. This is the only phone that I have ever had this kind of problem. it truly sucks.