Desire Fail! Help!!! - Desire Q&A, Help & Troubleshooting

Hi Guys,
I have a bit of a problem with the HTC Desire, I have had various roms on and its just been getting slower and slower....decided to put on a different ROM but appear to have cocked it up!
I am trying to get the CM7 Hboot on as I want to put CM7 on the phone....
Currently HBOOT says Revoluntary S-Offed with 6.93.1002
When I try and flash the CM7R2 Hboot the screen just hangs:
C:\Program Files\Android\android-sdk\platform-tools>fastboot flash hboot c:\bra
o_alphaspl-cm7r2.img
sending 'hboot' (512 KB)...
FAILED (status read failed (Too many links))
finished. total time: 7.344s
What am I doing wrong?????
any help appreciated and how I set up my partitions for optimum speed once this is sorted!
Rich

You might wanna try and use Android Flasher.... just make sure you are on fastboot mode already. I find it easier than going through the command line. Check the troubleshooting guide on my sig if you wanna try it out.

Hi Rich
Normally I rename CM7R2 Hboot to just hboot, place hboot.img on root of C drive. Make sure you just rename it only 'hboot'
Reboot to bootloader, connect usb, you should see fastboot usb.
Locate android-sdk/platform tools folder inside of the C drive
Now hold shift key down on your keyboard and right click in any blank area inside that folder. This will give you the option to open a command window here.
Enter in the command window:
fastboot devices
fastboot flash hboot C:\hboot.img
fastboot erase cache
fastboot reboot-bootloader
---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------
stankyou said:
You might wanna try and use Android Flasher.... just make sure you are on fastboot mode already. I find it easier than going through the command line. Check the troubleshooting guide on my sig if you wanna try it out.
Click to expand...
Click to collapse
In the past, I used android flasher. However, with any GUI there is risk involved. ADB might seem scary but it is the safest option when changing radio, hboot and recoveries. People are creature of habits, ADB is a good habit.
Besides the OP is already familiar with ADB and he simply wants to know where he is going wrong...

if its "getting slower and slower", I'll take a 5:1 bet that you're not doing a full wipe before flashing a new ROM. Wipe boot, system, data, cache & dalvic and you'll be fine (and stick to gingebrread).

Related

[Q] Bricked or is there still hope?

