[Q&A]Partitions list of Nokia x - Nokia X
Nokia X Partition
Partition - Mount - Alias
INTERNAL Storage
mmcblk0p16 - /persist - p16
mmcblk0p18 - /system - p18
mmcblk0p19 - /cache - p19
mmcblk0p21 -/storage/sdcard-p21
mmcblk0p22 -/data - p22
mmcblk0p23 -/variant - p23
mmcblk0p25 -/preload - p25
mmcblk0p3 - /bootloader - p3
mmcblk0p17 - /boot - p17
EXTERNAL STORAGE
mmcblk1p1 - /storage/sdcard1 - p1
mmcblkxpxx where XX is the number of the persist partition.
Rest of the blocks(XX) occupy little amount of space and by default they are NOT MOUNTED.
This post is only for knowledge purpose for those (ofcourse people like me,noob)who are confused or don't know the right partition for flashing
matrixex said:
can you help me i just wanted to flash Persist.img but don't know the partition
I'm currently on Jellybean 4.1.2 and
which partition i should choose i have tried
package_extract_file("pesrist.img", "/dev/block/platform/msm_sdcc.1/by-num/p1");
on updater script but results corrupted files in memory card
so please help me
thanks-matriex
Click to expand...
Click to collapse
A few points:
1) you have a typo in your command. You wrote pesrist instead of persist.
2) what device are you using?
3) try either this: package_extract_file("persist.img", "/dev/block/platform/msm_sdcc.1/by-name/persist");
or this, which I typically use:
package_extract_file("persist.img", "/tmp/persist.img");
run_program("/sbin/busybox", "dd", "if=/tmp/persist.img", "of=/dev/block/platform/msm_sdcc.1/by-name/persist");
delete("/tmp/persist.img");
efrant said:
A few points:
1) you have a typo in your command. You wrote pesrist instead of persist.
2) what device are you using?
3) try either this: package_extract_file("persist.img", "/dev/block/platform/msm_sdcc.1/by-name/persist");
or this, which I typically use:
package_extract_file("persist.img", "/tmp/persist.img");
run_program("/sbin/busybox", "dd", "if=/tmp/persist.img", "of=/dev/block/platform/msm_sdcc.1/by-name/persist");
delete("/tmp/persist.img");
Click to expand...
Click to collapse
Thanks
I am on Nokia x RM-980
I just flashed persist.img to persist
Partition but I flashed it in wrong partition "Dev/block/platform/msm_sdcc.1/by-num/p1"
After this my IMIE vanished
Again Thanks it is really pleasure to talk to a dev
matrixex said:
[snip]
Hey last question
fastboot -i 0x0421 flash persist persist.img
For flashing from adb this command is for my device
I found it on xda nokia x topic
But can you explain whay does 0x0421
Means
Click to expand...
Click to collapse
According to fastboot syntax, the "-i" option is for specifying a custom USB vendor ID, so 0x0421 is the USB vendor ID for your device. Are you using using Linux? I don't think it does anything on Windows.
Sent from my HTC One M9 using Tapatalk
efrant said:
According to fastboot syntax, the "-i" option is for specifying a custom USB vendor ID, so 0x0421 is the USB vendor ID for your device. Are you using using Linux? I don't think it on Windows
Click to expand...
Click to collapse
No I am on windows using fastboot.exe and adb.exe on a folder
efrant said:
A few points:
package_extract_file("persist.img", "/tmp/persist.img");
run_program("/sbin/busybox", "dd", "if=/tmp/persist.img", "of=/dev/block/platform/msm_sdcc.1/by-name/persist");
delete("/tmp/persist.img");
Click to expand...
Click to collapse
But there is no persist file or folder in my root(see attached img)
"Dev/block/platform/msm_sdcc.1/by-name/persist"
So I don't think your script will work for me
matrixex said:
But there is no persist file or folder in my root(see attached img)
"Dev/block/platform/msm_sdcc.1/by-name/persist"
So your code will work for me?
Instead this persist folder is located at root
(See 2nd attached img)
Click to expand...
Click to collapse
No, it will not work. You need to get the partition list to find out where to write the persist.img file. You can likely find it by searching, or you cun run "ls -lR /dev/block" from a terminal.
In any case, this is now off-topic, as it has nothing to do with edify syntax. I will move the relevant posts to the Nokia X section.
EDIT: Moved from Galaxy Nexus section.
efrant said:
No, it will not work. You need to get the partition list to find out where to write the persist.img file. You can likely find it by searching, or you cun run "ls -lR /dev/block" from a terminal.
In any case, this is now off-topic, as it has nothing to do with edify syntax. I will move the relevant posts to the Nokia X section.
EDIT: Moved from Galaxy Nexus section.
Click to expand...
Click to collapse
pls help me Cause I am noob.
I tried ls -lR /dev/block but I can't identify partitions
partitions List
[email protected]:/ $su
1|[email protected]:/ # ls -lR /dev/block
/dev/block:
brw------- root root 7, 0 2016-02-04 13:09 loop0
brw------- root root 7, 1 2016-02-04 13:09 loop1
brw------- root root 7, 2 2016-02-04 13:09 loop2
brw------- root root 7, 3 2016-02-04 13:09 loop3
brw------- root root 7, 4 2016-02-04 13:09 loop4
brw------- root root 7, 5 2016-02-04 13:09 loop5
brw------- root root 7, 6 2016-02-04 13:09 loop6
brw------- root root 7, 7 2016-02-04 13:09 loop7
brw------- root root 179, 0 2016-02-04 13:09 mmcblk0
brw------- root root 179, 1 2016-02-04 13:09 mmcblk0p1
brw------- root root 179, 10 2016-02-04 13:09 mmcblk0p10
brw------- root root 179, 11 2016-02-04 13:09 mmcblk0p11
brw------- root root 179, 12 2016-02-04 13:09 mmcblk0p12
brw------- root root 179, 13 2016-02-04 13:09 mmcblk0p13
brw------- root root 179, 14 2016-02-04 13:09 mmcblk0p14
brw------- root root 179, 15 2016-02-04 13:09 mmcblk0p15
brw------- root root 179, 16 2016-02-04 13:09 mmcblk0p16
brw------- root root 179, 17 2016-02-04 13:09 mmcblk0p17
brw------- root root 179, 18 2016-02-04 13:09 mmcblk0p18
brw------- root root 179, 19 2016-02-04 13:09 mmcblk0p19
brw------- root root 179, 2 2016-02-04 13:09 mmcblk0p2
brw------- root root 179, 20 2016-02-04 13:09 mmcblk0p20
brw------- root root 179, 21 2016-02-04 13:09 mmcblk0p21
brw------- root root 179, 22 2016-02-04 13:09 mmcblk0p22
brw------- root root 179, 23 2016-02-04 13:09 mmcblk0p23
brw------- root root 179, 24 2016-02-04 13:09 mmcblk0p24
brw------- root root 179, 25 2016-02-04 13:09 mmcblk0p25
brw------- root root 179, 26 2016-02-04 13:09 mmcblk0p26
brw------- root root 179, 3 2016-02-04 13:09 mmcblk0p3
brw------- root root 179, 4 2016-02-04 13:09 mmcblk0p4
Again thanks
matrixex said:
So here is my partitions generated by ls -lR /dev/block
export PATH=/data/local/bin:$PATH:.
[email protected]:/ $ export PATH=/data/local/bin:$PATH:.
[email protected]:/ $su
[email protected]:/ # ls -LR /dev/block
ls: Unknown option '-L'. Aborting.
1|[email protected]:/ # ls -lr /dev/block
ls: Unknown option '-r'. Aborting.
1|[email protected]:/ # ls -lR /dev/block
/dev/block:
brw------- root root 7, 0 2016-02-04 13:09 loop0
brw------- root root 7, 1 2016-02-04 13:09 loop1
brw------- root root 7, 2 2016-02-04 13:09 loop2
brw------- root root 7, 3 2016-02-04 13:09 loop3
brw------- root root 7, 4 2016-02-04 13:09 loop4
brw------- root root 7, 5 2016-02-04 13:09 loop5
brw------- root root 7, 6 2016-02-04 13:09 loop6
brw------- root root 7, 7 2016-02-04 13:09 loop7
brw------- root root 179, 0 2016-02-04 13:09 mmcblk0
brw------- root root 179, 1 2016-02-04 13:09 mmcblk0p1
brw------- root root 179, 10 2016-02-04 13:09 mmcblk0p10
brw------- root root 179, 11 2016-02-04 13:09 mmcblk0p11
brw------- root root 179, 12 2016-02-04 13:09 mmcblk0p12
brw------- root root 179, 13 2016-02-04 13:09 mmcblk0p13
brw------- root root 179, 14 2016-02-04 13:09 mmcblk0p14
brw------- root root 179, 15 2016-02-04 13:09 mmcblk0p15
brw------- root root 179, 16 2016-02-04 13:09 mmcblk0p16
brw------- root root 179, 17 2016-02-04 13:09 mmcblk0p17
brw------- root root 179, 18 2016-02-04 13:09 mmcblk0p18
brw------- root root 179, 19 2016-02-04 13:09 mmcblk0p19
brw------- root root 179, 2 2016-02-04 13:09 mmcblk0p2
brw------- root root 179, 20 2016-02-04 13:09 mmcblk0p20
brw------- root root 179, 21 2016-02-04 13:09 mmcblk0p21
brw------- root root 179, 22 2016-02-04 13:09 mmcblk0p22
brw------- root root 179, 23 2016-02-04 13:09 mmcblk0p23
brw------- root root 179, 24 2016-02-04 13:09 mmcblk0p24
brw------- root root 179, 25 2016-02-04 13:09 mmcblk0p25
brw------- root root 179, 26 2016-02-04 13:09 mmcblk0p26
brw------- root root 179, 3 2016-02-04 13:09 mmcblk0p3
brw------- root root 179, 4 2016-02-04 13:09 mmcblk0p4
brw------- root root 179, 5 2016-02-04 13:09 mmcblk0p5
brw------- root root 179, 6 2016-02-04 13:09 mmcblk0p6
brw------- root root 179, 7 2016-02-04 13:50 mmcblk0p7
brw------- root root 179, 8 2016-02-04 14:11 mmcblk0p8
brw------- root root 179, 9 2016-02-04 13:09 mmcblk0p9
brw------- root root 179, 32 2016-02-04 13:09 mmcblk1
brw------- root root 179, 33 2016-02-04 13:09 mmcblk1p1
drwxr-xr-x root root 2016-02-04 13:09 platform
drwx------ root root 2016-02-04 13:09 vold
brw------- root root 253, 0 2016-02-04 13:09 zram0
/dev/block/platform:
drwxr-xr-x root root 2016-02-04 13:09 msm_sdcc.1
drwxr-xr-x root root 2016-02-04 13:09 msm_sdcc.3
/dev/block/platform/msm_sdcc.1:
drwxr-xr-x root root 2016-02-04 13:09 by-num
lrwxrwxrwx root root 2016-02-04 13:09 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root 2016-02-04 13:09 mmcblk1p1 -> /dev/block/mmcblk1p1
/dev/block/platform/msm_sdcc.1/by-num:
lrwxrwxrwx root root 2016-02-04 13:09 p1 -> /dev/block/mmcblk1p1
/dev/block/platform/msm_sdcc.3:
drwxr-xr-x root root 2016-02-04 13:09 by-num
lrwxrwxrwx root root 2016-02-04 13:09 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx root root 2016-02-04 13:09 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-02-04 13:09 mmcblk0p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-02-04 13:09 mmcblk0p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-02-04 13:09 mmcblk0p12 -> /dev/blo
Can you explain which is persist partition
And it will be grateful if you explain some information about other
Partitions like system,boot etc
Again thanks
Click to expand...
Click to collapse
Hmmm. Someone else more knowledgeable on Nokia devices will have to chime in. In all the other Android devices I've used, the name of the partition is shown along with the number. In this case, it only shows the number.
You'll need to ask someone (maybe one of the devs that worked on a custom recovery) which number the persist partition is. Then just use this command from terminal (with a root prompt and persist.img saved in /sdcard or whatever folder you choose):
dd if=/sdcard of=/dev/block/mmcblk0pXX where XX is the number of the persist partition.
Or you could use an edify script in recovery:
package_extract_file("persist.img", "/tmp/persist.img");
run_program("/sbin/busybox", "dd", "if=/tmp/persist.img", "of=/dev/block/mmcblk0pXX");
delete("/tmp/persist.img");
But sorry, I can't help you with the number of the persist partition because I have no idea. The info might be in the forums somewhere (need to search or ask someone).
Hi
Finally I found it ,partitions just see 1st post
efrant said:
According to fastboot syntax, the "-i" option is for specifyina custom USB vendor ID, so 0x0421 is the USB vendor ID for your device. Are you using using Linux? I don't think it does anything on Windows.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Hi
Can you please delete all the post here I don't want it anymore
I have got answers so please delete this thread
matrixex said:
Hi
Can you please delete all the post here I don't want it anymore
I have got answers so please delete this thread
Click to expand...
Click to collapse
We typically don't delete threads - - if we delete this thread, it would make it difficult for someone having the same issue as you did.
You found the solution, and by posting here, you are helping others.
Sent from my HTC One M9 using Tapatalk
efrant said:
We typically don't delete threads - - if we delete this thread, it would make it difficult for someone having the same issue as you did.
You found the solution, and by posting here, you are helping others.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Sorry for the comment instead of this I will continue to post my resources as I dig
Related
[SC-03D] Japan NTT DoCoMo Galaxy S II LTE Users plus FAQ
This is a thread for Docomo's Galaxy S II LTE. Its model number is SC-03D. FAQ in progress... Q. Tell me about this phone. A. This phone was released 2011-11-24 in Japan by Docomo. nttdocomo.co.jp/product/next/sc03d/ ja.wikipedia.org/wiki/SC-03D Q. What phones is the SC-03D similar to? A. It appears to be similar to the AT&T Samsung Galaxy S II Skyrocket (SGH-I727) and T-Mobile Samsung Galaxy S II SGH-T989 (both SGSII phones with 4G support). Other than the modem/baseband, it is also probably similar to the Epic 4G Touch. Q. What is the model number: A. SC-03D Q. What is the stock Android version? A. 2.3.6 Q. What is the stock baseband version? A. SC03DOMKK3 Q. What is the stock kernel version? A. [email protected] #2 Q. What is the build number? A. GINGERBREAD.OMKK3 Q. Let's get our hands dirty. Tell me a little about the mounted filesystems. A. Okay, but you asked for it... Here are the mounted filesystems. Code: # mount rootfs / rootfs ro,relatime 0 0 tmpfs /dev tmpfs rw,relatime,mode=111 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 none /dev/cpuctl cgroup rw,relatime,cpu 0 0 /dev/block/mmcblk0p24 /system ext4 ro,relatime,barrier=0,data=ordered 0 0 /dev/block/mmcblk0p26 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0 /dev/block/mmcblk0p21 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0 /dev/block/mmcblk0p25 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0 /dev/block/mmcblk0p13 /system/etc/firmware/misc vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0 /dev/block/mmcblk0p17 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0 /dev/block/mmcblk0p27 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0 /dev/block/vold/179:28 /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 /dev/block/vold/179:33 /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:33 /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 /dev/block/dm-0 /mnt/asec/com.metago.astro-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 # Here is the size of the filesystems (keep in mind I've installed a few applications, so these sizes are very slightly bigger than they would be on a new phone). Code: # df Filesystem Size Used Free Blksize /dev 380M 76K 380M 4096 /mnt/asec 380M 0K 380M 4096 /mnt/obb 380M 0K 380M 4096 /mnt/usb 380M 0K 380M 4096 /system 698M 588M 110M 4096 /cache 297M 10M 286M 4096 /efs 9M 4M 5M 4096 /data 1G 214M 1G 4096 /system/etc/firmware/misc 199M 21M 178M 4096 /system/etc/firmware/misc_mdm 199M 26M 173M 4096 /tombstones 68M 4M 64M 4096 /mnt/sdcard 11G 92M 11G 16384 /mnt/sdcard/external_sd 29G 140M 29G 32768 /mnt/secure/asec 29G 140M 29G 32768 /mnt/asec/com.metago.astro-1 3M 1M 1M 4096 # Here is a listing of the block devices on the phone. There's a lot... Code: # ls -l -a /dev/block/ brw------- root root 179, 17 2011-11-27 12:41 mmcblkOp17 brw------- root root 179, 13 2011-11-27 12:41 mmcblkOp13 brw------- root root 179, 23 2011-11-27 12:41 mmcblkOp23 brw------- root root 179, 8 2011-11-27 12:41 mmcblkOp8 brw------- root root 254, 0 2011-11-26 00:56 dm-0 drwxr-xr-x root root 2011-11-26 00:56 vold brw------- root root 179, 33 2011-11-26 00:56 mmcblk1p1 brw------- root root 179, 32 2011-11-26 00:56 mmcblk1 brw------- root root 7, 7 2011-11-26 00:56 loop7 ... brw------- root root 1, 0 2011-11-26 00:56 ram0 brw------- root root 179, 28 2011-11-26 00:56 mmcblk0p28 brw------- root root 179, 27 2011-11-26 00:56 mmcblk0p27 brw------- root root 179, 26 2011-11-26 00:56 mmcblk0p26 brw------- root root 179, 25 2011-11-26 00:56 mmcblk0p25 brw------- root root 179, 24 2011-11-26 00:56 mmcblk0p24 brw------- root root 179, 23 2011-11-26 00:56 mmcblk0p23 brw------- root root 179, 22 2011-11-26 00:56 mmcblk0p22 brw-rw---- system system 179, 21 2011-11-26 00:56 mmcblk0p21 brw-rw---- system system 179, 20 2011-11-26 00:56 mmcblk0p20 brw-rw---- system system 179, 19 2011-11-27 16:06 mmcblk0p19 brw------- root root 179, 18 2011-11-27 17:06 mmcblk0p18 brw------- root root 179, 17 2011-11-26 00:56 mmcblk0p17 brw------- root root 179, 16 2011-11-26 00:56 mmcblk0p16 brw------- root root 179, 15 2011-11-26 19:07 mmcblk0p15 brw------- root root 179, 14 2011-11-26 00:56 mmcblk0p14 brw------- root root 179, 13 2011-11-26 00:56 mmcblk0p13 brw-rw---- root radio 179, 12 2011-11-26 00:56 mmcblk0p12 brw------- root root 179, 11 2011-11-26 00:56 mmcblk0p11 brw------- root root 179, 10 2011-11-26 00:56 mmcblk0p10 brw------- root root 179, 9 2011-11-26 00:56 mmcblk0p9 brw------- root root 179, 8 2011-11-26 00:56 mmcblk0p8 brw------- root root 179, 7 2011-11-26 00:56 mmcblk0p7 brw------- root root 179, 6 2011-11-26 00:56 mmcblk0p6 brw------- root root 179, 5 2011-11-26 00:56 mmcblk0p5 brw------- root root 179, 4 2011-11-26 00:56 mmcblk0p4 brw------- root root 179, 3 2011-11-26 00:56 mmcblk0p3 brw------- root root 179, 2 2011-11-26 00:56 mmcblk0p2 brw------- root root 179, 1 2011-11-26 00:56 mmcblk0p1 drwxr-xr-x root root 2011-11-26 00:56 platform br--r----- system system 179, 0 2011-11-26 00:56 mmcblk0 # Dumping the block images allows us to see their size. Code: $ ls -l image sizes 104857600 -- dev-block-mmcblk0p1.img 512000 -- dev-block-mmcblk0p2.img 1536000 -- dev-block-mmcblk0p3.img 1024 -- dev-block-mmcblk0p4.img 512000 -- dev-block-mmcblk0p5.img 2097152 -- dev-block-mmcblk0p6.img 2560000 -- dev-block-mmcblk0p7.img 10485760 -- dev-block-mmcblk0p8.img 512000 -- dev-block-mmcblk0p9.img 512000 -- dev-block-mmcblk0p11.img 10485760 -- dev-block-mmcblk0p12.img 102760448 -- dev-block-mmcblk0p13_system_etc_firmware_misc.img 3145728 -- dev-block-mmcblk0p14.img 3145728 -- dev-block-mmcblk0p15.img 3145728 -- dev-block-mmcblk0p16.img 102760448 -- dev-block-mmcblk0p17_system_etc_firmware_misc_mdm.img 3145728 -- dev-block-mmcblk0p18.img 3145728 -- dev-block-mmcblk0p19.img 3145728 -- dev-block-mmcblk0p20.img 10485760 -- dev-block-mmcblk0p21_efs.img 10485760 -- dev-block-mmcblk0p22.img 10485760 -- dev-block-mmcblk0p23.img 744488960 -- dev-block-mmcblk0p24_system.img 2149580800 -- dev-block-mmcblk0p25_data.img 316669952 -- dev-block-mmcblk0p26_cache.img 135266304 -- dev-block-mmcblk0p27_tombstones.img $ ls -lh image sizes 100M -- dev-block-mmcblk0p1.img 500K -- dev-block-mmcblk0p2.img 1.5M -- dev-block-mmcblk0p3.img 1.0K -- dev-block-mmcblk0p4.img 500K -- dev-block-mmcblk0p5.img 2.0M -- dev-block-mmcblk0p6.img 2.5M -- dev-block-mmcblk0p7.img 10M -- dev-block-mmcblk0p8.img 500K -- dev-block-mmcblk0p9.img 500K -- dev-block-mmcblk0p11.img 10M -- dev-block-mmcblk0p12.img 98M -- dev-block-mmcblk0p13_system_etc_firmware_misc.img 3.0M -- dev-block-mmcblk0p14.img 3.0M -- dev-block-mmcblk0p15.img 3.0M -- dev-block-mmcblk0p16.img 98M -- dev-block-mmcblk0p17_system_etc_firmware_misc_mdm.img 3.0M -- dev-block-mmcblk0p18.img 3.0M -- dev-block-mmcblk0p19.img 3.0M -- dev-block-mmcblk0p20.img 10M -- dev-block-mmcblk0p21_efs.img 10M -- dev-block-mmcblk0p22.img 10M -- dev-block-mmcblk0p23.img 710M -- dev-block-mmcblk0p24_system.img 2.1G -- dev-block-mmcblk0p25_data.img 302M -- dev-block-mmcblk0p26_cache.img 129M -- dev-block-mmcblk0p27_tombstones.img $ Q. Anything else important? A. None of the images are completely empty, and dev-block-mmcblk0p16.img is identical to dev-block-mmcblk0p20.img. Q. Which block image maps to what? A. I'm not sure. Looking at the `mount` output, it's obvious that mmcblk0p21 is /efs, mmcblk0p13 is /system/etc/firmware/misc, mmcblk0p17 is /system/etc/firmware/misc_mdm, mmcblk0p24 is /system, mmcblk0p25 is /data, mmcblk0p26 is /cache, and mmcblk0p27 is /tombstones. As far as Heimdall-related things like boot.img, recovery.img, etc... it has not been determined. I believe on the Epic 4g Touch, mmcblock0p8 contains boot.img and mmcblk0p22 contains recovery.img. These are probably the same. What is the kernel (zImage)...? forum.xda-developers.com/showpost.php?p=19269788&postcount=7 The modem is probably mmcblk0p17 because it is mounted on /system/etc/firmware/misc_mdm or mmcblk0p13 because it is mounted on /system/etc/firmware/misc. Q. How do I enter download mode and recovery mode? A. Recovery mode can be entered by holding down both the volume DOWN and volume UP buttons at the same time when pressing the power button. The phone should vibrate once. It is then alright to release the power button. Download mode can be entered two ways. One way is to just hold down the volume DOWN button when turning on the phone like above. The other way is to remove the battery from the phone and connect the phone to a usb port (or the phone charger). While it is connected hold down volume DOWN. It should go into download mode without even having to press the power button. Q. I want to void my warranty. How can I root my phone? A. You can use the zergrush exploit. (Windows program, I think...) xda-developers.com/showthread.php?t=1320350 (exploit runnable on the device for advanced users) xda-developers.com/showthread.php?t=1296916 (In order to run the binary, put it in /data/local/tmp. It is world-writable. /sdcard and /sdcard/external_sd are mounted noexec, so the binary cannot be run from there.) (exploit source code) github.com/revolutionary/zergRush Q. Post the stock kernel config? A. I have attached it to this post. Q. How can I get my phone back to stock? A. There is currently no way to get the phone back to stock yet. But I have created an odin package that contains stock boot.img (/dev/block/mmcblk0p8), stock recovery.img (/dev/block/mmcblk0p22), and /system plus `su` and `busybox` (/dev/block/mmcblk0p24). WARNING: this has not been tested, so it may brick your phone: Here is a package that is flashable using ODIN: 72.13.95.4/sc03dsmallkernelstockrootimg.tar.gz gunzip it and then flash it with ODIN. It may also be wise to add the md5sum to the end of the tar (`md5sum -t sc03smallkernelstockrootimg.tar >> sc03smallkernelstockrootimg.tar ; mv sc03smallkernelstockrootimg.tar sc03smallkernelstockrootimg.tar.md5`). Q. Help, my filesystem is corrupted! Help, the emmc is corrupted! Help, everything on /block/mmcblk0 is corrupted! A. Try doing a factory reset in the recovery mode. It may not work if you are using ClockWorkMod, so you may need to flash the stock recovery image. If that doesn't work, try the stock recovery image for the TMobile Galaxy S II 4G. Q. I feel like I've seen this thread somewhere else? A. You have, sort of. I'm trying to base this thread off of the thread about the non-LTE Docomo Samsung Galaxy S II: forum.xda-developers.com/showthread.php?t=1126190
What does this have to do with the Epic Touch Sent from the future.
SocialReject said: What does this have to do with the Epic Touch Click to expand... Click to collapse The SC-03D is (probably)techinally very similar to the Epic 4G Touch. This phone (probably) won't be able to use ROMs for the normal SGSII, but may be able to use ROMs for the 4G version of SGSII. I thought this forum would be the best place for this thread, but perhaps it belongs in the Galaxy S II General forum? Is there a Galaxy S II 4G General forum?
cdep.illabout said: The SC-03D is (probably)techinally very similar to the Epic 4G Touch. This phone (probably) won't be able to use ROMs for the normal SGSII, but may be able to use ROMs for the 4G version of SGSII. I thought this forum would be the best place for this thread, but perhaps it belongs in the Galaxy S II General forum? Is there a Galaxy S II 4G General forum? Click to expand... Click to collapse The LTE S2's are actually Qualcomm chipsets, so that phone is more like the AT&T Skyrocket & T-mobile versions than ours.
Maybe ur confusing wimax with LTE. I'd consider the skyrocket Sent from my SPH-D710 using XDA App
Calkulin said: The LTE S2's are actually Qualcomm chipsets, so that phone is more like the AT&T Skyrocket & T-mobile versions than ours. Click to expand... Click to collapse Okay, sorry for the confusion. Let me message a moderator and try to get this thread moved to the T-Mobile Samsung Galaxy S II SGH-T989 General forum... edit: Just sent jerdog (the moderator of this forum) a message asking for this thread to be moved
where am i supposed to get the drivers for windows 7 64 bit? i tried kies but it couldn't install all the drivers!
Calkulin said:
The LTE S2's are actually Qualcomm chipsets, so that phone is more like the AT&T Skyrocket & T-mobile versions than ours.
Click to expand...
Click to collapse
yup, the only difference really is the exterior shell which is a little bit more square than round, and has a HARD key + 2 capacitive buttons, instead of 4 capacitive buttons found in the American version of the phone
it's like the old I9000 super sized
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
fifo_thekid said: where am i supposed to get the drivers for windows 7 64 bit? i tried kies but it couldn't install all the drivers! Click to expand... Click to collapse I'm sorry, I'm not very familiar with Windows. In order to use Odin, I am running Windows XP in a VM on Linux. If you can't figure out your problem, try searching this forum or the AT&T Skyrocket forum for help with Odin and Kies.
lol that's exactly what i've done yesterday
back on topic there's additional info in Wikipedia that points the same http://en.wikipedia.org/wiki/Snapdragon_(system_on_chip) HP TouchPad, T-Mobile Galaxy S II, Galaxy S II Skyrocket, HTC Vivid, NTT DoCoMo, Galaxy S II LTE, LG Nitro HD Click to expand... Click to collapse basically all the Apps/Games running on those devices should be compatible with each other and here's a side by side compare from gsmarena http://www.gsmarena.com/compare.php3?idPhone1=4129&idPhone2=4124
Calkulin said: The LTE S2's are actually Qualcomm chipsets, so that phone is more like the AT&T Skyrocket & T-mobile versions than ours. Click to expand... Click to collapse Hi, I've just bought a Korean Galaxy S2 4G LTE (SHV-E110S) he looks exactly like the japaneese LTE, and have the same specifications. Do you things that the roms of skyrocket works on it?
you will need to extract the stock kernel, of the SHV-E110S or SC-03D, make a full nandroid backup install CWR then flash the ROM you want, and flash back the stock Kernel and possibly other minor updates/fixes there's a good guide over at the Skyrocket forum about how to use Tmo ROMs on ATT Skyrocket, so just replace all those steps with the Korean / Japan version http://forum.xda-developers.com/showthread.php?t=1337311
thank you for the quick reply. I have a small problem, I don't know if it's the right place to ask, this morning I flashed CW recovery and the capacitive touches dosen't work anymore, if I find the stock kernel it would resolve my pb? AllGamer said: you will need to extract the stock kernel, of the SHV-E110S or SC-03D Click to expand... Click to collapse How I extract the stock kernel? PS: I Can't send donations because of my country money regulation but if you come in Tunis I'll be happy to pay you a coffe
Same thing happened to me However, after restarting two three times it worked again. Albeit, without haptic feedback
Are you guys flashing on t989? Sent from my SGH-T989 using XDA App
Are there any stock roms for this phone Sent from my 丅-爪◯阝工しモ ム丹し丹メㄚ ち 工工 w/ Cyanogen Mod 7.2 ツ using XDA Premium App
Does this have Swype in Japanese? If there is...is there anyway to port it in the languages for our Swype keyboard for the languages?
fifo_thekid said: Same thing happened to me However, after restarting two three times it worked again. Albeit, without haptic feedback Click to expand... Click to collapse I'm in the korean version and I restarted many times but nothing changes, when I enter the recovrery and when I have the message "back menu button disabled" the recovery freezes! I think that there is a compatibility problem or something like, so I want to find the original recovery for my phone but I didn't found it I tried to change the touch key light duration just to see if something happens, but the delay never changes, the keys lights at the same time of the screen
I found the original firmware of the E110S in a chinese forum and I flashed it with odin but the capacitive touches still don't work any help? PS: if someone is searching for the firmware I posted the link http://115.com/file/cljkbns3#
[Q] reset flash counter (Galaxy Grand Korea Version)
Hello Everyone. I am using Galaxy Grand ( Korea Model SHW-E270K ). I want to reset flash counter, but Triangle Away is not supported by device. so I want manually Reset flash counter, but i Can't find galaxy grand's flash counter partition.. How can i find flash counter partitions?..T.T please help.. Also, I get /dev/block/mmcblk0p4 (PARAM) and extract param.img .. but param is not contains about flash counter files. maybe BOTA0 or BOTA1 has flash counter files.. but i can't extract files.. here is partition Info. I Attached Triangle Away Dump File (log or other info) brw------- root root 254, 0 2013-08-08 00:21 dm-0 brw------- root root 7, 0 2013-08-08 00:21 loop0 brw------- root root 7, 1 2013-08-08 00:21 loop1 brw------- root root 7, 2 2013-08-08 00:21 loop2 brw------- root root 7, 3 2013-08-08 00:21 loop3 brw------- root root 7, 4 2013-08-08 00:21 loop4 brw------- root root 7, 5 2013-08-08 00:21 loop5 brw------- root root 7, 6 2013-08-08 00:21 loop6 brw------- root root 7, 7 2013-08-08 00:21 loop7 brw------- root root 179, 0 2013-08-08 00:21 mmcblk0 brw------- root root 179, 1 2013-08-08 00:21 mmcblk0p1 brw------- root root 179, 10 2013-08-08 00:21 mmcblk0p10 brw------- root root 179, 11 2013-08-08 00:21 mmcblk0p11 brw------- root root 179, 12 2013-08-08 00:21 mmcblk0p12 brw------- root root 179, 2 2013-08-08 00:21 mmcblk0p2 brw------- root root 179, 3 2013-08-08 00:21 mmcblk0p3 brw-rw---- system root 179, 4 2013-08-08 00:22 mmcblk0p4 brw------- root root 179, 5 2013-08-08 00:21 mmcblk0p5 brw------- root root 179, 6 2013-08-08 00:21 mmcblk0p6 brw-rw---- system radio 179, 7 2013-08-08 00:21 mmcblk0p7 brw------- root root 179, 8 2013-08-08 00:21 mmcblk0p8 brw------- root root 179, 9 2013-08-08 00:21 mmcblk0p9 brw------- root root 179, 16 2013-08-08 00:21 mmcblk1 brw------- root root 179, 17 2013-08-08 00:21 mmcblk1p1 lrwxrwxrwx root root 2013-08-08 00:21 param -> /dev/block/mmcbl k0p4 drwxr-xr-x root root 2013-08-08 00:21 platform brw------- root root 1, 0 2013-08-08 00:21 ram0 brw------- root root 1, 1 2013-08-08 00:21 ram1 brw------- root root 1, 10 2013-08-08 00:21 ram10 brw------- root root 1, 11 2013-08-08 00:21 ram11 brw------- root root 1, 12 2013-08-08 00:21 ram12 brw------- root root 1, 13 2013-08-08 00:21 ram13 brw------- root root 1, 14 2013-08-08 00:21 ram14 brw------- root root 1, 15 2013-08-08 00:21 ram15 brw------- root root 1, 2 2013-08-08 00:21 ram2 brw------- root root 1, 3 2013-08-08 00:21 ram3 brw------- root root 1, 4 2013-08-08 00:21 ram4 brw------- root root 1, 5 2013-08-08 00:21 ram5 brw------- root root 1, 6 2013-08-08 00:21 ram6 brw------- root root 1, 7 2013-08-08 00:21 ram7 brw------- root root 1, 8 2013-08-08 00:21 ram8 brw------- root root 1, 9 2013-08-08 00:21 ram9 drwx------ root root 2013-08-08 00:21 vold lrwxrwxrwx root root 2013-08-08 00:21 BOOT -> /dev/block/mmcblk 0p5 lrwxrwxrwx root root 2013-08-08 00:21 BOTA0 -> /dev/block/mmcbl k0p1 lrwxrwxrwx root root 2013-08-08 00:21 BOTA1 -> /dev/block/mmcbl k0p2 lrwxrwxrwx root root 2013-08-08 00:21 CACHE -> /dev/block/mmcbl k0p8 lrwxrwxrwx root root 2013-08-08 00:21 EFS -> /dev/block/mmcblk0 p3 lrwxrwxrwx root root 2013-08-08 00:21 HIDDEN -> /dev/block/mmcb lk0p10 lrwxrwxrwx root root 2013-08-08 00:21 OTA -> /dev/block/mmcblk0 p11 lrwxrwxrwx root root 2013-08-08 00:21 PARAM -> /dev/block/mmcbl k0p4 lrwxrwxrwx root root 2013-08-08 00:21 RADIO -> /dev/block/mmcbl k0p7 lrwxrwxrwx root root 2013-08-08 00:21 RECOVERY -> /dev/block/mm cblk0p6 lrwxrwxrwx root root 2013-08-08 00:21 SYSTEM -> /dev/block/mmcb lk0p9 lrwxrwxrwx root root 2013-08-08 00:21 USERDATA -> /dev/block/mm cblk0p12 major minor #blocks name 7 0 35375 loop0 179 0 7634944 mmcblk0 179 1 4096 mmcblk0p1 179 2 4096 mmcblk0p2 179 3 20480 mmcblk0p3 179 4 8192 mmcblk0p4 179 5 8192 mmcblk0p5 179 6 8192 mmcblk0p6 179 7 32768 mmcblk0p7 179 8 1048576 mmcblk0p8 179 9 2097152 mmcblk0p9 179 10 614400 mmcblk0p10 179 11 8192 mmcblk0p11 179 12 3772416 mmcblk0p12 179 16 7772160 mmcblk1 179 17 7771136 mmcblk1p1 254 0 35374 dm-0 Thanks.
Developer infos
Let's collect and share some developer relevant infos about the h60. KERNEL TOOLBOX: http://forum.xda-developers.com/honor-6/orig-development/honor-6-kernel-toolbox-t3011000 Latest kernel sources and various stock ramdisks included. Kernel sources for L01, L02, L03, L11, L12 and L21 are identical. L04 doesn't boot using a kernel built from sources from above variants. Seems to be different. Code: Kernel address 0x608000 Ramdisk address 0x300000 Secondary address 0x1500000 Kernel tags address 0x200000 Flash page size 2048 Command line "vmalloc=384M [email protected] psci=enable mmcparts=mmcblk0:p1(vrl),p2(vrl_backup),p7(modemnvm_factory),p18(splash),p22(dfx),p23(modemnvm_backup),p24(modemnvm_img),p25(modemnvm_system),p26(modem),p27(modem_dsp),p28(modem_om),p29(modemnvm_update),p30(3rdmodem),p31(3rdmodemnvm),p32(3rdmodemnvmbkp)" Base: 0x00000000 || 0x001FFF00 Kernel offset: 0x00608000 || 0x00408100 Ramdisk offset: 0x00300000 || 0x00100100 Second offset: 0x01500000 || 0x00D00100 Tags offset: 0x00200000 || 0x00000100 RIL: libbalong-ril.so and libbalong-ril-1.so are different across variants. Everything else is identical. SYSTEM: build.prop - 6.94 KB from H60-L02V100R001CHNC00B310 PARTITIONS: Code: ls -al /dev/block/platform/ff1fe000.dwmmc0/by-name lrwxrwxrwx root root 2015-01-16 16:33 3rdmodem -> /dev/block/mmcblk0p30 lrwxrwxrwx root root 2015-01-16 16:33 3rdmodemnvm -> /dev/block/mmcblk0p31 lrwxrwxrwx root root 2015-01-16 16:33 3rdmodemnvmbkp -> /dev/block/mmcblk0p32 lrwxrwxrwx root root 2015-01-16 16:33 boot -> /dev/block/mmcblk0p13 lrwxrwxrwx root root 2015-01-16 16:33 cache -> /dev/block/mmcblk0p38 lrwxrwxrwx root root 2015-01-16 16:33 cust -> /dev/block/mmcblk0p36 lrwxrwxrwx root root 2015-01-16 16:33 dfx -> /dev/block/mmcblk0p22 lrwxrwxrwx root root 2015-01-16 16:33 dts -> /dev/block/mmcblk0p20 lrwxrwxrwx root root 2015-01-16 16:33 fastboot -> /dev/block/mmcblk0p4 lrwxrwxrwx root root 2015-01-16 16:33 fw_hifi -> /dev/block/mmcblk0p9 lrwxrwxrwx root root 2015-01-16 16:33 fw_lpm3 -> /dev/block/mmcblk0p5 lrwxrwxrwx root root 2015-01-16 16:33 hibench -> /dev/block/mmcblk0p8 lrwxrwxrwx root root 2015-01-16 16:33 hisitest0 -> /dev/block/mmcblk0p34 lrwxrwxrwx root root 2015-01-16 16:33 hisitest1 -> /dev/block/mmcblk0p35 lrwxrwxrwx root root 2015-01-16 16:33 misc -> /dev/block/mmcblk0p11 lrwxrwxrwx root root 2015-01-16 16:33 modem -> /dev/block/mmcblk0p26 lrwxrwxrwx root root 2015-01-16 16:33 modem_dsp -> /dev/block/mmcblk0p27 lrwxrwxrwx root root 2015-01-16 16:33 modem_om -> /dev/block/mmcblk0p28 lrwxrwxrwx root root 2015-01-16 16:33 modemnvm_backup -> /dev/block/mmcblk0p23 lrwxrwxrwx root root 2015-01-16 16:33 modemnvm_factory -> /dev/block/mmcblk0p7 lrwxrwxrwx root root 2015-01-16 16:33 modemnvm_img -> /dev/block/mmcblk0p24 lrwxrwxrwx root root 2015-01-16 16:33 modemnvm_system -> /dev/block/mmcblk0p25 lrwxrwxrwx root root 2015-01-16 16:33 modemnvm_update -> /dev/block/mmcblk0p29 lrwxrwxrwx root root 2015-01-16 16:33 nvme -> /dev/block/mmcblk0p6 lrwxrwxrwx root root 2015-01-16 16:33 oeminfo -> /dev/block/mmcblk0p16 lrwxrwxrwx root root 2015-01-16 16:33 recovery -> /dev/block/mmcblk0p14 lrwxrwxrwx root root 2015-01-16 16:33 recovery2 -> /dev/block/mmcblk0p15 lrwxrwxrwx root root 2015-01-16 16:33 reserved1 -> /dev/block/mmcblk0p3 lrwxrwxrwx root root 2015-01-16 16:33 reserved2 -> /dev/block/mmcblk0p12 lrwxrwxrwx root root 2015-01-16 16:33 secure_storage -> /dev/block/mmcblk0p21 lrwxrwxrwx root root 2015-01-16 16:33 sensorhub -> /dev/block/mmcblk0p17 lrwxrwxrwx root root 2015-01-16 16:33 splash -> /dev/block/mmcblk0p18 lrwxrwxrwx root root 2015-01-16 16:33 splash2 -> /dev/block/mmcblk0p33 lrwxrwxrwx root root 2015-01-16 16:33 splash3 -> /dev/block/mmcblk0p19 lrwxrwxrwx root root 2015-01-16 16:33 system -> /dev/block/mmcblk0p37 lrwxrwxrwx root root 2015-01-16 16:33 teeos -> /dev/block/mmcblk0p10 lrwxrwxrwx root root 2015-01-16 16:33 userdata -> /dev/block/mmcblk0p39 lrwxrwxrwx root root 2015-01-16 16:33 vrl -> /dev/block/mmcblk0p1 lrwxrwxrwx root root 2015-01-16 16:33 vrl_backup -> /dev/block/mmcblk0p2 Code: cat /proc/partitions major minor #blocks name 7 0 13545 loop0 7 1 49928 loop1 179 0 15267840 mmcblk0 179 1 128 mmcblk0p1 179 2 128 mmcblk0p2 179 3 1664 mmcblk0p3 179 4 1792 mmcblk0p4 179 5 256 mmcblk0p5 179 6 4096 mmcblk0p6 179 7 4096 mmcblk0p7 179 8 2048 mmcblk0p8 179 9 4096 mmcblk0p9 179 10 2048 mmcblk0p10 179 11 4096 mmcblk0p11 179 12 8192 mmcblk0p12 179 13 8192 mmcblk0p13 179 14 15360 mmcblk0p14 179 15 1024 mmcblk0p15 179 16 32768 mmcblk0p16 179 17 32768 mmcblk0p17 179 18 8192 mmcblk0p18 179 19 8192 mmcblk0p19 179 20 32768 mmcblk0p20 179 21 20480 mmcblk0p21 179 22 8192 mmcblk0p22 179 23 4096 mmcblk0p23 179 24 8192 mmcblk0p24 179 25 4096 mmcblk0p25 179 26 61440 mmcblk0p26 179 27 4096 mmcblk0p27 179 28 12288 mmcblk0p28 179 29 24576 mmcblk0p29 179 30 131072 mmcblk0p30 179 31 32768 mmcblk0p31 179 32 16384 mmcblk0p32 179 33 65536 mmcblk0p33 179 34 2048 mmcblk0p34 179 35 2048 mmcblk0p35 179 36 524288 mmcblk0p36 179 37 1572864 mmcblk0p37 179 38 262144 mmcblk0p38 179 39 12339200 mmcblk0p39 179 120 4096 mmcblk0rpmb 179 80 4096 mmcblk0boot1 179 40 4096 mmcblk0boot0 31 0 128 mtdblock0 31 1 128 mtdblock1 31 2 4096 mtdblock2 31 3 4096 mtdblock3 31 4 4096 mtdblock4 31 5 61440 mtdblock5 31 6 4096 mtdblock6 31 7 24576 mtdblock7 179 160 15646720 mmcblk1 179 161 15642624 mmcblk1p1 31 8 4096 mtdblock8 253 0 13545 dm-0 253 1 49927 dm-1
@codeworkx Very useful information for the developers...! Have you tried to build a CM. Or at least a cwm recovery...?
root-expert said: @codeworkx Very useful information for the developers...! Have you tried to build a CM. Or at least a cwm recovery...? Click to expand... Click to collapse 1st step: unpack stock boot image, repack it, boot it 2nd step: build kernel from sources, pack it with stock ramdisk, boot it 3rd step: start brewing cm
Just to make it clear. I don't own a honor 6 so i'll not do any development. It's up to the community. Had a look at their kernel sources and tried to build it. This is a pure mess. I've never seen such a chaos before.
Is it even worse than mtk? Sent from my H60-L02 using Tapatalk
Problem is that the community for this device is really small, at least the potential developer part of it. Additionally, I'm trying to build CM for it but damn is it a hassle as a newbie..
codeworkx said: Just to make it clear. I don't own a honor 6 so i'll not do any development. It's up to the community. Had a look at their kernel sources and tried to build it. This is a pure mess. I've never seen such a chaos before. Click to expand... Click to collapse Thanks very much for your interest!! I'm reading more guides about CM buildilng from source and I started to set up my computer. Than I signed on Github and I found your dir. I googled you before I'he found this thread: I'm really honored of Your concern about Honor 6! We started a petition too, in order to involve our community and devs and start the development of this device. Like @panamera2011 said, it would be really great if someone like you, began to support our work!
You're right, almost all developers continue to buy the same devices because with cpu Qualcom is easier to build rom cm
nrpetonr said: Is it even worse than mtk? Sent from my H60-L02 using Tapatalk Click to expand... Click to collapse for me it's all the same. mtk, rockchip, hisilicon.... their kernel sources are a pure accident und the community support is below zero. and it seems that huawei doesn't make it better.
panamera2011 said: You're right, almost all developers continue to buy the same devices because with cpu Qualcom is easier to build rom cm Click to expand... Click to collapse Maybe not easier, but there's documentation and sourcecode available. That's a huge difference.
codeworkx said: for me it's all the same. mtk, rockchip, hisilicon.... their kernel sources are a pure accident und the community support is below zero. and it seems that huawei doesn't make it better. Click to expand... Click to collapse What do you mean by pure accident ? As in really messy coding ?
Didn't have a close look at their code. The way the hisilocon drivers are organized is messy. And it seems they've copied parts of the userspace into the kernel. That stuff doesn't belong there. And they've copied samsungs exfat driver from one of the i9100 custom kernels. I'm not able to build the kernel with enabled balong modem stuff because of their mess.
codeworkx said: Didn't have a close look at their code. The way the hisilocon drivers are organized is messy. And it seems they've copied parts of the userspace into the kernel. That stuff doesn't belong there. And they've copied samsungs exfat driver from one of the i9100 custom kernels. I'm not able to build the kernel with enabled balong modem stuff because of their mess. Click to expand... Click to collapse Sounds like chaos as you described earlier.. Its too bad that things have been built this way. Would getting information from honor (aka huawei) help ? And if so what information would that be ? Honor is quite close to the community over on a French forum I'm a member of and they seem to be eager to make a good impression for their phones on the European market so I'm pretty sure they wouldn't mind sharing information as custom ROM development is quite a big deal for android devices and if they get into that their market shares would explode considering how well the phone has been doing so far..! What's missing is really this customisation ..!
Dervisk said: Sounds like chaos as you described earlier.. Its too bad that things have been built this way. Would getting information from honor (aka huawei) help ? And if so what information would that be ? Honor is quite close to the community over on a French forum I'm a member of and they seem to be eager to make a good impression for their phones on the European market so I'm pretty sure they wouldn't mind sharing information as custom ROM development is quite a big deal for android devices and if they get into that their market shares would explode considering how well the phone has been doing so far..! What's missing is really this customisation ..! Click to expand... Click to collapse I've already written a mail to huawei. let's see how it goes.
some more information. @codeworkx some more information to complete OP that user @spanorg could collect following that thread http://forum.xda-developers.com/showthread.php?t=2450045. http://pastebin.com/xSuphPVT http://pastebin.com/pwknz0FA i attached them in that post as zip cos pastebin is not eternal. xD
desalesouche said: @codeworkx some more information to complete OP that user @spanorg could collect following that thread http://forum.xda-developers.com/showthread.php?t=2450045. http://pastebin.com/xSuphPVT http://pastebin.com/pwknz0FA i attached them in that post as zip cos pastebin is not eternal. xD Click to expand... Click to collapse @desalesouche what model of Honor 6 uses? I use H60-L02
panamera2011 said: @desalesouche what model of Honor 6 uses? I use H60-L02 Click to expand... Click to collapse from what i know @spanorg use L02
just 4 info: the kernel sourcecode release from huawei is incomplete and broken. they didn't release needed tools which they've used to build the kernel and there are some missing vxworks headers. if you've managed to build a kernel, then baseband and audio will be dead. i've written a mail. let's see what happens.
Is it possible to built a cm version and use the available compiled kernel?
Julsen1985 said: Is it possible to built a cm version and use the available compiled kernel? Click to expand... Click to collapse yes, but radio and audio might be broken. can't say for sure. i've still no honor 6.
H815 System Dump Needed!
After flashing xposed 64bit the H815 will not boot. We need someone to dump the system partion so we have a way to restore system until kdz is available. After someone dumps and uploads the system.img we should just be able to flash via fastboot.
Mine is coming tomorrow. I'll gladly do it if you tell me how to dump it.
IlyaKol said: Mine is coming tomorrow. I'll gladly do it if you tell me how to dump it. Click to expand... Click to collapse Sure here's a guide.. http://forum.xda-developers.com/showthread.php?t=2450045 If you need help pm me
macdaddie87 said: Sure here's a guide.. http://forum.xda-developers.com/showthread.php?t=2450045 If you need help pm me Click to expand... Click to collapse I'm a system engineer (server support, etc.) so I should be able to handle it. Just needed to be pointed in the right direction. I shall post up tomorrow.
macdaddie87 said: After flashing xposed 64bit the H815 will not boot. We need someone to dump the system partion so we have a way to restore system until kdz is available. After someone dumps and uploads the system.img we should just be able to flash via fastboot. Click to expand... Click to collapse Scratch that, evidently root is only available for the EU H815 and mine is the Taiwan one, from what I know. I'll see if I get lucky somehow, but by the looks of it I won't be able to provide the dump since I can't achieve root.
Some help http://forum.xda-developers.com/g4/development/rom-docs-testrom-t3126728 Code: major minor #blocks name 253 0 721772 zram0 179 0 30535680 mmcblk0 179 1 88064 mmcblk0p1 179 2 512 mmcblk0p2 179 3 1024 mmcblk0p3 179 4 1024 mmcblk0p4 179 5 512 mmcblk0p5 179 6 512 mmcblk0p6 179 7 512 mmcblk0p7 179 8 2048 mmcblk0p8 179 9 1024 mmcblk0p9 179 10 512 mmcblk0p10 179 11 1024 mmcblk0p11 179 12 512 mmcblk0p12 179 13 512 mmcblk0p13 179 14 2048 mmcblk0p14 179 15 512 mmcblk0p15 179 16 512 mmcblk0p16 179 17 512 mmcblk0p17 179 18 512 mmcblk0p18 179 19 512 mmcblk0p19 179 20 512 mmcblk0p20 179 21 1536 mmcblk0p21 179 22 16384 mmcblk0p22 179 23 32768 mmcblk0p23 179 24 1536 mmcblk0p24 179 25 1536 mmcblk0p25 179 26 1536 mmcblk0p26 179 27 512 mmcblk0p27 179 28 512 mmcblk0p28 179 29 512 mmcblk0p29 179 30 2048 mmcblk0p30 179 31 512 mmcblk0p31 259 0 512 mmcblk0p32 259 1 512 mmcblk0p33 259 2 512 mmcblk0p34 259 3 2048 mmcblk0p35 259 4 4096 mmcblk0p36 259 5 49152 mmcblk0p37 259 6 40960 mmcblk0p38 259 7 40960 mmcblk0p39 259 8 8192 mmcblk0p40 259 9 8192 mmcblk0p41 259 10 32768 mmcblk0p42 259 11 47104 mmcblk0p43 259 12 10240 mmcblk0p44 259 13 4096 mmcblk0p45 259 14 4096 mmcblk0p46 259 15 4239360 mmcblk0p47 259 16 262144 mmcblk0p48 259 17 1261568 mmcblk0p49 259 18 24313856 mmcblk0p50 259 19 12271 mmcblk0p51 179 32 4096 mmcblk0rpmb DDR -> /dev/block/mmcblk0p30 aboot -> /dev/block/mmcblk0p8 abootbak -> /dev/block/mmcblk0p14 apdp -> /dev/block/mmcblk0p18 boot -> /dev/block/mmcblk0p38 cache -> /dev/block/mmcblk0p49 cust -> /dev/block/mmcblk0p48 devinfo -> /dev/block/mmcblk0p17 po -> /dev/block/mmcblk0p20 drm -> /dev/block/mmcblk0p40 eksst -> /dev/block/mmcblk0p33 encrypt -> /dev/block/mmcblk0p32 factory -> /dev/block/mmcblk0p43 fota -> /dev/block/mmcblk0p44 fsc -> /dev/block/mmcblk0p27 fsg -> /dev/block/mmcblk0p26 grow -> /dev/block/mmcblk0p51 hyp -> /dev/block/mmcblk0p6 hypbak -> /dev/block/mmcblk0p12 keystore -> /dev/block/mmcblk0p29 laf -> /dev/block/mmcblk0p37 limits -> /dev/block/mmcblk0p16 misc -> /dev/block/mmcblk0p22 modem -> /dev/block/mmcblk0p1 modemst1 -> /dev/block/mmcblk0p24 modemst2 -> /dev/block/mmcblk0p25 mpt -> /dev/block/mmcblk0p42 msadp -> /dev/block/mmcblk0p19 persist -> /dev/block/mmcblk0p23 pmic -> /dev/block/mmcblk0p2 pmicbak -> /dev/block/mmcblk0p10 raw_resources -> /dev/block/mmcblk0p45 raw_resourcesbak -> /dev/block/mmcblk0p46 rct -> /dev/block/mmcblk0p34 recovery -> /dev/block/mmcblk0p39 rpm -> /dev/block/mmcblk0p7 rpmbak -> /dev/block/mmcblk0p13 sbl1 -> /dev/block/mmcblk0p3 sbl1bak -> /dev/block/mmcblk0p9 sdi -> /dev/block/mmcblk0p5 sdibak -> /dev/block/mmcblk0p15 sec -> /dev/block/mmcblk0p31 sns -> /dev/block/mmcblk0p41 spare1 -> /dev/block/mmcblk0p21 spare2 -> /dev/block/mmcblk0p36 ssd -> /dev/block/mmcblk0p28 system -> /dev/block/mmcblk0p47 tz -> /dev/block/mmcblk0p4 tzbak -> /dev/block/mmcblk0p11 userdata -> /dev/block/mmcblk0p50
I can't unlock the BL as I'm a TW phone not an EU phone. Sorry OP.
Partition Layout for P20 lite
Code: HWANE:/ $ cat /proc/partitions major minor #blocks name 1 0 8192 ram0 1 1 8192 ram1 1 2 8192 ram2 1 3 8192 ram3 254 0 2293760 zram0 179 0 61071360 mmcblk0 179 1 256 mmcblk0p1 179 2 256 mmcblk0p2 179 3 256 mmcblk0p3 179 4 768 mmcblk0p4 179 5 4096 mmcblk0p5 179 6 4096 mmcblk0p6 179 7 6144 mmcblk0p7 179 8 65536 mmcblk0p8 179 9 4096 mmcblk0p9 179 10 4096 mmcblk0p10 179 11 8192 mmcblk0p11 179 12 4096 mmcblk0p12 179 13 32768 mmcblk0p13 179 14 2048 mmcblk0p14 179 15 2048 mmcblk0p15 179 16 2048 mmcblk0p16 179 17 14336 mmcblk0p17 179 18 32768 mmcblk0p18 179 19 65536 mmcblk0p19 179 20 2048 mmcblk0p20 179 21 24576 mmcblk0p21 179 22 61440 mmcblk0p22 179 23 4096 mmcblk0p23 179 24 2048 mmcblk0p24 179 25 16384 mmcblk0p25 179 26 12288 mmcblk0p26 179 27 24576 mmcblk0p27 179 28 32768 mmcblk0p28 179 29 16384 mmcblk0p29 179 30 24576 mmcblk0p30 179 31 16384 mmcblk0p31 179 32 32768 mmcblk0p32 179 33 16384 mmcblk0p33 179 34 28672 mmcblk0p34 179 35 4096 mmcblk0p35 179 36 98304 mmcblk0p36 179 37 1024 mmcblk0p37 179 38 1024 mmcblk0p38 179 39 2048 mmcblk0p39 179 40 16384 mmcblk0p40 179 41 4096 mmcblk0p41 179 42 131072 mmcblk0p42 179 43 131072 mmcblk0p43 179 44 2048 mmcblk0p44 179 45 2048 mmcblk0p45 179 46 4096 mmcblk0p46 179 47 32768 mmcblk0p47 259 0 2048 mmcblk0p48 259 1 16384 mmcblk0p49 259 2 14336 mmcblk0p50 259 3 5767168 mmcblk0p51 259 4 196608 mmcblk0p52 259 5 32768 mmcblk0p53 259 6 802816 mmcblk0p54 259 7 196608 mmcblk0p55 259 8 53043200 mmcblk0p56 179 144 4096 mmcblk0rpmb 179 96 4096 mmcblk0boot1 179 48 4096 mmcblk0boot0 179 192 62367744 mmcblk1 179 193 62366720 mmcblk1p1 253 0 4724684 dm-0 253 1 790064 dm-1 253 2 128924 dm-2 253 3 32172 dm-3 253 4 193424 dm-4 253 5 193424 dm-5 Code: HWANE:/ $ ls -l /dev/block/platform/hi_mci.0/by-name/ [I][B]User friendly display[/B][/I] /dev/block/mmcblk0p48 -> bootfail_info /dev/block/mmcblk0p42 -> cache /dev/block/mmcblk0p52 -> cust /dev/block/mmcblk0p40 -> dfx /dev/block/mmcblk0p35 -> dto /dev/block/mmcblk0p34 -> dts /dev/block/mmcblk0p27 -> erecovery_kernel /dev/block/mmcblk0p28 -> erecovery_ramdisk /dev/block/mmcblk0p38 -> erecovery_vbmeta /dev/block/mmcblk0p29 -> erecovery_vendor /dev/block/mmcblk0p5 -> fastboot /dev/block/mmcblk0p4 -> frp /dev/block/mmcblk0p26 -> fw_hifi /dev/block/mmcblk0p3 -> fw_lpm3 /dev/block/mmcblk0p44 -> hisitest0 /dev/block/mmcblk0p45 -> hisitest1 /dev/block/mmcblk0p46 -> hisitest2 /dev/block/mmcblk0p30 -> kernel /dev/block/mmcblk0p20 -> misc /dev/block/mmcblk0p36 -> modem_fw /dev/block/mmcblk0p18 -> modem_om /dev/block/mmcblk0p17 -> modem_secure /dev/block/mmcblk0p10 -> modemnvm_backup /dev/block/mmcblk0p6 -> modemnvm_factory /dev/block/mmcblk0p11 -> modemnvm_img /dev/block/mmcblk0p12 -> modemnvm_system /dev/block/mmcblk0p21 -> modemnvm_update /dev/block/mmcblk0p7 -> nvme /dev/block/mmcblk0p43 -> odm /dev/block/mmcblk0p8 -> oeminfo /dev/block/mmcblk0p47 -> patch /dev/block/mmcblk0p16 -> persist /dev/block/mmcblk0p55 -> product /dev/block/mmcblk0p31 -> ramdisk /dev/block/mmcblk0p32 -> recovery_ramdisk /dev/block/mmcblk0p37 -> recovery_vbmeta /dev/block/mmcblk0p33 -> recovery_vendor /dev/block/mmcblk0p22 -> reserved2 /dev/block/mmcblk0p9 -> reserved3 /dev/block/mmcblk0p14 -> reserved4 /dev/block/mmcblk0p15 -> reserved5 /dev/block/mmcblk0p39 -> reserved8 /dev/block/mmcblk0p50 -> reserved9 /dev/block/mmcblk0p49 -> rrecord /dev/block/mmcblk0p13 -> secure_storage /dev/block/mmcblk0p25 -> sensorhub /dev/block/mmcblk0p19 -> splash2 /dev/block/mmcblk0p51 -> system /dev/block/mmcblk0p23 -> teeos /dev/block/mmcblk0p24 -> trustfirmware /dev/block/mmcblk0p56 -> userdata /dev/block/mmcblk0p41 -> vbmeta /dev/block/mmcblk0p54 -> vendor /dev/block/mmcblk0p53 -> version /dev/block/mmcblk0p1 -> vrl /dev/block/mmcblk0p2 -> vrl_backup
Hello, I want to flash a firmware for downgrade. How i can make it without a dload method? I can't downgrade my phone with this method, always a warning appear "error checking files" or anything like that...
Yes me to dload not downgrade Gesendet von meinem ANE-LX1 mit Tapatalk
Manflack said: Hello, I want to flash a firmware for downgrade. How i can make it without a dload method? I can't downgrade my phone with this method, always a warning appear "error checking files" or anything like that... Click to expand... Click to collapse SirusX said: Yes me to dload not downgrade Gesendet von meinem ANE-LX1 mit Tapatalk Click to expand... Click to collapse This is a partition layout it can't help you with downgrade. To downgrade without brick the phone you have to find a roll back firmware. In the picture is an example for p20 pro.