Database Develop

[GUIDE]Unlocking Bootloader - Desire C {Step-to-Step}

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

[Enable Feature][100% Working] Enable Multiwindow in Android 6.0 without Root

{
"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?

Device is LOCKED. Status Code: 2 and failed to validate system image

Hi !
I have a problem with my Moto 2gen 2014 LTE (THEA). Firstly I unlock my bootloader using command : #fastboot oem unlock 'code' and install TWRP and custom ROM Lineage OS 14.1. In this ROM my SIM card was not detected and I'm going to lock my bootloader (Command: # fastboot oem lock 'code) and install stock ROM. Now when I turn the phone immediately enter into fastboot mode, and shows me :
Device is LOCKED. Status Code: 2
failed to validate system image
Fastboot Reason: Fall-throught from normal boot mode USB connected.
{
"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"
}
I try several times to boot the new system, but every time is the same
When i try unlock my bootloader cmd shows me :
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.030s
whether it is still somehow saved? Please, help me.
(Sorry for my bad english)

Have you fix it yet? I have the same problem....

b4toons said:
Hi !
I have a problem with my Moto 2gen 2014 LTE (THEA). Firstly I unlock my bootloader using command : #fastboot oem unlock 'code' and install TWRP and custom ROM Lineage OS 14.1. In this ROM my SIM card was not detected and I'm going to lock my bootloader (Command: # fastboot oem lock 'code) and install stock ROM. Now when I turn the phone immediately enter into fastboot mode, and shows me :
Device is LOCKED. Status Code: 2
failed to validate system image
Fastboot Reason: Fall-throught from normal boot mode USB connected.
I try several times to boot the new system, but every time is the same
When i try unlock my bootloader cmd shows me :
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.030s
whether it is still somehow saved? Please, help me.
(Sorry for my bad english)
Click to expand...
Click to collapse
select option 4 ,format device and reflash rom

Hay !!
After you lock your bootloader then flash the Entire ROM and make sure after flashing use those two command
$ fastboot erase userdata
$ fastboot erase cache
then reboot
$ fastboot reboot

Hi, sorry for necroposting. Did you fix it?

Help with finding stock recovery

Hi,
I have been given an old Huawei P9 from a friend who tried to install a custom ROM on it, which apparently didn't go so well. The phone doesn't seem to boot past the bootloader unlocked message. He asked me to try to recover it so he could use it temporarily as his current phone died.
It appears to have TWRP 3.1.1.0 installed, but from what I can tell TWRP can't mount the /data folder, I haven't really looked into that issue much as I was hoping to just reinstall the stock recovery and take it back to stock, but struggling to find/understand instructions. Hope there is someone that can still help, any help would be appreciated.
It is an Australian (carrier: Optus) model EVA-L09, and that's about all I can tell as fastboot doesn't seem to be able to get much else
Code:
fastboot.exe oem get-bootinfo
(bootloader) unlocked
OKAY [ 0.006s]
Finished. Total time: 0.009s
fastboot.exe oem get-product-model
(bootloader)
OKAY [ 0.006s]
Finished. Total time: 0.069s
fastboot.exe getvar vendorcountry
vendorcountry: optus/au
Finished. Total time: 0.007s
fastboot.exe oem get-build-number
(bootloader) :
OKAY [ 0.004s]
Finished. Total time: 0.007s
fastboot.exe oem oeminforead-System_Version
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed

greyjoy said:
I have been given an old Huawei P9 from a friend who tried to install a custom ROM on it, which apparently didn't go so well. The phone doesn't seem to boot past the bootloader unlocked message. He asked me to try to recover it so he could use it temporarily as his current phone died.
It appears to have TWRP 3.1.1.0 installed, but from what I can tell TWRP can't mount the /data folder, I haven't really looked into that issue much as I was hoping to just reinstall the stock recovery and take it back to stock, but struggling to find/understand instructions. Hope there is someone that can still help, any help would be appreciated.
It is an Australian (carrier: Optus) model EVA-L09, and that's about all I can tell as fastboot doesn't seem to be able to get much else
Click to expand...
Click to collapse
Are there really no answers (even no "Failed") to some commands - try to execute again and attach also screenshot from PC
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
PAUSE
REM fastboot getvar rescue_enter_recovery

zgfg said:
Are there really no answers (even no "Failed") to some commands - try to execute again and attach also screenshot from PC
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
PAUSE
REM fastboot getvar rescue_enter_recovery
Click to expand...
Click to collapse
No other errors that I can see when I run the oem commands at least, see 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"
}

