Database Info

[Q] Mount USB storage under ClockWorkmod Recovery 6.0.1.0

Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max

Use this guide to recover your device.

Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.

How did you erase everything? Was it through fastboot or CWM?

I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.

maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...

maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2

*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2

The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?

Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2

Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307

I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2

[Q] PC Does Not Recognize Device and Another Dumb Thing I Did

I did a really, really dumb thing a few months ago. I flashed a wrong something or another to fix an issue I had with my keyboard crashing after flashing another wrong thing..
Anywho, I couldn't get the damn keyboard to stop crashing for the life of me, so I set out to FORMAT/ CLEAR EVERYTHING ON MY PHONE. Yikes.
At this point, I can boot into recovery(CWM) and DL mode, but my PC will not recognize my phone at all. I installed your S3 toolkit v7.0, hoping it would help, but nay.
I cannot boot fully into Android to allow usb debugging, etc.
I can mount and unmount internal sd, cache, etc, but no drivers are being installed because it is not being recognized.
I've uninstalled Kies, etc.
HALP!HALP!

Daniel_NC said:
I did a really, really dumb thing a few months ago. I flashed a wrong something or another to fix an issue I had with my keyboard crashing after flashing another wrong thing..
Anywho, I couldn't get the damn keyboard to stop crashing for the life of me, so I set out to FORMAT/ CLEAR EVERYTHING ON MY PHONE. Yikes.
At this point, I can boot into recovery(CWM) and DL mode, but my PC will not recognize my phone at all. I installed your S3 toolkit v7.0, hoping it would help, but nay.
I cannot boot fully into Android to allow usb debugging, etc.
I can mount and unmount internal sd, cache, etc, but no drivers are being installed because it is not being recognized.
I've uninstalled Kies, etc.
HALP!HALP!
Click to expand...
Click to collapse
If you boot into DL mode and run odin on your PC does it fail to see the device?

apacseven said:
If you boot into DL mode and run odin on your PC does it fail to see the device?
Click to expand...
Click to collapse
I'm waiting on my PC to free up again(currently on a Mac). I had not tried Odin because in the past I was unable to mount internal SD, which I understood was keeping it from being recognized. I instead thought the Toolkit would do the trick automatically, though I most likely had the wrong idea. Everything is mountable again (for some odd reason), so I will give it a go.
Could I accomplish downloading drivers and flashing rom to device using Odin alone? Or should I use the Toolkit?
Thanks!

Daniel_NC said:
I'm waiting on my PC to free up again(currently on a Mac). I had not tried Odin because in the past I was unable to mount internal SD, which I understood was keeping it from being recognized. I instead thought the Toolkit would do the trick automatically, though I most likely had the wrong idea. Everything is mountable again (for some odd reason), so I will give it a go.
Could I accomplish downloading drivers and flashing rom to device using Odin alone? Or should I use the Toolkit?
Thanks!
Click to expand...
Click to collapse
Installing the drivers is independent from using odin. Install the drivers on the PC, fire up odin, connect phone (that has been booted into DL mode) and see if it connects. If it does, just flash a stock image and you are back in business.
You can use this driver http://d-h.st/vMk

apacseven said:
Installing the drivers is independent from using odin. Install the drivers on the PC, fire up odin, connect phone (that has been booted into DL mode) and see if it connects. If it does, just flash a stock image and you are back in business.
You can use this driver ...
Thanks!! I'll give it a shot now.
Click to expand...
Click to collapse

apacseven said:
Installing the drivers is independent from using odin. Install the drivers on the PC, fire up odin, connect phone (that has been booted into DL mode) and see if it connects. If it does, just flash a stock image and you are back in business.
You can use this driver......
Click to expand...
Click to collapse
Odin is not recognizing the device. Should I unmount or mount anything on the device for this to work properly? I have drivers installed.

PC does not recognize the phone

