Database Users

Titan nand android

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).

xperea S firmware, for fun and research

http://www.mediafire.com/?j0anq7kfe...ajlhunt3jras6,c92jlnxd3vdngn8,i6hqic38gc4h68d
system is ext4 image, can be mounted with mount -o loop in linux or by utilizing latest version of ext3 driver ( 0.51 ) for windows.

Can me give someone the WLAN widget with the GPS think in?
Gesendet von meinem R800i

is it the system dump from xperia s...?????

is it dump? real one?
Sent from my X10i using XDA App

works on xperia arc s ?

download, extract, sin2img, mount, get files
Sent from my X10i using XDA App

how you get this ...??????

can someone help me with this Im stuck on mounting the annoying img file

tatit1011 said:
can someone help me with this Im stuck on mounting the annoying img file
Click to expand...
Click to collapse
you can unpack it without mounting, by using unyaffs : http://code.google.com/p/unyaffs/

It says broken image file, can someone upload the xperia S system folder? Thanks

can you provide the binaries you are using to unpack this ?
1- extrating with 7zip : Ok, there are 3 .sin files
2- sin2img I already had : Crash
3- I tried an other version : Ok ... but the .img file size is exactly the same as the .sin ...
4- unyaffs : Crash !
So I think I don't have the good binaries ...
Thanks

sambastrakan said:
can you provide the binaries you are using to unpack this ?
1- extrating with 7zip : Ok, there are 3 .sin files
2- sin2img I already had : Crash
3- I tried an other version : Ok ... but the .img file size is exactly the same as the .sin ...
4- unyaffs : Crash !
So I think I don't have the good binaries ...
Thanks
Click to expand...
Click to collapse
THIS IS NOT YAFFS THIS IS EXT4
JUST MOUNT THE IMG IN LINUX AS EXT 4
(i hav not.done myself, I'm jus saying)
Sent from my X10i using XDA App

I also tried to mount the .img in DiskInternals Linux Reader without success. Until today it was working for any image available in xda-dev... so I think there is something special with these images ...
I will try directly in Linux to see ...
thx.

I can confirm it's not working.
Latest sin2img version gives a FileStream.Seek ArgumentException "Attempted seeking before the beginning of the stream.".
An older version creates an img file the same size as the sin, but unyaffs crashes with a segmentation fault / core dump and:
[email protected]:~$ dmesg | tail
[44637.019046] unyaffs[18031]: segfault at 1adb2b2c0 ip 0000000000400a08 sp 00007fffba023ca0 error 4 in unyaffs[400000+1000]
Click to expand...
Click to collapse
No mounting either, 'cause:
[email protected]:~$ sudo mount -t ext4 -o loop system.img /mnt/mountpoint/
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
[email protected]:~$ dmesg | tail
[44678.194165] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
Click to expand...
Click to collapse
So, wasted time, I guess...

zdzihu has some tool to extract the package try that one. I think it's called auip.exe

ShyamSasi said:
zdzihu has some tool to extract the package try that one. I think it's called auip.exe
Click to expand...
Click to collapse
Thanks, but no luck with that one either. It keeps telling me the page size is wrong (tried with all three options)
Code:
[email protected]:~$ ./aIUP
aZuZu - Direct SIN / YAFFS Image Unpacker, v1.03.5. (c) aZuZu. 2011.
usage adiup [System.Img OR System.Sin] [Page Size] [Directory]
page size is one of 2048, 4096, 8192. - Sorry to lazy to encode auto detect. ;)
Tip: Directory - directory will be created if doesn't exist.
Supported: SE System.SIN files & Android System.IMG files.
[email protected]:~$ ./aIUP system.sin 4096 test/
UnPacking system.sin to test/ ...
Error: Page size parameter is wrong.
done.
[email protected]:~$ ./aIUP system.sin 2048 test/
UnPacking system.sin to test/ ...
Error: Page size parameter is wrong.
done.
[email protected]:~$ ./aIUP system.sin 8192 test/
UnPacking system.sin to test/ ...
Error: Page size parameter is wrong.
done.
Same for the .img file.

