yashsingh1/xdaforums huggingface dataset:
[SuperSU] Chainfire:
This is implemented in v2.79 SR2.

Sorry, is this still relevant? I'm quite busy, and without having a device myself I can't really test.

I'm sorry I have no idea what is going on here.

Both the rules and file format are Android version and device specific. In some cases it may work. In some cases it will appear to work with subtle failures in random processes. I just wouldn't go there.
[SuperSU] Honestly Annoying:
Yes it is, and there are MANY people willing to test. My personal device is out for the next couple weeks, but once it is back to being up and running I will be available myself to test. If you will be less busy then, that's probably the better way to go :)
[SuperSU] InterestingTwist:
Hmm thanks for the information. I have used supolicy before to inject but when trying to inject the following lines supolicy says invalid syntax.

"set_prop(audioserver, dolby_prop)" needs to be in audioserver.te

"set_prop(mediacodec, dolby_prop)" needs to be in mediacodec.te

"media.dolby_memoryservice u:object_r:audioserver_service:s0" needs to be in service_contexts

Any help would be much appreciated, thanks for all you do. :good:
[SuperSU] Chainfire:
set_prop is a macro, you need to figure out exactly which allow rules these create. You can't copy/paste stuff from .te files into supolicy.

service_contexts is a file you need to modify. You may actually need to modify that in boot image ramdisk for it to work, I don't know.
[SuperSU] InterestingTwist:
You are one smart guy, thanks I found the macro and have changed them to allow rules. As for service_contexts, I can confirm you can modify it by extracting ramdisk. :good:
[SuperSU] Matt07211:
[MENTION=631273]Chainfire[/MENTION]

Update support of SuperSU for non-standard boot.img [Necessary source code included]

