[Q] I completely messed up my phone. (noob) - One (M8) Q&A, Help & Troubleshooting

Hello,
I tried to update the firmware on my phone and completely messed up my phone while doing it. No there is no os left on the phone.
Trying to install a new rom either trough adb or over the external sd also failed.
The reasons for this mess is that I don´t understand what I am doing,
its actually a trial an error process.
I am now really in the need of help.
Please help me.
Information:
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
M8_Ul PVT SHIP S-Off
CID- 11111111
The only thing that is still working on this phone is TWRP 2.8.1.0
So:
what files do I have to flash?
The files I tried to flash didn´t work…
Mainly it said: E: Unable to open zip file. Error flashing zip
Help would be really appreciated.
I am quite frustrated right now.
My operating system is Mac os X.
Thanks.

Try older 2.7 TWRP and flash ROM from extSD. That is old firmware so a ROM based on 1.5x firmware.

LeoMaier said:
Hello,
I tried to update the firmware on my phone and completely messed up my phone while doing it. No there is no os left on the phone.
Click to expand...
Click to collapse
Try this RUU : http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563
fast and clean

flyera343 said:
Try older 2.7 TWRP and flash ROM from extSD. That is old firmware so a ROM based on 1.5x firmware.
Click to expand...
Click to collapse
Thanks for your reply.
I am going to try.

pagoweb said:
Try this RUU : http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563
fast and clean
Click to expand...
Click to collapse
Thanks for your kind answer.
I really appreciate the help I get here.

failed
pagoweb said:
Try this RUU : http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563
fast and clean
Click to expand...
Click to collapse
I put the recommended zip on the external sd card.
This is what happened.
Sigh.
Updating partition details:
E: resource type (font) failed to load
E: resource type (font) failed to load
E: resource type (font) failed to load
Full SELinux support is present.
MTP enabled
E. unable to open zip file
Error flashing zip

LeoMaier said:
I put the recommended zip on the external sd card.
This is what happened.
Sigh.
Updating partition details:
E: resource type (font) failed to load
E: resource type (font) failed to load
E: resource type (font) failed to load
Full SELinux support is present.
MTP enabled
E. unable to open zip file
Error flashing zip
Click to expand...
Click to collapse
Are you trying to flash it via recovery ?
Read carefully op's instructions from the thread linked.
This file is NOT to be flashed via recovery. you need to flash it via bootloader (fastboot oem rebootRUU ...) or rename it to 06PBIMG.zip and put it in your sd-ext root and boot on hboot it'll fint it and try to flash it automatically.
BEWARE as this is a RUU and it may wipe everything (incl. internal mem)

pagoweb said:
Are you trying to flash it via recovery ?
Read carefully op's instructions from the thread linked.
This file is NOT to be flashed via recovery. you need to flash it via bootloader (fastboot oem rebootRUU ...) or rename it to 06PBIMG.zip and put it in your sd-ext root and boot on hboot it'll fint it and try to flash it automatically.
BEWARE as this is a RUU and it may wipe everything (incl. internal mem)
Click to expand...
Click to collapse
yes I tried to flash it via recovery.
I will take care with the next steps.

pagoweb said:
Are you trying to flash it via recovery ?
Read carefully op's instructions from the thread linked.
This file is NOT to be flashed via recovery. you need to flash it via bootloader (fastboot oem rebootRUU ...) or rename it to 06PBIMG.zip and put it in your sd-ext root and boot on hboot it'll fint it and try to flash it automatically.
BEWARE as this is a RUU and it may wipe everything (incl. internal mem)
Click to expand...
Click to collapse
It worked.
Thanks so much for your help.
I know your name from cm lollipop pre nightlies thread.
I couldn´t follow your updates anymore because of my wrong firmware.

LeoMaier said:
It worked.
Thanks so much for your help.
I know your name from cm lollipop pre nightlies thread.
I couldn´t follow your updates anymore because of my wrong firmware.
Click to expand...
Click to collapse
glad it worked... now you'll be able to enjoy next releases of cm12 ;p

Related

[Q] HTC Wildfire Buzz: stuck and doesnt accept custom roms or RUUs

