• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [International] [TOOL] Lock/Unlock Bootloader + Remove Tampered | Aroma GUI

This tool will allow you remove the Tampered flag from your bootloader. It will also allow you to easily Lock and Unlock your Bootloader directly from recovery.
No root required since it is run in recovery, however you still must be S-OFF.

Before using this tool you need to be sure you are using the latest version of recovery as the M7 U/UL TWRP requires at least version 2.6.3.3 for this package to work. The current downloads for both CWM and TWRP can found below:

The latest M7 U/UL TWRP can be downloaded HERE.
The latest M7 U/UL CWM can be downloaded HERE.

This should work for Verizon and Sprint as well, however they have different versions of these recoveries, so I am unable to verify.

Saying this again in case you missed it: YOU MUST BE S-OFF!


To use the tool simply copy the zip file to your phone and then boot to your custom recovery and choose install. Then browse to where you copied the file and select it. The aroma installer will begin. Follow the steps outlined in the pictures below and choose the options you want to run.

GBLpost.jpg



Now you can just keep this file on your phone and Lock and Unlock at anytime without a PC and without losing data.


***Credits***
S-trace for originally discovering the location of the lock status flag. See this thread.

scotty1223 for his ADB shell commands. Threads HERE and HERE. Scotty was also very helpful to me in understanding some of the default values.

Just to be clear I did not just copy and paste scotty1223's commands into a aroma installer. The echo command can be problematic in aroma, so I developed original code for all four commands. The end result is the same in that the data in the partitions is changed as needed.


***Download***

Guru Bootloader Reset Tool

md5: fdb8264a8f4741bae22939cd7734f7c2



Enjoy!

If this helped you out please consider a small donation or just a thanks would be great.
 
Demo Video:




***Troubleshooting***

If the installer stays on this screen fore more than a few seconds, then it means you need to delete/format cache. This can be done within both recoveries. You may need to reboot recovery after clearing cache and begin the installer again. This seems to happen more on CWM than TWRP.
Installing.jpg


If the installer runs but your bootloader doesn't change, it is proably one of these things:
  • You are not S-Off
  • You do not have the latest version of recovery (I recommend TWRP)
 
  • Like
Reactions: kdj67f and scotty85
Upvote 0
awsome! especially thnaks for giving proper credit to s trace. i picked up his ball and ran with it to get the word out to other devices,but there would be none of this without him,and his original work seems to go somewhat un-noticed.

sprint and vzw are using their own recoveries,so your nandroid tool would need those specific versions,but the flag locations are across the board,so this should work fine on sprint and vzw variants,as well as m7_u.

i prolly can round up a couple vzw testers if you want :)
 
  • Like
Reactions: kdj67f
Upvote 0
I've tried installing it with flashify and it says that installation was successful. When I go to the boot loader-> recovery it tries but just restarts into the Rom. This happened after I used guru and it didn't remove the locked and tampered flags either. I .did use moonshine tow root and I did some stuff that I don't remember in updating the hboot.
 
Upvote 0
I've tried installing it with flashify and it says that installation was successful. When I go to the boot loader-> recovery it tries but just restarts into the Rom. This happened after I used guru and it didn't remove the locked and tampered flags either. I .did use moonshine tow root and I did some stuff that I don't remember in updating the hboot.

maybe try flashing it the old fashioned way. put your image into your adb/fastboot folder,place phone in fastboot and flsh the image with:

fastboot devices

fastboot erase cache

fastboot flash recovery imagename.img

fastboot reboot

after the phone boots,try and enter recovery

im a little disapointed we havent heard from crushalot,ill try and get hold of him on xda and see if he can pop in here :)
 
Upvote 0
Sorry guys. I had a family issue come up that has kept me away for the past few months.

After having a look, I know why this is happening.
Since the tool needed the cache wiped most of time for it to work, I built the script to wipe the cache first.

The problem is that I have it set to clear/wipe the cache partition on M7 U/UL device types which is mmcblk0p36. Unfortunately that is the Sprint partition where recovery lives, so running the tool would wipe recovery for Sprint devices.

I will remove the line in the script so it doesn't wipe cache and post it back as version 1.1 so that it will be more universal since the partitions for Locking/Unlocking/Tampered should be the same.

I will make a new post when the new version is up.

Sorry for the trouble.
 
  • Like
Reactions: scotty85
Upvote 0
No, my adb is not loading correctly. I'm trying to find adb for windows 8. I'm trying to download adb again.

Do you have an older laptop or desktop you could use? Fastboot flashing should let you reinstall your recovery.

ADB works fine in windows 8 / 8.1
it's only fastboot that is broken on windows 8.1 and only on hboot below 1.55 is it a problem.

try these drivers
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
MD5: e2a21d71954d4164c1a116abb926a363

and here's the versions of adb and fastboot I use in windows 8.1
https://www.dropbox.com/s/0wzwt8843zx27nh/Fastboot.zip

their dated 7/25/2013
 
  • Like
Reactions: scotty85
Upvote 0
The twrp image that I downloaded said that it is corrupt when I double click it. I did it once by accident then I tried to install it using cmd.exe When it goes to installing the image it says

FAILED <remote: not allowed>


Sounds like you are not unlocked. In this case you'll need to install recovery as a zip file using ruu mode
 
Upvote 0
I downloaded goomanager and successfully installed twrp 2.6.3. I have a recovery now. Problem is I need the latest version right? If I run the guru tool to unlock with 2.6.3 recovery would that work?

Should work with that version, but I don't have the Sprint variant and sometimes there are tiny differences in the TWRP versions across the different device types.

And yes Scotty was saying that if you get that error when trying to flash a recovery via fastboot, more than likely your bootloader is not unlocked which is needed to write a new recovery via fastboot.

Hope you are all set now.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones