yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] movrshakr:
The Toolbox has not changed lately.

Inflammatory allegations without one shred of specific evidence reflects extremely poor taste (at a minimum) or an intent to harm another developer.

Do you know that these 3 people did not do one of the known things that will brick your phone? How did it happen? At which step in the process? What was their starting state? And you even admit you do not know if they used the right version.

Finally, we all know that phone bricking "happens." People brick their phone all the time when not using AIO. But no, you allege it is AIO that is causing it.

And if it WAS caused by AIO, why are you not helping to feed back the specifics so the issue could be addressed?

Sad, sad, sad.
[Captivate Android Development] AdamOutler:
Dude... I don't have the answers to your questions... I've just been unbricking devices. I'm leaving feedback.

Also, bricking does not just happen

[Youtube]DcknyMZUfhk[/YouTube]

I'm not making allegations. I'm not slandering... I'm leaving feedback. Plain and simple.
[Captivate Android Development] stayintwisted:
I have used the toolbox three times in the last week just because it works so well and easily for what I was doing,,and I have to say that that might have just been feedback but without any more information given it was some really harsh feedback,, would not a PM have been more reasonable given that you are both devs and you had nothing specific to say
[Captivate Android Development] rkkaranrk:
i have used thie when i was on eclair/foryo and never faced the issue, When you are leaving Feedback be more specific how did the bricked there phone ?
[Captivate Android Development] bay_wolf:
I've never updated this program for use with gingerbread ROMs. So, if users are using this to go to and from (back to stock) gingerbread ROMs then I will warn them that it could cause issues. There is a warning in the OP about this issue. I do not foresee this being updated to support gingerbread ROMs as I have a lot on my plate right now and I lost all the coding for this when I switched to a new computer (forgot to back it up).

For anyone wanting to go to/from froyo ROMs this should still work perfectly without causing bricks but as with anything there is a chance it could cause an issue so use it at your own risk.
[Captivate Android Development] AdamOutler:
They're not my phones. I have no clue. They just said aio toolbox. They sent the devices to me for UnBrickable mod. I did the mod and gave the phone back in operating condition. That is as speciffic ad I can be. I do about 3 of them per week. I got three last week which were all from aio. I can't be more speciffic. I'm noting patterns. Maybe with more information it can be useful. This is just 3 random instances within a short time period.
[Captivate Android Development] 4-2ndtwin:
Just my 2 cents, stating the obvious...

More than likely those that are bricking their phone using this AIO Tool have the Gingerbread Bootloaders installed and are choosing to go back to Stock, but are making the mistake of choosing the "3 Button Fix return to Stock" (only one bootloader -> sbl.bin) that is included as one of the 2 choices to get back to Eclair, the other choice being the "Recommended" way (includes both of the stock bootloaders) is the option that they should be selecting.
[Captivate Android Development] xavier55:
will this unlock the pre installed version of 2.2 on my phone i tried the super one click but no luck
[Captivate Android Development] AdamOutler:
You're telling me that AIO flashes a SBL without flashing the PBL, Repartitioning, Params and PBL? That's total crap. We have 4 versions of bootloaders out there.

Seriously.. this needs to be fixed now, or AIO needs to come off the sticky list.

Never flash a bootloader without all of the bootloaders. That's piss poor on the developers part. Going through my PMs, this IS the problem. "I flashed back to stock with AIO to get 3 button back".

If you'd like the IBL+PBL, PARAMS, and PIT, I can provide this for you. all of my One-Clicks contain bootloaders. You can unzip the one-click and grab the bootloaders from the tar.gz contained within at this location http://files.teamkomin.com/
[Captivate Android Development] conantroutman:
Perhaps that warning should be made a little larger and the thread title updated to be a little more descriptive..

We all know how people have a tendency to press buttons first then read the instructions later, while that may well be their own fault I'd like to think our developers are doing everything they can to make any possible risks clear from the outset...
[Captivate Android Development] movrshakr:
All I know is AIO was my saving grace when I was starting out with my phone. I had read and read and read, and still could not sort out the process in my head.

As we know now, there are about 13 ways to do these things, so reading bits and pieces where one is talking about method A (but doesn't say that) and another is talking about method B (but doesn't say that), and here you are trying to meld those together in your head when they don't belong together--well, AIO solved that.

GB came along and confused the bootloader situation AFTER this tool was developed.

A little bit of what I am seeing proposed here reflects the situation we seem to encounter so often these days is to make things more inconvenient for many in order to protect a few. Sorry, I don't subscribe to that. I do however, think a strong warning in the OP would be appropriate.

Just as an example of this phenomenon, I recently discovered that Carbonite does not backup ANY shortcuts. Their rationale is that if they are restored, they might no longer point to the right place and confuse some people--so they don't even back them up. Hurt the many to avoid a confused few.
[Captivate Android Development] AdamOutler:
The proper fix is to add the rest of the bootloaders (PBL, PARAMS and Repartitioning.. I also include a duplicate SBL2 in my flashes) into the current flash which simply flashes an SBL over what is available.
[Captivate Android Development] conantroutman:
Yep, agreed, that would be the ideal solution but as the OP has made it fairly clear that this won't get updated I think the best we can hope for here is for it to be labelled as a tool that is not suitable for use with GB....
[Captivate Android Development] 4-2ndtwin:
AdamOutler and conantroutman,

I agree with u both, but in the defense of Bay_wolf's Tool, he did build this and share it in the days when there was only Eclair or Froyo. There was no Gingerbread in sight. And the 3 button fix that was put together by designgears was around way before then. Things change fast in the phone world, so I can understand where it is difficult to go back and modify certain warnings so that everyone will see them. But again, in defense of Bay_wolf, the warning about possible bricking with the 3 button fix has been there since shortly after the gingerbread bootloaders came on the scene.

And no disrespect to designgears, but maybe his thread on the 3 button fix needs to be pulled as well if this is such a problem for people who are failing to read before the click.

Again, my 2 cents.

Sent from i897ucki2
[Captivate Android Development] conantroutman:
Totally agree, I mean absolutely no disrespect to the OP and am not in any way blaming him for any damage caused to someone's device.

It's just that when situations like this arise there is an obligation on the part of the developers and the moderation team to make sure the risks are made as clear as possible.

I'll have a look at DG's thread as well and see if any amendments are needed over there.

Edit;

If you check DG's OP I think the risks are pretty clear from the start.. :D
[Captivate Android Development] 4-2ndtwin:
+1

Thanks

Sent from i897ucki2
[Captivate Android Development] 4-2ndtwin:
This would be the corect fix for designgears original 3 Button Fix as well.

Sent from i897ucki2
[Captivate Android Development] AdamOutler:
Yep. They're in heimdall one-click UCKB1. The PBL from UCKB1 and the SBL from the fix would do the trick.
[Captivate Android Development] movrshakr:
Apparently you did not read his message of just yesterday, 10-3-11, that he has lost the code for this. I think that means "add[ing] the rest of the bootloaders (PBL, PARAMS and Repartitioning" is, like, impossible.

---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------

Is this not open source? Why don't YOU do it? (Assuming you are talking about something other than AIO which is now lost.)
[Captivate Android Development] votum:
Or you could download the proper one click, like this one: http://xdaforums.com/showthread.php?t=1285616

Rename it "ODIN" and overwrite the one click in the AIO folder wherever you installed it. Now it opens the correct one.
[Captivate Android Development] movrshakr:
Dang. That simple? Somebody independently confirm that this would make AIO compatible with Gingerbreaded phones?
[Captivate Android Development] perroschatos02:
Will this work with i897uckb2?
[Captivate Android Development] 4-2ndtwin:
Yes, but you will probably have to return to stock 2.1 first, because of the 3e Recovery that comes with the kb2.

If you do return to stock, use the tab that is marked "Recommended"

Don't use the "3 button fix" flash to stock.

And this is not for use to go to Gingerbread. (Read the Warning in the OP)
[Captivate Android Development] perroschatos02:
So I would have to use the return to stock tab? Once in odin do I have to master clear?
[Captivate Android Development] 4-2ndtwin:
Master Clear -- That is up to you. It's the same as going into the Settings and doing a Factory Reset.

