Related
I am trying to flash the honey3d rom on my desire HD but when I check the the sums i get 980DFD00F5C4BD2C1C3D265A687A89D8 and according to the theat
it should be 666DD197A3E541689307183A10A4D9F5
I already thy'd redownloading bt it is still the same, does anyone else have this issue?
hi guys.
Im having an issue
I changed from stock to rcmix3d rom and it keeps rebooting by itself.
Everything is working fine but the reboot issue is killing me
any help please?
Did you check the MD5 of the ROM before flashing? Does it actually boot so you can use it? Or are you stuck in a bootloop before it actually gets to a point where you can use it?
raze599 said:
Did you check the MD5 of the ROM before flashing? Does it actually boot so you can use it? Or are you stuck in a bootloop before it actually gets to a point where you can use it?
Click to expand...
Click to collapse
Yeah i checked md5
It boots and everything works.
Random times it just reboots. Sometimes 10 minutes sometimes hours
Sent from my GT-I9100 using XDA App
Do you get any error messages or strange behaviour before it reboots? What apps have you installed if any?
even i had the same issue with rcmix3d ,problem started after i flashed a new radio file though...nothing helped i had to flash a new fom..if by any chance you are running any UV script reset it with reset.zip UV is also known to cause tis issue
So I downloaded the most recent version of Cyanogenmod for the S4 today (7/18) and it won't connect to the wifi at all. Anyone else experiencing similar issues? Suggestions on what I should do?
Maybe a bad download? Check and compare the md5 sums, if they match, it's probably a bad flash. Check if anybody else on the latest has any issues similar to yours. If not, do a full wipe(cache and dalvik, data, and system) and reflash ROM+gapps to see if that resolves the problem. Hope I helped!
Sent from my Galaxy S3
manturduken said:
So I downloaded the most recent version of Cyanogenmod for the S4 today (7/18) and it won't connect to the wifi at all. Anyone else experiencing similar issues? Suggestions on what I should do?
Click to expand...
Click to collapse
I installed 7/18 today and WiFi works fine
Sent from your phone. You should be careful where you leave that thing.
Never mind about this. I did a factory reset and then my Wifi miraculously worked. Thanks for the replies though.
Hello all,
Recently I installed the Avatar rom from this page (http://forum.xda-developers.com/showthread.php?t=2130852) on to my galaxy s2. I did a full backup in twrp before wiping my caches and installing the rom. Upon installing I run into unrelenting com.android.phone crashes. I go to restore my backup and when I boot to that, my dialpad is missing and I get no service. Can anyone please help me with this? Thanks!
Edit: I have now tried flashing it to stock and I still run into this issue.
Have you tried flashing a new radio?
Sent from my SAMSUNG-SGH-T989
Fix
Okay I managed to fix this issue. Just to clarify what the issue was for anyone with similar problems:
After flashing a new rom I continuously get com.android.phone errors, no service, and no dialpad. Using my twrp full recoveries (2 of them) didn't fix the issue as I still got the crash and missing dialpad and no service.
To fix this, I flashed to stock using the Jellybean file from a thread. (Can't submit links but a google search of "[HOW TO] Odin any stock rom" provides the thread as the first result).
That alone didn't fix it, the last step is what fixed the problem for me, which was a factory reset and cache wipe after the flash.
I have fixed the issue but I am still left with the question of how this was possible. Isn't the dialpad simply an apk that should be in the backup?
Why would flashing a new rom leave me with this error?
Any help in clearing up the cause of the issue here would be much appreciated.
edk128 said:
Okay I managed to fix this issue. Just to clarify what the issue was for anyone with similar problems:
After flashing a new rom I continuously get com.android.phone errors, no service, and no dialpad. Using my twrp full recoveries (2 of them) didn't fix the issue as I still got the crash and missing dialpad and no service.
To fix this, I flashed to stock using the Jellybean file from a thread. (Can't submit links but a google search of "[HOW TO] Odin any stock rom" provides the thread as the first result).
That alone didn't fix it, the last step is what fixed the problem for me, which was a factory reset and cache wipe after the flash.
I have fixed the issue but I am still left with the question of how this was possible. Isn't the dialpad simply an apk that should be in the backup?
Why would flashing a new rom leave me with this error?
Any help in clearing up the cause of the issue here would be much appreciated.
Click to expand...
Click to collapse
I still think it was the radio, If you didn't get any signal then the first thing I would do is reflash the radio. The same thing happened to me on CM 10.1..I don't remember if the dialer was crashing on me but it probably was BUT I do know I was getting horrible battery life and I had no signal. I just flashed the latest radio and I was good It could be that the radio you had when you were flashing Avatar didn't support it.
edk128 said:
Okay I managed to fix this issue. Just to clarify what the issue was for anyone with similar problems:
After flashing a new rom I continuously get com.android.phone errors, no service, and no dialpad. Using my twrp full recoveries (2 of them) didn't fix the issue as I still got the crash and missing dialpad and no service.
To fix this, I flashed to stock using the Jellybean file from a thread. (Can't submit links but a google search of "[HOW TO] Odin any stock rom" provides the thread as the first result).
That alone didn't fix it, the last step is what fixed the problem for me, which was a factory reset and cache wipe after the flash.
I have fixed the issue but I am still left with the question of how this was possible. Isn't the dialpad simply an apk that should be in the backup?
Why would flashing a new rom leave me with this error?
Any help in clearing up the cause of the issue here would be much appreciated.
Click to expand...
Click to collapse
Sometimes what happens when flashing a rom or even restoring a backup sometimes with newer roms that support the preload partition is the recovery doesn't properly load the preload partition, causing some apps or system software to malfunction, what recovery are u using?
Sent from my SGH-T989 using xda premium
I use twrp. I think 2.5. Is there any way to prevent this problem? I want to try reflashing the avatar ROM but it's a pain to have to flash back to stock and then root and then restore my backup
As the title mentioned my phone freezes when the wifi is disconnected. The phone is on but I can't wake it. The only way to recover is to remove battery. After the operation Wifi gets stuck in "turning on" state. I noticed that that this can be fixed by using by "Fix permissions" -functionality. It's not very optional way to operate...
I'm using Viper DHD 2.3.0 and Kernel is 3.0.93-ucxl-2wcr-S27
I've tried several Radio images with no luck.
This began one morning out of nowhere so it might be some sort of HW issue, but I'm not ruling the software side out.
If someone knows what to try or has had similar issues, please comment.
Waldo_gg said:
As the title mentioned my phone freezes when the wifi is disconnected. The phone is on but I can't wake it. The only way to recover is to remove battery. After the operation Wifi gets stuck in "turning on" state. I noticed that that this can be fixed by using by "Fix permissions" -functionality. It's not very optional way to operate...
I'm using Viper DHD 2.3.0 and Kernel is 3.0.93-ucxl-2wcr-S27
I've tried several Radio images with no luck.
This began one morning out of nowhere so it might be some sort of HW issue, but I'm not ruling the software side out.
If someone knows what to try or has had similar issues, please comment.
Click to expand...
Click to collapse
Have you try flash another kernel, such as pacha kernel 2.9.1 or t10 kernel, or you can try dirty flash this rom again.
...and now it's working again
For some reason the phone started to act normally again without any further actions. Hopefully it was some sort of odd software bug...