Can I use odin one click to revert to stock even though I have 1101 build cappy? It seems oc only works for 1010 and below. Should I use odin 3 and flash stock jf6 instead? Currently on cog 4.4.
Sent from my SAMSUNG-SGH-I897 using XDA App
some people have trouble with odin one click with newer models. some dont.
you can flash anything with the odin 3 flasher.
avoid stocks with bootloaders. or "3 button fix" versions.
if you dont flash bootloaders you should never hard brick.
Once back to stock, do you know if I can use kies to flash official froyo upgrade, or will that be a prob after flashing custom rom? Is there an odin flash that will get me stock 2.2 without using any bootloaders? I've searched, but seems like everything takes you back to eclair.
Sent from my SAMSUNG-SGH-I897 using XDA App
Cdub3 said:
Once back to stock, do you know if I can use kies to flash official froyo upgrade, or will that be a prob after flashing custom rom? Is there an odin flash that will get me stock 2.2 without using any bootloaders? I've searched, but seems like everything takes you back to eclair.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
You could use the one Trusselo made.. In his sig right above your post
thats for rogers... is he rogers...?
I'm at&t. same thing right? I got one completely dead, bricked, cappy in the hands of samsung right now. Hoping they'll replace or fix me. Got one cappy in my hand that's being "borrowed" for the 30 day window till I find out what's up with the one samsung has. Hoping I can get functioning cappy back from samsung, and talk the wife into letting me keep the "borrowed" one. That way I have a stable one, and one to mess around with. Planning on taking on gingerbread, only once I've covered all my bases.....I think. Just wanted to know best way back to stock, just in case I needed to bring back the phone. Like I said, it's a 1101 build, and I'm currently running Cog4.4, so I didn't want to brick it with one click. Dumb noob question, but are boot animations same/diff from bootloaders. I opened archive on cog 4 and in system/bin their are boot animations. I flashed cog via rom manager. Did i just get lucky or are these not bootloaders, just animations? Is there a thread that shows which roms come with bootloaders and which don't?
read this it explains the boot process and what a bootloader is
http://forum.xda-developers.com/showthread.php?t=1049294
bootloaders are not the same as a boot animation.
animations are found in /system/media/bootanimation.zip
you didnt get lucky with cognition flashing a bootloader that will only **** **** up if you have gingerbread bootloaders which you didnt, so flashing a froyo secondary bootloader was fine (thats why its in there)
The bootloaders would be in the updates folder of the zip.
Thanks studacris. Seems the more I learn about all this, the more ii find stuff I didn't know. Constantly on forum trying to learn so I don't have to bother guys like you. Since I got ur attention, flashing to i9000 rom would require bootloaders correct? Looking to do that next. Currently im US, att, i896. Sorry to bother ya.
Sent from my SAMSUNG-SGH-I897 using XDA App
Sorry I meant i897
Sent from my SAMSUNG-SGH-I897 using XDA App
nope new bootloaders are only needed if you are jumping to gingerbread
only flashing the i9000 2.3.3 roms requires bootloaders. all the 2.2.1 roms will work without danger of bricking.
if all you did on the borrowed cappy is root and flash a kernel you can flash the backed up kernel and then unroot. (did you use sgs kernel flasher to flash the kernel like when we talked about it? did you back up the kernel?)
you might want to look at getting a jig just to have one around. samsung keeps releasing new builds of the phone and there are unknowns. there are mixed reports from the 1010 build and up. you should be able to use odin 1.7 and flash the jf6 from icezar1 and you still have stock bootloaders so there "should" be no need for odin one click.
all the problems last time must have been do to the gingerbread bootloaders in combination with your 1010 build phone, i should have told you to use odin one click, infact you should have had a jig before i encouraged you to try gingerbread, my fault, but i didnt have problems when i did the same thing.
Should I flash a i9000 kernel before a i9000 rom? Then after all is said and done, find a compatible modem? Only reason I want to go to i9000 rom is because there seems to be more available. Can I do all this via sgs kernel flasher and rom manager/cwm or does it have to be done odin for the first switch to i9000? I'm assuming I can go back between sgh I897 and i9000 no prob since no ginger boots are involved? Just to be clear, even if I flash a rom with bootloaders, it shouldn't be a prob as long as it's 2.2 rom? Are 2.2 boots backwards compatible if i want to flash back to stock? I ask cuz prob can't use oneclick cuz my build is to new. again, don't mean to be a pest. cut me off whenever you feel like it.
Roms are all in one package kernel and modems are included.
Related
Any word on if there will be an Odin One Click for the official Froyo 2.2 KB1? If so, will it be able to incorporate the ability to recieve OTA updates? I've looked in many obvious threads including, the development section as well as the Odin One Click thread.
Doesn't KB1 come with a newer recovery that needs to be downgraded regardless? So why not just flash back to JF6?
cavsoldier19d said:
Any word on if there will be an Odin One Click for the official Froyo 2.2 KB1? If so, will it be able to incorporate the ability to recieve OTA updates? I've looked in many obvious threads including, the development section as well as the Odin One Click thread.
Click to expand...
Click to collapse
Any more updates, I wouldn't hold my breath, won't be OTA. AT&T learned it's lesson with the JH7 fiasco.
You can just use Odin3 to get back to JF6, then reinstall the Froyo update via Kies. Done it a half dozen times already.
I am aware that I could flash back to jf6 and go from there. Just curious if odin would make a kb1 is all. I agree, hopefully att learned from ota update fiasco. When I first got my captivate, I was shocked to see that samsung didn't provide a desktop software cd that would allow your pc to download and push updates similarly with blackberrys and the blackberry manager software or iphone with itunes. For that reason alone is why i found myself on xda trying to find out how to update. I now know that is what the samsung lies is for. But that could still be provided with the phone for the average end users who don't rom their phone.
Sent from my SAMSUNG-SGH-I897 using XDA App
ODIN ONE CLICK (and ODIN3) are utilities made by Samsung, and how it was compiled is unknown, SO.. it cannot be "torn apart" and redone with froyo.
however there are some automated systems out, HEIMDALL and the new Captivate toolbox using HEIMDALL, may come out with easy froyo flashes,
and dont forget about froyo's 3e recovery, updated rooting, updated unlock, ect... it just adds more things to do to load a new custom rom..
so unless you want to flash froyo stock and leave it there, there isnt much point.
I am keeping a copy of the stock froyo firmware in this post http://forum.xda-developers.com/showthread.php?t=963403 Just in case I need to send it back. I have used Heimdall to flash it a couple of times so far.
pietro_spina said:
I am keeping a copy of the stock froyo firmware in this post http://forum.xda-developers.com/showthread.php?t=963403 Just in case I need to send it back. I have used Heimdall to flash it a couple of times so far.
Click to expand...
Click to collapse
Wait, so I can just flash that prior to sending my phone to ATT as opposed to odin to JF6 then Kies to KB1?
Something like this would definitely be handy.
+2 a Odin kb1 would make life easyer
Sent from my SAMSUNG-SGH-I897 using XDA App
qwertyaas said:
Wait, so I can just flash that prior to sending my phone to ATT as opposed to odin to JF6 then Kies to KB1?
Click to expand...
Click to collapse
Maybe, :-/
It depends on what you end up with when you flash it... as there are only the four (cache.rfs, factoryfs.rfs, modem.bin and zImage) files in there. if the rom you flashed has other stuff that won't get over written I guess you might ind up with some sort of Franken ROM and worst case a brick. If you arn't sure what you have done to or have on your phone then I guess you ask in your roms help thread what is the approved method of returning to stock from their rom... some have various lagfixes and such that can require a specific procedure.
Even Odin leaves behind remnants of things from your previous usage. I just sent two phones back and had to Odin both. I then did master clear and still there was some stuff left that I had to delete manually. I doubt AT$T has the manpower or time to go through every returned phone looking for custom ROM remnants. To insulate them from any claims of having access to a customer's private information that may have been left on the phone by a less tech savvy user, they probably just wipe them when they get them or toss them in a bin to be used as repair parts.
I have just flashed GR-11 on my Cappy and I have some questions.
GR-11 and Continuum have different instructions and ways on how to update the BootLoader. Do they end up with the same end product?
So does following the guide for GR-11 allows me to flash Continuum without having to go back to stock? or do I have to go back to stock before flashing Continuum (re-update bootloader)
Side questions, could you use Froyo Rom after updating the BootLoader?
Thanx
If you have the JVB bootloaders already installed you can change to another JVB rom without reinstalling bootloaders. A couple of people in GR11 thread have reported going from C5 to GR11 with no issues. You cannot however run a froyo rom on these. You must flash back to stock to get correct bootloaders.
Yes you can.. I had absolutely no problem running stock 2.1 or serendipity 6.4 with the new bootloaders.
Just make sure the rom you're flashing doesn't include an sbl.bin (like cognition does) or you risk hard bricking your device.
Sent from my GT-I9000 using XDA App
I stand corrected.
hard brick = dead even with jig?
or recoverable with jig?
oh and how do I know whether a rom has sbl.bin inside or not?
and I did post this on GR-11, but I thought I might ask here as well,
does changing the kernel on GR-11 from the instruction to Talon matters?
file system wise it doesn't change right?
modest_mandroid said:
Yes you can.. I had absolutely no problem running stock 2.1 or serendipity 6.4 with the new bootloaders.
Just make sure the rom you're flashing doesn't include an sbl.bin (like cognition does) or you risk hard bricking your device.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
It's not even a question of risk. it's a GUARANTEE if it contains a froyo sbl.bin while you're on a gb boot.bin you will brick it. For good. dead. No life. A shell if it's former glory. A corpse... I think I made my point
look in the updates folder if the rom zip you wanna flash, if it had an sbl.bin delete it.
if you wanna flash talon just pop it in the pda slot of odin and flash like the instructions say, if you look in the .tar you will see it only contains a zImage which is the kernel.
xtsuname said:
hard brick = dead even with jig?
or recoverable with jig?
oh and how do I know whether a rom has sbl.bin inside or not?
and I did post this on GR-11, but I thought I might ask here as well,
does changing the kernel on GR-11 from the instruction to Talon matters?
file system wise it doesn't change right?
Click to expand...
Click to collapse
Hard brick as in the hardware buttons or jig won't do anything. It'll just sit at a black screen until you mail it to Samsung for repairs.
You can check to see if a rom contains bootloaders by opening the zip archive. There will normally be three folders, META-INF, system, and a third one usually (but not always) called updates. Look into that last one. If it contains either boot.bin, sbl.bin or both, you might want to take a pass on that rom.
studacris said:
look in the updates folder if the rom zip you wanna flash, if it had an sbl.bin delete it.
Click to expand...
Click to collapse
Need to update the update script if you're going to delete things from the package..
So to be safe, just stay in Gingerbread and nothing should go wrong right?
Flashing kernel and other roms should be safe as long as they are meant for Gingerbread then I conclude?
Thanx!
Once you have the boatloader installed you should be ok. Flashing between Roms should be ok if its compatible with the kernel as long the Roms are based off the gingerbread boatloader
Sent from my GT-I9000 using XDA App
Do I have to flash the GB Bootloader if I want to go up to a JW1 2.3.6 rom from a JVP 2.3.4 rom?
Edit: Guess I got lucky. I tried and it worked.
Your already on GB BL so no
Sent from my SGH-I897 using xda premium
i just wanted this all in one place.i wanted my daily driver to be torch or fusion cause of call quality but also want to play around on gb roms.i found a safe way to go back and forth.if something happens to your phone i'm not responsible this is what works for me.
1.flash gb stock just like it says here:http://forum.xda-developers.com/showthread.php?t=1045734
2.i wanted mosaic on to play around with so i flashed mosaic.now from mosaic( I have only tried mosaic so far) you can flash back to 2.2 or 2.1 rom that has NO secondary bootloaders(this is very important).and you have to be on http://forum.xda-developers.com/showthread.php?t=1042543 the kernel from here in order for this to work cause it uses cwm 2.5 still.
3.make sure you wipe data/factory reset and also wipe cache partition and dalvik cache in between flashing roms.
4.if on talon kernel you cant flash from 2.3 to 2.2 cause it uses cwm 3.0.so you need to get kernel flasher from market and the this file http://etc.muteheadlight.net/android/I9000_reoriented_vG.1.1_novoo.tar and flash it from kernel flasher it will put you back on cwm 2.5 and you can go back to 2.2 from there.
this has worked for me several times today i wanted to make sure it worked go and thank all the devs on there respected paged.they work hard on all this development show some appreciation.
again dont mix boot loaders make sure the rom you are flashing does not flash boot loaders.just stay on gb boot loaders.as it is stated you will brick your phone mixing boot loaders.
I hope this helps some people out and explains it good enough.
I just use odin one click to flash back to stock then flash by froyo rom of choice.
To Gingerbread from 2.1 bootloaders:
odin flash bootloader and reorient kernel package HERE (7mb)
odin flash talon or other kernel with CWM3 built in
boot into CWM3
CWM3 flash GB wipe rom!
Back to Eclair/Froyo: (keeping GB booties)
Odin flash a Kernel with CWM2.5 built in (onix)
boot into CWM2
CWM2 flash 2.1 or 2.2 wipe rom.
------AVOID ROMS WITH SBL (secondary boot loader) LIKE A PLAGUE!!! or built-in 3 button fix!----- YOU WILL BRICK!!
****To not worry about mixing Bootloaders or the SBL on Eclair/Froyo roms flash odin-one-click to get stock booties before Odin flashing a Cwm2.5 kernel.
Easy Peasy Lemon Squeezy
i also use odin one-click to get back to stock
Fezz102 you have successfully flashed between GB and Froyo and only used odin to flash the initial boot loaders and rom after that you just swapped kernels with sgs kernel flasher and haven't had a single issue? And you haven't used odin again?
Sent from my SAMSUNG-SGH-I897
Why is everyone so afraid of odin? AS LONG AS IT DOESN'T HANG ON BOOT.BIN OR SBL.BIN YOU CANNOT BRICK. PERIOD.
Kernels don't have bootloaders AT ALL using odin to flash a kernel is recommended by all the kernel devs, they have stated the app is actually more likely to cause improper writes than odin.
studacris said:
Why is everyone so afraid of odin? AS LONG AS IT DOESN'T HANG ON BOOT.BIN OR SBL.BIN YOU CANNOT BRICK. PERIOD.
Kernels don't have bootloaders AT ALL using odin to flash a kernel is recommended by all the kernel devs, they have stated the app is actually more likely to cause improper writes than odin.
Click to expand...
Click to collapse
I'm on a mac I have a pc around but I swear if you saw it you'd be a little nervous to it's a cheap old lap top running xp it doesn't even have a battery, I'd be fine with odin if I had faith in my pc. That being said don't mention heimdall it doesn't recognize 2.1 bootloaders so in order to move up I still need odin.
Sent from my SAMSUNG-SGH-I897
heimdall doesnt recognize 2.1 bootloaders? really?
how was it created with 2.1 bootloaders before the 2.3 ones ever existed??
thats news to me.... learn somethin new every day...
*sarcasm*
This an interesting post from the guys that wrote heimdall the first is a list of confirmed devices that work with heimdall the eighth post is a list of confirmed working bootloaders and osx compatability i9000 this should give you an idea of what I'm talking about. Out of ten only two support osx. As far as the i897 is concerned if you ever flashed your phone with odin 1click and I have the boot loaders included do not support osx. THAT'D be a fact . *touchee*
Sent from my SAMSUNG-SGH-I897
Here's the linkhttp://forum.xda-developers.com/showthread.php?t=891518
Sent from my SAMSUNG-SGH-I897
1tontomato said:
Fezz102 you have successfully flashed between GB and Froyo and only used odin to flash the initial boot loaders and rom after that you just swapped kernels with sgs kernel flasher and haven't had a single issue? And you haven't used odin again?
Sent from my SAMSUNG-SGH-I897
Click to expand...
Click to collapse
no problems so far.just wipe everything and factory reset clear data in recovery the key there is to be in cwm2.5 and not 3.0. and to never flash anything with secondary bootloaders.
Hey if Im currently on a JVH ROM, and want to try out the Galaxy Sense i9000, but the whole deal about the bootloaders is a little irrating. And its even trickier for me to go back to stock considering I have a build 1010, thus One Click soft bricks my phone (*I have a jig*). But it really isnt a big deal because I use the JH2 method and iCezars method for flashing back without risk, without replacing the bootloaders. Those are the two methods I have had to flash back to stock while on a Gingerbread ROM.
But my question lies in whether I can flash back to stock using one of the two methods I stated above which DO NOT FLASH BOOTLOADERS and follow the instructions in the Sense i9000 thread (This isnt a how to, to flash, because from December--February all I did was flash MIUI and CM7), but rather do you know if I could flash with GB bootloaders or would it be too big of a mess?
And if I cant can someone point me into a direction of a .tar file that contains BOTH BOOTLOADERS such as Odin One Click but I have to use Odin 3 and manually put it in and flash.
Thanks!
Just use odin one click, yes it will soft brick you, no it's not s big deal you have a jig, after that soft brick use your jig, and icezar's packages liked you usually do. Bam stock with original bootloaders. That is your only option. Nothing else contains both bootloaders.
studacris said:
Just use odin one click, yes it will soft brick you, no it's not s big deal you have a jig, after that soft brick use your jig, and icezar's packages liked you usually do. Bam stock with original bootloaders. That is your only option. Nothing else contains both bootloaders.
Click to expand...
Click to collapse
Hmm.. I was seriously thinking that but I was worried that it would completely brick the phone because it does flash both bootloaders thus completely bricking the phone.
If I knew I could just Jig it back like ive had to do twice when I used Odin One Click Id use the JH2 package or Cezars and be good.
But since im playing with bootloaders Im worried that it will completely brick cause One Click doesnt even work on my phone.
it only completly bricks the phone if it DOESN'T flash both boot loaders!
what happens when you use one click? a soft brick right? if you get ANY activity out of you phone at all your bootloaders are intact. and your jig will work for download mode after that then you can fix the soft brick by using the .tar package you usually use.
nothing but odin one click will flash both stock bootloaders
studacris said:
it only completly bricks the phone if it DOESN'T flash both boot loaders!
what happens when you use one click? a soft brick right? if you get ANY activity out of you phone at all your bootloaders are intact. and your jig will work for download mode after that then you can fix the soft brick by using the .tar package you usually use.
nothing but odin one click will flash both stock bootloaders
Click to expand...
Click to collapse
yes I know that im not trying to argue you with you... hahah
Im just saying that I dont know Im just a little hesitant as I havent used Odin One Click in a while, plus the fact that it'll be twice the nerve racking coming from Gingerbread Bootloaders.
That is the one thing that is a little scary, but I know if anything flashes on to the screen im good to go, but just a little nervous, but am seriously considering just using the Odin One Click, and just praying that it at least flashes the AT&T screen then off like it normally does.
But I dont know if it'll work the same with GB, I know its mostly in my head but hahahaha
EDIT: I havent used One Click in a while should I wipe my phone before? And secondly I assume disabling lagfix?
FLASHED ONE CLICK.... Going now I will keep it posted when I get back to stock.
the bootloaders though flash went well so I think im in the clear. Lets hope : D
UPDATE: It soft bricked, Jig--> now on Stock.
THANKS SO MUCH!
No problem man.
TRUST THE ZOMBIE!!
Well, you started the topic, so...
I have gone back and forth one cycle now. GR-10, then Odin one-click to ancient stock, (no master clear), reboot recovery by reinstalling packages (update.zip still there), flash Serendipity 6 (rom cwm still on the phone), then restore from my Nandroid backup, and update calls, texts, and some apps. Takes maybe 30 minutes. On continuum now, since it's the only JVH rom.
I'm wondering if I can skip a step. They say the GB bootloaders are fine with Froyo. If so, I should be able to go download mode, flash Onix in Odin (no auto reboot - since the kernel and rom will be incompatible), then pull the battery, boot to recovery by holding volume-up/power, and simply load the old nandroid backup (since I would have the same kernel - Onix - and same modem - JQ1 - as I had when I created the backup). The backup contains the Dalvik cache, IIRC, so I wouldn't even have to clear that. That's about 5 minutes, plus the time it takes to restore newer messages, apps, etc - maybe 15 minutes total.
Does anyone know why this wouldn't work in theory?
Soccer_Dad said:
Well, you started the topic, so...
I have gone back and forth one cycle now. GR-10, then Odin one-click to ancient stock, (no master clear), reboot recovery by reinstalling packages (update.zip still there), flash Serendipity 6 (rom cwm still on the phone), then restore from my Nandroid backup, and update calls, texts, and some apps. Takes maybe 30 minutes. On continuum now, since it's the only JVH rom.
I'm wondering if I can skip a step. They say the GB bootloaders are fine with Froyo. If so, I should be able to go download mode, flash Onix in Odin (no auto reboot - since the kernel and rom will be incompatible), then pull the battery, boot to recovery by holding volume-up/power, and simply load the old nandroid backup (since I would have the same kernel - Onix - and same modem - JQ1 - as I had when I created the backup). The backup contains the Dalvik cache, IIRC, so I wouldn't even have to clear that. That's about 5 minutes, plus the time it takes to restore newer messages, apps, etc - maybe 15 minutes total.
Does anyone know why this wouldn't work in theory?
Click to expand...
Click to collapse
please read post 3
i wrote it. i know its there..
so how do i go back to 2.2 for 2.3? ive had nothing but problems with 2.3 roms so i wanna gonna back.
You can flash directly from a 2.3 ROM to a 2.2 with no problem, as the bootloaders are backwards compatible. Flashing back to stock isn't really needed. However, you have to make sure that you do not, under any circumstances, flash a ROM with the file "sbl.bin" or you will brick your phone.
Did you try doing a search? There must be a dozen of these threads and a sticky on how to do it.
Superalpaca said:
You can flash directly from a 2.3 ROM to a 2.2 with no problem, as the bootloaders are backwards compatible. Flashing back to stock isn't really needed. However, you have to make sure that you do not, under any circumstances, flash a ROM with the file "sbl.bin" or you will brick your phone.
Click to expand...
Click to collapse
Who's going to check the rom to see if it has a sbl.bin file.
If you have any doubt what you're doing, use Odin1Click and flash back to stock 2.1. Then flash whatever rom you want whether it's stock froyo or a custom rom.
Sent from my SAMSUNG-SGH-I897 using XDA App
im on continuum 6 with i897 bootloader right now. do you know of a few roms offhand that i can flash to?
bornjamerican said:
Who's going to check the rom to see if it has a sbl.bin file.
Click to expand...
Click to collapse
Plenty of people? It's quicker.
I'm not saying that going back to stock isn't a good thing for new people, but it's really not needed.
was trying to flash one of the new gb betas from one of the not quite as new betas without doing the wipes. now i have the random colored pixel of death screen. probably doesnt help that i was below 15% either. im charging then gonna try a 2.1 or 2.2 odin restore.
let this be a learning experience for those who are trying to flash. make sure your battery is at least 50% (doesnt take but 20 or 30 minutes to get there from nothing) and make sure you wipe your cache/dalv before anything else. the options are within recovery mode. if you dont know how to do it, do enough research to make sure you know how to do it in your sleep.
well, after a 10 minute charge, i tried again, flashing jf6. i can now get into 2e. gonna let it charge for a half hour or so from the wall then try again with the latest beta.
Charging had nothing to do with it, you didn't flash GB bootloaders with the ROM.
Sent from my I897 using xda premium
b-eock said:
Charging had nothing to do with it, you didn't flash GB bootloaders with the ROM.
Sent from my I897 using xda premium
Click to expand...
Click to collapse
nope, of corse i didnt, because i already had the i897 att gb boot loaders from kh3. no need to take that extra risk when i already have them. but i never clarified that so my bad.
running I897UCJF6-final-OCD-REV0 (odin 1 click) twice fixed everything.
there are other cases on these forums though of the same issue, all suggesting that the lack of charge was the issue.
BloodSkin said:
nope, of corse i didnt, because i already had the i897 att gb boot loaders from kh3. no need to take that extra risk when i already have them. but i never clarified that so my bad.
running I897UCJF6-final-OCD-REV0 (odin 1 click) twice fixed everything.
there are other cases on these forums though of the same issue, all suggesting that the lack of charge was the issue.
Click to expand...
Click to collapse
FYI: Any leak after KF1 doesn't have the full BL's in it. So unless you are on a previous leak of GB for the Captivate, you have to flash BL's again!
That puts you back on stock eclair BL, you will need to flash KF1 bootloaders(the AT&T GB BL) and then your Preferred ROM.
Sent from my I897 using xda premium
BloodSkin said:
nope, of corse i didnt, because i already had the i897 att gb boot loaders from kh3. no need to take that extra risk when i already have them. but i never clarified that so my bad.
running I897UCJF6-final-OCD-REV0 (odin 1 click) twice fixed everything.
there are other cases on these forums though of the same issue, all suggesting that the lack of charge was the issue.
Click to expand...
Click to collapse
The charge doesn't have the pixel effect you had, that was all due to having incompatible BL's
Sent from my I897 using xda premium
Well, since you flashed jf6 (twice), you sure don't have GB bootloaders now. Use either cezar's one click bootloader package, or the full Odin version in my sig.
This has happened to me once - when I tried flashing the latest (as of two days ago) Platypus kernel over a Miui 1.10 installation.
My protocol to overcome this has been standard since I started playing around with ROMs:
1) 1-click restore using Odin (thank heaven I have one computer still running Windows).
2) Flash to GB bootloaders using the procedure described on the Serendipity VII site.
3) Re-flash the ROM.
Hasn't failed so far.
why do people still flash jf6? thats retarded.
What would you suggest in place of jf6?
mrhaley30705 said:
What would you suggest in place of jf6?
Click to expand...
Click to collapse
Something with up to date bootloaders, like any of the gingerbread leaks. Flashing old bootloaders only forces you to flash new bootloaders again... flashing bootloaders is the most dangerous part of flashing. Why not try and avoid flashing them as much as possible?