yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Original Android Development] Phil3759:
When you actually repack my ramdisk with stock kernel into a boot.img, do you keep these files from my ramdisk:

Also, do you keep my ueventd stuff or you need to replace with what comes with stock boot.img?

Also, the init.rc from my ramdisk and many files that are in the root are required. I did not see how you are repacking, but take a look at my work on i9100 or even better on Siyah kernel work. He uses a fake init to decide what init.rc to load for each session
[Xperia Z1 Original Android Development] [NUT]:
[MENTION=4666971]Phil3759[/MENTION] and [MENTION=4675598]shoey63[/MENTION]

I've cracked it, I found the way to set the stock kernel to SELinux=permissive on the Sony kernel by controlling the sysfs entry.

Sony has no SELinux configuration AT ALL, file contexts are unset. But from the moment the kernel boots, SELinux is set to enforcing while sony themselves set it to permissive at some point.

The entry point for the locked bootloader recovery is too early so I need to write a 0 in to /sys/fs/selinux/enforce during the on init in the init.rc and Philz will be able to use minivold to mount the sdcard1 regardless of the used filesystem :victory:
[Xperia Z1 Original Android Development] Phil3759:
Good catch :good:

Sony sucks and you rock LoL
[Xperia Z1 Original Android Development] shoey63:
Problem solved! [MENTION=4904057][NUT][/MENTION] has delivered a "Master Stroke " by adding this to "on-init" in "init.rc"

write /sys/fs/selinux/enforce 0

Works perfectly on his dual recovery script for locked bootloader and unmodified stock boot.img :victory:
[Xperia Z1 Original Android Development] Phil3759:
I really appreciate sony community with many devs/advanced users working on the support

:good:
[Xperia Z1 Original Android Development] [NUT]:
[MENTION=4666971]Phil3759[/MENTION]

/dev/block/vold/179:65 on /storage/sdcard1 type fuseblk (rw,dirsync,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096)

It's working, but not as we expected on the honami: it's using fuse to mount the exfat card... is that done intentionally?

On the yuga it does use the texfat mount...
[Xperia Z1 Original Android Development] Phil3759:
Use minivold from the ramdisk i posted link to, on devhost
[Xperia Z1 Original Android Development] [NUT]:
I'll try that once more... Not sure if I'm still using that or the one from the goo.im hosting... :eek:

I'll let you know how it performs.
[Xperia Z1 Original Android Development] [NUT]:
Well, done that, but the minivold from the dev-host version doesn't want to play ball at all: It is unable to mount the sdcard and it does not mount a USB OTG drive either.

Using the one in the goo.im release does work, but it is using fuse as I said before.

When trying to use the whole ramdisk from dev-host it has the same problems ( and it's clearly a version from before the brightness fix :D )

---------- Post added at 12:33 AM ---------- Previous post was at 12:11 AM ----------

[MENTION=4675598]shoey63[/MENTION] had a stroke of genius himself, suggested to use the one from the yuga build...

And that one works!! :D

/dev/block/vold/179:65 on /storage/sdcard1 type texfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,umask=0007,allow_utime=0020,nls=utf8,min_prealloc_size=64k,readahead=4M,fail_safe,discard,errors=continue)

:highfive:

---------- Post added at 12:45 AM ---------- Previous post was at 12:33 AM ----------

:D

Backup time in PhilZ on the Z1, with fuse took over 12minutes for 2600MB

with texfat, just under 7 minutes!

Same slow exfat sdcard :good:
[Xperia Z1 Original Android Development] Phil3759:
Thanks for the feedback

I will enable texfat use on compile time

If next update still fails and you need minivold from yuga, let me know
[Xperia Z1 Original Android Development] [NUT]:
Will do :good: :)
[Xperia Z1 Original Android Development] Phil3759:
Uploaded repack with stock kernel, credits to DooMLoRD

