yashsingh1/xdaforums huggingface dataset:
[Captivate Q&A, Help & Troubleshooting] mack49:
When are Googler_1976 and Johnsondr80 going to develop a Rom based on KI2? As of today there is only one Dev with a KI2 Rom available. :confused: I hated to see all the other Dev's leave the captivate I897 as I don't believe that it has reached it's full potential. But, all of the Captivate developers deserve a great deal of thanks for all of the time and effort they put into their work. This from someone who started using Cognition 3.04 as soon as I got my Cappy. :D:D:D

Again thanks to all the Devs.
[Captivate Q&A, Help & Troubleshooting] prbassplayer:
Johnsondr80 is currently testing a KI2 Fusion. But its a WIP. No point releasing it till its ready considering KH3 Fusion works just fine.
[Captivate Q&A, Help & Troubleshooting] popfan:
Please don't forget that Fasty III is available already.
[Captivate Q&A, Help & Troubleshooting] prbassplayer:
I assumed when op said only 1 dev with KI2 he was talking about LostLogic89 and his Fasty III rom.
[Captivate Q&A, Help & Troubleshooting] El Niche:
Is there a noticeable difference between the new leak 2.3.5 and 2.3.4? Battery and smoothness?
[Captivate Q&A, Help & Troubleshooting] mack49:
Yes, i didn't mean to leave LostLogic89 out of the picture, he has done some outstanding work as well as the rest of the Dev's. I am currently on Victory 2.0 as well as my wife. To answer El Niche, all who have jumped to 2.3.5 say it is smooth and fast with good battery life.
[Eee Pad Transformer Android Development] rayman:
Thanks to everyone who tried out the tool.

It gave us valuable information! :)

There is some results available here http://androidroot.mobi/2011/10/10/sbkdetect-v2-the-result/

I'll be asking to have this thread closed now.
[Eee Pad Transformer Android Development] gnufabio:
Men, you are awsome!

So we are near to root also SBKv2 devices?

Great work BTW
[Eee Pad Transformer Android Development] Renarudo:
Works

I have a B70 tablet.
[Eee Pad Transformer Android Development] hackfanatic:
would you be interested in SBK info for the B80 as well ?

Opps, just read your whole thread, will get back with info soon..
[Eee Pad Transformer Android Development] Lizard:
Found APX mode device

Chip UID: 0x37c7045410080d7

Detected SBKv2

On a B70 tablet
[Eee Pad Transformer Android Development] marianus84:
it gives me sbkv1 but nvflash says error 0x4.

Hybrid??:confused:

tf101g B70
[Eee Pad Transformer Android Development] luisalhosilva:
I have b80 since i cant rin it from trsfoemer i will give feed back later.
[Eee Pad Transformer Android Development] rapman172003:
Tf101g B80KAS094

Chip UID: 0x388924342bf9517

Detected SBKv1:eek: :confused:
[Eee Pad Transformer Android Development] fserve:
I really dont know if i can help.

Rooted B7OKAS146

Found APX mode device

Chip UID: 0x3806202411fb117

Detected SBKv1
[Eee Pad Transformer Android Development] gee one:
Found APX mode device
Detected SBKv1

Rooted B50K

I'm running 64 bit Ubuntu 11.04- I had to use "apt-get install ia32-libs" to get it to work.
[Eee Pad Transformer Android Development] rayman:
First of all, thanks to everyone for running it! It's great information :)

Second, the program is slightly wrong in some cases.

Essentially, it verifies if your device has the SBK we have. This means that it will say "SBKv1" if your device matches certain criteria and does NOT have "our" SBK.

It's *very* important we get more people with TF101 B80's to try out this program!

See above.

We need confirmation from more people with B80's, but it looks like at least the 3G versions of the device (TF101G) have a different SBK from all other devices.
[Eee Pad Transformer Android Development] realdope:
i need help i am noob on ubuntu

how do i execute this script i am on kubuntu 10.04??
[Eee Pad Transformer Android Development] sblindheim:
I have a B80, Wifi only... Will run this as soon as I get home from work.

