[Q] Wifi problem with Froyo - Upgrading, Modifying and Unlocking

Alright as the Title says I got a problem with Froyo.
First of all, this is the first time i ever tried anything with a cellphone, although so far it went well (took me long though).
First I removed an old version of cyanogenmod from the old user.
Then I followed this guide: http://forum.xda-developers.com/showthread.php?t=1098899
Then I installed Froyo by Laszlo 5.2
http://forum.xda-developers.com/showthread.php?t=929678
Now to my ultimate surprise, I actually got this all done and it works perfectly, except for one thing. Wifi does not work. When I turn it on it starts scanning for networks, then gives the message "unable to scan for network" and Wifi automaticly gets turned off again. Before installing this I always found 2 networks from the point I'm sitting now.
I simply got no clue what it could be.
Some info. Following the guide for radio and boot I got the correct information in the bootloader as mentioned in step 3:
Dream PVT 32b SHIP S-on
HBOOT 1.33.0013d (drea10000)
CPLD-4
RADIO 2.22.28.25
OCT 21,2009,22:33:27
About Phone:
Android version 2.2.1
Baseband version 62.50SJ.20.17U_2.22.28.25
Kernel version 2.6.34.8-froyobylaszlo [email protected] #1
Mod version FroyoByLaszlo-5.2
If you need more info, just ask.
And thanks in advance,
Greetings,
Noddahead

Little update here. On some forums i found that a file bcm_supp.conf in /data/wifi caused a problem like mine. When I plug in my phone in my pc I only see the sd card. Therefore I installed sdk/adb thing, connected with my phone (correctly). and I manually tried to remove the file via cmd. This resulted in the notification that the file did not exist.
Hence, back to nothing. Any way I can make my internal memory show up again?
All in all it seems like I got the same problem as many people had with Froyo. But it seemed solved for everyone after a certain patch. My Froyo version is obviously more recent. And no one seems to have this problem with this version of Froyo (in the Froyo by Laszlo thread page 97ish and forth)

Related

2.29.405.2 update bugfest - any way to roll back?

Did the 2.29.405.2 update OTA initially and noticed problems. So reinstalled it from SD card but no help.
Bought sim free, unbranded/locked and never rooted:
Cannot dial out from phone lists or contacts. Going to phone and clicking on an entry in the call list does not launch phone call any more. Going to contacts, opening one and clicking on an available phone number does not launch phone any more.
The only way I can make a call is to punch it in on the keypad! Grrr.
Wifi connects to my home base after a reboot but, after an undetermined amount of time it drops the connection and cannot get it again. Going to Wifi settings shows it scans, connects and tries to obtain IP address. After a short time it gives up, turns wifi off and starts over. Again & again.
Cannot get it to connect again without another reboot.
This is a crippling loss of functionality for me. Can anyone suggest a way to roll back this update so my phone works as id did?
Many thanks all,
M1
First try a hard rest(you will lose all personal data on the phone,pictures and other stuff on the SD will be fine). If that does not work try either the 2.29.405.2 or 2.10.405.2 RUU.
More info - to my horror, around 15 minutes after I had tried and failed to make calls from contacts the phone started making them one after the other as if they were stuck in a spool or something! Ouch - any thoughts?
Backup everything you can and flash the same ruu from shipped roms.
Sent from my HTC Desire using XDA App
> flash the same ruu from shipped roms
where do I find this? - android noob!
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
And if it works, keep it safe!
Sent from my HTC Desire using XDA App
Thanks to all for help on this. Decided worth a trouble shoot before a hard reset and culprit seems to have been an app - extended controls widget. Removed this and all seems well again.
Try this one. This definately works! i have used it.
http://forum.xda-developers.com/showthread.php?t=768256
I was stuck at 2.29 update.
Then i used this guide and windows tool.
So i did this process and it rolled my phone back to stock android 2.1 rom 1.X
The first version that the phone was bought with.
This tool will boot the phone into bootloader and load a stock 1.x rom ota off the sd card as the tool will extract it to sd card and then load it.
This will wipe all your data not sure about the sd card as i dont remember any of that because i formatted my sd card after i had used the tool.
Thats because i had rooted my phone and tried custom sense hd rom.
The only reason i had was of the battery usage as the consumption was very badly increased and that the 2.29 rom was unstable.
PS: I did first try the htc service in Denmark. They couldn't help me and said i was stuck with the 2.29 rom update. :/
After my phone got rolled/flashed back to stock android 2.1.
The next day in the morning i could upgrade again to android 2.2 rom ver. 2.10 OTA from htc servers.
Maybe this works for you as i did for me and others.
Turns out it wasn't the app.
After a couple of days playing ok my sim free stock htc desire is unstable again.
Cut me off mid call - went to phone and clicked on last call entry - absolutely nothing happened, repeated with same problem. Exited phone to home screen then opened contacts and tried to make call from there - same behavior, a complete hang.
No web access either so opened wifi manager to find it hanging on "obtaining IP address" from my home network and continually shutting down and restarting wifi automatically at this stage.
Noticed general UI lag and several apps failing to open too.
Left phone alone and again, around 10 minutes later all of the actions - including trying to make the phone calls started running one after the other. Like everything had been caught in a spool or something. After this all seemed OK until it happened all over again later.
Although the UI seemed OK and some apps worked as expected, the only way to get phone and wifi working whilst it was hung was a warm boot.
Dreading a hard reset as it's going to waste another day or two getting everything reconfigured just so (can't find a back up solution that does everything - multiple mail account settings etc) but looks like only option.
Will try going back to mikep99's suggested rom as soon as I have time and will not be responding to an HTC OTA auto update offer again.
Grrr.
I still suspect an app conflict.
Can anyone recommend a util that might give me a clue which app / sys process could be hogging system / radio resources?
just got another OTA update pushed to me. installed (nothing to loose) and Congratulations my phone has been updated to 2.29.405.5.
Not sure whats going on here as that was the update I got 2 days ago. This time round it was only 4.8mb download so I'm assuming it's an update update. Hope it fixes things .....

