I'm crazing
Since i try to install a Froyo ROM with new radio (32.42.00.32U_5.09.00.08, all 2.2 ROMs requires this radio), how i connect to 3G the phone go continuosly in random restart.
I'm on Vodafone and the only ROM that works fine is the stock ROM 1.21.XXXX
Before installing a ROM i make all wipe. But never good.
What i must Do ?????
I am having the same issue. All new radio (for 2.2 froyo) will cause random reboot during 3G usage.
The easiest way to reproduce the problem is to keep browsing google map for a few minutes.
Flashing froyo custom rom with old radio (4.06.00.02) does not have this issue, but losing camcorder features...
Anyone idea for this?
Hi all,
I own a Desire GSM version and been running a pre-rooted stock ROM for quite a while and have been very happy with it. I have been running this with an ext3 partition and ran app2sd+ script to make use of it. All good.
My sense of curiosity got stronger and always wanted to try a custom ROM so I tried Cyanogenmod 7 RC1 on Monday.
I have been running the latest Radio (32.49.00.32U_5.11.05.27) so didn’t have to update that for CM7.
I formatted the DATA as well as the CACHE before flashing the CM7 ROM, then applied GAPPS to the ROM then restarted the phone.
All went OK and I loved this new ROM, except that I have been experiencing very strange connection issues whether I am on WiFi or 3G (Vodafone AU). The phone will establish connection; however sometimes will not be able to get data out of a request as simple as getting emails, opening a webpage through the stock browser etc …
The workaround to that was to tun off wifi and turn it back on, same for 3G …
I re-flashed numerous times the ROM (formatting the CACHE/DATA each times) but was still experiencing these issues, when sometimes I couldn’t even set my Google account at the first start of the phone…
After a couple of days of scratching my head I did find a potential solution that was suggesting updating the /system/lib/libhtc_ril.so file with the one provided in the nightly build. This had no effect what so ever to the situation.
I then decided to go back to FroYo () so re-flashed the pre-rooted ROM, but then I experienced the exact same issue!! I then re-flashed the Radio ROM thinking this may have been affected by all these changes but no changes at all …
I am a bit at a loss here and don’t know how to fix that really …
Is there any setting that resides on the phone relating to Radio ROM even if I format both Data and Cache each time I flash the ROM??
Thanks for your help guys.
Any ideas on this issue at all ??
I've been using my desire for about 1 year now and never had any problems until I decided to go back to Leedroid gingerbread rom and install the patches for A2SD+ with ext 3.
I was having restarts every 10-15 minutes on Leedroid, went back to CM7, currently on cm7 7.0.2 and I'm still getting restarts when I wasn't previously.
I have asked this question before and thought it was an issue with the SD card. Now the reason I thought it was the SD was when I was having loops of restarts I would take it out and it would be quite stable for a while. Formatted everything (SD and internal + cache) put on the latest radio rom and then put on the latest CM. Seemed to run fine for a while and then started restarting again. It locks up on the HTC screen occasionally and requires me to pull the battery.
I've noticed that it only happens when I'm using 3G internet connectivity. Just recently it tried to get a lot of updates and would start downloading them only to restart. It does eventually get the updates though.
To test this I can start watching a youtube video and it will crash. For example I just watched 1 minute of one video before it crashed, after reboot I started youtube again and it crashed immediately.
Can I stop log cat removing all the logs when the device restarts so I can have a look what's going on? Any other ideas on how to diagnose or fix would be much appreciated.
What's your radio?
My Radio version is
32.56.00.32U_5.17.05.23 and I'm running CynogenMod 7.0.3
I used something else before I switched to leedroid an old one, I changed it to go to Leedroid then changed it to this hoping it would help.
Flashed newest correcspondig ril 2.2.1003G?
Thread for radio/ril here on xda:
http://forum.xda-developers.com/showthread.php?t=902752
No I have never flashed a RIL before, didn't even know what these where. I'll give that a shot and see what happens.
DeliveryNinja said:
No I have never flashed a RIL before, didn't even know what these where. I'll give that a shot and see what happens.
Click to expand...
Click to collapse
RIL (by System of a pWne!^)
Radio interface layer. This is a layer between the Radio and the ROM. It communicates with the hardware over the Radio and supplies an interface for the ROM so it can use the hardware. This is similar to a driver.
Whenever you flash a new Radio, you should also consider flashing the corresponding RIL for it. This makes sure, the Radio is getting adressed correctly.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=805247
I was running the RIL suggested above yesterday, had about 11 hours and no issues, updated all my apps, was watching youtube etc.. I was trying to do stuff that usually would make it crash. Eventually I turned on my wifi at home and as soon as it came on the phone rebooted. It then proceeded to reboot every time I tried to go on the internet, with either 3g or wifi, I tried about 3-4 times. Leaving it with internet off for about 30 mins, I came back to it and it started working on wifi fine. Strange. TL;DR ril didn't seem to fix it. Seems like if I can get it back to stock I can go to the shop and change it.
Well, this sucks. Upgraded from the Hero to the Desire Z 1.5 weeks ago. Downgraded it, rooted it, tried out a few ROMs, settled on Virtuous Unity and all was happy.
I used the phone in the car this morning as a GPS, 3G data connection was working fine, etc. I had a couple of client meetings, after which I pulled out my phone to check for messages. I noticed there was no mobile signal at all. I figured it was building interference, so I went outside. Still nothing. Wifi was working fine, GPS was working fine. I enabled airplane mode, then disabled it again to see if that would kickstart things. Still no go.
I decided then to power cycle the phone to see if that would help. It went through the usual reboot cycle, displayed the lock screen, then the SIM unlock screen. Then no matter what I do or don't do, about 5 or 6 seconds later, the screen suddenly goes black and the phone reboots.
Now it just does the same thing over and over again. The phone boots up fine, displays the lock screen briefly, then the SIM unlock screen, then it crashes and reboots. Whether I unlock the SIM or not doesn't matter. Within 5 or 6 seconds, the phone will reboot. I can see notification icons popping up, so everything appears to be working fine otherwise.
I have not changed anything on the phone this morning: it was sitting in my pocket the entire time. Same ROM, same radio firmware. I restored last night's nandroid backup just in case, but it didn't help. I thought perhaps it was VU's built-in overclocking that wasn't agreeing with the phone, so I restored a MIUI-based backup. No go. I went all the way back to the stock (but rooted) Bell Desire Z image I took when I first got the phone. Still no go.
I've tried booting up without the SIM card, and without the SD card. Nothing works. I'm guessing the phone suddenly developed a hardware problem. It would be something that is triggered soon after the OS has successfully loaded. Maybe something to do with the 3G radio?
There are no obvious errors or kernel panic messages in logcat. Everything appears to be proceeding normally, until it just comes to a dead stop. Anyone have other suggestions I can try?
Search this forum for "boot loop" and you'll find some things to try.
Thanks, burtcom, but none of the threads I checked apply here. Other boot loop problems more often have to do with the phone rebooting while the boot animation is still playing. My phone successfully boots and is in the process of loading user apps when it crashes. Also, most reports come as a result of something attempting to root their phone and then installing a ROM. I've already made it past that stage. I am able to boot into CWM, do my nandroid backups and restores, etc. The ROMs have all been working fine up until some point this morning. The fact that several different ROMs now all have the same problem makes me suspect a hardware issue.
Moved my SIM and SD card back over to my Hero, and everything works fine there, so I strongly suspect some hardware just broke on the DZ this morning. I'll try flashing a new radio firmware, but I can't see how that would fix anything, since the old version was working just fine all along.
taob;15238893I'll try flashing a new radio firmware said:
Huh... so I flashed the latest Bell Canada 26.06.02.25_m2 radio.img, (up from my old 26.03.02.18_m3 firmware), and now the phone no longer crashes. I'm thinking maybe it isn't an issue with old vs new firmware, but that the old firmware was somehow corrupted during the course of the day. Re-flashing the original radio probably would have worked too, but now I have the latest one...
Hopefully this will help someone in the future with the same problem.
Click to expand...
Click to collapse
The phone no longer reboots, but I still had the problem of not picking up any signal whatsoever (voice or data), even though wifi and GPS work just fine. APN settings were verified to be correct. It turns out I had to go into Settings -> Wireless & networks -> Mobile networks -> Network operators -> Search network and manually re-register my phone on TELUS. Bizarre.
I had the same problem, update your radio and flash this zip on the Unity Thread
"For people experiencing random phone Freezes, this is due to overclocking, it's solved by lowering max speed.
Just flash this patch over: (link is on the thread)"
That's a different kind of problem, sengalang. My phone was working just fine overclocked to 1.2 GHz for over a weeks, so why would it suddenly start crashing like this? Problems due to overclocking tend to result in reboots at random times, and not at 100% predictable times like my problem. I did also boot with the MIUI and stock DZ ROMs, which do not overclock... same problem. Thus the root cause was not CPU speed.
I have massive problems using WiFi.
If I activate it, the phone spontanously "crashes", means it reacts extremely slow and is totally unusable till restarted.
It's always when WiFi is on, just the time till it starts differs. I've tried some different ROMs (MIUI with LordMods kernel or stock kernel with vanilla ROM-settings and no apps, CM7.1 stable with stock kernel) and also different WiFis and settings and can say it's independent from an established connection, so it also occurs when there is nothing in sight to connect to.
I can't remember since when I got this problem as I only recently activated WiFi again for usage. Before I never had such problems. I accidentally flashed a zip file as a radio some time ago o) and then flashed the right radio again after I got the battery out for some time. Possible the phone got damaged somehow or is there a possibility that it's a software related issue like a module that doesn't work well with more recent radios in combination with my phone?
I tried radios 12.59.60.26_26.11.04.21_M and 12.62.60.27_26.13.04.19_M, same problem.
Thanks
See if the official software works, try to install a 1.32 RUU.