Develop Bugs

[HOW-TO] CyanogenMOD on Telstra Defy

Hey everyone,
Just hope to make things a bit easier for all fellow aussies trying to install Cyanogen 7 on there Telstra Defy. Links and attachments at the bottom.
First thing is, so far as i can tell, 2nd-init does not run Clockwork recovery properly from the telstra stock SBF. On this ROM you will probably get the "unable to mount SDcard" error.
Also do NOT install clockwork recovery during any part of this, it comes with
2nd-init and does not need to be installed seperately (can cause problems if you do)
This is the series of steps I took to get it working.
1. Copy Defy-Cyanomod 7 Beta and Google Apps onto SDcard
2. Root phone with SuperOneClick 1.7 (1.8 doesnt seem to work)
3. Install 2nd-init (App is on market or below)
4. Reboot phone twice
5. Use RSD Lite and flash the Official Froyo Korean v3.4.2-74 fixed SBF
(This ROM allows you to downgrade back to the stock Telstra ROM and also
allows you to install CM7 from 2nd-init+custom recovery)
6. Reboot phone (2nd-init will still be installed after this SBF is flashed)
Your phone will now go into a Motorola boot loop. (this is ok)
7. Let the phone cycle through 2 complete loops.
(CM7 seems more stable once I did this)
8. On the third cycle enter 2nd-init (Volume Down when blue light is on)
9. Enter custom recovery from 2nd-init
10. WIPE Data/Cache
11. Install Defy-Cyanogen 7 from SDcard
12. Reboot phone and let CM7 load up
13. Reboot again and enter 2nd-init+custom recovery and install Google
Apps from SDcard
14. Enjoy some CM7 goodness
Thanks to everyone that made these things possible.
Links
Defy-Cyanogen 7
Latest Google Apps
http://forum.xda-developers.com/showthread.php?t=1033654
Korean 3.4-74 Fixed SBF
http://defy-sbf.4shared.com/

I'm running cm7 on my telstra,defy. At this stage no problems, only thing was i had already flashed a non-downgradable sbf. But for warranty purposes i can still go back to telstra by flashing a fixed telegraph Sgt and restoring with stock telegraph nandroid backup.
Sent from my MB525 using XDA App

Can you post a picture of the "About Phone" screen after restoring stock from non-downgradeable??
This is my second defy and Telstra wouldnt replace my first one because i didnt have the stock ROM. They can tell if its correct or not.

That's what I was thinking, my about screen after going back to the fixed sbf is not the telstra one.
Sent from my MB525 using XDA App

I will when I get a chance, don't suppose anyone could post an about screenshot of the stock telstra one.
Sent from my MB525 using XDA App

I suppose it depends on which tech you get at telstra, some will report it, others will just fix it.
I bricked mine while trying to produce a bufer overflow and divide by zero in the locked bootloader. Was getting some results until it bricked

This is what my about screen has after restoring nandroid and flashing fixed Telstra sbf.
System version: Blur_Version.2.26.0.MB525.Telstra.en.AU
Model Number: MB525
Firmware version: 2.1-update1
Baseband version: EPU93ST2_U_03.03.00
Kernel version: 2.6.29
[email protected] #1
BPFlex version: USAJRDNEMARAB1BTEL02A.OR
APFlex version: GAS_ASIA_USAJORDANTELSTRA_P033
Build number: JRNEM_U3_2.26.0
I would be intetested so see what a stock Telstra one says.
For now I've returned to Beta3 CM7. I had basically done the same as you to install, only difference is I used this fixed sbf, 3.4.2_155-002_DEBLUR
Cheers

I'll be changing mine back soon to get some things off my backup.
When i do i'll post up what it has on the "About Phone" screen

Thanks, I think the main one that will be different is the kernel version.
Sent from my MB525 using XDA App

Help...
The rom is perfect, very fast, so far so stable. Only
I noticed 2 bugs so far. 1. The camera's zoom, but that nothing
affects. 2. Skype does not connect here, / does anyone know how to solve
this? Put username and password, starts to connect, it restarts.
Someone managed to solve this problem?
CM7 Beta 4.1
Congratulations Quarx
Thanks

