Hi,
Apologies if this has been answered before elsewhere.
I have been trying to use Atools to install Android on a HTC Pola100 (Touchcruise) PDA using options HARET & FROYO with system.img and data.img files in order to protect other content on my SD card.
The help page was quite informative except for where to obtain compatible haret.exe and androidinstall.tar files but I found ones on the internet dated 28/01/2010 and 24/4/2010 respectively.
The install process starts running (has a penguin image if that helps), but produces dozens of messages (which scroll off the screen too quickly to read and I haven't found a log file) before finally hanging.
The final messages are:
/init: line 334 :mount_opt: not found
sh: 2: unknown operand
found boot parameter for system
system on sd partition
e2fsck 1.38 (30-JUN-2005)
e2fsck: while determining whether /dev/block/mmcblk0p2 is mounted
e2fsck: while trying to open /dev/block/mmcblk0p2
possibly non-existent or swap device?
e2fsck: mount: mounting /dev/block/mmcblk0p2 on /system failed. no such device or address
failed to mount/system
I thought it might be a problem with my SD card, so I reformatted it and tried again with the same result.
Also tried the partitioned install, but it failed to create the partitions.
have now found an alternative install process that works
alternative
hi,
i am trying to install an android version on my htc touch cruise
i am getting the same results
i tried the froyo install from :
http://forum.xda-developers.com/archive/index.php/t-1055266.html
what alternative did you use ?
change rom
what do you mean by 'change rom' ?
i would like to install android (any version) on my htc touch cruise with the hardware as it has right now
Hello Community!
I've lurked on these forums for what seems like forever, I remember when only about 6 phones were actually supported here, but I've barely ever posted before because I've always found the answers I needed kicking about somewhere.
This time I can't.
I have an old Pola200 that I am giving to my poorly wife largely as a media player, and I'd like to put Android on it, to give her a taste of the excellent OS I use on my own HD2 (Leo) in preparation for eventually upgrading her aging Symbian based phone. She's a total technophobe, so giving her an OS that does not work will put her off the idea in the future.
I've searched these forums thoroughly, and there is a lot of builds that work fine on the Pola100, and the larger posts that try to collect all functioning builds together get a little confused by folks asking unrelated questions, and others not actually reporting whether their phone is Pola100 or Pola200.
All I am after is a simple build, either method, NAND or Haret that works fully on the Pola200 that I have. I'd prefer Haret because there is a piece of winMobile software she's fond of, but I can talk her into using an android version if it's neccessary.
Please can someone simply point me to a fully functional build for the Pola200?
Come on folks, even a simple "No" would help over 100 views of this post and no replies at all? Please?
Nobody there?
NAND (Best speed) setup:
For your android distro I recommend Fresh Froyo on NAND. You can get it below.http://sourceforge.net/projects/androidhtc/files/2011-1-23-froyo/
For your NBH, I recommend DZO's latset nbh. Pick a polaimg one. On Pola200 Panel 2 or 3 should work fine (if not you can try panel 1), and use a 240x320 one for Fresh Froyo. You can get the NBH below.
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
And please check this thread if your Wi-Fi isn't working after install. It is below.
http://forum.xda-developers.com/showthread.php?t=820683
If you ABSOLUTELY need a haret setup, ask me and I'll upload a custom-made set. I hope you find this information useful.
so this Android NAND will work with XDA orbit 2 as it's Pola 200.
quick question are all these supported with this release
- 3g Sim card (3UK network) supported with this.
-camera.
- GPS
- wireless
- bluetooth
Apppreciate your help.
tri
pl0ppy you are awesome, thanks very much. I'll check and see if this works as soon as I can (computer and health troubles to get sorted first).
I'll let you know if I really need the custom setup, but if android works reliably and well on the phone, I can see me being ble to convert her totally away from winmob and on to Android.
Thanks again for the help, once again XDA Devs community Rocks!
=pl0ppy
Click to expand...
Click to collapse
Code:
usb_function_register() 'adb'
thats all =((
but i see the tux =))
i've O2 Orbit 2
what can i do?
bootlog.txt
Code:
** /dev/block/mmcblk0
** Phase 1 - Read and Compare FATs
Attempting to allocate 3773 KB for FAT
Attempting to allocate 3773 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
Next free cluster in FSInfo block (14526) not free
Fix? yes
8 files, 3805060 free (951265 clusters)
sh: 0: unknown operand
mount: mounting /dev/block/mtdblock2 on /system failed: Invalid argument
mount: mounting /dev/block/mtdblock3 on /data failed: Invalid argument
mount: mounting /data/tmpcache on /cache failed: Invalid argument
mount: mounting /data/shared_prefs on /shared_prefs failed: Invalid argument
mount: mounting /data/tmpcache on /tmp failed: Invalid argument
mount: mounting /data/sysfiles/su on /system/bin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /system/xbin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /bin/su failed: Invalid argument
mount: mounting /data/sysfiles on /system/etc/ppp failed: No such file or directory
mount: mounting /data/sysfiles on /smodem failed: Invalid argument
I change the display on my O2 =((((((( that is a problem????
install-seq.sh & radio
pl0ppy said:
NAND (Best speed) setup:
For your android distro I recommend Fresh Froyo on NAND. You can get it below.http://sourceforge.net/projects/androidhtc/files/2011-1-23-froyo/
For your NBH, I recommend DZO's latset nbh. Pick a polaimg one. On Pola200 Panel 2 or 3 should work fine (if not you can try panel 1), and use a 240x320 one for Fresh Froyo. You can get the NBH below.
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
And please check this thread if your Wi-Fi isn't working after install. It is below.
http://forum.xda-developers.com/showthread.php?t=820683
If you ABSOLUTELY need a haret setup, ask me and I'll upload a custom-made set. I hope you find this information useful.
Click to expand...
Click to collapse
and which install-seq.sh file should i use. where do i get it from
also which radio should i use?
Hi guys,
Yesterday, I just flashed the rom KatKiss-4.2.2_226.zip to my TF101. Everthing is working fine but I can't mount CIFS share like a local file system. First of all I was formating /system before flashing the rom and the gapps and after I made a Wipe cache/Dalvik... I think it's the usually way... Right? OK. The device work properly.
My next step was try to mount a CIFS share from my NAS. I want to mount something like //192.168.1.45/media to /sdcard/media in the local storage. Before to try in androd I tried it in Ubuntu and works with the user "guest" in read only:
# mount -t cifs //192.168.1.45/media /tmp/a -o username=guest
When I tried to do it in Andorid I found several errors. At the begin I was thinking in the cifs.ko/md4.ko and nsl_utf8.ko modules but I readed that the ROM have it in the kernel. Not like a module. When I try in the Android's command line I get error like "Key has Expired". I found that this error is allied by the multiuser feature of Android 4.2 and CIFS. Something about the user spaces in the storage.
And now the question: Is it a problem with the modules or a problem with the mounting of CIFS shares in Android 4.2?
Thanks in advances!!
Regards
abocaman said:
Hi guys,
Yesterday, I just flashed the rom KatKiss-4.2.2_226.zip to my TF101. Everthing is working fine but I can't mount CIFS share like a local file system. First of all I was formating /system before flashing the rom and the gapps and after I made a Wipe cache/Dalvik... I think it's the usually way... Right? OK. The device work properly.
My next step was try to mount a CIFS share from my NAS. I want to mount something like //192.168.1.45/media to /sdcard/media in the local storage. Before to try in androd I tried it in Ubuntu and works with the user "guest" in read only:
# mount -t cifs //192.168.1.45/media /tmp/a -o username=guest
When I tried to do it in Andorid I found several errors. At the begin I was thinking in the cifs.ko/md4.ko and nsl_utf8.ko modules but I readed that the ROM have it in the kernel. Not like a module. When I try in the Android's command line I get error like "Key has Expired". I found that this error is allied by the multiuser feature of Android 4.2 and CIFS. Something about the user spaces in the storage.
And now the question: Is it a problem with the modules or a problem with the mounting of CIFS shares in Android 4.2?
Thanks in advances!!
Regards
Click to expand...
Click to collapse
You need to mount it outside of /storage/* or /mnt/shell/*
timduru said:
You need to mount it outside of /storage/* or /mnt/shell/*
Click to expand...
Click to collapse
Hi timduru,
thanks for your cooked rom!! Is really brilliant!! Keep the good work. And thanks for the solution. Just now I'm trying and the cifs mount work very good. My fault was to try to mount the folder in the path. For exemple:
busybox mount -t cifs //192.168.1.69/media/Comics /storage/sdcard0/Comics -o username="user",pass="your password" <-- Not work
busybox mount -t cifs //192.168.1.69/media /data/media -o username="user",pass="your password" <-- Work
And then try in cifs manager and work perfectly!! Always mounting the share without folders in the path, and mounting it in the /data as a destination.
Thank you very much!!:good::good::good::laugh:
My primary goal was to build exfat and ntfs-3g for x86, for my Lenovo Yoga Tablet 2 830L, but I've resulted with a project that can be built for any platform, using only Android NDK, even under Windows/Cygwin. Also I've ended up with a mount script, which was not a trivial task. I thought it might be useful for other devices, or other developers. The project is here:
https://github.com/Lurker00/Android-fs
The pre-built binaries for ARM and x86, along with a mounting script, are here:
https://github.com/Lurker00/Android-fs/releases
So, if your device is running Android KitKat, it misses exFAT and/or NTFS support, and you have rooted it, you may try... I said, KitKat, because I have no idea how these things are working in Lollipop and later, and I don't believe there is any interest in earlier versions.
If you have any suggestions on how it can be improved, you are much appreciated
Very nice, I'll try with Lollipop and get back to you.
I've created a CWM/TWRP installation zip, with pre-built binaries for most of platforms, including 64-bit. It is also there:
https://github.com/Lurker00/Android-fs/releases
It still requires root and SuperSU already installed.
I've updated the drivers to version 1.0.2:
1. One more supolicy rule added to the mounting script. Without it, unmount from Android Settings didn't work.
I didn't put per-platform binaries this time, because the recovery zip contains them all.
I'm sorry for so frequent updates, but
exFAT/NTFS fuse drivers binaries for Android v1.0.3
The problem is that the original exFAT driver was designed to update the file system only at unmount events, but the current Android never unmounts microSD mounted not by Android's vold process Meaning, file system corruption may happen on a reboot or power off.
Version 1.0.2 partially addresses that issue, and is stable enough. Only freshly created directories can be damaged by a reboot, and only if there were no any file operations after that, i.e. a rare case. Version 1.0.3 ensures that the file system is kept consistent almost always. It can be damaged only by removing microSD card during write operation.
Nevertheless, I plan to make at least one more release, to keep microSD clean, when there are no pending writes. Also, I'd try to improve the write performance compared to 1.0.3, without a penalty of the file system consistency.
I just have released
exFAT/NTFS fuse drivers binaries for Android v1.0.4
and I can say I'm quite satisfied with both performance and robustness of the resulting exFAT driver (no changes were made to ntfs-3g). So, I believe, it is the final build for a while.
Lurker0 said:
I just have released
exFAT/NTFS fuse drivers binaries for Android v1.0.4
and I can say I'm quite satisfied with both performance and robustness of the resulting exFAT driver (no changes were made to ntfs-3g). So, I believe, it is the final build for a while.
Click to expand...
Click to collapse
When I mount an external with exfat I get "Permission denied" for any writing op...it's totally r/o. Running as root
Code:
mount.exfat -o rw,umask=000 /dev/block/sda1 /system/test
Thanks for any help...currently stumped.
Do you try to write also as root? If you don't, the reason can be CELinux restrictions.
setenforce 0 fixed me up. Thanks for the reply!
(and for the binaries)
Work
Hi,
I'm trying to use your drivers on my Chuwi Vi8 Intel based tablet but i have an error message in the log :
Error: SECONDARY_STORAGE is not set. Don\'t know where to mount!
I tried to take a look at the shell script but my memory is too confused about sh to understand what is done.
Can you help me to fix this ?
I installed your drivers using the zip file and modified the logfile variable to enable log.
PrinceGITS said:
Hi,
I'm trying to use your drivers on my Chuwi Vi8 Intel based tablet but i have an error message in the log :
Error: SECONDARY_STORAGE is not set. Don\'t know where to mount!
I tried to take a look at the shell script but my memory is too confused about sh to understand what is done.
Can you help me to fix this ?
I installed your drivers using the zip file and modified the logfile variable to enable log.
Click to expand...
Click to collapse
Hello,
I have the same problem here, and the same kind of device. Can I set the path manually, instead of using the environment variable?
asteck said:
I have the same problem here, and the same kind of device. Can I set the path manually, instead of using the environment variable?
Click to expand...
Click to collapse
Of course, you can!
asteck said:
Hello,
I have the same problem here, and the same kind of device. Can I set the path manually, instead of using the environment variable?
Click to expand...
Click to collapse
Hey there, meanwhile I had some time, and figured it out. I can give the path manually in the script. I modified it that if it not find the system variable SECONDARY_STORAGE, then it uses the path what Chuwi Vi8 use(/storage/sdcard1), and it is working with my Chuwi Vi8!
I attached the modified script.
!!!USE IT ONLY WITH CHUWI Vi8 dual boot windows8.1/android4.4!!!
Lurker0 said:
Of course, you can!
Click to expand...
Click to collapse
And ready!
Thank you very much for your work!
asteck said:
Hey there, meanwhile I had some time, and figured it out. I can give the path manually in the script. I modified it that if it not find the system variable SECONDARY_STORAGE, then it uses the path what Chuwi Vi8 use(/storage/sdcard1), and it is working with my Chuwi Vi8!
I attached the modified script.
!!!USE IT ONLY WITH CHUWI Vi8 dual boot windows8.1/android4.4!!!
Click to expand...
Click to collapse
Thanks ! :highfive:
I didn't had time to check this thread since last year ( ).
I'll update with your shell script this evening.
Thanks again for your help.
And thanks Luker0 for your driver.
It will ease the use of my SDcard between Android and Windows.
PrinceGITS said:
Thanks ! :highfive:
I didn't had time to check this thread since last year ( ).
I'll update with your shell script this evening.
Thanks again for your help.
And thanks Luker0 for your driver.
It will ease the use of my SDcard between Android and Windows.
Click to expand...
Click to collapse
But keep in mind, sdCard handling is not perfect in Chuwi Vi8. When you switch from android to windows, somehow the android keeps the sd-reader locked. That is why you can't use it in windows. If you make a turn off-turn on (not simple restart) in windows, then you can use the sdcard again. From windows to android it works perfectly, only from android to windows is problematic.
Sorry for the slight off topic in this thread, this is the chuwi vi8 thread:
http://forum.xda-developers.com/android/general/chuwi-vi8-review-cheap-z3735f-8-tablet-t3066807
asteck said:
But keep in mind, sdCard handling is not perfect in Chuwi Vi8. When you switch from android to windows, somehow the android keeps the sd-reader locked. That is why you can't use it in windows. If you make a turn off-turn on (not simple restart) in windows, then you can use the sdcard again. From windows to android it works perfectly, only from android to windows is problematic.
Sorry for the slight off topic in this thread, this is the chuwi vi8 thread:
http://forum.xda-developers.com/android/general/chuwi-vi8-review-cheap-z3735f-8-tablet-t3066807
Click to expand...
Click to collapse
I know this problem and had it several times.
I think I'll unmount the SDcard in Android before switching to Windows.
I tried last evening but it didn't work.
asteck, I looked at your script and I have a question.
Why do you add the variable in the "if...then" ?
Code:
if [ x$SECONDARY_STORAGE == x ]; then
echo "Error: SECONDARY_STORAGE is not set. Don\'t know where to mount!" >> $logfile
#exit 1
secstor=/storage/sdcard1
fi
I think this can be done outside the condition.
I didn't haave enough time to make some checks, I'll try to execute the script from a terminal with echo messages to understand where it doesn't work.
PrinceGITS said:
I tried last evening but it didn't work.
asteck, I looked at your script and I have a question.
Why do you add the variable in the "if...then" ?
Code:
if [ x$SECONDARY_STORAGE == x ]; then
echo "Error: SECONDARY_STORAGE is not set. Don\'t know where to mount!" >> $logfile
#exit 1
secstor=/storage/sdcard1
fi
I think this can be done outside the condition.
I didn't haave enough time to make some checks, I'll try to execute the script from a terminal with echo messages to understand where it doesn't work.
Click to expand...
Click to collapse
Yes, you can put it outside. My mistake. I think I put it there to execute only if there is no SECONDARY_STORAGE system variable, but if there is one, then it is fails now, because the variable don't get a value. It was a quick resolution for the exact problem.
However, to solve you problem maybe you should just change the path "/storage/sdcard1". You can check the right path by putting a FAT32 sdcard in it, and see where it mounts in a file explorer. My Chuwi Vi8 mounts to here, that is why I use this path.
I attached again with an else statement for use SECONDARY_STORAGE if exist, and the log is turned off.
Hello Everyone!
I'm trying to develop for the Microsoft Surface Duo. I feel this device has the potential to run other operating systems (like Ubuntu, different versions of Android, Windows, etc.) as the kernel source was released. I've ran into two problems: creating a device tree for the Surface Duo and unzipping the system image. First, the device tree for OS builds was not released. Second, the system image is formatted as an EXT2 file, NOT an EXT4 file, and not as an Android system file that sim2img desires.
I found the system image through two methods:
Finding the payload.bin OTA file and extracting the images there.
Rooting the phone, copying the super.img, and extracting the images.
In both situations running file system.img gives me
Code:
Linux rev 1.0 ext2 filesystem data, UUID=3dc9e73d-c9c2-5764-89e7-0426672bbdb9 (extents) (64bit) (large files) (huge files)
This is for both A and B Partitions. I can't mount ext2 images onto my linux OS (I'm on Kali OS) via mount loop.
Code:
wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
If anyone can give me some insight on what the problem could be, that would be great!