Develop Bugs

[HOW TO] Root a bootloader-unlocked Xperia Pro MK16a

There is now a MUCH easier way to root ALL Sony Ericsson 2011 phones including the Xperia Pro, making these instructions obsolete. Please see DooMLorD's thread here: http://forum.xda-developers.com/showthread.php?t=1319653
Remember to say thanks to DooMLorD for his awesome work!
However, I'll sill keep the 2 sets of instructions here in case anyone needs them or wants to refer back to them. My ZIPs do have all the drivers needed with good instructions on how to install them after all
My original instructions based on alvaroag's work can be found below, and the instructions via my instructions the Xperia Pro CWM Recovery method can be found on post 50 of this thread.
It's important to note that DooMLorD's tool only works for Windows. You can still use our original method in this post if you're running Linux.
We finally have a method to root the Xperia Pro MK16a (and PROBABLY MK16i) thanks to XDA Member alvaroag!!
This is his method, with the instructions modified by myself for ease of use.
What you need before you begin:
1. A rock hard stomach, because should the very unlikely happen and this brick/damage your phone in some way, I’m not responsible
2. An Unlocked Bootloader
NOTE: Sony offers a totally free, official, and simple method to unlock your bootloader here: http://unlockbootloader.sonyericsson.com/
Should that not work for you, your phone is probably SIM locked from your carrier (FIDO for example does that). You'll need to get the bootloader unlocked remotely from someone who has SETool and the appropriate security USB dongle. THIS COSTS MONEY, as SETool requires that user to pay per use.
Please see this thread for further instructions as it's the method I used personally: http://forum.xda-developers.com/showthread.php?t=1232050
Alejandrissimo was awesome at helping me through it.
3. On the phone itself navigate to the following locations:
a. Settings - applications – Make sure Unknown Sources (first option) is checked
b. Settings – applications – development – Make sure USB Debugging is checked
4. Download this archive. It contains all the files and drivers you will need:
http://www.mediafire.com/?7cz7672da9cxkrd​
Instructions:
1. Extract the archive you downloaded to a folder on your computer. Where doesn’t matter as long as you remember where it is.
2. Navigate to the folder ADB For Dummies (thanks to VanillaTbone for his guide) and install ADB for Dummies.exe
a. This will create a new folder on your C: drive called “android-sdk-windows”
3. Take the file “xperia_pro_root.zip” from the archive you downloaded and extract the contents to C:\android-sdk-windows\platform-tools\
4. Power off the phone and make sure it’s not plugged into anything.
5. Hold down the MENU button and connect the USB cable. A blue light will appear. If a blue light does NOT appear, then your phone can't get into FastBoot, and probably still has the bootloader locked.
a. If Windows asks you to install the drivers, install the driver from the folder “Fastboot Driver” in the archive you downloaded. Should those drivers not work, try the drivers found in "C:\android-sdk-windows\google-usb_driver"
6. Open the “Fastboot” folder in windows explorer (its part of the archive you extracted in step 1. Hold down the shift key and right click on an empty space in the folder window, select Open Command Prompt Here.
7. Type:
fastboot boot recoveryNEO.img​
8. The blue light on the phone will turn off, the screen on the phone will be blank, and the phone will be disconnected from windows, but after a few seconds you will get a Mass Storage & ADB Interface Detected. Note that the phone’s screen will continue to be black for the rest of this process. THIS IS NORMAL, your phone has not been bricked. If you need to stop anywhere along the way, simply unplug the phone from the computer and take your battery out. The phone will return to normal operations, though UNROOTED.
a. Windows will PROBABLY say hardware failed to install. This is fine.
i. Open the start menu, right click on “Computer” and select “Manage”
ii. Select Device Manager on the left side of the Computer Management window that opens.
iii. Look for the unknown piece of hardware. Right click on it and select update/install driver.
iv. Browse your computer, and select the main folder you extracted the archive to way back in step 1 – the drivers are somewhere in there, don’t worry about where, as windows will find them just fine.
9. On your computer navigate to “C:\android-sdk-windows\platform-tools”. Hold down the shift button on your keyboard and Right click on an empty part of the windows, and select “Open Command Window Here”
10. Type "adb shell". If it says "device not found", disconnect the USB cable, remove the battery, and try again from step 6. Also, try changing the USb port on your CPU. I'm not really sure about this, but I had to do it twice.
Now you’ll have to run a bunch of commands inside the ADB Shell window (the one with the black background and looks like a DOS window). You can just copy and paste each one from here. Be sure that once you start this step, you continue until the end of these instructions.
mount -t yaffs2 -o rw,relatime /dev/block/mtdblock0 /system​
If it says “/system is not empty” then type:
"rmdir /system/bin" and then run the first mount command again
type "exit"
11. From the DOS window, Run these commands (again copy and paste each one is fine)
adb push Superuser.apk /system/app/Superuser.apk
adb push su /system/bin/su
adb shell​
12. From the adb shell, run:
chmod 0644 /system/app/Superuser.apk
chown 0 /system/bin/su
chgrp 0 /system/bin/su
chmod 6755 /system/bin/su
ln -s /system/bin/su /system/xbin/su
cd
umount /system
reboot​
13. The adb shell will terminate. Disconnect the phone from the USB cable, wait for about 15 sec, remove the battery, and then turn it on.
14. From the phone, Open the Market, search for "Busybox" by "Stephen (Stericson)". Install that
15. From the Market, go to My Apps, search for "Superuser" by "ChainsDD" and make sure you're running the latest edition
16. Run the App "Superuser" from your app tray.
- under the settings tab, scroll to the bottom and click SU Binary "tap to check for updates"
17. Run the "Busybox Installer" app. Follow the onscreen instructions - just leave everything at default.
Congratulations! Your device should now be rooted! I personally suggest downloading and installing Titanium Backup to make sure - it will run a root check on startup and notify you if anything is wrong.
Notes:
This may seem to be a complicated method, but, as we will have to wait some weeks for an automated or simpler method, I think making writing an automated tool for this method is not worth the effort. But maybe, if no automated method appears in some weeks, I write one myself as a comunity contribution. - alvaroag​Thanks to VanillaTbone of XDA Developers for his awesome ADB For Dummies guide and app.
http://forum.xda-developers.com/showthread.php?t=502010
And of course thanks to Bin4ry for his NEO recovery image.
And thanks to all the other contributors to this thread for their help, advice, and overall contribution.
And if this thread helped you in some way, Please click THANK YOU to show your appreciation
Hello
Since there is no Xperia Pro forum I decided to post this here. Hope you can help me.
I recently bought an Xperia Pro MK16a and I have already unlocked the bootloader with setool (thanks to alejandrissimo and his remote unlock abilities). Now I'm searching for a way to root the device.
He and I experimented with it a bit, and we've already tried the recovery hot-boot with recovery.img from Arc, Play, and Neo, but with no luck. Recovery just doesn't boot.
He's guessing it's related to something like a different ramdisk or something like that.
Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse

rcummings100 said:
Hello
Since there is no Xperia Pro forum I decided to post this here. Hope you can help me.
I recently bought an Xperia Pro MK16a and I have already unlocked the bootloader with setool (thanks to alejandrissimo and his remote unlock abilities). Now I'm searching for a way to root the device.
He and I experimented with it a bit, and we've already tried the recovery hot-boot with recovery.img from Arc, Play, and Neo, but with no luck. Recovery just doesn't boot.
He's guessing it's related to something like a different ramdisk or something like that.
Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
If you bootloader is open you can flash directly "prerooted".img with fastboot? Arc and Neo have this option.
Regards!
Taavi
Sent from my MT15i using Tapatalk

Edit; ............
Sent from my LT15i using XDA App

taaviu said:
If you bootloader is open you can flash directly "prerooted".img with fastboot? Arc and Neo have this option.
Regards!
Taavi
Sent from my MT15i using Tapatalk
Click to expand...
Click to collapse
To be able to generate a pre-rooted system.img you need first a rooted phone and this is exactly the problem, how to root it if there is no recovery for MK16
For sure RootXperia.zip will work but for install it the proper recovery is needed first i guess

XperienceD said:
There is a Mini Pro forum. ;-)
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
Totally different phone
This is just the "Xperia Pro" - it was released in August. It's the same phone as the Neo, but with a slide out QWERTY keyboard. Model is MK16a (or MK16i for the international one)

