MTK 6592 Touch Screen Bricked ? - General Questions and Answers

hello i flash my drivice mtk6592 ( star n3+ ocracore ) with a same rom.
is not first time to i flash rom, but dhis new phone worked just a 30 min
after flash my touch screen dont work . and imei ( imei fix ok)
i try so send a lots rom , rom accept never found error . same my touch screen dont work.
and factory rom no success.
maybe i need to edit scatter file?
maybe my touch screen is bricked?
maybe my touch screen have hardware problem?

dhis is my test
Code:
============ Memory Detection Report ===========
Internal RAM:
Size = 0x00020000 (128KB)
External RAM:
Type = DRAM
Size = 0x40000000 (1024MB/8192Mb)
NAND Flash:
ERROR: NAND Flash was not detected!
EMMC:
EMMC_PART_BOOT1 Size = 0x0000000000200000(2MB)
EMMC_PART_BOOT2 Size = 0x0000000000200000(2MB)
EMMC_PART_RPMB Size = 0x0000000000020000(0MB)
EMMC_PART_GP1 Size = 0x0000000000000000(0MB)
EMMC_PART_GP2 Size = 0x0000000000000000(0MB)
EMMC_PART_GP3 Size = 0x0000000000000000(0MB)
EMMC_PART_GP4 Size = 0x0000000000000000(0MB)
EMMC_PART_USER Size = 0x00000003a3e00000(14910MB)
============ RAM Test ============
Data Bus Test:
[D0]
[D1]
[D2]
[D3]
[D4]
[D5]
[D6]
[D7]
[D8]
[D9]
[D10]
[D11]
[D12]
[D13]
[D14]
[D15]
[D16]
[D17]
[D18]
[D19]
[D20]
[D21]
[D22]
[D23]
[D24]
[D25]
[D26]
[D27]
[D28]
[D29]
[D30]
[D31]
OK!!
Address Bus Test:
[A1]
[A2]
[A3]
[A4]
[A5]
[A6]
[A7]
[A8]
[A9]
[A10]
[A11]
[A12]
[A13]
[A14]
[A15]
[A16]
[A17]
[A18]
[A19]
[A20]
[A21]
[A22]
[A23]
[A24]
[A25]
[A26]
[A27]
[A28]
[A29]
OK!!
RAM Pattern Test :
Writing ...
OK!!
Increment/Decrement Test:
Writing...
OK!!
============ NAND Test ============
SKIP! NAND Flash was not detected!
============ EMMC Test ============
OK!!

