[Q] Constantly Occurring MIUI Force Close Error - Nook Color Q&A, Help & Troubleshooting

I recently installed MIUI on my Nook Color. It boots up fine, but I immediately get a Force Close message that says "The process android.process.acore has stopped unexpectedly. Please try again." I get this message every 10 - 20 seconds while using MIUI. The message always comes up when I attempt to input something with my onscreen keyboard. I get the same error with the 1.8.5 MIUI install as well. The details of my installation method are below...
1. Booted into ClockworkMod Recovery v3.0.2.8 installed on an sd card.
2. Wiped Data / factory reset
3. Wiped Cache partition
4. Wiped Dalvik Cache
5. Installed MIUI 1.9.2 .zip (located on the sd card) file with ClockworkMod Recovery
6. Fixed Permissions with ClockworkMod Recovery
Am I missing any necessary steps?
Is there any way to fix the Force Close messages?
Regards,
Urhos

Sounds like what happened to me also. I did the install twice. Then figured WTF..reverted to Factory Reset to 1.2 and reinstalled from the ground up. Try that. Worked for me.
BTW make sure you use CWM 3.2.0.1
HTH

How would I go about reverting to Factory reset 1.2?

Related

[Q] cache error?

ok so i wiped out my cache and have two zips on my sd card,
when i open the ROM on my phone every thing seems right...
it says install complete and reboot phone. but when i reboot it brings me back to recovery and says "E: can't open/cache/recovery/log"? wtf is this?

[Q] Android.process.acore has stopped unexpectedly

Hello XDA,
A few days ago I installed HC V4 EMMC on my NC. Some apps stopped working so I used my CWM SD card to remove it and install CM7 instead. I factory reset and cleared the Dalvik cache, and then I installed the boot recovery repair zip.
Since then in both CM7 and Phiremod, I see this notification every few seconds, especially if I try to type:
"Process Android.process.acore has stopped unexpectedly..."
What should I do to fix this? I have tried reflashing, clearing the cache, factory resetting, and none of them has helped.
Flash the latest nightly, vanilla. Don't restore your data.
I flashed nightly 150 and the lastest gapps from the wiki and had the same problem.
This never happened before I installed Honeycomb, in which I had several apps force close if I tried to open them.

problem with Cyanogenmod 7.1 in nexus s

hi
I have flashed the new ROM, but there some problems
when i try to do a "factory data reset" from the settings-privacy
and check "erase USB storage" this error message appears "invalid path : null"
and when i try to do a "factory data reset" without checking "factory data reset"
the device restarts and stuck in the formatting screen for along time
I normally do a factory reset in CWM... Maybe that will help ?
yes i did a factory reset from the recovery
also when i try to "ersae usb storage" from settings
I get this message
"Sorry! The application settings/messages (process com.android.settings/messages)
has stopped unexpectedly. Please try again."
and when i try to "wipe Dalvik Cache"
i get this message
E: unknown volume for path [/sd-ext]
by the way I did a factory reset from the /recovery after installing the ROM
DigitalPerson said:
also when i try to "ersae usb storage" from settings
I get this message
"Sorry! The application settings/messages (process com.android.settings/messages)
has stopped unexpectedly. Please try again."
and when i try to "wipe Dalvik Cache"
i get this message
E: unknown volume for path [/sd-ext]
by the way I did a factory reset from the /recovery after installing the ROM
Click to expand...
Click to collapse
Second message is normal, you dont have that partition.
Not sure what you are trying to do. Start off fresh? If so, just go to CWM, wipe data, wipe dalvik ,cache and then if you want go to mounts and format sd card.
Then flash your ROM (and kernel if need be), fix permissions and reboot.
EDIT
Oh adn before somewhere berates you, there is a Q+A sub forum, this one if for devs only
I have tried what u said but the same problem still exists
DigitalPerson said:
I have tried what u said but the same problem still exists
Click to expand...
Click to collapse
Never wipe or format from within the booted rom. Always use recovery!!!!!!
little late for that
Rem3Dy said:
Never wipe or format from within the booted rom. Always use recovery!!!!!!
Click to expand...
Click to collapse
do u mean that it is normal to get this error when doing a format or wipe from within the cooked rom
cause I have tried to format the sd card and do a factory reset from within the rom when i were using the stock rom (not Cyanogenmod) and I haven't faced any problem
DigitalPerson said:
do u mean that it is normal to get this error when doing a format or wipe from within the cooked rom
cause I have tried to format the sd card and do a factory reset from within the rom when i were using the stock rom (not Cyanogenmod) and I haven't faced any problem
Click to expand...
Click to collapse
I meant reboot into clock work mod recovery. Do as I say and you'll be fine. It's normal to get that ext error
Sent from my Google Sexus S
doing a factory reset and wipe everything works fine for me.
i originally tried to run it without a wipe and it was hanging in a lot of apps