Hey, first of all thanks heaps for making this guide, thanks to you CM7 is finally running on my Defy. I have one problem though and just wanted to see if anyone else did: I can't play youtube on my Defy at all (through the app or m.youtube.com).
Is everyone else having this issue?
*Edit* I've seen a lot of forum posts from mid-last year relating to this, is this issue still unresolved or could this be a bug in the Defy CM7 port?
I've discovered that it will play youtube (both wifi and 3G) but it will only play HQ videos... While inconvenient, I can work with that

Thanks for the how-to+

Dazmonic said:
3. Install 2nd-init (App is on market or below)
Click to expand...
Click to collapse
For the idiots like me out there installing 2nd-init from the market isnt enough you have to run the file aswell by installing it from inside the 2nd-init program itself, i needed to reset my phone after using super one click for 2nd-init to be granted "superuser status" so it would run properly.
Also once you've chosen the cryogen mod file from the bootloader you can then go back to install the google apps file.
After stuffing up the 2nd init program I needed to reflash the origional telstra files, then repeat the guide.
All seems good now, and thanks alot for the guide. I'm sure i would have really botched it up with out it.

Dazmonic said:
I'll be changing mine back soon to get some things off my backup.
When i do i'll post up what it has on the "About Phone" screen
Click to expand...
Click to collapse
Have you changed back yet?
Sent from my MB525 using XDA App

hj all !
can u give me link download room fix sbf of KOREA ? i can't download it on 4share,because it's emty..
thanks bro

Dazmonic said:
5. Use RSD Lite and flash the Official Froyo Korean v3.4.2-74 fixed SBF
(This ROM allows you to downgrade back to the stock Telstra ROM and also
allows you to install CM7 from 2nd-init+custom recovery)
6. Reboot phone (2nd-init will still be installed after this SBF is flashed)
Your phone will now go into a Motorola boot loop. (this is ok)
Click to expand...
Click to collapse
My Defy is in the post and I will try install Cyanogen when I get it, however I would also like to try a blur free Froyo Rom so I was planning on installing the Nordic fixed ROM in step 5. and having a play with it before continuing the process. Is this possible or will I get a bootloop like you mention in step 6? Is the Froyo ROM used in step 5. useable or not?

Dazmonic said:
Korean 3.4-74 Fixed SBF
http://defy-sbf.4shared.com/
Click to expand...
Click to collapse
Has anyone got a copy of this SFB they could upload somewhere? It looks like all 4shared data has been pulled... see the updated 1st post here: http://forum.xda-developers.com/showthread.php?t=966537
I'd love to get a copy of this SFB so I can do these instructions by the book...
Thanks

Is there another SBF we could use besides the korean one? Does it mean if we use another SBF then we won't be able to flash back to the default telstra one?

****, Telstra are actually checking firmware versions before repairing known issues like the earpiece?
I flashed the China Froyo ROM from ages ago. Probably not downgrade-able huh. Does the upgrade to CM7 process change if you're already on Froyo?

