[CLOSED][ROM][G950F][7.0] *** GoogleWiz (nougat) *** extreme debloat [20/01/2018] - Samsung Galaxy S8 ROMs, Kernels, Recoveries, & Oth

I would like to share my work. This is the first time that I post a ROM on XDA, please keep that in mind.
***
{
"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"
}
Wiz ***
This is an extremely debloated Samsung rom with absolutely minimal Samsung functionality. The basic ROM apps (dialer, messaging, contacts) are from Google. Only for Galaxy S8 international equinox (SM-950F). Personally I very much like the Samsung phones/hardware but I am not so fond of the software and bloatware. I also prefer to use a ROM which just has what I use. If you want Samsung stuff ... use another ROM !!!
Name
Originally I called this ROM "minirom" until pvillasuso used the term "wizgoogle" in this (https://forum.xda-developers.com/ga...me-debloat-t3730681/post75271202#post75271202) post. So I decided to call it "GoogleWiz"
Features
The ROM contains (only) the following Samsung applications:
- Base: NRD90M.G950FXXU1AQL5
- Settings (you can't get rid of this unfortunately)
- Gallery (because of its integration with Camera)
- Camera (because it uses all hardware capabilities)
- minimal lockscreen
- Always On Display (Samsung - personally I like this feature a lot)
- Fingerprint & iris scanning for security
- Blue light filter
Others:
- Nova as launcher (https://play.google.com/store/apps/details?id=com.teslacoilsw.launcher); IMHO still the BEST launcher out there
- Swiftkey as (only) keyboard (https://play.google.com/store/apps/details?id=com.touchtype.swiftkey)
- Rooted with Magisk (see https://forum.xda-developers.com/apps/magisk)
- Magisk manager (see https://forum.xda-developers.com/apps/magisk)
- Latest Google Play services/store
- Bixby key is mapped to Nova "home"
- Google dialer (as of v2)
- Google contacts (as of v2)
- Google messaging (as of v2)
- Google clock
- Google calendar
- Google calculator
- optimized build.prop
- based on December 2017 security update from Samsung (AQL5)
- huge CscFeature list (in system/csc/feature.xml)
- huge SEC_FLOATING_FEATURE list (see system/etc/floating_feature.xml)
- Google pixel boot animation (I don't like the Samsung one)
ROM does not contain country specific CSCs. All settings are generic. To be clear again: there is no other Samsung stuff: no Samsung account, no Samsung appstore, no Samsung Themestore, no Samsung device manager, no Samsung calendar, no KNOX, no Samsung XYZ ... Technically it is possible to even remove the Gallery from the ROM but I left it in due to its integration with Samsung's camera (removed in v3). Everything else (file manager, browser, maps, ...) you can download from the Google Play store. Your choice.
Before installing this ROM, please make sure that "OEM unlock" is enabled in your developer settings (if you don't understand what this means then probably this ROM is not for you). ROM is reasonably small (less than 1 GB). Install from TWRP (wipe system, data, cache, dalvik). Other devs, please feel free to (re)use this for your own work ... I am not asking anything from anybody, no donation, no thanks, no beer ... you don't even have to mention that you (re)use this. If you download the standard Google stuff from the play store (Gmail, Google+, Drive, ...) then you should have a phone very close to a Google Pixel. Choice is up to you. I will try to support questions / feedback but I have a busy job and cannot spend all my free time on this. If people do like it though, I will update using Samsung's monthly security updates (that is something which I do for myself anyway). I use this as my own personal daily driver (all the rest coming from the Google Play store). I will not answer questions such as "Can you please add Samsung feature X,Y,Z" ... I have deliberately removed them. If you want Samsung, go and use a Samsung ROM. There are instructions further down on how to create your own variant of the ROM so you can do this yourself if you want to add stuff. I will not answer PMs (don't have time to look at them). I have attached also a bash script (as .txt file). This is the script which I personally use to generate the ROM starting from a standard Samsung system.img. If you are a DEV, you can study this to see how I create this ROM. Again, feel free to (re)use.
Disclaimer
The usual disclaimers apply: no warranty, installing this will trip KNOX, install at your own risk, ... I am not responsible for soft or hard bricks. Your phone must have TWRP to install this ROM.
Performance
If you want slightly faster performance, enable the developer settings and then set the animation speeds to 0 (zero). Also enable GPU 2D hardware rendering. The first boot will take time (a few minutes) as all apk files will be run through the dex2oat compiler.
Download (multiple versions): https://www.androidfilehost.com/?w=files&flid=239365
v0 (2018-01-05):
- initial release
v1 (2018-01-06):
- fix lag starting up settings
- fix lag in settings for lockscreen/security
- included SimSettingsMgr
- included MTP
v2 (2018-01-20):
- Google dialer (https://play.google.com/store/apps/details?id=com.google.android.dialer)
- Google contacts (https://play.google.com/store/apps/details?id=com.google.android.contacts)
- Google messaging (https://play.google.com/store/apps/details?id=com.google.android.apps.messaging)
- AOSP gallery
- removed Samsung contacts
- removed Samsung dialer
- removed Samsung messaging
- removed Samsung gallery
- updated to latest Magisk
- updated to latest PlayStore & Play Services
- updated to latest SwiftKey
v3 (2018-01-27):
- fix annoying message when Google dialer starts
- fix problem with NFC payment
- updated Google play store and services
- updated to latest Samsung AOD
- updated to latest Swiftkey
- Samsung gallery is back (better integration with Camera)
- updated Google dialer, messaging, contacts to latest versions
- Magisk 15.3 and Magisk manager 5.5.5
v4 (2018-01-31):
- fix crash in cameraserver
- integrated Google clock (alarm tone can be selected from Google clock) (https://play.google.com/store/apps/details?id=com.google.android.deskclock)
- left a bit more notifications and ringtones
- integrated SmartFittingService (but it does not seem to do much)
- integrated old (but very good) calculator (goes way back from Cyanogen)
- integrated Iris Scanner (please test as I do not use this myself)
- Arabic language support
v5 (2018-02-02):
- fix icons in statusbar not being displayed properly
- removed SmartFittingService (no use)
- replaced calculator with Google calculator (https://play.google.com/store/apps/details?id=com.google.android.calculator)
- updated keyboard to latest SwiftKey version
- updated Google dialer to latest version
- integrated Google calendar in ROM
- updated Play store to latest version
v6 (2018-02-03):
- latest Samsung S8 kernel (Jan 6)
- remove Samsung inCallUI (/system/priv-app/SamsungInCallUI)
- adapted the padding in the statusbar
- ROM installation now creates /data/system/users/0/settings_secure.xml to use Google dialer InCallUI as default (not a very nice solution but I do not see a better one)
v7 (2018-02-04):
- fix problem with missing call notifications in Google dialer
v8 (2018-02-05):
- fix problem of not being able to add an account (Settings > Accounts > Add Account)
- fix problem of mobile hotspot / tethering not present in settings
v9 (2018-02-06):
- added ~50 alarm tones for Google clock
v10 (2018-02-09):
- fixes for Gallery albums
v11 (2018-02-10):
- fix emoji in SwiftKey keyboard
- updated to latest Google Play Store and Google Play Services
Display resolution
Please set display resolution in settings to largest size !!! Settings > Display > Screen resolution > WQHD+. After a fresh install the screen resolution may be RESET on the second boot. If that happens, just set it back to WQHD+ and it will work fine as of that time.
Theming
- install Substratum (https://play.google.com/store/apps/details?id=projekt.substratum)
- install sungstratum (https://play.google.com/store/apps/details?id=projekt.sungstratum)
- install a samsung compatible substratum theme (e.g. https://play.google.com/store/apps/details?id=com.brit.swiftblack.layers)
Other stuff
If you want heart rate monitor / stress monitor: install SHealth (https://play.google.com/store/apps/details?id=com.sec.android.app.shealth) from the play store.
Known bugs / issues
- Magisk's Safenet check fails (but Magisk hiding is working)
- Max battery saving mode is not working (due to emergency stuff removed from ROM)
- Device encryption will not work (as it relies on Samsung KNOX which has been fully removed)
- Samsung Pay will not work (as it relies on Samsung KNOX which has been fully removed)
- Android for work will not function
Adblocking
If you would like to have adblocking (everywhere: browser, apps) do the following:
> adb shell
# su
# hl
The "hl" command will replace the hosts file with a huge (> 200000) hosts which refer to IP address 0.0.0.0; this will make ads go away in your browser and applications. No ad-blocking app is required.
Building a variant of this ROM
Instructions (for linux) on how to build your own variant of this rom are in:
https://forum.xda-developers.com/showpost.php?p=75185320&postcount=57
(sorry, no script for Windows ... I don't use Windows ... but the linux script should be easy to adapt into a windows script)
Screenshots
Screenshots in attach. Note: the black screenshots are taken after Subtratum theming and with my personal home screen configuration (so this is not the default if you install the ROM). The default has white applications.
Credits
topjohnwu for Magisk (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
ASSAYYED for the updater-script (https://forum.xda-developers.com/ch...-android-roms-editor-assayyedkitchen-t3410545)
osm0sis for his script which allowed me to set the Google dialer as default (https://github.com/opengapps/opengapps/issues/301)
BSDgeek_Jake for the fantastic adblock hosts file MoaAB (https://forum.xda-developers.com/showthread.php?t=1916098)
jayantraj for the pixel boot animation (https://forum.xda-developers.com/ga...-google-pixel-boot-animation-samsung-t3528179)

XDA requires the source.
Can you share it?
Thanks

Sorry, what do you mean with "source" precisely?
thanks

batuzai04123 said:
XDA requires the source.
Can you share it?
Thanks
Click to expand...
Click to collapse
foobar66 said:
Sorry, what do you mean with "source" precisely?
thanks
Click to expand...
Click to collapse
Stock based roms do not require source code.... All looks good here

I just flashed your rom and what can I say.. Awesome rom so far so good! Im gonna test a lit bit more to see but is very stable ive been using for 4 hours and is very fluid and I dont like samsung apps so dont bother me at all. but there is only one thing I want you to know, since you debloat your rom, and delete com.samsung.faceservice and another apk called face, the setting app takes like 3 to 4 seconds to open up, and that is because those apk are missing. Im telling you that because Im a fan of debloating and I tried one time to delete those apps and happpend that. so if you could just please to fix that lag of setting Ill appreciate that nice rom!! keep it up!

torhect said:
I just flashed your rom and what can I say.. Awesome rom so far so good! Im gonna test a lit bit more to see but is very stable ive been using for 4 hours and is very fluid and I dont like samsung apps so dont bother me at all. but there is only one thing I want you to know, since you debloat your rom, and delete com.samsung.faceservice and another apk called face, the setting app takes like 3 to 4 seconds to open up, and that is because those apk are missing. Im telling you that because Im a fan of debloating and I tried one time to delete those apps and happpend that. so if you could just please to fix that lag of setting Ill appreciate that nice rom!! keep it up!
Click to expand...
Click to collapse
You are right, I noticed it too.
"Settings" app launched at about 2-3 seconds slower on me.
"Lock screen and security" window takes 3-4 seconds to load up.
Not of a big deal, but it would be better if Settings could be launched quicker.
Magisk's Safenet check fails also. Im not sure why. I clean flash this rom and everything is stock.
Also, the width covers the whole edge of the screen, making Timer, Notifications "broken" on every corner of the screen.
---------- Post added at 06:07 AM ---------- Previous post was at 05:52 AM ----------
Sim Card manager is force closing.
Love this debloated rom, but i think you could check on the issues we previously posted, including this sim card manager force closing. thank you.
rm -rf system/app/SimSettingMgr
You removed this system app , I think you've removed some essential system apps that's causing performance drop
and force close issues.
MTP Via usb cable doesn't work, Windows can't detect the phone via cable, even adb isn't working.

Looks good , thanks @ foobar66 !
Gonna wait ( for the coming "fixes" regarding the last comments ) to try it
This is what I was looking for , a really minimal samsung ROM
Cheers

batuzai04123 said:
You are right, I noticed it too.
"Settings" app launched at about 2-3 seconds slower on me.
"Lock screen and security" window takes 3-4 seconds to load up.
Not of a big deal, but it would be better if Settings could be launched quicker.
Magisk's Safenet check fails also. Im not sure why. I clean flash this rom and everything is stock.
Also, the width covers the whole edge of the screen, making Timer, Notifications "broken" on every corner of the screen.
---------- Post added at 06:07 AM ---------- Previous post was at 05:52 AM ----------
Sim Card manager is force closing.
Love this debloated rom, but i think you could check on the issues we previously posted, including this sim card manager force closing. thank you.
rm -rf system/app/SimSettingMgr
You removed this system app , I think you've removed some essential system apps that's causing performance drop
and force close issues.
MTP Via usb cable doesn't work, Windows can't detect the phone via cable, even adb isn't working.
Click to expand...
Click to collapse
Maybe the devolper should consider those tips in a next update also when i.want to reboot it take some time to reboot... Dont know why

Have u deleted Samsung Task Manager and all those which are there by default? I mean Samsung SPCM, which u can also see on Priv-app folder on most ROMs.
Thanks and regards

Hi all, thanks for the feedback. I am currently uploading v1 to AndroidFilehost. As soon as the upload is completed, I will update the OP with the link.
v1 (2018-01-06):
- fix lag starting up settings
- fix lag in settings for lockscreen/security
- included SimSettingsMgr
- included MTP
Personally I do not use MTP. I always upload files to my phone using ADB. So someone should test this.
ADB does work for me (on Linux), obviously you have to enable USB debugging in developer's settings (and on Linux you need proper UDEV configuration for ADB).
Also, note that I only have a Linux box. I do not use Windows. So I cannot test anything on Windows.
Please also set resolution of display to WQHD.
OP is updated. Safetynet check bug is still there. I have no idea right now why this fails.

miguelang611 said:
Have u deleted Samsung Task Manager and all those which are there by default? I mean Samsung SPCM, which u can also see on Priv-app folder on most ROMs.
Thanks and regards
Click to expand...
Click to collapse
Yes, this is not in the ROM.

For info:
Files in system/app:
Code:
4 drwxr-xr-x. 3 philip philip 4096 Jan 6 12:38 Bluetooth/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 CaptivePortalLogin/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 CertInstaller/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 DownloadProviderUi/
16 -rw-r--r--. 1 philip philip 13021 Dec 31 2008 FFFFFFFF000000000000000000000001.drbin
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 FilterProvider/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 GoogleCalendarSyncAdapter/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 GoogleContactsSyncAdapter/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 GoogleExtShared/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 KeyChain/
4 drwxr-xr-x. 2 philip philip 4096 Dec 31 2008 mcRegistry/
4 drwxr-xr-x 3 philip philip 4096 Jan 2 18:29 MyGoogleTTS/
4 drwxr-xr-x 3 philip philip 4096 Jan 2 18:29 MyKeyboard/
4 drwxr-xr-x 3 philip philip 4096 Jan 2 18:29 MyWebViewGoogle/
4 drwxr-xr-x. 3 philip philip 4096 Jan 6 12:38 NfcNci/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SimSettingMgr/
Files in system/priv-app:
Code:
4 drwxr-xr-x. 3 philip philip 4096 Jan 6 12:38 AODService_v25/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 BioFaceService/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 BlockedNumberProvider/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 BlueLightFilter/
4 drwxr-xr-x. 4 philip philip 4096 Dec 13 13:45 DefaultContainerService/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 DocumentsUI/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 ExternalStorageProvider/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 FaceService/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 FingerprintService2/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 FusedLocation/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 GoogleExtServices/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 GoogleLoginService/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 GoogleOneTimeInitializer/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 GooglePackageInstaller/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 GoogleServicesFramework/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 GPUDriver-S8MaliG71_70/
4 drwxr-xr-x. 3 philip philip 4096 Jan 6 12:38 HealthService/
4 drwxr-xr-x. 3 philip philip 4096 Jan 6 12:38 Messaging_SEP81/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 MmsService/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 MsgCommService/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 MtpApplication/
4 drwxr-xr-x. 3 philip philip 4096 Jan 6 12:38 MtpDocumentsProvider/
4 drwxr-xr-x 3 philip philip 4096 Jan 2 18:29 MyGooglePlayServices/
4 drwxr-xr-x 3 philip philip 4096 Jan 2 18:29 MyGooglePlayStore/
4 drwxr-xr-x 2 philip philip 4096 Jan 2 18:29 MyLauncher/
4 drwxr-xr-x 3 philip philip 4096 Jan 2 18:29 MyMagisk/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 OmaCP/
4 drwxr-xr-x. 3 philip philip 4096 Jan 6 12:38 PhotoStudio_WQHD_Dream/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SamsungCamera7/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SamsungContactsStable/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SamsungInCallUI/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SamsungVideoPlayer2016/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SecCalendarProvider_NOTSTICKER/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SecContactsProvider/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SecDownloadProvider/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SecGallery2015/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SecIrisService/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SecMediaProvider/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 SecSettings2/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 SecSettingsProvider2/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SecSetupWizard2015/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 SecTelephonyProvider_Epic/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 SettingsReceiver/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 SetupWizard/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 Shell/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 ShootingModeProvider2/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 smartfaceservice/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 SystemUI/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 Telecom/
4 drwxr-xr-x. 3 philip philip 4096 Dec 13 13:45 TeleService/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 VpnDialogs/
4 drwxr-xr-x. 2 philip philip 4096 Jan 6 12:38 WallpaperCropper2/

v1 uploaded; see OP for description.
https://www.androidfilehost.com/?w=files&flid=239365

Thank you very much for sharing this rom. I have one question, apart of security updates, will it be possible to make this rom once oreo final rom is released?

Yes, I will try when the final Oreo comes out (probably middle/end of January).

Downloading , thanks @foobar66
Cant wait to customize and try this out
Cheers

Adblocking:
If you would like to have adblocking do the following:
> adb shell
# su
# hl
The "hl" command will replace the hosts file with a huge (> 200000) hosts which refer to IP address 0.0.0.0; this will make ads go away in your browser and applications.

Dear foobar66. I am waiting for such kind of firmware very long time... But it is a pity this firmware doesn't match for s8+..
Could You help with launching this rom on S8+ for FD version.
And second thing. Could You add screen mirroring to your firmware. We have modern device and mirroring on modern TV is very useful thing
TYVM

Andrunya1978 said:
Dear foobar66. I am waiting for such kind of firmware very long time... But it is a pity this firmware doesn't match for s8+..
Could You help with launching this rom on S8+ for FD version.
And second thing. Could You add screen mirroring to your firmware. We have modern device and mirroring on modern TV is very useful thing
TYVM
Click to expand...
Click to collapse
I don't have an S8+ so I can't test anything.
I can explain how to do a build (if you're familiar with linux).

I haven't linux. Please do it. I can test.
And what about screen mirroring?

Related

[Q] rom compatibility with china tablet alps md706 mtk mt6675

anyone have the rom that compatibility with my china tablet model Alps MD706 with cpu MTK MT6577 dual core 1,2ghz with ram 512mb. MY current rom have sleep death bugs.
spec sheet at the attachment
amir5569 said:
anyone have the rom that compatibility with my china tablet model Alps MD706 with cpu MTK MT6577 dual core 1,2ghz with ram 512mb. MY current rom have sleep death bugs.
spec sheet at the attachment
Click to expand...
Click to collapse
Hi i have a very similiar tablet, in the build.prop says that is an ALPS MD706, but mine has 1.0 ghz procesor.
Are you interested?:good:
need stock room
fanáticomaniático said:
Hi i have a very similiar tablet, in the build.prop says that is an ALPS MD706, but mine has 1.0 ghz procesor.
Are you interested?:good:
Click to expand...
Click to collapse
Hi,
My china tablet (momo9 3g) bootloop as I installed unicode font apk which not compatibility with this tablet. I need your help to get stock firmware from other source. Then I can flash with livesuit. I tried to download this stock rom, but no luck all link are dead. from My tablet detail was follow:
Android version: REL 4.2.2
onandroid script version: -1.0
Device: md706 alps alps MID
Contents of: /proc/partitions
major minor #blocks name
7 0 1254 loop0
7 1 8348 loop1
7 2 43691 loop2
7 3 15624 loop3
7 4 49928 loop4
7 5 13545 loop5
7 6 39533 loop6
7 7 19782 loop7
179 0 7613440 mmcblk0
179 1 1 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 786432 mmcblk0p3
179 4 524288 mmcblk0p4
179 5 1048576 mmcblk0p5
179 6 5217376 mmcblk0p6
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 96 994816 mmcblk1
179 97 994691 mmcblk1p1
254 0 8347 dm-0
254 1 43690 dm-1
254 2 15624 dm-2
254 3 49927 dm-3
254 4 13545 dm-4
254 5 39532 dm-5
254 6 19782 dm-6
7 8 2111 loop8
254 7 2110 dm-7
7 9 3150 loop9
254 8 3150 dm-8
7 10 43691 loop10
254 9 43690 dm-9
7 11 31217 loop11
254 10 31216 dm-10
7 12 36414 loop12
254 11 36414 dm-11
7 13 3150 loop13
254 12 3150 dm-12
Actually My friend has same model and similar tablet. Also has root access (root with rootmaster). But we don't known how to get img from his tablet. Anyway to get img from this tablet? In working tablet we install nanoid backup online apk and tried to backup nanoid. But not support for md706 model. Also tried rom manager, titanium backup pro and my backup pro, but cannot backup img.
We had read "CWM Recovery 6.0.1.2 for Allwinner A10 LY-F1/TREQ Tablets" but not dare to try. Cos some device got bootloop.
Pls share your stock rom.
sorry for my english.
I have momo93g with stock 4.1.2 jb. If i can help, i will. I am also interested in custom recovery, rom or kernel with overclock.
amir5569 said:
anyone have the rom that compatibility with my china tablet model Alps MD706 with cpu MTK MT6577 dual core 1,2ghz with ram 512mb. MY current rom have sleep death bugs.
spec sheet at the attachment
Click to expand...
Click to collapse
hello i have a smartpad mp720m mediacom is the Italian version of your tablet but according to some research I did on the internet appears to be identical to the md706 of Chinese production.
I think you can find help at this link
http://www.mediacomeurope.it/Supporto/Dettaglio.aspx?XRI=2129#googtrans(it|en)
---------- Post added at 08:53 AM ---------- Previous post was at 08:37 AM ----------
I have a question for you ... can you tell me if the mac address of your wi-fi card changes every time you activate the connection and turn it off? My tablet ...... has this problem and I do not understand what's causing it.
When active the wi fi I get a mac I can see in the status menu, after I turned off and on the wi fi and update status I can see a new mac with the last 3 pairs of different numbers.
This new mac I can see it in my router in the list of connected users.
You can check if you have the same problem on your models?
thank you!
fanáticomaniático said:
Hi i have a very similiar tablet, in the build.prop says that is an ALPS MD706, but mine has 1.0 ghz procesor.
Are you interested?:good:
Click to expand...
Click to collapse
Hi,i will be very glad if you can send this ROM to me, because i crashed mine
Hi,i will be very glad if you can send this ROM to me, because i crashed mine.my mail is [email protected]
ALPS MD706, 1.0 ghz procesor.
I need ROM (CM, AOKP, Stock) for NTT MD706 (link for firmware). Help! Please!
ROM for:
MD706B H V2 (4G + 512M + 1.0GHz Dual SIM)

[Q&A] Samsung Galaxy Appeal(Ace Q) SGH-I827(D) (AT&T GoPhone) - Root, Free Unlock

[Q&A] Samsung Galaxy Appeal(Ace Q) SGH-I827(D) (AT&T GoPhone) - Root, Free Unlock
Q&A for Samsung Galaxy Appeal(Ace Q) SGH-I827(D) (AT&T GoPhone) - Root, Free Unlock
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Samsung Galaxy Appeal(Ace Q) SGH-I827(D) (AT&T GoPhone) - Root, Free Unlock. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
thanks alot you made my day.
The information was very useful
xaueious said:
{
"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"
}
hardware
800mhz cortex a5 msm7227a processor, adreno 200 gpu, 512mb ram (400mb free in system).
Full qwerty keyboard, 3mp back camera fixed focus w/out led flash, qvga capacitive display (5 touchpoints).
This was all done on the i827d from telus. I was not able to retrieve the odin stock factory image from checkfus though.
The phone is retailing for $80 cad right now, making it one of the least expensive android devices on the market with these specs.
Internally it is very similar to the galaxy mini 2, which still retails for around the equivalent of $125usd.
root
confirmed root method here, with poot exploit package:
http://forum.xda-developers.com/showthread.php?t=2236445
do not require a pc. This will inject the su binary into your device. Then you need to manually install chainfire superuser and restart your phone.
free unlock
no root required
http://forum.xda-developers.com/showthread.php?t=1958859
my i827d (telus) never gets the 6th screen, but after nvdatainitialize, my device is fully unlocked already.
other notes
some people have ported cwm for this device, but at the moment there are no custom roms for this worth installing, so i wouldn't bother.
Samsung appears to be using an ondemand governor for some weird reason. Interactive governor is present and gives it a nice boost. Touchwiz launcher appears makes the phone sluggish.
i827d stuff
telus firmware code for 2.3.6
sgh-i827zsdtls
pda/phone: I827dtlle4
csc: I827doyble4
telus firmware has built in tethering support. If the at&t one doesn't i can dump the rom.
partitions
Code:
/dev/block/mmcblk0p16 /system ext4
/dev/block/mmcblk0p17 /cache ext4
/dev/block/mmcblk0p18 /data ext4
/dev/block/mmcblk0p19 /efs ext4
Code:
cat /proc/partitions
major minor #blocks name
179 0 3817472 mmcblk0
179 1 20 mmcblk0p1
179 2 150 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1000 mmcblk0p5
179 6 1000 mmcblk0p6
179 7 2000 mmcblk0p7
179 8 12288 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 12288 mmcblk0p12
179 13 4096 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 512 mmcblk0p15
179 16 512000 mmcblk0p16
179 17 153600 mmcblk0p17
179 18 956416 mmcblk0p18
179 19 12288 mmcblk0p19
179 20 24576 mmcblk0p20
179 21 4096 mmcblk0p21
179 22 51200 mmcblk0p22
179 23 1924534 mmcblk0p23
179 24 4096 mmcblk0p24
this looks almost identical to jena (mini 2): http://forum.xda-developers.com/showthread.php?p=30317179
this looks a lot like the mini 2. This is probably a good starting point here: https://github.com/thewhisp/
jena's partition naming from nandroidonline
https://github.com/ameer1234567890/...ter/part_layouts/raw/partlayout4nandroid.jena
if the partition maps match, boot image is partition 8, recovery is 12, and efs is 19.
Click to expand...
Click to collapse

S.Team Desire 816| S3-v3.0.0 | 6.0.1 Sense 7/7.0_g | KingSenseTweaks|HK Audio

{
"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"
}
ROM Base features:
Based on latest A9 base 1.57.1405.70
Android OS: Android 6.0.1 MMB29M from A9 (32 bit part)
Sense Version: Sense 7.0_g from A9, Sense 7 from M9
Hardware legacy drivers: A9 (32 bit part)
QMI (Qualcomm Message Interface) (Modem/Signal related): Latest M8
Android Media: A9 (32 bit part)
Camera Drivers: A9 + M8
FMRadio Drivers: A9
Audio: M8 HK Audio
Other Drivers/Libs/Modules: 100% unmodified A9 modules
Support model:a5dwg|a5dug|a5dwgl|a5tl|a5ul
All d816 Version:​
Made by @kinghunki for DualSim support
Based on S.ROM (Current: S3-12.0 c2)
Various options in Aroma Installer
Closer to pure stock
S Series - Original
S3: Based on A9 6.0.1, Sense 7_g
S.Team S3_Kinghunki_V3.0.0
Updates framework to 12.0 C2
Fixed 816V model
Added 816E support
Updated KingSenseTweaks
Added customizable statusbar network speed color
Added customizable statusbar label color
Added customizable statusbar arc information color
Added customizable statusbar battery bar color
Fixed unable to combine storage bug
Fixed unable to move app bug (need to switch to Sense 7 mode to work)
Fixed display wrong text after screenshot
Fixed Google contacts and calendar sync
Fixed start on boot manager and notification manager bug
Updated HTC Boost+ to latest version
Added optional Google services in Aroma
Added optional Root Explorer in Aroma
Added optional Titanium Backup in Aroma
Enabled developer options by default
S.Team S3_Kinghunki_V3.0.0 : MEGA Link
S.Team S3_Kinghunki_V3.0.0 : htcui Link
S.Team Lead Developer: sun_dream
XDA Support/Thread Maintainer: kinghunki
sun_dream for porting A9 to M8
kinghunki for XDA support, translation & Aroma
Chainfire for SuperSU
amarullz for Aroma installer
flar2 for wp_mod
It's not allowed to modify, repack this rom without my (sun_dream) permission.​​
first
second
Can anyone test this ? I can't download from baidu.
EDIT: Plus I really hope this one will work on UL version.
bonczas said:
Can anyone test this ? I can't download from baidu.
EDIT: Plus I really hope this one will work on UL version.
Click to expand...
Click to collapse
Please wait for MEGA upload!
MEGA upload to complete!
kinghunki said:
Please wait for MEGA upload!
MEGA upload to complete!
Click to expand...
Click to collapse
Tnx for your work guys.
Few remarks...
Aroma is in CN.
Setup process after successful boot is impossible to finish.
Since there are 216 apps, I guess there are lots of bloatware.
Couldn't check by myself, sorry.
bunkker said:
Tnx for your work guys.
Few remarks...
Aroma is in CN.
Setup process after successful boot is impossible to finish.
Since there are 216 apps, I guess there are lots of bloatware.
Couldn't check by myself, sorry.
Click to expand...
Click to collapse
HTC A9 official standards app!
我是路小轩
Got erro for a5_ul
HTC A5_Dug
Wifi not working...:crying:
Farid Sema said:
Got erro for a5_ul
Click to expand...
Click to collapse
Did you see the aroma installation process?
kinghunki said:
Did you see the aroma installation process?
Click to expand...
Click to collapse
Try to install as many times but error.
Farid Sema said:
Try to install as many times but error.
Click to expand...
Click to collapse
Probably system.img is too big for A5_UL /system partition.
bonczas said:
Probably system.img is too big for A5_UL /system partition.
Click to expand...
Click to collapse
Unfortunately the developer, from disk to disk, one and the same error. Too many applications for the system partition А5_UL. Plus encrypted system that does not give to delete part of the application for correct installation. I have repeatedly wrote on this topic, but the team S. Team has not fixed the problem.
A5UL user please wait, I will reduce the system size!
kinghunki said:
A5UL user please wait, I will reduce the system size!
Click to expand...
Click to collapse
Thank you for your prompt response, I look forward to an updated ROM.
I'm using a5dug, Wi-Fi doesn't work, in settings I can't see HK audio setting.
ROM so smooth, 3G work, camera work.
Huzin said:
I'm using a5dug, Wi-Fi doesn't work, in settings I can't see HK audio setting.
ROM so smooth, 3G work, camera work.
Click to expand...
Click to collapse
Flash ROM Model choice: 816w
Farid Sema said:
Try to install as many times but error.
Click to expand...
Click to collapse
adb shell
cat /proc/partitions
I need a5ul system partition size
kinghunki said:
adb shell
cat /proc/partitions
I need a5ul system partition size
Click to expand...
Click to collapse
c:\adb>adb shell
[email protected]_a5ul:/ $ cat /proc/partitio
cat /proc/partitions
major minor #blocks name
253 0 131072 zram0
253 1 131072 zram1
253 2 131072 zram2
253 3 131072 zram3
179 0 7634944 mmcblk0
179 1 1024 mmcblk0p1
179 2 32768 mmcblk0p2
179 3 16 mmcblk0p3
179 4 15327 mmcblk0p4
179 5 256 mmcblk0p5
179 6 24255 mmcblk0p6
179 7 256 mmcblk0p7
179 8 256 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 32 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 5120 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 32 mmcblk0p14
179 15 1024 mmcblk0p15
259 0 61441 mmcblk0p16
259 1 5120 mmcblk0p17
259 2 8192 mmcblk0p18
259 3 1536 mmcblk0p19
259 4 76801 mmcblk0p20
259 5 4096 mmcblk0p21
259 6 10240 mmcblk0p22
259 7 7167 mmcblk0p23
259 8 1024 mmcblk0p24
259 9 1536 mmcblk0p25
259 10 1536 mmcblk0p26
259 11 20480 mmcblk0p27
259 12 4 mmcblk0p28
259 13 256 mmcblk0p29
259 14 16 mmcblk0p30
259 15 1281 mmcblk0p31
259 16 64 mmcblk0p32
259 17 1024 mmcblk0p33
259 18 1 mmcblk0p34
259 19 8 mmcblk0p35
259 20 256 mmcblk0p36
259 21 25600 mmcblk0p37
259 22 30720 mmcblk0p38
259 23 14498 mmcblk0p39
259 24 16384 mmcblk0p40
259 25 16384 mmcblk0p41
259 26 278528 mmcblk0p42
259 27 2359296 mmcblk0p43
259 28 4587520 mmcblk0p44
179 16 4096 mmcblk0rpmb
179 32 31166976 mmcblk1
179 33 31165952 mmcblk1p1
[email protected]_a5ul:/ $

Bricked Device, Bootloop, Fastboot works

Hello to everyone, my englisch is not the best one, i'm sry for that
I have Bricked device here. 64gb MTK with china Mobile branding.
It's unlocked, rooted, twrp recovery.
It worked fine with root. But than i wanted to flash new Rom (xiaomi.eu_multi_HMNote4_7.1.19_v8-6.0.zip) from TWRP. Unfortanerly it's broke after 2 sec than reboot. The system startet normaly! Next day, I wanted to try it again. But i could not start the twrp rec. The device did start any more! Bootloop i see only the mi logo in the middle of Display after 30-60 sec reboot.
So recovery do not work. Fastboot work pretty fine.
I tried already pretty much.
I flashed almost all available Fastboot Roms with few different methods Smart Phone Flash*Tool & Miflash. With original cust.img and with modified one.
Almost every time the flash was successful in normal time (miflash
420 sec & smart phone flash tool about 200sec) still Bootloop.
Thanks for help greets
start in fastboot mode and flash new twrp
Code:
fastboot flash recovery TWRP.img
after if this sucessfull start recovery from fastboot
Code:
fastboot boot TWRP.img
Try to wipe all partitions and sideload your rom file.
headshotde said:
start in fastboot mode and flash new twrp
Code:
fastboot flash recovery TWRP.img
after if this sucessfull start recovery from fastboot
Code:
fastboot boot TWRP.img
Try to wipe all partitions and sideload your rom file.
Click to expand...
Click to collapse
I forgot, i flashed already few different recoveries.
Twrp 3.0.2 from cofface
Twrp 3.0.2-x from zcx
Stock recovery
Flash successful.
I start the device with power and vol +
The same story like with rom, Bootloop
okay try following
Boot in to Recovery via Fastboot boot twrp.img
now start adb shell in TWRP
and do following command # cat /proc/partitions
and post the result my Redmi Note 4 look like this...
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 61071360 mmcblk0
179 1 16384 mmcblk0p1
179 2 512 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 32768 mmcblk0p5
179 6 32768 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 13792 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 2048 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 24576 mmcblk0p12
179 13 4096 mmcblk0p13
179 14 3072 mmcblk0p14
179 15 5120 mmcblk0p15
179 16 1024 mmcblk0p16
179 17 1024 mmcblk0p17
179 18 5120 mmcblk0p18
179 19 4096 mmcblk0p19
179 20 4096 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 5120 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 530432 mmcblk0p26
179 27 3145728 mmcblk0p27
179 28 442368 mmcblk0p28
179 29 56660975 mmcblk0p29
179 30 44032 mmcblk0p30
179 31 16384 mmcblk0p31
179 96 4096 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 128 62367744 mmcblk1
179 129 62366720 mmcblk1p1
253 0 56660975 dm-0
~ # 
Unfortunately i can't boot into recovery, when I type
fastboot boot twrp.img happen nothing (i still see the fastboot logo on screen) after about 40 sec. Device reboot - - - > Bootloop
Gesendet von meinem HUAWEI MT7-L09 mit Tapatalk
make sure your twrp.img is inside the folder of adb
Gesendet von meinem Redmi Note 4 mit Tapatalk
Certainly is the twrp.img in adb folder.
On the PC screen i see that the recovery flash und boot was successful!
Sent from my HUAWEI MT7-L09 using Tapatalk
So i did it my redmi booted!!
The solution, remove battery tab for about 10 minutes. I read it @ 4pda Russian forum, Thanks for your help!
Sent from my HUAWEI MT7-L09 using Tapatalk
Daniel_Tregubov said:
So i did it my redmi booted!!
The solution, remove battery tab for about 10 minutes. I read it @ 4pda Russian forum, Thanks for your help!
Sent from my HUAWEI MT7-L09 using Tapatalk
Click to expand...
Click to collapse
i have the same problem as you,can u provide me more in detail plz
WickeGusLD said:
i have the same problem as you,can u provide me more in detail plz
Click to expand...
Click to collapse
Dear MasBro,
i got the same problem with my Redmi note 4 MTK, and here the solution :
* Open your caseback ReNo 4, for the information the screwdriver is 0.8. you can see the video in youtube. and becareful with the speaker on bottom of your phone
* after u open the caseback, unplug the conector battery from you handphone ( i dont know how long it need, but i unplug the battery for 1 hours )
* after that, plug back the connector and put it back the caseback ( dont turn on the handphone ).
* fastboot full rom using SP Tools, and enjoy you Redmi note 4 MTK back to normal.
Note:
- in some case the IMEI your will be missing, you can restore using "maui meta". for how to use that u can searching in google
- this is the last way u can do for u ReNo
- Do It By U Own Risk
- sorry, my languange a little bad.
JoninBlue said:
Dear MasBro,
i got the same problem with my Redmi note 4 MTK, and here the solution :
* Open your caseback ReNo 4, for the information the screwdriver is 0.8. you can see the video in youtube. and becareful with the speaker on bottom of your phone
* after u open the caseback, unplug the conector battery from you handphone ( i dont know how long it need, but i unplug the battery for 1 hours )
* after that, plug back the connector and put it back the caseback ( dont turn on the handphone ).
* fastboot full rom using SP Tools, and enjoy you Redmi note 4 MTK back to normal.
Note:
- in some case the IMEI your will be missing, you can restore using "maui meta". for how to use that u can searching in google
- this is the last way u can do for u ReNo
- Do It By U Own Risk
- sorry, my languange a little bad.
Click to expand...
Click to collapse
I have sent my phone back to xiaomi already,now it's fix.
Ps.for those people have this problem and u don't want to take risk .wipe my bootloader so that the warranty is true then sent it to xiaomi.
Anyway,thx bro,appreciate your help.

[GUIDE] EROFS - Mounting/ Accessing/ Creating system.img

Hiya folks! I'm trying to play with the firmware files for the P30 Pro, and have hit a roadblock. While I've gotten to extract the system.img (and all the other .img images) from update.app, I'm not able to mount or extract it using any of the usual tools because they are using EROFS file system.
I'm using Ubuntu 18.04 LTS, but haven't been able to spend much time on figuring out how to mount or access EROFS file systems yet. Has anyone gotten this figured out already? Any help will be great, thanks!
It started with that question, leading to finding the solution to mount the system.img, building mkfs.erofs and trying out a system.img etc.
I do not intend to work much on this, at least for quite a while owing to RL situations. In case anyone wants to build on this, please go ahead - everything I've used has a git that is linked appropriately
ph03n!x said:
In case anyone's looking to mount the erofs images from the stock firmware, here's what you have to do -
Download and extract UPDATE.APP from the firmware zip, and use splitupdate binary/ perl script or Huawei Update Extractor. (I have linked to the tools I have tried or used in the past)
Use simg2img to convert the system.img (or product.img or vendor.img) to raw format. simg2img is a part of android fsutils
Code:
sudo apt install android-tools-fsutils
You will need a linux box or VM with Kernel 5.x running (erofs support is added from 4.20, but I am running 5.x) - mount the raw image using
Code:
sudo mount -t erofs -o loop system.ext4.img /home/test/mnt/try2
(The "-t erofs" is optional - will work just fine with sudo mount -o loop system.ext4.img /home/test/mnt/try2)
You will get the erofs image mounted in the folder you've specified, and you can browse through it
Note that erofs images are not meant to be editable. If you want to modify the system.img, extract it's content and create a new system.img using the mkfs.erofs binary (I had linked to the source code). You'll of course need an unlocked bootloader to flash (or boot) the modified image
Click to expand...
Click to collapse
For building mkfs.erofs, here's what you need to do (mine is a Ubuntu 19.04 machine)
Code:
git clone https://kernel.googlesource.com/pub/scm/linux/kernel/git/xiang/erofs-utils.git -b dev
./autogen.sh
./configure
make
You will have the output in the mkfs/ folder.
More details from this post -
ph03n!x said:
@oslo83 I have attached the mkfs.erofs binary using this git source to the first post.
Please go through the README for this - I built this binary for the x64 architecture, and for lz4-1.9.0
The command options are -
Code:
mkfs.erofs 0.1
usage: [options] FILE DIRECTORY
Generate erofs image from DIRECTORY to FILE, and [options] are:
-zX[,Y] X=compressor (Y=compression level, optional)
-d# set output message level to # (maximum 9)
Note that the system.img that comes within UPDATE.APP is a root file system - here is a structure.
Code:
drwxr-xr-x. 2 root root 0 Aug 7 2018 3rdmodem
drwxr-xr-x. 2 root root 0 Aug 7 2018 3rdmodemnvm
drwxr-xr-x. 2 root root 0 Aug 7 2018 3rdmodemnvmbkp
drwxr-xr-x. 2 root root 0 Aug 7 2018 acct
lrw-r--r--. 1 root root 11 Aug 7 2018 bin -> /system/bin
lrw-r--r--. 1 root root 50 Aug 7 2018 bugreports -> /data/user_de/0/com.android.shell/files/bugreports
drwxrwx---. 2 ph03n1x 2001 0 Aug 7 2018 cache
lrw-r--r--. 1 root root 13 Aug 7 2018 charger -> /sbin/charger
dr-xr-xr-x. 2 root root 0 Aug 7 2018 config
drwxr-xr-x. 2 root root 0 Aug 7 2018 cust
lrw-r--r--. 1 root root 17 Aug 7 2018 d -> /sys/kernel/debug
drwxrwx--x. 2 ph03n1x ph03n1x 0 Aug 7 2018 data
drwxrwx--x. 2 ph03n1x ph03n1x 0 Aug 7 2018 data_old
lrw-------. 1 root root 23 Aug 7 2018 default.prop -> system/etc/prop.default
drwxr-xr-x. 2 root root 0 Aug 7 2018 dev
drwxr-xr-x. 2 root root 35 Aug 7 2018 dload
drwxr-xr-x. 2 root root 0 Aug 7 2018 eng
lrw-r--r--. 1 root root 11 Aug 7 2018 etc -> /system/etc
-rw-r-----. 1 root 2000 423 Aug 7 2018 fstab.zram1024m
-rw-r-----. 1 root 2000 423 Aug 7 2018 fstab.zram1280m
-rw-r-----. 1 root 2000 423 Aug 7 2018 fstab.zram1536m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram2240m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram256m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram4096m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram512m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram768m
-?????????? ? ? ? ? ? init
-rwxr-x---. 1 root 2000 1717 Aug 7 2018 init.environ.rc
-?????????? ? ? ? ? ? init.rc
-?????????? ? ? ? ? ? init.usb.configfs.rc
-?????????? ? ? ? ? ? init.usb.rc
-rwxr-x---. 1 root 2000 580 Aug 7 2018 init.zygote32.rc
-rwxr-x---. 1 root 2000 1042 Aug 7 2018 init.zygote64_32.rc
lrw-r--r--. 1 root root 8 Aug 7 2018 log -> /splash2
drwxr-xr-x. 2 root ph03n1x 0 Aug 7 2018 mnt
drwxr-xr-x. 2 root root 0 Aug 7 2018 modem_log
drwxr-xr-x. 2 root root 0 Aug 7 2018 odm
drwxr-xr-x. 2 root root 0 Aug 7 2018 oem
drwxr-xr-x. 6 root root 71 Aug 7 2018 patch
drwxr-xr-x. 2 root root 0 Aug 7 2018 patch_hw
drwxr-xr-x. 2 root root 0 Aug 7 2018 preload
drwxr-xr-x. 2 root root 0 Aug 7 2018 proc
drwxr-xr-x. 2 root root 0 Aug 7 2018 product
drwxr-xr-x. 2 root root 47 Aug 7 2018 res
-rw-r--r--. 1 root root 32 Aug 7 2018 resetFactory.cfg
drwxr-xr-x. 2 root root 0 Aug 7 2018 root
drwxr-x---. 2 root 2000 183 Aug 7 2018 sbin
lrw-r--r--. 1 root root 21 Aug 7 2018 sdcard -> /storage/self/primary
drwxr-xr-x. 2 root root 0 Aug 7 2018 sec_storage
drwxr-xr-x. 2 root root 0 Aug 7 2018 splash2
drwxr-x--x. 2 root 1028 0 Aug 7 2018 storage
drwxr-xr-x. 2 root root 0 Aug 7 2018 sys
drwxr-xr-x. 23 root root 478 Aug 7 2018 system
-?????????? ? ? ? ? ? ueventd.rc
drwxr-xr-x. 2 root 2000 0 Aug 7 2018 vendor
-rw-r--r--. 1 root root 524 Aug 7 2018 verity_key
drwxr-xr-x. 2 root root 0 Aug 7 2018 version
It would be good if you spend time with the system.img, vendor.img, product.img and understand how the structures are inter-linked. Happy hunting!
Click to expand...
Click to collapse
ph03n!x said:
Hiya folks! I'm trying to play with the firmware files for the P30 Pro, and have hit a roadblock. While I've gotten to extract the system.img (and all the other .img images) from update.app, I'm not able to mount or extract it using any of the usual tools because they are using EROFS file system.
I'm using Ubuntu 18.04 LTS, but haven't been able to spend much time on figuring out how to mount or access EROFS file systems yet. Has anyone gotten this figured out already? Any help will be great, thanks!
Click to expand...
Click to collapse
Current tools aren't working with EROFS, we will need new ones, compatible with EROFS.
Update as of today -
I have cloned erofs-utils git and have compiled mkfs for creating EROFS images. Will work on it whenever I have time to see if I can get an img to mount...
UPDATE 2 - SUCCESS!
In case anyone's looking to mount the erofs images from the stock firmware, here's what you have to do -
Download and extract UPDATE.APP from the firmware zip, and use splitupdate binary/ perl script or Huawei Update Extractor. (I have linked to the tools I have tried or used in the past)
Use simg2img to convert the system.img (or product.img or vendor.img) to raw format. simg2img is a part of android fsutils
Code:
sudo apt install android-tools-fsutils
You will need a linux box or VM with Kernel 5.x running (erofs support is added from 4.20, but I am running 5.x) - mount the raw image using
Code:
sudo mount -t erofs -o loop system.ext4.img /home/test/mnt/try2
(The "-t erofs" is optional - will work just fine with sudo mount -o loop system.ext4.img /home/test/mnt/try2)
You will get the erofs image mounted in the folder you've specified, and you can browse through it
Note that erofs images are not meant to be editable. If you want to modify the system.img, extract it's content and create a new system.img using the mkfs.erofs binary (I had linked to the source code). You'll of course need an unlocked bootloader to flash (or boot) the modified image
ph03n!x said:
Update as of today -
I have cloned erofs-utils git and have compiled mkfs for creating EROFS images. Will work on it whenever I have time to see if I can get an img to mount...
Click to expand...
Click to collapse
Have a look (read) here - > https://zhuanlan.zhihu.com/p/60617375
Pretoriano80 said:
Have a look (read) here - > https://zhuanlan.zhihu.com/p/60617375
Click to expand...
Click to collapse
I had come across that link earlier, but that is for compiling mkfs for arm/ arm64...
Got what I needed, mission accomplished
So have you actually modified system and packaged it back up as erofs and booted it?
freeza said:
So have you actually modified system and packaged it back up as erofs and booted it?
Click to expand...
Click to collapse
I do not have an unlocked bootloader yet - I have gotten as far as editing and recreating the EROFS image. One of these days I'll get the bootloader unlocked too :good:
ph03n!x said:
I do not have an unlocked bootloader yet - I have gotten as far as editing and recreating the EROFS image. One of these days I'll get the bootloader unlocked too :good:
Click to expand...
Click to collapse
Be careful with this kind of stuff after unlocking, Huawei devices are tricky as hell. Afaik Magisk already support EroFS, so it might be better to use that.
Of course,that's if you don't want to create some kind of custom rom, based on stock.
Pretoriano80 said:
Be careful with this kind of stuff after unlocking, Huawei devices are tricky as hell. Afaik Magisk already support EroFS, so it might be better to use that.
Of course,that's if you don't want to create some kind of custom rom, based on stock.
Click to expand...
Click to collapse
That is why I have two active phones, plus a few more right from the legendary HD2 to fall back on... what fun is it if you don't experiment with the flashy new hardware?!
I don't know when I will make credible progress on anything at all now though - am relocating to a different country shortly - to the home of Huawei
Hey! Congratulations and thank you for the time and effort you spent on this.
Also, It's awesome to see another LEO user! Mine died a while back, but that was the modders heaven!
I've got an unlocked device and rooted using Magisk.
Root Explorer or any other root tools available today cannot read the system partition. It shows as free space is 0 MB.
Actually, I can see the content inside /system but I cannot move anything to it - Like patching the hosts file.
Any clue on how to achieve that?
JazonX said:
Hey! Congratulations and thank you for the time and effort you spent on this.
Also, It's awesome to see another LEO user! Mine died a while back, but that was the modders heaven!
I've got an unlocked device and rooted using Magisk.
Root Explorer or any other root tools available today cannot read the system partition. It shows as free space is 0 MB.
Actually, I can see the content inside /system but I cannot move anything to it - Like patching the hosts file.
Any clue on how to achieve that?
Click to expand...
Click to collapse
You can't! You must use Magisk for that.
Pretoriano80 said:
You can't! You must use Magisk for that.
Click to expand...
Click to collapse
Hi Pretoriano,
Nice to see you on dead land. Remember those days when I was using Mate 10 Pro. Anyways let's move on and please guide us how to use magisk to push something in to system or remove / replace.
I'm rooted and looted on P30 Pro:laugh:
Thanks in advance,
goldybewon
goldybewon said:
Hi Pretoriano,
Nice to see you on dead land. Remember those days when I was using Mate 10 Pro. Anyways let's move on and please guide us how to use magisk to push something in to system or remove / replace.
I'm rooted and looted on P30 Pro:laugh:
Thanks in advance,
goldybewon
Click to expand...
Click to collapse
Just read Magisk documentation, it's easy to build yourself simple modules. Also you can get some examples from available modules.
JazonX said:
Actually, I can see the content inside /system but I cannot move anything to it - Like patching the hosts file.
Any clue on how to achieve that?
Click to expand...
Click to collapse
Pretoriano80 said:
You can't! You must use Magisk for that.
Click to expand...
Click to collapse
Yes, Pretoriano80 is right - EROFS by design is not meant to be modified. While I might take sometime later on to create a modified system.img, it'll be just an academic exercise - Magisk can easily add/ replace the contents of /system during boot, making system.img mods passe :angel:
@oslo83 I have attached the mkfs.erofs binary using this git source to the first post.
Please go through the README for this - I built this binary for the x64 architecture, and for lz4-1.9.0
The command options are -
Code:
mkfs.erofs 0.1
usage: [options] FILE DIRECTORY
Generate erofs image from DIRECTORY to FILE, and [options] are:
-zX[,Y] X=compressor (Y=compression level, optional)
-d# set output message level to # (maximum 9)
Note that the system.img that comes within UPDATE.APP is a root file system - here is a structure.
Code:
drwxr-xr-x. 2 root root 0 Aug 7 2018 3rdmodem
drwxr-xr-x. 2 root root 0 Aug 7 2018 3rdmodemnvm
drwxr-xr-x. 2 root root 0 Aug 7 2018 3rdmodemnvmbkp
drwxr-xr-x. 2 root root 0 Aug 7 2018 acct
lrw-r--r--. 1 root root 11 Aug 7 2018 bin -> /system/bin
lrw-r--r--. 1 root root 50 Aug 7 2018 bugreports -> /data/user_de/0/com.android.shell/files/bugreports
drwxrwx---. 2 ph03n1x 2001 0 Aug 7 2018 cache
lrw-r--r--. 1 root root 13 Aug 7 2018 charger -> /sbin/charger
dr-xr-xr-x. 2 root root 0 Aug 7 2018 config
drwxr-xr-x. 2 root root 0 Aug 7 2018 cust
lrw-r--r--. 1 root root 17 Aug 7 2018 d -> /sys/kernel/debug
drwxrwx--x. 2 ph03n1x ph03n1x 0 Aug 7 2018 data
drwxrwx--x. 2 ph03n1x ph03n1x 0 Aug 7 2018 data_old
lrw-------. 1 root root 23 Aug 7 2018 default.prop -> system/etc/prop.default
drwxr-xr-x. 2 root root 0 Aug 7 2018 dev
drwxr-xr-x. 2 root root 35 Aug 7 2018 dload
drwxr-xr-x. 2 root root 0 Aug 7 2018 eng
lrw-r--r--. 1 root root 11 Aug 7 2018 etc -> /system/etc
-rw-r-----. 1 root 2000 423 Aug 7 2018 fstab.zram1024m
-rw-r-----. 1 root 2000 423 Aug 7 2018 fstab.zram1280m
-rw-r-----. 1 root 2000 423 Aug 7 2018 fstab.zram1536m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram2240m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram256m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram4096m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram512m
-rw-r-----. 1 root 2000 422 Aug 7 2018 fstab.zram768m
-?????????? ? ? ? ? ? init
-rwxr-x---. 1 root 2000 1717 Aug 7 2018 init.environ.rc
-?????????? ? ? ? ? ? init.rc
-?????????? ? ? ? ? ? init.usb.configfs.rc
-?????????? ? ? ? ? ? init.usb.rc
-rwxr-x---. 1 root 2000 580 Aug 7 2018 init.zygote32.rc
-rwxr-x---. 1 root 2000 1042 Aug 7 2018 init.zygote64_32.rc
lrw-r--r--. 1 root root 8 Aug 7 2018 log -> /splash2
drwxr-xr-x. 2 root ph03n1x 0 Aug 7 2018 mnt
drwxr-xr-x. 2 root root 0 Aug 7 2018 modem_log
drwxr-xr-x. 2 root root 0 Aug 7 2018 odm
drwxr-xr-x. 2 root root 0 Aug 7 2018 oem
drwxr-xr-x. 6 root root 71 Aug 7 2018 patch
drwxr-xr-x. 2 root root 0 Aug 7 2018 patch_hw
drwxr-xr-x. 2 root root 0 Aug 7 2018 preload
drwxr-xr-x. 2 root root 0 Aug 7 2018 proc
drwxr-xr-x. 2 root root 0 Aug 7 2018 product
drwxr-xr-x. 2 root root 47 Aug 7 2018 res
-rw-r--r--. 1 root root 32 Aug 7 2018 resetFactory.cfg
drwxr-xr-x. 2 root root 0 Aug 7 2018 root
drwxr-x---. 2 root 2000 183 Aug 7 2018 sbin
lrw-r--r--. 1 root root 21 Aug 7 2018 sdcard -> /storage/self/primary
drwxr-xr-x. 2 root root 0 Aug 7 2018 sec_storage
drwxr-xr-x. 2 root root 0 Aug 7 2018 splash2
drwxr-x--x. 2 root 1028 0 Aug 7 2018 storage
drwxr-xr-x. 2 root root 0 Aug 7 2018 sys
drwxr-xr-x. 23 root root 478 Aug 7 2018 system
-?????????? ? ? ? ? ? ueventd.rc
drwxr-xr-x. 2 root 2000 0 Aug 7 2018 vendor
-rw-r--r--. 1 root root 524 Aug 7 2018 verity_key
drwxr-xr-x. 2 root root 0 Aug 7 2018 version
It would be good if you spend time with the system.img, vendor.img, product.img and understand how the structures are inter-linked. Happy hunting!
@ph03n!x
Is it possible to compile/assemble such software piece for Windows, or its unrealistical? There's millions of examples to explore ext4 images, but 0 about erofs.
I mean, we see sources. in C... i guess it should be still possible to translate it to something portable in Python or simply compile some component on Windows
dimon222 said:
@ph03n!x
Is it possible to compile/assemble such software piece for Windows, or its unrealistical? There's millions of examples to explore ext4 images, but 0 about erofs.
I mean, we see sources. in C... i guess it should be still possible to translate it to something portable in Python or simply compile some component on Windows
Click to expand...
Click to collapse
I will explore this when I find time.. relocating between countries at the moment. That said, please do not hold your breath - I'm more comfortable with Linux than with Windows. But I'll still give it a shot!
https://forum.xda-developers.com/mate-20-pro/help/emui-9-1-partition-rw-t3947916/post80059824
Thanks @ante0 for his mkfs.erofs arm build.
How do you convert system.img to raw img? System partion is erofs can you tell the trick clearly? With method... Plz
Has anyone tried this with WSL v2? Curious to see if it works.

Categories

Resources