**** BEGIN LOGGING AT Fri Sep 09 02:59:57 2011 Sep 09 07:57:06 lilstevie: I bought a TF101 (yaaaay!) Should I update to the latest android firmware before attempting to switch it to debian? Sep 09 08:25:10 twb: probably not :p you will end up blowing away everything on the fs and need to redo that stuff anyway Sep 09 08:26:36 $coworker said he thought it might have important fixes for the keyboard part or something Sep 09 08:27:10 (He bought a 16G one from RUC a few months ago, and followed your stuff to put Ubuntu on it last week.) Sep 09 08:27:49 well are you going pure linux, or dualboot Sep 09 08:28:00 I don't care about android Sep 09 08:28:01 cause things like prime include dock firmware updates Sep 09 08:28:10 Yeah, I think he is running prime Sep 09 08:28:23 to be honest dock firmware updates really are to benefit android Sep 09 08:28:44 I mean MAYBE it'd be useful to not blow away android on day one, but I kinda doubt I'll ever use it Sep 09 08:29:01 It's not like I ever used windows or vxworks on my netbooks and routers Sep 09 08:29:50 * twb thinks -- I probably shouldn't be drinking either Sep 09 08:32:36 heh, I don't have android on my device Sep 09 08:33:28 Good man Sep 09 08:46:32 Bleh, I forgot I have to get pppd working with this 3G dongle before I'm allowed to play with my transformer Sep 09 08:47:01 lol Sep 09 08:48:31 I have a Pandaboard rev A3. http://www.omappedia.org/wiki/Prebuilt_ubuntu_binaries only mentions up to A2. What to do? Sep 09 08:55:19 soren: it doesn't really matter Sep 09 08:55:52 Ok. Sep 09 08:56:15 soren: https://wiki.ubuntu.com/ARM/OmapNetbook only has one image Sep 09 08:56:40 and the only difference between the A2 and A3 is the CPU has been updated for ES2.2 Sep 09 08:59:26 I'm installing the headless image on an SD card right now. I don't have a serial cable handy. I don't suppose that image comes with any sort of networked access (ssh or even telnet)? Sep 09 09:02:03 that I don't know I don't have a panda, nor have I used the headless image before Sep 09 09:03:41 Ok. Sep 09 10:03:32 OK, got the 3g doodad working, back to transformer Sep 09 10:03:51 * twb digs up pile of napkins from last week when we were talking about this Sep 09 10:12:25 OK, so step #1 of flashing it is to find a copy of the nvflash ELF binary that can be trusted, i.e. download it myself from nvidia.com rather than "some forum post" Sep 09 10:13:07 Is that achievable? AIUI it's only available bundled in their dev board SDK, but I'm happy to download 200MB of zip file to get a trusted version of that one binary. Sep 09 10:20:31 twb: it is in the L4T pack Sep 09 10:20:36 which isn't that big Sep 09 10:20:44 Do you have the exact URL on you? Sep 09 10:20:58 Otherwise I'll wade through their search page Sep 09 10:23:30 FFS, all the ddg.gg hits are 404d Sep 09 10:23:41 http://tegradeveloper.nvidia.com/content/linux-tegra-release-12-alpha-1-released Sep 09 10:23:48 ty Sep 09 10:24:10 driver package has nvflash binary Sep 09 10:26:11 Man, 10MB, why do all these forum weenies keep reposting it Sep 09 10:26:49 It's like those bt users who put a bunch of .rar's in another rar Sep 09 10:27:16 there is a deb of that driver (not sure it will work on your kernel thrugh) Sep 09 10:27:55 https://launchpad.net/~ac100/+archive/ppa Sep 09 10:28:58 Well, eventually I'd like to run stock Debian armhf kernel with as few device-specific patches as possible, but for now I was just going to git clone lilstevie's tegralinux one and compile that Sep 09 10:29:06 twb: well I begrudgingly package it, if I didn't I would have a bunch of people continually complaining that my pack doesn't work Sep 09 10:29:24 twb: which one, my repo has 2 :) Sep 09 10:29:55 one is L4T driver compatible but only works with u-boot Sep 09 10:30:03 Dunno, I was gonna ask you once I was confident I had nvflash working and metastrap was chugging away building a btrfs debian sid armhf rootfs :P Sep 09 10:30:16 Oh, I can replace the bootloader with uboot? Sep 09 10:30:20 * twb like uboot Sep 09 10:30:40 yes, but u-boot is in its infancy Sep 09 10:31:07 Meaning that it isn't production-ready for this device? Sep 09 10:32:04 it is missing some stuff :p Sep 09 10:32:08 I mean, I'd like to minimize my use of non-free software, but at the same time I don't want to brick it or not be able to e.g. use the screen Sep 09 10:32:30 APX is always there Sep 09 10:32:42 That's the stage 1 bootloader? Sep 09 10:32:51 bootrom Sep 09 10:32:55 stage0 Sep 09 10:33:17 OK Sep 09 10:34:09 It would be nice if I could interactively pick which kernel to boot and whether to pass "single" to it, but I'm assuming that's... nontrivial at the moment. Sep 09 10:34:26 well you could do that with the standard bootloader Sep 09 10:34:47 Oh, OK. I thought that only had two options "normal boot" and "recovery boot" Sep 09 10:34:57 by adding single to the recovery kernel :p Sep 09 10:35:11 Yeah, that's plan B Sep 09 10:35:37 two kernels plus single vs. no single means four cases not two :P Sep 09 10:35:38 if we can get the GPIO driver to co-operate with u-boot it would be trivial Sep 09 10:35:47 but at the moment it is non-functional Sep 09 10:35:50 OK Sep 09 10:36:13 That ac100 PPA has a main and restricted in pool/, but only a main in dists/. Sep 09 10:38:04 ogra_: doing 'dhclient -r;dhclient wlan0' seems to add the route, RE: network manager not setting the default route for me in oneiric Sep 09 10:38:22 weird Sep 09 10:38:32 did you file an NM bug ? Sep 09 10:38:50 not yet Sep 09 10:39:12 was about to do that, only hit me today to try renew the lease Sep 09 10:39:26 renewing* Sep 09 10:51:08 twb, go to the package details,. thats a launchpad bug (the package has "restricted" in the control file, LP doesnt really have a concept for restricted packages) Sep 09 10:51:28 OK Sep 09 10:51:47 was just mentioning it fyi Sep 09 10:52:35 yeah, its known :( Sep 09 10:52:55 for the P release we will hopefully have the driver in the actual archive :( Sep 09 10:52:57 err Sep 09 10:52:58 :) Sep 09 10:53:56 lilstevie: awesome, that version of nvflash is 1) statically linked; and 2) has --help. Much nicer than "doesn't run at all" old version from that I was looking at last time Sep 09 10:54:13 (static linking = works without a 32-bit userland) Sep 09 10:55:14 twb: hmm, well the one in my package is from that dump Sep 09 10:55:24 the other one floating around is the asus one Sep 09 11:05:25 OK, this is weird Sep 09 11:05:56 I connect the keyboard (dock) 40-pin connector to my laptop, and lsusb can see two devices on it -- both ASUS vendor USB ID, one is a broadcom bluetooth device Sep 09 11:07:58 interesting Sep 09 11:09:06 Ah, nm Sep 09 11:09:15 the bluetooth is just the onboard bluetooth in my netbook Sep 09 11:09:41 Gods, that 40pin cable is flimsy Sep 09 11:16:58 OK, why isn't this working? Sep 09 11:17:09 http://paste.debian.net/128994/ Sep 09 11:18:02 Running nvflash as root seems like the coward's way out; I'd rather just have udev make the tf world-writable or so. Sep 09 11:20:40 i think nvflash uses raw device access, you need root Sep 09 11:21:07 Surely if I have write access to /dev/foo, that is "raw device access" Sep 09 11:22:21 The only related superuser capability I can see is CAP_SYS_RAWIO Sep 09 11:22:29 And that looks to be for something else Sep 09 11:23:11 well, i havent seen anyone getting nvflash to work without root in the 1.5 years i work with nvflash :) Sep 09 11:23:17 if yuo find a way, tell me :) Sep 09 11:23:31 OK, I did this Sep 09 11:23:39 chgrp -Rh twb /dev/bus/usb/* Sep 09 11:23:41 Now I get a different error Sep 09 11:23:47 USB device not found255 Sep 09 11:24:03 intresting Sep 09 11:24:11 Maybe I need to plug the 40pin into the table directly instead of the dock? Sep 09 11:24:13 * ogra_ never had to modify anything to flash his ac100 Sep 09 11:24:24 btw same error running it as root Sep 09 11:24:26 plugging and running nvflash just works Sep 09 11:24:36 ogra_: running as root I bet tho Sep 09 11:24:40 indeed Sep 09 11:24:53 I try to be a bit paranoid :P Sep 09 11:25:00 i only use nvflash for new ac100's anyway though Sep 09 11:25:14 after the first flashing i can flash from userspace Sep 09 11:25:41 yeah openwrt is like that too Sep 09 11:26:49 lilstevie: do I need to do something special to put the TF into guest most? Sep 09 11:26:51 *mode Sep 09 11:28:18 hmm, there is some little "asus sync" thing on the tf's screen Sep 09 11:28:36 ANd another "usb debugging connected" Sep 09 11:46:49 Grmph, I'm not having any joy getting nvflash to see it Sep 09 11:47:06 Maybe I should read the docs more than just --help Sep 09 11:50:11 Hmm, gentoo's tegra2 page says "To power on the board, you need to press *BOTH* the Force Recovery and the Power on buttons until the LEDs power up. Then execute the following command to flash the bootloader." Sep 09 11:51:53 OK, booting while holding the volume down gives "safe mode" Sep 09 11:51:59 ok back Sep 09 11:52:05 sorry disconnected for a sec Sep 09 11:52:41 lilstevie: short version: I'm trying to make "./nvflash --getbct" do something useful Sep 09 11:52:41 you should get error 0x4 if you invoke nvflash like that :p Sep 09 11:53:15 Hum Sep 09 11:53:17 yeah you cant Sep 09 11:53:17 the tf is an SBK locked device Sep 09 11:53:17 you need to use the --sbk option Sep 09 11:53:36 and with that you also need to specify --bl --bct and --config Sep 09 11:54:13 lilstevie: first of all, do I need to do anything on the TF to put it into "upgrade mode" or anything? Sep 09 11:54:43 vol up plus power on boot will put it in APX Sep 09 11:54:52 OK Sep 09 11:55:01 And I need to do that? Sep 09 11:55:54 need to do which? Sep 09 11:56:04 put the tablet in APX? Sep 09 11:56:09 Do I need to put it into APX mode to use nvflash Sep 09 11:56:18 yes Sep 09 11:56:25 OK. Sep 09 11:56:30 nvflash is for communicating with apx Sep 09 11:58:56 goddammit, now it isn't turning on at all Sep 09 11:59:35 ok here we go Sep 09 12:00:59 It seems like from off I can't just hold both vol+ and power and have it boot Sep 09 12:01:57 Do i get any visual feedback when it goes into APX? Sep 09 12:04:00 Aha Sep 09 12:04:11 Answer is no, the screen is off, but lsusb suddenly sees an nvidia device Sep 09 12:04:50 Progress Sep 09 12:05:11 ogra_: you can use nvflash as non-root user provided you have write access to the block device. Sep 09 12:05:40 which you usually dont :) Sep 09 12:05:59 ogra_: but what this means is that you wrie a udev rule to say something like GROUP=disk Sep 09 12:06:06 eeek Sep 09 12:06:10 Then instead of running it as root, you run it as a non-root user who is in the disk group Sep 09 12:06:21 thats more of a security hole than using root Sep 09 12:06:30 Yes, well, you know what I mean. Sep 09 12:06:35 the disk group should never be used for users Sep 09 12:06:55 If you want use polkit or something to hand it to the user on the local screen or whatever Sep 09 12:06:59 * ogra_ -> off for a phone conf Sep 09 12:07:03 np Sep 09 12:07:20 later ogra_ Sep 09 12:07:29 lsusb can't see it anymore after doing that bct (which did finally fail with error 4) Sep 09 12:07:55 yep that is cause of SBK Sep 09 12:08:19 error 0x4 is when the command is invalid Sep 09 12:08:40 Does it quit APX on the first command, or the first bad command? Sep 09 12:08:53 which in the case of these SBK locked devices that means the command is incorrectly encrypted Sep 09 12:09:24 it shuts down USB communication, only on incorrect bootrom commands Sep 09 12:09:32 OK Sep 09 12:10:21 but when you use an SBK locked device you need to upload the miniloader (built in to nvflash) and bootloader to get interactive Sep 09 12:10:47 at which point commands are no longer encrypted anyway Sep 09 12:11:02 OK, the SBK in your forum post (ending in 98) works for me, yay. Sep 09 12:11:15 awesome :D Sep 09 12:11:26 So now I have a working nvflash I need to learn how to use it. Sep 09 12:11:45 First goal is to make a complete dump of all the data on there to begin with, just in case I ever want to put it back Sep 09 12:11:54 ok, well best thing is to pass it create, and just configure the flash config Sep 09 12:12:13 ok ./nvflash -r --download Sep 09 12:12:46 Shouldn't I get the partition table first? :-) I don't know /a priori/ what partition IDs there are Sep 09 12:13:33 well you could do that :p Sep 09 12:13:40 but why reinvent the wheel Sep 09 12:14:04 http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/ Sep 09 12:14:34 Because I trust a dump I make myself more than "what some guy told me" Sep 09 12:14:48 Same reason I wanted to get nvflash direct from nvidia.com Sep 09 12:15:07 (No offense intended, I'm just a paranoid sysadmin.) Sep 09 12:15:18 nono I mean for flash.cfg and bct Sep 09 12:15:46 So presumably you can't just say "nvflash, please fetch flash.cfg and bct from my device, and write it to a file" ? Sep 09 12:15:52 no Sep 09 12:16:04 what you get is a basic information Sep 09 12:16:18 OK, then I fall back to plan B, which is using the prepared version you linked to :-) Sep 09 12:16:19 which you then need to work on Sep 09 12:16:36 and bct is something that is not really easy to get :p Sep 09 12:16:44 on device it is encrypted Sep 09 12:16:57 Yeah but symmetrically -- you have the shared secret :-P Sep 09 12:17:02 yeah Sep 09 12:17:03 :p Sep 09 12:17:18 Also this is the 32GB version -- does that matter? Sep 09 12:17:22 no Sep 09 12:17:26 Phew Sep 09 12:17:30 flash.cfg is universal Sep 09 12:17:38 Does it matter for bct? Sep 09 12:17:49 the 0x808 partition ID fills to end of partition Sep 09 12:17:55 OK, awesome Sep 09 12:18:12 and no bct is config data for the tegra2 cpu not the emmc controller Sep 09 12:18:23 Ooooh right Sep 09 12:18:26 and er, partition attribute to end of flash* Sep 09 12:19:23 I am used to in uboot sheevaplug where IIRC your "partition table" is basically half a dozen disk offsets and to boot you say "jump to block XXX of the MTD and start executing whatever you find there" Sep 09 12:19:38 I thought bct was that stuff Sep 09 12:19:44 ah Sep 09 12:19:52 afk getting caffeine Sep 09 12:19:59 thanks for all your help btw Sep 09 12:20:01 on sheeva bct is in the SPI IIRC Sep 09 12:20:56 cya Sep 09 12:23:55 back Sep 09 12:24:18 heh that was quick :p Sep 09 12:24:31 got a coffee machine in the office Sep 09 12:25:54 ah Sep 09 12:26:20 Ah, OK, I got bct mixed up with these .cfg files in your linux-flash-kit.tar.gz Sep 09 12:27:25 yeah the cfg files are the partition Sep 09 12:27:26 Is flash/default.cfg the flash.cfg that matches a brand new tf? Sep 09 12:27:50 yes Sep 09 12:28:40 You know, it just occurred to me that if nvflash wants to write to a file instead of stdout, I won't have space to write it on my netbook Sep 09 12:29:01 I was planning more like dd if=/dev/sda1 | gzip >sda1.orig.gz Sep 09 12:29:04 nvflash normally writes out to stdout Sep 09 12:29:09 Cool Sep 09 12:29:18 oh wait you mean for the backups? Sep 09 12:29:22 Yeah Sep 09 12:29:36 e.g. --getbct wants me to provide --bct-file or so Sep 09 12:29:40 the partition with UDA is the emmc Sep 09 12:29:47 OK Sep 09 12:29:56 well, the "emmc to android" Sep 09 12:30:49 the rest of your backup isn't that big Sep 09 12:31:01 OK Sep 09 12:31:23 don't need to back up PT, USP Sep 09 12:31:37 PT is generated at nvflash --create Sep 09 12:31:58 USP is the "staging" partition that blobs are written to from android Sep 09 12:32:24 for OTA updates Sep 09 12:33:00 Is android using ext3 or 4? Sep 09 12:33:08 ext4 Sep 09 12:33:10 Because default.cfg says 3, but the licenses page in android on the device, says ext4 Sep 09 12:33:13 OK Sep 09 12:33:22 it is ext3 for nvflash Sep 09 12:33:35 because nvflash doesn't know or understand the difference Sep 09 12:33:36 Yeah, I guess nvflash doesn't distinguish. Sep 09 12:33:50 Wish I knew what it actually did different for "ext3" vs "basic" Sep 09 12:34:10 What lives in MSC? Sep 09 12:34:30 tags Sep 09 12:34:36 as for ext3 vs basic Sep 09 12:34:43 it writes it differently Sep 09 12:34:55 basic just does a 1:1 raw write Sep 09 12:35:19 but MSC I guess really does not need to be backed up either Sep 09 12:35:22 Whereas ext3 only writes active blocks? Sep 09 12:35:31 something like that yeah :) Sep 09 12:35:37 Yeah, cool. Sep 09 12:35:48 still takes a full image, but only writes the ones that have content Sep 09 12:35:59 Even if I completely hose the UDA partition, I can still drop into APX and upload a new one, right? Sep 09 12:36:05 Because I plan to use btrfs :-) Sep 09 12:36:09 even easier Sep 09 12:36:09 :p Sep 09 12:36:19 UDA is "User DAra" Sep 09 12:36:25 haha Sep 09 12:36:50 so like in android, drop to CWM and do a factory reset Sep 09 12:36:52 :) Sep 09 12:37:00 "honolabaru data-san" Sep 09 12:37:32 CWM is the rescue partition? Sep 09 12:37:47 Like, the rescue mode uses a completelt separate root= filesystem? Sep 09 12:37:55 CWM is Clockwork Recovery Mod Sep 09 12:38:15 android recovery doesn't use a root= perse Sep 09 12:38:20 per se* Sep 09 12:38:33 the initrd is / Sep 09 12:38:44 and things like /system get mounted atop it Sep 09 12:38:53 android doesn't pivot_root Sep 09 12:39:07 Christ, that's... unnervin Sep 09 12:39:32 I mean I work with some elaborate initramfs's, but nothing like android or splashtop Sep 09 12:40:25 well android has its base set of tools in the initrd as well as the init info Sep 09 12:40:35 but the android system itself gets mounted into /system Sep 09 12:41:10 I certainly don't consider it "normal" Sep 09 12:41:35 Silly embedded devs :P Sep 09 12:41:47 heh Sep 09 12:43:00 the bootimg is really just a zImage squished up with an initrd, + a custom header with some information for the bootloader Sep 09 12:43:33 Yeah, that's how devicevm does it for their splashtop images, too Sep 09 12:44:01 not all android devices follow that though Sep 09 12:44:04 samsung don't Sep 09 12:44:08 When you compile the kernel you can even say "my ramdisk is that dir over there, tack it onto the end of the zimage" Sep 09 12:44:26 they use an initramfs compiled when you compile the kernel Sep 09 12:44:41 using the proper zImage packing method Sep 09 12:44:56 because they use a partition called params Sep 09 12:45:12 samsung use a u-boot based bootloader though Sep 09 12:45:27 So: ASUS are doing it wrong, film at 11 Sep 09 12:46:01 param.lfs is an j4fs filesystem with a param.blk which acts as nvram Sep 09 12:46:02 At least it's not using a damn graphical EFI BIOS like these new x86-64 motherboards I got last week Sep 09 12:46:10 heh Sep 09 12:46:18 I'm used to EFI tbh Sep 09 12:46:25 all my computers have EFI Sep 09 12:46:38 well AppleEFI Sep 09 12:46:39 "Sorry, we only support huge yelling bouncing icons, not text. This way is TEH FUTURE" Sep 09 12:47:06 I am referring to MSI ClickBIOS Sep 09 12:47:12 ew Sep 09 12:47:20 need something like rEFIt Sep 09 12:47:26 Last time I touched Apple it was still using OpenFirmware, which I still looooove Sep 09 12:47:40 OF was win Sep 09 12:47:44 I miss OF Sep 09 12:48:03 And POWER beats x86-64 Sep 09 12:48:13 hands down Sep 09 12:48:24 thats why my file server is an xbox360 :p Sep 09 12:48:42 I'm not happy about ARM's royalty model either, but they've pretty much won the embedded space Sep 09 12:48:44 using the JTAG hack ofc Sep 09 12:49:08 ARM may have a shoddy royalty model, but their processors are win in the embedded space Sep 09 12:49:15 Yep Sep 09 12:49:43 I couldn't imagine going back to MIPS or the likes Sep 09 12:49:43 Although I think they should probably ditch thumb and jazelle and stuff and just bake one ISA into any given core Sep 09 12:49:58 thumb does have its benefits Sep 09 12:50:01 lilstevie: Forth is best for microcontrollers tho Sep 09 12:50:07 REPL FTW Sep 09 12:50:48 You said MSC is for tags -- what are tags? Sep 09 12:51:02 well like bootloader args Sep 09 12:51:23 kinda what I was trying to say, but a bit more complex Sep 09 12:51:43 they also serve as tags for telling recovery to do certain actions Sep 09 12:52:23 most common use though is a file called recovery tells the bootloader to boot straight into recovery Sep 09 12:55:02 Oh, OK Sep 09 12:55:24 So kinda like a combination of nvram, syslinux.cfg and /forcefsck Sep 09 12:55:40 kinda' Sep 09 12:55:48 just done very wrong Sep 09 12:55:52 Heh Sep 09 12:56:24 I hate the bootloader Sep 09 12:56:35 One day Sep 09 12:56:44 One day we will have coreboot on the PROM Sep 09 12:56:53 I'd love to see UEFI :p Sep 09 12:57:18 And it will not load seabios or refit, it will load the openfirmware implementation that sun dumped into coreboot just before oracle ate them. Sep 09 12:57:34 heh Sep 09 12:57:44 EFI... saying "DOS 6 like UI!" as if that's a good thing Sep 09 12:57:55 :p Sep 09 12:58:17 And it is, man, it even has commands like "dir" Sep 09 12:58:26 And you run "if" at the prompt and it says "error: only works in batch scripts" Sep 09 12:59:51 heh Sep 09 13:00:07 Ruh roh Sep 09 13:00:11 ./nvflash --read UDA /dev/stdout --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 | file - # <-- hung Sep 09 13:01:47 ok have you already uploaded the bl and stuff? Sep 09 13:01:55 Nope Sep 09 13:02:00 also by ID I mean the numerical ID Sep 09 13:02:15 you need to put it into bootloader update mode Sep 09 13:02:40 apx wont listen to many commands when an SBK is set Sep 09 13:03:16 Do I do that with ./nvflash --bl --sbk ...; and then it's in bootloader update mode until next reboot? Sep 09 13:03:50 Ah, I need a bootloader.bin? Sep 09 13:04:52 yes Sep 09 13:04:58 and you also need a bct Sep 09 13:05:15 I notice the bootloader.bin you supply doesn't match any of the ones in tegra-linux-12.alpha.1.0 Sep 09 13:05:44 no Sep 09 13:05:47 it is an asus one Sep 09 13:06:06 Hum. Can I d/l that from foo.asus.com? :-) Sep 09 13:06:30 yes Sep 09 13:06:49 in the dlupdate you need to extract a file called "blob" Sep 09 13:06:50 Got the URL handy? Sep 09 13:06:57 no sorry Sep 09 13:11:46 Is it the stuff labelled "firmware", like 200MB dl file? Sep 09 13:12:41 yep Sep 09 13:13:49 OK Sep 09 13:15:39 Damn page needs js, and isn't working even in my fallback js-capable browser :-/ Sep 09 13:15:50 :/ Sep 09 13:23:19 OK, reverse-engineered their js Sep 09 13:24:07 heh Sep 09 13:26:49 It's EeePAD/TF101/UpdateLauncher_US_epaduser8659.zip, just need the hostname... Sep 09 13:28:14 Which is in http://support.asus.com/js/Download.js Sep 09 13:29:17 Bam: http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epaduser8659.zip Sep 09 13:29:40 * twb closes Xorg again Sep 09 13:43:00 lilstevie: FYI, the md5sum of blob also doesn't match yours Sep 09 13:43:13 ? Sep 09 13:43:28 oh right you are doing an md5 of the entire blob Sep 09 13:43:28 :p Sep 09 13:43:36 * twb sighs Sep 09 13:43:40 Lemem guess another yak to shave Sep 09 13:43:42 that blob is 4 or 5 partitions worth od data Sep 09 13:43:46 of* Sep 09 13:44:06 Oh, stupid me, the blob is the whole thing Sep 09 13:44:08 https://github.com/AndroidRoot/BlobTools Sep 09 13:44:13 not the whole thing Sep 09 13:44:54 Gotcha Sep 09 13:44:57 but it is the partitions EBT(bootloader) PT(tegraparts pt) SOS(recovery kernel) LNX(normal boot kernel) at minimum Sep 09 13:45:45 also there are multiple versions of the bootloader Sep 09 13:45:51 so md5 may not match Sep 09 13:46:11 there are at least 7 versions Sep 09 13:46:22 I might as well use the latest one from that blob tho, right? Sep 09 13:46:26 but only 3 are visually noticeable Sep 09 13:46:34 yeah, well, doesn't really matter :p Sep 09 13:47:03 only thing with the newest is that to boot from root=/dev/mmcblk1p* you need to add a rootwait Sep 09 13:47:23 Hum Sep 09 13:47:52 that is the microsd Sep 09 13:48:18 Oh, no, I only care about booting from eMMC Sep 09 13:48:28 yeah :p Sep 09 13:48:33 Except if I completely brick it, in which case SD isn't gonna work either Sep 09 13:51:00 you can't completely brick :) Sep 09 13:51:03 APX is always there Sep 09 13:51:07 k Sep 09 13:51:30 Apparently OMAP on the ROM has enough smarts to boot off a FAT16 SD card, no matter what Sep 09 13:51:45 Which is pretty nice, even if you have to carefully align the CHS and shite Sep 09 13:51:58 *Apparently on OMAP boards the ROM Sep 09 13:53:07 tegra2 does too Sep 09 13:53:12 well, Sep 09 13:54:35 tegra2 can change boot devices Sep 09 13:55:45 but in our case the reason it drops back to APX is because the tegra2 only has the eMMC configured as a boot device Sep 09 13:57:19 OK, so which blobunpack result is bootloader.bin ? Sep 09 13:57:37 blob.EBT Sep 09 13:57:52 Ha, so it's not an AmigaOS bitmap font :P Sep 09 13:58:09 they are named for the partition code Sep 09 13:58:44 so EBT refers to EBT in the flash.cfg Sep 09 13:58:53 Nod Sep 09 14:03:08 OK, so now I have a bootloader.bin that I can trace back to asus.com, and a bct from "some guy", and I need to load these in using -bl Sep 09 14:12:24 twb: not really "some guy" :p the guy who gave the tf root, and who got the sbk for nvflash in the first place :p Sep 09 14:12:40