I have searched multiple threads, on here and the rest of the intertubes, I haven't found anything that helps. Most of the tips I have come across deal with flashing in Odin, Roms, etc. I don't think any of those really apply here( I could be wrong about that)
Here is my problem....My wife's vibrant running stock 2.1(Not sure why she isn't running something more current) is acting up. She hasn't had any problems with it before, and there was no event that would point to these problems being a symptom.
It does the following -
Won't turn on.
Gets stuck at The Vibrant screen... Then shuts off.
Gets stuck at the TMO screen... Then shuts off.
Gets to "Scanning Media"... Then shuts off.
Gets to the Galaxy S screens and seems to be in a loop for about 45 seconds...Then shuts off
Gets to home screen, for about 20 seconds, this is as far as I can get...Then shuts Off.
All of these happen interchangeably and seemingly without any sort of reason or rhythm.
What I have tried -
Battery, sim, and sd out and restart
Change battery, with my Vibrant. My vibrant works fine with both.
Tried to update firmware with Kies... phone shuts down before any progress is made.
Not sure what else to do, but I would be willing to try just about anything.
Thanks
Sounds like it could be hardware, but you could try reflashing it with Odin. I'd suggest first just getting it into download mode while plugged into USB. If it shuts down while just sitting there while plugged in, I'd consider that hardware.
That's not looking good.
You could try flashing a CWR (Clockwork Recovery) zip and seeing if some of the normal cleaning techniques do anything (wipe cache, wipe dalvick cache, and fix permissions). The file and some tips on CWR can be found here http://forum.xda-developers.com/showthread.php?t=849028
You don't have to root to flash CWR. You can just do that one by itself. One thing to note is that you may have to do the reinstall packages step twice from the recovery menu. The second time would take you into CWR.
Having CWR on there would be nice since you can try some other things like flashing a different kernel to see if that helps. I'd recommend using Odin to flash the stock bootloader as well just as something else to try.
Thanks for the idea. I have been wanting to try it, but I could not get the phone to stay on or enter recovery.
Like I said I was willing to try anything, so when a friend said, throw it in the freezer for a few minutes, I was skeptical. But it works. As long as the phone is cold, it will turn on, make phone calls, etc. Usually for about 3-4 minutes. Then it warms up and shuts off. The only way to get it back on is another trip to the freezer.
Does anyone have any idea, what my issue could be? And how to fix it?
Thanks.
That's definitely hardware. Could be a bad solder joint, fixable, but it sounds more like a chip that is unstable at room temperature. I suggest you buy one with a bad screen cheap and make one good phone out of them. Adam Outler, the Unbrickable Mod guy, might have some ideas.
Related
If your phone was bricked in any way, but still shows something on the screen when powered on or plugged in, try this.
1. Take out battery, put it back in. (to turn the phone fully off)
2. Don't turn it the phone on!
3. Plug the phone into your PC, do not hit the power button!
4. See if the phone shows anything on the screen
IF the phone screen does show the battery charger or something else on the screen after being plugged in without you hitting the power button, so far so good.
5. Now while it's on like this, hold the volume up and volume down buttons.
6. Hold the power button as well as the volume buttons until the screen goes black.
7. As soon as the screen goes black, let go of the power button! But DON'T let go of the volume buttons!
When done properly, this will always get you into Download mode. After that you should be able to use Odin to revert to stock, tar and instructions here:
http://forum.xda-developers.com/showthread.php?t=734475
This fixed my 'odd' bricks. Over and over again.
I'd say it's impossible to truly brick this phone.
I have been researching this most of the day, due to some testing I was doing, and the one thing I have come to realize is that this phone recovers well from "brick" it's not a true brick it's just scary. One of the posts I read, here on xda, said that unless the blue progress bar started advancing while using Odin, you can unplug, pull battery fairly safely.
davbran said:
I have been researching this most of the day, due to some testing I was doing, and the one thing I have come to realize is that this phone recovers well from "brick" it's not a true brick it's just scary. One of the posts I read, here on xda, said that unless the blue progress bar started advancing while using Odin, you can unplug, pull battery fairly safely.
Click to expand...
Click to collapse
Haha well that's exactly what happened to me. I flashed wrong with Odin and it failed halfway through, and I had no choice but to reboot the phone.
And when I did I got a truly odd screen. All I could see was a picture of a phone connected to an exclamation point connected to a laptop. That's it. Lol.
And I fixed it by doing this.
omg, i love you This totally fixed my problem XD
Everyone kept saying go to download mode, but no one ever said to "7. As soon as the screen goes black, let go of the power button! But DON'T let go of the volume buttons!"
super life saver... thanks alot
I actually did find someone else say to do that but it was out of luck as it was deeply buried. Don't remember where it was here lol
Its nice to have people who help us newbies
andershizzle said:
Haha well that's exactly what happened to me. I flashed wrong with Odin and it failed halfway through, and I had no choice but to reboot the phone.
And when I did I got a truly odd screen. All I could see was a picture of a phone connected to an exclamation point connected to a laptop. That's it. Lol.
And I fixed it by doing this.
Click to expand...
Click to collapse
Yea, last night I was messing around with the latest lag fix, but it ending up causing a lot of FC's, so I had to revert to stock a few times. I tried to make it work using ext2 and ext3, but it still wasn't stable enough. I didn't enjoy the noticeable speed increase, but it wasn't worth it since launcher pro was one of the programs that was FCing.
Anyways, so after I gave up for the 3rd time, I flashed stock using ODIN and it got stuck. I left it there for awhile with no progress and the phone's screen actually just went completely black. I pulled the battery and got the weird cell phone pointing to computer icon. I almost crapped my pants at that point. Very scary moment since I had not seen that screen before.
A quick google search for "bricked Vibrant" led me to this thread and voila! My Vibrant is alive and well again.
Thanks a bunch.
PS: After reflashing stock that many times, I still find it strange that after a fresh flash, I still get a noticeable speed boost by wiping the phone through the privacy setting. Not sure if it's a placebo effect, but I swear it makes a noticeable difference every time.
Maverick777 said:
Yea, last night I was messing around with the latest lag fix, but it ending up causing a lot of FC's, so I had to revert to stock a few times. I tried to make it work using ext2 and ext3, but it still wasn't stable enough. I didn't enjoy the noticeable speed increase, but it wasn't worth it since launcher pro was one of the programs that was FCing.
Anyways, so after I gave up for the 3rd time, I flashed stock using ODIN and it got stuck. I left it there for awhile with no progress and the phone's screen actually just went completely black. I pulled the battery and got the weird cell phone pointing to computer icon. I almost crapped my pants at that point. Very scary moment since I had not seen that screen before.
A quick google search for "bricked Vibrant" led me to this thread and voila! My Vibrant is alive and well again.
Thanks a bunch.
PS: After reflashing stock that many times, I still find it strange that after a fresh flash, I still get a noticeable speed boost by wiping the phone through the privacy setting. Not sure if it's a placebo effect, but I swear it makes a noticeable difference every time.
Click to expand...
Click to collapse
Glad I could help!
And that's intersting. I'll make sure to wipe the privacy settings. I actually haven't ever wiped them yet.
No go for me.
I used the stupid partition tool in rom manager. partitioned the internal memory not the sd card.
Saw a few others did this, and this worked for them, either right away or after flashing eugene's froyo rom then reverting back, but that rom just hangs on cache.fsd or something like that.
Trying to repartition through odin, with no download files selected right now. It does not appear to be doing anything, just set pit file, then do not turn off target in odin.
Will leave it for a bit, maybe try to flash this again, i think the issue might be deeper for me though. need kernel and everything else.
I did that but my phone locked up and now all I get is a picture of a yellow cation sign next to a little phone and pc pic.. anything I can do at this point or??
tried going into recovery and download mode but it wont let me past that screen.
Thank you so much for this, I received a replacement set 2 days ago and was playing around the the phone and I bricked it, it thought it was frozen so I pulled the batter and it bricked.
I followed your instructions and it works like a charm. What I did find though is that i can't seem you use odin on a mac even with a virtual machine. I had to use an actual PC.
tweezit said:
I did that but my phone locked up and now all I get is a picture of a yellow cation sign next to a little phone and pc pic.. anything I can do at this point or??
tried going into recovery and download mode but it wont let me past that screen.
Click to expand...
Click to collapse
This is exactly the screen I had. Follow my instructions exactly and you'll get into download mode (at least i did)
This should be made a sticky.
thank you thank you thank you
Sticky this thread.
Sent from my SGH-T959 using XDA App
Great find for all.
has anyone found a way to unbrick a flashed EU rom then the person flashed to US rom? and then the power wont come on? But the unit does get hot when plugged in?
Im trying to see if i need to jtag this thing. or if anyone had success?
Thanks
ok so my vibrant gave me the cell phone and computer screen i got it back in download mode. started odin to get it back to stock but no matter how long i let odin go nothing happens i got the files that i need for odin out of a thread on these forums and i have followed the directions to the letter and still nothing. any help some one can give would be great. thank you for your time.
How do I know if my phone is being picked up by Odin or being flashed?
did the same thing the clockwork partition wiped my internal memory
F**k!
woop guess im going to tmobile in the a.m. and playin the whole
idk what happened it wont turn on
thank god for the 14 day return policy!
I ran into "brick mode" myself 2 nights ago and could not get my phone into download mode. Any possible combo of volume key up/down and power had no effect. Just that phone exclamation point pc icon slowly blinking in the center of the screen. I did finally get it into download mode but it wasn't using any of the previously mentioned methods, so I'll add one more to the growing list to try. This one worked for me after almost 4 hours of experimenting.
BTW....my phone would never display the battery charging image when powered off and plugged in. Just this same annoying image.
Pull the battery. Put it back in. Hold the just the volume down button. Do not hold the power button. Plug in either a wall charger or USB cable. The cable will power up the phone and voila. I was in the download screen.
I also highly recommend the stock ROM from the thread
"[ROM] OFFICIAL T-Mo Vibrant JFD ODIN/Nandroid Backup Images 7/29/10 (Tested/Working)" In Vibrant > Vibrant Android Development
I tried another ROM found out on the internet and ended up with a shell that crashed and restarted every 60 seconds.
For those running into Odin stuck on a message about verifying the file system, I had no luck when the phone used COM3. I suggest moving your USB cable into different ports on your PC. Each new port will "install" a new instance of the phone using different COM ports. COM5 and COM6 both worked as I was reflashing the day away yesterday.
Ok, so new one to me here. I went to check my phone and discovered that it appeared to be turned off, which is odd cause it was on and only in sleep mode. I pulled the battery and rebooted. The phone was stuck at the boot screen for way, way, way longer than it should have been. I pull the battery and try to get into recovery. No dice. Tried a couple times. I was able to get into download mode, so I decided to Odin back to stock and start fresh.
Knowing issues with using a voodoo enabled kernal and flashing to stock and the fact that I could not get into recovery to disable voodoo, I Odin Eugene's froyo that does not brick with repartition off. I get the error after reboot, pull the battery, go back into download mode, and Odin the stock image with repartition on. Says PASS, phone reboots, shuts off and goes to charging battery image, then reboots, goes back to charging battery. It keeps repeating. I have tried to Odin 1/2 dozen times now.
I was running Bionix V 1.3 with DoW14 v1.4. I was overclocking, but have had no bad past situations with overclocking on either DoW or Dragon kernals. Nor have I had any similar issues previous times I have done this method to return to stock.
I checked and made sure the power button is not sticking. I opened it up and there is no apparent damage to the board, power button, etc.
I cannot get into recovery, only download mode. Any suggestions?
I hate to be the bearer of bad news.
But your phone is F*K'd.
Please check this thread THIS THREAD
Myself and many others have friend, likely hardware- fried the internal NAND, SD card.
At present, there is no fix for this. There is a fix at the last 2 pages, that is a workaround, where you can use the external SD temporarily.
Check the thread.
Sorry, but GL
Yeah, through my amazing non-existent searching skills, I came across that thread shortly after posting (yay for searching). Reading through it now, so this thread can be closed.
If I fried something, oh well, I'll just get another one if I need to. Not a huge deal.
patience and keep trying (seriusly) and if not send me your phone with 1 dollar bill and return stamp i get this fixed for you , as i said keep trying ! some recovering ffrom bricks takem me hours sometimes i leave my phone home pissed off to come back to it next morning and keep on trying , guess what im still on the same phone
belive me sometimes these phone need a little JUMP START like keep that thing odining back keep ccharging for 20 min and unpluging oding back again charge it again take out battery hook up charger put battery in reodin ....if you think im playing that you just lost your phone so dont give up
my experience 6 bricked vibrants 7th current one is the luckiest
when u pull your battery out take out external sd and sim card make sure u leave your phone without any charged components leave it off for 10 min hook up charger putt battery in .
Well apparently, after flashing the latest AOKP for my phone, it keeps on rebooting itself at random time, and at other times, doesent boot at all. When I put it on charge, it shows the battery for a few seconds. I am unable to get in to recovery as it basically reboots there as well. In Download mode, I restored stock 2.1 FW and bootloaders carefully, but nothing, its still giving me an issue? Any advice, might just move on to the Galaxy Nexus
Did you do any flagrant battery pulls lately? Maybe check the contacts or that the battery fits snugly. Doubt that flashing caused it, but maybe something with the kernel power source.
I got it to boot into stock recovery, but after that nothing. Is there a way to fix it, i even tried a replacement battery but no cigar. Phone has plenty of potential.
There's no need for n extensive backstory because rooting, flashing, etc I am pretty familiar with, having first rooted the old HTC Thunderbolt.
Now here's what happened:
I have quite a few roms for the S4 but the BoneStock 1.1.4 rom by Andybones always kept bringing me back. I pretty much settled for that one as my dail driver and kept it so for at least 2 months.
Recently in the past week i started getting notifications on my internal sys memory almost out. So i check and realize that my Google Play Music is almost at 6 gb, so I decide to wipe my entire phone just to give it a fresh new flash. Flash goes well, fresh install. I hardly have the time to let my phone die, so I usually just charge it regardless (I have a 5200 mAh extended battery) but this time I decided to let it die. Once it did, i put it to charge immediately and thats when i noticed something was wrong. It was stuck at the battery logo, the animated one that charges while your phone isn't on yet? Well the circle that spins and sort of 'detects' how much battery is left is stuck there. Even if i disconnect my charger it stays there.
So i did what's natural and battery pulled. Did that, reconnected my phone, still the same thing. Now i tried multiple times to get it to turn on and what not but it won't. It gets stuck at the samsung boot logo, no idea why.
So i've decided to call it a night (3 am here, work in the afternoon) and hopefully this thread gets seen by someone who knows how to deal wth this.
TL;DR Clean re-flash of the same daily driver (BoneStock 1.1.4) and let my phone die because I realize I never let it die. Once it does, it get stuck at both the Samsung boot logo, or the animated battery charge circle. I tried accessing recovery, and while I see the little blue message top left hand corner, it just seems to shut itself off, and boot back up only to be stuck again. I have no idea what happeend, I never mess with system functions or any thing of that sort.
The only real solution I see if restoring to stock firmware through Odin? Hopefully that will work, but anyone else experience this before? or something similar and can shed some light on this weird situation?
Thanks in advance!
EDIT: I apologize for the bad grammar, I've been trying to figure this out for the past 2 hours, and it's very late right now.
FriendlyNeighborhoodEnt said:
There's no need for n extensive backstory because rooting, flashing, etc I am pretty familiar with, having first rooted the old HTC Thunderbolt.
Now here's what happened:
I have quite a few roms for the S4 but the BoneStock 1.1.4 rom by Andybones always kept bringing me back. I pretty much settled for that one as my dail driver and kept it so for at least 2 months.
Recently in the past week i started getting notifications on my internal sys memory almost out. So i check and realize that my Google Play Music is almost at 6 gb, so I decide to wipe my entire phone just to give it a fresh new flash. Flash goes well, fresh install. I hardly have the time to let my phone die, so I usually just charge it regardless (I have a 5200 mAh extended battery) but this time I decided to let it die. Once it did, i put it to charge immediately and thats when i noticed something was wrong. It was stuck at the battery logo, the animated one that charges while your phone isn't on yet? Well the circle that spins and sort of 'detects' how much battery is left is stuck there. Even if i disconnect my charger it stays there.
So i did what's natural and battery pulled. Did that, reconnected my phone, still the same thing. Now i tried multiple times to get it to turn on and what not but it won't. It gets stuck at the samsung boot logo, no idea why.
So i've decided to call it a night (3 am here, work in the afternoon) and hopefully this thread gets seen by someone who knows how to deal wth this.
TL;DR Clean re-flash of the same daily driver (BoneStock 1.1.4) and let my phone die because I realize I never let it die. Once it does, it get stuck at both the Samsung boot logo, or the animated battery charge circle. I tried accessing recovery, and while I see the little blue message top left hand corner, it just seems to shut itself off, and boot back up only to be stuck again. I have no idea what happeend, I never mess with system functions or any thing of that sort.
The only real solution I see if restoring to stock firmware through Odin? Hopefully that will work, but anyone else experience this before? or something similar and can shed some light on this weird situation?
Thanks in advance!
EDIT: I apologize for the bad grammar, I've been trying to figure this out for the past 2 hours, and it's very late right now.
Click to expand...
Click to collapse
I would tend to agree odin the full wipe stock image back and start over
FriendlyNeighborhoodEnt said:
There's no need for n extensive backstory because rooting, flashing, etc I am pretty familiar with, having first rooted the old HTC Thunderbolt.
Now here's what happened:
I have quite a few roms for the S4 but the BoneStock 1.1.4 rom by Andybones always kept bringing me back. I pretty much settled for that one as my dail driver and kept it so for at least 2 months.
Recently in the past week i started getting notifications on my internal sys memory almost out. So i check and realize that my Google Play Music is almost at 6 gb, so I decide to wipe my entire phone just to give it a fresh new flash. Flash goes well, fresh install. I hardly have the time to let my phone die, so I usually just charge it regardless (I have a 5200 mAh extended battery) but this time I decided to let it die. Once it did, i put it to charge immediately and thats when i noticed something was wrong. It was stuck at the battery logo, the animated one that charges while your phone isn't on yet? Well the circle that spins and sort of 'detects' how much battery is left is stuck there. Even if i disconnect my charger it stays there.
So i did what's natural and battery pulled. Did that, reconnected my phone, still the same thing. Now i tried multiple times to get it to turn on and what not but it won't. It gets stuck at the samsung boot logo, no idea why.
So i've decided to call it a night (3 am here, work in the afternoon) and hopefully this thread gets seen by someone who knows how to deal wth this.
TL;DR Clean re-flash of the same daily driver (BoneStock 1.1.4) and let my phone die because I realize I never let it die. Once it does, it get stuck at both the Samsung boot logo, or the animated battery charge circle. I tried accessing recovery, and while I see the little blue message top left hand corner, it just seems to shut itself off, and boot back up only to be stuck again. I have no idea what happeend, I never mess with system functions or any thing of that sort.
The only real solution I see if restoring to stock firmware through Odin? Hopefully that will work, but anyone else experience this before? or something similar and can shed some light on this weird situation?
Thanks in advance!
EDIT: I apologize for the bad grammar, I've been trying to figure this out for the past 2 hours, and it's very late right now.
Click to expand...
Click to collapse
When you see the blue text for recovery do you continue to hold the buttons down until you see the recovery screen? If you take your fingers off it will do what your describing. If you can get into recovery reflash your ROM.
Sent from my Nexus 7 using XDA Premium 4 mobile app
I'm new to this site so if this thread is in the wrong place, please redirect me to the appropriate section.
A couple days ago, my GSR had shut off for no reason that I could find, and would not turn on (even to try to boot in recovery mode) for 2 hours(it would go into the boot screen but would then shut off after 5-7 seconds of "booting up"), when suddenly it started working again. I couldn't figure out why it stopped working or why it suddenly starting working again. I even changed batteries but that didn't influence anything. Then, exactly (I mean exactly) 24 hours later at the same time, it shut off again. This time, it won't even show the boot logo, and instead says, for less than a second "Movinand checksum confirmation fail." It is rooted, but has been rooted for almost a year with no real modifications done to the device and no previous issues that I noticed. I have tried changing batteries, trying different chargers, replacing the SIM and SD, and tried booting into recovery but has no effect because it shuts off before I can even do anything to it. I've seen a lot of places say wipe cache partition by going into recovery mode, but that's just not possible with what is going on. I try every other hour to see if it has somehow started working again, but now won't even show the "movinand checksum..." message. It is charged because it has been plugged in most of the time that this has been going on. It's not water damaged, I have never dropped it, and it hasn't been exposed to any intense heat or coldness ever in its life. I'm at a loss here, not sure what to do, as it seems I've tried nearly everything. I'm welcoming any suggestions you may have, as well as answering any questions about the situation.
In Need of Dire Help! Galaxy S Relay 4G(SGH-T699) Completely Bricked?
XmashMAN said:
I'm new to this site so if this thread is in the wrong place, please redirect me to the appropriate section.
A couple days ago, my GSR had shut off for no reason that I could find, and would not turn on (even to try to boot in recovery mode) for 2 hours(it would go into the boot screen but would then shut off after 5-7 seconds of "booting up"), when suddenly it started working again. I couldn't figure out why it stopped working or why it suddenly starting working again. I even changed batteries but that didn't influence anything. Then, exactly (I mean exactly) 24 hours later at the same time, it shut off again. This time, it won't even show the boot logo, and instead says, for less than a second "Movinand checksum confirmation fail." It is rooted, but has been rooted for almost a year with no real modifications done to the device and no previous issues that I noticed. I have tried changing batteries, trying different chargers, replacing the SIM and SD, and tried booting into recovery but has no effect because it shuts off before I can even do anything to it. I've seen a lot of places say wipe cache partition by going into recovery mode, but that's just not possible with what is going on. I try every other hour to see if it has somehow started working again, but now won't even show the "movinand checksum..." message. It is charged because it has been plugged in most of the time that this has been going on. It's not water damaged, I have never dropped it, and it hasn't been exposed to any intense heat or coldness ever in its life. I'm at a loss here, not sure what to do, as it seems I've tried nearly everything. I'm welcoming any suggestions you may have, as well as answering any questions about the situation.
Click to expand...
Click to collapse
Edit, 11/12/2014: As of today, I managed to get myself into ODIN mode, but will only stay in ODIN mode for about
5 seconds before it shuts off. I can repeatedly do this as much as I want, but does not change anything to how long before it shuts off. I've tried rebooting through adb reboot-bootloader, but since my pc cannot find my device, I get this error "error: device not found". I made sure the drivers are installed, as they needed to be for me to even root my phone, but still no other results.
Also, when I take the battery out and put it back in, it vibrates as if it will boot up, but then red text saying "Movinand checksum..." comes up for a split second, then vibrates again with the same text. Then I can't do anything else until I remove the battery. I'm thinking about getting a JIG that will force it into download mode or recovery mode if one even exists.
XmashMAN said:
Edit, 11/12/2014: As of today, I managed to get myself into ODIN mode, but will only stay in ODIN mode for about
5 seconds before it shuts off. I can repeatedly do this as much as I want, but does not change anything to how long before it shuts off. I've tried rebooting through adb reboot-bootloader, but since my pc cannot find my device, I get this error "error: device not found". I made sure the drivers are installed, as they needed to be for me to even root my phone, but still no other results.
Also, when I take the battery out and put it back in, it vibrates as if it will boot up, but then red text saying "Movinand checksum..." comes up for a split second, then vibrates again with the same text. Then I can't do anything else until I remove the battery. I'm thinking about getting a JIG that will force it into download mode or recovery mode if one even exists.
Click to expand...
Click to collapse
The jig is for getting the phone into Download Mode, but I don't believe it's any help in keeping it there. If the phone won't stay in Download Mode, even with a charged battery, then I fear the phone is a lost cause. The only other thing that might help at this point would be a JTAG service, if it's available for that device like it is for the more popular Samsungs.
es0tericcha0s said:
The jig is for getting the phone into Download Mode, but I don't believe it's any help in keeping it there. If the phone won't stay in Download Mode, even with a charged battery, then I fear the phone is a lost cause. The only other thing that might help at this point would be a JTAG service, if it's available for that device like it is for the more popular Samsungs.
Click to expand...
Click to collapse
I'm not sure what I did, but I'm able to stay into ODIN mode for as long as I want. I'm still unable to boot into recovery. Is it possible to restore my phone through ODIN?
Sorry, I misunderstood. I thought you had said it reboots while in Download Mode. If it stays there, then that's definitely the 1st thing to try.
es0tericcha0s said:
Sorry, I misunderstood. I thought you had said it reboots while in Download Mode. If it stays there, then that's definitely the 1st thing to try.
Click to expand...
Click to collapse
Well, it stopped turning off while in download mode just recently. I'm just not sure what caused it. Also, I noticed that the battery I had in my phone when it first started shutting off is slightly bloated. I'm not sure if it's serious enough, but I know that bad batteries bloat, and they can potentially cause issues with your device. But I put my default battery in, but it didn't change anything in regard to the movinand error.
The Galaxy S Relay 4G can be a very odd challenge.
XmashMAN said:
Well, it stopped turning off while in download mode just recently. I'm just not sure what caused it. Also, I noticed that the battery I had in my phone when it first started shutting off is slightly bloated. I'm not sure if it's serious enough, but I know that bad batteries bloat, and they can potentially cause issues with your device.
Click to expand...
Click to collapse
Wow! I'm just making a note here as a marker I can return to and follow up on. This seems almost the worst that anyone can deal with. If the person that made this post just so happens to still be around, or for anyone who may be unfortunately dealing with such an issue, I have an either or "possible" fix, yet haven't been in this particular situation. There are repair files for this device I would assume could be used for this. I'm dropping them, and the last official Samsung software issued for the SGH T699. If I so much as even get a hint my device is going in this direction, I usually flash in the original firmware if and when I can. Back it up and flash it again just to make sure I have a clean build. I can work with stock. It's hard to work with a brick. This device can be very strange so far with any results I'm getting. Which is odd to me on one level because I've haven't had as much difficulty with any of my other devices such as I'm having with this one. I always try to be prepared for any eventuality before I start working on "any" device. I'd call it a very important suggestion, especially for this Galaxy S Relay 4G, to prepare yourself, it's going to be a fun ride!