Unlock Your Bootloader - Desire C {GUIDE}
DISCLAIMER
Code:
# I am not responsible if anything happens to your phone.
# I have tested this method and it works like a charm.
# Unlocking bootloader on HTC devices is not a big thing but yes it will void your warranty and if you mess up with your phone beyond its extent, then you will have to pay extra charges for that.
# First of all register yourself on the HTC Registration Website.
# Then go to the HTC – Unlock Bootloader and select “All Other Supported Models” at the end of the list in “Select Your Device” and the click “Begin Unlock Bootloader“.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
# After this you will have to accept the terms and agreement of HTC that it is not responsible if anything happens to your phone.
Now you will get the steps of Unlocking the Bootloader or perform these in the same way :-
AND THEN CLICK PROCEED TO THE NEXT STEP.
# Download the unlock_tools.zip file from here and extract it to a new folder in C:/Android/ (or select any short place like Desktop.)
# Now open the folder where you have extracted the contents of unlock_tools.zip (in this case C:/Android/) and press and hold SHIFT on your keyboard and then RIGHT-CLICK on mouse and then select “Open Command Window Here“.
In the command window type the following code:-
Code:
fastboot oem get_identifier_token
You will get a long message in which there will be some lines like this:-
Code:
<<<< IDENTIFIER TOKEN START >>>>
....................
....................
....................
....................
....................
<<<< IDENTIFIER TOKEN END >>>>
Their would be some combination of numbers and alphabets instead of the dots so just copy this code.
When copying the token, start with this line:
Code:
<<<< Identifier Token Start >>>>
And end with this line:
Code:
<<<<< Identifier Token End >>>>>
Now paste the copied code in the Device Token Code as in the picture below:-
You will receive an email (the one with which you registered on HTC Website) in which there will be an attachment Unlock_code.bin. Save this file in the same folder in which there is adb,fastboot etc. (in this case C:/Android/ THE ONE THAT YOU EXTRACTED) and then type the following code in the command window:
Code:
fastboot flash unlocktoken Unlock_code.bin
After a while your phone will reboot saying your bootloader is Unlocked......
Some Mistake
See i unlocked my bootloader around November and had elected Desire * instead of other devices
one topic exist already
identifier token to short!
vodafone nl locked thats weird
---------- Post added at 02:48 PM ---------- Previous post was at 02:41 PM ----------
keeps stuck at 0% flashing unlock code bin
papasieg said:
identifier token to short!
vodafone nl locked thats weird
---------- Post added at 02:48 PM ---------- Previous post was at 02:41 PM ----------
keeps stuck at 0% flashing unlock code bin
Click to expand...
Click to collapse
Use this one http://forum.xda-developers.com/showthread.php?t=2367385
Related
Hi,
i have rooted my phone and applied newest recovery following every instruction on this site to the letter.
also installed and using fyodor's excellent rom since it's first release.
when i use adb i always obtain root # and have done so since flashing and entering commands
but when i try to access root on my phone (root explorer for example) i am now unable to mount rw/ro?? and cannot browse files. i also use cachemate which appears to gain root access and do its job
any help much appreciated as to how to solve this issue and allow my phone to recognise root
thank you for any help
Hi huetson2:
Try to execute the command below(on PC):
Code:
adb shell ls -l /system/sbin/su
If you get this output, I think rootExplorer and others(e.g.: Autostarts, setCPU) will work properly.
Code:
-rwsr-sr-x root root 76232 2008-08-01 20:00 su
cn.fyodor said:
Hi huetson2:
Try to execute the command below(on PC):
Code:
adb shell ls -l /system/sbin/su
If you get this output, I think rootExplorer and others(e.g.: Autostarts, setCPU) will work properly.
Code:
-rwsr-sr-x root root 76232 2008-08-01 20:00 su
Click to expand...
Click to collapse
-rwsr-sr-x root root 76232 2008-08-01 13:00 su
but still no root on phone!, got an error message on handset telling me su cannot be found?
setcpu not working either,
I have a similar problem. I'll post a screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: adding some info... If I type "su" from terminal emulator, it says something like "access granted, courtesy of magicandroidapps.com.
Root explorer works ok...
Chackemate and SetCPU work...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. Download this zip file and extract it.
2. Hold Shift and then Right click inside the extracted folder and then click on
"Open Command Window here"
3. Connect your device to PC (Make sure that usb debugging is enabled).
4. In command window type
"adb reboot bootloader" //This will boot your phone into fastboot mode.
5. Then type
"fastboot boot twrp.img" //This will boot the device into TWRP recovery temporarily.
6. In recovery click mount -> check system.
7. Now type
"adb pull /system/build.prop" //This will copy the build.prop in the fastboot folder.
8. Open the build.prop using notepad++ (simple notepad may corrupt the file)
9. Find "ro.build.type=user" and change it to " ro.build.type=userdebug"
Then save it.
10. Now type
"adb push build.prop /system/" //this will push the edited build.prop.
11. Now type
"adb shell"(press enter)
"cd system"(press enter)
"chmod 644 build.prop"(press enter)
"exit" (press enter)
12. Type "adb reboot" //to reboot your device
13. Now go in Developer options in setting and enable Multi-window mode
14. enjoy:laugh:
HIT THANKS IS YOU LIKE THIS GUIDE
Error: Device offline
It shows me this error. What should I do?
error: device offline
check adb driver in device manager windows,up date
[email protected] said:
It shows me this error. What should I do?
error: device offline
Click to expand...
Click to collapse
Help!!!!!
bro i have extreated the fastboot file i didnt see the build prop file..................................so what can i do now................please help
Do I need an unlocked bootloader for this?
C:\Users\Elias\Desktop\Fastboot\Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.312s]
booting...
FAILED (remote failure)
finished. total time: 0.315s
C:\Users\Elias\Desktop\Fastboot\Fastboot>
Nera2600 said:
Do I need an unlocked bootloader for this?
C:\Users\Elias\Desktop\Fastboot\Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.312s]
booting...
FAILED (remote failure)
finished. total time: 0.315s
C:\Users\Elias\Desktop\Fastboot\Fastboot>
Click to expand...
Click to collapse
failed for me too
ArvinLam said:
failed for me too
Click to expand...
Click to collapse
9. Find "ro.build.type=user" and change it to " ro.build.type=userdebug"
Then save it.
Change these lines in system build.prop then reboot goto developer options nd enable it
dsbhai said:
9. Find "ro.build.type=user" and change it to " ro.build.type=userdebug"
Then save it.
Change these lines in system build.prop then reboot goto developer options nd enable it
Click to expand...
Click to collapse
thanks
me too..
you find any solution?
question
working fine in android one thanks....Does it work only on android one or any rooted phone?
error
device not found!!!
fail
C:\Users\William\Desktop\Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.277s]
booting...
FAILED (remote failure)
finished. total time: 0.294s
what to do?
Hi,
I'm interested in hacking some of the existing apps to see how they tick, since most of them are just HTML + CSS. I've been sleuthing around trying to find how to enable the remote debugging port of Chrome which is usually available (and even officially for apps that you actually register yourself). I've found
Code:
/data/chrome/.eureka.conf
contains a enable_remote_debugging flag which is currently set to false, is it as simple as modifying the file to say true? Does anyone know if this file is checksummed or have any other checking preventing me from modifying it? I normally would go right ahead but I don't want to brick the device, so I'm posting here for some reassurance/guidance.
Cheers,
Did it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Posting it here in case someone is trying to achieve the same/similar things with their own Chromecast.
HOW TO: Add (any?) Chrome command-line argument to the Chromecast shell / Get the remote DevTools working.
Note: You will need root access to your Chromecast to perform these steps. This guide assumes you have busybox installed and on your PATH
SSH into your Chromecast, this is usually just ssh [email protected], although you may need to specify an IP address in place of Chromecast if your router does not automatically create a DNS entry for it.
Optional: once in your SSH session type busybox sh to get a terminal that supports history and tab completion.
Copy the process.json file somewhere you can modify it and make it readable for the 'chrome' user:
Code:
busybox cp /system/chrome/process.json /data/chrome/process.json
chown chrome:chrome /data/chrome/process.json
Modify the process.json file to add "enable-remote-debugging" and "remote-debugging-port" (or whatever other flags you want to use) to the cast_shell external_flags JSON array and save the file. The only editor I found on the device was busybox's vi, so you'll need to know the basics to modify that file, or use adb and modify it elsewhere.
Extract the environment variables from the running cast shell process
Code:
ps | grep cast_shell # take note of the PID
busybox xargs -0 busybox echo < /proc/1234/environ # where 1234 is the PID from the previous step
Copy that line for later, the output should something look like: (you can most likely copy this, but it may change depending on your firmware version)
Code:
LD_LIBRARY_PATH=/system/lib PLAYREADY_STORE_DIR=/data/netflix/AACS/ CAST_CLIENT_CERT=/factory/client.crt CAST_CLIENT_PRIVKEY=/factory/client.key.bin CAST_CLIENT_CERT_CHAIN=/system/etc/cert_chain.pem HOME=/data/chrome/
Switch to the 'chrome' user (the groups may be different for your firmware, check by reading /init.rc and looking under groups for cast_receiver service)
Code:
sudo -u chrome -g chrome:graphics:wifi:net_mgr:watchdog:log:panel:metrics /bin/busybox sh
Now paste that line on ENV vars and on the same line type:
Code:
/system/chrome/cast_cli stop cast
Your TV may turn off at this step. You can safely turn it back on.
Paste the line of ENV vars again and then again on the same line type:
Code:
/system/chrome/cast_cli --process-json-path=/data/chrome/process.json --enable-remote-debugging --remote-debugging-port=9222 start cast
If you are running adb logcat in another window, you should start to see cast_shell starting up. If it crashes, be sure to read the log to find out what's going wrong. It normally takes 10-30 seconds to show the backdrop again on the screen.
Now that the cast shell is running in debug mode, you should be able to navigate to http://chromecast:9222 and inspect your browser window remotely (or replace chromecast with your IP address).
Enjoy!
[REDACTED FOR PRIVACY REASONS]
[REDACTED FOR PRIVACY REASONS]
Get unlock key from official Motorola site. You will have to enter it to unlock. Obviously it will void warranty
[REDACTED FOR PRIVACY REASONS]
Same here.
Shows some error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[REDACTED FOR PRIVACY REASONS]
ava2048 said:
You found a solution buddy?
Let me know when you find something.
Click to expand...
Click to collapse
No.
Tried to unlock many times. No output other than error.
Code:
C:\adb>fastboot oem get_unlock_data
(bootloader) slot-counttas: not found
(bootloader) slot-suffixe: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: 0.001s/CODE]
I have asked in telegram group.
jamespauljose said:
No.
Tried to unlock many times. No output other than error.
Code:
C:\adb>fastboot oem get_unlock_data
(bootloader) slot-counttas: not found
(bootloader) slot-suffixe: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: 0.001s/CODE]
I have asked in telegram group.[/QUOTE]
i am waiting for the answer of same question. please experts give answer.
Click to expand...
Click to collapse
Same problem here
drvikasjoshi said:
Get unlock key from official Motorola site. You will have to enter it to unlock. Obviously it will void warranty
Click to expand...
Click to collapse
I have the same problem here, the "fastboot oem get_unlock_data" command just hangs. I've tried leaving it for a few minutes, but it still doesn't work. Which is especially strange, considering X number of Youtubers/other users get the key in mere seconds! And yes, my model number matches, settings are correct, etc.
You can just use the computer of Windows XP system inside
Sorry,my English is not standard,but you must be understand
caocanhong said:
You can just use the computer of Windows XP system inside
Sorry,my English is not standard,but you must be understand
Click to expand...
Click to collapse
Windows XP won't support modern USB systems. It won't even run ADB, forget about unlocking anything.
Today i got an issue for my N960F after flashing a custom ROM. I'm not sure till now what've gone wrong, but after rebooting my device i faced an issue that my SIM card can not register on network.
Cellular network signal is full, but can not make any calls and can not connect to data.
Tried to restore through TWRP with a nand backup, but always fails as EFS partition can not be mounted. Eventually I managed to restore my EFS partition after following the hereunder steps.
I'll just leave it here if anyone faced the same in the future.
Disclaimer: You are doing this at your own risk. I shall not be held liable for any losses or bricked devices ( They already are )
Pre requisites:
- ADB on your PC, latest SDK is preferred.
- Custom recovery ( with ADB enabled )
- Better to have a previous EFS backup
Steps:
- Reboot into recovery and enable ADB ( in TWRP, ADB is enabled by default )
- Attach your device to your PC. and open your terminal or command prompt as an admin.
- Type the following commands:
- Navigate to your ADB folder ( in my case it is C:/ADB )
cd C:/ADB
- Ensure that your phone is readable in ADB mode
c:\ADB>adb devices[ATTACH type="full"]5610649[/ATTACH]
c:\ADB>adb shell
Your terminal handle should change into root ~ #
~ # cd /dev/block
/dev/block # ls
you should get an output like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
/dev/block # cd by-name
/dev/block/by-name # ls -la
you should see device partitions listed as this .. EFS partition is highlighted in yellow and is on sda3 as below
/dev/block/by-name # mke2fs /dev/block/sda3
and you should be prompted by a message to proceed or not. Press y then enter
Finally,
/dev/block/by-name # mount -w -t ext4 /dev/block/sda3
We successfully formatted and mounted EFS partition and now either to restore your old EFS backup or flash stock firmware through ODIN.
Resources: