Related
I know this has been asked before but i just want to be sure, i just got the xoom and i want to know if i can send it in for repairs. I just want to kno if its like the ipod's/phones where there is a physical feature that is broken, so i can relock and my warranty will be valid.
Moto doesn't care.
K thanks
Sent from my HTC Thunderbolt running Das BAMF v1.6.1 remix.
Elysian893 said:
Moto doesn't care.
Click to expand...
Click to collapse
Wait, what makes you say that? Do you know something we don't know? As far as I've heard, they've been very specific to say that they will not support devices that have been hacked.
slack04 said:
As far as I've heard, they've been very specific to say that they will not support devices that have been hacked.
Click to expand...
Click to collapse
... yet they sold us a Google-Experience device with an unlocked bootloader.
You can't break anything seriously with software, which means any potential problems we'd have are either physical, user-abuse, or hardware defects. If you send it in and they determine that the problem is SW, they'll probably just wipe it back to stock and send it to you.
Fact does remain, however, that when you unlock that device you have to acknowledge you are voiding your warranty if you proceed. I'd like to think they would be reasonable - but at the same time, you have agreed to kiss off your warranty when you unlock.
That is why I am hesitant to unlock, on all of my Android Phones I have rooted because I know there is no hardware function that can tell it has been "Hacked" like on the iPhone. The Xoom I am unsure about because nobody has a definitive answer yet. My Eris broke 3 times while rooted and I unrooted each time and sent it in for a exchange. I just want the above situation to be equivilent to when/if (Hopefully not) my xoom has a hardware failure.
Jiv3turk3y89 said:
That is why I am hesitant to unlock, on all of my Android Phones I have rooted because I know there is no hardware function that can tell it has been "Hacked" like on the iPhone. The Xoom I am unsure about because nobody has a definitive answer yet. My Eris broke 3 times while rooted and I unrooted each time and sent it in for a exchange. I just want the above situation to be equivilent to when/if (Hopefully not) my xoom has a hardware failure.
Click to expand...
Click to collapse
Moto has released their newest UPDATE for the xoom, on their website they included instructions and software to "RE-LOCK"/"UNROOT" your device before doing update. they dont care as long as you "relock"before sending the device to them to fix or reflash stock after you BUNKED a mod or etc...i dont recommend doing a theme flash, i did a few of them and had to go back to stock after every theme i tried, they did nothing but force close and i almost wasnt able to get back into CWM because the device wasnt recognized in adb...unlocking and rooting does nothing bad to your XOOM, best thing going for it, at least til there are some ROMS that couldnt get here any sooner...just a heads up
LNKNPRKFN said:
Moto has released their newest UPDATE for the xoom, on their website they included instructions and software to "RE-LOCK"/"UNROOT" your device before doing update. they dont care as long as you "relock"before sending the device to them to fix or reflash stock after you BUNKED a mod or etc...i dont recommend doing a theme flash, i did a few of them and had to go back to stock after every theme i tried, they did nothing but force close and i almost wasnt able to get back into CWM because the device wasnt recognized in adb...unlocking and rooting does nothing bad to your XOOM, best thing going for it, at least til there are some ROMS that couldnt get here any sooner...just a heads up
Click to expand...
Click to collapse
Thanks everyone! I think im going to unlock it when I get the chance, the SD card slot is a BIG thing that I could use, also I want it overclocked just a lil (1.25 Ghz per core) so it doesn't lag much on the home screen. Also im not going to be flashing roms and stuff mainly kernels. This device is going to be used as a family computer so i can't mess with it as much as I can with my Phone . Anyways thanks guys!
Ok, this might be a MEGA noobish question, but i have never dealt with Android before so please bare with me XD
I have just (yesterday) got my Atrix on tmobile in the uk, an would like to root it to use Aura ROM to get the 2.3.4 features and general improvements it seems to bring, but is there any reason to wait any length of time?
Its my understanding that Android is completely OpenSource, so is rooting it voiding any warranty, or is it OK with carriers? I ask since tmobile offers a 14 day period to make sure im happy with the phone, and that it all works fine, which it seems to after my extensive playing/testing over the last 2 days, but if it does go wrong i wouldnt want to take it in, rooted, and have them say they cant help me.
any clearing up of this would be much appreciated!
You should wait until the return period is over before rooting it. This will give you time to make sure nothing is physically wrong with it. Rooting alone will not void your warranty. However, unlocking the boot loader will and you need to do that to load a custom recovery so that you can flash another ROM. An unlocked message will get displayed on the start up screen. Some carriers may not pay much attention to that when returning it. Motorola will most likely notice if you need to use the manufacturers warranty though.
Root will void your warranty, wait till the trial period is over just to be safe...
Sent from my MB860 using xda premium
i got my phone from AT&T and rooted it as soon as i got home, a week later i ended up hard bricking my phone and went into the AT&T store and got it replaced for free. now, i did also pay for insurance on my phone so if anything happened to it (even if it's my fault) i'd get it replaced, but it seemed as if the representative had no clue what he was talking about. i was honest with them and everything and told him i was trying to unlock the phone when it happened, and he just kind of smiled and nodded and then pulled out a new phone out of the back. i asked how much i owed him, and he told me nothing.
point of the story is, i wouldn't worry about rooting the phone. it's possible that you won't be able to get it replaced, but chances are the rep you talk to either won't know what rooting is, or won't care. unlocking your bootloader though, i'd definitely wait a little while.
thanks, that is a good point though that people in the shop probably wont understand/care about rooting etc.
Though your reply, Alcapone, has confused me slightly i thought rooting and unlocking the bootloader were one and the same, but apparently not. could you please explain what is different, and is there any reason for me to root without unlocking the bootloader?
basically for now, since im on tmobile who seem quite slow at updating, i just want to get a way to put gingerbread on the phone. im ok with waiting 2 weeks for roms, but 2.3.4 i could do with now, if its possible, can that be done just by rooting?
many thanks
ishamm said:
thanks, that is a good point though that people in the shop probably wont understand/care about rooting etc.
Though your reply, Alcapone, has confused me slightly i thought rooting and unlocking the bootloader were one and the same, but apparently not. could you please explain what is different, and is there any reason for me to root without unlocking the bootloader?
basically for now, since im on tmobile who seem quite slow at updating, i just want to get a way to put gingerbread on the phone. im ok with waiting 2 weeks for roms, but 2.3.4 i could do with now, if its possible, can that be done just by rooting?
many thanks
Click to expand...
Click to collapse
rooting your device is just giving it root access, so apps can access parts of the system that they normally couldn't. rooting is extremely easily, and reversible. there are multiple ways to do it, i would suggest either the one click root for all gingerbread devices here
or the preinstall method here
now, unlocking the bootloader is a lot different. it pretty much enables you to install custom firmware onto your device. you can install a custom recovery that allows you to install amazing ROMs such as CM7, Aura, Ninja, Alien, Red Pill, Homebase, etc. etc.
i'm still assuming you're on gingerbread, so unlocking your bootloader is a panicky process. you'll get a fake hard brick (0x1000 error), but all you have to do is boot into fastboot mode and type the command 'fastboot oem unlock'. you can find a really awesome script that will do it all for you here
now, unlocking the bootloader voids the warranty. it gives you a bit of text on your boot logo (the motorola screen) that says 'unlocked' and allows your carrier to know you voided the warranty. it's also irreversible, once unlocked always unlocked. so make your decision wisely
nevermind, just skimmed over your post again. my apologies, i misread a few parts originally, you'll need to unlock your device to install a custom ROM with gingerbread. you can unlock your device by flashing the .sbf files you can find in this thread here: http://forum.xda-developers.com/showthread.php?t=1136261
thanks, so just to confirm, rooting alone wont allow me to update to 2.3.4? to be honest im not really to fussed about voiding warranty, it only lasts 2 weeks, and im away with no tmobile store even vaguely close for both of them plus i seem to be addicted to voiding the warranty on anything i buy by fiddling/overclocking asap, i cant help myself
i assume it is possible, if it does go wrong, to restore the phone to manufacturers settings and start again?
ishamm said:
thanks, so just to confirm, rooting alone wont allow me to update to 2.3.4? to be honest im not really to fussed about voiding warranty, it only lasts 2 weeks, and im away with no tmobile store even vaguely close for both of them plus i seem to be addicted to voiding the warranty on anything i buy by fiddling/overclocking asap, i cant help myself
i assume it is possible, if it does go wrong, to restore the phone to manufacturers settings and start again?
Click to expand...
Click to collapse
After you get the bootloader unlocked and cwm recovery installed going back to factory settings is as easy as installing a stock ROM. Which is pretty damn easy
And rooting alone isn't enough to get you gingerbread.
Sent from my MB860 using xda premium
awesome, thanks again. one last question (for now at least ) before i dive in, is this all possible on a mac, i noticed a lot of the rooters (if thats the right word?) are .exe which worried me slightly, im away from my windows machine for 2 weeks now. if not i guess thats as good a reason as any to not void my warranty for now XD
ishamm said:
awesome, thanks again. one last question (for now at least ) before i dive in, is this all possible on a mac, i noticed a lot of the rooters (if thats the right word?) are .exe which worried me slightly, im away from my windows machine for 2 weeks now. if not i guess thats as good a reason as any to not void my warranty for now XD
Click to expand...
Click to collapse
You can go to the ihop thread in the dev forum and use the Mac sbf flasher provided there. After that use the sbf that corresponds to your device. Flashing the wrong sbf can brick your device so maker sure you get the right one. Then boot into fastboot and use the fastboot OEM unlock command.
You can root as well on a Mac i'm sure, I just wouldn't know how. I'm guessing the preinstall method I linked would work.
Sent from my MB860 using xda premium
ishamm said:
Ok, this might be a MEGA noobish question, but i have never dealt with Android before so please bare with me XD
I have just (yesterday) got my Atrix on tmobile in the uk, an would like to root it to use Aura ROM to get the 2.3.4 features and general improvements it seems to bring, but is there any reason to wait any length of t
Its my understanding that Android is completely OpenSource, so is rooting it voiding any warranty, or is it OK with carriers? I ask since tmobile offers a 14 day period to make sure im happy with the phone, and that it all works fine, which it seems to after my extensive playing/testing over the last 2 days, but if it does go wrong i wouldnt want to take it in, rooted, and have them say they cant help me.
any clearing up of this would be much appreciated!
Click to expand...
Click to collapse
if you know how to root id do so. i already rooted, and also bricked my atrix. flashing the 4.2 sbf unbricked it and rerooted no problems so far, just the benefits of root (using apps that can only work with root permissions, flashing custom roms) also why flash Aura and run 2.3.4 when you can flash honeyatrix and run honeycomb 3.1?
rob219 said:
if you know how to root id do so. i already rooted, and also bricked my atrix. flashing the 4.2 sbf unbricked it and rerooted no problems so far, just the benefits of root (using apps that can only work with root permissions, flashing custom roms) also why flash Aura and run 2.3.4 when you can flash honeyatrix and run honeycomb 3.1?
Click to expand...
Click to collapse
Honey atrix isn't really honeycomb. It's gingerbread with a bunch of mods installed to make it resemble honeycomb
Sent from my MB860 using xda premium
Alcapone263 said:
Honey atrix isn't really honeycomb. It's gingerbread with a bunch of mods installed to make it resemble honeycomb
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
oh ok been running it along time so why does my android version say 3.1 and not 2.3?
rob219 said:
oh ok been running it along time so why does my android version say 3.1 and not 2.3?
Click to expand...
Click to collapse
It uses some files from honeycomb that edits the version number. It's still gingerbread, trust me.
Sent from my MB860 using xda premium
Alcapone263 said:
It uses some files from honeycomb that edits the version number. It's still gingerbread, trust me.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
i see well not gonna argue about it, just askin. still a great rom and very fast. i change alot of the look to my preference though. i may like the features and speed but im not a big honeycomb theme fan, i like my status bar white and such.
rob219 said:
i see well not gonna argue about it, just askin. still a great rom and very fast. i change alot of the look to my preference though. i may like the features and speed but im not a big honeycomb theme fan, i like my status bar white and such.
Click to expand...
Click to collapse
You should check out cm7. It's extremely customizable and really, really fast.
Sent from my MB860 using xda premium
Alcapone263 said:
You should check out cm7. It's extremely customizable and really, really fast.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
na not yet maybe after beta when everything works, kinda over cm now. new phone new roms hoping some new ones pop up here soon, but ill probly check out cm when its out of beta but most likely wont keep it as default.
after a bit of research it seems rooting on a mac is pretty tricky, since i dont have a vast ammount of terminal experience. is there a way i can forward some sort of app to the phone and root from the phone itself?
ishamm said:
thanks, so just to confirm, rooting alone wont allow me to update to 2.3.4? to be honest im not really to fussed about voiding warranty, it only lasts 2 weeks, and im away with no tmobile store even vaguely close for both of them plus i seem to be addicted to voiding the warranty on anything i buy by fiddling/overclocking asap, i cant help myself
i assume it is possible, if it does go wrong, to restore the phone to manufacturers settings and start again?
Click to expand...
Click to collapse
The 2 weeks is a return window with tmobile. Motorola, and most vendors, offer a one year manufacturer warranty. That is the warranty you void when unlocking the boot loader. Just wanted to clarify that bit.
ah thanks, i guess motorola WOULD notice its unlocked then. after some reading i think i'll use CM7, seems less likely to kill the phone, right?
the phone is insured, i guess it would be covered by that if i bricked it for good? if not i could take a hammer to it and claim it was a 'terrible accident' XD
I think my GPS is fubar... I've reinstalled my custom rom and from fresh the GPS is still having problems locking to satellites. It sees them, but can't lock for a long time, then it only locks 4/5 my xoom and my gf's atrix gets to lock on within seconds and 9/10 and i'll be at 4/9
sooo, I'm gonna put a stock ROM on and see what happens... if still problems, I want to take it back and have them try to replace it or something...
but here is the problem. it's unlocked boot, and also got CWM and stuff...
how can I bring the phone back to it's factory setting? just like how I got it from AT&T...
I want to see if I can have AT&T just replace it with warranty or something...
Before you get into any of that, here's a fix that worked for me. I was experiencing the same problem, until about a week ago when I tried this:
Go to settings --> Location and security --> uncheck "Use Wireless Networks".
Now, just turn on GPS like normal and see if it locks.
My guess is that the phone should override using wireless networks while locking on GPS, but it doesn't.
Sent from my MB860 using XDA App
razorseal said:
how can I bring the phone back to it's factory setting? just like how I got it from AT&T...
I want to see if I can have AT&T just replace it with warranty or something...
Click to expand...
Click to collapse
You can flash the stock gingerbread SBF and you'll be 100% back to stock. I've done this on two different phones (coming from cm7) and was able to warranty. You'll only hard brick if you flash a froyo SBF once you've upgraded to gingerbread. Gingerbread to gingerbread is OK.
I have the same issue and I just started the warranty exchange process (second time, first time was due to the phone rebooting constantly). I tried all sorts of things to troubleshoot - wifi on/off, removing battery for 15 minutes, running GPS utility apps, etc. Nothing worked - the GPS does not provide a fix.
henrys01 said:
You can flash the stock gingerbread SBF and you'll be 100% back to stock. I've done this on two different phones (coming from cm7) and was able to warranty. You'll only hard brick if you flash a froyo SBF once you've upgraded to gingerbread. Gingerbread to gingerbread is OK.
Click to expand...
Click to collapse
Even if it is unlocked? I'm afraid they might see the "unlocked" message on boot and reject my warranty. I have muffled sound issue so I need to do an exchange.
bleuiko said:
Even if it is unlocked? I'm afraid they might see the "unlocked" message on boot and reject my warranty. I have muffled sound issue so I need to do an exchange.
Click to expand...
Click to collapse
The unlocked text will be gone
henrys01 said:
You can flash the stock gingerbread SBF and you'll be 100% back to stock. I've done this on two different phones (coming from cm7) and was able to warranty. You'll only hard brick if you flash a froyo SBF once you've upgraded to gingerbread. Gingerbread to gingerbread is OK.
Click to expand...
Click to collapse
After all sorts of Magic, it still wont work.
Is there an sbf file you can link me to?
iirc its done via RSD
If anything ill do it and see how the gps acts.
I do have an sbf file but honestly i dont know if its ginger or froyo, so imdont wanna risk it. Lol
my GPS takes forever to lock now when it used to only take a few seconds.
But after a few minutes it locks on. still though..annoying. Ive gone back to using my old garmin
Thank you for your kind comment. Lol
But does anyone have link to gb sbf? And i think I need radio along with it?
Sent from my Xoom using Tapatalk
If you have to send it in, I don't think they care about it unless it is liquid or physical damage. I've sent in two unlocked and rooted phones no prob. Even told them I had done it to make sure that I didn't get the replacement charge.
Would they give me a replacement at att store? I assume not. They probably do t have them anyways...
There is no way I'm paying that deductible either far as I know rooting does void the warranty so...
Sent from my Xoom using Tapatalk
henrys01 said:
You can flash the stock gingerbread SBF and you'll be 100% back to stock. I've done this on two different phones (coming from cm7) and was able to warranty. You'll only hard brick if you flash a froyo SBF once you've upgraded to gingerbread. Gingerbread to gingerbread is OK.
Click to expand...
Click to collapse
I just SBF'd a 2.3.4 and now i'm stuck on boot loop... it goes to ATT logo and then resets to the moto one...
crap.
No. They have to send it out, and they send out a refurbished phone, but at least it works. Just call and try it. They never charged me any fee. They told me all that they we're concerned about was liquid and physical damage. Just tell them up front. You might be surprised.
chrism.brunner said:
No. They have to send it out, and they send out a refurbished phone, but at least it works. Just call and try it. They never charged me any fee. They told me all that they we're concerned about was liquid and physical damage. Just tell them up front. You might be surprised.
Click to expand...
Click to collapse
So there is a DSC in certain areas (Device Support Center) and what they do is, if they can't fix your phone on the spot, they give you a new one. which is what they did for me.
sweet!
Will google know if i rooted my phone? or unlocked bootloader. I was think of rooting it but then again i dont want to lose the warranty on it.
teddytales66 said:
Will google know if i rooted my phone? or unlocked bootloader. I was think of rooting it but then again i dont want to lose the warranty on it.
Click to expand...
Click to collapse
If you unroot it, I don't think they would know. But as in Google, I'm assuming that's the manufacturer because Google doesn't process warranties, it's the manufacturer, even if you have a nexus.
Sent from my Nexus 7 using Tapatalk HD
teddytales66 said:
Will google know if i rooted my phone? or unlocked bootloader. I was think of rooting it but then again i dont want to lose the warranty on it.
Click to expand...
Click to collapse
You can always unroot, but, to be honest, I don't think it matters, a lot of urban legend when it comes to rooting. I mean, the nexus 4 is a developer phone, what would a developer do with an unrooted phone with a locked bootloader? Root it, wipe it then flash it!
Sent from my Nexus 4 using xda app-developers app
Google won't know you're rooted until you send your device back for to them for repairs in case of a broken phone.
So, let's say you want to have the screen replaced. Before you RMA your unit, it's wise to lock the bootloader again and un-root your phone. THIS thread provides all the instructions for that. Even if your screen is broken, you can still return to a locked bootloader and an unrooted phone. For a little more information about this all, you could also search the forums for something along the lines of "RMA bootloader unroot". I'm sure there are other people who have wanted to return to stock before returning their devices.
So Google won't know unless you send the device to them. So if you're ever sending it back, don't forget to lock the bootloader, and unroot your device.
Yup, you can always unroot. BUT, if Google really wanted to it could figure out what phones are rooted and what phones aren't. Think about when you go into the Wallet app with a rooted device. The app knows and tells you it is unsupported. I really don't think they care that much though..
Not unless you put a billboard sign up near Google's headquarters!
At some point (I don't know if this is still the case) Google didn't allow rooted phones to upload photospheres to GMaps as they could fake their location and essentially end up doing something like placing the Colosseum in the middle of New York. It's not difficult for them to figure out which devices are rooted and block them for certain things but in most cases it won't make a difference.
Nope as long as you unroot, return to stock and lock the bootloader, they will not know.
Sent from my Nexus 4 running the latest PA ROM 3+ and Franco's M1 kernel
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.