Code:
?????????adb?fastboot?????,??:
??adb??:adb devices
??shell:adb shell
??????:adb logcat
???????SD?:adb push D:\myfile.pdf /sdcard/
???SD?????:adb pull /sdcard/myfile.pdf D:\
??fastboot??:fastboot devices
??adb????:adb help
??fastboot????:fastboot help
C:\Program Files (x86)\Shuame>adb shell
[email protected]_v92_zlh_hd:/ $ cat /proc/devices
cat /proc/devices
Character devices:
1 mem
2 pty
3 ttyp
5 /dev/tty
5 /dev/console
5 /dev/ptmx
10 misc
13 input
14 sound
29 fb
90 mtd
108 ppp
116 alsa
128 ptm
136 pts
141 mtk_stp_usktrk
153 mtk_wmt_WIFI_chrdev
160 Vcodec
166 ttyACM
168 MJC
180 usb
182 sec
184 ccci0
184 CCCI_IPC_DEV0
184 ccci1_fs
184 vir_chr0
184 ccci_tty_drv0
188 M4U_device
189 usb_device
190 mtk_stp_wmt
191 mtk_stp_GPS_chrdev
192 mtk_stp_BT_chrdev
193 fm
196 devmap
204 ttyMT
226 ttyGS
227 camera-pipemgr
228 mt3326-gps
229 camera-sysram
230 camera-isp
231 FM50AF
232 kd_camera_hw
233 DumChar
234 accdet
235 mtk-adc-cali
236 mtk_disp
237 MTK_SMI
238 dummy_eeprom
239 dummy_cam_cal
240 hall_dev
241 AGOLD_DRIVER
242 mtk_jpeg
243 pmt
244 kd_camera_flashlight
245 flash_info
246 btn
247 mtk_almk
248 btif
249 MT_pmic_adc_cali
250 mtkfb_vsync
251 mmp
252 sched
253 BOOT
254 rtc
Block devices:
259 blkext
7 loop
8 sd
31 mtdblock
65 sd
66 sd
67 sd
68 sd
69 sd
70 sd
71 sd
128 sd
129 sd
130 sd
131 sd
132 sd
133 sd
134 sd
135 sd
179 mmc
253 zram
254 device-mapper
[email protected]_v92_zlh_hd:/ $
C:\Program Files (x86)\Shuame>adb shell
[email protected]_v92_zlh_hd:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 1254 loop0
253 0 1048576 zram0
179 0 15246336 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 819200 mmcblk0p5
179 6 131072 mmcblk0p6
179 7 1212416 mmcblk0p7
179 8 13001728 mmcblk0p8
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 7764992 mmcblk1
179 97 7760896 mmcblk1p1
[email protected]_v92_zlh_hd:/ $ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,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/secure tmpfs rw,relatime,mode=700 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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/[email protected] /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=or
dered 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ord
ered 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_all
oc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_all
oc,commit=1,data=ordered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
/dev/block/vold/179:8 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]_v92_zlh_hd:/ $

BliNeR-KeY said:
hello i flash my drivice mtk6592 ( star n3+ ocracore ) with a same rom.
is not first time to i flash rom, but dhis new phone worked just a 30 min
after flash my touch screen dont work . and imei ( imei fix ok)
i try so send a lots rom , rom accept never found error . same my touch screen dont work.
and factory rom no success.
maybe i need to edit scatter file?
maybe my touch screen is bricked?
maybe my touch screen have hardware problem?
Click to expand...
Click to collapse
Same happened to me. Have you managed to fix this issue?

anyone found solution?

same happened to me too. i've tried removing the digitizer, but i don't think the problem is in digitizer. when it's connected i can see touchscreen: ili2113a in factory mode. when i disconnect the digitizer, i can see touchscreen: (null)
so digitizer should be working. i've tried flashing like 15 roms, but didn't manage to fix the problem.
anyone found a solution?

hello
you solved?
---------- Post added at 11:45 AM ---------- Previous post was at 11:34 AM ----------

maybe not yet solved

İ have same as your problem. My device is General Mobile etab5. Calibration failed it says invalid value: 165

Related

[Q] HTC Sensation, Flashing offical ROM, branded, SIMunlock, rooted

