how to change HTC 820u CID no - Desire 820 General

Hey guys pls I need every one knowledge to change HTC 820 dual cid to update the KK very

Connect your device to your computer using an USB cable and reboot your device into boot loader by typing the following command in the command prompt.
adb reboot bootloader
Now type the following command in the Cmd to change the CID on your device:
fastboot oem writecid <CID name>
Now reboot your device using the following command:
fastboot reboot
That’s it, you have successfully changed the CID on your device.
Note: S-Off Must Needed!

AFAIK, XTC2Clip is the only tool out there that can S-OFF Desire 820. And it costs some USD$10 to do it if you wish to S-OFF at a local electronics shop.

thx guys for helping

nazmul0046 said:
Connect your device to your computer using an USB cable and reboot your device into boot loader by typing the following command in the command prompt.
adb reboot bootloader
Now type the following command in the Cmd to change the CID on your device:
fastboot oem writecid <CID name>
Now reboot your device using the following command:
fastboot reboot
That’s it, you have successfully changed the CID on your device.
Note: S-Off Must Needed!
Click to expand...
Click to collapse
Yup it's off ty broo

Related

Computer recognises phone but phone doesn't think it's connected?

I'm trying to unlock the bootloader so that I can flash a custom recovery.
I've enabled both unlocking the bootloader and USB debugging and the computer recognizes the phone when I type "fastboot devices" in the terminal. When on the bootloader screen i've wrote "adb devices" and the computer recognised the phone.
I've then typed "fastboot flashing unlock" and a list of commands come up. The same list comes up even when I type "sudo fastboot flashing unlock".
"sudo fastboot oem" unlock gives me a FAILED (remote: unknown command) message.
What can be the cause of this problem?
My linux computer recognizes my phone when I type fastboot devices, but judging by the last line on the bootloader the phone doesn't think it's connected to the computer.
tbh just use nexus root toolkit
CloudPaganini said:
I'm trying to unlock the bootloader so that I can flash a custom recovery.
I've enabled both unlocking the bootloader and USB debugging and the computer recognizes the phone when I type "fastboot devices" in the terminal. When on the bootloader screen i've wrote "adb devices" and the computer recognised the phone.
I've then typed "fastboot flashing unlock" and a list of commands come up. The same list comes up even when I type "sudo fastboot flashing unlock".
"sudo fastboot oem" unlock gives me a FAILED (remote: unknown command) message.
What can be the cause of this problem?
My linux computer recognizes my phone when I type fastboot devices, but judging by the last line on the bootloader the phone doesn't think it's connected to the computer.
Click to expand...
Click to collapse
Try fastboot oem unlock.
fastboot flashing oem unlock.
http://www.androidpolice.com/2015/1...become-common-for-many-devices-in-the-future/

Unlocking bootloader unofficially?