Back in November last year, I implemented SuperSU by hand in my devices boot.img (Samsung xCover3 (Thread for reference: https://xdaforums.com/android/development/4-4-4-5-1-1-6-0-1-samsung-xcover3-t3465132), cause at the time no tools where unable to unpack our boot.img properly (Thus we wrote/modified our own). Now I'm almost ready to build some ROMs and would prefer not to repeat the process again, so that's why I'm here :)

Now to the code and commands (So you can hopefully implement this in your tool)

Required:

- pxa1088-mkbootimg: https://github.com/AKuHAK/pxa1088-mkbootimg

- minigzip

- mkbootfs

Unpacking Boot.img

./pxa1088-unpackbootimg -i boot.img -o boot -p 2048

Example output:

boot.img-base
boot.img-cmdline
boot.img-dt
boot.img-pagesize
boot.img-ramdisk.gz
boot.img-ramdisk_offset
boot.img-second
boot.img-second_offset
boot.img-signature
boot.img-tags_offset
boot.img-uImage
boot.img-unknown

Files of importance are

*-dt

*-ramdisk.gz (note it should be ramdisk.cpio.gz, but tool outputs it that way :( ...)

*-signature

*-uImage

*-unknown (Not the file but the value stored in the file)

Unpack ramdisk

mkdir ramdisk
cd ramdisk
gunzip -c ../ramdisk.cpio.gz | cpio -i

Repack Ramdisk

./mkbootfs ramdisk-directory-name | ./minigzip > ramdisk-new.cpio.gz

Cavet: mkbootfs and minigzip are unable to include hidden files into the boot.img, your tool used them that way to keep a copy of the stock files unmodified, it may require you to modify the code to be able to include hidden files.

Repack boot.img

./pxa1088-mkbootimg --kernel boot.img-uImage --ramdisk ramdisk-custom-supersu.cpio.gz --dt boot.img-dt --signature boot.img-signature --unknown 0x3000000 -o ../boot-supersu.img

usage: mkbootimg

--kernel <filename>

[ --ramdisk <filename> ]

[ --second <2ndbootloader-filename> ]

[ --cmdline <kernel-commandline> ]

[ --board <boardname> ]

[ --base <address> ]

[ --pagesize <pagesize> ]

[ --dt <filename> ]

[ --ramdisk_offset <address> ]

[ --second_offset <address> ]

[ --tags_offset <address> ]

[ --id ]

[ --signature <filename> ]

-o|--output <filename>
​

Hopefully this gives you enough info and the source code provided should make it easy to implement into your tool if you chose to do so.

Hopefully you decide to do this.
[SuperSU] Chainfire:
Unless you can pinpoint exactly what the difference is what a standard boot image, nothing is going to happen with that.
[SuperSU] Matt07211:
Android boot image:

Standard Android header:

Magic (8B)

kernel size (4B)

kernel addr (4B)

ramdisk size (4B)

ramdisk addr (4B)

2ndary size (4B)

2ndary addr (4B)

Tags addr (4B)

Page size (4B)

unused #1 (4B) (zero in standard Android)

unused #2(4B) (zero in standard Android)

product name (16B)

kernel cmdline (512B)

id (8B)

Samsung xCover3 header:

Magic (8B, ANDROID!)

kernel size (4B)

kernel addr (4B, 0x10008000)

ramdisk size (4B)

ramdisk addr (4B, 0x11000000)

2ndary size (4B, 0x0)

2ndary addr (4B, 0x10f00000)

device tree size (4B)

unknown(4B, 0x02000000)

tags addr(4B, 0x10000100)

page size (4B, 2048)

product name (24B, empty)

kernel cmdline (512B, empty)

id (8B, empty)

Samsung xCover3 layout:

A. header (as above - 1 page)

B. kernel (n pages)

C. ramdisk (m pages)

D. second stage (o pages)

E. device tree table (started with PXA-DT magic, p pages)

F. signature (272 bytes)

Taken from source code for completeness sake.

/*

** +-----------------+

** | boot header | 1 page

** +-----------------+

** | kernel | n pages

** +-----------------+

** | ramdisk | m pages

** +-----------------+

** | second stage | o pages

** +-----------------+

** | device tree | p pages

** +-----------------+

** | signature | 272 bytes

** +-----------------+

**

** n = (kernel_size + page_size - 1) / page_size

** m = (ramdisk_size + page_size - 1) / page_size

** o = (second_size + page_size - 1) / page_size

** p = (dt_size + page_size - 1) / page_size

**

** 0. all entities are page_size aligned in flash

** 1. kernel and ramdisk are required (size != 0)

** 2. second is optional (second_size == 0 -> no second)

** 3. load each element (kernel, ramdisk, second) at

** the specified physical address (kernel_addr, etc)

** 4. prepare tags at tag_addr. kernel_args[] is

** appended to the kernel commandline in the tags.

** 5. r0 = 0, r1 = MACHINE_TYPE, r2 = tags_addr

** 6. if second_size != 0: jump to second_addr

** else: jump to kernel_addr

*/

base = 0x10000000

kernel_offset = 0x00008000

ramdisk_offset = 0x01000000

second_offset = 0x00f00000

tags_offset = 0x00000100

unknown = 0x03000000

That's the difference I believe. [MENTION=631273]Chainfire[/MENTION]

If there is any other info needed please do tell me so I can provide it. :)

Edit: Signature is the random string found at the end of the boot.img, with it gone the "Kernel is not Seandroid enforcing" will show. It seems like a random string of data the bootloader validates against.
[SuperSU] Chainfire:
How many devices are affected by this?
[SuperSU] Matt07211:
I believe any device with a Marvell based SoC.

I personally know of 2 devices:

- my Samsung xCover3 (listed above)

- Samsung Galaxy Tab 4 7.0: signature size is slightly smaller coming in at 256 bytes and it's unknown offest is 0x02000000. Everything else is the same as the xcover3 device.

Some devices found in a Google search include:

- Samsung SM-J100f

- Chromecast 2

- Samsung Galaxy Tab 3

- Samsung Galaxy BEAM 2 SM-G3858 projector Smartphone

- HP Slate 6 Voice Tab 2

- HP Slate 7 VoiceTab

This is just from a quick google search, there of course may be plenty more, I just get inundated by the official realse webapges of these SoC's.

Marvell has mainline Linux kernel support as well.
[SuperSU] Matt07211:
[MENTION=631273]Chainfire[/MENTION] So my request is a no-go?
[SuperSU] no.human.being:
Hey, Chainfire (and others)!

When I try to root my BQ Aquaris U, it appears to patch the kernel image in the "boot" partition, which makes me somehow lose ADB access to the device.

Before rooting ...

$ ./adb start-server
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
$ ./adb shell
shell@chaozu:/ $ exit
$ ./adb kill-server
$

After rooting ...

$ ./adb start-server
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
$ ./adb shell
error: no devices/emulators found
$ ./adb kill-server
$

The device is running on the most recent firmware: Android 6.0.1, Kernel 3.18.24, Build 1.5.0_20170217-1219

My Android SDK is up to date as well.

I tried both SuperSU (v2.79-201612041815) and SuperSU (v2.79-SR3-20170114223742) and both lead to the same outcome.

When I connect the phone to my PC, it shows that a debugger is connected. However, ADB does not seem to see the phone as a viable target. Both developer options and USB debugging are enabled on the device and the device shows up on my PC under the USB ID "2a47:901b" in "lsusb".

What I tried so far:

Change USB mode (charging only, MTP, etc.) on the device.

Reset debug permissions on the device.

Add the device's USB ID to "~/.android/adb_usb.ini" on the computer.

Create "udev" rules on the computer.

Run ADB as root on the computer.

None of these seem to have any effect on the issue.

As a developer, I really need both ADB and root access to my targets, which is why I went with a different rooting utility, which does give me a root via "su" and debug access via ADB. However, it does not give me "./adb root". Instead, I need to "./adb shell" and then use "su", which also means that "./adb push ..." and "./adb pull ..." requests are carried out without root permissions, so it's not really convenient.

Have you heard of SuperSU breaking ADB before? In case it's rare and only happens on few devices, might I contribute in tracking the issue down?

Greetings.
[SuperSU] mucucu:
reeder P10s root help !

Hello. How can I root my Reeder P10S phone? I could not find a solution anywhere. Can you help me ?
[SuperSU] Maxr1998:
Please ask in the relevant device subforum if available or in the main SuperSU discussion, this topic is only for developers :)
[SuperSU] voider1:
Hey, I was giving a workshop on Xposed some time ago for which I needed some cheapo phones, found some 90 euro phone called Wiko Freddy. Interwebz told me it was rootable, so I bought a couple of them. Turns out, they weren't. No TWRP for my device either. After a lot of researching I managed to install Xposed without root access on the device by patching the recovery image. I added my own generated key to the image so I could sign my own OTA. That worked out for me, I just had to make minor modifications to the flash-script of Xposed. I also want to root the phone, just for the sake of it. I know for one thing that mounting /system as rw is very unusual on this phone. Is there any procedure for porting superSU to a phone?
[SuperSU] henrysinn:
Hi Chainfire et al,

Trying to embed to get root via instructions at http://su.chainfire.eu/#embed onto a Pumpkin 27-AQTU72 car head unit.

Their downloaded update rar consists of:

mcuupdate

update.script

update.zip

I unzipped update.zip, put supersu/supersu.zip in with other files (see attached) and re zipped.

Updated update.script as per code in 6.2 at http://su.chainfire.eu/#embed

Attempted update. Errors as attached.

Any thoughts?

Many thanks in advance.

Henry
[SuperSU] MATPOC:
I found very old bug in update-binary script. This bug is about mips determining and appearing in Android older then API 17.

Here is the patch solving this bug:

--- update-binary.~1~	2008-02-29 03:33:46.000000000 +0700
+++ update-binary	2017-06-06 13:48:59.515801184 +0700
@@ -956,13 +956,13 @@

if [ "$ABI" = "x86" ]; then ARCH=x86; fi;
if [ "$ABI2" = "x86" ]; then ARCH=x86; fi;
+if [ "$ABI" = "mip" ]; then ARCH=mips; fi;
+if [ "$ABILONG" = "mips" ]; then ARCH=mips; fi;
if [ "$API" -eq "$API" ]; then
if [ "$API" -ge "17" ]; then
PIE=.pie
if [ "$ARCH" = "x86" ]; then SU=su.pie; fi;
if [ "$ABILONG" = "armeabi-v7a" ]; then ARCH=armv7; fi;
- if [ "$ABI" = "mip" ]; then ARCH=mips; fi;
- if [ "$ABILONG" = "mips" ]; then ARCH=mips; fi;
fi
if [ "$API" -ge "18" ]; then
SUMOD=0755
[SuperSU] MATPOC:
[Linux] Universal script to embedding root in system.img image of Android up to 6.0

I modified update-binary script from SuperSU v2.82 update ZIP to work on Linux. This script mount system.img image and placing all needed files from SuperSU update ZIP. This script can work on system.img of Android version up to 6.0. I tested it on system.img of Android versions 4.0.3, 4.4.2, 5.1. I am run it on Ubuntu 14.04, other Linux versions should be OK. All you need is usual Linux tools and unzip.

Also this script deleting /system/recovery-from-boot.p - this file restoring original recovery in some firmwares.

Look at makeroot-0.1.sh.zip in attachment.
[SuperSU] Chainfire:
But... MIPS is only officially supported since API 17, so the code is as it should be ?
[SuperSU] MATPOC:
Friend of mine has Ainol NOVO7 Basic Tablet. It's mips, the first Android version for it was 3.2, the last firmware is Android 4.0.3.
[SuperSU] MATPOC:
Some firmwares contains another technique to restore recovery - the file /system/recovery-from-boot.p. Please modify your update-binary script to remove this file. Some like this:

if [ -f "/system/recovery-from-boot.p" ]; then
rm -f /system/recovery-from-boot.p
fi
[SuperSU] deadface007:
Systemless Root without altering Boot Image

Sorry if this is the wrong place to ask this question, but someone here might be helpful.

Is there a way to create a smaller android filesystem contained within an app(similar to like sandboxie for windows) so that one would be able to install apps within it and modify it's own files without ever touching the files outside of it?

I'm not asking for a virtual machine(maybe), but I think this would be a neat sandbox-root. The benefits of this being that devs wouldn't have to figure out how to bypass manufacturer locks, and it wouldn't trip Samsung's Knox. Essentially, one wouldn't even have to reboot their device for this root as it doesn't alter the boot image. Custom recoveries would also be unnecessary.

Please excuse my ignorance of the subject.

Thanks!
[SuperSU] hardd2007:
su with tmpfs of /data

When I mounted /data with tmpfs su not work.

When /data is ext4 all work correct. I need to mount /data with tmpfs and working su.

Any help?
[G4 Q&A, Help & Troubleshooting] trix95:
Guys yesterday and today caschys blog and smartdroid confirmed the v20c ota update on their blog posts and articles here is the one from smartdroid

http://www.smartdroid.de/lg-g4-marshmallow-update-kommt-drahtlos-bei-deutschen-geraeten-an/

i dont know if its the true because i am not getting any update messages on my phone or lg bridge both showing v20a is latest kdz and other methods like wiritng your imei at devtester.ro shows that latest version is v10d ??? i am very confused today and i dont mean the v20c kdz from another thread here in xda because this one is for baltics ;)

