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
hi all
my friend tried to update his phone, and all he's got is:
the phone can't boot into recovery. stuck on "entering recovery"
insert coin rom (v 3.0.8) works fine, except the play store!
i tried to flash a new recovery with no success. finally i flash a twrp by captain throwback version 2.8.0.6, and wow it works!
now, i'm wanna to update his M8 to least android version.
fastboot getvar all:
m8_ul
s-on
CID: HTC__K18
MID: 0P6B10000
HBOOT: 3.16.0.0000
version main: empty
settings >> about >> software information:
android version 4.4.2
sense 6.0
InsertCoin version 3.0.8
build number 1.54.401.10
can i simply flash 4.16.401.10 firmware.zip, least TWRP version, ARHD 34.0 (don't worry i don't forget the boot.img )
or
it's better to return to stock and perform software updates?
by the way,
the build number in settings, is the current firmware.zip that installed? or the firmware that the rom based on??
thank's
i read somewhere that its safer to flash firmwares in row, start at 1.54.401.10 then the others in the x.xx.401.xx line
you can also try simply to flash the latest RUU. maybe you get some wifi errors.
i was on 3.xx.401 firmware and installed the 4.x DEV RUU without any errors
yeah the build number in settings shows the rom base.
ok, thanks
erislav said:
yeah the build number in settings shows the rom base.
Click to expand...
Click to collapse
so, i cannot know the exact firmware he has..
i'm asked that because the safest way to update is going back to stock. i found only 1.54.401.5 NAND Backups.
i'm afraid to flash the wrong nand backup..
how can i know which firmware he has?
http://forum.xda-developers.com/showthread.php?t=2701376
If you want to go the save way Try the 1.54.401.x RUU.exe from the thread. Then you should be fine to apply the otas
Dont be to afraid from flashing wrong files in most cases your phone wont get bricked it just dont boot up
erislav said:
http://forum.xda-developers.com/showthread.php?t=2701376
If you want to go the save way Try the 1.54.401.x RUU.exe from the thread. Then you should be fine to apply the otas
Dont be to afraid from flashing wrong files in most cases your phone wont get bricked it just dont boot up
Click to expand...
Click to collapse
sorry about all of my questions but, i found there only 1.54.1540.10 RUU EXE
not 401 ..
TUR_G7 said:
hi all
my friend tried to update his phone, and all he's got is:
the phone can't boot into recovery. stuck on "entering recovery"
insert coin rom (v 3.0.8) works fine, except the play store!
i tried to flash a new recovery with no success. finally i flash a twrp by captain throwback version 2.8.0.6, and wow it works!
now, i'm wanna to update his M8 to least android version.
fastboot getvar all:
m8_ul
s-on
CID: HTC__K18
MID: 0P6B10000
HBOOT: 3.16.0.0000
version main: empty
settings >> about >> software information:
android version 4.4.2
sense 6.0
InsertCoin version 3.0.8
build number 1.54.401.10
can i simply flash 4.16.401.10 firmware.zip, least TWRP version, ARHD 34.0 (don't worry i don't forget the boot.img )
or
it's better to return to stock and perform software updates?
by the way,
the build number in settings, is the current firmware.zip that installed? or the firmware that the rom based on??
thank's
Click to expand...
Click to collapse
Version main is empty because of the older recovery. Try to flash TWRP 2.8.4.0 again.
You can't flash the firmware zip without being S-Off. Sunshine is the only way to do it now, and it costs $25 (totally worth it). Or you could return to stock and take the OTAs. (stock ROM and recovery plus unmodified system partition)
The build number in settings is in fact the ROM base, and not the current firmware version.
xunholyx said:
Version main is empty because of the older recovery. Try to flash TWRP 2.8.4.0 again.
You can't flash the firmware zip without being S-Off. Sunshine is the only way to do it now, and it costs $25 (totally worth it). Or you could return to stock and take the OTAs. (stock ROM and recovery plus unmodified system partition)
The build number in settings is in fact the ROM base, and not the current firmware version.
Click to expand...
Click to collapse
first thanks for your help!
i will try this tomorrow .
on my m8 I bought sunshine (totally worth it) agree
but before i have s-off i'm flashed new firmware.zip (you have to relock your bootloader)
s-off lets you to flash firmware.zip without Signature and without relock
look at this http://forum.xda-developers.com/showthread.php?t=2696282
TUR_G7 said:
first thanks for your help!
i will try this tomorrow .
on my m8 I bought sunshine (totally worth it) agree
but before i have s-off i'm flashed new firmware.zip (you have to relock your bootloader)
s-off lets you to flash firmware.zip without Signature and without relock
look at this http://forum.xda-developers.com/showthread.php?t=2696282
Click to expand...
Click to collapse
Another part of the problem is that HTC updates incrementally. You can't just leap frog from 4.4.2 to 5.0.1.
Once you get S-Off, you can flash a firmware zip from this thread. @Sneakyghost makes his firmware packages so that you don't have to flash each update one at a time. You can just jump to the newest.
But.....from the readout on the earlier post, it is WWE and there is an RUU for that. It is signed, so it should work. It will only get you to 4.4.4. (3.28.401.9 is the newest on this thread). You could try to flash the Lolly firmware after you have updated to this.
Hey guys, I just got a one x of ebay. The phone is currently running a very buggy cyanogenmod version m12. android 4.4.4. baseband 5.1204.167.31 it is rooted and the bootloader is unlocked. I have tried loads of different stock roms and ruu files without any joy. I wish I just bought a stock version of this phone as the seller sold it as working but a "test" build so I have no comeback.
Any help would be fantastic thanks
nikonite said:
Hey guys, I just got a one x of ebay. The phone is currently running a very buggy cyanogenmod version m12. android 4.4.4. baseband 5.1204.167.31 it is rooted and the bootloader is unlocked. I have tried loads of different stock roms and ruu files without any joy. I wish I just bought a stock version of this phone as the seller sold it as working but a "test" build so I have no comeback.
Any help would be fantastic thanks
Click to expand...
Click to collapse
What CID you have? You can find stock version of bootloader, recovery and rom at mike1986 https://www.androidfilehost.com/?w=files&flid=25113. Then you can download and install OTA to 4.18.401.4. There's also deodexed version of that OTA somewhere in forum.
Hey lesmil, CID is hg3_001 (hg3_uk)
nikonite said:
Hey lesmil, CID is hg3_001 (hg3_uk)
Click to expand...
Click to collapse
Well, latest nandroid backup for your CID is 3.14.771.34 https://docs.google.com/file/d/0B6Nhau4n1i__NWN6VTQxcWgzbkk/edit?usp=sharing (CID H3G__001), which is too old ^^. And what's h-boot version? 1.72.0000 ? If so, download those stock files from my previous post and go ahead with them.
If you are going to use this Stock ROM version, download Philz Touch recovery 5.15.9 http://fs1.d-h.st/download/00073/Hue/philz_touch_5.15.9-endeavoru.zip. Newer versions are for KitKats.
Use stock boot.img and stock rom (original OTA 4.18.401.4 for odexed stock is here: http://forum.xda-developers.com/showpost.php?p=52644588&postcount=935; deodexex OTA for deodexed stock is here http://forum.xda-developers.com/showthread.php?t=2754344. Flash OTA thru philz touch recovery. I guess you want to use root, that's why I am mentioning philz touch recovery and not a stock one
Thanks again Lesmil, yes hboot is 1.72.0000, can i restore the nandroid backup from twrp by placing it in the backups folder? My pc will not recognise the phone in adb with the google drivers installed. It does however find it as a fastboot device. I have only been at this two days and am learning but this is all quite new to me. If I could only show you my bookmarks, I have around 100 and understand about 5% of the content
nikonite said:
Thanks again Lesmil, yes hboot is 1.72.0000, can i restore the nandroid backup from twrp by placing it in the backups folder? My pc will not recognise the phone in adb with the google drivers installed. It does however find it as a fastboot device. I have only been at this two days and am learning but this is all quite new to me. If I could only show you my bookmarks, I have around 100 and understand about 5% of the content
Click to expand...
Click to collapse
I wouldn't go thru nandroid, as you have latest hboot, so i guess it might get bricked. I am not sure, maybe I am mistaken But if you download those Stock files from my first post and OTA and Custom recovery from second post, you are going to have stock version and you can root your Stock ROM If you don't want to root then use everything stock and you will be able to download OTa update regullary. You can read my newbie thread : http://forum.xda-developers.com/showthread.php?t=2525341.
On attachment of this post you can find latest HTC driver I have and fastboot files.
Thanks so much to lesmil who took the time to PM me with full instructions. I am now back to stock and much happier
Hi - I really hope someone can help me!
I have a unlocked UK HTC 10, I rooted sometime ago. Anyway, in preparation for the upcoming Nougat release, I wanted to be sure to be able to receive the OTA so I decided to go back to stock.
I (stupidly) flashed stock firmware 1.80.401.3 from within TWRP and then restored stock recovery (this was my mistake).
Now I can use the phone, but cannot take OTA's. Checking versions using fastboot getvar all, I have:
version-main: 1.95.401.4
mid: sp2620000
cid: htc_001
I cannot flash any updates as they are older than 1.95.401.4 (im s-on). I believe all Ill need to do is flash 1.95.401.4 again to restore OTA and get the versions to tally up - however my SD card i backed upto has died and I cannot find 1.95.401.4 anywhere.
Can any one help please with a 1.95.401.4 update or twrp backup?
I hope some one can! Or another solution to get this working please?
Many thanks in advance
dabbler77 said:
Hi - I really hope someone can help me!
I have a unlocked UK HTC 10, I rooted sometime ago. Anyway, in preparation for the upcoming Nougat release, I wanted to be sure to be able to receive the OTA so I decided to go back to stock.
I (stupidly) flashed stock firmware 1.80.401.3 from within TWRP and then restored stock recovery (this was my mistake).
Now I can use the phone, but cannot take OTA's. Checking versions using fastboot getvar all, I have:
version-main: 1.95.401.4
mid: sp2620000
cid: htc_001
I cannot flash any updates as they are older than 1.95.401.4 (im s-on). I believe all Ill need to do is flash 1.95.401.4 again to restore OTA and get the versions to tally up - however my SD card i backed upto has died and I cannot find 1.95.401.4 anywhere.
Can any one help please with a 1.95.401.4 update or twrp backup?
I hope some one can! Or another solution to get this working please?
Many thanks in advance
Click to expand...
Click to collapse
If you're s-on how you flashed older version of firmware? Besides you can't flash firmware in recovery.
I think you should wait for new android nougat ruu and flash it. You will be able to get RUU after official update.
You can flash this android nougat ruu 2.28.401.9,
but it's not official, leaked version.
https://forum.xda-developers.com/htc-10/how-to/wwe-htc-10-stock-rom-ruu-2-28-401-9-t3525075
That could be along wait. If someone has 1.95.404.4 I should be able to restore to it using twrp??
adriano25028 said:
If you're s-on how you flashed older version of firmware? Besides you can't flash firmware in recovery.
I think you should wait for new android nougat ruu and flash it. You will be able to get RUU after official update.
Click to expand...
Click to collapse
TWRP flashes OTA now
afuller42 said:
TWRP flashes OTA now
Click to expand...
Click to collapse
Ok, Twrp flahes OTA, not full update - I mean firmware too, it's only system update.
Can any one please help? A twrp system backup of 1.95.401.4 should fix my issue! Thanks!
Looks like you need an untouched system image + boot image which is available here
https://forum.xda-developers.com/ht...ry-ruu-ota-t3359297/post69259321#post69259321
restoring the above will make you device eligible to receive otas, if you get an "unexpected error" when attempting to install the ota then you will need to flash this
https://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
there are no ruu's available for 1.95.401.x (latest being 1.90.401.5)
Diz said:
Looks like you need an untouched system image + boot image which is available here
https://forum.xda-developers.com/ht...ry-ruu-ota-t3359297/post69259321#post69259321
restoring the above will make you device eligible to receive otas, if you get an "unexpected error" when attempting to install the ota then you will need to flash this
https://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
there are no ruu's available for 1.95.401.x (latest being 1.90.401.5)
Click to expand...
Click to collapse
You sir are a star, thankyou ever so much. All restored and working at 1.95.401.4. I wont know if OTA's are working yet as this is the latest software in the UK (i think?) Im sure hope it does!
Thanks again.
I wanted to root my HTC One M8 to uninstall unnecessary applications. I describe the procedure that I survived:
1- I unlock the HTC One M8 bootloader
2- I installed the CWM Recovery: recovery-clockwork-6.0.4.8-m8.img
3- I proceeded to the root with UPDATE-SuperSU-v2.46.zip
And at restart it's where everything gets complicated. It remains stuck on the logo of the boot and can not restart anything. I left for more than an hour to see but nothing moved.
I managed to enter bootloader by associating the volume + and Power key to restart, and when the phone turns off before restarting I do volume- and power.
And the I'm stuck I know more manipulation to make my HTC one M8 work again.
Is the phone ****ing kind unrecoverable?
How to recover my phone?
Help me please
The files (custom recovery and SuperSU) you used are horribly outdated. Unless your current firmware is something like Kitkat, the stuck on boot situation is expected.
Additionally, CWM never officially supported this phone, and that in itself may cause some problems (in addition to being outdated as well).
Correct versions depends on your current firmware number. Most folks (but not all) are on Marshmallow at this point. But you can tell us more by posting what it says for OS number on the bootloader screen. Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
But likely, you should use a TWRP version 2.8.7 or later. And SuperSU 2.79 or later. Or Magisk to root (latest is 13.3, which should work).
redpoint73 said:
The files (custom recovery and SuperSU) you used are horribly outdated. Unless your current firmware is something like Kitkat, the stuck on boot situation is expected.
Additionally, CWM never officially supported this phone, and that in itself may cause some problems (in addition to being outdated as well).
Correct versions depends on your current firmware number. Most folks (but not all) are on Marshmallow at this point. But you can tell us more by posting what it says for OS number on the bootloader screen. Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
But likely, you should use a TWRP version 2.8.7 or later. And SuperSU 2.79 or later. Or Magisk to root (latest is 13.3, which should work).
Click to expand...
Click to collapse
Yes indeed I had chosen the wrong files (custom recovery and SuperSU). The phone was on Marshmallow. I opted for a simple solution: to install a stock rom Android Jelly Bean 4.4.2 and wait for the update Marshmallow. But before I have installed last version of TWRP. After installing my rom stock, I installed stock recovery and I relock the bootloader.
thank you for your help
Koukougnon said:
I opted for a simple solution: to install a stock rom Android Jelly Bean 4.4.2 and wait for the update Marshmallow.
After installing my rom stock, I installed stock recovery and I relock the bootloader.
Click to expand...
Click to collapse
I don't think this will work. Your firmware indicated by OS number (in bootloader, not in OS Settings) will still read as updated (MM) and you won't be prompted to update.
Additionally, just as FYI, it is not necessary to relock the bootloader for an OTA update, only for RUU or flashing stock signed firmware.
Stuck on HTC logo screen due to old version TWRP and SuperSU, can often be fixed simply by using the proper updated files. But in the current condition, you will need to unlock the bootloader again. In light of that, it might make sense to restore by RUU (if you version has one - you haven't provided the info requested) or otherwise restore to MM (so ROM matches your firmware) before trying to root again.
Excuse me for my absence. I need your help.
As I said earlier, I opted to go back to a Stock ROM.
Actually as you said, I can not install the update to Marshmallow. It downloads the update but it crashes at installation.
I am sending you the information you requested:
OS number on the bootloader
*** Software statut: Modified ***
*** UNLOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8674_FO.1015
OS-6.12.401.4
eMMC-boot 2048MB
Dec 17 2015, 14:15:48.0
fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 1.29.214500021.12G
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.12.401.4
INFOversion-misc: PVT SHIP S-ON
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: m8_ul
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B10000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 76df2b54
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.024s
I still have the TWRP installed and unlock bootloader
Can you help me?
Koukougnon said:
Excuse me for my absence. I need your help.
As I said earlier, I opted to go back to a Stock ROM.
Actually as you said, I can not install the update to Marshmallow. It downloads the update but it crashes at installation.
Click to expand...
Click to collapse
No surprise there. It's best you follow the advice given, instead of making up your own solutions, unless you really know what you are doing. This device has a lot of nuances, and what seems like common sense or a simple solution, often doesn't apply.
OTAs will not install on this device with TWRP, but rather require stock recovery. But it probably doesn't matter, as I stated before, since you are trying to load an update (ROM + firmware), when the firmware is already updated (even if the ROM is not updated), it will likely not install. Basically you have mismatched components, and this will prevent the update from installing. ROM is older, but firmware is updated (version main in getvar indicates firmware is Marshmallow 6.12.401.4).
Koukougnon said:
I still have the TWRP installed and unlock bootloader
Click to expand...
Click to collapse
What version TWRP? You mentioned before the "latest" but did not give a version number. I've had a lot of cases where folks thing they have the "latest" but when prompted for specific version number, it turns out to be an old version.
Just want to be sure before we proceed. After all, the other files you used are going on 3 years old.
redpoint73 said:
No surprise there. It's best you follow the advice given, instead of making up your own solutions, unless you really know what you are doing. This device has a lot of nuances, and what seems like common sense or a simple solution, often doesn't apply.
OTAs will not install on this device with TWRP, but rather require stock recovery. But it probably doesn't matter, as I stated before, since you are trying to load an update (ROM + firmware), when the firmware is already updated (even if the ROM is not updated), it will likely not install. Basically you have mismatched components, and this will prevent the update from installing. ROM is older, but firmware is updated (version main in getvar indicates firmware is Marshmallow 6.12.401.4).
What version TWRP? You mentioned before the "latest" but did not give a version number. I've had a lot of cases where folks thing they have the "latest" but when prompted for specific version number, it turns out to be an old version.
Just want to be sure before we proceed. After all, the other files you used are going on 3 years old.
Click to expand...
Click to collapse
I had installed a stock recovery and relocked the bootloader after installing the rom stock. I received an update for Marshmallow but that crashed at the installation.
After I wanted to install a Rom Custom Nougat for HTC M8, so I unlocked the bootloader, installed TWRP (version twrp-3.1.1-0-m8) then root with SuperSU (the SR1-SuperSU-v2 version. 82-SR1-20170608224931). I installed the rom that no more.
So I reinstalled the rom stock Jelly Bean 4.4.2. That's why I have the TWRP installed and the bootloader unlocked.
Koukougnon said:
.
After I wanted to install a Rom Custom Nougat for HTC M8, so I unlocked the bootloader, installed TWRP (version twrp-3.1.1-0-m8) then root with SuperSU (the SR1-SuperSU-v2 version. 82-SR1-20170608224931). I installed the rom that no more.
Click to expand...
Click to collapse
I'm not sure what that means (what the problem was after flashing the custom ROM). You may have some words missing/wrong in the last sentence.
Flashing the custom ROM should work (seems that it was the real goal here). Did you also flash gapps (Google Apps) which is normally required for AOSP type ROMs? This (or trying a different gapps) is a frequent cause for an AOSP ROM not booting after flashing.
If you still want to return to stock, restore the stock TWRP backup from the collection, using the instructions and files on the following thread. Only need to do through Step 9, and reboot: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Also, keep in mind best practice is to make a TWRP backup of your stock ROM, before trying to root of flash a custom ROM. If you did that, returning to stock would have been as easy as restoring the backup you made.
redpoint73 said:
I'm not sure what that means (what the problem was after flashing the custom ROM). You may have some words missing/wrong in the last sentence.
Flashing the custom ROM should work (seems that it was the real goal here). Did you also flash gapps (Google Apps) which is normally required for AOSP type ROMs? This (or trying a different gapps) is a frequent cause for an AOSP ROM not booting after flashing.
If you still want to return to stock, restore the stock TWRP backup from the collection, using the instructions and files on the following thread. Only need to do through Step 9, and reboot: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Also, keep in mind best practice is to make a TWRP backup of your stock ROM, before trying to root of flash a custom ROM. If you did that, returning to stock would have been as easy as restoring the backup you made.
Click to expand...
Click to collapse
The problem I had with the Custom Rom was that I could not see my Sim contacts. It was a Rom Mokee 7.1.2 for HTC M8.
And I did not backup either the Rom Stock or the Custom Rom.
That's why I installed the Rom Stock 4.4.2 again
Can I install a RUU for HTC M8?
I found this zip file : 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
Koukougnon said:
The problem I had with the Custom Rom was that I could not see my Sim contacts. It was a Rom Mokee 7.1.2 for HTC M8.
Click to expand...
Click to collapse
The description of events that got you to the current condition, gets more and more convoluted every time you post.
Not critical in this case (returning to stock is fairly simple, and doesn't rely that much on the history). But for other issues, conveying the information this way could be a real problem for those trying to help you.
Koukougnon said:
Can I install a RUU for HTC M8?
I found this zip file : 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
Click to expand...
Click to collapse
You can. It would require relocking the bootloader. Then if you want TWRP, root or custom ROM, you will need to unlock the bootloader again after RUU. RUU will also wipe all data on the phone.
Must flash with SD card method, or using htc_fastboot
Not gaining much versus what I previously recommended, especially if you want to still have TWRP for root, custom ROM, etc.
redpoint73 said:
The description of events that got you to the current condition, gets more and more convoluted every time you post.
Not critical in this case (returning to stock is fairly simple, and doesn't rely that much on the history). But for other issues, conveying the information this way could be a real problem for those trying to help you.
You can. It would require relocking the bootloader. Then if you want TWRP, root or custom ROM, you will need to unlock the bootloader again after RUU. RUU will also wipe all data on the phone.
Must flash with SD card method, or using htc_fastboot
Not gaining much versus what I previously recommended, especially if you want to still have TWRP for root, custom ROM, etc.
Click to expand...
Click to collapse
I understand I was wrong at first to solve my problem. I got into that. I did not think well before applying the solutions. Thank you for your help.
So, if I understood correctly to flash the RUU,
- relocked the bootloader
- to be S-ON
- flash by SD Card or Fastboot
Should I install a recovery stock before relocking the bootloafer?
My comments/responses below in red font:
Koukougnon said:
So, if I understood correctly to flash the RUU,
- relocked the bootloader yes, using fastboot command: fastboot oem lock
- to be S-ON It's not a requirement to be s-on, but it's your current condition. With s-off, the requirement to lock the bootloader is bypassed (and RUU still works).
- flash by SD Card or Fastboot Either SD card method, or htc_fastboot specifically. Trying to use the "generic" fastboot will fail since the RUU file is too large. IF you need further info, see here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Should I install a recovery stock before relocking the bootloafer? NO. It's not needed when doing RUU.
Click to expand...
Click to collapse
I managed to flash the RUU with your advice. Everything works well.
The only problem is the recovery. When I go into the recovery it shows me a red triangle and nothing happens. But I intend to install the TWRP.
Thank you for your help.
Koukougnon said:
I managed to flash the RUU with your advice. Everything works well.
The only problem is the recovery. When I go into the recovery it shows me a red triangle and nothing happens.
Click to expand...
Click to collapse
That isn't a "problem", it is working as it should. It's the stock recovery. Press vol up and tap the power button to show the recovery menu options (although not much you can do in stock recovery).
Koukougnon said:
Thank you for your help.
Click to expand...
Click to collapse
You're welcome. Please click the "Thanks" button for any post you found helpful.
Some advice and "best practices" as it seems that you've missed a lot of important info when trying to mod the phone:
1) Always research the most up to date info on rooting a device, before you start anything. Files are updated often, and using old methods can (and will) lead to a lot of problems. I know a lot of the info for this device is outdated, or not entirely organized. So feel free to ask questions if you are confused.
2) Always make a TWRP backup of your stock ROM, before doing any mods (root, custom ROM, etc.).
3) Always know how to return to stock, before doing the mods.
4) At least for this device, after installing TWRP, you don't need to root, if you are then going to immediately flash a custom ROM. In other words, you don't need root to flash a ROM. Most ROMs are pre-rooted But the few that are not, you need to flash root (SuperSU or Magisk) after you flash the ROM.
redpoint73 said:
That isn't a "problem", it is working as it should. It's the stock recovery. Press vol up and tap the power button to show the recovery menu options (although not much you can do in stock recovery).
You're welcome. Please click the "Thanks" button for any post you found helpful.
Some advice and "best practices" as it seems that you've missed a lot of important info when trying to mod the phone:
1) Always research the most up to date info on rooting a device, before you start anything. Files are updated often, and using old methods can (and will) lead to a lot of problems. I know a lot of the info for this device is outdated, or not entirely organized. So feel free to ask questions if you are confused.
2) Always make a TWRP backup of your stock ROM, before doing any mods (root, custom ROM, etc.).
3) Always know how to return to stock, before doing the mods.
4) At least for this device, after installing TWRP, you don't need to root, if you are then going to immediately flash a custom ROM. In other words, you don't need root to flash a ROM. Most ROMs are pre-rooted But the few that are not, you need to flash root (SuperSU or Magisk) after you flash the ROM.
Click to expand...
Click to collapse
I understood well. Thank you.