yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 3] chevycam94:
I am about to download it and give it a shot. I will let you know.
[Motorola Droid 3] ovelayer:
Awww you broke it lolol:p

After installing 1.08f I found that

1. It doesn't completely wipe now

2. It doesn't fully install zips

3. It doesn't allow a second .zip to be flashed right after each other

4. icon (top hat) is hard to see as its perty much black on black

Other then that.... it sure does look pretty lol....I know not funny...:(
[Motorola Droid 3] buckmarble:
I have flashed multiple things today and also used usb mounting today. All is working for me. I rebooted into stock system and removed recovery then unistalled the safestrap app then installed 1.08f and installed recovery. Rebooted and reenabled safesystem and good to go.
[Motorola Droid 3] ovelayer:
Have you tried to factory reset or install zips to your safe system sence you installed it?

Because like you the installation of the safestrap and swap to safe system worked great for me as well..it just after that when you go to flash zips in safemode you run into problems..as stated above

I am on the xt862 just so ya know
[Motorola Droid 3] Rick#2:
Hey ovelayer, try to download it again from the first link. I found a bug in the safe-system flashing that I didn't catch during my first bout of tests.

I guess I ought to just call it 1.08g by now... haha I suppose the "f" could be for "fail", or "flop". But "g" is for "good"!
[Motorola Droid 3] ovelayer:
I thought i did redownload it after you upped the second version of 1.08f but yessir redownloading now and ill give her a shot...:D

Edit:

That worked bro...back up and running...thanks for helpin!
[Motorola Droid 3] TBBle:
What's your process for building an APK? The only things I've seen around are the droid3_recovery repo which has big warnings about not using it, and also seems to not have enough of a build infrastructure to actually produce an APK anyway.

I'm still looking for a 16GB microSD card so I can integrate my ext3-skipping patch into an APK for the (few) ME863 users, and start trying to patch safestrap to run a complete safe system on the SD card rather than having to archive data away every time you swap.
[Motorola Droid 3] ovelayer:
Now that would be a very badass idea.:)
[Motorola Droid 3] Rick#2:
That would be a pretty cool idea to try out!

TBBIe, I just used the latest .APK Hashcode put out and decompiled the .APK with baksmali, and replaced the "install-files.zip" in the assets/ directory with one of my own containing the new recovery.zip and 2nd-init.zip as well as my customized recovery-install.sh. Then I rebuilt and signed the .APK with the standard tools from the Android SDK. I can give you more details if you'd like, let me know!
[Motorola Droid 3] TBBle:
Ah, fair 'nuff. I suspected something like that. I was hoping for something I could do with 'make'. I might go ask Hashcode if _he_ automates.

By-the-by, did you notice that Hashcode's recovery repo imported a version of your console work for 1.09? Have you considered rebasing?

