My friend's One X (EndeavorU) is stuck in limbo. It doesn't have a ROM, but has a custom recovery and can be accessed while in Bootloader by Fastboot via USB. Now I need a way to either push a .zip ROM with Fastboot to its SDCard and flash it via recovery, or directly flash a system.img with Fastboot.
ADB does not detect the device while in recovery, so that's out, and I can't mount the storage in recovery either as it gets that f***ing annoying MTP device cannot start error (which is also probably the reason why ADB doesn't detect it). I've tried 2 computers, the registry edits, the custom drivers, nothing fixes it, so I'm stuck.
So, in short, does anyone have a basic One X ROM in .img form that I can use to at least boot up and use bluetooth or something to get the proper ROM on it, or know of a push equivalent command for fastboot?
*edit*
Forgot to paste:
version: 0.5a
version-bootloader: 1.72.0000
version-baseband: 5.1204.167.31
version-cpld: None
version-microp: None
version-main: 4.18.401.2
product: endeavoru
platform: HBOOT-T30S
modelid: PJ4610000
cidnum: HTC__032
battery-status: good
battery-voltage: 3954mV
devpower: 81
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
Click to expand...
Click to collapse
*edit#2*
Found out that TWRP apparently doesn't work (can either have touch pre 2.4.0.0 or USB mount post 2.4.0.0, and seeing as it's worse than useless without touch, it's out.)
Which recovery do you have?
What you are asking is not exactly possible.
What I would suggest is to search for a nandroid that matches your CID and main version, then, save it to sd card, and restore stock rom.
Before that, I suggest you use philz recovery, as it must work with higher hboots (such as shown above).
[email protected]|-|oR said:
Which recovery do you have?
What you are asking is not exactly possible.
What I would suggest is to search for a nandroid that matches your CID and main version, then, save it to sd card, and restore stock rom.
Before that, I suggest you use philz recovery, as it must work with higher hboots (such as shown above).
Click to expand...
Click to collapse
Only 2 recoveries I've come across are CWM and TWRP, and neither support USB mounting.
Thought so, but doesnt hurt to ask.
One X has no SD card slot, if it had, I wouldn't be here bothering all these nice people .
Will try out that recovery, though seeing as it's based on CWM, I won't get my hopes up.
Phil'z recovery you can find in original development section.
It has USB mounting, so you can transfer the ROM or nandroid to external memory (AKA sd card ).
Послато са Nexus 7 уз помоћ Тапатока
[email protected]|-|oR said:
Phil'z recovery you can find in original development section.
It has USB mounting, so you can transfer the ROM or nandroid to external memory (AKA sd card ).
Click to expand...
Click to collapse
Couldn't even install it since it's a .zip file (also, latest versions of Phil'z Recovery are the same as CWM according to several posters, no USB mounting). Found out though that CWM 5.x.x.x works, so flashed that and used it to install a stock ROM.
Man, it's getting harder and harder to root phones, miss the days of Desire.
*edit*
Seeing as I've kinda resolved this, how do I mark the thread as answered?
Did you try to unzip, and find an ".img" file inside ?
Anyhow, I' glad you managed to help your friend. :good:
Mods will lock this thread, don't worry.
[email protected]|-|oR said:
Did you try to unzip, and find an ".img" file inside ?
Anyhow, I' glad you managed to help your friend. :good:
Mods will lock this thread, don't worry.
Click to expand...
Click to collapse
Did a quick look through, and there was no .img in the archive.
Thanks for your help .
@ShEsHy
as i can see you have a new hboot.
download this recovery "recovery"
and in fastboot use "fastboot flash recovery cwr_6.0.4.4.img"
this recovery as it has updated touch drivers for newer hboots and a "working" mount as usb feature.
Related
HI every one,
i searched the forum upto some extent but i did't find the solution.
this the status of my htc one x
i have recovery-clockwork. nooting else is working. i formated the sdcard, system, data and cache.
when i try to push any thing to sdcard it is givig the error read-only-file system.
now what are all the steps to be done to recovery back my htc one x to normal mode.
and also please provide the links from where i have to download
Details of mobile(versions):
version: 0.5a
version-bootloader: 1.12.0000
version-baseband: 2.1204.135.20
version-cpld: None
version-microp: None
version-main: 2.17.720.2
product: endeavoru
platform: HBOOT-T30S
modelid: PJ4610000
cidnum: HTC__038
battery-status: low
battery-voltage: 3523mV
devpower: 0
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
PLEASE HELP
Thanks, in advance.
Flash cwm recovery 5.8.4.0 (if you don't have it already installed)
Download a ICS rom and copy the boot.img from the rom.zip to the fastboot folder.
Put the phone in fastboot USB mode and flash the boot.img
Go into recovery and do full wipe EXCEPT Sd card ! Then mount sdcard as USB drive and Copy the rom.zip over to it
Flash the rom.zip from recovery and reboot
And stay away from the AT&T ROGERS FORUM that's for a different one x !
We have the ENDEAVORU type phone.....stay in this forum and don't flash anything from the other forum, you might brick the phone !
Thanks for the help
Thanks for the help.
MarcelHofs said:
Flash cwm recovery 5.8.4.0 (if you don't have it already installed)
Download a ICS rom and copy the boot.img from the rom.zip to the fastboot folder.
Put the phone in fastboot USB mode and flash the boot.img
Go into recovery and do full wipe EXCEPT Sd card ! Then mount sdcard as USB drive and Copy the rom.zip over to it
Flash the rom.zip from recovery and reboot
And stay away from the AT&T ROGERS FORUM that's for a different one x !
We have the ENDEAVORU type phone.....stay in this forum and don't flash anything from the other forum, you might brick the phone !
Click to expand...
Click to collapse
msaipraneeth said:
Thanks for the help.
Click to expand...
Click to collapse
But did it work ?
Hope this helps. Everything you need should be in here.
http://forum.xda-developers.com/showthread.php?t=1609190
MarcelHofs said:
But did it work ?
Click to expand...
Click to collapse
Previously I am using the old clockworkmod, now by seeing ur post i updated the recovery and mounted the sdcard. from this rest of the steps to recover is pretty simple.
msaipraneeth said:
Previously I am using the old clockworkmod, now by seeing ur post i updated the recovery and mounted the sdcard. from this rest of the steps to recover is pretty simple.
Click to expand...
Click to collapse
It's very simple
MarcelHofs said:
It's very simple
Click to expand...
Click to collapse
i found custom rom zip file. used this zip to flash the system and boot. camera and beats audio is not working with this rom.
can you provide the link for RRU 2.17.720.2 asia. so that i can update my mobile to official jelly bean released by HTC.
or provide me work around to update my phone to official jelly bean
Thanks.
You can check here, but i don't see it
http://www.htcruu.com/?dir=Endeavor
But if you have the nandroid backup.....it's the same as a ruu !
You have to restore the whole nandroid and not just the system and boot.
You have to do a full wipe from recovery and flash the boot.img from the nandroid and then restore the complete nandroid in recovery ! It's exactly the same as a ruu except the stock recovery is not included so you have to flash that after you restored the nandroid !
msaipraneeth said:
Previously I am using the old clockworkmod, now by seeing ur post i updated the recovery and mounted the sdcard. from this rest of the steps to recover is pretty simple.
Click to expand...
Click to collapse
These are steps followed to recovery my whole HTC one x normal state.
1. Flashed the boot and recovery images form 2.17.720.2 OTA.
2. oem lock
3. Downloaded the RUU 2.17.720.2 from file factory (for this u need primer account. just googled it). As my device main version is 2.17 for ur download the respective ones.
4. Ran the RUU when the mobile is in fastboot mode.
5. That's it my devices is recovered back to 2.17.720.2
6. Software update is done form about section. (with out any issue.)
these steps are simple but, to identify these i have done lot of searching and background work.
at last I did it.
thanks for members helped me and thanks for XDA.
Now i got some idea about the process involved in the booting up of device and upgrade process. if you stuck any of the issue mentioned in the previous post of this thread. reply back with the issue.
Hello there,
I have the htc one m8. tried to install custom rom while i did followed carefully all steps beside the annoying thing - s-off.
It hasnt says anything about it and i just did those steps:
Open bootloader
install TWRP recovery
flash the rom
Then my m8 reboot but stock on the htc green logo, tried almost everything i had in mind including use my dad GS4 to transfer stock rom into my SD card and then try to install it throw recovery mod which of course, failed.
dont know what alse to do i've been like this for 4-5 hours, please help me!! :crying::crying:
ben33891471 said:
Hello there,
I have the htc one m8. tried to install custom rom while i did followed carefully all steps beside the annoying thing - s-off.
It hasnt says anything about it and i just did those steps:
Open bootloader
install TWRP recovery
flash the rom
Then my m8 reboot but stock on the htc green logo, tried almost everything i had in mind including use my dad GS4 to transfer stock rom into my SD card and then try to install it throw recovery mod which of course, failed.
dont know what alse to do i've been like this for 4-5 hours, please help me!! :crying::crying:
Click to expand...
Click to collapse
Hold down the power button + vol up till your phone reboots (it'll take a bit, 20 seconds or so). AS SOON AS THE SCREEN GOES BLACK slide your finger from vol up to vol down. That will take you to your bootloader.
Hook up to your PC and get into ADB. Enter the command fastboot getvar all and post the readout here. Delete your serial no and IMEI from the readout before posting it for your own security.
xunholyx said:
Hold down the power button + vol up till your phone reboots (it'll take a bit, 20 seconds or so). AS SOON AS THE SCREEN GOES BLACK slide your finger from vol up to vol down. That will take you to your bootloader.
Hook up to your PC and get into ADB. Enter the command fastboot getvar all and post the readout here. Delete your serial no and IMEI from the readout before posting it for your own security.
Click to expand...
Click to collapse
Ok there:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.14.21331931.LA21G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 0a41237a
hbootpreupdate: 11
gencheckpt: 0
ben33891471 said:
Ok there:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.14.21331931.LA21G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 0a41237a
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
You have old firmware and probably tried flashing a 4.4.4 ROM. I would suggest getting S-Off to update your firmware. Also your version main is blank. That would give your actual firmware version, but I can tell it is 4.4.2 based from your hboot number. It is blank because the TWRP version you are using is either old or 2.8.1.0. Both will cause that. Update your recovery as well.
In the meantime, flash this in recovery. It is a stock ROM backup that should fix your issue.
If you are going to try to run newer versions of ROMs, you'll need to have newer firmware. You can either get S-Off to do that, or convert back to stock (stock ROM and recovery, unmodified system partition) and take the OTAs.
xunholyx said:
You have old firmware and probably tried flashing a 4.4.4 ROM. I would suggest getting S-Off to update your firmware. Also your version main is blank. That would give your actual firmware version, but I can tell it is 4.4.2 based from your hboot number. It is blank because the TWRP version you are using is either old or 2.8.1.0. Both will cause that. Update your recovery as well.
In the meantime,flash this in recovery[/URL]. It is a stock ROM backup that should fix your issue.
If you are going to try to run newer versions of ROMs, you'll need to have newer firmware. You can either get S-Off to do that, or convert back to stock (stock ROM and recovery, unmodified system partition) and take the OTAs.
Click to expand...
Click to collapse
Yes, my phone is a at&t one, 4.4.2. tried to install the new version of android revolution hd with the lolipop 5.0.
I'm downloading the stock rom you gave me, but how do i install it? via cmd? becuase i cant transfer it to my htc..
ben33891471 said:
Yes, my phone is a at&t one, 4.4.2. tried to install the new version of android revolution hd with the lolipop 5.0.
I'm downloading the stock rom you gave me, but how do i install it? via cmd? becuase i cant transfer it to my htc..
Click to expand...
Click to collapse
You can't put it onto your extSD? In the bootloader menu, pick hboot (vol keys to navigate, power button to select) and it will give you the option for booting into recovery.
Or in ADB/fastboot issue the command fastboot reboot-recovery
xunholyx said:
You can't put it onto your extSD? In the bootloader menu, pick hboot (vol keys to navigate, power button to select) and it will give you the option for booting into recovery.
Or in ADB/fastboot issue the command fastboot reboot-recovery
Click to expand...
Click to collapse
I'll use my sister gs4 to copy the rom to the SD card. Back to you soon with answer
xunholyx said:
You can't put it onto your extSD? In the bootloader menu, pick hboot (vol keys to navigate, power button to select) and it will give you the option for booting into recovery.
Or in ADB/fastboot issue the command fastboot reboot-recovery
Click to expand...
Click to collapse
omg its says failed right away when i do "swipe to confirm flash".. what should i do?
ben33891471 said:
omg its says failed after 2 sec.. what should i do?
Click to expand...
Click to collapse
Okay. I didn't explain the process thinking you would realize that it is a nandroid backup and not a ROM.
You have to place it into your TWRP backup folder.
Here are the instructions:
Q : How do i restore the stock nandroid backup
A : In general :
- Place the nandroid backup unpacked on the sdcard of the phone in the right backup folder
TWRP uses - TWRP\Backups\ or TWRP/Backups/serialnum/ (replace serialnum with your device's serial number. To have TWRP create the proper directory structure for you, just do a simple backup of just the boot partition and put the backup files in there) thanks to garyd9 for the additional info
- Flash the boot.img or boot.emmc.win file from the nandroid backup
- Make a full wipe in the recovery
- Restore the nandroid backup and reboot
If your backups are saved to your SD card, that's where to put it. It's always best to save nandroids to external.
---------- Post added at 01:16 PM ---------- Previous post was at 12:49 PM ----------
ben33891471 said:
omg its says failed right away when i do "swipe to confirm flash".. what should i do?
Click to expand...
Click to collapse
This will probably be easier for you. Download this ROM. It is 4.4.2 based and should work for you. It's not a backup, so no messing around putting it into a folder. Place it onto your extSD and flash it in recovery.
xunholyx said:
Okay. I didn't explain the process thinking you would realize that it is a nandroid backup and not a ROM.
You have to place it into your TWRP backup folder.
Here are the instructions:
Q : How do i restore the stock nandroid backup
A : In general :
- Place the nandroid backup unpacked on the sdcard of the phone in the right backup folder
TWRP uses - TWRP\Backups\ or TWRP/Backups/serialnum/ (replace serialnum with your device's serial number. To have TWRP create the proper directory structure for you, just do a simple backup of just the boot partition and put the backup files in there) thanks to garyd9 for the additional info
- Flash the boot.img or boot.emmc.win file from the nandroid backup
- Make a full wipe in the recovery
- Restore the nandroid backup and reboot
If your backups are saved to your SD card, that's where to put it. It's always best to save nandroids to external.
---------- Post added at 01:16 PM ---------- Previous post was at 12:49 PM ----------
This will probably be easier for you. Download this ROM. It is 4.4.2 based and should work for you. It's not a backup, so no messing around putting it into a folder. Place it onto your extSD and flash it in recovery.
Click to expand...
Click to collapse
I cant to full wipe, only System and cache. Dalvik cache and Data says Failed right away.
I couldn't restore from the backup its says failed as well.
I'm downloading this rom now, hopefully it will work.
Just to be sure, after the download done, i move the zip to my SD card then go to recovery and flash? no other things to do? commands?
ben33891471 said:
I cant to full wipe, only System and cache. Dalvik cache and Data says Failed right away.
I couldn't restore from the backup its says failed as well.
I'm downloading this rom now, hopefully it will work.
Just to be sure, after the download done, i move the zip to my SD card then go to recovery and flash? no other things to do? commands?
Click to expand...
Click to collapse
Yes, just flash it. If you have issues after the flash, retry the wipes and flash it again. Not being able to wipe dalvik and data is strange. What version of TWRP are you using? The newest is 2.8.4.0. I'm using 2.8.3.0 and don't have these problems. You should probably update your recovery. The system, cache, and dalvik get wiped automatically during the ROM install as the devs have that put into the install script.
xunholyx said:
Yes, just flash it. If you have issues after the flash, retry the wipes and flash it again. Not being able to wipe dalvik and data is strange. What version of TWRP are you using? The newest is 2.8.4.0. I'm using 2.8.3.0 and don't have these problems. You should probably update your recovery. The system, cache, and dalvik get wiped automatically during the ROM install as the devs have that put into the install script.
Click to expand...
Click to collapse
This is the name of file Official-TWRP-m8wlv
maybe you could give me the TWRP you have?
ben33891471 said:
This is the name of file Official-TWRP-m8wlv
maybe you could give me the TWRP you have?
Click to expand...
Click to collapse
That's the version for Verizon. Are you on Verizon? If so, you can find all the Verizon TWRP downloads here: http://techerrata.com/browse/twrp2/m8_wlv
If you aren't on Verizon, then that will be what is causing your issues.
xunholyx said:
That's the version for Verizon. Are you on Verizon? If so, you can find all the Verizon TWRP downloads here: http://techerrata.com/browse/twrp2/m8_wlv
If you aren't on Verizon, then that will be what is causing your issues.
Click to expand...
Click to collapse
Oh crap
I'm on AT&T
Just download this one http://www.handy-faq.de/forum/htc_o..._0_touch_recovery_2015_01_01_twrp_themes.html
is it ok?
ben33891471 said:
Oh crap
I'm on AT&T
Just download this one http://www.handy-faq.de/forum/htc_o..._0_touch_recovery_2015_01_01_twrp_themes.html
is it ok?
Click to expand...
Click to collapse
Maybe. The link I gave you is from the official TWRP website, just like this next link is. Flashing a recovery not meant for your device can really screw stuff up and possibly hard brick your phone. Be more careful.
You will want to use one of these recovery versions. I'm using 2.8.3.0, but I have heard good things about the newest 2.8.4.0.
http://techerrata.com/browse/twrp2/m8
ben33891471 said:
Oh crap
I'm on AT&T
Just download this one http://www.handy-faq.de/forum/htc_o..._0_touch_recovery_2015_01_01_twrp_themes.html
is it ok?
Click to expand...
Click to collapse
At&t and GSM variants use same recovery so flash 2.8.4.0 provided in the link above BY xunholyx.
Also i recommend to upgrade the rom by running stock backup and then update through official OTA ..
xunholyx said:
Maybe. The link I gave you is from the official TWRP website, just like this next link is. Flashing a recovery not meant for your device can really screw stuff up and possibly hard brick your phone. Be more careful.
You will want to use one of these recovery versions. I'm using 2.8.3.0, but I have heard good things about the newest 2.8.4.0.
http://techerrata.com/browse/twrp2/m8
Click to expand...
Click to collapse
Allright thanx, this one is for AT&T, right?
Listen the download of the viperone rom just stop in 695 MB
I really dont know what to do, you think after ill put this TWRP recovery you just bring me, and try to flash revolution rom or used the backup it will work?
Even if i dont have s-off ?
xunholyx said:
Maybe. The link I gave you is from the official TWRP website, just like this next link is. Flashing a recovery not meant for your device can really screw stuff up and possibly hard brick your phone. Be more careful.
You will want to use one of these recovery versions. I'm using 2.8.3.0, but I have heard good things about the newest 2.8.4.0.
http://techerrata.com/browse/twrp2/m8
Click to expand...
Click to collapse
ahsan64 said:
At&t and GSM variants use same recovery so flash 2.8.4.0 provided in the link above BY xunholyx.
Also i recommend to upgrade the rom by running stock backup and then update through official OTA ..
Click to expand...
Click to collapse
damm its not working not the TWRP 2.8.4.0 and not the 2.8.3.0
i just ****ing want my phone to get work again why im ****ing stupid i screw my phone
i dont care dont have root and the other **** things just want my phone to work again dont care even on stock
please help me i get nervous its almost 12 hours im try to solve this
ben33891471 said:
damm its not working not the TWRP 2.8.4.0 and not the 2.8.3.0
i just ****ing want my phone to get work again why im ****ing stupid i screw my phone
i dont care dont have root and the other **** things just want my phone to work again dont care even on stock
please help me i get nervous its almost 12 hours im try to solve this
Click to expand...
Click to collapse
what's not working.. ?
Or any error while installing rom .
Can you please show the commands how you are flashing recovery .
ahsan64 said:
what's not working.. "
Or error while installing rom .
Can you please show the commands how you are flashing recovery .
Click to expand...
Click to collapse
I type fastboot boot and then paste the file its done and restart but stock on the logo with the red words and when i tap on the screen there is vibrate but thats all
please help me bro i dont know what to do
Self-admitted newb here. Been reading up on FAQs and instructions on how to Root my new device and am eager to learn more to eventually fully optimize. I was able to unlock, but when attempting to flash TWRP recovery, it'll just hang forever with this message:
"sending 'recovery' (11976 KB)...".
I confirmed checksums of files downloaded, USB Debugging is flagged, Fastboot is deselected, updated the HTC drivers on my PC, and my S/N is acknowledged with the 'fastboot devices' command. I even did a Factory Reset from bootload screen, as this is a new device with no data on it yet.
Any helpful suggestions on determining next steps would be greatly appreciated!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA12.5mv
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.109
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You need 2.7 series..
flyera343 said:
You need 2.7 series..
Click to expand...
Click to collapse
Agreed, and I was mistakenly attempting to flash twrp-2.8.6.1-m8.img initially . I'm sorry I failed to mention that in the original post and yes, I also did erase cache several times. Re-attempting to flash twrp-2.7.0.1-m8.img is when the 'sending recovery' hang issue comes up.
bump
pill_popper said:
(bootloader) version-main: 1.54.401.109
(bootloader) modelid: 0P6B12000
(bootloader) security: off
Click to expand...
Click to collapse
You have a very old software version. Since your device is S-Off, I suggest :
1. change the MID 0P6B12000 to 0P6B10000
Follow this thread : http://forum.xda-developers.com/showthread.php?t=2708581
2. run 4.16.401.10 RUU.exe - https://docs.google.com/file/d/0B17smFr95pleeTQ5U1NzNkZzM0U/edit?pli=1
RUU will flash your entire phone back to stock including recovery
(as your device is S-Off, no need to lock/relock bootloader)
3. Now you can install the latest TWRP recovery and do whatever you want to do
Thank you for your kind words. I appreciate it. Will follow up on the points covered in your post and report back.
Ahh.. you need a rooted ROM to do that change of MID.
Without a custom recovery installed, you may not have a rooted ROM.
Reading back your problem ... the error is stuck at sending recovery, not enter recovery. This is possible if you don't have a proper fastboot/adb files.
Try this : http://forum.xda-developers.com/showthread.php?t=2317790
then try to install TWRP recovery again
ckpv5 said:
Ahh.. you need a rooted ROM to do that change of MID.
Without a custom recovery installed, you may not have a rooted ROM.
Reading back your problem ... the error is stuck at sending recovery, not enter recovery.
Click to expand...
Click to collapse
Correct, sorry if I wasn't being clear about that. I've Unlocked, but not yet rooted hence, the attempt to send TWRP. I haven't yet taken next steps though.
ckpv5 said:
This is possible if you don't have a proper fastboot/adb files.
Try this : http://forum.xda-developers.com/showthread.php?t=2317790
then try to install TWRP recovery again
Click to expand...
Click to collapse
More reading! :cyclops:
**Updated**
So I've tried using Minimal ADB tool as well. Now instead of hanging, I'm eliciting errors.
target reported max download size of 1830711296 bytes
sending 'recovery' (11976 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.023s
I'm running as Administrator in Windows 7, I can hear the PC recognize the phone when I plug it in the USB and I've also confirmed multiple times the 'fastboot devices' command recognizes my phone.
If this might be a USB related issue, how would I go about investigating in that direction? Not sure what is preventing me from simply flashing a TWRP recovery. Any thoughts on this are welcome, thank you.
*bumpity bump*
So I can see 'FASTBOOT USB' in bootloader mode, and the fastboot devices command returns my S/N, but still the adb devices command just returns the message 'list of devices' and nothing else. Attempting to flash TWRP recovery still fails. I've uninstalled all HTC stuff and manually updated the driver to 'MTP USB Device' via Device Manager per redpoint73's advice. Before I give up on this PC, are there any additional steps I can take? Any guidance from you guys would be appreciated, thanks!
First, you don't run adb command when on fastboot mode, only fastboot command will work.
Is the USB 3.0 on PC ? You need USB 2.0
Is your device properly working ?
I like to suggest to flash Dev Edition firmware to your device or simply run the Dev Edition RUU to bring the hboot/software version to the latest version before you try TWRP again.
You have MID/CID that match/fit a Dev Edition device except the software version no.
ckpv5 said:
First, you don't run adb command when on fastboot mode, only fastboot command will work.
Is the USB 3.0 on PC ? You need USB 2.0
Is your device properly working ?
I like to suggest to flash Dev Edition firmware to your device or simply run the Dev Edition RUU to bring the hboot/software version to the latest version before you try TWRP again.
You have MID/CID that match/fit a Dev Edition device except the software version no.
Click to expand...
Click to collapse
I guess what most on here would consider to be trivial are to me revelations. Thank you for your response and now I see my device S/N is recognized after running the adb devices command when the phone is running in 'normal' mode! Yes, it is properly working but sadly, all four USB ports on the PC are USB 3.0 I'll read up on your suggestions and reply with questions at that point before taking action. Again with the reading! :cyclops: My concerns here are if stock recovery would continue to work if I go down either of those paths and how the phone is supposed to respond if it's not responding when attempting to flash TWRP. Thanks again for your inputs, I appreciate it!
First .. you need to know your reason to install a TWRP. If you plan to install a custom ROM, it won't properly work because you have a very low version hboot as most custom ROMs require a hboot 3.19.0000
then .. there are other ways to achieve this (all because you have a S-Off device)
1. You can install TWRP using the external_sd (microSD) method but you can only use a lower version TWRP 2.7.x.x or better 2.8.1.0 (because you failed in fastboot method)
2. As I said earlier - install the latest firmware.zip but using the external_sd method too ... but your device may get stuck because your ROM is too low
3. The safest/fastest is install RUU but again you need a USB 2.0 (I'm not sure whether you can install RUU zip using the external_sd method).
4. Back to no. 2 - you can install the firmware.zip using the external_sd method (need to do it twice) then install TWRP again the external_sd method then you need to install a ROM or restore a backup meant for the newer hboot 3.19
ckpv5 said:
First .. you need to know your reason to install a TWRP. If you plan to install a custom ROM, it won't properly work because you have a very low version hboot as most custom ROMs require a hboot 3.19.0000
then .. there are other ways to achieve this (all because you have a S-Off device)
1. You can install TWRP using the external_sd (microSD) method but you can only use a lower version TWRP 2.7.x.x or better 2.8.1.0 (because you failed in fastboot method)
2. As I said earlier - install the latest firmware.zip but using the external_sd method too ... but your device may get stuck because your ROM is too low
3. The safest/fastest is install RUU but again you need a USB 2.0 (I'm not sure whether you can install RUU zip using the external_sd method).
4. Back to no. 2 - you can install the firmware.zip using the external_sd method (need to do it twice) then install TWRP again the external_sd method then you need to install a ROM or restore a backup meant for the newer hboot 3.19
Click to expand...
Click to collapse
If I wanted to attempt #3, please point me to the correct version as it wasn't clear to me what file to choose here:
http://forum.xda-developers.com/showthread.php?t=2701376
Thanks!
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put device on fastboot/bootloader mode
2. run the exe (select run as administrator in windows context menu
3. follow instruction - accept, next, next, blablabla until finish
ckpv5 said:
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put device on fastboot/bootloader mode
2. run the exe (select run as administrator in windows context menu
3. follow instruction - accept, next, next, blablabla until finish
Click to expand...
Click to collapse
The whole point of this exercise is to gain root so that yes, I can have the option of flashing a custom ROM. I noticed in the executable's file name you referenced model M8_UL_L50, but mine is M8_UL_CA. I also noticed its radio version differs from the one listed in my getvar all file. *edit* I've now realized this file is straight from HTC.
Since my current version is so old, is it still OK to run this to update to the latest version rather than updating to an intermediate version before updating to the latest version? Just wanted to confirm before taking any unnecessary action. Thank you again for your patience and the helpful information!
M8_UL - M8 with LTE
L50 - Android L 5.0
CA - US region
Radio version different because yours is old/lower version and this is newer/latest version and you're going to update hboot, radio and many more with this RUU. You need the update in order to install custom ROM as I mentioned before most custom ROMs work only on hboot 3.19.0000
You have S-Off device, you don't need intermediate version ... and most important RUU doesn't need intermediate version because RUU will wipe clean your device and replace all images with those come with it. (So make a backup of your important files to 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).
Hi guys, I'm stuck in a bootloop with Android Revolution HD Rom installed, I took the risk and flashed it now I'm in a bootloop.
I'm pretty sure I just need a firmware update...
Can someone tell me what to do please!!!
Care to walk me through what you've done step by step?
SUPERUSER said:
Care to walk me through what you've done step by step?
Click to expand...
Click to collapse
Hi, yep. I've unlocked the bootloader installed twrp and rooted.....but all the twrps I've tried won't allow me to stick in a usb with a rom on....
So I stuck Android revolution HD on internal storage and flashed it from there except I'm now stuck in the bootloop.
I can adb/fastboot but I can't adb sideload as the pc says no devices attached when I boot into recovery when plugged into pc....
It's was on Orange UK but they are no longer so I wanted to wipe....
It would be OK if I could s-off and superCID but I can't so I'm stuck!!!
SUPERUSER said:
Care to walk me through what you've done step by step?
Click to expand...
Click to collapse
version: 0.5a
version-bootloader: 1.36.0000
version-baseband: 5.1204.163R.30
version-cpld: None
version-microp: None
version-main: 3.16.61.8
serialno: ***********
imei: ************
product: endeavoru
platform: HBOOT-T30S
modelid: PJ4610000
cidnum: ORANG001
battery-status: good
battery-voltage: 4156mV
devpower: 100
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
Just to confirm some details.
Is this the rom you flashed?
https://forum.xda-developers.com/showthread.php?t=1562603
And this file is the one you flashed?
https://androidfilehost.com/?fid=24415232478675057
The recoveries used for this device is divided into new and old layout.
Android Revolution HD uses the old layout.
To be sure you use the old layout just keep using an old version of.
https://eu.dl.twrp.me/endeavoru/
So you would use twrp twrp-2.6.3.0-endeavoru.img.
All the other links starts with 3.0 and that is the new layout.
If you have all this in order.
And you remembered to wipe everything before flashing this rom?
If so then your problem would be solved by easily flashing the boot.img in fastboot which is the kernel.
We cannot touch the kernel from the recovery because there is no official way to s-off the one x.
So when you flash a rom you are only half way there with this particular device because you need to boot to hboot and go into fastboot mode.
On a computer open the rom archive Android_Revolution_HD-One_X_33.1.zip and extract boot.img.
Open a cmd in the same folder ( hold shift and right click and select Open command window here)
In the cmd type "fastboot flash boot boot.img" without the quotes.
If you do not have adb/fastboot installed get it here https://forum.xda-developers.com/showthread.php?t=2588979
It will install all tools you need and even the driver but you will need to manually select this driver if your computer does not see your one x.
But we'll take it from there when and if that happens.
SUPERUSER said:
Just to confirm some details.
Is this the rom you flashed?
https://forum.xda-developers.com/showthread.php?t=1562603
And this file is the one you flashed?
https://androidfilehost.com/?fid=24415232478675057
The recoveries used for this device is divided into new and old layout.
Android Revolution HD uses the old layout.
To be sure you use the old layout just keep using an old version of.
https://eu.dl.twrp.me/endeavoru/
So you would use twrp twrp-2.6.3.0-endeavoru.img.
All the other links starts with 3.0 and that is the new layout.
If you have all this in order.
And you remembered to wipe everything before flashing this rom?
If so then your problem would be solved by easily flashing the boot.img in fastboot which is the kernel.
We cannot touch the kernel from the recovery because there is no official way to s-off the one x.
So when you flash a rom you are only half way there with this particular device because you need to boot to hboot and go into fastboot mode.
On a computer open the rom archive Android_Revolution_HD-One_X_33.1.zip and extract boot.img.
Open a cmd in the same folder ( hold shift and right click and select Open command window here)
In the cmd type "fastboot flash boot boot.img" without the quotes.
If you do not have adb/fastboot installed get it here https://forum.xda-developers.com/showthread.php?t=2588979
It will install all tools you need and even the driver but you will need to manually select this driver if your computer does not see your one x.
But we'll take it from there when and if that happens.
Click to expand...
Click to collapse
Fantastic, the Phoenix rose from the ashes!!!!
Thank you very much :laugh:
Everything you said above was correct, I just did what you said and voila, working perfectly.