Develop Bugs

[Q] Rom Manager and CWM

Hi, I have my phone unlocked via htcdev. I installed CWM by alquez, but it doesn't detect it in ROM Manager. I have tried going into recovery from rom manager, then rebooting from cwm, still nothing works. Only rebbot to recovery works in rom manager. Any solutions?

The CWM from Alquez is unofficial not supported by rom manager dev i think. The same thing was with samsung galaxy ace , don't flash recovery from manager you can get brick...

drummer1839 said:
The CWM from Alquez is unofficial not supported by rom manager dev i think. The same thing was with samsung galaxy ace , don't flash recovery from manager you can get brick...
Click to expand...
Click to collapse
I won't flash it that way, but then how do i flash the cm7 without rom manager?

SomeDudeOnTheNet said:
I won't flash it that way, but then how do i flash the cm7 without rom manager?
Click to expand...
Click to collapse
1/ Download and put the CM7.2 nightly zip from Alquez on your SD card root.
2/ Go into CWM Recovery
3/ Wipe Data/Factory reset
4/ Wipe Dalvik
5/ Format System from Mounts
6/ Install Zip from SD and choose CM72 Nightly ZIP
7/ Install Zip from SD and choose CM7x GAPPS
8/ When done reboot to your clean CM7.2 install

So, for now, we can delete Rom Manager then?
Sent via CyanogenMod 7.2

yop. its useless for now.

d33ps1x said:
1/ Download and put the CM7.2 nightly zip from Alquez on your SD card root.
2/ Go into CWM Recovery
3/ Wipe Data/Factory reset
4/ Wipe Dalvik
5/ Format System from Mounts
6/ Install Zip from SD and choose CM72 Nightly ZIP
7/ Install Zip from SD and choose CM7x GAPPS
8/ When done reboot to your clean CM7.2 install
Click to expand...
Click to collapse
Awesome. Thanks a lot.

okay, I just installed cm7.2, android market wasn't there. I installed an apk. it doesn't let me create a Google account, takes me to some exchange account. please help. and why does cm7 use adwlauncher? I thought it was something like sense quick help needed.
Sent from my HTC Wildfire S using the XDA mobile application powered by Tapatalk

It's non sense ROM.
I didn't like it too, so I just flashed sense rom.
Anyway, you can install any launcher you like, and use it as default one.
About google account.
That ROM doesn't have anything to do with google's apps, so you'll have to install gapps.
Find it somewhere, latest version is from 28.8.2011 I think.
It's .zip file, just flash it through recovery.
Sent from my HTC Wildfire S A510e using XDA App

It's non sense ROM.
I didn't like it too, so I just flashed sense rom.
Anyway, you can install any launcher you like, and use it as default one.
About google account.
That ROM doesn't have anything to do with google's apps, so you'll have to install gapps.
Find it somewhere, latest version is from 28.8.2011 I think.
It's .zip file, just flash it through recovery.
Sent from my HTC Wildfire S A510e using XDA App
Click to expand...
Click to collapse
Thanks, I found the file on cyanogen wiki, flashing now.

SomeDudeOnTheNet said:
Thanks, I found the file on cyanogen wiki, flashing now.
Click to expand...
Click to collapse
It was in the instructions.

I like non sense roms.Too bad WS is not officially supported by CM.
But maybe now, when most of us have the opportunity to install custom rom, we get full support.
Sent via Wildfire S using CyanogenMod

New tutorial
Here is a new tutorial on something a couple of us have been using for a while...

No.12 said:
I like non sense roms.Too bad WS is not officially supported by CM.
But maybe now, when most of us have the opportunity to install custom rom, we get full support.
Sent via Wildfire S using CyanogenMod
Click to expand...
Click to collapse
Me too, they're so ''nonsense'' lol
Sent from HTC Wildfire S powered by CM7.2

Can anybody help with CWM7 ?
I've tried to load this onto my phone but I keep failing. The app does not load. I cannot access any recovery, albeit standard or CWM. Everytime I try from the the bootloader screen and enter recovery, The phone gives me a Black Screen with a Picture and a Red Triangle in the middle and nothing else happens. I then have to reboot the phone.
Am I doing something wrong or am I missing something.
Is there a step by step guide to help make this work for me.
I have searched for a couple of days now and I cannot find anything that for me.
My phone is S-ON and Bootloader Unlocked via HTC-Devs.
Any help from you experts out there will be appreciated, even if it's just pointing me in the right direction.
Thanks in advance.

