yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 3] ovelayer:
I figured that out after installing and trying..FRIGGIN AWSOME!!!

Many many props to you! I actually like the different colors for the different boot systems :)

I bet this becomes the only one used now lol great job.

I did notice one thing..you moved the install .zip options to the advanced menu which i love! But it also has the install .zip option on the main screen. Anyway to remove it from the main screen and just have it under advanced?

Could this by chance be ported for the d2? I'd love to get this on the wife's phone
[Motorola Droid 3] fl4r3:
Just tried version 1.08d and had some major trouble...the phone would constantly boot to recovery only. Even from a battery pull and holding 'm' to choose normal boot. Additionally, backup/restore would not work and got error 255 when trying to install zips.

I thought it was because I didn't uninstall 1.08c. So I SBF'd back to stock and rooted/reinstalled safestrap 1.08d. But once again had some problems...tried to restore a non-safe backup but it said can't mount /systemorig. Then when I rebooted it just hanged at the logo.

SBF'd again, applied 1.08c and everything seems fine. Don't know whats wrong with 1.08d :confused: but it gave me a scare (couldn't see any /sdcard data in the console!!!! eventhough external was showing).
[Motorola Droid 3] thingonaspring:
@rick

Massive props for the non-safe flash capability, can't believe how quickly you did it.
[Motorola Droid 3] redsox985:
I also had a can't mount /systemorig issue and I think I was BL'ing. IIRC, I tried changing the Liberty3 framework-res.apk since it's from the Bionic and not the D3, but that failed. So, I think I reflashed Liberty3 (Thank you for adding non-safe flashing! Saved my ass here.) then was able to restore my nandroid. It didn't like that /system didn't match exactly I guess.
[Motorola Droid 3] fl4r3:
I should of tried that! Oh well, can't be bothered trying again (well yet lol)....although I was getting error 255 everytime I tried flashing a zip.

I'll stick with 1.08c for now.

I do still have one problem tho...In 1.08d the console worked perfectly (albeit with other problems)...but in 1.08c it closes immediately. Any ideas why?
[Motorola Droid 3] jellydroid13:
kind of useless request but by any chance could you change the safe color to blue instead of green :D

---------- Post added at 11:41 AM ---------- Previous post was at 11:31 AM ----------

and by any chance could you make an option to wipe systemorig?
[Motorola Droid 3] Willis111:
I can't get this to install a rom to my /system (non-safe), every time I try it looks like everything goes fine, I check the log and all it has is the last few lines of the liberty install but when I reboot it's still my stock motoblur. Does this have to do with the problem people are having with mounting /systemorig with this bootstrap?

Since the safestrap is installed to /systemorig probably best not. If you install a rom there it should format it for you (liberty kept trying when I was trying to install it to non-safe but ... that was fail all together) and then re-install a custom bootstrap. Couldn't you use mke2fs from the console anyways for advanced users?

Edit: Wanted to mention I tried that features change in the build.prop w/cm7 and with some combination and numerous reboots/force crashes of the phone through dev tools I saw the phone number populate correctly in phone info one time for a split second, tried to add an apn but it wouldn't save and when I rechecked the phone info the # wasn't populated again. The imei seems to be populating correctly every time but it's still causing sim errors, not reading network values like mcc/mnc, sim doesn't support a connection to this type of network (on home network) etc. As well I notice that no matter what I do with the build.prop etc in cm7 when I check w/set prop my default network mode is always 2, not sure if cm9 is doing the same but someone running a quick "getprop | grep telephony" and checking the value of ro.telephony.default_network perhaps it's reverting back to the (will have a value of 2 for gsm, 3 for wcdma/gsm, same as settings in build.prop )gsm network after a brief period on the umts which is why umts is up for a second and then back down. Just an idea, I'll check into it myself in the next day or two. Thought I'd post here because you'd be more likely to look, we should start a cm7/9 xt860/me863 thread in the next little bit if we can get anything more to actually work.

This is with the cm7 libmoto_ril.so, if I pushed the iuscell ril the phone would fc loop regardless of the features setting/build.prop edits, perhaps pushing the stock rild might help but I don't think Hashcode modified it. I think at one point (think may be when I got the phone # to populate randomly for a split second on a reboot, but no apns saved/data) I pushed the brazil retail libmoto_ril.so and didn't have the phone fc loop with this edit though it would normally, I'll have to double check.
[Motorola Droid 3] Rick#2:
Interesting that it wouldn't let some of you mount /systemorig, or install from a .zip file for that matter, too. I didn't touch any of the code dealing with the actual mounting/nandroid operations, mostly just fiddled with the menus a bit to get them to show what I want, so I'm curious as to why these problems are coming up.

When I have some more free time I'll come back to this and see what I can do; in the meantime, could anyone with any mounting or updating issues please post their logs? (You can find the current log in /tmp/recovery.log while you are inside the Safestrap recovery).
[Motorola Droid 3] Rick#2:
PS Willis: I got 3G data working on our XT860s, check out the thread I made here for a link to try it out for yourself! If only my wife could appreciate how awesome I think this is. :P

http://xdaforums.com/showthread.php?t=1465297
[Motorola Droid 3] Willis111:
Gave it a try, it's really awesome. Posted a response in your original thread but it's a little messy so if you read this it may clarify. Seems like I can get 3g up on the bell rom but phone stops working (for calls) and the sim card will show as not install 1/2 the boots. The only way this was 100% for me was with your zip/probably just need your patched files. Getting a smaller patch together and released should be 1st thing I think, that way whenever Hash releases a new build we just need to go to your thread and grab the patch (like with the safestrap data fix). Massive props man, I'm finally using ICS for more than a few minutes at a time and making it my daily driver.
[Motorola Droid 3] ovelayer:
BUMP...

Any news on an update with some of the changes???... :confused: :confused: :confused:
[Motorola Droid 3] Endoroid:
rick, here is a pastebin of recovery.log

http://pastebin.ca/2117848

this was during a restore. Ive had this happen several times tonight(screwing around with framework animations)

it happend twice, then i did an advanced restore of /system and then was able to do a full restore. Possibly coincidence and its just persistence is the key. i'm in the middle of trying to restore again so i'll let you know if i can recreate a succeful restore the same way

---------- Post added at 08:45 PM ---------- Previous post was at 08:30 PM ----------

so i can confirm a workaround for safestrap not mouning /systemorig

tried a restore, failed. It automatically goes to an advance restore, select the same nandroid image, restore /system. When it's done, do a full restore and it works. Weird

here's another recovery.log this is the same recovery session as the previous. It has 2 failed restores, /system restore then a full restore

http://pastebin.ca/2117876
[Motorola Droid 3] Rick#2:
Hey Endoroid,

I took a look into what you're seeing and I think I know what's happening. Can you describe to me exactly the scenario you were in? Ie: In Non-Safe Mode (I'm assuming so), fresh boot of Safestrap straight to Backup/Restore without doing anything else first, (eg: did you boot up the console first before trying to do your restore, did you mount any partitions like the sdcard/emmc, etc.). The more detail, the better... you know the way things go, it's always the thing you least expect that is causing the problem!

Here's a quick breakdown of what happens. Safestrap wants to format each partition before it performs the restore. Unfortunately for us, we can't do a proper format of our ext3-type /system partition; if we were to do that, we'd mess up the signature and the phone would cry bloody murder about it, as a few of the users on this board (myself included) can attest to.

To get around this, the /systemorig partition is not flagged as "ext3" in the format function's eyes but "auto", which is a condition that tells the function that takes care of how to handle the formatting procedure for each partition. If it sees "ext3" or ext2", it just goes ahead with the usual format, clean wipe. There are a few other conditions, and as a last resort, since "auto" doesn't fit the bill for any of the other choices, it does an "rm -rf /[PATH TO PARTITION]". (Recursive force delete of everything).

Then it does it again, immediately afterwards. Not sure why, just saw that now, I'm sure there's a good reason.

What happens next is that it wants to ensure that the path is unmounted, so it attempts to unmount /systemorig, and for some reason the partition is busy so it doesn't unmount, thus it causes the failure.

I'm sure it'll be something pretty easy to fix. Just need more information! I haven't seen it happen to myself yet so I'm sure it has something specific to do with whatever you're doing right before you do the restore.

Thanks for the log!
[Motorola Droid 3] Endoroid:
Ok the whole run down is: all in nonsafe mode. changed framework animations with rom toolbox, broke both status bar and toolbox. Booted into safestrap and went straight to restore. It failed twice went to boot back into rom to try to install nontweaked version and couldn't get past the boot logo. Motofastboot system.img, problem persisted, did whole fastboot package, booted up. Root, safestrap(tweaked)and booted into safestrap failed to restore twie again. I noticed that it was putting me into advance restore, so instead of backing out I chose to restore /system and then I tried a full restore again and it worked. So I went ahead and broke my **** again(I'm a slow learner:p)and when I tried to restore it failed to mount /systemorig again. So I went through the same process as before and it worked. Both times I booted into safestrap I went straight to restore
[Motorola Droid 3] redsox985:
Is doing a /system restore, then full nandroid restore a way around the /systemorig failure? I've run into this many times before and actually went to un-modded SS for this reason. One thing I did before was reflash the .zip for the ROM I wanted to restore, then it would restore as usual, but that became a burden.
[Motorola Droid 3] Endoroid:
The exact steps I took was to attempt a full restore, when it fails to mount /systemorig it seems to automatically place you in advance restore. If you look up top it says select an image, choose the same backup and chose to restore just system. When that completes I attempted the full restore and it worked. I did this twice and it worked both times so I'm saying its confirmed. Why it works…well i m not sure. Rick might have insight on that. If you try it and it works please post so we know for sure.
[Motorola Droid 3] nemiroG1:
I have an odd problem. I have an XT862, rooted/unlocked, running the XT883 radio (for T-Mobile). I have previously installed CWM, and then installed this, first clicking on 'Uninstall REcovery', then installed Safestrap 1.08d. OK. booting into recovery results in an initial boot into the stock recovery. I then select Reboot System Now, which then boots into Safestrap recovery. OK, do what I need to and reboot. The next time I boot into recovery, again, it boots into the stock recovery, I Reboot System Now, and it boots into CWM recovery!

Obviously this is not right. Any ideas?
[Motorola Droid 3] Willis111:
Its odd, all the advanced funtions/flashing that should deal with the partiton for system( /systemorig) seems to deal with the preinstall parition (/system) instead, so flashing my non-safe area actually still just flashes the safe area etc. I think its only in the advanced menu but havent checked mounts > format system or anything like that.
[Motorola Droid 3] Rick#2:
Hey Willis,

I think the reason you're only seeing changes to your safe system partition is due to the updater-scripts inside the .zip updates you are applying; if you take a look at them, they probably are targetting /system, which is (as you know) actually the /preinstall partition.

This is something I can't really change through the recovery, the update script inside the .zip needs to be modified to point to /systemorig. It's pretty easy though, search and replace /system for /systemorig and you're good to go! (I actually did this with your Optimized Bell .zip and it worked like a charm.)
[Motorola Droid 3] Rick#2:
Got a new release coming up pretty quick here to address the issue Endoroid described with /systemorig. Just want to do a bit more testing to make sure it's perfect!
[Motorola Droid 3] Endoroid:
Hey rick I have a question. If I wanted to move my /system rom to /systemorig, but preserving all the data, theming, and system mods would this work. Make a full backup of /systemorig and /system, then switch the name of those 2 .tar files and swap the md5sums to match, and then restore.
[Motorola Droid 3] ovelayer:
Shaweet! :)
[Motorola Droid 3] DoubleYouPee:
So the new version allows me to flash a ROM over my non-safe? E.g. MAVROM 3.5 right over my MAVROM 3.0?
[Motorola Droid 3] trini.s2k:
hey when you make a new release can you restart your post and give a better break down on how to use it , sorry if im being a noob , but i wen back to my non safe rom and it boot looped ...not tryin to be a pain it would be nice for people like me to have a step by step thanks
[Motorola Droid 3] mgerbasio:
I have an even more noob question, do I need to be rooted to run safestrap. I've read numerous threads but can't get any version to run on my D3 (stock, non-rooted).
[Motorola Droid 3] trini.s2k:
lol yes you have to be i feel your pain lmao
[Motorola Droid 3] mgerbasio:
Thanks. I'll load ICS tomorrow.
[Motorola Droid 3] roblav96:
whats the difference between 1.08c and the tweaked 1.08d?
[Motorola Droid 3] ovelayer:
Dont give up on us/this rick#2 still looking forward to an updated version! :D
[Motorola Droid 3] Rick#2:
New release of version 1.08e, see first post for more info.
[Motorola Droid 3] ovelayer:
Oh wow bro this update is through the roof!

