yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The SELinux changes in TouchWiz 6.0.1 are going to significantly impact the functionality of DualBootPatcher if there isn't a way to enable per-type permissive mode (see Chainfire's post about the topic for SuperSU: https://plus.google.com/+Chainfire/posts/54rqimkQiUL). Right now, per-type permissive mode is heavily used as it allows the patcher to essentially make SELinux permissive for itself. With the TW 6.0.1 changes, the patcher would need to explicitly add "allow" rules for all of the operations it needs to perform. This is especially troublesome for in-app-flashing, which would require several hundreds, if not thousands, of SELinux rules to be added as it needs to read, write, and modify every file of the ROM.

So for now, TouchWiz 6.0.1 is not going to work without a custom kernel that enables global permissive mode for SELinux.
[Galaxy S 4 i9505 Original Android Development] irfanbd94:
Thanx:)
[Galaxy S 4 i9505 Original Android Development] midi_1996:
Can you make the app patch in a queue? I usually put patched zips on my SDCard to save space on internal st. and it's really slow, if i let the app for a while it may crash due to low memory killing. And there is kinda a "bug" (maybe it's not), when i rename the rom, i have to go back to the roms section, refresh it by pulling down, then the new name would appear. And it would be preferable to put the old name when renaming, sometimes it's just a typo and you are forced to retype everything, also a dark/black theme for AMOLED displays (please please please). Other than that, it's a tool I'm using eveutime! Thanks!
[Galaxy S 4 i9505 Original Android Development] ewangw:
[MENTION=4277844]chenxiaolong[/MENTION], DBP is a great tool and I'm glad you added the Moto X Pure to the list of supported devices. Chainfire mentioned in his blog that SuperSU would now patch the SELinux policy to get around the per-type issue. Could DBP be coded to do the same or possibly leverage what Chainfire has done within SuperSU?

"As this no longer works, SuperSU now patches the SELinux policy so that virtually all common cases root apps encounter should be covered."
[Galaxy S 4 i9505 Original Android Development] nutpants:
Can anyone suggest a custom tw kernel for the s4.

I'm running waman lite rom tw 4.4.2 for the 9505 than can be found a few pages back. Just trying to find something that lets me install the mbtool that I'm having issues with (I'm sure our great developer will fix whatever bug is causing this but if I'm the only one with the issue and I can get a different kernel then he will have less to consider fixing)

I've tried the adam kernel the rom comes with.googlymax (or however is spelled, yes I know my brain abhors spelling) and koontz kernels

(All the newest of course as development on kitkat tw died long ago)

Other wise every device I have (And that is far too many) is running this excellent app that has brought if not life then interest back to them.
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Have you tried the Aurora kernel?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
DBP is actually already patching the SELinux policy in a way similar to SuperSU. The latest changes Chainfire made do cover most use cases for root apps, but unfortunately, a lot more is needed for the in-app flashing feature to work. For example, a TouchWiz 4.4 ROM I'm looking at right now has 546 SELinux types that can be assigned to a particular file. Since it flashes a ROM, it needs to be able to create any file, so for each of those 546 types, I have to grant the following permissions:

read

write

create

getattr

setattr

relabelfrom

relabelto

append

unlink

link

rename

which results in 6006 SELinux rules to add. That only covers this particular use case. While it is a very time consuming task to figure out all of the rules that need to be added, I'm more worried about this opening a whole new can of hard-to-detect bugs caused by SELinux blocking a particular action.

Oh well, I might as well start working on this since there's a pretty good chance that the TouchWiz SELinux changes will make it to AOSP.
[Galaxy S 4 i9505 Original Android Development] corncobman:
Got a couple of error messages when attempting to run the Windows patcher version 2298.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Hey [MENTION=427477]chenxi[/MENTION]along just setting you know my Tmobile S7 Edge came in today. Will let you know when I have recovery so we can get in here
[Galaxy S 4 i9505 Original Android Development] Andycar:
Dear dualbooters and [MENTION=4277844]chenxiaolong[/MENTION]!

I'm going to report some offtopic or side-effect. But since here is so many great devs and good people, I decided to let you alll know anyway.

Recently, I set to unlock my primary TW ROM by two fingerprints. Then I went to by dual CM13 ROM and also registered the same fingerprints there.

Everything was fine during the rebooting into dual CM13 ROM. The bad suprise was to find out that fingerprint authentification doesn't work anymore when I booted to primary TW ROM.