so my question any german user with v20c ota or update message on lg bridge?

thx for ur replies :D

edited: sry forgot the caschys blog link here it is: :b

http://stadt-bremerhaven.de/lg-g4-marshmallow-kommt-langsam-ota/
[G4 Q&A, Help & Troubleshooting] trix95:
no german user who has ota for v20c i got more links confirming v20c but i am not able to get the message to download it i think i am stuck on v20a :/

https://www.go2android.de/flash-news-lg-g4-bekommt-nun-android-6-0-via-ota-169074/

https://curved.de/news/lg-g4-android-6-0-marshmallow-nun-auch-per-ota-update-verfuegbar-337666

http://www.androvid.de/news/lg-g4-android-6-0-kommt-via-ota-in-deutschland-an/2738/

http://www.netzwelt.de/lg-g4/156044...lt-android-60-update-via-ota-deutschland.html
[G4 Q&A, Help & Troubleshooting] trix95:
here is one more: http://technologiejunkies.de/lg-g4-android-6-0-marshmallow-kommt-nach-deutschland/

anyone from germany who got the v20c ota ?? :/
[G4 Q&A, Help & Troubleshooting] trix95:
Anyone? :/

Did no german User got the official v20c ota or sth over bridge? :/
[G4 Q&A, Help & Troubleshooting] SuperBommel:
Not yet, waiting as well. Did the update to V20a last year via LG Bridge. Today, no update, neither via Bridge nor OTA. In Poland, they seem to have the V20d via OTA.
[G4 Q&A, Help & Troubleshooting] SuperBommel:
Looks like that 20D just arrived: http://www.android-hilfe.de/thema/lg-g4-6-0-update-diskussionsthread.735951/page-42#post-9523295
[One (M8) Q&A, Help & Troubleshooting] imkentoy:
Hi guys,

