yashsingh1/xdaforums huggingface dataset:
[Xperia Z5 General] :
Z,

Are you building a fips kernel? That should not be. :confused:

On the strip entry, that's just a long standing part of my build script, we're not compiling modules so it does nothing.

Total commander will only register, so far, from /mnt/media_rw/blah

media_rw UID and GID are 1023

sdcard_rw should be 1015

everyone = 9997

mounting the mmcblk1p1 partion as follows, and manually through adb shell will result in a readable/writeable experience

mount -o rw,remount /

mkdir /mnt/media_rw/sdcard1

mount -o uid=1023,gid=1023 -t vfat /dev/block/mmcblk1p1 /mnt/media_rw/sdcard1

scripting the same event for the automagical experience fails as perms on the directory revert to 700

the same is true when attempting the operation on-device in terminal.

I have confirmed some kind of fubar when using zImage and separate dt.img in boot.img, no mmcblk1 detected, format is immaterial

I have confirmed mmcblk1 etc detected and manually mountable rw when using concatenated,compressed image-dtb.gz

Since i did a resync my build has gone completely mental.

m

EDIT; This is positively maddening. SELinux must be destroyed. GRRRR.

SELinux: initialized (dev mmcblk1p1, type fuseblk), uses genfs_contexts

Oh and 2 days later i am still waiting for omni to finish syncing. xD
[Xperia Z5 General] zacharias.maladroit:
M,

yeah, the build process appears to or wanting to build a fips kernel,

I've no idea why it does so, however :confused:

These dtb (dt) files contain some serious magic :laugh:

I'm glad that the sd cards are reliably being detected now,

...

ouch :eek:

hehe - selinux won't leave you alone :cyclops:

Concerning the mounting issue of our beloved microSD cards - I believe to have possible found the cause:

https://github.com/Sony-Kitakami/an...7c65315b6b4754970beb3c/rootdir/fstab.kitakami

but other sources disagree and say

Would be nice if that was the missing straw,

it however also could be totally wrong :o

Or am I eyeballing the wrong one ?

edit:

That's the OTG port, stupid :silly:

---------- Post added at 01:31 AM ---------- Previous post was at 01:04 AM ----------

Actually you know what - try out the following:

instead of

use

or

explanation:

ntfs & exfat don't understand and support suid, dev entries (?) also the filesystem shouldn't be restricted to vfat,

when mounting a sdcard with ext4 (or similar filesystem) that support suid and dev files, these corner-cases should be addressed (security issue),

but for now if this gets access to the sdcard working - fine :D

or is it ?

well, it's already getting late again ... hope this helps in some way towards the solution ...
[Xperia Z5 General] :
Vold

[MENTION=6584695]CTXz[/MENTION] [MENTION=3037651]zacharias.maladroit[/MENTION]

Okay found it/got it

Additionally to image-dtb.gz, this patch to undo selinux asswittery found here

Don't abort even if setexeccon failed

system/vold/Utils.cpp

--- a/Utils.cpp
+++ b/Utils.cpp
@@ -258,12 +258,12 @@

if (setexeccon(context)) {
LOG(ERROR) << "Failed to setexeccon";
[COLOR="Red"]- abort();[/COLOR]
[COLOR="Olive"]+// abort();[/COLOR]
}
status_t res = android_fork_execvp(argc, argv, NULL, false, true);
if (setexeccon(nullptr)) {
LOG(ERROR) << "Failed to setexeccon";
[COLOR="Red"]- abort();[/COLOR]
[COLOR="Olive"]+// abort();[/COLOR]
}

free(argv);
@@ -290,12 +290,12 @@

if (setexeccon(context)) {
LOG(ERROR) << "Failed to setexeccon";
[COLOR="Red"]- abort();[/COLOR]
[COLOR="Olive"]+// abort();[/COLOR]
}
FILE* fp = popen(cmd.c_str(), "r");
if (setexeccon(nullptr)) {
LOG(ERROR) << "Failed to setexeccon";
[COLOR="Red"]- abort();[/COLOR]
[COLOR="Olive"]+// abort();[/COLOR]
}

