Develop Bugs

E:/ Can't mount /emmc - Possible Brick?

Well...long story short, I flashed ICS but I got locked out so I had to Nandroid back to my original ROM, but some error happened and now my phone won't turn on and I can't access my internal SD card. Using Rogue Recovery, when I try to Restore, my internal SD card isn't detected and I get E:/ Can't mount /emmc. Any way to fix this? Or am I bricked? Please help ASAP

I think my entire internal SD has been fried... If anyone has information, please tell me ASAP

I would start by seeing if you can get into download mode. Sorry if you've already tried this. Otherwise, pull the battery for 10 secs and then hold the volume down button and power key until your screen enters download mode. If that works, you can then Odin back to whatever you want.

I got into Odin, but I'm not really sure what to do with it. I'm not experienced with Odin. Should I push a Kernel? a ROM? My phone won't turn on regularly so a ROM would be pointless

Read along with this http://forum.xda-developers.com/showthread.php?t=1274337
If I tried to explain it, I'd for sure leave something out and you'd really be bricked. It sounds like you're phone is fine. It sounds like you just need to download a stock ROM .tar and flash it via Odin, then re-root, etc. Good luck.

Thanks. I pushed a kernel through but I'm hesitant to take the step for flashing a whole ROM. Also, by stock, do you mean a stock rooted ROM or a blank stock ROM?

in recovery, try to mount the SD card and connect it to your computer. See if it shows up in the computer and if your files are there and you can access it.

If you follow the steps in that guide, you'll be fine. I've done it a bunch of times. I keep a couple of stock ROM .tars on my laptop in case I screw something up while flashing. If I can do it, anyone can.

s9amme said:
in recovery, try to mount the SD card and connect it to your computer. See if it shows up in the computer and if your files are there and you can access it.
Click to expand...
Click to collapse
It won't let me. I think my internal memory is fried. But if I can get my phone working again, I don't care about the internal memoru

I'm on my way to bed. But, I can tell you that some of the vets around here have said time after time that if you're able to get into download mode, chances are your phone will be fine if you know how to Odin back to stock. Good luck to you.

iniz94 said:
It won't let me. I think my internal memory is fried. But if I can get my phone working again, I don't care about the internal memoru
Click to expand...
Click to collapse
It's fine. Mine was doing the same thing with Blazer ICS.
Basically, the way ICS handles USB mount is absurd. Makes no sense.
You have to flash clockworkmod touch from a zip file.
Just follow Phantoms steps exactly, only what's in bold:
To recover recovery:
Thru Odin:
Boot into Download Mode
Open ODIN
Download and Put this in PDA http://forum.xda-developers.com/showthread.php?t=1390393
Flash
Thru Recovery:
Temp CWM How-To (Thanks to overstew for the concept)
1. Download CWM Touch 5.8.1.5 for Epic 4G Touch
http://clockworkmod.com/rommanager
2. Reboot into Stock Recovery
3. "apply update from external storage"
4. Find CWM T ouch 5.8.1.5 zip file and flash it
5. Using Touch Recovery flash ICS-4-ICS v1.0 (FOR THE ICS THEME ONLY)
6. Reboot and enjoy.

Thank you very much, rde. I'm currently flashing sfhub's factory reset from Odin (http://forum.xda-developers.com/showthread.php?t=1383678)
I pray that my phone is okay, lol.

VoX_XDA said:
It's fine. Mine was doing the same thing with Blazer ICS.
Basically, the way ICS handles USB mount is absurd. Makes no sense.
You have to flash clockworkmod touch from a zip file.
Just follow Phantoms steps exactly, only what's in bold:
To recover recovery:
Thru Odin:
Boot into Download Mode
Open ODIN
Download and Put this in PDA http://forum.xda-developers.com/showthread.php?t=1390393
Flash
Thru Recovery:
Temp CWM How-To (Thanks to overstew for the concept)
1. Download CWM Touch 5.8.1.5 for Epic 4G Touch
http://clockworkmod.com/rommanager
2. Reboot into Stock Recovery
3. "apply update from external storage"
4. Find CWM T ouch 5.8.1.5 zip file and flash it
5. Using Touch Recovery flash ICS-4-ICS v1.0 (FOR THE ICS THEME ONLY)
6. Reboot and enjoy.
Click to expand...
Click to collapse
I've done that already but my phone was still acting up so I flashed Rogue Stock Kernel thru Odin and now I'm flashing a factory reset tar.

Awesome. glad you got it figured out.

Stuck at data.img
Gonna have to follow this
http://forum.xda-developers.com/showthread.php?t=1504808

rde34 said:
I'm on my way to bed. But, I can tell you that some of the vets around here have said time after time that if you're able to get into download mode, chances are your phone will be fine if you know how to Odin back to stock. Good luck to you.
Click to expand...
Click to collapse
We've actually found 2 cases where this isn't true:
1) if you flash the intl ICS release (which includes the intl bootloader) This seems to disable the USB port even though you can boot into ODIN D/L mode
2) some process people were doing early on when the FB02 release first came out (not saying it is the FB09 release causing issues, just some unidentified process people were doing at that time) seems to hoars the /data partition and even ODIN repartition doesn't help. I don't want to point fingers but there seemed to be pattern of CWM Touch being involved doing restores, but that was not scientifically proven.

