com.android.phone FC after installing stable CM7.1 - HTC Desire S

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.

Related

Rooted - Now no 4g/3g/1x. What gives?

Ok, so I purchased my Thunderbolt yesterday, and of course, first thing's first. Root.
I am familiar with the OG Droid, and rooted it using the RSDLite method. I am also familiar with using ADB to push/pull files, as well as using apkmanager to modify apks, primarily for themeing purposes, but I do a little bit of XML editing, as well.
I am also familiar with my wife's HTC Incredible, and I have rooted it (Using the UnRevoked method) and flashed a few custom ROMs to it, as well.
I took on the manual rooting instructions for the Thunderbolt, and all went easy peasy, other than being a bit time consuming. I thought I had it all worked out, and was running Plain Jane (flashed using CWM Recovery) and with the recommended baseband/radio (flashed from hBoot).
But I noticed when I left my house (where I was using wi-fi the whole time) that I wasn't getting any 4g/3g/1x service whatsoever. I had cell signal, full bars in fact, but no data transfer.
So, I tried flashing a few different radios, and I just ended up flahing BAMF Sense 3.0 with the mr2 baseband update for gingerbread ROMs.
I still have the same problem. I get cell reception, but no data transfer. I can get momentary data if I tell the software to check for a software update. 3g pops up, it checks for an update, and when it is done, 3g goes away and I once again have absolutely no data transfer. Can't surf the web, or use any apk that requires data.
Anybody have any pointers? I have made sure that the mobile network option is checked in the settings. Aside from that, I have no clue where to begin.
Any help is greatly appreciated! TIA!
Only thing I can think of is the radio. I'm using the .627 radio from the inj3cttheory rom post in dev section.
http://forum.xda-developers.com/showthread.php?t=1155986
Hi, and welcome to the tbot community!
a few quick questions,
prior to flashing did you check MD5 sums on both the radio and rom?
and did you delete the PG05IMG.zip file you flashed during the rooting process from your sdcard?
also this may sound like overkill but did you wipe everything (data/cache/dalvik/bat-stats) 3 times?
i would recommend re-downloading both the rom and the radio and check MD5 sums. then put them on your sdcard and make sure their is only one PG05IMG.zip on the root of the sdcard. this next stuff is important; connect phone to your computer and verify that adb recognizes your device. then reboot into recovery and wipe data/cache/dalvik/bat-stats 3 times each. and after that re-flash the rom first, let it do its thing as normal. after the rom is installed do not reboot just stay in recovery. at this time you need to use adb to reboot into the bootloader to flash the radio. after that just reboot like normal
Sent from me, using this app on this thing.
blazednova said:
Hi, and welcome to the tbot community!
a few quick questions,
prior to flashing did you check MD5 sums on both the radio and rom?
and did you delete the PG05IMG.zip file you flashed during the rooting process from your sdcard?
also this may sound like overkill but did you wipe everything (data/cache/dalvik/bat-stats) 3 times?
i would recommend re-downloading both the rom and the radio and check MD5 sums. then put them on your sdcard and make sure their is only one PG05IMG.zip on the root of the sdcard. this next stuff is important; connect phone to your computer and verify that adb recognizes your device. then reboot into recovery and wipe data/cache/dalvik/bat-stats 3 times each. and after that re-flash the rom first, let it do its thing as normal. after the rom is installed do not reboot just stay in recovery. at this time you need to use adb to reboot into the bootloader to flash the radio. after that just reboot like normal
Click to expand...
Click to collapse
Thanks for taking the time to write up your response.
To answer a few of your questions, I did check the MD5 for both the radio and the ROM, and found them both to match.
I did wipe thoroughly, at least 3 times, in fact I went so far as to go into the "Mounts" section of CWM Recovery, and I wiped everything (Data, Cache, System...) from there as well (save it be for the SDCard).
What I did NOT do, however, is ensure that the phone rebooted directly to the bootloader. Instead, I selected "reboot system now" from recovery, and just tried to catch the boot cycle to put it into the bootloader, but that failed.
I will re-wipe everything, and re-install the ROM, and this time I will make sure to reboot using adb directly into the bootloader and see how things go from there.
Thanks for the pointers. I will report back once I finish.
If that doesn't do it, I suppose I'll have to try some different radios...
EDIT: I also did delete the radio/baseband update from the SDCard after booting back up.
If that doesn't work it may be your SIM card. There have been reports where SIM cards randomly fail and data is unavailable. I don't think it has anything to with the rooting or flashing process that causes SIM failure. You may have to unroot to get SIM replacement though.
Sent from my ADR6400L using Tapatalk
OK, I went through the entire process over again, this time ensuring that I rebooted to the bootloader immediately after installing the ROM and letting it install the mr2 radio/baseband.
Results = no love.
Still no 4g/3g/1x.
I am now contemplating going completely back to stock to see if things work in stock form, and if they don't, then I suppose the sim card may be the issue.
OK, quick update. After little contemplation, I decided that reverting back to stock-unrooted was the most logical next step to take. I followed the steps outlined in the following thread: http://forum.xda-developers.com/showthread.php?t=1009423
I only flashed the 1st file (PG05IMG_MR1_no_hboot.zip), and left the bootloader alone. So, as far as I understand, I still have an unlocked, s-off bootloader.
I now have data back.
My next question is, am I able to gain root on the software that is currently on the phone (1.13.605.7) without having to do any downgrades? Or are the exploits only functional on an older/downgraded build?
And my other question is, are there any ROMs in an RUU format that I can simply flash from my bootloader since it's still unlocked with s-off?
Success!
After reverting back to stock, I decided to attempt the rooting process again. Took the exact same steps as the first time, only this time I made sure I allowed the data connection to connect between each downgrade/upgrade/reboot before continuing on with the next step. I'm not sure if that's what made the difference, but it really is the only thing I changed. I didn't redownload any of the files. Simply used the same ones I used previously.
Anyway, I hope this thread serves as an aid to anyone else that might run into this issue.
Thanks for all the suggestions and help.
Congrats! Now get to flashing some awesome ROMs!
Sent from my ADR6400L using Tapatalk
MrHawaii said:
Congrats! Now get to flashing some awesome ROMs!
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Done, and done. Currently running das BAMF RC4.9 with the MR2 radio. So far, running awesome!