if (!fp) {

fstab.cat_salami

/devices/soc.0/f98a4900.sdhci/mmc_host* auto auto defaults voldmanaged=sdcard1:auto,encryptable=userdata

vfat/fat32 :good:

exfat :good:

MMM external nom nom storage nom, it's soooo nom nom good nom. :silly:
[Xperia Z5 General] CTXz:
Nice work moon, i'll try to add it without the need of patches
[Xperia Z5 General] CTXz:
I've set some macros that forces setexeccon to return 1 and so skip the abort resulting conditions. Those are all located in the kitakami tree as we're using selinux.h from our include path now, giving us space for customization without patching/touching the cm source. The flags will be defined if TARGET_SKIP_SETEXECCON_CHECK is set true in the platform config. I haven't tested yet however it is a very dirty workaround and any more professional solution is apriciated. With that out of our mind it is still allot better than using patches as those can be a pain when working with other devices in one source

https://github.com/Sony-Kitakami/an...mmit/58b0d2590353cf0af0912fb4f471e3ff0359b16c
[Xperia Z5 General] zacharias.maladroit:
Excellent ! :)

Great work !

Agreed, that's a more flexible approach

There is a small typo in PlatformConfig.mk - so the changes wouldn't work

edit:

now it should
[Xperia Z5 General] CTXz:
Wups, my bad
[Xperia Z5 General] :
[MENTION=6584695]CTXz[/MENTION] [MENTION=3037651]zacharias.maladroit[/MENTION]

Okay this is driving me absolutely mad....[again].....[today]

when running build to mka systemimage with twrp as recovery variant,

Installing recovery patch to system partition
Traceback (most recent call last):
File "./build/tools/releasetools/make_recovery_patch", line 55, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/make_recovery_patch", line 37, in main
OPTIONS.info_dict = common.LoadInfoDict(input_dir)
File "/storage/cm13/build/tools/releasetools/common.py", line 201, in LoadInfoDict
d["fstab"] = LoadRecoveryFSTab(read_helper, d["fstab_version"], d["device_type"])
File "/storage/cm13/build/tools/releasetools/common.py", line 285, in LoadRecoveryFSTab
raise ValueError("malformed recovery.fstab line: \"%s\"" % (line,))
ValueError: malformed recovery.fstab line: "/recovery emmc /dev/block/bootdevice/by-name/FOTAKernel flags=backup=1;display="FOTAKernel""
build/core/Makefile:1072: recipe for target '/storage/cm13/out/target/product/satsuki/system/bin/install-recovery.sh' failed
make: *** [/storage/cm13/out/target/product/satsuki/system/bin/install-recovery.sh] Error 1
make: Leaving directory '/storage/cm13'

#### make failed to build some targets (05:45 (mm:ss)) ####

NYAAAAHHHH
[Xperia Z5 General] CTXz:
Gimme a sec, I think I know what's going on

*Edit*

Nvm :/
[Xperia Z5 General] CTXz:
I've updated all blobs to v4 now. It also turns out that suzuran uses a different Bluetooth driver than sumire and satsuki. This should explain the BT issue
[Xperia Z5 General] CTXz:
Now that all devices are up and runnin with CM I will start working on a fully documented buils guide on how to build CM from source and how to build CM based ROMs
[Xperia Z5 General] zacharias.maladroit:
Some more findings on Dual SIM devices:

# Radio
SIM_COUNT := 2
TARGET_GLOBAL_CFLAGS += -DANDROID_MULTI_SIM
TARGET_GLOBAL_CPPFLAGS += -DANDROID_MULTI_SIM

or something similar with SIM_COUNT needs to be added to BoardConfig.mk for the device

Dual SIM support appears to have been merged t o CyanogenMod 13 just recently or is still in progress:

http://review.cyanogenmod.org/#/q/extphone+branch:cm-13.0

We might need RIL/rild (a dual sim variant) from stock (if that exists) to get it working

Candidate devices to ask devs for how they got dual sim working:

