I have installed Myn’s Warm Donut on my Kaiser with the stable kernel from atools and it was working just perfect. Also i installed the [email protected] update from Millence. System and data on Nand.
I have installed several applications and just configured the options of the phone and it started restarting. Sometimes 2-3 restarts before it continue loading. The battery shows 45%. And sometimes everything is working just fine and me just touching the phone to take it, and restart....
Already several times happened after several restarts like this all the data was lost.... and everything from the beginning.
Please give any advice!
PS. I'm using Donut because it is the fastest version
Same thing with me. Im running .32 on nand with froyo and it happens.
It also happened with myns as well. Something to do with data on nand I think.
If data is on sd partition i dont get the phone flushed but still sometimes restarting and the phone is sooo slow and often not responding
Once i got a message for missing and/or incorect UID after the restart and the phone was flushed. Immediately i restarted and Fixed the permisions, everything was ok after that, just like before. And today after installing one application and little useing after that i got a restart and everything was flushed. Fixing the permisions gave an error. Please help, how to fix this issue. Thanks!
Check if it those restarts are happening if your data connection or wi-fi is off. If not, turn on gps first and then your data/ wi-fi. Working for me
same problem for me
Related
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.
Hi,
I installed Gingervillain 2.8 about a week ago and everything ran perfect.
Than for some reason(?) I rebooted my Desire and it got stuck on the Gingervillain boot screen. I than wiped the cache and the dalvikcache some times and even once reinstalled the rom (without wiping the data).
Eventually the phone booted and I could login, everything seemed to be ok.
But after a bout 5 minutes playing (mail, tweedeck, gallery...)the phone frooze. Rebooted, wiped caches, same thing..
In the end, I did the same, hooked the phone to the charger and went to sleep.
In the morning everything seemed to be working fine so far....
Any ideas what can cause this or how I can investigate this?
Jan
Did you flash/install anything (kernel,...)? Are you using SetCPU? (maybe you overclock it - can cause freezes)
No, I did not change anything compared to the default settings.
But indeed, it looks like something changed that was activated by a reboot.
I remember I tried to restore the HTC Weather widget with Titanium, but that failed. Not sure if this could have caused this. Sometimes a downloaded app does not work anymore (had that with whatsapp/googlemaps), remove and re-install fixes that.
Reboots now seem to work. But still an occasional freeze.
Is there a way to investigate this? I can connect to the Desire with putty....
Maybe you have a nandroid backup you made after the first time you flashed gv2.8?
And try if you have the same problems then?
Hans
Indeed I have a nandroid backup, made quite recent after the first install.
But first I want to see if this can be solved otherwise.
Using this backup will require to install a lot of apps again.
Unless I get a 'golden' tip here and I do not get too many freezes, first steps will be:
- getting a > class 4 micro sd (not sure what I have now)
- If that doesn't help, use the backup.
Hi,
I am having a really odd and very frustrating issue with the latest CM7 Stable Build on my device.
I have been using the latest stable since its release back in November.
I ensured a clean wipe and install of CM 7.1.0.1 and setup my phone accordingly and Nandroid Back Up around a Week later as the Device was behaving as intended.
Sadly, I am now plagued with the following issue which occurs without any common trigger....
I will be using the device which will be behaving normally and it will suddenly, normally when screen is off... reboot and enter a Boot Loop (CM7 Robot will either be frozen solid or will keep rebooting to CM7 Robot) which seems to continue until a battery pull.
I will then restart the device and it sometimes boots straight away though sometimes hangs for a while. Once booted it boot to the 'Setup your device' Screen, from which point onwards you are required to Re-Enter your Logins for Google and such like. All settings and sync profiles are normally missing/deleted so requires setting up of all apps requiring logins etc.
As you can imagine, the above is quite an inconvenient as it normally happens when I actually need to use the device
I have tried reinstalling a clean CM7 over the top as well as wiping and formatting the SD card.
Neither seem to have solved the issue.
Any help anyone can give would be greatly appreciated.
It is also worth noting that while the device will charge off USB, it will not allow usb tethering or any form of USB Mounting etc.
Cheers
Jason
Device Spec:
Phone: HTC Wildfire Alpharex S-Off
Android: 2.3.7
OverClocked: 518.4MHz-691.2MHz (SmartAssV2)
VM Heap Size: 24m
ROM: CyanogenMod-7.1.0.1-buzz
Radio: 13.55.55.24H_3.35.20.10
Recovery: ClockworkMod 2.5.0.7
Kernel: 2.6.35.14-nFinity arco(at)tuxbox #1
Custom MTD Partitons using S2E
cm7 issues.
sounds like your in quite a pickle my friend.
i used to get your reboot issues (the bootloops) but that was because my phone was overclocked to over 700. i never got the setup device screen though.
when you say youve tried a clean install over cm7 have you factory reset the device as well as deleteing the dalvik cache??
also my sound stupid but have you tried your backup to see if it starts again??
it sounds like something has became quite corrupted.
have you installed any new apps recently or changed anything in the system files of the phone?
also when you have to go through the set up are all your apps still there afterwards? And when you first flashed it did the tethering work at all?
Heavy_metal_man.
heavy_metal_man said:
when you say youve tried a clean install over cm7 have you factory reset the device as well as deleteing the dalvik cache??
Click to expand...
Click to collapse
Yup
heavy_metal_man said:
also my sound stupid but have you tried your backup to see if it starts again??
it sounds like something has became quite corrupted.
Click to expand...
Click to collapse
Yup and while it does restore to a point where I can use my phone quite quickly after however I'm very cautious after - typically it happens a couple of weeks later
heavy_metal_man said:
have you installed any new apps recently or changed anything in the system files of the phone?
Click to expand...
Click to collapse
No real new recent apps installed and no mods to the system files that I can recall.
heavy_metal_man said:
also when you have to go through the set up are all your apps still there afterwards? And when you first flashed it did the tethering work at all?
Heavy_metal_man.
Click to expand...
Click to collapse
All my apps are still installed but many apps require re-setup or accounts for sync require re-adding. Phonebook requires import of contacts however messages remain in place.
I can't recall I think it did or at least USB-Storage did
Do you have a SD ext partition?
I ask because I had similar problems (randomly losing data) with an ext 4 partition, repartitioning my card using ext 3 solved it, also put your dalvik cache and data back into phone memory if it isn't already as that can also cause instability.
Sent from my HTC Wildfire using xda premium
Try this....
Run an RUU for wildfire.
- Download (RUU_Buzz_HTC_WWE_1.14.405.2_R_C_Radio_13.45.55.24 _ 3.35.15.19_release_141106_signed) from android forums.
- Connect phone to PC and run RUU
- This downgrads phone OS to eclair (android 2.1)
- Let it do the bizniss
- Re-root with unrevoked 3
- Re-Flash CM7 and gApps
Many thanks Scratch and Arkose,
Since my post last week I have since formatted the SD Card as well as Wiping the Phone as much as possible.
I then flashed and installed the latest CM7 Stable, Radio Package as well as re-setting up the EXT Partition this time as Type 3.
Once up and running I reinstalled all Apps.
Seems to be running okay so far.
Long may it last hopefully.
If not will try last suggesion
Great stuff. Let us know how it goes
Sent from my HTC Wildfire using XDA App
A quick update...
Still having issues
I'm noticing that randomly phone process will crash for no apparent reason/cause, normally when off Wifi and on Mobile Data.
Last night was the worst its even been though... at a critical moment when I needed the phone to work... it decided it was having none of it.
Phone kept switching Airplane Mode On and Off causing process.android.com to crash along with most other services So I rebooted only to find that it now was either stuck in Airplane Mode or couldnt enable to Radio (No Phone Signal at all) so I did a battery pull while trying to walk home in the pitch black and rebooted.
The Saga continued even after a battery pull, I eventually as I got in the door was able to use the 'Torch' and recieve a phonecall before all the processes crashed once more...
So I did a battery pull, left the phone for five mins and rebooted. All was well for a while, enabled Wifi, phone seemed happy.
Had to reboot a short while ago, after recieiving a phonecall and text.... grrr... anyone have any suggestions?
I had problem with process restarting. Adw launcher process I downloaded Go Launcher ex I have no problems now.
Sent from my HTC Wildfire using Tapatalk
Hi there,
Just wanted your point of view regarding something really strange that happened to me yesterday.
(btw, I looked it up all over the forum + google but still unabale to find a proper answer)
So basically, I droped down my phone, which crashed on the floor but nothing really serious. Ever since, every time I try and turn on the wifi, it says "Error".
I've tried rebooting it several times and still get the issue.
Do you guys think the wifi chip could have been broken? Is there any report log I could find using terminal or root explorer?
Phone specs:
Virtuous Unity v1.29.0
Android 2.3.3
Phone rooted
Bluetooth does turn on
Thanks in advance for your help
Try flashing a different rom, back up your current one first, and check out if the wifi is working without restoring any apps.
Did you ever fix this? I did the exact same thing, dropped onto hard tile. Wifi error and couldn't read data partition.
Randomly after a day or 2 it fixed itself and was fine for 2 weeks.
BUT...just happened again today. I wiped caches, reflashed ARHD, fixed all permissions. Data partition became readable again (not sure which of those fixed that) but i still get "Wifi Error" when turning wifi on.
Any help/suggestions much appreciated.
Hello Guys,
Need some advice here.
I'm running Paranoid Android 3.99 since its release and just recently my phone has started acting strange, I am unable to unlock my phone resulting in having to soft reset, It seems when using the phone it keeps freezing, I.e i'm typing a text and it stops responding for a moment and then continues typing the letter i hit previously.
I just wiped the cache and davlik but that took far longer than normal, as if it froze whilst wiping.
Has anybody experienced this and recommend any fixes?
Madnessx9 said:
Hello Guys,
Need some advice here.
I'm running Paranoid Android 3.99 since its release and just recently my phone has started acting strange, I am unable to unlock my phone resulting in having to soft reset, It seems when using the phone it keeps freezing, I.e i'm typing a text and it stops responding for a moment and then continues typing the letter i hit previously.
I just wiped the cache and davlik but that took far longer than normal, as if it froze whilst wiping.
Has anybody experienced this and recommend any fixes?
Click to expand...
Click to collapse
try a different rom with clean wipe and see if prob persist
I suspect this is my only option, I'm just a little concerned it seemed to effect CWM.
I will give this a try this evening once I have backed up my apps etc.
I suspect this is my only option, I'm just a little concerned it seemed to effect CWM.
I will give this a try tonight once I have backed up my apps etc.
Cheers