[Q] HTC Wildfire S WiFi Error & UI filckering - HTC Wildfire S

PHONE INFO:
-------------------------------------------------------------
HTC Wildfire S A510b
Android version
2.3.5
HTC Sense ver.
2.1
Build No
2.26.841.4
Kernel
2.6.35.10-ga9ceb63
Baseband
47.10.35.3029H_7.46.35.08
Marvel PVT SHIP S-ON RL
HBOOT-0.90.0000
MICROP-0451
RADIO-7.46.35.08
APR 8 2011M 17:45:10
-------------------------------------------------------------
Symptoms: Wi-fi stopped working (can't be turned on - error ) and all the icons and UI elements are filckering at times.
"Factory Reset" didn't work...
Had the idea to re-install the stock rom but didn't know how and couldn't find the right one on androidruu.com
Now considering a CM mod or something better if you can recommend for htc WFS if a stock can't be found.
While trying the "HTC Easy Unlock Bootloader Tool" (tried to install CM 10.1 for htc WFS) another problem occurred. When I came to the part when it puts the phone in HBOOT and I press any key ... in the cmd like "HTC Easy Unlock Bootloader Tool" it says:
Obtaining Unlock Token
... INFO[ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
Now copy the identifier token as shown here (use the right button of the mouse to choose mark and then press right button again to select) then paste the token at the botton of the page and submit. Opening HTVDEV site
Press any key to continue . . .
What to do people ? Help if you can. :crying:

Doesn't anyone know anything about this???
By googling, have found out that hboot 0.90 may not support "fastboot oem get_identifier_token" command
which is only logical after receiving "command error" in return.
So does anyone know how to update HBOOT from 0.90 to 1.09 ???? I tried from RUUs and PGs with no success.
Tried these (Phone is Next G, Telestra):
From Win7
1. RUU_Marvel_HTC_Europe_1.33.401.2_Radio_47.10.35.3029H_7.46.35.08_release_185724_signed
2. PG7612000_Marvel_hboot_1.09.0099_1.52.841.1_1.52.841.2_0214 (i.imgur.com/7NqUW2f.jpg)
nothing worked....
Extracted rom.zip and tried from sdcard:
1. This one has the same HBOOT version so nothing happened
2. This one couldn't do it because of image version difference
(It has 2 rom.zip files, rom_01.zip and rom_02.zip. Tried with renaming rom_02.zip to PG76IMG.zip because it contains newer ver. of HBOOT.)
still... nothing happened...
HELP, getting desperate here

Related

[Q] Can't fastboot after RUU Update, Bootloader - Bypassed

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

[DEV] Possible S-OFF using HTCdev for WFS A510e

Hi guys,
A good friend of mine recently requested me to help with rooting her Wildfire S A510e (purchased from SingTel, CID HTC__044). I managed to change her Wildfire S from S-ON to S-OFF via HTCdev. As far as I know, HTCdev isn't supposed to give you S-OFF but only to remove the NAND write locks on certain partitions.
Users: This is NOT for you. This is NOT a tutorial.​I will not be responsible for any bricked WFS.​
Here's what happened, pretty long so I'm gonna break it down into multiple sections. Important points in red.
Replacing SingTel ROM with HTC EU ROM
The phone was originally running Android 2.3.3, ROM version 1.35.707.1, HBOOT 0.90.0000. This ROM version is not supported by HTCdev unlock yet.
Reboot to HBOOT on WFS. Choose FASTBOOT.
Connect WFS to computer via USB.
Downloaded the HBOOT RUU for "hTC Asia India" from HTCdev. Attempted to install the RUU but got a CID error.
Disconnected WFS from computer.
Rebooted normally on WFS.
Connect WFS to computer via USB (Disk Drive).
Created a goldcard by using SimpleGoldCard while WFS is mounted as Disk Drive. (this wipes your SD card)
Disconnect WFS from computer and reboot.
Connect WFS to computer via USB (Disk Drive).
Downloaded RUU_Marvel_S_HTC_Europe_2.13.401.2
Ran the RUU. Went into %temp%, found the relevant directory and copied rom.zip to the goldcard as PG76IMG.zip.
Disconnect WFS from computer.
Turn off WFS and rebooted into HBOOT.
Went into HBOOT -> Fastboot. RUU_Marvel_S_HTC_Europe_2.13.401.2 was installed successfully (Android 2.3.5, ROM version 2.13.401.2, HBOOT 0.90.0000).
Installing HTCdev Unlock
Rebooted WFS into HBOOT.
Connect WFS to computer via USB.
Downloaded the HBOOT RUU from HTCdev for "HTC EU".
Ran the HBOOT RUU. RUU installation gets stuck at 50% ("Flushing radio...") for about 20 minutes.
Decided that the RUU has hung so disconnected WFS from USB and did a battery pull
RUU offered to do a recovery but I clicked "Exit".
Turn on WFS in HBOOT mode.
S-OFF obtained!
I was pretty much at "dafuq?" at this stage. I didn't even need to upload the device identifier to HTCdev to get an unlock key. The device was already S-OFF (HBOOT shows it)!
HBOOT remained at 0.90.0000.
I verified the S-OFF by flashing ClockWorkMod which went without issues.
Possible theory of operation: (just my thoughts)
The HTCdev HBOOT RUU provides a temporary S-OFF in order to unlock the NAND
When the RUU is done, it is supposed to restore S-ON to the device.
However, since the process was hung, the RUU had no chance of restoring the device to S-ON.
Hence the WFS was left at S-OFF.
If there are any adventurous devs around who are willing to try to dissect the RUU, please do so, but standard disclaimer applies. Attempting to interrupt the HBOOT RUU flashing is pretty dangerous and WILL possibly brick your device! I will not be held responsible if you brick your WFS!
This seems to be a case of pure luck.
Addendum:
The HBOOT RUU contains 2 ZIP files: rom_01.zip, rom_02.zip
They are presumably flashed in-order.
rom_01.zip contains Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img
rom_02.zip contains hboot_1.08.0099_6e20b6fac09.nb0 and radio_47.23a.35.3035H_7.53.39.03M_MR.img
My friend has radio version 47.23b.35.3035_7.54.39.08M. From here, we can tell that rom_01.zip was successfully flashed but rom_02.zip wasn't. Also notice the "special" file name of the first radio image.
Addendum 2:
It appears that both radio ROMs have the same size but different md5sum. Can someone with S-ON try to flash Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img? (Again, standard disclaimer applies)
i like the very last sentence that you used ...
good job anyway mate !
how do you go about flashing a radio??
---------- Post added at 04:12 AM ---------- Previous post was at 04:09 AM ----------
rom1.zip is 10.370.252
rom2.zip is 10.586.425
ie not the same size
stevie67 said:
rom1.zip is 10.370.252
rom2.zip is 10.586.425
ie not the same size
Click to expand...
Click to collapse
If you look into the ZIP files, Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img and radio_47.23a.35.3035H_7.53.39.03M_MR.img are both the same size.
Reboot to HBOOT, choose FASTBOOT, connect WFS to computer. Use "fastboot flash radio Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img".
ok i tried to flash this radio i put the .img file on my sdcard went to fastboot then recovery,install from sdcard and there was nothing there so i put the rom1.zip folder on my sdcard went to fastboot,install from sdcard,rom1.zip and got this
CWM-based Recovery v5.0.2.6
-- Installing: /sdcard/rom_01.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/rom_01.zip
(bad)
Installation aborted
did i do something wrong??
You must flash the radio with fastboot command. But this wont work, bc the hboot will check if the file is signed. And that isn't.
But try, maybe i'm not right.
Sent from my HTC Wildfire S A510e using XDA App
and the fastboot command is??
and the file says its signed
Reboot to HBOOT, choose FASTBOOT, connect WFS to computer. Use "fastboot flash radio Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img".
Click to expand...
Click to collapse
He said it
Sent from my HTC Wildfire S A510e using XDA App
My phone wouldn't update using the HTC method so I extracted the two ROMs from the RUU and flashed them seperately. After the first one (radio) I noticed that the phone was S-OFF but when I'd flashed the second it was S-ON again and I couldn't go back.
WOW, you have S-OFF after flashing radio via
fastboot flash radio radio.img
???
And now you can't go back?
I extracted the htcdev ruu and tried to flash the radio image. but it is not possible, signature check fails. so if the bootloader is already unlocked, it is not possible to obtain s-off this way
Have u test it with
fastboot oem lock
first and then to flash the radio.img?
Or to try to downfrade hnoot with the tutorial here in forum and then flash the new radio.
not yet. Will try that and report again
did relock phone using oem lock.
*** RELOCKED ***
Tried flashing 1st radio from htcdev ruu
flashing successful, but still S-ON
Hmm, and can u try to downgrade to Hboot 0.9 or Hboot 1.08?
I'm a noob so it's possible I made a mistake but I'm pretty sure I was S-OFF after the first flash. I was on Hboot 0.09.0000. Unfortunately I didn't realise the significance at the time so proceeded anyway.
I will try
I will try too, but earliest tomorrow, then i have my windows pc
this is what i get with or without bootloader locked
C:\Android>fastboot flash radio Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.0
8M_Signed_20111208.img
sending 'radio' (23936 KB)...
OKAY [ 5.375s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 13.063s
stevie67 said:
this is what i get with or without bootloader locked
C:\Android>fastboot flash radio Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.0
8M_Signed_20111208.img
sending 'radio' (23936 KB)...
OKAY [ 5.375s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 13.063s
Click to expand...
Click to collapse
I extracted the rom1.zip and renamed it PG76IMG.zip and flashed via hboot. this worked when the phone was re-locked
theq86 said:
I extracted the rom1.zip and renamed it PG76IMG.zip and flashed via hboot. this worked when the phone was re-locked
Click to expand...
Click to collapse
so are you now s-off??

Brick or bootloop?

Hi there,
I don't know what happened to my Desire Z, it was freeze while installing sth from Play, I restart it and saw only red triangle with exclamation mark.
I run it into hboot, choose every options one by one, and it tries to update. it was succesful, but now phone is freeze on HTC logo at booting.
I can enter to hboot, but cannot upgrade ROM, i tried several files called PC10IMG.zip downloaded from internet, but no one help.
I dl Android SDK, HTC Sync, and adb is working, but no attached devices. But in my Device manager it shows one connected unknown device called Android 1.0
I still can open hboot, Is there any chances to repair it somehow?
I add photo of hboot...
i47.tinypic.com/nvxht3.jpg
edit: i got into "fastboot usb" and it installed in my windows, so now there isnot Android 1.0 but "My HTC"
edit: I used this: http://forum.xda-developers.com/showthread.php?t=1193915 and it can communicate with my Desire, but also warning me, that: "This device does not have s-off nor eng hboot."
ok, i dl RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed.exe
I run phone in hboot, go to fastboot usb, Ruu started to upgrade and wants to restart phone and bootloader - when I allow, it dies on HTC logo, and RUU says that there is error in USB connection.
when I allow to reset and go to hboot again, massage is this same.
So it's is alive, but how bring it back to normal?
http://forum.xda-developers.com/showthread.php?p=33917375
Sent from my Nexus 7 using xda premium
1) Are you rooted? Which method did you use to obtain root?
No, It's not rooted
2) Can you access either bootloader mode or recovery on your phone?
Yes, I can
3) Write down everything you can on this screen, including *SYSTEM INFO*
if you have it and the output from *IMAGE CRC*
Code:
Vision PVT SHIP S-ON
HBOOT-0.85.0005
Microp-0425
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010,20:10:38
HBOOT USB PLUG
<Vol up> to previous item
<vol down> to next item
<power> to select item
Fastboot
Recovery
Factory reset
simlock
image crc
I cannot see where "System info" is
Code:
Image CRC
calculating...please wait
hboot: 0x446acd38
boot 0xd28a4324
recovery: 0x2254909
system: 0x7c930797
press power key to go back
4) Which recovery do you have? Stock? Clockwork? 4EXT? Version #...
Stock, I guess... i didnt change this
then I select it, it reboots phone, and after HTC logo shown, it dies.
5) What happened recently or just prior that may have cause this?
It freezes while installing some app from Google Play
6) Pull a logcat of the bootloop
ADB doesnt recognise any attached device.
Only RUU and fastboot
EDIT:
while using UniExtract i get the file rom.zip from RUU, rename it, and tried to flash...
Code:
fastboot flash update PC10IMG.zip
sending 'update' (291447 KB)...
OKAY [ 48.782s]
writing 'update'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 105.805s
EDIT again.
I copied this file from RUU to SD card, but it shows mi info: Model ID incorrect! Update Fail!
So
I have, I use:
fastboot getvar cid
cid: HTC__032
finished. total time: 0.002s
Click to expand...
Click to collapse
fastboot getvar version-main
version-main: 1.34.405.5
finished. total time: 0.003s
Click to expand...
Click to collapse
RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e _26.03.02.26_M_release_155556_signed.exe
Click to expand...
Click to collapse
Maybe I use wrong RUU? But It was only one I found with this radio
Try the latest ruu downloaded directly from htc.com
Sent from my T-Mobile G2 using xda premium
There aren't any files to HTC Desire Z or Vision on HTC site ;/
But:then I installing one of those downloaded earlier, they can connect to phone, it wants to flash after telephone reboots. When it rebots i stuck with HTC logo, if I force it to go to hboot-fastboot usb, RUU says that there was an error with usb connection
If I try to flash it using flasbot all I can see is:
Code:
C:\kpina\adt-bundle-windows-x86_64\sdk\sdk\platform-tools>fastboot flash zip PC1
0IMG.zip
sending 'zip' (291447 KB)...
OKAY [ 48.957s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: not allowed)
finished. total time: 120.273s

[Q] Desire HD can't boot (red triangle) after AAHK Fail

Hi everyone!
I've managed to screw up my Desire HD after running aahk-11092012, and was wondering if anyone had any bright ideas...
The Phone is a Desire HD bought from SFR here in France in 2011, never rooted or custom rom'ed, although updated with 2or 3 SFR roms since.
I ran aahk from the terminal on a OSX 10.7 (see Output.txt). From this you will see that it wants naturally to downgrade (to Froyo I assume) but downloading the rom fails, and even though I refused the "-n Flash this RUU? (y/n)" question, it continued doing all sorts of things, getting a few error along the way, rebooting the phone into recovery a few times, and finishes with
************* Downgrade failed *************
** Either:
** GoldCtixiard/SDCard failed
** USB connections are not working 100%
************* Downgrade failed *************
I then tried to flash the "Gingerbread HTC WWE 2.50.405.2" rom from the options menu, thinking I'd be clever, but that monumentally fails too..
From this point on the phone boots to the "Red tringle with an exclamation mark" screen (after the white HTC logo) and does nothing else.
Restarting AAHK just fails with a "Error detecting HTC phone on USB connection."
Having discovered the "VOL-UP +Power" recovery screen during this process, the next thing I tried was a "Apply sdcard:update.zip", but this just results in an "Invalid command" message underneath that already present "E: Can't open /cache/recovery/command" in yellow further down the screen.
I then try a "Wipe data/factory reset" and also a "Wipe cache partition". I can't honestly explain this. At least not given that I hadn't really looked up the issue anywhere yet. I also cant remember exactly what the output was, but the result is the same, still the red triangle screen.
OK, so now I finally open my eyes and realize what a moron I've been, so i plunge into actually learning something and realize quickly (aside from I hate myself and I'm not special, bla bla) that there are loads of thing I could have done differently, and directly on the phone, but obviously it's now too late. (See below for the information I CAN get from the Phone)
Oh yes, I did try a "Factory reset" from HBOOT, but still no joy....
The main option I've been looking into has been to recover an original branded SFR firmware and Froyo ROM and go from there, so I did manage to get a PD98IMG.zip file onto the SD card and HBOOT recognizes it, but fails with a "CID Incorrect" error.
I seem, therefore to be stuck whether I want to return to original SFR or continue tryng to flash a custom ROM:
I can't make a goldcard: I cant adb any commands, in HBOOT the device is not found, and in recovery the device is found but is "offline".
I found jo0ls' CID reader, but I dont have a SD card reader directly plugged to the PCI bus!
I did finally try to install a clockwork recovery in FASTBOOT, but get this:
$ fastboot flash recovery recovery-clockwork-5.0.2.0-ace.img
sending 'recovery' (3624 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
I assume this is much the same error as for the PD98IMG...
Sorry about the long winded post, but I hope it has the maximum of info...
Anyone have any ideas?
- I can boot to HBOOT: it shows me this:
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.03.02.26_M
eMMC-boot
Sep 7 2011, 19:06:24
- ...and FASTBOOT, fastboot getvar all gives this:
INFOversion: 0.5
INFOversion-bootloader: 2.00.0027
INFOversion-baseband: 26.03.02.26_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 1.32.405.6
INFOserialno: SH12GRX00567
INFOimei: 356812048021701
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9810000
INFOcidnum: VODAP203
INFObattery-status: good
INFObattery-voltage: 4199mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 743ca94a
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
- The recovery is the original "Android system recovery <3e>"
AAHK, and the server hosting the downgrade files, is retired. You can still unlock the bootloader, but your hboot needs updating before it cam be unlocked. I think you could also run your stock RUU.
CID Number shows that your device is a Vodafone device, probably VodaSFR but who knows? Fetch a Voda RUU and install it
Sent from my Desire HD using Tapatalk 2
you need to upgrade your bootloader to 2.00.0029
htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe (sorry, i can´t atach links)
then unlock it(follow htc-dev guide) and you will be able of flashing a custom recovery
pascuals said:
you need to upgrade your bootloader to 2.00.0029
htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe (sorry, i can´t atach links)
then unlock it(follow htc-dev guide) and you will be able of flashing a custom recovery
Click to expand...
Click to collapse
Thanks for all your answers!
@ bananagranola: I did know aahk had been discontinued, I actually mentioned this originally but edited it out to "shorten my post"!
@ humzaahmed155: quite right, I'm with SFR, and I'm trying to simply restore an original branded ROM
@ pascuals: I will look into your suggestion right away! I was vaguely aware I might have to do this but could not get an accurate enough idea of what version might be appropriate for my phone
[SOLVED] [Q] Desire HD can't boot (red triangle) after AAHK Fail
Kawika1611 said:
Thanks for all your answers!
@ bananagranola: I did know aahk had been discontinued, I actually mentioned this originally but edited it out to "shorten my post"!
@ humzaahmed155: quite right, I'm with SFR, and I'm trying to simply restore an original branded ROM
@ pascuals: I will look into your suggestion right away! I was vaguely aware I might have to do this but could not get an accurate enough idea of what version might be appropriate for my phone
Click to expand...
Click to collapse
Woohoo!! I'm so happy, I got the phone working again last night!! I had a ruu kicking around:
RUU_Ace_Sense30_S_Vodafone_FR_3.13.163.3_Radio_12.65.60.29_26.14.04.28_M_release_227340_signed.exe
from the first day I'd bricked it. This hadn't worked the first time I tried it on windows (actually a Parallels VM on Mac), with the phone plugged in, but I can't remember what mode the phone was in; but as you'll see below I must not have been in fastboot...
Whatever, last night I finally tried pascuals's PD9810000 RUU, with the phone connected and in fastboot, the utility detects the phone fine, but fails with a firmware version error, saying the phone is 1.32.405.6, it will install version 3.13.0.0 but I need to "upgrade to 3.12.405.1"..:silly: (see attachments).
Feeling dejected I fired up the rom cited above thinking I have nothing to lose, and...lo an behold...10 minutes or so later the phone reboots to a beautiful welcome screen insulting me for not having inserted a SIM card!!!
Thanks anyway for your answers, at least they got me looking in the right direction!! I will now go a learn properly how this things work before bricking it again
pascuals said:
you need to upgrade your bootloader to 2.00.0029
htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe (sorry, i can´t atach links)
then unlock it(follow htc-dev guide) and you will be able of flashing a custom recovery
Click to expand...
Click to collapse
My HBOOT is 0.85.2425, after S-OFF. Can I update to 2.00.0029? How?
Thanks.
use that link and just run the exe with your phone connected, atleast with debugging on i think, mine was like that, the tool took care of the rest automatically.
mobidor said:
My HBOOT is 0.85.2425, after S-OFF. Can I update to 2.00.0029? How?
Thanks.
Click to expand...
Click to collapse
I see no reason why you need to update the bootloader when you already have s-off. If your bootloader is engineering bootloader then just let it be.
Sent from my Desire HD

[Q] HTC One Verizon Bricked Badly! PLease Help

okay so My HTC One M7 Verizon which I use in India on a Vodafone Network is stuck on the bootloader menu.
3 weeks ago i rooted my phone and installed a custom ROM but it got stuckk in wiping the cache but somehow i fixed it and installed a stock ROM (4.4.2) after doing all this my phone worked fine for 2 weeks and suddenly early morning it went off and dint boot-up and now its stuck in the bootloader menu, and no recovery, so i tried to get it back to Stock so as i started i got my Phone into re-lock state and made it S-ON but now it doesnt accept the RUU and even The OEM RUU BOOT fails! and if i try to UNLOCK AND S-OFF again it says no device found.
Phone state
***TAMPERED***
***RELOCKED***
m7_WLV PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO 1.12.42.0731
OpenDSP v31.120.274.0617
OS- 1.10.605.8 (1.10.605.10)
so now it only boots up into the bootload
when i try to unlock+S-OFF it says so devices found
and when i try to flash the RUU and type 'oem rebootRUU' this shows up
"bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.492s]
rebooting...
finished. total time: 1.582s" (phone goes off!)
PLEASE HELP!
architsheth said:
okay so My HTC One M7 Verizon which I use in India on a Vodafone Network is stuck on the bootloader menu.
3 weeks ago i rooted my phone and installed a custom ROM but it got stuckk in wiping the cache but somehow i fixed it and installed a stock ROM (4.4.2) after doing all this my phone worked fine for 2 weeks and suddenly early morning it went off and dint boot-up and now its stuck in the bootloader menu, and no recovery, so i tried to get it back to Stock so as i started i got my Phone into re-lock state and made it S-ON but now it doesnt accept the RUU and even The OEM RUU BOOT fails! and if i try to UNLOCK AND S-OFF again it says no device found.
Phone state
***TAMPERED***
***RELOCKED***
m7_WLV PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO 1.12.42.0731
OpenDSP v31.120.274.0617
OS- 1.10.605.8 (1.10.605.10)
so now it only boots up into the bootload
when i try to unlock+S-OFF it says so devices found
and when i try to flash the RUU and type 'oem rebootRUU' this shows up
"bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.492s]
rebooting...
finished. total time: 1.582s" (phone goes off!)
PLEASE HELP!
Click to expand...
Click to collapse
Don't ever s on again
The command is "fastboot oem rebootRUU"
Use this ruu... http://click.xda-developers.com/api...TC One | XDA Forum&txt=1.10.605.10 Signed RUU
Try It
First you need to do is s-off it and then flash the ruu that is given in #2 i used the same and i had no problems at all . I am form India as well
Unlock your bootloader later on but soff it first.
https://www.youtube.com/watch?v=e4zBk2m1FPU
architsheth said:
okay so My HTC One M7 Verizon which I use in India on a Vodafone Network is stuck on the bootloader menu.
3 weeks ago i rooted my phone and installed a custom ROM but it got stuckk in wiping the cache but somehow i fixed it and installed a stock ROM (4.4.2) after doing all this my phone worked fine for 2 weeks and suddenly early morning it went off and dint boot-up and now its stuck in the bootloader menu, and no recovery, so i tried to get it back to Stock so as i started i got my Phone into re-lock state and made it S-ON but now it doesnt accept the RUU and even The OEM RUU BOOT fails! and if i try to UNLOCK AND S-OFF again it says no device found.
Phone state
***TAMPERED***
***RELOCKED***
m7_WLV PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO 1.12.42.0731
OpenDSP v31.120.274.0617
OS- 1.10.605.8 (1.10.605.10)
so now it only boots up into the bootload
when i try to unlock+S-OFF it says so devices found
and when i try to flash the RUU and type 'oem rebootRUU' this shows up
"bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.492s]
rebooting...
finished. total time: 1.582s" (phone goes off!)
PLEASE HELP!
Click to expand...
Click to collapse
Here is how to fix it
Download this RUU file which matches your hboot
http://bit.ly/vzwone10
then put the file in your fastboot / adb directory, and rename it to Rom.zip
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip Rom.zip (rename file to Rom.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip Rom.zip
Then when it finishes, type "fastboot reboot"
Enjoy.
PS - NEVER s-on your phone. You do not to be s-on for ANYTHING. But being s-on will stop you from doing pretty much everything. The only reason to EVER revert to S-on is to send your phone in for a warranty replacement.
As soon as you finish those steps, go ahead and use rumrunner for your hboot version to get s-off again. Once you are s-off, you can take all your ota updates to get the newest firmware / stock rom, then flash a custom recovery through fastboot, and flash superuser or a custom rom from your recovery. You NEED s-off though. If you were s-off now this would be a simple fix, just flash firmware / recovery and a rom, but since you are s-on you are going to have to go to the matching stock RUU for your bootloader, and start from scratch. Hope i helped.

Categories

Resources