[XOOM2][RECOVERY/BOOTSTRAP] XOOM2/XYB Safestrap v3.1 [01/06 v3.12 - Stock Flash+]

Search This thread

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,424
23,730
SAFESTRAP v3.12 (2nd-System Bootstrap / Recovery)

** INSERT STANDARD DISCLAIMER: I'm not responsible for any damage you do to your phone using my tools. Always have a fastboot available for disaster recovery. **

Download the APK Installer Here for "XOOM2"
md5sum: 335f5bc247dfde9741c1173651591610
FOLLOW THESE INSTRUCTIONS: How to Safestrap
[ DOUBLE-CHECK you have the XOOM2 VERSION ]

CHANGES:
  • [01/04] (3.12) Fix initial file selector location for backup/restore
  • [12/29] (3.11) Allow use of custom updater-binary in .zip files for flashing on stock ROM (virtual slots still use prebuilt updater-binary in recovery).
  • [12/29] (3.11) BUGFIX: Fixed fake flash error at the end of a .zip install. (No real error, .zip installs fine)
  • [12/29] (3.10) Early support for booting custom ROMs on stock partitions. (Custom ROMs will need to be worked out for JB4.1 from Moto still)
  • [12/29] (3.10) Enable flashing to stock ROM -- BET FEATURE/STILL TESTING
    • After .zip installations, nandroid restore or system wipe on the stock ROM: the current Safestrap files are restored to the system partition (Doesn't include the APK in /data -- so if you're restoring an old backup, be sure to update the Safestrap APK)
    • During the Safestrap files restore a check is done to be sure there are minimal files on /system to re-enter Safestrap
  • [12/27] (3.07) Bugfix: missed some changes in Safestrap 3.06
  • [12/26] (3.06) Bugfix/Update for JB4.1 OTA for DroidRAZR (Non-JB devices can also use)
  • [10/17] (3.05) Fixed SD card / emmc sharing in recovery (UMS)
  • [10/17] (3.05) Fixed recovery installation/removal from ROM-slots
  • [10/14] Updated to v3.04 BETA.
  • [10/14] Recovery is now based off TWRP 2.2.2.1 (fully featured touch-based recovery)
  • [10/14] Can create up to 4 Virtual ROM-slots to flash ROMs to and when "Active" ALL TWRP functions affect that ROM-slot (For example: Flashing .zips, Backup and Restore)
  • [10/14] Nearly instant swapping from ROM to ROM
  • [10/14] User selectable data partition sizes during ROM slot creation: 1GB, 2GB or 3GB
  • [10/14] ROM slots are saved on the internal emmc space so that preinstall and webtop partitions are no longer used and shouldn't break OTAs.
  • [10/14] Charging in recovery
  • [10/14] Supports "Reboot Recovery" from Android OS
Entry to recovery via Splashscreen on boot-up. The screen stays up for around 8-10 seconds and if you hit the menu button, it takes you to Safestrap Recovery.


SPECIAL THANKS TO:
  • The entire TWRP team who has built an AMAZING recovery system.
  • The testers which have helped in past and present versions of Safestrap, knowing that it could mean they brick their devices.
As always, let me know what you think!
 

Attachments

  • mainmenu.jpeg
    mainmenu.jpeg
    110.4 KB · Views: 3,968
  • romslot-created.jpeg
    romslot-created.jpeg
    109.1 KB · Views: 3,461
  • filemanager.jpg
    filemanager.jpg
    83.8 KB · Views: 3,603
  • wipemenu.jpeg
    wipemenu.jpeg
    94.8 KB · Views: 3,072
Last edited:

taquion12

Senior Member
May 25, 2008
69
0
Caracas
Thanks man this sounds awesome, I'll test it right away, do you need logs or something?

Enviado desde mi XT910 usando XDA Premium HD app
 

jeffcavicchi

Senior Member
Dec 5, 2011
418
103
Wow - everything is working awesome - backup/restore work, ROM slot creation, switching, and deletion work - except the splashscreen is not active. It comes up, but it says Safestrap is disabled and the buttons are greyed out. I can get into Safestrap no problem using BPTools.

Charge Only mode working great too.

Super sweet!
 

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,424
23,730
So the buttons on the splashscreen don't work? Does the picture of the little Android look oriented correctly?

