Related
Hi i have a bell galaxy s i just flash ugkc1 firmware but when the phone boots i get force close message for almost every app.
i think the internal sd might be corrupted tried to format it but all files are still there
any idea ??
thank you
your SD card usually nothing to do with application force close, those files which you see after formatting on SD card should be there so do not worry about them.
if you want to find the reason explain about your previous rom and kernel. did you do a factory reset or wipe before and after rom installation?
Here is two simalar topics. I also have that problem and cannot solve it yet.
http://forum.xda-developers.com/showthread.php?t=1076101
http://forum.xda-developers.com/showthread.php?t=1069867
When i looked in internet i found sth similar for HTC, but devs corrected it. They parted some files from working devices and pushed it to system with adb.
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
Maybe sth like that will also solve our problem but we need help.
If you find any sollution please infrom us. Maybe it will be useful for us too.
Regards
thanks for your replies
all this strated when i updated to 2.3 with kies using spooffw upgrade went fine but phone didn't boot it was stuck on the first boot screen,
so i flashed back to 2.2 and here i am ..
Did you try booting twice or did you jump the gun flashing back? My phone appeared to be stuck during the first boot screen on the first time starting 2.3.3.
garbz said:
Did you try booting twice or did you jump the gun flashing back? My phone appeared to be stuck during the first boot screen on the first time starting 2.3.3.
Click to expand...
Click to collapse
i tried booting twice it ddn't work recovry mode didn't work either
now im back on froyo i still can use the phone but only as a phone all apps fail to start and i get force close message
flashed my phote to 2.3 (jvk) ans i installed speed mod... still the same
im pretty sure its an internal sd failure. is there any way to fix this ? i bought my phone some guy on kijiji so i don't think i have any warranty..
thank you
biscuit26 said:
flashed my phote to 2.3 (jvk) ans i installed speed mod... still the same
im pretty sure its an internal sd failure. is there any way to fix this ? i bought my phone some guy on kijiji so i don't think i have any warranty..
thank you
Click to expand...
Click to collapse
I doubt it is an SD problem. Go to recovery, clear cache and dalvik and fix permissions. If the problem persists to a factory reset and reinstall your apps from the market.
Sent from my GT-I9000 using XDA Premium App
thanks again for tryin to help i already tried this but didnt work
Edit :
flashed back to stock 2.2.. now i get ''blank internal sd'' on the notification bar. phone doesn't seem to detect internal sd card is this a hardware or software problem ?
thanks
now i flashed sppedmode kernel phone seems to be running a little better ( less force closes messages) but i still can't delete files or format my sd card
any idea ?
I tried to flash darky 9.2 (odin version). Then i reach with ADB to the internal when it is in CWM. I pushed there some custom roms and flashed with CWM. But it did not help either.
isn't there any way to fix a corrupted sd card ?
This is yet another thread on an GT I9000 stuck at boot, but with a twist!
The diference is that it hapened without me doing anything to it. No flashing roms, no rooting, no unlocking, nothing.
One day it turned itself off, turned on again, get pass the initial screen, gets pass the carrier animation, and it is stuck at the big shiny S screen.
I'm not new to XDA or to flashing (old windows mobile), so I decided to come here and look as usually I can find my answers. The thin is it seems no one else has a similar problem! Not here nor the entire web!
I've been searching and experimenting (it doesn't work anyway, so it is ok to test every solution) for 2 consecutive weeks and still nothing!
I am able to get into download mode, into recovery mode, I am able to flash rooted (or rooting) kernels, I can do everything (except update from SD card with Cyanogenmods, it always says the file is BAD).
I've flashed stock roms, following all the procedures, with Odin, with Heimdall, I've tried everything suggested by "Android Solutions" but nothing!
I'm really frustrated, so I'm reaching to see if there's someone that can shine some light on how to solve this... I feel I'm about to smash the thing with a hammer! (but this won't solve the problem, right...)
Thank you in advance
G
GAlves said:
(except update from SD card with Cyanogenmods, it always says the file is BAD).
Click to expand...
Click to collapse
I assume you had rooted and had CWM when trying to flash CM from SD cards? if not, it will not work, using 2e or 3e recovery
First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.
Also assume you had tried everything in My Android Solutions did not get you out of bootloops?
so, boot into CWM > mounts and Storage> to copy your entire SD card to PC, after which you should format every partition (you will in-effect lose everything by doing this,) and do not reboot
after this, you must pull out battery and powerup into download mode to flash JVU+Root ROM with 512 PIT (repartition and update boot loader ticked in odin3) from My Android Collections
Hi xsenman,
Thank you for the reply.
in fact, I tried to CM from the SD card after having flashed CWM rooted kernel with Odin, but at this point the phone was not booting anymore. The whole reason I wanted to flash it in the first place was because it started bootlooping by itself while completely stock.
So I came here to xda, and follewed the instructions. I thought it would be a simple matter of flashing with a new rom and everything would be a-ok. It didn't.
I've tried every single trick mentioned in "my android solutions" (great information repository by the way, lots of work there) and still nothing. Today when I get home (forgot the phone at home) I'll flash the stock everything and try to follow the SD format procedure you mention.
I'll post back
Cheers
G
Hi again,
I've tried xsenman's suggestion and still nothing.
I could understand if this was a SD card error (because it was damaged in some way), but I have no indication of a SD card error. It can read everything and I even can see the file structure inside the SD card (and I do not mena the external SD card ofc). I was even able to copy some files to and from it!
I think I'll "fix it" with a big hammer and buy me an iphone! This is soooo frustrating!
anyone has any other ideas? I'll try anything and everything.
Cheers
G
GAlves said:
in fact, I tried to CM from the SD card after having flashed CWM rooted kernel with Odin, but at this point the phone was not booting anymore.
Click to expand...
Click to collapse
CM needs to be flashed twice, try this method or this
Check Here to chose your forum/Guide by Version of your phone or you will have more problems by using wrong solutions due to different versions of Galaxy S
Use only ROM and solution for your model and Wipe x3
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
(Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.)
Hi again,
Tried everything and got always the same result. Nothing.
Maybe the problem was with some piece of hardware (but I find it strange). As I said before I firstly tried to flash it because it had come to a bootloop by itself so maybe it had a deeper problem.
Now I got it solved. I bought me a brand new iPhone 5 (LOL) and flashed a stock rom on the SGS and sent it to the carrier customer support. It had one year guaranty. Lets see what they say about it.
If they can solve it I'll have 2 very nice phones!
Thank you anyway for you help.
Had same problem some time ago.
THIS should help you too
Hi again!
I had tried that too, and the result was the same as all the other things I've tried. Nothing.
Today I had some feedback about the phone (I sent it to repair). The phone is on its way back to my hands, and the repair status says:
"Software update and power circuit repair. Tested OK".
Let's see if it does tests ok when I get it back!
Two weeks ago I got an e-mail from the tech support asking what was wrong with the phone because they could find nothing wrong with it. I asked them to turn it on and try to make a phone call for example, or connect to a wi-fi network. It doesn't really matter, I just wanted them to try to do something that involved turning it completely on and use the device in any way they wanted. Clearly they hadn't even tried to turn it on. Otherwise they would have figured out that there was a problem...
This was the carrier support, not Samsung (I think). Anyway it SUCKS bigtime!
Now I need to figure out what to do with it...
Thanks anyway for your support!
Cheers
G
Just to let people know how this ended up.
My SGS i9000 went to the repair shop for two times. The first they replaced the charger plug, the second they say they replaced nothing (but I don't belive them )
As I still think this was some sort of issue with the samsung firmware, I just flasher CM10 and it's been stable since then.
My girlfriend got it as a present and she's quite happy with it!
Thank you all for the help!
So, to make a long story, short, for the past couple of days my phone has been soft-bricked... It first happened when I attempted to flash dmodv6 in CWM. Everything looked good throughout the installation, however, when I rebooted my device, I got stuck in a boot loop where It would say "Samsung Galaxy S III GT-I8190" for a few seconds, the screen would go black, then say the same thing again... over and over and over...
After a lot of trial and error because of NOT making a nandroid backup via CWM (stupid, I know - I had made one via Titanium Backup and thought that might be good enough), I finally was able to boot. Thanks to xXPR0T0TYPEXx, I was able to flash another rom by puting my external sd card into another phone, loading another rom onto it, and putting it back in my phone. I now had Cyanogenmod10 and was able to boot back up.
I attempted to restore the Titanium Backup I had made with this new rom (stupid again, I know) and it made almost every service on the phone stop working... I desperately wanted just to get back to square one - to install stock firmware and go from there. I followed tys0n's guide on flashing stock recovery then attempted to install stock firmware... All seemingly went well - I booted up, got past the initial "Samsung Galaxy S III GT-I8190" logo and finally got hung up at the "Samsung" logo. I left it one while I went to sleep, just to see if it would eventually work... I woke up and it was still the same. I tried flashing different version of the same stock firmware but it all ended in getting hung up at the "Samsung" logo.
A major problem is that I absolutely CANNOT flash a custom recovery via Odin - it just will NOT work. Everything looks good on Odin's end - I PASS, get the (succeed 1 / failed 0) thing but am sent to stock recovery every time I do the 3 button combination. I've tried many version of CWM and TWRP.... NOTHING. I've even unticked the "Auto-Reboot" button in Odin and pulled the usb cable and battery upon completion but, but nothing ever works. The only way I was ever able to get CWM on my phone in the first place was by an in-phone app... Rom Manager, maybe? I can't remember. But, as it is, that method is out of the question.
I've learned a lot about what I did wrong so that's the only good part of all of this. Now, all that's left is to fix the thing so I can go about it right. I'm completely out of ideas, have spent almost a full 24 hours searching solutions to this problem and I am at wits end...
I just want to get back to stock firmware... Any ideas, guys? Should I go about re-partitioning my device at this time?
I have the PIT file... but I'm not sure as to which firmware to choose. I imagine a firmware that is 4.1.1 like my phone was... but I'm not sure about the region. I live in the US and there is no US or North American region firmware version.Can anyone shed some light on which one I should choose?
My SSN underneath my battery say "GTI8190GSMH".
I'm sorry this is so long, I just wanted to explain what happened as best as I could. So, should I go about re-partitioning my device at this point? If so, what firmware would you recommend for my model? Are different region versions okay for a this method?
Or is there another way?
Thanks, guys. :silly:
Some additional details (if it will help): I can, indeed, boot into both recovery and download mode. I just can't seem to flash a stock rom that will boot past the "Samsung" logo.
I've even attempted to flash the param file after the rom flash but it didn't help.
AffectiveEffect said:
Some additional details (if it will help): I can, indeed, boot into both recovery and download mode. I just can't seem to flash a stock rom that will boot past the "Samsung" logo.
I've even attempted to flash the param file after the rom flash but it didn't help.
Click to expand...
Click to collapse
Do you have the stock recovery now instead CWM? If yes do (if you didn't try it) a factory/data reset and wipe cache but it will delete your pics, music etc on your internal storage too.
xXPR0T0TYPEXx said:
Do you have the stock recovery now instead CWM? If yes do (if you didn't try it) a factory/data reset and wipe cache but it will delete your pics, music etc on your internal storage too.
Click to expand...
Click to collapse
Yeah, I have stock recovery now and I have tried that many, many times... Even if I install something like CyanogenMod, it still gets hung up on the CyanogenMod boot screen... And if I boot a stock firmware, it gets hung up at the same place at the "Samsung" logo...
I have an idea that one of the only options left is a PIT re-partitioning... If so, how would I properly go about that? Load the PIT file and the stock firmware in odin? Or only the PIT as PDA? I've heard a couple of different things and am unsure.
AffectiveEffect said:
Yeah, I have stock recovery now and I have tried that many, many times... Even if I install something like CyanogenMod, it still gets hung up on the CyanogenMod boot screen... And if I boot a stock firmware, it gets hung up at the same place at the "Samsung" logo...
I have an idea that one of the only options left is a PIT re-partitioning... If so, how would I properly go about that? Load the PIT file and the stock firmware in odin? Or only the PIT as PDA? I've heard a couple of different things and am unsure.
Click to expand...
Click to collapse
I don't know about PIT files but some people got this message : "CUSTOM PIT BINARY" in recovery mode after flashed a PIT file (maybe they used a other PIT file that wasn't compatible). So make sure you use a PIT file that is GT-i8190 compatible.
I tried flashing the PIT file for the hell of it because I am completely out of ideas.... It failed repeatedly in Odin.
I have no clue on how to fix this... I've tried countless roms and they all get stuck on their respective boot screens. The only one that gave me a glimmer of hope was Cyanogenmod10.2.... It went as far as saying "Android is upgrading" and showed "starting apps" but it got hung up there.
I don't know what to do, guys. Someone help!!!
AffectiveEffect said:
I tried flashing the PIT file for the hell of it because I am completely out of ideas.... It failed repeatedly in Odin.
I have no clue on how to fix this... I've tried countless roms and they all get stuck on their respective boot screens. The only one that gave me a glimmer of hope was Cyanogenmod10.2.... It went as far as saying "Android is upgrading" and showed "starting apps" but it got hung up there.
I don't know what to do, guys. Someone help!!!
Click to expand...
Click to collapse
Use a custom ROM to see if it will fix the problem .Try to flash CyanogenMod 10.2 by NovaFusion via odin or if you flash CyanogenMod 11 then you will automatically get the TWRP recovery. NovaFusion Team Homepage : novafusion.pl. I know you want the stock ROM but try other ROMs to get a booting phone again
xXPR0T0TYPEXx said:
Use a custom ROM to see if it will fix the problem .Try to flash CyanogenMod 10.2 by NovaFusion via odin or if you flash CyanogenMod 11 then you will automatically get the TWRP recovery. NovaFusion Team Homepage : novafusion.pl. I know you want the stock ROM but try other ROMs to get a booting phone again
Click to expand...
Click to collapse
I have... I've tried numerous stock roms and numerous custom roms... all versions of Cyanogenmod, Chameleon, Carbon, Slim mod, etc... They all get stuck at their respective logos.
I even tried the Cyanogenmod with TWRP but, as I explained earlier, I absolutely CAN NOT flash a custom recovery unless I use what ever app I used.... It doesn't work with Odin or with a rom. I don't know why.
I wish someone had more info on repartitioning my phone and if it would help.
NEED HELP?
AffectiveEffect said:
So, to make a long story, short, for the past couple of days my phone has been soft-bricked... It first happened when I attempted to flash dmodv6 in CWM. Everything looked good throughout the installation, however, when I rebooted my device, I got stuck in a boot loop where It would say "Samsung Galaxy S III GT-I8190" for a few seconds, the screen would go black, then say the same thing again... over and over and over...
After a lot of trial and error because of NOT making a nandroid backup via CWM (stupid, I know - I had made one via Titanium Backup and thought that might be good enough), I finally was able to boot. Thanks to xXPR0T0TYPEXx, I was able to flash another rom by puting my external sd card into another phone, loading another rom onto it, and putting it back in my phone. I now had Cyanogenmod10 and was able to boot back up.
I attempted to restore the Titanium Backup I had made with this new rom (stupid again, I know) and it made almost every service on the phone stop working... I desperately wanted just to get back to square one - to install stock firmware and go from there. I followed tys0n's guide on flashing stock recovery then attempted to install stock firmware... All seemingly went well - I booted up, got past the initial "Samsung Galaxy S III GT-I8190" logo and finally got hung up at the "Samsung" logo. I left it one while I went to sleep, just to see if it would eventually work... I woke up and it was still the same. I tried flashing different version of the same stock firmware but it all ended in getting hung up at the "Samsung" logo.
A major problem is that I absolutely CANNOT flash a custom recovery via Odin - it just will NOT work. Everything looks good on Odin's end - I PASS, get the (succeed 1 / failed 0) thing but am sent to stock recovery every time I do the 3 button combination. I've tried many version of CWM and TWRP.... NOTHING. I've even unticked the "Auto-Reboot" button in Odin and pulled the usb cable and battery upon completion but, but nothing ever works. The only way I was ever able to get CWM on my phone in the first place was by an in-phone app... Rom Manager, maybe? I can't remember. But, as it is, that method is out of the question.
I've learned a lot about what I did wrong so that's the only good part of all of this. Now, all that's left is to fix the thing so I can go about it right. I'm completely out of ideas, have spent almost a full 24 hours searching solutions to this problem and I am at wits end...
I just want to get back to stock firmware... Any ideas, guys? Should I go about re-partitioning my device at this time?
I have the PIT file... but I'm not sure as to which firmware to choose. I imagine a firmware that is 4.1.1 like my phone was... but I'm not sure about the region. I live in the US and there is no US or North American region firmware version.Can anyone shed some light on which one I should choose?
My SSN underneath my battery say "GTI8190GSMH".
I'm sorry this is so long, I just wanted to explain what happened as best as I could. So, should I go about re-partitioning my device at this point? If so, what firmware would you recommend for my model? Are different region versions okay for a this method?
Or is there another way?
Thanks, guys. :silly:
Click to expand...
Click to collapse
i got same problem with you before im wayback dmod v6 before and stuck at samsung logo i just try hard reset
1. open your phone
2. remove battery and put the battery try and try til u get in recovery mode (CWM) maybe just tried almost 20x restarting in logo til u in CWM :victory:
3. re-Flash your dmod v6 this way for dirty rom like what i said (softbricks)
4. just flash another new rom whatever u like or dmod v6.
5. I HOPE IT HELPS DONT FORGET TO THANKS <3 :highfive:
Hi.
Since yesterday my galaxy s3 lte i9305 does not boot anymore, the blue cyanogenmod logo keeps turning for hours. I can however still go to the recovery (which was a few month old cwm). I completely wiped the phone (both caches, data, internal sd, boot, firmware etc ... all but the modem) and reinstalled the newest cwm and the newest nightly build three times now using heimdall and the external sd (connected my external micro sd to my computer sd card reader via adapter and put the zip on it). Just now I installed twrp-2.8.5.0-i9305 as a new recovery and installed everything again, but everytime - and also now - despite the seemingly successful installation, the phone is stuck at the cyanogen bootlogo.
Any ideas on how to get my phone running again?
Cheers
ScPo said:
Hi.
Since yesterday my galaxy s3 lte i9305 does not boot anymore, the blue cyanogenmod logo keeps turning for hours. I can however still go to the recovery (which was a few month old cwm). I completely wiped the phone (both caches, data, internal sd, boot, firmware etc ... all but the modem) and reinstalled the newest cwm and the newest nightly build three times now using heimdall and the external sd (connected my external micro sd to my computer sd card reader via adapter and put the zip on it). Just now I installed twrp-2.8.5.0-i9305 as a new recovery and installed everything again, but everytime - and also now - despite the seemingly successful installation, the phone is stuck at the cyanogen bootlogo.
Any ideas on how to get my phone running again?
Cheers
Click to expand...
Click to collapse
I would try a factory reset from recovery and see if that helps. You did check the md5 for your downloads right?
Otherwise I would install the stock rom, then try again, this time(making sure you have a compatible recovery) just wipe caches, data, and format system, and then install CM
noppy22 said:
I would try a factory reset from recovery and see if that helps. You did check the md5 for your downloads right?
Otherwise I would install the stock rom, then try again, this time(making sure you have a compatible recovery) just wipe caches, data, and format system, and then install CM
Click to expand...
Click to collapse
I did do the factory reset. I just wiped the areas separately as well. Anyway, I took your advice and installed the latest stock rom. Now I got the Samsung logo slightly flashing blue for hours instead of the cyanogenmod logo. Did not do anything else.
I suspect that its a battery issue in some way. The last weeks the phone lost its charge very quickly very often (not constantly though). Yesterday, the phone was in my pocket and then went off. It went into the constantly trying to restart despite the lack of batteries state until I removed the battery. Maybe that gives any clue?
ScPo said:
I did do the factory reset. I just wiped the areas separately as well. Anyway, I took your advice and installed the latest stock rom. Now I got the Samsung logo slightly flashing blue for hours instead of the cyanogenmod logo. Did not do anything else.
I suspect that its a battery issue in some way. The last weeks the phone lost its charge very quickly very often (not constantly though). Yesterday, the phone was in my pocket and then went off. It went into the constantly trying to restart despite the lack of batteries state until I removed the battery. Maybe that gives any clue?
Click to expand...
Click to collapse
Try booting into stock recovery, then factory reset from there. Last time I went back to stock I had a bootloop until I did this, then it booted properly. If that doesn't work, maybe try new battery.
Have you tried booting up whilst plugged in to a usb charger?
noppy22 said:
Try booting into stock recovery, then factory reset from there. Last time I went back to stock I had a bootloop until I did this, then it booted properly. If that doesn't work, maybe try new battery.
Have you tried booting up whilst plugged in to a usb charger?
Click to expand...
Click to collapse
Thanks for your helpful input.
I did what you said, even tried it twice now. Phone is still booting after 20 minutes now. I also tried booting up while charging the phone, yes. That was my standard procedure actually, but nothing changes when I unplug it. I don't have a different battery and I am wary of buying one just for the sake of trying. Tried that when my galaxy s 1 broke down and that didn't save the phone. At this point I am contemplating if the phone (s3) is broken now or not. It still reliably boots to the recovery, but it doesn't do much else. How are the chances?
Or has anyone any idea on how to proceed?
ScPo said:
Thanks for your helpful input.
I did what you said, even tried it twice now. Phone is still booting after 20 minutes now. I also tried booting up while charging the phone, yes. That was my standard procedure actually, but nothing changes when I unplug it. I don't have a different battery and I am wary of buying one just for the sake of trying. Tried that when my galaxy s 1 broke down and that didn't save the phone. At this point I am contemplating if the phone (s3) is broken now or not. It still reliably boots to the recovery, but it doesn't do much else. How are the chances?
Or has anyone any idea on how to proceed?
Click to expand...
Click to collapse
Try to boot into recovery. Do a factory reset then boot straight into download mode and flash stock rom. You might have to redownload the firmware it could be corrupted.. If that doesn't work then you might have to send it in. It might cost about to fix. Or go to your local phone repair shop and see if they could fix it for cheaper
Sent from my GT-I9305 using XDA Forums
my galaxy note 4 (sm-n910t) caught in bootloop . i dont know what caused it. the phone simply restarts upto first bootscreen, ie upto 'samsung galaxy note 4' and then vibrates and then restarts.this process continues upto battery is down or i pull out battery.the phone is not entering to recovery mode but enters to download mode.
i have tried installing stock rom from sammobiles but it won't help.i have also installed custom recovery twrp but that also won't help to enter to recovery mode,
i am trapped pls help..
You didn't mention how you tried to install the stock ROM . Did you use Odin?
I just fixed mine with the same issue. I was able to boot into recovery and download mode but mostly download mode without bootloop when I had the usb cable plugged in. I used ADB when I could to boot into download mode, but the buttons worked too. Trying to restart the phone only lopped after the Google screen.
I followed several guides here to flash stock with Odin and wipe cache etc but none solved my boot loop issue. almost gave up but there is a video on You Tube that said the battery warping in the cause of the boot loop. The battery, after/during quick charge, may heat up and change shape causing the issue. Today I installed my new battery purchased on amazon and no more issues.
Now I am on stock and have to find a good rom.
If you do decide to flash back to stock there are a lot of good guides. You may find yourself stuck on the T-mobile screen for 15 minutes when booting for the first time but that is ok. If you still boot loop after installing stock and wiping cache I would try the battery.
Nabeel mhd said:
my galaxy note 4 (sm-n910t) caught in bootloop . i dont know what caused it. the phone simply restarts upto first bootscreen, ie upto 'samsung galaxy note 4' and then vibrates and then restarts.this process continues upto battery is down or i pull out battery.the phone is not entering to recovery mode but enters to download mode.
i have tried installing stock rom from sammobiles but it won't help.i have also installed custom recovery twrp but that also won't help to enter to recovery mode,
i am trapped pls help..
Click to expand...
Click to collapse
hi OP,
did you find any solution to your problem?
Hello all. I'm also pasting this in the T-mobile thread in case it can be of benefit to someone. This is advice to use as a very last resort if you are experiencing the recovery bootloop issue AND you don't have the emmc failure bug. I had the recovery reboot, sudden shutdown with no warning, etc. issue for the past two weeks. I tried everything on Google and Youtube to fix my problem with no success. I flashed multiple stock ROMS and recovery tars (stock and TWRP) via ODIN, but nothing worked. Oddly enough, I never received the emmc error that I have read about. Also, in the few times that my phone booted normally, I even loaded the Wakelock Power Manager app, set it to partial wakelock and my phone STILL continued to bootloop. As a last resort, I bought a new battery, but the reboot problems continued in Android 4.4.4 Kitkat, 6.0 Marshmallow, 7.1 Nougat and 8.1 Oreo ROMS. Well, here is what finally helped me to get my phone back operational. I had a backup ROM from a previous install and a TWRP flashable version of the same ROM on my SD card (in case the phone did not stay on for the full restore). I put the phone into a ziplock bag into a freezer for about 20 min. (thankfully this time TWRP stayed on long enough for me to do the following):
1) copy all the files I wanted to save from internal storage to a computer.
2) performed a full wipe (Dalvic, Cache, System, etc. Like when flashing a ROM, but this time also internal storage. Note: Please do not wipe both internal and SD card, as you may have a difficult time trying to load the ROM file back on the sd card (assuming you don't have a card reader).
3) After wiping, I was able to restore my stock ROM backup (or you can just flash the stock ROM).
I can't be 100% sure, but I think my wiping internal and then flashing the stock ROM finally did the trick. Since this morning, the phone has been pretty much back to as it was before. In either case, I'm sharing this with the hope that it helps someone else.
Sent from my SM-N910T using Tapatalk
chrismcnally123 said:
I just fixed mine with the same issue. I was able to boot into recovery and download mode but mostly download mode without bootloop when I had the usb cable plugged in. I used ADB when I could to boot into download mode, but the buttons worked too. Trying to restart the phone only lopped after the Google screen.
I followed several guides here to flash stock with Odin and wipe cache etc but none solved my boot loop issue. almost gave up but there is a video on You Tube that said the battery warping in the cause of the boot loop. The battery, after/during quick charge, may heat up and change shape causing the issue. Today I installed my new battery purchased on amazon and no more issues.
Now I am on stock and have to find a good rom.
If you do decide to flash back to stock there are a lot of good guides. You may find yourself stuck on the T-mobile screen for 15 minutes when booting for the first time but that is ok. If you still boot loop after installing stock and wiping cache I would try the battery.
Click to expand...
Click to collapse
Thanks sir! I have the same issue! it's working now after replace the battery