Related
It seems that there are a lot of ROMs out there that are doing some funky stuff from the edify scripting in CWM and providing a poor user experience. This overall hurts the entire custom NookColor community and puts a bad taste in peoples mouths.
This post is to point out best practices when creating CWM flashable zips in a consistant way allowing the user to upgrade and migrate between roms in a predictable way.
Rule #1: Don't touch /data!
There are many reasons why you don't want to touch /data but the most important is to allow the user to be able to upgrade your rom without completely wiping your data.
If you want to bundle in an applications (first of all... don't but if you reaally think it is necessary) put it in /system/app as a system app.
Rule #2: Don't overwrite /boot/uRecRam and /boot/uRecImg!
ROM and CWM should be separate. Users should be able to use your rom with CWM or even the stock recovery if they wish to. Allow the user to choose what version of CWM they want to run and allow them to upgrade it independently of your rom.
This allows you to not re-release roms every time a new version of CWM is released.
Exceptions to the rule are update zip that are intended to install CWM (which is ok) or zips that will restore the entire system to stock.
Rule #3 Learn edify
Edify scripting is quite powerful. It saddens me to open up the updater-script of a rom and see it extracting a script and then executing the script.
Don't store your roms as .tars and require a script to extract them to the right locations, you should be doing this all from edify scripts.
Rule #4: Only touch /system and /boot/uImage and /boot/uRamdisk
All other files should be off-limit! This goes back to rule #1 and rule #2. A rom should consits of a kernel, a ramdisk to boot the system and /system files for running the rom!
Rule #5: NEVER EVER EVER modify partitions or wipe the EMMC completely!
I cannot stress this one enough. Use stock partition scheme for your rom. It may seem like a "waste" to you but this is what will make all our roms compatible with each other!
Also the Nookcolor stores NVRAM type information on /dev/block/mmcblk0p2 and factory restore information and a backup of p2 on /dev/block/mmcblk0p3.
If you wipe these directories in your update.zip you WILL BRICK THE USERS NC! It may work for you but they can never return to stock. Their serial number and mac addresses will be lost!
Just don't even think about doing anything with the partition map or these partitions!
Rule #6: When in doubt look at the CM update.zips
A good example of the rules above is portrayed in the CyanogenMod nightly roms for the NC. Look at the updater-script in META-INF/com/google/android and see how things are done.
If we all agree to follow these rules the NC users will get a better and more consistent experience and you will have more users for your rom.
For the users I will list the ROM that are compatible with the list above and list ROMs that don't follow these rules.
ROMs that follow proper packaging
These rom have been built properly according to the rules in the OP. I highly recommend testing any of these out.
Cyanogenmod Nightlies
phiremod nook V5.2
Nookie Froyo 0.6.8
(Utility Update.zip) Nook Color SDcard and emmc swap
ROMs that DON'T follow proper packaging
Use these roms at your own risk!
Flashable eMMC dual boot ROMs
Dual booting roms violates changing the the parition table! If you want to dual boot I would use a bootable SD. If you get a class 6 or higher SD card the performance difference should be pretty low. The perceived speed boost i believe is negligible.
Avoid this rom if you are new to Android or the NookColor. I would call this rom an "Advanced user" rom and not for new members of the community who are unfamiliar with Android, Linux, or the NookColor
Click to expand...
Click to collapse
HC v4 eMMC 2nd ed. - Flashable ZIP
This rom packaging is the poster child for how to do it wrong. They overwrite your /data for app customization. It uses an external script and tar files for extraction and overwrites all of /boot!
AVOID THIS ROM PACKAGE!
Click to expand...
Click to collapse
This looks very wise and in accord with general programming principles.
In the same area of discussion, can you talk about whether or not to clear cache while doing this same update process.
In fact, some explanation of /cache and Dalvik Cache and Market Cache might help to alleviate confusion, especially in regards to specifically what they are, and when one should clear them.
Sure, a "cache" is a piece of data that is frequently used, and so put in a more accessible place, but in typical confusing fashion, that general term is being used in a specific way in Android.
Thanks !
Nice. Good guidelines.
It would, in a perfect world, be nice if a standard CWM recovery would give a choice to either write to SD or EMMC. Then we would not have many of these more involved boot file and CW file edits and changes that are making things more complicated.
If everyone used CW to right to EMMC, this would be easy. But users like myself are running ROMs from SD and are always looking for a way to easily update and flash mods or ubdate ROMs to SD. Yes I use ADB, and other methods, but often I am traveling and away from my office or studio were my PC's are.
Any ideas on CWM to keep things more unified as the op suggests and be able to write to bootable SD cards?
Thanks for starting the discussion.
12
Good explanation/write-up, nemith. Not being a dev, but a user, it helps me to better understand which ROMs to use on my NC. I really liked HC EMMC, but did not realize that it would make it so I could never return back to stock (losing my S/N and such).
Also concur with ADude about cache....a good explanation would be helpful here. I only clear the cache/Dalvik when installing a new kernel. Not sure if even necessary? And, I clear AFTER installing, not before, so not sure if I am even doing that in the correct order. Setting the record straight would go a long way for us non-devs.
Sorry, one more thing, it would be great to have a consistently updated bootable SD card with latest/greatest of CWR on it. I am still on 3.0.0.6 and I am not sure why??
Thanks!
~ Razir
Could have used this a few months ago.
Thank you.
Nemith, your thread is directed at devs. If you want to make sure people don't flash my HC v4 2nd edition, you might want to invite users to read this as well.
nemith said:
ROMs that DON'T follow proper packaging
Use these roms at your own risk!
Flashable eMMC dual boot ROMs
Dual booting roms violates changing the the parition table! If you want to dual boot I would use a bootable SD. If you get a class 6 or higher SD card the performance difference should be pretty low. The perceived speed boost i believe is negligible.
I would avoid dual booting roms if you can!
Click to expand...
Click to collapse
I have this installed..... I am going to run the dual boot removal zip when I get home.
Am I screwed? Anthing I need to worry about?
12paq said:
Nice. Good guidelines.
It would, in a perfect world, be nice if a standard CWM recovery would give a choice to either write to SD or EMMC. Then we would not have many of these more involved boot file and CW file edits and changes that are making things more complicated.
12
Click to expand...
Click to collapse
I've thought of this. CWM would require a major rewrite to do this and the changes would never be sucked in.
Maybe one of these day's I will may my own CWM Kang that can do this, or better yet a desktop application that takes a update.zip and splits out a SD image!
cromanorn said:
I have this installed..... I am going to run the dual boot removal zip when I get home.
Am I screwed? Anthing I need to worry about?
Click to expand...
Click to collapse
No you are just in the "I am smart enough to use these roms without posting big "help me" posts on XDA.
These roms are not really harmful, but they should be avoided by people who don't understand the nook and how it works.
If you understand Android and how the NC is laid out then there should be minimal risk to using these roms. I just want to spell it out for people who are new to the NC or Android that these are "advanced" roms.
nemith said:
No you are just in the "I am smart enough to use these roms without posting big "help me" posts on XDA.
These roms are not really harmful, but they should be avoided by people who don't understand the nook and how it works.
If you understand Android and how the NC is laid out then there should be minimal risk to using these roms. I just want to spell it out for people who are new to the NC or Android that these are "advanced" roms.
Click to expand...
Click to collapse
THANKS!!! I had the NC for about 4 days now and would hate to have messed it up in the long run. I have a Droid Incredible that has been flashed more times than I can remember. It would be nice if the warnings were incorporated into the OP of these roms. I read the entire thread before flashing and I may not have flashed if this warning was there. I like having the option of going back to Stock without repercussions.
edit: Just saw the update you put in your OP about advanced users. I don't consider myself advanced but I am not a beginner either.
nemith said:
I've thought of this. CWM would require a major rewrite to do this and the changes would never be sucked in.
Maybe one of these day's I will may my own CWM Kang that can do this, or better yet a desktop application that takes a update.zip and splits out a SD image!
Click to expand...
Click to collapse
Yup. That would be very nice.
The Nook having SD boot priority really makes it versatile for testing, and quite recoverable. It also satisfies a unique situation where many users have a family device with Nook magazines and children's books not available on the Nook app, so many like myself are booting experiments and daily runners from SD and keeping the wife happy. LOL.
cromanorn said:
edit: Just saw the update you put in your OP about advanced users. I don't consider myself advanced but I am not a beginner either.
Click to expand...
Click to collapse
If you go digging at nookdevs.com and on your own NC you should be able to figure out what is safe and what is not.
nemith said:
Rule #6: When in doubt look at the CM update.zips
A good example of the rules above is portrayed in the CyanogenMod nightly roms for the NC. Look at the updater-script in META-INF/com/google/android and see how things are done.
If we all agree to follow these rules the NC users will get a better and more consistent experience and you will have more users for your rom.
Click to expand...
Click to collapse
the ironic thing is CM Roms don't fully follow Rule #3 since they have multiple scripts that run inside their packages during rom installation.
I'm not sure you are correct in saying that if you flash one of the HC emmc roms you can not revert back to stock. I know for a fact I have done both the dual boot, and HC emmc roms and reverted back to stock multiple times after doing so
I'm not saying you are wrong but I don't think i did anything to "advanced" to get back.
Quoted:
(I have this installed..... I am going to run the dual boot removal zip when I get home.
Am I screwed? Anthing I need to worry about?)
I had it installed and got back to stock no problem... i'm not sure what he is talking about.... i could be wrong though...
It was dualbooted CM7 and HC
went back to stock, registered with BN and all was well.
nooted it and then install HC on emmc
reverted back to stock to set up the ubuntu on NC
got bored of that and am back on HC on emmc
I went back to stock after both as well. Has anyone not been able to after using one of those two roms? I work at b&n and I had to spend time with the stock since they wanted me on the nook counter. I've been back and forth between all the roms more times then I can count.
Sent from my NookColor using Tapatalk
To the OP again i'm not trying to be rude, but could you respond to the last few commenter on this thread, it seems like my self a few others are having an experience that is quite different from what you described in your first post.
Could you help me understand why it hasn't been that difficult to get back from the roms that you specifically said can make it very hard to go back to stock from for us?
I'm currently on HM on emmc and if i did something fancy to get back the last time i restores i'd like to know if i need to do it again.
(edit) I bring this back up only because I saw this thread referenced again recently, which means it is having an effect on peoples work so i'm just trying to understand it.
[Edit] It was the SD card's fault. It seemingly worked fine in the laptop and it mounted fine in CW Recovery, but as soon as I used a different SD card I could flash zips again.
So, now I'm playing with phiremod v6 and loving the Nook again.
I believe I just bricked my Nook through use of the dual boot script.
I can only boot from SD into CW but not a single zip can be applied to the internal storage. Not even the "reverse dual boot" zip will run. They all error out.
I believe this is due to unexpected partitioning.
I even formatted boot, system and cache and still it will not restore any Roms.
So now I'm hoping to access the Nook through USB and repartition the internal storage manually. But before I do that, I need to learn about ADB and what the correct settings are.
jlt220 said:
To the OP again i'm not trying to be rude, but could you respond to the last few commenter on this thread, it seems like my self a few others are having an experience that is quite different from what you described in your first post.
Could you help me understand why it hasn't been that difficult to get back from the roms that you specifically said can make it very hard to go back to stock from for us?
I'm currently on HM on emmc and if i did something fancy to get back the last time i restores i'd like to know if i need to do it again.
(edit) I bring this back up only because I saw this thread referenced again recently, which means it is having an effect on peoples work so i'm just trying to understand it.
Click to expand...
Click to collapse
I don't think Nemith was saying that the existing dual boot installer is going to prevent you from returning to stock. He singled it out as a "ROM" that modifies the partition table, which can be a dangerous thing to do. There is information stored in the /dev/block/mmcblk0p2 and /dev/block/mmcblk0p3 partitions that is specific to each device and required by the B&N software. This information can't be rebuilt easily if lost.
The dual boot install and removal tools (in their current versions) appear to leave these partitions in tact. They are modifying the partition table though, so they're not recommended for novice users. You were able to install and uninstall it with no problems, so you're clearly not one .
The other point is that future versions of the dual boot (doubtful since it has a good dev) or other similar style "ROMs" may not be so careful with your 0p2 and 0p3 partitions.
Hi,
I'm currently charging my new SGS II, and considering what to do with it when I power it of. I have had a lot of cutom roms and mods on my HTC Desire previously Now, I know I don't want an AOSP ROM right away, I want to try out the phone how way it was "meant to be".
But I want the bells and whistles also though, like root, and any other stuff that makes the phone better, and I assume some of you here has some suggestions. I read through a decent amount of threads yesterday but I don't have a firm grasp of everything.
1: Is it much to gain from switching to a custom kernel battery-wise or performance wise? Or should I just run "stock" with zergRush?
2: Are there any cooked ROM base on Samsung softwae that exceed the stock ROMs in usefull functionality, while still being perfectly stable? Or are the stock rom great/good on it's own?
3: What kind of backups should I make before I start, to be as sure as possible of avoiding a certain brick? I run linux, so I can't run Odin, but I can run Heimdall and I guess I can make pretty much the same backups from there. As far as I have gathered, the S II have a few special quirks regarding partitions and some other low-level info. Is installing CWM and then do a backup "good enough" or is there something else that should be done - or should it be done before I even install CWM?
To answer your questions:
1. Yes custom kernels do make a difference- performance and battery wise. Currently, in my opinion, siyah and speedmod are two of the better kernels out there. Also the different governors in the kernels help you decided what balance between performance and battery life you want.
This thread explains everything about governors- http://forum.xda-developers.com/showthread.php?t=1369817&highlight=simple+clean
2. As good Sammy Roms go, I'd recommend you try CheckRom & Hyperdoid. Other Roms I'd recommend if you're looking for stability are Simple & Clean and Cognition. MIUI is good too(I'm currently on it) and quite stable.
3. If you don't have CWM recovery and have root, use Titanium backup to backup all your apps and MyBackup Root to backup the rest of the misc data. If and when you do have CWM recovery, just make a nandroid backup so you can freely try out new roms and restore through nandroid if anything happens.
If there's anything I've missed lemme know
__________________________________________________________________
If anything I've said helps, feel free to hit the thanks button!!
I simply installed CF Root which include CWM, and made a backup from there. (Which I then move to the external sd card, where I believe it should be en the first place. Not much help having a backup on internal storage if you mess up your artitions/nand.
It gives me a great chance to try the phone pretty stock for a while. Although I'm very little impressed by the Samsung "extras" so far, which seems to be limited to a few not-so-useful apps and a pretty crappy launcher. Samsung dive is the only thin with any value that I have discovered so far.
Its full of guides.
Also backup your EFS with ktool from the market asap.
I prefer speedmod Kernel
I did backup from CWM and take a copy to my laptop
Personally... like you I wanted to see the phone how it is made - at first
I then zerg rushed my phone simply to gain root - REALLY SIMPLE
If your still using touchwiz.... i recommend appzorter (basically organises apps)
You can chose go launcher etc if you prefer more customisation!
Then after two weeks a developer who's work I previously used for my desire came back to xda... his work was always great on desire... so i fully rooted with ODIN
yet again it was really easy, follow the guides to a t and your set!
I popped his rom on (in my sig) and never looked back since!
If you do decide to go down the custom rom route, start with a 2.3.6 build instead of trying ICS 4.0 etc... stick to solid and STABLE builds until you have more knowledge!
Enjoy
With Safestrap I know it uses a different folder to install the 2nd OS. Is there any issues with space on the phone doing this? Should we factory reset the good OS before installing the 2nd one? And this also utilizes both cores on the processor correct? Seems like I remember reading somewhere we were only able to use one core because of the locked bootloader. If I do safestrap, is backing up the folder that gets modified enough or do I need to be prepared to RSD if there is a problem since I'm on .211?
Are there any guides that explain Safestrap vs Bootstrap? I've found a couple of smaller posts about this, but nothing going real in depth.
Thanks!
Yes, sometimes there are some issues with space when doing this. No, do not factory reset the first system before installing the second one. The phone would still use both processors, that's only with Kexec only one core is in use. This is a pretty good thread on bootstrap versus safestrap http://www.droidrzr.com/index.php/topic/2678-bootstrap-vs-safestrap/
Could you please clarify on "If I do safestrap, is backing up the folder that gets modified enough or do I need to be prepared to RSD if there is a problem since I'm on .211?" generally when you use safestrap, you don't need to use RSD all that much , you have nandroids and 2 systems that it's possible to boot into.
Leviathan26 said:
Yes, sometimes there are some issues with space when doing this. No, do not factory reset the first system before installing the second one. The phone would still use both processors, that's only with Kexec only one core is in use. This is a pretty good thread on bootstrap versus safestrap http://www.droidrzr.com/index.php/topic/2678-bootstrap-vs-safestrap/
Could you please clarify on "If I do safestrap, is backing up the folder that gets modified enough or do I need to be prepared to RSD if there is a problem since I'm on .211?" generally when you use safestrap, you don't need to use RSD all that much , you have nandroids and 2 systems that it's possible to boot into.
Click to expand...
Click to collapse
I guess my concern with backing things up was returning to stock if I ever needed to. I don't think I really need to worry about an update or coming out as .211 isn't even officially available to everyone. If an update does come out with updated radios would it even install with the modifications safestrap will make?
Defiant79 said:
I guess my concern with backing things up was returning to stock if I ever needed to. I don't think I really need to worry about an update or coming out as .211 isn't even officially available to everyone. If an update does come out with updated radios would it even install with the modifications safestrap will make?
Click to expand...
Click to collapse
Mostly, on safestrap there is no problem going back to stock, as with 2 button presses we can go back to the unsafe system(stock).
No it would not install, but you can bypass this. Since Safestrap uses /preinstall to store backups and the safe/unsafe system, it's modified while safestrap is in use and all you have to do before you install safestrap is copy and paste the /preinstall folder onto your sdcard. Then when there is an OTA, uninstall safestrap and put your original /preinstall back in.
Leviathan26 said:
Mostly, on safestrap there is no problem going back to stock, as with 2 button presses we can go back to the unsafe system(stock).
No it would not install, but you can bypass this. Since Safestrap uses /preinstall to store backups and the safe/unsafe system, it's modified while safestrap is in use and all you have to do before you install safestrap is copy and paste the /preinstall folder onto your sdcard. Then when there is an OTA, uninstall safestrap and put your original /preinstall back in.
Click to expand...
Click to collapse
Thanks! Thats kind of what I needed. I figured once I start this going back to stock really won't be an option for me as the benefit of running a custom rom is more appealing. I just wanted to make sure I restore the phone back if I ever need to send it in or decide to trade/replace for a Razr Maxx someday.
Is there a reasonably safe/reversible way to get AOSP (or close) onto what is currently a stock HDX 8.9? -- running 14.3.1.0.
Sorry to ask specifically, but there are multiple threads and many of them stretch to 20+ pages - I've read through them but there's just a little too much info for me to safely digest. I'm quite comfortable with linux and development environments in general but have no direct experience in the android world, so I'm looking for a sanity check before I try to root/safestrap/AOSP this thing.
Thanks.
ljwobker said:
Is there a reasonably safe/reversible way to get AOSP (or close) onto what is currently a stock HDX 8.9? -- running 14.3.1.0.
Sorry to ask specifically, but there are multiple threads and many of them stretch to 20+ pages - I've read through them but there's just a little too much info for me to safely digest. I'm quite comfortable with linux and development environments in general but have no direct experience in the android world, so I'm looking for a sanity check before I try to root/safestrap/AOSP this thing.
Thanks.
Click to expand...
Click to collapse
1: Root
2: Install SuperSU and block updates
3: Install safestrap and make a rom slot
4: Backup your stock rom then restore the backup you made to the rom slot
5: Install the zip to your rom slot http://forum.xda-developers.com/showthread.php?t=2577826
This is only for Apollo (8.9" hdx)
hdx not hdc
Thanks, very helpful. One question: what are the options (limitations???) of setting up ROM slots in safestrap as far as how the partitions are sized? Long term I'm *assuming* that I'll eventually want to run this thing almost entirely off the rooted/secondary ROM.
1) Can a system booted from a non-stock ROM slot see files/partitions (what's the right term?) from other ROM slots (or the stock ROM?)
2) once installed, can ROM slots be resized?
3) or is the actual file system allocation dynamic?
I guess the very short question is "what's the right way to size ROM slot partitions?"
ljwobker said:
Thanks, very helpful. One question: what are the options (limitations???) of setting up ROM slots in safestrap as far as how the partitions are sized? Long term I'm *assuming* that I'll eventually want to run this thing almost entirely off the rooted/secondary ROM.
1) Can a system booted from a non-stock ROM slot see files/partitions (what's the right term?) from other ROM slots (or the stock ROM?)
2) once installed, can ROM slots be resized?
3) or is the actual file system allocation dynamic?
I guess the very short question is "what's the right way to size ROM slot partitions?"
Click to expand...
Click to collapse
The rom slots can't be resized but the rom files are like a img partition with an addition of a small data partition and cache. When you install apps in stock it can still be ran from outside the stock rom. I think of it like this. Hardware|Bootloader/Kernal/|System base|Stock rom & Other rom's or rom slots|Apps&SDFiles
I'm not to sure how correct this is but it's what I picture. You can only install so many things to the data partition in the rom slot but if you run out of space you can install to the full sd. Slashes show were I'm unsure how it interacts with the next level above.
I'm not sure if this is the right idea at all but hopefully it brings some clarity.
It's like a vm but ran from the full system with access to the host os I guess.
I guess the very short question is "what's the right way to size ROM slot partitions?
Click to expand...
Click to collapse
To answer you question, just make the rom slot as big as you can make it if your planning on using it as you main rom. Until the system is fully open (ie cracking the bootloader) can you use the full system and partitions.
Hi there,
I'm very happy with my BMM however I noticed that I am part of a minority for some reason. Anyone knows why?
Further more, it seems that most tutorials to install nightly releases are mostly done for Safestrap. I really like my BMM and had a look at Safestrap but it does not seems very appealing to me. Should I consider to switch from BMM anyway?
Is Safestrap better than BMM? What good reasons would I have to switch, apart from the fact that its a software that has more spread.
Thanks in advance.
Vonz
vonz33 said:
Hi there,
I'm very happy with my BMM however I noticed that I am part of a minority for some reason. Anyone knows why?
Further more, it seems that most tutorials to install nightly releases are mostly done for Safestrap. I really like my BMM and had a look at Safestrap but it does not seems very appealing to me. Should I consider to switch from BMM anyway?
Is Safestrap better than BMM? What good reasons would I have to switch, apart from the fact that its a software that has more spread.
Thanks in advance.
Vonz
Click to expand...
Click to collapse
Had been on BMM for a very long time while running stock ROM. When I finally decided I wanted KK and options opened up in the custom kernel area to keep hdmi, I finally flashed slimkat and JBX to slot2. After about three days, I switched recoveries to safestrap and didn't look back.
It isn't that I didn't like BMM or to say BMM is a bad recovery or didn't serve it's purpose. The main reasons were that:
1. I ran out of space fast with slot1&2 loaded up, and I couldn't find a way of repartitioning the sd card with BMM. So I would have to go to slot3 to not run into "running out of space" issues since that would not run off the system side of the sd card. Not a big deal except sometimes I need the space.
2. I didn't want two or more ROM's on my phone, I had already had a good setup with SlimKat and JBX so, I didn't use, or even want the stock ROM anymore, but can run into trouble trying to flash them into slot 1 of BMM, while you can flash to slot1 on safestrap with no problems at all.
3. You CAN repartition the sd card with Safestrap so if I did decide I wanted another ROM, I could repartition my sd card to better accomodate my ROM's and apps, and not have to worry about losing space again.
TL : DR I was going to have to make sacrifices or accomodation's to keep BMM around so it is safestrap for me Maybe I am lazy, maybe not, but either way it is right in front of my face with safestrap, with BMM I did some digging, didn't find, lost interest and flashed!
Well,I don't think that SS is better because SS takes free space from internal memory for second slot.
In BMM second slot is on webtop partition,so you have your full 8gb available.
Sent from my Razr XT910
welder73 said:
Well,I don't think that SS is better because SS takes free space from internal memory for second slot.
In BMM second slot is on webtop partition,so you have your full 8gb available.
Sent from my Razr XT910
Click to expand...
Click to collapse
Ahh, I agree, and disagree. Yes BMM will put the second slot on top of the webtop partition, but that is only 1.3 gb if I am correct. One ROM and a few bulky apps/games, and slot2 is filled up. You once again get insufficient space toasts, even with another 2 gigs sitting on your card, because your system partition is filled up(slot 2 apps go into the slot2 partition which was webtop.) Sure you can swap back and forth between ROM's for various things but, some people don't want to have to swap between 2 ROM's for all their apps to accommodate a recoveries limitations that doesn't suit them.
And also remember some of that 8 gigs is cache, so we really never get to use it for our own purposes anyways, it is for the system.
Safestrap you can flash to the stock slot, and you can reconfigure the partitions to accomodate any other slots so that you don't get insufficient storage issues. Does it use internal memory, yes it does, but then again, that is the best source for unhindered space, and the phone does have ext. card capabilities so it isn't putting near the burden on us as, say, it would a nexus device.
Just my opinion, and I have nothing against BMM, it was a great recovery! It just doesn't suit my needs anymore.
Draxin said:
Ahh, I agree, and disagree. Yes BMM will put the second slot on top of the webtop partition, but that is only 1.3 gb if I am correct. One ROM and a few bulky apps/games, and slot2 is filled up. You once again get insufficient space toasts, even with another 2 gigs sitting on your card, because your system partition is filled up(slot 2 apps go into the slot2 partition which was webtop.) Sure you can swap back and forth between ROM's for various things but, some people don't want to have to swap between 2 ROM's for all their apps to accommodate a recoveries limitations that doesn't suit them.
And also remember some of that 8 gigs is cache, so we really never get to use it for our own purposes anyways, it is for the system.
Safestrap you can flash to the stock slot, and you can reconfigure the partitions to accomodate any other slots so that you don't get insufficient storage issues. Does it use internal memory, yes it does, but then again, that is the best source for unhindered space, and the phone does have ext. card capabilities so it isn't putting near the burden on us as, say, it would a nexus device.
Just my opinion, and I have nothing against BMM, it was a great recovery! It just doesn't suit my needs anymore.
Click to expand...
Click to collapse
I agree,everyone has different needs,for me it's enough 1.3gb.
But what do you mean by "you can flash to the stock slot",you can do it with BMM also?
Sent from my Razr XT910
welder73 said:
But what do you mean by "you can flash to the stock slot"
Sent from my Razr XT910
Click to expand...
Click to collapse
I guess I didn't complete the comment as I did in the previous post. The stock slot can be flashed in BMM but problems can arise. At least they did for me. It wasn't for a lack of trying but, when I was done and rebooted, I got logo, hijack, and then blank, twice! First time restored stock slot and redownloaded ROM, second time ended up being a firmware reflash.
I am not above saying I did something wrong, I probably did, but heck if I know what it was, I had no problem flashing slot2, and have had zero issues with safestrap. Same download of ROM and Gapps that were used in second flash was used in slot2 BMM and Safestrap. So I am not going to say BMM CAN'T do it, I am just not going to say it can when I couldn't do it successfully.
So I retained from previous comments that SS could help with saving memory? Correct? If so that is definitely interesting. Further more BMM is discontinued development am I right?
I will give SS a go and see what happens (even though the interface is not as schmick as BMM, oh well..!) .
So in order to switch from BMM to SS I shall save my stock ROM that is on slot 1 and my CM10 that is on slot 2, then uninstall BMM from settings/apps menu, then install SS, reboot in SSR and install CM11 from zip file correct?
Cheers.
ttt
vonz33 said:
So I retained from previous comments that SS could help with saving memory? Correct? If so that is definitely interesting. Further more BMM is discontinued development am I right?
I will give SS a go and see what happens (even though the interface is not as schmick as BMM, oh well..!) .
So in order to switch from BMM to SS I shall save my stock ROM that is on slot 1 and my CM10 that is on slot 2, then uninstall BMM from settings/apps menu, then install SS, reboot in SSR and install CM11 from zip file correct?
Cheers.
Click to expand...
Click to collapse
Yes BMM does seem to have discontinued development. Doesn't mean Boot menu manager right now isn't good, just means there probably won't be any more improvement.
As for saving space, no, safestrap doesn't do that. When you install a second slot in BMM it will install it on top of the webtop partition(read and watch your tutorial's on how to do this correctly.) So it isn't taking any extra space yet, the downside to that is that it is limited to 1.3gb. If you don't use alot of apps, or going to be using it strictly for testing ROM's, then it isn't a big deal. Any more slots after that eats into your internal storage.
Safestrap from what I understand, won't install a slot on top of webtop, instead, when you install to slot 1 it will be taking space from your internal storage right off the bat. You can choose from 1gb, 2gb, or 3gb, size for your new slot partition. Same for any more slots you make. The more space you take for one slot partition, the less you leave for any others you would make. From what I understand though, with safestrap, you CAN still remove webtop for stock slot (I haven't needed to yet) so the 1.3 gb is freed up for more storage to stock.
As welder and I had discussed prior, it completely depends on your needs. If you don't have alot of apps, and want to dual boot a stock ROM and a custom one... BMM will do you fine. If you have a lot of apps or games and want to dual boot both ROMS with both of them loaded up, then safestrap is the way to go. Some ROM's play well with one recovery but not the other, there are also work arounds in some cases.
Any of your backups from one will not work with the other
Draxin said:
Yes BMM does seem to have discontinued development. Doesn't mean Boot menu manager right now isn't good, just means there probably won't be any more improvement.
As for saving space, no, safestrap doesn't do that. When you install a second slot in BMM it will install it on top of the webtop partition(read and watch your tutorial's on how to do this correctly.) So it isn't taking any extra space yet, the downside to that is that it is limited to 1.3gb. If you don't use alot of apps, or going to be using it strictly for testing ROM's, then it isn't a big deal. Any more slots after that eats into your internal storage.
Safestrap from what I understand, won't install a slot on top of webtop, instead, when you install to slot 1 it will be taking space from your internal storage right off the bat. You can choose from 1gb, 2gb, or 3gb, size for your new slot partition. Same for any more slots you make. The more space you take for one slot partition, the less you leave for any others you would make. From what I understand though, with safestrap, you CAN still remove webtop for stock slot (I haven't needed to yet) so the 1.3 gb is freed up for more storage to stock.
As welder and I had discussed prior, it completely depends on your needs. If you don't have alot of apps, and want to dual boot a stock ROM and a custom one... BMM will do you fine. If you have a lot of apps or games and want to dual boot both ROMS with both of them loaded up, then safestrap is the way to go. Some ROM's play well with one recovery but not the other, there are also work arounds in some cases.
Any of your backups from one will not work with the other
Click to expand...
Click to collapse
Thanks for your reply, Draxin.
Which one are you using? I take it you are using BMM. You are talking about a tutorial.... this is A thing I could not find. Let me know if there is one, and if so where I can get it from.
My main concern is that I wanted to give a shot to CM11 and it seems that the install is not 100% reliable, even with the BMM workaround. So maybe I shall wait for a release candidate to occur.
I have 80 user apps apparently under CM10 according to Titanium Backup, is that a lot?
Also you talk about this webtop thing... After some research it appears that a webtop is a desktop integrated in a web browser. What does it have to do with android platform more exactly?
I mostly have 2 used slots, Official Moto ROM on slot 1 (just in case but never use it) and CM10 on slot 2 as it was advised on a youtube video. If I have to test a kexec ROM I usually backup my CM10 and try it out on slot 2, to avoid munching all the space on side storage.
So what do you recommend for us at this stage?
Thanks in advance.
Vz
vonz33 said:
Thanks for your reply, Draxin.
Which one are you using? I take it you are using BMM. You are talking about a tutorial.... this is A thing I could not find. Let me know if there is one, and if so where I can get it from.
My main concern is that I wanted to give a shot to CM11 and it seems that the install is not 100% reliable, even with the BMM workaround. So maybe I shall wait for a release candidate to occur.
I have 80 user apps apparently under CM10 according to Titanium Backup, is that a lot?
Also you talk about this webtop thing... After some research it appears that a webtop is a desktop integrated in a web browser. What does it have to do with android platform more exactly?
I mostly have 2 used slots, Official Moto ROM on slot 1 (just in case but never use it) and CM10 on slot 2 as it was advised on a youtube video. If I have to test a kexec ROM I usually backup my CM10 and try it out on slot 2, to avoid munching all the space on side storage.
So what do you recommend for us at this stage?
Thanks in advance.
Vz
Click to expand...
Click to collapse
I am using safestrap now, I had been using BMM for a while til I started flashing custom ROM's. After that safestrap suited MY needs better
BMM tutorials: http://forum.xda-developers.com/showthread.php?t=2325764
CM11 requires safestrap 3.65 http://forum.xda-developers.com/showthread.php?t=1391900
If you really want to try out CM11, and then it doesn't live up to your expectations, you can always go back to BMM and restore the backups you saved to where you are right now. SlimKat I know for a fact will install with BMM. You just have to make sure to completely uninstall whatever recovery you had previously, before adding a new one
It doesn't matter so much how many apps you have, as, how much space they take up. If you are just taking a ROM for a test run, you don't need all your apps, especially if you are dual booting, if you are going to use slot 2 as a daily driver, and they are bulky apps, that is when you get concerned.
Webtop, basically allows you to explore your phone as if it were a desktop computer, bluetooth keyboard, and the phone's touchscreen will act as a laptop touch pad, or you can run a bluetooth mouse, and using a typical tv with hdmi in as a moniter. Motorola thought it would be a bigger hit than it turned out to be. It really is a neat idea, turning your phone into a handheld desktop but, it has plenty of limitations. For most people, if they even know what it is, it's just taking up space.
What do I recommend? Well, it completely depends on what you are looking to do. Like I said before bro, you can save what you have with BMM, uninstall it and try out safestrap. If you don't like it, uninstall safestrap and go back to BMM and reinstall your backups, no harm, no foul. If you really like safestrap, then dump your BMM backups as they are just taking up space at that point. With titanium backup, as long as you saved your apps and modified data, call logs, wifi, and sms, really all you cost yourself in the switch, is time setting everything back up.
If I helped, hit the thanks.
Cool bro.
Will try ST to see what happens. Thanks again you're a true gentleman.