Database Info

Linux port to tornado problem?

i use this tutorial to try porting linux to my dopod 577w upgrade to WM6.
http://vivien.chappelier.free.fr/typhoon/index.html
i try boot from EOL (press camera button and power button) and boot Haret directly from my sd card but the result is the same. I got blank white screen .
Anyone can help me??
p/s sorry for my bad english.

Never tried it. But while reading the documentation I've found this:
Important Note: there is a glitch with the USB gadget driver for now, so you _have_ to boot with the phone plugged to a PC using the USB cable, otherwise the kernel will panic.
Did you try this?
EDIT: OK. I tried it and it does not work on my Tornado either! I used both 0.4.7 and 0.4.8 versions of HaRET for booting from within WM6. Maybe there are some Tornado specific option to be set in default.txt (RAM size or RAM address).

NiTroGenious said:
Never tried it. But while reading the documentation I've found this:
Important Note: there is a glitch with the USB gadget driver for now, so you _have_ to boot with the phone plugged to a PC using the USB cable, otherwise the kernel will panic.
Click to expand...
Click to collapse
I already try this both with my xp machine and linux box. Same result boot and i get white blank screen.
I try used old image tux logo appear and then they ask to push enter. Which button represent enter??

There is a guide for running linux on Tornado at WCE.BY forum. I don't speak russian, but I translated it using an online translator:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The needed files can be found here:
http://linuxtogo.org/~law/htctornado/gpephone/images/20070802/
http://rapidshare.com/files/57929506/haret-20070816b.exe
Instructions:
Create a second partition on the memory card, about 64-100MB, and format it as Ext2/3.
Unpack Angstrom-gpephone-image-glibc-test-20070802-htctornado.rootfs.tar.bz2 on this partition.
On the FAT partition place zImage-2.6.16.16-htctornado-20070502071325, haret-20070816b.exe and default.txt.
After placing the memory card back at the phone, run haret, select default.txt and press Run.
OS booting should start and finally you should see the GUI. There may be an issue with date set dialog at first boot, but the author doesn't remember exactly.
Also, if USB cable is attached and network is set up when booting, you can login to your phone by SSH. Details are in default.txt. The author doesn't know how to do it in Windows.
Well, I did not try it because I don't know how to create a Ext2/3 partition from within Windows. Thanks to ega2oo2 for helping with the translation.

NiTroGenious said:
5. - 6. OK!!! I couldn't translate those 2 steps!!! Help, please...
Click to expand...
Click to collapse
5. OS booting should start and finally you should see the GUI. There may be an issue with date set dialog at first boot, but the author doesn't remember exactly.
6. Also, if USB cable is attached and network is set up when booting, you can login to your phone by SSH. Details are in default.txt. The author doesn't know how to do it in Windows.
The author has written this guide from the scratch, and may have missed some details.
My 2 cents

Any hint on uncompressing the .tar.bz2 file to the ext2/3 partition from withing Windows???

I try it but dont work...when kernel boot stoped with notice:
"VFS: No root yet, retrying to mount root on mmcblk0p2(unknown-block(0,0))"
Please append a correct "root"= boot option
Kernel panic - not syncings: VPS: Unable to mount root fs on unknown -block(0,0)

http://e2fsprogs.sourceforge.net/ext2.html
for creating ext2 partitions under windows
you can extract .bz2 archive with winrar www.rarsoft.com

