69 replies to this topic

[newms323]

You may want to take your questions/concerns to hash`s thread about safe strap. It's in the development section.

Sent from my DROID SPYDER using Xparent SkyBlue Tapatalk 2

[strongbowsix]

I also did not go to the non-safe side. Ugh. I was in perpetual boot loop with the original red eye. I went into fastboot and used RSD to flash the official 211 code. Let it do its thing wit android dude, yet when it went to reboot it went perpetual boot loop again. I again went into fastboot and powered down from there. At least the phone turned off and I was able to charge it to 100% overnight. Now I need to try again to reflash to stock.



Since I am not seeing the SafeStrap flash even thought I installed 3.04, but it is obviously getting stuck on the bootloop in the stock rom, should I do a hard reset as motorolla suggests

Please Login or Register to see this Hidden Content

?

I also went into boot loop. I think my issue may have been that I moved the Safestrap files before disabling Safeside and rebooting maybe? Either way I ended up stuck in a bootloop (Continual Eye).

How I fixed:

• Booted into Safestrap recovery again.
• Did a Factory Reset
• Rebooted and set up google accounts again.
• Reinstalled SS 2.x
• Disabled SS 2.x recovery
• Moved Safestrap directory to SD-EXT
• Uninstalled SS 2.x APK
• Followed Install instructions for SS 3.x

SS 3.x is sweet, thanks!

[nobreak1970]

So far so good on Bionic.
Good stuff man.

[brewzer]

I came from Galaxy Nexus to Razr and I must admit so far loving it. This safestrap is awesome and it was easy to set up, no problems on my end.

My Question:
Can you use Titanium backup to reload your apps in the different roms in each Rom Slot? (before I try it and screw something up).

[androidlearner]

I came from Galaxy Nexus to Razr and I must admit so far loving it. This safestrap is awesome and it was easy to set up, no problems on my end.

My Question:
Can you use Titanium backup to reload your apps in the different roms in each Rom Slot? (before I try it and screw something up).

I have been doing so without any issues so far. I can't speak for anything system related though

Sent from my Droid Razr Maxx Full Throttle

[nybelle]

I disabled safe system, uninstalled recovery, removed the old safestrap, and installed the new safestrap. Now I'm stuck in boot loop. I boot into the new safestrap screen, but clicking menu goes into boot loop, as does clicking continue. Any suggestions??

[dmlsthe1]

I remember reading hash's blog and seeing the reasons he made ss3. One being that he wanted to be able to charge while in recovery. Is that possible in this version? Or is it something he is still working in implementing? If I'm wrong and that's completely off than just say so lol

I disabled safe system, uninstalled recovery, removed the old safestrap, and installed the new safestrap. Now I'm stuck in boot loop. I boot into the new safestrap screen, but clicking menu goes into boot loop, as does clicking continue. Any suggestions??

Sorry but i don't know what's causing that. Rsd? Or Matt's utility?

Sent from DDRMaxx using Xparent ICS Tapatalk 2

[SpyderMan]

dmlsth1 installation of the SS3 update will kill your existing Safe side rom

you have to create a rom slot (top left box in rom slot screen) & then go to the Wipe button- do the wipes the rom's dev requires; then install the rom.

Always be careful to note which rom slot is active & you'll be fine.

[monkteo]

dmlsth1 installation of the SS3 update will kill your existing Safe side rom you have to create a rom slot (top left box in rom slot screen) & then go to the Wipe button- do the wipes the rom's dev requires; then install the rom. Always be careful to note which rom slot is active & you'll be fine.

I personally put the name of the room on the partition created

[Quadroller]

I've got a question on useing safestrap. I've got 4 rom slots created and have four of my favorite roms that I switch back and forth from. My question is is there a way to create the rom slots on the sd-ext instead of the internal card? wit the four rom slots created on the internal card I keep getting the storage is low warning in the notification bar.



Thanks in advance

[robocuff]

My question is is there a way to create the rom slots on the sd-ext instead of the internal card?

No. Hashcode answered this question somewhere here. Maybe in the safestrap thread. Anyway, he stated it would be too slow. And, if you did have a card that would run fast enough, a lot of people wouldn't and it would just lead to a full email inbox for him ( "Why does it run so slow?" ). Something to that effect anyway. So, at this time anyway, it's your internal memory or none at all.

[Nitewolf]

Also. I believe using the ext-sd in that fashion would tend to burn it out quicker.

[markaguerrero]

dmlsth1 installation of the SS3 update will kill your existing Safe side rom

you have to create a rom slot (top left box in rom slot screen) & then go to the Wipe button- do the wipes the rom's dev requires; then install the rom.

Always be careful to note which rom slot is active & you'll be fine.

help!!! it doesn allow me to create rom slot...i choose the partition i want but the creat rom slot button never highlights. what do i need to do?..thanks

[markaguerrero]

help!!! it doesn allow me to create rom slot...i choose the partition i want but the creat rom slot button never highlights. what do i need to do?..thanks

i think its not enough internal memory so i was told..

[The Persuader]

I've got a question on useing safestrap. I've got 4 rom slots created and have four of my favorite roms that I switch back and forth from. My question is is there a way to create the rom slots on the sd-ext instead of the internal card? wit the four rom slots created on the internal card I keep getting the storage is low warning in the notification bar.



Thanks in advance

Storage Low....

You may have to delete some of your Backups when your getting this message...I usually keep 5 in total...4 for your Slotted ROMs and 1 for Stock Rooted...

Its Bubba

[The Persuader]

Morning everyone,

Just Flashed SS 3.07...So far so good...

But here's my Question...
Since I've D-loaded the New process of Safestrap the "Error Message" I'm getting now is;
"Internal Storage is Out of Space" or "Low Memory" ...Never had this problem before this New Install of SS...something tell me to Wipe Internal Memory and start over or a Factory Reset...

Is this Not a Good Choice on my part...

Can someone tell me How to get into the Guts of Internal Storage or Low Memory...think thats the same...

Everything is running Awesome, No Glitcy, Smooth, Fast and Very Responsive...

Its Bubba

[pmassey31545]

I posted in another

Please Login or Register to see this Hidden Content

but it seems this one is more fitting.

1) I am having issues getting the latter versions to see my SD card and v.2.11 will not let me format /system.
2) Also, when I try to perform a restore from a backup, I get an md5 mismatch error. I would be satisfied at this point just to be able to restore my backup.

Any body have any ideas on either issue???

I generated a report and it's long if anyone knows how to read it. I think my format problem is mentioned at the end (lines 49-55) but not sure what to make of it. Bad internal card (emmc)??? I added the numbers for the lines for better reference.


Starting recovery on Tue Jan 1 12:11:38 2013
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (540 x 960)
Safestrap Recovery v2.11
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 0
2 /emmc vfat /dev/block/mmcblk1p25 (null) 0
3 /systemorig auto /dev/block/mmcblk1p20 (null) 0
4 /system auto /dev/block/mmcblk1p23 (null) 0
5 /data ext3 /dev/block/mmcblk1p24 (null) 0
6 /cache ext3 /dev/block/mmcblk1p21 (null) 0
7 /preinstall ext3 /dev/block/mmcblk1p22 (null) 0

• W:Unable to get recovery.fstab info for /osh during fstab generation!
• 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.sf.lcd_density=240
• ro.default_usb_mode=2
• windowsmgr.max_events_per_sec=55
• ro.ngp_available=1
• ro.modem_available=0
• ro.opengles.version=131072
• dalvik.vm.heapsize=32m
• persist.mot.proximity.touch=1
• ro.service.start.smc=1
• ro.HorizontalBUA=true
• mot.proximity.delay=450
• mot.proximity.distance=60
• ro.mot.bindervm.config=210
• ro.hdcp.support=2
• ro.mot.setuptype=2
• ro.mot.internalsdcard=1
• dalvik.vm.dexopt-flags=m=y
• net.bt.name=Android
• net.change=net.bt.name
• dalvik.vm.stack-trace-file=/data/anr/traces.txt
• ro.mot.dpmext=true
• ro.mot.hidden_keyboards=evfwd
• ro.cwm.forbid_format=/misc,/radio,/bootloader,/recovery,/efs,/pds,/systemorig,/preinstall
• ro.factorytest=0
• ro.usb_mode=normal
• ro.bootmode=unknown
• ro.baseband=unknown
• ro.carrier=unknown
• ro.bootloader=0x0A74
• ro.hardware=mapphone_cdma
• ro.revision=0
• init.svc.recovery=running
• service.adb.root=1
• init.svc.adbd=running
• I:Checking for extendedcommand...
• I:Skipping execution of extendedcommand, file not found...
• Formatting /system...
• I:Formatting unknown device.
• mount: mounting /dev/block/mmcblk1p23 on /system failed: Invalid argument
• Error mounting /system!
• Skipping format...
• Done.
• W:failed to mount /dev/block/mmcblk0p1 (No such file or directory)

[pmassey31545]

I posted in another

Please Login or Register to see this Hidden Content

but it seems this one is more fitting.

1) I am having issues getting the latter versions to see my SD card and v.2.11 will not let me format /system.
2) Also, when I try to perform a restore from a backup, I get an md5 mismatch error. I would be satisfied at this point just to be able to restore my backup.

Any body have any ideas on either issue???

I generated a report and it's long if anyone knows how to read it. I think my format problem is mentioned at the end (lines 49-55) but not sure what to make of it. Bad internal card (emmc)??? I added the numbers for the lines for better reference.


Starting recovery on Tue Jan 1 12:11:38 2013
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (540 x 960)
Safestrap Recovery v2.11
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 0
2 /emmc vfat /dev/block/mmcblk1p25 (null) 0
3 /systemorig auto /dev/block/mmcblk1p20 (null) 0
4 /system auto /dev/block/mmcblk1p23 (null) 0
5 /data ext3 /dev/block/mmcblk1p24 (null) 0
6 /cache ext3 /dev/block/mmcblk1p21 (null) 0
7 /preinstall ext3 /dev/block/mmcblk1p22 (null) 0

• W:Unable to get recovery.fstab info for /osh during fstab generation!
• 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.sf.lcd_density=240
• ro.default_usb_mode=2
• windowsmgr.max_events_per_sec=55
• ro.ngp_available=1
• ro.modem_available=0
• ro.opengles.version=131072
• dalvik.vm.heapsize=32m
• persist.mot.proximity.touch=1
• ro.service.start.smc=1
• ro.HorizontalBUA=true
• mot.proximity.delay=450
• mot.proximity.distance=60
• ro.mot.bindervm.config=210
• ro.hdcp.support=2
• ro.mot.setuptype=2
• ro.mot.internalsdcard=1
• dalvik.vm.dexopt-flags=m=y
• net.bt.name=Android
• net.change=net.bt.name
• dalvik.vm.stack-trace-file=/data/anr/traces.txt
• ro.mot.dpmext=true
• ro.mot.hidden_keyboards=evfwd
• ro.cwm.forbid_format=/misc,/radio,/bootloader,/recovery,/efs,/pds,/systemorig,/preinstall
• ro.factorytest=0
• ro.usb_mode=normal
• ro.bootmode=unknown
• ro.baseband=unknown
• ro.carrier=unknown
• ro.bootloader=0x0A74
• ro.hardware=mapphone_cdma
• ro.revision=0
• init.svc.recovery=running
• service.adb.root=1
• init.svc.adbd=running
• I:Checking for extendedcommand...
• I:Skipping execution of extendedcommand, file not found...
• Formatting /system...
• I:Formatting unknown device.
• mount: mounting /dev/block/mmcblk1p23 on /system failed: Invalid argument
• Error mounting /system!
• Skipping format...
• Done.
• W:failed to mount /dev/block/mmcblk0p1 (No such file or directory)

Well I can't get anyone to chime in anywhere on what might be going on so I installed SS 3.11 on my wifes phone which is identical to mine. Her's works perfectly seeing the SD card and all. Does this mean I have some sort of internal issue with the emmc? Or is that something I should take elsewhere? And if it is bad, does anyone know how I can prove it so I can get a replacement phone?

[robocuff]

Have you tried using chkdsk in Windows to check for errors on the card?

[SpyderMan]

MD5 errors mean that the checksum generated after your backup doesn't match the checksum on your backup file - the backup can't be restored afaik…