Database Users

Big problem with Epic 4G! New UPDATE I/O device error.

This is when I put my phone into mass storage.
My phone is taking forever to be recognized by my Windows 7 computer, my laptop recognizes it right away, I am using my front USB ports and have tried the back one even. Also, I have installed drivers and un-installed them, I have also done everything under the sun to try and get it to sync better. But alas it takes a while for my desktop to recognize that I have put my phone into mass storage. It is really bugging me, I am also using the stock cable that came with the phone and have even installed the official drivers. But to no avail.

My windows 7 laptop recognizes it fine
Sent from my SPH-D700 using XDA App

Maybe its ur usb port then if ur laptop picks it up fine. U can't blame it on the phone
Sent from my SPH-D700 using XDA App

b1indsided said:
Maybe its ur usb port then if ur laptop picks it up fine. U can't blame it on the phone
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I am not blaming the phone at all. I am just trying to understand why this phone doesn't mount and my Hero did fine and does fine on the same port. How can I not say maybe its the phone...

Lol well maybe its the usb like I was saying. Or maybe it just doesn't like the micro usb??
Sent from my SPH-D700 using XDA App

b1indsided said:
Lol well maybe its the usb like I was saying. Or maybe it just doesn't like the micro usb??
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Very very possible my good sir. I will keep trying different ports!
EDIIITTT AND UPDATE!
I AM GETTING AN I/O device error.

Try reformatting the card... Use a card reader to pull your data off first..
You could also have a defect on your device, but I'd test it in a different computer before concluding its the phone..

nicknomo said:
Try reformatting the card... Use a card reader to pull your data off first..
You could also have a defect on your device, but I'd test it in a different computer before concluding its the phone..
Click to expand...
Click to collapse
It is definatetly not a device defect for I have a samsung laptop with Windows 7 home premium 64 bit and it recognizes right away. Also, I find that if I enable mass storage the computer reads it (my desktop) but it just takes a while to. I will jsut have to be patient I guess. lol

I'm having the same problem...I've tried both sets of drivers.
Sent from my SPH-D700 using XDA App

Blitzpwnage said:
It is definatetly not a device defect for I have a samsung laptop with Windows 7 home premium 64 bit and it recognizes right away. Also, I find that if I enable mass storage the computer reads it (my desktop) but it just takes a while to. I will jsut have to be patient I guess. lol
Click to expand...
Click to collapse
Very few defects exist across ALL the epic phones.. I was suggesting it could be a defect with that specific phone, but that conclusion should only be reached after further testing..

I had trouble with my Win 7 64bit laptop when I first tried to connect it. I switched to the usb port on the other side of the lappie and it recognized instantly. There seems to be a bug in Win 7 and how it recognizes the Epic on certain ports. My Blackberry worked fine in all ports. I did install the 64 bit drivers and still had problems with that port.

Got my replacement!

Here's a small little "unboxing" I did. Try not to laugh too much at my southern-self I'm not good with a camera, I'm shy ^_^
http://www.youtube.com/watch?v=JBRihHh4R-4&feature=youtube_gdata_player
Sent from my perfect epic

Lol nice... now odin your old broken epic and root your new one woooo first
Sent from my SPH-D700 using XDA Transparent App

Nice unboxing makes me wish I had a brand new one

Hope you got one from a good batch that let's you overclock as high as you want or undervolt. I will be interested to see what differences you have between the two
Sent from my SPH-D700 using XDA Premium App

I can't believe they send a new 16gb sd card with the replacement. I need to replace mine as well, it has cracks on the top corner of the screen.
Edit: do you have to send a 16gb card back in order to not have a penalty?
Sent from my SPH-D700 using XDA App

No you keep your old card battery charger everything only thing they want is the phone you even keep the old battery back
globalninja said:
I can't believe they send a new 16gb sd card with the replacement. I need to replace mine as well, it has cracks on the top corner of the screen.
Edit: do you have to send a 16gb card back in order to not have a penalty?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Sent from my SPH-D700 using XDA Transparent App

