Related
Hi,
I have lost the ability to use my internal and external storage memory. Is there anyone that can tell me how to fix this. I am at a loss.
Thanks
Zack Cadieux
I have the same problem after flashing JPH firmware. (I know how to flash FW, I've been flashing every FW as it was released)
It says that there is an I/O error in mmcblk0p1.
I think i'm screwed as well.
Not one person knows what is going on
Hi,
Im supprised that even the dev's know nothing about this issue. I have read almost every thread and nothing to show how to respolve this issue. Is there anyone???
I had the same problem. I have a Bell Vibrant which I flashed to JPH using the Kies method, rooted, then One Click Lag Fix. Things worked for about a day then I lost my storage. Luckily I did the samsung 3 button fix first.
I downloaded the Tmobile Stock Rom, and used the following instructions to flash.
http://forum.xda-developers.com/showthread.php?t=734475
It booted up to the Tmobile Rom, and everything worked. I then used Odin to flash back to JPH.. rooted.. and now am contemplating the Lag Fix.
Not sure if it was related to the problem but I had my phone connected to my computer transferring files before all hell broke loose. I may have yanked the USB without unmounting... Just a thought.
Good Luck..
Dawgplg said:
I had the same problem. I have a Bell Vibrant which I flashed to JPH using the Kies method, rooted, then One Click Lag Fix. Things worked for about a day then I lost my storage. Luckily I did the samsung 3 button fix first.
I downloaded the Tmobile Stock Rom, and used the following instructions to flash.
It booted up to the Tmobile Rom, and everything worked. I then used Odin to flash back to JPH.. rooted.. and now am contemplating the Lag Fix.
Not sure if it was related to the problem but I had my phone connected to my computer transferring files before all hell broke loose. I may have yanked the USB without unmounting... Just a thought.
Good Luck..
Click to expand...
Click to collapse
My situation is about the same. I did the update and applied the root and lag fix. Phone worked fine for a day or so and then it just locked up and couldn't detect the sd cards anymore. I rebooted and it was stuck on the S for over 30 minutes...I flashed HJ2 and when it rebooted all that happens is I get a gray blinking battery if it's attached via USB and if on battery it boots up to the I9000 initial screen and shuts down. Lucky for me the shop will do a swap when they restock in about a week. Back to the HTC for now.
LordSoth said:
My situation is about the same. I did the update and applied the root and lag fix. Phone worked fine for a day or so and then it just locked up and couldn't detect the sd cards anymore. I rebooted and it was stuck on the S for over 30 minutes...I flashed HJ2 and when it rebooted all that happens is I get a gray blinking battery if it's attached via USB and if on battery it boots up to the I9000 initial screen and shuts down. Lucky for me the shop will do a swap when they restock in about a week. Back to the HTC for now.
Click to expand...
Click to collapse
Dont recall if I did any of the Recovery options, but I remember the big Grey Battery... You could even try flashing back to JPH through Odin... It may wake it up. But good to hear they will replace it, at least you have something to fall back on.
Dawgplg said:
Dont recall if I did any of the Recovery options, but I remember the big Grey Battery... You could even try flashing back to JPH through Odin... It may wake it up. But good to hear they will replace it, at least you have something to fall back on.
Click to expand...
Click to collapse
There was another thread I read about this exact same issue happening and the guys had to return the phones in the end. Yea I was lucky I was under the 30 days limit. By the time I get a new one hopefully a proper Froyo build will be out.
Black screen of death. It's what I call it because that's all I get.
Here is a summary of what happened.
1) My Samsung Galaxy S started to get slower and slower. I decided to turn it off and back on (using
the power down button) to see if it would get any faster.
2) I would then only get the first start screen, then the graphic S screen after which it would go
blank (black screen of death). After about 2 min, if I pressed any keys, the two buttons on the bottom
would light up and stay on. If I pressed any one of them, it would go off and back on.
3) I could hold the power button and it would reboot.
So, that's were it was, here is what I have tried so far.
a) Check to see if I could get into download mode. Yep, that works.
b) Check to see if I could get into recovery mode. Yep, that works.
c) Hmmm, oh well, lets do a system wipe. Yep, can do that but it still would not boot up. I just get
to the graphic S screen and then the black screen of death.
d) Lets take the battery out. (over night) Nope, still black screen of death.
Based on the above, a flash should work right. Sorry, but I had a lag fix installed. Well no matter
what, I could not get the phone to boot so I guess I better try flashing anyway.
I've tried several images. Most of them get the error "your storage not prepared yet, please use UI me nu for format and reboot actions" OK, this is because of the lag fix. I then installed stzupy's image and that fixed the "your storage not prepared yet bla, bla bla. But still black screen of death.
I've tried flashing over and over, with pid 512, 513, 803. Nothing. I still come up the black screen of death.
So, can someone guide me in the right direction. I've done searches on this but everyone else seems to have had a different problem. Mostly doing a Factory Reset worked for them. I've done that over and over. After removing the battery, after flashing, before flashing. Nothing seems to get me past the black screen of death.
Thanks in advance for all and any help,
Jeff
p.s. Please don't reply with a message saying something like flash X's kernel. I need descriptive instructions such as flash with "this kernel" into CSC (or pda or modem) using XXX pid while checking repartion (or not). In other words, don't assume I know what I am doing. I don't.
there is now way you can save your apps installed but your sd card files will be there.
Only thing you can do is reflash my friend
webstar1 said:
there is now way you can save your apps installed but your sd card files will be there.
Only thing you can do is reflash my friend
Click to expand...
Click to collapse
Really don't care about my apps. (I have everything backed up onto my computer via Titanium Backup) But if you check my message above, I have reflashed until the cows come home. I still get the black screen of death.
- Jeff
Sorry Jeff Your Samsung Galaxy S is 'Proper F*cked Mate'
Yes sir I believe you are toast indeed! Your internal SD card is probably toast. I believe you're a fine Canadian of course assuming you've got the Bell i9000m? A lot of us have had this and there's a poll on it actually. Mine just toasted out about 2 weeks ago, thankfully i've an awesome friend in Canada on the forum that has helped me out!
No matter what you flash or try to do, it will not mount the sdcard in there or let you format it manually. You'll have to send it back to BELL or Samsung.
BA_Flash_GOD said:
Yes sir I believe you are toast indeed! Your internal SD card is probably toast. I believe you're a fine Canadian of course assuming you've got the Bell i9000m? A lot of us have had this and there's a poll on it actually. Mine just toasted out about 2 weeks ago, thankfully i've an awesome friend in Canada on the forum that has helped me out!
No matter what you flash or try to do, it will not mount the sdcard in there or let you format it manually. You'll have to send it back to BELL or Samsung.
Click to expand...
Click to collapse
Sigh! That's what I've been worried about. Yep, bell i9000m. Oh well, if I gotta, I gotta. Only 1 month old.
- Jeff
Flash stock, then give it back to samsung to repair, they should then
Sent from my GT-I9000 using XDA App
Had the same problem today. Wanted to change from JPA to JPO so thought it best to do a factory reset, but when phone booted up again, it started, then the screen went black with the occasional vibration. Tried all the usual things, removing battery & waiting, wiping cache etc., but no luck. Then put it in download mode & installed JPA again, but same problem on bootup. Thought I had finally managed to brick my phone (horrible feeling). So I solved it this way :-
Installed JM8 using .512 pit with repartition ticked, hooray my phone booted up again. The long delay after the S logo & finally completing boot was nail biting to say the lease. Now everything is working great & I am in the process of installing JPO.
Phone was flashed to 2.2, however after shutting down the phone and booting it up again, I get Black SCREEN + glowing buttons.
Device : Samsung i9000 from Bell running flashed 2.2 Rom.
I've tried following this guide :
STAGE 1 (applies only if you are coming from an earlier Froyo build)
* We are now going to flash the XWJM8 firmware again (Éclair), so make sure that you load the files for this firmware in Odin.
* In PIT, load the 502.PIT file
* For PDA, select the ‘CODE_I9000XWJM8.tar.md5’ file and for PHONE, select the ‘MODEM_I9000XXJM4.tar.md5’ file. Leave all others blank.
* Make sure that the Re-partition box is checked. All other settings should be as shown in the screenshot below.
*Sorry can't post link, forum restriction*
After stage 1, Odin says Passed, my i9000 reboots with still a black screen+ glowing buttons.
I want to start Stage 2, however I can't find the file ‘JPO_JPO_U_JPP.tar’ file.
I've looked up for solution for the last 2 days and can't seem to find a solution anywhere.
Things I've tried on my own without sucess :
Flashed again this time with a CSC from bell, I've read that sometimes without CSC flashing can't be done, but even with the CSC files, my phone is still ''bricked''
Anyone have any idea how to fix this? Ultimately, I want to go back on 2.2 but for now, I just want my phone to boot again =(.
Hate to say it but it sounds like yout internal sd card is dead like MANY OTHERS who have flashed... No way to fix except to send for repairs to bell/samsung...
Sent from my GT-I9000M using XDA App
I wish you'd stop stating that flashing fubar's your phone. Many people running stock, unrooted devices are reporting the same problem.
Isn't there a way to try and access internal sd card?
Have you try doing a factory reset?
Yeah, I've tried doing so, after reading and researching online, I think this could fix my problem.
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
see reply #7
However adb doesn't even reconize the phone =/
terranq said:
I wish you'd stop stating that flashing fubar's your phone. Many people running stock, unrooted devices are reporting the same problem.
Click to expand...
Click to collapse
I diddnt specifically mean that it was the flashing that did it but it is OBVIOUS that it happened after he flashed right???
It is known that flashing will sometimes "speed up" the death of an already faulty sd card and that is what I meant by my original post...
And PS... The number of people reporting their sd cards failing on stock firmware w/ no lagfix or no previous flashes to "unofficial firmware" is WAY lower than those reporting sd card death after flashing or adding lagfixes, etc...
Which obviously points to an existing hardware fault that is exacerbated by flashing, not caused by flashing
terranq said:
Which obviously points to an existing hardware fault that is exacerbated by flashing, not caused by flashing
Click to expand...
Click to collapse
And again... I did not specifically state that it was the "flashing" that killed the OP's phone. I simply stated that this seems to happen to MANY people after they flash. NOT the same thing...
Did you come to this thread to argue or to help the OP? I simply posted a reply last night stating that it seems his internal SD card is dead so that he could prepare himself for having to send it away for repairs. I did not respond to the OP to get into an arguement with anyone over "what causes the internal SD cards to fail".
Don't argue guys! I appreciate all your help
What is the best way to ''fix the internal sd card''
Isn't there a way to like factory reset the internal sd card.
cuem said:
Don't argue guys! I appreciate all your help
What is the best way to ''fix the internal sd card''
Isn't there a way to like factory reset the internal sd card.
Click to expand...
Click to collapse
@cuem,
Unfortunately... If it is an actual dead internal sd card (which it seems to be since the steps you followed already did not seem to fix the issue) the only way to fix it is to send it back to Bell who in turn will send it off for warranty repair.
IF you have just purchased the phone within the last 30 days (possibly 60 if Bell is still extending the DOA return policy) and you have a receipt you can take it back to Bell and get an exchange.
Again, unfortunately these are your only options to get this fixed...
Sorry to be the bearrer of bad news...
Just when I think this couldn't get worst,I was wrong.
I tried using Odin3 One-click downloader, I wanted to flash it with At&t stock firmware( hopefully it would work) then flash it again with 2.1 clair
After using Odin3 One-click downloader, it said sucessed, but now my phone is STUCK on At&t blinking logo and I can't go into download mode anymore.
I've tried the 3 keys combo, adb doesn't reconize the phone.
I'm pretty much screwed,warranty won't work if Bell sees At&T logo blinking upon power up.......
cuem said:
Just when I think this couldn't get worst,I was wrong.
I tried using Odin3 One-click downloader, I wanted to flash it with At&t stock firmware( hopefully it would work) then flash it again with 2.1 clair
After using Odin3 One-click downloader, it said sucessed, but now my phone is STUCK on At&t blinking logo and I can't go into download mode anymore.
I've tried the 3 keys combo, adb doesn't reconize the phone.
I'm pretty much screwed,warranty won't work if Bell sees At&T logo blinking upon power up.......
Click to expand...
Click to collapse
Ooooooo... That is not good. The American Vibrant is NOT the same as out i9000 models.
What you need to do now is search the forums for the homemade jig thread that will force your device into download mode. Search the forums and you will find it.
Be prepared to be "handy" as you will have to build the jig from scratch...
Sent from my GT-I9000M using XDA App
Yeah, I've read about the Jig thing, I've also read about heating your phone with a hairdryer,
I'm currently trying out the hairdryer, but it doesn't work =/
Might have to try the Jig thing, which seems a little complicated with ordering since I'm running out of time =/
Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.
This has happened to me, I just flashed with an older version, for me JM5 worked fine.
cuem said:
Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.
Click to expand...
Click to collapse
I had the same thing after flash and spent many hours and tried many different methods to get it back up with no success.
I'm leaving the country for Europe on January 2nd for vacation. This was the last thing I needed... Hopefully I get it back before then, but I'm not holding my breath.
cuem said:
Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.
Click to expand...
Click to collapse
Well... At the very least at least the firmware is now correct so you can send it away for repair if you need to...
Sent from my GT-I9000M using XDA App
I followed this guide
http://www.tunandroid.com/content/i...du-firmware-i9000xwjpa-pour-samsung-galaxy-s/
I believe now oneclicklagfix is installed on my device, can I flash again or that'll brick my phone, how do I uninstall oneclicklagfix if I can't boot up the phone but only acesss clockwork mod menu?
So just like everyone else i've got a bricked i9000m. So before i send it off to repair (thats if they take it that is), Im sorta curious what fixes have all you out there tried on your phones?
So far i have flashed with odin1.3 to jh2 and now stuck a the "S" boot screen.
Is there a way to get cwm recovery on a phone that dont boot?
patman18 said:
So just like everyone else i've got a bricked i9000m. So before i send it off to repair (thats if they take it that is), Im sorta curious what fixes have all you out there tried on your phones?
So far i have flashed with odin1.3 to jh2 and now stuck a the "S" boot screen.
Is there a way to get cwm recovery on a phone that dont boot?
Click to expand...
Click to collapse
i bricked my phone many times.i flash back to xxjm8 from samfirmwares.com, thats the password aswell you will have to register its free. if it does not work first time try flashinging again.use ordin 1.7 its good.you can get all your updates from ther without getting confussed on the fourm, i have been stuck on that screen many times trying to root my fone on the new 2.2.1 firmware.go to google type xxjpu galaxy root. the is a web site give you xxjpx rooted with voodoo + some cool tools follow all the steps to the letter,if you can print it off its only three pages .
what about adb ? Did tried it ?
a hammer
i flashed back to jh2 after it was in a boot loop from jk4 and then it wouldnt even turn on.. sent back for repair
bobekk said:
what about adb ? Did tried it ?
Click to expand...
Click to collapse
tried it
i can't get the phone to connect. keep getting the stupid "unmounted sd......." crap.
but the funny thing is i can get in to dnl mode reflash with odin, and everything works fine no error codes. But the phone won't boot. keep getting stuck at the s screen
workaround
I've tried everything i can find, i used adb and mounted the card in windows then formatted the card (there is a how to on here for that) but that didn't work. I've tried multiple roms and kernels but i still have the same problem. It seems that my only option is to send it in for warranty. But, if you want to use your phone over the holidays or wait for samsung to come out with an answer before sending your phone in for repair there is a little work around that you can try to get your phone to boot. The phone will be fully functional except that you cannot use the internal SD nor an external SD. Thus, you won't be able to install or save anything to your phone.
to do this workaround just flash the bell froyo rom (there was another froyo rom that i had working but i can't remember which one) then install the voodoo lagfix kernel. When it boots you will hear the "cool voice" state that it is converting it to the ext4 partition and then it will boot into the OS. there will be a program or two that require a "force close" but at least you're phone will work until you can get it repaired. In settings under SD card you'll notice that it says there is no internal or external disk space that's just because you still have the SD corruption and that this is only a work around to get your phone to boot.
I'm curious, for those having this problem and can get into recovery mode, can you report if you're seeing an error msg under the menu and if so, what does it state? Thanks.
Where can you find the official firmware for the i9000m? I had a custom rom installed but my phone decided to brick - jpu worked fine but the minute i upgraded to jpx... Anyway I want to flash the official firmware and take my phone back to bell.
Thanks
I've ran my phone with the original Eclair rom for a couple weeks. I then figured that I couldn't wait for the froyo rom. I've been running the Spike Speedy OC rom, with the JK4 modem and voodoo lagfix. The phone was running just great, very fast. I then changed the lagfix to overkill ext4. Some hours later, the phone hung up. When I rebooted it, it said that the configuration had changed. I saw that one of the options was back to RFS.
What?? It's formatted as ext4. Oh sh*t. Well it didn't boot back up.
I've tried flashing every different firmware I could find. I then tried to re-format the SD manually and found that the partition table was bad.
I've tried to reformat both SD card partitions. The system one (p2) formatted fine, but the "internal SD" (p1) storage one wouldn't format. When I ran fdisk on it, it told me that the partitions didn't end on cylinder boundaries.
Then, I (mistake) flashed a T959 firmware on it. At that point, I wasn't able to get into the download mode using the 3-button combo. Oh shi*... Now I really messed this up. I've managed to get it into download mode using ADB and flash the bell firmware back on it. Oh yeah!! Here we go again.
After the fact that I had installed the T959 and flashed back I9000 firmware, I couldn't find the /dev/block/mmc*** anymore. As if the SD didn't load up.
At that point I inserted a microSD in, and it was recognized as the internal SD. I managed to partition and use that external microSD card just like the internal one and got the phone to boot and work. However, no storage.
All of which I was trying to do while my USB connection was on-and-off, because the usb connector was damaged. It initially had corrosion because my car plug that was kept on the floor of the car, with all the dirt, water and snow. I used alcohol and a tooth brush to clean it, between flashes. As well, flashing it through a VirtualBox VM since I'm on Ubuntu. Sh*t..
This morning I figured I would stop trying, flashed the JH2 firmware on it and brought it to Bell. I tried to get a refund with the argument that this phone is badly designed - with the samsung movinand flash chip - and that it would fail again even if they fix it. It didn't work out for me since I bought the phone about 40 days ago. I was thinking of getting a refund and buy a Nexus S, when a compatible one comes out. It has a different flash chip - a iNand from Sandisk I believe. Oh well. If it fails again, I can still call VISA and give it a try through the purchase protection plan. I have to mention too that I tried calling bell with my concerns - nothing they would do too.
I don't recommend you take my approach. IMO, maybe try, as root, to check the partitions using fdisk /dev/block/mmc(something) and if they appear ok, try to format the SD card using fat.format /dev/block/mmc(something)p1 - but that's it. I'm an experienced linux user, but I'm not a developper. I don't even clearly understand this ODIN flashing stuff. It's like not all firmware you find on the net have the same amount of components inside. I'm thinking stuff from the other flashing is still remaining, not replaced by the later flashes.
I have to say that the next time I'll approach this using fdisk and fat.format only (If I've got a recovery mode working, with root and adb support). Perhaps I will write down the numbers for where the partitions start and end on this SD card when I get my refurbished phone.
Some might say that I had time to spare... I wrote this for you that might be thinking of fixing your 600$ brick yourself.
I have seem to have found the issue and solution to this problem that many of us have been experiencing. If you have encountered issues like myself, there is a thread dedicated to the description of this problem; MAJOR LAG, RANDOM REBOOTS, the phone won't boot up and goes into a screen where you read:
----Mmc_failed failed boot---
After searching for about a month, it seems to be an internal SD issue. Many have reported to having these issues after they root, others upgrading to the non reversible DOK2 FIRMWARE. Others were stock with out root and had this issue as well.
**THE PARTITION OF THE INTERNAL SD CARD IS CORRUPTED**
Could be corrupted files, that stick to the phone EVEN AFTER ODIN FLASHING STOCK MANY TIMES.
(I Odin 5 times back to back to fix and the partition was still corrupted)
People thought "well, if Odin doesn't work, it's a hardware issue" I thought that myself, and it was not.
My friends, I have found something that has worked for me and would like to share with you guys. I hope this fixes your device like it did mine. I've been so close to throwing this Note 4 against the wall, running it over with my car, or smashing it with a hammer. I had no way to return my device as many have suggested to do because I left T-mobile a while back. Plus, rooting my phone voided my warranty. Yada, yada, yada, let's get into it.
*Since the internal partition to the SD card is messing up, we need to repair it.
**In order for this to work, you will need to be ROOTED.
*Download an app called "AParted SD Card Partition." Hope I don't violate any rules, but here is the link to it on Google Play.
https://play.google.com/store/apps/details?id=com.sylkat.AParted
Once the app gains root access, you will be brought to the main screen. Click the tab that says tools. Once that screen pops up, you will see
Part 1 FS: fat32 . Size 31914 MB
Part 2
Part 3
Part 4
Please note that the size to Part 1 may be a different number. That is what mine read.
*You will now click Part 1
*After doing so, at the bottom where it says create, click it and replace it with REPAIR.
*Hit apply, and you're all set.
*Turn off phone, pull battery out for 10 seconds, as well as external SD card and Sim. (They hold small amounts of electric current which may prevent the phone to do a proper boot) I usually hold both volume buttons, power button, home button, and pull the s spen out for 10 seconds simultaneously, then put it all back together and boot up.
*******Also, I used the app to delete the partition, and creating it again to avoid problems from a faulty repair. So if you want to do that, click Part 1. Instead of repair, click delete. Once done, click Part 1 again, then click create. Hit the Fat32, and start it. Once it's created, you shouldn't have issues. In case you're worried, pictures and videos will not be erased.******
I HAVE NO AFFILIATION WITH THE DEVELOPER, BUT HE SAVED MY DEVICE WITH THIS APP. PLEASE, PLEASE, PLEASE DON'T FORGET TO THANK HIM AND HIT THE LIKE BUTTON IF THIS WORKED FOR YOU AS WELL. LEAVE COMMENTS AND QUESTIONS BELOW, AND IF YOU SEE PEOPLE TALKING ABOUT THE PROBLEM IN OTHER THREADS, RE- DIRECT THEM TO THIS THREAD.
This is what I got when repairing the partition. You should have a message as well.
um... if they can't start up the device, how are they going to download it from the play store and install to run it? Thanks!
Are you able to go into DOWNLOAD MODE AND FLASH FIRMWARE? I had the Mmc_failed screen and my phone would not turn on until I took everything out the phone; battery, both cards and s pen, then hold all the buttons down.
Try this to reboot like I described up at top.
Turn the phone off. Pull the battery out, s pen out, SD card and SIM CARD.
PRESS AND HOLD ALL HARDWARE BUTTONS FOR 10 SECONDS WITH EVERYTHING OUT THE PHONE. I CLICK ALL THE BUTTONS SEVERAL TIMES TO GET ANY ELECTRIC CURRENT OUT THE PHONE. IT WON'T BOOT UP IF YOU DON'T DO THAT. I'm assuming it messes with the boot up process. Anyways, Re assemble and boot. When I was having this mmc_failed crap, it would take several times doing these steps so that the phone could boot. Don't get frustrated and try again until it boots up. Sometimes it would sit on the NOTE 4 screen, other times it would boot up to the Android logo with the mmc_failed screen. It takes several attempts since the PARTITIONS TO THE SD CARD ARE CORRUPTED. IF YOU ARE ABLE TO ODIN FLASH FIRMWARE, FLASH THE FIRMWARE TO HELP YOU BOOT UP. FLASH TWRP, THEN ROM, then you will have root.
If you still get the mmc_ boot after repairing it, erase the partition, and create it again. I updated the guide on top on how to do that. Haven't had a single hiccup or Mmc_failed bs since then. Good luck guys.
Please report back if it worked for you.
I will try this as soon as I can. The t-mobile store I went to was unhelpful and only wanted to sell me a new phone, even though I've only had the phone for 1 yr and 1 week. The problems started 2 weeks ago. Thank you for giving me hope.
Sent from my SM-N910T using Tapatalk
mtran1977 said:
I will try this as soon as I can. The t-mobile store I went to was unhelpful and only wanted to sell me a new phone, even though I've only had the phone for 1 yr and 1 week. The problems started 2 weeks ago. Thank you for giving me hope.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
No problem. Save everything important from your sd card and formatt it. That also helps. Try booting up your phone without your sd card. You know what mmc is? An sd card. Google it. Ive seen corrupt sd cards prevent phones from booting up.
Now I can't turn on the phone to fix like you. This morrning I'n in stock DOK2 and have all of error like you. I flash TWRP and flash cook rom, hope can fix like you. But after flash TWRP succesfull, I'm flash cook rom but the phone turn off and can't turn on. when it turn on, it go in to download mode and notice MMcC read fail. I try many time but it still like that. I use odin to load DOK2 Stock firwame but it FAIL. try many time still FAIL
now I don;t know anything need to do to save my phone. lol
What does it fix??
I tried using this application and the first partition that came up was a 61240 Mb partition. I thought it has to be my external SD card. Then i pulled out the external sd card and ran this application again. This time it did not find any partition.
Is this what its suppose to do? If not can you post a screenshot of your partition list.
Thanks
thiennvbk said:
Now I can't turn on the phone to fix like you. This morrning I'n in stock DOK2 and have all of error like you. I flash TWRP and flash cook rom, hope can fix like you. But after flash TWRP succesfull, I'm flash cook rom but the phone turn off and can't turn on. when it turn on, it go in to download mode and notice MMcC read fail. I try many time but it still like that. I use odin to load DOK2 Stock firwame but it FAIL. try many time still FAIL
now I don;t know anything need to do to save my phone. lol
Click to expand...
Click to collapse
After flashing TWRP AND THE COOKED ROM, TURN OFF THE PHONE. TAKE THE BATTERY OUT....SIM CARD OUT...TAKE THE SD CARD OUT AND THE S PEN PUT.
THEN WITH ALL THAT OUT, PRESS AND HOLD POWER FOR 20 SECONDS. THEN TRY TURNING ON THE PHONE. HAD THE SAME ISSUE AND IT TURNED ON AFTER A FEW TRIES.
U may need tp try to do that a few times until you get it to power on.
This is Kinda confusing, we are talking about the INTERNAL STORAGE here, Right? If so, How on earth an App can Format the Internal Storage while its being used obviously by the OS itself? and How can it NOT erase any Media files? It seems very unrealistic approach? unless we boot the system using external boot device then wipe the affected partition, think "Ultimate Boot CD" or "Hiren" for Windows.
What you are saying is like this: Boot Windows laptop/Desktop normally, then Format C: from within Windows !!!
I know you mentioned REPAIR PARTITION, that would/might be OKAY, but to Re-Create the Partition of the MMC (Internal Storage), this sounds crazy, and not even doable.
Please Shed some more lights into this !
It does not fix internal SD
Willy318is said:
This is Kinda confusing, we are talking about the INTERNAL STORAGE here, Right? If so, How on earth an App can Format the Internal Storage while its being used obviously by the OS itself? and How can it NOT erase any Media files? It seems very unrealistic approach? unless we boot the system using external boot device then wipe the affected partition, think "Ultimate Boot CD" or "Hiren" for Windows.
What you are saying is like this: Boot Windows laptop/Desktop normally, then Format C: from within Windows !!!
I know you mentioned REPAIR PARTITION, that would/might be OKAY, but to Re-Create the Partition of the MMC (Internal Storage), this sounds crazy, and not even doable.
Please Shed some more lights into this !
Click to expand...
Click to collapse
If you take out the external SD card, the app does not detect any partition. So this means that we are never fixing the internal memory, just the external one.
rajatkuthiala said:
If you take out the external SD card, the app does not detect any partition. So this means that we are never fixing the internal memory, just the external one.
Click to expand...
Click to collapse
So all of this lengthy post and RED Promises are all BS?
I thought so !
Willy318is said:
So all of this lengthy post and RED Promises are all BS?
I thought so !
Click to expand...
Click to collapse
I am still waiting @notufatjesus to reply.
---------- Post added at 03:09 PM ---------- Previous post was at 02:37 PM ----------
I was wondering, could this issue be related to eMMC like they had on earlier galaxy series. These symptoms are pretty much similar.
created new thread with real solution
Ashwin Prabhunerurkar said:
created new thread with real solution
Click to expand...
Click to collapse
I have the same problem and also hope have a way to repair this error. Now very difficult to use the phone.lol
Mine works fine
@dannygoround
My hopes went up then got nuked as I read the comments lol