Hi I know im new to this forum, but I am technically knowledgeable, however I have a question, I bought a HTC Sensation, that was branded and locked to three UK network..
After thinking about this, is it not the case that network locks are applied by the network operator when they brand the device, if so, whats to stop me from flashing a Europe version, which I assume would get rid of all that, since it would then function as if it was not from any specific carrier right ?
My Sensation has been, s-off, permanently rooted, and super CID, with complete success, and i have done a backup with clockwork..
I mean the whole point to doing all this is so you are able to modify and have complete access to the set, i have seen people manually hex edit a specific file to make the phone unlocked on all networks, but that was for a different HTC model..
Any advice would be welcome.. !
List of defualt mounts HTC Sensation
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
/dev/block/mmcblk0p22 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p23 /data ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data= ordered 0 0
/dev/block/mmcblk0p24 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data= ordered 0 0
/dev/block/mmcblk0p27 /devlog ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data= ordered 0 0
/dev/block/mmcblk0p17 /vendor/firmware/misc vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022 ,codepage=cp437,iocha
rset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/sys/kernel/debug /sys/kernel/debug debugfs 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 /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/data/d /data/d debugfs rw,relatime 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allo w_other 0 0
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=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:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0702,dmask=
0702,allow_utime=0020,codepage=cp437,iocharset=iso 8859-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.androirc-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=02 22,dmask=0222,codepage=c
p437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.svox.pico.voice.eng.gbr-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=02 22,dmask=
0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
List of defualt files in /dev/block/
mmcblk1p1
mmcblk1
mmcblk0p31
mmcblk0p30
mmcblk0p29
mmcblk0p28
mmcblk0p27
mmcblk0p26
mmcblk0p25
mmcblk0p24
mmcblk0p23
mmcblk0p22
mmcblk0p21
mmcblk0p20
mmcblk0p19
mmcblk0p18
mmcblk0p17
mmcblk0p16
mmcblk0p15
mmcblk0p14
mmcblk0p13
mmcblk0p12
mmcblk0p11
mmcblk0p10
mmcblk0p9
mmcblk0p8
mmcblk0p7
mmcblk0p6
mmcblk0p5
mmcblk0p4
mmcblk0p3
mmcblk0p2
mmcblk0p1
mmcblk0
loop7
loop6
loop5
loop4
loop3
loop2
loop1
loop0
Will find out soon..
Im going to pay my three network to give me the code to unlock my phone, when thay do, ill serch for that code in the files on my device and tell you where you can also get yours.. thats if its not encoded or something..
will be looking forward to this, I also have a 3(uk) locked phone, which i installed a custom rom on, was expecting the phone to open onto all networks (like my old htc touch hd).
good luck, will be checking progress.
sa2am said:
will be looking forward to this, I also have a 3(uk) locked phone, which i installed a custom rom on, was expecting the phone to open onto all networks (like my old htc touch hd).
good luck, will be checking progress.
Click to expand...
Click to collapse
help me here, thanks.
http://forum.xda-developers.com/showpost.php?p=16816803&postcount=1
Ok ive held off paying £15 quid to get the code at the moment, im looking for the code my self.. at the moment the codes ive used dont work, including the date in mmcp6 file..
If you want to try your self.. use ADB..
Open a CMD window and type:
adb shell
su
dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcp4.dump
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcp6.dump
dd if=/dev/block/mmcblk0p16 of=/sdcard/mmcp16.dump
then mount ur sdcard, and open the drive in windows.. and copy the files over.. and open them in hex edotor or notepad dosent really matter what.. and try numbers.. it should be 8 digits..
This is the output from copying the files over for me.. so you can see the byte sizes etc
# dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcp4.dump
dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcp4.dump
2+0 records in
2+0 records out
1024 bytes transferred in 3.160 secs (324 bytes/sec)
# dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcp6.dump
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcp6.dump
512+0 records in
512+0 records out
262144 bytes transferred in 0.163 secs (1608245 bytes/sec)
# dd if=/dev/block/mmcblk0p16 of=/sdcard/mmcp16.dump
dd if=/dev/block/mmcblk0p16 of=/sdcard/mmcp16.dump
512+0 records in
512+0 records out
262144 bytes transferred in 0.086 secs (3048186 bytes/sec)
#
Heres more info on this subject:
http://forum.xda-developers.com/showthread.php?p=16933050#post16933050
Method one is not the same on my device, though there is a date its not in the same place.. and dosent work..
so im tempted to try mothod 2.. but a bit hessitant to try things that i dont know what damage it would do..
Ok screw it just did method 2 in here:
http://forum.xda-developers.com/showthread.php?p=16933050#post16933050
And POW indeed my sim is now unlocked.. and whats great it it also removed the dumb boot branding screen of Three network as well...

[Q] samsung galaxy wifi 5.0 boot.img