Official 2.2, looking for some CM7 goodness
Hi guys,
I found this page to be a godsend, detailing exactly what i want for my device.
problem is now that Tesltra have updated to 2.2 and the links to the Korean fixed file seem to have all been nuked, im not sure what to do, im a super noob (yes i watched the intro video
I have rooted and flashed CM7 on my desire and want it on my Defy!
so if someone could kindly explain what substitutions (if any) are needed or a link to the files required as from what i understand, if you flash to an official 2.2rom larger then 50MB then you cant downgrade to factory ?
TLR Have Telstra Defy with Telstra 2.2 want CM7 - Halp please

[Q] Defy won't update - says it has, and more errors

Whatever I try, using System Recovery/Clockwork Recovery, when I boot up the phone it's still UK 3.4.3-11 Froyo, but now with a red motorola logo (Nordic firmwire I flashed I suppose) .
When wiping in recovery I get these errors: "can't mount /dev/block/mmcblk0p2 (File exists)" and "error mounting /sd-ext/!".
I've create a FAT (should this be FAT32?), Ext2 and Linux Swap partition on my SD Card.
My original aim was to install CM7 from Quarx. Here's what I did:
Stock Defy UK (Other than root)
Used clockwork recovery to wipe and update to CM7
Booted fine (CM7/2.3), tried to then install gapps as an update.zip, then got stuck on boot at "M" screen on every boot
Used RSD lite to flash 3.4.3-11 UK with Blur
Superoneclick etc., tried to install CM7 again, had no effect
Used RSD lite to flash 3.4.2_177 Nordic - comes up with red logo, but hasn't updated to the actual blurless froyo
Tried again to install CM7, had no effect, still have the 2 errors on wiping
I've also found that when using stock recovery, it no longer does anything when I press the bottom right of the screen, it just stays at the green robot screen, I have to remove the battery.
I did get an app2sd error, which was why I partitioned the SD card using Clockwork recovery (bad move?), I then did it on my PC instead with an SD card adapter.
The phone's not bricked, since I've got a working 2.2 rom, however I've no clue what I've done to make it like it is now, and I can't install CM7 using clockwork recovery and the default recovery doesn't work.
I think fixing those errors might do the trick? Any help would be appreciated.

I am also not able to install quarx rom, tried several times it does not boot and I had to reflash the sbf to get the phone working. Btw I do no have sd partition.
What I did was from cloclwork I tried restore, shall it be install from zip. No idea why I cannot get it running. I have nordic 005 at the moment
Sent from my MB525 using XDA App

...maybe you guys should start to read a little more before attempting flashing any ROM...
If you would have done that, maybe you would have noticed that some people warned about some mounting of the SD card problems in some instances (I don't remember the specifics at this time..I beleive had to do with Super1click version used to root)
And most importantly:
that for CM7 installation instructions ask you to use '2ndinit' recovery and NOT CWM.... In fact you should even avoid having CWM recovery installed before starting the process...
I'm a noob too guys, I sometimes appreciate the help I can get from a post here. But I try my best to find existing answers and read as much as I can on the subject first. Obviously, you guys did not do your homework on this one.

[] AL [] said:
...maybe you guys should start to read a little more before attempting flashing any ROM...
If you would have done that, maybe you would have noticed that some people warned about some mounting of the SD card problems in some instances (I don't remember the specifics at this time..I beleive had to do with Super1click version used to root)
And most importantly:
that for CM7 installation instructions ask you to use '2ndinit' recovery and NOT CWM.... In fact you should even avoid having CWM recovery installed before starting the process...
I'm a noob too guys, I sometimes appreciate the help I can get from a post here. But I try my best to find existing answers and read as much as I can on the subject first. Obviously, you guys did not do your homework on this one.
Click to expand...
Click to collapse
I did in fact read around before I started, obviously in the wrong places or not enough. I've been pretty naive but all the guides I saw recommended that recovery, I must have missed the posts about 2ndinit (which sounds a lot easier). In fact I hardly read the actual CM7 thread since it's around 190 pages long.
It's interesting you noted superoneclick as the first time it worked and I used z4root.
I think for now I'll just use what I've got, which is ultimately better than what I started with (2.1), it's just a bit worrying as those errors I'm getting seem to suggest I've messed up the internal storage; and the default recovery won't work.
Probably installing a beta CM7 wasn't the best idea anyway since I'm very new to this.

Thanks al
I tried with cw recovery only. Tonight will try with 2ndinit. my sys info nordic 177_005 will I be able to get beta4 straight installing the zip
Sent from my MB525 using XDA App

Hi al[]
I tried booting into 2nd init boot but nothing comes up. Just blank screen any idea
Sent from my MB525 using XDA App

binodnepal said:
Hi al[]
I tried booting into 2nd init boot but nothing comes up. Just blank screen any idea
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Have you read this one:
http://forum.xda-developers.com/showthread.php?t=1043420
and for the recovery:
http://forum.xda-developers.com/showthread.php?t=1032212
Other than that, I will leave it to others to guide you on this...they'll do a better job than I would.
Sorry if I sound/ed rude in my post above...but was before 1st coffee of the day
Last note: on my side, I'm waiting (more or less) patiently...
As seen here http://forum.xda-developers.com/showthread.php?t=1033654&highlight=CM7
CyanogenMod 7 for Motorola Defy
Status Beta4:
Works:Wifi, SD-Card, 3D, Auto-Brightness, LED, Photo Camera with Flash, Video Camera(H264), GSM/3G, Bluetooth +Headset + HID, Sensors, GPS(have bugs)
Not works: aGPS, FM-radio, 720p & WVGA Recording.
BugList:
- some people say that they have wifi problems <---
- DroidWall/Iptables - not work <--- <--- <---
====>>>> So I will wait for that "tiny detail" [DroidWall/IP Tables] to get fixed before testing out any CM7 on my phone.
I like DroidWall apk and I also like to have a relative control on which app can access the internet...
Some of my apks 'might' not be so 'official' [..let say] and who knows what kind of party they're having in my phone....

I got it working and its quite fast. GPS works for me. Camera photo works but not the video. Will test other later. Quadrant score is very high not sure if it is correct. I got 2200
Sent from my MB525 using XDA App

Anyone having issues with music player stopping after few songs in cm7 beta4
Sent from my MB525 using XDA App

[Q] Boot Loop Problems - US Defy

Hello, all. I am stuck in a boot loop. It occurred when I rebooted after reestablishing 3G as discussed in this thread. I had made a recovery using the Recovery App (from aforementioned thread) before proceeding which created a cache.img, data.img, system.img and .android_secure.img. I have these images in a secure location, but cannot access them via the recovery console. So I tried going through the stock recovery wiping settings and cache and then rebooting as suggested in this thread. I have tried flashing a stock US SBFs from this thread on XDA-Dev and And-Dev (here) using RSDLite versions 4.5.3, and 4.6. I get this output from RSD:
Failed flashing process. Unable to retrieve initialization values from INI file. (0x7023); phone connected
Click to expand...
Click to collapse
My battery is fully charged, but still I cannot flash any of the SBF files. I have tried to not post for as long as possible, because I value your time and work, opting instead to scour the forums. If I have missed something, then I apologize for cluttering up the forum. But if there is anyone out there who can help me safely get out of this boot loop, I would appreciate it so very much. Thank you XDA-Developers, you're my only hope.
John
Conclusion:
Sweet. So my problem was that I was using an older version of RSDLite. As hinted at by farsight73, there was a compatibility issue with my machine and RSDLite 4.5.3 and 4.6. Several threads suggested that I try a later version of RSD to get it to work on my M$ Windows 7 64bit. So I tried v.4.9 (here) and it worked like a charm. It recognized my phone, and following this great guide I was able to flash a stock 2.2.1 sbf that I found linked to on the XDA forums. Thank you so much, farsight73, for encouraging me to look into hardware compatibility. Worked great! I'll be sure to look into your suggestion about 2nd init. Thanks all!

If you had initialled flashed full SBF froyo and wanted back Eclair then it's not possible.
Same goes to full flash Gingerbread which you will not be able to go back lower version AFAIK. But if you're on froyo in this bootloop then I would suggest you start with full wipe un stock recovery and flash the Nordic froyo of 2.2.2. Might need to flash using difference PC if the one you use is persistently giving the above failed flashing process.
If you somehow able to recover back your phone to live. I would suggest you to install 2nd-init so you can quickly recover your phone in case you messed things up again in the future.

Hey, thanks for the response, farsight73. I am in froyo, but 2.2.1. I'm currently trying RSDLite on a friend's XP, hopefully that works, but I will be sure to give your Nordic suggestion a go. I'll post the results when I finish.
I would suggest you to install 2nd-init
Click to expand...
Click to collapse
I don't really know what that is, but I will be sure to look into it so that I can avoid these types of issues in the future. I'm really new at this, so it's really just me hopping around from thread to thread trying to make sense of it all. Thanks again for the suggestions!

I added a conclusion to the OP. Thanks again, farsight73!

was having the same problem with the 3g used defy baseband on cm7 and got my 3g back easily..(hspa 2)

Running nordic and 2nd-init and really digging it. Thx.
Sent from my MB525 using Tapatalk
Edit:
Thanks, kidrobot52. I found and installed the Defy Baseband Switcher v4 from this thread. I picked the bands based on the table on this page. I'll post my results!
Results:
After following the advice of farsight73 in this thread, I was able to get Baseband Switcher v4 (link above) working for my provider and area. Thanks for the heads up on the tool, kidrobot52!

Glad I can be that helpful to you. 2nd-init is another advance custom boot menu with on board custom recovery. It triggered while the phone is in booting sequence, thus, you could always enter to custom recovery to restore your backup rom if anything goes wrong wirh your modding.
Press -vol when you see blue light while the phone is booting. In the boot menu is more of self explanatory.
Always make a backup if you're attempting to edit or modding which effecting system files.
Sent from my awesome Moto Defy: Stock Rooted Gingerbread 2.3.3 - XDA Premium

Boot Loops, forever.

So, I don't really post on forums because I'm pretty tech-savvy, but I have a big problem that I can't fix, and I can usually fix everything (thanks to you guys!)
This morning, my incredible acted up as I was checking an e-mail and it froze, so I decided to battery pull because restarting my phone didn't work. (Note, my incredible has been running VERY solidly on a CM7.1 nightly). As I tried to boot up the phone again, it would stay on the white HTC Incredible screen. When I rebooted into recovery thru HBOOT, i realized that there was an error mounting something, like recovery_log, or something like that (i didn't mind this because I thought I knew what I was doing), but I tried restoring my old nandroid backup that was working well, but it didn't work. It said it couldn't format /data or something... It ended up staying on the white HTC incredible screen. So, I wiped data/cache like 10 times, and dalvik cache as well and tried re-flashing a clean install of cm7.1 stable, but didn't work again - led me straight to the white Incredible screen. So, installing a fresh rom AND restoring a solid backup didn't work... so...
I found the RUU 2.3 stock rom on the development forums, and tried to install that like I do with the radios (PB31IMG.zip) through HBOOT, but no cigar. It did go PASSED the white screen, but boot loops at the Droid eye.
So, I thought I'd find a different stock img, and found the 2.2 official OTA .zip and installed it the same way, but got the exact same result (boot loops, forever).
Any suggestions? I can't think of anything else.... I feel like my phone is bricked, but I didn't do anything to make that happen.
I feel like something happened that made me not able to format the /data, and stuff. I even formatted my SDcard in case it was the problem.
Any help is appreciated. Thanks!

Load the RUU onto a different fat32 sd card and see if you are able to boot.
Sent from my ADR6300 using XDA Premium App

i'll try that and give an update. thanks for the reply!
*update* no luck. same thing happens. i tried on three different sdcards formatted fat32...

Can you factory reset and flash a ROM from a different sd than the one you were using? Description sounds like bad sd, and AOSP roms interact with the sd on boot. If original (CM 7) sd is toast, it'll never boot, hence different sd card and prefably RUU
Sent from my ADR6300 using XDA Premium App

I had this happen once where no matter what rom i flashed all i got was bootloops. I had to get the stock froyo ruu.exe that you run from your pc and install it that way. Then once installed boot up and go to settings/sd & phone storage and do a factory reset from there. This factory reset is a true reset as it wipes out vzw programing also. After reset folow on screen steps to reactivate your phone, you can skip the rest of the setup. Once thats done your good to go just flash clockwork or amon ra recovery and then flash what ever rom you want. No guarantees but it worked for me.
NOTE: This assumes you are s-off, if your not after flashing the ruu you will have to use unrevoked to regain root and s-off again.

You can also try wiping /system and /boot.

*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.

sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
if you are non root. you will need to download the RUU.exe for 2.2 and install if from you pc.
http://androidforums.com/htc-droid-...mplest-instructions-ever-windows-xp-only.html
follow that and your phone will be back to the day you got it out of the box.

All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.

SlimSnoopOS said:
All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.
Click to expand...
Click to collapse
RUU = ROM Update Utility

no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.

sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Then its gotta be a hardware failure.
Sent from my sexy assistant. (AMOLED HTC Incredible)

wow... what a bummer. thanks for the help anyway, it's much appreciated.

sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Does it give any specific error code when it says it can't connect to the phone?
Someone correct me if I'm wrong but don't you have to have HTC sync installed on your pc to use an ruu.exe? Do you have that installed?
Sent from my ADR6300 using xda premium

I'll try it again to verify the code, I'm pretty sure it was "170"

sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
I had this issue the first time i rooted my phone and attempted to put on a ROM, and i resolved it when i found this post to get back to stock. I also used this to fix a problem where my phone had a black screen with a line through it on booting to recovery or attempting to do a nandroid back up:
droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html
All i did was basically use the PB31IMG Method without turning s=on, ( i had stock radio and still have 7.28 )
1) download that PB31IMG.zip and drop it on the root of your sd card ( it has to be named ( PB31IMG.zip ) so make use you have file extensions showing on your PC.
2) boot to hboot and and let see the file and install it
3) used unrevoked ( remove sd card ) to aquire root again.
idk if this helps, but this seems to get me out of the few weird situations i had

