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:
Related
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
Relock the bootloader:
Code:
fastboot oem lock
Go back to fastboot mode ( lock causes the device to reboot )
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 the tacoroot.
s*** too late!!!!
Yesterday I unlocked my Tab via HTC Unlock, hopefully I'll never need the warranty ...
But thanks for your detailed and very helpful instructions in this forum, don't know where I would be without you.
globatron said:
7. Run the following command:
Code:
adb # /data/local/misc_version -s [COLOR="Red"]2.00.405.3[/COLOR]
Click to expand...
Click to collapse
I think there is a mistake, it should be:
Code:
adb shell /data/local/misc_version -s [COLOR="Red"]2.00.405.3[/COLOR]
But: it doesn't work. The device hangs in the boot process after flashing the RUU.
Tutmanichtun said:
I think there is a mistake, it should be:
Code:
adb shell /data/local/misc_version -s [COLOR="Red"]2.00.405.3[/COLOR]
But: it doesn't work. The device hangs in the boot process after flashing the RUU.
Click to expand...
Click to collapse
The typo correction is correct but that it doesn't work is not. I've done this multiple times with both my own and other peoples devices and it works just fine. Make sure you used a gingerbread RUU and the it flashed completely. AND that you not doing this on an S-OFF device.
globatron said:
AND that you not doing this on an S-OFF device.
Click to expand...
Click to collapse
Thats the fault. My Flyer is S-OFF. Is there a possibility to get back to GB anyway?
Edit: Found a Solution. It cost me the whole day, but now it works.
The bad note: I don't know the Link with the solution. But it was in this Forum.
I got to it by Flashing a 3.2.1 ROM, and after that a 2.3.4 ROM via Goldcard-Method. (Via the SD-Card.)
During the process the Bootloader creates a message, that the installed hboot version isn't downgradeable or something like that. I hacked that into Google and it throws out a Thread in this Forum with the Solution.
Might be a little off topic, but the title:
[Pocedure]No HTC unlock HC-GB downgrade for official HC OTA
"[Pocedure]" is missing a letter r
echaru said:
Might be a little off topic, but the title:
[Pocedure]No HTC unlock HC-GB downgrade for official HC OTA
"[Pocedure]" is missing a letter r
Click to expand...
Click to collapse
Cool. someone who actually reads
Thanks echaru, fixed.
Im on the HC leak - can I use this method flash the RUU for US WIFI HC Release or do I need to go back to GB first?
Back to gingerbread I believe is your only option
Sent from my HTC Flyer P510e using xda premium
mcord11758 said:
Back to gingerbread I believe is your only option
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
That's Correct.
Tutmanichtun said:
Thats the fault. My Flyer is S-OFF. Is there a possibility to get back to GB anyway?
Edit: Found a Solution. It cost me the whole day, but now it works.
The bad note: I don't know the Link with the solution. But it was in this Forum.
I got to it by Flashing a 3.2.1 ROM, and after that a 2.3.4 ROM via Goldcard-Method. (Via the SD-Card.)
During the process the Bootloader creates a message, that the installed hboot version isn't downgradeable or something like that. I hacked that into Google and it throws out a Thread in this Forum with the Solution.
Click to expand...
Click to collapse
What you say does not make sense to me. This thread specifically says this is for official HC upgrade which implies you have to be S-ON and locked.
If you are S-OFF you need to follow Globatron's other thread http://forum.xda-developers.com/showpost.php?p=19607833&postcount=3
cnewsgrp said:
What you say does not make sense to me. This thread specifically says this is for official HC upgrade which implies you have to be S-ON and locked.
If you are S-OFF you need to follow Globatron's other thread http://forum.xda-developers.com/showpost.php?p=19607833&postcount=3
Click to expand...
Click to collapse
Thats what I said: I've made a mistake.
hi
I try this method ... but something is wrong
adb push msc_version /data/local
error : cannot stat msc_version : No such file or directory
your file is misc_version
rename misc_version to msc_version? or ?!
plz help
nader1450 said:
hi
I try this method ... but something is wrong
adb push msc_version /data/local
error : cannot stat msc_version : No such file or directory
your file is misc_version
rename misc_version to msc_version? or ?!
plz help
Click to expand...
Click to collapse
Typo in the procedure, fixed now.
Hi
I followed the instruction and at this point:
adb shell /data/local/misc_version -s 2.00.405.3
I have a message: error opening input file.
I assume it is for the RUU.. where do I need to copy the RUU file to my SD or to the same folder where ADB is?
That is not the ruu. It is the misc file and all files should not be on your ad unless you are trying to flash the zip through hboot. They should be in your adv folder
Sent from my HTC Flyer P510e using xda premium
mcord11758 said:
That is not the ruu. It is the misc file and all files should not be on your ad unless you are trying to flash the zip through hboot. They should be in your adv folder
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
Thx for your answer. I have the misc file in the ADB folder the sameone I downloaded from the instruction.. any other idea?
Right the whole message is after I enter the command:
Finding misc partition
misc partition found: /dev/block/mmcblk0p28!
backing up misc partition to /data/local/miscBackup-1325954343.bin and determing
version length...
Error opening input file.
You failed to get root with tacoroot.
Start again from the last command in step 3.
globatron said:
You failed to get root with tacoroot.
Start again from the last command in step 3.
Click to expand...
Click to collapse
I think this would be the problem then after i run this:
C:\Android>adb shell /data/local/tacoroot.bin --root
Rebooting into root.
cannot create /data/local.prop: permission denied
globatron said:
Type in the procedure, fixed now.
Click to expand...
Click to collapse
thanks
i try again ... but:
adb shell /data/local/misc_version -s 2.27.707.1
have error (i don't remember error but something like that): misc only 11 number but this is 10
any way, restart and come htc boot and didn't go to android.
i flash HC ... and go to android ... but adb cannot connect device
error is: devices not found
i try:
adb kill-server
but still problem
plz help me
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.
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...
My DNA was previously S-off and unlocked before the latest kitkat OTA, when the new OTA came out I fastboot flashed the latest HBOOT and Radio before I started using a custom sense 6 rom. It seems that with the HBOOT update, my bootloader became locked and the tempered sign is gone as well, I tried using firewater, but since my phone is S-Off the application just say there's not anything it can do and closes. What can I do to unlock my bootloader? Or do I have to return everything to S-On and run firewater?
Just downgrade the hboot and install again 3.06.605.4 and later unlock your bootloader and keep it s-off!! and later if you want update again to kitkat but use the first ota zip and second one too!!
I would flash the 3.06 hboot first before this, but it probably won't make a difference.
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
Code:
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
Click to expand...
Click to collapse
quoted from this thread http://forum.xda-developers.com/showthread.php?p=47769994
Change CID, htcdev -> unlock
Sent from my Nexus 5 using XDA Free mobile app
.torrented said:
I would flash the 3.06 hboot first before this, but it probably won't make a difference.
quoted from this thread http://forum.xda-developers.com/showthread.php?p=47769994
Click to expand...
Click to collapse
worked perfectly!! Thanks so much
Hello everyone I'm a new VZW One Max owner and this device has proven to be the most complicated ive experienced so far in terms of Rooting/Bootloader unlocking/and S-off. (I'm temp rooted with weaksauce 1.0.1)
I cant seem to get the bootloader unlocked via HTCdev, and the firewater and rumrunner do not work for me either .
It seems like every method to help accomplish the above requires an unlocked bootloader, and after reading several threads the tool of choice is firewater.
While reading the thread for firewater I noticed it said it is for HBOOT 2.47, there was a note at the bottom of the thread for 2.49 HBOOT users but while following the instructions from that thread one of the steps was to unlock the bootloader via HTCdev :silly: . And install the Stock HTC 1.19xxxx
How can that be done in my situation?
Ive attached errors i've been experiencing from firewater and rumrunner.
***For rumrunners I'm using the custom device specific download. But i've seen all types of errors from flashing a new kernel to using a more updated version.
Verizon HTC One Max Android Version 4.4.2 with HBOOT 2.49
Thanks for any steps in the right direction!
ceo4eva said:
Hello everyone I'm a new VZW One Max owner and this device has proven to be the most complicated ive experienced so far in terms of Rooting/Bootloader unlocking/and S-off. (I'm temp rooted with weaksauce 1.0.1)
I cant seem to get the bootloader unlocked via HTCdev, and the firewater and rumrunner do not work for me either .
It seems like every method to help accomplish the above requires an unlocked bootloader, and after reading several threads the tool of choice is firewater.
While reading the thread for firewater I noticed it said it is for HBOOT 2.47, there was a note at the bottom of the thread for 2.49 HBOOT users but while following the instructions from that thread one of the steps was to unlock the bootloader via HTCdev :silly: . And install the Stock HTC 1.19xxxx
How can that be done in my situation?
Ive attached errors i've been experiencing from firewater and rumrunner.
***For rumrunners I'm using the custom device specific download. But i've seen all types of errors from flashing a new kernel to using a more updated version.
Verizon HTC One Max Android Version 4.4.2 with HBOOT 2.49
Thanks for any steps in the right direction!
Click to expand...
Click to collapse
If you still need help with this, I recently did this on a Verizon One Max, double check the following:
Fastboot mode is off in the power/battery settings
No lock screen security enabled, pattern, pin, face, nothing should be on
Leave the screen on a long timeout, or no timeout for this process, adb may prompt RSA checks you'll need to grant permissions to.
Remove all super user apps, busybox installer apps, supersu, superuser, whatever
Then:
Run weaksauce app
Install supersu from play store or you can adb install the apk if you have the updater zip or apk on your PC
After you have su (# prompt instead of $ after typing su) in adb shell turn off WiFi, leave mobile data on:
adb shell
su
If you see it change to # then proceed, if not, reboot and run weaksauce again, wait for a minute and try the commands again.
Exit adb shell (type exit and hit enter twice)
Push firewater to /data/local/tmp
adb push firewater /data/local/tmp
Set 755 permissions on firewater:
adb shell
su (if not on # prompt, it should still be there)
chmod 755 /data/local/tmp/firewater
Run firewater (still in shell, don't close the terminal or exit from su/#):
/data/local/tmp/firewater
Last time it froze the first time, then the second try it went through on the second bottle. If you see no improvement after 3 minutes hold power for 60 seconds until it reboots the device, then start again from the weaksauce running part.
Hope this helps. I did it over team viewer with another user and this is what finally got it to get it all finished.
Rumrunner doesn't work with verizon 2.49 that I can tell, it'll be weaksauce and firewater.