yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 3] DoubleYouPee:
Hey hashcode (or anyone else who knows).

I'm probably soon gonna install the new version of maverick. Since I'm flashing I thought it might be a good idea to install the 5.7.xxx OTA as well for new baseband and kernel (which aren't flashed with maverick).

Is this worth it and what should I do?

Should I turn off safe-system, then install the OTA update, turn on safe-system, and flash maverick?

Thanks
[Motorola Droid 3] Hashcode:
The OTA is installed in Motorola recovery (power + vol down). BUT, be sure to go back to your non safe system first.

Install a Root Keeper, or you will lose root and as far as I know the only way to get it back is to fastboot back to 5.6.890 and re-root.

Then once you have the OTA installed, swap back to Safe System and flash the ROM. And for CM7 use the additional patch to be 5.7.894 compatible.
[Motorola Droid 3] Hashcode:
If you try the upgrade again, grab alogcat from the market and let me know if you see anything suspicious in it (like repeating on/off commands, etc.) I can say that in general, I haven't seen this to be a wide spread problem, so it should be fixable.
[Motorola Droid 3] DoubleYouPee:
Thanks. I don't think I'll need rootkeeper because maverick has built-in permanent root.

After flashing OTA, I can just reboot into safestrap even without root, right?
[Motorola Droid 3] buckmarble:
You have to be in stock recovery to flash OTA and rootkeeper has to be in the stock system/stock rom with safestrap disabled and uninstalled.
[Motorola Droid 3] DoubleYouPee:
But why would I need root if I can just reboot into safestrap after OTA update?

Does maverick require 'normal root' to achieve permanent root??
[Motorola Droid 3] buckmarble:
When you flashed mavrom with safestrap, it flashed it to the preinstall partition. The OTA flashes to the system partition where stock blur is. So maverick will have nothing to do with the OTA. The safestrap installed interferes with the OTA and it wont install properly(pedwards tried to install the ota with safestrap installed and discovered this) so it needs to be uninstalled first.
[Motorola Droid 3] beard0:
Thanks when I get a chance I will lol this time of the year is a little busy and I'm wiped out so I'm just gunna sleep soon so maybe in the morning before work ill get a chance

/Droid3
[Motorola Droid 3] Phibernaut:
The reboot option in the Safestrap 1.06 recovery menu turns off my D3 and it requires a battery pull to be brought back to life. I've been able to reproduce it a few times - only immediately after flashing a new ROM. Reboots after flashing gapps, themes, etc are not affected and the new ROM seems happy otherwise. The M logo appears immediately upon replacing the battery - I do not need to press the power button to start the phone. Not sure what's causing it but it doesn't seem to be more than an inconvenience.
[Motorola Droid 3] ChaoticWeaponry:
The motorola logo appearing instantly after a battery pull is caused by residual charge in the phone.. leave the battery out for 10 seconds, it shouldn't happen anymore.
[Motorola Droid 3] mvp3:
I tried to use fdisk to readjust the partition,

umount cache

delete cache and preinstall then readjust them,

but I fail,my skill at linux is not good.

for your reference

if you don't have xt860 rom,don't try this.

if your phone is xt883 or me863,you can flash their rom to recovery.
[Motorola Droid 3] mvp3:
Hashcode

I tried to restore my system,but get an error.
[Motorola Droid 3] Hashcode:
Oh wow.. yeah that message doesn't look good. It's odd that those files would be locked in recovery. Hrm.

The command it's trying to do there is "rm -r *" so that the .tar file can be restored. Can't format the /systemorig partition w/o breaking the signature.

Was that the first time you've ever restored your /systemorig?
[Motorola Droid 3] mvp3:
Yes,that is my first time,tragedy.

I flash from xt883 to Verizon.so something is change?

edit:

false alarm.

when i'm desperate,I tried to toggle safe system,then restore system,verything is back,Thank God
[Motorola Droid 3] Hashcode:
Everything should work perfectly under the Verizon ROM, as I use it every day.

I don't have "su_backup" on my phone tho. Is that a Root Keeper? I wonder if it has special permissions which are causing this.
[Motorola Droid 3] mvp3:
I tried to toggle safe system,then restore system,verything is back.

1、quick toggle enable safe system

2、restore system

3、quick toggle disable safe system

yes,I installed OTA rootkeeper

su-backup permission is rwsr-sr-x
[Motorola Droid 3] Phibernaut:
The immediate appearance of the M logo and startup without using the power button isn't that big of a deal. I'm more concerned about the failed reboots and lock up forcing the battery pull.
[Motorola Droid 3] eww245:
Hashcode there is a thread in General about this actually. Yes it is from rootkeeper and chattr -i needs to be run on the file first. Not sure if thats something you'd want to check for but for anyone else it is a solution. xdaforums.com/showthread.php?p=19624767#post19624767
[Motorola Droid 3] TBBle:
Oh, fdisk! That never even occurred to me. Too much time with devices with partition tables in their firmware. >_<

You were doing that in recovery, right? 'cause otherwise you'd have to reboot to reread the partition table, and on rebooting it'd try and open the cache partition which you hadn't yet formatted.

If and when I can get a dd backup of my device put aside (i.e. working adb shell in a recovery, I guess) I might play with that myself. Approx. 128MB cache partition would leave enough room for a /preinstall the same size as /system.

Otherwise it's shrink _and_ move userdata. Yuck.

That's ME863_SOLANAUMTS_SLNCU-60.1.101_Fastboot-CFC-service.xml.zip right? There's no 60.1.103 around that I've seen, and no one's mentioned anything about being able to get that as an update after flashing 60.1.101.
[Motorola Droid 3] eww245:
I really like this idea theres no point to have that large of a cache partition, mine barely has 16mb, this also could allow us Droid 3 users to have a second data partition for dual booting, very interesting.
[Motorola Droid 3] mvp3:
I use adb shell to use fdisk command.

Reorder partition

format to ext3

but I see block of cache partition in /proc/partition is not changed.

May be it will push an OTA to your phone.
[Motorola Droid 3] TBBle:
Unless you've done something interesting, a small cache partition will badly confuse Android Market when downloading a large APK. I recently had to split a 25MB app into 6MB content packs because too many devices were failing to install it with the new Android Market, because either /cache was too small, or it was big enough but the eight step (or so) "clear cache" instructions from Google aren't sufficient to actually clear the cache.

Did you restart? Linux can't reread an MBR partition table from a device with blocks mounted. And I suppose we don't know if that table is being replaced on boot anyway, since I have no idea how the bootloader works. (My last phone was a HTC Dream, so this whole locked bootloader thing is new to me)

Maybe. I'm afraid to risk it. Although I did just take a dd backup of my device, so now I'll consider having a risky play.

Right before I leave the country. >_<

Edit: Okay, got Safestrap's nandroid working on my Milestone 3 by skipping the ext3 partition. Patch and recovery binary are attached.

To use the recovery binary, you'll have to replace the existing recovery binary in /etc/safestrap/2nd-init.zip after installing the bootstrap. There's also a recovery binary in /etc/safestrap/recovery.zip (in the sbin folder) but I don't know what that's used for.

I'm also uploading the custom manifest.xml I used to get Hashcode's Cyanogen branch checked out with repo, in case anyone else wants to play with the code. I'm further surprised that I can attach a .txt file but not a .xml file.
[Motorola Droid 3] mvp3:
restarting will brick. :(

yes,no OTA

Congrat,:)

I have just flashed verizon rom,

xt883 me863 xt860 can try this.
[Motorola Droid 3] tacosrdelicioso:
The only thing I miss is that the OK button doesn't select in the menus like 1.05 and below did...and all the other recoveries. This is seriously a wonderful way of doing things...thank you.
[Motorola Droid 3] Cdjones187:
[11/20] Fixed 2nd processor performance issue

[11/20] New ICS "install" graphic is now animated

[11/20] Fixed image error message on boot

If any of those fixes/features added seem like it would be worth it to you. Then yes =]

