What does the utility say when you are doing this? I read in the other thread to make sure to hit enter on the utility instead of any key. Grasping at straws here
unlock/recovery/reboot issues from the noob
#101
Posted 26 August 2013 - 03:45 PM
#102
Posted 26 August 2013 - 03:48 PM
Which SU app does Matt push with this utility? Maybe the binary needs an update? grasping with ya
#103
Posted 26 August 2013 - 03:49 PM
lol. I appreciate it definitely. the utility doesn't give any failed status reports, that's whats so confusing, the status is always success! and so I go to check it and it in the fastboot and it still says locked. but the root always works.
#104
Posted 26 August 2013 - 03:50 PM
ill get the app info in just a sec as soon as run the root again, then ill run the unlock and see if I can get some app info
#105
Posted 26 August 2013 - 03:54 PM
I even just reinstalled the drivers to make sure and it says that the Motorola network interface failed on the installation as well as the Motorola usb composite device failed.
#106
Posted 26 August 2013 - 03:55 PM
but the adb interface is ready to use
#107
Posted 26 August 2013 - 04:03 PM
the root took, and the unlock didn't.
#108
Posted 26 August 2013 - 04:06 PM
Did you check allow install from unknown sources under security in settings prior to running the unlock?
#109
Posted 26 August 2013 - 04:06 PM
no
#110
Posted 26 August 2013 - 04:06 PM
it didn't say to in the utility
#111
Posted 26 August 2013 - 04:10 PM
I'm grasping at straws here. When the app asked for SU perms did you say allow forever?? Is it SuperSU you have installed??
#112
Posted 26 August 2013 - 04:12 PM
I said allow forever, and its not superSU that comes with matts utility option 3, its just....superuser
#113
Posted 26 August 2013 - 04:13 PM
by chainsdd or the blue icon one from Koush?
if its chains you may need to update the binary
#114
Posted 26 August 2013 - 04:14 PM
the blue icon from koush
#115
Posted 26 August 2013 - 04:15 PM
by chainsdd or the blue icon one from Koush?
if its chains you may need to update the binary
That could be it. Go into the SU app and there should be something that says the binary is out of date
#116
Posted 26 August 2013 - 04:16 PM
I dont remember if theres an update binary function in that one, but poke around
#117
Posted 26 August 2013 - 04:17 PM
I dont remember if theres an update binary function in that one, but poke around
Will the app have an update in the market??
#118
Posted 26 August 2013 - 04:18 PM
Play store says: 1.0.2.1 and dated Aug 12, so yea theres a newer one
#119
Posted 26 August 2013 - 04:25 PM
#120
Posted 26 August 2013 - 04:26 PM
MD, you did mention that is was possible that your phone might have been updated in the past? If it was in fact updated to the newest OTA, you're out of luck with the BL unlock, regardless if you flash back to the previous version, or not. The OTA patches the "trusted zone" and it can't be re-opened by flashing backwards.
With that being said, if you haven't ever taken the update, you should be able to unlock. How long does the utility run, until it says it's a success? When I first ran the BL unlock, I ran it five times, with each saying it was success. Each time it worked for a few minutes. Well, it wasn't successful, until the fifth time. The last time, I woke up my phone while the utility was running and noticed a pop-up asking to grant root permissions to ADB. I pressed yes, and the exploit worked instantaneously. I was finally unlocked.
R. Long: Pixel 5
Also tagged with one or more of these keywords: unlock, bootloader, root, recovery, flash
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users