Does this device have a boot.img file that is accessible and editable?
I have the following details from the system files:
Code:
# cat /proc/partitions
major minor #blocks name
179 0 7757824 mmcblk0
179 1 1 mmcblk0p1
179 5 256 mmcblk0p5
179 6 256 mmcblk0p6
179 7 1280 mmcblk0p7
259 0 1280 mmcblk0p8
259 1 5120 mmcblk0p9
259 2 10240 mmcblk0p10
259 3 7680 mmcblk0p11
259 4 7680 mmcblk0p12
259 5 296960 mmcblk0p13
259 6 137216 mmcblk0p14
259 7 65536 mmcblk0p15
259 8 1970176 mmcblk0p16
259 9 5252096 mmcblk0p17
179 8 1931264 mmcblk1
179 9 1930240 mmcblk1p1
# grep "mmcblk0" init.rc
mount rfs /dev/block/mmcblk0p13 /system check=no
mount rfs /dev/block/mmcblk0p13 /system check=no
mount rfs /dev/block/mmcblk0p13 /system ro remount
mount rfs /dev/block/mmcblk0p10 /efs nosuid nodev check=no
# mount rfs /dev/block/mmcblk0p16 /data nosuid nodev check=no
mount rfs /dev/block/mmcblk0p16 /data nosuid nodev crypt check=no
mount rfs /dev/block/mmcblk0p14 /dbdata nosuid nodev crypt check=no
#mount rfs /dev/block/mmcblk0p14 /dbdata nosuid nodev check=no
mount rfs /dev/block/mmcblk0p15 /cache nosuid nodev check=no
mount j4fs /dev/block/mmcblk0p9 /mnt/.lfs
# 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
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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p13 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p10 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p16 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p14 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p15 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p9 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/259:9 /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 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd 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 0 0
/dev/block/vold/179:9 /mnt/secure/asec 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 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
no mtd in /proc
I also found that there is no /proc/mtd which makes it hard to figure out which mount points are the boot and recovery images.
Code:
# ls /proc/
param
rfs
last_kmsg
batt_info_proc
uid_stat
pvr
apm
sysrq-trigger
partitions
diskstats
crypto
kpageflags
kpagecount
kmsg
softirqs
version
uptime
stat
meminfo
loadavg
interrupts
devices
cpuinfo
cmdline
locks
filesystems
vmallocinfo
zoneinfo
vmstat
pagetypeinfo
buddyinfo
kallsyms
modules
timer_list
iomem
ioports
execdomains
sched_debug
cpu
asound
scsi
misc
fb
wakelocks
irq
cgroups
sys
bus
tty
driver
fs
sysvipc
net
mounts
self
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
37
38
39
40
41
42
49
51
52
53
54
55
56
57
58
59
60
61
62
64
67
68
69
71
72
73
74
75
76
77
78
79
80
84
86
87
91
93
100
120
199
207
212
213
217
234
276
309
419
557
566
574
695
995
1391
1409
2159
5135
5769
8293
8301
9704
10957
10959
10973
14462
14493
21343
32673
YP-G70 - 3 boot logos... wtf?
I successfully flashed the boot logo and replaced the animated boot logo but there is still a samsung boot logo showing up on this device.
When I boot I see my custom boot logo which is written to param.lfs after modifying the name of the original logo.jpg to l0g0.jpg and reflashing via odin. Heimdell won't successfully flash this device although it can extract the pit file without problems.
The custom logo in /mnt/.lfs displays for about 2 seconds then I see the original "samsung" logo for about 5 seconds then I see the custom boot animation.
I replaced the boot animation like this:
# cd /system/bin
# mv samsungani samsungloopani
# mv bootanimation samsungani
# reboot
I added my own custom boot animation "sanim.zip" to /system/media which plays just fine. Samsung have renamed bootanimation.zip to sanim.zip for no apparent reason.
I can't find any info anywhere about this mysterious third logo that shows up between the boot logo and the boot animation.
I found a logo file in /sbin/ called fota.png but it seems that it is not possible or at least undocumented on how to retrieve and edit the samsung "boot.img" to replace /sbin/fota.png with my own logo. Even if I did that I am not certain that it would solve the problem.
no one has any hints?
Turns out the "zImage" partition is located on /dev/block/mmcblk0p12
dd if=/dev/block/mmcblk0p12 of=/mnt/sdcard/zImage
dd if=/dev/block/mmcblk0p13 of=/mnt/sdcard/factoryfs.rfs
dd if=/dev/block/mmcblk0p9 of=/mnt/sdcard/param.lfs
hi i like ur thread
so can i change the
GT-S7500 Logo before boot animation

