CM9 / CM10 / Kernel Issues? / HELP! - HTC One V

Hi everybody,
After (to my knowledge) succesfully unlocking bootloader using Hasoon2000's Kit I used steps 1 to 8 (using http://forum.xda-developers.com/showthread.php?t=1598964) for the PrimoU to Root my phone. Then I installed CWM and make a backup of the build that I was using on my SDCARD.
LOG:
Code:
Starting recovery on Mon Aug 27 21:23:09 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
ClockworkMod Recovery v5.8.3.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p22 (null) 0
2 /cache ext4 /dev/block/mmcblk0p28 (null) 0
3 /data ext4 /dev/block/mmcblk0p26 (null) 0
4 /misc emmc /dev/block/mmcblk0p17 (null) 0
5 /recovery emmc /dev/block/mmcblk0p21 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
7 /system ext4 /dev/block/mmcblk0p25 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=cyanogen_primou-eng 2.3.7 GINGERBREAD eng.vivek.20120505.222219 test-keys
ro.build.version.incremental=eng.vivek.20120505.222219
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Sat May 5 22:22:37 IST 2012
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=vivek
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=cyanogen_primou
ro.product.device=primou
ro.product.board=primou
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=primou
ro.build.description=cyanogen_primou-eng 2.3.7 GINGERBREAD eng.vivek.20120505.222219 test-keys
ro.build.fingerprint=Android/cyanogen_primou/primou:2.3.7/GINGERBREAD/eng.vivek.20120505.222219:eng/test-keys
ro.cm.device=primou
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT23YTV21132
ro.bootmode=offmode_charging
ro.baseband=3831.17.00.18_M
ro.carrier=HTC-Dutch
ro.bootloader=1.17.0000
ro.hardware=primou
ro.revision=2
ro.emmc=1
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 116 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 116 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 116 1
fd: 10
ev: 0 0 0
After this I wanted to install CM9 or CM10 on my phone. Basically what I did is boot in bootloader->fastboot and I flashed the correct kernel supplied with the CM thread.
Code:
C:\HTCOneV\data>adb kill-server
C:\HTCOneV\data>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\HTCOneV\data>adb push Kernels/Modules/system /system
error: device not found
C:\HTCOneV\data>adb reboot bootloader
error: device not found
C:\HTCOneV\data>fastboot flash boot Kernels/boot.img
sending 'boot' (2800 KB)... OKAY [ 2.177s]
writing 'boot'... OKAY [ 1.444s]
finished. total time: 3.621s
C:\HTCOneV\data>fastboot reboot
rebooting...
finished. total time: 0.217s
Then I rebooted into recovery, I followed the steps and now what happens is that each time I reboot my phone I get the HTC Screen with the red text (Developer blablabla) then a few seconds of the CM animation and after that the phone just freezes. I can use the power button to restart and +voldown to get into the CWM/bootloader but thats it.
I tried to use the recovery to get back, but while using that I get the same thing, the HTC Screen with the red text (Developer blabla) then a few seconds of the HTC 'brilliance' animation, but then it also freezes.
I did something wrong, but what? I would like to try another kernel like the KISS one, but would it work with the CM-ROM or would I have to pick another ROM instead? (and if so; could you appoint me one?)
Last; if I would go back to a stock rom; I wouldnt know which one to chose. What if my battery runs out, is it actually charging when hooked to my pc? Help! :crying:
Kind Regards,
Aphromode
Information about my BOOT:
*** UNLOCKED ***
PRIMOU PVT SHIP S-ON RL
HBOOT-1.17.0000
RADIO-3831.17.00.18_M
eMMC-boot
May 15 2012,10:28:15
IMAGE CRC:
osbl: 0x7F9959AF
amss: 0xD1F29E93
hboot: 0xE46C3327
boot: 0x1555E80C2
recovery: 0xC8BBA213
system: 0x2D30BFD9

Just dropped by to say the KISS kernel thread has kernel for CM too and I believe one they provided on CM thread is the same.
Try again maybe? did you wipe /system?