I don't even use the safe system. I just like the fact I can choose to boot into recovery without actually opening a app or having to go into bp tools. Works just the same as koush's bootstrap if you dont use the safe system. I dont see how all these people are having issues, the directions are straight forward so I would think its user error or an issue with the current system your running.

Guidot was kind enough to help out over at df.net and posted a how-to. Check it out, I think it explains in more laymans terms. [HOW-TO] Use Safestrap (backup and flash) (WIP)

I highly suggest that ANYONE having these issues after following the how-to step by step needs to start completely over on a stock system so it is completely clear of any bootstrap, including the safe strap.

You don't even have to use the keyboard anymore. The touch keys are the controls, menu is up, home is down, back is back, and search is 'ok or enter'
[Motorola Droid 3] TBBle:
More evidence for that theory, my HK ME863 Milestone 3 has "@dun.vzw3g.com" and "@vzw3g.com" as its NAI values in its radio's non-volatile memory.
[Motorola Droid 3] DroidXY:
When i enable safe system it wont boot anymore? I'm on 5.7.894..
[Motorola Droid 3] kshen1:
did you install a ROM onto safe system?
[Motorola Droid 3] slow88lx:
Coming from a clean install, I cannot get into koush's recovery, it just boots on through. So then I installed safestrap and when I try to get into it I get bootlooping. I had similar problems before which required making room on system, I have already moved all the ringtones to my SD card. Still no luck.

Any ideas before I go for another clean install and try safestrap first this time?
[Motorola Droid 3] Hashcode:
Make sure you when you're in your primary system, that you only have 2 logwrapper files:

logwrapper ~6k

logwrapper.bin ~9k

If you have a 3rd file something like:

logwrapper.orig

Then you probably have 3 hijacks installed

or if 1 of those logwrapper's is a symlink back to hijack then something didn't work right on the installation of Safestrap (it should have cleared out any Droid3Bootstrap hijacks)
[Motorola Droid 3] slow88lx:
Yeah I only see the 2 logwrapper files. Any ideas on what my next step is?
[Motorola Droid 3] Hashcode:
What OTA are you on?
[Motorola Droid 3] slow88lx:
5.6.890. I might just start fresh with a fastboot tonight, but was hoping I'd could get past this to make a backup and jump on Liberty.
[Motorola Droid 3] Wolfhere:
Removing Koush's CWM 5.0.2.6

I am all about using Safestrap, but find myself unable to remove the CWM from my phone (I flashed the Clockworkmod Recovery from within Rom Manager). I have a recent TB backup of apps and data and even a fairly recent backup from the tweaked bootstrap.

So my guess is, I will have to sbf the phone (5.6.890). Unless someone has a better idea, like a recovery image I can flash. I am anticipating the worst and having to rebuild my apps and data again.

I want ICS. According to Rom Manager, my ROM will not do OTA's. I thought it was the stock blur - 5.6.890. I had bricked my phone sometime in the past and PSouza's 'rescue' saved my butt...er phone.

I am open to suggestions. Thanks in advance.

The One and Only Wolfhere

PS. Never mind. I sbf'd. I can recover from TB. Sigh. I should just have waited. ;)
[Motorola Droid 3] Willis111:
You could have used moto-fastboot to flash just the recovery image from the extract sbf I think. As long as what you're flashing is siged with motos tool.
[Motorola Droid 3] Phibernaut:
Its a shame there's no built in "Update" command to pull down the latest changes for CM7 or ICS like a rolling Linux distro. Safestrap could always restore a recent backup if something choked.

I'm not sure how crazy/impossible a thought this is - just putting it out there.
[Motorola Droid 3] Hashcode:
Safestrap 1.07 is available on the blog:

http://hash-of-codes.blogspot.com/p/android-downloads.html

Changes:

[12/14] Added "search" button binding on splashscreen to skip and continue booting

[12/14] Added "Disable Safestrap" item in the "Advanced" menu for those users who end up in a Recovery Loop (where no matter what they do they always enter recovery).

[12/14] Updated hijack for better ICS binary loading

Make sure you update BOTH Safestrap.apk's if you have it installed on both ROMs. (This eliminates any "Old version" warnings.)

I like this idea, but my time is fairly limited atm w/ the D3 devving. Maybe as things slow down, I'll take a look at some neat additions.
[Motorola Droid 3] DoubleYouPee:
I only updated the one on my safesystem (I used safestrap on my stock ROM, how else would someone install the 2nd?) but after installing the old version message was removed anyway.
[Motorola Droid 3] jjhiza:
Just to be safe (and I think this was what Hash was saying), I updated Safestrap on my 2nd (safe) system first, then I booted back to my non-safe and updated the app there as well. As per Hash's suggestion, I made backups of internal and external SD on my non-safe, toggled safe system back on, and booted back to my second system (CM9). In total, I'll say it took about 15 minutes, but it was well worth it to give me some piece of mind that I had done everything correctly.

Now I'm back rockin' CM9, and it actually booted about 10 seconds faster than v1.06, which is always nice. Can't say this enough...thank you Hash! You're killing it!! :)

Dirty Jersey Ice Cream Sandwich Distribution Inc.
[Motorola Droid 3] TBBle:
Any reason you didn't take my ME863/XT860 patch? It at least gets nandroid working....
[Motorola Droid 3] emprize:
just flashed brasil 2.3.5 rom on my me863, then install safestrap, but after i see the new splash screen and press the menu button, it just reboot, so never can go in recovery mode, any advise?
[Motorola Droid 3] Willis111:
Think it slipped his mind, I mentioned it to him last night and he said he'd get around to it. You need to have your phone plugged into the computer to get into the CWM menu
[Motorola Droid 3] jjhiza:
Deleted...

Dirty Jersey Ice Cream Sandwich Distribution Inc.
[Motorola Droid 3] Endoroid:
Whats the point of having safestrap apk installed in your safesystem

xt860, android 2.3.5, Monster rom
[Motorola Droid 3] Willis111:
Here is a recovery.zip modded w/Ricks patch for the xt860

(these steps assume you're already mounted rw with "adb shell busybox mount -o remount,rw /system")

1./ push it to /system/etc/safestrap(it goes on your non-safe system) "adb push recovery.zip /system/etc/safestrap/"

2./ chmod it to 755 "adb shell", "cd /system/etc/safestrap/", "chmod 755 recovery.zip"

3./ chown it to root.shell "chown root.shell recovery.zip", "reboot"

reboot.

This should allow you (xt860/me863) users to get into recovery mode without having to connect your phone to the computer, at least until Hashcode gets around to importing the fix. It's working on my xt860 at least.
[Motorola Droid 3] eww245:
It will always install to the /systemorig partition regardless of where it is.
[Motorola Droid 3] Hashcode:
Dunno, maybe you want to upgrade Safestrap's recovery but not swap back to non-safe to do it?
[Motorola Droid 3] Endoroid:
makes sense. But not having safestrap apk installed in safe system isn't detrimental?
[Motorola Droid 3] Willis111:
It must install needed files to the correct partition specifically. The program you run inside the OS just installs the software(when you click install recovery).
[Motorola Droid 3] ckarrow2:
Safestrap Error

I had an issue after installing 1.07 where I got the cache error... I've updated to v1.08 and now am getting a "read-only" area for /data... here's a copy of my error log:

Starting recovery on Sat Dec 17 01:27:21 2011

framebuffer: fd 4 (540 x 960)

Safestrap Recovery v1.08

recovery filesystem table

=========================

0 /tmp ramdisk (null) (null)

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

2 /emmc vfat /dev/block/mmcblk1p25 (null)

3 /systemorig auto /dev/block/mmcblk1p21 (null)

4 /cache ext3 /dev/block/mmcblk1p22 (null)

5 /system ext3 /dev/block/mmcblk1p23 (null)

6 /data ext3 /dev/block/mmcblk1p24 (null)

I:Completed outputting fstab.

I:Processing arguments.

I:Checking arguments.

I:device_recovery_start()

Command: "/sbin/recovery"

ro.secure=1

ro.allow.mock.location=0

ro.debuggable=1

persist.service.adb.enable=1

ro.cwm.forbid_format=/misc,/radio,/bootloader,/recovery,/efs,/pds,/systemorig

ro.factorytest=0

ro.usb_mode=normal

ro.bootmode=unknown

ro.baseband=unknown

ro.carrier=unknown

ro.bootloader=0x0000

ro.hardware=mapphone_cdma

ro.revision=0

ro.kernel.memsize=512M

init.svc.recovery=running

init.svc.adbd=running

I:Checking for extendedcommand...

I:Skipping execution of extendedcommand, file not found...

Emmc space free: 9651MB

-- Backing up Safe System...

Backing up data...

tar: can't open '/emmc/safestrap/safe/data.ext3.tar': Read-only file system

Error while making a backup image of /data!

Switch to non-safe system aborts and I can boot normally into the safe-system..

Backup and restore now work since the /cache write problem is fixed... Is this a similar issue?
[Motorola Droid 3] porky101:
wait so i am confused should i turn on safe system after making that initial backup?
[Motorola Droid 3] jjhiza:
Yes. You want to backup your non-safe (original) system first. Then you can turn safe system on, and flash your second system ROM.
[Motorola Droid 3] Hashcode:
I'm not sure what would cause a "read-only" file system. I'm on 1.08, and haven't experienced this issue. The data issue you **might** get if you swapped oddly in 1.07, but it should go away after you successfully toggle the next time.
[Motorola Droid 3] Willis111:
That actually reads more like an error that /emmc/safestrap/safe/ or /emmc is read-only to me. The "can't open '/emmc/...:Read-Only file system"
[Motorola Droid 3] ckarrow2:
After a few tries, and having to restore the non-safe system from a backup, I'm now able to switch between systems with no errors. No sure what the problem was but I do appreciate your help and all of the great work you've done with this phone's software!!
[Motorola Droid 3] DoubleYouPee:
I currently have stock rooted 5.6.890 rom as non-safe and maverick rom 1.1 as safe-system. Could someone tell me what I'd need to do to get maverick rom as non-safe, so I could test ICS as safe-system?

Will I need to :

1) flash stock SBF