steviee7 said:
No you keep your old card battery charger everything only thing they want is the phone you even keep the old battery back
Sent from my SPH-D700 using XDA Transparent App
Click to expand...
Click to collapse
What he said. They say not to send it back. Just the phone.

Ok, so im trying to root using the same method i did last time. but i cant get the drivers to install completely 4/5 install fine but: CDC Abstract Control Model (ACM) is stuck on Installing driver software. Adb says the device is attached, but offline. Any suggestions? Usb debugging is enabled.

Didn't you already have the drivers installed?
Help support autism awareness,it only takes 2 seconds to help make a difference...
http://picketfenceblogs.com/vote/3616

zanderman112 said:
Ok, so im trying to root using the same method i did last time. but i cant get the drivers to install completely 4/5 install fine but: CDC Abstract Control Model (ACM) is stuck on Installing driver software. Adb says the device is attached, but offline. Any suggestions? Usb debugging is enabled.
Click to expand...
Click to collapse
1. Plug in epic
2. Go to device manager
3. Uninstall anything samsung, google, android, sprint and epic.
4. Check add or remove software a make sure all drivers are gone
5. Unplug phone
6. Install drivers using the exe
7. Root

ecooce said:
Didn't you already have the drivers installed?
Help support autism awareness,it only takes 2 seconds to help make a difference...
http://picketfenceblogs.com/vote/3616
Click to expand...
Click to collapse
Yes, but when i plugged it in, it started installing stuff. I unplugged it, and plugged it back in. It worked this time.

Nice video

qbking77 said:
Nice video
Click to expand...
Click to collapse
Thanks. Lol

Sent from my SPH-D700 using XDA App

zanderman112 said:
Ok, so im trying to root using the same method i did last time. but i cant get the drivers to install completely 4/5 install fine but: CDC Abstract Control Model (ACM) is stuck on Installing driver software. Adb says the device is attached, but offline. Any suggestions? Usb debugging is enabled.
Click to expand...
Click to collapse
it will work without that one.

CrfEpic4g said:
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Forget something? lol

CrfEpic4g said:
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Sent from my SPH-D700 using XDA Transparent App

steviee7 said:
Sent from my SPH-D700 using XDA Transparent App
Click to expand...
Click to collapse
Haha
Sent from my perfect epic.

Nice... commense the rooting process
Sent from my Nexus S 4G using XDA App

I just had mine replaced this week and on low brightness settings the screen seems to have a yellow green tone. Turn up the brightness and the whites are as white as can be. Any issues with your screen on the lowest brightness?
As for over clocking I have had no issues @1300
Sent from my SPH-D700 using Tapatalk

Bad block

Guys.. I found that ma cell as two bad block using my recovery log ...!! I don't want to over come this problem...
I just want to know why this bad block occur and how? Is there any solution found for this? Is this bad block happens because of without flashing task 28 or task29? Clear me...
Sent from my HTC HD2 using Tapatalk

See this thread.
Please search before posting

I already seen that thread but no one as written about the cause for the bad blocks!!
Sent from my HTC HD2 using Tapatalk

i agree w/you

Thanks!!
Sent from my HTC HD2 using Tapatalk

They become bad blocks when you flash too often.
NAND can be rewritten very often but. It's like ssd in your pc. After some time they will have some. Issues etc.
These bad blocks get somehow destroyed so they can't be rewritten anymore.
There is no program managing to flag them or repair them.
Sent from my HD2 using xda premium

"Bad blocks" are physical imperfections in memory. Usually its from natural wear.
Anything that boasts the ability to "fix" bad sectors is really just flagging them as unwritable. Memory typically comes with a number of extra blocks to compensate.
Good practice is to check ocassionally for increase in bad sectors[blocks]… if so disk failure is likely imminent. If no increase, youre fine -- memory frequently run years with a few bad sectors.
Sent from my MB860 using xda premium

