Develop Bugs

[Q] Stuck on S-Off Screen

Hi, i've been using LeeDroid for a few months now and all has been well, however yesterday my Desire turned itself off and now won't come back on. Each time i try and power it up it freezes at the Alpharev S-Off screen. I went into the menu's with volume down + power, but i can't get into my recovery - it takes me to the same frozen screen as does trying to reboot etc. And i don't think it's being recognized by usb either. So i really don't know what to do now.. is my phone bricked? I was a complete noob before rooting and flashing a custom rom before, so now that i've hit a problem i'm clueless all over again. Any help would be greatly appreciated

can you use fastboot? If so just flash a new recovery and all should be fine... chill out it can be fixed

What would i need for that? That's going into new territory

j3nni said:
What would i need for that? That's going into new territory
Click to expand...
Click to collapse
Can you access recovery? If no can you access bootloader (vol down + power on)

I can get onto the menu with the options 'fastboot, recovery, clear storage and simlock' if that's what you mean? The recovery option takes me back to my frozen alpharev screen, but i can get onto fastboot and after reading around i can get my pc to recognize it from fastboot usb from my pc using cmd.. Am i going the right direction at all? Eek. What i don't get now is the recovery image i'm supposed to use

j3nni said:
I can get onto the menu with the options 'fastboot, recovery, clear storage and simlock' if that's what you mean? The recovery option takes me back to my frozen alpharev screen, but i can get onto fastboot and after reading around i can get my pc to recognize it from fastboot usb from my pc using cmd.. Am i going the right direction at all? Eek. What i don't get now is the recovery image i'm supposed to use
Click to expand...
Click to collapse
Use amon_RA ... Download and flash onto ur phone and ur phone should be fixed
Plenty of guides around man, good way of learning fastboot

to use fastboot you need to download several things. Instead of using fastboot with cmd, I'd just recommend using fastboot commander, which does the job for you. In order to use that however, you will need the adb drivers, and Java SDK.
Once you've got all that, simply boot into fastboot, run "fastboot commander.exe", go into the "misc" tab, wipe Recovery, system, cache, boot, and userdata. Once you've done that download recovery, navigate to the "Hboot, radio & Rec" tab on fastboot commander, select recovery, find the recovery.img you just downloaded, and flash it. Once you've done that just boot into recovery and install any ROM you want.

Thanks for the replies guys. I did what you said to do (using fastboot commander), and when trying to boot into recovery to install my ROM it froze again at the alpharev screen. I'm stuck again now. When the files show up as you turn on into fastboot, i'm getting this..
SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nhh]
No Image or Wrong Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nhh]
No Image or Wrong Image!it's saying my pb****.img files arn't found
which i gather can be normal. Other than that i'm stumped again

j3nni said:
Thanks for the replies guys. I did what you said to do (using fastboot commander), and when trying to boot into recovery to install my ROM it froze again at the alpharev screen. I'm stuck again now. When the files show up as you turn on into fastboot, i'm getting this..
SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nhh]
No Image or Wrong Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nhh]
No Image or Wrong Image!it's saying my pb****.img files arn't found
which i gather can be normal. Other than that i'm stumped again
Click to expand...
Click to collapse
try do a full wipe of everything like I've mentioned before and then a different HBOOT

Okiedoke, how do i use a different hboot? And where do i find one from? At the moment i believe it's 0.93

j3nni said:
Okiedoke, how do i use a different hboot? And where do i find one from? At the moment i believe it's 0.93
Click to expand...
Click to collapse
www.alpharev.nl download a HBOOT and flash it through fastboot. Just make sure to check MD5 (you need a MD5 utility AFAIK)

I'm not sure which one is the right one for my ROM, i'm using LeeDroid.. Sorry for all the questions!

j3nni said:
I'm not sure which one is the right one for my ROM, i'm using LeeDroid.. Sorry for all the questions!
Click to expand...
Click to collapse
For any sense UI ROMs you would use the Sense HBOOT, remember to nandroid backup before you do so! because you might find that you get a bootloop after flashing the HBOOT.
And don't worry about asking questions! it's what we're all here for.
By the way if you don't know what different HBOOTs do: they change the partition sizes for /system /cache and /data. So by using a different HBOOT instead of the stock one you may get more storage for apps etc. if you choose one with a larger /data partition.... if that makes sense

Ok the sense one it is =)
Ah i see! Thanks for explaining cos underneath the nerd in me would have been wondering what it did lol.
Not sure how to get a nandroid done when i can't get into recovery though

