Hello, I tried to unlock the bootloader several times, and was blocked, the page displays that too many attempts, how to unlock it? I care about time.
Thanks guy..
I'm sorry for my English.
Hello. Where exactly do you get "too many retries", in the webpage to request the code or in fastboot mode where you must type the command to unlock the watch's bootloader? What watch model? Can you share a screenshot showing the problem?
lfom said:
Hello. Where exactly do you get "too many retries", in the webpage to request the code or in fastboot mode where you must type the command to unlock the watch's bootloader? What watch model? Can you share a screenshot showing the problem?
Click to expand...
Click to collapse
When you enter the unlock command, an error appears and can not be unlocked.
When he types "fastboot devices" he shows me "0123456789 fastboot"
when entering a command to unlock shows me
"failed (remote: ED)
Rumek98 said:
When you enter the unlock command, an error appears and can not be unlocked.
When he types "fastboot devices" he shows me "0123456789 fastboot"
when entering a command to unlock shows me
"failed (remote: ED)
Click to expand...
Click to collapse
If you have the wrong code and you attempted to enter it many times then maybe there is some security mechanism that permanently locked it. I advise you to post your question, with screenshots if possible, in the unlock bootloader thread so other people with more experience about doing it can help you.
{
"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"
}
Related
I have an "old" Huawei Ascend G730-U10 which has a terrible..... TERRIBLE stock ROM, starting from the general stability of applications and the system itself to the fact that this phone was released to be never, ever updated; so I want to install a custom ROM.
But since I'm doing it, there are over 9000 bugs and problems, and maybe the only thing that went almost right was rooting (except for the fact that I'm stuck with KingRoot since SuperSU refuses to install).
First of all, I couldn't even request the unlock code the usual way, since the code to bring up the Product ID didn't work and I had to contact Huawei directly.
After getting the code, I booted into the bootloader, did "fastboot oem unlock *code*" and... I don't even know if it worked! No message appeared and doing "fastboot oem get-bootinfo" returns "FAILED (remote: not support on security)".
After finding both a TWRP and a Clockworkmod build for this phone (the latter one is actually for G730-U00, I don't know if it would work), I tried doing "fastboot boot *path_to_recovery_image*", but that doesn't work either, as it just hangs on "downloading 'boot.img'..." without doing anything (last try I left it there for 20 minutes). I don't want to already flash the recovery directly since I want to test if it works and I don't want to brick the phone.
Can someone help me?
Bootloader pictures (if it can help):
{
"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"
}
For clarity, my OS is Lubuntu 17.04 (Zesty)
Due to my phone's apparent obscurity, I'm unable to find any resources pertaining to it, so I've been trying to be as 'manual' as I can by unlocking it through fastboot commands. I really want to unlock my phone's bootloader in order to root it and install a custom recovery and then custom ROM.
However, I've run into an issue. Whenever I run 'fastboot oem unlock', as well as most other fastboot commands, I get stuck at an ellipsis('...') and it stays there until I shut off my phone. Ctrl+C and Ctrl+Z can't close it. So far, I've successfully installed ADB and fastboot tools.
For troubleshooting, I have:
- double checked if my device is listed whenever I run either the 'adb devices' command or the 'fastboot devices' command and it is listed for both
- I've set up my udev rules and adb_usb.ini
- changed usb ports/cables
- rebooted my phone and PC many times
- looked for official and unofficial unlocking instructions (to no avail)
If there is anyway you can help me or guide me to a resource which may be of use to me, please do so. It's been a real struggle having such an obscure phone, but it's what I can afford at the moment.
tl;dr: 'fastboot oem unlock' not working. stuck at ellipsis('...'). device is listed under 'adb devices' and 'fastboot devices' command.
Unfortunately, I can't post outside links yet, so please PM me for a link to my dropbox folder containing my .rules, adb_usb.ini, and CPU-Z information.
{
"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"
}
Bolded for skimmers.
Hi. I have problem with OEM unlocking. When I'm going to developer options and click on OEM unlock, button turns gray, not blue. When I enter phone to bootloader, device unlock mode didnt appear, and OEM LOCK (U1) is still active. Please, help.
{
"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"
}
Could be your KG state ( download mode ) be in active state.
radek225 said:
Hi. I have problem with OEM unlocking. When I'm going to developer options and click on OEM unlock, button turns gray, not blue. When I enter phone to bootloader, device unlock mode didnt appear, and OEM LOCK (U1) is still active. Please, help.
View attachment 5355759
View attachment 5355763
Click to expand...
Click to collapse
Did you already found a solution? I have the same problem, same device
have the same problem
still need help
I have the same problem. Someone found a solution?
I just got this phone and the OEM unlocking toggle was completely missing.
Turning off the automatic date and time under general management, adding manually 2 weeks to the current date, reboot the phone and turning on wifi to establish an internet connection solved the issue for me. I read that also helps if the OEM unlock button is just greyed out, but I cannot confirm that.
BTW I got the clue from the official Samsung support. Since this toggle is not only used for rooting but also other functions, they should help you out if you have issues.
As you can see, the OEM switch is only after entering Download Mode, there is no option to unlock the bootloads. Changing the date doesn't help.
also have the problem. how can i proceed to get root?
Hello,
A couple of days after buying the Nokia X20 it asked for an OTA update so I did it but it failed somehow and it booted into fastboot mode.
I tried through fastboot platform tools administrator:
- Flashing stock rom
result: "remote: did not have permission to flash"
-"flashing get_unlock_ability"
result: 1
-unlocking bootloader using "fastboot flashing unlock"
result: "FAILED (remote: 'unknown command')
fastboot: error: Command failed"
-wiping it using "fastboot erase data"
result: "
Erasing 'data' FAILED (remote: 'did not have permission to erase')
fastboot: error: Command failed"
PS: my only options are "Start", "Restart bootloader", "Power off". No recovery mode plus I can't take it to Nokia Care
I have no clue what to do next. If anyone could help it would be much appreciated
{
"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"
}
Hello! did you solve your problem?
I have same problem
Duck Lorenz said:
I have same problem
Click to expand...
Click to collapse
Your phone is fully bricked then! There's literally 0 WAYS to fix this issue, so you might as well just ask Nokia Customer Support to fix it. Sorry, but the next time you want to get a phone for tinkering and installing custom ROMs, just buy a Xiaomi or maybe a Samsung with good community support instead
I need some assistance with unlocking the stupid bootloader on this one plus. So it's a T-mobile Phone and I filled out the application for the unlock token waited two weeks no reply. Finally I Chit Chatted with One PLus Support and two days later I got the Token.Bin file sent to my email. Ok after the struggle typing in the correct command in power shell which i had to rename (unlock_token.bin) and then move the Unlock download into my adb folder i finally got it flashed threw the fastboot (fastboot flash cust-unlock unlock_token.bin) only to get stuck at which should of been the simplest part of the process which is the final step of unlocking the bootloader itself which is where i'm stuck at. I tried every command in powershell i can think of and nothing. I tried fastboot oem unlock and fastboot flashing unlock both to no avail. please someone help me in this matter before this phone is thrown against my cpu outta frustration. attatched is the screenshot of my powershell after the token is put in i type the next commands only to get the fastboot command directory when i hit enter.. what am i doing wrong?
{
"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"
}
Alright so it ended up being something so simple I overlooked it for 24 hrs. I was opening the powershell in the platform tools which only got me so far. After checking and rechecking everything from Drivers to updates. So It was super simple all I had to do was instead of powershell was to simply open the cmd in the search bar of the platform tool folder the rest was as simplistic as it should of been. So in my case DO NOT USE powershell but the CMD instead Hopefully this helps someone who has been encountering the same problem with the commands not working properly...
Sorry, I am not familiar with this process to unlock the vendor lock (T-mobile).