Database Info

USB device not recognised on none of my PCs

A week ago I faced this error for the first time but didn't have the time to take a look at it so I just downloaded Air Droid as a temporary solution. But then more problem appeared. The battery indicator wasn't working so I decided to fix it somehow. To dig on Google. I tried flashing different ROMs and recoveries and on and on. the problem is that I'm now stuck on bootloader. I have no system installed and that crappy TWP won't start. The splash screen just flashes and that's all. So my phone is now a brick and I just don't have any more ideas. I need to lock my bootloader somehow so I can take it back to Samsung establish some kind of USB connection so I can install a new atleast,
Any help would be very much appreciated.
Zunex

anyone?

Zunex95 said:
anyone?
Click to expand...
Click to collapse
Hello,
I assume you are using a windows pc (correct me if i'm wrong)
Use this forum > http://forum.xda-developers.com/showthread.php?t=1901617 to install drivers for your nexus s.
Afterwards, reboot your PC
Do you have adb installed? If so skip this part:
Install minimal adb and fastboot using this forum > http://forum.xda-developers.com/showthread.php?p=42407269
Try inputting fastboot devices into the terminal window and see if your device shows up
Then you can flash everything back to stock. You can do this by following the following steps:
Go to this link and download the appropriate files for your nexus s >https://developers.google.com/android/nexus/images
Use a program such as 7-Zip to open and uncompress the package to a folder of your choosing
Navigate to that folder and try clicking flash-all.bat
Hopefully that will flash your whole phone back to stock. If not you will have to manually flash each part. Do this by typing the following into the terminal, one by one, replacing the file names with the appropriate ones for your nexus s.
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju-jzo54k.zip
For example, for the first line of code, I would go into the uncompressed folder and hold down shift while right clicking the bootloader file. I would then select “copy as path”. Then I would go back to the terminal and type “fastboot flash bootloader ” then paste the path I just copied. I would then repeat for the rest of the items.
Feel free to ask questions if it does not work. Ill try to reply as soon as possible. Cheers.

Thanks I solved it. The problem was with my phone's USB port. Atleast the usb module/part of the port. I put a little metal in it then moved it around a couple times.. tried to save it. Somehow I got it working again, so I instantly flash a working recovery then went back stock. I returned my device to Samsung (It was under warranty) and they fixed it.
Cheers

Half bricked Xoom, deleted everything - help appreciated

Hello,
again i need help I have unlocked the bootloader on my Xoom, the i have flashed TWRP and downloaded a Rom and the Gapps. I copied the gapps onto the device and followed instructions which came with the rom. I was instructed to wipe "system" too which i did.
Of course that deleted the downloaded rom and gapps too. Now i have TWRP and was excited to mount USB storage and just copy over again the rom and gapps but unfortunately there is no mount as USB option.
What and how is the smartest way to go about it? I wanted to sideload over ADB but the device is not found. I have really tried everythin in my knowledge, hope someone can help
cheers

Come on guys, really need help here. My kids are killing me for the damn thing

I have same problem.......it's an issue of twrp !

Have you tried a micro sd card? (copy the rom and gapps there from a pc then put it in the Xoom, etc...)
Worst case, you should be able to grab the stock images http://forum.xda-developers.com/wiki/Motorola_Xoom and fastboot flash the device back to stock.

Have the same problem
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?

hbtwender said:
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?
Click to expand...
Click to collapse
Stock flash doesnt require adb, just fastboot mode. You may need to still install a driver, but if you can boot into recovery then the xoom should also be able to boot into fastboot mode and be recognized by a pc. If the instructions on the link I gave arent enough, I will see if I cant find something tomorrow when I am on a pc.
Sent from my GT-N8013 using XDA Premium 4 mobile app

hbtwender said:
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?
Click to expand...
Click to collapse
NOTE: This WILL erase everything remaining on the device. In the case of the above, I don't know that you have much choice, just be forewarned.
Lord AIO toolkit has all the tools you need (look at the second post if you need the Windows driver.) Extract both the stock image zip and the toolkit (unless you have the sdk, in which case as long as you can find fastboot.exe you should be fine,) to somewhere convenient. Install the windows driver if you never have before and reboot your pc.
1. Boot your Xoom in fastboot mode: Power+Vol+ until it says: Starting Fastboot protocol support (you may need to tap the Vol+ instead of holding it the whole time, my Xoom has always been a bit picky about the buttons.)
2. Connect the usb to the pc
3. In a Command prompt window, go into the extracted version of the toolkit above (or if you have the sdk, just go to where you have fastboot.exe from it)
4. Run the following commands (replacing the files at the end with the full extract path from your stock image zip extract)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
"fastboot reboot" if you want to stay unlocked or "fastboot oem lock" if you want to re-lock and follow the prompts. The Xoom will get OTA updates even if it's unlocked, so there should be no reason to re-lock unless you need to send it in for service.
The driver isn't what I used to use, but it *should* work, and the instructions should be correct as far as I can remember. As long as you don't flash the wrong image to the wrong place/run out of power during flashing/disconnect during a flash then none of this should permanently damage the hardware and should get you a working device again. It's just that it's been so long since I have personally done any of this that I have forgotten more than I ever knew .

Solved
airesch said:
NOTE: This WILL erase everything remaining on the device. In the case of the above, I don't know that you have much choice, just be forewarned.
Lord AIO toolkit has all the tools you need (look at the second post if you need the Windows driver.) Extract both the stock image zip and the toolkit (unless you have the sdk, in which case as long as you can find fastboot.exe you should be fine,) to somewhere convenient. Install the windows driver if you never have before and reboot your pc.
1. Boot your Xoom in fastboot mode: Power+Vol+ until it says: Starting Fastboot protocol support (you may need to tap the Vol+ instead of holding it the whole time, my Xoom has always been a bit picky about the buttons.)
2. Connect the usb to the pc
3. In a Command prompt window, go into the extracted version of the toolkit above (or if you have the sdk, just go to where you have fastboot.exe from it)
4. Run the following commands (replacing the files at the end with the full extract path from your stock image zip extract)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
"fastboot reboot" if you want to stay unlocked or "fastboot oem lock" if you want to re-lock and follow the prompts. The Xoom will get OTA updates even if it's unlocked, so there should be no reason to re-lock unless you need to send it in for service.
The driver isn't what I used to use, but it *should* work, and the instructions should be correct as far as I can remember. As long as you don't flash the wrong image to the wrong place/run out of power during flashing/disconnect during a flash then none of this should permanently damage the hardware and should get you a working device again. It's just that it's been so long since I have personally done any of this that I have forgotten more than I ever knew .
Click to expand...
Click to collapse
Hey airesch, thank you for your support. I couldn´t follow yours suggestion because my xoom was not recognizing the PC or MAC. However I discovered that my sdcard was broken. When I´ve tried a new one with ZIP files inside it works perfectcly and I could return to my old room doing flah in the recovery mode of TWRP2.2.
It is important to note that my Xoom did not find .IMG files inside the card but only ZIP ones. Any way it worked perfectly and I hope this solution will serve to other in solving his/her problems.
Many thanks

Well, that works too, and that was closer to what I originally suggested (tho I didn't expect you had a bad sd card.)
And yes, recoveries generally don't support IMG files directly, you need to have a specially crafted zip to flash those in. IMG files directly are for fastboot/pc tool flashing.
Congrats on fixing it.

Flashed stock recovery and thought I soft bricked my shield tablet.

First I'll give credit where it is due. From two threads on this site is where I got help with this issue:
I followed THIS guys steps for manually erasing and got the recovery images and lots of other useful information from HERE. Thank you guys very much!
OK, so, hopefully I can help someone with my little story as well. I was having issues with apps and programs crashing on me with lollipop and the new marshmallow update. The tablet just wasn't working properly and moving slow. I even had the SD card holding all my apps and larger files so I didn't overload the internal storage. So, I decided I wanted to flash back to factory/stock recovery and go from there. I did this using THIS method. I flashed via the "flash-all.bat" file (the command in fastboot is the same as the file name). I should note that there was one instance that failed during the install (I did try it again and got the same failure). Said something about “did you mean you wanted to flash this partition” or something, then showed it failed. After flashing I hit continue on the bootloader screen of the tablet and it said it was "cold booting." After about 5 minutes or so it started to boot but never made it past the NVidia screen. I tried wiping the phone with factory reset, wiping the cache, etc. and then re-flashing the recovery (again with the .bat file). I tried flashing TWRP but it didn't install apparently, because it still went to factory recovery. I even re-locked and then unlocked my bootloader to see if that would set everything straight. Nothing seemed to work. I knew I would eventually find a solution though so I kept looking. Stumbled on some other people that had the same issues but no solution (hope those people got it figured out). So here's what I did after some more research:
First, if you're in this situation and you did factory reset to try and resolve the problem, you may feel like you can no longer communicate with the device via fastboot/adb, but as long as you have the usb drive and your SDK tools installed (I used CodeWorks for Android all-in-one program) that shouldn't be a problem. You'll just have to be in the bootloader on the tablet.
-If for some reason you deleted or uninstalled your drivers and tools you'll have to download them again and then, the computer should still be able to communicate with the tablet. In the device manager under portable devices it will still show up as Module something or other. So the computer still sees the device but doesn't fully recognize it yet. Don't worry, this should still work! Just make sure you that fastboot is seeing the device by inputting "fastboot devices" in the command window and a 14 digit serial number should pop up. If it just says "list of devices" or there's nothing then you wont be communicating with the tablet.
Your device should be connected to your computer and started in bootloader mode. On your computer you should have the command prompt for adb/fastboot open. I just go to the folder where the .exe files are located and hold shift and right click in the white space of the folder, then select "open command window here."
From here follow the erase steps: stolen from manigault! :highfive:
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase recovery
fastboot erase cache
Then flash your recovery MANUALLY:
fastboot flash recovery {dir}/recovery.img
fastboot flash boot {dir}/boot.img
fastboot flash system {dir}/system.img
fastboot flash userdata {dir}/userdata.img
fastboot flash staging {dir}/blob
fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
You can download whatever recovery version you wish. I downloaded 2.2.2 because that's what my device came with out of the box on Christmas 2014. It will more then likely be a .zip file. To make this whole process a little easier simply extract the files in the .zip file where the adb.exe and fastboot.exe files are located (folder should be named platform-tools) and you can completely eliminate typing the whole directory before the file name. ***After your done flashing everything you can go back and delete those files if you want. Just double check that you're deleting the right files by looking at the original zip file. Not sure if it makes a difference but I deleted them anyway.
For example the commands in fastboot will look like this exactly :
(after extracting recovery files into platform-tools folder)
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Note: Do NOT use the flash-all.bat command as this doesn't seem to work for this situation. Do it manually like shown above. And let each individual process complete before attempting to input another command.
After this step I didn't select continue on the bootloader. You can either select reboot or simply input "fastboot reboot" into the command window. It may take about 5 minutes to start installing everything but just be patient, it should start. Sometimes with these things you have to do things twice before it works. If for some reason it doesn't work the first time then start from the beginning and try it again. It took two times for me, but that's because I installed system.img twice and was getting double screen. Newb error... and I was a bit inebriated last night when I did this.
Hope this helps someone!
Thanks again to manigault and MidgetMob!
NVIDIA download files HERE!

i think i done the same thing
but the problem i now have is i cnt get tablet into fastboot on pc. i can load fastboot on tablet with power and volume down , but the tablet only shows as MTP device in device manager. i have downloaded drivers from nvidia and no matter what i try i cant install them i have been through all instructions but scince it went to mtp device i cant get device showing in adb. The only way i can get device showing in adb on pc ist to select apply update from adb ! but none of these commands listed in your post will work because its in sideload. is there anyway i cn reset , flash custom rom ect bu using commands while device is in adb sideload.
all i get is now send the package you want to apply to the device with "adb sideload <filename>".....
if you could shed any light on this it would be much appreciated , thanks , lester

did you update official android 6.0 before? then, not working stock recovery, stock boot...
If you can enter bootloader mode, download unofficial twrp 3.0.0.0 (here http://forum.xda-developers.com/shield-tablet/development/wip-twrp-2-8-0-1-unofficial-t2877117) and flash it.
i have a working boot.img file on marshmallow if you want.. please reply.

Sorry for the late response! I have no clue how you got into sideload??? Are you talking about through the recovery on your device? You're not able to get adb/ fastboot to recognize the device, right? It doesn't matter how you get the tablet into the bootloader. Whenever you have the phone in the bootloader then you'll use the fastboot command to "talk to" the device; i.e. "fastboot devices" without the quotes. That command should show your device if it shows as an MTP device whenever you open your "device manager" in windows. That's the same exact situation I was in. Download the codeworks from nvidia like I linked above. Hopefully then you should be able to recognize your device through the bootloader. If not DM me and I'll try to help you.

I'm having the exact problem as Lester. Tablet boots into bootloader but won't connect to computer. So I go into recovery mode and nothing works except apply update from adb. Which brings up the side load message that Lester quoted. And bootloader is showing "device=locked". I am attempting to fix this tablet for a friend that messed it up trying to flash a custom rom. Problem is he had no idea what he was doing and I'm not exactly sure what he did. I do however have a lot of experience with rooted android devices and flashing so any help would be GREATLY APPRECIATED!
---------- Post added at 05:59 PM ---------- Previous post was at 05:55 PM ----------
Also, I've already tried flashing stock rom back onto the tablet by applying update from sd card function in the recovery but when I try to do that the tablet for some reason can't mount the sd card.

rom fiend said:
Tablet boots into bootloader but won't connect to computer.
Click to expand...
Click to collapse
If you've got the device in bootloader then you need to use fastboot, not adb. Try the command 'fastboot devices' and see if the device id is listed. If so then grab a factory image, unzip it and use fastboot to flash the .img files using the commands 'fastboot flash system system.img'. Just make sure to match the partition names to the files.

Hello i have similar issue except when i try flash something i get this error ''remote: file write failed''
and i have to reboot into fastboot to get it flashing fully
but even though i managed to flash everything by rebooting when i boot system nothing shows up, i can just see the back light coming on and turning off after a while
Please help

[NVIDIA K1] How can I flash to stock Nvidia ROM?

I currently have custom TWRP recovery.
I've looked around, and the only tutorial I could find for the K1 is something that needs a file it doesn't provide.
Anybody here know how? (What commands to run, what to do in TWRP, what specifically to download, what to do with said files)

The official way is to download the recovery images and flash them with your PC.
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20Tablet%20K1&tx=$additional,shield

njhuiz said:
The official way is to download the recovery images and flash them with your PC.
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20Tablet%20K1&tx=$additional,shield
Click to expand...
Click to collapse
a: I only know how to flash via TWRP - How do I flash via PC?
b: Which one of those do I download?
Thanks

A Connect both devices via USB an run the included script.
B Use the latest version

TheIncandescentOne said:
a: I only know how to flash via TWRP - How do I flash via PC?
b: Which one of those do I download?
Click to expand...
Click to collapse
Use your brain and read!
From the link given above:
SHIELD TABLET RECOVERY IMAGE FLASHING INSTRUCTIONS
To follow the instructions in this guide, you will need adb and fastboot.
These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html
Before flashing this recovery image to your SHIELD TABLET, connect your SHIELD TABLET
via USB to the PC where you downloaded this recovery image.
Next, put your SHIELD TABLET into fastboot mode using one of the following methods:
SW method:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt
HW method:
- Turn off the device
- Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
To flash this recovery image to your SHIELD TABLET, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader (see
below):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
Unlocking the Bootloader
Your SHIELD TABLET may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the "Volume Down" button to select "Unlock bootloader" option on device
- Press the "Power" button to confirm the unlock. Your device's bootloader is now unlocked.
Click to expand...
Click to collapse

Strange instructions. Official ROMs should flash fine with a locked bootloader.. and last time I checked, there was a script for all these fastboot flash X commands.
I would hope that there are more accurate instructions in the actual factory image zip.

Sorry, I'm very new to these sorts of things, and didn't realize I had to unzip the files. I thought I just had to flash via TWRP like any other ROM.

Moto x play os and twerp fix help

My phone doesn't has os i tried to fix things up but it didn't worked. The TWRP was there but now it's opening it also in fastboot mode. I tried to connect it with PC but it didn't worked. Need help, please help.

hello, problem is simple you cleared system in twrp right,
so, just follow step by step and you phone would boot normally.
first download latest firmware for your model.
unzip it.
download and install minimal adb and fastboot from here
secondly.
boot into fastboot mode as you said.
open command prompt in pc. connect your phone using adb cable (cable in the charger)
type fastboot devices
if you see your device (any number displayed like 0328438 )
if you see waiting for device then try another cable or let me know.
after that type fastboot flash file <-------- replace file with .img files in your firmware folder.
if you see any thing like flash locked or any thing try this command fastboot oem unlock
click like if i helped.