875 replies to this topic

[Bkthompson681]

You might want to look in Hashcode's corner if you haven't already, and maybe copy your question in the "safestrap 3.11 problems with stock rom" forum or "safestrap v3" forum.

[scwideglide]

So thats an odd issue for sure, although there have been a few odd things that have turned up. Here is a link to a similar problem:

Please Login or Register to see this Hidden Content

I know that cvhovey ended up contacting Hashcode with a log file.....

Could not figure out how to generate a log without getting into Safestrap so that was a bust but it helped me understand a little better how it works.....sort of. :-)

Got impatient so.......got everything back but the only way was to uninstall Recovery from Safestrap.......reboot phone (it booted into stock ROM).....uninstalled Safestrap3.11........reinstalled Safestrap3.11........wiped SDCARD (also cleaned up SDCARD-ext while I was at it......rebooted into Recovery, recreated ROM SLOTs and restored TWRP ROM backups. Don't know what caused initial problem but at least I could get back even when not getting to Safestrap. Always wondered what would happen and how to recover if I could not get to Safestrap, now I know. Probably not the best but the only way I knew how..,

[cmh714]

Glad you got it back working.

[runner1717]

Can you restore a backup to a slot of different size? Will it take advantage of the larger data area size? My favorite ROM is in a slot with a 2 gig data partition. Now that I've cleaned up some stuff I'd like to restore to a larger slot, one with a 3 gig data partition.

Is this possible?

TIA!

Mike

[cmh714]

Can you restore a backup to a slot of different size? Will it take advantage of the larger data area size? My favorite ROM is in a slot with a 2 gig data partition. Now that I've cleaned up some stuff I'd like to restore to a larger slot, one with a 3 gig data partition.

Is this possible?

TIA!

Mike

Smaller to larger yes

[Brad92]

Been out of the loop for awhile and was running the Christmas eve JB leak .8, I protected root with Voodoo, uninstalled SS recovery and flashed the update. Everything worked. Restored root and reinstalled SS. Recovery works, but every time I try and boot a slot, it gets past the SS screen and goes black for 30 seconds, then reboots. Any help?

[Brad92]

Never mind, looks like its due to the kernel.

Edit: I spoke too soon, its not fixed. Any help?

[jeff5241]

for some reason the link to download safestrap 3.11 is down... can someone upload a copy of the apk? thanks

[cmh714]

for some reason the link to download safestrap 3.11 is down... can someone upload a copy of the apk? thanks

Goo is having issues with Devs from A thru S. So yes, hashs code is temp unavailable....

[Brad92]

Here's a mirror:

Please Login or Register to see this Hidden Content

[spacemonkey]

Been out of the loop for awhile and was running the Christmas eve JB leak .8, I protected root with Voodoo, uninstalled SS recovery and flashed the update. Everything worked. Restored root and reinstalled SS. Recovery works, but every time I try and boot a slot, it gets past the SS screen and goes black for 30 seconds, then reboots. Any help?

Same things, after update JB leak 16 SS not workinging, ROM installing normal, when trying booting after red moto logo phone restart, stock ROM work without problem, try batakang, cyclone, aviator. Is there any solutions for this problem?

[nukeruss]

Same things, after update JB leak 16 SS not workinging, ROM installing normal, when trying booting after red moto logo phone restart, stock ROM work without problem, try batakang, cyclone, aviator. Is there any solutions for this problem?

I had the same issue yesterday. I had to reflash safe strap 3.11 from within the apk and then delete and regenerate my ROM slot to get it working again. I also backed up my ROM slot data image to my computer before I deleted the ROM slot. After I regenerated the ROM slot and installed the OS again (kexec JB 4.2.2), I pasted my old data back from my computer. It all works fine now.

Another issue might be that the ROMs based off of the .8 ota are not compatible with the .16 ota.

Sent from my Droid Razr Maxx on JB 4.2.2 kexec

[nukeruss]

Here is a link to a tool in the JB ROM section that will allow you to swap kernels as necessary to allow running ROMs based of of the .8 ota

Please Login or Register to see this Hidden Content

Sent from my Droid Razr Maxx on JB 4.2.2 kexec

[loonee2n]

OK, so apparently I found out that after installing SS3.11 and backing up my stock ROM, it turns out I'm one of the idiots that backed it up while still rooted. Turns out that you're not supposed to do that because restoring it boots to a blank screen. I'm still able to use the ROM I loaded in slot 1, but I'd like to get my stock slot back. Any help is appreciated.

[OldBaldy]

Use Matt's new utility to fastboot JB without wiping data, then re-root, reinstall safestrap and you should be good to go.

Sent from my DROID RAZR

[loonee2n]

Use Matt's new utility to fastboot JB without wiping data, then re-root, reinstall safestrap and you should be good to go.

Sent from my DROID RAZR

It says on OP that it is for JB leak only. Will it also work with JB OTA?

[OldBaldy]

It says on OP that it is for JB leak only. Will it also work with JB OTA?

His old unbrick was for the leak. His new one is the full fastboot for the OTA. Here's the link.

Please Login or Register to see this Hidden Content

Sent from my DROID RAZR

[loonee2n]

His old unbrick was for the leak. His new one is the full fastboot for the OTA. Here's the link.

Please Login or Register to see this Hidden Content

Sent from my DROID RAZR

Thanks. It's downloading now. So you think I should go with option 2? I don't care about a full wipe, so I could go with 1 also? Why wouldn't I go with option 4 since I already have SS3.11 installed?

[loonee2n]

Use Matt's new utility to fastboot JB without wiping data, then re-root, reinstall safestrap and you should be good to go.

Sent from my DROID RAZR

Thanks. It's downloading now. So you think I should go with option 2? I don't care about a full wipe, so I could go with 1 also? Why wouldn't I go with option 4 since I already have SS3.11 installed?

Nevermind, Just used option 1 and I'm back to stock. You guys ROCK!

[lex347b]

I get bootloops when using this with custom roms only, only one of the roms I have tried worked.