Problems after getting back to stock ROM from CM7

Hi,
I'va had CM7 a10 flashed on my Sensation for a few days. A couple of days ago I've decided to get back to Stock ROM, and then the problems started. Before installing CM7 everything was fine. After restoring my backup from before flashing CM7 weird things started to happen (apps dissapearing, settings changing on their own, hangs, and other stuff). So I've done a SuperWipe a few times, and flashed a completely new Stock ROM via USB using: RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223042_signed file. Then I've done a few factory resets, just in case. But still weird things are happening (eg. now I have a clean phone - once again - and trying to setup the sync options and the options app hangs everytime. and installing something from market is like praying for a miracle). I've tried doing factory reset, clear cache/dalvik (but with dalvik CWM recovery says that the partition or files wasn't found). Don't know what to do. Does anyone have any ideas ?? Please help. Phone worked fine before, and after CM7 everything is f*cked up
Wierd, looks like you've tried everything I could think of while reading the post.
Do you still have a nandroid backup of CM7, if so does that work if you restore ?
Can you use ADB to get to the phone ? If so you could check some things from there.
When you installed the RUU from the PC, did it install without errors ? Presumably you had to re-install CWM after that.
CM7 nand backup works fine after restore.
I can use ADB to comunicate with the phone.
No errors while updating RUU.exe / CWM recovery flashed without problems also after that.
I think that there's something screwed up with the file permissions.
I've downloaded and installed about 20 apps since the last HR, and now I have about 40 apps more queued in Market, and as before the downloads are stuck every 1-2 apps. Then I have to restart to CWM recovery and run fix permissions. After that another 1-2 apps will download and get stuck again, and so on...
Anyone has any ideas what the hell is going on ? Because my I'm getting more then irritated by this, and beggining to think that the best solution will be to send my phone flying through the window.
A few questions first.
What country are you in?
Who is your carrier?
What version did your phone originally come with? I believe 1.5xxxxx RUU was released recently, but I could be wrong.
Did you ever change your CID?
Have you ever flashed a new radio and RIL?
Did you copy all of the data from your SD card to your computer, then format your SD card using the phone?
Answer these questions and try the SD card thing, then report back. I may be able to help.
Poland.
T-Mobile (Sensation) / Play Mobile (Gio)
Don't remeber what version my Sensation originally came with - I have a 1.50.401.1 RUU that I'm flashing with currently.
Yes, I've changed CID to 11111111 some time ago, but I'm back to original HTC__001 now.
No I haven't changed my radio or RIL.
I've tried formatting the SD card using the phone, my laptop, my linux NAS, my other phones.
The weird thing is that yesterday all of this was progressing. It came to a point that after a factory reset or even a whole ROM reflash nothing would install (not even Market update). And this also started to happen on my Samsung Gio. So after very very very frustrating evening, and part of the night I gave up. And in the morning it was still the same (on both my android phones). But now things are starting to work (updates/installs). So I think I'm going to blame the whole thing on Google and Market. I'll see what happens while I'll install all my apps in the next few hours.
Still have to restart the phone every 1-3 apps installed. This is driving me crazy

