Database Info

Having Withdrawals Already!!!

Ok so today I mow my yard and I plug in my Thunderbolt in to the USB charger on my PC when I come inside my phone is bootlooping. So I think ok whatever I will flash one of the many backup's I made.
So I pull the battery and boot into the bootloader, then when I go into recovery after about 2 seconds the phone powers off and starts bootlooping again??? Ok that's a first for me and I have been flashing and rooting since launch day of the OG Droid, (ok, ok not since the first day but like a month later). So I pull the battery again this time for 30 minutes because I read someone else had something like this happen yesterday. When I put the battery back in same thing! Now I pull the battery for 4 hours...same outcome.
Now I'm thinking RUU time so I grab the stock RUU pull the SD card from my Thunderbolt pop it in my Incredible load the RUU renamed to PG05IMG.zip and put it back in the Thunderbolt. Load the bootloader and flash the RUU. Reboot after it's done and would you believe it...the same thing! the phone won't load past the splash screen before rebooting.
I forgot to mention before trying all this I tried using adb to reboot into recovery and I kept getting "error: device not found" and I know how to use adb.
It's only been about 9 hours since I've been able to use my 2.3.4 GingerBread with parts of 3.0 Sense Thunderbolt and I already having withdrawals how am I going to make the next 2 to 3 weeks while it's being repaired???
Ok end rant...

Go to verizon, swap it for a new one. Warranty case for sure.

bilbobrian said:
Go to verizon, swap it for a new one. Warranty case for sure.
Click to expand...
Click to collapse
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.

I'm loosing faith in the Thunderbolt. I really feel we are all just a bunch of beta testers.

bunklung said:
I'm loosing faith in the Thunderbolt. I really feel we are all just a bunch of beta testers.
Click to expand...
Click to collapse
Huh? Off topic and makes no sense.
//Tap'd on my TBolt while grounded\\

bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
I understand your rooted but if it cant boot up then there is a problem. Just go to verizon and show them. Once they see it cant boot properly they will exchange it or overnight one to you.
I apologize if Im missing something..

bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
You may get away with getting it swapped through warranty. But I can't promise you it won't come back at you. Someone may have a solution for you though. Wouldn't give up yet. Sorry I don't.
//Tap'd on my TBolt while grounded\\

chkmate said:
Huh? Off topic and makes no sense.
//Tap'd on my TBolt while grounded\\
Click to expand...
Click to collapse
*Shrug*
He has a problem, I do too. We both own Thunderbolts. Maybe I should have been more specific.
To each his own. The end.

bunklung said:
*Shrug*
He has a problem, I do too. We both own Thunderbolts. Maybe I should have been more specific.
To each his own. The end.
Click to expand...
Click to collapse
Well then relate your problem with his. Just saying "your losing faith in Thunderbolt" tells me nothing. Don't mean to sound like an a$$, just saying. When I read your first comment I got nothing from it.
That being said...I haven't been a Bolt owner for long, but it does seem like a strange issue. You would think flashing a radio or backup would resolve the issue. But hasn't.
//Tap'd on my TBolt while grounded\\

Definitely sounds like a Warranty Issue. I'd try to get it exchanged if no one can come up for a solution to the problem.

I had a G1 back in the day that had some odd problem and I was rooted, Tmo looked at it and wouldn't touch it. So, I called HTC. I told them that I purchased the phone off Craigslist so Tmo couldn't help me, and asked how the warranty works on their end. They said that since the production of the phone started less than a year ago, they knew it was still eligible for warranty even without a receipt. There would be a triage fee if it was found to be a non-warranty issue, and it was something like $40 including the shipping back. I acted dumb when they asked if it was rooted...asked them what that meant? LOL. Sent it in, they fixed it and sent it back to me, no charge. Fast too. I was very happy and that is why I have stuck with HTC since then. It may or may not work for you, but it was painless for me.

bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
Such chivalry is rare in these days.
Applaud. Best of luck!
Sent from my ADR6400L using Tapatalk

bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
They don't care. Take my word for it. If it never boots they won't care.

I'm actually having this exact same issue. Has anyone found a solution yet or is the only solution to have the phone replaced?

Wow. I thought for sure hbooting the unsigned stock RUU would fix this. How about hbooting a signed ruu? It wouldn't hurt at this point.
Also make sure when you renamed the pgimg05. Zip that there was nothing at the end of the extention. I've heard some people say that windows has been known not to show that full file extension correctly.