SomeDudeOnTheNet said:
okay, I just installed cm7.2, android market wasn't there. I installed an apk. it doesn't let me create a Google account, takes me to some exchange account. please help. and why does cm7 use adwlauncher? I thought it was something like sense quick help needed.
Sent from my HTC Wildfire S using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
You can download google apps package from rom manager which comes pre installed in the cm7 update.

HTC G2 White Screen with Andromadus ROM 1.1.2

Hi All, let me start with a warning…
total Android n00b here, doing his first ROM flash on a newly rooted T-Mobile G2. I’ve read and searched a bit in the forum threads to see if I could solve this on my own, but I do need help.
VISION PVT SHIP S-OFF
HBOOT - 0.82.0000 (PC1010000)
MICROP - 0425
RADIO - 26.02.01.15_M2
eMMC - boot
Aug 20 2010, 16:51:01
This is from using the instructions in Strawmetal’s PDF guide to Downgrading from Gingerbread to Froyo and Root. I am working with a G2 phone that was set to Factory Reset before rooting, so there is no user data to backup or worry about.
1. I downloaded the Andromadus Mimicry 1.1.2 ROM image, and verified the md5 checksum on my sdcard using the AFV Legacy application. The Gapps image also was verified as well.
2. Using ROM Manager 5.0.0.8 from the Google Market, I ran Clockwork Recovery to install the Andromadus image. I left all settings on defaults and the installer ran fine.
3. When it restarted, I was left stuck at the white HTC screen for ages… the longest I left it was 20 mins. After that, I pulled the battery and restarted. Same white HTC screen.
4. I tried using Volume (+) key and Power On to get back to Clockwork Recovery, but the phone vibrated (buzzed) 3x times quickly, and the Power LED lamp pulsed an amber color. Again, yank battery, restart, same white HTC screen.
5. finally I decided to read more of the help for adb, and found the command “adb reboot-bootloader”. This let me get into the default Recovery mode, and it proceeded to find the PC10IMG.zip I still had on the sdcard from doing the Froyo downgrade. Recovery checked it out, ran it and restored the stock Froyo image and my phone did a proper restart. WHEW.
After that, I had to run adb to install the hboot recovery image file, and the busybox checksums were valid according to Strawmetal’s PDF instructions to get permanent root back after restoring the stock Froyo image.
I have done this process about 4 times, and am really good at typing inside adb now
But I’m lost…
-did I pick a ROM that doesn’t work with the G2? Other posters to the forum thread appear to be using the HTC Vision or G2.
-is ROM Manager not a good way to install a ROM?
-when I tried to get back into Recovery, what do the 3x buzzes/amber power LED mean?
-I never got to install the Gapps image; was I supposed to install that first, then the ROM image?
I imagine I did something wrong (duh!), but I can’t spot it. If someone can help me through this, I’d appreciate some advice very much.
thanks!

Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).

Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium

Hi Nospin,
Thank you very much for your suggestions!
I will revise my root and remove Clockwork, and switch to 4EXT instead.
I appreciate the idea of "superwipe"; I will look for that as well today.
If I understand everything right...
-replace CWM with 4EXT
-place superwipe.zip, Gapps.zip and the Mimicry ROM.zip on the top level of the sdcard first.
-reboot the phone and run 4EXT recovery
-select superwipe to run first, then the ROM and then Gapps
-then restart the phone
When I used CWM before to install the ROM, it rebooted on its own before I could install Gapps. Will 4EXT let me do each install right after each other or do I have to return to 4EXT for each separate install?
regards,
motionmonk
Nospin said:
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Click to expand...
Click to collapse

Hi blk_jack,
I went back to the Mimicry page and re-read the FAQ section.
I think what I got out of it the first time was that if the ROM flash failed, it could be a corrupt ROM image. I will definitely use 4EXT to repartition before I try again with a ROM flash.
I guess I am still getting used to the terms for everything; can 4EXT do the nandroid backup? or is there a better process for setting that up?
thank you!
motionmonk
blk_jack said:
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse

Yes, you should be able to flash the rom and then GApps without rebooting. Give me a few and I will send you a PM with a few links....

Shot you a PM.

