[how to] lock/unlock your bootloader without htcdev(s-off required) - HTC One Max

this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock.
originally,we used a zip file flashable in recovery. i have found it to work on gsm m7_ul devices with 1.44 hboot and CW recovery. it did not work with twrp. if the following is too scary,feel free to test the zip files. that thread,info,and downloads can be found here. since not all recoverys are working,these values can be changed with simple adb commands.
advantages
-no hassle with htcdev,tokens,or unlock codes
-no submitting your phones personal info to htc
-the ability to get back to 100% stock without any visual traces or records of having been s off or unlocking your bootloader.
prerequsites
*you must be s off.
*you must have superuser installed(see this thread if you need help installing superuser. use the keep bootloader locked directions)
read this:
this will not work if your s on. its not a way to magically unlock
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.
it has been successfully tested on t6ul with MID 0P3P51000. i feel it is safe for other t6ul users,all MIDs,however,you are welcome to dump and we can verify the flag locations if you have concern.
if you have a different variant than t6ul,please pm me for more info prior to trying this.
credits
-beaups for giving me the echo comand,so yall didnt need to dump,edit with a hex editor,and copy back
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
-kdj67f for fearlessly testing on vzw m7_wlv and putting up some screenshots in post 2. thanks!
-matthew0776 for fearlessly testing for sprint m7_wls
*pradeepvizz for getting the ball rolling for t6 users-dumping partitions,testing commands and providing screenshots. make sure to give him a big thanks
*[email protected] for testing on sprint t6
*droidrev71 and oneandroidnut for testing vzw t6
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 "lock status flag"
to LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(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 you are now locked
_____________________________________________________________________________________________
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(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 you are now unlocked
Please Note:
*you must remove the tampered banner as well in order for the fingerprint scanner to work.
remove your tampered banner

This looks great! few quick questions before i attempt it. So will this let me get root and use of the finger print scanner? say if i unloocked installed custom recovery root all that, then relocked would the finger print scanner work? thanks very much!!!!

hectorz321 said:
This looks great! few quick questions before i attempt it. So will this let me get root and use of the finger print scanner? say if i unloocked installed custom recovery root all that, then relocked would the finger print scanner work? thanks very much!!!!
Click to expand...
Click to collapse
yes thats right.. i have got a custom recovery, root and a custom rom as well and i have LOCKED and also removed TAMPERED banner and i can use my fingerprint scanner happily
Thanks scott!! that was really quick work from you! i am glad that i choose to PM you and requested this!

hmmmm by looks of it you have to unlock with htc dev first to get s off, trying to install custom recovery without bootloader ulocked gives you an error
C:\max>fastboot flash zip recovery.zip
target reported max download size of 1554698240 bytes
sending 'zip' (7553 KB)...
OKAY [ 1.143s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.944s

hectorz321 said:
hmmmm by looks of it you have to unlock with htc dev first to get s off, trying to install custom recovery without bootloader ulocked gives you an error
C:\max>fastboot flash zip recovery.zip
target reported max download size of 1554698240 bytes
sending 'zip' (7553 KB)...
OKAY [ 1.143s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.944s
Click to expand...
Click to collapse
correct. youll need to be s off to install recovery as a zip file while locked.
custom made recovery zips do not have htc's official signiture required for s on flashing.

Can verify that this works to get fingerprint scanner working again on uk version of htc one max great work

I can also confirm that the unlock command works.. both of them works!
---------- Post added at 04:08 AM ---------- Previous post was at 04:04 AM ----------
@scotty1223 Will i need to UNLOCK in order to flash a zip from recovery? i am trying to flash elementx kernel zip which contains a zip file..

pradeepvizz said:
[/COLOR]@scotty1223 Will i need to UNLOCK in order to flash a zip from recovery? i am trying to flash elementx kernel zip which contains a zip file..
Click to expand...
Click to collapse
nope. should not have to. once youre s off,the normal unlock rules go out the window.
the ONLY reason you would have to be unlocked is if you wanted to use fastboot flash to install a recovery or kernel,or to use fastboot boot to temporarily boot a recovery.
zip files in recovery,or ruu zip files flashed from fastboot/ruu mode do not need the bootloader unlocked

scotty1223 said:
nope. should not have to. once youre s off,the normal unlock rules go out the window.
the ONLY reason you would have to be unlocked is if you wanted to use fastboot flash to install a recovery or kernel,or to use fastboot boot to temporarily boot a recovery.
zip files in recovery,or ruu zip files flashed from fastboot/ruu mode do not need the bootloader unlocked
Click to expand...
Click to collapse
Thanks Scott! i was trying to install flar2's elementalx's kernel from the One on our MAX and was getting bootloops sometimes and i was not sure if the kernel was installed..
I did try to install once with LOCKED and UNLOCKED.. the phone kept bootlooping ..

Tried it on my butterfly s and it worked too
Sent from my HTC Butterfly s using xda premium

for me it didnt work
i was unlocked via htc dev... locked it again and unlocked it with
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
but fingerprint sensor does not work ...
i have a german o2 phone !

B-Man2005 said:
for me it didnt work
i was unlocked via htc dev... locked it again and unlocked it with
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
but fingerprint sensor does not work ...
i have a german o2 phone !
Click to expand...
Click to collapse
deleted
---------- Post added at 02:15 PM ---------- Previous post was at 02:12 PM ----------
have you removed your tampered flag as well?

B-Man2005 said:
for me it didnt work
i was unlocked via htc dev... locked it again and unlocked it with
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
but fingerprint sensor does not work ...
i have a german o2 phone !
Click to expand...
Click to collapse
You must leave it locked. The phone is reacting to finding htcu
Sent from my HTC PG09410 using Tapatalk 2

daorderdillon said:
Tried it on my butterfly s and it worked too
Sent from my HTC Butterfly s using xda premium
Click to expand...
Click to collapse
again,not a good idea without any knowedge of what was in that spot.

Thanks Scotty . Worked great on my Sprint Max .I'm also s-off , rooted and using fingerprint scanner ??
Sent from my HTC0P3P7 using Tapatalk

scotty1223 said:
again,not a good idea without any knowedge of what was in that spot.
Click to expand...
Click to collapse
Don't forget to bring some other tricks to us too
Sent from my HTC Butterfly s using xda premium

Now is the time for everyone who has not donated to the great devs we have to break out their paypal! This initial great group of devs are helping us all out by creating a foundation for rom/kernel/whatever devs to provide us their magic from now on. Without these guys laying the framework none of that would be possible. Remember that we are very lucky that this mostly obscure device is getting the fabulous development support it is at this time. So show your support and DONATE!!

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
Click to expand...
Click to collapse
How do I enable USB debugging on my phone? I can't seem to find it in settings.

mustasusi said:
How do I enable USB debugging on my phone? I can't seem to find it in settings.
Click to expand...
Click to collapse
go to settings/about/software information/more/ and keep pressing build number until it says u r now a developer

daorderdillon said:
go to settings/about/software information/more/ and keep pressing build number until it says u r now a developer
Click to expand...
Click to collapse
Thank you very much +1!
They hid it well on 4.3...

Related

[Procedure]No HTC unlock downgrade HC-GB for official OTA

This procedure applies to both flyers and view
Required downloads
First download the Gingerbread RUU for your device from this thread.
If you don't have adb and fastboot on your PC
Get fastboot and adb tool for windows here
Get Fastboot and adb for linux here
I don't have a simple bundde for Mac, would welcome a link if anyone has one.
Download my universal misc_version and unzip to obtain the misc_version file.
Download tacoroot
Place both the misc_version and tacoroot.bin files in the same directory as adb
Procedure
Check the version number for your gingerbread RUU
In my example I am using this RUU: RUU_Flyer_HTC_WWE_2.00.405.3_R_Radio_20.3501.30.08 9BU_3809.05.04.10_M_release_194964_signed.exe
The version is the part highlighted in red.
Boot your flyer up to android if it's not already on, with usb debugging enabled and connect it to the PC.
Run the following adb commands
Code:
adb push tacoroot.bin /data/local
adb push misc_version /data/local
adb shell chmod 755 /data/local/tacoroot.bin
adb shell chmod 755 /data/local/misc_version
adb shell /data/local/tacoroot.bin --setup
At this point your device will reboot to recovery
Simultaneously press Volume Up, Volume Down and Power
Reboot your device
Run the following command
Code:
adb shell /data/local/tacoroot.bin --root
Your device will reboot, do not worry if it does not boot fully, it doesn't matter for this procedure, and it is a side effect of this root exploit.
Run the following command:
Code:
adb shell /data/local/misc_version -s [COLOR="Red"]2.00.405.3[/COLOR]
Note that the number in RED is the version number retrieved in step 1.
Reboot to fastboot:
Code:
adb reboot bootloader
Run your RUU ( if on linux or mac, see other similar threads from me on how to RUU on those OSes )
Special Thanks
jcase for providing the tacoroot.
Nice release globatron! I was actually looking at Tacoroot for this last night but didn't really want to go into it too much and decided against using it. Glad to see I wasn't the only one with the idea for it though.
heh, Gave jcase the updated misc_version so he has it on the github radme for tacoroot already but didn't want to release the procedure until I has actually tested misc_version to run on at least a few HTC emmc devices and with multiple version string lengths.
Even if you didn't release this today, I probably would have started on it tonight, I'm a bored teenager with too much time. Still, keep up the good work. If you want me to make a script for you or anything, let me know and I'll get to work on it. (also, you know you can actually have adb from the recovery so you dont need to hit the buttons on it, just have it wait then adb reboot (or even adb shell reboot))
Of course I know that but that's not the what the buttons is about here.
What are the points of the button?
Sent by breaking the sound barrier
To ensure with absolute certainty that a log will be created.
Ah, you want the button presses to be logged to ensure it's done the job. Alright, fair enough.
Glad to TacoRoot in use!
Thanks for the spice jcase, just realized I had a typo in the procedure....jcase *provided*, not tested (well that too), tacoroot.
globatron said:
Thanks for the spice jcase, just realized I had a typo in the procedure....jcase *provided*, not tested (well that too), tacoroot.
Click to expand...
Click to collapse
is the typo msc_version being misc_version
thanks Kevin, fixed that.
yep, didnt notice it until someone tried to do my procedure today lol... copy and paste my friend lol. Plus I just need to know one thing. This brings you down to GB but still keeps you locked right? You still technically have to use HTC unlock to bring it back to 1.13.000 correct?
Part1: correct, you've never unlocked if you do this.
Part2: No, you don't have to unlock at all during this procedure.
so to go from the 1.14 hboot to 1.13 u dont need to htc unlock?
kevinrocksman said:
so to go from the 1.14 hboot to 1.13 u dont need to htc unlock?
Click to expand...
Click to collapse
That's correct.
globatron said:
This procedure applies to both flyers and view
Required downloads
First download the Gingerbread RUU for your device from this thread.
the download link takes me to the flyer RUU, i understand the view & flyer are the same except the 3g/4g network on the View. i just want to make sure i download the correct RUU for my View. what verision do i need? this one "RUU_Express_Sprint_WWE_1.22.651.1_Radio_1.05.11.0531_NV_2.28_SPCS_release_198141_signed.exe"
agian thank you for the support
Click to expand...
Click to collapse
That one is fine. Express is the board name or the view so an RUU with express (not expresskt) in the name is what you need.
Hello, thanks for the downgrade help. Upgraded to honeycomb and hated it so I followed your instructions and everything went exactly as described until the middle of the RUU upgrade itself where it stopped and gave me an
ERROR[140]: BOOTLOADER VERSION ERROR
The ROM Update utility cannot update your android phone
Please get the correct ROM update utility and try again.
It won't successfully reboot now. When I go back to bootloader mode the recover screen shows
*** LOCKED ***
express pvt ship s-on rl
hboot-1.14.0005
microp-0656
radio-1.05.01.1006_3
emmc-boot
oct 25 2011, 16:35:13
used RUU_Express_Sprint_WWE_1.22.651.1
Its completely stock, was notified of the new update by htc and installed it over wifi. Thanks in advance for any help
What appears to have happened here is that somewhere along the way something didn't work fully and you failed to set the version to the same as or lower than the RUU you used.
I would need to see the output of :
Code:
fastboot getvar version-main
to be absolutely certain of this. If that is the case then becasue you are completely stock the best course of action would be for you to return it for repair. Tell the technical support people that this happened when you tried to take the OTA update to HoneyComb. The alternative will require you to use the HTC unlock.

[Q] Hboot 1.5 Evo3D Root Help

Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
navenine said:
Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
Click to expand...
Click to collapse
Try this, starting over. You shouldnt run into any hiccups.
tailsthecat3 said:
Try this, starting over. You shouldnt run into any hiccups.
Click to expand...
Click to collapse
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
navenine said:
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
Click to expand...
Click to collapse
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
tailsthecat3 said:
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
Click to expand...
Click to collapse
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
hey im trying to use the ruu to get back to stock , just re locked the phone , and im STILL getting errors with ruu, its saying Update Failed : Hboot version is older , im on hboot 1.5000 .........Im losing my mind trying to get this thing back to stock and out of htc screen logo bootlooping.........any ideas?
navenine said:
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
Click to expand...
Click to collapse
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
tailsthecat3 said:
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
Click to expand...
Click to collapse
this just got even worse, I uninstalled the drivers, and now I can't reinstall them. I can't find them. My computer wont recognize my phone at all. I've tried to goto the device manager and find them online automatically, and I've tried the google USB drivers from the extra folder from the SDK Manager...
if you can point me toward the USB drivers that'd be great, but regardless, what your saying is I need to connect my phone while its in the bootloader? not once its booted? or are you saying I need to boot my phone through the bootloader selecting "fastboot" first?
thanks again
-Nave
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
navenine said:
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
Click to expand...
Click to collapse
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
I pushed everything over, got it into the fastboot USB and then typed the "fastboot flash recovery recovery.img" command line
my script was:
sending 'recovery' <5068 KB>...
Okay [ 1.207s]
writing 'recovery'...
<bootloader> signature checking...
FAILED <remote:signature verify fail>
finished. total time: 1.855s
any ideas?
tailsthecat3 said:
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
Click to expand...
Click to collapse
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
navenine said:
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
Click to expand...
Click to collapse
Where were you going wrong? And what'd you do to correct it? So everyone knows, in case they encounter the same issues.
Sent from my Google Nexus S 4G via XDA Premium
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
navenine said:
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
Click to expand...
Click to collapse
I appreciate that, thank you.

[Q] [Flyer] Several questions about downgrading to Gingerbread

Hey guys,
beforehand: I'm totally new to this topic, so please be patient.
I got my HTC Flyer Wifi & 3G [P510e] back from reparation and the guys there also updated my Flyer to Honeycomb (3.2.1). Since I cannot use my touch buttons anymore, I would like to do a downgrade to Gingerbread again.
I've searched here and found this topics:
http://forum.xda-developers.com/showthread.php?t=1428104
http://forum.xda-developers.com/showpost.php?p=19607833&postcount=3
Now I'm not sure what to do: do I need to S-OFF my Flyer to make a downgrade, like shown in the following thread?
http://forum.xda-developers.com/showthread.php?t=1358758
Which Gingerbread-Version do I have to use, how can I find that out? And where do I get it from?
And the most important thing: what is the worst thing that could happen if I mess up something?
My Flyer is currently S-ON, my HBOOT-Version is HBOOT-1.11.0011 (see attached file) and it's a german version, if that is important to know.
I would appreciate it if someone would help me with this. Normally I'd ask my ex-boyfriend to do this for me, but since we broke up, I want to manage this kind of stuff on my own. :fingers-crossed:
Katzenmuetze said:
Hey guys,
beforehand: I'm totally new to this topic, so please be patient.
I got my HTC Flyer Wifi & 3G [P510e] back from reparation and the guys there also updated my Flyer to Honeycomb (3.2.1). Since I cannot use my touch buttons anymore, I would like to do a downgrade to Gingerbread again.
I've searched here and found this topics:
http://forum.xda-developers.com/showthread.php?t=1428104
http://forum.xda-developers.com/showpost.php?p=19607833&postcount=3
Now I'm not sure what to do: do I need to S-OFF my Flyer to make a downgrade, like shown in the following thread?
http://forum.xda-developers.com/showthread.php?t=1358758
Which Gingerbread-Version do I have to use, how can I find that out? And where do I get it from?
And the most important thing: what is the worst thing that could happen if I mess up something?
My Flyer is currently S-ON, my HBOOT-Version is HBOOT-1.11.0011 (see attached file) and it's a german version, if that is important to know.
I would appreciate it if someone would help me with this. Normally I'd ask my ex-boyfriend to do this for me, but since we broke up, I want to manage this kind of stuff on my own. :fingers-crossed:
Click to expand...
Click to collapse
if you are not s-off now,then your 2nd and third links are not really of any use.
depending on wether you want to use htcdev for root,or a temporary root exploint you need to use either this thread:
http://forum.xda-developers.com/showthread.php?t=1307759 (for htcdev)
or your first link:
http://forum.xda-developers.com/showthread.php?t=1428104
the disadvantage to htcdev for root,is that it will leave a watermark that shows you have unlocked the bootloader,and as the unlock website states,this could void "all or parts of your warranty"
the disadvantage of the other link,is that the root exploit(taco root) is kind of a funky exploit,and while safe, is a little tricky to use if youre not used to doing things like this.
after you have downgraded to gingerbread,you can use revolutionary to s-off( http://revolutionary.io/ ) this leaves the door open to upgrade to honeycomb with s-off later,if you desire. it will also let you install a custom recovery,and add root access so that you can modify the stock gingerbread rom,or flash a custom GB rom, so that you can continue to operate on GB without pesky OTA notifications.
last and not least,if you cannot find a GB ruu that supports your CID (carrier identification) you will need a goldcard to downgrade to a different carrier or unbranded RUU. (directions to make a gold card: http://www.addictivetips.com/mobile...-gold-card-for-htc-desire-without-hex-editing)
just holler if you have further questions.
if you decide to go the htcdev route,i have a guide with some download links that may simplify that process somewhat for you,and can reproduce it here if you desire.
scotty1223 said:
if you decide to go the htcdev route,i have a guide with some download links that may simplify that process somewhat for you,and can reproduce it here if you desire.
Click to expand...
Click to collapse
That would be great, thank you.
TSGM said:
That would be great, thank you.
Click to expand...
Click to collapse
sorry for the delayed reply.
here is my "htcdev" guide:
i sometimes refer folks to my rezound guide in other forums,so i decided to make a slightly more "universal" version that i could replicate in other forums,so everyone has a dedicated guide,and there are not accidents with accidental application of rezound specific details or files. devices i am familiar with i will try and tweak and add device specific recovery downloads/info. whatever device youre working on,please feel free to post in this thread,i will be happy to assist you
before we get started,however,be aware that htcdev does have its limitations. it can be used if you only wish to add root access to delete bloat and run a few root requiring apps,but IMO it is best used as a "steppig stone" to get root for downgrade,or for other exploits to run. if s-off is availble on any "downgradeable to" firmware,i do highly recomend to try and achieve that goal if you wish to activly flash roms. im happy to help with this,as well,if needed.
the basic steps will be:
1)unlock with htcdev
2)temporarily or permanently flash a recovery
3)flash root files
before you start,go ahead and download these files:
-mini-adb.zip: mini-adb.zip
-the latest custom recovery image of your choice, for your device(for the flyer,use http://hyuh.net/files/flyer/downgrade/recovery.img md5 bb366b025dcc454ffe8b21b8bf0c72d0)
-superuser files: for froyo use superuser 3.07 (found on revolutionary public wiki). for GB,HC or ICS,use the latest superSU from this thread on xda (the download link is where is says: CWM installable ZIP: CWM-SuperSU-v0.96.zip )
-go to HTCdev - Unlock Bootloader and register an account
1)unlock with htcdev
first thing you need is drivers for adb to see your phone. 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
most guides simply say "follow the directions to unlock with htcdev" but im gonna go thru it with ya the mini-adb.zip file is all the files that htcdev is telling you to download and put into a folder,so allready this should be a lil easier
1)prepair ADB
-unzip your mini-adb.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(sorry, you mac guys will need to develop this for yourself,i dont have a mac). 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 "mini-adb_devicename" since youll be putting some device specific files in here. (directions from here forward will assume this folder to be named "mini-adb_vigor",as an example)
-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 mini-adb_vigor directory. type the following at the prompt in your cmd window:
cd c:\mini-adb_vigor
your command promt should change to "c:mini-adb_vigor>" provided you: 1)unzipped the miniadb zip 2)put the folder on your c drive 3)entered the name of the folder correctly ("mini-adb_vigor" in this case)
-now make sure usb debugging is checked in settings/apps/development,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.
2)unlock using htcdev
-go to HTCdev - Unlock Bootloader and sign in to your account. chose your device from the "select your device bar"(or "other supported devices" if its not listed) and click the green "begin unlock bootloader" button underneath.
-click yes to procede,then read the warnings before checking the boxes and clicking yes to continue,as they are basically explaining that your warranty is now void,and any repairs that your phone needs that may have been a result of unlocking your bootloader and messing with your phones operating system may no longer be covered under mfgr warranty
*check your hboot screen. if you allready have an htc compatible hboot, then skip ahead to the next step,you dont need this.if you have a pink **locked** at the top of the hboot screen,then it is compatible with htcdev. if you dont have a compatible hboot,then download the RUU for the new hboot. right click it,and run as administrator. plug in your phone when prompted to. it will ugrade your hboot to the htcdev unlock compatible version.
-steps 1-4 are describing how to get your phone into bootloader mode and connect it to your PC,wich we have done above. ignore these steps and simply type in your cmd window:
adb reboot bootloader
it may take several seconds,but this command should boot your phone into the "fastboot" screen wich is white with a bunch of colored writing. once this happens,make sure your phone is still being seen in fastboot. type:
fastboot devices
again,this should return your phones serial number.
-click the green procede to step 5 bubble.
-steps 5-7 are telling you how to find the files and utilities inside your mini-adb folder. you have them,so ignore steps 5-7.
-click the green procede to step 8 bubble.
-heres where steps are important,steps 8-10 are telling you how to get your unlock token,and send it to htc. its phone specific(so they prolly know your serial number,meid,etc) so no,you cant use your buddys unlock token and not have htc know that youve unlocked your bootloader. copy this line either from below,or from step 8,and paste it into the prompt in your cmd window. you have to right click to paste in cmd,you cannot control/v :
fastboot oem get_identifier_token
-after yuo hit enter,you will get a bunch of letters that are your identifier token. not much i can say,other than follow the directions in steps 9 and 10 to copy and submit your identifier token to HTC. make sure you get the characters as shown in the pic,with no extra lines or letters. note that you can also hit the "enter" key on your PC to copy,as well as right clicking.
-click the green submit button. wait patiently for an email containing your unlock code. (dont worry,it should come pretty fast )
-save the unlock_code.bin that htc sends you directly to your mini-adb folder(if your PC automatically downloads somewhere else,no biggie. just move the unlock code to mini-adb folder)
-click the link in your email to get the rest of the unlock instructions
-step 12 is where them magic happens copy from below,or from htc dev:
fastboot flash unlocktoken Unlock_code.bin
-youll see the purdy screen pictured in step 13. use the vol rocker to chose "yes unlock bootloader" and select it with the power button. your phone will reboot,performaing a factory data reset in the process. your data is gone,sorry this boot may take a bit longer than they normally do,dont freak out this is normal
as you can see,once the adb files are put in one place to download,its not hard to use,and the commands are pretty simple. below is what you will see in your command window,the red are my inputs.
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:UsersScott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
c:mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx device
c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx fastboot
c:mini-adb_vigor>[COLOR="red"]fastboot oem get_identifier_token[/COLOR]
... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
INFO2ADC7C0C0F1BAF92074BAE9B0035CB6A
INFO021839BFA7465CD0788664688DCCFDEA
INFO33A2FD2C96C7308DD3C57A517DBA8E14
INFO8048F98A9FEA06B8F2AD05D4D3497CFE
INFO6FCCC1DC4E31E0C6F54CEA18D9A80C82
INFO27C33E209D472E6C11753E9D7BCBCE6D
INFO90D9F226E827B6C26165A029B6F7DFF2
INFO63E382B4C82F9F6D866C01B9823ED1BC
INFO0EEFA859327E6B5AC4C24533C9DFA7AF
INFODBD70D55E4666B4B41828B76FFBD010C
INFO1B916E350EFF199EA5B096FF3337FE19
INFO40E6CA9E7F1DD5B33D8D4780DD775289
INFO953404686AEC4C3CB6F1BBB9DC69BA13
INFO8738C00DAFF280ECF02D0C7A66E13855
INFO1D756616732FF47915EAD551A6933E08
INFO10C541C7RD02C14991E83CC49FCA4B92
INFO<<<<< Identifier Token End >>>>>
OKAY [ 0.069s]
finished. total time: 0.070s
c:mini-adb_vigor>[COLOR="red"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
sending 'unlocktoken' (0 KB)... OKAY [ 0.143s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.011s]
finished. total time: 0.156s
c:mini-adb_vigor>
2)flash a recovery
if you want to run stock,do not permanently install your recovery. keeping the stock recovery on the phone will ensure that you recieve OTAs without a hitch,wich i know is important to alot of users. YES,the OTA will break root. its no big deal. one good thing about htcdev is that you will always be able to reroot after,simply by following steps 2 and 3 again to launch recovery,flash superser.
once youve either skipped past all the setup,or have re-set up and are ready to root,chose either of the following options to either permantly or termporarily install a recovery:
1)temporary recovery:
-move the recovery image file you downloaded above and place it into the mini-adb folder.
-put the superuser zip file onto your phones sd card
-enable usb debugging once again,as above. open a cmd window,if its not still open from unlocking.
-if you had to re-open a cmd window,dont forget to change back to your mini-adb directory:
cd c:\mini-adb_vigor
-make sure youre connected by typing:
adb devices
-should return serial number
-check the md5 of your recovery image:
md5sums <recoveryname>.img
**make sure the resulting md5 matches the one that is listed for the image that you downloaded. ** (if no md5 is listed,post in the thread,i can download and compare my md5 to yours.this is not as good as getting an md5 from the one who linked the file,but its better than nothing)
-boot to bootloader:
adb reboot bootloader
-check for connectivity:
fastboot devices
-should return serial number
-temporarily launch your recovery to phone memory:
fastboot boot <recoveryname>.img
-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone. youll then see the HTC splash screen,then your recovery.
in your command window you will see(red are my inputs):
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:UsersScott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
c:mini-adb_vigor>[COLOR="Red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx device
c:mini-adb_vigor>[COLOR="red"]md5sums recovery-ra-vigor-3.14-gnm.img[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:mini-adb_vigor]
recovery-ra-vigor-3.14-gnm.img 915d5e3cb662076f36f3d6e54759e951
c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx fastboot
c:mini-adb_vigor>[COLOR="red"]fastboot boot recovery-ra-vigor-3.14-gnm.img[/COLOR]
downloading 'boot.img'... OKAY [ 1.518s]
booting... OKAY [ 0.005s]
finished. total time: 1.523s
2)permanently install your recovery
-move the image file you downloaded above and place it into the mini-adb folder.
-enable usb debugging once again,as above. open a cmd window,if its not still open from unlocking.
-if you had to re-open a cmd window,dont forget to change back to your mini-adb directory:
cd c:\mini-adb_vigor
-make sure youre connected by typing:
adb devices
-should return serial number
-check the md5 of your recovery image:
md5sums <recoveryname>.img
**make sure the resulting md5 matches the one that is listed for the image that you downloaded. ** (if no md5 is listed,post in the thread,i can download and compare my md5 to yours.this is not as good as getting an md5 from the one who linked the file,but its better than nothing)
-boot to bootloader:
adb reboot bootloader
-check for connectivity:
fastboot devices
-should return serial number
-permanently flash your recovery to phones recovery partition:
fastboot flash recovery <recoveryname>.img
-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone,then a (really,really fast) red bar as it flashes it. amon ra is now permanently on your phone when you need it. be aware that you can no longer accept OTAs,unless you reinstall the stock recovery at some point before the next OTAs are pushed.
-to get to recovery,push the power button to select hboot. once in hboot wait for the green writing to flash and disapear,then select recovery.
*note that you can still launch recovery by using the command from scenario 1 above.
-youll then see the HTC splash screen,then your recovery.
and the code(again,red my inputs):
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:UsersScott>[COLOR="red"]cd c:\mini-adb_vigor[/COLOR]
c:mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx device
c:mini-adb_vigor>[COLOR="red"]md5sums recovery-ra-vigor-3.14-gnm.img[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:mini-adb_vigor]
recovery-ra-vigor-3.14-gnm.img 915d5e3cb662076f36f3d6e54759e951
c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx fastboot
c:mini-adb_vigor>[COLOR="red"]fastboot flash recovery recovery-ra-vigor-3.14-gnm.img[/COLOR]
sending 'recovery' (7074 KB)... OKAY [ 1.659s]
writing 'recovery'... OKAY [ 5.179s]
finished. total time: 6.840s
3)flash superuser root files*
there is not much to explain with this one. if booted to recovery from above,use the recovery menu on your phone to:
-make a backup of your stock,unrooted rom. completely optional,but a very good idea,IMO.
-wipe cache
-wipe dalvik cache
-install zip from sd card(chose your superuser file)
-reboot
*congratulations,youre rooted
if your device has procedures to s-off,or procedures to downgrade to more exploitable firmware,you can procede with that now
for the flyer we can use these directions: http://forum.xda-developers.com/showthread.php?t=1307759
after we downgrade to gingerbread,we can root with revolutionary:
http://forum.xda-developers.com/showthread.php?t=1194709
after yoou have s-off on gingerbread,you can update back to honeycomb:
http://forum.xda-developers.com/showthread.php?t=1358758&highlight=honeycomb+easy+s-off
if youre considering leaving htcdev unlock,read this if you want to flash roms: http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html
s-off is better,and worth whatever extra efforts to achieve if available.
*hope it helps,holler if you have questions
donate to my device fund
Click to expand...
Click to collapse
gave you some links at the end to downgrade,then s-off,then upgrade back to honeycome,as well as a link that may be of some value if youre considering just unlocking via htcdev and leaving it at that. htcdev is a PITA if your intent is to flash different roms,and its even more dificult as there is no other option to chagne roms other than manually installing the boot image(i have verified that fastboot booting the recovery on the flyer does NOT provide the same advantages it does on the rezound,and other htc phones.
i will be happy to help you with any questions you have about htcdev vs s-off,or with the unlock procedure. if you just want to be rooted on the stock HC rom,htcdev unlock works,but thats about it
we can also help you with the downgrade etc. after yovue completed this,but will save that for later so we dont overwhelm you with info

[TUTORIAL]Unlock your bootloader and install a custom recovery with a Mac

Want to unlock your bootloader to install a custom recovery and root your One but have no idea how because you have a Mac?
Never fear, Gunnyman is here.
The procedure is actually pretty painless and only takes a few minutes
Some prerequisites:
ADB and Fastboot binaries for OS X, I've attached them to this post.
Your recovery of choice, I'm using Clockwork Mod Recovery, because TWRP seems to have problems with some Aroma installer based ROMS. Get CWM for the One from here
SuperUser.zip
a Unix friendly text editor. I really like Text Wrangler and it's free.
Android File Transfer for Mac macs don't work with MTP mode without this.
In developer Options on the phone, turn on USB Debugging
EDIT:
Thanks to user Shivasmith I now know you can skip textwrangler and
If you hold down the "Alt" (i.e. Option) key on the Mac keyboard in terminal you can do a "column select."
So when you generate the codes for the HTCdev unlock website, you can just do a straight copy-paste without going into TextWrangler. It made it that much quicker
So thanks for the tip!
I've been using macs for 10 years and never knew that.
1. Unzip the adb and fastboot binaries and put them where you can find them. I have a directory on my Mac called /Android and that's where my phone stuff lives, but you can put it anywhere.
2. Put the cwm recovery (or twrp if you prefer) in the same folder as adb and fastboot.
3. Got to htcdev.com and create an account there if you don't already have one.
4. Log in to htcdev.com and choose unlock bootloader.
5. pick the last option for Unlisted device.
6. Open a terminal window and navigate to where you installed fastboot,adb, and your recovery eg: cd /Users/Gunnyman/Android
7. In Terminal execute the following commands ./adb reboot bootloader once in bootloader mode In terminal execute the following command: ./fastboot oem get_identifier_token
8. Open Text Wrangler
9. Copy the output from the terminal window into Text Wrangler make sure you include every line AFTER "please cut the following message"
10. Use Text Wrangler to DELETE (bootloader) from every line and make sure the columns line up exactly.
11. Copy and Paste this output into the box you are provided on HTC Dev. This part is quite annoying, getting the lines to line up.
12. Submit your token. When successful you will be sent a key via email.
13. Put the Unlock.bin file you got via email in the same directory as adb and fastboot on your mac.
14. execute the following command in terminal with the phone in fastboot mode ./fastboot flash unlocktoken Unlock_code.bin
15. Say yes to the prompts on the phone. Bootloader will unlock and the phone will be factory reset (there is NO way to avoid this)
16. OK Now the bootloader is unlocked. Time to install a recovery. In Terminal ./adb reboot bootloader
17. In terminal ./fastboot flash recovery name_of_the_recovery.img
18. After recovery has flashed POWER DOWN PHONE COMPLETELY Then restart it
19. connect phone to the Mac Android File Transfer should fire up
20. Put the Superuser.zip file on your phone
21. in Terminal ./adb reboot recovery
22. Flash the SuperUser.zip in recovery.
23. Pat yourself on the back your phone is now rooted.
great tutorial...thanks. quick question since i have the dev edition (unlock bootlader) can i just follow all these steps but go straight to # 16 to root my One?
thanks again.
Absolutely
WHEN I enter the "fastboot flash unlocktoken Unlock_code.bin i get a "denied " message in the terminal can anyone figure this out for me
What are the cons of rooting the phone and installing a custom recovery?
I know that it voids the warranty. Is there anything else besides that?
Some people reported some functions not working.
Or is that just when you install a custom ROM?
pedromartinez1983 said:
WHEN I enter the "fastboot flash unlocktoken Unlock_code.bin i get a "denied " message in the terminal can anyone figure this out for me
Click to expand...
Click to collapse
I've seen it once before. It was solved by creating a new account on HTC.dev. And getting a new key.
No cons. Rooting doesn't do anything except add access to the super user account built into the device.
gunnyman said:
No cons. Rooting doesn't do anything except add access to the super user account built into the device.
Click to expand...
Click to collapse
Thanks man
Sent from my HTC One using xda app-developers app
gunnyman said:
No cons. Rooting doesn't do anything except add access to the super user account built into the device.
Click to expand...
Click to collapse
Gunny! Good to see you made the right moves for this phone too!
Im reading stuff about att updating that wont allow to unlock bootloader? Is this true?
Sent from my HTC One using Tapatalk 2
MrPlNK said:
Gunny! Good to see you made the right moves for this phone too!
Im reading stuff about att updating that wont allow to unlock bootloader? Is this true?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Not so far.
SU keeps aborting installation when I try to install it, any ideas?
broopa said:
SU keeps aborting installation when I try to install it, any ideas?
Click to expand...
Click to collapse
Youre flashing zip from recovery?
Sent from my HTC One using Tapatalk 2
MrPlNK said:
Youre flashing zip from recovery?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yeah, from CWM. I tried fixing permissions with no luck.
broopa said:
Yeah, from CWM. I tried fixing permissions with no luck.
Click to expand...
Click to collapse
Did you turn phone on when you flashed recovery and then turn off then boot to recovery?
Sent from my HTC One using Tapatalk 2
I turned off phone, booted phone into BL menu then from there into CWM.
broopa said:
I turned off phone, booted phone into BL menu then from there into CWM.
Click to expand...
Click to collapse
Did you let the phone turn on and boot and then turn it off? Its important because when you unlocked bootloader/flashed recovery it completely reset your system meaning you need to boot it up and let it install the necessary stuff during boot animation (why it always takes so long the first time you boot up)
Sent from my HTC One using Tapatalk 2
I am pretty sure I did, I will reflash the recovery and see if that fixes it.
Edit: I just noticed I am unable to go back and reflash the the recovery. Is there a stock att version without root and CWM already on them so I can start from scratch?
Nice one gunnyman. Never disappoint. Its actually simpler to do on a mac because there isn't any driver installation. I just hope that AT&T allows us to do this for a while so that all of us here can get out key. Thats really all you need. You don't even need to do it, but its always a good idea to just get the key so if AT&T decides to block it again, you're safe.
If you guys are having trouble getting TWRP or CWS to work, make sure you have fastboot turned off in the power settings. It caused mine to not mount data sometimes.
This is a good right up. Finally have a way to do this on my Mac

[s-off] rumrunner s-off

rumrunner s-off is now available for select htc one's, including those that have been previously unexploitable.
brought to you by beaups and fuses
www.rumrunner.us
note:
you MUST be htc dev unlocked or rooted
you MUST have working drivers (windows)
you MUST meet all of the prerequisites
support is available at #rumrunners on freenode and andirc
do NOT clutter support channels with unsupported configurations
updated version for 2.24.401.8 posted. If you are on this firmware and have been having issues, please remove ALL old versions and download again from rumrunner.us. Sorry for the issues.
Rumrunner custom hboot. Enjoy.
No portion of it may be redistributed, repacked, rehosted, or oneclicked!
S-OFF device is required!!
Features:
Full set of fastboot flash commands
Full set of fastboot erase commands
Full set of fastboot oem commands (eng-hboot command set)
Removes red banner
Removes tampered text
Download here
How to flash:
1) Put your phone in fastboot mode
2) Type the following commands into terminal
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rumrunner_2.24_401.8_hboot.zip
fastboot reboot-bootloader
If you like our work, please donate at rumrunner.us
thread opened.
Just sent a request for Sprint support
Hmmm, so I carefully ensured that I met the requirements and had the right package for my model 224113, I restored a stock TMO twrp backup, and ran rumrunner.
All seemed well until suddenly I encountered the following error during test 3
FATAL: **** IT
Now it's been printing periods in the cmd window for about 15 minutes.
The device is in bootloader.
What is safe for me to do?
S-OFFed yesterday. Thank you for this!
S-OFFed successfully, thank you very much
any way to remove "tampered" flag?
Will you be releasing Custom Hboot for different variants?
zorbakun said:
Will you be releasing Custom Hboot for different variants?
Click to expand...
Click to collapse
+1..
Will this support Hboot 1.55?
I'm unfortunately stuck on that HBoot...
hypocritelecteur said:
Hmmm, so I carefully ensured that I met the requirements and had the right package for my model 224113, I restored a stock TMO twrp backup, and ran rumrunner.
All seemed well until suddenly I encountered the following error during test 3
FATAL: **** IT
Now it's been printing periods in the cmd window for about 15 minutes.
The device is in bootloader.
What is safe for me to do?
Click to expand...
Click to collapse
Disable antivirus/firewall/Windows Defender etc etc. Retry.
Tabtoub said:
S-OFFed successfully, thank you very much
any way to remove "tampered" flag?
Click to expand...
Click to collapse
You can use revone to remote TAMPERED : http://forum.xda-developers.com/showthread.php?t=2314582
You should do BOLD steps:
Instructions
Use any operating system you like, you only need adb.
1. Download revone and push it to your device: adb push revone /data/local/tmp/
2. Open an adb shell and: => command : adb shell
* cd /data/local/tmp
* chmod 755 revone
3. (optional) If your device is unlocked and rooted please switch to root using su.
4. Prepare to gain S-OFF by running the command: ./revone -P
4a. If revone reports success reboot the device and proceed to step 5)
4b. If revone reboots the device (we'll pretend this isn't an undiagnosed random crash) please wait 2 minutes then try again from step 2.
4c. If revone reports that you need to reboot and try again please reboot and try again from step 2.
5. Now that revone has successfully prepared your device for S-OFF please open another adb shell (as per step 2) and change to
the /data/local/tmp directory.
6. Instruct revone to grant you S-OFF and unlock status by running the command: ./revone -s 0 -u
6a. Other optional command arguments:-
* -u - Unlock the device
* -l - Lock the device (as if it was never unlocked)
* -r - Relock the device (mark the device as relocked)
* -t - Reset the device's tamper flag.
7. Presuming revone reported success please reboot the device again, this time to the bootloader (adb reboot bootloader)
8. You should now observe your device is S-OFF (and the lock status changed if you invoked that option).
9. (optional) Re-run revone to remove TAMPERED from your HBOOT screen: ./revone -t
Click to expand...
Click to collapse
Does it works on Viper 2.7.0 sense based Custom ROM with build 2.24.401.1? Becase I lost my nandroid backup for last OTA 4.2.2 update
My HTC One Is International version
Asia WWE Version
Unlocked via HTCDev.com
Sent from my HTC One using xda premium
@acank46.mh I S-OFF'd with ViperOne 2.6.0, so 2.7.0 should be fine.
---------- Post added at 12:33 PM ---------- Previous post was at 12:33 PM ----------
@balla786 It will work on 1.55.
acank46.mh said:
Does it works on Viper 2.7.0 sense based Custom ROM with build 2.24.401.1? Becase I lost my nandroid backup for last OTA 4.2.2 update
My HTC One Is International version
Asia WWE Version
Unlocked via HTCDev.com
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Thank's Sir
Sent from my HTC One using xda premium
To remove 'Tampered' banner after S-OFF'ing, put this is in terminal emulator
Code:
su
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
Just copy and paste it into terminal to ensure no errors
Credits @scotty1223
Maybe @beaups can put this in the OP to prevent repeat questions?
Got S-Off this AM. Good start to a Monday! Thank you!
Sent from my HTC One using Tapatalk
Got my HTC one s-offed last friday. I was tring to make it work on windows 8.1 but it was impossible to get the fastboot drivers to work. finaly I tried on a different computer with windows 8 and all worked perfectly.
thank you for the hard work.
polys_a said:
Got my HTC one s-offed last friday. I was tring to make it work on windows 8.1 but it was impossible to get the fastboot drivers to work. finaly I tried on a different computer with windows 8 and all worked perfectly.
thank you for the hard work.
Click to expand...
Click to collapse
Ah, so it doesn't work on windows 8.1. Thanks for the tip, I've been trying for two days on 8.1 with no luck so I will try on Windows 8. Thanks.:good:

Categories

Resources