Develop Bugs

BIG problem!! please help (no sd-card, no usb-connection AFTER recovery image update)

hey guys,
once every serveal months i check for updates for my rom, my recovery, and some apps.
yesterday i wanted to update tp the latest recovery (1.52)
now, the phone connected, driver was installed correctly (windows 7 32-bit)
i used the adb commands as posted in the recovery topic.
now it updated it, but after a few minutes using and wiping the phone, the usb-connection will not come to live (in any way, not even a "unknown device") and when the phone booted it gave a message: "SD removed, please place sd-card." while it has a 8 gb on there. luckily i backed up all data i needed from the sd before i flashed. so i used recovery to recreate partitions and wipe sd. but nothing works anymore... when i select ANY option in recovery wich needs SD access it immediatly gives errors.
also tried a nother microsd of 1 gb which did also not work...
about the usb-connection, it also does not work in Recovery.
but in the bootloader, it installs without any problems the well known "My HTC" device. using fastboot to boot to recovery image works, but again: no usb connection
please guys... help me... without sd-card i find my phone completely useless. (because of many documents and pictures for my work.)

I've had this problem and I had to send my Hero for repair, but it could be difficult if you have custom software in there, thry to flash original rom. Not sure though if it can be done through fast boot.
Also if you have to send it back, pretend to be an idiot and say it just went wrong. "I didn't do anything" could work.

Use fastboot to revert to a stock ROM (update.zip)

This sounds very similar to this issue on Modaco - http://android.modaco.com/content-page/299174/no-adb-no-sd/
Still ongoing, as I (pulser) am trying to guide the OP through making the goldcard (need to find another android phone to do this) and then we need to try an RUU somehow???

adwinp said:
Use fastboot to revert to a stock ROM (update.zip)
Click to expand...
Click to collapse
ok, and how?
thanks for reply.
i was thinking of letting it be repaired, but as you all say, unlocked spl, recovery image, custom rom. it does not look so good when they disver that.
but i am a stupid guy, so pretending to be stupid should be easy for me

If you are just interested in getting it back to stock for returning under guarantee to HTC, here is what I would suggest.
(No guarantees, as I haven't had to try this, and won't, for obvious reasons)
Get the stock RUU file from the hero that you have. I would recommend the oldest one that is available for you. (eg. a 1.73 one).
DISCONNECT your phone, and run the exe file(Yes, sounds strange, but bear with me).
Wait till the splash screen for the RUU is up, asking you to accept the EULA etc.
Now browse in my computer to your temp directory (C:\Users\Username\AppData\Temp in Vista/7, C:\Documents And Settings\Username\Application Data\temp in XP)
Sort the folders/files by date modified, and the most recently modified (or one of the most recently modified) folder should contain the RUU stuff. Inside a subfolder is a file called rom.zip. Copy this file to the desktop or another safe place. Once file is copied, close the RUU.
Now get your phone plugged in and booted into fastboot. (hold back + power)
Then use the command
Code:
fastboot flashall C:\Users\Username\Desktop\rom.zip
No guarantees, but it should get you back to the stock recovery, system and boot (NOT HBOOT or SPL, the actual boot.img that android uses to boot the kernel)

can i also flash custom rom with fastboot? to test if something is wrong with the rom?

That would depend on what version of SPL/HBOOT you have. If it is security off, then maybe. Otherwise I doubt it. You usually need an original, HTC signed file to flash using that method.
Feel free to give it a go, but I don't think it would work.

[Q] Stuck on S-Off Screen

Hi, i've been using LeeDroid for a few months now and all has been well, however yesterday my Desire turned itself off and now won't come back on. Each time i try and power it up it freezes at the Alpharev S-Off screen. I went into the menu's with volume down + power, but i can't get into my recovery - it takes me to the same frozen screen as does trying to reboot etc. And i don't think it's being recognized by usb either. So i really don't know what to do now.. is my phone bricked? I was a complete noob before rooting and flashing a custom rom before, so now that i've hit a problem i'm clueless all over again. Any help would be greatly appreciated