xhazk said:
"Bad blocks" are physical imperfections in memory. Usually its from natural wear.
Anything that boasts the ability to "fix" bad sectors is really just flagging them as unwritable. Memory typically comes with a number of extra blocks to compensate.
Good practice is to check ocassionally for increase in bad sectors[blocks]… if so disk failure is likely imminent. If no increase, youre fine -- memory frequently run years with a few bad sectors.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I agree w/you

jonas2295 said:
They become bad blocks when you flash too often.
NAND can be rewritten very often but. It's like ssd in your pc. After some time they will have some. Issues etc.
These bad blocks get somehow destroyed so they can't be rewritten anymore.
There is no program managing to flag them or repair them.
Sent from my HD2 using xda premium
Click to expand...
Click to collapse
Following on from this point, one of the things you can do is try to refrain from a full cycle with Task29 etc when flashing new ROMs. It's kind of pointless as 99% of the time all that is necessary is a repartition and then flash the ROM. I haven't ever done a task 29 and I've flashed a couple of ROMs, but I never get issues (despite some of the ROMs recommending a 'full wipe' i.e. task 29 before flashing)

Thanks for all your reply...
Sent from my HTC HD2 using Tapatalk

xhazk said:
"Bad blocks" are physical imperfections in memory. Usually its from natural wear.
Anything that boasts the ability to "fix" bad sectors is really just flagging them as unwritable. Memory typically comes with a number of extra blocks to compensate.
Good practice is to check ocassionally for increase in bad sectors[blocks]… if so disk failure is likely imminent. If no increase, youre fine -- memory frequently run years with a few bad sectors.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
My question was is this bad block happens because of flashing without Task29?
Sent from my HTC HD2 using Tapatalk

sam razzy said:
My question was is this bad block happens because of flashing without Task29?
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
No, not mainly . Task29 just erases all data.
They come up because of the high number of rewrites.
Sent from my HD2 using xda premium

jonas2295 said:
No, not mainly . Task29 just erases all data.
They come up because of the high number of rewrites.
Sent from my HD2 using xda premium
Click to expand...
Click to collapse
Thanks for your response..
Okie lemme know if I flash without task28 or 29 ..will this cause for bad block..
I saw one guy comment that task 28 is the cause for bad block..
Also if I stay with one partition.. is that cause any problem...
Sent from my HTC HD2 using Tapatalk

sam razzy said:
Thanks for your response..
Okie lemme know if I flash without task28 or 29 ..will this cause for bad block..
I saw one guy comment that task 28 is the cause for bad block..
Also if I stay with one partition.. is that cause any problem...
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
No. It doesn't matter if you do a task or not they will appear.
Although you don't need to do a Task29 very often.
Sent from my HD2 using xda premium

If I do a Clk version flashing (not magdlr) can prevent from upcoming bad block
Sent from my HTC HD2 using Tapatalk

sam razzy said:
If I do a Clk version flashing (not magdlr) can prevent from upcoming bad block
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
When flashing clk, you are still flashing...
But, using clk, you can re-partition the location where your bad blocks are located.

yz.hd said:
When flashing clk, you are still flashing...
But, using clk, you can re-partition the location where your bad blocks are located.
Click to expand...
Click to collapse
How is that!?
Sent from my HTC HD2 using Tapatalk

You could probably use this, though I always just did it manually. I literally had too many bad blocks to count, as in when I formatted the partition through clK the bad blocks were scrolling up too fast to see. Wasn't a problem, just had to make the system partition large enough so that there were enough good blocks to flash a ROM.

I donno how the bad block disappeard .!! Actually I tried task29 ... but i can't c any bad blocks now.. why?
Sent from my HTC HD2 using Tapatalk

sam razzy said:
I donno how the bad block disappeard .!! Actually I tried task29 ... but i can't c any bad blocks now.. why?
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
Has anyone else done this and fixed your bad blocks? My HD2 has been slowly dying over the last 6 months and now is practically unusable. Would love to fix this issue