http://xdaforums.com/desire-816/development/rom-t3282978 (Desire 816) [not yet asked]

http://xdaforums.com/z3/development...ial-xperia-t3243603/post63712611#post63712611 (Xperia Z3) [answer pending]
[Xperia Z5 General] CTXz:
It has been there for quite time. Make sure you're building the dual sim defconfiguration
[Xperia Z5 General] zacharias.maladroit:
There is none in AOSP/CM,

but I've ported some stuff from stock - so that should hopefully work *fingers crossed* (at least kernel side)

So

# Radio
SIM_COUNT := 2
TARGET_GLOBAL_CFLAGS += -DANDROID_MULTI_SIM
TARGET_GLOBAL_CPPFLAGS += -DANDROID_MULTI_SIM

is the correct thing to add and ril/rild will afterwards be started with 2 instances on the ROM ?

I'm not really certain whether that is really enough ...

The information on this matter is really scarce - therefore I'm posting it here in this thread so that others can stumble upon it and base their work on it,

Most threads that I found only say:

There you have the source - it's in the CyanogenMod github repo - wow - Captain Obvious at work,

can't be more vague, can it ? ;)
[Xperia Z5 General] guentergunter:
Camera Color Space

The DEV-Thread wasn't on my radar. So here's what I originaly posted in the ROM-Thread:
[Xperia Z5 General] souriceau1993:
Hello xda community, i'm looking for the CM13 for my Xperia Z5 but i don't understand some little things... is the Dev released for this device or are you currently working on it ? I don't see any news since April 2016 ...
[Xperia Z5 General] iiicentury:
http://xdaforums.com/showthread.php?t=3339930
[Xperia Z5 General] souriceau1993:
First i'll thank you for the rapidity you let me know this. But i'm actually looking for the Xperia Z5 Not Xperia Z5 Compact... any more info ?
[Xperia Z5 General] zacharias.maladroit:
http://xdaforums.com/xperia-z5/development/rom-cyanogenmod-13-sony-xperia-z5-t3356163

rule of thumb: take a look at

Development

or

Original Development

subforums :p
[Xperia Z5 General] kakami okatsu:
Hello everyone!

I know this might not be the right place to start but i'm a new XDA member! I always came here, grab some work made from other, install on the phone and gone away. Right now I have a Sony Z5C and since the bugs are really annoing I wan't to help!

I'm a dev with 0 experience in the source of CM so where can I start? Can I help you in any way?

Thank you in advance.
[Xperia Z5 General] goRt:
Your device is much further ahead than ours:

http://xdaforums.com/showthread.php?t=3339930
[Xperia Z5 General] kakami okatsu:
Ops. I think this is the general thread for Z5 dev. I'll post on the other.
[G 2014 Q&A, Help & Troubleshooting] Davis26:
Hi guys!!

They could help me knoww that RECOVERY is right for Marshmallow ; I tried with different ROMS and the problem arises when installing Gapps because after installing the Gapps, not start, the warning "unfortunately has stopped setup wizard " appears , or ocacionan "bootloops" .

I researched and apparently is the RECOVERY , could you please help me?.

ROMS Tested :

CM13

Xperience

BeanStealk

Gapps Tested :

OpenGAPPS

( open_gapps-arm-6.0-nano-20160124.zip , open_gapps-arm-6.0-pico-20160124.zip )

BANK_GAPPS

Dynamic BANK_GAPPS

Tested RECOVERY :

philz touch

TWRP

XT1064

PLEASE HELP!

I'm desperate :eek::eek::eek::eek:
[G 2014 Q&A, Help & Troubleshooting] sagar846:
Using TWRP

clean flash cm 13 ( wipe everything except internal storage and ext SD) and flash zip and gapps , wipe dalvik and cache and reboot .

Its got to work since there is no problem at all with any ROM or gapps.

If that doesn't work restore to stock and start the process again (root and stuff)
[G 2014 Q&A, Help & Troubleshooting] Davis26:
Thank you !

Let me try and comment .
[G 2014 Q&A, Help & Troubleshooting] Davis26:
Solved

