Related
I would like to install the AT&T OTA of 4.4.2 but have a custom recovery and am unable to upgrade. I am rooted with the stock 4.3 ROM and have the twrp recovery installed. I have S-ON. I've searched around trying to find a way to get this to work but can't seem to figure it out. I've tried looking around for an AT&T 4.3 stock recovery to try and flash it but can't seem to find one. The one from the Dev sticky page is not available for download. Can someone detail the steps I have to perform to get the 4.4.2 OTA from AT&T. Thanks in advance.
[SOLVED]
OK, problem fixed and 4.4.2 installed from OTA. I had relocked the bootloader on my phone so... start from scratch. Steps to resolve
1 - Unlock Bootloader
2 - Get S-Off on device (Makes everything easier). I used Firewater (http://firewater-soff.com)
3 - Flash the AT&T 3.17.502.3 (4.3) RUU from here (http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/). You may need a different one if not on AT&T
4 - Start phone, check for update. Let it download. Cake.
Now off to redo all the settings on my phone. Hope this helps someone else.
You can extract recovery.IMG from the ATT 4.4.2 OTA update if you can't find anything else.
sent from my mobile device
SaHiLzZ said:
You can extract recovery.IMG from the ATT 4.4.2 OTA update if you can't find anything else.
sent from my mobile device
Click to expand...
Click to collapse
Awesome, that's what I wanted to hear. I'm going to give that a shot. Thank you
Stock recoveries here: http://d-h.st/users/guich/?fld_id=29380#files
sent from my mobile device
SaHiLzZ said:
Stock recoveries here: http://d-h.st/users/guich/?fld_id=29380#files
sent from my mobile device
Click to expand...
Click to collapse
I flashed my recovery but recovery now just gets a read triangle with the exclamation
Let the phone download OTA and apply it
sent from my mobile device
SaHiLzZ said:
Let the phone download OTA and apply it
sent from my mobile device
Click to expand...
Click to collapse
Doing now.
It downloaded and attempted to install, then failed half way. Anything else I have to do before I update? Do I have to lock my bootloader again or unroot?
Sent from my HTC One using xda app-developers app
Yea lock bootloader
sent from my mobile device
No dice. Same deal.
Sent from my HTC One using xda app-developers app
Text/Photo of the error?
SaHiLzZ said:
Text/Photo of the error?
Click to expand...
Click to collapse
It doesn't give me an error. The OTA downloads, reboots and gets to a triangle with the green arrows inside and starts installing, then about 25% of the way it stops and goes to a red triangle. I'm thinking the MD5 to one of my files may be failing. I installed an edit to the framework sometime ago to get the hotspot working (that's the only change to the stock rom I've made). It doesn't really give me an error message though.
It could be the issue. You will need to choose one of the few options:
1. Restore a stock ATT OS for the same version you have (4.3) and update again
2. S-OFF (Preferred to avoid future messy bricks) and reinstall old ATT RUU and then upgrade all the way without custom rom/rooting/firmware changes
3. Wait for someone to post a custom rom install of the new ATT 4.4 update and install that.
SaHiLzZ said:
It could be the issue. You will need to choose one of the few options:
1. Restore a stock ATT OS for the same version you have (4.3) and update again
2. S-OFF (Preferred to avoid future messy bricks) and reinstall old ATT RUU and then upgrade all the way without custom rom/rooting/firmware changes
3. Wait for someone to post a custom rom install of the new ATT 4.4 update and install that.
Click to expand...
Click to collapse
Thanks, I appreciate your help. I think I'm gonna go with option 2, depending on how much time I have to do this, or 3 if time is an issue. Just one more question for you. Is firewater the best method to get S-Off or do you recommend a different one?
SMaximus7 said:
Thanks, I appreciate your help. I think I'm gonna go with option 2, depending on how much time I have to do this, or 3 if time is an issue. Just one more question for you. Is firewater the best method to get S-Off or do you recommend a different one?
Click to expand...
Click to collapse
If the ota stops on the second half as you discribe I think you have the wrong stock recovery. Different version than your "version-main"
mb_guy said:
If the ota stops on the second half as you discribe I think you have the wrong stock recovery. Different version than your "version-main"
Click to expand...
Click to collapse
I guess it can't hurt to try and reflash the recovery and retry. I'll give it a try.
SMaximus7 said:
I guess it can't hurt to try and reflash the recovery and retry. I'll give it a try.
Click to expand...
Click to collapse
I had the exact same thing occur, had a newer recovery than "fastboot getvar all"
mb_guy said:
I had the exact same thing occur, had a newer recovery than "fastboot getvar all"
Click to expand...
Click to collapse
It could be because I flashed the recovery that came with the OTA with fastboot and then after SaHiLzZ pointed me in the right direction was able to download the 4.3 recovery but flashed that one with flashify. I bet you the one I did with flashify didn't take. Funny thing is I also relocked my bootloader and now must unlock it again and that will probably wipe my device. What a mess, oh well, I hope that's all it is and at least I'm learning as I go.
SMaximus7 said:
It could be because I flashed the recovery that came with the OTA with fastboot and then after SaHiLzZ pointed me in the right direction was able to download the 4.3 recovery but flashed that one with flashify. I bet you the one I did with flashify didn't take. Funny thing is I also relocked my bootloader and now must unlock it again and that will probably wipe my device. What a mess, oh well, I hope that's all it is and at least I'm learning as I go.
Click to expand...
Click to collapse
Ya, I was lucky, had a nandroid . But you are right the recovery in the ota is too new.
Solved
OK, problem fixed and 4.4.2 installed from OTA. I had relocked the bootloader on my phone so... start from scratch. Steps to resolve
1 - Unlock Bootloader
2 - Get S-Off on device (Makes everything easier). I used Firewater (http://firewater-soff.com)
3 - Flash the AT&T 3.17.502.3 (4.3) RUU from here (http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/). You may need a different one if not on AT&T
4 - Start phone, check for update. Let it download. Cake.
Now off to redo all the settings on my phone. Hope this helps someone else. Thanks everybody for chiming in.
I've recently upgraded to ViperOne 5.8 from 3.5 (and prior to that 1.0) on a Sprint HTC One running TWRP 2.7.0.1. I've never updated the firmware, done an S-Off or an Hboot update. Does anyone have recommendations regarding firmware version, hboot version and s-off software that work well with my setup. Thanks in advance.
coctostan said:
I've recently upgraded to ViperOne 5.8 from 3.5 (and prior to that 1.0) on a Sprint HTC One running TWRP 2.7.0.1. I've never updated the firmware, done an S-Off or an Hboot update. Does anyone have recommendations regarding firmware version, hboot version and s-off software that work well with my setup. Thanks in advance.
Click to expand...
Click to collapse
I believe i understood you were s-off already. If so you could update your recovery to the latest 2.7.0.4b and i would update your firmware to the latest as well. As for hboot i flashed roots aroma hboot and worked perfectly.
slickrick54 said:
I believe i understood you were s-off already. If so you need to update your recovery to at least 2.6.3 and i would update your firmware to the latest. As for hboot i flashed roots aroma hboot and worked perfectly.
Click to expand...
Click to collapse
No, it is not s-off presently. I originally rooted it a year ago when new and installed ViperOne 1.0.
Do you know where I can find the latest firmware? Are you suggesting I downgrade TWRP from 2.7.0.1 to 2.6.3.0?
coctostan said:
No, it is not s-off presently. I originally rooted it a year ago when new and installed ViperOne 1.0.
Do you know where I can find the latest firmware? Are you suggesting I downgrade TWRP from 2.7.0.1 to 2.6.3.0?
Click to expand...
Click to collapse
No dont downgrade your recovery you will be ok there but you can update it if you want. Here is the link to the newest firmware bud http://forum.xda-developers.com/showthread.php?t=2687690. I would definitely recommend getting s-off though if i were you
slickrick54 said:
No dont downgrade your recovery you will be ok there but you can update it if you want. Here is the link to the newest firmware bud http://forum.xda-developers.com/showthread.php?t=2687690. I would definitely recommend getting s-off though if i were you
Click to expand...
Click to collapse
Anybody else have actual experience with a specific Firmware version that works nicely with ViperOne 5.8? My phone works well as it is but it I wouldn't mind getting more up to date performance.
coctostan said:
Anybody else have actual experience with a specific Firmware version that works nicely with ViperOne 5.8? My phone works well as it is but it I wouldn't mind getting more up to date performance.
Click to expand...
Click to collapse
Dude i've flashed every firmware update there was. The newest one would be the best for you but if not why not try them all then and find out which one works best for your phone. Here's the link to the newest one if you want http://forum.xda-developers.com/showthread.php?t=2687690. Also searching really helps out.
slickrick54 said:
Dude i've flashed every firmware update there was. The newest one would be the best for you but if not why not try them all then and find out which one works best for your phone. Here's the link to the newest one if you want http://forum.xda-developers.com/showthread.php?t=2687690. Also searching really helps out.
Click to expand...
Click to collapse
Much appreciated. So I flashed the latest firmware from that link and when ViperOne loads back up it keeps showing "Unfortunately Setup has Stopped". Did I do something incorrectly?
coctostan said:
Much appreciated. So I flashed the latest firmware from that link and when ViperOne loads back up it keeps showing "Unfortunately Setup has Stopped". Did I do something incorrectly?
Click to expand...
Click to collapse
To be honest with you i would back up your apps and data with titanium backup from the playstore and then just do a full wipe in twrp meaning system and data as well. Just dont erase internal storage. Then reflash the rom zip and everything will be fresh and new. Then restore everything with titanium.
PS: just to let you know viper one has been updated to sense 6.0 if you check there link again.
Unforunately, I can't seem to do that now. Neither TWRP or Philz will allow me to do anything. Did I overwrite the SuperSU app?
Hello!
I just bought this phone. I have the HTC One HKE. I bought yesterday, and today I rooted it. I had no reason to wait.
So I was wondering, currently I'm on the Viper ROM 2.4.0, and I thought it would increase the performance but it has rather slightly hampered it. I want one that will increase the performance of the phone, so which ROM would you recommend? Also, please do make a kernel recommendation that goes along with it, too.
I prefer staying with Sense 6.0.
Not sure how you "slightly hampered" the performance of your phone by flashing Viper, other than the fact the version of Viper you flashed is outdated. I'm running Viper 3.2.1 with MassStash's Hypernova kernel and my phone runs great. To each his own, though. "Best ROM/kernel" threads are subjective at best because what works well for one person may not work well for another.
Magnum_Enforcer said:
Not sure how you "slightly hampered" the performance of your phone by flashing Viper, other than the fact the version of Viper you flashed is outdated. I'm running Viper 3.2.1 with MassStash's Hypernova kernel and my phone runs great. To each his own, though. "Best ROM/kernel" threads are subjective at best because what works well for one person may not work well for another.
Click to expand...
Click to collapse
I'm very well aware that this my rom is outdated, but I cannot seem to be able to return to stock to update the firmware in order to install the latest versions. When I do, my WiFi does not work and that's a real problem.
Can anyone direct me to the correct thread that explains how I can do this? Note that I have tried updating the firmware in many different ways - through the command prompt, and using the generic RUU update with replacing the rom.zip file. I do not know what I need to do first, I just relocked the device and had a little panic attack because I couldn't do anything else. I had to unlock it again using the HTC dev code.
Can somebody please tell me what I need to do to get the latest firmware? I'm on the HK device with firmware version 2.16.654.4
Take a look at the thread linked below:
http://forum.xda-developers.com/showthread.php?t=2729173
I tried to do this, as I previously stated. I tried to do it over fastboot. I tried using Generic RUU. Each time I get an error. At first it was error 99, but then I relocked the bootloader and got error 12 (signature verification failed).
Would you mind posting a link to the RUU you attempted to use? We were actually having a discussion in another thread about some similar issues folks were having.
I tried them all.
I tried the HK version, the non-HK version. I tried the ones with boot.img and the ones without. I even tried to download the entire image (1.6GB) and flash it with the program and that did not work either. I tried them all, believe me. I would not let something like that (wrong version) get in the way.
I have:
cidnum: SPCS_004
version-main: 2.16.654.4
I even tried running the SuperCID command, and that didn't do anything.
You won't be able to get SuperCID while S-on. My suggestion at this point would be to unlock your bootloader again, flash a stock rooted ROM and then get S-off with the Sunshine exploit. You can then update your firmware without having to mess with any of the RUU or FUU stuff.
Where could I find a stack rooted ROM that matches my version?
I looked them all up in the other thread and most of their versions are 1.xxx while my mainver is 2.16.xx
Amer28 said:
Where could I find a stack rooted ROM that matches my version?
I looked them all up in the other thread and most of their versions are 1.xxx while my mainver is 2.16.xx
Click to expand...
Click to collapse
Post #3 under "Old Downloads":
http://themikmik.com/showthread.php?16276-SPRINT-ROM-BeyondStockᵀᴹ-v1-2-0-amp-Stock-Rooted
Okay. Right now, I am on stock rooted. I am not quite sure how to proceed with the update. I have been going to the menu, and checking for an update but it says that no update is availible at this time.
Do I try running the RUU, or just wait for it to arrive?
I should also tell you that I am still on TWRP and unlocked. Should relock and install stock recovery as well?
Amer28 said:
Okay. Right now, I am on stock rooted. I am not quite sure how to proceed with the update. I have been going to the menu, and checking for an update but it says that no update is availible at this time.
Do I try running the RUU, or just wait for it to arrive?
I should also tell you that I am still on TWRP and unlocked. Should relock and install stock recovery as well?
Click to expand...
Click to collapse
You can go one of two routes. Either S-off and manually update your firmware, or install the stock Android system recovery, which will allow you to take the update.
So, I did it.
I'm currently on the latest firmware, running the latest Venom too with the WiFi working. I have root access.
You told me earlier that I should do sunshine s-off. I was wondering, why is that? I already have everything I wanted. What is the benefit of S-OFF, when I already have root?
I don't want to sound ignorant, but I really don't know. I feel like a big noob right now.
Amer28 said:
So, I did it.
I'm currently on the latest firmware, running the latest Venom too with the WiFi working. I have root access.
You told me earlier that I should do sunshine s-off. I was wondering, why is that? I already have everything I wanted. What is the benefit of S-OFF, when I already have root?
I don't want to sound ignorant, but I really don't know. I feel like a big noob right now.
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showthread.php?t=1680928
in short, I have a playstore M7_UL that just won't switch to LTE after flashing a couple of lolipop based roms, I already tried messing around with the APN settings. stock roms such as this one (http://forum.xda-developers.com/showthread.php?t=2499452) will work properly with every single feature the phone should have if it was originally from T-Mobile, however I would Ideally like to update my phone to 12.
do you have any suggestions for this problem? or am I stuck with this 4.3 rom? I would like to thank you in advance for your time and consideration, and I wait eagerly for your response.
BNMotive said:
I've tried updating to several Lolipop roms, flashed 2 different radios as well as double checked APN settings and confirmed that my Sim card does support LTE however no luck, I've been having the issue of not being able to retain LTE support. only rom that worked completely was this one http://forum.xda-developers.com/showthread.php?t=2499452 the help would be greatly appreciated to resolve this nightmare.
my carrier is T-Mobile.
Click to expand...
Click to collapse
That is a very old ROM, have you updated your system to the latest Sense 6 firmware? If not, then you might want to run the latest TMOUS RUU. When completed, check to see if you have LTE. My guess you will, then if you want you can try one of the Lollipop ROM.
majmoz said:
That is a very old ROM, have you updated your system to the latest Sense 6 firmware? If not, then you might want to run the latest TMOUS RUU. When completed, check to see if you have LTE. My guess you will, then if you want you can try one of the Lollipop ROM.
Click to expand...
Click to collapse
this makes a ton of sense to me, so I decided to downloaded this RUU http://forum.xda-developers.com/htc-one-tmobile/general/ruu-t-mobile-htc-one-android-4-4-3-t2995420
I tried flashing it through my PC but I get this "Error [170] USB connection error" I read briefly over the code and there are some mentions of re-locking my phone, before I get deeper into this, do you have any suggestions for flashing the right RUU?
I really appreciate the help
BNMotive said:
this makes a ton of sense to me, so I decided to downloaded this RUU http://forum.xda-developers.com/htc-one-tmobile/general/ruu-t-mobile-htc-one-android-4-4-3-t2995420
I tried flashing it through my PC but I get this "Error [170] USB connection error" I read briefly over the code and there are some mentions of re-locking my phone, before I get deeper into this, do you have any suggestions for flashing the right RUU?
I really appreciate the help
Click to expand...
Click to collapse
Yes, if you are S-ON you need to re-lock your bootloader. You can use this command in bootloader/FASTBOOT USB:
Code:
fastboot oem lock
Your bootloader should say Relocked, leave the phone connected to the computer then run the RUU.
Utterly Clueless
majmoz said:
Yes, if you are S-ON you need to re-lock your bootloader. You can use this command in bootloader/FASTBOOT USB:
Code:
fastboot oem lock
Your bootloader should say Relocked, leave the phone connected to the computer then run the RUU.
Click to expand...
Click to collapse
Finding the "right" RUU was difficult but I got it "working" I flashed RUU: "RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250.20_10.40.1150.04_release_324846_signed" that had 4G, then I unlocked and rooted once more, unfortunately I am currently still stuck with CM12 in 3g/h+, so am I missing something? I thought that by flashing a stock Sense RUU and then updating to CM12 that would help me get what I needed for 4G, any advice is greatly appreciated.
BNMotive said:
Finding the "right" RUU was difficult but I got it "working" I flashed RUU: "RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250.20_10.40.1150.04_release_324846_signed" that had 4G, then I unlocked and rooted once more, unfortunately I am currently still stuck with CM12 in 3g/h+, so am I missing something? I thought that by flashing a stock Sense RUU and then updating to CM12 that would help me get what I needed for 4G, any advice is greatly appreciated.
Click to expand...
Click to collapse
I think you have a gross firmware - ROM mismatch. You are running version 1.XX firmware with a version 6.XX or 7.XX rom. You need to update your phone to at least version 6.XX and then see if CM12 will give you 4G. If you still have troubles with it in CM12 but not in the stock then it is CM12 that is the issue! These need to be done in order so that you don't brick your phone!!!
RUU 3.24.531.3
RUU 4.19.531.10
RUU 5.14.531.1
RUU 6.10.531.10
BNMotive said:
Finding the "right" RUU was difficult but I got it "working" I flashed RUU: "RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250.20_10.40.1150.04_release_324846_signed" that had 4G, then I unlocked and rooted once more, unfortunately I am currently still stuck with CM12 in 3g/h+, so am I missing something? I thought that by flashing a stock Sense RUU and then updating to CM12 that would help me get what I needed for 4G, any advice is greatly appreciated.
Click to expand...
Click to collapse
if you have a read through the CM12 thread or use the search feature within the thread itself, you will find that 4G / LTE is currently a problem for most users and in all not working, seem's to be a problem with 11 and 12 at the moment.
tried installing the first one, I get Error [155] "The ROM update utility cannot update your android phone. please get the correct ROM update utility and try again."
is there a way to give detailed information of my phone's firmware status? would that help? I thank you for the help.
BNMotive said:
tried installing the first one, I get Error [155] "The ROM update utility cannot update your android phone. please get the correct ROM update utility and try again."
is there a way to give detailed information of my phone's firmware status? would that help? I thank you for the help.
Click to expand...
Click to collapse
as you are s-on you will need to do the updates in order, therefore your next one you'll need will either be a 1.28.531.xx or 1.29.531.xx or even 2.24.531.xx, you need to do them in the correct order otherwise you'll just keep erroring out, easier to just s-off on your current firmware.
you cant jump from 1xxxxxx to 3xxxxxxx
Windows 8.1 proved to be a very bad choice to begin flashing old RUUs. USB drivers went rogue on me, so I decided to switch to an old beat up windows 7 system. worked like a charm, I was able to flash 1.2 and 3.2 things were looking up till tried 4.2, both windows 8.1 and 7 killed the installer, 7 says it is a USB error [171] while 8.1 says it is the wrong RUU. apparently I am not the only one with this issue, I'll see what I can find. I feel that thanks to your help guys I am getting real close, I can almost smell the sweet scent of fresh 4G lolipop brewing.
BNMotive said:
Windows 8.1 proved to be a very bad choice to begin flashing old RUUs. USB drivers went rogue on me, so I decided to switch to an old beat up windows 7 system. worked like a charm, I was able to flash 1.2 and 3.2 things were looking up till tried 4.2, both windows 8.1 and 7 killed the installer, 7 says it is a USB error [171] while 8.1 says it is the wrong RUU. apparently I am not the only one with this issue, I'll see what I can find. I feel that thanks to your help guys I am getting real close, I can almost smell the sweet scent of fresh 4G lolipop brewing.
Click to expand...
Click to collapse
Error 171 is a connection error, meaning the RUU can't connect to/find your phone, recheck your drivers with the phone booted and plugged into the computer and also recheck your drivers with the phone in the bootloader and plugged into your PC, I think you might find when its in the bootloader you have "One" with a yellow exclamation mark in device manager, you will have to manually force the driver, right click and select update driver, you the manual installation instructions, don't let windows search anything itself, it will fail.
have you also tried to just run the updates from your phone, ie settings - about - software updates ?
majmoz said:
Yes, if you are S-ON you need to re-lock your bootloader. You can use this command in bootloader/FASTBOOT USB:
Code:
fastboot oem lock
Your bootloader should say Relocked, leave the phone connected to the computer then run the RUU.
Click to expand...
Click to collapse
majmoz said:
I think you have a gross firmware - ROM mismatch. You are running version 1.XX firmware with a version 6.XX or 7.XX rom. You need to update your phone to at least version 6.XX and then see if CM12 will give you 4G. If you still have troubles with it in CM12 but not in the stock then it is CM12 that is the issue! These need to be done in order so that you don't brick your phone!!!
RUU 3.24.531.3
RUU 4.19.531.10
RUU 5.14.531.1
RUU 6.10.531.10
Click to expand...
Click to collapse
Seanie280672 said:
Error 171 is a connection error, meaning the RUU can't connect to/find your phone, recheck your drivers with the phone booted and plugged into the computer and also recheck your drivers with the phone in the bootloader and plugged into your PC, I think you might find when its in the bootloader you have "One" with a yellow exclamation mark in device manager, you will have to manually force the driver, right click and select update driver, you the manual installation instructions, don't let windows search anything itself, it will fail.
have you also tried to just run the updates from your phone, ie settings - about - software updates ?
Click to expand...
Click to collapse
after the first comment in this post yeah, I had installed a very early TMOUS RUU, from there it asked to be updated to Sense 6.0, I let it update and from there I flashed CM12 and I had no 4G. would something different happen if i try this again now that I flashed 1.2 and 3.2?
more info though, both computers do "update" the phone but get interrupted. regarding the "wrong" RUU error message from windows 8.1, it says "ERROR[158]: Image Error"
BNMotive said:
after the first comment in this post yeah, I had installed a very early TMOUS RUU, from there it asked to be updated to Sense 6.0, I let it update and from there I flashed CM12 and I had no 4G. would something different happen if i try this again now that I flashed 1.2 and 3.2?
more info though, both computers do "update" the phone but get interrupted. regarding the "wrong" RUU error message from windows 8.1, it says "ERROR[158]: Image Error"
Click to expand...
Click to collapse
Im sure I read through here somewhere ages ago about users having problems with the 4xxxxx update, have a search through this forum for T-Mobile RUU, it was in the main RUU thread, and im sure someone fixed it too.
http://forum.xda-developers.com/htc-one-tmobile
Hi,
I was in the process of flashing new firmware (iI have a thread for this when asking advice and followed the steps on my previous thread) I was flashing firmware 5.11.401.11 which loaded succesfully and rebooted to bootloader.
When it rebooted a driver message cam up I think regarding Qsub or something and the device has frozen or dead.
In the command window it says "wating for device"...i cant seem to get it to do anything!!
My device shows as other devices in my computerQHSUSB-DLOAD and the message I recall was about drivers ...do i need to update them?
Any help please?
Shepps
shepppster said:
Hi,
I was in the process of flashing new firmware (iI have a thread for this when asking advice and followed the steps on my previous thread) I was flashing firmware 5.11.401.11 which loaded succesfully and rebooted to bootloader.
When it rebooted a driver message cam up I think regarding Qsub or something and the device has frozen or dead.
In the command window it says "wating for device"...i cant seem to get it to do anything!!
My device shows as other devices in my computerQHSUSB-DLOAD and the message I recall was about drivers ...do i need to update them?
Any help please?
Shepps
Click to expand...
Click to collapse
Seem's like you may have skipped an important firmware update, which firmware number were you updating from?
If you skipped a firmware version e.g 3.xx.401.x to 5.xx.401.x then you will be needing the Unbrick project here http://forum.xda-developers.com/showthread.php?t=2770684
Danny201281 said:
Seem's like you may have skipped an important firmware update, which firmware number were you updating from?
If you skipped a firmware version e.g 3.xx.401.x to 5.xx.401.x then you will be needing the Unbrick project here http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
I did go consecutively fro 3-4-5 but..I guess It happens. The firmware seemed to flash ok.
I will try the link.
Thanks
shepppster said:
I did go consecutively fro 3-4-5 but..I guess It happens. The firmware seemed to flash ok.
I will try the link.
Thanks
Click to expand...
Click to collapse
Ok the unbricking has worked so far....can someone confirm the fastboot commands in Linux are the same as on a windows CMD prompt please?
I dont want to get this far and not flash the firmware properly.
Danny201281 said:
Seem's like you may have skipped an important firmware update, which firmware number were you updating from?
If you skipped a firmware version e.g 3.xx.401.x to 5.xx.401.x then you will be needing the Unbrick project here http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
Is there a guide on the forum for using Linux so i get the last part (Flashing firmware) perfect please?
shepppster said:
Is there a guide on the forum for using Linux so i get the last part (Flashing firmware) perfect please?
Click to expand...
Click to collapse
Fastboot works just the same in Linux as in Windows with the exception of you must use "sudo"
So
Code:
fastboot devices
becomes
Code:
sudo fastboot devices
Code:
fastboot flash zip firmware.zip
becomes
Code:
sudo fastboot flash zip firmware.zip
and so on if you forget to use sudo you will just see "waiting for device" in which case press ctrl+c to cancel and do command again with sudo :good:
shepppster said:
I did go consecutively fro 3-4-5 but..I guess It happens. The firmware seemed to flash ok.
I will try the link.
Thanks
Click to expand...
Click to collapse
What actually happened is when I was flashing from 4****** to 5***** when I tried to reboot to booloader my PC wanted to reinstall device drivers ,which I think I cancelled by mistake causing the hang up?
I have unbricked and now in bootloader waiting for the device to recharge fully.
I have then got to flash the 5****** series of firmware again(as instructed by the unbrick software).
I will then either install a custom recovery and flash my jellybean back-up or a custom ROM, do you think ARHD 84 will install on the 5***** firmware? I dont fancy going to 6**** until all is ok.
Or is there a way of flashing a stock o/s that can be flashed from TWRP? for the WWE firmware?
Shepps
shepppster said:
What actually happened is when I was flashing from 4****** to 5***** when I tried to reboot to booloader my PC wanted to reinstall device drivers ,which I think I cancelled by mistake causing the hang up?
I have unbricked and now in bootloader waiting for the device to recharge fully.
I have then got to flash the 5****** series of firmware again(as instructed by the unbrick software).
I will then either install a custom recovery and flash my jellybean back-up or a custom ROM, do you think ARHD 84 will install on the 5***** firmware? I dont fancy going to 6**** until all is ok.
Or is there a way of flashing a stock o/s that can be flashed from TWRP? for the WWE firmware?
Shepps
Click to expand...
Click to collapse
Ok I have unbricked my device and used TWRP to recover my back up....however after flashing up to 5******** firmware ,the firmware seems to have reverted back to the 2******* series I started with??? Is that correct?
If so I have to start all over again?
shepppster said:
Ok I have unbricked my device and used TWRP to recover my back up....however after flashing up to 5******** firmware ,the firmware seems to have reverted back to the 2******* series I started with??? Is that correct?
If so I have to start all over again?
Click to expand...
Click to collapse
no firmware does not revert back .. where are you getting these files ?
clsA said:
no firmware does not revert back .. where are you getting these files ?
Click to expand...
Click to collapse
This is the information from my phone the "about" section in settings. software number 2.24.161.1 i havent gone as far as a getvar cmd in fastboot yet,if thats where the correct info will be?
shepppster said:
This is the information from my phone the "about" section in settings. software number 2.24.161.1 i havent gone as far as a getvar cmd in fastboot yet,if thats where the correct info will be?
Click to expand...
Click to collapse
I see in the Unbrick Project Thread your device is fixed But for the record the Software Number in settings is the software number of the rom not the firmware :good: Glad to hear your back up though good job. :highfive:
Danny201281 said:
I see in the Unbrick Project Thread your device is fixed But for the record the Software Number in settings is the software number of the rom not the firmware :good: Glad to hear your back up though good job. :highfive:
Click to expand...
Click to collapse
Ah I thought it might be...all I need know is to move to 6**401 firmware so I can flash the latest ktkt roms (not lolipop) I was a bit of a mare but find it easier to my Ubuntu pc as I dont have to worry about drivers and the like.
Thanks Danny
shepppster said:
Ah I thought it might be...all I need know is to move to 6**401 firmware so I can flash the latest ktkt roms (not lolipop) I was a bit of a mare but find it easier to my Ubuntu pc as I dont have to worry about drivers and the like.
Thanks Danny
Click to expand...
Click to collapse
No Problem, And yeah i'm a Linux user myself and it is the shizzle when it comes to android phones
Danny201281 said:
No Problem, And yeah i'm a Linux user myself and it is the shizzle when it comes to android phones
Click to expand...
Click to collapse
I intend to carry on where I left off...I havent got as far a flashing the new rom.
The 401 firmware I am using is currently 5.11.401.10 ,next step is the 6 series.
Is it best to flash 6.09.401.5 then 401.10,401.11,401.12 consecutively or jump straight to 12?(clearly I dont want to go through the bricking stuff again!!)
Is there a link to a good source of firmware,i looked on the Vomer guide but they are decribed as the dual simHTC one at the download page, is this going to be an issue as I will get them from there as a reliably good source?
http://forum.xda-developers.com/showthread.php?t=2365506
shepppster said:
I intend to carry on where I left off...I havent got as far a flashing the new rom.
The 401 firmware I am using is currently 5.11.401.10 ,next step is the 6 series.
Is it best to flash 6.09.401.5 then 401.10,401.11,401.12 consecutively or jump straight to 12?(clearly I dont want to go through the bricking stuff again!!)
Is there a link to a good source of firmware,i looked on the Vomer guide but they are decribed as the dual simHTC one at the download page, is this going to be an issue as I will get them from there as a reliably good source?
http://forum.xda-developers.com/showthread.php?t=2365506
Click to expand...
Click to collapse
I know that some have jumped strait to the latest without any problems and the theory goes as Lon as you don't skip a version number e.g 3.xx to 5.xx then it should be safe.
Obviously the safest option is to flash each update so you know your not missing anything important. As for a good source I prefer to stick with HTC signed firmware from official OTA updates all of which you can find here http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
Danny201281 said:
I know that some have jumped strait to the latest without any problems and the theory goes as Lon as you don't skip a version number e.g 3.xx to 5.xx then it should be safe.
Obviously the safest option is to flash each update so you know your not missing anything important. As for a good source I prefer to stick with HTC signed firmware from official OTA updates all of which you can find here http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
Click to expand...
Click to collapse
@Danny201281 and @clsA Thanks for all your help...successfully flashed up to the latest 6******** firmware and flashed a custom rom.
Perhaps minscule to u guys but massive step forward for me !
Few nailbiting moments anticipating a brick again..but it worked fine using Ubuntu which is much less finicky than windows to use and my weapon of choice from now on!
:good::good: