Related
Hey guys I am currently running Hamsterbread with X'Cals latest kernel.
And I have been reading everywhere that for flashing back to stock YOU MUST use Odin One CLick and if you use the 3-Button Fixed Odin you will brick you phone for good.
If I am a build 1010 and cannot use Odin One Click do y'all think this method would work:
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
Any Help will be GREATLY appreciated.
The only thing that could possibly happen to a later build phone using that odin one click is you will lose the 3 button combo (MAYBE) I flash and mod 3 captivates, 1 is a 1010 the other 2 are 1012 I have never used anything other than the one click to flash to stock, never even lost the button combo on ANY of those. But if you do lose the combo just use the odin with the button fix after you use the normal one.
The one with the button combo doesn't contain the second bootloader, so if you use that to go back to eclair from gb, you will have 2 incompatible bootloaders resulting in an unfixable BRICK. The normal one click contains BOTH bootloaders that is why you need to use it. But like I said once you are back on eclair and IF you have lost the button combo then you can use the other odin to get the combo back but only AFTER using the normal one click.
I don't know if that version of odin you posted contains both bootloaders so I personally wouldnt try it because of the reason I stated earlier.
studacris said:
The only thing that could possibly happen to a later build phone using that odin one click is you will lose the 3 button combo (MAYBE) I flash and mod 3 captivates, 1 is a 1010 the other 2 are 1012 I have never used anything other than the one click to flash to stock, never even lost the button combo on ANY of those. But if you do lose the combo just use the odin with the button fix after you use the normal one.
The one with the button combo doesn't contain the second bootloader, so if you use that to go back to eclair from gb, you will have 2 incompatible bootloaders resulting in an unfixable BRICK. The normal one click contains BOTH bootloaders that is why you need to use it. But like I said once you are back on eclair and IF you have lost the button combo then you can use the other odin to get the combo back but only AFTER using the normal one click.
I don't know if that version of odin you posted contains both bootloaders so I personally wouldnt try it because of the reason I stated earlier.
Click to expand...
Click to collapse
I just hear stories about Build 1010's and up who flash back to stock using Odin One Click and then they get a soft brick where the device flashes the AT&T screen then turns off.
Luckily i have a jig but I still dont really know what to do.
Dlev7 said:
I just hear stories about Build 1010's and up who flash back to stock using Odin One Click and then they get a soft brick where the device flashes the AT&T screen then turns off.
Luckily i have a jig but I still dont really know what to do.
Click to expand...
Click to collapse
First: no such thing as a "soft brick" that's a stupid name and it confuses people ... There is one kind of brick. When the phone does exactly the same as a brick. Nothing.
If you get a bootloop after using the one click I'm pretty sure the boot loaders have been flashed successfully (not 100% sure about that so wait for someone else to confirm/deny) in which case you could use another odin to recover from that.
If you weren't sure about how to return you really shouldn't have upgraded. As the deving for gingerbread is still in it's infancy. And might not be suited for daily use yet.
If you're still worried about all of it then just stay on gb and the devs will catch up and you will have more of options for roms/kernels, and maybe another way for later build phones to flash to stock with out the one click...
studacris said:
First: no such thing as a "soft brick" that's a stupid name and it confuses people ... There is one kind of brick. When the phone does exactly the same as a brick. Nothing.
If you get a bootloop after using the one click I'm pretty sure the boot loaders have been flashed successfully (not 100% sure about that so wait for someone else to confirm/deny) in which case you could use another odin to recover from that.
If you weren't sure about how to return you really shouldn't have upgraded.
If you're still worried about all of it then just stay on gb and the devs will catch up and you will have more of options for roms/kernels, and maybe another way for later build phones to flash to stock with out the one click...
Click to expand...
Click to collapse
I flashed GB when X'Cal released his beta and I was testing for him it is recently though that people are saying that you cannot use anything but Odin One Click. And I know what I am doing in regards to flashing Gingerbread and the kernels and such so thats why I upgraded.
I will try Odin One-Click if I ever need too, but if someone can confirm or deny the fact that if you get in a bootloop after flashing Odin One-Click the Bootloaders successfuly flashed?
I would guess thats correct and then Id just use my normal method and Jig it into Download mode.
Thanks again though.
Try and go look around samfirmware.com
and see if you you can't find the .pit flies that contain both bootloaders they should have every odin file. and use the full version of odin with the other corresponding files needed.
studacris said:
Try and go look around samfirmware.com
and see if you you can't find the .pit flies that contain both bootloaders they should have every odin file. and use the full version of odin with the other corresponding files needed.
Click to expand...
Click to collapse
Alright thanks
Sorry to be a noob but what exactly should I be looking for in specific? How do I navigate and find pit files with both bootloaders are they categorized? Thanks
I actually have no idea ... I'm looking now.
Look in the toolbox section at the top and navigate your way through the menus.
I'll post it if I find it.
studacris said:
I actually have no idea ... I'm looking now.
Look in the toolbox section at the top and navigate your way through the menus.
I'll post it if I find it.
Click to expand...
Click to collapse
Alright thanks so much.
And and we are looking for a pit file with both bootloaders?
And if we find one just use regular Odin and use the .pit file we find and like a JH6 or JH2.tar file for PDA.
One last thing although there is nothing wrong and I do have a jig, you think I should try flashing Odin One Click and see what happens? : D. I dont want too because my set up currently is un real haha.
I do not think odin one click is wise, it only flashes secondary boot loader not primary. If you use it worth out chanting the primary back you will have non matching primary and secondary boot loaders. Nothing good can come of that
Sent from my SGH-I897 using XDA Premium App
the pit file has nothing to do with the bootloaders. the bootloaders are in the .tar file which is inside the zip files on samfirmware.com
the pit file is for repartitioning, probably not needed, but probably worth doing just in case
mcord11758 said:
I do not think odin one click is wise, it only flashes secondary boot loader not primary. If you use it worth out chanting the primary back you will have non matching primary and secondary boot loaders. Nothing good can come of that
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Then how in the world do we flash back to stock with Gingerbread bootloaders?
As above I said I have always flashed back to stock using the Build 1010+ method with the JH2.tar pda file. But I dont know if that will work.
Can someone who has successfuly flashed back to stock with Gingerbread Bootloaders please create like a guide hahahah
Pirateghost said:
the pit file has nothing to do with the bootloaders. the bootloaders are in the .tar file which is inside the zip files on samfirmware.com
the pit file is for repartitioning, probably not needed, but probably worth doing just in case
Click to expand...
Click to collapse
Ya thats what I thought has anyone found a firmware .tar file with both bootloaders and post it so we can create a way for people to successfuly flash back to stock with GB bootloaders.
Dlev7 said:
Ya thats what I thought has anyone found a firmware .tar file with both bootloaders and post it so we can create a way for people to successfuly flash back to stock with GB bootloaders.
Click to expand...
Click to collapse
every firmware found on samfirmware.com has the boot loaders.......
Alright so we just have to get a .tar file form one of the firmwares at Samfirmware.com and put that in the PDA file of the Original Odin and flash normally?
This particular issue its going to explode. Get ready for the omg odin one click back from gingerbread, now my phone is unresponsive
Sent from my SGH-I897 using XDA Premium App
Dlev7 said:
Alright so we just have to get a .tar file form one of the firmwares at Samfirmware.com and put that in the PDA file of the Original Odin and flash normally?
Click to expand...
Click to collapse
yep. pretty much. i would go ahead and select the box that says repartition and include the 512.pit file so that it wipes it all....
mcord11758 said:
This particular issue its going to explode. Get ready for the omg odin one click back from gingerbread, now my phone is unresponsive
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Ya I know, there is currently nothing wrong with my phone and no need but I just wanted to know to help other if the are flashing back to stock currently, and also to help me in the future.
I am just confused if you cannot use Odin One-Click or the method I used above to go back to JH2 what are we supposed to do
I just downloaded the jf6 firmware rar but I can't extract it because it's password protected??
studacris said:
I just downloaded the jf6 firmware rar but I can't extract it because it's password protected??
Click to expand...
Click to collapse
Password is either:
www.samfirmwares.com
or
samfirmwares.com
Here it goes,
My phone had everything working including 3-button combo.
I successfully upgraded to Gingerbread about a week back and tried Mikey's rom and Icezar's rom.
Last time I was running Continum5.2, decided to downgrade to cognition 4.3.2, without any apparent reason.
Since some one said that you can run Froyo ROm with Gingerbread bootloaders, I decided to keep Gingerbread bootloaders.
Returned to stock JF5 using Icezar's safe method. (The one that does not modifies any boot loaders). Successfully booted to stock and then rebooted to recovery using vol up and power.
Installed Clockwork (2.5) using update.zip. (reinstall packages 2-times), and my phone is in clockwork recovery.
Flashed Cognition 4.3.2, flashed successfully.
Reboot the phone. Nothing happens. It's a hard brick. Have tried almost all the methods to go to download mode, but still unsucessful. I don't see anythng on screen, no light nothing.
Where I went wrong?
Can some one guide about jtag method.
bigbyte.me said:
Here it goes,
My phone had everything working including 3-button combo.
I successfully upgraded to Gingerbread about a week back and tried Mikey's rom and Icezar's rom.
Last time I was running Continum5.2, decided to downgrade to cognition 4.3.2, without any apparent reason.
Since some one said that you can run Froyo ROm with Gingerbread bootloaders, I decided to keep Gingerbread bootloaders.
Returned to stock JF5 using Icezar's safe method. (The one that does not modifies any boot loaders). Successfully booted to stock and then rebooted to recovery using vol up and power.
Installed Clockwork (2.5) using update.zip. (reinstall packages 2-times), and my phone is in clockwork recovery.
Flashed Cognition 4.3.2, flashed successfully.
Reboot the phone. Nothing happens. It's a hard brick. Have tried almost all the methods to go to download mode, but still unsucessful. I don't see anythng on screen, no light nothing.
Where I went wrong?
Can some one guide about jtag method.
Click to expand...
Click to collapse
U got a jig?
Sent from my Captivate using XDA Premium
Zig won't help as nothing is helps only in case of Soft brick.
BTW i figured out where I went wrong, The cognition ROM contains seconday bootloader. So when I flashed it I ended up with Gingerbread primary and Froyo secondary bootloader and hence the Brick. I request all the rom dev to mention at the start of their post if their ROm contains bootloaders.
bigbyte.me said:
Flashed Cognition 4.3.2, flashed successfully.
Click to expand...
Click to collapse
^ That's where you went wrong. Cog flashes sbl. You ended up with one bootloader from 2.3, and one bootloader from 2.2.
There are videos of how to unbrick a perma-bricked phone with a riff box jtag unit on youtube. It'll require you to remove the motherboard and blow $150 or so on a riff box, though.
or you send it to someone with the equiptment, like mobiletechvideos.com and not learn about riff/boxing and spend less money... and and and...
or because it doesnt boot and they cant prove you voided your warranty send it back!
So, this could be avoided doing what?
-Going back to GB stock and from there going back to froyo stock (without 3 button fix)?
I don't think moviletech does crappys something about the solder points too close together.
Edit: but could be wrong.
Sent from my GT-I9000 using XDA Premium App
i was in a similar situation, no 3 button nothing worked my phone wouldn't even power on
but the one method that saved me was this,
Remove battery, SIM card, SD card (if present)
Connect USB cable from computer
While holding down up & down volume, re-insert battery
may be this could help you too.
mobile tech does and has been for over a month, and the first few people are free!
i was able to get myself out of a hard brick, (no buttons no nothing working)
by removing the battery
count to 5
put battery back
DO NOT TOUCH ANY BUTTONS!!!! DO NOT!!! DONT !!!
then put in jig
for me if i touched any buttons the jig would not work.
other methods wouldnt work either.
worth a shot.
You are not the first person I have read about that is not aware that cognition overwrites the boot.bin, and bricked because they flashed it after gingerbread.
Sent from my SAMSUNG-SGH-I897
You messed up with the Bootloader.
Atually I always believe Froyo ROMs should not include Sbl.bin
1tontomato said:
You are not the first person I have read about that is not aware that cognition overwrites the boot.bin, and bricked because they flashed it after gingerbread.
Sent from my SAMSUNG-SGH-I897
Click to expand...
Click to collapse
It overwrites the sbl.bin not boot.bin.
DG put it in so people would always have a 3 button fix(which is contained in the secondary bootloader. sbl.bin)
but with the arrival off the new gb bootloaders means flashing this with those will result in a brick. Guaranteed.
studacris said:
It overwrites the sbl.bin not boot.bin.
DG put it in so people would always have a 3 button fix(which is contained in the secondary bootloader. sbl.bin)
but with the arrival off the new gb bootloaders means flashing this with those will result in a brick. Guaranteed.
Click to expand...
Click to collapse
Yea your right it is the sbl.bin. It was a good idea before gingerbread, but I think it's time has passed especially since it's really easy to get past not having a button combo with a jig. A bad combination of bootloaders is a "brick" for sure.
Sent from my SAMSUNG-SGH-I897
amtrakcn said:
You messed up with the Bootloader.
Atually I always believe Froyo ROMs should not include Sbl.bin
Click to expand...
Click to collapse
Actually, Now I believe that all rom's Froyo or ginger should include either both bootloaders or none.
bigbyte.me said:
Actually, Now I believe that all rom's Froyo or ginger should include either both bootloaders or none.
Click to expand...
Click to collapse
I say none. ANYTIME you touch bootloaders there is a chance of hard bricking. If they don't have any, worst case is a "clay" (soft brick)
TRusselo said:
i was able to get myself out of a hard brick, (no buttons no nothing working)
by removing the battery
count to 5
put battery back
DO NOT TOUCH ANY BUTTONS!!!! DO NOT!!! DONT !!!
then put in jig
....
Click to expand...
Click to collapse
Perhaps I;m not out of the woods yet but a wrong action in ODIN had HB'd my Cappy. Your steps got me back to DL mode. Perhaps it is the 5 count. Patience not being my strong pt I had "not waited" until your recommendation.
I was trying from Continuum5.3 to get back to eclair so to carrier unlock when I made an ODIN error. Still need do that but for now I'll just be thankful that it lives, and move only forward..
its the not touching buttons that makes this trick work
if you replace the battery, what is your normal instinct?
try the power button! or try the button methods...
you are the first to confirm my trick!
congrats!
http://forum.xda-developers.com/showthread.php?t=731989
Use this to get back to stock safely!
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE
use the thanks button!
Hmm very interesting...
I thought your trick worked because it was a screw up in the param.lfs not a bootloader brick, guess not.
im surprised too...
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..
ok i see since it has been so long since all the rogers development started people dont really remember about all the rainbow problems and how they were fixed and how the fix needs source code.
we now have bootloaders available in leaks from samsung. they are needed with the stock kernels that come in the leaks to avoid rainbow garbage. i am providing the bootloaders to be flashed in heimdall without having to flash a whole rom.
i would like to make this explicitly clear that if this bricks your phone i am not to blame. there is a significant risk when flashing bootloaders! though the infuse seems to have safety measures i strongly recommend only flashing once. and if your phone becomes a brick you will need to solder things to the phone to fix it via j-tag or adam outlers unbrickable mod. be cautious! dont flash boot.bin without sbl.bin, dont flash sbl.bin without boot.bin, dont mix up the partitions, and if the phone bricks i dont want to know about it unless you want to pay me to fix it!
heimdall package
http://www.multiupload.com/GXUTF4QCJX
odin package (untested)
http://www.multiupload.com.... REMOVED May be failing to flash. very dangerous situation...
bootloaders for heimdall to be added through the "flash" tab (unzip first! ibl/pbl-boot.bin, sbl-sbl.bin)
http://www.multiupload.com/NAIA23JZL1
good luck!
Thanks for posting this. Hopefully it will help out with leak questions that tend to get asked over and over again.
Sent from my SAMSUNG-SGH-I997
Yeah. Thanks for posting, Dani.
do you know if there its any difference in bootloaders amongst different gingerbread leaks?
I have been running the first leaked gingerbread's bootloaders since Prezkit gave them to us and have had zero issues. I think it was kk1? I've been taking an "if it ain't broke" stance. its going good!
MattSoRaven said:
Yeah. Thanks for posting, Dani.
do you know if there its any difference in bootloaders amongst different gingerbread leaks?
I have been running the first leaked gingerbread's bootloaders since Prezkit gave them to us and have had zero issues. I think it was kk1? I've been taking an "if it ain't broke" stance. its going good!
Click to expand...
Click to collapse
there is difs. but I couldn't tell you what. I saw posts by Linux bozo who did binary diferencials but I don't see any difference.
I know the bootloaders have a counter for customer kernels. if you flash the parameters.ifs from the ultimate unbrick it resets it. I also know they changed the galaxy s 2 bootloaders so it was harder to reset the counter so don't expect to be able to reset it when the official update comes along. I also have been using the "if it ain't broke " theory and honestly don't remember which I am using. the packages here are uckk3. if people can test if the counter can still be reset by flashing param.ifs let me know. ill post older bootloaders if it can't otherwise I can't think of any reason to pick one over another.
If i am flashing the bootloaders via odin does the .tar file go in the pda slot. thank you for this.
Sent from my SAMSUNG-SGH-I997 using xda premium
bigbadwolf311 said:
If i am flashing the bootloaders via odin does the .tar file go in the pda slot. thank you for this.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
yes. that's how I would do it. the PDA slot seems to be automatic as far as partition sorting. the phone slot is for modems but if a modem is included in a package for the PDA slot it flashes just fine. the bootloaders are in the PDA packages normally so that's how I would do it.
please report results because I don't run windows and did not test that package.
I will report back once i get around to flashing the bootloaders. Thanks again for this.
Sent from my SAMSUNG-SGH-I997 using xda premium
Dani897 said:
there is difs. but I couldn't tell you what. I saw posts by Linux bozo who did binary diferencials but I don't see any difference.
I know the bootloaders have a counter for customer kernels. if you flash the parameters.ifs from the ultimate unbrick it resets it. I also know they changed the galaxy s 2 bootloaders so it was harder to reset the counter so don't expect to be able to reset it when the official update comes along. I also have been using the "if it ain't broke " theory and honestly don't remember which I am using. the packages here are uckk3. if people can test if the counter can still be reset by flashing param.ifs let me know. ill post older bootloaders if it can't otherwise I can't think of any reason to pick one over another.
Click to expand...
Click to collapse
I've been using the UCKJ2 bootloaders since they came out with no issues.
Entropy512 said:
I've been using the UCKJ2 bootloaders since they came out with no issues.
Click to expand...
Click to collapse
Same here.
Sent from my SAMSUNG-SGH-I997 using xda premium
bigbadwolf311 said:
I will report back once i get around to flashing the bootloaders. Thanks again for this.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Wonder if u can give me directions for the odin method. Should i put it in download mode like im flashing back to stock? Can i Flash this over a custom rom?
schmidtty661 said:
Wonder if u can give me directions for the odin method. Should i put it in download mode like im flashing back to stock? Can i Flash this over a custom rom?
Click to expand...
Click to collapse
don't select repartition, no need for a pit, the rom shouldn't matter, the file should go in the PDA slot. remember I haven't tested it in Odin. I don't run windows and have little interest in using Odin for anything. phone needs to be in download mode just like flahong a rom. it should only take a second or two to flash. good luck
Cool i should be able to figure this out. Thanks for the quick response.
It didn't work. I had auto restart, f.reset and the PDA slot checked after i opened the file in the PDA slot and after clicking start it just sat at setup for 45 min until i gave up and flashed back to stock. I had to pull the cord while in download mode and the screen turned black with green dots so i had to flash blindly. I tried it twice and the same thing. Has anyone else tried this?
schmidtty661 said:
It didn't work. I had auto restart, f.reset and the PDA slot checked after i opened the file in the PDA slot and after clicking start it just sat at setup for 45 min until i gave up and flashed back to stock. I had to pull the cord while in download mode and the screen turned black with green dots so i had to flash blindly. I tried it twice and the same thing. Has anyone else tried this?
Click to expand...
Click to collapse
I have a bunch of downloads but nobody reported anything at all till now.
ill pull the Odin version for now. try it in heimdall. its not any harder to use.
Can you post an odin package.
I had an Odin package. I got a few downloads, didn't get any people thanking for it, didn't get any positive feedback that it worked and had one user report problems, see the last couple posts. I pulled the file for lack of evidence that it worked. I don't run windows and prefer heimdall so I haven't tested it in Odin. sorry but I suggest you either flash an entire rom leak then flash a non secure kernel through Odin ( any custom kernel should do also flashing back to stock should also do just fine) and then flash a rom or learn heimdall which works on windows as well as Mac and Linux. I would have done a oneclick package but it still requires the installation of the heimdall back end and I figured it was really no harder to just use the heimdall package system.
any chance of relink thats not at multiupload?
edit: disregard, found a workaround. might be useful in future tho.
I was caught in a boot loop and tried to re flash, when in my haste I forgot that Odin will recheck partition when loading .Pit files (pretty lame feature)
Still it was my fault for clicking start in haste.
**phone was partitioned, and would not go into download mode, it was stuck in a screen that said "Firmware update error, please restore in Kies", but it wouldn't connect to kies**
I sent my phone to XDA member Connexion2005
http://forum.xda-developers.com/member.php?u=1602851
I haven't got it in my hands yet, but he just told me it was fixed, I can't wait to get it back and leave it the hell alone (until someone makes CM7 or better work on it)
anyhow, this is out there so if you do what I did (DON'T) there's a solution. Set me back $50 plus shipping to TX from NYC but still, I didn't have to get a whole new phone.
for 50 bucks im sure k0nane would have made an uberfixit tar :/
shabbypenguin said:
for 50 bucks im sure k0nane would have made an uberfixit tar :/
Click to expand...
Click to collapse
Absolutely.
shabbypenguin said:
for 50 bucks im sure k0nane would have made an uberfixit tar :/
Click to expand...
Click to collapse
Please elaborate. Not finding much info on this "uberfixit", but it sounds like it's some method of re-creating the stock filesystem that's flashable in odin?
I was putting this out there, because I'm not the only one that this will happen to.
yea it happens when you repartition, an uberfixit requires a complete dump of the phone and quite a bit of time, but will completely fix what you described
the problem with repartitioning is that it wipes the phone clean and then starts to reinstall everything, problem is neither one of teh tars has the full dump (we do it for the sake of saving actual bricks)
knowing someone who can jtag is great we have had a few epic 4g touches that crashed and burned and were saved via jtag.
shabbypenguin said:
yea it happens when you repartition, an uberfixit requires a complete dump of the phone and quite a bit of time, but will completely fix what you described
the problem with repartitioning is that it wipes the phone clean and then starts to reinstall everything, problem is neither one of teh tars has the full dump (we do it for the sake of saving actual bricks)
knowing someone who can jtag is great we have had a few epic 4g touches that crashed and burned and were saved via jtag.
Click to expand...
Click to collapse
You may not remember, but I did go onto your IRC and spoke with you regarding this issue.
oh sorry, the irc channel we have is for a bunch of devices currently we house blaze 4g, attain 4g, conenct 4g, lucid and optimus m+ owners. so i probably thought you were an attain owner since we have had a good number of attain owners repartition as well :/
shabbypenguin said:
oh sorry, the irc channel we have is for a bunch of devices currently we house blaze 4g, attain 4g, conenct 4g, lucid and optimus m+ owners. so i probably thought you were an attain owner since we have had a good number of attain owners repartition as well :/
Click to expand...
Click to collapse
it's all good, bottom line is I f'd up my device, but now its fixed.
um...yeah...
So i did the exact same thing as you... Been trying to find anyone who can help me out. Is there anyway I can fix it myself? I haven't found a single place in my whole state that can fix the problem. If at all possible, I'd like to avoid sending it out for repair.
So how do I get this uberfixit?
I stupidly re-partitioned using Odin, also: I did not realize that Odin re-checked the check box -even after unchecking- when a new pda file was loaded. My bad. Totally though it was bricked until i was able to flash this stock gingerbread rom, but now kies says that my Blaze S does not qualify for upgrades... Did the re-partitioning do this?
I can no longer get to the recovery screen, although if I restart my blaze while connected to a pc via usb, it does allow the "re-install OS?" page to display, and I can get to recover from there: But absolutely no more access to the recovery "menu" which allows me to wipe cache/restore to factory/etc.
Just Odin cwm back then flash away
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Thanks for the quick reply; I will try that right now: My fingers are crossed.
2vivid said:
Just Odin cwm back then flash away
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
thomassino said:
Thanks for the quick reply; I will try that right now: My fingers are crossed.
Click to expand...
Click to collapse
It's just a soft brick, I have done that at least 10 times.
Will you make this?
k0nane said:
Absolutely.
Click to expand...
Click to collapse
Hi, k0nane I too have bricked my phone due to not unchecking re-partition. Now no matter what I do the phone displays the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. It is frustrating. I will certainly pay you if you make a fix for this that I can flash in odin! I don't care if it wipes my phone completely as I was trying to flash a new rom anyways. Please reply I'm desperate to get this thing working again.
runboyrun said:
Hi, k0nane I too have bricked my phone due to not unchecking re-partition. Now no matter what I do the phone displays the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. It is frustrating. I will certainly pay you if you make a fix for this that I can flash in odin! I don't care if it wipes my phone completely as I was trying to flash a new rom anyways. Please reply I'm desperate to get this thing working again.
Click to expand...
Click to collapse
That's a soft brick.
No need to pay anyone lol just pull the battery and go back to download mode (for Odin) again and revert back to stock. A quick search through 'bricked' type threads would have netted this info :thumbup:
Sent from my SGH-T769 using xda app-developers app