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.
Related
[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.
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/SIZE]
{
"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"
}
Xiaomi Mi Max
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
Please keep discussion focused, on questions pertaining to this Device
List of supporters@Vatsal
...
...To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
FAQs for Device Thread link
Please look for a similar [HELP THREAD] when visiting another device forum.
If you would like to create a similar [Help Thread] please Click Here.
CyanogenMod 14.1http://forum.xda-developers.com/mi-max/development/hydrogen-cyanogenmod-14-t3503822
[GUIDE]ROOT/TWRP/MULTIROM/Cm13/RR on Locked Bootloader + Hardbrick Recoveryhttp://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594
Telegram Invite Linkhttps://telegram.me/joinchat/B6at4UAb_dESnykJ_3PB6g
Thread stuck.
Thank you for this
I'm glad that this thread is up. It's quite timely as I had two quick questions.
After around 5 hours with the device, I was able to do the following:
Unlock the bootloader using the official unlocker.
Format System and Userdata Partitions using Fastboot
Flash TWRP using Fastboot
Mount MTP within TWRP
Copy latest Recovery Image (Stable Global) and SuperSU to Internal Storage
Flash latest Recovery Image (Stable Global) using TWRP
Flash SuperSU 2.78 using TWRP
Everything works as I want it to be right now. It was rather hard since the information was very limited and I haven't seen a detailed guide on how to do this.
If I have time, I'll try to do a short guide. I read a lot of posts in other forums that this was not possible without using a custom ROM which was not the case.
Nonetheless, two questions are coming to mind.
How can I update my ROM if a new version comes out without losing root?
Is Xposed available and if so, where do I download it and how do I flash it?
Thanks!
oreo27 said:
I'm glad that this thread is up. It's quite timely as I had two quick questions.
After around 5 hours with the device, I was able to do the following:
Unlock the bootloader using the official unlocker.
Format System and Userdata Partitions using Fastboot
Flash TWRP using Fastboot
Mount MTP within TWRP
Copy latest Recovery Image (Stable Global) and SuperSU to Internal Storage
Flash latest Recovery Image (Stable Global) using TWRP
Flash SuperSU 2.78 using TWRP
Everything works as I want it to be right now. It was rather hard since the information was very limited and I haven't seen a detailed guide on how to do this.
If I have time, I'll try to do a short guide. I read a lot of posts in other forums that this was not possible without using a custom ROM which was not the case.
Nonetheless, two questions are coming to mind.
How can I update my ROM if a new version comes out without losing root?
Is Xposed available and if so, where do I download it and how do I flash it?
Thanks!
Click to expand...
Click to collapse
1.You have done it already... Do the same steps from Copy..., Flash..., Flash...
2.Install this Xposed Installer and within you have option to install miui xposed framework
http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
nijel8 said:
1.You have done it already... Do the same steps from Copy..., Flash..., Flash...
2.Install this Xposed Installer and within you have option to install miui xposed framework
http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Click to expand...
Click to collapse
Alright. So I don't have to format the filesystem the next time I install an update?
Thanks. Installing that now.
CM14.1
So I just ordered this set. Primary goal was ofcourse to watch anime, secondary goal being psp emulation.
I was quite surprised I cannot disable any of the core system apps unlike my karbonn titanium where disabling google stuff made the 2000mah battery last 3 days in 2g mode without wifi easily.
I think the only way to remove the gapps would be to flash a custom rom at this point, being the CM14.1 with nougat. So my question is, the guide mentions installing the gapps after nougat, I want to know if I can skip it? The main guide doesn't mention anything about skipping it, would like to know what would happen.
Hi guys, Just added a Telegram invite link to the 2nd post.
It will help in making the community grow. Also you can help the developers to test ROMs/Kernels.
nonoganosus said:
So I just ordered this set. Primary goal was ofcourse to watch anime, secondary goal being psp emulation.
I was quite surprised I cannot disable any of the core system apps unlike my karbonn titanium where disabling google stuff made the 2000mah battery last 3 days in 2g mode without wifi easily.
I think the only way to remove the gapps would be to flash a custom rom at this point, being the CM14.1 with nougat. So my question is, the guide mentions installing the gapps after nougat, I want to know if I can skip it? The main guide doesn't mention anything about skipping it, would like to know what would happen.
Click to expand...
Click to collapse
I think skipping it won't prevent the device from functioning correctly. However, you won't have access to Google's services including the Play Store if I'm not mistaken.
---------- Post added at 09:52 AM ---------- Previous post was at 09:37 AM ----------
nijel8 said:
1.You have done it already... Do the same steps from Copy..., Flash..., Flash...
2.Install this Xposed Installer and within you have option to install miui xposed framework
http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Click to expand...
Click to collapse
Xposed installer worked great mate! Thanks.
So all I have to do is to flash the new ROM using the update(ZIP) package. Then flash SuperSU again? I'll probably have to re-install Xposed/Busybox too right?
Also, if the update is available and I flash an update ZIP from within TWRP, won't it overwrite userdata? I'm not sure but I think that zip contains some of these: (I have zero idea what these are) :highfive:
Code:
Line 206: /data(/.*)? u:object_r:system_data_file:s0
Line 207: /data/.layout_version u:object_r:install_data_file:s0
Line 208: /data/unencrypted(/.*)? u:object_r:unencrypted_data_file:s0
Line 209: /data/backup(/.*)? u:object_r:backup_data_file:s0
Line 210: /data/secure/backup(/.*)? u:object_r:backup_data_file:s0
Line 211: /data/security(/.*)? u:object_r:security_file:s0
Line 212: /data/system/ndebugsocket u:object_r:system_ndebug_socket:s0
Line 213: /data/drm(/.*)? u:object_r:drm_data_file:s0
Line 214: /data/gps(/.*)? u:object_r:gps_data_file:s0
Line 215: /data/resource-cache(/.*)? u:object_r:resourcecache_data_file:s0
Line 216: /data/dalvik-cache(/.*)? u:object_r:dalvikcache_data_file:s0
Line 217: /data/dalvik-cache/profiles(/.*)? u:object_r:dalvikcache_profiles_data_file:s0
Line 218: /data/adb(/.*)? u:object_r:adb_data_file:s0
Line 219: /data/anr(/.*)? u:object_r:anr_data_file:s0
Line 220: /data/app(/.*)? u:object_r:apk_data_file:s0
Line 221: /data/app/[^/]+/oat(/.*)? u:object_r:dalvikcache_data_file:s0
Line 222: /data/app/vmdl[^/]+\.tmp(/.*)? u:object_r:apk_tmp_file:s0
Line 223: /data/app/vmdl[^/]+\.tmp/oat(/.*)? u:object_r:dalvikcache_data_file:s0
Line 224: /data/app-private(/.*)? u:object_r:apk_private_data_file:s0
Line 225: /data/app-private/vmdl.*\.tmp(/.*)? u:object_r:apk_private_tmp_file:s0
Line 226: /data/tombstones(/.*)? u:object_r:tombstone_data_file:s0
Line 227: /data/local/tmp(/.*)? u:object_r:shell_data_file:s0
Line 228: /data/media(/.*)? u:object_r:media_rw_data_file:s0
Line 229: /data/mediadrm(/.*)? u:object_r:media_data_file:s0
Line 230: /data/property(/.*)? u:object_r:property_data_file:s0
Line 233: /data/misc/adb(/.*)? u:object_r:adb_keys_file:s0
Line 234: /data/misc/audio(/.*)? u:object_r:audio_data_file:s0
Line 235: /data/misc/bluetooth(/.*)? u:object_r:bluetooth_data_file:s0
Line 236: /data/misc/bluedroid(/.*)? u:object_r:bluetooth_data_file:s0
Line 237: /data/misc/bluedroid/\.a2dp_ctrl u:object_r:bluetooth_socket:s0
Line 238: /data/misc/bluedroid/\.a2dp_data u:object_r:bluetooth_socket:s0
Line 239: /data/misc/camera(/.*)? u:object_r:camera_data_file:s0
Line 240: /data/misc/dhcp(/.*)? u:object_r:dhcp_data_file:s0
Line 241: /data/misc/gatekeeper(/.*)? u:object_r:gatekeeper_data_file:s0
Line 242: /data/misc/keychain(/.*)? u:object_r:keychain_data_file:s0
Line 243: /data/misc/keystore(/.*)? u:object_r:keystore_data_file:s0
Line 244: /data/misc/logd(/.*)? u:object_r:misc_logd_file:s0
Line 245: /data/misc/media(/.*)? u:object_r:media_data_file:s0
Line 246: /data/misc/net(/.*)? u:object_r:net_data_file:s0
Line 247: /data/misc/shared_relro(/.*)? u:object_r:shared_relro_file:s0
Line 248: /data/misc/sms(/.*)? u:object_r:radio_data_file:s0
Line 249: /data/misc/systemkeys(/.*)? u:object_r:systemkeys_data_file:s0
Line 250: /data/misc/user(/.*)? u:object_r:misc_user_data_file:s0
Line 251: /data/misc/vpn(/.*)? u:object_r:vpn_data_file:s0
Line 252: /data/misc/wifi(/.*)? u:object_r:wifi_data_file:s0
Line 253: /data/misc/wifi/sockets(/.*)? u:object_r:wpa_socket:s0
Line 254: /data/misc/wifi/sockets/wpa_ctrl.* u:object_r:system_wpa_socket:s0
Line 255: /data/misc/wifi/hostapd(/.*)? u:object_r:wpa_socket:s0
Line 256: /data/misc/zoneinfo(/.*)? u:object_r:zoneinfo_data_file:s0
Line 257: /data/misc/vold(/.*)? u:object_r:vold_data_file:s0
Line 258: /data/misc/perfprofd(/.*)? u:object_r:perfprofd_data_file:s0
Line 259: /data/system/heapdump(/.*)? u:object_r:heapdump_data_file:s0
Line 262: /data/system/users/[0-9]+/fpdata(/.*)? u:object_r:fingerprintd_data_file:s0
Line 265: /data/bootchart(/.*)? u:object_r:bootchart_data_file:s0
Line 284: /data/system/users/[0-9]+/wallpaper u:object_r:wallpaper_file:s0
Line 312: /data/app-asec(/.*)? u:object_r:asec_image_file:s0
Line 326: /data/fpc(/.*)? u:object_r:fpc_data_file:s0
Line 330: # /data/extend_size.userdata
Line 331: /data/extend_size.userdata u:object_r:cache_file:s0
Line 613: /data/connectivity(/.*)? u:object_r:cnd_data_file:s0
Line 614: /data/data_test(/.*)? u:object_r:data_test_data_file:s0
Line 614: /data/data_test(/.*)? u:object_r:data_test_data_file:s0
Line 615: /data/diag_log(/.*)? u:object_r:diag_data_file:s0
Line 616: /data/misc/sensors(/.*)? u:object_r:sensors_data_file:s0
Line 617: /data/rfs.* u:object_r:rfs_file:s0
Line 618: /data/hlos_rfs(/.*)? u:object_r:rfs_shared_hlos_file:s0
Line 619: /data/camera(/.*)? u:object_r:camera_socket:s0
Line 620: /data/misc/stargate(/.*)? u:object_r:qfp-daemon_data_file:s0
Line 621: /data/system/sensors(/.*)? u:object_r:sensors_data_file:s0
Line 622: /data/time(/.*)? u:object_r:time_data_file:s0
Line 623: /data/nfc(/.*)? u:object_r:nfc_data_file:s0
Line 624: /data/system/perfd(/.*)? u:object_r:mpctl_data_file:s0
Line 625: /data/misc/iop(/.*)? u:object_r:iop_data_file:s0
Line 626: /data/misc/iop/iop u:object_r:iop_socket:s0
Line 627: /data/misc/display(/.*)? u:object_r:display_misc_file:s0
Line 628: /data/misc/ipa(/.*)? u:object_r:ipacm_data_file:s0
Line 629: /data/dpm(/.*)? u:object_r:dpmd_data_file:s0
Line 630: /data/misc/qsee(/.*)? u:object_r:data_qsee_file:s0
Line 631: /data/misc/location(/.*)? u:object_r:location_data_file:s0
Line 632: /data/misc/location/mq/location-mq-s u:object_r:location_socket:s0
Line 633: /data/misc/location/mq/alarm_svc u:object_r:location_socket:s0
Line 634: /data/FTM_AP(/.*)? u:object_r:mmi_data_file:s0
Line 635: /data/misc/hbtp(/.*)? u:object_r:hbtp_log_file:s0
Line 636: /data/misc/qlogd(/.*)? u:object_r:qlogd_data_file:s0
Line 637: /data/usf(/.*)? u:object_r:usf_data_file:s0
Line 638: /data/misc/dts(/.*)? u:object_r:dts_data_file:s0
Line 639: /data/misc/seemp(/.*)? u:object_r:seemp_file:s0
Line 640: /data/misc/SelfHost(/.*)? u:object_r:RIDL_data_file:s0
Line 641: /data/misc/qti-logkit(/.*)? u:object_r:qti_logkit_priv_data_file:s0
Line 642: /data/misc/qti-logkit/shared-public(/.*)? u:object_r:qti_logkit_pub_data_file:s0
Line 643: /data/misc/qti-logkit/logdata(/.*)? u:object_r:qti_logkit_pub_data_file:s0
Line 644: /data/misc/radio(/.*)? u:object_r:radio_data_file:s0
Line 645: /data/misc/port_bridge(/.*)? u:object_r:port_bridge_data_file:s0
Line 646: /data/misc/fm(/.*)? u:object_r:fm_data_file:s0
Line 647: /data/misc/audio_pp(/.*)? u:object_r:audio_pp_data_file:s0
Line 648: /data/ramdump(/.*)? u:object_r:ssr_ramdump_data_file:s0
Line 649: /data/misc/SelfHost/socket(/.*)? u:object_r:RIDL_socket:s0
Line 650: /data/misc/qti-logkit/socket-privileged(/.*)? u:object_r:qti_logkit_priv_socket:s0
Line 651: /data/fpc/s(/.*)? u:object_r:fpc_stat_data_file:s0
Line 652: /data/misc/qti-logkit/socket-public(/.*)? u:object_r:qti_logkit_pub_socket:s0
Line 660: /persist/data(/.*)? u:object_r:persist_drm_file:s0
Line 661: /persist/data/tz(/.*)? u:object_r:persist_drm_file:s0
Line 662: /persist/data/sfs(/.*)? u:object_r:persist_drm_file:s0
Line 816: /data/display-tests/media(/.*)? u:object_r:display_test_media_file:s0
Line 837: /data/system/mcd(/.*)? u:object_r:mcd_data_file:s0
Line 842: /data/system/nativedebug(/.*)? u:object_r:miui_native_file:s0
Line 843: /data/system/nativedebug/core(/.*)? u:object_r:miui_coredump_file:s0
Line 848: /data/system/theme(/.*)? u:object_r:theme_data_file:s0
Line 849: /data/system/theme_magic(/.*)? u:object_r:theme_data_file:s0
Line 863: /data/user/1[0-9]+/.* u:object_r:app_data_file:s0
Line 864: /data/user/1[0-9]+/com.android.providers.downloads/cache u:object_r:download_file:s0
Line 871: /data/system/users/[0-9]+/.Spaces(/.*)? u:object_r:securespaces_file:s0
oreo27 said:
I think skipping it won't prevent the device from functioning correctly. However, you won't have access to Google's services including the Play Store if I'm not mistaken.
Click to expand...
Click to collapse
Think... not good enough Would help to know if someone is sure. I'm actually puzzled its not given in the FAQ like "Can I skip GAPPS zip install after nougat rom").
Also really wish I could post on that main CM14.1 thread. Would like to have some before after benchmarks.
Hi Guys,quick one from me.Can the 'dual apps' feature be used for many apps at same time?Like viber,line,whatsapp etc?
Has anyone had scratches on this device? I scratched the top part (metal, I think) of mine and I was wondering if it's possible to remove it like how one would remove light scratches on a car using a buffing tool?
my charger makes sound slight soundwhen charging. is it normal?
shaun95 said:
my charger makes sound slight soundwhen charging. is it normal?
Click to expand...
Click to collapse
Had this in another device. I've read somewhere that this is perfectly normal. It scared me the first time I heard it too.
oreo27 said:
Has anyone had scratches on this device? I scratched the top part (metal, I think) of mine and I was wondering if it's possible to remove it like how one would remove light scratches on a car using a buffing tool?
Click to expand...
Click to collapse
If you're talking about the very top of the phone then its definitely plastic. Both the top and bottom sections of the rear cover are plastic caps. Only the middle section is metal. If the scratch is at the top of the middle section you might be able to buff it out, but I guess you'd run the risk of making a larger mark. Good luck!
RAMBO29 said:
Hi Guys,quick one from me.Can the 'dual apps' feature be used for many apps at same time?Like viber,line,whatsapp etc?
Click to expand...
Click to collapse
I think so, although I haven't tried it myself. On my device it recommends WhatsApp, Facebook, and Facebook Messenger. Plus, it lists all my other installs below, so I think you should be able to clone just about anything
Enable Softkeys on Navbar
Hi Folks. Has anyone been able to enable the Navbar on this device. I've tried the following to no avail:
GravityBox
SoftKey Enabler APK
qemu.hw.mainkeys=0
Is that Mi Max has different some hardware variant too between old batch and new batch?, like redmi note 3 that has two different FP sensor (goodix and fpc1020), has different front and back camera, also has different display, this cause some of a loot custom rom still doesn't support one of that hardware variant.
I'm interested in buying the Xiaomi Mi Max. But before I do I got some questions:
1) Is it compatible with T-mobile USA on their 4G LTE?
2) Can you install Marshmallow on it?
3) Is the phone easily bendable making it not structurally sound?
4) I saw a review that said that the video recording was jumpy and not stable. If this is true, is there a fix to this?
5) What are any problems with it you dont like?
6) Which is better, this phone or the Doogee Y6 Max?
7) Do you recommend this phone?
nonoganosus said:
Think... not good enough Would help to know if someone is sure. I'm actually puzzled its not given in the FAQ like "Can I skip GAPPS zip install after nougat rom").
Also really wish I could post on that main CM14.1 thread. Would like to have some before after benchmarks.
Click to expand...
Click to collapse
Hi, first of all thx @Vatsal for this thread, on my understanding you perfectly can skip to flash GAPPs cause no included in any nougat rom for mi max, but some apps need Play Services to work correctly, other you can freeze them with greenify or doze or other.
If you update from same version rom don't erase any data, of course yes all you flashed by recovery (mods, supersu) and you must reflash again and before reboot recommend for best performance.
I'm on last version 8.1.4.0 and my method to update is after download zip delete file emmc_appsboot_mnc from romzip/update-firmware to avoid replace recovery or relock bootloader.
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) ?
{
"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
Just learned about GIS. Still using a Galaxy S4 w/Lineage, but am a huge fan of eink everything and impulse pre-ordered this new black and white phone from new and unknown Chinese vendor. Alleged to ship in August.
Assumed I was just going to use it off line as an ebook reader (to replace my kobo mini), but GIS has given me hope that there is a chance for a (relatively) safe/unbloated life for this device beyond that.
I’m sure there will be some eink optimization in the official ROM, but am less concerned about that than I am mysterious Chinese software.
Would love to hear anyone’s thoughts. I am more than happy to contribute to the cost of a Getting a test device in capable hands if necessary.
As a privacy enthusiast would also appreciate thoughts on hardware security on random Chinese phone as well. This is the first time I’ve ever gone out on such a limb.
Kingrow K1 Specs
5.17-inch E Ink Carta display (1280 x 720 with 283 ppi).
Frontlight.
2.0GHz MediaTek Helio P23 (MT6763) octa-core processor.
16GB of storage space.
2GB of RAM.
MicroSD card slot with support up to 64GB.
3100 mAh battery.
8MP rear camera with LED flash and auto-focus.
Android 8.1 Oreo operating system.
Dual SIM.
USB-C port.
Dual speakers.
138 x 72 x 8.5mm.
Thanks in advance.
Just realized one particular hardware issue may be the front light (since screen is not backlit like an LCD) and the controls may not be identical to backlight controls. I hope it treats the screen brightness identically and that it won’t be an issue.
Bump. For this type of preocessor I’ve only seen one example of getting stock android running relatively easily, anybody have any insight on what I can expect in the attempt?
I waited with backing this project on Indiegogo, because of the lack of GMS. I hope that could be fixed through another rom. But I doubt there will be a big developer crowd for this device. Nevertheless its nice to see it here on XDA. Followed!
Hi, I just got my Kingrow K1 in the mail today. I've always wanted an e-ink smartphone for longer battery life + less distraction, so I'm pretty excited about this. Unfortunately, the preinstalled software looks rather clunky and, as you mention, it might include random Chinese bloat/spyware. I'm hoping somebody can root this thing and we can get a developer scene going for it.
Some of the work done for Barnes & Noble Nook devices might be relevant, as those are also e-ink devices running Android.
For future reference, here's a list of everything installed on the stock ROM. I'm still trying to sort out what it all is, I think all the MTK* stuff are alternatives to missing Google packages provided by MediaTek.
$ pm list packages -f
package:/system/priv-app/FMRadio/FMRadio.apk=com.android.fmradio
package:/system/app/Gba/Gba.apk=com.mediatek.gba
package:/system/priv-app/ImsService/ImsService.apk=com.mediatek.ims
package:/system/plugin/PrivacyProtectionLock/PrivacyProtectionLock.apk=com.mediatek.ppl
package:/system/priv-app/CtsShimPrivPrebuilt/CtsShimPrivPrebuilt.apk=com.android.cts.priv.ctsshim
package:/system/app/Uicc2Terminal/Uicc2Terminal.apk=org.simalliance.openmobileapi.uicc2terminal
package:/system/priv-app/MtkTelephonyProvider/MtkTelephonyProvider.apk=com.android.providers.telephony
package:/system/app/Camera/Camera.apk=com.mediatek.camera
package:/system/priv-app/MtkCalendarProvider/MtkCalendarProvider.apk=com.android.providers.calendar
package:/system/priv-app/MtkMediaProvider/MtkMediaProvider.apk=com.android.providers.media
package:/vendor/app/LPPeService/LPPeService.apk=com.mediatek.location.lppe.main
package:/system/priv-app/WallpaperCropper/WallpaperCropper.apk=com.android.wallpapercropper
package:/vendor/app/SchedulePowerOnOff/SchedulePowerOnOff.apk=com.mediatek.schpwronoff
package:/system/app/Protips/Protips.apk=com.android.protips
package:/system/app/SmartcardService/SmartcardService.apk=org.simalliance.openmobileapi.service
package:/system/priv-app/MtkDocumentsUI/MtkDocumentsUI.apk=com.android.documentsui
package:/vendor/overlay/framework-res__auto_generated_rro.apk=android.auto_generated_rro__
package:/system/priv-app/ExternalStorageProvider/ExternalStorageProvider.apk=com.android.externalstorage
package:/system/app/YGPS/YGPS.apk=com.mediatek.ygps
package:/system/priv-app/MtkSimProcessor/MtkSimProcessor.apk=com.mediatek.simprocessor
package:/system/app/HTMLViewer/HTMLViewer.apk=com.android.htmlviewer
package:/system/app/CompanionDeviceManager/CompanionDeviceManager.apk=com.android.companiondevicemanager
package:/system/app/QuickSearchBox/QuickSearchBox.apk=com.android.quicksearchbox
package:/system/priv-app/MtkMmsService/MtkMmsService.apk=com.android.mms.service
package:/system/priv-app/MtkDownloadProvider/MtkDownloadProvider.apk=com.android.providers.downloads
package:/system/app/EngineerMode/EngineerMode.apk=com.mediatek.engineermode
package:/system/priv-app/xxLauncher/xxLauncher.apk=com.android.xx.launcherink
package:/system/app/Omacp/Omacp.apk=com.mediatek.omacp
package:/system/app/MtkBrowser/MtkBrowser.apk=com.android.browser
package:/system/app/OP01SoundRecorder/OP01SoundRecorder.apk=com.android.soundrecorder
package:/system/priv-app/WfoService/WfoService.apk=com.mediatek.wfo.impl
package:/system/priv-app/DefaultContainerService/DefaultContainerService.apk=com.android.defcontainer
package:/system/app/RedStoneOta/RedStoneOta.apk=com.redstone.ota.ui
package:/system/app/MtkDownloadProviderUi/MtkDownloadProviderUi.apk=com.android.providers.downloads.ui
package:/system/app/PacProcessor/PacProcessor.apk=com.android.pacprocessor
package:/system/app/CertInstaller/CertInstaller.apk=com.android.certinstaller
package:/system/priv-app/MtkCarrierConfig/MtkCarrierConfig.apk=com.android.carrierconfig
package:/system/framework/framework-res.apk=android
package:/system/priv-app/MtkContacts/MtkContacts.apk=com.android.contacts
package:/vendor/app/EmCamera/EmCamera.apk=com.mediatek.emcamera
package:/system/app/EasterEgg/EasterEgg.apk=com.android.egg
package:/system/priv-app/MtkMms/MtkMms.apk=com.android.mms
package:/system/priv-app/MtpDocumentsProvider/MtpDocumentsProvider.apk=com.android.mtp
package:/system/app/NfcNci/NfcNci.apk=com.android.nfc
package:/system/priv-app/Stk1/Stk1.apk=com.android.stk
package:/system/priv-app/BackupRestoreConfirmation/BackupRestoreConfirmation.apk=com.android.backupconfirm
package:/system/plugin/PermissionControl/PermissionControl.apk=com.mediatek.security
package:/system/app/BtTool/BtTool.apk=com.mediatek.bluetooth.dtt
package:/system/priv-app/Provision/Provision.apk=com.android.provision
package:/system/priv-app/StatementService/StatementService.apk=com.android.statementservice
package:/system/app/MDMLSample/MDMLSample.apk=com.mediatek.mdmlsample
package:/system/app/MtkCalendar/MtkCalendar.apk=com.android.calendar
package:/system/app/DrmProvider/DrmProvider.apk=com.mediatek.providers.drm
package:/vendor/overlay/SysuiDarkTheme/SysuiDarkThemeOverlay.apk=com.android.systemui.theme.dark
package:/system/priv-app/MtkSettingsProvider/MtkSettingsProvider.apk=com.android.providers.settings
package:/system/priv-app/SharedStorageBackup/SharedStorageBackup.apk=com.android.sharedstoragebackup
package:/system/app/PrintSpooler/PrintSpooler.apk=com.android.printspooler
package:/system/app/Uicc1Terminal/Uicc1Terminal.apk=org.simalliance.openmobileapi.uicc1terminal
package:/system/app/BasicDreams/BasicDreams.apk=com.android.dreams.basic
package:/system/app/webview/webview.apk=com.android.webview
package:/system/priv-app/InputDevices/InputDevices.apk=com.android.inputdevices
package:/system/app/BuiltInPrintService/BuiltInPrintService.apk=com.android.bips
package:/system/framework/mediatek-res/mediatek-res.apk=com.mediatek
package:/vendor/app/AutoDialer/AutoDialer.apk=com.example
package:/system/priv-app/DuraSpeed/DuraSpeed.apk=com.mediatek.duraspeed
package:/system/priv-app/MusicFX/MusicFX.apk=com.android.musicfx
package:/system/app/ExtShared/ExtShared.apk=android.ext.shared
package:/system/priv-app/OneTimeInitializer/OneTimeInitializer.apk=com.android.onetimeinitializer
package:/vendor/app/NlpService/NlpService.apk=com.mediatek.nlpservice
package:/system/priv-app/MtkTelecom/MtkTelecom.apk=com.android.server.telecom
package:/system/app/KeyChain/KeyChain.apk=com.android.keychain
package:/system/app/PrintRecommendationService/PrintRecommendationService.apk=com.android.printservice.recommendation
package:/system/priv-app/MtkDialer/MtkDialer.apk=com.android.dialer
package:/system/app/MtkGallery2/MtkGallery2.apk=com.android.gallery3d
package:/system/app/GoogleTTS/GoogleTTS.apk=com.google.android.tts
package:/system/priv-app/ExtServices/ExtServices.apk=android.ext.services
package:/system/priv-app/CallLogBackup/CallLogBackup.apk=com.android.calllogbackup
package:/system/priv-app/MtkPackageInstaller/MtkPackageInstaller.apk=com.android.packageinstaller
package:/system/priv-app/ProxyHandler/ProxyHandler.apk=com.android.proxyhandler
package:/system/app/MtkLatinIME/MtkLatinIME.apk=com.android.inputmethod.latin
package:/system/priv-app/ManagedProvisioning/ManagedProvisioning.apk=com.android.managedprovisioning
package:/system/app/CalendarImporter/CalendarImporter.apk=com.mediatek.calendarimporter
package:/vendor/app/MTKThermalManager/MTKThermalManager.apk=com.mediatek.thermalmanager
package:/system/priv-app/CallRecorderService/CallRecorderService.apk=com.mediatek.callrecorder
package:/system/app/MtkWebView/MtkWebView.apk=com.mediatek.webview
package:/system/app/WAPPushManager/WAPPushManager.apk=com.android.smspush
package:/vendor/app/SimRecoveryTestTool/SimRecoveryTestTool.apk=com.mtk.telephony
package:/system/priv-app/Baidu_Location/Baidu_Location.apk=com.baidu.map.location
package:/system/priv-app/StorageManager/StorageManager.apk=com.android.storagemanager
package:/system/app/OpenWnn/OpenWnn.apk=jp.co.omronsoft.openwnn
package:/system/app/BookmarkProvider/BookmarkProvider.apk=com.android.bookmarkprovider
package:/system/priv-app/MtkSettings/MtkSettings.apk=com.android.settings
package:/system/app/MDMConfig/MDMConfig.apk=com.mediatek.mdmconfig
package:/system/app/ExactCalculator/ExactCalculator.apk=com.android.calculator2
package:/vendor/app/LocationEM2/LocationEM2.apk=com.mediatek.lbs.em2.ui
package:/system/app/CtsShimPrebuilt/CtsShimPrebuilt.apk=com.android.cts.ctsshim
package:/system/priv-app/VpnDialogs/VpnDialogs.apk=com.android.vpndialogs
package:/system/app/MtkEmail/MtkEmail.apk=com.android.email
package:/vendor/app/MusicBspPlus/MusicBspPlus.apk=com.android.music
package:/system/priv-app/MtkTeleService/MtkTeleService.apk=com.android.phone
package:/system/priv-app/Shell/Shell.apk=com.android.shell
package:/system/app/WallpaperBackup/WallpaperBackup.apk=com.android.wallpaperbackup
package:/system/priv-app/BlockedNumberProvider/BlockedNumberProvider.apk=com.android.providers.blockednumber
package:/system/app/UserDictionaryProvider/UserDictionaryProvider.apk=com.android.providers.userdictionary
package:/system/priv-app/MtkEmergencyInfo/MtkEmergencyInfo.apk=com.android.emergency
package:/system/priv-app/FusedLocation/FusedLocation.apk=com.android.location.fused
package:/system/app/FactoryTest/FactoryTest.apk=com.xthink.factorytest
package:/system/app/MtkDeskClock/MtkDeskClock.apk=com.android.deskclock
package:/system/priv-app/MtkSystemUI/MtkSystemUI.apk=com.android.systemui
package:/system/app/Exchange2/Exchange2.apk=com.android.exchange
package:/system/app/BluetoothMidiService/BluetoothMidiService.apk=com.android.bluetoothmidiservice
package:/system/app/MtkNlp/MtkNlp.apk=com.mediatek.location.mtknlp
package:/system/app/FileManager/FileManager.apk=com.mediatek.filemanager
package:/system/app/MTKLogger/MTKLogger.apk=com.mediatek.mtklogger
package:/system/app/SensorHub/SensorHub.apk=com.mediatek.sensorhub.ui
package:/system/app/MtkBluetooth/MtkBluetooth.apk=com.android.bluetooth
package:/system/app/MtkWallpaperPicker/MtkWallpaperPicker.apk=com.android.wallpaperpicker
package:/system/priv-app/MtkContactsProvider/MtkContactsProvider.apk=com.android.providers.contacts
package:/system/app/CaptivePortalLogin/CaptivePortalLogin.apk=com.android.captiveportallogin
package:/system/plugin/DataProtection/DataProtection.apk=com.mediatek.dataprotection
package:/vendor/app/WapiCertManager/WapiCertManager.apk=com.wapi.wapicertmanager
package:/system/app/kindlefc/kindlefc.apk=com.amazon.kindle
Click to expand...
Click to collapse
I've managed to get the device into fastboot mode. I'd like to flash a custom recovery like TWRP, but I don't know which one is compatible with this device. Any suggestions?
Bunyip123 said:
I've managed to get the device into fastboot mode. I'd like to flash a custom recovery like TWRP, but I don't know which one is compatible with this device. Any suggestions?
Click to expand...
Click to collapse
do you happen to have the stock firmware with the boot.IMG. i want to look at it and see if its similar to my device. i have a umidigi one max and it has the same chipset and it looks like alot of the same apps
th3d3ck3r said:
do you happen to have the stock firmware with the boot.IMG.
Click to expand...
Click to collapse
No, I don't have the stock firmware. If you can point me to some instructions, I'm happy to try to extract a copy of it and post it here.
Kingrow K1 doesn't let me log in to google services
Hi,
I'm not a developer, sorry for my lack of knowledgle, however I'm desparate to find a sollution, maybe you can help me here.
I've bought the Kingrow K1 only to find there's no way of signing in to google accounts, contacts, callendar etc. $%^&*()!~
I hope it's just a question of installing and configuring the missing pieces.
Can you please help me out?
Tom
Maybe flashing Gapps like on AOSP? ?
You could try flashing a gapps package like https://opengapps.org/ but I don't know if it will work without root.
Bunyip123 said:
You could try flashing a gapps package but I don't know if it will work without root.
Click to expand...
Click to collapse
Without TWRP
We even have no stock firmware. I see it's a first step to acquire it.
sandworm88 said:
Without TWRP
We even have no stock firmware. I see it's a first step to acquire it.
Click to expand...
Click to collapse
is it of any help the url that get called when a k1 fails to find a new OTA firmware?
It's using a server called
fota.redstone.net.cn
on the port 6100
and it's asking for service/request
_jet said:
is it of any help the url that get called when a k1 fails to find a new OTA firmware?
It's using a server called
fota.redstone.net.cn
on the port 6100
and it's asking for service/request
Click to expand...
Click to collapse
...i'm just asking, i don't know anything about how to retrieve (and keep) a firmware copy
Any updates on this? someone in Kingrow K1 eReader/Phone User Group on FB claims they got root:
{
"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"
}
Hello, I've worked on a MT6763 device before. You may be in luck because MTK devices have built-in flash mode you can access. This would mean you can dump partitions provided you locate their offsets (if you can get hands on a scatter file, that would help a lot). The flash mode also allows you to bypass any locked bootloader (though, you don't seem to face such issue, but nice to know it's possible) restrictions. You may also be able to dd the blocks and create a stock firmware dump for backup. A good chance TWRP can be ported without kernel sources by using a very similar device's port as a base and dropping your current recovery image's kernel and fstab values in it.
I do not own this device myself, but I am interested in any findings regarding this topic. Good luck.
EDIT:
_jet said:
...i'm just asking, i don't know anything about how to retrieve (and keep) a firmware copy
Click to expand...
Click to collapse
Can you tell me how your /dev/block structure looks like, (use ls). If you navigate deep enough, you will see "by-name" folder, you can then dd the "boot" partition as a boot.img file.
EDIT2:
Actually, I suggest just dd'ing your system partition to your PC. You can also flash GSIs using fastboot. By dd'ing your system partition, you essentially make a fallback in case the image fails.
Cernodile said:
Hello, I've worked on a MT6763 device before. You may be in luck because MTK devices have built-in flash mode you can access. This would mean you can dump partitions provided you locate their offsets (if you can get hands on a scatter file, that would help a lot). The flash mode also allows you to bypass any locked bootloader (though, you don't seem to face such issue, but nice to know it's possible) restrictions. You may also be able to dd the blocks and create a stock firmware dump for backup. A good chance TWRP can be ported without kernel sources by using a very similar device's port as a base and dropping your current recovery image's kernel and fstab values in it.
I do not own this device myself, but I am interested in any findings regarding this topic. Good luck.
EDIT:
Can you tell me how your /dev/block structure looks like, (use ls). If you navigate deep enough, you will see "by-name" folder, you can then dd the "boot" partition as a boot.img file.
EDIT2:
Actually, I suggest just dd'ing your system partition to your PC. You can also flash GSIs using fastboot. By dd'ing your system partition, you essentially make a fallback in case the image fails.
Click to expand...
Click to collapse
Thanks for you answer @Cernodile. I'm the guy Ti He who posted in the FB group.
I'm currently trying to port a TWRP to our device. First I did a full read with Miracle Box, so in case something goes wrong I can restore my device. I used a TWRP from Cubot King Kong 3 because it has the same SoC and GPU. I unpacked my stock recovery and the Cubot recovery and replaced files like recovery.img-kernel
recovery.img-kernel_offset
ramdisk/prop.default
ramdisk/init files
ramdisk/ueventd.rc
ramdisk/ect/recovery.fstab
I flashed the repacked recovery through fastboot and booted into TWRP. I assume that TWRP would have been booted, because I can do adb devices and see my phone in recovery. But the display only shows some black lines, so there must be something wrong. Do you have any idea where to look at? See attached the log from /cache/recovery/.
Regards - Timo
helnorsksvartmetall said:
Thanks for you answer @Cernodile
I'm currently trying to port a TWRP to our device. First I did a full read with Miracle Box, so in case something goes wrong I can restore my device. I used a TWRP from Cubot King Kong 3 because it has the same SoC and GPU. I unpacked my stock recovery and the Cubot recovery and replaced files like recovery.img-kernel
recovery.img-kernel_offset
ramdisk/prop.default
ramdisk/init files
ramdisk/ueventd.rc
ramdisk/ect/recovery.fstab
I flashed to repacked recovery through fastboot and booted into TWRP. I assume that TWRP would have been booted, because I can do adb devices and see my phone in recovery. But the display only shows some black lines, so there must be something wrong. Do you have any idea where to look at? See attached to log from /cache/recovery/.
Regards - Timo
Click to expand...
Click to collapse
That seems already quite promising! It seems like your device is trying to render some TWRP elements, perhaps you have wrong resolution set as suggested by "framebuffer: 3 (344 x 725)". What would assist me here greatly would be .prop files from stock and your TWRP port such as default.prop.
I also attached the Scatter file from my device on my last post.
See below the prop files from stock and port (Cubot King Row 3).
(I also tried with port TWRP from Umidigi One Max but with the same result)
helnorsksvartmetall said:
I also attached the Scatter file from my device on my last post.
See below the prop files from stock and port (Cubot King Row 3).
(I also tried with port TWRP from Umidigi One May but with the same result)
Click to expand...
Click to collapse
First inconsistencies I see:
This is in your stock, but not port.
Code:
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
dalvik.vm.isa.arm64.variant=cortex-a53
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=cortex-a53
Although, I don't think that is the cause. I'd keep looking for a device that has e ink patches for TWRP, you can use that as base, rebuild the similar device's TWRP and then do same port method.