sl4m said:
I'll try it again to verify the code, I'm pretty sure it was "170"
Click to expand...
Click to collapse
Check this out to fix your 170 error.
http://androidforums.com/incredible...170-171-solution-windows-7-a.html#post1472468

This low key happened to me and I booted in to HBOOT and went to clear storage and it did its thing and booted up, from there I had to activate it then I was set!
Sent from my ADR6300 using XDA App

=D
Sent from sweet snacks off tapatalk.

[Q] Newbie struggling to update from 2.2.1

Hello,
I've only just got this HTC Wildfire but nearly all apps say they are not compatible, so I thought I would try to update, but seem to be hitting problems:
Android version: 2.2.1
HBOOT-1.01.001
Boot menu: HBOOT BUZZ PVT SHIP S-OFF
Initially tried the links to unrevoked but the downloads always seem to time out
Now I tried the [Full Guide] All in one...
I've managed to install the HTCSync drivers OK
I've updated the Android 1.0 driver from the all-in-one package, but when I'm in the boot menu, my Windows XP machine give an error message
- something about a device problem, to try again and if it fails to replace the device. On a different USB port the device driver reports that it failed to start.
Anyway, I ran revolutionary from the all-in-one package but, not surprisingly, it got stuck - it was waiting for fastboot - which is reasonable if the device isn't being recognised.
So, what can anyone suggest?
- If HBOOT already reports S-OFF, can I skip this and still install a newer ROM? If so, how - if I don't have the revolutionary S-OFF?
- Should I give up with Windows and try Linux?
There is a good chance, I suppose , that I have missed something fairly obvious - applogies if that is the case.
I look forward nto any suggestions you may have.
Cheers

