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 rooted my Incredible S today from Bell Mobility using revolutionary.io and su-3.0-efgh-signed.zip
It worked as I verified it was S-Off once everything was done. The phone booted fine and everything worked.
I then installed the stable cyanogen mod 7.1 for my model.
The phone then got stuck on the cyanogen boot logo so I rebooted and wiped the cache and formatted the sd card. I rebooted and it everything seemed to work until I tried to make a call. It went through but I'm not getting any sound, I can't hear the person I'm calling and they can't hear me.
I then wiped the cache again and installed virtuous_quattro_rc3_vivo.zip
It installed fine but gave me the same issue, no sound when making or receiving calls.
I've tried doing a factory reset several times but it just brings me back to Virtuous ROM and now won't even find a cellular signal.
I'm new to Android (as you can tell) and just want to get this thing back to stock.
Can anyone help??
Thanks!
christanya99 said:
I rooted my Incredible S today from Bell Mobility using revolutionary.io and su-3.0-efgh-signed.zip
It worked as I verified it was S-Off once everything was done. The phone booted fine and everything worked.
I then installed the stable cyanogen mod 7.1 for my model.
The phone then got stuck on the cyanogen boot logo so I rebooted and wiped the cache and formatted the sd card. I rebooted and it everything seemed to work until I tried to make a call. It went through but I'm not getting any sound, I can't hear the person I'm calling and they can't hear me.
I then wiped the cache again and installed virtuous_quattro_rc3_vivo.zip
It installed fine but gave me the same issue, no sound when making or receiving calls.
I've tried doing a factory reset several times but it just brings me back to Virtuous ROM and now won't even find a cellular signal.
I'm new to Android (as you can tell) and just want to get this thing back to stock.
Can anyone help??
Thanks!
Click to expand...
Click to collapse
Since your Bell IncS probably came Android Froyo, when you installed CM 7, which is an Android Gingerbread based ROM, you need to update your radio from a Froyo Version1 radio to a GB Version 2 radio.
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1129014&highlight=radio
I would try using this one:
http://cmw.22aaf3.com/vivo/radio/20.2808.30.085AU_3805.06.03.03/PG32IMG.zip
So im jimmy. hey. Ive been on this site a while but never post anything. Why? because i can read directions and definitely am not a noob .
Anyways im stuck with my vivid.
I have HTC Unlocked it.
I successfully perm-rooted it.
I also have successfully S-off'd and installed the Juopunut H boot.
As well as sim unlocked my vivid.
I decided i didnt want to mess with any of the kernel mumbo jumbo or roms because i was happy with stock.
But the bluetooth glitch was driving me nuts so i decided to change roms.
I first experimented with a kernel just to see if i fully understood the procedure. Since i was s off i just flashed to CWM but it didnt work.
First, my wifi wouldnt work.
Then i tried the hboot method.
I got stuck in the boot loop. Cleared the cache and everything and nothing worked.
Tried fastbooting and its like it wants to work, it will load up to the preparing apps screen and then freeze on 1 of 8.
I tried flashing the stock rom over the kernel and the wallpaper comes up and the taskbar but thats it.
After that it restarts.
Ive read almost all the threads but no one seems to give a direct answer to this issue.
I REALLY WANT TO AVOID HAVING TO RELOCK AND RUU FLASH.
but if thats what i have to do then i have no choice.
Clearly if that is my only option how do i go about re installing the oem locked hboot?
EDIT:
Ok i got my phone to boot up again by installing the stock deodexed rom. But when i try to install the kernel by faux123 thats when my phone starts acting up.
Note that i am S OFF with the Juopunut hboot and the kernel should work with any rom.
I can flash this kernel through CWM or even fastboot it but no luck
Well ya can't use a different kernel than provided with the ROM for the stock rooted firmware. Extract the boot.img from the .zip and fastboot flash it and then flash the ROM after wiping all the usual partitions.
You should know this stuff if you've been lurking and reading for a while...
Sent from my HTC PH39100 using xda premium
Monkeymannnn said:
Well ya can't use a different kernel than provided with the ROM for the stock rooted firmware. Extract the boot.img from the .zip and fastboot flash it and then flash the ROM after wiping all the usual partitions.
You should know this stuff if you've been lurking and reading for a while...
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Youre right. I was able to do exactly that last night.
Thing is... i decided to go with the raiders rom, flashed it, installed the faux kernel then after reflashed the kernel after the install
via fastboot... it worked last night. wifi and everything.
BUT this morning i go to use my phone and the wifi was stuck yet again on turning on
Hey, HTC one m7 sprint here. Every custom ROM Ive tried either won't instal or crashes seconds after booting to the launcher. Ive tried cyanogenmod, aopk, miui, and used CWM as well as TWRP. nothing works, my backups got deleted and i don't have any ROM that works. any tips to get my phone working again?
cstevenson said:
Hey, HTC one m7 sprint here. Every custom ROM Ive tried either won't instal or crashes seconds after booting to the launcher. Ive tried cyanogenmod, aopk, miui, and used CWM as well as TWRP. nothing works, my backups got deleted and i don't have any ROM that works. any tips to get my phone working again?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2791126
Hello, I have flashed the stock rooted kit kat rom on my phone with sense 6.0. Everything was working perfectly until it suddenly rebooted. I thought it wasn't a big deal, but then it rebooted again after about 2 minutes. Now it keeps going on like this and I don't know what to do, I deleted my backup rom because everything seemed to work as it should. Is there any way to fix this??? I have tried rebooting it when it was still on but no luck!
What radio are you on? You may have to just RUU back to stock and then re-root. Make sure that your radio is up to date.
Andza195 said:
Hello, I have flashed the stock rooted kit kat rom on my phone with sense 6.0. Everything was working perfectly until it suddenly rebooted. I thought it wasn't a big deal, but then it rebooted again after about 2 minutes. Now it keeps going on like this and I don't know what to do, I deleted my backup rom because everything seemed to work as it should. Is there any way to fix this??? I have tried rebooting it when it was still on but no luck!
Click to expand...
Click to collapse
Try updating SuperSU, by flashing this zip in TWRP.