I was able to re-register fingerprints in CM13 once, but later on it also ceased to work completely.

Now I only can wipe everything and setup both ROMs again from sctratch :(((

I tried removing /data/validity/template.db, but this didn't help...

I just thought I let you guys know, because currently there seems to be no workaround... Do not use fingerprints for authentification across different ROMs!

I think it has to do with some kind of internal implementation of Android OS, but really hope that workaround is possible...

P.S. My device is N910G (trltedt) - the Note 4 Qualcomm.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hey [MENTION=1111850]Andycar[/MENTION],

I may be wrong (since is is way outside my knowledge), but as far as I understand, the fingerprints stored in the hardware are invalidated when a ROM is flashed (or maybe just the kernel?). On my Note 4 (SM-N910T/trltetmo), a simple backup and restore of the same ROM from TWRP would trigger this exact behavior. I think this may be a security feature Samsung implemented so somebody can't just flash a custom kernel that could potentially extract existing fingerprint data from the hardware. I don't believe there's anything that we can do from Android to prevent this because it happens at a lower level :(
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Holy cow, you got it way before it was supposed to be released!

Btw, you still hold the record of helping me add support for the most number of devices :D
[Galaxy S 4 i9505 Original Android Development] Andycar:
Yes, I also encounterd exactly this by restoring TWRP backup with the stored FP in int...

Even so... in hardware, yes. But still maybe someone brave/curious guy will find the corresponding blob from Samsung and try to decompile it. :confused:Anyway, this is also far from my knowledge.

[MORE OFFTOPIC] P.S. I just wonder why previously people reported that simple removing /data/validity/template.db helped, which is not the case anymore... ?

[/MORE OFFTOPIC]

I guess we will have to live with it :rolleyes:
[Galaxy S 4 i9505 Original Android Development] rlorange:
chen was wondering if you could use the recovery emulator part of the app. to flash zips without recovery. (such as my new Teclast Tablet).

The only app around is Flash Gordon. Hoplessly out of date for Lolipop
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Good day. ..may I take this opportunity to ask if sometime in the near future you're going to continue on the multiboot backup app, at latest version it can only back up secondary and multi - slot 1 but attempting on slot 2 and 3 the functions of backup were not yet implementd; are you planning continue this project?

If so and interested in testers I'm in!

I've also left you PM concerning this round about last year Nov!

Enjoy

<<<New World Order (NWO)>>>
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Lmao [MENTION=4277844]chenxiaolong[/MENTION] yeah T-Mobile had it shipped to my one day after I placed my upgrade online. I'll also be able to help add an HTC One M9 before I have to send it back in.
[Galaxy S 4 i9505 Original Android Development] rlorange:
Hey I'm not really developing anymore but if i get the urge certainly this is first on my lost
[Galaxy S 4 i9505 Original Android Development] nutpants:
I'm having no issues with tw 442 and liquid smooth 444

Only registers my finger with tw on my s5 900w8

If anyone is having problems with updating mbtool on tw 442 on the s4. I'm doing fine now after I flashed the imperium kernel.

The 5 others I tried failed. I was going to post logs but have lost my high speed net and I'm down to a 25kb/s connection
[Galaxy S 4 i9505 Original Android Development] midi_1996:
I have an S5 with 2 RR-Roms (CM13 based) with both fp support, and I installed a Note 5 Port ROM as a 3rd ROM and they all have fp and working fine, one thing to point out, on S5 FP support on CM13 based roms we have a big bug (I don't know if it's the same as yours), when you add FP and a lock screen mode, then change the lock screen to either "None" or "Swipe" (aka : no security) then re-enable a secure lock screen, you cannot delete a FP (donno if adding is possible after that) and the FP wont be recognized. If you did similar steps, then you got the same problem as we do, check the FP Support Thread on your device forum (we have one on S5 forum, there must be one for your device too) and report this with the exact procedure (and giving a logcat while trying to remove/add/unlock with your FP). Good luck

[Sorry for off-topic]
[Galaxy S 4 i9505 Original Android Development] :
[MENTION=4277844]chenxiaolong[/MENTION] just want to confirm that latest merge of lenovo vibe z2 pro (kingdom_row) is working. thanks a lot for your work, for me as a rom maintainer for this device this will be very helpfull. thanks again
[Galaxy S 4 i9505 Original Android Development] -MaD-:
Had the same problem, but for me deleting of template.db in recovery worked twice... Deleting the file with a file explorer while in a rom didn't work.

Gesendet von meinem SM-N910F mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] Andycar:
Thanks bro, that's really helpful and insightful.

Отправлено с моего GT-I9505 через Tapatalk
[Galaxy S 4 i9505 Original Android Development] Chevelle1768:
Having issues using the latest DualBootPatcher. I can no longer flash any file in TWRP since v2289, v2265 and before works fine. And flashing within apps works fine. Logs attached.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The issue is that it's failing to mount the efs partition. Can you post a link to any boot.img file and a link to your recovery? You can grab any boot.img file from /sdcard/MultiBoot or extract it from any ROM's zip file.

EDIT: In-app flashing is not affected because Android mounts the efs partition by default, so the patcher doesn't have to do it itself.
[Galaxy S 4 i9505 Original Android Development] Chevelle1768:
Link to TWRP: https://dl.twrp.me/vs985/twrp-3.0.0-0-vs985.img.html

or https://dl.twrp.me/vs985/twrp-2.8.7.0-vs985.img.html

CM13 primary boot.img attached.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Should be fixed in 8.0.0.r2305.gb038752 :)
[Galaxy S 4 i9505 Original Android Development] Eliminater:
Delete
[Galaxy S 4 i9505 Original Android Development] amir_s_m:
[MENTION=4277844]chenxiaolong[/MENTION]

Could u plz add support for galaxy note 10.1 (2014 edition) 3g version (sm-p601 code lt033g).

I tried lt03wifi, but it didn't work out.

rom
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
The latest 2305 build is having some text/images space rendering problems. Someone also experienced this?
[Galaxy S 4 i9505 Original Android Development] Chevelle1768:
Yep
[Galaxy S 4 i9505 Original Android Development] kingknuts:
Support to LG G Watch

Hey [MENTION=4277844]chenxiaolong[/MENTION]:

Could you add support to the LG G Watch?? Here are the logs

(The new squashfs from Android 6.0.1 is annoying)

Thank you as always
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Yes, this is exactly what I have also.
[Galaxy S 4 i9505 Original Android Development] NoFrown:
Unable to patch files..

Dear [MENTION=4277844]chenxiaolong[/MENTION],

I am unable to patch zips, because it opens them instead of selecting them. You can see it in the attachment.

In a previous version, I was able to select flashify or Es file Explorer for selecting zips, can you really implement that(my last screenshot shows what I mean)

Device is OnePlus Two

Kind regards
[Galaxy S 4 i9505 Original Android Development] Shanks:
Hh

---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------

Maybe try flashfire to flash zips
[Galaxy S 4 i9505 Original Android Development] rlorange:
Nope doesn't work yet for my device. However TWRP has been made for the Teclast x98 pro and works with my x98 plus model so Yay!!
[Galaxy S 4 i9505 Original Android Development] monkteo:
don't choose [recent] choose to find the zip for patch [interne opslag] (I suppose it's mean internal storage) if you don't have exSD card.:good:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Interesting... I can't seem to reproduce the bug and not a single line of code was changed in the app itself. I'll take a look at it tomorrow. It might be a problem with my second build server.
[Galaxy S 4 i9505 Original Android Development] ewangw:
[MENTION=4277844]chenxiaolong[/MENTION], I can confirm this bug also exists on my Moto X Pure.
[Galaxy S 4 i9505 Original Android Development] Muffycheeks:
The latest patcher app only shows the primary rom and none of my other 3 roms.
[Galaxy S 4 i9505 Original Android Development] NoFrown:
I tried all options, but it keeps opening the zip file instead of selecting it.

