Develop Bugs

Original htc recovery

I rooted and flashed clockwork orange. Now I want to revert back to complete stock recovery and all. How do I do this? I don't know if this is the right area for this topic.
Sent from my PC36100 using XDA App

flash the RUU .exe which will load the stock system, recovery, kernel and everything.

If I were to restore my EVO to stock, then run the official Sprint OTA update that just came out, will I still be able to root it? Or does the new update block Toast's root method?

Clockwork ORANGE??? lmao! I loved the movie though, loved it... U mean clockwork mod right? Oh yea just get the stock RUU.
Sent telepathically via my Evo.
-_-

driguez said:
Clockwork ORANGE??? lmao! I loved the movie though, loved it... U mean clockwork mod right? Oh yea just get the stock RUU.
Sent telepathically via my Evo.
-_-
Click to expand...
Click to collapse
The second OTA breaks RUU bootloader according to reports.

I tried the ruu and when it tries to open the bootloader it fails.
Sent from my PC36100 using XDA App

I get stuck at waiting for bootloader
Sent from my PC36100 using XDA App

clue1968 said:
I tried the ruu and when it tries to open the bootloader it fails.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
clue1968 said:
I get stuck at waiting for bootloader
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
My same pain....

So what other options do we have then?
Sent from my PC36100 using XDA App

clue1968 said:
I rooted and flashed clockwork orange.
Click to expand...
Click to collapse
This is EXACTLY what I say in my head when speaking about Clockwork Mod.

I was able to get past waiting for bootloader by putting the phone in bootloader mode before running the RUU. But it gives an error message saying the bootloader version is incorrect.

dammit all i want is to go back to stock no root no nand because 4g is broken with these new ota rooted crap that came out today!

Can someone post the stock recovery or a method of going back to a stock recovery pleaseeeeeee
Sent from my PC36100 using XDA App

The steps below worked for me. I had the latest clockwork,dc rom and The latest rooted ota updates installed.
http://www.htc.com/us/support/evo-sprint/downloads/
I unplugged/plugged my phone into the computer a couple times,switched to htc sync mode when it asks what type of usb connection I wanted(to install more driver updates), and did 2 reboots on my computer (windows 7 ultimate x86) to get all the drivers updated/installed and working as they should,
then I just turned off the phone, held volume down and held down power button to get to bootloader,
then I pressed Power button one more time to get to the menu where I can reboot bootloader,
then I rebooted bootloader once or twice BEFORE the unrooting process for good measure.
Stock RUUs
http://shipped-roms.com/shipped/Supersonic/
RECAP
Download and install HTC Sync Update http://www.htc.com/us/support/evo-sprint/downloads/ (if you already have it installed then click the repair option, or better yet uninstall your current one even if it is the same one, reboot your computer and then install this one again, all for good measure.)
Download either one of the RUU Stock Roms, I would do the first just to be safe http://shipped-roms.com/shipped/Supersonic/
Plug your phone into your computer, make sure ALL Drivers install properly if any, you may already have drivers installed, but double check, switch to HTC Sync mode and let it install any extra drivers, then turn off your phone and start it in bootloader (Hold Volume Down +Power button) Reboot your computer for good measure too, to make sure everything has been properly installed.
Then you can finally double click (right click run as admin imo) RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe and start the unrooting process, good luck!

Will this work if I have clockwork mod as my recovery?
Sent from my PC36100 using XDA App

clue1968 said:
Will this work if I have clockwork mod as my recovery?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
if you have clockwork, you still have system access and should beable to use any of those RUU's to downgrade back to stock.
i did the same thing and now im back at stock and have latest update running stock rom.
put phone into bootloader mode, then run RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253.exe
follow steps. and then you should have stock evo.
check for OTA updates and install it.
wait 10-15 minutes before rebooting after the update completes..
mine kept saying there was an update. which there wasnt, it just kept trying to download same update.

Yes it should I had clockwork too.
clue1968 said:
Will this work if I have clockwork mod as my recovery?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

Yes it did work....thank you to everyone..
Sent from my PC36100 using XDA App