[SOLVED] help! Can't enable bluetooth

EDIT: SOLVED!!!! it was a usb brick. see last post for details.
hi all,
I have a problem with my desire.
Bluetooth won't turn on. If I try to enable BT, it says grey'ed out for like 10 secs and the goes back to unchecked.
I got this device used so I don't have many background information. All I can tell is I tried different ROMs and wiped all I could, but still no luck. I actually highly suspect this might be an hardware issues, but I'd really like to try everything before shipping back to assistance.
Here are my current specs:
htc desire amoled
bravo pvt1 ship s-on
hboot 0.80.0000
radio 5.11.05.27
rom cyanogenmod 7.1.0
kernel 2.6.37.6-cyanogenmod-geb50077
Recovery: Clockworkmod
ANY hint highly appreciated.
Got exactly the same problem.
BT worked while running the former stable CM release. I first noticed this issue when flashing latest CM. You tried other ROMs which didnt work?
Did you try other Radios as well?
I am not an expert, but I think it could be a problem of the radio. I never totally understood what the radio does, so could anybody help with this guess? I never changed Radio as there was no need for (never touch a running system).
lexo, did you try rolling back to 7.0.3 to see if BT would work again?
I was also thinking about radio, exp b\c it seems to not be a ROM-specific issue, as I have tried several: LeeDroid, InsertCoin, MIUI, as well as a stock rom.
I believe the point with radio is not necessarily about having the latest, but finding the one that works well with one's rom. Also, there is RIL, but that I don't know what it does.
No, didnt try that yet.
I use BT in my car to listen to music only so I didnt notice the issue at first. Now i am thinking about buying Galaxy Nexus, so I am not too exited about that point. But as I am willing to pass my Desire to my lil sister I would love to have it fixed.
Whats "RIL"? Think I never heard about it.
Don't know if this is relevant but had a similar problem with Bluetooth, wifi and Mobile data yesterday. None of them had connectivity!
The remedy that worked for me was to wipe the cache and dalvik, reflash CM7.1 via recovery (but remember to also flash the Google apps package) and soft reset.
No data is lost this way.
Hope that helps!
Sent from my HTC Desire using XDA App
This may not be relevant but when I couldn't enable Bluetooth on my done when I have a USB brick.....
Try the USB brick fix it may work
Sent from my HTC Desire using XDA App
update:
so far I did:
- wiped everything including dalvik and reflashed cm7 - no luck
- removed files in etc/bluetooth [read somewhere] - nuthing
- applyied a .zip update that is supposed to fix a possible USB brick - no change.
@LEXO: I think you might try the first two things I did, in your case they might work.
So now I flashed a RUU Rom and reverted to stock s-on bootloader, hboot, radio (ril, too, I believe, though I dunno how to tell ril version) and recovery.
The only thing I'm not completely sure about is the USB brick fix, but otherwise it's ready to ship to assistance.
@Reaper, can you point me to the USB fix you referred to?
guys!!! Thanks everyone, expecially reaper.
My BT is working again!!! turn out it was a USB brick, which I was able to solve fairly easy.
I had tried a usb brick fix that involved flashing a .zip, which I did. However still no BT changed so I assumed phone was not bricked after all.
Also, I always assumed usb brick would involve major cd and usb connect malfunctions, and that was not my case at all.
However it must have been that fix that didn't work, because I then followed the guide on this forum http://forum.xda-developers.com/showthread.php?t=691639: got my CID via fastboot, modified the files accordingly, put them on sd card, got temp root with visionary, issued the necessary commands with "free root system tool" terminal, rebooted, and voilà! BT is finally green.
I can't believe I made it!

[Q] AceSMod007 V41_CM7 Troubleshooting Help?

Hey guys!
So. This is the first time I've been stumped enough to actually post, so I can't post to the actual ROM thread. I hope someone sees this and will help me.
Currently, I've succeeded (after many redos and restores) in getting AceSMod007 v41 onto my CDMA HTC Desire (BravoC). Fought with the patch for a while but it's functional. In case it's a needed tidbit, my radio is 0.93 CM7.
The problems I'm running into aren't the ones I'm seeing most people run into. I'm not having a problem with the lock screen or bootloops. My WiFi is acting up since I loaded the rom. It refuses to even turn on. It just says "Error" under the WiFi checkbox. At one point I found a "wifi_fix.zip" in the development forum from an earlier version, but when I flashed that for some reason my phone refused to go past the HTC loading screen so I had to restore.
The bigger problem I'm having is that I absolutely cannot update my APNs. On CM7 all I had to do was flash my "cellularsouth-mms.zip" and then restore default in APNs. That doesnt work. So, I tried to manually save a new APN with the appropriate information and it refuses to save the APN settings.
Other than that I'm running great though!
No one at all?

[Q] Wi-Fi doesn't work. Need help. I'm new to this.

Hello, I'm new here to this and to the flashing stuff and rest.
I wanted to do some change to my buzz so I just flashed my 2.2.1 to 2.3.7 (CyanogenMod-7.1.0.1).
Everything was fine, flashed Gapps also.
The only thing is my wi-fi isn't working.
It can't even connect. It's like refreshing by 3 secs and doing that in a circle.
/// What I Did:
- Reflashed CyanogenMod twice.
- Reflashed my radio (the newest version anyway).
/// Specs:
- Android 2.3.7
- CyanogenMod-7.1.0.1
- Radio 3.35.20.10
- HBOOt 6.01.1002
- S-OFF
Did everything today and WiFi was working in the morning perfectly (on 2.2.1)
Just let me know if you want to know something more. Thanks guys.
Heard that Regulatory domain may cause that problem. Tips?
There is a cm mod 7.2 and that must fix it i think
Sent from my HTC Wildfire using xda app-developers app
wilek619 said:
Hello, I'm new here to this and to the flashing stuff and rest.
I wanted to do some change to my buzz so I just flashed my 2.2.1 to 2.3.7 (CyanogenMod-7.1.0.1).
Everything was fine, flashed Gapps also.
The only thing is my wi-fi isn't working.
It can't even connect. It's like refreshing by 3 secs and doing that in a circle.
Click to expand...
Click to collapse
first of all: you asked if regulatory domain could have to do with your problem. If you have access to your WiFi's settings you could check that by simply changing the channels (the procedure for that might be totally different in different routers). From my experience I doubt it anyway but I might be wrong here.
Another possibility to check if your phone's WiFi works or not would be to log into a different network - no idea if you could do that.
The reason I'm suggesting this first is, we could of course suggest things you might try with your phone - but - if your WiFi is the problem this might take some days and wasting lots of posts without any result or help
Did you do wipe all? I think if you installed CyanogenMod 7.2 it would be ok then. Give a try
Some tests that you can do:
- Flash an older radio, to see if the radio didn't got corrupted somehow. Reboot the phone and then flash the newer again;
- Flash the stable CM7.2;
Did you have issues with the stock ROM and the wifi?
Sent from my badass HTC Wildfire.

