Develop Bugs

[Q] poss brick? can boot CWM, but can't flash or fastboot

I've been fighting this for hours over the last couple of days....
I rooted my phone (ebay-purchased T-mobile G2) a few months ago with the Cyanogenmod guide (http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting), got Clockworkmod on using Rommanager and (almost) everything was good.
Recently, the entire phone crashed and seemed to get stuck in a boot loop. I booted into CWM recovery (v3.0.2.4). CWM gave me these errors every single time:
"E:Can't mount /cache/recovery/command"
"E:Can't mount /cache/recovery/log"
"E:Can't open /cache/recovery/log"
"E:Can't mount /cache/recovery/last_log"
"E:Can't open /cache/recovery/last_log"
I tried to just reflash CM7 that I loaded onto the SD card via windows, always wiping data and cache first. The install would start, and then abort with "E:Error in /sdcard/update.zip" and "(Status 1)". Eventually one of the versions of CM6 started to actually install with the progress bar, but then would abort with "assert failed: write_raw_image" and "(Status 7)". Googling pointed to CWM possibly being the problem, saying updating to 3.0.2.5 would fix it. I haven't found a download for that, and because I'm stuck with boot loops, I can't get to Rommanager.
I tried using fastboot to flash the same version of CWM, but it comes up with "Failed (remote: not allowed)". Googling hints that installing stock ROM (PC10IMG?) would fix it, but I can't get that to flash or fastboot on.
I don't have a NAND backup, but I do have a CWM backup that I can't fully restore from because it always says "Error while formatting /system!". Haven't found a fix for that.
I am able to connect with ADB, but I've tried checking for the eMMC serial to see if I have a culprit chip (http://forum.xda-developers.com/showthread.php?t=1081243), and it doesn't return a value.
This thread OP is actually almost the exact same thing as I've been through except the last part about loading with hboot, which I can't get to work. And I've tried with the sd card mounted and unmounted.
I'm stumped, as most of the solutions are just "reflash ROM" or "reflash recovery" and I can't get either to work. At this point, I don't think I care if I end up rooted/customROM or stock. Any help is appreciated a hundred fold.
S-Off
HBOOT-0.82.0000
MICROP-0425
RADIO-26.03.0226_M
eMMC-boot

Hey,
Sorry, I have had the same exact problem. Spent a week+ working non stop, following every tutorial on the forums to try and fix it. I've had zero luck. good thing it was in warranty for me, I just sent it in and got a new one. just enjoying my non-rooted G2 now. I hope there is a fix for this somewhere, It has been happening quite a bit.

That's a bit discouraging. I wish I had the knowledge of the topic to even understand what the actual problem is, unless it's multiple smaller problems that I'm dealing with. It doesn't seem like a full-brick situation, but I guess it is.
Re: warranty - was it through HTC or the carrier? And how did you convince them to accept it? They usually say that rooting voids warranty, eh?

Tmobile told me rooting voids Htc 1 year warrenty but still have 129.
deductable through asurion for 5. a month.
I called Asurion to verify.
Sent from my HTC G2 using XDA Premium App

just curious but why doesn't fastboot work? otherwise you could try to recover via fastboot:
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot reboot

Here is a thread about the error
Its most probably a hardware issue, so there's nothing you can do about it except return it.
Also, fastboot probably doesn't work cause you don't have eng hboot?
-Nipqer

http://forum.cyanogenmod.com/topic/20898-easy-way-to-flash-eng-hboot-new-80416-radio-and-cwm-3024/
That PC10IMG worked great for me. All you need is S-OFF.
Once you get eng hboot, use fastboot to flash the recovery.img from your last working nandroid backup. Might want to do 'fastboot erase recovery' just before 'fastboot flash recovery recovery.img' just to give a clean slate.
Once you get in CWM you can format system, data, cache and restore from nandroid.
HTC Vision (G2) - CM7 B100 w/AUS radio
Your is not short for you are, but you're is.|It's means it is and never ever anything else.|Pluralization by way of an apostrophe is always wrong!