philz_touch_6.12.8-honami-FIXED-4.3_fw-290.img
[Xperia Z1 Original Android Development] DooMLoRD:
i already added the new 6.12.8 ramdisk in my kernel...

btw there is a new stock firmware (14.2.A.1.136) available :)

here are the split parts for it...
[Xperia Z1 Original Android Development] Phil3759:
you are an angel :angel:
[Xperia Z1 Original Android Development] Phil3759:
Uploaded on goo.im:

philz_touch_6.12.8-honami-FIXED-fw-C6902_14.2.A.1.136.img
[Xperia Z1 Original Android Development] mohanparvatham:
not working on 14.2.A.1.136....Every time getting rebooted to recovery only....Not able to getting into system.....
[Xperia Z1 Original Android Development] DooMLoRD:
thats how its supposed to work :)
[Xperia Z1 Original Android Development] Black_halo:
Hey guys. New to honami with the c6906 on AT&T but I just want to clarify some things because I've been familiar with Motorola with philz touch so long and switching to Sony seems so new but any way we're suppose to:

1. Download & flash CWM

2. Flash philz touch over CWM recovery

3. Unlock bootloader

4. Then install custom rom of choosing?

I've read through the forums and I saw things about .img and .dt files so are there any extra steps? I don't want to be on stock and I don't want to brick either. Sorry if I sound like a noob but these are the only steps I took with flashing on Motorola and just seeking clarity.
[Xperia Z1 Original Android Development] juicio90:
Can't take a backup, with the lasted version. I have CM 11, and everything work fine, just can't make a backup to SD ext...
[Xperia Z1 Original Android Development] [NUT]:
[MENTION=4666971]Phil3759[/MENTION]

I'm afraid something broke in PhilZ Touch 6.26.1 at least:

recovery.log snippet:

I:show_background_icon set to default (false)
overlay_display_frame failed, overlay commit Failed
!: Function not implemented
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented
I:show_battery set to default (true)
[SNIP]
overlay_display_frame failed, overlay commit Failed
!: Function not implemented
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented
overlay_display_frame failed, overlay commit Failed
!: Function not implemented
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented
overlay_display_frame failed, overlay commit Failed
!: Function not implemented
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented
Overlay Set Failed: Out of memory
[SNIP]
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented
Overlay Set Failed: Out of memory
display_frame failed, no overlay
: Out of memory
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented

This is true for the Z1, Z1 Compact and Z Ultra...

Have any idea what might be wrong?

Touch events seem to get registered and using the buttons actually performs actions. It's just not putting anything on screen.

[MENTION=4675598]shoey63[/MENTION] for reference
[Xperia Z1 Original Android Development] Phil3759:
Disabe the qcom msm flag or such

No pc to verify exact name

Probably not implemented in stock kernel or custom graphics.c you use
[Xperia Z1 Original Android Development] [NUT]:
Okay, will try to find it.

---------- Post added at 06:35 PM ---------- Previous post was at 06:30 PM ----------

@Phil3759

# inherit from Sony common
include device/sony/common/BoardConfigCommon.mk

BOARD_EGL_CFG := device/sony/rhine-common/rootdir/system/lib/egl/egl.cfg

# inherit from qcom-common
include device/sony/qcom-common/BoardConfigCommon.mk

TARGET_SPECIFIC_HEADER_PATH := device/sony/rhine-common/include

# Kernel properties
TARGET_KERNEL_SOURCE := kernel/sony/msm8974

# Platform
TARGET_BOOTLOADER_BOARD_NAME := MSM8974
TARGET_BOARD_PLATFORM := msm8974
BOARD_VENDOR_PLATFORM := rhine

[SNIP]

# Qualcomm
BOARD_USES_QCOM_HARDWARE := true
BOARD_USES_QC_TIME_SERVICES := true
TARGET_USES_QCOM_BSP := true
TARGET_ENABLE_QC_AV_ENHANCEMENTS := true
TARGET_QCOM_AUDIO_VARIANT := caf
TARGET_QCOM_DISPLAY_VARIANT := caf-new
TARGET_QCOM_MEDIA_VARIANT := caf-new

