Related
So today as I was preparing to flash the latest AOKP rom at 90% battery, I accidentally hit reboot to bootloader instead of recovery. No problem, i hit reboot. The screen turned black and a minute later it was still black, so I removed the battery. Nothing turned it on, couldn't access the bootloader and the charging light wouldn't even go on.
That was odd, so i thought maybe it was just still in bootloader mode. I gained access to ADB and it doesn't see the device at all (yes i tried the method explained because of the CWM problem, I also do not have CWM and have had a battery die before and it was able to charge fine) I also tried fastboot and it just sits at "waiting for device"
I called up Verizon support figuring it was the battery and they said i could test it at a store. The rep didn't think it was the battery, but when he tested it said 3/3 times it was increment, so it was bad. Then when he tried a regular battery it didn't work either, so he said the phone was bad.
Now, i called support and they are sending me a new phone and i am going to exchange my extended battery for a good one tomorrow. The thing is the lady on the phone said that as long as there were no hardware defects or unauthorized software than there wouldn't be any charge but if there was then it would be a $200 charge added onto the bill. A $200 charge would be pretty bad.
I would never return my phone if i messed it up actually doing something to the phone but here it didn't... at least not in any way I can think of. I am worried about the charge though. I know they usually don't check them but I had the Juopunut bear h-boot and neo's ICS installed. I am not even sure if it's recoverable at all because from everything i tried it definitely wasn't.
Am i just being silly here?
If they can't even boot the phone, then there is no way that they can tell it was hacked.
Sounds like the only way they'll get the phone booting is to do the manufacturer RUU thing with their special tools, so I'd say you're in the clear.
I've sent a phone back that was S-OFF running CM9. If they check before they JTAG it, I've seen no evidence of it.
I had heard before many times that they never checked, but i was extremely surprised whenever she said that. I wanted to ask some of you guys your opinion as well. I doubt it's recoverable without a full sbf as well, so i should be fine. Thanks!
Reaper0294 said:
I had heard before many times that they never checked, but i was extremely surprised whenever she said that. I wanted to ask some of you guys your opinion as well. I doubt it's recoverable without a full sbf as well, so i should be fine. Thanks!
Click to expand...
Click to collapse
I had to send mine back for a screen hardware issue. I was still s- on with the bootloader saying relocked and I did not get hit with that charge. As stated before I have heard of people sending back their phones with different ROMs without issue. Good luck
Sent from my Rezound using xda app-developers app
I've returned multiple devices saying relocked in the bootloader. I think Verizon simply doesn't care to be honest.. Hell I've even gotten a replacement phone that was rooted and running custom software. Shows you how muc hattention they pay to the devices they recieve and send out. Hell I've gotten replacements with screen protectors still on them and big ass gashes/scratches on the screen. 100 point inspection my ass.
Same here; my first Rezound was S-OFF, bootloader unlocked when the USB port failed (the unit would charge but couldn't connect to PC). I just factory reset it and sent it back. The folks who refurbish the phones don't even turn 'em on, and if they did, they probably wouldn't know what they were looking at. The things are bulk reflashed, if the motherboards are even retained at all.
Hi, uh I started another thread on making sure things got backed up. Which I did properly and everything was good. So today I haven't done anythign and was waiting for the new slim rom to make it's debute hopefully this week sometime as that is the one that appeals to me the most. Anyways, today my phone just got super hot, far hotter than before and it decided to die on me...I think. it shut off and I haven't been able to turn it on. Could this be a side effect of installing twrp/unlocking the bootloader/rooting? Or would it be a defective unit? One concern I had was getting a defective unit so i waited out my 30 days before even considering doing all this. So yea my 30 days from att is up. Would there possibly be a way to get a new phone from att or does anyone have any tricks on getting it back online? I personally think it was an overheating issue, but my phone is now cooled down.
So i went to the att store and of course they won't do anything. They told me to call some number they gave me. If I return it will they know it was boot unlocked and rooted? I can't turn it on at all. Using a power source or connecting to my computer nor my car charger...
blamster said:
Hi, uh I started another thread on making sure things got backed up. Which I did properly and everything was good. So today I haven't done anythign and was waiting for the new slim rom to make it's debute hopefully this week sometime as that is the one that appeals to me the most. Anyways, today my phone just got super hot, far hotter than before and it decided to die on me...I think. it shut off and I haven't been able to turn it on. Could this be a side effect of installing twrp/unlocking the bootloader/rooting? Or would it be a defective unit? One concern I had was getting a defective unit so i waited out my 30 days before even considering doing all this. So yea my 30 days from att is up. Would there possibly be a way to get a new phone from att or does anyone have any tricks on getting it back online? I personally think it was an overheating issue, but my phone is now cooled down.
So i went to the att store and of course they won't do anything. They told me to call some number they gave me. If I return it will they know it was boot unlocked and rooted? I can't turn it on at all. Using a power source or connecting to my computer nor my car charger...
Click to expand...
Click to collapse
Ok, so, im not sure if by return you mean, return for an exchange or simply a return as ATT will probably only send you a reman unit for yours and not allow an actual return. If you havent called them yet, i would recommend it. I have dealt with them many times in the past and one thing that has always shocked me is that they never have asked me about, or even commented on, how rooting or unlocking prevents them from exchanging it. Even during the disclaimer, they have never once said that if the device has been modified they wont allow the exchange.
I say all of this because should they not mention anything like that, and you send it back, im fairly sure you can claim you didnt know and werent told, and they will take care of it. Also, i say this because i personally sent back 3 bricked GS2s and an lg nitro as defective and got my reman units and every single one of them were rooted and such. So, i would feel safe. As long as they dont ask, and you dont lie to them, then there shouldnt be an issue. I wouldnt lie to them, i just dont mention it. AGAIN DO NOT lie to them or attempt to decieve them, i would never encourage that, but if its something they dont ask about, then, it, in my opinion, is not something that they are too concerned with.
cloudraker said:
Ok, so, im not sure if by return you mean, return for an exchange or simply a return as ATT will probably only send you a reman unit for yours and not allow an actual return. If you havent called them yet, i would recommend it. I have dealt with them many times in the past and one thing that has always shocked me is that they never have asked me about, or even commented on, how rooting or unlocking prevents them from exchanging it. Even during the disclaimer, they have never once said that if the device has been modified they wont allow the exchange.
I say all of this because should they not mention anything like that, and you send it back, im fairly sure you can claim you didnt know and werent told, and they will take care of it. Also, i say this because i personally sent back 3 bricked GS2s and an lg nitro as defective and got my reman units and every single one of them were rooted and such. So, i would feel safe. As long as they dont ask, and you dont lie to them, then there shouldnt be an issue. I wouldnt lie to them, i just dont mention it. AGAIN DO NOT lie to them or attempt to decieve them, i would never encourage that, but if its something they dont ask about, then, it, in my opinion, is not something that they are too concerned with.
Click to expand...
Click to collapse
Okay, thanks for the response. Sorry I was in a bit of a panic when I wrote that. But I have called ATT and they didn't ask me or mention in any disclaimer that if it's rooted or unlocked it won't qualify. I didn't mention it and so that does make me feel a lot better. Hasn't been physically damaged or come in contact with water so i'm pretty sure I'm safe. Thanks again.
blamster said:
Okay, thanks for the response. Sorry I was in a bit of a panic when I wrote that. But I have called ATT and they didn't ask me or mention in any disclaimer that if it's rooted or unlocked it won't qualify. I didn't mention it and so that does make me feel a lot better. Hasn't been physically damaged or come in contact with water so i'm pretty sure I'm safe. Thanks again.
Click to expand...
Click to collapse
They may or may not check when you return the phone. I returned my S3 a few months ago in exchange for a different phone but I forgot to unroot it and uninstall Superuser. The representative at AT&T didn't even turn the phone on. I didn't have anything to hide though, if they told me I couldn't return it because it was rooted then I would have sold it and purchased something else. I think the manufacturer is the one to worry about with these things. LG would definitely know if it were unlocked and they would be able to determine if rooting and unlocking the phone caused the problems you described.
johnbyebye said:
They may or may not check when you return the phone. I returned my S3 a few months ago in exchange for a different phone but I forgot to unroot it and uninstall Superuser. The representative at AT&T didn't even turn the phone on. I didn't have anything to hide though, if they told me I couldn't return it because it was rooted then I would have sold it and purchased something else. I think the manufacturer is the one to worry about with these things. LG would definitely know if it were unlocked and they would be able to determine if rooting and unlocking the phone caused the problems you described.
Click to expand...
Click to collapse
Well if they can turn it on I will gladly take it back due to them not accepting. I couldn't turn it on by anymeans, even plugging it in there is no lights to signifying it is receiving power. But i heard this phone had overheating issues in the first wave (or two) so it's probably for the best to get a new one. They are currently mailing me a new one and so I should receive it next week sometime hopefully.
blamster said:
Well if they can turn it on I will gladly take it back due to them not accepting. I couldn't turn it on by anymeans, even plugging it in there is no lights to signifying it is receiving power. But i heard this phone had overheating issues in the first wave (or two) so it's probably for the best to get a new one. They are currently mailing me a new one and so I should receive it next week sometime hopefully.
Click to expand...
Click to collapse
Sounds like everything worked out.
im in the same boat as you... completely dead phone. But I did open it to see of the battery pull would work. Do you think that theyll check and refuse my warranty because I opened it? the phone on the outside is NEW. Btw do you have a contract/account with ATT? I bought mine off ebay and used it on tmo...
I have the exact same problem! Totally dead phone that the charging light won't even turn on for. Unfortunately there is a small crack in the bottom left of the phone that was caused months prior so ATT wont give me a new one...
send it for repairs! I had rooted and unlocked mine so ATT didnt cover my warranty, but I only paid 50 bucks for the repairs and now I have my phone back!
Hey guys, so I recently picked up the S4 as I had an upgrade and chose this phone specifically for it's support by developers here on XDA. Strictly due to my own aloofness, and not having checked the forums for a few weeks before walking into the store (fail), I ran the update as it popped up immediately and I figured "why not" (I KNOW, I went full-retard and expected something useful from a Verizon OTA... they screwed me last time with an OTA too ).
Anyway, I still have about ten days before my "Worry-free Guarantee" runs out, and I'm really considering going back and claiming a warranty replacement on my phone in an attempt to receive a non-VRUAME7-equipped phone (as I said, the 16GB versions in stock there didn't have the update initially). If I attempt to claim the phone as defective, do you think I could avoid the $35 restocking fee, considering I'd swap for the exact same model of phone?
I'm not sure what to expect when going back there. Some CSR's seem much more technical than others, so I don't know if I'd be drilled about the issue I'm claiming. Any advice here? Would focusing on a 'bad battery' or 'device overheating' raise any red flags? Should I bring it in drained of battery life? I've kept excellent care of the phone; it's in mint condition without a scratch or blemish, non-rooted, and fully updated.
Even if I have to pay the $35 fee, I would do it for a non-updated phone. I'm just worried that by chance the CSR that gives me my replacement would decide to run the upgrade, as it will pop up immediately. Also, any tips on ensuring I avoid the upgrade until I back up the phone and root it? Just yank out the SIM until it's good to go?
Thanks for any advice you may have. I'm new here so flame me relentlessly for any rules I may have broken . And yes, I know, ultimately I'm complaining about having an S4 (read: kinda being a *****).
I stopped the update by turning off WiFi and data until I had it rooted and ROMed
Sent from my SCH-I545 using xda premium
My understanding of the guarantee is that it can be returned for any reason. I can't tell from a quick Google search, but it sounds like you might have a shot at no restocking fee if you're exchanging for the same model.
Given those tidbits, I'd tell them you want to exchange the phone due to reduced functionality after the update, and leave it at that. If they offer to troubleshoot, you can then say "sure, remove the update", which they can't do. I think this approach will give you the best chance of leaving the store with an un-updated phone and no fee. No CSR is going to take the OTA after having to deal with the guy who really hates the update for nonspecific reasons.
Sent from my SCH-I545 using xda premium
TheJ0hnman said:
My understanding of the guarantee is that it can be returned for any reason. I can't tell from a quick Google search, but it sounds like you might have a shot at no restocking fee if you're exchanging for the same model.
Given those tidbits, I'd tell them you want to exchange the phone due to reduced functionality after the update, and leave it at that. If they offer to troubleshoot, you can then say "sure, remove the update", which they can't do. I think this approach will give you the best chance of leaving the store with an un-updated phone and no fee. No CSR is going to take the OTA after having to deal with the guy who really hates the update for nonspecific reasons.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Interesting point, TheJ0hnman. I think turning window animations to something atrocious will help me have something that seems effed upon a cursory check, as well as some other developer options that undoubtedly make you think "wtf" if you don't know better, like flash on update etc. (wish I could then rehide the developer menu). Do you really think blaming the update would work well? I think I'd rather feign ignorance and say that the update "screwed with everything, battery life and runs slow", and act as if I'm unfamiliar with technical operation of android.
I don't think user error is covered under the 14 day WFG .
Why not keep it simple by saying you just want to swap colors. Whichever is less popular (white?) might have a bigger stock backlog & thus be more likely to have MDK firmware. Then either be bold and ask them not to update OTA, or be in a terrific hurry to get somewhere else and tell them you'll activate and set the phone up yourself.
cantare said:
Why not keep it simple by saying you just want to swap colors. Whichever is less popular (white?) might have a bigger stock backlog & thus be more likely to have MDK firmware. Then either be bold and ask them not to update OTA, or be in a terrific hurry to get somewhere else and tell them you'll activate and set the phone up yourself.
Click to expand...
Click to collapse
That makes a lot of sense, cantare. Only thing is I might end up paying the restocking fee. I think I'll try the warranty replacement first. Imagine me going through all this just to get another VRUAME7'd phone!
soad1789 said:
Hey guys, so I recently picked up the S4 as I had an upgrade and chose this phone specifically for it's support by developers here on XDA. Strictly due to my own aloofness, and not having checked the forums for a few weeks before walking into the store (fail), I ran the update as it popped up immediately and I figured "why not" (I KNOW, I went full-retard and expected something useful from a Verizon OTA... they screwed me last time with an OTA too ).
Anyway, I still have about ten days before my "Worry-free Guarantee" runs out, and I'm really considering going back and claiming a warranty replacement on my phone in an attempt to receive a non-VRUAME7-equipped phone (as I said, the 16GB versions in stock there didn't have the update initially). If I attempt to claim the phone as defective, do you think I could avoid the $35 restocking fee, considering I'd swap for the exact same model of phone?
I'm not sure what to expect when going back there. Some CSR's seem much more technical than others, so I don't know if I'd be drilled about the issue I'm claiming. Any advice here? Would focusing on a 'bad battery' or 'device overheating' raise any red flags? Should I bring it in drained of battery life? I've kept excellent care of the phone; it's in mint condition without a scratch or blemish, non-rooted, and fully updated.
Even if I have to pay the $35 fee, I would do it for a non-updated phone. I'm just worried that by chance the CSR that gives me my replacement would decide to run the upgrade, as it will pop up immediately. Also, any tips on ensuring I avoid the upgrade until I back up the phone and root it? Just yank out the SIM until it's good to go?
Thanks for any advice you may have. I'm new here so flame me relentlessly for any rules I may have broken . And yes, I know, ultimately I'm complaining about having an S4 (read: kinda being a *****).
Click to expand...
Click to collapse
Unfortunately it's yourself that screwed you. Not the OTA.
Root users know NEVER to take an OTA.
Hi Everyone. I just upgraded to the S4 last Sunday and while I was in the store and they were activating the phone, it started the update. I did not realize that this update locked everything down.
So, I decided that I would wait it out and see when the new update would be cracked. That was a couple days ago and I was having flash withdrawals. This morning I figured I would go to the Verizon store near work and just ask straight up ask if I could return my phone because of the new update....and as soon as the words update came out of my mouth, the girl interrupted me and said "Yes, we are having all kinds of issues with the new update and have replaced phones all weekend. We will get you a new phone".
5 mins later, new phone in hand with MDK software. AND the whole store told me not to take the update that another one is in the works. Can't wait to get home and root this thing and get Andy's Bone Stock ROM running.
anyone know the status on refurbs with the update?
i might have to get mine replaced due to brightness problems on my buttons and curious how well people are doing with the refurbs
kaos2569 said:
Hi Everyone. I just upgraded to the S4 last Sunday and while I was in the store and they were activating the phone, it started the update. I did not realize that this update locked everything down.
So, I decided that I would wait it out and see when the new update would be cracked. That was a couple days ago and I was having flash withdrawals. This morning I figured I would go to the Verizon store near work and just ask straight up ask if I could return my phone because of the new update....and as soon as the words update came out of my mouth, the girl interrupted me and said "Yes, we are having all kinds of issues with the new update and have replaced phones all weekend. We will get you a new phone".
5 mins later, new phone in hand with MDK software. AND the whole store told me not to take the update that another one is in the works. Can't wait to get home and root this thing and get Andy's Bone Stock ROM running.
Click to expand...
Click to collapse
Wow. I hope I have a similar experience! kaos2569, you got a black 16gig this morning and it was pre-ME7? This truly gives me hope.
Yes, I went to the store, and it was swapped out no problem. I didn't try to scam, or make up anything up. I just said what I posted and she stopped me mid sentence and knew about the update and how it was messing people's phones up and grabbed a brand new pre-updated one.
I just finished up rooting, installed a recovery, and installed Bone Stock. Everything went flawless.
kaos2569 said:
Yes, I went to the store, and it was swapped out no problem. I didn't try to scam, or make up anything up. I just said what I posted and she stopped me mid sentence and knew about the update and how it was messing people's phones up and grabbed a brand new pre-updated one.
I just finished up rooting, installed a recovery, and installed Bone Stock. Everything went flawless.
Click to expand...
Click to collapse
my phone should be here weds, so ill give this a try this weekend. unless the doodoo brown ones come pre-update.
kaos2569 said:
Yes, I went to the store, and it was swapped out no problem. I didn't try to scam, or make up anything up. I just said what I posted and she stopped me mid sentence and knew about the update and how it was messing people's phones up and grabbed a brand new pre-updated one.
I just finished up rooting, installed a recovery, and installed Bone Stock. Everything went flawless.
Click to expand...
Click to collapse
Wow do I feel sly! My experience was not quite as straightforward as yours, kaos2569, but I pulled it off! I had to convince two CSRs, one who actually also owned an S4 and was clearly no n00b (though he said he had the ME7 update so I guess not an XDA regular). I used one of the update screens in developer options to trick the first lady, who then restarted my phone and had me wait to be seen. While waiting, I went back and turned on developer options again, then turned them off, realizing beforehand that open apps will retain the "screwy" look even with the options off. The guy proceeded to investigate my phone for what must've been 20 minutes. I kept insisting the problem was intermittent and hinting at the possibility that the update played a role in the problem. After some skepticism (he noticed the developer options were off but the menu was available; I played dumb, saying I let a gadget-freak friend look at it for a bit), he finally offered me a free(!) replacement and I took it. I was waiting for a while once he got the new phone out, and was getting nervous that he might've been installing the update. He said "I'm downloading the update now, I'll run through it here to make sure there are no issues" so I immediately told him I had to be somewhere in ten minutes. He handed my phone back to me, I turned it off immediately, pulled the battery, and went home. Pulled the SIM card and booted-- still MDK indeed! Wow. It was a process but it was worth it. Can't wait to get some custom ROMs on this!
I can understand the animosity some people might have over doing something like this, but I was scarred by Verizon for nearly the entirety of the two years I had had my old phone, due to another damn OTA update, which didn't lock me out, but installed Gingerbread and made the phone basically impossible to use (legit, 12 seconds to open the ****** dialer). I just couldn't let Verizon lock me down again without a fight. And I will *SURELY* remember that guy the next time an upgrade comes along.
Thanks again kaos! You gave me the confidence to believe it could be done, and that it wasn't too late!
all i did was take it back within first 14 days... before i did though i went into app settings and disabled all apps including play store so they were not visible in app drawer. i told him it was freezing and soft booting itself after i updated the phone.. then i told him i called in and spoke with a tech n did a factory reset and everything dissappeared including my apps and i cant dl apps since my play store is gone.. he was lookin at it for a bit and was like wow thats weird! i told him the tech said since i was within 14 days he told me to go back to the store and exchange for a new one that wasnt updated.. worked like a charm! i told him not to update it that ill decline it until they come out with a new update n that was it! rooted n installed twrp soon as i got home been flashin every rom on here since! currently on hyperdrive n lovin it!
Sent from my SCH-I545 using xda app-developers app
soad1789 said:
Wow do I feel sly! My experience was not quite as straightforward as yours, kaos2569, but I pulled it off! I had to convince two CSRs, one who actually also owned an S4 and was clearly no n00b (though he said he had the ME7 update so I guess not an XDA regular). I used one of the update screens in developer options to trick the first lady, who then restarted my phone and had me wait to be seen. While waiting, I went back and turned on developer options again, then turned them off, realizing beforehand that open apps will retain the "screwy" look even with the options off. The guy proceeded to investigate my phone for what must've been 20 minutes. I kept insisting the problem was intermittent and hinting at the possibility that the update played a role in the problem. After some skepticism (he noticed the developer options were off but the menu was available; I played dumb, saying I let a gadget-freak friend look at it for a bit), he finally offered me a free(!) replacement and I took it. I was waiting for a while once he got the new phone out, and was getting nervous that he might've been installing the update. He said "I'm downloading the update now, I'll run through it here to make sure there are no issues" so I immediately told him I had to be somewhere in ten minutes. He handed my phone back to me, I turned it off immediately, pulled the battery, and went home. Pulled the SIM card and booted-- still MDK indeed! Wow. It was a process but it was worth it. Can't wait to get some custom ROMs on this!
I can understand the animosity some people might have over doing something like this, but I was scarred by Verizon for nearly the entirety of the two years I had had my old phone, due to another damn OTA update, which didn't lock me out, but installed Gingerbread and made the phone basically impossible to use (legit, 12 seconds to open the ****** dialer). I just couldn't let Verizon lock me down again without a fight. And I will *SURELY* remember that guy the next time an upgrade comes along.
Thanks again kaos! You gave me the confidence to believe it could be done, and that it wasn't too late!
Click to expand...
Click to collapse
And you are proud of this? It's because of people like you returning non defective products that the rest of the consumers have to suffer. tl;dr guess you have a total lack of integrity and morals to just accept your screw up. You sir are a douche bag.
Reading to learn about your device. Crazy, Who would of known.
Sent from my SCH-I545 using Tapatalk 2
zetsumeikuro said:
And you are proud of this? It's because of people like you returning non defective products that the rest of the consumers have to suffer. tl;dr guess you have a total lack of integrity and morals to just accept your screw up. You sir are a douche bag.
Click to expand...
Click to collapse
hexitnow said:
Reading to learn about your device. Crazy, Who would of known.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You guys are certainly entitled to your opinions, and I really don't disagree. I have egg on my face from the whole event. After all, it was my fumbling that screwed me over in the first place. However, I'm curious as to your feelings about Big Red itself. Like I said, this phone enticed me exactly for it's support by this community, and Verizon obviously realized that if they in turn locked the phone down with an update. What of that?
zetsumeikuro; this device will quickly be determined a Certified Like-New Replacement. I took pristine care of the phone, didn't screw around with the internals at all, and even kept the touchscreen under the manufacturer-issued screen protector the entire time I had the phone. If someone (due to their own bumbling) drops their phone in water, loses it, etc. They will end up with that phone and be very happy with it, unless they expected to luck out on a replacement and receive a pre-ME7 phone as well. I'm sorry, I can't say I see the harm in that, or how any other consumer suffers outright. I could've gotten a replacement within my 14 days for almost any reason. Yes-- I got out of a restocking fee and got a pre-update phone; what if I just paid $35 and got a Droid instead?
hexitnow, absolutely. I goofed up, that's for sure. I could attempt to excuse that by saying how I've been working 65-hour weeks and attempting to orchestrate a move into a new apartment lately, but I'm sure nobody really cares about that. Yes, I was negligent, having read up on the phone in early June thinking our upgrade was sooner than it actually was (and being treated oh-so-rudely by a CSR when we thought our upgrades were available back then), but ultimately it was me being stupid. I believe I learned a lesson here, and you rightly may resent me and people like me for our stupidity, but people make mistakes. This isn't my first or last one, either. Ultimately, it's just a phone update, I screwed nobody in doing what I did except arguably Verizon, who I managed to avoid paying yet another $35 to. I... I just don't feel that bad. I've felt wronged by them at every turn, and honestly I feel worse sticking with them as my carrier then I do taking advantage of my "Worry-free Guarantee" (assuming you don't worry about $35 fees).
Note that I am known to be a "whimsical douchebag", however.
soad1789 said:
You guys are certainly entitled to your opinions, and I really don't disagree. I have egg on my face from the whole event. After all, it was my fumbling that screwed me over in the first place. However, I'm curious as to your feelings about Big Red itself. Like I said, this phone enticed me exactly for it's support by this community, and Verizon obviously realized that if they in turn locked the phone down with an update. What of that?
zetsumeikuro; this device will quickly be determined a Certified Like-New Replacement. I took pristine care of the phone, didn't screw around with the internals at all, and even kept the touchscreen under the manufacturer-issued screen protector the entire time I had the phone. If someone (due to their own bumbling) drops their phone in water, loses it, etc. They will end up with that phone and be very happy with it, unless they expected to luck out on a replacement and receive a pre-ME7 phone as well. I'm sorry, I can't say I see the harm in that, or how any other consumer suffers outright. I could've gotten a replacement within my 14 days for almost any reason. Yes-- I got out of a restocking fee and got a pre-update phone; what if I just paid $35 and got a Droid instead?
hexitnow, absolutely. I goofed up, that's for sure. I could attempt to excuse that by saying how I've been working 65-hour weeks and attempting to orchestrate a move into a new apartment lately, but I'm sure nobody really cares about that. Yes, I was negligent, having read up on the phone in early June thinking our upgrade was sooner than it actually was (and being treated oh-so-rudely by a CSR when we thought our upgrades were available back then), but ultimately it was me being stupid. I believe I learned a lesson here, and you rightly may resent me and people like me for our stupidity, but people make mistakes. This isn't my first or last one, either. Ultimately, it's just a phone update, I screwed nobody in doing what I did except arguably Verizon, who I managed to avoid paying yet another $35 to. I... I just don't feel that bad. I've felt wronged by them at every turn, and honestly I feel worse sticking with them as my carrier then I do taking advantage of my "Worry-free Guarantee" (assuming you don't worry about $35 fees).
Note that I am known to be a "whimsical douchebag", however.
Click to expand...
Click to collapse
Don't see the harm in falsifying issues with a non defective device? I'm sure Samsung and Verizon will beg to differ. Yeah your device will probably get turned into a CLNR but clearly someone will be taking a hit for the brand new device you got. I mean the whole issue here that you seem to not see is the utter lack of integrity/honesty on your part. You screwing with developer options to make it look like the phone is having intermittent software issues to some untrained CSR. What you did there just reeks of desperation of you not willing to accept a mistake you made. I'm not going to go into the whole Verizon/Sammy locking down the device debacle, as there is the developer edition of the device. I'm not trying to defend Verizon and their ways.. Simply put it I'm disgusted with the lengths/measure you took to get a replacement device.
zetsumeikuro said:
Don't see the harm in falsifying issues with a non defective device? I'm sure Samsung and Verizon will beg to differ. Yeah your device will probably get turned into a CLNR but clearly someone will be taking a hit for the brand new device you got. I mean the whole issue here that you seem to not see is the utter lack of integrity/honesty on your part. You screwing with developer options to make it look like the phone is having intermittent software issues to some untrained CSR. What you did there just reeks of desperation of you not willing to accept a mistake you made. I'm not going to go into the whole Verizon/Sammy locking down the device debacle, as there is the developer edition of the device. I'm not trying to defend Verizon and their ways.. Simply put it I'm disgusted with the lengths/measure you took to get a replacement device.
Click to expand...
Click to collapse
As I said, you're entitled to your opinions. I could've swapped the phone for any reason, even if I just "didn't like it", as per Verizon's policy. Even if I paid$35 and swapped for an iPhone both Verizon and Samsung would've taken the same "hit". I just managed to avoid the restocking fee. But as you imply, I'm sure Verizon and Samsung will gather in a circle and weep.
They can take that $35 from the device upgrade fees they failed to mention in store. But I'm expected to maintain my full integrity.gotcha.
You sound like my father :laugh:
Verizon ran a special last night, LG G2 for free. I have been pining over this phone since getting one in my hands in the store, was just impressed. My Rezound has been the longest phone I've owned, but it's time is done. Late Nov 2011 until now.......an impressive stretch. But it's developed some issues recently that make me believe it's a goner. So the new white G2 is ordered and will be picked up tomorrow.
As for my rezound......if anyone is reading this......here's the issues it's developed, mainly after a particularly hard fall about two weeks ago. It was initially fine, but about 3-4 days later, it started boot looping out of nowhere. If I replace the battery it's hit or miss if it does it or not now. If it does, it could be 1-2 times, it could take over 10 minutes to get into the OS. Then in my car last week, I turned on Bluetooth (Chrysler Pacifica, has that Uconnect through the stereo) but it never fully turned on. Then two days ago the wifi quit picking up ANYTHING even though it says it's on. Now I notice the speaker (both headset and external) have gone very crackly.
I'm doubting it's software related, I think it's just been dropped one too many times. I'm going to try to reflash a stock kernel and factory ruu to set it back to stock (it's S-On, unlocked bootloader) and see how things work, but what are your guys opinion on whether or not that's worth my time?
Fastbird said:
Verizon ran a special last night, LG G2 for free. I have been pining over this phone since getting one in my hands in the store, was just impressed. My Rezound has been the longest phone I've owned, but it's time is done. Late Nov 2011 until now.......an impressive stretch. But it's developed some issues recently that make me believe it's a goner. So the new white G2 is ordered and will be picked up tomorrow.
As for my rezound......if anyone is reading this......here's the issues it's developed, mainly after a particularly hard fall about two weeks ago. It was initially fine, but about 3-4 days later, it started boot looping out of nowhere. If I replace the battery it's hit or miss if it does it or not now. If it does, it could be 1-2 times, it could take over 10 minutes to get into the OS. Then in my car last week, I turned on Bluetooth (Chrysler Pacifica, has that Uconnect through the stereo) but it never fully turned on. Then two days ago the wifi quit picking up ANYTHING even though it says it's on. Now I notice the speaker (both headset and external) have gone very crackly.
I'm doubting it's software related, I think it's just been dropped one too many times. I'm going to try to reflash a stock kernel and factory ruu to set it back to stock (it's S-On, unlocked bootloader) and see how things work, but what are your guys opinion on whether or not that's worth my time?
Click to expand...
Click to collapse
Are they discounting the full price on it too? I need to keep my unlimited.
As for the phone, what would you intend to do with it? They aren't worth much to sell, specially if it's damaged, if the screen is good, someone might take it off your hands for parts.
mjones73 said:
Are they discounting the full price on it too? I need to keep my unlimited.
As for the phone, what would you intend to do with it? They aren't worth much to sell, specially if it's damaged, if the screen is good, someone might take it off your hands for parts.
Click to expand...
Click to collapse
I don't know yet. I think I've still got my OG Droid hiding somewhere too.
I'm going to wipe it all and do a full factory ruu reflash and see if that doesn't help things out. I want to swap the outer bezel out because I closed my toolbox on it and ended up with a nice dent in the black chrome bezel. The LCD is fine, but I don't know about the digitizer considering the soft keys are really REALLY slow to respond anymore. I was thinking of rebuilding it for the fun and then I don't know. By rebuild I mean new circuit board because I think mine is the root of the issue. Won't know until after a factory reset, but the crackly speakers doesn't give me high hopes.
I really loved this phone. My biggest complaint was always the horrendous battery life. I have three batteries and could easily kill them all in a day with it. Guess I'm not done tinkering with it yet.
Hmmm.....looks like it may be getting sold for parts. It was bootlooping again tonight after I deactivated it and officially went full time to the G2. So I went into recovery (Amon Ra) and wiped everything, and did a recovery of a backup of Clean Rom that I'd done immediately after in install and setup back in July of 2012. And it's still boot looping. I get into the phone for just a few seconds, the SD card stuff tried to load, but neither Wifi or Bluetooth turn on. My guess is that the last couple of hard drops it took did the mainboard in. Good news is that I just pulled the Zagg InvisibleShield and the screen itself is freaking immaculate.
So I'm thinking one of two things. I could invest about $70 for a mainboard and a new outer bezel, see if that fixes it, and keep it as a spare phone. Or, just sell it as parts. I'm leaning towards a mainboard and bezel and just holding on to it, but I gotta say that I need to know if this is truly a mainboard issue or not.
Fastbird said:
Hmmm.....looks like it may be getting sold for parts. It was bootlooping again tonight after I deactivated it and officially went full time to the G2. So I went into recovery (Amon Ra) and wiped everything, and did a recovery of a backup of Clean Rom that I'd done immediately after in install and setup back in July of 2012. And it's still boot looping. I get into the phone for just a few seconds, the SD card stuff tried to load, but neither Wifi or Bluetooth turn on. My guess is that the last couple of hard drops it took did the mainboard in. Good news is that I just pulled the Zagg InvisibleShield and the screen itself is freaking immaculate.
So I'm thinking one of two things. I could invest about $70 for a mainboard and a new outer bezel, see if that fixes it, and keep it as a spare phone. Or, just sell it as parts. I'm leaning towards a mainboard and bezel and just holding on to it, but I gotta say that I need to know if this is truly a mainboard issue or not.
Click to expand...
Click to collapse
if after a full clean flash or even full factory restore you still have issues id lean towards hardware issues myself...and i hear you on battery life...i too have 3 batteries and the phone will die by the end of the day with it....i sold my daily rez for a different android but i still have my developer rez...which has been lately used for just that
I also just retire the rebound for similar reasons. I went with the note 3. Just picked it up yesterday. I was going to get the moto x to keep unlimited but was able to keep it with the N3.
I liking it so far. Not reboots or freezes. I think that is what finally got me. For the last few months, I could not get the red to run smoothly on any roms dating back to bean stock and maybe before. Gummy had worked great but for blacks screens that also happen on kitkat. I'm still keeping the red for roms as I am not going to root the N3.
Sent from my SM-N900V using Tapatalk
REV3NT3CH said:
if after a full clean flash or even full factory restore you still have issues id lean towards hardware issues myself...and i hear you on battery life...i too have 3 batteries and the phone will die by the end of the day with it....i sold my daily rez for a different android but i still have my developer rez...which has been lately used for just that
Click to expand...
Click to collapse
Yeah, the nandroid restore I did was, I think, CleanRom 1.4. But it was a totally clean install as I had installed it, set it up, and backed it up immediately. And it still just boots, gets into the UI, and about 30 seconds later reboots. I can't even get USB Debugging disabled so I can use Fastboot to relock the bootloader and flash an RUU.
I guess once my taxes come back in that I'll get a new logic board since ALL the modules seem to come with it (wifi, BT, etc) and get a new centerboard/outer bezel combo. Cost me about $70, but if I can get it up and running it'll be a nice backup phone. If anything, something to tinker with, lol.
Holy crap. I left it sit all night, and just turned it on and it booted! However, I try to turn Wifi on, and it just sits at "Turning Wi-Fi on......" so looks like wifi is definitely buggered. As it bluetooth.....same thing.
Just went into Settings and under Wi-Fi is says Error. Yep.....that's fubar.
It's SlimRom 1.6, just checked.
But the good news is that I now have USB Debugging enabled, so I can use Fastboot and relock and put a factory RUU on it. One last try, lol.
Fastbird, I had bought a used Rezound for my daughter over Christmas and when we tried it the wifi said the same thing as you stated, "turning on wifi". It would stay like that forever. I then went and put on ViperRez rom and then the wifi was fine. Not saying this will work for you as well but just a thought I had when I saw your problem. Good luck, hope it all works out for you.
Bryon
Fastbird said:
Yeah, the nandroid restore I did was, I think, CleanRom 1.4. But it was a totally clean install as I had installed it, set it up, and backed it up immediately. And it still just boots, gets into the UI, and about 30 seconds later reboots. I can't even get USB Debugging disabled so I can use Fastboot to relock the bootloader and flash an RUU.
I guess once my taxes come back in that I'll get a new logic board since ALL the modules seem to come with it (wifi, BT, etc) and get a new centerboard/outer bezel combo. Cost me about $70, but if I can get it up and running it'll be a nice backup phone. If anything, something to tinker with, lol.
Click to expand...
Click to collapse
you dont need to worry about usb debugging for an ruu....just boot to hboot and select fastboot and plug it in.....in my downgrade upgrade guide it will show all you need to do....the only thing you have to worry about with that is gaining s-off...an ruu wipes and reinstalls android completely...so any setting you set in rom will be wiped anyway....if wifi and all that still fails than it shows that the CleanRom is your issue....although downgrading and using the ruu.exe files require a locked bootloader and to be s-off
Also, the "turning WiFi on" issue, if it just stays like that, is usually an issue of a kernel/module mismatch... Remember when flashing a ROM or restoring a Nandroid when S-On you must flash the boot.img manually.
Sent from my Nexus 4 using Tapatalk
REV3NT3CH said:
you dont need to worry about usb debugging for an ruu....just boot to hboot and select fastboot and plug it in.....in my downgrade upgrade guide it will show all you need to do....the only thing you have to worry about with that is gaining s-off...an ruu wipes and reinstalls android completely...so any setting you set in rom will be wiped anyway....if wifi and all that still fails than it shows that the CleanRom is your issue....although downgrading and using the ruu.exe files require a locked bootloader and to be s-off
Click to expand...
Click to collapse
Now....I thought you had to be S-ON to run the RUU file? That crap-can's that idea then. I'm not S-Off. CleanRom isn't the issue. I ran a later version of it for 1.5 years, and the version I tried the restore from was 100% functional for me too. I don't think I'm going to bother flashing the phone as it sits because of the hardware issues. I'm just going to wait until I get a new logic board and then probably S-Off and play with flashing until I find something I like to sit on as a backup. The Screen is just too pretty for me to part with, lol.
Fastbird said:
Now....I thought you had to be S-ON to run the RUU file? That crap-can's that idea then. I'm not S-Off. CleanRom isn't the issue. I ran a later version of it for 1.5 years, and the version I tried the restore from was 100% functional for me too. I don't think I'm going to bother flashing the phone as it sits because of the hardware issues. I'm just going to wait until I get a new logic board and then probably S-Off and play with flashing until I find something I like to sit on as a backup. The Screen is just too pretty for me to part with, lol.
Click to expand...
Click to collapse
all ruu.exe files and ota.zips require s-off for downgrading..... ie. say your on an older version like 3.14.605.12 you can be s-on and upgrade to higher if im not mistaken...going s-off and redoing the whole phone from first to finish on ruu and ota's would be your last chance for that board without having to spend cash....and no offense you can probably get a used perfectly working rezound alot cheaper than 70 as well...is there any chance you deleted the wrong system files....only factory ruu will it restore original files...some deletions can cause these issues as well
The getting stuck turning Wifi on started BEFORE I tried a restore.
Shouldn't be a kernel mismatch because I used the same kernel for the nandroid CleamRom 1.6 and the other version of CleanRom I was running (I believe 1.7).
Only wiped Data, Cache, and dalvik cache. Several times for each.
The phone is acting EXACTLY like it was prior to the nandroid restore which is why I'm so sure it's a hardware issue. And I do mean exactly. 85% of the time after rebooting it boot loops for a random amount of time. Once booted in it's fine, save for Wifi and Bluetooth not working.
I understand I could get a replacement phone for cheaper to slightly more than te $70, but that's not the point. I like to tinker. I learn by doing. Gives me something to do.
Ok, relocked and trying to upgrade to a higher RUU which by what I read is acceptable. I flashed one of the earliest ICS firmware's and rom's, and the last RUU I could find was about 3 months later so I'm hoping it's good.f
*Edit* RUU took, trying to boot, but it's boot looping like normal. I think it's safe to say hardware is jacked at this point. It's getting into the UI then dying again, just like before.
Nappyloxs said:
I also just retire the rebound for similar reasons. I went with the note 3. Just picked it up yesterday. I was going to get the moto x to keep unlimited but was able to keep it with the N3.
Click to expand...
Click to collapse
How were you able to keep unlimited? My contract is over with my Rezound and I want to purchase a Galaxy S4. The best Verizon would offer me to give up my unlimited data is 6gb of data for $30.
Sent from my ASUS Transformer Pad TF700T using XDA Premium 4 mobile app
I recently sold a tablet on eBay that was working when I shipped it, I have pictures of it working both before and after I factory reset it. When the buyer received it, he emailed me saying it will not turn on, but I am 100% sure it was working when I shipped it out. The buyer has initiated a return, which pretty much means I have to refund the money as there is nothing I can really do to prove it was working when sent. I have pictures of it working, with the date stamp on the EXIF data, but I am almost certain PayPal / eBay will side with the buyer anyway so I would rather at least get the tablet back in my hands.
The tablet was not in the best shape, but the sold price reflected that and I was entirely honest in the description. Reading back through the messages from the buyer there are some red flags popping up that have me wondering if he tried to flash something to it and bricked it. In my auction description and in messages between us I had indicated it was rooted and running TWRP as well as a custom ROM. He had replied saying that he may end up flashing to the original ROM (this after also asking me if it was SIM unlocked, even though it clearly stated it is a wifi only tablet).
Is there any way to find out if he tried to flash something like a P605 ROM onto the P600 I sold him and bricked it? Assuming he did do something like that and I can connect to it somehow either via ADB or ODIN, will it be fairly straightforward to flash the correct ROM back onto it? I should have the tablet back tomorrow and will want to check it fairly quickly to see if the guy screwed it up himself or not.
The only thing that does not have me almost 100% certain of it is that he only had it a few hours before contacting me to say it was not working. However, I absolutely know I sent a working tablet and in all honesty, am going to be pretty annoyed if I get back a non-working tablet.
Thanks.