Related
I think the answer is no, but I wanted to confirm that.
Cozume said:
I think the answer is no, but I wanted to confirm that.
Click to expand...
Click to collapse
It work for my T-Mobile version.
sent via Le Motonovo X
eksasol said:
It work for my T-Mobile version.
Click to expand...
Click to collapse
Interesting, thanks!
It looks like the stock recovery in 4.4.2 is identical to the one in 4.4. I flashed the stock recovery img from the 4.4 SBF that I got directly from Motorola. I wrote down the version number showing when I booted into stock recovery. Then I installed the 4.4.2 OTA update, rebooted the phone and went back into stock recovery and the version number was the same as it was when I was on 4.4.
GrillMouster said:
It looks like the stock recovery in 4.4.2 is identical to the one in 4.4. I flashed the stock recovery img from the 4.4 SBF that I got directly from Motorola. I wrote down the version number showing when I booted into stock recovery. Then I installed the 4.4.2 OTA update, rebooted the phone and went back into stock recovery and the version number was the same as it was when I was on 4.4.
Click to expand...
Click to collapse
I'm trying to figure out how one actually flashes the stock recovery so that I can complete the update to 4.4.2. You're saying just extract the img from the official firmware zip and then flash it over in 'download' mode or something, right?
ED: Figured it out but thanks anyway!
LastSilmaril said:
I'm trying to figure out how one actually flashes the stock recovery so that I can complete the update to 4.4.2. You're saying just extract the img from the official firmware zip and then flash it over in 'download' mode or something, right?
ED: Figured it out but thanks anyway!
Click to expand...
Click to collapse
Can you post the steps on how your figured it out?? Thanks!
im not sure what u are trying to do are you trying to update to 4.4.2
if so find the SBF package and install it with RSD Lite
or find the OTA .zip and install it via stock recovery and it will update.
Hi All,
I have an ATT m7 that I'm running on GPE 4.4 (build KTR16S) with TWRP and the bulletproof kernel.
I'm getting notifications for the 4.4.2 update, and I'd like to install it, but obviously with TWRP installed, it can't automate the update process. So, a few questions:
1) Is it okay for me to manually install the update after locating it from my own recovery?
2) Where is the update stored, so that I can track it down within TWRP to flash?
Thanks guys!
karankshah said:
Hi All,
I have an ATT m7 that I'm running on GPE 4.4 (build KTR16S) with TWRP and the bulletproof kernel.
I'm getting notifications for the 4.4.2 update, and I'd like to install it, but obviously with TWRP installed, it can't automate the update process. So, a few questions:
1) Is it okay for me to manually install the update after locating it from my own recovery?
2) Where is the update stored, so that I can track it down within TWRP to flash?
Thanks guys!
Click to expand...
Click to collapse
Mines in the downloads folder
karankshah said:
Hi All,
I have an ATT m7 that I'm running on GPE 4.4 (build KTR16S) with TWRP and the bulletproof kernel.
I'm getting notifications for the 4.4.2 update, and I'd like to install it, but obviously with TWRP installed, it can't automate the update process. So, a few questions:
1) Is it okay for me to manually install the update after locating it from my own recovery?
2) Where is the update stored, so that I can track it down within TWRP to flash?
Thanks guys!
Click to expand...
Click to collapse
you can't flash ota updates with twrp. only stock recovery. like mb_guy said, the ota are stored in the ''downloads'' folder. When you apply the ota, the file is deleted automatically.
You can manually flash ota updates from stock recovery. Move the ota.zip to android/obb. boot phone in stock recovery, select ''apply from phone storage'' ---> /obb --> your ota.zip
For some reason the update is in the /cache/ directory instead of in the downloads directory.
How do I switch to the standard recovery? Do I need to reflash the entire ROM or is there another flashable file?
karankshah said:
For some reason the update is in the /cache/ directory instead of in the downloads directory.
How do I switch to the standard recovery? Do I need to reflash the entire ROM or is there another flashable file?
Click to expand...
Click to collapse
you can flash stock recovery the same way you flashed custom recovery:
Code:
fastboot flash recovery name_of_recovery.img
you must flash the stock recovery that match your firmware version which you can find with a:
Code:
fastboot getvar all
karankshah said:
For some reason the update is in the /cache/ directory instead of in the downloads directory.
How do I switch to the standard recovery? Do I need to reflash the entire ROM or is there another flashable file?
Click to expand...
Click to collapse
Stock recovery from here
http://forum.xda-developers.com/showthread.php?t=2545227
bored_stupid said:
Stock recovery from here
http://forum.xda-developers.com/showthread.php?t=2545227
Click to expand...
Click to collapse
Thanks for the help guys. I spent way too long trying to figure out how to get my computer to recognize my phone while in fastboot so I could get the main version number.
I finally was able to figure that out, but I'm not seeing my version (1.26.502.10) on the page.
Are any of the other recoveries usable? Or does this mean that I would have to go back to stock ATT, take the OTA update ATT was pushing a loong time ago, and then re-root to then flash a GE rom?
karankshah said:
Thanks for the help guys. I spent way too long trying to figure out how to get my computer to recognize my phone while in fastboot so I could get the main version number.
I finally was able to figure that out, but I'm not seeing my version (1.26.502.10) on the page.
Are any of the other recoveries usable? Or does this mean that I would have to go back to stock ATT, take the OTA update ATT was pushing a loong time ago, and then re-root to then flash a GE rom?
Click to expand...
Click to collapse
There is a rom dump here. once downloaded, you should be able to extract the stock recovery from there.
http://forum.xda-developers.com/showthread.php?p=40764389&highlight=1+26+502+10#post40764389
bored_stupid said:
There is a rom dump here. once downloaded, you should be able to extract the stock recovery from there.
http://forum.xda-developers.com/showthread.php?p=40764389&highlight=1+26+502+10#post40764389
Click to expand...
Click to collapse
It looks like he's pulled the 1.26.502.10 rom - know of any other places it might be? Most of the 502.10 roms I'm seeing now are pre-rooted.
karankshah said:
It looks like he's pulled the 1.26.502.10 rom - know of any other places it might be? Most of the 502.10 roms I'm seeing now are pre-rooted.
Click to expand...
Click to collapse
I can only find pre-rooted roms two. however, if the rom has the SuperSU installed, you can do a full unroot from the SuperSU settings
bored_stupid said:
I can only find pre-rooted roms two. however, if the rom has the SuperSU installed, you can do a full unroot from the SuperSU settings
Click to expand...
Click to collapse
That might be a good idea. Do you know if that removes S-OFF?
bored_stupid said:
I can only find pre-rooted roms two. however, if the rom has the SuperSU installed, you can do a full unroot from the SuperSU settings
Click to expand...
Click to collapse
Ah - nevermind - just found out it won't reinstall the stock recovery, which means the OTA update won't stick anyway. Looks like the only way is the long way.
karankshah said:
Ah - nevermind - just found out it won't reinstall the stock recovery, which means the OTA update won't stick anyway. Looks like the only way is the long way.
Click to expand...
Click to collapse
If you unzip the OTA the stock recovery should be in there..
Sent from my GT-I9505 using XDA Premium 4 mobile app
karankshah said:
Thanks for the help guys. I spent way too long trying to figure out how to get my computer to recognize my phone while in fastboot so I could get the main version number.
I finally was able to figure that out, but I'm not seeing my version (1.26.502.10) on the page.
Are any of the other recoveries usable? Or does this mean that I would have to go back to stock ATT, take the OTA update ATT was pushing a loong time ago, and then re-root to then flash a GE rom?
Click to expand...
Click to collapse
Here is your stock recovery
http://www.androidfilehost.com/?fid=23501681358538645
I was trying to flash a new ROM (Viper One) and followed the instructions to update the firmware. I got as far as getting into the fastboot and relocking the device so I could update the firmware to the latest version (per the instructions). I tried to no avail to unlock the bootloader and came across a thread saying I need to have a stock kernel to unlock the bootloader again. What I didnt count on was that the previous custom kernel was still loaded on the device even though I did a factory reset (again per instructions). I have searched for a stock 4.3 kernel but cant find one so I can finish this.
Ideas?
Thanks so much, in advance!
Sheik_Yerbutay said:
I was trying to flash a new ROM (Viper One) and followed the instructions to update the firmware. I got as far as getting into the fastboot and relocking the device so I could update the firmware to the latest version (per the instructions). I tried to no avail to unlock the bootloader and came across a thread saying I need to have a stock kernel to unlock the bootloader again. What I didnt count on was that the previous custom kernel was still loaded on the device even though I did a factory reset (again per instructions). I have searched for a stock 4.3 kernel but cant find one so I can finish this.
Ideas?
Thanks so much, in advance!
Click to expand...
Click to collapse
You can find the Stock Kernel here.
StormyNight said:
You can find the Stock Kernel here.
Click to expand...
Click to collapse
Thanks!
I was able to get my phone back to where it was before (viperOne ROM thats running v 4.1.2 and Sense 5.0). I am trying to get this back to stock before I take to Sprint to replace the phone for the purple camera bug.
I guess what Im looking for is the stock kernel for v4.1.2 so I can then flash it and take it in. The one you had linked to was for v4.4.x and will not work.
Thanks in advance!
Sheik_Yerbutay said:
Thanks!
I was able to get my phone back to where it was before (viperOne ROM thats running v 4.1.2 and Sense 5.0). I am trying to get this back to stock before I take to Sprint to replace the phone for the purple camera bug.
I guess what Im looking for is the stock kernel for v4.1.2 so I can then flash it and take it in. The one you had linked to was for v4.4.x and will not work.
Thanks in advance!
Click to expand...
Click to collapse
Since, I don't know which version you are looking for you can pull the kernel out of the firmware for that version. You can check this site: http://forum.xda-developers.com/showthread.php?t=2576995 or this one: http://forum.xda-developers.com/showthread.php?t=2658910.
Please help I unlocked and loaded twrp. Then I flashed the latest Bad Boys Rom 4.4.3 and now I am stuck at the HTC screen. I can't get it to do anything. I have read and tried for hours to RUU or find some way to get a ROM to boot. I am lost...any help much appreciated!
kpahl1973 said:
Please help I unlocked and loaded twrp. Then I flashed the latest Bad Boys Rom 4.4.3 and now I am stuck at the HTC screen. I can't get it to do anything. I have read and tried for hours to RUU or find some way to get a ROM to boot. I am lost...any help much appreciated!
Click to expand...
Click to collapse
Did you fastboot flash the boot image?
What firmware are you on?
Which version of TWRP did you flash?
Captain_Throwback said:
Did you fastboot flash the boot image?
What firmware are you on?
Which version of TWRP did you flash?
Click to expand...
Click to collapse
I used the One_M8_ALL-in -One-Kit_v to get root and to flash trwp 2.7.0.2. I didn't mess with the firmware but I know I was on 4.4.2 and it wanted to take the update but I didn't allow it. I flashed Bad Boyz 4.4.3 latest version...And I do feel dumb for doing that. Wasnt thinking. NOw I am stuck on the white htc screen and cant even get it off by holding the power down button.
kpahl1973 said:
I used the One_M8_ALL-in -One-Kit_v to get root and to flash trwp 2.7.0.2. I didn't mess with the firmware but I know I was on 4.4.2 and it wanted to take the update but I didn't allow it. I flashed Bad Boyz 4.4.3 latest version...And I do feel dumb for doing that. Wasnt thinking. NOw I am stuck on the white htc screen and cant even get it off by holding the power down button.
Click to expand...
Click to collapse
Ok I was just able to get it back to the bootloader and recovery. Thats a positive step. So what do I need to run? I am not S OFF and dont have a rom loaded at the moment. Any help appreciated. I dont want to mess it up any more than I have.
kpahl1973 said:
Ok I was just able to get it back to the bootloader and recovery. Thats a positive step. So what do I need to run? I am not S OFF and dont have a rom loaded at the moment. Any help appreciated. I dont want to mess it up any more than I have.
Click to expand...
Click to collapse
Does anyone have an old 4.4.2 rom I can load to get me going? I know I need to s off and right now I need to get my phone up and running for work and need an older rom that works with current firmware. Thanks so much for any help. I am dead in the water at the moment.
kpahl1973 said:
Does anyone have an old 4.4.2 rom I can load to get me going? I know I need to s off and right now I need to get my phone up and running for work and need an older rom that works with current firmware. Thanks so much for any help. I am dead in the water at the moment.
Click to expand...
Click to collapse
http://themikmik.com/showthread.php...L-Stock-Rooted-Base-2-16-651-4-(Android-4-4-3)
Don't forget to fastboot flash the boot image, and you'll need to download SuperSU and flash the zip after you flash the ROM for it to boot up completely.
Captain_Throwback said:
http://themikmik.com/showthread.php...L-Stock-Rooted-Base-2-16-651-4-(Android-4-4-3)
Don't forget to fastboot flash the boot image, and you'll need to download SuperSU and flash the zip after you flash the ROM for it to boot up completely.
Click to expand...
Click to collapse
Thanks Captain...how do you fastboot flash a .zip file? never done that before...I have flashed a image file but not a zip. I have downloaded your rom and waiting to make sure I flash your 0P6BIMG_m8whl_2.16.651.4_boot_kexec-hardboot_patched.zip correctly before moving forward. Also will any SuperSU zip file work on the phone?
kpahl1973 said:
Thanks Captain...how do you fastboot flash a .zip file? never done that before...I have flashed a image file but not a zip. I have downloaded your rom and waiting to make sure I flash your 0P6BIMG_m8whl_2.16.651.4_boot_kexec-hardboot_patched.zip correctly before moving forward. Also will any SuperSU zip file work on the phone?
Click to expand...
Click to collapse
Click the second link in my sig & scroll down to the section on S-on kernel flashing.
As far as SuperSU, you'll find it in the link below.
http://forum.xda-developers.com/showthread.php?t=1538053
kpahl1973 said:
Thanks Captain...how do you fastboot flash a .zip file? never done that before...I have flashed a image file but not a zip. I have downloaded your rom and waiting to make sure I flash your 0P6BIMG_m8whl_2.16.651.4_boot_kexec-hardboot_patched.zip correctly before moving forward. Also will any SuperSU zip file work on the phone?
Click to expand...
Click to collapse
You don't need that zip file. Just extract to boot.img from the ROM zip. The zip file is specifically for MultiROM support.
Captain_Throwback said:
You don't need that zip file. Just extract to boot.img from the ROM zip. The zip file is specifically for MultiROM support.
Click to expand...
Click to collapse
Ok I flashed the boot.img from the rom I downloaded which was M8WHL 2.16.651.4 Stock Rooted - Deodex and then I flashed the rom. I then flashed the latest SuperSU and rebooted and I am still stuck at the htc screen...did I do something wrong? I was careful to follow step by step with the instructions.
kpahl1973 said:
Ok I flashed the boot.img from the rom I downloaded which was M8WHL 2.16.651.4 Stock Rooted - Deodex and then I flashed the rom. I then flashed the latest SuperSU and rebooted and I am still stuck at the htc screen...did I do something wrong? I was careful to follow step by step with the instructions.
Click to expand...
Click to collapse
I thought you wanted to flash an older base ROM? If so, you wanted to choose a 1.xx base ROM from the thread. Perhaps that's your issue.
Captain_Throwback said:
I thought you wanted to flash an older base ROM? If so, you wanted to choose a 1.xx base ROM from the thread. Perhaps that's your issue.
Click to expand...
Click to collapse
Yes I did to get it going. What would I have to do to get the 2.xx rom going? Or do I need to just get it running first on the old version? I really do appreciate all the help! I really just want my phone to work and its so frustrating. I am downloading the older version now and will try that with the boot.img and supersu as well.
kpahl1973 said:
Yes I did to get it going. What would I have to do to get the 2.xx rom going? Or do I need to just get it running first on the old version? I really do appreciate all the help! I really just want my phone to work and its so frustrating. I am downloading the older version now and will try that with the boot.img and supersu as well.
Click to expand...
Click to collapse
Flashing the 2.xx base ROM requires updating your firmware. You needed an older stock ROM so you could S-OFF and do update it, correct? I thought that was the original issue?
Captain_Throwback said:
Flashing the 2.xx base ROM requires updating your firmware. You needed an older stock ROM so you could S-OFF and do update it, correct? I thought that was the original issue?
Click to expand...
Click to collapse
Yes you are correct. I got ahead of myself. I am downloading the older stock now and hopefully can get that running and then will attempt to s off and put this behind me. Believe it or not I have rooted the evo, lte, one7 and now first time messed up with the m8. You would think I would know a little more and not have made these mistakes. Oh well...with luck this will work and I appreciate all the help!
kpahl1973 said:
Yes you are correct. I got ahead of myself. I am downloading the older stock now and hopefully can get that running and then will attempt to s off and put this behind me. Believe it or not I have rooted the evo, lte, one7 and now first time messed up with the m8. You would think I would know a little more and not have made these mistakes. Oh well...with luck this will work and I appreciate all the help!
Click to expand...
Click to collapse
Thanks for all the help! I am back up and running. I will S off and update.
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: