[Q] Phone is incredibly slow after re-flashing CM 11 - General Questions and Answers

I don't know if I missed a step or not, but every app and settings screen now takes about 20-30 seconds to open, booting takes 3-5 minutes. The phone is set up with the same ROM, kernel, apps, etc. as a few weeks ago when it was running super-fast.
I reflashed this version of CM 11 which had worked perfectly for me for about a month (this is a Samsung Galaxy Blaze S 4G):
cm-11-20150119-NIGHTLY-t769.zip
I was downgrading back to that after trying a nightly that made staticky lines all over my phone and made it lock up constantly...
When I reflashed, here's what I did (after backing up with TiBu):
In recovery I wiped to factory
Cleared the cache and Dalvik cache
Formatted /system and /data
Flashed the zip of CM 11 from my external SD
Flashed the zip of GaPPs from the external SD
Rebooted
Rebooted fine, I installed TiBu and Link2SD and started restoring apps/moving to 2nd SD card partition.
The phone is much much slower than stock. I don't know what the difference is... can someone please give me a checklist to try or tell me what I might have done wrong in the re-flashing process?

kanjigirl said:
I don't know if I missed a step or not, but every app and settings screen now takes about 20-30 seconds to open, booting takes 3-5 minutes. The phone is set up with the same ROM, kernel, apps, etc. as a few weeks ago when it was running super-fast.
I reflashed this version of CM 11 which had worked perfectly for me for about a month (this is a Samsung Galaxy Blaze S 4G):
cm-11-20150119-NIGHTLY-t769.zip
I was downgrading back to that after trying a nightly that made staticky lines all over my phone and made it lock up constantly...
When I reflashed, here's what I did (after backing up with TiBu):
In recovery I wiped to factory
Cleared the cache and Dalvik cache
Formatted /system and /data
Flashed the zip of CM 11 from my external SD
Flashed the zip of GaPPs from the external SD
Rebooted
Rebooted fine, I installed TiBu and Link2SD and started restoring apps/moving to 2nd SD card partition.
The phone is much much slower than stock. I don't know what the difference is... can someone please give me a checklist to try or tell me what I might have done wrong in the re-flashing process?
Click to expand...
Click to collapse
Hi
There are newer versions of CM11 t769 up already.
You should wipe cache and dalvik after restoring your apps. If it doesn't help, make a clean installation of cm and try if the speed is better. Restoring apps via Titanium Backup while using Link2SD can easily cause errors. May be you have reinstall apps without restore. Also new partitioning of your sd card could help.

LS.xD said:
Hi
There are newer versions of CM11 t769 up already.
You should wipe cache and dalvik after restoring your apps. If it doesn't help, make a clean installation of cm and try if the speed is better. Restoring apps via Titanium Backup while using Link2SD can easily cause errors. May be you have reinstall apps without restore. Also new partitioning of your sd card could help.
Click to expand...
Click to collapse
How do I choose a version of CM to use?? This is new to me, just rooted for the first time last month. I don't know how to choose... I was using that one I mentioned above for a month with zero issues, then upgraded to a new nightly, but had to downgrade back due to problems and that was where my issue here started...
I did wipe cache and Dalvik after restoring my apps, and I did repartition my SD card as Link2SD wasn't working for me after reflashing (I got a new beta version of Link2SD from the developer that worked perfectly).

kanjigirl said:
How do I choose a version of CM to use?? This is new to me, just rooted for the first time last month. I don't know how to choose... I was using that one I mentioned above for a month with zero issues, then upgraded to a new nightly, but had to downgrade back due to problems and that was where my issue here started...
I did wipe cache and Dalvik after restoring my apps, and I did repartition my SD card as Link2SD wasn't working for me after reflashing (I got a new beta version of Link2SD from the developer that worked perfectly).
Click to expand...
Click to collapse
The CM11 builds are sorted by date. Newest build CLICK HERE are always on the top. Latest is 02/23. Keep in mind that CM is still under develpoment and may not run stable.

LS.xD said:
The CM11 builds are sorted by date. Newest build CLICK HERE are always on the top. Latest is 02/23. Keep in mind that CM is still under develpoment and may not run stable.
Click to expand...
Click to collapse
Should I pick the newest build then, and reflash with that? I see there's a stable one for CM 10 for my phone, but it's from 2012...
Should I go with something other than CM? I'm just confused at this point. I like Kitkat and would like to stay with that if feasible (my stock phone was ICS).

