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
Related
my phone is s-off and runs 2.3.5
ive tried to install custom roms many times but every time the same thing happens: my phone just goes to the white HTC screen and keeps restarting.......i have to revert to my old htc rom every time
please help!!!!!!!!
Can you talk us through the steps you are taking to flash the ROM so we can see what is going wrong?
hamzalateef said:
my phone is s-off and runs 2.3.5
ive tried to install custom roms many times but every time the same thing happens: my phone just goes to the white HTC screen and keeps restarting.......i have to revert to my old htc rom every time
please help!!!!!!!!
Click to expand...
Click to collapse
use rom manager from the market. make sure to delete dalvk cash
Clear Dalvk Cache, it makes a big difference
ok
1. so first i put the rom file on my sd card
2. then i go into recovery
3. clear dalvk cache,clear battery stats,clear cache partition
4. go to install zip from sd card,chose my rom and install it
5. restart my phone
i think thats what were supposed to do.
But my phone just keeps restarting,and nothing comes on!!
p.s. my phone is s-0ff
MARVEL PVT SHIP S-OFF RL
HBOOT-1.08.0000
MICROP-0451
RADIO-7.53.39.03M
0CT 31 2011,20:38:16
hamzalateef said:
ok
1. so first i put the rom file on my sd card
2. then i go into recovery
3. clear dalvk cache,clear battery stats,clear cache partition
4. go to install zip from sd card,chose my rom and install it
5. restart my phone
i think thats what were supposed to do.
But my phone just keeps restarting,and nothing comes on!!
p.s. my phone is s-0ff
MARVEL PVT SHIP S-OFF RL
HBOOT-1.08.0000
MICROP-0451
RADIO-7.53.39.03M
0CT 31 2011,20:38:16
Click to expand...
Click to collapse
you need to perform a full wipe before flashing a new rom
it's the "wipe data/factory reset" option within recovery. this will format the phone properly. if you don't do this bits of system and data partitions get mixed up hence it won't boot. dalvik cache and cache are just caches...wiping them rarely solves anything.
also check that your SD card meets the ROM requirements, for instance it may require that you have an ext partition, use gparted or recovery for this, but backup your sd card to PC first
eddiehk6 said:
you need to perform a full wipe before flashing a new rom
it's the "wipe data/factory reset" option within recovery. this will format the phone properly. if you don't do this bits of system and data partitions get mixed up hence it won't boot. dalvik cache and cache are just caches...wiping them rarely solves anything.
also check that your SD card meets the ROM requirements, for instance it may require that you have an ext partition, use gparted or recovery for this, but backup your sd card to PC first
Click to expand...
Click to collapse
i even wiped data/factory reset numerous times, my sdcard is partitioned but the roms never work
hamzalateef said:
i even wiped data/factory reset numerous times, my sdcard is partitioned but the roms never work
Click to expand...
Click to collapse
i m facing the same problem though my device is s-on...the problem occurs only if i try to flash a rom having an overclocked([OC]) kernel...else i m able to flash other roms like cm7 stable build etc...does anyone have a solution for this...(i even tried flashing the overclocked kernels separately...doesnt seem to work)
You can try this before you install new rom:
http://forum.xda-developers.com/showthread.php?t=1524955
If it doesn't help try to reinstall ClockWorkMod:
http://forum.xda-developers.com/showthread.php?t=1213229
sky_86 said:
You can try this before you install new rom:
http://forum.xda-developers.com/showthread.php?t=1524955
If it doesn't help try to reinstall ClockWorkMod:
http://forum.xda-developers.com/showthread.php?t=1213229
Click to expand...
Click to collapse
Tried the first option ie Superwipe...no changes...still not able to flash an overclockable kernel or a rom with it...the second option of Clockworkmod wont work for me as its for s-off devices and mines s-on....is it necessary to be s-off to flash an overclockable kernel???
sky_86 said:
You can try this before you install new rom:
http://forum.xda-developers.com/showthread.php?t=1524955
If it doesn't help try to reinstall ClockWorkMod:
http://forum.xda-developers.com/showthread.php?t=1213229
Click to expand...
Click to collapse
so am i supposed to flash a file thats made for HTC sensation?
will it work?
sky_86 said:
You can try this before you install new rom:
http://forum.xda-developers.com/showthread.php?t=1524955
If it doesn't help try to reinstall ClockWorkMod:
http://forum.xda-developers.com/showthread.php?t=1213229
Click to expand...
Click to collapse
the first link has a sensation file......will it work on wfs?
and i already have unofficial CWM
siddharthmani said:
is it necessary to be s-off to flash an overclockable kernel???
Click to expand...
Click to collapse
Nope, if your unlocked by HTCdev method should have no problem.
what other roms do you know of that arent overclockable??
ill try them if they work........
can you send me the links?
siddharthmani said:
Tried the first option ie Superwipe...no changes...still not able to flash an overclockable kernel or a rom with it...the second option of Clockworkmod wont work for me as its for s-off devices and mines s-on....is it necessary to be s-off to flash an overclockable kernel???
Click to expand...
Click to collapse
can you tell me which roms you know off that are non-overclockable.........i want to see it they work
Hello,
I have a S-ON phone unlocked with htcdev.
I tried two ROMS from m1ndh4x8r, with or without overclock, but it always failed like you. White screen with HTC logo and nothing starts. I am 100% sure I did everything right...
Then I tried another ROM, HenseMod5, and it worked perfectly at the first try ! I don't know what's wrong with my device (if anything). Now HenseMod6 is out, I am installing right now.
So, try this ROM (I took the stock one):
http://forum.xda-developers.com/showthread.php?t=1434497
I am very pleased with this.
Cédric
cdricx said:
Hello,
I have a S-ON phone unlocked with htcdev.
I tried two ROMS from m1ndh4x8r, with or without overclock, but it always failed like you. White screen with HTC logo and nothing starts. I am 100% sure I did everything right...
Then I tried another ROM, HenseMod5, and it worked perfectly at the first try ! I don't know what's wrong with my device (if anything). Now HenseMod6 is out, I am installing right now.
So, try this ROM (I took the stock one):
http://forum.xda-developers.com/showthread.php?t=1434497
I am very pleased with this.
Cédric
Click to expand...
Click to collapse
thanks alot bro.......HenseMod worked for me too!!!!!!!
although im not sure why the others dont work for me..........maybe because of some of the feature the have and HenseMod doesnt.......
Glad to know it helped you
I don't know either why the others don't work, but I haven't really tried to figure it out. HenseMod is fine and works great for me, so I don't need another one.
By the way, I upgraded from HenseMod5 to 6 and everything's fine.
Hi all,
As you can see from my post count I usually manage to solve any issues I have with the search funtion but this one has got complicated
I updated the firmware on my handset to upgrade the hboot, I know have 1.36.0000.
Since this though I'm having trouble booting any ROMs. Fastboot and CWM recovery are all fine but flashing boot.img and flashing the ROM from the sdcard I can't get past the HTC screen or sometimes the ROM's boot image. I also remember to erase cache after flashing the boot.img
I have a nandroid backup of a stock ROM that I've used to get the phone working but I'd like to know what's happening! I've tried this thread on getting out of boot loops but not had any luck.
If anyone has any ideas I'd appreciate it or if you need any other info please ask
I believe the handset has supercid but I used the info cidnum: ORANG001 3.16.61.6 anyway
I'm not very experienced with this so am hopeful I've missed something simple
Thanks in advance
This may sound stupid but did you perform a full wipe before installing the rom.zip ?
Mr Hofs said:
This may sound stupid but did you perform a full wipe before installing the rom.zip ?
Click to expand...
Click to collapse
Hey, thanks for the reply.
I've been over and over the process as I thought it might be something like that, but went through the instructions for each ROM step by step and wiped everything from CWM before flashing
I've done some more Googling and it looks like a lot of people have had problems with non-sense ROMs on hboot 1.36. I'm going to download a sense one and give that a try
Ah oke.....well i know this, if you want to run CM10 you need a modified boot.img ! This one
http://db.tt/uDdWaAtH
For the rest of the aosp roms i have no to less knowledge
Mr Hofs said:
Ah oke.....well i know this, if you want to run CM10 you need a modified boot.img ! This one
*boot.img link*
For the rest of the aosp roms i have no to less knowledge
Click to expand...
Click to collapse
I think I saw your post helping someone else about a modded boot.img for CM10 - there's no GPS, correct?
Maybe it's time to love Sense again
Yes i believe so, CM10.1 has it working. But yeah I'm always on sense
Problem rebooting
Mr Hofs said:
This may sound stupid but did you perform a full wipe before installing the rom.zip ?
Click to expand...
Click to collapse
I hav the same problem as above hav also updated to the same hboot and fw I'm also with orange. Tried to flash a rom did fastboot flash boot boot.img. Phone would not reboot. I did a nandroid backup but still my HOX will not boot it stays on the HTC quietly brilliant screen when I try restore from nandroid back up
Did you also flash the boot.img from the nandroid backup ?
Mr Hofs said:
Did you also flash the boot.img from the nandroid backup ?
Click to expand...
Click to collapse
No I can't get into the phone storage to get it. Where would I get that boot.img
yes you can, go into the recovery and mount the sdcard as a mass storage device....that way its a diskdrive and you can copy out the boot.img file....what recovery do you have, type and version number ?
Drunkineck said:
Hi all,
As you can see from my post count I usually manage to solve any issues I have with the search funtion but this one has got complicated
I updated the firmware on my handset to upgrade the hboot, I know have 1.36.0000.
Since this though I'm having trouble booting any ROMs. Fastboot and CWM recovery are all fine but flashing boot.img and flashing the ROM from the sdcard I can't get past the HTC screen or sometimes the ROM's boot image. I also remember to erase cache after flashing the boot.img
I have a nandroid backup of a stock ROM that I've used to get the phone working but I'd like to know what's happening! I've tried this thread on getting out of boot loops but not had any luck.
If anyone has any ideas I'd appreciate it or if you need any other info please ask
I believe the handset has supercid but I used the info cidnum: ORANG001 3.16.61.6 anyway
I'm not very experienced with this so am hopeful I've missed something simple
Thanks in advance
Click to expand...
Click to collapse
Can you send me your boot.img I have same hboot CID and fw
Going into the recovery and mounting it .... Is faster i guess ..... Takes just a few minutes......
Mr Hofs said:
yes you can, go into the recovery and mount the sdcard as a mass storage device....that way its a diskdrive and you can copy out the boot.img file....what recovery do you have, type and version number ?
Click to expand...
Click to collapse
Clockwork mod 5.8.2.7 can't get it to mount I get this
E:Unable to open ums lunfile(no such file or directory)
https://www.dropbox.com/s/guvfqd7tp8acxg6/recovery 5.8.4.0.img
flash this one and your problem is solved
Mr Hofs said:
flash this one and your problem is solved
Click to expand...
Click to collapse
In my haste to mount the phone last time I've ballsed up big time I've deleted all my sd card data nandroid back up has gone Your recovery did work and I managed to mount the successfully. Is there any thing I can do now
yes...flash a brand new rom. you said you updated the hboot to a JB one, so you must be able to run any rom now. which one would you like....
ow and keep the phone in the recovery, the battery loads in there !!!
Mr hofs the helper
Mr Hofs said:
yes...flash a brand new rom. you said you updated the hboot to a JB one, so you must be able to run any rom now. which one would you like....
ow and keep the phone in the recovery, the battery loads in there !!!
Click to expand...
Click to collapse
Thanks for all the advice and help I'll try another rom. :good:
Need a small tut ?
start in the bootloader and flash the boot.img of the rom
unhook the cable and enter recovery (to avoid error messages)
in the recovery you do :
wipe data/factory reset
wipe cache partition
advanced - wipe dalvik cache
mounts & storage - Format cache,data,system
then you mount the sdcard as a mass storage device, hook on the cable and copy the rom.zip.
UNHOOK THE CABLE BEFORE INSTALLING THE ROM !
install the rom.zip and reboot the phone.
Good luck mate.....if you need help just ask here again :good:
Mr Hofs said:
Need a small tut ?
start in the bootloader and flash the boot.img of the rom
unhook the cable and enter recovery (to avoid error messages)
in the recovery you do :
wipe data/factory reset
wipe cache partition
advanced - wipe dalvik cache
mounts & storage - Format cache,data,system
then you mount the sdcard as a mass storage device, hook on the cable and copy the rom.zip.
UNHOOK THE CABLE BEFORE INSTALLING THE ROM !
install the rom.zip and reboot the phone.
Good luck mate.....if you need help just ask here again :good:
Click to expand...
Click to collapse
Thank you again I got insert coin rom up and running, the rom it went wrong on was jellybam. :good::good::laugh:
Nice ! :thumbup:
CASE CLOSED !
At the moment it's on a bootloop with the HTC screen, although I've managed (just now) to flash CM10 which is now stuck on a loop of the CM10 Android splash screen
I'm feeling confident that this can be sorted as I can access phone through fastboot/adb and can mount the SD so all isn't lost... I'm on UK O2 HOX
Just looking for a little direction, I used to be fairly confident around the inside of my old HTC desire, but lost interest... Things are rather different with the HOX and I suspect I've maybe screwed up with some misguided bravado...
Mr Hofs has provided some excellent learning material on his responses to issues similar to mine but to no avail...
I've tried a lot of things, bootloader is unlocked, flashed boot.img and recovery.img but when I flashed x.xx.206.x - O2 UK (United Kingdom) firmware.zip with hboot 1.36 it said it failed (with no information as to why)
Just looking for pointers on where to go next!
Starting to become concerned I've made a proper mess...
mathesonewan said:
I've tried a lot of things, bootloader is unlocked, flashed boot.img and recovery.img but when I flashed x.xx.206.x - O2 UK (United Kingdom) firmware.zip with hboot 1.36 it said it failed (with no information as to why)
Click to expand...
Click to collapse
Additional to this - I've been through 10-12 pages of various fixes (searched bootloop within HOX forum) that's why the above is a little vague... They've all merged into one...
1: what hboot do you have now ?
2: what recovery are you on ?
and put the phone in the recovery in the mean time. it charges the battery there
Are you flashing cm10 or cm10.1 'cause cm10 does not support hboot 1.36.
Recovery is TWRP v2.4.1
HBoot is 1.36
and I'd read that somewhere about not supporting 1.36 and I've just checked it's 10.1 I was trying to flash
Everything sounds good to me.
Try again with my instructions:
1. Flash boot
2. Full wipe
3. Flash rom
4. Flash gapps
It should boot.
Yep....and otherwise the way around ! because i helped somebody on team-V ...it didnt work the way TT described. but actually did work the other way around
in recovery a full wipe....
install the rom and gapps
adb reboot bootloader
and flash the boot.img followed by
fastboot erase cache
fastboot reboot
TToivanen said:
Everything sounds good to me.
Try again with my instructions:
1. Flash boot
2. Full wipe
3. Flash rom
4. Flash gapps
It should boot.
Click to expand...
Click to collapse
Mr Hofs said:
Yep....and otherwise the way around ! because i helped somebody on team-V ...it didnt work the way TT described. but actually did work the other way around
in recovery a full wipe....
install the rom and gapps
adb reboot bootloader
and flash the boot.img followed by
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Right I'll try these out - If TTs method isn't successful is there anything I would need to be aware of inbetween these two methods? Or are both pretty much starting from scratch? (I hope you understand what I mean..?)
mathesonewan said:
Right I'll try these out - If TTs method isn't successful is there anything I would need to be aware of inbetween these two methods? Or are both pretty much starting from scratch? (I hope you understand what I mean..?)
Click to expand...
Click to collapse
TToivanen said:
Everything sounds good to me.
Try again with my instructions:
1. Flash boot
2. Full wipe
3. Flash rom
4. Flash gapps
It should boot.
Click to expand...
Click to collapse
I've expanded on the above steps to ensure I'm completing them correctly
1. Extracted the boot.img from the firmware zip contained within the CM10.1 zip, then ran fastboot flash boot boot.img from cmd line - this completed and reported "OKAY"
2. Full wipe done using TWRP - system wipe - for good measure wiped everything else too (wasn't sure if system was a catch all for the others or not)
3. Rom Flashed using TWRP install cmd (I've assumed this is the correct way to do it...)
4. Flashed Gapps similarly
It's now past the HTC "quietly brilliant" splash (very very quiet just now...) and is stuck on the CyanogenMod splash just circling round and round...
Going to try the other method see if I have anymore luck!
OK... So haven't had any luck with either method...
When flashing the boot.img it's behaving differently to how it did before - it now triggers the phone to reboot whereas it never did before... Is that normal?
Is there any more information I can give you guys that might narrow down the issue?
Thanks in advance!
i would try a stanrd sense based rom ..... just to check its all fine, i have seen more people that didnt get it booted, why ? no clue....
did a proper wipe....factory reset,wipe caches, dalvik cache, data, system ?
then it should work !
Just downloading the stock rom just now, going to try from there... At this point in time I'll be happy to just have a working phone!
Success!
I tried going back to the stock rom but something mad happened with the recovery (i.e. it didn't work anymore) and was replaced with a graphic of a flat HOX with a sync symbol and then the sync symbol was replaced by a red cross...
So had a minor panic, realised that something wasn't right with TWRP, so flashed on CWM, then flashed the boot.img from the stock zip, and flashed the rom perfectly.
I'm tempting fate but I started this process wanting a new rom and I will finish it, but I'm glad my phone isn't bricked!
Thanks to you both for your input, your faith certainly encouraged me to not give in!
Keep up the awesome work!
Well you can always try again to install CM10.1.....again but now with cwm.
I went with viper - which has flashed successfully, but everytime I unlock the screen it comes up with a white HTC screen... haha time to start trawling the viper forum... or go for CM again!
Strange.....tho i have the idea you missed something in the wiping process ?
Funnily enough for a "low stress" option I wiped everything (CWM > advanced > wipe em all) then reflashed the boot.img from CM10.1, then flashed the rom and it's loading into CM10 but repeatedly flashes "unfortunately the process com.android.phone has stopped"
There is something funny going on if no custom roms are working no?
Wipe data/factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache,data,system
That should do it.....
ohhhhh the mounts and storage one is new to me... I'll try that now with a custom...
Meh didn't work... I'm going to reflash the stock and go to bed I think!
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!
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.