Database Users

Battery gave out.

Anyone got an idea? It seems as if my battery wont take any charge. Only turns on when phone is "Charging." I gave HTC a call and they are so damn stupid. Im sorry but honestly.. they cant trade out my battery! Wanna know why?! THEY ARE MORE WORRIED ABOUT COMPLETING ORDERS WITH NEW CUSTOMERS. Hmph knowing google i wasnt surprised but STILL! REALLY?! So basically I have to shell out 50 bucks for a new battery? Maybe someone knows something.. I didnt post in accessories because it isnt so I dont know... if this is wrong place sorry.

flamerider88 said:
Anyone got an idea? It seems as if my battery wont take any charge. Only turns on when phone is "Charging." I gave HTC a call and they are so damn stupid. Im sorry but honestly.. they cant trade out my battery! Wanna know why?! THEY ARE MORE WORRIED ABOUT COMPLETING ORDERS WITH NEW CUSTOMERS. Hmph knowing google i wasnt surprised but STILL! REALLY?! So basically I have to shell out 50 bucks for a new battery? Maybe someone knows something.. I didnt post in accessories because it isnt so I dont know... if this is wrong place sorry.
Click to expand...
Click to collapse
Did you install the RAM hacked kernel? That has a known issue of causing batteries to no longer charge, and you must revert back to the stock kernel or the recently released patch RAM hacked kenel.

WHAT!? F******* lol i think i did uhm lemme see about flashing a stock rom

flamerider88 said:
WHAT!? F******* lol i think i did uhm lemme see about flashing a stock rom
Click to expand...
Click to collapse
The stock ROMs don't fix it, IIRC, you need to flash the stock kernel.

Would Cyans boot-nexus1-orig.img work?

flamerider88 said:
Would Cyans boot-nexus1-orig.img work?
Click to expand...
Click to collapse
Not really sure, I just started reading up on the Cyan and Kernel for the Nexus One a couple days ago. Perhaps someone that has messed around with the stuff and has a link handy to the kernel he needs could post it up?
As well, I would be willing to bet if you did a search of the Cyan 5.0 ROM thread for "kernel" you would find a link at some place in there.

OP, you need to chill.
Just reflash Cyanogen's addon pack.

I found the Zimage or what ever to flash.. but my battery is dead! GAH! now i have to order one because i dont have a batt to flash it with

That new battery may or may not come charged, if that's what you mean. You might need a friend with an N1 to help you out, if you need a charged battery to reflash.

FYI, worst case scenario, you could always mail your battery to somebody, let them charge it, then mail it back... I would recommend trying to find someone in Cali first, since it would take about 4 days round trip then. I would be willing to help you out, though, if you can't find anyone else... but I am in Iowa, so it would take more like a week or so round trip.

how about turning it on with the charger in w/o the battery? My g1 can do it. Not sure if that applies to other phones.

I find it funny how in your first post you call htc and google stupid for not fixing your battery issue which you obviously brought upon yourself by installing custom roms.

Gotenn said:
I find it funny how in your first post you call htc and google stupid for not fixing your battery issue which you obviously brought upon yourself by installing custom roms.
Click to expand...
Click to collapse
It's pretty obvious that he didn't realize that it was the custom kernel that was the cause of his issue.

uansari1 said:
It's pretty obvious that he didn't realize that it was the custom kernel that was the cause of his issue.
Click to expand...
Click to collapse
no wonder HTC doesn't want to know about unlocked nexus going in for warranty.
if you install a custom rom the least you can do is try to stay on top of things related to that rom. I haven't unlocked, but even I knew there was an issue with batteries not charging.

nmesisca said:
no wonder HTC doesn't want to know about unlocked nexus going in for warranty.
if you install a custom rom the least you can do is try to stay on top of things related to that rom. I haven't unlocked, but even I knew there was an issue with batteries not charging.
Click to expand...
Click to collapse
Perhaps now you can understand why some of us are irritated when people jump the gun on things. In this case, we're talking about people going straight to rooting and flashing their phones with custom ROMs without realizing the potential issues related with them... in other cases, well I won't get into off topic discussion...but suffice to say that this isn't the last time you see someone flash a ROM, then ask why his phone isn't working the same as it was before.

HTC picked up my N1 yesterday because it wasnt charging. It said it was charging but as soon as I took out the charger it turned off.
It had an unlocked bootloader and they said they would send me a new one...
Fingers crossed I get a new one soon
I didn't know about the kernel doing this so just I emailed them, then phoned and they sent someone to pick mine up...