Awsome awsome job! Best recovery by far..you get top dev for the month from me!:D:D
[Motorola Droid 3] Willis111:
Looks like I still can't flash non-safe with 1.08e. It looks like everything goes ok but when I boot it boots to the previously installed rom(nothing actually happens, just looks like it does?) tried cleaning up my system/rsd'd and tried installing to non-safe from a clean install but no dice, not sure what the problem is, /preinstall flashes fine. I think it has to do with the updater-script calling /system or /systemorig but shouldn't these partitions both just be mounted to /system (not at the same time ofc but depending on if you have safestrap enabled it should have either system or preinstall mounted to /system)?

Edit: I edited an updater script replacing /system instances with /systemorig but when I flash to non-safe(looked successful again) my phone wont boot, I double checked and with the edits everything should be mounted and placed correctly, I'm stumped for the moment.
[Motorola Droid 3] pmafdahl:
I tried to install Mavrom 3.5 and got the same result, it just booted up to stock rom with all dat verizon crapola. Great idea to have non safe flash but wish it worked!
[Motorola Droid 3] Rick#2:
Yeah, I have to admit my initial implementation was an afterthought, I forgot to take into account how different Safestrap is from the usual Bootstraps out there with respect to the /systemorig partition; since most updater scripts out there reference the device /dev/block/mmcblk1p21 as where to house the /system partition, Hashcode came up with a pretty good system to avoid having to manually hand-edit them in order to use /systemorig instead of /system for Safestrap as opposed to the alternatives that don't care what goes on with this partition.

