Titan nand android - Mogul, XV6800 General

can i use this method for vogue, instead for Titan
http://forum.xda-developers.com/showthread.php?t=593786

No it is made for the vogue not out titan. You would probably brick your phone.

unfortunately, the nbh rom is meant for the vogue only. i have been looking around to see if anyone has a working version for the titan, but it seems to require a slight modification to the kernel and a different bootloader. neither of these i have any idea on how to begin to do. the kaiser folks might have something going for them.. there doesnt seem to be much action here though.
edit: after looking through dzo's posts, i have hope that it may be done in the future as he has mentioned developing a method for polaris and kaiser after perfecting the vogue. however, the hardware itintializations on the vogue are proving more difficult and i am sure that will be even harder when trying to adapt the kernel for different phones.

Yes the kernel is the issue. I have a fair amount of experience with WM nand and nbh files and was able to fix the .nbh from the other thread to flash to a titan. Android even boots in the background and creates a log file of the boot process but too much of the hardware (including the screen I assume) is different and the screen never comes on and recovery mode does not work.
I have no idea of how to get the kernel and fix it to make this work and don't have the time to figure it out. It works off of SD with Haret because the default.txt file makes the right kernel arguments for the hardware and the hardware is initialized in WM before booting linux.
Each time I have tried it though I can just re-flash the phone with a WM rom and I'm back to normal. The hardspl makes it pretty hard to brick this phone.

jeffgarret said:
Yes the kernel is the issue. I have a fair amount of experience with WM nand and nbh files and was able to fix the .nbh from the other thread to flash to a titan. Android even boots in the background and creates a log file of the boot process but too much of the hardware (including the screen I assume) is different and the screen never comes on and recovery mode does not work.
Click to expand...
Click to collapse
i saw that and was wondering if you wouldnt mind explaining how you did it or post your modified nbh with the understanding that it is not actually working in its current state.

can u use the kaiser nand file on the titan

I have the ION version running very well on my mogul off SD and Haret. The performance and force closes would improve if run from nand I think. I will gladly assist in the development of a flashable Android ROM.
Any experts available to lead the way?

2 for testing
I got two mogul's that can go up for testing. let me know.

i tried the Vogue nbh, and it gets to 33% and then resets the phone saying that it is not compatible. I have also put the Ion Android 1.5 build on my phone it works very well. I hope someone can post a titan nbh soon.

http://forum.xda-developers.com/showpost.php?p=5875083&postcount=572