Man that's bad.You really should not root your next one, and if you do, you should take responsibility for your actions.

jongie123 said:
Man that's bad.You really should not root your next one, and if you do, you should take responsibility for your actions.
Click to expand...
Click to collapse
You talking to me?
HTC gave me a new Nexus One today and mine was unlocked and replaced no problem And it wasn't to do with the kernel because the report from HTC says the battery was faulty But they gave me a new device anyway.

I love it how people just love to automatically point the figure at somebody else for their fault. Maybe you should have first read more about something when you decide to root your phone rather than running and screaming like a two year old.

There are many reasons to root/rom/kernel the phone when you may not be considered one of the 'enlightenned' as this thread seems to insinuate.
If you need to do anything that is not in the android ideal as far as application framework goes your screwed.
I bought this phone since I was "sold" that it was "open"
and for "development" that to me impiled it at least had a shell...
This thread has gotten seriously off track.
Please respond in the vein of helping identify what the stable(est)rooted baseline should be.

Important Safety Tip For Hardware Locked Vibrants!

This might come off as me preaching here, but I hope I don't come across as high-handed...
If you have a hardware button sequence locked Vibrant you really need to think long and hard about whether or not you should be messing with custom firmwares, ESPECIALLY NOW.
The last few leaked firmwares (JI2, JI4, JI5) are ALL RUNNING A NEW KERNEL. One that is not compatible with JFD derived builds. Furthermore these great new custom kernels provided by our awesome dev's (Voodoo, JAC, Kingclick, etc...) are not compatible with these new leaked builds. So the likelihood of you ending up staring at a really scary screen on your phone is skyrocketing, unless you have reliable methods to deal with that scary screen.
I've ran across numerous posts here today, with all the fervor over the JI5 Kies leak, where people have Clockwork Recovered themselves into a nightmare because they simply didn't understand these points. Even simpler MOD's (like a few posts I found today where people were installing the JFD version of the MobileAP mod on JIx builds and screwing their phones up) can lead to grief if you don't do your homework.
If you cannot reliably get into recovery *AND* download mode, please please be sure you understand the risks your taking if you fail to be careful and read the information that is already here. Granted, I know few people can keep up with some of us and our ability to soak up info like a sponge. Still there is a process of risk assessment YOU MUST BE RESPONSIBLE FOR when you realize you are doing things that you probably shouldn't be.
This doesn't mean I won't continue trying to be helpful. I just want to make it clear to some of you that you really need to think things through more thoroughly before you let your excitement drive you into a corner.
I vote for the following statement to be made a sticky in this and the Q&A Forum...
"If you are updating firmware on a phone, and you've already hacked this and that, tweaked this and that, modified this and that...whatever the case may be you should be prepared to have to Odin your way back to stock.
If you are not prepared to Odin your way back to stock (don't know how, have a hardware button locked phone, etc...) then you should really be asking yourself whether or not you should be customizing your phone to the degree that you are.
It's just about risk assessment. Most risks are known, but some are not. Furthermore there can be bad synergies between multiple tweaks, mods, and/or hacks that no one can easily predict ahead of time. So it's not about anyone trying to be elitist. The best way to help people is to help them avoid making critical mistakes."

actually if u have a hardware locked phone, what you SHOULD do is call tmobile right now and complain that ur phone is defective and they'll send u a new one... keep doing this till u get a working phone, i did and i now have a phone that isn't HL'ed... only took one try

ookas said:
actually if u have a hardware locked phone, what you SHOULD do is call tmobile right now and complain that ur phone is defective and they'll send u a new one... keep doing this till u get a working phone, i did and i now have a phone that isn't HL'ed... only took one try
Click to expand...
Click to collapse
Indeed!!!
The hardware locked Galaxy S thing appears to be a bootloader bug affecting more than just our Vibrants (some other batches of Galaxy S phones are affected) rather than a real hardware issue, so T-Mobile should be able to get these fixed readily. Not like we should care about T-Mobile here, but what this means also is that T-Mobile shouldn't be making a huge deal about swapping these out either.
I'd encourage everyone with a button-sequence screwed Vibrant to simply go to T-Mobile and get it replaced.

Admittedly, I was one of those fools who installed the wrong MobileAp and also tried to go back to a nandroid that didn't work (different kernel - or so I have learned.) Bricked the phone. But I wasn't hardware locked so I was able to get everything back thanks to some really helpful people here on the forum.
I agree that all hardware locked phones should be returned. If mine were locked then I'd still be staring at a dead phone.
I would like to add that I am new to the android thing. But, I am not a software noob (i did software testing for a living). The thing is that I am sometimes impulsive and that leads to mistakes. Thankfully, I have a way to get out of the mistakes (ODIN and non-hardware locked phone.) I always know the risk I am taking and take full responsibility for anything I screw up.

How can I tell if I have a hardware-locked phone, without attempting to flash a ROM, I mean?
Thanks

aad4321 said:
i have a hardware locked phone that i unlocked and have a custom recovery on. I have only accessed the recovery through rom manger. is there any other way to access it with hardware locked? If so can someone post details. it will be good to know when i mess up my phone and it dosent boot preventing me from accessing rom manager to get to the recovery
Click to expand...
Click to collapse
you didn't unlock the hardware. You just simply rooted your phone. Hardware lock can not be unlocked and that's what this thread is trying to address. I have tried exchanging my phone from tmo once and the exchange phone they sent me still had the same problem, so i haven't bother with it. I wonder if i can just walk into a store and do an exchange since i got my phone from tmo online. Anyways, if you have a hardware locked phone, stick with roms that will flash through clockworks. That is the safest way, but keep in mind that there is still a slight chance of failure.

BruceElliott said:
How can I tell if I have a hardware-locked phone, without attempting to flash a ROM, I mean?
Thanks
Click to expand...
Click to collapse
Never mind; I figured it out.

Man, I'm glad I read your post on hardware-locked problems. I didn't even realise this was a problem until after I dicked around with my phone a bunch, and then ended up reflashing with odin back to stock. I could have messed up big time.
My problem is that I can't replace my phone at all. I purchased a T-Mobile Samsung Vibrant online, brand new, unopened and locked for use here in Canada on the Wind Mobile network.
After hearing about this defective hardware I called T-Mobile, they said I have no warranty with them since it wasn't a T-mobile store purchase. Alright I guess. So they give me the number to Samsung USA,USA transfers me to Canada, I get transferred back again and this is what I'm stuck with.
My new phone has NO warranty, in either country. Both refuse to honour any sort of warranty, and refer to the other for support. I didn't think I'd get this sort of run around from Samsung.
USA says that because I live in Canada, I voided the warranty.,
Canada says that because it's a USA device, and I didn't purchase an international warranty, they won't touch it.
I'll just have to be careful what I install on my phone, and avoid Samsung products in the future.
Thanks for the warning

I wouldn't say your lack of warranty is any surprise. I don't know about Canada, but in the US, phone warranty is normally tied to the carrier, which means if you're not an active customer using the phone on the account that it was first activated on, you will have no warranty. Nothing special about Samsung here, all brands are the same.
Sent from my SGH-T959 using XDA App

cwoodworth said:
Man, I'm glad I read your post on hardware-locked problems. I didn't even realise this was a problem until after I dicked around with my phone a bunch, and then ended up reflashing with odin back to stock. I could have messed up big time.
My problem is that I can't replace my phone at all. I purchased a T-Mobile Samsung Vibrant online, brand new, unopened and locked for use here in Canada on the Wind Mobile network.
After hearing about this defective hardware I called T-Mobile, they said I have no warranty with them since it wasn't a T-mobile store purchase. Alright I guess. So they give me the number to Samsung USA,USA transfers me to Canada, I get transferred back again and this is what I'm stuck with.
My new phone has NO warranty, in either country. Both refuse to honour any sort of warranty, and refer to the other for support. I didn't think I'd get this sort of run around from Samsung.
USA says that because I live in Canada, I voided the warranty.,
Canada says that because it's a USA device, and I didn't purchase an international warranty, they won't touch it.
I'll just have to be careful what I install on my phone, and avoid Samsung products in the future.
Thanks for the warning
Click to expand...
Click to collapse
Other companies will do the same thing. Warranties are country specific, no?

I don't know how it works with mobile phones, but whenever I've purchased computer parts, the country of origin has never been a problem. Maybe I've just been lucky.
Still have gripes about GPS, and lack of 2.2 though.
Don't misunderstand me though, I love this phone. Just surprised about the hardware issues.

I called Samsung today after tmobile rep gave me a number for warranty. After complaining and speaking to a supervisor, they said i could send it in and they would "fix" it. This is what they sent in the email.
Product Symptoms : Technical Inquiry/Internal Menu/Software Reflash - FOC/No fee. The Samsung Rep said a technician would look at it.
I got a shipping label and everything.
I have one question. How should i go about reflashing to stock? can i just factory reset + remove superusers. please help.

cwoodworth said:
I don't know how it works with mobile phones, but whenever I've purchased computer parts, the country of origin has never been a problem. Maybe I've just been lucky.
Still have gripes about GPS, and lack of 2.2 though.
Click to expand...
Click to collapse
PC parts aren't as tightly controlled as mobile phones. That's the difference.
GPS and Froyo should be coming soon. I doubt if Samsung would let their best mobile phones fall behind by much. From the leaked firmwares popping up, it shows they're working on it.

Latest and greatest for atrix?

My phone has been half broken for the better part of 3 months because i partitioned the internal sd and lost half my touch screen and the buttons on the bottom of the phone. So i got it fixed thanks to kermit and bongd and now im on 4.1.5.7 and I didn't do the newer update yet. My question is now what's the latest and greatest for the atrix as far as roms go. I used gingerblur in the past but its been 3 months so im wondering what you guys are using now
Sent from my MB860 using XDA App

moto 2.3.4

+1
lsxrx7 said:
moto 2.3.4
Click to expand...
Click to collapse
Sent from my MB860 using XDA App

Start here:
http://forum.xda-developers.com/showthread.php?t=1142674

I just can't see losing the warranty on my phone..

They never said it would. Just that it MAY.

ChumleyEX said:
I just can't see losing the warranty on my phone..
Click to expand...
Click to collapse
Lol, sux to be you then.
Sent from rooted Atrix on 2.3.4 with unlocked bootloader using xda premium app.

Can always go stock if u need to have the phone fixed through moto. I thought I read that the leaked 2.3.4 wasn't necessarily made for atrix and alot of things didn't work fully? And thanks for the info
Sent from my MB860 using XdA App

4.1.83 is the last official build for att, has been out for awhile and is very stable, no reason not to go to that.
Soon the 2.3.4 update will be out officially, tell then we can just wait.
and the same players are pretty much the same, higher version numbers but gingerblur, grayblur, gladiatrix are still the favorites.

My thoughts on warranty are that unless its obvious that its been tampered with (specifically that it says unlocked when first powered on), then warranty would not be an issue. All reports ive seen say that when flashing back to a stock 1.8.3 sbf, that unlocked disappears, even though the bootloader may still be partially unlocked. On top of that, in most cases, if the phone is damaged beyond the ability to repair with a sbf flash, its probably not going to be functional enough for the unlocked status of the bootloader to be determined in the first place. there is always a chance, but imo its very minimal.
In regards to "whats best" 1.8.3 with gingerblur imo is the best option if you arent willing to do some tweaking and play with the unlocked bootloader and 2.3.4. If you are however, then unlocked, rooted, 2.3.4 is the shiznit.

Conversation is winding up on the Motorola forums, and one of the forum managers, Mark, has indicated a survey will go out very soon, (soon being in the next few days), for soak testing the 2.3 update.
Looks like they may aim for very early July, if not end of this week, to start pushing out soak test beta updates.

pyro254750 said:
My thoughts on warranty are that unless its obvious that its been tampered with (specifically that it says unlocked when first powered on), then warranty would not be an issue. All reports ive seen say that when flashing back to a stock 1.8.3 sbf, that unlocked disappears, even though the bootloader may still be partially unlocked. On top of that, in most cases, if the phone is damaged beyond the ability to repair with a sbf flash, its probably not going to be functional enough for the unlocked status of the bootloader to be determined in the first place. there is always a chance, but imo its very minimal.
Click to expand...
Click to collapse
Unlock does disappear when you flash back, but where do you think all the refurb phones come from?
They go back to Moto, who run diagnostic software and tools to determine what, if anything, needs to be repaired before they send the phones back out as refurbs. They will see right away it is unlocked, and if it voids your warranty, expect a bill from them, or your carrier, after the fact. This happened to an ex of mine a couple of years ago where she was billed the full value of the replacement phone by AT&T after they found she had messed with the one she sent back. That was a Moto phone also.
Sure, if you run over your phone with your car you will be ok, but what if it's something simple like the screen goes out, power button stops working, etc.?
If people are worried about voiding their warranties, they have every right to not risk their warranties, and also to not listen to stupid advice telling them they, (Moto, AT&T, whoever), will probably never know!

CaelanT said:
Unlock does disappear when you flash back, but where do you think all the refurb phones come from?
They go back to Moto, who run diagnostic software and tools to determine what, if anything, needs to be repaired before they send the phones back out as refurbs. They will see right away it is unlocked, and if it voids your warranty, expect a bill from them, or your carrier, after the fact. This happened to an ex of mine a couple of years ago where she was billed the full value of the replacement phone by AT&T after they found she had messed with the one she sent back. That was a Moto phone also.
Sure, if you run over your phone with your car you will be ok, but what if it's something simple like the screen goes out, power button stops working, etc.?
If people are worried about voiding their warranties, they have every right to not risk their warranties, and also to not listen to stupid advice telling them they, (Moto, AT&T, whoever), will probably never know!
Click to expand...
Click to collapse
As i stated in my post, that was just my opinion, i never deemed it to be fact. Id also like to add, that i was referring to att tech support, and replacement being done under att insurance, NOT motorola direct.

pyro254750 said:
As i stated in my post, that was just my opinion, i never deemed it to be fact. Id also like to add, that i was referring to att tech support, and replacement being done under att insurance, NOT motorola direct.
Click to expand...
Click to collapse
Yup, and AT&T doesn't just junk them. They return them for evaluation/repair. Doesn't matter if your replacement is through insurance. They still repair and sell as refurbs if possible.

ceo.mtcl said:
Lol, sux to be you then.
Sent from rooted Atrix on 2.3.4 with unlocked bootloader using xda premium app.
Click to expand...
Click to collapse
How so, I love my phone? I won't suffer in the least from whatever I'm not doing.. lol
I don't have to have the latest and greatest hack or mod that's going around so that I can impress people.. My phone does everything I've needed of it so far (with rooting) and saving whatever money I can if it breaks within the warranty period is a no brainer.. Yes maybe it could look cooler or run just a tiny bit faster (I also can wait for the official at&t update for some of that) but nothing looks cooler than a working phone and $400 in my pocket..

CaelanT said:
Yup, and AT&T doesn't just junk them. They return them for evaluation/repair. Doesn't matter if your replacement is through insurance. They still repair and sell as refurbs if possible.
Click to expand...
Click to collapse
im sure they do. My opinion is based on my experiences with insurance in the past, specifically a phone that was returned due to water damage, but the water sensors did not trip (clearly damage that voids warranty), and yet it was replaced and i never heard anything from HTC or att regarding the water damage. It was inspected by a low level tech support representative to determine it could be replaced under warranty, the inspection consisted of removing the back panel and checking the water markers and determining the phone wouldnt power on. a more thorough investigation by htc would have revealed water damage, so either they did not inspect it, but rather just junked it, or they did not pursue reimbursement for the phone once they determined it was not warrantable. two different comanies, two different problems, but same concept. Just because its not warrantable, doesnt mean it wont be replaced under warranty. I would never suggest someone rely on this happening of course, just pointing out that it DOES happen.

Warranty claims are handled by the carrier. If the phone is deemed to be abused/damaged/hacked during the replacement process, you will be billed for the replacement handset's cost. If they don't find the cause during this process, the phone is grouped according to the level of damage and sent off to be refurbished/parted out/recycled, and you are in the clear.
The insurance process is handled by a third party, and covers pretty much ANYTHING that you could do to your phone. They don't care what you've done to it, because by that time you've already paid for the refurbished replacement via your monthly fee & deductible.
That being said.. I'm not encouraging anyone to commit fraud, nor do I guarantee results, but I work in the industry and have a lot of experience with thes issues. IMO, if you're trying to get a warranty replacement for your bricked phone, you're abusing the system. You knew what you were getting into when you started flashing/hacking/modding, and therefore the problem is clearly not a 'manufacturer's defect', which is what warranties cover.
Insurance on the other hand, is there to cover anything. If you're allowed to plunge your phone into the toilet, or toss it out of a moving vehicle, and still get a replacement, then flashing & bricking are certainly deserving of coverage as well. I have a feeling with all these manufacturers releasing unlocked bootloaders we'll see some more fine print added to our policies in the near future.
Just my experience & 2 cents. Personally i'm waiting for the official GB att release, because at least then when I unlock my phone I'll be doing it with the blessing (and testing) of the manufacturer, and therefore much less likely to screw myself with an incompatible version of GB

zoso28 said:
Personally i'm waiting for the official GB att release, because at least then when I unlock my phone I'll be doing it with the blessing (and testing) of the manufacturer, and therefore much less likely to screw myself with an incompatible version of GB
Click to expand...
Click to collapse
Not to mention the 30+ threads at the moment with people complaining about problems with their Hong Kong 2.3.4 build, and looking for solutions!

CaelanT said:
Not to mention the 30+ threads at the moment with people complaining about problems with their Hong Kong 2.3.4 build, and looking for solutions!
Click to expand...
Click to collapse
Exactly!! I'm just beginning to learn about android development and definitely not ready for such an experimental build. It amazes me how many people are willing to mess with their ROMs without knowing what they're doing. I'm taking the time to read everything I can find on here before I start experimenting with adb/rsd/fastboot/etc.. Hopefully i'll be ready to go when the official build is released.

zoso28 said:
Exactly!! I'm just beginning to learn about android development and definitely not ready for such an experimental build. It amazes me how many people are willing to mess with their ROMs without knowing what they're doing. I'm taking the time to read everything I can find on here before I start experimenting with adb/rsd/fastboot/etc.. Hopefully i'll be ready to go when the official build is released.
Click to expand...
Click to collapse
One can always flash back to 4.1.8.3. Are you willing to mess with CWM on Froyo?

[Q] Warranty dilemma with Verizon

Hey guys, i recently bought a phone off of eBay and added insurance on it through open enrollment at Verizon. It was a refurb phone for Assurion. Now the issue is that the screen sometimes become unresponsive and requires me to shut the screen of and turn it back on in order for it to function (The screen never has issues with the spen though). Upon calling Verizon, i was still rooted and it looks like they can actually look through you phone and see if you have root and what applications you have include safe strap. I pretended that i didn't know what the guy was talking about and told him i had nova launcher and that was probably my problem. I then performed a clean Odin factory stock wipe and the phone is back to normal. The knox hasn't even been tripped. When i called back verizon the guy told me "it looks like the phone was rooted the last time you called and now it's absolutely clean. I'm sorry, but because it was rooted, you're warranty is void". Always unroot before you call in!
Do you guys think i can contact Samsung and have them fix this issue for me? I doubt they will know if im rooted if i remove it all before i send it right

What!??? ??????
Sent from my SM-N900V
---------- Post added at 12:40 AM ---------- Previous post was at 12:39 AM ----------
Who you speak to miss cleo? ?????
Sent from my SM-N900V

This is something new if they did in fact see that you were rooted. Part of me wonders if the rep was pulling your chain to see if you'd slip a hint that you were rooted.

jmc2543 said:
This is something new if they did in fact see that you were rooted. Part of me wonders if the rep was pulling your chain to see if you'd slip a hint that you were rooted.
Click to expand...
Click to collapse
He definitely was not lying. The first rep i spoke to about 2 weeks ago was naming all the apps i had! He mentioned safestrap, superuser, along with other apps that had nothing to do with rooting. He made it personal to which you can tell he was looking at what i had. Also, the second time the guy had me update My Verizon Mobile. This is what they use to get access to your phone. Be warned everyone!

I wonder how this is legal. It's they can see apps installed what else can they see? My pictures, my documents? And what keeps them from only accessing my phone when I call in for support?
---------- Post added at 01:19 AM ---------- Previous post was at 12:29 AM ----------
Ok I found how they are doing it, my verizon mobile update gives them access. Can we say uninstall. But to answer your question, no samsung won't know. id just backup and reset to stock anyways. You figure you will be turning it in to them anyways.

jmc2543 said:
I wonder how this is legal. It's they can see apps installed what else can they see? My pictures, my documents? And what keeps them from only accessing my phone when I call in for support?
---------- Post added at 01:19 AM ---------- Previous post was at 12:29 AM ----------
Ok I found how they are doing it, my verizon mobile update gives them access. Can we say uninstall. But to answer your question, no samsung won't know. id just backup and reset to stock anyways. You figure you will be turning it in to them anyways.
Click to expand...
Click to collapse
OK, I will try contacting Samsung today. The only issue is that I'd have to be without a phone for 2-3 weeks . Also about the my Verizon mobile, they ask you to download it or update it in order to allow them to troubleshoot your phone (they don't tell you that's the reason, they just ask you to update it).

Remember...warranty and insurance are 2 different things. If in the TOS they list having the right to refuse warranty service due to unauthorized software modification, then that is Verizon's right. If after restoring stock it still has an issue then you have nothing to lose by trying Samsung.

dapimpinj said:
He definitely was not lying. The first rep i spoke to about 2 weeks ago was naming all the apps i had! He mentioned safestrap, superuser, along with other apps that had nothing to do with rooting. He made it personal to which you can tell he was looking at what i had. Also, the second time the guy had me update My Verizon Mobile. This is what they use to get access to your phone. Be warned everyone!
Click to expand...
Click to collapse
This is why you should not grant verizon mobile superuser rights i believe. The last update to Verizon mobile asked for these rights on my phone and I said no. I have a feeling that this is how they can see what you have on your phone.
Just my. 02
Sent from my SM-N900V using Tapatalk

dapimpinj said:
Hey guys, i recently bought a phone off of eBay and added insurance on it through open enrollment at Verizon. It was a refurb phone for Assurion. Now the issue is that the screen sometimes become unresponsive and requires me to shut the screen of and turn it back on in order for it to function (The screen never has issues with the spen though). Upon calling Verizon, i was still rooted and it looks like they can actually look through you phone and see if you have root and what applications you have include safe strap. I pretended that i didn't know what the guy was talking about and told him i had nova launcher and that was probably my problem. I then performed a clean Odin factory stock wipe and the phone is back to normal. The knox hasn't even been tripped. When i called back verizon the guy told me "it looks like the phone was rooted the last time you called and now it's absolutely clean. I'm sorry, but because it was rooted, you're warranty is void". Always unroot before you call in!
Do you guys think i can contact Samsung and have them fix this issue for me? I doubt they will know if im rooted if i remove it all before i send it right
Click to expand...
Click to collapse
I recently called because I was having proximity sensor issues. I immediately explained to the technician all of the steps I've taken to try to fix the problem and he agreed that I had everything possible so he was just going to issue a new device to me. I was still rooted at the time but he did not check my apps. Verizon has been doing this for a few years now but if you're smooth on the phone and explain all the steps you've taken upfront you can avoid them checking your apps. Google is able to do the same thing.

airmaxx23 said:
I recently called because I was having proximity sensor issues. I immediately explained to the technician all of the steps I've taken to try to fix the problem and he agreed that I had everything possible so he was just going to issue a new device to me. I was still rooted at the time but he did not check my apps. Verizon has been doing this for a few years now but if you're smooth on the phone and explain all the steps you've taken upfront you can avoid them checking your apps. Google is able to do the same thing.
Click to expand...
Click to collapse
Awww man, I know that this is a hardware issue and the root did nothing to it. I realized that this is an assurion replacement as the sticker on the inside of the phone says that. It looks like they didn't fix the phone correct when sending it to the previous owner. Debating if I should add insurance through the open enrollment Verizon is having and just submit a claim. And before anyone says "that would be warranty fraud since you already have an issue"... Keep in mind that assurion issued this phone with issues so technically I should get a free replacement.

dapimpinj said:
Awww man, I know that this is a hardware issue and the root did nothing to it. I realized that this is an assurion replacement as the sticker on the inside of the phone says that. It looks like they didn't fix the phone correct when sending it to the previous owner. Debating if I should add insurance through the open enrollment Verizon is having and just submit a claim. And before anyone says "that would be warranty fraud since you already have an issue"... Keep in mind that assurion issued this phone with issues so technically I should get a free replacement.
Click to expand...
Click to collapse
Call back and when you can say what option you would like say "cancel service", you'll immediately get transferred to their "do what we can to keep you as a customer" department. Explain to them the issue you're having and that yes, the phone was rooted, but it has been returned to it's original software and the issue is still there. Tell them that you were unaware that rooting your phone would void the warranty and that you've had issues since receiving the replacement. It's worth a shot and may work.

aithe 2362289 said:
Call back and when you can say what option you would like say "cancel service", you'll immediately get transferred to their "do what we can to keep you as a customer" department. Explain to them the issue you're having and that yes, the phone was rooted, but it has been returned to it's original software and the issue is still there. Tell them that you were unaware that rooting your phone would void the warranty and that you've had issues since receiving the replacement. It's worth a shot and may work.
Click to expand...
Click to collapse
Thank you for helping out. This sounds like a good idea. Although I still have about 1 year left of service left so they may use that against me. I also cancelled the $3 extended warranty yesterday since it was rendered "useless". The sad part is the only reason I rooted the phone was to increase the maximum output for the volume.

dapimpinj said:
Thank you for helping out. This sounds like a good idea. Although I still have about 1 year left of service left so they may use that against me. I also cancelled the $3 extended warranty yesterday since it was rendered "useless". The sad part is the only reason I rooted the phone was to increase the maximum output for the volume.
Click to expand...
Click to collapse
When you first call ask them how much it would cost to cancel your service, then they'll ask why at some point.

I would talk with Verizon and see what they say. Unroot first though. Should be fine. When assurien sends phones out they are refurbished so still claimable.
Sent from my SM-N900V using XDA Premium 4 mobile app

Bonniecal said:
its very important to read the instruction of warranty. if you do anything out of the warranty rule then your warranty will void. for this read the warrany book before using the phone. thanks
Click to expand...
Click to collapse
Sent from my SM-N900V using XDA Premium 4 mobile app

airmaxx23 said:
When you first call ask them how much it would cost to cancel your service, then they'll ask why at some point.
Click to expand...
Click to collapse
Thanks for you reply man, i really appreciate it. Before calling, i decided to try something out. I took apart the 12 screws on the back of the phone and pried the back off with my finger nail. Then i disconnected the LCD/Digitizer ribbon cable and blew some air there, i then re-fastened it and mad sure to push a little hard on it. I've been running strong so far for 15 minutes and everything is working smoothly with no touch screen issues! Let's hope it keeps working :highfive:

jmc2543 said:
I would talk with Verizon and see what they say. Unroot first though. Should be fine. When assurien sends phones out they are refurbished so still claimable.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had them send me a brand new phone before.

Borderpatrol1987 said:
I had them send me a brand new phone before.
Click to expand...
Click to collapse
Even though you rooted?

dapimpinj said:
Even though you rooted?
Click to expand...
Click to collapse
Yup, I called assuron and reported the claim to them.
Sent from my SM-N900V using XDA Free mobile app

I called vzw to get another battery, and according to them, using strong wifi results in more battery usage than poor LTE. First I've heard that.
Sent from my SM-N900V using XDA Free mobile app

[Q] Do you care about your flash counter?

I keep seeing all these posts worrying about your flash counter. Seriously, who is actually gonna go out of their way to go into DL mode and actually look?

hkbladelawhk said:
I keep seeing all these posts worrying about your flash counter. Seriously, who is actually gonna go out of their way to go into DL mode and actually look?
Click to expand...
Click to collapse
Repair depot technicians, that's who! LOL
It's funny actually, I don't even think I have a warranty on my international model, but I still haven't rooted my Note 4...

I think the bigger drawback of rooting is that OTA updates may no longer happen . Or am I confused there?

I've had two different rooted S3s replaced at Best Buy and they have never checked for anything.
EDIT: But I did revert back to the stock rom before going to BB.
Sent from my SPH-L710 using XDA Free mobile app

schlepprock said:
I've had two different rooted S3s replaced at Best Buy and they have never checked for anything.
EDIT: But I did revert back to the stock rom before going to BB.
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
What was the reason you brought two S3's back? I'm sure if it was something that needed immediate replacement, they may not bother, but a "regular" repair might involve checking your software/counters.

I don't really care since mine is far away from Hong Kong, and I think it doesn't support warranty (not too sure). I won't wait even it does, pretty sure it will gonna take over a month to get it fix plus fees. And I always change a new phone after a year, so unless hardware failure, I'm happy to have it even it tripped the Knox~
P.S. I rooted my phone straight away after I unpack it Now counted 2 already~

Normally rooting and Xposed is the first thing I'd do but I havent done it yet as I'm nervous about the flash counter and losing OTA updates. Really need root though for Viper and Xposed.

EP2008 said:
What was the reason you brought two S3's back? I'm sure if it was something that needed immediate replacement, they may not bother, but a "regular" repair might involve checking your software/counters.
Click to expand...
Click to collapse
The first time it was due to bad modem/radio( bad reception and dropping calls). The second time they couldn't have checked anyway, I destroyed it with a skid steer. But we've taken our kids S3s several times to be replaced and they didn't go into settings or anything like that so I know best Buy at least, doesn't know anything about checking for root.

On US carriers tripping Knox may be an issue with the 'Full-Price' upgrades (Next, etc.) -- That is how I picked up my N4, but if they look in detail, I would be on the hook for the remainder of the balance even though I had surrendered the phone back to them. There may be a work around / bypass eventually - there were in past phones that utilized counters. I would think there would be one if someone had the knowledge to dump everything and reload after a 'hard wipe'. They need to install them at the factory somehow. I am probably grasping at straws as my cooking experience was Windows Phones.