Related
HI guys, i kinda messed up my hox....
So I rooted it 3 days ago (SuperSu & TWRP), and today I tried to flash mods to it.
First i tried the Project X Revolution v3.6, followed the instruction step by step, but after rebooting it would just hang on the boot animation. So I tried again, wiped everything (cache, dalvik, system), and installed it agian, still the same problem.
So I tried a different rom. so I wiped everything, and installed MagioROMx R3.1, but still the same problem. So i gave up and tried to restore to my stock rom, which i made a backup of using TWRP (and also in titanium backup). But i still got hangs on booting. So i started searching the forums untill I found: http://forum.xda-developers.com/wik...very_-_what_to_do_in_the_event_of_a_bad_flash
And started following the last resort part (with the RUU), but i can't seem to find the ruu I need (1.26.707.4), I only found a fitting OTA I have no clue what to do with.
So now, my hox is only booting to bootloader (so no charging and battery is <30%), bootloader is relocked, and I can't access TWRP (an HTC booting screen comes up, with something written in red, and then the bootloader comes back).
Some data I have:
(bootloader) version: 0.5a
(bootloader) version-bootloader: 0.43.0000
(bootloader) version-baseband: None
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.707.4
(bootloader) serialno: --------------------------
(bootloader) imei: -----------------------
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: None
(bootloader) battery-status: low
(bootloader) battery-voltage: 3567mV
(bootloader) devpower: 5
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
So I am pretty lost, and could really use some help...
Did you flashed correctly boot. Img?
Sent from my HTC One X using xda premium
matitorres07 said:
Did you flashed correctly boot. Img?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Project X Revolution v3.6 came with a bat file who I assume flashed it:
Code:
fastboot flash boot boot.img
But I am not sure flashed the second time i tried it.
But the second mod I flashed both times.
P.S: a red LED while in bootloader means the phone is being charged?
You are not flashing correctly the boot. Img you need everytime With almost every rom flash it, if you cant or dont know how to do it use a toolkit!
Sent from my HTC One X using xda premium
matitorres07 said:
You are not flashing correctly the boot. Img you need everytime With almost every rom flash it, if you cant or dont know how to do it use a toolkit!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I have the "WinDroid HTC One X Toolkit", but i haven't used it to flash roms, because i couldn't figure out where the boot.img comes in place there.
(You have flash rom, and flash kernel, but flash rom is the first step, and I thought you should first flash the img and then the rom.)
So in theory, assuming i can charge the phone, re-unlock the bootloader and flash a rom correctly I should get the phone working again?
The phone doen't charge in bootloader,
If u r at bootloader enter fastboot.
-Check if htc fastboot drivers are correctly installed (ur phone should show "fastboot usb").
-install fastboot, adb drivers.
-extract boot.img from the custom rom u r trying to flash, and place it in fastboot folder.
-open cmd and navigate into fastboot folder through cd
eg:" cd c:\fastboot\
- type: fastboot flash boot boot.img
-type: fastboot erase cache
-type: fastboot reboot
Sent from my HTC One X using XDA Premium 4 mobile app
convict_moody said:
The phone doen't charge in bootloader,
If u r at bootloader enter fastboot.
-Check if htc fastboot drivers are correctly installed (ur phone should show "fastboot usb").
-install fastboot, adb drivers.
-extract boot.img from the custom rom u r trying to flash, and place it in fastboot folder.
-open cmd and navigate into fastboot folder through cd
eg:" cd c:\fastboot\
- type: fastboot flash boot boot.img
-type: fastboot erase cache
-type: fastboot reboot
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I managed to re-unlock the bootloader, but i cant flash the boot, i get:
Code:
sending 'boot' (4862 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
I got that while in the bootloader menu, in recovery and boot animation fastboot can find the device. So I don't know what to do :S
(will trying to push the file using adb, and flashing it though TWRP work?)
No, if you are failing using the console use a toolkit, enter to general there is a faq to root flash and unlock boot leader, download toolkit from there, put the toolkit and the boot Img in the same folder and follow the faq you are not flashing the boot Img correctly.
Sent from my HTC One X using xda premium
matitorres07 said:
No, if you are failing using the console use a toolkit, enter to general there is a faq to root flash and unlock boot leader, download toolkit from there, put the toolkit and the boot Img in the same folder and follow the faq you are not flashing the boot Img correctly.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yeah following the faq is the best idea, but there is something not done correctly in the phone, and not the console. Screenshots would help us find the problem... but follow the faq point by point will help u a lot.
Sent from my HTC One X using XDA Premium 4 mobile app
Are you guys sleeping or what, his hboot is WAY to low to flash any rom from here !!!!
Download the android SDK bundle (google it) unpack the package and go to the PLATFORM TOOLS folder. you see a file called fastboot.exe......now point in that folder with your mouse and hold SHIFT and press the right mouse button. Select open command window here and perform the fastboot commands from that window !
How to charge ?
Put the phone in the bootloader and run this script WITH admin rights from the fastboot (copy this file into the same folder as were fastboot.exe is) folder on the pc :
You execute the file while right clicking it and select "run as administrator" if it starts it will keep on rebooting the phone and charging it bit by bit.
https://www.dropbox.com/s/aaah8gqz8j024xz/Batt script.bat
when your phone is charged to let's say 3800mV stop it and relock the bootloader. then install this ruu
http://androidruu.com/getdownload.p...Radio_1.1204.105.14_release_260743_signed.exe
Keep the phone in the bootloader/fastboot usb mode and select also the ruu with your right mouse button. Select again "run as administrator"
after it ran succesful you reboot the phone into the os and continue to update via official OTA
Mr Hofs said:
Are you guys sleeping or what, his hboot is WAY to low to flash any rom from here !!!!
Download the android SDK bundle (google it) unpack the package and go to the PLATFORM TOOLS folder. you see a file called fastboot.exe......now point in that folder with your mouse and hold SHIFT and press the right mouse button. Select open command window here and perform the fastboot commands from that window !
How to charge ?
Put the phone in the bootloader and run this script WITH admin rights from the fastboot (copy this file into the same folder as were fastboot.exe is) folder on the pc :
You execute the file while right clicking it and select "run as administrator" if it starts it will keep on rebooting the phone and charging it bit by bit.
https://www.dropbox.com/s/aaah8gqz8j024xz/Batt script.bat
when your phone is charged to let's say 3800mV stop it and relock the bootloader. then install this ruu
http://androidruu.com/getdownload.p...Radio_1.1204.105.14_release_260743_signed.exe
Keep the phone in the bootloader/fastboot usb mode and select also the ruu with your right mouse button. Select again "run as administrator"
after it ran succesful you reboot the phone into the os and continue to update via official OTA
Click to expand...
Click to collapse
Yeah am a lil bit sleepy, and the arrival of Alexa's storm have freezed my brain.... u are the best in this domain. :highfive:
Nah not the best.....just more awake
Mr Hofs said:
Nah not the best.....just more awake
Click to expand...
Click to collapse
HAHA im new over here and in all this stuff,im just worried about learn more,and if i can ,help.
matitorres07 said:
HAHA im new over here and in all this stuff,im just worried about learn more,and if i can ,help.
Click to expand...
Click to collapse
Yeah it seems u r facing some problems too while flashing a custom....
Sent from my HTC One X using XDA Premium 4 mobile app
Mr Hofs said:
Are you guys sleeping or what, his hboot is WAY to low to flash any rom from here !!!!
Download the android SDK bundle (google it) unpack the package and go to the PLATFORM TOOLS folder. you see a file called fastboot.exe......now point in that folder with your mouse and hold SHIFT and press the right mouse button. Select open command window here and perform the fastboot commands from that window !
How to charge ?
Put the phone in the bootloader and run this script WITH admin rights from the fastboot (copy this file into the same folder as were fastboot.exe is) folder on the pc :
You execute the file while right clicking it and select "run as administrator" if it starts it will keep on rebooting the phone and charging it bit by bit.
when your phone is charged to let's say 3800mV stop it and relock the bootloader. then install this ruu
Keep the phone in the bootloader/fastboot usb mode and select also the ruu with your right mouse button. Select again "run as administrator"
after it ran succesful you reboot the phone into the os and continue to update via official OTA
Click to expand...
Click to collapse
I managed to re-unlock the phone and charge while in recovery, so the battery issue is solved.
I downloaded the sdk and the ruu, but when i run it (with admin priv) I get:
Error -5001 on InstallShield.
Details:
Code:
Error Code: -5001 : 0x80070002
Error Information:
>SetupNew\setup.cpp (142)
PAPP:
PVENDOR:
PGUID:
$
@Windows 7 / Server 2008 R2 Service Pack 0 (7600)
IE Version: 9.0.8112.16421
Could it be drivers related?
And also I get on the bootloader screen a "Security Warning" (only when bootloader is relocked).
The security warming is not the issue, are you logged in at the pc as admin ?
Mr Hofs said:
The security warming is not the issue, are you logged in at the pc as admin ?
Click to expand...
Click to collapse
Yes.
Try another ruu the 1.28.707 is also available.
Androidruu.com
Or try it on another pc. Also helps often
denounced
Mr Hofs said:
Try another ruu the 1.28.707 is also available.
Androidruu.com
Or try it on another pc. Also helps often
Click to expand...
Click to collapse
3 Different PCs, both RUU, same problem every time
Any use of trying on a Fedora? (will the .exe even run?)
It's not the ruu, it's some rights on the pc......
Sorry about any terminology...
Recently my htc one m8 stopped booting. I had rooted it a long time ago and had a ROM that was working fine for a long time. No recent changes.
On normal boot it sits on the white and green text 'htc' forever.
If I boot with power+down buttons I get to a hboot screen, but choosing 'recovery' takes me to a white screen small pink 'Entering Recovery' text. Nothing happens. To even get power+down screen to be available I had to move two zip files from root of sdcard which I guess were related to the custom rom, being 0P6BIMG.zip and M8-GPE-03-16-2015.zip
I tried reinstalling twrp after downloading the latest .img file
fastboot command
c:\twrp>fastboot flash recovery twrp-3.0.2-0-m8.img
just says <waiting for device> whether on pink text screen or white 'htc'
I can see the sdcard through a pc card reader and manipulate files. Is there any way to copy files manually so it will boot?
This is on Win 10, UK unlocked version of phone.
bt999 said:
To even get power+down screen to be available I had to move two zip files from root of sdcard which I guess were related to the custom rom, being 0P6BIMG.zip and M8-GPE-03-16-2015.zip
Click to expand...
Click to collapse
When you have a file named 0P6BIMG.zip, it will automatically try to install it every time you enter bootloader. Its an update or RUU of some sort, placed there by you, but exactly what is impossible to tell.
The other file is a ROM zip for a GPE ROM, which I would guess is the custom ROM you installed. It doesn't make a difference for this file not be on the SD card or not (bootloader will not try to install it automatically, and bootloader will function normally).
bt999 said:
I tried reinstalling twrp after downloading the latest .img file
fastboot command
c:\twrp>fastboot flash recovery twrp-3.0.2-0-m8.img
just says <waiting for device> whether on pink text screen or white 'htc'
Click to expand...
Click to collapse
Are you in bootloader-fastboot mode when you run the command (which is required)? Meaning, FASTBOOT should be highlighted in red just under the green text on the bootloader screen. If not, just select using the vol buttons, and confirm using power button.
Fastboot clarification
redpoint73 said:
When you have a file named 0P6BIMG.zip, it will automatically try to install it every time you enter bootloader. Its an update or RUU of some sort, placed there by you, but exactly what is impossible to tell.
The other file is a ROM zip for a GPE ROM, which I would guess is the custom ROM you installed. It doesn't make a difference for this file not be on the SD card or not (bootloader will not try to install it automatically, and bootloader will function normally).
Are you in bootloader-fastboot mode when you run the command (which is required)? Meaning, FASTBOOT should be highlighted in red just under the green text on the bootloader screen. If not, just select using the vol buttons, and confirm using power button.
Click to expand...
Click to collapse
Thanks for your reply.
I guess the 0P6BIMG.zip file would explain why it was always slow to boot when things were working ok, if it was being reinstalled each time. I don't recall its purpose.
I wasn't in bootloader-fastboot mode when trying the fastboot command, but have tried it again.
When connected to an Ubuntu 16.04 machine the white on red text says 'fastboot usb', but ubuntu commandline fastboot flash ... gives same 'waiting for device'. When connected to Win 10 white/red text just says 'fastboot', if that is relevant. When I installed fastboot on Win 10 from instructions at http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 there is a note to remove Google drivers before installing new ones - I did not do this, not sure if relevant, but new driver install gave no errors.
Is there a way to copy a new ROM image to the sdcard so that on 'normal' booting it gets detected and applied? Or to copy twrp somewhere manually?
Is there a log file that would show how far through the normal boot things get? I guess it is inaccessible until things work better.
bt999 said:
I wasn't in bootloader-fastboot mode when trying the fastboot command, but have tried it again.
When connected to an Ubuntu 16.04 machine the white on red text says 'fastboot usb', but ubuntu commandline fastboot flash ... gives same 'waiting for device'. When connected to Win 10 white/red text just says 'fastboot', if that is relevant. When I installed fastboot on Win 10 from instructions at http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 there is a note to remove Google drivers before installing new ones - I did not do this, not sure if relevant, but new driver install gave no errors.
Click to expand...
Click to collapse
Try going into Windows Device Manager, finding the device, and picking the option to manually select drivers, and select the generic Android MTP drivers. See if that helps fastboot connect.
Make sure you have HTC drivers (HTC Sync) installed as well. Try to re-install HTC Sync.
bt999 said:
Is there a way to copy a new ROM image to the sdcard so that on 'normal' booting it gets detected and applied? Or to copy twrp somewhere manually?
Click to expand...
Click to collapse
You can't flash a ROM, if TWRP isn't working properly. And there isn't a way to make one automatically flash upon normal boot, that I am aware.
I've seen some folks make 0P6BIMG.zip files for TWRP, which will install automatically when you boot to bootloader. But honestly, USB fastboot connectivity is a pretty vital thing to have working, and usually just a matter of right drivers and a good cable (and being in fastboot mode is a must), so shouldn't be that hard to troubleshoot.
Old twrp
redpoint73 said:
Try going into Windows Device Manager, finding the device, and picking the option to manually select drivers, and select the generic Android MTP drivers. See if that helps fastboot connect.
Make sure you have HTC drivers (HTC Sync) installed as well. Try to re-install HTC Sync.
You can't flash a ROM, if TWRP isn't working properly. And there isn't a way to make one automatically flash upon normal boot, that I am aware.
I've seen some folks make 0P6BIMG.zip files for TWRP, which will install automatically when you boot to bootloader. But honestly, USB fastboot connectivity is a pretty vital thing to have working, and usually just a matter of right drivers and a good cable (and being in fastboot mode is a must), so shouldn't be that hard to troubleshoot.
Click to expand...
Click to collapse
I have got a twrp running, unfortunately it says it is only compatible with bootloader 3.19 and above when I try to install the rom. I have 3.16.
Do you know where I can get an old twrp?
Thanks.
bt999 said:
I have got a twrp running, unfortunately it says it is only compatible with bootloader 3.19 and above when I try to install the rom. I have 3.16.
Do you know where I can get an old twrp?
Thanks.
Click to expand...
Click to collapse
https://dl.twrp.me/m8/
twrp versions
xunholyx said:
https://dl.twrp.me/m8/
Click to expand...
Click to collapse
Thanks. I have now tried
twrp-2.7.0.1-m8.img twrp-2.7.1.0-m8.img twrp-2.8.7.0-m8.img
twrp-2.7.0.2-m8.img twrp-2.8.0.0-m8.img twrp-3.0.2-0-m8.img
The oldest ones don't run the newer ones work but I still get an error on attempting to install the custom ROM. I think I may be misinterpreting the error message. I now think it is telling me the custom ROM needs bootloader 3.19, rather than twrp not being able to run, i.e. twrp knows not to install the rom.
Message 'This package supports bootloader(s): 3.19.0.0000; this device has bootloader 3.16.0.0000'
Do you know how I can update my bootloader?
bt999 said:
Do you know how I can update my bootloader?
Click to expand...
Click to collapse
Post fastboot getvar all result without serial & imei no.
Without proper info, everyone is guessing what you actually need.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(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: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I found this thread http://forum.xda-developers.com/showthread.php?t=2696282 and went through the process with a zip linked from there , but I guess it was old and turned out to still be 3.16
Shouldn't HTC be distributing these files? Or my carrier?
You need to relock bootloader if not yet done.
Command :
fasboot oem lock
fastboot reboot-bootloader
Then follow this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Put both files in your adb/fastboot folder.
(The guide was written for system-wide adb/fastboot)
Once completed, you can re unlock boorloader and install latest TWRP and install any ROM that you like, if you want to.
I have a working phone now, htc setup screens ended up with no google account prompts or apps, so I installed cwm nightlies and open-gapps hoping I would have full functionality, however gapps was rejected for not having enough internal storage.
I don't care whether htc or cwm but need gapps/play store. Is there anything you can suggest?
/Last reply lost..]I now have a working phone with cwm nightlies. Unfortunately open-gapps wont install saying not enough space on internal drive.
Any suggestions on how to clear space or to make HTC install Google accounts/store (it did not ask)?
I have a working phone now.
RUU didn't install google app store, so I installed cwm nightlies. I got an error that there was not enough space on internal for open-gappps.
Is there a way to free up space?
bt999 said:
I have a working phone now.
RUU didn't install google app store, so I installed cwm nightlies. I got an error that there was not enough space on internal for open-gappps.
Is there a way to free up space?
Click to expand...
Click to collapse
I have no idea what cwm nightlies is ... but if you have this kind of error not enough internal space ... you need to format data (not wipe) in TWRP.
Install latest TWRP, select wipe - format data - yes ... reboot to recovery again, now you can install ROM.
Solved
ckpv5 said:
I have no idea what cwm nightlies is ... but if you have this kind of error not enough internal space ... you need to format data (not wipe) in TWRP.
Install latest TWRP, select wipe - format data - yes ... reboot to recovery again, now you can install ROM.
Click to expand...
Click to collapse
I installed a mini gapps that had just Play Store then installed other apps manually through that.
Thank you all for your help, this is a well-informed forum.
For anyone reading one thing I learned was to run fastboot from Ubuntu/Linux with 'sudo' or else it will not connect, just says 'waiting for device'
ckpv5 said:
I have no idea what cwm nightlies is
Click to expand...
Click to collapse
He means CM, not CWM. Easy mistake to make (adding one letter) but the two are completely different things (Cyanogen Mod custom ROM versus Clockwork Mod custom recovery).
Hie everyone i am new here and i have an htc one m8 which is bootloader locked , s on and i dont have root access nor custom recovery installed .
All other tutorials i found here are more so related to those htc m8 devices with either bootloader unlocked or custom recovery installed and since the device is stuck on decrypt storage page i cant install an RUU firmware exe i downloaded and also i cant install a custom firmware too .
i found a tutorial on how to unlock bootloader and did got my token id from fastboot since it is the only thing working so far and am stuck with the stock recovery so i cannot get into adb mode.
when flashing the unlock code bin file in fastboot it says successfully and the warning page also appears which prompts me to choose to unlock bootloader or not . and after selecting unlock bootloader the device restarts into recovery mode i which i thought i have to factory reset for the bootloader process to be complete but still after factory reset the device boots straight to the decrypt storage page and when i reboot again into fastboot mode the bootloader is still locked like nothing happened . tried all methods to unlock bootloader and not factory reset in hope of getting better results but still its the same problem . so if there is another solution that might help me to unlock my bootloader or flash custom recovery or force it to install my RUU exe firmware without debugging i would greatly appreciate it
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Sxxxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__016
(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: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
thats from getvar
and i also downloaded this firmware i dont know if it is the correct one for my device since its showing region as south africa (Region : VODA-Africa-South)
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
any help related to my problem is greatly appreciated
Just follow this ,Might help
The correct RUU for your device
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
Just follow this ,Might help
The correct RUU for your device
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
ok let me try it and update you with the results
hie when i type fastboot oem rebootRUU it reboots and boots into the system where it shows decrypt storage again . installed htc sync and uninstalled it leaving the drivers installed i dont know what is happening now , what should it display when it is in RUU MODE?
cliffordmoyo said:
hie when i type fastboot oem rebootRUU it reboots and boots into the system where it shows decrypt storage again . installed htc sync and uninstalled it leaving the drivers installed i dont know what is happening now , what should it display when it is in RUU MODE?
Click to expand...
Click to collapse
i dont know how i did it but for a moment is showed me the allow usb debug screen and i could see the device on adb devices command prompt screen then i tried to install the RUU.exe firmware but it failed and rebooted now its no longer detected on adb :crying:
cliffordmoyo said:
i dont know how i did it but for a moment is showed me the allow usb debug screen and i could see the device on adb devices command prompt screen then i tried to install the RUU.exe firmware but it failed and rebooted now its no longer detected on adb :crying:
Click to expand...
Click to collapse
The RUU.exe from your first post?
That will not work for you. That RUU is for AT&T devices. The only way you would be able to flash that would be if you were S-Off and changed you CID to 11111111 (or AT&T's CID)
Take the RUU.zip (6.12.401.4 ~ the 401 being the important part, that is the identifier for your model) and rename the .zip to 0P6BIMG.zip (that's a zero, not the letter). The best way to do rename would be to place it onto your extSD so you can see the .zip extension (it is sometimes hidden on your PC) and use a file explorer so you don't accidentally rename it to 0P6BIMG.zip.zip
Boot to bootloader after this is renamed and on extSD (formatted to FAT32), and you should be prompted to flash it by pressing vol up. When the flash is finished, you'll be prompted to press power to reboot, and you are done.
Hope this helps
xunholyx said:
The RUU.exe from your first post?
That will not work for you. That RUU is for AT&T devices. The only way you would be able to flash that would be if you were S-Off and changed you CID to 11111111 (or AT&T's CID)
Take the RUU.zip (6.12.401.4 ~ the 401 being the important part, that is the identifier for your model) and rename the .zip to 0P6BIMG.zip (that's a zero, not the letter). The best way to do rename would be to place it onto your extSD so you can see the .zip extension (it is sometimes hidden on your PC) and use a file explorer so you don't accidentally rename it to 0P6BIMG.zip.zip
Boot to bootloader after this is renamed and on extSD (formatted to FAT32), and you should be prompted to flash it by pressing vol up. When the flash is finished, you'll be prompted to press power to reboot, and you are done.
Hope this helps
Click to expand...
Click to collapse
thank you for the reply . so i did download this firmware with the 6 .12.401.4 in its original name hope it is the correct one please confirm
(0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip)
and using extsd card is the best way to flash my device than using fastboot command prompt with RUU zip file stil in pc ? hope i am getting the steps right
cliffordmoyo said:
thank you for the reply . so i did download this firmware with the 6 .12.401.4 in its original name hope it is the correct one please confirm
(0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip)
and using extsd card is the best way to flash my device than using fastboot command prompt with RUU zip file stil in pc ? hope i am getting the steps right
Click to expand...
Click to collapse
Yeah, you can also flash it in fastboot from PC. You'll probably get an "Error 90". That's the hboot pre-update and nothing to worry about. When you get it don't disconnect, just enter the flash command (fastboot flash zip "name of firmware".zip) a second time to reflash it.
xunholyx said:
Yeah, you can also flash it in fastboot from PC. You'll probably get an "Error 90". That's the hboot pre-update and nothing to worry about. When you get it don't disconnect, just enter the flash command (fastboot flash zip "name of firmware".zip) a second time to reflash it.
Click to expand...
Click to collapse
sadly i guess i have got a bigger problem than i thought , so i tried with pc using these commands fastboot oem rebootRUU and the devices reboots straight into normal mode , and i did also the extsd tutorial you gave me and the device checks the file and prompts me if i want to continue bt after pressing the vol up button the device reboots again straight into normal mode where i am having the decrypt storage issue .if only i had that usb debugging screen prompt again i guess i would have had better odds since before it failed it actually went into RUU flash mode showing only the htc logo with black background
thank you for the quick response by the way
cliffordmoyo said:
sadly i guess i have got a bigger problem than i thought , so i tried with pc using these commands fastboot oem rebootRUU and the devices reboots straight into normal mode , and i did also the extsd tutorial you gave me and the device checks the file and prompts me if i want to continue bt after pressing the vol up button the device reboots again straight into normal mode where i am having the decrypt storage issue .if only i had that usb debugging screen prompt again i guess i would have had better odds since before it failed it actually went into RUU flash mode showing only the htc logo with black background
thank you for the quick response by the way
Click to expand...
Click to collapse
You can turn on usb debugging in settings > developer options, but it shouldn't be needed for fastboot commands.
Try flashing this firmware.zip first, then run the RUU.zip again.
xunholyx said:
You can turn on usb debugging in settings > developer options, but it shouldn't be needed for fastboot commands.
Try flashing this firmware.zip first, then run the RUU.zip again.
Click to expand...
Click to collapse
tried that last firmware zip but just want to confirm if i did the correct procedure ......
i downloaded this file you linked me : M8_6.12.401.4_WWE_TWRP2870.zip renamed it to 0P6BIMG.zip , copied it to my sdcard and and rebooted into bootloader . i could see the checking progress bar but then it just doesnt give me the prompt screen for vol up to continue or vol down to cancel , its just saying press power to reboot.
then tried fastboot oem rebootRUU but the fone is just stubborn and reboots into normal mode again not in RUU mode so i cant flash the zip firmware with fastboot . Another thing i noticed is when i finish unlocking bootloader and gets the success message with continue to unlock bootloader screen and then phone reboots into recovery (stock recovery) there is a chain of errors like "cannot mount data , cannot mount emmc" too but when i repeat the bootloader unlock process again this time with an sdcard in device i get "no cw files in sdcard" message when it reboots into recovery but still the bootloader wont be unlocked despite of repeating the process several times. the phone is still brand new never opened and i think this is somehow software related for i was beginning to think that its hardware issue but an app cause this "device decrypt storage" after the phone rebooted
Any idea where i can get htc mtp device drivers as i have reinstalled my operating system and installed htc syn too but those are the only ones failling to install now am on 32bit windows os , the ones i have downloaded are not installing maybe if those install i might recieve an "allow usb debugging " screen as i did earlier on before the screen didnt want to show up again
do you have any idea what might cause device to reboot into os/normal mode when executing the fastboot reboot-bootloader same as fastboot oem rebootRUU the device quickly reboots and enter into normal mode and does not hold those command . also if have downloaded almost 17 unlockcode.bin files from htc dev i kept on requesting after the bootloader wont get unlocked , it shows unlockcode flashed successfully in command prompt but when device reboots the bootloader is still locked . i still love my htc m8 but it seems i am the only one in this enter forum who has this problem since other are successfully getting their devices fixed :crying::crying:
Hey,
my problem is that, after a reboot, my phone went into a bootloop.
I tried to enter the Recovery or the Download mode but it does not working.
After an automatic restart there is the bootloop again.
I can enter the Bootloader.
Official Software status
Unlocked
S-OFF
an interesting thing is that when i try to read my cid or mid with
fastboot getvar cid/mid
there is nothing to read out. It's empty.
Code:
c:\android>fastboot getvar cid
cid:
finished. total time: 0.036s
c:\android>fastboot getvar mid
mid:
finished. total time: 0.003s
domme0852 said:
Hey,
my problem is that, after a reboot, my phone went into a bootloop.
I tried to enter the Recovery or the Download mode but it does not working.
After an automatic restart there is the bootloop again.
I can enter the Bootloader.
Official Software status
Unlocked
S-OFF
an interesting thing is that when i try to read my cid or mid with
fastboot getvar cid/mid
there is nothing to read out. It's empty.
Click to expand...
Click to collapse
What is the output with fastboot getvar all?
Code:
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61b000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:xxxxxxxxxxxx
all:
finished. total time: 0.380s
Since you have access to the bootloader did you try entering recovery from the bootloader itself?...or try using: fastboot reboot recovery, or adb reboot recovery?
I basically have the same problem as you... except my phone is still bootloader locked and s-on. Have you tried putting a 2PS6IMG.zip file (ruu) on the root of a FAT32 formatted microSD card and see if you can access download mode that way?
chrisz5z said:
Since you have access to the bootloader did you try entering recovery from the bootloader itself?...or try using: fastboot reboot recovery, or adb reboot recovery?
Click to expand...
Click to collapse
I tried both. Via bootloader and fastboot command but nothing worked.
adb reboot recovery also doesn't work. There is no devices in adb mode.
Code:
c:\android>adb devices
List of devices attached
c:\android>
mang0 said:
I basically have the same problem as you... except my phone is still bootloader locked and s-on. Have you tried putting a 2PS6IMG.zip file (ruu) on the root of a FAT32 formatted microSD card and see if you can access download mode that way?
Click to expand...
Click to collapse
The download mode is, as I see it, completely bricked. There is no way to enter it.
Without an SDcard it should at least boot into it. But the device is going back to the bootloop.
To answer your question... no I don't try it
domme0852 said:
I tried both. Via bootloader and fastboot command but nothing worked.
adb reboot recovery also doesn't work. There is no devices in adb mode.
Code:
c:\android>adb devices
List of devices attached
c:\android>
The download mode is, as I see it, completely bricked. There is no way to enter it.
Without an SDcard it should at least boot into it. But the device is going back to the bootloop.
To answer your question... no I don't try it
Click to expand...
Click to collapse
You wouldn't be able to see much information via fastboot getvar all unless you were in download mode, so it's not really that strange.
Sometimes you can "trick" (I don't know if that's the correct word) the system into entering download mode from the above method.
At least, from this post and this post, that is what I gathered.
mang0 said:
Sometimes you can "trick" (I don't know if that's the correct word) the system into entering download mode from the above method.
At least, from this post and this post, that is what I gathered.
Click to expand...
Click to collapse
I tried the Method but the Phone still don't want to boot into download mode. It starts the bootloop like before.
I also tried to do an Update via the RUU.exe but this doesn't work too. The program stops with the error low battery although the phone was the whole night on the charger in bootloader. (Don't know if it does not charge right in this state)
Help I have the same problem
Its a simple fix. Take your phone back to carrier or HTC
Hello an sorry for my bead english.
Today i tried to root my htc 10 and after i relockd oem, my patter to unlock the encription its not working... I can't enter in to twrp.
I tried to unlock the bootloader again and nothig...
It's there any way to recover frome this?
Are you able to enter download mode still (volume down+power). If so do the command "fastboot getvar all" in fastboot mode and post back here. pls delete imei or serial number info
ayyu3m said:
Are you able to enter download mode still (volume down+power). If so do the command "fastboot getvar all" in fastboot mode and post back here. pls delete imei or serial number info
Click to expand...
Click to collapse
Thx for the reply!
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: FA65MBN00470
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 354261072618309
(bootloader) version-main: 3.16.401.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__034
DjAurelian83 said:
Hello an sorry for my bead english.
Today i tried to root my htc 10 and after i relockd oem, my patter to unlock the encription its not working... I can't enter in to twrp.
I tried to unlock the bootloader again and nothig...
It's there any way to recover frome this?
Click to expand...
Click to collapse
When TWRP asks for the password (your post looks like you still have TWRP installed?), tap "cancel" (or something like that ~ I don't remember exactly but I think it's cancel)
Then go to advanced > file manager and navigate to data/system/locksettings.db and delete that.
When you reboot you can enter a new password.
xunholyx said:
When TWRP asks for the password (your post looks like you still have TWRP installed?), tap "cancel" (or something like that ~ I don't remember exactly but I think it's cancel)
Then go to advanced > file manager and navigate to data/system/locksettings.db and delete that.
When you reboot you can enter a new password.
Click to expand...
Click to collapse
It's "reloked". I can't access twrp. I need a way to unlock bootloader witouth bootin in to android..... so i cand access twrp an install the backup... i don't know....
I was talking about the pattern enctiption @ the boot of android not frome the bigining of twrp..
DjAurelian83 said:
It's "reloked". I can't access twrp. I need a way to unlock bootloader witouth bootin in to android..... so i cand access twrp an install the backup... i don't know....
I was talking about the pattern enctiption @ the boot of android not frome the bigining of twrp..
Click to expand...
Click to collapse
Boot your phone to download mode by pressing power + vol down to boot it up.
From download mode select bootloader
From bootloader select recovery
If TWRP is still on your phone it'll take you to that.
And I realize what were talking about. Following my previous instructions will remove the pattern lock (and any other password/PIN) via TWRP so you can boot into your phone.
xunholyx said:
Boot your phone to download mode by pressing power + vol down to boot it up.
From download mode select bootloader
From bootloader select recovery
If TWRP is still on your phone it'll take you to that.
And I realize what were talking about. Following my previous instructions will remove the pattern lock (and any other password/PIN) via TWRP so you can boot into your phone.
Click to expand...
Click to collapse
I tried and it's getting stuck in a reboot loop, or its shuting down after 1-2 seconds
As long as i know twrp works only if bootloader is unloked.
Ok, today i manage to reinstall the firmware and when i try to enter recovery mode, i get the exclamation red triangle. It's not shuting down any more.
I forgot to say, i have a clean twrp recovery saved if it help's somehow, including the system_image.emmc ...
Ok... So i did it!!!!!!!!!!!!!! It's alive again!!!!!!!!!
Hope this help's all with the same issue
If are in the same "place" follow there spteps and u will be able to hard reset ur phone:
1. reflush your phone firmware. This will erase any custom recovery and instrall the stock one.
2. reboot in to download mode -> reboot in to bootloader -> reboot to recoverry
3. in recoverry you will get the red triangle with exclamation marck, don't get cared The red triangle with exclamation isn't an error or problem or anything, it's what the stock recovery looks like!
At this screen, press Volume Up + Power, and you get the menu.
After that is all yours! Navigate volume bottons to wher you need!
If u got qwestions just reply to this post.
Thnx and have funn u all!!