[THEME][MOD][6.0.1][5.1.1][5.0.1][4.4.4] Customize Your Galaxy Note 4 (N910F) [25/07]

[supergrobi94]

They're only tested on N910F. ツ

 

[ForestCat]

Does anyone know which apk contains the qmg/pio/png/etc used in the stock 6.0.1 dialer keypad?
I've decompiled 'SecContacts_M_OSup_Note_Legacy_USA.apk' and 'InCallUI_M_OS_UP_Legacy.apk', and I can't seem to find them.
Thanks for any help.

 

[fizzingbees]

I am facing issue after flashing system UI zip from here.

Whenever I have to restore twrp backup, made after flashing systmUi zip, I don't get lockscreen or quick tiles or status bar afterwards.

Or at times after restore completes and phone boots up I get key guard or systmUi force close erros to the point I can't use phone and the only way to repair my phone is to flash stock firmware and start from there.

Even reflashing zip doesn't fix it for me.

Why is it like that. Can anyone explain

I was using aosp system UI zip
I do have the F (snapdragon version) and I flashed it on stock rooted twrp, deknoxed marshmallow rom

---------- Post added at 11:50 AM ---------- Previous post was at 11:49 AM ----------

Does anyone know which apk contains the qmg/pio/png/etc used in the stock 6.0.1 dialer keypad?
I've decompiled 'SecContacts_M_OSup_Note_Legacy_USA.apk' and 'InCallUI_M_OS_UP_Legacy.apk', and I can't seem to find them.
Thanks for any help.

Try phone app

 

[fizzingbees]

I am facing issue after flashing system UI zip from here.

Whenever I have to restore twrp backup, made after flashing systmUi zip, I don't get lockscreen or quick tiles or status bar afterwards.

Or at times after restore completes and phone boots up I get key guard or systmUi force close erros to the point I can't use phone and the only way to repair my phone is to flash stock firmware and start from there.

Even reflashing zip doesn't fix it for me.

Why is it like that. Can anyone explain

I was using aosp system UI zip
I do have the F (snapdragon version) and I flashed it on stock rooted twrp, deknoxed marshmallow rom

---------- Post added at 11:50 AM ---------- Previous post was at 11:49 AM ----

Anyone got any idea about this issue
I know this is an old thread and most people. May have move don to newer devices, but can I anyone advise a fix

 

[kevintm78]

I am facing issue after flashing system UI zip from here.

Whenever I have to restore twrp backup, made after flashing systmUi zip, I don't get lockscreen or quick tiles or status bar afterwards.

Or at times after restore completes and phone boots up I get key guard or systmUi force close erros to the point I can't use phone and the only way to repair my phone is to flash stock firmware and start from there.

Even reflashing zip doesn't fix it for me.

Why is it like that. Can anyone explain

I was using aosp system UI zip
I do have the F (snapdragon version) and I flashed it on stock rooted twrp, deknoxed marshmallow rom

---------- Post added at 11:50 AM ---------- Previous post was at 11:49 AM ----

Anyone got any idea about this issue
I know this is an old thread and most people. May have move don to newer devices, but can I anyone advise a fix

It's caused from a signature mismatch. When I first started to learn to modify apps this was what I ran into time and time again with the SystemUI in particular. What I would suggest is to make a copy of your original SystemUI and flash or copy/paste that before making your backup or it also may work after a restore.

You could maybe get away with dirty flashing the original rom that you're restoring if you can't get a copy of just the SystemUI, but that mismatch doesn't leave a lot of options after the fact.

The ultimate solution would probably be signing the modified app with the original SystemUI signature which is easier than it sounds. Just requires a computer with 7zip or winrar, open up both apks with the archive manager, and move the META-INF and AndroidManifest.xml from the old apk to the new one. You could also (this might work better) move the res, classes.dex, and resources.arsc files from the new apk to the old one. The latter method is what I prefer.

 

[fizzingbees]

It's caused from a signature mismatch. When I first started to learn to modify apps this was what I ran into time and time again with the SystemUI in particular. What I would suggest is to make a copy of your original SystemUI and flash or copy/paste that before making your backup or it also may work after a restore.

You could maybe get away with dirty flashing the original rom that you're restoring if you can't get a copy of just the SystemUI, but that mismatch doesn't leave a lot of options after the fact.

The ultimate solution would probably be signing the modified app with the original SystemUI signature which is easier than it sounds. Just requires a computer with 7zip or winrar, open up both apks with the archive manager, and move the META-INF and AndroidManifest.xml from the old apk to the new one. You could also (this might work better) move the res, classes.dex, and resources.arsc files from the new apk to the old one. The latter method is what I prefer.

Tried to replace original systemUI apk. Didn't worked
Tried restoring system partition from twrp. Didn't worked
Flashed stock UI.. Nope

I'll look into dirty flashing stock firmware

But why would restoring twrp backup that had systemUI working fine, would on restore cause systemUI to crash. Thats just bizzare. Makes me feel my twrp backups have no value whatsoever

 

[Windroid-user]

Tried to replace original systemUI apk. Didn't worked
Tried restoring system partition from twrp. Didn't worked
Flashed stock UI.. Nope

I'll look into dirty flashing stock firmware

But why would restoring twrp backup that had systemUI working fine, would on restore cause systemUI to crash. Thats just bizzare. Makes me feel my twrp backups have no value whatsoever

Are you serious? I thought my backup was corrupt, thinking I deleted it...

I do have an older backup but still...
Dammit lol still learning.

 

[fizzingbees]

Are you serious? I thought my backup was corrupt, thinking I deleted it...

I do have an older backup but still...
Dammit lol still learning.

Oh yeah.
There is always something new we learn everyday

---------- Post added at 04:35 AM ---------- Previous post was at 04:27 AM ----------

It's caused from a signature mismatch. When I first started to learn to modify apps this was what I ran into time and time again with the SystemUI in particular. What I would suggest is to make a copy of your original SystemUI and flash or copy/paste that before making your backup or it also may work after a restore.

You could maybe get away with dirty flashing the original rom that you're restoring if you can't get a copy of just the SystemUI, but that mismatch doesn't leave a lot of options after the fact.

The ultimate solution would probably be signing the modified app with the original SystemUI signature which is easier than it sounds. Just requires a computer with 7zip or winrar, open up both apks with the archive manager, and move the META-INF and AndroidManifest.xml from the old apk to the new one. You could also (this might work better) move the res, classes.dex, and resources.arsc files from the new apk to the old one. The latter method is what I prefer.

Please clarify one thing
Assuming I get my hands 9n stock systemUI apk.
Do I move its meta-inf and androidmanifest.xml ( old stock systemUI) to new apk(e.g Aosp systemUI apk and then flash this new apk)

Or the 2nd method you mentioned where I move res, classes and resources from new old?? ... Or old new?? ..... (new refers to aosp systemUI apk and old refers to stock systemUI apk)

 

[bysalihidriscan]

@supergrobi94 hello again how can i remove this shadow?
What this code which Values code?

 

[supergrobi94]

Sorry, I don't know.

 

[fbnccst]

Im resurrecting my Edge (n915v). Looks like the links for 5.0.1 are dead, do you (or anybody here) still have the moddes files? Thanks

 

[supergrobi94]

Which files do you need?

 

[fbnccst]

Which files do you need?

The dark system ui mod (the aosp one?)
Im on 5.0.1

 

[w41ru5]

The dark system ui mod (the aosp one?)
Im on 5.0.1

Use substratum

 

[supergrobi94]

For 5.0.1 only the attached files are available and tested on N910F:

 

[fbnccst]

For 5.0.1 only the attached files are available and tested on N910F:

thank you very much!!

---------- Post added at 07:22 AM ---------- Previous post was at 07:21 AM ----------

Use substratum

it doesnt seem to be working, i gave up on it