If you try to flash the CWM Recovery on the kb2 that has the 3e recovery it won't take. The Eclair has 2e recovery that doesn't require signatures.
[Captivate Android Development] perroschatos02:
Ok thanks, so once in odin just select the start tab and I should be ready for rooting and flashing?
[Captivate Android Development] 4-2ndtwin:
The 1 click (Recommended) Odin will take you back to the out of the box Stock Eclair 2.1 that the Captivate was originally released with. After you hit the Start on Odin for this and you get fully booted up with the 2.1 then go into the Settings and enable Debugging and then, yes, you can proceed from there.
[Captivate Android Development] perroschatos02:
Thanks appreciate the help.
[Captivate Android Development] perroschatos02:
Do I have to been in download mode, or with the phone just on?
[Captivate Android Development] 4-2ndtwin:
Phone on and debugging enabled. Then the AIO Tool will do the rest.
[Captivate Android Development] Bajanman:
Thanks

Nice work on that..
[Captivate Android Development] stayintwisted:
just finished using this tool to take two captivates back to eclair from gingerbread,,repeatedly,,guess it is safe IF YOU FOLLOW INSTRUCTIONS,, I do not know enough about this to offer more than that like almost everything else in this section if you dont read the OP and follow instructions you can brick your phone,, and I really doubt there will ever be a cure for stupidity ( definition of stupidity= intentionally ignorant)
[Captivate Android Development] Thuneau:
Just saying thanks.

Great tool. I installed a Gingerbread ROM that remapped my buttons and thus made selecting Restore Packages impossible. Also the phone would not go into download mode regardless of button/battery/USB combinations. I spent half my Saturday struggling with it. I thought I will have to make the resistor jig just to get it to boot to restore.

This tool restored me to Eclair and then allowed me to load a correct GB ROM.

This was definitely worth the donation I sent.
[Captivate Android Development] 4-2ndtwin:
Just heed this warning from the OP about Flashing back to Stock when you are already running GB Roms...

"Warning: Using the 3 Button Fix ODIN can brick your phone if you have Gingerbread bootloaders."

MY EDIT: "can" should read

WILL FOR SURE
[Captivate Android Development] Calamity88:
may i know how can i check the bootloader version? my friend has forgotten the unlock pattern and desperately finding a solution, so i thought if i could just help her root+flash along..is there anyway i could check which version would it be?
[Captivate Android Development] jmtheiss:
If your friend is on a Froyo Rom, and the V+/V-/Power combo gets them into recovery, they're most likely on the froyo/eclair bootloaders (and if the first screen is the AT&T world screen).

If your friend is on a GB Rom with the same key combo and first screen, it's most likely the i897 bootloaders.

If your friend is on a GB Rom with a "Galaxy S i9000" screen (or something similar) and Vol+ and Power get them to recovery, they most likely have the i9000 GB bootloaders.

Here's my suggestion, assuming your friend has the important stuff on their phone backed up:

If your friend's three-button combination isn't working right, flash a Gingerbread stock package with the bootloaders included. This will 100% fix the three-button issue, and you won't have to worry about it again. The plus of this is that you'll be able to do both Gingerbread and Froyo roms with the GB bootloaders.

However, if your friend isn't comfortable with that, look for Designgear's one-click ODIN back to stock. DO NOT USE ANYTHING THAT TALKS ABOUT A THREE-BUTTON FIX (at least for right now).

If, AND ONLY IF (All caps because it's really that important), after flashing the one-click back to froyo stock from designgears, you discover that the phone's three-button combo isn't working, should the thought of a three-button fix enter your mind. Even then, I would still recommend just flashing the GB bootloaders. The three-button fix was marginally good at the time it was necessary, but now it's largely useless and causes a lot of unnecessary heartache.

Just my two cents, though.
[Captivate Android Development] Calamity88:
Thanks for the reply :) its a pain cause most of the time i'm handling my desire hd phone, which seems so much simpler, thats why i wanna make sure i get the things right first before doing anything. I have few more questions still if you dont mind.. ( i'll only get the phone tmr, so thought that i might wanna download neccesary files first, since my net here is slow)

1. If say the phone is indeed on a froyo bootloader, would flashing [Gingerbread stock package with the bootloaders included] do harm to it? I'll definately choose the easier way since she doesn't know anything about this, and i've been wanting to flash CM7 rom from start.