-Sblindheim
[Eee Pad Transformer Android Development] Incoe:
I have a B70 an di think it has an new SBK. Have Ubuntu running at home so i will try it later and give you a feedback!
[Eee Pad Transformer Android Development] marianus84:
So we have no chance, right?

tf101g B70KAS16xx
[Eee Pad Transformer Android Development] gee one:
download the file

open up a terminal window and move to the download directory

cd /fill/in/the/blanks/directory/

untar the file

tar -xf sbkcheck.tar

plug in your TF and put it in SBK/nvflash mode

execute the file

./sbcheck

if you get an error about 32bit libs, use this

apt-get install ia32-libs

then re-run the file "./sbcheck"
[Eee Pad Transformer Android Development] raimondomartire:
Chip UID: 0x380618942408497

Detected SBKv1

TF 101g

b70kas280

why if sbkv1 in version g the root is not usable?
[Eee Pad Transformer Android Development] sblindheim:
I just ran it now:

Chip UID: 0x37c7089437f3617

Detected SBKv2

TF101 B80KAS1120

/sblindheim
[Eee Pad Transformer Android Development] marianus84:
Ok, it seems that there are two sbk right now, one for the b70/b80 models and another one for the 3g versions.

Maybe you can ask your "source" for the 3g one.:p:D
[Eee Pad Transformer Android Development] kepicz:
TF101 B80KAS....

Found APX mode device

Chip UID: 0x38062024120b497

Detected SBKv2

Let me know at @kepicz if you need anything else on B80.
[Eee Pad Transformer Android Development] raimondomartire:
@rayman any news on tf101g that have sbk1?
[Eee Pad Transformer Android Development] shrubber83:
this afternoon i'll try to install some linux system in my pc... and than i'll try this app... i have a B70 already rooted... could be helpful?
[Eee Pad Transformer Android Development] rayman:
it doesn't. It's a minor bug in the program.

It essentially has SBKv3. It's just not possible to properly test against.

It should probably have said "Unknown" if it couldn't detect tf101 sbkv2.

sorry to get your hopes up.
[Eee Pad Transformer Android Development] sblindheim:
For us with B70/80 and sbk v2, how? what? when? where? Any possibilities to provide some more info on how thigs are going? I've seen your post at androidroot.mobi, and the ones living in denmark willing to let you borrow their B80 devices. Have you gotten one?

I'm really crosing all that can be crossed (fingers, toes, foot, arms, balls...) waiting to get root and take control over my device :)

-Sblindheim
[Eee Pad Transformer Android Development] thorntree:
I downloaded sbkcheck. On Ubuntu 10.04 I unpacked, changed to that folder, turned the Transformer off, held down up volume and power buttons for over 5 seconds, plugged power cord into the USB port on the computer, then entered "./sbkcheck" at the terminal.

The results are:

./sbkcheck: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory

Am I doing something wrong? I haven't heard of anyone else getting this message. I have a later version B70. I already tried to root and no luck so it must be SBK2.
[Eee Pad Transformer Android Development] sblindheim:
You probably have 64-bit ubuntu?

Look further up in the thread to see what to type to get the 32-bit libs...

-Sblindheim

EDIT:
[Eee Pad Transformer Android Development] thorntree:
I do have 64-bit Ubuntu. Thanks for the suggestion, but I have already had ia32-libs installed for months. I just verified again that it is indeed installed.

The error doesn't mention ia32-libs, but instead refers to libusb-1.0.so.0. I searched my file system for that file and it exists (apparently in about 3 places). I tried copying the file to the local directory where sbkcheck resides and executing sbcheck again... I still received the same error.

Any other suggestions? I'd like to contribute whatever I can, even if it's only the information from sbkcheck. I really want to see the TF101 rooted.
[Eee Pad Transformer Android Development] gee one:
try this to confirm that it is installed, but it sounds like it is, and it's not a 32bit issue

dpkg -l |grep libusb

Have you ever used nvflash on your PC? Maybe you have to update the udev rules? The vendor ID is different for the TF in nvflash mode than it is in adb mode. I think there is even a difference between the original stock rom and one of the updates!

You might need to update /etc/udev/rules.d/96-android.rules

Some guides show it as 51, but higher is better, unless it conflicts with some other device you have.
[Eee Pad Transformer Android Development] rapman172003:
since i do not have linux on my pc.I have just downloaded ubuntu live cd 32 bit, and simply booted up. used the suggested command and didn't showed nothing after that i have tried "sudo ./sbkcheck" and voilá it worked. Maybe this will help somebody. :)
[Eee Pad Transformer Android Development] thorntree:
dpkg -l | grep libusb

produces the following results:

ii libusb-0.1-4 2:0.1.12-14ubuntu0.2 userspace USB programming library
ii libusb-1.0-0 2:1.0.6-1 userspace USB programming library
ii libusbmuxd1 1.0.2-1ubuntu2 USB multiplexor daemon for iPhone and iPod T

I've tried sudo ./sbkcheck and that produces the same error as in my first post (about libusb not being found).

Nvflash... The only Android thing I've done with this PC before is last year when I rooted my Droid 2 using adb. For that I created /etc/udev/rules.d/91-android.rules. It still contains what I put in it for my Droid 2 back then:

SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", SYMLINK+="android_adb", MODE="0666", OWNER="myname"

Does this information help diagnose the problem I'm having?
[Eee Pad Transformer Android Development] gee one:
Try adding this to your rules file:

SUBSYSTEM=="usb", ATTRS{idVendor}=="0955",ATTRS{idProduct}=="7820", MODE="0666"

Not sure if you need the owner bit? Maybe if you run in a non-root shell?

You can also type "lsusb" from the command line when the TF is in apx/nvflash mode and plugged in to verify the vendor and product numbers. You wouldn't think they would change, but...
[Eee Pad Transformer Android Development] thorntree:
gee one, I made that line the only line in my 91-android.rules file, rebooted, and still received the exact same error as before about libusb not being found when running ./sbkcheck. I tried it with and without the OWNER designated in the rules file. I tried "sudo ./sbkcheck" and that didn't work either. I was able to verify the vendor and device number (same as you gave me) by executing "lsusb", so at least my PC sees the Transformer, apparently.
[Eee Pad Transformer Android Development] gee one:
Well, I'm out of ideas?

rebound821 posted a liveCD for his universal root. You could boot from there and run sbkdetect from there. http://xdaforums.com/showthread.php?t=1198303
[Eee Pad Transformer Android Development] thorntree:
Well, that worked. I used the liveCD you pointed toward (that's what I had tried previously to root, but only got errors in the rooting process). I dropped to a terminal and ran ./sbkcheck and received the following output:

Found APX mode device

Chip UID: 0x37c710940bfa117

Detected SBKv2

My serial is B70KAS218xxx. I don't know if contributes in any way, but there it is.
[Eee Pad Transformer Android Development] debenham:
sbkcheck results

I just ran sbkcheck on my TF101 (SN: B70KAS239xxx) and received the following:

Found APX mode device

Chip UID: 0x3806202421f2357

Detected SBKv2
[Eee Pad Transformer Android Development] rabidrabbit001:
So does this mean that the tf101(G) tablets are using the sbk3 and are currently non-rootable devises??? And I know how to read guys. I just don't understand all the jargen. thanks
[Eee Pad Transformer Android Development] davebugyi:
Yes. Even SBK v2 devices are non-rootable ATM.
[Eee Pad Transformer Android Development] rayman:
I've made a post about the results of SBKDetect v2 here:

http://androidroot.mobi/2011/10/10/sbkdetect-v2-the-result/
[Eee Pad Transformer Android Development] rabidrabbit001:
That was very helpful guys thanks. I have not yet purchased a tf101 yet but am currently on the hunt and want to make the best educated purchase possible. Your post put the final nail in the l coffin for the tf101(G) for me. THANKS AGAIN
[Eee Pad Transformer Android Development] baderfgt:
I ran sbkcheck on my TF101 (SN: B70KAS025xxx):

Found APX mode device

Chip UID: 0x380624441007557

Detected SBKv1
[Eee Pad Transformer Android Development] pa+:
Output From Terminal:

Found APX mode device

Chip UID: 0x38061464260a257

Detected SBKv2

Device Info

Serial: B70KAS2499XX

Build Number: HTK75.TW_epad-8.6.5.13-20110925

Hope this helps, and good luck all you devs :)
[Eee Pad Transformer Android Development] gaijin2:
French B80/TF101G (With 3G)

