Hi,
The release of the stable CM7.1 really encouraged me to finally S-OFF my phone and install it. I used Revolutionary 0.4pre4, and installed CWM 5.0.20. I wiped everything (data, system, cache, dalvik, you name it), and installed the CM7.1 update zip and right afterwards the new Google apps zip. Eventually, I used Fix Permissions, and rebooted.
I was quite happy, until I saw the com.android.phone FC message. It just showed the same message over and over. I updated my radio to the latest version, to no avail. I tried reformatting, re-wiping, reinstalling quite a few times, and I even tried 3 different sim cards. I finally decided to go back to RUU (kept S-OFF), and didn't get any FCs.
I'm really frustrated, since it is my first Android phone, and I really believe I tried everything already.
Thanks in advance.
I got no problem at all until now.
Another thing I've discovered is when I get these FCs, sometimes if I enable the bluetooth, the phone suddenly discovers the network and the FCs stop. That's just very odd, to me.
I really hope that's not a problem with my phone (especially since it does work properly with RUU).
foouser said:
Hi,
The release of the stable CM7.1 really encouraged me to finally S-OFF my phone and install it. I used Revolutionary 0.4pre4, and installed CWM 5.0.20. I wiped everything (data, system, cache, dalvik, you name it), and installed the CM7.1 update zip and right afterwards the new Google apps zip. Eventually, I used Fix Permissions, and rebooted.
I was quite happy, until I saw the com.android.phone FC message. It just showed the same message over and over. I updated my radio to the latest version, to no avail. I tried reformatting, re-wiping, reinstalling quite a few times, and I even tried 3 different sim cards. I finally decided to go back to RUU (kept S-OFF), and didn't get any FCs.
I'm really frustrated, since it is my first Android phone, and I really believe I tried everything already.
Thanks in advance.
Click to expand...
Click to collapse
Nothing has ever broken my phone quite as much as when I have done the 'fix permissions' thing. Totally screwed my phone and was FC city. I've never done it since, and never had any problems since. Try going back over your steps and leave out the fix permissions part!
I recently had a quick go with CM7 nightlies and had no issues. This included the last nightly before it became stable which was very close to the stable version.
wnp_79 said:
Nothing has ever broken my phone quite as much as when I have done the 'fix permissions' thing. Totally screwed my phone and was FC city. I've never done it since, and never had any problems since. Try going back over your steps and leave out the fix permissions part!
I recently had a quick go with CM7 nightlies and had no issues. This included the last nightly before it became stable which was very close to the stable version.
Click to expand...
Click to collapse
Tried doing the same process without fixing permissions, twice already, and I still get the same problem.
have you tried this?
http://forum.xda-developers.com/showpost.php?p=18309360&postcount=9
Helped with the market issue, but not yet with the com.android.phone FC...
foouser said:
Helped with the market issue, but not yet with the com.android.phone FC...
Click to expand...
Click to collapse
Odd. Here is how I did mine, step-by-step. (Do a NANDroid backup before this, and copy it to your PC/Mac.)
1. Install latest 4EXTRecovery from here: http://forum.xda-developers.com/showthread.php?t=1130004
2. Use this to format all partitions to EXT4. (Not sure if you are using EXT3, not sure if it matters, just saying I'm on EXT4 formatting with no issues.)
3. Do the full wipe & manual format routine (including boot) again just in case!
4. Flashed CM7.
5. Flashed Gapps.
6. Flashed Tiamat kernel (1.1.4)
7. Reboot.
I'm used the same radio as in my sig but also doubt that matters. Not sure what else to suggest. Try downloading the ROM again, and compare the MD5 of your two downloads.
Wow, I believe I'm in some big trouble now. I decided to try and get my phone replaced in the store since I just recently bought it. I used this guide: http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2 to get back to S-ON, but when I tried to flash back the RUU, I get a CUSTOMER ID ERROR and the flash fails.
I've tried two RUUs: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199476_signed
But they both end up the same way. I'm now stuck on the HBOOT screen with S-ON and a big purple security warning (I guess since CM7 is still on the /system partition).
Any help?
Try solution 2 of this guide http://forum.xda-developers.com/showthread.php?t=1284196
but replace the mmc....
With
mmcblk0p25
this will format your system partition,
maybe also data could be formatted by replacing mmc... with mmcblk0p26,
after that run the ruu again.
Swyped from my Desire S
Tectas said:
Try solution 2 of this guide http://forum.xda-developers.com/showthread.php?t=1284196
but replace the mmc....
With
mmcblk0p25
this will format your system partition,
maybe also data could be formatted by replacing mmc... with mmcblk0p26,
after that run the ruu again.
Swyped from my Desire S
Click to expand...
Click to collapse
I don't really have access to recovery (it just gets me back to fastboot), let alone Android, so I don't see how I can follow this guide (maybe I misunderstood)...
I have FC with Market. Everytime i try to acces it.
foouser said:
I don't really have access to recovery (it just gets me back to fastboot), let alone Android, so I don't see how I can follow this guide (maybe I misunderstood)...
Click to expand...
Click to collapse
Don't mind the recovery step, just do the commands within adb shell
Swyped from my Desire S
mihaibuda said:
I have FC with Market. Everytime i try to acces it.
Click to expand...
Click to collapse
Have you tried wiping cache and
dalvik cache?
I also had fc after an update, this solved it for me.
If you're using cyanogen, try changing the language to English us, this solved it for some users.
Swyped from my Desire S
Never mind, I actually created a goldcard in order to bypass the CUSTOMER ID error and flashed my phone back to original and S-ON. Thanks anyways.
Just as a note to everyone, you should really go about getting back to S-ON via this way: Flash any RUU, get the original HBOOT image from that RUU (you can find it in your temp folder while flashing the RUU), and then just downgrade the HBOOT using fastboot. Easier than going through ENG HBOOT, and allows you to avoid these kind of problems (CID errors).
The problem is that you restored "DIALER STORAGE" via titanium backup. Reflash ROM, and don't restore this. It'll work, FOR SURE.
foouser said:
Never mind, I actually created a goldcard in order to bypass the CUSTOMER ID error and flashed my phone back to original and S-ON. Thanks anyways.
Just as a note to everyone, you should really go about getting back to S-ON via this way: Flash any RUU, get the original HBOOT image from that RUU (you can find it in your temp folder while flashing the RUU), and then just downgrade the HBOOT using fastboot. Easier than going through ENG HBOOT, and allows you to avoid these kind of problems (CID errors).
Click to expand...
Click to collapse
Can you please post the thread that contains the Gold Card creation process (if there was one) so that I can add it to the INDEX.
As no doubt this will be useful to others...
ty
ben_pyett said:
Can you please post the thread that contains the Gold Card creation process (if there was one) so that I can add it to the INDEX.
As no doubt this will be useful to others...
ty
Click to expand...
Click to collapse
Sure, it's really the same process for all HTC phones and works even on the newest models (Sensation generation). Thanks a lot to EFI from AlphaRev who actually pointed me in the right direction.
I used this guide: http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
I'm using Windows 7 x64 and when I inserted the card after modifying it, Windows required me to format it (as opposed to what's written in the above guide), but it still worked. Also, since my phone was stuck on HBOOT I had to use another Android phone to get the SD's CID (I used a friend's SGS, and the SD slot to query is mmc2 on it).
shrome99 said:
The problem is that you restored "DIALER STORAGE" via titanium backup. Reflash ROM, and don't restore this. It'll work, FOR SURE.
Click to expand...
Click to collapse
Well, I actually didn't use Titanium Backup at all, so nope.
So about two weeks ago Ive noticed my infuse starting to get laggy. Now its laggy all the time. Ive tried reinstalling CM7 and nothing, Ive installed CM9 and it still lags. can anybody help with this?
Did you try any other ROMs and noticed similar behavior?
If you use Google voice it will cause that. Make sure when you first reinstall a rom don't add any apps... run it and see if its laggy. If not install your apps you always use one at a time... if after installing one Ans you notice lag you got your culprit. GV used to do this to my aria
Sent from my SAMSUNG-SGH-I997 using XDA
i would backup everyone on both of you sd cards to a computer.
(also back up any apps with titanium and text and such)
read this whole page
http://forum.xda-developers.com/showthread.php?t=1524081
then flash stock gingerbread
factory reset your phone
then flash the kernal in the same thread
(format your external sd in your pc, then put it back in your phone and format it with your phone)
remember to back up things on the phone, then move them over to your pc before you start this process, because EVERYTHING on your phone will be wiped
then flash a rom again, from this clean of a state it should fix pretty much anything.
diablo009 said:
Did you try any other ROMs and noticed similar behavior?
Click to expand...
Click to collapse
Before ive ran lots of different roms with no problems, ive been running cm7 for a few months now and its just now starting to act like this. I must have installed a bad file or something.
The_Zodiac said:
i would backup everyone on both of you sd cards to a computer.
(also back up any apps with titanium and text and such)
read this whole page
http://forum.xda-developers.com/showthread.php?t=1524081
then flash stock gingerbread
factory reset your phone
then flash the kernal in the same thread
(format your external sd in your pc, then put it back in your phone and format it with your phone)
remember to back up things on the phone, then move them over to your pc before you start this process, because EVERYTHING on your phone will be wiped
then flash a rom again, from this clean of a state it should fix pretty much anything.
Click to expand...
Click to collapse
okay thanks, ive went back to stock gingerbread and im formatting everything right now. after everything is done ill try flashing cm7 and see if the lag is gone and if it is ill move on to cm9
Evening everyone-
Having some issues I am hoping someone can help me with.
I have a rooted ATT HOX on 1.85 that is having some major problems. I started this morning by trying to flash the Magnolia ROM after being on one of the Cleanroms.
I guess the download was corrupt and I received an error while flashing in CWM and was then stuck in a boot loop. I did the whole RUU deal going back and was able to get back on 1.85, root with super user, etc. but once I got back into the phone to setup I noticed that none of my contacts were syncing after signing in. After playing around a few more minutes I noticed the Messaging would crash after being open for a few seconds with no Force Close warning. Occasionally I could go into a text but after trying to respond or type anything it would revert back to the previous page.
Contacts is a complete no go. As soon as the app is opened it crashes. Same with phone. Absolutely can't use any of the three core apps.
I then tried flashing a variety of the roms and even using the different recoveries and have had absolutley no luck getting the Phone, Messaging or Contacts to work on anything. Even stock RUU 1.85! The only thing I have had luck with is the AOKP port which is working ok minus the phone audio being botched.
Any hope here? Any idea what the deal is?
Any help would be greatly appreciated. Thanks in advance!!!
Do a full wipe and install the ROM.. this should take care of it
I am also having this problem. I tried doing factory restore from TWRP 2.1.8 multiple times. Re-locked the phone and reinstall RUU 1.85 and still have issues.
Can you explain further what you mean by full wipe?
fishscale28 said:
Evening everyone-
Having some issues I am hoping someone can help me with.
I have a rooted ATT HOX on 1.85 that is having some major problems. I started this morning by trying to flash the Magnolia ROM after being on one of the Cleanroms.
I guess the download was corrupt and I received an error while flashing in CWM and was then stuck in a boot loop. I did the whole RUU deal going back and was able to get back on 1.85, root with super user, etc. but once I got back into the phone to setup I noticed that none of my contacts were syncing after signing in. After playing around a few more minutes I noticed the Messaging would crash after being open for a few seconds with no Force Close warning. Occasionally I could go into a text but after trying to respond or type anything it would revert back to the previous page.
Contacts is a complete no go. As soon as the app is opened it crashes. Same with phone. Absolutely can't use any of the three core apps.
I then tried flashing a variety of the roms and even using the different recoveries and have had absolutley no luck getting the Phone, Messaging or Contacts to work on anything. Even stock RUU 1.85! The only thing I have had luck with is the AOKP port which is working ok minus the phone audio being botched.
Any hope here? Any idea what the deal is?
Any help would be greatly appreciated. Thanks in advance!!!
Click to expand...
Click to collapse
I think I figure out how to fix our problem. I was on re-lock status and stock RUU 1.85. I proceed to unlock the bootloader, flash cwm, go into advance, and select fix permissions. I also wipe everything while I am here. After reboot, I am able to set up e-mails and sync contacts and make calls again.
Hopefully, the same will work for you too.
leo14888 said:
Can you explain further what you mean by full wipe?
Click to expand...
Click to collapse
In recovery, wipe data, cache and Dalvik.
Thanks for the responses. To be honest I did factory resets and wipes about 15 times in total...between all the various available roms, the factory 1.85 and a combination of anything I could imagine. Nothing-and I mean nothing-would work. Finally I put it as close to stock as possible and brought it back for a swap. I couldn't find anything at all to help rectify the situation or any info on what in the world may have caused it.
To those of you stuck-good luck! Sounds like it was only a handful that experienced it...hope you get it sorted. Would love to find out why it happened though!
Best of luck!!!
did anyone ever figure out the problem and how to fix this? ive been screwing around for an hour just clearing the data from anything related to contacts or google sync, and even people and still can't get my contacts to sync.. everything else syncs fine my calendar, drive, etc. just not contacts!! grr... any help would be much appreciated. if i figure it out and know how i did it i'll post so others don't waste as much time as i have.
edit: it all started when i tried to flash clean rom using CWM (it said not to but i missed that part lol).. so i ended up having to relock my bootloader, unlocked it again, flashed 1.85 RUU and then finally i was able to boot my phone past the HTC screen.. after that i booted into TWRP and flashed cleanrom. that is when i noticed contacts won't sync, phone book, sms etc. just close when i open them..
tried everything suggested in this thread and still no luck
current status: I decided to flash CWM again, and restored a nandroid backup i had from a while back.. which is a stock rogers rom. contacts r syncing fine.. question is. when i flash to cleanrom 4.0 again will it break the contacts sync again? i sure hope not.. we'll find out tomorrow lol sleep time!
ok so installed cleanrom 4.1 again today and all is working well..
i guess the solution is:
* somehow obtain a stock rogers or att rom (1.85 ruu should work for most)
* once thats installed use fastboot to flash CWM or TWRP
* boot into recovery
* clear cache, dalvik cache, factory reset / clear data
* install custom rom (in my case cleanrom 4.1)
* Reboot phone and check if ur contacts r syncing properly
such a messed up problem hopefully this helps anyone else who runs into it..
Hey guys. Forgive my noobity but I could do with some help and might have a unique problem although I dare say someone has had this or similar.
Firstly, after putting a 64GB stick in my tablet the other day, it all went badly wrong. I had done it before with my previous 64GB that had been playing up so I sent it back and got a new one. The new one seems to be where it all went pear shaped. I might add, the 64GB is for my phone really but my phone cam was playing up so I was swapping it over and stuff... anyway the card itself seems fine in my phone.
Anyways... now my ampe tablet is suffering some strange effects that have changed. initially it would not boot up unless I redone it with the official firmware.. but then wouldn't boot up again, unless I did the same thing over and over. then one time it just refused to boot up past the initial boot screen. I gave up for weeks then picked it up again two days ago.
Now I give it the firmware installed using pheonix again and it booted up. Ahh I thought... lets play. Now I plug it into the pc but the pc says I need to format the 5GB internal partition. So I did. I then looked how to fix the fact that the tab still says it has 0.00kbs internal storage in settings. Then after a while it came up saying 5GB so i copied some files onto it.. great. But I still can't install apps as I found when trying to do this tested working fix http://www.youtube.com/watch?v=sJlpek6w624
I then read about using android commander to move busybox from xbin to bin in the system folder but mine is already there.
So now I am stuck. I can't test if my tab is rooted for the youtube link fix above although this is what I said to Nayeem on youtube:
================
Hi Nayeem. I'm really struggling with this. At first my tab was staying at the 2nd initial boot up screen after I put in a 64GB SD card. Using pheonix I managed to get it to boot by reinstalling the updated official rom from szampe but every reboot back to square one. I left it alone for weeks and came back to it, reinstalled the factory rom again and now it will boot up everytime but it has factory reset every time. I cant run the apps you supply for some reason. Everytime I have rebooted the tab, and connected back to pc it says I need to format the internal 5GB partition. I don't know if I have rooted it properly as I can't check. The commands you give above, work as it changes the location proven when I 'get' it. I'm really stumped. I'm trying out a method someone said about moving busybox from sys/xbin to sys/bin but it's already there (using android commander) so I am really stumped now. When I format the partition, it allows me to copy files to it.
================
So far I am stuck with boot up being a factory reset and the partition needs formatting and although the tablet seems a little laggy, everything I have tried works including wifi and incoming email alerts after logging into google account for playstore but no apps will install or update. the best warning I get is there is no memory to install anything and Nayeems method of moving the install location to the sd card seems to work but nothing will install still saying NOT INSTALLED when I try.
Sorry for the long winded thing but I am really new to all of this.
My hat is off to you if you read all of this and can offer a solution so i can give this tablet back to the kids.
Do you have an installed recovery
Try installing a recovery and wipe data and cache. If it does not work u have to repartition ur tablet
nelsontky said:
Try installing a recovery and wipe data and cache. If it does not work u have to repartition ur tablet
Click to expand...
Click to collapse
I am gonna look into this tonight and see what I can find out. I really don't know exactly what I am doing outside of getting pheonix up and sending a standard rom back to it as previously mentioned.
How would I repartition it ? Sounds stupid asking as i can build pcs... just want to make sure I am doing the correct method.
Edit: Solved, see bottom
ROM (D6633_Customized HK_1290-5630_23.4.A.0.546_R6C_HK_SuperSU2.46_XZDR2.8.21-signedv2)
Bit of a dumb move on my part. It all started when my snapchat stopped working, I updated, and then Titanium Backup wouldn't restore the data properly (giving me "parse error"). I was trying to fix that and read online that sometimes this is caused by improper permissions, so I booted into recovery mode, couldn't find the option, but somehow decided "hey, maybe my root permission (?) is wrong slash it's 6am and I just watched a wild 2016 election end" and I hit the button. Now my phone is stuck in a bootloop.
So my question:
1) What exactly does re-root phone do (in CWM), and why would that have messed me up? Is it because I have a pre-rooted rom?
2) I wiped cache and delvik and it doesn't help
3) How do I fix this? I was thinking of loading a SuperSU zip on the SD card from my computer and flashing that, assuming somehow a corrupted root is at fault. I can't seem to get the thing in ADB mode as a side note.
3b) If that seems like a good idea, does it matter what one I use?
4) If I reflash the ROM, it should keep my apps and stuff, ya? I don't actually care if my phone is crippled, I just need it to work long enough to properly back up some media, and mainly get my whatsapp over to my new SIM card. If I can't get in it's forever stuck on my old number which I don't have the SIM for anymore.
Any help would be GREATLY appreciated.
Edit: I don't know how to delete this. Anyways, with other resources I found out that because I used a pre-rooted ROM, there were issues with using CWM to try to do the rooting with its built in functions, softbricking the phone. Reflashing the original pre-rooted ROM worked fine.