dusty_bin said:
Hello,
I've only just got this HTC Wildfire but nearly all apps say they are not compatible, so I thought I would try to update, but seem to be hitting problems:
Android version: 2.2.1
HBOOT-1.01.001
Boot menu: HBOOT BUZZ PVT SHIP S-OFF
Initially tried the links to unrevoked but the downloads always seem to time out
Now I tried the [Full Guide] All in one...
I've managed to install the HTCSync drivers OK
I've updated the Android 1.0 driver from the all-in-one package, but when I'm in the boot menu, my Windows XP machine give an error message
- something about a device problem, to try again and if it fails to replace the device. On a different USB port the device driver reports that it failed to start.
Anyway, I ran revolutionary from the all-in-one package but, not surprisingly, it got stuck - it was waiting for fastboot - which is reasonable if the device isn't being recognised.
So, what can anyone suggest?
- If HBOOT already reports S-OFF, can I skip this and still install a newer ROM? If so, how - if I don't have the revolutionary S-OFF?
- Should I give up with Windows and try Linux?
There is a good chance, I suppose , that I have missed something fairly obvious - applogies if that is the case.
I look forward nto any suggestions you may have.
Cheers
Click to expand...
Click to collapse
Hey pal
take the attached file and rename it to pc49img.zip and put it onto your sdcard. boot the phone into hboot with the sdcard in and the hboot should ask you to update, select yes.
this will add a custom recovery to your device. once this has completed remove the file from your sdcard via computer and then move back to the phone. reboot into hboot and select recovery using the volume rocker and hit power to enter it,
now your ready to go as far as flashing a custom rom is concerned. i would strongly advise making a nandroid backup as this is your main way to restore your phone if issues occur.
the controls for clockworkmod recovery are different from hboot, the can be found in one of my how too threads if you get lost. most of the roms in the dev section have instructions in thier OP for flashing them so just browse around and remember the limitations of this phone, updates wont make it epic but if you use cm7 or higher you should get market apps again.
Good luck and enjoy browsing our corner of the forum