Thanks! I'll check it out :good:
Nospin said:
Shot you a PM.
Click to expand...
Click to collapse

Update-not working
Ok...
I re-flashed back to stock Froyo, and did a permanent root.
Installed 4ext Recovery (instead of Clockwork), and got a copy of SuperwipeG2+ext4;
I copied new checksum'd copies of Mimicry 1.1.2 ROM and GApps to my sdcard.
Booted into 4ext Recovery and installed from .zip the SuperwipeG2+ext4 file.
System, data and cache are all converted to ext4 partitions.
Wiped the system and data and cache partitions.
Installed from inside Recovery the Mimicry ROM and then the GApps archives.
No errors reported.
Upon reboot, I still get the white HTC screen. UGH.
I've left it on in that state for 30 mins... I had to yank the battery after that in shame...
I have tried to make sure that I read up on background steps, and I feel I do understand the overall process, but something is still getting in the way. I am doing this as I mentioned in an earlier post on a factory reset G2 with a clean erased SD card (has the stock Froyo image, Andromadus Mimicry ROM and GApps only). There is no SIM card installed either, wifi is off (to avoid OTA upgrade requests).
Are there other things I can try, or info I can supply that would help? I think I'm so close to getting this done... I must be overlooking something obvious.

I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium

Hi amogil,
Just to be sure I understand, are you saying you are swapping between Andromadus and CM9 beta on your phone?
Did you flash CM9 first? and then Andromadus?
or just carrying the CM9 beta image and running Andromadus?
Sorry, I'm all sorts of confused here lol
thanks
amogil said:
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse

Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....

It's definitely a thought, and I believe that's what amogil is telling me too...
Ya, I can try a different ROM and report back.
I guess I should go back to stock Froyo and then start from CM7.2, and if that boots, try Mimicry again?
-from the Andromadus FAQ, it says it if a different ROM is based on ICS9, you shouldn't have to wipe. But with CM7, I'd have to wipe the Dalvik cache, yes?
-since CM7 is obviously not based on ICS9, would being able to launch into that show some details I can't see at present? Just was curious.
Or, do you think it better to go stock Froyo and then the older Mimicry ROM?
Either way, I'll make sure that I use the Superwipe to set things to ext4 first.
thanks guys for the ideas,
motionmonk
Nospin said:
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
Click to expand...
Click to collapse

The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium

SUCCESS!
Woohoo!
It works!
Since I had an ICS9 ROM already in place and was planning to wipe back to stock anyways, I tried flashing the older Andromadus 1.1.0 ROM.
What a surprise and treat to see the startup animation!
After poking around for an hour inside it, I then tried Recovery to reflash to the newest 1.1.2 ROM.
YAY! It works!
OMG, having a new ROM is like having a new phone-- there are so many improvements to the UI and it's quick and speedy versus GB. Dang, I'm happy now :victory:
Observations:
1. I did notice that inside Recovery, my touchscreen was barely functional when I tried to update from 1.1.0 up to 1.1.2-- I had to use the Volume +/- and the d-pad button to make selections. After the flash, the touchscreen is as responsive as ever.
2. it's got me thinking, that there must be a setting that is expected in the v1.1.2 ROM that the v1.1.0 ROM installed. Or could something else be the issue? I mean absolutely no disrespect to the developers... but on the technical side, I'm just curious what possibilities exist that might lead to this situation.
3. backup question... when I use MyBackup Pro, I know I can make an archive of the apps I've installed, and an archive of the data (documents, music, settings). Is a nandroid backup different from that? when I see the backup/restore options inside of 4ext Recovery, what are those doing that's different from what I get from MyBackup Pro?
thanks for all the help and encouragement. I have a new ROM installed! :good:

strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Oooh, a possibility. We will see if he can boot a different rom.
Whenever you switch roms (even if they are using the same Android version as a base) I suggest a full wipe. (Wipe all user data + Dalvik Cache + Cache, or just flash the superwipe zip). When upgrading the rom you are currently on (say upgrading CM Nightlies or going from Mimicry 1.1.1 to 1.1.2) you only need to really wipe cache and dalvik cache. Unless the dev states otherwise of course.

Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse

Thank You All!
A big shout out to:
Nospin
blk_jack
amogil
strawmetal
for taking the time out to help a total n00b stumble through his first ROM flash.
I really appreciate the points you guys made, and the help provided.
Thank you!
I hope that one day I can help someone else out with a problem and pass the kindness forward.
Yay! I have a working ROM!
motionmonk

