Database Develop

4.06 radio and AT&T/Rogers phone incompatibility?

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

Constant rebooting

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.

Having issues with overclocked ROMs

Any help on this would be greatly appreciated! I have flashed just about every single ROM on XDA and have never run into any issues, besides obvious bug within each of those ROM's. But since all of the .29 overclocked kernel ROM's have been popping up I have had nothing but problems with them. I have tried Darchdroid v2.7 and Buffed 2.0B and on each of those after flashing I either get stuck at the HTC screen or it gets stuck in an HTC screen boot loop. One thing I did notice was that after multiple battery pulls I can sometimes get Darch's ROM to boot, but every time I power off or reboot I get the same thing. I have done all the normal stuff that you guys tell all the n00bs, I have wiped EVERYTHING (Factory Reset, Dalvik, and EXT), I have tried booting up wih no SD card in, repartioned SD (with and without EXT), nothing seems to work. I have flashed back to DamagedControl and Fresh with no problems. Obviously there are people here using these ROM's on their Hero but for some reason mine does not like them, are there difference between Hero's based on when their purchased (different chipsets, ect.)?

Try using regawmod with darch's kernal for honeybun, that combo seems pretty awesome for me.
Just search the development forum for them.
Sent from my HERO200 using XDA App

neuro_genesis said:
Try using regawmod with darch's kernal for honeybun, that combo seems pretty awesome for me.
Click to expand...
Click to collapse
I am not a fan of the look of Regawmod, it looks to photoshoppy for me.

Kernels causing reboots? Or is it something else

When I was on DocRambone's 7.5 JPA with the older ReOrient kernel 2.1.1 I never had soft reboot problems and then it seems I started getting them after a lot of the Captivate kernels started incorporating these small tweaks.
After reading a lot of other posts other people have been having this same problem but we have no idea what is causing it. At first I thought it was one of the tweaks that you enable in the new recovery ULF tweak section but after disabling all those tweaks and doing a factory reset I was still getting them.
I tried a very untweaked setting with haptic feedback and only bln (no lagfixes, etc...) and it still happened.
Has anyone been able to find the culprit? I've tried 2 different kernels: Reorient and SetiroN's.
When I have my phone in my pocket and I'm driving I'll randomly feel haptic feedback even though I dont have a call or text and shortly thereafter I'll get 2 small vibrations and then a reboot. Once it reboots it seems to come back up for a few minutes and reboot again. I was using ChompSMS with BLN and haptic enabled and that was pretty much the only things I changed from stock.
P.S - The purpose of this thread is to put a collaborative effort in finding out WHY our phones are restarting for some unknown reason. As this community and devs grow, sometimes problems like this arise.

I have seen a few post about the reboots. I have never had any with the kernels. Its kinda strange some of us dont have the issue.

there are several reasons for soft reboots.
if you are running an i9000 rom with a captivate modem, you will get them
if you are running an i9000 rom with a particular modem that doesnt work in your area, you will get them when the modem tries to hand off between towers.
you can get them from oc/uv, bad framework hacks, bad rom, etc. it is all circumstantial, it all depends on what changes you have made from stock....

