Develop Bugs

[q] So i think my Epic is screwed...

First and foremost, been a long time lurker here (first time poster) on XDA... and the community here is just outstanding.
So I've decided to root my epic, everything was great. I used the one click 2.5CWM root, and realized I wanted to try out another rom that wasn't compatible. Reflashed with the( ReRFS.Format.ROM.EC05 ) (since it kept me stuck on the samsung black screen) then went ahead and flashed the zip for CWM 3.0.0.6 with viperrom,...
Now here's where it gets interesting... I want to be able to revert back to a stock rom, and flash syndicate... but for some reason my CWM wont allow me to flash any .zip files from SD card. It says "failed to mount /sdcard". i formated it on my pc, it reads / writes fine, but anytime i boot into clockwork, it can't mount my sd card. I can still boot into my phone, it's still usable for daily usage, but it just doesn't look like what I like.
Now I've tried running Odin, but when im in the download mode, odin will not recognize my phone being plugged in. I've downloaded the proper drivers, for both my win7 x64 and 32 bit computers, tried every USB port etc... and it still wont work.
any idea on what I can do to get my CWM to work?

Use Odin with a non-stock cable.

I've tried it with 4 different data cables, 2 Samsung OEM, and 2 generics...

Have you tried a different PC, or Heimdall?
Make sure you're using Odin 1.61, the correct PIT, and the EC05 TAR.
http://k0nane.info/rom/odin-pit.zip
http://k0nane.info/rom/SPH-D700-EC05-8gb-REL.tar

Also there is a small amount of phones that did not want to Odin correctly unless the battery was out. You can try that too.

So I've tried to run Heimdall, and i'm still experiencing the same issue that I was having with Odin.
Every time I plug in my device via USB (samsung OEM data cable, only cable i have that will prompt that a device is connected) windows will pop up with a message, device not recognized (unknown device in device manager when in download mode) it seems to be fine and it'll recognize it correctly when I have the phone running (booted up into the rom)
I ran the zadig.exe for the drivers, and nothing seems to work.