motionmonk said:
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
Click to expand...
Click to collapse
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.

WOW. i just realized there is SO MUCH I need to catch up on!
I'll have to look up some of these guides later today... but the RUU is the ROM upgrade, right?
Did you ever find a reason why you got the false S-OFF flag? It's clear that the way I was looking at the failed fre3vo exploit as proof of S-OFF isn't always going to be true... but how would you separate a false S-OFF flag from lets say a wrong hboot image?
BTW, your PDF on downgrading and rooting the G2 was a godsend. Very very helpful and clear.
One of the reasons why I took so long to try rooting was that I was confused by the different methods and the replies of X not working, Y is a better way... going through your guide and the info here on xda cleared alot of things up. :good:
strawmetal said:
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
Click to expand...
Click to collapse

[Q] Recovery and Rom Install Problems

Help, I will describe the following and any help I would love. I have the PRIMOC VM usa HTC ONE V.
Using Hasoon2000's All in one toolkit I have successfully Unlocked my phone, flashed TWRP recover 2.4.4, got root, and made a backup.
I then continue on to wipe cache and system and Factory reset to prepare to install ANY ROM. When I try to install the rom every time it just says Error in /sdcard/...[wherever rom is] (Status 1) FAILED
So then I proceed to restore my backup (this is why you always make a backup) and that works fine
Does the "(Status 1)" mean anything important?
I thought this was happening because I was running the newer radio so I used the RUU tool and now am using the good radio (not 0928) But this did not fix anything. This same thing happens over again. I have checked to make sure and I do have full root privileges.
I then tried to flash boot.img first and jmz kernel flashed successfully, but no rom will flash.
Why will NO ROM install?
I feel like I am missing something obvious but can't figure it out.
Also, whenever I do the factory restore it goes through all the process then fails when trying to wipe sd:ext , but my card is not partitioned. <I didn't know if that would be any help>
I am not a complete newb at all of this (running lg optimus for years- just new to the htc methods)

NEED Help please...
Can anyone help me out with this?
I have not made any progress since yesterday. I am successful at flashing kernels, I have flashed the boot.img of the sic kernel, but on both kernels I have no WiFi with the stock ROM.
So I either need to find the stock boot.img or have help flashing a ROM that fails everytime.
When every instruction says "Extract ROM" that is only to pull out the boot.img right, we don't flash an extracted package you flash exactly what you downloaded right?

sdxben said:
Help, I will describe the following and any help I would love. I have the PRIMOC VM usa HTC ONE V.
Using Hasoon2000's All in one toolkit I have successfully Unlocked my phone, flashed TWRP recover 2.4.4, got root, and made a backup.
I then continue on to wipe cache and system and Factory reset to prepare to install ANY ROM. When I try to install the rom every time it just says Error in /sdcard/...[wherever rom is] (Status 1) FAILED
So then I proceed to restore my backup (this is why you always make a backup) and that works fine
Does the "(Status 1)" mean anything important?
I thought this was happening because I was running the newer radio so I used the RUU tool and now am using the good radio (not 0928) But this did not fix anything. This same thing happens over again. I have checked to make sure and I do have full root privileges.
I then tried to flash boot.img first and jmz kernel flashed successfully, but no rom will flash.
Why will NO ROM install?
I feel like I am missing something obvious but can't figure it out.
Also, whenever I do the factory restore it goes through all the process then fails when trying to wipe sd:ext , but my card is not partitioned. <I didn't know if that would be any help>
I am not a complete newb at all of this (running lg optimus for years- just new to the htc methods)
Click to expand...
Click to collapse
When u flash sickkernel make sure you also install the zip through your recovery that should fix your WiFi problems and which recovery are you using ? Twrp or cwm?
Sent from my HTC One V using xda app-developers app

Obeezy562 said:
When u flash sickkernel make sure you also install the zip through your recovery that should fix your WiFi problems and which recovery are you using ? Twrp or cwm?
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Hi Obeezy562,
my advice is to use the recovery program CMW or TWRP to re-format your external SD card. Then follow the normal instrutions and install the rom from zip using your recovery program. If you still have the same issue just let me know and I'll ponder longer.
regards