Luckily, I have a tendency to be super-OCD when it comes to these little procrastination projects of mine and have spent many more hours than I should have on this; I should have a working update soon that will truly allow ROMs to get dropped wherever the end user wants, without the hassle of editing the scripts by hand. Whether or not it's a good idea, well, that's up to those of us who think we know what we're doing. :P

Also, I think I found a way to speed it up quite a bit, at least on my phone. I clocked a full safe-system backup with /systemorig at 155 seconds, which was pretty shocking since I usually leave the room for what feels like 15 minutes when I'm doing a full backup.

I'll be sure to throw it up as soon as I'm satisfied that *most* of the bugs are worked out... :eek:
[Motorola Droid 3] blkwlf:
Awesome! Looking forward to the next update. Thanks Rick!
[Motorola Droid 3] ovelayer:
Can't wait rick#2 you know I'm a huge fan lol..:D

Post count 69..nice...lol...:cool:
[Motorola Droid 3] blackbuddha:
This post might give you some idea while waiting for Rick#2's update.
[Motorola Droid 3] ovelayer:
So will the new version be f or 2.0 lol :confused:
[Motorola Droid 3] Anthrax79:
HELP!! Stuck on Moto Dual Core Logo!!!!

:mad:

I have been waiting for weeks for the soak test and finally gave up and decided to re-root and put a custom ROM down. I used the latest Pete's Root tool v 1.7. It booted fine after. I updated the super user binary, cus it was slighly out of date. I then installed this tweeked version of the safestap. Now I am stuck on the first Moto Dual Core logo at power up. I have left the phone in this state for well over 30 minutes hoping it would wake back up...