Found APX mode device

Chip UID: 0x428014943602317

Detected SBKv1
[Eee Pad Transformer Android Development] Renarudo:
Thank you so much to you and the team! I personally have concerns that ASUS will take all year and a day updating this tablet to ICS, so having root and being able to flash my own ROM choice would make me immensely happy!

I know you all don't want donations because that would put "pressure" on your work - but please tell us there's a way to donate just to say "thanks"!
[Eee Pad Transformer Android Development] rayman:
I'm not as such against donations. I'm just against donations for specific purposes, as this creates a sense that I "owe" people something. If you want to say thank you, you are more than welcome to :) I appreciate all donations a lot and usually I do actually keep my paypal money for paying for technical stuff.

See http://androidroot.mobi/donations/
[Eee Pad Transformer Android Development] shrubber83:
TF-101 rooted B70KAS102xxx

Found APX mode device

Chip UID: 0x380624041004357

Detected SBKv1
[Eee Pad Transformer Android Development] wwnmt:
B70

Found APX mode device

Chip UID: 0x37c70894380b5d7

Detected SBKv2

B70KAS281XXX

Willing to help out additionally if needed.
[Eee Pad Transformer Android Development] P500:
S/N: B70KAS...

Found APX mode device
Chip UID: 0x37c624540a02657
Detected SBKv1
[Eee Pad Transformer Android Development] reaperzero:
TF101 B80KAS1196..

Found APX mode device

Chip UID: 0x428014940a0d057

Detected SBKv2

hope this helps
[Eee Pad Transformer Android Development] beer-in-box:
Found APX mode device

Chip UID: 0x380618942208597

Detected SBKv1

S/N: B70KAS086***

So, does that mean that I can root this because it has SBKv1?
[Eee Pad Transformer Android Development] rayman:
IF you device is a TF101 (e.g. Wifi only), then most likely, yes.
[Eee Pad Transformer Android Development] will8578:
Lucky sod lol
[Eee Pad Transformer Android Development] beer-in-box:
Thank you. It is a TF101, yes. So, do you suggest me waiting or trying to root it? And if rooting can be done now, can you direct me to the proper tools and tutorials etc.?
[Eee Pad Transformer Android Development] thebadfrog:
http://xdaforums.com/showthread.php?t=1124217
[Eee Pad Transformer Android Development] reaperzero:
luck of the gods i tell yee
[Eee Pad Transformer Android Development] billouetaudrey:
Found APX mode device

Chip UID: 0x380620842407657

Detected SBKv2

This command work :

sudo ./sbkcheck

Thanks
[Eee Pad Transformer Android Development] got_rice64:
This worked for me too.

SBKv2 for me too...

There is no way to root SBKv2 as of current?

That also means no ROMs, right?
[Eee Pad Transformer Android Development] billouetaudrey:
Can't root for moment

Because, developers haven't got TF v2 ...

Sent from my Transformer TF101
[Eee Pad Transformer Android Development] jakevis:
B70 here...

Found APX mode device

Chip UID: 0x37c708140402257

Detected SBKv2
[Eee Pad Transformer Android Development] gaijin2:
Hi everybody,

Any chance to have the B80 unroot one day ?

Thanks for all.

Best regards
[Eee Pad Transformer Android Development] KilloMaster:
Transformer TF101

S/N: B80kas01xxxx

Detected SBKv1
[Eee Pad Transformer Android Development] rayman:
Hrm. Is yours routable with nvflash?

If not, then that's worrying :S
[Eee Pad Transformer Android Development] antond57:
Hi,

I'v a tf101 wifi only,

sbkcheck results:

Found APX mode device

Chip UID: 0x3806102423f2117

Detected SBKv2

Serial: B70KAS350669