so close yet so far, i got android to install on the titan through harret using mym's warm donut nomorootfs, a custom default.txt and Magister2k7's zimage. got through the install perfectly, even said "android installed" but when it tryed to start... got a error... waited 20 minutes to see if it would boot and nothing at all, im going to try it one more time and this time post the exact error, will edit the post when im done, hopefully i can get it working, if and when i do i will upload a copy of the exact files i used for easy acess for all you who want android on your titan.
EDIT: here we go, the boot log. if you cant tell by looking at this, its having trouble mounting the system and data images. oh well, closer then i have ever been before. and i will keep trying different methods til i succeed.
Code:
** /dev/block/mmcblk0p1
** Phase 1 - Read and Compare FATs
Attempting to allocate 121 KB for FAT
Attempting to allocate 121 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
/data.img has too many clusters allocated
Drop superfluous clusters? yes
** Phase 4 - Checking for Lost Files
Update FATs? yes
Attempting to allocate 121 KB for FAT
215 files, 1233184 free (38537 clusters)
***** FILE SYSTEM WAS MODIFIED *****
Formatting...
256+0 records in
256+0 records out
mke2fs 1.38 (30-Jun-2005)
mke2fs: cannot determine if /sdcard/andboot/system.img is mounted
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
65536 inodes, 262144 blocks
13107 blocks (5.00%) reserved for the super user
First data block=1
32 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185
Writing inode tables: 0/32 1/32 2/32 3/32 4/32 5/32 6/32 7/32 8/32 9/3210/3211/3212/3213/3214/3215/3216/3217/3218/3219/3220/3221/3222/3223/3224/3225/3226/3227/3228/3229/3230/3231/32done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 29 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
256+0 records in
256+0 records out
mke2fs 1.38 (30-Jun-2005)
mke2fs: cannot determine if /sdcard/andboot/data.img is mounted
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
65536 inodes, 262144 blocks
13107 blocks (5.00%) reserved for the super user
First data block=1
32 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185
Writing inode tables: 0/32 1/32 2/32 3/32 4/32 5/32 6/32 7/32 8/32 9/3210/3211/3212/3213/3214/3215/3216/3217/3218/3219/3220/3221/3222/3223/3224/3225/3226/3227/3228/3229/3230/3231/32done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 23 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
Installing...
Android Installed
Fixing Permissions on files
chown: /data/app_s: No such file or directory
chmod: /data/app_s: No such file or directory
chown: /system/bin: No such file or directory
chmod: /system/bin: No such file or directory
chown: /system/xbin: No such file or directory
chmod: /system/xbin: No such file or directory
chown: /system/bin/netcfg: No such file or directory
chmod: /system/bin/netcfg: No such file or directory
chown: /system/bin/ping: No such file or directory
chmod: /system/bin/ping: No such file or directory
chown: /system/bin/pppd: No such file or directory
chmod: /system/bin/pppd: No such file or directory
chown: /system/etc/bluez: No such file or directory
chmod: /system/etc/bluez: No such file or directory
chown: /system/etc/ppp: No such file or directory
chmod: /system/etc/ppp: No such file or directory
chown: /system/etc/bluez: No such file or directory
chmod: /system/etc/bluez: No such file or directory
chown: /system/etc/dbus.conf: No such file or directory
chmod: /system/etc/dbus.conf: No such file or directory
chown: /system/etc/dhcpcd/dhcpcd-run-hooks: No such file or directory
chmod: /system/etc/dhcpcd/dhcpcd-run-hooks: No such file or directory
chown: /system/bin/su: No such file or directory
chmod: /system/bin/su: No such file or directory
chown: /system/init: No such file or directory
chmod: /system/init: No such file or directory
chown: /system/etc/init.d: No such file or directory
chmod: /system/etc/init.d: No such file or directory
grep: /system/etc/apns-conf.xml: No such file or directory
sed: /system/etc/apns-conf.xml: No such file or directory
/bin/instscripts/fixperms: line 90: can't create /system/etc/apns-conf.xml: nonexistent directory
sh: 2: unknown operand
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/loop1 is mounted
/dev/block/loop1: clean, 129/65536 files, 15800/262144 blocks
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/loop0 is mounted
/dev/block/loop0: clean, 11/65536 files, 8286/262144 blocks
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 on /system/etc/ppp failed: No such file or directory

any success?
i have USCC titan (running ppck 23569 with spl-2.40) i have ran the android 1.5 off sd-card before but i sure would like it running off the nand (and would really like wifi to work) i dont even have cell service so wifi is most important to me.
i use skype a tiny bit but mostly just surf.

@nyterage: i'm having the same issue with fixing permissions:
Fixing Permissions on files
chown: /data/app_s: No such file or directory
chmod: /data/app_s: No such file or directory
chown: /system/bin: No such file or directory
chmod: /system/bin: No such file or directory
chown: /system/xbin: No such file or directory
chmod: /system/xbin: No such file or directory
chown: /system/bin/netcfg: No such file or directory
chmod: /system/bin/netcfg: No such file or directory
chown: /system/bin/ping: No such file or directory
chmod: /system/bin/ping: No such file or directory
chown: /system/bin/pppd: No such file or directory
chmod: /system/bin/pppd: No such file or directory
chown: /system/etc/bluez: No such file or directory
chmod: /system/etc/bluez: No such file or directory
chown: /system/etc/ppp: No such file or directory
chmod: /system/etc/ppp: No such file or directory
chown: /system/etc/bluez: No such file or directory
chmod: /system/etc/bluez: No such file or directory
chown: /system/etc/dbus.conf: No such file or directory
chmod: /system/etc/dbus.conf: No such file or directory
chown: /system/etc/dhcpcd/dhcpcd-run-hooks: No such file or directory
chmod: /system/etc/dhcpcd/dhcpcd-run-hooks: No such file or directory
chown: /system/bin/su: No such file or directory
chmod: /system/bin/su: No such file or directory
chown: /system/init: No such file or directory
chmod: /system/init: No such file or directory
chown: /system/etc/init.d: No such file or directory
chmod: /system/etc/init.d: No such file or directory
Did you managed to fix the issue and figure out what caused it ?
In my case, even if I'm getting those errors while trying to "fix permissions" the android is booting up.
It's a little bit slow in my opinion but it's working(the wireless is not working and I don't know why because the guy who did it posted photos with wireless working).

Related

[q]install ubuntu or debian in legend

i tried different method but i couldn't install Ubuntu or Debian in legend.........could someone post a tutorial..............????? pls
FOLLOW ME http://smartsreenath.blogspot.com/
smartsreenath said:
i tried different method but i couldn't install Ubuntu or Debian in legend.........could someone post a tutorial..............????? pls
Click to expand...
Click to collapse
I have tried too without sucess... Would be really cool if this would work on Legend too.
How do you go about even starting?
check this sites.......
http://www.saurik.com/id/10
http://nexusonehacks.net/
i hope some one will do a nice tutorial for us...........
FOLLOW ME http://smartsreenath.blogspot.com/
Does the Legend kernel have support for loop devices?
EDIT:
Well, I pulled the config file from my legend and the dumfuq OC kernel looks like it might do, but I'm not sure if it's commented out... Also, we need the loop devices in order to mount the Ubuntu images, so if support isn't there someone is gonna have to compile a few kernels that do have it...
EDIT:
Argh!!! I can't even download the sodding files needed, my internet keeps dropping out.
Buddy
Follow the instructions here
http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-nexus-oneandroid/
I had made a little change to the bootubuntu script , to make it work for legend
Download it from here
http://10stones.com/ubuntu/bootubuntu
I had tried it on stock rom , 2.1 update 2 , with temporary root access using the Universal And Root .
make sure you ran the "sh ./ubuntu.sh" command each time you change the bootubuntu.
Since mine was a temporary root i pushed the busybox binary to /data/ using
adb push busybox /data/
download the busybox binary from here
http://10stones.com/ubuntu/busybox
** For custom roms the busybox will be installed.
If you are facing any problems reply with the output of commands.
smartvinu said:
I had made a little change to the bootubuntu script , to make it work for legend
Download it from here
http://10stones.com/ubuntu/bootubuntu
Click to expand...
Click to collapse
how i can change the script ?
with sdk and cmd ?
tnx
Something ain't working here. The script fails (see below) then I get a forced reboot...
C:\AndroidSDK\tools>adb shell
# su
su
# cd /sdcard/ubuntu
cd /sdcard/ubuntu
# sh ./ubuntu.sh
sh ./ubuntu.sh
modprobe: module 'ext2' not found
←[H←[Jmkdir failed for /data/local/mnt, File exists
←[H←[Jrm: can't remove '/system/bin/fsrw': No such file or directory
rm: can't remove '/system/bin/bootubuntu': No such file or directory
rm: can't remove '/system/bin/unionfs': No such file or directory
unknown option -- /BusyBox v1.16.2androidfull (2010-08-01 14:57:25 EDT) multi-ca
ll binary.
Usage: rm [OPTIONS] FILE...
Remove (unlink) FILEs
Options:
-i Always prompt before removing
-f Never prompt
-R,-r Recurse
cp: can't create '/system/bin/fsrw': Out of memory
cp: can't create '/system/bin/bootubuntu': Out of memory
cp: can't create '/system/bin/unionfs': Out of memory
cp: can't create '/system/bin/mountonly': Out of memory
chmod: bootubuntu: Operation not permitted
chmod: fsrw: Operation not permitted
chmod: mountonly: Operation not permitted
chmod: ubuntu.img: Operation not permitted
chmod: ubuntu.sh: Operation not permitted
chmod: unionfs: Operation not permitted
chmod: su: No such file or directory
←[H←[J
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at NexusOneHacks.net
To enter the Debian Linux console just type 'bootubuntu'
#
Click to expand...
Click to collapse
TheGrammarFreak said:
Something ain't working here. The script fails (see below) then I get a forced reboot...
Click to expand...
Click to collapse
what is the busybox version .. ?
I tried with 1.16.1
also check if you have enough phone memory
smartvinu said:
what is the busybox version .. ?
I tried with 1.16.1
also check if you have enough phone memory
Click to expand...
Click to collapse
Busybox 1.16.2
How much phone memory is enough?
I tried some more tinkering and now I just get an error about /bin/bash not existing whenever I try and run ubuntuboot...
C:\AndroidSDK\tools>adb shell
# su
su
# cd /sdcard/ubuntu
cd /sdcard/ubuntu
# sh ./ubuntu.sh
sh ./ubuntu.sh
modprobe: module 'ext2' not found
←[H←[Jmkdir failed for /data/local/mnt, File exists
←[H←[Junknown option -- /BusyBox v1.16.2androidfull (2010-08-01 14:57:25 EDT) mu
lti-call binary.
Usage: rm [OPTIONS] FILE...
Remove (unlink) FILEs
Options:
-i Always prompt before removing
-f Never prompt
-R,-r Recurse
chmod: bootubuntu: Operation not permitted
chmod: fsrw: Operation not permitted
chmod: mountonly: Operation not permitted
chmod: ubuntu.img: Operation not permitted
chmod: ubuntu.sh: Operation not permitted
chmod: unionfs: Operation not permitted
chmod: su: No such file or directory
←[H←[J
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at NexusOneHacks.net
To enter the Debian Linux console just type 'bootubuntu'
# bootubuntu
bootubuntu
mount: can't setup loop device: No such file or directory
mount: mounting devpts on /data/local/ubuntu/dev/pts failed: No such file or dir
ectory
mount: mounting proc on /data/local/ubuntu/proc failed: No such file or director
y
mount: mounting sysfs on /data/local/ubuntu/sys failed: No such file or director
y
net.ipv4.ip_forward = 1
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexist
ent
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexist
ent
Setting localhost on /etc/hosts
bootubuntu: cannot create /data/local/ubuntu/etc/hosts: directory nonexistent
READY TO ROCK AND ROLL BABY!
Brought to you by NexusOneHacks.net and the open source community!
chroot: can't execute '/bin/bash': No such file or directory
Shutting down Ubuntu
umount: can't umount /data/local/ubuntu/dev/pts: No such file or directory
umount: can't umount /data/local/ubuntu/proc: No such file or directory
umount: can't umount /data/local/ubuntu/sys: No such file or directory
umount: can't umount /data/local/ubuntu: Invalid argument
#
Click to expand...
Click to collapse
Can u try with the busybox i uploaded
smartvinu said:
Can u try with the busybox i uploaded
Click to expand...
Click to collapse
Still no joy...
C:\AndroidSDK\tools>adb push busybox /data/
1042 KB/s (1120536 bytes in 1.050s)
C:\AndroidSDK\tools>adb shell
# su
su
# cd /sdcard/ubuntu
cd /sdcard/ubuntu
# sh ./ubuntu.sh
sh ./ubuntu.sh
modprobe: module 'ext2' not found
←[H←[Jmkdir failed for /data/local/mnt, File exists
←[H←[Junknown option -- /BusyBox v1.16.2androidfull (2010-08-01 14:57:25 EDT) mu
lti-call binary.
Usage: rm [OPTIONS] FILE...
Remove (unlink) FILEs
Options:
-i Always prompt before removing
-f Never prompt
-R,-r Recurse
chmod: bootubuntu: Operation not permitted
chmod: fsrw: Operation not permitted
chmod: mountonly: Operation not permitted
chmod: ubuntu.img: Operation not permitted
chmod: ubuntu.sh: Operation not permitted
chmod: unionfs: Operation not permitted
chmod: su: No such file or directory
←[H←[J
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at NexusOneHacks.net
To enter the Debian Linux console just type 'bootubuntu'
# bootubuntu
bootubuntu
mount: can't setup loop device: No such file or directory
mount: mounting devpts on /data/local/ubuntu/dev/pts failed: No such file or dir
ectory
mount: mounting proc on /data/local/ubuntu/proc failed: No such file or director
y
mount: mounting sysfs on /data/local/ubuntu/sys failed: No such file or director
y
net.ipv4.ip_forward = 1
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexist
ent
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexist
ent
Setting localhost on /etc/hosts
bootubuntu: cannot create /data/local/ubuntu/etc/hosts: directory nonexistent
READY TO ROCK AND ROLL BABY!
Brought to you by NexusOneHacks.net and the open source community!
chroot: can't execute '/bin/bash': No such file or directory
Shutting down Ubuntu
umount: can't umount /data/local/ubuntu/dev/pts: No such file or directory
umount: can't umount /data/local/ubuntu/proc: No such file or directory
umount: can't umount /data/local/ubuntu/sys: No such file or directory
umount: can't umount /data/local/ubuntu: Invalid argument
#
Click to expand...
Click to collapse
This clearly throws a large number of errors, I just don't know why. The first command I issue is "su"
smartvinu said:
Can u try with the busybox i uploaded
Click to expand...
Click to collapse
why don't you check it after rooting your mobile? you already posted that your phone is hafly rooted and using stock rom........why don't you move it to azure rom and post custom bootubuntu [sorry my opinion]
FOLLOW ME http://smartsreenath.blogspot.com/
here is my log just check it smartvinu
E:\sdk\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
xxxxxxxxxxxxx device
E:\sdk\tools>adb shell
# su
su
# su
su
# cd /sdcard/ubuntu
cd /sdcard/ubuntu
# sh ./ubuntu.sh
sh ./ubuntu.sh
modprobe: chdir(/lib/modules): No such file or directory
←[H←[Jrm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
mkdir failed for /data/local/mnt, File exists
←[H←[Jrm failed for -/system/bin/mountonly, No such file or directory
Unable to chmod bootubuntu: Operation not permitted
←[H←[J
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at NexusOneHacks.net
To enter the Debian Linux console just type 'bootubuntu'
# bootubuntu
bootubuntu
net.ipv4.ip_forward = 1
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
Setting localhost on /etc/hosts
READY TO ROCK AND ROLL BABY!
Brought to you by NexusOneHacks.net and the open source community!
[1] Illegal instruction chroot ${mnt} /b...
Shutting down Ubuntu
#
Click to expand...
Click to collapse
FOLLOW ME http://smartsreenath.blogspot.com/
HTC legend hvn't full R/W on system files ...
edit : sorry i'm french
smartsreenath said:
here is my log just check it smartvinu
FOLLOW ME http://smartsreenath.blogspot.com/
Click to expand...
Click to collapse
@smartsreenath
Can u check that after doing this steps the /data/local/ubuntu is mounted with the ubuntu.img
Umm, post missing??
I can run ubuntu with sucess and access it with vlc-viewer to localhost.
Do a "cat ubuntu.sh" and manually enter commands to see whish fail
and the same with bootubuntu.
Oops
I'll try again to make it work tomorrow
mmm my post was deleted ?!
I can't mount with indigo bean rom ...
But with anothersotckrom that work fine ^^

[Q] problem installing ubuntu on nook

Hi, i've followed the guide inside the nook color android development subforum but i cant make it to work...
This is what i get from adb (connected trough wifi)
Code:
# sh ./ubuntu.sh
mount: not found
modprobe: module 'ext2' not found
mkdir: can't create directory '/data/local/mnt': File exists
rm: remove '/system/bin/fsrw'? y
rm: can't remove '/system/bin/fsrw': Read-only file system
rm: remove '/system/bin/bootubuntu'? y
rm: can't remove '/system/bin/bootubuntu': Read-only file system
rm: remove '/system/bin/unionfs'? y
rm: can't remove '/system/bin/unionfs': Read-only file system
unknown option -- /BusyBox v1.16.2androidfull (2010-08-01 14:57:25 EDT) multi-call binary.
Usage: rm [OPTIONS] FILE...
Remove (unlink) FILEs
Options:
-i Always prompt before removing
-f Never prompt
-R,-r Recurse
cp: can't create '/system/bin/fsrw': File exists
cp: can't create '/system/bin/bootubuntu': File exists
cp: can't create '/system/bin/unionfs': File exists
cp: can't create '/system/bin/mountonly': File exists
chmod: *: No such file or directory
chmod: InputChannel_test: Read-only file system
chmod: InputDispatcher_test: Read-only file system
chmod: InputPublisherAndConsumer_test: Read-only file system
chmod: InputReader_test: Read-only file system
chmod: Looper_test: Read-only file system
chmod: ObbFile_test: Read-only file system
chmod: String8_test: Read-only file system
chmod: alsa_amixer: Read-only file system
chmod: alsa_aplay: Read-only file system
chmod: alsa_ctl: Read-only file system
chmod: alsa_ucm: Read-only file system
chmod: am: Read-only file system
chmod: app_process: Read-only file system
chmod: audioloop: Read-only file system
chmod: backuptool.sh: Read-only file system
chmod: bluetoothd: Read-only file system
chmod: bmgr: Read-only file system
chmod: bootanimation: Read-only file system
chmod: bootubuntu: Read-only file system
chmod: bugreport: Read-only file system
chmod: cat: Read-only file system
chmod: clear_bootcnt.sh: Read-only file system
chmod: cmp: Read-only file system
chmod: compcache: Read-only file system
chmod: dalvikvm: Read-only file system
chmod: date: Read-only file system
chmod: dbus-daemon: Read-only file system
chmod: dd: Read-only file system
chmod: debuggerd: Read-only file system
chmod: dexopt: Read-only file system
chmod: dhcpcd: Read-only file system
chmod: dmesg: Read-only file system
chmod: dnsmasq: Read-only file system
chmod: dspexec: Read-only file system
chmod: dump_image: Read-only file system
chmod: dumpstate: Read-only file system
chmod: dumpsys: Read-only file system
chmod: dvz: Read-only file system
chmod: e2fsck: Read-only file system
chmod: e2label: Read-only file system
chmod: erase_image: Read-only file system
chmod: fix_permissions: Read-only file system
chmod: flash_image: Read-only file system
chmod: fsck_msdos: Read-only file system
chmod: fsrw: Read-only file system
chmod: gdbjithelper: Read-only file system
chmod: gdbserver: Read-only file system
chmod: getevent: Read-only file system
chmod: getprop: Read-only file system
chmod: gzip: Read-only file system
chmod: handle_compcache: Read-only file system
chmod: hciattach: Read-only file system
chmod: hd: Read-only file system
chmod: id: Read-only file system
chmod: ifconfig: Read-only file system
chmod: iftop: Read-only file system
chmod: ime: Read-only file system
chmod: input: Read-only file system
chmod: insmod: Read-only file system
chmod: installd: Read-only file system
chmod: ioctl: Read-only file system
chmod: ionice: Read-only file system
chmod: iptables: Read-only file system
chmod: keystore: Read-only file system
chmod: keystore_cli: Read-only file system
chmod: kill: Read-only file system
chmod: linker: Read-only file system
chmod: log: Read-only file system
chmod: logcat: Read-only file system
chmod: logwrapper: Read-only file system
chmod: lsmod: Read-only file system
chmod: lsof: Read-only file system
chmod: mediaserver: Read-only file system
chmod: mke2fs: Read-only file system
chmod: mkyaffs2image: Read-only file system
chmod: modelid_cfg.sh: Read-only file system
chmod: monkey: Read-only file system
chmod: mountonly: Read-only file system
chmod: mtpd: Read-only file system
chmod: nandread: Read-only file system
chmod: ndc: Read-only file system
chmod: netcfg: Read-only file system
chmod: netd: Read-only file system
chmod: netstat: Read-only file system
chmod: newfs_msdos: Read-only file system
chmod: notify: Read-only file system
chmod: omx_tests: Read-only file system
chmod: pand: Read-only file system
chmod: ping: Read-only file system
chmod: pm: Read-only file system
chmod: pppd: Read-only file system
chmod: printenv: Read-only file system
chmod: ps: Read-only file system
chmod: pvrsrvinit: Read-only file system
chmod: qemu-props: Read-only file system
chmod: qemud: Read-only file system
chmod: racoon: Read-only file system
chmod: radiooptions: Read-only file system
chmod: reboot: Read-only file system
chmod: record: Read-only file system
chmod: renice: Read-only file system
chmod: resize2fs: Read-only file system
chmod: rild: Read-only file system
chmod: rmdir: Read-only file system
chmod: rmmod: Read-only file system
chmod: route: Read-only file system
chmod: rtp_test: Read-only file system
chmod: run-as: Read-only file system
chmod: schedtest: Read-only file system
chmod: schedtop: Read-only file system
chmod: sdcard: Read-only file system
chmod: sdptool: Read-only file system
chmod: sendevent: Read-only file system
chmod: service: Read-only file system
chmod: servicemanager: Read-only file system
chmod: setconsole: Read-only file system
chmod: setprop: Read-only file system
chmod: sh: Read-only file system
chmod: showlease: Read-only file system
chmod: skia_test: Read-only file system
chmod: sleep: Read-only file system
chmod: smd: Read-only file system
chmod: stagefright: Read-only file system
chmod: start: Read-only file system
chmod: stop: Read-only file system
chmod: surfaceflinger: Read-only file system
chmod: svc: Read-only file system
chmod: sync: Read-only file system
chmod: sysinit: Read-only file system
chmod: system_server: Read-only file system
chmod: tc: Read-only file system
chmod: testid3: Read-only file system
chmod: tiap_cu: Read-only file system
chmod: tiap_loader: Read-only file system
chmod: toolbox: Read-only file system
chmod: top: Read-only file system
chmod: tune2fs: Read-only file system
chmod: uim-sysfs: Read-only file system
chmod: unionfs: Read-only file system
chmod: unyaffs: Read-only file system
chmod: uptime: Read-only file system
chmod: vdc: Read-only file system
chmod: verify_cache_partition_size.sh: Read-only file system
chmod: vmstat: Read-only file system
chmod: vold: Read-only file system
chmod: watchprops: Read-only file system
chmod: wipe: Read-only file system
chmod: wlan_cu: Read-only file system
chmod: wlan_loader: Read-only file system
chmod: wpa_cli: Read-only file system
chmod: wpa_supplicant: Read-only file system
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at NexusOneHacks.net
To enter the Debian Linux console just type 'bootubuntu'
# bootbuntu
bootbuntu: not found
# whoami
root
#
As you can see i'm root , i type everything from root after su command.
I cannot get out of this...
I use the latest CM7 image with OC
No one can help me?
did you try a "adb remount" before getting into the shell?
yes! i've tried same resoult.
I tried also to install it without the script, making all the passage by hand.
For example if i try to mount the image on Sd whit mount loop /sdcard/ubuntu/ubuntu.img mount tell me that he cant fine the file
WTF
I have the same problem.
Please help.
Anybody can help?
Still need help.

[Q] Backtrack 5 on HD2 problem

Code:
localhost / # cd sd-ext
localhost sd-ext # ls
app bt5 lost+found
app-private dalvik-cache
localhost sd-ext # cd bt5
localhost bt5 # ls
bt5.img changelog.txt scripts
localhost bt5 # cd scripts
localhost scripts # ls
go l mkdirectory stop
localhost scripts # sh go
mount: mounting /dev/block/vold/179:3 on /data/bootbt failed: No such file or directory
losetup: /dev/block/loop253: No such file or directory
swapon: /dev/block/loop253: Invalid argument
losetup: /dev/block/loop254: No such file or directory
mount: mounting /data/bootbt/bt5.img on /data/runbt failed: No such file or directory
mount: mounting devpts on /data/runbt/dev/pts failed: No such file or directory
mount: mounting proc on /data/runbt/proc failed: No such file or directory
mount: mounting sysfs on /data/runbt/sys failed: No such file or directory
net.ipv4.ip_forward = 1
go: cannot create /data/runbt/etc/resolv.conf: directory nonexistent
go: cannot create /data/runbt/etc/hosts: directory nonexistent
-Backtrack Loaded-
Run Backtrack as: (select number)
1. CLI
2. VNC
2
chroot: can't change root directory to /data/runbt: No such file or directory
localhost scripts #
My android is: cyanmod 7 (TyphooN_CM7_v3.4.1-MAGLDR)
Backtrack 5 arm downloaded from: http://forum.xda-developers.com/showthread.php?p=15443300#post15443300 (V 0.2)
Please help me.
Sorry, missed this somehow :/
the mount and image points are static, i see you have them possibly in the wrong spot. the .img file needs to be on the third partition of your SDcard (the ext4 one). if you place it somewhere, you need to tell the script where to find it.
these scripts were written with static mount points, so placement of the files is crucial.

Rooting just not working

Hello,
I have tried searching these forums for an eligible solution however all my attempted search terms came back with threads that did not quite explain what i am experiencing. Or for that matter were understandable by me. So excuse me in advance if you believe this question has been answered somewhere else. Instead of expressing your rage please feel free to send me a message pointing me in the right direction.
I have tried multiple ways to obtain root access to my tablet. Sadly all of them failed.
What I understand from this is that somehow there is not enough memory on a partition in order to succeed.
Here's the conflict Does one need root access to say, enlarge or change a partition?
DooMLoRD's method seemed to get the furthest but ultimately failed.
--- checking free space on /system
19 KB/s (439 bytes in 0.021s)
df: /mnt/.lfs: Function not implemented
--- Free space on /system : 0 bytes
--- NOT enough free space on /system!!!
--- making free space by removing Google Maps
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: Read-only file system
--- correcting permissions
Unable to chmod /system/xbin/busybox: Read-only file system
--- installing busybox
[1] Segmentation fault /system/xbin/bus...
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Click to expand...
Click to collapse
GT-P1000
Firmware version 2.3.6
Baseband version P1000XXJPZ
Kernel version 2.6.35.7
GINGERBREAD.XWJQ8
you are just simply in a wrong forum....
better find your answer on Original Galaxy Tab 7.0
http://forum.xda-developers.com/forumdisplay.php?f=752
edan1979 said:
you are just simply in a wrong forum....
better find your answer on Original Galaxy Tab 7.0
http://forum.xda-developers.com/forumdisplay.php?f=752
Click to expand...
Click to collapse
Valid point, Moving thread.

Root LG G2 Korean Version

Hi I followed the method here: http://forum.xda-developers.com/showpost.php?p=48709232 and http://forum.xda-developers.com/showthread.php?p=45692679#post45692679
Unfortunately, the automatic rooting is not working, its say something see AUTOROOT MESSAGE BELOW . So I took the manual method but on Step 12:
12: adb shell "sync;mount -o remount,ro /system"
It says mount: Device or resource busy
So what should I do? Thanks
====AUTOROOT MESSAGE =======================================================================
Mounting system, pushing su binary and installing SuperSu...
2244 KB/s (1085140 bytes in 0.472s)
cp: can't create '/system/xbin/busybox': Read-only file system
failed to copy 'su' to '/system/xbin/daemonsu': Read-only file system
cp: can't stat '/system/xbin/daemonsu': No such file or directory
failed to copy 'install-recovery.sh' to '/system/etc/install-recovery.sh': Read-
only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to open /system/xbin/su: No such file or directory
Rebooting Phone.
***************************************************
***************************************************
You should hopefully now be fully rooted!!
Wait for your device to reboot and continue
with ioroot script to backup EFS...
***************************************************
***************************************************
/sdcard/modemst1.img: cannot open for write: Read-only file system
/sdcard/modemst2.img: cannot open for write: Read-only file system
remote object '/sdcard/modemst1.img' does not exist
remote object '/sdcard/modemst2.img' does not exist

Categories

Resources