I'm messing around since 3 days with a non working Desire.
I was trying to root that Vodafone UK Branded Phone with a goldcard, but it somehow did't really work stable.
So I managed it to install a RUU in order to revert it and begin the Process from the beginning on:
1.This was the RUU, and everything went fine: RUU_Bravo_Froyo_Vodafone_UK_2.33.161.2_Radio_32.49.00.32U_5.11.05.27_release_157522_signed
2.Then I tried to downgrade my HBOOT from 0.93.0001 to 0.80 using the method in this thread (with goldcard!)
3. During the installation of the PB99IMG.zip something went wrong and (maybe a mismatch with goldcard or the mtd0.img, i still don't know / understand) HBOOT could not be updated and RADIO-V2 also
4. now I cant boot the Phone at all or issue adb commands (I think the phone needs to be fully booted and USB-debbug-enabled for this) so I cant follow any of the solutions wich I found in the last two days. A PB99IMG.zip is also not flashable in HBOOT since it just cancels after "Checking..[PB99IMG.zip]" and returns back to the HBOOT screen.
Here's my phones specs:
CID: VODAP102
PVT4
S-ON
HBOOT 0.93.0001
MICROP-051d
SLCD
RADIO 5.11.05.27
If someone has an idea where to start, any help would be greatly apreciated. If someone is even willing to assist via instant messaging or skype I would be happy to compensate his time with a donation via paypal! Thank you in advance!
EDIT: SOLVED!!!
cosine83 from the unrevoked IRC channel solved it for me!!
I was able to enter RUU mode and flash the PB99IMG.zip in 2 quick steps!
In fastboot mode:
1.fastboot oem rebootRUU
2.fastboot flash zip PB99IMG.zip
huge thanks!!!
Hello sorry for that
but the good news is your phone is not dead, do you red this
http://forum.xda-developers.com/showthread.php?t=750888
I think your fix is here : http://forum.xda-developers.com/showthread.php?p=7602850#post7602850
hope it can help you
what happens if you hold vol down + power when the phone is off?
Good idea. I forgot to ask
Sent from my HTC Desire using XDA Premium App
Droidxda said:
Hello sorry for that
but the good news is your phone is not dead, do you red this
http://forum.xda-developers.com/showthread.php?t=750888
I think your fix is here : http://forum.xda-developers.com/showthread.php?p=7602850#post7602850
hope it can help you
Click to expand...
Click to collapse
Trying this right now, almost gave up on this...
vol down + power brings me to the regular hboot manu and i can also enter fastboot...
Regular 0.93 ?
Do you try unrevoked?
Sent from my HTC Desire using XDA Premium App
Droidxda said:
Regular 0.93 ?
Do you try unrevoked?
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
for unrevoked I need my phone booted up and have debugging enabled as far as i know, but I cant boot it...
EDIT: I followed your guide from HERE but the result is still the same. I am not able to flash the PB99IMG.zip HBOOT reads it (the blue bar on the right top goes all the way up but then comes "Checking..[PB99IMG.zip]" and the procedure just aborts.
I think it must have something to do with a wrong mtd0.img which was flashed during my first attempt to downgrade (mybe not matching the PB99IMG???) or there is a problem with the goldcard (i am very certain that I did everythin correct with the gc, did it manually and also tith the gc-maker)
On the fastboot menu, could you access a recovery?
Sent from Desire Bravo with xda App. Leedroid ROM HD port inside.
Droidxda said:
On the fastboot menu, could you access a recovery?
Sent from Desire Bravo with xda App. Leedroid ROM HD port inside.
Click to expand...
Click to collapse
well I can select the "recovery" from the Hboot menu and also try flashing an update.zip, but every time I do this I get:
E:failed to verify whole-file signature
E:signature verifivation failed
Installation aborted
The best way should find a correct hboot P99IMG.zip and put it on the SD
Should ask to unrevoked team by the irc channel.
Sent from Desire Bravo with xda App. Leedroid ROM HD port inside.
cgorki said:
well I can select the "recovery" from the Hboot menu and also try flashing an update.zip, but every time I do this I get:
E:failed to verify whole-file signature
E:signature verifivation failed
Installation aborted
Click to expand...
Click to collapse
**** I know this message, but I can't remember.
EDIT - hboot 0.93 ?
Sent from Desire Bravo with xda App. Leedroid ROM HD port inside.
I thought it wasn't possible to change hboot until you s-off? or does a goldcard make it possible when s-on?
if you can access the bootloader menu (vol down + power) then you should be able to fix your phone.
Do you try to install an ruu Rom?
Sent from Desire Bravo with xda App. Leedroid ROM HD port inside.
Boot the phone into bootloader menu.
connect usb cable.
in command prompt load the SDK folder, instead of typing adb.exe type fastboot.exe.
place the hboot you want into the "platform-tools" folder in the SDK directory - if its in the pb99img.zip then extract the .img file from there and place just that file into the folder.
type "fastboot flash hboot *name-of-file.img*"
if this works then type
type "fastboot reboot-bootloader"
type "fastboot erase cache"
Not sure it will work though as you are S-ON.
However you should be able to flash a recovery through the same way, type "fastboot flash recovery *name.img*". Not sure if this will help fix it, but if you can access recovery then its a start! Obviously you'll need to download a recovery first and place it into the platform-tools folder.
himeshladva said:
Boot the phone into bootloader menu.
connect usb cable.
in command prompt load the SDK folder, instead of typing adb.exe type fastboot.exe.
place the hboot you want into the "platform-tools" folder in the SDK directory - if its in the pb99img.zip then extract the .img file from there and place just that file into the folder.
type "fastboot flash hboot *name-of-file.img*"
if this works then type
type "fastboot reboot-bootloader"
type "fastboot erase cache"
Not sure it will work though as you are S-ON.
However you should be able to flash a recovery through the same way, type "fastboot flash recovery *name.img*". Not sure if this will help fix it, but if you can access recovery then its a start! Obviously you'll need to download a recovery first and place it into the platform-tools folder.
Click to expand...
Click to collapse
doubt that this will work with s-on, but trying anyways!!
thank you!
cgorki said:
doubt that this will work with s-on, but trying anyways!!
thank you!
Click to expand...
Click to collapse
would probably give the recovery option a go first..
himeshladva said:
would probably give the recovery option a go first..
Click to expand...
Click to collapse
C:\1>fastboot flash recovery cwm.img
sending 'recovery' (3366 KB)... OKAY [ 0.488s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.958s
EDIT: Is there a way to issue ADB commands to the phone without having it booted up?
cgorki said:
C:\1>fastboot flash recovery cwm.img
sending 'recovery' (3366 KB)... OKAY [ 0.488s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.958s
EDIT: Is there a way to issue ADB commands to the phone without having it booted up?
Click to expand...
Click to collapse
You can if you are able to access recovery.. or try to just turn the phone on and see.
Also, take a read through this.. maybe it will help.
http://www.askabouthugo.com/general...n-fastboot-with-remote-signature-verify-fail/
Not sure what else can be done if that doesn't help.
Would be best to join unrevoked IRC channel as they would know a lot more about it..
himeshladva said:
Not sure what else can be done if that doesn't help.
Would be best to join unrevoked IRC channel as they would know a lot more about it..
Click to expand...
Click to collapse
I'm talking to some of the guys from the IRC, so far no solution in sight. Maybe tomorrow there are some ppl online who are familiar with the HTC Bravo GSM...

Flashing Radio using Android Flasher

I can't post on the developers thread so thought best to post here.
I'm trying to use android flasher to flash the latest Desire radio (bravo.5.17.05.23) as recommended by the Sense ROM's I'd like to try.
I have installed Windows .net 4.0 on Windows Vista, have downloaded HTC Sync and then uninstalled it leaving only the drivers remaining. I also have USB debugging enabled.
I have booted into FASTBOOT having powered off (Power button, back button) and have connected the phone to the laptop to get FASTBOOTUSB to appear.
I unzip Android Flasher and the two .dll files to the desktop and then open Android Flasher. I select Desire and then browse for the radio .img on my desktop. I tick "I'm already in fastboot" and then press flash.
At this point the status bar reaches just over halfway. No script appears in the dialogue box and nothing further happens.
Can anyone advise if I have missed a step? Do I need to reboot the phone from inside the FASTBOOT USB menu?
-Revolutionary-
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
You might want to try and flash the radio image directly via fastboot. Just download the fastboot binary, put it in a path you can remember, put the radio img file in the same directory, click Start > Run and type in cmd. Then, type in 'cd C:\path\to\the\fastboot\directory\', followed by 'fastboot.exe flash radio radio_image_name.img'. That's it!
Proz0r said:
You might want to try and flash the radio image directly via fastboot. Just download the fastboot binary, put it in a path you can remember, put the radio img file in the same directory, click Start > Run and type in cmd. Then, type in 'cd C:\path\to\the\fastboot\directory\', followed by 'fastboot.exe flash radio radio_image_name.img'. That's it!
Click to expand...
Click to collapse
Hello - I just tried this and got the following error ....
H:\>fastboot.exe flash radio D:bravo.5.17.05.23.zip
sending 'radio' (11561 KB)...
OKAY [ 1.906s]
writing 'radio'...
FAILED (remote: image update error)
finished. total time: 1.969s
Any ideas ?
Sorry wrong post
Looloup said:
Hello - I just tried this and got the following error ....
H:\>fastboot.exe flash radio D:bravo.5.17.05.23.zip
sending 'radio' (11561 KB)...
OKAY [ 1.906s]
writing 'radio'...
FAILED (remote: image update error)
finished. total time: 1.969s
Any ideas ?
Click to expand...
Click to collapse
Yep, you need to extract the .Img file from the zip and fastboot flash that. Not going to work trying to flash the zip file.
Sent from my HTC Desire using Tapatalk
Is it necessesary to be S-OFF to flalsh new Radio?
I tried with revoked but it does not find my phone so i think of flashing radio via fastboot instead of sdcard.
Px80 said:
Is it necessesary to be S-OFF to flalsh new Radio?
I tried with revoked but it does not find my phone so i think of flashing radio via fastboot instead of sdcard.
Click to expand...
Click to collapse
yes i believe you need to be s-off to flash radios
in your sig, you have desire s, so don't flash radios from this thread (for desire (Bravo))!
make sure you check the md5 sum of the radio.img before flashing, a bad radio flash = brick! the fastboot commands should still be the same however.

unlocking problem "waiting for device"

Hey guys,
I am trying to s-off my girlfriends Wildfire S.
MARVEL PVT SHIP S-ON RL
HBOOT-1.009.0099
MICROP-041
RADIO-7.57.39.10M
FEB 9 2012 18:29:31
I am following the directions from htcdev.com/bootloader
I got to the point where I am supposed to "get_identifier_token"
Now my phone is connected as it should be, I am in "fastoot usb".
Still, the only thing happens is that I get the following message in command prompt: "waiting for device". Nothing happens. I tried to restart PC and phone again: same problem.
Does anyone have an idea about what I'm doing wrong? I'm stuck.
Okay. Now I unlocked bootloader. I think the problem was USB-debugging was not turned on.
Trying to run clockworkmod, but keep getting error messages:
"you must root your phone for ROM manager to function. Superuser was not found at "/system/bin/su" or "system/xbin/su".
When I try to flash clockworkmod recovery I get the following error:
"An error occured while attempting to run privileged commands".
My deviced is with unlocked bootloader, buy of course still S-ON. I understood from the threads around that that's not a problem.
http://forum.xda-developers.com/showthread.php?t=1927757&highlight=root
How can I install a custom ROM?
How can I install data2sd?
Can someone help? Thanks a lot.
szaboagoston said:
Okay. Now I unlocked bootloader. I think the problem was USB-debugging was not turned on.
Trying to run clockworkmod, but keep getting error messages:
"you must root your phone for ROM manager to function. Superuser was not found at "/system/bin/su" or "system/xbin/su".
When I try to flash clockworkmod recovery I get the following error:
"An error occured while attempting to run privileged commands".
My deviced is with unlocked bootloader, buy of course still S-ON. I understood from the threads around that that's not a problem.
http://forum.xda-developers.com/showthread.php?t=1927757&highlight=root
How can I install a custom ROM?
How can I install data2sd?
Can someone help? Thanks a lot.
Click to expand...
Click to collapse
-------------------------------------------------------------
Hi, what you need to do is go into your bootloader as you usually do, Volume - and Power Button, plug your USB and go into fastboot USB. Then you need to create a file on you C: drive called "fastboot" and put the following files in there "adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll & fastboot.exe" and your recovery image, I suggest you use the offical clock work mod recovery which is available here,
if you do not have these files you can download them from here,
http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvel.img
http://forum.xda-developers.com/showthread.php?t=1474956
once you do this then open a command dos window by typing cmd in the start search box of windows.... once the command window opens go to the right folder of C:\fastboot> where you saved the files.
Then as your phone is in fastboot USB and you are in the command window C:\fastboot>, type in the command window the following,
fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img
Then press enter, what you should see is the below,
c:\fastboot>fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img
sending 'recovery' (2224 KB)... OKAY
writing 'recovery'... OKAY
If you follow the above then you should have clockworkmod recovery, you can then take the USB out and go back to the hboot in you bootloader and choose recovery under hboot by navigating with the volume button and power button.
I do need to inform you though that if you are one of the unlucky WFS owners that get the "Black Screen Recovery" issue where you go into recovery and you only get a black screen and you tactile buttons are on then you need to follow the bellow method to be able to see you recovery on you PC screen than on your phone.
http://forum.xda-developers.com/showthread.php?t=1781105
Also here is a youtube video of what I mean
http://www.youtube.com/watch?v=HgrPctWKW8E
I know all this as I had the same issue and this helped me. Now I feel that I need to inform you about other issues... When you unlock the bootloader you can't flash a ROM and then just switch your phone on and it boots into the new ROM, there is a process you need to follow.
When you choose your ROM, and not all ROMs work with the Wildfire S new batch of phone as I had to find out the hard way, you need to flash your ROM and then open the .zip file of your phone copy the boot.img of the ROM paste it in the c:\fastboot> directory and again in the command window type,
fastboot flash boot boot.img
You will see the below,
c:\fastboot>fastboot flash boot boot.img
sending 'boot' (2224 KB)... OKAY
writing 'boot'... OKAY
Then type,
c:\fastboot>fastboot reboot
And your phone will reboot into the new ROM allow 10 to 15 minutes... BE PATIENT.
I hpe the above helps you.
I am currently having the below problems just for your info if you have the same...
http://forum.xda-developers.com/showthread.php?t=1948038
success
Karavasileiadis said:
-------------------------------------------------------------
Hi, what you need to do is go into your bootloader as you usually do, Volume - and Power Button, plug your USB and go into fastboot USB. Then you need to create a file on you C: drive called "fastboot" and put the following files in there "adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll & fastboot.exe" and your recovery image, I suggest you use the offical clock work mod recovery which is available here,
if you do not have these files you can download them from here,
http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvel.img
http://forum.xda-developers.com/showthread.php?t=1474956
once you do this then open a command dos window by typing cmd in the start search box of windows.... once the command window opens go to the right folder of C:\fastboot> where you saved the files.
Then as your phone is in fastboot USB and you are in the command window C:\fastboot>, type in the command window the following,
fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img
Then press enter, what you should see is the below,
c:\fastboot>fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img
sending 'recovery' (2224 KB)... OKAY
writing 'recovery'... OKAY
If you follow the above then you should have clockworkmod recovery, you can then take the USB out and go back to the hboot in you bootloader and choose recovery under hboot by navigating with the volume button and power button.
I do need to inform you though that if you are one of the unlucky WFS owners that get the "Black Screen Recovery" issue where you go into recovery and you only get a black screen and you tactile buttons are on then you need to follow the bellow method to be able to see you recovery on you PC screen than on your phone.
http://forum.xda-developers.com/showthread.php?t=1781105
Also here is a youtube video of what I mean
http://www.youtube.com/watch?v=HgrPctWKW8E
I know all this as I had the same issue and this helped me. Now I feel that I need to inform you about other issues... When you unlock the bootloader you can't flash a ROM and then just switch your phone on and it boots into the new ROM, there is a process you need to follow.
When you choose your ROM, and not all ROMs work with the Wildfire S new batch of phone as I had to find out the hard way, you need to flash your ROM and then open the .zip file of your phone copy the boot.img of the ROM paste it in the c:\fastboot> directory and again in the command window type,
fastboot flash boot boot.img
You will see the below,
c:\fastboot>fastboot flash boot boot.img
sending 'boot' (2224 KB)... OKAY
writing 'boot'... OKAY
Then type,
c:\fastboot>fastboot reboot
And your phone will reboot into the new ROM allow 10 to 15 minutes... BE PATIENT.
I hpe the above helps you.
I am currently having the below problems just for your info if you have the same...
http://forum.xda-developers.com/showthread.php?t=1948038
Click to expand...
Click to collapse
Thanks a lot for the quick and professional answer. By the time I read it, I managed to root.
I used rezo609's all-in-one utility, which I found in at this location:
http://forum.xda-developers.com/showthread.php?t=1697985
I got the advice from this thread:
http://forum.xda-developers.com/showthread.php?t=1927757
I installed the Speeddroid ROM and data2SD as described here:
http://forum.xda-developers.com/showthread.php?t=1932534&highlight=data2sd+install
The result: so far everything working. It looks like a new phone!
stuck to root
Hi,
I have the same situation here.
But Which tool do you run of the [UTILITY]rezo609's All-In-One Utility ? (http://forum.xda-developers.com/showthread.php?t=1697985&page=3)
In the whole topic there is no how to.
I managed to unlock the bootloader, and clockwork recovery is also on there.
I just want to root the phone (not to put an other rom)
Thanks in advance,

[Q] Idiot With HTC one X stuck in boot loop.

Hello,
I’ve been following guides to root my phone and put a custom ROM onto it. I had no experience in doing this so I thought I would follow an idiots guide and was stupid enough not to back up the original ROM along with not reading up properly on what I was about to do… (yes you can call me names I shall accept it)
The problem I'm having is after putting the custom ROM which was ViperX3.2.0 The phone just stays stuck on the HTC one Tm with beats audio and keeps resetting it self, anyway i can fix it? or have i bricked it.
I'm a complete noobie cause I've been looking around for the past 3 days and still can't find anything (or something I can understand) :angel:
- I've wiped cache, dalvik cache and battery stats
- I go to recovery and click mount sd card nothing happens mount usb storage nothing happens.
- I don't understand next to nothing, need like android for idiots. :good:
- When phones booting up my computer recognises something but has not drivers and fails (But i had drivers and could transfer stuff too and from)
So if you can help i will love you forever
Many Thanks
RIch
I'm going to quote the instructions on the ViperX page. Have you even followed these steps?
Code:
1. Make sure your that your HBOOT is 1.31 or greater
2. Check if you CID is supported, visit http://forum.xda-developers.com/showthread.php?t=1957376 for updates. Cheers Mike
3. Unlock your bootloader via HTCDev and install a custom recovery.
4. Download the ROM and place it on your virtual SD card.
5. Do a nandroid backup!
6. Extract boot.img from ROM zip and flash it using ‘fastboot flash boot boot.img’.
7. Use 'fastboot erase cache' to avoid boot issues.
8. Go into recovery and install the ROM.
9. Please choose fullwipe if you are asked, highly recommended if you go from one rom from another rom.
10. Reboot the device and enjoy!
Did you flash the boot.img file in fastboot? fastboot flash boot boot.img followed by fastboot erase cache
tomascus said:
I'm going to quote the instructions on the ViperX page. Have you even followed these steps?
Code:
1. Make sure your that your HBOOT is 1.31 or greater
2. Check if you CID is supported, visit http://forum.xda-developers.com/showthread.php?t=1957376 for updates. Cheers Mike
3. Unlock your bootloader via HTCDev and install a custom recovery.
4. Download the ROM and place it on your virtual SD card.
5. Do a nandroid backup!
6. Extract boot.img from ROM zip and flash it using ‘fastboot flash boot boot.img’.
7. Use 'fastboot erase cache' to avoid boot issues.
8. Go into recovery and install the ROM.
9. Please choose fullwipe if you are asked, highly recommended if you go from one rom from another rom.
10. Reboot the device and enjoy!
Click to expand...
Click to collapse
Like I Said I was stupid enough not to follow instruction, where to start. First my Hboot is not 1.31 but 1.12 or somthing. No clue what CID is Trust an idiot like me to do something like this HA.
I never did a nandroid backup, I'm hitting myself for that one quite badly
Apart from that i did everything else HA yes i did do fastboot boot boot.img folowed by somthing to do with cache
Richlilrich said:
Like I Said I was stupid enough not to follow instruction, where to start. First my Hboot is not 1.31 but 1.12 or somthing. No clue what CID is Trust an idiot like me to do something like this HA.
I never did a nandroid backup, I'm hitting myself for that one quite badly
Apart from that i did everything else HA yes i did do fastboot boot boot.img folowed by somthing to do with cache
Click to expand...
Click to collapse
Okay, in fastboot mode, type 'fastboot getvar cidnum' to get your CID number.
then according to that number, go here: http://forum.xda-developers.com/showthread.php?t=1957376
and download your firmware.zip
then use the following commands:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
tomascus said:
Okay, in fastboot mode, type 'fastboot getvar cidnum' to get your CID number.
then according to that number, go here: http://forum.xda-developers.com/showthread.php?t=1957376
and download your firmware.zip
then use the following commands:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Ahh, i've done what you just said it looks like i'm getting somewhere.
looks like i'm stuck on this one.
C:\fastboot>fastboot flash zip 3.16.61.6.zip
sending 'zip' (12875 KB)...
OKAY [ 1.786s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 5.130s
Just keep trying 'fastboot flash zip (lalala)' until it works.
Afterwards, you need to re-unlock your bootloader with 'fastboot flash unlocktoken unlock_code.bin'
then reflash boot.img 'fastboot flash boot boot.img'
then 'fastboot erase cache'
then reflash recovery 'fastboot flash recovery (lalalaa.img)'
tomascus said:
Just keep trying 'fastboot flash zip (lalala)' until it works.
Afterwards, you need to re-unlock your bootloader with 'fastboot flash unlocktoken unlock_code.bin'
then reflash boot.img 'fastboot flash boot boot.img'
then 'fastboot erase cache'
then reflash recovery 'fastboot flash recovery (lalalaa.img)'
Click to expand...
Click to collapse
I feel bad, wasting your time still. CMD has froze should i cancel ctrl +c? so i apologise in advance
C:\fastboot>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.008s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
also 0kb?
-EDIT-
DONE IT! However i don't have no signal and can't connect to wifi? did i miss a step?
also i would love the opportunity to learn about this stuff starting from the basics, any advice on some reading i should do? i know it's a cheeky question but it's a must I think LOL
But thank you for your time.
Rich
Richlilrich said:
I feel bad, wasting your time still. CMD has froze should i cancel ctrl +c? so i apologise in advance
C:\fastboot>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.008s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
also 0kb?
-EDIT-
DONE IT! However i don't have no signal and can't connect to wifi? did i miss a step?
also i would love the opportunity to learn about this stuff starting from the basics, any advice on some reading i should do? i know it's a cheeky question but it's a must I think LOL
But thank you for your time.
Rich
Click to expand...
Click to collapse
I'm happy for you.
Man, just search and you shall find
Try reflash boot.IMG or if it doesn't work- Full wipe and reflash ROM.
Sent from my HTC One X using xda app-developers app
tomascus said:
I'm happy for you.
Man, just search and you shall find
Try reflash boot.IMG or if it doesn't work- Full wipe and reflash ROM.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Whoopsie, did fastboot flash boot boot.img didn't start up so i thought i would check recovery and earse some caches, theres an error for it to load. (a phone laying down with an exclaimation mark) so i can't do a wipe
Reflash the custom recovery
Fastboot flash recovery recover.img
Fastboot erase cache
Anyway to get the recovery back? so i can try another ROM to see if that could possibly fix the problem, just can't get into recovery D: happy my phone turns on lol however no network or can't connect to wifi
by fashing the boot did nothing but crash it more.
so i had to redo what you taught me, thank you again and i'm back to where i said i was
Flash this one again
http://db.tt/Krlm4dPs
Fastboot flash recovery recovery.img
Rename the downloaded file to recovery.img before you flash !
Mr Hofs said:
Flash this one again
http://db.tt/Krlm4dPs
Fastboot flash recovery recovery.img
Rename the downloaded file to recovery.img before you flash !
Click to expand...
Click to collapse
Many thanks, recovery up and running. now that I know this I'll try to reinstall the ROM.
Are there any reasons why I'm not getting signal or WiFi? along with that from the unlock it seem rather slow,
But I guess it's time for me to experiment, now that i know how to fix it if I mess up
Maybe because of this :
When installing the viper you get a question about the custom kernel ....
Answer with NO !
Mr Hofs said:
Maybe because of this :
When installing the viper you get a question about the custom kernel ....
Answer with NO !
Click to expand...
Click to collapse
I am sure I have done that a few times, going to try re downloading and try to reinstall. May not be installing right,
Thanks
Just signed up to say thanks Mr Hofs for the help you've posted in this thread in particular but also in many other threads I've been referring to over the last 4 hours or so. I was well on my way to brickage following a screwed up attempt to root my HOX, but thanks to you I'm now up and running again. Admittedly I'm back at square one with a non-rooted handset, but I never would've believed that would be such a happy place to be, plus I feel a tiny bit less of a noob now.
Anyway, apologies for crashing your thread Richlilrich - as you were!
Screwed up my One X
tomascus said:
Okay, in fastboot mode, type 'fastboot getvar cidnum' to get your CID number.
then according to that number, go here: http://forum.xda-developers.com/showthread.php?t=1957376
and download your firmware.zip
then use the following commands:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Hey Guy's,
I know this thread is old and many of you might not see this anymore but I'm sure this is where I need to be.
I have a UK Quad Core HOX and rooted fine a while ago.
I placed Cyanogen on for a while and all was running fine but it doesn't have all the tweaks I'd like so looked around for another ROM.
I came across the ViperROM and thought - Great! Exactly what I wanted, checked the reviews - All good, checked my HBoot etc... All seems fine. Went ahead and installed it through CWM (5.8.4.0) like I have done a thousand times before and went and rewrote the boot.img and got a continuous HTC boot loop. Thought hey no harm no fuss and went back into recovery to restore my most recent back-up only to find that they had all gone - My stock recovery my previous tries at other ROMS and most importantly my most recent Backup!!!!
I followed the steps above over and over again, I can re-lock my HOX, reboot into RUU and flash the 3.16.61.6 firmware (and boot img inside zip) and it still bootloop's over and over....... (I can unlock again too)
I've tried adb pushing Stock and custom ROMS to the SD card which says success in windows cmd but says no files on SDcard.
What am I doing wrong?
P.S hboot details are;
Endeveavoru PVT Ship S-ON RL
HBOOT-1.36.0000
CPLD-None
Microp-None
Radio-5.1204.163R.30
eMMC-Bootmode: disabled
CPU-bootmode: disabled
HW Secure boot:enabled
Modem path : off
Nov 16 2012, 18:32:39
Hope someone can help
---------- Post added at 07:29 PM ---------- Previous post was at 07:24 PM ----------
DrUmMiSt said:
Hey Guy's,
I know this thread is old and many of you might not see this anymore but I'm sure this is where I need to be.
I have a UK Quad Core HOX and rooted fine a while ago.
I placed Cyanogen on for a while and all was running fine but it doesn't have all the tweaks I'd like so looked around for another ROM.
I came across the ViperROM and thought - Great! Exactly what I wanted, checked the reviews - All good, checked my HBoot etc... All seems fine. Went ahead and installed it through CWM (5.8.4.0) like I have done a thousand times before and went and rewrote the boot.img and got a continuous HTC boot loop. Thought hey no harm no fuss and went back into recovery to restore my most recent back-up only to find that they had all gone - My stock recovery my previous tries at other ROMS and most importantly my most recent Backup!!!!
I followed the steps above over and over again, I can re-lock my HOX, reboot into RUU and flash the 3.16.61.6 firmware (and boot img inside zip) and it still bootloop's over and over....... (I can unlock again too)
I've tried adb pushing Stock and custom ROMS to the SD card which says success in windows cmd but says no files on SDcard.
What am I doing wrong?
P.S hboot details are;
Endeveavoru PVT Ship S-ON RL
HBOOT-1.36.0000
CPLD-None
Microp-None
Radio-5.1204.163R.30
eMMC-Bootmode: disabled
CPU-bootmode: disabled
HW Secure boot:enabled
Modem path : off
Nov 16 2012, 18:32:39
Hope someone can help
Click to expand...
Click to collapse
Would like to add that I would prefer Viper to stock but stock would help for now
Before going for RUU and stuff, try any other roms.
I'd say do this :
Flash TWRP - Better than CWM anyday.
Go to recovery. Mount USB. Copy Viper (or any other) rom to phone.
Reboot to bootloader.
Flash boot.img.
Fastboot erase cache.
Go to recovery.
Clean install ROM.
Reboot and wait for it. First boot takes pretty long sometimes.
There is no better recovery, a recovery is personal. I'm using CWM now for 2 years....never had a problem with that.....
Now the issue.
How to copy it is in the post above, however before you install the rom you need to make a real good full wipe
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then install the rom...and ofcourse flash the boot.img from the rom.zip
The option to mount in CWM is under mounts and storage copy the rom.zip over and unmount.
The way i personally follow is :
Flash the boot.img (fastboot, bootloader mode) then enter the recovery and follow the above....make sure you unplug the usb cable BEFORE installing the rom.zip

[Q] bricked (challenge to members)

MARVEL PVT SHIP S-ON RL
HBOOT 1.09.0099
MICROP-0451
RADIO-7.57.39.10M
Feb 8 2012, 18:29:31
Hello,
Recently my htc wildfire S crashed and only boots to Hboot mode..
cannot go to recovery and cannot do factory reset.. when i press these options the phone just reboots to hboot mode
the phone can be detected via usb and i do get hboot usb plug detection as well fastboot usb mode..
I have tried hundreds of possibilities to flash but failed..
Have tried the RUU method via computer whereby i get different errors and also tried different RUU but unsuccessful
The last RUU that i had used to root my phone was
RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed
which worked well for one year but crashed after reseting to factory settings
now..
when my bootloader is unlocked i got error 155 image error
when my bootloader is relocked i get error 140 bootloader version error
both ways it stops during verifying for signature
and on the phone it shows main version older.. update failed
have tried to place PM76IMG.zip on sdcard but the phone reads as wrong or no image
(and this goes for different RUU as well)
have tried to use fastboot via cmd commands but get
FAILED (remote: 12 signature verify fail)
or
FAILED (remote: 43 signature verify fail)
images do load without problem but fail after signature checking
there is no other RUU newer than 2.26
cannot downgrade hboot cause cannot access my phone just hboot mode only
cannot do flash recovery as i have tried many recovery images all failing as well as clockword mode recovery image
PLEASE HELP load the ROM and make the phone usable again
Did you make a Gold card before placing PG76IMG in SD card?
tahaice said:
MARVEL PVT SHIP S-ON RL
HBOOT 1.09.0099
MICROP-0451
RADIO-7.57.39.10M
Feb 8 2012, 18:29:31
Hello,
Recently my htc wildfire S crashed and only boots to Hboot mode..
cannot go to recovery and cannot do factory reset.. when i press these options the phone just reboots to hboot mode
the phone can be detected via usb and i do get hboot usb plug detection as well fastboot usb mode..
I have tried hundreds of possibilities to flash but failed..
Have tried the RUU method via computer whereby i get different errors and also tried different RUU but unsuccessful
The last RUU that i had used to root my phone was
RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed
which worked well for one year but crashed after reseting to factory settings
now..
when my bootloader is unlocked i got error 155 image error
when my bootloader is relocked i get error 140 bootloader version error
both ways it stops during verifying for signature
and on the phone it shows main version older.. update failed
have tried to place PM76IMG.zip on sdcard but the phone reads as wrong or no image
(and this goes for different RUU as well)
have tried to use fastboot via cmd commands but get
FAILED (remote: 12 signature verify fail)
or
FAILED (remote: 43 signature verify fail)
images do load without problem but fail after signature checking
there is no other RUU newer than 2.26
cannot downgrade hboot cause cannot access my phone just hboot mode only
cannot do flash recovery as i have tried many recovery images all failing as well as clockword mode recovery image
PLEASE HELP load the ROM and make the phone usable again
Click to expand...
Click to collapse
Your recoverys are not flashing as you have relocked your bootloader pal. Try flashing the stock recovery from hboot this should at least have a factory reset option. Failing this, you should try re-unlocking your bootloader and then flashing cwm.
If all of this fails then you will need to gain access to an xtc clip, make the phone s-off and then flash any ruu you want bump this thread if you need anymore help
Sent from my Nexus 7 using Tapatalk HD
varun26296 said:
Did you make a Gold card before placing PG76IMG in SD card?
Click to expand...
Click to collapse
thanks for reply
i did not make a gold card.. my phone crashed on me without consent lol..
and i cannot make one now coz there is no shell or rom on my phone.. just bootloader and thats it..
unless there is a way around to make a goldcard via fastboot menu??
heavy_metal_man said:
Your recoverys are not flashing as you have relocked your bootloader pal. Try flashing the stock recovery from hboot this should at least have a factory reset option. Failing this, you should try re-unlocking your bootloader and then flashing cwm.
If all of this fails then you will need to gain access to an xtc clip, make the phone s-off and then flash any ruu you want bump this thread if you need anymore help
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for reply
none of the recoverys are flashing either bootloader is unlocked or relocked.. Tried even flashing CWM but all i get is errors that image verify fail!! unless i am going somewhere wrong..??
My phone is S-ON is there no around this without an xtc clip..?? coz thats another issue
tahaice said:
Thanks for reply
none of the recoverys are flashing either bootloader is unlocked or relocked.. Tried even flashing CWM but all i get is errors that image verify fail!! unless i am going somewhere wrong..??
My phone is S-ON is there no around this without an xtc clip..?? coz thats another issue
Click to expand...
Click to collapse
What errors are you getting when trying to flash cwm via fastboot while the bootloader is unlocked. Be specific please
Also their is no other way to s-off bar the xtc clip. But, once you have s-off trouble shooting bootloader/ruu issues is far easier
Sent from my Nexus 7 using Tapatalk HD
heavy_metal_man said:
What errors are you getting when trying to flash cwm via fastboot while the bootloader is unlocked. Be specific please
Also their is no other way to s-off bar the xtc clip. But, once you have s-off trouble shooting bootloader/ruu issues is far easier
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
#heavymetal
when UNLOCKED
image update error
when RELOCKED
signature verify fail
i tried flashing CWM version 5.0.2.8 image file..
(the same happens while flashing other files!!)
tahaice said:
#heavymetal
when UNLOCKED
image update error
when RELOCKED
signature verify fail
i tried flashing CWM version 5.0.2.8 image file..
(the same happens while flashing other files!!)
Click to expand...
Click to collapse
Ok while unlocked, take your cwm recovery image and rename it to recovery.img if you have not already.
Then boot into fastboot and use the command
Fastboot boot recovery recovery.img
Hopefully it will boot into the recovery. This is only tempoary, do not reboot until you have wiped everything. Check and see if it boots after full wipes.
If this fails you will need a xtc clip...
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
---------- Post added at 09:45 PM ---------- Previous post was at 09:04 PM ----------
heavy_metal_man said:
Ok while unlocked, take your cwm recovery image and rename it to recovery.img if you have not already.
Then boot into fastboot and use the command
Fastboot boot recovery recovery.img
Hopefully it will boot into the recovery. This is only tempoary, do not reboot until you have wiped everything. Check and see if it boots after full wipes.
If this fails you will need a xtc clip...
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Edit: the more i look into this the more it doesn't look good to be honest pal, most people who get into this state send it back to the manufacturer and get the motherboards replaced....
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
heavy_metal_man said:
Ok while unlocked, take your cwm recovery image and rename it to recovery.img if you have not already.
Then boot into fastboot and use the command
Fastboot boot recovery recovery.img
Hopefully it will boot into the recovery. This is only tempoary, do not reboot until you have wiped everything. Check and see if it boots after full wipes.
If this fails you will need a xtc clip...
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
---------- Post added at 09:45 PM ---------- Previous post was at 09:04 PM ----------
Edit: the more i look into this the more it doesn't look good to be honest pal, most people who get into this state send it back to the manufacturer and get the motherboards replaced....
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
tried again all possibilities..
with fastboot boot recovery recovery.img it does download successfully and writes booting.. however after the phone has booted by itself the htc screen shows up (with white background) and directly goes into fastboot menu without other options...
Maybe i am uploading wrong recovery image??
if its loading into bootloader menu that means my phone is soft bricked right?? which can be undone??
my dilemma is that i live in a third world country with no htc service providers or good phone repair shops who would have an xtc clip..
tahaice said:
tried again all possibilities..
with fastboot boot recovery recovery.img it does download successfully and writes booting.. however after the phone has booted by itself the htc screen shows up (with white background) and directly goes into fastboot menu without other options...
Maybe i am uploading wrong recovery image??
if its loading into bootloader menu that means my phone is soft bricked right?? which can be undone??
my dilemma is that i live in a third world country with no htc service providers or good phone repair shops who would have an xtc clip..
Click to expand...
Click to collapse
The main issue is that it should still boot into the recovery via fastboot regardless of its working state from what i have read the main nand seems to have some sort of error that it cannot over write so its not letting you boot anything weither that is a fail safe or not i dont know. At this point a xtc clip would be your last hope, but i cannot guarrentee it would work... I have an xtc clip, but i dont want to post it outside of the uk ......
Sent from my Nexus 7 using Tapatalk HD
Were you overclocked ? Were you using some sort of memory script ?
I'd say your best option is to have it sent back, smells like a burnt motherboard.
heavy_metal_man said:
The main issue is that it should still boot into the recovery via fastboot regardless of its working state from what i have read the main nand seems to have some sort of error that it cannot over write so its not letting you boot anything weither that is a fail safe or not i dont know. At this point a xtc clip would be your last hope, but i cannot guarrentee it would work... I have an xtc clip, but i dont want to post it outside of the uk ......
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
thanks for your help heavy metal.. seems i am left with a dead fone after all RIP :crying:
omnomnomkimiiee said:
Were you overclocked ? Were you using some sort of memory script ?
I'd say your best option is to have it sent back, smells like a burnt motherboard.
Click to expand...
Click to collapse
no didnt mess with phone settings.. didnt overclock it.. and no memory scripts.. though had installed avast anti-theft software.. would it have played a part? but i remember uninstalling the software before resetting my to factory settings!!
im sorry for your loss man what do you think you will do with the device? bin?
Recover soft-bricked HTC Wildfire S
tahaice said:
no didnt mess with phone settings.. didnt overclock it.. and no memory scripts.. though had installed avast anti-theft software.. would it have played a part? but i remember uninstalling the software before resetting my to factory settings!!
Click to expand...
Click to collapse
Hi tahaice!.
I just recovered an HTC Wildfire S A510e for a friend with a problem similar to yours!
He entered on HBOOT and wiped & format some partitions: data/factory reset, system, data, sdcard, etc.....
I read quickly your problem and I think that this can help you:
1.- Download the correct RUU from: androidfiles.org/ruu/?developer=Marvel_MarvelC
For instance, I used RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed for Spain (Device was with last update, my friend was sure).
You can check it on HBOOT:
MARVEL PVT SHIP S-ON RL
HBOOT 1.09.0099
MICROP-0451
RADIO-7.57.39.10M
Feb 8 2012, 18:29:31
Click to expand...
Click to collapse
And when you finish restore: go to Settings/About phone/Software info/More. Base band version must match the file you used (you will not restore radio.img, if not needed).
2.- Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be folders with long names (C:\Users\lefe\AppData\Local\Temp\{9739F95A-99D7-43BA-8AB6-E4F02264D361}\{50F2F878-636A-496F-A7CB-544C067E0C4B} for instance).
Inside one of them you will find the file rom.zip from RUU. Open it with 7zip and extract recovery.img, boot.img and system.img. Put it in the location you preffer (C:\Users\lefe\HTC Wildfire S A510e\ADB in the example).
You also need adb.exe, AdbWinApi.dll and fastboot.exe. Copy from the folder you found the file rom.zip (or from Android SDK tools if you have installed it).
3.- Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
As you say, this is not needed in your case because your phone goes directly. Just plug.
4.- Open a command prompt in Windows and navigate to the folder where you unpacked ADB / installed Android SDK tools. Flash the stock images extracted in step 2 above using the following commands (Remember to turn your firewall off):
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Click to expand...
Click to collapse
Example (what I did):
Code:
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash boot boot.img
sending 'boot' (2870 KB)...
OKAY [ 1.336s]
writing 'boot'...
OKAY [ 1.650s]
finished. total time: 2.994s
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash recovery recovery.img
sending 'recovery' (3494 KB)...
OKAY [ 1.572s]
writing 'recovery'...
OKAY [ 1.970s]
finished. total time: 3.554s
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash system system.img
sending 'system' (259862 KB)...
OKAY [ 31.535s]
writing 'system'...
OKAY [ 64.846s]
finished. total time: 96.393s
5.- Finally, in your phone go to HBOOT menu and make a FACTORY RESET.
If needed, PowerOff device (remove battery for 3 seconds) and Boot the phone into bootloader (hold down volume and press power).
That's all!!.
I hope you get lucky!
[Plz, mark thread as Solved if that helped you, other users will love to read it when googling]
heavy_metal_man said:
im sorry for your loss man what do you think you will do with the device? bin?
Click to expand...
Click to collapse
right now its hidden deep inside my cupboard.. dont want to see it near me!! a disappoinment
bolzass said:
Hi tahaice!.
I just recovered an HTC Wildfire S A510e for a friend with a problem similar to yours!
He entered on HBOOT and wiped & format some partitions: data/factory reset, system, data, sdcard, etc.....
I read quickly your problem and I think that this can help you:
1.- Download the correct RUU from: androidfiles.org/ruu/?developer=Marvel_MarvelC
For instance, I used RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed for Spain (Device was with last update, my friend was sure).
You can check it on HBOOT:
And when you finish restore: go to Settings/About phone/Software info/More. Base band version must match the file you used (you will not restore radio.img, if not needed).
2.- Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be folders with long names (C:\Users\lefe\AppData\Local\Temp\{9739F95A-99D7-43BA-8AB6-E4F02264D361}\{50F2F878-636A-496F-A7CB-544C067E0C4B} for instance).
Inside one of them you will find the file rom.zip from RUU. Open it with 7zip and extract recovery.img, boot.img and system.img. Put it in the location you preffer (C:\Users\lefe\HTC Wildfire S A510e\ADB in the example).
You also need adb.exe, AdbWinApi.dll and fastboot.exe. Copy from the folder you found the file rom.zip (or from Android SDK tools if you have installed it).
3.- Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
As you say, this is not needed in your case because your phone goes directly. Just plug.
4.- Open a command prompt in Windows and navigate to the folder where you unpacked ADB / installed Android SDK tools. Flash the stock images extracted in step 2 above using the following commands (Remember to turn your firewall off):
Example (what I did):
Code:
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash boot boot.img
sending 'boot' (2870 KB)...
OKAY [ 1.336s]
writing 'boot'...
OKAY [ 1.650s]
finished. total time: 2.994s
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash recovery recovery.img
sending 'recovery' (3494 KB)...
OKAY [ 1.572s]
writing 'recovery'...
OKAY [ 1.970s]
finished. total time: 3.554s
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash system system.img
sending 'system' (259862 KB)...
OKAY [ 31.535s]
writing 'system'...
OKAY [ 64.846s]
finished. total time: 96.393s
5.- Finally, in your phone go to HBOOT menu and make a FACTORY RESET.
If needed, PowerOff device (remove battery for 3 seconds) and Boot the phone into bootloader (hold down volume and press power).
That's all!!.
I hope you get lucky!
[Plz, mark thread as Solved if that helped you, other users will love to read it when googling]
Click to expand...
Click to collapse
thank bolzass for ur reply..
without doubt we have the same ROM version and i had downloaded the same RUU from androidfiles website.. but still getting those silly errors despite following each step carefully!! i dont know what has gone wrong
BY THE WAY I CANNOT ERASE USERDATA
it says FAILED (remote: not allowed)
can this be causing other errors???
tahaice said:
right now its hidden deep inside my cupboard.. dont want to see it near me!! a disappoinment
Click to expand...
Click to collapse
At this point its probably for the best
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
tahaice said:
thank bolzass for ur reply..
without doubt we have the same ROM version and i had downloaded the same RUU from androidfiles website.. but still getting those silly errors despite following each step carefully!! i dont know what has gone wrong
Click to expand...
Click to collapse
Ops!?!?..., Can you detail these errors?.
I'm also reading your message bellow about erasing Userdata...:$, detail also this scenario so we can think about your concret issues.
Keep fighting till you're sure there's nothing to do...

Categories

Resources