Related
Hi tereg,
[SIZE=-1](If you are not tereg, you can stop reading this. I didn't PM because I needed to ship an attachment)[/SIZE]
Have a look at the attached (custom) recovery (pick it apart and diff it against the leak-V3/RUU recovery.img) using split_bootimg.pl and the gunzip | cpio pipeline.
You can flash it to your recovery partition and run it if you like, it doesn't do anything dangerous. Basically, it is the same thing as the Leak-V3(=RUU = OTA-2.1) recovery, with two major changes:
- /sbin/recovery service is turned off so this doesn't run automatically (and as a result you won't see the splash screen change from the 3 skating droids). You can run it manually, though, from the adb shell - just wait 8-10 seconds and adbd will come up.
- I added the shell (sh) and a few of the diagnostic tools (dmesg, dumpstate, logcat... and supporting dynamic link libraries, the linker, etc), and dropped in there both /system/bin/toolbox (HTC) and /system/xbin/busybox and created some of the symlinks so that an adb shell has a useful set of tools available. (Oh yeah, I added an /etc/fstab as a convenience for /system/xbin/mount. Note the system mtd partition mounts at /os-system so it won't cover up all the installed tools underneath /system in the boot image)
- I altered the init.rc (and default.prop) so that adbd will always come alive - not just when a race is won.
The base of this image (kernel, bootscripts, /sbin), is the leak-V3 recovery.img; everything else such as dynamicly linked executables and supporting dynamic libraries comes from Jcase's Plain Jane, which in turn comes from Leak-V3/OTA/RUU, so, essentially everything in this bootable recovery comes from HTC except the version of busybox in /system/xbin and mods to the init scripts and default.prop
Note that the NAND flash partition in the mtd device for the recovery is only something like 5.2 MB - I would have added more, but was starting to get tight on space.
If you want it to run as close as possible to the timing of the HTC leak-V3 recovery.img, what I would do would be the following:
- defer all the symlinking in init.rc (except for the "sh" and "ln", of course) and package that up into a shell script that you can run after the recovery has booted
- uncomment (re-enable) the "recovery" service (/sbin/recovery)
- maybe experiment and see if you can get the complete kernel boot sequence from dmesg without starting logcat as the first service (that's not done in the normal recovery).
The only other useful piece of info that I can think of at the moment is that you need to use the ---base option with mkbootimg with an address that starts with something like 0x11208000..... (I can't recall and my machine is down - crap.) You can discover the value of the kernel base address load offset for the Eris by snooping through a hexdump of the beginning of any valid Eris bootable image
cheers
bftb0
MD5s
5801babcdf4e6e5d51e5f775aad0a09e ErisNoRecovery-recovery-v0.9.0.img.zip
4d280b367be75e7e75563a6357575ea7 ErisNoRecovery-recovery-v0.9.0.img
Sent via my nearly dead crap Pentium II booted from a 2003 version of Knoppix - 256 megs of EDO RAM - woot!
Sorry, here's the attachment
I read it anyway.
Suck it.
Hungry Man said:
I read it anyway.
Suck it.
Click to expand...
Click to collapse
Same Here Brosidon,
Well, actually i attempted to read it. Then I got confused and went and got some beef jerkey.
mmm beef jerky. i read it to maybe there will be a fresh recovery menu for the eris.
i read somones got beef jerkey and not sharing *waves fist* four messin up kid
j/k
it would be nice if we got an updated recovery. especially now learning that we won't need/be able to format our sdcards using FroYo.
Actually, I don't mind if anybody reads or uses that - it just gets me off the hook when somone asks
"But what is this for?"
Now someone will ask, LOL
bftb0
bftb0 said:
Actually, I don't mind if anybody reads or uses that - it just gets me off the hook when somone asks
"But what is this for?"
Now someone will ask, LOL
bftb0
Click to expand...
Click to collapse
but what is this for??? can i root my eris 2.1 v3 leak??? can it make pizza out of code? jk jk lol,
Thank you, I got it now.
I will definitely be experimenting with this. I'll let you know if I have further questions.
Tereg, I'll be online tonight and can help with testing.
The advent vega has started shipping in the UK, hardware is very similar except it does not have 16gb internal memory. A system image has been made available by advent, is this something you can use with the Viewsonic? Videos of the vega show it is very responsive
http://www.myadventvega.co.uk/boot_update_20101119_v1.0.3_dix.zip
mcb00f said:
The advent vega has started shipping in the UK, hardware is very similar except it does not have 16gb internal memory. A system image has been made available by advent, is this something you can use with the Viewsonic? Videos of the vega show it is very responsive
http://www.myadventvega.co.uk/boot_update_20101119_v1.0.3_dix.zip
Click to expand...
Click to collapse
I'd love top get a system update, but that's just a boot.img I think.
I'd be interested in the hardware differences. The picture I saw sure did look a lot like the malata tablets.
The first batch are on their way, i'll keep an eye on the Modaco forums to see whether anyone extracts a system image. I'm still deciding whether to get the VS or the Vega.
This is listed as a full system update, more useful?
http://www.myadventvega.co.uk/softwareImage_v1.02_Vega_Final.exe
mcb00f said:
This is listed as a full system update, more useful?
http://www.myadventvega.co.uk/softwareImage_v1.02_Vega_Final.exe
Click to expand...
Click to collapse
Awesome! thanks - more fun for me!
EDIT: This is actually an nvflash script of some kind. That in itself doesn't bother me, except that it's Windows based.
roebeet said:
Awesome! thanks - more fun for me!
EDIT: This is actually an nvflash script of some kind. That in itself doesn't bother me, except that it's Windows based.
Click to expand...
Click to collapse
Well, I was feeling curious/adventureous tonight... So I figured I'd see what would happen were I to actually run this Vega .exe and Flash one of my Gtabs with it...
I have the Tegra SDK loaded so nvflash works normally, but I was pleased that they seem to have included everything anyone would need in this self extracting/excuting exe... it extracts to $TEMP as;
PowerDesk Pro 7 - C:\_Save\Tegra2-Gtab\Vega-1118-Rom\Files Date: 11/23/2
Name Ext Size Type Date Modified Time Attr
bootloader.bin .bin 937,416 VLC media file (.bin)
clean_steps.mk .mk 8,866 MK File 11/18/2010 3:52 PM a
flash.bct .bct4,080 BCT File 11/18/2010 3:52 PM a
flash.cfg .cfg2,064 Config file 11/18/2010 3:52 PM a
installed-files.txt .txt 29,140 Text Document 11/18/20103:52 PM a
kernel 3,001,816 File 11/18/20103:52 PM a
previous_build_config.mk.mk 187 MK File 11/18/20103:52 PM a
ramdisk.img .img 1,247,868 WinZip File 11/18/20103:52 PM a
ramdisk-recovery.img .img 1,481,495 WinZip File 11/18/20103:52 PM a
recovery.img .img 4,487,168 WinZip File 11/18/20103:52 PM a
system.img .img 115,019,520 WinZip File 11/18/20103:52 PM a
android-info.txt .txt 14 Text Document11/18/2010 3:52 PM a
boot.img .img 4,253,696 WinZip File 11/18/20103:52 PM a
libnv3p.dll .dll 51,712 Application Extension
libnvaes_ref.dll .dll 45,056 Application Extension
libnvapputil.dll .dll 80,384 Application Extension
libnvdioconverter.dll .dll 45,056 Application Extension
libnvflash.dll .dll 77,312 Application Extension
lvds.bat .bat 164 Windows Batch File 11/18/20103:16 PM a
nvflash.exe .exe 151,552 Application 11/18/20103:16 PM a
libnvboothost.dll .dll 43,520 Application Extension
libnvos.dll .dll 94,208 Application Extension
libnvusbhost.dll .dll 44,544 Application Extension
So I Plugged in one of my GTabs and Pwr+ Vol+/- to give it a go and...
C:\Temp>nvflash.exe --bct flash.bct --setbct --bl bootloader.bin --configfile fl
ash.cfg --odmdata 0x000c0075 --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17144009417f4317
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xc0075
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 937416/937416 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MSC
failed executing command 16 NvError 0x120000
command failure: create failed
Press enter to continue:
Actually pretty anti-climactic... I figured I was going to need to restore this tab to factory default but tried a power cycle to see what happens and it booted Normally to TNT original with Launcherpro which is where I had started...
Just figured I'd pass this along and save some else the disappointment :>)
Full image means it has a kernel, system image (.apks) so in theory there should bea lot of material that can be extracted from this and potentially incorporated into TNT Lite or even an all new custom rom.
Even the Vega is lightly skinned from what I have read, so still no vanilla tablet.
Thanks for giving it a try!
mcb00f said:
Full image means it has a kernel, system image (.apks) so in theory there should bea lot of material that can be extracted from this and potentially incorporated into TNT Lite or even an all new custom rom.
Even the Vega is lightly skinned from what I have read, so still no vanilla tablet.
Thanks for giving it a try!
Click to expand...
Click to collapse
Yes, thus why I expected to end up with a virgin Vega install... Once it started and actually ran for a while I was actually surprised that wasn't the final outcome... actually ODD that it seems to have failed on creating Partition 5 of 11 in flash.cfg....
I have extracted the saved files from temp so wouldn't be hard to actually pack a clockworks loadable zip I suppose... but as this was so easy to get this far and I'm no pro at packaging something useful for all... I'll leave that to the experts like Roebeet who have a lot of experience here...
Edit... This sure seems an Easy way to package a Full System restore for folks who wouldn't already have the Tegra development enviroment tools loaded, as everything here seems it could be re-made into a self-extracting/executing Zip Exe that anyone with a PC could use as long as the USB drivers were also packaged into the mess...
Making a signed update.zip with a an install script may work out. All the nessecary seem to be there.
Sent from my DROIDX using Tapatalk
I tried replacing boot.img and system.img, both failed. Then I actually nvflashed my entire device (it wasn't pretty).
There may be tidbits in there we could use, but the devices aren't the same.
Here's one thing interesting -- their settings app has a G-Sensor section. But, it FC's when I try to run it on either TnT Lite or zPad Clean 1.0.
Are you able to grab any system apps such as calendar or contacts? Or do they rely on the framework of the vega?
mcb00f said:
Are you able to grab any system apps such as calendar or contacts? Or do they rely on the framework of the vega?
Click to expand...
Click to collapse
The entire system.img in the the .exe (which is really just an archive file)
roebeet said:
The entire system.img in the the .exe (which is really just an archive file)
Click to expand...
Click to collapse
Well, maybe there's something useful... I'm really surprised as thought these tabs were twins with upgrades... Guess I was wrong... again surprised what I tried didn't hose mine as I guess bootloader is close at least... as it flashed successfully and I still came up... I guess they are running different layout based on partitions failing...
THANX for trying... You Da Man!!!
The vega rom looks pretty fast and it looks like Angry birds run on it
Check out the clip
http://www.youtube.com/watch?v=-3sI1aTpdDs
Does this look quicker/more responsive than the G Tablet running TNT Lite 2?
bootloader.bin version?
jtbnet said:
Well, I was feeling curious/adventureous tonight... So I figured I'd see what would happen were I to actually run this Vega .exe and Flash one of my Gtabs with it...
I have the Tegra SDK loaded so nvflash works normally, but I was pleased that they seem to have included everything anyone would need in this self extracting/excuting exe... it extracts to $TEMP as;
PowerDesk Pro 7 - C:\_Save\Tegra2-Gtab\Vega-1118-Rom\Files Date: 11/23/2
Name Ext Size Type Date Modified Time Attr
bootloader.bin .bin 937,416 VLC media file (.bin)
clean_steps.mk .mk 8,866 MK File 11/18/2010 3:52 PM a
flash.bct .bct4,080 BCT File 11/18/2010 3:52 PM a
flash.cfg .cfg2,064 Config file 11/18/2010 3:52 PM a
installed-files.txt .txt 29,140 Text Document 11/18/20103:52 PM a
kernel 3,001,816 File 11/18/20103:52 PM a
previous_build_config.mk.mk 187 MK File 11/18/20103:52 PM a
ramdisk.img .img 1,247,868 WinZip File 11/18/20103:52 PM a
ramdisk-recovery.img .img 1,481,495 WinZip File 11/18/20103:52 PM a
recovery.img .img 4,487,168 WinZip File 11/18/20103:52 PM a
system.img .img 115,019,520 WinZip File 11/18/20103:52 PM a
android-info.txt .txt 14 Text Document11/18/2010 3:52 PM a
boot.img .img 4,253,696 WinZip File 11/18/20103:52 PM a
libnv3p.dll .dll 51,712 Application Extension
libnvaes_ref.dll .dll 45,056 Application Extension
libnvapputil.dll .dll 80,384 Application Extension
libnvdioconverter.dll .dll 45,056 Application Extension
libnvflash.dll .dll 77,312 Application Extension
lvds.bat .bat 164 Windows Batch File 11/18/20103:16 PM a
nvflash.exe .exe 151,552 Application 11/18/20103:16 PM a
libnvboothost.dll .dll 43,520 Application Extension
libnvos.dll .dll 94,208 Application Extension
libnvusbhost.dll .dll 44,544 Application Extension
So I Plugged in one of my GTabs and Pwr+ Vol+/- to give it a go and...
C:\Temp>nvflash.exe --bct flash.bct --setbct --bl bootloader.bin --configfile fl
ash.cfg --odmdata 0x000c0075 --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17144009417f4317
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xc0075
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 937416/937416 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MSC
failed executing command 16 NvError 0x120000
command failure: create failed
Press enter to continue:
Actually pretty anti-climactic... I figured I was going to need to restore this tab to factory default but tried a power cycle to see what happens and it booted Normally to TNT original with Launcherpro which is where I had started...
Just figured I'd pass this along and save some else the disappointment :>)
Click to expand...
Click to collapse
Did you use the original bootloader.bin from the TNT Releases? Someone had commented earlier that the standard bootloader.bin wouldn't work on the gtab. Even the bootloader.bin that was included in the NVIDIA release didn't work for some reason.
dkhilo said:
Did you use the original bootloader.bin from the TNT Releases? Someone had commented earlier that the standard bootloader.bin wouldn't work on the gtab. Even the bootloader.bin that was included in the NVIDIA release didn't work for some reason.
Click to expand...
Click to collapse
I tried that, and it failed miserably. Boot.img is to blame.
They have the same Tegra2, but I think there are too many other differences to make them compatible. Still, we might be able to rip out some things.
You could split the boot.img and use the kernel. Don't know how much of a gain you could possibly get from it. But no one has been able to figure out how the software is bogging the tab down. The hardware in the gtab is very powerful. In my opinion no one has been able to come anywhere near completing a build of android that does the chipset justice. It maybe because the hardware is bleeding edge or it could be that android itself is just not ready to take advantage. Seeing that the gtab is open to modding and more and more devices based off of the tegra chipset are coming out I feel that it will just be a matter of time before our little tablet will truly shine. I have no doubt either that we have more than enough power for future builds of android.
Sent from my DROIDX using Tapatalk
Just in case there might be anything you can extract and use here roebeet:
New 1.04 system image from Advent Vega: http://www.myadventvega.co.uk/softwareImage_v1.04_Vega_Final.exe
Modaco Custom Rom for the Advent Vega, adding market and GApps as you have done for the VS. May be something ele in there you can use:
http://android.modaco.com/content/a...for-the-advent-vega-1-04-with-online-kitchen/
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
I've done the webtop2sd, webtopfix, and installed xfce4 via synaptic. Today I tried to install openoffice from synaptic (along with it's recommended dependencies and extras). I got the following error, which now happens on every package install:
Code:
Setting up openoffice.org-emailmerge (1:3.0.1-9ubuntu3.3) ...
Adding extension /usr/lib/openoffice/basis3.0/program/mailmerge.py...BusyBox v1.10.2 (2010-10-25 17:12:51 PDT) multi-call binary
Usage: mktemp [-dt] [-p DIR] TEMPLATE
Create a temporary file with its name based on TEMPLATE.
TEMPLATE is any name with six 'Xs' (i.e., /tmp/temp.XXXXXX).
Options:
-d Make a directory instead of a file
-t Generate a path rooted in temporary directory
-p DIR Use DIR as a temporary directory (implies -t)
For -t or -p, directory is chosen as follows:
$TMPDIR if set, else -p DIR, else /tmp
dpkg: error processing openoffice.org-emailmerge (--configure):
subprocess post-installation script returned error exit status 1
Setting up openoffice.org-writer2latex (0.5-8ubuntu1) ...
Adding extension /usr/lib/openoffice/share/extension/install/writer2latex.uno.pkg...BusyBox v1.10.2 (2010-10-25 17:12:51 PDT) multi-call binary
Usage: mktemp [-dt] [-p DIR] TEMPLATE
Create a temporary file with its name based on TEMPLATE.
TEMPLATE is any name with six 'Xs' (i.e., /tmp/temp.XXXXXX).
Options:
-d Make a directory instead of a file
-t Generate a path rooted in temporary directory
-p DIR Use DIR as a temporary directory (implies -t)
For -t or -p, directory is chosen as follows:
$TMPDIR if set, else -p DIR, else /tmp
dpkg: error processing openoffice.org-writer2latex (--configure):
subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of openoffice.org:
openoffice.org depends on openoffice.org-writer2latex; however:
Package openoffice.org-writer2latex is not configured yet.
dpkg: error processing openoffice.org (--configure):
dependency problems - leaving unconfigured
Setting up gawk (1:3.1.6.dfsg-0ubuntu1) ...
No apport report written because the error message indicates its a followup error from a previous failure.
I don't know if I really need these packages, and even though I'm an old-timer with Ubuntu (been running since before Jaunty), I'm not as comfortable with dinking around with dpkg and would rather dpkg stop trying to install these every time. Any help would be appreciated.
its a known issuse i dont think it does work n xfce4 i rries it too and it didnr work eather the other type of cusrom webtop it might woek the debian one
i did get gimp to work well
chuck norris aint got **** on this atrix!
That's strange... I have the same setup (Webtop2SD, XFCE4, OpenOffice, and many others) and all is good and dandy...
By webtopfix you mean to fix dependencies?
How big is your EXT partition you installed the Webtop copy through Webtop2SD app?
I created a 4 GB EXT partition to avoid running out of space. I'm not saying that the error you are seeing is because you are running out of space, but could that be the reason?
Also, are you using the latest Busybox release?
Cheers!
Rayan
I created a 4GB partition. Openoffice seems to be working, I've run a few of the apps. I think these are addins that are failing, and it seems to be a busybox issue at that (or perhaps the deb but I doubt it)... And right now I don't know the busybox release.
I also did the chromium install after that and no issue.
I read somewhere that emailmerge doesn't work with webtop, and that's why it keeps doing that. You'll have to remove it somehow... I'm not smart enough to tell you how though.
Kinda doubt this will work:
sudo apt-get purge openoffice.org-emailmerge
Edit: I read your full log. Run webtopscripts again.
Ok, I'll run it again, but I hope this isn't normal to have to run it multiple times after installing things.
Edit: Wow! Either it missed a lot the first time I ran this script, something undid its changes, or it's just reinstalling packages for fun (actually, the first part of the script had a whole bunch of "already installed" messages, so it probably isn't just re-installing).
I've had to run it three or four times as other packages force upgrades. Fixes most issues. Had some packed named ed that can't install or uninstall, removed it by editing its file in /var... something.
Trolling from my ATRIX 4G's XDA premium app, still on the gold medal winner of worst customer satisfaction for the second year in a row! Congrats!
If you can see an app or component inside Sytaptic Manager, you can remove it the same way you installed it. Just select the option to uninstall.
Cheers!
Rayan
On my last rom (Alien v4, Faux 0.22 1.2GHz Kernel, webtop2sd, Webtop v2.3.4, webtopscripts v1.4) I was able to download and install OpenOffice without an issue; but everytime I launched it the webtop-panel would crash. OpenOffice appeared to work fine though. I'll probably install it again here shortly on this FruitCake 2.3.6 setup, installing xfce4 at the moment.
I think the tzdata issue was biting me. I went in and made the recommended change and it finished installing.
viroid said:
On my last rom (Alien v4, Faux 0.22 1.2GHz Kernel, webtop2sd, Webtop v2.3.4, webtopscripts v1.4) I was able to download and install OpenOffice without an issue; but everytime I launched it the webtop-panel would crash. OpenOffice appeared to work fine though. I'll probably install it again here shortly on this FruitCake 2.3.6 setup, installing xfce4 at the moment.
Click to expand...
Click to collapse
It crashes it in debian chroot, but in a normal environment it worked for me.
Trolling from my ATRIX 4G's XDA premium app, still on the gold medal winner of worst customer satisfaction for the second year in a row! Congrats!
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.