crimilde said:
Thanks, but no luck with that one either. It keeps telling me the page size is wrong (tried with all three options)
Code:
[email protected]:~$ ./aIUP
aZuZu - Direct SIN / YAFFS Image Unpacker, v1.03.5. (c) aZuZu. 2011.
usage adiup [System.Img OR System.Sin] [Page Size] [Directory]
page size is one of 2048, 4096, 8192. - Sorry to lazy to encode auto detect. ;)
Tip: Directory - directory will be created if doesn't exist.
Supported: SE System.SIN files & Android System.IMG files.
[email protected]:~$ ./aIUP system.sin 4096 test/
UnPacking system.sin to test/ ...
Error: Page size parameter is wrong.
done.
[email protected]:~$ ./aIUP system.sin 2048 test/
UnPacking system.sin to test/ ...
Error: Page size parameter is wrong.
done.
[email protected]:~$ ./aIUP system.sin 8192 test/
UnPacking system.sin to test/ ...
Error: Page size parameter is wrong.
done.
Same for the .img file.
Click to expand...
Click to collapse
What is your page files size? Those 3 are just examples. You need to find the page file of your PC.

ShyamSasi said:
What is your page files size? Those 3 are just examples. You need to find the page file of your PC.
Click to expand...
Click to collapse
Ah ok, sorry.
It's :
[email protected]:~$ getconf PAGESIZE
4096
Click to expand...
Click to collapse
Which I had already tried.

crimilde said:
Ah ok, sorry.
It's :
Which I had already tried.
Click to expand...
Click to collapse
I'll download it and try it today.

ShyamSasi said:
I'll download it and try it today.
Click to expand...
Click to collapse
yap please sone one fine a way to unpack it .......... ????
i am waiting too for it

Unsuccessfull root on lg g2 f320k20f

Hi,
2nd time trying to root but still some message about can't reate, start and failed to copy. Full results below also. I've use the files and methods heree:
http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
http://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=45693809&nocache=1
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
++++++++++++++++++++++++++++++++++++++++FULL RESULT START+++++++++++++++++++++++++++
======adbd is already running as root
uid=0(root) gid=0(root) context=u:r:shell:s0
If you do NOT see uid=0(root) gid=0(root) above then
it is likely your device firmware is not supported or
USB mode was not toggled properly. You can try to
run the script again.
Press CTRL+c to stop this script...
If you DO see uid=0(root) gid=0(root) mentioned above...
CONGRATS.. Rooted ADB is now confirmed.
You will have a rooted ADB shell but no apps on the
phone will
'be' is not recognized as an internal or external command,
operable program or batch file.
PRESS ENTER to continue with full root.
PLEASE NOTE!
Continuing with full root can trip LG's rootchecker.
This means your phone will show ROOTED in Download mode.
You can remove root flag by flashing stock firmware...
.bin .tot or .kdz
If you do not want to possibly invalidate your warranty
press CTRL+c to stop this script...
*******************************************************
Press any key to continue . . .
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
***************************************************
***************************************************
EFS partitions now in ioroot folder on computer...
They are named modemst1.img and modemst2.img
They will come in handy in case of an emergency.
Store them somewhere you won't lose them.
IOroot is now complete.
***************************************************
***************************************************
Press any key to continue . . .
++++++++++++++++++++++FULL RESULT END++++++++++++++++++++

Same problem here, no solution yet.

LG G2 root
Hello guys,
is there any solution for this? I have same issue
Thank you

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

[Q] TWRP flashable ZIP for VS980 failed to flash under TWRP

This seems to be an old problem.
My VS980 is on TWRP v2.8.0.1, and I see there is a newer TWRP from the official site: openrecovery-twrp-2.8.1.0-vs980.zip
So I downloaded that and put it on sdcard, by "installing" this zip, the error was as follows:
Code:
Installing '/usb_otg/ROM/openrecovery-twrp-2.8.1.0-vs980.zip'...
Checking for MD5 file...
MD5 matched
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
*******************************
* TWRP Recovery by Dees_Troy *
*******************************
minzip: Extracted file "/tmp/loki.sh"
minzip: Extracted file "/tmp/loki/loki_flash"
minzip: Extracted file "/tmp/loki/loki_patch"
about to run program [/tmp/loki.sh] with 1 args
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.033627 seconds, 29.7MB/s
[+] loki_patch v2.1
[-] Unsupported aboot image.
run_program: child exited with status 1
script aborted: assert failed: run_program("/tmp/loki.sh") == 0
assert failed: run_program("/tmp/loki.sh") == 0
Is it because my aboot is already lokified? Or am I doing the upgrade wrong?