I got the 4.3 OTA update on 12.26.13, and was obviously excited. Sadly, whenever I remove the device from a charger and turn the screen off (not exactly a rare combination), the device will vibrate twice and reboot.
Things I've tried:
- Swapping out the battery
- Rebooting into safe mode
- Wiping Dalvik cache
- Factory data reset
- Factory data reset again
I spoke to Verizon, and they were of no use. They transferred me to Samsung, who said that my device is out of warranty, therefore I would have to pay for a repair. Really? From a software update while sitting on the nightstand? My argument fell on deaf ears.
I've already told them to eff off, and if I'm going to have to pay out of pocket to buy a new phone, I'm getting a N5 and going to ATT. Well, that's present tense now. Anyway, I'd love to fix the device to have it as a spare wifi device while traveling or to sell. Thoughts?
Plug it into the PC and run the installer that pops up. It will reload the 4.3 update and repair any issues.
Sent from my SCH-I535 using xda app-developers app
Hi Chatham7, were you rooted or 100% stock before taking the update? Did you have a custom rom or recovery before the update?
Sent from my Last Ever Samsung Device.
5ft24 said:
Plug it into the PC and run the installer that pops up. It will reload the 4.3 update and repair any issues.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
What installer? I've never seen one before. I have it in USB debugging right now, as I rooted it yesterday in attempt to try to resolve the issue.
0331 said:
Hi Chatham7, were you rooted or 100% stock before taking the update? Did you have a custom rom or recovery before the update?
Sent from my Last Ever Samsung Device.
Click to expand...
Click to collapse
100% stock with no modifications before the update.
If you prefer odin you can get the official tar now http://forum.xda-developers.com/showthread.php?t=2586319
Thanks, guys. I was able to re-install the update after some massaging of drivers and various other annoying hardware tweaks. However, it hasn't resolved the issue. My initial thought was that it was a hardware issue, but a hardware issue the very second after getting the 4.3 update? Just too coincidental for me.
chatham7 said:
Thanks, guys. I was able to re-install the update after some massaging of drivers and various other annoying hardware tweaks. However, it hasn't resolved the issue. My initial thought was that it was a hardware issue, but a hardware issue the very second after getting the 4.3 update? Just too coincidental for me.
Click to expand...
Click to collapse
It has to be hardware if you're 100% stock, your phone just isn't playing nice with the new update.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
It has to be hardware if you're 100% stock, your phone just isn't playing nice with the new update.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Agreed, sorry I wasn't being clear. I meant that it couldn't be a device issue caused by me (as Samsung and Verizon are implying), but rather a hardware compatibility with the new update. Their knee-jerk solution to everything is to use warranty and insurance. I'm not buying insurance to protect myself against them sending me software updates that will ruin my device. That's like paying protection money to the mob so that you don't get robbed.
Related
Getting tried of watching my phone reboot. If going back to stock would resolve the issue I would do it. I called big red today and the pinhead I spoke to acted like it was the first time anyone had called about the TB rebooting on it's own. I'm looking at going to a different phone. I really think at this point it is a software issue that they need to correct. Just like with most businesses things are not addressed until they become a problem. So my thought is we should set a date when every one calls in to report their rebooting phones. We do this every week until we get a resolution. Anyone with me?
Wait... You are rooted and getting reboots? Are you on gb? Did you root or install your rom properly? What kernel?
Stock I had no issues. Non-Gb I've had mostly no issues... Some kernels less reliable than others, of course. But to be honest it sounds more like a user issue than a tb issue
Sent from my ADR6400L using XDA App
Sent from my ADR6400L using XDA App
Are you near a Verizon store? Verizon is usually very easy to convince that you need your phone replaced. (Although I think they will only replace it with the same model. But I'm not sure.) My Thunderbolt never reboots on its own but I know it is a problem that many Thunderbolts are experiencing, so maybe yours (and many others) is/are defective. I'm 99% sure if you go into a Verizon store and tell them that it randomly reboots all the time, they'll replace it for you.
I reverted back to stock and haven't had a single reboot or loss of data on three days. Just sayin'.
Sent from my ADR6400L using XDA App
I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.
Funny how VZW is changing their stance on it, almost as if it never has happened. About a month ago I went into a store and they told me that Im not the only one experiencing problems and that there will be a fix within 2 months.
I called VZW tech support and they told me that no one else is having reboots.. . . . I dont get it.
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App
sethschmautz said:
Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
No, but each flash has two radios
Sent from my ThunderBolt using XDA Premium App
Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
Any issues with tethering or gps using the old radios?
Sent from my ADR6400L using XDA App
Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
I still had reboots with both at .6, currently trying cdma.7/LTE.6.
Sent from my ADR6400L using Tapatalk
It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App
satseaker said:
It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I would love to think its a hardware issue, but my phone was solid from day one. Then I took the update and get these random reboot.
Sent from my ADR6400L using XDA App
It is not a hardware issue. It is a problem with the update and how certain phones installed it. Verizon is in the process of making a new update and has been working on it with HTC for a little while now & expect to have it going out this month. For some reason the software does not talk to the towers properly with some models & the hardware does not get the proper info which causes the reboots. Exactly how to tell which phones are affected, I don't know. My friend is trying to find out for me.
I can say that I ran my phone with rooted stock & moved up to the rooted update when it was available which I am still on and I have not had any issues at all besides the low recorded video audio which the update seems to have fixed for me.
My phone is:
Rooted stock & radios w/update
Adrynelynes 4.47 Kernal
I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App
I didn't do the update over the air on my other bolt, I downloaded it from HTC and it killed the phone,but the same download is on this phone and it works just fine,not one reboot, and its still stock and not rooted. The other one was dated Dec
10 and this one is dated Feb 11, I would just about guess they tweaked the update to weed out the bad phones faster,makes sense to me.
Sent from my ADR6400L using XDA Premium App
satseaker said:
I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I wasn't aware of HTC stating there was some defective hardware. Never saw any references to it. If thats the case then glad they acknowledged it.
It's definitely not a hardware issue. Its a radio/ signal issue. Verizon does know about it, and is working on getting a new update out there. I know this, for a fact.
Sent from my ADR6400L using XDA App
jett2314 said:
I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.
Click to expand...
Click to collapse
My TBolt is not rooted and before the update I had no problems at all but after the update the random reboots started. Battery life is acceptable but could be allot better.
Called Verizon yesterday and they acknowledge the problem and actually said HTC is aware of the problem and are working on it but have no expected date as to when it will be fixed. I believe it is definitely is a software issue and will be fixed when the official Gingerbread is released. Just my 2 cents.
I am totally new heree and not sure if this is the right place to post this. Please bear with me.
I updated my G2X when the Gingerbread version first came out. I just noticed that it still automatically rebooted itself twice last night while I was reading. The G2X was right nest to me and I heard the T-Mobile tone while it rebooted. Has anyone experienced this? I thought this update shall fix this bugging issue. I also notice the battery drains faster. Anyone knows how to root it after gingerbread update? Thanks.
traveljazz said:
I am totally new heree and not sure if this is the right place to post this. Please bear with me.
I updated my G2X when the Gingerbread version first came out. I just noticed that it still automatically rebooted itself twice last night while I was reading. The G2X was right nest to me and I heard the T-Mobile tone while it rebooted. Has anyone experienced this? I thought this update shall fix this bugging issue. I also notice the battery drains faster. Anyone knows how to root it after gingerbread update? Thanks.
Click to expand...
Click to collapse
A factory reset after I did the update has helped me avoid all issues.
tmo will replace it. you just need to speak with them and not the first person you get. The first person I think are outsorced and they will transfer you to tmo tech guys.
jimcarroll said:
tmo will replace it. you just need to speak with them and not the first person you get. The first person I think are outsorced and they will transfer you to tmo tech guys.
Click to expand...
Click to collapse
you mean calling customer service? or in store?
Yea get that ***** replaced. there are good ones out there you just need to find it..
Factory reset after the update fixed it for me to.
jabhome said:
A factory reset after I did the update has helped me avoid all issues.
Click to expand...
Click to collapse
Yup, go to the privacy menu and use the option.
The simple act of doing a reset does a lot for a smart phone.
I had an Iphone 3g where after 4.2.1 the solution to speed was to do 2 factory resets in a row.
Some people will return a laptop because they don't want to do a reboot.
------------After the reset, go to the marketplace and the first thing install the T-Mobile My Account app. The original version is problematic and can lead to buggieness
tombaker1 said:
Yup, go to the privacy menu and use the option.
The simple act of doing a reset does a lot for a smart phone.
I had an Iphone 3g where after 4.2.1 the solution to speed was to do 2 factory resets in a row.
Some people will return a laptop because they don't want to do a reboot.
------------After the reset, go to the marketplace and the first thing install the T-Mobile My Account app. The original version is problematic and can lead to buggieness
Click to expand...
Click to collapse
If you return a phone to Tmobile before doing a factory reset to see if it solves your problem then you simply don't value your time. A factory reset takes all but five minutes. If you call Tmobile you will have to wait for them to ship you a phone, and when it arrives it will be in "factory reset" condition anyway. If you go to a retailer and pick a replacement up, it too will be in the same condition. So if you are going to get a reset replacement, everyone would be wise to try a reset before rushing to Tmobile.
I had the same problems with GB after the update- I didnt do a factory reset though.
Moved to Eagles Blood and seems like a much more stable and cleaner rom- havent tested enough to see if it reboots or not though.
To root, flash clockwork mod recovery using nvflash and install a rooted rom. There's a rooted version of gb stock out there, or you could be adventurous and install one of the many custom ones we have.
Sent from my Nexus 3 using XDA Ultimate App
Return your broken phone ASAP. Phones should not randomly turn off or reboot. It is broken. Do not try to fix a broken phone on your own. It will result in nothing but headaches. Take it back now!
Yeah my replacement phone still randomly dies, I'll come back in a few hours and have to do a battery pull. It doesn't reboot like the old one but it does die more.
Should I get the replacement replaced?
Horsey said:
I had the same problems with GB after the update- I didnt do a factory reset though.
Moved to Eagles Blood and seems like a much more stable and cleaner rom- havent tested enough to see if it reboots or not though.
Click to expand...
Click to collapse
I ran Xboarders OTA GB with no tweaks since it came out. I then switched to EB 1.07 and had a ton of issues. I then returns to Xboarders OTA tweak and it was flawless. Now I am on to Weapon G2x.
Like I said, I really think a good scrub down and wipe, i.e. factory reset does wonders, at least folks should give it a try.
I absolutely agree that theres a good, actually great batch out there, I have NEVER had a single issue with my phone and its bone stock on 2.2.
Sent from my LG-P999 using XDA Premium App
so are you doing this in the store? or calling customer service?
So auto reboot issue is the only issue you people are facing in this mobile phone?
Returned phone . New works flawlessly. Tmo is aware of the issue. When u call you will talk first with an outsourced person. Get past them they will transfer u to tmo who will pretty much no questions asked process ur return
Sent from my LG-P999 using XDA App
Mine is still rebooting and having problems, i factory reset twice and still having issues. What should i do now?
same problem with my g2x and my wifes g2x...is there a solution for this?
I bought from ebay after reading reviews that the phone works find after gb update.....that means going back to tmobile is not an option for me
Sonic Marvel said:
Mine is still rebooting and having problems, i factory reset twice and still having issues. What should i do now?
Click to expand...
Click to collapse
Purchase at eBay does not affect 1-year warranty.
Hey so after a few days of the new update running OK I started having random reboots! I noticed on a few other sites people complaining about the same issue of reboots multiple times of the day! Just wanted to let everyone know a possible solution to the issue! I have went through multiple FDR's and did come to the conclusion that the random reboots for my phone were associated with a new update to the chrome browser and were easily fixed by uninstalling new update and telling it not to automatically update so hope this helps anyone who may be having the same issues!!!
Well so much for that after trying everything its back to rebooting again? I love my phone but seriously considering putting it against a wall!!!
xgshortbus25 said:
Hey so after a few days of the new update running OK I started having random reboots! I noticed on a few other sites people complaining about the same issue of reboots multiple times of the day! Just wanted to let everyone know a possible solution to the issue! I have went through multiple FDR's and did come to the conclusion that the random reboots for my phone were associated with a new update to the chrome browser and were easily fixed by uninstalling new update and telling it not to automatically update so hope this helps anyone who may be having the same issues!!!
Well so much for that after trying everything its back to rebooting again? I love my phone but seriously considering putting it against a wall!!!
Click to expand...
Click to collapse
Never had that issue with the new update. Try doing a factory reset or try the new fast boot files to start fresh. Not sure why chrome would be an issue.try the chrome beta version but I suspect chrome had nothing to do with the reboot just a bad initial update.
Sent from my DROID RAZR HD using Tapatalk 2
Fixed!! I hope!!!
Finally broke down done a fast boot to the new files all is working seems OK anyway know in a day or 2!!!
xgshortbus25 said:
Finally broke down done a fast boot to the new files all is working seems OK anyway know in a day or 2!!!
Click to expand...
Click to collapse
My Wife's phone is doing the Random Reboot thing since the 4.1.2 update as well. I did a Factory Reset on it and it still does the same thing.
I suspect an application is doing it? Because I put the phone in Safe Mode and it never rebooted while in Safe Mode.
But I have No Idea of how to tell which app is doing it, other than to uninstall a random app after every reboot to find out which one it is.
But I would like to try this fast boot option? I know how to get the phone into fastboot, but which files are you redoing? What exactly are your doing ?
Have the same problem. I have done:
SBF 4.1.2
FDR
WIPE
Even tried running a parallel rom with safestrap (bakatang)
The chrome thing did not work
Keeps freezing. Seems the problem is way worse when having the phone play some music.
I am just about unlocking the thing and SBFing back to 4.1.1 but not really interested into unlocking the bootloader. That would be the last choice for me.
If someone knows of some way to fix this, please help, this used to be a great phone...
No problem here with the sfr rom... used for over 1 month now and no problem and my system is always fast...
Sent from my XT925 using xda premium
I've been running some tests for about a week now since I got my RAZR and the results are interesting... I've had lockups and reboots multiple times a day, most often while doing something involving sound i.e. listening to music or playing a game or video. I've tried stock and custom 4.1.2 ROMs and custom 4.2.2 ROMs and it persists so I'm inclined to say its either bad audio software or faulty audio chips. This is everything I've done:
1. turning off sounds (keeping phone on vibrate/silent) pretty much eliminates the random lockups/reboots I got from receiving multiple texts or calls at once. I noticed if I bombarded the phone and made it ring a lot it gave the same results as listening to music but if its just a text or email or call here and there during regular use it the phone works fine.
2. Listening to music, either streamed or local from phone/SD storage and through headphones or speaker, would cause skips and audio cutting out. After a few minutes of this the phone will lock up completely and reboot itself. Strangely enough it happened only rarely or not at all while streaming music via bluetooth to a stereo.
3. I don't think its anything kernel related or if it is its not causing visible errors or wake locks. My battery seems to be just fine through all this.
4. I have tried multiple music/video players, put my SD card with music in another phone and the music plays fine, stock ROMs with nothing disabled/removed still has the issue, custom ROMs debloated and modified also have the issue. I think I've just about covered every base I can as an end user to track down what's causing it but I'm open to suggestions.
I have a replacement scheduled so I will see if that fixes it, I have seen this problem reported quite a few times all over the interwebz but there are also a lot of people not having the issue either so idk. If there are any Devs or anyone skilled in android-fu that can read logcats I will be more than willing to get those for you. Sorry for the essay everyone lol
tl;dr Like others I have freezes and reboots from what seems to me to be an audio software/hardware problem, either built in or from the 4.1.2 update
Sent from my DROID RAZR HD using Tapatalk 2
I am almost sure is kernel related bc I did not have problems in the 4.1.1 sw.
If someone that has an unlocked bootloader could install 4.1.1 from an sbf and tell if the problems are gone, would be great!
here is the sbfs: http://sbf.droid-developers.org/vanquish/list.php
here is the bl unlocker: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
u have to be rooted here: http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit-412/?pid=244281#entry244281
I am not doing that bc I do not use custom roms so dont want to unlock BL. If someone has, this could help much. It is different from using safestrap, because safestrap uses the same kernel, from what I read.
barbaroja said:
I am almost sure is kernel related bc I did not have problems in the 4.1.1 sw.
If someone that has an unlocked bootloader could install 4.1.1 from an sbf and tell if the problems are gone, would be great!
here is the sbfs: http://sbf.droid-developers.org/vanquish/list.php
here is the bl unlocker: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
u have to be rooted here: http://www.droidrzr.com/index.php/t...roid-root-exploit-412/?pid=244281#entry244281
I am not doing that bc I do not use custom roms so dont want to unlock BL. If someone has, this could help much. It is different from using safestrap, because safestrap uses the same kernel, from what I read.
Click to expand...
Click to collapse
I have seen reports that the problem persists even on 4.1.1 but I am unlocked and rooted on stock 4.1.2 so if I get time I can give it a try
Sent from my DROID RAZR HD using Tapatalk 2
anoninja118 said:
I have seen reports that the problem persists even on 4.1.1 but I am unlocked and rooted on stock 4.1.2 so if I get time I can give it a try
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
When I was at 4.1.1 phone was near perfect.
If you are unlocked, please do check. I am debating whether to unlock or not just bc of this. Today it has resetted at least a good 20 times or so.
Thanks for helping!!! Waiting for your results!!!!
barbaroja said:
When I was at 4.1.1 phone was near perfect.
If you are unlocked, please do check. I am debating whether to unlock or not just bc of this. Today it has resetted at least a good 20 times or so.
Thanks for helping!!! Waiting for your results!!!!
Click to expand...
Click to collapse
one solution that has worked for me is silencing the phone or putting it on vibrate and I haven't had a freeze or reboot in almost 2 days... the problem seems to me to be related to audio/sound and not listening to music or watching videos along with silencing ringtones has put a stop to it which kind of confirms my suspicions... I will try and flash back when I can but it'll need a day or 2 of field testing to confirm if its a solution
Sent from my DROID RAZR HD using Tapatalk 2
I can confirm that audio stuff just does worse to the phone. However, I have not had your luck when silencing. Keeps rebooting no matter what. Please let us know when you do.
barbaroja said:
I can confirm that audio stuff just does worse to the phone. However, I have not had your luck when silencing. Keeps rebooting no matter what. Please let us know when you do.
Click to expand...
Click to collapse
looks like a negative on the SBF, tried to restore 4.1.1 and it failed halfway through the flash, now won't turn on... working on reviving it... I really need to replace this thing as its been nothing but a PITA since I got it
old school post from my Thunderbolt via Tapatalk
wow that sucks. I recall reading somewhere that you could actually downgrade your software version if you have an unlocked bootloader.what is the error you are getting? Tried using RAZR utility 1.1? Won't it turn on at all? Maybe a discharged battery? Hope we can solve it
barbaroja said:
wow that sucks. I recall reading somewhere that you could actually downgrade your software version if you have an unlocked bootloader.what is the error you are getting? Tried using RAZR utility 1.1? Won't it turn on at all? Maybe a discharged battery? Hope we can solve it
Click to expand...
Click to collapse
got it revived with Mattlgroff's new 1.2 utility, was able to force it to fastboot mode... the problem seemed to be some kind of partition error, I tried redownloading the sbf files thinking it was a bad file and got the same error so idk what it is since I'm on stock unrooted 4.1.2. My bootloader is already irreversibly unlocked so that won't be a problem lol but I am a n00b to RSD Lite and Moto devices so I'll tinker with it more when I get some free time
edit: I did have a Maxx HD way back at launch for a month or so running stock 4.1.1 and it ran perfectly, so my idea is its kernel/codec/software related. Hopefully a custom ROM (or hell even stock) with Hashcodes Qcom kernel will fix the issue we're having
Sent from my DROID RAZR HD using Tapatalk 2
I talked with vzw service, the assistant said that 2% of the phones were having this issue, wich for this kind of technology is a pretty big number of phones. Suuggested to send it to Motorola but since its rooted its almost sure not to be replaced by them. What is strange is that not everyone is having this issue. I would be almost sure Motorola is going to release a fix for this, but would not count days. Getting kind of frustrated with this phone I used to like so much. Thinking of going the htc route bc this is getting unbearable.
Any news in this? Anyone tried a new ROM that could solve this? Or even a fix?
... or just everyone had another phone lying aroud...
barbaroja said:
Any news in this? Anyone tried a new ROM that could solve this? Or even a fix?
... or just everyone had another phone lying aroud...
Click to expand...
Click to collapse
My wife & I both have this phone and still are constantly being rebooted. This is even after the software update. I have been wiped, factory reset, and everything possible, but I've not called for a replacement yet. Normally I havea worse luck with those.
Wife used to love this phone, now she hates it and hates we changed from AT&T to Verizon since we have no backup Verizon phones. At least we could take the sim out and go to the iPhone that's floating around the house when the phone went to pot before. Makes me really hate suggesting that we go back to Moto phones since that's all that I've used on Verizon.
Wonder if big red will get the new HTC One....
Tried flashing the MR-4 sbf, but did not solve the issue.
Sent from my GT-I9100 using Tapatalk 2
barbaroja said:
Tried flashing the MR-4 sbf, but did not solve the issue.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
If an sbf didn't solve it then it's a hardware problem.you guys are definitely in the minority with this reboot issue.go get a warranty replacement.this phone and moto in general are solid phones.
sent from my xt926 RAZR maxx hd
I am having trouble with my Galaxy S3 (SCH-I535), mainly the touchscreen does not respond to input, but still has a display. This all came about after I tried rooting and updating the ROM. I was able to successfully root and unlock bootloader, but then I tried doing a system update via the Stock ROM and upon a restart my touchscreen stopped working. I tried a factory reset from stock recovery and now I am stuck on the the screen that says Language selection English, Espanol, and some other languages. The 2 soft keys on either side of the home button respond to touch (make a noise and light up the screen, but do nothing for the screen I am on). Volume rocker works fine, I just cant move forward in the screen!! Like I said, I am able to get into stock recovery, as well as ODIN.
I bought this phone on eBay and just got it activated this past Thursday. Samsung told me the phone is out of warranty. The ebay seller said it came from Amazon and might have a receipt, but I'm not sure if that would even help anything. Can someone tell me what my options are in this situation? Screen replacement? Soft brick?
Thanks!
Anyone?
Bump
Any help is most appreciated...thanks!
I would Odin back to stock. Sounds like you updated to 4.3 so just Odin to 4.3 and factory reset after. If that does not fix it then it's a hardware problem. Do you have a warranty?
Sent from my SCH-I535 using Tapatalk
Galaxy S3 touchscreen not working
Sandman-007 said:
I would Odin back to stock. Sounds like you updated to 4.3 so just Odin to 4.3 and factory reset after. If that does not fix it then it's a hardware problem. Do you have a warranty?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I'll try that, thanks!
No warranty...bought off eBay from a regular auction, not an agent or licensed retailer.
Still bricked...
Sandman-007 said:
I would Odin back to stock. Sounds like you updated to 4.3 so just Odin to 4.3 and factory reset after. If that does not fix it then it's a hardware problem. Do you have a warranty?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
ODIN'd to the 4.3 file in this thread http://forum.xda-developers.com/showthread.php?t=2586319 and did a factory reset, still no screen response. Looks like a hardware issue after all. I think I am at 4.3, though because the menu background looks different and so was the bootup splash.
pinto4598 said:
ODIN'd to the 4.3 file in this thread http://forum.xda-developers.com/showthread.php?t=2586319 and did a factory reset, still no screen response. Looks like a hardware issue after all. I think I am at 4.3, though because the menu background looks different and so was the bootup splash.
Click to expand...
Click to collapse
Sounds like it. Sorry bud.
Sent from my SCH-I535 using Tapatalk
How severe a hardware issue?
So I definitely have a hardware issue, but is there anyway to determine how severe (read: costly) the issue is? If I'm looking at a simple screen replacement that is under $50 I might consider, but if we are talking a digitizer that is the cost of what I paid, then fugggetaboutitttt
Any way to determine this?
pinto4598 said:
So I definitely have a hardware issue, but is there anyway to determine how severe (read: costly) the issue is? If I'm looking at a simple screen replacement that is under $50 I might consider, but if we are talking a digitizer that is the cost of what I paid, then fugggetaboutitttt
Any way to determine this?
Click to expand...
Click to collapse
It's either the LCD or Digitizer. Definitely not the glass. If you get the whole Assembly (LCD and Digitizer) its around $130 just for the part. Your call. The glass panel is only $10 but your issue is the digitizer. Might be mobo (maybe).
This link include the the glass panel too but it's only worth $10. So LCD+Digitizer=$120
http://www.amazon.com/gp/aw/d/B00D5Y42LQ
Sent from my SCH-I535 using Tapatalk
My wife's phone is a virgin mobile s5. It was only about 3 months old.
It was already on 5.0 when she purchased it.
After doing a system update, my wife's phone became unstable.
Phone will randomly freeze or sometimes makes a crackling sound
then restarts.
Any of this didn't happen at all before the update.
Any help would be appreciated
drckml said:
My wife's phone is a virgin mobile s5. It was only about 3 months old.
It was already on 5.0 when she purchased it.
After doing a system update, my wife's phone became unstable.
Phone will randomly freeze or sometimes makes a crackling sound
then restarts.
Any of this didn't happen at all before the update.
Any help would be appreciated
Click to expand...
Click to collapse
You should probably download and odin the full factory tar.
OTA updates sometimes cause problems with existing loads.
tdunham said:
You should probably download and odin the full factory tar.
OTA updates sometimes cause problems with existing loads.
Click to expand...
Click to collapse
I'm sorry? I didn't quite get that.
The only part I understood is downloading odin, which I already have. I don't want to ruin my wife's phone warranty.
Nevertheless, we already sent the device to Samsung to get it checked...
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
You could have downloaded the factory image and reflashed the phone. Hopefully they will do it for you. I'm sure that support with vm is probably pretty limited anyway.
Just got the phone back from samsung service center, they didn't even manage to fix it. Wtf