You have to use the KISS kernel. If you are using the latest kiss kernel, the problem might be that your phone can not handle the kernel that is overclocked by default. Try to use the previous version that boots at 1GHz. This issue was reported also by another user.

hlavicka82 said:
You have to use the KISS kernel. If you are using the latest kiss kernel, the problem might be that your phone can not handle the kernel that is overclocked by default. Try to use the previous version that boots at 1GHz. This issue was reported also by another user.
Click to expand...
Click to collapse
The Issue has been resolved, indeed it was the default overclocking that lead to the freezing.
Solution: Use the 1GHz kernel instead of the overclocked one.

Related

[Q] Info`s about /dev/block

Hello, can anybody with a rooted Gio point me out to the /dev/block files for /system , /data , /cache ?
For example for GSII is /dev/block/mmcblk0p24 25 26
At us i think it should be something with 12/13/14
I need the correct filenames from our Gio. Only names i don`t actually need the files
Thank u in advance
I have CyanogenMod 7.2 installed with ext4 partition on SD.
Here's what "mount" says on my phone (stripped the mounts for individual apps).
I decided to leave other non-/dev/block entries here, too, just in case
Code:
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/stl12 on /system type ext4 (ro,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/stl13 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/stl14 on /cache type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p2 on /sd-ext type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=19,barrier=0,nobh,data=writeback)
/dev/block/mmcblk0p2 on /data/app type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=19,barrier=0,nobh,data=writeback)
/dev/block/mmcblk0p2 on /data/data type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=19,barrier=0,nobh,data=writeback)
/dev/block/mmcblk0p2 on /cache/download type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=19,barrier=0,nobh,data=writeback)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
BML partition layout of the Samsung Galaxy Gio GT-S5660:
bml0: contents of the entire flash
bml1: mibib
bml2: qcsbl
bml3: oemsbl
bml4: amss
bml5: block level representation of /dev/stl5 (efs)
bml6: block level representation of /dev/stl6 (empty)
bml7: arm11boot
bml8: boot image
bml9: recovery image
bml10: unknown
bml11: empty (contains only 0xff bytes)
bml12: block level representation of /dev/stl12 (/system)
bml13: block level representation of /dev/stl13 (/data)
bml14: block level representation of /dev/stl14 (/cache)
STL partition layout of the Samsung Galaxy Gio GT-S5660:
stl5: /efs
stl6: empty partition (contains only 0xff bytes)
stl12: /system
stl13: /data
stl14: /cache
Partition layout used by ODIN (GIO_v1.0.ops):
0,mibib
1,qcsbl
2,oemsbl
3,amss
4,arm11boot
5,boot
6,recovery
7,system
8,data
9,csc
10,
Available partitions according to /proc/partitions:
major minor size device
137 0 513024 bml0/c
137 1 1536 bml1
137 2 512 bml2
137 3 768 bml3
137 4 25600 bml4
137 5 9216 bml5
137 6 5120 bml6
137 7 2048 bml7
137 8 8192 bml8
137 9 8192 bml9
137 10 768 bml10
137 11 6144 bml11
137 12 222464 bml12
137 13 192768 bml13
137 14 29696 bml14
138 12 214784 stl12
138 13 185600 stl13
138 14 25856 stl14
particle.blurringexistence.net/samsung-gt-s5660/partition-layout
Sent from my GT-S5660 using XDA Premium App
Thank u both ! I wanted to try to port DARKSIDE::SUPER::WIPE but it formats in Ext4 and i need in rfs because atm i only use stock rom
Note that my output is from CM which uses ext4, too. No rfs there, sorry
hsrars-d said:
BML partition layout of the Samsung Galaxy Gio GT-S5660:
bml0: contents of the entire flash
bml1: mibib
bml2: qcsbl
bml3: oemsbl
bml4: amss
bml5: block level representation of /dev/stl5 (efs)
bml6: block level representation of /dev/stl6 (empty)
bml7: arm11boot
bml8: boot image
bml9: recovery image
bml10: unknown
bml11: empty (contains only 0xff bytes)
bml12: block level representation of /dev/stl12 (/system)
bml13: block level representation of /dev/stl13 (/data)
bml14: block level representation of /dev/stl14 (/cache)
STL partition layout of the Samsung Galaxy Gio GT-S5660:
stl5: /efs
stl6: empty partition (contains only 0xff bytes)
stl12: /system
stl13: /data
stl14: /cache
Partition layout used by ODIN (GIO_v1.0.ops):
0,mibib
1,qcsbl
2,oemsbl
3,amss
4,arm11boot
5,boot
6,recovery
7,system
8,data
9,csc
10,
Available partitions according to /proc/partitions:
major minor size device
137 0 513024 bml0/c
137 1 1536 bml1
137 2 512 bml2
137 3 768 bml3
137 4 25600 bml4
137 5 9216 bml5
137 6 5120 bml6
137 7 2048 bml7
137 8 8192 bml8
137 9 8192 bml9
137 10 768 bml10
137 11 6144 bml11
137 12 222464 bml12
137 13 192768 bml13
137 14 29696 bml14
138 12 214784 stl12
138 13 185600 stl13
138 14 25856 stl14
particle.blurringexistence.net/samsung-gt-s5660/partition-layout
Sent from my GT-S5660 using XDA Premium App
Click to expand...
Click to collapse
Sorry to bring the thread back up from the ground but i need some info on how to rebuild/force format on block stl13.
Have tried multiple CWM flashes now and stock rom flashes via Odin but stilll no good