What do I do?? Do I have to reflash the old SBF and apply the stock ROM? Any hope of recovery without that extreme???
[Motorola Droid 3] Rick#2:
Try a battery pull; if half an hour has gone by it probably isn't going to boot up. In the worst case, you'd only want to try flashing your /system partition in fastboot and not do a complete fastboot restore, this way your /data partition will remain intact and you probably won't lose anything important.

Try the battery pull first and see what happens.
[Motorola Droid 3] Rick#2:
Updated the first post with details on the latest release!
[Motorola Droid 3] ovelayer:
Woohoo thanks for this bro
[Motorola Droid 3] chevycam94:
Seems there is some kind of glitch here. I dont know what happened, but in 1.08f, EVERY time the phone reboots, it goes directly into Recovery, without question, and never shows the screen that prompts me to choose Menu (enter recovery), or Search (continue booting). Anyone else catcth that? 1.08e worked perfectly, but 1.08f has the issue.
[Motorola Droid 3] VincentDHam:
Same here..
[Motorola Droid 3] chevycam94:
Im thinking that when he set up the ability to reboot into recovery from within the OS, he crossed both options (both reboot and reboot recovery) to do the same thing (reboot into the recovery). So its probably a simple fix. I dont have his source, or any more space on my drive to sync it, so Im not able to fix it myself. Plus Im not sure what all he did. lol Recoveries are not my thing, ROMs are. lol
[Motorola Droid 3] Rick#2:
Hmm, it's probably to do with my changes to /systemorig/bin/logwrapper. Try manually deleting /data/.recovery_mode, that's the trigger file that tells it to boot straight into the recovery.

