I've had it rooted, and flashed many roms to it.. then tonight it all went to sh!t.
I was trying to put a froyo rom onto it(i think it was called extreme froyo), and i got the boot loops, and on the download page it said i needed the newest radio/spl if that happened...
So i ended up flashing some sapphire SPL, and it got stuck on the "HTC MAGIC" bootscreen.... then I tried flashing this:
http://code.google.com/p/android-roms/downloads/detail?name=splhard1_update_signed.zip&can=2&q=
and now it wont even power....
Is it done for?
Yeah u need to be careful, flashing new radios and spls are very dangerous and best flashed from fast boot. Sorry but you sir are ****ed
Sent from my HTC Magic using XDA App
****in ****.. thats lame, and Tmobile is saying they won't warranty it.. ridiculous.
Ridiculous they won't warranty a phone you bricked? Sounds just fine to me...all the rooting stuff does say it voids the warranty...
Yea, but if you cant tell, then whats the big deal. it just doesn't turn on.
th1rt3en said:
Yea, but if you cant tell, then whats the big deal. it just doesn't turn on.
Click to expand...
Click to collapse
tell them u reccieved an ota update and when it finished it wouldnt work
That's what you get for not reading up about something which could harm your phone. I don't mean to add insult to ingury, but chances are you didn't even need HardSPL.
It if you can't get into Fastboot or anything, you're screwed. But you shouldn't be flashing new radios or SPLs if you don't know if they are compatible with your phone.
There has been no OTA updates for the fender/mytouch 1.2. They won't believe that line...
NetrixTardis said:
There has been no OTA updates for the fender/mytouch 1.2. They won't believe that line...
Click to expand...
Click to collapse
First you go about it very dumb like..... and then you start by saying that you was out and phone was all most dead. by the time you got home it was turned [email protected]@h...........new phone. But by no-means do i support this action nore do I believe in any act of theft by deception!!! This can get you in trouble big time.
First of all, if you're going to flash a rom that clearly states that you need the newest radio and SPL, you want to update those BEFORE you flash the rom. More than likely, that's what caused your boot loop. Second, do a little research before you start flashing things, if you had, you would know that you always update your radio before your SPL. That's where you went wrong, and that's what bricked your phone. Of course T-mobile isn't going to replace a phone that you bricked. Rooting your phone voids the warranty and a bricked device is definitely no exception.
Do you have insurance on your phone? You're better off taking it outside, running it over with you car and making an insurance claim. Problem solved.
this thread was for help.. not for everyone to chime in about whether its ethically right for me to try and warranty.
If its helpful to me trying to get this thing going again, post, if not, just go to the next thread.
Ethically speaking, I personally could care less if you CAN actually get your phone replaced under warranty. If you can, do it! As far as getting your bricked phone up and running again, its not going to happen. Like I said, you obviously flashed the SPL before updating the radio which bricked your phone, there's no turning back. So basically, you have three options.
1. Don't replace your phone and use it as a nice paper weight.
2. Lie your ass off to T-Mobile and get your phone replaced under warranty and cross your fingers they don't find out and tack additional charges to your account for voiding your warranty. Who cares about ethics or what anyone else says, its your call. Honestly, as long as your hardware is ok, they can reflash your device and will end up reselling your phone to someone else, so who cares.
3. If you have insurance, smash you phone, drop it in the toilet, throw it at the wall, anything. That's what insurance is for, of course then you're still stuck with pay some cash.
Related
I was attempting to flash 2.x using behnaam and lox's rom.
Rom: http://forum.xda-developers.com/showthread.php?t=592596
Here is the HBoot info previous to my tinkering:
HERC XC
HBOOT-1.41.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-1.04.01.09.21
SEP 1 2009,19:18:45
Phone is rooted using adb.
I used unlockr's guide to flash a custom recovery image onto my CDMA hero and that worked fine, here is the guide I followed:
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
I first moved the radio recommended for the rom by the dev to root on the sd and renamed it update.zip. After, I used the recovery image to wipe, then apply update.zip from sdcard. It seemed to flash fine, as it said please select reboot to complete, which I did, and it completed and rebooted the phone.
Once rebooted it gave me the android installing software image without anything else for a while, then turned off. I cannot seem to awaken my phone with any combo of keys or by plugging it into its use cable. The charging led doesn't even light up anymore.
Well I seem at the moment to be SOL, unless someone can come by and throw me a bone. I really am at a loss as to what I did wrong, as I have always read to do radio first. Not to mention as I watched it install radio it said it was installing radio.
Thanks for the help everyone.
You attempted to flash a GSM ROM to your CDMA phone, this is why your phone is bricked. I'm not sure if its possible to recover, people with more experience than I have can help you there. The problem was flashing a GSM ROM to CDMA. You are not the first to have done it, we all mess up from time to time.
Uuuh Umm...that software was for the GSM hero's NOT THE CDMA Hero.............bless your heart.
Ah **** I thought it was CDMA, guess it was a bad idea jumping into roms while still a noob.
Yea I only got the radio installed, not the rom, although that probably doesn't make a difference.
I don't think the phone can be recovered once you attempt to flash the Radio, but I could be wrong.
Hmm well if worst comes to worst I'm going with what I read on another thread and saying that I was installing the update that it found when I went to phone details and halfway through the update the phone just turned off and won't turn on anymore.
According to the other thread once it is bricked beyond belief and you play stupid they can't prove you wrong.
Best case scenario they replace it, and I won't feel bad seeing as it was a defective phone that is allowing dust to enter under the screen. But that who ordeal is an entirely different rant...lol
Sigh
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
Go......Now......Move with haste...
gu1dry said:
I don't think the phone can be recovered once you attempt to flash the Radio, but I could be wrong.
Click to expand...
Click to collapse
Yea, you're right. Flashing a GSM rom on the CDMA won't really break much. It's flashing the radio that bricked it.
flipzmode said:
Yea, you're right. Flashing a GSM rom on the CDMA won't really break much. It's flashing the radio that bricked it.
Click to expand...
Click to collapse
All is lost!!!!
Yep RUU brought back Error 170 cannot connect to phone.
Maybe the sprint repair stores will not be so asshole-esque this time around.
I'm hopeful though, as I have read a few posts about them exchanging it for a new one. Which after a bunch of calls I had hoped to have happen due to the dust thing, but oh well.
Maybe I will get lucky and my brick will actually turn out to be a phoenix in disguise.
unfortunately, flashing the GSM radio on pretty much destroys the phone.
i think its got something to do with the voltage and electricity used by the GSM radios. probably higher than what the CDMA radios use, so you didn't really brick your phone, you 'fried' it in a sense.
sorry bout that... but if you have the equipment protection plan you can probably get it replaced real easily, since the sprint people probably won't really understand what's wrong.
again I am reminded why I dont screw with radios
willowmp said:
Yep RUU brought back Error 170 cannot connect to phone.
Maybe the sprint repair stores will not be so asshole-esque this time around.
I'm hopeful though, as I have read a few posts about them exchanging it for a new one. Which after a bunch of calls I had hoped to have happen due to the dust thing, but oh well.
Maybe I will get lucky and my brick will actually turn out to be a phoenix in disguise.
Click to expand...
Click to collapse
Once you do get it replaced and you want to put a custom ROM on it, look at the first page of this forum and you'll find sticky threads regarding four different ROMs you can put on your phone (two production release and two experimental betas).
I would suggest either MoDaCo's rom or Fresh rom. I use Fresh in mine and had no problems (although I have used MoDaCo's before and also had no issues).
Also, if you want to root the phone, there are also sticky threads that will tell you how to root your phone from Windows, Mac and Ubuntu.
Good luck.
Yep thanks everyone.
Yea I figured once no buttons would do anything and the leds wouldn't even light up for charging that it was pretty much fried. Definitely got that sinking feeling in the pit of my stomach.
I definitely should have come into this section specific to my phone and read this info instead of just doing tons of searches and getting mixed up.
Although I'm hesitant on flashing to a replacement phone if I get one, I think I will but this time make a post just to verify without a doubt. I'm sure many wouldn't mind a simple post asking if this will blow up my phone or not, lol.
Once again thought, thanks for the help. Especially to a noob that made a real noob mistake lol.
Edit: All is well, I contacted sprint chat and they confirmed I will be receiving a brand new phone when I arrive at a sprint store, and with the chat log sent to my email and printed out the repair stores cannot pull any of their gimmicks on me, they are getting a command from sprint HQ after all. This is nice, I kill my phone and I get a brand new one without dust, and this time the invisible shield goes on asap.
willowmp said:
Although I'm hesitant on flashing to a replacement phone if I get one, I think I will but this time make a post just to verify without a doubt. I'm sure many wouldn't mind a simple post asking if this will blow up my phone or not, lol.
Click to expand...
Click to collapse
Well once you are retry the flashing on your new phone, just msg me & I'll give you my contact info & I'll walk you thru it.
willowmp said:
Edit: All is well, I contacted sprint chat and they confirmed I will be receiving a brand new phone when I arrive at a sprint store, and with the chat log sent to my email and printed out the repair stores cannot pull any of their gimmicks on me, they are getting a command from sprint HQ after all. This is nice, I kill my phone and I get a brand new one without dust, and this time the invisible shield goes on asap.
Click to expand...
Click to collapse
while the attempted flash was boneheaded , this (what I quoted) was very smart. I've had them try to reverse the decision and noted on my account in the past. All ended well, but a hard copy of the convo between me and Corporate would have been nice to have.
props for a good idea.
if you don't want trouble with rooting and flashing new ROMs to your phone, try flipz's pre-kitchen. just to try it, i RUU'd my phone and re-rooted it through that app, and its simply amazing. you just sit back and watch, don't even have to do anything.
Ok so its pretty funny but whoever it was who says that once you flash for the first time its addictive, I do have to agree. I will be getting my phone tomorrow because they had to replace it and I will be flashing, although this time I will play it safe and triple check before I get click happy...lol
So what are the danger zones in flashing, like what can brick or kill your phone? I know playing with radios can kill it if the wrong one is flashed, and I know powering off or interrupting a flash will kill/brick, but what else.
I know people said firmware alone usually will not brick you.
willowmp said:
So what are the danger zones in flashing, like what can brick or kill your phone?
Click to expand...
Click to collapse
Well obviously it can brick your phone if you flash the Radio I kid, I kid
willowmp said:
I know playing with radios can kill it if the wrong one is flashed
Click to expand...
Click to collapse
With the CDMA Hero, you do not have to flash the Radio. So if your attempting to flash the Radio, you're doing it wrong.
willowmp said:
I know powering off or interrupting a flash will kill/brick, but what else.
Click to expand...
Click to collapse
Well if the custom recovery is installed (RA-heroc), if the phone looses power while flashing the firmware, you are usually still safe, because you (usually) still boot into the recovery without issues.
Like I already said, if you want I can walk you thru the entire process thru an IM client, Steam, or Skype.
Oh ok thanks, I'm actually headed up to PA for a little trip but definitely will hit you up on that offer when I get back.
i flashed a radio from the tmo hd2 radio thread. but it's an older radio (2.05.50.11) i' ve tried like 5 different radios and the oldest one (Leo RADIO 2.07.50.27_2) seemed to work the best so i tried Leo RADIO 2.05.50.11 to see if i can get better results but it didn't boot back up. anyone with any ideas?
yut916 said:
i flashed a radio from the tmo hd2 radio thread. but it's an older radio (2.05.50.11) i' ve tried like 5 different radios and the oldest one (Leo RADIO 2.07.50.27_2) seemed to work the best so i tried Leo RADIO 2.05.50.11 to see if i can get better results but it didn't boot back up. anyone with any ideas?
Click to expand...
Click to collapse
Ouch. I'm still new around but if I remember correctly, 2.07 is the lowest version of Radio you can flash in your 1024 Leo (although most people you recommend that you run 2.08 and above instead). You should have read this thread as many times as you needed to understand everything because making a mistake will cost you a lot of time, trouble and money. I can only hope that T-Mobile will let you get a new one by making some excuse like "It failed to update and look what I got!".
actually i tried 2.06 and it was fine which is why i decided to try 2.05
yut916 said:
actually i tried 2.06 and it was fine which is why i decided to try 2.05
Click to expand...
Click to collapse
Sounds like you wanted to brick it. They say 2.07 is the safest and anything below that is risking you brick your phone. Your out of luck. If you have HSPL i wouldn't go in for a warranty exchange as they will possibly see it once upon recieving it. So better hope you have insurance.
rlacsamana1989 said:
Sounds like you wanted to brick it. They say 2.07 is the safest and anything below that is risking you brick your phone. Your out of luck. If you have HSPL i wouldn't go in for a warranty exchange as they will possibly see it once upon recieving it. So better hope you have insurance.
Click to expand...
Click to collapse
yea i do have insurance. i guess i was just pushing my luck. having super slow and inconsistent data speeds kinda forced me to do it. was hoping for a miracle but oh well.
yut916 said:
yea i do have insurance. i guess i was just pushing my luck. having super slow and inconsistent data speeds kinda forced me to do it. was hoping for a miracle but oh well.
Click to expand...
Click to collapse
Yeah just call up insruance or go online and sumbit a claim. Just say it is broken on the claim. Most people will say to say you lost it but most people don't understand that insurance is not the same thing as warranty as they will replace it even if you tampered with it.
Sorry to hear but yeah if others were reporting the same thing as you were it prob wasn't the best idea? TMOUS HD2 is so much easier to brick than the International HD2.
rlacsamana1989 said:
Yeah just call up insruance or go online and sumbit a claim. Just say it is broken on the claim. Most people will say to say you lost it but most people don't understand that insurance is not the same thing as warranty as they will replace it even if you tampered with it.
Sorry to hear but yeah if others were reporting the same thing as you were it prob wasn't the best idea? TMOUS HD2 is so much easier to brick than the International HD2.
Click to expand...
Click to collapse
but i have hspl and a custom rom on there. is there any way they can check that and deny my warranty and or insurance claim?
Probably not, but just in case I'd say it was lost...if it were me that is.
Sorry to hear its dead, but i must say its very strange that a tmous radio killed a tmous.
It certainly changes the ideas as to why radios kill tmous phones. We assumed it was because the 51 radios couldn't access the extended rom/ram, however this was a 50 radio, from a tmous rom, so it should be able to see the rom/ram fine.
No explanation, very strange. I'd be almost inclined to think someone packed a 51 radio into a 50 filename.
Dont file an insurance claim, thats a horrible idea. Call tmobiles customer care and tell them your phone wont boot up. They will send you a replacement phone and you send the broken one back. Its doubtful they will check it but if they do and charge you its only $110 instead of the $130 through insurance.
Edit: Are you able to boot into the bootloader or will the phone not turn on at all? If you can boot into the bootloader then its not bricked.
I havent flashed my hd2 after reading all the people briking their phones.
josemedina1983 said:
I havent flashed my hd2 after reading all the people briking their phones.
Click to expand...
Click to collapse
You shouldn't have to worry about trusted and tested ROMs/Radios. Unless you do something horribly wrong, you'll be fine. It's when you experiment with stuff that you get into trouble. Just tread the beaten path and you'll be fine
Flashing your phone is like skydiving; it's fun, it can be completely safe, but there will always be some risk (especially for the inexperienced).
speoples20 said:
Dont file an insurance claim, thats a horrible idea. Call tmobiles customer care and tell them your phone wont boot up. They will send you a replacement phone and you send the broken one back. Its doubtful they will check it but if they do and charge you its only $110 instead of the $130 through insurance.
Edit: Are you able to boot into the bootloader or will the phone not turn on at all? If you can boot into the bootloader then its not bricked.
Click to expand...
Click to collapse
nope. won't turn on at all. after flashing it turned off but never booted back on.
joe_coolish said:
You shouldn't have to worry about trusted and tested ROMs/Radios. Unless you do something horribly wrong, you'll be fine. It's when you experiment with stuff that you get into trouble. Just tread the beaten path and you'll be fine
Flashing your phone is like skydiving; it's fun, it can be completely safe, but there will always be some risk (especially for the inexperienced).
Click to expand...
Click to collapse
How do i know what Hardspl am i running I cant seem to find it
josemedina1983 said:
How do i know what Hardspl am i running I cant seem to find it
Click to expand...
Click to collapse
boot into bootloader, and there is a line that starts 'spl '.
The number following that is your spl.
If it ends .0000 then it is stock. Example 2.08.0000 or 2.10.0000
If it ends .hspl then it is hspl. It will also say cotulla on screen too. Example 2.08.hspl
samsamuel said:
boot into bootloader, and there is a line that starts 'spl '.
The number following that is your spl.
If it ends .0000 then it is stock. Example 2.08.0000 or 2.10.0000
If it ends .hspl then it is hspl. It will also say cotulla on screen too. Example 2.08.hspl
Click to expand...
Click to collapse
LOL one step can take me a long way so i have 2.10.000 so finally i can install a rom that was the only thing holding me back thanks.
josemedina1983 said:
LOL one step can take me a long way so i have 2.10.000 so finally i can install a rom that was the only thing holding me back thanks.
Click to expand...
Click to collapse
with spl 2.10.0000 you need to use hspl3 See my sig, connect phone, run hspl3, choose 2.08.hspl, done.
samsamuel said:
with spl 2.10.0000 you need to use hspl3 See my sig, connect phone, run hspl3, choose 2.08.hspl, done.
Click to expand...
Click to collapse
awsome that was my only problem seen so many hspl it got me alittle confused now im about flash a new rom thanks alot you made my monday
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.
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!
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.