Safestrap won't be "active" till we get a ROM installed on a slot and have it booting.

Sent from my XT894 using Tapatalk 2
 

jeffcavicchi

Senior Member
Dec 5, 2011
418
103
So the buttons on the splashscreen don't work? Does the picture of the little Android look oriented correctly?

Safestrap won't be "active" till we get a ROM installed on a slot and have it booting.

Sent from my XT894 using Tapatalk 2

Exactly - Android is oriented correctly, but the buttons don't work. After 10s it boots into normal Android. Boot into Safestrap via bptools works fine, and everything in Safestrap seems to work fine.

And - CAN'T WAIT TO HAVE A ROM TO INSTALL!
 

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,424
23,730
I can do a new version which includes logging of the splashscreen and user touches in a bit to see where that's breaking.

Sent from my XT894 using Tapatalk 2
 

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,424
23,730
I just realized that this doesn't have the correct Safestrap theme in it. And the buttons in recovery might be "off" a bit. So those will be addressed in the next test.
 

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,424
23,730
v3.05.03 is up:

1. Added a new logfile to the splashscreen which generates /sdcard/ss.log
I'd like a pastebin of this logfile with 4 touches during the splashscreen:
1a. Touch once in the upper left corner of the screen
1b. Touch once in the upper right corner of the screen
1c. Touch once in the lower right corner of the screen
1d. Touch once in the lower left corner of the screen

2. Fixed some of the theme graphics which weren't updated for the 1280x800 layout
 
  • Like
Reactions: steeq and FCN

FCN

Member
May 10, 2012
30
3
Well the Buttons are still quite off. Also, The splash screen doesn't even appear with the new version, It's just a flashing red and white screen.

EDIT: The SplashScreen came on normal this time. But the buttons are still funky. I'll upload a touch log in a sec.
 
Last edited:

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,424
23,730
Well the Buttons are still quite off. Also, The splash screen doesn't even appear with the new version, It's just a flashing red and white screen.

EDIT: The SplashScreen came on normal this time. But the buttons are still funky. I'll upload a touch log in a sec.

Thanks, make sure they are in the right order starting top-left and going clockwise from there. :)
 

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,424
23,730
Hey Hash-
What do we need to do as far as un installing / cleaning up the previous version?

Sent from my XOOM 2 ME using Tapatalk 2

If you are going from 1 version of Safestrap to the next, you don't have to worry about anything.

Just install the new APK (it will let you know it's over-writing an existing app)
Then use "Install Recovery" button. Done. :)
 

jeffcavicchi

Senior Member
Dec 5, 2011
418
103
If you are going from 1 version of Safestrap to the next, you don't have to worry about anything.

Just install the new APK (it will let you know it's over-writing an existing app)
Then use "Install Recovery" button. Done. :)

Excellent - I'll be able to do some testing in a few hours!

Sent from my XOOM 2 ME using Tapatalk 2
 

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,424
23,730
K, from the log, its recognizing qtouch-touchscreen. I'll adjust my code to use that.

Sent from my XT894 using Tapatalk 2
 

FCN

Member
May 10, 2012
30
3
Ah, So will that help fix the Splash Screen And/Or the Funky Button issue?
 

taquion12

Senior Member
May 25, 2008
69
0
Caracas
Always says after downloadind the apk "there's a problem analizing the packet ",any clue?, xoom 2 Me 8.2 unfortunaly Honeycomb

Enviado desde mi MZ607 usando XDA Premium HD app
 