First of all I apologize for my English
Phantom V7 installed the kernel on my Xperia L C2104 and was trying to install CyanogenMod 11 but installation gave error. I tried to use the backup I had made with Titanium Backup and it worked (at least in the message that appeared) but when I called the phone he stood on part of the kernel logo. I can access the TWRP, already used Eipe Data, Cache and Dalvik but not out of that screen.
Well after that I tried to use Flashtool to return to the stock ROM but FlashTool not recognize my phone and now neither computer recognizes. When I connect it makes the characteristic sound when connected to a USB but soon after that the same sound plays 3 times really fast.
I do not know what to do already that the computer does not recognize the phone. Already installed the drivers, tried using another computer and so far nothing ...
Help me.
Note: I have no SD card

tnagato said:
First of all I apologize for my English
Phantom V7 installed the kernel on my Xperia L C2104 and was trying to install CyanogenMod 11 but installation gave error. I tried to use the backup I had made with Titanium Backup and it worked (at least in the message that appeared) but when I called the phone he stood on part of the kernel logo. I can access the TWRP, already used Eipe Data, Cache and Dalvik but not out of that screen.
Well after that I tried to use Flashtool to return to the stock ROM but FlashTool not recognize my phone and now neither computer recognizes. When I connect it makes the characteristic sound when connected to a USB but soon after that the same sound plays 3 times really fast.
I do not know what to do already that the computer does not recognize the phone. Already installed the drivers, tried using another computer and so far nothing ...
Help me.
Note: I have no SD card
Click to expand...
Click to collapse
which rom do you restore?
try to fastboot kernel of the rom you restore using command.
Sent from my Nexus 7 using XDA Premium

Used a second laptop here to make it work. Flashed it and now it works just fine. Maybe it has something to do with the drivers, lol.

Mate 8 NXT-L29 BRICKED? LOOP? NO OS! NO RECOVERY! NO FASTBOOT! NO ADB! NEED HELP PLS

Hello guys..
I really have a problem right now! I appreciate everyone who tries to help me. I´ll try to expain what exactly is my problem with my Mate8.
Also I´d like to apologize for mistakes of gramatics, because im acutally from Germany..
So, my phone was working right, and actually everything was okay. With time it got so slowly, because storage was full with datas and so on. I tried to clean up some things to get it again a bit faster and so on, but that did not make it (at all). Also windows wont recognize the phone anymore. When plug in the USB it didnt even asked for data, charging or photos.. also I had problems with charging, it took toooo long for a few %.
I was on "KANGVIP" Rom (as much I know i changed stock to this custom rom) https://forum.xda-developers.com/mate-8/development/rom-kangvip-slim-t3318572
Time passed untill 3 days I decided to flash a new rom normally, like put rom on sd card, wipe dalvic and cache, and so on. I wanted this rom; Lineage OS https://forum.xda-developers.com/mate-8/development/6-0-1-cyanogenmod-13-port-t3512985
But everything came up with different errors for different actions I did like this:
"cant mound sd card"
"cant mount inernal storage"
"cant mount data"
"cant format data"
"cant mount system"
"cant mount cache"
etc. etc...
I tried to change file system to EXT3. EXT4, EXT2, FAT, and so on, for Data and System. Nothing worked correctly (but I had still on some Filestystems instead of 0MB like 2700MB). Still not working correct... On TWRP.
Then I tried to update TWRP from 3.0.1 to 3.1 (new one released). Because I saw, more precisely, I heard that an update can fix this mount issues I had.
Said and done, I updated it and instead of 3.1 I had 3.0.2 (idk why but I didnt care). But still theese problems happend.
So then I saw in a Video on youtube (which I cant find anymore) that another recovery like CWM can fix this issues. So I downloaded CWM recovery.img and installed it with TWRP an rebooted to recovery again. And now I´m in a situation, in wich I dont know what to do.
Now the phone tries to start, but no OS installed.
Try to get into Recovery, but no recovery aviable exept eRecovery which is failing with data when trying to restore.
Problem is also that Fastboot and ADB is not working. Installed HiSuite, ADB drivers, Samsung drivers (though could help).
Tried Knife Italian, but no connection to pc..
Tried different cable, no luck.
Tried windows 7, 8.1, 10 Home and now im on Win 10 Pro 64x.
All I can do is to boot into Fastmode, but cant do anything. And when I try to boot the phone normally it stucks on "Your device is booting now..." because no OS...
PLEASE HELP ME GUYS! I REALLY NEED THAT PHONE :crying::crying::crying::crying::crying:
THANK YOU !!! :good:

Hallo,
If your phone is still recognized in fastboot mode, you can try following up my tutorial here » https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
I was experiencing the same problem. No OS, no recovery, no fastboot flash possibility, only fastboot booting. Keep in mind that you will need 15€ for this method to work but it is the only way to resurrect your device.
PM me if you need further assistance.

djmitza222 said:
Hallo,
If your phone is still recognized in fastboot mode, you can try following up my tutorial here » https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
I was experiencing the same problem. No OS, no recovery, no fastboot flash possibility, only fastboot booting. Keep in mind that you will need 15€ for this method to work but it is the only way to resurrect your device.
PM me if you need further assistance.
Click to expand...
Click to collapse
Thank you for the reply my friend.
The problem is, that it only boots in to fastbootmode, but any pc wont recognize it. I tried even with Mac...:crying:
Greetings

DC-Phoenix should recognize the fastboot brick state even if the device doesn't show up in Minimal ADB & Fastboot. Try my method and let me know if it works.

Hi guy's.
DC Phoenix save my mate 8 with factory firmware.
I was the same problem like you and search one week a solution and after I decided to pay and try Phoenix and now I write from my mate 8
Before buy 15€ of credit you can download and try to connect your phone on DC Phoenix

does the DC phoenix method take your phone to absolute stock? ie, stock firmware +recovery + Locked + no root?

Yes. You will have the factory firmware (stock) but with unlocked bootloader.

Galaxy Tab 2 GT-P5110 Restarting and does not install stock or any other rom.

Hi guys, after many tries, many googling and youtube research, I dicided to share my problem with our community
1. At sunday, my galaxy tab started to restart continuously, It was recharging and I took some time to see.
2. I tried to activate USB DEBUGGING but when It Restarts, it's usb debugging is disabled again.
3. I'm using Stock Rom Again...was;
4.Using Stock Recovery.
5. Tried to install many others recovery's with odin and it seems to be ok but after a restart, its all back to stock recover.
6. Tried to install Stock FW again by Odin and its stuck about 50% FAIL
7. Tried to install CFW and Other Roms by SD Card but it shows a messege "Failed to check Signature" aborting... maybe because of stock recover.
8. Not rooted, usb debugging DISABLE
9 Tried to activate USB Debugging by odin, installing a patch, without success.
10 Samsung KIES does not recognize it in Download Mode.
11. I have samsung drivers installed.
one more information, when I start in recovery Mode, it shows first an android pic and a messege NO COMMAND, then proceeds to RECOVERY(STOCK).
What Can I do?? I Did Everything I can find on Internet. Is there a phisical problem??
Best Regards!!

Seems like a similar issue like mine. Check my post about behavior of my tab 2 7" (P3100) at https://forum.xda-developers.com/galaxy-tab-2/help/p3100-16gb-bricked-emmc-bug-to-t3707134
If you have symptoms similar to mine or any mentioned in the links in the post, then it seems you have a faulty emmc (internal memory).
The only solution i get to hear up till now is either to get motherboard replaced from service center or get emmc replaced from repair shop or get it jtag'ed.
Other solutions, which would avoid jtag or other service, like dual booting from SD card existed here in xda for p3100 but having stuck in stock recovery brought limitations.
If possible share all things you tried and solution if you found any.

amarb said:
Seems like a similar issue like mine. Check my post about behavior of my tab 2 7" (P3100) at https://forum.xda-developers.com/galaxy-tab-2/help/p3100-16gb-bricked-emmc-bug-to-t3707134
If you have symptoms similar to mine or any mentioned in the links in the post, then it seems you have a faulty emmc (internal memory).
The only solution i get to hear up till now is either to get motherboard replaced from service center or get emmc replaced from repair shop or get it jtag'ed.
Other solutions, which would avoid jtag or other service, like dual booting from SD card existed here in xda for p3100 but having stuck in stock recovery brought limitations.
If possible share all things you tried and solution if you found any.
Click to expand...
Click to collapse
Tks for the answer, I guess we have the same problem, by the way, I already read your topic (lol), Surelly I'm gonna find some technical assistance , the hard thing is to find these kind of stuff, but let's see. I'm gonna share any solution, see ya!

