Develop Bugs

CWM Porting Help [Completed]

I have a found a developer that is willing to help port CWM to this device. He doesn't have this device. He needs the following files.
UPDATE
Got everything we needed so far. Thanks to all that helped! Consider sending the developer utkanos a little something if this is useful to you.
Initial testing is done. He has posted the official release thread. Hope see some cool stuff soon.
Feel free to join #utkanos on freednode as a tester or watch the progress.
...and we have liftoff!
I got CWMR booting on the 927r and thus far it appears stable. Very early stages right now so I'm testing it deeply thanks to a helpful owner as we speak. More details as they come.
Click to expand...
Click to collapse
Hi.
I need the following:
1) A boot.img or zImage
2) A dump of /proc/partitions
3) A dump of /proc/emmc or /proc/mtd (if they exist)
4) A dump of the 'mount' command
Click to expand...
Click to collapse
You need to be rooted to dump the files and I am not rooted. So the faster we get these files, the faster CWM can be ported. Attach or link to the files in your post and thanks.

vil33 said:
I have a found a dev that is willing to help port CWM to this device. He doesn't have this device and isn't on xda as far as I know. He needs the follwing files.
You need to be rooted to dump the files and I am not rooted. So the faster we get these files, the faster CWM can be ported. Attach or link to the files in your post and thanks.
Click to expand...
Click to collapse
Here:
cat /proc/partitions
major minor #blocks name
7 0 12506 loop0
7 1 2111 loop1
7 2 5229 loop2
7 3 3150 loop3
179 0 7552000 mmcblk0
179 1 12288 mmcblk0p1
179 2 614400 mmcblk0p2
179 3 319488 mmcblk0p3
179 4 3932672 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2097152 mmcblk0p6
179 7 16384 mmcblk0p7
259 0 5120 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 8192 mmcblk0p10
259 3 524288 mmcblk0p11
179 8 7782400 mmcblk1
179 9 7781376 mmcblk1p1
254 0 12505 dm-0
254 1 2110 dm-1
254 2 5229 dm-2
254 3 3150 dm-3
/proc/emmc doesn't exist
cat /proc/mtd
dev: size erasesize name
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
debugfs /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 /mnt/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p2 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered 0 0
/dev/block/mmcblk0p6 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p3 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:4 /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: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
/dev/block/dm-0 /mnt/asec/net.skyscanner.android.main-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
/dev/block/dm-1 /mnt/asec/com.flightradar24free-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iochar
set=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/org.scummvm.scummvm-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/org.scummvm.scummvm.plugin.scumm-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=c
p437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

tcfx44 said:
Here:
Click to expand...
Click to collapse
Thanks for the quick response, I passed it on to the Dev and hopefully he can do this. Do you have the boot.img as well?

vil33 said:
Thanks for the quick response, I passed it on to the Dev and hopefully he can do this. Do you have the boot.img as well?
Click to expand...
Click to collapse
I'm still new to Android and cannot find boot.img. Can you help me with the location of the file?

tcfx44 said:
I'm still new to Android and cannot find boot.img. Can you help me with the location of the file?
Click to expand...
Click to collapse
okay, go ahead and laugh, i'm no dev or linux guy, but there is a boot.img file ready for download on the Rooting the captivate glide thread right? I believe it is on the step 2 of the process (with a link on CarrierIQ Free). When I download that file and extracted, I got boot.img in tar file. Can they use that?
I don't want to upload, unsure about it.

gabby131 said:
okay, go ahead and laugh, i'm no dev or linux guy, but there is a boot.img file ready for download on the Rooting the captivate glide thread right? I believe it is on the step 2 of the process (with a link on CarrierIQ Free). When I download that file and extracted, I got boot.img in tar file. Can they use that?
I don't want to upload, unsure about it.
Click to expand...
Click to collapse
Thanks I forgot about that. Sent him it and hopefully it's the right one.

It would be nice if your friend release CWM to prepare a guide on how he did it, I am learning myself, successfully compiled the kernel but I dont really understand the proccess for CWM, should it is included in the kernel like it is the case for a lot of samsung devices or should it be a recovery...
Thanks for the details