I've learned that no matter what happens, this file will always fill the cracks in mah heart.
SPH-D710.EL29_CL852097_ROOTED-OneClick
afterwards I can begin anew

VoX_XDA said:
I've learned that no matter what happens, this file will always fill the cracks in mah heart.
SPH-D710.EL29_CL852097_ROOTED-OneClick
afterwards I can begin anew
Click to expand...
Click to collapse
Tried that... stuck at data.img like 10 other ppl. I hope there's a fix soon :/ Only just got this phone.

iniz94 said:
Tried that... stuck at data.img like 10 other ppl. I hope there's a fix soon :/ Only just got this phone.
Click to expand...
Click to collapse
If you just got the phone and can get it replaced, I would just do that.

sfhub said:
If you just got the phone and can get it replaced, I would just do that.
Click to expand...
Click to collapse
Got it around a month ago and didn't get insurance... is it possible to suddenly add insurance and go next week to get it replaced? Or do I need to bring the phone in?

SPH-L710 Bricked!

So, I was attempting to flash the CWM 6 recovery (IMG) from the CWM site. I definitely grabbed the Sprint file. However, I couldn't find very much info on how to flash IMG files. I found 3 posts all saying to use Terminal Emulator on the phone with some command line entries. I followed these exactly. After this, the phone will not boot and I cannot get into download mode. In Device Manager I get QHSUSB_DLOAD, which I believe is code for hard bricked and needs JTAG.
I have a RIFF BOX, but since I just got this phone a week ago, I don't really want to solder to it (though I could). I don't see on Multi-COM where there is a JTAG JIG for this phone. Does anyone have any other sources for such adapters? Or should I just take it to the store (Best Buy) and play dumb?
Is there a way to load a driver for QHSUSB_DLOAD and use that interface to flash or is that just a dummy device placeholder with no functionality?

muzicman82 said:
So, I was attempting to flash the CWM 6 recovery (IMG) from the CWM site. I definitely grabbed the Sprint file. However, I couldn't find very much info on how to flash IMG files. I found 3 posts all saying to use Terminal Emulator on the phone with some command line entries. I followed these exactly. After this, the phone will not boot and I cannot get into download mode. In Device Manager I get QHSUSB_DLOAD, which I believe is code for hard bricked and needs JTAG.
I have a RIFF BOX, but since I just got this phone a week ago, I don't really want to solder to it (though I could). I don't see on Multi-COM where there is a JTAG JIG for this phone. Does anyone have any other sources for such adapters? Or should I just take it to the store (Best Buy) and play dumb?
Is there a way to load a driver for QHSUSB_DLOAD and use that interface to flash or is that just a dummy device placeholder with no functionality?
Click to expand...
Click to collapse
I don't get what you where doing? Why not flash the recovery in Odin as this has to be the easiest phone in the world to root. Cwm should 5 something. Something....
Transmitted with a portable device using Xparent Blue Tapatalk 2

You're hard bricked. You can try playing dumb at best buy and if that doesn't work it looks like your only other option would be http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/. The Android Development section has fantastic tutorials on how to install recoveries so start you're search there next time.

edfunkycold said:
I don't get what you where doing? Why not flash the recovery in Odin as this has to be the easiest phone in the world to root. Cwm should 5 something. Something....
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
The CWM from here came as an IMG file, which ODIN apparently doesn't support. I didn't try it, but that is what I read. I found multiple posts even for the GSIII that said to use Terminal and the commands: "su", then "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18".
I was already rooted and on CM10.1, but with CWM 5.xxx. Wanted to move to CWM6/Touch.

muzicman82 said:
The CWM from here came as an IMG file, which ODIN apparently doesn't support. I didn't try it, but that is what I read. I found multiple posts even for the GSIII that said to use Terminal and the commands: "su", then "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18".
I was already rooted and on CM10.1, but with CWM 5.xxx. Wanted to move to CWM6/Touch.
Click to expand...
Click to collapse
Rom Manager from the Play Store would install Cwm touch one easy step. Sorry you have to go through this. Good luck I would go with the play dumb technique.
Transmitted with a portable device using Xparent Blue Tapatalk 2

edfunkycold said:
I don't get what you where doing? Why not flash the recovery in Odin as this has to be the easiest phone in the world to root. Cwm should 5 something. Something....
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
edfunkycold said:
Rom Manager from the Play Store would install Cwm touch one easy step. Sorry you have to go through this. Good luck I would go with the play dumb technique.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
When I get this fixed, I will try that. Coming from the Epic 4G Touch, I was told to NEVER use ROM Manager for that phone. Not sure why, or why I can on the GSIII.

Only reason I can think to not use rom manager for me personally would be because the only recovery you can have with it is CWM. If you have another recovery, TWRP, ect. then to even browse the roms with rom manager, you have to install CWM, which is an inconvenience if you have backups and such. Unless of course you don't mind reflashing your recovery.
Sent from my SPH-L710 using xda app-developers app

