Ok, so my fiancee's at&t note is stuck in a bootloop. I had it running on Blackstar, and since giving it to her hadn't bothered messing with the setup as it was stable. On her way home from work she apparently left the phone in her truck while making a stop in 92 degree weather(Farenheit). Now it will show both Samsung screens and then bootloop. I did some searching here on the forums and have tried everything I can find/think of. Here's a list of everything I've done:
1. Booted into twrp recovery, wiped data, cache, and sdcard for good measure.
2. Got to lockscreen, bootloop.
3. Used ODIN to push Samsung stock files onto phone, including recovery.
4. Got to AT&T easy setup screen, bootloop.
5. Used stock recovery to do hard reset.
6. Still bootlooping from second Samsung screen.
7. Removed back of phone, cleaned power button.
8. Still bootlooping.
I should note that the phone never booted itself after a battery pull, but I figured cleaning the power button couldn't hurt any.
Is there anything else I can try before going to at&t to have it fixed?
UPDATE: Thanks rangercaptain for that. I had totally forgotten Kies had the Firmware recovery. Unfortunately, it didn't work. And AT&T, well, we all know how they are about out of warranty phones. So I'm seemingly stuck, but I did have a thought. If the battery overheated, and malfunctioned, could it cause this? Would it be worth the 10 bucks to order a replacement OEM battery on Amazon and see if it fixes it?
Kies emergency firmware upgrade. Factory cable. Rear (powered) usb port on pc. Battery fully charged. Serial and model number under battery (all capital letters). Pray.
Don't quote, reply. If you quote, edit.
The battery try might be worth a shot. If not.... Surely mobiletechvideos could fix it. If they can be brought back from the dead, surely they can be brought out of bootloop.
Sent from my SGH-I717 using Tapatalk 2
darthmalgus said:
UPDATE: Thanks rangercaptain for that. I had totally forgotten Kies had the Firmware recovery. Unfortunately, it didn't work. And AT&T, well, we all know how they are about out of warranty phones. So I'm seemingly stuck, but I did have a thought. If the battery overheated, and malfunctioned, could it cause this? Would it be worth the 10 bucks to order a replacement OEM battery on Amazon and see if it fixes it?
Click to expand...
Click to collapse
Definitely try the battery. I had exactly this same problem, and even though the old battery seemed to be taking a charge, it was still screwing everything up (in the same ways you described). A new battery fixed everything*.
* - Ok, it actually it took a couple ROM reinstalls, to fix everything I apparently screwed up while trying to fix the devices before switching out the batteries.
Thanks for the info. I went ahead and ordered a new bateery, it'll be here Monday, so hopefully that works. I have the phone flashed stock with Kies at the moment, so I would hope I don't have to do any more reflashing if the battery is the issue.
Yeah i have the same issue. I was running blackstar. I had some issues occasionally with it crashing, nothing major. decided to install JB once ATT had official out. Wiped, installed, gets to att logo and reboot... please post your fix if it works. I have a second battery. I'll give it a shot but I have been keepeing it plugged in while doing these things and it still doesnt work.
"Wiped, installed, gets to att logo and reboot..."
If you're getting to the att logo, it may not be a battery problem. I'd suggest reinstalling the update after manually wiping everything using CWM.
Matt Bernius said:
"Wiped, installed, gets to att logo and reboot..."
If you're getting to the att logo, it may not be a battery problem. I'd suggest reinstalling the update after manually wiping everything using CWM.
Click to expand...
Click to collapse
Tried a couple flashes, with the debloated and bloated Roms based on Official JB. I can get to the getting started screen sometimes. typically I hit the next button and it goes into bootloop. once or twice i was able to select the next button and get to the next screen before it crashed. I'm thinking it's dead but.... idk.
This fixed my issue...
Replaced battery and yeah. I'm all better. so odd.. shrug. The other wasn't giving any indication that it was actually defective.
Awesome ... final step ... change the title to include solved :victory:
Related
so this guy came into my store who had a rezound, never once had a problem with it ever...then the battery died fully overnight because he forgot to charge it..
so when he woke up, it was dead obviously. he then plugged it in, and the orange light came on for 5 seconds...then shuts off. and nothing happens. this even happened when he brought it in for me to try. so i'm like, wtf, probably a bad battery maybe?
so i put in a good one we've got...same thing. so i ask if he's rooted or anything, he says no...but i did a search, and found some posts that when people had bad flashes of roms, it would stick at the white screen, and they had to restore a backup in CWM for it to work.
so i tried to see if maybe he was rooted...went into bootloader, hit recovery, and the phone just died. just shut off. so i was like, thats weird...so then i tried to do a factory reset....same thing, i hit factory reset, the white HTC screen came rgiht up, then the phone just died...and this was with a fully charged battery, too.
eventually we had to just call up and get him sent a refurb, but still, has anyone seen this problem? nothing i could do could get it to boot, and that's such a ****ty feeling especially if this guy said that he NEVER had a problem with any HTC phone, especially this rezound, until that battery died and it would'nt turn on again.
I've had that problem after a bad flash, but it still let me get into hboot and recovery without problems, so I doubt it was that. Don't have a clue what it could be though... at least you got him taken care of with a refurb. Maybe the inability to boot to recovery could be not having amon ra or cwm installed (never tried without one) and if he wiped /data or /system I don't know if factory reset would know what to reset to (again, never tried).
Edit: Also, with me, the phone never died. White HTC screen would stay up until I pulled the battery and it would still recognize the charger.
exactly! it's a problem after a bad flash. i wonder if this dude was lying and tried to flash something, his battery died, and it bricked it
I am currently experiencing the exact same problem; I was able to replicate everything you describe, including what happened when you tried to go into recovery or factory reset mode. I have NOT tried to root or do anything else untoward with the phone ... if anyone has any idea what I can do other than get a new phone and lose all my data, I would really appreciate it!
edit - there is one difference: my battery never died. I took my phone out of my pocket at 5:40 to look at it, and it was fine. I looked at it again at around 5:50 and I had the white htc screen. At this point I pulled the battery and started googling.
second edit - could the forced update have something to do with it??
nope, he brought his in before the update.
have you gotten anything to work? when we called customer service, they just replaced his phone for him..i hope it works out for you, man. maybe try to get into fastboot and wipe the phone, or something? i know i was able to get into the bootloader..maybe you can push a factory reset from the comp
avertist said:
I am currently experiencing the exact same problem; I was able to replicate everything you describe, including what happened when you tried to go into recovery or factory reset mode. I have NOT tried to root or do anything else untoward with the phone ... if anyone has any idea what I can do other than get a new phone and lose all my data, I would really appreciate it!
Click to expand...
Click to collapse
If you want to at least get the data off of it you can try using testdisk.
http://www.cgsecurity.org/wiki/TestDisk
I used it for my external sd card that wouldn't read in the phone or computer anymore and had all my nands and other backups on it. It seems like it won't work on Android but it will, but since I formatted it in the phone it didn't seem to have a volume name.
After you select the drive and it comes up with the partition table list, select [None].
Then select [Analyse]
I think that's when it will list all your directories.
You might be able to hook up your phone and get stuff off the internal card if you leave it at the white htc screen, not sure. But I have used testdisk successfully on a drive and the sd card that all systems said was unreadable and needed to be formatted. Anyway, it's worth a shot to see if you can get your stuff off it even if you have to return it.
jayochs said:
so this guy came into my store who had a rezound, never once had a problem with it ever...then the battery died fully overnight because he forgot to charge it..
so when he woke up, it was dead obviously. he then plugged it in, and the orange light came on for 5 seconds...then shuts off. and nothing happens. this even happened when he brought it in for me to try. so i'm like, wtf, probably a bad battery maybe?
so i put in a good one we've got...same thing. so i ask if he's rooted or anything, he says no...but i did a search, and found some posts that when people had bad flashes of roms, it would stick at the white screen, and they had to restore a backup in CWM for it to work.
so i tried to see if maybe he was rooted...went into bootloader, hit recovery, and the phone just died. just shut off. so i was like, thats weird...so then i tried to do a factory reset....same thing, i hit factory reset, the white HTC screen came rgiht up, then the phone just died...and this was with a fully charged battery, too.
eventually we had to just call up and get him sent a refurb, but still, has anyone seen this problem? nothing i could do could get it to boot, and that's such a ****ty feeling especially if this guy said that he NEVER had a problem with any HTC phone, especially this rezound, until that battery died and it would'nt turn on again.
Click to expand...
Click to collapse
Yeah I had a lot of white screen time when I had the Evo! A co-worker of mine had this happen on his Evo. It was from overheating. Now I realize this is the Rezound we're talking about but brilliant phones do think alike.
Sent from my ADR6425LVW using Tapatalk
happened to me when the kernel didn't flash but the rom did. Had to boot into fastboot and flash a kernel through a command prompt on my PC.
Just finished dealing with this after a bad flash. I couldn't boot, couldn't flash a new rom because of the Mainver error and couldn't get into recovery. Finally fixed it by deleting the PH98IMG.zip file. That let me get into recovery. Then had to flash back from ICS to Gingerbread. The I could follow the instructions to fix the Maiver error.
I had heard reports that people had data loss issues from the battery dying all the way in the rezound? Something tells me running the RUU on the phone would have fixed it.
Sent from my ADR6425LVW using XDA App
So yesterday I was in a call with low battery when it shut off. Normally not a problem, just plug it into the wall for a while. Well when I tried to turn it on, it wouldn't even boot up. It was stuck at the red M logo. The LED showed amber colored as well. I left it plugged in and the light remained amber until 90% battery, where it turned green.
I tried to turn it on and its been stuck on the red M logo. Its been stuck for more than 12 hours now.
I CAN access fastboot, android recovery, etc. I already tried wiping the cache and even did a factory reset. Still wont work.
What can I possibly do? I luckily have a backup phone, but I've had my photon for less than a month, no warranty, and I'm a novice Android user. Any help would be greatly appreciated.
MooseV2 said:
So yesterday I was in a call with low battery when it shut off. Normally not a problem, just plug it into the wall for a while. Well when I tried to turn it on, it wouldn't even boot up. It was stuck at the red M logo. The LED showed amber colored as well. I left it plugged in and the light remained amber until 90% battery, where it turned green.
I tried to turn it on and its been stuck on the red M logo. Its been stuck for more than 12 hours now.
I CAN access fastboot, android recovery, etc. I already tried wiping the cache and even did a factory reset. Still wont work.
What can I possibly do? I luckily have a backup phone, but I've had my photon for less than a month, no warranty, and I'm a novice Android user. Any help would be greatly appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1393519
Click on the software and tools link and use rsd lite to reflash the stock os onto the phone. If that doesn't work I would take it to the sprint store.
I assume you tried pulling the battery?
I'm downloading SBF now. Hopefully it works, because I live in Canada and we don't have Sprint stores.
And YES, I tried pulling the battery. Multiple times. With every combination (eg, plug in, turn on, then insert battery; put in battery, turn on, then plug in, etc)
the sbf should work but may i ask how you managed to brick your photon? when i just got mine i did everything wrong and i never got even a soft brick so i'm interested what i didn't mess up haha
Quick question: I should be downloading the most recent? Will it make a difference?
And damn, did I actually brick it?? I'm pretty new to this thing, this is my first Android and I've had it for less than a month...
And nothing should have triggered it. I added another line in build (ro.media.setting.1080p or something) and I added another setting in /system/etc/mediaprofiles.xml. I was trying to add 1080p to the camera (unsuccessfully). I didn't remove anything, and even after a reboot it was fine.
It wasn't until the battery died, where it stopped booting up. Just my luck :/
You should probably choose one of the newer ones, just becasue of bug fixes, etc. If you happen to know what version you were running before then I'd choose that. I cant stress enough, make sure the one you download is for the Photon and NOT Electrify! And technically yeah that is a brick lol but its extremely hard to legit brick beyond repair a photon due to the fact that we have RSD Lite and SBF files to bring it back.
Strangely, I found a thread depicting the same problem that I had, although with the electrify. http://forum.xda-developers.com/showthread.php?t=14813
Anyways, the problem is fixed, by reflashing the SBF using RSD Lite, everything is back to normal! Well, almost, just have to restore my backup
Thanks so much for your help guys, I wouldn't have been able to fix it without you all!
can you fix a bricked phone??
My Photon has done the same thing! I rooted her and did the Bootstrap Recovery thing. Everything was kosher until I tried to load that stupid Beats Audio. Something happened between me flashing it and the reboot where it locks the phone. I tried to do the Android recovery screen, I wiped, I did about everything I could find. No bueno.
I followed this forum and clicked the software and tools link as instructed. I tried with RSD 5.6, and tried several iterations of SBF's located here and here. I was using SBF - 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_MR-3-CM.
It lets me go into boot mode, and when I try to flash the SBF it appears to go through, but it always fails at the end. Which, the posts state it will do, but my phone will not reboot afterwords. After trying everything I could for a couple days, I decided to just take it to a Sprint store. Mind you I've had this under 30 days, but longer than 14 so they stated it would have to be replaced. They tried to flash, but said they were getting stuck too.
I know that a replacement is pretty much the answer, but just wanted to check one more time to see if anyone had any other ideas, or could point me to other forums maybe? Appears I've done what few have been able to accomplish...brick this joker.
[Q&A] [ROM]【4.4.4】Google Play Edition 【KTU84P】- 09/30/2014
Q&A for [ROM]【4.4.4】Google Play Edition 【KTU84P】- 09/30/2014
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
gpz1100 said:
I gave up trying to calibrate my compass. I have issues with it in any rom including stock TW. Some of these chips are just broken.
Click to expand...
Click to collapse
After trying many of the suggestions on this thread to fix the compass (my GPS lock is fine), I thought I might have messed up the hardware somehow. However, last night I flashed the 7/12 KT GE kernel, and the compass now correctly points in the right direction.
Germany?
Hi Dan (or whoever else reads this). Love the ROM! It's amazing. Do you know if it will work in Germany? I went to Mexico a few months ago, and the latest build at the time would not get reception anywhere. Flashing a TW ROM solved the problem, but I would much rather use yours.
Thanks!
TheSt33v said:
Hi Dan (or whoever else reads this). Love the ROM! It's amazing. Do you know if it will work in Germany? I went to Mexico a few months ago, and the latest build at the time would not get reception anywhere. Flashing a TW ROM solved the problem, but I would much rather use yours.
Thanks!
Click to expand...
Click to collapse
Well in case anyone is curious, this ROM gives me great cell service (full signal on Vodaphone.de) but no data in Munich. I tried airplane mode, disabling/enabling data roaming several times and setting the network mode to GSM preferred, but no luck. Flashing the latest release of Hyperdrive ROM allowed me to use data. Oh well.
flashing google edition on verizon s4 on nc5
I'm a noob and can't figure out if i can use safestrap to flash the dandvh google play edition rom.
verizon galaxy s4 on nc5 build, rooted with towel root and running safestrap 3.75
Viper Audio Working?
Does anyone else use Viper Audio with this rom? I find that the audio driver frequently stops processing when I stop playing music and then come back and play again. It will start processing again if I reboot the phone or even kill the Viper gui process. I've tried installing it as a user or system app but hasn't seemed to matter. Anyway, just curious if anyone else was having the same kind of results.
Hi everyone, hoping you all can help me with a problem I'm having with my phone. First, some specs:
ROM: Danvdh GPE 9/30
I am one of those lucky MDK users, I got the phone in May 2013 and rooted early
I had been running the NC5 modem for a while now with no issue. The problem started after I flashed the NG6 modem (from Surge1223's thread) in TWRP. Just fyi, here are the steps I took to flash the modem. Within TWRP, I flashed the zip file, cleared Dalvik/cache, then rebooted.
Almost immediately I started getting random reboots. It rebooted twice, then seemed to settle down, so I decided to wait a day or so to see what my phone would do. Sadly enough, it started rebooting again, so I gave up last night and reflashed the NC5 modem in TWRP using the same method as before. The phone was fine after that, until this afternoon. About an hour ago, my phone froze, and rebooted, but the screen cut off at the Samsung custom padlock boot screen. It seems to be off at this point, but I can't power on the phone without pulling the battery. After pulling and replacing the battery, the phone powers on by itself, but again cuts off at the Samsung boot screen, about 3-4 seconds into the boot process. I've tried booting into TWRP and download mode, with the screen turning off and the device seemingly freezing after 3-4 seconds. I'm at a loss as to what to do at this point.
I'm at work right now, but when I get home, I will see if Odin3 can make some sort of contact with the phone. Any help in the meantime would be greatly appreciated!
Sounds like you may have a bad dl. Re download. Turn phone off. Then boot into TWRP and reflash the modem zip. Not the non-halos.zip.
Alxoom33 said:
Sounds like you may have a bad dl. Re download. Turn phone off. Then boot into TWRP and reflash the modem zip. Not the non-halos.zip.
Click to expand...
Click to collapse
I would love to, but I can't.
I put a video up on Youtube showing what the phone is doing right now. I don't have 10 posts yet, so I can't post links, but if you go to youtube.com then add "/watch?v=3ey5xD9LodY" at the end of the URL, you can see what the phone is doing.
It is the only thing the phone will do. I've tried doing a hard reset by holding the power button, but nothing happens. All I can do is pull the battery and start this process again. If I hold the correct button combos, I can begin to boot into TWRP or download mode, but the phone cuts off/freezes like clockwork after 3 seconds.
I tried to get Odin3 to recognize the phone, but my desktop doesn't recognize that anything is plugged in when I connect my phone to it, so Odin3 by extension doesn't see anything.
Did you install the Samsung apps on your computer? You need them for the computer to recognize your phone.
To hard boot into recovery you need to hold power button and volume up at the same time, then let go of power button once blue writing appears on upper corner of phone.
Sent from my Xoom Wifi using Tapatalk
I'm sure I have. I've been able to send adb commands to the phone in the past. Now however, my PC doesn't even see that a device has been connected to it (nothing shows up in the device manager, not even an unrecognized device).
The phone will no longer charge when I plug it into an AC adapter either (or at least the LED no longer lights up indicating it's charging).
I have tried booting into recovery several times. Each time, it will begin to boot into TWRP, the blue text, "RECOVERY BOOTING...", will display, then immediately afterwards, the screen will cut off and the phone will freeze, just like in the Youtube video I posted.
I'm afraid the thing is bricked...
So, I was talking to a friend about what's been going on with my phone. During the conversation, I started goofing around and smacking the back of the phone like 4-year-old me would an NES to try and make it work (ah, good times...). Believe it or not (and I did not touch the power button while doing this), the phone powered up and successfully booted!!!
It showed only 2% battery life, so I connected it to the AC adapter, but then a few seconds later the phone died again.
This occurrence leads me to believe there is something wrong with the battery, and leads me to another question. Can the S4 (or any other smartphone) run solely on USB power?
My roommate has a Galaxy SIII, I read the SIII battery can be used in the S4, so I will test the phone out with his battery when he gets back tomorrow, and update you then.
marioluigi64 said:
So, I was talking to a friend about what's been going on with my phone. During the conversation, I started goofing around and smacking the back of the phone like 4-year-old me would an NES to try and make it work (ah, good times...). Believe it or not (and I did not touch the power button while doing this), the phone powered up and successfully booted!!!
It showed only 2% battery life, so I connected it to the AC adapter, but then a few seconds later the phone died again.
This occurrence leads me to believe there is something wrong with the battery, and leads me to another question. Can the S4 (or any other smartphone) run solely on USB power?
My roommate has a Galaxy SIII, I read the SIII battery can be used in the S4, so I will test the phone out with his battery when he gets back tomorrow, and update you then.
Click to expand...
Click to collapse
Have you tried a different USB cable/transformer? It sounds like you might just have a charging issue. Not enough juice to get it started.
Allowing a battery to cool down will give it more usable power, which as it heats back up will deplete again. This sounds like your situation... Power off for a few, restart it has enough to begin booting, then depleted again.
The phone cannot run on USB alone it needs the battery to sustain it's operation.
I have tried 3 USB cables, 2 AC adapters, and 2 PCs.
When this started on Friday, my phone was hooked up to my PC at work and showing about 50% battery, but it's possible something went wrong with the battery and it's stopped delivering any significant amount of power or accepting a charge.
So it turns out it wasn't the rom or new modem that was the problem, my battery has decided to kick the bucket. I tried my roommate's battery in my phone and it booted right up as if nothing was ever wrong! Strange that an OEM battery would just die like that, but I suppose that does happen from time to time. Thanks for the help!
matycakes said:
Does anyone else use Viper Audio with this rom? I find that the audio driver frequently stops processing when I stop playing music and then come back and play again. It will start processing again if I reboot the phone or even kill the Viper gui process. I've tried installing it as a user or system app but hasn't seemed to matter. Anyway, just curious if anyone else was having the same kind of results.
Click to expand...
Click to collapse
I use it, and I've never had any issues with it. I would recommend reinstalling, but you've probably tried that already. Are you using the latest version of the app?
TheSt33v said:
I use it, and I've never had any issues with it. I would recommend reinstalling, but you've probably tried that already. Are you using the latest version of the app?
Click to expand...
Click to collapse
Yeah, I have tried reinstalling it, and I am using the latest version of the app. The fact that you haven't had any issues is encouraging. I'll continue to troubleshoot and see what I can find.
I keep getting this (in CWM touch)
Flashing Google Play Edition
Android 4.4.4
Enjoy!
format() expects 5 args, got 4
E: Error in /storage/sdcard1/danvdh-GE-4.4.4-09-30-2014-VZW.zip
(status 7)
installation aborted
Is it just a bad DL?
EDIT: Tried a new DL, same issue. I want to get this fixed asap
Is cm11 theme manager included in this rom?
brd912 said:
Is cm11 theme manager included in this rom?
Click to expand...
Click to collapse
It is not.
Hi there! Long time reader, first time poster (TL;DR below...but it should be a quick read anyways )
So I've been using this S2 of mine for almost 4 years now, haven't had any trouble (other than a couple of battery swaps). For the past 6 months or so I've been using CM 12.1 nightlies without issue.
The events:
- The other day, my phone froze (I wasn't using it when it froze, it was when I went to use it that I noticed...it was on the wifi selection screen if it matters), so I held the power button to shut it down, and when I powered it back up, it just froze at the Samsung boot screen (with the usual yellow triangle).
- At this point, I was able to reboot into download mode at will, but any attempt to boot to recovery just led to the freeze at the Samsung boot screen. Also, the phone would automatically reboot itself at this point any time I inserted the battery (I was of course putting the battery in and out trying everything I could).
- I would have reflashed from Odin at this point, but since I was away for a few days I just kept trying to reboot into recovery, to no avail. On one of these attempts (power+vol up+ home) it showed the Samsung boot screen, and then immediately shut down and I haven't been able to get anything onto the screen since
I'm now home, and I can't seem to fix it. If I plug the phone into a charger, the top half or so of the phone gets warm, and it also seems to get warm if it isn't plugged in and I try to power it up. I was thinking maybe the phone was maybe doing the same thing as before and just not showing anything on screen, but I blindly do the steps to get it into download mode, and Odin doesn't recognize anything (drivers are definitely installed). I have also tried other batteries, no luck.
Any ideas of what I might try? I'm willing to do anything. For the record nothing happened to the phone at all when this all happened (no dropping or water damage or anything, just my attempts at booting into recovery). Maybe I should try a jig? I'm also open to opening the phone if there's something I can do, though I don't have experience with this.
Thanks so much for any suggestions!
TL;DR: phone froze (running CM 12.1 nightly), held power to shut it down, and then consistently froze at the boot screen on any attempts to power it on. After a few attempts at booting into recovery (the phone would only freeze or enter download mode) the screen suddenly shut off and I haven't seen anything on it since no matter what I try. I can't think of anything that happened to the phone I'm open to any and all suggestions! Thanks
One sentence amongst your description stands out like a 'sore thumb'.....
That the device heats up towards the top when you attempt to charge it.......
Until you try a jig I can't be certain, but that heating coupled with a dead/unresponsive screen along with a lack of recovery and/or download modes (download mode is 'hardwired' into the device, and NOTHING should be able to corrupt it) are the primary symptoms of a failed motherboard.......
That is my opinion based on my experience in these forums and personal experience with a (now dead) S2 (one of two that I own).........
Get the jig just to be sure, but I'd be surprised if it had any effect.....sorry to be typing something you don't want to read, but you said it yourself, the device is 4 years old....it's been in service roughly twice as long as most smartphones, and they don't last forever....
http://i.imgur.com/rVnFwJM.jpg
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
smacsmac said:
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
Click to expand...
Click to collapse
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Sorry it took me a while...the jig was in the post haha. It didn't do anything at all (no response when I plugged it in) so I think it's safe to say you were bang-on and the motherboard failed! Happily using a new S2 (with CM13.0 now ) on behalf of my friend though.
Thanks again.
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Elaias said:
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Click to expand...
Click to collapse
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Its hard to tell you and hard to accept. You can almost give up the hope, your NAND Chip is just what we call " wear-out ". In the most cases no write is possible anymore, the funny part is -> sometimes read is still fine. If that is the case: The system is booting and working, but saving just nothing. The NAND is frozen to its state before it broke.
At our local store, customers come to us with issues like " Factory Reset impossible ", "Can't delete my Files" "Can't create files". All these Devices have inaccessible NAND's and inaccessible Recovery. Only Bootloader is working, but as the NAND is broken, flashing doesn't change anything.
smacsmac said:
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Click to expand...
Click to collapse
yeah, flashing with odin did the trick. now running cm13 and everything works fine. sorry to hear that your phone turned to brick.
So I recently had Marshmallow firmware version G900TUVU1GPE1_G900TTMB1GPE1_TMB installed and had gotten tired of the update service running and trying to download a firmware update, I used these directions here to root my phone and then install Titanium backup to turn off OTA updating services and ES file explorer to delete the update.zip file
http://forum.xda-developers.com/tmo...l/root-how-to-root-sm-g900t-firmware-t3358190
I recently started having an issue with the phone whenever I would use it with GPS enabled or off, it would reboot and get back to the unlock screen and then go into a reboot loop, which would only stop if the battery were pulled. This happens in Apps too such as Google Play or Facebook, or Accuweather. I figured I'd try to install the Stock KitKat version of G900TUVU1BNH5_G900TTMB1BNH5_TMB, well the reboot loop issue still exists. Is there anyway of resolving this issue as I am thinking of putting GPE1 back In and Redoing the root just to undo it. I know it is forbidden to check NAND Erase All or other firmware options in ODIN. I downloaded a partition/PIT file just i ncase I need it too. I'm pulling my hair out lol.
Thank you
Upate, After I reinstalled G900TUVU1GPE1_G900TTMB1GPE1_TMB, and did a normal system recovery (no TWRP in at this point) I had enabled WIFI and it went into a reboot loop, took the battery out, then I installed TWRP- went to advanced wipe, did not select System, Only Davlik, Internal, Cache. I have not installed SuperSU. I hope this resolves the issue, otherwise I might need a new phone or motherboard...
Did you pull the battery as soon as it boot looped? Mine always loops once after flashing firmware, but boots normally on the second attempt without pulling the battery.
invisiblewave said:
Did you pull the battery as soon as it boot looped? Mine always loops once after flashing firmware, but boots normally on the second attempt without pulling the battery.
Click to expand...
Click to collapse
I have been pulling the battery, plus another oddity is when the phone goes into a loop and I can't get it to stop until after a bit, I can just plug the charger in and then It stops. Someone said the battery could be at fault. I bought a battery and waiting on it between the 14th and 16th, I will definitely follow up if that resolves my issue too.
invisiblewave said:
Did you pull the battery as soon as it boot looped? Mine always loops once after flashing firmware, but boots normally on the second attempt without pulling the battery.
Click to expand...
Click to collapse
Well I believe the Issue has been Resolved, I got the battery yesterday, charged it up over the night and started using it today, so far no random reboots or bootloops.
Differences
The Battery that came with my phone was Made in China, the one I just bought is made in Vietnam.
I will keep yall posted after a few days to see if it has any issues.
Well the battery Fixed my issue.
I'm on my third battery and still looping... Anyone else have any ideas?
workingmomjd said:
I'm on my third battery and still looping... Anyone else have any ideas?
Click to expand...
Click to collapse
go back to stock 4.4.2 rom is the most I can say at this point
The 5th was the charm (I hope!)! Going on day two and at 78%, so the rapid battery drain that started right before the looping is also cured. It's a good thing this is the last of 4 Samsung s5's so cycle the house, so I had lots of spare batteries on hand Thank you!
workingmomjd said:
The 5th was the charm (I hope!)! Going on day two and at 78%, so the rapid battery drain that started right before the looping is also cured. It's a good thing this is the last of 4 Samsung s5's so cycle the house, so I had lots of spare batteries on hand Thank you!
Click to expand...
Click to collapse
i come to notice the battery that came with my phone stated made in china, the new one I ordered said Made In vietnam. I believe batteries made in china is what caused the Note 7s to go up in flames along with Surefire Flashlights to overheat and catch fire too