killerbee12345 said:
just curious but why doesn't fastboot work? otherwise you could try to recover via fastboot:
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot reboot
Click to expand...
Click to collapse
"fastboot erase boot"
"Failed (remote: not allowed)"
Nipqer said:
Here is a thread about the error
Its most probably a hardware issue, so there's nothing you can do about it except return it.
Also, fastboot probably doesn't work cause you don't have eng hboot?
-Nipqer
Click to expand...
Click to collapse
starting to seem more and more like it's hardware. i don't have an Eng HBOOT, but I am S-OFF. Cyanogen wiki says that should be enough, but I'm still stuck, so maybe.
onelikeseabass said:
http://forum.cyanogenmod.com/topic/20898-easy-way-to-flash-eng-hboot-new-80416-radio-and-cwm-3024/
That PC10IMG worked great for me. All you need is S-OFF.
Once you get eng hboot, use fastboot to flash the recovery.img from your last working nandroid backup. Might want to do 'fastboot erase recovery' just before 'fastboot flash recovery recovery.img' just to give a clean slate.
....
Click to expand...
Click to collapse
tried that PC10IMG.zip and it actually recognized it as soon as I got into HBOOT. but then I came up with the Partition Update Fail message.
Any tips on convincing HTC to warranty it anyway?

tatsuha said:
"fastboot erase boot"
"Failed (remote: not allowed)"
starting to seem more and more like it's hardware. i don't have an Eng HBOOT, but I am S-OFF. Cyanogen wiki says that should be enough, but I'm still stuck, so maybe.
tried that PC10IMG.zip and it actually recognized it as soon as I got into HBOOT. but then I came up with the Partition Update Fail message.
Any tips on convincing HTC to warranty it anyway?
Click to expand...
Click to collapse
This may be a shot in the dark, but have you tried reformatting your SD card? Back it up, format, and just put that PC10IMG.zip I linked earlier on it. Maybe it's a problem reading from the source that causes the write to fail.
HTC Vision (G2) - CM7 B100 w/AUS radio
Your is not short for you are, but you're is.|It's means it is and never ever anything else.|Pluralization by way of an apostrophe is always wrong!

onelikeseabass said:
This may be a shot in the dark, but have you tried reformatting your SD card? Back it up, format, and just put that PC10IMG.zip I linked earlier on it. Maybe it's a problem reading from the source that causes the write to fail.
HTC Vision (G2) - CM7 B100 w/AUS radio
Your is not short for you are, but you're is.|It's means it is and never ever anything else.|Pluralization by way of an apostrophe is always wrong!
Click to expand...
Click to collapse
Hadn't gotten a chance to do much during these last few days, but I finally sat down with the G2 again. I had already tried formatting, but it was a quick format, I'm fairly certain.
I tried with full reformats on both the SD cards I have (the 8GB Sandisk that came with the phone and an older 2GB Kingston). One recognized the PC10IMG, but had the same partition update fail. The other didn't even recognize the file.
If this ends up being unrecoverable, does anyone have any advice for a shot at the HTC warranty? or is there no chance that they would miss the fact that it's rooted? >_>

[Q] I need help, am going in circles with all the pages on xda-ddev and other sites

Right, basically I think I have pretty much messed up my phone, yeah yeah I know what your all thinking, seen this before.. you most likely have, I have read all the pages and tried to search for people with similar problems to me to save asking the same thing again, however I keep finding answer's that take me back to another problem on my phone.
anyway long story short, my phone wont get past bootloader. i can still get to recovery, but that does not help much as i get about 1 minute before it restarts if i plug it into my pc when in this mode, unless i format the system.
Phone spec:
Bravo PT3 SHIP S-On
Hboot-0.93.0001
Microp-051d
Touch Panel-Synt0101
Radio-5.17.05.08
Aug 10 2010, 17:52:18
Running ClockworkMod Recovery v2.5.0.1
am able to format Boot, System, Data and Cache.
However when i try format SDcard i get the message
"E: Can't Mount /dev/block/mmcblk (or /dev/block/mmcblk0p1)
(no such file or directory)
Error Mounting / SDcard/! "
I thought maybe trying to re-root my desire using unrevoked, if that would have been an option, with the latest Clockwork recovery, but it will not find my phone in fastboot. However after a few attempts of plugging in my phone ,AMDesire Recovery finds my phone and can get it to wipe the dalvic cache, sd:ext partition, create a partition, try to wipe sd:ext partition and it says "error : run 'wipe ext' via adb.
I thought at looking at the DeBricking page on here, but that seems a lot of code, and when trying to find the right downloads i to even enter all that code i have got myself a bit lost.
any help whatssoever, would be greatful,
also i apologise for this if it is in the wrong forum but as i am pretty much a new user, i am unable to post in many places.
Steve

