Thanks for posting the updated utility.
Number 4 explained mentions TWRP again instead of CWM though.
Will this work on the latest OTA 9.16.6? I know the previous version did not and I have been waiting to root my phone. If yes, do I simply do options 6, then 5, and my choice of either 3/4?
Unlock your bootloader before you try to do anything, it's the best safeguard to have.Matt,
First, let me say thanks for all your amazing work developing this phone and for the two utilites (I am very grateful for 1.10 and looking forward to using 1.20).
Before I jump into the utility, I want to (as briefly as possible) explain my situation (and now looking back, ask a ton of questions): I have 4.1.1, rooted, and have performed the Wireless Hotspot hack procedure. I am unable to take the 4.1.2 update (most likely due to my hacking of the hotspot app, though I may have done something else that I don't remember). Will I be able to use this utility to upgrade to 4.1.2? And unlock my bootloader? And keep (or re-do) my hotspot hack? What is the correct order for me? I'm thinking since I am rooted, I unlock the bootloader, then install 4.1.2, correct? Does this keep my root intact, or do I need to use VooDoo OTA Rootkeeper to unroot prior to performing the 4.1.2 update in the utility, then re-root?
Finally, is there a way to copy and save my currently installed apps (and pics, etc) so I don't have to re-install them all? Is this the function of Titanium Backup, or is there a different/easier way to do it?
Thanks again!
Thanks Matt!
- I've unlocked the bootloader this morning and it worked perfectly (have to find the program in the forum to change the "bootloader unlocked" startup screen now, but I digress).
- After installing 4.1.2 I can always re-root using the utility I'm guessing, yes? Yes... but it's better to flash SuperSu.zip through CWM or TWRP because no doubt in the next update the Motochopper exploit will be patched.
- Will the utility install 4.1.2 and replace a "modified" 4.1.1, or do I have to have a "stock" 4.1.1 ROM for the 4.1.2 to work? By "modified" I mean deleted apps, reconfigured SQLite Edited hotspot app, etc... I only ask since I cannot get the 4.1.2 OTA to install as my phone is currently, and was wondering if it was known if I would run into the same problem using the Utility 1.20. Or if this is the reason for the creation of the Utility 1.20...This Utility will install 4.1.2 using the FXZ files. You won't need to OTA, this brings you there.
- If I have to be stock and the 4.1.2 won't work as my phone is currently, I am thinking I could use the Utility 1.10 to go back to 4.0.4, then up to stock 4.1.1 and 4.1.2 from there (or straight to 4.1.2 from 4.0.4 if possible), then re-delete and re-hack the apps I want to delete and hack (if that all makes sense). I don't understand why you don't just go directly to 4.1.2 using this
Another blob of text, hopefully broken down a little bit better for you
Thanks Matt!
- I've unlocked the bootloader this morning and it worked perfectly (have to find the program in the forum to change the "bootloader unlocked" startup screen now, but I digress).
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 1.25 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/xbin/su:
Result: ---sr---wt root root 91980 2013-04-28 00:36 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwxr-xr-x root shell 380532 2013-01-11 13:48 su
Analysis: Setuid attribute NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your DROID RAZR HD device by Root Checker Pro version 1.3.1 from joeykrim in the Android Market - http://goo.gl/NcnHn