CarpeNoctem said:
It would be nice if your friend release CWM to prepare a guide on how he did it, I am learning myself, successfully compiled the kernel but I dont really understand the proccess for CWM, should it is included in the kernel like it is the case for a lot of samsung devices or should it be a recovery...
Thanks for the details
Click to expand...
Click to collapse
Hey you can meet him on the freenode irc network on channel #koush by the name utkanos, he's usually there 9-5 central. Also it would help if we had a rooted user to help the process out. He just emailed me that he wanted this:
Can you get into stock recovery and get me the recovery.log? Should be in cache or tmp.
Click to expand...
Click to collapse

Hi.
In addition to the recovery.log from stock recovery, I would like to see a build.prop (from system) please.
I do not post on XDA very much, usually over on rootzwiki or on freenode.

Here is the build.prop
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.RUXKJ5
ro.build.version.incremental=RUXKJ5
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Fri Oct 14 15:36:02 KST 2011
ro.build.date.utc=1318574162
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEI-28
ro.build.tags=release-keys
ro.product.model=SAMSUNG-SGH-I927R
ro.product.brand=samsung
ro.product.name=SGH-I927R
ro.product.device=SGH-I927R
ro.product.board=SGH-I927R
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=I927RUXKJ5
ro.build.hidden_ver=I927RUXKJ5
ro.build.changelist=652095
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=CA
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SGH-I927R
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SGH-I927R-user 2.3.5 GINGERBREAD RUXKJ5 release-keys
ro.build.fingerprint=samsung/SGH-I927R/SGH-I927R:2.3.5/GINGERBREAD/RUXKJ5:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I927RUXKJ5
ro.build.hidden_ver=I927RUXKJ5
ro.build.changelist=652095
ro.tether.denied=false
ro.flash.resolution=1080
# end build properties
ro.opengles.version = 131072
wifi.interface=eth0
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttys0
ro.sf.lcd_density=240
dalvik.vm.heapsize=64m
# Samsung USB default mode
persist.service.usb.setting=0
# Set Default Timezone as America/New_York
persist.sys.timezone=America/New_York
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.locationfeatures=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.3_r7
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=false
dev.sfbootcomplete=0
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.ms=android-samsung
ro.com.google.clientidbase.am=android-samsung
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.clientidbase.yt=android-samsung
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.locationfeatures=1
keyguard.no_require_sim=true
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=01_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.monkey=0
ro.opengles.version=131072
ro.secdevenc=true
ro.wtldatapassword=true
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Here if the result of the cat proc/mounts
Code:
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
debugfs /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 /mnt/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p2 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered 0 0
/dev/block/mmcblk0p6 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered,noau
to_da_alloc,discard 0 0
/dev/block/mmcblk0p3 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0

Cheers for that
edit: I believe I have what I need now, thank you to those who provided the files for me. I will update when I have something tangible for you.

Well I have some bad news for you guys.
The stock kernel provided is bitwise EXACTLY the size of the partition that holds it, and I need to add about 500KB of space to make recovery work.
Thus, repacking the ramdisk with a hacked recovery isn't going to be possible unless the kernel image can get much smaller to accommodate.

utkanos said:
Well I have some bad news for you guys.
The stock kernel provided is bitwise EXACTLY the size of the partition that holds it, and I need to add about 500KB of space to make recovery work.
Thus, repacking the ramdisk with a hacked recovery isn't going to be possible unless the kernel image can get much smaller to accommodate.
Click to expand...
Click to collapse
Isn't it possible to resize the partitions ?
also this mean Samsung has no intention to release any other kernel/version of android or the kernel needs to remains always the same?

Has anyone tried the kernel from the KL1 build? CIQ should be removed from that (it came out a few days after the CIQ fiasco), which could provide the space we're missing...

Symmetric said:
Has anyone tried the kernel from the KL1 build? CIQ should be removed from that (it came out a few days after the CIQ fiasco), which could provide the space we're missing...
Click to expand...
Click to collapse
Thanks for the tip, I think I might have something worth testing if someone wants to hop into IRC
I am on freenode as utkanos in #koush

...and we have liftoff!
I got CWMR booting on the 927r and thus far it appears stable. Very early stages right now so I'm testing it deeply thanks to a helpful owner as we speak. More details as they come.

Symmetric said:
Has anyone tried the kernel from the KL1 build? CIQ should be removed from that (it came out a few days after the CIQ fiasco), which could provide the space we're missing...
Click to expand...
Click to collapse
Good call

Work beautifully achieved

