EDIT: For further updates and newer versions, please see my consolidated M2 8.0 Marshmallow ROM thread.
Here is the Huawei Official update ROM for the M2-802L, with Android 6.0 Marshmallow with EMUI 4.0. The download link points to the official Huawei server at hicloud.com.
Version: M2-802LC229B207CUSTC229D006
Download link: http://update.hicloud.com:8180/TDS/data/files/p4/s10/G506/g0/v67917/f1/full/update.zip
Download link text:
Code:
http://update.hicloud.com:8180/TDS/data/files/p4/s10/G506/g0/v67917/f1/full/update.zip
I installed this ROM over my old B005 ROM (Android 5.1.1 Lollipop + EMUI 3.1) and it installed fine, rebooted, created a new Dalvik cache and then updated the Google framework. Calls (I'm on AT&T in USA) and texts seem to work fine after the update. All my apps (and most of my settings) were preserved after the update. My AT&T MMS APN was erased, but I have another post on XDA for that. Wifi works too, it connects (as you can see in the screenshot) to the Wifi access points to which I had authenticated on my old ROM, before the update.
I have attached a screenshot of the ROM on my phone.
{
"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"
}
Installation Instructions:
If you are currently rooted and/or have a custom recovery installed, you will need to go back to the Huawei official recovery to install this update. You can do this by following the instructions in my previous post here.
Download the ROM update zip from the above link. Extract the contents of the zip file in the link after it has finished downloading. The contents are as follows:
Code:
update.zip contains
├── META-INF
│** ├── blacklist.conf
│** ├── CERT.RSA
│** ├── CERT.SF
│** ├── com
│** │** ├── android
│** │** │** └── otacert
│** │** └── google
│** │** └── android
│** │** ├── update-binary
│** │** └── updater-script
│** └── MANIFEST.MF
└── UPDATE.APP
5 directories, 8 files
Create a folder called dload on your SD Card. You can create it on either the internal or the external SD, it doesn't matter.
Copy the entire contents (the full META-INF directory as well as UPDATE.APP) of the unzipped download package into the dload folder on your SD Card, which you created above.
Go to your phone's "Settings". There, navigate to "Updater"->"Menu"->"Local Update", select the displayed option, and allow it to install. Your phone will boot into the original OEM recovery and install the ROM, after which it should (hopefully) boot into the new ROM.
It should then connect to the Google Play Store and update the Google framework. All your settings, apps etc should still be preserved - mine were.
Rooting instructions using phhusson's Superuser:
First install TWRP as your recovery. If in doubt, use the excellent Huawei Mediapad M2 rooting guide found on these forums. Note that if following this guide, you may want to make sure that your ROM is Android 5.1.1 (Lollipop), because Android 6.0 (Marshmallow) does not have the Unlock OEM selection in developer option (thanks for the tip, @Dvalin21).
Then grab the latest superuser.zip (from phhusson's Superuser project which is an actively-maintained fork of Koush's open-source Superuser project), and install it via the TWRP recovery.
Finally, get the "phh superuser" app from the Google Play store.
At this point, when I typed "su" in my terminal app, I got the usual permission dialog, and upon granting permissions, I was dropped into a root shell:
Have fun!
I found this ROM after seeing some posts on Russian forums - Google translate was my friend :silly:
Fantastic! I'll give this a go tonight.
PHH Superuser works to root the ROM
wmoore said:
Fantastic! I'll give this a go tonight.
Click to expand...
Click to collapse
Good luck!
Note: For some reason, running the latest stable SuperSU (SuperSU-v2.79-201612051815.zip from the main SuperSU thread) to root this ROM failed and the phone went into a bootloop. Since I had reflashed TWRP back on this ROM, I was able to get back into the bootloader (fastboot), reflash the stock recovery from B207 (which I had been wise enough to extract from the UPDATE.APP), and reflash the ROM again (kept my apps and settings). Trying to install SuperSU again now...
EDIT: There definitely seems to be a problem with SuperSU 2.79 as well as the updated beta 2.79-SR2. I've reported it on the SuperSU forums. Going to try rooting this ROM with an older version of SuperSU - I have 2.78 from when I rooted the older ROM (Android 5.1.1 Lollipop). Eyes, fingers and other crossable body parts crossed
EDIT 2: No joy on SuperSU 2.78 either. Given that Chainfire has relinquished control of SuperSU to some other entities, maybe this is not a bad thing. I am now trying phhusson's fork of Koush's open-source superuser.
EDIT 3: phhusson's Superuser worked!! To install it,
First install TWRP as your recovery,
Then grab and install the latest superuser.zip via the TWRP recovery.
Finally, get the "phh superuser" app from the Google Play store.
At this point, when I typed "su" in my terminal app, I got the usual permission dialog, and upon granting permissions, I was dropped into a root shell:
It worked! I'm finally on Marshmallow on my M2!! I haven't seen anything weird happening yet but I'll keep you posted.
Worked for me too!!! Thanks!
wmoore said:
It worked! I'm finally on Marshmallow on my M2!! I haven't seen anything weird happening yet but I'll keep you posted.
Click to expand...
Click to collapse
murphinator said:
Worked for me too!!! Thanks!
Click to expand...
Click to collapse
You're most welcome, you guys. Happy it worked for you :good: It's too bad that Huawei hasn't officially released Marshmallow to us, forcing us to take matters into our own hands...
When I get a little bit of free time here and there, I'll see if I can work on kanging this ROM - no promises though, since first I have a lot to learn :silly:
Can I use other country's firmware. But same model? (801L)
Caelestiel said:
Can I use other country's firmware. But same model? (801L)
Click to expand...
Click to collapse
Yes, it shouldn't be a problem. I was running the B005 build from China in USA. I had also installed the SYSTEM.img from the German ROM for a different model - the 801L - on my 802-L, and it worked.
One more thing, Can I use TWRP System and Data backup from B007 if I'm using Marshmallow?
Caelestiel said:
One more thing, Can I use TWRP System and Data backup from B007 if I'm using Marshmallow?
Click to expand...
Click to collapse
No, I don't think this will be possible.
The system image is actually the main ROM image/partition. If you overwrite system with your TWRP backup, you will actually be back in your old Lollipop B007 image.
The old data partition may or may not work, but I wouldn't take a chance - most cases of ROM misbehavior in custom ROMs are caused by people not properly clearing their data partition; the same principle may apply here.
If you asked this question because you want to keep all your existing apps and data, they should (most of them) survive the upgrade process, but make sure that you do not manually format/clear/factory-erase your main partitions in TWRP before you upgrade.
I am in Finland and myself have M2-801L. Does this update also in it.
Issue Resolved. idk how to delete comment :v
Eagle-no1 said:
I am in Finland and myself have M2-801L. Does this update also in it.
Click to expand...
Click to collapse
This ROM is specifically for the 802L. It may work on your 801L (as I mentioned in one of my other posts I have successfully flashed and used the 801L System image on my 802L), but be aware that since the two models support different cell frequencies, the radio image in this ROM may not work for you.
Later today, after I get back home, I will see if I can find a Marshmallow stock ROM for the 801L
Caelestiel said:
Issue Resolved. idk how to delete comment :v
Click to expand...
Click to collapse
No problem, don't worry about the comment. I missed seeing the original comment where you mentioned an issue, so just out of curiosity may I know what the issue was?
beast.in.black said:
This ROM is specifically for the 802L. It may work on your 801L (as I mentioned in one of my other posts I have successfully flashed and used the 801L System image on my 802L), but be aware that since the two models support different cell frequencies, the radio image in this ROM may not work for you.
Later today, after I get back home, I will see if I can find a Marshmallow stock ROM for the 801L
Click to expand...
Click to collapse
Alright. Great, I can not find this version of the OEM unlock possibility at all.
https://forum.xda-developers.com/showpost.php?p=70375484&postcount=39
beast.in.black said:
No problem, don't worry about the comment. I missed seeing the original comment where you mentioned an issue, so just out of curiosity may I know what the issue was?
Click to expand...
Click to collapse
I can't flash TWRP because of fastboot error and can't root because I have no recovery.
My bootloader was unlocked before using free and weird software, (nothing that has been said here so I can't remember how did I unlocked it) My warranty ended last Oct. 2016 so I decided to get unlock code from huawei. And reunlocked using that code.
The error was gone and I was able to flash recovery
---------- Post added at 12:53 PM ---------- Previous post was at 12:43 PM ----------
https://forum.xda-developers.com/mediapad-m2/development/rom-stock-rooted-xposed-t3519031
I installed this to my 801L.
But in the settings, it became 803L...
Caelestiel said:
I can't flash TWRP because of fastboot error and can't root because I have no recovery.
My bootloader was unlocked before using free and weird software, (nothing that has been said here so I can't remember how did I unlocked it) My warranty ended last Oct. 2016 so I decided to get unlock code from huawei. And reunlocked using that code.
The error was gone and I was able to flash recovery
Click to expand...
Click to collapse
Oh, great to hear that you were able to get past the error!
Caelestiel said:
---------- Post added at 12:53 PM ---------- Previous post was at 12:43 PM ----------https://forum.xda-developers.com/mediapad-m2/development/rom-stock-rooted-xposed-t3519031
I installed this to my 801L.
But in the settings, it became 803L...
Click to expand...
Click to collapse
Yes, the build.prop in that ROM seems to be the 803L build.prop. However, that ROM doesn't seem to overwrite the radio partition, so it should still be OK. When I had flashed the 801L system image on my 802L, my phone model showed "801L" in settings but I was still able to use all phone functions of the 802L frequencies (AT&T US data, MMS, calls).
beast.in.black said:
Oh, great to hear that you were able to get past the error!
Yes, the build.prop in that ROM seems to be the 803L build.prop. However, that ROM doesn't seem to overwrite the radio partition, so it should still be OK. When I had flashed the 801L system image on my 802L, my phone model showed "801L" in settings but I was still able to use all phone functions of the 802L frequencies (AT&T US data, MMS, calls).
Click to expand...
Click to collapse
But there's something bothering me, something suddenly pops up like "Unfortunately blahblah.apk has stopped" or something like that. I flashed it properly tho. Waiting for the creator's response.
Caelestiel said:
But there's something bothering me, something suddenly pops up like "Unfortunately blahblah.apk has stopped" or something like that. I flashed it properly tho. Waiting for the creator's response.
Click to expand...
Click to collapse
Hmmm...the way I see it, there are two separate and orthogonal variables at play here, any one of which might be responsible for the issue:
The ROM is a customized ROM.
It is originally for a mediapad model (803L) which is different from yours (801L).
Anyway, I have posted a thread with all the latest stock Marshmallow ROMs I was able to find for the different Mediapad M2 8.0 models - maybe the 801L ROM mentioned there can be your rescue ROM when you have a SHTF situation :fingers-crossed:
when coming android 6 for 801LV100R001c199b005 (middle easte) ?
when coming android 6 for 801LV100R001c199b005 (middle easte) ?
Related
{
"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"
}
It has LINUX/UNIX and MAC support!
Because there is another tool for Android called Android Multi Tools, I renamed this one to Lx Multi Tool, future releases will go under this name.
Features:
Fastboot- Unlock/Lock Bootloader- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.2 Included- Flash any partition (Flashing submenu)- Flash full Stock images (you can choose and add images)- Erase partitions (you can choose which of the partitions)- Reboot (you can choose again...)Adb- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.56 (Systemless!) included- Backup (you can choose the name and place for your backup)- Restore (you can choose your backup)- Version (it just shows the version of your adb binaries) - platform-tools 23.0.1 included- Logs (DMESG and Logcat)- Screenshots (you can directly take screenshots to your PC with no Root)- Reboot (lots of choices)Others- Refresh and delete files/folders from menus (Right-click or key F5 and Del)- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)- Tab key support for easier keyboard navigation- Tool-tips for all buttons- Check for updates- Link to xda-thread (here) Download links:
Windows x86|x64 - Linux x64 - MAC x64All released versions can be found here.
(The latest versions are always on the bottom.)[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.
Known bugs/limitations:
- For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)- For the return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)
Changelog:
Check the changelog for each release here. Tutorials/FAQ:
Q: How do I get in bootloader/fastboot mode?Turn off the phone and turn it on by using Volume down + Power key.Q: How do I check for updates on your tool?Follow the instructions on the screen below.
Q: Where can I find the device driver to install it for windows?Click here, download the driver, and run the setup.Q: How do I root my stock phone?- Unlock bootloader.- Flash recovery.- Use SuperSU 2.62 systemless or higher from here.(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)Q: I get an error "Cannot open file" on MAC, what should I do?Open the terminal, go to your application path and paste this command:
Code:
chmod +x LxMultiTool.app/contents/macos/*
Q: What do I need to do in order to be in Fastboot or in ADB mode.Fastboot mode will be detected only while being in bootloader.ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.Refresh button needs to be used in order to check for what mode you are in.Q: Are there any other software that I need to install in order to run this tool?On Windows and MAC everything is bundled, so nothing needs to be installed, just run.On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.If it's not enough, use ldd LxMultiTool in the terminal to find out what you're missing from your environment.Q: I have a yellow/orange/red text screen during boot, what's that?When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.Q: Hey, my device is not detected, why?On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.Also, make sure you click the connection Refresh button after connecting the device to your PC.Q: What do I need to do in order to install a custom ROM?1. Unlock Bootloader.2. Flash a custom recovery of your choice.3. Flash an insecure kernel (boot).4. Flash custom ROM with no problems via recovery.All those things are found and can be done via this tool.Q: Hi, I just downloaded this tool, how do i use it?First, extract the folder somewhere.After that, run LxMultiTool.exe on windows by double-clicking it, LxMultiTool on Linux, and the same on mac.Q: Do I need android-sdk installed or something else?No! This tool uses its own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyway.This tool is fully portable and stand-alone.Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:- Enable Developer options- Enable USB Debugging- Look for the ‘OEM Unlock’ Option and toggle it.Q: How do I use the return to stock feature?First, download the latest package from here, then extract the contents (there is an archive in the archive) until you get to a folder like angler-mda89dthat contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.
Q: How do I enable Developer options?- Launch the Settings- Scroll Down and Tap on About Phone(or About Device)- Locate the Build Number Section- Tap on the Build Number Option 7 Times- Go Back to the Main Settings Page- Scroll Down and Tap on Developer OptionsQ: Hi, I just bought a phone what should I do now?Well, you firstly need to unlock your bootloader...Q: What is logcat?Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.It is usually used for debugging and entertainment(?).When you report an error/bug to somebody, it will be a blessing to provide a logcat (log file)!Q: What is a Custom Recovery and why do I need one?A custom recovery is that thingy that lets you flash .zip files, use your logic, and you will get it why you need one.Q: There are other guides/tutorials out there. Should I check them instead of this?If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...Q: What is sideload and how do I use it?Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.Please note that you need to be in sideload mode on your recovery before doing this.To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload
Sources:
The official and original repository can be found here.
Bug reports/feature requests:
If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on GitHub for more traceability here.
Licensing:
Please note that this tool is open source and released under the GPL v3 license, which can be read here.Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.
Tech and stuff:
Some additional marketing for stuff used in this toolQt - An awesome cross-platform IDEVmware - For letting me test this tool on all platforms (Linux and MAC).Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)UnixUtils - For the sed utility for Windows.AndroidFileHost - For the awesome file-management platform for developers.
Donations:
Even though this tool is provided free of charge, fully open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.This section will also include the hall of fame for donors and on the github repository.Special thanks for donations:- @john7760
Disclaimer:
I will not be responsible for smashed screens, bricked phones, or any other things that you can accuse me of, I've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A, or useless posts, please read the FAQ section upside, it's like a Mini-Guide!
XDA:DevDB Information
Lx Multi Tool, Tool/Utility for the Huawei Nexus 6P
Contributors
Lexmazter
Source Code: https://github.com/lexmazter/LxMultiTool
Version Information
Status: Stable
Created 2016-01-01
Last Updated 2016-01-16
Already tool kit?
*Damn, nexus dev support is amazing
I feel so bad for buying galaxy s6, 0 aosp roms, Mod edit: Profanity removed dev support and all because of stupid exynos ;C
You da man! Can't wait for my phone to show up.
That was quick!! Waiting for this phone to be launched in India.
It works great thanks.I mean Tool
Wow. Can't wait to get my 6P and use this
Sent from my A0001 using Tapatalk
Add to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P
Haven't even received my device yet, just wanted to say Thanks in advance!
Showing so much promise
I can't say more for this kind of support.
Great to see this already in the forum. Waiting on my 6P 128 Gig MONSTER.
wilbarger said:
Great to see this already in the forum. Waiting on my 6P 128 Gig MONSTER.
Click to expand...
Click to collapse
Got the 128gb monster on the way myself.
Thanks for this. Making it easy for everyone is a great thing I'm so excited to get back on a nexus
Thanks for this tool, I need to start from scratch because I don't have a Nexus since Nexus One
Thanks for this. Will be a first time user for the nexus generation. Just ordered the 6P so will definitely be doing this .
Great seeing this already. Coming from an S4 to the 64GB 6P. Will it be possible to relock the bootloader after installing a custom recovery or is the stock recovery required for the lock?
Sent from my SPH-L720 using Tapatalk
C4PO said:
Great seeing this already. Coming from an S4 to the 64GB 6P. Will it be possible to relock the bootloader after installing a custom recovery or is the stock recovery required for the lock?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
AFAIK, locking bootloader has nothing to do with the recovery, but then again, I never locked a bootloader...
Pretty sure you'd need to flash stock recovery. It won't hurt anything to try it without stock recovery, but if it doesn't work then you'll know for sure why.
I'm not planning to mess around with it too much until a stock system file is available. I need a Plan B. Lol
Doesn't run for me. (Mac User)
Heres the terminal error
sh [Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh
[Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh: line 3: [Path to location]/6PMultiTool.v0.2/simple_curses.sh: No such file or directory
There doesn't seem to be a "simple_curses.sh" file in the tool directory that I can find. Hope you can get it figured out! Thanks for the awesome tool as well!
ryman222 said:
Doesn't run for me. (Mac User)
Heres the terminal error
sh [Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh
[Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh: line 3: [Path to location]/6PMultiTool.v0.2/simple_curses.sh: No such file or directory
There doesn't seem to be a "simple_curses.sh" file in the tool directory that I can find. Hope you can get it figured out! Thanks for the awesome tool as well!
Click to expand...
Click to collapse
Unfortunately I never got the chance to test the MAC version, finally I have a tester
From what I can see at a first look is that this simple_curses.sh is some leftover from when I experimented with some UI tricks for bash to try to simulate the looks of the batch version..
Can you please check this temporary version from here -> 6PMultiTool.v0.2.1.zip
{
"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"
}
You flash this MOD at your own risk,
i take no responsibility for any mishaps.
Subscribe to update notifications and general chat by clicking the button below
PIXEL TELEGRAM CHANNEL
WETA is a rom for Music geeks like me, though because we are still waiting on TWRP to become available i'd thought i'd make these MODs to flash in the meantime.
How to install...
This method is redundant from V2.0 forward
1. Make sure you are on Stock firmware and have rooted device
2. Download mod zip
3. Install this app "Root Browser"
4. Extract the zip (click and hold, select extract) using Root Browser directly into Download folder. (you should have /sdcard/Download/(zip name) as folder with files in it)
5. Go into Download/(zip name) folder and select script for desired Emoji.
6. Tick "Execute script as root"
7. Then select the Execute button
8. It will say "Executing script"
9. Once complete you should have a popup box with no errrors.
10. Device will reboot automatically
V1
includes emoji from…
emoji-one (open source emoji)
IOS 10
Mozilla
Twitter
Windows 10
Facebook
LG G5
V2.0
This is now an Aroma installer, use TWRP to flash...
First Aroma version Installer
Added back to stock option
Added Samsung
updated ios to 10.2
updated Tweemoji to 2.2.1
updated emojione to 2.2.4
MOD Download Page
If you like my work, please consider buying this poor guy a craft beer for his efforts
--->
I don't get it. What does this mod do? I did Everything but nothing changed and it didn't Reboot Automaticly.
Gesendet von meinem Pixel XL mit Tapatalk
Mentalmuso said:
You flash this MOD at your own risk,
i take no responsibility for any mishaps.
Subscribe to update notifications and general chat by clicking the button below
PIXEL TELEGRAM CHANNEL
WETA is a rom for Music geeks like me, though because we are still waiting on TWRP to become available i'd thought i'd make these MODs to flash in the meantime.
How to install...
1. Make sure you are on Stock firmware and have rooted device
2. Download mod zip
3. Install this app "Root Browser"
4. Extract the zip (click and hold, select extract) using Root Browser directly into Download folder. (you should have /sdcard/Download/(zip name) as folder with files in it)
5. Go into Download/(zip name) folder and select script for desired Emoji.
6. Tick "Execute script as root"
7. Then select the Execute button
8. It will say "Executing script"
9. Once complete you should have a popup box with no errrors.
10. Device will reboot automatically
V1
includes emoji from…
emoji-one (open source emoji)
IOS 10
Mozilla
Twitter
Windows 10
Facebook
LG G5
MOD Download Page
If you like my work, please consider buying this poor guy a craft beer for his efforts
�� --->
Click to expand...
Click to collapse
Thanks for this, the iOS10 emojis work great. Can we only have one set installed at a time or is it possible to install multiple emoji packs?
airmaxx23 said:
Thanks for this, the iOS10 emojis work great. Can we only have one set installed at a time or is it possible to install multiple emoji packs?
Click to expand...
Click to collapse
Looking at the script and files, it looks to be the same font name, so no. It would take some trickery to have multiple emoji sets available on the same system.
raynan said:
Looking at the script and files, it looks to be the same font name, so no. It would take some trickery to have multiple emoji sets available on the same system.
Click to expand...
Click to collapse
Thanks, now I'm trying to find some pics showing the emojis from each pack.
No way! Thank You been looking for this everywhere.
EDIT: Any chance we can get iOS9 Emojis as well?
can we get a screenshot of what they each look like.?
I could but I'm not going to haha
Here though. Look through this
http://emojipedia.org
? --->
Edit
Is there a return to stock script for the emojis?
airmaxx23 said:
Is there a return to stock script for the emojis?
Click to expand...
Click to collapse
No. But thanks I'll make one. Didn't even think about these
WETA stock emoji installer
Takes you back to stock emoji.
MOD Download Page
--->
I tried running your script and it did not work. Well, it appeared to have worked, rebooted, but all the emoji's are the same (not iOS 10).
I'm contemplating on manually doing it, as I've replaced system files in the past.
Edit: Just moved the file manually and changed the permissions to RW-R-R and it worked like a charm. I don't think your script is moving the file correctly ?
Anyways, thanks for the font packs!
xocomaox said:
I tried running your script and it did not work. Well, it appeared to have worked, rebooted, but all the emoji's are the same (not iOS 10).
I'm contemplating on manually doing it, as I've replaced system files in the past.
Edit: Just moved the file manually and changed the permissions to RW-R-R and it worked like a charm. I don't think your script is moving the file correctly ?
Anyways, thanks for the font packs!
Click to expand...
Click to collapse
They've all worked fine for me.
xocomaox said:
I tried running your script and it did not work. Well, it appeared to have worked, rebooted, but all the emoji's are the same (not iOS 10).
I'm contemplating on manually doing it, as I've replaced system files in the past.
Edit: Just moved the file manually and changed the permissions to RW-R-R and it worked like a charm. I don't think your script is moving the file correctly ?
Anyways, thanks for the font packs!
Click to expand...
Click to collapse
You didn't follow the steps is all. You probably didn't use the app stated in op, or you didn't have the zip in your Download folder
Mentalmuso said:
You didn't follow the steps is all. You probably didn't use the app stated in op, or you didn't have the zip in your Download folder
Click to expand...
Click to collapse
I did both of these things, but okay.
I re-read your instructions and it appears that you're assuming there will be a folder with the name of the zip file under Downloads with the scripts in it. I extracted the zip contents into downloads and it put the scripts in downloads, and the sys folder in there as well. Perhaps this is where the confusion is? I see your script has the following path: /sdcard/Download/WETA_Pixel_emoji/sys/ios10/fonts/, where the bolded folder is the difference. When I extract your zip to the Downloads folder, it doesn't create this folder automatically (perhaps your version of Root Browser is set to do this).
I'm sure this will help anyone in a similar situation.
xocomaox said:
I did both of these things, but okay.
I re-read your instructions and it appears that you're assuming there will be a folder with the name of the zip file under Downloads with the scripts in it. I extracted the zip contents into downloads and it put the scripts in downloads, and the sys folder in there as well. Perhaps this is where the confusion is? I see your script has the following path: /sdcard/Download/WETA_Pixel_emoji/sys/ios10/fonts/, where the bolded folder is the difference. When I extract your zip to the Downloads folder, it doesn't create this folder automatically (perhaps your version of Root Browser is set to do this).
I'm sure this will help anyone in a similar situation.
Click to expand...
Click to collapse
Root browser is not root explorer. Root browser extracts to a folder of the same name as the zip. This is why I link the app also. All I'm trying to do is make it as simple as possible for people who don't even know what a script is. If root browser is not extracting to that named folder then I'm sorry I got it wrong. I don't want people misled by any of this. Please confirm what root app you are using
Use root browser peoples just like the OP stated.
Is this just http://forum.xda-developers.com/general/general/mod-ios10-profession-emojis-t3487038 but in an "installable" version? If so, would be good to credit the source.
Juzman said:
Is this just http://forum.xda-developers.com/general/general/mod-ios10-profession-emojis-t3487038 but in an "installable" version? If so, would be good to credit the source.
Click to expand...
Click to collapse
Um no. I got my font file from elsewhere, in fact ive had it since before his release date.
--->
{
"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.
Didn't see a thread, but I just checked the Members app and saw the OneUI 3.0 beta registration was finally on there for G975U1. Registered and am downloading now.
{
"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"
}
Links:
BETA 1 - Android 10 ETJ3 -> ZTKI Update.zip link ( courtesy of @GreenDinoXD )
BETA 2 - ZTKI -> ZTL9 Update.zip link ( courtesy of @GreenDinoXD )
Rename .bin file to update.zip
Follow installation instructions from this thread:
Kapitein187 said:
ADB-method:
1. Download SDK platform tools from here https://developer.android.com/studio/releases/platform-tools
2. Extract them on your desktop.
3. Inside the extracted folder put the update.zip
4. Inside this folder, holding left shift, right click the mouse and select "open command prompt here". The command prompt will open.
5. Shutdown the phone.
6. Holding power+volume up buttons, enter into recovery mode.
7. Select "update via ADB". (you scroll down using the volume buttons and select using the power button).
8. Connect the phone to the PC using original samsung USB cable.
9. In the command prompt run the following command:
./adb devices
10. Wait to see that the daemon has started and that your device is found.
11. If you device is found, run the following command:
./adb sideload update.zip
The update process will start. You will see a percentage counting. First it will verify, then patch etc. Do not move the cable, disconnect the phone or power off the PC.
Once the process is completed (it takes some time) the phone will boot itself, update the apps and log into your home screen.
SD-card method:
1. Download the bin file and rename it to update.zip (by going to file options in win10 you can select to view the file extensions. This makes the renaming process much easier and safer, and avoids renaming the file to update.zip.zip)
2. Copy it to the root directory of your SDcard.
3. Shut down your phone.
4. Hold simultaneously Power+volume up buttons to get into stock recovery.
5. Using your volume keys navigate to "update via SdCard" and press power button to select it.
6. Again using volume keys navigate to the file "update.zip" and press power button to select it.
7. Update will start. Leave it till it completes. It will take some time.
8. Phone will reboot by itself and load android.
Click to expand...
Click to collapse
How to capture the update.zip file to share with other people:
1. Download HTTP canary app from playstore
2. Open HTTP Canary app
3. Start the update by pressing "download" and don't pause it
4. Go back to canary app and start it and it will grab the link for you
rikipy said:
How to capture the update.zip file to share with other people:
1. Download HTTP canary app from playstore
2. Open HTTP Canary app
3. Start the update by pressing "download" and don't pause it
4. Go back to canary app and start it and it will grab the link for you
Click to expand...
Click to collapse
Is it still possible to grab the link after it's finished downloading? It's finished but I haven't installed it yet.
jeston said:
Is it still possible to grab the link after it's finished downloading? It's finished but I haven't installed it yet.
Click to expand...
Click to collapse
Just redownload it.
Hello, please post update.zip file
please do you have the update.zip file , please share the link
is it for snapdragon?
Good day, anyone was able to download the zip file? My CSC is XXA. I tried to do the trick of taken out my sim card and restarting my phone to see the notice come up in the members app but cannot enrol because I do not have a us simcard in my phone.
Ackeem.Salmon said:
Good day, anyone was able to download the zip file? My CSC is XXA. I tried to do the trick of taken out my sim card and restarting my phone to see the notice come up in the members app but cannot enrol because I do not have a us simcard in my phone.
Click to expand...
Click to collapse
That's not how this works, unfortunately.
Some people END UP with Snapdragons outside US, i have a friend who i recently found out was on PIE.
It's logical that SIM Region and Actual Location match up.
The only way we can alleviate this is by finding out a way to spoof requests to Samsung's Servers (alla Frija) for OTA's with mocked locations, but i've never seen something like that.
That said, Snapdragon Beta testers seem to be as helpful as Samsung is to them, so far none of them have shared the package with us.
PlutoDelic said:
That's not how this works, unfortunately.
Some people END UP with Snapdragons outside US, i have a friend who i recently found out was on PIE.
It's logical that SIM Region and Actual Location match up.
The only way we can alleviate this is by finding out a way to spoof requests to Samsung's Servers (alla Frija) for OTA's with mocked locations, but i've never seen something like that.
That said, Snapdragon Beta testers seem to be as helpful as Samsung is to them, so far none of them have shared the package with us.
Click to expand...
Click to collapse
okay please if you hear any please let me know .. and thanks so much am grateful
I tried a manual Frija fetch with OP's information, just for the sake of it, and got some interesting results.
This is the latest XAA Android 10 Build in Auto shows:
SM-G975U1_1_20201020093603_5lxag3hh7k_fac.zip.enc4
So build date is 20th October 2020. And this is ETJ3 (November).
Manually looking up for XAA with:
PDA: G975U1UEU4ZTKI
CSC:G975U1OYM4ZTKI
Phone: G975U1UEU4ZTKI
Gives me this:
SM-G975U1_7_20201112155200_rpfk7uveqc_fac.zip.enc4
So, build date is 12th November 2020. Build Date and release dates can differ up to two-three weeks. Weirdly though it reports Android 7.1.1 (which this device never had).
OP (@jeston ) Can you just check if the build date matches with yours in Software Information?
PlutoDelic said:
I tried a manual Frija fetch with OP's information, just for the sake of it, and got some interesting results.
This is the latest XAA Android 10 Build in Auto shows:
SM-G975U1_1_20201020093603_5lxag3hh7k_fac.zip.enc4
So build date is 20th October 2020. And this is ETJ3 (November).
Manually looking up for XAA with:
PDA: G975U1UEU4ZTKI
CSC:G975U1OYM4ZTKI
Phone: G975U1UEU4ZTKI
Gives me this:
SM-G975U1_7_20201112155200_rpfk7uveqc_fac.zip.enc4
So, build date is 12th November 2020. Build Date and release dates can differ up to two-three weeks. Weirdly though it reports Android 7.1.1 (which this device never had).
OP (@jeston ) Can you just check if the build date matches with yours in Software Information?
Click to expand...
Click to collapse
Looks like the build date is November 30...
I can't be the only one in the beta, nobody else has been able to join and grab the update.zip?
jeston said:
Looks like the build date is November 30...
Click to expand...
Click to collapse
That's nice news, why is Frija able to download a November ROM when there isnt one built in that month (As i said, November release was built in October).
I could never do this before with Beta's or Test Firmwares on SamFirm or Frija, why is it suddenly reacting to the exact values of the Beta is a myth to me.
jeston said:
I can't be the only one in the beta, nobody else has been able to join and grab the update.zip?
Click to expand...
Click to collapse
There are quite a few on reddit, but no one sniffed the package. Bummer.
jeston said:
Is it still possible to grab the link after it's finished downloading? It's finished but I haven't installed it yet.
Click to expand...
Click to collapse
yes its still posible and me on insta: Mateuzs_95 so i can help you with the steps:
PlutoDelic said:
That's not how this works, unfortunately.
Some people END UP with Snapdragons outside US, i have a friend who i recently found out was on PIE.
It's logical that SIM Region and Actual Location match up.
The only way we can alleviate this is by finding out a way to spoof requests to Samsung's Servers (alla Frija) for OTA's with mocked locations, but i've never seen something like that.
That said, Snapdragon Beta testers seem to be as helpful as Samsung is to them, so far none of them have shared the package with us.
Click to expand...
Click to collapse
I actually get updates my latest being last month.
PlutoDelic said:
That's nice news, why is Frija able to download a November ROM when there isnt one built in that month (As i said, November release was built in October).
I could never do this before with Beta's or Test Firmwares on SamFirm or Frija, why is it suddenly reacting to the exact values of the Beta is a myth to me.
There are quite a few on reddit, but no one sniffed the package. Bummer.
Click to expand...
Click to collapse
I guess they were quite hasty so nobody thought about grabbing the update
I really hope someone grabs the update and upload the zip. Waiting for 3 months to get a feel of android 11 is just out of it.
Ackeem.Salmon said:
I really hope someone grabs the update and upload the zip. Waiting for 3 months to get a feel of android 11 is just out of it.
Click to expand...
Click to collapse
the guy that created this post can do it right know but i don't know if he want to do it. i can help him but he needs to contact me so i can tell him the steps
BETA 1 FOR G975U1.
Install guide found here I believe. I did not create that guide. I am not responsible for what you do with the file, I just grabbed it cause it seems people needed it.
GreenDinoXD said:
BETA 1 FOR G975U1.
Install guide found here I believe. I did not create that guide. I am not responsible for what you do with the file, I just grabbed it cause it seems people needed it.
Click to expand...
Click to collapse
Can anybody confirm that's the correct update.zip before I include the link in the OP?