@Tundricles i cannot use ruu to unroot because i don't have the HTC Drivers and before i re downloaded HTC SYNC i had some drivers just not ADB driver after downloading the program i have no drives at all !!!!!!!
is there a way i can download and manually install the htc evo drivers!!
im back to normal i can read my sd card and i can connect to pc thank you all

same problem
im on fresh 1.0.1 ive downgraded fresh wiped everything tried different ruu and nothing so far

Bricked or not bricked?

I had an issue with my phone a couple of weeks ago where I'm only able to the bootloader screen and the fastboot screen. Fortunately, I got a replacement EVO 3 days later but I'm still trying to get my old phone up and running. But after trying everything I can find, still nothing.
So my question is, when do I say that the phone is officially bricked?
Sent from my PC36100 using Tapatalk

If you can get to the bootloader screen, then you be able to flash an image to get you phone working again.
Sent from my Decked Out HTC EVO with Tapatalk!

dwelder said:
If you can get to the bootloader screen, then you be able to flash an image to get you phone working again.
Sent from my Decked Out HTC EVO with Tapatalk!
Click to expand...
Click to collapse
Believe me, I've tried everything, from using amon ra PC36IMG.zip in the bootloader. It updates successfully then still no recovery.
I've tried the ruu via bootloader, it updates successfully. It still bootloops continually.
I ran Football's recent 4.54 ruu in fastboot successfully and still nothing.
Everything I try, it continues to bootloop.
Sent from my PC36100 using Tapatalk

Were you using CM7 before your phone started bootlooping?

Concordium said:
Were you using CM7 before your phone started bootlooping?
Click to expand...
Click to collapse
10/14 miui with tiamat 4.1 sbc.
Sent from my PC36100 using Tapatalk

andygu3 said:
10/14 miui with tiamat 4.1 sbc.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Well CM7 is the ROM typically being run when phones enter the bootloop of death. However, I've heard that there have been a couple of MIUI ROMs that have entered the bootloop of death as well. If you've flash a recovery and still cant enter it and tried to fully unroot then you might have to take it to Sprint. I'd make sure that you're fully unrooted before doing so. I would also recommend removing your SD card so that they cant try to deny you based on rooting the phone. Just a precaution.

andygu3 said:
Believe me, I've tried everything, from using amon ra PC36IMG.zip in the bootloader. It updates successfully then still no recovery.
I've tried the ruu via bootloader, it updates successfully. It still bootloops continually.
I ran Football's recent 4.54 ruu in fastboot successfully and still nothing.
Everything I try, it continues to bootloop.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Have you tried flashing the images via fastboot?

Concordium said:
Well CM7 is the ROM typically being run when phones enter the bootloop of death. However, I've heard that there have been a couple of MIUI ROMs that have entered the bootloop of death as well. If you've flash a recovery and still cant enter it and tried to fully unroot then you might have to take it to Sprint. I'd make sure that you're fully unrooted before doing so. I would also recommend removing your SD card so that they cant try to deny you based on rooting the phone. Just a precaution.
Click to expand...
Click to collapse
Fortunately, I already got a new phone but the reason I didn't take it into Sprint was because it still was S-off. Since I can't get to recovery, how would I get s-on?
And now that I ran stock ruu's, is it a possibility that the PC36IMG.zip's won't be recognized anymore?
I'd love to get this phone running again and let my 7 year play some games on it but I'm afraid I may be sol!!
Sent from my PC36100 using Tapatalk

teh roxxorz said:
Have you tried flashing the images via fastboot?
Click to expand...
Click to collapse
Please elaborate! Not sure what to flash in fastboot?
Sent from my PC36100 using Tapatalk

andygu3 said:
Please elaborate! Not sure what to flash in fastboot?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.

andygu3 said:
Fortunately, I already got a new phone but the reason I didn't take it into Sprint was because it still was S-off. Since I can't get to recovery, how would I get s-on?
And now that I ran stock ruu's, is it a possibility that the PC36IMG.zip's won't be recognized anymore?
I'd love to get this phone running again and let my 7 year play some games on it but I'm afraid I may be sol!!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Here you go
http://forum.xda-developers.com/showpost.php?p=18399552&postcount=2