raider3bravo said:
Wow. I thought for sure hbooting the unsigned stock RUU would fix this. How about hbooting a signed ruu? It wouldn't hurt at this point.
Also make sure when you renamed the pgimg05. Zip that there was nothing at the end of the extention. I've heard some people say that windows has been known not to show that full file extension correctly.
Click to expand...
Click to collapse
I thought hbooting the stock RUU would fix it as well, and yep it was named correctly. It's funny because it would stay on the hboot screen as long as I let it with no issue what so ever but within 2 seconds of going into recovery it would reboot.
I went back to Best Buy today as that is where I bought it to see how much they would charge to ship it out to be fixed. The mobile manager remembered me because I was 1st on the pre-order list. (I'm sure we all remember the train wreck the Best Buy pre-orders became) So any way he really went out of his way to help me. He said he has had 3 other Thunderbolts brought in for the same issue. He was able to send my phone in under their Black Tie program.
I told him I rooted the phone and was willing to pay for the repairs but he said he was pretty sure that the other 3 phones were not rooted. He said that he knew FOR SURE that at least one of the phones was not rooted because the lady that owned it did not have any branches in her family tree, (his words not mine). Since he has seen it 3 times he was not charging me. He only asked that I had the stock hboot on the phone. I had already flashed that in my attempt to get it running.

I'm with cstrife, I managed to destroy my tab with a mix of flashing and charging via outlets in India. It bootlooped for a while then just kind of gave up and began to display a strange download screen when I plugged it in to charge. I brought it to VZW and played stupid, I told them I woke up and it had this weird screen... I had a brand new one at my door the next morning and haven't heard a word from them... It probably just costs more to check it out deep enough to find out its rooted than it does to just give you a refurbished one, gut swap yours, and then send to someone else as a refurbished one...
Sent from my SCH-I800 using XDA App

Had this happen to me and just pulled my SD card, rebooted and it was fine. Not saying it will work for u but give it a shot.
Sent from my ADR6400L using XDA App

bp328i said:
I thought hbooting the stock RUU would fix it as well, and yep it was named correctly. It's funny because it would stay on the hboot screen as long as I let it with no issue what so ever but within 2 seconds of going into recovery it would reboot.
I went back to Best Buy today as that is where I bought it to see how much they would charge to ship it out to be fixed. The mobile manager remembered me because I was 1st on the pre-order list. (I'm sure we all remember the train wreck the Best Buy pre-orders became) So any way he really went out of his way to help me. He said he has had 3 other Thunderbolts brought in for the same issue. He was able to send my phone in under their Black Tie program.
I told him I rooted the phone and was willing to pay for the repairs but he said he was pretty sure that the other 3 phones were not rooted. He said that he knew FOR SURE that at least one of the phones was not rooted because the lady that owned it did not have any branches in her family tree, (his words not mine). Since he has seen it 3 times he was not charging me. He only asked that I had the stock hboot on the phone. I had already flashed that in my attempt to get it running.
Click to expand...
Click to collapse
Honesty turned out to be the best policy in this case. Congrats.
Sent from my ADR6400L using Tapatalk

MrHawaii said:
Honesty turned out to be the best policy in this case. Congrats.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Thanks, now I just have to wait 2 to 3 weeks to get it back. What to do with all that time!!!

[Q] Should Verizon replace my phone?

I was running cm7 on my phone, and was throwing on the audio fix to get better speaker volume, which sent the phone into a boot loop. I tried to put my phone into hboot (power+volume-) which it does not. It tries to boot every time. I've tried probably 50+ times and same result. I'm guessing it has to deal with the poor built buttons on this phone and the volume down just does not work. My question is despite the fact I'm rooted and running cm7, am I safe to say this is a hardware issue? I just don't want to send in my phone to Verizon and get billed for the fact the phones "tampered" with.

Should verizon replace your phone after you borked it? I think you already know the answer

xebryus said:
I was running cm7 on my phone, and was throwing on the audio fix to get better speaker volume, which sent the phone into a boot loop. I tried to put my phone into hboot (power+volume-) which it does not. It tries to boot every time. I've tried probably 50+ times and same result. I'm guessing it has to deal with the poor built buttons on this phone and the volume down just does not work. My question is despite the fact I'm rooted and running cm7, am I safe to say this is a hardware issue? I just don't want to send in my phone to Verizon and get billed for the fact the phones "tampered" with.
Click to expand...
Click to collapse
long of it, no they shouldn't. will they? who knows, depends on if you tell them the truth or not.

Should they? Technically no. Will they? Sure. They would be happy to.

but he didnt break it if the loop comes from a hardware defect,all he did was get it to fail sooner than later basically what happened to others,so technically yes they should,or can anyone prove the software killed the hardware.
sent from a screamin' bamfed out tbolt

satseaker said:
but he didnt break it if the loop comes from a hardware defect,all he did was get it to fail sooner than later basically what happened to others,so technically yes they should,or can anyone prove the software killed the hardware.
sent from a screamin' bamfed out tbolt
Click to expand...
Click to collapse
Honestly, it doesn't matter if anyone can prove the software did it or not. He voided his warranty by rooting. But they likely will replace his phone, driving up the costs for future phones.
You rooted your phone. Take it for what it is...a non-warrantied phone.

Touchy
I will start off by saying I don't have a solid answer but being as it is a hardware problem they "should" fix it. Will they? Probably not. They'll take one look, see it's rooted, and tell you that you broke it by tampering with it. All bets are off as soon as the phone is rooted...unless you can unroot and take it in I think you're in trouble but since the button is broken you can't do anything with it. Good luck and let us know what you were able to get done.

I see what you guys are saying from a moral standpoint. I'm just angry cause I know for a fact my buttons are not up to par to what they're supposed to be. I don't want to fraud the companies over something that is my fault, but in this case I'm almost positive it's related to the fact this phone was not built too well. I dunno, do "authorized retailers" handle claims with faulty hardware or just official Verizon wireless stores?

This is why you should have ADB installed and working on your computer. Hook up the phone via USB, get into ADB and reboot into recovery. There are a few threads out there for ADB you should be able to find them using Google, hopefully that will be able to help you.

If you can get into the boot loader with and then you might be able to save your phone.. Maybe, not clear take your as card out and import the rhi, they might work...
Sent from my ThunderBolt using XDA App

if you can prove that the failure was not caused by rooting, then they should fix it for you under warranty. but that is hard to prove.

xebryus said:
I see what you guys are saying from a moral standpoint. I'm just angry cause I know for a fact my buttons are not up to par to what they're supposed to be. I don't want to fraud the companies over something that is my fault, but in this case I'm almost positive it's related to the fact this phone was not built too well. I dunno, do "authorized retailers" handle claims with faulty hardware or just official Verizon wireless stores?[/QUOTE
Did you try BOTH volume buttons at the same time? This got me to bootloader.
Click to expand...
Click to collapse

Just say you tried to install the last update and your phone wont boot now. They won't know the difference.

dpham00 said:
if you can prove that the failure was not caused by rooting, then they should fix it for you under warranty. but that is hard to prove.
Click to expand...
Click to collapse
Caused by rooting or not, there is NO warranty once a phone is rooted. Has nothing to do with what caused the malfunction.
ADB reboot bootloader or recovery should work though, as long as he catches it with the right timing during the loop.
Sent from my ADR6400L using XDA App

Well update on the situation. I called Verizon telling them I can't turn on my because it "freezes" when it tries to boot up every time. He told me to try a hard reset (try to go into hboot) and I told him I tried that at least 30 times and it won't. I said I think there's something wrong with my buttons because they're not very responsive and stick really easily (which they do) and he said they're overnighting a phone to me. That was yesterday, its waiting for me at home. I'm gonna send my old phone back asap.
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.

you're probably aright since they might just get it and toss it in the "to be refurbed" bin. It costs a lot of money to test every return. Good luck and let us know how it turns out.

xebryus said:
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
Click to expand...
Click to collapse
If they do find out, they will charge you. Don't know if they will, but be prepared for the worst.
Sent from my ThunderBolt using Tapatalk

Yes, they get broken down abd only really check for water/physical damage
Sent from the Swag ThunderBolt ADR6400L with some GingerLove (Gingeritis 1.0) using XDA Premium App
Must Watch Before Any Forum Post http://goo.gl/b4IJJ

xebryus said:
Well update on the situation. I called Verizon telling them I can't turn on my because it "freezes" when it tries to boot up every time. He told me to try a hard reset (try to go into hboot) and I told him I tried that at least 30 times and it won't. I said I think there's something wrong with my buttons because they're not very responsive and stick really easily (which they do) and he said they're overnighting a phone to me. That was yesterday, its waiting for me at home. I'm gonna send my old phone back asap.
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
Click to expand...
Click to collapse
Congrats on getting a new phone I guess.
I have noticed Verizon has been VERY accomodating with these phones. One call is all that's needed to get a new phone. Im guess they're so generous because they devices have been so finnicky so far and they just want to keep people pleased for now.
I envision them cracking down hard sooner or later though. They're not stupid. They've already come down on tethering and such, so it probably wont be long until they get hardcore on replacements.

My son works for VZ...
and he takes your calls... and this is what he told me. Anything covered under insurance (Asurion), they really don't check/don't care about rooting. VZ, on the other hand, will look pretty extensively if it's covered under the warranty. They will look for rooting or anything else that would break warranty coverage.

need advice, almost bricked tonight....

....i think? Running bamf ginger remix and the latest OTA radio not the leaks. I fixed my permissions and noticed my 4g kept going in and out. The phone got warm so i rebooted and got the splash screen, then it hung and rebooted two more times before booting normal. I literally freaked out for a second. Phone seems ok now. Should i be worried? What could cause this?

fixxxer2008 said:
....i think? Running bamf ginger remix and the latest OTA radio not the leaks. I fixed my permissions and noticed my 4g kept going in and out. The phone got warm so i rebooted and got the splash screen, then it hung and rebooted two more times before booting normal. I literally freaked out for a second. Phone seems ok now. Should i be worried? What could cause this?
Click to expand...
Click to collapse
Sounds like the radio to me. That's the thing that will suck up power the worst if it can't get it's crap together finding a signal, even to the point of heating that thing up. Mine starts cooking if I tether it and watch movies on it. Never had boot loops though, and I use the 1.70 radio for weeks.

im glad i have full insurance on this phone in case. so far, so good today. in case i do brick is there a way to set the phone back to stock before returning it?

fixxxer2008 said:
im glad i have full insurance on this phone in case. so far, so good today. in case i do brick is there a way to set the phone back to stock before returning it?
Click to expand...
Click to collapse
In that event, I say "Brick? What brick? It fell out of my pocket and sank to the bottom of a VERY deep lake." I've never had Asurion ask me for a phone back. The whole "My CRAZY ex stole it!" worked just fine.

loonatik78 said:
In that event, I say "Brick? What brick? It fell out of my pocket and sank to the bottom of a VERY deep lake." I've never had Asurion ask me for a phone back. The whole "My CRAZY ex stole it!" worked just fine.
Click to expand...
Click to collapse
yeah but there has to be a way to set it to stock in case right?

How do you "almost brick" a phone ? How does one know it was "almost" ?

fixxxer2008 said:
yeah but there has to be a way to set it to stock in case right?
Click to expand...
Click to collapse
I think if there was a way to set things back to stock, you wouldn't actually be bricked.

hallstevenson said:
How do you "almost brick" a phone ? How does one know it was "almost" ?
Click to expand...
Click to collapse
it started to endless reboot, that's what people say happened when they bricked.

loonatik78 said:
I think if there was a way to set things back to stock, you wouldn't actually be bricked.
Click to expand...
Click to collapse
if im correct i thought there was a way to do it. ill have to do some checking. if i had to bring it in, if they found out i was rooted it would void my warranty.

fixxxer2008 said:
if im correct i thought there was a way to do it. ill have to do some checking. if i had to bring it in, if they found out i was rooted it would void my warranty.
Click to expand...
Click to collapse
I don't really know what to describe the "brick situation" we were having back in the day with the first leaked gingerbread as. Technically, it's not REALLY a brick because many of them could be fixed. It was more of a boot-loop issue. That whole situation muddied the waters of what defines a brick, but before that I always understood a brick to be a completely useless device beyond any help. Whether it could be powered on to view the hboot S-on or S-off state, I don't know because thankfully I've never had that problem.
There's always the option of electrocuting it until it won't power on though. Take an electronic lighter, remover the piezo igniter, and use that to zap sensitive parts of it's guts until it never worked again. That's like a few thousand volts. Not much inside there will survive that for long. (Yes, I really do sit around thinking about how to destroying things in undetectable ways.)

it's funny because everytime i hear about someone getting insurance for their cell phone i think "lol.. sucker!" but broke 2 phones so far and had to "craigslist" like crazy to find replacements at decent prices.

fixxxer2008 said:
if im correct i thought there was a way to do it. ill have to do some checking. if i had to bring it in, if they found out i was rooted it would void my warranty.
Click to expand...
Click to collapse
When the boot loop of death thing happened people were still able to get into hboot. So from there you would just flash an RUU and get back to s-on. If it truly is the same issue people were having the phone will be s-on after the RUU, but it will still just bootloop. If you are using the patched hboot I don't know if you would be able go get back because I don't know if fastboot was functioning.
Sent from my HTC Thunderbolt

[Q] Htc Shift battery / device issue

I have an HTC Shift that is now a replacement phone Sprint sent because the other Shift bricked on a OTA update. The phone itself looks brand new. (we have had it since Apriil) The problem with the phone is that it will never charge the battery. I actually have 3 spare batteries so in total 4 batteries are charged to 100% but as soon as I put them into the Shift device the battery status will range from 0% to 8% an occassionally will charge to 12% but no higher. If I take the battery out and put it into another HTC it will show 95% or better as charged - to be clear this is the same battery that just seconds before registered 12% or less.
I've tried everything. I've changed Roms (the good thing about this is that I can tell you the ins and outs on about 12 different Roms and kernels now) I've changed up kernels. I installed Bettery Battery, battery calibration tools, spare parts...booted it up empty, let it stay off and "charge" all night, on and charge all night, factory reset, everything but RUU because it just won't do it and HTC update, won't do that either because of the battery being below 30%.
OK, so you say - take it back to Sprint and get a new one - can't do that because I can't unroot it with the RUU as it still shows s-off -
I'm brain dead on this one.
I'm not a newbie at this. I've rooted several phones, HTC, LG, Palm Pre, even turned the Palm Pixie to a wifi goddess in it's day by switching out the radio(you know). I've jailbroke the Iphone and Ipad. Rooted my Thrive and turned a pandigital into a sweet little android.
I don't want to take the phone back like it is. I want to figure out what the heck is the issue. (i know...i know) When I plug the phone in the led comes on as though it is charging but it never charges...any ideas? you know it's probably something simple and I've just fried my brain at this point. Any ideas? Anybody??
Thanks in advance for any input, ideas or helpful tips!
Sondee
We be - Riding With The Nerd Herd

I'm no expert on this, but if i were you i'd just brick the thing and take it to sprint.

jesuscash said:
I'm no expert on this, but if i were you i'd just brick the thing and take it to sprint.
Click to expand...
Click to collapse
Excellent advice... FAIL... COME ON MAN...
Make sure you are wiping the system partition as well... Going from sense to aosp needs a thorough system (not data) wipe... To wipe system, it's located in mounts and storage in recovery if using cwm...
Sent from my EVO LTE

My girlfriend's phone has the EXACT SAME ISSUE. No idea how to fix, I figure there's a contact or sensor hw at fault. It's not ROM specific, flashing a new rom won't make a diff. As soon as the gf or I get a new phone, I'll mess with the device itself.
Best advice - return it!

jkrlvgn said:
My girlfriend's phone has the EXACT SAME ISSUE. No idea how to fix, I figure there's a contact or sensor hw at fault. It's not ROM specific, flashing a new rom won't make a diff. As soon as the gf or I get a new phone, I'll mess with the device itself.
Best advice - return it!
Click to expand...
Click to collapse
Can't return something rooted unless you want your account flagged lol
Sent from my EVO using Tapatalk 2

YoungCorruptionV2.0 said:
Can't return something rooted unless you want your account flagged lol
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Been there.....not fun at first, but once CS knew I knew more than they did it was no longer an issue to have my account credited for the service I WASN'T getting. Most ever off was 165 from a 180 dollar bill
Sent from my myTouch_4G_Slide using Tapatalk 2

strapped365 said:
Been there.....not fun at first, but once CS knew I knew more than they did it was no longer an issue to have my account credited for the service I WASN'T getting. Most ever off was 165 from a 180 dollar bill
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
Well that's a lot of money. When i was buying the Evo LTE i didn't know i would have to give them my phone and so when she asked for it i was like ummm... I need to go home and do something real quick. She gave me a weird like and ask what i need to do and told her that i can't say. I think she knew i was rooted cause she told me i won't get in trouble but i just was like nope i don't want a flagged account so i'll be back in 30 minutes. She gave up at that point

YoungCorruptionV2.0 said:
Well that's a lot of money. When i was buying the Evo LTE i didn't know i would have to give them my phone and so when she asked for it i was like ummm... I need to go home and do something real quick. She gave me a weird like and ask what i need to do and told her that i can't say. I think she knew i was rooted cause she told me i won't get in trouble but i just was like nope i don't want a flagged account so i'll be back in 30 minutes. She gave up at that point
Click to expand...
Click to collapse
How I got stuck was I was having like extremely poor service and was waiting on a call back from them, and through reading what people said about them never calling I thought I was safe, about 30 minutes after I flashed cm7 a rep called and wanted me to go into epst and at that time I was so new to being a rooted user I had no idea it wasn't in aosp. So I tried the ## code and when she asked what happened I said nothing she said ok hang on while I flag your account. My first words to the rep was are you fu**ing kidden me! So I stabbed back by tethering to my ps3 while playing Modern Warfare lol
Sent from my myTouch_4G_Slide using Tapatalk 2

YoungCorruptionV2.0 said:
Can't return something rooted unless you want your account flagged lol
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
So...unroot before taking. As it says, there's an issue with reading the battery correctly. It's charging the battery, because when it goes into another phone, it shows the correct percentage.
It -has- to be a hardware issue. Unroot, RUU, whatever... there isn't an easy fix for this without messing with the hardware (which will likely result in ruining the device).
If the flex cables were shot, you'd all recommend the same thing. What's the difference with this?

There is a newer and easier way to unroot HERE

[Q] Static from headphone jack (questions about Moto service)

Hi, my headphone jack has always been pick about having things plugged in just right, usually the slightest bit of ling screws it up. Finally today, it just started giving serious static in right side. when music or any sound starts it goes away, but the volume is very low on that side. It only does it when there is power (battery is in), so I think it is a bad connection in there. I have some questions regarding this.
1. How horrible is the Motorola service? they say 5-7 days, but is that really the case (In the U.S.). My warranty is still good, I'll just flash back to stock.
2. will opening the phone up void my warranty? I am somewhat experienced with electronics, so I could probably fix it, but I don't wantt to void the warranty in case it doesn't work.
3. I also have a stuck pixel on my screen that has been there since I got the phone (New). Will they fix that as well even though I can only select one problem on the application form? Should I mention it as well so that they might fix it?
Thank you,
-lkrasner
P.S. Unfortunately this means that I might be unable to do much for a while when I send my phone away. I hope you guys get ICS without me, and I will be waiting to try it out myself.

lkrasner said:
Hi, my headphone jack has always been pick about having things plugged in just right, usually the slightest bit of ling screws it up. Finally today, it just started giving serious static in right side. when music or any sound starts it goes away, but the volume is very low on that side. It only does it when there is power (battery is in), so I think it is a bad connection in there. I have some questions regarding this.
1. How horrible is the Motorola service? they say 5-7 days, but is that really the case (In the U.S.). My warranty is still good, I'll just flash back to stock.
2. will opening the phone up void my warranty? I am somewhat experienced with electronics, so I could probably fix it, but I don't wantt to void the warranty in case it doesn't work.
3. I also have a stuck pixel on my screen that has been there since I got the phone (New). Will they fix that as well even though I can only select one problem on the application form? Should I mention it as well so that they might fix it?
Thank you,
-lkrasner
P.S. Unfortunately this means that I might be unable to do much for a while when I send my phone away. I hope you guys get ICS without me, and I will be waiting to try it out myself.
Click to expand...
Click to collapse
Just do a mis-flash or delete the system partition and take it into a store and tell/show them it does not boot, that you picked it up off the charger and it was like that, and you need a replacement. They will send you a replacement and you have 30 days to return your "broken" phone. I have done this 4 times with my A2s.

jimbridgman said:
Just do a mis-flash or delete the system partition and take it into a store and tell/show them it does not boot, that you picked it up off the charger and it was like that, and you need a replacement. They will send you a replacement and you have 30 days to return your "broken" phone. I have done this 4 times with my A2s.
Click to expand...
Click to collapse
But my AT&T warranty is up?!?! will it still work? I still have my 1 year moto warranty.
Edit: If this does work I owe you something huge, plus I would get my screen problem fixed
EDIT 2: would I be better off just deleting something that would just stop if from booting past the boot logo (big M) so it wouldn't be so obvious that I just killed it with is basically sayins so on the fastboot screen. If so what could I delete that wouldn't prove I had rooted, probably nothing now that I say that.

lkrasner said:
But my AT&T warranty is up?!?! will it still work? I still have my 1 year moto warranty.
Click to expand...
Click to collapse
That is the Moto warranty, AT&T will just help you "file" it since it is done through them anyhow.
Just don't call moto yourself.

jimbridgman said:
That is the Moto warranty, AT&T will just help you "file" it since it is done through them anyhow.
Just don't call moto yourself.
Click to expand...
Click to collapse
sweet, I will try that, what should I do to brick just erase system with fastboot? isn't that really obvious? or are all the employees just stupid. Obviously I need to do something recoverable so that i can get it back if it doesn't work.

lkrasner said:
sweet, I will try that, what should I do to brick just erase system with fastboot? isn't that really obvious? or are all the employees just stupid. Obviously I need to do something recoverable so that i can get it back if it doesn't work.
Click to expand...
Click to collapse
Do anything that will make it either boot loop or stick on the dual core/moto boot screen. Whacking system/boot should do that, and you can still flash it back to stock before you send it back if you really want to.... they are just going to fully refurb it and re-sell it...
The secret is to act dumb, pretend like you know nothing bout flashing and this site... just act like it just went nuts and started this, and it will not boot.
Ask for the advanced replacement.

jimbridgman said:
Do anything that will make it either boot loop or stick on the dual core/moto boot screen. Whacking system/boot should do that, and you can still flash it back to stock before you send it back if you really want to.... they are just going to fully refurb it and re-sell it...
Click to expand...
Click to collapse
OK, and they will not be able to see root then, and if they flash it back to stock it will no longer be rooted, so I should be fine. I opened a service request with Moto earlier, do you think that will be a problem? Should I wait until it expires so they don't get suspicious that I bricked it on purpose.

lkrasner said:
OK, and they will not be able to see root then, and if they flash it back to stock it will no longer be rooted, so I should be fine. I opened a service request with Moto earlier, do you think that will be a problem? Should I wait until it expires so they don't get suspicious that I bricked it on purpose.
Click to expand...
Click to collapse
if it is borked when you take it to the store they can't see that it is rooted cause it won't boot... all they are going to do it call their 1-800 number and help you file a support request... then the person the phone will let you know of the "requirements" and ask if the phone has any visible water damage, yadda yadda...
Then they will send you a new phone and you should get it in 3 or so days and you are supposed to send the old one back in the SAME box... so you will already have flashed the fxz and been using the phone the whole time you waited for the new one to show up... just don't forget to send it back... I did and waited until 25 days later, and I was bugged mercillessly by att...
Just make sure you factory wipe and take out your sim and SDcard, and battery door... they do not send anything but the core of the phone, no batt or batt door or anything.

lkrasner said:
OK, and they will not be able to see root then, and if they flash it back to stock it will no longer be rooted, so I should be fine. I opened a service request with Moto earlier, do you think that will be a problem? Should I wait until it expires so they don't get suspicious that I bricked it on purpose.
Click to expand...
Click to collapse
@jim on playing dumb,hilarious ..i do that when i upgrade my phone.im such an ass when i upgraded to a2 from xperia x10 that i didnt even bother restoring it to stock, i left cm7 on it,custom bootlogo ,said "free xperia team" on boot.i just pretended i didnt know what happend. it was so enjoyable.
service rep - "it appears to be rooted"
My response - "What do you mean rooted? It has roots like a plant?".
@krasner
You worry to much,they cant prove anything.just brick it and youll be fine.u could even play dumb as u crack a smile while doing so and they still really cant do anything to prove u did it and have to exchange it.
Sent from my MB865 using xda premium

worked beautifully! I deleted build.prop and default.prop, so it just went to a black screen after the moto logo. when the guy called the warranty center he said it was "extremely defective and clearly in need of replacement."
After I walked out, I went home, booted into bp tools, taking me to cwm and used adb to push the two files back. The phone already shipped.
However I am thinking of selling it BNIB and getting something else, any ideas what I could get for it

lkrasner said:
worked beautifully! I deleted build.prop and default.prop, so it just went to a black screen after the moto logo. when the guy called the warranty center he said it was "extremely defective and clearly in need of replacement."
After I walked out, I went home, booted into bp tools, taking me to cwm and used adb to push the two files back. The phone already shipped.
However I am thinking of selling it BNIB and getting something else, any ideas what I could get for it
Click to expand...
Click to collapse
Maybe 150. It wont be "NIB" you will not get a box, batt, back cover, etc. With the replacement.
Sent from my SAMSUNG-SGH-I747, running CM9, using xda premium