I'm going to have to reteach myself "repo", I've forgotten everything I once knew (which wasn't a lot) about the Android build-system. I just unintentionally rebased my patch to Safestrap v1.09. ^_^
[Motorola Droid 3] Rick#2:
I've got it pretty much automated, if you'd like I could put up the scripts I made. Basically, each time I want to test out a new build all I do is

$:~/android/{clean recovery/updater intermediate files script}
$:~/android/mmm bootable/recovery
$:~/android/{update recovery.zip & 2nd-init.zip files script}
$:~/android/{compile & sign APK script}
[Motorola Droid 3] chevycam94:
By the way, I still cant get the SD card to mount. I try to flash something, and it keeps saying that it cant mount the SD card. Everything else seems to work ok now though, that I have tested so far. Of course, with the 7000 itterations of v1.08F, Im not sure I even have the current one! lol
[Motorola Droid 3] Rick#2:
Can you try to do a clean install of it and see if it still happens? I did fix that issue but I want to make sure it's working for everyone and not just a few people.
[Motorola Droid 3] pmafdahl:
I also can't get sd card to mount with version f. Works fine with version e. Will wipe everything tonight and try again with fresh downloads. BTW I did make the plunge and upgraded my system to 906.
[Motorola Droid 3] chevycam94:
Im trying right now. Also, you might want to include in the installer what version it is. just says 1.08. Not 1.08e, or 1.08f or anything. Just thinking outloud.

---------- Post added at 03:55 PM ---------- Previous post was at 03:51 PM ----------

Hate to say it Rick, but your current build of 1.08f in the OP (2 minutes ago) still wont mount my SD card so I can flash anything.....
[Motorola Droid 3] Chrissell:
Also can't mount SD card

Using what I assume is 1.08f, installed and removed twice, can't get SD card to mount. Going to remove and go back to e in an attempt to use. Thanks anyway.
[Motorola Droid 3] rbgCODE:
I dont know what is wrong with me, I must be in special mode today but I cant for the life of me get it to boot up into this mode, only the stock useless motorola boot I get. I installed this, opened it up, pressed Install Recover, gave it su permissions, it prepared the installation, then went back to the screen, and I rebooted the phone and nothing, it boots up fine to the OS, if I reboot recovery it just goes to the stick boot screen where I can clear my cache and do nothing else.

Why am I so not with it today :?
[Motorola Droid 3] ovelayer:
Well sd mounts and works for me on 1.08f.-verizon-us-xt862

Running stock rooted motoblur (unsafe system) aokp ics (safe system)

All is actually perfect

Reboot to recovery does not work with safestrap...

When you reboot your phone you need to press the menu button when the safescreen apears
[Motorola Droid 3] rbgCODE:
Actually my problem was the root method I used, it did not install busybox, and you need busybox installed for this application to work. If other people are having problems please keep this in mind.. You need busybox installed for this application to work!
[Motorola Droid 3] Rick#2:
Safestrap has busybox included (I think Hashcode has had it included at least since v1.06).

Also, chevycam94 (or anyone else still having issues with their external sdcard) could you do me a favor: go into the recovery console and post here what the contents of your /dev/block directory are? ie:

ls -a -l /dev/block

It wouldn't hurt to get the output of that directory listing from within Android either but for now, a listing directly from the recovery is fine. I think some devices (mine included) label the external sdcard as /dev/block/mmcblk0 and some as /dev/block/mmcblk0p1, which would explain the issues.
[Motorola Droid 3] rbgCODE:
boot -> /dev/block/mmcblk1p15

cache -> /dev/block/mmcblk1p22

cdrom -> /dev/block/mmcblk1p17

cid -> /dev/block/mmcblk1p19

emstorage -> /dev/block/mmcblk1p25

kpanic /dev/block/mmcblk1p20

misc -> /dev/block/mmcblk1p18

pds -> /dev/block/mmcblk1p7

recovery -> /dev/block/mmcblk1p16

system -> /dev/block/mmcblk1p23

systemorig -> /dev/block/mmcblk1p21

userdata -> /dev/block/mmcblk1p24
[Motorola Droid 3] Rick#2:
Thanks, could you let me know what it says for your external sdcard? It should either say /dev/block/mmcblk0 or /dev/block/mmcblk0p1.

I think the device's location on /dev has something to do with whether or not you have ever encrypted data before on your card or something along those lines. In any case, it's pretty easy to try out my hunch.

While you're in Safestrap, either go into the console or "adb shell" into your phone. (Remember that for adb to work properly in the recovery your phone has to boot up with the USB cable already connected).

If you type:

ls -l /dev/block | grep mmcblk0

what output does it provide? For me, it spits out "mmcblk0" but I'm pretty sure that for those that aren't able to mount their external sdcards it will say mmcblk0p1. In which case, the fix is easy; I'll be sure to update my package, obviously, but for those of you who want to try a little DIY, copy the file /systemorig/etc/safestrap/recovery.zip onto your computer and unzip it. Inside, there's be a file called /etc/recovery.fstab; edit this and change the line corresponding to /sdcard (It ought to be on line 3, or the second line of actual text) to the following:

/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0

Doesn't really matter how many spaces you have between; ideally you'll just need to hit tab each time.

Hopefully this is what the issue was. I remembered changing that line because I was getting random error messages about my external /sdcard and since I didn't see /dev/block/mmcblk0p1 in my /dev/block directory I assumed I must have made a typo and changed it... here's one tiny example of how easy it is to completely bork these things. Multiply it by a million and you have kernel development... :eek:
[Motorola Droid 3] ovelayer:
here's one tiny example of how easy it is to completely bork these things. Multiply it by a million and you have kernel development...:eek:

Ooooohhh that quote is so now mine lol
[Motorola Droid 3] rbgCODE:
I have never encrypted my card or any of my data and when I type that command this is what I get for a response...

brw------- 1 root root 179. 0 Apr 22 07:03 mmcblk0
brw-rw---- 1 root mot_tcmd 179. 1 Apr 22 07:03 mmcblk0p1

How else can I help to trouble shoot this because if I goto recovery mode, then try to do a backup to the external SD card I am getting the error: can't mount backup path.

Also are you the developer of this bootloader? If so PM me.

---------- Post added at 03:09 AM ---------- Previous post was at 03:07 AM ----------

Another option, if you would like to get access to a phone with the issue, would be you can remote into one of my computers or use say like team viewer and I will set the phone up for you to poke around in...
[Motorola Droid 3] TBBle:
mmcblk0 is the raw device. mmcblk0p1 is partition 1 of that device. So it depends on how you formatted the SD card as to whether it has a partition table (like a hard disk) or is using the whole device as a filesystem (like a floppy disk)
[Motorola Droid 3] Willis111:
Busybox is installed unless you manually removed the binary or something you flashed removed them (or perhaps just moved them to an incorrect path which would make them seem to not be installed), you can't safestrap without rooting and its installed then. You could try just rerunning a root tool like zerg and watch the command window just to make sure it doesn't throw an error when pushing busybox etc or download it off market (think you need root).

Rick#2 does safestrap still include the option to enter via power + m boot > bp tools? Hashcode mentioned he wanted to remove that some time ago but didn't get around to it. I mentioned to him that the splashscreen could be removed from safestrap (a users wife was having an issue w/the splash just because of the possibility of accidental keypress entry which I can understand if her phone is rebooting in her pocket like mine does randomly, I said the simple fix of removing the splash, hashcode said he removed the bp tools recovery entery but it was still there when I tested, he mentioned he would be removing it in an upcoming version but I don't think he's released a new safestrap but then again I'm having trouble w/bp tools > bootloader but it might just be me pissing around w/the recovery a bit) or at least be given an option to turn off which would speed the boot by those ~10 seconds as well as give the phone a perfectly stock appearance all through boot which I've seen a few users ask about. Don't think hashcode really got around to looking at it and wonder if he's been doing much on the d3 at all lately, hopefully working on a new ics build with his kindle kernel and kexec, but probably busy in general with all the projects he has on the go lol. Would it be possible for you to add this option or release a version w/out the splash altogether? Tia for possibly looking into this.

Another cool thing would be to replace the bootsplash with something that shows when safestrap is installed and/or powered by hashcode/xda if anyones keen on graphics/animation. I could rough one out for concept but you wouldn't want to use it until someone with skills polished up the graphics lol, I'm not an artist. The idea would be just to honor Hashcode obvious wish of at least showing the safestrap is installed (easy for end users to mod though) or giving him some credt/both.
[Motorola Droid 3] ovelayer:
And this version should be 2.0 safestap on steriods!

Those are some killer ideas never thought about the splashscreen but it would be nicer

And credits should be created by hash modded by rick#2 both deserve hella credit
[Motorola Droid 3] Rick#2:
Yes, Safestrap still boots the phone into the CWM-based recovery if bp-tools is chosen from the Motorola boot menu.

This could easily be done by making a custom boot logo, ie: the Motorola Dual Core image that shows up during the first few seconds the phone is on. I've made a few already but I'm in the same boat as you in terms of artistic merit. It involves making a "logo.bin" that is flashable with fastboot; I used a guide for the Atrix somebody posted a few months ago on here but I think I saw someone had made a guide that was tailored more to the Droid 3, if I remember correctly the process was slightly different (slightly different image resolution and patching process) but wasn't difficult.

EDIT: Found a guide on the rootzwiki.com forums:

http://rootzwiki.com/topic/21470-custom-boot-logos-droid-3-droid-bionic-droid-razr-droid-4

kudos to mhous33.

I've actually been using my phone without the splashscreen for months, haha. I didn't know if people were attached to it or not but it's certainly no problem at all. That's kind of what I was going towards with the booting straight into recovery changes that I reverted in this last release, it was working solidly for me but others were having issues. I'm sure it was just something minor that I overlooked like this last fiasco with the external sdcards and am sure I'll have it working for everyone pretty soon.

The only issue with booting straight into recovery is if the end-user wants to do it from a stock system that doesn't have a Reboot Menu in the Power Options dialog; it can, however, be easily done (and I'm in fact doing it right now) through a terminal emulator that issues the necessary commands to trigger booting directly into the recovery upon booting up. Otherwise, I've already got everything in place to roll this one out.
[Motorola Droid 3] Rick#2:
That makes sense, thanks! I thought it might have had something to do with the "ecryptfs" type that shows up in /proc/mounts but your explanation makes more sense.
[Motorola Droid 3] ovelayer:
Could you maybe add a boot to recovery option in the actual safestrap app right under install/uninstall recovery for the ones that run it on their stock systems without the option in the power options?
[Motorola Droid 3] rbgCODE:
Has the mounting of the SD card issue been resolved in a new version already? If anyone needs help with graphics let me know, I can help out.
[Motorola Droid 3] ovelayer:
One thing Ihave noticed and Idont know if anyone else has but when Iam in either safe or non-safe mode when Iinstall a zip sometimes Ihave to install the zip a second time as it does not install properly the first time..not a big hassle just thought Iwould toss that out there so your aware bro

