Database Users

Primish? Nvflash prime based image.

Took the deodexed apks and bits and pieces of Prime and put it in an ext4 nvflashable system.img. It has Music, Maps, and a couple other apps that are downloadable via Market REMOVED.. This way, they are updatable.. It annoys me to have system app be "automatically updated" (installed again on data partition). This includes aria2c, unrar, chngfrq (a script I wrote to display certain stats like cpu vdd, dock batt, max clock and so on).. Its what I use and it may not be for everyone. Also uses a 3.2 kernel i just made.. 1232000 1424000 1544000 1656000 are the non-stock freqs.. Don't freq out. hah oh my - so funny. they're stable..
it has a script included and it pretty much goes like this..
nvflash-backup.sh is the same as posted on another thread... obviously run that first.
Then here is 'flashnew.sh'. It only (obviously) writes to system (APP-part9) and boot (lnx-part 6). I'll post a windows batch file soon. Here's a hint tho - substitute sudo nvflash for nvflash.exe and you're good to go.
sudo ./nvflash --bct transformer.bct --setbct --configfile flash.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync
sudo ./nvflash --resume --download 6 boot.img
sudo ./nvflash --resume --download 9 system.img
sudo ./nvflash --resume --sync
If Roach tells me to take this down. I take it down, its -pretty much- his rom (concerning stuff in /system/etc and /system/app. Oh and I added htop and nano as well. Any libncurses binary should do fine. That said, don't complain to him if things don't work on this (all set on my end) - complain to me - I love it when you do. Yes, I am aware that there is no boot screen besides the default glistening android deal. Also, you can delete Phone.apk in /system/app/ - but then System->About->Status will FC - Boohoo I know - I left it in there.. but just saying..
Is everyone peachy on all that?
http://home.comcast.net/~ibladesi/primishistical.rar
Oh, also removed nearly all Asus apps.. if enough people want them, I'll post a script that will download (using aria2c) them, unrar, and restore to your /system/app directory.

this is good cause it works for ubuntu users. Thanks

pardon my ignorance, but is the 3.2 kernel source out aready?
edit: did a bit of googling...it seems the generic 3.2 kernel was released. so i'm guessing this is that + some transformer specific stuff from 3.1 spliced in?
Sent from my Transformer TF101 using Tapatalk

excellent, I think this is a great idea. Will wait till you put out a .bat, thanks!
Sent from my Transformer TF101 using XDA Premium App

u-boot and kernel 2.6.38 for tf101 and iconia

Hi all here!
I ported u-boot and latest chromium kernel to tf101. U-boot can also be used on Acer Iconia.
here it is:
enodev.org/~muromec/u-boot/2011-08-04/u-boot-tf101.bin (tf101)
enodev.org/~muromec/u-boot/2011-08-04/u-boot-picasso.bin (iconia)
enodev.org/~muromec/tf101/vmlinux-2.6.38.3-g3effdbe.uimg
source code at my github page: github.com/muromec/iconia-gnu-kerne github.com/muromec/uboot-tegra
U-boot can be loaded via nvflash like this:
Code:
./nvflash --bct transformer.bct --setbct --configfile flash.cfg --bl u-boot.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync
Or flashed replacing nvidias boot like this (using flash.cfg from here: enodev.org/~muromec/tf101/flash.cfg
Code:
./nvflash --bct transformer.bct --setbct --configfile flash_hack.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync
./nvflash -r --format_all --configfile flash_hack.cfg --create --bct transformer.bct --setbct
Tries to load kernel image in u-boot format from three different places:
At very first: usb flash (or dockstation sd-slot) partition 3, formatted in ext2. kernel should be placed at /boot/vmlinux.uimg
At second: partition 3 on internal mmc when its partitioned using msdos/mbr.
At last: from internal mmc sector 0x1c00 (SOS partition).
Bootloader passes kernel mtype 3640 (one i registered for tf101).
Feel free to use.

Ummm. So what it be possible to actually port chromium itself?

ilyamuromec said:
Hi all here!
Click to expand...
Click to collapse
Hi ilyamuromec, Welcome to xda-developers!
Thanks for your hard work. I tried to compile your code, but it's unbootable & build size is bigger than yours (266K). I used
Code:
make ventana_config
make
Please guide

Amazing work, lets see what this brings, but will probably be a great addition to ubuntu on the transformer

I get fails with the device tree stuff and can't compile it as a result,

lilstevie said:
I get fails with the device tree stuff and can't compile it as a result,
Click to expand...
Click to collapse
Usually when I have trouble compiling someone else's code, it's due to the version of the armeabi cross-compiler.
ilyamuromec, what cross-compiler and build options do you use?

msticninja said:
Usually when I have trouble compiling someone else's code, it's due to the version of the armeabi cross-compiler.
ilyamuromec, what cross-compiler and build options do you use?
Click to expand...
Click to collapse
at this point it is actually the Device-tree-compiler

I`m building with such command:
make ARCH=arm CROSS_COMPILE=/opt/arm/arm-2010q1/bin/arm-none-eabi- ventana DEV_TREE_SRC="tegra2-tf101"
only difference in devices trees is a label and machid (mtype). and my gcc version:
gcc version 4.4.1 (Sourcery G++ Lite 2010q1-188)
anything newer gives same unbootable crap. about device tree compiler: I`m using one from kernel tree: Version: DTC 1.2.0-g37c0b6a0

ilyamuromec said:
I`m building with such command:
make ARCH=arm CROSS_COMPILE=/opt/arm/arm-2010q1/bin/arm-none-eabi- ventana DEV_TREE_SRC="tegra2-tf101"
only difference in devices trees is a label and machid (mtype). and my gcc version:
gcc version 4.4.1 (Sourcery G++ Lite 2010q1-188)
anything newer gives same unbootable crap. about device tree compiler: I`m using one from kernel tree: Version: DTC 1.2.0-g37c0b6a0
Click to expand...
Click to collapse
Code:
dtc -R 4 -p 0x1000 -O dtb -o dt.dtb /home/lilstevie/transformer_ubuntu/uboot-tegra/board/nvidia/ventana/tegra2-tf101.dts
DTC: dts->dtb on file "/home/lilstevie/transformer_ubuntu/uboot-tegra/board/nvidia/ventana/tegra2-tf101.dts"
FATAL ERROR: Couldn't open "skeleton.dtsi": No such file or directory
Is the error I am getting, dtc version is 1.2.0 from the ubuntu software repos

lilstevie said:
at this point it is actually the Device-tree-compiler
Click to expand...
Click to collapse
Late night, words failed me. You know what I meant...

lilstevie said:
Code:
dtc -R 4 -p 0x1000 -O dtb -o dt.dtb /home/lilstevie/transformer_ubuntu/uboot-tegra/board/nvidia/ventana/tegra2-tf101.dts
DTC: dts->dtb on file "/home/lilstevie/transformer_ubuntu/uboot-tegra/board/nvidia/ventana/tegra2-tf101.dts"
FATAL ERROR: Couldn't open "skeleton.dtsi": No such file or directory
Is the error I am getting, dtc version is 1.2.0 from the ubuntu software repos
Click to expand...
Click to collapse
please, try one from kernel sources. there is some difference in path resolition for dtsi includes.

lilstevie said:
Is the error I am getting, dtc version is 1.2.0 from the ubuntu software repos
Click to expand...
Click to collapse
I got the same error before using DTC 1.3. The syntax inside the dts file isn't compatible with older version.

Awesome, could we possibly use this to dual boot stuff (without replacing the recovery image)?

brando56894 said:
Awesome, could we possibly use this to dual boot stuff (without replacing the recovery image)?
Click to expand...
Click to collapse
yeah, i`m using it for dual-boot. one kernel on sd-card, other on internal mmc.

Okay, cool using device-tree-compiler_1.3.0 builds and works now awesome work, I will forking this now and making the necessary changes for it to work for my ubuntu port this combined with your port of the chromeos kernel has just made things a hell of a lot easier for me mad props man

lilstevie said:
Okay, cool using device-tree-compiler_1.3.0 builds and works now awesome work, I will forking this now and making the necessary changes for it to work for my ubuntu port this combined with your port of the chromeos kernel has just made things a hell of a lot easier for me mad props man
Click to expand...
Click to collapse
I was hoping you'd pick this thread up. I love your dual-boot, but I've always hated using recovery as the second OS. Did the same on my Archos and always felt dirty about it.

lilstevie said:
Okay, cool using device-tree-compiler_1.3.0 builds and works now awesome work, I will forking this now and making the necessary changes for it to work for my ubuntu port
Click to expand...
Click to collapse
Hint: you can place so-called "u-boot script" on 13th partition to hook necessary options into bootloader. u-boot should be sort of thing that is same for different distros.
living with different u-boot forks for ubuntu, chromeos and something like archlinux would be just wrong. if you need, I will merge back some defaults like loading initrd.
lilstevie said:
this combined with your port of the chromeos kernel has just made things a hell of a lot easier for me mad props man
Click to expand...
Click to collapse
eah, but kernel port still misses some pieces like internal battery driver, sound config, etc. also, asusec driver should be cleaned and pushed mainstream.

ilyamuromec said:
Hint: you can place so-called "u-boot script" on 13th partition to hook necessary options into bootloader. u-boot should be sort of thing that is same for different distros.
living with different u-boot forks for ubuntu, chromeos and something like archlinux would be just wrong. if you need, I will merge back some defaults like loading initrd.
eah, but kernel port still misses some pieces like internal battery driver, sound config, etc. also, asusec driver should be cleaned and pushed mainstream.
Click to expand...
Click to collapse
eh work is expected, asus kernel doesn't work that brilliantly anyway, a few of the drivers are pretty broken

just wondering if you have any specific requirements on the emmc partition, been trying various things and the fatload just keeps failing

lilstevie said:
just wondering if you have any specific requirements on the emmc partition, been trying various things and the fatload just keeps failing
Click to expand...
Click to collapse
fatload? do you have FAT support enabled and partition actually in fat?
I`m doing it in sort of tricky way. I created dos partition table on mmcblk0:
/dev/mmcblk0p3 7168 10492927 5242880 83 Linux
it is important that partition number is 3 and starts from block 7168 (all before wiped on reflash). partition formatted with ext2

[Q] Issue with Acer Iconia A500 Flashing Bootloader and Entering Recovery

Alright I did find a forum where this should be posted but due to restrictions I said I would post it here the forum was http://forum.xda-developers.com/showthread.php?t=1622425
I have searched through all that forum and tested every method to try and get my issue resolved.
DEVICE INFO:
Device : Acer Iconia A500
Android version : 4.0.3
Kernal: 2.6..39.4+
Image Version: Acer _AV041_A500_RV03RC01_WW_GEN1
Build Number: Acer_AV041_A500_1.031.00_WW_GEN1
Image P/N: FM.S14A0.00U
Bootloader Version 0.03.12-ICS
Tablet is also Rooted
The issue is that when I attempt to enter recovery it says
" Erasing Cache beofre SD Update...
SD Update cmd: recovery
--update_package=SDCARD: Update.zip
Booting recovery kernal image
Recovery verified failed ... "
I have tried putting an update.zip file on both the internal and external SD card but issue still happens.
The next issue is that when I try flash the bootloader using the information in the above forum It just continously hangs and looking at the cmd output it has an error
Flashing bootloader: ics_boot_unlk_V4.bin ...
Nvflash started
[resume mode]
Formatting partition 4 please wait.. Command Execution failed cmd 13, error 0x12
0002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
Nvflash started
[resume mode]
I have attempted to remove the batch script that formats the partitions but that still doesnt work.
I have attempted the bootloader flash both manually using the CMD and the automatically using the A500APXFlashing tool.
I have tried all issue resolutions in the forums above but still not working
Any help would be great
Thanks in advance
ADDITIONAL INFO:
In the normal operations the tablet works fine it is boots into android ICS without any problems

Issue with Acer Iconia A500 Flashing Bootloader and Entering Recovery
I been having the same problem as you with no soluton.

shenny585 said:
I been having the same problem as you with no soluton.
Click to expand...
Click to collapse
Have you tried all TS in the thread that I linked at the top of my post?

Issue with Acer Iconia A500 Flashing Bootloader and Entering Recovery
Yes I did

Ok well it seems that we need to see can we get a dev to look at this forum to see if there is any resolution.

Sounds like a dodgy SBK
OP: what app did you root woth!?
Sent from my Iconia A500 using Tapatalk 2

Issue with Acer Iconia A500 Flashing Bootloader and Entering Recovery
SBK is right
Used the blackthund3r apx flash utility and the simple method for rooting

shenny585 said:
SBK is right
Used the blackthund3r apx flash utility and the simple method for rooting
Click to expand...
Click to collapse
Try Skrilax's bundle market repo bundle #4 (see his boot loader thread for the URL, input it into the bundle market then choose bundle 4). Press yes to stage for flash when you download
Sent from my Iconia A500 using Tapatalk 2

Issue with Acer Iconia A500 Flashing Bootloader and Entering Recovery
Tried Skrilax's bundle market repo bundle #4 with no result.
The acer usb boot recovery drives disappears when entering download mode bootloader..

blackthund3r said:
Sounds like a dodgy SBK
OP: what app did you root woth!?
Sent from my Iconia A500 using Tapatalk 2
Click to expand...
Click to collapse
Firstly Id like to thank you for the rooting tool made it a breeze.
I have tested my SBK in CMD using the tool form the forum above and it seems to be right
I have tried uninstall and reinstall of Acer drivers to no aval.
Will try the latest post you put up and get back with an update

What is the output upon the initial command where you enter the SBK (when using nvflash manually)?

Skrilax_CZ said:
What is the output upon the initial command where you enter the SBK (when using nvflash manually)?
Click to expand...
Click to collapse
Here is the response after I enter the SBK. Is this the right response
**********************************************************
* Make your choise: *
*(1) HC bootloader with TWRP cwm (touch cwm) *
*(2) ICS bootloader V4 with TWRP-2.1.3-ICS cwm(touch cwm)*
*(3) ICS bootloader V4 with PubRecovery-ICS (BareBones) *
*(4) ICS bootloader V4 with Thor-1.7cwm (touch cwm) *
*(5) ICS bootloader V4 with Thor-1.7.2 NEW cwm(touch cwm)*
* with its compatible recoveries. *
**********************************************************
(1 2 3 4 5):5
Loading bootloader...
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0380624843c11517
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 3
sending file: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714981/714981 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (cod
e: 14) message: nverror:0x4 (0x4) flags: 0
**********************************************************
* Press any key when your A500 is in bootloader mode *
**********************************************************
Press any key to continue . . .

blackthund3r said:
Try Skrilax's bundle market repo bundle #4 (see his boot loader thread for the URL, input it into the bundle market then choose bundle 4). Press yes to stage for flash when you download
Sent from my Iconia A500 using Tapatalk 2
Click to expand...
Click to collapse
I have tried that method and it just hangs and doesnt do anything and the tablet says entering download mode not APX mode
Any other ideas?

steokeogh said:
I have tried that method and it just hangs and doesnt do anything and the tablet says entering download mode not APX mode
Any other ideas?
Click to expand...
Click to collapse
Well, the thing is that you have to dump your bct from the tablet and decrypt it with SBK and read odmdata from that. No real guide exists for this, BCT is first 4k bytes from mmcblk0 (w/o partition), and used method is aes. It's 2:46 AM now, so just very basic info:
A) dd if=/dev/block/mmcblk0 of=/sdcard/bct.enc bs=4096 count=1
B) Pull bct.enc to PC
C) Decrypt with AES using SBK as the key (remove the "0x" and join it)
D) odmdata parameter is on 0xFE4 in bct (little endian)
And if you repartition the tablet, you have do it again.
That's what causes the issues, blackthund3r's app uses the most common bct. Seems like we'll have to automate this.