teh roxxorz said:
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.
Click to expand...
Click to collapse
Thanks for the info! I will give this a go.
I keep reading that the NV got corrupted some how, is there any way to correct this or flash something in fastboot?
Again thanks for your input, much appreciated!
Sent from my PC36100 using Tapatalk

andygu3 said:
Thanks for the info! I will give this a go.
I keep reading that the NV got corrupted some how, is there any way to correct this or flash something in fastboot?
Again thanks for your input, much appreciated!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
No problem.
And if the NV is corrupted, its toast. It was a flaw with the evo when you bought it, and now its decide to tap out. At that point you'd have to take it to sprint, as the NV is part of flash memory and its locked.

Concordium said:
Here you go
http://forum.xda-developers.com/showpost.php?p=18399552&postcount=2
Click to expand...
Click to collapse
Thanks for this, hopefully if I can't get the boot.img working from ruu, I will do this!
Sent from my PC36100 using Tapatalk

andygu3 said:
Thanks for this, hopefully if I can't get the boot.img working from ruu, I will do this!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Oh crap I forgot you were the one having the issue with the boot.img. If you can't get that to work then the post I gave you will most likely not work either. It's worth a try....but I doubt it.

teh roxxorz said:
No problem.
And if the NV is corrupted, its toast. It was a flaw with the evo when you bought it, and now its decide to tap out. At that point you'd have to take it to sprint, as the NV is part of flash memory and its locked.
Click to expand...
Click to collapse
Well sh**, that's a downer! If this is the case, I'm definitely sol! But hopefully I can get something out of the phone but I seriously doubt it!
Thanks guys for your input, again much appreciated. I will report back if I have any breakthrough!!
Sent from my PC36100 using Tapatalk

Im having the same issue
bootloop and the phone was using CM7. I was able to get to boot loader menu but can not get to recovery.
Tried to add recovery image no dice...now the phone will only charge and not boot

teh roxxorz said:
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.
Click to expand...
Click to collapse
No luck!
I know someone posted the EVO Brick_fix, I believe cutthroat but since no PC36IMG.ZIP is being recognized on my sdcard. I may officially say my phone is toast.
Any other suggestions are welcome!
Sent from my PC36100 using Tapatalk

Is this normal? I can run any stock ruu and my hboot changes! I was on 2.16 but I ran the froyo ruu and now I'm back to 2.10
Any thoughts?
Sent from my PC36100 using Tapatalk

andygu3 said:
Is this normal? I can run any stock ruu and my hboot changes! I was on 2.16 but I ran the froyo ruu and now I'm back to 2.10
Any thoughts?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Did you unbrick your EVO
I tried to use unbrick method and now phone will not boot at all
It just stays at black screen and vibrates once after pressing the power button

Major problems! Phone completely bricked nothing is fixing! Please help

I pulled my phone out of my pocket it and saw that it was on the HTC boot screen. It stayed like the for a while so i shut it down using Power, Volume UP&Down.
I tried to boot again but was freezing at the HTC boot screen.
I booted into recovery and it said it couldnt load /cach/x (command and log and last_log)
Ive tried everything from flashing RUU to new HBOOTS, nothing is working.
Now my laptop keeps saying a USB port is malfunctioning everytime i plug the phone in.
Im two seconds away from smashing this with a sledgehammer.
I was running Aeroevan's Unofficial CM10 Jelly Bean With the v12 Kernel w/ Video Drivers.

Have you tried the pg32img in bootloader?
Sent from my DROID SPYDER using Tapatalk 2

jamminjon82 said:
Have you tried the pg32img in bootloader?
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Yes, when i go to install it, it does a few things.
It p****s the zip
bypasses the bootload
and freezes at boot saying updating and at the bottom is says can not roll back hboot version.
Its been at this screen for about 45 minutes THIS TIME

May have to try one of the methods of bringing it back to stock. There is a good tutorial on rootzwiki. I'll post the link in a sec..
EDIT: Here you go. Follow everything to the T.
http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Sent from my Incredible 2 using Tapatalk 2

