6 replies to this topic

[kitcostantino]

     This may sound like a strange request, and to many may be considered frivilous and highly unnecessary, but I really want Safestrap for my unlocked XT108oMDEV. (Droid MAXX Developer Edition). I know, just use TWRP, CWM, PHILZ, etc...but after my stock backup of 12.7.7 failing to boot after TWRP 2.6.3.0 restored it, (i did root before backing up), I feel like it would be awesome to have the option to use my stock software as a failsafe. I have seen others post the same request, but I do not know how difficult that would be, nor if it would be the PITA Hashcode had making the version for locked bootloaders. i almost think it would be easier, but easy is relative for me to say. So what do you think, Hashcode ? Is it viable? More of a pain than what it is worth? I appreciate everything you have already done for the community, and I was rediscent to even ask, but I figured it couldnt hurt to ask. Thank you. 

[johnlgalt]

SafeStrap was developed primarily for devices with locked bootloaders.  See

Please Login or Register to see this Hidden Content

[kitcostantino]

I, like you, John, have used safestrap heavily on the Bionic. I just didnt know if maybe twrp, cm, Hashcode, or whomever could be convinced into developing a different version exclusively for unlocked mot8960 devices. The folly in my thought, i guess was that the unlocked bootloader would make it far easier (considering there is a version for locked bl's). I have read the "about" on both of hashcodes sites over the last couple of years. (Im a bionic man, still, as well)  I get that part. I also read his frustration on developing the locked version (for the maxx, i believe).  I guess i was wrong on that.  Thank you guys. 

[johnlgalt]

If there is a version of SafeStrap for your device, it should work regardless of whether the bootloader is locked or not.  My understanding is that it is designed to allow those with locked bootloaders to overcome the ability of not being able to run a custom ROM.  However, it is not designed to require that the bootloader be locked.  It will still function in the same way, but you'll have to use the SS app to boot into the SS recovery in order to handle the switching process, so that your default recovery does not take over the process.

 

Nowm, don't quote me on this, as my understanding might be incorrect, but when I did use it I'm pretty sure that was the takeaway message that I got from using it.

 

The other thing to realize is that SafeStrap is really a backward way of doing things that an ordinary custom recovery should be able to do with an unlocked bootloader in the first place.  Also, was the backup that you made of stock made in TWRP 2.6.3.0, or another version (or another recovery)?  That could be a factor.

 

One thing that you can do instead of going the SS route is to bring your phone back to stock like you had it, and make two backups, and then copy both to your computer.  Now, wipe the phone, restore one backup and see if it boots - if so, you're good, and keep that backup in a safe place on your computer just in case your microSD card takes a nosedive.  I learned a long time ago to make backups of the backups because of the same problem, where a previous backup failed to load when restored on my OG DROID.

[kitcostantino]

You get what I was saying from the onset, John. If it works on locked it *should* work on unlocked. It likely would be a pita to use BC no one is supporting it on non-stock kernels. It is backwards and the secondary feature I would really want (press menu (recents?) for recovery screen) would not work as-is. It just is such a brilliant idea. I am runningliquid smooth KK on my bionic now, vanir on my rezound (snuzzo's carbon was awesome), and after my delving into boot loader warning land, I really just want a quicker, safe way to flash w/o modding an fxz, moving up from factory devedition software, or bricking. (I have owned 8

bionics and only lost one due to the red triangle of death radio fry. I saved them all thanks to safestrap and the HOB/HOM. 

         As far as what i did/was on, i was on twrp 2.6.3.0 backed up stock, flashed liquidsmoothkk (drdevs.com) and then wiped. But i accidentally wiped everything (internal sd too.) I then couldnt fxz until i modded the "get var" line from the fxz and then flashing TWRP 2.6.3.0 again via fastboot (credit sam for the xml edit idea indirectly) and managed to fxz my originAl software, but it was glitchy. I repeated all steps sans wiping internal SD, and still could not restore stock and locked into the boot loader unlocked screen. At that point, I missed the fxz to have hashcodes TWRP 2.6.3.1 for unlocked (ghost) and leftthe internal storage wipe intact but still had to delete the get var line BC it was erroring out on that step. This time the flash via rsd went completely right. I am gun shy at the moment to test it out again. I was on the same recovery version. I wiped dalvik/cache after restoring and also tried leaving them intact on 2.6?3.0 . I am at a loss, but I am wanting to try out yesterdays Gummy rom and Nitro's eclipse test ROM. Stock JB it is for now though.  Up at 4am to be on an ambulance all day tomorrow. Gotta have a functional phone.

[johnlgalt]

Oh, well, if you wipe everything, then yeah, no going back lol.

 

Make your backups to External microSD, power off the device, then copy the contents of the microSD safely onto your computer, and then go back and play with new ROMs and whatnot.

 

Safest way to make sure that even an accidental full wipe will not leave you totally high and dry.

 

Then you can play with the new gummy too

[kitcostantino]

gummy's recovery won't download for some reason. throws up a page of code (actually i think it is the code for the recovery). Gonna try again on the laptop in a few. I figured out my issue was the system being borked (unmounting itself, not allowing full wiping/root access, and not allowing a proper wipe of system via recovery, red lite, nor fast boot. i ended up completely wiping the Maxx again. manually pushing system to isolate the error using fast boot (system (sp space [low/insufficient ] )  I think i am back on track now as Root Browser (for the first time since I pushed custom recovery, etc) actually downloaded it's utilities and I have proper root access on the system now. I still do not know what I did wrong. perhaps my fast boot setup I used was off. I honestly am just glad to (at this point) have the phone hackable for real considering it is a dev edition. I wish I could port Carbon. Maybe that will be my next reading/learning project.