android.process.acore keep crashing after fresh RUU flash

I was having this issue where I couldn't make calls or get my contacts to come up without seeing
Unfortunately, the process android.process.acore has stopped
keep crashing. I finally decided it was best to RUU the 1.85 image and start from scratch. Well that didn't solve the problem! Any ideas what is going on? I can't bring up my contacts, make phone calls, and my google acct won't sync contacts. Any ideas anyone?
google.com
see if that works huh
http://www.shaneycrawford.com/2011/...d-process-acore-problem-on-an-android-device/
Your Android device (tablet, phone, Android TV) gives you the following message.
“The process android.process.acore has stopped working.”
The solution:
Settings –> Applications –> Manage Applications –> All (button on the top that lets you see all applications) –> scroll down to “Contacts Storage” –> Click on “Clear Data”.
This worked on my Android TV and I have seen reports of it working on other Android devices.
Click to expand...
Click to collapse
expertzero1 said:
google.com
see if that works huh
http://www.shaneycrawford.com/2011/...d-process-acore-problem-on-an-android-device/
Click to expand...
Click to collapse
i tried all that already. clearing all the data off apps. factory wipes, master resets. ran out of ideas to try.
I am in the same boat right now. Was having some different issues so I decided to RUU 1.85 and then rooted and unlocked. After installing cleanrom, I start getting phone, contacts, and messages to start crash with no error message. After a while it started giving android.process.acore errors. I've tried:
-Factory wipe, cache and dalvik wipe
-Re-flashing the ROM
-Flashing a different ROM
-clearing app data for contacts, Google framework services, etc.
-fixing permissions
All with no fix. Next step for me was RUU again, but it sounds like that won't do it. Any thoughts out there would be appreciated.
Sent from my HTC One XL using xda app-developers app
this happened when i first installed clean rom 4.0. I immediately re-installed 4.0 and it fixed it. strange... I see some devs say you must wipe 3 times before installing any rom. its worth a try. Also maybe use a different recovery than you have been using. most important thing is to re-download the rom and check the MD5. dude the other day downloaded the rom 6 times with different MD5 before he got a good download. If that is the case, check the memory on your computer as well as hard drive. either of those bad could be corrupting the download. Good luck.
nugzo said:
this happened when i first installed clean rom 4.0. I immediately re-installed 4.0 and it fixed it. strange... I see some devs say you must wipe 3 times before installing any rom. its worth a try. Also maybe use a different recovery than you have been using. most important thing is to re-download the rom and check the MD5. dude the other day downloaded the rom 6 times with different MD5 before he got a good download. If that is the case, check the memory on your computer as well as hard drive. either of those bad could be corrupting the download. Good luck.
Click to expand...
Click to collapse
+1..thats why i always verify md5
Sent from my HTC One X using XDA
Verified the MD5 on the ROM, all checked out there. I'm re-downloading the RUU from a different mirror, so we'll see how that goes. May give switching recoveries a try in the meantime.
Well I was able to get mine to work. I switched back to CWM from TWRP, wiped and installed CleanROM (had Nocturnal running). After the wipe and then flash of CleanROM, I was shocked to see the Nocturnal boot animation. I figured something had gone screwy, and I wiped 5 times in recovery, and then installed CleanROM on top of itself 2 extra times. Rebooted and now all is working again. Not sure what the main issue was from the beginning, but hope this helps you out a little OP. Maybe run RUU again?
ddebart2 said:
Well I was able to get mine to work. I switched back to CWM from TWRP, wiped and installed CleanROM (had Nocturnal running). After the wipe and then flash of CleanROM, I was shocked to see the Nocturnal boot animation. I figured something had gone screwy, and I wiped 5 times in recovery, and then installed CleanROM on top of itself 2 extra times. Rebooted and now all is working again. Not sure what the main issue was from the beginning, but hope this helps you out a little OP. Maybe run RUU again?
Click to expand...
Click to collapse
i'll try switching back to cwm from twrp. what version of cwm worked for you?
trant01 said:
i'll try switching back to cwm from twrp. what version of cwm worked for you?
Click to expand...
Click to collapse
ok well after switching back to cwm and doing wipes for 5 times before installing cleanrom 4.1 it finally worked. can make calls and text without having that error. thanks for the input!!
Thanks for this post. Had the exact same issue. Reverted to the 1.85 RUU and still had it. CWM + Flashing a rom a couple of times and wiping multiple times did the trick.
Glad to be of help. I was stressing over this issue for about 2 days myself. Good to hear it helped someone else too.
Sent from my HTC One X using xda app-developers app

