Related
I did refer to this thread:
http://forum.xda-developers.com/showthread.php?t=2656275&page=13#post55838770
This is what happened:
I bricked my phone trying to install the autorec custom recovery after successfully rooting my phone. I get this " fastboot mode started" then on the 2nd line "uds_start()"
I think I am getting into download mode, it just says fastboot: processing commands.
however I don't see anything about com ports or LPT in device manager. all i see when i plug in my phone is "adb interface", and in that is "fastboot interface (google usb id). i can't find anything about my lg phone in there. so i can't reassign it to com41. is there any other workaround?
I have the same problem, look for solution.
Greetings
you have to download the laf.img and boot.img from http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zvc_partitions and then using fastboot, do fastboot flash laf.img and also fastboot boot.img. You should then be able to get into download mode correctly (with phone completely off, press and hold volume up button (dont let go) and also plug phone into computer using usb cable. When you see "DOWNLOAD MODE" on your phone, you can let go of the volume button. At this point, just tot back to stock.
jcwxguy said:
you have to download the laf.img and boot.img from http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zvc_partitions and then using fastboot, do fastboot flash laf.img and also fastboot boot.img. You should then be able to get into download mode correctly (with phone completely off, press and hold volume up button (dont let go) and also plug phone into computer using usb cable. When you see "DOWNLOAD MODE" on your phone, you can let go of the volume button. At this point, just tot back to stock.
Click to expand...
Click to collapse
i have been trying to tot back to stock and have all the files. I can get into download mode now but i can't get my phone to show up in device manager at all.
1. firmware
CN firmware:X(U1005)-Android8.1-CN-190123-------chinese firmware,no google play,SN number begin with U1005
update:X(U1005)-Android8.1-CN-20190225update2:X(U1005)-Android8.1-CN-20190514
NON EU firmware:X(U1005)-Android8.1-ALLDOCUBE-NONEU-190116------with google play,but for Non-European Region.SN number begin with U1005
update:X(U1005)-Android8.1-ALLDOCUBE-NONEU-190313
EU firmware：X(U1005E)-Android8.1-ALLDOCUBE-EU-190108------with google play,but for European Region.SN number begin with U1005E
update:X(U1005E)-Android8.1-ALLDOCUBE-EU-190313
2. UNLOCK,TWRP,ROOT,AND OTHER
Ⅰ.UNLOCK
"Settings"-"System"-"About tablet"-tap "build number" six times-go back to "System"-"Developer options"-let "OEM unlocking" enable.
download google adb and fastboot tool for windows
"Developer options"-let "USB debugging" enable.connect the tablet to your windows computer via type-c cable.The "Allow USB debugging" window pops up on the machine and clicks the "OK" button to allow
unzip platform-tools-latest-windows.zip file, open the "platform-tools" folder.Hold down the shift key and right-click to open the command line or power shell window
type “adb devices” in command line,if the result is "0123456789ABCDEF device"，that means the type-C line is well connected and the ADB debugging is successfully opened.
type "adb reboot bootloader" in command line to let tablet goto fastboot mode.
type "fastboot getvar unlocked" in command line.if the result is "unlocked: no",that means oem is locked.
type "fastboot oem unlock" in command line.and the tablet will metion you press "volume up" to allow unlock the tablet,press volume-up button on tablet.
if the command line shows like:
"(bootloader) Start unlock flow
OKAY [ 5.970s]
finished. total time: 5.974s"
that means Unlock success。
or you can type "fastboot getvar unlocked" in command line.if the result is "unlocked: yes" ,that also means Unlock success。
PS: unlock will wipe out all data.
Ⅱ. TWRP
twrp-u1005-20190113-zh.img------by WUXIANLIN default chinese language
update:twrp-u1005-20190223-zh.img by WUXIANLIN
recovery-U1005-TWRP-noMTP-1204.img------complied by me,default english language ,no mtp ,some bug
update:twrp-u1005-en-20190313.img
type "fastboot flash recovery xxxx.img" in command line.xxxx.img is one of two twrp images you have downloaded above ,and please place the twrp images file in " platform-tools"folder .
When tablet boot, you can press the volume up button to select recovery mode
Ⅲ. ROOT
downloadMagisk-v20.0.zip,and place zip file in "platform-tools" folder
in twrp mode--cancel "enter password "--then Swip to allow Modifications--Advanced-ADB Sideload-Swipe to Start Sideload.
type "adb sideload Magisk-v20.0.zip " in command line to install magisk Module
reboot the tablet ,and the tablet is rooted 。
install full magisk manager app
Ⅳ. OTHER
U1005-decrypt-data-sign.zip,in twrp mode .use adb sideload command flash the zip file,and then format data partition
3. tips
Do not use the "Format All + Download" option when flash firmware with MTK SP flash tool.
when the wire flashing process is interrupted, the machine may enter a fake dead state, and the mtk spflashtool does not recognize the port. The machine needs to be completely powered off or powerless before it can be reset.
4.ROMS
First thanks to wuxianlin.wuxianlin has ported lineageos 15.1 to alldocube x.
lineageos device link:android_device_cube_u1005 by wuxianlin
lineageos vendor link:android_vendor_cube_u1005 by wuxianlin
lineageos 15.1 rom link: lineage-15.1-20190303-UNOFFICIAL-u1005.zip for cn firmware by WUXIANLIN
lineage-15.1-20190406-UNOFFICIAL-u1005.zip for cn firmware by WUXIANLIN
lineage-15.1-20190320-UNOFFICIAL-u1005.zip uploading
Guys who have the ability to port ROM can also refer to his device and vendor for porting.
Thanks WUXIANLIN again!
5.kernel source
CUBE-kernel-U1005
RESERVE
Wonder if it has project treble and if we can flash gsi on it
It does have Treble.
But only Treble without Seamless Updates
Please share some official updates !
hassan_1000 said:
Wonder if it has project treble and if we can flash gsi on it
Click to expand...
Click to collapse
you can flash system-aonly PT image
wangyiling said:
you can flash system-aonly PT image
Click to expand...
Click to collapse
Thanks for all support wangyiling... :highfive:
Thanks wangyiling!!!
Thank you wangyiling
Could you perhaps help, I did choose the 'download' option only, not with the 'Format All', but some error occurred,
and now the tablet does not show any sign of life; It is even not detected by SP Flash Tool.
Is there anything to do at this point? I tried pressing the power button for ages and ages, but nothing would happen.
The tablet had a charge of approximately 80%, but it even won't charge at this point.
Is this the fake-dead state that you were referring to? What is there to do? :-/
MiOBi said:
Thank you wangyiling
Could you perhaps help, I did choose the 'download' option only, not with the 'Format All', but some error occurred,
and now the tablet does not show any sign of life; It is even not detected by SP Flash Tool.
Is there anything to do at this point? I tried pressing the power button for ages and ages, but nothing would happen.
The tablet had a charge of approximately 80%, but it even won't charge at this point.
Is this the fake-dead state that you were referring to? What is there to do? :-/
Click to expand...
Click to collapse
Try first to click Download on SP Flash Tool, then connect the cable and then press the Power Button (it can take some time, keep pressing) until the program detect the tablet and start to flash the Rom...
There's one guy on 4PDA forum that wake up his X like this...
Perhaps you will have the same luck!
MiOBi said:
Thank you wangyiling
Could you perhaps help, I did choose the 'download' option only, not with the 'Format All', but some error occurred,
and now the tablet does not show any sign of life; It is even not detected by SP Flash Tool.
Is there anything to do at this point? I tried pressing the power button for ages and ages, but nothing would happen.
The tablet had a charge of approximately 80%, but it even won't charge at this point.
Is this the fake-dead state that you were referring to? What is there to do? :-/
Click to expand...
Click to collapse
I'm on vacation.
make sure that the driver for MTK is installed properly (the driver for MTK should be very easy to find on web). you also can try this mtk inf driver
if it's the fake-dead state mentioned by me, the machine can only be reset untile the battery is completely cut off or the battery power is exhausted.
my above steps use the ADB or FastBoot command to flash the file like twrp , just in order to avoid the machine into a fake-dead state because of interruption in flash .
best luck @MiOBi
Thank you wangyiling for replying while on your vacation Thank you SafuPT too for trying...
I'm afraid nothing has helped, no matter how long I pressed... Is there a way to drain the battery quickly? it had almost %80, so I think it would take weeks to drain by itself :-/
Thanks for the TWRP / Root Guide.
All working well here just need better battery life
Do we have alternative option for camera app that could perform better than stock one?
is there any screen modes, like on samsung?
I read screen colors are inacurate ...
thanks
Has anyone successfully rooted their device and installed Miravision? If so does it work well?
Vertron said:
Has anyone successfully rooted their device and installed Miravision? If so does it work well?
Click to expand...
Click to collapse
I have the same question! Mine it's still in customs, hope to received it next week...
If you don't like the screenshot button (I find I keep hitting it by accident), or the layout of the buttons in the 'nav bar', you can follow this article to change them: https://www.xda-developers.com/how-to-change-your-nav-bar-icons-or-re-arrange-the-buttons-without-root/
You will first need to enable developers mode (go to 'Settings->System->About tablet', and keep tapping 'Build number' until developer mode is enabled). You should now have the 'Developer options' in 'System'.
Go to 'Developer options' and enable 'USB debugging'. Connect to your PC and follow the instructions.
I found a 'sysui_nav_bar' setting of ';left[1.0WC],back[1.0WC],home[1.0WC],recent[1.0WC],right[1.0WC];' was similar to my other Android devices.
Does this tablet support 10bit HDR x265 content? When I am playing 10bit HDR x265 content the colours look washed out and dull.
Hey everyone,
A2 lite phone is in bootloop - allegedly (not my phone) "out of nowhere". The user does not do any fancy things like flashing, and this has not been done either.
Phone is on continuous boot loop, and sometimes (really seems randomly), the device starts up in the "no command" mode and stays there for a while. I read that we could go into fastboot mode by pressing "power button and tapping volume up key", but this doesn't do anything.
I've tried this thread: https://www.the***********.com/boot-xiaomi-mi-a2-fastboot-mode-recovery-mode/
But I'm not even getting into fastboot.
I'm almost thinking that the volume buttons are just broken, though from the feedback of the buttons this doesn't seem realistic.
EDIT: ok, now I'm somehow able to get it into fastboot.... sometimes. Now I'm here:
I switched the partition from a to b, but it still goes into bootloop. Then I switched it back to a, still bootloop. Then back to b. Still bootloop! But at least now sometimes I'm able to get into fastboot. No matter what kind of commands I'm typing in the cmd console, after about 10 seconds on the fastboot screen, the phone just reboots.
idk, it looks almost as if both partitions have the bad android 10...
Do you guys have any idea? Please let me know if more info is helpful.
You go into fastboot mode by holding Vol Down + Power button. So try holding Vol Down and Power button at the same time to go into fastboot mode. (Don't tap it)
Go here and grab the image you prefer (latest should do the trick) : https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Then go ahead and follow this guide here to flash the stock ROM : https://c.mi.com/oc/miuidownload/detail?guide=2
This will wipe the data on the device, but it seems like you have no other option at this point. Cheers.
Thanks! I've tried that now. It starts flashing the device until... after about 10 seconds, the phone reboots from Fastboot mode .
As per this page: https://twrp.me/xiaomi/xiaomimia2lite.html
I've tried to do a recovery via TWRP. If I execute `fastboot boot path/to/twrp.img` then I go from fastboot to TWRP (the teamwin logo), but right after that the phone already reboots.
https://www.xda-developers.com/how-to-install-twrp/ - I don't know if it means anything, but when I execute `adb reboot bootloader`, the console returns `error: no devices/emulators found. If I execute `adb devices`, it does not list my device. However, if I execute `fastboot devices`, my device is listed.
I installed ADB usb drivers, so when I get my phone connected in fastboot, it shows up as Android Bootloader Interfacee in device manager. So not sure what's going on here, but it's all weird.
What I'm facing is very, very similar to https://www.reddit.com/r/Xiaomi/comments/4ltzt9/xiaomi_mi_note_boot_loop_even_in_fastboot/ <-- but that thread is a bit of a dead end (and 3 y/o)...
daize said:
after about 10 seconds, the phone reboots from Fastboot mode .
Click to expand...
Click to collapse
Hmm, it should never do that, maybe it's a hardware issue that we can not fix via Fastboot ?
daize said:
As per this page: https://twrp.me/xiaomi/xiaomimia2lite.html
when I execute `adb reboot bootloader`, the console returns `error: no devices/emulators found. If I execute `adb devices`, it does not list my device. However, if I execute `fastboot devices`, my device is listed.
Click to expand...
Click to collapse
When the device is in Fastboot mode, it will only be recognized as Fastboot. Only when it's properly booted, the device can be recognized in ADB, so no issues there.
I assume your bootloader is already unlocked as you have successfully booted into TWRP. You might try EDL (Emergency Download Mode) flash as a last resort :
Download MiFlash (20160401) from here : https://www.xiaomiflash.com/download/
You're downloading that particular version because it is able to EDL flash on your phone. Install the MiFlash you've downloaded and open it, then put the phone into fastboot mode. Connect it to your PC and use this code to take the phone into EDL mode:
Code:
fastboot oem edl
After you hit enter, you will see the screen turn off and notification LED blinking, this is normal. This means the phone is in EDL mode. Open the MiFlash you've installed (likely in C:\Program Files\Xiaomi\MiPhone) and browse to the ROM location and connect the phone. Choose "Flash All" and start flashing.
After the EDL flash is complete the phone will not reboot. It will stay in EDL mode. You need to disconnect the phone from PC and hold power button (about 10-15 seconds) to boot the phone. If the phone boots properly, you can go into fastboot and connect it to PC, then use:
Code:
fastboot oem lock
to relock your bootloader. Try it and let me know. :fingers-crossed:
Thanks for the continued help!
I've followed your steps - When I run fastboot oem edl, the console returns "... okay [ 0.0202s] finished. total time: 0.022s" and the phone turns to a black screen (no notification led blinking). Then... after a couple of seconds, goes back into the boot loop .
Something maybe to note: every time that my phone starts up, it (1) shows a screen saying "Your device software can'tbe checked for corruption.Please lock the bootloader.", and then slides down to the typical "androidone" white screen before it reboots again.
daize said:
every time that my phone starts up, it (1) shows a screen saying "Your device software can'tbe checked for corruption.Please lock the bootloader.", and then slides down to the typical "androidone" white screen before it reboots again.
Click to expand...
Click to collapse
The screen with the ugly text is normal, since you have an unlocked bootloader, it's there to warn you that the device's software might've been tampered with. On the main subject though, I'm out of ideas. You might try booting the phone by holding Power + Vol Up, which should normally boot into stock recovery or wipe the data on the device. But I'm slowly beginning to think that this might be a hardware issue rather than a software issue that I can help you to fix.
Under normal circumstances, EDL flash is the way to fix any problems you might encounter with the software, that's why it's called the Emergency Download mode. But since we're past that stage, I believe I will not be able to assist you further. Hope you can fix your device my dude/dudette!
If the phone gets out of fastboot mode your phone does not get recognized from your computer. Try to delete fastboot and minimal adb and download the latest version. [https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445]
Open MiFlash, click Driver left on the top and install them.
Set path to the downloaded firmware. Now boot into fastboot, once that is done connect your USB cable to both, computer and phone. If this doesn't work try different USB-Ports and USB-cables. Some work, some don't. This might be the reason for leaving the fastboot mode.
Click refresh and see if your device appears
@marstonpear thanks for your help so far <3 @Cappucinto, thanks for chiming in! What do you mean with this: "Open MiFlash, click Driver left on the top and install them." <-- in MiFlash, I do not see an option to select driver...
@marstonpear thanks for your help so far <3
@Cappucinto, thanks for chiming in! What do you mean with this: "Open MiFlash, click Driver left on the top and install them." <-- in MiFlash, I do not see an option to select driver...
What did change now after installing these drivers: https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445]
I did try some other USB cables. The one I've been trying triggers the windows sound for "new device successfully connected" when I boot the phone up in fastboot, and then of course gives the "device disconnected" sound when the phone then reboots. With another USB cable in this case, windows just states: "USB device not recognized". So it seems like the cable I haven't been using is defect .
I'm unable to use MiFlash at the moment so I can't explain the whole procedure with installing the drivers in MiFlash. But there has to be something like "Install > Drivers" or something. Maybe someone else can help out.
Try to use the working cable again, open a command prompt and type: fastboot devices
Then wait for an answer, post it here and see if the phone reboots again or if it stays in fastboot
daize said:
Hey everyone,
A2 lite phone is in bootloop - allegedly (not my phone) "out of nowhere". The user does not do any fancy things like flashing, and this has not been done either.
Click to expand...
Click to collapse
The response by marstonpear below makes sense.
marstonpear said:
You go into fastboot mode by holding Vol Down + Power button. So try holding Vol Down and Power button at the same time to go into fastboot mode. (Don't tap it)
Click to expand...
Click to collapse
Although u shd consider this link, i tried to arrange it step by step:
https://forum.xda-developers.com/sho...php?p=79365091
Follow the instructions, as dat was how i revived mine. Hopefully it may help u.
Note; wen using twrp, preferably use " twrp - offain "
Miflash tool:
Link 1: https://www.xiaomiflash.com/download/
Preferably use Link 1 & choose either 2016, 2017 or 2018 versions. They come preloaded with the drivers u need
Link2: https://xiaomibuzz.com/downloads/download-xiaomi-mi-firmware-flash-tool-latest-version-2018.html
Lets know how it goes
Cappucinto said:
I'm unable to use MiFlash at the moment so I can't explain the whole procedure with installing the drivers in MiFlash. But there has to be something like "Install > Drivers" or something. Maybe someone else can help out.
Try to use the working cable again, open a command prompt and type: fastboot devices
Then wait for an answer, post it here and see if the phone reboots again or if it stays in fastboot
Click to expand...
Click to collapse
Hey there When I get into fastboot and run `fastboot devices`, a code returns <tab> fastboot.
... and then the phone restarts I'm trying but I guess I'm beyond the stage of being upset, haha.
@agbadino https://forum.xda-developers.com/sho...php?p=79365091 <-- that first link seems to be broken, could you check again? I'd love to try your steps!
daize said:
@agbadino https://forum.xda-developers.com/sho...php?p=79365091 <-- that first link seems to be broken, could you check again? I'd love to try your steps!
Click to expand...
Click to collapse
Sorry bout d previous link. I believe this shd take u directly to the tutorial:
https://forum.xda-developers.com/mi...tboot-mode-t3920925/post79365091#post79365091
remember to use "twrp offain for daisy". It works better than the regular twrp for daisy
It my take and procedure that worked for me at the time. Good luck tho
Thanks! Sadly, when I get to the `fastboot oem edl` step, it fails. I get into fastboot, I quickly enter `fastboot oem edl`. CMD says finished, the screen turns off. I immediately refresh in MiFlash (COM3 is the device), I start flashing. After 4 seconds, the device turns off (windows sound "device disconnected"). The flashing runs for a total of 7-9s says "the operation completed successfully.(0x000000000: cmd <?xml version="1.0" ?><data .. etc etc
So I don't really know what to do if I can't get into EDL mode .
daize said:
Thanks! Sadly, when I get to the `fastboot oem edl` step, it fails. I get into fastboot, I quickly enter `fastboot oem edl`. CMD says finished, the screen turns off. I immediately refresh in MiFlash (COM3 is the device), I start flashing. After 4 seconds, the device turns off (windows sound "device disconnected"). The flashing runs for a total of 7-9s says "the operation completed successfully.(0x000000000: cmd <?xml version="1.0" ?><data .. etc etc
So I don't really know what to do if I can't get into EDL mode .
Click to expand...
Click to collapse
Try getting another chord and try again.
Tried some other cables. Every time I run fastboot oem edl, it keeps saying "finished", and then reboots the phone in about 5 seconds. One time, it said "Catastrophic failure" as "status" for the flashing.
Otherwise, it most often says "The operation completed successfully.(0x00000000: cmd <?xml version="1.0"?><data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="16" filename="DISK" physical_partition_number="0" size_in_bytes="4" start_sector="NUM_DISC_SECTORS-1." value="CRC32(NM_DISK_SECTORS-1.,92)" what="Update"/></data>)
But then still continues in the bootloop...
So uh they said the only thing I need to do to fix this problem is that I need to re-enable/install one of my disabled apps, com.coloros.weathersystem. but the thing is my laptop doesn't recognise/read my phone despite enabling "always allow this pc" before this incident.
What I did:
Disable the weather system app.
Enable "always allow" & usb debugging befor the incident.
Update to realme UI 2.0
What I am sure I did before the incident:
Enable "always allow" & usb debugging befor the incident.
What happened:
Flicker on homescreen.
Can't touch anything.
Long press on power button shows grey square.
V^+power button restart still works.
Vv+power buttin power off still works.
Recovery mode still works
What I did after the incident:
Tried to fastboot it on my laptop, didn't recognise despite enabling "always allow this pc" before the incident.
Tried to go to recovery mode, my laptop didn't recognise it still also.
Probable causes from what at least I believe:
I am illiterate.
Updating to 2.0.
My phone doesn't show the prompt that says "file transfer" & "charging only" during the flicker making it unable to be read by my pc/lappy.
I don't know how to adb fastboot my phone during recovery mode or without that prompt that says "file transfer" & "charging only".
Here's my footages and pictures:
The picture also shows what my internal storage has when I looked on "recovery mode">"install from phone". There's an minimal adb zip there that I have downloaded and I think that's not an installable thing
So, I flashed Derpfest A12 ROM, It boots fine but gets stuck on "getting your Android 12 Ready" screen with the animation. I can access wifi and visiblity options but not settings. I flashed TWRP from the official website to install the recovery. But now when I reboot and press Volume Down, TWRP is stuck on boot animation. So I thought just reset using fastboot and start again and pressed volume up and power button but it does NOT work. I tried the volume buttons again in the rom [i can change volume in the starting screen] and they are working. I can press volume down and power button to reboot into recovery and it works fine but gets stuck. So, I just want to have access to adb or fastboot to reset this phone but neither seems possible. I Cant enable advanced reboot in the starting screen. Fastboot doesnt work. ADB not recognizing as it is a new rom and havent enabled it [i enabled in the previous rom]. Thanks for you Help in Advance!
P.S. I have tinkered POCO F1 fairly so I am not totally new to this scene!
EDIT: Thanks for all the replies! But I solved the problem, Idk how but i got access to fastboot mode after some tries and reflashed everything and now it works, also I use linux and the adb drivers and fastboot were in repos so it was easy.
hello,
I am a novice and use a translation tool to write to you (sorry if there are errors...).
Ok I already installed roms (but a long time ago on a OnePlus One...
I have an OP5T, I want to install lineage Os 19.1 on it.
I followed the tutorial on the lineage wiki.
I installed ADB and fastboot well, as well as universal adb driver.
I'm on windows 11, it works.
I enabled debug mode
The adb reboot bootloader command works, so the tel is well seen by the pc and the tel restarts in fastboot mode.
Then nothing, no command (oem unlock) works, the computer does not seem to see such after restarting in fastboot mode.
I read some topic on the net that say that the phone must be in "battery charging" mode and not "file transfer". Me to be visible by adb I have to put it in file transfer mode, otherwise it is not seen.
If I put in recharge mode, same thing to do.
Do you have a tip or should I give up?
ezivoco_163 said:
The adb reboot bootloader command works, so the tel is well seen by the pc and the tel restarts in fastboot mode.
Then nothing, no command (oem unlock) works, the computer does not seem to see such after restarting in fastboot mode.
I read some topic on the net that say that the phone must be in "battery charging" mode and not "file transfer". Me to be visible by adb I have to put it in file transfer mode, otherwise it is not seen.
If I put in recharge mode, same thing to do.
Do you have a tip or should I give up?
Click to expand...
Click to collapse
You need to install not just the adb drivers, but the fastboot ones as well, see this guide for example. This driver is the one needed for fastboot.
My devices have always been in file transfer mode btw, I've never heard of it needing to be in charging mode only.
No, you don't have to be in "charging only" vs "data transfer".
Still, those of us who distain to be plebian keep our devices in "charging only" (with ADB on) as MTP is beneath our contempt.
(Actually, the problem is that the USB VID/PID sometimes changes with each mode and that you may not have a driver loaded for ADB only.)
Nimueh said:
You need to install not just the adb drivers, but the fastboot ones as well, see this guide for example. This driver is the one needed for fastboot.
My devices have always been in file transfer mode btw, I've never heard of it needing to be in charging mode only.
Click to expand...
Click to collapse
Renate said:
No, you don't have to be in "charging only" vs "data transfer".
Still, those of us who distain to be plebian keep our devices in "charging only" (with ADB on) as MTP is beneath our contempt.
(Actually, the problem is that the USB VID/PID sometimes changes with each mode and that you may not have a driver loaded for ADB only.)
Click to expand...
Click to collapse
ok thanks, i a going to try this