mcgi5sr2 said:
Hi Obeezy562,
my advice is to use the recovery program CMW or TWRP to re-format your external SD card. Then follow the normal instrutions and install the rom from zip using your recovery program. If you still have the same issue just let me know and I'll ponder longer.
regards
Click to expand...
Click to collapse
I'm not the one with the issue is sdxben lol I was just helping him but you are correct. I also recommend people cwm.
Sent from my HTC One V using xda app-developers app

Obeezy562 said:
I'm not the one with the issue is sdxben lol I was just helping him but you are correct. I also recommend people cwm.
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Ok, so tonight I will reformat my sdcard with TWRP then try to install the ROM. I tried the CWM recovery, but it was not touch based and did not respond to the power button as the OK, only the volume rocker worked.
I will try CWM recovery if someone can provide a link to the latest one, perhaps I was using an old one.

Twrp 2.4.4 I've also had issues with flashing some roms then downgraded to Twrp 2.2.0 and everything has been well since
sentfromtx

I can add that twrp 2.4 does have some issues. I use a cwm I found on google somewhere and if works just fine.
Sent from my HTC One V

http://forum.xda-developers.com/showthread.php?t=1871243
try this one out, should set up everything fine. Let me know if you need any further help

Unable to flash radio

Hi guys,
I have a wildfire with hboot-6.01.1002 S-off and radio 3.35.20.10.
I had the gps bug, so I tried all the ways to fix it but without success. So I tried to reflash radio and just trying to flash older versions I found out that the radio doesn't get flashed.
I tried laptop method too but with win8 is impossible for my wildfire to get recognized and all the tricks seen on internet or on this forum don't work.
Ooops I forgot to say that from RomManager I downgrade to cwm 2.x, then I reboot the phone, but in recovery I see again cwm 5.x, so everytime I install from there the 2.x version and I flash radio, but at system reboot I find 3.35.20.10 radio again.
Could you help me pls?
ps. sorry for my bad english.

sangkavr said:
Ooops I forgot to say that from RomManager I downgrade to cwm 2.x, then I reboot the phone, but in recovery I see again cwm 5.x, so everytime I install from there the 2.x version and I flash radio, but at system reboot I find 3.35.20.10 radio again.
Click to expand...
Click to collapse
You can try to use a temporary 2.x flashable cwm zip file and flash it after a cwm recovery reboot: I have cwm 6 installed and reflashing the radio in this way I usually fix GPS and WiFi problems (I have to do it once or twice every time after I install a new ROM).
Sent from my HTC Wildfire using xda app-developers app

Hi, could you explain me the procedure?
Where do I find a temporary cwm?
--- do you mean install a cwm 2.x in recovery mode? It doesn't work, I wrote it in the first post too.

mate, you don't have to flash a new radio to fix the GPS issue.
Here's what I do,
#Turn GPS on in your current ROM, and wait for a stable location fix,
#while GPS is still on, power off the phone.
#Now boot into recovery and flash your new ROM
#now after flashing and booting into your new ROM you'll be able to use GPS again.
You'll have to do this everytime you flash a new gingerbread ROM or above..
if your current ROM doesn't have working GPS, just flash Sense ROM, the GPS will work. then do as I said.
I always though flashing radio's are a little risky, as this is a risk free method, I think everyone should use this instead..
cheers ...

upon latesxt
Every time I try a sense rom at installing point I lose screen, just some colored strips, do you remember 80 cabinet game before loading? if yes ... those ones
But that's really strange that i'm not able to flash radio anyway.

sangkavr said:
Every time I try a sense rom at installing point I lose screen, just some colored strips, do you remember 80 cabinet game before loading? if yes ... those ones
But that's really strange that i'm not able to flash radio anyway.
Click to expand...
Click to collapse
I'm guessing you're referring to RemPuzzle ROM which has Aroma installer.
yea Aroma installer does that on cwm5.
only way to fix that is to revert to CWM4 permanent ( untill you decide to go back to a higher cwm version.)
anyway try another sense ROM, like DK's custom ROM or similar ..
cheers..

I was just reading about DK roms, it has to be installed using a temporary cwm.
Just a curiosity: all newer roms are cyano based?

sangkavr said:
I was just reading about DK roms, it has to be installed using a temporary cwm.
Just a curiosity: all newer roms are cyano based?
Click to expand...
Click to collapse
Yes, most gingerbread and up roms are usually bases on CM.
About the temporary cwm. Just flash it as a normal zip and you'd get temporary cwm2.5 , flash DK with that, after reboot you'll be back on your current cwm version.
Sent from my HTC Wildfire using Tapatalk 2

