Develop Bugs

[Q] Please help. 4 versions of Froyo and WIPES all give my DINC touch sreen issues.

I have tried bot 08/2# roms, SkyRaider 2.5.2, and now the rom from the leaked RUU (and done via RUU) , but all require me to connected to my DINC to PC or AC power to temp. restore multitouch to my display.
Any suggestions???
Thanks

I would get a replacement then, everyones that i have rooted have worked flawlessly. call 611 and state you need a warranty replacement due to int power

WRONG FORUM. But reinstall your stock os and take it to Verizon for replacement.

Sorry. Thanks, I will restore 2.1 update 1 non-rooted and contact Verizon. It is strange that every time I go back to 2.1 rooted or non-rotted I don't have the touchscreen problems.

wrong forum.

Galaxy S3 Shutdown

Hey guys,
starting last night my Galaxy S3 began to freeze and then randomly shut off. I then had to press the power/home button for a while for it to turn on (around 20-40secs). At first I thought it might be a battery issue, but I used another S3 battery and the issue persisted. I bought the phone in June, and it is currently unrooted but running a leaked Bell Jelly Bean rom which I installed a while ago....
Not sure what the issue could be, and I was wondering if anyone else was experiencing the same issues or if anyone had a fix?

vnsnk said:
Hey guys,
starting last night my Galaxy S3 began to freeze and then randomly shut off. I then had to press the power/home button for a while for it to turn on (around 20-40secs). At first I thought it might be a battery issue, but I used another S3 battery and the issue persisted. I bought the phone in June, and it is currently unrooted but running a leaked Bell Jelly Bean rom which I installed a while ago....
Not sure what the issue could be, and I was wondering if anyone else was experiencing the same issues or if anyone had a fix?
Click to expand...
Click to collapse
I have the same issue, I'm running 4.1.2 XXELL5 firmware, have you found something?

vnsnk said:
Hey guys,
starting last night my Galaxy S3 began to freeze and then randomly shut off. I then had to press the power/home button for a while for it to turn on (around 20-40secs). At first I thought it might be a battery issue, but I used another S3 battery and the issue persisted. I bought the phone in June, and it is currently unrooted but running a leaked Bell Jelly Bean rom which I installed a while ago....
Not sure what the issue could be, and I was wondering if anyone else was experiencing the same issues or if anyone had a fix?
Click to expand...
Click to collapse
What ROM are you running ?

Same here, started last night. I'm not running a ROM just rooted and a few apps removed. In the process of reverting to unrooted stock to see if that helps.

le0nphelps said:
Same here, started last night. I'm not running a ROM just rooted and a few apps removed. In the process of reverting to unrooted stock to see if that helps.
Click to expand...
Click to collapse
It might need a factory reset
EDIT: Ahhh I just noticed you must be on the international version. June didn't ring a bell until I remembered we didn't get carrier models until July
Might want to head over there

hednik said:
It might need a factory reset
EDIT: Ahhh I just noticed you must be on the international version. June didn't ring a bell until I remembered we didn't get carrier models until July
Might want to head over there
Click to expand...
Click to collapse
i agree on the reset. as a matter of fact, i'd suggest a full wipe, flash the appropriate stock firmware in odin and full wipe again. this tends to solve the biggest issues when users update/change android operating systems.
stock firmware thread: http://forum.xda-developers.com/showthread.php?t=1968625

xBeerdroiDx said:
i agree on the reset. as a matter of fact, i'd suggest a full wipe, flash the appropriate stock firmware in odin and full wipe again. this tends to solve the biggest issues when users update/change android operating systems.
stock firmware thread: http://forum.xda-developers.com/showthread.php?t=1968625
Click to expand...
Click to collapse
Do y'all have the i747 or the i9300 international version ? 4.1.2 was never released for north America phones and you quoted a UK version of the OS
Don't flash anything on this site unless you have a i747 or i747m

[Q] S3 Reboot Issue

Running stock 4.1.1, not rooted. Phone randomly reboots and is stuck on the samsung screen. Did a factory reset and also reloaded the firmware still no difference.
Does anyone know of a possible solution.
This happens every few hours.