What functionality or feature will I lose after unlocking bootloader?

Thanks.[emoji4]
[One (M8) Q&A, Help & Troubleshooting] Giblet-dono:
none, this is HTC not Sony
[One (M8) Q&A, Help & Troubleshooting] imkentoy:
This is amazing! I was thinking that it does the same thing as Sony; that loses camera features. Thanks mate!
[Miscellaneous Android Development] yadavji_technical:
[IMG="https://xolooneroms.files.wordpress.com/2016/01/988806_806106602868001_7348151032327479285_n.jpg?w=1108"]https://xolooneroms.files.wordpress.com/2016/01/988806_806106602868001_7348151032327479285_n.jpg?w=1108[/IMG]

based on android 5.0.2

kernal based on (3.10.54)

+=+=+=+=+=+=+=+=+=+===================

GIVE A BIG THANKS TO =

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

1.me(vikas yadav)

for this custom rom for xolo one

+=+=+=+=+==+=+=+=+==+=+=+=+==========

BUGS: ==[CHECK SS BELOW]

=======

NOT FOUND:p

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

1.USSID (working)

2.camera/video recording working

3.audio working

4both sim working

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

if u find any bug report to me.

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

DOWNLOAD LINK ROM LINK
[Miscellaneous Android Development] Varun c. Kulkarni:
Not flashing this os

Sir i have rooted my device xolo one and installed cwm recovery . Miui7 easily flashed but there is problem occurring while flashing this expection os plz help
[Android Q&A, Help & Troubleshooting] adityaupreti:
im getting this error while compile slimrom for grand 2 ms013g

build/core/binary.mk:619: recipe for target '/home/aditya/slim/out/target/product/ms013g/obj/EXECUTABLES/verifier_test_intermediates/ui.o' failed

make: *** [/home/aditya/slim/out/target/product/ms013g/obj/EXECUTABLES/verifier_test_intermediates/ui.o] Error 1

make: *** Waiting for unfinished jobs....

#### make failed to build some targets (01:10:17 (hh:mm:ss)) ####
[Android Q&A, Help & Troubleshooting] _that:
Looks like building verifier_test failed (it's in bootable/recovery). The real error message is further up in your output.
[Android Q&A, Help & Troubleshooting] adityaupreti:
so how to fix it
[Android Q&A, Help & Troubleshooting] _that:
- Read error message

- If you don't understand it, try searching the internet for at least 2 hours

- Fix bug

- Rebuild
[Nexus 9 Q&A, Help & Troubleshooting] Mckillagorilla:
Was using my N9 comfortably noticed a update for my rom and kernel was out so i updated as instructed. Everything was fine booted nicely stable, until when to reapply my layers Theme. I applied my old theme it worked fine but decided to try a new color from within the same theme. Got a boot loop, annoying but it happens so i re-flashed(dirty) the updated version of the rom. Still not booting past android animation, so a go back and do a wipe and re-flash the new rom, still not getting pass animation. Finally gave up and went to restore to the previous version of my rom but i still cant get it to boot pass android animation.

I'm out of ideas and tired any suggestions would be helpful.

rom: Pure Nexus

kernal: Fire and Ice

recovery: modded FnI Twrp
[Nexus 9 Q&A, Help & Troubleshooting] dmantilal:
No idea, but a full-wipe will solve it. Make sure to flash boot, vendor, & system.
[Nexus 9 Q&A, Help & Troubleshooting] sheenswizner:
Dirty flash won't work.

Wipe system & internal storage first than flash your favourite ROM.
[JAM, MDA Compact, S100 General] ATZatz:
Is it possible to Emulate WM5 or WM6 from SD card just like PSP Devhook?

:confused: :confused: :confused: :confused:
[Android Auto General] mateshelma:
Hi folks,

i ve been experiencing Android auto connection issues.

Want to connect to Skoda car infotainment from my rooted htc one V(CM 12.1 - Lollipop 5.1), but unfortnatelly havent had luck so far.

Downloaded newest AA apk, but it won´t even let me start the app. So I tried the older version (1.2.084954_2166577-release) of AA with successfull start. However, the only thing I see is the initial screen(see attachment), nothing else. Even after USB connection the infotainment display gives me "not compatible USB" warning. Have tried all MTP, PTP and only charging connection modes.

Is there something Im doing wrong? Is there any other way I can get this running?

Cheers for all ideas and comments.
[Android Auto General] alakiha:
I am almost in same situation!
[Android Q&A, Help & Troubleshooting] Navi6293:
hii guys,

please help me.. mid_changer is not changing my mid... i need to update my firmware 4.25.651.14 to 6.12.1540.4 ..to do so i need to change my mid (required)..
[Sprint Samsung Galaxy Note5] sahed01:
my phone is bricked! flashed a stock rom from sammobile. odin was able top flash it. but i'm having bootloop. i'm triying to flash a custom rom, but i can not since the oem is locked. i forgot to unlock it from inside. anyway... is there any way to unlock oem with odin or fastboot??
[Sprint Samsung Galaxy Note5] dschachm:
If you are having boot loop after flashing stock, try going into stock recovery and wipe data to factory reset
[Sprint Samsung Galaxy Note5] sahed01:
did it.. still the same problem! :'(
[Sprint Samsung Galaxy Note5] migjr415:
Hold volume down and then the power button at the same time to turn the phone of, it takes about 5 seconds. After that go back to download mode by pressing volume down, home, power...once you're in download mode follow these steps

http://xdaforums.com/show...php?p=64369712

I bricked my phone a couple of days ago and this is how I fixed it, you will loose root but at least your phone will work again, then you can re-root
[G3 Q&A, Help & Troubleshooting] KronicSkillz:
im downloading a stock mm rom right now so i can pull the apk from it and see what i can find out? has anyone else tried this on aosp yet or cm 13.?
[G3 Q&A, Help & Troubleshooting] justyourimage:
delete me
[G3 Q&A, Help & Troubleshooting] KronicSkillz:
i like the quick remote feature of being able to use the remote from the original device to program a custom remote, and i'm not the only one people have already ported it for android L juts not M yet.

with this feature i can program my tv/sat/android box all on one remote.
[G3 Q&A, Help & Troubleshooting] KronicSkillz:
So when I looked through the d855 mm rom I found the quick remote SDK but not the app... Very strange but of anyone wants the SDK let me know I'll post
[HTC Desire 610] Sephirth:
Hi

I have problems with backlight in my desire 610.

Phone does not respond to backlight adjust. It's always in ~50% of brightness. Also I see that backlight is flashing but just a little. Only seeing on white colors. How can i repair it? Changing coil 220 or whole screen? Coil from desire bravo will fit?
[Galaxy Note 4 Q&A, Help & Troubleshooting] greatgrandking:
MM based CM roms are absolutely out of question..because they are unusable ....i have tried all of them.

if you running a stable for daily driver rom with many customizations. ..... please suggest me.
[Galaxy Note 4 Q&A, Help & Troubleshooting] Tha:
im using this;

http://forum.resurrectionremix.com/index.php?PHPSESSID=prtsikt0k4ejnvk508afaejra2&topic=2037.new#new

really happy with it.

CM is loosing it in my honest opinion.... takes them way to long to even build a stable rom for most of the devices.
[XDA Assist] XDA Visitor:
Specifications:

Intel Atom Z2550 de 1.2Ghz Dual Core

1GB RAM

8GB storage

Frontcamera 0.3 MP VGA

Back camera 2.0MP

Model: Tr10cs1

Size: 10.1"

Just need a custom rom and we still don't have the stock rom.

All Venezuela are waiting for that rom.... :)
[XDA Assist] Saber:
Hi,

Thanks for using XDA assist.

Unfortunately, I couldn't find any useful information on XDA. However, you may want to post in the Android Q&A, Help & Troubleshooting forum. Please note that in order to post, you will need to create a XDA account.

Good Luck! - gsstudios
[A3000 Q&A, Help & Troubleshooting] raththaran:
can anyone port dolby atmos for our a3000 ???????