Instead of Odin, try the SWUpdate for EB13, it is much less fickle
Place your phone in download mode (keyboard #1 and the power button) and see if it will connect/install
If It works, you can then move on to either upgrade to EC05 using the stock update zip, or install CWM and flash your FAV ROM

My comp doesn't seem to want to recognize the phone anymore... everything is "unknown device" now

Yeah get your hands on a blackberry cable. My guess it will help your cause. Make sure the drivers are installed on your pc as well.

im just going to reformat my netbook and do a fresh install on the drivers, too tires of the "guess work" i'll keep you guys posted on how that goes

SUCESS!
my epic is back to full stock via Heimdall. (took a little playing around to get)
@qbking77 - Thanks for the tip, I ended up using a 7" black berry data cable, and heimdall recognized it.
The only thing now though, all of the wires i have now, don't seem to let me use One Click Root CWM 3.0.2.5 I'll try it with my OEM samsung cable (that worked before) when i get home, I'll keep you guys posted.
Thanks again!

[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] i747 (AT&T) Galaxy S3. No Rom, No recovery. Odin not recognized by Win7. Screwed?

[Q] i747 (AT&T) Galaxy S3. No Rom, No recovery. Odin not recognized by Win7. Screwed?
THREAD CLOSED:Final update made
Solution: JTAG. I have updated the main page for anyone who comes across this in their troubles. Try the advice in this thread. It's good advice. I just couldn't be helped. These guys are smart as ****. Take their advice. Good luck, and good night.
Original post
Alright, I'll give as much info as possible. If anyone can save me from having a $250 paperweight, I would... Well, probably whatever they asked me to. Here it is in a nutshell. I was on AOKP with TWRP recovery. I jump ROMS everyday it seems, so why would today be any different? I boot into TWRP, make a backup, wipe cache, factory reset (data and cache), delvik cache, and then system (here was my mistake). Then I was going to install another ROM when I was suddenly needed by family. In my infinite genius I decided "Oh I'll just shut down without a ROM installed, that'll go well!" and shut the phone down through TWRP options (/facepalm).
Finally, I come back to it and decide "Ok, I'd like to install a ROM now". I boot it up (holding up, home, power), but accidentally let go of home and power instead of just power so it tries to boot. No prob, I just do it again. Now I hold it this time and the trusty "teamwin" splash comes up. But something isn't right. It restarts instead of giving me options. "ok...." I think, and I try it again. Same thing. F**k, I have no recovery... So I go to my last resort. Odin mode. I get into Odin Mode, grab my USB cable and plug in (to my computer with drivers already on it from the toolkit) and! TADA! USB not recognized. That's right. USB. NOT. RECOGNIZED.
Recap
So lets recap:
No ROM
No recovery
Drivers from Toolkit installed
Odin Mode = USB not Recognized in Windows
What I tried
Here is what I have tried (in no particular order)
New USB cable. 3 to be exact.
Different ports. All of them on all of the computers.
Different computers. 2 laptops, 2 desktop. All Win 7 64-bit.
Going into recovery (it bootloops)
Letting it boot. (Does nothing)
Uninstalling and reinstalling drivers
Installing Kies
Installing nothing
"adb devices" (doesn't show up)
Using toolkit (no devices seen)
Manually chosing every driver from "Samsung electronics LTD" that my computer has installed.
Plugging in before starting Odin
Plugging in after starting Odin.
Every combination of "Power cycle, Odin Mode, connect to computer" I can think of
Actually praying to Odin
Crying
Giving up
Gaining Second Wind
Searching Google, XDA and numerous forums extensively.
Making a new thread myself
I would really, REALLY appreciate it if someone, somewhere has ANY idea on how I can flash something ANYTHING to my phone again. Thank you SO much for your time. Honestly. I mean it, thank you. Let me buy you a beer. I'm serious.
Extra Info
Extra Information: The pop up is always the "USB not Recognized" balloon. Device manager comes up with an "Unknown Device" and yellow [!] triangle. Sometimes, under details, I'll see "Code 10: Device could not start". To reiterate, the phone WILL go into Odin Mode. Thanks again.
Conclusion:
Windows GS3Toolkit fails to see it
Windows Kies fails to see it
Windows 7 OS fails to recognize it
Windows adb fails to see it
Linux adb fails to see it
Mac OS X heimdall fails to see it
Mac OS X adb fails to see it
My conclusion: For some reason, my phone is reporting itself incorrectly, with a potentially damaged usb port on the phone.
Solution A: Try to JTAG myself. (NOT RECOMMENDED) Pros: Learning. Cons: Too much to buy and ugh. F that noise.
Solution B: (Chosen path) Send to someone to JTAG it for me. Pros: Fast, easy (for me) Cons: $60
Solution C: Sell the phone. Pros: Potentially less cost (through loss) Cons: Time to sell and buy, jockey for prices, potentially lose my ass.
Solution D: Do nothing. Pros: No more loss, no more work, maybe something will come through. Cons: bricked phone

Kilo__ said:
Alright, I'll give as much info as possible. If anyone can save me from having a $250 paperweight, I would... Well, probably whatever they asked me to. Here it is in a nutshell. I was on AOKP with TWRP recovery. I jump ROMS everyday it seems, so why would today be any different? I boot into TWRP, make a backup, wipe cache, factory reset (data and cache), delvik cache, and then system (here was my mistake). Then I was going to install another ROM when I was suddenly needed by family. In my infinite genius I decided "Oh I'll just shut down without a ROM installed, that'll go well!" and shut the phone down through TWRP options (/facepalm).
Finally, I come back to it and decide "Ok, I'd like to install a ROM now". I boot it up (holding up, home, power), but accidentally let go of home and power instead of just power so it tries to boot. No prob, I just do it again. Now I hold it this time and the trusty "teamwin" splash comes up. But something isn't right. It restarts instead of giving me options. "ok...." I think, and I try it again. Same thing. F**k, I have no recovery... So I go to my last resort. Odin mode. I get into Odin Mode, grab my USB cable and plug in (to my computer with drivers already on it from the toolkit) and! TADA! USB not recognized. That's right. USB. NOT. RECOGNIZED.
So lets recap:
No ROM
No recovery
Drivers from Toolkit installed
Odin Mode = USB not Recognized in Windows
Here is what I have tried (in no particular order)
New USB cable. 3 to be exact.
Different ports. All of them on all of the computers.
Different computers. 2 laptops, 1 desktop. All Win 7 64-bit.
Going into recovery (it bootloops)
Letting it boot. (Does nothing)
Uninstalling and reinstalling drivers
Installing Kies
Installing nothing
"adb devices" (doesn't show up)
Using toolkit (no devices seen)
Manually chosing every driver from "Samsung electronics LTD" that my computer has installed.
Plugging in before starting Odin
Plugging in after starting Odin.
Every combination of "Power cycle, Odin Mode, connect to computer" I can think of
Actually praying to Odin
Crying
Giving up
Gaining Second Wind
Searching Google, XDA and numerous forums extensively.
Making a new thread myself
I would really, REALLY appreciate it if someone, somewhere has ANY idea on how I can flash something ANYTHING to my phone again. Thank you SO much for your time. Honestly. I mean it, thank you. Let me buy you a beer. I'm serious.
Extra Information: The pop up is always the "USB not Recognized" balloon. Device manager comes up with an "Unknown Device" and yellow [!] triangle. Sometimes, under details, I'll see "Code 10: Device could not start". To reiterate, the phone WILL go into Odin Mode. Thanks again.
Click to expand...
Click to collapse
Uninstall Kies
Uninstall the Samsung USB Drivers
Run CCleaner
Reboot
Install The Samsung USB Drivers
Go into Download Mode
Open ODIN
Hook up, and see if drivers install and ODIN sees the phone

DirtyOldMan said:
Uninstall Kies
Uninstall the Samsung USB Drivers
Run CCleaner
Reboot
Install The Samsung USB Drivers
Go into Download Mode
Open ODIN
Hook up, and see if drivers install and ODIN sees the phone
Click to expand...
Click to collapse
Followed this to the letter. Didn't work. Thanks though! Can I send you money for a beer?

Kilo__ said:
Followed this to the letter. Didn't work. Thanks though! Can I send you money for a beer?
Click to expand...
Click to collapse
You could do some research into putting twrp on via adb.....or cwm depending on your preference..... if I remeber correctly you need to download the android sdk... I am sure it tells you on the trwp page though....... I know I have adb'd myself out of some tight spots with my transformer and also my old htc hero... haven't commited to changing the s3 yet though... concept is the same....
http://www.teamw.in/project/twrp2/104
Download - Recovery Image Method (using dd):
--------------------------------------------------------------------------------
Select the latest .img file from here
Download the above file. Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18
Make certain that you get this command right. Typing the wrong number could result in a brick!
After the SU on the PC i copy paste the command.....

Kilo__ said:
Followed this to the letter. Didn't work. Thanks though! Can I send you money for a beer?
Click to expand...
Click to collapse
It's cool man... If you want me to look at it, PM me, I can probably fix it...

Gage_Hero said:
You could do some research into putting twrp on via adb.....or cwm depending on your preference..... if I remeber correctly you need to download the android sdk... I am sure it tells you on the trwp page though....... I know I have adb'd myself out of some tight spots with my transformer and also my old htc hero... haven't commited to changing the s3 yet though... concept is the same....
http://www.teamw.in/project/twrp2/104
Download - Recovery Image Method (using dd):
--------------------------------------------------------------------------------
Select the latest .img file from here
Download the above file. Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18
Make certain that you get this command right. Typing the wrong number could result in a brick!
After the SU on the PC i copy paste the command.....
Click to expand...
Click to collapse
I'm not sure how this applies. I think this is a good solution except that I can't get it to connect to my computer at all. ADB, ODIN, nor Windows 7 will recognize the device in Odin Mode and I have no ROM or recovery installed, and I can't install anything without getting it to connect. I'll keep this in case I can get something to connect and Odin doesn't work, so thank you!
DirtyOldMan said:
It's cool man... If you want me to look at it, PM me, I can probably fix it...
Click to expand...
Click to collapse
I'll talk with you no doubt.

Kilo__ said:
I'm not sure how this applies. I think this is a good solution except that I can't get it to connect to my computer at all. ADB, ODIN, nor Windows 7 will recognize the device in Odin Mode and I have no ROM or recovery installed, and I can't install anything without getting it to connect. I'll keep this in case I can get something to connect and Odin doesn't work, so thank you!
I'll talk with you no doubt.
Click to expand...
Click to collapse
to you start a command prompt, open the directory where adb.exe is. Press and hold shift while right clicking in the window, select open command prompt here...... manytimes if you don't do this ... adb isn't going to work for you.....
Once you do this then type devices if you get your device showing up then you can install twrp or cwm.....
When the instructions say to enter a command, highlight it on the webpage and copy then in your command window right click and paste (control V does not work here)
If you use adb to install anything, that file MUST be in the same directory as the adb.exe

Gage_Hero said:
to you start a command prompt, open the directory where adb.exe is. Press and hold shift while right clicking in the window, select open command prompt here...... manytimes if you don't do this ... adb isn't going to work for you.....
Once you do this then type devices if you get your device showing up then you can install twrp or cwm.....
When the instructions say to enter a command, highlight it on the webpage and copy then in your command window right click and paste (control V does not work here)
If you use adb to install anything, that file MUST be in the same directory as the adb.exe
Click to expand...
Click to collapse
Well that's the thing. It does not show up in devices. ADB will not recognize the device. I'm fairly knowledgeable with using adb and I have 3 versions on my computer. None of the three (adb.exe adb-toolkit.exe or SOCadb.exe) will view 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"
}

Have you tried using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.

aybarrap1 said:
Have you tried using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.
Click to expand...
Click to collapse
No I haven't. I can try to do that too. And I have the cable that came with the phone (but I bought it used). I'll try it tomorrow at work

aybarrap1 said:
Have you tried using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.
Click to expand...
Click to collapse
Kilo__ said:
No I haven't. I can try to do that too. And I have the cable that came with the phone (but I bought it used). I'll try it tomorrow at work
Click to expand...
Click to collapse
Tried it. Unrecognized still. I think I may just be f***ed

Kilo__ said:
Tried it. Unrecognized still. I think I may just be f***ed
Click to expand...
Click to collapse
So when you get into recovery mode (or attempt to) it just reboots after a few seconds ?
You have the teamwin spleash screen and then it doesn't give you time to select any options ? There's really no harm in formating system because it will just boot into twrp without a recovery. You might have a borked recovery but it seems like more. Samsung cords are crap and like to die randomly so another cord is really worth a shot of course make sure it has data.
When you say odin mode I assume you mean download mode and odin just doesn't light up with a com port showing a device ?

hednik said:
So when you get into recovery mode (or attempt to) it just reboots after a few seconds ?
You have the teamwin spleash screen and then it doesn't give you time to select any options ? There's really no harm in formating system because it will just boot into twrp without a recovery. You might have a borked recovery but it seems like more. Samsung cords are crap and like to die randomly so another cord is really worth a shot of course make sure it has data.
When you say odin mode I assume you mean download mode and odin just doesn't light up with a com port showing a device ?
Click to expand...
Click to collapse
No, I don't get any options. "Teamwin" for about 30 seconds. Then black... 5 seconds. Then vibrate twice and then reboot. I think I wiped system, and then TWRP borked as you say. I have used many cords for this.
And yes, the phone goes into Odin mode, but the Odin program doesn't pick it up, neither will ADB and windows says "USB not recognized"

DirtyOldMan said:
Uninstall Kies
Uninstall the Samsung USB Drivers
Run CCleaner
Reboot
Install The Samsung USB Drivers
Go into Download Mode
Open ODIN
Hook up, and see if drivers install and ODIN sees the phone
Click to expand...
Click to collapse
Gage_Hero said:
You could do some research into putting twrp on via adb.....or cwm depending on your preference..... if I remeber correctly you need to download the android sdk... I am sure it tells you on the trwp page though....... I know I have adb'd myself out of some tight spots with my transformer and also my old htc hero... haven't commited to changing the s3 yet though... concept is the same....
http://www.teamw.in/project/twrp2/104
Download - Recovery Image Method (using dd):
--------------------------------------------------------------------------------
Select the latest .img file from here
Download the above file. Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18
Make certain that you get this command right. Typing the wrong number could result in a brick!
After the SU on the PC i copy paste the command.....
Click to expand...
Click to collapse
DirtyOldMan said:
It's cool man... If you want me to look at it, PM me, I can probably fix it...
Click to expand...
Click to collapse
Gage_Hero said:
to you start a command prompt, open the directory where adb.exe is. Press and hold shift while right clicking in the window, select open command prompt here...... manytimes if you don't do this ... adb isn't going to work for you.....
Once you do this then type devices if you get your device showing up then you can install twrp or cwm.....
When the instructions say to enter a command, highlight it on the webpage and copy then in your command window right click and paste (control V does not work here)
If you use adb to install anything, that file MUST be in the same directory as the adb.exe
Click to expand...
Click to collapse
aybarrap1 said:
Have you tried using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.
Click to expand...
Click to collapse
hednik said:
So when you get into recovery mode (or attempt to) it just reboots after a few seconds ?
You have the teamwin spleash screen and then it doesn't give you time to select any options ? There's really no harm in formating system because it will just boot into twrp without a recovery. You might have a borked recovery but it seems like more. Samsung cords are crap and like to die randomly so another cord is really worth a shot of course make sure it has data.
When you say odin mode I assume you mean download mode and odin just doesn't light up with a com port showing a device ?
Click to expand...
Click to collapse
I just wanted to say thank you all for the help on this situation. Nothing has turned up with the phone but I'm 99% sure this isn't a driver thing now. I'm gonna face the music and try to find either a Jtag kit somewhere or possibly someone to buy it from me. If anyone has any ideas on this and wants to weigh in, I'll of course attempt their solution, but I am going to try other solutions now. Once the device has been either sold or fixed, I will close this thread and edit my first thread with the solution for others to see. Again, each and every one of you, thank you. Hopefully, I can return the favor some day

Jtag is a little harsh at this point. That's typically reserved for devices that show absolutely zero signs of life.

mrhaley30705 said:
Jtag is a little harsh at this point. That's typically reserved for devices that show absolutely zero signs of life.
Click to expand...
Click to collapse
Yea, yea it is but I don't know what else to try. I've browsed forum after forum after forum. Of all the people that have received help this problem (Odin is the only choice and isn't recognized), a total of 0 have had something work for them and most threads die unsuccessful. I partially blame the OPs for their lack of through information and replies, but also to the fact that I believe this is just a case of Bad Luck Brian. To have me mess up with the ROM, TWRP take a nose dive, and ODIN play enigma all at the same time seems like a very unlucky scenario.
It has been 8 days now that I've had no phone. Now, I'm not an important person, but I'd at least like to have the phone number I'm paying for, be usable to me. I am really grateful for all of the help and I don't feel slighted or let down in any way, it's just plain and simple that I want a working phone back. If something comes up here before I remedy the situation myself, I'll be sure to let y'all know how it goes, but I'm at the point where I want a usable phone. Again, thank you all for help you have provided and the time you've put into my issue.

Do you have a friend/colleague that also had an s3? Try their computer if you do. They should have the proper drivers installed, so Odin should work. This is the last idea I have. Also, check your pm.

mrhaley30705 said:
Do you have a friend/colleague that also had an s3? Try their computer if you do. They should have the proper drivers installed, so Odin should work. This is the last idea I have. Also, check your pm.
Click to expand...
Click to collapse
Ah, yes. Actually, one of my posts (probably the main one) I bring up 2 laptops and 1 desktop being used, one of the laptops was his. He has an S3 (he's actually the one that pushed me towards getting one). It was the first one with this problem, as I was at his house when it all happened.

I saw that all of your attempted solutions were with a win 7 machine. Have you given using a Linux environment any thought? No drivers to worry about, and if adb will recognize it you can push a recovery, as mentioned earlier

mrhaley30705 said:
I saw that all of your attempted solutions were with a win 7 machine. Have you given using a Linux environment any thought? No drivers to worry about, and if adb will recognize it you can push a recovery, as mentioned earlier
Click to expand...
Click to collapse
I haven't. Is there an easy guide on how to do this or how to get adb on linux?

[Q] I Did the impossible! - Galaxy Nexus fully bricked

Hello everyone!
I have fully bricked my phone (at least, I am unable to repair it). So I hope there is someone who could help me restore my Galaxy Nexus to a working state again.
Story:
I wanted to flash a new custom ROM and a whole new clean phone. So I decided to wipe everything. I wiped all /sdcard, /system, /cache and /data with ClockWorkMod (recovery mode). Now it looks like I do not have any OS on the device at all and the device would not boot past the 'Google' logo and the 'unlocked' padlock symbol. Connecting the device to the computer is also not working (cannot recognize the device, even with the drivers installed manually). So my conclusion, I bricked my Galaxy Nexus.
Facts:
1) Wiped all /sdcard, /system, /cache and /data. So the phone is emptier than there is dirt in a hole that is 6 feet by 6 feet by 4 feet.
2) Cannot boot past the 'Google' logo and the 'unlocked' padlock, it gets stuck there
3) Rooted
4) Can get in Download (Odin) mode
5) Can get in Recovery (CWM) mode
6) Can get in Fastboot mode
7) None of the computers of laptops would recognize the device
8) Can not access the device or sdcard with a computer
Tried:
1) Universal Naked Driver
2) ADB push the files
3) Odin to restore to factory settings (Odin cannot see the device)
4) Send for repairs to Samsung (denied because of water damage , the device was working just fine before the wipe..)
5) Kies for the drivers
6) Galaxy Nexus ToolKit
None of the things I tried has worked.
I hope there is someone who could help me. I would buy that person a cup of coffee
Thanks in advance!

