hi guys please help me ive tried everything i saw on the internet but still no luck,
i tried reinstalling the usb driver but its still the same.
any suggestions from you guys?
maybe theres other way?
TIA
Which OS? Which drivers do you use? What do you see in device manager? Is your phone really in fastboot mode?
Another way is to use Linux OS, fastboot should work without any special drivers.
bonluis said:
hi guys please help me ive tried everything i saw on the internet but still no luck,
i tried reinstalling the usb driver but its still the same.
any suggestions from you guys?
maybe theres other way?
TIA
Click to expand...
Click to collapse
possibly what you are missing are the Qualcomm drivers for xiaomi mi a3
What's the command that you used to detect the phone while it's fastboot mode ? My guess it's ''adbdevices'' , if you did that you should try ''fastboot devices '' .
docrates1975 said:
possibly what you are missing are the Qualcomm drivers for xiaomi mi a3
Click to expand...
Click to collapse
Qualcomm drivers are for EDL mode. For fastboot and ADB, drivers come from Google.
docrates1975 said:
possibly what you are missing are the Qualcomm drivers for xiaomi mi a3
Click to expand...
Click to collapse
I already installed that but still no show
_mysiak_ said:
Qualcomm drivers are for EDL mode. For fastboot and ADB, drivers come from Google.
Click to expand...
Click to collapse
Already tried Google USB driver
_mysiak_ said:
Which OS? Which drivers do you use? What do you see in device manager? Is your phone really in fastboot mode?
Another way is to use Linux OS, fastboot should work without any special drivers.
Click to expand...
Click to collapse
This might be my last resort :crying:
{
"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"
}
Bre3eze said:
What's the command that you used to detect the phone while it's fastboot mode ? My guess it's ''adbdevices'' , if you did that you should try ''fastboot devices '' .
Click to expand...
Click to collapse
it worked bro thanks!
but i cant use adb right?
No , you can't use adb while in fastboot mode , only when phone is booted into system and you allow the device . Glad it worked
Dear I have a xiaomi my a3 when I go from a custom rom to a stock the phone that I do in fastboot mode, the bootloader is blocked,
and if it does not come out I have turned it off and when I start it it remains in fastboot mode, please help me with this topic.
Stay tuned to your comments
Related
any idea why cant recognized my devices in command "fastboot devices", i already install omap driver.
this problem started when i installed fresh win xp.
{
"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"
}
nh4Rdz said:
any idea why cant recognized my devices in command "fastboot devices", i already install omap driver.
this problem started when i installed fresh win xp.
Click to expand...
Click to collapse
Did you run it as an admin ?
Lelus said:
Did you run it as an admin ?
Click to expand...
Click to collapse
no i'm using win xp
Edit: theres no option "run as admin" when you right click
nh4Rdz said:
no i'm using win xp
Edit: theres no option "run as admin" when you right click
Click to expand...
Click to collapse
Can you run another command prompt as an admin enter c:\faseboot\bin and try fastboot devices ?
Lelus said:
Can you run another command prompt as an admin enter c:\faseboot\bin and try fastboot devices ?
Click to expand...
Click to collapse
i already tried that cd
c:\fastboot\bin
fastboot devices
still the same
when i fastboot flash recovery recovery.img
<waiting for devices>
Edit: fastboot works perfectly before but when i started format pc then used fresh win xp( win xp before) im facing that problem.
try rebooting your system once or maybe just logging off and on
i faced a similar problem with adb...its like it goes to sleep if you dont use it for sometime and to wake it up, you have to kill the server and restart it again. Just a guess
nh4Rdz said:
i already tried that cd
c:\fastboot\bin
fastboot devices
still the same
when i fastboot flash recovery recovery.img
<waiting for devices>
Edit: fastboot works perfectly before but when i started format pc then used fresh win xp( win xp before) im facing that problem.
Click to expand...
Click to collapse
Perhaps try adjusting the timing before you put battery back in, maybe slightly shorter time
problem solved. just reinstalling win xp.
nh4Rdz said:
problem solved. just reinstalling win xp.
Click to expand...
Click to collapse
I have sam problem, you can help me
Hello,
I am new to this forum but maybe I have an interesting thing.
I found a Samsung A3 (SM-310F 16GB) wich was going to trash. It seems it acts as a medical device for monitoring heart diseases. It has a custom launcher loaded on wich you can only load the monitoring program. It has the Android top bar with time bluetooth-status battery and so on, but you can´t swipe down to access preferences or else. You also can´t take screenshot due to security guidelines and you can´t connect to it with a PC.
So my question, is it possible to do a root on this device. Or to flash it with a stock firmware to use it as anormal phone?
I´m wondering if anyone has an idea about this.
Thanks
Dirk
The door to any Android device is ADB ( read: Android Debug Bridge ). If device isn't accessable by means of ADB then you can NOTHING do with it, IMHO.
jwoegerbauer said:
The door to any Android device is ADB ( read: Android Debug Bridge ). If device isn't accessable by means of ADB then you can NOTHING do with it, IMHO.
Click to expand...
Click to collapse
Ok, so how do I know if it is accessable with ADB?
And just for understanding, how do you customize a normal android device (smartphone), that it won´t act like a phone anymore? Just custom firmware, or custom chips?
igel81 said:
Ok, so how do I know if it is accessable with ADB?
Click to expand...
Click to collapse
You on Windows computer
install the Android USB driver suitable to this phone
install ADB
Then you connect Windows computer and phone via USB-cable, power on phone, and run this ADB command
Code:
adb devices
Look also inside here.
jwoegerbauer said:
You on Windows computer
install the Android USB driver suitable to this phone
install ADB
Then you connect Windows computer and phone via USB-cable, power on phone, and run this ADB command
Code:
adb devices
Look also inside here.
Click to expand...
Click to collapse
Thanks. I tried this, but unfortunately it shows no device. By holding up and home at start, it boots into a firmware update mode. From here I can connect with adb in sideload mode. Don´t know if this is helpfull...
@igel81
If you can boot phone into ADB Sideload mode
{
"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 you can flash a ROM as a whole.
jwoegerbauer said:
@igel81
If you can boot phone into ADB Sideload mode
then you can flash a ROM as a whole.
Click to expand...
Click to collapse
Too bad, it doesn´t work. It says "footer is wrong" and "signature verification failed". It seems you can only install roms signed by that medical company.
Hi, I decided to unlock bootloader on my Xiaomi Mi 11 Lite 5G NE. I downloaded Mi Unlocker, and did everything as it was described on the internet: enabling debugging functions, unlocking OEM, logging to Mi Account etc, installing all required drivers etc. The problem is that after entering fastboot mode there's literally no device in Device Manager associated with my phone, so neither Mi Unlocker, nor fastboot can detect my phone. I tried reinstalling drivers, restarting PC, changing cables, ports, different version of adb, fastboot, and MI Unlocker with no result.
One thing that helped (but only for a minute) was doing factory reset, and then fastboot mode image changed to some older one, and then it appeared in device list, and Mi Unlocker detected it, but sadly there was an error saying "Couldn't verify device", and then fastboot exited, and after rebooting previous (newer) image appeared, and problem was back. Then I thought: hey, maybe I have too old system? So I upgraded it to MIUI 13, and now the problem is still there, but fastboot image has been reduced to only barely visible label.
Maybe I'm using obsolete drivers? Maybe you have some recent drivers, or maybe I should try another PC/linux booted from pen?
install mi pc suite 3.2.1.3111 for the drivers and check in windows/peripherals if drivers are corrected installed
Nope, it didn't help. I forgot also to mention, that phone is discoverable by adb, and I can execute adb reboot bootloader without any problems
Try (with minus - there are two diff modes):
adb reboot-bootloader
The same thing happens FASTBOOT label, and no device is detected.
Any other advices? I tried with Linux, but with the same results
Okay it's strange, but now I tried logging in to my Google account and switching most of debugging options in developer settings to on, and now it appeared as fastboot device after reboot, and I was able to unlock it
But now, unfortunately, when I wanted to flash something to phone, then fastboot disappeared again - wtf is going on?
Have you tried a different USB cable?
fibur said:
But now, unfortunately, when I wanted to flash something to phone, then fastboot disappeared again - wtf is going on?
fibur said:
But now, unfortunately, when I wanted to flash something to phone, then fastboot disappeared again - wtf is going on?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I can help you! Please check PM.
mvikrant97 said:
I can help you! Please check PM.
Click to expand...
Click to collapse
{
"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"
}
Okay, the issue was broken USB port, now it works perfectly
I followed the steps, but I can't get into bootloader mode. Please help. When I reboot to bootloader, the screen is blank and doesn't respond to fast boot commands.
Turn off phone then hold volume up and plug into computer to get to bootloader mode (screen should still be off)
If computer doesnt recognize fastboot mode then your computer is lacking the right driver
I did follow the steps and downloaded both the google USB driver and driver for my device model from sony mobile communications via 'install OEM drivers'. Did I miss anything? In fact, how do I remove and reinstall both drivers if they are faulty?
RP1408 said:
I did follow the steps and downloaded both the google USB driver and driver for my device model from sony mobile communications via 'install OEM drivers'. Did I miss anything? In fact, how do I remove and reinstall both drivers if they are faulty?
Click to expand...
Click to collapse
I remember window 10 and 11 block driver if you install normal through double click. You need to get to device manager and update driver manually. Google it
i tried but still the same problem. From this screenshot , could you make out anything regarding anything ive might have missed. i installed the google usb driver and fastboot driver by the device manager as stated in the previous comment.
{
"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"
}
RP1408 said:
i tried but still the same problem. From this screenshot , could you make out anything regarding anything ive might have missed. i installed the google usb driver and fastboot driver by the device manager as stated in the previous comment.View attachment 5805835
Click to expand...
Click to collapse
Boot windows in safe mode, and disable driver certification and reinstall the driver.
RP1408 said:
i tried but still the same problem. From this screenshot , could you make out anything regarding anything ive might have missed. i installed the google usb driver and fastboot driver by the device manager as stated in the previous comment.View attachment 5805835
Click to expand...
Click to collapse
Hey, man I had a problem with the drivers in bootleader mode on my 5 IV as well. Which had the Android under Other Devices with a question mark, meaning it couldn't find the drivers.
You could try forcefully installing the drivers for the device as I explained how to do in my post here: https://forum.xda-developers.com/t/...-and-flashing-firmwares.4537183/post-88051049
Make sure you don't have US version because you can't unlock bootloader on it
RP1408 said:
i tried but still the same problem. From this screenshot , could you make out anything regarding anything ive might have missed. i installed the google usb driver and fastboot driver by the device manager as stated in the previous comment.View attachment 5805835
Click to expand...
Click to collapse
There's a Sony driver you jeed to use, SA2000 or some weird name. Did you get that one? Install it by right clicking on the Android device name with yellow warning triangle. Select the install disk manually and assign that one to manually install
Hello,
Can we root the Android tablet YC-83T?
Specs: https://portworld-solu.com/portfolio-item/yc-83t-portable-8-inch-android-10-wifi-tablet/
Runs Android 10 (go)
Ram: 1GB
Storage: 32gb
It's not locked down, as in it has google services and it can install APK files
I don't think so, I can't seem to find a custom recovery, you might be able to use adb sideload to install magisk or superuser though, good luck though
running adb reboot bootloader gets stuck on the boot logo, nice
17lifers said:
running adb reboot bootloader gets stuck on the boot logo, nice
Click to expand...
Click to collapse
could you send a picture of what it's stuck on?
{
"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"
}
OEM Logo, not bricked as it can boot fine without usb cable (yes tablet was given away for free lol)
17lifers said:
OEM Logo, not bricked as it can boot fine without usb cable (yes tablet was given away for free lol)
Click to expand...
Click to collapse
lucky you, what you planning on rooting a tablet for?
oh and what model does it say you have in your settings?
YC-38T
might have an idea, does the tablet bootloop whilst adb is on? or does it just not turn off at all?
only with adb on, i can disconnect cable, force off the device, and boot it back up then it'll turn on fine
so it doesn't turn off at all?
no
17lifers said:
no
Click to expand...
Click to collapse
whilst it's stuck, could you run the fastboot devices command?
will try again, currently charging it (18:54 in the netherlands )
nope, no response
17lifers said:
nope, no response
Click to expand...
Click to collapse
It could have a non-standard VID/PID on the bootloader.
Is it even detected as anything?
What does DeviceManager say?
hm, if possible, can you go to recovery and use adb sideload? you should probably do the devicemanager thing first though
shows up as usb download gadget
17lifers said:
View attachment 5856319
shows up as usb download gadget
Click to expand...
Click to collapse
that's odd, what about entering recovery?
no command ¯\_(ツ)_/¯
we need usb drivers thats why, gonna install them