Related
Hi guys, I tried ext2fs and ext2fsd to see my ext2 partition on windows but I just can't see it. I tried rebooting my phone and computer but I only see the fat32 partition.
Anybody ran into it before ?
Btw, I would like to make my own rom so does anybody have any tutorial for me ?
Tutorial like : how to include your apks and saves that titanium backup does.
Btw I would like to explore my ext partition cuz some apps give me error when updating so I want to check the remaining room.
I am also seeking for the best superuser apk at the moment. Cuz for example,what the hell do I do if I prevent an app from using root access and its an error ? I mean ok I can click on the entry on Superuser but after that Superuser didnt ask me about root access and I had to reflash the rom cuz it was unusable.
(I already tried to flash a zip containing a superuser but it gave me an error at line 7 lol ... and trying to launch the apk with astro didnt work)
Thank's guyz
btw : all my recent nandroids backup fail when restoring telling me to use adb but adb just tells me files are corupted. < dead micro sd ? :// what's your opinion is it a frequent error or anything?
Mister-Tea said:
Hi guys, I tried ext2fs and ext2fsd to see my ext2 partition on windows but I just can't see it. I tried rebooting my phone and computer but I only see the fat32 partition.
Anybody ran into it before ?
Btw, I would like to make my own rom so does anybody have any tutorial for me ?
Tutorial like : how to include your apks and saves that titanium backup does.
Btw I would like to explore my ext partition cuz some apps give me error when updating so I want to check the remaining room.
I am also seeking for the best superuser apk at the moment. Cuz for example,what the hell do I do if I prevent an app from using root access and its an error ? I mean ok I can click on the entry on Superuser but after that Superuser didnt ask me about root access and I had to reflash the rom cuz it was unusable.
(I already tried to flash a zip containing a superuser but it gave me an error at line 7 lol ... and trying to launch the apk with astro didnt work)
Thank's guyz
btw : all my recent nandroids backup fail when restoring telling me to use adb but adb just tells me files are corupted. < dead micro sd ? :// what's your opinion is it a frequent error or anything?
Click to expand...
Click to collapse
You can see your ext partitions via adb shell, i forget what the mounting command is but i believe that's the only way to see it.
for ext partition:
put your card in external card reader, then you'll be able to see all partitions.
if you're using phone to read card, it will mount only fat partition, bcoz ext is in constant usage, so you have no access to ext via windows (you can get access via adb shell)
remaining space on ext you can see for example in android explorer.
questions about cooking rom
topics with tutorials how to create own rom are somewhere on this forum, use search.
and create separate topics for each problem, post title is only about ext so probably nobody will answer rest of questions. i see that are questions absolutely independent of ext part about which is this topic.
zbaracki said:
for ext partition:
put your card in external card reader, then you'll be able to see all partitions
Click to expand...
Click to collapse
That's not true and won't work - Windows cannot natively mount linux partitions. There are some tools to allow you to access them read only but not advisable.
If you want to access the ext partition, you will need to use linux so either set up a dual boot system or use a live CD.
What I think zbaracki was getting at was that you would need to remove the card from the phone to see the partition with anything other than ADB, but even then, Windows won't see it.
HTH.
Smiffy.
You could create a Linux virtual machine using VirtualBox. That would put Windows to good use!
There are ext2 plugins for Total Commander.
Free.
Easiest solution for Windows: http://www.fs-driver.org/
Others solutions: boot a Gparted LiveCD or Install Ubuntu (dual boot if not ready to be a full linux user (don't forget your phone is running on a linux kernel ))
I have done via ADB!
At android sdk/windows/tools I have "cmd exe"
and I get this:
Code:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. Alle Rechte vorbehalten.
C:\android-sdk-windows\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
# ls -al /data
ls -al /data
drwxrwx--x 1 1000 1000 2048 May 31 07:45 .
drwxr-xr-x 14 0 0 0 May 31 10:43 ..
drwxrwxrwx 1 0 0 2048 May 31 07:45 DxDrm
drwxrwx--x 1 1000 1000 2048 May 31 07:47 anr
lrwxrwxrwx 1 0 0 14 May 31 10:21 app -> /system/sd/app
lrwxrwxrwx 1 0 0 22 May 31 10:21 app-private -> /system/s
d/app-private
drwx------ 1 1000 1000 2048 May 31 07:52 backup
drwxrwxrwx 1 1002 1002 2048 May 31 10:45 btips
drwxrwx--x 1 1000 1000 2048 May 31 09:55 dalvik-cache
drwxrwx--x 1 1000 1000 2048 May 31 07:45 data
drwxr-x--- 1 0 1007 2048 May 31 07:45 dontpanic
lrwxrwxrwx 1 0 0 11 May 31 07:45 drm -> /data/local
drwxrwx--x 1 2000 2000 2048 May 31 07:45 local
drwxrwx--- 1 0 0 2048 May 31 07:45 lost+found
drwxrwx--t 1 1000 9998 2048 May 31 07:45 misc
drwx------ 1 0 0 2048 May 31 10:45 property
-rw-rw-rw- 1 1013 1000 2 May 31 08:11 pvcodec.txt
drwxrwxr-x 1 1000 1000 2048 May 31 10:46 system
drwxr-xr-x 1 1000 1000 2048 May 31 07:54 tombstones
drwxrwxrwx 1 1018 1018 2048 May 31 07:45 wimax
# mount
mount
rootfs on / type rootfs (ro)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k)
none on /dev/cpuctl type cgroup (rw,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev)
/dev/block/mmcblk0p2 on /system/sd type ext2 (rw,noatime,nodiratime,errors=conti
nue)
/dev/block//vold/179:1 on /sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=
1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=is
o8859-1,shortname=mixed,utf8,errors=remount-ro)
# df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.6M 0 95.6M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 170.0M 149.9M 20.1M 88% /system
/dev/block/mtdblock5 165.8M 69.2M 96.6M 42% /data
/dev/block/mtdblock4 130.0M 1.1M 128.9M 1% /cache
/dev/block/mmcblk0p2 228.8M 719.0K 215.9M 0% /system/sd
/dev/block//vold/179:1
1.6G 124.0K 1.6G 0% /sdcard
#
My method:
To check whether App2SD is set up really, there are two possibilities. The first would be that you control whether the links are set correctly on the SD card. For this you start adb shell with the argument:
adb shell
And give it one in the shell:
ls-al / data
Then, the folder app, app-private (and depending on the after-A2SD also the folder version Dalvik-cache) to the SD card reference, there should therefore be read as:
app -> / system / sd / app
app-private -> / System / sd / app-private
Under certain circumstances also:
Dalvik-cache -> / system / sd / Dalvik-cache
Then Apps are stored on the SD card.
Otherwise, you can still see if enter the Ext-partition (for the apps) is properly mounted, this again in the adb shell:
Mount
Then all mounted partitions are displayed, the App2SD partition should be this:
/ Dev/block/mmcblk0p2 on / system / sd type ext2
To check how full the partition is, you give a:
df-h
Then you will see an overview, how full the partitions. The partition for App2SD you find i.d.R. here:
/dev/block/mmcblk0p2 228.8M 719.0K 215.9M 0% /system/sd
I have done these works :
1. Removed full battery notification
2. Installed supercurio kernel
3. Removed touchwiz launcher (replaced with the stock gingerbread of the nexus s 9020)
4. Removed all Samsung stuff (unuseful) except voice commands and dlna.
Now i would share this with all the comunity, but how i can do this ?
(i can't do a nandroid backup because clockworkmod isn't avaible).
Please, help me, this phone it's terrible with all samsung customization!
Im pretty sure you can create an ODIN package.
I am not sure if the partitions are the same on SGS2 (dont own one yet) but take a look at this.
icezar1 said:
Im pretty sure you can create an ODIN package.
I am not sure if the partitions are the same on SGS2 (dont own one yet) but take a look at this.
Click to expand...
Click to collapse
Ok, i'll try now to pack my first worlwide rom!
kawa636r said:
I have done these works :
1. Removed full battery notification
2. Installed supercurio kernel
3. Removed touchwiz launcher (replaced with the stock gingerbread of the nexus s 9020)
4. Removed all Samsung stuff (unuseful) except voice commands and dlna.
Now i would share this with all the comunity, but how i can do this ?
(i can't do a nandroid backup because clockworkmod isn't avaible).
Please, help me, this phone it's terrible with all samsung customization!
Click to expand...
Click to collapse
thanks man
does the removal of the samsung bloatware resolve the android os battery issue>
winwiz said:
thanks man
does the removal of the samsung bloatware resolve the android os battery issue>
Click to expand...
Click to collapse
seems to be yes, because samsung apps stay forever in background.
I'm trying to take nexus s keyboard and port to s2, but where are keyboard files located?
****URGENT****
When trying to make odin flashable image, i have this error after these commands :
# su
# mount -o remount,rw /dev/block/stl9 /system
# dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
/dev/block/stl9: cannot open for read: No such file or directory
I have followed http://forum.xda-developers.com/showthread.php?t=960946 but seems to be not good for S2. I think that /dev/memory addressing it's different.
Who can help me?
In shell type mount and see on what stl is mounted /system. I DONT OWN A SGS 2! If you don't have some basic linux knowledge and dont know how the phone works, don't do this! I'm really serious!
But if you wanna go ahead you will need to find out your mount points. Is vital!
How i can see on what stl is mounted system? there isn't an fstab file?
kawa636r said:
****URGENT****
When trying to make odin flashable image, i have this error after these commands :
# su
# mount -o remount,rw /dev/block/stl9 /system
# dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
/dev/block/stl9: cannot open for read: No such file or directory
I have followed http://forum.xda-developers.com/showthread.php?t=960946 but seems to be not good for S2. I think that /dev/memory addressing it's different.
Who can help me?
Click to expand...
Click to collapse
SGS2 has different mount points. I see mention of RFS as well, which is wrong for the SGS2...
# mount
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=7168k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
nil /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0
/dev/block/vold/179:11 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard 0 0
Somebody can help me for the commands that i must do for creating a ROM?
kawa636r said:
Somebody can help me for the commands that i must do for creating a ROM?
Click to expand...
Click to collapse
Not got an SGS 2. Also, I hate working on ROMs from a dump of the device to be perfectly frank...
pulser_g2 said:
Not got an SGS 2. Also, I hate working on ROMs from a dump of the device to be perfectly frank...
Click to expand...
Click to collapse
from my response of mount command you can't help me?
kawa636r said:
from my response of mount command you can't help me?
Click to expand...
Click to collapse
Nope, sorry. I need the device to figure it out really, as I've not worked with a Samsung before. And I don't know about repackaging a ROM into a tar for ODIN based on a dump.
I wouldn't want to try and help either, as I need the device to actually check it properly, and wouldn't want you or someone else to have to try reflashing after messing something up...
Never looked at using a dump before - I prefer to take the stock ROM and modify it on my PC tbh
pulser_g2 said:
Never looked at using a dump before - I prefer to take the stock ROM and modify it on my PC tbh
Click to expand...
Click to collapse
Yes, but stock rom come with odin files format.
If i want to cook a rom i must start from sources, from a system dump, or from a zip rom (in nexus s i remember that rom are packaged in zip)....
Me too
I have the same problem, do you have find a solution?
I don't want to ruin your mojo, the more people interested in android, the better... but I'm a bit worried if inexperienced people give other inexperienced people things to flash with Odin. Since your ROM doesn't bring anything new (all other roms have this already), why not put some more time in it, polish it a bit, and maybe you will get some original ideas to add to it, instead of rushing it like this, and possibly brick some phones?
The probleme is that i have no time to do this, i have created a system and i have modivied the cyanogenmod to work with this system, the probleme is that i should to find a better methode to install the cyanogenmod rom from a pc, it is not for me is for other simple users.
This is a think tank for making 2nd init load aosp based roms. It currently loads only init.rc. Attached below is the zip file I have made of where I currently stand with 2nd init. Please only download it if you want to help fix it. It probably doesnt work yet.
2nd init is further than the attached in this build (This is a full CM build) The script that is currently being hammered out is mot_boot_mode inside of /system/bin/ Also note that I have made the update script work in the build.
http://www.multiupload.com/4QG0NHCRG7
Hope this is what you needed:
http://www.multiupload.com/X0GM6Q60S3
Here ya go extracted boot.img from cm7-atrix nightly
rename it to .tgz as it wouldnt let me upload that lol
This is the ramdisk uncompressed did you need the kernel as well?
Nope, no need for the kernel. Checking those files now.
Edit: That was exactly what I needed, thanks!
K im asking the X and D2G devs for help with how to make it load a hijack zip rather than what it's doing. Hopefully we have this fixed soon. I know whats wrong but I just can't get it to work right. It isn't drawing the screen when I use the wrapper because it doesnt use the task sets so I am seeing if the shell script we use to execute we could make it load a hijack zip.
Good luck, this community can be secretive @ times
I suspect this thread will gradually decline like the other so i if can suggest, change the title to status update. And continue to update the top post with the newest info. And a mod might wanna move it to general but i personal think it should be here as it is an active dev project.
I think in this way maybe we can start to have a public dev conversation and perhaps pool efforts from others that have similar goals. I know of a few others that are tackling the same issues for different purposes.
Seems the ways things are set up here it discourages anything but releases in the dev section. Perhaps its time for a dev q&a forum lol ...
Allot of things make our situation unique which draws allot of blank stares in the general dev forums.
EDIT:
Yay 200th post lol
aceoyame said:
K im asking the X and D2G devs for help with how to make it load a hijack zip rather than what it's doing. Hopefully we have this fixed soon. I know whats wrong but I just can't get it to work right. It isn't drawing the screen when I use the wrapper because it doesnt use the task sets so I am seeing if the shell script we use to execute we could make it load a hijack zip.
Click to expand...
Click to collapse
Im not familiar with a hijack.zip this being my first android device.. Is it a zip to replace the contents of the init ramdisk?? If so why not just use some space in /system?
mastafunk said:
Im not familiar with a hijack.zip this being my first android device.. Is it a zip to replace the contents of the init ramdisk?? If so why not just use some space in /system?
Click to expand...
Click to collapse
As far as I know, it loads 2nd-init via exec command, which init then loads and does a hijack.killall and KILLS everything in sight, and then remounts /system as whatever it's booting so recovery would become /system. I think that's how it works? It's all so confusing to me.
aceoyame: You might benefit from getting in touch with RevNumbers, he does nightlies for the CM 4 Droid X w/ Gingerbread Kernel, so he has a lot of experience with 2nd-init and how to make it work.
0vermind said:
As far as I know, it loads 2nd-init via exec command, which init then loads and does a hijack.killall and KILLS everything in sight, and then remounts /system as whatever it's booting so recovery would become /system. I think that's how it works? It's all so confusing to me.
Click to expand...
Click to collapse
The implementations i have seen launch second init via a bash hijack or a mount script. The other stuff you describe is a function of second init, and not of any hijack.zip. From searching elsewhere it looks like a hijack.zip is a compressed filesystem for 2ndinit potentialy containing init scripts etc.. but i could be way off..
So this may be beating a dead horse but is there source for our specific 2ndinit?
The answer to why ours functions different has to be in there..
Got it. Research indicates the hijack.zip is cm teams answer to keeping the boot image seperate for device which need 2nd-init it is just the boot filesystem should be similar to the files i posted earlier except for a specific device. The Question i am asking is since 2ndinit is up why not parse those from elsewhere, the nameless series roms limited implementation threw them in /system/etc/rootfs why not pickup from there.. or are you intent with trying to make an official port? Does cm maintain the source for the 2ndinit on supported hardware? If so diffing those to the source for ours should put us in a solid direction as far as a cm port goes...
And for anyone that doesnt know where im coming from im a long time linux dev, but fairly new to android and this is my first android device so be nice
2nd init is maintained for supported devices. As for contacting revnumbers... I already was in contact with him lol. I worked with him on the D2G for a lot of things. Really our best contact would be to see if CVPCS can figure out what we need to do exactly. All we need to do is expand that task set but I myself am not sure how it works just yet. If you look in that shell script it calls on the task set and copies init.rc into /system/etc/rootfs. Seems like we need to make ALL of the files for our hijack zip copy into there. Right now the atrix ramdisk should be enough to boot at least. We just need to get it loaded lol. Oh and I don't think CM team actually maintains the Hijack zips, I think they pull it from a seperate repo. But it is maintained for supported devices.
aceoyame said:
2nd init is maintained for supported devices. As for contacting revnumbers... I already was in contact with him lol. I worked with him on the D2G for a lot of things. Really our best contact would be to see if CVPCS can figure out what we need to do exactly. All we need to do is expand that task set but I myself am not sure how it works just yet. If you look in that shell script it calls on the task set and copies init.rc into /system/etc/rootfs. Seems like we need to make ALL of the files for our hijack zip copy into there. Right now the atrix ramdisk should be enough to boot at least. We just need to get it loaded lol. Oh and I don't think CM team actually maintains the Hijack zips, I think they pull it from a seperate repo. But it is maintained for supported devices.
Click to expand...
Click to collapse
Nathan,
CVPCS is on Twitter. I've found that to be the best stream to contact him from. He seems to be pretty responsive. Although, he hasn't posted anything in like 5 days. He seems to have dropped off the face of the earth.
I asked on IRC in #koush and this might be helpful:
(11:30:47 PM) CEnnis91: the only thing i would have to guess is that you're not starting a service that draws the screen
Click to expand...
Click to collapse
Also here is our init.rc uploaded in pastebin, with syntax highlighting. Perhaps it will be helpful, if indeed there is a service that needs to be started, it would probably be in one of these files:
init.rc: http://pastebin.com/kRmnArby
init.mapphone_cdma.rc: http://pastebin.com/qrBpqxGq
init.mapphone_umts.rc: http://pastebin.com/kRmnArby
Btw links #1 and #3 are the same.
I'd like to take a look at several files / outputs from the X2:
Files needed:
/init.rc (or fixed link above)
And the ouput of these adb / terminal commands:
cat /proc/mounts
cat /proc/partitions
cat /proc/cmdline
busybox df
Code:
$ cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p12 /system ext3 ro,noatime,nodiratime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p16 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p15 /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p3 /pds ext3 rw,nosuid,noexec,relatime,data=ordered 0 0
/dev/block/mmcblk0p17 /preinstall ext3 ro,nosuid,nodev,noatime,nodiratime,data=ordered 0 0
/dev/block/vold/179:33 /mnt/sdcard-ext vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/mnt/sdcard-ext /mnt/sdcard-ext ecryptfs rw,dirsync,nosuid,nodev,noexec,relatime,ecryptfs_sig=36933d94cc9c5e9b,ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_passthrough,no_new_encrypted 0 0
/dev/block/vold/179:18 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:18 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/mnt/sdcard /mnt/sdcard ecryptfs rw,dirsync,nosuid,nodev,noexec,relatime,ecryptfs_sig=36933d94cc9c5e9b,ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_passthrough,no_new_encrypted 0 0
Code:
$ cat /proc/partitions
major minor #blocks name
179 0 7747072 mmcblk0
179 1 3584 mmcblk0p1
179 2 512 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 460800 mmcblk0p12
179 13 512 mmcblk0p13
179 14 20480 mmcblk0p14
179 15 315392 mmcblk0p15
179 16 2097152 mmcblk0p16
179 17 307200 mmcblk0p17
179 18 4516864 mmcblk0p18
179 32 15558144 mmcblk1
179 33 15554048 mmcblk1p1
Code:
# cat /proc/cmdline
[email protected] [email protected] vmalloc=224M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=mbr:1100:100:800,kpanic:2500:400:800 security=tomoyo mot_prod=1 androidboot.serialno=TA05406FDO
Code:
# busybox df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 206888 56 206832 0% /dev
tmpfs 206888 0 206888 0% /mnt/asec
tmpfs 206888 0 206888 0% /mnt/obb
/dev/block/mmcblk0p12
458562 201471 257091 44% /system
/dev/block/mmcblk0p16
2064204 115632 1948572 6% /data
/dev/block/mmcblk0p15
305420 10287 295133 3% /cache
/dev/block/mmcblk0p3 1980 1139 841 58% /pds
/dev/block/mmcblk0p17
305793 130975 174818 43% /preinstall
/dev/block/vold/179:33
15549952 875136 14674816 6% /mnt/sdcard-ext
/mnt/sdcard-ext 15549952 875136 14674816 6% /mnt/sdcard-ext
/dev/block/vold/179:18
4508040 3258836 1249204 72% /mnt/sdcard
/dev/block/vold/179:18
4508040 3258836 1249204 72% /mnt/secure/asec
tmpfs 4508040 3258836 1249204 72% /mnt/sdcard/.android_secure
/mnt/sdcard 4508040 3258836 1249204 72% /mnt/sdcard
init.rc @ http://iswarm.net/init.rc
Hashcode said:
Btw links #1 and #3 are the same.
I'd like to take a look at several files / outputs from the X2:
Files needed:
/init.rc (or fixed link above)
And the ouput of these adb / terminal commands:
cat /proc/mounts
cat /proc/partitions
cat /proc/cmdline
busybox df
Click to expand...
Click to collapse
I have all those files, I had to pull them for CVPCS a while back. How do those help in making 2nd-init work right. I haven't really looked at em so sorry if it's obvious.
Sent from my DROID X2 using XDA App
Here is a PM I had from dragonzkiller about a week ago.
Hey, I've appeared to lost my old 2nd-init for CM7. I think that I may actually be able to find it later. I know that you can use mot_boot_mode. Basically if you look at the C code for the hijack that is used for the other motorola devices for CM7 it's really close, but I used a shell script instead. These are the thing that have to happen:
1.Remount the rootfs and system directories as rw
2.rename adbd to adbd.old in /sbin
3.setprop ctl.stop runtime
4.setprop ctl.stop zygote
5.setprop persist.service.adb.enable 1 (this might not work, but I have a new method that actually starts it)
6.mkdir /preinstall
7.mount -t ext3 /dev/block/mmcblk0p17 /preinstall
8./preinstall/update-binary 2 0 NAMEANDPATHOFUPDATE.zip
9.cp -f /NEWROOTPATHFROMUPDATEZIP/* / (CM7 creates a directory named /newboot and all those files will get copied to the rootfs)
10.run the hijack.killall script from the CM7 hijack. (NOTE: you must remove all the references to hijack because we're not using the standard method. just use the regular ones and you'll be fine)
11./sbin/taskset -p -c 0 1 (taskset can be in you update zip)
12./sbin/taskset -c 0 /sbin/2nd-init (this should stop 2nd-init and restart with a new init.rc that you created and copied overy after using the update zip)
Here is the way I edited my script, going to test it in a bit here.
#!/system/bin/sh
PATH=/system/xbin:/system/bin
mount -o remount,rw rootfs /
mount -o remount,rw /system
rename /sbin/adb /sbin/adb.old
setprop ctl.stop runtime
setprop ctl.stop zygote
setprop persist.service.adb.enable 1
mkdir /preinstall
mount -t ext3 /dev/block/mmcblk0p17 /preinstall
/preinstall/update-binary 2 0 /system/etc/hijack-boot.zip
cp -f /newboot/* /
/sbin/hijack.killall
/sbin taskset -p -c 0 1
sbin/taskset -c 0 /sbin/2nd-init
I think your looking for 'mv' not 'rename' ..
Can you link me to where you got your implementation of 2nd init, so i can play as well...
How would mv rename it? I didnt get that part, but rename should work I would imagine.
My system doesnt respond to rename mv is the linux equivalent you 'move' the file to a new name, mv oldfile.txt newfile.txt ..
# cd tbin
# ls
mount.sh
unmount.sh
mrw
mro
# rename mro mrx
rename: not found
# mv mro mrx
# ls
mount.sh
unmount.sh
mrw
mrx
#
Click to expand...
Click to collapse
Update:
I've successfully compiled CWM Recovery for my device. If anyone is inquiring on how PM and I will create a post for it. Because of the lack of support getting to that point I will hold on to it for now.
Now that I've compiled this I really dont know what do next.
---------------------
So I've spent a majority of the day looking at this device (hipstreet flare HS-9DTB4-8GB).
What I'd like to do is compile my own ClockworkMod for this device.
I've spend most of the day working on discovering where everything is and backing up everything using ADB.
Information From Device
Current Rom: Softwinerf900_V1.1.7_20121225r587_27d8028 (Found in Current Chinese Recovery, Option 2, Displayed in Center)
Model-Number: HS-9DTB4
Android version: 4.0.4
Baseband version: 1.4rc3
Kernel version: 3.0.8+ (Tue Dec 25 18:20:41 CST 2012)
Build number: 20130118 F900
Memory: 353MB (Supposed to be 512 and is but I've read there is issues with kernel support.)
Processor: ARMv7 Proccessor rev 2 (v71) 1200MHz
Partition Layout and Confirmed Partitions
cat /proc/partitions
major minor #blocks name
Code:
93 0 16384 nanda bootloader
93 8 16384 nandb
93 16 32768 nandc
93 24 393216 nandd system
93 32 1048576 nande data
93 40 16384 nandf
93 48 32768 nandg
93 56 262144 nandh
93 64 131072 nandi
93 72 16384 nandj
93 80 5799936 nandk sdcard (Mounted by vold as /mnt/sdcard and /mnt/secure/asec)
Partition Layout from what I can see follows Allwinner as described in second table on this site:
http://linux-sunxi.org/Android/partitions
Code:
[email protected]:/ # mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/nandd /system ext4 rw,nodev,noatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/93:80 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:80 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.quoord.tapatalkxda.activity-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
I've backed up nanda, nandb, nandc, nandd, nandg just incase with ADB.
(If anyone would like them I have no issue with sharing. Only thing I've done so far is added ROOT and fixed Keyboard issue, which both can be reversed.)
Like I said, what I'd like to do is Compile CWM for this device. I'm currently setting up Ubuntu as a dual boot so I can do this.
My question is what exactly do I need to do to do this. I understand there are many guides on the steps envolved to do this but if someone could provide the links that are rather structured. Also I'd be interested in working on taking this to the next step to work on making a rom for this.
Update: Stage One
I'm currently following mithun46 guide to build my enviroment (installing linux) I'm installing on a tower that I was using to grow my dust farm...
Now when I get to:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
What should I actually be using so I can build CWM Recovery?
CWM for Hipstreet
I have the same tablet as you Hispstreet Flare 9" ics 4.0 ...... I would love to be able to flash the CWM recovery to my device and thus be able to install custom rom ...could you please help me out
Thanks its would be much appreciated
Did anyone get anywhere with this? Would love a simple way to root and install custom rom on this. Launchers just don't give me quite the flexibility that I want and it's very laggy when I get too many apps open but hardware specs should allow this to run better. I'm not a dev and knowledge is limited but I can follow steps in order and send feedback if that would help, as long as it's not going to brick it LOL - Hubby would kill me but I am just itching to do more with it.
Lost On Off Switch Function
I was cleaning up some old installs and somehow deleted the file that controls the on off switch. You would not know which file that would be would you? (And where I might find it?)
Regards,
tsb
stock roms
tsbrownie said:
I was cleaning up some old installs and somehow deleted the file that controls the on off switch. You would not know which file that would be would you? (And where I might find it?)
Regards,
tsb
Click to expand...
Click to collapse
Does anyone know where to find stock roms for the hip street devices? Would be greatly appreciated! thanks
Help with stock rom
cr3at1ve said:
Does anyone know where to find stock roms for the hip street devices? Would be greatly appreciated! thanks
Click to expand...
Click to collapse
I have been looking for a stock rom as well as my issue is that it will not boot past the hipstreet flare 2 logo, i'm really not sure what to do now I have tried to contact customer support with no avail.
Any help would be great!!
Thanks in advance
Good news. Root is on the way. I have found an exploit (namely the dirty cow exploit to gain root access), only problem is my root lasts for 1 command and I am trying to work out a way to transfer over the su binary itself. I will update this post once I have more info.
ALSO, AND THIS IS IMPORTANT. IF YOU WANT ROOT, DO NOT UPDATE TO ZV6 WHEN IT DROPS. ZV6 WILL LIKELY PATCH THIS EXPLOIT.
Reserved
Following!
Noticed on another forum, ZV6 has appeared.
I cannot remember if you are given a choice whether to install these or not...turned off wifi/data just in case, lol.
It will download the update, but it won't install without your permission. As an update on root. I have a root shell, but I cannot do anything thanks to SELinux. I need to find an exploit to get around SELinux.
Code:
λ adb -d shell
[email protected]:/ $ run-as exec whoami
Warning: setcon transition to 'u:r:init:s0' failed (is SELinux Enforcing?)
root
[email protected]:/ $ run-as exec dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
Warning: setcon transition to 'u:r:init:s0' failed (is SELinux Enforcing?)
dd: /dev/block/bootdevice/by-name/boot: Permission denied
I knew about ZV6 because I saw the kernel sourrces when I went to download the ZV5 source
if this helps........
EagerestWolf said:
Reserved
Click to expand...
Click to collapse
https://mega.nz/#!6BMlmIZB!CBKqxLvGl3c2EfYXj6_hIbdUKxPtbfWzgoglQb0d5aA
thats the ZV5 update for the LGLS775ABB that popped up on my LGLS775ABB ZVZ4!
454.4mb.zip, unzips to 1.02gb..............
If you can get any way to recovery from a predicament out of it, please share!
zach
---------- Post added at 11:16 PM ---------- Previous post was at 11:10 PM ----------
EagerestWolf said:
It will download the update, but it won't install without your permission. As an update on root. I have a root shell, but I cannot do anything thanks to SELinux. I need to find an exploit to get around SELinux.
Code:
λ adb -d shell
[email protected]:/ $ run-as exec whoami
Warning: setcon transition to 'u:r:init:s0' failed (is SELinux Enforcing?)
root
[email protected]:/ $ run-as exec dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
Warning: setcon transition to 'u:r:init:s0' failed (is SELinux Enforcing?)
dd: /dev/block/bootdevice/by-name/boot: Permission denied
Click to expand...
Click to collapse
Definitely no dev here, but using a selenix mode changer app, in 5.1.1, linking su binaries from su/bin to system/xbin allowed it to set selenix to permissice on the Samsung Galaxy J3 (2016) SM-J320P until we got a permissive kernel. That phone has one messed up os hyrbid odex & deodex mix..............
zach...........
---------- Post added at 11:21 PM ---------- Previous post was at 11:16 PM ----------
EagerestWolf said:
I knew about ZV6 because I saw the kernel sourrces when I went to download the ZV5 source
Click to expand...
Click to collapse
If your kdz's available you can't be talking about the BOOST Mobile Stylo 2........... only one LG's not coughing up software for........ oh well, damn, thought I had found something going somewhere for this device..............
Yes that link above is for BOOST LG Stylo 2! The update was waiting right out of the box, it was already on ZV4 so factory reset hooked it up immediately and run a log cat until it acquired the update again. Then spent about 20 minutes going through all the https links until finding the one the update was coming from and downloaded to the Windows machine.
zach
If you go to LG's Open Source Website. They have all the kernel sources there. ZV6 is listed so it's coming. As for your update package, I looked and I wasn't sure if I saw a recovery image, but I did see a LAF image, which is also helpful.
As for bypassing SELinux, I have a few leads on that one. Once we have root, we will have recovery and ROM's, but we need root first to fix fastboot.
I am actually going to try injecting a modified kernel into your update an flashing it. Since this is an official FOTA. It may work.
!!!!!!!
EagerestWolf said:
I am actually going to try injecting a modified kernel into your update an flashing it. Since this is an official FOTA. It may work.
Click to expand...
Click to collapse
Coolbeans!!! Its signed, can't remember the name but do remember seeing the signature verification. I used winrar so nothing should be messed up with it as well.
Any help, anything, just let me know! I cannot understand why another excellent phone for this price is drifting str8 past any development. Went to Asus after I first got into modding and my HTC burnt..... left them due to their never unlocking bootloaders, etc.... Samsung next, the J3, one messed up piece of os there but we modded the hell out of it, now LG............ every variant of this device has the kdz available if I'm not mistaken. If temp root had to be forced onto this phone, to dd it it would just about be worth the $119 it cost me!
zach
TWRP
EagerestWolf said:
I am actually going to try injecting a modified kernel into your update an flashing it. Since this is an official FOTA. It may work.
Click to expand...
Click to collapse
terminal:
cat /proc/cmdline
trying to get kernel cmd line
& arguments
also stock boot.img
but keep getting perm denied
Can you get any of this so TWRP can be ported?
The person who did TWRP for the Stylo 2 + says he can port TWRP for Stylo 2 LGLS775ABB (my device) if whats listed above can be provided.
Any ideas?
That won't work, we need root, and before we can do anything related to TWRP, we need fastboot, so this is all in vain.
Sent from my LGLS775 using Tapatalk
coolbeans2016 said:
terminal:
cat /proc/cmdline
trying to get kernel cmd line
& arguments
also stock boot.img
but keep getting perm denied
Can you get any of this so TWRP can be ported?
The person who did TWRP for the Stylo 2 + says he can port TWRP for Stylo 2 LGLS775ABB (my device) if whats listed above can be provided.
Any ideas?
Click to expand...
Click to collapse
I can provide a stock boot.img I have for LS775 ZV5 build, but cat /proc/cmline is useless right now. I do get some output with cat /proc/partitions and cat /proc/mounts
Code:
major minor #blocks name
253 0 485204 zram0
179 0 15388672 mmcblk0
179 1 512 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 1536 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 512 mmcblk0p14
179 15 1536 mmcblk0p15
179 16 1536 mmcblk0p16
179 17 24576 mmcblk0p17
179 18 24576 mmcblk0p18
179 19 24576 mmcblk0p19
179 20 24576 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 512 mmcblk0p24
179 25 512 mmcblk0p25
179 26 512 mmcblk0p26
179 27 512 mmcblk0p27
179 28 512 mmcblk0p28
179 29 8192 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 10240 mmcblk0p31
259 0 8192 mmcblk0p32
259 1 8192 mmcblk0p33
259 2 65536 mmcblk0p34
259 3 1024 mmcblk0p35
259 4 2560 mmcblk0p36
259 5 2048 mmcblk0p37
259 6 6144 mmcblk0p38
259 7 40960 mmcblk0p39
259 8 3207168 mmcblk0p40
259 9 921600 mmcblk0p41
259 10 10915840 mmcblk0p42
259 11 8175 mmcblk0p43
179 32 4096 mmcblk0rpmb
Code:
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
/dev/pstore /dev/pstore pstore rw,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/bootdevice/by-name/system /system ext4 ro,seclabel,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,resuid=1000,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/modem /firmware vfat ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/bootdevice/by-name/sns /sns ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/drm /persist-lg ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/mpt /mpt ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/carrier /carrier ext4 rw,seclabel,nodev,relatime,noauto_da_alloc,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
EagerestWolf said:
That won't work, we need root, and before we can do anything related to TWRP, we need fastboot, so this is all in vain.
Sent from my LGLS775 using Tapatalk
Click to expand...
Click to collapse
Have you been able to achieve some progress? If you need to try I have some time and one of these phone to try. I really need root on this version.
coolbeans2016 said:
terminal:
cat /proc/cmdline
trying to get kernel cmd line
& arguments
also stock boot.img
but keep getting perm denied
Can you get any of this so TWRP can be ported?
The person who did TWRP for the Stylo 2 + says he can port TWRP for Stylo 2 LGLS775ABB (my device) if whats listed above can be provided.
Any ideas?
Click to expand...
Click to collapse
You can get your cmdline from unpacked boot
Sent from my SM-J320P using Tapatalk
coolbeans2016 said:
terminal:
cat /proc/cmdline
trying to get kernel cmd line
& arguments
also stock boot.img
but keep getting perm denied
Can you get any of this so TWRP can be ported?
The person who did TWRP for the Stylo 2 + says he can port TWRP for Stylo 2 LGLS775ABB (my device) if whats listed above can be provided.
Any ideas?
Click to expand...
Click to collapse
rick.wardenburg said:
You can get your cmdline from unpacked boot
Sent from my SM-J320P using Tapatalk
Click to expand...
Click to collapse
This is cmdline from unpacked boot image.
Code:
cmdline = console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=ph1 user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 vmalloc=600m
Any progress on this or is it a another dead end for us?
Sent from my LGLS775 using Tapatalk
can someone pm me when you do obtain root permanently
....will keep checking...also i can make a stock dimp of my zv4 if ne one needs it since lg likes to keep everything tight....does anyone know how to enter download mode??
Doctur said:
can someone pm me when you do obtain root permanently
....will keep checking...also i can make a stock dimp of my zv4 if ne one needs it since lg likes to keep everything tight....does anyone know how to enter download mode??
Click to expand...
Click to collapse
And if someone tells you, please tell me. : )
I was going to root my friends Android, however after further discovery --- thus far--- it looks like this device has not been rooted yet.
Is anyone able to create a partion.xml for use with tool studio eMMC download tool. Im trying to figure it out myself and having a little trouble but I believe it should allow us to flash the v3 firmware.