And this is why removable storage is not always good

My sd card died all of a sudden. No warning, just a damaged sd card notification and it can't be mounted. It wasn't cheap and I really didn't even use it that much, this is the 2nd time this has happened.
I lost all my media, nandroids, dta2sd apps, pictures. Some of that is backed up but not the recent stuff.
Since I didn't even use the full 16GB, I will in future prefer a phone with 16GB memory even if it has no sdcard. Internal memory is faster and more reliable.

Sometimes lol or stop buying cheapo
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

nrm5110 said:
Sometimes lol or stop buying cheapo
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
YUP!! You buy cheap you get cheap!!

internal memory can crap out just as easily, then you are even more screwed.
Sent from my PC36100 using XDA

vladthedog said:
internal memory can crap out just as easily, then you are even more screwed.
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
EXACTLY.
And if the data on the card was that important to you, you should have had a backup of it.

One example implies truth?
So internal > external because your external stopped working?
What would you say to someone who says external > internal because their internal stopped working?
One is easily fixed (buy a new SD card), one is not easily fixed (buy a new phone).
This thread makes me sad.

Well if you just use internal, wouldn't that be even worse if it was damaged?

mazdarider23 said:
YUP!! You buy cheap you get cheap!!
Click to expand...
Click to collapse
He said it wasn't cheap......

HipKat said:
He said it wasn't cheap......
Click to expand...
Click to collapse
I read it was cheap also the first time.
I really don't care for SD slots I would much rather have a removable battery.
Sent from my PC36100 using Tapatalk 2

Just an fyi if internal dies phone is perma bricked, ask the 200 or so ppl who fried their emmc chips(internal storage/rom) on the et4g by wiping in recovery while on an ics kernel. The partition structure has changed and when wiping on a leaked ics kernel it would damage the partition causing a perm brick that even jtag couldn't save. So internal=/=external. External is replaceable, internal damage = dead phone/paperweight.
Sent from my SPH-D710 using xda premium

The New leak 4.2.1 doesn't have the sudden death fix

For my surprise today my phone don't respond, I left charging with the travel adapter, no boot, no Samsung logo, no recovery no download mode, maybe Is a sudden death problem :'(
I put my battery in the my wife's S3, and the battery is fully charged.
This is my last configuration:
Wanamlite rom 6.0
Philz touch recovery 4.63
Stock kernel (rom's kernel)
Last bootloader with the red light I in the upper left corner.
Enviado desde mi E15a usando Tapatalk 2

You should have been protected from Phil recovery perhaps that line of kernel code doesn't fix SDS after all.
Sent from my GT-I9300 using xda premium

no, philz recovery would only protect him while he was in the recovery

delsus said:
You should have been protected from Phil recovery perhaps that line of kernel code doesn't fix SDS after all.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
So? what went wrong Mr. delsus?

This is very concerning but let's not jump to conclusions too fast, shall we? People would freak out.
Maybe someone can look over the leaked kernel and search for the SDS string (Movi ops or something ).
Sent from my GT-I9300 using Tapatalk 2

No source, no strings... They said. (I already asked)
Sent from my GT-I9300 using xda premium

Glebun said:
no, philz recovery would only protect him while he was in the recovery
Click to expand...
Click to collapse
Makes sense, so the real need for the fix in recovery isn't really needed, the chances of SDS in recovery are almost none existent.
Sent from my GT-I9300 using xda premium

delsus said:
Makes sense, so the real need for the fix in recovery isn't really needed, the chances of SDS in recovery are almost none existent.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Of course they are existent... What if you are running a Nandroid Backup or you're installing a new ROM...
Those two activities take more I/O Requests to the memory chip than the "Normal" usage of the phone, you are reading and writting to the memory like crazy...
So the recovery fix is completely needed my friend...

jimbo77 said:
Of course they are existent... What if you are running a Nandroid Backup or you're installing a new ROM...
Those two activities take more I/O Requests to the memory chip than the "Normal" usage of the phone, you are reading and writting to the memory like crazy...
So the recovery fix is completely needed my friend...
Click to expand...
Click to collapse
The majority of reports of SDS are whilst they are charging, also unless you flash more than 4 times a day you don't spend much time in recovery.
I haven't seen anything to say the amount of read/write requests affect SDS, its not the only thing that can make your NAND fail.
Sent from my GT-I9300 using xda premium

Must.... flash..... back..... to.... sds....safe....romm...
Oh wait, warranty .
Sent from my GT-I9300 using xda premium

How old was your phone? Are you sure your memory wasn't damaged enough before the fixes got launched?
I can't figure out why Samsung shouldn't fix it for that 4.2.1 build. Maybe to screw leakers?
Sent from my GT-I9300 using xda app-developers app

delsus said:
The majority of reports of SDS are whilst they are charging, also unless you flash more than 4 times a day you don't spend much time in recovery.
I haven't seen anything to say the amount of read/write requests affect SDS, its not the only thing that can make your NAND fail.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
But Jimbo is correct - we don't know what causes the SDS but there is a very real possibility of a higher risk on more intensive IO operations.
This does not depend on time but rather on the wear of the EMMC, it has been theorized that the wear leveler is again at fault (like on S2 superbrick)
Recovery and restore are maybe the most intensive IO operations (besides installing AND the transcoding - which is seemingly done while charging, remember the Video Player CPU usage on that state... maybe that's the reason why it manifested... but I cannot tell for sure).

htcsnap93 said:
Must.... flash..... back..... to.... sds....safe....romm...
Oh wait, warranty .
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
LOL !!!

so what about someone unpacking the kernel and find if this lines r in drivers/mmc/core/mmc.c and mmc_ops.c
https://github.com/AndreiLux/Perseus-S3/commit/54ddcbe7aff1c19c07f76a05ab45f37bcbae2951

t0n0n said:
How old was your phone? Are you sure your memory wasn't damaged enough before the fixes got launched?
I can't figure out why Samsung shouldn't fix it for that 4.2.1 build. Maybe to screw leakers?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Now you speak of memory, comes to my mind that this rom has a swap memory partition, if you type "free" on the terminal emulator, you can see it.
I bought the phone on june 1, 2012.

delsus said:
The majority of reports of SDS are whilst they are charging, also unless you flash more than 4 times a day you don't spend much time in recovery.
I haven't seen anything to say the amount of read/write requests affect SDS, its not the only thing that can make your NAND fail.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Exactly. It is the correlation between charging and SDS which is quite apparent when analyzing the data thread that has led me to speculate that the factory charger may be responsible for this, or at the very least be exacerbating the situation. I've never used the stock charger, (mine is still in the box and I'm using the SII charger) but there are several reports of fried USB cables, etc. when using the stock charger, so I don't think it too far-fetched that they could be related somehow.

donalgodon said:
Exactly. It is the correlation between charging and SDS which is quite apparent when analyzing the data thread that has led me to speculate that the factory charger may be responsible for this, or at the very least be exacerbating the situation. I've never used the stock charger, (mine is still in the box and I'm using the SII charger) but there are several reports of fried USB cables, etc. when using the stock charger, so I don't think it too far-fetched that they could be related somehow.
Click to expand...
Click to collapse
stock charger has nothing to do with SDS its bug in the eMMC firmware :silly:

they would've issued a statement about it it though, because it would've saved a lot of phones

yahyoh said:
stock charger has nothing to do with SDS its bug in the eMMC firmware :silly:
Click to expand...
Click to collapse
Yup, the thing is, apparently there is a TranscodeService for the Video Player that is triggered to start on charge, the operation should be IO intensive. That could be a valid co-relation. But the charger itself does not have any influence from what developers have gathered, it is a defect in the eMMC firmware.

This is really an great discussion
I wanted to know if I flash with any other kernel instead of stock, will there be even problem on leak
Sent from my GT-I9300 using xda app-developers app