Many thanks in advance to root this device!
[Eee Pad Transformer Android Development] KilloMaster:
Not routable.
[Eee Pad Transformer Android Development] antond57:
Indeed Not, nvflash gives errors.

It's a device with the new SBK v2, bad luck.
[Eee Pad Transformer Android Development] rschalie:
Keep getting a "permission denied" on my Slider
[Eee Pad Transformer Android Development] SWEATTAIMI:
hmm, seems like theres a SBKv1 more on b80, lemme know if its 3G?
[Eee Pad Transformer Android Development] gaijin2:
Mime is also B80, and SBKv1. It's a 3G one.
[Eee Pad Transformer Android Development] SWEATTAIMI:
And its not root able?
[Eee Pad Transformer Android Development] markp1989:
Mines is an unrootable B70:

Found APX mode device

Chip UID: 0x38401814XXXXXX

Detected SBKv2
[Eee Pad Transformer Android Development] JamieD81:
cant remember where i read it probably on here but ive read alot of forums lately waiting for root,

the 3g tabs are sbk3, this program is designed to see sbk2 *sees sbk1 though*

but it shows sbk3 as sbk1 aswell.

so anything b70kas2xxx + isnt rootable right now

i have a b70kas200415 :( JUST past the bootloader lock down :\
[Eee Pad Transformer Android Development] PatrickVogeli:
Yeah, this program is designed to see SBK2 while sending some special command. If it doesn't get a correct answer, it returns SBK1, which may be true or not. The correct answer would be return SBK2 or UNKNOWN, since it doesn't check if it's SBK1, and SBK3 tablets are already here.

So, right now:

TF101 WITHOUT 3g are SBK1 or SBK2

TF101 WITH 3g (TF101G) are SBK3

TF Slider are most likely SBK4

Easy, isn't it?
[Eee Pad Transformer Android Development] SWEATTAIMI:
Ehm thats sad
[Eee Pad Transformer Android Development] gaijin2:
Yes, unfortunately un-rootable.
[Eee Pad Transformer Android Development] DocSourd:
Found APX mode device

Chip UID: 0x43c70814408057

Detected SBKv2

B70KAS4****
[Eee Pad Transformer Android Development] Svenvdmeer:
Is it still necessary to do this or do the devs have all the information they need. Is there any progress in this project and/or is there anyway to help. I have an B70xxx TF101 and live in the Netherlands.
[Eee Pad Transformer Android Development] ndwatkins:
When I run the program on my Arch machine or my Mint laptop (both have ia32-libs installed) I get "Segmentation fault". I've never seen anyone else report this, so I'm wondering what it means. My TF is a B6O, but I had to RMA it, and I'm pretty sure they replaced the board in it, so I wanted to check the SBK of the new chip.

Anyone have any ideas?
[Eee Pad Transformer Android Development] kopus:
I'm also getting the seg fault.
[Eee Pad Transformer Android Development] uiterlix:
The author mentioned the program will crash hard when it cannot find a device in APX mode, and so it does.
[Eee Pad Transformer Android Development] ndwatkins:
That wasn't really what I would call "crashing hard", but thanks for the help. I'll try again when I get home tonight and see if I maybe am not powering off the device for long enough. I see what it says about holding power for 20 seconds for a B7O, which I don't have, but we'll see.

Anyway, thanks for the tip.
[Eee Pad Transformer Android Development] ndwatkins:
I am having a hell of a time getting into APX mode. Please, before anyone tells me I don't know how, I do, I've done this so many times between mine and my husband's transformers it's ridiculous. This is part of why I didn't even realize I wasn't in APX mode and that the script was crashing, because I'm doing everything the way I've always done it, and I can't seem to get it into APX mode. I managed it once, and it told me I had SBKv1 (yay) but now I can't seem to get back into it to nvflash. It's incredibly frustrating. I don't really get what the problem is. And yes, power off, volume up + power for at least 5 seconds (I usually hold it for longer just in case). I really don't understand what's going on here.

Anyone else have this issue?

Edit: I got it to work after like 50 tries, so whatever, but it worries me a little for the future. I refuse to RMA this thing ever again, even if it spontaneously starts on fire. At any rate, thanks for the help. If it helps anyone in the future, even though they replaced the board, I still ended up with a v1 SBK, so there's some hope there for people!
[Eee Pad Transformer Android Development] Kasush:
There have been many users reporting that the volume buttons have stopped working. Perhaps your issue is with the physical button. That would explain the intermittent successes you have had. It is possible if you open it you can clean or realign the buttons, but it could be risky.

Chris
[Eee Pad Transformer Android Development] ndwatkins:
I was actually wondering this myself, but it always registers presses otherwise - I've never had an issue turning up the volume or turning off the tab since I got it back. It's weird. I did wonder if there was an issue internally with it not registering properly both presses at the same time, though. Either way I won't be opening it up myself, I just don't know enough and am not willing to risk it.

I do appreciate the suggestion though :)
[Eee Pad Transformer Android Development] SWEATTAIMI:
Chip UID: 0x43c708