If you install a custom recovery and then reboot to system, it will automatically install the stock recovery again unless you are rooted. To avoid this uncheck the "reboot system when finished" box in odin and after installing the recovery boot directly into it.
Stock recovery is only for installing official updates, not for custom roms. You need a custom recovery for that.

hello
cfautoroot
regards

john99ap said:
If you install a custom recovery and then reboot to system, it will automatically install the stock recovery again unless you are rooted. To avoid this uncheck the "reboot system when finished" box in odin and after installing the recovery boot directly into it.
Stock recovery is only for installing official updates, not for custom roms. You need a custom recovery for that.
Click to expand...
Click to collapse
Thanks, but we I tried this too. The issue is possibly our emmc is gone into permanant write protection state as far as i have studied. i tried unchecking the "reboot system when finished" box and even pulling battery after getting odin status as success for recovery as suggested in some threads but nothing helped.
Even if i do a factory reset from recovery all data would remain as is, nothing deleted!
@blankfile99 i agree its hard to find stuff, for me jtag service is more than 500kms from my place!
I am searching for any possibility to boot from external sd card. The thing existed for p3100 (one mentioned here https://forum.xda-developers.com/showthread.php?t=1866675 which allows sd boot) and the other is the blackhawk NEXT https://forum.xda-developers.com/showthread.php?t=2285366 but this is not suitable for our case where no modifications in emmc contents are possible. Devs were able to carry out sd boot for nook color tab .
But again I am stuck trying the dual boot mentioned above at how to flash the sd boot build rom zip file to sd card since stock recovery gives signature verification failure....
Great struggle to keep the tab working...

amarb said:
Thanks, but we I tried this too. ....But again I am stuck trying the dual boot mentioned above at how to flash the sd boot build rom zip file to sd card since stock recovery gives signature verification failure....
Great struggle to keep the tab working...
Click to expand...
Click to collapse
I had the same issue - here is what I did (I'm writing this as much for me later on, as for you!). This should be fine for your device - but of course, the usual "no guarantees" applies.....
I assume you have downloaded the appropriate files ?
- I used philz_touch_6.57.8-p5100.tar.md5 (google it)
- Odin3 v1.85
1) Install / Start Odin on computer
2) Start device in download mode For my P5100 - I held down power and the UP volume button.
3) Connect USB cable to computer. In ODIN, Click PDA and select the downloaded philz_touch_6.57.8-p5100.tar.md5 (or whatever you're going to use).
4) in ODIN - UNTICK "Auto- Reboot" and Re-Partition is unticked - leave Reset Time ticked.
5) Click start. you should get the "PASS" All threads completed.
6) Disconnect USB cable
7) - important bit - Press and hold down POWER and Volume DOWN together at same time for about 15 seconds. This hopefully will restart into PhilZ mod.
Let me know how it goes.

I have decided to install custom rom on my Samsung tab 2. but it's not connecting with my laptop(not recognized).I think there's a driver problem because in device manager It is showing "Unknown USB DEVICE". Can anyone please send me the Samsung tab 2 gt p5110 driver software or any folders which are use to connect. (I have tried many times but I can't find a good solution )

@Sura 102005
Have you tried reading and following this - also read the older threads
You may need to install Samsung kies
You should also try with a newer / different cable as that could be the issue. I had this same problem and when I swapped to newer cable it solved the issue. Just try different things.

clappertrap said:
@Sura 102005
Have you tried reading and following this - also read the older threads
You may need to install Samsung kies
You should also try with a newer / different cable as that could be the issue. I had this same problem and when I swapped to newer cable it solved the issue. Just try different things.
Click to expand...
Click to collapse
Hi clappertrap, Thank you for your kindness. I have tried Samsung Kies but I haven't tried a different cable I have order for OTG cable and USB male-male cable. I think this will work.