Related
Hey guys and gals,
This is my first post and i need some help. Here's the story.
I rooted my phone a few weeks ago, everything went stunningly easy, and worked great. Clockworkmod recovery was installed (by unrevoked) at this time. While driving home I broke my phone's screen and had to get a replacement phone. Asurion had a phone to me within 18 hours (my word they're fast). I slapped the 16GB SD card from my first phone in and I was off and running.
So I have my new phone with my original 16GB SD card and set it up normally again. I wanted to wait a bit and get it set prior to rooting again. Tonight I rooted the phone with Unrevoked 3.21 as I did before. It went much faster than before. I now have S-Off but clockworkmod recovery is not on my hboot screen and recovery mode doesn't work at all. Just a black screen for about 15 seconds before loading into the OS.
Have I screwed up a one click root? I've tried a few things.
I used droid-life as a guide to help me root.
Phone Stats:
Droid Incredible
Asurion replacement
OS 2.2
radio 2.15.00.07.28
kernel 2.6.32.15-gb7b01d1
build 3.21.605.1 CL231334 release-keys
Although clockworkmod recovery isn't in Hboot the reflash tool still says "Recovery Image: ClockworkMod Recovery" on the bottom. I have tried renaming the clockworkmod folder on the SD card to see if it would create a new one, or boot into clockworkmod recovery after realizing the folder is not there.
I have also tried formatting my SD card and running the reflash tool again. Again no dice, no recovery mode.
I have tried unrevoked 3.21 after every change.
What have I done? what do I do? any suggestions?
Thanks for anybody and everybody's input. I appreciate it. I would like to start flashing roms but really dont want to mess with it if I dont have a recovery option.
-MOJO
Is it a complete download of the unrevoked tool? Sounds almost like the recovery package isn't there. Try redownloading unrevoked and run it again. Do you have root and Superuser app at least? If so, try downloading and running ROM Manager and tell it to flash Clockwork again. Still no dice, try telling it to flash RA recovery. And for the record, which screen do you have?
I wish I knew
PonsAsinorem said:
And for the record, which screen do you have?
Click to expand...
Click to collapse
thanks for the quick reply I will try that. Yes I have root and the superuser app.
I dont know how to tell which screen I have, but I was wondering the same thing. BoyGeniusReport says its incredibly hard to tell the difference and I haven't found were it says SLED vs AMOLED
Grrrr
PonsAsinorem said:
Is it a complete download of the unrevoked tool? Sounds almost like the recovery package isn't there. Still no dice, try telling it to flash RA recovery.
Click to expand...
Click to collapse
Downloaded unrevoked 3.21 straight from unrevoked twice.
Tried the reflashing clockworkmod recovery, no dice.
Whats an RA recovery?
RandomMOJO said:
Downloaded unrevoked 3.21 straight from unrevoked twice.
Tried the reflashing clockworkmod recovery, no dice.
Whats an RA recovery?
Click to expand...
Click to collapse
It's an alternate recovery. Here's the link: http://forum.xda-developers.com/showthread.php?t=758874
It's also the second to the last option in ROM Manager. Flash Alternate Recovery: RA_GNM Recovery v1.7.6
I actually like that one better. It was able to format my SD card correctly. I just miss the integration with ROM Manager.
Phew... It worked.
the alternate recovery worked.
now if I want to flash ROMs do I need to know anything in particular before doing so with the AMON_RA recovery tool.
I downloaded the a4d utility that I found when doing a search for AMON_RA on appbrain. It asks if I want to flash my phone to unlock my bootloader (and void my warranty, haha).
do I need to unlock my bootloader before flashing ROM's
I like the sense UI. thats all I have actually used. Is there anything better? what are suggested, STABLE, ROMs/kernels for the DInc? or should I stay "stock 2.2 rooted"?
RandomMOJO said:
the alternate recovery worked.
now if I want to flash ROMs do I need to know anything in particular before doing so with the AMON_RA recovery tool.
I downloaded the a4d utility that I found when doing a search for AMON_RA on appbrain. It asks if I want to flash my phone to unlock my bootloader (and void my warranty, haha).
do I need to unlock my bootloader before flashing ROM's
I like the sense UI. thats all I have actually used. Is there anything better? what are suggested, STABLE, ROMs/kernels for the DInc? or should I stay "stock 2.2 rooted"?
Click to expand...
Click to collapse
Uncommon sense with king kernel bfs # 5 is as good or better than stock.
Btw. Hboot only shows recovery, not clockwork recovery. Did you ever try selecting recovery from hboot?
silverxbv2 said:
Uncommon sense with king kernel bfs # 5 is as good or better than stock.
Click to expand...
Click to collapse
and still has all the capabilities of stock 2.2 (GPS, WIFI Tether, etc), I know that was a problem at one point. I assume/hope all has been fixed with those issues.
With flashing ROMs. do Custom ROM's have the bloatwear (CityID) removed?
RandomMOJO said:
and still has all the capabilities of stock 2.2 (GPS, WIFI Tether, etc), I know that was a problem at one point. I assume/hope all has been fixed with those issues.
With flashing ROMs. do Custom ROM's have the bloatwear (CityID) removed?
Click to expand...
Click to collapse
Uncommon sense has some of it removed. Some of it you can remove yourself. It's the only rom I've donated to and had on my phone more than two days.
Just be careful if removing stuff. Some of it has other dependencies. There are guides on how to remove things safely without breaking other functionality.
Also do a backup first. I'm not sure how amon ra works, but it must be in there somewhere.
RandomMOJO said:
and still has all the capabilities of stock 2.2 (GPS, WIFI Tether, etc), I know that was a problem at one point. I assume/hope all has been fixed with those issues.
With flashing ROMs. do Custom ROM's have the bloatwear (CityID) removed?
Click to expand...
Click to collapse
I used to use Virtuous 3.0.1, but I've switched over to Redemption ROM 2.0.5
silverxbv2 said:
Also do a backup first. I'm not sure how amon ra works, but it must be in there somewhere.
Click to expand...
Click to collapse
It is. In the main menu, just like Clockwork
So I definitely have recovery with the amon_RA 1.7.6 alternative recovery with the ROM manager. but from what I have read I can no longer use ROM manager to flash.
Now I have been searching for information/instructions on how to use AMON_RA but have come up short, at least recently written stuff. I can find a ton of information about clockworkmod which I assume is because of Unrevoked 3.21.
PonsAsinorem as you said you miss the integration of ROM manager. I really want to use ROM manager.
I read somewhere in XDA that people were having trouble using clockworkmod and ROM manager and it could be because of a corrupted cache. there were some LIMITED instructions about using ADB to fix it but I wasn't completely understanding them.
I think my problem is spawning from using my old SD card and maybe a corrupted cache. I have made a back up using Amon_RA (actually two).
Does anyone think that completely formatting my SD card (after moving my backups to my MAC) and factory restoring my phone. then reflashed using unrevoked 3.21, or reflashed clockworkmod recovery using rom manager would work to solve my problem with clockworkmod recovery?
I would have backups if it didn't work. I would just have to restore the Amon_RA backup if I screwed anything up or wanted my SD card back... Right?
Thanks for all the help so far.
MOJO
Found this and it solved the problem for me:
http://androidforums.com/incredible...ckwork-recovery-blank-screen.html#post1723460
dirtpan said:
Found this and it solved the problem for me:
http://androidforums.com/incredible...ckwork-recovery-blank-screen.html#post1723460
Click to expand...
Click to collapse
Dirtpan. you're a lifesaver thanks for pointing me at this. saved clockwork for me. All this time, its because I have the new SLCD screen as opposed to the AMOLED screen.
For the record, my wife has an AMOLED screen and I an SLCD. I can see no discernible difference.
Thanks again everybody for the help.
MOJO
So I'm tying to flash Incredibly Re-Engineered and I know you have to have a lower updated version of cwm. I tried to manually downgrade trough Rom manager but when I try to it says that I can not. Can anyone show or tell me how to? And does anyone know which version I should use? I would post this directly to the Incredibly Re-Engineered page but as a new member I can not. Anything helps
mkhang said:
So I'm tying to flash Incredibly Re-Engineered and I know you have to have a lower updated version of cwm. I tried to manually downgrade trough Rom manager but when I try to it says that I can not. Can anyone show or tell me how to? And does anyone know which version I should use? I would post this directly to the Incredibly Re-Engineered page but as a new member I can not. Anything helps
Click to expand...
Click to collapse
I believe its a PB32IMG.zip to flash through HBOOT, just google PB32IMG.zip 2.5.1.2 and it should pull something up. I'm pretty sure that's how it should go. If not, consider this a bump, and I'm sorry lol.
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS5.3.
I'm having issues here as well with cwm 3.0.7, it just flat out will not boot into recovery, and ROM manager no longer has the option to flash 2.5.1.2. I also wasn't able to find a PB32IMG.zip cwm 2.5.1.2 recovery, but maybe I just didn't look hard enough. If anyone could provide any link/instructions for how to get my old recovery back it would be very much appreciated!
hotpantsmcgavin said:
I'm having issues here as well with cwm 3.0.7, it just flat out will not boot into recovery, and ROM manager no longer has the option to flash 2.5.1.2. I also wasn't able to find a PB32IMG.zip cwm 2.5.1.2 recovery, but maybe I just didn't look hard enough. If anyone could provide any link/instructions for how to get my old recovery back it would be very much appreciated!
Click to expand...
Click to collapse
Wow, I'm sorry. Its PB31IMG.zip lol I'm fail :/
EDIT: Here's a link to a few recoveries, you're going to want the second one listed there http://dougpiston.com/?page_id=85
Rename it PB31IMG.zip put it on the root of your sd card, and boot into hboot. Be sure to check your MD5 sum with the one provided to [hopefully] be problem free. Again, I'm sorry about before :/
Sent from my Droid Incredible running Myn's Warm TwoPointTwo RLS5.3.
No worries, got it back up and running again. Thanks for the help!
hotpantsmcgavin said:
No worries, got it back up and running again. Thanks for the help!
Click to expand...
Click to collapse
No problem.
Sent from my Droid Incredible running Myn's Warm TwoPointTwo RLS5.3.
I've searched this whole forum (and learned a lot) but I'm still stuck!
I upgraded from Leedroid (Froyo) to InsertCoin (Gingerbread) but the upgrade failed and now all I get is the white HTC screen.
I have:
BRAVO PVT4 S-ON
HBOOT-0.93.0001
Clockworkmod v2.5.07 (installed when I rooted with unrevoked earlier this year).
I can access HBOOT, fastboot, clockworkmod, but not the main system.
I tried restoring from Nandroid. Had MD5 errors, but once I fixed those it still doesn't work.
I've tried RUU to no avail (Got error 170).
Tried flashing Leedroid via Clockworkmod, says it's successful but it makes no difference.
So, no Nandroid, no RUU, no ability to flash new roms. What else should I try?
Your suggestions are GREATLY appreciated
go to mounts & storage, format boot, system, userdata, cache.
go to flash zip from sdcard, and choose your ROM. Should work.
Aye, it just worked then - with an older version of Leedroid.
Do newer ROMs require newer versions of Clockworkmod? Or S-off? Because I have an old clockworkmod and S-on. Those are the only things I can think of that might have broken my Gingerbread installation (and caused the Nandroid restore to fail).
S-OFF and try flashing RaDesire, it's probably the best recovery for the Desire.
Also being S-OFF makes the phone a lot easier to "fix".. e.g. if your recovery mysteriously died and so did your system then you'd have to use a RUU to return to stock, then re-root or S-OFF again.. however with this you could just flash a new recovery. Simples.
http://forum.xda-developers.com/showthread.php?t=839621
they don't require a newer recovery.. it probably didn't boot because you didn't do a full wipe that's all.
My only hesitation with S-Off is that after screwing up this ROM upgrade I was thankful of that 'safety net'. But I agree that it would make things easier to fix. As long as I can get into the bootloader
Currently attempting to install AmonRa...
zouden said:
My only hesitation with S-Off is that after screwing up this ROM upgrade I was thankful of that 'safety net'. But I agree that it would make things easier to fix. As long as I can get into the bootloader
Currently attempting to install AmonRa...
Click to expand...
Click to collapse
if you need help on how to do it just ask. (you need to be S-OFF first by the way..)
Oh, I didn't see that post until I already started the process via Unrevoked. It seemed to work though. I have AmonRa Desire v2.
It's late here now though, so I'll try installing InsertCoin in the morning. Thanks for all your advice, greatly appreciated
zouden said:
Oh, I didn't see that post until I already started the process via Unrevoked. It seemed to work though. I have AmonRa Desire v2.
It's late here now though, so I'll try installing InsertCoin in the morning. Thanks for all your advice, greatly appreciated
Click to expand...
Click to collapse
There's a thank button ya know
AmonRa successfully installed InsertCoin
Though I had to disable signature verification. Is that normal?
zouden said:
AmonRa successfully installed InsertCoin
Though I had to disable signature verification. Is that normal?
Click to expand...
Click to collapse
In short, yes.
zouden said:
AmonRa successfully installed InsertCoin
Though I had to disable signature verification. Is that normal?
Click to expand...
Click to collapse
This has to be done from to time to time for a few zips. Nothing to worry about.
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
davidnjessicacruz said:
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
Click to expand...
Click to collapse
I would recommend tracking down calkulins format zip for the evo
1brainsurgeon said:
I would recommend tracking down calkulins format zip for the evo
Click to expand...
Click to collapse
Yeah... tried that already... Didn't fix it...
davidnjessicacruz said:
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
Click to expand...
Click to collapse
I can say with certainty that I don't have this problem. I've flashed every ROM from here to Timbuktu, AOKP, Deck's, Evervolv, and have had no problem restoring a nandroid of, or flashing MikG, Mik3D, MikRunny, The Express, or any other ROM I may have forgotten.
That boot partition error doesn't sound good, though. What HBOOT version do you use?
Captain_Throwback said:
I can say with certainty that I don't have this problem. I've flashed every ROM from here to Timbuktu, AOKP, Deck's, Evervolv, and have had no problem restoring a nandroid of, or flashing MikG, Mik3D, MikRunny, The Express, or any other ROM I may have forgotten.
That boot partition error doesn't sound good, though. What HBOOT version do you use?
Click to expand...
Click to collapse
HBOOT 0.97 is what I'm still using... never upgraded... should I & how do you recommend that I do so?
davidnjessicacruz said:
HBOOT 0.97 is what I'm still using... never upgraded... should I & how do you recommend that I do so?
Click to expand...
Click to collapse
No reason to upgrade - just wondering.
I'd recommend you flash a stock ROM in the bootloader - that should normalize everything, and then try those other ROMs again.
Captain_Throwback said:
No reason to upgrade - just wondering.
I'd recommend you flash a stock ROM in the bootloader - that should normalize everything, and then try those other ROMs again.
Click to expand...
Click to collapse
I assume your talking about in the recovery (aka amon ra/ clockworkmod), if so then I've tried that as well. Same issue.... This is not sounding good for me.
davidnjessicacruz said:
I assume your talking about in the recovery (aka amon ra/ clockworkmod), if so then I've tried that as well. Same issue.... This is not sounding good for me.
Click to expand...
Click to collapse
I believe he's talking about a RUU
Sent from my PC36100 using XDA App
evo4gnoob said:
I believe he's talking about a RUU
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The stock one? Wow... don't even know how to flash that back.... hmm... I'll see if I can find it here, if not then I'll google it. I'll keep you informed.... hopefully bricking does not ensue.... any help here would be great as well
davidnjessicacruz said:
The stock one? Wow... don't even know how to flash that back.... hmm... I'll see if I can find it here, if not then I'll google it. I'll keep you informed.... hopefully bricking does not ensue.... any help here would be great as well
Click to expand...
Click to collapse
In the first "My Links" link in my sig, there are 3 of them.
They're PC36IMG files - you rename the file to exactly that - PC36IMG.zip - and put the file on the root of your sd card. Then you reboot your device into bootloader (HBOOT) mode. From a powered off state, hold the Volume down button and then press and hold the power button until you see the HBOOT screen. The file should be recognized and loaded, and after a minute or so it will ask you to update. Press Volume Up to accept, and then wait for a while.
NOTE: This will upgrade your HBOOT, but that's no big deal. The phone will reboot into the bootloader once near the beginning of the process by itself - that is also okay. Don't touch anything while it's updating.
At the end of the process, you'll need to find a PC36IMG for your preferred recovery (RA-supersonic-v2.3 recommended), which you will flash the same way as the ROM (in fact, you can replace the ROM file with the recovery file - unless you want to hold on to it, then you can just move or rename it).
Captain_Throwback said:
In the first "My Links" link in my sig, there are 3 of them.
They're PC36IMG files - you rename the file to exactly that - PC36IMG.zip - and put the file on the root of your sd card. Then you reboot your device into bootloader (HBOOT) mode. From a powered off state, hold the Volume down button and then press and hold the power button until you see the HBOOT screen. The file should be recognized and loaded, and after a minute or so it will ask you to update. Press Volume Up to accept, and then wait for a while.
NOTE: This will upgrade your HBOOT, but that's no big deal. The phone will reboot into the bootloader once near the beginning of the process by itself - that is also okay. Don't touch anything while it's updating.
At the end of the process, you'll need to find a PC36IMG for your preferred recovery (RA-supersonic-v2.3 recommended), which you will flash the same way as the ROM (in fact, you can replace the ROM file with the recovery file - unless you want to hold on to it, then you can just move or rename it).
Click to expand...
Click to collapse
Failed on #4 Boot.... it stated "failed - PU" "Partition failed" Fun times.... Now the phone is a brick (stuck at the white screen).... Where there is a will then there is a way so I'll find a way.... any help would be appreciated though....
Sooo... I was able to flash back my alternate recovery using a PC36IMG version of it. Thank god for the rooted community.... Restoring back my last backup. Funny though, that I still could not restore a rooted stock backup I had or a new upgraded .zip that I wanted to use. Common denominator in all this (even when trying to use the 4.24.651.1 version of the stock software PC36IMG), it can not write the boot.img Any one else had this problem? Next I will try to RUU which will technically make me lose root but I should be able to get it back, assuming I'm successful, since I still have S-OFF.
PS: My HBOOT now, btw, is 2.16.0001 so I know that the original attempt to get back to gingerbread was succesful
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