can you use fastboot? If so just flash a new recovery and all should be fine... chill out it can be fixed

What would i need for that? That's going into new territory

j3nni said:
What would i need for that? That's going into new territory
Click to expand...
Click to collapse
Can you access recovery? If no can you access bootloader (vol down + power on)

I can get onto the menu with the options 'fastboot, recovery, clear storage and simlock' if that's what you mean? The recovery option takes me back to my frozen alpharev screen, but i can get onto fastboot and after reading around i can get my pc to recognize it from fastboot usb from my pc using cmd.. Am i going the right direction at all? Eek. What i don't get now is the recovery image i'm supposed to use

j3nni said:
I can get onto the menu with the options 'fastboot, recovery, clear storage and simlock' if that's what you mean? The recovery option takes me back to my frozen alpharev screen, but i can get onto fastboot and after reading around i can get my pc to recognize it from fastboot usb from my pc using cmd.. Am i going the right direction at all? Eek. What i don't get now is the recovery image i'm supposed to use
Click to expand...
Click to collapse
Use amon_RA ... Download and flash onto ur phone and ur phone should be fixed
Plenty of guides around man, good way of learning fastboot

to use fastboot you need to download several things. Instead of using fastboot with cmd, I'd just recommend using fastboot commander, which does the job for you. In order to use that however, you will need the adb drivers, and Java SDK.
Once you've got all that, simply boot into fastboot, run "fastboot commander.exe", go into the "misc" tab, wipe Recovery, system, cache, boot, and userdata. Once you've done that download recovery, navigate to the "Hboot, radio & Rec" tab on fastboot commander, select recovery, find the recovery.img you just downloaded, and flash it. Once you've done that just boot into recovery and install any ROM you want.

Thanks for the replies guys. I did what you said to do (using fastboot commander), and when trying to boot into recovery to install my ROM it froze again at the alpharev screen. I'm stuck again now. When the files show up as you turn on into fastboot, i'm getting this..
SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nhh]
No Image or Wrong Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nhh]
No Image or Wrong Image!it's saying my pb****.img files arn't found
which i gather can be normal. Other than that i'm stumped again

j3nni said:
Thanks for the replies guys. I did what you said to do (using fastboot commander), and when trying to boot into recovery to install my ROM it froze again at the alpharev screen. I'm stuck again now. When the files show up as you turn on into fastboot, i'm getting this..
SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nhh]
No Image or Wrong Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nhh]
No Image or Wrong Image!it's saying my pb****.img files arn't found
which i gather can be normal. Other than that i'm stumped again
Click to expand...
Click to collapse
try do a full wipe of everything like I've mentioned before and then a different HBOOT

Okiedoke, how do i use a different hboot? And where do i find one from? At the moment i believe it's 0.93

j3nni said:
Okiedoke, how do i use a different hboot? And where do i find one from? At the moment i believe it's 0.93
Click to expand...
Click to collapse
www.alpharev.nl download a HBOOT and flash it through fastboot. Just make sure to check MD5 (you need a MD5 utility AFAIK)

I'm not sure which one is the right one for my ROM, i'm using LeeDroid.. Sorry for all the questions!

j3nni said:
I'm not sure which one is the right one for my ROM, i'm using LeeDroid.. Sorry for all the questions!
Click to expand...
Click to collapse
For any sense UI ROMs you would use the Sense HBOOT, remember to nandroid backup before you do so! because you might find that you get a bootloop after flashing the HBOOT.
And don't worry about asking questions! it's what we're all here for.
By the way if you don't know what different HBOOTs do: they change the partition sizes for /system /cache and /data. So by using a different HBOOT instead of the stock one you may get more storage for apps etc. if you choose one with a larger /data partition.... if that makes sense

Ok the sense one it is =)
Ah i see! Thanks for explaining cos underneath the nerd in me would have been wondering what it did lol.
Not sure how to get a nandroid done when i can't get into recovery though

