i need some help. i just bought my htc one tonight, and of course the first thing i want to do after i turn it on is root. but i can't get fastboot to recognize it. i've reinstalled the drivers a few times, googled my heart out, and can't seem to come up with an answer.
now before a lynch mob starts, please, i'm very frustrated, and i'm fighting the urge to just throw the phone into the wall. (at this point i think it's the only thing i haven't tried).
i read somewhere about firmware and windows 8.1 (which i'm on). my phone is still on 4.1.2. i think i read 4.3 is the only one that works with windows 8.1. but there are no updates available to me.
i greatly appreciate any help here. it's such a let down to get a shiny new phone, and being stuck... once i figure out the fastboot problem i should be good to go. i want to say i had this problem a while back with my htc one x, but it was so long ago i don't remember how i fixed it. in the middle there i switched to the s3 and that rooted without a hitch.
i don't know what i did but the phone magically decided now it wants to do the att update, it's downloading pretty slow but i'll see what happens.
ck4794 said:
i need some help. i just bought my htc one tonight, and of course the first thing i want to do after i turn it on is root. but i can't get fastboot to recognize it. i've reinstalled the drivers a few times, googled my heart out, and can't seem to come up with an answer.
now before a lynch mob starts, please, i'm very frustrated, and i'm fighting the urge to just throw the phone into the wall. (at this point i think it's the only thing i haven't tried).
i read somewhere about firmware and windows 8.1 (which i'm on). my phone is still on 4.1.2. i think i read 4.3 is the only one that works with windows 8.1. but there are no updates available to me.
i greatly appreciate any help here. it's such a let down to get a shiny new phone, and being stuck... once i figure out the fastboot problem i should be good to go. i want to say i had this problem a while back with my htc one x, but it was so long ago i don't remember how i fixed it. in the middle there i switched to the s3 and that rooted without a hitch.
Click to expand...
Click to collapse
Im sure you did this, but did you make sure in HBOOT its highlighted in red "FASTBOOT USB"? And you are in the platform tools folder of the android sdk? How about ADB? Does "adb devices" (Without quotations) work?
Let me know.
GalaxyUser50 said:
Im sure you did this, but did you make sure in HBOOT its highlighted in red "FASTBOOT USB"? And you are in the platform tools folder of the android sdk? How about ADB? Does "adb devices" (Without quotations) work?
Let me know.
Click to expand...
Click to collapse
i haven't gotten there yet. still trying to do the update. for some reason i can only download 10 or 15 mb at a time. it seems like it's timing out, maybe losing connection. after a restart it downloads for a while again. so basically it's going to be a loooong night to get this update done. and some prayer that the update is not corrupted.
ck4794 said:
i haven't gotten there yet. still trying to do the update. for some reason i can only download 10 or 15 mb at a time. it seems like it's timing out, maybe losing connection. after a restart it downloads for a while again. so basically it's going to be a loooong night to get this update done. and some prayer that the update is not corrupted.
Click to expand...
Click to collapse
Are you trying this on wifi or data?
ck4794 said:
i haven't gotten there yet. still trying to do the update. for some reason i can only download 10 or 15 mb at a time. it seems like it's timing out, maybe losing connection. after a restart it downloads for a while again. so basically it's going to be a loooong night to get this update done. and some prayer that the update is not corrupted.
Click to expand...
Click to collapse
you need to s-off your phone before taking that update !!!
and you need a windows 8 or windows 7 PC ... you'll never get fastboot on windows 8.1 and hboot 1.44.000 might as well give up on that.
clsA said:
you need to s-off your phone before taking that update !!!
and you need a windows 8 or windows 7 PC ... you'll never get fastboot on windows 8.1 and hboot 1.44.000 might as well give up on that.
Click to expand...
Click to collapse
no that seemed to do the trick. installed the update this morning. the phone is now on 4.3 and fastboot works just fine.
ck4794 said:
no that seemed to do the trick. installed the update this morning. the phone is now on 4.3 and fastboot works just fine.
Click to expand...
Click to collapse
ok good ...try rumrunner if you want s-off
clsA said:
ok good ...try rumrunner if you want s-off
Click to expand...
Click to collapse
thanks. it's been a hot minute since i've had an htc phone, can you remind me why i would want s-off after i already have the device rooted?
ck4794 said:
thanks. it's been a hot minute since i've had an htc phone, can you remind me why i would want s-off after i already have the device rooted?
Click to expand...
Click to collapse
This pretty well sums it up
S-OFF – What And Why?
In their devices, HTC have installed a sort of security check whose level is determined by S-OFF/S-ON. Essentially, this security level is a flag stored on the device’s radio that checks signature images for any firmware before it is allowed to be written to system memory. This hinders using any custom ROMs, splash images, recovery etc., and also restricts access to the NAND flash memory. However, when security level is set to S-OFF, the signature check is bypassed, allowing a user to upload custom firmware images, unsigned boot, recovery, splash and HBOOT images, as well as official firmware that has been modified, this enabling maximum customization of your HTC Android device.
Furthermore, S-OFF also reduces restrictions on accessing the NAND flash memory on the device, allowing all partitions (including /system) to be mounted in write mode while the operating system is booted.
Source: http://www.addictivetips.com/mobile...on-htc-android-phones-with-unrevoked-forever/
Click to expand...
Click to collapse
Related
I have an unrooted HTC Aria (AT&T) that i upgraded to Froyo a couple of weeks ago. I have been using it for a while and i don't like the performance with the new upgrade, it used to be a LOT snappier before.
I would like to know if its possible to revert the phone to Factory Defaults (Eclair 2.1) and where i can get the ROM since HTC is no longer providing it in its website.
I'm not interested in rooting my phone nor custom roms i just want it the way it was at the moment I took it off the box and turned it on for the first time.
If the downgrade is possible I would really appreciate if someone could provide a list of steps to follow to make it happen.
Thanks in advance.
Check out this thread: http://forum.xda-developers.com/showthread.php?t=971119. You can but you will still have the updated HBOOT (Bootloader). You will have to use the ROM linked in post 3 (Original 2.1 Rom)
P.S - Search before starting new threads on the same topic.
http://www.mediafire.com/?cj56c2gfk86k8oe
This is the original ship ROM. I downloaded this back when I first got my phone (first day the Aria was released) and have kept it for future use. This was even before they added the ability to receive OTA updates, so you won't even have to worry about being notified about the 2.2.2 OTA update.
Now, you should be able to just run this and have it downgrade everything (except HBOOT, but that isn't a problem unless you want to root). I haven't actually done it before but it should work.
If it doesn't work, there is another way that will definitely work, but I'll explain that if the need arises. Let me know if you run into any problems.
Theonew said:
Nope. Not possible since you don't want to root your device.
Click to expand...
Click to collapse
It is possible. You can downgrade everything except the HBOOT. (Meaning, he will have the original ROM like he wants but be unable to use Unrevoked, which he doesn't care about.)
drumist said:
It is possible. You can downgrade everything except the HBOOT. (Meaning, he will have the original ROM like he wants but be unable to use Unrevoked, which he doesn't care about.)
Click to expand...
Click to collapse
That post I made was a mistake. That's why I edited it. Sorry I didn't get to change it in time.
Theonew said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=971119. You can but you will still have the updated HBOOT (Bootloader). You will have to use the ROM linked in post 3 (Original 2.1 Rom)
P.S - Search before starting new threads on the same topic.
Click to expand...
Click to collapse
To be honest the advice from those threads is not really very good anyway. You don't need temp root on your device. There are easier methods that ought to work fine. Namely, just putting the 2.1 RUU zip as LIBEIMG.zip on your SD card. But from what I've read, even just running the RUU should be enough.
(Nevermind, this doesn't work.)
Thanks for you advice, in fact did some research before creating the thread, but all the threads i found were about people who wanted to downgrade to get the root back, so they were either redirected to other threads or were given a lot information not relevant to what i really need.
drumist said:
This is the original ship ROM. I downloaded this back when I first got my phone (first day the Aria was released) and have kept it for future use. This was even before they added the ability to receive OTA updates, so you won't even have to worry about being notified about the 2.2.2 OTA update.
Now, you should be able to just run this and have it downgrade everything (except HBOOT, but that isn't a problem unless you want to root). I haven't actually done it before but it should work.
If it doesn't work, there is another way that will definitely work, but I'll explain that if the need arises. Let me know if you run into any problems.
Click to expand...
Click to collapse
I tried this but for some reason i got a BOOTLOADER VERSION ERROR [140] message. Thanks for your help anyway.
eljuanpelos said:
I tried this but for some reason i got a BOOTLOADER VERSION ERROR [140] message. Thanks for your help anyway.
Click to expand...
Click to collapse
Don't give up yet. This next method should work if that one didn't.
Download this file: http://www.mediafire.com/?ct1ay7t93d8g742
Rename the zip file as LIBEIMG.zip (don't extract it) then place it on your SD card (not in a subfolder).
Then turn the phone completely off, and press VOL DOWN + power to turn the phone back on. It should detect the file after a couple seconds and start flashing it automatically. At this point just be patient for a minute or two, then press VOL UP key to start the update process when it asks you to. After that, be patient while it does everything. It takes about 5 minutes to finish installing everything and will reboot once during the process. After it's done (it will tell you when it's done), the phone will reboot and there will be a scary looking screen but JUST WAIT about 10 seconds and it will boot normally. Then you're good to go.
After you're done with this, make sure to DELETE the LIBEIMG.zip file from your SD card. Otherwise it will ask you every time you go into HBOOT if you want to apply the update.
Good luck.
drumist said:
Don't give up yet. This next method should work if that one didn't.
Download this file:
Rename the zip file as LIBEIMG.zip (don't extract it) then place it on your SD card (not in a subfolder).
Then turn the phone completely off, and press VOL DOWN + power to turn the phone back on. It should detect the file after a couple seconds and start flashing it automatically. At this point just be patient for a minute or two, then press VOL UP key to start the update process when it asks you to. After that, be patient while it does everything. It takes about 5 minutes to finish installing everything and will reboot once during the process. After it's done (it will tell you when it's done), the phone will reboot and there will be a scary looking screen but JUST WAIT about 10 seconds and it will boot normally. Then you're good to go.
After you're done with this, make sure to DELETE the LIBEIMG.zip file from your SD card. Otherwise it will ask you every time you go into HBOOT if you want to apply the update.
Good luck.
Click to expand...
Click to collapse
Unfortunately this method doesn't work either, it throws an error that says "Main Version is older, Update Fail!"
I could have sworn I've read about this working before. I would have tested it first myself but I don't have a phone that isn't S-OFF. Sorry for making you jump through hoops.
You could try the methods in the other threads linked above. I guess you do need temp root to do a downgrade.
Alternatively, you could use AlphaRevX to S-OFF, install Clockwork, and install the factory original, unrooted ROM. The downside of this is that it requires voiding your warranty if you have one.
Easiest way would be to run the official 2.2 RUU update from HTC. 100% stock.
Sent from my Liberty
Optic2 said:
Easiest way would be to run the official 2.2 RUU update from HTC. 100% stock.
Sent from my Liberty
Click to expand...
Click to collapse
He wants to return to android 2.1 so that wouldn't help whatsoever. Plus he already did that which is why he wants to downgrade.
Oh my bad, I didn't read the whole thread. Hmm why do you want to downgrade to 2.1?
Sent from my Liberty
Optic2 said:
Hmm why do you want to downgrade to 2.1?
Sent from my Liberty
Click to expand...
Click to collapse
This is the reason which he said in his post:"I don't like the performance with the new upgrade, it used to be a LOT snappier before."
drumist said:
This is the original ship ROM. I downloaded this back when I first got my phone (first day the Aria was released) and have kept it for future use. This was even before they added the ability to receive OTA updates, so you won't even have to worry about being notified about the 2.2.2 OTA update.
Now, you should be able to just run this and have it downgrade everything (except HBOOT, but that isn't a problem unless you want to root). I haven't actually done it before but it should work.
If it doesn't work, there is another way that will definitely work, but I'll explain that if the need arises. Let me know if you run into any problems.
Click to expand...
Click to collapse
One question... I have HTC Gratia, which is operator free, so can I restore your original (backuped) ROM on my phone and update it, so I can use it just like original one?
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
jaawerth said:
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
Click to expand...
Click to collapse
Exact same thing happened to me last evening...except I'm rooted with S-off.
grimmkt said:
Exact same thing happened to me last evening...except I'm rooted with S-off.
Click to expand...
Click to collapse
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
jaawerth said:
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
Click to expand...
Click to collapse
Sounds good! let us know!:good:
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
I can't get the phone to connect in fastboot. I keep getting a "driver failed to load" type error when I plug in the USB...the device is never visible.
Worked like a charm! The download took awhile, but once I had it downloaded it was easy.
For others searching for this issue:
Once you have the RUU, just install Android Development tools (specifically fastboot) and enter
>fastboot oem rebootRUU
>fastboot flash install IMAGEFILE.ZIP
Terminal/command prompt on the computer side told me it was finished but the phone was stuck at the very end of the progress bar. I waited a while few minutes, and when it didn't move I risked doing a
>fastboot reboot
and we were good to go.
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
jaawerth said:
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
Click to expand...
Click to collapse
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
jaawerth said:
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
Click to expand...
Click to collapse
It's a known hardware issue in the DNA. When they give you a new Sim tray it's thicker and it holds the Sim card in place better resulting with no more errors.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
I'm stupid, I get it.
I just got an Asurion replacement DNA the other day and I wanted to S-Off, Root, Recovery Image, and new KitKat ROM.
So, I was able to use Rumrunner, and that worked out fine.
I rooted my DNA and then loaded TWRP 2.6.3, and that worked fine as well.
My intent was to load GPE and I d/l'd it to my phone (not knowing it was a corrupt download).
So I got into recovery, wiped, wiped, reset, and loaded the ROM - and it puked all over itself.
Now, I have a phone that is in recovery, has no image, and I can't figure out how to put one on it.
I'm running Mint Linux, but I have access to a W7 laptop if I need it.
It's my daily driver, I'm frustrated, upset, and stupid. And I could certainly use some help.
Thanks
In a terminal window (thanks .torrent), I typed: adb devices (then sudo adb devices) and got nothing in return.
I've tried sideloading; the ROM loads according to the terminal window, but I don't see anything happening on the phone (no failures though).
I've tried pushing a ROM to the phone but the terminal window says that it doesn't see the device. That doesn't make sense because I can sideload (apparently).
ugh.
Yehudah said:
In a terminal window (thanks .torrent), I typed: adb devices (then sudo adb devices) and got nothing in return.
I've tried sideloading; the ROM loads according to the terminal window, but I don't see anything happening on the phone (no failures though).
I've tried pushing a ROM to the phone but the terminal window says that it doesn't see the device. That doesn't make sense because I can sideload (apparently).
ugh.
Click to expand...
Click to collapse
This question has been answered at least a dozen times, "Help I wiped my internal storage", blah blah blah.
Download the rom you want on your computer. Put it in the same directory as your ADB stuff (mine is C:\android, I don't know what yours is).
Plug phone into computer, make sure you have ADB enabled on your phone, open a command prompt, verify you have ADB working by typing "adb devices"
You should see your device listed.
Boot phone into recovery >advanced >ADB sideload
Follow instructions at top of sideload screen to sideload rom from computer to phone.
In the future a little searching would get you to all this information, rather than starting a new thread... :good:
Enjoy
P.S. ALWAYS verify your MD5 before flashing, and ALWAYS have a backup made to fall back on.
I know it's been done to death. I searched and read every thread that was like mine and did everything in each thread.
It was the last thing I did that worked. RUU from .torrents links. That worked. I'm still rooted, Next time I'll make sure I have I backup I can restore - won't make this mistake again.
Thanks for the low level chastising, I deserved it. And thanks for the info, ad nauseum.
After a two day ordeal, I finally got my DNA back to where it was before I borked it up last week.
Because of what I did; I needed to use Rumrunner to unlock, RUU to get back to where the phone worked, ADB and Fastboot to get the recovery image set up and put a ROM on the phone.
When it was all said and done, .torrent walked me through getting the phone fixed. Without him, I'd still be banging my head against my desk.
Thanks to the developers who created Rumrunner, and who developed the Android tool kits that helped me overcome my stupidity. Because of their ability to create great applications, I've learned more about Linux and how my phone works than I ever did before....just wish it hadn't taken this to cause that.
Thanks to all, you guys ROCK! :good:
Yehudah said:
After a two day ordeal, I finally got my DNA back to where it was before I borked it up last week.
Because of what I did; I needed to use Rumrunner to unlock, RUU to get back to where the phone worked, ADB and Fastboot to get the recovery image set up and put a ROM on the phone.
When it was all said and done, .torrent walked me through getting the phone fixed. Without him, I'd still be banging my head against my desk.
Thanks to the developers who created Rumrunner, and who developed the Android tool kits that helped me overcome my stupidity. Because of their ability to create great applications, I've learned more about Linux and how my phone works than I ever did before....just wish it hadn't taken this to cause that.
Thanks to all, you guys ROCK! :good:
Click to expand...
Click to collapse
At least you learned from your mistakes.
Sent from my HTC6600LVW using XDA Premium 4 mobile app
thayl0 said:
At least you learned from your mistakes.
Sent from my HTC6600LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Are you using an HTC 6600 as your daily driver? LOL I had one of those, loved it.
Yehudah said:
Are you using an HTC 6600 as your daily driver? LOL I had one of those, loved it.
Click to expand...
Click to collapse
I'm not use haven't looked I'm using whatever it installed. lol
Hi All,
I have been trying to get the FW update with extreme save mode for almost a week now.
I check for software updates daily and I get the NO UPDATE found message.
Called At&t and tech support is as useful as my 3 years old kid.
Does anyone have the same problem? Solutions?
Thanks
Unlock bootloader, install Android Revolution thats been updated with latest release and you are good to go. No reason to wait till they let it work for yea when you can do it yourself.
JayRolla said:
Unlock bootloader, install Android Revolution thats been updated with latest release and you are good to go. No reason to wait till they let it work for yea when you can do it yourself.
Click to expand...
Click to collapse
Thanks for the advice, but others are getting the update OTA, without root or downloading Android Rev.
Some M8 owners may see a delay in getting the OTA, as it rolls out sequentially, by some means (I've seen AT&T suggest its by IMEI number). A minority of folks will never get it, just by some random fluke or other (as happens on any OTA).
If you don't want to wait, the RUU is already posted. You can download to a PC, and run it with your phone connected. But it will wipe user data.
http://forum.xda-developers.com/showthread.php?t=2757462
redpoint73 said:
Some M8 owners may see a delay in getting the OTA, as it rolls out sequentially, by some means (I've seen AT&T suggest its by IMEI number). A minority of folks will never get it, just by some random fluke or other (as happens on any OTA).
If you don't want to wait, the RUU is already posted. You can download to a PC, and run it with your phone connected. But it will wipe user data.
http://forum.xda-developers.com/showthread.php?t=2757462
Click to expand...
Click to collapse
Thanks for the tip, I tried that and it wouldn't work. Do I need root or s-off?
Also, has everyone that attempted to download things manually received the update?
I would really appreciate the responses
sassij said:
Thanks for the tip, I tried that and it wouldn't work. Do I need root or s-off?
Also, has everyone that attempted to download things manually received the update?
I would really appreciate the responses
Click to expand...
Click to collapse
How did it not work? As long as you are completely stock with cid cws__001 it should work.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
sassij said:
Hi All,
I have been trying to get the FW update with extreme save mode for almost a week now.
I check for software updates daily and I get the NO UPDATE found message.
Called At&t and tech support is as useful as my 3 years old kid.
Does anyone have the same problem? Solutions?
Thanks
Click to expand...
Click to collapse
download ota package from here http://www.androidfilehost.com/?fid=23487008491963146
put it on your micro sd card
boot to recovery "vol up and power 10 sec, vol down and power until boot loader comes up and navigate to recovery"
once in recovery its either vol up and power or vol down and power for a few seconds for advanced options
choose install update from external sd.
sassij said:
Thanks for the tip, I tried that and it wouldn't work. Do I need root or s-off?
Click to expand...
Click to collapse
No, the phone does not need to be modded to run the RUU. Its a "official" update/recovery tool provided by HTC. If you phone is stock, it should work, as the above response also indicated.
If it "wouldn't work" it would be more helpful to give details, if you want proper help. Not just say it didn't work. What step did it fail at , any error message, etc. Also, the current state of your phone (root, unlocked bootloader, etc.), as we can only assume based on your comment about root, etc.
RUU failing on a stock device is usually a USB connectivity issue on the part of your computer (not a problem on the phone's side). Install or re-install the HTC drives, try a different USB port, or a different computer (if available). If on Windows 8.1, that version is a known issue and will not work with the HTC drivers. You can also try re-downloading the RUU to make sure it wasn't damaged/corrupted during download.
Hi
I read most of the threads here before about the internal memory can't be mounted issue, but nothing seems to work for me. I can't even figure out which ruu I should download, bacause i bought my phone used and unlocked. I saw it somewhere in android that it was telus, but I downloaded tons of ruu-s and nothing works.
The issue started like 2 years ago and I tried everything I could find online and now my other phone broke I pulled the amaze out again to try to bring it back to life. I took a photo when the battery died and I believe it was using the internal memory that time.
All the info I can get is what it says in the bootloader because I relocked it.
I tried ADB, Linux, and the RUU way and maybe I do something wrong... thats why I ask for help here
The device is S-On hboot is 1.93.0002 so its ICS
I used it on Wind Mobile (Canada) network, but I believe it came from Bell
Also I have some more info from Image CRC, but thats hexa decimal that doesn't mean me anything
So something must be wrong with the partitions, but there's no way I can reach it and partition it again at the second.
If anyone can help me than please do it.
Also I'm not really a pro in Adb and linux and stuff like that. The adb commands don't seem to work, but the fastboot ones do. adb devices doesn't print any connected devices.
kiskisboki said:
Hi
I read most of the threads
If anyone can help me than please do it.
Click to expand...
Click to collapse
Start here:
http://forum.xda-developers.com/amaze-4g/help/qa-htc-unbricking-project-t2966472
pbergonzi said:
Start here:
http://forum.xda-developers.com/amaze-4g/help/qa-htc-unbricking-project-t2966472
Click to expand...
Click to collapse
Thanks. I read that page before, but didn't see the link to the actual thread, so the whole thing didn't make sense... now it does.
Anyways, I believe I have the Linux live cd that they suggested not to use so I stuck at the brickdetect part. Im trying tho