Hello,
I just installed the latest cyanogen rom (cm-10.1-20130113-NIGHTLY-p990.zip), everything was working fine. Then I installed the latest gapps (gapps-jb-20121212-signed.zip) to get gesture typing, which causes this problem: when I write in an empty input, if I press one letter or after the second word wrote with gesture typing, the keyboard disappears for 5 seconds, then everything works fine.
I did a factory reset, format /system and dalvik cache, but the problem is still here.
Someone has also this bug?
Dreamkey said:
Hello,
I just installed the latest cyanogen rom (cm-10.1-20130113-NIGHTLY-p990.zip), everything was working fine. Then I installed the latest gapps (gapps-jb-20121212-signed.zip) to get gesture typing, which causes this problem: when I write in an empty input, if I press one letter or after the second word wrote with gesture typing, the keyboard disappears for 5 seconds, then everything works fine.
I did a factory reset, format /system and dalvik cache, but the problem is still here.
Someone has also this bug?
Click to expand...
Click to collapse
It is a Rom's bug... Just download Swift Key
Sent from my Optimus 2X with Paranoid Android. Thanks button is here ↓ !!! Just use it
Gjot said:
It is a Rom's bug... Just download Swift Key
Sent from my Optimus 2X with Paranoid Android. Thanks button is here ↓ !!! Just use it
Click to expand...
Click to collapse
Ok, it was a while when you posted in this theme, but I have the same problem with Swift Key. I'm using Paranoid Android latest build.
Professor_Woland said:
Ok, it was a while when you posted in this theme, but I have the same problem with Swift Key. I'm using Paranoid Android latest build.
Click to expand...
Click to collapse
Does this have anything to do with the gapps? What gapps are you using? I think the right ones for Paranoid Android are gapps-jb-20121011. But I think that SwiftKey should work anyway. Is everything ok in "Language & input" in the settings?
filarod said:
Does this have anything to do with the gapps? What gapps are you using? I think the right ones for Paranoid Android are gapps-jb-20121011. But I think that SwiftKey should work anyway. Is everything ok in "Language & input" in the settings?
Click to expand...
Click to collapse
I used to use those, but now I tried Aroma Multipack by tantrums after full wipe and it's still the same... In Language & input I see only Swift Key and I can only go to Swift Key settings from there.
Professor_Woland said:
I used to use those, but now I tried Aroma Multipack by tantrums after full wipe and it's still the same... In Language & input I see only Swift Key and I can only go to Swift Key settings from there.
Click to expand...
Click to collapse
"Instructions:
Coming from another ROM:
Make sure everything is set up properly (correct CWM for your bootloader etc.)
No need for a full wipe you're coming either from a official CM10 old bl or from a CM10 new bl ROM.
Any other ROM: Do a full wipe! Apperantly even needed if you come from CM10.1.
Just do the wipe, you will be thankful afterwards when everything does run better.
Format /system
Choose the correct ROM for your bootloader
Flash ROM + Gapps
Flash the latest kowalski kernel!
Reboot
Don't restore system apps (like Settings) or system data (like Wifi data) with TitaniumBackup!
You'll find a new Settings entry "Paranoid Settings" - to get a first impression of PA choose "Launch" and then "tonyp's profile".
If you want to use adb in recovery, here are my modded adb drivers for ICS.
Updating from a previous version:
Backup your PA Settings (at Settings - Paranoid Settings - Tools)
Download new build
Flash ROM (you don't need to do a full wipe - or any other wipes)
Flash the latest kowalski kernel!
Reboot
done"
You did everything as tonyp said??
filarod said:
"Instructions:
Coming from another ROM:
Make sure everything is set up properly (correct CWM for your bootloader etc.)
No need for a full wipe you're coming either from a official CM10 old bl or from a CM10 new bl ROM.
Any other ROM: Do a full wipe! Apperantly even needed if you come from CM10.1.
Just do the wipe, you will be thankful afterwards when everything does run better.
Format /system
Choose the correct ROM for your bootloader
Flash ROM + Gapps
Flash the latest kowalski kernel!
Reboot
Don't restore system apps (like Settings) or system data (like Wifi data) with TitaniumBackup!
You'll find a new Settings entry "Paranoid Settings" - to get a first impression of PA choose "Launch" and then "tonyp's profile".
If you want to use adb in recovery, here are my modded adb drivers for ICS.
Updating from a previous version:
Backup your PA Settings (at Settings - Paranoid Settings - Tools)
Download new build
Flash ROM (you don't need to do a full wipe - or any other wipes)
Flash the latest kowalski kernel!
Reboot
done"
You did everything as tonyp said??
Click to expand...
Click to collapse
I did, I'm on PA for a while now, but when I saw that crashing I did a full wipe and still nothing.
EDIT: I went from old bootloader to new and for now everything looks fine.
Related
hi, currently i have installed cm9.1 stable for note,
using the philz kernel at 1st then wipe and flash cm,
then i realize is not what i want:
1.no video call?
2.can't do apps re-arrangement like samsung ui did
then i want to roll back to the original rom (the samsung ui),
i follow back the steps and install the philz kernel, then i reboot it,
but when i go in to android it say phone process can't open blah blah blah, then i was terrified,
OH MY GOD!!!!! AM I BRICKED!!????!?!?!?!?!:crying:
and i can't go into the phone ui (cm9),
then i quickly take out the battery, using to old vol up+home+power to go in to the recovery by force,
luckyly i saw the CWMR from philz,
and so i'm restoring the old system now,
i'm not sure in future will there be any problem,
but the main thing is, did i do some thing wrong ?
when you went from CM9 back to Samsung TW, did you do a factory reset ? If not, That is probably what caused your issues.
they are both completely different ROMs so more than likely settings from CM transfered over to TW and resulting in tons of FC's
Its normal so dont panic, Wipes are essential when changing ROMs (unless updating the same ROM) just be sure to be on a safe kernel
azzledazzle said:
when you went from CM9 back to Samsung TW, did you do a factory reset ? If not, That is probably what caused your issues.
they are both completely different ROMs so more than likely settings from CM transfered over to TW and resulting in tons of FC's
Its normal so dont panic, Wipes are essential when changing ROMs (unless updating the same ROM) just be sure to be on a safe kernel
Click to expand...
Click to collapse
im back on TW now, phew scare me out of the dead,
anyway, do u mean that every time on changing kernel or rom i need to do a full wipe, even in restoration?
by the way, backing up a nand, does backup the kernel too, right?
side,
im going to try out [JB:CM10:HYBRID][GT-N7000] PARANOIDANDROID [Utacka] [19 NOV] ,
hope it got the things that i want,
but im not sure bout here:
Make sure to run CM9/10 or an AOSP-based ROM : FLASHING FROM STOCK ICS OR ROMS BASED ON STOCK ICS WILL RESULT IN A BRICK! - You're warned!<<<<<<<<<is this mean the kernel? if i already install philz kernel + in stock ics rooted, can i direct start the wipe section and so on without installing cm9 again?
• [GUIDE] Which Kernels are Safe/Unsafe to Wipe and Flash from <- READ THIS IF YOU ARE CONFUSED
•CWM: YOU NEED TO FULLWIPE IF YOU ARE COMING FROM ANOTHER ROM
•CWM: Install Zip: Rom: http://goo.im/devs/Utacka/n7000
•CWM: Install Zip: Gapps: http://goo.im/gapps/ (latest gapps-jb and even when updating to new PA build)
•Reboot and edit your Apps Dpi & Layout under Settings/Paranoid Settings - DO NOT RESTORE YOUR OLD PROPERTIES FOR NOW
•If you want to explore the various phone modes, tap "Configuration," chose an option, wait for it to finish, then do a manual reboot
•Video tutorial: http://www.youtube.com/watch?v=72Ow-YQeex4
thank you
NooBDroidPlayer said:
im back on TW now, phew scare me out of the dead,
anyway, do u mean that every time on changing kernel or rom i need to do a full wipe, even in restoration?
by the way, backing up a nand, does backup the kernel too, right?
side,
im going to try out [JB:CM10:HYBRID][GT-N7000] PARANOIDANDROID [Utacka] [19 NOV] ,
hope it got the things that i want,
but im not sure bout here:
Make sure to run CM9/10 or an AOSP-based ROM : FLASHING FROM STOCK ICS OR ROMS BASED ON STOCK ICS WILL RESULT IN A BRICK! - You're warned!<<<<<<<<<is this mean the kernel? if i already install philz kernel + in stock ics rooted, can i direct start the wipe section and so on without installing cm9 again?
• [GUIDE] Which Kernels are Safe/Unsafe to Wipe and Flash from <- READ THIS IF YOU ARE CONFUSED
•CWM: YOU NEED TO FULLWIPE IF YOU ARE COMING FROM ANOTHER ROM
•CWM: Install Zip: Rom: http://goo.im/devs/Utacka/n7000
•CWM: Install Zip: Gapps: http://goo.im/gapps/ (latest gapps-jb and even when updating to new PA build)
•Reboot and edit your Apps Dpi & Layout under Settings/Paranoid Settings - DO NOT RESTORE YOUR OLD PROPERTIES FOR NOW
•If you want to explore the various phone modes, tap "Configuration," chose an option, wait for it to finish, then do a manual reboot
•Video tutorial: http://www.youtube.com/watch?v=72Ow-YQeex4
thank you
Click to expand...
Click to collapse
The way I see it , you need a CM 9/10 or AOSP Rom before you should flash paranoid ..
You dont need to wipe everytime, For example, Upgrading Paranoid Android version 1 to Paranoid Android version 2 will NOT necessarily require a full wipe.
But changing from Paranoid Android to Rocket ROM (for example) WILL require a full wipe
You can also full wipe then restore a nandroid, if you wish too. The main thing is to keep regular backups incase something unplanned happens !
azzledazzle said:
You dont need to wipe everytime, For example, Upgrading Paranoid Android version 1 to Paranoid Android version 2 will NOT necessarily require a full wipe.
But changing from Paranoid Android to Rocket ROM (for example) WILL require a full wipe
You can also full wipe then restore a nandroid, if you wish too. The main thing is to keep regular backups incase something unplanned happens !
Click to expand...
Click to collapse
oh i see, im abit understand now,
so, the steps goes on like this,
nand(4.0.4) >> wipe >> cm9 or aosp >> wipe >> pA(4.1.2) >> done
if i want to roll back from pA is
pA(4.1.2) >> wipe >> restore(4.0.4)
is it?
I am currently running V20a EURxx the one that everyone was downloading a while back, via the lg suite hack..
I have installed the all-in-one root tool and "think" i have rooted it but i found it to be very confusing
Cyanogenmod 10.1 (the one that came out yesterday) is what i want. http://forum.xda-developers.com/showthread.php?t=2238040
so.....
What are the steps i have to take? I have rooted and done custom roms in the past but am still kind of a n00b.. Please help a fellow XDA member
ragdoll20 said:
I am currently running V20a EURxx the one that everyone was downloading a while back, via the lg suite hack..
I have installed the all-in-one root tool and "think" i have rooted it but i found it to be very confusing
Cyanogenmod 10.1 (the one that came out yesterday) is what i want. http://forum.xda-developers.com/showthread.php?t=2238040
so.....
What are the steps i have to take? I have rooted and done custom roms in the past but am still kind of a n00b.. Please help a fellow XDA member
Click to expand...
Click to collapse
You have the steps right there in the first post. I'll leave some explanations
You need cwm (clockwordmod recovery) first. The easiest way to install it is via rommanager https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager&hl=en. Use rommanager to flash cwm.
Once cwm is installed. Then proceed.
1. Place cm-10.1-20130416-NIGHTLY-p880.zip and gapps-jb-20130301-signed.zip in to your internal sdcard
- Download cm http://get.cm/get/jenkins/25315/cm-10.1-20130417-NIGHTLY-p880.zip
- Download gapps http://goo.im/gapps/gapps-jb-20130301-signed.zip
- Move the files to your internal sdcard
You need to be in cwm recovery for the next steps. To do this you need to power off your phone, Hold VolUp and Power Button at the same time to power on your phone. Wait till you get to cwm recovery console.
2. BACKUP ALL YOUR DATA with CWM Recovery
- In cwm console select backup. use vol+/vol- to navigate through the menus and use power button to select the option.
3. In CWM Recovery make wipe data/factory reset, wipe cache partition, wipe dalvik cache, format system
- These options can also be found in cwm
4. Flashcm-10.1-20130416-NIGHTLY-p880.zip from sdcard
- Still in cwm. Select Install zip from sdcard -> choose zip from sdcard -> navigate to where you put cm-10.1-20130416-NIGHTLY-p880.zip
5. Gapps-jb-20130301-signed.zip from sdcard
- Still in cwm. Select Install zip from sdcard -> choose zip from sdcard -> gapps-jb-20130301-signed.zip
6. Done
- Reboot
I'm not an expert, but that is how I did it.
ragdoll20 said:
I am currently running V20a EURxx the one that everyone was downloading a while back, via the lg suite hack..
I have installed the all-in-one root tool and "think" i have rooted it but i found it to be very confusing
Cyanogenmod 10.1 (the one that came out yesterday) is what i want. http://forum.xda-developers.com/showthread.php?t=2238040
so.....
What are the steps i have to take? I have rooted and done custom roms in the past but am still kind of a n00b.. Please help a fellow XDA member
Click to expand...
Click to collapse
Actually, the first thing you must do is unlock the bootloader. For now, the only sure versions are EUR-XXX (and to be clear, it's not enough that you installed the Euro-Open FW, your phone must have the software identified as EUR-XXX - for instance, german sim-free phones will be identified as 262-000, even if they install Euro-Open FW, and they don't seem to be unlockable as of yet).
So, check the software version (at system settings -> phone info -> software information -> software version) and, if it's Eur-XXX or something similar, you can unlock the bootloader.
If you're using the all-in-one tool, you just have to follow the instructions on it's thread to unlock the bootloader.
Only then can you install CM with the method akosierwin provided.
Okay i followed the steps and installed clockwork mod via the rom manager...BUT!
If i boot into recovery it says: LG Security,ERROR boot image signature, 5 seconds shut down something something...
Whats that all about? thanks for the fast reply's!
you need to unlock your bootloader first
Yep, unlock your bootloader first.
Here are the steps for that
http://forum.xda-developers.com/showthread.php?t=2224020
Okay i unlocked the bootloader ( when im in the S/W upgrade screen it says unlocked at the top..) i have clockworkmod installed but i cant install anything... All the zips give: assert failed,status 7.. Now im in a bootloop. I can go into clockword mod but thats about it. I have tried other zips than the Nightlys from cyanogen but nothing works. WTF
ragdoll20 said:
Okay i unlocked the bootloader ( when im in the S/W upgrade screen it says unlocked at the top..) i have clockworkmod installed but i cant install anything... All the zips give: assert failed,status 7.. Now im in a bootloop. I can go into clockword mod but thats about it. I have tried other zips than the Nightlys from cyanogen but nothing works. WTF
Click to expand...
Click to collapse
In the general section there's a thread callled flashable CM 10.1 FIX P880 (or similar).
The status 7 error occurs because of a little line (p880 instead of x3 for device recognition).
Install the CM from there or try to reinstall CWM through ROM Manager (should be latest and working)
And don't forget the GApps (from goo.im or the thread with the fixed CM)
EDIT: Link to the fix http://forum.xda-developers.com/showthread.php?t=2238814
ImInMunichBitch said:
In the general section there's a thread callled flashable CM 10.1 FIX P880 (or similar).
The status 7 error occurs because of a little line (p880 instead of x3 for device recognition).
Install the CM from there or try to reinstall CWM through ROM Manager (should be latest and working)
And don't forget the GApps (from goo.im or the thread with the fixed CM)
EDIT: Link to the fix http://forum.xda-developers.com/showthread.php?t=2238814
Click to expand...
Click to collapse
Thanks a bunch! I didnt find that thread, i will try it now!
ImInMunichBitch said:
In the general section there's a thread callled flashable CM 10.1 FIX P880 (or similar).
The status 7 error occurs because of a little line (p880 instead of x3 for device recognition).
Install the CM from there or try to reinstall CWM through ROM Manager (should be latest and working)
And don't forget the GApps (from goo.im or the thread with the fixed CM)
EDIT: Link to the fix http://forum.xda-developers.com/showthread.php?t=2238814
Click to expand...
Click to collapse
IT WORKED!! YOU JUST MADE MY DAY! PM me and i'll give your reward :laugh:
ragdoll20 said:
IT WORKED!! YOU JUST MADE MY DAY! PM me and i'll give your reward :laugh:
Click to expand...
Click to collapse
I'm glad that I helped you, but I really don't want some kind of reward
Just click the thanks button and donate to our developers if you want to give a reward
to the people who deserve it
In the steps for installing CM, there is the advice to do a nandroid backup of the existing system!
Is it possible, after wiping and installing CM 10.1, to restore only data, so I would have all my Apps and Userdata back, or would this cause problems with CM 10.1 settings?
Has someone tried this already?
Is CWM after wiping and installing still present?
Bogeyof said:
In the steps for installing CM, there is the advice to do a nandroid backup of the existing system!
Is it possible, after wiping and installing CM 10.1, to restore only data, so I would have all my Apps and Userdata back, or would this cause problems with CM 10.1 settings?
Has someone tried this already?
Is CWM after wiping and installing still present?
Click to expand...
Click to collapse
CWM ist still installed after CM 10.1 flash.
If you want to have your apps + data back install titanium,
though I don't really know about restoring a backup on CM
(but it's a different android so I think it wouldn't work)
ImInMunichBitch said:
CWM ist still installed after CM 10.1 flash.
If you want to have your apps + data back install titanium,
though I don't really know about restoring a backup on CM
(but it's a different android so I think it wouldn't work)
Click to expand...
Click to collapse
Thanks, but I tried with Titanium Backup on V20a (after wiping and installing V20a over V10h) and not all Apps was correctly restored, settings of system, all the screens of Nova Launcher, the Widgets and their settings and many more was wrong or not restored, so I tried with restoring only "data" from CWM-Backup and it works perfectly...
Anyone tried this on CM 10.1?
Glad that it worked
Didn't know that.
Sent from my LG-P880
ROM's based on original firmware and CM 11 work fine. Doom/Zombie/etc kernels work fine.
But SlimKAT, any official 4.1 or 4.2, Vanir or any other ROM causes hot reboot when opening camera for second time.
First time everything is OK, I can use e.g. PAC ROM for several days, but if I close the camera and open it again (without rebooting) it causes hot reboot. Always.
But CM11 is rock stable so is any original 4.3 and higher.
Any help with that?
Thanx!
slimKAT weekly 5.6's camera works without any problems .bro.
Orangewanted said:
slimKAT weekly 5.6's camera works without any problems .bro.
Click to expand...
Click to collapse
Yes, I know. Once ...
If I start if again it causes hor reboot.
CM 11, stock 4.3/4.4 no problems ...
Z O X said:
Yes, I know. Once ...
If I start if again it causes hor reboot.
CM 11, stock 4.3/4.4 no problems ...
Click to expand...
Click to collapse
Have you done a fresh installation ?
In CWM perform wipe data/factory reset and in mounts and storage section format system.
In TWRP choose advanced in wipe section and wipe dalvik cache, cache, system and data.
or please check your gapps which may cause the problem.
always use the gapps from here http://forum.xda-developers.com/showthread.php?t=2397942
Orangewanted said:
Have you done a fresh installation ?
In CWM perform wipe data/factory reset and in mounts and storage section format system.
In TWRP choose advanced in wipe section and wipe dalvik cache, cache, system and data.
or please check your gapps which may cause the problem.
always use the gapps from here http://forum.xda-developers.com/showthread.php?t=2397942
Click to expand...
Click to collapse
Yes, always fresh.
Point is, even flashed TFT ver 4.1 and 4.2 have same issues. Only 4.3 and 4.4 work OK :-/
Those are the GAPPS I always use ... Don't know. I'll try replacing camera libraries with version that work and see how that goes ...
Oh my Glob...
After visitng service - audio now works fine :victory: - so there was a high time to bring everyting back to normal, which is Kitkat Custom ROM and other stuffs.
So this time I decided to go with CarbonROM 4.4.4.
Eveything was fine, until I restored some apps via TitaniumBackup, and then flashed Tegra4Bin. The system was working on ART. After reboot - nothing works. Apps crash, and when I go into setting - after selecting something from the list - settings crash as well.
think there's a problem with ART and Tegra4Bin - all apps were compiled for different drivers than are now on the phone. How can I fix this? Is there a way to go back to Dalvik? I can't get to developer options as well, so maybe there's a way to change runtime via PC then phone is connected? <- nope nope nope
OK, I managed to get into developer setting via notification about USB debbuging, but still - apps crash. I've also noticed that they can be launched 2-3 second after reboot.
I got to NovaLauncher and then when I try to open any app here, there is only a notification - "app is not installed"
Can I clear apps cache with the option "clear cache" in recovery? I wonder if it only clears apps cache or something more?
EDIT
Ok, nevermind anymore, I did factory reset and reinstalled everything :3
EDIT2 CONCLUSION
There was something with gapps. It seems like CarbonROM has gapps included, so installing another pack was causing crashes. But when I first installed CarbonROM, I also flashed gapps and everything was fine. Well...<--- bull**** :x
Dont think carbon can have gapps included in rom since it is against XDA rules.
dimi89 said:
Dont think carbon can have gapps included in rom since it is against XDA rules.
Click to expand...
Click to collapse
I guess that it isn't the cause of this afterall. And also it surely doesn't have gapps included, it's just "wipe cache" and "wipe data/factory reset" don't delete everything x) it just resets all the data so new ROM can be flashed... am I right?
I alwayse perform full wipe : system and data then catche then dalvik then format system manualy then format /data never had any problems like you described.
Where are all those options in CWM 6.0.4.4 ? If they are there, then I'll definitely find them
EDIT Ok, done ^.^ Thanks for the hint ;]
They are all there some on firat page some in advanced manu and some in second folder from bottom.
I'm tired.... I happened again, which is the third time x.x I don't know if it's because of ROM, or kernel or whatever else... Beanstalk didn't have this issue, but I don't want to accuse CarbonROM of this if I'm not sure if it's ROM's fault
Uh, sorry for double-posting but it happened again and this time it was on Beanstalk 4.4.4 !
I'm really confused... Maybe iodak 9.95 really doesn't work well with 4.4.4 ROMs?
Artisto said:
Uh, sorry for double-posting but it happened again and this time it was on Beanstalk 4.4.4 !
I'm really confused... Maybe iodak 9.95 really doesn't work well with 4.4.4 ROMs?
Click to expand...
Click to collapse
Heck, even my system UI crashes in a loop in official CM11 when I'm on ART.
For some reason, ART causes so many crashes/random restarts and my phone keeps wiping dalvik cache during these restarts.
Stay on dalvik until it becomes more stable.
@UP
I'm on Dalvik since it happend the second time.
I left the phone without battery for the entire night - like it would somehow help. Either way - when I turned it on and got to system the first thing I've done was deleting COMODO Mobile - I noticed that when this app launched after restart, everything began to crash. And guess what?
It seems fine now...
Logs logs logs logs LOOOOOOOOOOOOOOOGSSSSSSSSS
Rudjgaard said:
Logs logs logs logs LOOOOOOOOOOOOOOOGSSSSSSSSS
Click to expand...
Click to collapse
How do I get proper logs?
Anyway, I also noticed that all my gapps were deleted and probably thanks to this system started to work properly. COMODO wasn't the source of issues. So I am almost sure that it was something with gapps for android 4.4.4 - I'll try to flash different gapps or just downgrade to 4.4.2 where everything worked just perfect
I downloaded new Gapps for 4.4.4, changed ROM to official CM11 and today it happened again.
I can't do factory reset - too much data to be lost.
I can't open any app - only error "app is not installed"
Trying to get to any setting in setting menu cause crash.
I can only open apps in 5 seconds, then everything is fudging up.
Is there a way to delete apps from CWM? Or somehow via USB from PC?
Im using nook hd+ with latest cm12.1
When i shut down my nook, it automatically restarts
After like 5 seconds.
Please help me how can i turn off my nook??
Do you have power connected? I'm not sure, but I think the hardware forces a power-on when power is connected.
No the power is not connected
This issue has been discussed at length in #Amaces's thread where this ROM is located.
Have you looked there?
FirePsych said:
This issue has been discussed at length in #Amaces's thread where this ROM is located.
Have you looked there?
Click to expand...
Click to collapse
Thanks. this thread helped a lot.
It seems like this issue has been fixed in latest 08/03 version of CM12.1.
I will try installing this version today.
Thanks.
Does anyone know how I can fully wipe my current CM 12.1 and install new-latest CM12.1 safely?
Is this safe way to do this ?
- insert sd card and reboot in recovery mode
- wipe data / factory reset
- wipe cache partition
- install zip files(recovery/cm12.1/gapps)
- wipe dalvik cache
- reboot
Is this safe way to install cm12.1 - 0803 from my current cm12.1 - 0723??
Thank you
I would reboot after flashing recovery.
Reboot after flashing ROM. Set up the basics. Make a back-up. Flash GAPPS, log into your Google account and set up the basics. Make another back-up , wipe cache/ dalvik,, reboot, and then finish setting up your device.
I think you might want to wipe system to and look into converting Cache and Data to F2FS.
Also, I typically wipe everything 3 times when switching ROMs.
Sent from my XT1060 using Tapatalk
I installed cm12.1 0803 version but i am still having this problem ......
FirePsych said:
I would reboot after flashing recovery.
Reboot after flashing ROM. Set up the basics. Make a back-up. Flash GAPPS, log into your Google account and set up the basics. Make another back-up , wipe cache/ dalvik,, reboot, and then finish setting up your device.
I think you might want to wipe system to and look into converting Cache and Data to F2FS.
Also, I typically wipe everything 3 times when switching ROMs.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Dear sir,
Thank you for your information at my thread.
I am currently running cm 12.1 0803 version with the same auto-restarting problem.
(the shut down functions works sometimes when i shut my nook in landscape mode)
However, I also found out that my Bluetooth mouse is not compatible with CM 12.1 and
I am planning to install cm11 version(because i heard that my mouse works in cm11 version fine).
And i would like to ask you these(I hope you will be kind enough to answer them) :
1. is there a way to make my bluetooth mouse work in CM 12.1 version?
2. which version(date) of cm11 will you recommend me?
3. you mentioned about changing cache and data to fsf2, can you tell me how i can do this? what would be the advantage?
4. you mentioned about wiping everything 3 times, do you wipe 3 times with only booting once? or do you reboot everytime you wipe?
5. Please tell me if this procedure is correct, if i will change my cm 12 to cm 11
- insert sd card and reboot in recovery mode
- wipe data / factory reset
- wipe cache partition
- install recovery and reboot
- install cm rom and reboot
- install gapps and reboot
- format/system(3times?)
- format/data(3times?)
- format/cache(3times?)
- format/bootdata (3times?)
- format/data and sd card (3times?)
- wipe dalvik/cache
- reboot
Thank you.
tnckd13 said:
Dear sir,
Thank you for your information at my thread.
I am currently running cm 12.1 0803 version with the same auto-restarting problem.
(the shut down functions works sometimes when i shut my nook in landscape mode)
However, I also found out that my Bluetooth mouse is not compatible with CM 12.1 and
I am planning to install cm11 version(because i heard that my mouse works in cm11 version fine).
And i would like to ask you these(I hope you will be kind enough to answer them) :
1. is there a way to make my bluetooth mouse work in CM 12.1 version?
2. which version(date) of cm11 will you recommend me?
3. you mentioned about changing cache and data to fsf2, can you tell me how i can do this? what would be the advantage?
4. you mentioned about wiping everything 3 times, do you wipe 3 times with only booting once? or do you reboot everytime you wipe?
5. Please tell me if this procedure is correct, if i will change my cm 12 to cm 11
- insert sd card and reboot in recovery mode
- wipe data / factory reset
- wipe cache partition
- install recovery and reboot
- install cm rom and reboot
- install gapps and reboot
- format/system(3times?)
- format/data(3times?)
- format/cache(3times?)
- format/bootdata (3times?)
- format/data and sd card (3times?)
- wipe dalvik/cache
- reboot
Thank you.
Click to expand...
Click to collapse
1) Shut down and boot into recovery isn't working for me on 8/03 either, but I haven't had time to mess with it to find out why not. Maybe wiping system and then flashing 8/03 might work. I wouldn't wipe Data if you're coming from the last July version of 12.1
But, if you hold down the power button long enough, the tablet will shut down. I just can't shut down from the menu.
Once you're completely off, you can boot into recovery with the power/n combo.
I also tried the Reboot shortcut and widget from ROMToolbox Pro and that didn't work either.
1) I don't know much about how to make bluetooth work. I know that some stuff works on these builds and some stuff doesn't
2) I'm using Amaces's Unofficial CM 12.1. I never found a CM 11 that worked well on my Nook HD+
3) Theoretically,F2FS uses flash memory more efficiently. I think we're talking nano or micro seconds here, but many say it helps. To answer your question about Why and How, I'd have to look it up to give you clear instructions. You can do the same, and you'll learn more by researching it yourself, than by me explaining it poorly.
3) I wipe three times, then reboot
------NOTE---
I'm barely above a novice and my advice isn't worth diddly squat
Below is what generally has worked for ME and what I've read that other folks do. It does not mean this is the best way to do it.
The MOST important thing is to read a lot, then read some more, take your time and make back-ups often.
You need to look in the CM11 threads to see what Recoveries are compatible with CM11. Not all of the current Recoveries are backwards compatible.
AND you're better of asking about flashing to CM11 in a CM11 thread, rather than a CM12 thread.
I don't use an SD, I do everything off of the onboard memory.
I use TWRP as my recovery.
1) If I'm going to a new ROM, rather than do Factory Data Reset, I manually go in and choose to wipe System, Dalvik, Data and Cache. I've never touched BootData as far as I remember. I do that 3 times.
2) Flash new recovery if you want.
3) Reboot into recovery too make sure the new recovery flashed okay.
4) I then flash the ROM, wipe Dalvik and Cache 1 time, boot into the ROM to make sure it was a good flash and set up the bare minimum.
5) Boot to recovery
6) Flash GAPPS and wipe Dalvik and Cache 1 time (usually)
7) Reboot and make sure there were no problems with GAPPS
8) Set up my minimum accounts and apps.
9) Boot to recovery and make a back up.
10) Reboot and install the rest of my apps.
11) Make sure everything works okay and once I'm satisfied, make another back up.
If I'm going from one version of the same ROM to the next update, I just flash the latest version, wipe Dalvik and Cache 1 or 2 times and reboot.
Thereafter, I make back-ups ever week or so, depending on how much I've been using my tablet and how much time I have.