kanjigirl said:
Should I pick the newest build then, and reflash with that? I see there's a stable one for CM 10 for my phone, but it's from 2012...
Should I go with something other than CM? I'm just confused at this point. I like Kitkat and would like to stay with that if feasible (my stock phone was ICS).
Click to expand...
Click to collapse
I haven't tested the builds as i don't have the phone, its usefull to read the CM11 thread for your phone to check out bugs. You can try newer builds, but theres no guarantee that everything works. All in all you should go for newer versions from time to time

LS.xD said:
I haven't tested the builds as i don't have the phone, its usefull to read the CM11 thread for your phone to check out bugs. You can try newer builds, but theres no guarantee that everything works. All in all you should go for newer versions from time to time
Click to expand...
Click to collapse
Hmm. My build was stable, I upgraded to a new one, and my phone stopped working. Going back isn't working either.
CM 10.0 is listed as a stable release, I'm wondering if that would be better (i.e. less time spent wiping and reflashing repeatedly) than a new nightly for CM 11?

kanjigirl said:
Hmm. My build was stable, I upgraded to a new one, and my phone stopped working. Going back isn't working either.
CM 10.0 is listed as a stable release, I'm wondering if that would be better (i.e. less time spent wiping and reflashing repeatedly) than a new nightly for CM 11?
Click to expand...
Click to collapse
CM10 = Android 4.1.2
CM10.1 = Android 4.2.2
CM10.2 = Android 4.3.1
CM11 = Android 4.4.4
CM12 = Android 5.0.2
CM10 means you have NO bugs, everything runs stable at the cost that you have a really old rom. If you don't like maintain your phone continuisly its a good choice. I really like trying new stuff, so i flash nearly every new build of used roms / kernels for my phones. So I would stay at CM11. But thats just my personal opinion. By the way you don't need to create backups with Titanium Backup all the time. Just make a backup with your recovery. After installing a new rom, use Titanium Backup with the option "Extract from nandroid backup" to restore your apps. On previous phones I also used tools like Link2SD or Int2Ext, but after some time it always caused problems and never ran 100% stable and fast, so think about if you really need it.

LS.xD said:
CM10 = Android 4.1.2
CM10.1 = Android 4.2.2
CM10.2 = Android 4.3.1
CM11 = Android 4.4.4
CM12 = Android 5.0.2
CM10 means you have NO bugs, everything runs stable at the cost that you have a really old rom. If you don't like maintain your phone continuisly its a good choice. I really like trying new stuff, so i flash nearly every new build of used roms / kernels for my phones. So I would stay at CM11. But thats just my personal opinion. By the way you don't need to create backups with Titanium Backup all the time. Just make a backup with your recovery. After installing a new rom, use Titanium Backup with the option "Extract from nandroid backup" to restore your apps. On previous phones I also used tools like Link2SD or Int2Ext, but after some time it always caused problems and never ran 100% stable and fast, so think about if you really need it.
Click to expand...
Click to collapse
Ack. Well... I like Kitkat a lot. I might get the latest CM11 nightly and new GAPPS and try that first.
I have so little memory, kept running out of space and that's why I use Link2SD. But thanks for the advice on TiBu, I did make a Nandroid backup last night from CWM.

kanjigirl said:
Ack. Well... I like Kitkat a lot. I might get the latest CM11 nightly and new GAPPS and try that first.
I have so little memory, kept running out of space and that's why I use Link2SD. But thanks for the advice on TiBu, I did make a Nandroid backup last night from CWM.
Click to expand...
Click to collapse
PA GApps are quite good and still up-to-date. Use "PICO" to save some space.

LS.xD said:
PA GApps are quite good and still up-to-date. Use "PICO" to save some space.
Click to expand...
Click to collapse
That looks great, thanks very much!
I'll post back here once I get my phone straightened out in the next couple of days to say what happened, in case it helps someone later.

Possibly stupid question - do I need to do anything with the kernel or pit if I'm just installing a new ROM? That was only for rooting, right?

kanjigirl said:
Possibly stupid question - do I need to do anything with the kernel or pit if I'm just installing a new ROM? That was only for rooting, right?
Click to expand...
Click to collapse
Kernel is always included in the new "rom". So everytime you flash a rom, you automatically flash the kernel with it. PIT is the partition table of the phones partition. As long its not clearly necessary, DON'T ever change it!

Got it, thank you for your help!

So last night I wiped the phone and flashed the latest CM 11 (from yesterday) and the Pico package from PA-GApps. The phone is now super-fast again. I restored a few key apps to try out for the next day or so before restoring the rest, but so far so good, everything is back to normal. Thank you so much for the help.

