Develop Bugs

USB brick and adb not working

I tried to flash CM7 RC2 onto my phone last night. I usually do this manually, but last night I did it through Rom Manager which I think was probably my first mistake.
Anyway, the package flashed fine but after a reboot my SIM and SD card were no longer recognised. So I went into recovery (Amonra) and wiped ready to flash the update manually only to find my SD card wasn't recognised: E:Can't mount /dev/block/mmcblk01p (No such file or directory). So, left with a phone with no ROM.
I can still get into recovery and bootloader but that's it. I've seen a few posts on here with regards to USB bricks, but my phone is no longer recognised by adb. However, I haven't accessed the phone via adb for some time now, so not sure of the reason I can't connect is my PC setup or the phone. I've got the HTC Bootloader device appearing when I plug it in via USB though.
Can anyone advise on anything I can do to sort this?
Thanks

Might be a driver issue when your in recovery. Re-install the drivers for the device using Device Manager and point windows to the driver directory within the SDK folder.

Can I Access my external SD card through CWM?

A quick question, looked around a bit, couldn't find a similar one.
When I had my Samsung EPIC 4g, the version of CWM I was using allowed me to access my SD card by selecting "Mount USB Storage". However, I dont find this option in the current version of CWM I am using for my galaxy s3. Is this feature not available yet, or is it listed under a different section/name?
Also, whenever I have my phone plugged into my PC while I am in clockwork mod, my PC always alerts me that the proper drivers arent installed. However, I know this isn't true because when my phone is on I can use odin and my PC recognizes the device. Anyone have any idea whats causing this?
Thanks

We don't have the option to mount in recovery yet. Don't believe any version of cwm supports it. And for the drivers find ur phone in the device manager while ur in recovery and hit update driver. Manually install an adb driver for it. As far as the PC goes ur device in recovery and download mode are 2 different devices. It just doesn't know how to identify it when its in recovery. If you install it as an adb interface you can push/pull stuff to it if u need to

if you use an older version of CWM, like 5847...you can, but for some reason in 5849 it stopped....

Naddict said:
if you use an older version of CWM, like 5847...you can, but for some reason in 5849 it stopped....
Click to expand...
Click to collapse
Didn't know that.thought I'd tried them all. Guess I missed one. I'll have to revert later n try the older one.

[Q] Mouting in TWRP 2.2.2.0 Recovery/Computer won't recognize the phone

Hey guys,
I'm having some issues with mounting while I'm in the recovery. In fact, the computer (win7) won't even recognize that the phone is connected via USB. The device manager just shows "SAMSUNG_Android_SPH-L710" with a yellow exclamation mark. Whenever I connect the phone in recovery to the computer, it tells me driver installation was unsuccessful. I searched around before posting and made sure of few things.
1. Using the Samsung USB Cable.
2. Installing the Sprint_L710_GSIII_Samsung_USB_Driver_v1_4_6_0.exe found on Samsung's website.
3. I reinstalled the driver after it didn't work the first time.
I did read that I need adb drivers to get my computer to recognize my phone while in recovery mode. Is that true? If so, can someone please provide me the link to those drivers. I googled it but want to make sure I install the right version and don't end up bricking it.
Is anything else can be the issue here? Also, is mounting in recovery supported in latest CWM/TWRP?
I'm stock rooted with the LI3 update and trying to wipe everything clean before trying out Paranoid Android ROM. I haven't wiped anything yet since I want to make sure after I wipe my external/internal SD Card, I can place ROM files in the storage. Please let me know and any help is appreciated.
Thanks!

Not sure why you are trying to access your computer from recovery mode.

MobDad said:
Not sure why you are trying to access your computer from recovery mode.
Click to expand...
Click to collapse
1) Because a lot of root instructions tell you to
2) Because it's really annoying to reboot the phone, load a file, reboot to recovery and flash
I root devices part time and use that feature pretty often
Sent from my Jelly Bombed SGS3
---------- Post added at 03:12 AM ---------- Previous post was at 03:06 AM ----------
It is hit or miss and I don't know why. Sometimes it mounts for me, sometimes it doesn't.
Save yourself a ton of time and heart ache. You shouldn't lose and internal or external memory when you flash a rom on the SGS3. When you wipe, it only wipes your system and data which is on a separate system storage. I have read some people report a flash wiped their internal storage, but certainly not the external.
Btw.. Are you selecting "mount usb storage"?
Sent from my Jelly Bombed SGS3

Thanks guys for replying. So I finally got it working. After the first reinstall of the drivers, it still wasn't working. I was getting frustrated so I was like let me reinstall one more time. Give it a one more try. This time, I have no idea what changed but it started mounting. It still shows up in device manager with yellow exclamation mark. However, when I click Mount USB Storage in TWRP, it mounts. It does seem random in a sense that it works sometimes and doesn't other times.