Thank you

I commented that worked perfectly . :good: :laugh: :laugh:
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] QualcommCode:
i have a verizon (G900V) samsung galaxy S5.

it was originally on 5.0

i wanted to root it, so i downgraded it to 4.4.2.

after you downgade from certain software versions, the phone goes in to a boot loop.

so after downgrading i went in to stock recovery to factory reset.

this is where the issuse is:

so i can NOT factory reset the device because it says (at the bottom of the screen:

"MDM does not allow factory reset"

p.s. - i prevously had a verizon (N910V) Samsung Galaxy Note 4 witht he same issue, i was able to fix it

by flashing a modified stock tar that also reset the device.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] painiac:
Factory reset doesn't undo a version downgrade, it only deletes user settings and restores all the pre-installed apps.

You want to use Odin to flash a factory image. Get the image in this thread and follow the rooting instructions: http://xdaforums.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] jrkruse:
How are you on 5.1.1 firmware when it hasnt even been released yet for the verizon S5
[Mate 8 Q&A, Help & Troubleshooting] Shtihi:
hi guys, i've got the NXT-AL10 4gb/128gb

and for some reason i cant install through google play the whatsapp or chrome or poweramp apps, its says its not competible with my device

is its still not suitable with android 6.0? or that there is a problem with my rom..

if so how can i fix this?
[Mate 8 Q&A, Help & Troubleshooting] jbmc83:
whats your firmware version? was google play store preinstalled on your device? maybe youre missing some google app components...
[Mate 8 Q&A, Help & Troubleshooting] Shtihi:
yep my bad.. the phone came with outdated google play .. i updated the app and all good :)
[Nexus 6P Q&A, Help & Troubleshooting] jabawarkie:
Hi guys

So I bought a brand new nexus 6p on eBay 2 months ago. Stupidly I met the guy at his girlfreinds house (supposedly) and paid cash for it.

Today my phone stopped getting signal so I spoke to three (uk) and they advised me the phone had been blacklisted.

I can't get in contact with the guy I bought it off and can't remember where his girlfriend lives, I'm guessing he's reported it as stolen as to do an Insirance claim or something g.

Question is..... Is there anything I can do to get the phone I paid for to work again? I've heard about changing the imei number but I'm guessing that's illegal. Any advice would be greatly appreciated.

Thanks
[Nexus 6P Q&A, Help & Troubleshooting] XxMORPHEOUSxX:
Sounds like it may just be stolen. I would hand it over to the authorities and ask them to sort it out. You don't need to be involved any further than you are. I'm guessing the price was really good. Usually when it seems to good to be true, it is. See if you can get eBay to help you out as well. They should have some sort of policy.
[Nexus 6P Q&A, Help & Troubleshooting] jabawarkie:
Think you may be right.... I paid £300 for it so yeh it was really cheap to say it was brand new. He did look abit of a dodgey character though so its my own fault. I think I'll pass it in to the police. I do have his eBay username though and his full name so I'll give that to the police as well.

Shame I'll be the one out of pocket at the end of the day.
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
It is a huge shame, but you don't really have a choice. Changing the IMEI is indeed illegal. Plus, if you were to knowingly try to get this phone to work after finding out that it's most likely style, you'd be up for criminal charges yourself.
[Android Q&A, Help & Troubleshooting] ovik22:
my divice is symphony h250 and gpu is mali t720..and chipset is mt6735...how can I root it...all rooting pc apps and mobile apps are failed
[Android Q&A, Help & Troubleshooting] KHSH01:
Hey bro. I use h250 too. You can technically root it with king root but you would need a stable fast net connection. Even then it will fail sometimes. The best method would be to download the recovery I ported from this link [http://www.needrom.com/download/h250-custom-recovery-philz/] then flash supersu zip from chainfire's website. And voila you have supersu with root!
[Galaxy Note5 Q&A, Help & Troubleshooting] Luwize1:
Why ?????????????? :crying:

Still new couldn't add external links ... *
[Galaxy Note5 Q&A, Help & Troubleshooting] Luwize1:
Problem Solved

Problem Solved after reset settings, at the bottom of the settings menu, I hope this post could help other users that have the same problem that I was facing.
[Galaxy Note 4 Q&A, Help & Troubleshooting] Motawa88:
I could get a note 4 pretty cheap but it has knox 0x1 . I dont care about waranty. Can i still root and install custom roms?
[Galaxy Note 4 Q&A, Help & Troubleshooting] l3o4nn:
Yes you can
[Galaxy Note 4 Q&A, Help & Troubleshooting] xdm9mm:
Not a bad idea, just make sure it is working as it should. You will be rooting and using custon roms anyway so knox being tripped is nothing to worry about.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] leshan:
Would you please teach me how to dump(or extract?) the nk.nbf file into a kitchen? Like this one:http://xdaforums.com/showthread.php?t=311027.