Hi,
I have HTC Wildfire Buzz which had a problem getting stucking at HTC logo and kept rebooting. I decided to unlock the bootloader and flash a custom rom, I downloaded CWM recovery and tried flashing a custom rom but got an error and then I tried flashing different variations of CM roms such as update-cm-7.1.0.1-buzz-signed.zip and cm_buzz_full-256.zip but I got different types of errors including Err 7.
The other custom rom I tried to install was Android_Freedom_Wildfire_By_MONI69_a2sd but I kept getting the following error:
E:Can't symlink /system/bin/cat
E:Failure at line 10: symlink toolbox SYSTEM:bin/cat
installation aborted
I tried running different relevant RUUs based on my phone region but always ended up with error due to the fact that the firmware version currently installed is 2.46.0.0 and all the RUUs have versions lower than it.
I would appreciate providing me with your guidance and advice, my phone info is provided below.
INFOversion: 0.5
INFOversion-bootloader: 1.02.0000
INFOversion-baseband: 3.35.20.10
INFOversion-cpld: None
INFOversion-microp: 0622
INFOversion-main: 2.46.0.0
INFOserialno: SH13TPY12305
INFOimei: xxxxxxxxxxxxxx
INFOproduct: buzz
INFOplatform: HBOOT-7225
INFOmodelid: PC4910000
INFOcidnum: HTC__044
INFObattery-status: good
INFObattery-voltage: 4211mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 42e5cc47
INFOhbootpreupdate: 11
INFOgencheckpt: 0
yabdali said:
Hi,
I have HTC Wildfire Buzz which had a problem getting stucking at HTC logo and kept rebooting. I decided to unlock the bootloader and flash a custom rom, I downloaded CWM recovery and tried flashing a custom rom but got an error and then I tried flashing different variations of CM roms such as update-cm-7.1.0.1-buzz-signed.zip and cm_buzz_full-256.zip but I got different types of errors including Err 7.
The other custom rom I tried to install was Android_Freedom_Wildfire_By_MONI69_a2sd but I kept getting the following error:
E:Can't symlink /system/bin/cat
E:Failure at line 10: symlink toolbox SYSTEM:bin/cat
installation aborted
I tried running different relevant RUUs based on my phone region but always ended up with error due to the fact that the firmware version currently installed is 2.46.0.0 and all the RUUs have versions lower than it.
I would appreciate providing me with your guidance and advice, my phone info is provided below.
INFOversion: 0.5
INFOversion-bootloader: 1.02.0000
INFOversion-baseband: 3.35.20.10
INFOversion-cpld: None
INFOversion-microp: 0622
INFOversion-main: 2.46.0.0
INFOserialno: SH13TPY12305
INFOimei: xxxxxxxxxxxxxx
INFOproduct: buzz
INFOplatform: HBOOT-7225
INFOmodelid: PC4910000
INFOcidnum: HTC__044
INFObattery-status: good
INFObattery-voltage: 4211mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 42e5cc47
INFOhbootpreupdate: 11
INFOgencheckpt: 0
Click to expand...
Click to collapse
Hello dude...i have the same phone with exactly same specs n had d same prob
go to fastboot,connect usb
now u have a .img file in ur rom's zip.
extract it to fastboot folder
via cmd go to fastboot folder with ur ph connected.. type
fastboot flash boot xxx.img
it will take some time
nxt flash cwm if u dont hv it
then get a micro sd wid ur rom(unedited) and flash it via cwm...disable signature verification if needed
press d thanks button n voila u have ur nw rom
ontheflames said:
Hello dude...i have the same phone with exactly same specs n had d same prob
go to fastboot,connect usb
now u have a .img file in ur rom's zip.
extract it to fastboot folder
via cmd go to fastboot folder with ur ph connected.. type
fastboot flash boot xxx.img
it will take some time
nxt flash cwm if u dont hv it
then get a micro sd wid ur rom(unedited) and flash it via cwm...disable signature verification if needed
press d thanks button n voila u have ur nw rom
Click to expand...
Click to collapse
Hi, Thanks for your advice, unfortunately it didnt work! I tried the following:
Extracting the rom zip and flashing boot.img via fastboot then using CWM flashing the rom xxxx.zip.
update-cm-7.1.0.1-buzz-signed.zip error:
assert failedackage_extract_file("boot.img","/tmp/boot.img")
E:error in /sdcard/update-cm-7.1.0.1-buzz-signed.zip
(Status 7)
Installation aborted
Android_Freedom_Wildfire_By_MONI69 error:
E:Can't symlink /system/bin/cat
E:Failure at line 10: symlink toolbox SYSTEM:bin/cat
installation aborted
Hope this gives further insights about the problem, any suggestion advise would be highly appreciated.
hey man, silly question but are you sure you are doing a full factory wipe, data wipe cache wipe and dalvick cache wipe?
you should do the wipes every time you try to flash a new rom.
heavy_metal_man said:
hey man, silly question but are you sure you are doing a full factory wipe, data wipe cache wipe and dalvick cache wipe?
you should do the wipes every time you try to flash a new rom.
Click to expand...
Click to collapse
Yes, I use CWM to do factory reset, cache, dalvick wipes everytime I flash a rom!
yabdali said:
Hi, Thanks for your advice, unfortunately it didnt work! I tried the following:
Extracting the rom zip and flashing boot.img via fastboot then using CWM flashing the rom xxxx.zip.
update-cm-7.1.0.1-buzz-signed.zip error:
assert failedackage_extract_file("boot.img","/tmp/boot.img")
E:error in /sdcard/update-cm-7.1.0.1-buzz-signed.zip
(Status 7)
Installation aborted
Android_Freedom_Wildfire_By_MONI69 error:
E:Can't symlink /system/bin/cat
E:Failure at line 10: symlink toolbox SYSTEM:bin/cat
installation aborted
Hope this gives further insights about the problem, any suggestion advise would be highly appreciated.
Click to expand...
Click to collapse
Another alternative is formating all partitions before flashing..
and btw did u extract the whole zip for boot.img?
what is ur cwm version?
did u try disabling signature check and script asserts??
ontheflames said:
Another alternative is formating all partitions before flashing..
and btw did u extract the whole zip for boot.img?
what is ur cwm version?
did u try disabling signature check and string asserts??
Click to expand...
Click to collapse
Hi, thanks for your continous support, I tried the following but not matter what rom I flashed I still get some sort of an error. As for your question regarding the boot.img, yes I extracted the xxxx.zip flashed boot.img via fastboot pulled the batter started CWM and installed the original xxxx.zip. I tried the partiations formatting, below are the details.
ClockworkMod Recovery v2.5.0.7
Green color
wipe data/factory
wip cache
wipe delivak (E: can't mount /dev/block.mmcblk0p2)
format system
format boot
format data
format cache
toggle script asserts/signature (disabled)
Rom: cm-buzz_full-256.zip
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/cm-buzz_full-256.zip
(Status 7)
Installation aborted.
Rom: update-cm-7.1.0.1-buzz-signed.zip
E:Error in /sdcard/update-cm-7.1.0.1-buzz-signed.zip
(Status 0)
Installation aborted
I also get package_extract_file("boot.img","/tmp/boot.img") error in some other roms.
yabdali said:
Hi, thanks for your continous support, I tried the following but not matter what rom I flashed I still get some sort of an error. As for your question regarding the boot.img, yes I extracted the xxxx.zip flashed boot.img via fastboot pulled the batter started CWM and installed the original xxxx.zip. I tried the partiations formatting, below are the details.
ClockworkMod Recovery v2.5.0.7
Green color
wipe data/factory
wip cache
wipe delivak (E: can't mount /dev/block.mmcblk0p2)
format system
format boot
format data
format cache
toggle script asserts/signature (disabled)
Rom: cm-buzz_full-256.zip
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/cm-buzz_full-256.zip
(Status 7)
Installation aborted.
Rom: update-cm-7.1.0.1-buzz-signed.zip
E:Error in /sdcard/update-cm-7.1.0.1-buzz-signed.zip
(Status 0)
Installation aborted
I also get package_extract_file("boot.img","/tmp/boot.img") error in some other roms.
Click to expand...
Click to collapse
Strange...btw how did ur wf stop booting all of a sudden? I think u have failed to get proper root and unlocked bootloader
pl verify it in hboot..on top it must display 'UNLOCKED'
more when u comment
Hit thanks if i helped u
ontheflames said:
Strange...btw how did ur wf stop booting all of a sudden? I think u have failed to get proper root and unlocked bootloader
pl verify it in hboot..on top it must display 'UNLOCKED'
more when u comment
Hit thanks if i helped u
Click to expand...
Click to collapse
Its my wife's phone. Out of the blue started getting stuck in HTC logo and kept rebooting. Yes, its unlocked using HTCDEV and it shows that in hboot "UNLOCKED".
Appreciate your further feedback..
I'd first try a different sd card, it looks to me like it's not reading properly with some of those errors, mount /system from Cwm mounts and storage option before wiping and flashing the new rom too, if that fails try fastboot flashing Cwm 5.0.2.0, then try again. I've never seen this problem before so my apologies if I'm way off the mark.
Sent from my HTC Wildfire using xda premium
i have the same problem here.
hboot 1.02.0000 - won't downgrade for anything in the world
s-on
in cwm i cannot install any rom. says "status 0 installation aborted" or "bad"
the ruu's are not working either.
i don't have a backup or a rom installed. if there's anyone who can provide me a buzz backup so i can restore into my phone, i would much appreciate it. i think is the single thing i didn't try.
seagerfreak said:
i have the same problem here.
hboot 1.02.0000 - won't downgrade for anything in the world
s-on
in cwm i cannot install any rom. says "status 0 installation aborted" or "bad"
the ruu's are not working either.
i don't have a backup or a rom installed. if there's anyone who can provide me a buzz backup so i can restore into my phone, i would much appreciate it. i think is the single thing i didn't try.
Click to expand...
Click to collapse
It already has been mentioned a few times here in the forum: htcdev won't give you s-off and it's not absolutely clear (= not confirmed) that can get s-off after the htcdev unlock (because you can't downgrade the HBOOT).
I have no idea if there's a possibility but it doesn't look good - there are 2 other threads regarding this issue here in Q&A or General section - you might want to have a look.
For the install problem I'm pretty sure that's something different as you usually should be able to install a ROM...
i have looked into othet threads. nothing works
seagerfreak said:
i have looked into othet threads. nothing works
Click to expand...
Click to collapse
You need to relock your boot loader for an ruu to work. relock the bootloader and remove the rom.zip from the htcdev bootloader unlock ruu. Remember an ruu with a lower hboot will not run. Rename it to pc49img.zip and put it on the root of your sdcard. Boot to hboot and allow the bootloader to flash the rom. but if I was you I would just try to get access to an xtc clip and fully s-off the phone. Then it will run any ruu and custom rom.
Sent from my HTC Sensation using xda premium
heavy_metal_man said:
You need to relock your boot loader for an ruu to work. relock the bootloader and remove the rom.zip from the htcdev bootloader unlock ruu. Remember an ruu with a lower hboot will not run. Rename it to pc49img.zip and put it on the root of your sdcard. Boot to hboot and allow the bootloader to flash the rom. but if I was you I would just try to get access to an xtc clip and fully s-off the phone. Then it will run any ruu and custom rom.
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
thanx for the answer. i have relocked my bootloader. renamed the rom and put it on the root of the sdcard. the hboot shows a loading bar, but after loading, nothing happens. the part with the removing the rom.zip from the htcdev bootloader unlock ruu i didn't understand. can you be more specific? thanx
quick edit: when running a ruu, it gives me usb connection error
Here's the quick guide
Install hTc drivers successfully on pc.
Remove hTc sync and other related apps.
Now download clockworkmod recovery(whichever you want) and fastboot+adb kit on pc.
Open fastboot.
Connect ur phone. Load the bootloader and then fastboot. Fastboot mode(something like that) should be on your phone. Paste recovery and boot image in fastboot folder.
Type fastboot devices
Type fastboot flash boot boot.img(i faintly remember what this was, sorry )
Type fastboot flash 'recoveryname'.zip
After that disconnect ur phone.
Select recovery.
(If u dont see anything, it was unsuccessful, hold vol up+power to see default recovery.)
Now install roms like this(http://forum.xda-developers.com/showthread.php?t=1851096):p(my rom) via recovery.
Hit Thanks.
You are done
Note:s off is not required for flashing a custom rom, however an unlocked bootloader is.
Edit: Hey sorry didnt read my earlier posts, after all wf is slow on internet.
However this is the problem where u you are flashing incorrect boot.img
Make sure its from your rom, or try using the one in cm7, try both as Im not exactly certain. If u have cwm it asserts that u have root and you can flash roms.
ontheflames said:
Here's the quick guide
Install hTc drivers successfully on pc.
Remove hTc sync and other related apps.
Now download clockworkmod recovery(whichever you want) and fastboot+adb kit on pc.
Open fastboot.
Connect ur phone. Load the bootloader and then fastboot. Fastboot mode(something like that) should be on your phone. Paste recovery and boot image in fastboot folder.
Type fastboot devices
Type fastboot flash boot boot.img(i faintly remember what this was, sorry )
Type fastboot flash 'recoveryname'.zip
After that disconnect ur phone.
Select recovery.
(If u dont see anything, it was unsuccessful, hold vol up+power to see default recovery.)
Now install roms like this(http://forum.xda-developers.com/showthread.php?t=1851096):p(my rom) via recovery.
Hit Thanks.
You are done
Note:s off is not required for flashing a custom rom, however an unlocked bootloader is.
Edit: Hey sorry didnt read my earlier posts, after all wf is slow on internet.
However this is the problem where u you are flashing incorrect boot.img
Make sure its from your rom, or try using the one in cm7, try both as Im not exactly certain. If u have cwm it asserts that u have root and you can flash roms.
Click to expand...
Click to collapse
i made every step you told me to. this is what i get.
the only way i can make the phone visible in adb, is in recovery. being unable to boot a rom, i cannot set the usb debugging mode. so, everything that i will make, is via fastboot or ruu. but ruu gives me usb connection error or error [155] in fastboot, and baterry < 30% in adb mode.
What if you unlock your bootloader again and flash a recovery.img from fastboot? Maybe there is problem with your cwm recovery. I guess you have already tried formatting you sd card, tried a different sd card and tried different custom roms.
I would definitely try to get some more charge in your phone first because if you loose power while flashing it could end up really bad. An RUU won't install on low battery (i thought you needed >70%) what if you charge up and run ruu from adb again?
Rename your CID to HTC_001 (fastboot writecid HTC__001). Relock your bootloader using fastboot oem lock. Run a WWE RUU. Use the rooting link in my sig.
Done, and don't ever root with HTCDev again.
hans moleman said:
What if you unlock your bootloader again and flash a recovery.img from fastboot? Maybe there is problem with your cwm recovery. I guess you have already tried formatting you sd card, tried a different sd card and tried different custom roms.
I would definitely try to get some more charge in your phone first because if you loose power while flashing it could end up really bad. An RUU won't install on low battery (i thought you needed >70%) what if you charge up and run ruu from adb again?
Click to expand...
Click to collapse
i tried every possible combination of cwms and roms.
usaff22 said:
Rename your CID to HTC_001 (fastboot writecid HTC__001). Relock your bootloader using fastboot oem lock. Run a WWE RUU. Use the rooting link in my sig.
Done, and don't ever root with HTCDev again.
Click to expand...
Click to collapse
i get this error
C:\android sdk\platform-tools>fastboot oem writecid HTC__001
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
C:\android sdk\platform-tools>
Click to expand...
Click to collapse
just to be clear, the phone was in this state, it's not mine. i am only trying to put whatever rom i can so i can make it work

[Q] Bootloop

Hi, I've tried to root my htc one x with Insecure boot & root method without locking bootloader fist and it went into a bootloop, then I've tried to do the recovery from this guide http://forum.xda-developers.com/showthread.php?t=1609190 but i dont know where to find the correct ruu, also I cannot open rom.zip file form the ruu I've found RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed, my phone is from three uk. I'm not sure if it's rooted or not and don't really know how to check it from bootloader or revovery. Could anyone please help me, thanks.
kalasster said:
Hi, I've tried to root my htc one x with Insecure boot & root method without locking bootloader fist and it went into a bootloop, then I've tried to do the recovery from this guide http://forum.xda-developers.com/showthread.php?t=1609190 but i dont know where to find the correct ruu, also I cannot open rom.zip file form the ruu I've found RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed, my phone is from three uk. I'm not sure if it's rooted or not and don't really know how to check it from bootloader or revovery. Could anyone please help me, thanks.
Click to expand...
Click to collapse
please post the result from command fastboot getvar all and delete your IMEI and S/N.
version: 0.5a
version-bootloader: 1.72.0000
version-baseband: 5.1204.167.31H
version-cpld: None
version-microp: None
version-main: 4.18.771.4
serialno:
imei:
product: endeavoru
platform: HBOOT-T30S
modelid: PJ4610000
cidnum: H3G__001
battery-status: good
battery-voltage: 3612mV
devpower: 0
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
Click to expand...
Click to collapse
is that it?
Look here: http://forum.xda-developers.com/showthread.php?t=1975140
I think there is a nandroid for your phone.
This should be the one: https://dl.dropboxusercontent.com/u/64946445/JB-4.2.2-stock-factory_H3G_001.7z
Read instructions carefully!!
[email protected]|-|oR said:
Look here: http://forum.xda-developers.com/showthread.php?t=1975140
I think there is a nandroid for your phone.
This should be the one: https://dl.dropboxusercontent.com/u/64946445/JB-4.2.2-stock-factory_H3G_001.7z
Read instructions carefully!!
Click to expand...
Click to collapse
I cannot mount a device into PC in recovery mode, its comming on adb devices and I cant see it on devices manager. How to I copy rom on my sd card? I would actually would prefer to use Android Revolution HD mod is it possible?
kalasster said:
I cannot mount a device into PC in recovery mode, its comming on adb devices and I cant see it on devices manager. How to I copy rom on my sd card? I would actually would prefer to use Android Revolution HD mod is it possible?
Click to expand...
Click to collapse
How did you get the fastboot getvar all, then?
Did you try adb reboot recovery? It should work. Or, adb reboot bootloader, and once there, select recovery.
Do you have stock or custom recovery?
If on stock, download CWM from here: https://www.dropbox.com/s/2ph8jrr6lrmjqfc/fastboot.zip (there are other files, too, don't worry)
Flash CWM from fastboot and bootloader: fastboot flash recovery recovery-cwm.img
Go to your recovery and mount sd card.
Copy the nandroid backup and follow the instructions from the link in my previous post.
Once you're back to stock, you can flash any ROM at your will. These instructions are to get your phone out of bootloop.
icitiesc article
C:\android>fastboot flash revovery recovery-cwm.img
sending 'revovery' (5742 KB)...
OKAY [ 0.711s]
writing 'revovery'...
FAILED (remote: not allowed)
finished. total time: 0.917s
Click to expand...
Click to collapse
also i had cwm recovery before, but when I tried to use Mounts and storage menu/mount usb storage I'm getting back E:unable to opem ums lunfile(no such file or disc) am I doing something wrong?\
I also mount sd but still my PC doesnt see anything.
kalasster said:
also i had cwm recovery before, but when I tried to use Mounts and storage menu/mount usb storage I'm getting back E:unable to opem ums lunfile(no such file or disc) am I doing something wrong?\
I also mount sd but still my PC doesnt see anything.
Click to expand...
Click to collapse
Hm!
This is strange.
I recommend you uninstall HTC drivers, and try installing them again. That could be the reason of your trouble.
Do other fastboot commands work properly? Did you do fastboot erase cache? Sometimes that helps too.
There is also a way with "adb push..." but I don't remember it from the top of my head...
If Mr. Hofs woud be so kind to help you...
And, watch your battery, mate, don't let it drain out!
C:\android>fastboot flash revovery recovery-cwm.img
sending 'revovery' (5742 KB)...
OKAY [ 0.711s]
writing 'revovery'...
FAILED (remote: not allowed)
finished. total time: 0.917s
Click to expand...
Click to collapse
kalasster said:
also i had cwm recovery before, but when I tried to use Mounts and storage menu/mount usb storage I'm getting back E:unable to opem ums lunfile(no such file or disc) am I doing something wrong?\
I also mount sd but still my PC doesnt see anything.
Click to expand...
Click to collapse
First you must to flash recovery not REVOVERY. Second flash Philz recovery because it is the only one that work without any problem every time, mount SD storage and wait 1-3 minutes to mount the stodage and you can start restore nandroid.
Yeah flash philz indeed, the ems lunfile error is because you are using an old recovery that not support usb mass storage !
I already did it, now i cannot restore nandroid backup, because I cannot use JB version, since my hboot is to old and there is not firmware for my CID (H3G_001) so i cannot update hboot. I cannot find any older nandroid backup version for cwm recovery for my CID. Also when i tried to restore TWRP nandroid and I couldn't because I can't use touch in TWRP recovery. Anyone has any idea on how can I resolve this please?
Or is it something else my hboot ver is 1.72 and I cannot flash 16mb boot.img, but all of the nandroid recoveries I'm finding have one of that size.
kalasster said:
I already did it, now i cannot restore nandroid backup, because I cannot use JB version, since my hboot is to old and there is not firmware for my CID (H3G_001) so i cannot update hboot. I cannot find any older nandroid backup version for cwm recovery for my CID. Also when i tried to restore TWRP nandroid and I couldn't because I can't use touch in TWRP recovery. Anyone has any idea on how can I resolve this please?
Or is it something else my hboot ver is 1.72 and I cannot flash 16mb boot.img, but all of the nandroid recoveries I'm finding have one of that size.
Click to expand...
Click to collapse
Man install Philz recovery and this is your nandroid download and unzip in folder on the sd card flash the nandroid flash the boot.img flash the recovery.img from nandroid.
And the boot.img in this nandroid is only 8 MB from where you take this 16 MB
Thant said:
Man install Philz recovery and this is your nandroid download and unzip in folder on the sd card flash the nandroid flash the boot.img flash the recovery.img from nandroid.
And the boot.img in this nandroid is only 8 MB from where you take this 16 MB
Click to expand...
Click to collapse
Yeah, this is TWRP nandroid and TWRP is not working (no touch), i managed to just flash cyonogenmod though, so everything is fine, also i think i found firmware for my model, so I'll uprage hboot version and flash Revolution HD, thanks for your help everyone.
kalasster said:
Yeah, this is TWRP nandroid and TWRP is not working (no touch), i managed to just flash cyonogenmod though, so everything is fine, also i think i found firmware for my model, so I'll uprage hboot version and flash Revolution HD, thanks for your help everyone.
Click to expand...
Click to collapse
Philz recovery work with TWRP and CWM nandroid I can't understand what is your problem with Phi9lz recovery and why you can't restore nandroid!!!!

Cant flash Stock Rom over, tried 3 different ones.

Trying to flash my rom to stock so i can install the OTA updates. I believe im on firmware 1.54.. Here is my getvar all results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I have tried all 3 of the firmware backup roms (including the 1.2 one) from the stock nandroid backups.
Please can someone help ive been trying to do this for about 8 hours now.
EDIT:
Hello,
I tried again to flash to stock. I tried versions 1.12 stock and 1.54 to go back, using 2.7.02 TWRP (2.7.0.1 doesnt boot) and it still says failed.
Anyone know how to work around this or help me get to stock. I want to update my phone to latest version!
looking in this wrong corner mate, you need a backup from the voda cid. your official version is not 2.22.401 !
check the backup thread and compare by CID and not by buildnumber of your custom rom
and BTW read the whole OP there. its literally written there what to do, take the time for it. hboots, software numbers and cids.....its all explained
saw that ? its not rocket science, just simple look & compare. my 6 year old does this also in pre school
think you have info info now to try again.
cheers
Mr Hofs said:
saw that ? its not rocket science, just simple look & compare. my 6 year old does this also in pre school
think you have info info now to try again.
cheers
Click to expand...
Click to collapse
No need to try and make me look silly loool. The first few lines in my post say I have tried the versions starting 1.54 and 1.2.. I got them from the VOPAP001 section. Those are the ones which are giving me a failed attempt.
Everytime I flash it it just says failed and error mounting E:/cache. I looked up the error I was receiving and based off what I read it seemed I was using the wrong rom so I came over here to ask.
SO the question with the 2.22 was just another attempt as trying something that might work.
Could you suggest something else please?
EDIT: Also does it matter what version of twrp I am using? 2.8.3 doesnt boot, gets stuck in white screen, 2.8.1 doesnt get into white screen, thats the one i have flashed as recovery
sorry not once tried to make you look silly.
cheers.
Mr Hofs said:
sorry not once tried to make you look silly.
cheers.
Click to expand...
Click to collapse
"Just simple look & compare. my 6 year old does this also in pre school"
But okay. Is there something else you would recommend me trying?
sorry if that offended you, thats something we use here as a phrase a lot.
apologies.
Mr Hofs said:
sorry if that offended you, thats something we use here as a phrase a lot.
apologies.
Click to expand...
Click to collapse
No worries!
Update:: I have tried to use 1.54 from htc_001 CID as well as the ones from VODAP001 however I still get failed.
Anyone have any clue as to why this is??
THanks!
use an older twrp 2.7 range. the newer ones are compiled differently and therefore doesn't work on your lower hboot.
restore the 1.12 voda nand and flash back the matching stock recovery. then ota up again
imAmbitious said:
"Just simple look & compare. my 6 year old does this also in pre school"
But okay. Is there something else you would recommend me trying?
Click to expand...
Click to collapse
The "error mounting E:/cache" always happens after you have flashed a recovery and erased cache (TWRP prints it 3 times on my phone)
The failed usually means your download was corrupt or it was created with a different recovery than what your using, if the recovery was created with Phils you can't restore it with TWRP. Also are you restoring the backup from the ext_sd or the internel sdcard or a usb-otg. Are you MD5 checking your downloads ?
If your having problems with the recovery partition also you phone may have damaged partitions ..have a look at mike1986 fix
http://android-revolution-hd.blogspot.com/2014/09/how-to-fix-random-reboots-on-htc-one-m8.html
clsA said:
The "error mounting E:/cache" always happens after you have flashed a recovery and erased cache (TWRP prints it 3 times on my phone)
The failed usually means your download was corrupt or it was created with a different recovery than what your using, if the recovery was created with Phils you can't restore it with TWRP. Also are you restoring the backup from the ext_sd or the internel sdcard or a usb-otg. Are you MD5 checking your downloads ?
If your having problems with the recovery partition also you phone may have damaged partitions ..have a look at mike1986 fix
http://android-revolution-hd.blogspot.com/2014/09/how-to-fix-random-reboots-on-htc-one-m8.html
Click to expand...
Click to collapse
I am using twrp for the recovery, does it matter which version of twrp i use or does it have to be the same version the one where the backup was made?
Thanks for the second link as well, whenever I try to restore my data from previous backup it fails at 85%, ill see if that fixes it.
Thanks for your help, will post with an update once tried.
Mr Hofs said:
use an older twrp 2.7 range. the newer ones are compiled differently and therefore doesn't work on your lower hboot.
restore the 1.12 voda nand and flash back the matching stock recovery. then ota up again
Click to expand...
Click to collapse
This is good advice ^^
imAmbitious said:
I am using twrp for the recovery, does it matter which version of twrp i use or does it have to be the same version the one where the backup was made?
Thanks for the second link as well, whenever I try to restore my data from previous backup it fails at 85%, ill see if that fixes it.
Thanks for your help, will post with an update once tried.
Click to expand...
Click to collapse
Like Mr Hofs said the older version of TWRP may be all you need
http://forum.xda-developers.com/showthread.php?t=2717932
Hello,
I tried again to flash to stock. I tried versions 1.12 stock and 1.54 to go back, using 2.7.02 TWRP (2.7.0.1 doesnt boot) and it still says failed.
Anyone know how to work around this or help me get to stock. I want to update my phone to latest version!
1. Install TWRP 2.8.1.0 - http://techerrata.com/browse/twrp2/m8
command fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
2. Download TWRP backup 1.54.161.10 - https://mega.co.nz/#!HJ0AlKjJ!ex5IiqKhUnsZBPKdJlVvToU6-htL2QtjAjuxsP1QS6o
3. Download stock 1.54.161.10 recovery - http://sourceforge.net/projects/htconem8/files/Recovery/1.54.161.10_recovery.img/download
4. Extract the downloaded TWRP_1.54.161.10.rar on PC
5. Transfer the extracted TWRP_1.54.161.10 folder (the last folder) and its content to the backup path on your device
6. Reboot to TWRP, wipe your device - in TWRP go to wipe - advance - select dalvik cache, cache, data, system (only these)
7. Restore the transferred backup - make sure all boot, data & system are ticked - swipe to restore
8. In reboot menu select bootloader
9. fastboot flash stock recovery that you downloaded - command fastboot flash recovery 1.54.161.10_recovery.img
10. reboot - check for OTA, download, install
11. repeat step 10 until the last OTA 4.19.161.2
12. done
If you want to flash TWRP again, use the latest TWRP 2.8.5.0 after last OTA 4.19.161.2
ckpv5 said:
1. Install TWRP 2.8.1.0 - http://techerrata.com/browse/twrp2/m8
command fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
2. Download TWRP backup 1.54.161.10 - https://mega.co.nz/#!HJ0AlKjJ!ex5IiqKhUnsZBPKdJlVvToU6-htL2QtjAjuxsP1QS6o
3. Download stock 1.54.161.10 recovery - http://sourceforge.net/projects/htconem8/files/Recovery/1.54.161.10_recovery.img/download
4. Extract the downloaded TWRP_1.54.161.10.rar on PC
5. Transfer the extracted TWRP_1.54.161.10 folder (the last folder) and its content to the backup path on your device
6. Reboot to TWRP, wipe your device - in TWRP go to wipe - advance - select dalvik cache, cache, data, system (only these)
7. Restore the transferred backup - make sure all boot, data & system are ticked - swipe to restore
8. In reboot menu select bootloader
9. fastboot flash stock recovery that you downloaded - command fastboot flash recovery 1.54.161.10_recovery.img
10. reboot - check for OTA, download, install
11. repeat step 10 until the last OTA 4.19.161.2
12. done
If you want to flash TWRP again, use the latest TWRP 2.8.5.0 after last OTA 4.19.161.2
Click to expand...
Click to collapse
If you were infront of me id hug you.

[Solved] Cannot install CM12 due to outdated bootloader

Hello.
I am currently running ParanoidAndroid 4.6Beta5. Since PA's developement for M8 seems to be dead, I wanted to try CM12.
When I tried to install latest nightly build of CM12 I got a message that my bootloader (3.16) is not supported, and that I need to update it to 3.18 or 3.19.
I googled a bit and found out that in order to update it, I need to restore latest official ROM.
I managed to restore official ROM (3.28.401.6, based on android 4.4.4) but the WiFi wasn't working, so I couldn't do much there. I relocked bootloader and flashed official recovery, and then tried to run RUU.
RUU failed with code [315]. I ran out of ideas and google results to browse.
I unlocked my bootloader again, flashed clockworkmod recovery back, and restored my backup of ParanoidAndroid.
Right now the phone is in the same state as when I was starting.
Here is some basic info about my phone:
Model: HTC ONE M8 16GB Unlocked (purchased on amazon; network free)
CID: HTC_001
Bootloader: Unlocked
Recovery: Clockworkmod Touch v6.0.4.8
S status: S-ON
Click to expand...
Click to collapse
So the basic question is: how to flash CM12 on HTC One M8? I spent so many hours on it without any result, so this thread is my last chance.
Edit: SOLVED!
See http://forum.xda-developers.com/showpost.php?p=58859881&postcount=13 for solution.
ProTofik said:
Hello.
I am currently running ParanoidAndroid 4.6Beta5. Since PA's developement for M8 seems to be dead, I wanted to try CM12.
When I tried to install latest nightly build of CM12 I got a message that my bootloader (3.16) is not supported, and that I need to update it to 3.18 or 3.19.
I googled a bit and found out that in order to update it, I need to restore latest official ROM.
I managed to restore official ROM (3.28.401.6, based on android 4.4.4) but the WiFi wasn't working, so I couldn't do much there. I relocked bootloader and flashed official recovery, and then tried to run RUU.
RUU failed with code [315]. I ran out of ideas and google results to browse.
I unlocked my bootloader again, flashed clockworkmod recovery back, and restored my backup of ParanoidAndroid.
Right now the phone is in the same state as when I was starting.
Here is some basic info about my phone:
So the basic question is: how to flash CM12 on HTC One M8? I spent so many hours on it without any result, so this thread is my last chance.
Click to expand...
Click to collapse
Since you are S-On, you can't just flash the firmware, which is the easiest way. But you can use this method.
I'll give you an RUU to flash. But before you flash it, backup everything that is important to you, because this will wipe your phone.
Download this.
Rename it to 0P6BIMG.zip (that's a zero not the letter)
Put it onto the root of your extSD (By root of I mean just on the card and not a folder)
Boot into bootloader and choose hboot.
Follow the prompts (vol up to flash, power button to reboot when done)
Congratulations! You now have the latest lollipop firmware.
Make sure you delete the renamed zip from your extSD when you are done. If you don't delete it, it will try to update again every time you go back to hboot.
Since you are S-On, you can't just flash the firmware
Click to expand...
Click to collapse
What do you mean by firmware. Bootloader or ROM? I did 'just' flash PA without a problem.
I guess the ROM you liked is the latest official one. By installing it I will get my bootloader updated and then I will be able to flash CM12. Do I get this right? or will I get stuck on stock forever?
Edit: I just tried to flash your image using hboot but it didn't work. Check file attached.
I checked MD5 checksum just to make sure that it did download correctly and it does match with the one on the download page. However, I did notice that when I'm trying to open that zip file on my PC I'm getting an error saying that the archive is corrupted.
ProTofik said:
What do you mean by firmware. Bootloader or ROM? I did 'just' flash PA without a problem.
I guess the ROM you liked is the latest official one. By installing it I will get my bootloader updated and then I will be able to flash CM12. Do I get this right? or will I get stuck on stock forever?
Edit: I just tried to flash your image using hboot but it didn't work. Check file attached.
I checked MD5 checksum just to make sure that it did download correctly and it does match with the one on the download page. However, I did notice that when I'm trying to open that zip file on my PC I'm getting an error saying that the archive is corrupted.
Click to expand...
Click to collapse
It probably didn't work because you are S-On. The method I gave you is generally used by S-Off users to flash firmware, but since it was a signed zip, I thought it might work.
Rename the download I gave you to ROM.zip at put it into your fastboot/platform-tools folder on your PC. Then hook your phone up to your PC and fastbooot.
fastboot devices to make sure your phone and PC are properly connected. (letters and numbers/ser. #)
fastboot oem rebootRUU
fastboot flash zip ROM.zip
EDIT: If you respond here, please use the reply button, I will get a notification that way. I just stumbled back to this thread by chance.
xunholyx said:
It probably didn't work because you are S-On. The method I gave you is generally used by S-Off users to flash firmware, but since it was a signed zip, I thought it might work.
Rename the download I gave you to ROM.zip at put it into your fastboot/platform-tools folder on your PC. Then hook your phone up to your PC and fastbooot.
fastboot devices to make sure your phone and PC are properly connected. (letters and numbers/ser. #)
fastboot oem rebootRUU
fastboot flash zip ROM.zip
EDIT: If you respond here, please use the reply button, I will get a notification that way. I just stumbled back to this thread by chance.
Click to expand...
Click to collapse
Sorry, doesn't work either. I'm getting this error on 3rd command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip ROM.zip
target reported max download size of 1830711296 bytes
error: cannot load 'ROM.zip'
Click to expand...
Click to collapse
ProTofik said:
Sorry, doesn't work either. I'm getting this error on 3rd command:
Click to expand...
Click to collapse
Okay. There must be something I am not aware of.
In fastboot: fastboot getvar all and post the readout here. But delete the serial number and IMEI for your own safety. Never post those on a public forum.
xunholyx said:
Okay. There must be something I am not aware of.
In fastboot: fastboot getvar all and post the readout here. But delete the serial number and IMEI for your own safety. Never post those on a public forum.
Click to expand...
Click to collapse
There you go:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: TOP SECRET
(bootloader) imei: TOP SECRET
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
Click to expand...
Click to collapse
ProTofik said:
There you go:
Click to expand...
Click to collapse
It should work. Try this download instead. https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view
It's pretty much the same one. Maybe the other one is screwed somehow? Try with this one instead and hopefully you can get updated.
xunholyx said:
It should work. Try this download instead. https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view
It's pretty much the same one. Maybe the other one is screwed somehow? Try with this one instead and hopefully you can get updated.
Click to expand...
Click to collapse
Didn't work but I got a different error this time
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip ROM
.zip
target reported max download size of 1830711296 bytes
sending 'zip' (1536838 KB)...
OKAY [ 43.198s]
writing 'zip'...
(bootloader) zip header checking...
FAILED (remote: 32 header error)
finished. total time: 43.510s
Click to expand...
Click to collapse
Is it not possible to just restore whatever ROM my phone came with and then just do the OTA update?
ProTofik said:
Didn't work but I got a different error this time
Is it not possible to just restore whatever ROM my phone came with and then just do the OTA update?
Click to expand...
Click to collapse
LOL!
Yes. I got caught up in this method. You will also need the stock recovery (more important than the ROM) to use the OTAs. Plus your system partition has to be unmodified. That means no Xposed modules. If you have them, delete them using Xposed framework, then uninstall that as well.
xunholyx said:
LOL!
Yes. I got caught up in this method. You will also need the stock recovery (more important than the ROM) to use the OTAs. Plus your system partition has to be unmodified. That means no Xposed modules. If you have them, delete them using Xposed framework, then uninstall that as well.
Click to expand...
Click to collapse
So if I get this right, I just need to restore my factory ROM and Recovery image, then update it through OTA to lollipop. After that I will be able to flash my custom recovery and ROMs once again, right?
Do you have any links to the ROM and Recovery to my phone?
ProTofik said:
So if I get this right, I just need to restore my factory ROM and Recovery image, then update it through OTA to kitkat. After that I will be able to flash my custom recovery and ROMs once again, right?
Do you have any links to the ROM and Recovery to my phone?
Click to expand...
Click to collapse
Yes. Sorry for the confusion I have caused.
xunholyx said:
LOL!
Yes. I got caught up in this method. You will also need the stock recovery (more important than the ROM) to use the OTAs. Plus your system partition has to be unmodified. That means no Xposed modules. If you have them, delete them using Xposed framework, then uninstall that as well.
Click to expand...
Click to collapse
Success. For future generations, here is what I did:
Using fastboot getvar all command I found out that my phone was still mentally stuck on stock rom 1.54.401.5. Using this info, I downloaded matching nandroid backup of that ROM from here and restored it using my custom recovery.
Then, downloading from the same thread, I flashed back stock recovery image using HTC One 2014 (M8) All-In-One Toolkit V2.0.
I was back on my original ROM with original recovery, so I started doing OTA updates until I got to the official android 5.0.1. These updates updated my bootloader to version 3.19.
Having the bootloader that I needed, I flashed custom recovery and installed CM12 without any problem.
Thanks for help!
Hey, I just found this as I am having the same problem. I am trying to follow your solution, but hit a road block and was wondering if you could help. I ran the command "fastboot getvar all" in fastboot and got output similar to yours. Following your advice I looked at the line (bootloader) version-main: 1.55.605.2 which is different than yours, but okay I just need to find a matching one. But when I go to the link that you had provided I can't find a backup that matches mine (or at least I think I can't). What does it mean for it to match anyway? I'm getting so close! I want cm12!!
I did it over like 6 months ago. I can't remember any more. Sorry.
Anyway, CM12 has way too many problem on HTC ONE M8 to be used as a daily driver. I am using GPE Rom now, which I can recommend.
I just need to find some way to update my bootloader so I can get lollipop up and running. Thanks tho
noo_too_droid said:
Following your advice I looked at the line (bootloader) version-main: 1.55.605.2 which is different than yours, but okay I just need to find a matching one. But when I go to the link that you had provided I can't find a backup that matches mine (or at least I think I can't). What does it mean for it to match anyway?
Click to expand...
Click to collapse
The number needs to match exactly to restore to stock and OTA update the software/firmware (and therefore update hboot).
You can try to post on the following thread, and ask if someone can post the stock nandroid for 1.55.605.2 :http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Otherwise (if you can't get a stock nandroid) you may need to resort to getting s-off in order to update hboot (actually I recommend updating all firmware, not just hboot).
ProTofik said:
Success. For future generations, here is what I did:
Using fastboot getvar all command I found out that my phone was still mentally stuck on stock rom 1.54.401.5.
Click to expand...
Click to collapse
Hi there! I have a problem with my One M8 (S-OFF) - I cant flash any ROM on it. I can restore backups from a CM11 4.4.4 and an ARHD 41.0 but can't upgrade from either. I was looking at your solution and noticed that my ROM number is blank when I run fastboot getvar all. Is this a matter of concern? How can I flash a ROM again?
raghuchary said:
Hi there! I have a problem with my One M8 (S-OFF) - I cant flash any ROM on it. I can restore backups from a CM11 4.4.4 and an ARHD 41.0 but can't upgrade from either. I was looking at your solution and noticed that my ROM number is blank when I run fastboot getvar all. Is this a matter of concern? How can I flash a ROM again?
Click to expand...
Click to collapse
Your version-main is blank because of a bug in some older TWRPs. Update to 2.8.7.0. Flashing the new recovery won't fix version-main being blank until you flash new firmware though.
Also, you probably do have to update your firmware. You say you can't flash any ROMs, but you give no details.
xunholyx said:
Your version-main is blank because of a bug in some older TWRPs. Update to 2.8.7.0. Flashing the new recovery won't fix version-main being blank until you flash new firmware though.
Also, you probably do have to update your firmware. You say you can't flash any ROMs, but you give no details.
Click to expand...
Click to collapse
Apologies, newbie here. I was looking for the correct place to place my request for help, when I found this thread and asked. I will put it up in the Q&A section.

(solved)Help with update To android M

Today I received the android m update I download it and install stock recovery so I can install the update But every Time I do it gets to the half of the bar and then says install aborted I have tried factory reset and wipe cache nothing worked
I had twrp recovery before And every time I get any update I replace the twrp with stock recovery and it always worked for me until today
Any solution please?????
What did you use TWRP for, or better asked what did you change on your system? Has your system been rooted or the system.img been manipulated in any kind?
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
HTCNerdYoda said:
What did you use TWRP for, or better asked what did you change on your system? Has your system been rooted or the system.img been manipulated in any kind?
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
Click to expand...
Click to collapse
I used TWRP for root access and yes my system Is rooted but and boot loader unlocked for reinstalling stock recovery was working before and the updates were installed successfully
OTA failure
My device is not rooted and today I tried to upgrade to marshmallow (ota) but it failed to do so after 80% it aborted the installation and now I'm stuck with a dump phone please help I'm not familiar with this kind of situation. I tried to wipe cache partition and wipe data/factory reset but nothing works. IT says on the screen:
Android Recovery
HTC/htc_m8/htc_m8
6.0/MRA58K/buildteam12171409
user/release-keys
Use volume up/down and power.
-----------------------------------------
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Power off
-----------------------------------------
Supported API: 3
handle_cota_install: install cwpkg to/c
ache/data/cwtemp/cwpkg.zip
handle_cota_install: install cwprop to /
cache/data/cwtemp/cw.prop
Write host_mode success
handle_cota_install: No CW files. Skip c
w installation.
ecmelg said:
My device is not rooted and today I tried to upgrade to marshmallow (ota) but it failed to do so after 80% it aborted the installation and now I'm stuck with a dump phone please help I'm not familiar with this kind of situation. I tried to wipe cache partition and wipe data/factory reset but nothing works. IT says on the screen:
Android Recovery
HTC/htc_m8/htc_m8
6.0/MRA58K/buildteam12171409
user/release-keys
Use volume up/down and power.
-----------------------------------------
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Power off
-----------------------------------------
Supported API: 3
handle_cota_install: install cwpkg to/c
ache/data/cwtemp/cwpkg.zip
handle_cota_install: install cwprop to /
cache/data/cwtemp/cw.prop
Write host_mode success
handle_cota_install: No CW files. Skip c
w installation.
Click to expand...
Click to collapse
Try flashing RUU for ur model id.
Alxens said:
I used TWRP for root access and yes my system Is rooted but and boot loader unlocked for reinstalling stock recovery was working before and the updates were installed successfully
Click to expand...
Click to collapse
If it is rooted the OTA won't be installed as the system partition and thus it's md5 has been changed by mounting it r/w and flashing SuperSU. This is as google and HTC following this guidelines changed the OTA delivery to a block based system where the routine checks if the system has been untouched prior to installing it. You got to restore the untouched image of the system partition for your device. After this you could flash the stock recovery and install the OTA.
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
HTCNerdYoda said:
If it is rooted the OTA won't be installed as the system partition and thus it's md5 has been changed by mounting it r/w and flashing SuperSU. This is as google and HTC following this guidelines changed the OTA delivery to a block based system where the routine checks if the system has been untouched prior to installing it. You got to restore the untouched image of the system partition for your device. After this you could flash the stock recovery and install the OTA.
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
Click to expand...
Click to collapse
I have twrp backup system
would this work??
Alxens said:
Today I received the android m update I download it and install stock recovery so I can install the update But every Time I do it gets to the half of the bar and then says install aborted I have tried factory reset and wipe cache nothing worked
I had twrp recovery before And every time I get any update I replace the twrp with stock recovery and it always worked for me until today
Any solution please?????
Click to expand...
Click to collapse
Esta solución me sirvió a mi. www . htc.com/us/support/rom- downloads . html (saca los espacios) en tú caso descarga la versión desbloqueada
Yes would work
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
I'm having the same problem. I don't have a ROOT and already talked to the HTC help desk and didn't find any solution. With this TWRP can I fix this problem?
sonoman87 said:
I'm having the same problem. I don't have a ROOT and already talked to the HTC help desk and didn't find any solution. With this TWRP can I fix this problem?
Click to expand...
Click to collapse
Most likely NO.
The above user(s) used TWRP backups to remove changes that were done by root.
Since you never rooted (from the sounds of it) you don't have the same problem.
redpoint73 said:
Most likely NO.
The above user(s) used TWRP backups to remove changes that were done by root.
Since you never rooted (from the sounds of it) you don't have the same problem.
Click to expand...
Click to collapse
Thanks redpoint73. So, what do you recommend me to do now? Because, the problem started with the android notification of the update and then the system crashed. Search for a ROM and try to install it?
Thanks again!
sonoman87 said:
Thanks redpoint73. So, what do you recommend me to do now? Because, the problem started with the android notification of the update and then the system crashed. Search for a ROM and try to install it?
Click to expand...
Click to collapse
If there is a MM RUU for your version, download and run it.
redpoint73 said:
If there is a MM RUU for your version, download and run it.
Click to expand...
Click to collapse
I've fixed it! Thanks so much again!
sonoman87 said:
I've fixed it! Thanks so much again!
Click to expand...
Click to collapse
Which country are you from? And which ROM did you use? I'm from Spain and I'm afraid if I install the ROM it wouldn't work again in my country
oscar1355 said:
Which country are you from? And which ROM did you use? I'm from Spain and I'm afraid if I install the ROM it wouldn't work again in my country
Click to expand...
Click to collapse
First of all, you need to understand that ROM and RUU are two very different things.
Also, nobody can advise you the proper RUU is, without knowing some basic information. Namely, do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
Hey everyone,
I am trying to get my M8 to stock (been stuck at this for about 10 days now, tried everything). I am from India. There was some problem and I accidentally have a phone now with no OS and TWRP. I have installed stock recovery and plan to flash the ROM/RUU. Some details of my device:
Software status: Modified
Unlocked S-ON
C:\Android>fastboot getvar all
(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-ON
(bootloader) serialno: <serial number>
(bootloader) imei: <imei number>
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I would really appreciate it if you could guide me how to get my phone to stock OS. The ROM that I should prefer etc. I have been going through a lot of forums and ended up being utterly confused.
Thanks in advance for the help!
skull_143 said:
been stuck at this for about 10 days now, tried everything
There was some problem and I accidentally have a phone now with no OS and TWRP.
Click to expand...
Click to collapse
Sorry, this is a pet peeve of mine, but I really wish folks would stop posting they "tried everything". This literally tells us nothing, and you should list specifically one-by-one (and in detail) what things you tried, and the results (again in detail) of each.
"Accidentally" appears to mean you unlocked the bootloader, then flashed an very old, obsolete version TWRP (which causes the main version to be blank) then decided it was a good idea to wipe the OS (system)? Again, you need to tell us exactly what steps you took to get to this point.
My next advice to you, is to only do things that are specifically instructed for you to do in your situation. Don't guess or do things without fully understanding them. As your present situation seems to indicate you don't have a very good understanding of what you are doing, and only making matter worse by proceeding with insufficient knowledge.
skull_143 said:
I have installed stock recovery and plan to flash the ROM/RUU. Some details of my device
Click to expand...
Click to collapse
RUU will only work if its version 6.15.720.2
Your version (CID and MID) is rather obscure, so I'm not sure whether such RUU exists or not. If not, your best bet is to get TWRP back on the phone, and restore the stock nandroid 6.15.720.2 using the files and instructions on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Also, flashing stock recovery is not needed to RUU; and not helpful in your current situation (you'll probably need to go back to custom recovery TWRP).
redpoint73 said:
Sorry, this is a pet peeve of mine, but I really wish folks would stop posting they "tried everything". This literally tells us nothing, and you should list specifically one-by-one (and in detail) what things you tried, and the results (again in detail) of each.
"Accidentally" appears to mean you unlocked the bootloader, then flashed an very old, obsolete version TWRP (which causes the main version to be blank) then decided it was a good idea to wipe the OS (system)? Again, you need to tell us exactly what steps you took to get to this point.
My next advice to you, is to only do things that are specifically instructed for you to do in your situation. Don't guess or do things without fully understanding them. As your present situation seems to indicate you don't have a very good understanding of what you are doing, and only making matter worse by proceeding with insufficient knowledge.
RUU will only work if its version 6.15.720.2
Your version (CID and MID) is rather obscure, so I'm not sure whether such RUU exists or not. If not, your best bet is to get TWRP back on the phone, and restore the stock nandroid 6.15.720.2 using the files and instructions on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Also, flashing stock recovery is not needed to RUU; and not helpful in your current situation (you'll probably need to go back to custom recovery TWRP).
Click to expand...
Click to collapse
Sorry about the shortened version, just though it might be too big and unnecessary. Okay here goes what happened. I moved the whatsapp media to my laptop (at this time the device was unrooted and running stock android M updated over OTA). After the move, the device was stuck at the splash screen with HTC logo. After this I gave the phone to a service centre (not official HTC) and asked them to NOT root and put stock OS and get the phone working. What they did was, rooted it and installed a custom ROM with TWRM recovery (which was very screwed up, as in the camera kept crashing and I couldn't even use that). So, I decided to get it back to stock ROM and sense UI.
So what I did was looked up some thread (not sure which one) and went ahead to do a wipe through recovery. Here I did the mistake of wiping everything and so the device doesn't have any OS at the moment. The phone is still getting stuck in HTC logo now (obviously as it doesn't have an OS). I have tried to do the following:
1. To flash the boot only using fastboot flash boot and fastboot flash zip commands. The version I tried was stock 3.35.720.1_recovery.img. This didnt seem to work.
2. Next tried to go to usb fastboot mode and tried to run the RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe official one from the laptop. But it showed some mismatch of versions and aborted.
3. Then I read that stock could only be flashed on S-ON devices if we relock the bootloader. So used the fastboot oem relock command to relock bootloader and then tried both the above but didn't work.
4. Next saw somewhere that it is pretty impossible to flash on a locked S-ON device. So went to htcdev and got the bootloader unlocked again.
5. Downloaded a stock image 3.35.720.1 Stock Unrooted. Read that we need lower or same stock recovery to flash the same and so flashed the stock recovery of the same version. Next extracted the .win001 and .win002 files using the tar command and finally put them along with META_INF folder and boot.img files into a zip file. The image had the contents of the system folder and tried to flash this using fastboot and also through the stock option "Update from SD card". Got error "E: footer is wrong. E: update signature verification failed".
This is the status so far. I am not sure what I should be doing anymore. Hope this helps in understanding the situation. Sorry it's so long.
Please advice what I should do now. Currently, I have stock recovery installed and no OS. I just want to have the stock sense OS on the device.
Thanks for all your time.
skull_143 said:
Please advice what I should do now. Currently, I have stock recovery installed and no OS. I just want to have the stock sense OS on the device.
Thanks for all your time.
Click to expand...
Click to collapse
1. Download the 6.15.720.2 RUU.zip : http://forum.xda-developers.com/showpost.php?p=66309774&postcount=20
2. relock the bootloader with command - fastboot oem lock
option 1 - if you have a microsd
1. rename the downloaded RUU.zip as to 0P6BIMG.zip
2. put it on root of your microsd not in any folder
3. on bootloader select hboot - it will scan the zip and ask you to update.
4. select volume up to update
5. once completed, delete the zip from microsd
option 2
1. Download htc_fastboot.exe : https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view
2. put both htc_fastboot.exe and the 0P6BIMG.zip in your fastboot folder
3. run below commands :
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 0P6BIMG.zip (to install RUU - read it is htc_fastboot not fastboot)
Once complete - fastboot reboot
run setup .. done

Categories

Resources