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).
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.
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"
}
Hello everyone, a week ago I received my Mi 11 Lite 5G and the first thing I did was unlock the bootloader. Today I managed to unlock it and tried to install a custom ROM (xiaomi.eu). However, I had a problem that made the operation impossible. I forgot to activate the option "install via USB" thinking that this one was not important, obviously I underestimated it. My question is: do you have any solution to reinstall the basic ROM (there isn't system currently), or activate this option other than in the phone (in fastboot with adb for example...), regardless of the method, I hope there is at least one.
Awaiting a positive response (I hope), greetings and I wish you all a merry Christmas.
This option doesn't really matter, if your bootloader is unlocked (as in there is a undone lock icon every boot above the Mi logo) just go into fastboot by shutting the phone off forcefully, then holding down Power + Volume Down until you see the Fastboot Screen as shown below
{
"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"
}
Then after that, check device manager in Windows to see if your device is being seen as "Android Bootloader Interface", if it is. Then you're good to go! Download the latest Xiaomi.eu ROM for Renoir then unzip it, then run the batch script for your case. You will lose all of the data on your phone's internal storage when installing though. So beware and be sure to make backups!
good evening. i have o problem with the twrp installation.
after unlocking the bootloader with the adb method i tried to install the twrp. at first there was a problem with partition but with no command the twrp will open
.
{
"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"
}
the twrp.img is in the platform-tools folder with the same name as the command.
i though thw twrp was installed in the command but it does not open neither in recovery. i tried throug command or by pressing power button and the volupe up.
in addition the phone does open either. i reboot in the fastboot screen.
what is the the mistake and how should i procced?
thank you
poikon5 said:
good evening. i have o problem with the twrp installation.
after unlocking the bootloader with the adb method i tried to install the twrp. at first there was a problem with partition but with no command the twrp will open
.
the twrp.img is in the platform-tools folder with the same name as the command.
i though thw twrp was installed in the command but it does not open neither in recovery. i tried throug command or by pressing power button and the volupe up.
in addition the phone does open either. i reboot in the fastboot screen.
what is the the mistake and how should i procced?
thank you
Click to expand...
Click to collapse
If this phone has A/B partitions this command cannot work.
You must use
Type' fastboot boot twrp.img' without the apostrophes.
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP.
Or https://forum.xda-developers.com/t/...omi-mi-a3-laurel_sprout.3987759/post-80625495