2. After reading through few thread, i found that AIO Captivate toolbox seems to be the simple method out there, but i notice that it's only compatible with froyo. Does that mean if the phone is gingerbread but on Froyo bootloader it wont work?
[Captivate Android Development] jmtheiss:
Please check your PM - I've replied there to avoid clogging up this thread.
[Captivate Android Development] reinbeau:
Thread closed

Due to reported issues regarding confusion over bootloaders, Froyo and Gingerbread, this thread is closed and unstuck until such time as the issues are resolved.
[Captivate Android Development] TommyZee:
In the beginning God created the heavens and the earth.

Needed this months ago, THANKS for sharing :cool:
[Captivate Android Development] KMan94:
I can find it on my pc just fine. I am looking in the system/app folder on the phone. I guess I think its there on the phone somewhere, I just don't know how to find it, get it in my apps drawer and run it. I'm missing something dumb I know.
[Captivate Android Development] soritong:
Mine appears to be just sitting at the "finding update package" screen for quite a bit. Is this normal?

Edit: Nevermind - I pulled the battery and tried it again. Seems to be working now.
[Captivate Android Development] AtoZ0to9:
teamkomin mirror is blazing fast...
[Captivate Android Development] bay_wolf:
Just wanted to say thanks to team komin again for the mirrors.
[Captivate Android Development] connexion2005:
Lol. I'm guessing this is sarcasm. I was getting 80KB down. Not that I will even complain a bit about them hosting it! Thanks to Team Komin for offering another mirror. Still going to do the video review on this btw. Just in the hospital currently for a bebe to be born...
[Captivate Android Development] bay_wolf:
No rush. Especially with a baby being born. Haha. I think having a review of the program with a birth happening in the background would lose a few viewers. :eek:
[Captivate Android Development] tazman171:
LOL, funny stuff there! :cool:
[Captivate Android Development] max_82:
I think it's not sarcasm but teamkomin mirror is very fast. I got 600 kBps. One question, why the file size of 2.2 is smaller than 2.1.1? Can you explain it? Thank you anyway.
[Captivate Android Development] AtoZ0to9:
I was getting nearly 1mb down....
[Captivate Android Development] bay_wolf:
I ended up duplicating some of the driver files in 2.1.1 and removed them in 2.2.
[Captivate Android Development] bay_wolf:
I need opinions on the next build. The screenshot below is the look for the next version. What do you guys think?

From that menu you will branch off into the sub menus. Something like this:

Done or closing the window will take you back to the main menu.
[Captivate Android Development] Oxicottin:
2.2 worked perfectly.... This is the first time I have installed a custom ROM "Cognition 3.04" and everything went smooth. I have read the thread and someone had suggested a progress bar or something and that is a very important fetcher that is needed. I think the next version your working on looks easier to understand due to the pop outs ect.

Since this is my first time doing this and from here im lost as to what if I want another ROM instead of the one I installed, What do I do? Do I go threw the entire process again or do I use the rom manager and somehow install it from there.

Once again great gob on the app and it is the most useful app for us that don't know a lot...

Thank,

Chad
[Captivate Android Development] bay_wolf:
Yep, for new ROMs is best to just go through the whole process again. And the next version would have progress bars included.
[Captivate Android Development] Oxicottin:
Can i just uninstall rom manager then since i wont use it again.
[Captivate Android Development] bay_wolf:
I don't know if it's required for anything else. I'd leave it just in case but if it bothers you just uninstall it.
[Captivate Android Development] unnamedsoul91:
I dont know why? but when I use ver. 3 Button Fix. after my phone reset it show a kenel panic download mode in yellow and some row on them???
[Captivate Android Development] bay_wolf:
At which step does this happen? and what specifically does the screen on your phone look like?
[Captivate Android Development] joebednarz:
3BF

Thanks for your work on this... I've flashed a previous phone and am looking forward to what looks like a much easier process thanks to your program!