[Q] Extract recovery.img from your phone

Hey everyone,
I'm having trouble extracting a recovery.img from my phone. More specific I can't seem to find which file I have to 'dd' to create the img file.
Some commands with the output
Code:
[email protected]:/ # cat /proc/mtd
dev: size erasesize name
Code:
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/[email protected] /system ext4 ro,relatime,user_xattr,commit=1,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/179:97 /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:97 /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
/dev/block/vold/179:6 /mnt/sdcard2 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
Code:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 3792000 mmcblk0
179 1 1 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 524288 mmcblk0p3
179 4 524288 mmcblk0p4
179 5 2621440 mmcblk0p5
179 6 85216 mmcblk0p6
179 64 1024 mmcblk0boot1
179 32 1024 mmcblk0boot0
179 96 15110144 mmcblk1
179 97 15106048 mmcblk1p1
Code:
[email protected]:/ # cat /proc/emmc
partno: start_sect nr_sects partition_name
emmc_p1: 00000020 00000002 "ebr1"
emmc_p2: 0000ac40 00002800 "sec_ro"
emmc_p3: 00010740 00100000 "android"
emmc_p4: 00110f40 00100000 "cache"
emmc_p5: 00211740 00500000 "usrdata"
emmc_p6: 00711f40 000299c0 "fat"
Even by running the commands above I'm still not able to determine where I can extract a recovery.img.
Ive been looking around and can't seem to find anything so I hope someone can point me in the right direction.
PS: Phone in question is a Star B92M (chinaphone)
Thanks for the help!
~Whookid
EDIT: I'm looking for a way to do this without SP Flash tool
Is your phone rooted? If so, you can create a backup by using a script made available by our fellow Russian users from forum.china-iphone.ru. Give it a shot... here.
I've just remembered that you can also use MTK Droid Root & Tools for that.

[Q] cat /proc/mtd or emmc not working, EXT4 partitions, not YAFFS

A Chairde
Having a problem extracting partitions using DD ....
Start of the process involves either CAT /PROC/MTD or /PROC/EMMC , but neither command works .. they are not in /PROC directory , and no CAT commands I ran there give a similar output to types I got off different phones ...
Ran these commands, outputs below ... ls /dev/mtd/mtd* is not working ..... no such files ... anyone give me some help on this ?
[email protected]:/system/media # cat /proc/mounts
cat /proc/mounts
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
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/179:1 /mnt/extsd fuseblk rw,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
/dev/block/vold/93:72 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=asci
i,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:72 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset
=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]:/system/media # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
93 0 16384 nanda
93 8 16384 nandb
93 16 32768 nandc
93 24 393216 nandd
93 32 819200 nande
93 40 16384 nandf
93 48 32768 nandg
93 56 327680 nandh
93 64 131072 nandi
93 72 13762560 nandj
179 0 31166976 mmcblk0
179 1 31162880 mmcblk0p1
[email protected]:/system/media #

Size of partition

