Do I revert to JFD the same way with GB bootloader as I would with froyo bl ?
Going from 4.0 to 2.1
Sent from my SGH-T959 using XDA App
From what I understand you can revert back to JFD normally unless the JFD Odin package contains only an Sbl.bin or only boot.bin...
adyscorpius said:
8. Can I ODIN to stock JFD like I always did?
The JFD Odin packages that I have seen don't contain sbl.bin or boot.bin ! Hence, till that's the case, its safe to ODIN to stock. Please check your ODIN tar packages using 7zip or WinRAR or any other Archive utility for absence/presence of the mentioned files. If they do appear, they should be present together. Else, if they don't appear, you are safe to ODIN to stock.
Click to expand...
Click to collapse
Pretty sure there are not any ROMs with them in there, so you should be safe.
If you do Odin back to stock, chances are that you'll lose your GB bootloaders as most pit/tar packages will restore you to Froyo bl's.
If you want GB bl's, you'll have to reflash them again. That is ususally what I do.
So Odin to stock JFD then flash gb boot loaders after .
Was wondering cause there was a JFD file specifically for GB BLs which doesn't have a working link
Woodrube said:
Pretty sure there are not any ROMs with them in there, so you should be safe.
If you do Odin back to stock, chances are that you'll lose your GB bootloaders as most pit/tar packages will restore you to Froyo bl's.
If you want GB bl's, you'll have to reflash them again. That is ususally what I do.
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App
Yep. That'll work just fine.
That JFD was floating around and I might have a copy of it somewhere on my HD, but really if you've flashed bl's before, then you know what's up and don't need that package. It is more for noobs who are scared to flash the bl's by themselves.
Alright thanks bro didn't know what that file was for...
Sent from my SGH-T959 using XDA App
Beaten drum, but yeah, I used my ODIN files in the noob guide many times to go back to JFD with no issues.
Related
will repartitioning with odin and doing a flash to stock remove present
kernels from phone.
To properly repartition you must use one of the official vzw .tar files either dl09 or eb01 and you must have the atlas 2.2pit file and the repartition box needs to be checked...that will make sure you correctly repartition...and in doing so your kernel will be replaced along with deleting root, cwm and any user data that you may have
Sent from my SCH-I500 using XDA App
efan450 said:
To properly repartition you must use one of the official vzw .tar files either dl09 or eb01 and you must have the atlas 2.2pit file and the repartition box needs to be checked...that will make sure you correctly repartition...and in doing so your kernel will be replaced along with deleting root, cwm and any user data that you may have
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Also worth noting that some (not all) of these stock odin packages will revert your modem as well. If you follow these instructions you *should* be stock everything.
man i wish that was the case. however, atm i cannot connect my 3g. do you think the modem has something to with this? (btw its the modem that will affect it right?)
Yes the modem is your 3g. If you are having issues try *228 option 2 a few times. If that doesn't fix it Odin back to stock. There is a thread in the general section that has everything you need including instructions for Odin. Use the pit file and one of the Odin files there for coming off of cm7 and you will be completely back to stock, everything wiped and reinstalled.
Sent from my EC09 UKB GB Fascinate.
Dale you are the man..3g works now..THANK YOU
Sent from my SCH-I500 using XDA App
Ok so I was in the process of trying to install CM7 from Superclean 2.9.2 and tried installing CM7 through CWM (red). Didn't work...so I tried installing the fixes for the recoveries in case it didn't work via Odin...
My phone stayed in the boot animation screen the whole way rebooting into the same animation...
So i flashed dl01 all in one to get it to stock...tried reading up and saw that I was supposed to re-partition with atlas v2.2.pit through odin in conjunction with a full stock app...
everytime I flash something with atlas 2.2 ...it always ends up booting into blue recovery with no way to boot into phone. I've tried the Stock DL09 and I've tried it with the dl01 all in one package...no cigar...
At one point I thought it worked and I saw the boot animation with the cyanogenmod logo...but it errored and kept booting into error in which I could only catch a glimpse of the words...some include "mount"
How can I fix this and be able to install Cyanogenmod 7? Please include step by step...I am aware that it is noob to ask such things, but I've tried searching and came up with solutions that didn't work for me.
Thank You
Did you have "re-partition" checked in Odin when using Atlas? Also, double check the MD5 on the .pit in case the download was corrupted.
Sent from my SCH-I500 using XDA Premium App
Reflash that .pit file with a froyo odin file. EB01 or ED01 will work. Then boot up fully. Then flash the dl09 odin file by itself, no .pit then boot OTA and profit.........
Just a heads up. Dont flash a froyo .pit file with an eclair .tar file. Youll boot into recovery evertime.
Just do what I said and youll be good.
check the repartition box and odin the atlas file first(wait for "pass"message)
reset odin
put phone in download mode again
odin dlo9 or eb01 package (no repartition)
Quick caveat on going OTA from DL09: VZW's updates now skip ED01 entirely and go direct to ED04. Keep this in mind if you prefer ED01
Sent from my SCH-I500 using XDA Premium App
laureanop said:
check the repartition box and odin the atlas file first(wait for "pass"message)
reset odin
put phone in download mode again
odin dlo9 or eb01 package (no repartition)
Click to expand...
Click to collapse
This might work too. but I havnt tried it. I did same thing as you and was told by adryn how to get phone booted back up. This was awhile ago tho..... Good luck.
Sent from my SCH-I500 using XDA App
Jazz848 said:
Quick caveat on going OTA from DL09: VZW's updates now skip ED01 entirely and go direct to ED04. Keep this in mind if you prefer ED01
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
That is true. But you prob want ec09 radio anyway. Best ive used...
Sent from my SCH-I500 using XDA App
no ec09 radio for me anymore. I was running cm7 and decided to install ec09. Stuff started disappearing from my sd card (I mean like entire huge folders). I'm sticking with the EDs
Just re-read OP and noticed you asked for step-by-step. There are a few guides out there, but this one by kidserious is the most up-to-date one I've found and it has yet to give me a single issue: Hope this helps!
EDIT: When using the aforementioned guide, I have always used the DL09 .tar and cannot speak for the EB01 .tar. YMMV
I have been messing with my phone alot lately and have had a bunch of issues(not booting, boot loop, different colore recoveries). So I put together a little folder for myself that gets me back to ED01 TW Debloated and OTB 1.6 kernel. If you would like me to post it or send you the folder with everything you need I can. at work now so it wouldnt be till later tonight
So I've tried starting off with kidserious's way of returning to stock...and it seemed to have worked for me because I was able to see the logo with no problem booting into recovery (red).
But when I tried installing CM7 Test Build 10 via CWM, and it didn't work...it went into repeat boot (blue) and before it started doing that after I saw "Installation aborted"
I'm actually now at a stump of how to install CM7 now...
If your using the DI01 file in ODIN you dont need to have the .pit file. Its a full stock ODIN it already has it. If you flash that to eclair your fine.
Fasinationinmotion said:
If your using the DI01 file in ODIN you dont need to have the .pit file. Its a full stock ODIN it already has it. If you flash that to eclair your fine.
Click to expand...
Click to collapse
I apologize, but I'm confused by this. It's my understanding that the .pit is necessary if you're coming from a Voodoo setup. Are you saying that the DL01 .tar reverts the file system to stock on its own? Not challenging you, per se, just making sure I understand properly.
Sent from my SCH-I500 using XDA Premium App
Jazz848 said:
I apologize, but I'm confused by this. It's my understanding that the .pit is necessary if you're coming from a Voodoo setup. Are you saying that the DL01 .tar reverts the file system to stock on its own? Not challenging you, per se, just making sure I understand properly.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
You've got it right, thats the whole reason for using the atlas and repartition checked, it's to format everything back to rfs(non voodoo) from ext4.( voodoo) or in this case mtd
This it's especially important when coming from an mtd build..ie. Cm7 and going back to an old rfs or ext4 rom. I'm no dev, just a flash a holic but I think of it like this, voodoo is just a lag fix modification of our original rfs(non voodoo) format, while mtd is a completely different format so we no longer have the luxury of a recovery that supports this ability to enable and disable our lag fix (voodoo)...which your new mtd format doesn't support. I don't even think it is possible to make a recovery that will repartition your system in preparation to flash any rom format you want
Again I am no dev and this is how I think of it to make sure I take the appropriate steps...it's just my way of remembering what to do when flashing
This is why every time you want to go back from an mtd build you must repartition with the atlas 2.2 to re format your previous mtd format back to the original rfs
Everyone I've helped with issues going from mtd to rfs/ext4 or vice versa I always suggest
rfs (non voodoo)--->mtd
Odin the 3-30 fix all recovery...immediately boot to cwr
wipe everything and flash newest cm7...(I used the 7/4 build but I see it's no longer available but the newest one works too) and reboot
power button menu to recovery...flash gapps/mtd kernels/misc.zip files you may also have with out wiping and reboot.
odin desired radio...reboot.. done.
Mtd---> rfs/ext4
Odin vzw eb01 with atlas 2.2pit and repartition checked
Fully reboot...then pull batt.
Odin desired recovery..(I still use 3-30 fix all cwr).....immediately three finger boot to cwr wipe everything and flash new rom/kernel (voodoo our non voodoo)...reboot
Hasnt done me wrong yet...no fc...no boot loops just flash a holic goodness!
Sent from my SCH-I500 using XDA App
go to this thread, read about the files you need, flash back to stock. here
Then root, install CWR, follow part of odin heimdall guide on how to keep root on ed builds, then get jt's Cyanogen MTD, supposed to have install issues fixed. here
Hope this gets you what you are looking for.
leonvx671 said:
At one point I thought it worked and I saw the boot animation with the cyanogenmod logo...but it errored and kept booting into error in which I could only catch a glimpse of the words...some include "mount"
Click to expand...
Click to collapse
That happened to me. The download was corrupted. I odined EB01 then odined jt's new recovery, redownloaded cm7, and reflashed.
Sent from my SCH-I500 using XDA App
GrainOsand said:
Reflash that .pit file with a froyo odin file. EB01 or ED01 will work. Then boot up fully. Then flash the dl09 odin file by itself, no .pit then boot OTA and profit.........
Just a heads up. Dont flash a froyo .pit file with an eclair .tar file. Youll boot into recovery evertime.
Just do what I said and youll be good.
Click to expand...
Click to collapse
Please help! I have tried this numerous times, and my phone just keeps booting into stock recovery. It won't let me get past it.
I originally tried the .pit file with dl09 (mistake - I know), and it started the recovery mess. Then I downloaded the "stock" rooted eb01 file (EB01_DXC.tar.md5), and flashed it with the .pit file (atlas v2.2) and re-partition checked.
I have no other clue what's going on. I was just trying to wipe completely fresh to be able to load the CM7 Espresso on my phone. I've been running old CM7's for a while with the glitch kernels.
Help, please - I've been without a phone for the past 2 days. A huge thanks to anyone that can help me out!
I only use the DL01 or the ED05 stock packages. I think you should try those. I restored my phone when I was running SuperClean w/Voodoo with the DL01 package, no pit file.
Here is a link to ED05
OhioYJ said:
I only use the DL01 or the ED05 stock packages. I think you should try those. I restored my phone when I was running SuperClean w/Voodoo with the DL01 package, no pit file.
Here is a link to ED05
Click to expand...
Click to collapse
I'm scared that I've already messed something up by using the pit file, because I actually had the full dl01 file, and nothing. Not really sure what would be different about the ed05 file. I mean, I'm gonna try it, but does any one else have a suggestion? Thanks.
brettdacosta said:
Please help! I have tried this numerous times, and my phone just keeps booting into stock recovery. It won't let me get past it.
I originally tried the .pit file with dl09 (mistake - I know), and it started the recovery mess. Then I downloaded the "stock" rooted eb01 file (EB01_DXC.tar.md5), and flashed it with the .pit file (atlas v2.2) and re-partition checked.
I have no other clue what's going on. I was just trying to wipe completely fresh to be able to load the CM7 Espresso on my phone. I've been running old CM7's for a while with the glitch kernels.
Help, please - I've been without a phone for the past 2 days. A huge thanks to anyone that can help me out!
Click to expand...
Click to collapse
a pit file is a pit file, they are no different for eclair or froyo from my understanding. I have no problems odin dl09 w/ pit...I actually got that tip from the stickies on the galaxy s forums.
http://www.galaxyforums.net/forum/fascinate-rs-guides/2911-how-upgrade-cyanogenmod7.html
as you can see by reading the link alot, there are alot of different guides out there with different methods and I have tried them all... Thats why I created my own guide with pieces from all the other guides that I felt worked the best. My best advice to you is spend alot of time doing research and form your own opinion on what works best. DO NOT take one posters advice as it being the correct way because there is alot of misinformation on teh internet!!
hi,
can i flash CM7 on GB bootloader ?
I'm just having a hard time rooting my phone(usb problem, but i can get to download mode) after going back to stock.
I'm right now on 2.3.4 ROM(non CM7).
You can flash it, but you wont have access to your external sdcard.
And before you go to CM7, Odin the froyo bootloaders, then Odin back to jfd, then flash CM7.
Sent from my SGH-T959 using XDA App
doesnt taking the external out and putting it into 1 of them usb stick things to plug in by itself work or it just doesnt work plugging the phone into usb ??
im not on CM7, just wondering
geoffcorey said:
You can flash it, but you wont have access to your external sdcard.
And before you go to CM7, Odin the froyo bootloaders, then Odin back to jfd, then flash CM7.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
2 questions
1. doesn't JFD tar has boot loaders in it that will be flashed during odin ?
2. if i do need froyo boot loaders, where can i take them from ?
thanks.
xxprowler said:
2 questions
1. doesn't JFD tar has boot loaders in it that will be flashed during odin ?
2. if i do need froyo boot loaders, where can i take them from ?
thanks.
Click to expand...
Click to collapse
same place you got the GB 1s from
^that about the ffroyo bootloaders... you wont have aaccess to external sd on your phone if you have cm7 and gb bootloaders. I suggest you odin froyo bootloaders, thrn jfd and the flash cm7 as mentiones above.. idk if odin jfd will do bootloaders as wwell, just do it the long way.
Sent from a cell tower to the XDA server to you.
xxprowler said:
2 questions
1. doesn't JFD tar has boot loaders in it that will be flashed during odin ?
2. if i do need froyo boot loaders, where can i take them from ?
thanks.
Click to expand...
Click to collapse
1: nope, it does not contain any bootloaders.
2: the same.place you get the gb bootloaders. Go look in the dev section within the 1st 3 pages. It's in there.
Sent from my SGH-T959 using XDA App
Nighty #73 changelog said:
kernel: support for emmc on gingerbread bootloaders (android_device_samsung_vibrantmtd)
So... im going to install #73 right now, and let you guys know how its works.
Update: Nightly 73# and up Will work with GB Bootloaders, External SD card works. Now you can bounce around between 2.2/2.2.1, JVR, CM-7 and Maybe Miui, without having to Odin. WOOT!
Just wondering what else they do besides fix rainbow effect.
I've had a bad past with bootloaders... SoftBricked a few times, hard bricked twice.
So what are the benefits?
And if I do flash bootloaders, when I odin to eclair does it auto flash the default bootloaders?
xriderx66 said:
Just wondering what else they do besides fix rainbow effect.
I've had a bad past with bootloaders... SoftBricked a few times, hard bricked twice.
So what are the benefits?
And if I do flash bootloaders, when I odin to eclair does it auto flash the default bootloaders?
Click to expand...
Click to collapse
They give a more convenient key mapping to enter the download mode and recovery.other than that no I guess.flashing to eclare does not restore original bootloaders.you have to flash it separately if you want it.but bootloadres are backward compatible.so no need to so.But if you are flashing a CM based rom you need to be on froyo bootloaders even its a GB rom.
Sent from my SGH-T959 using XDA App
nuwanmw1988 said:
They give a more convenient key mapping to enter the download mode and recovery.other than that no I guess.flashing to eclare does not restore original bootloaders.you have to flash it separately if you want it.but bootloadres are backward compatible.so no need to so.But if you are flashing a CM based rom you need to be on froyo bootloaders even its a GB rom.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
+1 and it provides less conflicts with all the newer software we are now using.
I think some of the other custom bootloaders were snappier but that's the trade off less speed but less conflicts
ok thats all i needed, thanks guys
Some Odin packages do contain bootloaders. I haven't flashed actual jfd in a long time, so I don't remember if it does, I do know the jk2 odin package eugene373 put together does flash bootloaders.
You can view the tar archive with 7zip or wnrar, if it contains the boot.bin and sbl.bin, then it will flash bootloaders along with everything else.
Sent from my ZenDroid, meditating on the XDA App
Currently flashing ICS Passion as every version appears. I try to clean out my phone every 2 versions or so by reverting to stock then back to CM7 then back to ICS again
Everytime I go from ICS back to Stock, I first go to ODIN and convert my bootloader back to Froyo. Then only do i install stock.
Is this constant change of bootloaders from GB to Froyo necessary or will it eventually kill my phone if i keep flashing back and forth?
So far my phone is going great...no problems. Question is Just for knowledge.
Definitely put yourself at a greater risk to mess it up! Honestly, I don't think it matters. I've read people using ics just fine on froyo loaders and the GB loaders say they are compatible with froyo roms. So there really is no reason to keep switching back and forth.
Sent from my SGH-T959 using XDA App
Don't be so sure of that, though.. there's been a few hard bricks going back to stock with Gingerbread bootloaders, it's safest to go the way you're doing it, not sure if it'll 'kill' your phone sooner.
My experience is that I put GB bootloaders on months and months ago and have never gone back to froyo bootloaders. I have odined back to stock jfd many times with GB bootloaders. I have used them for 2.1, 2.2, 2.3 and 4.0 roms.
Also I have put ICS Passion on a few phones now and have never flashed cm7 in the process. I have flashed straight from 2.2 and 2.3.
Odin gb bootloaders if not installed then I factory reset, wipe cache, format system, flash ics, wipe dalvik, fix permisions, boot system. First time it goes into a bootloop due to cwm mismatch, pull batt, boot recovery and repeat the flash process. It boots fine the second time. I've never had issues with fc's, lag, etc.
bobshute said:
My experience is that I put GB bootloaders on months and months ago and have never gone back to froyo bootloaders. I have odined back to stock jfd many times with GB bootloaders. I have used them for 2.1, 2.2, 2.3 and 4.0 roms.
Click to expand...
Click to collapse
I agree with that. I flashed GB bootloaders half a year ago and never had any problem.
I'd rather stick to GB bootloaders, and what dpaul007 said, you risk it alot by flashing it often.
Ive been on the GB boot loaders for over 6 months - no issues. Odin'd JFD about 5 times since then...no issues.
Ill prob try Odin to Lidriod next time though.
Jfd is fine. but once i trid to flash stock froyo jfd to kb7(odin) without change the gingerbread bootloader. My phone was hardbricked.exactly i can not say reson was the gn bootloader. Be safe its not good to change bootloader its a great risk. Whenever i want flash an ics Rom first i flash cm then ics. No rainbow issue at all.
Sent from my vibrant using xda premium
gdtennak said:
Jfd is fine. but once i trid to flash stock froyo jfd to kb7(odin) without change the gingerbread bootloader. My phone was hardbricked.exactly i can not say reson was the gn bootloader. Be safe its not good to change bootloader its a great risk. Whenever i want flash an ics Rom first i flash cm then ics. No rainbow issue at all.
Sent from my vibrant using xda premium
Click to expand...
Click to collapse
The only time you will run into issues is if you Odin a rom that only has one of the two bootloaders files in it causing a mismatch. The two files are boot.bin (primary bootloader) and sbl.bin (secondary bootloader). If both of those files are from the same generation (froyo or GB) there is no problem.
The problem you had with ka7 is it only had the sbl.bin file and not the boot.bin file leaving you with a gb boot.bin and a froyo sbl.bin. They should never have put one file in a rom without the other. JFD does not have either bootloader files in it so it's a safe odin with either gb or froyo bootloaders. Btw you would run into the same problem if on froyo bootloaders you odined a gb rom with only a gb sbl.bin and not a gb boot.bin.
I never Odin a rom that has either bootloader files in it. I use 7zip to open the tar to check. If either boot.bin or spl.bin are in it I remove them first or don't odin the tar. Then there is no problem. I do not like flashing roms with bootloaders as I would rather flash the bootloaders myself.
bobshute said:
The only time you will run into issues is if you Odin a rom that only has one of the two bootloaders files in it causing a mismatch. The two files are boot.bin (primary bootloader) and sbl.bin (secondary bootloader). If both of those files are from the same generation (froyo or GB) there is no problem.
The problem you had with ka7 is it only had the sbl.bin file and not the boot.bin file leaving you with a gb boot.bin and a froyo sbl.bin. They should never have put one file in a rom without the other. JFD does not have either bootloader files in it so it's a safe odin with either gb or froyo bootloaders. Btw you would run into the same problem if on froyo bootloaders you odined a gb rom with only a gb sbl.bin and not a gb boot.bin.
I never Odin a rom that has either bootloader files in it. I use 7zip to open the tar to check. If either boot.bin or spl.bin are in it I remove them first or don't odin the tar. Then there is no problem. I do not like flashing roms with bootloaders as I would rather flash the bootloaders myself.
Click to expand...
Click to collapse
Thank you so much for you explanation. I never knew what was gone worng. Seems like its risky to flash a rom using odin without cheking both bootloaders.
Sent from my vibrant using xda premium
So I should stick to gingerbread bootloader now on and make sure that files i flash have both .bin and .sbl to eliminate bootloader mismatch
Thanks for all the responses!
Sent from my SGH-T959 using XDA App
accura407 said:
So I should stick to gingerbread bootloader now on and make sure that files i flash have both .bin and .sbl to eliminate bootloader mismatch
Thanks for all the responses!
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yes, but make sure that the tar's you Odin DO NOT have either boot.bin or sbl.bin in them unless you specifically want to change your bootloaders, then they must have both. A flash from CWM will never (can never) have them.
I only use ODIN to flash back to stock JFD
Everything after that, I flash only using CWM. So that means I should be safe then right?
Because as previously said, stock JFD has no .bin or .sbl right?
Sent from my SGH-T959 using XDA App
accura407 said:
I only use ODIN to flash back to stock JFD
Everything after that, I flash only using CWM. So that means I should be safe then right?
Because as previously said, stock JFD has no .bin or .sbl right?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
right
10char
So now i kept gb bootloader, reverted back to stock JFD....with stock it would do the is9000 then vibrant screen
Once i loaded ICS there is only a galaxy boot, no vibrant boot...my understanding is that all this is normal.
Question is....if i want to revert to stock Jfd again there are no other steps i need to take right? Just the same as usual i hope.
Thanks
Sent from my SGH-T959 using XDA App