Skrilax_CZ said:
Well, the thing is that you have to dump your bct from the tablet and decrypt it with SBK and read odmdata from that. No real guide exists for this, BCT is first 4k bytes from mmcblk0 (w/o partition), and used method is aes. It's 2:46 AM now, so just very basic info:
A) dd if=/dev/block/mmcblk0 of=/sdcard/bct.enc bs=4096 count=1
B) Pull bct.enc to PC
C) Decrypt with AES using SBK as the key (remove the "0x" and join it)
D) odmdata parameter is on 0xFE4 in bct (little endian)
And if you repartition the tablet, you have do it again.
That's what causes the issues, blackthund3r's app uses the most common bct. Seems like we'll have to automate this.
Click to expand...
Click to collapse
Thanks for the further TS but I cannot seem to find the files you mention above.
Would you be able to give me more broken down steps to try fix this? Thanks
Also I saw that blackthund3r has released a new version of the tool. It mentions in the post some of the things you mention in yours is the tool now updates to automate the process you were talking about.
Sent from my HTC Desire HD A9191 using XDA

Skrilax_CZ said:
Well, the thing is that you have to dump your bct from the tablet and decrypt it with SBK and read odmdata from that. No real guide exists for this, BCT is first 4k bytes from mmcblk0 (w/o partition), and used method is aes. It's 2:46 AM now, so just very basic info:
A) dd if=/dev/block/mmcblk0 of=/sdcard/bct.enc bs=4096 count=1
B) Pull bct.enc to PC
C) Decrypt with AES using SBK as the key (remove the "0x" and join it)
D) odmdata parameter is on 0xFE4 in bct (little endian)
And if you repartition the tablet, you have do it again.
That's what causes the issues, blackthund3r's app uses the most common bct. Seems like we'll have to automate this.
Click to expand...
Click to collapse
Hmm. Well the tool has ADB already integrated. If you have a copy of the bct decryption utility (its download link is currently down AFAIK) then I would happily work with you in producing the updated version of the flash tool to support this. I can easily get dd etc for windows and script the production of the data. Assuming the SBK is correct we should even be able to read raw bytes from the flash and produce the mmcblk0_start from APX Mode.
Would this help us? http://git.chromium.org/gitweb/?p=chromiumos/third_party/cbootimage.git
Sent from my Iconia A500 using Tapatalk 2

