Develop Bugs

cm7r2

just tried to flash alpharev cm7r2 file using android flasher. In hboot mode it says alpharev cm7r2. I tried to boot into 4ext recovery but it says it fails to fetch recovery log. So I cant use recovery and if I try to use android flasher to flash recovery again or hboot it stops responding. What should I do?
Any help and I would be very grateful.

Assume that you are s-off.
Can you still get you h-boot screen?
If so you should be able to use fastboot to flash both recovery and h-boot.
I find it easier than android flasher.
There are plenty of guides about on using fastboot so would suggest reading them as well and have a search about as wont be the first to encounter this issue
Also use fastboot to wipe system and cache and reboot the bootloader and you should be fine......
There is a thread on android forum about e: failure to get recovery log
Check it out
sent from my Oxygen desire

paul8944 said:
Assume that you are s-off.
Can you still get you h-boot screen?
If so you should be able to use fastboot to flash both recovery and h-boot.
I find it easier than android flasher.
There are plenty of guides about on using fastboot so would suggest reading them as well and have a search about as wont be the first to encounter this issue
Also use fastboot to wipe system and cache and reboot the bootloader and you should be fine......
There is a thread on android forum about e: failure to get recovery log
Check it out
sent from my Oxygen desire
Click to expand...
Click to collapse
Yes i am s-off and I can get to the hboot screen. Where do I download terminal from if I have to use that to use fastboot?
Thanks for the reply

Have a read of this thread
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
It explains how to set up fastboot. The adb part is not relevant so once set up you can use commands like
Fastboot flash hboot c:\*****.img
Fastboot flash recovery
Fastboot erase
Which should enable you to change your hboot, recovery etc
The following link is a good step guide to changing your hboot along with a utility to set up fastboot
http://forum.oxygen.im/viewtopic.php?id=1412
And I would also highly recommend the oxygen rom
sent from my Oxygen desire

paul8944 said:
Have a read of this thread
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
It explains how to set up fastboot. The adb part is not relevant so once set up you can use commands like
Fastboot flash hboot c:\*****.img
Fastboot flash recovery
Fastboot erase
Which should enable you to change your hboot, recovery etc
sent from my Oxygen desire
Click to expand...
Click to collapse
When setting up the computer for fastboot it does not have enviroment variables in the advanced my computer bit. I am using windows vista

Follow this and it should work fine
How do I set up my Windows PC to use adb and fastboot?
Download SDK Tools only Open the .rar file, then drag and drop the folder "android-sdk-windows" to the C: drive Right click My computer > Properties > Advanced > Environment Variables under system variables click "path" and click "edit" at the end of the line add a sem semi colon ";" and without a space put C:\android-sdk-windows\tools -It should look like ;C:\android-sdk-windows\tools then click ok.
I assume you already have h-boot drivers installed (you need these to root with unrevoked) if not my previous post link has advice on how to do this
Update : I'm using vista as well so know this works
sent from my Oxygen desire