I do believe so
[Motorola Droid 3] Willis111:
I was actually thinking something that would boot straight into the system unless bp-tools was specifically selected. I do get random reboots from time to time and recovery drains my battery pretty quick so I don't think booting straight into recovery is a good idea, if I had my phone 1/2 dead in my pack it would be a brick until I got home vs if it rebooted normally. The idea of removing the splash was just for non-techies or just for a pure stock look( would be good if you went to your cell provider for some troubleshooting and they rebooted your phone etc ).
[Motorola Droid 3] nemiroG1:
One thing I have noticed (I am on 1.08e) is that when I switch from SAFE to NON-SAFE, or vice-versa, the restore it does is not complete. I will have incorrect ring tones, missing email accounts, etc. I have to go and do a wipe, then a Nandroid restore, and then it works right.
[Motorola Droid 3] Willis111:
I think you can use the app to uninstall the recovery and then just remove/update to 1.08f
[Motorola Droid 3] Rick#2:
Sorry for the lack of updates guys, been extremely busy with exams and recently landed a new job. Fortunately for me, the job will permit more time for Android tinkering and I'll get a break from full-time studies for awhile! (Not to mention I'll be moving away from my wife and kids for 8 months, freeing up my after-work hours to **** around with little projects like these).

Now I'll only be limited to the number of hours of sleep I need... hehe.
[Motorola Droid 3] ovelayer:
Well that's good and sad news leaving the wife and kids for 8 month..but woohoo for us lol..
[Motorola Droid 3] Willis111:
strange, didnt notice it until you pointed it out but I've had it happen a few timesw/formats etc. Maybe it has trouble mounting the first time or something and just isn't throwing an error so reports success.
[Motorola Droid 3] ovelayer:
That's what im thinking..still worth the trouble (not like it really is trouble) to flash twice cause this modded safestrap is the sizzle and like a crackhead I can't give it up lol...:)
[Motorola Droid 3] ovelayer:
Bump...

doesn't belong on 2nd page...:D
[Motorola Droid 3] rbgCODE:
has there been a new release that properly mounts the sd card for backups?
[Motorola Droid 3] chevycam94:
I dont think so. I have been checking back about every day now, and still nothing. I was hoping for an update. That animated Android background slows everything so much I cant stand it. lol Plus he puts a LOT of work into this. Its what I use all the time now. :-D
[Motorola Droid 3] ovelayer:
He normally comes around on the weekends...woohoo its the weekend!

And I agree chevy, sence its launch this has been the only one I use!:cool:
[Motorola Droid 3] chevycam94:
Im curious if hes still working on this. Its been quite a while. Maybe its harder than it sounds.
[Motorola Droid 3] Endoroid:
He probably has other things in his life and only has time here and there to work on it. I think sometimes as end users we forget that these devs don't do this full time and have jobs and lives and such.
[Motorola Droid 3] chevycam94:
No doubt. Its takes me forever to develop my ROM. I understand. :-D
[Motorola Droid 3] yus4eel:
Whenever i enable Safe system the phone doesnt boot it just leaves a blank screen after the spalsh screen that says whether safe syetm is enabled or disabled

help? Its annoying to flash roms in non-safe system
[Motorola Droid 3] VincentDHam:
after you enable safe system, wipe data, cache, davlik cache, and system