iKaosTony said:
Hello everyone!
I have fully bricked my phone (at least, I am unable to repair it). So I hope there is someone who could help me restore my Galaxy Nexus to a working state again.
Story:
I wanted to flash a new custom ROM and a whole new clean phone. So I decided to wipe everything. I wiped all /sdcard, /system, /cache and /data with ClockWorkMod (recovery mode). Now it looks like I do not have any OS on the device at all and the device would not boot past the 'Google' logo and the 'unlocked' padlock symbol. Connecting the device to the computer is also not working (cannot recognize the device, even with the drivers installed manually). So my conclusion, I bricked my Galaxy Nexus.
Facts:
1) Wiped all /sdcard, /system, /cache and /data. So the phone is emptier than there is dirt in a hole that is 6 feet by 6 feet by 4 feet.
2) Cannot boot past the 'Google' logo and the 'unlocked' padlock, it gets stuck there
3) Rooted
4) Can get in Download (Odin) mode
5) Can get in Recovery (CWM) mode
6) Can get in Fastboot mode
7) None of the computers of laptops would recognize the device
8) Can not access the device or sdcard with a computer
Tried:
1) Universal Naked Driver
2) ADB push the files
3) Odin to restore to factory settings (Odin cannot see the device)
4) Send for repairs to Samsung (denied because of water damage , the device was working just fine before the wipe..)
5) Kies for the drivers
6) Galaxy Nexus ToolKit
None of the things I tried has worked.
I hope there is someone who could help me. I would buy that person a cup of coffee
Thanks in advance!
Click to expand...
Click to collapse
From what I can see in your explanation, it won't boot up because you wiped your old rom (system) and did not flash a new one before you tried to boot up. If you can boot into recovery you are not bricked. Perhaps you still have a downloaded rom on there. Full wipe (at least with TWRP) Doesn't usually wipe that partition nor your Nandroids. So you should be able to flash a rom or a restore from recovery. If that fails, get Wugs Tool kit and carefully follow the instructions, especially about driver installation. After that, Wugs should see your Nex in adb and fastboot and you can put rom on from there.
Odin useless on Gnex & Kies is dicey at best.
Sent from my Hyperdriven Vzw Dev Edition Galaxy S4 with Tapatalk 4