Sorry about that guys, I'll fix it right away.
[Motorola Droid 3] Aaron1017:
version f isnt mounting my SD card either.
[Motorola Droid 3] blackbuddha:
Could you please update it once it's done? Thanks.
[Motorola Droid 3] chevycam94:
Thanks Rick. I use your version exclusively on my D3 because its so much easier to use, and has so many features extra. I was actually going to suggest removing the animated Droid background to speed things up, but it looks like you got to that before I said anything. Nice work as always!

On a side note, Im not seeing /data/.recovery_mode
[Motorola Droid 3] ovelayer:
He might have ment recovery-from-boot.p and that is in /system

but you may need root explorer or something that lets you see hidden files

Awsome work rick lovin it;)
[Motorola Droid 3] Rick#2:
Hey guys, I just removed the rebooting directly to recovery entirely from both /systemorig/bin/logwrapper and from the recovery menu to avoid confusion until I sort out why that's happening to you guys. I can't seem to replicate the error myself so there must be something else I haven't thought of on my phone that is allowing it work that isn't present on everyone else's... I'll try a fastboot restore and install it from there later on when I have some more time.

Also, I took a look into the mounting USB and it's working for me now after a minor change, try that and see. The link in the first post will still point to the newest revision now.

Sorry guys, I put a lot of time into this release trying to make it perfect for everyone and I guess it's not my day today!!! :)
[Motorola Droid 3] Rick#2:
PS: Make sure you guys uninstall your old Safestrap within the application and then again through the Settings->Manage Applications menu within the Android OS before you install 1.08f, I'm pretty sure I took care of this with my install scripts but just to be on the safe side.
[Motorola Droid 3] Rick#2:
Thanks!

I did mean /data/.recovery_mode though, here's what happens when a request to reboot directly to recovery is made:

1) Either the shell command "reboot recovery" is executed, or the function reboot_wrapper( "recovery" ) is called from within the recovery. The reboot command parses the argument "recovery" and from there, it is told to mount /data if it isn't already mounted, create the empty file ".recovery_mode", and then bypass the stock recovery and perform a normal reboot. (Traditionally, the command "reboot recovery" would boot you into the stock, ie: useless, recovery).

2) When your phone is in the init process, the script that replaces the original logwrapper binary checks for the presence of /data/.recovery_mode and if it's present, then it skips the Safestrap bootmenu screen; otherwise it will pop up the bootmenu screen and allow you to choose whether to go into the recovery or continue booting your safe/non-safe system.

3) If /data/.recovery_mode was found by the hijacked logwrapper, then it is deleted by the script before it boots up the recovery so that a continuous loop into the recovery is avoided. For some reason, a few of you are having issues at this stage. There isn't any other way for it to boot straight into the recovery without presenting the bootmenu without that file being present, or at least not any way that I can think of.

(Interesting exercise for those of you who are interested, just open up /systemorig/bin/logwrapper in a text editor and follow the script, it's actually pretty simple and a pretty elegant way to take over the init process... kudos to Hashcode once again!)

Anyways, for now I've just scrapped rebooting directly to the recovery fro within the recovery, which isn't that useful anyways besides to restart the adb daemon, which for some reason I can't figure out won't allow you to unplug and plug a USB cord back into it and adb in after it's already booted; you can only adb in if the cord was attached at boot.

If anyone wants to help me figure out why it's looping, let me know and I'd be happy to step through it.
[Motorola Droid 3] Rick#2:
I've just tested out a completely clean install of the revised version obtainable from the link in the first post on a freshly fastbooted XT860 (shouldn't make any difference compared to the XT862 as the filesystem is identical in terms of the recovery) and it's working as expected now.

Is anyone else experiencing the reboot issue or unable to mount their USB storage?