Thank you.

Never mind
[8125, K-JAM, P4300, MDA Vario Software Upgrading] ndn715:
the collection of command line tools in most of the kitchens will do it but they're a PIA to use... recently, ive used the automated tools in the HyperCore kitchen or the new Wizard Service Tool 4.0.... that thing is awesome!
[8125, K-JAM, P4300, MDA Vario Software Upgrading] jwzg:
Leshan, the you'll need to use the Hypercore kitchen to do that. I don't think that it is well sorted out instruction-wise, but it does extract the ROM (XIP) as well as the SYS and OEM folders. You might post in his thread or send him a PM as I'm not able to go into detail right now since I'm at work.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] leshan:
Hi, Thank you.

Yes, I have already tried to use Hypercore kitchen to do my job. I tried to Dump the Official T-Mobile AKU3.3 rom take off some trash and add some apps. I know you created a clean AKU3.3. So may I have two questions please:

1. How can I take off the T-mobile dialer skin and use the WM5 default one or even WM6 default one? I tried to replace the 6 'bmp' files and some 'dll' files, I only got the blue dialer skin but no 3D button and no smartdial.

2. How can I replace the old Office with Office 2007?

Thank you.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] seth66:
If you dont want to mess with cooking the rom you can use these cabs..

First one will replace the carrierlogo (with nothing..you wont see it)from the dialer and activate the default wm5 dialer .

Second will enable smart dialing but however you wont be able to use smartdial because the default wm5 skin does not support this ..

If you really want smart dialing you can use the 3rd file which is a wm6-ish skin.Or pick another one from http://www.zombienexus.net

I dont think office 2k7 will work under wm5 maybe i am wrong..

Sorry for bad english...
[8125, K-JAM, P4300, MDA Vario Software Upgrading] leshan:
Thank you.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] jwzg:
Leshan, I had to replace all of the .gif files in the OEM camera folder with the files from the original Cingular 2.25 ROM to get the blue smart dialing back. In addition, there are some registry changes that need to be made so the smart dialing highlights will not be pink and grey. You can also replace the Phone Pad with the files from the same ROM (MMS/other apps folder) as well so you totally get rid of the pink and grey.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] leshan:
So, Would you please tell me the name of the folder which have the .gif files. And the registry changes detail?

Thanks. I do not want to just change the registry in the WM5 to disable the Tmobile Dialer skin.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] jwzg:
The two folders are 1a8ae8d9-5f48-47a0-9d6d-1731f4ac839a (MMS/other apps) and 71d74e8a-db26-4396-936e-96957645b723 (camera). You have to delete all of the pink and gray .bmp's and then take the blue .bmp's from the Cingular ROM and put them in the camera folder to get blue smart dialing. You'll then have to get the phone pad app. from the Cingular ROM as well. The .rgu file in 71d74e8a-db26-4396-936e-96957645b723 has the color settings for smart dialing. I'll let you find them.

:)
[8125, K-JAM, P4300, MDA Vario Software Upgrading] leshan:
Cool, Appreciate that first.