supposing that there is no issue with driver
hmmmm water damage?
did you try to clean micro usb port from rust or dust, or see if there is a pin needs bending?

wtherrell said:
From what I can see in your explanation, it won't boot up because you wiped your old rom (system) and did not flash a new one before you tried to boot up. If you can boot into recovery you are not bricked. Perhaps you still have a downloaded rom on there. Full wipe (at least with TWRP) Doesn't usually wipe that partition nor your Nandroids. So you should be able to flash a rom or a restore from recovery. If that fails, get Wugs Tool kit and carefully follow the instructions, especially about driver installation. After that, Wugs should see your Nex in adb and fastboot and you can put rom on from there.
Odin useless on Gnex & Kies is dicey at best.
Sent from my Hyperdriven Vzw Dev Edition Galaxy S4 with Tapatalk 4
Click to expand...
Click to collapse
no... just no.
dont ever recommend a toolkit.
OP,
your problem is the phone isnt bricked. you just do not have a system for the phone to boot into. if it was bricked it would not turn on and you could not get into fastboot.
you need to fix your drivers.
follow this: http://forum.xda-developers.com/showthread.php?t=1626895
it has steps for drivers, etc.

wtherrell said:
From what I can see in your explanation, it won't boot up because you wiped your old rom (system) and did not flash a new one before you tried to boot up. If you can boot into recovery you are not bricked. Perhaps you still have a downloaded rom on there. Full wipe (at least with TWRP) Doesn't usually wipe that partition nor your Nandroids. So you should be able to flash a rom or a restore from recovery. If that fails, get Wugs Tool kit and carefully follow the instructions, especially about driver installation. After that, Wugs should see your Nex in adb and fastboot and you can put rom on from there.
Odin useless on Gnex & Kies is dicey at best.
Sent from my Hyperdriven Vzw Dev Edition Galaxy S4 with Tapatalk 4
Click to expand...
Click to collapse
Thank you for your fast reply.
That is about right. When I go in CWM and try 'install zip' -> 'choose zip from sdcard', I get 2 folders. The first one is called '0/' and the other is called 'clockworkmod/' both of them are empty. So I guess there are no files on my device anymore.
I will try Wugs Toolkit. I will keep you updated.