Gingerbreak??
Sent from my MT15i using Tapatalk

Alejandrissimo said:
To be able to generate a pre-rooted system.img you need first a rooted phone and this is exactly the problem, how to root it if there is no recovery for MK16
For sure RootXperia.zip will work but for install it the proper recovery is needed first i guess
Click to expand...
Click to collapse
How to do it? Generate prerooted system.img
Thanks!
Sent from my MT15i using Tapatalk

I think that NEO recovery should work:
http://forum.xda-developers.com/showthread.php?t=1183465
Maybe the keys are wrong mapped, you have to try a little. Just flash RootXperia.zip from Recovery and you are rooted.
Regards

Bin4ry said:
I think that NEO recovery should work:
http://forum.xda-developers.com/showthread.php?t=1183465
Maybe the keys are wrong mapped, you have to try a little. Just flash RootXperia.zip from Recovery and you are rooted.
Regards
Click to expand...
Click to collapse
That was the first thing I tried, since the Pro should just be a Neo with a keyboard. Unfortunately it doesn't work.
Here's the output:
C:\root-play>fastboot boot recoveryNEO.img
downloading 'boot.img'...
(bootloader) USB download speed was 9336kB/s
OKAY [ 0.517s]
booting...
(bootloader) Download buffer format: boot IMG
OKAY [ 0.002s]
finished. total time: 0.519s​
The phone is clearly still turned on, but no longer in fastboot mode, and the screen is totally blank, though the backlight is active.
I've tried the same thing with the Arc and Play recovery images and had the same results.
What do you mean by the keys are mapped wrong?
Is this what you're talking about?
http://www.knowyourcell.com/sony-er..._hard_reset_the_sony_ericsson_xperia_pro.html
The instructions on how to get into Recovery on that site are very similar to how to do it on the stock build of my previous phone, the Motorola Milestone. Unfortunately THEY DON'T WORK
I've tried substituting the volume down button with other keys, but with no success. Pretty difficult to guess the right key combination when there's a full qwerty keyboard on here
Is there a way to boot into the standard recovery from ADB or fastboot or something? Possibly from an on-board terminal emulator? A command like "Reboot Recovery" perhaps? Or is that too easy to be possible...
It's ironic that my old Motorola milestone with a totally locked down bootloader proved easier to hack than this phone with it's wide open bootloader

Well,
i wrote you already in PM. But now here too. The PRO is only released in Canada and some Asien Countrys. Until it is released in Europe i cannot help you, because i need the device for testing.
One thing you can try:
after you fastboot boot and the phone is in blackscreenmode please unplug and replug it to pc.
Now try to adb shell on it. Is this working? If yes please gimme a logcat
Regards