[Q] Phone restarts when using 3G (GSM/WCDMA)

Hi XDA people,
This is my first post in XDA and its a problem i am facing. Whenever i switch to GSM/WCDMA Mode and start using the 3G internet, the phone restarts with 5 - 7 vibrating alerts. I did searched this forum before posting and got similar posting for HTC Buzz
BIG ISSUE: 3G problem..!!
http://forum.xda-developers.com/showthread.php?t=1823816
Went through that and found out that by updating the radio this problem can be fixed, so went ahead to find the udpated radio and hboot and updated them using RUU, got a tutorial for the same in XDA forums
So updated Radio from 7.53.39.03M to 7.54.39.28M
Hboot : 1.08.0000
But the problem is still there, as soon as i switch it to 3G mode, i can see the H symol comes up for the GPRS and the network changes to R (Roaming- no clues why this happens but i am fine with this as long it works.) and within minutes it restarts making 5-7 vibrating alerts before rebooting.
can someone help me with this, is there a way to fix this for HTC Wildfire S (Marvel)
Kernel : [email protected] #2
Android version : 2.3.5
Htc Sense : 2.1
Software Number : HenseMod 7
tonan791 said:
Hi XDA people,
This is my first post in XDA and its a problem i am facing. Whenever i switch to GSM/WCDMA Mode and start using the 3G internet, the phone restarts with 5 - 7 vibrating alerts. I did searched this forum before posting and got similar posting for HTC Buzz
BIG ISSUE: 3G problem..!!
http://forum.xda-developers.com/showthread.php?t=1823816
Went through that and found out that by updating the radio this problem can be fixed, so went ahead to find the udpated radio and hboot and updated them using RUU, got a tutorial for the same in XDA forums
So updated Radio from 7.53.39.03M to 7.54.39.28M
Hboot : 1.08.0000
But the problem is still there, as soon as i switch it to 3G mode, i can see the H symol comes up for the GPRS and the network changes to R (Roaming- no clues why this happens but i am fine with this as long it works.) and within minutes it restarts making 5-7 vibrating alerts before rebooting.
can someone help me with this, is there a way to fix this for HTC Wildfire S (Marvel)
Kernel : [email protected] #2
Android version : 2.3.5
Htc Sense : 2.1
Software Number : HenseMod 7
Click to expand...
Click to collapse
it happened to me, the only solution I found was flash the backup of my original Rom Sense PREROOT, turn on 3G and check that it worked.
Then without turning off the 3G flash another rom clean (a bit like the problem of the gps).
is a bit long but I was going crazy, my Willy sometimes restarted.
it may be useful with my HTC Buzz it worked ... but you're rooted?
quack75 said:
it happened to me, the only solution I found was flash the backup of my original Rom Sense PREROOT, turn on 3G and check that it worked.
Then without turning off the 3G flash another rom clean (a bit like the problem of the gps).
is a bit long but I was going crazy, my Willy sometimes restarted.
it may be useful with my HTC Buzz it worked ... but you're rooted?
Click to expand...
Click to collapse
Yes i am rooted, also i dont have any stock backup
I read in the forums that in HTC buzz if you update to an older radio then wipe cache then update to a higher radio version it fixes it, but i need to find out if that would work for MARVEL, and what would be versions that i should switch to.
thanks for the help
tonan791 said:
Yes i am rooted, also i dont have any stock backup
I read in the forums that in HTC buzz if you update to an older radio then wipe cache then update to a higher radio version it fixes it, but i need to find out if that would work for MARVEL, and what would be versions that i should switch to.
thanks for the help
Click to expand...
Click to collapse
tonan791 said:
Hi Eventcom, i went through the forum and found that you too had this same problem of bootloop after switching to 3g. I see that you have Buzz, just wanted to know will this simiar fix (update older radio, wipe cache, update to newer radio) can be applied on HTC wildfire Marvel as well.
I have posted my question after a lot of search, got similar threads for BUZZ but none for MARVEL, can you please help.
http://forum.xda-developers.com/showthread.php?p=31998311
Click to expand...
Click to collapse
Well, I don't know anything about the Marvel. Both phones are quite different besides their names and enclosure.
Anyway I don't think that your phones radio will be touched when flashing a ROM or restoring a nandroid backup or that you could wipe, clear or format your radio partition - so in theory it could work with the Marvel, too.
A short explanation about the whole thing: The Buzz has well known issues with the radio (no GPS or BT, WiFi probs) - even directly after rooting and flashing the first custom ROM. There's also a chance that something might go wrong or get messed up when flashing different ROMs, installing tweaks etc. and the problem is that the radio resides on a separate partition which can't be wiped or formatted. All this sounds pretty logical to me but I'm not a developer so I might be totally wrong
The solution seems to be to flash a different radio (older/newer doesn't matter) to "overwrite" the current one - and sometimes reflash the current ROM again.
The problem I had has been hard to spot and even harder to solve. Luckily I found out that switching on 3G initiated the reboots (after quite a while and by accident, really). I made a lot of tests and could put it down to that (WiFi, 2G had no probs - phone rebooted only when switching to 3G or switching on data when 3G has been activated/chosen).
Furthermore I found the "solution" by accident, too: I reflashed the current radio without any success. Then I also tried an older radio - no success. So, as a final attempt, I started to download a RUU to reset the phone to factory condition.
The download server has been awful slow - it took ages to download the file - so I (almost randomly) decided to flash the previous radio again.
I couldn't believe it: that did the trick. (Luckily) I rebooted again, switched on data and 3G and noticed that the phone didn't reboot anymore.
So if you're able to flash a different radio - just give it a try. For the Buzz you need to be S-OFF to flash a radio - no idea about your phones.
I'd be glad if that would work for the Marvel, too :fingers-crossed:
I found this tread
http://forum.xda-developers.com/showthread.php?t=1485345
if you do not solve in any other way you could give it a try
I do not know the Marvel, but the Buzz htc are not all the same, the same solution to different results :silly:
eventcom said:
Well, I don't know anything about the Marvel. Both phones are quite different besides their names and enclosure.
Anyway I don't think that your phones radio will be touched when flashing a ROM or restoring a nandroid backup or that you could wipe, clear or format your radio partition - so in theory it could work with the Marvel, too.
A short explanation about the whole thing: The Buzz has well known issues with the radio (no GPS or BT, WiFi probs) - even directly after rooting and flashing the first custom ROM. There's also a chance that something might go wrong or get messed up when flashing different ROMs, installing tweaks etc. and the problem is that the radio resides on a separate partition which can't be wiped or formatted. All this sounds pretty logical to me but I'm not a developer so I might be totally wrong
The solution seems to be to flash a different radio (older/newer doesn't matter) to "overwrite" the current one - and sometimes reflash the current ROM again.
The problem I had has been hard to spot and even harder to solve. Luckily I found out that switching on 3G initiated the reboots (after quite a while and by accident, really). I made a lot of tests and could put it down to that (WiFi, 2G had no probs - phone rebooted only when switching to 3G or switching on data when 3G has been activated/chosen).
Furthermore I found the "solution" by accident, too: I reflashed the current radio without any success. Then I also tried an older radio - no success. So, as a final attempt, I started to download a RUU to reset the phone to factory condition.
The download server has been awful slow - it took ages to download the file - so I (almost randomly) decided to flash the previous radio again.
I couldn't believe it: that did the trick. (Luckily) I rebooted again, switched on data and 3G and noticed that the phone didn't reboot anymore.
So if you're able to flash a different radio - just give it a try. For the Buzz you need to be S-OFF to flash a radio - no idea about your phones.
I'd be glad if that would work for the Marvel, too :fingers-crossed:
Click to expand...
Click to collapse
Thankyou Eventcom, i will try the method, i am searcing for the Radio to downgrade and upgrade too, i did find a link here in xda will search for that again and see if that resolves my problem, thankyou for the details, appreiciate it

Categories

Resources