I think you got a USB-BRICK problem.

op8867555 said:
I think you got a USB-BRICK problem.
Click to expand...
Click to collapse
This is very easy to solve i got it a lot of times
Here a link with the tutorial how to fix ithttp://android.modaco.com/content/htc-desire-desire-modaco-com/309939/usb-brick-rickrolled-b0rked-fixed/
Done in a few minutes
PS: wanted to quote not to press the thanks button anyway

adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
error: device not found..
my device drivers are android bootloader interface.
only just noticed with the adb tools that i don't need to install java SE and about 200 more apps being uploaded from adk server... but still, now i cant get past this bit!

Fastboot
Like what the other replies said, this is, most likely, a USB brick.
Try this command in fastboot mode: "fastboot oem enableqxdm 0"
Search in the forums to set up ADB/fastboot properly in your PC.

steve81uk said:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
error: device not found..
my device drivers are android bootloader interface.
only just noticed with the adb tools that i don't need to install java SE and about 200 more apps being uploaded from adk server... but still, now i cant get past this bit!
Click to expand...
Click to collapse
In order to install Android SDK you need JRE. You do not have to install all the software available in SDK you have only to download the tools.

steve81uk said:
"E: Can't Mount /dev/block/mmcblk (or /dev/block/mmcblk0p1)
(no such file or directory)
Error Mounting / SDcard/! "
Click to expand...
Click to collapse
This reads to me like you have a corrupt Ext...did you attempt to flash any alignment.zip before this happened?? Every time I try to flash an alignment, I also get this error message...hence I don't bother anymore...
My suggestion is to remove your SD and place in a card reader, then format your Ext using GParted. When you boot to recovery again, all should be sweet.
Just a thought.

dont use any EXT partition at this stage.. format ur sd card with single FAT32 partition and then try

Thanks to all of you trying to help me, I think i may need to mention that my phone does not seem to be able to read any sd card, not just the one i was using, tried my 16 gb, 8 gb, and 4gb. same message comes up.
going to try gparted later, and also have another go at creating gold card (what driver should be on set for this to work, Androidbootloader or MY HTC ? )
hopefully by the end of tonight i will have a working phone .
Once again thanks for everybody's help, I will click all the Thanks bit later
Steve

this is an usb brick, you should install android sdk, go into cmd
1. type in cd C:/android-sdk-windows/tools atleast if you have it there
go into hboot, press fastboot and connect your phone to your pc, it should say fastboot usb. then enter fastboot enable etc..(this enables the sd card read ability) after that go to the link i gave you, flash the update.zip and ur usb brick is gone,
easy as that

this sounds too simple and i still am having problems, do i not need a gold card?
Command prompt and typing in the commands you say, i continue to get an error message saying deice not found, seriously, i bet i am doing one thing wrong.. that's too simple to notice?!?!

i've never heard that you need a goldcard for a usb brick, it may sound dumb but have you installed htc sync? if so uninstall it and i you haven't install and uninstall for the drivers, usually a usb brick is solved in 4-5min, so maybe you missed out something, because when i had my first usb-brick i entered adb shell-.- you just have to type the command in once

just tried same on my notebook, no htc sync installed , Still Says error : device not found. am guessing i am pretty much screwed.

not got my hopes up too high just yet, but i think it's actually looking up a bit now, conected to phone, typed in the commands given, it can read sd card, installed update.zip. now i dunno if i should go back to backup, or try install everything again,
Thanks so much guys

[Q] Image Unzipping Fail!!!

Hello, I have like eight hours of continuous searching for solve this problem.
I installed like two months ago the Android Revolutionary HD 6.1.5 ROM, i did S-off, Radio-off, Root, etc, following the tutorials of XDA. But i installed the actualization of ARHD 6.2.0 and it works very nice but one day later when i was talking by the phone it stopped, then sense was not responding, and it finally restarted alone.
The big problem is it was only showing the HTC logo and then the screen puts black.
I get into HBoot and it searches for PD98IMG.zip
i putted the PD98IMG.zip in the card and it says this:
- Sd checking...
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nhb]
No image or wrong image!
Loading...[PD98img.zip]
I say yes and it shows:
- Image unzipping fail!
Update Fail!
Press <POWER> to reboot
I tried a lot of RUU`s, like 13 and i can´t find one who works, the only who was acepted was ono withe the recovery only. With USB it does not work either.
I sent it to the company who sold me it and they have no idea about...
I hope you can help me, i am a little dissapointed, because i tried all the RUU`s what i founded in the web.
Thank you very much, Freesoft.