By the way, Is there any Kitchen which can directly dump from the MDA in to a .nbf or nb file?
[Galaxy Note II Q&A, Help & Troubleshooting] soufwinn:
Plz help how i can fix it
[Galaxy Note II Q&A, Help & Troubleshooting] yaro666:
Flash stock rom, then flash new modem and bootloader. You have radio and bootloader thread in android development.

The newest is OE2
[Galaxy Note II Q&A, Help & Troubleshooting] soufwinn:
U have link for this stock? Plz
[Galaxy Note II Q&A, Help & Troubleshooting] yaro666:
Sammobile

Just use google or search next time
[Galaxy Note II Q&A, Help & Troubleshooting] soufwinn:
Thx sir but What i have to search there?
[Galaxy Note II Q&A, Help & Troubleshooting] yaro666:
Firmwares and enter your model number i.e. N7100, N7105, etc.

Every rom there is stock
[Galaxy Note II Q&A, Help & Troubleshooting] soufwinn:
Yes sir but i will lost DN3 rom right?
[Galaxy Note II Q&A, Help & Troubleshooting] yaro666:
yes, but do it like that:

flash stock rom with Odin

flash new bootloader - you can get it from stock rom, just unpack it, search for sboot.bin and pack it to tar with 7zip to get sboot.tar.md5

flash new modem - you can get it from stock rom, just unpack it, search for modem.bin and pack it to tar with 7zip to get modem.tar.md5

then go to recovery do a full wipe and flash your custom rom, like DN3

I hope you have EFS backup, if not, make one
[Galaxy Note II Q&A, Help & Troubleshooting] soufwinn:
how i can make EFS sir?
[Galaxy Note II Q&A, Help & Troubleshooting] yaro666:
CLICK

or go to recovery and you'll find backup EFS option
[Galaxy Note II Q&A, Help & Troubleshooting] soufwinn:
Thank you bro so much

do u know how i can add arabic in DN4 coz when i flash my phone to DN4 cant read arabic :/
[Galaxy Note II Q&A, Help & Troubleshooting] yaro666:
go to keyboard settings and there you can add languages, it should do the job
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] nogloww:
I've been posting for months with no response so I'm assuming maybe I've been posting in the wrong threads? So I'll try this one. Feel free to move it as necessary. I can't get apkeditor to work on my device. I'd really like a c clone of the app Squid (formerly known an Papyrus) to help with my school work flow. If anyone can get apkeditor to work if be very appreciative. I've attached the apk link here https://app.box.com/s/9enmgc9ytzw38jqt5r2zwlvxofcfzjqd
[Nexus 9 Android Development] Martin_Devil:
​

OmniROM is a free, community built, aftermarket firmware distribution of Android by [MENTION=2162789]XpLoDWilD[/MENTION], [MENTION=631273]Chainfire[/MENTION], [MENTION=912474]Dees_Troy[/MENTION] & Team. OmniROM is designed to increase performance, reliability and features over stock Android for your device as well as optimizations and customizations.

#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/

OmniROM is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed.

All the source code for OmniROM is available in the OmniROM Github repo.

Homepage:

=================

http://omnirom.org/

Wiki:

=================

http://docs.omnirom.org/Main_Page

Gerrit:

=================

https://gerrit.omnirom.org/

Bugtracker:

=================

http://jira.omnirom.org

IRC:

=================

irc.freenode.net #omnirom

Be Advised:

=================

Root access is not included by default as of yet. Please flash SuperSU for root (See below).

If problems arise from your use of custom kernels, "performance scripts", etc. etc., we can't be responsible.

Installation Instructions:

=================

First time installing OmniROM, or coming from another ROM:

- Wipe / Factory Reset

- Flash OmniROM zip from SDCard

- Flash GApps zip from SDCard

- Reboot

- Don't restore system data using Titanium Backup!

Upgrading from earlier version of OmniROM:

- Copy the OmniROM ZIP to your SDCard

- Boot into Recovery

- Flash the OmniROM zip from SDCard

- Reboot

Downloads:

=================

https://www.androidfilehost.com/?w=files&flid=48512

Google Apps:

OpenGApps (choose arm64, 6.0, nano)

SuperSU:

SuperSU.zip