Hi
I brought a rooted desire a month ago and 2 nights ago it restarted its self and now is stuck on the boot logo. Fastboot and Recovery both go to HTC boot screen and hang there too.
I have tried taking the battery out and leaving it.
I have tried removing the SD card and booting it.
Also from what i can tell usb debugging is disabled in the phone settings...
I Wont try and pretend that i know what i'm doing here i rather out of my depth trying to sort this out so please bear with me,
i'm using windows xp (x32)
Thank you for your time and patience
EDIT: I think it has a rooted froyo rom on there also. (version unknown)
Chuck_Neus said:
Hi
I brought a rooted desire a month ago and 2 nights ago it restarted its self and now is stuck on the boot logo. Fastboot and Recovery both go to HTC boot screen and hang there too.
I have tried taking the battery out and leaving it.
I have tried removing the SD card and booting it.
Also from what i can tell usb debugging is disabled in the phone settings...
I Wont try and pretend that i know what i'm doing here i rather out of my depth trying to sort this out so please bear with me,
i'm using windows xp (x32)
Thank you for your time and patience
EDIT: I think it has a rooted froyo rom on there also. (version unknown)
Click to expand...
Click to collapse
Not sure if there is an easier solution..But, have you tried unrooting with a RUU?
i haven't tried, can i unroot without a Goldcard?
Chuck_Neus said:
i haven't tried, can i unroot without a Goldcard?
Click to expand...
Click to collapse
Only if you have an unbranded Desire.
But..you try the following in Recovery..It may be stuck in a loop and yet communicate with the pc..
Get into recovery (with an sdcard inside), and issue the following command from your PC (You must have the sdk installed and must be the Tools folder:
Code:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid>c:\goldcard.txt
start c:\goldcard.txt
A text file opens up with a code. If it does you can make a goldcard now. Use the goldcard tool.
Two options to try solving your problem:
METHOD 1
If goldcard can be created ok, then you may proceed with flashing the RUU. Be careful to use the newest version on shipped-Roms. Older ones can brick your device if it's SLCD. We'll use Method 1 as last resort. Try Method2 first.
Note:
Before you try this out, CREATE A GOLDCARD EVEN IF YOU THINK YOUR DEVICE IS UNBRANDED.
Flashing an RUU always has the potential to softbrick your device. Recovering may be difficult unless you have a goldcard and extensively know some advanced methods to unbrick the device/or willing to research it
METHOD2: FLASHING CLOCKWORKMOD DIRECTLY WITH FASTBOOT (Will work only on rooted ROM. Will need goldcard if branded)
Since your current recovery is corrupted, you can try flashing the Clockworkmod again from Fastboot. In fact, it may be safer to try this option first rather than unrooting.
Download the latest image for Clockworkmod recovery
Rename the ClockworkMod Recovery Image to simply recovery.img.
Boot into the bootloader mode.
Turn the phone off.
Insert goldcard
Press the back button & power at the same, until you are booted into bootloader mode.
Connect the phone to the computer.
On the computer, open the command prompt/terminal & navigate to the Android SDK Tools folder.
Issue the following command:
Code:
fastboot flash recovery recovery.img
Try Method2 and tell me if it worked for you.
method 2 didnt work
Code:
flash recovery recovery.img
sending 'recovery' (4216 KB)... OKAY [ 0.578s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.045s
Chuck_Neus said:
method 2 didnt work
Code:
flash recovery recovery.img
sending 'recovery' (4216 KB)... OKAY [ 0.578s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.045s
Click to expand...
Click to collapse
Your goldcard must be inside the device. Try again with goldcard? Did you get the CID for goldcard creation. Follow Method 1 till creation of goldcard. Dont run the RUU though
Use the goldcard tool to make it simpler.
Tried Following method 1 but all i get is access denied... Could this be down to USB Debugging not being on?
Chuck_Neus said:
Tried Following method 1 but all i get is access denied... Could this be down to USB Debugging not being on?
Click to expand...
Click to collapse
At what point?
Dont run the RUU. Just issue the code I've written:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid>c:\goldcard.txt
start c:\goldcard.txt
Try this from Fastboot and from the stuck recovery screen. What does the textfile display>?
Note that your USB device must get recognized within Windows. After the device is notified as connected in Windows (notification icon and a sound in the PC), To check, type this command and see if it shows a code (the serial of device)"
Code:
adb devices
when i type adb devices it says "list of devices attached" and that's it. Could there be a driver problem or something more sinister?
Chuck_Neus said:
when i type adb devices it says "list of devices attached" and that's it. Could there be a driver problem or something more sinister?
Click to expand...
Click to collapse
Your device is not interacting with adb. You could try the following:
Code:
Fastboot devices
If this one works, it's a problem with only adb. More sinister if that is so. Try to boot into Fastboot, Recovery and Simple Boot (See my thread here, and read the part which tells you how to boot into each), and try the adb devices command in each. If it works in any one, get the CID and proceed with goldcard.
If you cant get the CID, you cant get the goldcard. Two solutions exist-1.Use the correct updated RUU and flash to stock. 2.Use Teppic74's guide to downgrade (Search XDA for it) and then flash a lower RUU for your device.
Note that without a goldcard, only the appropriate RUU will work.
fastboot devices gives
Code:
HT05SPL07600 fastboot
Problem with only adb then. See my post and the other thread..
Thank you for your time and help. I sure hope this works
problem fixed unrooted back to stock.
Related
Guys,
I am lost. I thought I am not stupied, but it seems I am.
Here's the problem:
After flashing a couple of different ROMs somehow I wasn't able to access recovery any more - I always used a batch to load the recovery, I never flashed in permanently. Now I only see the white HTC screen.
So I unrevoked, a new RUU plus rerevoked but both scenarios give the same result: unrevoked it stopping when it should boot in recovery.
Also I used some batch scripts flying around. and the problem should be that it is not possible to write the recovery.
my phone:
BRAVO DVT1 SHIP S-OFF
HBOOT-0.75.0000
MICORP-031d
TOUCH PANEL SYNT0101
Radio 0-4.05.00.11
Any clue how I can restore recovery???
Thanks in advance.
M
Can you get into fastboot? If you can, go to shipped-roms.com and find your original stock RUU. Connect your phone and place it in Fastboot mode (select Fastboot and wait until it says FASTBOOT USB and run the RUU your phone came with originally). You may need to insert a Gold Card into your phone if you are running a generic one).
I;m just thinking... it could also be a USB brick, see this guide here for a possible fix:
http://forum.xda-developers.com/showthread.php?t=691187
If i were you, i would steer away from manually accessing recovery using batch scripts/pushfiles, especially when connected via USB, as this can always potentially brick your phone. As you were saying, use unrEVOked with a permanent custom recovery like Amon-Ra, or use ClockworkMod. This will make it virtually impossible to brick your phone.
Hope you get it fixed soon.
You could also try running unroked from a linux live cd. People have less problem running it true linux.
Thank you guys for trying to help.
I installed the RUU from fastboot and still... no recovery in sight. I looked into USB brick as well, but all solutions require a recovery mode - which I don't have. Also I don't this it is a bricked misch partition. But hell, what I know. I just bricked this *****.
After RUU I ran unrevoked again. all fine until booting the recovery: White screen and HTC logo. But at least I have root ;-)
Is it possible that there is something wrong with the rights? I tried:
r5-desire-root/fastboot-mac boot recovery-clockwork-2.5.0.7-bravo.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
Any clue?
Cheers
M
tameike said:
Thank you guys for trying to help.
I installed the RUU from fastboot and still... no recovery in sight. I looked into USB brick as well, but all solutions require a recovery mode - which I don't have. Also I don't this it is a bricked misch partition. But hell, what I know. I just bricked this *****.
After RUU I ran unrevoked again. all fine until booting the recovery: White screen and HTC logo. But at least I have root ;-)
Is it possible that there is something wrong with the rights? I tried:
r5-desire-root/fastboot-mac boot recovery-clockwork-2.5.0.7-bravo.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
Any clue?
Cheers
M
Click to expand...
Click to collapse
Try placing the 'recovery-clockwork-2.5.0.7-bravo.img' in the tools folder of the android sdk folder, and then drag the tools folder into terminal and type:
./fastboot-mac boot recovery recovery-clockwork-2.5.0.7-bravo.img (to boot the clockwork recovery through fastboot)
or this:
./fastboot-mac flash recovery recovery-clockwork-2.5.0.7-bravo.img (to flash the clockwork recovery through fastboot)
Hope this helps some.
Tried this just now:
./fastboot-mac flash recovery ../recovery-clockwork-2.5.0.7-bravo.img
sending 'recovery' (4216 KB)... OKAY
writing 'recovery'... FAILED (remote: not allowed)
./fastboot-mac boot recovery ../recovery-clockwork-2.5.0.7-bravo.img
cannot load 'recovery'
Does this mean anything to anyone?
Thanks guys...
You are S-on, maybe running alpharev so that you are S-off can help you. But I have no experience with that. If you are S-Off you can use the fastboot commands to push the recovery.
It's possible that the stock RUU you ran earlier may have had an HBOOT update in it forcing s-off to change to s-on, causing the HBOOT to be overwritten.
I s-off'ed not too long ago (i know... i know... it does sound dirty ) and it is a risky procedure as it could end up bricking your phonr entirely if not done correctly. I'm am not certain on what exact procedure to follow on Mac, running Windows 7 here...
If you want to give it a try yourself, you can follow what is suggested in the following guide:
http://forum.xda-developers.com/showthread.php?t=805811
This is what i did to security unlock my phone:
I ensured USB Debugging was enabled.
Downloaded this AlphaRev 1.5 HBOOT reflash utility (.iso file)
Important: Before starting this procedure, it is very important that you do not have your phone sync'd to your PC, as you should only connect the phone to the computer when prompted after the .iso is booted.
I burned the .iso to a bootable CD (you can also boot from a DVD disc or USB key).
Note: You may need to change the boot order in your computer BIOS to either boot from a CD/DVD or external device, like a USB key.
I rebooted my computer and booted from the CD I created, and pressed enter at the flashing cursor - you will know that you have successfully booted the .iso as the screen will display some Tiny Core Linux logos. While I waited, I powered on your phone but I made sure that I had not connected it to my PC via USB. After the initial loading, the screen will prompt you to press any key to continue. After this, I was prompted to connect the phone via USB.
Make sure you wait and only connect your phone via USB when prompted on your Mac. When you are ready, connect the phone via USB (while you are doing this, check the status of your phone as you may be prompted to allow super user permissions to continue). During this process, do not interact with your phone and just let it run it's course. Your phone will automatically reboot a few times during the 3 stages, so do not stop the procedure at any cost.
When it is done, go back into the Bootlader and at the top of the screen, it should show the AlphaRev text and s-off.
Next, you will need to flash the custom clockwork recovery here - http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.7-bravo.img
Then, simply follow and enter the command I posted above (make sure you place the recovery image in the tools folder of the android sdk folder, and execute the fastboot command via the Terminal) to flash the custom clockwork recovery from fastboot, and it should then hopefully get you back on track.
Let us know how you get on with this. I will keep my fingers crossed for you
Regards,
Mas.
Another case of someone with a factory unlocked bootloader...where are they coming from or have HTC just sent them all out like it!?!?!
EddyOS said:
Another case of someone with a factory unlocked bootloader...where are they coming from or have HTC just sent them all out like it!?!?!
Click to expand...
Click to collapse
I think these s-off supplied devices are supplied specifically for developers as developer phones... i think
Hello everyone,
I think this might be my first post here.
Anyways, I have a rather depressing problem. I have my phone rooted running cm 6.1, and when i was about to go to sleep last night, it randomly started to reboot. At first i did not think anything of it because i have had my phone do this several times with cm. But then i became more concerned, it would go into a boot loop at the splash screen (htcEVO4g). Once again, i have had this happen before and i would do a wipe and reinstall the rom, but this time it did not work. I could not get into recovery. I am able to access only the boot loader.
So, i tried to install the stock pc36img. Now when i start my phone, it vibrates 5 times followed by the flashing green led. it also does this when i try to go into recovery. I am still able to get into the bootloader.
i tried doing the ruu thing, and different pc36img
I just got back from the sprint store. After waiting 3 hours, they were not able to fix it. I had told them it was rooted and everything.
If there is no way to fix it, is there at least a way i can turn s-on? That way, i can send it back to sprint.
That is odd. As far as I know, if you used unrevoked forever at any point, the only way to get s on is to flash the unrevoked s on tool, using recovery. But you don't have recovery. If I were you, I would use your computer to format your sd card to fat 32 ( after backing it up, of course) , then put a pc36img on your sd card, and try to flash again using the bootloader. You could also try putting a pc36img of amon ra recovery on your sd card, and flashing that with the bootloader. Maybe you can get recovery back, and flash a rom, or the s on tool. Hope you get it worked out.
Sent from my PC36100 using XDA App
If I were you I would try the newest pc36img.zip and if that does nothing a pc36img.zip of Amon ra. If that doesn't work go to the last link in my sig about splash screens. In that tut I give, I say how to manually run an ruu. Use the pc36img.zip with the fast boot commands from the thread. Hope this helps.
i tried formatting the sc card, and that did not do anything. How can i connect my phone to adb?
marzban123 said:
i tried formatting the sc card, and that did not do anything. How can i connect my phone to adb?
Click to expand...
Click to collapse
Just Download the android SDK and follow the steps. There are some pretty excellent tutorials on XDA and other sites that will walk you through the whole process.
I want to weigh in here for just a moment. There is no way your phone is completely botched, unless it has experienced physical damage (including any overheating). By the way, you running any SBC kernels?
I would look into learning your way around ADB, I think it's a necessary tool for anyone who wants to flash and alter their android phones, unfortunately things have become so easy that many out there haven't had to learn these tools and how to use them.
Seriously, go mess with ADB, I am sure you can get it running again.
Some good info here http://forum.xda-developers.com/showthread.php?t=865204 on using ADB and other methods that may help you.
marzban123 said:
I had told them it was rooted and everything.
Click to expand...
Click to collapse
ouch... they should give you new phone for being honest
ok, so i connect the phone, and in device manager i see "Android Bootloader Interface"
i opened up command prompt, and tried to push a file to the phone and i got this
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Andrew>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb push PC36IMG.zip /sdcard/
error: device not found
C:\android-sdk-windows\tools>
you sure your usb cable is good? id run the RUU to go back to stock & unroot you. then start over from scratch.
i just tried a different cable. No luck
I have already tried a stock ruu, that still does not let me get into recovery or turn s-on
your sorta up ****s creek here if you told sprint you rooted. they probably flagged your account.
is your sd card good? try another, fully formatted for fat32 only. then try the s-on flashable zip. that's all i can think of for you to do. if you need another evo, im sure you can pick one up for cheap on craigslist.
nobody ever took my information
Is there an s-on flashable zip?!?! where can i find it? i have searched before with no luck
first of all, adb doesnt work in bootlaoder. select fastboot, then plug in. you should see fastboot usb come up on the phone. now try using fastboot commands instead. not sure where to download fastboot commands. i have the mac ones if you need them. then do this
with the pc36img.zip ON YOUR COMPUTER:
after flashing s-on tool http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip
fastboot oem rebootRUU
you should see a black screen with silver htc lettering
fastboot flash zip pc36img.zip (do this command with the pc36img.zip in the same directory as fastboot)
you should see a green bar appear under htc and a bunch of lines on the comp. make sure it successfully completes, then type:
fastboot reboot
done.
but make triple sure you are s-on first.
thank you very much, that makes things ALOT clearer.
I am still a huge noob to this stuff so i need to ask you some silly questions:
i found out the commands for fastboot in a wiki,
http://wiki.cyanogenmod.com/index.php?title=Fastboot
but i dont really understand how to use them. can someone please give me a little clarification.
well, first check your sdk and see if you have fastboot.exe. i know the mac one doesnt come with it. if you dont google it. if you do, cd to the directory (hold shift and right click in the folder. select open command prompt here) and boot phone into fastboot. make sure it is in fastboot usb mode. then do the commands.
i have the fast boot exe and i am in command prompt.
when i say i am a noob, i really mean it.
for example, when i try a simple command like checking the serial number, i will input
c:\android-sdk-windows\tools>fastboot <-s>
or
c:\android-sdk-windows\tools>fastboot -s
or
c:\android-sdk-windows\tools>fastboot <serial number>
it says
the syntax of the command is incorrect.
i really dont know how to use this stuff
ok forget the last post,
i figured that out
what partition do i want to flash and with what file?
No partition just use the pc36img.zip in ruin more and type fastboot flash zip pc36img.zip.
Sent from my PC36100
C:\android-sdk-windows\tools>fastboot flash zip PC36IMG.zip
sending 'zip' (171727 KB)... OKAY [ 30.475s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 30.477s
C:\android-sdk-windows\tools>
Click to expand...
Click to collapse
i researched the "(remote: not allowed)" error message, and everyone says its cause when the phone is set to s-on. However, on my phone it says s-off.
what the heck?
Starting from a new stock Desire HD, I have attempted gaining root access using Visionary (r14). Temproot worked, but permroot apparently failed. My device rebooted, but didn't come back up - I get the phone-with-red-triangle screen.
If I pull the battery and then boot into the bootloader, using the Image CRC menu option I can see that my system partition has been modified (but all other partitions are unchanged):
<redacted>
Do I have any options available to me now, or am I screwed?
My phone is a stock Desire HD A9191 (stock HBOOT S-ON, stock recovery, stock radio S-ON):
Code:
Branded (Vodafone Australia)
<redacted>
Is there magic process that can be done to re-flash the faulty system partition?
Any help would be hugely appreciated. Sorry to make this my first post to the forums, but I'm well and truely stuck... hopefully not permanently, but I have that sinking feeling
What happens when on the red triangle screen, you HOLD the volume up, and then press power button? I think this will take you to stock recovery. Reboot if you have the option, or Wipe data & factory reset.
Sent from my Desire HD using XDA App
Thanks UpInTheAir.
At the red-triangle screen I press vol-up and power, and it displays the Android system recovery screen. It shows the options:
1 Reboot system now
2 Apply sdcard:update.zip
3 Wipe data/factory reset
4 Wipe cache partition
I've tried (3) and (4) and then rebooted, but it does not help - the phone continues to boot into the red-triangle screen.
It looks to me like the system partition was incorrectly modified / corrupted by visionary, and somehow flashing it back to a known-good condition seems like the only way forward...
Is it possible to use option (2) to flash a new rom if I package it up and put it on the SD card somehow? My phone is branded vodafone-australia, and they have not published any RUU update files yet. I gather that using a WWE rom update from HTC will not be possible?
Try DL think stock 1.32 RUU
Rename to PD98IMG.zip (not .zip.zip, do not extract)
Put PD98IMG.zip onto sdcard
HOLD volume down, and power on -> this will boot into Bootloader
Start update and follow the prompts
I hope this helps, but as always, please don't hold me responsible if anything goes pear-shaped.
Thanks again. Downloading now, and will update this post when I've tried it out. Cheers.
You'll need to make a Goldcard to flash this ROM (if your phone is branded).
http://android.modaco.com/content/general-discussion/305672/creating-a-goldcard/
Also for more help follow this thread http://forum.xda-developers.com/showthread.php?t=1035027 (follow the bit about flashing the PD98IMG.zip)
a33a said:
You'll need to make a Goldcard to flash this ROM (if your phone is branded).
http://android.modaco.com/content/general-discussion/305672/creating-a-goldcard/
Also for more help follow this thread http://forum.xda-developers.com/showthread.php?t=1035027 (follow the bit about flashing the PD98IMG.zip)
Click to expand...
Click to collapse
Won't the Gold Card be useless if the system partition is already corrupted?
This was to be done before using visionary?
Thanks a33a.
My phone doesn't boot (I can only get to the bootloader menu, or the red-triangle screen). I tried talking to it with ADB, but it says "device offline".
The instructions for making a gold-card appear to require you using adb to talk to the phone to get it to tell you some long id number... I don't think it's possible for me to do this.
Is there a work around or some other way?
Did the PD98IMG.zip work?
Did u update the HTC drivers for the usb before. The adb needs the latest drivers for Windows to communicate.
If u can't create a goldcard than u should try and borrow 1 from a friend that already rooted his dhd. It might work that way. If not than u have to bring it to HTC and have it reflash.
When you tried ADB;
1. Make sure your phone is in FASTBOOT USB (HOLD volume down + power on -> Bootloader)
2. Connect to PC
3. CMD (Command Prompt) cd\............android\android-sdk-windows\tools\ (or whewrever the adb.exe & fastboot.exe is)
4. Type fastboot devices
5. You should get pyour device serial number HT............
But as I said, if the partition is screwed up, it is pointless with the goldcard?........
Edit: Memory coming back......You only need the Gold Card if you flash a stock ROM and require OTA updates? Without this you can't get the updates. So not having it shouldn't stop the flash?
Unfortunately the PD98IMG.zip did not work.
As suspected, the bootloader found it, loaded it, checked it, then displayed:
Code:
CID incorrect!
Update Fail!
Press <POWER> to reboot.
I haven't tried creating the gold card yet. I'm not holding out much hope, because with the device not booting into the OS, I don't think you can get adb to connect.
When the phone was working, I was able to use ADB to install apps and run commands from the shell, so I'm pretty sure the USB drivers are OK (I've installed the latest HTC Sync, which included the usb drivers and adb.exe).
I don't know anyone with another Desire HD, let alone anyone who has created a gold card... maybe someone on here with one can zip up the files and send them to me?
Did you try through fastboot? Sorry I don't have one as wasn't carrier branded. I never had intention to keep the stock, so never bothered. I will keep an eye open for ideas though.
I suppose you would get the same if you rename it to update.zip & try flash through the recovery / update. My guess is yes, but doesn't hurt to try?
Sent from my Desire HD using XDA App
I'm just trying the fastboot method now (downloading and installing the SDK as I type).
I'll let you know how it goes.
Thanks for sticking around to help out.
If no good, look on the bright side. There will be no evidence on your phone about the attempted root, still s-on etc. With the system partition corrupt, you could send it back and claim ignorance, not sure what happened. I would think you would have a very goof chance of repair (htc flash) or replacement.
Well hope you have some luck first though.
Edit: meant s-on
Sent from my Desire HD using XDA App
Yeah, I was considering that -- all partitions except system are unmodified and stock, and both S-flags are S-ON. Using the bootloader to wipe cache and data, should erase any evidence that I was attempting to root the phone.
Fingers crossed they will replace / repair under warranty -- if it comes to that!
Okay, as per the earlier post, I've put the phone into FASTBOOT USB mode, and used the Android SDK fastboot.exe program, which gave me back a 12 digit number beginning with "HTxxxxxxxxxx".
However, the linked gold-card creation guide says to run "adb shell cat /sys/... " which does not work -- adb returns "error: device not found". Presumably this is because you can't talk to the phone when it's in the bootloader.
What should I do with the "HTxxxxxxxxxx" value? The goldcard guide doesn't mention it as far as I can tell...
That's your device serial number, meaning you can ay least talk with it via fastboot. Try substituting 'fastboot' instead of 'adb'. Your connected in Fastboot, ADB command is when your phone is powered up and connected in charge only, usb debugging enabled.
Sent from my Desire HD using XDA App
Okay, I've tried a couple more things:
Renaming PD98IMG.zip to update.zip and selecting "Apply sdcard:update.zip" from the recovery menu. This failed, displaying "E:Can't open /cache/recovery/command ---- invalid operation ----"
Then I tried issuing ADB commands using fastboot.exe, but fastboot doesn't support the shell parameter, so "fastboot shell cat /sys/...." doesn't work.
It does look like fastboot can be used to flash various parts of the device though... I wonder if this is worth looking into a bit more?
ie: fastboot's usage output says:
Code:
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
I tried "fastboot update update.zip" giving it the renamed PD98IMG.zip file, but it complained of:
Code:
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in '....garbage characters...'
Does anyone know how and what to feed to fastboot to get to force-flash the system partition?
UPDATE: yeah I thought this might have been too easy... This link suggests that you can't flash a production device with fastboot unless you already have ENG S-OFF (which I don't).
http://wiki.cyanogenmod.com/index.php?title=Fastboot
Hey there,
Got a bricked rom so wanna flash my Desire again.
My problem is my Recovery doesnt work.(Stucks in Mainscreen)
So i tried to flash it with fastboot (command: fastboot flash recovery recovery.img )(Security is Off) but during this command it stack at 'sending 'recovery' <3398>...'
Does anyone know why?
Help Please :S
Is 'fastboot devices' detecting the phone?
Sent from my HTC Desire using XDA App
my phone detects the fastboot usb
and in the command line doesn't stand [waiting for device] like when the phone is not connected
edit:
ah i guess you mind the fastboot devices command
yeah there is one device HT072...6 fastboot
Now I also got another error here the Details:
D:\Nero\Desktop\android-sdk-windows\tools>fastboot flash recovery recovery-cloc
kwork-3.0.0.5-bravo.img
sending 'recovery' (3398 KB)...
FAILED (status read failed (Too many links))
finished. total time: 0.002s
D:\Nero\Desktop\android-sdk-windows\tools>fastboot flash recovery recovery-cloc
kwork-3.0.0.5-bravo.img
sending 'recovery' (3398 KB)...
edit:
okay got it and flashed recovery v3.0.0.5 (i know not uptodate there is already 5.0.0.2 or sth =P)
looked up for the other error here and found a solution had to take another usb-port
but i still got the problem that i can not "install zip from sdcard" when i select it, i get a black screen with the icon of clockworkmod :S
try this http://forum.xda-developers.com/showthread.php?t=839621
you might have a PVT4 device which doesn't work with cwm
i already flashed my desire about 4times with clockworkmod
btw just checked its pvt1
but ill try alphaRev just give me a sec
after flashing it with that recovery it works
still don't know why clockworkmod won't this time cause as mentioned i used it for some ROMs before and was quiet simple
how ever at least it works again BIG thanks!
NeroBoron said:
after flashing it with that recovery it works
still don't know why clockworkmod won't this time cause as mentioned i used it for some ROMs before and was quiet simple
how ever at least it works again BIG thanks!
Click to expand...
Click to collapse
no prob, here to help
NeroBoron said:
Hey there,
Got a bricked rom so wanna flash my Desire again.
My problem is my Recovery doesnt work.(Stucks in Mainscreen)
So i tried to flash it with fastboot (command: fastboot flash recovery recovery.img )(Security is Off) but during this command it stack at 'sending 'recovery' <3398>...'
Does anyone know why?
Help Please :S
Click to expand...
Click to collapse
Hi,
I have a same problem with stucking on sending recovery...can u tell me how to resolve the problem??
mullamadd said:
Hi,
I have a same problem with stucking on sending recovery...can u tell me how to resolve the problem??
Click to expand...
Click to collapse
firstly, make sure you're phone is actually seen by the PC tpye in cmd (if you;ve got fastboot setup)
Code:
fastboot devices
should come up with you're phones serial number. If nothing comes up then a) if havent got fastboot/ SDK setup, or b) you're S-ON.
Secondly make sure you're S-OFF... if you're not you can't flash things..
thirdly, if you're S-OFF and your phone IS seen, make sure you're in FASTBOOT and not in BOOTLOADER.
to boot into fastboot you poweroff then hold BACK and POWER. or you boot it from the bootloader..
my advice to you, nothing else I can think of. At least when I'm not sober anyways
bortak said:
firstly, make sure you're phone is actually seen by the PC tpye in cmd (if you;ve got fastboot setup)
Code:
fastboot devices
should come up with you're phones serial number. If nothing comes up then a) if havent got fastboot/ SDK setup, or b) you're S-ON.
Secondly make sure you're S-OFF... if you're not you can't flash things..
thirdly, if you're S-OFF and your phone IS seen, make sure you're in FASTBOOT and not in BOOTLOADER.
to boot into fastboot you poweroff then hold BACK and POWER. or you boot it from the bootloader..
my advice to you, nothing else I can think of. At least when I'm not sober anyways
Click to expand...
Click to collapse
First of all, thanks for your answare.
My S is ON, how to make him go OFF??
When i type in fastboot devices i see my device HT97....
so, my ges is that it recognise my device...
You can download the original RUU from xda rename update put on SD. power off fastboot should run it back to stock I would then use alpharev's site to S-OFF easiest & safest. I'd run it through Virtual Machine as it saves wasting discs just remember to keep turning USB device on as it will unmount a couple of times during the procedure!
Sent from my HTC Desire using XDA App
=JP said:
You can download the original RUU from xda rename update put on SD. power off fastboot should run it back to stock I would then use alpharev's site to S-OFF easiest & safest. I'd run it through Virtual Machine as it saves wasting discs just remember to keep turning USB device on as it will unmount a couple of times during the procedure!
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Sory, i dont get it...downloaded apherev.iso but dont know how to use it?
You better use Revolitionary(.io)
Its more convenient an easier.
Just download ,then on windows you have to install fastboot drivers, the site will give you a betakey (for that you have to type in some phone information), extract the folder ,start revolutionary as admin ,then make sure usbdebugging is enabled an connect to charge only , type in beta key an hit enter.
WRson said:
You better use Revolitionary(.io)
Its more convenient an easier.
Just download ,then on windows you have to install fastboot drivers, the site will give you a betakey (for that you have to type in some phone information), extract the folder ,start revolutionary as admin ,then make sure usbdebugging is enabled an connect to charge only , type in beta key an hit enter.
Click to expand...
Click to collapse
i allredy try that, but, there is no support for my phone HTC magic sapphire 32b.
It sucks, im stuck here..and ther's no way to move acros.
I dont know what you have to do with a magic , sorry about that.
You may look a the magic forum if their is anything written about usbbrick ?
Ask in magic section, not in the one for desire.
Sent from dGB with Transparent XDA App
mullamadd said:
i allredy try that, but, there is no support for my phone HTC magic sapphire 32b.
It sucks, im stuck here..and ther's no way to move acros.
Click to expand...
Click to collapse
Magic ≠ Desire
Hello,
I have an HTC desire, root, s-off, oxygen rom installed.
When I switch on my phone stays in startup screen and does nothing.
Also I have problem accessing to recovery mode through fastboot.
When i choose recovery, the phone restarts and stays again to the startup screen.
-I have tried to access through the ADB (SDK manager) but in cmd cannot find my phone (adb devices)
-But if i write in cmd:
C:\>fastboot devices
everthing is ok it shows the serial number of my phone.
Then i wrote:
C:\>fastboot flash recovery recovery-clockwork-3.0.0.5-bravo.img
sending 'recovery' (3054 KB)...
OKAY [ 0.446s]
writting 'recovery'...
OKAY [ 0.912s]
finished. total time: 1.360s
After that i tried to access to recovery through the HBOOT and my phone restarted once again to the startup screen and did nothing.
Everytime i go to the recovery does the samething.
Does anyone knows what to do?
Thank you
dimitrisvel said:
Hello,
I have an HTC desire, root, s-off, oxygen rom installed.
When I switch on my phone stays in startup screen and does nothing.
Also I have problem accessing to recovery mode through fastboot.
When i choose recovery, the phone restarts and stays again to the startup screen.
-I have tried to access through the ADB (SDK manager) but in cmd cannot find my phone (adb devices)
-But if i write in cmd:
C:\>fastboot devices
everthing is ok it shows the serial number of my phone.
Then i wrote:
C:\>fastboot flash recovery recovery-clockwork-3.0.0.5-bravo.img
sending 'recovery' (3054 KB)...
OKAY [ 0.446s]
writting 'recovery'...
OKAY [ 0.912s]
finished. total time: 1.360s
After that i tried to access to recovery through the HBOOT and my phone restarted once again to the startup screen and did nothing.
Everytime i go to the recovery does the samething.
Does anyone knows what to do?
Thank you
Click to expand...
Click to collapse
try another recovery like RA Recover you can find it here:
http://forum.xda-developers.com/showthread.php?t=839621
I also got some problems with clockworkmod before, so i switched to RA and it works fine for me.
Hi guys and gals,
I'm new here, and I'm just recovering my confidence after the video they make noobs sit through. I have also searched related threads, and have around 20 tabs open in Firefox right now. Alas, no solutions found yet so I'm finally going to make my own thread. The problem is as follows:
I have used MIUI v4 for a while, but it was becoming very slow, battery inefficient and not letting my call or send texts. Therefore I went on to flash the Revolution HD 6.3.1 ROM, which I used when I first flashed my DHD and used to be very stable. After having succesfully flashing the ROM and booting, I was flooded with errors of .acore processes, rendering my DHD unusable. Fortunately USB debugging was still on by default. I then went on to use AAHK, thinking I could flash everything back to the situation when I first rooted and flashed my phone.
After taking well over an hour of being non-responsive, my PC (Win 7) froze up and I had to restart. Hoping the AAHK had finished, I unplugged my phone only to discover that it wouldn't do anything other than show the white screen with the HTC logo. At this point I was already starting to sweat, but when I couldn't even get into the bootloader I fell down to my knees letting out a big NOOOO.
I then finally managed to properly hold down the vol- and power buttons, and I was soon basking in the cold white light emanating from the hboot screen. Unfortunately, selecting either RECOVERY or FACTORY RESET leads to the same white HTC screen. FASTBOOT however, does work, and after reading some other threads I have acquainted myself with SDK, adb and fastboot. adb doesn't seem to work, and it also doesn't show any devices when using the 'adb devices' command. 'fastboot devices' does show my phone, and I can use some commands.
Here comes the real tricky bit. I am now trying to flash a recovery or a new ROM using just fastboot, without USB debugging being on as far as I know. I have the PD98IMG-GB2.zip file on my SDcard (done by taking the card out of the phone, and using another phone as a card reader), and also in a C:\Android folder, that also has adb.exe, fastboot.exe, AdbWinApi.dll and AdbWinUsbApi.dll, as per other instructions in various other threads. I have also used these two commands:
"fastboot erase cache" which got an OKAY.
and
"fastboot oem rebootRUU" which also got an OKAY.
I then tried putting the recovery.img, PD98IMG-GB2.zip and recovery.zip files in my C:\Program Files\Android\android-sdk\platform-tools folder. When using the "fastboot flash recovery recovery.img" command, this got me as far as:
sending 'recovery' <3650 KB>...
OKAY [ 0.607s]
writing 'recovery'...
FAILED <remote: not allowed>
finished. total time: 0.609
This leads me to believe that because USB debugging isn't enabled, I can't write to the flash.
Then tried this:
"fastboot update PD98IMG-GB2.zip"
(short wait)
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to acces zipdata in *jibberish*
I'm at a loss as to anything else I might try. The HBOOT still works, and the phone is S-OFF, but I can't seem to flash anything to my phone. I'm hoping some of you gurus here might know something else. My deepest thanks in advance.
EDIT: with Fastboot Commander I made a print of my device:
-----------------------------------.
SPL/hboot version: 0.85.0024.
Radio version: 26.03.02.26_m.
Main software version: 1.32.405.6.
cid: 11111111.
cpld: none.
product: ace.
mid: pd9810000.
security: off.
build-mode: ship.
-----------------------------------.
EDIT 2: After a horrible day of thinking my phone was dead, but still trying to revive it, I have managed to find a solution! In this thread: http://forum.xda-developers.com/showthread.php?p=26844128#post26844128 there was the suggestion to rename PD98IMG-GB2.zip to just PD98IMG.zip. As soon as I did this, copied the file to my SDcard through another phone, and booting into the bootloader, I was asked if I wanted to upgrade. Hell yeah! After a short wait, I now have my phone up and running again, in a very stock configuration!
After going through a similar situation I can definately relate and know exactly how you felt lol. The OMFG what did I just do moment is hard to get past. I am glad all is working good now though! Good luck!
Thanks for the info. It pointed me in the right direction and now my phone is back up and running
Glad to have helped!
**Edit** I feel like a idiot lol please ignore this post
Experiencing same problem, but with S-on
Hi, I'm having same problem with my friends' Incredible S. Without usb debugging I can't do anything.
Will it make sense if I put my PD98IMG.zip file into sd-card and perform steps you did? Only difference is S-on.
NoorBall said:
Hi, I'm having same problem with my friends' Incredible S. Without usb debugging I can't do anything.
Will it make sense if I put my PD98IMG.zip file into sd-card and perform steps you did? Only difference is S-on.
Click to expand...
Click to collapse
If your friend has a Incredible S, then this thread won´t help you much. This is for the Inspire 4G devices. PD98000 is the boot Device ID, and it will be different in your case. Try to find help in the Incredible S forums first. :good:
Same issues - different outcome
Hey everyone, I'm not sure if there is anyone here to help, but it's worth a shot!
I'm having the exact same issues Richard has and I tried the same solutions and they worked, until a point.
I have a HTC Desire (Bravo) EU that is rooted, S-OFF but doesn't have an OS on it. Before it was experiencing a bootloop with a RD2 sound, because of the Leedroid ROM on it. I fixed the loop but now it can't boot.
I have another HTC Desire from home, that one is fully functional. To test out the differences. :highfive:
""Here comes the real tricky bit. I am now trying to flash a recovery or a new ROM using just fastboot, without USB debugging being on as far as I know. I have the PD98IMG-GB2.zip file on my SDcard (done by taking the card out of the phone, and using another phone as a card reader), and also in a C:\Android folder, that also has adb.exe, fastboot.exe, AdbWinApi.dll and AdbWinUsbApi.dll, as per other instructions in various other threads. I have also used these two commands:
"fastboot erase cache" which got an OKAY.
and
"fastboot oem rebootRUU" which also got an OKAY.
I then tried putting the recovery.img, PD98IMG-GB2.zip and recovery.zip files in my C:\Program Files\Android\android-sdk\platform-tools folder. When using the "fastboot flash recovery recovery.img" command, this got me as far as:
sending 'recovery' <3650 KB>...
OKAY [ 0.607s]
writing 'recovery'...
FAILED <remote: not allowed>
finished. total time: 0.609""
-RichardPNL
I did the exact same steps, only the 'PD98IMG-GB2.zip' was called PB99IMG.zip and my recovery WORKED.
After that I could finally load up the HBOOT, and guess what, I did something stupid.
In the phone there is a SD card with a few zip files on it (the PB99IMG.zip(older version), recovery.zip and a LeedroidROM.zip). I booted into the HBOOT and I was sooooooo happy that I could finally do something with the phone. But then it said "Do you want to update using zip blahblahblah", and I was like "No, I ain't touching anything". But when I layed the phone on the table, I accidentally pressed the volume up button and it updated
Since then the phone is bricked, no way to get into recovery, hboot, bootloader or the OS. Fastboot and adb don't work since the phone won't be recognized by the PC's I'm using and doesn't boot further.
Fastboot used to work when the HTC was having a bootloop, which gave me a chance.
Now I only need fastboot to work again with the phone, but I have no idea how!!
If u need help let me know.
---------- Post added at 11:23 PM ---------- Previous post was at 11:20 PM ----------
DenJento said:
Hey everyone, I'm not sure if there is anyone here to help, but it's worth a shot!
I'm having the exact same issues Richard has and I tried the same solutions and they worked, until a point.
I have a HTC Desire (Bravo) EU that is rooted, S-OFF but doesn't have an OS on it. Before it was experiencing a bootloop with a RD2 sound, because of the Leedroid ROM on it. I fixed the loop but now it can't boot.
I have another HTC Desire from home, that one is fully functional. To test out the differences. :highfive:
""Here comes the real tricky bit. I am now trying to flash a recovery or a new ROM using just fastboot, without USB debugging being on as far as I know. I have the PD98IMG-GB2.zip file on my SDcard (done by taking the card out of the phone, and using another phone as a card reader), and also in a C:\Android folder, that also has adb.exe, fastboot.exe, AdbWinApi.dll and AdbWinUsbApi.dll, as per other instructions in various other threads. I have also used these two commands:
"fastboot erase cache" which got an OKAY.
and
"fastboot oem rebootRUU" which also got an OKAY.
I then tried putting the recovery.img, PD98IMG-GB2.zip and recovery.zip files in my C:\Program Files\Android\android-sdk\platform-tools folder. When using the "fastboot flash recovery recovery.img" command, this got me as far as:
sending 'recovery' <3650 KB>...
OKAY [ 0.607s]
writing 'recovery'...
FAILED <remote: not allowed>
finished. total time: 0.609""
-RichardPNL
I did the exact same steps, only the 'PD98IMG-GB2.zip' was called PB99IMG.zip and my recovery WORKED.
After that I could finally load up the HBOOT, and guess what, I did something stupid.
In the phone there is a SD card with a few zip files on it (the PB99IMG.zip(older version), recovery.zip and a LeedroidROM.zip). I booted into the HBOOT and I was sooooooo happy that I could finally do something with the phone. But then it said "Do you want to update using zip blahblahblah", and I was like "No, I ain't touching anything". But when I layed the phone on the table, I accidentally pressed the volume up button and it updated
Since then the phone is bricked, no way to get into recovery, hboot, bootloader or the OS. Fastboot and adb don't work since the phone won't be recognized by the PC's I'm using and doesn't boot further.
Fastboot used to work when the HTC was having a bootloop, which gave me a chance.
Now I only need fastboot to work again with the phone, but I have no idea how!!
Click to expand...
Click to collapse
First of all...update SDK on your PC..ALL VERSIONS...this will help PC see phone via platform tools folder. There u can issue fastboot commands