Good day.
I've working on rooting my Lenovo legion 2 pro CN ROM, and currently stuck in the process of fastboot flash image.
It seems like the phone won't be able to detect by my laptop, after I ran the cmd #adb reboot bootloader. There is nothing showing up on the #fastboot devices.
I've checked on some others thread, by understand the fastboot are communicating through the side port instead of the below port, been reseating cable on that ports, but still no luck.
If Anyone who can guide me through this would be very much appreciated.
install device driver in device manager
Related
Hello everyone, I'm using Redmi Note 3 and I have tried rooting it several times.
I have unlocked the bootloader. I have also installed the adb drivers.
When I connect phone in fastboot mode and write 'fastboot devices' in cmd it doesn't return anything. But when I connect when its on, adb devices returns the device code.
Please help.
Same, happens to mine too. Used to work with a previous install of windows, but now, nope.
Had this issue too.
Try going to Device Manager and check to see if Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Install minimalist ADB and fastboot and right click Android Bootloader Interface. Click Update Driver Software, browse computer, and then click the option to list driver files already present on your drive. It should pull up a fastboot driver that's an older version than the one you currently have. Install that and fastboot will work again.
Doesn't work
Can you please link the files for download when we're updating the driver software.
I recently got a BLU VIVO 6 and i just want to unlock the bootloader(and then install TWRP and root it etc).
the phone is recognised with ADB Devices, but once i put my phone into fastboot mode ( and type into prompt fastboot devices ) nothing comes up.
OEM unlocking is on
I've swapped out USB ports
I bought a new USB cable for the phone
Reinstalled drivers, manually.
halp, what do
:crying: :crying::crying:
Try a diffferent computer or uninstall all the drivers and reinstall only the ones that are needed. Most probably its a problem with Drivers.
It was, thank you. I was able to unlock the bootloader, now my issue is with TWRP. the phone is softbricked at the moment, and has been for a few day. I going to keep trying to find out how to get it working again.
Do you have the recovery file you want to install? If so just flash it from fastboot. Otherwise find the recovery in the forum of your device.
Hit thanks if it helped!
hi..
Greetings to every Android Magicians out there...!
Device:- MiA1 (Never rooted)
1.USB debugging was enabled and OEM is not enabled.
2.Hence Boot loader is Locked.
3. Adb drivers installed in my laptop.
4.Windows driver signature are disabled.
5. Xaiomi flash tool and drivers installed.
6. Qualcom HS-USB Diagnostics 900E installed.
7. Can be enter in fastboot mode and edl mode as well.
The problem:- My MiA1 was never rooted (USB debugging was enabled and OEM is not enabled.).
All apps are force stopped suddenly while using the phone so tried to reboot my devices,
and there it begins.. it stuck at boot logo.
Things i have tried:
1. Fastboot Mode:
Since the boot loader is locked i cant flash Any ROM through fastboot so i tried to enter in EDL mode through CMD.,But failed.
so i just open the back panel & however entered in EDL mode by Testpoint.
(and i've tried in fastboot through cmd { fastbooot oem unlock } it says successful but when i check the status through
{fastboot oem devices-info} but the bootloader is still locked).
2. Test Point Method:
I tried to flash MiA1 official global version ROM's (7,8,9 as well) through Xaiomi Flash tool(2015,2016,2017 versions) by test point Methods.
i have encountered the problems like AKC don't match and Cant receive Hello packets.
However i have got solved this Prolems by using Beta version of Xaiomi Flash tool.
3. When i flash (tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794) flashing was successful but devices still stuck at
Androidone logo.
Tried to flash other versions of ROM (tissot_images_V10.0.4.0.PDHMIXM_9.0) flashing was successful but devices still stuck at
Androidone logo.
By the way i have tried it using different type C cables and different ports (COM5, COM20,COM40 etc) and and different laptop as well but No luck.
i hope you guys do some Magic and help me out.
Thank you so Much for reading this thread.
Hi all,
Just bought yesterday this phone and after doing typical actions like android config (oem, debugging, etc.), installed adb and fastboot. PC recognized command adb devices and shows the phone but when I reboot to fastboot mode, it stucks and the device manager shows unknown android.
Have read all the tips here, forums, youtube, etc. but no way. Tried in 2 different computer with same results. Installed last android studio with sdk manager, same error. Installed oneplus drivers and also the same.
Even I have tried a different cable but no success at all.
This is so frustrating situation, ever more considering that I'm not newbie at this (years ago always changed rom every month and smartphone every 2 months).
Any advice? Format pc? Install other windows in other partition?
Or selling the phone and buying another brand
spamerobaldomero said:
Hi all,
Just bought yesterday this phone and after doing typical actions like android config (oem, debugging, etc.), installed adb and fastboot. PC recognized command adb devices and shows the phone but when I reboot to fastboot mode, it stucks and the device manager shows unknown android.
Have read all the tips here, forums, youtube, etc. but no way. Tried in 2 different computer with same results. Installed last android studio with sdk manager, same error. Installed oneplus drivers and also the same.
Even I have tried a different cable but no success at all.
This is so frustrating situation, ever more considering that I'm not newbie at this (years ago always changed rom every month and smartphone every 2 months).
Any advice? Format pc? Install other windows in other partition?
Or selling the phone and buying another brand
Click to expand...
Click to collapse
Did you select always allow from this computer after enabling debugging and plugging your phone into computer when phone was booted and running(not in recovery or fastboot. Also adb does not work in the bootloader only fastboot commands. Secondly search for the insecure modded stock recovery if you want to do adb access commands in recovery. There is also a fastboot d mode on our phones which look like recovery but you can flash all partions via full fastboot to get to fastboot d your phone has to be on then you type adb reboot fastboot
toolhas4degrees said:
Did you select always allow from this computer after enabling debugging and plugging your phone into computer when phone was booted and running(not in recovery or fastboot. Also adb does not work in the bootloader only fastboot commands. Secondly search for the insecure modded stock recovery if you want to do adb access commands in recovery. There is also a fastboot d mode on our phones which look like recovery but you can flash all partions via full fastboot to get to fastboot d your phone has to be on then you type adb reboot fastboot
Click to expand...
Click to collapse
finally solved!! thanks mate
spamerobaldomero said:
finally solved!! thanks mate
Click to expand...
Click to collapse
No prob
Long story short: installed custom rom, went into TWRP bootloop, tried to flash back to stock ended with bootloop.
Is there a way to enter into fastboot? So I can at least flash TWRP back.
Currently it's booting, displaying the boot screen with the orange state warning and almost immediately rebooting
Fastboot on Android side gets activated by bootloader. Hence you should be able to run Fastboot commands.
To test this you run on Windows computer
Code:
fastboot devices
jwoegerbauer said:
Fastboot on Android side gets activated by bootloader. Hence you should be able to run Fastboot commands.
To test this you run on Windows computer
Code:
fastboot devices
Click to expand...
Click to collapse
Tried to spam sudo fastboot devices on linux, but to no avail.
Trying on windows as soon as I find the drivers
Installed the drivers from here and rebooted: https://gsmmobiledriver.com/umidigi-f1
Spammed fastboot.exe devices in admin power shell, but again no output at all
While it doesn't respond to fastboot, I noticed that, while booting, lsusb displays the preloader:
Bus 003 Device 010: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader
Is there a way to interact with it?
It seems it's possible to unbrick the phone with SP Flash Tool, I can't find a guide or how to do it however...
Edit: all guides I had foudn require to device to be powered off. Given that my case is a bootloop, I will try to wait until the battery has dried up
Ended up following this: https://forum.xda-developers.com/t/stuck-in-a-boot-loop-and-cant-access-recovery-mode.3818742/
Standard procedure with SPFlashTool: no preloader, download all else. Results in a "PMT changed for the rom; it must be downloaded", so I probably have a faulty firmware copy
Edit: wrong firmware, my phone uses the global instead of the EU one for some reason