Hello,
I now have a .bin containing this 1.00A bootloader; the file is 202 059 bytes long.
When in bootloader mode, the "l" command says "not allow operation", even after I type "task 32".
> How may I force the 1.06 bootloader to replace itself with a "polite" 1.00A version?
Thanks,
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!
Check if phone can be unlocked, type on Phone: *#*#7378423#*#*
If bootloader unlock allowed says Yes, then you’re able to unlock it, If it says No, or if the status is missing, then stop reading this and do root without bootloader unlock
Get your unlock code at sony website
Download Flashtool
Extract Fastboot.zip with 7zip
Enter Fastboot mode on phone, press menu button and you will see (Blue LED)
Press shift in and right click on Fastboot folder that you’ve extracted, click open command window here & type: [without quotes]
"fastboot.exe -i 0x0fce getvar version"
If you see java version then its working) if not, check drivers.
"fastboot.exe -i 0x0fce oem unlock 0xKEY"
Replace KEY with unlock code
Hi
Is it possiable to lock the bootloader after flashing android wear 5
or at least to remove the Bootloader Unlocked warning?
Thanks,
Dor
Yes. You can relock it.
1. Enable ADB Dubugging on the Watch
2. Type "adb reboot bootloader"
3. Once it boots to the bootloader, type "fastboot oem lock"
4. The device will restart and it should be locked
I got error when unlocking bootloader with flashtool (0.9.20.0)
FAILED (remote: Command not allowed)
I also tried with fastboot on commant prompt and got the same error.
And created a folder with my device's serial and put ulcode in it (folder is at flashtool/custom/mydevices) and got the error bootloader cannot be unlocked offically.
Rooting status in my device's service mode says unlock bootloader allowed:yes
My device is E6803
Is there anyone to help?
Any help?
Do you have OEM unlocking on in developer options?
Yeah man, I have. And that was the problem. Thanks for your help
Hi everyone I run my own phone repair shop i had a Customer bring a HTC u11 2PZC1000 in to repair was soft bricked with an attempted custom rom installation, then re lock of bootloader without flashing a system to it
The os version was still there however when the device booted a message appeared the device is corrupt cannot be trusted and will not boot,
Devixe specs were,
Fastboot oem readmid
2PZC10000
Fastboot oem readcid
htc_039
hTc download mode
***relocked***
***production***
htc_ocnuhl PVT S-ON
LK-1.0.0.0000
Radio-8998-002772TOV-1712061121
OpenDSP-V11.6.00347.CB8998_0711
OS-2.33.710.9
Dec 8 2017,21:29:54 (1002308)
Bootloader displayed killswitch enabled on the 3 options when trying to unlock with provided original unlock_code.bin that was provided on with the phone & returns not allowed on production build in bootloader, could not flash any stock recoveries or TWRP back to the device,
I used htc_fastboot with the htc_fastboot command syntax, then used minimal adb and fastboot 1.7msi & also power shell im using windows 8.1 couldn't get anything to flash to the customers phone i downloaded the OTA's & firmware from the google spreadsheet it had no file for the 2.33.710.9 section there the page it went to was 404 so I just downloaded all of the files with the same CID htc_039 in this case but still to no avail, one day however I stumbled upon the fix,
What i found that actually worked to repair the device was,
#1 went through the files in spreadsheet then downloaded all with the same CID as mine even though the main versions were different,
#2 tried to flash them all to see what was a signed or close to signed zip and what was garbage that needed to be deleted, (you will know by the RUU errors you face anything but RUU security fail zip from USB command ) means it probably won't work but try anyway,
narrowed it down to a few but the one that did end up working was main version 1.11.710.5, but this main Verision was 2.33.710.9 ??? Dont ask me how it worked twice as it needed to be flushed first time it said but it did,
#4 now to the only tool that works and I had already had it on my PC believe it or not but its the HTC 10 batch tool which can be found amongst where the Google spreadsheet Info is found,
#5 all I did was placed the .zip into the "com" folder which is located where ever the batch tool is installed in my case was C://Android/com,
#6 opened the batch tool selected option 3 to open fastboot terminal with the purple screen,(when entered location of the terminal should be "example" C://android/com on the screen) this is where you place your RUU.zip file.
#7 booted to download mode, plugged the device into the computer made sure drivers were installed properly and working.
#8 type into the terminal "fastboot oem rebootRUU"
phone will reboot to RUU mode.
#9 type into terminal "fastboot flash zip <file_name.zip>
it flashed all 28 zips twice as it needed to be flushed the first time, so there you go this helped me and now I hope it can help you all out with your broken U11 fix.
Enjoy
☆NOTE☆
when using the HTC 10 batch tool fastboot terminal you can use either standard "fastboot" syntax or the "htc_fastboot" syntax both work do not add " " or < > into the command syntax simply drag and drop the file if you do not wish to type the entire filename out.
☆Standard syntax☆
fastboot oem rebootRUU
fastboot flash zip "<example.zip>"
☆htc_fastboot syntax☆
htc_fastboot oem rebootRUU
htc_fastboot flash zip "<example.zip>"
☆☆☆EDIT☆☆☆ so it definitely works 100% I've been doing it again and again and again just to be sure,
However what I have noticed is that in download mode OS VERSION is 2.33.710.9 still,
But in the OS system settings in about phone & also HTC sync manager the OS VERSION is 1.03.710.7,
BUT it can also receive and install updates up until 1.28.xxx.x before it will not install any higher updates,
So may be best to unlock the bootloader & flash a newer RUU version to your device to OTA update.
Very strange indeed but just thought I'd better add it.
Thanks