Atrix will not boot - Atrix 4G General

I am returning the Atrix back to factory so I did a factory reset from the phone, but it's not booting into the phone now. It stays stuck at the AT&T rethink possible logo.
Im pretty sure this was caused by the root. Anyway to get it to boot again?
Returning the phone back to AT&T, not liking the phone. I will never buy another AT&T branded phone.
EDIT: I forgot to unroot the phone, that's what caused it..

Anyone? 10-chars

so you rooted it incorrectly and blame it on ATT ?

You did un-root it didn't you?

lsxrx7 said:
so you rooted it incorrectly and blame it on ATT ?
Click to expand...
Click to collapse
He's not blaming it on att, he says he doesn't like the phone.
Sent from my LiquidLight using XDA App

royolpunk said:
He's not blaming it on att, he says he doesn't like the phone.
Click to expand...
Click to collapse
to me it sounds like he bricked the phone because he didnt root it right
and he didnt like the phone because its now a brick
shoot, i wouldnt like a brick either ....

I think there is a post in dev section listing possible key combinations for "extra" boot menu/options. Maybe one of them can help. I havent tried any of them so I can be sure. Try plugging it in to a wall for a while powered off. Maybe pull the battery and charge it for a few minutes and try again. I am having trouble getting mine to boot at all because the battery drained.
http://forum.xda-developers.com/showthread.php?t=961148
as for lsxrx7, if you dont have anything positive to say...

royolpunk said:
He's not blaming it on att, he says he doesn't like the phone.
Sent from my LiquidLight using XDA App
Click to expand...
Click to collapse
i "think" he just didn't read instructions right, bricked his phone, and now just doesnt like the phone, and hes done with ATT. that was my interpretation.

Yea. sounds like he rooted the phone and didn't un-root. Bricked the phone and now hates ATT because he has a brick.,

I am not blaming AT&T. I simply don't like the phone and forgot to unroot the phone before I did a factory reset. Now I hate it more that its bricked Maybe I should just bring it to a store and return it since they don't usually check to see if the phone is working.

lsxrx7 said:
to me it sounds like he bricked the phone because he didnt root it right
and he didnt like the phone because its now a brick
shoot, i wouldnt like a brick either ....
Click to expand...
Click to collapse
FYI. I rooted and it was working fine. Removed everything possible with root explorer. But still not liking the phone simply because of not having hsupa.

XeoNoX said:
i "think" he just didn't read instructions right, bricked his phone, and now just doesnt like the phone, and hes done with ATT. that was my interpretation.
Click to expand...
Click to collapse
How hard can 1 button root be? I just forgot to click the "un-root" button before I did a factory reset.....and now I have a brick... Just need to return it to stock so I can return it to AT&T.
I don't like the phone because it's crippled not only by Motorola, but also by AT&T....This is the reason why I'm never going to buy an AT&T branded phone again...

you must have done something else, because i did a factory reset without unrooting mine. and it's just fine.
I'm betting you screwed something up with this bit
ogxjason15 said:
Removed everything possible with root explorer.
Click to expand...
Click to collapse
edit: and this is the least crippled phone from AT&T yet. Just about everything was removable without root, which is unheard of on an AT&T phone.

cegna09 said:
you must have done something else, because i did a factory reset without unrooting mine. and it's just fine.
I'm betting you screwed something up with this bit
Click to expand...
Click to collapse
Could be....I didn't really delete them, but actually renamed them to *.bak.
I agree with you on the phone being the least crippled by AT&T......but crippling the HSUPA on a "4G" (HSPA+) phone? Really?

Did AT&T charge you for restocking fee? I'm tempted to get this phone but just want to be sure I can return it if I don't like the performance.

hammondhui said:
Did AT&T charge you for restocking fee? I'm tempted to get this phone but just want to be sure I can return it if I don't like the performance.
Click to expand...
Click to collapse
I didn't return it yet. Trying to fix it first. I think they charge you a $35 restocking fee.