steokeogh said:
Thanks for the further TS but I cannot seem to find the files you mention above.
Would you be able to give me more broken down steps to try fix this? Thanks
Also I saw that blackthund3r has released a new version of the tool. It mentions in the post some of the things you mention in yours is the tool now updates to automate the process you were talking about.
Sent from my HTC Desire HD A9191 using XDA
Click to expand...
Click to collapse
I haven't worked on this yet but I would be interested in doing so. The decryption iirc is done with openssl. I'll look around and let you know when I find the steps. What we can do so far:
A) use a terminal emulator or adb shell to run
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_start bs=4096 count=1
B) copy /sdcard/mmcblk0_start to your PC
Sent from my Iconia A500 using Tapatalk 2

blackthund3r said:
Hmm. Well the tool has ADB already integrated. If you have a copy of the bct decryption utility (its download link is currently down AFAIK) then I would happily work with you in producing the updated version of the flash tool to support this. I can easily get dd etc for windows and script the production of the data. Assuming the SBK is correct we should even be able to read raw bytes from the flash and produce the mmcblk0_start from APX Mode.
Would this help us? http://git.chromium.org/gitweb/?p=chromiumos/third_party/cbootimage.git
Sent from my Iconia A500 using Tapatalk 2
Click to expand...
Click to collapse
Well, sp3dev posted a way here (for linux / cygwin):
http://forum.xda-developers.com/showthread.php?t=1514951
The openssl cmd is:
Code:
openssl aes-128-cbc -K $SBK -iv 0 -d -in $FTMP -out $FOUT
About the decryption, in short:
I believe .NET AES decryptor is this: http://msdn.microsoft.com/en-us/library/system.security.cryptography.aes.aspx
Set initialization vector to all zeroes, and the key:
If your SBK is "0x09A81E00 0xD4531301 0x3B1AF703 0x9A052103" it becomes 09A81E00D45313013B1AF7039A052103.
Haven't tried the .NET way yet. But it works when the ouptut isn't just some random crap, say I dunno: 0xFD0 - 0xFDF should be all zeroes for instance?