kanjigirl said:
So last night I wiped the phone and flashed the latest CM 11 (from yesterday) and the Pico package from PA-GApps. The phone is now super-fast again. I restored a few key apps to try out for the next day or so before restoring the rest, but so far so good, everything is back to normal. Thank you so much for the help.
Click to expand...
Click to collapse
Sounds great

Quick question - if this thread is still open. The phone's been fine since I flashed CM 11 and Pico GApps, until this morning, when it now does 'Android is Upgrading' every time I boot and every user app crashes as soon as it's opened. I have all auto-syncs and auto-updates disabled, and haven't added any user apps to the phone since Wednesday.
Do I need to flash again, and then have to go through the restore process all over? Or could it be an app causing this? I'm not sure where to look for a source of the problem.

Related

sudden constant reboots and less internal memory?

Ive been running the same CM7 nightly for a while ( current version in sig)
and a few weeks ago upgraded to a 32GB micro SD.
everything seemed fine for weeks until last week. I have been getting random reboots and now it reboots and stays sluggish for about 1 min then reboots again. it doesnt have time to load all my apps so i cant titanium backup and USB wont connect.
as far as memory the external card reads 32 but internal reads 5 with 62mbs left, I thought it was 8gb?
Im not sure what happened as I didnt change anything. I wanted to finally update the rom and it started going crazy today
decided to reboot to recovery and install the latest nightly on top of everything. if that works Ill back up settings & apps and factory reset before i try again.
I wish this damn phone would just work and stay working, if its not one thing its another.
If just flashing the new nightly doesn't work I'd recommend wiping it completely and reflashing everything from a clean slate. It's a little more work but it should fix the random reboots and the sluggishness. As for the loss of internal space, that's usually a custom ROM issue. I don't think I've had all 8 gigs of mine available since my G2X was running stock (which was quite a few ROMs ago)
---------- Post added at 02:29 PM ---------- Previous post was at 02:25 PM ----------
And a lot of ROMs will also just mount the remaining space under a separate internal SD paritition.
ehafling said:
If just flashing the new nightly doesn't work I'd recommend wiping it completely and reflashing everything from a clean slate. It's a little more work but it should fix the random reboots and the sluggishness. As for the loss of internal space, that's usually a custom ROM issue. I don't think I've had all 8 gigs of mine available since my G2X was running stock (which was quite a few ROMs ago)
---------- Post added at 02:29 PM ---------- Previous post was at 02:25 PM ----------
And a lot of ROMs will also just mount the remaining space under a separate internal SD paritition.
Click to expand...
Click to collapse
that was the plan, just flashed long enough to get it stable to back up apps & settings. I always wipe cache ect between nightlies and always full wipe between different roms or major build changes. this time I didnt change or do anything and it just starting going crazy.
flashed the newest nightly and was better but not long enough to backup. had to delete a bunch of apps to get some memory back. which again is odd because I had plenty before and havent installed any new apps.
at any rate I have been using my old N1 with an early CM7 rom and its fine. about to wipe and flash the G2X now. BTW I haven't searched yet but is the newest base band flashable to the CM7 roms yet? i really dont want to flash a stock rom ect
Sounds like its your phone and not roms, and yes cm7 rc3 and the 5-27 nightly are okay with the latest baseband. you have to use a lg tool or OTA to change basebands though.
Sent from my LG-P999 using xda premium
Spoo76 said:
BTW I haven't searched yet but is the newest base band flashable to the CM7 roms yet? i really dont want to flash a stock rom ect
Click to expand...
Click to collapse
Basebands can only be updated with LG's software (which checks for a stock ROM), just do a Nandroid backup of your current ROM, download a stock Nandroid backup, restore to it, run LG software update to get new BB, then nandroid restore your ROM, wipe caches, and flash latest CM7 nightly. Guide links are in my signature.
mt3g said:
Sounds like its your phone and not roms, and yes cm7 rc3 and the 5-27 nightly are okay with the latest baseband. you have to use a lg tool or OTA to change basebands though.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Im still not sure what it was, but it seems fine now.
I flashed the latest nightly on top.
got it stable enough to titanium backup recent MMS ( so handy for work!)
restore to factory.
wipe internal SD ( which I haven't done in a while )
I knew the roms worked with the new baseband, just thought it was flashable from recovery with a file. I thought that's how i got the july 15.
Whyzor said:
Basebands can only be updated with LG's software (which checks for a stock ROM), just do a Nandroid backup of your current ROM, download a stock Nandroid backup, restore to it, run LG software update to get new BB, then nandroid restore your ROM, wipe caches, and flash latest CM7 nightly. Guide links are in my signature.
Click to expand...
Click to collapse
Thanks! I didnt even think to use a Nandroid
BTW I just noticed the in CM settings the "use internal storage" check box.
I just rebooted after clicking it. seems this just swapping internal memory with internal SD?
EDit, after reboot it looks like it just swaps the default location for the "store to SD" feature. I was hopping it was like Apps2SD was on my N1
Thanks again everyone. Haven't been that frustrated with android in a while. usually I don't get problems until i mess with something.
Well the phone is running smooth other than when in a call. speaker & mic don't seem to work. both work for other apps. also happened when i flashed on top, but after I wiped it was fine until work today. still on the baseband from the 15th. wont have time to try the new one till tomorrow

[Q] Help, stuck in bootloop with CM 10 ROM

So I was able to successfully root my AT&T HTC One X and decided I wanted to install the CM 10 ROM (1st ROM install). I did all the data backups with Titanium, downloaded the latest zip files from cyanogenMod (both the 12/13 and 12/14 nightly versions), transferred them to my phone, booted into recovery (TWRP), did a back-up, did a system wipe, flashed the ROM and then did a reboot. However, when it boots it gets stuck in the boot-up screen (bootloop) and doesn't do anything. I have read on this and it keeps saying to wipe system data again and flash the ROM again and it keeps doing this. I want to install this ROM, but I need some help. Any suggestions on what I did wrong?
Note: I accidentally posted this in the Android Q&A section, so I apologize for the double post. I just think this is probably the best place to get my answer.
Did you flash the boot.img?
I did, but incorrectly the first time. I flashed it the right way and everything is working good. Then only problem I have now is when restoring from Titanium Backup it gives me an error from a process called com.android.phone (I think that is what it said). So I wiped it again and rebooted and everything is fine. I can reinstall all the apps, but what could cause that? Could it be some of the data backed up doesn't cooperate with this ROM? Either way I love the CM10 ROM.
jon8105 said:
I did, but incorrectly the first time. I flashed it the right way and everything is working good. Then only problem I have now is when restoring from Titanium Backup it gives me an error from a process called com.android.phone (I think that is what it said). So I wiped it again and rebooted and everything is fine. I can reinstall all the apps, but what could cause that? Could it be some of the data backed up doesn't cooperate with this ROM? Either way I love the CM10 ROM.
Click to expand...
Click to collapse
if they are backups from sense, that *MAY* cause problems, but don't quote me on that. I don't use sense, can't say for sure
OK, maybe that is why. Not a big deal since I haven't had the One X too long. Thanks for the help guys.
Good to know

upgrade one a from 4.1.2

i have CM10 and android 4.1.2 on my one x (att), i want to upgrade to 4.2.2.
if i install the new rom and gapps do i need to flash a new boot.img or will the one i have still work?
also what is the best way to restore my settings to the new version? i spent lots of time setting this phone up with and and i'd prefer to migrate as much as possible. I would appreciate if if you treated me as a newbie with the migration and are descriptive in your response as i have never done this before.
TIA
You can probably find out more about upgrading from CM10 to 10.1 by looking through the 10.1 thread. I'm almost entirely a Sense person, so I can't speak specifically to this situation (moving from CM10 to 10.1). But seeing as you are moving from one Android build to another, I'd assume you need to treat it as moving to a "new" ROM. I would also bet that you need to flash boot.img again. It only takes a minute to do, so why bother even trying to skip that step?
In general, if moving from one ROM to another, you should wipe user data, and not migrate system data, and migrate as few settings as possible. Migrating system data is almost sure to cause serious bugs, and migrating settings can be problematic also.
Recommend using Titanium Backup to migrate apps and data (but not system data), and if you get the paid version, its well worth the couple dollars to get the batch function (can backup and restore all your user apps with just a couple taps).
Do any other backing up you want to do (I like to backup my text messages by using the app SMS Backup+). And if you like, use TWRP to make a nandroid backup, in case you want to revert to your current ROM.
Then before flashing CM10.1 factory reset only within TWRP (factory reset in hboot will corrupt your SD card). Factory reset will wipe any user data (but should leave the internal SD untouched). So be sure to backup anything you want to keep, beforehand. Then wipe Dalvik and cache, also within TWRP. Then flash the ROM, boot.img and gapps. Then startup the ROM, restore your apps with Titanium. Then setup your homescreen and settings to your liking. Some people also like to migrate WiFi and Bluetooth pairings (I think Titanium will do it). Especially handy if you have a lot of pairings. But I don't have many pairings, and migrating them never seemed to work right for me, so I just do it manually.
Really, setting up from scratch is not that hard. With the help of Titanium, I can be back up and running in about 20 minutes.
You shouldn't have to flash a new boot just flash the new Rom over the old one. As long ast there there both cm something your good. But make a backup in recovery just on case
Sent from my HTC One X using xda premium
Arrow44 said:
As long ast there there both cm something your good. But make a backup in recovery just on case
Click to expand...
Click to collapse
I don't think you mean that literally. If you were to go from CM9 to CM10, and not flash the kernel, I don't think that would work.
Even going from CM10 to CM10.1, it would require the kernels being the same, or at least similar enough to not cause any problems. Have you tried this yourself, or read others tried it on the CM thread?
Are you sure you aren't thinking of just going from one nightly to another?
Also assume the OP is hboot 1.14 or higher, and S-on. Otherwise flashing boot.img separately is not an issue at all.
redpoint73 said:
I don't think you mean that literally. If you were to go from CM9 to CM10, and not flash the kernel, I don't think that would work.
Even going from CM10 to CM10.1, it would require the kernels being the same, or at least similar enough to not cause any problems. Have you tried this yourself, or read others tried it on the CM thread?
Are you sure you aren't thinking of just going from one nightly to another?
Also assume the OP is boot 1.14 or higher, and S-on. Otherwise flashing boot.img separately is not an issue at all.
Click to expand...
Click to collapse
thanks for the relies, i backed it all up this morning and tried to flash the latest nightly and the htc screen just hung, so im guessing i need to flash the boot.img, i need to do that home where i have the android sdk tools installed.
as far as migrating the data, im guessing that's not practical with what appears to be two separate builds... sigh, the 10.1 night came out a week after installed cm 10. oh well at least im not still waiting for slow ass ATT to get me the update.
mike_311 said:
thanks for the relies, i backed it all up this morning and tried to flash the latest nightly and the htc screen just hung, so im guessing i need to flash the boot.img, i need to do that home where i have the android sdk tools installed.
as far as migrating the data, im guessing that's not practical with what appears to be two separate builds... sigh, the 10.1 night came out a week after installed cm 10. oh well at least im not still waiting for slow ass ATT to get me the update.
Click to expand...
Click to collapse
Sorry I come from sense based roms but I have a feeling you haven't heard of flash gui. http://forum.xda-developers.com/showthread.php?t=1453617
Sent from my HTC One X using xda premium

[Q] BMM and custom rom

Just out of curiosity, does anyone else having lag, slowdown and force close issue when using rom with bmm? I have tried Cm, PAC, Aokp, Mokee and many more, but keep having serious lag issue and fc after few hours of usage, and keep having to reboot my phone so that it is usable again.
I've tried putting 2gb for system.img, data .img and cache.img on bmm0.3.2, and 1gb for bmm 0.3.4( for some reason 2gb doest work), but to no avail
Just curious if its only an issue with my phone or everyone else is facing the same thing
faridr said:
Just out of curiosity, does anyone else having lag, slowdown and force close issue when using rom with bmm? I have tried Cm, PAC, Aokp, Mokee and many more, but keep having serious lag issue and fc after few hours of usage, and keep having to reboot my phone so that it is usable again.
I've tried putting 2gb for system.img, data .img and cache.img on bmm0.3.2, and 1gb for bmm 0.3.4( for some reason 2gb doest work), but to no avail
Just curious if its only an issue with my phone or everyone else is facing the same thing
Click to expand...
Click to collapse
never have that prob.. my basic set ups is 500sys 1GBdat 300cache
hafizkris90 said:
never have that prob.. my basic set ups is 500sys 1GBdat 300cache
Click to expand...
Click to collapse
That was one of my first setting, it was the recommended size I've read somewhere, i guess the issue is down to my phone.
Fxz back to 4.1.2 jb leak 3, running fine, but damn how I miss the quick setting panel on 4.2.2 rom
faridr said:
That was one of my first setting, it was the recommended size I've read somewhere, i guess the issue is down to my phone.
Fxz back to 4.1.2 jb leak 3, running fine, but damn how I miss the quick setting panel on 4.2.2 rom
Click to expand...
Click to collapse
Hi,
same problem here. Hope you solved it. If so, could you please share it here?
10q.
amplatfus said:
Hi,
same problem here. Hope you solved it. If so, could you please share it here?
10q.
Click to expand...
Click to collapse
Did not manage to solve it, but instead running non-kexec cm10.1, which seems to work just fine. I guess there's something wrong with kexec and my phone
faridr said:
Just out of curiosity, does anyone else having lag, slowdown and force close issue when using rom with bmm? I have tried Cm, PAC, Aokp, Mokee and many more, but keep having serious lag issue and fc after few hours of usage, and keep having to reboot my phone so that it is usable again.
I've tried putting 2gb for system.img, data .img and cache.img on bmm0.3.2, and 1gb for bmm 0.3.4( for some reason 2gb doest work), but to no avail
Just curious if its only an issue with my phone or everyone else is facing the same thing
Click to expand...
Click to collapse
It depends upon the ROM ur using try giving a higher partition on the systems ur facing trouble with wnd ur problem is sure to go away !!!!
coz 1 thing 4 sure ATRIX 2 never lags (atleast mine doesnt )
and use arnd 800 to a gig for the partitions they should do just fine ......
Press on the Thanks button if it helped.......
Better Gadget but Not a good phone
faridr said:
Just out of curiosity, does anyone else having lag, slowdown and force close issue when using rom with bmm? I have tried Cm, PAC, Aokp, Mokee and many more, but keep having serious lag issue and fc after few hours of usage, and keep having to reboot my phone so that it is usable again.
I've tried putting 2gb for system.img, data .img and cache.img on bmm0.3.2, and 1gb for bmm 0.3.4( for some reason 2gb doest work), but to no avail
Just curious if its only an issue with my phone or everyone else is facing the same thing
Click to expand...
Click to collapse
Hey,
TO me, they are very quick and good interface providers, First when i started using custom roms main thing bothered me is camera. How many camera apps i try results in no use. BY the time (continues updation by developers ) Now it is fun and pleasure to use custom rom. BUt some times they showing blank image and no ringtone when some call is coming, that is the only reason we use phone for (to call n receive) and so to avoid custom rom for.(weak signal reception of custom roms than my stock rom). some roms even restart as when they want to.
according to me, roms good to bad on my atrix2 are
mokee pac(battery drain) aokp pa.......bad :slim cm dirtyunicorn
Regards
Nani7
Custom ROM on System 1
Can anyone please let me know on, how do I install a custom rom (e.g.Slimbean edision) onto system 1 using BMM.
I am already using JB 4.1. Leak 3 on system1 and Slim Bean 4.3 on system3. I wish to install slimbean to system1.
Do I have to follow the same steps as noted through the rom installation process. If so, will it create a problem to BMM as it is installed on system1.
I have searched the forum for such issue, but couldn't find a proper tag.
Thank you to all developers for creating such a wonderful ROMs and Mods for Atrix 2.
neelz369 said:
Can anyone please let me know on, how do I install a custom rom (e.g.Slimbean edision) onto system 1 using BMM.
I am already using JB 4.1. Leak 3 on system1 and Slim Bean 4.3 on system3. I wish to install slimbean to system1.
Do I have to follow the same steps as noted through the rom installation process. If so, will it create a problem to BMM as it is installed on system1.
I have searched the forum for such issue, but couldn't find a proper tag.
Thank you to all developers for creating such a wonderful ROMs and Mods for Atrix 2.
Click to expand...
Click to collapse
Just wipe and flash. BMM will remain there.
neelz369 said:
Can anyone please let me know on, how do I install a custom rom (e.g.Slimbean edision) onto system 1 using BMM.
I am already using JB 4.1. Leak 3 on system1 and Slim Bean 4.3 on system3. I wish to install slimbean to system1.
Do I have to follow the same steps as noted through the rom installation process. If so, will it create a problem to BMM as it is installed on system1.
I have searched the forum for such issue, but couldn't find a proper tag.
Thank you to all developers for creating such a wonderful ROMs and Mods for Atrix 2.
Click to expand...
Click to collapse
The reason it is suggested that custom ROMs be installed on system 3 and up is because bmm is not the same as most other recoveries. It is installed in the system folder rather than on a separate partition. If you have a problem with whatever is on your first system it could cause you to loose the bmm recovery forcing you to flash an fxz and start over. This is also the reason that a factory reset on first system will wipe ALL other systems. As a general rule you should follow all instructions to have the best possible experience. You can always change the default system in bmm to have it automatically boot the system of your choice.
If I had a dollar for every time I said that, I'd be making money in a very weird way.
hi
hi, i have installed cm 10.2 unofficial JB4.3 on system 3.. but rotation not working.. and other roms are working fine.. i am using main system as JB china leak and miui on my atrix 2
I never have that issue..,except force close issue but maybe its because of my fault i tought...
actually i never use custom rom as my main system,so i have 3rd,4th,5th n 6th system to test a custom rom ...
i try diffrent tweak,mod,script like Fly on Mod,V6 Supercharger,Operation Killjoy etc ... and it works very well ...
So AFAIK, we should never do something stupid on BMM 1st system.., and we will be fine to use BMM recovery and want to playing safe with this device..
That my opinion... Happy multi booting .....
neelz369 said:
Can anyone please let me know on, how do I install a custom rom (e.g.Slimbean edision) onto system 1 using BMM.
I am already using JB 4.1. Leak 3 on system1 and Slim Bean 4.3 on system3. I wish to install slimbean to system1.
Do I have to follow the same steps as noted through the rom installation process. If so, will it create a problem to BMM as it is installed on system1.
I have searched the forum for such issue, but couldn't find a proper tag.
Thank you to all developers for creating such a wonderful ROMs and Mods for Atrix 2.
Click to expand...
Click to collapse
PLease dont flash anything new on System 1 you will lose all the data on the remaining systems and you could end up screwing up everything.....
Just flash it on any other system leave the system 1 alone..........
---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------
buddykartz said:
hi, i have installed cm 10.2 unofficial JB4.3 on system 3.. but rotation not working.. and other roms are working fine.. i am using main system as JB china leak and miui on my atrix 2
Click to expand...
Click to collapse
Use the JBX kernel for the ROM it should solve your rotation problem its a common problem with the new 4.3 ROM s
Just flash the JBX kernel on the system your using the ROM on and wipe cache and davlik ..........(Use 1.xx series on the kernel for 4.3 ROM's)
http://forum.xda-developers.com/showthread.php?t=2320784 :laugh:
Thank you
darth_nihar said:
PLease dont flash anything new on System 1 you will lose all the data on the remaining systems and you could end up screwing up everything.....
Just flash it on any other system leave the system 1 alone..........
---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------
Use the JBX kernel for the ROM it should solve your rotation problem its a common problem with the new 4.3 ROM s
Just flash the JBX kernel on the system your using the ROM on and wipe cache and davlik ..........(Use 1.xx series on the kernel for 4.3 ROM's)
http://forum.xda-developers.com/showthread.php?t=2320784 :laugh:
Click to expand...
Click to collapse
Thank you.. I will try this
bmm backup
Is there a way to make a reliable nandroid with bmm or other recovery. I tried using the backup via bmm. When I went to restore, it kept failing, even when trying on a clean system. After about the sixth attempt, it finally recovered, but only reinstalled three apps, and was missing some system apps like the camera.
Thanks for any advicez
mkinsocal said:
Is there a way to make a reliable nandroid with bmm or other recovery. I tried using the backup via bmm. When I went to restore, it kept failing, even when trying on a clean system. After about the sixth attempt, it finally recovered, but only reinstalled three apps, and was missing some system apps like the camera.
Thanks for any advicez
Click to expand...
Click to collapse
Why don't you try Titanium Backup it has a update.zip package option which will restore all your apps and settings if it is only the apps your worried about..........
https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup&hl=en
:laugh:
darth_nihar said:
Why don't you try Titanium Backup it has a update.zip package option which will restore all your apps and settings if it is only the apps your worried about..........
:laugh:
Click to expand...
Click to collapse
Thanks. I do use TiBu but have not used the zip option. I think my main concern was having to restore all of my settings, widgets, homesrceens, etc. My guess is that TiBu zip doesn't do that, correct? It just reinstalls the apps, right?
mkinsocal said:
Thanks. I do use TiBu but have not used the zip option. I think my main concern was having to restore all of my settings, widgets, homesrceens, etc. My guess is that TiBu zip doesn't do that, correct? It just reinstalls the apps, right?
Click to expand...
Click to collapse
Yes, you are correct. You really don't want to use TiBu to restore system apps and settings. It's really only good for user apps and the zip does do that well. Not to mention that it is not at all relevant to your question about BMM. (Some people don't read the questions properly and give bad advice as a result of inexperience.)
As for your problem, I would say that you should make sure that you're using the fast backup option in BMM and make sure that the partitions you set up are large enough for what you're trying to restore.
If I had a dollar for every time I said that, I'd be making money in a very weird way.
hi,
i have a question regarding BMM and kexec.
are kexec roms of slot 3 to 6 related with rom (said stock) of slot 1??
i had been noticed that if i changed some system setting of slot 1, my kexec roms get more stable.
i used pimp my rom at slot 1, and did not know that it changed my system a lot. i used its restore function but did not work.
thus i reverted it back one by one, i guess, there are some left.
as soon as i reverted back, my kexec roms at slot 3 to 5 run longer than before.
mkinsocal said:
Thanks. I do use TiBu but have not used the zip option. I think my main concern was having to restore all of my settings, widgets, homesrceens, etc. My guess is that TiBu zip doesn't do that, correct? It just reinstalls the apps, right?
Click to expand...
Click to collapse
Ya just reinstalls the apps and data like i said ..........if thats all you wanted its a good option
as badwolf said it just might be that your not setting aside enough space for the full backup
Have a look at ur partition size and then go ahead with your earlier steps....
(@1BadWolf i was just giving him a suggestion which you always fail to realize)

[Q] Wondering what to expect by an overwrite of a ROM?

I was tinkering with my TF101 and sort of accidentally (lol) overwrote my installation of Timduru's KatKiss-4.3.1_029.zip with his KatKiss-4.4.2_016.zip without wiping anything before doing so. (Actually didn't have any data to speak of - as I formatted and wiped in proper fashion on the install of KatKiss-4.3.1_029), and it hadn't been run for more than a couple of days.
I've developed a severe addition to ROM experimentation, and so may install and backup every few days it seems. Don't have a nickname for that habit yet, but I sense that they are many similar addicts around this site.
What I would like to know, since all seems, at least to this n00b, to be just fine - what "might" happen w/ my TF101 since the overwrite of a newer ROM?​
Staying put, until I hear from a forum guru, or at least anyone with more experience than me (and that will include most all members).
Thanks,
Cal
If you overwrite a ROM with a different one (different android version, or by a different developer) you may run into issues where it will not boot, or it may run poorly, random reboots, sleep o death.
When changing ROMs it is HIGHLY recommended to wipe the system, caches and the data partition (wiping data is not the same as FORMAT DATA in TWRP). There are some system settings stored in the /data/ partition that may conflict with different ROMs.
Most of TimDuru's KatKiss ROMs you can forward flash (even to new versions of Android) but you CANNOT go backwards. I flashed from 4.2.2 to 4.3 without wiping data and had no issues. However, if you tried to flash from 4.3 to 4.2.2 without wiping data, it will not boot until you wipe the data partition.
I have not tried this with the 4.4 version of his ROM (I am still on 4.3 for now.)
Oh, and yes, the addiction is called CrackFlashing.
Always ALWAYS make a backup in TWRP before flashing a new ROM or even an upgrade to the current ROM. If you want to go back to 4.3, make a backup and then use Titanium Backup Pro version to extract any apps and data from the 4.4 version and restore to 4.3. Do not restore any system settings or apps.
frederuco said:
<snipped a bit>
When changing ROMs it is HIGHLY recommended to wipe the system, caches and the data partition (wiping data is not the same as FORMAT DATA in TWRP). There are some system settings stored in the /data/ partition that may conflict with different ROMs.
Most of TimDuru's KatKiss ROMs you can forward flash (even to new versions of Android) but you CANNOT go backwards. I flashed from 4.2.2 to 4.3 without wiping data and had no issues. However, if you tried to flash from 4.3 to 4.2.2 without wiping data, it will not boot until you wipe the data partition.
Oh, and yes, the addiction is called CrackFlashing.
Always ALWAYS make a backup in TWRP before flashing a new ROM or even an upgrade to the current ROM. <some stuff snipped>
Click to expand...
Click to collapse
Ahh...then the addiction is obviously not curable unless one destroys the tablet, BUT the new ROM may be just fine as is, I take it. That was what I was hoping to hear.
Thanks, and any idea when a new experimental ROM will come from Tim? Just felt a slight twitch. I've tried the other team's creations and seem to only feel really satisfied with Kits - (guess 'CrackFlashing' addiction picks a really hard one to withdraw from).
Many thanks!
Cal
Cal-123 said:
Ahh...then the addiction is obviously not curable unless one destroys the tablet, BUT the new ROM may be just fine as is, I take it. That was what I was hoping to hear.
Thanks, and any idea when a new experimental ROM will come from Tim? Just felt a slight twitch. I've tried the other team's creations and seem to only feel really satisfied with Kits - (guess 'CrackFlashing' addiction picks a really hard one to withdraw from).
Many thanks!
Cal
Click to expand...
Click to collapse
I think it will be a while until timduru starts to work in a experimental rom , since there is no Android 5 yet.
But Tim has marked katkiss as stable and for my daily use it is. But you could try 4.4.2.
schwigi said:
I think it will be a while until timduru starts to work in a experimental rom , since there is no Android 5 yet.
But Tim has marked katkiss as stable and for my daily use it is. But you could try 4.4.2.
Click to expand...
Click to collapse
Read the original post again -- I've been on the 4.4.2_16 forever now it seems!! The urge to try something new is over-bearing! :silly: :victory:
Ah-Ha! I see that Tim's put up a new 'stable' one. KK 4.4.2_17! Yeah!! This should be a super easy fix for the 'crack-itis' I have developed...as I will overwrite this one also.

Categories

Resources