I'm in the same boat as the op. Did you change the /system folder to r/w in root explorer? I think that may be the commonality.
Clueless as to how to unbrick this thing.
Edit: To clarify, I did not do a factory reset. I rooted yesterday and it was working fine, and then I rebooted it today and got stuck at rethink possible.

seanmac said:
I'm in the same boat as the op. Did you change the /system folder to r/w in root explorer? I think that may be the commonality.
Clueless as to how to unbrick this thing.
Edit: To clarify, I did not do a factory reset. I rooted yesterday and it was working fine, and then I rebooted it today and got stuck at rethink possible.
Click to expand...
Click to collapse
Yes. I did change the system/apps folder to r/w in order to rename/delete things that I want to get rid of. I might just ship it back this way :x

Phone returned. Case closed

I've done the same.

Related

Do not install second update!!!!

I first reported this morning that after the first OTA update, a second update became available and was downloaded by my phone. I did not install it because I was noit sure what it was...and I am glad I didn't! This update appears to BRICK phones, so beware of this second update and DON'T INSTALL IT!!!!
Brick rooted phones? Mines completely stock, will it be bricked? If it does get bricked can I get a new Evo?
Don't download an OTA update if your rooted. pretty simple. You won't download an update for a patched piece of software
Plancy said:
Brick rooted phones? Mines completely stock, will it be bricked? If it does get bricked can I get a new Evo?
Click to expand...
Click to collapse
shouldn't/won't brick it, if it does yes you can get a new one.
Nope, it doesn't brick stock phones.
Plancy said:
Brick rooted phones? Mines completely stock, will it be bricked? If it does get bricked can I get a new Evo?
Click to expand...
Click to collapse
Uhm, no. Because there are no Evos to be had, so you can brick your Evo all you want but you won't get a new Evo.
Update breaks root nowai
sent with my evo from a secret place
jasonleb1 said:
Uhm, no. Because there are no Evos to be had, so you can brick your Evo all you want but you won't get a new Evo.
Click to expand...
Click to collapse
OH yeah I forgot, I'd be without a phone for a while .
jasonleb1 said:
Uhm, no. Because there are no Evos to be had, so you can brick your Evo all you want but you won't get a new Evo.
Click to expand...
Click to collapse
Of course he will, as long as Sprint can confirm he didn't break his warranty. They'll give him a new one when their new shipment comes in. After all, it would be their fault and they would have to provide a replacement.
Second update? I did the ota update my evo works even better now! But I didn't get a second update
Sent from my PC36100 using XDA App
wortiz33 said:
Second update? I did the ota update my evo works even better now! But I didn't get a second update
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
A friend said something about seeing it when he re-searched for an update. Not sure if others are getting a prompt or what not after initial update.
Also bumping so it's nearer to the top.
Yeah, I'm not getting an option for a second update. Maybe it's only area based.
It's not a new update its the same one and if you reply yes your definitely gonna get a brick Sprint messed up lol bringing back the old Samsung instinct days lol
it would help alot if you shared the name of this update
vdub804 said:
it would help alot if you shared the name of this update
Click to expand...
Click to collapse
if you got the first one, install it, if you got a second one, don't. easy
what i did was uninstall all apps requiring su then uninstalled unrevoked and the restarted and shut off anything that didnt have to be running and updated...so far no problems short of having to reload a couple of widgets, i cant seem to get back to regular android launcher though
a friend of mine updated with unrevoked still installed and his phone made it through but it hung for about 20 min and i had to take the phone from him because he was ready to remove the battery, his sister had wifi running and after update it wouldnt start, my cousin turned off wifi before updating and his wifi seems fine...
Does anyone have a "bricked" phone? I'm curious as to whether it's a true brick or if recovery/bootloader can still be reached. As far as I can tell it's only rooted phones having these problems, I'm also wondering if people are pulling their batteries. Reports are saying that normal unrooted customers are saying their phones were "bricked", but I'm sure there's a lot of people that were rooted trying to get theirs replaced that aren't going to admit that they were rooted.
since someone in my inner-circle designated me as tech support i have a lot of people calling me, i just had a somewhat akward convo with a friend ending... root?? whats root, i dont even know what that **** is....*background* um dad..... yeah safe to say if you have an expensive phone and a competent kid with access and general knowledge of general electronics keep your phone away from them
JoshHart said:
Does anyone have a "bricked" phone? I'm curious as to whether it's a true brick or if recovery/bootloader can still be reached. As far as I can tell it's only rooted phones having these problems, I'm also wondering if people are pulling their batteries. Reports are saying that normal unrooted customers are saying their phones were "bricked", but I'm sure there's a lot of people that were rooted trying to get theirs replaced that aren't going to admit that they were rooted.
Click to expand...
Click to collapse
I have a normal, unrooted EVO 4G paperweight. Won't boot at all. Dead.
YUP same here, normal EVO, installed second update and BOOM, will not turn on, went to near sprint store and order new one at no cost, should be getting it tuesday or wed.