Skrilax_CZ said:
Well, sp3dev posted a way here (for linux / cygwin):
http://forum.xda-developers.com/showthread.php?t=1514951
The openssl cmd is:
Code:
openssl aes-128-cbc -K $SBK -iv 0 -d -in $FTMP -out $FOUT
About the decryption, in short:
I believe .NET AES decryptor is this: http://msdn.microsoft.com/en-us/library/system.security.cryptography.aes.aspx
Set initialization vector to all zeroes, and the key:
If your SBK is "0x09A81E00 0xD4531301 0x3B1AF703 0x9A052103" it becomes 09A81E00D45313013B1AF7039A052103.
Haven't tried the .NET way yet. But it works when the ouptut isn't just some random crap, say I dunno: 0xFD0 - 0xFDF should be all zeroes for instance?
Click to expand...
Click to collapse
Aha! That's the openssl command I was thinking of. I'll look into .Net cryptography and see if I can write a function for it but it might be easier to just script the Unix tools as-is. I'll play with it now and get back to you on it
EDIT: I get a bad decryption error with my SBK / openssl / mmcblk0_start
Sent from my Iconia A500 using Tapatalk 2

blackthund3r said:
EDIT: I get a bad decryption error with my SBK / openssl / mmcblk0_start
Click to expand...
Click to collapse
Your mmcblk0_start is probably not containing an even number of blocks, AES 128 work on blocks of 16 bytes (128 bits).
So if the size of the file is not a multiple of 16 bytes the decryption will fail in the end.
Decrypting like that will technically give an incorrect result as not all data is encrypted.
In the BCT the first block (of 16 bytes) is a hash for the following 4064 bytes, and since we are using cipher block chaining including this in the decryption will mess up the decryption of the second block (which should have been the first block). But in this case we probably do not really care about the 2nd block.