S4 I9500 partitions and CPU info

[email protected]:/dev/block/platform/dw_mmc.0/by-name $ ls -la
ls -la
lrwxrwxrwx root root 2013-03-26 16:07 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-03-26 16:07 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-03-26 16:07 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-03-26 16:07 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-03-26 16:07 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-03-26 16:07 CDMA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-03-26 16:07 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-03-26 16:07 HIDDEN -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-03-26 16:07 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-03-26 16:07 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-03-26 16:07 PERSDATA -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-03-26 16:07 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-03-26 16:07 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-03-26 16:07 RESERVED2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-03-26 16:07 SYSTEM -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-03-26 16:07 TDATA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-03-26 16:07 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-03-26 16:07 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-03-26 16:07 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-03-26 16:07 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-03-26 16:07 m9kefs3 -> /dev/block/mmcblk0p6
[email protected]:/ $ cat /proc/cpuinfo
cat /proc/cpuinfo
Processor : ARMv7 Processor rev 3 (v7l)
processor : 0
BogoMIPS : 1590.88
processor : 1
BogoMIPS : 1590.88
processor : 2
BogoMIPS : 1590.88
processor : 3
BogoMIPS : 1590.88
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva id
ivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc0f
CPU revision : 3
Hardware : UNIVERSAL5410
Revision : 0009
Serial : xxxxxxxxxxx4d00ee10
Build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39
ro.build.display.id=JDQ39.I9500XXUAMC6
ro.build.version.incremental=I9500XXUAMC6
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Mon Mar 11 22:42:39 KST 2013
ro.build.date.utc=1363009359
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-127
ro.build.tags=release-keys
ro.product.model=GT-I9500
ro.product.brand=samsung
ro.product.name=ja3gxx
ro.product.device=ja3g
ro.product.board=universal5410
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=exynos5
# ro.build.product is obsolete; use ro.product.device
ro.build.product=ja3g
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=ja3gxx-user 4.2.2 JDQ39 I9500XXUAMC6 release-keys
ro.build.fingerprint=samsung/ja3gxx/ja3g:4.2.2/JDQ39/I9500XXUAMC6:user/release-keys
ro.build.characteristics=lightTheme
# Samsung Specific Properties
ro.build.PDA=I9500XXUAMC6
ro.build.hidden_ver=I9500XXUAMC6
ro.build.changelist=265143
ro.product_ship=true
ro.chipname=exynos5410
# end build properties
This is the 16gb model if I am correct? Interesting it's ext4.
Sent from my HTC One S using xda app-developers app
Closed Source Project said:
This is the 16gb model if I am correct? Interesting it's ext4.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Why is that interesting?
Toss3 said:
Why is that interesting?
Click to expand...
Click to collapse
+1 :angel:
Samsung has been on EXT4 after the S1. Google forced them over. Its not surprising.
I want to ask you, to do into terminal
Code:
su
cd dev/block/platform/dw_mmc/by-name
ls -l
and upload result..
after this, if you can, make dump partitions: boot, recovery, system, cache, hidden, modem, param
Code:
su
dd if=dev/block/mmcblk0p[partition number] of=sdcard/[image file]
Then I will try make ROM for flash via odin
my S4 not have root！ Can you ROOT my S4?
zhangqip said:
my S4 not have root! Can you ROOT my S4?
Click to expand...
Click to collapse
But for this i need any stock rom or system dump from cwm
p.s.
try load phone into recovery mode, connect to kies and choose restore device, kies must download 3th files service ROM, on PC
zhangqip said:
my S4 not have root！ Can you ROOT my S4?
Click to expand...
Click to collapse
If you want it to root plant it in the ground and water it...
Sent from my HTC One S using xda app-developers app
Here are more details extracted from Screener device, credits goes to him.
Partition sizes:
Code:
major minor #blocks name
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 20480 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 8192 mmcblk0p10
259 3 8192 mmcblk0p11
259 4 8192 mmcblk0p12
259 5 90112 mmcblk0p13
259 6 262144 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 573440 mmcblk0p16
259 9 12288 mmcblk0p17
259 10 4096 mmcblk0p18
259 11 2121728 mmcblk0p19
259 12 2830336 mmcblk0p20
259 13 9379840 mmcblk0p21
and Mount points:
Code:
rootfs / rootfs ro,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
none /dev/cpuctl cgroup rw,relatime,cpu 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
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p17 /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p20 /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p19 /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p21 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/legacy sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/legacy/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
[/COLOR]wanam you're a genius, finally, today I will make system.img... with root for Odin
well done
http://forum.xda-developers.com/showthread.php?t=2213775
Closed Source Project said:
If you want it to root plant it in the ground and water it...
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Hahahahaha rooting made simple lol
Sent from my GT-I9500 using xda app-developers app
wanam said:
Here are more details extracted from Screener device, credits goes to him.
Partition sizes:
Code:
major minor #blocks name
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 20480 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 8192 mmcblk0p10
259 3 8192 mmcblk0p11
259 4 8192 mmcblk0p12
259 5 90112 mmcblk0p13
259 6 262144 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 573440 mmcblk0p16
259 9 12288 mmcblk0p17
259 10 4096 mmcblk0p18
259 11 2121728 mmcblk0p19
259 12 2830336 mmcblk0p20
259 13 9379840 mmcblk0p21
and Mount points:
Code:
rootfs / rootfs ro,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
none /dev/cpuctl cgroup rw,relatime,cpu 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
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p17 /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p20 /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p19 /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p21 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/legacy sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/legacy/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
Click to expand...
Click to collapse
with this in future can have more space in internal card??
e
GT-I9500 cihazımdan Tapatalk kullanılarak gönderildi
Deleted because I found what I was looking for :thumbup:
Sent from my GT-I9500

