So here's the problem. My little bro (age 12) has the sprint note 3. And i rooted it for him. And install sacs v3 ROM. (V4 has no mobile data) and he comes to me and says his sound is distorted. He will play music , set it to the highest state it can go. Then I hear crackling noises. So I unrooted the phone. And its all good again. Then he decides he want root again. And the same problem persist. Could this be a hardware problem? And I'm not sure about what tripping Knox is either. Help please. (Too late to take back the phone)
MonstaSaleens said:
So here's the problem. My little bro (age 12) has the sprint note 3. And i rooted it for him. And install sacs v3 ROM. (V4 has no mobile data) and he comes to me and says his sound is distorted. He will play music , set it to the highest state it can go. Then I hear crackling noises. So I unrooted the phone. And its all good again. Then he decides he want root again. And the same problem persist. Could this be a hardware problem? And I'm not sure about what tripping Knox is either. Help please. (Too late to take back the phone)
Click to expand...
Click to collapse
If it happens only with a custom rom, but not stock. Then I would say it is a rom issue.. I have had strange problems when on a custom rom and Bluetooth on my note 2 when I had it.. Went back to stock and it was fine...
doubledragon5 said:
If it happens only with a custom rom, but not stock. Then I would say it is a rom issue.. I have had strange problems when on a custom rom and Bluetooth on my note 2 when I had it.. Went back to stock and it was fine...
Click to expand...
Click to collapse
.
But every ROM tho? I've tried many and it was all distorted. No one else has had this problem. (That I've seen) I don't understand this as I one from a galaxy nexus. And this kind of this ever happens
MonstaSaleens said:
.
But every ROM tho? I've tried many and it was all distorted. No one else has had this problem. (That I've seen) I don't understand this as I one from a galaxy nexus. And this kind of this ever happens
Click to expand...
Click to collapse
Again if it only happens of custom roms, then yes it could be.. My Bluetooth issue happened on all custom roms as well.. If it helps, return your phone for a replacement, and see if the problem is still there, when you install a custom rom on your new phone..
doubledragon5 said:
Again if it only happens of custom roms, then yes it could be.. My Bluetooth issue happened on all custom roms as well.. If it helps, return your phone for a replacement, and see if the problem is still there, when you install a custom rom on your new phone..
Click to expand...
Click to collapse
i think its too late for a replacement.its been since like janurary. thats weird tho. never had these strange bugs happen on droid incredible or galaxy nexus when rooted. can i still replace it??
MonstaSaleens said:
i think its too late for a replacement.its been since like janurary. thats weird tho. never had these strange bugs happen on droid incredible or galaxy nexus when rooted. can i still replace it??
Click to expand...
Click to collapse
If you bought their insurance package, then you should.. But if you only bought it in January call Samsung, as it will be covered under their 1 yr plan.. I heard Samsung is not worried about rooted phones, just flash it back to stock, before you have any warranty work done..
doubledragon5 said:
If you bought their insurance package, then you should.. But if you only bought it in January call Samsung, as it will be covered under their 1 yr plan.. I heard Samsung is not worried about rooted phones, just flash it back to stock, before you have any warranty work done..
Click to expand...
Click to collapse
Its ok. My bro says he'll just keep the phone
Related
The Reason i ask is either it is or i am the unluckiest person ever with a S2 lol
So far got the phone at xmas wasn't happy with the screen colours sent it off they said the main chip was faulty and had been replaced and a software upgrade etc...
Got it back and flashed a custom rom, well a few and noticed that i then had an issue where if someone called i had to put loudspeaker on in order to hear the other person...
Put phone back to stock and sent it off again...
Phone came back last week picked up monday used for a day all seemed fine, flashed a custom rom got another problem with the phone this time i have to put the loudspeaker on to hear other people they can hear me fine...
So its back to stock and back to vodafone tomorrow...
So can custom roms/kernels cause physical issue's with phones, never had an issue with my HTC Desire HD but i'm beginning to wonder if i should leave my next S2 stock, or have i just been unlucky ???
Would also add when going back to stock the screen colours seem much better than custom roms but the sounds issue's remain...
One word NO!
What rom are you flashing?
Checkrom, wickedrom, illusion Xt, not sure which if any has caused any issues could be I'm just unlucky
Definatly noticed issues with screen colours too which now in I'm back on stock have been sorted
Its all a bit weird
Sent from my GT-I9100 using xda premium
wakers said:
Checkrom, wickedrom, illusion Xt, not sure which if any has caused any issues could be I'm just unlucky
Definatly noticed issues with screen colours too which now in I'm back on stock have been sorted
Its all a bit weird
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Trust me if that was the case damaging my phone by flashing a rom then my phone would of been damaged goods by the first month i had it
Anyway just be careful how you flash a rom and it is always advised to do a full wipe before installing one
Um, actually, yes.
You run the (slight) risk of bricking your phone every single time you flash something to it. If you're the type of person who's paranoid about these things & can't handle the idea of possibly not getting warranty service if things go wrong, you shouldn't be messing with your phone in the first place.
Anyone who has an expectation (as opposed to a "hope") of warranty service after they stuff around with the phone is an idiot.
The SG2 is a hard phone to brick. Follow the general guidelines and you should be fine. I can't imagine flashing a rom can break this phone. Worst that can happen is you brick it. Either it works or it doesn't.
Yeah Im fully aware that you risk bricking the phone
I've been flashing roms to HTC,s for years always trouble free
I always read and full wipe between flashes
Sounds like I've been unlucky then 3rd time phone is going back and since Xmas 1day without a fault not a great introduction to Samsung for me...
Sent from my GT-I9100 using xda premium
In all my time reading SGS1 and 2 the only ones who have bricked their phone are the idiots (1) who refuse to read instructions . Even then 90% of them have been able to recover .
the SGS2 quota of 1 is getting higher day by day for some reason .
jje
Yeah 3 physical faults though in a month which is what got me thinking maybe installing the custom roms is causing an issue, but if others are installing with no issue's i've obviously just been unlucky
Hopefully this time i get it back its sorted...
wakers said:
Yeah 3 physical faults though in a month which is what got me thinking maybe installing the custom roms is causing an issue, but if others are installing with no issue's i've obviously just been unlucky
Hopefully this time i get it back its sorted...
Click to expand...
Click to collapse
~Don't accept a repair... DEMAND A NEW PHONE
Samsung doesnt change phones, only repairs.
GeorgeCm said:
Samsung doesnt change phones, only repairs.
Click to expand...
Click to collapse
Who said Samsung??? I meant Vodafone, and they do give new phones
About a stock I don't know, and on aosp try it
http://forum.xda-developers.com/showthread.php?t=1385862
Suarez7 said:
Trust me if that was the case damaging my phone by flashing a rom then my phone would of been damaged goods by the first month i had it
Anyway just be careful how you flash a rom and it is always advised to do a full wipe before installing one
Click to expand...
Click to collapse
Seconded..
It's possible to introduce some new bugs by flashing a custom ROM (that's the price of development, you uncover new weird stuff), but not to physically damage the phone. You'd have to fiddle with the battery or greatly increase the voltages to accomplish that.
If you experience hardware issues after flashing a ROM, it means that the hardware was faulty before, and flashing the ROM just uncovered it and made it obvious to you whereas it was hidden before.
But don't let it get you down. Apparently a lot of SGS2's are faulty when coming out of the factory and need to be replaced.
The first one I had didn't last the night, it 'overcooked' itself when I plugged it to the mains to get it recharged (I knew those phones could get pretty hot but damn ! a 100°C is too much for it, it didn't stand the strain and gave up)..
In fairness they suggested a new phone in Vodafone today so it's gone back with the the request of a new phone rather than repair so we'll see
Also if anyone is interested I obviously flashed a few custom roms and reset the counter to zero and installed original Vodafone software and have had no issues warranty wise
wakers said:
In fairness they suggested a new phone in Vodafone today so it's gone back with the the request of a new phone rather than repair so we'll see
Also if anyone is interested I obviously flashed a few custom roms and reset the counter to zero and installed original Vodafone software and have had no issues warranty wise
Click to expand...
Click to collapse
I seem to have been lucky with a Vodafone SGSII, I'd have insisted on a new phone from it's first problem, Vodafone have always been pretty good at replacing.
I am wondering however how did you manage to reset the flash counter ? Even with a USB Jig mine won't reset. It will go into download mode, but that's it. I presumed my six week old SGSII was a newer one a jig won't work on.
Before trying to reset the counter you should flash the old boot loader (pre-KI1) on, the new one cannot be reset safely with a jig. Works just fine after this
What Snakeforhire said i flashed the old bootloader reset the counter with the USB Jig then reflashed the new bootloader...
Updated through kies and sent back...
i am starting to get extremely pissed with my new sg3... i dont know if this a phones prob or roms prob... the screen every now and then open and closes after 1 sec by itself without touching the phone at all... it gets really disturbing and i am just wondering if i have to return back my phone and get a new one...
any opinions / help ?
thanks
Do a factory reset and more information would help.
Are you rooted/on a custom ROM?
Reviewers said:
Do a factory reset and more information would help.
Are you rooted/on a custom ROM?
Click to expand...
Click to collapse
yes i am rooted and i have a custom rom (omega)
i will do as you said and come back with the results...
might not be related to your issue, but by any chance are you using a case?
often times if the case's molding is not perfect, it will apply pressure on the power button, so a slight touch on it will fire off the wake up/sleep call. It happened a lot when I was using cheap case.
[email protected]@xyS said:
yes i am rooted and i have a custom rom (omega)
i will do as you said and come back with the results...
Click to expand...
Click to collapse
Surely you need to eliminate the possibility that it's being caused by the custom Rom before sending it back? Does it do the same thing on stock Rom?
Sent from my Samsung Galaxy SIII via Tapatalk
jonathanyong said:
Surely you need to eliminate the possibility that it's being caused by the custom Rom before sending it back? Does it do the same thing on stock Rom?
Sent from my Samsung Galaxy SIII via Tapatalk
Click to expand...
Click to collapse
i just installed another rom to see if it does the same... if yes i will install the stock rom and see the results...
Hi Guys,
In the past few days ive noticed that if i dont check my phone regularly it will simply refuse to wake up (screen on). I know the phone is still working as the LightFlow settings still use the notification light when needed. I have also had situations where the phone wakes up but theres no touch functions, but locking and waking up again fixes that in 1 try. Has anyone else had this issue or am I going to have to send the phone back?
Thanks
Michael
P.S. The phone is not rooted and hasnt been updated since out the box. Any suggestions to root the phone to fix this will be ignored.
Uninstall LightFlow it has been known to cause this issue.
That is all we can suggest unless your willing to root.
Lennyuk said:
Uninstall LightFlow it has been known to cause this issue.
That is all we can suggest unless your willing to root.
Click to expand...
Click to collapse
Thanks for the suggestion. I had my HTC Desire rooted and this has put me off rooting my phone at the moment, but I was waiting for the Jelly Bean AOSP anyway.
Not trying to take this too far off topic, but what do you have against root? All root effectively is is an admin mode, you don't have to flash a custom rom.
Lennyuk said:
Not trying to take this too far off topic, but what do you have against root? All root effectively is is an admin mode, you don't have to flash a custom rom.
Click to expand...
Click to collapse
I dont have anything against root. Its just that when I have a problem with my phone and people suggest to root it, if it doesnt work im kinda screwed over with warranty etc.
Unfortunatly removing Lightflow didnt help and its still happening
if it doesnt work im kinda screwed over with warranty etc
Click to expand...
Click to collapse
It's quite easy to revert back to Stock for warranty repairs.
Rooting does not brick your phone.
d4fseeker said:
It's quite easy to revert back to Stock for warranty repairs.
Rooting does not brick your phone.
Click to expand...
Click to collapse
Wont they reject it if its rooted? This would be the first phone ive sent for repairs. My HTC Desire never faulted in 2 years but this is starting to annoy me just a month and a half into my contract.
mtmannion said:
Wont they reject it if its rooted? This would be the first phone ive sent for repairs. My HTC Desire never faulted in 2 years but this is starting to annoy me just a month and a half into my contract.
Click to expand...
Click to collapse
Yes, but u can use "triangle away" (by chainfire) to reset flash counter(found in download mode) and flash a stock rom with Odin and back is your warranty.
root...warranty...bla bla bla...why want to return just because of that? do u know that samsung software engineers sucks? i bought nexus, and i just use it for 1 week. want to know why? because it's so boring. the phone so perfect. no problem at all. nothing to tweak, nothing to fix, nothing to improve. i switch back to Samsung Galaxy because of this (before this use SGS1, now SGS3). so, if you have problem like THIS, change your kernel, or just sit and wait for update to fix it. samsung monitoring it (SLOWWWWWLYYY)
mtmannion said:
Wont they reject it if its rooted? This would be the first phone ive sent for repairs. My HTC Desire never faulted in 2 years but this is starting to annoy me just a month and a half into my contract.
Click to expand...
Click to collapse
ascariz said:
root...warranty...bla bla bla...why want to return just because of that? do u know that samsung software engineers sucks? i bought nexus, and i just use it for 1 week. want to know why? because it's so boring. the phone so perfect. no problem at all. nothing to tweak, nothing to fix, nothing to improve. i switch back to Samsung Galaxy because of this (before this use SGS1, now SGS3). so, if you have problem like THIS, change your kernel, or just sit and wait for update to fix it. samsung monitoring it (SLOWWWWWLYYY)
Click to expand...
Click to collapse
U got a lot blablabla"s, Samsung"s phone has clearly the best hw but they don't give a s... about the sw.
About rooting, what the f... are talking about read the posts made by OP. he asked if u loose warrenty if u root and yes u do, but root is reversible and THAT is what the OP wanted to know
he asked if u loose warrenty if u root and yes u d
Click to expand...
Click to collapse
Over here afaik at least within the first period the seller has to actually prove you caused the damage to refuse the claim.
Having a rooted device will not stand as having caused hardware-damage.
So far I've yet to hear about a single case of warranty being refused in this country due to software modifications.
If it was as simple as putting a "Waranty void if removed" sticker on stuff actually having any meaning, that would be the end of democraty. Fortunately the law tells otherwise and manufacturers have to obey it (or buy their own law... at least in the USA that seems to work)
However it most certainly will make repairs far easier if the device is stock since they cannot even try to blame you for incorrect configurations or bad flashes.
ascariz said:
root...warranty...bla bla bla...why want to return just because of that? do u know that samsung software engineers sucks? i bought nexus, and i just use it for 1 week. want to know why? because it's so boring. the phone so perfect. no problem at all. nothing to tweak, nothing to fix, nothing to improve. i switch back to Samsung Galaxy because of this (before this use SGS1, now SGS3). so, if you have problem like THIS, change your kernel, or just sit and wait for update to fix it. samsung monitoring it (SLOWWWWWLYYY)
Click to expand...
Click to collapse
zodiaxe66 said:
U got a lot blablabla"s, Samsung"s phone has clearly the best hw but they don't give a s... about the sw.
About rooting, what the f... are talking about read the posts made by OP. he asked if u loose warrenty if u root and yes u do, but root is reversible and THAT is what the OP wanted to know
Click to expand...
Click to collapse
Thanks for the help guys, Im on holiday at the moment so I'll see if theres a Kernal update when I get home. If not I'll check on the Jelly Bean (or something popular thats been out for a long time) rom stability and root for that. If nothing helps from those ill use the Triangle program to get rid of the root history and send it back for repairs.
EDIT: My Kernal is from May 13th. Surprised I havent had an update come thorugh yet. There isnt even a check for update button in my "About Phone"
There isnt even a check for update button in my "About Phone"
Click to expand...
Click to collapse
Are you by any chance on Orange UK or Three UK? (Can't remember which of both was it)
They've removed that button in their bloatware-edition of the Samsung ROM - probably to prevent users from updating over 3G connectivity.
d4fseeker said:
Are you by any chance on Orange UK or Three UK? (Can't remember which of both was it)
They've removed that button in their bloatware-edition of the Samsung ROM - probably to prevent users from updating over 3G connectivity.
Click to expand...
Click to collapse
Bingo, Orange UK.
Happy 666th post
Happy 666th post
Click to expand...
Click to collapse
Thanks =) I guess that means I'm far too much online, since I've accumulated these posts only since having my S3 =D
So that number is why I'm having such a particular foul mood today, May be related to exams too I sincerly HATE IT logic, especially Prolog -.-
Sadly there is no such thing as good-luck charms to protect against exams like the Pentagrams protect against evil. (Please noone now say it's the symbol of evil...)
Bingo, Orange UK.
Click to expand...
Click to collapse
Just flash any Samsung- or aftermarket-ROM (I recommend CM9 or the CM9-based ParanoidAndroid) of your choice and you're good.
DXLF3 modem should work well according to what I've heard.
My DNA has just started popping up the message "com.android.phone has stopped" and crashing the dialer every time I try to make a call. It worked fine for the first couple weeks I had it, and still works fine apart from making calls. 4G works and I get data. I've tried re-inserting the SIM, doing a factory reset, flashing RUU, and I just got back from the Verizon store where the swapped out the SIM. Nothing has fixed it.
Before I call the VZ warranty department I thought I'd post here and see if anyone had an idea. I'm a little worried they'll see my "Relocked/Tampered" bootloader and tell me I'm SOL. :/
Hmm...that didn't work I think there's a tread about this issues somewhere around here
sent from my beastly powered viper DNA using Tapatalk 2
holla420 said:
Hmm...that didn't work I think there's a tread about this issues somewhere around here
sent from my beastly powered viper DNA using Tapatalk 2
Click to expand...
Click to collapse
Hmm, I didn't find anything in my (admittedly brief) search. Either way, I gave up and called Verizon warranty service. The rep was very helpful and agreed to send me a new phone.
neo_1221 said:
Hmm, I didn't find anything in my (admittedly brief) search. Either way, I gave up and called Verizon warranty service. The rep was very helpful and agreed to send me a new phone.
Click to expand...
Click to collapse
Wow, it would never be that easy to get a replacement in Australia
uppon2 said:
Wow, it would never be that easy to get a replacement in Australia
Click to expand...
Click to collapse
Just to be clear, my "new" phone is actually "recertified like-new". And I have to send the old one back or pay full price for it. And if they find evidence of damage or tampering on the old phone I'll get charged $300. But yeah, aside from that it was pretty easy.
Guys, i am having the same problem! On every call i get com.android.phone has stopped ! Does anyone had the same and found a solution?!
I tried 3 custom roms(viper hatka and another one) no work, reflashed back to stock, problem remains!
I am also living overseas! Is this a problem?
Just out of curiosity, do you still have the little flap covering your microUSB port? I got annoyed with mine and yanked it out...now I'm wondering if it damaged the antenna.
I have removed it too, no way this thing can affect the operation!
It has to do with someone on you facebook or contacts has a birthday on Feb 29 find out which one it is delete the contact sync for that person or change the birthday
Thanks for the reply, have you experienced the same problem in htc DNA?
The solution you are giving is kinda strange, as i haven't passed any contacts or fb account to my mobile and the problem persists. Of course, i had done this one in the past, lets check what you just said, thanks!
ergotelis said:
Thanks for the reply, have you experienced the same problem in htc DNA?
The solution you are giving is kinda strange, as i haven't passed any contacts or fb account to my mobile and the problem persists. Of course, i had done this one in the past, lets check what you just said, thanks!
Click to expand...
Click to collapse
sorry wrong on the one I thought it was is http://forum.xda-developers.com/showthread.php?t=2076784
android.phone.acore .. again I am sorry
I also am having this problem.
I completely wiped everything and stuff as well.
Any solutions?
any resolutions?
has anyone been able to resolve this? after S-OFF, i'd hoped that flashing the new radio may work, but it didn't. i've formatted every partition and then resintalled every rom i can think of, to no avail. sucks!!
I had stock rom, unlocked, rooted, flashed viper and had the problem. Flashed different roms, the same. Returned to stock RUU, the same. Reflashed, the same. Unlocked, rooted again, and flashed viper again, and voila, the problem solved!:laugh:
ergotelis said:
I had stock rom, unlocked, rooted, flashed viper and had the problem. Flashed different roms, the same. Returned to stock RUU, the same. Reflashed, the same. Unlocked, rooted again, and flashed viper again, and voila, the problem solved!:laugh:
Click to expand...
Click to collapse
I tried this hoping it would fix com.android.phone, no luck
If RUUing doesnt help it then it might be a hardware related issue and its getting that error because the software can not communicate with the hardware... possibly? maybe? just an idea
.torrented said:
If RUUing doesnt help it then it might be a hardware related issue and its getting that error because the software can not communicate with the hardware... possibly? maybe? just an idea
Click to expand...
Click to collapse
It's not like I'm not getting a signal, I still receive txt sms. The signal cuts as soon as I try using dialer.
ergotelis said:
I had stock rom, unlocked, rooted, flashed viper and had the problem. Flashed different roms, the same. Returned to stock RUU, the same. Reflashed, the same. Unlocked, rooted again, and flashed viper again, and voila, the problem solved!:laugh:
Click to expand...
Click to collapse
I tried following what you mentioned flashed ruu and then flashed back to viper rom. So can you please tell me what I'm doing wrong?
thanks
Have you checked md5 files for your files to be sure that you have the right ones?What recovery are you using? Are you locking-unlocking etc as you have to on every step?Try it once more but be sure for all these! I personally used cwm recovery!
ergotelis said:
Have you checked md5 files for your files to be sure that you have the right ones?What recovery are you using? Are you locking-unlocking etc as you have to on every step?Try it once more but be sure for all these! I personally used cwm recovery!
Click to expand...
Click to collapse
I am using cwm and followed step-by-step. I think it maybe a hardware issue or partitions are corrupt
Hello everyone. I jumped the gun and rooted/unlocked the BL and am running the stock Deoxed rom that is located in the dev section. But now I need to return the phone as the service around here isnt great. Since I am in a tight window I am unsure what to do since there is no RUU available and no Nandroids of stock AT&T.
Any suggestions would be helpful!
I would just do the return I don't think they would really check the boot loader.
As long as you have a stock rom on there you should be in the clear. I've returned unlocked phones before and the AT&T rep never did more than reboot the phone.
tier~ said:
As long as you have a stock rom on there you should be in the clear. I've returned unlocked phones before and the AT&T rep never did more than reboot the phone.
Click to expand...
Click to collapse
+1, I've returned unlocked phones also without any trouble.
Give it a try, you might get lucky and they won't notice..
Anyone reading this can avoid this by always doing a nandroid before installing a custom ROM..
They won't notice. When I exchanged my note 2.it even had a different boot animation than the stock one and he still exchanged it. They really don't check.
cdromo90 said:
They won't notice. When I exchanged my note 2.it even had a different boot animation than the stock one and he still exchanged it. They really don't check.
Click to expand...
Click to collapse
Even with a custom recovery?
mobilecarlos said:
Even with a custom recovery?
Click to expand...
Click to collapse
Yup.
Be careful...I exchanged my Rooted Stock ATT HTC One and the rep got ready to restore the phone to factory settings. However, I told him I'd do it instead. Good thing I did because it went into TWRP to restore the phone..than there was also a white screen with a message at the bottom of the screen about custom recovery...I didn't read the entire message because the phone re-booted. But if the Rep would've wiped the phone, he would have seen all this...
So my best advice is to wipe the phone yourself...
I'm a rep at ATT and we don't hardly check an if it is it doesnt matter any way we still return it.
Sent from my HTC One using Xparent Blue Tapatalk 2