greyjoy said:
No other errors that I can see when I run the oem commands at least, see screenshot
Click to expand...
Click to collapse
This is all very strange. Even after custom ROM and/or brick it should know to answer on get-product-model or get-build-number.
Maybe only if some ... deleted all partitions by TWRP or so?!
Just one suggestion. Forget Platform tools and install to the PC very simple and small (only few MB) "Minimal ADB and Fastboot" package and execute from there (you don't need to type "fastboot.exe", just "fastboot" is enough)
Do you know at least, was it Android 6, 7 or 8. Almost certainly not 8, it would be CN, not AU. 6 only if stock was not updated from the beginning
From the TWRP version I would guess it was Nougat, i.e. EMUI 5.
In that case you can install generic/no-check version of Nougat stock recovery:
https://mega.nz/file/09k1wIST#IyMKcRwPq7llKEmnflOAQJSl2B4v8pmz6Myj_ZawxQs
You should also know was it L09 Single SIM or L19 Dual SIM
Searching for custs, Australia might be c636 or c183 but seems that c34 was Australia Optus
Find on FirmwareFinder or from:
https://pro-teammt.ru/firmware-database/?firmware_model=EVA-L09c34
"FullOTA-MF-PV" (only PV are suitable for DLOAD) firmware for e.g. EVA-L09c34, like EVA-L09c34b380 (pkg #93280 from 2017.08.15) and try simple DLOAD method
But if really all partitions were deleted, DLOAD would likely fail. You could try (with your c34, not c432 as in the guide) something like this:
https://forum.xda-developers.com/showpost.php?p=74169408&postcount=7

General [VENDOR][EOL] Stock Vendor with No Oversharpening

So, you just got your new Redmi Note 10S and the software sucks. So you decided to flash a GSI, got it working and you still have one problem left, the video look oversharped and the colors might look weird. Well, this vendor will fix 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"
}
So what's new in this vendor?
A little bit debloated
And ofcourse, no oversharpening.
Anything else?
Nothing else, literally just that.
Download Link:
Google Drive
Requirements:
1. Unlocked bootloader.
2. A PC with fastboot tools.
3. Reading ability.
Flashing Process:
1. Reboot your phone into bootloader.
2. Check if fastboot detects your device.
3. Type fastboot reboot fastboot to reboot into fastbootd.
4. After that, type fastboot flash vendor path/to/vendor.img
5. That's it. Reboot and enjoy!
KEEP IN MIND
This vendor only has been tested on DotOS 5.1.3. If you possibly can, please try this on MIUI, and if it doesn't boot, report it to me. Thanks.
Now try watching video at 360p, and you might see a difference.

It failed:
target reported max download size of 134217728 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/8 (130795 KB)...
OKAY [ 2.928s]
writing 'vendor' 1/8...
FAILED (remote: This partition doesn't exist)
finished. total time: 2.933s
Any idea what happened?

It actually works with MIUI as well. However, color management seems to be disabled leaving the phone to oversaturate the colors at will.
EDIT 1: It's not just the color management that gets disabled. Changing the color temperature gets disabled, reading mode gets disabled as well. It seems like trying to solve one problem causes more.
EDIT 2: It could be solved by tweaking ro.vendor.mtk_pq_color mode. With this vendor, it's set to 1 which may be the reason why the phone is stuck in the "Saturated" mode.

EL66K said:
It failed:
target reported max download size of 134217728 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/8 (130795 KB)...
OKAY [ 2.928s]
writing 'vendor' 1/8...
FAILED (remote: This partition doesn't exist)
finished. total time: 2.933s
Any idea what happened?
Click to expand...
Click to collapse
you must flash it on fastbootd , using fastboot reboot fastboot or adb reboot fastboot. try to flast it again on every partition (a and b)

jacobpayag said:
It could be solved by tweaking ro.vendor.mtk_pq_color mode
Click to expand...
Click to collapse
How can i change this value? If i try edit build.prop on /vendor folder, this file erased and phone not boot again. Any try for restoring file from adb failed...

hey guys, this project is EOL. Please use my LiteE RN10S ROM instead, the ROM has no oversharpening while maintaining every display color related stuff.

J6idot said:
hey guys, this project is EOL. Please use my LiteE RN10S ROM instead, the ROM has no oversharpening while maintaining every display color related stuff.
Click to expand...
Click to collapse
Hey bro can you please provide device vendor (not .img)