Hi All,
I have a UK HTC One M8, rooted, S-off, and with ViperOne installed, an old version - 1.8.0
I have flashed a new firmware in order to update ViperOne, and I have lost root access. I used root checker app to verify.
I used this method to flash the firmware:http://forum.xda-developers.com/showthread.php?t=2696282
I obtained the firmware from here: http://android-revolution-hd.blogspot.co.uk/p/android-revolution-hd-mirror-site-var.html
I had changed the cid to supercid, as I am S-off, and i checked that the modelid was correct in "android-info.txt"
The flash went fine, no errors, phone turned on first time, but root access is lost.
This thread I just found says that upgrading the firmware will always cause you to lose root. This is surprising as it wasn't mentioned in any of the guides I read to flashing firmware.
http://forum.xda-developers.com/showthread.php?t=2417442
I was wondering if somebody knowledgeable could reassure me that everything is fine, and perhaps point me to the most appropriate method for getting root access back. I am a little out of my depth here, I learned how to do most of this stuff a year ago when i first rooted, but I haven't been back to update since then, and have forgotten a lot of what I learned before.
Would appreciate any assistance you can offer
Cheers
Will
Willr01 said:
This thread I just found says that upgrading the firmware will always cause you to lose root. This is surprising as it wasn't mentioned in any of the guides I read to flashing firmware.
http://forum.xda-developers.com/showthread.php?t=2417442
Click to expand...
Click to collapse
Different device manufacturers do things in very different ways, so I wouldn't take that thread to mean anything, one way or another, regarding losing root when updating firmware. I also think in that thread, they may be talking about firmware = ROM (as opposed to something very different on HTC devices). In which case, yes, installing a stock ROM will in fact usually remove root on most Android devices.
In any case, see if you still have TWRP installed. That depends on whether the firmware package was modified or not to remove the stock recovery. If TWRP was replaced by stock recovery, simply install TWRP again using your method of choice (personally I prefer installing by fastboot). Then download the SuperSU zip to your phone from here and flash in TWRP.
In reality, I think you may not even have to download SuperSU. If you boot into TWRP and select reboot, I believe TWRP will automatically sense your ROM is not rooted, and ask you if you want it to do so. But I'm not 100% on that, and the SuperSU method is a sure thing.
Thanks a lot for your input. I don't have a recovery installed, so I have tried to flash twrp.
I tried flashing it twice, after reading it can be necessary to do that, and erasing the cache before attempting to boot to recovery. When I try and enter recovery, I get stuck on the startup htc screen with "Entering Recovery..." in pink.
Snippets off other threads have suggested my hboot might not be compatible with the new version of twrp. Is it straightforward to update hboot?
Thanks in advance
Willr01 said:
Snippets off other threads have suggested my hboot might not be compatible with the new version of twrp. Is it straightforward to update hboot?
Click to expand...
Click to collapse
Updating your firmware updates the hboot. 3.19 is the current hboot, and you can check no the bootloader screen.
Make sure its a current version TWRP (2.8.7.0) and I think the opposite is also true (old versions of TWRP don't work with current hboot).
And to clarify, you want to fastboot erase cache, then flash TWRP; as this often clears up issues with TWRP not installing properly.
redpoint73 said:
Updating your firmware updates the hboot. 3.19 is the current hboot, and you can check no the bootloader screen.
Make sure its a current version TWRP (2.8.7.0) and I think the opposite is also true (old versions of TWRP don't work with current hboot).
And to clarify, you want to fastboot erase cache, then flash TWRP; as this often clears up issues with TWRP not installing properly.
Click to expand...
Click to collapse
So my hboot is 3.16, and the twrp was the latest version. I guess i need to find a more up to date firmware file. Any suggestions as to the best sources for firmware?
Willr01 said:
So my hboot is 3.16, and the twrp was the latest version. I guess i need to find a more up to date firmware file. Any suggestions as to the best sources for firmware?
Click to expand...
Click to collapse
What exactly did you flash from the Android Revolution website (what you linked in the top post)?
That website has up-to-date firmware, but what you want is 4.xx version firmware, found under the "Firmware collection" link on that webpage.
Since your hboot number is 3.16, you either did not properly flash a firmware (flashed something else) or flashed a really old firmware (hboot 3.16 corresponds to firmware version 1.xx).
Related
My M8 is flashed with Viper 1.6. I however wish to use latest firmware from the official OTA update, to get the newest radio etc. I am however unable to flash this.
I flashed the stock recovery, however the update does not succeed via fastboot. Error 99 something.
Are you able to guide me how to do this update. Is it at all possible, when not running a stock rom?
I would like to avoid going back to stock, to be able to do this, unless necessary, but I do not know if this is possible.
My former phone was a Samsung Note, where I was able to flash about everything with the Odin Flash utility. Is it simply because I am S-ON This causes problems?
In the Viper thread this has been asked, but no clear answers are given, as it is not viper specific.
[/COLOR]
sblop said:
My M8 is flashed with Viper 1.6. I however wish to use latest firmware from the official OTA update, to get the newest radio etc. I am however unable to flash this.
I flashed the stock recovery, however the update does not succeed via fastboot. Error 99 something.
Are you able to guide me how to do this update. Is it at all possible, when not running a stock rom?
I would like to avoid going back to stock, to be able to do this, unless necessary, but I do not know if this is possible.
My former phone was a Samsung Note, where I was able to flash about everything with the Odin Flash utility. Is it simply because I am S-ON This causes problems?
In the Viper thread this has been asked, but no clear answers are given, as it is not viper specific.
Click to expand...
Click to collapse
First of all make it clear what you want to do.If you want to do OTA of viper from 1.6 to 1.7 you must have a custom recovery like twrp then go to settings->about->software updates.If you want to get official HTC's OTA then you have to be on Stock.you sshould follow this guide http://forum.xda-developers.com/showthread.php?t=2735235
sblop said:
My M8 is flashed with Viper 1.6. I however wish to use latest firmware from the official OTA update, to get the newest radio etc. I am however unable to flash this.
I flashed the stock recovery, however the update does not succeed via fastboot. Error 99 something.
Are you able to guide me how to do this update. Is it at all possible, when not running a stock rom?
I would like to avoid going back to stock, to be able to do this, unless necessary, but I do not know if this is possible.
My former phone was a Samsung Note, where I was able to flash about everything with the Odin Flash utility. Is it simply because I am S-ON This causes problems?
In the Viper thread this has been asked, but no clear answers are given, as it is not viper specific.
Click to expand...
Click to collapse
You need to be S-OFF to flash firmware. You would need to go back to stock and apply the OTA, however, you can flash the radio while S-ON.
Thanks for your replies.
I of cause know I am unable to directly install the OTA.
I am interested in the radio and other relevant parts of the OTA.
Is the best solution to revert to a locked bootloader/Stock recovery, and simply update?
The radio itself I assume I can flash with fastboot. (fastboot flash radio radio.img)
The firmware however also contains the following files
Boot.img
Hboot
Radio
RCData
Recovery.
I am unaware what RC data is? Recovery is not relevant. Hboot, I assume an older version is better, in case a weakness is found in the old version, leaving boot and radio. Would you update boot? Do I gain anything at all? If yes, I assume I can use this command? (fastboot flash boot boot.img). Or am I restricted flashing the boot, as long as I am S-on?
bump
So I got an M8 recently, unlocked bootloader with HTCDev and flashed a rom without upgrading the firmware, so later I restored my stock backup and downloaded the OTA update which was for 2.22.401.5. But my recovery wasn't stock so it wouldn't flash then long story short I soft bricked and did a factory reset from hboot.
So now I flashed stock recovery but since I factory reset my original backup was gone, and for some reason Wi-Fi does not turn on at all after I did the factory reset. I downloaded a TWRP backup from here http://forum.xda-developers.com/showthread.php?t=2710735 (The Telus one, I am with Telus) and when I go to download the OTA update it gives me the option to download and install 1.55.661.4 instead of the more recent version.
I am S-On and I have read that flashing an RUU for a firmware older than yours will hard brick your phone and I definitely don't want that, so what I'm asking is can I download and install this 1.55.661.4 OTA then install a more recent one afterwards or will that brick my phone? And if so how should I go about updating firmware?
Thanks
FormaldehydeSon said:
So now I flashed stock recovery but since I factory reset my original backup was gone, and for some reason Wi-Fi does not turn on at all after I did the factory reset.
Click to expand...
Click to collapse
Factory reset (wipe data, Dalvik and cached) by definition does not delete internal storage where nandroids are stored. Either you specifically went into TWRP Advanced Wipe settings and wiped storage (which wasn't necessary) or you did a factory reset in bootloader which on a modded phone may corrupt internal storage.
WiFi not working is a known issue with outdated firmware + 2.22 Sense ROM. So updated firmware will fix this.
FormaldehydeSon said:
I am S-On and I have read that flashing an RUU for a firmware older than yours will hard brick your phone
Click to expand...
Click to collapse
This is not correct. With S-on, flashing an older RUU will flash (version check will fail). With S-off, it will not brick the phone, and will actually work correctly (re-image the phone to the older RUU).
But its not clear to me whether your phone even has firmware/software that is "newer" than the RUU or OTA you are referring to. If the hboot and radio was never changed, and the ROM and recovery were returned to the "older" version, then nothing is in fact "newer" anymore.
RUU is actually a safer proposition than OTA in my opinion. But do you know for fact that an RUU exists for your version (not many versions do)?
OTAs with S-on, should work, but do you know for a fact that everything on the phone (ROM, recovery, hboot, radio, etc.) is now restored (or never changed) to whatever software number directly preceding 1.55? If not, with S-on the OTA will fail version check and not install. Further, if OTA is not installed in sequence, this actually is a brick risk (in contrast with RUU). Although the last part is probably only possible with s-off.
Thanks for the reply, how can I check the version of my recovery to make sure it matches my rom version number? I am using recovery downloaded from here http://forum.xda-developers.com/showpost.php?p=52734619&postcount=14 but the recovery doesn't mention a version number. Is it safe to assume that the recovery and nandroid backup linked in that post are for the same version, since they both came from the same person's backup?
In phone settings it shows my software version number as 1.12.661.17, and in hboot my radio is 1.16.2133156, hboot version is 3.16, but am I correct in assuming that my radio or hboot versions could not have changed, since I don't have s-off and haven't flashed anything other than the recovery and TWRP backup in the linked post? Do these version numbers match up properly for me to try downloading the OTA? Thanks again
FormaldehydeSon said:
Thanks for the reply, how can I check the version of my recovery to make sure it matches my rom version number? I am using recovery downloaded from here http://forum.xda-developers.com/showpost.php?p=52734619&postcount=14 but the recovery doesn't mention a version number.
In phone settings it shows my software version number as 1.12.661.17, and in hboot my radio is 1.16.2133156, hboot version is 3.16, but am I correct in assuming that my radio or hboot versions could not have changed, since I don't have s-off and haven't flashed anything other than the recovery and TWRP backup in the linked post? Do these version numbers match up properly for me to try downloading the OTA? Thanks again
Click to expand...
Click to collapse
I don't know how else to confirm recovery. But if you used the nandroid from that same post, its probably safe to assume they go together.
You are right that with S-on, you can't have modified hboot or radio. So if you haven't gotten any OTAs, and you were originally on 1.12 when you got the phone, those should be okay.
In this instance S-on is kind of a good thing. If the OTA finds anything amiss, it will just fail whatever security check and fail to install. Although S-on is the whole reason you're at this point in the first place.
I was able to install the OTA without problem, as well as download and install the 2.23 OTA, thanks for all your help!
I got the bootloader unlocked. I flashed TWRP. I installed SuperSu. Now after wiping and installing a new ROM, I can no longer get passed the HTC logo at all. I have tried multiple ROMs including Eragon ROM, Skydragon, and Viper. I really have no idea what to do at this point. Please help. If you need more info just ask. I am able to get into bootloader and TWRP but nothing I have tried has worked. This is the AT&T variant.
Edit: I've also just tried using a different recovery as well (Philz).. no luck.
the only time i had this happening with the M8 was when i forgot to do a full wipe before flashing, then got stuck with the logo. Are you absolutely sure you're performing a full wipe prior to flashing (daft Q i know).
Maybe it's something to do with TWRP? I'm using PhilZ Touch (simply because that it was recommended on the skydragon thread).
Can you restore the original ROM from a backup?
westy123 said:
the only time i had this happening with the M8 was when i forgot to do a full wipe before flashing, then got stuck with the logo. Are you absolutely sure you're performing a full wipe prior to flashing (daft Q i know).
Maybe it's something to do with TWRP? I'm using PhilZ Touch (simply because that it was recommended on the skydragon thread).
Can you restore the original ROM from a backup?
Click to expand...
Click to collapse
Yes I am doing a full wipe before install. This is incredibly stupid of me and you can all make fun of me for it but I didn't have a backup. I am coming off of an M7 and never had issues with it so I figured it was fine. Guess I was wrong. . I thought it came with a backup stock but there is not one.
What's your hboot no. on the bootloader.
All these ROMs require no lower than hboot 3.19.0000
ckpv5 said:
What's your hboot no. on the bootloader.
All these ROMs require no lower than hboot 3.19.0000
Click to expand...
Click to collapse
That could be it then. Says I'm on 3.16.0.0000. So I'll have to be S-Off and update my firmware then to get any ROMs working?
Seltioasa said:
That could be it then. Says I'm on 3.16.0.0000. So I'll have to be S-Off and update my firmware then to get any ROMs working?
Click to expand...
Click to collapse
I'm not familiar with AT&T variant. The last info that I know they have RUU for 4.4.4, not sure about lollipop.
If you have plan to S-Off your device, with hboot 3.16.0000 you have better chance to do it with SunShine.
Once you updated your firmware, the chance to S-Off is slimmer.
Either you browse thru AT&T forum for info or maybe @redpoint73 can assist you here.
Seltioasa said:
That could be it then. Says I'm on 3.16.0.0000. So I'll have to be S-Off and update my firmware then to get any ROMs working?
Click to expand...
Click to collapse
Depending on the ROM, most of them require a particular firmware (which contains hboot, radio, WiFI, media moduels and others), not just the hboot.
You can update to 4.4.4 firmware by RUU (relock bootloader since you are s-on). Backup any personal data first, as RUU will wipe the phone.
Once updated to 4.4.4 firmware, you can run any ROM that supports that firmware. If you want a ROM that requires 5.0 firmware, you currently need s-off to manually (by "unofficial" means) update the firmware; until AT&T releases official 5.0.
Yes, its confusing and you can blame HTC for the firmware complications.
RUUs are linked in my (AT&T specific) index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Before I begin, I have already read through a lot of the guides but almost of all them are not updated enough for my case. If I am wrong please direct me to it.
I would like to restore AT&T stock rom on my phone which was previously converted to GPE Lollipop 5.1 (with root, bootloader unlocked and s-off).
Here's what I have already done.
Restored MID and CID to 0P6B12000 and CWS__001 (for AT&T) respectively.
Relocked the bootloader.
Restoring from a nandroid (before going GPE) fails.
Downloaded the most latest RUU file for AT&T model, and ran the process.
But RUU fails with error 155. And after reading online, any of the following could be cause of the problem.
Partition size difference in GPE and AT&T stock rom.
Difference in firmware version or may be HBOOT version.
GPE is lollipop 5.1 and I think AT&T's latest rom is 5.0.1. So may be this downgrade is causing the problem
The RUU file I was using: RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
I think my first step would be to flash some correct firmware to be able to successfully run RUU, but I don't know how which one. Plus, will downgrading firmware cause problems?
I would appreciate any help in resolving this problem. At minimum, I would like to be able to flash some stock rom with all the sense and AT&T stuff.
My responses below in red font:
lief.erl said:
I would like to restore AT&T stock rom on my phone which was previously converted to GPE Lollipop 5.1 (with root, bootloader unlocked and s-off).
Here's what I have already done.
Restored MID and CID to 0P6B12000 and CWS__001 (for AT&T) respectively. correct
Relocked the bootloader. Not required, since you are s-off. Just making more work for yourself needlessly.
Restoring from a nandroid (before going GPE) fails. No way this would ever work. nandroid is just a backup of ROM and user data. Since the partition sizes are different, the Sense ROM won't fit on the system partition, and failure is a certainty. You need to re-partition via firmware/RUU.
Downloaded the most latest RUU file for AT&T model, and ran the process.
But RUU fails with error 155. And after reading online, any of the following could be cause of the problem.
Partition size difference in GPE and AT&T stock rom. This is most likely the cause.
Difference in firmware version or may be HBOOT version. Only a "downgrade of hboot is prohibited (trying to flash the same or higher number hboot is ok), and that is with s-on. Downgrade is even allowed with s-off.
GPE is lollipop 5.1 and I think AT&T's latest rom is 5.0.1. So may be this downgrade is causing the problem This also would not matter with s-off. Downgrades are ok
The RUU file I was using: RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
I think my first step would be to flash some correct firmware to be able to successfully run RUU, but I don't know how which one. Plus, will downgrading firmware cause problems?
Click to expand...
Click to collapse
Find the 4.28.502.1 firmware zip and flash it in fastboot first. Then flash the RUU.
Some folks have been able to just RUU to get back to the Sense partition scheme. But many folks have to flash the firmware first, then RUU. Not sure why folks have different experiences.
redpoint73 said:
My responses below in red font:
Find the 4.28.502.1 firmware zip and flash it in fastboot first. Then flash the RUU.
Some folks have been able to just RUU to get back to the Sense partition scheme. But many folks have to flash the firmware first, then RUU. Not sure why folks have different experiences.
Click to expand...
Click to collapse
Thanks a lot.
Before I proceed, I have following questions.
How do I make sure that a RUU and the suggested firmware are compatible. Should I be looking at some thing in particular.
I was also curious about how do we decide which firmware to flash?
One again, thanks.
lief.erl said:
Before I proceed, I have following questions.
How do I make sure that a RUU and the suggested firmware are compatible. Should I be looking at some thing in particular.
I was also curious about how do we decide which firmware to flash?
Click to expand...
Click to collapse
You want the firmware that matches the RUU, they will have the same number (4.28.502.1).
The firmware was posted here: http://forum.xda-developers.com/att-htc-one-m8/general/lollipop-ota-twrp-backup-firmware-t3075835
redpoint73 said:
You want the firmware that matches the RUU, they will have the same number (4.28.502.1).
The firmware was posted here: http://forum.xda-developers.com/att-htc-one-m8/general/lollipop-ota-twrp-backup-firmware-t3075835
Click to expand...
Click to collapse
Looks like there are three[4.28.502.1] different firmware files.
4.28.502.1 OTA.ZIP
4.28.502.1 TWRP backup
4.28.502.1 Firmware
None of them say they are mirrors (ones which are have "mirror by" as prefix), so I am assuming some difference. Which one should I go with.
BTW, is it possible to go back to earlier android os, for example kit kat. I am asking this because going back might mean downgrading firmware.
lief.erl said:
Looks like there are three[4.28.502.1] different firmware files.
4.28.502.1 OTA.ZIP
4.28.502.1 TWRP backup
4.28.502.1 Firmware
None of them say they are mirrors (ones which are have "mirror by" as prefix), so I am assuming some difference. Which one should I go with.
Click to expand...
Click to collapse
Those aren't all firmware. Just the one that says "firmware" is firmware.
OTA.zip is the actual official OTA form AT&T, which would only work if you were on the Sense version directly preceding this update (so this is to go from stock Sense 3.42 > 4.28), and also stock recovery.
TWRP backup is just a backup of the ROM, and doesn't include firmware. Obviously, restore with TWRP as you would your own TWRP backup.
lief.erl said:
BTW, is it possible to go back to earlier android os, for example kit kat. I am asking this because going back might mean downgrading firmware.
Click to expand...
Click to collapse
Sure, you would just need the RUU for the desired version, and the matching firmware.
Downgrading firmware is only prohibited with s-on (version check prevents it).
You can find the RUUs here: http://forum.xda-developers.com/showthread.php?t=2751432
Some of the unmodified firmwares can be found at the bottom of the 1st post of the following thread: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
redpoint73 said:
Those aren't all firmware. Just the one that says "firmware" is firmware.
OTA.zip is the actual official OTA form AT&T, which would only work if you were on the Sense version directly preceding this update (so this is to go from stock Sense 3.42 > 4.28), and also stock recovery.
TWRP backup is just a backup of the ROM, and doesn't include firmware. Obviously, restore with TWRP as you would your own TWRP backup.
Sure, you would just need the RUU for the desired version, and the matching firmware.
Downgrading firmware is only prohibited with s-on (version check prevents it).
You can find the RUUs here: http://forum.xda-developers.com/showthread.php?t=2751432
Some of the unmodified firmwares can be found at the bottom of the 1st post of the following thread: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Click to expand...
Click to collapse
Do you know which version of android os will ruu 1.58.502.1 install?
Some guides say to rename the firmware file to SOMETHINGfirmware.zip, while others say to rename to 0P6BIMG.zip. Does it depend on how I am flashing. For the first one I will flash using fastboot, and for the other one I will flash by putting the file on the sd card.
lief.erl said:
Do you know which version of android os will ruu 1.58.502.1 install?
Click to expand...
Click to collapse
Android 4.4.2
Software 1.x = Android 4.4.2
2.x = 4.4.3
3.x = 4.4.4
4.x = 5.0
lief.erl said:
Some guides say to rename the firmware file to SOMETHINGfirmware.zip, while others say to rename to 0P6BIMG.zip. Does it depend on how I am flashing. For the first one I will flash using fastboot, and for the other one I will flash by putting the file on the sd card.
Click to expand...
Click to collapse
Yes, it depends on how you flash (fastboot vs. putting file on the phone).
redpoint73 said:
Android 4.4.2
Software 1.x = Android 4.4.2
2.x = 4.4.3
3.x = 4.4.4
4.x = 5.0
Yes, it depends on how you flash (fastboot vs. putting file on the phone).
Click to expand...
Click to collapse
I am sorry to bother you again, but I can't seem to find RUU and a firmware for android 4.4.2 for AT&T.
The closest thing I have found is http://forum.xda-developers.com/att-htc-one-m8/general/att-1-58-501-1-bootable-ruu-hboot-t2818556
which is a bootable zip.
I am trying to avoid using any method other than official RUU.
lief.erl said:
I am sorry to bother you again, but I can't seem to find RUU and a firmware for android 4.4.2 for AT&T.
The closest thing I have found is http://forum.xda-developers.com/att-htc-one-m8/general/att-1-58-501-1-bootable-ruu-hboot-t2818556
which is a bootable zip.
I am trying to avoid using any method other than official RUU.
Click to expand...
Click to collapse
Link to the 1.58 RUU is in my Index thread, which I indicated in Post #6 above (1st link).
On my Index thread, under RUUs, its the 1st link under "Official" RUUs.
I'll see if I can find the firmware zip for that RUU.
EDIT: Here you go: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC%2FHTC_One_M8%2F502%2F
Linked from here (so you know its a reliable XDA source): http://forum.xda-developers.com/showthread.php?t=2696282
redpoint73 said:
Link to the 1.58 RUU is in my Index thread, which I indicated in Post #6 above (1st link).
On my Index thread, under RUUs, its the 1st link under "Official" RUUs.
I'll see if I can find the firmware zip for that RUU.
EDIT: Here you go: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC%2FHTC_One_M8%2F502%2F
Linked from here (so you know its a reliable XDA source): http://forum.xda-developers.com/showthread.php?t=2696282
Click to expand...
Click to collapse
One last question (I think), how do I determine what should be the name of the firmware zip, if I am going to be flashing from PC.
lief.erl said:
One last question (I think), how do I determine what should be the name of the firmware zip, if I am going to be flashing from PC.
Click to expand...
Click to collapse
I actually do not think it matter, as long as its a zip.
Some instructions will say firmware.zip. Others will call it something else, such as the specific file name including software number. And in fact, this guide says: fastboot flash zip 2.22.1540.3_firmware.zip or whatever the latest builds firmware zip is called.
If you look at the syntax of the command, its simply flashing a zip and not even specific to firmware: "fastboot flash zip blahblahblah.zip" and its what is inside the zip that determines what is being flashed to what partition on the phone.
Just make sure if you rename the file, that you don't have the Windows option enabled to hide file extensions. Otherwise you may name the file firmware.zip.zip and not realize it. This is a common error, since hiding the file extensions is typically enabled by default in Windows.
redpoint73 said:
I actually do not think it matter, as long as its a zip.
Some instructions will say firmware.zip. Others will call it something else, such as the specific file name including software number. And in fact, this guide says: fastboot flash zip 2.22.1540.3_firmware.zip or whatever the latest builds firmware zip is called.
If you look at the syntax of the command, its simply flashing a zip and not even specific to firmware: "fastboot flash zip blahblahblah.zip" and its what is inside the zip that determines what is being flashed to what partition on the phone.
Just make sure if you rename the file, that you don't have the Windows option enabled to hide file extensions. Otherwise you may name the file firmware.zip.zip and not realize it. This is a common error, since hiding the file extensions is typically enabled by default in Windows.
Click to expand...
Click to collapse
Thanks for all the help, but this method didn't work for me. After I was successful in flashing older firmware, M8 refused to the go in the the actual android os which is required for RUU (.exe) to work its magic (needs adb). May be because older firmware and latest OS (GPE 5.1) weren't compatible with each other. So I ended up using a bootable RUU with excellent result. Though the deed is done and I have returned the phone (Color banding was too much bear), I am curious whether it would have worked if adb was enabled inside TWRP.
lief.erl said:
Thanks for all the help, but this method didn't work for me. After I was successful in flashing older firmware, M8 refused to the go in the the actual android os which is required for RUU (.exe) to work its magic (needs adb). May be because older firmware and latest OS (GPE 5.1) weren't compatible with each other. So I ended up using a bootable RUU with excellent result. Though the deed is done and I have returned the phone (Color banding was too much bear), I am curious whether it would have worked if adb was enabled inside TWRP.
Click to expand...
Click to collapse
You can RUU with the phone in fastboot mode as well as booted into the OS. The only difference with booted into OS, is that the RUU will reboot into fastboot anyway. RUU will not work in TWRP (with adb enabled).
And yes, running "newer" version of OS with older firmware will result in issues. Extreme long boot times (and broken WiFi) are the most common issues. So its possible the phone would have booted eventually (just taking a really long time, and not completely "stuck").
Hi
hope any can help with the issue i am facing, simply i deleted my os & the back up file while trying to flash a rom
all i can access now is twrp recovery screen, i tried flashing a couple of custom rom with no luck
my device is HTC one M8, it was rooted but i don't think it is anymore since it says that i don't have su installed
excuse my lack of android knowledge, as i am new to this whole thing
thanks for reading and any help is appreciated
I never fail to be frustrated at the nearly countless reports here of "I deleted everything on my phone and now its stuck".
If you lack knowledge of Androids mods, the proper way to proceed is to familiarize yourself and understand what you are doing before doing it. The absolute wrong thing to do, is to delete things without knowing what the result will be, and not knowing how to revert from that condition. Plus, the default wipe (user data, cache and Dalvik) on TWRP clearly states that "most of the time, this is the only wipe you need". It says this for good reason, and the additional wipe options are labelled "Advanced" also for good reason. So there were a couple warning signs against doing what you did, that you chose to ignore.
You didn't specify what ROMs you tried (makes it hard to help) and whether you put those on the phone before you wiped the OS; or if you know how to put ROMs on the phone in the current condition (using adb push, or removable SD).
Also, missing some key info:
1) hboot number
2) OS number on hboot screen (or main version as determined by adb getvar all)
3) CID (carrier version) of your phone
4) S-on or s-off
5) What version TWRP
while in TWRP, plug your phone into a computer and under mount you mount the phone as USB, and you copy over a ROM zip, and you flash it as you would normally. that should have fixed it.
ashypanda said:
while in TWRP, plug your phone into a computer and under mount you mount the phone as USB, and you copy over a ROM zip, and you flash it as you would normally. that should have fixed it.
Click to expand...
Click to collapse
While your advice is generally true, the specific ROM (or TWRP version) may part of the issue. OP will need to be careful to flash a ROM that supports his current firmware (hboot, radio, etc.) otherwise he may have some serious problems.
The fact that he said he tried a few ROMs that didn't work, leads me to believe he either has old firmware, or old TWRP.
OP should provide the info I requested in my last post, so we can more specifically help.
thank you for your assitance
1) hboot number:3.16..0.000
2) OS number on hboot screen: nothing apears next to OS on Hboot screen
3) CID (carrier version) of your phone-HTC__j15
4)s-off
5) What version TWRP: 2.7.0.2
hope this info helps
please advise me which rom to use as i am totally lost here
sorry if i caused any disturbance
ahmed.abdelradi said:
thank you for your assitance
1) hboot number:3.16..0.000
2) OS number on hboot screen: nothing apears next to OS on Hboot screen
3) CID (carrier version) of your phone-HTC__j15
4)s-off
5) What version TWRP: 2.7.0.2
hope this info helps
please advise me which rom to use as i am totally lost here
sorry if i caused any disturbance
Click to expand...
Click to collapse
To bring your phone up to date, you can flash the 4.16.1540 firmware posted here. Then update to TWRP 2.8.7 (flash in fastboot), then flash most any current ROM for the M8.
Another option you can flash an old Android 4.4.2 ROM based on software version 1.xx (1.12, 1.54, etc.) to match your old firmware. But in this case, don't update to the latest TWRP before doing so, as it won't work with hboot 3.16.
redpoint73 said:
To bring your phone up to date, you can flash the 4.16.1540 firmware posted here. Then update to TWRP 2.8.7 (flash in fastboot), then flash most any current ROM for the M8.
Another option you can flash an old Android 4.4.2 ROM based on software version 1.xx (1.12, 1.54, etc.) to match your old firmware. But in this case, don't update to the latest TWRP before doing so, as it won't work with hboot 3.16.
Click to expand...
Click to collapse
Personally, I would rather go with a "combined" firmware, such as the ones provided here: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
Mike's firmwares are incremental afaik (pulled from the OTAs), so jumping from from a 1.xx firmware all the way to an [incremental] 4.16 version, is going to cause problems.
i did the same..
htc one m8
UNLOCKED
S-OFF
cid-11111111
hboot- 3.18.0.0000
radio-1.08.20.0612_4
opendsp- v38.2.2-00542-M8974.0311
os-1.54.651.8
eMMC-boot 2048mb
jul 7 2014, 20:03:18.23767
this is displayed when i turn on my device and i can enter recovery( teamwin recovery project 3.1.1-0 )
i was running on 4.2.2 version and wanted to upgrade to viper rom (i ended up flashing a rom for some other device and deleting every stuff on my internal and sdcard by wiping it in recovery.
kindly help me to how should i get back to 4.2.2 or how can i still get viper rom flashed ...!
thank you.. been trying to get my phone back to 4.2.2 for the past week and havent tried doing viper yet..
plzzzz help...
srijan0008 said:
i did the same..
htc one m8
UNLOCKED
S-OFF
cid-11111111
hboot- 3.18.0.0000
radio-1.08.20.0612_4
opendsp- v38.2.2-00542-M8974.0311
os-1.54.651.8
eMMC-boot 2048mb
jul 7 2014, 20:03:18.23767
this is displayed when i turn on my device and i can enter recovery( teamwin recovery project 3.1.1-0 )
i was running on 4.2.2 version and wanted to upgrade to viper rom (i ended up flashing a rom for some other device and deleting every stuff on my internal and sdcard by wiping it in recovery.
kindly help me to how should i get back to 4.2.2 or how can i still get viper rom flashed ...!
thank you.. been trying to get my phone back to 4.2.2 for the past week and havent tried doing viper yet..
plzzzz help...
Click to expand...
Click to collapse
Dude, your firmware is super old and you won't be able to run the latest ViperROM with it.
Be aware what I'm telling you to do will wipe your phone, (you'll need to do a full wipe to flash the ViperROM anyway)
Go here to download the official RUU from HTC's US website
Scroll down to the "Manual System Update Instructions" and read them. The RUU download is at the end of the instructions
After the RUU has run, reflash TWRP, then flash the ROM
srijan0008 said:
i did the same..
Click to expand...
Click to collapse
A word of advice, I know you are new here, but posting "I did the same" or similar ("same problem" etc.) is never true. Especially since you are responding to a thread from 2 years ago, different M8 versions, different ROM, different TWRP version.
There are simply far too many differences to say you "did the same" and that statement is therefore meaningless. Better to just describe the exact issue (which you did) and not bother with such vague statements.
srijan0008 said:
os-1.54.651.8
this is displayed when i turn on my device and i can enter recovery( teamwin recovery project 3.1.1-0 )
i was running on 4.2.2 version and wanted to upgrade to viper rom
Click to expand...
Click to collapse
As xunholyx explained you need to update the firmware, not just the ROM. Firmware includes a whole bunch of other partitions (hboot, radio, WiFi, and more) that ROM doesn't touch. Old firmware (your is very old) is not compatible with a more recent version ROM.
Old firmware is also not compatible with the current TWRP 3.1.1-0, so the ROM won't flash properly, either.
So as already suggested, flash RUU to update all the firmware. Then flash TWRP 3.1.1-0 back to the phone, and flash Viper.
srijan0008 said:
i ended up flashing a rom for some other device and deleting every stuff on my internal and sdcard by wiping it in recovery.
Click to expand...
Click to collapse
Another good rule of thumb, do NOT wipe things in TWRP "Advanced" wipe options, unless you know exactly what it is, and what the result will be. Wiping internal storage and/or SD will in most cases not help matter, but just make them worse (wipe backups, ROM zips, etc.).