I don't know how much work it is to add the third party app selection method, but since it has been there, I hope it's not a big deal.

Would be really great if it would be re-implemented, since the app is kind of useless for me now :(...

If anybody has had the same problem and found a solution, please let me know :D

Sent from my OnePlus Two
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
Somebody had that because he deleted Recent files app
[Galaxy S 4 i9505 Original Android Development] NewsTimes:
Still has issue: signal drop down when switch rom on Zenfone2 ?

Sent from my Surface Pro 4 using ChromeOS!​
[Galaxy S 4 i9505 Original Android Development] NoFrown:
Using another application for selecting files (for example my recent camera pictures) it does show all the third party options, so I assume that that is not the issue
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
The problem is fixed on 2310 build, thanks man! :)
[Galaxy S 4 i9505 Original Android Development] Andycar:
Yes. Same for me.

EDIT: fixed in build 2310.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Awesome! But I didn't do anything lol :D Let me take a look at my build servers logs to see why it happened in the first place.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Lol :D I just saw the AndroidGUI changelogs in the newest builds and I thought that you tweaked around. It's interesting, you can share why is this happening when you find out. Cheers.:highfive:
[Galaxy S 4 i9505 Original Android Development] alahkel:
[MENTION=4277844]chenxiaolong[/MENTION] can you add support for xiaomi redmi note 3 (mtk)? what do i have to provide to help you? thank you :)

Inviato dal mio SM-G920F utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
My best guess is that a dependency was updated on one build server, but not the other. I just cleared the caches on both servers so they'll redownload all the dependencies. Anyway, I've also updated the code so that the cards always use the minimum height (which I probably should have done in the first place :D)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Just flash the GetLogs file from https://snapshots.noobdev.io/ and send me the file it creates in /sdcard/logs/ :)

I'll try adding support for it, but Mediatek devices are notoriously hard to support, so I can't make any promises.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Very, very tempting: http://www.sammobile.com/2016/03/09/t-mobile-confirms-buy-one-get-one-free-offer-for-the-galaxy-s7/

Two S7 Edges + Gear VR + 1 year of Netflix for the price of one S7 Edge? YES PLEASE! (though my wallet is already starting to cry...)
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
[MENTION=4277844]chenxiaolong[/MENTION] just wondering if this post has passed under your watchful radar!

I asked possibility of adding that device to tree some 18 days ago...I respect your schedule, and when you're able plz help!

http://xdaforums.com/showthread.php?p=65442563

...I hope this won't be considered as spamming!

Have a great day!

<<<New World Order (NWO)>>>
[Galaxy S 4 i9505 Original Android Development] alahkel:
Thank you! I tried using FlashFire to flash it but it just reboots, unfortunately I need to wait for xiaomi to authorize my mi account to unlock the bootloader to flash twrp recovery (or do you know why it "fails" in flashfire? I flashed correctley xposed framework through flashfire)

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] Chevelle1768:
Its back again, v2310 was fine in the main screen of ROMs and sub menu ROMs. But 2312 has the issue in the sub menu.
[Galaxy S 4 i9505 Original Android Development] messi2050:
hi

can u add support for samsung galaxy j7 , i need this patch badly for debugging my cm13 port
[Galaxy S 4 i9505 Original Android Development] csmarino90:
Hi [MENTION=4277844]chenxiaolong[/MENTION], can you add support for the Motorola Moto G 2015? Thanks you for that great application. I am using it in my LG G2 and is great!

Atached the logs. Tell me if you need something more. Thanks!!

https://mega.nz/#!2tYhQDKa!d6Hi_4LpLbzhC0w01WjoAY5eYS0-OSAp2CCrLZGCdd8

Enviado desde mi MotoG3 mediante Tapatalk
[Galaxy S 4 i9505 Original Android Development] Andycar:
See what Chen wrote here:

Отправлено с моего GT-I9505 через Tapatalk
[Galaxy S 4 i9505 Original Android Development] Sagarking:
appreciate your work Please bring support for Samsung galaxy j7
[Galaxy S 4 i9505 Original Android Development] NewsTimes:
[MENTION=4277844]chenxiaolong[/MENTION]

Thanks for hard work!!!

How can I get signal on sim1 when I switch rom on Zenfone2?

Sent from my Surface Pro 4 using ChromeOS!​
[Galaxy S 4 i9505 Original Android Development] messi2050:
Logcat for adding support to j7

https://mega.nz/#!AMgAVSDK!OKm3xuh_BAZaf0xIgQV3zbm3uq9yPLOz0QaTrqYEERU
[Galaxy S 4 i9505 Original Android Development] amir_s_m:
Thx 4 your efforts.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] Dude, the problem is still present, but now it seems that it's limited to only rom details page. 2312 build.
[Galaxy S 4 i9505 Original Android Development] alahkel:
NVM, xiaomi just texted me back that I'm authorized to unlock my bootloader! So asai have some free time I'll unlock my bootloader, flash twrp and flash the getlogs zip through it and finally attach logs here, thank you again! :)

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] chavdar:
[MENTION=4277844]chenxiaolong[/MENTION]: Thanks for the great work! Your dual boot concept is really one of a kind! I am posting this for the third time, hope you can have a look at it

I am currently experiencing difficulties in updating the ram disk on my Galaxy S5 G900F TouchWiz Lollipop. ROM is installed as primary and no other rom is present. The patcher says ramdisk update is successful but after reboot it fails to boot and goes directly to recovery. I then have to restore the original ketnel before patching to get the ROM booting again. I am attaching a couple of logs, hope you find the time to have a look. Thanks again for the nice work!

Ramdisk log:

https://www.dropbox.com/s/epo83b4q8h28tit/ramdisk-update.log?dl=0

Multiboot

https://www.dropbox.com/s/83ytile5y69as21/MultiBoot.log?dl=0
[Galaxy S 4 i9505 Original Android Development] Gerxp:
I am getting mbtool needs update message running JDCTeam 6.0 as primary.

There is no "update ramdisk" option in 3-dot menu.

My primary rom is JDCTeam 6.o AOSP. Secundary is VRToxin.

Any help appreciated.
[Galaxy S 4 i9505 Original Android Development] dave7802:
Is this still specific to device Transformer

Running note 3 and was looking at this solution.
[Galaxy S 4 i9505 Original Android Development] Ather:
i get this error when trying to run DualBootPatcher-8.0.0.r2312.gcdd0c6a-win32
[Galaxy S 4 i9505 Original Android Development] twint14:
Can i switch bitween roms in recovery by flashing a file or something?

Thanks,
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Yes...head to install, then select images, by default it's zip files, bottom right, then navigate to your multiboot folder as you would looking for zips to flash...then select your desired secondary or primary ROM, select the boot.img of that ROM then flash it as boot file after selecting it!

Then you'll have switched to that ROM!

Or

If you've got multiboot utilities, flash/run it, it's AROMA installer, then select the ROM you want switch then you'll find options there, choose your desired!

This it's more easier!

<<<New World Order (NWO)>>>
[Galaxy S 4 i9505 Original Android Development] Bombo1:
Same here, with other errors
[Galaxy S 4 i9505 Original Android Development] alahkel:
logs xiaomi redmi note 3 (mtk) aka hennessy

Hi, I'm attaching here the logs for the hennessy (redmi note 3 mtk version).
[Galaxy S 4 i9505 Original Android Development] fanfzero:
What TW roms can I use as secundary? I've tried Imperium and Hulk rom (both have Aroma installer) and when I boot it makes 4 rumbles and reboots in recovery, I'm on I9505 so I patch the roms for jflte (there is no jfltexx option)
[Galaxy S 4 i9505 Original Android Development] george stamatos:
ASTRA N5 v 2.5 , with imperium kernel, work's amazing
[Galaxy S 4 i9505 Original Android Development] fanfzero:
Use the 20th February build https://snapshots.noobdev.io/files/...ualBootPatcher-8.0.0.r2265.ga8a1e6f-win32.zip
[Galaxy S 4 i9505 Original Android Development] Muffycheeks:
+1
[Galaxy S 4 i9505 Original Android Development] fanfzero:
It flashes, but when I reboot it makes the 4 rumbles on the Samsun Galaxy S4 screen ( the one before the bootanimation) and reboots in recovery
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
Did you set your kernel and update ramdisk on your primary rom? That maybe getting in the way.. I have lollirom as my multi slot, and I never use the dual slots
[Galaxy S 4 i9505 Original Android Development] fanfzero:
Yes, I have kernel set, how do I update ramdisk?
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
Here is the screen
[Galaxy S 4 i9505 Original Android Development] fanfzero:
Where is that screen? I can't find it
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Click the 3 dot menu to the right of the ROM you're trying to update ram disk for!

---------------------------------------------------------------------

[New World Order (NWO)

Telegram it's better than Whatsapp In every way!]

---------------------------------------------------------------------
[Galaxy S 4 i9505 Original Android Development] Garry050:
kltekdi is worked.

it working my scl23(kltekdi). but not support "kltekdi"(It works when you edit the Build.prop. and twrp default.prop)

please support kltekdi. no need patch, need add device list.(Working "Add ROM,Patch ROM,Ramdisk Update,Set Kernel,Sync App Data,Wipe,Switch ROM,Boot Second ROM,Boot Data ROM")

Sorry my bad english