Related
My M8 has the CID of HTC_044 and I would like to flash latest ROM. However it requires latest firmware, ie 2.22.401.4, I am wondering if it is safe to flash the firmware to my device being with different CID as the firmware's android-info does not contain my device CID.
I have S-OFF on my device, I am wondering if I change mt CID to supercid would allow my device to run the firmware without issue.
Thanks in advance.
Yep,if your phone is supercid,u can flash that firmware...
hellcommando said:
My M8 has the CID of HTC_044 and I would like to flash latest ROM. However it requires latest firmware, ie 2.22.401.4, I am wondering if it is safe to flash the firmware to my device being with different CID as the firmware's android-info does not contain my device CID.
I have S-OFF on my device, I am wondering if I change mt CID to supercid would allow my device to run the firmware without issue.
Thanks in advance.
Click to expand...
Click to collapse
If your firmware for CID HTC__044 is 2.22.707.3, it is not necessary for you to flash another firmware to run a 2.22.401.4 ROM.
As long as the firmware is 2.22.xxx.x ... you're good to go.
Anyway it's up to you if you want to flash 2.22.401.4 firmware but your Radio will be the EU region if the firmware that you flash come with radio image. If you currently in Asia, it's best to keep 2.22.707.3 firmware
hdorius said:
Yep,if your phone is supercid,u can flash that firmware...
Click to expand...
Click to collapse
Thank you!
ckpv5 said:
If your firmware for CID HTC__044 is 2.22.707.3, it is not necessary for you to flash another firmware to run a 2.22.401.4 ROM.
As long as the firmware is 2.22.xxx.x ... you're good to go.
Anyway it's up to you if you want to flash 2.22.401.4 firmware but your Radio will be the EU region if the firmware that you flash come with radio image. If you currently in Asia, it's best to keep 2.22.707.3 firmware
Click to expand...
Click to collapse
Thank you! However I have heard there was one 2.22.7xx posted but was meant for M7, and at the moment I could not find 2.22.707.3 firmware from any firmware repository. I'm from Asia, could you please kindly post the link so that I wont brick my phone? Thank you!!
hellcommando said:
Thank you! However I have heard there was one 2.22.7xx posted but was meant for M7, and at the moment I could not find 2.22.707.3 firmware from any firmware repository. I'm from Asia, could you please kindly post the link so that I wont brick my phone? Thank you!!
Click to expand...
Click to collapse
When we read firmware we look at x.xx.707.x not 2.22.7xx.x
You don't need 2.22.707.3 firmware if you already done the OTA update.
Please advise your current firmware that you have ... check what is written on the bootloader ... is it 1.54.707.7 or 2.22.707.3 ?
If it is 1.54.707.7 then you need to do OTA update.
If it is 2.22.707.3 then you're good to flash any ROM.
ckpv5 said:
When we read firmware we look at x.xx.707.x not 2.22.7xx.x
You don't need 2.22.707.3 firmware if you already done the OTA update.
Please advise your current firmware that you have ... check what is written on the bootloader ... is it 1.54.707.7 or 2.22.77.3 ?
If it is 1.54.707.7 then you need to do OTA update.
If it is 2.22.707.3 then you're good to flash any ROM.
Click to expand...
Click to collapse
Couldn't check my firmware version as the OS field is empty in the bootloader.
Hboot: 3.16.0.0000
Radio: 1.16.2133156.UA10G
But I highly doubt my firmware is 2.22.707.3, I would think it is more likely to be 1.54.707.7 as I have rooted by phone before newer firmware roll out.
So can I use your firmware in http://forum.xda-developers.com/showthread.php?t=2701376&page=141
and flash it by using this guide? http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
hellcommando said:
Couldn't check my firmware version as the OS field is empty in the bootloader.
Hboot: 3.16.0.0000
Radio: 1.16.2133156.UA10G
But I highly doubt my firmware is 2.22.707.3, I would think it is more likely to be 1.54.707.7 as I have rooted by phone before newer firmware roll out.
So can I use your firmware in http://forum.xda-developers.com/showthread.php?t=2701376&page=141
and flash it by using this guide? http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Click to expand...
Click to collapse
Right ... your current hboot is 3.16 so it's 1.54.707.7
I suggest that you restore 1.54.707.7 stock Backup, flash back stock recovery and do the OTA (no need to relock bootloader or S-On .. OTA update work on unlocked bootloader and S-Off)
I don't post firmware on XDA. Those that I posted are recovery and stock backup.
If you insist to update firmware without OTA update .. that's you call. Someone maybe will guide you how to do it as I don't feel comfortable telling how to update firmware.
ckpv5 said:
Right ... your current hboot is 3.16 so it's 1.54.707.7
I suggest that you restore 1.54.707.7 stock Backup, flash back stock recovery and do the OTA (no need to relock bootloader or S-On .. OTA update work on unlocked bootloader and S-Off)
I don't post firmware on XDA. Those that I posted are recovery and stock backup.
If you insist to update firmware without OTA update .. that's you call. Someone maybe will guide you how to do it as I don't feel comfortable telling how to update firmware.
Click to expand...
Click to collapse
Awesome! I just followed your advice by doing the safe way, flashed stock recovery and backup. I'm running on 2.22.707.x now! Thanks a lot :good:
hellcommando said:
Awesome! I just followed your advice by doing the safe way, flashed stock recovery and backup. I'm running on 2.22.707.x now! Thanks a lot :good:
Click to expand...
Click to collapse
Great
Now you can flash any Sense 6 custom ROM that you like.
Only remember that you don't need to flash another firmware, your current one is good enough.. just flash ROM.
I am having the same issue - I have the HTC__044 and need new firmware to get the newest ROM.
I am S-On and CANT get S-off (s-off needed to flash firmware)...firewater does not work with my phone after multiple tries.
I tried getting Sunshine to work for s-off, but I need to be on a stock Sense ROM (I am on Viper 1.8) and don't have a stock backup. I can't find ANY stock ROM's online! Once I have supercid i was going to flash firmware, but without S off...I'm going nowhere (it seems)
anyone have an idea where I should start?
charkswitlazers said:
I am having the same issue - I have the HTC__044 and need new firmware to get the newest ROM.
I am S-On and CANT get S-off (s-off needed to flash firmware)...firewater does not work with my phone after multiple tries.
I tried getting Sunshine to work for s-off, but I need to be on a stock Sense ROM (I am on Viper 1.8) and don't have a stock backup. I can't find ANY stock ROM's online! Once I have supercid i was going to flash firmware, but without S off...I'm going nowhere (it seems)
anyone have an idea where I should start?
Click to expand...
Click to collapse
Stock ROMs and recoveries for HTC__044
http://forum.xda-developers.com/showthread.php?t=2701376
charkswitlazers said:
anyone have an idea where I should start?
Click to expand...
Click to collapse
Everything that you need is here : http://forum.xda-developers.com/showthread.php?t=2701376
1. Restore nandroid backup 1.54.707.7
2. flash stock recovery 1.54.707.7
3. reboot and check for OTA
4. install OTA
5. done .. your ROM will be 4.4.3 - 2.22.707.3
6. flash any 4.4.3 custom ROM that you like if any
All above no need to relock bootloader or S-Off, it works on S-On
If you want to S-Off with sunshine, step 1 & 2 then sunshine
or after step 5 then sunshine (both way should work)
ckpv5 said:
Everything that you need is here
1. Restore nandroid backup 1.54.707.7
2. flash stock recovery 1.54.707.7
3. reboot and check for OTA
4. install OTA
5. done .. your ROM will be 4.4.3 - 2.22.707.3
6. flash any 4.4.3 custom ROM that you like if any
All above no need to relock bootloader or S-Off, it works on S-On
If you want to S-Off with sunshine, step 1 & 2 then sunshine
or after step 5 then sunshine (both way should work)
Click to expand...
Click to collapse
I'm still a little on the noob side with rooting/flashing..I am at work and don't have time to read much - i will go home and give it a go... I'm sure I will have lots of questions
A quick look at the site, i saw lots of recoveries but not very many stock ROMs. I mainly just need a plain/rooted stock Sense rom to run Sunshine. After which i can flash new firmware, then the new custom ROM i've been wanting. Also, does a nandroid HAVE to be HTC__044, or can it be any WWE cid? (like anything that's "HTC__xxx")?
Excuse my ignorance...trying to learn as much as possible
I just got my m8 from Tmobile today, and I am on firmware 157.531.7
I've checked several times for updated firmware, but always comes back nothing.
Am I stuck on this, or will it take awhile for the network to "see me" and send it?
not rooted, fully stock for now
thanks so much!
charkswitlazers said:
I'm still a little on the noob side with rooting/flashing..I am at work and don't have time to read much - i will go home and give it a go... I'm sure I will have lots of questions
A quick look at the site, i saw lots of recoveries but not very many stock ROMs. I mainly just need a plain/rooted stock Sense rom to run Sunshine. After which i can flash new firmware, then the new custom ROM i've been wanting. Also, does a nandroid HAVE to be HTC__044, or can it be any WWE cid? (like anything that's "HTC__xxx")?
Excuse my ignorance...trying to learn as much as possible
Click to expand...
Click to collapse
If your main purpose to restore to stock to get SunShine working, then any nandroid backup will do either HTC__044 or WWE. You don't really need a rooted stock as SunShine works on non-rooted ROM too.
As you said you're a noob, that is why I suggest to restore to 1.54.707.7 then OTA to 2.22.707.3 so you don't need to manually flash firmware to get other custom ROMs running flawlessly. It is not necessary to have 2.22.401.4 firmware but it is necessary to have a 2.22.xxx.x firmware for those custom ROMs, unless you're not in Asia.
As you can see in my sig, I'm on 2.22.707.3 firmware, I can run any ROM without problem.
Being a noob, you may make a stupid mistake when flashing firmware.
There is also by mike or so a stock Rom as a zip.
Flash it like a custom Rom Flash the stock kernel and better the recovery and do sunshine...easier then with getting nandroid backup etc
Slow Booting & Sense 6 Toolbox Not Working On ARHD v10.2
One-M8-Master said:
There is also by mike or so a stock Rom as a zip.
Flash it like a custom Rom Flash the stock kernel and better the recovery and do sunshine...easier then with getting nandroid backup etc
Click to expand...
Click to collapse
Hi One-M8-Master,
I've read quite a few of your posts & given that your moniker seems appropriate, I'm wondering if you might be able to help me?
I've posted this on another thread but haven't got very far as yet, so am hoping that you might be able to get me out of the stupid hole I've dug myself into :fingers-crossed:
It is quite a long description but if you don't fall asleep reading it, I'd really appreciate any help you might be able to give me.....Here goes:
"Hi Guys,
Now I know you're all already thinking that I didn't update my firmware before I flashed ARHD & now I'm getting all the problems that come along with not doing that......& you'd be correct....kind of. HOWEVER, as it turns out, I already seem to have it. Let me explain.
As you can see, I'm relatively new to all this but successfully unlocked, rooted & installed a custom ROM on my ASUS TF700T tablet, so I wanted to do it with my One M8. I always do loads of reading before I start anything (I even read the instructions for new games before I attempt to play them because I'm a bit weird like that!) but what happened on this occasion was that I did the reading, unlocked the phone, flashed TWRP, & rooted it but then ran into the problem that some people appear to have had when trying to s-off via the adb commands & Firewater, that is, my pc could see the phone but when I gave the reboot command, it told me it wasn't connected.
I then got into hours of reading to try & solve this issue, discovered that (without Sunlight) on some devices it just doesn't work once you've accepted the 'should we allow this pc to connect every time' message (which I NEVER normally say 'yes' to), unless you install the Android Studio & Java Develpers Kits, update your version of adb, & force the phone to ask again (which I did but it turned out that I already had the latest version of adb, so that route proved fruitless!). I actually missed a night's sleep trying to resolve the problem, so work wasn't good the next day! but I think it is here is where my problems started because I was so tired & frustrated that I just picked a ROM & flashed it. I had even read the warning about not flashing it if you didn't have the correct firmware but I think that being so tired, it didn't really sink in, or I'd forgotten about it by the time I just flashed the ROM.
By this point, I'd been sat in front of my pc for about 30 hours & needed to go to work but the phone was actually booting through to ARHD, so I was relatively happy in the knowledge that at least I hadn't bricked it! On starting to use the phone that evening, I noticed the long boot times & then that my Sense 6 Toolbox didn't seem to be making any changes, even if I rebooted the device, so I went back to the beginning of this thread & started reading again. Thus, I re-read the firmware warning & panicked (my 2nd mistake!), thinking that I was getting the problems because I hadn't updated the firmware (it still didn't occur to me to just check because I think I just assumed that I wouldn't have it). So.....I tried to restore my TWRP backup of the stock ROM that I made after I had unlocked/rooted, with the intention of reverting to the stock ROM, getting the OTA update & then re-flashing ARHD but despite TWRP telling me that the backup had been successful, the phone went into a bootloop back into TWRP. I solved this by re-flashing the ARHD ROM that I knew at least would get my phone out of the bootloop & back into KitKat, which it did. I then checked what version of the firmware I had & to my surprise, my Build Number in About\Software Information\More says "2.22.401.4 CL365360 release-keys", so it looks like I had the correct firmware version all along?
The above being the case, I'm now puzzled as to why I'm getting the problems that I'm getting with ARHD? Does anyone have any clues/answers that might get me out of this hole I've dug for myself & get my awesome One M8 working like it should?
I know I've caused this problem by doing things when I was too tired to think straight but I'm fresh as a daisy now (still fairly noobish but fresh ) & now I need your help to sort myself out. I would be so grateful for any help anyone can give me to get me back on track.
I hope all of that makes sense & thanks in advance."
@dan5001
The firmware you speak of is the displayed version main number of the flashed rom. It has no relation to your actual installed firmware. Check your bootloader and post here what it says. I bet it is still hboot 3.16 and if that's the case your firmware is not updated.
Mr Hofs said:
@dan5001
The firmware you speak of is the displayed version main number of the flashed rom. It has no relation to your actual installed firmware. Check your bootloader and post here what it says. I bet it is still hboot 3.16 and if that's the case your firmware is not updated.
Click to expand...
Click to collapse
Hi.
This is my own fault but I'm getting really frustrated with it because I've probably spent a total of 40 hours on it so far
I tell you that because I know that I needed S-OFF & SUPER CID to be able to update my firmware, so I just thought "screw it" & I paid for Sunshine. I now have S-OFF & following Vomer's guide here:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
I now have S-OFF & SUPER CID. I thought that would be the end of my issues but it would appear not!
Looking at my bootloader, you are correct, HBOOT is 3.16.0.0000!
However, I've tried to upgrade this firmware by downloading what I think is the correct update .zip from the list at the bottom of the aforementioned Vomer's guide (v2.22.401.5 (Rename to firmware.zip after downloading)), renaming it as suggested, & then flashing it in TWRP but it just keeps telling me that the update has failed!
Do I have to do it using the adb commands on Vomers guide? I didn't think so but it's just not working??
I appreciate any help you can give me with this. Given that I've spent so long on this & have paid for Sunshine, you can see that I'm trying to help myself but I've still got rain!!
EDIT
Just a thought, I do still have ARHD v10.2 installed at the moment because even though it's not working properly without the correct firmware, it's the only ROM I've got at the moment, so it means I can use the M8 to a degree; would that cause the problem with upgrading the firmware?
Firmware flash can be done via fastboot commands, that's how i did it
Installed rom has no influence on the to flash firmware, try it via fastboot
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!
Hey guys, first post here and I couldn't find a good thread title. Hope that's not a problem
Anyways I need a little help with my m8, because I don't know what else to do.
I'll start from the beginning:
It's a One m8, bought from O2 Germany a few months ago. There were no O2 apps installed as I bought it, though.
I unlocked the bootloader, rooted the phone, flashed the TWRP recovery and the Venom m8 ROM. It was S-On over the whole time. Tried to make it S-OFF with the help of firewater but it didn't worked, so I didn't tried it anymore.
I just wanted to flash the newest Venom ROM, but to do so, I had to flash the newest firmware (Kitkat 4.4, have 4.2 right now)
So I relocked the bootloader, because that's what people on the internet said you have to do, to flash the newest stock firmware. After that I wanted to go back to Venom m8.
After relocking the bootloader, I rebooted the phone, and now I'm stuck in there. But in the fastboot mode.
Tried to enter the recovery -> can't access it
Tried to make a factory reset -> didn't worked
Everytime klick on recovery or factory reset, the phone reboots and comes back into fastboot.
Normaly you boot into hboot I think.
At the top of the screen stands:
***TAMPERED***
***RELOCKED***
***Security Warning***
I've seen the first two the whole time, but the third one is new :/
Here are the things I tried until now:
Flashing a stock ROM (it was a OTA_m8_O2___102...) I could try to find the actual link, if that helps.
Flashing a custom recovery (tried TWRP, after that CWM) Yea I already have custom recovery, but I tought it might help somehow.
Erased fastboot cache
None of these things worked. Fastboot is the only thing that works.
So my question now is, if anyone of you guys got any other idea how to solve that problem?
I really would appreciate any help.
If you need some more informations about the phone, just let me know. I guess there's missing some important informations
Sorry for the long text and if I misspelled something
EDIT: I just remembered that the flashing of TWRP or CWM didn't worked. It said FAILED: signature verify fail
Flashing of the Stock ROM worked I guess. There was the silver HTC logo on the phone. Then I flashed it in fastboot mode.
I tried to find this RUU software, but I couldn't find it :/
And "adb" in cmd also not working. It says "device not found"
Have you tried unlocking it again ?
Sent from my HTC One_M8 using XDA Free mobile app
---------- Post added at 12:10 AM ---------- Previous post was at 12:08 AM ----------
Oh, and what are your CID / MID / bootloader version / firmware version / etc. ?
Sent from my HTC One_M8 using XDA Free mobile app
You're bootloader needs to be unlocked, not re-locked. Go to HTC Dev to unlock in again, just like the first time. Then you can flash a recovery.
Like said above, phone HAS to have unlocked bootloader to flash custom ROMs and recovery(which is why you're getting FAILED: signature verify fail). Can't flash custom recovery/ROMs with a locked bootloader.
Go to HTCDev.com and unlock the bootloader like before, then head over to the collection of stock backups thread(in general section) download a nandroid backup for your device and restore it. After that you can flash back the stock recovery(also in the collection thread) and just do the OTA updates until you get to 4.4.4 to use the latest ViperROM.
SunShine don't work with a modifyed custom Rom like ViperS. I flashed ARHD (or stock Rom) and got S-Off with SunShine.
Firewater don't work at all anymore so you have to use SunShine and pay the 25$ it cost.
3fiddy said:
Hey guys, first post here and I couldn't find a good thread title. Hope that's not a problem
Click to expand...
Click to collapse
Its not a bad one. At least better than many thread titles that say things like "Need help". Which of course is obvious, since its a Q&A, help forum! At least you tried to classify your issue!
Although the question of whether its a "soft brick" is not a critical one. IMO the term "soft brick" really doesn't mean anything. It simply means the user just got himself into a jam and doesn't know how to recover. And recovering is usually just a matter of knowing the right simple steps. More important to whether its a "soft brick", is whether the phone is truly bricked or not. And as long as the screen comes on, this phone is virtually never bricked.
RUUs don't exist for Euro versions (only the US versions, as far as I know).
The bootloader needs to be UNLOCKED to flash anything. Either just use the previous unlock bin code and fastboot command, or go through HTCDev.com unlock process again (as previously suggested). Then flash custom recovery, and flash a custom ROM or restore a stock nandroid.
Hey guys, sorry for the late response.
I did what you all said and unlocked the bootloader again. And that was it.
After unlocking it everything works normal.
You guys are the best, I knew this is the right place to come
Even the Venom ROM is on the phone. Everything else is gone, but the ROM is there.
Alright but I still would like to get the newest firmware for the phone. Could you guys give me a little help with this?
What do I have to do first?
I read a lot about how to do this. But as you can see something still went wrong :/
On the phone is currently Android 4.4.2 and ViperOneM8 1.7.0
First thing I have to do is, to grab a Nandroid Backup with the stock ROM, right?
I did this before, but then I read somewhere that the bootloader has to be locked, or relocked to update the newest stock ROM/ the newest firmware.
So if anyone knows how to do this correctly, please let me know.
Also when I flashed the nandroid backup (my own backup from before I flashed venom) I tried to update the firmware, but it wanted to update the latest Venom update.
Is this considered as normal?
Bootloader version (Hboot) is 3.16.0.0... At least I think this is the right one.
@jkolner: Didn't know that firewater doesn't work anymore. How long is this?
@redpoint73: Thanks for the heads-up Also I didn't know that there are no RUUs for the european versions. Good to know that now.
Thank you all for your answers
EDIT: I just tried to enter the recovery and it worked as well.
Oh and when I wrote above that I flashed the stock nandroid backup and the phone wanted to update the latest venom update, I think it was because the rom was still the Venom Rom, right?
Sure it was a nanroid backup, but the ROM was not the stock ROM? Or am I mix-up something there?
3fiddy said:
Alright but I still would like to get the newest firmware for the phone.
I read somewhere that the bootloader has to be locked, or relocked to update the newest stock ROM/ the newest firmware.
Click to expand...
Click to collapse
It sounds like you are trying to return to stock, and install official OTA to update firmware. In that case, unlocked bootloader is OK for OTA (no need to relock). But you need stock ROM and stock recovery.
3fiddy said:
Also when I flashed the nandroid backup (my own backup from before I flashed venom) I tried to update the firmware, but it wanted to update the latest Venom update.
Is this considered as normal?
Oh and when I wrote above that I flashed the stock nandroid backup and the phone wanted to update the latest venom update, I think it was because the rom was still the Venom Rom, right?
Sure it was a nanroid backup, but the ROM was not the stock ROM? Or am I mix-up something there?
Click to expand...
Click to collapse
You are mixing something up. The point of restoring a stock nandroid, is to return to the stock ROM. It sounds like your nandroid is made while on Viper ROM, not stock ROM. Either that, or the nandroid just didn't restore the ROM properly. Make sure "system" is checked on partitions to restore in recovery.
3fiddy said:
Bootloader version (Hboot) is 3.16.0.0... At least I think this is the right one.
Didn't know that firewater doesn't work anymore. How long is this?
Click to expand...
Click to collapse
Its been that way for months now. But your hboot version is old; so firewater might work, might not. Worth a few tries; as firewater is free and doesn't take long. If it still fails, you need to use sunshine to s-off.
redpoint73 said:
It sounds like you are trying to return to stock, and install official OTA to update firmware. In that case, unlocked bootloader is OK for OTA (no need to relock). But you need stock ROM and stock recovery.
Click to expand...
Click to collapse
Exactly this. Alright, then I read something wrong. I thought to flash the stock ROM you have to have a relocked bootloader.
I'll search a stock ROM and recovery. Hoperfully it will work.
redpoint73 said:
You are mixing something up. The point of restoring a stock nandroid, is to return to the stock ROM. It sounds like your nandroid is made while on Viper ROM, not stock ROM. Either that, or the nandroid just didn't restore the ROM properly. Make sure "system" is checked on partitions to restore in recovery.
Click to expand...
Click to collapse
This could be it. I don't know if there was already the Venom ROM in use. Could be.
redpoint73 said:
Its been that way for months now. But your hboot version is old; so firewater might work, might not. Worth a few tries; as firewater is free and doesn't take long. If it still fails, you need to use sunshine to s-off.
Click to expand...
Click to collapse
Okay I'll try it with firewater again.
Thanks for your help
EDIT: After I flashed the Nadroid Backup, do I have to wipe something, like Dalvik or anything?
3fiddy said:
EDIT: After I flashed the Nadroid Backup, do I have to wipe something, like Dalvik or anything?
Click to expand...
Click to collapse
I wipe Dalvik and cache when I flash anything.
Recovery will wipe system as it flashed the ROM. No need to do so manually.
If restoring a nandroid without data partition backed up, you may or may not have to wipe user data. It might not play well with the restored ROM, but it depends on what ROM you are coming from. If error occur, wipe data and restore again.
If you are restoring a nandroid with data partition backup, it will be wiped during restore. No need to do so manually.
Alright I flashed my own stock nandroid backup. Guess I just read something wrong because I thought it will get the latest Venom Update.
Then I downloaded and installed the latest updates. Now the phone has finally Android 4.4.
After everything went good, I flashed the twrp recovery, made a Backup, rooted the phone, did another backup and flashed the latest Venom ROM.
Before flashing something I wiped everything, like you said.
All is good now.
I think now I can totally forget to gain S-OFF with firewater. But I'll save the link to sunshine. Maybe I'll give it a try
Thanks again everyone, couldn't have done it without your help
Hello,
I am looking for the stock ROM for my HTC ONE M8 because I had a few issues before and I put the first ROM that worked. Because my phone is S-On still it was difficult to find a ROM.
I am currently on a 4.4.4 ROM which has no check for updates feature so when Android L is pushed onto my device I won't be able to get it.
My HTC One M8 is a European version and is currently unlocked to all networks. I've tried to install the official HTC ROM from the website but it hangs and nothing updates, on my task manager I can see the CPU is busy but it does nothing.
Android Version : 4.4.4
HTC Sense version : 6.0
Software number : Android Revolution HD 22.1 by mike1986
Baseband bersion 1.22.2133147A1
Build number : 3.28.401.9
have you read this page: http://forum.xda-developers.com/showthread.php?t=2701376 ?
nathankk said:
I am looking for the stock ROM for my HTC ONE M8 because I had a few issues before and I put the first ROM that worked. Because my phone is S-On still it was difficult to find a ROM.
Click to expand...
Click to collapse
Why? You can flash any M8 ROMs with s-on. And since it appears your firmware is up to date, you can flash any of the latest ROMs with any firmware mismatch issues.
nathankk said:
I am currently on a 4.4.4 ROM which has no check for updates feature so when Android L is pushed onto my device I won't be able to get it.
Click to expand...
Click to collapse
Custom ROMs won't get official OTAs.
Also, in addition to returning to stock ROM, you need to revert to stock recovery to install any OTAs. Its all described in the thread linked in the previous response.
redpoint73 said:
Why? You can flash any M8 ROMs with s-on. And since it appears your firmware is up to date, you can flash any of the latest ROMs with any firmware mismatch issues.
Custom ROMs won't get official OTAs.
Also, in addition to returning to stock ROM, you need to revert to stock recovery to install any OTAs. Its all described in the thread linked in the previous response.
Click to expand...
Click to collapse
I was under the impression with,S-On you can't flash any ROM onto it. Can I literally choose any of those CIDs and it will be compatible with my phone? Instead of messing around can I just wait for the release of lollipop and then flash the ROM that gets posted on here. I just got a little confused because on that post it has carrier names and my phone is unlocked to all networks.
nathankk said:
I was under the impression with,S-On you can't flash any ROM onto it. Can I literally choose any of those CIDs and it will be compatible with my phone? Instead of messing around can I just wait for the release of lollipop and then flash the ROM that gets posted on here. I just got a little confused because on that post it has carrier names and my phone is unlocked to all networks.
Click to expand...
Click to collapse
I think you are talking about flashing firmware or a RUU ? No... If you're s-on, you can only flash your CID. But that has nothing to do with custom roms... Which is what the others have been talking about. ?
Darth said:
I think you are talking about flashing firmware or a RUU ? No... If you're s-on, you can only flash your CID. But that has nothing to do with custom roms... Which is what the others have been talking about.
Click to expand...
Click to collapse
I'm on a custom ROM now I believe and I'm wanting to return to stock, I want to be sure before I do anything so I don't brick the phone. How do I find which CID I need to download?
nathankk said:
I was under the impression with,S-On you can't flash any ROM onto it. Can I literally choose any of those CIDs and it will be compatible with my phone?
Click to expand...
Click to collapse
Any of the stock nandroids should work (meaning they will function). But if you want the stock ROM for your CID, than obviously you need to determine the CID and restore the corresponding stock nandroid.
One reason to restore to your stock nandroid, is that if you also restore the corresponding stock recovery you will be able to receive official OTAs.
nathankk said:
Instead of messing around can I just wait for the release of lollipop and then flash the ROM that gets posted on here.
Click to expand...
Click to collapse
Yes and no. You can flash any custom ROM, including upcoming LP Sense ROMs. But what complicates the issue is that HTC has updated the firmware (hboot, radio, WiFI, etc.) for every major OS software update. If you don't update the firmware accordingly, flashing a ROM that depends on that firmware will result in some major issues (such as long boot times and broken WiFi).
Updating firmware manually requires s-off (which may be the reason why you are under the impression that ROMs can't be flashed with s-on). Or alternately, you can return to stock ROM and recovery and OTA when the LolliSense update rolls out; and this will also update the firmware.
Keep in mind, as previously mentioned your current firmware will work with any current custom ROMs that depend on 3.x firmware.
nathankk said:
I just got a little confused because on that post it has carrier names and my phone is unlocked to all networks.
Click to expand...
Click to collapse
Regardless of the fact your phone is not carrier branded, it still has a CID, probably HTC__ something or other.
fastboot getvar all will yield your CID. No need to post your getvar data, just look for where it says CID. If you post getvar data, be sure to delete IMEI and serial number, as these are personal data that should not be posted on the internet.
redpoint73 said:
Any of the stock nandroids should work (meaning they will function). But if you want the stock ROM for your CID, than obviously you need to determine the CID and restore the corresponding stock nandroid.
One reason to restore to your stock nandroid, is that if you also restore the corresponding stock recovery you will be able to receive official OTAs.
Yes and no. You can flash any custom ROM, including upcoming LP Sense ROMs. But what complicates the issue is that HTC has updated the firmware (hboot, radio, WiFI, etc.) for every major OS software update. If you don't update the firmware accordingly, flashing a ROM that depends on that firmware will result in some major issues (such as long boot times and broken WiFi).
Updating firmware manually requires s-off (which may be the reason why you are under the impression that ROMs can't be flashed with s-on). Or alternately, you can return to stock ROM and recovery and OTA when the LolliSense update rolls out; and this will also update the firmware.
Keep in mind, as previously mentioned your current firmware will work with any current custom ROMs that depend on 3.x firmware.
Regardless of the fact your phone is not carrier branded, it still has a CID, probably HTC__ something or other.
fastboot getvar all will yield your CID. No need to post your getvar data, just look for where it says CID. If you post getvar data, be sure to delete IMEI and serial number, as these are personal data that should not be posted on the internet.
Click to expand...
Click to collapse
Fantastic reply! let me buy you a beer.
nathankk said:
Fantastic reply! let me buy you a beer.
Click to expand...
Click to collapse
Heh, while I love beer, gratitude by clicking the "Thanks" button is enough!
OP, check the link in my signature. Full guide to go back to stock with the EU M8 (most of it will work with S-ON as well)
redpoint73 said:
Yes and no. You can flash any custom ROM, including upcoming LP Sense ROMs. But what complicates the issue is that HTC has updated the firmware (hboot, radio, WiFI, etc.) for every major OS software update. If you don't update the firmware accordingly, flashing a ROM that depends on that firmware will result in some major issues (such as long boot times and broken WiFi).
Updating firmware manually requires s-off (which may be the reason why you are under the impression that ROMs can't be flashed with s-on). Or alternately, you can return to stock ROM and recovery and OTA when the LolliSense update rolls out; and this will also update the firmware.
Keep in mind, as previously mentioned your current firmware will work with any current custom ROMs that depend on 3.x firmware.
Click to expand...
Click to collapse
Heads up, as of early this week (Monday?) the Dev Edition M8 is rolling out Lollipop Sense via OTA. Some custom ROMs have now updated to this base, which is 4.16 software, and requires 4.16 firmware.
But as mentioned, any 3.x software based ROM will work on your current firmware.
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).