Hi all,
I have an HTC 10 with:
kernel: lk
product: htc_pmeuhl
version: 1.0
version-main: 1.95.401.4
version-baseband: [email protected]
version-bootloader: 1.0.0.0000
mid: 2PS620000
cid: HTC__034
S-ON
Here's my problem.
I unlocked the bootloader, flashed latest TWRP recovery, did a full back up of Stock ROM (with TWRP Backup). Then I flashed latest SuperSU (which is supposed to not mess up the HTC 10 encryption). After that I flashed Viper10 4.1.0 ROM, which I didn't like (wasn't working well on my phone), so I wanted to get back to my stock ROM.
I went to the TWRP Restore, and reflashed the Stock ROM backup I had created before. After booting the Stock ROM was being stuck on "Decrypt your device with a password" screen. Then I decided to flash Viper10 again, and this time when I did it, it boots into and android screen saying: "Decryption Unsuccessful - Reset Phone". Clicking "reset the phone" doesn't change anything. I tried flashing the Stock ROM backup again, but TWRP says: "Unable to mount storage". Therefore I'm stuck with an unlocked bootloader, TWRP Recovery, and no working ROM.
So my understanding is that there's some mess up with the device encryption. I can see three potential options of how to fix it, but I need your help, because I'm afraid I'll brick it completely.
OPTION 1:
-The easiest would be just flashing a Stock RUU.exe for my CID/MID, this way I'd go back to full stock. However I cannot find an RUU for my firmware version: 1.95.401.4. I have S-ON, so from what I understood, I cannot do a downgrade to a lower RUU Firmware.
-What happens if I upgrade my firmware by flashing RUU with a different SKU? (e.g. 1.95.401.4 -> 2.28.617.8 which is available on HTC support site)
-Is there a way to change my CID/MID, so that I could flash Stock RUU for Unlock/Developer models?
OPTION 2:
I want to try the following:
-Format Data in TWRP (in order to get encryption off)
-Now that there's no encryption I guess I won't get "Unable to mount storage" message
-Restore backup of my Stock ROM TWRP Backup
-But I'm afraid of bricking my device completely this way, also since I read it can mess up your radio.
OPTION 3:
-Get the S-OFF somehow, from bootloader? Is it even possible? The only way I saw was through SunShine app, but I need a working ROM for that.
-Then I can downgrade my Firmware, using available Stock RUU.exe for my CID/MID (e.g. 1.95.401.4 -> 1.80.401.3)?
Really hope someone can guide me through this process. Please let me know if there are any other available option in this situation, and if the Option 2 is worth trying?
Btw, I dont care about losing data on my phone, there's nothing important there.
Thank you,
Djotto.
Hope you got your stock backup on your external sdcard or somewhere backed up on your PC.
Yes, you need to format data in TWRP, to get rid of the encryption. Else the TWRP can't mount /data.
Formatting data wipes your internal sdcard...since you already messed up any data on there is lost already, since you'll never be able to decrypt it again.
j to the 4n said:
Hope you got your stock backup on your external sdcard or somewhere backed up on your PC.
Yes, you need to format data in TWRP, to get rid of the encryption. Else the TWRP can't mount /data.
Formatting data wipes your internal sdcard...since you already messed up any data on there is lost already, since you'll never be able to decrypt it again.
Click to expand...
Click to collapse
Hey j,
Thanks for the advice. With the help of amazing guys at Venom Support IRC channel, and your advice, I went ahead and formatted data in TWRP, then I flashed Viper 3.5 ROM Android M (unlike Viper 4.2 ROM Android N before that), and it worked like a charm.
Btw, just for the record, I figured out that Venom 4.2 didn't work very well for me, since I have Android M firmware, now Venom 3.5 works really well, its amazing, I'm not going back to the stock HTC 10 ROM
Thank you once again!
Related
help! lol
my dilemma, i updated to 4.4.3, rooted, created a nandroid backup.
then i installed viperone 2.5
all going well till phone stopped sending texts (ee update fault, common fault)
after checking solutions all say factory reset, did that, phone booted, but i couldnt log into google, kept saying could not connect to servers
thought ive had enough, restore my nand, and now its stuck on load screen, been left for 15 mins and no joy, i can still get into twrp but im at a loss at what i can do.
twrp wont let me mount internal storage so i can send another backup, only mounts sd card
s-on so limited options
houston33 said:
help! lol
my dilemma, i updated to 4.4.3, rooted, created a nandroid backup.
then i installed viperone 2.5
all going well till phone stopped sending texts (ee update fault, common fault)
after checking solutions all say factory reset, did that, phone booted, but i couldnt log into google, kept saying could not connect to servers
thought ive had enough, restore my nand, and now its stuck on load screen, been left for 15 mins and no joy, i can still get into twrp but im at a loss at what i can do.
twrp wont let me mount internal storage so i can send another backup, only mounts sd card
s-on so limited options
Click to expand...
Click to collapse
If you can get into recovery, you can get into your bootloader. Flash a new ROM using ADB.
Also, only factory reset as a last resort. There's usually a way to fix stuff without resorting to that.
xunholyx said:
If you can get into recovery, you can get into your bootloader. Flash a new ROM using ADB.
Also, only factory reset as a last resort. There's usually a way to fix stuff without resorting to that.
Click to expand...
Click to collapse
i thought flashing a new rom on the m8 required the firmware setup?
so i can just reinstall viperone 2.5 again?
408
so from where i am now i can just go to twrp and install android rev 21? or do i have to use adb sideload?
is 21 even compatible?
i swore i wasnt gonna mess on with this phone.........
houston33 said:
i thought flashing a new rom on the m8 required the firmware setup?
so i can just reinstall viperone 2.5 again?
Click to expand...
Click to collapse
You sure can. The newer firmware is needed for 4.4.4 ROMs. If you had 2.5, reflash it. It will work with the newest firmware as well. Just not the old stuff.
Here's a pointer: A dirty flash of the ROM you are currently running will reset your tweaks, and often fix problems you are having. When I start having glitches, I first reboot. If that didn't work; and I can't find a solution on XDA easily, I reflash my ROM; the dirty way. It really does help to clear up stuff, especially if you are using themes and tweaks.
Sadly didn't work.
Will have to use one of the stock na droid backups from the collection on here once the thread is up and running again
How do I access phone memory to copy the backup over? I only have boot loader and twrp
houston33 said:
Sadly didn't work.
Will have to use one of the stock na droid backups from the collection on here once the thread is up and running again
How do I access phone memory to copy the backup over? I only have boot loader and twrp
Click to expand...
Click to collapse
In TWRP, you can manage files easily.
Click advanced > file manager
There you can copy files, move them and change permissions. Plus deleting and renaming them.
Hey guys, I really hate to be the guy that asks these questions, but I've spent the past two days here looking for an answer but haven't found much that's quite like what I'm experiencing.
I have a google play edition of the htc one m8 and I was trying to get s-off and I installed insertcoin via philz recovery (I realize now this was probably a mistake since google play editions aren't compatible with sense based roms?). Ever since I've tried to boot up, it tries, then ends up restarting into recovery mode.
Things I've tried:
Installing the 4.4.4 gpe RUU, this failed with a (99 unknown fail) error.
Restoring a nandroid backup of the google play edition (gpe3.zip) from this thread. This fails with a set_perm issue (error 7).
I'm kinda at a loss. Anyone have any insight here?
GPE partitioning is different from Sense versions. So you can't flash a Sense ROM, unless you change to the Sense partitioning scheme.
I think trying to flash the Sense ROM borked up the partitions, and that is why restoring the GPE nandroid won't work.
GPE RUU should fix you up. You need to relock the bootloader to run the RUU, since you are s-on. That is the reason for the RUU error.
redpoint73 said:
GPE partitioning is different from Sense versions. So you can't flash a Sense ROM, unless you change to the Sense partitioning scheme.
I think trying to flash the Sense ROM borked up the partitions, and that is why restoring the GPE nandroid won't work.
GPE RUU should fix you up. You need to relock the bootloader to run the RUU, since you are s-on. That is the reason for the RUU error.
Click to expand...
Click to collapse
Thanks so much man!
Unfortunately I'm now getting a "12 signature verify failure". I googled this and most of the results said it's because the phone has root (I think the nandroid I mentioned I tried to flash in the previous post comes with root...), so I downloaded the "unsuperuser.zip" from here and tried running it, and restoring the default recovery then locking and trying the ruu again, but still no luck! Any ideas?
technicaltonic said:
Unfortunately I'm now getting a "12 signature verify failure". I googled this and most of the results said it's because the phone has root (I think the nandroid I mentioned I tried to flash in the previous post comes with root...), so I downloaded the "unsuperuser.zip" from here and tried running it, and restoring the default recovery then locking and trying the ruu again, but still no luck! Any ideas?
Click to expand...
Click to collapse
I forgot the GPE RUU is not an "official" signed RUU, so you can't run it with s-on.
What happens if you re-install custom recovery and try to flash a GPE based custom ROM (adb push ROM to the phone, or put on SD card with a USB card reader from your computer)?
technicaltonic said:
Thanks so much man!
Unfortunately I'm now getting a "12 signature verify failure". I googled this and most of the results said it's because the phone has root (I think the nandroid I mentioned I tried to flash in the previous post comes with root...), so I downloaded the "unsuperuser.zip" from here and tried running it, and restoring the default recovery then locking and trying the ruu again, but still no luck! Any ideas?
Click to expand...
Click to collapse
redpoint73 said:
I forgot the GPE RUU is not an "official" signed RUU, so you can't run it with s-on.
What happens if you re-install custom recovery and try to flash a GPE based custom ROM (adb push ROM to the phone, or put on SD card with a USB card reader from your computer)?
Click to expand...
Click to collapse
He can also try doing a factory reset from stock recovery ... that could get the partitions back in order
clsA said:
He can also try doing a factory reset from stock recovery ... that could get the partitions back in order
Click to expand...
Click to collapse
Doubt that would help. All a factory reset does is wipe /data (user data) partition.
redpoint73 said:
Doubt that would help. All a factory reset does is wipe /data (user data) partition.
Click to expand...
Click to collapse
As I understand it, a factory reset from the bootloader/phone does what you described .. however a factory reset from stock recovery actually reformats the data partition returning it to it's correct size. I could have it wrong but that's what works on the M7.
redpoint73 said:
I forgot the GPE RUU is not an "official" signed RUU, so you can't run it with s-on.
What happens if you re-install custom recovery and try to flash a GPE based custom ROM (adb push ROM to the phone, or put on SD card with a USB card reader from your computer)?
Click to expand...
Click to collapse
I tried flashing the skydragon lollipop and it worked!!! Thanks so much man! I feel a bit like an idiot, cause this was my actual goal, and I got caught up thinking it wouldn't work because of the state of my phone.
Thanks much for your help guys!
technicaltonic said:
I tried flashing the skydragon lollipop and it worked!!! Thanks so much man! I feel a bit like an idiot, cause this was my actual goal, and I got caught up thinking it wouldn't work because of the state of my phone.
Thanks much for your help guys!
Click to expand...
Click to collapse
Okay, I spoke too soon. It sorta works... Basically the first run works as long as I don't interrupt it but afterwords it reverts to a boot loop again. If I re-flash it and let it start uninterrupted again things are okay for the first run again but subsequent restarts start the bootloop again. I did notice that the sd card location seems to alternate between /sdcard and /sdcard/0 I assume this is the partitioning scheme thing you guys were talking about... Any idea what might be resetting the partitioning scheme, or causing subsequent restarts to fail?
EDIT: To anyone that may have the same problem, I ended up fixing this by installing the rom from this post. After that I was back to normal. Hallelujah.
I've been doing the custom ROM game for 13 years and somehow tonight I've managed to brick my phone for the first time ever.
Here's the breakdown.
Started with my S-OFF, SuperCID M8 Unlocked WWE which was running the Skydragon 6.0 GPE ROM with associated firmware.
I decided I wanted to try the latest 6.0 Sense rom, so downloaded the 6.0 Firmware zip and Maximus 12 ROM.
From a bit of reading I saw that to get my Sense partition back and be able to install the relevant ROM to go with it, I'd need to flash the Sense firmware, which I did, and that seemed to go OK.
I rebooted into TWRP and went to do a wipe, and was greeted with the following error:
"could not mount /data and unable to find crypto footer"
Followed by lots of
"Unable to mount /data" error messages.
If I leave the phone to boot, it asks me for my password and says that the data is no longer there and I need to reset, but I'm hesitant to do that as I expect I would be left completely shafted then.
I tried reflashing the GPE Firmware but it looks like the damage has been done.
Desperately need some help in getting myself back to working. Any ideas please?
You missed a step.
After firmware is flashed and twrp is installed, you need to format data (not wipe data).
Further update. I followed the back to sense guide, got to the point of re-flashing TWRP but now when I try to enter recovery from the bootloader it goes to the screen saying "entering recovery..." and then reboots, but there's no ROM to boot into so it tries to reboot into recovery again, and fails etc...
Flashed the 6.0 Sense firmware again, managed to install and get into TWRP. Now installing MaximusHD 12...fingers crossed...
ckpv5 said:
You missed a step.
After firmware is flashed and twrp is installed, you need to format data (not wipe data).
Click to expand...
Click to collapse
Hmm, maybe I made this all way too complicated for myself! At the uncomfortably long stage of first boot. Hopefully it will make it through...
It worked. Running fine now. I'll keep the format idea in mind if there's ever a next time
Sent from my HTC One_M8 using Tapatalk
Hey everyone, long time reader here but first post. I could not find any post with my same situation...
I have an HTC One M8 that I've been running CyanogenMod 13 nightlies on for some time. Here are the specs:
TWRP Recovery (Though I have used CWM and Cyanogen Recovery in the past)
Currently Cyanogenmod 13 nightly is installed, but I have a bootloop.
Unlocked bootloader and all that jazz. S-ON right now, not sure if it has ever been off.
Always worked well with minimal glitches. Cyanogenmod 14.1 nightlies began a few days ago, so I downloaded one and installed it via CWM recovery as I typically would. Things were REALLY glitchy, and I read that it is better to clean install when you bump up a release number (i.e. 13 to 14). I booted into recovery and must have screwed something up.
I did a factory reset, possibly in FASTBOOT (don't remember, first mistake). I think that caused corruption of the DATA partition. CWM was incapable of doing basically anything. It could not wipe or install anything regarding the DATA Partition. I looked up tutorials and installed TWRP via Fastboot and did some wipes of the Dalvik Cache, Cache, Data, System, and Internal Storage. It took some repair of the DATA partition, but I changed its format a few times from FAT to EXT4 and it worked when I settled on EXT4 (problem seemingly solved).
Everything acts normal in Recovery. Multiple times I have wiped everything and done one of the following:
1) Installed the CM14.1 nightly and the GAPPS. When I boot up, so many apps and utilities are crashing that the popups do not let me touch the Startup Wizard. I can barely get it to turn off.
2) Installed a working CM13 nightly just to get something back. Bootloops at the CM logo infinitely (checked, yes it bootlooped overnight and I'm not just impatient).
I've tried all three Recovery options, multiple CM Roms (including ones I knew worked), and wiped everything I could (with the exception of the External-SD card where I store the Roms and GAPPS).
Like an idiot, I don't have a nandroid backup. However, I know what Rom worked and have a copy of it. I don't need anything that was on the phone.
What else is there to do? I'm scared to RUU, and I don't think that'll help me much. Any functionality at this point is fine with me, I don't care about Nougat until I get things working again.
Suggestions? Thanks a lot.
deltacadet84 said:
.... Cyanogenmod 14.1 nightlies began a few days ago, so I downloaded one and installed it via CWM recovery as I typically would. Things were REALLY glitchy, and I read that it is better to clean install when you bump up a release number (i.e. 13 to 14). I booted into recovery and must have screwed something up.
Click to expand...
Click to collapse
These where the problem are (as I see them and I maybe wrong)
- I don't think CM14.1 can properly be installed with CWM. You need TWRP 3.0.2-0
- In order to run TWRP 3.0.2-0 and CM14.1, your current firmware must be Marshmallow 6.xx.xxx.x
Post fastboot getvar all result (without serial & imei no.) then we can see what you need.
If your firmware already on Marshmallow and TWRP 3.0.2-0 is installed, boot to TWRP recovery - wipe - format data - type "yes" then main menu, reboot - recovery
Now you can install ROM.
With fastboot getvar all result, someone will be able to help you. I got to sign off now .. good night & good luck
Go into twrp wipe everything system, data, dalvic, cache and flsh the rom that you know will work or the stock rom from http://www.htc.com/us/support/rom-downloads.html and report to us if it works
justinchao740 said:
Go into twrp wipe everything system, data, dalvic, cache and flsh the rom that you know will work or the stock rom from http://www.htc.com/us/support/rom-downloads.html and report to us if it works
Click to expand...
Click to collapse
this will not help him,if he find his device RUU in the link you provide it just back to stock
the above post by ckpv5 is the answer,ckpv5 just tell him how to solve his issue by flashing the latest released firmware ( 6.xx.xxx.xx ) and the latest TWRP ( 3.0.2-0 ) then flash the ROM,after that everything will work as it should
Sent from my HTC M8 using XDA Labs
tried to install cm 14.1 on htc m8 s-on unlocked via twrp 3.0.2.0.
sayes system patching unconditionally how to solve it?
Did a clean install with full wipe with formated data. still no luck.
any solve please?
Dewzone said:
tried to install cm 14.1 on htc m8 s-on unlocked via twrp 3.0.2.0.
sayes system patching unconditionally how to solve it?
Did a clean install with full wipe with formated data. still no luck.
any solve please?
Click to expand...
Click to collapse
Did you complete the flash ? Did you reboot after the flash end ?
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
Did you complete the flash ? Did you reboot after the flash end ?
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
These steps i did
Flashed even after that notice.
Wiped cache/dalvik
Flash gapps
Wiped cache/dalvik
Reboot.
But after it many functions were not working like sim card n few other options.
Did something went wrong?
Sent from my HTC One M8 using XDA-Developers mobile app
Dewzone said:
These steps i did
Flashed even after that notice.
Wiped cache/dalvik
Flash gapps
Wiped cache/dalvik
Reboot.
But after it many functions were not working like sim card n few other options.
Did something went wrong?
Click to expand...
Click to collapse
No there is nothing to worry about it's normal
What rom you coming from before cm ?
If you have any issues flash firmware then flash the rom,this may solve some issues for you as it solved for me
Sent from my HTC M8 using XDA Labs
Dewzone said:
tried to install cm 14.1 on htc m8 s-on unlocked via twrp 3.0.2.0.
sayes system patching unconditionally how to solve it?
Did a clean install with full wipe with formated data. still no luck.
any solve please?
Click to expand...
Click to collapse
I got system patching unconditionally notice too but it worked fine with no problem. As of the Sim card, you will need to wait a while for the sim card to be recognized.
ckpv5 said:
Post fastboot getvar all result (without serial & imei no.) then we can see what you need.
If your firmware already on Marshmallow and TWRP 3.0.2-0 is installed, boot to TWRP recovery - wipe - format data - type "yes" then main menu, reboot - recovery
Click to expand...
Click to collapse
Thank you very much! Its been a busy weekend, just got back to my phone. Here are the results of fastboot getvar all:
Code:
C:\adb-fastboot\Android>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 1.12.20.1211
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: FA453SF02819
INFOimei: 990004298621792
INFOimei2: Not Support
INFOmeid: 99000429862179
INFOproduct: m8_wlv
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B20000
INFOcidnum: LRA__001
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: e7c075a3
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Thanks for the help guys! I really don't care about getting CM 14.1 working, I'm perfectly happy with the older nightlies like I was using. I have already used TWRP to wipe Data, Dalvik, System, and Internal Storage MULTIPLE times and tried to flash all kinds of ROMs I know I've used before, so I know that's not the fix. I think ckpv5 is right about the firmware, I just don't know what I'm doing past this point.
deltacadet84 said:
... I have already used TWRP to wipe Data, Dalvik, System, and Internal Storage MULTIPLE times and tried to flash all kinds of ROMs I know I've used before, so I know that's not the fix...
Click to expand...
Click to collapse
Firstly .. you have a LRA device and AFAIK there is no Marshmallow firmware / update for your device version.
Secondly .. wiping all those won't help. You need to format data in TWRP as I said earlier.
Thirdly .. for your current firmware level, it's best to install TWRP 2.8.7.0 then do that format data not wipe data.
boot to TWRP recovery - wipe - format data - type "yes" then main menu, reboot - recovery
then you can install your working ROM.
ckpv5 said:
it's best to install TWRP 2.8.7.0 then do that format data not wipe data.
boot to TWRP recovery - wipe - format data - type "yes" then main menu, reboot - recovery
then you can install your working ROM.
Click to expand...
Click to collapse
Steps complete, still bootlooping at the Cyanogenmod alien logo. I installed TWRP 2.8.7.0, followed your above steps for a CM13.0 Nightly I had run before and the CM12.1 latest release candidate. No cigar
New strategy?
deltacadet84 said:
New strategy?
Click to expand...
Click to collapse
Revert to stock with RUU and start all over again.
You need to relock bootloader because you have S-On device.
Read this : http://forum.xda-developers.com/htc-one-m8/help/help-friends-t3402398
RUU is linked on post #5
Good luck & good night
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Followed your instructions I found here. Got a failure:
Code:
sending 'zip'... (53965 KB) OKAY
sending time = 2.544 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 3(s)
Trying to find a solution, thought I followed everything to the letter.
EDIT: Just realized that RUU.zip file is for the European model. I have the US AT&T model...
ahmed.ismael said:
No there is nothing to worry about it's normal
What rom you coming from before cm ?
If you have any issues flash firmware then flash the rom,this may solve some issues for you as it solved for me
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
Got any Link to the firmware?
I think this might be partition format might be.
Sent from my HTC One M8 using XDA-Developers mobile app
I was on viperone 6.1.0
Then ice 8.2.2 then cm 13 (patch prob)
Then RR(same patch error)
Then 14.1 patch error.
Now back to 6.1.0(adb prob though).
deltacadet84 said:
Trying to find a solution, thought I followed everything to the letter.
EDIT: Just realized that RUU.zip file is for the European model. I have the US AT&T model...
Click to expand...
Click to collapse
Definitely yoi didn't follow everything .. you didn't read what I wrote above.
I asked you to get the RUU on post #5 in the thread that I linked above but you got wrong RUU that is on post #6 on other link.
Your device is neither EU nor AT&T ... yours is LRA.
The RUU 4.21.512.4 is what you need. Read again.
Or read this : http://forum.xda-developers.com/showpost.php?p=67431802&postcount=19
Deleted
@ckpv5 sorry about that
Dewzone said:
Got any Link to the firmware?
I think this might be partition format might be.
Click to expand...
Click to collapse
ahmed.ismael said:
all cm based rom will give you the patching system unconditionally line while flashing
IT'S NORMAL nothing to worry about
about the firmware i ask you because some roms manipulate the partitions
Click to expand...
Click to collapse
Maybe you guys should discuss this unrelated problem to OP in his own thread here : http://forum.xda-developers.com/htc-one-m8/help/cm-14-1-patching-unconditionally-m8-t3511928
Helloes ^^
I was trying to root HTC One M8 following a guide. I managed to unlock the bootloader and install TWRP 2.7.0.2 but I accidentally deleted the system partition :SS I hope I left everything else intact..
I downloaded OTA_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_R-4.16.401.13 and tried flashing it but Im getting
mount failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata
Click to expand...
Click to collapse
Package expects build fingerprint of htc/htc_europe/htc_m8:5.0.1./LRX22C/448934. 13:user/release-keys...
Click to expand...
Click to collapse
I also downloaded RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 and tried to update but it fails with error 155(I tried locking the bootloader and running it again but it still gives me the same error
My bootloader is unlocked atm and S-on...
Is it possible to recover the os in any way?
------
After trying to flash like 5 roms flashing InsertCoin worked somehow...
Qitsch said:
Helloes ^^
I was trying to root HTC One M8 following a guide. I managed to unlock the bootloader and install TWRP 2.7.0.2 but I accidentally deleted the system partition :SS
Click to expand...
Click to collapse
Why did you flash such an old version TWRP? That one is from about 3 years ago, and will cause lots of problems!
Couple simple rules to live by, when modding these phones:
1) Do not wipe things in TWRP willy-nilly, without knowing what they are, or what the result will be. The option to wipe "system" is in the Advance wipe section. It's called "Advanced" for a reason. That alone would have been a warning to be careful, and not mess with things, unless you know what you are doing. It also clearly says in TWRP wipe screen, that most of the time, the default wipe (cache, Dalvik/ART and data) is all you ever need. It says that for a reason.
2) Right after you install TWRP, and before messing around with anything, you should make a TWRP backup of your current stock ROM. Definitely do that, before trying to flash root, ROMs, or any other mods. That way, if anything goes wrong (or you simply screw up, and wipe system) you have a backup, that you can easily restore.
Qitsch said:
I downloaded OTA_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_R-4.16.401.13 and tried flashing it but Im getting
Click to expand...
Click to collapse
In general, you should never flash a file named "OTA" unless you know exactly what you are doing. The requirements for an OTA on this device are steep:
a) Must currently have the version number directly before the OTA number (you can't skip or flash the same number OTA)
b) Must have stock recovery installed (not TWRP)
c) Must match your version (CID, MID). Do you have the Euro version? You never stated this info.
Qitsch said:
I also downloaded RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 and tried to update but it fails with error 155(I tried locking the bootloader and running it again but it still gives me the same error
Click to expand...
Click to collapse
This RUU is only for the US Developer's Edition version M8. Will not work on any other version.
Even if you had the US Dev Ed (which is unlikely) this RUU would require the firmware being flashed, before the RUU will install (thus, Error 155).
In short, it seems like you are just guessing at solutions. Not a good idea.