heavy_metal_man said:
Hey pal
[...]
the controls for clockworkmod recovery are different from hboot, the can be found in one of my how too threads if you get lost. most of the roms in the dev section have instructions in thier OP for flashing them so just browse around and remember the limitations of this phone, updates wont make it epic but if you use cm7 or higher you should get market apps again.
Good luck and enjoy browsing our corner of the forum
Click to expand...
Click to collapse
Hi and thanks.
Before I saw your message I had managed to get through the revolutionary issue by using the secon USB port and removing and reinserting the USB plug each time it got stuck. Now I think of it, I has also reinstalled the drivers using the HTCdriver.exe file before that but still had the same issues as before.
Anyway it didn't seem to change anything except that Revolutionary message at the top of the HBOOT screen.
Now I have flashed the image file you possed and I can get into the CWM-based Recovery v5.0.2.8 menu screen. I got stuck at that point but went to you FAQ post to reconfirm that the power button should select the menu item, but it doesn't. Well, it just flips between the menu sceen (with the orange circular arrow behind) and the hat with the circular arrow - but nothing happens.
So I'm back to scratching my head...
Anyway, thanks again - I've managed to get a bit further and would be interested in any further thoughts you may have

dusty_bin said:
Hi and thanks.
Before I saw your message I had managed to get through the revolutionary issue by using the secon USB port and removing and reinserting the USB plug each time it got stuck. Now I think of it, I has also reinstalled the drivers using the HTCdriver.exe file before that but still had the same issues as before.
Anyway it didn't seem to change anything except that Revolutionary message at the top of the HBOOT screen.
Now I have flashed the image file you possed and I can get into the CWM-based Recovery v5.0.2.8 menu screen. I got stuck at that point but went to you FAQ post to reconfirm that the power button should select the menu item, but it doesn't. Well, it just flips between the menu sceen (with the orange circular arrow behind) and the hat with the circular arrow - but nothing happens.
So I'm back to scratching my head...
Anyway, thanks again - I've managed to get a bit further and would be interested in any further thoughts you may have
Click to expand...
Click to collapse
When in clockworkmod recovery you need to press the trackball button to select instead of using power
Sent from my Desire S using Tapatalk

