{
"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"
}
This is only for Huawei Mate 8 (NXT)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x with decryption support.
Intended for usage on stock emui 5.x in combination with unlocked bootloader and
modded boot image with disabled dm-verity (depending on what you want to do).
Code:
[COLOR="red"][B]WARNING:[/B] since 3.1.0-2 update we've enabled image flashing to special partitions -
not just /recovery or /boot partition.
That means your device could be bricked in a few seconds if you do not pay attention
or don't know what you're doing. (Noobs please stay away out of this section!)[/COLOR]
Installation Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-1-next.img
3. reboot to recovery!
Rooting Methods
Code:
[B][U]1. Official SuperSU (not just 2.82+)[/U][/B]
1. Ensure you are running stock kernel from b380+
2. Tick the option "Keep vendor partition mounted" inside OpenKirin Settings
3. download and install [URL="www.supersu.com/download"]official SuperSU[/URL]
4. Enjoy!
[B][U]2. Custom SuperSU[/U][/B]
1. Make sure the device running stock EMUI 5.x boot.img
2. flash this modded SuperSU 2.79: [URL="https://drive.google.com/open?id=0BxWP2gF_0Bd_UmQ2Zm9ZRGxBTUE"]download here[/URL]
3. enjoy root :)
[COLOR="red"][B]NOTE:[/B][/COLOR] this is for every device (except kirin 960 based) running emui 5.x without loop support.
[B][U]3. Magisk[/U][/B]
1. ensure you are running a kernel from b380 or later
2. flash magisk
3. enjoy root & safetynet (read note)
[B][COLOR="red"]NOTE:[/COLOR][/B] Magisk Hide is a known problem on Huawei/Honor devices.
Make sure you are not rebooting/turning off your device with Magisk Hide enabled!
You may face a broken fingerprint scanner, do not worry,
simply disable magisk hide and reboot - fps works again!
Downloads
Code:
[LIST]
[URL="https://github.com/OpenKirin/android_device_huawei_next/releases/download/3.1.1-1/twrp-3.1.1-1-next.img"][U]download twrp-3.1.1-1-next.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 10. June 2017
Q: which Mate 8 models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
yes, you can! (have a look at the instructions in FAQ)
Q: Can i install LOS or AOSP based roms with this TWRP?
yes, you can! (please follow the installing procedure in the corresponding rom thread)
Q: Can i install Magisk?
A: Every ROM based upon b380+ kernel should now include proper loop support.
Since 3.1.0-3 you are able to flash Magisk through TWRP (recovery kernel has been updated)
Q: Does official SuperSU work?
A: Yes, even though chainfire included a fix in his upcomming version,
you can use every version of it, just check the "Rooting Instructions" section.
Q: ETAs?
A: No.
Going back from decrypted -> encrypted?
Code:
1. Format /data inside of TWRP
2. Flash eRecovery & Kernel from your currently installed Stock ROM Build
3. Do a factory reset inside of eRecovery
5. Let device boot up
6. Install your current firmware hw_data package & SuperSU using TWRP again
Want to decrypt? No problem.
Code:
1. Format /data inside of TWRP
2. Flash a kernel with forceencrypt disabled
3. bootup your device
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=2335078"]surdu_petru[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=220328"]paulobrien[/URL]
XDA:DevDB Information
[TWRP][3.1.1-0][MATE 8][DECRYPTION SUPPORT], Tool/Utility for the Huawei Mate 8
Contributors
OldDroid, XePeleato, surdu_petru
Source Code: http://ttps://github.com/OpenKirin
Version Information
Status: Stable
Created 2017-04-08
Last Updated 2017-06-11
Reserved
TWRP 3.1.0-1 next for encrypted/ decrypted data
This post has been deplaced here. I'll remove it when the TWRP above will work for encrypted/ decrypted data.
Thanks for comprehension!
I'm glad, that we can help the Mate 8 community
Thanks for distribution ...
The themes are here now.
Thanks!
Thak you very much.
I have your "Boot_Insecure_B560_Fix-adb_dm-verity.img" installed. Do you recomend to go back to stock boot and use this TWRP for any flashing? Or shoud i stay in a insecure boot?
Sorry but this twrp have not decryption support.
Have you test it on Mate 8 with no formated datas ? and boot with no disabled encryption ? with untouched boot ?
On my mate 8 with encrypt datas it don't work
I don't see my internal sdcard
But I take this twrp and I changed some parameters and it work fine for me .
TWRP-3.1.0-0_Decrypt_Mate-8.img
But it must be used on really encrypt datas, not formated .
I flash suspersu on an untouched boot and system and I'm root .
Us there 2 differnt versions of this twrp 1 for decripted data and 1 for formated data ??
jac10000 said:
Sorry but this twrp have not decryption support.
Have you test it on Mate 8 with no formated datas ? and boot with no disabled encryption ? with untouched boot ?
On my mate 8 with encrypt datas it don't work
I don't see my internal sdcard
But I take this twrp and I changed some parameters and it work fine for me .
TWRP-3.1.0-0_Decrypt_Mate-8.img
But it must be used on really encrypt datas, not formated .
I flash suspersu on an untouched boot and system and I'm root .
Click to expand...
Click to collapse
We can see what we can do with the both. A merger is perhaps possible?!
Edit:
Already it works with untouched boot.
With no formatted datas, it seems to me.
jac10000 said:
Sorry but this twrp have not decryption support.
Have you test it on Mate 8 with no formated datas ? and boot with no disabled encryption ? with untouched boot ?
On my mate 8 with encrypt datas it don't work
I don't see my internal sdcard
But I take this twrp and I changed some parameters and it work fine for me .
TWRP-3.1.0-0_Decrypt_Mate-8.img
But it must be used on really encrypt datas, not formated .
I flash suspersu on an untouched boot and system and I'm root .
Click to expand...
Click to collapse
Thank you very much for your test
As I can see it's working for decrypt unmodified /data if mount point to /dm-0 ...
franzyroy said:
We can see what we can do with the both. A merger is perhaps possible?!
Edit:
Already it works with untouched boot.
With no formatted datas, it seems to me.
Click to expand...
Click to collapse
I make a new TWRP, but should be tested in the same conditions like @jac10000 !
Also, please @jac10000, if you can test my new release to see if it decrypt /data , thanks !
EDIT :
Please, @franzyroy - you should test TWRP with unmodified data, so if your data was modified by wipe or format, you should restore device to Stock Huawei Firmware N by /dload/UPDATE.APP method . Thanks !
Downloads : twrp-3.1.0-next-v2.img md5 : 7ee1833ea51bf3835efc23851ad9a011
surdu_petru said:
Thank you very much for your test
As I can see it's working for decrypt unmodified /data if mount point to /dm-0 ...
I make a new TWRP, but should be tested in the same conditions like @jac10000 !
Also, please @jac10000, if you can test my new release to see if it decrypt /data , thanks !
EDIT :
Please, @franzyroy - you should test TWRP with unmodified data, so if your data was modified by wipe or format, you should restore device to Stock Huawei Firmware N by /dload/UPDATE.APP method . Thanks !
Downloads :twrp-3.1.0-next-v2.imgmd5 : 7ee1833ea51bf3835efc23851ad9a011
Click to expand...
Click to collapse
It seemed to me that dexz had tested it like that.
If I can test it, I'll do it. In the week, it's not really possible for me. @dexz should can do it.
jac10000 said:
Sorry but this twrp have not decryption support.
Have you test it on Mate 8 with no formated datas ? and boot with no disabled encryption ? with untouched boot ?
On my mate 8 with encrypt datas it don't work
I don't see my internal sdcard
But I take this twrp and I changed some parameters and it work fine for me .
TWRP-3.1.0-0_Decrypt_Mate-8.img
But it must be used on really encrypt datas, not formated .
I flash suspersu on an untouched boot and system and I'm root .
Click to expand...
Click to collapse
With the TWRP here, the root works too.
surdu_petru said:
Thank you very much for your test
As I can see it's working for decrypt unmodified /data if mount point to /dm-0 ...
I make a new TWRP, but should be tested in the same conditions like @jac10000 !
Also, please @jac10000, if you can test my new release to see if it decrypt /data , thanks !
EDIT :
Please, @franzyroy - you should test TWRP with unmodified data, so if your data was modified by wipe or format, you should restore device to Stock Huawei Firmware N by /dload/UPDATE.APP method . Thanks !
Downloads :twrp-3.1.0-next-v2.imgmd5 : 7ee1833ea51bf3835efc23851ad9a011
Click to expand...
Click to collapse
The one I tested and working yesterday was with /dm-0 before you posted another version.
Anyway twrp-3.1.0-next-v2.img is working fine and decrypted. Using adb shell mount. it show /data is on /dev/block/dm-5 the same with the one I have tested before.
Edit : I got force reboot using twrp-3.1.0-next-v2 after 5 seconds
Edit2 : It's only stop force reboot when I got the "Unmodified System Partition" screen.
Edit3 : I see force reboot stop if there's no changes on twrp setting (example time zone, language & etc)
@surdu_petru
Yes I just test it this twrp-3.1.0-next-v2.img and like @dezx I have force reboot when I use TWRP File Manager
dexz said:
The one I tested and working yesterday was with /dm-0 before you posted another version.
Anyway twrp-3.1.0-next-v2.img is working fine and decrypted. Using adb shell mount. it show /data is on /dev/block/dm-5 the same with the one I have tested before.
Edit : I got force reboot using twrp-3.1.0-next-v2 after 5 seconds
Edit2 : It's only stop force reboot when I got the "Unmodified System Partition" screen.
Edit3 : I see force reboot stop if there's no changes on twrp setting (example time zone, language & etc)
Click to expand...
Click to collapse
jac10000 said:
@surdu_petru
Yes I just test it this twrp-3.1.0-next-v2.img and like @dezx I have force reboot when I use TWRP File Manager
Click to expand...
Click to collapse
Perhaps you should make that and send the console.recovery.log to @surdu_petru or @OldDroid because if they have made the TWRP with mine, it's perhaps the cause.
@surdu_petru
---->logs
Thanks guys for feedback
I'll upload a new version very soon, hope will fix reboot issues !
I say that because :
I have no issues with a prerooted boot
It's also with Decrypted data boot
I can install a zip without to see an error
I see the internal storage
I can also see the size, not 0 MB
Only thing which doesn't work fine, when I mount the data, it's unmounted in the 5 seconds.
surdu_petru said:
Thanks guys for feedback
I'll upload a new version very soon, hope will fix reboot issues !
Click to expand...
Click to collapse
Thank you. Looking forward to it.
Sorry I'm out of like bullet :laugh:
New Test Version 3 !
Downloads : twrp-3.1.0-next-v3.img md5 : d969789ee06d3d323a98d9f028e6f475
Thank you for the feedback
Related
I've seen a couple of requests for the F2FS file system support in some of the CM12.x based rom threads and did some googling on why anyone would want F2FS instead of EXT4. There are also reports, by Nexus 7 users, that converting to F2FS fixes their performance issues.
So after some learning/failing, I'm releasing this zip file that updates (theoretically) any kernel to add F2FS support for the /cache partition. This is not necessary for the /data partition as it has always been F2FS formated (stock Moto or CM roms) for ghost :good:
The modification works by adding a mount options for the F2FS file system (in addition the the EXT4 file system mount option) to the fstab in the current kernel on your ghost.
ghost zip is for AOSP/CM based roms only!
MOTO 4.x.x is for KitKat Stock/Moto based roms only!
MOTO 5.x.x is for Lollipop Stock/Moto based roms only!
I used the information on HTC dev @jrior001's thread so I'll include some of the info he provided:
Original thread here: http://forum.xda-developers.com/htc-desire-hd/development/f2fs-acecm12-lp-aosp-t2995418
What is F2FS?
F2FS wiki
Why F2FS?
F2FS put to the test vs EXT4
Does it work?
Ghost already benefits (per Anandtech's post) from F2FS formated /data so there isn't going to be a massive difference in performance. However, my phone seems to be a little quicker/smoother FWIW.
Switch to F2FS cache file system:
1. Update to TWRP 2.8.x.x and boot into recovery.
2. Create a backup of your device (you can get away with a backup of /boot only).
3. Goto WIPE > ADVANCED WIPE.
4. Select CACHE > "REPAIR OR CHANGE FILE SYSTEM" > F2FS.
5. Flash the attached zip file.
6. Reboot.
Switching back to EXT4 cache file system:
1. Boot into recovery.
2. Goto WIPE > ADVANCED WIPE.
3. Select CACHE > "REPAIR OR CHANGE FILE SYSTEM" > EXT4.
4. Reboot.
Devs can add this to their builds by simply inserting the following line into fstab.qcom prior to building boot.img:
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs rw,nosuid,nodev,noatime,nodiratime,inline_xattr wait,check
Credit:
@jrior001
@infectedorganism (gave me the heads up to check fstab.qcom)
@tdhite (I used your zip file as a basis to create the flashable zip)
As always, I'm not responsible for any loss of data; always make a backup prior to messing around :laugh:
{
"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"
}
So did u notice any performance difference? CM12.1 is smooth and fast as it is so I can't imagine our baby might be even faster
Edit: OK I missed that part about a bit smoother etc I will give it a try though and report back
chaoslimits said:
I've seen a couple of requests for the F2FS file system support in some of the CM12.x based rom threads and did some googling on why anyone would want F2FS instead of EXT4. There are also reports, by Nexus 7 users, that converting to F2FS fixes their performance issues.
So after some learning/failing, I'm releasing this zip file that updates (theoretically) any CM12.x based kernel to add F2FS support for the /cache partition. This is not necessary for the /data partition as it has always been F2FS formated (stock Moto or CM roms) for ghost :good:
The modification works by adding a mount options for the F2FS file system (in addition the the EXT4 file system mount option) to the fstab in the current kernel on your ghost.
This is for CM12.1 (and possibly AOSP) based roms only.
I used the information on HTC dev @jrior001's thread so I'll include some of the info he provided:
Original thread here: http://forum.xda-developers.com/htc-desire-hd/development/f2fs-acecm12-lp-aosp-t2995418
What is F2FS?
F2FS wiki
Why F2FS?
F2FS put to the test vs EXT4
Does it work?
Ghost already benefits (per Anandtech's post) from F2FS formated /data so there isn't going to be a massive difference in performance. However, my phone seems to be a little quicker/smoother FWIW.
Switch to F2FS cache file system:
1. Update to TWRP 2.8.x.x and boot into recovery.
2. Create a backup of your device (you can get away with a backup of /boot only).
3. Goto WIPE > ADVANCED WIPE.
4. Select CACHE > "REPAIR OR CHANGE FILE SYSTEM" > F2FS.
5. Flash the attached zip file.
6. Reboot.
Switching back to EXT4 cache file system:
1. Boot into recovery.
2. Goto WIPE > ADVANCED WIPE.
3. Select CACHE > "REPAIR OR CHANGE FILE SYSTEM" > EXT4.
4. Reboot.
Devs can add this to their builds by simply inserting the following line into fstab.qcom prior to building boot.img:
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs rw,nosuid,nodev,noatime,nodiratime,inline_xattr wait,check
Credit:
@jrior001
@infectedorganism (gave me the heads up to check fstab.qcom)
@tdhite (I used your zip file as a basis to create the flashable zip)
As always, I'm not responsible for any loss of data; always make a backup prior to messing around :laugh:
View attachment 3399179 View attachment 3399180
Click to expand...
Click to collapse
Can I use this mod for stock Android 5.1 ?
md07 said:
Can I use this mod for stock Android 5.1 ?
Click to expand...
Click to collapse
This is for only Cm12.1 based rom or for aosp based roms
md07 said:
Can I use this mod for stock Android 5.1 ?
Click to expand...
Click to collapse
I doubt this will work for stock 5.1. Can you check /fstab.qcom and see if it mentions /cache partition?
Megatron007 said:
This is for only Cm12.1 based rom or for aosp based roms
Click to expand...
Click to collapse
Pretty sure it will work for your AOSP (looked at r6 build) and all motorola/msm8960dt-common tree based roms (unless there are some major changes to the kernel which prevents it from being rebuilt). :good:
where screenshots from?
I doubt this will work for stock 5.1.
Click to expand...
Click to collapse
not boot on stock 5.1
chaoslimits said:
I doubt this will work for stock 5.1. Can you check /fstab.qcom and see if it mentions /cache partition?
Pretty sure it will work for your AOSP (looked at r6 build) and all motorola/msm8960dt-common tree based roms (unless there are some major changes to the kernel which prevents it from being rebuilt). :good:
Click to expand...
Click to collapse
i flashed this mod for stock 5.1. Phone stucked at bootloader unlocked warning screen, and not boot.
md07 said:
i flashed this mod for stock 5.1. Phone stucked at bootloader unlocked warning screen, and not boot.
Click to expand...
Click to collapse
Restore "boot" from your nandroid. I stated that this was for CM/AOSP roms only
Zorge.R said:
where screenshots from?
not boot on stock 5.1
Click to expand...
Click to collapse
md07 said:
i flashed this mod for stock 5.1. Phone stucked at bootloader unlocked warning screen, and not boot.
Click to expand...
Click to collapse
I can't test since I'm not on stock, but the STOCK zip in the OP should boot stock moto firmwares 4.x.x or 5.x. Same instructions:
1. Nandroid
2. Flash zip
3. Change cache to F2FS in TWRP.
chaoslimits said:
I can't test since I'm not on stock, but the STOCK zip in the OP should boot stock moto firmwares 4.x.x or 5.x. Same instructions:
1. Nandroid
2. Flash zip
3. Change cache to F2FS in TWRP.
Click to expand...
Click to collapse
I downloaded the MOTO_5.x.x_F2FS_enable_v2.zip and placed it on my phone and followed your instructions and it seems like I am stuck, was there another zip?
mastarifla said:
I downloaded the MOTO_5.x.x_F2FS_enable_v2.zip and placed it on my phone and followed your instructions and it seems like I am stuck, was there another zip?
Click to expand...
Click to collapse
Where are you stuck? It'll take a while to boot as it has to optimize the apps on boot again. If it doesn't boot after a 5 or so minutes, go back to recovery and verify that the change to F2FS stuck. You can switch back to EXT4 and it'll boot.
At worse just restore "boot" from your nandroid.
chaoslimits said:
Where are you stuck? It'll take a while to boot as it has to optimize the apps on boot again. If it doesn't boot after a 5 or so minutes, go back to recovery and verify that the change to F2FS stuck. You can switch back to EXT4 and it'll boot.
At worse just restore "boot" from your nandroid.
Click to expand...
Click to collapse
I understand that it has to optimize apps, but it wasn't making it that far, it was stuck on the boot logo like other people have mentioned
I changed it back to EXT4 and restored the BOOT partition, and its back to normal
chaoslimits said:
Where are you stuck? It'll take a while to boot as it has to optimize the apps on boot again. If it doesn't boot after a 5 or so minutes, go back to recovery and verify that the change to F2FS stuck. You can switch back to EXT4 and it'll boot.
At worse just restore "boot" from your nandroid.
Click to expand...
Click to collapse
i tested V1 on AICP, worked good ! How about V2? you must test on stock before release
md07 said:
i tested V1 on AICP, worked good ! How about V2? you must test on stock before release
Click to expand...
Click to collapse
Not sure what you're saying. OP doesn't say it works on stock yet. I asked someone with stock, who was willing to test to try it. Also all V2 are for moto firmware not for CM or AOSP roms.
I'll load stock when I am able but TWRP flash logs would help me figure it out quicker. I'm 99% sure the boot.img isn't being rebuilt due to rramdisk name inconsistencies.
V2 also not worked with stock 5.1 . stuck at bootloader warning screen, not continue boot
md07 said:
V2 also not worked with stock 5.1 . stuck at bootloader warning screen, not continue boot
Click to expand...
Click to collapse
Thanks for getting back to me. Found a silly typo in the scripts. v3 should work for you. Can you test?
chaoslimits said:
Thanks for getting back to me. Found a silly typo in the scripts. v3 should work for you. Can you test?
Click to expand...
Click to collapse
Well well, finally, V3 worked on stock 5.1.
Tks for your hard work!
md07 said:
Well well, finally, V3 worked on stock 5.1.
Tks for your hard work!
Click to expand...
Click to collapse
Great! Please post if you notice any performance changes. I'm curious if it's a placebo or if there's real improvement
Confirm, v3 worked on stock 5.1, thanks for work!
I think in order for this to work on stock 5.1, the kernel has to support fsfs, which so far there aren't any custom kernel available on 5.1. It does however work on CM roms perfectly well although to be perfectly honest I don't see any difference except for the hassle of reformatting the cache partition back to ext4 everytime I want to flash stock.
Sent from my Moto X
It includes DRM patch and disabled force encryption.
Because fstab.qcom has been moved to system since 8.0, I cannot modify the boot image.
Some of you guys might have a problem with TWRP encryption password. With stock kernel, /data will be encrypted in a few boots even if you set no password.
About this kernel:
- Working camera (DRM-patch)
- Disabled dm-verity (so we can use magisk)
- Can mount /data in recovery (it means we can install magisk inside /data)
- Pass both safetynet
- You can still encrypt any time
- It will not decrypt your data. In other words, you have to do factory reset (wipe data) if it's already encrypted.
- See encryption status in Setting->Security
You can download from the attachments.
41.3.A.2.24
G8231 - View attachment xzs-p3-2.24.zip Based on Nordic Combined
G8232 Dual - View attachment xzsd-p3-2.24.zip Based on Customized TH
41.3.A.0.401
G8231 - Download from a thread by @Pandemic
G8232 Dual - View attachment xzsdp3.0.401-unzip.zip Based on Customized VN (for fingerprint)
Also, patch View attachment drmfix.zip before first system boot.
41.2.A.7.76
G8231 - View attachment xzs-p2.7.76.img.zip
G8232 Dual - View attachment xzsd-p2.7.76.img.zip
41.2.A.7.65
G8231 - View attachment xzs-p2.7.65-extract-first.zip
G8232 Dual - View attachment xzsd-p2.7.65-extract-first.zip
41.2.A.7.53
G8231 - View attachment 8231-boot753noencrypt.zip
G8232 Dual - View attachment boot-7.53-noforceencrypt.zip
It's not flashable zip, so please extract before use.
It will bootloop if you flash wrong version.
{
"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"
}
How to disable by yourself? - Not for Oreo
Prerequisite:
- 32-bit linux (you can use it on liveboot drive or VM)
It doesn't work on cygwin (windows) because of its native executable. So use linux 32 bit (i386), or 64 bit (amd64) with multiarch.
- Unpack using mkbootimg tool made by xiaolu (I tried kitchen and it won't work)
- Open fstab.qcom
- Replace "forceencrypet" with "encryptable"
- Pack again
- Done!
Thanks tobias.waldvogel and xiaolu for their awesome tools.
If you have any question, feel free to ask me or some nice guys here.
zlRampageSlz said:
Some of you guys might have a problem with TWRP encryption password. With stock kernel, /data will be encrypted in a few boots even if you set no password.
About this kernel:
- Working camera (DRM-patch)
- Disabled dm-verity (so we can use magisk)
- Can mount /data in recovery (it means we can install magisk inside /data)
- Pass both safetynet
- You can still encrypt any time
You can download from attachment.
View attachment 4246515
It's not flashable zip, so please extract it before use.
View attachment 4246527
How to disable by yourself?
Prerequisite:
- 32-bit linux (you can use it on liveboot drive or VM)
It doesn't work on cygwin (windows) because of its native executable. So use linux 32 bit (i386), or 64 bit (amd64) with multiarch.
- Unpack using mkbootimg tool made by xiaolu (I tried kitchen and it won't work)
- Open fstab.qcom
- Replace "forceencrypet" with "encryptable"
- Pack again
- Done!
Thanks tobias.waldvogel and xiaolu for their awesome tools.
If you have any question, feel free to ask me or some nice guys here.
Click to expand...
Click to collapse
i'd just like to ask a question.. are we gonna be able to have the tap2wake feature back? or it's just not possible...
Thank you! Can you recover?
谢谢！超逼真可以恢复吗？
In what order to I flash recovery, root and the kernel? (I've never used a kernel before)
Great, but you can just flash twrp-3.0.2-0-kagura.img instead of a newer version and it will work perfectly. For some reason the newer twrps for xz will ask for password to decrypt data
And can you make this for g231?
tapperyaus said:
In what order to I flash recovery, root and the kernel? (I've never used a kernel before)
Click to expand...
Click to collapse
You have to unlock bootloader first before you can flash anything. Then just "fastboot flash boot <thatkernel>.img" in fastboot (blue LED). Recovery and root is optional. Normally, you have to use TWRP recovery to flash zip (su installer).
So, unlock bootloader -> flash kernel -> flash recovery -> install su in TWRP
Also, you can read detailed my tutorial here.
HellFish23 said:
Great, but you can just flash twrp-3.0.2-0-kagura.img instead of a newer version and it will work perfectly. For some reason the newer twrps for xz will ask for password to decrypt data
And can you make this for g231?
Click to expand...
Click to collapse
When you use 3.0.2-0, does it work while being encrypted? Or you have to do a factory reset to prevent further encryption.
Sure, I'll make for you guys when I'm free.
I've added G8231 kernel in the attachments.
zlRampageSlz said:
When you use 3.0.2-0, does it work while being encrypted? Or you have to do a factory reset to prevent further encryption.
Sure, I'll make for you guys when I'm free.
Click to expand...
Click to collapse
I understood the issue was twrp saying is encrypted while you didn't encrypt it yourself, may have misunderstood but I didn't test it while I actually encrypt it myself. And thanks!
Everything is working fine for the kernel, I no longer get the green photos and I can download Super Mario Run (my go to Safetynet app), but when I try to boot into recovery to flash Magisk all I get is a black screen. I tried flashing another TWRP version and still get a black screen. I'm on the dual sim variant.
Even if this problem can't be fixed, thanks for the kernel!
tapperyaus said:
Everything is working fine for the kernel, I no longer get the green photos and I can download Super Mario Run (my go to Safetynet app), but when I try to boot into recovery to flash Magisk all I get is a black screen. I tried flashing another TWRP version and still get a black screen. I'm on the dual sim variant.
Even if this problem can't be fixed, thanks for the kernel!
Click to expand...
Click to collapse
Could you give me TWRP log while installing magisk? Try using uninstaller and wiping cache first. Then flash stock kernel before install magisk again.
zlRampageSlz said:
Could you give me TWRP log while installing magisk? Try using uninstaller and wiping cache first. Then flash stock kernel before install magisk again.
Click to expand...
Click to collapse
The problem wasn't installing magisk, it was that TWRP wasn't installing correctly. Attempting to reach TWRP leads to a black screen. It's easily avoidable by booting the twrp.img through adb/fastboot (then flashing magisk there), I just can't install TWRP onto the phone.
tapperyaus said:
The problem wasn't installing magisk, it was that TWRP wasn't installing correctly. Attempting to reach TWRP leads to a black screen. It's easily avoidable by booting the twrp.img through adb/fastboot (then flashing magisk there), I just can't install TWRP onto the phone.
Click to expand...
Click to collapse
Sorry I misunderstood your question, TWRP right now cannot boot in the normal way (from fastboot/adb, or even TWRP itself). You have to hold power+vol down at the same time.
zlRampageSlz said:
Sorry I misunderstood your question, TWRP right now cannot boot in the normal way (from fastboot/adb, or even TWRP itself). You have to hold power+vol down at the same time.
Click to expand...
Click to collapse
Why can't i enter the TWRP by hold power+vol down at the same time? The screen just turned between black and logo.
Thanks.
I found the problem is that i forgot to flash recovery
Hi, Does this kernel support DoubleTap2Wake?
Ok
AWESOMEE..
Xenroe said:
Hi, Does this kernel support DoubleTap2Wake?
Click to expand...
Click to collapse
Not yet, I'll look around if I have some time.
zlRampageSlz said:
Not yet, I'll look around if I have some time.
Click to expand...
Click to collapse
Thanks, i would've flashed XZ Kernel just so i can have DoubleTap2Wake if i could.. I'll be looking forward to your update...
This kernel is good, but I have a question: When I brush the kernel, I can't enter TWRP through the combination of the volume key and the power button. Instead, my phone switch between the logo and the black screen. Do I need to write a TWRP again?(My English is not good, please fogive me:crying
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
As we all know - the tablet does not support treble. And we do not have a separate /vendor partition, i'm using /cache as /vendor.
Instructions
1. flash my twrp from link above - this is latest twrp with system_image support, it need to restore system treble images
2. download system image from https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Known Issues
1. rotate sensor working, but strange - on rotate tablet show black screen for a moment and then back to normal in right state
2. SM-T580 only: gps
Links
Treble images
SM-T585:
1. 20180827: initial treble: https://drive.google.com/file/d/1uX5JYqLCTMPpT5Zx2Wvi0U-Ms49S0YrW/view?usp=sharing
2. 20180904: camera recording in oreo images, both sdcards in pie images: https://drive.google.com/file/d/1cTEXJb9n5oZad0O3DXT5nlEhnlBDP6QB/view?usp=sharing
3, 20180906: remove shim for mediaserver - only for pie!!!: https://drive.google.com/file/d/1C0MfHt0SNYL4hD-BtOj3i7O_qBBPD25t/view?usp=sharing
SM-T580:
1. 20180828: initial treble: https://drive.google.com/file/d/1sgB1xQjRWyGM1OfF73Yhl5vRNunP04iK/view?usp=sharing
2. 20180904: camera recording in oreo images, both sdcards in pie images: https://drive.google.com/file/d/13WL9_Q_WoStf0WVHbmoYaL2CHbCluzNO/view?usp=sharing
3, 20180906: remove shim for mediaserver - only for pie!!!: https://drive.google.com/file/d/15dN2DugPBjhi_m0SOy4qYwVmR03nyY69/view?usp=sharing
Root
Use Magisk, it's should work. If during install Magisk give error about missed /vendor, run my prepare script and the install Magisk: https://drive.google.com/file/d/10JnOtyF5Y_4q1OE3FOZYPDcR7TK1jRhA/view?usp=sharing
GApps - Pie only!!!
Right now on T580\T585 pie images with gapps dnw, it's stuck on the start wizard, what is strange.
Solution: flash image without gapps and then flash gapps. It's working. I'm playing right now with aosp 9.0 and gapps.
We have 32bit recovery and right now standalone gapps think about arm and 6.0.1 version, what is wrong. I took gapps from https://forum.xda-developers.com/android/development/gapps-unofficial-opengapps-builds-t3828141 and fix script inside to arm64 and right sdk version, this is gapps with my fix, what should work on T580\T585: https://drive.google.com/file/d/1kkHUPSznfibcER0DV89GhDdepEjqjCl9/view?usp=sharing
How install gapps:
1. install treble image, then pie system image
2. boot to system
3. restart to twrp and install gapps
4. boot to system, go to play market and login
For now working only this sequence
Recovery
SM-t585:
1. twrp-3.2.3-0: https://drive.google.com/file/d/16D-sFDt41n-wxNu1A0q01oRRKiZ-AsfF/view?usp=sharing
SM-T580:
1. this is original twrp (from https://dl.twrp.me/gtaxlwifi/twrp-3.2.3-0-gtaxlwifi.img.html), I just added system_image support and repack: https://drive.google.com/file/d/10LgZ1rabkgVSyIyd38BxIxNr22_9PJY5/view?usp=sharing
All firmware say about wrong vendor version. This is normal, just press OK.
System images:A only and 64Bits
Checked firmwares
Almost all oreo roms from treble's thread working.
Even new Android 9.0 Pie roms working, but it has issue with sdcard, it will require additional checks from me.
Installation
1. (optional): "Wipe\Format Data": type yes and press ok
{
"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"
}
2. wipe data: "Wipe\Advanced Wipe" and select "Dalvik/ARP Cache" / "Data" / "Internal Storage" / "System" / "Cache"
3. install treble: "Install", then navigate to lineage-15.1-20180827-treble.zip and "Swipe to confirm Flash"
4. install system: "Install", then press "Install Image" then navigate to system images, then select "System Image" and "Swipe to confirm Flash"
5. reboot
let's experiment together!
Valera1978 said:
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
As we all know - the tablet does not support treble. And we do not have a separate /vendor partition, i'm using /cache as /vendor.
Instructions
1. go to the current twrp and full wipe
2. flash my twrp - this is latest twrp with system_image support, it need to restore system treble images (twrp-3.2.3-0-gtaxlltexx.img): https://drive.google.com/file/d/16D-sFDt41n-wxNu1A0q01oRRKiZ-AsfF/view?usp=sharing
3. flash zip with vendor data and boot image (lineage-15.1-20180827-treble.zip): https://drive.google.com/file/d/1uX5JYqLCTMPpT5Zx2Wvi0U-Ms49S0YrW/view?usp=sharing
4. now you device is ready to flash any treble system image from: https://forum.xda-developers.com/project-treble/trebleenabled-device-development - download img, copy to sdcard and then flash as system image in twrp
5. if you wanna check another rom, just make 1-4 again
Known Issues
1. video-recording
2. rotate sensor working, but strange - on rotate tablet show black screen for a moment and then back to normal in right state
All firmware say about wrong vendor version. This is normal, just press OK.
System A only
Checked firmwares
Almost all oreo roms from treble's thread working.
Even new Android 9.0 Pie roms working, but it has issue with sdcard, it will require additional checks from me.
let's experiment together!
Click to expand...
Click to collapse
You are amazing dude thanks so much for releasing this to us. Keep up the great work.
Wow, can you Do the same for the WiFi Version SM-T580?
This is by far the best news for our device. I am wondering if when we'll get official Oreo, Samsung will provide us with a treble rom as well.
Thanks Valera for you support.
I get "No OS installed"
Wow. Good job, my friend! I already want to try it on T580 wifi version. I remember that the roms of t585 work in the wifi version, can you flash this without problems?
Many cravings
Thank you!
paulo boë said:
I get "No OS installed"
Click to expand...
Click to collapse
just ignore this error. look like twrp not quite correctly handle the situation with restore via system_image and think that there is no system.
alanloax said:
Wow. Good job, my friend! I already want to try it on T580 wifi version. I remember that the roms of t585 work in the wifi version, can you flash this without problems?
Many cravings
Thank you!
Click to expand...
Click to collapse
I can build version for t580, the kernel and almost all stuff is not a problem, question only in the gps. In the t585 it's connect to the ril, but t580 using own gps chip. I don't know, where I can get 64bit binary for it. In case of t585 i'm using proprietary bin\libs from a5'17. Need to check, can I use 32bit gps in 64bit system.
And may be can be a problems (not sure now) - all treble's images created for phones. tablet with lte is close to phone, but not a witi version. but in any way - it's need to check.
Valera1978 said:
I can build version for t580, the kernel and almost all stuff is not a problem, question only in the gps. In the t585 it's connect to the ril, but t580 using own gps chip. I don't know, where I can get 64bit binary for it. In case of t585 i'm using proprietary bin\libs from a5'17. Need to check, can I use 32bit gps in 64bit system.
And may be can be a problems (not sure now) - all treble's images created for phones. tablet with lte is close to phone, but not a witi version. but in any way - it's need to check.
Click to expand...
Click to collapse
Oh I understand. Luckily I use little the gps. At least to try haha.
Thank you very much again for contributing to these devices, very good work!
Valera1978 said:
just ignore this error. look like twrp not quite correctly handle the situation with restore via system_image and think that there is no system.
Click to expand...
Click to collapse
And still it reboots over and over. The Galaxy Tab logo, then 6 7 secs black screen and the the Galaxy tab logo again.
paulo boë said:
And still it reboots over and over. The Galaxy Tab logo, then 6 7 secs black screen and the the Galaxy tab logo again.
Click to expand...
Click to collapse
Did you flashed anything other than rom? Magisk, gapps?
EugenStanis said:
Did you flashed anything other than rom? Magisk, gapps?
Click to expand...
Click to collapse
Nope, but I kinda forgot to mention that I use it on the T580
Hey, very good job. Please make a 580 version, GPS doesn't matter. You said it was experimental.
paulo boë said:
Nope, but I kinda forgot to mention that I use it on the T580
Click to expand...
Click to collapse
It's cannt work on T580 right now, because treble require changes in DTB. Without DTB changes system cann't mount /cache as /vendor and you will get boot before animation.
Will try build T580 today.
Please someone check version for T580
Valera1978 said:
Please someone check version for T580
Click to expand...
Click to collapse
And the twrp for t580? Cuz when I flash I get "this is for wifi this is lte"
Also can you post some screenshots with a link to the treble rom that works?
paulo boë said:
And the twrp for t580? Cuz when I flash I get "this is for wifi this is lte"
Click to expand...
Click to collapse
are your right now on twrp for lte? In this case in the gtaxlwifi-20180828-treble.zip - go to "\META-INF\com\google\android\updater-script" and remove first line with assert
Or you can use my twrp repack for t580: https://drive.google.com/file/d/10LgZ1rabkgVSyIyd38BxIxNr22_9PJY5/view?usp=sharing
this is original 3.23 version, I added only system-image
Valera1978 said:
are your right now on twrp for lte? In this case in the gtaxlwifi-20180828-treble.zip - go to "\META-INF\com\google\android\updater-script" and remove first line with assert
Or you can use my twrp repack for t580: https://drive.google.com/file/d/10LgZ1rabkgVSyIyd38BxIxNr22_9PJY5/view?usp=sharing
this is original 3.23 version, I added only system-image
Click to expand...
Click to collapse
I flashed it. Tried to flash a img, but still reboots back into galaxy logo
paulo boë said:
I flashed it. Tried to flash a img, but still reboots back into galaxy logo
Click to expand...
Click to collapse
can you send me /data/tombstones and /proc/last_kmsg?
SM-T285YD
Hi,
I have twrp for SM-T285YD but I cannot find any rom for my SM-T285YD. So can I flash this rom in my SM-T285YD.
If not then tell me what I need to do to get it working in my SM-T285YD and also I have the twrp but tell me how can make my twrp treble supported twrp....
Best regards....
xXx NoLimits ☆ Magisk TWRP Installer- SM-N986B Exynos ☆
{
"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"
}
☆ Magisk TWRP Installer ☆
This is originaly a Magisk TWRP Installer made by xXx for OnePlus 8 Pro.
I just took and modified it to get it work on our Samsung Galaxy Note 20 5G Ultra.
Our Dr.Ketan helped me to fix the TWRP Installer with the path of the recovery partiton.
1. Before using this Installer you must need following!!!!...... else it wont work:
- Root your device like Dr.Ketan mentioned in his Root thread!!! --> [Guide] How to root N20 Ultra (N986B)(N9860)
2. How you can use this TWRP Installer?
- Download the Magisk TWRP Installer from post 2
- Just open Magisk -> Go to Modules -> Press Install from storage -> Choose the TWRP Installer -> Flash and press Reboot
Congratulation now you flashed TWRP made by ianmacd
3. How to update the Magisk TWRP Installer?
-Download the latest TWRP from Ian and swap only the .img file inside the .zip and repeat point 2.
Credits
@xXx ; @Dr.Ketan ; @ianmacd
Source from TWRP made by Ian:
https://github.com/ianmacd/twrp_c2s
Telegram Group:
Be my guest at Samsung Galaxy Note 20 / 20 Ultra
☆ Downloads ☆
Android 11
TWRP_3_5_0_10-A11_6_ianmacd_xXx-Installer_N986B_SGN_20_5G_Ultra.zip
TWRP_3_5_0_10-A11_1_ianmacd_xXx-Installer_N986B_SGN_20_5G_Ultra.zip
Android 10
TWRP_3_4_0_1a23_ianmacd_xXx-Installer_N986B_SGN_20_5G_Ultra.zip
TWRP_3_4_0_1a20_ianmacd_xXx-Installer_N986B_SGN_20_5G_Ultra.zip
TWRP_3_4_0_1a19_ianmacd_xXx-Installer_N986B_SGN_20_5G_Ultra.zip
TWRP_3_4_0_1a18_ianmacd_xXx-Installer_N986B_SGN_20_5G_Ultra.zip
TWRP_3_4_0_1a16_ianmacd_xXx-Installer_N986B_SGN_20_5G_Ultra.zip
reserved..........
I do have the TWRP already installed that I got from the the main thread : https://forum.xda-developers.com/galaxy-note-20-ultra/development/recovery-twrp-galaxy-note-20-note-20-t4152335.
Can I just install this Magisk TWRP module to override the current TWRP ?
nawaf2816 said:
I do have the TWRP already installed that I got from the the main thread : https://forum.xda-developers.com/ga...ecovery-twrp-galaxy-note-20-note-20-t4152335.
Can I just install this Magisk TWRP module to override the current TWRP ?
Click to expand...
Click to collapse
Exactly for that purpose it is made my friend ?
Let us know the result
xenix96 said:
Exactly for that purpose it is made my friend
Let us know the result
Click to expand...
Click to collapse
I have successfully installed it and installation was very quick & smooth! :good:
I will keep monitoring for any issue may arises , hopefully non ..
Thank you dude, Good work !
Good job :good:
The backup/restore function doesn't seem to work . Which is expected .. as i haven't got any working nand backup since the time of old devices ..
I wonder if any one got any successful backup either full or partial for some parts .. ?
I'm using a stock rooted ROM with lite magisk module to enable some CSC features .
What I'm looking for is the ability to restore the system (mainly boot portion) to get back the phone booting if any improper installation of a module or app affected the device to boot normally !
Many function doesnt work in this moment.And recovery have problem with reboot from recovery to system and others problem.
Stock rooted ROM the best for now.
nawaf2816 said:
The backup/restore function doesn't seem to work . Which is expected .. as i haven't got any working nand backup since the time of old devices ..
I wonder if any one got any successful backup either full or partial for some parts .. ?
I'm using a stock rooted ROM with lite magisk module to enable some CSC features .
What I'm looking for is the ability to restore the system (mainly boot portion) to get back the phone booting if any improper installation of a module or app affected the device to boot normally !
Click to expand...
Click to collapse
Vitalik666teen said:
Many function doesnt work in this moment.And recovery have problem with reboot from recovery to system and others problem.
Stock rooted ROM the best for now.
Click to expand...
Click to collapse
I hope our devs can manage to solve the issues in the twrps.
For flashing roms, kernel, magisk, twrp etc it is working at the moment
can i install this TWRP on device N981B
tnx
usitaly said:
can i install this TWRP on device N981B
tnx
Click to expand...
Click to collapse
This recovery is only for N986B.
Sorry mate
Oh what the hell.
I tried that on my one plus 8 pro when I had it.
Can you do snapdragon as well?
When will the system recovery partition be supported. In TWRP ??
Uploaded new ianmcd a18 TWRP in post #2
If you get bootloop dirty reflash your custom rom -> worked for me :good:
What is the way to flash I use the old version
Is mtp fixed in this version?
songoku1 said:
Is mtp fixed in this version?
Click to expand...
Click to collapse
Good question.
I didnt test it cause i use the sd card which is working great.
Let us know if you want test and have a result ?
xenix96 said:
Uploaded new ianmcd a18 TWRP in post #2
If you get bootloop dirty reflash your custom rom -> worked for me :good:
Click to expand...
Click to collapse
Where can I find this telegram channel?
Uploaded new ianmcd a19 TWRP in post #2
Just flashed over Magisk without a issue :good::good::good::good::good:
Changelog:
Samsung TWRP unofficial build announcements
(Ian Macdonald)
The following alpha 19 releases for devices launched with Android 10 have, in addition to the latest round of TWRP fixes, a couple of new features:
* When using the file manager, it is now possible to open a terminal in the currently selected folder. This currently works only on devices with TWRP in portrait orientation.
* logd now runs in recovery, so adb logcat will now work when the device is booted to TWRP.
I own Nothing of the contents i will provide below but i wanted to share with you This Amazing ROM that became Available to Our Device thanks to Iceows, DarkJoker360, Hamido and DotOS Team that made the GSI available. So make Sure to give proper Credits whenever you Publish this Method.
{
"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"
}
Requirements :
- Unlocked Bootloader
- Darkjoker360's Twrp prague A11 edition : LINK
- Stock Emui Rom version below 400 for Rne-L21( For other variants i haven't tested yet which version you must have, but ofc don't be on the latest ones ).
- Patience.
- Follow my Steps.
What's working :
- Everything if you install all the fixes.
What's not working :
- Something probably you only have found about.
To Begin i recommend you download :
1- dotOS-R-v5.2-arm64-ab-vndklite-GAPPS-OFFICIAL.img.xz (none of the A-only builds worked for us so don't waste your time) and must be vndklite (IMPORTANT) : LINK
2- all the necessary 6 fixes from Iceows Sourceforge in this LINK
3- Hamidos Patch 1 and 2 to convert ab to a only. LINK I will add the patch 1 and 2 in the attachements.
Also your data have to be decrypted before installing this Rom (ignore this step if you have done this before), to do so download the decrypt zip file from this link and put it in your microSD directory : LINK
- Extract dotOS-R-v5.2-arm64-ab-vndklite-GAPPS-OFFICIAL.img.xz to your microsSD so you will obtain : dotOS-R-v5.2-arm64-ab-vndklite-GAPPS-OFFICIAL.img
- Put The 6 fixes Zips + hamido Patch 1 and 2 in your sdcard (Fixes exist in Iceows Sourceforge in the link provided previously).
So now you have these files in your MicroSD :
* dotOS-R-v5.2-arm64-ab-vndklite-GAPPS-OFFICIAL.img.
* Huawei-Decrypt-Emui_8.zip
* MakeHi6250-Iceows-v0.2-signed.zip
* AGPS-FIX-AltairVendor-v3.3-signed.zip
* NFC-FIX-Altair-v1.6-signed.zip
* DisplayEngine-FIX-Altair-v0.3-signed.zip
* LibAptx-FIX-Altair-v0.1-signed.zip
* Media-FIX-Altair-v0.1-signed.zip
* Patch1.zip
* Patch2.zip
Now Follow these easy Steps :
=============================
1) Format Data
Reboot to recovery TWRP and perform these steps
Code:
- Wipe > Format Data
then
Code:
- Reboot > Recovery
- Wipe Data
============================
2) Now in TWRP again, perform these steps:
Code:
- Wipe > Advanced Wipe :
Select only these partitions
[x] Dalvik / ART Cache
[x] Cache
[x] Data
[x] System
Swipe to format
============================
3) Install EMUI 8 decrypt file (not needed if you are already decrypted your data, move to step 4)
I previously put the zip file on my MicroSD, so:
Code:
- Install > Huawei-Decrypt-Emui_8.zip
Code:
Reboot > Recovery
============================
4) Install the system
Still in TWRP do:
Code:
- Reboot > Recovery
- Install > Install Image > Pick from your Micro SDcard "dotOS-R-v5.2-arm64-ab-vndklite-GAPPS-OFFICIAL.img" > flash it as system image (Warning not System only).
- Install zip > Flash Patch 1 then flash Patch 2
- Install zip > Flash the 6 fixes One by One.
============================
5) Resize the file system
After flashing the image reboot in TWRP by pressing back until you get to TWRP main screen then
Code :
- Reboot > Recovery
once rebooted again to twrp
- Wipe > Advanced Wipe > pick System Partition > Repair or change file system > Resize File System
============================
Code:
Reboot > System
===========================
6) ENJOY!
I followed your guide and managed to finally install a custom rom for my phone after years, it works well and I really thank you for sharing this! but i'm not sure how to root it. i tried to install magisk and supersu through TWRP but neither worked, I dont know what i did wrong.
Mastershaff said:
i tried to install magisk and supersu through TWRP but neither worked, I dont know what i did wrong.
Click to expand...
Click to collapse
Try the following:
1. Magisk root - first flash in TWRP M-Mount-Fix-11 , reboot into TWRP and flash Magisk.zip .
2. Superuser root - in TWRP flash
Phh-superuser-aonly , and install superuser appk download .
Maybe it will help you.
-Alf- said:
Try the following:
1. Magisk root - first flash in TWRP M-Mount-Fix-11 , reboot into TWRP and flash Magisk.zip .
2. Superuser root - in TWRP flash
Phh-superuser-aonly , and install superuser appk download .
Maybe it will help you.
Click to expand...
Click to collapse
Installing Superuser root worked. Thank you!
Mastershaff said:
Installing Superuser root worked. Thank you!
Click to expand...
Click to collapse
No problem.
Can you please suggest me which gapps works perfectly?? I’ve installed Opengapps nano but it doesn’t seem perfect to me because Chrome is getting crashed everytime I visit a website. Some apps can’t use location even though it’s allowed to use the location, like Chrome, Foodpanda.
Google Map works fine.
Messenger bubble isn’t working.
Also can you help me attaching the file “Media-FIX-Altair-v0.1-signed.zip” here?? The download link on sourceforge isn’t working.
Salekin_Limon said:
which
Click to expand...
Click to collapse
On dotOS try MindTheGapps, more stable when they launched. OpenGapps had some issues.
Or NikGapps basic. (you have to flash gapps before booting up the ROM!)
Salekin_Limon said:
Chrome is getting crashed
Click to expand...
Click to collapse
Try to update System Webview. Also you can try Chrome Beta :
guide
P.S.: In general, dotOS is the least suitable treble ROM for kirin devices, imo.
-Alf- said:
On dotOS try MindTheGapps, more stable when they launched
Click to expand...
Click to collapse
I tried, it was not installed saying that this package was for android 11 and it was not compatible with my android sdk, even though the package was MindTheGapps-11.0.0-arm64
-Alf- said:
Try to update System Webview. Also you can try Chrome Beta :
guide
Click to expand...
Click to collapse
Updated the System Webview, and followed the instructions after installing Chrome beta. It didn’t work for me. Even all the browsers (EDGE, Brave Browser) I installed, had the same issue except the system installed browser.
Flash dotOS gapps variant, it should work, imo...
-Alf- said:
Flash dotOS gapps variant, it should work, imo...
Click to expand...
Click to collapse
Many thanks. Everything is working really fine except for some apps.
Google Chrome issue remained unsolved.
Salekin_Limon said:
Google Chrome issue remained unsolved
Click to expand...
Click to collapse
Try Thor, Via or Dolphin
https://forum.xda-developers.com/t/...plus-a11-gsi-unofficial.4298551/post-86104931
Anyone manage to get VoLTE working ?
And there are 3 more files showing up in the sourceforge download link so shall I install those as well ?
The first file says 0-BigPatch-Altair-v0.1-signed.zip
And second one is 7 - VoLTE-FIX-A11-Altair-V1.4-signed.zip
The 3rd is VoLTE-FIX-A11-NoT-V1.5-signed.zip
Razr1804 said:
VoLTE working
Click to expand...
Click to collapse
On emui 8 try the following:
https://forum.xda-developers.com/t/...-0-9-with-working-volte.4356215/post-85877725
-Alf- said:
On emui 8 try the following:
https://forum.xda-developers.com/t/...-0-9-with-working-volte.4356215/post-85877725
Click to expand...
Click to collapse
I tried this method all day and I managed to boot it up but no luck with volte, The call seems to dial (and reaches the other end) but the calling screen shows that the 'call is ended', I even tried applying magisk fix as well as the zip provided for volte still no luck.
One more thing the TWRP seems to be stuck on Darkjoker360'sTWRP Prague A11 edition.
I tried it with Huawei Mate 10 Lite RNE-L01. Everything works fine but NFC doesn't work. Is there any solution?
teknolojiazmani said:
I tried it with Huawei Mate 10 Lite RNE-L01. Everything works fine but NFC doesn't work. Is there any solution?
Click to expand...
Click to collapse
NFC...Mate 10 lite...