Just a thing, I flash a sense rom, after that I wait gps fix and then I install cyano rom. But without wipe or format?
I ask that cause before I use Mtd partition procedure to have more free space, and without any format and wipe I can't do that.

sangkavr said:
Just a thing, I flash a sense rom, after that I wait gps fix and then I install cyano rom. But without wipe or format?
I ask that cause before I use Mtd partition procedure to have more free space, and without any format and wipe I can't do that.
Click to expand...
Click to collapse
No no... just wipe everything. And also the Dalvik cache. Then install the new ROM. After rebooting to your new ROM GPS would work.
Sent from my HTC Wildfire using Tapatalk 2

Ehm .. dkmod roms failed to install cause "installation aborted", 4.6.2 and 4.7.
I tried joyOs but gps doesn't start. With Rempuzzle I have screen problems.
It seems I have to forget gps.

Flashing a radio requires at least 30mb on cache, so make sure you aren't using a custom mtd setup.
If its not the case, try flashing a 2.x permanent recovery and then flash the radio.

sangkavr said:
Ehm .. dkmod roms failed to install cause "installation aborted", 4.6.2 and 4.7.
I tried joyOs but gps doesn't start. With Rempuzzle I have screen problems.
It seems I have to forget gps.
Click to expand...
Click to collapse
you got installation aborted msg with CWM 2?
Mate, then try CM6. its a froyo ROM. and can be flashed with any CWM version. and as I remember GPS works without any issues. get it from http://get.cm/?device=buzz
then try again my steps.
hope it'll work. Good luck
cheers..

Thanks, cyano6 works.

sangkavr said:
Thanks, cyano6 works.
Click to expand...
Click to collapse
I'm glad you got it sorted
Cheers...

But now jellybread doesn't boot
arghhhhhh

sangkavr said:
But now jellybread doesn't boot
arghhhhhh
Click to expand...
Click to collapse
are you using custom mtd partitions?
if yes, there is an additional zip file to flash after flashing a new ROM.

I tried with higher mtd values but nothing, without mtd no problem, but without mtd this phone is useless for me.

