I formatted the device and sd card...I tried restarting and it would not load into the ROM anymore. (It was previously working) I messed up by formatting them both...
I was able to get the TWRP recovery installed (I am rooted) via the KF Utility. Now I am trying to mount it via TWRP with Mount > Mount USB Storage. If I can do that I can put a ROM on it and reflash a new one. However when I click "Mount USB storage" it goes to the screen "Unmount" but nothing pops up on my computer. I checked my Computer and there are no usb storage devices that pop up on my computer.
I installed the KF driver from the KF Utility folder that it comes with. I can't get it to mount...PLEASE help me!
syypher said:
I formatted the device and sd card...I tried restarting and it would not load into the ROM anymore. (It was previously working) I messed up by formatting them both...
I was able to get the TWRP recovery installed (I am rooted) via the KF Utility. Now I am trying to mount it via TWRP with Mount > Mount USB Storage. If I can do that I can put a ROM on it and reflash a new one. However when I click "Mount USB storage" it goes to the screen "Unmount" but nothing pops up on my computer. I checked my Computer and there are no usb storage devices that pop up on my computer.
I installed the KF driver from the KF Utility folder that it comes with. I can't get it to mount...PLEASE help me!
Click to expand...
Click to collapse
The KF would show up as a Android Composite ADB Interface under Android Phone. If you don't see that try installing the drivers again from the KFU > Drivers directory. Either dpinst32.exe or dpinst64.exe. If they won't install because of an error you need to find what the driver is installed as on your system, then uninstall it and reinstall dpinst... and you should be good.
If you havent got it fixed make sure there are no checks in the boxes of system and data then mount there should only be checks in cache and sdcard
Also having the same problem...
syypher said:
I formatted the device and sd card...I tried restarting and it would not load into the ROM anymore. (It was previously working) I messed up by formatting them both...
I was able to get the TWRP recovery installed (I am rooted) via the KF Utility. Now I am trying to mount it via TWRP with Mount > Mount USB Storage. If I can do that I can put a ROM on it and reflash a new one. However when I click "Mount USB storage" it goes to the screen "Unmount" but nothing pops up on my computer. I checked my Computer and there are no usb storage devices that pop up on my computer.
I installed the KF driver from the KF Utility folder that it comes with. I can't get it to mount...PLEASE help me!
Click to expand...
Click to collapse
Have you figured it out yet? I'm having the same problems where I attempt to mount through twrp and nothing happens on my pc.
I have Glazed ICS
It's odd though... when I connect while booted my kindle shows up as a galaxy, it's only when in twrp that it appears as a kindle/android adb device
Reinstalled the drivers... ect, nothing...
Any other suggestions anybody?
For some reason, formatting the sdcard in TWRP breaks its ability to be mounted via USB and must be mounted manually and formatted via your computer.
Open your CLI and prepare to send adb commands:
Code:
adb shell
echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file
You'll get a dialog saying the drive needs to be formatted. Choose quick format, FAT32, block size 4096
Be damn sure the "mmcblk0p12" says "p12", not p1 or p2, or you will be performing a little "surgery" on your device to fix it.
soupmagnet said:
For some reason, formatting the sdcard in TWRP breaks its ability to be mounted via USB and must be mounted manually and formatted via your computer.
Open your CLI and prepare to send adb commands:
Code:
adb shell
echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file
You'll get a dialog saying the drive needs to be formatted. Choose quick format, FAT32, block size 4096
Be damn sure the "mmcblk0p12" says "p12", not p1 or p2, or you will be performing a little "surgery" on your device to fix it.
Click to expand...
Click to collapse
Alright, I'm going to be rather noobish here and I'm incredibly sorry about that...
Win7 64, Kindle Fire rooted to Glazed ICS
I'm going to go through all the stupid questions at the beginning... should I have my device booted regularly or in TWRP?
In TWRP:
devices doesn't show up in adb devices
In Regular Boot:
My devices is showing up in adb devices...
after opening cmd and starting amd.exe I enter amd shell and nothing happens. cmd goes to the next line and sits there (wont let me do any kind of input)
From searching and reading I'm suppose to get a $ symbol yes?
(What it looks like)
C:\android-sdk-windows\platform-tools>adb shell
_
No. In Unix based systems (OSX, Linux, Android), the root prompt is a "#" I have no idea what it is for Windows.
soupmagnet said:
No. In Unix based systems (OSX, Linux, Android), the shell prompt is a "#" I have no idea what it is for Windows.
Click to expand...
Click to collapse
Alright, so I've been working for two weeks to get some kind of shell prompt and have been unable to get it.... Any ideas as to why I'm not able to do it?
My first suggestion will always be to eliminate any possibility of Windows errors and set up a Linux LiveUSB. By doing so, you can rest assured it isn't the computer itself causing any unnecessary difficulties.
If your shell is messed up, the way to fix it is by reinstalling the ROM. Just be careful doing so, because if you accidentally forget to wipe the necessary partitions and it prevents the system from booting, you'll likely be looking at getting a factory cable before you can move any further.
Linux is very stable but it needs to be configured before it will work with adb and fastboot. Soupkit will do that for you very easily. Just remember, the device itself plays a big role in whether or not adb or fastboot will connect. If that's the case, you may have to look at other options.
I have the same problem... the biggest problem is when there is OS the kinlde fire adb driver was different from in the recovery I went to my computer device manager and It have amazon kindle fire2 unknown and Linux storage G:\ different from the old driver is google USB or amazon kindle fire USB and the storage is diffrent too and I can't delete the old driver either... need help how can?
Oh dear, am a noob, please forgive me!!
I have a Kindle Fire HD 8.9, rooted it OK, then followed "Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial" to install TWRP.
Everything seemed ok, then got stuck on blue/white logo, so got into TWRP hoping somehow I could move a rom on there to flash it. Now I'm in TWRP , the Kindle won't show up on My Computer, so how do I do this? I did try pressing "mount" but nothing happened.
I've searched forums but am just getting more confused!!
Maybe the drivers are wrong, but I don't know how to fix that.
Tried looking at "[HOW-TO] ADB Push a ROM to your phone"http://forum.xda-developers.com/showthread.php?t=1667929, it tells me to find where my ADB is on my PC's hard drive, but I can't find anything that says AndroidSDK on my c:drive.
Oh God!! Am I doomed???
Please can someone kind help me??
Thanks guys
6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done.
http://forum.xda-developers.com/showthread.php?t=2277105
mfg
German JPL
Thank you German JPL,
I did try to follow this trobleshooting bit at the end, but I'm kinda stumped by the fact I don't know where this "ADB binary is (usually inside platform-tools folder in Android SDK directory)"
I'm on Windows 7 and there's no such thing on my c:drive. Under User, there is an ".android" folder, but I don't think that's it.
Hi pixie67,
sorry for my bad english, I'm a German speaking English writer.
in what way do you have adb drivers and fastboot drivers installed?
when did you proceed to the manual, you would still have a folder with android sdk?
===== 5. What is Android SDK, ADB, and Fastboot? =====
Android SDK is a package with the tools for an Android developer to modify devices and collect data to help them create builds and maintain a device. Included in the package is what we commonly use around here in the development world, called ADB (Android Debug Bridge) and Fastboot. ADB allows a computer to communicate with a device by means of a USB cable, allowing a developer to push and pull data between the two devices, and this is the way some root methods are discovered.
Fastboot is the term we use to refer to a diagnostic tool built into Android. This is because fastboot is the first thing a developer turns to when their device is bricked. Factory cables are designed to power the devices into fastboot, and that's all they're really good for. While ADB is for communication between two devices, pushing and pulling data, fastboot is all about writing data into the partitions on a device. We call this process "flashing". This is only for the 7 version of the device, the 8.9 version does not require the factory cable.
Generally, ADB commands in command prompts start with "adb" (i.e. "adb reboot bootloader" which commands a typical Android device to boot into bootloader mode, another name for fastboot mode). ADB commands can only be used when both devices are fully booted up, and ADB debugging is selected on the Android device. After the device boots into fastboot, the device no longer recognizes ADB commands, only fastboot commands. Likewise, in fastboot mode, commands begin with "fastboot" (i.e. "fastboot oem unlock" which unlocks the bootloader on many Android devices). While in fastboot mode, the only safe way to exit is by typing "fastboot reboot" although the usual power button will be fine for most cases.
On the Kindle Fire HD 7" and 8.9", you will notice that the fastboot commands look something like this: "fastboot -i 0x1949 flash boot boot.img" ("flash" is the command to flash a file, "boot" is the partition to flash the file into, and "boot.img" is the image file containing the booting information). The reason why there's a "-i 0x1949" is simply because of the locked-down bootloader. After we install the 2nd-bootloader, this part commands the device to flash the files into the stock bootloader, because the 2nd-bootloader doesn't accept fastboot commands.
To install the Android SDK and be able to use ADB + fastboot, go to this link: Android SDK. After you hit download, just be patient, and you will need a video reference to help set up the package properly, so click here: Video on Installation of Android SDK. To check if it installed properly, once you're done with the video, open up a command prompt (for Windows, hold the Windows key + R, and type cmd, then hit Enter), and type either "adb" or "fastboot" and hit Enter. For both cases, you should get a block of text that tells you what each command does.
To check if your device can work with ADB, enable ADB on the device (may be called USB debugging), and connect it to the computer. If there are any drivers installing, let them finish. Then, on the command prompt, type "adb devices" and hit Enter. If your ADB drivers work, you should see a line of letters and characters. Same thing with fastboot. Always do this check before you start messing around to make sure your devices are receiving the commands.
Click to expand...
Click to collapse
I have windows 7 and when I enter in the search window windows sdk, I find the folder.
mfg
GermanJPL
Hello,
I installed KindleADB.exe for the drivers. That seemed successful. I managed to root it ok,
My Kindle, in TWRP shows up in device manager as Android Phone/Android ADB interface.
I can boot into fastboot from the options in TWRP.
I've updated the android SDK package and rebooted my computer.
I can't use ADB sideload, it just sticks on "starting ADB sideload feature...."
If I reboot to system, I just end up on the white/blue logo.
I don't know what to do next
I do not understand ... have you thought you were the instructions?
you've got installed 2nd Boot Loader & TRWP after manual with ADB and fastboot .... ? why are you not looking adb.exe, then you have your folder
or you install you Andrid sdk subsequently follow the instructions, then you've got everything you need.
German JPL
I don't really understand your answer German, I've followed the instructions, but I'm still stuck on the boot screen, or in TWRP with no way to flash a ROM as there is no ROM on the device and I can't transfer a rom onto the device because mounting doesn't work and Adb sideload doesn't work.
So I'm stuck.
Help!
You have written the sideload does not work because the can not find the sdk folder. Did you find it now and sideload does not work?
Before you experiment still around for hours, start your Kindle in fastboot and play the 3 img a backup folder.
After that you start from scratch and copy before the Rome and gapps on the Kindle.
German JPL
GermanJPL said:
You have written the sideload does not work because the can not find the sdk folder. Did you find it now and sideload does not work?
Before you experiment still around for hours, start your Kindle in fastboot and play the 3 img a backup folder.
After that you start from scratch and copy before the Rome and gapps on the Kindle.
German JPL
Click to expand...
Click to collapse
I can't find a SDK folder anywhere, I've searched, I've enabled hidden folders. I don't know if this is why the ADB sideload option doesn't work, but it doesn't, it just hangs there.
I can start the Kindle in fastboot, there is a message saying "installing device driver software", then another, confirming the ADB driver software has been successfully installed. In device manager I now see
Kindle Fire listed with android adb interface.
I don't know what "play the 3 img a backup folder." means. I'm sorry. While I'm in fastboot mode, I'm not sure what to do. Can you tell me?
And I don't know how to start from scratch as I can't copy anything anywhere. Although I can see the Kindle in device manager, I can't get to it in windows explorer.
The problem is, I didn't copy the ROM and GAPPS onto the Kindle before installing TWRP and now I can't.
Oh dear, I'm sorry to be so frustrating!! Thank you for trying to help though xx
Step 2: Grabbing Files and Backing Up
Once you're rooted successfully, you need to grab the files we'll need for the installation. Go to Hashcode's thread: Kindle Fire 2nd-bootloader + TWRP for the Kindle Fire HD 8.9. Download ONLY two files: the TWRP recovery image, and the freedom-boot image. That's all, and transfer both of those to the root of the sdcard, now you can move on to Step 3: Installation if you wish to skip backing up.
I will go through the steps to backup. Remember that it is not mandatory that you do this; should you follow the guide very closely, you do not require backing up whatsoever. This just serves as an extraneous step for those who feel comfortable working with ADB and would like to participate in modding the device, in which case these files would come in handy in case the device is bricked. Again, it is NOT mandatory.
Connect the device to the computer through a normal USB cable, turn on ADB through settings. Open up the command prompt (CMD) on your computer: hold down the Windows key, and press R. This will open up Run, type "cmd" and hit Enter. Now, enter the following lines of code one-by-one, wait for a line to finish before going to the next one.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\KFHD8Backup
adb pull /sdcard/stock-boot.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD8Backup]
Now open up the Computer folder, and in the C: drive you will find a folder called "KFHD8Backup" with all of those files that you just pulled in there. Once you're at this stage, you have finished backing up. Take that folder and put it somewhere safe, on a USB drive, or an external flash drive.
If you need to flash these to restore the device in case you have bricked it, boot into fastboot mode. Place the folder and the files in it back to the C: drive before attempting to restore (if you know how to use the cd command, feel free to change the location of the files). Once you're in fastboot, start with the first line of code to command CMD to locate the backups folder, then proceed with the second, one-at-a-time:
Code:
cd C:/KFHD8Backup
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
fastboot -i 0x1949 reboot
+Note: Be patient, as some of the codes take a while due to the amount of data being transferred between the device and your computer. If nothing happens after you hit Enter on a line of code or it just hangs at nothing, close the command prompt, open it up again, and retry. It might seem scary, but if there are no codes being executed in the command prompt (you'll see data transfers with kB/s and such if there's communication), it's safe to unplug the cable or close the command prompt. Feel free to reboot your computer, then plug the cable in and try again.
Also, know that these files, when flashed through fastboot, will revert your device back to the state of when these backups were made, so once you have TWRP, these files are no longer important. The backups you make in TWRP will be just as useful, and can save you both time and patience. If, however, you want to revert to a completely stock Amazon OS software for warranty purposes, or to redo this process for any reason, they will come into play because these backups retain your apps and your settings. Otherwise, use the KFHD System Restore Tool to go completely stock.
After you have backed-up (optional), and you have the two needed files on the sdcard (TWRP image and freedom-boot image, ignore the Amazon OS and the stack override files), you can move on to step three.
Recap:
1. Go to Hashcode's 2nd-bootloader thread
2. Download both the required files and move them to sdcard
3. Use ADB to make backups (optional)
4. Use fastboot to restore the images you backed up if there are issues
Click to expand...
Click to collapse
German JPL
Thank you for helping me.
I can't transfer the 2 files as I can't access the sdcard, but I did do this initially.
Also, do I use the command prompt just from the desktop and will it work while I'm in fastboot mode as I can only get into fastboot or recovery. I can't boot normally.
I will give it a go anyway, I really am very grateful for your help
Well, I've done it!!
I made sure ADB was properly installed, following the video link German helped with. Had to make my own android-sdk folder on the C:\ drive. Put KFFirstAide100 and KFHD_SRT_v2.1 downloaded from here in the "platform-tools" folder, ran KFHD_SRT_v2.1 tool to get into fastboot (turn Kindle off first, press option 1, then n, then connect kindle to computer via cable. It will go into fastboot.
Then Go to Firstaide in fastboot mode and restore kindle via one of the options on there.
Now I'm up and running again. Yey!!
Thank you German for all your help!!:highfive:
HELP
pixie67 said:
Well, I've done it!!
I made sure ADB was properly installed, following the video link German helped with. Had to make my own android-sdk folder on the C:\ drive. Put KFFirstAide100 and KFHD_SRT_v2.1 downloaded from here in the "platform-tools" folder, ran KFHD_SRT_v2.1 tool to get into fastboot (turn Kindle off first, press option 1, then n, then connect kindle to computer via cable. It will go into fastboot.
Then Go to Firstaide in fastboot mode and restore kindle via one of the options on there.
Now I'm up and running again. Yey!!
Thank you German for all your help!!:highfive:
Click to expand...
Click to collapse
I dont get how you fixed it i am a noob can you please send me everything i need to download and how to do it? I really need to get my kindle back so i can put my cm rom on it please!
OhhRey said:
I dont get how you fixed it i am a noob can you please send me everything i need to download and how to do it? I really need to get my kindle back so i can put my cm rom on it please!
Click to expand...
Click to collapse
This should do the trick(assuming you just want to push a rom onto your device), drivers are always in my signature, adb is in the zip on the tutorial i wrote a while back. Here ya go!
HELP
stunts513 said:
This should do the trick(assuming you just want to push a rom onto your device), drivers are always in my signature, adb is in the zip on the tutorial i wrote a while back. Here ya go!
Click to expand...
Click to collapse
Good news and bad news, i installed the gapps and cm but it is stuck on the cyanogenmod screen and keeps looping. Please help! I thought i was done so close to a new android device! HELP!
OhhRey said:
Good news and bad news, i installed the gapps and cm but it is stuck on the cyanogenmod screen and keeps looping. Please help! I thought i was done so close to a new android device! HELP!
Click to expand...
Click to collapse
Do a factory reset from twrp and see if it fixes the problem.
I have been researching and trying various things for a week now, including soupkit.
Every partition on the Kindle had been wiped, so there is no OS installed.
I am able to boot my kindle into fastboot mode using fastboot -i 0x1949 oem idme bootmode 4002 which lets me flash a bootloader, firefirefire 1.4a and a recovery TWRP 2.6
However nothing I do will get the kindle to register over USB unless its in fastboot mode. I have been in linux and it does not even detect the kindle when it is plugged in. Therefore I can not mount the USB drive and put a factory image on the sdcard to flash through recovery nor can I push a factory image with adb to the sdcard to flash through recovery.
It seems my only option would be to flash a system.img through the fastboot mode which i am still able to enter, but I am unable to find a good copy of stock 6.3.2 or any other system.img that would able my kindle to boot again or possibly re-enable the ability to use adb or mount the usb drive. Hopefully someone could point me in that direction or give some other suggestion.
Maybe I'm missing something, but why can't you boot into recovery (by pressing the power button while booting to get the Recovery option) , connect via a standard USB cable (not a factory cable) from the KF to your computer, and then use 'adb push <pathname> /sdcard/' to copy to the KF whatever ROM you want to install, and then install it using the TWRP commands on the KF?
aarons510 said:
Maybe I'm missing something, but why can't you boot into recovery (by pressing the power button while booting to get the Recovery option) , connect via a standard USB cable (not a factory cable) from the KF to your computer, and then use 'adb push <pathname> /sdcard/' to copy to the KF whatever ROM you want to install, and then install it using the TWRP commands on the KF?
Click to expand...
Click to collapse
I can boot into recovery, but when I plug in a USB cable at that point, the kindle does not register on a computer. Like I said, I even tried in Linux using the command lsusb, it does not show, it will only be on the list if in fastboot mode.
Maverickwolf said:
I can boot into recovery, but when I plug in a USB cable at that point, the kindle does not register on a computer. Like I said, I even tried in Linux using the command lsusb, it does not show, it will only be on the list if in fastboot mode.
Click to expand...
Click to collapse
The answers to the following questions are probably all in the affirmative, but, just to be sure, I'll ask anyway:
Does your computer recognize other devices when they are plugged into the same cable?
Have you tried other cables?
Does the Kindle work as it should when in recovery, aside from not being recognized by your computer?
aarons510 said:
The answers to the following questions are probably all in the affirmative, but, just to be sure, I'll ask anyway:
Does your computer recognize other devices when they are plugged into the same cable?
Have you tried other cables?
Does the Kindle work as it should when in recovery, aside from not being recognized by your computer?
Click to expand...
Click to collapse
My computer does recognize other devices as well as the kindle in fastboot mode.
I have tried different cables as well.
The kindle functions in recovery aside from not being recognized. I have also tried flashing older versions of TWRP and CWM and no detection on those either.
Good afternoon, I need help in TWRP mode I can not mark usb-otg in mount.
My terminal does not have a rom because I mistakenly delete all the data.
My idea was to put the rom in a pendrive otg and intalarla from TWRP but I can not check the corresponding box.
In Fastboot mode either since my pc does not recognize the terminal, I have tried all the ports of the pc and all the cables that I have.
The drivers are well installed and adb and others work correctly.
I need your help, since the phone works very well and I changed the battery recently.
Thanks in advance.
can you mount mtp in twrp? perhaps you could try loading a rom from your pc to your phone via adb sideload in twrp.
NightRaven49 said:
can you mount mtp in twrp? perhaps you could try loading a rom from your pc to your phone via adb sideload in twrp.
Click to expand...
Click to collapse
thanks, there is some tutorial to do this. I'm pretty new in these things
to mount mtp, boot twrp, then go to mount. there will be a button on the bottom right that says enable mtp (if mtp is disabled) and tap it. if mtp is already enabled, the button will say disable mtp, so you don't have to do anything here. just plug your phone into your computer and see if it gets detected. if it doesn't get detected, again try the different ports on your computer or switch cables.
once your phone is detected, you have 2 options.
1) mtp allows files to be copied over from your pc to your phone while in twrp. so you can just copy a rom file into your internal storage and flash normally.
2) you can also flash the rom through adb sideload. first, place the rom in an easily accessible directory, such as directly on C:\. next, you can start adb on your computer by opening up terminal/powershell and typing
Code:
adb start-server
you should get a message saying adb daemon is now running on port xxx. next, open up the adb sideload dialog in twrp through advanced >> adb sideload, then swipe to start the service. just to be sure your phone is detected by your pc, type
Code:
adb devices
your phone should show up on the terminal with its serial number. now navigate to the folder where your rom is and flash it.
Code:
cd C:\
adb sideload rom.zip
make sure your phone doesn't get disconnected during the process of flashing.
I'd recommend 1) since it's a more familiar method of flashing.
Try formatting your Usb pen drive as FAT32, it worked for me. My pen drive was formatted as NTFS previously and twrp did not allow me to check box the "usb otg" option, but after formatting as FAT32 it worked like a charm.
Good luck
I am using a custom ROM and I want to go back to stock and relock the bootloader, but I'm having a problem with my computer not properly being able to connect to my phone while in fastboot or sideload modes. From what I've read online it's because I'm using the USB-C -> C cable that came with the phone, but I don't have a USB-C -> A cable. According to the recovery menu, besides the usual adb sideload procedure, it should be possible to flash a zip file (OTA) if the file is in the /sdcard folder, but I don't know how to put something there.
whoadood said:
I am using a custom ROM and I want to go back to stock and relock the bootloader, but I'm having a problem with my computer not properly being able to connect to my phone while in fastboot or sideload modes. From what I've read online it's because I'm using the USB-C -> C cable that came with the phone, but I don't have a USB-C -> A cable. According to the recovery menu, besides the usual adb sideload procedure, it should be possible to flash a zip file (OTA) if the file is in the /sdcard folder, but I don't know how to put something there.
Click to expand...
Click to collapse
Install MiXplorer from this forum: https://forum.xda-developers.com/t/...released-fully-featured-file-manager.1523691/
Start it, and tap the 3 dot menu in the upper right corner.
Select Servers, Start HTTP/WebDav Server
In your web browser, go to the URL displayed.
Click "Choose File" and select your file.
Click Upload
Done
First, make sure that all your drivers are successfully entered. In the rec mode, the ADB devices command can display the device, and in the bootloader mode, the FastBoot devices command can display the device. Configure the environment variables for the ADB on your PC side, and put the files you want to put into the sdcard into a file folder in an all English directory, Then use ADB push to drag in the file to be placed in the sdcard directory / sdcard command to push
Eventually I could get ahold of a USB-A -> USB-C cable. But thanks for your suggestions!