i succesfully created
first 256 mb fat partition on the sd
second 220 mb ext partition on the sd
using the smartphone and wm5 storage
(goide here http://forum.xda-developers.com/archive/index.php/t-267475.html)
i uncomressed the bz2 file to ext2 partition
i copied the required files to the fat partition
rebooted the phone
now the phone is frosen after 'freeing 100 kb" mesage
i will try to debug
did somebody have the same mesage ????

need help to install Incubus26Jc_s RLS10

Hi all,
I have download the following basefiles-20091116:
http://a.imagehost.org/view/0955/a1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and I have download voguimg.nbh + Zimage + Incubus26Jc_s Super FroYo RLS10 Themed.zip
I replaced the Zimage with the new one.
My question is how can I install the voguimg.nbh ? and to add the themed files ?
In the basefile I don't see any nbh files.
Please advice.

please check this thread for detail on flashing to NAND
and this wiki for installing with haret

OK, I have tried to flash via NAND and I got the follwoing error after 33%:
the file that I am tring to run is: voguimg-240x320-froyo-08-07-10.nbh
Please advice.

Yeah... one question..
Why do you try to install a vogue rom on a polaris?
So heres a easy guide:
1. Download this nbh: http://it029000.massey.ac.nz/vogue/files/polaimg-panel3-320-froyo-07-07-10.nbh
2.in your sdcard you have the andboot folder with the androidinstall.tgz from incubus rls10 nothing more
3. Flash, after flash it boots and when the on the screen comes something like "push center dpad to install etc" push the button => you come into installer
(if you miss button no problem just reset)
4. In Installer go to install, yes to both, so install and wipe data.
after its finished wait around half a minute
5. Dont quit, reset (while its in installer, its no problem)
Let it run for its first boot. It can take quite some time, best is to lay it on the desk until you see the first text (Touch to start or smth)

First - thanks for your help
We are in progress...
Now after flash done, the device boot, then I got 2 vibrate and black screen...

Same identical problems.
We need to have a working newest kernel for pola100...
Please anyone ask to DZO why old kernel (29.04.10) works and newer no.
I need to resolve this problem before switching definitely to Android.
Regards.

foxct2005 said:
Same identical problems.
We need to have a working newest kernel for pola100...
Please anyone ask to DZO why old kernel (29.04.10) works and newer no.
I need to resolve this problem before switching definitely to Android.
Regards.
Click to expand...
Click to collapse
So I guess that I am not the only one and finally I did something good...
As far as I understand, all pola100 users should wait for a new kernel ?
Thanks for your help guys

hmm im not sure about this.. On my pola200 this works.
You could try to load a different (older) polaimg from dzo:
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
Or you can take the newes vogueimg and change it to polaris using
loserkaters nbh editor:
http://forum.xda-developers.com/showthread.php?t=689812

To avoid black screen after double vibration, you might want to change panel. Panel 1 works the best for me. However I have read somewhere in this forum, not every TC works with panel 1. Try with haret first and start playing with default.txt changing panel_type value. I finally can use any newer kernel with haret. Btw, you can also check your dmesg for any [error] messages.
PS: I am using pola100 with haret, zimage 02-07-10

I tried the following from the follwoing release (http://forum.xda-developers.com/showthread.php?t=706668):
1. Downloaded the following kernel (POLAIMG-PANEL1-320-ECLAIR.NBH - from Kallt_kaffe VaniljEclair RLS7c (CM5.0.8) - http://forum.xda-developers.com/showthread.php?t=660158
2. Downloaded last build (VaniljEclair_RLS7c.zip) - http://sourceforge.net/projects/androidhtc/files/2010-07-02/VaniljEclair_RLS7c.zip/download
3. Put last build (.tar or .tgz file) on SD card in directory /andboot
4. Flashed by using NBH file together with RUU Update Utility
After flashing done, unix start runing and stucked with the folloing line:
init: Unable to open persistent property /data/property error:2
I see that he failed to mount /data/sysfile on smodem failed: invalid argument
Can any one help ?

Is your sdcard fat32 formatted?

too bad my phone is Panel1 ...

goges said:
too bad my phone is Panel1 ...
Click to expand...
Click to collapse
Try Loserkaters nbh editor for NAND or change default.txt for haret.
NBH Editor : http://forum.xda-developers.com/showthread.php?t=689812

Use BSG choose where you want install (i suggest nand)
select first install
put the script file on andboot folder (with the tgz android install)
don't touch anything
wait and it will install all system
(use one of the latest kernel from here)

I manage to install it but I recive the following error:
sh: 1: unkown operand
Failed
Can't boot from SD without an SD partition
Please advice.

You need to prepare partition before installing the system
If don't want to create them you can use nand or image disk

l1q1d said:
You need to prepare partition before installing the system
If don't want to create them you can use nand or image disk
Click to expand...
Click to collapse
OK, I have 1 GB card, I will create partition.
Do I need a specific partition ? I mean I will split the card to 2 different partitions 800\200 mega each.
Another question, where should I put andboot directory ? for example I will move andboot directory to the 800 mega partition and just leave the 200 partition empty ? correct ?
Should I format both partition as FAT32 ?
Thanks in advance.

You need 3 partion on your sd card. Read this

l1q1d said:
You need 3 partion on your sd card. Read this
Click to expand...
Click to collapse
It's alive...
Thanks for your help

[Q4DEV] Desire HD - where is the hidden partition??

When you take a look at the original ROM file for the ACE device you will see this files below:
- hboot... bla, bla, bla (which is self spelling)
- boot.img (...no comment...)
- recovery.img (...no comment again...)
- system.img (...we all know what's inside)
...a few more files and...
- lib.img (...uhhh??? what's this???)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When you open the lib.img there you can find all the files which belongs to the /system/lib folder.
So far - everything seems to be O.k. BUT now my problem and question.
When I use the PD98IMG.zip to install my device and do a backup with the RECOVERY tool and create .tar files - the /system/lib folder within the backup is empty.
When I do a wipe of my device and erase EVERYTHING on it and I try to restore my backup file this fails. This was driving me nearly crazy until I have found that the /lib folder has his own partition.
First I need to restore the original PD98IMG.zip and after this I'm able to successfully restore my backup.
On the one hand this is a great thing because this will offer more space within the /system partition and this will give the DEV's more options for porting ROM's from and to other devices.
On the other hand - where the hell is the /lib folder or partition or whatever located on the DHD device???
Regards!

I think these files are from the Sense 3.0 leaked ROM for ace rite?
For some reason they've made a separate lib.img & if you want to know how exact & where it is extracted during the installation, unpack boot.img & check init.rc / init.spade.rc..
You'll see few lines in either of the files related to extraction of lib.img..
hope this helps

fshami said:
I think these files are from the Sense 3.0 leaked ROM for ace rite?
For some reason they've made a separate lib.img & if you want to know how exact & where it is extracted during the installation, unpack boot.img & check init.rc / init.spade.rc..
You'll see few lines in either of the files related to extraction of lib.img..
hope this helps
Click to expand...
Click to collapse
Yep m8, this is related to the leaked 3.06 ROM for the ACE.
I guess this might be interesting for some DEV's and this is also a thing which needs to be covered by the guy's who are developing the kernels and ramdisk for the ACE.
Also the 4EXT Recovery should be adjust for the ACE device.
From my point of view this is a good solution to get more space on the /system partition.
The next thing is /data/at folder within the original dzdata.img and the sub folders. This folders will be mounted automatically to the /system partition. Don't know how...
Let me give an example for WhatsApp.apk
The original dzdata.img contains this folder structure:
/data/app
/data/at/app
/data/at/lib
/data/at/plugin
If I store this file within /data/at/app I can use WhatsApp without creating an hard link to the /system/apps folder.
All this things might be interesting for the DEV's.

Just a quick (related) question. How do you unpack dzdata.img?

It might not be a hidden/new partition. Quite the contrary. Notice that with the 3.06, there's a new hboot shipped. I'm theorizing, that it changes the partition layout, chopping up /system into smaller partitions. Now, as we all probably use the eng hboot and a custom update-script for unsigned roms, this doesn't concern us.
Or at least that's my theory. I remember in the sapphire/magic days, the new radio would allot more flash space to /system to fit in SenseUI, while old radio would allot more space to /data.

[TUTORIAL][LINK2SD][ROOT][KK,L,M] For All Devices with Root by HassanMirza01

DESCRIPTION:
Hey Guyz welcome to Link2sd tutorial... After receiving many request for this type of thread, am writing it with screenshots step by step guide with all links
We all know that Link2sd is an app which can extend the apps storage of android smartphone by using 2nd ext4 partition of android's SD Card.
Who can use it ??
Anyone who has root can use this awesome app... support dev for it too
We just need Rooted device and it should be atleast running Android version 2.3-6.0.1
Lets move on it...
PREREQUISITES:
1.) First of all, its assumed that the device is rooted perfectly.
2.) There is SD card available(of good class).
3.) A Laptop or PC
4.) Internet for downloading software
5.) And most importantly, A Brain
PROCEDURE:
Now the Procedure for all devices except Android 6 Marshmallow is same.
So we will move with categorizing android versions as 2.3-5.1.1 and 6.0
COMMON METHOD FOR ALL ANDROID VERSIONS:
First of all, download this software named MiniTool Partition Wizard Professional
and attach the Memory card to Laptop/PC using CARD READER i repeat CARD READER not using phone or any other way.
When you have done that, open installed MiniTool Partition Wizard Professional software,
It will show you the detailed info o all partitions attached with your Laptop/PC.
At the last, there will be your memory card attached and it will be with FAT32 style. like in this pic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now Right click on this Memory card partition and click delete... like this
now right click on this card and select Create
and then select Create as "Primary"
File system should be "Ext4" and select the memory of memory card you want to donate to Link2sd for linking apps.
i selected 2.0GB for it like this
Now click ok and you will see you partition on minitools partitions tool. like this
Now right click the unallocated space and click create.
Now create as "Primary"
File system should be "FAT32" now.
Click ok and its done. like this now
Now click Apply present at top Left corner and it will do all tasks we did.
Times to remove sd card from Laptop and Insert in Smartphone now.
Switch on and download Link2sd from Play store... Here is the Play link for Link2sd
Open it and it will Promped Supersu permission, grant it and then it will ask you for the 2nd partition of your SD Card,
click ext4 and then click ok... it will create script and ask for reboot. Now you will be able to link apps to sd card's 2nd Partition.
If you gets the error that unable to create mount script, failed etc see Marshmallow method for its solution
METHOD FOR ANDROID 6 MARSHMALLOW:
On Marshmallow, after doing same above method, in last, while creating script, you will get error that mount script not created blah blah blah!!
Ignore it, no problem, Don't uninstall Link2sd,
Install another app named App2sd:All in one tool from here Play Link for App2sd
Now open this app and give root permissions,
now click the Link apps to SD Card.
It will ask for partitions style, select ext4 and dont tick init.d support, and done it, it will successfully create the script...
Now you wish if you want to use app2sd for linking or Link2sd.
Open link2sd and see storage, it will show u 2nd partition too cause app2sd write script for link2sd too too nice app
Now you are able to Link apps on any device
Hit Thanks and Support me if you Like and get help from this thread...Thank you...
Contributors:
@HassanMirza01
Created on: 2016-04-16
Last Updated on: 2016-04-16

