I need help before i snap this thing over my knee. lol
Right i am very tech savvy but still a bitt noob when it comes to flashing etc. So basically, i rooted, several times my one x and finally landed
on the viper x rom and upon using the multi shot on my camera it caused a fatal error on my inbuilt SD and bricked my phone. I am now trying to
restore to official vodafone RUU so i can return this thing as this is the second time this has happened now.
However i am getting error 140 Bootloader error. Can someone please help.
C:\onexroot>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.12.0000
(bootloader) version-baseband: 1.1204.105.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.161.4
(bootloader) serialno: HT24DW118008
(bootloader) imei: 359188049780711
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3930mV
(bootloader) devpower: 70
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
Thanks
Kris
I'm guessing you've relocked your bootloader and flashed stock recovery before trying to flash the RUU?
Plus a quick search shows Error 140 means the RUU you're trying to flash has an older bootloader than the one on the phone.
Are you sure the RUU you have matches your version on your phone? (2.17.161.4)
Brownie2k said:
I'm guessing you've relocked your bootloader and flashed stock recovery before trying to flash the RUU?
Plus a quick search shows Error 140 means the RUU you're trying to flash has an older bootloader than the one on the phone.
Are you sure the RUU you have matches your version on your phone? (2.17.161.4)
Click to expand...
Click to collapse
Nope the RUU is older something like 1.4.xxxx the problem is there doesnt seem to be any RUU above 2 let alone 2.17 does this mean im goosed? and yeah ive relocked boot loader flashed stock recovery although it will let let me flash boot.img i just get access denied when i try that.
You can't flash a boot.img with a locked bootloader as far as i know.
That will be why you're getting the Error 140, the bootloader on the RUU is older than the one on your phone. You can only flash the equivilent or higher bootloader.
I know there is a few OTA's out there for carriers, but not sure if it'll help you. I'm sure someone else with more knowledge of flashing RUU's will be able to help more.
Probably a silly question, but don't you have a CW backup from before flashing Viperx that you can restore via recovery? It's the way I went back to stock and possibly the best thing you can do if you have a rooted phone...
Kutusov said:
Probably a silly question, but don't you have a CW backup from before flashing Viperx that you can restore via recovery? It's the way I went back to stock and possibly the best thing you can do if you have a rooted phone...
Click to expand...
Click to collapse
Well.... Thats the funny bit. Its was saved to the sd card *facepalm* Which has now corrupted and had to be formatted so no more backup. The bit I am stuck on is how i get back to stock firmware. The only RUU with a higher hboot than current is HTC ONE X EUROPE but that one wont flash because the CID doesn't match and i don't know how to fix. Hate my life! lol
Unlock bootloader
Flash latest cwm you can mount sd card and Copy a rom over
Flash boot.img
Flash rom fixed
Heres a tool to help you with every step
http://forum.xda-developers.com/showthread.php?t=1734365
Heres stock rom
http://forum.xda-developers.com/showthread.php?t=1546970
Sent from my HTC One X using xda premium
---------- Post added at 12:37 PM ---------- Previous post was at 12:33 PM ----------
And my fav
http://forum.xda-developers.com/showthread.php?t=1705334
Sent from my HTC One X using xda premium
joewong1991 said:
Unlock bootloader
Flash latest cwm you can mount sd card and Copy a rom over
Flash boot.img
Flash rom fixed
Heres a tool to help you with every step
http://forum.xda-developers.com/showthread.php?t=1734365
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Hey cheers bro for advice but that isnt what im trying to do. The handset is needing to be returned to vodafone and im trying to get it back onto the official vodafone UK endeavouru rom and unroot but the the offieal RUU are only running around about 1.21.x.x.x.x but the viper x rom has but me on 2.17.161.4 which means the RUU is failing because of bootloader error, im still a bit confused on this but it seems i cant downgrade and my handset is NTEGRA 3 international version which mean no S-OFF, no super CID and no HBOOT access hence, pardon the language.. F**cked phone...
No worrys but why do you wont to send it back?
Sent from my HTC One X using xda premium
joewong1991 said:
No worrys but why do you wont to send it back?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Because the guys at Vodafone will just charge me 350 quid if i send it in with a customer rom and custom bootloader on it lol I need it back to stock.
klashnikoff said:
Because the guys at Vodafone will just charge me 350 quid if i send it in with a customer rom and custom bootloader on it lol I need it back to stock.
Click to expand...
Click to collapse
But i dont see why you wont to send it back all you have done is formatted your sd card and lost all you backups i would just install a new rom and start from fresh
Sent from my HTC One X using xda premium
joewong1991 said:
But i dont see why you wont to send it back all you have done is formatted your sd card and lost all you backups i would just install a new rom and start from fresh
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Are sorry i miss read, though it said why dont you, erm because i have one of the faulty ones. Issue with wifi disconnects if you move the phone, spoke to HTC who said some of the One X UK editions have been know to have wifi issues and to contact vodafone for replacement, i was going to just live with it but this is now the 4th maybe 5th time the SD card has currupted, twice was before i even rooted it so theres something wrong me thinks. Thats was why i rooted because i though maybe it was the bloatware damaging the files on the phone but nope looks like ive got a dodgy phone. lol.
klashnikoff said:
Are sorry i miss read, though it said why dont you, erm because i have one of the faulty ones. Issue with wifi disconnects if you move the phone, spoke to HTC who said some of the One X UK editions have been know to have wifi issues and to contact vodafone for replacement, i was going to just live with it but this is now the 4th maybe 5th time the SD card has currupted, twice was before i even rooted it so theres something wrong me thinks. Thats was why i rooted because i though maybe it was the bloatware damaging the files on the phone but nope looks like ive got a dodgy phone. lol.
Click to expand...
Click to collapse
Mate, no matter what you do, HTC will be able to see that you were messing with the phone. Your bootloader will be "RELOCKED", instead of "LOCKED" as in the original unit.
So, whatever the problem is within the phone, they have a reason to charge you for the repair, as the warranty will be void. I even believe it's said on htcdev website, during the unlocking process.
[email protected]|-|oR said:
Mate, no matter what you do, HTC will be able to see that you were messing with the phone. Your bootloader will be "RELOCKED", instead of "LOCKED" as in the original unit.
So, whatever the problem is within the phone, they have a reason to charge you for the repair, as the warranty will be void. I even believe it's said on htcdev website, during the unlocking process.
Click to expand...
Click to collapse
Oh Im well aware of that but this is a contract phone, HTC dont need to touch it, Voda do which coincidently their techs dont check to see whether it is locked/relocked just whether there is custom software on there. I must of had about 6 different handsets rooted then re locked and repaired by vodafone.
klashnikoff said:
HTC dont need to touch it, Voda do which coincidently their techs dont check to see whether it is locked/relocked just whether there is custom software on there.
Click to expand...
Click to collapse
Good for you, mate! Then, search for stock boot.img, stock recovery, and proper RUU, and you're good to go!
[email protected]|-|oR said:
Good for you, mate! Then, search for stock boot.img, stock recovery, and proper RUU, and you're good to go!
Click to expand...
Click to collapse
Well this is what i need help on, im still a bit stumped understanding bootloaders and allsorts, my hboot number is 1.12.0000
but my main version is 2.17.161.4 and when im trying to use the RUU all i get is error message 140 saying that im basically trying to restore to a previous bootloader and this is what im stuck on because the RUU is "Footballs" RUU and is the most recent vodafone UK one. What am i doing wrong. This is where nobody helps me. Thanks for talking to me btw you dont understand how much i apprectaiate this. Oh and ive tried flashing boot.img and system.img before locking and then using RUU but it when i flash system it just says failed :/
klashnikoff said:
Well this is what i need help on, im still a bit stumped understanding bootloaders and allsorts, my hboot number is 1.12.0000
but my main version is 2.17.161.4 and when im trying to use the RUU all i get is error message 140 saying that im basically trying to restore to a previous bootloader and this is what im stuck on because the RUU is "Footballs" RUU and is the most recent vodafone UK one. What am i doing wrong. This is where nobody helps me. Thanks for talking to me btw you dont understand how much i apprectaiate this. Oh and ive tried flashing boot.img and system.img before locking and then using RUU but it when i flash system it just says failed :/
Click to expand...
Click to collapse
Oh, now I see your main issue! Sorry, I disregarded the root cause of your trouble...
What you need is proper RUU only. But, that's easier said than done. Did you search filecatory.com or htcruu.com. There are plenty of RUU's there. But you MUST run 2.17 RUU. So, if Vodaphone didn't release 2.17 update, .. You know what I mean.
The other way you could go is finding custom rom with 1.29 base, flashing that one, then flashing stock boot.img, stock recovery, RELOCKING bootloader (don't forget this!), and then running RUU. Shortly, bringing your base to the one of RUU's.
Aww this is getting wierd now, so im looking down the avenue that we have discussed i remembered i can extract roms from the RUU itself which is how i repaired my phone last time but when i 7-zip into the ROM (bearing in mind this is the latest RUU aswell) the HBOOT .img file is 0.95.0000 ....So how the hell did i get onto 1.12.0000 ?? I havnt ran any RUU or anything and surely the ViperX Rom cant update my hboot image... can it? And the RUU which i am trying to use is the software i was on before i re-rooted.... oh god my head hurts....
I have no idea how you got 1.12 hboot, really. You are right, ViperX should not have anything to do with hboot...
If I were you I wouldn't mess too much with extracting the ROM from RUU. Again, what RUUs did you find? What is their base?
[email protected]|-|oR said:
I have no idea how you got 1.12 hboot, really. You are right, ViperX should not have anything to do with hboot...
If I were you I wouldn't mess too much with extracting the ROM from RUU. Again, what RUUs did you find? What is their base?
Click to expand...
Click to collapse
I have found a few with a 1.21 and 1.22 ans a few 1.29 base but it will not flash the system.img it just fails which apperntly seems to be a common occurance because the system files are to big.
Related
So I'm fairly new to the rooting scene. I had clockworkmod installed and I was unlocked and s-off. There were some weird google sync issues that popped up and I tried a factory reset. It still didn't fix the issues, so I decided to take it back into verizon, but I wanted to get it relocked. so I installed the stock recovery got relocked and s-on. I tried once more for a factory reset and I got stuck in the bootloader with the locked and security warning flags showing. Am I completely out of luck or is there a way that I've missed to get s-off again?
Unlock the bootloader again, then flash twrp or cwm recovery, then flash a rom. Then use firewater to get s-off. Alternativley you could do an ruu, and then use firewater to get unlocked and s-off.
cmlusco said:
Unlock the bootloader again, then flash twrp or cwm recovery, then flash a rom. Then use firewater to get s-off. Alternativley you could do an ruu, and then use firewater to get unlocked and s-off.
Click to expand...
Click to collapse
I appreciate the reply but I just need a little more direction on the first step. I believe rumrunner won't complete because when it tries to reboot the phone to run adb commands it can't since the phone is stuck in the bootloader. When I try to flash a new recovery (be it cwm or twrp) in fastboot the flash fails @ the bootloader signature check. I'm not really sure what that means, but I get it everytime.
Also, I have't found any RUU that is for a Verizon phone. I'm not sure that others will work.
Reading over your reply one more time I think I just need to get that bootloader unlocked, then I can try out everything else but I'm hitting a wall. Any more insight into that?
When you originally unlocked it did you use htcdev to do it? If so they gave you and unlock_token.bin file, do you still have it on your pc somewhere, possibly where fastboot is? If you didnt use htcdev you can try to now http://www.htcdev.com/bootloader. Select all other supported devices in the drop down box on the side, then follow the instructions to try to unlock the bootloader again.
Unfortunately I didn't use htcdev, and the One isn't a supported device anymore. Or at least doesn't seem to be - I get an error:
Error Code: 160.
Error Reason: MID Not Allowed.
Ah that sux. Well you need to try to ruu then, but im having trouble finding the right one. Do me a favor and type this using fastboot
Code:
fastboot getvar all
and post what it outputs here.
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 1.12.41.1112_2
version-cpld: None
version-microp: None
version-main: 2.10.605.1
version-misc: PVT SHIP S-ON
serialno: ***
imei: ***
meid: ***
product: m7_wlv
platform: HBOOT-8064
modelid: PN0731000
cidnum: VZW__001
battery-status: good
battery-voltage: 4264mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-3c88cdd7
hbootpreupdate: 11
gencheckpt: 0
Ok let me look for the rigjt ruu. Also remove your serial ime and meid from that post. Not something you want people to know.
Ok well i got some bad news. I cant find a 2.10.605.1 ruu. I can find older ones but that dosent help, since a s-on hboot wont allow you to downgrade. Im stumped at what to do at this point. Hopefully the correct ruu will be available soon. Mabey someone smarter than me has some other ideas.
Ah, well... hopefully they can come out with it soon I really appreciate you looking into it!
I'm in the same boat. Unsure what to do as I need a phone.
I found a decrypted one, but that wont work with s-on. ?
But if there is a decrypted one, that means there must be a signed one somewhere. I will keep looking.
If you still need the signed 2.10.605.1 RUU.... PM me.. I'll get santod to add link to his thread
Yea you need an encrypted version of the same software build you were on. You can't ruu to a lower version since you are s on. But if you are boot loader locked you won't be able to flash anything.
If you can get the encrypted signed ruu from somewhere you could possibly boot to ruu mode and flash that. Then use firewater to unlock and get s off.
Sent from my HTC6500LVW using Tapatalk 2
Where might i find the correct encrypted signed ruu?
As far as I know only HTC has them and they used to be available here but not any more. See if flyhalf has it somehow.
If you are s on though I'm unsure if you can flash it. But it's worth a try as long as it's the encrypted version and signed...that way all the stock files match the partitions and files on your device currently.
Sent from my HTC6500LVW using Tapatalk 2
Flash a rom in an unlocked bootloader with an on the go external sd card.
Sent from my Galaxy Tab 10.1
Here you guys go. Santod added it to his thread. http://goo.gl/JEkyCk 2.10.605.1 RUU Signed
cmlusco said:
Here you guys go. Santod added it to his thread. http://goo.gl/JEkyCk 2.10.605.1 RUU Signed
Click to expand...
Click to collapse
Nice, thanks for this. I can flash this too right even if I'm s off? Going to download it and keep it in case I ever need to ruu.
Sent from my HTC6500LVW using Tapatalk 2
Yes even if your s-off.
Hi, I am trying to revert my m8 to stock with no root, but I just formatted and wiped my phone, now the only thing I have is an s-on unlocked bootloader and twrp. All the roms I tried installing using TWRP keep saying that the updater binary failed or something. When I try to do RUU, it just doesn't work. Can anyone help me restore functionality to my phone?
Need to provide more info.
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
What ROMs did you try?
What version TWRP?
What RUU? You need to relock the bootloader to RUU. But if its not the right RUU for your version (CID), it won't work and you'll be stuck unlocking the bootloader again. So don't relock the bootloader until you provide all the info requested.
---------- Post added at 02:45 PM ---------- Previous post was at 02:44 PM ----------
TheOnlyLite said:
Hi, I am trying to revert my m8 to stock with no root, but I just formatted and wiped my phone
Click to expand...
Click to collapse
Did you think that would return your phone to stock?
redpoint73 said:
Need to provide more info.
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
What ROMs did you try?
What version TWRP?
What RUU? You need to relock the bootloader to RUU. But if its not the right RUU for your version (CID), it won't work and you'll be stuck unlocking the bootloader again. So don't relock the bootloader until you provide all the info requested.
---------- Post added at 02:45 PM ---------- Previous post was at 02:44 PM ----------
Did you think that would return your phone to stock?
Click to expand...
Click to collapse
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0321
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: fd3e0448
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I just tried a bunch of random ones online tbh. I can't find any that match my phone's CID or MID even thought my CID is 1111111.
I have twrp 2.8.1.0 right now.
I am just trying to get the os working for now because everything I tried flashing didnt work.
You have the Verizon version.
Randomly looking online for ROMs is not a good idea. Stick to XDA, and in your case, stick to the Verizon Dev forums.
Also, what RUUs did you try (don't like asking the same question twice)? If it wasn't a Verizon RUU, you are lucky it didn't work, since any other RUUs can radio brick your phone. Again, flashing random things is not a good idea, especially with s-off and SuperCID, the results can be disastrous.
You have a couple things going on:
1) Your firmware (hboot, radio, etc.) is woefully outdated. It won't work on any of the current ROMs.
2) Only ROMs meant for the Verizon version will work, due to kernel differences.
I'd advise run an Lollipop or Marshmallow Verizon RUU, which will get you to stock, and with updated firmware. I'll see if I can find the VZN RUUs.
EDIT: Here you go: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
redpoint73 said:
You have the Verizon version.
Randomly looking online for ROMs is not a good idea. Stick to XDA, and in your case, stick to the Verizon Dev forums.
Also, what RUUs did you try (don't like asking the same question twice)? If it wasn't a Verizon RUU, you are lucky it didn't work, since any other RUUs can radio brick your phone. Again, flashing random things is not a good idea, especially with s-off and SuperCID, the results can be disastrous.
You have a couple things going on:
1) Your firmware (hboot, radio, etc.) is woefully outdated. It won't work on any of the current ROMs.
2) Only ROMs meant for the Verizon version will work, due to kernel differences.
I'd advise run an Lollipop or Marshmallow Verizon RUU, which will get you to stock, and with updated firmware. I'll see if I can find the VZN RUUs.
EDIT: Here you go: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Click to expand...
Click to collapse
I tried just any RUU that I found that was for the HTC One M8 like things from android revolution, but they all just failed.
Also, I have S-ON right now because of a guide online telling me to do that, but it was wrong. Is there a way I could change it back to S-ON without os?
edit: i tried using the RUU exe on the link you put, but it didn't work and it says to get the correct firmware update utility. I don't know what I'm doing wrong.
TheOnlyLite said:
I tried just any RUU that I found that was for the HTC One M8 like things from android revolution, but they all just failed.
Click to expand...
Click to collapse
Of course, any RUU not intended for the VZN version will fail, by design. You can't run an RUU for a different CID and MID. And I must stress do not change the CID and/or MID in an attempt to flash another version's RUU. As mentioned, if any other RUU actually flashed, it would probably radio brick your phone. VZN version (along with Sprint version) has different radio, partitions, and kernel from all other M8 versions. FOr this reason, RUUs are not interchangeable in your case (VZN version). You should not try to run any RUU except those specifically for the VZN M8.
TheOnlyLite said:
Also, I have S-ON right now because of a guide online telling me to do that, but it was wrong. Is there a way I could change it back to S-ON without os?
Click to expand...
Click to collapse
The guide isn't wrong, if the intent is to return to full stock, for which s-on is the stock condition.
Usually, the only reason to do so (return to s-on) would be if you were trying to return the phone for warranty purposes; which I do not believe is the case for you.
I agree that for the purposes of what you wanted to do, s-on limits your options and was not a good idea.
But no, there is no way to return to s-off with no OS.
TheOnlyLite said:
edit: i tried using the RUU exe on the link you put, but it didn't work and it says to get the correct firmware update utility. I don't know what I'm doing wrong.
Click to expand...
Click to collapse
I don't know what you did wrong either, if you don't specify which file you tried.
If you tried the Marshmallow RUU, you may need to run the corresponding stock MM firmware before you can RUU. Try the LP RUU and see if that works.
redpoint73 said:
Of course, any RUU not intended for the VZN version will fail, by design. You can't run an RUU for a different CID and MID. And I must stress do not change the CID and/or MID in an attempt to flash another version's RUU. As mentioned, if any other RUU actually flashed, it would probably radio brick your phone. VZN version (along with Sprint version) has different radio, partitions, and kernel from all other M8 versions. FOr this reason, RUUs are not interchangeable in your case (VZN version). You should not try to run any RUU except those specifically for the VZN M8.
The guide isn't wrong, if the intent is to return to full stock, for which s-on is the stock condition.
Usually, the only reason to do so (return to s-on) would be if you were trying to return the phone for warranty purposes; which I do not believe is the case for you.
I agree that for the purposes of what you wanted to do, s-on limits your options and was not a good idea.
But no, there is no way to return to s-off with no OS.
I don't know what you did wrong either, if you don't specify which file you tried.
If you tried the Marshmallow RUU, you may need to run the corresponding stock MM firmware before you can RUU. Try the LP RUU and see if that works.
Click to expand...
Click to collapse
So I tried all the RUUs, exe and flashing with rebootRUU. Nothing worked. Would the only way to rename the file to 0P6BIMG.zip and having the phone detect it in my external sd? The exe keeps saying "The Firmware Update Utility cannot update your Android phone." and when I flash using adb or fastboot, it just fails.
edit: Actually I don't even know. I'm pretty dumb when it comes to this kinda stuff. What do you suppose I do step by step? I still have access to bootloader and TWRP, but I just can't flash anything for some reason. Or the roms that I try always end up with an error.
TheOnlyLite said:
So I tried all the RUUs, exe and flashing with rebootRUU. Nothing worked. Would the only way to rename the file to 0P6BIMG.zip and having the phone detect it in my external sd?
Click to expand...
Click to collapse
I wouldn't say the SD card method is the "only way". But if you have an SD card, and a way to put the file on the card (USB card reader) then its probably the easiest way to RUU. At least, the least points of failure, as the exe can be finicky depending on your PC setup, and the fastboot method has some pitfalls as well (more on that below).
TheOnlyLite said:
when I flash using adb or fastboot, it just fails.
Click to expand...
Click to collapse
If you are trying adb commands, there is no method to flash RUUs with adb. You need to use fastboot. If you are using adb, I don't know what you are doing or why.
"It just fails" meaning what? Is there an error message (if so, what is it exactly?) or it just hangs?
Try the method posted here: http://forum.xda-developers.com/htc-one-m8/help/help-htc-one-m8-bricked-t3298412
Not the actual RUU zip posted (its the Euro RUU, not for your Verizon version). But download the htc_fastboot.exe where it says: 2. Download htc_fastboot.exe here : https://drive.google.com/file/d/0B8L...dKVEdHX1U/view
Then do as it says:
Make a folder say "RUU" on your desktop and put both RUU zip and htc_fastboot.exe in this RUU folder
fastboot reboot-bootloader (reboot to bootloader to ensure the connection is good)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip RUU.zip (to install RUU)
TheOnlyLite said:
I still have access to bootloader and TWRP, but I just can't flash anything for some reason. Or the roms that I try always end up with an error.
Click to expand...
Click to collapse
I already stated in Post #4 above that none of the current ROMs will work on your device.
You're also making it harder for folks to help you, if you don't give any details. What ROMs did you try exactly (link them if you can)? What are the specific error messages, and at what point do they fail?
But flashing a ROM is contradictory to what you were originally trying to do (return to stock). Do you want to return to stock, or flash a custom ROM? Is the intent in flashing a ROM to just get the phone back up and running?
You need to pick one path, and stick with it; at least for a bit. Flip flopping back and forth is just going to complicate matters, and cause more problems.
For instance, if the bootloader currently relocked or unlocked? You need to have it relocked in order to RUU (as I previously stated) but having it unlocked is needed if you want to flash custom ROMs.
redpoint73 said:
I wouldn't say the SD card method is the "only way". But if you have an SD card, and a way to put the file on the card (USB card reader) then its probably the easiest way to RUU. At least, the least points of failure, as the exe can be finicky depending on your PC setup, and the fastboot method has some pitfalls as well (more on that below).
If you are trying adb commands, there is no method to flash RUUs with adb. You need to use fastboot. If you are using adb, I don't know what you are doing or why.
"It just fails" meaning what? Is there an error message (if so, what is it exactly?) or it just hangs?
Try the method posted here: http://forum.xda-developers.com/htc-one-m8/help/help-htc-one-m8-bricked-t3298412
Not the actual RUU zip posted (its the Euro RUU, not for your Verizon version). But download the htc_fastboot.exe where it says: 2. Download htc_fastboot.exe here : https://drive.google.com/file/d/0B8L...dKVEdHX1U/view
Then do as it says:
Make a folder say "RUU" on your desktop and put both RUU zip and htc_fastboot.exe in this RUU folder
fastboot reboot-bootloader (reboot to bootloader to ensure the connection is good)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip RUU.zip (to install RUU)
I already stated in Post #4 above that none of the current ROMs will work on your device.
You're also making it harder for folks to help you, if you don't give any details. What ROMs did you try exactly (link them if you can)? What are the specific error messages, and at what point do they fail?
But flashing a ROM is contradictory to what you were originally trying to do (return to stock). Do you want to return to stock, or flash a custom ROM? Is the intent in flashing a ROM to just get the phone back up and running?
You need to pick one path, and stick with it; at least for a bit. Flip flopping back and forth is just going to complicate matters, and cause more problems.
For instance, if the bootloader currently relocked or unlocked? You need to have it relocked in order to RUU (as I previously stated) but having it unlocked is needed if you want to flash custom ROMs.
Click to expand...
Click to collapse
Sorry for being so vague about everything. So I guess all the RUUs that I tried flashing failed because of bootloader. I just relocked it and it worked. It was giving me error: 99 or unknown error when I tried any RUU including stock ones. And right now I just want my phone to work again haha. Now that I have that, I would like to return my phone to non-rooted, because some apps/games I have detect root somehow and I would like to use my phone to access them. After getting a working OS on my phone, how would I be able to return it to stock, and maybe install cyanogenmod?
Thanks for the help.
edit: Actually nevermind. My phone is unrooted now lol. Again thanks for the help
So you were able to successfully RUU? If so, which one?
TheOnlyLite said:
Again thanks for the help
Click to expand...
Click to collapse
There's a button for that.
redpoint73 said:
So you were able to successfully RUU? If so, which one?
There's a button for that.
Click to expand...
Click to collapse
So I flashed the 5.0.1 rom on that first link you provided with the official stock roms, but I'm sure the other ones would have worked. I was severely outdated with the one I flashed and had to update like 10 times to get back to the most recent ota lol.
Morning,
I've been into this phone for two days now, the phone would not Update OTA to Android 6 it was on stock 4.4.4 so I figured I'd install the RUU from HTC's site, I unlocked the bootloader and acquired S-OFF, I tried several RUU's (GEp, UNlocked/dev, android 5, 6, even tried to go back to stock 4.4, I know I'm doing many things wrong so I now ask for direction) since I knew nothing about CID and MID, the exe's did not work and the zips would flash via fastboot oem rebootRUU I even (regrettably) flashed several firmwares as it stands now with most hopes lost my phone has this values:
Bootloader is "relocked" since it was said to be required for RUU.
HTML:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.04.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: eee2521c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also, I can no longer unlock the bootloader using my Unlock_code.bin file, nor can I install a recovery image I get a "FAILED (remote:" error each time.
Thanks.
This is really bad. This looks to be a result of improper research by your part, and I hope the damage is not permanent (although it may possibly be).
Reason I say this, is that your product ID (m8_whl) indicates you have the Sprint version M8. This version is fairly unique (along with Verizon M8) in that its designed to work on the Sprint CDMA network (along with GSM networks). Due to this, the Sprint version has different partitioning and different radios from most other "GSM" M8 versions. And one should never attempt to convert a Sprint M8 to any other version; by flashing another version's RUU or firmware.
I also do not recommend ever changing the MID on the Sprint device (from its original MID), as there is no valid, safe reason to do so (for reasons mentioned above).
Mods with s-off can be extremely dangerous, as they can result in bricking your phone. You may already have a permanent radio brick (as we've seen happen after folks have flashed another version's RUU or firmware to a Sprint M8). The moment you started having trouble flashing an RUU, you should have backed off, and come here for help. Guessing, and trying multiple random things (like RUUs/firmwares) on these devices, especially with s-off, is a recipe for disaster.
When you say "boot loop" do you mean the phone is actually restarting itself over and over to fastboot? Or it simply can't boot to OS, and goes to fastboot (and if you manually reboot it, it goes again to fastboot)?
---------- Post added at 12:10 PM ---------- Previous post was at 12:07 PM ----------
Herzchell said:
Bootloader is "relocked" since it was said to be required for RUU.
Click to expand...
Click to collapse
This is only a requirement when s-on. Relocking the bootloader to RUU not needed when s-off. With s-off, you can RUU with the bootloader unlocked.
---------- Post added at 12:12 PM ---------- Previous post was at 12:10 PM ----------
Herzchell said:
nor can I install a recovery image I get a "FAILED (remote:" error each time.
Click to expand...
Click to collapse
You can try it a million times, and it won't make a difference. You can't install custom recovery with bootloader locked or relocked. That is the exact reason to have a locked bootloader, to prevent custom recovery from being installed.
Thank you for your answer, got the thing unlocked again and restored a previous backup I made, the phone would restart constantly so I flashed the stock kernel for the phone, its back to how it was first.. I think..
The phone appears to be rooted ir something because it still wont update OTA and that was the problem un the first place, any advice?
Herzchell said:
Thank you for your answer, got the thing unlocked again and restored a previous backup I made, the phone would restart constantly so I flashed the stock kernel for the phone, its back to how it was first.. I think..
The phone appears to be rooted ir something because it still wont update OTA and that was the problem un the first place, any advice?
Click to expand...
Click to collapse
for a sprint device with the things you have made you are so lucky :laugh:
Any way all you need is in this thread flash firmware then flash the RUU
https://forum.xda-developers.com/showthread.php?t=2729173
Edit: you maybe need to revert mid to it's stock but try it if it fail revert it
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
for a sprint device with the things you have made you are so lucky :laugh:
Any way all you need is in this thread flash firmware then flash the RUU
https://forum.xda-developers.com/showthread.php?t=2729173
Edit: you maybe need to revert mid to it's stock but try it if it fail revert it
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
OK Ismael, I kind of got that idea last night so I got this file "Sprint_HTC_One_M8_1.54.651.8_RUU.zip" which coincides with the kernel I installed "1.54.651.8", also, this RUU seems to be the oldest they have there so I would think it's as stock and back in time as I'm going to get.
I'm cautious now though, it was hard to get back to where I am now.
Herzchell said:
OK Ismael, I kind of got that idea last night so I got this file "Sprint_HTC_One_M8_1.54.651.8_RUU.zip" which coincides with the kernel I installed "1.54.651.8", also, this RUU seems to be the oldest they have there so I would think it's as stock and back in time as I'm going to get.
I'm cautious now though, it was hard to get back to where I am now.
Click to expand...
Click to collapse
you need the latest not the oldest
download 6.20.651.3 if your device non h/k
Download 6.20.654.3 if your device h/k
either ways you need the firmware and the RUU,pick a version of those according to your device ( it won't harm if you pick wrong ) and flash both firmware and RUU by following the thread instruction
You don't need anything else ( i hope )
and don't relock the bootloader ( you don't need that as long is your device s-off )
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
you need the latest not the oldest
download 6.20.651.3 if your device non h/k
Download 6.20.654.3 if your device h/k
either ways you need the firmware and the RUU,pick a version of those according to your device ( it won't harm if you pick wrong ) and flash both firmware and RUU by following the thread instruction
You don't need anything else ( i hope )
and don't relock the bootloader ( you don't need that as long is your device s-off )
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
Thanks, I'll try that, should I change my CID to install RUU's, I was under the impression that a super CID overrides the need for a specific CID, the RUU I mentioned before complains about "FAILED (remote: 24 parsing android-info fail)"
Herzchell said:
Thanks, I'll try that, should I change my CID to install RUU's, I was under the impression that a super CID overrides the need for a specific CID, the RUU I mentioned before complains about "FAILED (remote: 24 parsing android-info fail)"
Click to expand...
Click to collapse
error 24 means one of the following
1- the .zip is corrupted
2- the .zip is an OTA package ( and it can't be flashed in fastboot mode )
3- android-info.txt have something wrong ( if this is the meant error you will need to change the cid and mid )
so you can tell which one of those is the meant error
about cid it's correct that it eliminate the needs of a specific cid ( and in some cases it passes the mid check )
ahmed.ismael said:
you need the latest not the oldest
download 6.20.651.3 if your device non h/k
Download 6.20.654.3 if your device h/k
Click to expand...
Click to collapse
Since the OP is SuperCID, I believe he can pick either. Same model hardware, the only difference is software.
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
Herzchell said:
The phone appears to be rooted ir something because it still wont update OTA and that was the problem un the first place, any advice?
Click to expand...
Click to collapse
Most US carriers, you can only OTA update if connected to that specific carrier (in this case, Sprint).
That being the case, your best bet is to RUU to latest Marshmallow image, as ahmed instructed.
And since RUU is a fully image (not just an update "patch") it doesn't matter the current configuration (as long as CID, MID checks pass or bypassed). Meaning you don't need to install any "older" RUUs before the current MM one.
Thanks,
The phone is running marshmallow now, the only issue I have now is that the bottom speaker does not reproduce sound.
You have both been very helpful.
Herzchell said:
The phone is running marshmallow now, the only issue I have now is that the bottom speaker does not reproduce sound.
Click to expand...
Click to collapse
Did this phone have an issue with the speaker before you started messing around with it?
Hello friends!
My HTC10 is not rooted and is running on Nougat 7.0 with software version 2.42.651.66 and im not able to update it from the settings.
It is a Middle East unlocked device.
I tried going to SETTINGS-SYSTEM UPDATES-HTC SOFTWARE UPDATE
and then CHECK NOW
But it is only showing CHECKING for an infinite amount of time.
Tried this over wifi and on cellular data but still cant update.
I need a solution where i can update my ROM (STOCK ROM ONLY, DONT WANT TO ROOT) manually using an SD CARD only because my USB connector has got some issues.
Would really appreciate if someone can help.
That is weird i have unlocked OS with software number 2.41.401.41 and it is the latest update for MENA and EU, how did you update your phone ?
hejawi said:
That is weird i have unlocked OS with software number 2.41.401.41 and it is the latest update for MENA and EU, how did you update your phone ?
Click to expand...
Click to collapse
Why is that weird. It's locked to Sprint. Check the region number. When it's bought in the Middle East it's probably imported. There is more to find about this in the sprint section, it has its own subforum
Mr Hofs said:
Why is that weird. It's locked to Sprint. Check the region number. When it's bought in the Middle East it's probably imported. There is more to find about this in the sprint section, it has its own subforum
Click to expand...
Click to collapse
Do you mean that mine is a Sprint locked?? No... Im using it here in Middle East with the local service provider network. I have even factory restored it a few times...
tej835 said:
Do you mean that mine is a Sprint locked?? No... Im using it here in Middle East with the local service provider network. I have even factory restored it a few times...
Click to expand...
Click to collapse
Not sure what happened to your phone but it has a sprint version number?!
Mr Hofs said:
Not sure what happened to your phone but it has a sprint version number?!
Click to expand...
Click to collapse
Yes I just checked on the HTC website and the software version of my phone matches the Sprint details.
How do I change it to a Middle east version? Is it possible by flashing the ROM?? Which is the latest version of OS available on HTC10?? I have no issues with the network... I have factory reset it several times and yet my Local network is working. If it was locked to Sprint, it wouldnt have worked here on my Local Network.
I know this is an old thread now but I've just purchased a new htc 10 in the UK and it looks like I have the same issue as the op, (running what appears to be an unlocked Sprint phone running nougat on 2.42.651.66). Just wondering should I/is it safe to, update to Oreo via the ruu on the US htc support site, or I guess the other option would be to s-off, change mid and then flash leedroid or similar? I'm happy just running stock Oreo and don't 'want' to go down the route of s-off etc. Will I be safe enough to just flash the ruu?
Stevie1984 said:
I know this is an old thread now but I've just purchased a new htc 10 in the UK and it looks like I have the same issue as the op, (running what appears to be an unlocked Sprint phone running nougat on 2.42.651.66). Just wondering should I/is it safe to, update to Oreo via the ruu on the US htc support site, or I guess the other option would be to s-off, change mid and then flash leedroid or similar? I'm happy just running stock Oreo and don't 'want' to go down the route of s-off etc. Will I be safe enough to just flash the ruu?
Click to expand...
Click to collapse
Yes if the 651 part of the ruu matches and the first numbers are higher than 2.42 (like 3.16.651) you can flash it to get to oreo. After that you can stay stock or gain root, or flash a custom oreo or pie (los, aosp) roms.
Mr Hofs said:
Yes if the 651 part of the ruu matches and the first numbers are higher than 2.42 (like 3.16.651) you can flash it to get to oreo. After that you can stay stock or gain root, or flash a custom oreo or pie (los, aosp) roms.
Click to expand...
Click to collapse
Thanks for that. But now another quick question if you can help. Using a cid app via playstore it reports as a Sprint cid. I've since booted into fasboot/bootloader, it says *locked* but also says s-off. cid there shows cid.11111. I'm thinking this has been flashed with a Sprint ruu. Will I be safe enough to follow the steps to unlock the bootloader and just flash a wwe ruu do you think? I've flashed plenty of roms in the past and from what I remember cid. 11111 looks like supercid? In which case I can flash many different ruu's? Just really want to update to Oreo so would the Sprint ruu be the best option as you say? Then I can go on to whatever I want after that and just ignore the Sprint cid side of things?
Thanks in advance ?
Can you put the output here of "fastboot getvar all" minus the serial number and imei ?
And/or a picture of your download mode..... that way i can see more clearly what to be done.
Mr Hofs said:
Can you put the output here of "fastboot getvar all" minus the serial number and imei ?
And/or a picture of your download mode..... that way i can see more clearly what to be done.
Click to expand...
Click to collapse
Sure thing:
C:\ADB>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61f000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:HT6*********
all:
Finished. Total time: 0.380s
C:\ADB>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_pmewhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: HT6*********
(bootloader) current-slot:
(bootloader) imei: *******************
(bootloader) version-main: 2.42.651.6
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS640000
(bootloader) cid: 11111111
all:
Finished. Total time: 0.061s
As far as i can tell you can safely flash the sprint oreo ruu, i don't think you need to unlock the BL because it's s-off (the flag "locked" is changed by sunshine s-off). You should be able to flash the ruu straight up.
Most easy is to get the nougat sprint ruu and flash that, then update via HTC OTA to oreo.
If you want to flash the oreo ruu you need to flash the oreo firnware first and then the ruu other wise the ruu won't flash.
Mr Hofs said:
As far as i can tell you can safely flash the sprint oreo ruu, i don't think you need to unlock the BL because it's s-off (the flag "locked" is changed by sunshine s-off). You should be able to flash the ruu straight up.
Most easy is to get the nougat sprint ruu and flash that, then update via HTC OTA to oreo.
If you want to flash the oreo ruu you need to flash the oreo firnware first and then the ruu other wise the ruu won't flash.
Click to expand...
Click to collapse
Just want to say thanks again for all your help man. Made some progress late last night. Oreo firmware flashed, Leedroid rom installed. All good....or so i thought...Realised i no longer have either a 3G or 4G data connection. If i put my sim in my old phone i pick up 4G fine. I also know for sure i did have 4G when it was on Nougat. (Why, 'o' why did i start this.....). In the Aroma installer im selecting WWE UHL build. Thought okay, maybe this is the issue. But if i try the sprint setting i then get stuck in a loop on the setup wizard with it trying to do "Handsfree activation". Im thinking maybe its a radio issue that somehow ive skipped/missed? Anyway im going to download the Nougat RUU and try going through the steps again, (if i can, from what ive read im not sure i can do that after flashing an oreo RUU). Any help suggestions you've got would be most welcome at this point mate.
Stevie1984 said:
Just want to say thanks again for all your help man. Made some progress late last night. Oreo firmware flashed, Leedroid rom installed. All good....or so i thought...Realised i no longer have either a 3G or 4G data connection. If i put my sim in my old phone i pick up 4G fine. I also know for sure i did have 4G when it was on Nougat. (Why, 'o' why did i start this.....). In the Aroma installer im selecting WWE UHL build. Thought okay, maybe this is the issue. But if i try the sprint setting i then get stuck in a loop on the setup wizard with it trying to do "Handsfree activation". Im thinking maybe its a radio issue that somehow ive skipped/missed? Anyway im going to download the Nougat RUU and try going through the steps again, (if i can, from what ive read im not sure i can do that after flashing an oreo RUU). Any help suggestions you've got would be most welcome at this point mate.
Click to expand...
Click to collapse
Did you try 4G on the stock oreo build, flash the stock oreo ruu and see if that helps. I think I've seen reports about this in the leedroid thread but never really followed it as i know nothing to little about sprint
Mr Hofs said:
As far as i can tell you can safely flash the sprint oreo ruu, i don't think you need to unlock the BL because it's s-off (the flag "locked" is changed by sunshine s-off). You should be able to flash the ruu straight up.
Most easy is to get the nougat sprint ruu and flash that, then update via HTC OTA to oreo.
If you want to flash the oreo ruu you need to flash the oreo firnware first and then the ruu other wise the ruu won't flash.
Click to expand...
Click to collapse
hi!
i'm exactly in the very same situation
but instead, i'd like to use the ruu you provided (the previous link redirects me to ebay)
i can't update to oreo, can i have some help?
cigarpill said:
hi!
i'm exactly in the very same situation
but instead, i'd like to use the ruu you provided (the previous link redirects me to ebay)
i can't update to oreo, can i have some help?
Click to expand...
Click to collapse
What previous link ? I checked this thread but didn't see that i posted a link ?
Mr Hofs said:
What previous link ? I checked this thread but didn't see that i posted a link ?
Click to expand...
Click to collapse
that's weird, maybe some kind of add the directed me to ebay
i'm looking for the oreo room, so it will be a pleasure if you tell me how to get it
i'm 2.42.651.66
hello,
i really need help because my htc m8 stuck in ( htc white screen logo ) after trying installing a custom rom.
now i want to restore stock rom and i tried more methods but it failed.
i downloaded both of ruu exe and zip file
when i set up ruu.exe after two steps of the setup by click (next)..nothing happen!(although my htc m8 in the black and grey screen logo)
can you help me friends ?what can i do?by the easiest way.
thank you
audi19844 said:
hello,
i really need help because my htc m8 stuck in ( htc white screen logo ) after trying installing a custom rom.
now i want to restore stock rom and i tried more methods but it failed.
i downloaded both of ruu exe and zip file
Click to expand...
Click to collapse
Your post creates far more questions in my head, than answers.
It would make far more sense to try to figure out what went wrong with the custom ROM install, since that is what you were trying to accomplish from the start.
Most issues flashing custom ROM are due to outdated firmware on phone, old version TWRP, or wrong variant of M8. To determine which of those applies to you, we would need more info:
What custom ROM did you try to install? What version TWRP?
Also need to do fastboot getvar all, and post the results (delete IMEI and serial number).
If you still want to use the RUU:
How do you know it was the proper RUU version for your M8 variant (there are dozens)?
What is the file name or version number of the RUU(s) you tried?
Also need the getvar info indicated above, to know more info about the M8 variant, and therefore what determine what RUU to use.
You also need a relocked bootloader to RUU (unless the phone is s-off). But if it is still unlocked, I would recommend you leave it that way, and instead try to troubleshoot why the custom ROM is not working, rather than going backwards and relocking the bootloader, RUU, etc.
Also, when flashing a custom ROM, you should always make a backup in TWRP of the existing (such as stock) ROM before trying to flash a custom ROM. If you had done that, you could just restore the TWRP backup you made, instead of messing with RUUs.
redpoint73 said:
Your post creates far more questions in my head, than answers.
It would make far more sense to try to figure out what went wrong with the custom ROM install, since that is what you were trying to accomplish from the start.
Most issues flashing custom ROM are due to outdated firmware on phone, old version TWRP, or wrong variant of M8. To determine which of those applies to you, we would need more info:
What custom ROM did you try to install? What version TWRP?
Also need to do fastboot getvar all, and post the results (delete IMEI and serial number).
If you still want to use the RUU:
How do you know it was the proper RUU version for your M8 variant (there are dozens)?
What is the file name or version number of the RUU(s) you tried?
Also need the getvar info indicated above, to know more info about the M8 variant, and therefore what determine what RUU to use.
You also need a relocked bootloader to RUU (unless the phone is s-off). But if it is still unlocked, I would recommend you leave it that way, and instead try to troubleshoot why the custom ROM is not working, rather than going backwards and relocking the bootloader, RUU, etc.
Also, when flashing a custom ROM, you should always make a backup in TWRP of the existing (such as stock) ROM before trying to flash a custom ROM. If you had done that, you could just restore the TWRP backup you made, instead of messing with RUUs.
Click to expand...
Click to collapse
Thank you for your importance,
For now a successful ruu.zip flash done by HTC fastboot command prompt.
But the system looks like HTC one m7 Rom!!
Not the HTC m8
What is the wrong
audi19844 said:
For now a successful ruu.zip flash done by HTC fastboot command prompt.
But the system looks like HTC one m7 Rom!!
Not the HTC m8
What is the wrong
Click to expand...
Click to collapse
I asked a number of questions, zero of which you answered. I can't help you, if you don't provide any useful information. You haven't given a single piece of information about your device or the files you tried to flash. How do you think anyone can help you?
redpoint73 said:
I asked a number of questions, zero of which you answered. I can't help you, if you don't provide any useful information. You haven't given a single piece of information about your device or the files you tried to flash. How do you think anyone can help you?
Click to expand...
Click to collapse
sorry for missing information .
- i tried to install ( [ROM][UNOFFICIAL] LineageOS 15.1 for HTC One M8 )
-by twrb recovery 2.7.0.2 may be the recovery was old and i get fail when flashing the rom,so i sucked in the recovery between cant flash the custom rom or returning to the stock one.
-my big fault also was not making backup for my stock rom.
so i thought after that to use the ruu.zip files or ruu.exe
i tried to flash the ruu.exe but after 2 steps i see that (
erorr 130 model id error
the rom utility cannot update your android phone please get the correct rom utility and try again)
i tried to flash the ruu.zip by htc fastboot,and after many times it was succeeded to be flashed by htc fastboot
so this is my htc info
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT4*********
(bootloader) imei: 3591970********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__M27
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
the ruu zip file i used was this one ( RUU-4.16.401.10-0P6BIMG.zip )
i dont know if this is true or not one.
the ruu file was successfully flashed but the result was the (m7) like software not m8
thank you for your patience.
audi19844 said:
sorry for missing information .
Click to expand...
Click to collapse
No worries. Thanks for providing the info. You're doing much better now. Now we can get somewhere!
audi19844 said:
-by twrb recovery 2.7.0.2 may be the recovery was old and i get fail when flashing the rom,so i sucked in the recovery between cant flash the custom rom or returning to the stock one.
Click to expand...
Click to collapse
That version is really old, over 3 years old. It's not compatible with current ROMs, and not compatible with your current firmware (which is Marshmallow as shown in the getvar output).
Fail to flash the ROM is an expected result.
If you still want to flash Lineage, you need to flash a more current version (latest is TWRP 3.2.1-0) which you can get from here: https://dl.twrp.me/m8/
But you've also flashed an old RUU, and downgraded the firmware to Lollipop. It's probably not a big deal, but you're going backwards here. You might also find that you need to play around with TWRP versions to get one that works with Lollipop firmware. Not sure, but I think TWRP 3.2 (maybe earlier even) or later does not play well with Lollipop. And the 2.7 is way too old. So a version in between may be needed (2.8.7 is tried and trusted in many cases).
Probably better to RUU back to Marshmallow (I'll describe that below). Then from there, you can flash latest TWRP and then Lineage, if you like.
audi19844 said:
so i thought after that to use the ruu.zip files or ruu.exe
i tried to flash the ruu.exe but after 2 steps i see that (
erorr 130 model id error
Click to expand...
Click to collapse
Sounds like you are flashing multiple RUU versions. But we can't troubleshoot the error message, if you don't tell us what RUU's resulted in the error. RUU 4.16.401.10 clearly didn't give you that error, since it works. So it must have been other RUUs that you trie.
First of all, as the error message makes clear, the RUU for the wrong model (or wrong Carrier ID also) will result in RUU failure.
Also, flashing RUU's randomly, without knowing if it is the right one for your device is really dangerous, and can result in permanent damage if you flash the RUU for the wrong M8 version!
Be aware that flashing RUU (and some other things) is very risky with s-off, if you don't know exactly what you are doing!
audi19844 said:
the ruu zip file i used was this one ( RUU-4.16.401.10-0P6BIMG.zip )
i dont know if this is true or not one.
the ruu file was successfully flashed but the result was the (m7) like software not m8
Click to expand...
Click to collapse
You flashed the Lollipop RUU. You basically downgraded the OS, as you started with Marshmallow. That is probably why you think the software looks like that of the M7.
The Marshmallow RUU is here:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
After that, if you still want to flash Lineage, put TWRP back on the phone (such as version 3.2.1-0) and you should be able to flash Lineage successfully. I assume your bootloader is still shown as UNLOCKED on the bootloader screen?
redpoint73 said:
No worries. Thanks for providing the info. You're doing much better now. Now we can get somewhere!
That version is really old, over 3 years old. It's not compatible with current ROMs, and not compatible with your current firmware (which is Marshmallow as shown in the getvar output).
Fail to flash the ROM is an expected result.
If you still want to flash Lineage, you need to flash a more current version (latest is TWRP 3.2.1-0) which you can get from here: https://dl.twrp.me/m8/
But you've also flashed an old RUU, and downgraded the firmware to Lollipop. It's probably not a big deal, but you're going backwards here. You might also find that you need to play around with TWRP versions to get one that works with Lollipop firmware. Not sure, but I think TWRP 3.2 (maybe earlier even) or later does not play well with Lollipop. And the 2.7 is way too old. So a version in between may be needed (2.8.7 is tried and trusted in many cases).
Probably better to RUU back to Marshmallow (I'll describe that below). Then from there, you can flash latest TWRP and then Lineage, if you like.
Sounds like you are flashing multiple RUU versions. But we can't troubleshoot the error message, if you don't tell us what RUU's resulted in the error. RUU 4.16.401.10 clearly didn't give you that error, since it works. So it must have been other RUUs that you trie.
First of all, as the error message makes clear, the RUU for the wrong model (or wrong Carrier ID also) will result in RUU failure.
Also, flashing RUU's randomly, without knowing if it is the right one for your device is really dangerous, and can result in permanent damage if you flash the RUU for the wrong M8 version!
Be aware that flashing RUU (and some other things) is very risky with s-off, if you don't know exactly what you are doing!
You flashed the Lollipop RUU. You basically downgraded the OS, as you started with Marshmallow. That is probably why you think the software looks like that of the M7.
The Marshmallow RUU is here:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
After that, if you still want to flash Lineage, put TWRP back on the phone (such as version 3.2.1-0) and you should be able to flash Lineage successfully. I assume your bootloader is still shown as UNLOCKED on the bootloader screen?
Click to expand...
Click to collapse
I would like to thank you for your big help, thank you very much
I successfully used Marshmallow RUU
and my phone is now ok.
I learned now what i shoud do next time before installing a custom rom.
Thank you again.