Better Desktop Environment for Ubuntu

Hey everyone
I've been playing round with Ubuntu on my TF101 for quite a while but it was never fast enough to use seriously (school work etc) I stumbled across the Enlightenment DR17 desktop environment and I have to recommend anyone with Ubuntu on the TF101 give it a try (https://help.ubuntu.com/community/Enlightenment). It's made primarily for smartphones and tablets so the touch screen interface is brilliant, Ram usage is very small, looks amazing (Looks like its based on kde) The overall performance is much, much better the unity (about the same as if not faster then xfce). Just thought id share my find, id like to here some opinions of it
Cheers

Looks interesting. I've been thinking about putting Ubuntu on my tf101, but given the default interface I was leaning away from the idea. With this option, I might revisit the idea.
Thanks for sharing!

I really wish there was a step by step guide to install Ubuntu on the tf101cuz the mentioned ones are mostly either out dated or hard to understand, I really love Ubuntu and it running on my transformer

alizafar said:
I really wish there was a step by step guide to install Ubuntu on the tf101cuz the mentioned ones are mostly either out dated or hard to understand, I really love Ubuntu and it running on my transformer
Click to expand...
Click to collapse
If your SBK1 I can help you get it running

Is there any difference (in terms of installing ubuntu) between SBK1 and SBK2 now that we have wheelie?