I still havn't got anywhere with my problem, if anyone could advise me further i'd really appreciate it, as this is really stressing me out now.
The only screen i can still ever see is a frozen alpharev screen, and i still can't enter recovery. I've cleared everything using fastboot commander and flashed a new recovery which did nothing. Then i took the next advice and flashed a new hboot. The hboot has changed on my hboot menu (vol down + power) but still goes to the frozen alpharev screen when i try to go to recovery or turn the phone on. I then flashed a LeeDroid rom, which came up with an error at the end of it..
"sending 'zip' (173060 KB)... OKAY [ 23.469s]
writing 'zip'... FAILED (remote: not allowed)"
And that's as far as i've got.
Reading further i've been trying to work out how to flash a stock ruu to see if that works. However my phone was a branded Orange UK phone before so there is no ruu for that. So my question is, bearing in mind i can't get into the phone at all, how can i go about downgrading the hboot and installing a htc stock ruu. Can anyone point me to the right files i would need. I really don't know what i'm doing and i think the amount of searching i've been doing is just confusing me further

j3nni said:
I still havn't got anywhere with my problem, if anyone could advise me further i'd really appreciate it, as this is really stressing me out now.
The only screen i can still ever see is a frozen alpharev screen, and i still can't enter recovery. I've cleared everything using fastboot commander and flashed a new recovery which did nothing. Then i took the next advice and flashed a new hboot. The hboot has changed on my hboot menu (vol down + power) but still goes to the frozen alpharev screen when i try to go to recovery or turn the phone on. I then flashed a LeeDroid rom, which came up with an error at the end of it..
"sending 'zip' (173060 KB)... OKAY [ 23.469s]
writing 'zip'... FAILED (remote: not allowed)"
And that's as far as i've got.
Reading further i've been trying to work out how to flash a stock ruu to see if that works. However my phone was a branded Orange UK phone before so there is no ruu for that. So my question is, bearing in mind i can't get into the phone at all, how can i go about downgrading the hboot and installing a htc stock ruu. Can anyone point me to the right files i would need. I really don't know what i'm doing and i think the amount of searching i've been doing is just confusing me further
Click to expand...
Click to collapse
Hi.
As I can see the only way to restore is using a RUU to go back to stock then root and S-Off the phone again.
First: Preparation.
1. If you have a custom HBOOT (e.g.: 6.93.0001) you need first to flash the HBOOT Downgrader (found on alpharev site), then flash the RUU.
2. You will gonna need a Gold Card if your phone was branded.
Second: Starting
1. Make your Gold Card using someone's else phone (it has to be running Android) - the Gold Card is unique per SD Card, not per phone.
2. Use this tool to make the Gold Card: HERE
3. Guide how to make a Gold Card in Linux: HERE
4. get the latest RUU WWE 2.29.405.5. Extract the PB99IMG.zip file from the RUU: here it is how: http://forum.xda-developers.com/showthread.php?t=880268 -2nd post.
5. Reboot in bootloader (Volume-Down + Power)
7. Select fastboot
8. Flash the HBOOT Downgrader (don't forget to check the MD5 of the file you have downloaded from alpharev)
9. Extract the PB99IMG.zip and put it on root of SD Card.
10. Reboot in bootloader (scroll to REBOOT and select)
11. It will automatically load the img and ask you if you want to install
12. Check Yes and follow onscreen progress.
13. Wait untill it finnishes
14. I think it will reboot itself, if not scroll down to the Reboot obtion and press Power button to select.
IMPORTANT WARNING!!!
droidzone said:
Whatever you do, DO NOT turn off the device manually unless the software tells you to. If something goes wrong, dont switch off phone. Keep the phone on while trying a solution. Newer RUUs dont usually wreck a phone, and with a goldcard, you can always recover. But, the flash SHOULD NOT be interrupted by switching off or disconnecting the cable.
Always start with a battery with >50% power (full recommended).
Click to expand...
Click to collapse

Or if you want to go to stock and it is an unbranded phone you can just run ur ruu when the phone is in fastboot
Sent from my HTC Desire using XDA App

Think i may be the happiest girl in the world today lol i finally got it all fixed. I had a bit of trouble making the goldcard as at first my sd card kept saying it needed to be reformatted after, but after formatting it with SD Formatter program rather than Vista's own, it worked. All the rest went without a hitch. Now just gotta root, s-off and grab my new ROM and this past week can all get forgotten about =)
Thankyou so much to everyone that helped!
Incase anyone does read this far, is the procedure still the same as when i first used it back in April.. from here? http://forum.xda-developers.com/showthread.php?t=1016084

It is still the same.

If you like sense -
http://forum.xda-developers.com/showthread.php?t=1054435
░█░ [ROM][28/06] ✰.Reflex S v2.1.7 Gingerbread 2.3.3· ░█░ · |SenseGingerB 2.1+3.0|
You might like it...

[Q] Sorry, Ive read and read.....

Hi Guys,
This is my first post and its only in desperation.
I have a HTC Desire. I upgraded to 2.3.3. After reading how unrevoked doesn't work on this, I created a Goldcard and managed (all on my own) to turn the phone to s /off.
Now Im stuck, many threads explain the process in different ways (as most of them related to pre 2.3.3). So do I load a custom rom onto the Goldcard and flash from there? Also, do I need to install a rollback program first or after?
Really sorry for starting a new thread, but you will see by my profile, Ive been at this for two days .
[Takes cover for flaming session]

im no expert, indeed i have only rooted only a few days ago. I was lucky to have a unlocked phone.
I guess to help the more expert in here is maybe if you detail what now shows on the Bootscreen, eg VOL Down + Power button.
Have you now got a custom Recovery installed, the common one is Clockwork Recovery?
I believe, that Revolutionary.io is able to handle 2.3.3... anyway it what i used to Root, and it installed CWR and from recovery i was able to point it to the ROM zip file and it all installed fine.
Now i didnt need a goldcard so i cant really say if there some additional steps involved first.

u need revolutionary to make s-off, then u can root it flashing the super user zip from the documentation, u don't need the goldcard, it will also install a custom recovery
official revolutionary site: http://revolutionary.io
official revolutionary doc: http://unrevoked.com/rootwiki/doku.php/public/revolutionary
complete guide: http://wiki.rootzwiki.com/index.php/HTC_Desire

don't worry about it, we are all here to help so let me explain some things.
A goldcard is a tool that allows you to use an unbranded RUU on a branded phone, effectively de branding it, as the RUU (Rom Update Utility) ignores the CID (Customer ID) of the device.
To flash different ROM's, you will need to flash something called "recovery", there are many versions, each arguably, or questionably better than the next. In order to flash recovery, you need to download a recovery image.
Download the above file, rename it to "recovery.img" for simplicity, and put it in your C:\
now the flashing process, there are many tools and utilities you can use, but for now, let's just use command prompt as it does not require you to install anything, just as long as you get the commands right. (you'll also need the file I attached [fastboot.exe], just unzip it into your C:\)
Ok, once you've done the steps stated above, turn your phone off. With it off, PRESS AND HOLD the RETURN/BACK key on your phone, and while still holding it, press the POWER key. This will boot you into "fastboot" mode.
Plug your phone in via USB to your PC.
Open command prompt (start menu, accessories, command prompt)
type the following:
Code:
cd\
fastboot flash recovery recovery.img
Congratulations, you have now flashed recovery. This now allows you to flash ROM's.
Put whatever ROM you would like on your SD-CARD, I recommend CyanogenMod (for No Sense) or MIUI (For something completely different) or RCMixS for Sense (sense 2.1) (all comes with preference)
To boot into recovery, boot into bootloader, (while powered off, press and hold VOLUME DOWN, and POWER), use the volume keys to navigate, and the power key to select. Navigate to RECOVERY and hit power.
When you are booted into recovery, before flashing a new rom IT IS VERY IMPORTANT TO BACK UP!!. You can do this in the "backup and restore" menu.
Once you are backed up, go to "mounts and storage" and use "format [partition]" option, to format boot, system, and userdata.
Then, go to "flash zip from sdcard", and find the ROM you have chosen, and wait for it to finish flashing.
Good luck to you