Pirateghost said:
there are several reasons for soft reboots.
if you are running an i9000 rom with a captivate modem, you will get them
if you are running an i9000 rom with a particular modem that doesnt work in your area, you will get them when the modem tries to hand off between towers.
you can get them from oc/uv, bad framework hacks, bad rom, etc. it is all circumstantial, it all depends on what changes you have made from stock....
Click to expand...
Click to collapse
The DocRambone 7.1 and 7.5 I9000 ROM uses the JPP modem if I'm not mistaken, and I never had reboots. It wasn't until I went to reorient kernel 2.1.2 (or 2.1.3 can't remember) that these reboots occurred.
Right now I'm doing Doc 7.6 MikeyMike01 with JG8 modem and SetiroN 1.2. I also had a previous setup of using JPP and a different rom with both kernels and had reboot problems.
If the modem is somehow causing reboots I may go to the stock captivate modem and see what's going on.
So far in my apartment the phone has not rebooted by itself (has had a constant HSUPA connection). I'm also running the ROM stock without recovering any of my apps. When I leave here soon I'll see if my phone restarts. If it does, then it would appear a modem issue may be at hand.

smokestack76 said:
I have seen a few post about the reboots. I have never had any with the kernels. Its kinda strange some of us dont have the issue.
Click to expand...
Click to collapse
What type of setup do you have?

LinuxNewb said:
What type of setup do you have?
Click to expand...
Click to collapse
Cog 2.3b modded with setiroNs kernel. No oc/uv enabled, Using the jpp modem with Hsdpa working.

For some reason clearing dalvik cache and fix permissions in recovery did it for me..i haven't reboot since
xdaApp via Captivate

darkamikaze said:
For some reason clearing dalvik cache and fix permissions in recovery did it for me..i haven't reboot since
xdaApp via Captivate
Click to expand...
Click to collapse
If my phone crashes ill try that and see if works. So far at home it's been perfect.

LinuxNewb said:
If my phone crashes ill try that and see if works. So far at home it's been perfect.
Click to expand...
Click to collapse
That makes me think modem.

smokestack76 said:
That makes me think modem.
Click to expand...
Click to collapse
why is that .. ? soft reboots did only happen to me when I wasn't home lol

darkamikaze said:
why is that .. ? soft reboots did only happen to me when I wasn't home lol
Click to expand...
Click to collapse
as i stated earlier, the soft reboots usually occur due to modem/rom incompatibilities when the modem is trying to hand off from network to network.
this was a part of our experiments with the ji6/jpk roms that boomerod, shep, and several others were testing. it has to do mostly with the 850mhz frequency.

interesting.. well i'm on JPP right now.. so far stable

darkamikaze said:
interesting.. well i'm on JPP right now.. so far stable
Click to expand...
Click to collapse
i am on jpp right now also, and am about to go for a drive to make sure its completely stable with the handoffs.

I remember one time i did a certain combination of install rom, restore apps and apply jfs lagfix and a popup came up that said i had mismatching uid's and that i had to format /data directory.
Sure enough soft reboots all.over the place after some fc's.
I found that the best way to use the lagfix is to restore apps b4 lagfix and activate the tweaks at the same time as the fix. It works for me
Sent from my GT-I9000 using XDA App

The JG8 modem for me in Shep's ROM causes frequent soft reboots. As soon as I get rid of it, problem solved.

fatttire said:
The JG8 modem for me in Shep's ROM causes frequent soft reboots. As soon as I get rid of it, problem solved.
Click to expand...
Click to collapse
Ya... as soon I started driving my phone would restart. When it's at home nice and solid connection theres no problem lol
So if we narrowed it down to a possible modem issue lets start testing which ones work.
Fatttire - If you could attach the modem you're using so we can try it out that'd be cool did anyone play with the combi bands or any other settings within the service mode?

tytdfn said:
I remember one time i did a certain combination of install rom, restore apps and apply jfs lagfix and a popup came up that said i had mismatching uid's and that i had to format /data directory.
Sure enough soft reboots all.over the place after some fc's.
I found that the best way to use the lagfix is to restore apps b4 lagfix and activate the tweaks at the same time as the fix. It works for me
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I didn't even restore apps or do any lagfixes and I'm having this issue Good to see yours worked for you though. Hopefully we'll find a modem thats compatible with this JPA/JPP setup.

I've only used stock modems on our two captivates - occasionally they will restart out of the blue.
Once in particular I think it was because of a live wallpaper. After disabling it, everything seemed smooth running again. I just use plain black wallpaper and mine never reboots.

K-mart Shopper said:
I've only used stock modems on our two captivates - occasionally they will restart out of the blue.
Once in particular I think it was because of a live wallpaper. After disabling it, everything seemed smooth running again. I just use plain black wallpaper and mine never reboots.
Click to expand...
Click to collapse
Ive done so many weird configs of roms/firmware/kernel/custom frameworks and I've never had an issue with reboots. I ran a 2.1 i9000 setup with HSUPA and that never ever reset on me.

JG8 is only to start with to enable 850
fatttire said:
The JG8 modem for me in Shep's ROM causes frequent soft reboots. As soon as I get rid of it, problem solved.
Click to expand...
Click to collapse
The JG8 is an Eclair modem, not Froyo. Its purpose is to use at the beginning of an install from stock JF6. Once you have the rom and kernel you want, you need to replace it with a Froyo (suggest JPP) modem.
Don't leave yourself running a Froyo (i.e. Shep) rom with an Eclair modem, you are just asking for trouble.

[Q] NESOID and SNESOID won't run? Please advise.

I recently rooted my old G1 and installed Cyanogen 4.08 (or whatever that gen is) and along with the new 8 gig card have room to install apps. One pair of apps I had pre-rooting and flashing was NESOID and SNESOID which I had to get rid of due to room. Now I reloaded them with the old roms I had and tried to run them and lo and behold they don't run....but they did before!
The software loads and I select a ROM (still zipped as usual but I tried unzipping just in case) but when I hit a ROM it goes black for a second then returns to the load screen. Trying all the ROMS gets the same result.
In the task bar i see the icon of NESOID (or SNESOID...I tried both) and it says "NESOID is Running" and if I pull down that screen and hit that it goes back to home screen and stops. No force close or anything. Just nothing.
Any ideas? I tried cachecompress on and off and that's about it. Can't think of what else to do. Is it Cyanogen?
Thanks!
fil

You should try running gingerbread or some of the newer froyo builds with new spl/radio hack to run those emualtors, you'll see about a 30-45% performance boost when playing them imo. I've tried both Sparksmod 1.6.2 and gingerbread cos and both roms ran emulators very well.

d12unk13astard said:
You should try running gingerbread or some of the newer froyo builds with new spl/radio hack to run those emualtors, you'll see about a 30-45% performance boost when playing them imo. I've tried both Sparksmod 1.6.2 and gingerbread cos and both roms ran emulators very well.
Click to expand...
Click to collapse
I was thinking about this but I was wondering why it worked with the factory build of 1.6 but not the suped up (for the time) Cyanogen build of 1.6? I was thinking of flashing one of the newer builds (I already have the new radio) but was always hesitant. Will gingerbread run on an old hoopty of a phone like the
G1?
Thanks!

You'd e surprised how well gingerbread is running on the OG g1
http://forum.xda-developers.com/showthread.php?t=950765
i have been trying out almost every new releasd build for that rom and its getting better imo, heres the direct download for rom with gaps and themes pre installed..
http://www.multiupload.com/5RNO8BZHTZ
make sure you read thru the thread first though to avoid and semi bricks.