Zombie is a Kernel which extends the Xperia Z5C's capabilities.
It is aimed at including only useful and strictly tested features, enhancements and optimisations,
Important: I do not accept Bug reports when you are running a modified Rom or using Xposed!
Changes compared to Stock-Kernel:
* Important bug fixes / security patches
* CPU-Speedbin visible in debugfs node (sys/kernel/debug/msm8994_cpuinfo/*Speedbin)
* Underclocked both Cluster to 1,344/1,536 GHz respectively
* Custom brightness scaling (reduced min. brightness, increase max. brightness)
* Hold Power-Button for 5 seconds to reboot into bootloader
Security Patch-Level: November
Todo:
* -
App to check your device's Panel Manufacturer:
SonyKitakamiPanelInfov1.0 Download
Downloads:
Kernel Zip Package:
Latest Build: Zombie-b9
Installation:
* Unpack ZIP and flash Kernel via Fastboot
Sources:
Zombie-MM Kernel Source at Github
PanelInfo-App Source at Github
XDA:DevDB Information
Zombie, Kernel for the Sony Xperia Z5 Compact
Contributors
Tommy-Geenexus
Kernel Special Features:
Version Information
Status: Testing
Created 2015-10-13
Last Updated 2016-11-12
Reserved
Code:
// nothing to see here
Great, hope there will be a continous work on these thingies as this device is rather new and we need every bit that can help. Even for Locked Bootloaders...
Since it is insecure (ro.secure=0), will adbd run as root?
nilezon said:
Since it is insecure (ro.secure=0), will adbd run as root?
Click to expand...
Click to collapse
Nope, it needs also ro.debuggable=1 and a modified adbd binary in ramdisk.
Tommy-Geenexus said:
Nope, it needs also ro.debuggable=1 and a modified adbd binary in ramdisk.
Click to expand...
Click to collapse
Thank you.
I guess it would be easier to just drop a "rootsh" shell binary in ramdisk with setuid and root owner (chmod 4750) ?
I need that root shell
Edit:
I'm trying to compile your kernel but am getting a weird error:
Code:
CC mm/filemap.o
mm/filemap.c: In function 'grab_cache_page_write_begin':
mm/filemap.c:2306:1: internal compiler error: Segmentation fault
}
Using aarch64-linux-android-4.9 toolchain from Google.
Do you have any pointers for me?
nilezon said:
Thank you.
I guess it would be easier to just drop a "rootsh" shell binary in ramdisk with setuid and root owner (chmod 4750) ?
I need that root shell
Click to expand...
Click to collapse
One could implement su and all needed files in the ramdisk and copy them over, however i'd vote for someone to build TWRP.
I have not much experience in shell scripting, and having a working recovery would be the optimal solution.
nilezon said:
Thank you.
I guess it would be easier to just drop a "rootsh" shell binary in ramdisk with setuid and root owner (chmod 4750) ?
I need that root shell
Edit:
I'm trying to compile your kernel but am getting a weird error:
Code:
CC mm/filemap.o
mm/filemap.c: In function 'grab_cache_page_write_begin':
mm/filemap.c:2306:1: internal compiler error: Segmentation fault
}
Using aarch64-linux-android-4.9 toolchain from Google.
Do you have any pointers for me?
Click to expand...
Click to collapse
Had exactly the same issue.
I suppose you cloned the GCC from Google like me, just checkout the marshmallow branch, the master branch has some issues.
Otherwise i can upload my GCC (latest AOSP toolchain) and link it.
Tommy-Geenexus said:
Had exactly the same issue.
I suppose you cloned the GCC from Google like me, just checkout the marshmallow branch, the master branch has some issues.
Otherwise i can upload my GCC (latest AOSP toolchain) and link it.
Click to expand...
Click to collapse
Got it working using marshmallow-release branch.
THANK YOU!
nilezon said:
Got it working using marshmallow-release branch.
THANK YOU!
Click to expand...
Click to collapse
Np, feel free to contribute if you find any useful stuff, always good to have some dev's around.
Tommy-Geenexus said:
One could implement su and all needed files in the ramdisk and copy them over, however i'd vote for someone to build TWRP.
I have not much experience in shell scripting, and having a working recovery would be the optimal solution.
Click to expand...
Click to collapse
Hey @Tommy-Geenexus.
1.) Great work btw.
2.) Have you run
Code:
$. su
#. cat /proc/emmc
(or similar) On your Z5C yet?
Id love to know the partition lay out. Will speed along the development of a custom recovery. I would do this my self but I don’t have a Z5C yet.
3.) Have you attempted to/had any luck compiling your kernel with any tool chain other then GCC 4.9 from marshmallow branch?
Regards
Joeisgood99.
Joeisgood99 said:
Id love to know the partition lay out. Will speed along the development of a custom recovery. I would do this my self but I don’t have a Z5C yet.
Click to expand...
Click to collapse
You can use
/dev/block/platform/soc.0/by-name/***
if you need it for fstab.
https://github.com/AndroPlus-org/an...ob/TWRP-28.0.A.8.251-karin/rootdir/twrp.fstab
I posted test TWRP build for E6653 before in Z5 forum, but no one has interest....
http://x.andro.plus/1OrEQ7i
[EDIT] @nilezon
It's for E6653, but differences are only configs in default.prop and kernel modules in sbin in recovery ramdisk, so you can use it on other Z5/Z5C after editing codenames and lcd_density and overwriting kernel modules.
AndroPlus said:
You can use
/dev/block/platform/soc.0/by-name/***
if you need it for fstab.
https://github.com/AndroPlus-org/an...ob/TWRP-28.0.A.8.251-karin/rootdir/twrp.fstab
I posted test TWRP build for E6653 before in Z5 forum, but no one has interest....
http://x.andro.plus/1OrEQ7i
Click to expand...
Click to collapse
Good job!
Does the E6653 recovery work with E5823, or could you recompile it for suzuran, please?
Edit @AndroPlus
Thank you. I'll get the Z5C in a few days and will take the recovery for a spin then.
Joeisgood99 said:
Hey @Tommy-Geenexus.
1.) Great work btw.
2.) Have you run
Code:
$. su
#. cat /proc/emmc
(or similar) On your Z5C yet?
Id love to know the partition lay out. Will speed along the development of a custom recovery. I would do this my self but I don’t have a Z5C yet.
3.) Have you attempted to/had any luck compiling your kernel with any tool chain other then GCC 4.9 from marshmallow branch?
Regards
Joeisgood99.
Click to expand...
Click to collapse
Not yet, but here is the output of "cat /proc/partitions":
Code:
major minor #blocks name
254 0 524288 zram0
179 0 30535680 mmcblk0
179 1 2048 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 81920 mmcblk0p3
179 4 128 mmcblk0p4
179 5 128 mmcblk0p5
179 6 1 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 256 mmcblk0p9
179 10 1 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 8 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1024 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 256 mmcblk0p19
179 20 256 mmcblk0p20
179 21 128 mmcblk0p21
179 22 128 mmcblk0p22
179 23 1024 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 512 mmcblk0p25
179 26 512 mmcblk0p26
179 27 1024 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 65536 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 32768 mmcblk0p31
259 0 65536 mmcblk0p32
259 1 1024 mmcblk0p33
259 2 512 mmcblk0p34
259 3 1 mmcblk0p35
259 4 512 mmcblk0p36
259 5 102400 mmcblk0p37
259 6 10240 mmcblk0p38
259 7 16384 mmcblk0p39
259 8 307200 mmcblk0p40
259 9 204800 mmcblk0p41
259 10 24182784 mmcblk0p42
259 11 5384192 mmcblk0p43
179 32 4096 mmcblk0rpmb
179 64 31166976 mmcblk1
179 65 31162880 mmcblk1p1
The names are missing, however from my first research there is no recovery partition (I guess thats what you're interested in).
Regarding TC'S, 4.8 did not work, 4.9 works fine, haven't tested anything higher though.
i saw this recovery in z5 forum, i've used android kitchen on windows to unpack and edited the lcd density etc in the default.prop and repacked file
but havent done anything to the kernel modules. dont know how to
anyway here's the thing i've done for now. it's the recovery i've played with
https://db.tt/tqhL9Qba
shafiq01 said:
i saw this recovery in z5 forum, i've used android kitchen on windows to unpack and edited the lcd density etc in the default.prop and repacked file
but havent done anything to the kernel modules. dont know how to
anyway here's the thing i've done for now. it's the recovery i've played with
https://db.tt/tqhL9Qba
Click to expand...
Click to collapse
Hey thanks @shafiq01
But that link takes me to a picture of your settings menu.
Thanks @Tommy-Geenexus for the partition table! Thats a great help.
Are you able to get the partition names?
Regards
joeisgood99.
Here is a repack of @AndroPlus TWRP.
Anyone with an E5823 and unlocked bootloader can try it out using:
Code:
fastboot boot recovery.img
I still have no phone, so it is not tested.
Download:
https://mega.nz/#!pgIy2bYR!G-Hemo8rZdh9GBG_hIQOxHnPhdweFZNGpcQdAWPT1t8
All credit to @AndroPlus !
nilezon said:
Here is a repack of @AndroPlus TWRP.
Anyone with an E5823 and unlocked bootloader can try it out using:
Code:
fastboot boot recovery.img
I still have no phone, so it is not tested.
Download:
https://mega.nz/#!pgIy2bYR!G-Hemo8rZdh9GBG_hIQOxHnPhdweFZNGpcQdAWPT1t8
All credit to @AndroPlus !
Click to expand...
Click to collapse
Screen is blank, ADB controls work though.
However mounting /data failed, something must be up with the twrp fstab.
Tommy-Geenexus said:
Screen is blank, ADB controls work though.
However mounting /data failed, something must be up with the twrp fstab.
Click to expand...
Click to collapse
Thank you for testing.
I'll get the phone tomorrow and will fix the bugs then.
Joeisgood99 sorry, i uploaded to dropbox while battery on laptop was dying hehe... socopy wrong url
anyway, now i see nilezon has done it. so no reason to i also try
anyway a bit of topic (but then again we all aim to get root in the smartest way and avoid loss of drm at the same time)
have to wait a bit and see if we in some way can root before unlocking bl
i saw in another thread that if we flash userdebug dev firmware, then we could use adb commands such as 'adb remount' 'adb disable-verity' and then 'adb root'
i'll try to flash userdebug firmware first and see what outcome it gives, hence i have access to that but last time i didn't managed to pack it correctly in flashtool
but i will give it shot more
Related
http://forum.xda-developers.com/showthread.php?t=1010807
I just tested my cappy running Firefly 2.7
R/W speeds were 14.2/4.5 MB/s
When I navigated to the file it said that the cache was 4mb, but upon opening the file to edit it was actually 128kb.
I manually edited the file, to 2mb
speeds went to 29.4/5.0 MB/s
I then edited it to 4072kb
speeds jumped to 29.6/7.8 MB/s
Is this mod something that can be incorporated into the roms?
EDIT: Loading the gallery after these changes is Lightning fast! This is using the internal sd card as well.
I applied the CWM.zip from that thread, but it still reverts to 128kb on reboot.
nickm50 said:
Is this mod something that can be incorporated into the roms?
Click to expand...
Click to collapse
Check out my kernel here
I've included the tweak in the init scripts on boot.
Was this possibly left this way on purpose so as to not fry our internal storage?
HaiKaiDo said:
Was this possibly left this way on purpose so as to not fry our internal storage?
Click to expand...
Click to collapse
no. running sd cards at their rated speed would not damage them.
And to OP, trust me the devs already know. been talking about it in so many threads.. for the past day and a half. welcome to the party!
oh wait you might want to tell the devs that the fix needs to be renamed to S77sdcardspeedfix in the init.d folder or in the zip before flashing for the fix to stay after reboot!!!
Trusselo said:
no. running sd cards at their rated speed would not damage them.
And to OP, trust me the devs already know. been talking about it in so many threads.. for the past day and a half. welcome to the party!
oh wait you might want to tell the devs that the fix needs to be renamed to S77.... for the fix to stay after reboot!!! haha
Click to expand...
Click to collapse
LMAO....Well I tried.....
yeah I just edited my post above so you can fix your reboot
Trusselo said:
yeah I just edited my post above so you can fix your reboot
Click to expand...
Click to collapse
Downloading now ,will try it later after new Dragon ROM.
Been looking forward to some extra boost!
Trusselo said:
yeah I just edited my post above so you can fix your reboot
Click to expand...
Click to collapse
Still not sticking after reboot.
EDIT: my bad forgot to ,mount system R/W
3072kb gives me the best results so far
34.2 read
9.8 write
This seems to be using cache on subsequent runs and getting faster with each run...
Default 128
W: 3.5
R: 21.3
manually set to 2048
W: 3.2
R: 22.8
manually set to 3072
W: 8.0
R: 26.3
manually set to 4096
W: 11.2
R: 78.0
manually set back to 128
W: 11.4
R: 76.6
This will be in the next released Onix, its already in the kernel used for the latest Dragon (its in the kernel (2048) and DAGr8 has it in a script (4096)..his setting overwrite mine, but if you want to use the kernel with a different rom it will set 2048)
If kernel devs dont want to add it in init.rc or as a script in init.d, you can add it straight in the source
https://github.com/existz/linux_gt-i9000/commit/05172cf5f0c8182dccad36b023383a889cfc3e27
joeybear23 said:
This seems to be using cache on subsequent runs and getting faster with each run...
Default 128
W: 3.5
R: 21.3
manually set to 2048
W: 3.2
R: 22.8
manually set to 3072
W: 8.0
R: 26.3
manually set to 4096
W: 11.2
R: 78.0
manually set back to 128
W: 11.4
R: 76.6
Click to expand...
Click to collapse
Instructions for the program say to exit out completely and restart it for each run . Or you will get results like that.
existz said:
This will be in the next released Onix, its already in the kernel used for the latest Dragon (its in the kernel (2048) and DAGr8 has it in a script (4096)..his setting overwrite mine, but if you want to use the kernel with a different rom it will set 2048)
If kernel devs dont want to add it in init.rc or as a script in init.d, you can add it straight in the source
https://github.com/existz/linux_gt-i9000/commit/05172cf5f0c8182dccad36b023383a889cfc3e27
Click to expand...
Click to collapse
eXistZ, will you include this in your eXistZ KB1 Beta kernel as well ? Would be nice !
TheGrub said:
eXistZ, will you include this in your eXistZ KB1 Beta kernel as well ? Would be nice !
Click to expand...
Click to collapse
Yep, ill have it in all my kernels once I update them (kinda waiting around on next voodoo sound version before updating my kb1 and sp-voodoo)
So many threads on this.... Wth =.="
nickm50 said:
Instructions for the program say to exit out completely and restart it for each run . Or you will get results like that.
Click to expand...
Click to collapse
Got it.
Menu > Exit... not just close, or back.
Warning! Posted with Swype.
...and yes, I bought the premium app.
Hello
I post my problem here because i am new and so cannot use the official threads in dev part...
So I just install the topogigi 1.7 release and now each time I try to access the market to install anything it fail with a message that my device to not have enough free space.
As it's a fresh install, it's of course not the case ...
I did a df using adb, /data as 1Gb free ...
df
Filesystem Size Used Free Blksize
/dev 185M 32K 185M 4096
/mnt/asec 185M 0K 185M 4096
/mnt/obb 185M 0K 185M 4096
/system 338M 283M 55M 1024
/data 1G 92M 1G 4096
/mnt/extasec 185M 0K 185M 4096
/lgdrm 2M 2M 398K 2048
/mnt/sdcard 5G 874M 4G 32768
/mnt/secure/asec: Permission denied
/mnt/sdcard/_ExternalSD 3G 2G 1G 32768
/mnt/extsecure/extasec: Permission denied
Any ideas ?
thanks
Hi,
Yes, this a known problem, do a reboot after the first configurations, and all will be ok then.
It's probably not enough space on /cache that it's complaining about.
Indeed, I reboot the phone and now market is ok to install software
I did not find that info in the original post (which is quite huge I must agree)
Thanks for your answer
if you want to know, open your build.prop file and look for a line that starts:
ro.build.fingerprint
Here is what CM uses:
Code:
ro.build.fingerprint=lge/lge_star/p990/p990:2.2.2/FRG83G/lgp990-V10b.2ED2ADCFFC:user/release-keys
Rusty! said:
if you want to know, open your build.prop file and look for a line that starts:
ro.build.fingerprint
Here is what CM uses:
Code:
ro.build.fingerprint=lge/lge_star/p990/p990:2.2.2/FRG83G/lgp990-V10b.2ED2ADCFFC:user/release-keys
Click to expand...
Click to collapse
So if I just edit the build.prop file, will I get access the all the apps that have been missing from the market? It's a weird mix that is missing - various games like NOVA2, and even the tvguide.co.uk app.
If this works, your'e a hero!
I actually meant to put that in the other Topogigi Market problem thread, but yeah you might well find it fixes that.
Thanks for your help, will try this later
Rusty! said:
if you want to know, open your build.prop file and look for a line that starts:
ro.build.fingerprint
Here is what CM uses:
Code:
ro.build.fingerprint=lge/lge_star/p990/p990:2.2.2/FRG83G/lgp990-V10b.2ED2ADCFFC:user/release-keys
Click to expand...
Click to collapse
I noticed that Paul spoofs the Nexus S fingerprint in his Gr2
ro.build.fingerprint=google/soju/crespo:2.3.4/GRJ22/121341:user/release-keys
Will that give a better range of market compatibility or will I lose Tegra specific apps? There is a ro.board.platform=tegra so that might take care of that.
I guess I'll just experiment.... but it's amazing how much you can learn from a few tweaking experts here on XDA.... one day I'll have to try doing a proper custom rom for myself
rmein said:
I guess I'll just experiment
Click to expand...
Click to collapse
That's the best option.
Even with the 2.2.2 CM fingerprint, I had no trouble getting Sprinkle from the Market, which requires 2.3
Rusty! said:
That's the best option.
Even with the 2.2.2 CM fingerprint, I had no trouble getting Sprinkle from the Market, which requires 2.3
Click to expand...
Click to collapse
Experimentation done!
Spoofed Nexus S and CM fingerprint won't let me download Galaxy on Fire or Sprinkle and can't even find NOVA2, but tvguide.co.uk is OK.
Back to Fr19 Let's hope Paul's Gr3 will help me out.
Misread, oops!
Sorry what is this topigigi?
Sent from my Optimus 2X using Tapatalk
Workaround mabye
rmein said:
Experimentation done!
Spoofed Nexus S and CM fingerprint won't let me download Galaxy on Fire or Sprinkle and can't even find NOVA2, but tvguide.co.uk is OK.
Back to Fr19 Let's hope Paul's Gr3 will help me out.
Click to expand...
Click to collapse
You can install tegra games from the www marked, just installed sprinkle
@hd2000
Topogigi is a custom rom, one of the best I would say (IMO)
http://forum.xda-developers.com/showthread.php?t=1254359
kernel sources for Xperia Z (SO-02E) {FW: 10.1.D.0.317} & C660x are {FW: 10.1.A.1.350} [these work for Xperia ZL too] available...
link to download sources:
http://dl-developer.sonymobile.com/code/copylefts/10.1.D.0.317.tar.bz2
http://dl-developer.sonymobile.com/code/copylefts/10.1.A.1.350.tar.bz2
i will post build instructions for developers who plan to work on this device....
Building kernel (zImage):
for Xperia Z (C6600x):
import defconfig
Code:
ARCH=arm CROSS_COMPILE=~/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- make fusion3_yuga_defconfig
for Xperia ZL (C6500x):
import defconfig
Code:
ARCH=arm CROSS_COMPILE=~/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- make fusion3_odin_defconfig
build zImage
Code:
ARCH=arm CROSS_COMPILE=~/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- make -j8
incase u get errors like:
Code:
error : /scripts/gcc-wrapper.py
just correct the permissions of that file
Code:
chmod 777 ./scripts/gcc-wrapper.py
regards,
DooMLoRD
Instructions for building kernel.elf
Instructions for building boot.img
first get the kernel built... once kernel is built u will get zImage and copy that zImage to the folder containing the mkbootimg files...
i am attaching a tar file which contains the correct mkbootimg binary and a shell script to build this boot.img
Sony has switched to a standard kernel (boot.img) format...
only issue is that the bootloader does not allow hotbooting of kernels
Code:
[I]fastboot boot boot.img[/I]
does not work
build boot.img
u can directly use the attached files
or
use the following command:
Code:
mkbootimg --kernel zImage --ramdisk ramdisk.img --pagesize 2048 --base 0x80200000 \
--cmdline "androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 vmalloc=400M androidboot.emmc=true" \
--offset 0x02000000 --output boot.img
Re: [Kernel-Sources] Xperia Z (SO-02E) {FW: 10.1.D.0.317}
I have made 10.1.A.1.350 ftf
Only need to upload one more part, but I'm not home now. I'll upload it on sunday
Sent from my LT26i using xda app-developers app
Re: [Kernel-Sources] Xperia Z (SO-02E) {FW: 10.1.D.0.317}
hey doom, good to see you around again been a while since the x10
Sent from my Transformer Prime TF201 using xda premium
Hawkysoft said:
hey doom, good to see you around again been a while since the x10
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
hey Hawkysoft! LONG time no see
@ALL
seems we have a new type of kernel.elf for the Xperia Z/ZL...
it only contains zImage and ramdisk.cpio.gz
i am guessing that the following build command should work:
Code:
python mkelf.py -o kernel.elf [email protected] [email protected],ramdisk
this information might be valid only for the Xperia ZL as the file i received were for that device...
Code:
10.1.A.1.350-C65
ro.semc.version.sw=1266-7597
ro.semc.version.sw_revision=10.1.A.1.350
since i do not have the Xperia Z/ZL i need some testers... please send me kernel.sin which works for your device so that we can do testing...
Re: [Kernel-Sources] Xperia Z (SO-02E) {FW: 10.1.D.0.317}
Good to see you DoomLord, following you since X10..ditched you after Xperia S
Now waiting for my Xperia Z, will be getting on 28th Feb..
sent from Giant Killer Galaxy Note 2
xperiax10.awesome said:
Good to see you DoomLord, following you since X10..ditched you after Xperia S
Now waiting for my Xperia Z, will be getting on 28th Feb..
sent from Giant Killer Galaxy Note 2
Click to expand...
Click to collapse
glad to see u here
u still have the same nick>> X10 awesome
i really like the xperia Z but i dont have the money to buy it... its too costly for me...
@ALL
did a lot of testing today thanks to one user over teamviewer... bootloader unlock is easy, we got full FTF flashed (updated FlashTool)... just the damn kernel is the issue... seems Z is using a standard boot.img format... but i havent been able to get the correct parameters, commands to get the damn boot.img to boot...
DooMLoRD said:
glad to see u here
u still have the same nick>> X10 awesome
i really like the xperia Z but i dont have the money to buy it... its too costly for me...
@ALL
did a lot of testing today thanks to one user over teamviewer... bootloader unlock is easy, we got full FTF flashed (updated FlashTool)... just the damn kernel is the issue... seems Z is using a standard boot.img format... but i havent been able to get the correct parameters, commands to get the damn boot.img to boot...
Click to expand...
Click to collapse
Hi Doomlord, nice to see you here.
Planning to hack some Kernels for the device. I would probably buy it after March.
Can you send me the boot.img? I've downloaded the sources.
Also, if we could get a dump of /proc/partitions , we could probably figure out the size of the boot partition. (Misread your comment)
Cheers.
Re: [Kernel-Sources] Xperia Z (SO-02E) {FW: 10.1.D.0.317}
Offtopic
Hey doom-. I just bought nexus 4 fr 23k.. Believe me its a great phone. If not xz dn plz buy nexus 4...
Sent from my Nexus 4 using xda app-developers app
Re: [Kernel-Sources] Xperia Z (SO-02E) {FW: 10.1.D.0.317}
Adi_Pat said:
Hi Doomlord, nice to see you here.
Planning to hack some Kernels for the device. I would probably buy it after March.
Can you send me the boot.img? I've downloaded the sources.
Also, if we could get a dump of /proc/partitions , we could probably figure out the size of the boot partition. (Misread your comment)
Cheers.
Click to expand...
Click to collapse
I am posting some info which should be useful...
FOR XPERIA Z (C660x)
Code:
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/platform/msm_sdcc.1/by-name/system on /system type ext4 (ro,relatime,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/userdata on /data type ext4 (rw,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type ext4 (rw,nosuid,nodev,relatime,discard,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/LTALabel on /lta-label type ext4 (ro,nosuid,nodev,noexec,noatime,nobarrier,data=ordered)
tmpfs on /mnt/qcks type tmpfs (rw,relatime,mode=770,uid=1000,gid=1000)
/dev/block/platform/msm_sdcc.1/by-name/apps_log on /data/idd type ext4 (rw,nosuid,nodev,noexec,noatime,discard,nobarrier,data=ordered)
/dev/fuse on /storage/sdcard0 type fuse (rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/vold/179:33 on /storage/sdcard1 type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 941876 68 941808 0% /dev
tmpfs 941876 0 941876 0% /mnt/asec
tmpfs 941876 0 941876 0% /mnt/obb
/dev/block/platform/msm_sdcc.1/by-name/system
2067560 1026752 1040808 50% /system
/dev/block/platform/msm_sdcc.1/by-name/userdata
12301652 2967792 9333860 24% /data
/dev/block/platform/msm_sdcc.1/by-name/cache
554908 9856 545052 2% /cache
/dev/block/platform/msm_sdcc.1/by-name/LTALabel
16164 4740 11424 29% /lta-label
tmpfs 941876 5432 936444 1% /mnt/qcks
/dev/block/platform/msm_sdcc.1/by-name/apps_log
8100 4292 3808 53% /data/idd
/dev/fuse 12301652 2967792 9333860 24% /storage/sdcard0
/dev/block/vold/179:33
15537664 526752 15010912 3% /storage/sdcard1
lrwxrwxrwx root root 1970-01-11 04:46 FOTAKernel -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-11 04:46 LTALabel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-11 04:46 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-11 04:46 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-11 04:46 alt_aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-11 04:46 alt_rpm -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-11 04:46 alt_s1sbl2 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-11 04:46 alt_sbl1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-11 04:46 alt_sbl2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-11 04:46 alt_sbl3 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-11 04:46 alt_tz -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-11 04:46 apps_log -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-11 04:46 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-11 04:46 cache -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-11 04:46 m9kefs1 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-11 04:46 m9kefs2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-11 04:46 m9kefs3 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-11 04:46 ramdump -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-11 04:46 rpm -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-11 04:46 s1sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-11 04:46 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-11 04:46 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-11 04:46 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-11 04:46 system -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-11 04:46 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-11 04:46 userdata -> /dev/block/mmcblk0p26
varshil said:
Offtopic
Hey doom-. I just bought nexus 4 fr 23k.. Believe me its a great phone. If not xz dn plz buy nexus 4...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have played with the Nexus 4... It's good but it's LG...
Sent from my LT30p using xda app-developers app
Re: [Kernel-Sources] Xperia Z (FW: 10.1.D.0.317, 10.1.A.0.350)
10.1.A.0.350 sources out!!!
Sent from my LT30p using xda app-developers app
Re: [Kernel-Sources] Xperia Z & ZL (FW: 10.1.A.0.350)
Dear doomlord,
I m following you (and krabbel from my x10 (to arcs xs xt and now xz in 3 days)
Love your work...
I'm not a developer, just someone who love stock Sony, and even more if it's not totally stock.
I see the development didn't started yet, is it hard for a development noop to start? Just to create a deodext Rom with root (just like krabbels on the xt). Can you please point me in the right way? If I can understand it I will try to start something, (if I don't get it I will wait patiently)
Love your work mate!!
Sent from my LT30p using xda premium
Re: [Kernel-Sources] Xperia Z & ZL (FW: 10.1.A.0.350)
yaabaa1986 said:
Dear doomlord,
I m following you (and krabbel from my x10 (to arcs xs xt and now xz in 3 days)
Love your work...
I'm not a developer, just someone who love stock Sony, and even more if it's not totally stock.
I see the development didn't started yet, is it hard for a development noop to start? Just to create a deodext Rom with root (just like krabbels on the xt). Can you please point me in the right way? If I can understand it I will try to start something, (if I don't get it I will wait patiently)
Love your work mate!!
Sent from my LT30p using xda premium
Click to expand...
Click to collapse
Check xda university.
Sent from my C6603 using xda app-developers app
DooMLoRD said:
glad to see u here
....
i really like the xperia Z but i dont have the money to buy it... its too costly for me...
Click to expand...
Click to collapse
Hi, Doom! I am glad to read your posts again since x10)).
can again repeat that?
yaabaa1986 said:
Dear doomlord,
I m following you (and krabbel from my x10 (to arcs xs xt and now xz in 3 days)
Love your work...
I'm not a developer, just someone who love stock Sony, and even more if it's not totally stock.
I see the development didn't started yet, is it hard for a development noop to start? Just to create a deodext Rom with root (just like krabbels on the xt). Can you please point me in the right way? If I can understand it I will try to start something, (if I don't get it I will wait patiently)
Love your work mate!!
Sent from my LT30p using xda premium
Click to expand...
Click to collapse
well to begin with the device isnt yet globally available... most devs who plan to buy the device havent got it yet...
if u want to create de-odexed ROM you will have to wait for proper recovery to be posted (FYI from what i know recovery is already working just not released yet)...
if u interested please search... lots of threads for that...
TangVLD said:
Hi, Doom! I am glad to read your posts again since x10)).
can again repeat that?
Click to expand...
Click to collapse
thanks! good to see ppl from the X10 days...
about that... well depends on community...
DooMLoRD said:
thanks! good to see ppl from the X10 days...
about that... well depends on community...
Click to expand...
Click to collapse
From paypal:
"Currently PayPal accounts in India are only able to send payments. This recipient is not eligible to receive funds"
TangVLD said:
From paypal:
"Currently PayPal accounts in India are only able to send payments. This recipient is not eligible to receive funds"
Click to expand...
Click to collapse
Please try this
and thanks in advance!
DooMLoRD said:
Please try this
and thanks in advance!
Click to expand...
Click to collapse
I did. Still 20 people would have done the same thing)
TangVLD said:
I did. Still 20 people would have done the same thing)
Click to expand...
Click to collapse
wow! thank you for your generous donation!
damn i should have corrected the donation link before and thanks a lot for pointing that out!
Re: [Kernel-Sources] Xperia Z & ZL (FW: 10.1.A.0.350)
yaabaa1986 said:
Dear doomlord,
I m following you (and krabbel from my x10 (to arcs xs xt and now xz in 3 days)
Love your work...
I'm not a developer, just someone who love stock Sony, and even more if it's not totally stock.
I see the development didn't started yet, is it hard for a development noop to start? Just to create a deodext Rom with root (just like krabbels on the xt). Can you please point me in the right way? If I can understand it I will try to start something, (if I don't get it I will wait patiently)
Love your work mate!!
Sent from my LT30p using xda premium
Click to expand...
Click to collapse
I'll have mine on wednesday probably
Sent from my Xperia S using xda app-developers app
Hello,
I have a problem to enable fast charging.
Using PROMETHEUS KERNEL(Version7- Linaro(on speed 767)) and as I checked "FAQ & SOURCES" in that thread this option is allowed by siple modification:
"echo 1 > /sys/class/power_supply/battery/fast_charge"
But I am not allowed write to "/sys/class/power_supply/battery/", return error is:
"cannot create /sys/class/power_supply/battery/fast_charge: No such file or directory"
Directory "/sys/class/power_supply/battery" exist, but I don't have a permission write.
Any idea why I cannot do this?
Did you type 'su' in the terminal?
Sent from my HTC Desire C using XDA Premium 4 mobile app
smoza said:
Did you type 'su' in the terminal?
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, this is complete command which using:
[email protected]:/ # su
[email protected]:/ # echo 1 > /sys/class/power_supply/battery/fast_charge
sh: cannot create /sys/class/power_supply/battery/fast_charge: No such file or directory
1|[email protected]:/ #
but of course, directory exists:
130|[email protected]:/ # ll /sys/class/power_supply/battery/
-rw--w---- root root 4096 2013-09-06 13:45 audio_stat
-r--r--r-- root root 4096 2013-09-06 13:45 batt_attr_text
-r--r--r-- root root 4096 2013-09-06 13:45 batt_current
--w--w---- root root 4096 2013-09-06 13:45 batt_debug_flag
-r--r--r-- root root 4096 2013-09-06 13:45 batt_id
.....
I'm sorry but I really don't know how to help you
Sent from my HTC Desire C using XDA Premium 4 mobile app
BlaMa said:
Hello,
I have a problem to enable fast charging.
Using PROMETHEUS KERNEL(Version7- Linaro(on speed 767)) and as I checked "FAQ & SOURCES" in that thread this option is allowed by siple modification:
"echo 1 > /sys/class/power_supply/battery/fast_charge"
But I am not allowed write to "/sys/class/power_supply/battery/", return error is:
"cannot create /sys/class/power_supply/battery/fast_charge: No such file or directory"
Directory "/sys/class/power_supply/battery" exist, but I don't have a permission write.
Any idea why I cannot do this?
Click to expand...
Click to collapse
I talked with nikhil (the maker of Prometheus ) and he told me that he will enable it in the next version then he left it was like a month ago or before so I think you must do something inside the kernel to enable it then you must type what you said above
Edit: I meant cm10 kernel not sense
webhijacker said:
I talked with nikhil (the maker of Prometheus ) and he told me that he will enable it in the next version then he left it was like a month ago or before so I think you must do something inside the kernel to enable it then you must type what you said above
Edit: I meant cm10 kernel not sense
Click to expand...
Click to collapse
Hello, thank you for explanation.
I am using Sense version, but maybe this is a reason why I can not use this feature.
Due my account limitation, I can send my post only in this general forum and not directly in Prometheus kernel thread.
Say my thanks also to developer and thank you one more time.
Hi i want to port android one (sprout) rom to another media tek based devices .Any help will be appreciated.
Hello Ab200000,
This is a lecagy boot.img, MTKIMG dont work on it because there is no MTK header at the begining of each bloc.
I will modify MTKIMG to handle this case but for tide you i manually unpack kernel and ramdisk.
In the next message i will explain you how i do
Hop this help you (Dont forgot to click on thank button )
To manually extract your boot.img this is how i do :
I use mtkimg to get the image layout
Code:
> mtkimg.exe info boot.img
MTKIMG V0.44(win64) by rom1nux
Image header :
Signature : ANDROID!
Kernel size : 4931048 bytes
Kernel load address : 0x80008000
Ramdisk size : 1075216 bytes
Ramdisk load address : 0x84000000
Second stage size : 0 bytes
Second stage load address : 0x80F00000
Tags address : 0x80000100
Page size : 2048 bytes
Product name : ''
Command line : ''
ID : 12FF85BE30433CB9FCDBF9C90DC5EE8BCBC70C04
Image layout :
Bloc Offset Pages Size (bytes)
------------------------------------------------
Header 0x00000000 1 2048
Kernel 0x00000800 2408 4931584
Ramdisk 0x004B4800 526 1077248
Free 0x005BB800 2185 4474880
------------------------------------------------
Total 5120 10485760
------------------------------------------------
With an hexadecimal editor i extract kernel from 0x800 to 0x4B4800 from boot.img
I check for valid kernel at offset 0x24 we need to find magic 0x18 0x28 0x6F 0x01, good it's a "Linux ARM zImage"
With an hexadecimal editor i extract ramdisk from 0x4B4800 to 0x5BB800 from boot.img
I check for valid gzip at offset 0x00 we need to find magic 0x1F 0x8B, good it's a cpio.gz
I try to extract the ramdisk, no error, well, all good
I will modify mtkimg soon as possible
Hope this help you
(Dont forget to click on thank button)
Thank you for this
rom1nux said:
To manually extract your boot.img this is how i do :
I use mtkimg to get the image layout
Code:
> mtkimg.exe info boot.img
MTKIMG V0.44(win64) by rom1nux
Image header :
Signature : ANDROID!
Kernel size : 4931048 bytes
Kernel load address : 0x80008000
Ramdisk size : 1075216 bytes
Ramdisk load address : 0x84000000
Second stage size : 0 bytes
Second stage load address : 0x80F00000
Tags address : 0x80000100
Page size : 2048 bytes
Product name : ''
Command line : ''
ID : 12FF85BE30433CB9FCDBF9C90DC5EE8BCBC70C04
Image layout :
Bloc Offset Pages Size (bytes)
------------------------------------------------
Header 0x00000000 1 2048
Kernel 0x00000800 2408 4931584
Ramdisk 0x004B4800 526 1077248
Free 0x005BB800 2185 4474880
------------------------------------------------
Total 5120 10485760
------------------------------------------------
With an hexadecimal editor i extract kernel from 0x800 to 0x4B4800 from boot.img
I check for valid kernel at offset 0x24 we need to find magic 0x18 0x28 0x6F 0x01, good it's a "Linux ARM zImage"
With an hexadecimal editor i extract ramdisk from 0x4B4800 to 0x5BB800 from boot.img
I check for valid gzip at offset 0x00 we need to find magic 0x1F 0x8B, good it's a cpio.gz
I try to extract the ramdisk, no error, well, all good
I will modify mtkimg soon as possible
Hope this help you
(Dont forget to click on thank button)
Click to expand...
Click to collapse
Thank you rom1nux
I appreciate the work you done on this mediatek boot.img . I hope i can port rom now without any problem.
Yes it will be helpful if you include this method in your future mtkimg tool. As it will increase the porting possibilities android one roms
Mtk 6582 KitKat 4.4.4 miui rom available ,is it possible to port for android one
android one uses
android one uses legacy boot.img
sheshank said:
Mtk 6582 KitKat 4.4.4 miui rom available ,is it possible to port for android one
Click to expand...
Click to collapse
@Ab20000
I guess you could also try AIK for unpacking stock boot.img. I was able to unpacked sprout recoveries without any issue
1cefire said:
@Ab20000
I guess you could also try AIK for unpacking stock boot.img. I was able to unpacked sprout recoveries without any issue
Click to expand...
Click to collapse
do you have any android one device? Does it have alarm function even when the phone is powered off? As other media tek phones have it.
I want to port android one rom to other mediatek based soc of mine. I am not sure what else i need to besides editing ramdisk, using device's original kernel , fixing updater script , original specific drivers and what else?
Ab20000 said:
do you have any android one device? Does it have alarm function even when the phone is powered off? As other media tek phones have it.
I want to port android one rom to other mediatek based soc of mine. I am not sure what else i need to besides editing ramdisk, using device's original kernel , fixing updater script , original specific drivers and what else?
Click to expand...
Click to collapse
yes, one of the sprout4 variant. I haven't had any chance to verify if the alarm function is working while powered off. Sorry dude, i wish i could help you, but my porting abilities is very limited Better ask ricky_adhitya, as i was saying, he was able to port RR 5.1.1 to other mtk6582 devices
I will contact him,
1cefire said:
yes, one of the sprout4 variant. I haven't had any chance to verify if the alarm function is working while powered off. Sorry dude, i wish i could help you, but my porting abilities is very limited Better ask ricky_adhitya, as i was saying, he was able to port RR 5.1.1 to other mtk6582 devices
Click to expand...
Click to collapse
Thanks for the boot.img method, did anyone succed to make it work ? (Ex with CM12.1 port from Spout)
I'll try this when im at home.
I usually use this tutorial for porting LL : http://mtkromsxda.blogspot.fi/2015/08/how-to-port-cm12cm121-lollipop-based.html
But i just found this !! : http://techintact.com/how-to-port-cm-12-1-for-mt6582-from-android-one/
Ill try them when im home
Ab20000 said:
Hi i want to port android one (sprout) rom to another media tek based devices .Any help will be appreciated.
Click to expand...
Click to collapse
Can you help me to port Android one marshmallow update to port into mt6582 running Lollipop based phone using kernel 3. 10. x? please email me at [email protected]