Related
hi
Ive just installed Cleanrom, and it seems slower than the stock rom i used before.
I wonder if i should have done a system format in cwm, as doing this for Slimbean on my SGS helped quite a bit...
thanks
geoslake said:
hi
Ive just installed Cleanrom, and it seems slower than the stock rom i used before.
I wonder if i should have done a system format in cwm, as doing this for Slimbean on my SGS helped quite a bit...
thanks
Click to expand...
Click to collapse
Format system is when you delete your ROM, if you want a clean install, yeah you should format system. This also depends on what ROM you want to flash. If you're going to flash stock, format system is good. I do it all the time when I flash stock
But I can also do it whatever the rom, right ? I mean if I upgrade from Cleanrom from 3.03 to 3.04, I cannot go wrong doing that ? (although they don't talk about formatting system in the guidelines).
Thank you
Format system is when you delete your ROM, if you want a clean install, yeah you should format system. This also depends on what ROM you want to flash. If you're going to flash stock, format system is good. I do it all the time when I flash stock
Click to expand...
Click to collapse
format system basically deletes all your system apps, which really isn't worth to do in an update from v3.0.3 to 3.0.4 - if it's a big update with many more apps included maybe it's worth, but otherways it's waste of time...
-angel* said:
format system basically deletes all your system apps, which really isn't worth to do in an update from v3.0.3 to 3.0.4 - if it's a big update with many more apps included maybe it's worth, but otherways it's waste of time...
Click to expand...
Click to collapse
System app? When I use twrp it said wipe system removes ROM, I guess on cwm is called format system.
Well, I guess "format system" should format system (=wipe the os i guess), not remove apps...
geoslake said:
Well, I guess "format system" should format system (=wipe the os i guess), not remove apps...
Click to expand...
Click to collapse
Hmmm why don't you use twrp. It's much better haha
Tamaskan said:
Hmmm why don't you use twrp. It's much better haha
Click to expand...
Click to collapse
Guess so, I guess its no problem to overwrite CWM with TWRP (as long as I load the right version, that is, JB as im on Cleanrom Inheritance 2.7.2)...
Format system on twrp and cwm means the same thing.
When you flash any ROM, all it does is place everything in the /system partition, and sometimes a kernel is also flashed.. this partition contains all files that make up android. All the apps that come with roms, all mods, themes, framework.. everything is here.
When /system is wiped, it deletes all these files to make way for a new rom. Most roms wipe system automatically when they get flashed anyway :good:
However, I think that cleanrom 3.0.3 is a dependancy for 3.0.4, this means that 3.0.4 requires the 3.0.3 system files to work properly. Check the cleanrom changelog or install instructions
Sent from my GT-I9100
Nothing happens, it just clears your data.
Tamaskan said:
System app? When I use twrp it said wipe system removes ROM, I guess on cwm is called format system.
Click to expand...
Click to collapse
I'm sorry, I was thinking of /system/app lol
I think the updates should rule that themselves that they delete the unnecessary things of an old version, so it's only recommended if you change your ROM or update to a ROM based on a later Android Version (4.1 to 4.2 or vice versa) or from AOSP to stock...
Otherwise it's just waste of time I think, I never used it and never had problems, so I think it's pretty good ruled in the updater scripts of the ROMs
So most of you must have used the PACman ROM at some point of time.Right???
Love it?But wish that the UI Tearing goes away...
Well your wish has come true...
HALO IS HERE!!!
JBX KERNEL IS HERE!!!!
SAY GOODBYE TO UI-TEARING AND ENJOY THE PACman AS IT SHOULD BE...
Well you're all well aware of the features,have seen the screenies(hell even used it) so I won't waste your and my time rattling about that.
Let's go then:
Links:
PAC
GAPPS Collection
Installation Instructions:
Note:This ROM uses JBX kernel(0.6).Those of you who were getting the black screen problem with kexec kernel will get the same bug here.
Note:Please backup your CID just to be safe.You may not have this error ever but it's always safe to have a backup of the CID.So that if you get a message invalid CID or soemthing just restore it and you'll be good to go.
To backup CID:
Reboot into Recovery
Tap on firmware flashing
Tap on backup CID.
Note:To be flashed via BMM only
BMM instructions:
See here if this is your first time multibooting with BMM.
Download and install BMM from google play https://play.google.com/store/apps/d...otmenu.manager
Our phone does not have a partition for internal storage.. so we use the data partition for it.. To do so, just open a root browser like root explorer and navigate to /etc/bmm/conf
Open "recovery.fstab" with a text editor
The last line will be something like this
/int vfat /dev/block/mmcblk1p25
Just change 'vfat' to 'auto' and 'mmcblk1p25' to 'userdata' (its the same though..)
So that it looks like this
/int auto /dev/block/userdata
and of course save it and close it..
Done.. you are good to go.. Happy Multi Booting..
Just some tips
On your first reboot, tap the android, go to settings-->System_2-->Partition setup and tap on ACTIVATE. This formats cdrom partition to ext2.
Now go back 2 two steps, and select any other system(3-6). choose Partition setup, tap on system.img, tap on Create, select the size, create it. go back and do the same with data.img and cache.img.
Once thats done, go back and select recovery, select switch system. choose your system that you created the images for, the colour will change, install any custom rom.. Enjoy!!
NOTE: BMM stores the images in internal memory(/int/clockworkmod/virtual/system_(num)). Since we dont have emmc partition and are using the data partition for /int, doing a factory reset will wipe it out and you will lose all your other roms.. So be carefull..
NOTE 2: USE ONLY SYSTEMS 3 TO 6 FOR CUSTOM ROMS.. SUSTEM 2 IS CDROM PARTITION.. YOU ACTIVATE IT ONCE AND DONE.. DONT TOUCH IT AGAIN.. ITS ONLY 12MB..
IMPORTANT NOTE: DO NOT INSTALL BMM IF YOU USED A2 BOOTSTRAPPER BEFORE. THAT WILL MESS THINGS UP WITH YOUR LOGWRAPPER.BIN. THERE IS A GOOD CHANCE YOU WILL BOOT LOOP AFTER REBOOT. NOW IF FOR SOME REASON YOU DID NOT READ THIS, AND GET A MESSAGE ABOUT BMM ASKING YOU TO GET HELP, BEST THING FOR YOU TO DO IS RECHARGE YOUR BATTERY FULLY AND FXZ BACK. OR THERE IS A GOOD CHANCE YOU WILL HAVE TO USE MCGRUVYER METHOD OR ANOTHER A2 BATTERY. USER RAD7 RECENTLY HAD QUITE A LOT OF TROUBLE WITH HIS BATTERY DYING AFTER BMM MESSED WITH LOGWRAPPER. YOU HAVE BEEN INFORMED.
Make sure you have BMM recovery.
Reboot and hit the droid at the BMM splash screen
Optional:
Tap on Settings
Create a new System by creating system,data and cache partitons.Delete the previous partitions if you have to(NOTE: You can skip this but it's better to do it this way)
Click to expand...
Click to collapse
Wipe data/factory reset
Wipe dalvic cache
Flash ROM
Flash Gapps
Reboot
Click to expand...
Click to collapse
Credits:
surdu_petru for his port on Motorola Razr.
dtrail1 for his kexec kernel
CHANGELOG:
22-06-2013:
Minor Fixes and synced to latest sources.(Full changelog to be uploaded)
12-06-2013:
Added HALO from Paranoid source !
Updated to CyanogenMod 10.1 RC5 ;
Updated PA commits ;
Fix Pie & Tablet Date View;
Update AOKP Ribbons;
Fix 3-dot Menu Button;
Fix ParanoidAndroid Settings !
Add CPU Mode Switch ( need custom kernel to enable settings ... )
Add toggle Music from Slim Rom !
Updated PA to 3.6
Removed MDPI/HDPI PA Preferences Hack
TRDS 2.0
[30-05-2013]
Initial Release
PREVIOUS VERSIONS:
[12-06-2013] PAC v04 HALO!!!:
PACman v4.0 HALO
PACman v4.0 HALO-Mirror
[30.05.2013]PAC v1.0
PACman v1.0
PACman v1.0 MIRROR
i'm so sad can;t boot into kexec kernel.
i wish to try this..
Ok I've made a small Fix Audio.zip it should enhance audio significantly and also fix the broken sound recorder(I bet no one new that it was broken)
Anyways flash in recovery.No wipes needed.
Also if you don't like the new audio you can revert back to your old settings and broken voice recorder by flashing the Fix Audio Revert.zip
See the attachment below
guffoe said:
i'm so sad can;t boot into kexec kernel.
i wish to try this..
Click to expand...
Click to collapse
Try the non kexec version from ravi then.It's been out for like forever
---------------------------------------------------
May the -Mass times Acceleration-be with You...
deveshmanish said:
Ok I've made a small Fix Audio.zip it should enhance audio significantly and also fix the broken sound recorder(I bet no one new that it was broken)
Anyways flash in recovery.No wipes needed.
Also if you don't like the new audio you can revert back to your old settings and broken voice recorder by flashing the Fix Audio Revert.zip
See the attachment below
Click to expand...
Click to collapse
I actually did notice it in AOKP , but didn't had the chance to post about it .
iamezio said:
I actually did notice it in AOKP , but didn't had the chance to post about it .
Click to expand...
Click to collapse
Lol nvm it's fixed now.
---------------------------------------------------
May the -Mass times Acceleration-be with You...
I installed this to system 3 and got it to boot up once, but whenever I rebooted, every time I try to boot it up, I just get sent back to the moto dual core logo. Does this mean I'm a kexec reject?
Edit: I played around some more, turns out system 1 and system 3 didnt play nice together,so deleting system 3 fixed it!
Sent from my MB865 using xda app-developers app
i'm currently on boot menu manager 0.2.7 right now and on the NUMA ROM. Is the BMM I'm supposed to use different and is the process different since I'm coming from NUMA?
EDIT: nvm, installed and rebooted to system 2. Now waiting for it to boot (taking forever)!
Chowlz said:
i'm currently on boot menu manager 0.2.7 right now and on the NUMA ROM. Is the BMM I'm supposed to use different and is the process different since I'm coming from NUMA?
Click to expand...
Click to collapse
Well the multi booting process is significantly different in the 0.2.7 and 0.3.4 better just upgrade the BMM and then flash it.
But the process would be the same.
deveshmanish said:
Well the multi booting process is significantly different in the 0.2.7 and 0.3.4 better just upgrade the BMM and then flash it.
But the process would be the same.
Click to expand...
Click to collapse
Okay... kind of lost on the instructions. I rebooted, clicked the droid, and click settings, picked system 2 (NUMA is on system 1) and I'm only given "Partition setup" and "Boot mode". I clicked System 2 and clicked activate. Am I supposed to go back, enter recovery and then continue with the instructions?
Chowlz said:
Okay... kind of lost on the instructions. I rebooted, clicked the droid, and click settings, picked system 2 (NUMA is on system 1) and I'm only given "Partition setup" and "Boot mode". I clicked System 2 and clicked activate. Am I supposed to go back, enter recovery and then continue with the instructions?
Click to expand...
Click to collapse
Have you modified the recovery.fstb files???
See here
And then use system 3 or above to install
deveshmanish said:
Have you modified the recovery.fstb files???
See here
And then use system 3 or above to install
Click to expand...
Click to collapse
Ahh, I see. Would be nice if you included these in your instructions. Thanks!
Chowlz said:
Ahh, I see. Would be nice if you included these in your instructions. Thanks!
Click to expand...
Click to collapse
Hmmm...Done!!!
So far, so epic
So, just to be sure before I begin: I'm on JB leak 1 (4.1.2), and I must go back to stock ICS before flashing this, right? Or I can just install BBM and install it from here? I was absent in the recent weeks so can someone direct me?
So, just to be sure before I begin: I'm on JB leak 1 (4.1.2), and I must go back to stock ICS before flashing this, right? Or I can just install BBM and install it from here? I was absent in the recent weeks so can someone direct me?
Click to expand...
Click to collapse
You can flash over ICS or jb leak
Sent from my MB865 using xda premium
filip990 said:
So, just to be sure before I begin: I'm on JB leak 1 (4.1.2), and I must go back to stock ICS before flashing this, right? Or I can just install BBM and install it from here? I was absent in the recent weeks so can someone direct me?
Click to expand...
Click to collapse
Yeah. Go on and flash . Its kexec. Doesn't matter which kernel it is.
In the first post it says that I shouldn't install BMM if I have A2 Bootstrapper. Should I remove it first?
I never used BMM before, so I'm not familiar with it yet
Can i install roms on System 1, who and how? pls help, i dont want to break my phone, i 've LiquidSmooth but on System 3, i need more space and the only way its installing on system 1..
Who other roms can i install on system 1, and who are requirement? thx for your help :good::cyclops:
Yes, you can. In fact, I am using just System 1 (AOSB) as my daily ROM.
I don't know if this is required, but I'm always doing the following:
1. Format /system, /data, /cache
2. Wipe System, Cache, Dalvik Cache
3. Install ROM
4. Install GApps
I never had any problems since.
Goodluck mate!
Cheers,
Rae
I have never used any other system other than system 1 as daily driver..i don't know y ppl are so scared to flash..same time two years back we didn't even have a recovery on boot and still used to flash roms courtesy rdavisct, alteredlikeness, jimbridgman n co..this whole concept of multiple systems has made things more complicated than before it seems
Sent from my MB865 running CaRbOn 4.4.3 source built by dmroeder!!
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
devilhunter47 said:
I have never used any other system other than system 1 as daily driver..i don't know y ppl are so scared to flash..same time two years back we didn't even have a recovery on boot and still used to flash roms courtesy rdavisct, alteredlikeness, jimbridgman n co..this whole concept of multiple systems has made things more complicated than before it seems
Sent from my MB865 running CaRbOn 4.4.3 source built by dmroeder!!
Click to expand...
Click to collapse
To the steps mentioned above
Wipe battery stats
After installation go to system keeper option
Install bmm to main system
Reboot
Safer this way
Sent from my MB865 using Tapatalk 2
Raeshabu said:
Yes, you can. In fact, I am using just System 1 (AOSB) as my daily ROM.
I don't know if this is required, but I'm always doing the following:
1. Format /system, /data, /cache
2. Wipe System, Cache, Dalvik Cache
3. Install ROM
4. Install GApps
I never had any problems since.
Goodluck mate!
Cheers,
Rae
Click to expand...
Click to collapse
Thaankss..! bro im gonna try it now..! i did a back up of stock 4.0.4
devilhunter47 said:
I have never used any other system other than system 1 as daily driver..i don't know y ppl are so scared to flash..same time two years back we didn't even have a recovery on boot and still used to flash roms courtesy rdavisct, alteredlikeness, jimbridgman n co..this whole concept of multiple systems has made things more complicated than before it seems
Sent from my MB865 running CaRbOn 4.4.3 source built by dmroeder!!
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
To the steps mentioned above
Wipe battery stats
After installation go to system keeper option
Install bmm to main system
Reboot
Safer this way
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
ohhh i'm really thankful , i was nervous but with this steps i'm sure of wait i'm going to do..
saga02 said:
Thaankss..! bro im gonna try it now..! i did a back up of stock 4.0.4
Click to expand...
Click to collapse
Good luck mate! :good:
@devilhunter47
Thanks for the additional info.
Anyways, I never install BMM after flashing ROMs because it auto-installs after you press back from Install from Zip. Or maybe we just have different experiences regarding this.
Thank you again! :highfive: :good:
Raeshabu said:
Good luck mate! :good:
@devilhunter47
Thanks for the additional info.
Anyways, I never install BMM after flashing ROMs because it auto-installs after you press back from Install from Zip. Or maybe we just have different experiences regarding this.
Thank you again! :highfive: :good:
Click to expand...
Click to collapse
Sometimes it fails to and i had to fxz
Sent from my MB865 using Tapatalk 2
171
devilhunter47 said:
Sometimes it fails to and i had to fxz
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
guys i've a problem, when the installations finish i did "system keeper option", and then show me a mistake, saying "BBM will not start after reboot", and now the phone dont show me BBM and only restart and restart :/ i dont know what to do now, because i can enter to bbm and fix this :S.. I can not even go to android, is happening and I did wrong? : ( And how to fix this please help ..!
Raeshabu said:
Good luck mate! :good:
@devilhunter47
Thanks for the additional info.
Anyways, I never install BMM after flashing ROMs because it auto-installs after you press back from Install from Zip. Or maybe we just have different experiences regarding this.
Thank you again! :highfive: :good:
Click to expand...
Click to collapse
Heelpp..! BMM not appear, and the phone stayed restarting does nothing but nothing out of the motorola logo screen goes black for a minute and not start, should show BBM but no longer does, and prior to the reboot when installation is complete and I gave keeper system option "Install bmm to main system" not only told me BBM started after reboot and so did not know what to do now ..: S can not access the system 3 is where I have q my other system: (help please
saga02 said:
Heelpp..! BMM not appear, and the phone stayed restarting does nothing but nothing out of the motorola logo screen goes black for a minute and not start, should show BBM but no longer does, and prior to the reboot when installation is complete and I gave keeper system option "Install bmm to main system" not only told me BBM started after reboot and so did not know what to do now ..: S can not access the system 3 is where I have q my other system: (help please
Click to expand...
Click to collapse
Sorry to hear that.
So, are you saying that after you installed a ROM in System 1, you force-installed BMM again through System Keeper?
I think you need to FXZ back to stock ICS, then root, then install BMM from the market again.
I think I had the same experience back when I first got this phone and was still experimenting on stuffs.
Anyways, do you know how to FXZ back to stock ICS? There's a guide on how to do that here:
forum.xda-developers.com/showthread.php?t=1937112
Click to expand...
Click to collapse
You SHOULD follow every step mentioned on the thread, and also download the correct FXZ for your phone.
Or you could check my post here:
forum.xda-developers.com/showthread.php?p=53305693#post53305693
Click to expand...
Click to collapse
Just ignore the part where I insist you should download the AT&T FXZ for your phone. That part is for my phone only.
Raeshabu said:
Sorry to hear that.
So, are you saying that after you installed a ROM in System 1, you force-installed BMM again through System Keeper?
I think you need to FXZ back to stock ICS, then root, then install BMM from the market again.
I think I had the same experience back when I first got this phone and was still experimenting on stuffs.
Anyways, do you know how to FXZ back to stock ICS? There's a guide on how to do that here:
You SHOULD follow every step mentioned on the thread, and also download the correct FXZ for your phone.
Or you could check my post here:
Just ignore the part where I insist you should download the AT&T FXZ for your phone. That part is for my phone only.
Click to expand...
Click to collapse
Ready brother could fix all that I did just now was able to install in system 1 and so far everything is fine, the problem was the gapps and they made the bootlooping, I am LiquidSmooth 3.1 (4.4.3) that I can recommend another rom this stable and fast ... thank you very much for your help really'm super grateful to you ..
saga02 said:
Ready brother could fix all that I did just now was able to install in system 1 and so far everything is fine, the problem was the gapps and they made the bootlooping, I am LiquidSmooth 3.1 (4.4.3) that I can recommend another rom this stable and fast ... thank you very much for your help really'm super grateful to you ..
Click to expand...
Click to collapse
Hey, I'm glad that you fixed your phone. :highfive:
Cheers,
Rae
saga02 said:
Can i install roms on System 1, who and how? pls help, i dont want to break my phone, i 've LiquidSmooth but on System 3, i need more space and the only way its installing on system 1..
Who other roms can i install on system 1, and who are requirement? thx for your help :good::cyclops:
Click to expand...
Click to collapse
Dude you can flash ROM's on System 1 but please be careful as it will delete all other data on the other systems.
One more thing if your using altreds CM 11 use the BaNkS minimal gapps, It's not a problem to flash on the system 1, the thing is a failed flash can sometimes lead to you needing a FXZ, so just be careful on which ROM your flashing. :good:
I have little bit confusion. Please guide if these steps are correct:
1. Using BMM, format system 1 partition, data, cache.
2. Clean/wipe data, cache, battery, dalvik
3. Install ROM and GAPPs in system 1
4. system keeper > keep/install BMM
Are these steps correct?
Another question is if I want to install only one ROM in system 1 and want to use all available space for this setup then how to setup the partitions with maximum available space? Or I don't need to setup partitions?
Jack Sparrow xda said:
I have little bit confusion. Please guide if these steps are correct:
1. Using BMM, format system 1 partition, data, cache.
2. Clean/wipe data, cache, battery, dalvik
3. Install ROM and GAPPs in system 1
4. system keeper > keep/install BMM
Are these steps correct?
Another question is if I want to install only one ROM in system 1 and want to use all available space for this setup then how to setup the partitions with maximum available space? Or I don't need to setup partitions?
Click to expand...
Click to collapse
No need to set partition sizes on system 1, that's solely for multi-booting ROMs on systems 3-6. Everything else is good though.
1BadWolf said:
No need to set partition sizes on system 1, that's solely for multi-booting ROMs on systems 3-6. Everything else is good though.
Click to expand...
Click to collapse
Thanks for the info, that was really helpful
But one confusion, I use BMM for flashing ROMs. And in case of BMM, we have to set partitions for system, data and cache. How to do that partitioning step in case if we want to flash ROM in the system 1 ? Won't we have to specify the sizes for all of those partitions?
Another question is, how to fully clean up the system 1 and free up whole ROM space before starting system 1 setup? I mean can I clean everything which came from factory before flashing on the system one to get as big as possible size of internal ROM for the system 1 setup? How much space we can get by doing that? Right now it shows around 2 GB available for user (apps and data) in the 4GB ROM of the Atrix 2, how much would it show in case of custom ROM flashing by freeing up whole space?
Jack Sparrow xda said:
Thanks for the info, that was really helpful
But one confusion, I use BMM for flashing ROMs. And in case of BMM, we have to set partitions for system, data and cache. How to do that partitioning step in case if we want to flash ROM in the system 1 ? Won't we have to specify the sizes for all of those partitions?
Another question is, how to fully clean up the system 1 and free up whole ROM space before starting system 1 setup? I mean can I clean everything which came from factory before flashing on the system one to get as big as possible size of internal ROM for the system 1 setup? How much space we can get by doing that? Right now it shows around 2 GB available for user (apps and data) in the 4GB ROM of the Atrix 2, how much would it show in case of custom ROM flashing by freeing up whole space?
Click to expand...
Click to collapse
System 1 gets partitioned by flashing the FXZ so it's not necessary to do it with BMM. The best way to clean up system for flashing is to flash the FXZ first, then root and install BMM, etc. You can also use BMM to format system, data, cache and dalvik cache if you haven't created partitions for other systems. The only reason you will ever need to create partitions with BMM is to flash on systems 3-6.
1BadWolf said:
System 1 gets partitioned by flashing the FXZ so it's not necessary to do it with BMM. The best way to clean up system for flashing is to flash the FXZ first, then root and install BMM, etc. You can also use BMM to format system, data, cache and dalvik cache if you haven't created partitions for other systems. The only reason you will ever need to create partitions with BMM is to flash on systems 3-6.
Click to expand...
Click to collapse
Oh, I thought BMM will do it on sys 1 as well. I used sys 3 & 4 just to try out various ROMs without risking the stock system so that I can know which ROM suites me and later I can cleanup the whole system and put that ROM of my liking in the main system.
I am not familiar with FXZ method and it seems more complicated to me. isn't there any way to flash ROM on sys 1 and deleting the other partitions?
I am noob in this flashing thing and its been just 10-12 days since I started it up. the bmm method looked easy to me and I would prefer it if its possible to use for this purpose.
Sent from my MB865 using Tapatalk
Jack Sparrow xda said:
Oh, I thought BMM will do it on sys 1 as well. I used sys 3 & 4 just to try out various ROMs without risking the stock system so that I can know which ROM suites me and later I can cleanup the whole system and put that ROM of my liking in the main system.
I am not familiar with FXZ method and it seems more complicated to me. isn't there any way to flash ROM on sys 1 and deleting the other partitions?
I am noob in this flashing thing and its been just 10-12 days since I started it up. the bmm method looked easy to me and I would prefer it if its possible to use for this purpose.
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
Flashing the FXZ is actually pretty simple. The main thing to know is which FXZ is the correct one for your phone. (Also it's a really good idea to find THAT out BEFORE you need it.) BMM is far more complicated and confusing IMHO.
Anyway, it's still possible to do a clean flash via BMM if that's what you're more comfortable with, though, so no worries. Just do a factory reset, which will format data, cache, and dalvik. Since that formats the data partition you will lose everything on any other existing systems. (though it may not always be necessary I normally format the system as well. DO NOT reboot at this point or you'll have no choice but to FXZ.) Then you just flash the zip plus gapps and whatever other mods you want. Personally I like to reboot between flashing each zip. In other words, I flash the ROM then reboot. Then gapps and reboot, etc. No repartitioning is necessary for flashing on system 1 and might actually be detrimental so just skip that.
Thanks a lot @1BadWolf, your post clears all doubts in my mind
1BadWolf said:
No repartitioning is necessary for flashing on system 1 and might actually be detrimental so just skip that.
Click to expand...
Click to collapse
Thanks for letting me know about no need of partitioning sys 1. If I wouldn't have been in this discussion with you, I would have ended up creating partitions on system 1 as well like what I have learnt to do on other systems and there would have been a thread by me on getting stuck in bootloop, you saved me from that.
To be bit on more safer side, let me put what I have understood so far:
1. Boot in BMM.
2. Factory reset on system one. (I have two other custom ROMs on system 3 and 4. will it also clear all the other ROMs installed on other systems also?
3. Format partitions on system one.
4. Clear system, data cache etc
5. Install ROM and GApps on system 1
6. Keep BMM in main system
7. Reboot and done
Is there anything broken or wrong in that chain?
One more query, can I keep continue installing ROMs on other systems like what I am doing right now in case of retaining stock ROM?
Hello again xD, i have a question,
¿i need make system,data and cache partitions after installing any rom? Plz help me
cdxmantilla said:
Hello again xD, i have a question,
¿i need make system,data and cache partitions after installing any rom? Plz help me
Click to expand...
Click to collapse
Not after, before, but it's not a necessity unless you're installing additional systems for multi-booting.
1BadWolf said:
Not after, before, but it's not a necessity unless you're installing additional systems for multi-booting.
Click to expand...
Click to collapse
Just to piggy back this question.
One rom installing guide told that i have to manually create the system 3 partition.
But my rooted BMM is showing system 1-6. are these just dummy entries or do the partitions exist already?
Rishav Sharan said:
Just to piggy back this question.
One rom installing guide told that i have to manually create the system 3 partition.
But my rooted BMM is showing system 1-6. are these just dummy entries or do the partitions exist already?
Click to expand...
Click to collapse
They're just dummy entries. You only need to create additional partitions if you intend to use them. Creating additional will leave you with less room for apps, etc on system 1 so don't do that step unless you're multi booting.
When installing my rom(slimkat) i couldnt figure out how to create system 3, so i flashed onto system 1. I got the error about BMM not installing
bye to bmm, install didnt take and i had to flash ics back. What did i do wrong?
1. did you used/remove bootstrap files before install BMM?
2. did you made any changes to recovery.fstab file from etc/bmm/conf?
you suppose to change /int vfat /dev/block/mmcblk1p25 to /int auto /dev/block/userdata
Barb3r said:
When installing my rom(slimkat) i couldnt figure out how to create system 3, so i flashed onto system 1. I got the error about BMM not installing
bye to bmm, install didnt take and i had to flash ics back. What did i do wrong?
Click to expand...
Click to collapse
When installing a ROM by formatting /system, BMM is removed from system partition. To get it back for next boot you have to go to system keeper option in recovery and install BMM again.
I had to go to back to ICS twice when I made this mistake. Hope you don't make the same mistake next time.
Cheeers!
I tried again this time flashing the rom first then rebooting. Rom loaded up nice with BMM already installed. However, when I went back to recovery to flash the gapps I got a boot loop.
TWRP METHOD ONLY
HOW TO TRANSFER ALL APP DATA + SETTINGS + ALL USER CONFIGURATION FROM PREVIOUS ANDROID OS TO NEW ANDROID CUSTOM ROM
Greetings, i have Great info for everyone for RESTORING User App + Data as it was before from TWRP. I used pixel experience 10 official rom for 2 days and after flashing it i restored my app data from titanium backup which after that took time to configure everything which is a bummer hectic to configure phone settings as per our likes and install & configure every app. Official Pixel 10 showed me little lags and slower performance compared to MIUI 11. Caution: TWRP DOES NOT BACKUP users Internal Storage data so make sure you backup your internal storage data like Photos, videos anything in internal flash storage backup somewhere else.
Now here's what i did, i rebooted to TWRP > Backup > Backed-up system image(incase anything goes wrong), boot and specially DATA (All user app + its data + settings stored in this). Make sure you backup data in external storage like memory card or OTG flash drive.
Then i installed EvolutionX Pixel 10 latest version released on 5th Dec after complete format, flashed DFE, Flashed Drunk Kernel, Flashed Magisk and wiped cache & dalvik cache. Then rebooted phone and configured the new os startup> rebooted to TWRP > Restore > selected only DATA and restored it > BOOTED SUCCESSFULLY WITH SAME APP DATA AND SETTINGS including same wallpaper and everything was same.
WARNING: After you boot your fresh backed up data & it asks for password after boot & gets stuck then reboot to TWRP and Install ResetScreenLock.zip (find it in XDA or CLICKHERE and boot successfully.
You can ONLY do this on SAME VERSION OF ANDROID OS. Like i had Pixel Experience 10 Official so it's data can only be transferred to any other Pixel Experience 10 custom Rom. I'm not sure about transferring Data from different versions of Android example android 9 Pie TO android 10 Q let me know if it's possible.
I didnt backup from titanium backup because usually restoring backup from titanium freezes & it cannot restore specific User App data to a new rom and it was a headache restoring apps manually after titanium backup didn't restore half of my apps & its data
You are welcome have blessed day. God Bless:laugh:
This is twrp 101. But mind that every problem and every force close you will encounter (and you most probably will) is going to be because of this.
Phone overheating, battery drain, apps crashing etc.
Developers suggest clean flashing for a reason, old ROM data interference with the new ones.
What you did is called dirty flashing and is the same as wiping system, davlik, cache and flashing ROM and gapps.
Your data backup is very useful when you want to try a new rom, clean flash it and then want to go back to your previous one.
sotosgolf said:
This is twrp 101. But mind that every problem and every force close you will encounter (and you most probably will) is going to be because of this.
Phone overheating, battery drain, apps crashing etc.
Developers suggest clean flashing for a reason, old ROM data interference with the new ones.
What you did is called dirty flashing and is the same as wiping system, davlik, cache and flashing ROM and gapps.
Your data backup is very useful when you want to try a new rom, clean flash it and then want to go back to your previous one.
Click to expand...
Click to collapse
Not a single problem till now, No phone heating, no abnormal battery drain, not a single app crashed. Phone is working perfectly smooth and not even a mili second lag. Basically Technically what actually i did is transfer my previous Pixel 10 data to New Pixel 10 data so there are no changes at all in Data.
You can test it if you follow my steps exactly you will successfully transfer Data to any New custom rom, i have tried. Just make sure the data you want to transfer is between same base roms like i transferred from Official Pixel 10 TO EvolutionX Pixel 10, similarly you can transfer to any Custom rom that is based on same base rom which you are using currently.
NOTE: Before you go & do TWRP backup, make sure you do complete system cleanup, app cleanup, corpse cleanup from SD Maid Pro and then do clean backup from TWRP
After you flash new custom rom make sure you boot it and go through its initial startup process then go back to TWRP and restore rom and flash ResetLockScreen.zip
Enjoy
eladamcain said:
Enjoy
Click to expand...
Click to collapse
I'm using custom ROMs since 2014, i have certainly enjoyed the issues i'm describing above.
Dirty flashing causes a lot of unwanted stuff.
Anyway, that's my two cents.
sotosgolf said:
I'm using custom ROMs since 2014, i have certainly enjoyed the issues i'm describing above.
Dirty flashing causes a lot of unwanted stuff.
Anyway, that's my two cents.
Click to expand...
Click to collapse
If you don't know what you are doing, you will face problem. This method works perfectly IF you are on Stock Rom and it is not bloated and you are transferring your data to custom rom who's made from the same base stock os. Example heavily bloated and transferring its settings to a different setting os is going to create instability its common sense. Backing up non bloated stock rom data to custom rom works
You saved my life... I tried a similiar method but it didn't work. But this... this saved my LIFE
(2FA Problems...)