then flash your rom.

Did you do that? just switching to safe system from non safe isnt going to work without flashing a rom in your safe system.
[Motorola Droid 3] ovelayer:
Yessir..sounds like he didnt flash a rom to safe..:D
[Motorola Droid 3] VincentDHam:
lol.
[Motorola Droid 3] Endoroid:
Its a common mistake I've noticed
[Motorola Droid 3] ovelayer:
Calling canadian bacon ham? Lol...:p
[Motorola Droid 3] LaZiODROID:
Having a little trouble installing this. I previously installed safestrap (older versions) after flashing a fresh Mexican or Brazilian sbf.

Today, I flashed Bell 2.3.6 sbf (umts_solana_bell-user-2.3.6 5.5.1-112_SLU-47.6M-111109-release-keysMDM6600BPLA_U_03.3B.01P.xml.zip), and rooted it. I installed this safestrap, launched it, allowed it root access, hit "Install Recovery" and it went through the process and indicated that it was successful. The Recovery State line didn't update (it still says "Not installed") so I assumed it didn't work out. I restarted the phone to look for the usual safestrap splashscreen (just in case), but nothing. It just booted normally.

Any help would be appreciated! I gots to have my Liberty ROM back and safestrap is wicked
[Motorola Droid 3] Endoroid:
Check to make sure you have busybox. Happened to me before
[Motorola Droid 3] ovelayer:
Hmm safestrap has busybox built in but wouldn't hurt to make sure its current...

Maybe just try to re-install

And

Liberty? Lol ever try mav 4.0?

Its pretty slick..:cool:
[Motorola Droid 3] LaZiODROID:
F****** amazing, thanks endo/ove!

I installed busybox from the market and safestrap installed just fine.

Time to play

p.s. yes Mav was slick! But I had some issue with it .. which I can't remember right now... Liberty has been the best for me (not the fastest, but the most stable). Before I did this SBF I was using the V6 Supercharger script and it helped Liberty become a little more responsive (or maybe I was tricking myself... hah)
[Motorola Droid 3] ovelayer:
Yeah the supercharger script really helps liberty and a few more tweeks and she runs decent..

I just prefer mav because it uses the current system files from verizon updates and the support from the mav crew is incredible..

Glad you got it all sorted out and running good...:D:D:D
[Motorola Droid 3] ovelayer:
Wow 2wks and no word...think we got ditched lol...:confused:
[Motorola Droid 3] nemiroG1:
People get busy....
[Motorola Droid 3] Endoroid:
Rick often seems to go long time with no word. Don't stress it
[Motorola Droid 3] ovelayer:
Really?...:p
[Motorola Droid 3] LaZiODROID:
I was having the "cannot mount /sdcard" error when trying to install a zip (to safe zone of course). I can use internal sdcard, so not a huge deal for me. I tried the suggestion mentioned earlier (editing the fstab in the recovery.zip) which allowed me to browse my external sd, but when selecting the zip, it just returned me to the menu.

Sent from my XT860
[Motorola Droid 3] AragornPE:
Hey, sorry if I'm asking it again, couldn't read the whole thread (I'm on a bus and 3G isn't helping much) but something came to my mind while toggling between safe/non-safe. I tried the quick toggle, and that didn't go so well, but have you thought about creating a quick toggle for /data as well?

As I see, currently quick toggle just changes a file and that file says to the phone which partition to boot, /system or /systemorig, while toggle makes the change in said file, backup non-safe/safe /data and flashes safe/non-safe /data (not in sequence) , and that takes ages AND consumes a lot of space in /sdcard or /sdcard-ext. What if we had /data and /dataorig, in the same way as /system and /systemorig, and all we needed to do was quick toggle every time we wanted to change the ROM we want to boot? I know we can have some problems with space, but can't you mount /data inside /sdcard and "redirect" any requests for /dataorig for this folder? It would be great! I remember from the M2 forum a script that mounted a portion of the internal storage (8gb just for apps? Wtf Moto) and we had sweet extra 4gb to use, so it's feasible, at least when the system has booted. I don't know if it can be made before boot, but if it works it will be great!

Also, bump =D

Rocking with my M3 and XDA app
[Motorola Droid 3] ovelayer:
Oooooohhhhhh. Ricky....:p