samersh72 said:
supposing that there is no issue with driver
hmmmm water damage?
did you try to clean micro usb port from rust or dust, or see if there is a pin needs bending?
Click to expand...
Click to collapse
Yeah, really strange. I have never dropped it in water or let it get in contact with water.
But because of that reason they will not accept it for repairs and I have to deal with it myself.
I have checked the port for dust and pins for bending, nothing wrong with them.
Zepius said:
no... just no.
dont ever recommend a toolkit.
OP,
your problem is the phone isnt bricked. you just do not have a system for the phone to boot into. if it was bricked it would not turn on and you could not get into fastboot.
you need to fix your drivers.
follow this: http://forum.xda-developers.com/showthread.php?t=1626895
it has steps for drivers, etc.
Click to expand...
Click to collapse
I just tried Wugs Toolkit without success.
{
"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"
}
I just tried the Universal Naked Driver guide from bourne-nolonger here http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
But I cannot get the window that says 'Windows can't verify the publisher of this driver software' with the button 'Install this driver software anyway'. That is step 3E and 3F. It just skips that and say Unknown Device.
Could it be my USB port being broken? That the reason no computer would recognize it because of that?

iKaosTony said:
Yeah, really strange. I have never dropped it in water or let it get in contact with water.
But because of that reason they will not accept it for repairs and I have to deal with it myself.
I have checked the port for dust and pins for bending, nothing wrong with them.
I just tried Wugs Toolkit without success.
I just tried the Universal Naked Driver guide from bourne-nolonger here http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
But I cannot get the window that says 'Windows can't verify the publisher of this driver software' with the button 'Install this driver software anyway'. That is step 3E and 3F. It just skips that and say Unknown Device.
Could it be my USB port being broken? That the reason no computer would recognize it because of that?
Click to expand...
Click to collapse
You would have been in a very bad luck if your usb port died spontaneously at the same time you fully wiped your device....
Did you check another cable, often is the easiest solution which is overseen...

