[ZIP] [FLASHABLE] [ROOT] [04-28-2017] (Re)Enable Hotspot (Stock or Custom) [MM & N]
Introduction
This flash fixes the telephony database (i.e., /data/data/com.android.providers.telephony/databases/telephony.db) and if necessary injects busybox and init.d support into ROMs. The purpose is to properly enable hotspot tether support. It fixes the hotspot support on each reboot so if you lose hotspot due to, for example, a factory data reset, this will repair the database at the next boot.
DISCLAIMER
Always read the DISCLAIMER file before committing to the use of this flashable mod.
What It Does NOT Do
The flash does not add the hotspot menu item to ROMs that do not otherwise have it. In other words, if you do not have a 'Hotspot' menu in your Settings or other toggle items, this flash will not add those. You need to talk to your ROM developer in order to get those.
What It Does
The flash does two basic things for ROMs WITH built in init.d support:
Installs a working sqlite3 executable at /system/xbin/sqlite3;
installs an init.d script at /system/etc/init.d/01-hotspot to correct telephone database settings;
installs an init.d script at /system/etc/init.d/02-hotspot to add a quick setting tile for hotspot;
sets global setting tether_dun_required to 0 (zero).
Most custom kernel flashes modify the init files to support calling on /system/xbin/run-parts to run the scripts in /system/etc/init.d -- check the boot image you are using.
The flash does quite a bit more for ROMs missing init.d support (e.g., stock):
Installs a working busybox (and all applets) at /system/xbin;
Installs a working sqlite3 executable at /system/xbin/sqlite3;
Injects init.d support into the boot image (boot.img);
installs an init.d script at /system/etc/init.d/01-hotspot to correct telephone database settings;
installs an init.d script at /system/etc/init.d/02-hotspot to add a quick setting tile for hotspot;
regularly checks and keeps global setting tether_dun_required at 0 (zero);
add build.prop setting to enable USB tethering.
The script at /system/etc/init.d/01-hotspot logs its operations to logcat so you can see what it did, if anything at all. Make sure you have logging enabled if you use a kernel that supports such changes (e.g., my SkyHigh port).
Hope this helps those who are having troubles with hotspots after wiping data before or after flashing ROMs.
Instructions for ROMS that DO HAVE init.d Support
Download the hotspot-v5.zip file from Android File Host (MD5 sum: 201820413864c9d60e971d06a59ac8ff)
Copy the hotspot.zip file to your phone, assume to /sdcard/hotspot-v5.zip
Boot into TWRP Recovery
Install the zip (e.g, from /sdcard/hotspot-v5.zip)
Reboot to system (Android)
Instructions for ROMS that DO NOT HAVE init.d Support Built-In
Download the hotspot-busybox-initd-v6.zip file from Android File Host (MD5 sum: 60f01ccdfe88a22673ef0efe6e390309)
Copy the hotspot-busybox-initd-v6.zip file to your phone, assume to /sdcard/hotspot-busybox-initd-v6.zip
Boot into TWRP Recovery
Install the zip (e.g, from /sdcard/hotspot-busybox-initd-v6.zip)
Reboot to system (Android)
Previous Versions:
Instructions for ROMS that DO HAVE init.d Support
Download the hotspot-v4.zip file from Android File Host (MD5 sum: 40082313f82c7cbe7b866d77e250f16e)
Copy the hotspot.zip file to your phone, assume to /sdcard/hotspot-v3.zip
Boot into TWRP Recovery
Install the zip (e.g, from /sdcard/hotspot-v4.zip)
Reboot to system (Android)
Instructions for ROMS that DO NOT HAVE init.d Support Built-In
Download the hotspot-busybox-initd-v4.zip file from Android File Host (MD5 sum: c495361fdd3cc72e52e868473fe5fb92)
Copy the hotspot-busybox-initd-v4.zip file to your phone, assume to /sdcard/hotspot-busybox-initd-v3.zip
Boot into TWRP Recovery
Install the zip (e.g, from /sdcard/hotspot-busybox-initd-v3.zip)
Reboot to system (Android)
Version 3 for ROMS that ALREADY HAVE init.d Support Built-In: Android File Host (MD5 sum: 77611280dac47c6ca328aff73d721d56)
Version 3 for ROMS that DO NOT HAVE init.d Support Built-In: Android File Host (MD5 sum: 48a3e3ba78892927a3b26e45b2052e30)
Version 2 hotspot-busybox-initd-v2.zip: Android File Host (MD5 sum: 5b978c9312f79f6d26f541811160350a)
Version 1 hotspot-busybox-initd.zip: Android File Host (MD5 sum: 45b8bea3e01fa74e443ea1ec9791561f)
ROMS Tested
TeamSPR ROM
Stock, rooted 6.0.1
Stock, rooted 5.1.1
Note: Some recent ROMS include this script in the init.d support already (e.g., TeamSPR v3).
If you verify on another, please let me know and I'll add it to this list.
Notices
The flash for ROMs not having init.d support includes:
The busybox program in binary form. Busybox is a GPLv2 licensed tool, which provides you the option to receive source code underlying the binary executable. That source code can be found here: http://git.busybox.net/busybox/. If you want that source code and cannot obtain, feel free to ask me and I will get you a copy by reasonable means, at your cost.
The sqlite3 program in binary form. SQLite is a public domain program. You can read its license here: https://www.sqlite.org/copyright.html.
The programs known as mkbootfs, mkbootimg and unpackbootimg. These are all licensed under the Apache 2.0 License. The sources may be found here: https://github.com/osm0sis/Android-Image-Kitchen/blob/master/authors.txt.
Disclaimer
*** Legal Disclaimer -- READ ALL OF THE FOLLOWING ***
If you use the software, or convey it to someone else, you and all subsequent conveyees are bound by the following:
LEGAL DISCLAIMERS AND ASSUMPTION OF THE RISK BY THE USER OF THIS PROGRAM
Assumption of the Risk of Use
YOU ASSUME, AND AGREE TO ASSUME, ALL THE RISK OF HARM BY USING THIS PROGRAM. THIS PROGRAM MAY VOID YOUR WARRANTY WITH A THIRD PARTY, IT MAY IMPROPERLY OPERATE AND DAMAGE YOUR DEVICE, IT MAY CAUSE ANY MYRIAD OF HARMFUL OUTCOMES REGARDING YOUR DEVICE OR THE USE OF THE DEVICE ON WHICH IT GETS INSTALLED. YOU ACKNOWLEDGE THAT YOU ARE AWARE OF THOSE RISKS, UNDERSTAND THOSE RISKS, AND VOLUNTARILY AND INTELLIGENTLY ELECT TO ENGAGE THOSE RISKS BY USING THE PROGRAM.
Disclaimer of Warranty
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME ALL LIABILITY AND AGREE THAT IN NO EVENT WILL YOU SEEK ANY FORM OF RECOMPENSE, WHETHER LEGAL OR EQUITABLE, INCLUDING BUT NOT LIMITED TO NECESSARY SERVICING, REPAIR, CORRECTION OR OTHERWISE.
Limitation of Liability
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM, PERMITTED OR NOT, BE LIABLE TO YOU FOR LEGAL DAMAGES OR EQUITABLE RELIEF, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Change log
This post will keep up to date the various changes that occur from version to version of each flash in this thread.
hotspot-v5 and hotspot-busybox-initd-v5:
Updated to support Nougat.
hotspot-v3 and hotspot-busybox-initd-v3:
Now sets all APNs that have MMS type set to include DUN type as well (tethering). The belief is this should also fix many non-sprint carrier variants, but testing all those is not something possible for the author.
All init.d scripts log to logcat for all versions.
hotspot-busybox-initd-v2:
Now honors (and reinjects) SELINUX enforcement tag on the boot image to prevent the 'red text' folks were seeing on boot after flashing;
Now logs to logcat (Android system log) when it takes actions (every five minutes or so it verifies that the telephony database and system properties still are set for tether support.
This worked perfectly on the SPRrom , thank you. ?
i have galaxy s6 g920p (BOJ7)
in setting menu i cant see Mobile Hotspot!!
i flash this file and nothing happend.
please help me i need hotspot
mahdi72 said:
i have galaxy s6 g920p (BOJ7)
in setting menu i cant see Mobile Hotspot!!
i flash this file and nothing happend.
please help me i need hotspot
Click to expand...
Click to collapse
A little more info please. ROM? Recovery.log from TWRP? Hard to help flying blind.
Also, see where your telephony.db file exists.
Sent from my SM-G920P using Tapatalk
tdhite said:
A little more info please. ROM? Recovery.log from TWRP? Hard to help flying blind.
Also, see where your telephony.db file exists.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Stock Rom
Rooted
Software version : G920PVPU3BOJ7
Hardware version :G920P.02
Android : 5.1.1
Base Band : G920PVPU3BOJ7
Build Number :LMY47X. G920PVPU3BOJ7
Telephony.db = /data/data/com.android.providers.telephony/databases/telephony.db
/data/user/0/com.android.providers.telephony/databases/telephony.db
tnx
Updated -- Custom and Stock ROM Support
New flash supports ROMs missing init.d support. See the OP.
tdhite said:
New flash supports ROMs missing init.d support. See the OP.
Click to expand...
Click to collapse
Sprint S6 G920P, 6.0.1 stock root.
after flashing, nothing changes. i dont see the option to turn on/off hotspot.
yaibakt said:
Sprint S6 G920P, 6.0.1 stock root.
after flashing, nothing changes. i dont see the option to turn on/off hotspot.
Click to expand...
Click to collapse
Click on the Hotspot menu Item. It doesn't look like a menu item, but it opens the hotspot setup.
Sent from my SM-G920P using Tapatalk
could you please give me a screenshot of it?
yaibakt said:
could you please give me a screenshot of it?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click that Hotspot item.
Sent from my SM-G920P using Tapatalk
silly me.
I dont have that hotspot and tethering setting either
yaibakt said:
silly me.
I dont have that hotspot and tethering setting either
Click to expand...
Click to collapse
Please attach the file at /data/local/tmp/tdh-hotspot.log so I can see what is happening in the update.
Also, are you rooted?
Sent from my SM-G920P using Tapatalk
tdhite said:
Please attach the file at /data/local/tmp/tdh-hotspot.log so I can see what is happening in the update.
Also, are you rooted?
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Yes, my s6 is rooted, so that i could flash your zip via twrp...
I dont have that log file
Sent from my SM-G920P using Tapatalk
Do you have OEM Unlocking turned on in Developer's settings? What you show suggests the flash was not able to persistently rewrite the boot image.
Tell me that answer above and whether the file exists at /init.d.rc and if not, that tells me the flas is not in fact suceeding at persistently updating the boot image.
Sent from my SM-G920P using Tapatalk
tdhite said:
Please attach the file at /data/local/tmp/tdh-hotspot.log so I can see what is happening in the update.
Also, are you rooted?
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Hi tdhite, my phone was rooted. And this is my tdh-hotspot.log. I also flashed your file but still don't get hotspot and tether Can u check for me ty
I also got the file init.d.rc in root and my OEM unlocking opened too
andyz0301 said:
Hi tdhite, my phone was rooted. And this is my tdh-hotspot.log. I also flashed your file but still don't get hotspot and tether Can u check for me ty
I also got the file init.d.rc in root and my OEM unlocking opened too
Click to expand...
Click to collapse
Ok, hang on folks, looks like I found (I think) the issue some are seeing. Long story -- a selinux permissions issue. Working on it.
@tdhite My offer is still on the table
Updated -- 03/18/2016
Does a couple *more* things now:
keeps tether_dun_required at 0 (there is a background process that sets it to 1)
sets up build.prop for usb tethering
See the original post, use the flash for ROMs lacking init.d support.
Let me know if if that helps with folks not getting the tether option at all, and for those working, you should not see provisioning requirements. IF you do, wait a minute or so and try again. There is a service that checks randomly between every 15 to 45 seconds for changes to the tether_dun_required global setting.
Related
Made by pepcisko!!! I just wanted to post this here for those of you who have forgotten about the V6 Supercharger!
Original post here! Go hit the thanks button for him!
======================================================================
Contents
Patcher Information - Post 1 (this post)
[*]Simplified Tutorial - Post 2http://forum.xda-developers.com/showpost.php?p=31917581&postcount=2
[*]Download/Changelog - Post 3
======================================================================
----------------------------------------------------------------------------------------------------------------------------------------------
I hate that Zeppelinrox's thread is being cluttered with OT questions about this.. so opening a new thread. Please post any JellyScreamPatcher.exe questions here. Thanks.
----------------------------------------------------------------------------------------------------------------------------------------------
[experimental] Windows tool for patching services.jar for V6 SuperCharger
Opening note: When replying to this post, please do not quote it!!! Or quote selectively.
For each fully quoted reply a puppy will die somewhere in the world. If you love puppies as much as I do, you'll stop quoting long posts.. thank you
----------------------------------------------------------------------------------------------------------------------------------------------
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.. LOL I guess you knew it already.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because your phone bootloops. Please
* do some research if you have any concerns about features included in my utility
* before using it! YOU and only YOU are choosing to make these modifications.
* I'm providing no ETA's, though usually I'm responding PM's in a timely manner ;)
*
* While the tool provides some backup functionality, allowing you to roll back to
* a working system, feel free to create a nandroid backup trying this ;)
*
*/
For downloads and changelog, see Post #2
----------------------------------------------------------------------------------------------------------------------------------------------
Preface:
Many of us V6 Supercharger users have been flashing nightlies nightly and dailies daily, resulting in the need for a patched services.jar almost daily since the automatic web patcher no longer works for Android 4.1.1 Jellybean files, we had to stick with manually patching this files as described in Zep's guide here. Eventually Zep prepared several versions of the Jelly_Scream_Smali_Patcher_Test_x.sh script, which does the job perfectly, but the user still has to get his services.jar, extract the .smali files, put them to the phone, put the script to the phone, run it in the phone's terminal, copy the patched .smali files back to the PC etc. etc. and for many of us, this is time consuming (and difficult for others). Time is money, right?
Currently, this tool is using a ported version of the ALL_ROMS_Ultimate_Jar_Power_Tools-Jelly_ISCream+Maximum_MultiTasking_Mods-Smali_Patcher_Test_11.sh script for patching.
So... here an automated workflow, which assumes a few things:
you are running a MS Windows operating system (tested on Win7 x64)
you have Java installed. This was tested with Java7, should run fine on Java 6 as well. In the Q&A section below I provide a link to download Java. Make sure that java.exe is accessible from any folder (is in PATH). Java 7 installs the binaries into the windows/system32 folder, so I hope you have that folder in your PATH. If not, just google how to add a folder to the PATH, there are many tutorials on the web.
[optional] you know how to connect your phone to the PC via USB
[optional] you have ADB drivers installed (either via Android SDK or from your phone's manufacturer)
[optional] you know how to enable USB debugging in your phone and did that
[optional] the USB connection mode is NOT "mass storage" (for the online mode) - please set it to "Charge only" or "None" (varies from device to device)
How to patch the services.jar file
The following assumes you have a "stock" (or unchanged) services.jar in your phone's ROM or in my tool's framework subfolder .
Note: The current version should still be considered as beta-release. While it works for me (most of the computer stuff works when I'm near it, my family has been puzzled about this since long ago.. LOL), it may not work for you. Please report any bugs you find (thread, PM) and I'll be happy to fix them. Although I inserted many "hit the Enter" prompts into the tool, it's always good to run the tool from a console so that you can keep the output in case you flash through the workflow too fast
Also, the tool maintains an activity.log file where it flushes messages about what's happening. If you encounter a bug, send me this file. Please do not copy/paste the log contents into the thread!!! Attach it. Or upload to any cloud service and send me the public URL.
Click to expand...
Click to collapse
Tip: When running the tool, feel free to enlarge the command prompt window vertically
Click to expand...
Click to collapse
After running the tool and passing the initial screen, you will be presented with a choice between online and offline mode.
Online mode
Online mode assumes that the phone is connected via USB. In this mode, the tool can pull all the information from the phone. Not only the files, but system variables, as well as some debug info (e.g. is the ROM odexed?)
Connect the phone via USB
Enable connection mode "Charge only" or "None". This won't work, if the phone is in "Mass Storage" mode!
Sit back and enjoy (and don't forget to answer the tool's questions!)
After patching there will be a warm reboot
Offline mode
Offline mode means, that there will be no interaction of the tool with the phone via USB. You need to do all the file transfers and in case of odexed ROMs, the final in-phone patching, manually. Also you will have to enter some other information into the tool manually.
make sure to copy your /system/framework/services.jar to the tool's framework folder. If you have an odexed ROM (e.g. stock), copy the whole /system/framework folder contents to the tool's framework folder.
make sure to know your system's version because the tool will ask for it
make sure to know your BOOTCLASSPATH variable. It can be pulled from the phone using the command
Code:
adb.exe set | grep BOOTCLASSPATH
make sure you know if the ROM is odexed or not
After patching, you will need to transfer the patched files to the phone and perform manual patching/replacement:
Odexed ROM:
For odexed ROMs, there is some more patching required that you can do in the phone.
copy services.jar from the 'dist' folder to the sdcard
copy 'dexopt-wrapper' from the 'odex' folder to the sdcard
copy 'dexopt-wrapper.sh' from the 'scripts' folder to the sdcard
Make sure they are in the card's root folder !!
In the phone, open Script Manager or any other app that can run shell scripts with superuser rights.
Open the app, run the dexopt-wrapper.sh script. A warm reboot may occur, since the script will restart the framework
Reboot to recovery, Clean Cache, Clean Dalvik Cache
That's it
Deodexed ROM:
update-signed.zip in the dist folder
Copy this file to your sdcard, then reboot to cwm recovery and install it from there. Then do a Dalvik Cache wipe, Cache wipe and reboot.
services.jar in the dist folder
You can copy this file to phone's /system/framework folder and replace the existing one. Make sure that the new file will have owner/group 'root' and permissions 644. Then reboot to recovery, clean Cache & Dalvik Cache.
Rollback
In case something goes wrong, there should be a message about that in the activity.log file.
Feel free to send this file to me - either attach (not paste!!!) the file to a post in this thread, or upload it to any of the cloud services and tell me the URL. I'll take a look.
Before patching, the tool creates backup of the files as a CWM recovery compatible update.zip file. It will sit in the backup folder. This is your way back to a working system. Of course, you can do a nandroid backup..
So what is the tool actually doing?
Very easy to explain.
it pulls the services.jar (and odex files if needed) from your phone to the working folder (or takes an existing one that you put into the folder)
it uses the baksmali.jar to decompile the services.jar/odex
creates a backup of the unchanged files
it runs a ported perl version (and compiled to exe) of Zeppelinrox's JellyScream patcher script (v6) to patch the .smali files
it uses smali.jar to compile the new classes.dex
inserts the new classes.dex back to the services.jar
[optionally] it pushes the new services.jar back to the phone
[optionally] for ODEXed ROMs, created services.odex from the patched services.jar
[optionally] for deODEXed ROMs, it creates and signs an update.zip that can be flashed in CWM recovery
collects the garbage and exits with a nice message .. LOL
Q&A
Q: It doesn't decompile the services.jar and complains that the .smali files don't exist !!!
A: Yeah, probably your Java is crap. Install Java JRE from Oracle's web (http://java.com/en/download/index.jsp), it will offer you the latest version. I tested with Java 7, but latest releases of Java 6 should work as well.
Q: Getting java errors "not recognized" "not found" and so !!!
A: You probably don't have the java executable in the system PATH. Search the web on how to do this. Typically, Java7 installs its binaries to the <system>:\Windows\System32 folder, other versions may act differently.
Q: I'm getting bootloops after patching the services.jar with this tool!
A: Make sure to Wipe Cache, Wipe Dalvik Cache and Fix permissions in the CWM recovery. ALso, feel free to send me your original services.jar, I'll take a look. If you have an odexed ROM, send me the whole /system/framework folder and the activity.log file generated while using this tool in "online" mode.
Q: After reboot with the new services.jar file, it says "Android is upgrading" and optimizing apps, even though I did not wipe my dalvik cache.
A: Well, yes that is expected. It will take a while, depending on how many apps you have installed.
Q: Will my phone's memory be blazing fast and effective after this?
A: No, you still have to run the V6 Supercharger script.
Q: Does it run on Linux?
A: Not yet, but it will. I need some more internal testing to release a Linux version.
Q: Does it run on ODEXed ROMs?
A: Yes !!!
Q: Why is the executable so large???
A: Blame PAR long story short, I wrote my stuff in Perl and used Perl to port Zep's stuff as well. Then I compiled the script to exe using the PAR:acker package, resulting in the huge executable. I know, there is another way, to use Activestate's PDK (Perl Development Kit), but the license is approx. $250 and I just don't have that money for spending on a single tool. PDK creates much smaller files (approx. 1/3rd), but for now we have to stick with what we have
Q: Tool fails and in the log I see messages like "failed to copy 'C:/super/backup/services.jar' to '/mnt/sdcard/services.jar': Permission denied"
A: Make sure the USB connection mode is other than "Mass Storage". It can be "Charge Only" or "None", really this is depending on the device you own.
Q: Isn't there a virus included in the executable?
A: LOL.. No. This community gave me a lot since 2007 and I have no intention to harm it in any way. If you are using NOD32 and it starts complaining about the URL to my file I posted above, let me know. ESET support is pretty quick in identifying and fixing false warnings
Enjoy.. and feel free to PM me in case of any questions. I'll keep this post updated all the time.
Thanks
- Zeppelinrox for the V6 Supercharger and the associated scripts/tools
- Rexstor for the ODEX guide
- Android community for all the other tools (smali/baksmali/sign)
- Google for Android... luv ya!!!
If you feel like I deserve a beer for what I've done, feel free to consider donating to Zeppelinrox first as I'm just making his fabulous work a tiny bit more accessible. And if you still think I deserve a beer, you can use the button below.
Simplified Tutorial
Here's my tutorial on this if the above is unclear!
Starting
Download the patcher
Plug in your phone with USB debugging ON!
Now you're already almost done!
Patching
Go to where you downloaded the patcher and unzip it.
Open the JellyScreamPatcherV6_0.9.x.x folder and launch the .exe
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
READ ALL THE INFORMATION and select your desired options.
After you have completed patching, you may now exit the cmd window and reboot your phone to recovery.
Wipe the CACHE, DALVIK CACHE, and FIX PERMSSIONS!
Reboot and enjoy!
ALL CREDITS TO pepcisko and Zeppelinrox!!!
Download/Changelog
Downloads
http://dev.pepcok.info/jellyscreampatcher/JellyScreamPatcherV6_0.9.0.6.7z
Changelog
0.9.0.6 [2012-09-23]
still using ALL_ROMS_Ultimate_Jar_Power_Tools-Jelly_ISCream+Maximum_MultiTasking_Mods-Smali_Patcher_Test_11.sh
added a proper error reporting when sdcard is not writable in online mode
0.9.0.5 [2012-09-20]
using ALL_ROMS_Ultimate_Jar_Power_Tools-Jelly_ISCream+Maximum_MultiTasking_Mods-Smali_Patcher_Test_11.sh
multiple users with Odexed ROMs have reported this version to work. Feel free to try
with online mode, there is a framework restart after patching, causing warm reboot of the device.
0.9.0.4 [2012-09-13]
using ALL_ROMS_Ultimate_Jar_Power_Tools-Jelly_ISCream+Maximum_MultiTasking_Mods-Smali_Patcher_Test_11.sh
Warning for odexed ROM users - proceed with cautions, many have reported bootloops (even with previous version). Investigating
0.9.0.3c [2012-09-12]
patcher: Jelly_IScream+Time_Killer_Killer--Smali_Patcher_Test_9.sh
fixes STUPID bug with storage detection (I hope)
0.9.0.3b [2012-09-12]
patcher: Jelly_IScream+Time_Killer_Killer--Smali_Patcher_Test_9.sh
storage detection, as requested by one of the users (thanks Zep for the code! )
fixes in shell scripts for online mode
removal of the -f flag for rm commands
0.9.0.3 [2012-09-11]
patcher: Jelly_IScream+Time_Killer_Killer--Smali_Patcher_Test_9.sh
odex: if the baksmali decompile fails (e.g. file missing, although being in BOOTCLASSPATH), the tool will create an alternate BOOTCLASSPATH based on the files that were pulled from the phone and try decompile again. It even this fails, then I guess the world will end in 2012
ui: revamped the whole ui, user is now selecting offline vs online (adb) mode at the beginning
ui: added a proper note for the user to make sure to clean cache/dalvik cache when rebooting for the first time with the new services
ui: added instructions for the user in offline mode (when he wants to do the final steps manually)
internal: added some file exists checking, online (with adb) mode works better now and is prettier
other: as always, please read what the tool says.
0.9.0.2 [2012-09-06]
patcher: Jelly_IScream+Time_Killer_Killer--Smali_Patcher_Test_9.sh
instead of using crappy adb commands, the final patching is done via shell scripts in the phone - please help me test that. I already restored my phone's system partition 4 times (since patching a GB MotoDefy+ with ICS HTC Evo services is not healthy, but necessary for my testing), all the final patching seems to work fine here. Tested for both odexed and deodexed files and my phone already hates me
the tool will make a backup of your original services.jar/odex file into a CWM recovery update.zip (will be in the backup folder) .. that's your way back from potential hell
fixed a typo in manual API level selection - thanks for catching
0.9.0.1 [2012-09-05]
patcher: Jelly_IScream+Time_Killer_Killer--Smali_Patcher_Test_9.sh
few fixes (shell user detection, trying to implement better /system rw mount )
0.9.0 [2012-09-05]
patcher: Jelly_IScream+Time_Killer_Killer--Smali_Patcher_Test_9.sh
initial support for ODEXed ROMs - alpha version. I need testers please ! Since my phone does not have any odexed ICS or JB, I was able to test with sample files from xda fellow members end-to-end, but the real full fledged experience, I can't verify
0.8.9.2 [2012-09-05]
patcher: Jelly_IScream+Time_Killer_Killer--Smali_Patcher_Test_9.sh
minor update to capture the system calls, stdout and stderr into the log, for people who have problems with java. Let's see how it works
0.8.9 [2012-09-04]
patcher: Jelly_IScream+Time_Killer_Killer--Smali_Patcher_Test_9.sh
updated adb communication
added proper logging
internal preparation for ODEX ROMs (yeah, 0.9.0 will work with ODEXed ROMs !!!)
added framework folder as the working folder (reduces file clutter.. LOL)
0.8.5 [2012-08-27]
patcher: Jelly_IScream+Time_Killer_Killer--Smali_Patcher_Test_9.sh
update-binary from Titanium Backup
0.8.4 [2012-08-26]
patcher: Jelly_IScream+Time_Killer_Killer--Smali_Patcher_Test_8.sh
minor fixes only
0.8.3 [2012-08-25]
patcher: Jelly_IScream+Time_Killer_Killer--Smali_Patcher_Test_8.sh
this one should work with services.jar files where the smali files don't include debug information
0.8.2 [2012-08-23]
some more checks for "non-compatible" data, will provide warnings to the user in case of "incompatible" services.jar. Users seeing that message should proceed with caution until the next version. Zeppelinrox is aware of the potential problem.
0.8.1 [2012-08-22]
patching based on Zep's v7 script
resolves patching issue with the services.jar from the Alliance 2.1 ROM for Galaxy Note (GT-N7000)
resolves a weird compilation error when running the executable
0.8 [2012-08-22]
First public version, based on Zep's v6 patcher
Deleted
???
I like your tutorial so make sure you keep that but i heard the dev is picky about permissions, how did you get permission?
Anyway, i'll be trying this
THEindian said:
I like your tutorial so make sure you keep that but i heard the dev is picky about permissions, how did you get permission?
Anyway, i'll be trying this
Click to expand...
Click to collapse
I think you're talking about Zeppelinrox... lol pepcisko is very nice and allowed for me to post this!
What exactly does the v6 super charger do and will it work with Toasted Marshmallow?
Sent from my Toasted Marshmallow using Tapatalk 2
pyr0sphere said:
What exactly does the v6 super charger do and will it work with Toasted Marshmallow?
Sent from my Toasted Marshmallow using Tapatalk 2
Click to expand...
Click to collapse
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind
NO LAUNCHER REDRAWS, faster than ever, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
And yes! It works with Toasted Marshmallow... I'm using it now
Coryyyy said:
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind
NO LAUNCHER REDRAWS, faster than ever, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
And yes! It works with Toasted Marshmallow... I'm using it now
Click to expand...
Click to collapse
With this substantial increase in performance, is there an opposite hit in battery life?
Sent from my Toasted Marshmallow using Tapatalk 2
pyr0sphere said:
With this substantial increase in performance, is there an opposite hit in battery life?
Sent from my Toasted Marshmallow using Tapatalk 2
Click to expand...
Click to collapse
Not at all
Sent from my SGH-T999 using Tapatalk 2
I've never noticed a change on AOSP/AOKP/CM ROMs when using V6.
I have, however, noticed a significant change on Sense ROMs, since they are such memory hogs.
Sent from my HTC Glacier using xda app-developers app
estallings15 said:
I've never noticed a change on AOSP/AOKP/CM ROMs when using V6.
I have, however, noticed a significant change on Sense ROMs, since they are such memory hogs.
Sent from my HTC Glacier using xda app-developers app
Click to expand...
Click to collapse
I concur!,I although a slight improvement on AOKP/CM ,it really seems to help Sense Roms alot!!
:good:
estallings15 said:
I've never noticed a change on AOSP/AOKP/CM ROMs when using V6.
I have, however, noticed a significant change on Sense ROMs, since they are such memory hogs.
Sent from my HTC Glacier using xda app-developers app
Click to expand...
Click to collapse
Yep I totally agree only sense version I believe in my opinion that don't need super charge would be 2.1/4.0 Lite since they don't get up ram
sent from my glacier via tapatalk
I'll be adding to my tutorial on how to continue on to actually using the V6 Supercharger after patching the services.jar! I just realized that some might not know you still have to run that I just got wait until my cord ships in... mine broke.
Sent from my SGH-T999 using Tapatalk 2
Somebody recommended flashing this V6 cuz I'm experiencing slow data & wifi speeds on the Glacier One V. Do I have to do the services.jar step or can I just go ahead & download the sh file & run the exe?? Lil bit confused here
I cannot seem to gain adb shell root rights when I'm on elginsk8r or 0.0 jellybean roms. Works fine with toasted marshmallow. Anyone else have this problem?
I'm not sure about roasted marshmallow, but the 0.0 Rom doesn't have and adb root selected by default under settings/developer options. Check there.
Sent from my T-Mobile myTouch 4G using XDA
hi, good work bro.
i got this
Activity log:
[system call] java -Xmx1024M -jar "C:/Users/Papenko/Desktop/JellyScreem/smali/smali.jar" "C:/Users/Papenko/Desktop/JellyScreem/framework/classout" -o "C:/Users/Papenko/Desktop/JellyScreem/dist/classes.dex"
2012-11-18 04:18:12 | D | [stdout] Error occurred during initialization of VM
Could not reserve enough space for object heap
2012-11-18 04:18:12 | D | [stderr] Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
2012-11-18 04:18:12 | E | [smali] Classes.dex does not exist after compilation. Exiting.
2012-11-18 04:18:16 | D | [cleanup] deleting the framework\classout folder
2012-11-18 04:18:16 | D | [cleanup] deleting the framework folder contents
I just put the last and problematic part. Cheers M8
Just tried using JellyScream Patcher 0.9.0.6 with the new ViperTouch v1.0.0 ROM and stuck at HTC logo. Clear cache/dalvik/fix permissions. Still no good. Dirty flash of ViperTouch and I'm back in business (minus the supercharger of course).
All that said, it could just be me. I didn't have luck with Pimp My Rom either (not on ViperTouch but garlest(sp?) Sense ROM) where others seemed to do ok.
Code:
#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.
*/
Hello guys, this is an unofficial build of AOSP Nougat (with tag android-7.0.0_r6). Kernel is based on CM13's, with some recent commits in kernel/common in AOSP. Sources and patches are available at the end of the post.
Note: this ROM is just for having the first taste of Nougat, and thus missing a lot of key features. I may not be able to update it regularly.
Basic hardware functionality:
Almost everything works, except video hardware encoding, which causes camcorder to fail. HW decoding works though.
Everything should be working since 20160903.
I didn't find more hardware failures, but there can be more.
And remember, the proprietary firmwares and blobs are still in the age of Marshmallow, and a system won't be complete without corresponding firmwares and blobs.
Known bugs:
1. HW disk encryption is likely broken. I reverted some commits to make cryptfs_hw build, but I'm not sure if that works. Do not try it.
2. SELinux is permissive, and init allows service without a SELinux domain to start.
3. GPS may take longer to obtain a position fix. (yes it's working... sorry for the misunderstanding)
4. Only Launcher2 is included. You may install a new one as you like.
5. No LiveDisplay and gestures except DT2W (DT2W can not be turned off via Settings app for now) Color calibration is possible, see FAQ below.
6. Default input method could be broken. Be ready to "pm install your_ime.apk" in adb shell. Fixed in 20160828
7. com.qti.dpmserviceapp may produce continous FC. You can disable it via adb shell ("su -c pm disable com.qti.dpmserviceapp"). Removed in 20160828
8. Rotating screen while playing video can cause the display to "split" Fixed in 20160903
9. Camera service and media codecs all run in the same process, eliminating one of the security enhancements of Android N. May not be fixed until new HAL and blobs are available.
So the security improvements in Nougat are not making much difference in this only-a-taste ROM. If you rely on this, it would be better to wait for official releases.
FAQs:
1. Root / Gapps?
I'm using SuperSU 2.76 stable and OpenGapps 7.0 pico. They work without any issue.
If your contacts / calendars is not syncing, try the following steps:
1. Goto Settings > Apps, tap "Show system" in menu
2. Find "Google Contacts Sync", tap on it, tap "Permissions", turn on everything
3. Go back to Detail screen, clear its data
4. Go back to app list, clear "Contacts Storage"' data
5. Do the same for calendars (2-4)
6. Reboot
Click to expand...
Click to collapse
2. F2FS?
I did not test this myself... But kernel has support already (of cource, it's from CM) so you may have a try. Remember to backup!
EDIT: Some users reported that F2FS partitions are corrupted. If you are using F2FS, maybe you should wait.
Click to expand...
Click to collapse
3. Menu key / App switcher?
Menu key now acts as recents, since I don't think the former is as useful as the latter. And there is no more lag while tapping home button since we don't check for double tap anymore.
Click to expand...
Click to collapse
4. TWRP shows error?
If that's two lines of "log", you can safely ignore it.
If there is something else, please stop and post it here.
If you are using MultiROM, you may modify update-script. Read the first ~8 pages and you will find it.
Reference: I'm using official TWRP 3.0.2 w/o MultiROM This recovery didn't get replaced by stock one...
Click to expand...
Click to collapse
5. File manager (to install APKs)?
http://forum.xda-developers.com/showpost.php?p=68402423&postcount=73
Click to expand...
Click to collapse
6. Disable HW keys, enable soft keys, screen color calibration?
Disable HW keys: echo 0 > /proc/touchpanel/keypad_enable (needs repeat on reboot)
Enable soft keys: echo "qemu.hw.mainkeys=0 >> /system/build.prop (once)
Screen color calibration: echo "32768 31784 27852" > /sys/class/graphics/fb0/rgb (needs repeat on reboot, change the values as you need. This example is 100% R, 97% G, 85% B)
Optionally you can enable color enhancing: echo 1 > /sys/class/graphics/fb0/color_enhance
Click to expand...
Click to collapse
Screenshot spoiler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashing Guide by @The Dork Knight Rises
In the 3rd post. Direct link: http://forum.xda-developers.com/showpost.php?p=68397804&postcount=3
Video hands-on by @savadam
https://www.youtube.com/watch?v=r54vWk-Azh8
Thanks for all your support!
Download:
20160919: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAYWRKd1owSUNudEU Mirror 2: https://mega.nz/#!fEk1CTyJ!F8rdnqT_oiipP-tHCuzFGFvsQGmUV6LRaD2t81N2WIA
You can still use HALs from 20160906 if you want.
(And if you are posting this somewhere else, please include the HALs in your post)
Older versions:
20160918: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAMWZ4OEx6Unp5bU0 Mirror 2: https://mega.nz/#!rdlkgboI!LQuFDtcppbizC_7Tfww1uWAmhw-lYuxjAlrhg9Z0tuQ
20160910: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAdGVTV3V0ekZaWHM Mirror 2: https://mega.nz/#!XEsTESpR!QDa7he2jdPCeIsbMY1vJAlCZ0RokAKV0IdtyuB0R-yc
20160906: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAWHNFb0xyYlBZM3c Mirror 2: https://mega.nz/#!zBVX1DTZ!S-LnpIEgJqn1r7So6QmEoD_APUqDnp93XbP-Ug__XBk
CAF and original AOSP HALs: https://drive.google.com/open?id=0BwkmhbR5VHpAaGdCQmxDUWgxQlU
Note on the HALs:
AOSP HALs (msm8996 display + msm8974 media) can not record screen, but they "seem" to make the system smoother. (msm8974 display HAL cannot be used because it corrupts the display when rotating screen with video playing)
CAF HALs (both based on vanilla CAF LA.BF.1.1.3_rb1.13) can record screen but "seem" not to be so efficient as AOSP ones.
The HAL included in the ROM are the AOSP variant.
20160903: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpATlN5T29WTS01Qkk Mirror 2: https://mega.nz/#!OcFlTDDK!EYiNpfE-9Pxx2wu4Oto7kO_oevfe0bMkXOTdhP1HDZc
20160831: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAVE1WR2xYd180MzA Mirror 2: https://mega.nz/#!jE92iSAD!pl0NMU6PPY3UNXE5DTDBKLUd4sFLG6fNTaUUMI0xdzg
20160828: Mirror 1: https://mega.nz/#!XdlXFDBQ!p7E0N64IEkGHn4GBzOZQDTCgR4KdD00O0dRwJlEnvcw Mirror 2: https://drive.google.com/open?id=0BwkmhbR5VHpAczA2T2g0RUZRS3c
20160827: https://drive.google.com/open?id=0BwkmhbR5VHpAUVdWUHNlc0lHZWs
Note: please read "known bugs" section before flashing! Also you can read the guide below.
When updating the ROM, just dirty-flash new build and Gapps (if you use them).
In order to prevent your recovery from being replaced by the stock one, flash SuperSU along with the ROM.
Sources:
Kernel: https://github.com/updateing/android_kernel_oneplus_msm8974/tree/nougat
Device: https://github.com/updateing/android_device_oneplus_bacon/tree/nougat
Build system: https://github.com/updateing/platform_build/tree/custom-kernel
And there are a lot more repos I didn't fork. The changes there as well as local_manifest are here:
20160918+ Check GitHub
20160910 https://drive.google.com/open?id=0BwkmhbR5VHpAcmo1RjhPd0N1c3c
20160906 No new patches except the HALs. For AOSP HALs, check previous patch archive and Sony's guide. For CAF HALs, just cherry-pick "Fix clang build" from CM.
20160903 https://drive.google.com/open?id=0BwkmhbR5VHpAQXFqZEJCT21UNDA
20160831 https://drive.google.com/open?id=0BwkmhbR5VHpASW54QnR4eGFlR1E
20160828 https://drive.google.com/open?id=0BwkmhbR5VHpAOEx2OWNYcE1xU2s
20160827 https://drive.google.com/open?id=0BwkmhbR5VHpALXdkNkptRnBLMkU
Changelog:
20160919
Fixed Fackbook crash by avoiding preloading libboringssl-compat.so (CM camera HAL is the only camera HAL that does not require this)
Updated BT configuration (please test if it has any side effect. Sometimes you need to search twice to find your Bluetooth gadgets.)
Tried to fix network location (added Google's network location provider)
20160918
Reverted to previous "stub" power HAL. May fix lagging and unusual power consumption noticed by some users.
Tried to fix NFC FW download mechanism. May fix non-working NFC for some users.
20160910
Updated to NRD90U (android-7.0.0_r6)
Switched to CM/QCOM power HAL. The original power HAL is more like a placeholder.
Now on Tap can be launched by long-pressing home button
Switchable WebView implementation, thanks to @fards here
Note:
1. If you are experiencing display issues (such as screen flicker with FLV SW decoding), try switching on "Disable HW Overlay" in Development Settings.
2. If you need multi-user feature, remove /system/priv-app/com.qualcomm.location. Otherwise the system will crash. It was accidentally added in this build.
20160906
Switched back to AOSP HALs to increase performance, but screen recording is broken again. You can choose CAF HALs listed above to fix that. Camcorder and HW encoding work with both variants, no need to worry.
Updated media profiles. Front camera knows that it is not capable of 1080p recording.
20160903
Fixed HW encoder and camcorder (they are different issues, though related) (and switched to CM13 media HAL)
Fixed display corruption while rotating screen with video playing (by switching to CM13 display HAL, don't know which lines of code fixed that)
DT2W can be turned off via Settings
Added Reboot option in power menu
20160831
Fixed crash in World Clock page when selecting countries/regions
Fixed hang in Developer Settings when the ROM is installed as secondary
Fixed crash when taking photos with HDR on
Added support for kexec
Added Stk
20160828
Fixed default input method FC
Remove com.qti.dpmservices to prevent FC
Dev: updated build system to finally automate everything
20160827
Initial build
Click to expand...
Click to collapse
Notes on the sources:
1. Build system produces correct boot.img in $OUT, but the boot image in OTA zip still has no DT included. Fixed in 20160828
2. Some fixes are really "dirty" (as I'm not able to find a proper way)...
3. Some JNIs fail to build (lots of C++ symbols no found). You may try linking C++ libs dynamically (c++_static -> c++_shared) to avoid this. See 20160828 patches, packages/inputmethods/LatinIME for example.
4. Some apps require android-8 ndk, but the earliest version in the tree is android-9. A symlink will do (or you can change the Android.mk in app) but I'm not really sure this will not introduce any bug.
5. Android N split mediaserver into multiple processes to improve security, such as cameraserver, mediacodec, etc. But camera blobs and old HALs were not designed like this. They assume they run in the same process, thus a buffer created by blobs are being used everywhere, which will cause illegal memory access under Android N. I reverted lots of patches about this, forcing camera and codec services to run in the mediaserver process as before - security compromised with functionality, again.
Hope you enjoy this.
I am going to try this out, thanks @updateing for your work:good:
If I could find fixes then I would send an pull request.
The All-In-One Post
Oh look at the time...it's flashy time already? XD
Screenshots:
(Layers themes work. Use Substratum app)
Guide to flashing this properly (TWRP v3.0.2-0):
(THIS GUIDE IS MAINLY FOR THE FIRST BUILD 20160827. AS I AM RUNNING IT SMOOTHLY, I DO NOT PLAN TO UPDATE TO 20160828, AS IT HAS SOME MINOR FIXES, ALREADY COVERED IN MY GUIDE.
IF HOWEVER, YOU'RE FLASHING 20160828 OR LATER BUILD, HERE'S WHAT YOU SHOULD DO DIFFERENTLY:
-Flashing Google keyboard is not mandatory, as default input mode has been fixed
-adb steps do not need to be performed as the com.qti.dpmserviceapp has been removed
-You probably shouldn't flash the SystemUI Tuner mod zip, as the SystemUI APK from previous build may not be compatible with new build. If you flash it on 28 build and have SystemUI FCs or missing SystemUI, just reflash ROM, and don't flash the mod.
REST OF THE GUIDE REMAINS THE SAME)
(This guide is for flashing as primary ROM without MultiROM. MultiROM guide by @7u5h4r: http://forum.xda-developers.com/showpost.php?p=68413163&postcount=242)
TL;DR version (that means short version)
http://forum.xda-developers.com/showpost.php?p=68552389&postcount=1172
Download ROM zip from OP and Google Keyboard flashable zip, as well as any of the zips I linked below.
Wipe your device (data, cache, dalvik/ART cache; preferably even system, just to be as "clean" as possible)
(NOTE ABOUT DIRTY FLASHING:
-If you dirty flash this ROM (eg. flashing newer build), you will need to flash GApps again along with the ROM zip as GApps are not preserved
-This ROM actually booted for me even on a dirty flash from an MM custom ROM, and as a result I didn't face a lot of the problems you'd face on clean flash (GApps crashes, continuous qti app FCs, etc)
But a lot of my apps were crashing until I reinstalled them, and in any case, it is not advised to dirty flash when coming from MM)
Flash ROM zip and keyboard zip, optionally any of the following addons (DO NOT FLASH GAPPS YET):
-SuperSU (v2.68+) for root
-Any of the mods I linked below
-Any other mods like Viper4Android etc (AT YOUR OWN RISK)
Boot into the ROM. you'll probably see a lot of crashes, ignore them, and just find a PC for the next step
(Optionally, you could try to enable Developer Options by tapping past the FC dialogs, once you have DevOps enabled, you'll see an option to mute FC notifications till next boot)
Using ADB on your PC, disable the com.qti.dpmserviceapp package by running following commands:
Code:
adb devices
You should see a device in the list of devices connected
Code:
adb shell
pm disable com.qti.dpmserviceapp
If you get error with permissions, you may need root. If your device is rooted:
Code:
su
pm disable com.qti.dpmserviceapp
(SKIP 6, 7 & 8 if you do not need Google services)
Now reboot into recovery and flash a compatible GApps package (USE 7.0 GAPPS ONLY)
Boot into ROM
Go to Settings>Apps
Find Google Play Services, and go to its Permissions. Enable essential permissions. Now Play Services won't keep crashing on you. Also find Google Contact Sync and give it permission to access Contacts.
Go to Settings>Accounts and add your Google account
Profit
Praise DuARTe
Hit Thanks if this helped
Here's some helpful zips for you guys!
My flashable zip to ENABLE Navbar/softkeys (same as the one on the MM thread) https://drive.google.com/open?id=0B2Y1syM7UNuDYVRhM3BTYVA3SXc
Flashable zip to DISABLE HW keys
https://drive.google.com/open?id=0B2Y1syM7UNuDSFZwUHNLQ0RfdXM
Flashable zip to ENABLE HW keys (revert changes made by zip above)
https://drive.google.com/open?id=0B2Y1syM7UNuDalVLVzd0SFdLekk
Flashable stock bootanimation (same as the one in MM thread; since this ROM doesn't really have a bootanimation and uses the basic fallback bootanimation)
https://drive.google.com/open?id=0B2Y1syM7UNuDelFPZVh6dmxSR2c
Flashable zip to ENABLE Hidden SystemUI Tuner Features (thanks to @AL_IRAQI, see his original guide here)
This one was tricky, my first time decompiling an APK. I was getting some crashes at first, but I think this ZIP should work fine (I tested it on a dirty flash, and it works)
https://drive.google.com/open?id=0B2Y1syM7UNuDd0JBV2ViMXl1bnc
Flashable Google Keyboard 5.1
https://drive.google.com/open?id=0B2Y1syM7UNuDbnBmdEtWZlRlNlk
Flashable Nexus Launcher (credits to uploader)
https://www.androidfilehost.com/?fid=24588232905722237
Replace the stock Power Menu with an extended custom power menu (thanks to @nofx161):
See his post
Link to app
Layers themes are supported, use Substratum app (Play Store link) to apply
(ROOT NEEDED)
NOTE: Themes made only for Substratum will not work (properly) as this ROM doesn't support Substratum (that will need patches to ROM source). Only which support RRO/Layers will work without any issues.
Wow! Great work
Subscribed!
thanks for your work dude
Cool, thanks, gonna try asap
Enviado desde mi A0001 mediante Tapatalk
Great! Thank u dev!
updateing said:
2. SELinux is permissive, and init allows service without a SELinux domain to start.
Click to expand...
Click to collapse
Which sepolicy did you use? I am porting to a different device and Im currently trying to fix neverallows which is painful but I think I merged a commit to qcom/sepolicy which allows domain to start (im not very good in sepolicy). Its based off Cyanogenmod qcom/sepolicy repo. If you want to take a look its here android_device_qcom_sepolicy-1 and I had to add one thing to platform_system_sepolicy. I hope we'll be able to fix sepolicy soon.
Awesome.... Downloading already.
Awesome! Has anyone tried If gapps work?
Flashed it. But i get a FC all the time
com.qti.dpmserviceapp has stopped.
I cant do anything..?
Deltastylez said:
Flashed it. But i get a FC all the time
com.qti.dpmserviceapp has stopped.
I cant do anything..?
Click to expand...
Click to collapse
Really sorry that I forgot this. You could do "pm disable com.qti.dpmserviceapp" in adb shell (su first if it asks so)
A fellow hamster I see! Nice one.
updateing said:
Really sorry that I forgot this. You could do "pm disable com.qti.dpmserviceapp" in adb shell (su first if it asks so)
Click to expand...
Click to collapse
I am kind of a newbie to ADB
Could you perhabs tell me how to? step a step?
Thanks!
Deltastylez said:
I am kind of a newbie to ADB
Could you perhabs tell me how to? step a step?
Thanks!
Click to expand...
Click to collapse
You may find a lot of adb tutorials around...
But if there is a mute option in the FC dialog, you can mute it and disable in Settings.
updateing said:
Really sorry that I forgot this. You could do "pm disable com.qti.dpmserviceapp" in adb shell (su first if it asks so)
Click to expand...
Click to collapse
updateing said:
You may find a lot of adb tutorials around...
But if there is a mute option in the FC dialog, you can mute it and disable in Settings.
Click to expand...
Click to collapse
well, getting this error
" Error: java.lang.SecurityException: Shell cannot change component state for com.qti.dpmserviceapp/null to 2 "
Never mind, fixed
updateing said:
You may find a lot of adb tutorials around...
But if there is a mute option in the FC dialog, you can mute it and disable in Settings.
Click to expand...
Click to collapse
i've tried through adb shell but it doesn't work shell cannot change component state for com.qti.dpmserviceapp/null to 2 moreover it is not possible to disable it in settings thank u for your job
anyone!! please any reviews??
Knew it wouldn't be long before the famous Bacon machine got that great taste of nougat :good:
holy crap holy crap
EVERYONE BOARD THE HYPE TRAIN! CHOO CHOO!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Definition
Let me first define what I mean by Creator's Experience. This ROM is just as good as your stock ROM on KNOX 0x0. I am in no way taking credit for any of the development in this ROM, I'm just repackaging the stock Samsung ROM in Samsung's experience how they created it. But if you flashed stock ROM you may get a ton of KNOX warnings so selling the device or giving your device to someone else would make it more complicated and frustrating due to nagging popups that you have to disable by first setting up the device. I wanted to create something that you can restore your device to when you get bored of a custom ROM, or you just want to use the latest stock firmware again.
This ROM will never contain any tweaks or system addons, it is barebones stock with no KNOX and stubs so people can use it as a rescue/reference firmware.
Purpose
Being the owner of the Korean Samsung Galaxy S8+ 128GB/6GB (SM-G955N), there are only so many stock firmwares available from Updato or Sammobile. All listed firmwares contain all the CSCs located in the /system partition, and the CSC file toggles between them. This means that regardless of what CSC you flash on the device, you will activate all the applications that were disabled by the CSC (KT mobile apps should be disabled on the SKT CSC, and vice versa). So flashing a Canadian CSC will still have every single South Korean carrier bloat on your device, which sucks.
This is a strange situation with 955N users, where ALL THE BLOAT is stored in /system/priv-app, while the csc is just one small file that controls which applications are active/inactive on the device.
Process
So, what does this mean? I wanted the stock international 955F ROM on my device, really badly. But Odin refused to flash it due to a secure write/invalid magic string error. I have tried everything from modifying the PIT tables in the ROMs to flashing custom ROMs. As much as custom ROMs are great, I wanted something I could fall back to when sh*t hits the fan, as well as something that fit the stock lifestyle...since I would really have loved to keep KNOX 0x0 if the Korean firmware was not as bloated as I thought it would be.
So for those who were searching for the stock ROM that was created with stock in mind, I have repackaged the 955F stock using the kitchen by @SuperR., with removed KNOX + KNOX apps (Secure Folder, KNOX Settings 1 & 2, Samsung Pay, Samsung Pass, etc.), removed stub apps (Microsoft apps folder) and removed CSC (I will elaborate more below).
As it takes me from 3-6 minutes to download stock firmware, I will be keeping this up to date for people who will need a rescue zip.
Reproduction
The reason why I'm keeping this as clean as possible is because it functions the same way as the Odin package. The AP will be the ROM zip, while you have to flash your own custom kernel, and flash the CSC package by @Tkkg1994. Finally, to top everything off, Magisk will be flashed.
A flowchart of this process (clean flash) is listed below:
Flash CeX stock (this ROM)
Flash the CSC using the CSC utility tool by @Tkkg1994: https://forum.xda-developers.com/galaxy-s8+/development/utility-flashable-csc-selection-v1-0-0-t3605264
Flash the kernel, I highly recommend @jesec's Jesse Kernel: https://forum.xda-developers.com/galaxy-s8/samsung-galaxy-s8--s8-cross-device-development/kernel-jesse-s-kernel-galaxy-s8-exynos-t3603521
Flash Magisk v12+: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
A flowchart of this process (dirty flash) is listed below [dirty flash is supported on CeX, as long as you follow these steps]:
Use TWRP and wipe /system
Flash CeX stock (this ROM)
Flash the CSC using the CSC utility tool by @Tkkg1994: https://forum.xda-developers.com/galaxy-s8+/development/utility-flashable-csc-selection-v1-0-0-t3605264
Flash the kernel, I highly recommend @jesec's Jesse Kernel: https://forum.xda-developers.com/galaxy-s8/samsung-galaxy-s8--s8-cross-device-development/kernel-jesse-s-kernel-galaxy-s8-exynos-t3603521
Flash Magisk v12+: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Anomalies
At the current stage, this is just the stock Samsung firmware. So any bugs found in the official bugs list of the current firmware revision would be present in this ROM. See the second bracketed codename in the title of this thread.
Do you use Netflix or Amazon Prime Video?
With their Widevine DRM Module, it bypasses anything Magisk Hide has to offer.
Using TWRP, remove /system/lib/liboemcrypto.so, then reboot to system.
If you ever want to restore stock, this is the AQEB binary: https://www.androidfilehost.com/?fid=961840155545569722
Screenshots
There really doesn't need to be any screenshots, unless you have never turned on your phone on stock ROM before...but here, I'll show you Settings.
SafetyNet?
This is a simple phenomenon solved by having both a custom kernel with KNOX 0x0 simulation, like Jesse's kernel, and Magisk v12 installed with Magisk Hide enabled. It is confirmed that CeX respects SafetyNet.
Programmatically Displayed Debloated Applications/Services/Libraries
Code:
system/app/Facebook_stub*
system/app/MSSkype_stub*
system/app/SecureFolderSetupPage*
system/priv-app/OneDrive_Samsung_v2*
system/priv-app/SecureFolder*
system/priv-app/SamsungPass_1.1*
system/priv-app/Excel_SamsungStub*
system/priv-app/PowerPoint_SamsungStub*
system/priv-app/Word_SamsungStub*
system/container*
system/app/BBCAgent*
system/app/Bridge*
system/app/ContainerAgent*
system/app/ContainerEventsRelayManager*
system/app/kioskdefault*
system/app/KLMSAgent*
system/app/Knox*
system/app/KNOX*
system/app/MyKNOX*
system/app/RCPComponents*
system/app/SecurityLogAgent*
system/app/SwitchKnoxI*
system/app/UniversalMDMClient*
system/container*
system/etc/secure_storage/com.sec.knox*
system/preloadedkiosk*
system/preloadedmdm*
system/preloadedsso*
system/priv-app/KLMSAgent*
Download Links
AndroidFileHost Folder (Autopushed builds): https://www.androidfilehost.com/?w=files&flid=185563
AQH3 builds (August):
FullRebaseOptions from last build:
https://www.androidfilehost.com/?fid=745425885120758691
Normal build:
https://www.androidfilehost.com/?fid=817550096634795846
AQF7 build (June): https://www.androidfilehost.com/?fid=673368273298964156
AQEB build (May): https://www.androidfilehost.com/?fid=817550096634773510
Credits & Thanks
@SuperR. for his kitchen
@jesec for him helping out when I was frustrated something isn't working, and pretty much his experience with his 955N
@fahadali2315 for refreshing my memory of messing with a Samsung device
Anyone I missed, just hit me up in private!
XDA:DevDB Information
CeX, ROM for the Samsung Galaxy S8+
Contributors
nicholaschum, fahadali2315
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Current Stable Version: AQH3
Stable Release Date: 2017-05-31
Created 2017-06-01
Last Updated 2017-08-29
Building with SuperR Kitchen for your own stock region ROM
If you're interested in creating your own flashable ZIP based on a ROM, I will be listing the full instructions on how to get your own stock ROM up and running.
I will be building the latest XXU builds as soon as they drop.
Please do not PM me, instead, post in the thread for people to learn.
Prerequisites:
- Your device MUST be of the Exynos variant, with an available TWRP on the device. If you have a Qualcomm device, close this window now!
- You must have a Linux environment. I know @SuperR.'s kitchen works on Windows using Cygwin, but as an AOSP developer, I work with Linux to build stuff!
- Sudo account
- Collect and utilize as much wits as you can!
- I will be doing all of this from the command line using SSH, no GUI for this!
1) Download the latest SuperR kitchen here: https://forum.xda-developers.com/ap...chen-superr-s-kitchen-v1-1-50-v2-1-6-t3597434
by doing this (press enter after each line in this code block):
Code:
curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | sudo bash
sudo apt-get install git-lfs
git lfs install
git config --global credential.helper cache
cd ~/
git clone https://bitbucket.org/superr/superrs-kitchen.git
cd superrs-kitchen
./superr
The first time running the kitchen, you may need to install dependencies. It should automatically install all dependencies for you, but if it keeps asking you to install the same dependencies, you should install them using
Code:
sudo apt-get packageName
.
After all dependencies are installed, press 1 to create a new project, and name it whatever you want. In this example I will name it STOCK.
Press Q once the project is created (quits SuperR kitchen)
2) Download your Samsung stock firmware. There are two main sites nowadays to get Samsung stock firmwares from, including Updato and Sammobile.
Updato: http://updato.com/firmware-archive-select-model?q=SM-G955F&rpp=15&order=date&dir=desc&exact=1
Sammobile: https://www.sammobile.com/firmwares/galaxy-s8/SM-G955F/
You will need to get the firmware on your Linux box, or from Updato, right click Download (the orange button) and click Copy Link.
If you are planning to download from the SSH box, do:
Code:
cd ~/superr-kitchen/superr_STOCK && wget link_of_updato
3) Your firmware file is now ready to be loaded up into the kitchen. So do:
Code:
./superr
Then click 4 to extract for a new ROM, then click "y"
4) When it asks you whether you want to include cache.img, it doesn't really matter if you do or don't. Click "y" and include it in the ROM.
5) It will then ask you to type a name for your output ZIP
6) If it asks you where to locate the partition info from, pick the entry that is recommended, which takes the partition from system.img and recovery.img (Detect by-name from boot/recovery images (recommended))
So simply click 1.
7) Finally, we must set the perm type/archive type of your images. Click 1 for set_metadata (KitKat+)
NOTE: I have tried using Sparse dat for Korean 955N image - which working at a cost of all Google apps crashing/not responding, but doing so on the 955F ZIP will completely break and cause it to get stuck in TWRP trying to flash. set_metadata is the most stable.
8) You can now fiddle with the ROM! It is highly recommended to replace the stock kernel with @jesec's kernel, but make sure you extract his other folders from his ZIP into your working directory (~/superr-kitchen/superr_STOCK/system/*) or you won't boot! You can either opt for this, or just flash the kernel ZIP to retain support from Jesse (this is what I picked for CeX).
Key configurations (the options I picked for CeX):
->7) Boot/Recovery Tools
- Unpack boot.img
- Type 5 and disable forceencrypt
- Type 1 and pack boot.img
->8) ROM Tools Menu
- Asserts Menu (if you're trying to do 955N ROM)
- Add/Remove Device (dream2lte) <- change from dream2lteks or any other model, since TWRP only recognizes dream2lte.
->6) Debloat Menu
- Custom Debloat
- ~/superr-kitchen/tools/root/bloat_custom must be edited to contain these entries (nano ~/superr-kitchen/tools/root/bloat_custom to edit the file):
Code:
system/app/Facebook_stub*
system/app/MSSkype_stub*
system/app/SecureFolderSetupPage*
system/priv-app/OneDrive_Samsung_v2*
system/priv-app/SecureFolder*
system/priv-app/SamsungPass_1.1*
system/priv-app/Excel_SamsungStub*
system/priv-app/PowerPoint_SamsungStub*
system/priv-app/Word_SamsungStub*
system/container*
- Remove Samsung Knox
9) You can make external edits by placing files in ~/superr-kitchen/superr_STOCK/system, or do whatever you want with the APKs
10) Let's start building!
If you left the window, all you have to do is do:
Code:
./superr
8
7
1
This will get you to the ROM zip building screen.
If the kitchen asks if you would like to convert the updater-script to an updater-binary, do it. Now give it some time to build. Usually my computer takes 2-3 minutes.
11) Finally, you can decide whether you want to sign the ZIP or not. Personally, I do not sign my ZIPs.
If you decide to skip signing, you're done! Just type "n" on your keyboard and click "q" to quit the kitchen. Your new ZIP is located in ~/superr-kitchen/superr_STOCK/STOCK_BASED_ROM.zip
You can either move this to your h5ai server, like I do at http://download.projektsubstratum.com/, or you could use transfer.sh here:
Code:
curl --upload-file ./STOCK_BASED_ROM.zip https://transfer.sh/STOCK_BASED_ROM.zip
You could also move it to AndroidFileHost using FTP, if you have a developer account.
This may take a while for the upload to complete, but once it is done, you are ready to flash the four ZIPs:
The ROM
A custom kernel
The CSC utility flasher
Magisk (for SafetyNet)
12) Congratulations, you're done!
Pulling your own CSC files
So you tried to extract the CSC file (cache.img) from the CP tar for Odin but no luck flashing...but you really wanted an up to date version..
Prerequisites:
- Your device MUST be of the Exynos variant, with an available TWRP on the device. If you have a Qualcomm device, close this window now!
- You must have a Linux environment for simg2img
- Sudo account
- Collect and utilize as much wits as you can!
- I will be doing all of this from the command line using SSH, no GUI for this!
1) Download simg2img to your Linux box and build the project
Code:
cd ~/
git clone https://github.com/anestisb/android-simg2img
cd android-simg2img
make
2) After simg2img has been compiled, we will have to use it.
Place your cache.img.ext4, yanked out of the CP.tar.md5 file (renamed to CP.tar) in the same directory of the git cloned repo
If you need a command to extract the .tar file, run:
Code:
tar xf CP.tar
3) Convert the image
Code:
./simg2img cache.img.ext4 cache.raw.img
4) Mount the image
Code:
sudo mkdir /media/csc
sudo mount -t ext4 -o loop cache.raw.img /media/csc
cd /media/csc
5) Copy the prepared flashable CSC zip out of the image
Code:
cp sec_csc.zip ~/
6) Flash the ZIP
7) Boot into the system. If you flashed a multi-CSC, you may need to configure it to be specific to your country.
This will require root, so get yourself into adb shell, then (credits to @jesec):
Code:
adb shell
su
am start com.sec.android.Preconfig/.Preconfig
A window will pop up giving you all the options selectable in your MultiCSC. Clicking and installing any of them will wipe your device, so watch out!
one last reserve post
locking my thread till the upload is finished....
@OP
Great idea bro, thanks a lot.
Nice work! @nicholaschum
Very Good! Thanks!
Sorry, my english is to bad...
Thats mean, if i Flash this Rom and later, when i go back to stock, my knox will be 0x0?
No, KNOX still tripped but with fake 0x0
Good work !! @nicholaschum
Th3PorTuGa said:
No, KNOX still tripped but with fake 0x0
Click to expand...
Click to collapse
Thanks
@nicholaschum
Can I ask possibly a dumb question
Is flashing CSC required?
I mean what happens if you don't flash CSC.
I am currently in AU on Vodafone CSC. I would change it to XSA but if I decided not to or forgot to do it. Would the CSC activate based on what is currently set as my CSC there or is this required so the rom can then load the apps based on location?
Perfect Build Perfect ROM. Installed as per instructions and works like a charm. Thanks for the work.
davjak said:
@nicholaschum
Can I ask possibly a dumb question
Is flashing CSC required?
I mean what happens if you don't flash CSC.
I am currently in AU on Vodafone CSC. I would change it to XSA but if I decided not to or forgot to do it. Would the CSC activate based on what is currently set as my CSC there or is this required so the rom can then load the apps based on location?
Click to expand...
Click to collapse
The CSC is required or else Samsung stock ROMs will not know how to configure your phone. This also I closed LTE-A capabilities, wifi calling and VoLTE functionality. Since this ROM does not contain any CSC you could flash the DBT CSC from the flashing utility which is the default CSC on most ROMs that is Germany debranded.
@nicholaschum - thanks for sharing this ROM. i'm using as a daily driver for my "work device" in combination with the ATT CSC flashed via TK's CSC package. if/when Substratum is available for TW based S8 ROMs, can i assume your ROM will support it? thanks for taking time to read/respond to my question.
Just installed. Silky smooth! Great work op
cortez.i said:
@nicholaschum - thanks for sharing this ROM. i'm using as a daily driver for my "work device" in combination with the ATT CSC flashed via TK's CSC package. if/when Substratum is available for TW based S8 ROMs, can i assume your ROM will support it? thanks for taking time to read/respond to my question.
Click to expand...
Click to collapse
Yes. That is the whole point behind it , keeping it stockish with subs support when it arrives.
I want install it, but i dont what do..
I want sale my phone later and get Note 7.
Is complicate if we cant use Samsung pay when we back to stock.
@nicholaschum Thanks heaps for this, took the leap and followed the instructions. Very simple task! now running XSA CSC with AQEB
Please read the following instructions carefully .
Download Link(only latest):
G980F Version 1.2.0 https://drive.google.com/file/d/1w-5cKNsord7KwvfOAD8hTvxhAS__6mmo/view?usp=sharing
G985F Version 1.1.0 https://drive.google.com/file/d/1kEOkf5Yfs3DGDYjSwph-mINwmOtZ2JUR/view
G981B Planed
G986B Planed
G988B Planed Should be next since I got tons of request.
This custom firmware is based on stock S20(+) G980(5)FXXU4BTH5 . Please make sure you are using G980F/G985F. The G980F is a unblocked 4G version S20, the G985F is a unblocked 4G version S20+.
Depending on the feedbacks and requirements, I might make for other variants in the future. But now, G980F/G985F are the only supported devices.
Disclaimer:
1.This firmware has been tested on G980F real device properly, however, you choose to use at your own risk.
2.Feedbacks are generally welcomed, but please use "search thread" function before ask how to fix xxx problem.
Features:
1.Patched boot.img with Magisk. thanks (https://github.com/topjohnwu/magisk_files/tree/canary)
2.Debloat system.img/product.img, full list below.
3.Deknox system.img/product.img, full list below.
4.Debloat prism.img, full list below.
5.Debloat userdata.img, full list below.
6.Build.prop tweaks in system.img.
7.Replace Samsung default apps(Contacts, Calender, Clock, Calculator, Messages, Dialer, Recorder) to Google apps in system.img.
8.Clear Bootlogo, thanks (https://forum.xda-developers.com/galaxy-s20/development/s20-5g-clean-bootlogo-unlocking-t4067177)
9.Mod optics.img to unlock the advanced features, thanks (https://forum.xda-developers.com/ga...agisk-module-decodedcscfeaturesfiles-t4082445)
10.Mod vbmeta.img to disable Android Verified Boot(proved in screenshot below), thanks (https://forum.xda-developers.com/galaxy-s20/how-to/howto-root-s20-series-upgrade-firmware-t4079353)
11.Disable first boot initial setup wizard, your first boot will enter the system straight away.
12.Debloat media/audio(alarms, notification, ringtones), replace with theme audio from Samsung/Google Pixel/Sony.
13.Youtube No Ad version included. Please disable auto update from Google Play, if you accidentally update youtube, you can always uninstall update from google play, thanks (https://forum.xda-developers.com/android/apps-games/app-youtube-vanced-edition-t3758757)
14.All apps up-to-date(28/9/2020) in this rom.
How to flash?
0. Back up all your data.
1. OEM unlock follow (https://forum.xda-developers.com/galaxy-s20/how-to/howto-root-s20-series-upgrade-firmware-t4079353)
2. Download the zip file flash with Odin.
3. Choose BL, AP and CP. Please note there is no CSC.tar in this zip, since CSC files are included in AP.
4. After flashing, make sure wipe data/factory reset in recovery. (Volume up + power button when boot up)
5. Enjoy!
Changelog:
1.2.0
1.Support G980F
2.Based on BTIB OneUI 2.5 Sep Patch, (1.Improved performance. - Camera 2.The security of your device has been improved.) (https://doc.samsungmobile.com/SM-G980F/DBT/doc.html)
3.Fix Samsung Health compatibility, you can install from Google Play or Samsung store.
4.Replace Samsung Dialer with Google Dialer, now we are Samsung app free except the Samsung Gallery app, since stock camera app can only open gallery.
5.Fix some bugs here and there.
1.1.0
1.Support G980F/G985F.
2.Based on BTH5 OneUI 2.5, all apps update-to-date.
3.Fix some bugs here and there.
4.Debloat list update.
1.0.0
1.Support G980F.
2.All basic features implemented.
FAQ/Known issues:
1.Accessibility -> Visibility enhancements can not be open. This is due to nasty Samsung requires Samsung keyboard's content provider to open this setting. Since Samsung keyboard is considered as bloatware, so you wouldn't be able to open this setting. But in reality, there is nothing need to be set in this setting unless you are colour-blind or having other vision disorder.
2.Please don't mod /system partition. Originally, if you using the official firmware, you can't even edit /system partition. Now you can with edited super.img and root access, but it will cause boot loop. I believe this is a mount issue with logical partition. To save your soft brick phone, the easily way is extract super.img from AP, compress super.img to super.tar, then simply flash super.tar as AP in odin and reboot, no need to wipe data/factory reset.
3.Riru Edxposed is fully compatible, since it is systemless.
4.If you found any app you want to use is in the debloat list, you can try to manually install but please do not ask me how to fix certain apps, such questions won't be answered again and again.
5.Generally speaking, if you found any app does not work but it is not in the debloat list, chances are you forgot wipe data/cache in recovery after flashing this rom.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is a list of bloats been deleted in system.img/product.img.
#Knox
system\app\BBCAgent
system\app\KnoxAttestationAgent
system\app\MDMApp
system\app\SecurityLogAgent
system\app\UniversalMDMClient
system\priv-app\DiagMonAgent
system\priv-app\KLMSAgent
system\priv-app\KnoxCore
system\priv-app\knoxvpnproxyhandler
system\priv-app\knoxanalyticsagent
system\priv-app\KnoxDesktopLauncher
system\priv-app\KnoxKeyChain
system\container
system\etc\permissions\knoxsdk_mdm.xml
system\etc\permissions\knoxsdk_edm.xml
#Skip Setup & Restore
product\priv-app\SetupWizard
product\priv-app\GoogleOneTimeInitializer
product\priv-app\GoogleRestore
#AR
system\app\ARDrawing
system\app\ARZone
system\app\ARCore
system\app\VisionARApps1.1
system\priv-app\AREmoji
system\priv-app\AREmojiEditor
system\priv-app\AvatarEmojiSticker*
system\priv-app\AutoDoodle_Q
system\priv-app\LiveStickers
#Bixby
system\app\*Bixby*
system\app\VisionARApps
system\app\VisionIntelligence*
system\priv-app\Bixby*
system\priv-app\Routines
system\priv-app\*Bixby*
#Wearable
system\app\AntHalService
system\app\ANTPlusPlugins
system\app\ANTPlusTest
system\app\GearManagerStub
system\priv-app\ANTRadioService
#Dex
system\priv-app\DesktopModeUiService
system\priv-app\DeXonPC
system\priv-app\SystemUIDesktop
#Original Youtube
product\app\YouTube
#Samsung Mixed
system\app\ClockPackage
system\app\DailyBoard
system\app\GameOptimizingService
system\app\HoneyBoard
system\app\KidsHome_Installer
system\app\LinkSharing*
system\app\LiveDrawing
system\app\SamsungCalendar
system\app\SamsungDaily
system\app\SamsungPassAutofill*
system\app\SamsungTTS
system\app\SBrowserEdge
system\app\SecFactoryPhoneTest
system\app\SetupWizardLegalProvider
system\app\SmartSwitchAgent
system\app\SmartReminder
system\app\VideoEditorLite_Dream_N
system\app\VideoTrimmer
system\app\Weather_SEP*
system\priv-app\AuthFramework
system\priv-app\GameHome
system\priv-app\GameOptimizingService
system\priv-app\GameTools_Dream
system\priv-app\MateAgent
system\priv-app\PreloadInstaller
system\priv-app\SamsungContacts
system\priv-app\SamsungCloudClient*
system\priv-app\SamsungMessages*
system\priv-app\SamsungPass
system\priv-app\SamsungSocial
system\priv-app\SendHelpMessage
system\priv-app\SmartSwitchAssistant
system\priv-app\SecMyFiles*
system\priv-app\SOAgent
system\priv-app\SPPPushClient
system\priv-app\SVoiceIME
system\priv-app\OneDrive*
system\priv-app\Tips
#Other Mixed
product\app\DuoStub
product\priv-app\AndroidAutoStub
product\priv-app\Turbo
system\app\AutomationTest_FB
system\app\BasicDreams
system\app\BlockchainBasicKit
system\app\CarmodeStub
system\app\DictDiotekForSec
system\app\DRParser
system\app\DuoStub
system\app\EasterEgg
system\app\EasyOneHand3
system\app\ESEServiceAgent
system\app\Facebook_stub
system\app\FBAppManager_NS
system\app\FactoryAirCommandManager
system\app\FactoryCameraFB
system\app\FlipboardBriefing
system\app\HandwritingService
system\app\IceCone
system\app\Netflix_activationCommon
system\app\Netflix_stub
system\app\SafetyInformation
system\app\WebManual
system\app\WifiGuider
system\priv-app\AndroidAutoStub
system\priv-app\ContainerAgent*
system\priv-app\DigitalWellbeing
system\priv-app\EnhancedAttestationAgent
system\priv-app\FBInstaller_NS
system\priv-app\FBServices
system\priv-app\Fmm
system\priv-app\FotaAgent
system\priv-app\HealthService
system\priv-app\LedBackCoverAppHubble
system\priv-app\LedCoverService
system\priv-app\LinkToWindowsService
system\priv-app\ManagedProvisioning
system\priv-app\NSFusedLocation*
system\priv-app\PaymentFramework
system\priv-app\RubinVersion*
system\priv-app\SecureFolder
system\priv-app\Upday
system\priv-app\YourPhone*
system\preload\SmartSwitch
system\etc\recovery-resource.dat
system\recovery-from-boot.p
system\hidden\INTERNAL_SDCARD\Samsung
system\media\audio\ui\Media_preview_Over_the_horizon.ogg
system\tts
Here is a screenshot of bloats in prism.img
Here is a screenshot of bloats in userdata.img
Reserved.
thanks for share。
Sent from my HTC U11+ using XDA Labs
hi mate
can i use this on S20 ULTRA?
patuticci said:
hi mate
can i use this on S20 ULTRA?
Click to expand...
Click to collapse
no
hmy65 said:
@MikeChannon
Can you move this post to Samsung Galaxy S20 / S20+ / S20 Ultra Samsung Galaxy [EXYNOS] S20 / S20+ / S20 Ultra ROMs, Kernels, Recoveries, & Other Development?
I can't post at that area. But I think only I made the public available S20 custom rom right now.
Click to expand...
Click to collapse
hi man,
can you do the same for S20Ultra G988B?
or if you can share what you used to do maybe someone could do it for S20Ultra G988B.
thanks.
stefanz08 said:
hi man,
can you do the same for S20Ultra G988B?
or if you can share what you used to do maybe someone could do it for S20Ultra G988B.
thanks.
Click to expand...
Click to collapse
Hi, I only have S20 G980F. To release a custom firmware, I need to test it on real device to make sure it won't break your phone, because I can't expect everyone to have the ability to save their soft-bricked phone. I saw some people doing this to expect others to test for them, but that is not my current way of doing things, maybe it will change in the future. Thanks for understanding.
hmy65 said:
Hi, I only have S20 G980F. To release a custom firmware, I need to test it on real device to make sure it won't break your phone, because I can't expect everyone to have the ability to save their soft-bricked phone. I saw some people doing this to expect others to test for them, but that is not my current way of doing things, maybe it will change in the future. Thanks for understanding.
Click to expand...
Click to collapse
hi,
total understanding.
but if you can /want to send me a private message how it is doing and i will doing it for my onw. if you want.
and btw, the debloated ROM is rooter right? if you are using Magisk..
stefanz08 said:
hi,
total understanding.
but if you can /want to send me a private message how it is doing and i will doing it for my onw. if you want.
and btw, the debloated ROM is rooter right? if you are using Magisk..
Click to expand...
Click to collapse
It is rooted by patching boot.img with Magisk.
If you asking how to make this ROM, you need to use Linux. 1. extract tar 2. extract lz4 3. convert sparse img to ext img 4. mount and edit that img 5. convert ext img back to sparse img.
Can someone post system.img vendor.img unpacked from super.img
Thank you very much for your efforts, is there anyway to get my led cover working? I've tried downloading the APK with no luck
i understand it right, that i just have to unlock bootloader? So i only have to do stage 1,2 and then i can flash it?
And should i use my HOME_CSC (DBT)?
I just unlocked my boot loader, then booted system to check its unlocked in developer options, then flashed using Odin using only the files in the download,I didn't add my own home CSC,
bazz007 said:
Thank you very much for your efforts, is there anyway to get my led cover working? I've tried downloading the APK with no luck
Click to expand...
Click to collapse
Sorry, I didn't expect anyone use Samsung's offcial led cover. So I deleted that supported apk as a bloat. Next update I will include that apk.
Segelflugpilot said:
i understand it right, that i just have to unlock bootloader? So i only have to do stage 1,2 and then i can flash it?
And should i use my HOME_CSC (DBT)?
Click to expand...
Click to collapse
If you read the instruction carefully, you should notice I mentioned you don't need CSC.
No problem, thx
Yeah i have read that it is in the AP, but just want to be Sure, sorry. Thanks!
if editing system causes bootloop then u probably didnt disable avb.. u cant disable simply by editing vbmetq anymore.. theres more steps to it then that
elliwigy said:
if editing system causes bootloop then u probably didnt disable avb.. u cant disable simply by editing vbmetq anymore.. theres more steps to it then that
Click to expand...
Click to collapse
The way to disable avb is from ((https://forum.xda-developers.com/gal...mware-t4079353)), I mentioned that in the post.
However, I don't think bootloop is caused by avb.
I guess is caused by super.img. Cuz super.img uses logical partition, I use lpunpack/lpmake to unpack/repack that to system.img, product.img, odm.img, vendor.img.
I guess maybe some data lost during these processes causes the entire system.img uneditable, but it won't affect your normal daily use.
Cuz I tried only root with magisk with stock firmware, the entire system partition is read only. But with my repacked super.img, you can edit system partition, but it can cause bootloop.
There is no twrp for firmware packed with super.img, even they don't know how to mount logical partition properly, so I can only do my best lol
Please Help
Hi there, I'm having some issues flashing the three .tar files in Odin - Odin is getting stuck on <ID:0/005> up_param.bin
Please can you assist, thanks.
Andy1122 said:
Hi there, I'm having some issues flashing the three .tar files in Odin - Odin is getting stuck on <ID:0/005> up_param.bin
Please can you assist, thanks.
Click to expand...
Click to collapse
1.Are you using G980F the S20 4G version?
2.Check your devices is OEM unlocked.
3.From other members post, this ROM has no problem with odin at all.
This is the support thread of PixelFlasher
(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).
Note: This thread is meant for issues and problems faced in Google Pixel 6 Pro devices, generic issues that are device agnostic should be discussed in the main thread.
For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.
Troubleshooting:
If you need support or assistance, the best way to get is by generating a support file from within PixelFlasher.
You can hit that big Support button on the main screen, or select it from the Help menu.
The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.
Placeholder
Placeholder
this is an interesting project.
can you add a way to flash all partition/boot slots easily for new users? I think that can resolve a ton of issues. (the flash tool doesn't do this, just reinstalls some of the images like bootloader and raidio).
Alekos said:
this is an interesting project.
can you add a way to flash all partition/boot slots easily for new users? I think that can resolve a ton of issues. (the flash tool doesn't do this, just reinstalls some of the images like bootloader and raidio).
Click to expand...
Click to collapse
There's some discussion ongoing in the main thread of PixelFlasher about advanced options.
Feel free to chime in there, as this point is not specific to Pixel 6 Pro and would help all devices if it is discussed in the main thread.
📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...
forum.xda-developers.com
badabing2003 said:
There's some discussion ongoing in the main thread of PixelFlasher about advanced options.
Feel free to chime in there, as this point is not specific to Pixel 6 Pro and would help all devices if it is discussed in the main thread.
📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...
forum.xda-developers.com
Click to expand...
Click to collapse
Done, check the new release.
New Release:
March 24, 2022 v1.2.0.1-alpha release.
Added Advanced Configuration menu which unlocks advanced features such as:
- Flashing to both slots
- Disabling Verity
- Disabling Verification
- (More features to come)
The UI will now display the chosen Android Platform Tool's version.
Added an option to toggle verbose console output (help troubleshooting, more verbosity to come).
Stability fixes.
New Release: (See full details here on xda or here at github)
April 03, 2022 v2.0.0.0-pre release.
Major refactoring
Added Advanced (Expert) mode UI.
Basic mode keeps UI simple and hides expert features.
Support for setting active slot.
Reboot options (recovery, system, bootloader)
Moved custom ROM options to expert mode.
Added custom flashing to expert mode, can now flash to live (temporary root), or custom flash any image to any partition.
Moved flashing to both slots, disabling verity / verification to expert mode.
Many other improvements, validations and checks.
Updated documentation.
Update:
Version 2.0.1 which includes a hotfix for issue reported here.
Flawless one click update. Thanks. This going to be my default update tool.
Just used it to flash April update on my 6 Pro. Worked like a charm. Thanks.
Also used this to get to April from February and it was one of the simplest things I've ever had to do. Excellent work on this.
It keeps saying magisk is not on my phone, but it is, and it's not hidden.
According to the logs it thinks my phone is not rooted, but it is.
Edit: Followed the instructions and it updated perfectly though, just weird it thinks my phone is not rooted. Awesome app my friend, will be using this as long as it works!
Zach Alt said:
It keeps saying magisk is not on my phone, but it is, and it's not hidden.
According to the logs it thinks my phone is not rooted, but it is.
Edit: Followed the instructions and it updated perfectly though, just weird it thinks my phone is not rooted. Awesome app my friend, will be using this as long as it works!
Click to expand...
Click to collapse
Thanks for bringing this up, I'll add it to the guide,
Shell would need root permission for it to be able to do detect and use magisk.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
badabing2003 said:
Thanks for bringing this up, I'll add it to the guide,
Shell would need root permission for it to be able to do detect and use magisk.
View attachment 5581317
Click to expand...
Click to collapse
Awesome, I'll enable it for next month's update. Again, thanks for this software, it's awesome.
I toggled root access for shell and now my phone shows as rooted in Pixel Flasher.
New Release:
April 06, 2022 v2.1.0 release
Setup dedicated profile directory.
Put logs in the profile directory and maintain log history.
Plumbing for Linux support (just the flashing part is left to do).
Plumbing for new workflow.
Bugfix to handle name conflict in ROM filename.
Various minor improvements.
Update documentation.
Forgot to mention this but I was running this last night and did a dry run before the real thing, it progressed but my cable was apparently faulty so it lost connection mid way (good thing I did dry run and thank you for having it). Anyway, when it lost connection it caused the app to lock up. I closed it in task manager but the files were stuck in use and I had to find and kill the processes still open to free them up before I could start again.
Suggestion: add a check for and close of any existing processes related to the pixel flasher program if it gets reopened to avoid things being stuck in use. I work in IT so I was fine poking around to kill those processes but not everyone will be.
If you can't, maybe just add the list of processes to the OP so people can kill them on their own.
wgrant said:
Forgot to mention this but I was running this last night and did a dry run before the real thing, it progressed but my cable was apparently faulty so it lost connection mid way (good thing I did dry run and thank you for having it). Anyway, when it lost connection it caused the app to lock up. I closed it in task manager but the files were stuck in use and I had to find and kill the processes still open to free them up before I could start again.
Suggestion: add a check for and close of any existing processes related to the pixel flasher program if it gets reopened to avoid things being stuck in use. I work in IT so I was fine poking around to kill those processes but not everyone will be.
If you can't, maybe just add the list of processes to the OP so people can kill them on their own.
Click to expand...
Click to collapse
The reason that happened is because PixelFlasher is running flash-all equivalent script, which has fastboot commands in it, most fastboot commands (aside from informational ones) are blocking, i.e. it waits for device.
Because your cable was faulty and your device was not appearing connected, it got blocked waiting for it.
It's a good idea to display a message and the PID of the spawned process, the user can kill it if they wish.
I really don't want to intervene with that spawned process as it is the one flashing your phone, any glitch in there and it could mess up the phone.
badabing2003 said:
The reason that happened is because PixelFlasher is running flash-all equivalent script, which has fastboot commands in it, most fastboot commands (aside from informational ones) are blocking, i.e. it waits for device.
Because your cable was faulty and your device was not appearing connected, it got blocked waiting for it.
It's a good idea to display a message and the PID of the spawned process, the user can kill it if they wish.
I really don't want to intervene with that spawned process as it is the one flashing your phone, any glitch in there and it could mess up the phone.
Click to expand...
Click to collapse
That's a good idea as well, better to not force a closure of the process and instead inform then give the user the information necessary to close it themselves. It was definitely the fastboot process that was holding the files. Once I killed that it was fine for me to proceed. Providing a pop up with the PID or even just the process name (unless the PID is always the same) and instructions in that pop up would certainly help someone get out of a jam without needing to reboot the computer.
I've done some stuff like this project with batch but this blows that completely out of the water. Excellent work, you should be proud of what you've given to the community.
can I also root my Pixel with that?