Hey guys! Is there any way to unlock Redmi Pro's bootloader without waiting for permission from Xiaomi? Have anybody found a way to bypass it?
easy, first make sure you have spflash tool and a working fastboot rom (just in case of trouble)
Next make sure your computer has working fastboot and adb.
Enable USB debugging on the device.
Enable OEM unlock in the Developer options settings on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine.
From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
Device is wiped & unlocked & no OS
Now flash twrp, reboot into it and copy xiaomi.eu rom on card & install
Good luck
hello i haven't on my xiaomi redmi pro eom unlock in the devlopper mode help me pls
criszz said:
easy, first make sure you have spflash tool and a working fastboot rom (just in case of trouble)
Next make sure your computer has working fastboot and adb.
Enable USB debugging on the device.
Enable OEM unlock in the Developer options settings on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine.
From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
Device is wiped & unlocked & no OS
Now flash twrp, reboot into it and copy xiaomi.eu rom on card & install
Good luck
Click to expand...
Click to collapse
press in settings about phone 7 time on miui version
after that you will find developer options in aditional settings
criszz said:
press in settings about phone 7 time on miui version
after that you will find developer options in aditional settings
Click to expand...
Click to collapse
Sadly there is no oem unlock option in developer options. I'm on MIUI 8.1.2.0 Stable (MHQCNDI)
EDIT: i just switched to Developer ROM and still nothing.
sorry, my mistake i use another laguage, activate usb debuging , conect to the pc and run adb , if some permision asked alow
I can't unlock it using fastboot oem unlock since it's mediatek device =/ When I try I get
(bootloader) Start unlock flow
FAILED (remote:
Unlock failed - Err:0xffffffff
)
finished. total time: 0.016s"
Click to expand...
Click to collapse
i unlocked that way, maybe you do something wrong
try another way without unlocking try flash twrp with spflash tool
Do you remember what miui version did you have when you unlocked this way? Maybe I can roll back to it and then try again. Were you using developer or stable rom?
i was on fake/vendor rom this i thinlk http://blog.geekbuying.com/index.ph...ndroid-6-0-smartphone-firmware-212302-161109/
Crissz, your bootloader was allready unlocked when you received your phone. You cannot do a simple oem unlock via fastboot with a xiaomi phone. It's a fact..
@KarKlim please try fastboot oem unlock-go comand too
This method does not work as many say
(bootloader) Start unlock flow
FAILED (remote:
Unlock failed - Err:0xffffffff
)
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Redmi Pro with Latest stable china rom
Is it possible? Xiaomi regoke my unclock previleges and now i have my Redmi Pro stuck in China Developer Rom. No way to install multilanguase Xiaomi.eu... can someone help please?
Maybe try with a new xiaomi account with different sim card.
And then from a different internet ip, from your friend or something.
I have no idea how they collect data or what. I'm just guessing here.
wow great news for Xiaomi lovers:
wow great news for Xiaomi lovers:
GeekBuying offering 73% off ( Xiaomi Redmi Pro 3GB + 64GB) 184.65 EURO
spam, all post of this user is spam
So, I bought my Redmi Pro today and i want to install xiaomi.eu ROM. Do I have to unlock bootloader first? Or can I do it with unlock bootloader?
No OEM in my xiaomi redmi pro
[[/B]
criszz said:
easy, first make sure you have spflash tool and a working fastboot rom (just in case of trouble)
Next make sure your computer has working fastboot and adb.
Enable USB debugging on the device.
Enable OEM unlock in the Developer options settings on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine.
From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
Device is wiped & unlocked & no OS
Now flash twrp, reboot into it and copy xiaomi.eu rom on card & install
Good luck
Click to expand...
Click to collapse
Can you help me please because I don't have a OEM unlock option in redmi pro and how to unlock bootloader... please man
criszz said:
easy, first make sure you have spflash tool and a working fastboot rom (just in case of trouble)
Next make sure your computer has working fastboot and adb.
Enable USB debugging on the device.
Enable OEM unlock in the Developer options settings on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine.
From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
Device is wiped & unlocked & no OS
Now flash twrp, reboot into it and copy xiaomi.eu rom on card & install
Good luck
Click to expand...
Click to collapse
Not worked for redmi note 8 pro ......failed.....

How can i unlock bootloader

Sir, i have micromax A120 2 colours (4GB). I have rooted it(using kingroot) and flashed cwm recovery. Now i want to unlock bootloader. When i gave command on adb and fastboot "adb devices" then MT6582 appeared, but i don't know the appropriate command to unlock my device's bootloader. Sir please provide me the commands along with details.
Yashwant Koshta said:
Sir, i have micromax A120 2 colours (4GB). I have rooted it(using kingroot) and flashed cwm recovery. Now i want to unlock bootloader. When i gave command on adb and fastboot "adb devices" then MT6582 appeared, but i don't know the appropriate command to unlock my device's bootloader. Sir please provide me the commands along with details.
Click to expand...
Click to collapse
U don't have to unlock bootloader. Old mtk phones don't have the bootloader locked.
adb devices shows the devices connected to your computer.
" fastboot oem unlock " [In Fastboot Mode ]
goludr said:
" fastboot oem unlock " [In Fastboot Mode ]
Click to expand...
Click to collapse
Sir, I think we don't have to unlock bootloader because it is already unlocked that's why I have successfully installed custom rom without doing so.
However thanks to reply sir.

Can not unlock bootloader 21s (oem unlock is not allowed)

I have followed the guides to the best of my ablity
This is the procedure I followed: From this thread
Have ADB/Fasboot tools on your computer (I am not helping you here, it you're lucky, maybe your friends will help)
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device (again, I'm not helping with that)
Make sure adb can see your device when you run "adb devices"
Run "adb reboot bootloader"
Run "fastboot devices" to make sure you see your device
Run "fastboot oem unlock-go" to unlock your device temporarily
FAILED (remote: oem unlock is not allowed)
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.100s]
finished. total time: 0.100s
I then tried to downgrade to s19, but does not seem to work.
Anyway, if anyone has any ideas it would be welcomed, thank you
Is there an option you can turn on in dev options called "allow bootloader unlocks"? Because my mom's Le 2 has it and I assume it allows the unlock to go through. Are you on a vendor ROM? Flash the original stock Chinese 18s for your device.
Closest setting like that I have is the "OEM unlock" and I have it enabled
Well, did you have it enabled back when you were trying to unlock it? Because not having it enabled is usually what causes the unlock to fail.
Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
Code:
fastboot flash aboot emmc_appsboot.mbn
You may need to do the XBL as well:
Code:
fastboot flash xbl xbl.elf
Then
Run
Code:
fastboot reboot bootloader
and then
Code:
fastboot oem device-info
to verify.
slgooding said:
Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
Code:
fastboot flash aboot emmc_appsboot.mbn
You may need to do the XBL as well:
Code:
fastboot flash xbl xbl.elf
Then
Run
Code:
fastboot reboot bootloader
and then
Code:
fastboot oem device-info
to verify.
Click to expand...
Click to collapse
I will try this asap, thanks
Woot! that worked
Hey can i lock the bootloaded after I am done? I want to use like android pay and stuff
Well I figured out I can relock it, bit now my issue is when I am in fastboot mode adb does not see the device...
I installed the drivers, did not work....
Even went to my wife's laptop that I have never once plugged my phone in to... Installed adb, and plugged in the phone in fastboot... Still not being seen when I do an "adb devices"
I really want to use android pay
Don't understand
slgooding said:
Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
Code:
fastboot flash aboot emmc_appsboot.mbn
You may need to do the XBL as well:
Code:
fastboot flash xbl xbl.elf
Then
Run
Code:
fastboot reboot bootloader
and then
Code:
fastboot oem device-info
to verify.
Click to expand...
Click to collapse
Hi I know this is a older thread but I cannot get past the oem unlock is not allowed on my pro 3. I have all the drivers installed and the cmd recognizes my device but when I try to unlock I get the error. I downloaded the files you provided and when I try to insert from fastboot on command prompt it says the files is not recognized as internal or external command. I don't know what else to do at this point. Any help would be appreciated.
bobster82 said:
Hi I know this is a older thread but I cannot get past the oem unlock is not allowed on my pro 3. I have all the drivers installed and the cmd recognizes my device but when I try to unlock I get the error. I downloaded the files you provided and when I try to insert from fastboot on command prompt it says the files is not recognized as internal or external command. I don't know what else to do at this point. Any help would be appreciated.
Click to expand...
Click to collapse
Make sure ur files are in the right directory or cd to where they are.
bobster82 said:
Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
You may need to do the XBL as well:
Then
Run
and then
Hi I know this is a older thread but I cannot get past the oem unlock is not allowed on my pro 3. I have all the drivers installed and the cmd recognizes my device but when I try to unlock I get the error. I downloaded the files you provided and when I try to insert from fastboot on command prompt it says the files is not recognized as internal or external command. I don't know what else to do at this point. Any help would be appreciated.
Click to expand...
Click to collapse
You need adb installed on your computer.
You don't need adb installed, you just need platform-tools. https://www.xda-developers.com/install-adb-windows-macos-linux/
You usually have to preface every command with adb shell. So after enabling USB Debugging and connecting to your device (make sure to allow your PC on your phone when the prompt comes up), type adb shell fastboot flash aboot emmc_appsboot.mbn in the terminal.
thanks everyone. I tried everything suggested and nothing worked. I switched to my wifes computer witht he same files and seemed tp brick the pro 3. How in the world did I do this through adb?
bobster82 said:
thanks everyone. I tried everything suggested and nothing worked. I switched to my wifes computer witht he same files and seemed tp brick the pro 3. How in the world did I do this through adb?
Click to expand...
Click to collapse
Do you have fastboot yet if not you will have to try to unbrick it.
Which model do you have?
Sent from my LEX720 using xda premium
mchlbenner said:
Do you have fastboot yet if not you will have to try to unbrick it.
Which model do you have?
Sent from my LEX720 using xda premium
Click to expand...
Click to collapse
I dontI don't its bricked bricked. When I plug it in it comes up as hus9009 ..I have the US model 727
bobster82 said:
I dontI don't its bricked bricked. When I plug it in it comes up as hus9009 ..I have the US model 727
Click to expand...
Click to collapse
Power of push power down and volume down when you are plugged in to your PC.
Make sure you adb installed on your computer.
What did you flash on your phone.
Sent from my LEX720 using xda premium
mchlbenner said:
Power of push power down and volume down when you are plugged in to your PC.
Make sure you adb installed on your computer.
What did you flash on your phone.
Sent from my LEX720 using xda premium
Click to expand...
Click to collapse
see this the only thing I don't understand. I booted into fastboot and attempted to flash the files eemc and the xl files to unlock bootloader. The first try gave me an error and then the screen went black and has not come back on yet. No vibrations,no lights, no nothing.
---------- Post added at 05:09 PM ---------- Previous post was at 05:07 PM ----------
sk8223 said:
You don't need adb installed, you just need platform-tools. https://www.xda-developers.com/install-adb-windows-macos-linux/
You usually have to preface every command with adb shell. So after enabling USB Debugging and connecting to your device (make sure to allow your PC on your phone when the prompt comes up), type adb shell fastboot flash aboot emmc_appsboot.mbn in the terminal.
Click to expand...
Click to collapse
I had all the files you listed and followed to a T and for some reason it bricked my device. Any idea how to resurrect it?
bobster82 said:
I had all the files you listed and followed to a T and for some reason it bricked my device. Any idea how to resurrect it?
Click to expand...
Click to collapse
Well, I simply rephrased slgooding's post in this thread. See the first page. And by brick, I assume you only have fastboot working.
Try the other commands: https://forum.xda-developers.com/showpost.php?p=74123111&postcount=5
hey I got it unbricked by using the flash 2.0 method. The only thing is now its reading 720 instead of 727. Also When I get into FASTBOOT it says the bootloader is already unlocked but when I try put twrp recovery into the command prompts its telling me the image file is corrupt. What am I doing wrong with this adb command?
bobster82 said:
hey I got it unbricked by using the flash 2.0 method. The only thing is now its reading 720 instead of 727. Also When I get into FASTBOOT it says the bootloader is already unlocked but when I try put twrp recovery into the command prompts its telling me the image file is corrupt. What am I doing wrong with this adb command?
Click to expand...
Click to collapse
Make sure you have correct image recovery for your device.
Redo due unlocking commands you may have flash a bootloader on it.
What build are you on
Sent from my LEX727 using xda premium
mchlbenner said:
Make sure you have correct image recovery for your device.
Redo due unlocking commands you may have flash a bootloader on it.
What build are you on
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Hi I made sure I downloaded the correct twrp recovery and when I command in prompt its telling me now that it cannot load the image error. the build is Le_zl1 -eng 6.0.1 WAXCNFN5841510281D eng.letv.
I'm almost fixing to give up cause no matter what I do I cannot get into twrp recovery

Cannot Unlock Bootloader of Coolpad Cool 1

hi .
i cannot Root Coolpad Cool 1
when enter this command to adb : fastboot oem unlock-go
H:\New folder (3)\A\platform-tools_r30.0.3-windows\platform-tools>adb reboot boo
tloader
error: no devices/emulators found
H:\New folder (3)\A\platform-tools_r30.0.3-windows\platform-tools>
All drives & ADB are installed
No phone detection when fast boot
sorry; cannot speak english ...
This phone doesn't respond to fastboot unlock command.
First you need to enable usb debugging and allow OEM unlock in developer options.
Then you just flash TWRP recovery , by using Qualcomm QPST flash tool.
Once you have TWRP installed , flash Magisk to root the phone.
Search the threads here , there are a few Twrp/rooting guides that you can follow.
Sent from my C103 using XDA Labs

Categories

Resources