reserved

Android 10+ system file r/w access

Hi what is secret to using file manager on phone Android 10+ with su access to read and write in system - remove bloat apps? I have su access, but I read in 10+ file system not allow from file manager, only need use adb. How to use file manager with su to remove manually on Android 10+? I get error when deleting app from any file manager with su access "cannot delete". Danke.

Well, i guess that i can reply your question. It seems that we can't mount R/W due to Google's use of dynamic partitions for new version android devices.
However, we still have a way to fix it. Use su permissions and dd command to export those partitions which you want to modify (for example: system, product, vendor, and oem, but oem special), unpack and then repack, at last reboot you devices into fastbootd mode and flash back those partitions into you devices. reboot, now, you can R/W those partitions .
if you need to edit oem partition. You need edit a file in vendor partition firstly. Export and unpacking vendor partition. Finding a file which called "fstab.qcom". Open it and delect（,avb_keys=/product/etc/security/avb/oem.avbpubkey）code inside. Repacking and flash into you devices again. After this, the repackaged oem partition can be mounted correctly by flashing it again otherwise the oem partition can not be mounted (no files inside).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

SirisRui said:
Well, i guess that i can reply your question. It seems that we can't mount R/W due to Google's use of dynamic partitions for new version android devices.
However, we still have a way to fix it. Use su permissions and dd command to export those partitions which you want to modify (for example: system, product, vendor, and oem, but oem special), unpack and then repack, at last reboot you devices into fastbootd mode and flash back those partitions into you devices. reboot, now, you can R/W those partitions .
if you need to edit oem partition. You need edit a file in vendor partition firstly. Export and unpacking vendor partition. Finding a file which called "fstab.qcom". Open it and delect（,avb_keys=/product/etc/security/avb/oem.avbpubkey）code inside. Repacking and flash into you devices again. After this, the repackaged oem partition can be mounted correctly by flashing it again otherwise the oem partition can not be mounted (no files inside).
View attachment 5577955
Click to expand...
Click to collapse
Wow very complex but thank you for explain!