Freesoft64 said:
Hello, I have like eight hours of continuous searching for solve this problem.
I installed like two months ago the Android Revolutionary HD 6.1.5 ROM, i did S-off, Radio-off, Root, etc, following the tutorials of XDA. But i installed the actualization of ARHD 6.2.0 and it works very nice but one day later when i was talking by the phone it stopped, then sense was not responding, and it finally restarted alone.
The big problem is it was only showing the HTC logo and then the screen puts black.
I get into HBoot and it searches for PD98IMG.zip
i putted the PD98IMG.zip in the card and it says this:
- Sd checking...
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nhb]
No image or wrong image!
Loading...[PD98img.zip]
I say yes and it shows:
- Image unzipping fail!
Update Fail!
Press <POWER> to reboot
I tried a lot of RUU`s, like 13 and i can´t find one who works, the only who was acepted was ono withe the recovery only. With USB it does not work either.
I sent it to the company who sold me it and they have no idea about...
I hope you can help me, i am a little dissapointed, because i tried all the RUU`s what i founded in the web.
Thank you very much, Freesoft.
Click to expand...
Click to collapse
Try to go into recovery mode. What exactly is the problem. If it is not booting in...go to recovery and select fix permissions... this will solve any problems. If not try to install a rom with full wipe and reboot. If you flash a PD98IMG.zip then once again you need to root, S OFF, etc etc....

Stop what you are doing before you brick your phone.
The PD98 error you are getting happens to all rooted DHD's, and is nothing to worry about (delete it from your sd card). RUU's are for stock devices, or for returning to stock.
Check to make sure you haven't screwed up your root access, and flash a ROM .zip file from the developers thread (in recovery, from your sd card). And always check the checksum before flashing.
Sent from The App that Time Forgot.

JagDave said:
Stop what you are doing before you brick your phone.
The PD98 error you are getting happens to all rooted DHD's, and is nothing to worry about (delete it from your sd card). RUU's are for stock devices, or for returning to stock.
Check to make sure you haven't screwed up your root access, and flash a ROM .zip file from the developers thread (in recovery, from your sd card). And always check the checksum before flashing.
Sent from The App that Time Forgot.
Click to expand...
Click to collapse
Well, actualy, i can`t get into Recovery, it reboots and the screen turns black, the only thing what the phone admits is PD98IMG.zip.
Thank you very much for responding!

Delete that file from your SD card, and check if you can get into recovery. If yes, download superWIPE for ARHD, and ARHD rom and install it ( it's different base i think, so you have to superWipe it )

PD98IMG.zip is the radio, if that's what you need they can all be found here:
http://forum.xda-developers.com/showthread.php?t=996630
Might be worth flashing the latest and seeing if your phone behaves enough afterwards to let you get into recovery.

I take it you are trying from bootloader?
Also does your computer recognize the phone on usb?
Sent from The App that Time Forgot.

Sounds to me your Recovery has an error.
Download and extract Android Flasher http://forum.xda-developers.com/showthread.php?t=794638
Boot into Bootloader & select fastboot
Use AndroidFlasher to install a new Recovery image.
Link to my copy of of the previous 4ext Touch recovery, so it should work.
Extract the image to wherever you extracted AndroidFlasher and make sure you select 'already in fastboot' prior to flashing.
Then you should be able to get into Recovery. Full wipe, install ROM, etc.
Hope this solves your problem.

JagDave said:
Sounds to me your Recovery has an error.
Download and extract Android Flasher http://forum.xda-developers.com/showthread.php?t=794638
Boot into Bootloader & select fastboot
Use AndroidFlasher to install a new Recovery image.
Link to my copy of of the previous 4ext Touch recovery, so it should work.
Extract the image to wherever you extracted AndroidFlasher and make sure you select 'already in fastboot' prior to flashing.
Then you should be able to get into Recovery. Full wipe, install ROM, etc.
Hope this solves your problem.
Click to expand...
Click to collapse
I am trying all this and i think it will work, the problem is my phone is "SHIP S-OFF"
But i don`t know hot to change from Ship to ENG...
Thank you very much for the answer, from now in one week i think my DHD will work again

