Related
After a Update failure my Desire isn’t feeling to good...
I was running oxygen-2.1.6 on my Desire but decided to go back to stock. BAD choice!
Now when power on I get the black htc screen with the triangles in the corners. When I try volume down + power on I get the same black screen.
If I start the RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe again to do the same update I get ERROR [152]:IMAGE UPDATE ERROR with the option to Recover which gives me a black screen until I pull the USB connection. Then I get a fastboot lock a like screen.
AlphaRev CM7 r2
BRAVO PVT3 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-4.06.00.002_2
Aug 10 2010, 17:52:18
RUU
[1] BOOT - OK
[2] BOOTLOADER - Bypassed
[3] RADIO_v2 - OK
[4] RADIO_CUST -OK
[5] RECOVERY - OK
[6] SPLASH1 - OK
[7] SYSTEM - Fail-PU
[8] USERDATA - OK
Partition update fail!
Update Fail!
I’ve tried many of the other RUU but they all results in ERROR [110]: FILE OPEN ERROR […] Click ‘Exit’ to quit
How do I get past this?
Have no goldcard...
All I want is my phone up and running again…
Any solution out there?
//Tommy
Everything is fine except you can't RUU over the hboot you have as /system is too small for the Rom.
You need bravo stock. You need to either fastboot flash the downgrader from alpharev and run the RUUagain or fast boot flash a recovery img and restore a nandroid backup
Sent from my HTC Desire using XDA App
Yep downgrade the hboot first from AlphaRev website then continue.
Swyped...
Ok no!! Do not flash the downgrader just yet!! Flash the stock alpharev hboot but not the downgrader, otherwise that will put you s-on when you flash the RUU and if something goes wrong you wont have s-off to help. So as I said just flash the stock hboot, restart and then try the RUU again. Sorry it feels like I'm hanging my ass over the ragged edge when I'm S-ON
bortak said:
Ok no!! Do not flash the downgrader just yet!! Flash the stock alpharev hboot but not the downgrader, otherwise that will put you s-on when you flash the RUU and if something goes wrong you wont have s-off to help. So as I said just flash the stock hboot, restart and then try the RUU again. Sorry it feels like I'm hanging my ass over the ragged edge when I'm S-ON
Click to expand...
Click to collapse
Sounds great but how do I do that?
My phone is as I said not responding to vol. down + power for the bootloader or the back + power for fastboot. Black htc screen with the triangles in the corners on both cases. I can’t flash anything from my phone (that I know off) since I can’t get to the fastboot or the bootloader. How do I use the .img file from alpharev.nl? I don’t know how to run the PB99IMG from my phone as it is now.
I’ve tried to run the alpharev cd again but with no luck.
“Waiting for your device… hub 2-0:1.0: unable to enumerate USB device on port [number of the USB port]”
My computer recons the phone, or at least that it’s an Android 1.0 device, when I’m in windows (both win 7 and XP) so can I do anything from there?
try download Android flasher 1.8 in dev.section
after that try to flash CWM recovery 3.0.0.5 and alsom try to flash stock Hboot
all these steps via android flasher can be done
edit - you can run alpharev but only with stock rom and hboot
in other way rooted phone with custom rom wont work with alpharev, there is also recommendation on the site about stock rom in case to use alpharev boot cd
I had the same problem today and I flashed the stock hboot with android flasher 1.8 and it worked. Thanks AssassinSvK.
This did the trick! Thank you =)
I have a problem with fastboot, I can`t acces it when I hold down the volume button and the power button nothing happens rom starts normally and everything works fine except the fastboot. What caused this problem? I flashed new rom and new radio, maybe something went wrong
adobric said:
I have a problem with fastboot, I can`t acces it when I hold down the volume button and the power button nothing happens rom starts normally and everything works fine except the fastboot. What caused this problem? I flashed new rom and new radio, maybe something went wrong
Click to expand...
Click to collapse
Settings/Application/untick fast boot
Alternative reboot phone and hold volume down at beginning of reboot process.
SwiftKeyed from Oxygen with Transparent XDA App
andQlimax said:
Settings/Application/untick fast boot
Click to expand...
Click to collapse
Thank you! This solved the problem
AssassinSvK said:
try download Android flasher 1.8 in dev.section
after that try to flash CWM recovery 3.0.0.5 and alsom try to flash stock Hboot
all these steps via android flasher can be done
edit - you can run alpharev but only with stock rom and hboot
in other way rooted phone with custom rom wont work with alpharev, there is also recommendation on the site about stock rom in case to use alpharev boot cd
Click to expand...
Click to collapse
So I am having the same issue here but I have tried what you suggested. I get the following error when flashing CWM recovery 3.0.0.5 (under recovery tab)
The system cannot find the path specified.
The system cannot find the path specified.
cd data\
taskkill /F /IM adb.exe
taskkill /F /IM fastboot.exe
taskkill /F /IM fastboot.exe
ERROR: The process "fastboot.exe" not found.
adb.exe reboot bootloader
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
I then tried to flash back the HBoot (HBOOT) but get the following error
The system cannot find the path specified.
The system cannot find the path specified.
cd data\
taskkill /F /IM adb.exe
ERROR: The process "adb.exe" not found.
taskkill /F /IM fastboot.exe
ERROR: The process "fastboot.exe" not found.
adb.exe reboot bootloader
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
Just an update what I have tried
Have tried to push the following to the phone via windows “RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed”. Loads and at about 55%, says that there is an issue. Try to restore but no success. When I unplug the USB, I get the following screen
AlphaRev CM7 r2
BRAVO PVT3 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
RUU (highlighted orange)
[1] BOOTLOADER- Bypassed
[2] RADIO_V2- OK
[3] RADIO_CUST- OK
[4] BOOT- OK
[5] RECOVERY- OK
[6] SYSTEM- Fail-PU
[7] USERDATA- OK
[8] SPLASH1- OK
[9] SPLASH2- OK
Partition update fail!
Update Fail
When I try to load boot loader (-ve + power), it just starts up with the screen with HTC in the middle and 4 x triangles with “!” in all 4 corners..
So in short, am I screwed and should I be looking for another phone?
You cannot run ruu because the hboot version you use is protected against overwriting by ruu or ota. You have to flash bravo downgrader first.
SwiftKeyed from Oxygen with Transparent XDA App
MatDrOiD said:
You cannot run ruu because the hboot version you use is protected against overwriting by ruu or ota. You have to flash bravo downgrader first.
SwiftKeyed from Oxygen with Transparent XDA App
Click to expand...
Click to collapse
Hey
So I have run bravo downgrade and the screen has the following
BRAVO PVT3 SHIP-ON
HBOOT-0.83.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO 5.11.05.14
Jun 10 2010, 12:12:05
When I try and and hit "Recovery" on "recovery-clockwork-3.0.0.5-bravo" i get the following error
ERROR: The process "fastboot.exe" not found.
ERROR: The process "fastboot.exe" not found.
cd data\
taskkill /F /IM adb.exe
taskkill /F /IM fastboot.exe
adb.exe reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* daemon started successfully *
fastboot.exe flash recovery recovery.img
sending 'recovery' (3398 KB)...
OKAY [ 0.475s]
writing 'recovery'...
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.957s
downloading 'boot.img'...
OKAY [ 0.475s]
booting...
booting...
FAILED (remote: not allowed)
finished. total time: 0.475s
When going to load HBOOT, I get the following
C:\Users\Philip\Desktop\Stock Phone>@echo off
cd data\
taskkill /F /IM adb.exe
SUCCESS: The process "adb.exe" with PID 5456 has been terminated.
taskkill /F /IM fastboot.exe
adb.exe reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* daemon started successfully *
fastboot.exe flash hboot hboot.img
sending 'hboot' (512 KB)...
OKAY [ 0.084s]
OKAY [ 0.084s]
writing 'hboot'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.157s
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.023s
finished. total time: 0.023s
erasing 'cache'...
FAILED (command write failed (No such file or directory))
FAILED (command write failed (No such file or directory))
finished. total time: -0.000s
finished. total time: -0.000s
rebooting...
finished. total time: -0.000s
Please let me know what I can do please to get my phone working again??
u are s-on now...u can't use fatboot
what u need to do? U can run the ruu if u want go back to stock and having the phone working
andQlimax said:
u are s-on now...u can't use fatboot
what u need to do? U can run the ruu if u want go back to stock and having the phone working
Click to expand...
Click to collapse
Hey
So I have tried to run the Ruu to go back to stock (from windows). However, I am getting errors that saying it can not varify signature and other error messages that I googled which say that I am actually downgrading the software..
I took the phone to a store and they tried the "goldSD" or something, before it was downgraded... I wonder if I should take it back and get them to try again? Other than that, what are the options if ruu wont load??
Freaking out that I may need to buy a new phone..
Now i have got this problem on my legend any suggestions?
nevermind...
doolz23 said:
Hey
So I have tried to run the Ruu to go back to stock (from windows). However, I am getting errors that saying it can not varify signature and other error messages that I googled which say that I am actually downgrading the software..
I took the phone to a store and they tried the "goldSD" or something, before it was downgraded... I wonder if I should take it back and get them to try again? Other than that, what are the options if ruu wont load??
Freaking out that I may need to buy a new phone..
Click to expand...
Click to collapse
If you're still interested, from what I've read you need to make a GoldCard and then run the RUU: http://forum.xda-developers.com/showthread.php?t=1275632
Edit: this appears to have been an issue with my USB cable. Thanks anyway to kotag82 for all his help.
I am trying to unroot my desire because the power button is broken and I need to send it in for warranty. I currently have CM7 installed, with the Bravo CM7 r2 HBOOT from AlphaRev.
I am trying to flash the stock desire HBOOT but I get this error:
Code:
C:\AndroidSDK\tools>fastboot flash hboot bravo_alphaspl.img
sending 'hboot' (512 KB)... FAILED (status malformed (1 bytes))
finished. total time: 0.001s
I have checked the MD5 of the .img
I don't know what to do next.
Thanks
Edit: also the RUU can't see my phone. I assumed that was because I'm not using Sense so HTC Sync doesn't connect, but it may be relevant.
Did you try to flash downgrade first, cm7/r2 has protection
kotag82 said:
Did you try to flash downgrade first, cm7/r2 has protection
Click to expand...
Click to collapse
I did not, please could you point me in the right direction? I have never heard of that before.
It has protection(RUU can't overwrite it) download downgrader from alpharev: first flash it reboot and flash stock one
Edit... sorry you can do it without downgrader my bad...
did you try fastboot devices?
Code:
C:\AndroidSDK\tools>fastboot flash hboot bravo_downgrade.img
< waiting for device >
sending 'hboot' (512 KB)... OKAY [ 0.087s]
writing 'hboot'... OKAY [ 0.152s]
finished. total time: 0.239s
C:\AndroidSDK\tools>fastboot flash hboot bravo_alphaspl.img
sending 'hboot' (512 KB)... ^C
C:\AndroidSDK\tools>fastboot flash hboot bravo_alphaspl.img
sending 'hboot' (512 KB)... ^C
C:\AndroidSDK\tools>fastboot devices
HT03FPL01263 fastboot
C:\AndroidSDK\tools>fastboot flash hboot bravo_alphaspl.img
sending 'hboot' (512 KB)... FAILED (status malformed (1 bytes))
finished. total time: 0.003s
C:\AndroidSDK\tools>fastboot devices
HT03FPL01263 fastboot
"^C" was where it was just hanging for ages and I cancelled the command.
But now downgrade is flashed atleast. But that does mean I'm now stuck in a bootloop.
Hi try this stock hboot, stock.img inside
kotag82 said:
Hi try this stock hboot, stock.img inside
Click to expand...
Click to collapse
Is this more likely to work than the stock hboot on http://alpharev.nl/ ?
I'm slightly hesitant about flashing something I don't know where its from..
Edit, its MD5 is identical. I tried it anyway but I had the same message. "sending 'hboot' (512 KB)... FAILED (status malformed (1 bytes))"
this was downloaded from alpharev ages ago, i flashed it 1 hour ago... everything ok, i just renamed it because of im lazy to type it all...and im using rmd recovery too to flash it... see my signature, there is an option flash image in recovery menu... try to flash your original from alpharev to see if it is working... if not try mine... btw it looks like your file is corrupted
I did have a go with it, but had the same trouble. I don't think my download is corrupted because the MD5 matches what it shows on the alpharev website.
have you tried pb99img.zip method?
Ok, I tried with another USB cable and this time was successful. I don't know if that is coincidence or not but I'm happy with it. Hopefully the RUU will work once I restore Sense from nandroid.
Ruu should work now... good luck... did you use original htc usb cable?
just curious..
trying to switch partition tables on HTC desire GSM
Hi all - I've got a similar problem to that which was discussed here.
In my case I've been using my HTC desire with cyanogenmod7 BRAVO N1table partition for nearly a year now. Lately I'm noticing I am running out of space with my huge app appetite so I thought I would change the partition table to the BRAVO cm7r2 (which was not around when I first reset the partition table).
I managed to get fastboot working on my ubuntu 11.10 machine after some strife but I am stuck when it comes to flashing the hboot .img file with fastboot.
I followed the instructions on alpharev.nl and various other sites to no avail...
when I run the command:
fastboot flash hboot bravo_alphaspl-cm7r2.img
the response i get from the terminal is:
sending 'hboot' (512 KB)... FAILED (status malformed (1 bytes))
I am sadly quite a n00b when it comes to this stuff and really don't know how to interpret this message... I tried the bravo_downgrade.img file with fastboot flash hboot in a similar fashion and got the exact same error message
I hope the question makes sense and I've not been too verbose...
for further info, on my phone i see the following when I'm in HBOOT USB PLUG mode, from the top:
AlphaRev N1Table
BRAVO PVT4 SHIP S-OFF
HBOOT-0.93.1000
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
HBOOT USB PLUG
Any more info required just let me know - Thanks in advance for any help you can offer
something is wrong but try pb99200.zip method, place it in root of your sdcard and start the phone vol- and power buttons together
Sorry forgot to mention - I did try the PB99IMG.zip method... I put it in the root of the SDcard as per the alpharev and your instructions.. I get the error:
CID incorrect!
Update Fail!
Do you want to reboot device?
<VOL UP> Yes
<VOL DOWN> No
I read up on this a bit too and I'm having trouble understanding exactly what the error means but it seems I may need to use a GoldCard? Just researching those now... perhaps I will try to make one.
Is there any possibility that my ubuntu fastboot is not working as normal? I have windows 7 dual booted so I thought next I might try running fastboot from there as it seems there is more support for windows in general... could I use a program like androidflasher to flash partition table changes?
Thanks for your super speedy reply!!!
i think golcard is needed i can't confirm as all my sdcard are goldcards
yes you can try android flasher or you can try that via RMD recovery flash image section there just put your image file on sdcard
I just had this problem after flashing cm7r2, but only because I was silly and did these steps in the wrong order:
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
Follow the above after fastboot flash hboot image.img and you should be fine
Bingley said:
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
Click to expand...
Click to collapse
If the command does not give effect, then remove the battery for a while. It had just helped me.
ze7zez said:
If the command does not give effect, then remove the battery for a while. It had just helped me.
Click to expand...
Click to collapse
2012 dude
Do you know where a full description of the solution to the problem of "FAILED status of malformed"?
I added something from each other, which may one day help someone.
Hey everyone,
My Droid Incredible running CM7.1 began randomly rebooting the other day. Everything was working fine, then it shut down and is now stuck in a continuous boot cycle.
What I can do:
I can boot into hboot and flash PB31IMG.zip's, but nothing else. I cannot run a factory reset or boot into recovery from hboot, both options just induce the boot cycle.
What I have tried:
I reflashed the RUU Gingerbread ROM from hboot.
Reflashed CWM from hboot.
Afterwards, there is no change; the phone never makes it past the white HTC Incredible screen, rather it just reboots.
I have also ttempted to use fastboot to erase both the boot and recovery partitions and reflash recovery.img, but neither command was successful and both produce the same error:
Code:
./fastboot-mac devices
HT07THJ06738 fastboot
./fastboot-mac erase recovery
erasing 'recovery'... FAILED (remote: not allowed)
Any help would be appreciated. At this point I'm beginning to think it's a hardware error, and I'm just going to have to replace the phone.
Details:
Code:
INCREDIBLE XC SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.07.07
Jul 23 2010, 18:06:51
You could try flashing the engineering hboot 0.77, do the fastboot erase and reflash, and then see if you can access recovery. The eng hboot will allow you to use the fastboot commands without getting the remote not allowed error. Not sure that will fix your issue but its worth a shot. You will have to flash back to hboot 0.92 to be able to restore a backup. You can get the hboots here http://dinc.does-it.net/Hboots/
cmlusco said:
You could try flashing the engineering hboot 0.77, do the fastboot erase and reflash, and then see if you can access recovery. The eng hboot will allow you to use the fastboot commands without getting the remote not allowed error. Not sure that will fix your issue but its worth a shot. You will have to flash back to hboot 0.92 to be able to restore a backup. You can get the hboots here (can't post links yet...
Click to expand...
Click to collapse
Thanks for the suggestion. I flashed the engineering hboot 0.77, then wiped the phone completely:
Code:
./fastboot-mac devices
HT07THJ06738 fastboot
$ ./fastboot-mac erase boot
erasing 'boot'... OKAY
$ ./fastboot-mac erase recovery
erasing 'recovery'... OKAY
$ ./fastboot-mac -w
erasing 'userdata'... OKAY
erasing 'cache'... OKAY
I then booted to hboot 0.77 and flashed the RUU PB31IMG.zip. BUT! No dice...
After rebooting, the phone just reenters the same cycle. At this point, I'm assuming there has to be a hardware fault, specifically bad memory. Any other suggestions are welcome.
GATechAE07 said:
Thanks for the suggestion. I flashed the engineering hboot 0.77, then wiped the phone completely:
Code:
./fastboot-mac devices
HT07THJ06738 fastboot
$ ./fastboot-mac erase boot
erasing 'boot'... OKAY
$ ./fastboot-mac erase recovery
erasing 'recovery'... OKAY
$ ./fastboot-mac -w
erasing 'userdata'... OKAY
erasing 'cache'... OKAY
I then booted to hboot 0.77 and flashed the RUU PB31IMG.zip. BUT! No dice...
After rebooting, the phone just reenters the same cycle. At this point, I'm assuming there has to be a hardware fault, specifically bad memory. Any other suggestions are welcome.
Click to expand...
Click to collapse
Not sure man. If the wipes and ruu completed sucessfully then your partitions are fine, so like you said it may be hardware related. Have you tried flashing the froyo ruu, the one originaly on the phone when it was brand new? Mabey that would help. Or you could go the opposite direction and htcdev upgrade and unlock your hboot and see if that helps. Just throwin stuff out there, it sounds like you got nothing to lose.
1. I am posting to this thread to help out a fellow Yellow Jacket, ME '11...
2. I agree with cmlusco, doing the froyo ruu correctly should fix issues. I can't seem to think of anything other than your boot partition, or whatever its called, as either failed or needs formatting.
My experience with bootloops has usually been fixed by just installing a stable rom version.
Had you recently switched to cm7.1 or had you been using it as a daily driver? I've heard of some issues with people using ICS then switching roms back to GB.
My dad got a HTC Incredible from ebay and it will not boot. It is stuck in bootloop if I try to just boot it normally. I can get into HBoot, S-on. HBoot version is 1.02.000. Recovery does not work from here. It just goes into bootloop. I've tried flashing various images with hboot as well as using RUU. RUU always gives me a error of 140.
Anyone have any idea of what I need to do?
benpfeil said:
My dad got a HTC Incredible from ebay and it will not boot. It is stuck in bootloop if I try to just boot it normally. I can get into HBoot, S-on. HBoot version is 1.02.000. Recovery does not work from here. It just goes into bootloop. I've tried flashing various images with hboot as well as using RUU. RUU always gives me a error of 140.
Anyone have any idea of what I need to do?
Click to expand...
Click to collapse
You need to unlock the bootloader with the htcdev site unless its already unlocked, and then fastboot flash cwm recovery img.
When I go to the HTCdev site and select the phone then "Begin Unlock Bootloader" nothing happens. I'm assuming it will download an exe or something?
I am able to get the token for the phone through fastboot but I can't seem to get the site to progress past the main screen.
Edit - For some reason Chrome would not work on the site. I had to move to IE to get the process to work.
I was able to flash clockwork recovery but now when I choose to boot into recovery I just see the white HTC Incredible screen.
benpfeil said:
I was able to flash clockwork recovery but now when I choose to boot into recovery I just see the white HTC Incredible screen.
Click to expand...
Click to collapse
Hmm so your unlocked now and can use extended fastboot commands, that may come in handy. What android version and radio version is the phone on?
This is what I can see in HBoot.
***UNLOCKED***
INCREDIBLE XC SHIP S-ON
HBOOT 1.02.0000
MICROP-0417
TOUCH PANEL-ATMEL224_15ab
RADIO-2.15.10.07.07
DEC 21 2011, 23:37:16
Does that help?
benpfeil said:
This is what I can see in HBoot.
***UNLOCKED***
INCREDIBLE XC SHIP S-ON
HBOOT 1.02.0000
MICROP-0417
TOUCH PANEL-ATMEL224_15ab
RADIO-2.15.10.07.07
DEC 21 2011, 23:37:16
Does that help?
Click to expand...
Click to collapse
Yes it does. Ok follow this guide http://forum.xda-developers.com/showthread.php?t=1506258 starting at number 28 and going till the last step.
Sent from my ADR6300 using xda premium
How can I do that when I can't get the device into usb debug mode?
benpfeil said:
How can I do that when I can't get the device into usb debug mode?
Click to expand...
Click to collapse
Crap your right. Ok there is another way here is where fastboot comes in handy.
Download this file http://dinc.does-it.net/Guide_Root_New_Hboot/mtd0.img, and place it on your pc in the same folder as fastboot.exe, the same place you put the unlock_code.bin file. Boot to hboot with the phone connected to the pc, and open a command promt to where the files are. Then type without quotes "fastboot flash misc mtd0.img".
Sent from my ADR6300 using xda premium
C:\Android>fastboot flash misc mtd0.img
sending 'misc' (640 KB)... OKAY [ 0.102s]
writing 'misc'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.216s
No luck
benpfeil said:
C:\Android>fastboot flash misc mtd0.img
sending 'misc' (640 KB)... OKAY [ 0.102s]
writing 'misc'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.216s
No luck
Click to expand...
Click to collapse
Damn. I was trying to get you s-off but im not sure how to do it in your situation other than adb and flashing the misc partition. We have pretty much run out of options. Ruu dosent work, cwm dosent work, you vant flash misc, Let me think some more and i will get back to you.
Sent from my ADR6300 using xda premium
Sounds good. Thanks for all your help so far.
benpfeil said:
Sounds good. Thanks for all your help so far.
Click to expand...
Click to collapse
Ok try this download this http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip, rename it update.zip and place it on your pc in the same folder as fastboot.exe. Then open a cmd prompt and type without quotes "fastboot update update.zip". If it works, see if you can boot.
Really weird error from fastboot.
benpfeil said:
Really weird error from fastboot.
Click to expand...
Click to collapse
That is weird, never seen anything like that before. It seems nothing is working to get the phone going, mabey it has some sort of hardware failure.
Hi All,
I'm hoping an expert will be able to help me. I have a Desire HD that a friend has asked me to have a look at knowing that I have tinkered around with my android phones. She said it "just happened" while she was out riding her bike one day.
Basically, all I'm getting is the green on white HTC logo regardless of what I try. I can get into HBOOT & fastboot and have tried to flash recovery.img, run RUU, flash boot.img and flash PD98IMG.zip (both via fastboot & direct from root of SD card). I obviously couldn't root the device using AAHK as I can't boot into the phone to enable USB debugging and adb obviously won't work for the same reason.
I've tried flashing both 4ext & CWM recoveries neither of which work. When I try to boot into recovery using by selecting that option in HBOOT it just goes straight back to the green on white HTC logo.
In a vein attempt to get anywhere with it I managed to "unlock" the bootloader using htcdev instructions but it hasn't succeeded in helping with the problem.
HBOOT details are as follows:
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Dec 22 2011,14:28:19
The RUU I have tried works to a point and then fails but I'm guessing it's because I need the Vodafone UK RUU which doesn't seem to be anywhere. I tried this one to no avail
Code:
RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_R_Radio_12.65.60.29_26.14.04.28_M_release_233505_signed.exe
If anyone has any advice it would be greatly appreciated.
Thanks in advance.
Geff
wheest said:
Hi All,
I'm hoping an expert will be able to help me. I have a Desire HD that a friend has asked me to have a look at knowing that I have tinkered around with my android phones. She said it "just happened" while she was out riding her bike one day.
Basically, all I'm getting is the green on white HTC logo regardless of what I try. I can get into HBOOT & fastboot and have tried to flash recovery.img, run RUU, flash boot.img and flash PD98IMG.zip (both via fastboot & direct from root of SD card). I obviously couldn't root the device using AAHK as I can't boot into the phone to enable USB debugging and adb obviously won't work for the same reason.
I've tried flashing both 4ext & CWM recoveries neither of which work. When I try to boot into recovery using by selecting that option in HBOOT it just goes straight back to the green on white HTC logo.
In a vein attempt to get anywhere with it I managed to "unlock" the bootloader using htcdev instructions but it hasn't succeeded in helping with the problem.
HBOOT details are as follows:
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Dec 22 2011,14:28:19
The RUU I have tried works to a point and then fails but I'm guessing it's because I need the Vodafone UK RUU which doesn't seem to be anywhere. I tried this one to no avail
Code:
RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_R_Radio_12.65.60.29_26.14.04.28_M_release_233505_signed.exe
If anyone has any advice it would be greatly appreciated.
Thanks in advance.
Geff
Click to expand...
Click to collapse
ok, are you sure that you actually flashed recovery successfully? unless you have a messed motherboard, you should be able to flash recovery image and then a custom rom.
A RUU won´t work as you have unlocked the bootloader. Make sure that you are flashing the recovery from fastboot and you get the OKAY. Finished in the cmd / terminal session.
If you need further help, just let me know. :good:
glevitan said:
ok, are you sure that you actually flashed recovery successfully? unless you have a messed motherboard, you should be able to flash recovery image and then a custom rom.
A RUU won´t work as you have unlocked the bootloader. Make sure that you are flashing the recovery from fastboot and you get the OKAY. Finished in the cmd / terminal session.
If you need further help, just let me know. :good:
Click to expand...
Click to collapse
Thanks for the quick reply. Here is my CMD text pasted below:
Code:
D:\***\***\***\***\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-5.0.2.0-ace.img
sending 'recovery' (3624 KB)...
OKAY [ 0.613s]
writing 'recovery'...
OKAY [ 0.572s]
finished. total time: 1.188s
It always seems to succeed whichever recovery I use and that's now CWM, Touch CWM & 4ext that I've tried. So is the prognosis a screwed mobo?
wheest said:
Thanks for the quick reply. Here is my CMD text pasted below:
Code:
D:\***\***\***\***\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-5.0.2.0-ace.img
sending 'recovery' (3624 KB)...
OKAY [ 0.613s]
writing 'recovery'...
OKAY [ 0.572s]
finished. total time: 1.188s
It always seems to succeed whichever recovery I use and that's now CWM, Touch CWM & 4ext that I've tried. So is the prognosis a screwed mobo?
Click to expand...
Click to collapse
If You can't access recoveryi am afraid that does not look Good.