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.
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 need help before I go to my last resort of taking my phone to Verizon to be replaced. I have rooted my droid 2 and was running and old version of fission 2.1 I think. Tried flashing the new version of fission after wiping data, cache, dalvik, battery status etc. I followed the directions perfectly and when it was done it was stuck on Moto logo. Tried a few things like pulling battery etc and decided I needed to resort to SBF. I have SBFed this phone before with no problems but this time I think I may have pulled the USB cable out at the very end of the SBF process without realizing it. The screen went black and no longer had the transferring info on it so I thought it was done. When I tried to boot it up the screen will flash on for a second or so with no text and then shut off. I tried holding the UP key while booting to get back to SBF again and the screen just shuts off...
Is there ANYTHING else I can try or might work before I take this back to verizon? I really dont want to resort to that and dont want them to think I have been rooted and deny me a new device... PLEASE HELP....
RammiKan said:
I need help before I go to my last resort of taking my phone to Verizon to be replaced. I have rooted my droid 2 and was running and old version of fission 2.1 I think. Tried flashing the new version of fission after wiping data, cache, dalvik, battery status etc. I followed the directions perfectly and when it was done it was stuck on Moto logo. Tried a few things like pulling battery etc and decided I needed to resort to SBF. I have SBFed this phone before with no problems but this time I think I may have pulled the USB cable out at the very end of the SBF process without realizing it. The screen went black and no longer had the transferring info on it so I thought it was done. When I tried to boot it up the screen will flash on for a second or so with no text and then shut off. I tried holding the UP key while booting to get back to SBF again and the screen just shuts off...
Is there ANYTHING else I can try or might work before I take this back to verizon? I really dont want to resort to that and dont want them to think I have been rooted and deny me a new device... PLEASE HELP....
Click to expand...
Click to collapse
Thats really bad, i think at the end SBF flashs the bootloader and the recovery modules and such. i cant think any other ways of recovering, if im wrong, someone please correct me
Ouch... never even heard of that happening. My D2 fell off my desk a few weeks back, while I was in the middle of an sbf, and it was fine afterwards. The sbf failed but I ran rsd lite again and it was good. Guess I got lucky.
Instead of going to the store, you can call to try and get a replacement. I called after the incident above, and told them my micro usb port wasn't working anymore. They overnighted me a replacement with no questions asked...
Sent from my DROID2 using Tapatalk
YOU DONE GOOFED.
No but seriously, this doesn't sound too good. Hopefully someone knows how to get you out of it. Good luck.
Hold down x+power on.
Sent from my Squidlied Droid 2 using Tapatalk Pro
What kind of backup are you running. Can you absolutely rule out a dead battery at this point, I don't know how long you've been messing with it. I've heard of some d2 users using charge only instead of pcmode. What mode were you in. What does it do when you plug it in to a wall charger. Sorry if this is redundant just trying to get a good feel for your problem and rule a few things out till maybe somebody more of a help than me comes along.
Sent from my Squidlied Droid 2 using Tapatalk Pro
lizard1 said:
What kind of backup are you running. Can you absolutely rule out a dead battery at this point, I don't know how long you've been messing with it. I've heard of some d2 users using charge only instead of pcmode. What mode were you in. What does it do when you plug it in to a wall charger. Sorry if this is redundant just trying to get a good feel for your problem and rule a few things out till maybe somebody more of a help than me comes along.
Sent from my Squidlied Droid 2 using Tapatalk Pro
Click to expand...
Click to collapse
You are a genius. My battery must have died in the middle of the SBF. I swapped out the battery with a charged one and it booted to the bootloader. The SBF said that it was corrupt but I plugged it back in and ran it again and it worked. Thanks for saving my droid!
Even a blind squirrel finds a nut every now and then!
Glad I could help out. Best of luck with the phone.
Sent from my Squidlied Droid 2 using Tapatalk Pro
all i did was install CM7 nightly 41 after a full wipe, all went well. then installed titanium backup, restored all apps, then went to recovery and installed gapps, powered back up, and it tried to sync and it froze up, so after a while i pulled battery and pow no power!!! uh oh? any ideas?
Does it light up when you charge it?
Sent from my HTC Desire Z/G2 Using XDA Premium App
nope. i think its a total brick.
when i plugged it into computer the computer did attempt to install software (bubble on lower right of screen near clock that pops up saying new hardware found) but failed to install properly
holy crap tmo takes up to 7 days for an exchange to be shipped!!!! wtf???
verizon gives free 2 day exchange via fedex. tmo does it for 20 bucks for 3-5 days!! unreal. im starting to hate tmo more and more
tackleberry said:
holy crap tmo takes up to 7 days for an exchange to be shipped!!!! wtf???
verizon gives free 2 day exchange via fedex. tmo does it for 20 bucks for 3-5 days!! unreal. im starting to hate tmo more and more
Click to expand...
Click to collapse
Yea.. I hate that too. It doesnt really take that long though. You should get it in 5 days the latest.
Sent from my HTC Desire Z/G2 Using XDA Premium App
yea i bought a nokia prepaid X2 as a spare so i can at least get email. my old spare isnt great its a nokia 6310i lol. it works great as a phone but nothing more.
according to ups ground, its 4 days from texas to me, so tuesday i should see my refurb crap again lol.
just irritating, they wanna charge 20 bucks for 3 day shipping....verizon charged 10 for overnight and free for 2 day. unreal. i just dont understand how it failed like that. i did nothing different when changing roms! my phone was running like crap after i wiped and installed virtuous sense on it, so i wiped again and flashed CM back on, and it just bugged the hell out! any idea why it would brick like that?
Holding power+volume down doesn't work?
This may sound silly. But have you tried a battery pull?
You seem kind of stupid, you supposedly brick your phone and before anyone can try to help you call tmobile and tell them to replace it, then complain about how long it takes them to replace your screw up.
Sent from my HTC Desire Z/G2 using XDA App
ionic7 said:
You seem kind of stupid, you supposedly brick your phone and before anyone can try to help you call tmobile and tell them to replace it, then complain about how long it takes them to replace your screw up.
Sent from my HTC Desire Z/G2 using XDA App
Click to expand...
Click to collapse
And in the process make the cell phones and rate plans cost more for everyone else cause yet another a-hole wants there warranty honored when they knowingly VOIDED the warranty. Getting so tired of this. Between people bypassing paying for tethering and OVERLY taking advantage, and bull**** like returning phones that you KNOWINGLY VOIDED THE WARRANTY WHEN YOU ROOTED AND INSTALLED THAT CUSTOM ROM on it, it is ZERO wonder why they all want to sign the god dam bootloader anymore. These may be evil corporations were dealing with, but there is still a difference between right and wrong. These few on xda will ultimately be our downfall. This thread is all kinda fail.
Edit: sorry for sounding so harsh but you could have waited for at least a LITTLE bit of help first. it sounds like something not that out of our league to have fixed.
Sent from my HTC Vision using XDA Premium App
Edit: double post. Everytime I go to edit on the new xda prem app I accidentally hit quote!
battery pull yes, vol down and pwr nothing. charged it overnight, and led didnt even power up, tried 2 different batteries, etc. nothing.
i dont know why it bricked, i did nothing different than what was done before to it. any time i ever did have problems was with the bootanimation screen would stay on and device would never boot, but i was still able to fix that with a full wipe and fresh reinstall. this was maybe a hardware failure of some sort? ive done all the same stuff to my mt4g (went from iced glacier to CM7, been on CM7 since nightly 6 or 8 with that one), and for a longer amount of time now and no issues at all. funny thing is i dont even flash nightly, or weekly...usually about 10-14 days ill flash an updated newer rom. now i know some of you people here are major fanatics about flashing nightly, changing radios constantly, kernels, amongst other things...i do half of that stuff and at probably a tenth of the rate that some of you hardcore folks do. so before you wanna pass judgement, i have been doing this same stuff since november on 3 different phones and never had a problem since yesterday at random. so i dont know why some of you get pissed when people have defective equipment. id guess if my hinge broke you would be telling me it was because of flashing roms too??? my rom was already flashed, working, and then when email was syncing it locked up, did a battery pull and nothing worked since. get a grip folks, crap happens. its not like i improperly flashed a non sense rom direct over a sense rom then back again with no wiping, clearing cache, data, etc etc etc then flash 3 incorrect kernels and bad themes and so on. if my device at least would power up, i wouldnt have decided to have it exchanged under warranty because i probably would have been able to fix it somehow since there are write ups about semi bricked devices. even plugging it into the computer does nothing now.
We have been looking into this issue on IRC for the past week or so. ANYONE WHO IS HAVING THIS ISSUE NEEDS TO STOP BY THE IRC CHANNEL.
We need to get some more info, right now we only have 2 cases to go on.
irc.freenode.net
#G2ROOT
tackleberry said:
battery pull yes, vol down and pwr nothing. charged it overnight, and led didnt even power up, tried 2 different batteries, etc. nothing.
i dont know why it bricked, i did nothing different than what was done before to it. any time i ever did have problems was with the bootanimation screen would stay on and device would never boot, but i was still able to fix that with a full wipe and fresh reinstall. this was maybe a hardware failure of some sort? ive done all the same stuff to my mt4g (went from iced glacier to CM7, been on CM7 since nightly 6 or 8 with that one), and for a longer amount of time now and no issues at all. funny thing is i dont even flash nightly, or weekly...usually about 10-14 days ill flash an updated newer rom. now i know some of you people here are major fanatics about flashing nightly, changing radios constantly, kernels, amongst other things...i do half of that stuff and at probably a tenth of the rate that some of you hardcore folks do. so before you wanna pass judgement, i have been doing this same stuff since november on 3 different phones and never had a problem since yesterday at random. so i dont know why some of you get pissed when people have defective equipment. id guess if my hinge broke you would be telling me it was because of flashing roms too??? my rom was already flashed, working, and then when email was syncing it locked up, did a battery pull and nothing worked since. get a grip folks, crap happens. its not like i improperly flashed a non sense rom direct over a sense rom then back again with no wiping, clearing cache, data, etc etc etc then flash 3 incorrect kernels and bad themes and so on. if my device at least would power up, i wouldnt have decided to have it exchanged under warranty because i probably would have been able to fix it somehow since there are write ups about semi bricked devices. even plugging it into the computer does nothing now.
Click to expand...
Click to collapse
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!
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.