Related
Good evening!
I'm new to this so ill try to be as specific as I can. about a month ago I've bought the One x from a private store here in Israel and i think it was from taiwan or something. anyways, a couple of days ago i started messing with it, rooting it and everything.
I unlocked the bootloader via the htcdev.com, did the whole CMD thing and everything and flashed the android revolution HD rom (thats the name?)
so it was great and everything but it wasnt as complete as the rom my phone came with (I guess its the stock rom) so i tried the RD MIUI rom and it was fine, but still not what i was looking for and so i realized i need to come back to the stock rom, simple and clean.
now after the whole unlocking and rooting and everything, how the hell do i get my stock rom back? i want to lock back my phone, unroot it and put the old rom back on it and im very new to this whole HTC rooting thing, since i was using the galaxy s 1 and 2 before the HTC.
I searched the forum and couldnt find a guide, every post here is just links but no TUT's, as if everyone already knows everything!
anyways, I would really appreciate anybody helping me!
my phone is the international version i guess, bought in israel shipped from some asian country but is unlocked to all carriers and everything, not an AT&T version or anything.
First thing, make sure what is your original software version.
If you're not sure, run this in fastboot mode
go to bootloader
type fastboot getvar version-main
tell us what no. it show
then will be the next step to get the correct RUU for your device
ckpv5 said:
First thing, make sure what is your original software version.
If you're not sure, run this in fastboot mode
go to bootloader
type fastboot getvar version-main
tell us what no. it show
then will be the next step to get the correct RUU for your device
Click to expand...
Click to collapse
version-main: 1.29.707.11
finished. total time: 0.006s
thats the thing it showed me.
That's great.
Here is your RUU : http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.105.14_release_260743_signed.exe
How to : go to bootloader / fastboot mode
(even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- run/doubleclick RUU and follow instructions.
Grab the stock boot.img & recovery from : http://forum.xda-developers.com/showpost.php?p=27261622&postcount=1149
ckpv5 said:
First thing, make sure what is your original software version.
If you're not sure, run this in fastboot mode
go to bootloader
type fastboot getvar version-main
tell us what no. it show
then will be the next step to get the correct RUU for your device
Click to expand...
Click to collapse
Can this be done with terminal emulator also?
If so how?
Sent from my HTC One X using CoreDroid Premium
Doo Doo said:
Can this be done with terminal emulator also?
If so how?
Sent from my HTC One X using CoreDroid Premium
Click to expand...
Click to collapse
If you are talking about the Terminal Emulator app, I don't think it can read the version-main as the getprop command will read what is written in the build.prop
But I maybe wrong as I'm not really familiar with Terminal Emulator except some basic command.
So how do we flash this whole thing?
GUARDIANBD said:
So how do we flash this whole thing?
Click to expand...
Click to collapse
Reboot to bootloader / fastboot mode where you see the word fastboot usb highlighted in red.
And the above files only for 1.29.707.11 software version, it won't work for others.
Doo Doo said:
Can this be done with terminal emulator also?
If so how?
Sent from my HTC One X using CoreDroid Premium
Click to expand...
Click to collapse
ckpv5 said:
That's great.
Here is your RUU : http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.105.14_release_260743_signed.exe
How to : go to bootloader / fastboot mode
(even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- run/doubleclick RUU and follow instructions.
Grab the stock boot.img & recovery from : http://forum.xda-developers.com/showpost.php?p=27261622&postcount=1149
Click to expand...
Click to collapse
This should be stickied in this section as it is smack bang on the number.. AWESOME WORK
try'd to use the "fastboot getvar version-main" in linux terminal
i see FASTBOOT USB but i cannot get the info that u need..
so would this help?
Code:
*** UNLOCKED ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-0.96.0000
CPLD-None
MICROP-None
RADIO-1.1204.105.14
eMMC-bootmode : disabled
CPU-bootmode : disabled
MODEM PATH : OFF
May 10 2012,01:32:07
Not so sure about linux, but maybe the command is:
$ ./fastboot getvar version-main
ckpv5 said:
Not so sure about linux, but maybe the command is:
$ ./fastboot getvar version-main
Click to expand...
Click to collapse
just to get this straight :
to find this info what i need to do? i'v got dualboot WIN7 & Linux,at the Win drivers are installed + HTC SYNC
is there anything else i need to do ?
im in the HBOOT the 1X is connected and it says "FASTBOOT USB"
try'd to type in the cmd "fastboot getvar version-main" and nothing is happend
where this syntax is needed to put? via CMD or ADB?
Do you still have the fastboot folder/files that you downloaded when you unlock your
device ?
In Windows, open cmd prompt, cd to the fastboot folder where you have the fastboot.exe
example:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd\
C:\>cd fastboot
C:\fastboot>fastboot getvar version-main
version-main: 1.29.707.11
finished. total time: 0.044s
C:\fastboot>
Attached here the fastboot files & adb files in case anyone need them
ckpv5 said:
Do you still have the fastboot folder/files that you downloaded when you unlock your
device ?
In Windows, open cmd prompt, cd to the fastboot folder where you have the fastboot.exe
example:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd\
C:\>cd fastboot
C:\fastboot>fastboot getvar version-main
version-main: 1.29.707.11
finished. total time: 0.044s
C:\fastboot>
Attached here the fastboot files & adb files in case anyone need them
Click to expand...
Click to collapse
done
Code:
c:\fastboot>fastboot getvar version-main
version-main: 1.29.720.11
finished. total time: -0.000s
now i have CWM recovery
how can i revert back to stock from there?
ckpv5 said:
That's great.
Here is your RUU : http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.105.14_release_260743_signed.exe
How to : go to bootloader / fastboot mode
(even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- run/doubleclick RUU and follow instructions.
Grab the stock boot.img & recovery from : http://forum.xda-developers.com/showpost.php?p=27261622&postcount=1149
Click to expand...
Click to collapse
This is just great, ill do this and post the result!
after I finish these steps, my phone will be just like it was when i first bought it? and will I be able to update it with original HTC updates and maybe the new JB when it comes out?
THANKS ALOT!!!!!!!
Also waiting ^_^
GUARDIANBD said:
Also waiting ^_^
Click to expand...
Click to collapse
ckpv5 said:
Do you still have the fastboot folder/files that you downloaded when you unlock your
device ?
In Windows, open cmd prompt, cd to the fastboot folder where you have the fastboot.exe
example:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd\
C:\>cd fastboot
C:\fastboot>fastboot getvar version-main
version-main: 1.29.707.11
finished. total time: 0.044s
C:\fastboot>
Attached here the fastboot files & adb files in case anyone need them
Click to expand...
Click to collapse
i flashed the recovery, flashed boot img and relocked, cleared all caches and everything but now when the phone powers up (i currently have the miui on it) it shows me the lock screen, freezes for a second and phone restarts over and over again, i cant use the rom update utility when the phone is in this weird loop... and idea? (((
ChuckTesta said:
i flashed the recovery, flashed boot img and relocked, cleared all caches and everything but now when the phone powers up (i currently have the miui on it) it shows me the lock screen, freezes for a second and phone restarts over and over again, i cant use the rom update utility when the phone is in this weird loop... and idea? (((
Click to expand...
Click to collapse
If you follow the step carefully, there is no phone power up needed. You need to run the RUU in fastboot, directly after step 3.
Put your device in bootloader mode. Press power and hold it, you wll see the three buttons blinks and the device will shutdown. Release the power button, hold the volume button, the device will boot to bootloader/fastboot mode. Connect to your PC and run RUU.
---------- Post added at 08:02 PM ---------- Previous post was at 07:59 PM ----------
GUARDIANBD said:
done
Code:
c:\fastboot>fastboot getvar version-main
version-main: 1.29.720.11
finished. total time: -0.000s
now i have CWM recovery
how can i revert back to stock from there?
Click to expand...
Click to collapse
There is no 1.29.720.11 RUU available at the moment. Unless you have a nandroid backup of your stock ROM and you have the OTA files with you, there is no way to return to Stock for 1.29.720.11 currently.
ckpv5 said:
If you follow the step carefully, there is no phone power up needed. You need to run the RUU in fastboot, directly after step 3.
Put your device in bootloader mode. Press power and hold it, you wll see the three buttons blinks and the device will shutdown. Release the power button, hold the volume button, the device will boot to bootloader/fastboot mode. Connect to your PC and run RUU.
---------- Post added at 08:02 PM ---------- Previous post was at 07:59 PM ----------
There is no 1.29.720.11 RUU available at the moment. Unless you have a nandroid backup of your stock ROM and you have the OTA files with you, there is no way to return to Stock for 1.29.720.11 currently.
Click to expand...
Click to collapse
Oh my bad, The RUU said to turn on the phone and connect it so I thought is should be on, will do it in a bit and post results.
Thanks alot ckpv5!!!!
ChuckTesta said:
Oh my bad, The RUU said to turn on the phone and connect it so I thought is should be on, will do it in a bit and post results.
Thanks alot ckpv5!!!!
Click to expand...
Click to collapse
Ya.. I know, HTC's instructions always misleading, like when to unlock bootloader, it says to remove the battery...
Hi,
I have problems while trying to change CID into 11111111 from 032, the phone is S-OFF and run actually with 2.7 firware. The message error is still the same... FAILED (remote: failed unknown command).
Thank you
What commands do you use? Most of the time that are very small errors
Tecardo said:
What commands do you use? Most of the time that are very small errors
Click to expand...
Click to collapse
Hi, in adb folder click shift and right on the mouse in order to open cmd...
1. adb reboot bootloader
2. adb devices
3. fastboot oem writecid 11111111
Something is wrong?
Thank you!
Second one Is stupid otherwise user HTC_001
same error without the second command...
even with the batch tool same error...
In order to use fastboot commands you must be in download mode not bootloader. Once you are in bootloader, chose download mode on phone. Then your commands should work.
not working even in download mode... no error command, but still the same CID...
rentngo said:
not working even in download mode... no error command, but still the same CID...
Click to expand...
Click to collapse
Can you post a screen cap of your errors?
rentngo said:
not working even in download mode... no error command, but still the same CID...
Click to expand...
Click to collapse
In my experience I have to open command prompt as administrator and then cd to my platform tools folder. The shift right-click method doesn't work for me
Hello guys/girls,
I have built successfully a TWRP 2.8.7.0 recovery for Alcatel Idol 3 6039 4.7 inch (tested on 6039y). The recovery image can be downloaded from here:
Edit (30.09.2015): I think this will be the final version of the recovery. The date/time issue is fixed now and additionally small adjustments to the initialization process have been added.
twrp_recovery-2.8.7.0-idol347.img
md5sum: 175be787d67839d15beab7285279a72c
Please note that the latest OTA updates from the end of August and the start of September disable the fastboot commands which means that this recovery cannot be started as described below (if your device is already upgraded)!!! The device will return FAILED (remote: unknown command) when you try to boot the recovery.
If you find yourself in this situation but want root access please see this thread.
It can be tested as follows:
- enable the developer options
- allow the USB debugging
- reboot to bootloader:
Code:
adb reboot-bootloader
- start the recovery image with:
Code:
fastboot -i 0x1bbb boot twrp_recovery-2.8.7.0-idol3-6039y.img
Please do not forget first to make a backup of the system partition by selecting System Image from the Backup settings. The backup image will be needed in order to install future OTA updates if available, so please keep it in a safe place.
petrov.0 said:
Hello guys/girls,
I have built successfully a TWRP 2.8.7.0 recovery for Alcatel Idol 3 6039 4.7 inch (tested on 6039y). The recovery image can be downloaded from here:
twrp-2.8.7.0-idol3-6039y.img
It can be tested as follows:
- enable the developer options
- allow the USB debugging
- reboot to bootloader:
Code:
adb reboot-bootloader
- start the recovery image with:
Code:
fastboot -i 0x1bbb boot twrp_recovery-2.8.7.0-idol3-6039y.img
Please do not forget first to make a backup of the system partition by selecting System Image from the Backup settings. The backup image will be needed in order to install future OTA updates if available, so please keep it in a safe place.
Click to expand...
Click to collapse
Great job! A couple of the outstanding issues on the 6045 TWRP are that the date/time stamp of the backup is screwy because of a known bug with 64 bit chips and also the recovery identifies every model as a Y model (you can see in recovery.log) because the boot.img for a Y was used. Yours may also encounter one or both of these issues. I suggested in the other thread they consider building for each model using the individual boot.img but didn't get a reply.
famewolf said:
Great job! A couple of the outstanding issues on the 6045 TWRP are that the date/time stamp of the backup is screwy because of a known bug with 64 bit chips and also the recovery identifies every model as a Y model (you can see in recovery.log) because the boot.img for a Y was used. Yours may also encounter one or both of these issues. I suggested in the other thread they consider building for each model using the individual boot.img but didn't get a reply.
Click to expand...
Click to collapse
Yes, the date/time stamp is wrong. The device model however is not much . The ro.product.model is shown as idol347. It is a custom build after all.
I tried to use TWRP on my 6039Y and it's not working. Well to be more precise I don't know if your custom recovery works or not because I can't seem to get past the first step. Here's what happened
Code:
adb reboot-bootloader
So the device reboots, but doesn't get past the first screen (Alcatel OneTouch Powered by Android) even after a minute or so. Should I let it more time or is this the bootloader?
Then i try this
Code:
fastboot -i 0x1bbb devices
This seems to have no effect, the command seems to execute without any consequence and I'm able to type a new line in cmd
And if I try
Code:
fastboot -i 0x1bbb boot twrp_recovery-2.8.7.0-idol3-6039y.img
I get a <waiting for device> and I'm stuck on that line, having to Ctrl+C to stop the command and reboot the phone by holding power
Yes I know, I'm on Windows and it might be the drivers causing this. However I have installed the ADB drivers through SDK just fine. I would like to be able to install the drivers from the phone but the only options I see in the USB connection settings are MTP, PTP and Charging only. Any idea on how to get that CD-Rom option to appear?
Thanks for your help in advance
Rorshan said:
I tried to use TWRP on my 6039Y and it's not working. Well to be more precise I don't know if your custom recovery works or not because I can't seem to get past the first step. Here's what happened
Code:
adb reboot-bootloader
So the device reboots, but doesn't get past the first screen (Alcatel OneTouch Powered by Android) even after a minute or so. Should I let it more time or is this the bootloader?
Click to expand...
Click to collapse
This is OK it's in the bootloader.
Rorshan said:
Code:
fastboot -i 0x1bbb devices
This seems to have no effect, the command seems to execute without any consequence and I'm able to type a new line in cmd
And if I try
Code:
fastboot -i 0x1bbb boot twrp_recovery-2.8.7.0-idol3-6039y.img
I get a <waiting for device> and I'm stuck on that line, having to Ctrl+C to stop the command and reboot the phone by holding power
Click to expand...
Click to collapse
Looks like a driver issue. I use Linux no problems here no need of drivers too.
Rorshan said:
Yes I know, I'm on Windows and it might be the drivers causing this. However I have installed the ADB drivers through SDK just fine. I would like to be able to install the drivers from the phone but the only options I see in the USB connection settings are MTP, PTP and Charging only. Any idea on how to get that CD-Rom option to appear?
Thanks for your help in advance
Click to expand...
Click to collapse
Try with the drivers posted by @famewolf here or with these.
Meanwhile the first post has been updated with a new link. Please download the recovery again. There was a bug with the screenlock in the previous build. The screenlock is disabled in this one.
Alright I'll make sure to try that. Otherwise I guess I'll just try with Linux or Mac. Thanks
Sent from my 6039Y using Tapatalk
Rorshan said:
Alright I'll make sure to try that. Otherwise I guess I'll just try with Linux or Mac. Thanks
Sent from my 6039Y using Tapatalk
Click to expand...
Click to collapse
A quick check of the dirvers shared by @famewolf shows that they should work on windows with 6039y (at least to start the recovery). These are the vendor and the product IDs of 6039y from one of the INF files in the archive so the drivers should be compatible with the device when is in the bootloader (they match with those reported by the device).
Code:
USB\VID_1BBB&PID_D00D.DeviceDescRelease="Android Sooner Single ADB Interface"
I don't see however the IDs for the recovery mode:
Code:
[726530.487224] usb 1-4: New USB device found, idVendor=18d1, idProduct=4ee2
and the IDs from when the phone is connected as MTP device:
Code:
[726695.431624] usb 1-4: New USB device found, idVendor=1bbb, idProduct=af2b
but I hope everything to be OK. Good luck.
Why is this thread in Mi Note pro development section ? It's about idol 3 6039....
frankee207 said:
Why is this thread in Mi Note pro development section ? It's about idol 3 6039....
Click to expand...
Click to collapse
I asked the moderator to move it to the development section of Idol 3, but something went wrong. The moderator is informed about this. Now I'm waiting to be moved to the Idol 3 forum again.
petrov.0 said:
I asked the moderator to move it to the development section of Idol 3, but something went wrong. The moderator is informed about this. Now I'm waiting to be moved to the Idol 3 forum again.
Click to expand...
Click to collapse
Yeah I was thinking that's a bit strange! Got me excited thinking theres newer TWRP for Mi Note Pro xD
Cyanogen recovery
Here is a download link of the cyanogen recovery (built from the 12.1 branch). It's useless. But if someone wants to try it. The md5sum of the image is 3ff21bbf5ece48422f3135fa583eaa78
Should this work on 6039J?
Has not been tested on 6039J until now, but you can try it. Don't rush with backups wipes etc. (because the partition table can be different) just boot with it through fastboot. You can examine your partitions with the recovery from the repartitioning guide which contains gdisk (if your phone is not rooted yet). But this is only if this one works with your device. By the way what is the J version ? Dual sim ?
I'm trying to create a backup of the 6039S (North American 16GB, 1-SIM/1-SD model), and am having some issues with fastboot.
ADB is working flawlessly, and I can boot into the bootloader. As petrov.0 noted earlier in this thread there is no dedicated bootloader screen, just the onetouch splashscreen displays.
I can enter:
Code:
fastboot -i 0x1bbb devices
and the device shows up: "6346ce6d fastboot".
However, when I go to run any of the OEM commands, e.g.
Code:
fastboot -i 0x1bbb oem device-info
it shows:
...
FAILED (remote: unknown command)
finished. total time: 0.016s
Any ideas? By all appearances the alcatel driver seems to be working, but could this still be a driver issue?
Bradlee22 said:
I'm trying to create a backup of the 6039S (North American 16GB, 1-SIM/1-SD model), and am having some issues with fastboot.
ADB is working flawlessly, and I can boot into the bootloader. As petrov.0 noted earlier in this thread there is no dedicated bootloader screen, just the onetouch splashscreen displays.
I can enter:
Code:
fastboot -i 0x1bbb devices
and the device shows up: "6346ce6d fastboot".
However, when I go to run any of the OEM commands, e.g.
Code:
fastboot -i 0x1bbb oem device-info
it shows:
...
FAILED (remote: unknown command)
finished. total time: 0.016s
Any ideas? By all appearances the alcatel driver seems to be working, but could this still be a driver issue?
Click to expand...
Click to collapse
Probably this problem is not related to the driver. Something is different in your device. By the way can you boot this recovery ?
petrov.0 said:
Probably this problem is not related to the driver. Something is different in your device. By the way can you boot this recovery ?
Click to expand...
Click to collapse
No, I can't boot this TWRP recovery either. I get the same error message: FAILED (remote: unknown command).
I must admit that the internal sd card has not been mounted properly until now. I found the proper way however how to do it. The first post has been updated and now contains a link to the recovery which includes the corrections. The configuration files with which I do these recoveries, are also publicly available now and can be found here. Nothing special but ...
Bradlee22 said:
No, I can't boot this TWRP recovery either. I get the same error message: FAILED (remote: unknown command).
Click to expand...
Click to collapse
Any output from
Code:
fastboot -i 0x1bbb getvar secure
fastboot -i 0x1bbb getvar version-bootloader
fastboot -i 0x1bbb getvar all
petrov.0 said:
Any output from
Code:
fastboot -i 0x1bbb getvar secure
fastboot -i 0x1bbb getvar version-bootloader
fastboot -i 0x1bbb getvar all
Click to expand...
Click to collapse
Nothing useful from any of those.
Code:
fastboot -i 0x1bbb getvar secure
Output is:
secure:
finished. total time: 0.016s
Code:
fastboot -i 0x1bbb getvar version-bootloader
Output is:
version-bootloader:
finished. total time: -0.000s
Code:
fastboot -i 0x1bbb getvar all
Output is:
all:
finished. total time -0.000s
P.S. Thanks for your help. It's much appreciated!
Bradlee22 said:
Nothing useful from any of those.
Click to expand...
Click to collapse
remote: unknown command is a protocol error, as long as I understand the source. What is the host OS ? Windows ... which version ... did you try to start cmd.exe as administrator ? Which drivers you use ? On what port is your device connected (USB 2 or USB 3). Do you have access to a Linux box ? If you have try from there. I'm not sure how Windows handles the sharing of the USB ports with a virtual machine. You can try to start a distro in VirtualBox, which have option to expose a device connected on the host to the guest system and then to try fastboot from there.
I cant flash everything on fastboot mode
i have usb enabled and bootloader unlocked latest
status: Bootloop, no recovery
only fastboot mode
help for a fix ... I bricked the tab
TRIED TO RETURN TO STOCK WITH FLASH ALL.BAT BUT ALL PARTITIONS END WITH UNKNOWN COMMAND
help i paid 700 $ for this tab ... i can reboot anduse fastboot mode... bootloader unlocked
Alessandro999 said:
help i paid 700 $ for this tab ... i can reboot anduse fastboot mode... bootloader unlocked
Click to expand...
Click to collapse
Are you using the latest FASTBOOT.exe?
Can you screenshot the CMD?
unknown commands usually indicate an error in the command not the execution of the command.
parakleet said:
Are you using the latest FASTBOOT.exe?
Can you screenshot the CMD?
unknown commands usually indicate an error in the command not the execution of the command.
Click to expand...
Click to collapse
i have fixed!!! just relock the bootloader... waiting for delete and erasing.... unlock the bbotloader and waiting for esasing
now can flash all i want
Alessandro999 said:
i have fixed!!! just relock the bootloader... waiting for delete and erasing.... unlock the bbotloader and waiting for esasing
now can flash all i want
Click to expand...
Click to collapse
Good job
I've tried to unlock my device with enable OEM unlock in the developer options, because it is needed for enable VoLTE in my regions(with QPST). But it seems that device doesn't recognize it's allowed to unlock. Every advanced fastboot command in fastboot mode returns "FAILED (remote: 'Command not supported in default implementation')".
Is this possible to you who using the device to unlock the bootloader with fastboot? Or, OTA updates I've received blocked that?
How unlock the bootloader?My HTC U20 5G no download mode in bootloader !!!!!
Try
fastboot oem get_identifier_token --- error
fastboot flashing unlock --- error
fastboot oem unlock --- error
Yes I have the same problem. I thought it was Win 10, so I tried Win 7 as well, but got the same error there too.
Check if "USB debugging" and "OEM unlocking" are activated in Developer options
iourikil said:
Check if "USB debugging" and "OEM unlocking" are activated in Developer options
Click to expand...
Click to collapse
Yes, both options are activated (at least in my case).
Both commands "fastboot flashing unlock" and "fastboot oem unlock" result in "FAILED (remote: 'unknown command'), fastboot: error: Command failed".
I have no problem with Desire 20 pro and have no guess why it doesn't work with U20
C:\adb>adb reboot bootloader
C:\adb>fastboot devices
CN06D1V02*** fastboot
C:\adb>fastboot flashing unlock
...
OKAY [ 0.040s]
finished. total time: 0.042s
iourikil said:
I have no problem with Desire 20 pro and have no guess why it doesn't work with U20
Click to expand...
Click to collapse
It also works with the U19e, very annoying that they changed it.
iourikil said:
I have no problem with Desire 20 pro and have no guess why it doesn't work with U20
C:\adb>adb reboot bootloader
C:\adb>fastboot devices
CN06D1V02*** fastboot
C:\adb>fastboot flashing unlock
...
OKAY [ 0.040s]
finished. total time: 0.042s
Click to expand...
Click to collapse
In U20 fastboot can't use this way and In bootloader no download mode to select. >"<
elimiriel said:
I've tried to unlock my device with enable OEM unlock in the developer options, because it is needed for enable VoLTE in my regions(with QPST). But it seems that device doesn't recognize it's allowed to unlock. Every advanced fastboot command in fastboot mode returns "FAILED (remote: 'Command not supported in default implementation')".
Is this possible to you who using the device to unlock the bootloader with fastboot? Or, OTA updates I've received blocked that?
Click to expand...
Click to collapse
for anyone that might come across this problem. I had the same issue trying to use fastboot to relock my bootloader. Found the answer on another forum. I was using adb to reboot to fastboot mode to run the command. This was the problem. I needed to reboot to the bootloader to run the command
elimiriel said:
I've tried to unlock my device with enable OEM unlock in the developer options, because it is needed for enable VoLTE in my regions(with QPST). But it seems that device doesn't recognize it's allowed to unlock. Every advanced fastboot command in fastboot mode returns "FAILED (remote: 'Command not supported in default implementation')".
Is this possible to you who using the device to unlock the bootloader with fastboot? Or, OTA updates I've received blocked that?
Click to expand...
Click to collapse
Try rebooting to the bootloader screen instead of directly rebooting. This solved my problem.
Hi there,
Just wanted to check in and see if anyone has managed to get bootloader unlocked?
Or is the htc u20 out of luck....
arcslt18 said:
Try rebooting to the bootloader screen instead of directly rebooting. This solved my problem.
Click to expand...
Click to collapse
can you teach me how to do that?
thank you
mofish said:
can you teach me how to do that?
thank you
Click to expand...
Click to collapse
Hi, Just manually enter the fast boot mode with power key+Volume Up or Down depending upon the model and make, You can search this online how to enter Bootloader mode for one particular device. Once you are in Bootloader, Try Fastboot mode and Enter your commands. Should work
Anyone figure this out on Nord n200 5g T-Mobile variant? Please help