[Q] Widget/script for properly mounting/unmounting external sd card

Hey, I'm trying to create two shortcuts on my home launcher to unmount the sdcard and the other one to mount it for safe eject purposes. I have a galaxy s3 sgh-i747 at&t running AOKP 4.4.4 rooted/busyboxed. I am trying to create two scripts that i can simply run with a click of the SManager widget instead of having to go through all the settings and unmounting it from there.
Partitions:
Code:
179 0 15388672 mmcblk0
179 1 61440 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 10240 mmcblk0p10
179 11 13952 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 1536000 mmcblk0p14
179 15 12832768 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 860160 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 6144 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 8 mmcblk0p22
179 23 5120 mmcblk0p23
179 32 7761920 mmcblk1
179 33 7757824 mmcblk1p1
Mounts:
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
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,fmask=0177,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:33 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
The sdcard is mount # 33 located at block mmcblk1p1
The location of the mount is /storage/sdcard1 or /mnt/media_rw/sdcard1 (looks like the one in /storage is just a link to the real one in /mnt)
I am aware of the commands mount/umount.
Please help me out. Thanks!

[REF] partition layout

Output from cat /proc/partitions, names shown in red do not appear, they have been taken from different files in the system, they could be wrong!
Code:
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
31 0 1024 mtdblock0
179 0 3866624 mmcblk0
179 1 128 mmcblk0p1
179 2 512 mmcblk0p2 [COLOR="Red"] mbm[/COLOR]
179 3 512 mmcblk0p3
179 4 1 mmcblk0p4 [COLOR="Red"] ebr[/COLOR]
179 5 512 mmcblk0p5 [COLOR="Red"] cdt[/COLOR]
179 6 4096 mmcblk0p6 [COLOR="Red"] pds[/COLOR]
179 7 1536 mmcblk0p7
179 8 1024 mmcblk0p8 [COLOR="Red"] logo.bin[/COLOR]
179 9 16384 mmcblk0p9[COLOR="Red"] boot[/COLOR]
179 10 16384 mmcblk0p10[COLOR="Red"] recovery[/COLOR]
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 8192 mmcblk0p13
179 14 262144 mmcblk0p14 [COLOR="Red"] system[/COLOR]
179 15 262144 mmcblk0p15 [COLOR="Red"] cache[/COLOR]
179 16 131072 mmcblk0p16 [COLOR="Red"] customize[/COLOR]
179 17 3160064 mmcblk0p17 [COLOR="Red"] data[/COLOR]
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
To encourage more research and developments, use the donate button on the right! thanks!
in case needed, heres output for mount
Code:
[email protected]:/ $ mount
rootfs / rootfs ro,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
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb 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/block/mmcblk0p14 /system ext4 ro,seclabel,relatime,discard,data=ordered 0 0
/dev/block/mmcblk0p15 /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,data=ordered 0 0
/dev/block/mmcblk0p17 /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p6 /pds ext4 rw,seclabel,nosuid,nodev,noatime,discard 0 0
/dev/block/mmcblk0p16 /customize ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime,mode=755 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

