i plan on picking one of these up as soon as LTE models are available,so eventually i can collect all this myself.
however if anyones bored,i wouldnt mind taking a peak at at the results of:
in a rooted OS:
adb shell
su
cat /proc/emmc
cat proc/partitions
in fastboot:
fastboot oem ?
fastboot getvar all
(in a locked and unlocked state)
post pm or upload documents,please remove all imie,esn,etc.
im also real curious of fastboot oem lock results in a relocked or locked bootloader.
if we can install any firmware,and unsigned images this may be the first htc device not to have an "s-" status
scotty1223 said:
i plan on picking one of these up as soon as LTE models are available,so eventually i can collect all this myself.
however if anyones bored,i wouldnt mind taking a peak at at the results of:
in a rooted OS:
adb shell
su
cat /proc/emmc
cat proc/partitions
in fastboot:
fastboot oem ?
fastboot getvar all
(in a locked and unlocked state)
post pm or upload documents,please remove all imie,esn,etc.
im also real curious of fastboot oem lock results in a relocked or locked bootloader.
if we can install any firmware,and unsigned images this may be the first htc device not to have an "s-" status
Click to expand...
Click to collapse
There is no S flag. Adb works. Fastboot works. Unlock works. Root via fastboot works. Just waiting on recovery.
prdog1 said:
There is no S flag. Adb works. Fastboot works. Unlock works. Root via fastboot works. Just waiting on recovery.
Click to expand...
Click to collapse
thanks ,but thats not what i asked.
just because there is no s flag displayed,does not mean there are no securities.
scotty1223 said:
thanks ,but thats not what i asked.
just because there is no s flag displayed,does not mean there are no securities.
Click to expand...
Click to collapse
Only SLinux from what we can see.
Nothing unusual in getvar except unlocked. OEM unlock shows unlocked. OEM lock says locked. Not relocked. Lock or unlock erases all data.
Related
if I use the htc unlock and someone finds a way to s off this device can I revert back or am i always stuck with the htc way. or can i do htc unlock and just probably do the hacked s off. thanks
You can relock through adb. I believe the command is "fastboot oem lock"
applying an OTA also relocks the bootloader
thanks good info
bernechad said:
You can relock through adb. I believe the command is "fastboot oem lock"
Click to expand...
Click to collapse
You relock thru fastboot not adb. Run that command you posted in fastboot mode.
Sent from my EVO 4G LTE
NewZJ said:
applying an OTA also relocks the bootloader
Click to expand...
Click to collapse
Running a ruu relocks the bootloader.
Sent from my EVO 4G LTE
david279 said:
You relock thru fastboot not adb. Run that command you posted in fastboot mode.
Sent from my EVO 4G LTE
Click to expand...
Click to collapse
If you want to get technical about it, you need either the sdk or adb installed in order to use fastboot command and your phone in fastboot from the bootloader. .
And on the evo lte, htc has brought in fast boot mode in the os for a quicker startup sequence, because the phone doesn't truly turn off, just a hibernate state.
But I wasn't being technical about it because that's not what the op was asking
I just didn't want the guy to try to do
Adb fastboot OEM lock
That won't work. It would throw a error.just trying to be correct. also you don't necessarily need adb to use fastboot. The fastboot and adb binaries are packaged separately. He could boot into fastboot by doing volume down and power then using fastboot only unlock the bootloader using the fastboot binary.
Fastboot OEM unlock.
Sent from my EVO 4G LTE
david279 said:
I just didn't want the guy to try to do
Adb fastboot OEM lock
That won't work. It would throw a error.just trying to be correct. also you don't necessarily need adb to use fastboot. The fastboot and adb binaries are packaged separately. He could boot into fastboot by doing volume down and power then using fastboot only unlock the bootloader using the fastboot binary.
Fastboot OEM unlock.
Sent from my EVO 4G LTE
Click to expand...
Click to collapse
Oh, I wasn't aware that you could use fastboot without the sdk or adb installed.
Hello
I'm trying to revert back to complete stock (stock rom, no root, S-ON) and following this guide/post:
http://forum.xda-developers.com/showthread.php?p=33770807
For that i need to do check the CID and then write back the original CID (Though i can skip this because i didn't use HTC Dev method at all, just original root and revolutionary S-OFF)
Then i need to do "fastboot oem lock" before running the RUU.. but here in lies my problem.
For some reason i can't get fastboot to work.
ADB works fine and i can push and pull files when in android or recovery, but as soon as i enter hboot and try to use fastboot commands, i just get "< Waiting for device >" and have to close the CMD window. (Before you ask, yes it does say "FASTBOOT USB" on the screen)
I have tried both using my standard adb and fastboot files, and i have also tried downloading the latest android SDK and using those files, but neither to any luck.
Anyone have any idea? It might be something simple, as i haven't had to use fastboot before now.
I'm guessing it can't be a driver problem as i can connect fine with ADB and it shows my device when doing "adb devices" (Though it does not show my device when i do "fastboot devices", it just skips the line entirely and prompts me to enter something new).
- Moon
Moonbloom said:
I'm guessing it can't be a driver problem as i can connect fine with ADB and it shows my device when doing "adb devices" (Though it does not show my device when i do "fastboot devices", it just skips the line entirely and prompts me to enter something new).
Click to expand...
Click to collapse
If "fastboot devices" doesn't show the serial number of your phone, none of the other fastboot commands are going to work.
Have you tried disconnecting the phone, rebooting your PC and then connecting the phone again? If that doesn't work, try uninstalling the drivers, rebooting the PC, then reinstalling the drivers.
ramjet73
ramjet73 said:
If "fastboot devices" doesn't show the serial number of your phone, none of the other fastboot commands are going to work.
Have you tried disconnecting the phone, rebooting your PC and then connecting the phone again? If that doesn't work, try uninstalling the drivers, rebooting the PC, then reinstalling the drivers.
ramjet73
Click to expand...
Click to collapse
Tried to reboot the computer, no change.
Decided to try using my laptop before going through the trouble of reinstalling drivers, and it worked
My laptop can see my device fine using "fastboot devices" and i'm able to get my CID (cid: 0202)
Thanks for trying to help me out anyways I might be back with more questions
EDIT: I just google'd a bit and found another command to get the CID "fastboot oem readcid" and it shows HTC_Y13 (which i find more believable tbh).
Is your hboot unlocked?
I am s-off, but couldn't use fastboot commands untill i unlocked my bootloader again..
klect said:
Is your hboot unlocked?
I am s-off, but couldn't use fastboot commands untill i unlocked my bootloader again..
Click to expand...
Click to collapse
There's no need to unlock the bootloader if you are S-OFF.
If you want to run fastboot commands like "flash" or "erase" just install a custom bootloader like ENG, JBear or Revoutionary from the current bootloader. It's better to keep the bootloader locked since that's the stock status and it makes it much easier to return the phone to 100% stock.
AFAIK, the "*** RELOCKED ***" heading you get when locking an unlocked bootloader which flags to HTC/Sprint that you modified the phone can only be undone with the JuopunutBear wire trick.
ramjet73
For me IT was the only way to get fastboot working though...
Sent from my Evo 3D GSM using xda app-developers app
klect said:
For me IT was the only way to get fastboot working though...
Click to expand...
Click to collapse
Did you try one of the JuopunutBear bootloaders (GB or ICS) for the GSM version of the Evo 3D? That should allow the fastboot commands without unlocking.
ramjet73
Yeah, after i s-offed i flashed the ICS jb hboot, but no luck...
So i decided to flash the 1.49.0007 hboot and unlock it the htcdev way.
But if you want to lock it again, you can simply redo the wiretrick right?
klect said:
Yeah, after i s-offed i flashed the ICS jb hboot, but no luck...
So i decided to flash the 1.49.0007 hboot and unlock it the htcdev way.
But if you want to lock it again, you can simply redo the wiretrick right?
Click to expand...
Click to collapse
That's correct.
ramjet73
For all those who were directed here...
This solved my problem when everybody else's advice failed, and it was the easiest.
http://forums.androidcentral.com/ve...how-install-device-drivers-android-1-0-a.html
I am in the process of turning of factory restoring my htc one and i have the bootloader unlocked and i am turning my s-off with moonshine right now because i know that it needs to be off but i dont know what ruu to use and what command to put in in order to remove the tampered icon so can anyone please help?
use revone. will do s-off and let you remove the tampered flag. the post has it all explained already you will need to be on 1.27.531.8 though. Revone Thread
Based on you posting this in the tmobile section il assume your device is on tmobile. in witch case there is only 1 RUU at the current time (official atleast) get it Here
as for downgrading to 1.27.531.8 i cant post the thread link so google for " tmobile HTC one downgrade to 1.27.531.8 " should take you to a rootzwiki page thread.
or if you are looking for 99.999% pure stock just run that RUU linked above. you will need to be relocked witch you can achieve by going into fastboot plug in your usb cable and type into a cmd prompt cd'd to your android sdk directory aka platform-tools folder.
Code:
fastboot oem lock
for example.
F:\androidsdk\sdk\platform-tools>fastboot oem lock
Click to expand...
Click to collapse
Your directory will be different
then you should be set aslong as your CID is T-MOB010 the RUU should flash.
Ok I'm going to just use this thread since it's an issue I need help with also. I attached a photo of what my T-mobile HTC One says. I don't understand the fastboot thing? Can you further explain it to this n00b? Like I guess step by step lamen terms lol. I don't understand ADB or fastboot at all. All my previous devices just had one click root tool buttons to return to stock. All I want is out of the box stock condition with no tampered text. Thank You.
damon7620 said:
Ok I'm going to just use this thread since it's an issue I need help with also. I attached a photo of what my T-mobile HTC One says. I don't understand the fastboot thing? Can you further explain it to this n00b? Like I guess step by step lamen terms lol. I don't understand ADB or fastboot at all. All my previous devices just had one click root tool buttons to return to stock. All I want is out of the box stock condition with no tampered text. Thank You.
Click to expand...
Click to collapse
Fastboot and ADB are all run from the command line on your PC with you phone plugged in. First question, do you have ABD and Fastboot installed on your computer?
RangerLG said:
Fastboot and ADB are all run from the command line on your PC with you phone plugged in. First question, do you have ABD and Fastboot installed on your computer?
Click to expand...
Click to collapse
no
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...
Hey folks,
I have a HTC incredible 4g and was able to successfully unlock the phone with s-off following the directions given by this post:
http://forum.xda-developers.com/showthread.php?t=2664460
Unfortunately, when I continued with step 5, which was "flash ENG-hboot 1.15.1111 ... obtainable from DirtyRacun webpage:", I ended up with a "relocked" phone.
What should I do to unlock my phone again? Should I rerun the rumrunner binaries?
Thanks in advance.
Update: trying to install CyanogenMOD
FYI - I tried rerunning the rumrunner binaries, and that did not "unlock" my phone again. If someone has a link that describes fastboot options such as
Code:
fastboot oem lock
or
Code:
fastboot oem unlock
that would be much appreciated. Because my phone is "locked", I'm concerned that my phone is going to get bricked if an OTA update hits it based on this post:
http://forum.xda-developers.com/showthread.php?t=1077019
Based on the comments in that post, it would also appear that my phone needs to be in an "unlocked" state in order to flash anything. Can somebody please confirm that is true?
Install new HBOOT after S-OFF
stringedonbass said:
FYI - I tried rerunning the rumrunner binaries, and that did not "unlock" my phone again. If someone has a link that describes fastboot options such as
Code:
fastboot oem lock
or
Code:
fastboot oem unlock
that would be much appreciated. Because my phone is "locked", I'm concerned that my phone is going to get bricked if an OTA update hits it based on this post:
http://forum.xda-developers.com/showthread.php?t=1077019
Based on the comments in that post, it would also appear that my phone needs to be in an "unlocked" state in order to flash anything. Can somebody please confirm that is true?
Click to expand...
Click to collapse
Installing Unlimited.io's hboot fixed my problem. Follow the directions on their website, and you'll see a sneaky little DirtyRacun during bootup that will replace your "relocked" status:
Code:
sudo ./fastboot erase cache
sudo ./fastboot oem rebootRUU
sudo ./fastboot flash zip [file name]
sudo ./fastboot reboot
Being S-OFF was enough to perform these tasks. Thanks everyone for looking, and a special thanks to the unlimited team for making it happen!