[Q] CM7/Phiremod Not working for me

I must be doing something wrong.
I started with a 1.2 Nook Color. I flashed CM7.1 and Gapps from a CWR SD card. Got CM7 to load but had no status bar, and whenever I would try to go into CM7 settings it would force close. I tried reflashing CM7 2-3 more times, no dice.
So I reloaded 1.2 Nook OS. During the configuration, I couldn't get the keyboard to stay on the screen so I couldn't totally configure it.
Got myself a copy of Phiremod 7.1 and tried flashing this. Got it installed and tried to go to the phiremod settings and ....force close. Tried reflashing phiremod multiple times and still no dice. I get into the OS but I get no status bar and I can't adjust CM or Phiremod settings.
This is what I do
As suggested by a member of the forums:
boot into recovery
go into mounts & storage then format system
go into mounts & storage then format data (this is where it says format data failed)
wipe data/factory reset, wipe cache partition, wipe dalvik cache
flash phiremod
flash gapps
reboot...
Still no dice. After 6-8 installs I'm at my wits end. Please help.

[Q] TPT "error while restoring /system" problem

my problem is that suddenly my TPT hangs and keep rebooting, it starts the system normally then it hangs for 3 sec then reboots and so on
-from CWM i did wipe data factory reset and wipe cache partition, but the problem still occurs
-i tried to restore a backup and i get this message "error while restoring /system"
-i tried to make advanced restore, all options can be restored normally except for restore system i get the above message
-the new now the tab is not rebooting and stuck at the lenovo screen
-now i tried to install CM10 ROM from my internal memory and it installs normally
-when cyanogenmod screen loading then it freezes for 3 sec and reboots again and again
any advice and suggestions will be greatly appreciated
m7mdrda said:
my problem is that suddenly my TPT hangs and keep rebooting, it starts the system normally then it hangs for 3 sec then reboots and so on
-from CWM i did wipe data factory reset and wipe cache partition, but the problem still occurs
-i tried to restore a backup and i get this message "error while restoring /system"
-i tried to make advanced restore, all options can be restored normally except for restore system i get the above message
-the new now the tab is not rebooting and stuck at the lenovo screen
-now i tried to install CM10 ROM from my internal memory and it installs normally
-when cyanogenmod screen loading then it freezes for 3 sec and reboots again and again
any advice and suggestions will be greatly appreciated
Click to expand...
Click to collapse
I'm in the same boat. Boot loop, can get into CWM recovery, but can't do anything to get it functional; factory reset, wiping cache, reflashing koshu's 0.91 build, none of these work. Only other suggestion I've seen is getting an ADB shell while in CWM and checking the partitions are not corrupt. As per this post:
http://forum.xda-developers.com/showpost.php?p=39917591&postcount=7
At the bottom of that thread there's reference to a possibly related Lenovo thread of people suffering similar problems, which was closed in Feb with a message about an extended repair program, valid until August.
It'd be a shame if it's a hardware issue, that we can't claim on because we're running custom software... you have to accept that risk when you decide to flash a custom ROM, but I don't think I'll be buying Lenovo again; mine's been repaired once already, and now this.

Categories

Resources