[DONE] Fix for "Preparing Sim Card..." Error for CleanROM

Hey,
Starting this thread up as a place to figure out the "Preparing Sim Card" problem.
Essentially, if you flash CleanROM 4.1 with CWM, you'll probably get this error. There were plethora of fixes out there, such as:
1. Clearing all cache (fastboot/recovery)
2. Clearing all data/force stopping problem apps (people/dialer/messaging)
3. RUUing back to stock
4. Flashing a new radio
5. Removing/Changing SIM cards
6. Trying dialer trick:
.....a. Go to Dialer (if you can't access it, clear the data in it first)
.....b. dial *#*#4636#*#*
.....c. Turn off the radio
.....d. Turn on the radio, and right as the toast appears, choose something from the drop down menu.
.....e. Run a ping test to make sure everything's alright.
7. Used TWRP to clear system/flash new ROM
8. Tried another ROM with GSM Patch
CURRENT STATUS: WORKING!!!! =D
The answer to all your problems issss........
Well, it's multi-step
1. Make sure to flash back via RUU (preferably 1.82 since 1.85 was a b**** for me to re-root T_T)
2. Make sure to unlock your bootloader again
3. Install back CWM (I know...wtf?!) <<THIS STEP IS IMPORTANT (believe it or not)
4. Go back and flash CleanMOD 3.1 or something (just anything below 4.1 should do the trick) [if just installing CleanMOD doesn't work, install the GSM Patch too!]
5. NOW install TWRP
6. Install CleanMOD 4.1
7. SUCCESS!!!
Also, thanks to tehdef, who also tried this method:
Here is what I did to break my phone.
I had the following MODS.
-AOKP 6.1
-CWM
Decided I wanted to test something on CleanROM 4.1
- Flashed CR4.1 in CWM
Got stuck in Boot Cycle and CWM would not load
1. Locked Bootloader
2. Installed 1.85 Evita RUU
3. Unlocked Bootloader
4. Installed TWRP
5. Flashed AOKP 6.1
At this point, I still had an issue. Instead of receiving the "Preparing SIM" Message, I had absolutely zero signal, and I could not "SAVE" an APN.
6. Rebooted to Bootloader
7. Reset to Factory while in AOKP
8. TWRP Loads
9. Reboot to System
My phone now has signal and full contacts and I can make calls and send Texts and MMS with no additional modifications. Please note that with AOKP Superuser comes installed and works just fine, so for whatever reason I did not have to root my device.
NOTE: YOU DO NOT NEED TO USE CLEANROM 3.1 IN ORDER TO GET BACK TO A WORKING STATE!!! Just any rom supporting the unofficial CWM should do. =] (at least I think so, but I'll confirm when someone get's back to me =D)
Thanks goes out to...
Scott for his awesome ROMs and his life lessons
kleeman7 for toughing it out and helping me through the entire thing
tehdef for helping me test out several of my theories
shackman716 for suggesting the idea that worked (it was so crazy it actually worked! XD)
and thanks goes out to anyone I forgot to mention. XD
Now, back to more ROM flashing
scrosler specifically states not to use CWM to flash his ROM. Have you tried TWRP?
redpoint73 said:
scrosler specifically states not to use CWM to flash his ROM. Have you tried TWRP?
Click to expand...
Click to collapse
We are well past that point, redpoint. We've already flashed, and now things aren't working correctly.
In my specific case, XDA Mobile didn't Bold/Red the text to use TWRP instead of CWM, so when I flashed and attempted to boot, I got stuck in a boot cycle. I went back to try to get into recovery, and it wouldn't even go there. So I re-locked, and flashed the 1.85 RUU.
Now I'm getting the same 'Preparing' issue only when I attempt to open up Phone, Contacts, Messaging, all on the stock RUU while being Locked.
I can't even attempt to re-flash the Stock RUU because I'm getting Error 170 on the RUU installer.
This majorly sucks.
Error 170 is a usb communication error and is fixable. Turn off HTC sync. Check for it in running processes. If you still get the error reboot to the bootloader make sure the phone says fastboot usb in red then start the ruu.
tehdef said:
We are well past that point, redpoint. We've already flashed, and now things aren't working correctly.
In my specific case, XDA Mobile didn't Bold/Red the text to use TWRP instead of CWM, so when I flashed and attempted to boot, I got stuck in a boot cycle. I went back to try to get into recovery, and it wouldn't even go there. So I re-locked, and flashed the 1.85 RUU.
Now I'm getting the same 'Preparing' issue only when I attempt to open up Phone, Contacts, Messaging, all on the stock RUU while being Locked.
I can't even attempt to re-flash the Stock RUU because I'm getting Error 170 on the RUU installer.
This majorly sucks.
Click to expand...
Click to collapse
thats a driver error do u have htc drivers installed? good usb cable? tried a diff slot?
if not install htc sync let the first portion install. when it comes time for htc sync inself to install cancel. and just the drivers will be installed
tehdef said:
We are well past that point, redpoint. We've already flashed, and now things aren't working correctly.
In my specific case, XDA Mobile didn't Bold/Red the text to use TWRP instead of CWM, so when I flashed and attempted to boot, I got stuck in a boot cycle. I went back to try to get into recovery, and it wouldn't even go there. So I re-locked, and flashed the 1.85 RUU.
Now I'm getting the same 'Preparing' issue only when I attempt to open up Phone, Contacts, Messaging, all on the stock RUU while being Locked.
I can't even attempt to re-flash the Stock RUU because I'm getting Error 170 on the RUU installer.
This majorly sucks.
Click to expand...
Click to collapse
The OP never stated any of that, and it doesn't seem that he is stuck in the same way you are. So I was asking if he tried to flash TWRP, and then reflash the ROM. Which is not listed as one of his "possible fixes".
I had the same error. I believe I was able to reproduce it by adding my Google Play Account then adding my gmail account (with the same email address) using Activesync. Right after adding my gmail account I would get an application crash (cant recall which one) the phone would reboot and go into a reboot cycle when "Preparing Sim Card". To avoid the issue I did the following:
1. Wipe System, Wipe Data
2. Flash CleanROM 4.1 DE
3. Wipe Cache
4. Install Mods
5. Boot up, add Google Account from the setup wizard
6. Turn on Auto-Sync from Wizard
7. Go into Settings > Accounts > Uncheck sync Email,Contacts, Calendar
8. Clear Data for Email, Contacts, Calendar apps.
9. Add gmail via Activesync w/ Email/Contact/Calendar sync
elsupermang said:
I had the same error. I believe I was able to reproduce it by adding my Google Play Account then adding my gmail account (with the same email address) using Activesync. Right after adding my gmail account I would get an application crash (cant recall which one) the phone would reboot and go into a reboot cycle when "Preparing Sim Card". To avoid the issue I did the following:
1. Wipe System, Wipe Data
2. Flash CleanROM 4.1 DE
3. Wipe Cache
4. Install Mods
5. Boot up, add Google Account from the setup wizard
6. Turn on Auto-Sync from Wizard
7. Go into Settings > Accounts > Uncheck sync Email,Contacts, Calendar
8. Clear Data for Email, Contacts, Calendar apps.
9. Add gmail via Activesync w/ Email/Contact/Calendar sync
Click to expand...
Click to collapse
Well, I tried emailing and stuff, and it seems anything regarding data seems to be alright. It just seems to be the issue with phone/sms data now. I believe it's something software related as it still reads my sim just fine, and it recognizes when it gets a call. Just when I get a call, it repeatedly FCs. I might give it a try though, so thanks!
redpoint73 said:
The OP never stated any of that, and it doesn't seem that he is stuck in the same way you are. So I was asking if he tried to flash TWRP, and then reflash the ROM. Which is not listed as one of his "possible fixes".
Click to expand...
Click to collapse
Sorry, I had to go out for lunch, so I didn't really go into much detail. I have tried using TWRP and is still using that atm, and also tried flashing a rom with GSM Patch, which I'll edit the OP to match. Both of these did not work and I'm going to try and pull a logcat or something. Will update when I get it
Just got mine to flash. I noticed though that for whatever reason my current 1.85 had an _r2 at the end, and the one I'm flashing does not. Curious if ATT network is rejecting due to the RUU version.
Guess we will find out when it's done.
Edit: Nope, nada... Same issue.
Curious though why none of my contacts sync. seems like this is a contacts issue for me.
tehdef said:
Just got mine to flash. I noticed though that for whatever reason my current 1.85 had an _r2 at the end, and the one I'm flashing does not. Curious if ATT network is rejecting due to the RUU version.
Guess we will find out when it's done.
Edit: Nope, nada... Same issue.
Curious though why none of my contacts sync. seems like this is a contacts issue for me.
Click to expand...
Click to collapse
i feel like the dialer and the contacts are linked together. if we can solve one, we can probably solve both. I looked in my catlog and they stated that they couldnt find a particular file/db in the /data/data folder. ill look into this and see what happens
Did either of you try flashing a different rom like xi40, or sick sense, and do a system, cache, dalvik, factory reset, wipe from twrp before you flash a rom, and see how that goes
Sent from my HTC One X
Well, hopefully that's it.
---------- Post added at 01:12 PM ---------- Previous post was at 01:06 PM ----------
kleeman7 said:
Did either of you try flashing a different rom like xi40, or sick sense, and do a system, cache, dalvik, factory reset, wipe from twrp before you flash a rom, and see how that goes
Sent from my HTC One X
Click to expand...
Click to collapse
I haven't unlocked my BL again because I'm at home, and frankly, I'm not sure how the process is changed once I already ahve the Auth Key, and if I can do it quickly here from work.
kleeman7 said:
Did either of you try flashing a different rom like xi40, or sick sense, and do a system, cache, dalvik, factory reset, wipe from twrp before you flash a rom, and see how that goes
Sent from my HTC One X
Click to expand...
Click to collapse
lol actually, i just came from Cobra ROM and yeah I cleared everything and flashed, but to no avail. I can always try again, but time's running out and I don't think it's going to work since Ive done it over 15 times in order to try everything
jojojohnson7410 said:
lol actually, i just came from Cobra ROM and yeah I cleared everything and flashed, but to no avail. I can always try again, but time's running out and I don't think it's going to work since Ive done it over 15 times in order to try everything
Click to expand...
Click to collapse
Try flashing AOKP + GApps to see if the People vs Contact system is diff?
tehdef said:
Try flashing AOKP + GApps to see if the People vs Contact system is diff?
Click to expand...
Click to collapse
That's a good idea, maybe once Scott reads his thread he will have some input for everyone.
Sent from my HTC One X
Found an interesting read in another forum, which would confirm what error I saw in the logcat:
http://forum.xda-developers.com/showpost.php?p=20892463&postcount=15
http://forum.xda-developers.com/showpost.php?p=27115182&postcount=16
tehdef, try these two for me and see where you get. I'm trying to get my phone into another rom so I can try this out cause 1.85 won't let me root (the problem we have specifically screws up that exploit, go figure!) so let me know how it works. I'll be trying it in a bit so i'll update back when i test it out
...actually, tehdef, did you ever unlock your bootloader with the one-click without HTCDEV unlock at any point in time? This might help me out cause this might also be the problem. Thanks!
jojojohnson7410 said:
Found an interesting read in another forum, which would confirm what error I saw in the logcat:
http://forum.xda-developers.com/showpost.php?p=20892463&postcount=15
http://forum.xda-developers.com/showpost.php?p=27115182&postcount=16
tehdef, try these two for me and see where you get. I'm trying to get my phone into another rom so I can try this out cause 1.85 won't let me root (the problem we have specifically screws up that exploit, go figure!) so let me know how it works. I'll be trying it in a bit so i'll update back when i test it out
Click to expand...
Click to collapse
Clearing contacts seems to work. My list is now populating.
Attempted to send text. Prepairing SIM Card returns.
---------- Post added at 02:23 PM ---------- Previous post was at 02:12 PM ----------
Unfortunately the Android.acore process has stopped when I tried to sync my Gmail contacts after clearing everything.
I'm having the exact same issues. I've usually been able to figure out all my own screw ups but just not this time. I too flashed cleanrom 4.1 using cwm because i failed at reading the directions. Got stuck at recovery and was able to install a 1.85 ruu and them proceeded to put twrp on it and flash cleanrom 4.1. Everything seemed fine but then i noticed that my xfinity email would open and and then quickly close. Didn't think much of it, but then i realized that also the phone and contacts do the same thing. I've tried everything but holy water to get this fixed including trying other roms, fixing permissions in recovery, clearing phone and contacts data, deleting db.journal file, and shaking the phone really hard....
Any ideas?
Something is corrupt.
I want to put AOKP back on the phone, because I honestly think it's Sense related.
natediddydude said:
I'm having the exact same issues. I've usually been able to figure out all my own screw ups but just not this time. I too flashed cleanrom 4.1 using cwm because i failed at reading the directions. Got stuck at recovery and was able to install a 1.85 ruu and them proceeded to put twrp on it and flash cleanrom 4.1. Everything seemed fine but then i noticed that my xfinity email would open and and then quickly close. Didn't think much of it, but then i realized that also the phone and contacts do the same thing. I've tried everything but holy water to get this fixed including trying other roms, fixing permissions in recovery, clearing phone and contacts data, deleting db.journal file, and shaking the phone really hard....
Any ideas?
Click to expand...
Click to collapse
lol at the shaking your phone really hard XD
Anyways, I have a theory:
there are two ways we COULD possibly fix this:
1. obtain a rom that has root. Get root explorer or somehow get into /data/data/com.android.providers.contacts/databases/ and delete .db-journal if its in there. Do this in conjunction with clearing out the data of all the affected apps and their sister apps (i.e. Contacts, Contacts Storage, Contacts Sync) and force stopping all of them. Can't test this cause bootloader refuses to unlock atm)
2.lock the bootloader, RUU to 1.82 (NOTE: NOT 1.85!) and try to unlock using this: http://forum.xda-developers.com/showthread.php?t=1734558. REMEMBER take out your SIM card! but maybe this might help not 100% sure if this is what caused it for me, so it's best to consider it too. Can't test this right now because I am stuck without a BL unlock and i can't get root on this firmware
*EDIT* ahahhahahah i lied. no sim card needed, so why would it rely on mobile data? ahh im such a silly person alright here goes!
i'll let you know when i get out of my pickle, but it might be a while. That, or i might just get pissed off enough to just go to the store and look like an idiot cause i really do feel like one right now and I need to get the phone working T_T
Keep checking back!

Stuck on white splash screen after disabling su permissions and Superwiping

My phone is stuck on the white splash screen that displays the HTC logo.
It happened because I’ve been trying to get an app working that requires me not to be rooted. I had tried a few of the “ hide your root” apps from the Market but none worked.
I eventually found a way to get it working by going into system/xbin and disabling all the su permissions.
However after disabling the su permissions I found I was unable to allow the permissions again when attempting to reverse the same procedure.
This morning I tried doing an ARHD Superwipe. I thought this would be similar to doing a factory reset (didn’t realise 4EXT had it’s own factory reset).
After doing Superwipe 4EXT told me I was now ready to flash my ROM. I still haven’t flashed the ROM, instead the phone attempted to boot up but got stuck on the white / HTC screen.
Is it normal procedure that Superwipe will completely wipe the ROM off my phone – hence the reason why it’s now stuck like this (until I flash the ROM again)?
I’m at work right now and don’t currently have the ROM on my SD card.
If I reflash the ROM when I get home will that fix everything?
I’m worried that I might have messed my phone up disabling these su permissions?
I can still get into recovery OK what it matters.
Please help if you can as I am panicking a bit here.
Kurdt Kobain said:
My phone is stuck on the white splash screen that displays the HTC logo.
It happened because I’ve been trying to get an app working that requires me not to be rooted. I had tried a few of the “ hide your root” apps from the Market but none worked.
I eventually found a way to get it working by going into system/xbin and disabling all the su permissions.
However after disabling the su permissions I found I was unable to allow the permissions again when attempting to reverse the same procedure.
This morning I tried doing an ARHD Superwipe. I thought this would be similar to doing a factory reset (didn’t realise 4EXT had it’s own factory reset).
After doing Superwipe 4EXT told me I was now ready to flash my ROM. I still haven’t flashed the ROM, instead the phone attempted to boot up but got stuck on the white / HTC screen.
Is it normal procedure that Superwipe will completely wipe the ROM off my phone – hence the reason why it’s now stuck like this (until I flash the ROM again)?
I’m at work right now and don’t currently have the ROM on my SD card.
If I reflash the ROM when I get home will that fix everything?
I’m worried that I might have messed my phone up disabling these su permissions?
I can still get into recovery OK what it matters.
Please help if you can as I am panicking a bit here.
Click to expand...
Click to collapse
Hi,
Yes,Superwipe will clear your phone.
This includes the ROM.
Re-flash the ROM,and this will return your ROM,and SU.
Kurdt Kobain said:
My phone is stuck on the white splash screen that displays the HTC logo.
It happened because I’ve been trying to get an app working that requires me not to be rooted. I had tried a few of the “ hide your root” apps from the Market but none worked.
I eventually found a way to get it working by going into system/xbin and disabling all the su permissions.
However after disabling the su permissions I found I was unable to allow the permissions again when attempting to reverse the same procedure.
This morning I tried doing an ARHD Superwipe. I thought this would be similar to doing a factory reset (didn’t realise 4EXT had it’s own factory reset).
After doing Superwipe 4EXT told me I was now ready to flash my ROM. I still haven’t flashed the ROM, instead the phone attempted to boot up but got stuck on the white / HTC screen.
Is it normal procedure that Superwipe will completely wipe the ROM off my phone – hence the reason why it’s now stuck like this (until I flash the ROM again)?
I’m at work right now and don’t currently have the ROM on my SD card.
If I reflash the ROM when I get home will that fix everything?
I’m worried that I might have messed my phone up disabling these su permissions?
I can still get into recovery OK what it matters.
Please help if you can as I am panicking a bit here.
Click to expand...
Click to collapse
I had a similar issue once when i removed superuser accidentally. I flashed a recovery and it fixed the problem and returned me to root. Did you do a backup?
Sent from my HTC Sensation using xda premium
evetsno1 said:
I had a similar issue once when i removed superuser accidentally. I flashed a recovery and it fixed the problem and returned me to root. Did you do a backup?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Cheers guys I was hoping it would be as simple as that. I just had a bit of a panic this morning I guess! I've never used Superwipe with previous Androids.
Yeah I did make a backup of my stock ROM before flashing.
So in future is there a more easier way to restore the permisions in su?
Kurdt Kobain said:
Cheers guys I was hoping it would be as simple as that. I just had a bit of a panic this morning I guess! I've never used Superwipe with previous Androids.
Yeah I did make a backup of my stock ROM before flashing.
So in future is there a more easier way to restore the permisions in su?
Click to expand...
Click to collapse
4ext fix permissions in tools menue I believe. You can also hold down on the apk till the menue comes up then go to properties and manually fix them if you know what to set them to.
Sent from my HTC Sensation using xda premium
evetsno1 said:
4ext fix permissions in tools menue I believe. You can also hold down on the apk till the menue comes up then go to properties and manually fix them if you know what to set them to.
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
I found that when I first went to disable them the various permission boxes all showed up no problem but when I went back to restore them the boxes would no longer display anymore.
That's good to know that I should be able to do it via 4EXT. Would also like to know if its possible via the phone itself too as my gf's Android doesn't have 4EXT.
Would it work if I copied the system/xbin/su file before disabling them, maybe store it on my PC, and copy it back again afterwards when I want the root reactivating? I'm thinking no because r/rw is turned off right?
Or if I just reflashed the root again from the PC to phone. Would that work?
Kurdt Kobain said:
I found that when I first went to disable them the various permission boxes all showed up no problem but when I went back to restore them the boxes would no longer display anymore.
That's good to know that I should be able to do it via 4EXT. Would also like to know if its possible via the phone itself too as my gf's Android doesn't have 4EXT.
Would it work if I copied the system/xbin/su file before disabling them, maybe store it on my PC, and copy it back again afterwards when I want the root reactivating? I'm thinking no because r/rw is turned off right?
Or if I just reflashed the root again from the PC to phone. Would that work?
Click to expand...
Click to collapse
I dont think you can get root back by fixing permissions. It is my understanding that root is a two part system. First is a binary and second is a program that interacts with the binary such as superuser or supersu. If you remove either part you lose root.
When I lost root I only lost it because I lost supersu. After losing supersu oil checked for root with root checker and it was lost. I tried replacing it but it didnt work. I had to flash a recovery that had root to get it back or re-root my phone. That is about the extent of my knowledge of it.
Sent from my HTC Sensation 4G using xda premium

Categories

Resources