Best Answer livinginkaos , 08 September 2014 - 10:16 AM
For Safestrap, using the save data as shown in the thread, yes you should, go into the app and disable it, then uninstall. Then follow the update/root/unlock instructions.
Go to the full postBest Answer livinginkaos , 08 September 2014 - 10:16 AM
For Safestrap, using the save data as shown in the thread, yes you should, go into the app and disable it, then uninstall. Then follow the update/root/unlock instructions.
Go to the full postPosted 08 September 2014 - 09:58 AM
Hello everyone. Long time reader. But reading doesn't appear to be clearing up some confusion I have. So first I will lay the groundwork then ask my questions.
The phone:
Droid Razr Maxx HD
9.30.1.XT926Verizon.en.US
Android 4.1.2
Rooted
SafeStrap
I am on 4.1.2 because the KitKat update bricked two of my phones. When I got the second replacement I immediately rooted (thanks to advise I found here) and froze the updater.
I would now like to update to KitKat and unlock the phone via methods found here:
If I understand the process, it's basically:
So, questions one if I may;
Sorry for the meandering post. I'm just trying to get all my ducks in a row before going forward.
Thanks in advance.
Bill
Posted 08 September 2014 - 10:16 AM Best Answer
For Safestrap, using the save data as shown in the thread, yes you should, go into the app and disable it, then uninstall. Then follow the update/root/unlock instructions.
Sig by livinginkaos
Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7
Posted 08 September 2014 - 10:31 AM
Then follow the update/root/unlock instructions.
Thanks for the reply. I'm still concerned that the KitKat update may brick my phone, but a bit less so now.
Posted 08 September 2014 - 11:08 AM
The actual OTA process for updating had a few things with it that could easily cause issues during the update. Here you are flashing the FXZ, full firmware, so chances are slim as long as you follow the directions.
Sig by livinginkaos
Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7
Posted 09 September 2014 - 04:28 AM
I am now happily updated, rooted and unlocked. Thank you so much for your help!
It's funny. All I ever really wanted was root on an up to date system. Now I have it all.
Posted 09 September 2014 - 07:45 PM
I am now happily updated, rooted and unlocked. Thank you so much for your help!
It's funny. All I ever really wanted was root on an up to date system. Now I have it all
I'm in the same boat as you, the ota downloaded 183.46.10 and it asks me every 12 hours if I want to install the update and I'm like hell no, so now I'm going to try this. Anything I should know?
Thanks
Posted 10 September 2014 - 02:35 AM
Updating to 183.46.10 gives you the ability to unlock the bootloader once again if you hadn't previously. It's you update to 183.46.14 you will lose the ability forever.I'm in the same boat as you, the ota downloaded 183.46.10 and it asks me every 12 hours if I want to install the update and I'm like hell no, so now I'm going to try this. Anything I should know?
Thanks
Sig by livinginkaos
Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7
Posted 11 September 2014 - 02:07 AM
I think my problem with the OTA was that I was rooted. At least on the first phone. Don't know why it bricked the second one.
As for anything you should know, there was one hitch I ran into. I was using windows 8 and no matter how many times I tried, the jar never started RSD. I had to manually start it and them open the keepdata.xml. It could be that the jar was supposed to be moved to where RSD was, but I thought that was why you had to tell it where it was in the first place. Who knows. Its simply to manually open the XML file so no big deal.
Posted 11 September 2014 - 11:39 AM
Windows 8 has been problematic for some people. I develop on it so I have no idea what causes the problem. I'm guessing it's a permissions thing but I really don't know. Works for some people not for others.
Non potest esse nisi unus
0 members, 0 guests, 0 anonymous users