When did it start doing this? Did you recently update from 4.0.4 when this began?
If you've never rooted or modded this device before and have no intentions to, I would take it down to your local at&t service and repair center for a replacement.

Take it back.
I had the same problem with my new fresh out of the box S3.
Came loaded with 4.1.1

Random Restart Issues

I have been having issues with my Note3 ever since the kit kat update back in April. It worked flawlessly on Jelly Bean and I had no issues for over 3 months. I updated to kit kat via Kies with everything completely stock. Since then I get completely random reboots, it could happen when launching an app or even unlocking the screen, and it happens 2 or 3 times a day. So far I have tried 2 factory resets, clearing dalvik cache, and replacing the battery with an Anker replacement. I have tried turning off auto-updating of apps, and turning off wifi scanning. I have also tried running the phone with no apps installed. So far nothing has worked.
I have read several posts with people blaming the stock kernal for these reboots, but there is no definitive solution to this problem. I am looking for any and all help the community has to offer.
Some additional info:
Running latest stock rom- rooted via effortless method
Stock Recovery
Knox is still 0x0
No sd card in phone

Since you have no issues doing a factory reset, I recommend the following:
1.). Backup all the data you need
2.) Download the newest carrier available firmware for you from sammobile.com
3.) Flash via Odin
4.) Once finished and phone has rebooted, return to stock recovery and perform another data wipe
That will 100% fix your issues, sounds like maybe a corrupt system partition or libs

icenight89 said:
Since you have no issues doing a factory reset, I recommend the following:
1.). Backup all the data you need
2.) Download the newest carrier available firmware for you from sammobile.com
3.) Flash via Odin
4.) Once finished and phone has rebooted, return to stock recovery and perform another data wipe
That will 100% fix your issues, sounds like maybe a corrupt system partition or libs
Click to expand...
Click to collapse
Thanks, I'll give this a try. Last night I uninstalled a bunch of bloat ware with titanium backup to make sure it's still not an app issue. If it reboots again I'll reflash the firmware. Since I'll. Be flashing stock it shouldn't trip knox right?

No, latest firmware complete stock will not trip Knox, as long as you're either doing a parallel upgrade NF9 > NF9 or NB4 > NF9. A downgrade will either fail or trip.

For anyone reading this, i tried to reflash the stock nf9 kernal to see if that was the issue, but i got a restart about 4 hours later. I am going to reflash the firmware via odin and report back.

I am having this issue for a long time. i have done everything, and finally i gave up, as i think it is a hardware issue. what make me confuse is the problem start since the day i upgrade to kit-kat. with every firmware come out i have a new problem. the latest "NF9" my phone just hang and black screen untill i press the power button for 30 second, then will restart. what make crazy is that it shuts off at night, and when i woke up i miss the alarm.

I'm sad to report that the reflash didn't work. I reflashed the NF9 firmware using odin about 4 days ago and it was fine for awhile, but I got 2 reboots today. I'm not sure what is causing this, but I am still open to suggestions. I don't think its hardware related since it didn't do this before kitkat. I still have my samsung warranty until february I believe, so if worst comes to worst then ill have to send it in, but i'm not sure what they will do about it.

The only thing I havent tried is replacing the sim card. Could a sim card cause a reboot issue like this?

i have already done it, even the SD card, still same problem.

Is there some kind of log feature in android that logs crash events or errors somewhere so i can maybe figure out what the problem is?

by the way i think i have solve my problem by updating busybox and supersu. i had to install busybox to system/xbin. and since that day i haven't encounter any restart or freez. almost 2 week. i hope that fix your problem as well.

makki666 said:
by the way i think i have solve my problem by updating busybox and supersu. i had to install busybox to system/xbin. and since that day i haven't encounter any restart or freez. almost 2 week. i hope that fix your problem as well.
Click to expand...
Click to collapse
I do not have busybox installed, and SuperSU is up to date. Also, the restarts happen with or without root ie without SuperSU. I still dont think its an app problem.
Just an update for anyone reading this. I have installed SetCPU to manage cpu clock speeds. I have had it installed for about a week and have not had an update with my custom profiles. It seems the restarts occur when cpu speed is at about ~675MHz. Not sure if its hardware or software yet. Any help is appreciated!

