CM7 Error message - Nook Color Q&A, Help & Troubleshooting

I keep getting this error message, over and over. "Sorry! The process android.process has stopped unexpectedly. Please try again.
Any ideas ?

When posting in forums, only three things truly matter...
Location, location, location...
However, assuming this thread is moved and not deleted.... be sure you wiped properly, and try using "fix permissions" in recovery.

So, Nook Color Q&A ?

Yes, that is the correct place, sorry I did not mention. This will probably be moved when a mod sees it. I apologize for again bumping this thread to the top of the dev forum.

Moved to correct board..
On the topic, i would suggest reflashing the ROM you are using (you don't have to wipe data), and wipe cache. A fix permissions cannot hurt either..

Related

Recovery bootup issue

Searched through the forums, couldn't find the same issue I was having. If I missed it, go easy on me :_).
I went through 1.5 to the rooted 2.1 scenario. Double checked everything including Hash's. The phone booted to the PD00IMG just fine. everything else was done to the letter of the post. Now the problem, when I reboot the phone to the recovery it boots up just fine to the recovery system...but there is an error at the bottom of the screen that says...e: Can't open /cache/recovery/command. Wiped and have gone through the complete process 2 times..same error. so when I hit wipe data/factory reset, the only choice i get is delete all user data? No Flash zip from SDcard choice. Obviously I have missed something. Anyideas or help would be appreciated.
Thanks in advance
Did you try this?
No i didn't. Thank you for the link. I'll give it a try.
If that doesn't do it. PM me.
thanks North, going through the process now. Hopefully this will resolve it.
Got it
Well, after redoing everything...I went with Amons recovery and Ivans 0.5.4 rom..>Everything is good. Thanks
No problem. I'm glad you got it working.
BTW...
I just wanted to say WOW...Great work to all the Devs and everyone who helps support in the forums. Thanks for all the cool eye candy! GL with all future work.

[Q] "Sorry, there's not enough space to install this item." - HELP!

Nevermind. I found a fix. please delete this? I don't know how.
How did you fix it? I am assuming you flashed over voo doo just like I did. I have tried to uninstall voo doo and restore to stock through Odin several times go into force close loops ect finally got back to stock, but still get the "sorry not enough space to download" mess. How did you do it?
Instead of saying "nevermind" after asking for help... It'd be more beneficial to the community if you explained how you fixed it ya know?
Give/Take
Thanks...
Read adrynalyne's sticky on completely removing voodoo. You need to rewrite the original master boot record because voodoo writes a new one for a different partition map. Just check out the stickies in this subforum. Should be the second one.
Sent from my SCH-I500 using XDA App
So...
Was this ever resolved? I'm having this issue with my Fascinate, which I just updated to 2.2 via the below instructions.
http://forum.xda-developers.com/showthread.php?t=948722
It seems that my phone does not have enough storage in the built in memory, which is why the issue persists. However, I do not think I have actually run out of memory, since I just did a clean install. Also, whenever I restart my phone, it wipes all of the synced information, removes the market completely, and makes it so that I must add my Google account information again. Oh, and it will not actually accept the Google account that I add, saying, "Can't establish a reliable data connection to the server".
Thoughts? I'm totally lost.
Edit: Used this to fix it.
http://forum.xda-developers.com/showthread.php?t=867648
Just built up from there.

MIUIv4 Messaging App

I had already flashed to 2.4.13 before realizing that sms wasn't working and I am having a very hard time getting back to 2.4.6 without any problems. At first all I did was wipe cache and dalvik and then flashed 2.4.6 over 2.4.13 but ran into a whole mess trying to get that to work.. should that be possible without completely wiping data and doing a factory reset? I somehow ended up in a recovery bootloop and after trying EVERYTHING including odin an old CWM trick I found under the development section I spent about 5 hours getting it right to odin back to stock in order to get back to a nandroid backup of 2.4.13. Now I successfully made it to 2.4.6 but I can't for the life of me get the messaging app to work.. it keeps force closing. I tried uninstalling it and reflashing the ROM but that didn't work either. I'm going to try to extract the apk from the zip and manually install it over the current one, but if that doesn't work does anyone have any ideas? Am I just going to gave to do a complete data wipe? (I'd really like to avoid that I use a lot of apps.. its a pain to restore all of them with TB). Anyway i'd appreciate some help and sorry I'm not allowed to post in the MIUI thread yet bc of 10 post minimum requirements? so I had to post this here.
Thank you kindly
click here _ for finger exercise
Ahh I apologize I just realized there was a separate Q&A section.. anyway still looking for advice if I just have to do a data wipe and start all over or not.
Thanks again!
click here _ for finger exercise
new2this:i see now
Soo I've been with xda for about a year but haven't used the forum myself much except for reading and links, and again I apologize for posting in the wrong section.. it's a lot clearer when i'm on my laptop vs. the xda app
I'm just going to do a full data wipe/reset to make this easy (well, sort of ).. but thank you anyway and thank you for understanding...
I guess we all have to learn somehow, right? Hope it's cool
try clearing data of the messaging app. if it still doesn't work then wipe data for everything and start over.
Sent from my SCH-I500 using Tapatalk 2