Battery drain 6.0.1

Hi, my battery works normally (48 hrs), but if i make a call from Contacts , the battery lasts about 16 hours. If reboot, the problem is solved. I have images but i can't attach them. Thank you.
Wearable-report
Build: M1D64T
Build fingerprint: 'Sony/tetra/tetra:6.0.1/M1D64T/3508863:user/release-keys'
Bootloader: TETRA_Release_118
Radio: BCM23550_14100_04
Network: (unknown)
Kernel: Linux version 3.10.17+ ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Thu Nov 3 17:34:00 CET 2016
------ UPTIME MMC PERF (/sys/block/mmcblk0/) ------
stat: 9856 3958 824554 26170 3360 2445 53441 11030 0 16410 37040
stat: read: 16131KB/s write: 2480KB/s
mmcblk0boot0/stat: 2 0 16 0 0 0 0 0 0 0 0
mmcblk0boot0/stat: read: 0KB/s write: 0KB/s
mmcblk0boot1/stat: 2 0 16 10 0 0 0 0 0 10 10
mmcblk0boot1/stat: read: 819KB/s write: 0KB/s
mmcblk0p24/stat: 54 1770 14592 330 0 0 0 0 0 270 320
mmcblk0p24/stat: read: 22639KB/s write: 0KB/s
mmcblk0p26/stat: 4 3 56 10 0 0 0 0 0 10 10
mmcblk0p26/stat: read: 2867KB/s write: 0KB/s
mmcblk0p30/stat: 24 72 756 0 10 2 96 0 0 0 0
mmcblk0p30/stat: read: 0KB/s write: 0KB/s
mmcblk0p31/stat: 7065 470 597274 18630 0 0 0 0 0 8850 18610
mmcblk0p31/stat: read: 16414KB/s write: 0KB/s
mmcblk0p32/stat: 2699 1643 211796 7200 2880 2443 53345 10970 0 9660 18040
mmcblk0p32/stat: read: 15061KB/s write: 2489KB/s
------ MEMORY INFO (/proc/meminfo) ------
MemTotal: 460620 kB
MemFree: 21148 kB
Buffers: 3456 kB
Cached: 159136 kB
SwapCached: 4 kB
Active: 168824 kB
Inactive: 167808 kB
Active(anon): 88600 kB
Inactive(anon): 88856 kB
Active(file): 80224 kB
Inactive(file): 78952 kB
Unevictable: 1592 kB
Mlocked: 0 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 460620 kB
LowFree: 21148 kB
SwapTotal: 32764 kB
SwapFree: 30552 kB
Dirty: 16 kB
Writeback: 0 kB
AnonPages: 175696 kB
Mapped: 121496 kB
Shmem: 1788 kB
Slab: 25936 kB
SReclaimable: 11508 kB
SUnreclaim: 14428 kB
KernelStack: 5048 kB
PageTables: 10804 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 263072 kB
Committed_AS: 7012588 kB
VmallocTotal: 532480 kB
VmallocUsed: 80148 kB
VmallocChunk: 382980 kB
CmaFree: 12676 kB
CmaA(active): 0 kB
CmaA(inactive): 4 kB
CmaF(active): 16 kB
CmaF(inactive): 0 kB
CmaUnevictable: 0 kB
ContigAlloc: 3688 kB
------ CPU INFO (top -n 1 -d 1 -m 30 -t) ------
User 17%, System 22%, IOW 0%, IRQ 0%
User 37 + Nice 1 + Sys 49 + Idle 132 + IOW 0 + IRQ 0 + SIRQ 0 = 219
PID TID PR CPU% S VSS RSS PCY UID Thread Proc
1701 1701 1 9% R 2372K 932K fg shell top top
91 91 1 6% S 0K 0K fg root irq/411-2-0028
459 538 0 5% R 680248K 71456K fg system PhotonicModulat system_server
121 121 0 4% S 1036K 372K fg root ueventd /sbin/ueventd
459 488 0 3% R 680248K 71456K fg system PowerManagerSer system_server
788 788 0 2% S 401304K 29808K fg u0_a2 earable.ambient com.google.android.wearable.ambient
661 783 0 1% S 514612K 75568K fg u0_a3 SpeechThread com.google.android.wearable.app
157 174 0 1% S 35040K 4156K fg system DispSync /system/bin/surfaceflinger
459 468 0 0% R 680248K 71456K fg system HeapTaskDaemon system_server
157 184 0 0% S 35040K 4156K fg system surfaceflinger /system/bin/surfaceflinger
673 673 0 0% R 437216K 47556K fg u0_a15 rable.watchface com.sonymobile.wearable.watchface
459 478 0 0% S 680248K 71456K fg system Binder_1 system_server
459 863 0 0% S 680248K 71456K fg system Binder_A system_server
24 24 0 0% R 0K 0K fg root kworker/0:1
459 506 0 0% S 680248K 71456K fg system SensorService system_server
157 181 0 0% S 35040K 4156K fg system EventThread /system/bin/surfaceflinger
459 529 0 0% S 680248K 71456K fg system UEventObserver system_server
98 98 0 0% S 0K 0K fg root cfinteractive
160 469 0 0% S 13128K 1324K fg root netd /system/bin/netd
154 154 0 0% S 1700K 176K fg root healthd /sbin/healthd
157 531 0 0% S 35040K 4156K fg system Binder_3 /system/bin/surfaceflinger
25 25 1 0% S 0K 0K fg root kworker/1:1
8 8 1 0% S 0K 0K fg root rcu_preempt
157 173 0 0% S 35040K 4156K fg system Binder_1 /system/bin/surfaceflinger
459 459 0 0% S 680248K 71456K fg system system_server system_server
58 58 1 0% S 0K 0K fg root kswapd0
661 661 0 0% R 514612K 75568K fg u0_a3 id.wearable.app com.google.android.wearable.app
459 861 0 0% S 680248K 71456K fg system Binder_8 system_server
43 43 1 0% S 0K 0K fg root i2c_master_rese
46 46 1 0% S 0K 0K fg root i2c_master_rese
[top: 1.434s elapsed]

Categories

Resources