Top Liked Posts

  • There are no posts matching your filters.
  • 24
    SAFESTRAP v3.12 (2nd-System Bootstrap / Recovery)

    ** INSERT STANDARD DISCLAIMER: I'm not responsible for any damage you do to your phone using my tools. Always have a fastboot available for disaster recovery. **

    Download the APK Installer Here for "XOOM2"
    md5sum: 335f5bc247dfde9741c1173651591610
    FOLLOW THESE INSTRUCTIONS: How to Safestrap
    [ DOUBLE-CHECK you have the XOOM2 VERSION ]

    CHANGES:
    • [01/04] (3.12) Fix initial file selector location for backup/restore
    • [12/29] (3.11) Allow use of custom updater-binary in .zip files for flashing on stock ROM (virtual slots still use prebuilt updater-binary in recovery).
    • [12/29] (3.11) BUGFIX: Fixed fake flash error at the end of a .zip install. (No real error, .zip installs fine)
    • [12/29] (3.10) Early support for booting custom ROMs on stock partitions. (Custom ROMs will need to be worked out for JB4.1 from Moto still)
    • [12/29] (3.10) Enable flashing to stock ROM -- BET FEATURE/STILL TESTING
      • After .zip installations, nandroid restore or system wipe on the stock ROM: the current Safestrap files are restored to the system partition (Doesn't include the APK in /data -- so if you're restoring an old backup, be sure to update the Safestrap APK)
      • During the Safestrap files restore a check is done to be sure there are minimal files on /system to re-enter Safestrap
    • [12/27] (3.07) Bugfix: missed some changes in Safestrap 3.06
    • [12/26] (3.06) Bugfix/Update for JB4.1 OTA for DroidRAZR (Non-JB devices can also use)
    • [10/17] (3.05) Fixed SD card / emmc sharing in recovery (UMS)
    • [10/17] (3.05) Fixed recovery installation/removal from ROM-slots
    • [10/14] Updated to v3.04 BETA.
    • [10/14] Recovery is now based off TWRP 2.2.2.1 (fully featured touch-based recovery)
    • [10/14] Can create up to 4 Virtual ROM-slots to flash ROMs to and when "Active" ALL TWRP functions affect that ROM-slot (For example: Flashing .zips, Backup and Restore)
    • [10/14] Nearly instant swapping from ROM to ROM
    • [10/14] User selectable data partition sizes during ROM slot creation: 1GB, 2GB or 3GB
    • [10/14] ROM slots are saved on the internal emmc space so that preinstall and webtop partitions are no longer used and shouldn't break OTAs.
    • [10/14] Charging in recovery
    • [10/14] Supports "Reboot Recovery" from Android OS
    Entry to recovery via Splashscreen on boot-up. The screen stays up for around 8-10 seconds and if you hit the menu button, it takes you to Safestrap Recovery.


    SPECIAL THANKS TO:
    • The entire TWRP team who has built an AMAZING recovery system.
    • The testers which have helped in past and present versions of Safestrap, knowing that it could mean they brick their devices.
    As always, let me know what you think!
    11
    I'm rolling out a new Safestrap v3.11. It includes quite a few updates and should fix the backup/restore data size bug.

    Just a heads up. It will probably still take me a day or two to get the build ready.

    Sent from my DROID RAZR using Tapatalk 2
    10
    OP updated for Safestrap v3.12:

    Download the APK Installer Here for "XOOM2"
    md5sum: 335f5bc247dfde9741c1173651591610
    FOLLOW THESE INSTRUCTIONS: How to Safestrap
    [ DOUBLE-CHECK you have the XOOM2 VERSION ]

    CHANGES:
    • [01/04] (3.12) Fix initial file selector location for backup/restore
    • [12/29] (3.11) Allow use of custom updater-binary in .zip files for flashing on stock ROM (virtual slots still use prebuilt updater-binary in recovery).
    • [12/29] (3.11) BUGFIX: Fixed fake flash error at the end of a .zip install. (No real error, .zip installs fine)
    • [12/29] (3.10) Early support for booting custom ROMs on stock partitions. (Custom ROMs will need to be worked out for JB4.1 from Moto still)
    • [12/29] (3.10) Enable flashing to stock ROM -- STILL BETA/TESTING
      • After .zip installations, nandroid restore or system wipe on the stock ROM: the current Safestrap files are restored to the system partition (Doesn't include the APK in /data -- so if you're restoring an old backup, be sure to update the Safestrap APK)
      • During the Safestrap files restore a check is done to be sure there are minimal files on /system to re-enter Safestrap
    • [12/27] (3.07) Bugfix: missed some changes in Safestrap 3.06
    • [12/26] (3.06) Bugfix/Update for JB4.1 OTA for DroidRAZR (Non-JB devices can also use)
      end of a .zip install. (No real error, .zip installs fine)[/b]

    PS. Sorry for the delay, was making sure with a tester that the basics are working.
    8
    Haven't finished the ROM entirely, work has been holding me up. Hoping to get done soon though.
    8
    I can't believe you guys do not have a custom rom yet. I might have to pick one of these up just to give you guys something lol.