Update. I sent my phone in to samsung for repair. It looks like they just reflashed the firmware. After having it up and running again for 15 minutes the phone rebooted again. I contacted samsung and they recommended sending it in again. I'm not sure if it's worth it to send in again or if i should break my warranty and flash a custom rom. Any suggestions are welcome!

I get restarts because the modem crashes... its a known issue apparently

gtharea said:
I get restarts because the modem crashes... its a known issue apparently
Click to expand...
Click to collapse
I cant believe its taken over a year for this issue to get fixed. Im almost positive its a software issue since it never happened on jelly bean. It's strange that not a lot of people have this problem though. A lot of people must have already flashed custom roms I may send it in again since I still have knox 0x0 and see if they do anything else besides reflash the firmware this time. If they only do a reflash again i will just flash a new rom and hopefully everything will be fixed

Final Update:
I sent my phone back to Samsung, apparently my issues were a hardware problem. This time they replaced the "PBA assembly" aka the mainboard. I have had the phone back for almost two weeks without a single restart. I believe my restart problems are over. I hope this information helps anyone with similar issues. I would recommend sending it to Samsung for warranty repair if you are still under warranty. :good:

_bhaves_ said:
Final Update:
I sent my phone back to Samsung, apparently my issues were a hardware problem. This time they replaced the "PBA assembly" aka the mainboard. I have had the phone back for almost two weeks without a single restart. I believe my restart problems are over. I hope this information helps anyone with similar issues. I would recommend sending it to Samsung for warranty repair if you are still under warranty. :good:
Click to expand...
Click to collapse
I had the same problem but already tripped knox so iffy on sending it in. Funny thing is I did the external sd write fix and the phone has not rebooted since, going on 3 days.

meoshe said:
I had the same problem but already tripped knox so iffy on sending it in. Funny thing is I did the external sd write fix and the phone has not rebooted since, going on 3 days.
Click to expand...
Click to collapse
I would get reboots even without an SD card put in the phone, so I don't think that would have helped me. I havent had a reboot since I've had the device back

Random restarts and 'mmc_read failed' error on OTA MM update after factory reset

After flashing CM 12.1 on Lollipop (rooted w/ TWRP), I started encountering issues (lagging, random restarts, programs crashing). I proceeded to restore my backup (Lollipop) through TWRP. Updated to Marshmallow OTA. Attempted to root and flash roms on Marshmallow which also led to issues. Ran multiple factory resets after removing root and twrp. Still experiencing issues (before and after rooting) like random restarts into download mode with "Could not do normal boot. mmc_read failed" error message, screen staying off and not responding while phone is on, program freezes, and the default boot Samsung logo screen displays "Set Warranty Bit : kernel" message in top left corner.
Software version: N910PVPS4DPD1
Hardware version: N910P.05
Model number: SM-N910P
Android version: 6.0.1
Build number: MMB29M.N910PVPS4DPD1
Build fingerprint: samsung/trltespr/trltespr:6.0.1/MMB29M/N910PVPS4DPD1:user/release-keys
Baseband version: N910PVPS4DPD1
Kernel version: 3.10.40-7381751
[email protected]#1

Most likely, it's hardware failure. Do you have TEP (insurance through Sprint)? If so, take it to a Sprint owned repair center. They'll try to fix it, but won't be able to, and will replace it for free.
Sent from my SM-N910P using Tapatalk

LMMT said:
Most likely, it's hardware failure. Do you have TEP (insurance through Sprint)? If so, take it to a Sprint owned repair center. They'll try to fix it, but won't be able to, and will replace it for free.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Don't have insurance actually. Had this phone for almost two years now with no problems. Is it just a random coincidence that the hardware failure happened after I started flashing roms and messing with it?

dipped9900 said:
Don't have insurance actually. Had this phone for almost two years now with no problems. Is it just a random coincidence that the hardware failure happened after I started flashing roms and messing with it?
Click to expand...
Click to collapse
The phone's "memory" has a limited number of times it can be written to. The number of write cycles is dependent on the type, and quality of memory the phone manufacturer uses, and is somewhat different for each individual phone.
Sent from my SM-N910P using Tapatalk