sangkavr said:
I tried with higher mtd values but nothing, without mtd no problem, but without mtd this phone is useless for me.
Click to expand...
Click to collapse
If you have followed all the steps.correctly for custom mtd partitioning, it should work.
If it still fails, try link2sd, its an app. It moves apps to a separate partion in SDcard and saves internal storage.
But you have to partion your SDcard for that.
I suggest you should recheck if you followed all the steps correctly for mtd partioning. And remember to flash the bravo-boot.zip ( I don't remember the exact name) after flashing a ROM..
Sent from my HTC Wildfire using Tapatalk 2

I'm sure I followed all the steps, but I'm gonna try again.
Further jellybread is now on (without mtd) but without gapps too and they're integrated in the rom.
Android is trying to make me crazy

[Q] Radio fails to flash under CWM 2.5.0.7 recovery

I've been searching for a solution before writing my own post, for I'm aware there are probably many, many topics of people dealing with the same issue.
Well, here's is my problem.
I've got two wildfires A3333. Flashed CM 7.2.0 on both of them, successfully. GPS does work on only one of them. I've tried the GPS test on the other one. The compass is working, the localization is not.
So, as said before, I've googled for some solution for the other one, and here comes the temporary downgrading of CWM to 2.5.0.7 and then installing one of the following: buzz.radio-3.35.15.31-signed.zip, buzz.radio-3.35.20.10-signed.zip or buzz.radio-3.35.19.25-signed.zip that will be put on the SD.
Ok, everything is set up, let's reboot to recovery.
Now, the recovery screen is showing version 3.0.0.6 and I don't know if that's normal, since I've set it to 2.5.0.7 before rebooting. Won't mind for now.
Let's flash the zips. And all I get is this message, with all of the radios:
E: signature verification failed
Installation aborted.
Uhm, let's try by setting the option toggle signature verification to disabled.
Here's a different message:
Amend scripting (update-script) is no longer supported. Amend scripting was deprecated by Google in Android 1.5. It was necessary to remove it when upgrading to the Clockworkmod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation aborted.
It seems that the 3.0.0.6 version shown on the main menu is kind of relevant... Should it show 2.5.0.7 instead of that? What now?
Thanks in advance.

After flashing the temporary CWM,it'll automatically boot into that CWM version. Now flash the radio with that.
And if you reboot you'll return to the CWM version you had before.
To fix GPS you could also use this method,
http://forum.xda-developers.com/showthread.php?t=2354499

lakshan_456 said:
After flashing the temporary CWM,it'll automatically boot into that CWM version. Now flash the radio with that.
And if you reboot you'll return to the CWM version you had before.
To fix GPS you could also use this method,
http://forum.xda-developers.com/showthread.php?t=2354499
Click to expand...
Click to collapse
Yes, if by "flashing the temporary CWM" you mean entering the ROM manager, tapping on All ClockwordMod Recoveries, download the 2.5.0.7 version, let it install and tap Reboot into recovery, well that's exactly what I did. And the recovery screen is showing me this 3.0.0.6 version anyway, which is kind of suspicious to me.
I've already read the topic you linked, some days ago, but that means having to wipe the CM 7.2.0 and reinstall it later and I'm not sure whether I can backup the apps that are in the EXT partition since I'm using Link2SD. And honestly, I'm not even sure I'm able to make a good backup.

Snakebar said:
Yes, if by "flashing the temporary CWM" you mean entering the ROM manager, tapping on All ClockwordMod Recoveries, download the 2.5.0.7 version, let it install and tap Reboot into recovery, well that's exactly what I did. And the recovery screen is showing me this 3.0.0.6 version anyway, which is kind of suspicious to me.
I've already read the topic you linked, some days ago, but that means having to wipe the CM 7.2.0 and reinstall it later and I'm not sure whether I can backup the apps that are in the EXT partition since I'm using Link2SD. And honestly, I'm not even sure I'm able to make a good backup.
Click to expand...
Click to collapse
I wouldn't really recommend using ROM Manager, and what I meant by flashing was to flash the CWM zip with your current Clockworkmod recovery.
And also consider upgrading your recovery.
And about the guide, just make a nandroid backup with CWM, and restore it instead of flashing a new rom.
Hope this helps

I shall give a try to it all and let you know.
One last question before I proceed. In order to upgrade my recovery I'd have to download the latest CWM available for Buzz and install it the same way I'll do with v2.5.0.7 (of course, after that step), am I right?
Thanks!

Ok, I've installed the v2.5.0.7 via the install from .zip option and got to install the radios. Woo!!
No, hold back.
Now the GPS icon is showing up but GPStest doesn't detect any activity.
I've installed 13.55.55.24H_3.35.20.10 first, then 13.45.55.24H_3.35.15.31 and then 13.53.55.24H_3.35.19.25. Same result.
Now should I rely on plan B?
I've read of someone who got it working by installing the 3 radios in crescent order. Is it worth a try?

Snakebar said:
I shall give a try to it all and let you know.
One last question before I proceed. In order to upgrade my recovery I'd have to download the latest CWM available for Buzz and install it the same way I'll do with v2.5.0.7 (of course, after that step), am I right?
Thanks!
Click to expand...
Click to collapse
No, that'll only be temporary, as with 2.5.
Get the PC49IMG.zip file for that recovery, put it on the root of the SD, reboot to bootloader, it'll scan and will ask to install, select yes, you're done.
First GPS fix will take some time, maybe from 2-10 mins.
I've only flashed the .20.10 Radio. It worked for me...
Or if you have a sense rom or the backup of your stock rom, give the guide a try...

Try this radio file. link, worked for me under cwm 2.5.0.7

lakshan_456 said:
No, that'll only be temporary, as with 2.5.
Get the PC49IMG.zip file for that recovery, put it on the root of the SD, reboot to bootloader, it'll scan and will ask to install, select yes, you're done.
First GPS fix will take some time, maybe from 2-10 mins.
I've only flashed the .20.10 Radio. It worked for me...
Or if you have a sense rom or the backup of your stock rom, give the guide a try...
Click to expand...
Click to collapse
My fault, there's something I should make clear.
The radios I've been talking about before have been installed on the first Wildfire, the one I said the GPS was working (and in the meanwhile it proved to be untrue as I discovered the GPS icon has never showed up before flashing the radio). This one Wildfire has CWM 2.5.0.1, installed with Unrevoked. The second Wildfire (which I'd like to use as my usual phone) was rooted with PC49IMG as Unrevoked wouldn't work with it and is running CWM 3.0.0.6, which I've reported in the first post.
For now, let's discard the CWM 3.0.0.6 phone.
It is on the CWM 2.5.0.1 phone where I've temporarily installed 2.5.0.7 and flashed the radios. Could it be relevant?
(maybe I'd better update the CWM anyway)
ChristianPe said:
Try this radio file. link, worked for me under cwm 2.5.0.7
Click to expand...
Click to collapse
Uhm, link is broken. My CWM 2.5.0.7 looks to be working properly anyway.

stick with 2.5.0.7 recovery and 20.10 radios, that worked for me using Navitel, as for file here.

Flashed Froyo 2.2.1 shipped ROM... and GPS didn't work on it either. Great.
I've restored my CM backup and found out all my link2SD linked apps to be screwed in return. Vanished. Link2SD says there's soooo much free space in that second partition... can't imagine when it's been formatted, but nevermind.
ChristianPe said:
stick with 2.5.0.7 recovery and 20.10 radios, that worked for me using Navitel, as for file here.
Click to expand...
Click to collapse
I've already got that radio version but tried to flash the one you've gently provided me, well, same as the other radios. Icon showing but no activity at all.
I give up.

Snakebar said:
Flashed Froyo 2.2.1 shipped ROM... and GPS didn't work on it either. Great.
I've restored my CM backup and found out all my link2SD linked apps to be screwed in return. Vanished. Link2SD says there's soooo much free space in that second partition... can't imagine when it's been formatted, but nevermind.
I've already got that radio version but tried to flash the one you've gently provided me, well, same as the other radios. Icon showing but no activity at all.
I give up.
Click to expand...
Click to collapse
where you at?, i might be a weather-related issue?

ChristianPe said:
where you at?, i might be a weather-related issue?
Click to expand...
Click to collapse
Unlikely, it's been some days I'm testing the GPS on the phone. But I shall test it away from home to be sure.
I'm from Naples, (IT) by the way.

Snakebar said:
It is on the CWM 2.5.0.1 phone where I've temporarily installed 2.5.0.7 and flashed the radios. Could it be relevant?
(maybe I'd better update the CWM anyway)
Click to expand...
Click to collapse
Not really sure if CWM matters or not, we use 2.5 to flash radios because the flashing script is different from currently used ones.
Ty upgrading anyway,
Are you sure it isn't a hardware fault. If GPS doesnt work in stock rom, it could possibly be a hardware issue...

lakshan_456 said:
Not really sure if CWM matters or not, we use 2.5 to flash radios because the flashing script is different from currently used ones.
Ty upgrading anyway,
Are you sure it isn't a hardware fault. If GPS doesnt work in stock rom, it could possibly be a hardware issue...
Click to expand...
Click to collapse
Too weird it happens on both devices, even if... well them both have had a nice dive in the sea but GPS used to work before flashing the new ROMs on each phone.
Sure there's something not correct in my procedure but can't find it out.

Snakebar said:
Too weird it happens on both devices, even if... well them both have had a nice dive in the sea but GPS used to work before flashing the new ROMs on each phone.
Sure there's something not correct in my procedure but can't find it out.
Click to expand...
Click to collapse
Well, I'm sorry mate. unless its a hardware fault or something I'm not in the know of, there are no more solutions I can think of.

Behold! He's thinking back.
It just looks like it's not able to track many satellites. Well, at least that's a relief.

Snakebar said:
Behold! He's thinking back.
It just looks like it's not able to track many satellites. Well, at least that's a relief.
Click to expand...
Click to collapse
Indeed it is, atleast it wasn't a hardware issue
Well done mate...
P.S. :- I'd recommend using 'GPS status and Toolbox' app which is much better than GPStest.
Sent from my HTC Wildfire using Tapatalk 2

lakshan_456 said:
P.S. :- I'd recommend using 'GPS status and Toolbox' app which is much better than GPStest.
Click to expand...
Click to collapse
Done!
~400s for first GPS lock... yeesh...

Snakebar said:
Done!
~400s for first GPS lock... yeesh...
Click to expand...
Click to collapse
Mission accomplished.
Cheers
Sent from my HTC Wildfire using Tapatalk 2