I'm posting here because I don't know what else to do, my phone freezes using any froyo rom. It happens randomly and sometimes will not happen until I reboot the phone, but it makes my phone pretty much unusable. I've tried the leaked froyo rom, BB, CM 6 1&2 and countless others. I've tried wiping data / cache and formating the SD card (worked until i put my music back on), and I'm about to just try stock 2.2 and exchange it for a new one if it wont work.
Anyone else have this problem that could help me?
One thing I didn't see you do...
Have you at all root your phone to install the desired froyo rom for your phone?
Yes I am rooted, I'm currently on CM 5.0.8 and very happy but I would really like to get froyo working.
Alright. This is what I've done to get Froyo working on my Droid: I rooted my phone, downloaded BB v4 and changed the name of the file to update, installed Rom Manager on my phone(then found out I can download the roms from here as well), reboot into recovery through rom manager, wiped data & cache, selected install zip, then selected reboot phone. It took a bit to register but it converted over with BB v4.
I think I've found my problem
droidforums.net/forum/tech-issues-bug-reports-suggestions/67526-music-sd-card-causes-bb-4-freeze.html
this sounds like my exact problem, I'm going to look through my library and see if there is a corrupt file then try again
Hopefully that is the source of the issue and that'll be solved quickly. Good luck to ya
Related
There seems to be a major issue with the 4.06 radio and my phone - every time I have tried to flash it (from both validated .img's and update.zips) my phone becomes extremely unstable afterwards.
It goes into booting loops, hangs at the X, when I get it to boot it crashes while using heavy 3G or WiFi data, reboots when plugged into USB and receiving a call and it becomes almost impossible to get into recovery mode etc, etc.
The only way to get back to a working phone is to revert to stock 4.04. I have tried 5 different times over the last 2 weeks now with the same results every time.
I am starting to wonder if it is a AT&T/Rogers N1 issue or something specific to my device. If it was my device I would think that flashing back to 4.04 would also cause problems but that is not the case. This makes me believe there is there maybe an incompatibility with the leaked Froyo radio.
Appreciate any thoughts/comments.
I'm not having that problem. I flashed Modaco's first FroYo repack with root and the new radio, and things have been fine. To be honest, the only thing I've noticed is that Bluetooth seems to sync a lot faster to the head unit in my car.
Did you do a complete wipe before you installed the update and what applications have you added that may not like the radio?
Edit to add: By the way, you guys have a kick-ass little HTC Magic up there. It may not be a Nexus One, but it more than holds it's own running cyanogen. I have an import that my wife is playing with. I really like it.
Have you tried the 4.6.00.12_7 radio as well ast the 4.6.00.2_2? The 12_7 is working flawlessly for me both on Froyo and on CM 5.0.8-derived ROMs.
I just verified my version - it's definitely the 4.6.00.12_7 Froyo radio firmware.
codesplice said:
Have you tried the 4.6.00.12_7 radio as well ast the 4.6.00.2_2? The 12_7 is working flawlessly for me both on Froyo and on CM 5.0.8-derived ROMs.
Click to expand...
Click to collapse
I tried the 12_7 last night and after flashing it using fastboot, my phone got stuck in a reboot loop. I could get back into fastboot and saw the new radio version on the screen but could not for the life of me get my phone to boot into either the rom or recovery mode - I pulled the battery, took out the SD card etc but nothing worked. This prevented me from flashing a ROM and I could not get into Recovery. After about an hour of trying, I managed to get the 4.04 radio flashed using fastboot and then my phone booted with no problems.
Previously, I tried the various Froyo builds and with no additional apps installed I would still get random roboots when using data via either 3G or WiFi - usually when I try to do something big like downloading/syncing a large file.
This is the story every time I try a 4.06 radio. 4.04 is rock solid.
Have you tried flashing the 4.6 radio via an update.zip as opposed to through fastboot? It's about the only other idea I can think of lol...
Just checked, I flashed the 2_2 last night, not 2_7.
I have flashed the radio via update.zip before and my phone worked but would be unstable. I will have to double check which version I used, could have been 2_2 as well.
codesplice said:
Come to think of it, that's the radio version I'm currently using, and that's where I got mine while I was running his ROM. So yes, flash that zip, flash Kangorama, and you should be square.
Click to expand...
Click to collapse
This is the same radio image I flashed two days ago and it worked for me quite well for an entire day (light 3G use) and then started crashing the phone when I tried downloading larger files (using the Audible app) via both WiFi and 3G in the evening. Once it started crashing I could not get into recovery until after I pulled my SD card. Once it booted OK without the SD card I put the card back and it booted ok again. It would still crash on heavy data use though.
Maybe try the 12_7 radio from http://forum.xda-developers.com/showthread.php?t=692609 ? I'm fairly certain that is the same radio update that I have applied on my AT&T N1.
edit: disregard....
I'm running out of ideas, dude
codesplice said:
I'm running out of ideas, dude
Click to expand...
Click to collapse
I appreciate your input. Thank you. I will try _7 again.
DvTonder said:
This is the same radio image I flashed two days ago and it worked for me quite well for an entire day (light 3G use) and then started crashing the phone when I tried downloading larger files (using the Audible app) via both WiFi and 3G in the evening. Once it started crashing I could not get into recovery until after I pulled my SD card. Once it booted OK without the SD card I put the card back and it booted ok again. It would still crash on heavy data use though.
Click to expand...
Click to collapse
Did you try not running/removing the audible app and see about stability then? What else are you using? Not every app is going to play nice with newer firmware.
attn1 said:
Did you try not running/removing the audible app and see about stability then? What else are you using? Not every app is going to play nice with newer firmware.
Click to expand...
Click to collapse
The crashes started just after I got the Rom installed.
I did the following:
- Nandriod backup (thank goodness for this!)
- I wiped all as per instructions
- Installed radio, rebooted OK
- Installed ROM (Rodriguesstyle 1.6)
- Booted OK into setup
- Configured my phone - first crash just after entering my gmail ID and the syncing of all the apps from the market started
- Rebooted, configured my phone again - apps installed this time but while configuring ChompSMS the phone rebooted again
- Rebooted, phone came up clean, ran OK all day
- Got home and tried syncing Audible content - phone crashed
- Could not get into recovery or boot the phone normally for almost an hour (pulling battery etc did not help)
- Pulled the SD Card and the phone booted, shut down, put the sd card in again, phone booted OK
- Got a phonecall, phone rebooted
- Got fed up and restored 4.04 radio and stock ROM
- Phone stable since
I was running the following apps:
- Autokiller
- Doubletwist Player
- Audible beta
- Silent Sleep
- ChompSMS 4.2
- Switchpro Widget
- Barcode Scanner
- ADW Launcher
- newsRob
- File manager
- Backgrounds
- Rom Manager
DvTonder said:
The crashes started just after I got the Rom installed.
I did the following:
...
- Installed ROM (Rodriguesstyle 1.6)
...
Click to expand...
Click to collapse
What kernel is the Rodrigessstyle ROM using?
Try Modaco's straight up Froyo repack - it has a stock kernel. I'd get as close to stock Froyo ROM/Radio as possible, see what I have and then go from there.
Also, make sure you're using an updated version of chompsms. I think I heard that reports were that it was not compatible with Froyo, but that it's been updated.
attn1 said:
What kernel is the Rodrigessstyle ROM using?
Try Modaco's straight up Froyo repack - it has a stock kernel. I'd get as close to stock Froyo ROM/Radio as possible, see what I have and then go from there.
Also, make sure you're using an updated version of chompsms. I think I heard that reports were that it was not compatible with Froyo, but that it's been updated.
Click to expand...
Click to collapse
I used the stock kernel. ChompSMS 4.1 and later is compatible and I was using 4.2. I am planning on trying the new Kang-o-rama 0.8b1! (CM-5.0.8+2.6.34 Kernel) rather than Froyo - if only I can get the radio to flash.
DvTonder said:
I used the stock kernel. ChompSMS 4.1 and later is compatible and I was using 4.2. I am planning on trying the new Kang-o-rama 0.8b1! (CM-5.0.8+2.6.34 Kernel) rather than Froyo - if only I can get the radio to flash.
Click to expand...
Click to collapse
Why not start with FroYo - the ROM the radio was meant to work with - before flashing anything else? If it doesn't run then, you have a real problem. otherwise, you have no idea where the problem is.
attn1 said:
Why not start with FroYo - the ROM the radio was meant to work with - before flashing anything else? If it doesn't run then, you have a real problem. otherwise, you have no idea where the problem is.
Click to expand...
Click to collapse
Point taken. Back to the basics.
I came straight from Rodriguesstyle 1.6 with the included add-on OV/UV kernel to Kang 0.8b1 without any issues. Even got the 720p hack working beautifully
well i am using the new froyo radio with my ATT nexus one, and its been no different than the old radio. no crashes or anything. however, i had NO idea that there were 2 froyo radios. is that what someone just posted on the first page?
I have had a simmilar experienc, but it is NOT froyo related.
I was rooted, on the desire ROM
It was restarting at seemingly random (and frequent) times through the day -
I reflashed to stock 2.1.
During setup, phone rebooted.
Got through sign-in. Installed some apps. Phone rebooted.
Phone was absolutely fine, as long as I didn't touch it. I would use it - browse, etc. Seemed to be fine. Would then reboot. FLashed it up to froyo. Same.
I think it's the bad RAM issue i've seen reports of, but I'm not sure. Sent in for a replacement.
Let's hope that's not OPs issue, though the problem seems to be pointed in that kind of direction. Hope you get your situation resolved under warranty.
chordmasta said:
I have had a simmilar experienc, but it is NOT froyo related.
I was rooted, on the desire ROM
It was restarting at seemingly random (and frequent) times through the day -
I reflashed to stock 2.1.
During setup, phone rebooted.
Got through sign-in. Installed some apps. Phone rebooted.
Phone was absolutely fine, as long as I didn't touch it. I would use it - browse, etc. Seemed to be fine. Would then reboot. FLashed it up to froyo. Same.
I think it's the bad RAM issue i've seen reports of, but I'm not sure. Sent in for a replacement.
Click to expand...
Click to collapse
i have had my ATT N1 for a few months now and all has been great. I rooted awhile back and have been using Cyanogen 5.0.7 to great success. I have the pershoot kernal and never really had any issues.
Well, that has all changed. Recently I have been rebooting any many different occasions. It almost always does it when I am in Maps and navigation, which is not good because I need it in my life having relocated.
I have decided that maybe I will look to update my Cyanogen or maybe go over to 2.2. I did this today and still having these issues. I tried Kang and it still rebooted randomly and when I tried Modacos r17 it just would keep rebooting at the setup screen. I think that has to do with not having the stock kernal.
Any clues as to what is happening? I really need help and do not want to stop using Android, but I need my phone to be reliable.
If it happens on any ROM and with no correlation to anything - sounds like HW problem.
Did you use overclocked kernel?
I do have a overclocked under volted kernal
sounds like bad sw. get back to stock 2.1 update 1 (if you can) and see if your phone is stable...
WIPE all ( everything ) , and flash 2.2
http://forum.xda-developers.com/showthread.php?t=692609
Follow those 3 easy steps there !
Does your phone lock up (unresponsive) before rebooting?
Phone doesnt lock up. I tried wiping evertyhing but could not wipe the sd partition. Is that necessary? I have done full wipe's (data, dalvik, & cache) and still had similar results. I have updated my kernal to the newest pershoot and I installed Kang .9b1 and so far have only had 1 rebbot. It happened when I was in the browser and went to a flash heavy site to see how it worked. Is there any 2.2 roms that keep it close to stock? I am not a total fan of adw launcher.
Have a look in this thread,
http://forum.xda-developers.com/showthread.php?t=703687
I'm really determined to figure out what is causing this issue for so many people! I've managed to cure my reboots for the time being, and it seems it is kernel related. That said, we need as many people as possible to give feedback as experiences seem to differ in regards to the ROMs and Kernels people are using.
Regards.
I looked over that thread and see some similarities but it is still not totally consistent with my issues. I am running Kang now fine but still have reboots that I won't call so random anymore. It happens when I use Maps for the first time, and definitely when I go to a flash site on the browser.
I cannot successfully use any other ROM since once I install it it goes into boot loop. This is driving me crazy and do not like the thought of being stuck to one ROM since it is the complete reason I bought this phone.
I curently have a bell i9000M I was running Doc's JPY for a few months but decided to his JS8 version the other day. As soon as I flashed it I noticed my phone was unable to install apps and in manage applications it gets stuck on computing.
So things I have tryed to get this working again........
Flashed EZbase using re-partition , still same issue on base.
Flashed Stock JH2 , still same issue.
Flashed Stock JL2 still same issue.
Flashed JH2 then JL2 through Kies same issue.
It seems I can not write to my internel SD although the rest of my phone seems to be working fine any Ideas?
Another thing I noticed is mass storage is not working on any rom only can connect using Kies method if I want to transfer files. Format internal SD is not working , it asks if you want to format you click yes it seems like something happens but then check the internal sd and all the files are still there.
I am not familiar with the I9000M but i know its very common to have SD card failures.
And it seems to me thats whats happened, im sorry for you
best thing you can do is, flash back to stock and send off for repair, hopefully you may get some luck with the next device.
One thing before you get all emotional have a look at this, its a long shot but......http://forum.xda-developers.com/showthread.php?t=905975
azzledazzle said:
I am not familiar with the I9000M but i know its very common to have SD card failures.
And it seems to me thats whats happened, im sorry for you
best thing you can do is, flash back to stock and send off for repair, hopefully you may get some luck with the next device.
One thing before you get all emotional have a look at this, its a long shot but......http://forum.xda-developers.com/showthread.php?t=905975
Click to expand...
Click to collapse
Yea I was not getting any mounting errors in CWM or 2e/3e recovery...Anyway after a frustrating 3 days I now and I think it's finally working , so far.
I manually deleted all files off the internal SD, then did a format from within 3e recovery while on JL2 (this was acting like it was formatting before but all the files I downloaded were still there after the format). Then flashed Hardcore's K13 and installed a custom rom all seems fine so far but it did work periodically over these past few days so I'm hoping it stays working now.
What was weird is I could download files using the web browser but the market would not work all the time but when it did it was downloading the items but would just get stuck installing them.
Anyway thanks for the quick response. Hopefully I have this sorted out now.
Hi all,
I've done a search on this (both XDA-wide, and Google) and no-one seems to have a valid answer for me yet.
I am running Gingerbread (PDA = XWJVB, Phone = XXJVK, CSC = XAJVK) via a Doc's beta RomKitchen build. I am aware that I am running a beta and things can get a bit hairy, but this problem is really annoying.
Basically after the rom flash, I went and got Titanium Backup working again, and started restoring my favourite apps and widgets. All worked fine, then I had to do a reboot for some reason. All the restored apps are still in the apps folder , but greyed out and with an SD-card image overlaid to tell me they are on the SDCard. They ALL no longer work but give the "application is not installed on your phone" error, which is annoying, because before the reboot, they all worked.
I have tried twice to restore them from Titanium backup, and each time they only work until the next reboot breaks them, meaning the only apps I get to keep are the system apps and the ones I cooked into the Rom.
Anyone have any ideas?
Anyone at all?
Hi, I had a similar problem, with one difference: it started after a while. I had Doc's JVK installed, I restored my apps with Titanium Backup and it worked flawlessly for a while. At some point I noticed that the apps installed recently would disappear after a reboot. The worst thing is that even the market disappeared at some point.
To solve the problem, I flashed several times a WIPE version of Doc's rom along with several wipes from recovery. It didn't work right away and it took me several reflashes.
No problems since then.
Cheers
Thanks for that.
After much reading, I reckoned it was probably the Fugu kernel doing most of the damage, so I flashed a Chainfire XWJVB kernel, then a recooked Doc rom without the Fugu kernel. Lubberly Jubberly now
Posted this in the wrong place... so here I go again.
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/show....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
edit:
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)
Alright. I'm trying my very best but I'm really clueless right now.
After not getting this wifi to work I tried the COS-DS mod. Installing it and everything went fine, except for one thing: the settings menu would not open.
Not being able to do anything on that I went on to the next to the next rom: Cyanogenmod 7 Magpie. Once again, most things work, but some do not. I started out with an input.latin error, which I somehow fixed. I do not have a status bar, and I think I'm missing some other things too... for example, the android market does not appear. Wifi does work now though.
I have no clue what's going on... do I just need to start over from scratch? Trying Froyo again? I could really use some advise.
Noddahead
Have you tried wiping properly before flashing the new roms because I've never had a wi-fi issue unlees it was broken in the kernel which is rare these days.
Thank you for replying.
I am back to Froyo by Laszlo now, seems the best option. Before installing that I wiped cache, wiped data/factory reset, and I used Ohsaka Superwipe. But no Wifi.
Using another Kernel with Froyo by Laszlo did not help.
Well, last update here. Never got it to work, now having succes with GingerYoshi. This topic can be locked.
try everything???? re partition and re format sd card, try ezbifftest 2708 kernel, i had best luck with laszlo rom
First of all, thank you for your guide.
I had not actually partioned before installing froyo, and I did partition before using Ginger right now.
If I would repartion right now, and then reformat... can I then instantly install froyo laszlo and the kernel? And what values for the partioning?
you can flash a rom whenever you want, as long as you wipe all data from previous rom or mod first,so i would repartition to this
96-128mb=swap
512mb=ext
than flash the ohsaka superwipev2, power off device than reboot back to recovery.
flash the rom you want and enjoy!!
re-partitioning/re-formatting does not have to be done everytime.. it's just good to do every once in a while because you never know what could be happening in there... you or a developers rom could have done something somewhere that caused a bug in your sd partitions so its always good to wipe them at some point...
the ohsaka superwipe i do reccomend using everytime!! I also recommend wiping it manually sometimes... also another good known method is a fastboot wipe 'i forget the cmd for it' lol but do these every once in a while...
Did exactly as you said, unfortunately I still get the same problem: Cannot scan for networks.
I will stick to Gingeryoshi for the moment.
Thank you for your time and help.
wow, thats a bummer... i never had that issue with laszlo's rom at all... i wonder what could be wrong. sorry i couldn't help.. just out of curiosity what device do you have? is it a dream or magic?
possibly if you are using a magic, you may need a kernel with wlan.ko modules included for the specific kernel(would be icluded in kernel.zip file)... different kernels wont work with different drivers...
It is a Dream