19Max87 said:
You would have been in a very bad luck if your usb port died spontaneously at the same time you fully wiped your device....
Did you check another cable, often is the easiest solution which is overseen...
Click to expand...
Click to collapse
I did tried using other cables, 2 from other Samsung devices, 1 cheap one and a cable from another Galaxy Nexus.
So I tried it on a computer with all the drivers working from another Galaxy Nexus.
Maybe bring it to a repairstore?

iKaosTony said:
I did tried using other cables, 2 from other Samsung devices, 1 cheap one and a cable from another Galaxy Nexus.
So I tried it on a computer with all the drivers working from another Galaxy Nexus.
Maybe bring it to a repairstore?
Click to expand...
Click to collapse
OK, you installed all the drivers, but did you delete every driver before you installed the new one.
I would try to delete every nexus driver from your computer and start from the very beginning. As the others said, your phone is not bricked and sometimes the drivers just want to fùck brains....
I'm sure you will find the solution, wish you the best of luck... :thumbup:

19Max87 said:
OK, you installed all the drivers, but did you delete every driver before you installed the new one.
I would try to delete every nexus driver from your computer and start from the very beginning. As the others said, your phone is not bricked and sometimes the drivers just want to fùck brains....
I'm sure you will find the solution, wish you the best of luck... :thumbup:
Click to expand...
Click to collapse
Yes, I have tried deleting and uninstalling every driver or software related to my device or any mobile device. Also I used this to make sure I have got rid of everything