muzicman82 said:
When I get this fixed, I will try that. Coming from the Epic 4G Touch, I was told to NEVER use ROM Manager for that phone. Not sure why, or why I can on the GSIII.
Click to expand...
Click to collapse
The galaxy s I and II weren't formatted correctly, so, instead of having a normal boot.img and a separate partition for a recovery.img, it had one big zimage. The zimage for the sI and sII had another zimage (which was the actual kernel), a ramdisk (which you need along side the kernel file, I.e. The zimage), and a recovery.img (which is why ROM Manager didn't work, the app couldn't decompile kernels and load a new recovery.img). The sIII was formatted properly, meaning you have a boot.img and a separate partition for a recovery.img. Inside the boot.img there is a zimage (the actual kernel file) and a ramdisk. In normal android phones there is a partition for a recovery.img, which Samsung did give us. That is why you can use ROM Manager on here but not on the E4GT. But when you get your new phone look through the threads they have the newest recoveries for ODIN and how to flash them with ODIN.
Edit: when you get your new phone, feel free to message me for help! I'll point you to the ODIN file you want and the best way to flash that said file.
Generating random authentication keys

jamcar said:
The galaxy s I and II weren't formatted correctly, so, instead of having a normal boot.img and a separate partition for a recovery.img, it had one big zimage. The zimage for the sI and sII had another zimage (which was the actual kernel), a ramdisk (which you need along side the kernel file, I.e. The zimage), and a recovery.img (which is why ROM Manager didn't work, the app couldn't decompile kernels and load a new recovery.img). The sIII was formatted properly, meaning you have a boot.img and a separate partition for a recovery.img. Inside the boot.img there is a zimage (the actual kernel file) and a ramdisk. In normal android phones there is a partition for a recovery.img, which Samsung did give us. That is why you can use ROM Manager on here but not on the E4GT. But when you get your new phone look through the threads they have the newest recoveries for ODIN and how to flash them with ODIN.
Edit: when you get your new phone, feel free to message me for help! I'll point you to the ODIN file you want and the best way to flash that said file.
Generating random authentication keys
Click to expand...
Click to collapse
Yup summed that up perfectly. That said the op must of had a typo in that command somewhere. I use that all the time and even use it to flash modems/kernels while the phones running. Terminal is too easy to screw up tho I'd plug in and use adb over terminal in the future

jamcar said:
The galaxy s I and II weren't formatted correctly, so, instead of having a normal boot.img and a separate partition for a recovery.img, it had one big zimage. The zimage for the sI and sII had another zimage (which was the actual kernel), a ramdisk (which you need along side the kernel file, I.e. The zimage), and a recovery.img (which is why ROM Manager didn't work, the app couldn't decompile kernels and load a new recovery.img). The sIII was formatted properly, meaning you have a boot.img and a separate partition for a recovery.img. Inside the boot.img there is a zimage (the actual kernel file) and a ramdisk. In normal android phones there is a partition for a recovery.img, which Samsung did give us. That is why you can use ROM Manager on here but not on the E4GT. But when you get your new phone look through the threads they have the newest recoveries for ODIN and how to flash them with ODIN.
Edit: when you get your new phone, feel free to message me for help! I'll point you to the ODIN file you want and the best way to flash that said file.
Generating random authentication keys
Click to expand...
Click to collapse
Thanks for the info! I am basically just looking for the latest CWM6 Touch for this phone. Hopefully, I'll have a new phone today. I am curious if anyone has made a jig yet for this phone for me to resurrect with RIFFBOX. Or, where to find/buy the correct mating Molex header to make my own jig.

jamcar said:
The galaxy s I and II weren't formatted correctly, so, instead of having a normal boot.img and a separate partition for a recovery.img, it had one big zimage. The zimage for the sI and sII had another zimage (which was the actual kernel), a ramdisk (which you need along side the kernel file, I.e. The zimage), and a recovery.img (which is why ROM Manager didn't work, the app couldn't decompile kernels and load a new recovery.img). The sIII was formatted properly, meaning you have a boot.img and a separate partition for a recovery.img. Inside the boot.img there is a zimage (the actual kernel file) and a ramdisk. In normal android phones there is a partition for a recovery.img, which Samsung did give us. That is why you can use ROM Manager on here but not on the E4GT. But when you get your new phone look through the threads they have the newest recoveries for ODIN and how to flash them with ODIN.
Edit: when you get your new phone, feel free to message me for help! I'll point you to the ODIN file you want and the best way to flash that said file.
Generating random authentication keys
Click to expand...
Click to collapse
billard412 said:
Yup summed that up perfectly. That said the op must of had a typo in that command somewhere. I use that all the time and even use it to flash modems/kernels while the phones running. Terminal is too easy to screw up tho I'd plug in and use adb over terminal in the future
Click to expand...
Click to collapse
Actually, I copied and pasted it. I even double checked the command line against another thread to make sure they were the same. Path to the IMG was correct. I am also 100% sure the IMG file was a good download and the correct one. No idea what went wrong.

Well you got me stumped then as the command you have in your op is 100% correct and even if you had a bad img the most you wouldve done is borked your recovery partition and had to reflash(believe me ive tried some ballsy **** here). That would not have been enough to brick the phone. As far as a JIG goes its worthless in this scenario as like you said QHSUSB_DLOAD is the sign that its done for. If bestbuy wont charge then your idea of going and playing stupid is your best shot. Although if you can solder and own a riff box then you're a lucky bastard and I got a serious case of envy for that.(I understand the jtag process but couldnt solder to save my life.) That said here is the JTAG process on the s3 done by the guys you were linked to a few posts up. Also while you figure out what to do I would search around for the HTC unbricking project where HTC phones that go into the same QHSUSB mode are able to be unbricked through usb using a terminal prompt in Linux. Hoping one day we'll figure out a way to do the same