Regarding Pixel 32GB, I want to know the size of each partition(boot, system etc).
Please show below via adb shell.
cat /proc/partitions
ls -l /dev/block/platform/soc/7824900.sdhci/by-name
notice: "7824900.sdhci" is diffirent name folder.
Sorry, the following path is correct.
ls -l /dev/block/bootdevice/by-name
Can't list the /dev directory due to lack of permissions. Best I can give you is /proc/partitions:
Code:
sailfish:/ $ cat /proc/partitions
major minor #blocks name
254 0 524288 zram0
8 0 31145984 sda
8 1 512 sda1
8 2 512 sda2
8 3 512 sda3
8 4 512 sda4
8 5 2048 sda5
8 6 2048 sda6
8 7 512 sda7
8 8 512 sda8
8 9 512 sda9
8 10 512 sda10
8 11 512 sda11
8 12 512 sda12
8 13 256 sda13
8 14 256 sda14
8 15 256 sda15
259 0 256 sda16
259 1 4096 sda17
259 2 4096 sda18
259 3 32768 sda19
259 4 32768 sda20
259 5 32768 sda21
259 6 32768 sda22
259 7 128 sda23
259 8 128 sda24
259 9 71680 sda25
259 10 71680 sda26
259 11 256 sda27
259 12 256 sda28
259 13 256 sda29
259 14 256 sda30
259 15 307200 sda31
259 16 307200 sda32
259 17 2097152 sda33
259 18 2097152 sda34
259 19 26038272 sda35
259 20 4820 sda36
8 32 4096 sdc
8 33 4052 sdc1
8 16 4096 sdb
8 17 4052 sdb1
8 48 49152 sdd
8 49 1024 sdd1
8 50 8 sdd2
8 51 32768 sdd3
8 52 128 sdd4
8 53 4 sdd5
8 54 4 sdd6
8 55 1024 sdd7
8 56 4 sdd8
8 57 2048 sdd9
8 58 2048 sdd10
8 59 1024 sdd11
8 60 4 sdd12
8 61 9020 sdd13
8 64 36864 sde
8 65 512 sde1
8 66 6144 sde2
8 67 4096 sde3
8 68 2048 sde4
8 69 16384 sde5
8 70 7636 sde6
8 80 8192 sdf
8 81 16 sdf1
8 82 256 sdf2
8 83 2048 sdf3
8 84 4 sdf4
8 85 5824 sdf5
253 0 2064396 dm-0
253 1 302360 dm-1
Thank you so much for reply!
I have a another request.
Please show below via adb shell.
df
mount
tatsu_vel said:
Thank you so much for reply!
I have a another request.
Please show below via adb shell.
df
mount
Click to expand...
Click to collapse
Here you go:
sailfish:/ $ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 1999708 1484912 498412 75% /
tmpfs 1898468 440 1898028 1% /dev
tmpfs 1898468 0 1898468 0% /mnt
/dev/block/dm-1 292868 223040 63784 78% /vendor
/dev/block/bootdevice/by-name/userdata 25497924 8109564 17371976 32% /data
/dev/fuse 25497924 8109564 17371976 32% /storage/emulated
sailfish:/ $ mount
rootfs on / type rootfs (rw,seclabel)
/dev/root on / type ext4 (ro,seclabel,relatime,data=ordered)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1898468k,nr_inodes=474617,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
none on /dev/stune type cgroup (rw,relatime,schedtune)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,size=1898468k,nr_inodes=474617,mode=755,gid=1000)
none on /config type configfs (rw,relatime)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
none on /dev/cpuset type cgroup (rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent)
pstore on /sys/fs/pstore type pstore (rw,seclabel,relatime)
/dev/block/dm-1 on /vendor type ext4 (ro,seclabel,relatime,discard,data=ordered)
/dev/block/bootdevice/by-name/modem_a on /firmware/radio type vfat (ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/bootdevice/by-name/userdata on /data type ext4 (rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered)
/dev/block/bootdevice/by-name/persist on /persist type ext4 (rw,seclabel,nosuid,nodev,relatime,data=ordered)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,size=1898468k,nr_inodes=474617,mode=755,gid=1000)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/fuse on /mnt/runtime/default/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
Click to expand...
Click to collapse

Categories

Resources