I'm in bootloader mode, and I see USB on screen.
What is boot command "info 2"?
I see nothing that allows me to type this.
I have tried to do this on two computers.
Do I need to have the tytn connected via usb cable? ( I have tried both with and without).
Is there an easier way to find out what my CID is?
pufftissue said:
I'm in bootloader mode, and I see USB on screen.
What is boot command "info 2"?
I see nothing that allows me to type this.
I have tried to do this on two computers.
Do I need to have the tytn connected via usb cable? ( I have tried both with and without).
Is there an easier way to find out what my CID is?
Click to expand...
Click to collapse
I believe you have to start the program MTTY first on you pc. You will be in a commandbox then and there you can type your commands.
Read instructions here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
You need to disable usb in activesync and run mtty.
Thank you for being an angels (robust, manly angels).
I have now successfully unlocked my tytn and given it a super cid....now I need to choose which ROM to use.
Cingular, HTC, or Imate? Choices choices...
I did look for bootloader but for some reason I missed it in the search.
Thanks again
Related
How do I identify the CID on my TyTN from Vodafone?
alfazulu said:
How do I identify the CID on my TyTN from Vodafone?
Click to expand...
Click to collapse
bootloader command "info 2":
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
Use mtty.exe to connect, link is on this wiki page too.
MTTY ust says CLIENTCLIENTCLIENT but I cannot type any command.
Any suggestions?
- open mtty.exe
- select USB port on the drop down list
- put your Hermes in bootloader mode (side ok + power + stylus reset)
- connect your hermes to pc using miniUSB cable
- on the tri-color screen "serial" should be changed by "USB"
- click ok on mtty to connect
- hit enter twice, a "USB>" prompt should appear where you should be able to type in bootloader commands (do not copy-paste the commands, type them using the keyboard).
- "info 2" should give you your CID, encapsulated on a "HTCS + CID + 4byte checksum + HTCE"
Thank-you. I get HTCSVODAP001©®±HTCEUSB>.
That means this is your CID: VODAP001
help i cannot get only get cmd> and i follow the guide. how i get the usb>
On new bootloader version USB> has been replaced by Cmd>, but the process is the same.
If you have HardSPL with "info 2" you'll always get "SuperCID", so if you want to check your real CID use "info 4".
Any tips on getting Mtty to work with vista? I have tried everything under the sun and no go for me. I can flash radios and ROMs all day long but when it comes to Mtty i have no luck what so ever! Please prof help...
mines showing as
USB>
USB>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCEUSB>
is it corrupt then? and if so how can i fix it with a device thats bricked already?
Smith2001 said:
is it corrupt then?
Click to expand...
Click to collapse
yes
Smith2001 said:
and if so how can i fix it with a device thats bricked already?
Click to expand...
Click to collapse
i already answered you here, use platform builder!
I've already unlocked the bootloader and am about to flash cwd but my computer won't recognize the phone in the bootloader while plugged into USB. So when I try to enter the command "fastboot flash recovery <recovery.img>", the command prompt comes back with an error. I bet I'm missing something simple here, but it's getting pretty frustrating.
I have the HTC drivers installed and I'm using bootcamp, if that matters.
Are you positive that you are in fastboot mode. Does it say fastboot USB on your phones screen in red? Uninstall the HTC sync drivers its like a 150mb package. All you need is the regular HTC android drivers. As far as bootcamp I'm unfamiliar with it so can't really say but the good old original ways are always reliable. If bootcamp is some sort of interface for fastboot and adb then I reccomend you read up a little on how to operate the two and simply do things the way they were originally implemented. It will benefit you in the long run. If I'm way off then sorry just trying to cover all the bases.
Good luck!
jonesin said:
Are you positive that you are in fastboot mode. Does it say fastboot USB on your phones screen in red? Uninstall the HTC sync drivers its like a 150mb package. All you need is the regular HTC android drivers. As far as bootcamp I'm unfamiliar with it so can't really say but the good old original ways are always reliable. If bootcamp is some sort of interface for fastboot and adb then I reccomend you read up a little on how to operate the two and simply do things the way they were originally implemented. It will benefit you in the long run. If I'm way off then sorry just trying to cover all the bases.
Good luck!
Click to expand...
Click to collapse
Haha i meant bootcamp for the mac. Allows you to run windows. I highly doubt this has anything to do with it, just thought I might throw it out there. I deleted the HTC sync drivers and the phone is still not recognized in the bootloader. It is recognized when the phone is on the homescreen, though.
My phone says "FASTBOOT USB" highlighted in red. The way I know it's not connected is entering "adb devices" into the command prompt and the response comes up as "List of devices attached" and doesn't display the serial number like it does when the phone is on the homescreen.
feperlman51 said:
Haha i meant bootcamp for the mac. Allows you to run windows. I highly doubt this has anything to do with it, just thought I might throw it out there. I deleted the HTC sync drivers and the phone is still not recognized in the bootloader. It is recognized when the phone is on the homescreen, though.
My phone says "FASTBOOT USB" highlighted in red. The way I know it's not connected is entering "adb devices" into the command prompt and the response comes up as "List of devices attached" and doesn't display the serial number like it does when the phone is on the homescreen.
Click to expand...
Click to collapse
Thats because adb is not functional during fastboot mode so it shouldnt be showing up. Try fastboot flash recovery recovery.img again it should run this time.
also try another usb port but it sounds like everything is set up correctly as long as you have fastboot in your platform tools folder and the device is in fastboot mode which it seams to be you should be good to go.
jonesin said:
Thats because adb is not functional during fastboot mode so it shouldnt be showing up. Try fastboot flash recovery recovery.img again it should run this time.
also try another usb port but it sounds like everything is set up correctly as long as you have fastboot in your platform tools folder and the device is in fastboot mode which it seams to be you should be good to go.
Click to expand...
Click to collapse
I got it this time! Didn't change anything, really, just ran the "fastboot flash recovery" command again. FWIW, twrp worked but cwd didn't. I had tried both initially, but twrp worked this time. I would bet that it was all human error. From what others have said this isn't actually an issue.
Either way, thanks for replying and trying to help!
feperlman51 said:
I got it this time! Didn't change anything, really, just ran the "fastboot flash recovery" command again. FWIW, twrp worked but cwd didn't. I had tried both initially, but twrp worked this time. I would bet that it was all human error. From what others have said this isn't actually an issue.
Either way, thanks for replying and trying to help!
Click to expand...
Click to collapse
"just ran the "fastboot flash recovery" command again"
Lol thats what I said man! Glad it worked! CWM and TWRP should both work, I bet a nickel to a dime you werent actually in fastboot mode the first time! anyway happy flashing! Get comfortable with ADB and Fastboot because they will be our primary utilities for the foreseeable future!
I want to unroot and go back to stock completely. I read some howto threads and they had a step about relocking the bootloader by going into fastboot. How exactly do I do that?
nulcon said:
I want to unroot and go back to stock completely. I read some howto threads and they had a step about relocking the bootloader by going into fastboot. How exactly do I do that?
Click to expand...
Click to collapse
I believe Hassoon's all in one tool has an option to do that:
http://forum.xda-developers.com/showthread.php?t=1493905
Kobraki17 said:
I believe Hassoon's all in one tool has an option to do that:
http://forum.xda-developers.com/showthread.php?t=1493905
Click to expand...
Click to collapse
I tried his toolkit so many times to try to relock the bootloader but it doesn't detect my phone even if USB Debugging is check on.
nulcon said:
I tried his toolkit so many times to try to relock the bootloader but it doesn't detect my phone even if USB Debugging is check on.
Click to expand...
Click to collapse
You have USB debugging checked on, do you also have it set up as CHARGING ONLY, and not the SD CARD setting?
Double check these settings and report back - another possibility (I can not confirm if it is necessary or not), try booting into the bootloader screen first and then run his re-locking script.
Kobraki17 said:
You have USB debugging checked on, do you also have it set up as CHARGING ONLY, and not the SD CARD setting?
Double check these settings and report back - another possibility (I can not confirm if it is necessary or not), try booting into the bootloader screen first and then run his re-locking script.
Click to expand...
Click to collapse
I have it set up as Charging Only.
if your having issues with the phone being detected... try reinstalling the usb drivers then restarting your computer... and just a heads up.. don't make more then one thread pertaining to the same problem/issue with the phone.. its harder for people to offer you help/advice if they haven't seen what was said/tried before...( i believe i told this to someone already) but yes.. re-install your usb drivers from hasoon's toolkit and see.. if you want to test the adb connection use some of his shortcut commands to boot the phone into recovery or restart it
nulcon said:
I tried his toolkit so many times to try to relock the bootloader but it doesn't detect my phone even if USB Debugging is check on.
Click to expand...
Click to collapse
If you haven't tried resetting it manually through fastboot commands, this may work:
Reboot your phone to bootloader (power button + volume down)
Open a command window and navigate to the folder where your fastboot.exe file is located using the command "cd C:\<folder tree>"
Execute the command "fastboot oem lock"
This worked for me about an hour ago even with my computer not recognizing my phone. Hope it helps.
Hello,
After over an hour of searching for something similar, I figured I'd just ask...
I'm trying to set-up a phablet as a dedicated car informant. I've got most everything set-up to satisfaction. I ran the fastboot command "fastboot oem off-mode-charge 0" to have the phone boot on charge. This worked fine for the Medion (lenovo) life X6001 with 5.1.
Then I set-up the tasker to automate certain actions. All seemed fine; low battery parameters as a safety net, offline maps on boot, turns off when disconnected from power source, ect.
But... now that I've got the tasker doing what I want; the phone no longer turns on by itself when connected to power source. Seemingly reverted back to it's charging screen, I enter fastboot, run the command again, seemingly accepted; no dice. Ok, so it worked before I had set-up the tasker, so I assume the tasker has changed something. I start disabling the new flows individually to find the culprit and sure enough, a few shut-down and boot-ups later, apparently the auto-off on power disconnect throws the fastboot command out the window. Disabled the phone starts up when connected to power source.
Here's the kicker: after dicking with the phone to no avail, I discover that not only does the phone boot when it's off and finds a power source but it also boots when it's turned off and is disconnected from it's power source... How weird is that? Logically, a tasker shut-down on power disconnect would interfere with a command that also tells the phone to boot when disconnected.
Before this point I hadn't entered any other fastboot commands, so I couldn't have inadvertently given an unknown command. Fastboot oem off-mode-charge 0 seemingly makes this device boot on connect and disconnect.
All great and well, there are more than one way to skin a cat...yet I tried to reverse the command with fastboot oem off-mode-charge 1 but the command isn't recognized. So I tried fastboot oem off-mode-charge disable; this was a recognized command but doesn't toggle the command to off. I've tried all the different variations I can find with regards to oem off-mode-charge but nothing will restore the original function.
I've also tried to dump the bootloader to find the hidden commands, but the walkthrough
on this forum doesn't work with this device. I get into super user function just fine but # cd /dev/....... isn't a recognized directory....
I know this is kind of a long post. I hope someone will bare with me who can shed some light. Thanks in advance.
Bump.
No one willing to share an idea?
Am I asking my questions incorrectly?
Bummer...
There's a forum named Connected Car on XDA, try asking over there
Thanks for your reply. I can ask in the car forum, I assumed being that the specific question doesn't have anything to do with the actual installation that it belonged here...
I've read all the posting rules and guidelines and I'm still not a star on choosing the correct forum.
Are you looking for fastboot commands?
Mwmcc said:
Hello,
After over an hour of searching for something similar, I figured I'd just ask...
I'm trying to set-up a phablet as a dedicated car informant. I've got most everything set-up to satisfaction. I ran the fastboot command "fastboot oem off-mode-charge 0" to have the phone boot on charge. This worked fine for the Medion (lenovo) life X6001 with 5.1.
Then I set-up the tasker to automate certain actions. All seemed fine; low battery parameters as a safety net, offline maps on boot, turns off when disconnected from power source, ect.
But... now that I've got the tasker doing what I want; the phone no longer turns on by itself when connected to power source. Seemingly reverted back to it's charging screen, I enter fastboot, run the command again, seemingly accepted; no dice. Ok, so it worked before I had set-up the tasker, so I assume the tasker has changed something. I start disabling the new flows individually to find the culprit and sure enough, a few shut-down and boot-ups later, apparently the auto-off on power disconnect throws the fastboot command out the window. Disabled the phone starts up when connected to power source.
Here's the kicker: after dicking with the phone to no avail, I discover that not only does the phone boot when it's off and finds a power source but it also boots when it's turned off and is disconnected from it's power source... How weird is that? Logically, a tasker shut-down on power disconnect would interfere with a command that also tells the phone to boot when disconnected.
Before this point I hadn't entered any other fastboot commands, so I couldn't have inadvertently given an unknown command. Fastboot oem off-mode-charge 0 seemingly makes this device boot on connect and disconnect.
All great and well, there are more than one way to skin a cat...yet I tried to reverse the command with fastboot oem off-mode-charge 1 but the command isn't recognized. So I tried fastboot oem off-mode-charge disable; this was a recognized command but doesn't toggle the command to off. I've tried all the different variations I can find with regards to oem off-mode-charge but nothing will restore the original function.
I've also tried to dump the bootloader to find the hidden commands, but the walkthrough
on this forum doesn't work with this device. I get into super user function just fine but # cd /dev/....... isn't a recognized directory....
I know this is kind of a long post. I hope someone will bare with me who can shed some light. Thanks in advance.
Click to expand...
Click to collapse
In order to obtain fastboot commands. I assume you must have installed the ADB and fastboot program on your computer (ADB setup version 1.3.exe etc) once you install this program there would be a folder under your C:\ drive named ADB.
Open the folder after installing the driver
Press window button + R to bring the Run dialogue box
Type cmd and press enter if Win XP or "if you use Windows 7 OS right click a blank space while holding shift"
Open command prompt here.
if XP then, command prompt appears; use "cd" command in the command window to start the command from the open folder.
i.e. if command indicates C:\ Documents and Settings\ User etc change the command to open by typing "cd.." twice and then type "cd adb" all without quotes until your command starts in the folder where your adb and fastboot. exe files are present.
Now type " fastboot" without quotes in the folder C:\adb, the command would look similar "C:\adb\fastboot" without quotes to receive all fastboot commands and switches associated with this command; similarly adb commands and its switches when typing "C:\adb\adb" without quotes in the same folder.
Hope this information will resolve your issue,
Regards,
alza689
I appreciate your effort. Yes, I'm looking for device specific hidden fastboot commands. Unfortunately, this method only shows the basics and doesn't display the command needed to toggle fastboot oem off-mode-charge. The walk-through for dumping the bootloader provided on these forums didn't work for my device.
Thanks again.
Perhaps googling might help
Mwmcc said:
I appreciate your effort. Yes, I'm looking for device specific hidden fastboot commands. Unfortunately, this method only shows the basics and doesn't display the command needed to toggle fastboot oem off-mode-charge. The walk-through for dumping the bootloader provided on these forums didn't work for my device.
Thanks again.
Click to expand...
Click to collapse
Try various methods of google search, it might help! try fastboot commands and enter your specific device in the search, as I ran out of options to help you.
Regards,
689alza
Trust me, before I take the time to register on a forum and ask a question I've searched 'til near anxiety attack through google...
Thanks anyway.
Try this link, hope it helps you.
Mwmcc said:
Trust me, before I take the time to register on a forum and ask a question I've searched 'til near anxiety attack through google...
Thanks anyway.
Click to expand...
Click to collapse
http://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/
Mwmcc said:
Am I asking my questions incorrectly?
Bummer...
Click to expand...
Click to collapse
Possibly you have already solved your issue from 2 years ago.
I suspect that you are using an OTG USB adapter.
Have you tried disconnecting it before shutting down the phone/tablet?
That was the only way I could prevent my tablet from rebooting by itself after installing the "fastboot oem off-mode-charge 0".
Hey all i dont know what the deal is but ive got an lg g5 that just will not boot to the bootloader. I've tried factory resetting it and all the methods to get to bootloader just reboots the phone fully. Adb reboot booloader, key combos, nothing seems to work. Any ideas??
First, connect your smartphone with your PC; plug in the USB cord in order to establish the connection.
On your computer access the Android SDK folder.
From there open a command prompt window: press and hold the Shift keyboard key while right clicking on any blank space.
Next, in the cmd window type “adb reboot bootloader” and wait while the bootloader mode is displayed on your smartphone
That's basically what I did and worked first time..make sure the adb and fastboot package is installed and open the command window from that folder
russy23 said:
First, connect your smartphone with your PC; plug in the USB cord in order to establish the connection.
On your computer access the Android SDK folder.
From there open a command prompt window: press and hold the Shift keyboard key while right clicking on any blank space.
Next, in the cmd window type “adb reboot bootloader” and wait while the bootloader mode is displayed on your smartphone
That's basically what I did and worked first time..make sure the adb and fastboot package is installed and open the command window from that folder
Click to expand...
Click to collapse
Did all that.. I mean I've flashed custom recoveries and roms to other phones before and never really had a problem i couldn't google..this has me stumped. It simply refuses to even access the bootloader.
If it helps it was a koodo phone and is running the latest official patch from lg on nougat. The only thing i could find online was that sprint supposedly removed all access to the bootloader on theirs, but i cant find any real info on that either. It reboots when i send the adb reboot bootloader but its like fastboot just isn't there..?? It reboots right back to the android home screen. Ive tried all possible key combos as well... Ugh
Which model is it..mines the h850
Ive got the h831
I think I've sort of answered my own question. From browsing the forums it appears the Canadian variant has the bootloader locked down and inaccessible, which would explain a lot..lol.. I really hate when this kind of thing is done to the consumer...ugh. Back to xiaomi i guess lol
bproulx said:
... has the bootloader locked down and inaccessible, which would explain a lot..lol.. I really hate when this kind of thing is done to the consumer...ugh. Back to xiaomi i guess lol
Click to expand...
Click to collapse
Interesting - my xianomi hat an locked bootloader and i had to ask for permission (for the phone I bought!) to unlock the bootloader.
LG is also locked, but the unlocking procedure is way easier.
logg.sar said:
Interesting - my xianomi hat an locked bootloader and i had to ask for permission (for the phone I bought!) to unlock the bootloader.
LG is also locked, but the unlocking procedure is way easier.
Click to expand...
Click to collapse
Unless you're from Canada apparently ..lol