dirtsky said:
May have to try one of the methods of bringing it back to stock. There is a good tutorial on rootzwiki. I'll post the link in a sec..
EDIT: Here you go. Follow everything to the T.
http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
The only issue now is I only have FastBoot Support but no ADB support. I have no idea why but my phone only shows up under fastboot devices and not adb devices. so i have no idea how to use that guide

The Inc 2 ports often go bad. Try wiggling and plugging it in not all the way. Also sometimes had to push on the cable and hold for it to recognize the USB.
________________________________
Easy as 3.1415926536

If your phone can be used via fastboot it should be able to via adb. Like CS said, It might be a bad micro-usb slot. I would try wiggling it to see if that helps. Being able to access fastboot means its not bricked, it just might be a hardware failure.

sjpritch25 said:
If your phone can be used via fastboot it should be able to via adb. Like CS said, It might be a bad micro-usb slot. I would try wiggling it to see if that helps. Being able to access fastboot means its not bricked, it just might be a hardware failure.
Click to expand...
Click to collapse
I did??
Sent from Kangdemnation

CondemnedSoul said:
I did??
Sent from Kangdemnation
Click to expand...
Click to collapse
What happens when you type
adb devices?
what about fastboot devices.
If you can do one you should be able to do the other, but i'm not sure how you have your adb folders setup. Its a weird error. Can you explain your setup some more.

sjpritch25 said:
What happens when you type
adb devices?
what about fastboot devices.
If you can do one you should be able to do the other, but i'm not sure how you have your adb folders setup. Its a weird error. Can you explain your setup some more.
Click to expand...
Click to collapse
When i type in Fastboot device my phone shows up, but when i type in adb devices it doesnt. i set up the android sdk and assorted tools the way i always have because i use them for development in eclipse, but ive never had a problem with adb before.

sjpritch25 said:
What happens when you type
adb devices?
what about fastboot devices.
If you can do one you should be able to do the other, but i'm not sure how you have your adb folders setup. Its a weird error. Can you explain your setup some more.
Click to expand...
Click to collapse
this is what it should look like.

CondemnedSoul said:
I did??
Sent from Kangdemnation
Click to expand...
Click to collapse
Lol I think he had just looked at your contact picture. They look very similar at a glance

If your phone isn't booting past HTC screen it won't usually show up as an adb device.
Are you s-off?
Have you tried the return to stock that I posted?
http://forum.xda-developers.com/showthread.php?t=1599767
This does not change hboot version so you shouldn't get that error but will put un-rooted stock and stock recovery back on your phone. Then you can install custom recovery, flash su bins and be ready to go again...... hopefully

CondemnedSoul said:
If your phone isn't booting past HTC screen it won't usually show up as an adb device.
Are you s-off?
Have you tried the return to stock that I posted?
http://forum.xda-developers.com/showthread.php?t=1599767
This does not change hboot version so you shouldn't get that error but will put un-rooted stock and stock recovery back on your phone. Then you can install custom recovery, flash su bins and be ready to go again...... hopefully
Click to expand...
Click to collapse
Everything i try keeps freezing in the bootloader screen when i go to install any RUU or image file or zip including that PG32IMG thing or whatever.
My phone recognizes it in fastboot but not adb.
I am S-Off. I rooted the phone the day i got it 6 months ago and have flashed a new rom weekly. never had a problem like this before.

dirtsky said:
May have to try one of the methods of bringing it back to stock. There is a good tutorial on rootzwiki. I'll post the link in a sec..
EDIT: Here you go. Follow everything to the T.
http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
The download links in this do not work or else id try that too.

Try it
Try putting a random rom on the Sd of the phone then try and get it to root ClockWork through the volume down method. Wipe and run the other Rom. try it ive been stuck before and it sounds something like this

flydoug9 said:
Try putting a random rom on the Sd of the phone then try and get it to root ClockWork through the volume down method. Wipe and run the other Rom. try it ive been stuck before and it sounds something like this
Click to expand...
Click to collapse
Yes i would try this except ClockWorkMod isnt working when i attempt to boot into it. It starts to load then freezes.

I'm having this very same issue. Turned the phone off Friday night, turned it on Saturday morning to the white HTC screen. Stock RUUs don't do anything.
Sent from my Ally using xda app-developers app