If memory serves, you only need Eng to change the radio.
But don't quote me on that
Sent from The App that Time Forgot.

I have tried this http://forum.xda-developers.com/showthread.php?t=1396253
The PD98IMG.zip worked, so i am glad my desire is not bricked yet.
I still not having access to recovery, my phone is SHIP S-OFF not ENG S-OFF and i can`t change the Recovery, i can`t install the SDK drivers for bootloader.
I tried too with Android Flasher, and there doesn`t work because my phone is not ENG S-OFF.
My questions are this: how i can change now to ENG S-OFF?
What else i can do for revive the Desire HD?
Thank a lot for responding this post, i don`t know what i`ll do without all of you!

Personally I see no reason to Eng soff. You can still flash radios and recoveries with just regular soff. Just its done in a different way.
In that thread you posted their is a link for cwr in a pd98img. Just follow the directions I wrote.(its the first section)
But if you are set on getting Eng soff in the dev section you can use jkoljo tool.
Your second question confuses me. You said your phone is now working so what do you mean by reviving your phone?

Well, i tried ADB, the problem now is when i installed the drivers, in the command prompt i cant find my phone.
I was trying with this:
C:\adb devices
List of devices attached
In Device Manager it appairs like: Android Phone>Android ADB Interface
What i can do now?
I know I'm a little annoying, but I will really appreciate your help if we make it work!

Anyone can help with ADB with desire hd?

Well to be able to use command prompt on your computers first off would be to add the adb path which is normally C:\Program Files (x86)\Android\android-sdk\platform-tools or in C:\Program Files (x86)\Android\android-sdk\tools
Then you'll be able to use adb commands.
if not while in command prompt, just use the cd command to get in that directory so you can use the adb.exe
per exemple;
cd C:\Program Files (x86)\Android\android-sdk\tools
then you'll be able to use commands has
adb push [the file which should be in the same place] /data/local/tmp
Then if you just want to run command on your cell interface just write
adb shell
if you're in root you should start to write beside a #
it would look
<C:\[path]>adb shell
# [here you'll run command on your cellphone]
because if you run in command prompt right away
<C:\>adb device
without having the file to get the adb.exe
But as for using adb shell, if your device is connected and activated in debugged mode you'll be fine.

earthbrother said:
Well to be able to use command prompt on your computers first off would be to add the adb path which is normally C:\Program Files (x86)\Android\android-sdk\platform-tools or in C:\Program Files (x86)\Android\android-sdk\tools
Then you'll be able to use adb commands.
if not while in command prompt, just use the cd command to get in that directory so you can use the adb.exe
per exemple;
cd C:\Program Files (x86)\Android\android-sdk\tools
then you'll be able to use commands has
adb push [the file which should be in the same place] /data/local/tmp
Then if you just want to run command on your cell interface just write
adb shell
if you're in root you should start to write beside a #
it would look
<C:\[path]>adb shell
# [here you'll run command on your cellphone]
because if you run in command prompt right away
<C:\>adb device
without having the file to get the adb.exe
But as for using adb shell, if your device is connected and activated in debugged mode you'll be fine.
Click to expand...
Click to collapse
I did that, it doesn`t work because it says "error: device not found" i tried reinstalling many times the ADB drivers and another few with the path file, no results. With "adb devices" it says "list of devices attached" then, nothing.
I am really gratefull with all your answers, i hope we can made it work
I have a question more, it`s posible to put it in "debugging mode" from HBOOT?
Thanks a lot!

So, nobody can help me? that who help me will be rewarded!

You said only the recovery pd98 works. Reflash it. After it reboot and hangs take out battery and SD card. Reinsert battery and enter boot. Wait for it to scan, then reinsert sdcard and enter recovery. Wipe and reflash a rom or backup
Edit - still confused, from your pm you suggested that your dhd doesn't work? I need a simple yes it boots or doesn't, before we can go anywhere
Sent from my Desire HD using XDA App

[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