Wow guys, cant thank you enough
I actually had a small amount of brain oozing out of my ears at one point Thanks for the custom info, like I said, the tuts are excellent, but being new, they are a bit irrelevant if you half way through the process. Trust me to upgrade to an 'unrootable' system a week before I decide to root it
I will remove my flame-proofing now
Thanks again
PP

@bortak
Thats only when he have s-off...If i not wrong he have the stock 2.3.3 with no root an s-on
EDIT: nevermind..i didn't read the post properly..

Hi guys
Im getting an error on fastboot :
This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem.
Click to expand...
Click to collapse
Ive tried a different version ,but that came up with the same error. I have android SDK installed in the same directory, is this interfering with it?
Thanks again
PP

palm_pilot said:
Hi guys
Im getting an error on fastboot :
Ive tried a different version ,but that came up with the same error. I have android SDK installed in the same directory, is this interfering with it?
Thanks again
PP
Click to expand...
Click to collapse
Okay, put "fastboot.exe" in c:\android-sdk\platform-tools\
and then before issuing fastboot commands, type:
Code:
cd c:\android-sdk\platform-tools\
this *should* fix it for you

Hi Guys,
This isnt going very well for me
Ive downloaded the .img file tried to flash it. Re-downloaded another copy (in case it was corrupt) , tried to flash that. Changed the file name back to the original (along this command text) to see if it was a recognition issue
On all occasions Im geting :
error: cannot load 'recovery-clockwork-2.5.0.7-bravo.img'
Click to expand...
Click to collapse
Any ideas fellas?
PP