Please help for HD2 NAND booting problem

hi guys
one month ago,I installed this room
HD2_NDT_MIUI_GINGER_2.3.7_STABLE_V5.1_MA GLDR_New
& it was the first time for me to try android on HD2.
Yesterday,the device was very slow so I made Reboot, the device restarted and load till reaching moving coloured rectangels or cubs on starting & couln't complete to load , i tried to soft reset it many times or give it more time to load ,the same problem
what is wrong , & how can i solve this issue??
sorry for my bad english & thanks in advance
Wrong section to post this in, questions belong in the Q&A section. It would also help if you described exactly what you did better.
Not sure that you have posted in the right thread
Have you try to wipe the cache in the recovery, and wipe Dalvik cache + fix in the recovery, advanced...
If it don't work, try an hardreset in magldr ...
sorry , I will post it in the right section
Dr_Mask said:
sorry , I will post it in the right section
Click to expand...
Click to collapse
you should pay attention to partition size and also forum section
if loosing data is no biggy you can start from scratch. I mean task29, install magldr, flash recovery and then any rom you like.

[Q&A] [ROM][AOSP][5.0.0_r2 LRX21M][BSZAospLP v1.0][SuperSU|BusyBox][06/11/14]

Q&A for [ROM][AOSP][5.0.0_r2 LRX21M][BSZAospLP v1.0][SuperSU|BusyBox][06/11/14]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][AOSP][5.0.0_r2 LRX21M][BSZAospLP v1.0][SuperSU|BusyBox][06/11/14]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
keith.valdez said:
If I'm flashing from an All F2Fs Ext4 rom, are there any special preparations I need to perform to ensure I don't brick? I would like to flash it but I want to ensure that there are few caveats first. Thanks.
Click to expand...
Click to collapse
Make sure you change the partitions filesystem in TWRP to ext3 or it will not work!
NUMB401 said:
Make sure you change the partitions filesystem in TWRP to ext3 or it will not work!
Click to expand...
Click to collapse
Exactly - if coming from All-F2FS in recovery put cache and data back to ext4 otherwise when you boot it will think your tablet is encrypted and ask for a password!
Thanks for the ROM. However a tilapia(3g) version would be greatly appreciated!
Click to expand...
Click to collapse
I have built Lolipop from source for it but 3G does not seem to be working with radio from KitKat (and I don't know where to get another radio.img)
failing Google+ apk
Trying to install google+ and it keeps failing any ideas? I've tried the past 3 versions and it won't work.
irishman13 said:
Trying to install google+ and it keeps failing any ideas? I've tried the past 3 versions and it won't work.
Click to expand...
Click to collapse
Known incompatible for now. Rest assured it'll be fixed by the ota ?
For those of you still having issues -- make absolutely sure that you've wiped And repaired the cache, data, and system partitions, under TWRP's advanced menu (you have to select each 1 at at time). It takes like 1-2 secs per partition. Without the repair option, you're gonna be stuck on the Google logo forvever.
THEN restart once repaired wiped repaired, and flashed, and don't bother to let TWRP install SuperSU, as the ROM already has it.
---------------
Admin Note: this thread has a dedicated questions and answers section which you can access here -->.
@nickmv is that if you're coming from a f2fs Rom or for everyone?
gsmyth said:
For those of you still having issues -- make absolutely sure that you've wiped And repaired the cache, data, and system partitions, under TWRP's advanced menu (you have to select each 1 at at time). It takes like 1-2 secs per partition. Without the repair option, you're gonna be stuck on the Google logo forvever.
THEN restart once repaired wiped repaired, and flashed, and don't bother to let TWRP install SuperSU, as the ROM already has it.
---------------
Admin Note: this thread has a dedicated questions and answers section which you can access here -->.
@nickmv is that if you're coming from a f2fs Rom or for everyone?
Click to expand...
Click to collapse
Just F2FS
---------- Post added at 12:42 PM ---------- Previous post was at 12:42 PM ----------
irishman13 said:
Trying to install google+ and it keeps failing any ideas? I've tried the past 3 versions and it won't work.
Click to expand...
Click to collapse
Latest GApps newly linked in OP has a working Google+
There is broken "Ok Google" hotword as well as voice search. It just won't listen to me
First off let me say this is awesome and really breathed new life into my old N7! Secondly I used the Tap & Go setup method from an GPE One M8 and it didn't really work all the way but whatever.
The issue is there is now an undismissable notification on my M8 saying setup completed. Any ideas how to get rid of this?
Oh and also has Face Unlock ever been present on the Nexus? Wanted to try it out but wasn't listed as an option. Thanks a ton!
TitBkp
Hi
I have supersu installed but titanium backup doesn't recognise the device is rooted! Any ideas? Other root apps work on android 5 but this one doesn't.
I cannot log into play store since upgrading to lollipop. How can I fix this?
Sent from my AOSP on Grouper using XDA Free mobile app
Successfully installed via multirom, however play store crashes when opened.
am2012 said:
Hi
I have supersu installed but titanium backup doesn't recognise the device is rooted! Any ideas? Other root apps work on android 5 but this one doesn't.
Click to expand...
Click to collapse
Try this beta one:
http://forum.xda-developers.com/showpost.php?p=56629869&postcount=196
When installing the GApps package I get this error: E:Error executing updater binary in zip '/data/media/0/sideload.zip'
I originally got a different one but I remembered I was on the "buggy" 2.7.1.1 version so I updated to latest 2.8.1.1 version and well...this. I've wiped my data/cache/system/all of it and repaired the data n cache and then did this all and still a no go. What am I doing wrong? Am I missing something? The only issue I noticed listed for this was the recovery I used.
S1L3nTShaDoWz said:
When installing the GApps package I get this error: E:Error executing updater binary in zip '/data/media/0/sideload.zip'
I originally got a different one but I remembered I was on the "buggy" 2.7.1.1 version so I updated to latest 2.8.1.1 version and well...this. I've wiped my data/cache/system/all of it and repaired the data n cache and then did this all and still a no go. What am I doing wrong? Am I missing something? The only issue I noticed listed for this was the recovery I used.
Click to expand...
Click to collapse
So issue is just with the GApps zip file? Try flashing the ROM then rebooting recovery I had read in my main thread... Also be sure MD5 matches.
bshiznit said:
So issue is just with the GApps zip file? Try flashing the ROM then rebooting recovery I had read in my main thread... Also be sure MD5 matches.
Click to expand...
Click to collapse
Yes originally it was but I managed to fix it by re-doing it all over again w system repair too, though I believe it was doing it over again that fixed it the system repair could've helped. Anyways new issues now, TWRP claims I have no OS....yet here I am....booted in 5.0 w GApps. Oh well nothing to be upset by I guess, least I fixed it.
S1L3nTShaDoWz said:
Yes originally it was but I managed to fix it by re-doing it all over again w system repair too, though I believe it was doing it over again that fixed it the system repair could've helped. Anyways new issues now, TWRP claims I have no OS....yet here I am....booted in 5.0 w GApps. Oh well nothing to be upset by I guess, least I fixed it.
Click to expand...
Click to collapse
Glad to hear it! Sometimes /system remains mounted so TWRP will incorrectly report missing OS
I guess the mic doesn't work, Shazam doesn't work?
Works great so far! Only issue appears to be the volume buttons (when used for notification volume) results in crashing.

Categories

Resources