Which one are you refering to?
[Xperia Z1 Original Android Development] Phil3759:
TARGET_USES_QCOM_BSP

remove / comment that line
[Xperia Z1 Original Android Development] [NUT]:
Will try to build it later tonight, thanks, will update you on the subject after some testing.
[Xperia Z1 Original Android Development] Phil3759:
do not forget to make clobber after that or at least remove all minui intermediates

Not sure if more cleaning is needed before building again. Start with minui, then maybe a clobber if it fails
[Xperia Z1 Original Android Development] [NUT]:
:victory:

It works again!!

Thanks for the help! :highfive:
[Xperia Z1 Original Android Development] juicio90:
[MENTION=1390705]Phil37[/MENTION]can you check this log? https://www.dropbox.com/s/ht947kckgqzyira/philz_recovery.log
[Xperia Z1 Original Android Development] Phil3759:
read the FAQ
[Xperia Z1 Original Android Development] juicio90:
Have problem with upload from my cellphone...
[Xperia Z1 Original Android Development] Phil3759:
it is related to cm updater and /data/media path they use

There is a toggle for cm users
[Xperia Z1 Original Android Development] juicio90:
Sorry, but I'm nooby ... Where is it?

Edit: I found it... Man.. I really appreciated your work :thumbup:. Thanks for you help. Now it is working !!! :D Sorry for my bad English. Thank you very much!
[Xperia Z1 Original Android Development] acabreram:
Hi could you dev this for Xperia Z1 Compact please!! I know that there is a locked dual recovery and is a excelente work but i never use TWRP

and cwm has some bugs for example when you make a back up don´t show progress and you don´t know if is stuck or what.

Please Dev this for stock Kerner and custom.

Thanks!!
[Xperia Z1 Original Android Development] madalone:
can someone please make a build with f2fs?
[Xperia Z1 Original Android Development] DooMLoRD:
hi can you please post the latest ramdisks for:

honami

sirius

yuga

huashan

mint

thanks!
[Xperia Z1 Original Android Development] Phil3759:
As you maybe know, I really have no more time to build for devices

I barely maintain sources so that they keep compiling until CWM is completely dead project

I only build for jflte, the device I use and need

Really sorry
[Xperia Z1 Original Android Development] DooMLoRD:
no worries mate...
[Xperia Z1 Original Android Development] lukensteinz:
Hi guys. I'd be willing to have a go at maintaining sources.
[Xperia Z1 Original Android Development] shoey63:
Here you go - just remove the fake "..img" extensions ;)

View attachment yuga-recovery.cpio.img

View attachment mint-recovery.cpio.img

View attachment honami-recovery.cpio.img

View attachment sirius-recovery.cpio.img

View attachment huashan-recovery.cpio.img
[Xperia Z1 Original Android Development] LSD DREAMER:
So I install the image file like I would a kernel

Sent from my Xperia Z1
[Xperia Z1 Original Android Development] shoey63:
Nope. Cpio needs to be inserted into a custom boot.img (ie: unpack boot.img, replace ramdisk-recovery.cpio and repack)
[Xperia Z1 Original Android Development] LSD DREAMER:
How can I flash the img file on the op. Tried to follow the install instructions but my cm does not give the same options

Sent from my Xperia Z1
[Xperia Z1 Original Android Development] ->---:
I made it work with that and it has not been replaced since many ROM flashes:

http://xdaforums.com/showpost.php?p=52501509&postcount=990