Bin4ry said:
Well,
i wrote you already in PM. But now here too. The PRO is only released in Canada and some Asien Countrys. Until it is released in Europe i cannot help you, because i need the device for testing.
One thing you can try:
after you fastboot boot and the phone is in blackscreenmode please unplug and replug it to pc.
Now try to adb shell on it. Is this working? If yes please gimme a logcat
Regards
Click to expand...
Click to collapse
Nope, adb shell doesn't work. Shows "error: device not found"
But because I'm new to this (I came from a motorola milestone), I want to make sure I did what you actually asked of me:
- I turned on the phone into fastboot mode (hold down menu, plug in usb cable, get blue light)
- from a command prompt window: fastboot boot recoveryARC.img
(replacing ARC with NEO and PLAY depending on the image I'm trying)
- phone now boots into black screen, no blue light, screen backlight is on
- unplug from computer, plug back in
- from command prompt: adb shell
Are those the instructions you wanted me to follow?
Fastboot works fine. Can I do anything from there? Getvar for example, or something? can I run the command Update and flash the RootXperia.zip file? Or will that not work because it's not signed properly or something similar?

Via fastboot you cannot flash the zip. Zip needs to be flashed via recovery, because this only contains some files and not whole system!
I'm sorry, you have to wait until i have the device! Only if the adb shell would work i could help you, if even this is not working it's hard to say what's goin wrong. All you can do is sending me the kernel.sin from you firmware. Maybe i can mix something up with this file
Regards

Bin4ry said:
Via fastboot you cannot flash the zip. Zip needs to be flashed via recovery, because this only contains some files and not whole system!
Click to expand...
Click to collapse
I figured as much. Just hoped I might be wrong.
Bin4ry said:
I'm sorry, you have to wait until i have the device! Only if the adb shell would work i could help you, if even this is not working it's hard to say what's goin wrong. All you can do is sending me the kernel.sin from you firmware. Maybe i can mix something up with this file
Regards
Click to expand...
Click to collapse
Can anyone give me instructions or pointers on how I extract the kernel.sin from my firmware?
Thanks for your continued patience with me. I really do appreciate it.

Its funny how all the phones without forum ends up here!
Sent from my LT15i using xda premium

datagubben said:
Its funny how all the phones without forum ends up here!
Sent from my LT15i using xda premium
Click to expand...
Click to collapse
It's because they're all so similar, and are based on the same hardware as the Arc.

Process is simple:
IF you NEVER used UpdateService or PCCompanion BEFORE you unlocked your bootloader then : You need to relock bootloader first (sorry :/)
Then have to use SonyEricsson UpdateService/PC-Companion and tell it to REINSTALL/REPAIR your firmware.
If you used one of the tools before just skip the relock and do this:
After that is done you copy out the two files named:
FILE_XXXXXXXXXXX
FILE_XXXXXXXXXXX
where XXXXXXXXXX are some numbers. This files are located in the subfolder blob_fs inside the UpdateService/PC-Companion directory.
Just copy it on a "safe" place.
After that is done you have to start flashtool go to the "Advanced" Tab -> Decrypt -> then just choose the folder where you copied the files and let flashtool do its work
Afterwards upload the Firmware which is now present as a FTF file, somewhere and post it here (others will be happy to to have the whole MK16a Firmware )
Regards

Bin4ry said:
Process is simple:
IF you NEVER used UpdateService or PCCompanion BEFORE you unlocked your bootloader then : You need to relock bootloader first (sorry :/)
Then have to use SonyEricsson UpdateService/PC-Companion and tell it to REINSTALL/REPAIR your firmware.
If you used one of the tools before just skip the relock and do this:
After that is done you copy out the two files named:
FILE_XXXXXXXXXXX
FILE_XXXXXXXXXXX
where XXXXXXXXXX are some numbers. This files are located in the subfolder blob_fs inside the UpdateService/PC-Companion directory.
Just copy it on a "safe" place.
After that is done you have to start flashtool go to the "Advanced" Tab -> Decrypt -> then just choose the folder where you copied the files and let flashtool do its work
Afterwards upload the Firmware which is now present as a FTF file, somewhere and post it here (others will be happy to to have the whole MK16a Firmware )
Regards
Click to expand...
Click to collapse
Unfortunately the very first thing I did with the phone was unlock the bootloader. 'Fido' is the only phone company selling the phone, but I'm with 'Rogers'...so I needed to unlock the bootloader in order to actually use the phone as a phone, which was and remains the most important thing to me.
That being said, I'll see if Alejandrissimo can give me a hand with re-locking the bootloader, then I can get the firmware as you instructed, then have him re-unlock the bootloader. I'll just stick my SIM Card back in my old motorola milestone while we work on this so I can still have a working phone.
You're awesome Bin4ry for helping like this

Maybe I could help with that since I am with Fido and I have a locked bootloader (I haven't touched the phone except adding an ssh key) with my Xperia Pro MK16a. Though I know my way with ssh, I am new with the rooting stuff and Android. If you need some files or something from a locked bootloader I can help with that, just need some simple instructions.
Bin4ry said that files FILE_XXXXXXXXXXX were located under UpdateService/PC-Companion, can I access those via ssh? I have used PCCompanion only once when I got on Windows, but I am always on Ubuntu so I was wondering if I could get those file via scp and if so, where are they?.

ratius said:
Maybe I could help with that since I am with Fido and I have a locked bootloader (I haven't touched the phone except adding an ssh key) with my Xperia Pro MK16a. Though I know my way with ssh, I am new with the rooting stuff and Android. If you need some files or something from a locked bootloader I can help with that, just need some simple instructions.
Bin4ry said that files FILE_XXXXXXXXXXX were located under UpdateService/PC-Companion, can I access those via ssh? I have used PCCompanion only once when I got on Windows, but I am always on Ubuntu so I was wondering if I could get those file via scp and if so, where are they?.
Click to expand...
Click to collapse
If you could, that'd be great. I don't especially want to lock my bootloader over again since you have to use SETool to unlock it, which costs money each time you use it (essentially). Not to mention it involves some acrobatics with a paperclip to connect a testpoint inside the phone to a ground!
Unless there's an easier way to lock/unlock now that I've done it once that is...if so, I'm happy to do it.
As for accessing the files Bin4ry is talking about, boot to windows if you can and do it that way. Just follow his instructions to repair your firmware, then go to that folder in windows (it's located in C:\Program Files (x86)\Sony Ericsson\Sony Ericsson PC Companion). At least, that's my understanding.

Hi. Yesterday, I bought a Xperia Pro. Ive spent most of the afternoon and the nigh trying to root it, and I've finally got how to do it. It's a manual method, as there is not an automated one.
There's no need to say I'm not responsible for any damaged or bricked devices(but mine is working ok )
What you need:
1. The Xperia Neo Recovery, by Bin4ry, get it here
2. xperia_pro_root.zip I'm attaching. It contains the files from RootXperia.zip, but without the update.zip-related files, as they are not needed.
3. The Android SDK, with the Google USB Drivers Package.
4. If you've never used your device in fastboot mode, you may also need to follow steps 7 & 8 from SE bootloader unlocking tutorial.
5. [NOT REALLY SURE] Application Debugging & Unknown Sources enabled.
6. [NOT REALLY SURE] Unlocked Bootloader. This is because mine is unlocked, but I don't really know if that is required to boot the recovery image via fastboot.
I'm assuming that you are working on a Windows/Unix terminal, with a working directory where you have recoveryNeo.img, Superuser.apk and su /these two from the zip file I attach), and that fastboot & adb are on the PATH. If some file is not on the working directory, or fastboot/adb are not on the path, use full paths.
Instructions:
1. Disconnect & Power off the phone.
2. Hold down the menu button and connect the USB cable.
(If Windows asks you to install the drivers, install the driver from ANDROIDSDK\extras\google\usb_driver folder).
3. Run "fastboot boot recoveryNeo.img". The fastboot device will be disconnected, but after a few seconds you will get a Mass Storage & ADB Interface Detected.
4. Run "adb shell". If it says "device not found", disconnect, remove the battery, and try again from step 1. Also, try changing the USb port on your CPU. I'm not really sure about this, but I had to do it twice.
5. Run "mount -t yaffs2 -o rw,relatime /dev/block/mtdblock0 /system" from the adb terminal. If it says /system is not empty. run "rmdir /system/bin" and then run mount again.
6. type "exit"
7. Run :
adb push Superuser.apk /system/app/Superuser.apk
adb push su /system/bin/su
adb shell
8. From the adb shell, run:
chmod 0644 /system/app/Superuser.apk
chown 0 /system/bin/su
chgrp 0 /system/bin/su
chmod 6755 /system/bin/su
ln -s /system/bin/su /system/xbin/su
cd
umount /system
reboot
9. The adb shell will terminate. Disconnect the phone, wait for ~15 sec, remove the battery, and then turn it on.
10. Your device should now be rooted.
Notes:
1. When booting with recoveryNeo.img, the screen will keep blank. That's normal(I think).
2. This may seem to be a complicated method, but, as we will have to wait some weeks for an automated or simpler method, I think making writing an automated tool for this method is not worth the effort. But maybe, if no automated method appears in some weeks, I write one myself as a comunity contribution.
Hope this is usefull for you.

[HOWTO] Root Your Stock Galaxy Nexus

This post is now deprecated there are new ways of rooting more easily here is the link to one of those
http://forum.xda-developers.com/showthread.php?t=1392310
just kept for reference
link no longer works as it is a very old boot img, if you wanna go this way use latest superboot
Rooting your Galaxy Nexus
Download this file contains necessary files and also lastest samsung drivers in case you dont have them, probably you need android sdk drivers for fastboot
Download
credit to @peteralfonso for the insecure boot.img which allows this to remount system and this way install su binary and Superuser.apk
This are the instructions for Galaxy Nexus
they require basic knowledge of fastboot adb and using command prompt/terminal
works same way on linux and windows
Be sure to have fastboot and adb ready and working
extract somewhere and you will get 4 files su, Superuser.apk , boot.img and drivers
turn off the phone
Boot into bootloader mode (Vol UP+ Vol Down + Power) then execute this command, be sure to have fastboot and boot.img on same folder or be ready to type a long path pointing to your boot.img
REMINDER: by doing fastboot oem unlock you will completely wipe your device so be sure to backup anything important
execute this command
Code:
fastboot oem unlock
fastboot boot boot.img
edit: thanks chirality forgot the oem unlock
the device will reboot and start in unsafe mode where you can enable adb as root usually on production devices this is not posible
Be sure to enable adb debugging on menu
back to command prompt
Code:
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
and you are done and youve got your Galaxy Nexus rooted
This process does not involve flashing another boot.img, it just boots once with it and after that returns to original boot.img
As usual
YOU ARE PERFORMING THIS AT YOUR OWN RISK! I AM NOT RESPOSIBLE FOR ANY BRICKS OR PROBLEMS!
Which wont happen we are just pushing 2 files to our phone
edit2: sorry for the bad paths of adb was too late and didnt notice my error

Don't you have to do "fastboot oem unlock" first before being able to boot off the insecure image? I thought they fixed that with the Nexus S already.

Thanks for the post - apparently people are having problems with the Superboot method, so I'll give this a go when mine arrives today.
I guess this comes with all the usual "at your own risk" and "will void your warranty" warnings?
(sorry if that's a stupid question - this is my first Nexus, so I'm not sure where I stand on rooting, unlocking bootloaders, and the warranty etc.)

Great - worked without issue for me and I can now use the Entree VPN client for connecting into work. (the HD screen is great for remote desktop work)
Minor typo in the permissions lines though - should read:
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
Thanks very much,
Chris.

Thanks for this davioxx for putting together the guide, chriscole for the fixes and @peteralfonso for the insecure boot.img.
I'm now succesfully rooted.
It seems Root Explorer needs an update for the GN though. Only opens in the bottom left corner of the screen for me, and is comprised of static.

Sorry for the newbee question, been quite a while since rooting my nexus one...
Do i need to enable adb debugging on phone menu before executing the fastboot oem unlock code and then enable it again after it reboots and starts in safe mode?

w00t!
Thank you
You may want to change the path names on the chmod part, I blindly followed the instructions and the files were in diffrent places from where I pushed them to
But thanks \o/
I haz root!

Tnx, easy like all nexus devices, now need some you tube for that!
Sent Via My HTC Desire HD

looks pretty simple ... hopefully it will be the same process for us in the States

Not 100% sure what's going on here. I haven't rooted since I got the Nexus One.
When my phone is on and connected, command prompt shows my phone as an attached device. But when I boot into bootloader, it isn't attached anymore and command prompt just tells me that the commands are unrecognized? How come?

majikdragoon said:
Not 100% sure what's going on here. I haven't rooted since I got the Nexus One.
When my phone is on and connected, command prompt shows my phone as an attached device. But when I boot into bootloader, it isn't attached anymore and command prompt just tells me that the commands are unrecognized? How come?
Click to expand...
Click to collapse
Are you doing it via adb or fastboot?

Not sure. I restarted the phone into bootloader and tried to follow the instructions
Hahaha... I was trying to sideload N64oid as it's been removed from the market. I ended up using Android Centrals Sideloader instead.

majikdragoon said:
Not sure. I restarted the phone into bootloader and tried to follow the instructions
Hahaha... I was trying to sideload N64oid as it's been removed from the market. I ended up using Android Centrals Sideloader instead.
Click to expand...
Click to collapse
Hi probably you dont have the bootloader driver installed, that has to be done manually at least for my win 64 machine, check this thread about that
Set Up ADB, fastboot and drivers Nexus S it is practically the same for your Galaxy Nexus

Oh ok! I'll look at that now. Thanks fellas

Why couldn't you just....
Fastboot OEM unlock
Fastboot flash recovery
Flash su zip in recovery
(obviously, I'm omitting some steps here like after Fastboot flashing recovery, booting into recovery...ect)
Unless there isn't a custom recovery available yet...
That's how I rooted BOTH the N1 and NS....
Sent from my HTC Sensation 4G using xda premium until I can get the Galaxy Nexus on T-Mobile

there isnt a custom recovery yet and stock recovery needs signed recoveries
actually not hard you take 3 mins in all process
Babydoll25 said:
Why couldn't you just....
Fastboot OEM unlock
Fastboot flash recovery
Flash su zip in recovery
(obviously, I'm omitting some steps here like after Fastboot flashing recovery, booting into recovery...ect)
Unless there isn't a custom recovery available yet...
That's how I rooted BOTH the N1 and NS....
Sent from my HTC Sensation 4G using xda premium until I can get the Galaxy Nexus on T-Mobile
Click to expand...
Click to collapse

Babydoll25 said:
Unless there isn't a custom recovery available yet...
Click to expand...
Click to collapse
Ding ding ding.
Also some people don't want to flash a custom recovery anyway.
Sent from my Nexus S using XDA App

Drivers
Does anyone know where else to get the drivers from? installed the ones attached but when i go into device manager, i am seeing android.1 and when type "fastboot devices" nothing comes up

coleburns said:
Does anyone know where else to get the drivers from? installed the ones attached but when i go into device manager, i am seeing android.1 and when type "fastboot devices" nothing comes up
Click to expand...
Click to collapse
How I got fastboot working was to install pdanet, one of the steps is to install all the drivers. It doesn't matter if it fails after that step, I didn't want pdanet anyways
The ones attached seem to only be for adb mode.
Sent from my Galaxy Nexus using xda premium

el3ctrik said:
How I got fastboot working was to install pdanet, one of the steps is to install all the drivers. It doesn't matter if it fails after that step, I didn't want pdanet anyways
The ones attached seem to only be for adb mode.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
thanks for that, managed to get it working with pdanet.
however when i try to run the adb commands, i get the adbt cannot run as root in production builds
how did you get rooted?
thanks

Help with Unlocking bootloader with Htc dev on linux

I have been on this for 5 hours and i just cant seem to get anywhere.
I want to root my HOX i know you have to go to http://htcdev.com/ to unlock the bootloader but there isnt enough information from htc how to do it with linux and am still learing it i have follwed instructions from all over the web but i get no were. I have placed the Fastboot file from HTC in android/sdk/platform-tools i then go to type this command in terminal cd android/sdk/platform-tools i then get bash: cd: android/sdk/platform-tools: No such file or directory i have tried it via SU but i get the same.

elsworth1983 said:
I have been on this for 5 hours and i just cant seem to get anywhere.
I want to root my HOX i know you have to go to http://htcdev.com/ to unlock the bootloader but there isnt enough information from htc how to do it with linux and am still learing it i have follwed instructions from all over the web but i get no were. I have placed the Fastboot file from HTC in android/sdk/platform-tools i then go to type this command in terminal cd android/sdk/platform-tools i then get bash: cd: android/sdk/platform-tools: No such file or directory i have tried it via SU but i get the same.
Click to expand...
Click to collapse
Did you map the .zip or .bat? It needs to be unzipped into the folder to work.

vodka7 said:
Did you map the .zip or .bat? It needs to be unzipped into the folder to work.
Click to expand...
Click to collapse
Cheers for the reply i did unzip it and i was just coming to update my progress lol i finally got to the token part but it just waiting for device i typed in adb devices and it comes up with no info but if i boot the phone up normally a get a device number.
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$
[email protected]:~$ fastboot oem get_identifier_token
< waiting for device >

On linux, sometimes you need to mess with one of the virtual filesystems for it to see the device. I can't remember how it works now, but you add a file with the manufacturer id and product id.

BenPope said:
On linux, sometimes you need to mess with one of the virtual filesystems for it to see the device. I can't remember how it works now, but you add a file with the manufacturer id and product id.
Click to expand...
Click to collapse
Cheers for the info is it this what you are on about sudo adb kill-server if so i have tried it and it only shows the device when powerd on i have had a little play this morning before going to work still no joy I really want to unlock this device and flash a better rom than uk's O2 rubbuish but it feels like i am hitting my head against a brick wall. Any how thanks again this community rocks well of to work i go

hello,
I did it last week...
try
Code:
./adb reboot bootloader
the important part if you just unzip the "android/sdk/platform-tools" it that you put "./" before adb and fastboot commands and eventually before folders's paths
Give it a try.

Cheers will give it a try tonight when I get home @ work now and knackered lol
Sent from my HTC One X using xda app-developers app

You may also need to add your device ID to your udev rules. There are plenty of guides of you Google it

Michealtbh said:
You may also need to add your device ID to your udev rules. There are plenty of guides of you Google it
Click to expand...
Click to collapse
This is what I was talking about, stupid brain couldn't think of "udev".

RIght Back Home now lets have a play :laugh: thanks to every 1 for the help.
Just got fastboot flash unlocktoken Unlock_code.bin
BOOTLOADER UNLOCKED
Thanks again

[WIP] [TUT] How to Root HTC One Xv

Want closed till me and 8trix figure what the hboot update IMG is called
PLEASE HIT THANKS.... READ ALL BEFORE PROCEEDING
FIXED COMMANDS HAD A COMMON MISTAKES
Hi, I am a developer from the " HTC Droid Incredible 4G LTE " My Rom http://forum.xda-developers.com/showthread.php?t=2065615 and I am still a newbie at this developing thing.. So with this being said I am not resposable for anything that could or may happen.*
Now I'm this TUTORIAL I will be providing the links and the instructions on how to proceed on the rooting process
*Requirments*:
-Android SDK - http://developer.android.com/sdk/index.html
-HTC drivers -*http://www.htc.com/us/support/
-The Su .zip - attachment
-And.... The HTC One Xv of course.
STEPS:
1. On your computer make sure you have adb access ( usually just install android sdk )
2. Make sure you have HTC drivers installed ( remove HTC sync after the installment )
3. With that being said download the attachment file ( I downloaded the SU from*http://androidsu.com/superuser/ )
4. To makes matter safer your gonna need to Temp Root, download this : http://uploaded.net/file/h44f6vni
5.Once downloaded, unzip it to C:\Root. Navigate to the folder in the command Prompt by typing *please follow directions CLEARLY
- *cd c:\Root\stuff
- *adb devices
- *adb restore fakebackup.ab
DO NOT click OK to the restore on the device just yet! Now type:
- *adb shell "while ! ln -s
/data/local.prop /data/data/com.android.settings/a/file99; do
:; done"
(errors will appear, ignore) Accept the restore on the device, then type:
-adb reboot
(At this time, you are temprooted, and the phone UI will be in an unusable state, with temproot shell.) After reboot type:
- adb shell
Verify that the prompt is "#" (meaning root) or "$" (meaning normal user). If it's not "#", please start over. At this point, you can optionally do this ONLY if you want to revert changes:
- rm /data/local.prop
- exit
- adb reboot
Close cmd and start a new one then type
- adb devices
- adb install /system/apps/superuser.apk
- adb push su /system/bin or try adb push su /system/bin/su
6. - adb reboot
7. reboot twice, and if this don't work then please leave a comment and I will explain a new way.
ATTENTION
2nd way to try to root
1. On your computer make sure you have adb access ( usually just install android sdk )
2. Make sure you have HTC drivers installed ( remove HTC sync after the installment )
3. With that being said download the attachment file ( I downloaded the SU from*http://androidsu.com/superuser/ )
4.read carefully
5. create a folder were the superuser.apk and Su file is and name it system and inside that make a bin folder and place the Su file in the bin folder
6.Go to the folder were you extracted root folder in the last root alternative
7.Open cmd in that folder and make sure to extract the files ( superuser.apk and Su file to the root of the root folder )
8.Type : adb devices
9. Type: adb shell
10. Type: adb install ( locate were apk is on your pc.... Here is an Example of what ide put: adb install c:/root/nameOf app.apk , then press enter )
11. Type: adb push su /system/xbin or try adb push su /system/xbin/su or try adb push system/xbin/su /system/xbin/su
12. Use the following command to add the correct permissions to the su binary on the device adb shell chmod 6755 /system/bin/su
13. Adb reboot
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!

I'll try when I get ack home tonight,
thanks for this

avid.aria said:
I'll try when I get ack home tonight,
thanks for this
Click to expand...
Click to collapse
Download a ruu to be on the safe side too... There's 2 ways on how you could root
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!

Reserved

Another reserved

Hope this helps everyone

Not working
So after we spent all that time I thought we should update people that at least for me this doesn't seem to work, even when we get the UI to break and not show anything there's still no root access. For anyone that does this and breaks the UI, mine seems to come back after locking and unlocking the bootloader. The following commands will get you back to a good state:
Reboot into fastboot mode
Make sure you have the fastboot and Unlock_code.bin (you get that from HTC dev website, you probably already have it) files in the same directory and:
fastboot oem lock
Device reboots, go back to fastboot
fastboot flash unlocktoken Unlock_code.bin
To unlock it again, then it should restart and be factory reset, which works for me to get it functional again. Hope that helps.

8trix said:
So after we spent all that time I thought we should update people that at least for me this doesn't seem to work, even when we get the UI to break and not show anything there's still no root access. For anyone that does this and breaks the UI, mine seems to come back after locking and unlocking the bootloader. The following commands will get you back to a good state:
Reboot into fastboot mode
Make sure you have the fastboot and Unlock_code.bin (you get that from HTC dev website, you probably already have it) files in the same directory and:
fastboot oem lock
Device reboots, go back to fastboot
fastboot flash unlocktoken Unlock_code.bin
To unlock it again, then it should restart and be factory reset, which works for me to get it functional again. Hope that helps.
Click to expand...
Click to collapse
Me and you will work on finding a way
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!

but there is no support for unlocking the bootloader in htc dev , how did you do it ??

Both methods will not work.
1st method is designed for the Droid Incredible 4G LTE, not this phone.
2nd method requires to be rooted before you can even push files to the system folder.

hasoon2000 said:
Both methods will not work.
1st method is designed for the Droid Incredible 4G LTE, not this phone.
2nd method requires to be rooted before you can even push files to the system folder.
Click to expand...
Click to collapse
Yeah me and 8trix found this out.... We need a temp root or We need a costom recovery. And I have no experience on that
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!

lateral18 said:
but there is no support for unlocking the bootloader in htc dev , how did you do it ??
Click to expand...
Click to collapse
To unlock the bootloader is easy, its like any other htc. Go to htc dev site and choose "all other supported devices" and follow the guide. It'll give you the file to fastboot flash to unlock. We're just working on getting root now. HTC definitely did something different with this phone because none of the other methods seem to work. Seems like there are some smart dedicated people working with us so please be patient and keep a watch on this thread!

lateral18 said:
but there is no support for unlocking the bootloader in htc dev , how did you do it ??
Click to expand...
Click to collapse
Yes there is. Re check
---------- Post added at 06:07 AM ---------- Previous post was at 05:59 AM ----------
24ky said:
Yeah me and 8trix found this out.... We need a temp root or We need a costom recovery. And I have no experience on that
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!
Click to expand...
Click to collapse
I tried to help my friend before he brought it back his htc to [email protected] cuz he bricked his phone. I unlocked bootloader and tried to flash recovery with HTC ONE V recovery thinking it would be similar. It did brick my phone with a warning on boot though i flashed the recovery again with the recovery in sdk platform tools and no longer brick. I know this might not be useful though i think u can flash the recovery with different recovery's till u find one that works with htc one v x just use htc models. Also the ruu is out where is the link ?

flipinfin said:
Yes there is. Re check
---------- Post added at 06:07 AM ---------- Previous post was at 05:59 AM ----------
I tried to help my friend before he brought it back his htc to [email protected] cuz he bricked his phone. I unlocked bootloader and tried to flash recovery with HTC ONE V recovery thinking it would be similar. It did brick my phone with a warning on boot though i flashed the recovery again with the recovery in sdk platform tools and no longer brick. I know this might not be useful though i think u can flash the recovery with different recovery's till u find one that works with htc one v x just use htc models. Also the ruu is out where is the link ?
Click to expand...
Click to collapse
With ruu all will be fixed
Sent from my Incredible 4G LTE using xda app-developers app

jose51197 said:
With ruu all will be fixed
Sent from my Incredible 4G LTE using xda app-developers app
Click to expand...
Click to collapse
I wish that were true lol. I cant seem to get the ruu to run all the way even on an xp machine. I think once it finished sending but then errored out right after.
I have flashed a bunch of random recoveries and nothing seems to work, but none have bricked my phone, my recovery just doesn't work. If someone could decrypt the rom.zip from the ruu that would be awesome and we could make custom recovery from that right?
Ruu:
http://forum.xda-developers.com/showthread.php?t=2097438
If that doesnt work (looks like its not there), i have already extracted the encrypted rom.zip and put it on my web server here:
Http://pnxcloud.com/rom.zip

8trix said:
I wish that were true lol. I cant seem to get the ruu to run all the way even on an xp machine. I think once it finished sending but then errored out right after.
I have flashed a bunch of random recoveries and nothing seems to work, but none have bricked my phone, my recovery just doesn't work. If someone could decrypt the rom.zip from the ruu that would be awesome and we could make custom recovery from that right?
Ruu:
http://forum.xda-developers.com/showthread.php?t=2097438
If that doesnt work (looks like its not there), i have already extracted the encrypted rom.zip and put it on my web server here:
Http://pnxcloud.com/rom.zip
Click to expand...
Click to collapse
Did you relock before flashing ruu?
Sent from my HTC EVARE_UL using xda premium

jmztaylor said:
Did you relock before flashing ruu?
Sent from my HTC EVARE_UL using xda premium
Click to expand...
Click to collapse
I know this is old and not needed anymore since you're putting up root tomorrow, but I wanted to close this with yes, I did re-lock, and it kind of almost worked, like it finished sending the file, but then errored out with some other bs. No woory now though, I am back to fully stock unlocked and will test your root tomorrow if it's up then. Thanks again jmz, great work!

So... how do I get the UI working again? I'm stuck with an unusable UI ._. !

zeratos said:
So... how do I get the UI working again? I'm stuck with an unusable UI ._. !
Click to expand...
Click to collapse
Whats wrong?

None of the methods described on the main post work and I got stuck on the unusable UI, I google how to do a factory reset and now it's working again.
Thanks.
Also, is there a way to root this thing?

[how to] remove your "tampered" banner

if you have recently s-off'ed using a java card,or some other exploit that did not remove your tampered banner from the bootloader screen,then this thread is for you.
you do NOT need to downgrade your hboot. this simple adb command works without any scary hboot downgrades.
*you must be s off.
*you must have superuser installed(see this thread if you need help installing superuser)
read this:
this will not work if your s on
the usual disclaimers:
use this info at your own risk. if it melts your phone into a little pile of aluminum goo,its not my fault.
credits
-beaups for giving me the echo comand,so yall didnt need to dump,edit with a hex editor,and copy back
[email protected] for testing it
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "tampered flag"
enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify tamered is gone

mine

Disregard, I figured it out...

Any way to remove the unlocked tag?

santod040 said:
Just wanted to say thanks for this and all your helpful posts about the forums. (as always)
I also wanted to ask your opinion on the Regaw Mod Customizer.
Following the steps for creating a plugin, I made one in Visual Studio as directed for hboot 1.54.
However, when I place newly built .dll, made using our hboot and info.txt, in the directory with the customizer, it fails to see any plugins...?
Any thoughts or suggestions? I can move this elsewhere if need be as well.
Seemed here was as good a place as any though.
I didn't wanna make a thread for a broken plugin, but would like to get it done.
I also asked in the Dev's thread :fingers-crossed: and uploaded my not yet working for me/broken? plugin for him.
Just thought maybe you might have some input, maybe not.
No worries either way and thanks again.
Click to expand...
Click to collapse
your quite welcome,glad to help as always.
while i do get the desire to customize all aspects of ones device,im not a fan of the bootloader modifier for a couple simple reasons:
-it carries a certain amount of risk.no matter how small,i just dont think folks should mess with the bootloader too much since its such an important piece of firmware.
-some folks are using it to decieve their carriers about being s on and locked,rather than taking the time to restore to stock correctly.
so unfortunately,no ideas or suggestions for you there,lol. ive never messed with it and have no idea how it works.

GrayTheWolf said:
Any way to remove the unlocked tag?
Click to expand...
Click to collapse
I think Scotty can help you put it back to "locked" if you want
Sent from my HTC6500LVW using XDA Premium 4 mobile app

GrayTheWolf said:
Any way to remove the unlocked tag?
Click to expand...
Click to collapse
yup!
http://forum.xda-developers.com/showthread.php?t=2470340
assuming you want it to read locked and not gone entirely

scotty1223 said:
yup!
http://forum.xda-developers.com/showthread.php?t=2470340
assuming you want it to read locked and not gone entirely
Click to expand...
Click to collapse
Sorry, that's what I meant. I want to look as stock as possible in case I have another radio mishap.
But does that completely relock the bootloader, or just reset the flag?

Pretty sure stock has a locked flag
Sent from my Stock, Locked Down HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button

GrayTheWolf said:
Sorry, that's what I meant. I want to look as stock as possible in case I have another radio mishap.
But does that completely relock the bootloader, or just reset the flag?
Click to expand...
Click to collapse
well,both. its NOT a patched or hex edited hboot.
hboot checks mmcblk0p3 to see what the status is. if it finds 00 00 00 00 then it keeps itself locked,allows no access,and displays locked. if it finds HTCL,same scenario,but it displays relocked. finding HTCU it will allow access to boot,system,and recovery and display unlocked
when you first flash unlock_code.bin,the flag is set to HTCU
when you enter fastboot oem lock the flag is set to HTCL,and is not accessible while s on. so once youve unlocked while s on,someone can always tell.
even while s off,there is no "naturally occuring" situation(like running an ruu) that can change the lock flag back to stock locked,as p3 is not a block that is updated,and no other scenarios other than flashing unlock_code.bin or entering fastboot oem lock will set the flag.
the command is resetting the flag in p3 to 00 00 00 00,wich is just like it came from the factory. no tricks or false banners,its now 100% from the box stock
hope that clears it up

Thanks for that little bit of insight Scotty.
Sent from my HTC6500LVW using XDA Premium 4 mobile app

scotty1223 said:
well,both. its NOT a patched or hex edited hboot.
hboot checks mmcblk0p3 to see what the status is. if it finds 00 00 00 00 then it keeps itself locked,allows no access,and displays locked. if it finds HTCL,same scenario,but it displays relocked. finding HTCU it will allow access to boot,system,and recovery and display unlocked
when you first flash unlock_code.bin,the flag is set to HTCU
when you enter fastboot oem lock the flag is set to HTCL,and is not accessible while s on. so once youve unlocked while s on,someone can always tell.
even while s off,there is no "naturally occuring" situation(like running an ruu) that can change the lock flag back to stock locked,as p3 is not a block that is updated,and no other scenarios other than flashing unlock_code.bin or entering fastboot oem lock will set the flag.
the command is resetting the flag in p3 to 00 00 00 00,wich is just like it came from the factory. no tricks or false banners,its now 100% from the box stock
hope that clears it up
Click to expand...
Click to collapse
So I wouldn't be able to do fastboot commands over ADB.

GrayTheWolf said:
So I wouldn't be able to do fastboot commands over ADB.
Click to expand...
Click to collapse
correct. being unlocked lets you use fastboot flash partition imagename.img and fastboot boot imagename.img ,but only for boot,system and recovery,so their useage is pretty limited. you still cant fastboot flash a radio,hboot,splash screen etc.
its not a terribly big deal,you just need to install things in RUU mode,using the fastboot flash zip zipname.zip command. so you can still do everything you could with an unlocked bootloader,you just have to go about it a bit differently.
alternately,beaups new method will possibly include a patched hboot,wich will let you fastboot flash all partitions(tho still not give you all the eng commands)
since its easy enuff to make it locked again,i keep mine unlocked. but it honestly doesnt matter much.

This worked perfectly! Thanks, scotty!

Thanks I can use this now that s-off is available.

thanks guys this worked awesome . love all the help you can get here !

Thank you! Hated that tampered badge.

Thanks much! worked great!

Worked for me, thanks!

Thanks for posting this method, it worked great for me.