wolfpack15 said:
Hey guys,
I'm having some issues with mounting while I'm in the recovery. In fact, the computer (win7) won't even recognize that the phone is connected via USB. The device manager just shows "SAMSUNG_Android_SPH-L710" with a yellow exclamation mark. Whenever I connect the phone in recovery to the computer, it tells me driver installation was unsuccessful. I searched around before posting and made sure of few things.
1. Using the Samsung USB Cable.
2. Installing the Sprint_L710_GSIII_Samsung_USB_Driver_v1_4_6_0.exe found on Samsung's website.
3. I reinstalled the driver after it didn't work the first time.
I did read that I need adb drivers to get my computer to recognize my phone while in recovery mode. Is that true? If so, can someone please provide me the link to those drivers. I googled it but want to make sure I install the right version and don't end up bricking it.
Is anything else can be the issue here? Also, is mounting in recovery supported in latest CWM/TWRP?
I'm stock rooted with the LI3 update and trying to wipe everything clean before trying out Paranoid Android ROM. I haven't wiped anything yet since I want to make sure after I wipe my external/internal SD Card, I can place ROM files in the storage. Please let me know and any help is appreciated.
Thanks!
Click to expand...
Click to collapse
I have the same problem. I need a driver for device manager while in twrrp.

[Q] Issue with installing mod/adb/SDcard/drivers

Hi folks,
I previously managed to get Cyanagenmod installed on my HTC One X but since made a mess of it trying to get a stock ROM on there (to unlock my SIM). I have since given up on getting a stock ROM back on there and am now trying to get Cyanogenmod back on there, but I have hit some problems.
I have CWM on there and my PC can see the phone in Fastboot, but not via ADB (which I am trying to use to 'push' the ROM on there so I can install it). My PC (Win 8.1) is giving me a "device descriptor request failed" when connecting to USB when on the boot menu, and is showing up just as "One" in device manager when I load CWM. However neither of these situations are allowing my computer or ADB to recognise the SD card.
I have tried 'mounting' it in CWM, updating drivers through device manager, installing Sync (and uninstalling/reinstalling it), installing HTCDriver_4.10.0.001.msi all to no avail.
Does anyone have any advice to get my PC to recognise my phone or otherwise get a customer ROM installed (if there is another way.)
Thanks in advance all.

Bglamb said:
Hi folks,
I previously managed to get Cyanagenmod installed on my HTC One X but since made a mess of it trying to get a stock ROM on there (to unlock my SIM). I have since given up on getting a stock ROM back on there and am now trying to get Cyanogenmod back on there, but I have hit some problems.
I have CWM on there and my PC can see the phone in Fastboot, but not via ADB (which I am trying to use to 'push' the ROM on there so I can install it). My PC (Win 8.1) is giving me a "device descriptor request failed" when connecting to USB when on the boot menu, and is showing up just as "One" in device manager when I load CWM. However neither of these situations are allowing my computer or ADB to recognise the SD card.
I have tried 'mounting' it in CWM, updating drivers through device manager, installing Sync (and uninstalling/reinstalling it), installing HTCDriver_4.10.0.001.msi all to no avail.
Does anyone have any advice to get my PC to recognise my phone or otherwise get a customer ROM installed (if there is another way.)
Thanks in advance all.
Click to expand...
Click to collapse
Flash Philz 5.15.9 recovery use it to mount sd card then to copy the rom you need then flash recovery for your rom for CM12 is one for CM11 is other and for Sense is third. For sense rom you can use Philz 5.15.9. And for the new layout is fourt recovery