iKaosTony said:
Yes, I have tried deleting and uninstalling every driver or software related to my device or any mobile device. Also I used this to make sure I have got rid of everything
Click to expand...
Click to collapse
Sorry bro, I'm out of ideas... :banghead:

Boot into an Ubuntu live USB. It doesn't require drivers. Just install the adb and fastboot tools from apt-get. There are about 50,000 tutorials on how.
Sent from my Galaxy Nexus

Try an other cable or computer or USB port.. Go to a friend if you must.. Then flash the Factory image via fastboot..
Sent from my Galaxy Nexus using XDA Premium HD app

I have tried using Ubuntu to access my device, but no luck either. When I come to the step where I have to use the command 'lsusb' does not show up. I have tried putting my device in Download mode, Fastboot mode and Recovery mode to see if 'lsusb' will show my device.
The tutorials I followed:
http://rootzwiki.com/topic/20770-gu...-adb-and-fastboot-in-linux-ubuntu-and-mint12/
http://www.youtube.com/watch?v=3heTSqjWcaY
http://bernaerts.dyndns.org/linux/245-ubuntu-precise-install-android-sdk
Tried 4 different cables, 3 different computers and a friends computer where all the drivers are working with his Galaxy Nexus.
I do not know what I am doing wrong. :crying:

in recovery mode execute "adb push rom.zip /sdcard/", better from Ubuntu so you don't need any driver
Then flash the rom from the recovery
Inviato dal mio Galaxy Nexus con Tapatalk 2

If neither lsusb shows the device connected nor there's any event under kernel logs that point to the device.. Is the USB port really working?
Sent from my maguro

do you have cwm or twrp? try mounting your device as usb while connected to pc
Sent from my Galaxy Nexus using xda app-developers app

beekay201 said:
If neither lsusb shows the device connected nor there's any event under kernel logs that point to the device.. Is the USB port really working?
Sent from my maguro
Click to expand...
Click to collapse
I am also thinking my USB port is broken...
unmystic said:
do you have cwm or twrp? try mounting your device as usb while connected to pc
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I have CWM. How do I do that?

In Device Manager can you right-click Unknown Device to view its properties?
You should be able to update the device driver there.

stevemw said:
In Device Manager can you right-click Unknown Device to view its properties?
You should be able to update the device driver there.
Click to expand...
Click to collapse
I tried that too, but no luck.

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/).