TheValk said:
I'm having this very same issue. Turned the phone off Friday night, turned it on Saturday morning to the white HTC screen. Stock RUUs don't do anything.
Sent from my Ally using xda app-developers app
Click to expand...
Click to collapse
Yeah i've been trying everything. When i install any RUU or anything it keeps getting hung up at recovery and i tried flashing that seperately and that isnt doing anything.

Have you tried doing anything in fast boot like wiping data and cache?
Sent from my Incredible 2 using xda premium

[Q] "Error: Device not found" in adb.

Hello friends,
I'm trying to install cyanogenmod and no matter what I do I consistently get the device not found error when I try to use "adb push cm-10.2.0-RC1-endeavoru.zip \sdcard\"
I know that in the cyanogenmod install guide it says it's probable that it's a driver issue. I've looked around for a good 2 hours trying to find what it might be, so I've tried reinstalling htc sync, I've tried uninstalling htc sync and using koush's universal adb driver, but nothing seems to work.
When using "adb devices" it doesn't give me the error, it just gives me "List of devices attached" which is empty. (I'm not sure if this is what it is supposed to do though)
Attached img of what I've been doing.
USB debugging is on. It's been automatically turned on whenever I connect it to my PC since I updated to 4.2.2 anyway.
I have no idea where to go from here. Any help would be appreciated.

Aireon said:
Hello friends,
I'm trying to install cyanogenmod and no matter what I do I consistently get the device not found error when I try to use "adb push cm-10.2.0-RC1-endeavoru.zip \sdcard\"
I know that in the cyanogenmod install guide it says it's probable that it's a driver issue. I've looked around for a good 2 hours trying to find what it might be, so I've tried reinstalling htc sync, I've tried uninstalling htc sync and using koush's universal adb driver, but nothing seems to work.
When using "adb devices" it doesn't give me the error, it just gives me "List of devices attached" which is empty. (I'm not sure if this is what it is supposed to do though)
Attached img of what I've been doing.
USB debugging is on. It's been automatically turned on whenever I connect it to my PC since I updated to 4.2.2 anyway.
I have no idea where to go from here. Any help would be appreciated.
Click to expand...
Click to collapse
mount the sdcard inside the recovery and copy the rom

Mr Hofs said:
mount the sdcard inside the recovery and copy the rom
Click to expand...
Click to collapse
Sorry, I'm completely new to this. Do you mean normal recovery from bootloader or a custom recovery that I should of done but completely skipped due to my ignorance? (I also haven't unlocked bootloader so I'm assuming that's a misstep as well?)
Because all I get when I do the normal recovery is a picture of a phone with a red triangle and "!" combo.
Thanks

Yeah to install a custom rom it's mandatory to unlock the bootloader and install a custom recovery. And what i can tell from your post it that you really are a novice on things. Some tips ?
1: never start without a full battery
2: learn fastboot + commands
3: always make a stock rom nandroid backup before starting flashing !
Read up in this forum. Under the stickys there are some nifty guides. If you have questions after that just ask here.