Maybe it will work for others too?
[General Questions and Answers] byseby:
I have an Alcatel one touch idol mini and messed it up trying to flash something while the device was on and now i need a way to flash stock rom for it and a stock rom if you can(i'm noob whit things like this) i can get to the stock recovery mode and i need a software to flash rom back and the rom... i have downloaded something but i don't know if it is what i need... it is a .tar.xz file(opened with winrar)

P.S.: My device is locked to Orange Romania
[General Questions and Answers] guifort:
You should use this : http://www.alcatelonetouch.com/fr/downloads/otu/mobile-upgrade-s-4-0-6-setup.exe
[General Questions and Answers] SprintyCell:
Thanks, but this don't work for my phone (an other operator (Sosh)), do you have another idea please ?

Thanks
[Defy Q&A, Help & Troubleshooting] measel:
Is there a way to resolve the Android Domain Name (or is it host name?) with SAMBA?

I use "Samba Filesharing" (com.funkyfresh.samba) and since CM10 I have to use the (dynamic) IP address which changes quite often but would like to have a permanent network drive in my Windows Explorer.

Any solution?

Thank you.
[Defy Q&A, Help & Troubleshooting] Vicsa:
You could assign/reserve one permanent ip adres for your defy in your network router. Just assign one specific ip adres to MAC adres of your defy in your router. That's how it'll get the same ip adres any time you connect to your network.
[Defy Q&A, Help & Troubleshooting] measel:
no access to the router but. thx
[JAMin, XDA Neo, S200 General] mackarus:
FYI this page combines the search for all the htc prophet devices on ebay (Qtek S200, Dopod 818 Pro, Imate JAMin) and list the lowest price. It looks like the S200 wins on this one.
[Hardware Hacking General] filipd:
Hi,

I have one SD card that I wanted to image , so I plugged it in my laptop reader and used Win32 Disk Imager.

However , during the write process it crashed and now my SD card is not being recognised. Is there any way to reformat it again?
[General Questions and Answers] innahouse:
Hi! I just brought myself a Colorfly CT 132 tablet from China, I was there for holiday, saw that tablet in a shop and thought, what the f...give it a try...but the stock 4.1.1 android firmware sucks bigtime....so..my question, is there any chance to just flash another rom on this tablet or does it need to be a specially designed firmware for that particularly model?

Until now I flashed all of my Samsung mobiles with custom rom, but for that tablet my knowledge is not enough, hopefully some pro of you can give me an advice...

Thanks in advance...

Greg

Item specifics

RAM:

2GB

CPU:

Allwinner A31 Quad Core

Camera:

Front 2.0Mp Back 2.0Mp

Bluetooth:

Yes

Shell Material:

Plastic

Extend Card:

Support TF card up to 128GB

Gravity Sensor:

Yes

OS:

Android 4.1

Item Type:

Tablet PC

Brand:

Colorfly

Screen Size:

13.3 Inch

Processor Main Frequency:

1GHz

Tablet Data Capacity:

16GB

Touch Screen Type:

Capacitive touch screen

Battery:

8000mAh/3.7V Rechargeable Li-ion Battery

Supporting Language:

Czech,Dansk,German,English,Spanish,Russian,French,Italian,Dutch,Norwegian,Polski,Greek,Portuguese, Svenska,Turkey,Korean,Japanese,Simplified Chinese,Traditional Chinese

Resolution:

1280*800
[Android Software Development] tkruijer:
I solved it, somehow got back into the bios.

Thread can be removed...
[Xperia SP General] KeiranFTW:
Hi,

Some of you may recognise my name from around the forums, especially if you have had an Xperia device before. I started my first android developments on the Xperia Play and then continued onto the Xperia U. I then lost mass interest in development due to joining college and being overloaded with work due to a computing course. I was no longer able to contribute to any developments.

Now, I am in the second year of college and have dropped a subject I am finding myself with more free time so I have decided to start developing again, only this time I have an Xperia SP.

There's only one catch, the device I have is network locked to O2 and therefore I cannot unlock my boot loader, so most if not all of my work will be for those with a locked bootloader. I am mostly interested in creating custom ROMs based on stock and also creating my own applications and embedding them into the stock ROM.

And the flashy bar at the bottom, yeah I have ideas for that.

Developments for Xperia SP:

illumination app

~Keiran
[Xperia SP General] fsyh95:
Thank you!:)
[Xperia SP General] Zenderable:
Thank you!