So, question... do I need both v2.2 and 3BF?
[Captivate Android Development] bay_wolf:
You just need one of them.
[Captivate Android Development] REKnight:
Just to follow up, I ended up rooting with SuperOneClick, so I'm good. Thanks for the help.
[Captivate Android Development] unnamedsoul91:
click "start" on odin, after odin say "reset" my phone reset and stuck at the screen that has red text on the upper left side with a little android behind the text and some yellow text on the upper right side saying: "Kernel panic, upload mode".
[Captivate Android Development] seemles:
Absolutley Amazing!!! thanks for making ROM life easier!:)
[Captivate Android Development] buttstache:
I just used this application to flash stock and install Cognition 3.04. Couldn't have been easier. Thank you so much for this!
[Captivate Android Development] bay_wolf:
Another user reported this. I think it has to do with how/what the ODIN 3BF is flashing. My advice would be to do a battery pull then turn the phone back on and see what happens.
[Captivate Android Development] bay_wolf:
Uploading 2.3...
[Captivate Android Development] gbrown2036:
Great! Let us know when the link is live.
[Captivate Android Development] dmutpp:
Where are the stock odin files for the Cappy? You getting them from http://samfirmware.com/ ?
[Captivate Android Development] bay_wolf:
Nope, there's a thread in the development section with it in it that design gears posted.

Sorry for the delay of 2.3 but my internet crapped out last night. It'll probably be another hour or two.
[Captivate Android Development] dmutpp:
So question, is there anyway to integrate those files into your program to make it a more "true" all in one? I realize that the program download would be bigger, but if it had the Odin included here, it would make it all that much easier to flash. Or if it included this. Sorry, I am just lazy so I am trying to see how much lazier I can become. Love this BTW.
[Captivate Android Development] bay_wolf:
Both of those are integrated into my program...

EDIT: It's step 3 and says, "reboot into download and start ODIN"
[Captivate Android Development] dmutpp:
Ok, let me fool around with it then. Must have missed something. Thanks.
[Captivate Android Development] bay_wolf:
Version 2.3 is now live!
[Captivate Android Development] LightningGA:
Looks like a great tool, downloading now.
[Captivate Android Development] 4-2ndtwin:
Thanks

Great tool. Really appreciate you putting this together.

Your time and effort, as well as the other Devs, does not go unappreciated. :)

Gonna give this a try later and will post how it goes...
[Captivate Android Development] mfpmax:
Oh this program saved my butt big time.
[Captivate Android Development] bay_wolf:
Awesome. Let me know how it works for you.
[Captivate Android Development] 4-2ndtwin:
Having problems when I get to CWM. Getting error after I select install ROM.zip

E:Can't open /sdcard/ROM.zip

(bad)

Installation aborted.

Any ideas ??

Also previous to this step, everything went good except when I selected Copy Root File + Reboot into Recovery I got the on screen error with the yellow droid guy in the upper left hand corner of the screen with red words over him--RST_STAT =0x4 and 6 other lines with other red words = 0 x etc. And then out to the right hand of that the words in yellow--KERNEL PANIC UPLOAD MODE Pulled battery and rebooted fine and went back to the rooting step and selected again but when the phone shut off I immediately unplugged from usb and all went well. until CWM error... any help appreciated.

Anyone else experiencing errors like this ??
[Captivate Android Development] TorqueWrench001:
Aborted Installation

Bay_wolf looks like a great program! I'm having some trouble, I can't get it to install on my system. About 3/4 of the way through the installation I get an error

"An error occurred while attempting to create the directory: C:\ProgramData\Microsoft\Windows\Start Menu". I have to cancel out because it won't continue, the installation is aborted. I'm assuming it's an issue with my system because I've read the thread and I didn't see anyone else having this problem. Anyone have any ideas?
[Captivate Android Development] bay_wolf:
I just checked it out and the problem for the ROM is that pressing the step of copying the ROM and CWM copying and rebooting is happening too quick. Wait like 3 minutes between those two buttons.

EDIT: I'll be uploading a bugfix for this now. I'm removing the links to 2.3 so no one else gets this error. Thanks for pointing it out to me.
[Captivate Android Development] 4-2ndtwin:
Thanks for your work and help. Will check back tomorrow.
[Captivate Android Development] novagator:
I gotta say, as a relative n00b, I can't wait to try this out.
[Captivate Android Development] bay_wolf:
You can download 2.2 in the changelog right now but 2.4 (bug fix of 2.3) should be up within 2 hours. And I hope it helps. Let me know if you have any issues.
[Captivate Android Development] bay_wolf:
It's definitely your system. What OS are you running and are you the admin or just a normal user? Also try selecting between "just for me" and "everyone" options in the installation.