Hey,
I'm trying to work around with Linux on my Folio a little bit..
I compiled a kernel and build a boot.img and put it into an update.zip..
This works quite nicely but after updating the boot on the tablet the folio reboots and after the "Toshiba loading screen" the display becomes black and nothing else happens...
So I would like to enter fastboot mode to boot my compiled image easier by
Code:
./fastboot -c "blabla" zImage
...
But when my tablet is in fastboot mode ("Starting fastboot usb download protocol.." appears on the screen) I can't find it when I type:
Code:
./fastboot devices
I also tried this as root but nothing happens.
But lsusb shows my folio:
Code:
Bus 002 Device 012: ID 0955:7000 NVidia Corp.
I'm working in Ubuntu 10.04 64bit with ia32-libs installed!
Also tried to connect on my Windows 7 Desktop PC.
The drivers are installed correctly after adding the lines to the .inf file.
But my Folio100 doesn't appear in fastboot devices too..
Hope you can tell me what I can do to connect to my Folio using fastboot..
Greetz
Philipp
//Edit:
Also tried it on WinXP.. But it doesnt work too..
BTW: ADB-Shell works, so I think there is no problem with usb..
You need a recent version of fastboot, best take the one that comes precompiled with the android sdk. The fastboot binary that is still distributed by htc here does not work.
Also don't forget to set the right udev rules (http://developer.android.com/guide/developing/device.html).
I used the fastboot binary from Nvidia's Linux4Tegra package...
I just downloaded the Android SDK again, but there is no precompiled fastboot binary..
I guess the problem is that I'm using 64bit Linux.. I'm also not able to build the fastboot binary...
I used this udev rule:
Code:
SUBSYSTEM=="USB", SYSFS{idVendor}=="0955", MODE="0666", OWNER="philipp"
I guess this should work for my Device...
I took the vendor id from lsusb...
Thanks for your post.. I'm not at home atm, but I will go on trying later and edit this post..
Now that you mention it, the binary did not come with the sdk, but was compiled as a side product when I compiled cyanogenmod for my old g1. I am also on 64bit ubuntu (10.10), when I have some time I can upload the binary here, but it may take some time (quite busy this weekend).
Udev rule looks fine. If adb works, fastboot (correct binary) should also do.
Shame on me..
Looked at the source code of the fastboot binary and saw that the USB vendor id of Nvidia is not implemented into the source of fastboot >_<
And I also wasn't using -i parameter :-!
Sorry for taking your time^^
But now I'm still having problems with compiling a working kernel..
My kernel doesn't work on the Folio..
The display simply becomes black and nothing happens..
And I'm not able to compile this kernel correctly:
https://github.com/tsh/folio100
I'm trying to make using the following command:
make ARCH=arm CROSS_COMPILE=arm-none-eabi- -j2
and the config provided in the config.gz but I always get this error:
Code:
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h: In function '_iovmm_client_lock':
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h:60:2: error: output number 2 not directly addressable
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h:60:2: warning: use of memory input without lvalue in asm operand 5 is deprecated
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h:80:2: error: output number 2 not directly addressable
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h:80:2: warning: use of memory input without lvalue in asm operand 5 is deprecated
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h: In function 'iovmm_block_put':
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h:98:2: error: output number 2 not directly addressable
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h:98:2: warning: use of memory input without lvalue in asm operand 5 is deprecated
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h: In function 'tegra_iovmm_area_get':
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h:42:2: error: output number 2 not directly addressable
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h:42:2: warning: use of memory input without lvalue in asm operand 5 is deprecated
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h: In function 'tegra_iovmm_find_area_get':
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h:42:2: error: output number 2 not directly addressable
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h:42:2: warning: use of memory input without lvalue in asm operand 5 is deprecated
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h: In function 'tegra_iovmm_client_unlock':
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h:98:2: error: output number 2 not directly addressable
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h:98:2: warning: use of memory input without lvalue in asm operand 5 is deprecated
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h: In function 'tegra_iovmm_free_client':
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h:98:2: error: output number 2 not directly addressable
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h:98:2: warning: use of memory input without lvalue in asm operand 5 is deprecated
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h:98:2: error: output number 2 not directly addressable
/media/data/kernel_source/folio100/arch/arm/include/asm/atomic.h:98:2: warning: use of memory input without lvalue in asm operand 5 is deprecated
I just like to know which kernel was used by DerArtem in his sdmmc/usb-update.zip..
This works for me, but then I'm having problems loading the kernel modules...
What toolchain (i.e. C compiler) are you using. arm-none-eabi- is not within (my) the source tree
For the kernel builds I do, I use <mvidia-android-source>/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/
Note, that the black screen is a known issue with FolioMod 1.4.
The kernel will only work on pre 1.4 versions of the Mod.
Okay I got it now =)
Simply replaced the Header file (atomic.h) with the header-file of the original Linux kernel source for arm and now it works and I'm also able to boot normally (with output on screen)
Do you already got the wifi module running?
I checked out the git source @ nvidia and compiled the kernel module for my kernel.
I'm also able to install it via insmod, but the wifi interface doesn't appear in if/iwconfig..
°EraZoR° said:
Shame on me..
Looked at the source code of the fastboot binary and saw that the USB vendor id of Nvidia is not implemented into the source of fastboot >_<
And I also wasn't using -i parameter :-!
Sorry for taking your time^^
Click to expand...
Click to collapse
Wait a minute... I'm not that fast
Which source code did you use for compiling fastboot and how exactly did you modify it? What is it about that -i parameter?
I'm trying to do the same thing here, flashing with update.zip got pretty annoying... :-/ especially since im just trying to boot several kernels with several command lines... :-/
I used this source:
https://github.com/tsh/folio100
And fechted the asm/atomic.h from somewhere on the net...
The -i parameter is the USB-Vendor-ID..
You have to provide this parameter to tell the fastboot binary which USB device it has to use..
0x0955 is for Nvidia Tegra...
You can get this string by:
lssub
on Linux or in the Device Manager on Windows..
Im also having problems with Fastboot. I have ADB setup and working for Folio. But now device is ****ed up, i have clockwork rec. installed but when trying to flash it flashes system.img fine but when flashing boot.img it returns an error. So i would like to try and fastboot the boot.img to the device or if that fails i atleast can flash stock recovery so i can send it to toshiba. I put my device in fastboot mode, insert mini usb, computer detects Folio, I update driver to the same as ADB uses but i choose bootloader, it all goes well no error. But when writing fastboot devices in command prompt( from adb tools map) all i get is:
? fastboot
I have had my Folio like this for days now and have an open thread about it here:http://forum.xda-developers.com/showthread.php?t=1009587
I need help so if someone who has done this could point me in the right direction i would be most gratefull
Related
Anyone tried to port this to Toshiba Folio?
I see some work here with Vega and Gtablet
http://wiki.meego.com/ARM/TEGRA2
Some video of MeeGo tablet UI.
http://www.youtube.com/watch?v=GB-nnFhGKbk&feature=player_embedded#!
Looks nice. Seems to run on our oldish 2.3.32.9 kernel. Might be worth a try to get this working.
I copy MeeGo to sdcard with dd command and from fastboot ONLY BOOTED(NOT FLASH) 2.6.32 kernel for booting from sdcard(DerArtem's) with this command(like it said in readme file):
fastboot -c "boardtype=PR root=/dev/mmcblk1p1 init=/sbin/init usb-storage.delay_use=0 rootdelay=10 tegrapart=recovery:122000:a00:800,linux:a0e00:1000:800,loader:300:400:800,mbr:700:200:800,system:900:20000:800,cache:20900:80000:800,misc:a0900:400:800,userdata:a1f00:80000:800 [email protected] [email protected] vmalloc=192M video=tegrafb usbcore.old_scheme_first=1 debug" boot boot.img
BUT
during boot I saw that sdcard is recognized,(and) first cpu stopped.(and) I'm not sure for init, it said that init isn't fond(that's ok, I unpacked boot.img and there're nothing in ramdisk folder and there're something else under init not found. Some words and numbers that I don't understand. Init is in /sbin folder, I checked. I set init position in fastboot command(init=/sbin/init) and I forgot, it said that it's try to pass "init=" and after that some strange words and numbers.
Is it problem in booting kernel but I think that isn't, I this thread ==> http://forum.xda-developers.com/showthread.php?t=899976 (post 6, wolfx) he only boots kernel.
What's the problem???
Thank's in advice!!!
Hello everyone I'm new to android and have been trying to run Emscripten on it: I've ported over the necessary dependencies: Node, Python, Fastcomp/Clang via the NDK Toolchain and tested with the Android Emulator (from Android SDK) inside the the Android Terminal Emulator (from jackpal's github) but when I finally attempted to run Emscripten itself as so:
Code:
cd /data/data/jackpal.androidterm/shared_prefs
bin/python2 emscripten-1.22.1/emcc -v
I ran into some rather vague error messages:
Code:
[2] + Stopped (signal) bin/python emscripten-1.22.1/emcc -v
[1] - Segmentation fault bin/python emscripten-1.22.1/emcc -v
Does anyone have any ideas on this? I there a way I can get better debugging info to help find the problem?
I think I figured out the problem. Those error seem to come from python. Particularly python seems to be crashing. Trying the python console doing a simple:
Code:
import shutil
will crash the interpreter. Since discovering this I've found many other things that will crash python in my setup. So I guess it wasn't such a good port after all.
I ran some test in the python interpreter as this is what I go so far:
These modules are fine:
Code:
os, platform, re, pprint, atexit, subprocess, sys, time, string, struct
These modules will crash python:
Code:
optparse, logging, urlparse, SocketServer, cgi shutil, tempfile, shlex
These modules will spit out error messages but not crash python:
Code:
BaseHTTPServer, SimpleHTTPServer, socket,
Don't really, no what is cause this yet.
After trying to build python several different ways and not getting those modules to work I broke down and decided to try out Python4Android. And it works. After following their guide on getting it to work in the shell, I test the modules and they were fine. After that I pushed my builds of fastcomp(llvm/clang) and node.js and the Emscripten python scripts ot Py4A's files location and then tried to run emcc (emscripten's compiler).
The scripts needed a little (very little) tweeking to get them to work but they worked. And now I'm going to try and copy Py4A's files to Android Terminal Emulators' location. If that works to my satisfaction I'll try to get these to work with VimTouch.
I've been working on porting Octave (command line only) to the m8 for a few days now. I have all of its' dependencies compiled now, except for SuiteSparse. It requires output from some components during compile (it first compiles one program, then runs it to generate some data, then uses the data to compile others.) Since I can't run these on a computer, I've created a toolchain to compile on the device itself. Surprisingly, I can get the compiler to run on the device. Unfortunately, I have to use ld to run anything. The command looks something like this:
~$ ld-linux.so /path/to/gcc/tuple-gcc
It outputs just fine. But I can't simply run
~$ tuple-gcc
I have added the path to PATH, but still can't figure it out.
To compile anything I need to specify CC, as well as the other tools, but I can't figure out how to do this if they have to be executed using ld.
Any ideas?
Also, for anyone trying to do this, many configure scripts require "ls -t".
The coreutils that are installed in the base system are extremely stripped down, and ls doesn't support many of its normal switches.
I have compiled coreutils and will be testing them shortly. Hopefully they don't also have to be executed using ld!
***UPDATE***
I now have a fully-working compiler, to compile on the hardware itself.
Will try to make the 10 post minimum soon, to post a tut.
Hi everyone,
I have recently been trying to port Ubuntu Touch to our beloved surnia.
I'm using the phablet-5.1 tree with AOSP-5.1 device, vendor, kernel and other repositories.
I managed to finish the build with the kernel config adapted to work with Ubuntu. (using jamino's phablet-porting-scripts (on github) and patching some files about uid/gid errors). But this isn't the problem, the default defconfig causes the same problems.
I can confirm my kernel/e3 recovery both work and can mount partitions etc, but only when I'm using the
Code:
fastboot boot recovery.img
command AND my custom boot.img isn't flashed to the device.
When trying to boot the recovery directly from the phone I get a
Code:
Error: Failed to load kernel!
error message in the bootloader log.
If my boot.img is flashed to the phone, whatever file I try to load with
Code:
fastboot boot
, I get an error from my computer :
Code:
booting...
FAILED (remote failure)
but no error from the phone
I had to replace the prebuilt gcc toolchains in the android source tree with my system's ones, could it cause the problem?
I'm quite new to android development and all so please don't blame me if the fix is obvious.
Thanks in advance
So I have a few of these Kramer Panels which aren't supported anymore (The official webpage doesn't have them anymore but the same product here) and I want to wipe out the Kronomeet Software they got going on and install some other flavor of Android (I'm thinking Lineage OS).
To start I got adb and fastboot up and running with Aptitude.
Code:
$ adb --version
Android Debug Bridge version 1.0.41
Version 28.0.2-debian
$ fastboot --version
fastboot version 28.0.2-debian
Connecting fine with adb, and using lsusb we see
Bus 001 Device 037: ID 2207:0011 Fuzhou Rockchip Electronics Company SmartTab
Googling around that name led me to the Rockchip Wiki, which had an article on Fastboot and a bunch of open source repos
https://opensource.rock-chips.com/wiki_Fastboot
Which states: "Rockchip uses 0x2207 as its USB vendor ID. This VID is not in Google's original fastboot code. So every fastboot command has to use "-i" parameter to specify vid to fastboot."
However, running -i on fastboot gives me an invalid option error:
Code:
$ sudo fastboot -i 0x2207 devices
fastboot: invalid option -- 'i'
I also tried downloading the most recent version of the android platform tools with fastboot version 33.0.3-8952118, which gave the same results.
Doing any other fastboot command without the -i just has < waiting for any device >
So essentially, I'm trying to figure out how to load a custom rom onto it, and what my next steps try are.
Other Misc Info I've tried:
In the Developer Settings on the tablet, there's no option to enable "OEM Unlocking"
Tablet doesn't have a power button, just a switch, so no pressing power and volume at the same time.
Rockchip seems to have a TWRP image available to build, which I would like to be able to fastboot flash (https://github.com/rockchip-software/TWRP/tree/android-9.0)
There's also a development tool (https://opensource.rock-chips.com/wiki_Rkdeveloptool) that also lets you load firmware.
Using adb reboot bootloader reboots the tablet to a black empty screen, which I can then communicate with the rkdeveloptool.
In this mode, lsusb returns a new name:
Code:
$ lsusb
Bus 001 Device 038: ID 2207:320a Fuzhou Rockchip Electronics Company RK3288 in Mask ROM mode
$ ./rkdeveloptool ld
DevNo=1 Vid=0x2207,Pid=0x320a,LocationID=106 Loader
$ ./rkdeveloptool ppt
**********Partition Info(parameter)**********
NO LBA Name
00 00002000 uboot
01 00004000 misc
02 00006000 resource
03 0000E000 kernel
04 00016000 boot
05 00026000 recovery
06 00036000 backup
07 00050000 cache
08 00090000 kpanic
09 00092000 system
10 00392000 metadata
11 0039A000 radical_update
12 003BA000 userdata
Found some more useful thread, and am trying to use rkflashkit. But still struggling to find out what .img to use.
Firmware Upgrade Guide For RK3188 RK3288 RK3368 Devices
UPD: Rreflashing guide for linux Host PC added. BEFORE START What you need: 1. Image file 2. Host PC (Windows) 3. USB OTG Cable Supported host OS: 1. Windows XP （32/64bit) 2. Windows 7 (32/64bit) 3. Windows 8 (32/64bit) All manipulations I...
forum.xda-developers.com
[Q] has anyone had success flashing a RK3126 based tablet?
Hello, I've got an irulu X30 (expro 30 plus) running stock firmware, nougat 7.1.2 I've been trying to use rkflashtool in linux and androidtool in windows. Both programs can report some device info and read partitions, the img files created...
forum.xda-developers.com