heavy_metal_man said:
When in clockworkmod recovery you need to press the trackball button to select instead of using power
Click to expand...
Click to collapse
Oops - that's rather embarrassing.
I thought I had read power button or trackball and, although I had seen trackball mentioned before, I had never knowingly used it and certainly hadn't realised where it was or that there was a button function associated with it
Next, I'll check out your nandroid backup app recommendation, although I don't really have much on this phone yet. I did a backup from CWM already.
In the set of files I have downloaded while reading various threads , I have cm-7.2.0-buzz.zip and cm-7-20130301-NIGHTLY-buzz.zip. I suppose either of these should be fine, or do you have some other recommendation?
Thanks - I appreciate your patience...

dusty_bin said:
Next, I'll check out your nandroid backup app recommendation, although I don't really have much on this phone yet. I did a backup from CWM already.
In the set of files I have downloaded while reading various threads , I have cm-7.2.0-buzz.zip and cm-7-20130301-NIGHTLY-buzz.zip. I suppose either of these should be fine, or do you have some other recommendation?
Thanks - I appreciate your patience...
Click to expand...
Click to collapse
Its all good pal the back up you made from recovery Is a nandroid back up (from a fusion of the words nand and android I believe. Nand being the memory type used in older android phones) I would recommend any cm7 7.2.x roms as they are very stable usually. Remember that you will also need flash gapps (Google apps) for cm7 which can normally be found in the roms description.
Sent from my Desire S using Tapatalk

heavy_metal_man said:
Its all good pal the back up you made from recovery Is a nandroid back up (from a fusion of the words nand and android I believe. Nand being the memory type used in older android phones) I would recommend any cm7 7.2.x roms as they are very stable usually. Remember that you will also need flash gapps (Google apps) for cm7 which can normally be found in the roms description.
Click to expand...
Click to collapse
Cheers -I installed the cm 7.2.0 file and gapps - and everything went fine this time :victory:
It looks like the next challenges wil be to avoid running out of memory - the phone memory is already down to 20 MB even though I've moved all the apps I can to the SD card. Working out where everything is in new settings menu can be quite interesting too
One final question: if I want to install the later version of cm7 (or an even higher version), can I just use 'upgrade from SD card' from the CWM menu item, to avoid having to reinstall everything?
Thanks again!

Yes and no. if your upgrading to a later version of cm7, IE 7.2.3 or 7.3 you could flash it over your rom with minimal issues but if your changing android version dramatically like from gingerbread to Ice cream sandwich or jelly bean then a full wipe is recommended along with nandroid backup before flashing or wiping anything