Maybe download 'recovery-clockwork-2.5.0.7-bravo.img' and then select that from unrevoked ?

palm_pilot said:
Hi Guys,
This isnt going very well for me
Ive downloaded the .img file tried to flash it. Re-downloaded another copy (in case it was corrupt) , tried to flash that. Changed the file name back to the original (along this command text) to see if it was a recognition issue
On all occasions Im geting :
Any ideas fellas?
PP
Click to expand...
Click to collapse
Please tell me what code you put before getting that error - or the whole cmd from start to getting that error

BigMrB said:
Please tell me what code you put before getting that error - or the whole cmd from start to getting that error
Click to expand...
Click to collapse
Hi
Im using :
\cd (enter)
Then :
android-sdk\platform-tools\fastboot flash recovery recovery.img
I have revolution installed, can I flash from within this ie. loading the image to the SD and running from within the phone itself?
ATB
PP

cd C:/android-sdk/platform-tools/
fastboot flash recovery recovery.img
(providing you changed the name of your recovery to recovery.img)

[Q] MIUI Rom gone wrong

okay so heres what happened.
I have an international htc one x that is indeed rooted with no roms installed.
I did create a back up and then tried to install the MIUI rom (but I dont really know where that is on my phone. I know I made one with rom manager. I dont have any backups on my computer though)
It worked, however, it didnt have wifi or data signals so i went back to try again.
I opened my bootloader screen. For the record, it is unlocked and hboot is version 1.73 if that helps.
I wiped cashe/data/delvic everything and even factory reset and installed the MIUI RD rom now hoping it would have a difference.
The darn thing got stuck on the MIUI bootloader for hours.
I did the same thing again a few times, sometimes in different orders and then it passed on and another screen came saying 'starting apps'. That got stuck for hours too.
Now I don't have any other roms on my phone, just the MIUI RD. The original miui just vanished too, i dont see it anymore. Also, when I put my USB wire to the phone and connect it to the pc, I cant transfer newer files into it. So this is all I have access to on my phone apparently.
I tried flashing a boot.img and a couple kernels but no luck. I've been trying to do this for all day and this is my first time so I don't know much about it.
I've been googling and somethings say to open cmd and type but i keep getting 'fastboot is not recognized as an internal or external command'
Currently, its not stuck at either the MIUI screen or the Starting Apps. but just the HTC logo screen and not going past.
I don't really want to install any new roms considering i've worked really hard to get this to work and I really want it now more so.
How do i fix this? I want to use this rom.