Thank you guy!

You have locked bootloader and you don't use fastboot :(

You should sell branded phone and buy no-branded :D
[Xperia SP General] KeiranFTW:
I can't, it just means that I will only be able to developed for locked bootloader which is no problem really. All it means is that I cannot change the kernel image, using scripts I can mess about with the ramdisk though and may be able to boot CM on a locked boot loader if the stock kernel allows it.
[Xperia SP General] wisnuhadi23:
Glad to see you back in the game mate ! Too bad that you can't unlock your bootloader. Although I know that would not be a problem for you.
[Xperia SP General] adfad666:
Hi [MENTION=4344506]KeiranFTW[/MENTION] welcome to Xperia SP development!

I hope we can work together on a project I want to try when we get the Android 4.3 update, I'm not sure if it will be successful and I'm not sure if anyone else tried this on other devices, but I want to try.

Basically I want to build Android 4.3 that works with the stock Sony 4.3 bootloader. I already have my fork of CodeAurora up and running here, I call it recaf, it will 'simply' be a matter of satisfying the extra dependencies and other Sony changes.

Come chat on freenode IRC, I'm in #freexperia, or on my own at #recaf. (If I don't reply immediately it mean's I'm afk, but my irc bouncer keeps me logged in.)
[Xperia SP General] KeiranFTW:
I'm sure it is very possible, as there is a way that could work really, I could probably set it up as a dual boot. You would need the AOSP ramdisk in tar format somewhere on your phone and at boot time if you wish to boot AOSP then it would delete everything at / and extract that ramdisk to / and then continue boot process with that ramdisk.. as long as stock kernel is compatible.
[Xperia SP General] niaboc79:
Welcome in SP section ;)

Happy to see more real dev here :)
[Xperia SP General] MrSteve555:
Well, maybe you could port kexec to our locked SP's? The main part of the module and binary is done, there is only one thing left - implementing proper hardboot and finally porting to our phones. I think some Xperia SP devs might help you. There's a thread in Z1 forums where delewer tries to get last parts of the job done. If you decide to start working on it, I want to be a alpha or beta tester:o

http://xdaforums.com/showthread.php?t=2495152
[Xperia SP General] clewis:
Welcome mate, glad you are here can't wait to see your work I also had an xperia play and I'm pretty sure I had a few of your roms and mods installed at some point.
[Xperia SP General] KeiranFTW:
I have a few projects in mind at the moment:

1. Getting the 4.3 leak to boot on locked bootloader

2. When 4.3 is released get AOSP 4.3 to run also on locked boot loader - I will be working with [MENTION=4193352]adfad666[/MENTION] on this - most priority

3. Maybe a stock based custom ROM - least priority.
[Xperia SP General] MrSteve555:
Maybe after booting AOSP 4.3 on locked BL you could try booting 4.4? Because it was possible in Xperia X8 "age of glory"(some devs booted 2.2 on 2.1 kernel if I'm not mistaken).
[Xperia SP General] KeiranFTW:
We could try.

The way I'm going to do it is hijack pre_hw_config.sh and then launch a script from there to determine whether to extract recovery ramdisk or AOSP ramdisk, then this will be extracted to /, and then everything will be unmounted and init will be started again to restart the boot process.
[Xperia SP General] MrSteve555:
I think I'll try to boot 4.3 today, with the method described in this thread: http://xdaforums.com/showthread.php?t=2593806

I'll post my results later.
[Xperia SP General] adfad666:
Unfortunately pre_hw_config.sh doesn't exist in the 4.3 leak, so assuming that doesn't change when we receive the official update, we won't be able to use that.
[Xperia SP General] KeiranFTW:
then /system/bin/charger :)
[Xperia SP General] MrSteve555:
Well, pre_hw_config.sh doesn't exist even in stock 4.1.2. I think we should try with chargemon, not charger(because it's executed earlier). I tried booting DooMLord's DoomKernel ramdisk on stock kernel. Absolutely no luck. I don't even know what's wrong - after loading ramdisk, kernel panic occurs. Maybe someone more clever will figure it out.:silly:
[Xperia SP General] KeiranFTW:
I think I'm nearly there at hijacking the boot process to inject new ramdisk, I just have a little test that I will have to do later as I need to go out now.