I swapped out my Vibrant for a new one and forgot to delete the file for root

I swapped out my Vibrant for a new one and forgot to delete the file for root. Is this a problem or will T-Mobile not even notice the file and just wipe the internal mem? I unrooted it before I sent it in but I forgot to delete the file.
Authorities have been notified..... probably on their way to your house now......
alecjake said:
I swapped out my Vibrant for a new one and forgot to delete the file for root. Is this a problem or will T-Mobile not even notice the file and just wipe the internal mem? I unrooted it before I sent it in but I forgot to delete the file.
Click to expand...
Click to collapse
Pack your bags, get on the first flight out of town.
Sent from my SGH-T959 using XDA App
Hahaha nice jokes.
Don't worry they don't check every phone infact they putthe phones on racks and a computer auto turns them to stock erasing everything
No worries
Sent from my SGH-T959 using XDA App
I bricked mine and sent it back to them with a custom rom and a i9000 kernel on it....no problem once its in good physical condition they wont give you any trouble
alecjake said:
I swapped out my Vibrant for a new one and forgot to delete the file for root. Is this a problem or will T-Mobile not even notice the file and just wipe the internal mem? I unrooted it before I sent it in but I forgot to delete the file.
Click to expand...
Click to collapse
Vibrant + Nero + OCLF
I hope you don't get charge cuz if they find out you will. Trust me I got a couple of friends working for Tmo.
I did the same thing OP, no big deal... I didn't get charged..
When I got mine I asked the sales person about rooting the phone. Keep in mind this is a salesperson and not T-Mobile corporate, but she really knew her stuff. She was the one everyone else in the store went to for help when they were not sure of the answer to a customer's question.
She said, if you have to return it just get it back to looking stock. Have the stock ROM on the phone and remove any obvious root or root required apps if they are still installed after you put the stock ROM on there. She said if it made me more comfortable I could remove busybox and su, but that nobody was going to go digging into the file system to see if the phone was rooted.
Basically they know, even if they don't officially acknowledge, that rooting the phone does not break it. If the phone is running stock firmware and it is still having issues then it is highly likely that the issue is hardware. Also, the preliminary acceptance or denial of the claim is done in store. If it makes it back to the factory it is pretty much accepted unless something really fishy pops up, like it is obvious you have been dissembling the device. They might kick it back if they find a FFC or soldering at the GPS antenna, but they are not looking for the su executive at that point.
They don't check the phones out that they get back they just restore them or whatever
lrobles787 said:
I hope you don't get charge cuz if they find out you will. Trust me I got a couple of friends working for Tmo.
Click to expand...
Click to collapse
Vibrant + Nero + OCLF
Yeah. Everyone is right. No worries. I ducked up a captivate on a30 day test drive with ATT, I took it back with stock ROM and even left superuser icon on there just hid it with launcher pro. Shouldn't have any problems. I didnt and believe they didn't wanna take that phone back on day 29.
Sent from my ADR6300 using XDA App
I've sent mine to samsung after i bricked it messing with roms, it was sent in with absolutely nothing original software wise.
didnt even get a warning. they flashed and sent it back A-ok