I still havn't got anywhere with my problem, if anyone could advise me further i'd really appreciate it, as this is really stressing me out now.
The only screen i can still ever see is a frozen alpharev screen, and i still can't enter recovery. I've cleared everything using fastboot commander and flashed a new recovery which did nothing. Then i took the next advice and flashed a new hboot. The hboot has changed on my hboot menu (vol down + power) but still goes to the frozen alpharev screen when i try to go to recovery or turn the phone on. I then flashed a LeeDroid rom, which came up with an error at the end of it..
"sending 'zip' (173060 KB)... OKAY [ 23.469s]
writing 'zip'... FAILED (remote: not allowed)"
And that's as far as i've got.
Reading further i've been trying to work out how to flash a stock ruu to see if that works. However my phone was a branded Orange UK phone before so there is no ruu for that. So my question is, bearing in mind i can't get into the phone at all, how can i go about downgrading the hboot and installing a htc stock ruu. Can anyone point me to the right files i would need. I really don't know what i'm doing and i think the amount of searching i've been doing is just confusing me further

j3nni said:
I still havn't got anywhere with my problem, if anyone could advise me further i'd really appreciate it, as this is really stressing me out now.
The only screen i can still ever see is a frozen alpharev screen, and i still can't enter recovery. I've cleared everything using fastboot commander and flashed a new recovery which did nothing. Then i took the next advice and flashed a new hboot. The hboot has changed on my hboot menu (vol down + power) but still goes to the frozen alpharev screen when i try to go to recovery or turn the phone on. I then flashed a LeeDroid rom, which came up with an error at the end of it..
"sending 'zip' (173060 KB)... OKAY [ 23.469s]
writing 'zip'... FAILED (remote: not allowed)"
And that's as far as i've got.
Reading further i've been trying to work out how to flash a stock ruu to see if that works. However my phone was a branded Orange UK phone before so there is no ruu for that. So my question is, bearing in mind i can't get into the phone at all, how can i go about downgrading the hboot and installing a htc stock ruu. Can anyone point me to the right files i would need. I really don't know what i'm doing and i think the amount of searching i've been doing is just confusing me further
Click to expand...
Click to collapse
Hi.
As I can see the only way to restore is using a RUU to go back to stock then root and S-Off the phone again.
First: Preparation.
1. If you have a custom HBOOT (e.g.: 6.93.0001) you need first to flash the HBOOT Downgrader (found on alpharev site), then flash the RUU.
2. You will gonna need a Gold Card if your phone was branded.
Second: Starting
1. Make your Gold Card using someone's else phone (it has to be running Android) - the Gold Card is unique per SD Card, not per phone.
2. Use this tool to make the Gold Card: HERE
3. Guide how to make a Gold Card in Linux: HERE
4. get the latest RUU WWE 2.29.405.5. Extract the PB99IMG.zip file from the RUU: here it is how: http://forum.xda-developers.com/showthread.php?t=880268 -2nd post.
5. Reboot in bootloader (Volume-Down + Power)
7. Select fastboot
8. Flash the HBOOT Downgrader (don't forget to check the MD5 of the file you have downloaded from alpharev)
9. Extract the PB99IMG.zip and put it on root of SD Card.
10. Reboot in bootloader (scroll to REBOOT and select)
11. It will automatically load the img and ask you if you want to install
12. Check Yes and follow onscreen progress.
13. Wait untill it finnishes
14. I think it will reboot itself, if not scroll down to the Reboot obtion and press Power button to select.
IMPORTANT WARNING!!!
droidzone said:
Whatever you do, DO NOT turn off the device manually unless the software tells you to. If something goes wrong, dont switch off phone. Keep the phone on while trying a solution. Newer RUUs dont usually wreck a phone, and with a goldcard, you can always recover. But, the flash SHOULD NOT be interrupted by switching off or disconnecting the cable.
Always start with a battery with >50% power (full recommended).
Click to expand...
Click to collapse

Or if you want to go to stock and it is an unbranded phone you can just run ur ruu when the phone is in fastboot
Sent from my HTC Desire using XDA App

Think i may be the happiest girl in the world today lol i finally got it all fixed. I had a bit of trouble making the goldcard as at first my sd card kept saying it needed to be reformatted after, but after formatting it with SD Formatter program rather than Vista's own, it worked. All the rest went without a hitch. Now just gotta root, s-off and grab my new ROM and this past week can all get forgotten about =)
Thankyou so much to everyone that helped!
Incase anyone does read this far, is the procedure still the same as when i first used it back in April.. from here? http://forum.xda-developers.com/showthread.php?t=1016084

It is still the same.

If you like sense -
http://forum.xda-developers.com/showthread.php?t=1054435
░█░ [ROM][28/06] ✰.Reflex S v2.1.7 Gingerbread 2.3.3· ░█░ · |SenseGingerB 2.1+3.0|
You might like it...

Rom Advice / Steps please

Good Afternoon everyone,
Here once again. I have been having lots of problems recently with my phone memory getting low, crashes freezing, un-expected reboots etc. I have been using the same rom for a few months and was fine at first but just broke down. So I went into recovery and did a wipe now when powered on for the first time it doesnt get past boot animation just stay on the screen no matter how many reboots or further wipes. I also got a brand new 32GB Micro SD card for xmas that I haven't used yet so my idea was to get a new cool rom and use the SD card
First of all which rom. Now I know people say try different roms and see which you like but so many roms I dont know what to go for and was wondering for some advice. My requirements are that it is not ICS version as I get a phone upgrade on contract in July and want to leave ICS for a new phone so Gingerbread it is.
Now the rom requirements are:
> HTC Sense, prefferably a latest 3D version but if it doesn't work or very laggy then no.
> Camera needs to be fully working
> USB Tethering
> As much as possible on the SD card to save phone space
> Dont need super battery life but at least something that lasts a day and doesnt drain it
> Music Working nicely
> Not too buggy and fairly stable
Now secondly I still have not got myself familiar with Android flashing etc. If I want to start again from scratch new memory card does anyone know the steps. Is there any plain step by step instructions out there that tells me completly what I need to do as I can get confused quite easily.
Thanks in advance for any responses,
Regards,
Max

For this moment(in my opinion) this is the one from the best ROM for HTC Desire...including everything what you questing...
http://forum.xda-developers.com/showthread.php?t=1315961

Thanks. I was already interested in this rom and you saying that has swayed by boat. The next problem is how to go about it. the first steps appears to be installing EXT4 Recovery but its an APK and they are installed with the phone botted up normally correct? My phone isnt booting only in Recovery Mode which is the clockwork mod (from about 8 months ago)

4ext has an app to download its recovery. If you are s-off, the app will flash the recovery img.
Sent from my HTC Desire using Tapatalk

Ok I beleive I do have S-OFF from previous flashing however I can no longer boot the rom up so what do I do?
I can boot into recovery mode but as soon as I boot normally it just sits on the boot animation completly animated but never going further (left it for 3 hours until battery died) also tried wiping about 5 times after a wipe and I just cannot get it on. So what do I do?

I'll upload it for you (from my sd card).
If you are s-off, you can fastboot flash it (see link to my guides for info on fastboot flash - Forget adb, not relevant...)

Thanks but I am a little confused as to what I am doing.
Is there any step by step?
i have the 4EXT now not installed yet. What about HBOOT, radio rom I have no idea what I am doing in what order now due to my phone not botting :-(

If you don't have 4EXT recovery-reboot phone normally, install this app and update you're recovery from the list...

But if you read above I cannot boot my phone normally!

1.update the recovery(like i say)
2.change the hboot:downolad file PB99IMG.zip, put it on your sdcard, then start the phone in HBOOT mode (VolDown+POWER) to flash(update) the HBOOT.
3.Restart phone in recovery,perform full wipe(format all partition without FAT32)
4.Download file with ROM, put into your SDCARD and reflash...

I am sorry not having much luck. I have put both the EXT4 recoevry zip and the pb99img zip on my memory card rebooted into the boot loader with vol down went into the fastboot option and the only options there are bootloader (takes me back to main screen) reboot, reboot bootloader and power down.
I am so lsot and need my phone working again :-(

max_carpenter said:
But if you read above I cannot boot my phone normally!
Click to expand...
Click to collapse
If you'd bothered to read the fastboot faq I told you to read, you'd know that you fastboot flash from the fastboot screen NOT in Android!
max_carpenter said:
Irebooted into the boot loader with vol down went into the fastboot option and the only options there are bootloader (takes me back to main screen) reboot, reboot bootloader and power down.
Click to expand...
Click to collapse
Again, all in the FAQ you were supposed to read!!!

Sorry missed the link couldnt see one very tired. I appreciate your help. I am looking over it now trying to figure it out.

max_carpenter said:
Sorry missed the link couldnt see one very tired. I appreciate your help. I am looking over it now trying to figure it out.
Click to expand...
Click to collapse
OK good luck, although if you're tired, it may be better to wait until tomorrow. Its not broken so its just a case of remaining calm and doing the required.

Ok I think I got it phone is plugged in with the HBOOT drivers I h ave extracted that EXT4 zip you sent me to the C Drive and I run the following command:
fastboot flash recovery c:\recovery.img
Just wanted to check before I did it.

Hmm ok I have done something wrong :-(
sending 'recovery' (3730 KB)... FAILED (status malformed (1 bytes))
finished. total time: 0.004s

Ok I went into FASTBOOT on the phone screen then tried running the command again and I get this:
sending 'recovery' (3730 KB)... OKAY [ 0.676s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.197s

Are you sure you're s-off? Should say on the hboot screen
Sent from my HTC Desire using Tapatalk

Ahh its on damn I am sure it was off. Dont you have to be booted into a rom to get it off though?

Ok so who is clever enough to figure out the mess I am in now then..
1: Custom rom Won't boot even after wipe/several reboots
2: HBOOT Version = PVT1 0.93.0001
3: Radio Version = 5.09.05.30_2
4: Recovery Image is ClockworkMod v2.5.0.7
5: S-ON is set
6: Running the HTC Official RUU returns this error after a little while:
ERROR[140]: Bootloader version error
7: I have been asked to run the following commands with the following files and results are on each line after the = sign:
fastboot erase cache = OK
fastboot oem rebootruu = ... INFO[ERR] Command error !!!
fastboot flash zip C:\rom.zip = INFOsignature checking...
FAILED (remote: not allowed)
fastboot flash zip C:\PB99img.zip = FAILED (remote: signature verify fail)
rom.zip was extracted from the official HTC RUU utility.
Any ideas? At the moment i will be pleased jsut to get back to stock.

[Q] Flashed EU HOX with AT&T stuff and BRICKED! Please help

I'm desparate, please help me!
I flashed the remove-3-dot for the AT&T HOX, but I have another one. Now I cannot go back, since the device doesn't completely boot.
It is stuck with the HTC figures showing up and halfway the music stops and the device hangs.
I can go to recovery, but since the Àll-In-One Kit from Hasoon2000 doesn't see the device when in recovery (CWM 5.8.2.7 Touch), I cannot even put anything to the SD card, so I cannot even flash anything else!
Please help me before the battery dies out!! (I cannot turn it off since lonng press of the power button only restarts the booting)

If you have CWM did you made a nondroid backup?

Bright.Light said:
I'm desparate, please help me!
I flashed the remove-3-dot for the AT&T HOX, but I have another one. Now I cannot go back, since the device doesn't completely boot.
It is stuck with the HTC figures showing up and halfway the music stops and the device hangs.
I can go to recovery, but since the Àll-In-One Kit from Hasoon2000 doesn't see the device when in recovery (CWM 5.8.2.7 Touch), I cannot even put anything to the SD card, so I cannot even flash anything else!
Please help me before the battery dies out!! (I cannot turn it off since lonng press of the power button only restarts the booting)
Click to expand...
Click to collapse
THIS will help you

@muamers: Thanks!!
I already found out how to turn the device off, not draining the battery anymore.
I also flashed the new CWM 5.8.3.1 so it should have some ability to charge.
I am currently downloading the latest stock 1.29.401.11 and will try to flash that one.
I did search, but it's difficult currently. However, I made a permanent link to the Wiki - it's more than useful (the reason it exists, I know...)
Oh - it wasn't bricked (because it still did some stuff)
@jeyml: No, I did not do that (didn't know it was possible)
Does that mean that I could recover with the rom exactly as it was put on the device? (including installed ZIP files)

Bright.Light said:
@muamers: Thanks!!
I already found out how to turn the device off, not draining the battery anymore.
I also flashed the new CWM 5.8.3.1 so it should have some ability to charge.
I am currently downloading the latest stock 1.29.401.11 and will try to flash that one.
I did search, but it's difficult currently. However, I made a permanent link to the Wiki - it's more than useful (the reason it exists, I know...)
Oh - it wasn't bricked (because it still did some stuff)
@jeyml: No, I did not do that (didn't know it was possible)
Does that mean that I could recover with the rom exactly as it was put on the device? (including installed ZIP files)
Click to expand...
Click to collapse
Yup.It is actualy quite simple,i always do a backup before i flash something or update my ROM and other stuff.You keep the volume down + power button.After that you enter recovery mode (you will need to have CWM) and you have an option there "backup and restore",enter there and make a backup.Next time if you have any problems just enter again in the CWM,go to "backup and restore" and restore the backup you've made.It saves everything you have (i mean the ROM setting and such.Apps and other stuff must be backed up with Titanium Backup).
The backups you made are saved in the SD card in the nandroid directory if i remember corectly,so if you update you're ROM to...1.29 for example and have a 1.28 backup just enter there and delete it and make a new backup of the 1.29 so you don't get confused in so many backups and if you ever have problems and restore a 1.28 backup on you'r 1.29..well...you realize that the phone isn't going to work anymore.So,be carefoul.

Didn't work... I downloaded this rom: RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed
did everything this page told us: http://forum.xda-developers.com/showthread.php?t=1609190
But I do not see anything change... It's still stuck in the boot process.
I don't know what I am doing wrong...
I also didn't find a clear guide for how to do things - it's all pieces which everyone has to put together, making it hard when there is a real problem.
If this can be solved, I will investigate the nand backup for certain!
For now I need my phone, but it does not work...
Oh - how does the charging with the new clockwork work? I don't see anything happen, so I am afraid the battery will be down soon.
edit: It was on power all night and when I looked it had the screen on. Unplugging and replugging and the gren light went on. Does that mean the battery is filled?
One important fact: the adb command cannot find the device and I don't know why!

How did you flash the RUU? You have to connect the phone in FASTBOOT to the PC and then run it (with a locked bootloader) and it replaces the entire system

EddyOS said:
How did you flash the RUU? You have to connect the phone in FASTBOOT to the PC and then run it (with a locked bootloader) and it replaces the entire system
Click to expand...
Click to collapse
with a LOCKED bootloader?
Mine is unlocked...
I will try to relock the boorloader (saw somewhere a snippet)

Tried with a locked one:
Code:
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot oem lock
... INFOLock successfully...
OKAY [ 0.143s]
finished. total time: 0.143s
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot flash boot boot_signed.img
sending 'boot' (4288 KB)... OKAY [ 0.667s]
writing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.874s
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot flash system system.img
sending 'system' (963584 KB)... FAILED (remote: (00000008))
finished. total time: -0.000s
The bootloader loocks relocked ok (as it shows on top of that screen)
But flashing is impossible and, of cause, I don't know why

Adb will work in recovery but only if you boot the recovery from fastboot.
Fastboot boot recovery recovery.img

ok, next approach:
- Booted to fastboot
- unlocked bootloader with the unlock .bin file
- fastboot boot Recoveries\CWM5.8.3.1.img
- adb push rom.zip /sdcard/
- waited 5 minutes until done
- in recovery: Install zip from sdcard
- manual selected the rom.zip (yes, it was actually on the SDcard, so adb did its job)
- got an error that the image was bad:
ClockworkMod Recovery v5.8.3.1
-- Installing: /sdcard/rom.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/rom.zip
I think I will have to get another image, right?
This one was extracted from
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed.exe
I started the program and searched for the rom.zip in my temp folder. Was this ok?

Run .11 RUU, wait until load all completely, now go to %temp% in your pc and find a folder that contain a ROM.ZIP file... Unzip the files and flash the boot_signed.img and the recovery_signed.img, then relock your phone fastboot oem lock) do a factory reset (with the new recovery) and then try to run the .11 RUU.
THAT SHOULD WORK
pd: sorry for my poor english.
Sent from my HTC One X using XDA

Bright.Light said:
ok, next approach:
- Booted to fastboot
- unlocked bootloader with the unlock .bin file
- fastboot boot Recoveries\CWM5.8.3.1.img
- adb push rom.zip /sdcard/
- waited 5 minutes until done
- in recovery: Install zip from sdcard
- manual selected the rom.zip (yes, it was actually on the SDcard, so adb did its job)
- got an error that the image was bad:
ClockworkMod Recovery v5.8.3.1
-- Installing: /sdcard/rom.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/rom.zip
I think I will have to get another image, right?
This one was extracted from
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed.exe
I started the program and searched for the rom.zip in my temp folder. Was this ok?
Click to expand...
Click to collapse
You haven't a clue have you?
You don't flash an RUU from CWM, it's a Windows application!
1. Boot phone into FASTBOOT
2. Connect to the PC
3. Lock the bootloader
4. Run the RUU
Job done

@wolfraim: Yes, the factory reset was the one culprit, it seems!
EddyOS: Tried that so many times, but finally wolfraim added a crucial point: Factory reset!
Now the RUU install from the PC is working... (Have to wait for some time ...)
* I have to go for now, right after the flash is done.
When I've got the time, I will try to make some more notes and maybe another step-by-step story on how to make the device work again.
Thank you very much for your patience and help!
This is why I love the xda-developers site so much!
(and all possible ways included on XDA to brick my device is the reason why I hate xda sometimes... )
edit: Flashing has succeeded! Software number: 1.29.401.11, so it seems I also have the latest ROM update now.
I'll make a recovery backup asap and will try the titanium backup too.
Oh, this one is SU-locked of cause, so I will have to install the SU zip file again... Much work is to be done yet. Maybe I should look for a good ROM in the Android development area.

[Q] Trouble downgrading for root.

Hi, total newbie here.
I have a HTC HD Desire
Android 2.3.5
I started the process of Rooting using aahk -11092012
I was instructed I needed to downgrade.
After "Flash the downgrade RUU? [y/n]" I typed y>enter
I got this:
Quote:
pushing rom to sdcard - this takes time please be patient.
protocol failure
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
Starting stock recovery the first time to init....
Steps:
1. When you see the ugly red triangle, push/hold vol-UP and then push power to
start stock recovery.
2. When you get to the blue stock recovery menu, choose reboot and push power.
The SDcard is new and I formatted it.
Click to expand...
Click to collapse
Then I tried another SD card and seemed to get some response going through the same process.
However, all I got on three occasions going through the same process (after using another sdcard and factory reset in phone) was this 30 mins on each occasion until I unplugged the usb:
pushing rom to sdcard - this takes time please be patient
Click to expand...
Click to collapse
appeared.
Then I got the protocol error not found message again.
But I could still use the phone.
I didn't realise this could be so frustrating.
Any help would be appreciated.
Thanks

cake100 said:
Hi, total newbie here.
I have a HTC HD Desire
Android 2.3.5
I started the process of Rooting using aahk -11092012
I was instructed I needed to downgrade.
After "Flash the downgrade RUU? [y/n]" I typed y>enter
I got this:
Then I tried another SD card and seemed to get some response going through the same process.
However, all I got on three occasions going through the same process (after using another sdcard and factory reset in phone) was this 30 mins on each occasion until I unplugged the usb:
appeared.
Then I got the protocol error not found message again.
But I could still use the phone.
I didn't realise this could be so frustrating.
Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
Have you installed drivers with the phone unplugged? did you check connectivity before starting?

glevitan said:
Have you installed drivers with the phone unplugged? did you check connectivity before starting?
Click to expand...
Click to collapse
Yes, installed, uninstalled and reinstalled after each time it failed.
Connectivity, as in the phone is connected to the computer?
Well it was on and connected to the computer in charge mode. Although, you could not see it was connected to the PC from the PC. But the USB sounds were coming from the PC when I plugged and unplugged.
Here is the text:
Ace Advanced Hack Kit [Linux/OSX/Windows] attn1 2011/2012
___________________________
MAIN MENU | |
| Only ONE Menu Step to: |
1 - Hack Ace <----------------------------+ * S-OFF |
| * SIM Unlock |
2 - DONATE (Encouraged, but optional) | * SuperCID |
**********************************************************************
o - Options Menu (Return to Stock, Flash radios, etc)
**********************************************************************
t - Toggle Flash Method - current method is fastbootRUU
*********************************************************************
q - Quit
[Select and press Enter]1
ro.product.version=3.16.921.3
This version of Android cannot use the hack kit at this time.
You can downgrade if you like, then rerun the hack step.
WARNING: THIS WILL WIPE DATA
[Would you like to downgrade? y/n]y
a67daa6baa7ef085307593fef6329d14 *PD98IMG/PD98IMG-GB2.zip
Flash the downgrade RUU? [y,n]y
pushing rom to sdcard - this takes time please be patient.
protocol failure
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
Starting stock recovery the first time to init....
Steps:
1. When you see the ugly red triangle, push/hold vol-UP and then push power to
start stock recovery.
2. When you get to the blue stock recovery menu, choose reboot and push power.
/data/local/tmp/tacoroot: not found
Starting stock recovery for the last time....
Steps:
1. When you see the ugly red triangle, push/hold vol-UP and then push power to
start stock recovery.
2. When you get to the blue stock recovery menu, choose reboot and push power.
/data/local/tmp/tacoroot: not found
allowing time for the rom to settle.....
'golcard:' is not recognized as an internal or external command,
operable program or batch file.
Creating goldcard....
/data/local/tmp/goldcard: not found
/data/local/tmp/goldcard.img: cannot open for read: No such file or directory
setting mainver lower for downgrade...
/data/local/tmp/misc_version: not found
rm failed for /data/local.prop, No such file or directory
starting downgrade...
** The phone will now reboot into HBOOT.
** It will then check the file just sent.
** If everything is okay, the phone will
** prompt you to continue by pressing
** VOLUME UP. It will reboot, flashing twice.
**** PUSH POWER WHEN THIS STEP COMPLETES ****
If downgrade is successful, you may set up the phone and try to hack it again.
Once the downgrade is successful, press a key to return to the menu......
Otherwise, cut and paste the output to the screen into a text file for evaluatio
n.... then press a key.
Press any key to continue . . .
Click to expand...
Click to collapse
Cheers

cake100 said:
Yes, installed, uninstalled and reinstalled after each time it failed.
Connectivity, as in the phone is connected to the computer?
Well it was on and connected to the computer in charge mode. Although, you could not see it was connected to the PC from the PC. But the USB sounds were coming from the PC when I plugged and unplugged.
Here is the text:
Cheers
Click to expand...
Click to collapse
That is because your download seems to be flaw. No tacoroot is found in your Hack Kit. Have you downloaded the Hack Kit with the antivirus disabled?

glevitan said:
That is because your download seems to be flaw. No tacoroot is found in your Hack Kit. Have you downloaded the Hack Kit with the antivirus disabled?
Click to expand...
Click to collapse
No, I didn't.
I will have to revisit this in a couple of weeks. I am going away. I will try that next time and report back.
Thanks a lot.

cake100 said:
No, I didn't.
I will have to revisit this in a couple of weeks. I am going away. I will try that next time and report back.
Thanks a lot.
Click to expand...
Click to collapse
No problem. Just make sure you re download the kit again with the antivirus disabled.

boot loop for no reason, unmodified phone

Hello,
I am no expert but i usually fix problems, however this one keeps puzzling me for a long time now.
I own a wildfire, not modded, not modified in any way. One day I open a qr code app, it decides to freeze, so i reboot. (i think i had to remove the battery) It takes about 15min to boot, doesn't respond to any input and then reboots and the cycle continues.
I have looked into several solutions for the problem, but all require me to turn S-off. But to do that I need to turn on usb-debug, but to do that I need a bootable image!!!!
At first i wanted to mod, tried revolutionary to turn off S, but doesn't work because i can't turn on usb-debug.
Then i wanted to turn off S the HTC way, where they send me the code needed to unlock it, but it said i had to first update the RUU and guess what:
"To install the RUU, simply follow these instructions: On your phone, enable USB debugging. (..)"
I do not understand what i should choose from the RUU download page, but if it helps i am from Italy. I tried the program and this is the output:
C:\Users\*user*>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
I did all possible options the bootloader gives me: deleted all user data (losing most of my stuff i guess), I tried recovery too but it doesn't like the image. (which i have not touched or modified in any way)
specs:
BUZZ PVT SHIP S-ON
HBOOT - 1 . 01 . 0001
MICROP - 0622
TOUCH PANEL - ATMELC03_16ac
RADIO - 3 . 35 . 20 . 10
Nov 17 2010 , 12:08:53

stormsight said:
Hello,
I am no expert but i usually fix problems, however this one keeps puzzling me for a long time now.
I own a wildfire, not modded, not modified in any way. One day I open a qr code app, it decides to freeze, so i reboot. (i think i had to remove the battery) It takes about 15min to boot, doesn't respond to any input and then reboots and the cycle continues.
I have looked into several solutions for the problem, but all require me to turn S-off. But to do that I need to turn on usb-debug, but to do that I need a bootable image!!!!
At first i wanted to mod, tried revolutionary to turn off S, but doesn't work because i can't turn on usb-debug.
Then i wanted to turn off S the HTC way, where they send me the code needed to unlock it, but it said i had to first update the RUU and guess what:
"To install the RUU, simply follow these instructions: On your phone, enable USB debugging. (..)"
I do not understand what i should choose from the RUU download page, but if it helps i am from Italy. I tried the program and this is the output:
C:\Users\*user*>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
I did all possible options the bootloader gives me: deleted all user data (losing most of my stuff i guess), I tried recovery too but it doesn't like the image. (which i have not touched or modified in any way)
specs:
BUZZ PVT SHIP S-ON
HBOOT - 1 . 01 . 0001
MICROP - 0622
TOUCH PANEL - ATMELC03_16ac
RADIO - 3 . 35 . 20 . 10
Nov 17 2010 , 12:08:53
Click to expand...
Click to collapse
Hmmm. First off, have you tried to factory reset from recovery? If you boot into the recovery and then hold both volume buttons and power a usable menu should appear. Factory reset from there and reboot. See if that helps.
If not we turn our attention to your hboot. The error is because it is not updated enough to have that command. So we have two choices here. You can either upgrade the hboot, unlock your bootloader via htcdev and flash a custom rom. Or you could create a Goldcard, flash a ruu that has the same hboot as the one you have. This should fix your rom and enable the phone to boot again.
In any event you will need to extract the rom.zip from whichever ruu you choose. To do that have a quick google search for a guide but its easy enough. After that rename the rom.zip to PC49img.zip and place it onto your sdcard, boot into hboot and allow it to flash it. The golcard process should be covered in one of my downgrade threads or one of the others from this forum.
Post back here if your having and trouble or need a hand

heavy_metal_man said:
Hmmm. First off, have you tried to factory reset from recovery? If you boot into the recovery and then hold both volume buttons and power a usable menu should appear. Factory reset from there and reboot. See if that helps.
Click to expand...
Click to collapse
Yes, i forgot to mention: i have tried all options in the recovery (red triangle thing) too (clear cache, factory reset) nothing worked, it says: E:Can't open /cache/recovery/command
heavy_metal_man said:
You can upgrade the hboot, unlock your bootloader via htcdev and flash a custom rom.
Click to expand...
Click to collapse
To do this, i would need usb-debug enabled, so I think i cannot, but if there is a way please tell me!
heavy_metal_man said:
Or you could create a Goldcard
Click to expand...
Click to collapse
To do this i will need a micro-sd adapter to put my card into my computer, i will find one and try it out.
I also read that i need the correct RUU for my carrier. I am not understanding very well what i'm doing, also no idea what a RUU is or where to get the appropriate one for my Hboot and carrier, any advice ?

stormsight said:
Yes, i forgot to mention: i have tried all options in the recovery (red triangle thing) too (clear cache, factory reset) nothing worked, it says: E:Can't open /cache/recovery/command
To do this, i would need usb-debug enabled, so I think i cannot, but if there is a way please tell me!
To do this i will need a micro-sd adapter to put my card into my computer, i will find one and try it out.
I also read that i need the correct RUU for my carrier. I am not understanding very well what i'm doing, also no idea what a RUU is or where to get the appropriate one for my Hboot and carrier, any advice ?
Click to expand...
Click to collapse
All usb debugging is for is so that adb can reboot the device to hboot. If you google for how to extract the rom.zip from the ruu and then put it on the sdcard (after renaming it to PC49IMG.zip) and boot to hboot it is the same thing. Just without usb debugging needed.
You will need a micro sdcard adapter pal.

alright, after using the HTC dev method, i unlocked the phone, it still says S-ON but *** UNLOCKED *** on top, the HBOOT is now 1.02.000
after that i obtained the ClockWorkMod recovery img (i used version 5.0.2.0) and did in the terminal:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img

stormsight said:
alright, after using the HTC dev method, i unlocked the phone, it still says S-ON but *** UNLOCKED *** on top, the HBOOT is now 1.02.000
after that i obtained the ClockWorkMod recovery img (i used version 5.0.2.0) and did in the terminal:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
Click to expand...
Click to collapse
good stuff pal.
when you are in clockworkmod recovery the controls are different. use the trackball to scroll and select. power button is now the back button.
I would recommend this custom rom as it is stable and has a stock vibe to it. just follow its install instructions and you should be good to go

Thanks, after many trial and error i ended up asking my hacker friend and managed to install cyanide mod.
However the same problem which i originally had persists ( it is very slow to boot (when it boots) and it doesn't react to any input, at this point it must be a hardware problem. This makes me very sad, i thought i saved it..

stormsight said:
Thanks, after many trial and error i ended up asking my hacker friend and managed to install cyanide mod.
However the same problem which i originally had persists ( it is very slow to boot (when it boots) and it doesn't react to any input, at this point it must be a hardware problem. This makes me very sad, i thought i saved it..
Click to expand...
Click to collapse
That suck man.
Hmmm. Slow boot times are normal on this phone to a certain degree. Usually 20secs to 3 minutes at first boot aftet rom flash.
Once the phone has booted up does the trackball still work? Could just be a damaged digitizer. They are fairly cheap these days. Look here http://m.ebay.co.uk/itm/281644653982 and here http://m.ebay.co.uk/itm/281644653982 fairly straight forward to install, but you could buy a used version of the phone for £30 minimum so its up to you
Edit: although, on reflection 15 boot time and constant reboots are not a good sign. I was hoping it was a software issue. If the trackball is functional you could go into settings, enable usb debugging and then get a logcat. That would at least give us somewhere to work from :-/

the trackball is functional because i can use it in clockwork recovery! but the phone doesn't react to it after boot, it's like it's stuck, i don't think the issue is the touchscreen, it used to work fine, it must be something else.
boot time is about 5-6minutes now, but after that it's like frozen, and after a couple more minutes it reboots. A big improvement, now the bootloop period is at least 70% shorter! xD

stormsight said:
the trackball is functional because i can use it in clockwork recovery! but the phone doesn't react to it after boot, it's like it's stuck, i don't think the issue is the touchscreen, it used to work fine, it must be something else.
boot time is about 5-6minutes now, but after that it's like frozen, and after a couple more minutes it reboots. A big improvement, now the bootloop period is at least 70% shorter! xD
Click to expand...
Click to collapse
Lol! Well at least thats a plus :-/ theres not much else we can do here. We could try to enable usb debugging fron within clockworkmod by editing the build.prop and see if we can get a logcat but if the phones just locking up we might not even get one :-/