Related
Just as title says. Ive tried all the fixes for it with no luck.
I dont really care for the trackball anyway, but I cant load roms without being able to scroll down.
Any suggestions xda community.
i had that problem like a week ago,didnt find any answers, i went to verizon and told them my trackball wasnt working and they were going to try and make me pay for another under my warranty,i told them that I read on many forums that it was a hardware issue and after they researched it they exchanged my phone for free.thats the only thing i can tell you to do. hopefully they can do it for you also.
It's the infamous trackball issue. I had ignored it until my came down with it a few months ago, it was around 6 months old. I called Verizon and got a replacement phone, they shouldn't charge you for anything. I couldn't see any other way around it, since I too am a rooted user. Good Luck!
i agree. its a known crappy trackball issue. call verizon and they should sent a replacement. there was an ruu that was an exe ran from your computer that should (someone correct me if i'm wrong) allow you to go back to stock on your eris if you are worried about the verizon people asking about your root. it was posted here, but i just looked and couldn't find it. trying to reup now. will edit this post with a link.
uploaded file http://www.multiupload.com/0B4EAQE25I fyi i'm not responsible if you brick your phone blah blah blah. i actually had nothing to do with writing the file, i just couldn't find it so i reposted it. it is an exe to run on a windows based computer with your eris attached via usb.
gthirty6ptime said:
Just as title says. Ive tried all the fixes for it with no luck.
I dont really care for the trackball anyway, but I cant load roms without being able to scroll down.
Any suggestions xda community.
Click to expand...
Click to collapse
Here is a brutal hack from the Eris Root forum on AF.
I works, but you need to use adb from a PC, and be comfortable working at the command line.
bftb0
I actually sent my phone rooted with KaosFroyo on it and Verizon didn't say anything! I've heard of a handful of people that have done the same.
People have sent it back no problems, but if you're worried run the RUU.
I've recently rooted and had some issues with my personal phone, which I've cleared up with help from this board and members, and have actually enjoyed messing with my phone, its been fun learning about android and the possibilities with these phones. But with a bit of hesitation on going at it again with my phone, and how screwed I was when I couldn't get it going for a while, I thought I'd browse for a spare phone, anything, something old to screw around with and really practice on.
well, don't I find a 'bricked' amaze in my local classifieds! so $50 later I have myself a spare amaze to mess with! This phone powers on and goes straight to hboot, and I thought sweet, a factory rom upgrade and away we go. but it wasn't so easy.
this phone is a telus, and was relocked, but the one thing I noticed on this one that I didn't on mine when I flashed the telus rom is that this one has a 'security warning' under the relocked banner at the top of hboot. For the life of me I can't seem to get an oem rom to upgrade this phone. I've tried 3 different sd's, formatting etc. downloading the telus ruu zip from lots of different sites, trying with sd out then installing it when hboot loads, with and without usb plugged in, you name it I've tried it, and I cant' seem to get a stock rom to load.
hboot checks for ph85diag, then ph85img, finds it, checks it, then checks it again and back to hboot. No matter what I do, it won't ask to upgrade, and even trying out other ruu's it'll at least tell me that its the wrong file. Funny thing is in all of this I've already done this on my fully working amaze, and it worked right away, the only thing I'm thinking is that security warning banner, if that's in any way preventing the install.
any thoughts?
andy55 said:
I've recently rooted and had some issues with my personal phone, which I've cleared up with help from this board and members, and have actually enjoyed messing with my phone, its been fun learning about android and the possibilities with these phones. But with a bit of hesitation on going at it again with my phone, and how screwed I was when I couldn't get it going for a while, I thought I'd browse for a spare phone, anything, something old to screw around with and really practice on.
well, don't I find a 'bricked' amaze in my local classifieds! so $50 later I have myself a spare amaze to mess with! This phone powers on and goes straight to hboot, and I thought sweet, a factory rom upgrade and away we go. but it wasn't so easy.
this phone is a telus, and was relocked, but the one thing I noticed on this one that I didn't on mine when I flashed the telus rom is that this one has a 'security warning' under the relocked banner at the top of hboot. For the life of me I can't seem to get an oem rom to upgrade this phone. I've tried 3 different sd's, formatting etc. downloading the telus ruu zip from lots of different sites, trying with sd out then installing it when hboot loads, with and without usb plugged in, you name it I've tried it, and I cant' seem to get a stock rom to load.
hboot checks for ph85diag, then ph85img, finds it, checks it, then checks it again and back to hboot. No matter what I do, it won't ask to upgrade, and even trying out other ruu's it'll at least tell me that its the wrong file. Funny thing is in all of this I've already done this on my fully working amaze, and it worked right away, the only thing I'm thinking is that security warning banner, if that's in any way preventing the install.
any thoughts?
Click to expand...
Click to collapse
unlock it done
you're kidding, its that easy? I thought about it too and didn't try that. First thing I'll be doing when I get home
what I was screwed by was I did the exact same thing to my good phone, I re-locked it, and loaded the telus rom and it went easy, no problems, and I tried the same with this phone, and no dice
did the unlock trick work
I'll let you know in a couple hours, the dud's at home and I'm stuck at work with computers that encrypt everything connected to them no screwing around (to a certain degree) at work
yup worked, had issues with wifi/bluetooth but bulletproof fixed that issue, all is working again, thanks, I can't believe I didn't think that would work before!
Verizon is sending out replacement phone and need to restore this to stock.
This also started prior to flashing the new ICS leak and after dling ~600mb's via wireless tether.
Not sure if something burned up.
Phone is stuck on 1X only. Tried everything and can't get 3g or reliable 4g.
It get's 4G but only a minute at a time.
I tried doing the various "Fix network bootloop 1x issue threads" but still a no go.
Phone doesn't take the CDMA only option under Mobile networks, it resets back to to lte/cdma.
It never drops to 3g.
I dled the RUU but it does not update nor recover.
Any ideas?
Thanks!
Flash the stock Rom from scrosler's website.
www.scottsroms.com
Droidel said:
Verizon is sending out replacement phone and need to restore this to stock.
This also started prior to flashing the new ICS leak and after dling ~600mb's via wireless tether.
Not sure if something burned up.
Phone is stuck on 1X only. Tried everything and can't get 3g or reliable 4g.
It get's 4G but only a minute at a time.
I tried doing the various "Fix network bootloop 1x issue threads" but still a no go.
Phone doesn't take the CDMA only option under Mobile networks, it resets back to to lte/cdma.
It never drops to 3g.
I dled the RUU but it does not update nor recover.
Any ideas?
Thanks!
Click to expand...
Click to collapse
First thing I'm thinking is you can't RUU back in your situation because the version number is higher than the old RUU. My suggestion is to ROM it, and then flash back to stock RUU, because most ROMs set the version number to 1.0.0.0, therefore all RUU's are a higher version number. Then when you go to flash it, it will recognize, read and flash.
On a side note form this, you're pretty much screwed if you're trying to go to stock from something ripped, since your bootloader will show relocked or tampered, or something other than 'locked' as it shows when completely stock out of the box. This is of course unless you never unlocked it, which means you cant change version numbers, which means you're screwed either way.
Verizon will be able to look at your bootloader and know that it isnt factory stock, so chances are, they are going to charge you for your phone. I'm just trying to be honest and upfront, since I'm kind of a realist when it comes to getting screwed by big corporations like Verizon.
Good luck getting it back to an older version though.
p.s. on the note of your signal issue... the back is on the phone, right? Did you check the contacts inside the cover?
poppajules said:
First thing I'm thinking is you can't RUU back in your situation because the version number is higher than the old RUU. My suggestion is to ROM it, and then flash back to stock RUU, because most ROMs set the version number to 1.0.0.0, therefore all RUU's are a higher version number. Then when you go to flash it, it will recognize, read and flash.
On a side note form this, you're pretty much screwed if you're trying to go to stock from something ripped, since your bootloader will show relocked or tampered, or something other than 'locked' as it shows when completely stock out of the box. This is of course unless you never unlocked it, which means you cant change version numbers, which means you're screwed either way.
Verizon will be able to look at your bootloader and know that it isnt factory stock, so chances are, they are going to charge you for your phone. I'm just trying to be honest and upfront, since I'm kind of a realist when it comes to getting screwed by big corporations like Verizon.
Good luck getting it back to an older version though.
p.s. on the note of your signal issue... the back is on the phone, right? Did you check the contacts inside the cover?
Click to expand...
Click to collapse
The contacts are fine. what if the phone bricked during a software update in hboot? Can they still see relocked and tampered?
Some say that vz doesnt care as long as it has no physical damage.
I don't know about Verizon not caring, but I highly doubt they would take back all of our rooted phones..
I doubt the phone bricked if it booted up. I would flash the ICS RUU and see if the radios fix your signal issue.
Like I said before, I am running Scott's CleamROM and it sets the software versions to 1.0.0.0, so any RUU will flash over it. This is your best bet.
If VZW doesn't care about the bootloader, then you're golden, but don't count on that.
If I may pry, why are you sending it back for the replacement? If it's because of the radios, then I really doubt they are going to just take the phone back, since you could have messed up software to cause the issue.
Just try flashing some stuff before you call it busted. I would go with the ICS leak, Scott's CleanROM, and then back to your old RUU if you want. There's also a patch you have to install to downgrade from CleanROM and ICS leak back to GB, so you might want to do research, also. If you need help finding stuff, just send me a PM.
p.s. Anyone can boot your phone to bootloader (unless of course your phone is in little tiny pieces all over the street), and see that the bootloader is unlocked, possibly tampered for the custom recovery installed, and even if you lock it again, it will say relocked, indicating to everyone that it has been unlocked at one point. 'Unlocked', 'Relocked', 'Tampered', and 'Security Warning' void certain parts of your warranty (in the words of HTC dev.com). The only thing that doesn't void it is if it reads 'Locked'. Period.
Some say that vz doesnt care as long as it has no physical damage.[/QUOTE] Dude I sent two Dinc2 back completed rooted with no problems. Most times the tech at big V. couldn't care less. Most don't wouldn't know what rooting is and the ones that do, more than likely are rooted themselves. The question is if they send it to HTC? And will it meet their requirment now that they have a record that you are rooted as I'm sure if you're had to go thru HTC to unlock. However in reading alot of cases noone have posted a problem with returning a rooted or relocked phone at lease none I've read about. Good luck tho as there's always that first time.
ghostt021 said:
Dude I sent two Dinc2 back completed rooted with no problems. Most times the tech at big V. couldn't care less. Most don't wouldn't know what rooting is and the ones that do, more than likely are rooted themselves. The question is if they send it to HTC? And will it meet their requirment now that they have a record that you are rooted as I'm sure if you're had to go thru HTC to unlock. However in reading alot of cases noone have posted a problem with returning a rooted or relocked phone at lease none I've read about. Good luck tho as there's always that first time.
Click to expand...
Click to collapse
Yeah, I've never tried to send a rooted phone back, personally, but I've never asked anyone at VZW about it. (I'm paranoid that SWAT will descend from the roof and take me down if they knew my phone was rooted)
Good luck dude, just box it up and ship it off then. 'F' 'em.
No go, reflashed ICS leak, the tamper and security warning are gone.
I don't understand why it's not letting me switch to CDMA only. It goes back to CDMA/LTE. Could a bad SIM card cause 3g issues?
I doubt the SIM card would cause 3G issues, but hey, anything is possible I guess. I would say that you wouldn't get ANY signal if the SIM card were bad. Do you have another SIM card phone to test with, perhaps? Just an idea...
Did you go to a ROM instead of just the leak? Hell, you might just have signal issues where you are.. Maybe?
Maybe the antenna did burn up.. never heard of it, but that's not saying it can't happen.
I think tracing your steps back is going to be the best at figuring out the issue. When you flashed the ICS leak, you relocked and flashed, right? no errors? the install went straight down the list with no skipping around? After the install, you went through full HTC/Verizon setup? Have you tried the phone in other locations, i.e. work, groceiry store, gas station, interstate, etc.? Even outside the house will give a different strength... Forgive these sugestions as 'elementary' or 'duh' type suggestions, but something just doesn't sound right.
Also, go to your network settings and try changing the network type from automatic to home only. See what happens.
poppajules said:
I doubt the SIM card would cause 3G issues, but hey, anything is possible I guess. I would say that you wouldn't get ANY signal if the SIM card were bad. Do you have another SIM card phone to test with, perhaps? Just an idea...
Did you go to a ROM instead of just the leak? Hell, you might just have signal issues where you are.. Maybe?
Maybe the antenna did burn up.. never heard of it, but that's not saying it can't happen.
I think tracing your steps back is going to be the best at figuring out the issue. When you flashed the ICS leak, you relocked and flashed, right? no errors? the install went straight down the list with no skipping around? After the install, you went through full HTC/Verizon setup? Have you tried the phone in other locations, i.e. work, groceiry store, gas station, interstate, etc.? Even outside the house will give a different strength... Forgive these sugestions as 'elementary' or 'duh' type suggestions, but something just doesn't sound right.
Also, go to your network settings and try changing the network type from automatic to home only. See what happens.
Click to expand...
Click to collapse
I noticed this happeneng a day prior to flashing the ICS leak. I was using wifi tether do download about 600mb's and notice a couple of hours later that it dropped to 1x. Restarted phone and it went to 4g. I usually switch to 3g to save battery, that's when i notice the problem.
The ics leak flash didn't show any errors.
I am trying to flash GB to this new firmware but i'm having a hard time flashing the PH98IMG RUU from scott's site. It reads and checks it but doesnt flash it.
RUU.exe errored out with "Unknown Error"
Droidel said:
I am trying to flash GB to this new firmware but i'm having a hard time flashing the PH98IMG RUU from scott's site. It reads and checks it but doesnt flash it.
RUU.exe errored out with "Unknown Error"
Click to expand...
Click to collapse
Make SURE you are pulling the PH98IMG for the stock RUU from the android police website, NOT Scott. He didn't post up the new leak. The RUU that Scott has will NOT flash over the old ICS stuff he's put out before.
Go here to get the leaked RUU.
In this process, relock your bootloader, flash the file from A.P.(TWICE, this is important), unlock your bootloader with your unlock token from htcdev, and THEN flash what scott has. It's a time consuming process. It's up to you though. The directions are out there on A.P., Scott's website, all over Scott's thread around the 400-page range for the 4.0.1 release... and my abbreviated directions here.
Grab one of the top three selections, not the pre-rooted version.
also, try going back and re-downloading your ROM file, maybe you got a bad download.
If you upgraded to ics, you can't ruu to gingerbread at all because of the older hboot. But you can flash a gb kernel then a Rom or nandroid+ scrosler sdcard fix
Sent from my ADR6425LVW using xda premium
So here's my story, I am not entirely new to rooting as I have successfully rooted my Motorola Droid, My Droid X2, My Acer Iconia a500 (twice), My aunts Lg something, and my mothers Kindle Fire.
So a few days ago my Droid X2 started acting up, and would go hours on end sometimes without working.
I was very happy to find out that Verizon would replace it with no hassle as it was less than a year old. I got the replacement yesterday and it's working great... that is until I found out it came stock with 2.3.5 right out of the box.
Now I have always trusted XDA forums and have used them for a long time (although I finally just registered today to ask this)
The only root method I can find is to downgrade to 2.3.4 and then root, then install voodoo root protector, then upgrade.
Now I saw a few things about possibilities of bricking your phone when trying to read those tutorials (I have never had to downgrade before) and I was a bit concerned.
I was mainly wondering, I don't care about loosing data on the phone. I have a backup sd card I can use if I need to format that, and like I said, the phone is new and actually doesnt have a single app I have installed on it yet.
Is there any easy way to go back down to 2.3.4 for my situation? I just got the free phone and don't want to brick it a day later you know?
From what I gather, you can SBF back down to 2.3.4 with no problem. There may be a certain way you have to do it though. I have never been on stock 2.3.5 so I cant tell you from experience. But Everyone says it's possible.
That's my question in a nutshell
Yeah, I read a tutorial about how to do it using RSDlite, which I downloaded to my comp.
Now what I'm cautious about is white file to use. One of the tutorials had one, now while I know a tiny bit about rooting I know NOTHING about flashing it back, I wasn't sure if there was a way that this could screw up my phone, as it seems everything tested is with a phone that had already been rooted, or if there is anything phone specific in that file, or even if it actually is an OTA original (I'd rather not mess around with anything customized right now)
Whatever is the easiest method for getting be back down, I know how to take it from there as I've done it before.
Thanks for the response though!
Excolo said:
Yeah, I read a tutorial about how to do it using RSDlite, which I downloaded to my comp.
Now what I'm cautious about is white file to use. One of the tutorials had one, now while I know a tiny bit about rooting I know NOTHING about flashing it back, I wasn't sure if there was a way that this could screw up my phone, as it seems everything tested is with a phone that had already been rooted, or if there is anything phone specific in that file, or even if it actually is an OTA original (I'd rather not mess around with anything customized right now)
Whatever is the easiest method for getting be back down, I know how to take it from there as I've done it before.
Thanks for the response though!
Click to expand...
Click to collapse
So you have never used an SBF file? If you would have used it on your broken Droid X2 when it wasnt acting right, it might have fixed your phone. An SBF file simply wipes everything of your phone (excluding your SD card) and flashes brand new software on it. The SBF files are provided by Motorola so its not like you are using something made by a dev and can break your phone easily. You should be able to use RSD lite to flash the 2.3.4 SBF file and you should be fine. But then again, I have never SBF'd from 2.3.5 to 2.3.4 personally so I would feel bad saying go ahead with no worries and something bad happen. So wait for someone else to respond first.
Thanks!
Thanks for that info!
Also, I doubt that would have fixed my old phone, it seems pretty much like a hardware issue. The screen will display static for hours on end (think like an old tv if you didnt have cable plugged in) I think it's a loose connection somewhere or something. I didn't bother to really troubleshoot it myself though because I was like "lets see if Verizon will give me a new one" and they did, and because they didnt have any "replacements" i got a brand new one, with a brand new battery, so I wasn't going to argue the fact
Anyway, if the file is from Motorola where can I get it? I saw on a verizon forum that they were not allowed to post it there (or is it "from motorola" in the sense it was leaked?)
Thanks for all your help so far, you've been great!
Excolo said:
Thanks for that info!
Also, I doubt that would have fixed my old phone, it seems pretty much like a hardware issue. The screen will display static for hours on end (think like an old tv if you didnt have cable plugged in) I think it's a loose connection somewhere or something. I didn't bother to really troubleshoot it myself though because I was like "lets see if Verizon will give me a new one" and they did, and because they didnt have any "replacements" i got a brand new one, with a brand new battery, so I wasn't going to argue the fact
Anyway, if the file is from Motorola where can I get it? I saw on a verizon forum that they were not allowed to post it there (or is it "from motorola" in the sense it was leaked?)
Thanks for all your help so far, you've been great!
Click to expand...
Click to collapse
Yeah, it does sounds like it was a hardware problem. Actually, I never thought about if motorola had a list of sbf files somewhere or if they were just leaked or what. I always downloaded them from threads like these. I just know they are made by motorola. You got me curious now. hmmm...
Duh
forget about my question as to where to get them, just saw the sticky at the front of this forum.
Although, it would be interesting to know if they were officially given out by motorola or leaked
Excolo said:
forget about my question as to where to get them, just saw the sticky at the front of this forum.
Although, it would be interesting to know if they were officially given out by motorola or leaked
Click to expand...
Click to collapse
What's An SBF File?
• SBF Is A File Leaked By Motorola That Is The System Image Flashed By RSDLite.
Taken from the Motorola Droid X2 FAQ page here
Excolo said:
So here's my story, I am not entirely new to rooting as I have successfully rooted my Motorola Droid, My Droid X2, My Acer Iconia a500 (twice), My aunts Lg something, and my mothers Kindle Fire.
So a few days ago my Droid X2 started acting up, and would go hours on end sometimes without working.
I was very happy to find out that Verizon would replace it with no hassle as it was less than a year old. I got the replacement yesterday and it's working great... that is until I found out it came stock with 2.3.5 right out of the box.
Now I have always trusted XDA forums and have used them for a long time (although I finally just registered today to ask this)
The only root method I can find is to downgrade to 2.3.4 and then root, then install voodoo root protector, then upgrade.
Now I saw a few things about possibilities of bricking your phone when trying to read those tutorials (I have never had to downgrade before) and I was a bit concerned.
I was mainly wondering, I don't care about loosing data on the phone. I have a backup sd card I can use if I need to format that, and like I said, the phone is new and actually doesnt have a single app I have installed on it yet.
Is there any easy way to go back down to 2.3.4 for my situation? I just got the free phone and don't want to brick it a day later you know?
Click to expand...
Click to collapse
bro, you wont have any problems downgrading/sbfing back to 2.3.4, i did it without any problems
i used sbf_flash through linux though idk about RSDLite
My HTC M8 runs Android 5.0.2, Software number 4.28.502.2 and it is stuck in airplane mode. In settings the airplane mode is "greyed out". I did a hard reset,
spent 1 hour with HTC technician on phone and no one could help. Only solution seems to send it to HTC for reflashing. Any ideas out there on how to solve it ?
Would appreciate any help, thanks.
[email protected] said:
My HTC M8 runs Android 5.0.2, Software number 4.28.502.2 and it is stuck in airplane mode. In settings the airplane mode is "greyed out". I did a hard reset,
spent 1 hour with HTC technician on phone and no one could help. Only solution seems to send it to HTC for reflashing. Any ideas out there on how to solve it ?
Would appreciate any help, thanks.
Click to expand...
Click to collapse
Run the latest ruu for your phone. But backup everything because that will wipe your phone clean. Best results is using Windows 7 You can find the ruu here http://www.htc.com/us/support/htc-one-m8-att/news
Sent from my HTC One_M8
[email protected] said:
My HTC M8 runs Android 5.0.2, Software number 4.28.502.2 and it is stuck in airplane mode. In settings the airplane mode is "greyed out". I did a hard reset,
spent 1 hour with HTC technician on phone and no one could help. Only solution seems to send it to HTC for reflashing. Any ideas out there on how to solve it ?
Would appreciate any help, thanks.
Click to expand...
Click to collapse
Is the phone "stock" or has it ever been modded (unlocked bootloader, root, custom ROM, etc)?
redpoint73 said:
Is the phone "stock" or has it ever been modded (unlocked bootloader, root, custom ROM, etc)?
Click to expand...
Click to collapse
phone is stock, never changed anything to it.
[email protected] said:
phone is stock, never changed anything to it.
Click to expand...
Click to collapse
Than I agree with the previous recommendation, RUU to stock is your best bet.
Backup your data first, as also mentioned, RUU will wipe the phone.
redpoint73 said:
Than I agree with the previous recommendation, RUU to stock is your best bet.
Backup your data first, as also mentioned, RUU will wipe the phone.
Click to expand...
Click to collapse
Thank you but I have never tinkered with any smartphone software so I really need step by step instructions otherwise I will make a mess of it.
[email protected] said:
Thank you but I have never tinkered with any smartphone software so I really need step by step instructions otherwise I will make a mess of it.
Click to expand...
Click to collapse
See the link in Post #2 above. The RUU download is at the bottom of the linked HTC webpage; and the instructions are near the bottom under "Manual system update instructions".
PC is required, and Win7 are USB 2.0 are suggested.
Its not really "tinkering" but rather an official HTC update/recovery program, that is pretty self-explanatory and intended for use by folks without much specialized knowledge.
If you want to backup any personal data on the phone before running the RUU, the methods would depend on what you want to save; and your preferred storage method (SD card, computer, cloud).
redpoint73 said:
See the link in Post #2 above. The RUU download is at the bottom of the linked HTC webpage; and the instructions are near the bottom under "Manual system update instructions".
PC is required, and Win7 are USB 2.0 are suggested.
Its not really "tinkering" but rather an official HTC update/recovery program, that is pretty self-explanatory and intended for use by folks without much specialized knowledge.
If you want to backup any personal data on the phone before running the RUU, the methods would depend on what you want to save; and your preferred storage method (SD card, computer, cloud).
Click to expand...
Click to collapse
So, I started the process, sync manager does not recognize the phone, so had to do it the other way with the fastboot and that worked, but the upgrading of ROM is stuck at 14%, and the version I am installingis the same as the one I had installed.
[email protected] said:
the upgrading of ROM is stuck at 14%
Click to expand...
Click to collapse
RUU just gets stuck sometimes, its not uncommon based on reports here.
Disconnect the phone (or otherwise end the process) and start over. It says you're not supposed to do that. But there isn't anything else you can do.
[email protected] said:
the version I am installingis the same as the one I had installed.
Click to expand...
Click to collapse
That is normal and intended. In this case, its not an actual "upgrade". But rather a recovery, re-writing all partitions back to stock; which will hopefully fix your "stuck in airplane mode" issue.
redpoint73 said:
RUU just gets stuck sometimes, its not uncommon based on reports here.
Disconnect the phone (or otherwise end the process) and start over. It says you're not supposed to do that. But there isn't anything else you can do.
That is normal and intended. In this case, its not an actual "upgrade". But rather a recovery, re-writing all partitions back to stock; which will hopefully fix your "stuck in airplane mode" issue.
Click to expand...
Click to collapse
Well, I re-did it and this time it did all correctly but the phone is still stuck in airplane mode. I am starting to believe that it is a hardware problem. I bought the phone new on Ebay from an online retailer
in November and HTC will not repair it because the seller is not an approved HTC retailer. So now I am stuck with a useless $300 piece of equipment and of course I will never buy an HTC again. If you look at the blogs
there are literally thousands of people saying that the after service from HTC is the worst in the industry. I have written a letter to HTC in Taiwan with copy to HTC USA in Oregon explaining everything and how disappointed I am at the way they do business.
Well all you XDA guys out there, many thanks for the help, I really appreciate it. PATRICK
Sync manager should recognize the phone. Hook your phone up to your PC and wait for sync to see the phone. it should automatically run the OTA updates for you. (some models will allow updates from HTC Sync) You are on older software. Have you tried a more recent RUU to see if it goes through? running a repair with same version will not let you know if the phone fully took the repair, but with a newer RUU, you will see in settings - about phone the software upgrade so you know the RUU took.
Uzephi said:
Hook your phone up to your PC and wait for sync to see the phone. it should automatically run the OTA updates for you. (some models will allow updates from HTC Sync) .
Click to expand...
Click to collapse
AT&T version will only update over the AT&T network.
Also, no further OTA updates are available for the AT&T version at this time.
AT&T is an oddball version, so you not knowing these things is understandable.
Uzephi said:
You are on older software. Have you tried a more recent RUU to see if it goes through? running a repair with same version will not let you know if the phone fully took the repair, but with a newer RUU, you will see in settings - about phone the software upgrade so you know the RUU took.
Click to expand...
Click to collapse
4.28.502 is the current and latest software and RUU for the AT&T version. They haven't rolled out MM for AT&T version yet.
I agree its worth a try to RUU to MM, when its available. But I'm not optimistic it will change anything.
---------- Post added at 09:08 AM ---------- Previous post was at 09:04 AM ----------
[email protected] said:
Well, I re-did it and this time it did all correctly but the phone is still stuck in airplane mode. I am starting to believe that it is a hardware problem.
Click to expand...
Click to collapse
I tend to agree that its a hardware issue, since RUU back to full stock did not fix it.
Have you tried another SIM?
So the phone has been working since November, and just recently "stuck" in airplane mode? Any other changes to the phone around that same time that may be related?
Guys, again thanks for all the help postings. My only chance is to update to MM when available with AT&T, but I doubt whether it will work. Like I said before, more and more
I am convinced that something inside the phone is simply broken. It could be a defective circuit board. What puzzles me though is that worldwide there are thousands of HTC owners complaining about the same thing, none has managed successfully to repair one and the lucky ones simply got a replacement. What bugs me most is the horrible service at HTC, minimal efforts to help you, borderline rude. Years ago I had a similar problem with a Nokia, the same day they overnighted me a replacement phone to help me until my broken one could be sorted out. Now, that was service.
[email protected] said:
Guys, again thanks for all the help postings. My only chance is to update to MM when available with AT&T, but I doubt whether it will work. Like I said before, more and more
I am convinced that something inside the phone is simply broken. It could be a defective circuit board. What puzzles me though is that worldwide there are thousands of HTC owners complaining about the same thing, none has managed successfully to repair one and the lucky ones simply got a replacement. What bugs me most is the horrible service at HTC, minimal efforts to help you, borderline rude. Years ago I had a similar problem with a Nokia, the same day they overnighted me a replacement phone to help me until my broken one could be sorted out. Now, that was service.
Click to expand...
Click to collapse
Well, to be honest, you bought a phone from a third party. Phones have a 1 year warranty through HTC. I know from personal experience, the first boot an HTC does in it's life (not a factory reset or RUU will do this) it provisions itself and tells HTC the time stamp it was turned on to activate the warranty.
Now, you bought it from a third party retailer. This phone is obviously over a year old. Maybe the phone has been on for over that year marker? Quite understandable when you think about it. I got a DNA off a friend and when I had issues with it, I asked HTC if they had a way to see if I could just warranty the phone. They told me the exact time down to the second the phone was set up for the first time. It was out of warranty, sadly and they couldn't do anything.
Also, do you know if the previous owner unlocked the bootloader? The phone's serial gets sent to HTC. Maybe they knew the warranty was void. (There is a way to "hide" the fact it wasn't unlocked, but HTC still knows)
Did your Nokia ever get any modifications like that to void the warranty?
You make a valid point but we the consumers buy from a "reputable" online retailer a brand-new-in-box phone and we get it and it is originally packed and sealed in November 2015 and we feel that the warranty starts right then. Has the "reputable" seller tinkered with it ? Maybe, how is the layman to know.
But, let me tell you that they checked the IMEI and spent 1 hour on the phone trying to help me, to no avail. The phone cost me $300, they could have offered to repair it against cash and if the price had been reasonable I would have gone along. But no, our specialists cannot fix, you should send it in but you cannot send it in because the warranty is out.
After all, it still is a premium product at a premium price, the only thing not premium is HTC itself.
[email protected] said:
You make a valid point but we the consumers buy from a "reputable" online retailer a brand-new-in-box phone and we get it and it is originally packed and sealed in November 2015 and we feel that the warranty starts right then. Has the "reputable" seller tinkered with it ? Maybe, how is the layman to know.
But, let me tell you that they checked the IMEI and spent 1 hour on the phone trying to help me, to no avail. The phone cost me $300, they could have offered to repair it against cash and if the price had been reasonable I would have gone along. But no, our specialists cannot fix, you should send it in but you cannot send it in because the warranty is out.
After all, it still is a premium product at a premium price, the only thing not premium is HTC itself.
Click to expand...
Click to collapse
I know from experience HTC will fix any of their phones for a price. I openly admitted to using an exploit to s-off my DNA and they quoted me the screen replacement and the new main board as mine was s-off they would need to replace that as well. It was pretty steep due to pretty much needing everything but the battery and shell.
Also, I admitted in the call that I got it second hand from someone else which is worse than a third party seller. The quote was $275 at the time.
Well, I paid $300 for mine and the way I see it they would not repair it but replace it a probable cost of at least $300.
In this transaction I was always the loser.
[email protected] said:
Well, I paid $300 for mine and the way I see it they would not repair it but replace it a probable cost of at least $300.
In this transaction I was always the loser.
Click to expand...
Click to collapse
Their rule is phone is under warranty 17 month after production date, that's in case when you or they can't prove when the phone was bought . Call again and tell them that you got it from att , they might ask for proof of when was purchased , tell them you will try to get proof then call again and talk to somebody else and pray that they don't ask for proof. that's how I did it and was covered under warranty. I think its about who you talk to on the phone. Never claim that you are second owner, just say you are the original owner. Good luck.
Sent from my HTC One_M8
The moment they see the IMEI number they know they will not cover it. In a last desperate attempt to get consumer justice, I wrote a letter to HTC Headquarters in Taiwan asking for their stand in this matter.
I also posted some blog links which show that this problem seems systematic on a large number of HTC's worldwide. If this fails all that is left to do is use the "crippled" phone as an Ipod.
Stuck Airplane Mode
Dear Support Team,
Am from Kenya and I have a HTC one M8 with the exact problem explained in this forum. Stuck Airplane mode and it it greyed out and I have lost network in the process.
Mu phone is currently running on Adroid Version 6.0; HTC Sense Version 7.0 and Software number 6.14.707.1.
How do I reset the stuck airplane mode ?
Sent from my HTC One_M8[/QUOTE]