brick?

i was running fission rc1 on my d2g, used frm to download stock d2g deodexed blah blsh, flashed it, stuck on motorola m screen. cant get it to boot to bootstrap recovery for ****. only regular recovery...i could cry
edit: omg im gonna throw up. please tell me theres something i can do.
EDIT: ok...so if it is bricked and i have the $1.99 or $2.99 insurance, whatever....can i get it replaced...and if not, what if hypothetically speaking...it was smashed by a car...could i then get it replaced?
I am no expert, but lets try this, start the phone and as soon as the M appears, immediately pull the battery, and the put back in and start the phone. Lets see if the phone goes into ClockworkMod, and if it does, you can do a restore. Let me know how you make out.
MICP1480
no luck dude. thanks tho
EDIT: just got off the phone with verizon, theyre sending me a new one. wasnt hard at all, i played dumb and acted like bootloader mode was a whole new world to me, she had me wipe the data and reboot, of course i had already done that to no avail so of course it didnt work this time either, she put me on hold and talked to a tech and then came back and said they'd send out a new one.
botnryan said:
no luck dude. thanks tho
EDIT: just got off the phone with verizon, theyre sending me a new one. wasnt hard at all, i played dumb and acted like bootloader mode was a whole new world to me, she had me wipe the data and reboot, of course i had already done that to no avail so of course it didnt work this time either, she put me on hold and talked to a tech and then came back and said they'd send out a new one.
Click to expand...
Click to collapse
They will check your phone to make sure there is no ROM's and that it is not rooted as that voids the warranty.
This just means moto needs to release the sbf for the D2G so we can fix them instead of moto/verizon getting a bunch of returned devices.
Sent from my DROID2 using XDA App
miketoasty said:
They will check your phone to make sure there is no ROM's and that it is not rooted as that voids the warranty.
Click to expand...
Click to collapse
really? and how will they know if its all messed up and wont even boot? plus i did a data and cache wipe of the phone thru the regular recovery, will that not kinda wipe away anything incriminating? Not to mention the last rom i flashed was the stock d2g rom, just deodexed and such
When you flash a custom ROM or root the phone, evidences remain in /system which survives data wipe.
It is another question how would they see that if phone is not booting.
If you sent it in already and you do not receive a nasty 600 dollar invoice in the following days/billing cycle stating you have voided the warranty, then they really do not check.
I guess all they do is to flash the oh-so-desired-by-everyone stock SBF and sell it as refurb or give it as replacement phone.
leobg said:
When you flash a custom ROM or root the phone, evidences remain in /system which survives data wipe.
It is another question how would they see that if phone is not booting.
If you sent it in already and you do not receive a nasty 600 dollar invoice in the following days/billing cycle stating you have voided the warranty, then they really do not check.
I guess all they do is to flash the oh-so-desired-by-everyone stock SBF and sell it as refurb or give it as replacement phone.
Click to expand...
Click to collapse
i havent sent it in yet as ill be recieving the replacement tomorrow...any ideas on how to prevent this? could a good strong magnet wipe the memory completely?
botnryan said:
i havent sent it in yet as ill be recieving the replacement tomorrow...any ideas on how to prevent this? could a good strong magnet wipe the memory completely?
Click to expand...
Click to collapse
without the sbf to get back in there isn't really much you can do. The stuff is on there and you don't have a way to get back in.
try to get into recovery by:
pulling battery (or powering down phone)
while completely off plug in to wall via charging cable
turn on phone while connected to power (if you get the battery screen press power again)
you should hopefully be in recovery (not sure if this method works on D2 G but it does wonders for the D2 but it's worth a try.)
unless you really flashed crazy and messed up recovery theoretically bootstrap should be there unless completely wiped it.
newk8600 said:
without the sbf to get back in there isn't really much you can do. The stuff is on there and you don't have a way to get back in.
try to get into recovery by:
pulling battery (or powering down phone)
while completely off plug in to wall via charging cable
turn on phone while connected to power (if you get the battery screen press power again)
you should hopefully be in recovery (not sure if this method works on D2 G but it does wonders for the D2 but it's worth a try.)
unless you really flashed crazy and messed up recovery theoretically bootstrap should be there unless completely wiped it.
Click to expand...
Click to collapse
dude i tried that with both usb and wall charger, no luck either way, i flashed stock d2g deodexed blah blah rom over fission rc1 and this happend. totally blows my mind. got my replacement today, super glad to be back away from the eris lol
botnryan said:
dude i tried that with both usb and wall charger, no luck either way, i flashed stock d2g deodexed blah blah rom over fission rc1 and this happend. totally blows my mind. got my replacement today, super glad to be back away from the eris lol
Click to expand...
Click to collapse
Just checking I didn't see you tried that specifically glad you got your replacement now you know to be very careful as the sbf isn't out yet.
sorry if that last post came off harsh lol, didnt mean it to, read it again and was like geez dude chill (at myself). So im really hoping they dont charge my ass for this, but i dont see how theyre going to know. if you flash an sbf, does it unroot it? Because, if thats what they do to phones like mine, then they wont know i had it rooted/rom'd right?
botnryan said:
sorry if that last post came off harsh lol, didnt mean it to, read it again and was like geez dude chill (at myself). So im really hoping they dont charge my ass for this, but i dont see how theyre going to know. if you flash an sbf, does it unroot it? Because, if thats what they do to phones like mine, then they wont know i had it rooted/rom'd right?
Click to expand...
Click to collapse
Yeah SBF put's it back to stock from factory software. Unless they have another way of getting in and see what was in there they won't know much unless after they SBF they can pull the residual data in data or cache but I don't think they will go to that extent only if D2 G's start dropping like flies.
If they would just release the SBF for us we could have fixed your phone in 15 minutes and it wouldn't have cost them anything at all.
newk8600 said:
Yeah SBF put's it back to stock from factory software. Unless they have another way of getting in and see what was in there they won't know much unless after they SBF they can pull the residual data in data or cache but I don't think they will go to that extent only if D2 G's start dropping like flies.
If they would just release the SBF for us we could have fixed your phone in 15 minutes and it wouldn't have cost them anything at all.
Click to expand...
Click to collapse
alrights, thanks man. i feel they probably wont be able to find anything out but im still going to use up my 10 day period i have to send the phone in just in case the sbf is magically released in that time period.

did i brick my phone?

used unrevoked 3 to root my phone, did a backup, then attempted to install CM6. during the process, my phone shut off (i dont believe it was the battery, as it was fully charged and plugged in). now once in awhile (rarely) if i attempt to boot into recovery, the white htc evo screen will appear for a second or two, then the phone will shut back up.
what are my options?
i wouldn't expect anyone to reply with any real answers until you are more clear about your problems & what you've done already to try & fix them. not to mention, hardware specifics..
exempt said:
used unrevoked 3 to root my phone, did a backup, then attempted to install CM6. during the process, my phone shut off (i dont believe it was the battery, as it was fully charged and plugged in). now once in awhile (rarely) if i attempt to boot into recovery, the white htc evo screen will appear for a second or two, then the phone will shut back up.
what are my options?
Click to expand...
Click to collapse
Put this on your SD card. http://db.tt/uo4mOhh remove "_RA_2.2.1" and place on the root of your SD card. Once you get the "white screen" it will re install a recovery. Just make sure you go with it in bootloader (white screen) prompts.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!
drdrewdown said:
i wouldn't expect anyone to reply with any real answers until you are more clear about your problems & what you've done already to try & fix them. not to mention, hardware specifics..
Click to expand...
Click to collapse
Figured since this was the EVO forums it would be assumed I have an EVO
I havent attempted any solutions yet, as I wanted to be sure of something before trying. As for the problems, what is unclear? Rooted successfully, attempted to flash CM6 and phone went dead and no longer turns on.
So I should use something else to get it on the SD card, then try to start phone?
exempt said:
Figured since this was the EVO forums it would be assumed I have an EVO
Click to expand...
Click to collapse
Damn...I thought this post was for a BlackBerry Storm. But on a serious note, he was asking about what hardware version, hboot, etc... Hardware version 002? 003? 004? 007...wait, James Bond?
exempt said:
Figured since this was the EVO forums it would be assumed I have an EVO
I havent attempted any solutions yet, as I wanted to be sure of something before trying. As for the problems, what is unclear? Rooted successfully, attempted to flash CM6 and phone went dead and no longer turns on.
So I should use something else to get it on the SD card, then try to start phone?
Click to expand...
Click to collapse
Card reader or other phone.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!
tgruendler said:
Damn...I thought this post was for a BlackBerry Storm. But on a serious note, he was asking about what hardware version, hboot, etc... Hardware version 002? 003? 004? 007...wait, James Bond?
Click to expand...
Click to collapse
ah, that does make more sense. HW 003, HBOOT is 2.10
Rydah805 said:
Cars reader or other phone.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!
Click to expand...
Click to collapse
that fixed it! thank you!
exempt said:
that fixed it! thank you!
Click to expand...
Click to collapse
no problem. glad i could save your sanity and save you a trip to going to the sprint store then waiting an hour for diagnostics then getting a replacement when you really didn't need anything but a recovery re-flash. =]

Did I just Hard Brick my phone?

I've had my HTC 10 about a month. I was running NuSense Marshmallow by Santod040 and I had run the "NoRedText_aboot_firmware zip" to get rid ot the red text. Still, things were running well.
I then updated to the Nougat version of NuSense and the firmware and again things were running well. But the red text was back so I decided to get rid of the red text again. That is where things went wrong.
I didn't realize that there was a "new version" of the "NoRedText_aboot_firmware zip" and I tried to flash the same one.
I got an error message about it being the version prior to the update then the phone shut down. Now it wont power up.
Am I totally screwed? Is there a way to fix this? HELP... :crying:
Are you S-Off? Does your computer see it?
@dottat
acbrocksit said:
I've had my HTC 10 about a month. I was running NuSense Marshmallow by Santod040 and I had run the "NoRedText_aboot_firmware zip" to get rid ot the red text. Still, things were running well.
I then updated to the Nougat version of NuSense and the firmware and again things were running well. But the red text was back so I decided to get rid of the red text again. That is where things went wrong.
I didn't realize that there was a "new version" of the "NoRedText_aboot_firmware zip" and I tried to flash the same one.
I got an error message about it being the version prior to the update then the phone shut down. Now it wont power up.
Am I totally screwed? Is there a way to fix this? HELP... :crying:
Click to expand...
Click to collapse
Try charging with oem stock charger and cable overnight.
If it starts to take a charge, prepare a blank SDcard with
2PS6IMG_PERFUME_WL_M60_SENSE80GP_VZW_VERIZON_WWE_1.85.605.8_Radio_1.0.C010141xxxx.zip or similar. Rename it 2PS6IMG.zip with only one .zip at end. Try and boot with volume down and power.
With any luck, you'll get enough charge on it to allow you to do this software install.
Hard Brick
I did ask Santod and he said it is hard bricked. I flashed the wrong aboot image and now the phone does nothing, no power, no response from any combination of button presses, the computer does not see it. I don't know of anything else that might work.
I'm going to try to see if HTC can fix it, if not then I may use it for parts because the phone looks great. So I may try to get a beat up phone with a busted screen and swap out the guts.
Pretty sure this is what I've been talking about folks.
Stop messing with custom aboots.
Sent from my HTC6545LVW using Tapatalk
Bricked / aboot
dottat said:
Pretty sure this is what I've been talking about folks.
Stop messing with custom aboots.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Yeah, I read your info and warning about it after the fact.
acbrocksit said:
Yeah, I read your info and warning about it after the fact.
Click to expand...
Click to collapse
Yep...Moreso posting for anyone who sees this as further warning.
Sent from my HTC6545LVW using Tapatalk
I did the same thing trying to downgrade my firmware. Same exact thing happened. So I got it replaced by Verizon with the warranty, and they accepted it, I just said that I was trying to update it and that it won't turn on now. They haven't noticed that I did it, and I doubt they'll be able to get it to boot without flashing complete stock.
Spinkness said:
I did the same thing trying to downgrade my firmware. Same exact thing happened. So I got it replaced by Verizon with the warranty, and they accepted it, I just said that I was trying to update it and that it won't turn on now. They haven't noticed that I did it, and I doubt they'll be able to get it to boot without flashing complete stock.
Click to expand...
Click to collapse
So Verizon accepted your bricked phone? No issues?
Sent from my HTC6525LVW using Tapatalk
I sent mine to HTC to see what they would charge me (repair center in USA). I didn't say what happened, just that it wouldn't turn on. I don't think that they looked very close at it. They just sent me a refurbished phone, no charge.
But I won't mess with the red text again. It's really not worth the risk.
acbrocksit said:
I sent mine to HTC to see what they would charge me (repair center in USA). I didn't say what happened, just that it wouldn't turn on. I don't think that they looked very close at it. They just sent me a refurbished phone, no charge.
But I won't mess with the red text again. It's really not worth the risk.
Click to expand...
Click to collapse
They didn't even ask why Verizon wouldn't warranty it?
Sent from my m8wl using Tapatalk
Evocm7 said:
So Verizon accepted your bricked phone? No issues?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Sorry about the delayed response!!!
Yes they accepted it with no issues. Been a few months now and still nothing bad from them. The people at Verizon don't even have the knowledge to revive a hard bricked phone. At least not the people I've ever been able to speak to. But either way, it's not worth the hassle for them. They'll just part it, toss it, or send it back to HTC, where they will either part it or toss it. So yeah, no worries about sending Verizon a rooted/s-offed/bootloader unlocked phone. I've done it more times than I can count, and they've never found out.
Spinkness said:
Sorry about the delayed response!!!
Yes they accepted it with no issues. Been a few months now and still nothing bad from them. The people at Verizon don't even have the knowledge to revive a hard bricked phone. At least not the people I've ever been able to speak to. But either way, it's not worth the hassle for them. They'll just part it, toss it, or send it back to HTC, where they will either part it or toss it. So yeah, no worries about sending Verizon a rooted/s-offed/bootloader unlocked phone. I've done it more times than I can count, and they've never found out.
Click to expand...
Click to collapse
No problem. I called Verizon and even though it was dead, they were still able to communicate with the phone while I was talking to them on another phone. The power led was flashing red and then she said the phone wasn't under warranty because there was custom software. I ended up sending it to HTC where they sent me a refurb with a bad mic then the second one I have now is fine. So after a month and $40 worth of shipping charges, I have a working 10 again. I honestly don't think HTC cares about rooted phones and the time it would take to diagnose what actually happened in our down grade brick wouldn't be worth it for them.
Sent from my HTC6545LVW using Tapatalk
If it's under warranty, make a claim. Verizon will tell you to ship it back to another location where all they do is refurbish the phones for subsequent resale. You will likely get a replacement refurb. The refurbisher has absolutely no clue what you have done; they handle these things in bulk and I have not once ever heard of a phone under warranty being "refused" because an end user did something stupid. Which, as @dottat says, is what flashing an edited aboot to get rid of the red text is, by the way. Stupid.
I *like* the red-text, frankly. It reminds me whether I'm running pure stock boot and recovery or not while I'm flashing updates, etc.

Categories

Resources