Hi guys
I am new to posting here but an avid viewer, now recently I had a problem with my device where the battery died and the device no longer boots and I cannot flash a new rom or recovery, the same as these two posts:
http://forum.xda-developers.com/moto-g-2014/help/device-bricked-0-battery-left-t3085322
http://forum.xda-developers.com/moto-g-2014/help/moto-g-2014-dead-t3072930
Now unfortunately unlike those two I am unable to send my device to Motorola for repairs as it was bought in another country, now I have tried all the options available to me, even all those mentioned in the two posts, including Wipe /data /system /cache in twrp & fastboot, but /data remains unchanged. I was running Blisspop V3.2 before the issue and no matter what I do or how I flash it keeps showing the blisspop boot logo & gets stuck there.
After a few attempts i switched to adb, and in adb I realised that the /data partition is set to "read only"
{
"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"
}
And as you can see chmod cannot change the permissions for the /data partition.
Now my question is this does anyone out there have any clue as how reset the data partitions read-write permissions without using chmod ?
FYI this device is a paper weight at the moment and I would like to see if I can do anything about that and maybe learn something on the way.
Leader0fr4tz said:
Hi guys
I am new to posting here but an avid viewer, now recently I had a problem with my device where the battery died and the device no longer boots and I cannot flash a new rom or recovery, the same as these two posts:
http://forum.xda-developers.com/moto-g-2014/help/device-bricked-0-battery-left-t3085322
http://forum.xda-developers.com/moto-g-2014/help/moto-g-2014-dead-t3072930
Now unfortunately unlike those two I am unable to send my device to Motorola for repairs as it was bought in another country, now I have tried all the options available to me, even all those mentioned in the two posts, including Wipe /data /system /cache in twrp & fastboot, but /data remains unchanged. I was running Blisspop V3.2 before the issue and no matter what I do or how I flash it keeps showing the blisspop boot logo & gets stuck there.
After a few attempts i switched to adb, and in adb I realised that the /data partition is set to "read only"
And as you can see chmod cannot change the permissions for the /data partition.
Now my question is this does anyone out there have any clue as how reset the data partitions read-write permissions without using chmod ?
FYI this device is a paper weight at the moment and I would like to see if I can do anything about that and maybe learn something on the way.
Click to expand...
Click to collapse
adb root; adb remount
Does your phone get recognized by your pc?
Mine went black a few days ago and i cant do anything.
LuK1337 said:
adb root; adb remount
Click to expand...
Click to collapse
Hi LuK1337
Firstly thanks for the help.
adb root returns a message saying adb already has root access.
asb remount only remounts the /system partition (unless im using it incorrectly).
So far I have well and truly wiped every partition of this device excluding the /data partition which returns a message saying partition is read-only
So I have now officially proved that this is a hardware issue at least for me, look here for my findings:
http://forum.xda-developers.com/moto-g-2014/help/battery-drained-encrypted-device-pinned-t3079871/page2
Short version I've used every available software method including 'Fastboot Erase all' which has no effect.
So would anyone be able to help build a usb jig or finding a hardware way to fix this ? my device has been opened so I would be able to provide high res pictures of the motherboard to anyone who needs it, will also upload when my 10 post count has been reached
Solved: Dead battery stuck in fastboot mode unable to flash any image. Works for all.
Same thing happened to me.
Nothing to do with the hardware.
Steps to Follow:
1) Open fastboot mode in your phone.
2)Connect to your pc and open cmd in platform-tools folder.
3)Place the twrp.img file in platform tools.
4)In cmd, type : fastboot boot twrp.img (Very Important Command)
Now your phone will boot to recovery mode i.e. TWRP and the connect it to charger. It will charge slowly.
Now you can flash anything using ADB Sideload.
(If found helpful, hit the thanks button )
Related
{
"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"
}
My friend has a Bell GT-i9000M phone. I am not sure what he did but I believe he applied lagfix and tried to update to 2.3
Current status is that I am able to get to Dowload mode.
I have tried:
1. Darkys stock rom: http://www.darkyrom.com/community/i...-this-is-the-stock-rom-for-sgs-gt-i9000.1115/
(No success)
2. JPU: http://forum.xda-developers.com/showpost.php?p=10449932&postcount=7 (no success)
3. JL2/Speed Kernel http://forum.xda-developers.com/showthread.php?t=905975 - No success.
I can get into recovery but I get can't mount DBDATA error.
Currently the phone is rebooting constantly at Galaxy S GT-i9000M screen.
If I flash only JPU, it get stuck a round circle, I have waited about 15 mins with no change. I have used ODIN 1.3 and 1.82 and 1.83.
HELP!
What else to try?
This is where I am so far:
Phone boots with 2.2 with 0 for SD card and internal. Followed instructions as per: http://forum.xda-developers.com/showthread.php?t=973687
Now, trying to use sdparted or parted.
If I use parted, using http://forum.xda-developers.com/showthread.php?t=937072 and http://forum.cyanogenmod.com/topic/...56396__hl__sdparted__fromsearch__1#entry56396, I am able to get to:
Step 4:
okay now copy all the six files you pushed into the /system directory to the /sbin directory and set permissons like this:
#cp /system/[xyz] /sbin
#chmod 0755 /sbin/[xyz]
(replace the [xyz] with the filenames..do this for all 6 files..)
now get into the /sbin directory
#cd /sbin
#ls
This should display all the files in your /sbin
The parted files you copied should be here...
Now lets start partitioning..
#parted /dev/block/mmcblk0 and hit enter.
here it should get you into the parted prompt..(parted)
enter "print"
>(parted) print
Click to expand...
Click to collapse
However instead of listing, I get "can't have a partition outside the disk parted"
I am stuck at this point. I am currently using adb in normal mode. If I reboot to CLM SpeedMod recovery, I only get $ when typing adb shell, and su results in permission denied. I have tried installing super user via recovery but no go.
ThoughtS?
Anyone ?
10char
I had the same problem a while back
You should be able to fix it if you odin flash UGJL2
^ Endless BOOT!
Followed JL2 instructions from http://forum.xda-developers.com/showthread.php?t=853950&highlight=JL2
SaHiLzZ said:
^ Endless BOOT!
Followed JL2 instructions from http://forum.xda-developers.com/showthread.php?t=853950&highlight=JL2
Click to expand...
Click to collapse
endless boot is fine as long as when you go back into recovery your SD card can be mounted unlike before.
So i ask, is it mounting now?
If it is, your free to flash any other ROM
Hi Jay,
No go on recovery mode. Vol up + home + power doesn't get me anywhere. Vol down + home + power gets to download mode.
Phone continues bootlooping...
you mean you are still getting the same error in recovery?
sorry that didnt work for you as i had the exact same error and that is what worked for me.
I then flashed darky 10.2 RE once i could mount my SD card
I got my XT1086 from Amazon.de yesterday.
There was no OTA for Lollipop yet, so I figured I could force it using this method:
http://forum.xda-developers.com/moto-g-2014/development/tool-moto-g-xt1068-andoid-l-updater-t2964933
It worked. I had an unlocked bootloader, lollipop, and root.
Wanted to remove the bootloader warning message at start-up, so I did this:
http://forum.xda-developers.com/mot...x-remove-unlocked-bootloader-warning-t2875385
It kinda worked, but took ages to start up.
Had problem with dual sim not working, did a factory reset from the phone menu. Didn't boot since then.
Get stuck on the image that replaces the unlocked boot loader warning, it appears and disappears seconds later (over and over again)
Can't turn off, automatically restarts
Don't get the normal charging screen
I can get into fastboot
I can get into recovery (takes a while to open)
So I'd like to go stock again. Found this: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Dev-host is impossible slow, can't download from there (with my 60Mbit/s connection). Official mirrors are all down?.
Downloaded "RETDEALL_XT1068_4.4.4_KXB21.85-23_cid7_CFC.xml.zip" from somewhere else, but that does not appear to work with the method above. I see warnings in recovery like "Unable to mount /data, /cache, /system".
Any other method to return to stock? Any help?
I flashed the cr*p out of my old Xperia X10 and HTC Sensation without big issues, but now I f*cked up...
Press volume down+power off button for at least 3 min then release the button now you will see fastboot mode of your phone connect your phone to pc and flash twrp recovery and then restore lollipop from below link
http://forum.xda-developers.com/showthread.php?t=2964330
vikasb32 said:
[...] http://forum.xda-developers.com/showthread.php?t=2964330
Click to expand...
Click to collapse
Need to fill in my phone's serial number. I don't have that serial number written somewhere, and can not get it from the about menu 'cause I can't boot right now...
Can't copy to internal memory either (can't connect as multimedia device to pc), only external SD.
JoWannes said:
Need to fill in my phone's serial number. I don't have that serial number written somewhere, and can not get it from the about menu 'cause I can't boot right now...
Can't copy to internal memory either (can't connect as multimedia device to pc), only external SD.
Click to expand...
Click to collapse
you able to go to fastboot mode?
I found my phone's serial number by going to TWRP recovery, and trying to make a full backup to my SD card.
It didn't make a backup, but made the (empty) folders. I put the lollipop TWRP in there. I see it in recovery but can't restore it.
When I go to TWRP -> Backup, I see the following partitions and their sizes:
Data: 0MB
Cache: 0MB
System: 0MB
Boot: 9MB
PDS: 3MB
When I press the backup button, I see the error message " unable to mount '/system' " (and the other partitions). I get the same error when I try to restore that backup.
I'm on TWRP v2.8.0.1, tried to flash v2.7.1.1 from here with this tool, but that was not successful...
Edit: TWRP 2.7.1.1 is installed now. Still can't restore that lollipop archive because " unable to mount '/system' ".
I found this:
http://droiddefy.com/how-to-update-...69-to-official-android-5-0-lollipop-manually/
Same files as I used before, different method. Although I got errors at the first 2 steps, this method worked. I have a working lollipop again.
Still the US version (as before), without working dual sim. Need to figure out how to get another (Brazilian?) version working.
{
"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"
}
http://forum.xda-developers.com/moto-g-2014/development/windows-tool-moto-g-2014-xt1068-dual-t2983295#post57801996 this will restore kitkat to XT1068 Dual Sim for ALL retail
Hi there. My cousin's phone stopped working some weeks ago. He tried to wipe everything via TWRP and installing different ROMs but no ROM seems to work. Now, when he does a complete wipe, he gets the error "E:Unable to wipe '/sdcard1' -- unknown file system 'auto'" and "Unable to mount storage". Also, now everytime he tries to copy a ROM to the TWRP folder (the only folder which appears on his MacBook or his friend's PC) it stops at 16k and he can't copy it.
What can he do to fix this? Nothing seems to work and a guy at a service center said it was a disk error and that there was no hope for the phone.
Here's a screenshot of it:
{
"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"
}
Thanks in advance!
Uhm... Why don't you remove the faulty micro SD from the phone?
This doesn't look like a bricked phone at all - "storage" and "sdcard1" refer to external storage.
Remove the phones's cover and remove the SD card (do NOT go beyond step 2, FFS). Then you can try to run some diagnostics or format it on your working phone, tablet, MAC or PC or you can buy a new one - they are quite cheap.
Then add a proper ROM (and proper GApps) on the card and stick it back in. Moto G 2014 comes in two variants - make sure your cousin's device is an actual Titan - chances are it is a Thea, if you're in Europe; that's why the TWRP doesn't want to install it. Choose one from here.
Remember you have to delete everything on the internal card through the recovery utility I see in your image before flashing a new ROM - do NOT wipe the SD Card; it stores your installation files: the properly chosen ROM and GApps you add after you format it through a different device.
If it works, make sure you do NOT format it as adopted/internal storage when/if asked by the installation wizard at first run, once the flashing is complete. This is probably why the phone got in this state in the first place.
Now I have it in my hands, this is the situation:
- Both on my PC and in TWRP it says I have 766MB free of a total of 5637MB when I don't have anything stored there and when I try to copy anything onto it it just gets stuck at 0% forever
- Tried repairing and changing file system: apparently Data is F2FS and the rest is EXT4 but everytime I try to repair or change any partition it says it worked but then it's all the same (still not working, with the file system it had before)
- Tried updating to the newest TWRP (via fastboot and also TWRP) - like what happened above, it says "done" but then it shows the TWRP version number I had before (3.0.2-3 and not the 3.1.1-0 I tried to install)
- He had no SD card inside but apparently had already tried to install a ROM with it. I put a 4GB one inside with the lastest LineageOS and all I get is "E1001: Failed to update system image unconditionally... / E:unknown command [log] / Updater process ended with ERROR: 7 / "Error installing zip file '/sdcard1/lineage.zip'
- Also the error "Unable to mount storage" is constant
I am running out of options here, don't really know what else I can do...any help? Thanks in advance!
Framboesa96 said:
Now I have it in my hands, this is the situation:
- Both on my PC and in TWRP it says I have 766MB free of a total of 5637MB when I don't have anything stored there and when I try to copy anything onto it it just gets stuck at 0% forever
- Tried repairing and changing file system: apparently Data is F2FS and the rest is EXT4 but everytime I try to repair or change any partition it says it worked but then it's all the same (still not working, with the file system it had before)
- Tried updating to the newest TWRP (via fastboot and also TWRP) - like what happened above, it says "done" but then it shows the TWRP version number I had before (3.0.2-3 and not the 3.1.1-0 I tried to install)
- He had no SD card inside but apparently had already tried to install a ROM with it. I put a 4GB one inside with the lastest LineageOS and all I get is "E1001: Failed to update system image unconditionally... / E:unknown command [log] / Updater process ended with ERROR: 7 / "Error installing zip file '/sdcard1/lineage.zip'
- Also the error "Unable to mount storage" is constant
I am running out of options here, don't really know what else I can do...any help? Thanks in advance!
Click to expand...
Click to collapse
Why don't you try reflashing the stock rom..Once I encountered a similar problem and reflashing the stock rom solved it
Hi all! This is my first attempt to flash a custom rom and I'm stumbling. Summary below:
DEVICE AND SYSTEM:
Xiaomi Mi 6X
Running MIUI 11.0.6.0(PDCCNXM) (based on Android 9)
Device bought in China in 2018, not used until now, only updated through Xiaomi OTA.
Mi Unlock status - Unlocked
Developer options unlocked
USB debugging - activated
Phone not rooted.
Phone has no lock screen password set.
FILES TO FLASH:
1. dm-verity anti-rollback flash:
no-verity-opt-encrypt-6.0.zip
2. Paranoid Android custom ROM:
pa-quartz-5-wayne-20200924.zip
METHOD
I'm using Google pltaform-tools (https://developer.android.com/studio/releases/platform-tools) + TWRP files (https://twrp.me/xiaomi/xiaomimi6x.html) and command prompts in adb and fastboot.
WHAT HAS WORKED SO FAR
adb devices OK - cmd shows hexa key
adb reboot bootloader OK - phone enters fastboot
fastboot flash recovery twrp.img OK - cmd shows Finished. Total time: 1.504s
fastboot reboot (holding recovery key combo to avoid entering automatic MIUI recovery) OK - TWRP loads
Then the problems start. TWRP shows:
Mount
Decrypt Data
Enter Password
and no password in the realms of man or heaven works. by clicking cancel as a workaround several mounting problems appear:
THE ISSUE
Since TWRP can't decrypt internal storage, I can't find the zip files I copied to the phone's memory.
Googling around I found the OTG option and tried it. But as it turns out it's also impossible to mount OTG (on Mount, the option for OTG appears but clicking it does nothing)
Googling more I found out about abd sideload, but TWRP fails to start the feature (on Advanced -> ADB sideload -> select Wipe Dalvik Cache + Wipe Cache)
Also googling intensely I found that by wiping the memory (on Wipe - Format Data - write "yes") then reentering recovery it was possible for TWRP to enter a decrypted mode. after doing this no password is required but both OTG and ADB show the same problems as before (and of course the internal memory files are no longer there).
As a summary of my woes, this is what I've tested so far and the results:
{
"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"
}
Assorted tests with older versions of TWRP have exactly the same results.
After every wipe I have to set up MIUI11 again, open developer optios, allow USB debugging etc. My fingers hurt. Morale is low. My soul is leaking. Any ideas on where to go next? Is this some unfixable incompatibility between TWRP and MI? I think I've exhausted the paths I can find by just googling around like a progressively more hairless maniac noob.
TWRP sucks for mi 6X. Download this one (OrangeFox Recovery) and everything works fine.To install it extract the zip and flash the recovery.img that is there. After that reboot to recovery and if it still asks for password just ignore, go to menu, manage partitions, clik on data, click on the button that will show, then format data and type yes. This will clean every partitions (It's the only way i found to fix encryption since our device doesn't support sd cards)Then download the Rom you want to your pc and then copy to your phone storage and install it. Good Luck.
Hello
I have a Kindle Fire HD 7 2nd gen and it is stuck on the "Kindle Fire" logo. I bought a factory cable and get a 'fastboot' screen when connected to my Windows laptop. But in ADB no devices are listed and when I try the command 'fastboot -i 0x1949 getvar product' it says ' <waiting for device>' What can I try next? Any help would be great
Thanks in advance
check the device manager of PC, then maybe you will see a warning devices. install the attach files.
Finally someone replied. I looked in Device Manager and saw something in yellow called "Tate-PVT-08". So Windows was not recognizing the Kindle. I installed the Kindle ADB drivers from rootjunkysdl.com and now "fastboot -i 0x1949 getvar product" gives me "Tate-PVT-08"
My guess it is working now, but when I try to flash boot, recovery, and system img's from the KFRT here it does nothing and I'm still stuck in "Kindle Fire" logo/bootloop. What is the problem ? Is this thing hard bricked ?
Yes. I also have similar issue:
during I'm running the "fastboot -i 0x1949 flash system system.img"
My thread
I feeling that's should be a root problem. Since during I'm running (adb shell su -c reboot fastboot) there shown a pop windows on the KFTT.
shall ask the permission
with my understanding, that should be can mount -o remount rw /system. to get rw privilege to reflash system.
But, nothing..
and sdcard, no data can be removed or deleted. Read only..
I read your thread and if you had root (I did not) that may be the issue or else try a new USB 2 port or computer. But I need to ask where you got bootloader.img from ? I found out boot.img is only the kernel and ramdisk, so it is likely the bootloader is damaged.
seskanda said:
I read your thread and if you had root (I did not) that may be the issue or else try a new USB 2 port or computer. But I need to ask where you got bootloader.img from ? I found out boot.img is only the kernel and ramdisk, so it is likely the bootloader is damaged.
Click to expand...
Click to collapse
a long story. Before, I rooted it to remove some initial software from official version. then, turn it down a long time, about 2 years. Last week, I'd like to reboot it to check. Then, I found the system looks like to read only on lastest time. Even login system to remove any software, after reboot. they would be back. I tried to flash the img, such as boot, recovery, system and so on. you can check.
{
"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"
}
except kfhd7*.img . I reflashed them one by one, except system, other should be OK.
I tried "adb shell mount -o remount rw /system" or "chmod 669 " but doesn't work.
looks I have to click the allow the "shell" privilege as same as I ran "adb shell su"
I tried to hold the root to run all commands....
That is a lot of partitions in this screenshot, where did you find and get them from? The ones of interest are bootloader, crypto, dfs, dkernel, efs, idme, and xloader. Most of these I have no clue what they do and are for. Other than the obvious like boot and bootloader. I think xloader has something to do with the bootup process too. I'm not able to use ADB at this point, only fastboot, and that only takes img files, and system is a folder in the firmware .bin files from Amazon. There is no easy way to convert that into a system.img
seskanda said:
That is a lot of partitions in this screenshot, where did you find and get them from? The ones of interest are bootloader, crypto, dfs, dkernel, efs, idme, and xloader. Most of these I have no clue what they do and are for. Other than the obvious like boot and bootloader. I think xloader has something to do with the bootup process too. I'm not able to use ADB at this point, only fastboot, and that only takes img files, and system is a folder in the firmware .bin files from Amazon. There is no easy way to convert that into a system.img
Click to expand...
Click to collapse
where did you find and get them from? From Website. Yes, official way only the bin file. But if you'd like to write the KFTT with fastboot to flash. only img. files.
There is no problem on the img files. only I can't flash. There should be a way to format /system as re-partition something like that. Or a way to reset chip of memory.
03300209 said:
where did you find and get them from? From Website. Yes, official way only the bin file. But if you'd like to write the KFTT with fastboot to flash. only img. files.
There is no problem on the img files. only I can't flash. There should be a way to format /system as re-partition something like that. Or a way to reset chip of memory.
Click to expand...
Click to collapse
I see and which website might that be? But what i meant is where did the website get the partitions from. Yes hope to find out how to turn a System folder to an img
If you look up some commands for fastboot there is a format option but not sure if it will work for you. I'd try it anyways just to see the errors. That will be quite hard to do
seskanda said:
Finally someone replied. I looked in Device Manager and saw something in yellow called "Tate-PVT-08". So Windows was not recognizing the Kindle. I installed the Kindle ADB drivers from rootjunkysdl.com and now "fastboot -i 0x1949 getvar product" gives me "Tate-PVT-08"
My guess it is working now, but when I try to flash boot, recovery, and system img's from the KFRT here it does nothing and I'm still stuck in "Kindle Fire" logo/bootloop. What is the problem ? Is this thing hard bricked ?
Click to expand...
Click to collapse
I am stuck in a similar bootloop as you describe. I can only get the device to power on for a second. It shows the Kindle Fire Screen, the fastboot screen, then it shuts back down. I tried this with the OEM cable, a third-party cable, and a fastboot cable. I also tried all three cables in my PC over USB 2 and Windows constantly sends a notification saying USB device not recognized.