Thanks!
I couldn't find it so I downloaded a newer version, but it didn't work, so I looked for longer and found a version, but that wouldn't even boot. In the end I used openrecovery-twrp-2.1.7, which did let me mount the SD and install the ROM.
Then I got stuck on the loading screen, but I discovered I needed to just flash a boot.img (which wasn't in either of the guides I was following, for some reason?!) and now I'm all up and running.
Thank you kind sir!

How to get T-Mob S3 off (third) Samsung splash screen to access data

Can anyone please assist to get data off an S3 which sticks at the blue-backed throbbing SAMSUNG splash screen just after the android rocket take-off.
The history is that the phone started constant-rebooting and I left it off for a few weeks. Then I took it into a shop to get the power switch replaced and the repairer noticed that it no longer reboots, it just sticks at that SAMSUNG screen. When neither of us could get it into safe mode, he diagnosed that it was "definitely" a software problem. Resetting caches from recovery mode doesn't do anything and as I am trying to get data off it, I am a bit reluctant to follow other solutions I have found here and do a master reset!
I THINK this device is rooted (with towelroot)? See below
I can get to an Odin screen and can get the device recognised on the computer and wondered if I could do resets from there with one of the 4 files included with 3.07. Curiously enough one of them did succeed (though the success was too quick to convince me it had actually flashed very much) and the device did reboot but still got stuck at the same splash screen! Taking the battery out and restarting/cleaning caches again etc didn't help and now, none of the Odin files will 'flash' successfully, which is why I am not sure if I am still rooted or if something is returned to stock. I am just not sure which file or what exactly flashed successfully and what it did to the ROM, bootloader, CID, etc etc etc. SO I am assuming that if I can still load Odin and get the S3 recognised, it is still rooted.
Is there anything else I can try either through odin or independently to get me into the os please? I have loaded skipsoft and run it and it has connected to the S3 (and changed things) just by connecting to the computer in download mode: But I can't see where in skipsoft I can diagnose or correct whatever is wrong

Flash TWRP via Odin, boot into TWRP, mount data partition, connect the phone to a computer, and try to copy the phone's data to the computer.

What that guy said ^^^ Install a new OS for your system which should replace your old one. You don't need to boot TWRP if you are going to boot a new OS. My method involves you losing all your data so you have been warned. You can get the stable version for that here http://techbeasts.com/update-t-mobi...o-android-4-3-jelly-bean-t999uvuemjc-guide/2/. Good luck

Thanks for that guys but I have apparently already loaded Philz and it SAYS it has backed up the data and/or storage to sc card and I am wondering if Ican restore it to a new Galaxy J7. I especially need to figure out if I can restore telephone text messages from the S3 onto the J7 but i could make do for the moment with knowing whether such messages have made their way onto the SD card.
Yes, I am a bit reluctant to do a full wipe and restore until I can figure this out.
Or if I can access the files through my computer as you suggest, what file / format would they be in?

If you used Philz to create a backup, I don't think you'll be able to restore the data to the J7, but I could be wrong because Philz hasnt been updated for a long time which means there may be no Philz for the J7.
Philz can only be restored with Philz and possibly cwm.

I got Philz installed through Skipsoft but am wondering whether there is any newer utility I can install over whatever Skipsoft has put there? Or is that what TWRP is?
I am a bit reluctant to install anything through TWRP if it is going to not only overwrite the OS but also delete all the data I am trying to access! But is there any utility which might conceivably get my phone working again without deleting all my data please?
If I load T999UVUEMJC_T999TMBEMJC_TMB,md5 through Odin, will it delete all my data??

Flashing twrp should not over write the rom, only the recovery.
Was the phone recognized as a removable when it was booted into philz?

audit13 said:
Flashing twrp should not over write the rom, only the recovery.
Was the phone recognized as a removable when it was booted into philz?
Click to expand...
Click to collapse
Why did you ask me that? 'cos I was pretty sure it was recognised but checked again and it isn't recognised by the computer at all when I plug it in (and obviously isn't recognised by Odin)
Philz shows as Touch 6.26.6 and ClockworkMod v 6.0.4.8

Why would I ask? Because twrp can mount the phone as a removable drive to copy off the data as you wanted to do in your original post.

audit13 said:
Why would I ask? Because twrp can mount the phone as a removable drive to copy off the data as you wanted to do in your original post.
Click to expand...
Click to collapse
Sorry to harp but are we agreed generally that there is no way of getting this phone working again, - whether with some utility or by re-flashing the stock or some new ROM?
Once the phone starts hanging at that third throbbing SAMSUNG screen, is it effectively dead save only for the purposes of getting data off it as a media device please? I really need to access my text messages and couldn't even identify them on a file directory and wouldn't know what format they were in if I could access the file browser. That was sorta a last resort but I am now downloading T999UVUEMJC_T999TMBEMJC_TMB for installation through Odin? Or for installation through Philz if I can get the file onto the SD card.

Did you try twrp and use a otg usb?
It really depends on how much your time is worth.

audit13 said:
Did you try twrp and use a otg usb?
It really depends on how much your time is worth.
Click to expand...
Click to collapse
I will keep retrying to see if it is something I am doing wrong but whereas Skipsoft installed easily, i dont seem to be able to install twrp on this nonbooting pda?

If the phone is not recognised by the computer, either the drivers are not working properly, the USB port is damaged, or the USB cable is not compatible with Odin.
Until the phone is recognised in Odin, you can't flash a stock rom from sammobile.com.

audit13 said:
If the phone is not recognised by the computer, either the drivers are not working properly, the USB port is damaged, or the USB cable is not compatible with Odin.
Click to expand...
Click to collapse
I am not exactly a newbie at this but I am beginning to wonder if I havent just got a developing massive hardware failure. I have tried a number of computers, including ones which formerly recognised the computer/cable/S3 setup and none can now recognise the phone, eg in Odin.
The phone is detected on plugin to Windows 10 (with the recognition beep) and is then not seen in windows explorer. Changing cables doesn't do anything. I am assuming it should automatically appear on the drop-down menu in TWRP's app in the playstore. That menu only shows a phone I plugged into the system about 6 months ago (without it being rooted) and asks for root permissions on this now-nonexistent phone.
The phone is not now recognised as it was up till only a few days ago in XP. Nothing is now recognised on a Mac, though on all three units the phone charges.
Restarting in download mode a few times changes nothing.
audit13 said:
.Until the phone is recognised in Odin, you can't flash a stock rom from sammobile.com.
Click to expand...
Click to collapse
The only other thing I can think of is putting some TWRP file (?) on an SD card, booting into recover/Philz and can i not install TWRP or reflash some ROM from there?

I'm not sure if twrp can be flashed from Philz as I have always flashed TWRP via Odin.
You have done everything I would have done to get the phone recognized short of a installing a fresh installation of a Windows OS.
You could also try Heimdall (http://glassechidna.com.au/heimdall/).