I apologize if there is already a thread on this, but I have not found an actual solution to it yet.
My Captivate's screen is on sleep mode, and maybe 20 ish minutes later, when I press the unlock button, I find that the phone is off and I have to turn it on again. This happens every 20 minutes, and the only way for me to keep it on is to frequently unlock the phone to verify that it is still on.
This is not a very practical method of doing things though, because the phone turns off in while I'm sleeping and I'm not always able to check my phone every 20 minutes.
My firmware version is 2.3.3 and I'm running Gingerbread OS. It's a refurbished phone I received from Rogers a week ago, and I really don't want to factory reset or anything like that as I have very important information/app data on my phone I don't want to have wiped.
I've heard of flashing a custom rom to fix the problem but the thread i read was from 2011. Can anyone help me with this issue? Thanks.
If you received it as a refurbished from Rogers then I would go back to them and get them to send you a new one. There was a batch of Captivates that had this issue and a new motherboard was the only true fix.
Sent from my SGH-I777 using xda premium
Is that really the only way to fix the problem? Aren't there any custom roms that might fix the problem?
They might help the issue but they will not fix it. It is a hardware defect. I had to send one back to At&t for the same issue.
Sent from my SGH-I777 using xda premium
Dude send the phone back to Rogers. Call them or go to the Rogers Plus store and explain them the problem. Tell them that you did factory reset and you're still getting the problem.
Sent from my SGH-I896 using XDA
Related
I send a phone back with a custom ROM on it? AT$T are sending me a refurbished phone because mine has the random shutdown issue (build 1007) If I don't spend the time to Odin back to JF6 before sending this one back, will they clip me somehow when they get it back and find it is not stock?
why you do not want to just a few minutes to do that ? just want to be on their list ?
My first phone had random shutdown issue...so I flashed to the first leaked 2.2 rom.
That didn't fix it, so I took it back still flashed. Nothing was ever said to me. The way I figure, if they are going to fix the phone and resell it, then they will reinstall the stock software regardless, so who cares? lol
They haven't exactly made my life easy, why shouldn't I give them the same consideration? They are just going to wipe it anyway. And what list are you speaking of?
Miami_Son said:
I send a phone back with a custom ROM on it? AT$T are sending me a refurbished phone because mine has the random shutdown issue (build 1007) If I don't spend the time to Odin back to JF6 before sending this one back, will they clip me somehow when they get it back and find it is not stock?
Click to expand...
Click to collapse
Lmao!! Dooooo it!!
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Literally it takes 1min flash stock...
Sent from my SAMSUNG-SGH-I897 using XDA App
If you really want to do it go ahead but if att is really that troublesome chances are good that they might say that was the problem and try to charge you for the new phone out of contract
Sent from my SAMSUNG-SGH-I897 using XDA App
qhsusb_dload is all I get. Buttons no work. Doesn't vibe or anything. Soft reset doesn't work. Any help or am I screwed. I flashed overcome 8.9 wiped prior and wiped dalvik after the reboot and black screen since.
Sent from my SAMSUNG-SGH-I727 using xda premium
I'm really sorry but your device is done. The skyrocket people haven't been able to fix this yet by using a jig or qualcomm tools.
Reading and researching is really important. You can't flash any p73xx rom to the i957, it will brick.
This is exactly why I have tried to get a separate forum for the i957, but that hasn't worked yet.
Hope you are under warranty or that is an expensive mistake.
Sent from my SAMSUNG-SGH-I727 using xda premium
I did the exact same thing you did. It is very confusing (Well not really, I just did'nt take my time to read). I was exhausted because I was very happy to have my new skyrocket and new lte tab. I researched and researched. I rooted, installed custom rom and kernel on my skyrocket. I then rooted my tablet and it was great. I then installed a custom rom for a 7300 on my i957 and Boom, gone. Luckily I was within my 30 day return policy. Everything in my home is either jailbroken, rooted, homebrewed, w/e. so I have somewhat experience.
But the combination of tiredness, excitedness, and what ever else comes along with getting new gadgets, I didn't pay attention and blew up my tablet.
Even with my experience and never bricking anything before, I bricked my tablet. I took it back to the store and making believe I never even heard about rooting, jailbreaking, homebrewing; the sales people tried starting it up and eventually they couldn't get it to start up. I got a new tablet, I told them I left the tablet charging overnight and left it charging when I went to work, because I forgot to disconnect it. When I got home from work it just didn't turn on.
Eventually they gave me a new tablet and said do not charge it for more than 8 hours. They said I was the first customer to ever return this tablet because it was defective (This tablet is a beast). I told them sure I learned my lesson.
When I went home, I rooted it lol and installed the oc kernel. Remember there are no roms for the 4g model.
Before I went back to the store where I purchased my phone&tablet, I found that there is a youtube store that fixes bricked phones and tablets (He has videos of him fixing them) but when I emailed him, he said their program does not support in unbricking the lte tablet. This was about a month ago so you can check to see if they support it now. I think to unbrick phones it was like 50-100 dollars (I forgot)
You are not alone, I made the same dumb mistake. Never do important stuff when you are tired or excited or anxious. Sorry man, good luck.
I may have put this in the wrong area it was late last night and I was frustrated. I tried putting a 7300 ROM on a 7300. I didn't try anything fancy lol. But I appreciate the responsses. You think I'll be able to take it back and see what they can do? Maybe they'll exchange it as if it was a defect? I'll take it there today. See if they will exchange.lesson learned for me. Lesson being wait for updates from Samsung. As slow as they are. Lol thanks for the input if anyone has the capability to fix this
Hit me up.
Sent from my SAMSUNG-SGH-I727 using xda premium
A 7300 rom on a 7300 should only soft brick. Can you get into download or recovery?
Sent from my SAMSUNG-SGH-I727 using xda premium
If you try to turn on your tablet and your screen turns on you can try to install the stock rom through odin again and it will work. There is a thread in this forums that explains how. If it is off and you turn it on and ABSOLUTELY NOTHING happens and it just stays with the black screen, no vibration or anything then it is hard bricked.
If it is hard bricked you can try to take it back and act dumb, not sure how long ago you purchased the tablet. If you are still within the 30 days you should be good because the sales people I took my tablet to did not have the machine to see how many times my device was flashed. If you are outside the 30 days they will tell you to send it to a samsung repair dealer (which I think they will see how many times the device has been flashed). Once you rooted your tablet it voids the warranty and they either do not have to fix it or will charge you an amount equal to your tablet. I did hear of cases where people with rooted tablets just returned it and they fixed it for free. I guess it dpeneds on anything else in life (How lucky are you?)
Yes you did put your question on the right place since this is for all the 8.9 tablets. (Thats the problem I came across with, I wish they make two forums for both tablets because they are in fact different.
Posting from my mobile so I didn't read your post again.
It is extremely rare but sometimes this can happen. Did you have repartition checked in Odin? If so that's bad.
There is something called qpst - qualcomm product support tools - that people are trying to get to work to fix hard bricks.
Sent from my SAMSUNG-SGH-I727 using xda premium
No prob man. I'll look that up. I'm gonna seems it in to Samsung see if they can fix it. It's under warranty. Anyone done this before?
Sent from my SGH-I727 using xda premium
mobiletechvideos now has support for hard bricked tabs! finally! just sent the payment today and i will send out my tab once i get home from work. ill keep yall posted on how it goes.
here is the link: http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-tab-8-9-jtag-brick-repair/
Thanks for updating us.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I've had it with the nexus one. I got the phone over 2 months ago and the amount of problems I have had with it are endless. To list a few
1.The screen goes dead all of a sudden
2. Cannot take calls, I cant listen to the dial tone when I make calls. Its only on speaker can I listen to the other caller
3. The battery back up is awful, I have to charge it for 5-6 hours straight
4.The music player gets stuck, the music player on the n1 sucks. Every time half way through the playlist it gets stuck and I get the wait,forceclose or report option
5. The on screen keypad is awful. I was glad to get hold of few apps that helped solve this
6. Updating of the OS, I have tried every method that has been posted in the internet to update my n1 from the outdated 2.2.1 to froyo or gingerbread. None of them have worked maybe because the files are outdated as every post or video I came across was almost 2 years old.
If anyone can help me in putting an end to this misery that would be the most helpful.
did you try super one click to root?
Sent from my Nexus One using Tapatalk
if you need help updating your phone make use of this guide http://wiki.cyanogenmod.com/wiki/Nexus_One:_Full_Update_Guide i have followed the instructions that were there and i have fully upgraded my nexus one to GB and ICS
Like said, Root the device the correct way. And if possible, use a custom ROM, preferably CM7.
if incase all your rooting method fails. u still can unlock ur bootloader and can flash cm rom
Sent from my Nexus One using Tapatalk
Thanks for the reply. I was thinking of not rooting my phone so that I can make use of the warranty. I might actually have to get a new N1 given the issues I had with this one. Do i absolutely have to root?
@omglol23: Where did you buy the phone? Should return for a repair if it is still under warranty.
I got it from the states, bestbuy to be even mor precise. But is there no way to update it without rooting the phone. This seems like an impossibility. Is there a customer care for nexus one? I get redirected to the samsung nexus s.
I tried updating to frg83d from frg83 which also failed still stuck with android 2.1, feel like crying
Dude i seriously doubt that you r having a vodafone n1....i was going through the same situation as you....for vodafone n1..follow this guide carefully
ossadmin.wordpress.com/2011/02/26/goodbye-vodafone-uk-nexus-one-rom/
Sent from my HTC Nexus One using XDA
Since you don't want to root your phone coz of the warranty, I suggest have it check try contacting HTC and see if they can repair your phone. Possibly they might be able to update it for you once they repaired it.
On most roms I am to get the half screen problem, and I was wondering if there is something I can do to prevent it.
According to T-Mobile it is a know problem. Got my replacement on order. I had the problem happen before I even rooted the phone. Seems to have gotten worse over time for me though and that's why I called to have it replaced. If your having the problem I totally recommend the same to you. I will say after trying chroma I think it has gotten more frequent even after loading up my light rom backup. I can't blame it on anything other then bad hardware though cause like I said it happened before I rooted a week into having the phone.
Hardware issue, replace it
Sent from my Nexus 6 using XDA Free mobile app
Yeah I had the issue before I rooted as well. Lol I had called tmobile for the replacement 5 min before reading this and they are sending me a replacement device. Thanks for responding though!
When to you guys called it in, do you get the normal "factory reset" troubleshooting, or do they know that this issue is random and just send a replacement? I get the issue with certain kernels, and not with others and am wondering if I should call it in.
Sent from my Nexus 6 using XDA Free mobile app
So, I've been using this wonderful device for a while now, since early October. I've finally got it set up the way I like it and all. Now, I'm just flashing ROMs to see which I prefer. Just a few hours ago, I decided to revert to the T-Mobile ANK3 (or AN-whatever) stock ROM because on Lollipop 5.0.1+ the battery dies much quicker than I'd like it to. Yet, that ROM would constantly either:
A) Die whenever it wanted to
B) Freeze and just not respond
C) Require a battery pull
D) Send me to D/L mode with "mmc_read fail".
So I decided to revert back to stock 5.0.1 because I was tired of all the bugs I was encountering with 4.4.4.
Now, every hour or so, the phone dies and gets stuck on the splash screen (with the obvious SEAndroid not enforcing + Set Warranty Bit). Or if it isn't that, the phone just outright freezes when I'm using a light application (i.e. Kik Messenger).
I'm starting to think that my eMMC is dying, because the phone was not acting like this when I first got it in early October. Every once in a while D/L mode keeps repeating my fears. I cannot send it in to Samsung because I already voided my warranty, and I am a prepaid subscriber on T-Mobile. (So, no, T-Mobile will not help me, likely.)
Any ideas on what's happening, or what I should do?
First thing I would do Is flash a different kernel
Odin back to stock and reroot the device. Sounds like something got messed up.
Sent from my SM-N910T using XDA Free mobile app
ShrekOpher said:
Odin back to stock and reroot the device. Sounds like something got messed up.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Did that, ended up having the same problems. I said screw it, and am now using CM12.1...
Although I really don't like it (because TW is now a good thing as opposed as to how bad it was on the S3), I'll settle with it. It's not so bad.
---
LMAO OOOOO I LIED TO MYSELF
even CM is force rebooting itself wwwwhat
Why can't u take it in for warranty? Out of warranty they just replaced my note 4 under warranty and it was rooted
sqmala4321 said:
Why can't u take it in for warranty? Out of warranty they just replaced my note 4 under warranty and it was rooted
Click to expand...
Click to collapse
I bought the phone second hand, and it is out of warranty. I can't fork over money right now, as seeing how replacing the eMMC chip is probably expensive. I'll probably find some hackjob way of finding a replacement, or just live with it. I also don't think reflashing the bootloader will help.
Each time I power on the phone, it seems that it keeps getting worse each time. I get the "ddi: mmc_read fail" message more often, and off a cold boot, the phone will not actually boot and I have to battery pull like 2 times before it actually boots. Gee, looks like I'm screwed.
Good news...since they know that the eMMC chip is bugging out, they'll do a free repair. Success! Now, time to go into the repair shop and hope they accept my reference ticket, since I'll be a walk in.
I can't call right now, seeing as my phone has difficulty doing ANYTHING now...
eduardog131 said:
I bought the phone second hand, and it is out of warranty. I can't fork over money right now, as seeing how replacing the eMMC chip is probably expensive. I'll probably find some hackjob way of finding a replacement, or just live with it. I also don't think reflashing the bootloader will help.
Each time I power on the phone, it seems that it keeps getting worse each time. I get the "ddi: mmc_read fail" message more often, and off a cold boot, the phone will not actually boot and I have to battery pull like 2 times before it actually boots. Gee, looks like I'm screwed.
Click to expand...
Click to collapse
actually i am having the same exact problem....i had the tmobile note 4, and its doing the same thing about 1 month ago...reboots, black screens; and all that you have mentioned. so i started to look into rooting/flashing tekxodus hd onto my phone...still the same problem...phones restarts to boot loop time to time...bad screens....i'm still trying to find outwhat the hack is going on...and the phone's warranty expireds about 1 month ago right before the phone start to act up....let me know if you find a solution to that..lol...thanks:good:
---------- Post added at 11:25 PM ---------- Previous post was at 11:17 PM ----------
ShrekOpher said:
Odin back to stock and reroot the device. Sounds like something got messed up.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
yes, i did that too...odin back to stock, still same problem...my phone was on stock when these problems started. i hoping different roms would solve the problem...so i started rooting and intalled tedxodus and the same problems...hopefully someone could help please.