paul8944 said:
Follow this and it should work fine
How do I set up my Windows PC to use adb and fastboot?
Download SDK Tools only Open the .rar file, then drag and drop the folder "android-sdk-windows" to the C: drive Right click My computer > Properties > Advanced > Environment Variables under system variables click "path" and click "edit" at the end of the line add a sem semi colon ";" and without a space put C:\android-sdk-windows\tools -It should look like ;C:\android-sdk-windows\tools then click ok.
I assume you already have h-boot drivers installed (you need these to root with unrevoked) if not my previous post link has advice on how to do this
Update : I'm using vista as well so know this works
sent from my Oxygen desire[/QUO
Yep have now set the variables. What do I do next? I have read the post but it is very confusing. Thanks. I can open what I think is terminal - android sdk
Click to expand...
Click to collapse

Right
Click start > run > cmd
This will open a command window
Have you phone connected in fastboot mode
And then use fastboot commands to flash the recovery, hboot etc.
I would recommend changing your recovery to amon-ra ( but this is personnel choice)
You need the files you want to flash on you PC.
For example to flash an hboot you would use the following
Fastboot flash hboot c:\*****.Img
The same would apply for recovery etc
Fastboot flash recovery c:\*****.img
Once you have flashed hboot
Make sure you use fast boot to wipe system / cache / reboot bootloader.
Have a read of the oxygen.im link I posted on one of my previous posts in this thread.
Hope this has helped resolve your issue
sent from my Oxygen desire

paul8944 said:
Right
Click start > run > cmd
This will open a command window
Have you phone connected in fastboot mode
And then use fastboot commands to flash the recovery, hboot etc.
I would recommend changing your recovery to amon-ra ( but this is personnel choice)
You need the files you want to flash on you PC.
For example to flash an hboot you would use the following
Fastboot flash hboot c:\*****.Img
The same would apply for recovery etc
Fastboot flash recovery c:\*****.img
Once you have flashed hboot
Make sure you use fast boot to wipe system / cache / reboot bootloader.
Have a read of the oxygen.im link I posted on one of my previous posts in this thread.
Hope this has helped resolve your issue
sent from my Oxygen desire
Click to expand...
Click to collapse
I managed to open the command window but it said the command fastboot was not recognized (or something) internally or externally
Have I got the files in the correct places? Where should they be because I tried to follow the instructions very carefully?
Thanks so much for your help I hopefully nearly there!

right,
finally booted up my laptop so this should get easier for me.....
how did you root your phone, did you use unrevoked or did you s-off with revolutionary and then install the recovery that came with it.
Can you answer the following
You have the h-boot drivers installed ?
You have download and followed the steps for the SDK files.
You have set the environment variables as previously mentioned.
When you boot your phone holding down the volume button and power you get the hboot screen, can you then select fast boot. and with your phone connected to your pc does it change from fast boot to fastboot usb.
if so the commands should work. if not you could try the utility by _thalamus on the oxygen.im website
http://forum.oxygen.im/viewtopic.php?id=1412
You may want to change your recovery to amon-ra or an earlier version of clockworkmod 2.5.0 something....(i use amon-ra and rate it very highly, you can down load it from the following
http://androidforums.com/desire-all...oads-root-users-updated-22nd-july-2011-a.html)
if you can answer the above I will endeavor to assist further but why this is not setting up correctly on your pc is a bit confusing for me
but we'll keep going and get you back up and running again
UPDATE :
If your still struggling have a look at this trouble shooting guide it may be of assistance.
http://forum.xda-developers.com/showthread.php?t=1275632

Thanks so so much for your help but I will be away until prob wednesday afternoon so I will not be able to answer until then. I hope you will still be there!!!
I will check that I have followed the steps correctly and then I will reply.

Whoopeeeee!!!!!!!!!!
I managed to use android flasher to flash rmd recovery and it worked. So I have no installed runnymede aio 2.2 cm7r2 without a problem. Thank you so so much for your help Paul. xxxxxxx

RiThBo said:
Whoopeeeee!!!!!!!!!!
I managed to use android flasher to flash rmd recovery and it worked. So I have no installed runnymede aio 2.2 cm7r2 without a problem. Thank you so so much for your help Paul. xxxxxxx
Click to expand...
Click to collapse
Did you manage to change your hboot as well. ? As you can flash that as well with android flasher.
Glad to have been of assistance and if you want to try something different go for an aosp rom like oxygen which I find extremely smooth and fast.
Enjoy your rom and wait you flashing addiction to kick in and your be changing rom's, kernals and hboot on a weekly basis if not more
sent from my Oxygen desire

paul8944 said:
Did you manage to change your hboot as well. ? As you can flash that as well with android flasher.
Glad to have been of assistance and if you want to try something different go for an aosp rom like oxygen which I find extremely smooth and fast.
Enjoy your rom and wait you flashing addiction to kick in and your be changing rom's, kernals and hboot on a weekly basis if not more
sent from my Oxygen desire
Click to expand...
Click to collapse
Yes I did, I am now on cm7r2 with rmd recovery. Flashed both with android flasher.
Thank you again for your help

S-on AND Root

I've been posting here and there around here lately but thought I'd get a cleaner, more focused thread going for those of us who used HTC's unlock tool and want root.
I managed to get the bootloader unlocked with HTC's tool and installed SU and clockwork onto my Inc2 but I think I'm having problems because I'm still S-On instead of S-Off.
So, what do we do next after unlocking the bootloader? I'm under the impression that because I'm S-On still, I can flash a custom ROM, but not only the ones with the stock kernel intact. This would be why Sabotage was able to install, but Mik wouldn't. Still only a theory, though.
ANY HELP PLEASE!!!

Kayak83 said:
I've been posting here and there around here lately but thought I'd get a cleaner, more focused thread going for those of us who used HTC's unlock tool and want root.
I managed to get the bootloader unlocked with HTC's tool and installed SU and clockwork onto my Inc2 but I think I'm having problems because I'm still S-On instead of S-Off.
So, what do we do next after unlocking the bootloader? I'm under the impression that because I'm S-On still, I can flash a custom ROM, but not only the ones with the stock kernel intact. This would be why Sabotage was able to install, but Mik wouldn't. Still only a theory, though.
ANY HELP PLEASE!!!
Click to expand...
Click to collapse
There are 2 options to flash a custom ROM that has a custom kernel on an unlocked bootloader.
1. Instead of booting to recovery mode directly, you need to boot in Fastboot mode and issue the command:
Fastboot boot [path to custom recovery.img]
This will boot you into recovery mode using the custom recovery image. Then you can flash a custom ROM with a custom kernel correctly.
2. Extract the boot.img from the custom ROM zip file and copy it to your SDK tool directory.
Then boot into recovery mode and flash the custom ROM. Next you must reboot into bootloader mode and enter Fastboot mode. Enter the following command:
Fastboot flash boot [path to the boot.img file].
Try either option 1 or option 2. You do not need to do both.
Hope this helps.

tpbklake said:
There are 2 options to flash a custom ROM that has a custom kernel on an unlocked bootloader.
1. Instead of booting to recovery mode directly, you need to boot in Fastboot mode and issue the command:
Fastboot boot [path to custom recovery.img]
This will boot you into recovery mode using the custom recovery image. Then you can flash a custom ROM with a custom kernel correctly.
2. Extract the boot.img from the custom ROM zip file and copy it to your SDK tool directory.
Then boot into recovery mode and flash the custom ROM. Next you must reboot into bootloader mode and enter Fastboot mode. Enter the following command:
Fastboot flash boot [path to the boot.img file].
Try either option 1 or option 2. You do not need to do both.
Hope this helps.
Click to expand...
Click to collapse
Tried option 1 and when I go to select install zip from sd card after booting to cwm the phone restarts. Trying option 2 now...

Option #2 won't work since I get stuck at the HTC screen when trying to load a custom ROM.

Kayak83 said:
Option #2 won't work since I get stuck at the HTC screen when trying to load a custom ROM.
Click to expand...
Click to collapse
How did you try to reboot into bootloader from recovery once the ROM was flashed. Once I get into recovery I connect the phone with a USB cable and then type
Adb reboot bootloader
This will boot you into HBOOT straight from recovery and should prevent the hang at the HTC.

Ok. Let's start fresh and complete:
1- Plug phone into computer.
2- select HTC sync on phone
3- open cmd and get to sdk
4- type "adb reboot bootloader"
5- phone should reboot to HTC's recovery thing
now what?
I have cwm installed already.

Kayak83 said:
Ok. Let's start fresh and complete:
1- Plug phone into computer.
2- select HTC sync on phone
3- open cmd and get to sdk
4- type "adb reboot bootloader"
5- phone should reboot to HTC's recovery thing
now what?
I have cwm installed already.
Click to expand...
Click to collapse
Just select Charge Only, not HTC Sync.
Once you type adb reboot bootloader you should get the HBOOT screen and it should show FASTBOOT USB.
At this point you should enter Fastboot commands from you PC command prompt.
So you said you tried fastboot boot [path to recovery.img file] and it did boot you into recovery, right? Then you should be able to flash the custom ROM and reboot normally when the install is complete.
For option 2 once you are in recovery mode flash the custom ROM and then when it is finished connect the phone with the USB cable and at the command prompt you should be able to type adb devices and it will respond with your device id.
If it does, then type adb reboot bootloader and it will take you back to the HBOOT screen. From there you would then enter the following Fastboot command:
Fastboot flash boot [path to boot.img file]
Then Fastboot reboot

tpbklake said:
Just select Charge Only, not HTC Sync.
Once you type adb reboot bootloader you should get the HBOOT screen and it should show FASTBOOT USB.
At this point you should enter Fastboot commands from you PC command prompt.
So you said you tried fastboot boot [path to recovery.img file] and it did boot you into recovery, right? Then you should be able to flash the custom ROM and reboot normally when the install is complete.
For option 2 once you are in recovery mode flash the custom ROM and then when it is finished connect the phone with the USB cable and at the command prompt you should be able to type adb devices and it will respond with your device id.
If it does, then type adb reboot bootloader and it will take you back to the HBOOT screen. From there you would then enter the following Fastboot command:
Fastboot flash boot [path to boot.img file]
The Fastboot reboot
Click to expand...
Click to collapse
I'm able to fastboot into cwm. But when I go to select install zip from sd card via the phone controls (volume up/down/power), the phone reboots.

Kayak83 said:
I'm able to fastboot into cwm. But when I go to select install zip from sd card via the phone controls (volume up/down/power), the phone reboots.
Click to expand...
Click to collapse
Which version of CWM are ou using. I use CWM 5.0.2 and it works fine.

SUCCESS. Thanks for your help!

Glad you got it goin!
Sent from my ADR6350 using xda premium

Kayak83 said:
SUCCESS. Thanks for your help!
Click to expand...
Click to collapse
Which option did you have success with?

dumb question but...
how do you find the path to your custom recovery?

mza929 said:
dumb question but...
how do you find the path to your custom recovery?
Click to expand...
Click to collapse
You determine what the path is when you download the recovery image to your PC. The best place to download or copy it to is the same folder you run adb.exe and fastboot.exe from.

tpbklake said:
You determine what the path is when you download the recovery image to your PC. The best place to download or copy it to is the same folder you run adb.exe and fastboot.exe from.
Click to expand...
Click to collapse
great thank you... i was thinking i had to use a path to the recovery on my phone's storage not my PC's...

Can someone link me to a cwm recovery that works. I'm having the reboot issue after selecting choose file from SD card.
Sent from my dinc2 using XDA App

mza929 said:
Can someone link me to a cwm recovery that works. I'm having the reboot issue after selecting choose file from SD card.
Sent from my dinc2 using XDA App
Click to expand...
Click to collapse
You should look for and use CWM 5.0.2

Kayak83 said:
I've been posting here and there around here lately but thought I'd get a cleaner, more focused thread going for those of us who used HTC's unlock tool and want root.
I managed to get the bootloader unlocked with HTC's tool and installed SU and clockwork onto my Inc2 but I think I'm having problems because I'm still S-On instead of S-Off.
So, what do we do next after unlocking the bootloader? I'm under the impression that because I'm S-On still, I can flash a custom ROM, but not only the ones with the stock kernel intact. This would be why Sabotage was able to install, but Mik wouldn't. Still only a theory, though.
ANY HELP PLEASE!!!
Click to expand...
Click to collapse
OK maybe I am missing something here. Do you actually have full root? If you do, how did you get it? I don't know how to get the su binary and busybox installed. I have unlocked my bootloader using the htc supertool and I don't have root, which is keeping me from installing CWM or anything root related for that matter. I have not seen any instructions on how to root this thing since the unlock tool became compatible 3 days ago. But maybe I have missed something.
Thanks for any help.

Still cant get rom to boot... however, i have been able to fastboot into custom recovery and complete the flashing process...
Now i am just stuck at the HTC screen after reboot.
Any suggestions?
Thank you all so far. You have been most helpful.
***** update ***** I finally got it after fast booting into recovery, flashing rom, and then extracting boot.img from that rom and flashing it via fastboot.

mza929 said:
Still cant get rom to boot... however, i have been able to fastboot into custom recovery and complete the flashing process...
Now i am just stuck at the HTC screen after reboot.
Any suggestions?
Thank you all so far. You have been most helpful.
***** update ***** I finally got it after fast booting into recovery, flashing rom, and then extracting boot.img from that rom and flashing it via fastboot.
Click to expand...
Click to collapse
Yes good job. The last part is the key to getting a custom ROM installed. Glad it worked for you.
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
hackweed said:
OK maybe I am missing something here. Do you actually have full root? If you do, how did you get it? I don't know how to get the su binary and busybox installed. I have unlocked my bootloader using the htc supertool and I don't have root, which is keeping me from installing CWM or anything root related for that matter. I have not seen any instructions on how to root this thing since the unlock tool became compatible 3 days ago. But maybe I have missed something.
Thanks for any help.
Click to expand...
Click to collapse
After you have an unlocked HBOOT, you need to flash CWM recovery image in FASTBOOT mode. Once you have CWM installed, you can install the latest SU-3.0.xx.zip to root your current ROM and then you can installl and use root programs like ROM Manager, Busybox, Titianium Backup, etc. or you can install a rooted custom ROM.

restarting

hi all i have been flashing my htc one x for a bit now and i wanted try miui boot i needed to follow this
Here is a boot.img flasher, for easier flashing boot.img !!!
Instructions
1-Boot to Bootloader
2-Make sure your One X displays "fastboot usb" at the header of the fastboot screen
3-Extract the boot.img flasher zip you downloaded anywhere on your PC & run the script relating to your OS (windows, linux or mac)
4-Press the power button once, click volume down, highlight recovery & press power (This will take you to recovery)
5-Flash the downloaded ROM via recovery normally
6-Reboot
7-Enjoy!!!
i have done this but didn't have the rom on the phone and now i cant get it to boot have tried to restore with my back up stock rom no luck have tried to flash another custom rom i had still the same phone just keeps rebooting ..
help lol

chester-2k11 said:
Here is a boot.img flasher, for easier flashing boot.img !!!
Click to expand...
Click to collapse
The main thing here is flashing boot.img that belongs to the ROM that you are flashing.
When you flash the custom rom that you have, you need to flash its boot.img.
Why don't you mount usb storage in recovery and put in the MIUI rom.zip that you want to flash ?

ckpv5 said:
The main thing here is flashing boot.img that belongs to the ROM that you are flashing.
When you flash the custom rom that you have, you need to flash its boot.img.
Why don't you mount usb storage in recovery and put in the MIUI rom.zip that you want to flash ?
Click to expand...
Click to collapse
hi thanks done it now

[Q] Another bricked phone thread!

Hi all,
Hopefully someone can help. So I am stuck on the bootloop screen on CM10. I have searched and researched but so far to no avail.
Here's what I have so far:
My One X is the international version and I have unlocked the bootloader and rooted.
Instead of doing the usual route of downloading a rom on my PC, I tried it through the phone via an app on play called CM downlander.
I then attempted to install from SD as usual.
I am unable to mount the phone/sd via clockwork as the pc seems to not see the phone.
I have looked all over the web and the only thing I can find is something called android debugging bridge? This looks like it could be helpful.
Although I am a complete android geek, I am relatively new to custom android, I have run CM successfully on a GSII but that is it so if anyone can help, please could you do it newbie friendly? Thanks!

u have not flashed the kernel it seems.to mount sdcard,try rebooting recovery and then mount sdcard. just now this happened 2 me.
Sent from my One V

Which recovery do you have ? Is it cwm 5.8.4.0 ? If not ..... upgrade the recovery, it has the option to mount sd card as USB diskdrive.....and second, i doubt that you flashed the boot.img with fastboot commands ? It's needed because we can not flash complete roms with recovery because we are s-on ! You have to flash the kernel separately

First of all, download the cm10 zip from official source: get.cm/?device=endeavoru
Do you get an error if you try to mount in cwm?
Sent from my HTC One X

Sorry, being sent out by the missus! Will be back on tonight.

Hi guys, thanks for your replies earlier. In response:
I have downloaded a copy of cm10 on my pc. Unfortunately TToivanen I am unable to mount in cwm. I'm using 5.8.2.7.
I am almost certain you guys are correct, I vaguely remember flashing the kernel for my old GSII but didn't touch the kernel this time.
Now....how the hell do I do get out of this one!?
By the way, forgot to add. when I boot up I just get stuck in cm bootloop.

Easy fix: download latest cwm here:
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img
Then flash it in fastboot.
Code:
fastboot flash recovery filename.img
Then mounting usb should work.
And don't forget to extract the boot.img and flash it as well.
Sent from my HTC One X

Ok, I'm going to sound totally newbie now, I'm not sure how to do these things that you have suggested. Do I download to my pc then use a command line or something to get it to my phone?

Ok, just researching fastboot for windows now...

Alright, dl these fastboot files:
http://www.mediafire.com/?q2540u4g3v6qqd7
Extract and put the recovery img I linked in the fastboot folder.
Then hold shift and right click anywhere in that folder and select open command prompt here.
Hold power and volumedown to get to fastboot modeand connect usb cable to pc, on phone screen you should see fastboot usb.
Then execute the command I posted while ago.
Finally, on your phone menu, select hboot -> recovery.
Usb mounting should work now.
Flash rom and proceed to next step.
Installing kernel:
Extract boot.img from the rom.zip to the fastboot folder.
Open fastboot command prompt as described earlier and type
Code:
fastboot flash boot boot.img
followed by
Code:
fastboot erase cache
Sent from my HTC One X

don't forget to factory reset!...
Sent from my One V

Thanks. Just to top this off. I think my battery has died because it'll no longer switch on. I'm sure it was fully charged before I started. I know I saw a thread about that so will check it now.

Yeah, the one with the batch file.
Let it run at least overnight.
I'm off to bed and will check back tomorrow. :thumbup:
Sent from my HTC One X

TToivanen said:
Yeah, the one with the batch file.
Let it run at least overnight.
I'm off to bed and will check back tomorrow. :thumbup:
Sent from my HTC One X
Click to expand...
Click to collapse
Thanks TToivanen. LED is just slowly flashing red so will check it in the morning. Fingers crossed I can sort this tomorrow.
Cheers.

wow.....after this all, we have another expert on the team

Hi all, I'm off to a wedding today (on a Monday, I know) so won't be able to do anything to the phone today. I will be back on tomorrow though with a raging hangover. I will say though that I followed your instructions and got stuck at initiating the command. I'm not at the pc but it said something wasn't found. I'll post the full error message tomorrow.

Evening fellow geeks! Can I just say thanks for your replies so far. It's not like you are paid to do this so I just want to say that I appreciate your help.
I'm hoping that by the time I go to bed tonight I will have a working phone, that's my hope anyway.
I'm going to re-follow TToivanen's advice now and post the error message I am getting. Will post in a few minutes.

Ok, so I downloaded fast boot and the clockwork recovery file. Extracted fastboot and copied clockwork into it. Opened a command screen from fastboot, then entered the fastboot screen on my phone and attached usb.
This is where I think I am getting stuck/going wrong, I pasted fastboot flash recovery filename.img into the and screen and get the following:
C:\Users\Simon\Downloads\Fastboot>fastboot flash recovery filename.img
error: cannot load 'filename.img'
C:\Users\Simon\Downloads\Fastboot>

ilikegoogles said:
Ok, so I downloaded fast boot and the clockwork recovery file. Extracted fastboot and copied clockwork into it. Opened a command screen from fastboot, then entered the fastboot screen on my phone and attached usb.
This is where I think I am getting stuck/going wrong, I pasted fastboot flash recovery filename.img into the and screen and get the following:
C:\Users\Simon\Downloads\Fastboot>fastboot flash recovery filename.img
error: cannot load 'filename.img'
C:\Users\Simon\Downloads\Fastboot>
Click to expand...
Click to collapse
Download this. And paste to fastboot folder.
The file name in this case is: recovery-clockwork-touch-5.8.4.0-endeavoru.img
Or you can change the name to whatever easier to type.

TToivanen said:
Download this. And paste to fastboot folder.
The file name in this case is: recovery-clockwork-touch-5.8.4.0-endeavoru.img
Or you can change the name to whatever easier to type.
Click to expand...
Click to collapse
Cheers TToivanen. That is the one I have in the fastboot folder. For some reason though, I keep getting the same error when trying to execute the code.

[Q] phone failed while updating TWRP and now i cant access RECOVERY, only HBOOT.

Hey!
So here's the deal:
I'm running LiquidSmooth ROM (KK Version) and I was trying to update the ROM to the newest Lollipop version, but it kept failing. No big deal, i nandroid backed up, and then did a total wipe and tried again. Failed.
Okay, maybe my TWRP recovery was out of date, i tried updating it using the official TWRP app...
then everything went wrong. The install failed and now whenever i ask my phone to go into recovery mode, it sends me into HBoot. I've been trying for 3 days to figure this out, and i cant, so any help would be greatly appreciated.
Im not incredibly well versed at this stuff, so it might have to be a dummy's guide.
in the meantime, here are the details...
When i try to flash ANY custom recovery using ROM Installer app, here is what the error message says:
"COMMAND:
flash image recovery /storage/emulated/legacy/romtoolbox/recoveries/openrecovery-twrp-2.7.1.0-m8.img"
"OUTPUT:
/dev/block/mmcblk0p34: write error: No space left on device
3+0 records in
2+0 records out
1024 bytes transferred in 0.004 secs"
And when i try to reboot into RECOVERY (and it sends me into BOOTLOADER instead), here is the information it gives me:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO - 1.14.21331931.LA02_2G
OpenDSP - v32.2.2-00542-m8974.0213
OS -
eMMC-boot 2048MB
JUNE 16 2014 18:47:55
FASTBOOT USB
thank you so much in advance. i have NO idea what happened... i know the fact that i have S-On might have something to do with it, but i dont have access to a PC, only MACs and i can't use the Sunshine app because i'm already running a custom rom. What can i do?

The thing I noticed is the block that's indicated is not the right one,if you look at the pic below the recovery block is mmcblk0p43.
I would download the custom recovery you want and manually input it "dd" method
Or
Download the custom recovery img and use an app called Flashify

If you can't boot into Android you'll need to fastboot flash your recovery. The one you're using is rather old (I believe 2.8.3.0 is the most recent version). You'll need to download the recovery img file and place it in your ADB/Fastboot folder on your computer. Connect your phone and computer in Fastboot USB mode. Open up a command terminal and type fastboot flash recovery nameofrecovery.img and hit enter (enter the actual recovery file name and not nameofrecovery). The new recovery should then be flashed to your phone, unless you get an error in the terminal on your computer.
As stated above, Flashify works great for flashing recoveries to your phone, but it only works if you can boot into the Android OS.

I would seriously stay away from flashing recovery using apps, they rely on build.prop to identify your device, and if that's not correct the recovery will go to the wrong partition (which seems what's going on in your case because mmcblk0p34 is the recovery partition on the HTC One M7, not HTC One M8 !!!!
just flash it in bootloader (FASTBOOT USB):
Code:
fastboot flash recovery <name of recovery>.img
fastboot erase cache

Magnum_Enforcer said:
If you can't boot into Android you'll need to fastboot flash your recovery. The one you're using is rather old (I believe 2.8.3.0 is the most recent version). You'll need to download the recovery img file and place it in your ADB/Fastboot folder on your computer. Connect your phone and computer in Fastboot USB mode. Open up a command terminal and type fastboot flash recovery nameofrecovery.img and hit enter (enter the actual recovery file name and not nameofrecovery). The new recovery should then be flashed to your phone, unless you get an error in the terminal on your computer.
As stated above, Flashify works great for flashing recoveries to your phone, but it only works if you can boot into the Android OS.
Click to expand...
Click to collapse
I'll try to flash it from bootloader! Could you tell me how to place the recovery img file into my adb folder? Thank you!!!

nkk71 said:
I would seriously stay away from flashing recovery using apps, they rely on build.prop to identify your device, and if that's not correct the recovery will go to the wrong partition (which seems what's going on in your case because mmcblk0p34 is the recovery partition on the HTC One M7, not HTC One M8 !!!!
just flash it in bootloader (FASTBOOT USB):
Code:
fastboot flash recovery <name of recovery>.img
fastboot erase cache
Click to expand...
Click to collapse
Oh damn thank you!!! Is this the exact code/command I'll use in Terminal on Mac OS or does it differ since it's not a PC?

jball said:
The thing I noticed is the block that's indicated is not the right one,if you look at the pic below the recovery block is mmcblk0p43.
I would download the custom recovery you want and manually input it "dd" method
Or
Download the custom recovery img and use an app called Flashify
Click to expand...
Click to collapse
What is DD method? Thank you so much for your help

karmendc said:
Oh damn thank you!!! Is this the exact code/command I'll use in Terminal on Mac OS or does it differ since it's not a PC?
Click to expand...
Click to collapse
Don't dd
Don't flashify
Just install mini adb+fastboot for Mac and do the commands mentioned. It's pretty much the same for Windows, Mac and Linux.
Sent from my HTC One_M8 using Tapatalk

nkk71 said:
Don't dd
Don't flashify
Just install mini adb+fastboot for Mac and do the commands mentioned. It's pretty much the same for Windows, Mac and Linux.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Why do you think I've mentioned the other methods.
Not everyone understands how to use fastboot like we do.
If he has a bootable OS than Flashify will work just fine (I wouldn't recommend an app that I haven't tried/used myself)

karmendc said:
What is DD method? Thank you so much for your help
Click to expand...
Click to collapse
dd is a method using a terminal emulator on your device.
The screenshot is from the twrp website and the "dd" method is described as a working method if in fact you can boot to the OS (SuperSU is needed)

jball said:
Why do you think I've mentioned the other methods.
Not everyone understands how to use fastboot like we do.
If he has a bootable OS than Flashify will work just fine (I wouldn't recommend an app that I haven't tried/used myself)
Click to expand...
Click to collapse
Because flashify, TWRP manager, ROM manager, etc apps expect the proper device info in build.prop
and will then dd whatever partition it sees fit... In this case, it thinks it's an m7
fastboot flash does not.
Sent from my HTC One_M8 using Tapatalk

nkk71 said:
Because flashify, TWRP manager, ROM manager, etc apps expect the proper device info in build.prop
and will then dd whatever partition it sees fit... In this case, it thinks it's an m7
fastboot flash does not.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I read what you've stated already.
I agree the sure fire way is fastboot .
Easy for you
Easy for me
But maybe not so easy for some.
As long as the OP gets what he wants is all I'm in here for(not a long drawn out tutorial as those already exist)

jball said:
I read what you've stated already.
I agree the sure fire way is fastboot .
Easy for you
Easy for me
But maybe not so easy for some.
As long as the OP gets what he wants is all I'm in here for(not a long drawn out tutorial as those already exist)
Click to expand...
Click to collapse
Sorry if my answers are short and not in much detail, I'm typing on the phone... I prefer a full keyboard
But dd is not something I easily recommend (much more difficult than fastboot flash)
and if you check the build.prop of the ROM mentioned by the OP you'd see it's not entirely proper
I've seen enough bricks due to "flashy apps" and one-clicks (no offence intended to any)
fastboot at least does some checking of what is being flashed and where, so that is what I personally recommend.
Sent from my HTC One_M8 using Tapatalk

nkk71 said:
Sorry if my answers are short and not in much detail, I'm typing on the phone... I prefer a full keyboard
But dd is not something I easily recommend (much more difficult than fastboot flash)
and if you check the build.prop of the ROM mentioned by the OP you'd see it's not entirely proper
I've seen enough bricks due to "flashy apps" and one-clicks (no offence intended to any)
fastboot at least does some checking of what is being flashed and where, so that is what I personally recommend.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thank you for the more detailed information.
Small keyboards blow for sure.

@nkk71 warning is quite valid
dd used correctly, but ideally from a script, is very useful and powerful.
dd is also affectionately know as 'disk destroyer'
just one small typo, or worse getting the input and output reversed, can really make a mess.
it will write more or less anything to anything including your boot sector and data.
just saying.

gazzacbr said:
@nkk71 warning is quite valid
dd used correctly, but ideally from a script, is very useful and powerful.
dd is also affectionately know as 'disk destroyer'
just one small typo, or worse getting the input and output reversed, can really make a mess.
it will write more or less anything to anything including your boot sector and data.
just saying.
Click to expand...
Click to collapse
Thank you for the second opinion kind sir.
http://www.youtube.com/watch?v=JUCM_tJaNHU
Here is a short video on how to input the "fastboot flash recovery recovery.img " command once you have drivers correctly installed and the img file in the proper location .
Now this video is from a tablet to my HTC one m8 and not from a
PC/Desktop as it's over obvious.
Just like all other videos I don't show how to "easily" set up the drivers for fastboot (oh that's cause you don't need drivers to adb or fastboot from a tablet to a phone).

nkk71 said:
I would seriously stay away from flashing recovery using apps, they rely on build.prop to identify your device, and if that's not correct the recovery will go to the wrong partition (which seems what's going on in your case because mmcblk0p34 is the recovery partition on the HTC One M7, not HTC One M8 !!!!
just flash it in bootloader (FASTBOOT USB):
Code:
fastboot flash recovery <name of recovery>.img
fastboot erase cache
Click to expand...
Click to collapse
Okay so i finally tried flashing it using Terminal/FASTBOOT... I downloaded the latest TWRP recovery for GSM, placed it in my adb/fastboot folder...and typed in the command and it came up with an error. Here are the screenshots. Help? Im at my wits end.... thank you in advance!

wait, i got it! flashed!! I was in the wrong directory, i guess. So now i got into the correct directory, but the phone still wont go into recovery when i reboot. :crying:
Sigh. okay, back to square one.
edit:
and great. i think that "erase cache" command unmounted my internal storage...because now i get no phone signal and my local storage cannot be found.
What. is. happening.

karmendc said:
wait, i got it! flashed!! I was in the wrong directory, i guess. So now i got into the correct directory, but the phone still wont go into recovery when i reboot. :crying:
Sigh. okay, back to square one.
edit:
and great. i think that "erase cache" command unmounted my internal storage...because now i get no phone signal and my local storage cannot be found.
What. is. happening.
Click to expand...
Click to collapse
1) you're on hboot 3.18 so that would indicate you firmware (the OS- line or version-main from a fastboot getvar all) is still 2.xx.xxx.x version, so yes, you're going to have signal and wifi problems, as mentioned in the various ROM threads you need matching firmware to the ROM you're running.
2) this could also be the reason it's not entering the recovery, you could try an older version of TWRP, and make sure MD5 checks out on your download, a corrupt download could also be the reason
3) the "fastboot erase cache" doesnt affect your internal storage or anything, it just wipes the cache which will get rebuilt as needed
4) missing/not mounted internal storage, is a common issue on Android 5.x (not only HTC, many devices), download a terminal emulator to your phone (or alternatively open an abd shell), and do the following commands:
Code:
su
restorecon -FR /data/media/0