Mr Hofs said:
Yeah to install a custom rom it's mandatory to unlock the bootloader and install a custom recovery. And what i can tell from your post it that you really are a novice on things. Some tips ?
1: never start without a full battery
2: learn fastboot + commands
3: always make a stock rom nandroid backup before starting flashing !
Read up in this forum. Under the stickys there are some nifty guides. If you have questions after that just ask here.
Click to expand...
Click to collapse
Thanks for the tips!
After a while of toiling to try and unlock the boot loader manually and getting stuck at the load error for Unlock_code.bin, I found Hasoon2000's tool, so he is my god for now.
My query that I have is, Do I need a custom recovery like ClockWorkMod to create a nandroid back up? Because all I get when I try to go into recovery from the bootloader is this (img attached, not mine because I don't have another camera in the house but luckily I managed to find one on google img.)
I can't find anything saying that I do need a custom recovery, but then again it's not working when I try without one, so I'm not too sure where to go from here.
Thanks again

Please read carefully what i write, i know exactly what to do !
You need a custom recovery !

Sorry to be back again so soon but I'm stuck again, haha.
When I try to flash cwm I get "error: cannot load 'recovery.img'". When I try to use Hasoon2000's tool kit to do it for me it doesn't work either as it just says device not found and in the second command window it says that it can't load it's .img file either.
The recovery.img is in the same location as fastboot. My phone is in Fastboot in bootloader.
I'm typing "r:\Android\adt\sdk\platform-tools\fastboot flash recovery recovery.img". Trying to auto complete recovery.img using tab does nothing (if that might indicate some sort of problem).
The only thing I can think of is that the MTP drivers never install properly but I read on this forum that it shouldn't affect fastboot.

If you are on windows you must select camera as usb option
Sent from my GT-I8190 using xda app-developers app
---------- Post added at 02:25 AM ---------- Previous post was at 02:22 AM ----------
I mean windows 8
Sent from my GT-I8190 using xda app-developers app

robindebruin said:
If you are on windows you must select camera as usb option
Sent from my GT-I8190 using xda app-developers app
---------- Post added at 02:25 AM ---------- Previous post was at 02:22 AM ----------
I mean windows 8
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Ah, I probably should of said it earlier, sorry. I'm using windows 7.

And did you install java jdk and driver
Sent from my GT-I8190 using xda app-developers app

robindebruin said:
And did you install java jdk and driver
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
If javaj jdk is just normal java then yes. In programs and features it's called Java 7 Update 45?
Do you mean the phone drivers on my PC?
Edit: Noticed jdk was the dev kit. Downloaded and installed. Will try again.
Edit2: Still not working, same errors.

Jre is normal java jdk is the development kit
and yes that drivers
Sent from my GT-I8190 using xda app-developers app

robindebruin said:
Jre is normal java jdk is the development kit
and yes that drivers
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
I just updated the phone drivers (without HTC sync) from http://forum.xda-developers.com/showthread.php?t=2376761 to 4.2.0.001 from the 4.0 version I had that HTC sync had installed previously for some reason.
Shows up in fastboot devices now. Still doesn't show up in adb devices. Still getting the can't load recovery.img error.
Would it be worth it to try doing it on another computer?

Yes and plz post results
Sent from my GT-I8190 using xda app-developers app

robindebruin said:
Yes and plz post results
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Ok so I still couldn't do it manually on the other computer. Got the same errors as with the first. I tried flashing with Hasoon2000's tool again and noticed that it was trying to flash CWM.img while the recovery for it was actually called recovery.img. Renamed it to CWM.img and it flashed perfectly.
I assume it would of done the same on the original PC I tried it on.
No idea why it wouldn't work when I tried it manually, but yolo. Hasoon2000 is love. Hasoon2000 is life.

Holy hell Hasoon2000 has saved me again.
I flashed the kernal by accident and it got stuck in boot. So i just sideloaded the rom in H2K's tool and everything turned up Milhouse.

Yay congrats
Sent from my GT-I8190 using xda app-developers app

And if it says can not load recovery that means it's named differently or that it's not placed in the same dir of the fastboot files. A common error is that people hide filename extensions in windows. Then rename the recovery to recovery.img.img and then it won't be found by fastboot

Mr Hofs said:
And if it says can not load recovery that means it's named differently or that it's not placed in the same dir of the fastboot files. A common error is that people hide filename extensions in windows. Then rename the recovery to recovery.img.img and then it won't be found by fastboot
Click to expand...
Click to collapse
Hmmm, I'm not sure what it would of been as a tried flashing recovery.img.img as well. But everything worked out well in the end .
Thank you both the help.

Glad to hear that it worked
Sent from my GT-I8190 using xda app-developers app

HTC ONE Complete Data loss Stuck in TWRP

So somehow my HTC One m7vzw was wiped completely of everything from the ROM, system and data to recovery image, etc. Now I cant access the developers options to turn USB Debugging on. Is there anyway to recover from such an ordeal?? HELP PLEASE !!!!!!

aaronpw0621 said:
So somehow my HTC One m7vzw was wiped completely of everything from the ROM, system and data to recovery image, etc. Now I cant access the developers options to turn USB Debugging on. Is there anyway to recover from such an ordeal?? HELP PLEASE !!!!!!
Click to expand...
Click to collapse
There is an ADB push option in TWRP which should let you put a ROM on the phone using:
adb push PUTROMENAMEHERE.zip /sdcard/.
or
You should be able to RUU something back onto the phone. Try to get to fastboot by rebooting to the bootloader from TWRP. Then you can use something like:
http://forum.xda-developers.com/showthread.php?t=2485319 Firmware update if needed
http://forum.xda-developers.com/showthread.php?t=2437436 RUU image
or
Alternatively, if you have an OTG cable you should be able to select a flash drive as a source media in TWRP.

I had a similar issue a few days ago when I wiped everything including my internal storage without even thinking how am I going to get the rom.zip back on the card (all my previous phones had SD cards).
In order to avoid flashing RUU I used sideload in TWRP to load rom directly through ADB. the only issue I had was with the drivers because for some reason my PC wouldn't recognize the phone (even though I used the same PC to root it) so I downloaded universal drivers that I found somewhere on the XDA.
unfortunately I don't have the links saved but if you search sideload and universal drivers I'm sure you'll find it.

aaronpw0621 said:
So somehow my HTC One m7vzw was wiped completely of everything from the ROM, system and data to recovery image, etc. Now I cant access the developers options to turn USB Debugging on. Is there anyway to recover from such an ordeal?? HELP PLEASE !!!!!!
Click to expand...
Click to collapse
To activate Developer Options, go into Stettings, then About Phone, then find Build Number. Press Build Number seven times.

jpradley said:
To activate Developer Options, go into Stettings, then About Phone, then find Build Number. Press Build Number seven times.
Click to expand...
Click to collapse
You must have misread his post. Everything was wiped. There is no way to go to settings, etc. There is no rom.
Sent from my HTC6500LVW using XDA Premium 4 mobile app

Your options are to boot it to the bootloader manually by holding power and volume down, then go to fastboot and push a recovery to it, from there you can also push a Rom to your storage and then use recovery to install your Rom.
Sent from my HTC6435LVW using Tapatalk 2

I tried installing a couple recoveries. A new TWRP and also CWM Recovery(hoped that worked since was the most recent recovery I used.
Sent from my XT907 using XDA Premium 4 mobile app

aaronpw0621 said:
I tried installing a couple recoveries. A new TWRP and also CWM Recovery(hoped that worked since was the most recent recovery I used.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Once you have a recovery on there now just push a Rom using fastboot. Then boot into recovery and install Rom or if you already have a Rom on the internal storage just boot recovery and go from there.
Sent from my HTC6435LVW using Tapatalk 2

When I try using adb sideload in twrp the progress bar just keeps spinning.
Sent from my XT907 using XDA Premium 4 mobile app

Instead of side load can't you push a rom through the pc in fastboot? Drivers on your pc may not be working properly with sideload.
Sent from my HTC6435LVW using Tapatalk 2

I have nothing on internal. Like I said all is wiped
Sent from my XT907 using XDA Premium 4 mobile app

you can try
You will need to reboot to recovery and enter fastboot
not sure if this is exact so research it lower case and caps are needed the way they are done in tuts i used copy and paste then edited
enter command prompt window change to where your adb stuff is
fastoot devices if you get a response with sn great
fastboot oemRUU
fastboot flash zip imagename.zip where imagename is the rom you want to put on
for recovery it is like
fastboot flash recovery imagename.zip where imagename is your custom recovery

aaronpw0621 said:
I have nothing on internal. Like I said all is wiped
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I got it to get into recovery. I ended up using a HTC ONE all in one kit. So I got a stock like ROM and radio and firmware to get me going. Thing is now is when I try to sideload any ROM I keep getting stuck in either a bootloop or at the Boot Image. I still have SuperCid. I tried using the how-to on changing "mid" so that way I can use any variant ROM. But apparently I dont have a way to re-zip files So now going trying to sideload CM10.2 with GAPPS. Thing is is what I do sideload I cant find in storage. I just cant figure out why a few ROMS I had before now wont boot past the boot animation or just wont flash. PLEASE HELP

how did u make out with cm 10?
just checking in