EC01 must be old, right? Not so. I cannot give you the build date however, per request of...someone else. Its considerably newer than EC10, however. For some it may be hard to take my word for it, but I have never lied to anyone here.
In here you will find a new shiny radio, a voodoo or non voodoo EC10 kernel, courtesy of JT1134, and...a ROM!
No more hacking pieces together from other devices. No more crappy radios (hopefully). No more poor GPS (hopefully).
Please do not ask where it came from. I will not tell you. All file dates have been changed, the build.prop has been masked.
Please do not ask for an Odin. I will not give you one at this time.
Please enjoy yourself, I insist.
This ROM is ever so slightly tweaked. It is not a quality release by my standards (mostly because its stock). I recommend folks wait for the community rom to be finished. If you can't wait, by all means, flash away.
Does not include a kernel.
Debinged, browser included.
Debloated, yet contains most stock apps.
Custom boot animation, because I am not including the original kernel.
Dialer voicemail button points to Google Voice.
Your current kernel will be retained. So if you are using a Froyo kernel, you will be just fine.
Xoom boot animation because you will be using a custom boot animation supporting kernel.
Installation Instructions (read carefully)
---------------------------------------------------------
Make a nandroid backup.
Odin back to EB01 stock.
http://adbdev.com/danknub/CI500_VZW_EB01_FROYO_REL.tar.md5
Boot once, then Odin clockwork recovery.
http://adbdev.com/danknub/cwm-recovery-ALL-3-30-FIX.tar
Boot straight to clockwork recovery, and flash my kernel of choice from here:
http://forum.xda-developers.com/showthread.php?t=1003017
Boot once, convert to voodoo if need be.
Boot back to clockwork recovery and flash rom.
Boot once, then Odin the radio.
Please follow these directions. There are apparently some kernel/cwr issues that are causing boot loops. If you decide to flash another kernel afterwards, be my guest. Don't wipe, however. The above directions are after hours of testing by IRC folks, and I THANK all of them!!!!!
Radio:
http://adbdev.com/danknub/ec01_radio.tar
Rom:
http://www.multiupload.com/ETEG610SJR
Reserved.
Edify compatible version coming out tomorrow.
<3 your the man
Much thanks man. You're always coming through for us. Thanks for continuing to work on the fascinate.
Sent from my SCH-I500 using XDA App
excellent work man, i new you werent going to give up on us, im gonna have to get the tbolt just so i can continue to use your work. ive been with your roms since my omnia
edit-kernal links are down, both of them.
NM me. I followed your post to a T and I was able to flash a diff kernel then. THanks guys
Great work! Thank you for the work. I'll take your advice and wait for the community rom, but VERY much appreciate your work.
jrobinsky said:
for me, only your kernel works dude. I tried a few other ones after my initial boot and i get stuck on boot loops. IDK about anyone else, but thats my results.
Click to expand...
Click to collapse
I was able to get times_infinity's comavolt voodoo to work, but only if I ODIN'd back to EB01 stock, then ODIN'd ec01 radio, ODIN 03/30 cwm fix, boot directly to recovery, flash ec01 rom, flash comavolt kernel, boot was successful. Going to play with it a bit tomorrow.......errr later today after I get some sleep.
Copied from my "Most Thorough Method of Fixing Every Problem You Might Have" section in the recovery thread, and adapted to this post.
This will wipe your data, btw, so be sure to backup any important info. You can make a nandroid backup, but you will probably have issues if you try to restore the data to use with this ROM.
[SIZE=+2]Bestest Best Way to Install This ROM[/SIZE]
Download to PC
CWM-Recovery 3-30 Odin Package
MD5 Checksum: 00e90e790a70e2d66b6cba6a152de504
ec01_radio.tar Odin Package
MD5 Checksum: 099c7cf67e14fea5c9bbd886a83e48b1
CI500_VZW_EB01_FROYO_REL.tar.md5
MD5 Checksum: d04733ce540ab1af291cfa44d42c768e
atlas_v2.2.pit
MD5 Checksum: a0eaf496375cf72b90f7ceef4f0a4538
Place on /sdcard
ec01_rom.zip
MD5 Checksum: 30849feb8d53b05c611fc9b03263a414
The kernel of your choice
Step-by-Step Installation - Important!
ODIN the full stock EB01 package in PDA, the atlas_v2.2.pit in PIT, and "Re-Partition" checked
Let your phone fully boot into the OS and verify everything is working correctly
Remove your battery
ODIN the CWM Recovery package
Close odin, Unplug/replug the phone from USB, re-enter download mode, Re-open odin.
ODIN the modem
Unplug USB Cable, THEN reinsert your battery
Hold both of the volume keys and the power button down until a second after you see the Samsung boot logo, then let go
It should now boot into red CWM recovery
Wipe Cache only. Flash the ec10_rom.zip
Flash the kernel of your choice
Reboot. If you have installed a voodoo kernel, then you should hear a Sexy Robot lady telling you that she is converting your partitions. This process will take 10 minutes or so. If you pull the battery, you will have to start all over again.
Let your phone fully boot into the OS and verify everything is working correctly
I can't stress enough how important it is to check your files for the correct checksum to verify that your download did not get corrupted (you can also use it as a way to make sure you have the right version). Also, follow these instructions exactly. You could potentially be wasting your time and anyone else's who is trying to help you fix whatever random issue you might be having, merely because you didn't follow the instructions.
I've been scanning threads for news of this mystery drop since your first hint and just as I'm about to cash out for the night... OMFG! You f'ing rock mate! Now, if I can only find the strength to hold out for the community brain child... I know it will be worth the wait. Oh, but a tasty new radio sure sounds delicious right now!
Thanks again Adryn for everything you've done to make this phone great!
Sent from my #@&$ing SCH-I500 using my %!#@ing XDA App
justin94 said:
excellent work man, i new you werent going to give up on us, im gonna have to get the tbolt just so i can continue to use your work. ive been with your roms since my omnia
edit-kernal links are down, both of them.
Click to expand...
Click to collapse
For now you can just get them from the superclean thread. Same ones.
Might be a silly question, but is it safe to odin just the modem and nothing else? I want to hold off on flashing the ROM and kernel.
Sent from my SCH-I500 using XDA App
tripacer99 said:
Might be a silly question, but is it safe to odin just the modem and nothing else? I want to hold off on flashing the ROM and kernel.
Click to expand...
Click to collapse
Yes, I believe it was verified to work just fine.
is there a reason why after i odin in the first step then go to odin recovery ... it just sits on "setup connection..."
lucas.scott said:
is there a reason why after i odin in the first step then go to odin recovery ... it just sits on "setup connection..."
Click to expand...
Click to collapse
Are you using Adrynalyne's steps or GizmoDroid's steps? Did you reboot phone and let it fully boot into OS before powering down to pull battery to start new ODIN session?
of course ... and im no stanger to odin or anything .. new problem for me
lucas.scott said:
of course ... and im no stanger to odin or anything .. new problem for me
Click to expand...
Click to collapse
Oh, ok, sorry. I didn't run into that problem when testing it before release so that's a new one on me. Only thing I can think of is trying to download the cwm-fix file again and try flashing it in ODIN again. Maybe you got a bad download. Try this one, different link location:
http://www.mediafire.com/file/06al8prkgj29gps/cwm-recovery-ALL-3-30-FIX.tar
landshark68 said:
For now you can just get them from the superclean thread. Same ones.
Click to expand...
Click to collapse
Which kernel are you using from the superclean thread? eb01 or eb16?
DeezNotes said:
Which kernel are you using from the superclean thread? eb01 or eb16?
Click to expand...
Click to collapse
Neither. EC10
landshark68 said:
Oh, ok, sorry. I didn't run into that problem when testing it before release so that's a new one on me. Only thing I can think of is trying to download the cwm-fix file again and try flashing it in ODIN again. Maybe you got a bad download. Try this one, different link location:
http://www.mediafire.com/file/06al8prkgj29gps/cwm-recovery-ALL-3-30-FIX.tar
Click to expand...
Click to collapse
thanks for the link man . that did the trick . bad DL i guess . thanks .
Related
Much like I did for ED01, I created a new Odin for the OTA ED03 update. Once again, this doesn't include the modem, just the base system, kernel, and recovery. It will also perform a factory reset, and is currently Odin only, I'll create a CWM flashable package at some point as well. Enjoy. This should be fully stock unrooted as I was only temp-rooted when I created the image.
Download here
Benefits over ED01 as its 2 days newer than ED01 according to build date??
Sent from my SCH-I500 using XDA App
is it rooted? i figure its stock.
am i a noob? yes. but im addicted to flashing so im about to do it!!!
ED03????? WTF over?!?!?!?!
Bubbadogg14 said:
Benefits over ED01 as its 2 days newer than ED01 according to build date??
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
See the ED03 thread in General
touchthecaleb said:
is it rooted? i figure its stock.
Click to expand...
Click to collapse
It is fully stock and should be unrooted as well.
Hashes
Could you provide file hashes? I've had corrupted download with very small errors which was not detected until I use odin.
beray5 said:
Could you provide file hashes? I've had corrupted download with very small errors which was not detected until I use odin.
Click to expand...
Click to collapse
Umm, if it fails verification in Odin, it doesn't flash. How is allowing Odin to check it harder than checking it manually that you wouldn't just allow Odin to work as it is designed to do?
ok I flashed it! I don't know what's different but it's working perfectly.
Im using the latest otb kernel the latest cwm (in purple) and the ec01 radio.
I even rooted it and uninstalled all the annoying aps. Think I'm going to use this rom for now. Thanks imnuts!!!!
Edit: it just feels good to be "up-to-date" lol
Edit: LOL! such small changes.... Pointless but fun.
imnuts said:
Umm, if it fails verification in Odin, it doesn't flash. How is allowing Odin to check it harder than checking it manually that you wouldn't just allow Odin to work as it is designed to do?
Click to expand...
Click to collapse
I'm very often in places with no connection of any kind whatsoever, its also when I'm between time waiting and had the time for things like odin.
If the file is corrupted, then I would have to abort and wait for the next unknown available free time period to repeat all over again.
I don't see any files on the forums to attain the ED03 modem
Odin has a built in MD5, and created the file to support it. If you don't have a connection or time to flash via Odin, how is having the checksum going to help you? No connection and the checksum is bad, you can't download the file again. No time for Odin, and you probably don't have time to generate and verify a checksum because in the time that it'd take you to verify it, you'd be part way through flashing in Odin.
AuroEdge said:
I don't see any files on the forums to attain the ED03 modem
Click to expand...
Click to collapse
That's because there isn't a file available.
If you want the radio, you'll need to Odin back to DL09 or DI01 and go through the OTA process
imnuts said:
Odin has a built in MD5, and created the file to support it. If you don't have a connection or time to flash via Odin, how is having the checksum going to help you? No connection and the checksum is bad, you can't download the file again. No time for Odin, and you probably don't have time to generate and verify a checksum because in the time that it'd take you to verify it, you'd be part way through flashing in Odin.
Click to expand...
Click to collapse
I'll just make do with my own limitations.
Thanks.
Os anyone working on a debinged / debloated version of this?
Sent from my SCH-I500 using Tapatalk
MANY many thanks, imnuts! This will come in VERY handy in the future!
heya mate
first up thanks awesome pice of work indeed.
second , I AM A NEWBIE on myvzn fsc that i am using in INDIA i guess only DL09 seems to working well as all other builds apart from DL09 and EB01 seem to stuck on language selection after first boot.
]can you please tell me what do i have to actually do to install it ( your odin package )
i mean my details are :
Firmare
2.1-update1
baseband version
S:i500.04V.DL09
Kernal version
2,6.29
Build number
SCH-I500.DL09
the handset aint rooted ( as there is no CWM or superuser thingy ion here there is a vooodoo folder in the sdcard though - i am a noob LOL pl bear with me )
please help me man , i am sorta fed up now flashing cstuff 10 times a day since last 4 days
regards
lord dredd said:
heya mate
first up thanks awesome pice of work indeed.
second , I AM A NEWBIE on myvzn fsc that i am using in INDIA i guess only DL09 seems to working well as all other builds apart from DL09 and EB01 seem to stuck on language selection after first boot.
]can you please tell me what do i have to actually do to install it ( your odin package )
i mean my details are :
Firmare
2.1-update1
baseband version
S:i500.04V.DL09
Kernal version
2,6.29
Build number
SCH-I500.DL09
the handset aint rooted ( as there is no CWM or superuser thingy ion here there is a vooodoo folder in the sdcard though - i am a noob LOL pl bear with me )
please help me man , i am sorta fed up now flashing cstuff 10 times a day since last 4 days
regards
Click to expand...
Click to collapse
You should use this -> http://forum.xda-developers.com/showthread.php?t=1044474
Since there will not be any data wipe in that procedure as you already are on DL09 you should be able to update to ED01 without being stuck at the language menu.
Are there actually any benefits
to the ED03 update as opposed to ED01?
beray5 said:
You should use this -> http://forum.xda-developers.com/showthread.php?t=1044474
Since there will not be any data wipe in that procedure as you already are on DL09 you should be able to update to ED01 without being stuck at the language menu.
Click to expand...
Click to collapse
well i did that as well
still i get stuck at language selection window ,
just donno what to do.
seems like apart from dl09 and eb01 no other ROM works
pntballer505 said:
Are there actually any benefits
to the ED03 update as opposed to ED01?
Click to expand...
Click to collapse
benefits: very little if any
negatives? there are no mods/roms/themes available and probably wont be
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?
Well, first off, I FINALLY ROOTED !!!!!!.....samsung fascinate.I500...2.2.2.....edo5.........rooted with SIMPLE ONE CLICK.......... achieved SUPER USER........downloaded ROM MANAGER........however.......when i try to flash ANY rom, i get error msg " FAILED TO VERIFY WHOLE-LIFE SIGNATURE".....". SIGNATURE VERIFICATION FAILED "....
"INSTALLATION ABORTED"
ANY IDEA WHY I GET THIS ?..........thanks.Dennis
Flashing or installing a recovery on a stock kernel gets reset at boot. You need to flash recovery (cwm) in odin with battery out, insert batt and 3 finger into recovery and flash a custom kernel to get recovery to stick.
good day.
???
hi, and thanks for reply........im sorry but im obviously newbie. can you give advice on how exactly i can acheive your suggestion ?.......i dont know what ODIN is or even how to do this
thanks
dennis
What exactly are you trying to flash? Or what rom are you looking to be on?
good day.
well, like i said, im newb, so i tried the ROM MANAGER app.......and it lists only a few ROMs. but any i try i get same error.
btw, i would like to be on Cynogen, or fresh
Don't really recommend Rom Manger...
-Download Odin.
-Download CWM4 fixed for CM7... HERE. (Bottom of JTs post)
-Copy the ROM you wish to use onto your SD card anywhere.
-Open Odin
-Phone off, remove the battery, hold down volume button, plug in USB cord
-Should go into download mode, shown on the screen of your phone, and show show up as connected in Odin.
-Using PDA Button (Never use phone button in ODIN!) flash the CWM4 for Odin file you downloaded. DON'T do anything until it says success, finished done, etc, just don't stop mid flash. Shouldn't take that long, and your phone should turn back off.
-Reinsert the battery, do the three finger recovery (DO NOT let the phone boot back up otherwise you'll need to reflash recovery)
-Choose install ROM from SD card, choose the rom, CM7 or whatever you downloaded, and flash it.
-Now that's going from memory, so it might not be exactly "install rom from sd card", I think it actually says "install .zip from sd card" or something like that but you get the idea.
- I would recommend backing up all your data, and then wiping cache, dalvik, and data before flashing a new ROM.
- If going to CM7, MIUI, OMGB OMFGB, VGB, etc, any 2.3 based rom you'll want to ODIN the GB_Bootloaders too.
Superoneclick has had problems on 2.2.2 ed05. If you odin the stock ed05 package from pentafive, you dont need to flash a modified kernal to get cwm to stick! Also there is no need to root if your installin a rom, it will already be rooted. My suggestion is to start with powerwashed 1.2 rom get familiar with what you are doing before messing around with mtd gingerbread roms.
Here is directions http://forum.xda-developers.com/showpost.php?p=16566628&postcount=285
odin ?
well my problem is im newbie lol...........i dont know what ODIN is, nor do i know how to flash PENTAFIVE package..........i realize im being a PITA on these forums, but i really need someone to step-bystep me thru this
icemanwbs said:
well my problem is im newbie lol...........i dont know what ODIN is, nor do i know how to flash PENTAFIVE package..........i realize im being a PITA on these forums, but i really need someone to step-bystep me thru this
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1053567
http://forum.xda-developers.com/showthread.php?t=1124391
http://forum.xda-developers.com/showthread.php?t=1013312
Sent from my SCH-I500 using XDA App
icemanwbs said:
well my problem is im newbie lol...........i dont know what odin is, nor do i know how to flash pentafive package..........i realize im being a pita on these forums, but i really need someone to step-bystep me thru this
Click to expand...
Click to collapse
click the link and read!!!!!!!!!!!!!!!!!!! This is all the step by step instructions you need. The link efan450 is good too, but the link I posted has everything you need right there!!!!
icemanwbs said:
btw, i would like to be on Cynogen, or fresh
Click to expand...
Click to collapse
If you don't have any clue what ODIN is, or what CWM is, or even how to spell Cyanogen correctly, you have no business at all even thinking about being on CyanogenMod 7. Have to learn to crawl before you can walk before you can run. Read the stickies, read the stickies again, read the stickies again, know what you are doing and understand what you are doing before doing anything to your phone, then start simple with a debloated/deodexed stock rom or powerwash ED05.
+1
There's no trick or magic or easy fix for rooting. Its all about experience. Once you've flashed 20 ROM's+...you'll understand!
I know that some of these are 150+ pages long, I KNOW...I've read them all! Trust me when I tell you, each page is money!
You've got an amazing machine, go read some of the ROM postings and learn the lingo, the steps, the problems and fixes. then root your fascinate.
You'll be glad you did.
sent from outerspace
Root and Rom completed. Special thanks to droidstyle. Powerwash working very smooth.
Sent from my SCH-I500 using XDA App
Okay, so after installing the kang build 25 ICS for the vibrant, everything went fine. Randomly I get a random reboot and my phone says there was an "encryption error" and that I have to do a factory reset. Since I already had everything backed up, I didn't mind the data wipe. When it went rebooted the CWM screen came up and started wiping everything but when it got to the "formatting data" part, it failed. I tried this many times and it kept failing... SO, I decided to ODIN back to JFD. After doing so, all I get is the Vibrant screen, then an instant shut down. I even tried Eugene's old No Brick Froyo PDA, then tried to reinstall the JFD image, but got no luck.
Question is: What should I do now?
Any help will be GREATLY appreciated. Thanks!
Its a little involved but It's all I could find to help buddy
http://www.youtube.com/watch?v=Rdn5GoRjhn0
It's not the easiest thing in the world to accomplish but It is a guarantied way to get your vibrant into successful download mode to reflash to stock.
At the least something to get you started
Good Luck!
Perhaps it could be a bootloader problem? If you're sure you are doing Odin right, including repartition with the pit file, you could look at your SBL.
.
Sorry but what is SBL?
lolrus101 said:
Sorry but what is SBL?
Click to expand...
Click to collapse
I dont know how to explain it very well lol but to check if the rom you are trying to odin has the sbl in it. Rename it and put a .zip at the end. Then extract to see if its in there it should be named "sbl". To change it back simply delete the .zip off the original file.
JFD
I'm trying to ODIN the original JFD firmware, and I just checked that it does not have SBL in it.
Try odining a rom that has the sbl file in it thats probably why its not working.
---------- Post added at 04:14 AM ---------- Previous post was at 04:09 AM ----------
Here http://forum.xda-developers.com/showthread.php?t=1278683 you need to have java installed to open it
Just tried the Heimdall thing. No luck. As soon as it says rebooting, it goes to the vibrant screen, then the battery charging screen, then continues to bootloop. Same thing happened with Odin
why don't you try what I did
http://forum.xda-developers.com/showpost.php?p=23056603&postcount=10
lolrus101 said:
I'm trying to ODIN the original JFD firmware, and I just checked that it does not have SBL in it.
Click to expand...
Click to collapse
The SBL is the Secondary Boot Loader, which is loaded by the Primary Boot Loader.
I haven't personally encountered any roms which also flash bootloaders.
I did manage to get my phone bootlooped in some weird way which apparently could only be fixed by reflashing the SBL. Note: flashing bootloaders is more dangerous than regular roms.
I am presently running a GB SBL from this thread:
http://forum.xda-developers.com/showthread.php?t=1117990
ian577416 said:
http://www.youtube.com/watch?v=Rdn5GoRjhn0
It's not the easiest thing in the world to accomplish but It is a guarantied way to get your vibrant into successful download mode to reflash to stock.
At the least something to get you started
Good Luck!
Click to expand...
Click to collapse
a 301kohm jig is ONLY good if you have a valid Initial Bootloader, Primitive Bootloader, Partition Table AND Secondary Bootloader. If you damage any of those, a 301kohm jig won't work.
Use UnBrickable Mod. http://forum.xda-developers.com/showthread.php?t=1277056
Flashed the GB bootloader and no luck either . Flashed back to the froyo one, and got the data wipe error again, the phone rebooted, and now its at "KERNEL PANIC - UPLOAD MODE"
AdamOutler said:
a 301kohm jig is ONLY good if you have a valid Initial Bootloader, Primitive Bootloader, Partition Table AND Secondary Bootloader. If you damage any of those, a 301kohm jig won't work.
Use UnBrickable Mod. http://forum.xda-developers.com/showthread.php?t=1277056
Click to expand...
Click to collapse
I have already tried the Heimdall method... and I can access download mode. I think the thing that is causing the bootloop is that the Data wipe fails after a restore. Thats when the bootloop kicks in
lolrus101 said:
I have already tried the Heimdall method... and I can access download mode. I think the thing that is causing the bootloop is that the Data wipe fails after a restore. Thats when the bootloop kicks in
Click to expand...
Click to collapse
If you did Odin/Heimdall to stock after flashing the SBL, and it is still messed up, its beyond me and I'd really like to know the fix. Wiping should be irrelevant after Odining to stock.
If you are getting errors in recovery when you try to wipe/format/restore, that indicates a mismatch between the kernel and the partitioning or filesystem.
cashmundy said:
If you did Odin/Heimdall to stock after flashing the SBL, and it is still messed up, its beyond me and I'd really like to know the fix. Wiping should be irrelevant after Odining to stock.
If you are getting errors in recovery when you try to wipe/format/restore, that indicates a mismatch between the kernel and the partitioning or filesystem.
Click to expand...
Click to collapse
SO the thing is I used the GLITCH kernel with vibrant build 25... I dont think I was supposed to... could that have caused the problem? maybe a voodoo problem?
There are two glitch kernel series that I know of, one for CM7 and one for CM9 and ICS (I think, not sure, that all ICS builds and CM9 use the same basic filesystem scheme).
All stock builds use a Samsung FS scheme which is different from the two above. So there are at least three mutually-incompatible families of FS+kernel pairs.
I used the CM9 kernel I think...
After the installation went fine, I got the encryption error which told me to reboot. as soon as I did, I got the Data wipe fail. Any ideas?
Encryption Error
I'm going through the same thing. I had my phone at ICS passion for months, last night I noticed my phone was in a boot load screen, but it was dimmed. I simply went and took out my battery. . maybe not the best idea, cause I'm now unable to flash back to stock.
I used odin to go back to stock, but I keep getting a boot load/reset. Nothing is happening.
If anyone has found out more on this, please let me know. Thank you so much.
tabthelab said:
I'm going through the same thing. I had my phone at ICS passion for months, last night I noticed my phone was in a boot load screen, but it was dimmed. I simply went and took out my battery. . maybe not the best idea, cause I'm now unable to flash back to stock.
I used odin to go back to stock, but I keep getting a boot load/reset. Nothing is happening.
If anyone has found out more on this, please let me know. Thank you so much.
Click to expand...
Click to collapse
If you are still able to access Clockworkmod Recovery CWM (NOT STOCK RECOVERY) then try this:
http://forum.xda-developers.com/showthread.php?t=1447303
Otherwise just give up. There is currently no fix for this bug as of now.
This is really getting out of hand ICS rom devs should put a big caution sign on their thread(s) stating the following:
WARNING THIS ROM WILL BRICK YOUR DEVICE!!!
Goodluck... in the meantime find yourself a spare phone like i did cuz you certainly ain't fixing this one.
Sent from my Galaxy Nexus using XDA
mother of god
I hope this helps you. I finally, after hours of nothing, tried to use Odin to flash to 2.2 froyo. cha ching. got in.
tar file I used here: http://forum.xda-developers.com/showthread.php?t=833024&page=49
worked for me. I hope it helps you
I was rooted on a stock rom with n9005 CWM for kitkat. I tried flashing the deodexed version for wifi tether. I didnt realize i needed odexed instead. now i am stuck on the sprint screen upon reboot. i tried using odin to reflash that rom again as well as a Cf auto root. both flashed but still stuck on the same screen upon reboot. I then tried to wipe and clear all data and cashe as well as factory reset from recovery mode. still the same issue. ANY help will be appreciated.
NOTE: i looked for 3 days for help on XDA as well as other sites and can not find anything specific to my case, or anything that will work. Please if you offer help include links as i have searched for everything i could think of.
Have you tried to get the stock tar file and use that in Odin? That would bring you back to complete stock.
is this it
i downloaded this SM-N900P_NAB_Stock_Bootloader.tar.md5 from rwilco12's android repository
is this what you are referencing? or is there a different stock file you are refering to?
is this it?
DarkManX4lf said:
Have you tried to get the stock tar file and use that in Odin? That would bring you back to complete stock.
Click to expand...
Click to collapse
i downloaded this SM-N900P_NAB_Stock_Bootloader.tar.md5 from rwilco12's android repository
is this what you are referencing? or is there a different stock file you are refering to?
I meant this one
http://forum.xda-developers.com/showthread.php?t=2712205
twrigh5 said:
i downloaded this SM-N900P_NAB_Stock_Bootloader.tar.md5 from rwilco12's android repository
is this what you are referencing? or is there a different stock file you are refering to?
Click to expand...
Click to collapse
First, let's diagnose what's wrong, to see what you need to do to fix it.
Flashing a DeOdex Mod onto an Odex ROM.
This will mess up your system files. What you'll most-likely get is a bootloop (or stuck at startup, which is where you're at). When this happens, you should be able to still access Recovery and Download Modes. This is good news! This means you have many options to fix your phone.
Possible solutions for your problem.
Restore a backup in Recovery.
The first rule when flashing ROMs/Mods is that you read and understand the thread first.
A close second rule is to make a backup before flashing anything.
I doubt that you have a backup, since that would've been the first thing you would've tried. That's ok, we just have to do a little more work to get your phone fixed.
Reflash the custom ROM in Recovery
This doesn't apply to you too much, because you weren't running a custom ROM, just a rooted stock ROM, but I think it's good for others who might have a similar problem. If you had a bootloop issue, you can always re-flash the ROM in recovery. I'd just recommend wiping data, cache, dalvik cache, and system prior to flashing the ROM.
Reflash the Stock ROM in ODIN.
This is the last-case scenario. I'd go to this thread that micmars wrote and follow his instructions very carefully. Doing this should get your phone back to stock. Then I'd re-do the rooting like you did originally (make sure you're using the kit-kat instructions.
Once you get your phone back and running (and rooted), the first thing I'd recommend is to create a nandroid backup in recovery. This will be your life-saver whenever something gets messed up.
Hope this helps!
EDIT:
I figured that I should give you a reason why the CFAutoRoot didn't work for you:
CF Auto Root only modifies certain files. It's not flashing an entire rooted ROM onto your phone, it's just selectively modifying/replacing files so that you have root access. So, when the system is messed up due to flashing a incompatible Mod, CF Auto Root is not likely to fix those issues. Only flashing a stock Rom, like DarkManX4lf suggested.
topherk said:
First, let's diagnose what's wrong, to see what you need to do to fix it.
Flashing a DeOdex Mod onto an Odex ROM.
This will mess up your system files. What you'll most-likely get is a bootloop (or stuck at startup, which is where you're at). When this happens, you should be able to still access Recovery and Download Modes. This is good news! This means you have many options to fix your phone.
Possible solutions for your problem.
Restore a backup in Recovery.
The first rule when flashing ROMs/Mods is that you read and understand the thread first.
A close second rule is to make a backup before flashing anything.
I doubt that you have a backup, since that would've been the first thing you would've tried. That's ok, we just have to do a little more work to get your phone fixed.
Reflash the custom ROM in Recovery
This doesn't apply to you too much, because you weren't running a custom ROM, just a rooted stock ROM, but I think it's good for others who might have a similar problem. If you had a bootloop issue, you can always re-flash the ROM in recovery. I'd just recommend wiping data, cache, dalvik cache, and system prior to flashing the ROM.
Reflash the Stock ROM in ODIN.
This is the last-case scenario. I'd go to this thread that micmars wrote and follow his instructions very carefully. Doing this should get your phone back to stock. Then I'd re-do the rooting like you did originally (make sure you're using the kit-kat instructions.
Once you get your phone back and running (and rooted), the first thing I'd recommend is to create a nandroid backup in recovery. This will be your life-saver whenever something gets messed up.
Hope this helps!
Click to expand...
Click to collapse
Thanks for your fast response. Im sure as soon as the file downloads i will be just fine. Thanks again!
DarkManX4lf said:
I meant this one
http://forum.xda-developers.com/showthread.php?t=2712205
Click to expand...
Click to collapse
the download isnt working right now, but maybe it will in a few. if you know of another link id appreciate that, if not then thanks again for all youre help thus far and i will just wait and hopefully it works.
Hmm the link wasn't working either earlier this week. Try posting in the thread or messaging mcmars.
twrigh5 said:
the download isnt working right now, but maybe it will in a few. if you know of another link id appreciate that, if not then thanks again for all youre help thus far and i will just wait and hopefully it works.
Click to expand...
Click to collapse
I'm able to download it at home (currently at 10%). I'll upload it to Dropbox when it's done and PM you the link.
topherk said:
I'm able to download it at home (currently at 10%). I'll upload it to Dropbox when it's done and PM you the link.
Click to expand...
Click to collapse
thanks a lot!
twrigh5 said:
thanks a lot!
Click to expand...
Click to collapse
My upload speed is atrocious, so it might be a few hours (it's a large file!)
How did the OP make out? Let us know.
topherk said:
My upload speed is atrocious, so it might be a few hours (it's a large file!)
Click to expand...
Click to collapse
it stuck on the yellow screen for like 3 minutes and i was sad.... than it worked! THANKS SO MUCH!!!! it all worked greatly. i appreciate everyones help!
Yeah. On a full stock Odin flash, things need a little longer to initialize and set up at the first boot. Even after you boot up completely, it takes awhile for everything to finish and settle down.