Samsung i500 Fascinate internal memory zero (0 bytes) NEED HELP!!! - Fascinate Q&A, Help & Troubleshooting

I have Fascinate with 0.00b internal memory. I think this problem because voodoo lagfix.
I've just tried to flashing DI01 firmware using odin,and always stuck at movinand.bin
So i tried to flashing Reliance Mobile EH18 and that's worked! but my internal memory still 0.00b (zero) the system working well,but the problem i can't install any program cause zero internal memory. I've just root my phone using 1-click root (but cwm are not)
About my phone
Hardware version
I500.04
Model number
SCH-I500
Firmware Version
2.2.2
Baseband version
S:i500.04 V.EH18
Kernel version
2.6.32.9
Build number
SCH-I500.EH19
I have seen this tread {FIXED} 0.00 internal storage problem and [HOWTO] Completely Remove Voodoo Lagfix
but my problem is i can't get the file original.mbr and stock kernel i needed that file,if you have that please PM or share to me
How can i do to unbrick this internal memory?
Please help me and give me advice what should i do to make this phone fixed....i am still loving this phone so much..
Thanks,XDA-developers

please,need help somebody if still have file original.mbr and stock kernel...please share it or send me PM

Uppppp...need somebody to help

Can you get into cwm recovery? If you can, try flashing this http://db.tt/KpUGnoOZ before flashing the rom of your choosing.
Sent from my SCH-I500 using xda premium

Have you tried this thread?
How To Recover Your Fascinate From Any Brick, And Rooting Methods
If you get ODIN to complete *successfully* you'll probably be good. If it won't complete, you might have to repartition using the atlas_2.2 PIT file.
The tar download links in the above thread are no good, but I've personally used the EH03 ODIN from this thread with success:
(full tar package/radio)(EH03){odin/heimdall} Verizon 2.3.5 TWGB (cwr ver as well)

Did you install a Voodoo kernel? Then switched to a non-Voodoo one??
I suggest you use ODIN and flash a full image (EH03 is good) and also use the atlas .pit file and make sure repartition is checked!
Good luck..

Related

[Q] Samsung vibrant Errors(odin problems)

First of all im new to xda and i wanna say thanks to all u guys out there that put in so much work to help those like me who mess up phones.
So i decided to root my phone an apply axura 205 and it work pefectly. Then i tried to apply the VooDoo lagfix and my phone said it was complete an then it booted into recovery mode an everytime i boot it it goes into recovery.
So then i ran odin wit the tar file an the 512 pit file. An now when its installing my phone says wipe failed. It restarts angoes to the samsung galaxy s logo then black. So now im stuck. Can anyone help please
What are you trying to flash with ODIN? I suggest flashing JFD and not clicking the repartion option. If that doesn't work flash Eugenes Froyo that does not brick then JFD.
Also there is a good chance you will get flamed for posting in the wrong section. [Q] belongs in the q&a section. Welcome to XDA.
T959UVJFD i put that on the pda tab. Now it that flash on xda? An will that work for the t mobile version vibrant
That's Tmo's official firmware that came with your phone. Just make sure you also load the 512 pit file.
still not working
im know how to run it but my problem is when its running odin my phone say wipe data failed so i dont know what to do. So the what does the phone tap and the csc tab do?
ttaylorllc said:
im know how to run it but my problem is when its running odin my phone say wipe data failed so i dont know what to do. So the what does the phone tap and the csc tab do?
Click to expand...
Click to collapse
Sounds to me like you have an issue with voodoo. You're going to have to use Eugenes froyo that does not brick first.
Make sure and pull the sd card and sim before odin, it never works for me if I don't do that first.
Sent from my SGH-T959 using XDA App

[Q]After reverting from... 5 bucks over paypal to the one who solves my problem.

After Reverting from the gingerbread, I used odin to flash JFD ODIN
http://forum.xda-developers.com/showthread.php?t=734475
and now when it boots up it shows t-mobile and then galaxy s then it shows nothing on the screen and the 4 buttons stay lit up!
Can someone please help, I'd appreciate it was a gift from my gf and I really hope its not bricked a few days after I got it.
You might want to check your files for Odin then try to odin again or just try to get into recovery and flash another rom
Find yourself a 2.1 kernal and flash that. You probably still have a 2.2 kernal on the phone.
Well when I get into recovery How do I flash a rom... I cant stick any files onto my phones memory and it doesnt detect my external sdcard file named update.zip.
Is there a way to transfer files onto the phone without boooting it.
If you have a sd card reader you can put that in your pc and download a rom on it but I'm not sure how you would copy it onto the internal sd I surprised you don't already have a 2.2 rom on there but there are a couple of roms on the team whisky website that can be loaded with odin you could try one of those
http://www.teamwhiskey.com/
Edit: this man could be correct but I flashed gb from sombionix I had voodoo enabled and used odin to jfd and didn't have this problem but he might be right
you didnt disable voodoo... download eugenes froyo that doesnt brick flash it through odin and then flash back to whatever you want
I had the same problem using JFD Odin ROM. It worked for me when i used JI4 ROM.
jdeleon said:
you didnt disable voodoo... download eugenes froyo that doesnt brick flash it through odin and then flash back to whatever you want
Click to expand...
Click to collapse
This is the correct answer. I always do this and it solves all problems since it comoletely wipes, but after eugenes I then odin jfd and then I start the flashing again.
By the way, you can send him his 5 bucks now.

***READ THIS!!!!!!*** Going from CM7/MIUI/OMFGB to another rom/Unbricking your device

I figured I would put this out there for those who have flashed or are thinking of flashing CM7/MIUI/OMFGB/OMGB or any mtd rom for that matter. If you have flashed one of the aforementioned roms, then you will need to use odin if/when you choose to go to another non-mtd rom. But, you cannot simply use any odin file and there is a particular procedure that is needed to execute this correctly. *Note* This method will also work to unbrick your device from pretty much anything. ***PERFORM ALL OF THE FOLLOWING STEPS WITH THE BATTERY IN YOUR PHONE, DO NOT REMOVE BATTERY***
STEP 1. Open odin (http://www.mediafire.com/download.php?73ta726ghelw381) and place the linked file below in the "PDA" section and WAIT. You will need 7zip or the like to extract the tar image from the zip file below. This particular type of odin file is the only kind that I know of that contains the proper bootloaders to re-partition your phone. ONLY THE PDA SECTION!!!!
Link removed. My dropbox account was suspended due to excessive traffic. I'll figure out another place to upload and then post the link.
STEP 2. Then, place this file in the "PIT" section in odin and WAIT.
http://dl.dropbox.com/u/20070269/atlas_v2.3.pit <---*Atlas_v2.3 Re-partitioning "PIT" file*
STEP 3. And place a check in the "Re-partition" box in odin.
STEP 4. At this point you need to power off your phone. Then, enter download mode by holding the volume down button and continuing to hold it while you plug the cable into your phone, you should then see a yellow "downloading" screen popup. If/when this happens, go to step 5.
STEP 5. When you have done the first 4 STEPS, THEN hit the "START" button in odin and wait about 5-10 minutes until you see the green "PASS" in odin and profit. ***You must allow the phone to boot fully one time after running this odin process so that it can wipe the phone and complete the the re-partitioning.*** However, when the phone boots, you will be on stock, binged, bloated, unrooted TouchWiz. So odin a recovery and remedy that situation quickly!!! And just in case there are any misconceptions, you do NOT need to be rooted to install a custom cwm recovery.tar file with odin. So unless you plan on staying stock, you don't need to root again because any rom you flash will already be rooted. So just odin a recovery and boot immediately into the recovery via the 3 finger method (holding both volume up and down buttons and the power button at the same time and continue to hold them until you see the samsung logo). YOU MUST DO IT THIS WAY BEFORE THE PHONES BOOTS UP NORMALLY OR YOU WILL LOSE THE RECOVERY THAT YOU JUST ODINED! Then, as good practice, follow the instructions of the next paragraph.
And as a good suggestion, if you want voodoo converted partitions (in others words, if you want to flash a voodoo kernel) after odin does it's thing, flash this package (courtesy of navenedrob) from cwm recovery 3x before flashing whatever rom in conjunction with a voodoo kernel you were wanting to flash after coming from CM7 MTD/GB MIUI. Here is the link, flash this if you want voodoo partitions (ext4): http://dl.dropbox.com/u/20070269/ext4_formatter_all.zip . This will help to insure that you obtain a clean install of whatever rom/voodoo kernel you are flashing after coming from CM7 MTD/GB MIUI ***If you flash the Ext4 package, you must flash a voodoo kernel afterwards or you will have another brick.***
It is absolutely mandatory that you follow these steps exactly to properly get off of CM7 MTD/GB MIUI so that you can flash another rom. Attempting another method or not following these steps implicitly will result in eventual problems down the line and/or a bricked phone and you will have to follow this guide to fix it.
Thanks for the info.
Sent from my SCH-I500 using Tapatalk
kidserious said:
I figured I would put this out there for those who have flashed CM7 MTD or GB MIUI. If you have flashed jt's new CM7 MTD or andmer's AOSP GB MIUI, then you will need to use odin if/when you choose to go to another rom. But, you cannot simply use any odin file and there is a particular procedure that is needed to execute this correctly:
Open odin (http://download1422.mediafire.com/ii578172dylg/429fcpdtpckkcea/Odin3+v1.83.exe) and place one of "ONLY" these two files in the "PDA" section: These are the only odin files that contain the proper bootloaders to re-partition your phone. ONLY THE PDA SECTION!!!!
http://adbdev.com/danknub/CI500_VZW_EB01_FROYO_REL.tar.md5
http://adrynalyne.us/files/stuff/CI500_VZW_DL09_ECLAIR.tar.md5
Then place this file in the "PIT" section in odin:
http://download248.mediafire.com/z5q4aw8ablig/26xbh796jmwvwqb/atlas_v2.2.pit
And place a check in the "Re-partition" box in odin.
When you have done all of these things, hit the "START" button in odin and wait about 10 minutes until you see the green "PASS" in odin and profit.
It is absolutely mandatory that you follow these steps exactly to properly get off of CM7 MTD/GB MIUI so that you can flash another rom. Attempting another method or not following these steps implicitly will result in a bricked phone and you will have to follow this guide to fix it.
Click to expand...
Click to collapse
I will have to give this a try since I just chewed out Big Red for screwing up my phone with their ED04 OTA, wich I odin'd back to stock from JT's CM7 to get it.
I vote for a sticky
Sent from my SCH-I500 using XDA Premium App
Moved to the development section and temporarily stuck for now.
yep big +1
If you do all this and Odin hangs or something else fails to work, make sure you are using an OEM data/charge cord to do this. I did this exact beautiful brick a month ago was stuck believing for a good 8 hours that I had done it this time, because I was using a data/chord that was supposed to be an upgrade from the OEM chord. Fun times
kidserious said:
I figured I would put this out there for those who have flashed CM7 MTD or GB MIUI. If you have flashed jt's new CM7 MTD or andmer's AOSP GB MIUI, then you will need to use odin if/when you choose to go to another rom. But, you cannot simply use any odin file and there is a particular procedure that is needed to execute this correctly:
Open odin (http://download1422.mediafire.com/ii578172dylg/429fcpdtpckkcea/Odin3+v1.83.exe) and place one of "ONLY" these two files in the "PDA" section: These are the only odin files that contain the proper bootloaders to re-partition your phone. ONLY THE PDA SECTION!!!!
http://adbdev.com/danknub/CI500_VZW_EB01_FROYO_REL.tar.md5
http://adrynalyne.us/files/stuff/CI500_VZW_DL09_ECLAIR.tar.md5
Then place this file in the "PIT" section in odin:
http://download248.mediafire.com/z5q4aw8ablig/26xbh796jmwvwqb/atlas_v2.2.pit
And place a check in the "Re-partition" box in odin.
When you have done all of these things, hit the "START" button in odin and wait about 10 minutes until you see the green "PASS" in odin and profit.
It is absolutely mandatory that you follow these steps exactly to properly get off of CM7 MTD/GB MIUI so that you can flash another rom. Attempting another method or not following these steps implicitly will result in a bricked phone and you will have to follow this guide to fix it.
Click to expand...
Click to collapse
Bro, just a thought...But for people who follow these steps and STILL get issues, like force closes, the phone not saving your contacts or settings, etc. Then go to http://forum.xda-developers.com/showthread.php?t=1090127&highlight=ext4+formatter. Most of us, I think, use ext4, but RFS is the default for Samsung phones. Ext4 is what VooDoo converts your file systems to. Download the file system .zip of your choice, flash it in CWM, then re-flash your ROM, kernel, theme, etc. and it should fix your issues. I had many issues, this killed them all.
I am pretty sure the atlas file is not required if you are using the dl09 package. At least I was able to revert just fine without it.
solido888 said:
I am pretty sure the atlas file is not required if you are using the dl09 package. At least I was able to revert just fine without it.
Click to expand...
Click to collapse
you are correct, if you odin dl09 with the atlas 2.2 pit, it will only boot to recovery.
Copperhed said:
you are correct, if you odin dl09 with the atlas 2.2 pit, it will only boot to recovery.
Click to expand...
Click to collapse
This isn't true. I have odined with DL09 and 2.2 pit file and repartition checked many times and it causes the phone to boot normally to stock. I have actually done it with both files many times. They both work just as I wrote it, at least for me and everyone else that I know.
kidserious said:
This isn't true. I have odined with DL09 and 2.2 pit file and repartition checked many times and it causes the phone to boot normally to stock. I have actually done it with both files many times. They both work just as I wrote it, at least for me and everyone else that I know.
Click to expand...
Click to collapse
TRUE !!
even i have positive experience of using both these files .. either one works with the 2.2 pit file and i didnt loose root either !
Copperhed said:
you are correct, if you odin dl09 with the atlas 2.2 pit, it will only boot to recovery.
Click to expand...
Click to collapse
You HAVE to let it boot into stock recovery once after flashing the full Odin. Stock recovery needs to do an automatic data wipe before it boots into the OS. Which is why if you were to flash cwm right after flashing the full Odin, you'd get the datadata/dbdata issues.
Sent from my SCH-I500 using XDA App
krispuniq said:
TRUE !!
even i have positive experience of using both these files .. either one works with the 2.2 pit file and i didnt loose root either !
Click to expand...
Click to collapse
Wow, I don't know how you didn't lose root seeing as how neither one of those Odin packages are rooted and it does a complete data wipe.
Sent from my SCH-I500 using XDA Premium App
Good advice! regarding that ext4 formatting...
kidserious said:
I figured I would put this out there for those who have flashed or are thinking of flashing CM7 MTD or GB MIUI...
[...]
And as a good suggestion, after odin does it's thing, flash one of these two packages (courtesy of navenedrob) from cwm recovery 3x before flashing whatever rom you were wanting to flash after coming from CM7 MTD/GB MIUI. Flash this one: http://forum.xda-developers.com/attachment.php?attachmentid=614756&d=1307095153 if you want voodoo partitions (ext4) or this one: http://forum.xda-developers.com/attachment.php?attachmentid=614757&d=1307095153 if you want nonvoodoo partitions (rfs).This will help to insure that you obtain a clean install of whatever rom you are flashing after coming from CM7 MTD/GB MIUI ***If you flash the Ext4 package, you must flash a voodoo kernel afterwards or you will have another brick.***
[...]
Click to expand...
Click to collapse
This was essentially the process I followed a few days ago when I reluctantly reverted back to touchwiz framework for reliable call operation (CM7 MTD is getting so close).
After letting the DL09 image boot for the first time, I odined Times_Infinity's CM3 and booted straight into it with the intention of running navenedrob's ext4 formatter utility. I immediately heard the familiar scary voodoo lady reporting the lagfix conversion operation, backing up & restoring DL09 system and data files that I had no interest in keeping around, etc. Once it finished and I had TI's CWM on screen, I flashed navenedrob's ext4 utility to reformat.
So, to save some time and an unnecessary format cycle, here's a reminder to create a "/sdcard/voodoo/disable lagfix" file before starting this process .
FWIW, the latest imnuts PBJ kernel has a modified CWM (in yellow) that reportedly incorporates navenedrob's ext4 formatting enhancements, but I've had other issues with that kernel and there's no version to apply via Odin...
kidserious said:
This isn't true. I have odined with DL09 and 2.2 pit file and repartition checked many times and it causes the phone to boot normally to stock. I have actually done it with both files many times. They both work just as I wrote it, at least for me and everyone else that I know.
Click to expand...
Click to collapse
While it may work with those 2 files, the atlas file is not required if using the dl09 tar. I am not a coder, but I believe it may be redundant to use that file with the dl09 tar. Either way, my phone has been fully functional on comrom for the past 3 days now, and I did not use the 2.2 pit file to revert from the 6.09 CM7 build.
solido888 said:
While it may work with those 2 files, the atlas file is not required if using the dl09 tar. I am not a coder, but I believe it may be redundant to use that file with the dl09 tar. Either way, my phone has been fully functional on comrom for the past 3 days now, and I did not use the 2.2 pit file to revert from the 6.09 CM7 build.
Click to expand...
Click to collapse
I hear you and that may be true, but it is just safer to post it the way I did.
solido888 said:
While it may work with those 2 files, the atlas file is not required if using the dl09 tar. I am not a coder, but I believe it may be redundant to use that file with the dl09 tar. Either way, my phone has been fully functional on comrom for the past 3 days now, and I did not use the 2.2 pit file to revert from the 6.09 CM7 build.
Click to expand...
Click to collapse
The atlas_v2.2.pit is required for repartitioning. Which is mandatory for coming off of MTD.
Sent from my SCH-I500 using XDA App
times_infinity said:
The atlas_v2.2.pit is required for repartitioning. Which is mandatory for coming off of MTD.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
What problems should I be anticipating since I didn't use it? I haven't had any problems yet.
Edit: I am under the impression the DL09 tar repartitioned for me.
kidserious said:
This isn't true. I have odined with DL09 and 2.2 pit file and repartition checked many times and it causes the phone to boot normally to stock. I have actually done it with both files many times. They both work just as I wrote it, at least for me and everyone else that I know.
Click to expand...
Click to collapse
+++++++1. I have used the DL09 file plus the atlas 2.2 pit file many times. It's the best thing for a good, clean, fresh start to build from. If you aren't using the PIT file, you aren't restoring your partitions back to where they need to be.
landshark68 said:
+++++++1. I have used the DL09 file plus the atlas 2.2 pit file many times. It's the best thing for a good, clean, fresh start to build from. If you aren't using the PIT file, you aren't restoring your partitions back to where they need to be.
Click to expand...
Click to collapse
And I'll reiterate, what problems will I be experiencing? Since I haven't had any yet?

[Q] Help! 0.00 internal memory and can't mount SD Card in CWM

I am completely stuck trying to get my Fascinate back to stock and i have read through and tried everything i have seen on the issue execpt the How to completely remove voodoo lagfix because I cannot down load the original.mbr file.
Let me see if I can sum up the issues I am having on my phone;
I mistakenly flashing I9000 which led to a soft bricked phone. Since then I have spent the past seven days researching and trying to figure out how to get it fixed.
Phone shows 0.00 internal memory
Can't mount SD Card in CWM3-Voodoo-Blue E: Unable to mount sdcard so i can't install update.zip or even install a new kernel
Permission denied ... E: Can't mount /dev/block/mmcblk0p1
While I don't remember flashing a voodoo kernel using Odin, I am getting all of the same errors. I can't get CWM to do anything with the SD Card
Phone stats:
Firmware 2.2.1
Baseband version S:i500.04 V.EB01
Kernel version 2.6.32.9
Build number SCH.I500.EB01
I can only get the following to run on my phone, EC10SC292x_DXC.tar.md5 from Droid Forums (Super Clean version 2.9.2 - EB01/EC10 Froyo leak root+Froyo Clockworkmod with MALWARE protection).
This runs great except for the 0.00 memory and unable to mount SD card errors in CWM recovery.
I have tried everything out there with no luck to include flashing back to stock using the threads on this site and others and Odin gets stuck at the movinand file install and fails. Everything except the thread How to completely remove Voodoo Lagfix over.
The link for the orginal.mbr is broken and I can't find the file anywhere.
Does anyone have the original.mbr file they could post for download.
Odin back to stock ED05 using the pit file and repartition. If that isn't enough Odin back to DI01 using the pit to repartition.
Sent from my SCH-I500 using XDA App
Trying now, waiting for download. The thread for Installing ROM/CWM recovery, root, go back to stock oh this site say no need to flash the Pit file sine ED05 already has it. Should I flash it anyway?
peaser1 said:
Trying now, waiting for download. The thread for Installing ROM/CWM recovery, root, go back to stock oh this site say no need to flash the Pit file sine ED05 already has it. Should I flash it anyway?
Click to expand...
Click to collapse
Try it without first, and if that doesn't fix it try it with. Just make sure you have Repartition checked.
Sent from my SCH-I500 using XDA App
Tried both ways with ED05 and DI01 with no luck each time I flash Odin gets stuck on the movinand file install and fails.
Any other suggestions?
peaser1 said:
Tried both ways with ED05 and DI01 with no luck each time I flash Odin gets stuck on the movinand file install and fails.
Any other suggestions?
Click to expand...
Click to collapse
Are you using Odin with the battery pulled? Sometimes that helps. Basically hold the volume down button when plugging in the USB cable and it will still use the download mode. If that doesn't help maybe the download is corrupt so try redownloading.
Sent from my SCH-I500 using XDA App
scarfman4 said:
Are you using Odin with the battery pulled? Sometimes that helps. Basically hold the volume down button when plugging in the USB cable and it will still use the download mode. If that doesn't help maybe the download is corrupt so try redownloading.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Yes, Odin with battery out. at least fourth time re-downloading all the stock files. It seem that the only files that make it through Odin are then custom ROMs. All of the stock downloads fail at the movinand install point.
Have you tried a different USB cable? Also what version of ODIN are you using? The most reliable one I've used is 1.3.
scarfman4 said:
Have you tried a different USB cable? Also what version of ODIN are you using? The most reliable one I've used is 1.3.
Click to expand...
Click to collapse
Yes on the usb cable, 4 to be exact and odin 1.3 and 1.7. 1.3 has been the most stable.
I think i have tried everything across the board and like I said the only files that make it through Odin and pass have been the custom roms, anything that say stock locks up in Odin.
I would try the full GeeWiz Rom then with the pit file with Repartition checked. I'm not sure if it contains the movinand.bin file or not. If not then try GeeWiz with just the Rom & Kernel; that doesn't wipe data.
Also have you tried wiping the SDCard in either CWM or GeeWiz recovery?
If that doesn't help, I'm out of suggestions, and unfortunately I don't have the mbr file so I'm no help there.
scarfman4 said:
I would try the full GeeWiz Rom then with the pit file with Repartition checked. I'm not sure if it contains the movinand.bin file or not. If not then try GeeWiz with just the Rom & Kernel; that doesn't wipe data.
Also have you tried wiping the SDCard in either CWM or GeeWiz recovery?
If that doesn't help, I'm out of suggestions, and unfortunately I don't have the mbr file so I'm no help there.
Click to expand...
Click to collapse
Will try when it gets done downloading, cant do anything with SDcard in CWM as i get the can't mount SDcard, error every time I try to access for restore/update.zip.
Will let you know when i finish downloading.
thanks
peaser1 said:
Will try when it gets done downloading, cant do anything with SDcard in CWM as i get the can't mount SDcard, error every time I try to access for restore/update.zip.
Will let you know when I finish downloading.
thanks
Click to expand...
Click to collapse
First try locked up on the movinand file. downloading the other and will try.
Thanks again for the help.
I had a similar problem. Im not an expert but Re-installing the usb drivers and giving odin a few more tries solved everything for me.
Thanks, seven days of this and I have done each of these more times than I count. Anything with a movinand file locks up.
Wife wants to buy me an Iphone but I am resisting because I really like to the android system and versatility. Will out as long as i can fix this issue.
The only other thing I can think of is taking the sdcard out and trying to put it in a card reader and format it there. Either that or moving it to a different phone and trying to reformat it.
scarfman4 said:
The only other thing I can think of is taking the sdcard out and trying to put it in a card reader and format it there. Either that or moving it to a different phone and trying to reformat it.
Click to expand...
Click to collapse
Have done that also, actually multiple SDcards. Still no joy
peaser1 said:
Have done that also, actually multiple SDcards. Still no joy
Click to expand...
Click to collapse
Try re-flashing Clockwork Recovery in Odin, or even a different copy from Times_Infinity's thread. Perhaps then it will recognize your sd card.
Terminators run on Android
Try flashing Eh03 stock with odin with out pit or repartition.
Just try the image
skynet11 said:
Try re-flashing Clockwork Recovery in Odin, or even a different copy from Times_Infinity's thread. Perhaps then it will recognize your sd card.
have done that as well, mulitple versions of CWM. Will try what on Times_Infinity's thread tonight after work just not holding my breathe based off previous attempts.
Click to expand...
Click to collapse
Tried eh03 stock and multiple cwm and still no go. Still have 0.00 internal memory and no sdcard access in cwm.
I'm out of ideas at this point, any help is greatly appreciated.
Does anyone know where to find the original.mbr file for the fascinate?

[q] q> galaxy s3 (shv-e210k) always stucked @ get pit for mapping

NOTE: I have been also searching in other threads, but as of now, to no avail. Still failed!
After trying to flash in Odin, got stuck in "get pit for mapping". Tried below steps but still no go:
-tried using different original cables
-tried using other computers
-installed proper drivers (checked device manager, and detected by Odin)
-tried using different versions of Odin
Details of my phone:
-SHV-E210K
-4.3 (official, OTA updated)
-baseband - E210KKKND3
-Kernel - 3.0.31 - 2bb039b
-build # - JSS15J.E210KKKUGND3
My phone is NOT bricked, it is usable right now. But I want to gain root access, by flashing CF-Root in Odin. But everytime I flash, it got stuck in "get pit for mapping"
In addition, I have noticed that my device only detects 16GB of internal storage instead of it's original 32GB storage, I have used an app (just can't remember the name) in figuring it out. I believe this is the root cause. Any help/advise would be much appreciated. Thanks in advance!
Well im not sure if this is going to help or not just downgrade to 4.1.2 make a full wipe befire downgrading and then download ota 4.3 and then root using the older methods installing cwm i mean flashing it via odin and then flashing supersu via cwm that'll definitely work and your storage thing check it via cpu-z after downgrading u should have it all good!
paulmuning said:
NOTE: I have been also searching in other threads, but as of now, to no avail. Still failed!
After trying to flash in Odin, got stuck in "get pit for mapping". Tried below steps but still no go:
-tried using different original cables
-tried using other computers
-installed proper drivers (checked device manager, and detected by Odin)
-tried using different versions of Odin
Details of my phone:
-SHV-E210K
-4.3 (official, OTA updated)
-baseband - E210KKKND3
-Kernel - 3.0.31 - 2bb039b
-build # - JSS15J.E210KKKUGND3
My phone is NOT bricked, it is usable right now. But I want to gain root access, by flashing CF-Root in Odin. But everytime I flash, it got stuck in "get pit for mapping"
In addition, I have noticed that my device only detects 16GB of internal storage instead of it's original 32GB storage, I have used an app (just can't remember the name) in figuring it out. I believe this is the root cause. Any help/advise would be much appreciated. Thanks in advance!
Click to expand...
Click to collapse
Sent from my GT-I9300 using Tapatalk
Sulaimanshariff said:
Well im not sure if this is going to help or not just downgrade to 4.1.2 make a full wipe befire downgrading and then download ota 4.3 and then root using the older methods installing cwm i mean flashing it via odin and then flashing supersu via cwm that'll definitely work and your storage thing check it via cpu-z after downgrading u should have it all good!
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Thank you for your prompt response! However just a clarification though, do I still need to downgrade it even I have been in 4.1.2 (when I brought this), then did OTA update to 4.3. Do you think it's just that the OTA update didn't finish completely, so my storage thing is not properly partitioned?
Forgot to mention, I'm afraid that downgrading to 4.1.2 would be possible since even when I try to flash a ROM in Odin, still it get stuck in "pit for mapping".
paulmuning said:
Thank you for your prompt response! However just a clarification though, do I still need to downgrade it even I have been in 4.1.2 (when I brought this), then did OTA update to 4.3. Do you think it's just that the OTA update didn't finish completely, so my storage thing is not properly partitioned?
Click to expand...
Click to collapse
Nope that are the errors youre getting because u flashed it some three or four times via odin to root your device i have a strong feeling that the above stated method can help u out all you can do if u have root acess erase the binary count make a full wipe including internal storage and everything then plug into download mode and flash 4.1.2 via odin once booted check storage if its fine then update to 4.3!
Sent from my GT-I9300 using Tapatalk
Are there any other methods to downgrade this, aside from using Odin?
I'm not sure about the shv-e210k. In Google it appears as south korean model (2gb ram, 29gb internal storage). Maybe you are trying to flash the rom for the international model of S3, i9300 (1gb ram, 16gb i.s.)
Envidado desde mi Note 3.
Atrankas said:
I'm not sure about the shv-e210k. In Google it appears as south korean model (2gb ram, 29gb internal storage). Maybe you are trying to flash the rom for the international model of S3, i9300 (1gb ram, 16gb i.s.)
Envidado desde mi Note 3.
Click to expand...
Click to collapse
Hi. I'm not flashing the ROM, just the CF-autoroot. Even when I flash the official ROM, it still got stuck @ get pit for mapping.
Possible your partition table is corrupt, normally a pit file flashed with a firmware would solve -but no idea if one is available for your model.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Possible your partition table is corrupt, normally a pit file flashed with a firmware would solve -but no idea if one is available for your model.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Hi. Thanks for your response. Is it possible to flash "that firmware with pit file" using Odin or any other methods? Have downloaded a separate "pit file" for this model, flashed it thru Odin, but got an error "re-partition failed". Thanks
Flash the right firmware and right pit for your model together at the same time, if it still fails then normally the emmc chip is damaged.
Sent from my GT-I9300 using Tapatalk

Categories

Resources