What I'm going to do is use the same ramdisk as that's in the kernel but inject it again after removing anything, this way I don't need to change my ROM and I know that I can inject a new ramdisk. I'll upload my work to github later too so people can contribute :)

~Keiran
[Xperia SP General] KeiranFTW:
Okay, so I've been successful in booting a custom RAMdisk, only problem I am experiencing is that the data partition is not being remounted when the new ramdisk is loaded, no idea why though.

Okay, done and fixed, sources are at https://github.com/keiranFTW/hijack-ramdisk-huashan

Get ready for exciting things coming now ;)
[Xperia SP General] MrSteve555:
I tried your method, but it has one bug - it doesn't symlink /data/media to /storage/sdcard0, so the data from internal memory isn't accesible through that path. Still amazing work, but I suggest you to change the format of ramdisk read by the script to .cpio, because it's easier to get from kernels. :good:
[Xperia SP General] dghostpt:
Do you know this?

http://www.xda-developers.com/android/locked-bootloader-xperia-s-and-want-cm10-no-problem/
[Xperia SP General] KeiranFTW:
I have a problem, if I stop all the services some of them don't start again after chroot and I can't see why. For example WiFi doesn't work and neither does any of the telephony functions of the phone, also is seems SD card is not being remounted.

I think /system/bin/chargemon is too late in initial boot process to hijack ramdisk
[Xperia SP General] KeiranFTW:
There's only one thing I can conclude really...

I have tried this method a few times and chargemon is too far through boot process to inject a new ramdisk, as most system services have started before /system/bin/chargemon has been executed, and when a new ramdisk is chrooted into the stage is past on-early-boot, and therefore most default services have already been started and when the new ramdisk is loaded, these services will not start, even if they are killed because /system/bin/chargemon is executed after this has happened...

What this realistically means is, that there is really no way of having a different ramdisk load, and boot an AOSP ROM, the difference is with the Xperia S is that pre_hw_config.sh is executed and this is on-early-boot, so this method works..

I don't think it will ever be possible to boot a ROM on an unlocked bootloader that requires a different ramdisk, I'm basing this opinion on my efforts so far,
[Xperia SP General] bez_iom:
Cheers for trying.
[Xperia SP General] kristophe.t:
Thanks for your efforts

Will this be http://xdaforums.com/showthread.php?t=2261606 usefull for developping xperia sp custom rom? Can it be adapted to xsp ?
[Xperia SP General] MrSteve555:
Check your inbox, maybe the info I provided will be useful.
[Xperia SP General] MrSteve555:
I think I finally made it. SDcard(through /storage/sdcard0) works, Wi-Fi works, BT works, sensors work, telephony works. Only problem I'm encountering is that the recovieries in ramdisk aren't working,(I'm using DooMLord's ramdisk) I'm just getting black screen(althrough I think I have an idea to get it working). I'll contribute to github later, and then we can start working on 4.3 on locked BL.
[Xperia SP General] KeiranFTW:
This is because all services are still running and so recovery cannot boot. Also DooMLoRD uses a different approach to booting recovery. I'll post an update on the thread soon when I have time to work, I need to kill services such as tad before new ramdisk is loaded.

Edit:

Also SD card service /system/bin/sdcard binary: is responsible for getting /data/media to link to sdcard0. I need to edit script to kill all services except chargemon, then merge step2.sh into chargemon, but this needs to be executed at /tmp/sh not /xbin/sh... I'll work on it later.