yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 3] Hashcode:
Hey MVP,

Thanks! I'll make a note of the advanced restore "go back" bug. I confirmed it on my phone as well.

FYI, you can only restore the non-safe backups while Safe System is DISABLED.

The primary system is called /systemorig in recovery and it is already mounted in most cases. I removed it from the mounts menu because I didn't want anyone to accidentally select "format /systemorig".
[Motorola Droid 3] mvp3:
I see. Thank you hashcode.:)
[Motorola Droid 3] DoubleYouPee:
Any help Hashcode? I just let it go for 5min but nothing happens :(
[Motorola Droid 3] Hashcode:
Hi again MVP,

I had a question for you. I'm wondering how to support the other models of the Droid 3 hardware (XT860, XT883, Milestone 3, etc). And I noticed in your post and from user's sending me files that they have different partition sizes making this difficult.

For instance, the Milestone 3 shows this in "cat /proc/partitions":

179 55 512 mmcblk1p23 preinstall

179 56 2588160 mmcblk1p24 userdata

The /preinstall partition is very small, and they have that space allocated to the /data partition.

(compare to VZW Droid 3):

179 55 491520 mmcblk1p23 preinstall

179 56 2097152 mmcblk1p24 userdata

I noticed you walked Nanostrike through a somewhat complicated way of using the fastboot files to expand his /preinstall partition...

I was wondering if you thought it might be useful for me to build a "resize2fs" feature into Safestrap so that devices with the wrong sizes can be altered.

Basically, the process could look at the /proc/partitions output, do some math and alter the partition sizes to allow for a 2nd-system to be placed on /preinstall.

I'm wonder what the down sides of having a slightly smaller /data partition would be for the non-US users, and if this would have any bad side effects for say fastboot restore, etc.

Looking for input.
[Motorola Droid 3] magicelf:
I currently have the first released Bootstrap installed. I made a nandroid backup of my original settings, in case I ever need to go back to stock. I understand we can't use old backups with Safestrap.

Can I make a nandroid of my current settings (using bootstrap), flash back to stock, install safestrap - make stock backup, flash back to my current settings (using bootstrap) and delete bootstrap (and old nandroid backups)?

Also, there seems to be differing opinions on how to go about deleting Bootstrap/Recovery. What is the best way to do this?
[Motorola Droid 3] Hashcode:
No need to have to restore, uninstall, backup, install.

To make your previous backups available in Safestrap, you can move the original settings backup that you made from /{your sd card}/clockworkmod/backup to /{your sd card}/safestrap/backup.

MAKE SURE YOU'RE COPYING THE RIGHT BACKUP OVER (it will have a /systemorig.ext3.tar file in it).

Backups made with Koush's Bootstrap recovery are *NOT* compatible with Safestrap.. if restored in Safestrap it will put an incorrect ROM in your Safe System partion.

To get rid of Koush's Bootstrap, just uninstall the APK. Safestrap cleans up the old hijack files when you use the "Install Recovery" button.
[Motorola Droid 3] DoubleYouPee:
Then how come it's not working for me?

I just tried last time:

-disabled recovery in Safestrap app

-uninstalled Safestrap app

-rebooted

-reinstalled safestrap app

-enabled recovery

-rebooted

-pressed MENU at new bootscreen

-vibrate

-BLACK SCREEN

I'm on 5.6.890, rooted, debloated, STOCK ROM.

Please answer, I don't wanna try new ROMs without safestrap :(

EDIT: it's bootlooping now at the DROOOOID sound :mad::mad:

Edit: Ok flashed back to stock rom... Gonna give it another go now
[Motorola Droid 3] magicelf:
I think I have Koush's bootstrap. Would my backup-restore scenario work in that case?
[Motorola Droid 3] Hashcode:
As long as you use the same recovery to restore the backups that they were made with. I think you'll be fine.
[Motorola Droid 3] beard0:
Any insight to what my problem is?
[Motorola Droid 3] Hashcode:
When you see this error, can you go to "advanced" and "show log" and let me know what this says?
[Motorola Droid 3] beard0:
Lol I'm gunna pass out cause I got an early day tomorrow but ill try and do that tomorrow morning I'll be sure to let you know what it says thanks
[Motorola Droid 3] mvp3:
Hi Hashcode,

Yes,I think this way that using resize2fs might sovled 2nd-system problem on xt883 etc.

But I have used Safestrap v.92 in xt883 rom,backup system to sd card failed,

So may be more things need to adjust.

xt883 xt862 hardware are same,but radio.img is different,I wonder if these mod rom can run on xt883 radio.img.

But may be chinese would mod xt883 rom later.

I guess me863 and xt860 has no cdma.different from xt862 xt883.

xt862 and xt883 both has globle mode.

sorry my english is not good.:D
[Motorola Droid 3] Hashcode:
In theory yes, that's how you would do it.

In reality, the /system backups won't work correctly because they will be applied to your /preinstall partition with the hijack in place as it was while using that Bootstrapper. 2 hijacks is always bad.

/data might be a different story. You might be able to advanced restore your /data for ROM that you were using and get ok results.

Mixing and matching backup / bootstraps is always touch and go.
[Motorola Droid 3] matthskim:
My idea is to figure out or learn to use solely Safestrap utlizing previous backups, if needed. What if I restore them in non-safe system in Safestrap? Would it still put it into /preinstall rather than /system? I am just pondering.

Thanks for your response.
[Motorola Droid 3] Hashcode:
/system partition backups will always get restored to the /preinstall partition in Safestrap, that's just how it's setup (safe or non-safe mode, it's the same). The original system is /systemorig and unfortunately the tar backups have the partition name as the root so all of the files in the tar start with system/*, so it's not like you can even rename the system.ext3.tar to systemorig.ext3.tar and have it restore to the original system.

The best way to use Safestrap (and I'm just calling it the way I envisioned it) is just like any other recovery:

Completely ignore the fact that you can in theory dual boot with it. Leave Safe Mode on all the time.

When you want to swap ROMs, do a backup and start a new ROM just like Koush's recovery.

Go nuts like you did on your previously unlocked phone (if you had one) and just know that you'll always be able to get back into recovery to fix it.
[Motorola Droid 3] matthskim:
Thank you for our reply.

So, I install the original stock rom with permaroot and make a backup of the rom right after the safestrap installation for disaster recovery. Then, when do you envison would be the time to restore this backup, if any?

Also, I understand that I can install any non-safe rom as long as the "/system/etc/rootfs" folder is deleted. Is this something I do/remove to the zip file that I download? If so, wouldn't it damage the file? or is it something that the developer has to do for us?

Sorry to bother you with many questions, but I would like to clarify my thoughts and understanding before I start.
[Motorola Droid 3] Hashcode:
The idea was to use that "master" backup somewhat like you would an SBF. Only if you needed it. And only swap back to non-safe mode for OS updates, etc.

I've even put up MotoBlur "ROM"s on my blog to run in Safe Mode if you happen to want a nice "safe" fallback ROM for work, etc.

For the most part the ROMs for Droid 3 have all had the bad /system/etc/rootfs files removed. Doesn't hurt to double check tho. The exception to this rule would be any AOSP ROM, like CM7, etc. Those ROMs actually need the files in that folder to boot.

And there's no such thing as dumb questions when it comes to rooting/recovery of your phone.
[Motorola Droid 3] zeroktal:
backup, but no restore

I did a backup, flashed another rom, then tried to restore my backup.

I get Can't mount /system no matter what I try. Any ideas? I have the xt862, flashed to xt883 and then back to xt862 before trying to restore it.
[Motorola Droid 3] matthskim:
Thanks a lot for your explanation.

Now, it makes a lot more sense why you developed this dual-system scheme. What a great idea and excellent execution of the idea!!!!!!!!!

I will keep following your development.

Keep up the good work for us.
[Motorola Droid 3] celicaus:
I got bootloop with Safestrap Enabled.

I installed the Safestrap 1.04 in the rooted stock ROM and flashed a customer ROM following the instruction. When rebooting, it falled in the loop of "Android BootMenu" and power-on reboot.

My D3 is on VZW.

Can you guys please help me? Thanks so much!
[Motorola Droid 3] Hashcode:
Which ROM are you flashing? And when you say "bootloop" are you soft-bricked atm? Or can you re-access recovery?

If you ROM isn't an AOSP ROM such as CM7 or NarcotICS, double-check that the flash .zip file doesn't have an erroneous directory in /system/etc/rootfs. We had an issue early on where the deodexed ROM had some testing files in that directory and Safestrap will attempt to put them in the root of the filesystem when it 2nd-inits.
[Motorola Droid 3] Hashcode:
I've seen this happen 1 other time for a Bionic user. Apparently he ran out of internal memory during the toggle to safe system, so that his "stashed" data was corrupted.

You can use the "QUICK" toggle to get back to non-safe mode, and then you will probably have to restore your data via "advanced restore" -> "userdata".

Let me know how it goes.
[Motorola Droid 3] Willis111:
I'm running a bell xt860 and my output from 'cat /proc/partitions' looks the same as yours regarding the preinstall and userdata partitions. I've attached the full output of 'cat /proc/partitions > /sdcard/partitions.txt'. I can't boot anything via safestrap or your other bootstrap besides my own recoveries. Let me know if anything else would help.
[Motorola Droid 3] Hashcode:
Can you get me the output of the following terminal commands:

ls -l /system/bin/log*

cat /proc/cmdline

busybox df

Thanks!
[Motorola Droid 3] celicaus:
My D3 has original ROM (Build Number 5.5.1_84_......). I rooted it. I installed "Droid3Safestrap-1.0.apk". My D3 can enter CWM recovery when rebooted. I also can Enable Safe System. I wiped all data and flashed "Maverick for the Droid3 (MavROM) - BETA v1.0". When I rebooted phone, it just went to the splashscreen and then rebooted phone. And again and again. So what's my issue?

Thanks so much!
[Motorola Droid 3] Hashcode:
I'll have to take a look at the flash .zip for MavROM and make sure there's no extra /system/etc/rootfs files in it.

And, I'm not sure what OTA version the binaries for his ROM are using. (Compared to your stock version).

I know that Liberty and some other ROMs should work perfectly. I haven't tested MavROM yet.
[Motorola Droid 3] DoubleYouPee:
I have used maverick rom with safestrap - it works fine. Not sure what you mean by binaries but the ROM is based on the new 5.7.xxx update
[Motorola Droid 3] Willis111:
I've attached those outputs below as per your request. Thank you so much for taking the time to look into this for us xt860 users. Again, let me know if there's anything else I can do to help.
[Motorola Droid 3] zeroktal:
Partitions the issues>

Fixed with non fastboot rom flash.
[Motorola Droid 3] aaron1389:
Thanks!

It work Great!
[Motorola Droid 3] beard0:
So I tried again only with bioweponx rom instead of liberty and got it working :) thanks Hashcode lol I like playing with my phone and now I can do it without wasting twice as much time trying to make it work again lol

/Droid3
[Motorola Droid 3] Hashcode:
Wow, this is sort of a mystery. So far I'm not seeing why Safestrap isn't booting the 2nd-system.

May I get your /init*.rc files? I know I may have asked before at some point but we'll try it again.

Thanks.
[Motorola Droid 3] eastside770:
i just installed this and now my fone isnt booting up just has a blk screen i was on monster rom going

edit: ok so i installed liberty successfully and now wondering is there any way i can get my texts from back up
[Motorola Droid 3] Hashcode:
Titanium Backup for swapping ROM to ROM and restoring apps. But you'd need to revert back to your previous ROM and do a Titanium Backup there first.
[Motorola Droid 3] eastside770:
it wont boot up i did a back up of it and it would just stay at a blk screen after the safeboot screen
[Motorola Droid 3] Hashcode:
So to clarify:

- You made a backup of your previous ROM (which was running in Safe Mode? or Non-Safe Mode?)

- You restored it and then rebooted and it gets stuck at a black screen?
[Motorola Droid 3] eastside770:
both safe mode and non safe mode and yes
[Motorola Droid 3] celicaus:
I also flashed Liberty ROM. My D3 has same behavior.
[Motorola Droid 3] Willis111:
Here they are again. I also uploaded them in the me863 thread, figured you'd be more likely to see them here. Trying to dig up some info from the atrix forums, I think they might have had the same problem with that device(the bell model took a lot longer to get roms etc I remember). Of course, we appreciate all your hard work and even just looking into getting this running on a phone different than your own is awesome. tyvm
[Motorola Droid 3] Endoroid:
I agree with Willis. Its nice to see some dev for our phone. Thank you Hashcode
[Motorola Droid 3] MrJudylicious:
i agree, hashcode is a BA. are you guys even getting to the M or the safestrap splash screen? are you able to get into the modified CWM? celicaus - are you on 5.7?
[Motorola Droid 3] celicaus:
Yes, I got M and safestrap splash screen. When I tap "menu" button, D3 goes to the modified CWM. If I don't tap "menu" button on the splash screen, D3 goes to M again and in the loop of switching between M and splash screen. My D3 is still on 5.5?

Anything is wrong?

Thanks,
[Motorola Droid 3] MrJudylicious:
i would turn safesystem off, which should revert back to your blur system. i would then grab the OTA and go to 5.6.890. I think thats why the roms wont work. the phone should pick it up by itself, as its been a while since it came out. if youre already on 5.6, then it could be a different problem. if you cant get into motoblur, i would sbf, but thats just me.
[Motorola Droid 3] Hashcode:
You could try to sort of "restart from scratch" without fastboot restoring like this:

- Go back to non-safe system

- Restore your full backup that you made of non-safe system

- Check that you can boot back into the OS? (You should be able to)

- Then toggle to Safe Mode

- Wipe data/cache, and format /system.

- Flash ROM

- Reboot, and check to see if you can get into that ROM.
[Motorola Droid 3] celicaus:
Thanks a lot, Hashcode.

I can go back the OS (stock) when the safe system is disabled. My issue is that the phone can not boot into the flashed customer ROM. It stays on the splash screen for a few seconds and then reboots. My stock ROM build # is 5.5...... Should I update it to 5.6....?

Thanks again!
[Motorola Droid 3] MrJudylicious:
yes that is why the roms will not boot.
[Motorola Droid 3] ckarrow2:
When in the safe system I cannot update Safestrap. In the safe system I have ver 1.02 installed. I've downloaded ver 1.04 but it will not install on the safe system. It does install on the non-safe system and updates the recovery.

Am I missing something?
[Motorola Droid 3] Joe.cotto:
What Rom you running? If you're running MavRom it comes install with 1.02. You'll have to go to system/app and delete the safestrap, reboot phone,and then install Safestrap 1.04.
[Motorola Droid 3] celicaus:
I came back blur system. When I tap \setting\About Phone\System updates, nothing happens. It doesn't pick any updates. What's wrong?

Thanks for help!
[Motorola Droid 3] Phibernaut:
I updated SafeStrap to the latest version while in Safe Mode (oops), breaking the connection to my original backups. If I understand correctly, I can move the files from the clockworkmod folder to the appropriate SafeStrap folder and simply disable Safe Mode to restore the original system?

Edit: assuming all the files are SafeStrap generated (system.ext3.tar, etc).
[Motorola Droid 3] Hashcode:
Yep. Just move the backup folders.
[Motorola Droid 3] Hashcode:
MavROM includes the Safestrap recovery files? Blech. I'll check the ROM in a bit. That's bad news.
[Motorola Droid 3] Phibernaut:
Crud. My original Safestrap backup isn't stock Blur. Are there any advantages to having stock Blur for the non-safe system? Can I use the Safestrap 890 zip in non-safe mode?
[Motorola Droid 3] Hashcode:
no real advantages to using stock blur as non-safe other than you can grab OTAs very easily.

And the Safestrap motoblur-890.zip is made for Safestrap to use in 2nd-system.

I've never tried to flash to the original system by using Koush's Bootstrap. Bad things could happen. But if you do try it let me know. Have a fastboot restore handy!
[Motorola Droid 3] Phibernaut:
Aren't all the OTA updates normally/eventually worked into the ROMs? Or are there certain things we can't access with a Safestrap flash?

Edit: I suppose any backup system is better than nothing, but I would like to see an easy way to change the original system for "oops" moments such as this if nothing else. I'm not familiar with changing systems outside of Safestrap so this has become a well used utility.
[Motorola Droid 3] ckarrow2:
Worked Great! Thanks for the advice!
[Motorola Droid 3] celicaus:
Hello MrJudylicious,

You are right. I flashed 5.6.... stock ROM and Safestrap works now! Thank you so much for your time helping me.

Special thanks to Hashcode for the greate tool and helping me.

Now my D3 can breathe the fresh air and enjoy the diversity of android world.
[Motorola Droid 3] Phibernaut:
Do I need to do anything special in Safestrap to use the fastboot 890 files in the development sticky post? I'm assuming its best to toggle into the original system first so enabling safe mode creates stock backups?
[Motorola Droid 3] Hashcode:
The MotoBlur ROMs I posted are for use in the Safe System only as a stock fall-back but don't want to turn Safe Mode off.
[Motorola Droid 3] mvp3:
thank you hashcode

I had flash back xt883 rom,and installed the safestrap 1.05

but still could not backup system,

below is the error log:

if can't mount the preinstall,I think we can skip this partition.

please take a look
[Motorola Droid 3] Phibernaut:
I understand your 890 files are meant for Safestrap use, but what if I want to use the fastboot recovery files in the Droid 3 Android Development sticky post? I'm on my D3 or I'd paste a link. Its listed above this discussion in XDA. Can I just follow their instructions or is there something special I need to do for use with Safestrap?
[Motorola Droid 3] Hashcode:
Definately follow their instructions (to use the fastboot files you'll need Motorola's RSDLITE for Windows or the linux files mentioned in the posting.)
[Motorola Droid 3] Hashcode:
You've just found the reason why XT883 and XT860 out of the box can't run Safestrap.

It looks like there's a glitched image of /preinstall where journaling is turned off. Dropping the FS to ext2.

In theory, you could dd the /preinstall partition from the VZW fastboot files for 5.6.890 to the /dev/block/mmcblk1p23 device and it will fix the size of the partition as well as the FS.
[Motorola Droid 3] Joe.cotto:
What's the missing bitmap on the splash screen about? Just wondering just in case I may have miss something. Thanks.
[Motorola Droid 3] Phibernaut:
Thanks, I was concerned using those files would overwrite something important for normal Safestrap function.
[Motorola Droid 3] Hashcode:
You can safely ignore the missing image message. I'll be putting out a fix for that later tonight.
[Motorola Droid 3] TBBle:
Dropping the journal was done by e2fsck in response (I guess) to the superblock pointing to the journal somewhere outside the 512kbyte partition. Assuming I didn't break my /preinstall earlier, then presumably the stock image is of an ext3 filesystem that wasn't cleanly unmounted... (Edit: partition is marked clean but needs_recovery. I guess it was cleanly unmounted after writing a huge whack of data, but before the journal had finished flushing.)

Wouldn't that have the same issue as now, where mmcblk1p23 would contain the first 512kbytes of a 490Mbyte partition, and fail to mount?

If there _was_ some magic that stretched the mmcblk1p23 partition when you tried to dd a file that was too big to it, then you'd be overwriting the start of the userdata partition.

I'd be interested to know the checksum of other non-Droid3 owner's mmcblk1p23 partitions. Mine is:

root@umts_solana:/# dd if=/dev/block/preinstall | md5sum
1024+0 records in
1024+0 records out
524288 bytes transferred in 0.087 secs (6026298 bytes/sec)
2b0c5ad4e4a215ba9f904f4f2494ba9a
root@umts_solana:/#

Edit: Just tried to format /dev/block/preinstall as a 512kbyte ext3 partition, but both stock mke2fs and the one in safestrap generate a filesystem that'll only mount with "-t ext4" not "-t ext3". And recovery.fstab in Safestrap specifies ext3. So next time I'm on a Linux box, I'll generate myself a 512kbyte ext3 partition image and dd it onto my device, and that should get Safestrap working until you (Hashcode) fix it to gracefully ignore unmountable /dev/block/preinstall, or skip it if it's only 512kbytes long, whatever seems appropriate.

Edit: Oh yeah, tried to format /system in safestrap, still wouldn't mount. I guess that's the same problem from the paragraph above, that it generated an ext4 partition but tries to mount it using ext3.
[Motorola Droid 3] mvp3:
what do you want?

backup system or flash cm7?

why confused in preinstall partition.
[Motorola Droid 3] TBBle:
For now, ability to make a full backup. I'm not having any issues with MotoBlur (except the occasional Chinese-only widget) and I found Cyanogen way too heavily-loaded when I ran it on my HTC Dream so I'm in no hurry to leave MotoBlur.

I don't understand what you mean by this.
[Motorola Droid 3] dove0rz:
ME863 is in the same situation now.
[Motorola Droid 3] mvp3:
sorry,my english is not good,I mean,if you just need make backup,may be hashcode could make an options or special version to us,to automatic skip mount/backup/restore the preinstall partition if he can check the preinstall is small,because nothing in the preinstall partition,so no need to do these action.
[Motorola Droid 3] TBBle:
Ah, I see. Yes, that would be the quickest fix in Safestrap.

The rest of my mucking about was trying to get it working _before_ Safestrap is fixed, particularly if Hashcode decides to do more than just skip small preinstall partitions but instead take the time to develop a system to expand the preinstall partition to match the Droid 3 TX862.

I would have had a go myself, but I couldn't see a source drop for Safestrap in a brief search.
[Galaxy S II Q&A, Help & Troubleshooting] Dramadeur:
This version of the device cannot be updated - Kies, after I installed ("flashed") XWKDD from here, which is the same as my original (which could obtain updates and came along with my phone) kernel which name was starting as XWKDD-L..16 something

Now I wonder how can I restore or retrieve my previous kernel with which I could use kies to check for updates and have a possibility to update via kies.
[Galaxy S II Q&A, Help & Troubleshooting] MattP79:
This is the issue I have after flashing XWKI4. As best I can guess this is due to network lock. Although all the firmware has loaded and most of the TMU defaults have gone if I dial *#2

72*(IMEI)# I can only select TMU rather than XEU or any other CSC code.
[Continuum General] Jaidynne:
Okay this is a silly question, probably... I might be over looking something but...

Is there any real point to having an ipod touch if I have my handy dandy continuum? They basically can do the same things, right? And my continuum can call/text people, where as my ipod can't? Maybe the ipod has more storage but that is about it I would assume? Correct me if I am wrong lol.
[Continuum General] asellite:
F**k your ipod and buy a bigger micro as card.
[Continuum General] Nuckin:
Not to mention, if you have a Google Music account, your phone can stream up to 20,000 of your uploaded songs, not something you can do on your ipod.

Personally, I took the free 8gb ipod touch I got with my Mac and Gamestop gave me $72 of store credit for it, helloooo PS3 games :p