2) root, install bootstrap or safestrap??

3) flash maverick

4) switch to safe-system

5) Install ICS

?

Why would I need to use bootstrap instead of safestrap? If I stay in non-safe and install maverick from zip it will flash to non-safe right?
[Motorola Droid 3] tonyx3:
Installed 1.08 for D3, and now my D3 won't boot at all. It gives me the 'M Dual Core Technology' splash screen, and stays there forever.

Went back and checked the md5 of the safestrap .apk I downloaded, and it doesn't match what's on the website. Re-downloaded multiple times, always got the same md5, but it doesn't match. The download page lists the md5 for 1.08 as

416786e83d54fc2423fde03ac82dd91a

But WinMD5 shows my copy of Droid3Safestrap.apk as

8e8853a769f679c9246c08272f4dda44

The apk installed fine, and it got su priveleges, and the 'install recovery' button seemed to work, at least it flashed me the 'install completed' notification.

So I tried to re-boot, and bang, now I can't boot.

Looking for help/suggestions on what to do next.

My phone is stock, but rooted by oneclick. No other roms or recoveries or bootstraps have ever been on it.
[Motorola Droid 3] DoubleYouPee:
Why can't safestrap flash non-safe? If I would want maverick as non-safe and CM9 as safe, I wouldn't be able to update maverick without installing safestrap, reinstalling bootstrap, updating rom, and reverse. Why can bootstrap flash it and safestrap can't?

Now I have stock as non-safe.. so you can go back if you kill the safe-rom. However you can also do this by flashing SBF so there's no need to have stockrom as backup
[Motorola Droid 3] Phibernaut:
My battery ran out while sitting on the end table overnight after testing the latest ICS for a few hours.

I plugged the D3 in this morning and it immediately began boot looping to a 0% battery image. Motorola logo, Safestrap, battery image, repeat. Now it’s up to 5% after an hour on the charger and I’m hoping it’ll decide to boot if/once it reaches a reasonable charge level.

I’ve tried the usual reformatting the system, reinstalling the latest ICS, reformatting the cache, resetting the system, rewiping the davlik, etc. Has anyone else seen similar issues on this or other ROMs?

UPDATE:

Interestingly, neither an older ICS restore or a reflash of the latest release would correct the boot loop but restoring a Blur based Maverick backup finally permitted the phone to shut off (though it’s not supposed to when I choose “restart” from Safestrap) and boot correctly.

I am moving this issue to the ICS thread.
[Motorola Droid 3] redsox985:
As I switch safe and non, does SS overwrite the old backup or does it create another? Because a few switches could easily suck up multiple gigs of card space.
[Motorola Droid 3] MrJudylicious:
not sure what went wrong but it looks like youll need to use rsd to sbf your phone. sorry bro, refer to the RSD thread for exact instructions, and do verify that u have a verizon d3 and not an xt860.

DoubleYouPee, hashcode designed safestrap to leave stock blur in a safe location and ready for updates vs using it to dual boot. it is a pita to go from bootstrap to safestrap and back if you wanted to update (or use ur camera lol). he did say once he might change it in the future, but i understand his reasoning.

Phibernaut -- i had the same problem in build previous to Alpha. It works now. It did suck though lol.

and redsox985 -- i guess u could say it overwrites, but its not really backing anything up, its moving that directory to keep it untouched.
[Motorola Droid 3] DoubleYouPee:
But there's no need to have a safe stock install other than OTA updates because with easy-unbrick you're back on stock in the same time it takes when switching safe to non-safe
[Motorola Droid 3] redsox985:
The only qualm I have about SS is that I can't flash my non-safe system. Would it be possible to add in non-safe flashing, but with an extra notification that says something like "You are attempting to flash your non-safe system. Are you sure you want to do this?" I don't like having to uninstall SS, re-install bootstrap, flash, reboot, uninstall, then re-install SS.
[Motorola Droid 3] pgzerwer:
I agree. Understand the principle of preserving the non safe install, but the current process is pretty cumbersome if you find a new daily driver to replace the one you started with. Maybe with two or three frightening warnings to pass through we could be allowed to overwrite the non safe portion.

Installed Mavrom on safe side to try out and found it to be much better than my rooted stock 890. Would like to set this as my non safe and flash the ICS alpha to try it out, but I am too lazy to jump through more than two hoops to make it happen (just being honest lol).

NOT a complaint; I love Safestrap and what it allows us to do on our devices. For all I know, it might not even be possible to make this work, but I personally think this suggestion would be cool if it could be done.