Develop Bugs

[Q] SD card not mounting

Hi..
Hopefully someone can help me..
I previously had ClockworkMod 2.5.0.1 installed and desided to change to Amon RA recovery 2.0.0, since I couldn't backup my ext4 partitions.
I've got RCMixHD 3.0b1 installed, but since I flashed another recovery it installed a new superuser - This superuser didn't work properly, as I had to "allow" all the time, everytime I needed root (try backing up with MyBackup Root eh'?).
Then someone told me to re-flash my current ROM without wipe, so I tried that..
But... I got an error after the ROM installed a bit and then tried wiping to restore my nandroid.
This unfortunately didn't work, as I got somekind of mount error.
Now, everytime I try wipe, install or anything from my SD Card in recovery I get the following error:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount /sdcard
Click to expand...
Click to collapse
I tried re-partitioning my card, which didn't work, now I don't know what to do, already been phone-less for a day now =/
I can't flash another recovery with unrEVOked, as I can't get past the damn "HTC"-screen.
EDIT: Using "Clear storage" in FASTBOOT just made it reboot all the time @ "HTC"
Any sugestions will do, please help.
- Neo3000x

try formatting / partitioning via nokia ( i did the same on my 5800xm running c6 firmware and it fixed the card ) hope it helps and hope you have access to a 5800 with c6 firmware

Post title edited to remove swearing. Please do not swear on the forums.
Thanks

Format it in Sd Crad reader

I already tried formatting it through gParted, RA Recovery and Windows, no luck yet..
When I boot into fastboot, I see that it's loading the .zips, but not in recovery

Okay...
Anything will do, currently I have a phone that does absolutely nothing, besides showing me the HTC logo..
Should I install a RUU and the root it afterwards?

What happens when you connect your phone to the computer? It actually sounds like a USB brick!
Hallydamaster

hallydamaster said:
What happens when you connect your phone to the computer? It actually sounds like a USB brick!
Hallydamaster
Click to expand...
Click to collapse
Without pressing the button it boots over and over, trying to install Qualcomm CDMA Technologies MSM driver.

Tried to do the unbrick of USB and got "Device not found" in adb all the time..
Did I do something wrong? Installed the usb-driver from unrEVOked to connect.

Neo3000x said:
Tried to do the unbrick of USB and got "Device not found" in adb all the time..
Did I do something wrong? Installed the usb-driver from unrEVOked to connect.
Click to expand...
Click to collapse
Seems to me this is what we call an USB Brick
Have a look here http://forum.xda-developers.com/showthread.php?t=691187or here http://android.modaco.com/content/htc-desire-desire-modaco-com/309939/usb-brick-rickrolled-b0rked-fixed/

leinad said:
Seems to me this is what we call an USB Brick
Have a look here http://forum.xda-developers.com/showthread.php?t=691187or here http://android.modaco.com/content/htc-desire-desire-modaco-com/309939/usb-brick-rickrolled-b0rked-fixed/
Click to expand...
Click to collapse
So.. Can I fix it 100% myself or do I actually have to send it in for fixing?
EDIT: Aren't my warranty gone, since I ****ed this up myself btw?

Neo3000x said:
So.. Can I fix it 100% myself or do I actually have to send it in for fixing?
Click to expand...
Click to collapse
Can you still get into Recovery?
Also...
Do you have Insurance on it? If you Do Try going that Route, just tell them You got a FC and it
Shut Off on its Own!!
Good Luck!
Sent from my HERO200 using XDA App

Neo3000x said:
So.. Can I fix it 100% myself or do I actually have to send it in for fixing?
EDIT: Aren't my warranty gone, since I ****ed this up myself btw?
Click to expand...
Click to collapse
I think you can fix it by yourself, following these totos.

I can still get into recovery yes, but I really can't do that much in there, as it won't mount the damn SD card.

Neo3000x said:
I can still get into recovery yes, but I really can't do that much in there, as it won't mount the damn SD card.
Click to expand...
Click to collapse
I'm gonna upload a SU Zip for you, I want you to try that! I had the Same Issue but not as Drastic and I Flashed this and it fixed everything! Gimme 5mins. To Find it!! OKAY TRY THIS... I'LL KEEP MY FINGERS CROSSED FOR YOU!!
Sent from my HERO200 using XDA App

PMGRANDS said:
I'm gonna upload a SU Zip for you, I want you to try that! I had the Same Issue but not as Drastic and I Flashed this and it fixed everything! Gimme 5mins. To Find it!! OKAY TRY THIS... I'LL KEEP MY FINGERS CROSSED FOR YOU!!
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Okay, ty..
But, what should I do with it? How to flash it when I can't access my SD card?

Neo3000x said:
Okay, ty..
But, what should I do with it? How to flash it when I can't access my SD card?
Click to expand...
Click to collapse
See Sh.t, I Misunderstood you I Thought you were able to Flash Zips, But they Weren't Fully Installing Because of the Mount Problem... You Don't happen to have a Micro Sdcard Adapter do you? On the Adapter there's a LITTLE WHITE SWITCH to the Left of the M in the word Micro... that Switch was Responsible for me Getting the Same Reading... the Dev/Block/Whatever Else? Can't Remember, but all I did was take the Sdcard out of my phone and flick that Stupid Little Switch the Opposite way and All of a Sudden I was Back in Business!
Sent from my HERO200 using XDA App

Neo3000x said:
I can still get into recovery yes, but I really can't do that much in there, as it won't mount the damn SD card.
Click to expand...
Click to collapse
I you can still get into recovery, you can also still get into bootloader and fastboot:
power off, then power on while holding 'back' button => You should get into bootloader
When in bootloader, you choose 'fastboot' => first choice in the list of four
You then connect you USB cable => You should see a message like 'fastboot usb' in red.
On you PC, open a terminal window and go to your fastboot directory (directory where you should have installed the Google SDK)
Then, you type the following command in your terminal window:
Code:
fastboot oem enableqxdm 0
This should reenable your SD card.
At that stage, you are back with a working phone, but the USB is not yet working properly. You'll have to reflash your 'misc' partition with a correct mtd0.img.
The tutos I showed you in a previous reply explains the procedure to follow.
hope this will help.

leinad said:
I you can still get into recovery, you can also still get into bootloader and fastboot:
power off, then power on while holding 'back' button => You should get into bootloader
When in bootloader, you choose 'fastboot' => first choice in the list of four
You then connect you USB cable => You should see a message like 'fastboot usb' in red.
On you PC, open a terminal window and go to your fastboot directory (directory where you should have installed the Google SDK)
Then, you type the following command in your terminal window:
Code:
fastboot oem enableqxdm 0
This should reenable your SD card.
At that stage, you are back with a working phone, but the USB is not yet working properly. You'll have to reflash your 'misc' partition with a correct mtd0.img.
The tutos I showed you in a previous reply explains the procedure to follow.
hope this will help.
Click to expand...
Click to collapse
yay, that worked and my phone is running!
Got a locations.apk fc when it booted, but still..
So, you're saying that I still need to do something to be completely unbricked?

Neo3000x said:
yay, that worked and my phone is running!
Got a locations.apk fc when it booted, but still..
So, you're saying that I still need to do something to be completely unbricked?
Click to expand...
Click to collapse
Ya ... Your phone is working, but, when you plug your USB cable, your PC does not detect it, is'it ?
All depends now on the following points :
Is your phone s-off or not ? Is your current ROM rooted or not ?

[Q] Desperately need help - stuck on splash screen

My S-Off, Alfarev Desire running the latest CM7 RC has been working very well for some time until recently I used it for navigating. It got very hot until it turned off. I thought it was nothing out of the ordinary (very hot and sunny over here, wasn't too surprised) until in the evening, after it had cooled off for several hours it simply refuses to get past the splash screen (the joker screen). I'd be happy to reflash and see if that's the problem, but I can only access fastboot and hboot: if I select recovery, it just gets stuck on the splash screen again. I've tried leaving it for a while, but turned it off after an hour as it was obviously going nowhere.
What should I do?
Thanks to all the gurus that may have some lifesaving advice.

Should be in the Q&A section.

@lucchini please explain to me why is there a Q&A (QUESTION AND ANSWER) section.

ooops, sorry about that - I'll see if I can get somebody to move it.
Anybody that actually has some advice?

look here mate http://www.youtube.com/watch?v=JmvCpR45LKA

Put it in the refrigator for a while (im not kidding), it helped numerous people with same issue.

You say that you can enter bootloader, so that means that you can flash RUU

Sadly, I tried that already to no avail. I also tried leaving it for a few days and then restarting, but nothing's changed.

Then find a good solid hammer and show that bitc* what she desirves

lucchini said:
Sadly, I tried that already to no avail. I also tried leaving it for a few days and then restarting, but nothing's changed.
Click to expand...
Click to collapse
Is your phone recognized in fastboot?
Try running:
fastboot devices

Did you rooted and s-offed your phone with revolutionary? If us, you have to flash bravo downgrader before you can apply ruu.
Or did you (also) get cid error when you wanted to apply ruu?
TouchPaled from Oxygen with Transparent XDA App

Thanks for all the replies.
update: It was indeed recognised in fastboot devices, so I followed jeremija8's suggestion and ran the RUU. Everything was going smooth until it got to the system files, when it said the partition didn't exist. It has since been stuck in the black HTC screen with a /!\ sign in each corner. As I understand it, it's still in fastboot, but I'm starting to feel a sense of impending doom now.
Any ideas?
Again, thanks to all.

SOLVED: I finally figured it out - I had a damaged system partition. Managed to fix it by using fastboot from within Teppik74's downgrade tool [http://forum.xda-developers.com/showthread.php?t=768256] to erase everything, then ran the latest official WWE RUU which set everything to stock. Finally back in business.
A big thank you for everybody's suggestions, especially howdid's video - very entertaining.

lucchini said:
SOLVED: I finally figured it out - I had a damaged system partition. Managed to fix it by using fastboot from within Teppik74's downgrade tool [http://forum.xda-developers.com/showthread.php?t=768256] to erase everything, then ran the latest official WWE RUU which set everything to stock. Finally back in business.
A big thank you for everybody's suggestions, especially howdid's video - very entertaining.
Click to expand...
Click to collapse
Have exactly the similar problem , stuck on Alpharev splash screen. Can you please explain what do you mean by erase everything or if you can give details of the steps you performed ?
Thanks

ridhavm said:
Have exactly the similar problem , stuck on Alpharev splash screen. Can you please explain what do you mean by erase everything or if you can give details of the steps you performed ?
Thanks
Click to expand...
Click to collapse
This is what I did last night when I was stuck on the alpharev logo (albeit with a CACHE error having no space, but this should erase the partitions so you can start from scratch again):
Try with Fasboot Commander v1.51 (http://forum.xda-developers.com/show....php?t=1193915).
Here are steps I used last night when I was in the same situation as you:
1.Once you download Fastboot Commander, make sure you have the latest java downloaded on your PC (java.sun.com).
2.Once you've done that, open up Fastboot Commander on your PC, then boot your phone using Vol Down + Power and choose "FASTBOOT".
3.Then, connect your phone to your PC using a USB cable and go to the "misc" tab in Fastboot Commander and click "Check connection", and if it's successful, then choose "print device info" so you see everything is OKAY.
4.Paste the "Device Info" here too so we can see what's up!
5. On the same "misc" tab in Fastboot Commander, tick the boxes in the "Erase partitions": System, Cache, Boot
6. Click "Erase Chosen Partitions"
7. Choose "BOOTLOADER" on your phone display, and when it's done, disconnect the USB cable.
8. Flash the new ROM as usual, while doing a full wipe right after you flashed it (still in recovery): Dalvik/Data/Cache
9. Reboot when done and hopefully it will work.
Good luck

EddieN said:
This is what I did last night when I was stuck on the alpharev logo (albeit with a CACHE error having no space, but this should erase the partitions so you can start from scratch again):
Try with Fasboot Commander v1.51 (http://forum.xda-developers.com/show....php?t=1193915).
Here are steps I used last night when I was in the same situation as you:
1.Once you download Fastboot Commander, make sure you have the latest java downloaded on your PC (java.sun.com).
2.Once you've done that, open up Fastboot Commander on your PC, then boot your phone using Vol Down + Power and choose "FASTBOOT".
3.Then, connect your phone to your PC using a USB cable and go to the "misc" tab in Fastboot Commander and click "Check connection", and if it's successful, then choose "print device info" so you see everything is OKAY.
4.Paste the "Device Info" here too so we can see what's up!
5. On the same "misc" tab in Fastboot Commander, tick the boxes in the "Erase partitions": System, Cache, Boot
6. Click "Erase Chosen Partitions"
7. Choose "BOOTLOADER" on your phone display, and when it's done, disconnect the USB cable.
8. Flash the new ROM as usual, while doing a full wipe right after you flashed it (still in recovery): Dalvik/Data/Cache
9. Reboot when done and hopefully it will work.
Good luck
Click to expand...
Click to collapse
Thanks . Just to add some more information, when I took out the memory card earlier today, windows detected it as corrupt and asked to reformat it.
I have used Fastboot and followed these steps, but getting this message :
PRINT OF DEVICE INFO FAILURE - PLEASE CHECK YOUR CONNECTION.
I believe I recently formatted my windows system and its missing drivers.
Is there any way to install the drivers without connecting phone ?
Thanks again for your help.

Got it , Here is the Device Info:
SPL/hboot version: 0.93.0001.
Radio version: 5.11.05.27.
Main software version: 2.12.110.4.
cid: t-mob005.
cpld: none.
product: bravo.
mid: pb9920000.
security: off.
build-mode: ship.
I had RCMIX v2.x installed on my desire

ridhavm said:
Thanks . Just to add some more information, when I took out the memory card earlier today, windows detected it as corrupt and asked to reformat it.
I have used Fastboot and followed these steps, but getting this message :
PRINT OF DEVICE INFO FAILURE - PLEASE CHECK YOUR CONNECTION.
I believe I recently formatted my windows system and its missing drivers.
Is there any way to install the drivers without connecting phone ?
Thanks again for your help.
Click to expand...
Click to collapse
Now that you say it, it might be your SD card acting up. So try and reformat it and prep it according to this: http://forum.xda-developers.com/showpost.php?p=7279872&postcount=3.
I wouldnt recommend 512mb ext though, people usually recommend 1gb
After this you'll have to reflash the rom again and do a full wipe

Thanks, Tried reformatting SD card , was still stuck on boot loop.
Got Screwed up further now , Tried installing the official TMo RUU, it detected the phone in fast boot mode but aborted in the middle with error relating to verifying signature.
Now stuck with a Black bricked screen. No display , not able to get to FastBoot mode now.

ridhavm said:
Thanks, Tried reformatting SD card , was still stuck on boot loop.
Got Screwed up further now , Tried installing the official TMo RUU, it detected the phone in fast boot mode but aborted in the middle with error relating to verifying signature.
Now stuck with a Black bricked screen. No display , not able to get to FastBoot mode now.
Click to expand...
Click to collapse
Tried with a new recovery through ADB?
EDIT: Try this http://forum.xda-developers.com/showthread.php?t=831734

[Q] Help rooting Wildfire S please

Hi All
Spent most of yesterday trying to root the good lady's phone, using http://forum.xda-developers.com/show....php?t=1195275 Much more difficult than I thought! I have got as far as having unlocked the bootloader but when I try Flashing the Custom Recovery UI, I get "CID incorrect" Researched what this meant and have now managed to create a goldcard and have tried again with this card fitted in the phone but nothing seemed to happen so I copied the PG76.IMG file on to the sd card and tried again. This time I get some action the message i get is "Main version is older", please see attached image if anyone can help me out I would be most grateful. Many thanks.

Since you have unlocked it, download the recovery image of CWM and the root.zip. Then, considering you have the fastboot files, type
fastboot flash recovery recovery.img.
Then boot into recovery and flash the root.zip from there. I'll give you more detailed instructions tomorrow, if you need them, since I'm on my phone now.
Sent from my HTC Wildfire S A510e using Tapatalk 2

Thanks
Hi Tyr Fifteen thanks for coming back to me. I have the files on the PC I am connected to and when I run the command:
Code:
fastboot flash recovery recovery.img.
the cmd window shows waiting for device and sits at that for ages >10 minutes?
The phone is telling me that it is in HBOOT USB PLUG highlighted in blue and also says FASTBOOT the same with a blue background. If I kill the cmd nothing still happens at the phone screen. Your help is much appreciated thanks.

pompeyrodney said:
Hi Tyr Fifteen thanks for coming back to me. I have the files on the PC I am connected to and when I run the command:
Code:
fastboot flash recovery recovery.img.
the cmd window shows waiting for device and sits at that for ages >10 minutes?
The phone is telling me that it is in HBOOT USB PLUG highlighted in blue and also says FASTBOOT the same with a blue background. If I kill the cmd nothing still happens at the phone screen. Your help is much appreciated thanks.
Click to expand...
Click to collapse
After it shows HBOOT USB PLUG, it's highlighting FASTBOOT right? Press power and enter Fastboot mode.
The HBOOT USB PLUG should change to FASTBOOT USB. If it remains FASTBOOT, (re)install the drivers. It's waiting for the device to be in fastboot, it wont work in HBOOT mode.

pompeyrodney said:
Hi All
Spent most of yesterday trying to root the good lady's phone, using http://forum.xda-developers.com/show....php?t=1195275 Much more difficult than I thought! I have got as far as having unlocked the bootloader but when I try Flashing the Custom Recovery UI, I get "CID incorrect" Researched what this meant and have now managed to create a goldcard and have tried again with this card fitted in the phone but nothing seemed to happen so I copied the PG76.IMG file on to the sd card and tried again. This time I get some action the message i get is "Main version is older", please see attached image if anyone can help me out I would be most grateful. Many thanks.
Click to expand...
Click to collapse
see this link video...
http://www.youtube.com/watch?v=UqCk2NiHTTg

After it shows HBOOT USB PLUG, it's highlighting FASTBOOT right? Press power and enter Fastboot mode.
The HBOOT USB PLUG should change to FASTBOOT USB. If it remains FASTBOOT, (re)install the drivers. It's waiting for the device to be in fastboot, it wont work in HBOOT mode.
Click to expand...
Click to collapse
I guess I must have not known that I needed to press the power button, the guides for rooting all assume a lot of knowledge that the new user needs, but does not have. Is there a guide that hand holds you through the whole process. I will try again when I have access to the phone this evening. If I do need to install the drivers, is there a guide I can refer to please?

pompeyrodney said:
I guess I must have not known that I needed to press the power button, the guides for rooting all assume a lot of knowledge that the new user needs, but does not have. Is there a guide that hand holds you through the whole process. I will try again when I have access to the phone this evening. If I do need to install the drivers, is there a guide I can refer to please?
Click to expand...
Click to collapse
For the drivers download and install htc sync. Then uninstall htc sync, if you wish. That's all. But since it shows HBOOT usb plug, I think the drivers are already installed.
Sent from my HTC Wildfire S A510e using Tapatalk 2

Thanks
Hi Tyr Fifteen
I seem to go from one issue to another, on a positive note you were right about the drivers as the phone was waiting to be in fastboot, when I hit the power button it went ahead and pushed the recovery image to the phone, at last! Now I show recovery version 5.0.2.8 and when I select "install zip from sdcard" I just see the CWM bowler hat and nothing happens? In fact CWM recovery does not respond if I select any of the options in the menu. I have to take out the battery before I can restart as normal. Any ideas please? Please see enclosed pictures showing menu and result of selection of any item

Maybe you should try it again I used this utilitie to root my phone a long time ago. It worked great.
HTML:
http://forum.xda-developers.com/showthread.php?t=1678421

Thanks 4ndKava
I came across this tool before but as there was no info on how to use it, i did not bother. How is the phone connected and what are the prerequisites etc. Do I connect to the phone by usb and then put the phone in fast boot usb and run the batch file in the tool?

Connect your phone with your computer, activate usb-debugging in your setting and than start the "one click.bat". I hope, i could help.

Hi
I have just managed to download the correct Recovery image as suggested and it appears to have installed correctly.
Code:
c:\WFS>fastboot flash recovery recovery.img
sending 'recovery' (4494 KB)...
OKAY [ 1.700s]
writing 'recovery'...
OKAY [ 2.200s]
finished. total time: 3.900s
I have then removed the battery for a couple of minutes, restarted while holding down the volume minus.
I get the white screen showing hboot at the top highlighted in blue and fastboot highlighted in blue further down.
The sd card is then checked? and I can then select recovery and press the power button.
I then wait for the recovery options but all I am seeing is a white screen saying HTC followed by a black screen with all the four screen button lights on?
There is no mention of any recovery options at all.
Has something gone horribly wrong?

pompeyrodney said:
Hi
I have just managed to download the correct Recovery image as suggested and it appears to have installed correctly.
Code:
c:\WFS>fastboot flash recovery recovery.img
sending 'recovery' (4494 KB)...
OKAY [ 1.700s]
writing 'recovery'...
OKAY [ 2.200s]
finished. total time: 3.900s
I have then removed the battery for a couple of minutes, restarted while holding down the volume minus.
I get the white screen showing hboot at the top highlighted in blue and fastboot highlighted in blue further down.
The sd card is then checked? and I can then select recovery and press the power button.
I then wait for the recovery options but all I am seeing is a white screen saying HTC followed by a black screen with all the four screen button lights on?
There is no mention of any recovery options at all.
Has something gone horribly wrong?
Click to expand...
Click to collapse
When did you buy the phone? I guess its 2012... Because that model is nasty. You need to flash a modified recovery for it. Search a topic in general section I think. You can't flash cm ROMs. only stock based ROMs, sadly. However, there are few 2012 lucky guys who can. Try that recovery and try installing cm9 or 10. If it works, good for you, and if it doesn't, oh well.
Good luck.
Sent from my Wildfire S A510e using Tapatalk 2

I am one of the lucky ones, had no problems ..

4ndaKava said:
I am one of the lucky ones, had no problems ..
Click to expand...
Click to collapse
Good for you!
Sent from my Wildfire S A510e using Tapatalk 2

Help
Maybe you should try it again I used this utilitie to root my phone a long time ago. It worked great.
Click to expand...
Click to collapse
Just tried One Root for WFS and this is what I got
Code:
ECHO is off.
rezo609's Rooting Utility for HTC Marvel v1.3 on xda.
Press any key to continue . . .
Pushing root.zip to sdcard! Here we go.
failed to copy 'root.zip' to '/sdcard/root1.zip': Permission denied
.
Rebooting to Fastboot
Check Fastboot
Press any key to continue . . .
SH23CTR01506 fastboot
.
sending 'recovery' (4494 KB)...
OKAY [ 1.700s]
writing 'recovery'...
OKAY [ 2.200s]
finished. total time: 3.900s
Press any key to continue . . .
.
downloading 'boot.img'...
OKAY [ 1.701s]
booting...
OKAY [ -0.000s]
finished. total time: 1.701s
.
DO NOT USE THE POWER BUTTON TO SELECT. Please use the Search button instead of the Power button.
Now choose Install Zip from Sdcard then select root.zip. Press yes.
Press any key to continue . . .
You are now ROOTED. Lets grab a beer and get drunk. lol xD
Press any key to continue . . .
Now you can press the power button :)
Press any key to continue . . .
I guess the permission denied is because the sd card already has root.zip on it?
Can you tell me what the boot.img file is?
I guess my phone is not getting to recovery as I do not see any of the options for choosing the root.zip file at all.

Success
Found this post by Operator 3 http://forum.xda-developers.com/showthread.php?t=1997465&page=3 which provided a modded CWM image and it works which is brilliant, so I now have a rooted phone.

pompeyrodney said:
Found this post by Operator 3 http://forum.xda-developers.com/showthread.php?t=1997465&page=3 which provided a modded CWM image and it works which is brilliant, so I now have a rooted phone.
Click to expand...
Click to collapse
I was right about it being a 2012 one. Good for you.
Sent from my Wildfire S A510e using Tapatalk 2

[Q] Stuck At Recovery

Hi,
I always power off my phone at night and yesterday morning it booted to recovery so I thought that I must had pressed the vol key but it was frozen, removed/replaced the battery, booted into recovery again, still frozen.
Pressing the volume keys won't change the selection, pressing power will not make the device do anything. I believe that it is somewhat working because HBOOT will change to HBOOT USB PLUG when plugging it.I can also see it looking for "P98IMG" for a little moment.
If I connect it to my PC, it will be detected as "Android 1.0". I did install the drivers as specified at : http://forum.xda-developers.com/showthread.php?t=737728 I have Androik SDK installed & working (I am a developer).
The phone is detected by fastboot as :
HT12NTZ00637 fastboot
but I was not able to do anything with it.
Code:
fastboot reboot
rebooting...
finished. total time: 0.000s
The phone doesnt do anything
Code:
fastboot -w
erasing 'userdata'...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s
I've discovered Ace Think Tank post while searching the forums : http://forum.xda-developers.com/show....php?t=1824379
I was running ViperDHD1.1.0 if it makes any difference.
Thanks for helping me out.
HTC Desire HD (Telus)
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
MICROP-0438
RADIO-26.06.04.06_M
eMMC-boot
Oct 11 20120, 12:47:02

Tried to put PD98IMG.zip from this post on my SD : http://forum.xda-developers.com/showpost.php?p=20203105&postcount=5
It looks like the phone is trying to install it however once the "blue loading bar" finishes, I see all the folder such as bootloader, boot, recovery, system, ... but it has been displaying this for 4 hours now. I thought it could take a while but I really doubt that this is every gonna finish.
Any help?

SOuellet said:
Tried to put PD98IMG.zip from this post on my SD : http://forum.xda-developers.com/showpost.php?p=20203105&postcount=5
It looks like the phone is trying to install it however once the "blue loading bar" finishes, I see all the folder such as bootloader, boot, recovery, system, ... but it has been displaying this for 4 hours now. I thought it could take a while but I really doubt that this is every gonna finish.
Any help?
Click to expand...
Click to collapse
well, it seems that you failed to read...why being S-OFF you flashed a RUU? was that RUU froyo? Sounds like you might have messed the bootloader.

glevitan said:
well, it seems that you failed to read...why being S-OFF you flashed a RUU? was that RUU froyo? Sounds like you might have messed the bootloader.
Click to expand...
Click to collapse
First, I'm going to thank you for being the only person to try to answer but it seems that you did failed to read too as the phone was stuck in HBOOT before I tried this out. If I remove the SD card, the phone will act the same as described earlier as the install does nothing.
Any other suggestions?

SOuellet said:
First, I'm going to thank you for being the only person to try to answer but it seems that you did failed to read too as the phone was stuck in HBOOT before I tried this out. If I remove the SD card, the phone will act the same as described earlier as the install does nothing.
Any other suggestions?
Click to expand...
Click to collapse
Why not flashing a rom from recovery? If your phone is not flashing anything in fastboot or hboot, then might be a hardware issue.
Sent from my GT-N7000 using xda app-developers app

glevitan said:
Why not flashing a rom from recovery?
Click to expand...
Click to collapse
I wish I could go into recovery but I'm stuck into HBOOT and to quote myself :
Pressing the volume keys won't change the selection, pressing power will not make the device do anything
Click to expand...
Click to collapse

SOuellet said:
I wish I could go into recovery but I'm stuck into HBOOT and to quote myself :
Click to expand...
Click to collapse
have you tried navigating without the sdcard?? power the device off and take the sdcard out...then boot in hboot..

glevitan said:
have you tried navigating without the sdcard?? power the device off and take the sdcard out...then boot in hboot..
Click to expand...
Click to collapse
Yes I did, I am no SIM, no SD, even tried a different SD...

SOuellet said:
Yes I did, I am no SIM, no SD, even tried a different SD...
Click to expand...
Click to collapse
You mean that you can not move in hboot nor select anything? then it seems to be a hardware issue...

glevitan said:
You mean that you can not move in hboot nor select anything? then it seems to be a hardware issue...
Click to expand...
Click to collapse
Exactly, pressing vol up / vol up / power buttons won't make the selection change. The display will change from HBOOT to HBOOT USB PLUGwhen plugging/removing USB cable tho so it's not completely frozen...
In the mean time, I have been trying to do a couple things, like fastboot update bleh.zip but it'll give
Code:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I thought that I could try flashing with a RUU so I got this file :
http://goo.im/ruu/RUU_Ace_Sense30_S...60.29_26.14.04.28_M_release_225512_signed.exe
but it doesn't work. If I remove/replace the battery from the phone and plug it in the USB, my PC will not find any drivers for my phone and it'll be detected as "Android Phone", trying to run the RUU will fail because it will not recognize the phone. If power it up before trying the RUU, it will say that my battery is less than 30% even if the green led (fully charged) was on.
Any ideas or maybe I'm just doing something wrong?
Thanks a lot for taking the time to help me out.

Found the Telus image T : http://shipped-roms.com/download.ph...60.25_26.10.04.03_M_release_194001_signed.exe
extracted recovery.img as another post points out but no success so far, after typing this command :
Code:
fastboot flash recovery recovery.img
my cpu stays at 100%, and even after 2 hours and got no feedback whatsoever.
trying to update using fastboot update telus.zip will result in :
Code:
Whoops: didn't find expected signature
read_central_directory_entry failed
╗±ýpïð7'@=z«▼Gñ▼äò̪¦╝WDÙh¬Ð秬)↓ø┌温§h█←àV*PѲ╠╗[ø×e┐§¨v╗ÚY}╬áDƒ▒ýrÙ®│E█¸ÄÝÐþ\
é·\ËÜÈ⌂▓☼ÐÌõ╬PO↑pm5üå饧sÌéä]ÚâÍ▒á▼ÈØ░▼üÐ↑ggGÊè¯ãÿuÛ¸0uÁ¿Ã¾´Éë♠S%¹ ¸÷u$,gRÛÐ─3X/
═ÀE╬⌂¢↕J▄½u'LÃoáK▀Ò¥L8┴rÞ/³┌öò©7qg▀⌂¢r÷ñxrX²o¦ÆDGb8Ê☼ï■ÍÁóSR¶q¥8A_YƒKË?♦´å(E¹╩ðÄ
î/█t¬÷³4yÛ÷*←█├9▒}®Ò´m4s▓║╝Ã]╬¨ÞÞH¼
ܨXâ¨'
Yes, all the weird chars were outputted to console.
I also copied the zip to my SD, renamed it to PD98IMG.ZIP but it looks like doing the same at the other ROM I've tried earlier, the blue progress bar will complete, then when a "directory parsing" appears, it will stays there _forever_.
Hope these details can help you find a solution.

Since I haven't found any solutions yet, I am willing to offer a monetary compensation if anyone can help.

would appreciate if somebody can help, i've exactly the same problem here

Have you (both) flash a froyo RUU or ENG S-OFF and you were running Gingerbread?

I was running ICS (ViperDHD 1.1.0) and I wasn't able to flash anything as it freezes as explained in previous posts.

What happens if you just try running the RUU in hboot? I mean, connecting your phone to the computer and running the exe.

SOuellet said:
I was running ICS (ViperDHD 1.1.0) and I wasn't able to flash anything as it freezes as explained in previous posts.
Click to expand...
Click to collapse
Sorry, have you also tried with the sim card out?

Question :
sashank said:
What happens if you just try running the RUU in hboot? I mean, connecting your phone to the computer and running the exe.
Click to expand...
Click to collapse
Answer :
SOuellet said:
I thought that I could try flashing with a RUU so I got this file :
http://goo.im/ruu/RUU_Ace_Sense30_S...60.29_26.14.04.28_M_release_225512_signed.exe
but it doesn't work. If I remove/replace the battery from the phone and plug it in the USB, my PC will not find any drivers for my phone and it'll be detected as "Android Phone", trying to run the RUU will fail because it will not recognize the phone. If power it up before trying the RUU, it will say that my battery is less than 30% even if the green led (fully charged) was on.
Click to expand...
Click to collapse
I also did try a Telus image : http://shipped-roms.com/download.ph...60.25_26.10.04.03_M_release_194001_signed.exe
Maybe Ì'm just doing it wrong? or wrong image? or ...
glevitan said:
Sorry, have you also tried with the sim card out?
Click to expand...
Click to collapse
Yep, tried to flash w/ SIM, w/o SIM, w/ SD, w/o SD (from PC)
It seems to always give the same result...

SOuellet said:
Question :
Answer :
I also did try a Telus image : http://shipped-roms.com/download.ph...60.25_26.10.04.03_M_release_194001_signed.exe
Maybe Ì'm just doing it wrong? or wrong image? or ...
Click to expand...
Click to collapse
If you are S-OFF and have superCID, any RUU should be flashing. I am afraid that it can be a hardware issue...

glevitan said:
If you are S-OFF and have superCID, any RUU should be flashing. I am afraid that it can be a hardware issue...
Click to expand...
Click to collapse
Wow, quick reply.
I believe that I am S-OFF as it is displayed at the top of the screen : ACE PVT SHIP S-OFF. I don't really know about the superCID.
When looking for one of my previous posts to quote myself, I figured that I didn't explicitly said that when I plugged my phone turned off in my PC, I had no drivers for "Android Phone". If powered on, it will use the Google ADB drivers.

[Q] Major issues re-rooting

I've been trying to re-root my phone since late last night, and have had nothing but problems. I've searched all over the internet, and tried anything that I thought would apply to my situation in the slightest.
I originally downgraded from 2.3.4 to 2.3.3 and rooted my phone using the method in this thread:
http://forum.xda-developers.com/showthread.php?t=1298990
I ran Revolutionary, ClockworkMod, and SuperUser. Everything worked perfect the first time around. Installed the Cyanogenmod 7.2 ROM and Tiamat v1.1.5 kernel. Then I started having issues with my battery, and Cyanogenmod seemed to be increasing the issues. At that time HTC announced they'd be releasing ICS, yada yada yada. I found a stock ROM online, and installed it, and updated as they were released OTA. Having finally gotten a new extended battery, I'd like to re-root & ROM my phone, but I've hit some road blocks.
I currently have the Android Version of 2.3.4 & Software Number of 5.10.605.9
I tried to re-do the entire process that had previously worked for me, but once I used the command hack-vivow.cmd, the phone would boot to the Revolutionary (of HBOOT ?) screen. Command line shows this, and just hangs:
c:\vwhk-12102011-c>fastboot oem rebootRUU
< waiting for device >
Click to expand...
Click to collapse
Phone shows this:
-Revolutionary-
VIVO_W XB SHIP S-OFF RL
HBOOT -6.13.1002
RADIO -1.09.01.1111
eMMC -boot
Click to expand...
Click to collapse
Phone gives me the options of "BOOTLOADER", "REBOOT", "REBOOT BOOTLOADER", & "POWER DOWN". "REBOOT BOOTLOADER" changes "FASTBOOT" briefly to "FASTBOOT USB", but changes back in about 15-20 seconds. When I select "BOOTLOADER", the screen freezes for a few seconds, and it won't let me select any options, "FASTBOOT" changes to "HBOOT", and I get this in green text:
SD Checking
Loading...[PG32DIAG.zip]
No image!
Loading...[PG32DIAG.nbh]
No image or wrong image!
Loading...[PG32IMG.zip]
Click to expand...
Click to collapse
The next screen of green text says "Parsing...[SD ZIP]" followed by 9 things, and I'm only given an option to Update or No/Reboot. No/Reboot reboots my phone into an endless bootloop, until I remove the battery and power back on with Volume Down + Power Button. Update does a reset of my phone, and puts me right back to where I am now. While it is updating there is an error message at the bottom that says "Can not roll back hboot version".
I've tried multiple things to attempt to fix this... I ran the TacoRoot method from here:
http://forum.xda-developers.com/showthread.php?t=1751796
When the 8th line was completed
adb shell /data/local/tacoroot.sh --setup
Click to expand...
Click to collapse
, the phone rebooted, it got stuck in a bootloop.
So that's where I am now. I'm stuck with S-Off, the PG32DIAG/PG32IMG errors, an HBOOT that seems to be far too new of a version, and I haven't found a way to get back to 2.3.3. As you can see I'm a noob. I'm really not sure where I went wrong (other than going back to a stock ROM and allowing it to update). Unfortunately a lot of things are just way over my head, without seeing a step by step process. But I'm just stuck at the moment. If anyone has any ideas on how to fix this, or any ideas of things to try I GREATLY appreciate it.

Still looking for an answer, but I've done some more digging.
Would I be correct is assuming that I have to find a way to downgrade hboot (which Revolutionary won't allow) and get S-On, in order to do what I need to do? If so, does anyone know of an accurate way to accomplish this? All I've found are old threads that apparently are no longer relevant for newer Software & hboot updates.

Cleanincubus said:
Still looking for an answer, but I've done some more digging.
Would I be correct is assuming that I have to find a way to downgrade hboot (which Revolutionary won't allow) and get S-On, in order to do what I need to do? If so, does anyone know of an accurate way to accomplish this? All I've found are old threads that apparently are no longer relevant for newer Software & hboot updates.
Click to expand...
Click to collapse
I am by no means an expert, but my limited understanding would suggest this: try flashing a new recovery like clockworkmod with fastboot. If that is successful you can flash a superuser zip in clockwork. I don't recall the steps to flash the recovery, but I think since you are s-off you should be able to do it fairly easily.

gtdtm said:
I am by no means an expert, but my limited understanding would suggest this: try flashing a new recovery like clockworkmod with fastboot. If that is successful you can flash a superuser zip in clockwork. I don't recall the steps to flash the recovery, but I think since you are s-off you should be able to do it fairly easily.
Click to expand...
Click to collapse
Sorry for my ignorance, I'm trying to understand exactly what you mean. From my very limited knowledge, there might be 2 ways of doing what you're saying.
First, rebooting the phone with Volume Down + Power button, with the the ClockworkMod file placed on the root of my SD card, and renamed PG32IMG.zip. Then selecting Bootloader, and allowing it to Update.
Second would be rebooting the phone (Volume Down + Power), and then "force" the flashboot via command, with the phone connected to the USB cable.
The 1st option I would love to try, if that has a chance of working. The 2nd option though, won't work, because the phone won't respond to any commands via command lines.
The reason I'm not immediately jumping on option #1 for a try, is that I might be on track to get things straightened out, with a possibility of critical failure. I found this thread:
rootzwiki.c om/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
I'm currently using Revolutionary, but apparently Alpharevx is a previous incarnation of that, and some users in that thread claim that it worked for their Revolutionary S-Off phones. So far, I have gotten to the point where I now have Android Froyo/ Android version 2.2.1 (from the same way of doing things as Option #1 above). The rest of that thread is messing with the Bootloader, which I'd rather not risk if I don't have to (I do realize how serious the consequences are). If there's any other way to do it, I'll gladly give it a try, as long as it doesn't put me in a place much worse than I'm at now (bricking my phone by messing with the bootloader certainly would be.)
I apologize for being a pain in the ass, I just want to make sure I understand any recommendations fully before I do something wrong. Clearly I should have done a lot more research before "un-rooting" my phone. Had my original issues not been my battery, I'd still be out of warranty for having S-Off. :laugh: Thank you very much for the response, it is truly appreciated.

Cleanincubus said:
Sorry for my ignorance, I'm trying to understand exactly what you mean. From my very limited knowledge, there might be 2 ways of doing what you're saying.
First, rebooting the phone with Volume Down + Power button, with the the ClockworkMod file placed on the root of my SD card, and renamed PG32IMG.zip. Then selecting Bootloader, and allowing it to Update.
Second would be rebooting the phone (Volume Down + Power), and then "force" the flashboot via command, with the phone connected to the USB cable.
The 1st option I would love to try, if that has a chance of working. The 2nd option though, won't work, because the phone won't respond to any commands via command lines.
The reason I'm not immediately jumping on option #1 for a try, is that I might be on track to get things straightened out, with a possibility of critical failure. I found this thread:
rootzwiki.c om/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
I'm currently using Revolutionary, but apparently Alpharevx is a previous incarnation of that, and some users in that thread claim that it worked for their Revolutionary S-Off phones. So far, I have gotten to the point where I now have Android Froyo/ Android version 2.2.1 (from the same way of doing things as Option #1 above). The rest of that thread is messing with the Bootloader, which I'd rather not risk if I don't have to (I do realize how serious the consequences are). If there's any other way to do it, I'll gladly give it a try, as long as it doesn't put me in a place much worse than I'm at now (bricking my phone by messing with the bootloader certainly would be.)
I apologize for being a pain in the ass, I just want to make sure I understand any recommendations fully before I do something wrong. Clearly I should have done a lot more research before "un-rooting" my phone. Had my original issues not been my battery, I'd still be out of warranty for having S-Off. :laugh: Thank you very much for the response, it is truly appreciated.
Click to expand...
Click to collapse
So with Froyo on there can you get to the stock recovery?

Oh wow, yes I can. I just tried the fastboot clockworkmod flash, but it doesn't seem to be working, or even more likely, I don't know what I'm doing.
I booted the phone with Volume Down + Power, selected "Fastboot", which changed HBOOT to FASTBOOT USB. I used the command prompt and typed "fastboot flash recovery cwm-4.0.1.4-vivow.img". The command prompt stalls at "< waiting for device >" and FASTBOOT USB changed to FASTBOOT. Maybe I just don't know what to do after than. I tried "Recovery", which I thought would have booted ClockworkMod, had it been installed properly.

Cleanincubus said:
Oh wow, yes I can. I just tried the fastboot clockworkmod flash, but it doesn't seem to be working, or even more likely, I don't know what I'm doing.
I booted the phone with Volume Down + Power, selected "Fastboot", which changed HBOOT to FASTBOOT USB. I used the command prompt and typed "fastboot flash recovery cwm-4.0.1.4-vivow.img". The command prompt stalls at "< waiting for device >" and FASTBOOT USB changed to FASTBOOT. Maybe I just don't know what to do after than. I tried "Recovery", which I thought would have booted ClockworkMod, had it been installed properly.
Click to expand...
Click to collapse
I think you should be able to do 1B at this little how-to site:
http://forum.xda-developers.com/wiki/ClockworkMod_Recovery

Cleanincubus said:
Oh wow, yes I can. I just tried the fastboot clockworkmod flash, but it doesn't seem to be working, or even more likely, I don't know what I'm doing.
I booted the phone with Volume Down + Power, selected "Fastboot", which changed HBOOT to FASTBOOT USB. I used the command prompt and typed "fastboot flash recovery cwm-4.0.1.4-vivow.img". The command prompt stalls at "< waiting for device >" and FASTBOOT USB changed to FASTBOOT. Maybe I just don't know what to do after than. I tried "Recovery", which I thought would have booted ClockworkMod, had it been installed properly.
Click to expand...
Click to collapse
I also just noticed...did you do "fastboot devices" first to make sure it actually recognized your phone? I'm really guessing, but I figured it was worth asking.

Yes it does recognize my phone. I think you're exactly right, in the direction you're showing me. I think flashing CWM is the key to getting this all to work.
But I'm getting some strange stuff happening. When I was finally able to select the Fastboot section, I had CWM saved as PG32IMG.zip. I started getting an error (black screen with a little center image of my phone, with a red "!" on it), after rebooting. I had to press Volume Up + Power, which brought me to some kind of Android settings (Wipe Cache, & something about clearing or wiping partition). I selected to just reboot, and the phone rebooted fine. I changed the PG32IMG.zip file back to the Froyo, and I can no longer get past the "Recovery" and forcing to do the Update or Bootloop from declining.
So now I don't know what to do, when it comes to the PG32IMG.zip file. I even just changed the Froyo PG32IMG.zip to a 2.3.3 Gingerbread PG32IMG.zip, so now I'm at the correct ROM for rooting. I changed it because I wasn't sure if being at Froyo was preventing me from doing all of this from the beginning, similar to how the most up to date update did as well.
But back to the PG32IMG.zip, what would be the best thing to do with this situation? Should I change it back to the CWM, and deal with the Android error, while still allowing me to get into FASTBOOT. Or should I just keep it as the GB 2.3.3, as it is now? Can I just delete the PG32IMG.zip file altogether, or is it absolutely necessary? It just keeps trying to update to what the file already is, and prevents me from doing anything else.
I think I'm going to try the CWM.zip renamed to PG32IMG.zip and see if I can get it to work.

Cleanincubus said:
Yes it does recognize my phone. I think you're exactly right, in the direction you're showing me. I think flashing CWM is the key to getting this all to work.
But I'm getting some strange stuff happening. When I was finally able to select the Fastboot section, I had CWM saved as PG32IMG.zip. I started getting an error (black screen with a little center image of my phone, with a red "!" on it), after rebooting. I had to press Volume Up + Power, which brought me to some kind of Android settings (Wipe Cache, & something about clearing or wiping partition). I selected to just reboot, and the phone rebooted fine. I changed the PG32IMG.zip file back to the Froyo, and I can no longer get past the "Recovery" and forcing to do the Update or Bootloop from declining.
So now I don't know what to do, when it comes to the PG32IMG.zip file. I even just changed the Froyo PG32IMG.zip to a 2.3.3 Gingerbread PG32IMG.zip, so now I'm at the correct ROM for rooting. I changed it because I wasn't sure if being at Froyo was preventing me from doing all of this from the beginning, similar to how the most up to date update did as well.
But back to the PG32IMG.zip, what would be the best thing to do with this situation? Should I change it back to the CWM, and deal with the Android error, while still allowing me to get into FASTBOOT. Or should I just keep it as the GB 2.3.3, as it is now? Can I just delete the PG32IMG.zip file altogether, or is it absolutely necessary? It just keeps trying to update to what the file already is, and prevents me from doing anything else.
I think I'm going to try the CWM.zip renamed to PG32IMG.zip and see if I can get it to work.
Click to expand...
Click to collapse
You shouldn't be flashing romantic zips as PG32IMG. That's what clockwork is for. If get it back to froyo, then go to the HTC recovery and follow the clockwork instructions I linked to. But maybe someone more knowledgeable than I can answer better.
Sent from my ADR6350 using xda app-developers app

After you go onto bootloader and it flashes your IMG you either rename the file on your SD card or delete it from your SD card. You will be able to proceed after that has been done
sent from my incredibly paranoid inc2
---------- Post added at 07:00 PM ---------- Previous post was at 06:58 PM ----------
Your s-off so the hard part is done.
sent from my incredibly paranoid inc2

You're right. The PG32IMG.zip was a problem. I removed them from the SD card's root, and it's working as it should.
Now the issue is the instructions in that link. I can't find any update.zip for the phone anywhere. I also can't find any options in the Recovery for "re-install package". I go to "BOOTLOADER" and then "RECOVERY". The Phone then boots to a small image of my phone with a red "!". I press Volume Up + Power button, and it loads the "Android system recovery <3e>". I have a Yellow error at the bottom stating"
E:Can't open /cache/recovery/command
Click to expand...
Click to collapse

You need to flash a new recovery. Do you adb setup on your pc? If not, google it and get it setup.
Here is a link to CWM
http://goo.im/devs/aeroevan/cwm/recovery-clockwork-6.0.1.5-vivow.img
Save it to your adroid-tools folder
You will need to navigate to your anroid tools folder in cmd before issuing the commands below
Code:
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img
---------- Post added at 11:55 PM ---------- Previous post was at 11:44 PM ----------
FYI cmd needs to be run as administrator.

sjpritch25 said:
You need to flash a new recovery. Do you adb setup on your pc? If not, google it and get it setup.
Here is a link to CWM
http://goo.im/devs/aeroevan/cwm/recovery-clockwork-6.0.1.5-vivow.img
Save it to your adroid-tools folder
You will need to navigate to your anroid tools folder in cmd before issuing the commands below
Code:
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img
---------- Post added at 11:55 PM ---------- Previous post was at 11:44 PM ----------
FYI cmd needs to be run as administrator.
Click to expand...
Click to collapse
screenshot for you

The version I have has the correct files in the "platform-tools" folder.
I get an error with the "adb remount" command, saying "remount failed: Operation not permitted"
When I use the command "fastboot devices", my phone doesn't show up, and it just skips to the next command line, showing nothing. My phone does say "FASTBOOT" though.
Then when I type "fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img" it just hangs at "< waiting for device >"
Maybe I didn't set it up the sdk stuff properly? I'll look more stuff up when I get home later tonight. But I figured, I'd at least post this up now, in case this is showing another issue.

Cleanincubus said:
The version I have has the correct files in the "platform-tools" folder.
I get an error with the "adb remount" command, saying "remount failed: Operation not permitted"
When I use the command "fastboot devices", my phone doesn't show up, and it just skips to the next command line, showing nothing. My phone does say "FASTBOOT" though.
Then when I type "fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img" it just hangs at "< waiting for device >"
Maybe I didn't set it up the sdk stuff properly? I'll look more stuff up when I get home later tonight. But I figured, I'd at least post this up now, in case this is showing another issue.
Click to expand...
Click to collapse
I don't think it's going to work until you get fastboot devices and adb devices to recognize your phone. I wish I could point you in the right direction, but I'm not very experienced with it.
I'm assuming you have the drivers for our phone installed? Some people have to reboot the pc to get those to recognize the device...

Yeah, I'm going to have to do some more digging. ADB device does recognize my phone, at the 6th line on the screen cap I posted. I've restarted the pc multiple times since first trying to get all of this to work.

Cleanincubus said:
Yeah, I'm going to have to do some more digging. ADB device does recognize my phone, at the 6th line on the screen cap I posted. I've restarted the pc multiple times since first trying to get all of this to work.
Click to expand...
Click to collapse
First of all make sure you have fastboot.exe in your tools folder
Code:
adb kill-server
adb start-server
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery***.img

Make sure you have the drivers and that you delete HTC sync from your computer. If you can get it to boot up into the phone make sure you have android debugging turned on.
sent from my incredibly paranoid inc2

sjpritch25 said:
First of all make sure you have fastboot.exe in your tools folder
Code:
adb kill-server
adb start-server
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery***.img
Click to expand...
Click to collapse
Yup, it's there.
Did those commands, and it ended in the same result. No errors or "waiting" messages at the flashboot devices command, but it didn't show my device either.
Jasonp0 said:
Make sure you have the drivers and that you delete HTC sync from your computer. If you can get it to boot up into the phone make sure you have android debugging turned on.
sent from my incredibly paranoid inc2
Click to expand...
Click to collapse
Definitely installed driver. I originally tried to install the driver I previously used with my original s-off/root/rom, but it didn't work with Windows 8 (previous PC was WinXP), so I found the correct one for my OS. The "adb devices" command never found my phone, before installing the current driver.
I never installed HTC Sync. Just double checked the "Uninstall or change program" in the Win8 control panel (previously "Add/Remove Programs") to make sure it didn't get installed with out my knowledge, and it's not in there.
If you mean on the phone: "Settings" > "Applications" > "Development" > check box for "USB debugging", then yes. If it's a command of some sort, then no & I don't know how to do it.
I'm also making sure to run these commands by right-clicking the Command Prompt and selecting "Run as administrator", before doing these commands.