flash philz recovery (http://forum.xda-developers.com/showthread.php?t=2240646), usb mounting should work on that, then:
steps to install ROM
1. bootloader version should be 1.3x
2. copy ROM to SD Card
3. copy boot.img INCLUDED in the ROM zip to fastboot folder
4. flash the boot.img in fastboot
5. in recovery, wipe system/data/cache/everything
6. flash rom
7. restart

but how exactly do i put it on my phone? my computer isnt detecting my phone when i connect it? im sorry im not exactly an expert on this.

Go to recovery - mounts and storage - hook up the usb cable - tap the last option in the mounts and storage list and wait a few minutes. It won't be mounted instantly

ok i flashed the philtz recovery but when i flash the boot.img it says:
Finding update package
Opening update package
Installing update
installation aborted
for reference: http://forum.xda-developers.com/showthread.php?t=1957490
thats the rom i used and i flashed the boot.img flasher thats right above the download link
edit: also i tried just flashing the rom again and im still stuck on the HTC screen.
its not even going to the miui screen or starting apps anymore. :[

Boot.img must be flashed via fastboot. Not via recovery !

ok, i looked up how to fastboot, downloaded sdk files and i moved the boot.img into the fastboot folder and i opened command prompt there and wrote fastboot flash boot boot.img but i keep getting:
'fastboot is not recognized as an internal or external command'
what did i miss?
EDIT: ok, so the fastboot folder i got from the page didnt work so i used a different fastboot folder, dragged the .boot there and now it worked! finally passed the screen and wifi is connecting!
thank you!

Good, thanks to @tomascus. He summed it up real nice
Cheers

[Solved] Stuck on HTC Logo after flashing firmware update

This is pretty much my first time doing such things in my phone. I rooted my phone and installed ARHD 11.2 without any trouble following the instructions. When ARHD released 21.0, I tried flashing the ROM but my WiFi stopped working which I did my research and found out that it requires a firmware update (3.28.xxxx) to work. So I tried FireWater which didn't work for some reason and bought SunShine which work out as expected and my M8 is now S-OFF & set my CID to 11111111.
Now, here comes the problem. I flashed 3.2.8.401.7 firmware downloaded from ARHD blog and it returns a SUCCESSFUL but with an ERROR 90, which I also did search and said that I just have to flash the firmware again without reboot in between. Now when I boot up my phone, it's stuck on the HTC Logo with an android text below it and doesn't boot up. I went into the bootloader and tried going into recovery but it went to a black screen with and phone with a red triangle and exclamation mark in between. I erased the cache with fastboot erase cache but still didn't work. Also, I noticed that on the top of my bootloader, it says "*** Software status: Modified ***". I don't know if that is supposed to be there. I remembered TAMPERED banner was supposed to be there. My M8 is unlocked as well.
TWRP 2.8.1.0
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.21.21331147A1.19_2G
I followed this guide: VomerGuides [M8]: Bootldr Unlock, S-OFF, SuperCID, Firmware Upgrade & Custom Recovery
EDIT: Solved thanks to lukes91
Solution: Flash custom recovery and then flash ROM via ext_sd and you should be good to go.

Serenity13 said:
This is pretty much my first time doing such things in my phone. I rooted my phone and installed ARHD 11.2 without any trouble following the instructions. When ARHD released 21.0, I tried flashing the ROM but my WiFi stopped working which I did my research and found out that it requires a firmware update (3.28.xxxx) to work. So I tried FireWater which didn't work for some reason and bought SunShine which work out as expected and my M8 is now S-OFF & set my CID to 11111111.
Now, here comes the problem. I flashed 3.2.8.401.7 firmware downloaded from ARHD blog and it returns a SUCCESSFUL but with an ERROR 90, which I also did search and said that I just have to flash the firmware again without reboot in between. Now when I boot up my phone, it's stuck on the HTC Logo with an android text below it and doesn't boot up. I went into the bootloader and tried going into recovery but it went to a black screen with and phone with a red triangle and exclamation mark in between. I erased the cache with fastboot erase cache but still didn't work. Also, I noticed that on the top of my bootloader, it says "*** Software status: Modified ***". I don't know if that is supposed to be there. I remembered TAMPERED banner was supposed to be there. My M8 is unlocked as well.
TWRP 2.8.1.0
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.21.21331147A1.19_2G
I followed this guide: VomerGuides [M8]: Bootldr Unlock, S-OFF, SuperCID, Firmware Upgrade & Custom Recovery
Click to expand...
Click to collapse
it looks like you still have stock recovery... flash a custom one and try to boot, but you might need to reflash the rom... let me know

lukes91 said:
it looks like you still have stock recovery... flash a custom one and try to boot, but you might need to reflash the rom... let me know
Click to expand...
Click to collapse
Thanks lukes91, I noticed that some people said that the Red triangle with a ! mark on it means that it's Stock Recovery. I didn't know why my TWRP got wiped off when I flashed the firmware. I'll give it a try and update this post.
edit: I'm afraid that for some odd reason. I can't get my phone connected with ADB. It's just says device not found when bootloader says FASTBOOT USB. I reinstalled the drivers from HTC Sync and tried it with HTC Sync installed and uninstalled but I still can't get it to work. I'm plugged into USB 2.0 port.
edit2: I tried plugging in my phone while it's stucked on the HTC logo. My computer detects the Phone and opens up the Internal Storage from my Computer. I have bunch of folders inside which is empty and about 0.3GB storage are used. I'm afraid that it might have to do with the USB Debugging option is off which I do not know how to get it on in bootloader.
edit3: Okay I managed to get TWRP flashed finally. How do I get the ARHD 21.1 ZIP into the Phone? I tried ADB Sideload but it just gets stuck at "Starting ADB Sideload feature..." I tried entering the command in CMD and it said Cannot read file "rom.zip"

Serenity13 said:
Thanks lukes91, I noticed that some people said that the Red triangle with a ! mark on it means that it's Stock Recovery. I didn't know why my TWRP got wiped off when I flashed the firmware. I'll give it a try and update this post.
edit: I'm afraid that for some odd reason. I can't get my phone connected with ADB. It's just says device not found when bootloader says FASTBOOT USB. I reinstalled the drivers from HTC Sync and tried it with HTC Sync installed and uninstalled but I still can't get it to work. I'm plugged into USB 2.0 port.
edit2: I tried plugging in my phone while it's stucked on the HTC logo. My computer detects the Phone and opens up the Internal Storage from my Computer. I have bunch of folders inside which is empty and about 0.3GB storage are used. I'm afraid that it might have to do with the USB Debugging option is off which I do not know how to get it on in bootloader.
edit3: Okay I managed to get TWRP flashed finally. How do I get the ARHD 21.1 ZIP into the Phone? I tried ADB Sideload but it just gets stuck at "Starting ADB Sideload feature..." I tried entering the command in CMD and it said Cannot read file "rom.zip"
Click to expand...
Click to collapse
put the rom zip inside ext_sd and flash from there
it's the easiest way...

lukes91 said:
put the rom zip inside ext_sd and flash from there
it's the easiest way...
Click to expand...
Click to collapse
Best answer :good:

lukes91 said:
put the rom zip inside ext_sd and flash from there
it's the easiest way...
Click to expand...
Click to collapse
Alright I'll give it a try. I did try it and placed it in the internal storage but the file went missing after I rebooted into recovery. I'll try your directory instead and give a reply asap.
I actually felt embarrassed on that and my stupidity lol.
edit: Thanks very much! I flashed ARHD 21.1 and now it worked. Now I feel more embarrassed after the ext_sd incident...that actually works.

Serenity13 said:
Alright I'll give it a try. I did try it and placed it in the internal storage but the file went missing after I rebooted into recovery. I'll try your directory instead and give a reply asap.
I actually felt embarrassed on that and my stupidity lol.
edit: Thanks very much! I flashed ARHD 21.1 and now it worked. Now I feel more embarrassed after the ext_sd incident...that actually works.
Click to expand...
Click to collapse
Great! Glad i helped
Sent from here

Serenity13 said:
I noticed that some people said that the Red triangle with a ! mark on it means that it's Stock Recovery. I didn't know why my TWRP got wiped off when I flashed the firmware.
Click to expand...
Click to collapse
If the firmware zip contains stock recovery, of course its going to overwrite TWRP with stock recovery. Sometimes, folks here will intentionally remove stock recovery from the firmware zip (for the express purpose of preventing custom recovery from being wiped when flashing the firmware). But as it comes with an OTA, it will contain stock recovery.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
Serenity13 said:
edit3: Okay I managed to get TWRP flashed finally. How do I get the ARHD 21.1 ZIP into the Phone? I tried ADB Sideload but it just gets stuck at "Starting ADB Sideload feature..." I tried entering the command in CMD and it said Cannot read file "rom.zip"
Click to expand...
Click to collapse
I know you solved your issue another way. But the adb syntax needs to contain the actual file name, in place of "rom.zip" (with no quotes). This is assuming from the error message that you did not actually rename the file to "rom.zip"(which is another way to do it).

redpoint73 said:
If the firmware zip contains stock recovery, of course its going to overwrite TWRP with stock recovery. Sometimes, folks here will intentionally remove stock recovery from the firmware zip (for the express purpose of preventing custom recovery from being wiped when flashing the firmware). But as it comes with an OTA, it will contain stock recovery.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
I know you solved your issue another way. But the adb syntax needs to contain the actual file name, in place of "rom.zip" (with no quotes). This is assuming from the error message that you did not actually rename the file to "rom.zip"(which is another way to do it).
Click to expand...
Click to collapse
Well I did rename the original name(Android_Revolution_HD-One_M8_21.1.zip) to rom.zip since it's way long and it didn't work the first time I entered adb side load Android_Revolution_HD-One_M8_21.1.zip. I renamed to rom.zip just to see whether if it works but I still received the same error. It could be something wrong with the ADB Sideload. It got stuck at "Starting ADB Sideload feature..." but "adb devices" listed the device with sideload tag on it. Thanks to lukes91, the method he posted above, which was the most simplest method that I should have done at the first place works perfectly.

Serenity13 said:
It could be something wrong with the ADB Sideload.
Click to expand...
Click to collapse
Could be, I've found adb sideload to be finicky, and adb push to be more reliable. Although sideload is good to have in your bag of tricks "just in case". And of course the method you eventually used (putting it on the removable SD) works, as well.
The other common cause for the error message "cannot read file" is that the file is accidentally named rom.zip.zip due to the user not realizing they have the Windows option selected to hide file extensions (and erroneously adding ".zip" to the file name). But as you loaded and flashed the file successfully by putting it on the removable SD, this likely is not the case either.
You had the ROM zip in the same folder as your adb executable, right (when trying to sideload)? An obvious thing, probably. But just asking, since its sometimes the seemingly obvious things that trip us up.

redpoint73 said:
Could be, I've found adb sideload to be finicky, and adb push to be more reliable. Although sideload is good to have in your bag of tricks "just in case". And of course the method you eventually used (putting it on the removable SD) works, as well.
The other common cause for the error message "cannot read file" is that the file is accidentally named rom.zip.zip due to the user not realizing they have the Windows option selected to hide file extensions (and erroneously adding ".zip" to the file name). But as you loaded and flashed the file successfully by putting it on the removable SD, this likely is not the case either.
You had the ROM zip in the same folder as your adb executable, right (when trying to sideload)? An obvious thing, probably. But just asking, since its sometimes the seemingly obvious things that trip us up.
Click to expand...
Click to collapse
Yep I had the ROM zip at the same folder as the adb executable. I did tried both rom.zip and rom.zip.zip in case it was the extension setting mistake. Still it was a happy ending. I got my firmware and ARHD updated. It feels so good to be updated. :good: