Long story short, my windows PC died recently, leaving me without Odin. So, I'm forced to use Heimdall to flash from CM7 back to stock JFD. The only problem is that each guide for Heimdall seems to suggest a different method (What files to use, whether or not to check repartition, etc), and none of them are directly related to the Vibrant (More specifically, flashing from CM7 back to JFD). So, does anyone have experience using Heimdall to get back to JFD?
Sent from my SGH-T959 using XDA App
Bump.
Sent from my SGH-T959 using XDA App
I always use odin3 v1.00, heimdall never worked for me and seems more complicated than odin.
Don't check repartition... it'll reformat your internal sd and you'll lose all your personal data (saved files and such).
Just use Odin like you normally would to go back to stock from any rom. Use the .pit file and .tar of JFD and no repartition.
buru898 said:
I always use odin3 v1.00, heimdall never worked for me and seems more complicated than odin.
Don't check repartition... it'll reformat your internal sd and you'll lose all your personal data.
Click to expand...
Click to collapse
Problem is, I no longer have a Windows PC to use Odin with, so Heimdall's my only option.
Sent from my SGH-T959 using XDA App
Generic112 said:
Long story short, my windows PC died recently, leaving me without Odin. So, I'm forced to use Heimdall to flash from CM7 back to stock JFD. The only problem is that each guide for Heimdall seems to suggest a different method (What files to use, whether or not to check repartition, etc), and none of them are directly related to the Vibrant (More specifically, flashing from CM7 back to JFD). So, does anyone have experience using Heimdall to get back to JFD?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I'm the developer of Heimdall and I just did this exact procedure a couple of days ago as I finally got around to checking out the status CM7. As such Heimdall most certainly works for flashing to CM7 and then back to stock.
When returning back to stock make sure you chose to repartition (i.e. Select a PIT file), then provide all the files that Heimdall Frontend has slots for. The reason you need to repartition is because CM7 does not use the RFS partition format used by stock ROMs. You'll remember that when you installed CM7 you had to do some partition related stuff in recovery mode, what you were doing is repartitioning 3 partitions on the device. Anyway you need to undo that, selecting repartition in Heimdall will do this.
Thanks for the response, and I'll be attempting to flash back later today. Also, do I need to flash bootloaders as well? I just cringe whenever I have to mess with bootloaders...
Sent from my SGH-T959 using XDA App
Generic112 said:
Thanks for the response, and I'll be attempting to flash back later today. Also, do I need to flash bootloaders as well? I just cringe whenever I have to mess with bootloaders...
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
No need to mess with bootloader.
Wow, it feels weird to ask so many questions, but I'd rather be safe than sorry. Just a question to anyone who knows this phone better than me, would the following files, from the JFD tar file and the pit file, suffice for the Heimdall flash:
cache.rfs, dbdata.rfs, factoryfs.rfs, modem.bin, param.lfs, s1_odin_20100512.pit, and zimage.
Basically, that fills up all the spots in Heimdall's GUI, except Primary Bootloader, Secondary Bootloader and Recovery. That seem about right?
Yet another problem I need help solving.... For some reason, after plugging my phone into my computer in download mode, the "Start" button in Heimdall never lights up. I can see the phone using "lsusb", but Heimdall never recognizes it. Any ideas?
Could it be that the device ID (Which is now 18d1:4e22 when fully booted, 04e8:6601 in Download Mode) isn't recognized by Heimdall, or is it something wrong with the Heimdall installation (Or just my computer, since a reinstallation of Heimdall did nothing)?
No the greyed out start button is unrelated to whether or not your device is detected. When you repartition you must include the primary and secondary bootloaders.
Benjamin Dobell said:
No the greyed out start button is unrelated to whether or not your device is detected. When you repartition you must include the primary and secondary bootloaders.
Click to expand...
Click to collapse
Oh wow... didn't know that.
Related
Hello all, I'll give my story chronologically.
1. Installed Clockwork Recovery.
2. Did a nandroid backup. Everything OKAY at this point.
3. Tell Clockwork to partition my SD card.
---- It does its thing, reboots phone into recovery to partition SD, then upon reboot, it will get past initial T-Mobile Spash and Galaxy S splash but will not proceed further (black screen when phone would normally load up).
Figuring I'm ****ed, I try p much everything. Even going back into recovery for some reason brought me back into stock recovery instead of clockwork.
Damn.
4. Installed Odin, flash back to stock, no problems or errors detected during odin-ing process.
5. Phone goes through start-up, same issue.
Whaaa? Please help, as this really sucks. The phone is obviously not bricked, but it might as well be because it's about as useful as... well, it's not very useful in the current state.
Thanks for any help that can you offered.
edit: All my datas are gone. D:
Also, I can get into download mode (obviously) and recovery mode. Here is what I see in recovery mode.
" -- Movi_check Start..!!
checksum confirmation need_checksum[1301305579]
MBR_ChkSum in header : 4.1
MBR checksum : EC0063A432AFDBA2B104C3F0DF52FE3D
MRB Checksum Error
Movinand Checksum Confirmation Fail
-- movi_checking done!...
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC "
Click to expand...
Click to collapse
You need to odin 'eugenes froyo that doesnt brick' first, search for that thread, then odin stock
Sent from my SGH-T959 using XDA App
metalfan78 said:
You need to odin 'eugenes froyo that doesnt brick' first, search for that thread, then odin stock
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yep, that's what you have to do and then make sure NOT to partition your sd card again. Bad things happen with that. As you have seen
Yea, never partition with clockwork. Just out of curiosity why did you partition in the first place
Sent from my SGH-T959 using XDA App
metalfan78 said:
Yea, never partition with clockwork. Just out of curiosity why did you partition in the first place
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
The clockwork app said there was some advantage or another. I can't quite recall anymore.
Anyways, working on following all of the advice now, guys. Thanks a bunch.
ok so here is what you have to do:
1. download odin, froyo that doesn't brick, and 2.1 true stock
2. go to download mode, flash the pit and tar file from the froyo that doesn't brick (DON'T RE-PARTITION!)
3. it will boot into recovery and error out, DONT PANIC, that is what is supposed to happen
4. remove battery (from phone) and usb from phone and computer
5. put battery back in, access odin and download mode
6. flash the pit and tar file from the true 2.1 stock (RE-PARTITION THIS TIME!)
7. if done successfully, your phone software will like when you just took it out of the box!
Thanks. Typing this from eugenes froyo now. I almost do not want t go back to 2.1 now. Haha
edit: does eugene have any fully-functioning 2.1 builds? i really love the stockyness of his froyo. reminds me of when i was playing with the i9000 in korea over the summer and doesn't have all of the disgusting gradients that the tmo builds have.
edit: I think I can deal with the switched volume, non-functioning 3.5mm jack, and no home button. This version of android is what i've always wanted. TMOBILE TAKE NOTE. Haha. Can't wait for this to be bug-free.
Edit again... ok i miss the home button
I have the same exact issue.
Only problem is that the steps explained here do not fix the problem.
Shouldnt this procedure wipe out your internal SD?
Mine is never wiped out. I get to Froyo/ no brick with no issues.
No errors in recovery once I "adb reboot"
Flash back to stock with repartition and back to the same checksum error.
Cant figure out why this wont erase and rebuild the NAND.
Anyone???? Maybe an ADB commant to manually repartition and erase the entire internal SD?????
sknobs said:
I have the same exact issue.
Only problem is that the steps explained here do not fix the problem.
Shouldnt this procedure wipe out your internal SD?
Mine is never wiped out. I get to Froyo/ no brick with no issues.
No errors in recovery once I "adb reboot"
Flash back to stock with repartition and back to the same checksum error.
Cant figure out why this wont erase and rebuild the NAND.
Anyone???? Maybe an ADB commant to manually repartition and erase the entire internal SD?????
Click to expand...
Click to collapse
Did you download the correct "Eugenes Froyo That Does Not Brick"? Its titled exactly that.
Click here for the thread
cthach11 said:
Did you download the correct "Eugenes Froyo That Does Not Brick"? Its titled exactly that.
Click here for the thread
Click to expand...
Click to collapse
Yep, thats the one.
It even saved some of my email settings. I was shocked!!!
I did the adb reboot
It booted and after boot.......ding, you have a new email. Had all my account settings and all.
I have done the odin flash over and over, never erased the nand once?????
metalfan78 said:
You need to odin 'eugenes froyo that doesnt brick' first, search for that thread, then odin stock
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thank you so much for this info...I thought I was going to have a nice paper weight after only 8 days of owning my Vibrant!
Do exactly what this says.
First EUGENE373_SamsungS_Froyo_PDA.tar and s1_odin_20100512.pit
then when phone reboots, use
s1_odin_20100512.pit and Original.tar and and all is good
hi
Did you repair your phone？
where to download the 2.1 true stock
I searched but didnot find
thanks
The Tech Game said:
ok so here is what you have to do:
1. download odin, froyo that doesn't brick, and 2.1 true stock
2. go to download mode, flash the pit and tar file from the froyo that doesn't brick (DON'T RE-PARTITION!)
3. it will boot into recovery and error out, DONT PANIC, that is what is supposed to happen
4. remove battery (from phone) and usb from phone and computer
5. put battery back in, access odin and download mode
6. flash the pit and tar file from the true 2.1 stock (RE-PARTITION THIS TIME!)
7. if done successfully, your phone software will like when you just took it out of the box!
Click to expand...
Click to collapse
said323 said:
where to download the 2.1 true stock
I searched but didnot find
thanks
Click to expand...
Click to collapse
Having the same issue, ended up ODIN with eugene and had a somewhat working phone, just couldnt download anything. Once in Euegne froyo, should I load anything onto SD card (mounting it to computer) or adb push anything somewhere???
After reverting to a stock image Im back where I started
Have tried the following 2.1 tars: JI6 & JFD
I'm able to get back to stock but not sure if its the correct stock rom. I still get the mbr checksum error when rebooting into recovery. If I did the correct rom would the mbr checksum error be done with?
I can't seem to get this to work either.
Tried Eugene a thousand times.
Stock ROM- MBR error in recovery
Only 4 lights at bottom...
Have read about 20 hours of same problem on multiple forums with no avail.
Was it Voodoo Lagfix? How do I remove it or FIX MY INTERNAL PARTITION SIZES?
Do I need to install certain drivers for MacOS X? The Start button won't ungray. I tried to just flash the EC01.tar radio but the start button would not become selectable.
Search for Odin clone. Its an Odin file and Odin clone is for Mac.
Sent from my SCH-I500 using XDA Premium App
Make sure u get phone into download mode before starting heimdall. Also, when flashing the modem I extract the modem.bin file out of the tar and flash it directly...this is how I do it on archlinux and it always works...did it three times in 5 minutes last night...i see no need for odin clone and have actually never had to use odin...but I have no windows computer either so probably why...heimdall is great
Also, like dalev is saying, maybe the tar is made for odin, but the extracted modem.bin works perfect in heimdall...i installed just the EC01 modem with my voodoo'd sc2.9.2 with jt 4/08 kernel...works great
Sent from my SCH-I500 using XDA App
rand4ll said:
Make sure u get phone into download mode before starting heimdall. Also, when flashing the modem I extract the modem.bin file out of the tar and flash it directly...this is how I do it on archlinux and it always works...did it three times in 5 minutes last night...i see no need for odin clone and have actually never had to use odin...but I have no windows computer either so probably why...heimdall is great
Also, like dalev is saying, maybe the tar is made for odin, but the extracted modem.bin works perfect in heimdall...i installed just the EC01 modem with my voodoo'd sc2.9.2 with jt 4/08 kernel...works great
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Absolutely correct, .tar files are for odin and odin clone, but they can be extracted and the .bin are used in heimdall. I don't have much experience with Mac so i was hesitant to say anything other than I know odin clone is for Mac. Thanks for teaching me something new tonite, I had no idea heimdall was Mac compatible.
Almost any simple gtk app can easily be made to work on mac...and any time on the education...the more we all know 2hr better e can help each other out
Sent from my SCH-I500 using XDA App
AuroEdge said:
Do I need to install certain drivers for MacOS X? The Start button won't ungray. I tried to just flash the EC01.tar radio but the start button would not become selectable.
Click to expand...
Click to collapse
Heimdall Frontend has a bunch of simple features built in to stop users doing things that will damage their phone. One example of which is attempting to flash a tar file to your device. Please follow the instructions in the README that came with Heimdall when you downloaded it. They indicate that you must extract the contents of the .tar file and then flash the contents themselves.
I did that but now it's displaying "failed to detect compatible device". I followed the instructions presented in the readme
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?
I have tried to read as many posts on this topic as possible, and I haven't found a proper solution. I've found a few threads where the issue was apparently fixed but they never bothered posting how they did it. If there is a thread that addresses and fixes this issue, my apologies and please redirect me.
First off, I've had my phone rooted since February and it has been working fine. I forget exactly what I rooted with but I have the super user app icon. Last week my Fascinate crashed and re-booted into startup wizard, and all my apps were erased, and I kept getting the force close error boxes. I dont know exactly what caused this but think I might have erased super user when I was going through and deleting apps to free up space. When I reboot everything erases and I go into the start up wizard. My internal memory is 0 and I cannot download any apps. I tried to do factory reset but the data could not be wiped. I tried flashing with odin all the possible .tar packages out there and they all get stuck on the movinand.bin file and fails. I've tried flashing in heimdall but couldnt get it to reboot at all. I've booted into cwm, and every time I try to factory reset/wipe data i get the "error mounting data!" message. I know there's definitely a memory problem and a data problem that has been consistent, and everything I've tried can't get around it.
My current temporary fix has been installing the cyanogen mod, which allows me to use the basic phone functions without the force close boxes. I still have the memory issue and cannot receive text messages, and my network settings are deleted when I reboot. Again, I've read quite a bit of threads on this topic and there seems to be a consensus that I might need the original.mbr and stock.zip files, which I tried downloading from that link everyone posts and they dont work. CWM says the .zip file is bad. Also, the link is like 2 years old as well as most of the threads on this topic, and I havent found anything recent. I've also read about using adb shell to address the issue in the HOW TO guide, and it seems i really need those files. Sorry this was long, I just want to make sure I'm not repeating something that has already been addressed and fixed. Please help. Thanks.
JSlice said:
I have tried to read as many posts on this topic as possible, and I haven't found a proper solution. I've found a few threads where the issue was apparently fixed but they never bothered posting how they did it. If there is a thread that addresses and fixes this issue, my apologies and please redirect me.
First off, I've had my phone rooted since February and it has been working fine. I forget exactly what I rooted with but I have the super user app icon. Last week my Fascinate crashed and re-booted into startup wizard, and all my apps were erased, and I kept getting the force close error boxes. I dont know exactly what caused this but think I might have erased super user when I was going through and deleting apps to free up space. When I reboot everything erases and I go into the start up wizard. My internal memory is 0 and I cannot download any apps. I tried to do factory reset but the data could not be wiped. I tried flashing with odin all the possible .tar packages out there and they all get stuck on the movinand.bin file and fails. I've tried flashing in heimdall but couldnt get it to reboot at all. I've booted into cwm, and every time I try to factory reset/wipe data i get the "error mounting data!" message. I know there's definitely a memory problem and a data problem that has been consistent, and everything I've tried can't get around it.
My current temporary fix has been installing the cyanogen mod, which allows me to use the basic phone functions without the force close boxes. I still have the memory issue and cannot receive text messages, and my network settings are deleted when I reboot. Again, I've read quite a bit of threads on this topic and there seems to be a consensus that I might need the original.mbr and stock.zip files, which I tried downloading from that link everyone posts and they dont work. CWM says the .zip file is bad. Also, the link is like 2 years old as well as most of the threads on this topic, and I havent found anything recent. I've also read about using adb shell to address the issue in the HOW TO guide, and it seems i really need those files. Sorry this was long, I just want to make sure I'm not repeating something that has already been addressed and fixed. Please help. Thanks.
Click to expand...
Click to collapse
Is your sdcard broke? Try another if you have...
Use this guide! http://forum.xda-developers.com/showthread.php?p=17050028 you'd want section 2....Use Odin and follow the directions to a tee. You want to restore...so use how to flash eh03
DROID DOES, Apple did...like I forgot when
I don't think my sd card is broken, as I can still save files and music to it. That is how I was able to install cyanogen mod - I did it through clockwork recovery and then install from .zip. Could there still be something wrong with it?
Also, are you absolutely sure I'll be able to flash the eh03 in Odin without it getting stuck on "movinand.bin" ? Every .tar file I've tried so far has had that happen.
JSlice said:
I don't think my sd card is broken, as I can still save files and music to it. That is how I was able to install cyanogen mod - I did it through clockwork recovery and then install from .zip. Could there still be something wrong with it?
Also, are you absolutely sure I'll be able to flash the eh03 in Odin without it getting stuck on "movinand.bin" ? Every .tar file I've tried so far has had that happen.
Click to expand...
Click to collapse
when using Odin, try different USB port, different USB cable, be sure battery is out..
Also, are you using Odin to flash a stock tar? you should be, and if so are you using the v2.2 pit with the repartition box checked?
See also, droidstyles guide in the fascinate general section
Sent from my SCH-I500 using xda premium
neh4pres said:
when using Odin, try different USB port, different USB cable, be sure battery is out..
Also, are you using Odin to flash a stock tar? *you should be, and if so are you using the v2.2 pit with the repartition box checked?*
See also, droidstyles guide in the fascinate general section
Click to expand...
Click to collapse
I've used all my USB ports and 2 different cables, including the one that came with my phone
Here are all the files I've tried:
CI500_VZW_ED05_FROYO_REL.tar
CI500_VZW_EH03_GB_CM.tar
eh03_full_odin.tar
DI01package3.tar
stock_kernel.tar
I'm also using atlas_v2.2.pit
All of the .tar files get stuck at movinand.bin for about half an hour then it fails. I've tried checking and unchecking the re-partition box with the same result.
Pixelation also recommended the droidstyle guide, I was just afraid of running into the same issue with the movinand.bin file. I've found numerous other threads about people having this same problem and never found a clear solution. I think one person was able to get it fixed with help from adrynalyne, but it was through IRC, so it was never posted in the thread. Any other ideas on what I should try?
Cloyne venlyt
Update: Trying Section 2 of droidstyle's guide. Currently stuck at 99% on movinand.bin, trying to flash the PowerWashed 2.3.4 eh09 rom
ahhhhh!!!! Why, God?
I really don't know. Besides glitched usb drivers on the computer.. Did you try setting up drivers for the fascinate on another pc yet? There is always unbrickable mod if no other fix works
Sent from my SCH-I500 using xda premium
I've tried it on another computer and it still hangs on movinand.bin. It's definitely not a computer issue, since I rooted the phone in February just fine. I think something must have happened when I accidentally deleted the superuser app last week. The only files that I've been able to flash successfully are atlas_v2.2, cwm4-bml-i500, and cwm3_voodoo.tar. Then from clockwork I can install cyanogen from the sd card so I sort of have a working phone. What's the unbrickable mod?
JSlice said:
I've tried it on another computer and it still hangs on movinand.bin. It's definitely not a computer issue, since I rooted the phone in February just fine. I think something must have happened when I accidentally deleted the superuser app last week. The only files that I've been able to flash successfully are atlas_v2.2, cwm4-bml-i500, and cwm3_voodoo.tar. Then from clockwork I can install cyanogen from the sd card so I sort of have a working phone. What's the unbrickable mod?
Click to expand...
Click to collapse
Well, first you don't flash the atlasv2.2pit. that file is a partition map. It repartitions the phone when combined with a factory image. when doing so you need to have the repartition box checked.
The unbrickable mod by adam outler is a hardware mod that allows you to recover from a brick. Google it.
Sent from my SCH-I500 using xda premium
As some possible help, Have you tried sixstringsg one click. Not sure if it re-partitions but here's the link! EH03 Heimdall One-Click
Also you say the tar's are failing at 99%, have you tried flashing them individually? IE: extract the tar and use the following!
Code:
heimdall flash --repartition --pit atlas_v2.2.2.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --primary-boot boot.bin --secondary-boot Sbl.bin --param param.lfs --kernel zImage --modem modem.bin --recovery recovery.bin
neh4pres said:
Well, first you don't flash the atlasv2.2pit. that file is a partition map. It repartitions the phone when combined with a factory image. when doing so you need to have the repartition box checked.
The unbrickable mod by adam outler is a hardware mod that allows you to recover from a brick. Google it.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Oops sorry, I didnt actually flash the atlas.pit file. I meant the only files I got to PASS in Odin were the ones mentioned. The unbrickable mod looks way to complicated, and I dont feel comfortable taking apart my phone and soldering it.
What do you know about unbricking via adb? I just installed it yesterday so I dont know all the shell commands. If my phone can't wipe or mount data, i cant get past this damn movinand.bin in odin, and my internal memory is zero - is there a folder i need to go in and delete in adb that is preventing me from flashing in odin? Can't I just delete all data so I'm free to flash anything? It seems like something is still present in my phone to be showing 0 internal memory and not letting me wipe data that needs to be removed.
JSlice said:
Oops, sorry man , I didnt actually flash the atlas.pit file. I meant the only files I got to PASS in Odin were the ones mentioned. The unbrickable mod you mentioned requires that I need to take the phone apart and solder the hardware, is that correct? If that's the case, then I'll go ahead and cross that out as a possible solution.
What do you know about unbricking via adb? I just installed it yesterday so I dont know all the shell commands. If I my phone can't wipe or mount data, i cant get past this damn movinand.bin in odin, and my internal memory is zero - is there a folder i need to go in and delete in adb that is preventing me from flashing in odin? Can't I just delete all data so I'm free to flash anything? It seems like something is still present in my phone to be showing 0 internal memory and not letting me wipe data that needs to be removed.
Click to expand...
Click to collapse
I'm just a user, I think your looking for a 1337 mofo.
I think you need to get familiar with irc, and contact the overlords
Sent from my SCH-I500 using xda premium
I seriously doubt that all this was caused by deleting Superuser. You likely have a corrupt filesystem. Have a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1705257
Hello all,
I'm hoping someone can advise me with the following problem. I bought a unlocked S3 in Belgium (no branding, network locks etc), and the other day I noticed the latest firmware I9300XXBLFB on http://forum.xda-developers.com/showthread.php?t=1646610
As I use OSX I found out that I needed to use Heimdall to flash it.
I download the ROM, unzipped it, then I renamed the tar.md5 to .tar extracted that which gave me the following files:
boot.img
cache.img
hidden.img
modem.bin
recovery.img
system.img
Now the problem began with the PIT... I required one, and stupidly went off to google in search of an S3 .pit file.... which I found
So I selected the .pit, added the files to their relevant partition, and flashed....
Upon rebooting the phone had updated, however there was no factory reset, everything I had previously was there (to my surprise), but the system info showed the correct rom, baseband, blah blah.
Yesterday I noticed I could not access any internet services. Say I open GMail app, and tried to open a mail, it closed the app after a number of seconds (without displaying the mail contents btw).... no error, just back to the main screen.
I also had problems using 3G or WiFi... nether was stable.
So I reflashed yesterday evening.. at which point I found out how to read in my own .pit file off the phone... but of course I've flashed someone else's previously. I did an MD5 sum on the one I extracted off my phone, and also on the one I downloaded off the net and they still matched.
Still I had the same problems, so I thought perhaps I should drop down a ROM version.
I grabbed a zip file with I9300XXALF2_I9300OXAALF2_I9300XXLF2_HOME.tar.md5 and proceeded to flash it.
Now the phone won't fully boot, it just sits in the Samsung animation and the blue LED pulsing.
I'm guessing I've stuffed up the PIT... the big question is now, what the hell should I do.
FYI I can still get to recovery mode and Odin mode.
Any help / advice would be really appreciated guys.
All the best and thanks in a advance
PS: I just this minute reflashed using Heimdall the I9300XXBLFB. Now it boots up, on first boot it said Updating Android optimsing applications 1/65 and proceeded thru to the point it asks me which language I want... this normal??
kuntstubble said:
Hello all,
I'm hoping someone can advise me with the following problem. I bought a unlocked S3 in Belgium (no branding, network locks etc), and the other day I noticed the latest firmware I9300XXBLFB on http://forum.xda-developers.com/showthread.php?t=1646610
As I use OSX I found out that I needed to use Heimdall to flash it.
I download the ROM, unzipped it, then I renamed the tar.md5 to .tar extracted that which gave me the following files:
boot.img
cache.img
hidden.img
modem.bin
recovery.img
system.img
Now the problem began with the PIT... I required one, and stupidly went off to google in search of an S3 .pit file.... which I found
So I selected the .pit, added the files to their relevant partition, and flashed....
Upon rebooting the phone had updated, however there was no factory reset, everything I had previously was there (to my surprise), but the system info showed the correct rom, baseband, blah blah.
Yesterday I noticed I could not access any internet services. Say I open GMail app, and tried to open a mail, it closed the app after a number of seconds (without displaying the mail contents btw).... no error, just back to the main screen.
I also had problems using 3G or WiFi... nether was stable.
So I reflashed yesterday evening.. at which point I found out how to read in my own .pit file off the phone... but of course I've flashed someone else's previously. I did an MD5 sum on the one I extracted off my phone, and also on the one I downloaded off the net and they still matched.
Still I had the same problems, so I thought perhaps I should drop down a ROM version.
I grabbed a zip file with I9300XXALF2_I9300OXAALF2_I9300XXLF2_HOME.tar.md5 and proceeded to flash it.
Now the phone won't fully boot, it just sits in the Samsung animation and the blue LED pulsing.
I'm guessing I've stuffed up the PIT... the big question is now, what the hell should I do.
FYI I can still get to recovery mode and Odin mode.
Any help / advice would be really appreciated guys.
All the best and thanks in a advance
Click to expand...
Click to collapse
UNZIP THE DOWNLOADED ROM ONCE FROM .RAR TO .TAR/MD5 FILE. AND PUT THE SINGLE .TAR FILE IN PDA SECTION IN ODIN AND FLASH IT. Really, start to read before you do anything
the instructions don;t mention requiring a pit, also, why remane .tar.md5 to .tar when the instructions say "Click PDA and select *.tar.md5". seeing as you can still connect with odin, you onlt have a soft brick and you can still use odin and flash something properly.
gee2012 said:
UNZIP THE DOWNLOADED ROM ONCE FROM .RAR TO .TAR/MD5 FILE. AND PUT THE SINGLE .TAR FILE IN PDA SECTION IN ODIN AND FLASH IT. Really, start to read before you do anything
Click to expand...
Click to collapse
Erm, think you need to read first... I said I use Heimdall because I'm on OSX.
OrbNRG said:
the instructions don;t mention requiring a pit, also, why remane .tar.md5 to .tar when the instructions say "Click PDA and select *.tar.md5". seeing as you can still connect with odin, you onlt have a soft brick and you can still use odin and flash something properly.
Click to expand...
Click to collapse
Once again, I'm using Heimdall not Odin. I'm on OSX not Windows.
Secondly the tar.md5 file is a tar file containing all the components that make the ROM.
kuntstubble said:
Erm, think you need to read first... I said I use Heimdall because I'm on OSX.
Click to expand...
Click to collapse
Oke, my bad. I don`t use heimdal so can`t help you.
Go to recovery (power on with pressing VOL-UP + HOME + POWER when the phone is off) and do a factory reset / wipe data.
This wasn't caused by using a .PIT, though: never use a .PIT ever again, never ever.
HellcatDroid said:
Go to recovery (power on with pressing VOL-UP + HOME + POWER when the phone is off) and do a factory reset / wipe data.
This wasn't caused by using a .PIT, though: never use a .PIT ever again, never ever.
Click to expand...
Click to collapse
Done that also, made no difference :-(
I don't care which ROM I recover correctly but I do want to get the phone working LOL
Use a windows pc and stop using mac?
Its really easy to fix your problem via Odin....
U can use usb jig to unbrick ur phone,and in the future,use odin for all the flashing on ur s3..
Sent from my GT-I9300 using xda app-developers app
pedja381 said:
U can use usb jig to unbrick ur phone,and in the future,use odin for all the flashing on ur s3..
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Stupid reply USB Jig does not unbrick a phone .
ODIN how can the OP use Odin and why would you think its better than Heimdall ??? .
jje
OK the phone is running, but it's bizarre ...
Basically I'm connected to my WiFi signal, and Chrome works 100%... but the normal browser does'nt... just hangs, then closes.
GMail if I open it I can see all the mails, if I click on one, it just sits there with the circle going round, then closes, although if I scrolll thru all mails it does load more... very strange.
Seems any default apps that where installed have connection issues... It's really pi**ing me off....
Anyone?
BTW: *#1234# reports:
AP: I9300XXBLFB
CP: I93000XXLFB
CSC: I9300OXABLFB
It doesn't matter if you change .tar.md5 to .tar i always do it to.
What was the name of the pit you flashed?
Hi,
I downloaded GalaxyS3RootMac which contained a file called
s3pit.pit
MD5 (s3pit.pit) = c67ccbe3628793a9f0dba761c15e0896
Thats the one I used ... stupidly ... so I guess I overwrote mine own one...
I had this exact same thing with browser. That was caused eather from wrong csc or that I mistakenly flashed the firmware using phone field in odin and not pda. Try to change your csc to something else using *#272*IMEI#. That wipes the phone.
Tried what you recommend but still same problem
I choose BTC btw
It previously was on KOR
Sent from my GT-I9300 using xda premium
People read the damn topic before posting.
Usb jig is for accessing download mode, which he can do just fine without.
The phone is softbricked, not soft-hardbricked.
I've never used Heimdall but afaik it has caused issues in the past.
Is anyone you know using Windows or can you install Windows as Bootcamp on your Mac?
If so, please try again with Odin, but factoryreset your phone before and after.
Please also confirm you're actually on hardware i9300 or i9300T, not e.g. i9308
Sent from my GT-I9300 using xda premium
d4fseeker said:
People read the damn topic before posting.
Usb jig is for accessing download mode, which he can do just fine without.
The phone is softbricked, not soft-hardbricked.
I've never used Heimdall but afaik it has caused issues in the past.
Is anyone you know using Windows or can you install Windows as Bootcamp on your Mac?
If so, please try again with Odin, but factoryreset your phone before and after.
Please also confirm you're actually on hardware i9300 or i9300T, not e.g. i9308
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hi, well you're completely correct I could go bootcamp although I prefer not to. If all else fails I'll do it that way. Sadly today I can't get my hands on a Windows system to use.
The phone is a Benelux model I believe (bought from Mobistar), under that battery it says i9300 from what I remember.
Cheers for the logical response
I got exactly the same problem as the OP with the S3, a Macbook Air on Lion, and Heimdall yesterday. I was frustrated but ended up trying Odin on a Windows 7 virtual machine to re-flash a stock firmware. It went through perfectly and I was saved.