Symmetric said:
Has anyone tried the kernel from the KL1 build? CIQ should be removed from that (it came out a few days after the CIQ fiasco), which could provide the space we're missing...
Click to expand...
Click to collapse
Hooray for me!
Let the games begin?

utkanos said:
...and we have liftoff!
I got CWMR booting on the 927r and thus far it appears stable. Very early stages right now so I'm testing it deeply thanks to a helpful owner as we speak. More details as they come.
Click to expand...
Click to collapse
Amazing work utkanos, now I can get my flash fix on my GF's phone! Thanks a million!

[MOD] Swap SDcards mod for SGS2 CM10

This is a simple mod that will swap SDcards (use microSD card as primary storage) on Samsung Galaxy S2 phones with Cyanogenmod 10.
With this mod microSD card will appear as primart storage (/storage/sdcard0 and /mnt/sdcard) and internal SD memory will appear as secondary storage (/storage/sdcard1 and /mnt/extSdCard).
Technically this mod updates file /system/etc/vold.fstab
Mod is flashable via recovery and is meant only for Cyanogenmod 10/10.1 (Jelly Bean).
Always make full Nandroid backup before flashing this mod!
Disclaimer: I am not responsible for anything that may happen as a result of using this mod.
I didn't find GUI option for this, so I created this mod.
P.S. If there is a GUI option or other similar mods, please post about them in this thread.

I just change 1's to 0's
Nice effort
Though this probably wont stay on Original Android Dev for long, general or Android Dev type.

rudolf895 said:
I just change 1's to 0's
Click to expand...
Click to collapse
That's the way this mod was born
Although booting to edit the file (via Root Explorer) may remove songs from media library.

can u make a script for galaxy s3 please? ive upgraded and i cant find any scripts, or zips. thankyouu

markryan44 said:
can u make a script for galaxy s3 please? ive upgraded and i cant find any scripts, or zips. thankyouu
Click to expand...
Click to collapse
For what ROM?
I have no Galaxy S3 where to test, but if you want, you can be the tester...

Works this on cm10.1 ? Thx
Sent from my GT-I9100 using xda premium

-ghost- said:
Works this on cm10.1 ? Thx
Click to expand...
Click to collapse
It should work

markryan44 said:
can u make a script for galaxy s3 please? ive upgraded and i cant find any scripts, or zips. thankyouu
Click to expand...
Click to collapse
From this link, it seems that the xda developer, "droidiser" has manage to get vold.fstab to work on S3. I personally have not tried it yet, but will soon.
http://www.droidiser.com/2012/11/swap-internal-sdcard-external-mod-android.html
I tried it today (3/27/2013). Script does NOT work on Samsung S3 t-mobile.

DavisNT said:
For what ROM?
I have no Galaxy S3 where to test, but if you want, you can be the tester...
Click to expand...
Click to collapse
I have t-mobile Samsung Galaxy S3, running on cynogenmod 10.0 and willing to be the guinea pig. Contact me, via reply to this post and we can proceed

I got bootloop after flashed this script. I am on alliance 7.02.
Sent from my GT-I9100 using xda premium

AW: [MOD] Swap SDcards mod for SGS2 CM10
freewind29 said:
I got bootloop after flashed this script. I am on alliance 7.02.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Epic xD
Read the OP...or the title atleast..
Greetz
SlimBean-b2.5|i9100¬Tapa2

You should make a zip to revert also..

goja said:
You should make a zip to revert also..
Click to expand...
Click to collapse
The best methods to get back original vold.fstab are:
reflash ROM, Gapps and any other mods (without wiping data)
restore full Nandroid backup, made before flashing my mod
If several users want, I can also implement a simple backup and restore functionality in my mod...
P.S. Added backup warning to original post.

