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.
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"
}
When I use ADB to reboot into recovery, there is no option on my device to update from ADB. (See picture)
I just want to wipe the device and flash the latest update to get it running normally.
Am I missing something obvious?
Thanks.
{
"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've also tried going into fastboot and running the recovery command
.\fastboot flash recovery recovery.img
It returns with:
FAILED (remote: 'flashing not allowed for locked hw')
I'm guessing this has something to do with why ADB is not showing in recovery menu.
zantaff said:
When I use ADB to reboot into recovery, there is no option on my device to update from ADB. (See picture)
I just want to wipe the device and flash the latest update to get it running normally.
Am I missing something obvious?
Click to expand...
Click to collapse
zantaff said:
I've also tried going into fastboot and running the recovery command
.\fastboot flash recovery recovery.img
It returns with:
FAILED (remote: 'flashing not allowed for locked hw')
I'm guessing this has something to do with why ADB is not showing in recovery menu.
Click to expand...
Click to collapse
Stock HDX devices do not have a customary recovery menu or fastboot command set. If your device fails to boot and Amazon's simplistic reset does not fix it there is no recourse other than unlocking the bootloader (3rd gen) or tossing it in the waste bin (4th gen).
Hi all, as the title says, I'm unable to install twrp recovery.
Before proceeding on Android:
- USB debugging enabled
- Bootloader unlocked
- All screen security disabled
Befor proceeding on Windows:
- ADB tools & fastboot downloaded
- Z5C drivers downloaded
- General Google driver downloaded
- TWRP recovery downloaded
First connection pc the phone shows up at portable devices as Xperia Z5 Compact.
{
"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"
}
Opened command prompt -> ADB devices
command prompt -> ADB reboot bootloader
Phone goes into black screen + blue led
Moves from "portable devices" to "other devices" and shows up as S1Boot Fastboot
command prompt -> ADB reboot bootloader
fastboot flash recovery recovery.img -> stuck into "waiting for device"
I tried installing drivers via different methods with no luck.
Any help is much appreciated
PD: Can't post links to pics
Disconnect the device and shut it down.
Wait a few seconds.
Press volume up and hold it and connect usb cable.
Flash recovery.
Would be nice if you give a feedback!
I have problem with installing new ROM on phone Xiaomi MIX4 with A/B Partition file system. I followed this tutorial: https://www.xda-developers.com/how-to-install-twrp/
Before I started my trying to update my system, my phone was running this ROM from xiaomi.eu community and everything was running good.: xiaomi.eu_multi_MIX4_V13.0.6.0.SKMCNXM_v13-12-fastboot.zip
Newer ROM, I want to install, is this one: xiaomi.eu_multi_MIX4_V13.0.8.0.SKMCNXM_v13-12.zip
but this new ROM can’t be installed simple through fastboot as previous one, so I need to do it in more complicated way (via TWRP):
Steps I did:
1. I did all data backup on external drive.
2. Phone is fully charged.
3. Bootloader is unlocked.
4. USB Debugging and OEM Unlocking allowed
5. Reboot to bootloader
6. Set active B partition through ADB command – “fastboot set_active b”
7. Run TWRP and tried to wipe all the data through WIPE button, but error occurred:
{
"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"
}
8. Trying to install TWRP zip file (twrp-installer-3.7.0_11-0-odinx.zip) through TWRP Install button, but this error occurred:
Can you help me, what do I wrong? What step did I miss?
I tried a few alternative ways to solve this problem, but nothing helped and phone acctually can't run android anymore. Only shows fastboot logo and nothing else.
Thank you very much
Lukas
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).