billard412 said:
Well you got me stumped then as the command you have in your op is 100% correct and even if you had a bad img the most you wouldve done is borked your recovery partition and had to reflash(believe me ive tried some ballsy **** here). That would not have been enough to brick the phone. As far as a JIG goes its worthless in this scenario as like you said QHSUSB_DLOAD is the sign that its done for. If bestbuy wont charge then your idea of going and playing stupid is your best shot. Although if you can solder and own a riff box then you're a lucky bastard and I got a serious case of envy for that.(I understand the jtag process but couldnt solder to save my life.) That said here is the JTAG process on the s3 done by the guys you were linked to a few posts up. Also while you figure out what to do I would search around for the HTC unbricking project where HTC phones that go into the same QHSUSB mode are able to be unbricked through usb using a terminal prompt in Linux. Hoping one day we'll figure out a way to do the same
Click to expand...
Click to collapse
By JIG, I meant the JTAG to RIFFBOX adapter... mating connector... Not a USB Jig. I have that anyway and does nothing but enter download mode for you.
I can solder to those tiny pins but don't want to since I have a better shot at just returning.
Thanks for the insight.

Ya realized that after I posted the word jig is thrown around here so loosely these days its hard to tell sometimes. That said best of luck in the future. And for future reference here are odin flashable recoveries and for easy switching here are recovery flashable recoveries.

billard412 said:
Ya realized that after I posted the word jig is thrown around here so loosely these days its hard to tell sometimes. That said best of luck in the future. And for future reference here are odin flashable recoveries and for easy switching here are recovery flashable recoveries.
Click to expand...
Click to collapse
So, I'm back with a new GSIII. No problems with the swap.
I flashed the link you gave with CWM6 Touch for ODIN. It flashed successfully, but it wouldn't boot into CWM6. I had to flash CWM5 from ODIN. Any ideas why? Is it because I was coming from stock?

Heres cwm6 but not touch
https://www.dropbox.com/s/54fgrgo6ax1jf88/recovery-clockwork-6.0.1.2-d2spr.tar.md5
Sent from my SPH-L710 using Tapatalk 2

daniel4653 said:
Heres cwm6 but not touch
https://www.dropbox.com/s/54fgrgo6ax1jf88/recovery-clockwork-6.0.1.2-d2spr.tar.md5
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Thanks!

HELP*********
Heres what happn >>
I was running 3.1 slim bean for quite awhile and decided to try out the new Beta (4.2 i think) everything going as usual I rebooted and realize i forgot to install the GAPPS, i go back to recovery just to found myself missing pretty much all my folders (wtf?) i reboot phone thinking well let me re create another folder with the GAPPS in it, and as I do thru my PC i noticed all my folders are actually STILL in my phone.
So I go back to recovery once again thinking well let me reset factory for w.e it is that its causing this to go away, and I did, unfortunately everything went away LITERALLY. Now im stucked in recovery with no folders and no OS.
If i reboot my phone it just goes pitchblack and within a few seconds I'm still able to go to recovery mode (holding buttons) so I'm assuming the phone turns off right after the samsung logo.
A friend of mine who introduced me to flashing gave me this link and told me i'll prolly would need to wipe everything off and re-root my phone, the problem is that this download takes about 20hrs (my speed) and while doable after like 2hrs of download it just cancelled itself, cant afford to have this happen again http://forum.xda-developers.com/show....php?t=1919919
so I read on how to flash a ROM in ODIN if possible. I just cant find a stock rom for my phone or from my region. Can someone please provide me with a link?
I have a Galaxy S3 SPRINT North America.
Will this fix my problem? if not what do i need to do?
What made my phone delete my folders in the first place?

Yeah you have to download a ROM and then move it to your sdcard then flash. You're only soft bricked not hard bricked.
Sent from my SPH-L710 using Tapatalk 2

Like the guy above me said, just download a ROM and if you are using TWRP you can mount your SD card so that it shows up on the computer then just drag the ROM over to the SD card and then you should be able to see and flash it.
If you don't have TWRP you can go into download mode (Power-Home-Volume Down) and flash the one for TWRP in Odin. http://forum.xda-developers.com/showthread.php?t=1933956

Unable to Flash anything via Recovery

My coworker has a T989 with CWM 6.xxx touch that he acquired from the forums. He flashed CM 10 stable but was stuck in
a bootloop. We went back to recovery and flash the darksider scripts which as known to many here shouldn't be used in anything
higher than cwm 5.xx. Any action done in recovery now hangs and freezes. My solution to this would be to go into download mode
and odin a recovery or return the phone to stuck. Now the big problem is the USB port on the phone doesn't work. With properly installed
drivers the phone is not detectable in download mode, nor when the phone was working.
Any suggestions on getting out of this?