hi DavisNT,
I have pm you the mount points on my S3 t-mobile SGH-T999 running CM 10.0.0 build Nov 13, 2012 with superuser access. Thanks for helping
....................
[email protected]:/ $ su
[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
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,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 /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/com.picsel.tgv.app.smartoffice-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/com.jrummy.liberty.toolboxpro-2 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-2 /mnt/asec/org.koxx.pure_messenger-2 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-3 /mnt/asec/org.gtmedia.seekdroid-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-4 /mnt/asec/com.stoik.mdscan-2 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-5 /mnt/asec/com.roflharrison.agenda.plus-2 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-6 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-7 /mnt/asec/com.speedsoftware.rootexplorer-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-8 /mnt/asec/com.mseven.msecure-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-9 /mnt/asec/org.koxx.pure_calendar-2 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-10 /mnt/asec/cz.directservices.SmartVolumeControlPlus-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-11 /mnt/asec/com.alexvas.dvr.pro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-12 /mnt/asec/com.Relmtech.RemotePaid-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-13 /mnt/asec/com.psyrus.packagebuddypro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-14 /mnt/asec/com.liveov.shotux-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
[email protected]:/ #

this script isn't running anymore on CM10.2 resp. Android 4.3.
Any updates on this?
cheers!

samukinson said:
this script isn't running anymore on CM10.2 resp. Android 4.3.
Any updates on this?
cheers!
Click to expand...
Click to collapse
+1 I would like this as well! Either that or a walk through on how to swap the mounts on 4.3. This would be greatly appreciated! Thanks in advance.

Nice but any app apk I like this as app not mod please get app for this not explorer
Thanks
تم الإرسال من جهازي GT-I9100 بواسطة تاباتوك 2

This will work with cm10.1.3 for galaxy S2 i9100G???
Sent from my GT-I9100G using xda app-developers app

encik_racun said:
This will work with cm10.1.3 for galaxy S2 i9100G???
Click to expand...
Click to collapse
Most likely this mod won't work on i9100G.

DavisNT said:
Most likely this mod won't work on i9100G.
Click to expand...
Click to collapse
Ohh boy, i guess i'll stay with cm9 for dacade
Sent from my GT-I9100G using xda app-developers app

[4.4] CM 11.0 broken

Hello
I try to build cm 11, but Its broken.
My log is : http://pastebin.com/zakHeqW8
It stucks at samsung logo. I dont know what would fix it.
Anyone idea?

bubor said:
It stucks at samsung logo. I dont know what would fix it.
Anyone idea?
Click to expand...
Click to collapse
ther is something wrong with mount points
in linux is configurable in /etc/fstab but in android??
maybe is something with filesystem, do U add vfat module to image??

croolyc said:
ther is something wrong with mount points
in linux is configurable in /etc/fstab but in android??
maybe is something with filesystem, do U add vfat module to image??
Click to expand...
Click to collapse
you dont need sdcard0 or sdcard1 to boot, nor vfat.
All other fses are mounted.
Filesystem Size Used Free Blksize
/dev 361.2M 132.0K 361.1M 4096
/sys/fs/cgroup 361.2M 12.0K 361.2M 4096
/mnt/secure 361.2M 0.0K 361.2M 4096
/mnt/asec 361.2M 0.0K 361.2M 4096
/mnt/obb 361.2M 0.0K 361.2M 4096
/mnt/fuse 361.2M 0.0K 361.2M 4096
/system 590.6M 441.1M 149.4M 4096
/efs 11.8M 8.1M 3.7M 4096
/cache 307.1M 5.5M 301.6M 4096
/data 2.0G 115.9M 1.9G 4096
/preload 503.9M 104.6M 399.3M 4096
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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/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
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p2 /system ext4 ro,seclabel,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,acl,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p3 /cache ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,acl,barrier=1,journal_async_commit,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p6 /data ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,journal_async_commit,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p11 /preload ext4 ro,seclabel,nosuid,nodev,noatime,user_xattr,acl,barrier=1,journal_async_commit,data=ordered 0 0

Probably this is the problem:
Code:
I/ ( 116): NV Interposer: k:Error creating socket.
I/ ( 116): NV Interposer: Communication layer init failed.
D/NvOsDebugPrintf( 116): Init second stage failed.

Adam77Root said:
Probably this is the problem:
Code:
I/ ( 116): NV Interposer: k:Error creating socket.
I/ ( 116): NV Interposer: Communication layer init failed.
D/NvOsDebugPrintf( 116): Init second stage failed.
Click to expand...
Click to collapse
and I have no idea how to fix it. (maybe no internet permission for SurfaceFlinger? )
I've found tegra3 base with same issue http://pastebin.com/GvrTX968
I dont like that either:
Code:
I/SurfaceFlinger( 116): Using composer version 0.0
It was
Code:
I/SurfaceFlinger( 112): Using composer version 0.1
edit: and omnirom 4.4 works. ( https://github.com/omnirom/android_...53b0969124a8817beed8fad03ceaad68546b22#diff-0 patch didnt help)
Missing BOARD_EGL_NEEDS_LEGACY_FB in:
https://github.com/CyanogenMod/andr....0/services/surfaceflinger/SurfaceFlinger.cpp

So what are the chances of a working KitKat 4.4 ROM? Also are you saying we can use your Omnirom safely? Thank you for developing for us!

stormdude124 said:
So what are the chances of a working KitKat 4.4 ROM? Also are you saying we can use your Omnirom safely? Thank you for developing for us!
Click to expand...
Click to collapse
going to release omni rom 4.4, but it has many problem ATM, and I dont feel I could fix it, problem is in old HALs.
Android droped tegra2 support in 4.2, CM in 10.2, so its miracle to hace stable cm-10.2.

(recovery) twrp 2.6.3.0 selinux updated 3/8/2014

anyone wanna test this one let me know if it boots.
recovery.img attached

Anyone got a KitKat ROM to try? @Wambo_ ?

Unbelievable..... Umm. I think I still have that Link up that's in the Evervolv thread. Not sure if it's live.

Wambo_ said:
Unbelievable..... Umm. I think I still have that Link up that's in the Evervolv thread. Not sure if it's live.
Click to expand...
Click to collapse
I downloaded your blackat for supersonic and I have it on my computer. I think the link is still working fine.
I tried to flash it via fastboot. It downloads boot image but when booting it gets stuck on htc evo 4g startup screen.
I tried to get a logcat (I don't know if it is possible to get logcat) but it says "CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "/sbin/sh", caused by library "libc.so" not found"
What is 411? How can I get that?

411 just means let me know the problems you find so i can fix them.
Sent from my One Mini using Tapatalk

Also could some get me the partition layout for the device. That would be very helpful.lol
Sent from my One Mini using Tapatalk

[email protected]:/ # dh
sh: dh: not found
127|[email protected]:/ # df
Filesystem Size Used Free Blksize
/dev 206M 48K 206M 4096
/mnt/asec 206M 0K 206M 4096
/mnt/obb 206M 0K 206M 4096
/app-cache 8M 0K 8M 4096
/system 350M 247M 102M 4096
/data 427M 346M 80M 4096
/cache 160M 56M 103M 4096

mewthree1 said:
[email protected]:/ # dh
sh: dh: not found
127|[email protected]:/ # df
Filesystem Size Used Free Blksize
/dev 206M 48K 206M 4096
/mnt/asec 206M 0K 206M 4096
/mnt/obb 206M 0K 206M 4096
/app-cache 8M 0K 8M 4096
/system 350M 247M 102M 4096
/data 427M 346M 80M 4096
/cache 160M 56M 103M 4096
Click to expand...
Click to collapse
do adb shell and type "mount" without quotes and gimme the readout.

cmvienneau said:
do adb shell and type "mount" without quotes and gimme the readout.
Click to expand...
Click to collapse
|[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
tmpfs /app-cache tmpfs rw,relatime,size=8192k 0 0
/dev/block/mtdblock4 /system yaffs2 ro,noatime 0 0
/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,noatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0

I have a active EVO I can test if needed, can someone post a link to the Rom were testing on.

Need one more thing from y'all. I need to know the names of the partition along with the mount point. Example "/dev/block/mmcblk0p13= /boot" and so on?
Sent from my One Mini using Tapatalk

^ Someone provide the output of cat proc/mtd.
That'll do it. If your kernel was built w/SELinux enabled, it should be a simple matter of splitting an existing TWRP image and repacking with your zImage. Then all of the fstab stuff should already be correct.

This what ya looking for
{
"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"
}

Yes that'd be it. I'll see what I can do now
Sent from my One Mini using Tapatalk

Ok I have a few of these phones so I can test just let me no.

vinman12 said:
Ok I have a few of these phones so I can test just let me no.
Click to expand...
Click to collapse
Well, this is exciting! I'm still using my Evo as my every day phone.

Lol yeah, I'm game for getting this working, Hell looking foward to even theming it up some.

im no dev, but ill help test or whatever. bring on the kit kat!!!!

Any progres on this

That recovery img in the op working

[INFO][TWRP for Ascend P7 - WIP ]

Hello everybody !
TWRP 2.7.1.0 for ascend P7
*** Working In Progress ***
Open this new thread in the hope that you can help me in achieving TWRP for your P7 .
First of all, I have not this device currently - so, your help is welcome :good:
I will post here ( soon ) a list of the required - to be able to start building TWRP .
This stuff are required from your P7 device :
your international model : ( example Ascend P6 -> P6-U06 ) :
if your device can be unlocked ? ( bootloader unlocked )
build.prop ;
stock boot.img
stock recovery.img
screenshoots with CPU-Z !
more stuff will be added later ;
Please keep this thread clean, and on topic - in this way, it will be much easier to find the information needed !
Thank you very much for your cooperation !
Best regards !

How extract stock boot.img and recovery.img :
- root your device ;
> adb shell
$ su
# dd if =/dev/block/mmcblk0pX1 of=/storage/sdcard0/boot.img ( extract boot.img on internal storage )
# dd if=/dev/block/mmcblk0px2 of=/storage/sdcard0/recovery.img ( extract recovery.img on internal storage )
# exit
$ exit
> adb pull /storage/sdcard0/boot.img ( extract boot.img from your device on your PC )
> adb pull /storage/sdcard0/recovery.img ( extract recovery.img from your device on your PC )
How you can determainate partition mmcblk0pX1 for boot :
> navigate in your device : /dev/block/platform/xxx.1 or xxx.2/by-name/ here you will be able to see :
Example :
boot
07 Jul 14 06:01:00 rwxrwxrwx -> mmcblk0p42
Click to expand...
Click to collapse
So , mmcblk0pX1 will be in this case -> mmcblk0p42 !
Please follow the same way for determinate partition mmcblk0pX2 for recovery !

surdu_petru said:
your international model : ( example Ascend P6 -> P6-U06 ) :
{
"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"
}
if your device can be unlocked ? ( bootloader unlocked )
build.prop
https://drive.google.com/file/d/0B1KQ4_n2Fu3AZFlreS1xSEtEYlE/edit?usp=sharing
stock boot.img
Code:
dd if=/dev/block/mmcblk0p17 of=/storage/sdcard0/boot.img
32768+0 records in
32768+0 records out
16777216 bytes transferred in 2.305 secs (7278618 bytes/sec)
https://drive.google.com/file/d/0B1KQ4_n2Fu3AeHY4a3NvTDZLRTQ/edit?usp=sharing
stock recovery.img
Code:
dd if=/dev/block/mmcblk0p18 of=/storage/sdcard0/recovery.img
32768+0 records in
32768+0 records out
16777216 bytes transferred in 2.378 secs (7055179 bytes/sec)
https://drive.google.com/file/d/0B1KQ4_n2Fu3AdDA4Rk5Yc2s3ekU/edit?usp=sharing
screenshoots with CPU-Z !
Click to expand...
Click to collapse
I hope this is helpfull.

Hi,
I hope that I can help you.
My model is P7-L10, bought in Germany
I extracted boot.img, recovery.img and recovery2.img (in case if it's of any use) from mmcblk0p17, 18 and 19. Also included is the /system/build.prop:
https://mega.co.nz/#!P8IGWBpL!7YVCaAoc8AYFbbXGVVjGtjnL0B9jBih9h35qqX4lIpg
Here are screenshot of CPU-Z:

Thank you very much ... tomorrow I'll try to build the first twrp .
I'll let you to know if I'll need more info from your device .

Hi, Surdu
model
P7-L00
bootloader unlocked
http://4pda.ru/forum/index.php?showtopic=544043&view=findpost&p=32647974
recovery+Boot+Buildprop P7-L00 B122SP01.zip
https://drive.google.com/file/d/0B5ikIYcL8lmXZnFOUUlqT0JKSk0/edit?usp=sharing
Thank you very much.

If you have already CWM for your device, even in Chinese, please upload here - I don't understand this language currently
Also some question :
Do you have in your device :
/dev/block/platform/hi_mci.0/by-name/system ?
or
/dev/block/platform/hi_mci.0/by-name/newsys ?
or both ....
Also do you have : /dev/block/platform/hi_mci.0/by-name/sdcard ?
Please, can you take a screenshot with "mount" on your device :
> adb shell
$ su
# mount
Click to expand...
Click to collapse
Thank you very much !

Again, P7-L10
Do you have in your device :
/dev/block/platform/hi_mci.0/by-name/system ?
Click to expand...
Click to collapse
Yes.
/dev/block/platform/hi_mci.0/by-name/newsys ?
Click to expand...
Click to collapse
No.
Also do you have : /dev/block/platform/hi_mci.0/by-name/sdcard ?
Click to expand...
Click to collapse
No.
Mount:
Code:
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
/dev/block/mmcblk0p11 /mnvm1:0 ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p12 /mnvm2:0 ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p16 /mnvm3:0 ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 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/frz cgroup rw,relatime,freezer 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
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 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
tmpfs /fs_emmc_log tmpfs rw,seclabel,nosuid,nodev,relatime,mode=664 0 0
/dev/block/platform/hi_mci.0/by-name/system /system ext4 ro,seclabel,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/hi_mci.0/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/hi_mci.0/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/hi_mci.0/by-name/cust /cust ext4 ro,seclabel,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/hi_mci.0/by-name/splash2 /splash2 ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/hi_mci.0/by-name/3rdmodem /3rdmodem ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/hi_mci.0/by-name/3rdmodemnvm /3rdmodemnvm ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/hi_mci.0/by-name/3rdmodemnvmbkp /3rdmodemnvmbkp ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/data/share /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
/dev/block/vold/179:97 /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
/data/share /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/share /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/share /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/share /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0

Chinese recovery
This one according with Chinese sites is for model P7-00. This is the model I own.
I have seen CWM also for 05 and 07. Not sure if are the same.
I am in CH and I can give you all they have posted for this phone.
Sanatate....

/dev/block/platform/hi_mci.0/by-name/system
Yes
/dev/block/platform/hi_mci.0/by-name/sdcard
No

Nice, i will try to help

Why TWRP ? I'm starting a CWM Recovery for P6/P7 and other devices.

Hello again !
For enable some stuff in TWRP recovery ( like mount external storage, battery indicator and auto light display ) I need also to know some PATH from your device !
Here you will see P6 PATH :
Brightness Path = /sys/devices/platform/k3_fb.1/leds/lcd_backlight0/brightness
Mass Storage Path = /sys/class/android_usb/android0/f_mass_storage/lun/file
Battery Path = /sys/devices/platform/bq_bci_battery.1/power_supply/Battery
1° I need some proper path from your device for Brightness, Mass Storage and Battery !
2° Need a screenshots with this commands :
> adb shell
$ su
# cat /proc/partitions
Click to expand...
Click to collapse
> adb shell
$ su
# cat /proc/app_info
Click to expand...
Click to collapse
3° Also I need some stock : libraries , /system/lib/egl/egl.cfg and also /system/bin/linker !
( /system/lib/libc.so; /system/lib/libdl.so ; /system/lib/liblog.so ; /system/lib/libm.so ; /system/lib/libstdc++.so ; /system/lib/libz.so )
Also I can see you have a new service /sbin/set_immutable ... if someone can clarify me what could be ?
In your boot.img after mount /system you have this command :
exec /sbin/set_immutable 1
Maybe someone can set to 0 ( # exec /sbin/set_immutable 0 ) to see what is happend ....
Thank you very much for your collaboration , and I'll await your response :highfive:
Edit :
Please , I need also to know your system and userdata partitions :
boot -> /dev/block/mmcblk0p17
recovery -> /dev/block/mmcblk0p18
system -> /dev/block/mmcblk0p??
userdata -> /dev/block/mmcblk0p??

P7-L00
Brightness Path =/sys/devices/platform/k3_fb.1/leds/lcd_backlight0/brightness
Yes
Mass Storage Path = /sys/class/android_usb/android0/f_mass_storage/lun/file
Yes
Battery Path = /sys/devices/platform/bq_bci_battery.1/power_supply/Battery
Yes

olegusss said:
Brightness Path =/sys/devices/platform/k3_fb.1/leds/lcd_backlight0/brightness
Yes
Mass Storage Path = /sys/class/android_usb/android0/f_mass_storage/lun/file
Yes
Battery Path = /sys/devices/platform/bq_bci_battery.1/power_supply/Battery
Yes
Click to expand...
Click to collapse
Thank you very, very much ! :good:
Edit :
Please, can you take a look into : /dev/block/platform/hi_mci.0/by-name... and tell me the right partition for system and userdata ?
/dev/block/platform/hi_mci.0/by-name/system -> mmcblk0p??
/dev/block/platform/hi_mci.0/by-name/userdata -> mmcblk0p??
I already know boot and recovery :
/dev/block/platform/hi_mci.0/by-name/boot -> mmcblk0p17
/dev/block/platform/hi_mci.0/by-name/recovery -> mmcblk0p18
Thanks again !
Re-Edit :
I think you will have :
/dev/block/platform/hi_mci.0/by-name/system -> mmcblk0p28
/dev/block/platform/hi_mci.0/by-name/userdata -> mmcblk0p30
/dev/block/platform/hi_mci.0/by-name/cust -> mmcblk0p29
But I need confirmation if this value is true !

I think you will have :
/dev/block/platform/hi_mci.0/by-name/system -> mmcblk0p28
/dev/block/platform/hi_mci.0/by-name/userdata -> mmcblk0p30
/dev/block/platform/hi_mci.0/by-name/cust -> mmcblk0p29
But I need confirmation if this value is true !
Click to expand...
Click to collapse
Confirmed (P7-L10)

Also I can see you have a new service /sbin/set_immutable ... if someone can clarify me what could be ?
In your boot.img after mount /system you have this command :
exec /sbin/set_immutable 1
Maybe someone can set to 0 ( # exec /sbin/set_immutable 0 ) to see what is happend ....
Click to expand...
Click to collapse
In the /system folder there's a file called set_immutable.list - even if you rooted the device, it still prevents writing to system folders. E.g. you can't install Xposed.
Only if you delete / rename set_immutable.list on top of root you gain full writing access:
http://forum.xda-developers.com/showpost.php?p=53291974&postcount=200

XQC said:
In the /system folder there's a file called set_immutable.list - even if you rooted the device, it still prevents writing to system folders. E.g. you can't install Xposed.
Only if you delete / rename set_immutable.list on top of root you gain full writing access:
http://forum.xda-developers.com/showpost.php?p=53291974&postcount=200
Click to expand...
Click to collapse
OK, now I anderstand .... But why you not remove set_immutable binary from /sbin into boot.img - I think in this way there will no be any set_immutable.list in your /system - so you'll have no restrictions to mount /system ro/rw .
If you want to testin this way , let me to know and I'll make this change for you to test. Also I can enable /init.d into kernel.
Awaiting your request ....
Also thank you very much for all info about your device ... Today later I'll provide a test TWRP for P7.
Edit :
If you set set_immutable 0 , than you will be able to write into /system !
Code:
> adb shell
$ su
# exec /sbin/set_immutable 0
# exit
$ exit

surdu_petru said:
Please, can you take a look into : /dev/block/platform/hi_mci.0/by-name... and tell me the right partition for system and userdata ?
/dev/block/platform/hi_mci.0/by-name/system -> mmcblk0p??
/dev/block/platform/hi_mci.0/by-name/userdata -> mmcblk0p??
Click to expand...
Click to collapse
Can is not so actual. There simply was not time to get to the phone.
I think you will have :
/dev/block/platform/hi_mci.0/by-name/system -> mmcblk0p28
/dev/block/platform/hi_mci.0/by-name/userdata -> mmcblk0p30
/dev/block/platform/hi_mci.0/by-name/cust -> mmcblk0p29
But I need confirmation if this value is true !
Click to expand...
Click to collapse
Yes, You as always right

Test TWRP !
Hello !
Test TWRP 2.7.1.0 for Huawei Ascend P7 .
At this time is recommended for P7-L10 .
Downloads :
openrecovery-twrp.img md5 : 5e1f511b81c5a16a6de7b64ff299b0c9
Because is a beta test, please do not install :
if you are not accustomed to installing (flash) a custom kernel / recovery ;
if you don't know to put your device in bootloader mode by pressing hardware keys ( this require to put your device in bootloader mode
in case your device will not boot after install this custom recovery - and to be able to flash stock recovery ) !
you are totally responsible, for your actions on your device - that's why I'm not respond in any way if something goes wrong ! -
Installations :
your bootloader device must be unlocked ;
put your device in bootloader mode -> ( adb reboot bootloader )
flash recovery.img -> ( fastboot flash recovery openrecovery-twrp.img )
reboot your device from bootloader mode -> ( fastboot reboot )
Revert to stock recovery :
download stock recovery.img for P7-L10 !
install stock recovery -> ( fastboot flash recovery recovery.img )
You can go in TWRP recovery in the same way like into stock recovery or ( > adb reboot recovery ) !
First, please report if your device boot in TWRP recovery , and than the rest of issues !
Best regards !