Detected SBKv2

works
[Eee Pad Transformer Android Development] antond57:
SBKcheck result

I have a TF101G (with 3G)

SBKcheck results:

Found APX mode device

Chip UID: 0x3889207423f7557

Detected SBKv1 (not correct, may be SBKv3)

Model TF101G - 1B113A

Serial Number: BAOKAS023999

NVflash gives errors 0x4 and 0x8

There after the APX mode is ended.

Not root-able at this moment.
[Eee Pad Transformer Android Development] mplaines:
SBKcheck results:

I have a TF101G (wifi)

SBKcheck results:

Found APX mode device

Chip UID: 0x37c708941010317

Detected SBKv2
[Eee Pad Transformer Android Development] Penphoe:
Here's what my machine said...

Found APX mode device

Chip UID: 0x37c704342801397

Detected SBKv1

It's a 32GB Asus Transformer - B70KAS019xxx

Looks like I got one of those "early" B70s! :D

LaterZ!

Darren!!
[Eee Pad Transformer Android Development] Von Ropen:
A lucky one :D
[Eee Pad Transformer Android Development] frdurso:
Ran it, Ubuntu 11.10 with ia32-libs instaled, only worked with sudo...

Mine is a EEE PAD SLIDER

Serial: B80KAS18****

fernando@Kanopus:~/Download$ sudo ./sbkcheck

Found APX mode device

Chip UID: 0x388924344004197

Detected SBKv1
[Eee Pad Transformer Android Development] kopus:
Can you confirm if the syslog got any when sbkcheck seg faulted?

I keep getting the following error: bkcheck[28478]: segfault at 24 ip 000000004c5b2c57 sp 00000000ffa8cfb0 error 4 in libpthread-2.14.90.so[4c5aa000+17000]

I have the 32bit libs installed and I also see the device coming up on syslog:

kernel: [174789.495089] usb 2-3: USB disconnect, device number 14

kernel: [174789.846086] usb 2-3: new high speed USB device number 15 using ehci_hcd

kernel: [174789.961038] usb 2-3: New USB device found, idVendor=0955, idProduct=7820

kernel: [174789.961047] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0

kernel: [174789.961055] usb 2-3: Product: APX

kernel: [174789.961060] usb 2-3: Manufacturer: NVIDIA Corp.

mtp-probe: checking bus 2, device 15: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-3"

mtp-probe: bus: 2, device: 15 was not an MTP device

So I would say that it's in APX mode but still I'm getting the seg fault.

Does anyone have any idea why this can be happening?

I have also tried it on different Linux pcs (Fedora and Ubuntu).
[Eee Pad Transformer Android Development] kopus:
Finally I got it to work.

Found APX mode device

Chip UID: 0x37c704541a08257

Detected SBKv2
[Eee Pad Transformer Android Development] SWEATTAIMI:
heh'h lucker, slider got a sbkv1 (but still is it rootable)

maybe is a sbkv1 for transformer TF101G (3G Verision)
[Eee Pad Transformer Android Development] Arctiik:
B70KAS046947

SBK1 and Rooted.
[Eee Pad Transformer Android Development] FalloutMan:
B70 tablet

Found APX mode device

Chip UID: 0x37c710941207117

Detected SBKv2