Warbuff said:
My coworker has a T989 with CWM 6.xxx touch that he acquired from the forums. He flashed CM 10 stable but was stuck in
a bootloop. We went back to recovery and flash the darksider scripts which as known to many here shouldn't be used in anything
higher than cwm 5.xx. Any action done in recovery now hangs and freezes. My solution to this would be to go into download mode
and odin a recovery or return the phone to stuck. Now the big problem is the USB port on the phone doesn't work. With properly installed
drivers the phone is not detectable in download mode, nor when the phone was working.
Any suggestions on getting out of this?
Click to expand...
Click to collapse
Hhhmm, I have used the darkside super wipe before in CWM 6 and have not seen anything like this [I don't anymore no real need for now it as everything cleans up nice under CWM just use mounts and storage and tap to format /system and /data and then just wipe cache and dalvick cahce and install ROM then install GApps.
You sure you used the right CM10 image [listed under the device name Hercules?
I didn't think we had an official stable CM 10 only nightlies.
If you flashed CM10 that you used on a different device then it replaced some critical files that probably caused this.
If I were you keep trying to get to download mode [there is a trick to it, it is like getting in to recovery manually on boot EXCEPT you need to plug in the USB cable right as you see SAMSUNG logo] and even though I have done it countless times there are those times when it takes me several good tries to get back there.
If you can get in to recovery DONT TOUCH THE DEVICE JUST GET IT THERE then plug in a USB cable and see if you can get to adb
if in windows be sure to run cmd [command prompt] as admin
if you can run adb shell and if it comes up with either just $ or # or a bunch of text then $ or # then...
If it is a $ then type in "su" [no quotes]
that way you get #
If it says # then type [again without quotes]: "restart download"
You should even be able to run the following command without opening the shell first but if it defaults to a user shell and not an admin shell [$ is a user shell and # is an admin shell] it may refuse to follow the command:
[again without quotes] "adb restart download"
This should get the phone to restart to download mode without using hardware keys
If you can get in to recovery and can adb shell to it on the computer that may give you a way to run commands and do things manually, but you will need to find guides on exactly how to run recovery via ADB [I have seen cases where you can copy a recovery to the temp section via adb and then manually run a command in adb shell and basically get the device to use the new file until the next restart.

The darkside scripts will bork any CWM that isn't CWM 5. A much quicker way is to download TWRP recovery and flash it. The recovery will lock up in the the flashing process, but after actually finishing the install. Once it locks up, hold the power button for 10 seconds to reboot. Once the vibration is felt hold both volume buttons and voila! You should be in TWRP recovery now.
I've personally done this myself as I'm the person who actually discovered that the darkside scripts are the cause for borked CWM 6 recoveries. Just don't use them unless you're on CWM 5 or TWRP.
Sent from my SAMSUNG-SGH-T989 using xda premium

RushAOZ said:
The darkside scripts will bork any CWM that isn't CWM 5. A much quicker way is to download TWRP recovery and flash it. The recovery will lock up in the the flashing process, but after actually finishing the install. Once it locks up, hold the power button for 10 seconds to reboot. Once the vibration is felt hold both volume buttons and voila! You should be in TWRP recovery now.
I've personally done this myself as I'm the person who actually discovered that the darkside scripts are the cause for borked CWM 6 recoveries. Just don't use them unless you're on CWM 5 or TWRP.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah but keep in mind myself and sevral others have had issues with TWRP not formatting partitions correctly [I almost threw a Nexus 7 through the wall for it] and it would boot loop over several different ROM flashes for a whole weekend.until I got tired of it and in a last ditch effort changed back to CWM [this was only a version or 2 ago, oh and one of the TWRP devs tried to convince me their /data wipe should also wipe /sdcard [/data/media in JB] and there was no way around that when in CWM I can go to mounts and storage and wipe /data without touching my user data on sdcard [I say SDCard to differentiate the user data housed in internal storage mounted as /sdcard and not just the user data in /data I know there is no actual SDCard in a Nexus 7] so that didn't inspire a ton of confidence in me.
I NEVER recommend TWRP to new users as it has also incorrectly hosed my boot partition on a flash and bricked my device and I had to get a replacement [This was a few versions ago].
Not saying you will get the same trouble just saying to me it is not worth the gamble when talking about my awesome T989 or Nexus 7.
Not to mention TWRP has a tendency when a JB ROM is installed to mirror the legacy mount points on to the /SDCard [in JB for backwards compatibility you get /storage/emulated/0/sdcard that has to be used by recoveries and when I used TWRP it would create that directory structure on to my SDCard when in fact it is only supposed to be a hard link [the directory /storage/emulated/0/sdcard exists but not on the SDCard it is just a pointer]
so essnetially you would end up with a double copy of your SDCard storage back on your SDCard [files still listed under /sdcard but then on sdcard would be a directory 0 that should not be there and in that would be /SDCard/ and another copy of what was on my SD]. I dunno if that bug has yet to be addressed or not [I think so but have not checked].
If you really want to flash TWRP just use market to download GooManager in Android and open and grant root
Once done hit settings button so you see its menu and tap Open Recovery and it will go through flashing TWRP [Similiar to how ROM Manager can flash CWM recovery for you from inside Android [must have Super User access first or they can't do so and you would then need to use Odin and flash it that way]]. Keep in mind your recovery should never freeze and CWM has never done so for me even as part of any install process.

RealPariah said:
Yeah but keep in mind myself and sevral others have had issues with TWRP not formatting partitions correctly [I almost threw a Nexus 7 through the wall for it] and it would boot loop over several different ROM flashes for a whole weekend.until I got tired of it and in a last ditch effort changed back to CWM [this was only a version or 2 ago, oh and one of the TWRP devs tried to convince me their /data wipe should also wipe /sdcard [/data/media in JB] and there was no way around that when in CWM I can go to mounts and storage and wipe /data without touching my user data on sdcard [I say SDCard to differentiate the user data housed in internal storage mounted as /sdcard and not just the user data in /data I know there is no actual SDCard in a Nexus 7] so that didn't inspire a ton of confidence in me.
I NEVER recommend TWRP to new users as it has also incorrectly hosed my boot partition on a flash and bricked my device and I had to get a replacement [This was a few versions ago].
Not saying you will get the same trouble just saying to me it is not worth the gamble when talking about my awesome T989 or Nexus 7.
Not to mention TWRP has a tendency when a JB ROM is installed to mirror the legacy mount points on to the /SDCard [in JB for backwards compatibility you get /storage/emulated/0/sdcard that has to be used by recoveries and when I used TWRP it would create that directory structure on to my SDCard when in fact it is only supposed to be a hard link [the directory /storage/emulated/0/sdcard exists but not on the SDCard it is just a pointer]
so essnetially you would end up with a double copy of your SDCard storage back on your SDCard [files still listed under /sdcard but then on sdcard would be a directory 0 that should not be there and in that would be /SDCard/ and another copy of what was on my SD]. I dunno if that bug has yet to be addressed or not [I think so but have not checked].
If you really want to flash TWRP just use market to download GooManager in Android and open and grant root
Once done hit settings button so you see its menu and tap Open Recovery and it will go through flashing TWRP [Similiar to how ROM Manager can flash CWM recovery for you from inside Android [must have Super User access first or they can't do so and you would then need to use Odin and flash it that way]]. Keep in mind your recovery should never freeze and CWM has never done so for me even as part of any install process.
Click to expand...
Click to collapse
Oh don't mistake my comment Lola I only said to flash TWRP over CWM just so he can have a fully working recovery again. Once that step is done flash back over to CWM 6 again. I myself prefer CWM or TWRP. This is just a method of dumping a borked CWM installation.
Sent from my SAMSUNG-SGH-T989 using xda premium

RushAOZ said:
Oh don't mistake my comment Lola I only said to flash TWRP over CWM just so he can have a fully working recovery again. Once that step is done flash back over to CWM 6 again. I myself prefer CWM or TWRP. This is just a method of dumping a borked CWM installation.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Well Lola as you say, so would opening ROM Manager from inside Android and just tapping to flash the Recovery from the app without having to worry about ADB and manual commands and a run around [as long as you have root access of course].

RealPariah said:
Well Lola as you say, so would opening ROM Manager from inside Android and just tapping to flash the Recovery from the app without having to worry about ADB and manual commands and a run around [as long as you have root access of course].
Click to expand...
Click to collapse
Haha sorry about that. I meant lol if he can get into his ROM, then why hasn't he done so yet? I assumed what happened to him is what happened to me. Flashed dark side wipe, formatted phone, then every install afterwards failed.
Sent from my SAMSUNG-SGH-T989 using xda premium

RushAOZ said:
Haha sorry about that. I meant lol if he can get into his ROM, then why hasn't he done so yet? I assumed what happened to him is what happened to me. Flashed dark side wipe, formatted phone, then every install afterwards failed.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I figured you meant LoL but Lola was funner so I used it again. I was not sure if originally he was one of the posts that siad he could have booted back or not [depends onn where the script froze in recovery as to whether Android boots].
If he can't then the easier way for most folks without having to go in to ADB running cmd as admin if using Windows, the commands and all
I would just say grab good ol Odin and CWM Recovery flash [Odin compatible usually is cwm-hercules-blah.md5 [in this case is not a text file with MD5 hash check it is the actual recovery] and have them flash it via Odin and fix it all up at once and besides they can get CWM touch for free if using Odin and searching the forums because if you dont mind flashing with Odin CWM touch is offered free here whereas if you use ROM Manager and try to flash Touch version of CWM that way it will charge you $2 per device [if you choose market pay option it should be tied to your account and that devices ID and allow future installs without charge [at least how it is for me had to pay once for my T989 once for my 8G Nexus 7 and the n once when I upgraded to 32G Nexus 7, but multiple installs on each individual device don't prompt me after I paid once [I have plenty of times where I may need to flash my recovery without computer access [and I know Koush myself so I like to donate his way he really does bust his ass ] so the ability to just flash the touch version via ROM Manager is great for myself.

I tried adb when I had the device. The Usb port I believe is damaged. I also tried using a flashable twrp and it stopped right before installation. When I restarted cwm was still there. Odin doesn't detect the phone even with the right drivers. It detects a gs3 and a skyrocket. To answer the question above there is a a cm10 stable for the Hercules. Do you think maybe I'm using the wrong flashable twrp. It just gets stuck on installing.
Sent from my Nexus 4 using xda app-developers app

Warbuff said:
I tried adb when I had the device. The Usb port I believe is damaged. I also tried using a flashable twrp and it stopped right before installation. When I restarted cwm was still there. Odin doesn't detect the phone even with the right drivers. It detects a gs3 and a skyrocket. To answer the question above there is a a cm10 stable for the Hercules. Do you think maybe I'm using the wrong flashable twrp. It just gets stuck on installing.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I believe I had TWRP 2.3.0.0. You should be able to find a zip somewhere or you can PM casonswag and ask him for it. He's the one who's been making flashable TWRP zips. Just make sure its for the Hercules.
One question though, does the phone have a ROM you can boot into or is it wiped.completely? Cuz if so, you can download goomanager or rommanager and flash a new recovery that way.
Sent from my SAMSUNG-SGH-T989 using xda premium

Only have access to the messed up recovery. No rom available to boot into.
Sent from my Nexus 4 using xda app-developers app

Warbuff said:
Only have access to the messed up recovery. No rom available to boot into.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Try PMing casonswag for twrp 2.3.0.0. That's what I used and it worked. If not.. man I really don't know :-/
Sent from my SAMSUNG-SGH-T989 using xda premium

Thanks for your help. I've contacted him and awaiting reply. In the meantime my coworker already got a new gs2 from tmo through warranty.
Sent from my Xoom using xda app-developers app

[Q] Phone bricked, no ODIN access! E: Unable to mount '/data'

Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster

Taxmaster said:
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Click to expand...
Click to collapse
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2

elesbb said:
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Hello! I actually downloaded Philz touch recovery in both .zip and in .md5, so that is what I intend to go with. The issue is how I push it using adb, as I believe I need to install something in order to do so, but I don't have any administrative privileges! This is what's preventing me from running ODIN in the first place!
Can you confirm that I can push using adb without installing anything?
Thank you! - Taxmaster

I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.

Monkz said:
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Click to expand...
Click to collapse
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC

Taxmaster said:
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Click to expand...
Click to collapse
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.

lordcheeto03 said:
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
Click to expand...
Click to collapse
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash

elesbb said:
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
Click to expand...
Click to collapse
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster

Taxmaster said:
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Click to expand...
Click to collapse
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.

lordcheeto03 said:
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
Click to expand...
Click to collapse
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!

Taxmaster said:
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Click to expand...
Click to collapse
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD

elesbb said:
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
Click to expand...
Click to collapse
I think I just need to accept that fact that I have been had and that the only thing I can do is wait until I'm home to use ODIN. Absolutely asinine in my opinion, however it seems the only logical conclusion at this point.
If anyone else cares to chime in with suggestions, please let me know!
-Taxmaster

I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.

coolastar said:
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
Click to expand...
Click to collapse
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.

Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
Same, TWRP just has too many problems.
CWM is much more reliable.
Sent from my SGH-M919 using xda premium

Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
If you were using TWRP 2.6.0, that could have been the problem. I reverted back to 2.5.0.2 and like many others, have had no issues. If you had a TWRP backup, that might have fixed it early on.

[Q] TWRP & No Os On my Samsung Galaxy S3 HELP!

I have Samsung At&T Galaxy S3. I bought it used and it worked fine for days until I dropped it and cracked the screen, However it still worked fine until it died. I plugged it in and went to turn it on and it took me to the Team Win recovery. When I try to go to recovery and then reboot it tells me there is no os installed and asks me if I want to install Super SU. If I go to install it takes me to the Odin downloading mode but that is it. Phone is Bricked and stays at the S III screen. HELP is there any hope for me!? I also tried to follow a forum that instructed the rooting of the phone using ODIN. I tried to use the link but couldn't and then I tried Chain fires way but still after 4 hours NO luck, could be me but I am as "Noob" as they come with this apparently. Can someone please help me!?

What ROM was the phone running before it was dropped? You could copy a custom ROM to a micro SD card and try flashing it from recovery.
Don't worry, your phone is not bricked.

Well, if it happened out of the blue like that, there is a possibility of a hardware problem.
Do as audit13 said and flash a ROM via recovery, preferably the same as what was on it before.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

Previous ROM
audit13 said:
What ROM was the phone running before it was dropped? You could copy a custom ROM to a micro SD card and try flashing it from recovery.
Don't worry, your phone is not bricked.
Click to expand...
Click to collapse
I was running I believe the Jelly Bean 4.3...SO I bought the phone from a person. They did not mention it having TWRP or anything else. It I think had something called Super SU too...not sure what that is. I have tried to flash in ODIN. nothing. I have also tried to flash a rom using an SD card it was the kit kat 4.4.4 but it says failed each time. I don't know what to do...

Super SU
DocHoliday77 said:
Well, if it happened out of the blue like that, there is a possibility of a hardware problem.
Do as audit13 said and flash a ROM via recovery, preferably the same as what was on it before.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
So I bought the phone from another person who failed to mention anything not stock about the phone! It came with I believe the jellybean 4.3 and something like super su. What is super SU? I have tried to flash the kit kat 4.4.4 to the phone with an sd card but it always says failed...I don't understand! I have been going out of my mind and reading and trying a but nothing is working!

SuperSU is part of your root access. Its an app that helps to manage root access from your other apps.
When the flash fails does it give you an error message? Try flashing again, but after it fails do not reboot. Go back to the Advanced menu and choose copy log to SD. Then attach the recovery.log here.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

Unsure
DocHoliday77 said:
SuperSU is part of your root access. Its an app that helps to manage root access from your other apps.
When the flash fails does it give you an error message? Try flashing again, but after it fails do not reboot. Go back to the Advanced menu and choose copy log to SD. Then attach the recovery.log here.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yes I get an error message. Ok so I suppose I am still trying to grasp at the entire concept of all of this! So let me start here: I bought the phone as I said and it seemed fine. It didn't however have all the normal Google apps etc. and I wasn't sure why. 2 days later after purchase I dropped the phone. Screen cracked but for the rest of the day it worked fine. It died, I plugged it in at home and when I tried to turn it on it went straight to TWRP. I messed with the phone in recovery NOT understanding what I was doing and I think I may have wiped/deleted the Super SU off my phone, I don't know if it is rooted or anything anymore if it was rooted in the first place. I believe it was running Jellybean before this mess and since then I have tried to do multiple things to it including installing a ROM on an SD with gapps and flashing in TWRP but always get an error message. I did just try installing UPDATE-SuperSu back onto the flashing using an Sd and that installed but still couldn't flash a rom. I still cannot get past the Samsung S III screen and still the phone says no OS. So I suppose is there a way to start from scratch so...someone that can walk me through this. I am dying and DON'T want to spend the money the Phone stores want to fix my phone! I don't have a carrier like Sprint etc. I was using the phone with a sim card for straight talk. Please if I can try this I will! Thanks again for all your help...

Try flashing the MJB firmware via Odin on your computer. That should restore your device to fully working stock, provided there isnt a hardware problem.
Factory reset in recovery, then reboot download mode. Plug into your computer and run Odin v3.09. Click the AP button and select the firmware you downloaded. Should be a .tar.md5 file. Then click start.
You can get odin from my sig if needed.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
Try flashing the MJB firmware via Odin on your computer. That should restore your device to fully working stock, provided there isnt a hardware problem.
Factory reset in recovery, then reboot download mode. Plug into your computer You can get odin from my sig if needed.and run Odin v3.09. Click the AP button and select the firmware you downloaded. Should be a .tar.md5 file. Then click start.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
So, I tried to do what you said but when I extract the files there is no tar md5 file, if I don't extract I can't see any of the MJB firmware. I don't know what I doing wrong...

Highlight/select all of the files at once. Then right click and extract. It should combine them all into the one.
If you're still having trouble with it, I'll try to do it for you. Been meaning to do this anyway to make things a little easier for folks. But it'll probably be at least Sunday night or Monday before I can do anything. (Funeral/family stuff has me tied up all weekend).
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
Highlight/select all of the files at once. Then right click and extract. It should combine them all into the one.
If you're still having trouble with it, I'll try to do it for you. Been meaning to do this anyway to make things a little easier for folks. But it'll probably be at least Sunday night or Monday before I can do anything. (Funeral/family stuff has me tied up all weekend).
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
So I have tried SO many things now I can't even remember. I have tried flashing roms via SD card, I have tried to re-root the phone by flashing Super SU from an SD card no luck...I have tried to factory reset using the instructions you posted but upon extracting there is no tar md5 file. lots of others but not that one. My download screen says:
ODIN MODE
PRODUCT NAME: SGH I747
CUSTOM BINARY DOWLOAD: YES (2 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUAULCOM SECUREBOOT: ENABLE
WARRANTY BIT: 1
BOOTLOADER RP SWREV: 2
When I try to reboot my phone in TWRP it says, "NO OS" installed are you sure you wish to continue.
I will slide the deal towards yes/reboot and then it will say, "Your phone is not rooted do you wish to install Super SU" I will slide to install and it will go to download mode and look like the above. That's it. No successful flashing via SD or Odin...I am pooped. By the way I appreciate your time, and I am so sorry for your loss.

Still No Luck
DocHoliday77 said:
Highlight/select all of the files at once. Then right click and extract. It should combine them all into the one.
If you're still having trouble with it, I'll try to do it for you. Been meaning to do this anyway to make things a little easier for folks. But it'll probably be at least Sunday night or Monday before I can do anything. (Funeral/family stuff has me tied up all weekend).
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I don't know what happened but I thought I had responded to this, I know its late but please accept my deepest condolences.
As for my phone I have tried EVERTHING I can think of, everything you have suggested as well and nothing is working. I Can download ODIN, I can download files and Md5. tar files but it always says failed...I don't know what to do or anything. I have been working on this for almost 2 months now. I need help, there is no cell phone repair here that can flash software except ONE company and they have a bad reputation...I want to start from scratch here because I am So turned around. I have tried so much I am just confused...If you can help me at all, step by step perhaps then I could get you the answers you need to help me. Really thank you for the time you have already given me.

I suggest using CWM to flash anything. I had issues with TWRP and Philz Touch worked perfectly. I have recommended it to other that had no OS on their phone and they were able to get their phone up and running on a custom ROM.
http://forum.xda-developers.com/showpost.php?p=55897607&postcount=2

I apologize for not responding before. Been hard to keep up with everything lately.
Try as audit13 suggested and flash cwm or philz recovery with Odin. Then reboot recovery and flash a rom. Hopefully one of those will work where twrp failed.
Sent from my SAMSUNG-SGH-I747 using Tapatalk