SafeStrap vs CWM BootStrap

[Dad23Boys77]

SafeStrap vs Droid 3 BootStrap

So I've actually posted a similar question to this before but I really didn't get an answer to my question. So I'd first like to say, sorry for asking the same thing again. I'd also like to mention that I tried to do a google search before posting this to find an answer to my question with absolutely no success. So, without further delay is my question(s) are this: (I'm still relatively new to the whole rooting seen, so if possible, please provide responses in laymans terms, thanks)

1. What is the difference between SafeStrap and Droid 3 Bootstrap (sorry, but I dont know whose bootstrapper I have installed.....hashcodes, etc)?



2. Is there an advantage to using one over the other?



3. I've also read about something being referred to as fastbooting/faststrap. Are these 2 one in the same or are they completely different?



To any and all that reply, thank you in advance for your assistance.



Dad23boys77

 

[tcrews]

Droid3Bootstrap is a method to boot to a recovery that is not the stock recovery. It's by Koush and works with Rom Manager (also by Koush). To boot to recovery you launch the Droid3Bootstrap app and select reboot recovery. Hashcode "tweaked" that source and added the ability to boot to recovery from a powered off starting point. This is nice because if your phone is bootlooping you can't get to the Droid3Bootstrap app to boot to recovery.

Hashcode also wrote Safe-strap. This is different in that it is designed to allow you to install a ROM to a second "system" instead of overwriting the phone's original system. It basically uses the /preinstall location and mounts that as /system and install the ROM there. This allows for your stock /system to remain untouched and easily accessible by using safe-strap to switch back to the stock /system.

Safe-strap is incompatible with droid3bootstrap. Backups from one will not work with the other.

Safe-strap is a great way for testing a rom build (for developers) but I'm not sure it's the best way for just running a ROM. You are using up system resources (two /system partitions basically) and relying on the safe-strap boot software to boot to your "other" rom.

Hashcode has releases of his kang'ed CM7 for both safe-strap and the standard Droid3Bootstrap. So pick your poison and go with it......

 

[guidot]

From hashcode's blog, D3Bootstrap backups ARE compatible with Safestrap. They aren't compatible in the reverse however.

And Safestrap isn't 2 'systems'; He's copying userdata to /emmc which is an unused partition. The ROM then gets installed to the actual /system location.

 

[tcrews]

No, he mounts /system as /systemorig (or something like that) and mounts /preinstall as /system. Safe-strap does not touch the phone's /system partition when enabled. You have the "new" /system and the old /system (now /systemorig) as he specifically states he does not touch the stock /system of the device so you can switch back easily.

A Safestrap installed ROM is on a separate /system partition of it's own....not the default "stock" ROM's /system.

 

[guidot]

Either way, its a much safer system IMO. Starts on boot without having to use bptools.

 

[Endoroid]

The idea of safestrap being you can still receive OTA updates as your stock blur is still there

Sent from my rooted xt860

 

[cvhovey]

The idea of safestrap being you can still receive OTA updates as your stock blur is still there

Do you need to use Rootkeeper or some other method to retain root when using Safestrap and then receiving OTA updates? Yeah, I did a search on this but not seem to turn up anything definite as to the way to go.

 

[guidot]

Do you need to use Rootkeeper or some other method to retain root when using Safestrap and then receiving OTA updates? Yeah, I did a search on this but not seem to turn up anything definite as to the way to go.

I would suggest this because everytime we find a hole, they fill it in.


Sent from my Safestrapped, Rooted, ROM'd XT862

 

[neowiz73]

yeah essentially it's a boot loader that allows you to dual boot ie. Grub boot loader for Linux. which i'm surprised more haven't tried to use the old grub boot loader for separate roms since android is built on a Linux kernel.
but nonetheless, safestrap is a much safer method for devs and users. plus you could essentially have custom kernels etc even on "locked" phones. if anyone has used the bootloader for the HP touchpad it's a very similar concept.