gbesso said:
Is there any difference (in terms of installing ubuntu) between SBK1 and SBK2 now that we have wheelie?
Click to expand...
Click to collapse
I only say that because ive only installed on SBK1 using OLiFE and Franks tools.(There is a SBK2 version of franks tools now that uses wheelie but i think it has issues). there is also (http://forum.xda-developers.com/showthread.php?t=1537566) for installing on SBK2 but its a hardcore install

I've got an sbk2 device. I'm not opposed to hardcore as long as there's an exit strategy if something goes wrong.

riot929 said:
I've got an sbk2 device. I'm not opposed to hardcore as long as there's an exit strategy if something goes wrong.
Click to expand...
Click to collapse
Yeah easyflasher will be able to restore an SBK2 device

JoinTheRealms said:
I only say that because ive only installed on SBK1 using OLiFE and Franks tools.(There is a SBK2 version of franks tools now that uses wheelie but i think it has issues). there is also (http://forum.xda-developers.com/showthread.php?t=1537566) for installing on SBK2 but its a hardcore install
Click to expand...
Click to collapse
yep I have an SBK 1 ASUS TF101 running team eos Jellybean!
and would love your help

Ok you have two options, you can use OLife on a Linux machine (or Virtual machine) or Franks tools on a windows machine.
OLiFE (http://forum.xda-developers.com/showthread.php?t=1191141)
Download OLiFE prime (http://lilstevie.geek.nz/ports/OLiFE-Prime-Edition.tar.gz)
Extract it anywhere
Put your TF101 in APX mode (Holding vol down, up and power at boot)
Open the extracted OLiFE file and right click the "OLiFE.sh" file Properties/ Permissions then tick "allow executing file as a program"
Double click "OLiFE.sh" then run in terminal, follow instructions til you get to menu, choose flash, dualboot, Android (Then double check your in apx and Linux has detected it)
Press any key
It should start uploading the files (Will take about 30-60 minutes).
Franks tools (http://forum.xda-developers.com/showthread.php?t=1364095)
Download Franks tools (http://livtx.com/frankc123/frankstools.rar)
Download OLiFE prime (http://lilstevie.geek.nz/ports/OLiFE-Prime-Edition.tar.gz) - we use the .img files from OLiFE
Extract them anywhere
Put your TF101 in APX mode (Holding vol down, up and power at boot)
Open the "Images" file in OLiFE Prime and copy the (system,boot,recovery,ubuntu .img's) and paste them in the inside the Frank's tools folder
Open "frankc123" ,"Dualboot A/U" , click install
It will upload files (it will take 30-60 minutes also).
Both methods will require you to boot into Ubuntu by holding volume down and power at the same time (same as booting into recovery)
Then go through the install process as usual.
Pm me if you need further help or if you get stuck.

JoinTheRealms said:
Ok you have two options, you can use OLife on a Linux machine (or Virtual machine) or Franks tools on a windows machine.
OLiFE (http://forum.xda-developers.com/showthread.php?t=1191141)
Download OLiFE prime (http://lilstevie.geek.nz/ports/OLiFE-Prime-Edition.tar.gz)
Extract it anywhere
Put your TF101 in APX mode (Holding vol down, up and power at boot)
Open the extracted OLiFE file and right click the "OLiFE.sh" file Properties/ Permissions then tick "allow executing file as a program"
Double click "OLiFE.sh" then run in terminal, follow instructions til you get to menu, choose flash, dualboot, Android (Then double check your in apx and Linux has detected it)
Press any key
It should start uploading the files (Will take about 30-60 minutes).
Franks tools (http://forum.xda-developers.com/showthread.php?t=1364095)
Download Franks tools (http://livtx.com/frankc123/frankstools.rar)
Download OLiFE prime (http://lilstevie.geek.nz/ports/OLiFE-Prime-Edition.tar.gz) - we use the .img files from OLiFE
Extract them anywhere
Put your TF101 in APX mode (Holding vol down, up and power at boot)
Open the "Images" file in OLiFE Prime and copy the (system,boot,recovery,ubuntu .img's) and paste them in the inside the Frank's tools folder
Open "frankc123" ,"Dualboot A/U" , click install
It will upload files (it will take 30-60 minutes also).
Both methods will require you to boot into Ubuntu by holding volume down and power at the same time (same as booting into recovery)
Then go through the install process as usual.
Pm me if you need further help or if you get stuck.
Click to expand...
Click to collapse
question will this delete my current ROM if so how can I dual boot this ROM with Ubuntu
p.s which Ubuntu version is this and what is the productivity value of Ubuntu on a tf101, I am asking this because most of the time I saw Ubuntu running on phones and tablet "via VPN" it was fairly laggy, does running Ubuntu natively solve this issue and what is the case with the new 3.1 Ubuntu optimized kernel?

alizafar said:
question will this delete my current ROM if so how can I dual boot this ROM with Ubuntu
p.s which Ubuntu version is this and what is the productivity value of Ubuntu on a tf101, I am asking this because most of the time I saw Ubuntu running on phones and tablet "via VPN" it was fairly laggy, does running Ubuntu natively solve this issue and what is the case with the new 3.1 Ubuntu optimized kernel?
Click to expand...
Click to collapse
There is instructions on backing up your current rom then copying the files from the back up and re-flash with Ubuntu ive never done it but ull find them here (http://forum.xda-developers.com/wiki/How_to_install_Ubuntu_on_an_Asus_EEEPad_Transformer). you can flash any rom you want once you have it all installed by flashing a temporary CWM (Im running team EOS jelly bean and ubuntu atm) from OLiFE. The Ubuntu .img is 11.10 but can be upgraded to 12.04. The problem with Ubuntu on the tf101 is ram, Unity is very ram heavy and doesn't play well on the TF. XFCE is a much easier on ram, Enlightenment DR17 as in the OP is the best desktop environment IMO very fast and look's good. All the libreoffice apps ive tried work fine. I haven't updated the kernel so i wouldn't know, Jhinta's 3.1 isn't supported anymore but RaymanFX has one in development.
Overall the I found the performance surprisingly fast (and stable). It not gonna run ram heavy applications very well but firefox and the like have no trouble.

JoinTheRealms said:
There is instructions on backing up your current rom then copying the files from the back up and re-flash with Ubuntu ive never done it but ull find them here (http://forum.xda-developers.com/wiki/How_to_install_Ubuntu_on_an_Asus_EEEPad_Transformer). you can flash any rom you want once you have it all installed by flashing a temporary CWM (Im running team EOS jelly bean and ubuntu atm) from OLiFE.
Click to expand...
Click to collapse
And how on exactly do i flash the temp CWM??

alizafar said:
And how on exactly do i flash the temp CWM??
Click to expand...
Click to collapse
Inside OLiFE: update/ advanced/ "Temporary CWM" (called something along those lines), it will install CWM, close OLiFE, then reboot into recovery install a rom as usual power off, back into apx mode then inside OLiFE: update/ "ubuntu/linux kernel" and flash and it will recovery you ubuntu installation and remove CWM.

JoinTheRealms said:
Inside OLiFE: update/ advanced/ "Temporary CWM" (called something along those lines), it will install CWM, close OLiFE, then reboot into recovery install a rom as usual power off, back into apx mode then inside OLiFE: update/ "ubuntu/linux kernel" and flash and it will recovery you ubuntu installation and remove CWM.
Click to expand...
Click to collapse
bro can't thank u enough, just downloaded olive and frank tools and am about to start the process
can't wait to have Ubuntu running
however while the dual boot process I don't have to have an extra ROM image do I ?
I mean during the install the frank tools should keep the android IMG on the main partition right??

alizafar said:
bro can't thank u enough, just downloaded olive and frank tools and am about to start the process
can't wait to have Ubuntu running
however while the dual boot process I don't have to have an extra ROM image do I ?
I mean during the install the frank tools should keep the android IMG on the main partition right??
Click to expand...
Click to collapse
Do you mean the .img of your current android rom? no it will be replaced with the android rom that comes with OLiFE and it will delete all data on the internal stroage just make sure you do a backup before you start, If its just the apps you want to keep you could do a titanium backup of them and reinstall when you get a proper rom installed (The rom that comes with OLiFE is Prime! which is HC)

ok something has gone wrong
i followed the steps u mentioned exactly
and end up with a bricked tablet, not to worry nvflashing it right now
here are the logs
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x033c2083449fd0d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: UBT
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 UBT please wait.. done!
Formatting partition 17 GPT please wait.. done!
done!
sending file: bootloader.bin
bootloader.bin sent successfully
file not found: linux.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
Please help! what have i done wrong??

alizafar said:
ok something has gone wrong
i followed the steps u mentioned exactly
and end up with a bricked tablet, not to worry nvflashing it right now
here are the logs
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x033c2083449fd0d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: UBT
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 UBT please wait.. done!
Formatting partition 17 GPT please wait.. done!
done!
sending file: bootloader.bin
bootloader.bin sent successfully
file not found: linux.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
Please help! what have i done wrong??
Click to expand...
Click to collapse
Errors are to be expect the first time round :silly: Can you check your franks tools folder and see if "linux.img" is in there?

JoinTheRealms said:
Errors are to be expect the first time round :silly: Can you check your franks tools folder and see if "linux.img" is in there?
Click to expand...
Click to collapse
no but an ubuntu one is there, Shall i rename it??

alizafar said:
no but an ubuntu one is there, Shall i rename it??
Click to expand...
Click to collapse
Strange, no i suggest you re download franks tools, extract it then see if its in there if not ill upload it

Possible Nvflash key found

I'm not trying to get my hopes up too high but i think i might of got my partial SBK.I was reading this guide i found on recovering it and decided to try it.
http://forum.xda-developers.com/showthread.php?t=1751978
This is what i came up with on my phone:
0x00000012a33080
Basically most of it seems correct besides all the zeros at the beginning.Not really sure why it won't connect the key in nvflash.Any ideas?When i run it in the sbcalc program i get something similar to the how it should look from an android device.The tutorial says you should have a 64 bit ubuntu/linux system,but there is an option to change the code for 32 bit.If someone out there that has a 64 bit machine maybe they could try it out:
make sure your phone is plugged into the usb port,and the phone is off.
open a terminal,then sudo su(make sure your root)
then this command watch -n2 lsusb (apx doesnt always show up so this keeps checking until it does)
hold down u+s+b plus power on the phone (sometimes i hold then let go of the power while holding the buttons)
once you see something like (Bus 001 Device 031: ID 0955:7416 NVidia Corp) you are in apx mode(ctrl + c to stop the watch command)
after that you need to make the apx.c file.Go back to this guide and follow the instructions on the top on how to make it.The most important thing to do is to change the code ( 0x0955, 0x7820 ) to whatever it says from the lsusb command.Mine is like this( 0x0955, 0x7416 )Once you make the .apx file just open another terminal (make sure its root)then run ./apx
It should pop out a number similar to mine.If you end up with a code something else besides all those zero at the beginning,then there is a chance it make work when we run it in Nvflash
From there goto this website and enter the code in there (delete the x)
http://a500bootloaderflash.tk/sbkcalc/
It should spit out a code like this: 0x07B91000 0x204AF201 0xD09B1103 0xF768F302
So after that you would go back into terminal (sudo su) then run nvflash like this:
./nvflash --sbk 0x07B91000 0x204AF201 0xD09B1103 0xF768F302
If were lucky then it should pop up a whole bunch of info.My hope is that someone will know a little bit more on what i might be doing wrong with the code to get this working correctly.I believe it must be doing something though as it will only display that code when in apx mode.It's getting late over here and spent too many hours trying to figure this out tonight.lol.Let me know if anyone needs help.Good luck.

update
I setup another computer with ubuntu 12.04 x64 and configured a new apx file once again:
0x00fcfe12a33080
It looks like i got closer but still need 15 digits past the 0x to make a correct SBK.Nvflash wasnt having anything i tried so far.I'm still looking for a way to fix this.

Keep up the good work. Glad to see some love coming back to the kin
Sent from my DROID RAZR using xda app-developers app

I found some new commands off a older version of nvflash i was using :
nvflash action [options]
action (one or more) =
--help (or -h)
displays this page
--cmdhelp cmd(or -ch)
displays command help
--resume (or -r)
send the following commands to an already-running bootloader
--quiet (or -q)
surpress excessive console output
--wait (or -w)
waits for a device connection (currently a USB cable)
--create
full initialization of the target device using the config file
--download N filename
download partition filename to N
--setboot N
sets the boot partition to partition N
--format_partition N
formats contents of partition N
--read N filename
reads back partition N into filename
--getpartitiontable filename
reads back the partition table into filename
--getbit filename
reads back BIT into filename
--getbct
reads back the BCT from mass storage
--odm C Data
ODM custom 32bit command 'C' with associated 32bit data
--go
continues normal execution of the downloaded bootloader
options =
--configfile filename
indicates the configuration file used with the following commands:
--create, --format_all
--bct filename
indicates the file containing the BCT
--sbk 0x00000000 00000000 00000000 00000000
indicates the secure boot key for the target device
--bl filename
downloads and runs the bootloader specified by filename
--odmdata N
sets 32bit customer data into a field in the BCT, either hex or
decimal
--diskimgopt N
sets 32bit data required for disk image convertion tool
--format_all
formats all existing partitions on the target device using the config file,
including partitions and the bct
--setbootdevtype S
sets the boot device type fuse value for the device name.
allowed device name string mentioned below:
emmc, nand_x8, nand_x16, nor, spi
--setbootdevconfig N
sets the boot device config fuse value either hex or decimal
--verifypart N
verifies data for partition id = N specified. N=-1
indicates all partitions
Intended to be used with --create command only.
--setbct
updates the chip specific settings of the BCT in mass storage to
the bct supplied,used with --create, should not be with --read,and
--format(delete)_all,format(delete)_partition,--download, and--read
--sync
issues force sync commad
--rawdeviceread S N filename
reads back N sectors starting from sector S into filename
--rawdevicewrite S N filename
writes back N sectors from filename to device starting from sector S
--updatebct <bctsection>
bctsection should refer to the section of the bct we are updating.
Curently we suport updates for following sections
<SDRAM> updates SdramParams and NumSdramSets fields
<DEVPARAM> updates DevParams, DevType and NumParamSets
<BOOTDEVINFO> updates BlockSizeLog2, PageSizeLog2 and PartitionSize
Apart from that i tried everything i could really think of for getting that key.This phone seems to be very locked down and without enough info on the system or where that sbk might be located,i think were back to a dead end again.I know on bitpim there are some files on there that can be downloaded and maybe decompiled or something.(maybe the key is in there)
I was figuring the key would be the same setup as the later tegra devices but i believe its different now.My only guess now is too have someone with a lot of electronics knowledge to find the uart on the board and we could read the nand like that.