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.
Notes
The idea of this project treble is to separate the device-dependent part and the system.
The project treble requires a separate /vendor partition for device-dependent part. But unfortunately we do not have it. But we have a /cache partition, which takes about 200mb and there is a /hidden partition, which takes 50-60mb. 200mb is not enough for us, our vendor is about 450mb.
In the first edition I maded for the 825 tablet, I implement an original solution using separate files for the system and the vendor. But this solution was very difficult to understand. Now my good friend @bonuzzz suggested an idea to me using a compressed partition (squashfs with lz4 compression). With this method, our vendor takes 190-195mb and it is possible to write it to the /cache partition. And use the /hidden partition as a /cache.
Now the installation has become much easier, almost like installing the usual lineage.
Installation
1. install twrp version with treble support (this is my special twrp, based on 9.0 with my latest caf kernel with squashfs support)
2. download treble zip and flash it as usual zip. It will flash boot.img and /vendor partition (in /cache)
3. download any treble system (64bit System A-only) image from: https://forum.xda-developers.com/project-treble
extract, you should get .img file, then copy to sdcard/extsd card and then flash image as system_image in twrp (Install - switch to Install Image and flash as System Image)
4. if you wanna back to stock firmware or lineage - you need flash normal twrp version and make full wipe or just flash stock firmware via odin
Links
Firmware
[SM-T820]
1. 20190404: https://drive.google.com/file/d/1hOPdO9UajY7AlJ5lE859Tr6Y7sEpwhTf/view?usp=sharing
[SM-T825]
1. 20190408: https://drive.google.com/file/d/1DokV37D8f2s9OtoAJTCURfdx88tNW788/view?usp=sharing
TWRP
[SM-T820]
1. 20190404: https://drive.google.com/file/d/1gJ50Sg75Vh7PKyiWfejiCPSD0SYCL5p2/view?usp=sharing
[SM-T825]
1. 20190408: https://drive.google.com/file/d/1x_MKQ1PDM6eEbSPsDyFk0DABjXnZfyB4/view?usp=sharing
System images
You can use almost any system image from https://forum.xda-developers.com/project-treble
Our version is: arm64 and a-only image
Magisk
You should use only latest 19.0 beta version from: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Do not use 18.1 or early version - it's dnw, it will corrupt firmware or may be even corrupt recovery (need flash recovery again via odin)
Almost all firmware say about wrong vendor version. This is normal, just press OK.
let's experiment together!
Version for SM-T825 hope will come soon too. I have some ril issues.
Update boot.img
Wow! Thank you for the amazing work. I seriously can't believe no one hasn't gone crazy over this already.
How would I go about adding some libraries to my /vendor partiton now? I want to try a Samsung OneUI GSI image on my tablet but it requires additional libraries.
The files I want to add are in here: https://mega.nz/#!oi52TSTY!2Qy3WU7DjVmafs4zENPF6dlOsbY06JG5NuvsNeDTRn4
How did you build this file in the first place?
EDIT: I noticed that video playback does not work. I see the video starts to buffer, then some ghosting appears, and finally the app crashes (both YouTube and Vimeo). Also, camera apps seem to crash.
cephasara said:
EDIT: I noticed that video playback does not work. I see the video starts to buffer, then some ghosting appears, and finally the app crashes (both YouTube and Vimeo). Also, camera apps seem to crash.
Click to expand...
Click to collapse
With me, YouTube and YouTube Vanced I run without problems and also the camera app works (only the switching times to the front cam take some time).
GSIs
rainman74 said:
With me, YouTube and YouTube Vanced I run without problems and also the camera app works (only the switching times to the front cam take some time).
Click to expand...
Click to collapse
Maybe my /hidden & /cache partitions got corrupt somehow. I tried several GSIs and had the same issue. Thanks for confirming though.
Have you tried an GSIs from non AOSP-based images? Like OneUI or Xperia? I had trouble with those.
rainman74 said:
With me, YouTube and YouTube Vanced I run without problems and also the camera app works (only the switching times to the front cam take some time).
Click to expand...
Click to collapse
Could you let us know which treble rom you used, as I have the same issues with video playback on youtube.
I also want to throw out there I was on the Nougat bootloader when I tried this and had video playback issues. I have not tried it out on Oreo. I would imagine that could make a big difference.
deleted (it sucks none of the sensors function properly)
just installed RR but i think gps not working
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
This is great!
Hey everyone, this project is big news! I am so happy that we can use Treble GSI, using the cache partition via squashfs is a really elegant way for this.
Almost everything works on my T820! I am using Phh-Treble AOSP 9.0 v112, MindTheGapps and Magisk. Even adoptable storage works, I have 256GB for internal storage now (it displays as 256/512 used when empty, but whatever).
The device is certified with magisk and custom prop value.
Contrary to the old Lineage OS from last year, there is no crazy wifi jitter, so Steam Link just works fine. I did not try out the recent Lineage 20190331, so I don't know if it was due to Lineage.
The rotation sensors are not working, for now I am using "Rotation Quick Setting" app from Play Store. Also, the camera app crashes, but I am not using it anyway.
Thank you so much @bonuzzz and @Valera1978 for making this possible! It is stable enough for daily use for me.
BTW, I came from Oreo bootloader, and have no problems regarding video playback (but I use MX Player, not stock)
Mhh.. I get constantly soft reboots if i try to install third party apps or restore my titanium backup on Havoc for treble. Fingerprint is also not working. Seems to be very unstable...
How could I go about adding files to this treblized /vendor partition? Presumably through the zip? If this is the case, how could I do that?
Fair warning to those wanting to try this: treble roms do install and run, but sensor support appears to be lacking. I can't get any input from gps, accelerometer, gyro, or light sensor.
@Valera1978 If anybody has any idea on how to add support for these to the (I'm assuming) vendor partition, I'd love any hint or direction.
usb otg not working
alegru said:
Hey everyone, this project is big news! I am so happy that we can use Treble GSI, using the cache partition via squashfs is a really elegant way for this.
Almost everything works on my T820! I am using Phh-Treble AOSP 9.0 v112, MindTheGapps and Magisk. Even adoptable storage works, I have 256GB for internal storage now (it displays as 256/512 used when empty, but whatever).
The device is certified with magisk and custom prop value.
Contrary to the old Lineage OS from last year, there is no crazy wifi jitter, so Steam Link just works fine. I did not try out the recent Lineage 20190331, so I don't know if it was due to Lineage.
The rotation sensors are not working, for now I am using "Rotation Quick Setting" app from Play Store. Also, the camera app crashes, but I am not using it anyway.
Thank you so much @bonuzzz and @Valera1978 for making this possible! It is stable enough for daily use for me.
BTW, I came from Oreo bootloader, and have no problems regarding video playback (but I use MX Player, not stock)
Click to expand...
Click to collapse
Does Netflix work?
I get a bootloop after installing image and reboot to system. I have followed the instructions and got an error "Updater process ended with ERROR:7" installing the treble-16.0.zip. I flashed the custom TWRP using odin and using stock Pie. Did I do something wrong?
Hey all. Flashed all the relevant files in the relevant order and currently have a tablet sitting on the Tab S3 splash screen. How long does this normally take?
I flashed the custom TWRP,
Rebooted into Recovery,
Flashed the Treble .zip file,
Rebooted into Recovery,
Flashed the latest Havoc OS, then Magisk v20.3
then rebooted and it's stuck here.
Strange thing is, Windows has flashed up saying that it is "setting up Samsung_Android" while it's on the splash screen.
I come from the tweaked T825 ROM.
Anyone else had this issue? Should I have flashed stock first?
ianrobbie said:
Hey all. Flashed all the relevant files in the relevant order and currently have a tablet sitting on the Tab S3 splash screen. How long does this normally take?
I flashed the custom TWRP,
Rebooted into Recovery,
Flashed the Treble .zip file,
Rebooted into Recovery,
Flashed the latest Havoc OS, then Magisk v20.3
then rebooted and it's stuck here.
Strange thing is, Windows has flashed up saying that it is "setting up Samsung_Android" while it's on the splash screen.
I come from the tweaked T825 ROM.
Anyone else had this issue? Should I have flashed stock first?
Click to expand...
Click to collapse
Well I've hard-bricked my tab by flashing the Treble zip so consider yourself lucky. I think you should flash ODIN stock and start from scratch. Flash ashyx's TWRP, follow the instructions there. DO NOT FLASH MAGISK. Then flash Treble TWRP, flash zip, reboot recovery, DO A WIPE DATA / FACTORY RESET, NOT FORMAT, Then flash Havoc OS a only or whatever. After that wipe cache/dalvik and let it boot to ROM, AND THEN flash magisk and stuff.
I hard bricked my tab because Magisk was installed on the device while I flashed Treble. So yeah DON'T DO THAT EITHER
By the way im so sorry for being 2 months late i saw this just now
Looking dangerous. I'd like to try it but uncertain procedures
NullCode said:
Well I've hard-bricked my tab by flashing the Treble zip so consider yourself lucky. I think you should flash ODIN stock and start from scratch. Flash ashyx's TWRP, follow the instructions there. DO NOT FLASH MAGISK. Then flash Treble TWRP, flash zip, reboot recovery, DO A WIPE DATA / FACTORY RESET, NOT FORMAT, Then flash Havoc OS a only or whatever. After that wipe cache/dalvik and let it boot to ROM, AND THEN flash magisk and stuff.
I hard bricked my tab because Magisk was installed on the device while I flashed Treble. So yeah DON'T DO THAT EITHER
By the way im so sorry for being 2 months late i saw this just now
Click to expand...
Click to collapse
would some of the issues seen by others be fixed if one started with non-rooted stock 9.0 and 9.0 bootloader (if it is different from that for Oreo)? thanks anyone
Related
Unofficial TWRP for Moto G5S Plus (Sanders)
Additional Features over Official TWRP:
Supports flashing of both 32bit and 64bit ROMs and Kernels.
OREO Images/ROMs support.
Decryption and Encryption support.
No SuperSU by default.
No TWRP app.
No HTC Dumlock cruft.
Updated pigz compressor (slightly faster and more tolerant of corruption).
NTFS support(Both Read and Write).
Covers more partitions for nandroid backup (OEM, FSG and FSC).
Experimental support for SD cards that are partitioned for partial adopted storage and partial removable storage.
Faster I/O performance.
Fixed Gapps/aroma freeze issues.
IMPORTANT!!! : READ INSTRUCTIONS CAREFULLY BEFORE PROCEEDING TO FLASHING PROCESS..!!
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either Magisk or flash any of the verity disabler zips available on xda.
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Flashing Instructions:
Using Existing TWRP:
Reboot to recovery > Click on Install > Install Image > recovery > select recovery image and flash > reboot to recovery
Other Methods(Fastboot) :
Make sure you have unlocked bootloader
Reboot to bootloader
Enter following command in terminal: fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary boot)
Incase your device is encrypted (while coming from stock rom), Follow these steps to decrypt:
Reboot to recovery > cancel the password prompt > mount all partitions > Format Data/Userdata (on f2fs) > Reboot Recovery > Mount all partitions again > Flash Magisk > Reboot
Now you are free to use Stock ROM (Decrypted) or Flash any custom rom you want.
Download Links: https://www.androidfilehost.com/?w=files&flid=216298
TWRP Themes: Check 3rd post
Known Issues: None || Report if you find any.
XDA:DevDB Information
[RECOVERY][UNOFFICIAL][Sanders] TWRP-3.2.1-r20 (64bit Supported!), Tool/Utility for the Moto G5S Plus
Contributors
CheckYourScreen
Source Code: https://github.com/CheckYourScreen/twrp_device_motorola_sanders
Version Information
Status: Stable
Current Stable Version: r20
Stable Release Date: 2018-04-04
Created 2017-10-26
Last Updated 2018-04-04
|| Changelog ||
r20:
Fixed Encryption support on custom roms.
Updated kernel
Updated build fingerprint for latest bootloader support.
Reverted pigz changes.
Switched back to original twrp themes. (TWRP Themes can be found in 3rd post )
Various bug fixes and improvements.
r16:
Fixed compatibility with New Bootloader (C2.07-December patch)
Merged october patches in kernel.
Various twrp upstream patches and fixes.
Fixed remote wipe process (Earlier remote wipe issued from play account wasnt processed due to twrp)
r15:
Added 64bit Support (You can flash both 32bit/64bit roms or kernels with it).
Fixed Encryption Support! (No need to format data to decrypt and mount).
Updated to 3.2.1 upstream changes with full oreo support.
Remove android reboot during password check on multiple wrong inputs.
r9:
Fixed F2FS mount issues(You can flash magisk modules or SuperSu now).
Enabled NTFS Write Support (You can make backups on sdcard/pendrives formatted on NTFS).
Fixed size of various partitions.
Switched to LZMA compression to decrease size.
r7: Initial Public Release
|| Themes ||
Here are some of the twrp themes:
Preview images: https://photos.app.goo.gl/DLrfDseGzfxE8Uq93
Download link: https://androidfilehost.com/?w=files&flid=233551
:good:
Only one that has actually be working for me ever since I got the phone. Thank you for your efforts.
this seems to suffer from the same thing the stock rom/kernel suffers from, the weird f2fs bug that makes certain mounts fail. geneticengineer has shared a kernel that fixes this in stock rom , maybe you could get in touch with him about how he updated f2fs
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
revengineer said:
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
Click to expand...
Click to collapse
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Schrotty35 said:
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Click to expand...
Click to collapse
Well my guess is that the kernel in the present twrp is from the -26 firmware posted in the other thread. That firmware was US Retail also. The OP in the other thread states in can be used on other models. But I am not going to tell you that because I do not know. I have not found any other firmware for the sanders model.
Ae3NerdGod said:
this seems to suffer from the same thing the stock rom/kernel suffers from, the weird f2fs bug that makes certain mounts fail. geneticengineer has shared a kernel that fixes this in stock rom , maybe you could get in touch with him about how he updated f2fs
Click to expand...
Click to collapse
Afaik it doesnt affect TWRP, you just need to be on a custom kernel if you are running stock rom.
Twrp has nothing to do with it.
If you face any problem flashing anything then post a screenshot or log.
revengineer said:
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
Click to expand...
Click to collapse
Schrotty35 said:
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Click to expand...
Click to collapse
Stock kernel is same in both the firmwares.
-45 is just for US variant, i dont recommend you to even flash that firmware on other variants.
CheckYourScreen said:
Afaik it doesnt affect TWRP, you just need to be on a custom kernel if you are running stock rom.
Twrp has nothing to do with it.
If you face any problem flashing anything then post a screenshot or log.
Click to expand...
Click to collapse
but i have a custom stock kernel, and things that fail in TWRP work in flashfire or magiskmanager
its mostly magisk modules im having problems with, ill reproduce an error when i get the chance
Ae3NerdGod said:
but i have a custom stock kernel, and things that fail in TWRP work in flashfire or magiskmanager
its mostly magisk modules im having problems with, ill reproduce an error when i get the chance
Click to expand...
Click to collapse
Flash the magisk module via twrp > take screenshot when flashing completes > go to advance section of twrp and take recovery log > reboot system > send that screenshot and recovery log here.
CheckYourScreen said:
Flash the magisk module via twrp > take screenshot when flashing completes > go to advance section of twrp and take recovery log > reboot system > send that screenshot and recovery log here.
Click to expand...
Click to collapse
will do, it happens with every magisk package i try. they used to fail in stock too till i used geneticengineers kernel from telegram now they work
didnt know you could screenshot in recovery, i assume its the same buttons
Ae3NerdGod said:
will do, it happens with every magisk package i try. they used to fail in stock too till i used geneticengineers kernel from telegram now they work
didnt know you could screenshot in recovery, i assume its the same buttons
Click to expand...
Click to collapse
Yes, same buttons to take a screenshot in TWRP
TWRP backup is frozen at 13% completed. The progress bar is still showing its animation.
I unlocked the bootloader, and then rebooted. Android came up with the language selection screen. I powered off, connected the phone to the PC, and booted into TWRP (not flashed yet):
Code:
fastboot boot twrp-3.1.1-sanders-r7.img
I did not let TWRP format /data.
Then I started a backup, selecting all partitions, so that I could always go back after flashing TWRP and Magisk.
Does anyone know why backup is stuck at 13%? Last log line says "Backing up System..."
I tapped "Cancel" after two hours. That stopped the progress bar animation, but not the backup itself.
BTW: I used TWRP from this thread, the one in another thread freezes at the TWRP boot logo.
Edit: after two hours I killed the backup by powering down (the only way it seemed). On retry it froze at 21%.
Edit 2: Retried, this time backing up everything except system. No problem. I then tried to backup system. Frozen at 1%. What is the problem here?
Edit 3: Finally, a complete backup of system! Only one to go: system_image. But unfortunately that froze at 0%. Every subsequent try freezes at 1666MB (40%). The card has over 30GB free. I tried backup to USB-OTG, but that also froze.
gewe said:
TWRP backup is frozen at 13% completed. The progress bar is still showing its animation.
I unlocked the bootloader, and then rebooted. Android came up with the language selection screen. I powered off, connected the phone to the PC, and booted into TWRP (not flashed yet):
Code:
fastboot boot twrp-3.1.1-sanders-r7.img
I did not let TWRP format /data.
Then I started a backup, selecting all partitions, so that I could always go back after flashing TWRP and Magisk.
Does anyone know why backup is stuck at 13%? Last log line says "Backing up System..."
I tapped "Cancel" after two hours. That stopped the progress bar animation, but not the backup itself.
BTW: I used TWRP from this thread, the one in another thread freezes at the TWRP boot logo.
Edit: after two hours I killed the backup by powering down (the only way it seemed). On retry it froze at 21%.
Edit 2: Retried, this time backing up everything except system. No problem. I then tried to backup system. Frozen at 1%. What is the problem here?
Edit 3: Finally, a complete backup of system! Only one to go: system_image. But unfortunately that froze at 0%. Every subsequent try freezes at 1666MB (40%). The card has over 30GB free. I tried backup to USB-OTG, but that also froze.
Click to expand...
Click to collapse
Might be due to data partition being encrypted, you cant write anything in it without decrypting it first.
Format data and reboot recovery, then make the backup. You can flash magisk after taking the backup.
Btw r9 new release on its way with some really important changes
CheckYourScreen said:
Might be due to data partition being encrypted, you cant write anything in it without decrypting it first.
Format data and reboot recovery, then make the backup. You can flash magisk after taking the backup.
Btw r9 new release on its way with some really important changes
Click to expand...
Click to collapse
I was not trying to write the backup to the data partition, but to external SD card (tried OTG-USB as well without success).
I have flashed TWRP, formatted the data partition, and flashed Magisk. I have not tried to create a new backup yet. First I want to find out why Magisk does not pass the Safetynet check.
Can't wait to see what r9 brings. Thanks for your efforts. :good:
gewe said:
I was not trying to write the backup to the data partition, but to external SD card (tried OTG-USB as well without success).
I have flashed TWRP, formatted the data partition, and flashed Magisk. I have not tried to create a new backup yet. First I want to find out why Magisk does not pass the Safetynet check.
Can't wait to see what r9 brings. Thanks for your efforts. :good:
Click to expand...
Click to collapse
Magisk won't pass safety net with stock boot.img (kernel). Here is a modified kernel.
https://forum.xda-developers.com/showthread.php?p=73930507
After flashing new kernel Magisk passes no problem.
Sent by way of magic
lilcdroid said:
Magisk won't pass safety net with stock boot.img (kernel). Here is a modified kernel.
https://forum.xda-developers.com/showthread.php?p=73930507
After flashing new kernel Magisk passes no problem.
Sent by way of magic
Click to expand...
Click to collapse
When I flash this my WiFi stops working completely. I'm running aosp extended rom. I'm not sure if I can achieve battery life as good as I can on the stock ROM as I can on this one so im not sure what I should do about that..
Brycearuuni said:
When I flash this my WiFi stops working completely. I'm running aosp extended rom. I'm not sure if I can achieve battery life as good as I can on the stock ROM as I can on this one so im not sure what I should do about that..
Click to expand...
Click to collapse
Sorry I wasn't aware you weren't still on stock. That kernel will only work on stock. I would verify with the maintainer of AOSP extended ROM that the kernel is patched to work with Magisk.
Sent by way of magic
The below works for Nougat ROMs. I didn't have a chance to try with Oreo yet, sorry.
The ability to encrypt a device doesn’t depend on the presence of the stock recovery nor no-verity-opt-encrypt being flashed or not. It simple needs an unrooted boot.img at the moment the encryption is attempt. You do however need no-verity-opt-encrypt flashed to allow a custom ROM to boot. So the desired state to allow encryption from within a custom ROM is to have the stock boot.img with only no-verity-opt-encrypt applied to it.
The simplest sequence to archive a fully encrypted device with a custom ROM is the following:
- Flash (I recommend Dr. Ketan) ROM as always, but DISABLE ANY ROOTING in the installer
- Encrypt the device from the settings menu
- Flash the ROM one more time, this time WITH MAGISK ROOT. It will display a warning about /data not being mountable as it is now encrypted. That is ok as everything we need is already in place
If you didn’t choose fast encryption (which I recommend for security), download Trimmer (fstrim) from Play Store, tick all partitions and click Trim Now. This will free up all the sectors overwritten by the encryption process on the flash controller and makes your device work super smooth like before encryption.
This obviously only works that simple with ROMs that offer the ability to initially flash without root and if you’ve been on stock or a rootless ROM before. If that’s not the case you have the following options:
- Flash Magisk Uninstaller after initial ROM flash. You may have to reflash no-verity-opt-encrypt in TWRP again, in case it fails to boot now.
- Flash the stock book.img back in Odin and apply no-verity-opt-encrypt in TWRP. Use 7-Zip to create a tar only containing the stock BOOT.IMG and flash it in Odin using the AP slot.
- Flash back a TWRP backup taken of the boot partition before installing a root ROM, but after flashing no-verity-opt-encrypt.
Updating your ROM works no different then usual also. Just dirty flash over if it's the same ROM unless the release notes explicitly mention to factory reset. You don't need /data writable for a ROM update.
Enjoy your fully encrypted and rooted device.
Thank you, I'll try this when I'm at home. Nice recommendation with the trimmer tool, too!
Chainfire root & encryption [N950F]
Many thanks for this guide, plop12345. When it comes to the S7, Chainfire has been bit less optimitic in terms of encryption in conjunction with root, though. Maybe this is related to the weird case that on the S7, encryption seems to be enabled by default whereas it (once again) isn't on the Note 8 which doesn't make any sense to me as it was released after the S7.
Anyway, could you maybe elaborate on whether TWRP and Magisk are necessary or a stock rom with stock recovery and Chainfire's SuperSU only suffices as well?
So far I relinquish the encryption and only rooted by this method.
I would greatly appreciate your advice, thanks.
Encryption in oreo rom
Hi there,
nice guide to a encryped rooted rom :good:
I tried it with the new Dr.Ketan oreo rom o5, but it does not work. Is this guide also for the oreo update?
Everytime i hit the encryped button in settings, the phone only soft reboots. I also tried the stock boot.img from AP, without any luck.
Greez,
hallo
halloweltkk said:
Hi there,
nice guide to a encryped rooted rom :good:
I tried it with the new Dr.Ketan oreo rom o5, but it does not work. Is this guide also for the oreo update?
Everytime i hit the encryped button in settings, the phone only soft reboots. I also tried the stock boot.img from AP, without any luck.
Greez,
hallo
Click to expand...
Click to collapse
I haven't tried it with Oreo yet. But I'll probably give it a spin with Oreo within the next month. Sorry for that, will add a note to the guide.
little-endian said:
Many thanks for this guide, plop12345. When it comes to the S7, Chainfire has been bit less optimitic in terms of encryption in conjunction with root, though. Maybe this is related to the weird case that on the S7, encryption seems to be enabled by default whereas it (once again) isn't on the Note 8 which doesn't make any sense to me as it was released after the S7.
Anyway, could you maybe elaborate on whether TWRP and Magisk are necessary or a stock rom with stock recovery and Chainfire's SuperSU only suffices as well?
So far I relinquish the encryption and only rooted by this method.
I would greatly appreciate your advice, thanks.
Click to expand...
Click to collapse
Sorry for the late reply. I have no S7 to try, but believe using Magisk instead of SuperSu should work. Magisk has means to work with devices with forced encryption. AFAIK with an encrypted device it will put things to the cache partition first and on the next boot move things to the final location. I'm not aware of a similar mechanism in SuperSu.
I would try to unroot with Supersu, flash TWRP and give Magisk a spin. Keeping the stock ROM should be ok, however it will likely fail SafetyNet after plain Magisk Root. In that case try the universal SafetyNet fix also available as module within the Magisk app. If it fails to boot after Magisk root, try flashing the no verify opt encryption patch, but I don't think you need it.
I tried it in O5 as well and cannot get it to work. Just soft reboot as mentioned. No magisk just the ROM with stock kernel and still fails. Any advice?
will this work on s8?
Worked for me on S9 (GF-960F)! Thanks!
Had to use the Magisk Uninstaller first though, as I've alrady rooted.
Has anyone had any luck with this on Oreo? I've been trying to get my N960F simultaneously rooted and encrypted, but haven't had any luck with any method I've tried thus far. I can root it just fine, or encrypt it, but I've not found a way to do both at the same time without it resulting in "Verification failed" and a reset loop.
no-verity-opt-encrypt unable to find boot block location
I am having problems following these indications for rooting/encrypting an S2 tablet (nougat). The problem happens with the installation of no-verity-opt-encrypt from twrp, the script fails with "Unable to find boot block location". I have tried various versions of no-verity-... starting with 6.0 with same results. I wonder whether I have done something wrong in the process or if the S2 tablet behaves differently than the Note 8.
I started unrooting an earlier chainfire installation and reinstalling a stock boot image without problems, then comes the unsuccessful no-verity-opt-encrypt and if I carry on I end with an encrypted system that gets broken when I try to root with magisk.
I have also tried to use the no-verity-opt-encrypt features of magisk (KEEPVERITY=false and KEEPFORCEENCRYPT=false in /data/.magisk) without success.
The other thing that bothers me is that as soon as I have an encryted (but not rooted) system I am unable to mount /data from twrp. I have followed various threads with workarounds on the topic but my twrp (3.2.3) seems to behave differently.
Thanks for any hint that you may have.
sllorent said:
I am having problems following these indications for rooting/encrypting an S2 tablet (nougat). The problem happens with the installation of no-verity-opt-encrypt from twrp, the script fails with "Unable to find boot block location". I have tried various versions of no-verity-... starting with 6.0 with same results. I wonder whether I have done something wrong in the process or if the S2 tablet behaves differently than the Note 8.
I started unrooting an earlier chainfire installation and reinstalling a stock boot image without problems, then comes the unsuccessful no-verity-opt-encrypt and if I carry on I end with an encrypted system that gets broken when I try to root with magisk.
I have also tried to use the no-verity-opt-encrypt features of magisk (KEEPVERITY=false and KEEPFORCEENCRYPT=false in /data/.magisk) without success.
The other thing that bothers me is that as soon as I have an encryted (but not rooted) system I am unable to mount /data from twrp. I have followed various threads with workarounds on the topic but my twrp (3.2.3) seems to behave differently.
Thanks for any hint that you may have.
Click to expand...
Click to collapse
Maybe it's too late to answer to you, but this could be usefull for someone else.
I had same problem, "Unable to find boot block location", with same TWRP 3.2.3.
To solve this problem i downgrade TWRP 3.2.3 to TWRP 3.1.0-1 - Nougat that i found here https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627.
Than i followed the step to root, but i used Magisk 17.3 instaead SuperSu (Magisk 18.0 gave me some problem). Now i have root permissions with Magisk
Thanks, it is interesting that that particular version of twrp works with the no-verity script. Did you also succeed in keeping the tablet encrypted while rooted with Magisk?
sllorent said:
Thanks, it is interesting that that particular version of twrp works with the no-verity script. Did you also succeed in keeping the tablet encrypted while rooted with Magisk?
Click to expand...
Click to collapse
I don't know, sorry. How can i check that?
Inviato dal mio SM-T819 utilizzando Tapatalk
Android root + encryption possible at all ???
According to TWRP root + encryption is not possible / working.
One could easily disable encryption / extract the password by having access to root and kernel files using TWRP recovery. There are also programs like "Oxygen OS" that can be flashed from the recovery and bypass the password prompt. That would make the whole procedure useless...
Any thoughts on this? And other ideas on Android / third party encryption apps? Encrypting containers with EDS would be an alternative (recommended by Veracrypt) since full disc encryption is still not available for Android (why btw.? nobody seems to care...) - but I am not sure if one could run / move apps into the container (like contacts, sms, e-mail-apps etc.)...
Cheers!
no ideas - nobody ??
no ideas - nobody ??
Finally, rooted with Magisk and encrypted data note8 exynos
Followed these threads
https://forum.xda-developers.com/galaxy-s7/help/to-magisk-data-encryption-s7-t3667007
https://forum.xda-developers.com/note-fe/how-to/exynos-8890-sm-n935f-ds-twrp-root-t3771767
Tested with stock Nougat and TWRP-3.2.1.0-greatlte (with twrp-3.2.3-0 fail)
got these combinations working
Samsung_S7+Oreo+Magisk+Xposed+root+encryption
LG_V30+OreoAOSP+Magisk+Xposed+root+encryption(+BThandsfree)
also according to TWRP and the threads it was impossible. the TWPR might not be able to read files, i don't care as long as i have encrypted system. I can flash from the system.
Wouldn't like 3rd party solution as i want Secure Boot and type password during the boot.
Encryption and root is a must. But it's getting difficult more and more nowadays. ROM threads don't list limitations since KNOX was ever introduced, and that sucks. Instead of "knox will be tripped, warning boot screen will be showm, TWRP won't read filesystem, BT handsfree won't work, encryption won't work" you get "no limitations". Have to read full threads to discover the truth.
Hope Note9 and S10 will be ok.
No encryption working on my N960FD
I tried to install it while updating to DrKetan p09 and it doesnt work.
Is it possible for somebody to help me ?
I ve done a clean install and unrooted the no-verity-encrypt flash (The phone didn't even unlocked with pin )
xdaparanoia said:
According to TWRP root + encryption is not possible / working.
One could easily disable encryption / extract the password by having access to root and kernel files using TWRP recovery. There are also programs like "Oxygen OS" that can be flashed from the recovery and bypass the password prompt. That would make the whole procedure useless...
Cheers!
Click to expand...
Click to collapse
Is this true??
Hello, I am newbie yet so I am asking if anyone can explain the vendor's use, and what do I get from installing them.
Thank you for your time
Now almost roms here includes custom vendor. So you need firmware only.
https://xiaomifirmwareupdater.com/vendor/beryllium/
And here's custom rom installation process
Flash rom
Flash firmware
Gapps(optional)
Dfe(if you don't want it to be encrypted)
Magisk(optional)
That's it. No need to know more.
nasos_Gr said:
Hello, I am newbie yet so I am asking if anyone can explain the vendor's use, and what do I get from installing them.
Thank you for your time
Click to expand...
Click to collapse
Miui decided to use MODIFIED VENDOR IMAGE hence POCO F1 gets a modified vendor image for Android Pie-based Project Treble GSIs
what was the impact?
custom roms couldn't be flashed (booted) if you don't flash the modified vendor image from twrp
even today when most of the roms have their own vendor you still need to flash the vendor+firmware (atleast)
Developer Akhil Narang started collecting all releases at
https://mirror.akhilnarang.me/MIUI/beryllium/
currently I am using 9.6.27-9.0 which is working best for me, 10.3.6 image made my batter drainage high (atleast i noticed)
I am on HAVOC2.8 and this is how i did it
1. flashed TWRP 3.3.1 unofficial (download it from HERE ) ref Reference - as official twrp has TOUCH driver issues. this one worked with me very well
2. I wiped /data, /system then
3. flashed VENDOR.zip from HERE
4. FLASHED CUSTOM ROM (i use HAVOC2.8)
5. FLASHED DFE HERE - REFERENCE
6. FLASHED GOOGLE APPS ( GAPPS.ORG) ( ARM64>9.0MicroPackage)
7. Flash Kernel ( OPTIONAL- havoc uses shadow kernel , i feel optimus drunk kernel is better, battery and 4g connectivity) even Franco Kernel is very good
8. FLASHING MAGISK19.3
9. when i was on havoc2.7, by using MIGRATE, it made flashable zip of my APPS+DATA, stored in internalStorage, and now I will FLASH that file., Mine size goes to 2gb you can get it from HERE
10. WIPE CACHE/DELVIK
11. REBOOT
fire reboot may go in to bootloop and then second reboot may take a while and finally you should see Pixel Setup asking google accounts and info etc
-----------------------
extraa
once after you finish setup! don't RESTORE APPS from PLAYSTORE, (download only license apk, in my case I have purchases many apps from playstore and saperate license info is always appear in intial setup! SELECT THOSE ONLY)
ONCE playstore is DONE downloading all your selected (fewer) apps, and MAGISK ROOT is working...... put device on AIRPLANE MODE
FROM DROP DOWN Notification panel, CLICK MIGRATE, and it will prompt you what do you wana restore from your previouce ROM to newly flashed HAVOC ..APPS+SETTINGS+PERMISSION+DATA etc - migrate restoration may take upto 30 mins,
once done, uninstall from system and reboot device!
REMEMBER I DONOT RECOMEND MIGRATE TRICK FOR WHATSAPP, it doesn't work properly and NOTIFICATION ISSUES with BLANK DP observed by me whenever I forcely re-instated whatsapp by migrate!
Martensite said:
Now almost roms here includes custom vendor. So you need firmware only.
https://xiaomifirmwareupdater.com/vendor/beryllium/
And here's custom rom installation process
Flash rom
Flash firmware
Gapps(optional)
Dfe(if you don't want it to be encrypted)
Magisk(optional)
That's it. No need to know more.
Click to expand...
Click to collapse
I understand but I have installed some custom Roms without finding vendor image and still it works perfect.
And do I need to install this image every time I flash a new ROM?
Thanks
nasos_Gr said:
I understand but I have installed some custom Roms without finding vendor image and still it works perfect.
And do I need to install this image every time I flash a new ROM?
Thanks
Click to expand...
Click to collapse
Flashing custom roms will not wipe anything, so the vendor is still there. And firmwares too.
Disclaimer: I'm not a dev, i'm just someone who has a lot of time to do research on Windows, Android... So that i can say i'm quite a talent that stuffs when other don't, may be just know to use Facebook, Youtube or something similar. But when you're here, want to read my topic, i'm happy you're something like me, want your phone yours and yours only, want to do more with your phone. So let's get started.
- My Phone: Redmi 8A -4/64 China Variant, i'm not from China though. Running Xiaomi.eu rom 11.0.4.0 as base to install gsi. I have tried Global Rom but it's incompatible with my phone (random reboot, missing imei, no MAC address...) so please flash another market version with caution.
- Why i write this topic? Because firstly i want to demonstrate how to install a GSI rom. Secondly, i feel somehow wifi speed on MIUI is ridiculous, only 500-600kb/s, it takes me 15 minutes to download a 16mb app; random ping in game, that make the game not enjoyable. This wifi symptom is like on a phone from my country, Vsmart joy 2+, run on the same entry variant 4xx, due to support wifi 2.4 ghz only. (Because bluetooth interfering with wifi 2.4 Ghz and our device doesn't support 5ghz wifi)
Compare to MIUI, Havoc OS has somethings i like:
+ Faster download/upload speed: no delay with wifi bluetooth interference
+ Doesn't have bloatware, you choose what you want to install
+ All known bugs i mentioned in my previous topic are fixed, except Auto Brightness - i don't use it though
+ D2TW needs to be fixed. But i have a workaround using Magisk and root.
And a lot that i dont write all here.
Instructions:
Read my previous topic first, all instructions below will focus on Havoc OS only.https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
0) Backup Backup Backup, be sure to have a plan in case anything goes wrong. I use a offline disk drive to backup anything important.
1) Unlock Bootloader, Install TWRP or Orange Fox. If you come from stock MIUI, use Volume Up + Power to enter recovery directly after flash with Fastboot, ortherwise, stock recovery will be replaced.
Remember to flash vbmeta.img.
2) Download all the files in my post, download Havoc OS GSI and extract to get system
From Official Havoc OS here: https://sourceforge.net/projects/havoc-os/files/a64-ab/ (Newer Version)
Download Opengapps (optional) from opengapps (10/arm/nano or pico)
Download boot.img from my previous topic, choose the right version matched your phone version.
3) Copy all the files to the phone. I recommend use a micro sd card because internal storage may be encrypted, or you can format data first, your call.
4) Format the following partitions: Cache, Dalvik, Data and System
5) Install system image to system partition.
6) Install permissiver_v5
7) Resize system partition to install opengapps.
8) Install Opengapps or what gapps you choose
9) Flash Certification + Patch
10) Reboot. If bootloop, format data. Not wipe data. Then setup your phone.
11) Install Magisk Manager. Follow the app instructions.
12) Install d2tw module to have d2tw feature. If it doesn't work, then try an alternative way:
Open /vendor/bin/init.qcom.post_boot.sh and add the string:
Code:
sendevent /dev/input/event2 0 1 5
then reboot
13) Enjoy Havoc OS. Install apps, configure settings...
How to Update
- Flash system image over, no wipe require. Just reboot.
Bugs
I don't use the phone often so i can say it's stable enough to be a daily driver rom. If there's any, just comment below so i can add them.
Additions
- Here are all apps i want to install on my phone: Youtube Vanced from https://vancedapp.com/; Bromite for browsing; modded messenger from @evilwombatHere, outdated version but still okay.
- If you don't like stock camera, you can use gcam, here is a working version i download from Telegram group: Here
- To fix Recording, from Misc features -> Force Timestamp Source, choose Clock boottime
And that's all. Now enjoy!
I gifted my sister this phone so i don't have device to test anymore. Still, sometime i'll test if i can. The guide still works so enjoy flashing!!!
Great. I've been using havocOs for almost two months now and it's great. Much quicker and smoother than stock miui. Only problem I've been trying to find a fix for is setting up a lock screen.
Thanks for sharing the dt2w module for magisk. Is there some sort of setting I need to mess with to get it to work? I've installed the module and activated it in magisk but dt2w still won't work. I also activated the dt2w setting that comes with havocOs 3.1 under " xiaomi features " but that never worked from the beginning.
ways2 said:
Great. I've been using havocOs for almost two months now and it's great. Much quicker and smoother than stock miui. Only problem I've been trying to find a fix for is setting up a lock screen.
Thanks for sharing the dt2w module for magisk. Is there some sort of setting I need to mess with to get it to work? I've installed the module and activated it in magisk but dt2w still won't work. I also activated the dt2w setting that comes with havocOs 3.1 under " xiaomi features " but that never worked from the beginning.
Click to expand...
Click to collapse
Did you flash no_encrypt zip? It'll make set up screen password impossible because encryption is disable. I have clean flashed Havoc OS and confirm d2tw module working, despite i don't active the xiaomi option in setting.
Ga_hap_la_chanh said:
Did you flash no_encrypt zip? It'll make set up screen password impossible because encryption is disable. I have clean flashed Havoc OS and confirm d2tw working, despite i don't active the xiaomi option in setting.
Click to expand...
Click to collapse
Yes I believe I did flash no_encrypt. Is there any possible way to re-enable Encryption to set up a screen lock at this point?
ways2 said:
Yes I believe I did flash no_encrypt. Is there any possible way to re-enable Encryption to set up a screen lock at this point?
Click to expand...
Click to collapse
There is a trick, you can enable encryption through Settings -> security -> Encryption and credentials then encrypt phone. If it doesn't work, then read this thread https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Or you can do the whole process again, clean flash and do as my thread. May be d2tw starts working.
Thank you sir
thanks a lot for this
can you tell me how to upgrade our 32bit os to 64bit
Ga_hap_la_chanh said:
There is a trick, you can enable encryption through Settings -> security -> Encryption and credentials then encrypt phone. If it doesn't work, then read this thread https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Or you can do the whole process again, clean flash and do as my thread. May be d2tw starts working.
Click to expand...
Click to collapse
I wasn't able to encrypt my phone it would just reboot and nothing change.
So I ended up re-flashing back to MIUI stock firmware.
Flashing OrangeFox and HavocOS 3.1
Flashed all of the other necessary stuff EXCEPT for Disable_ForceEncrypt.
Now my phone is encrypted and able to set up a Screen Lock .
Now I'm still not able to use dt2w for some odd reason. No worries though I'm able to set up tap status bar to lock so that'll help for Now until I can keep dt2w to work.
ways2 said:
I wasn't able to encrypt my phone it would just reboot and nothing change.
So I ended up re-flashing back to MIUI stock firmware.
Flashing OrangeFox and HavocOS 3.1
Flashed all of the other necessary stuff EXCEPT for Disable_ForceEncrypt.
Now my phone is encrypted and able to set up a Screen Lock .
Now I'm still not able to use dt2w for some odd reason. No worries though I'm able to set up tap status bar to lock so that'll help for Now until I can keep dt2w to work.
Click to expand...
Click to collapse
Hi bro
i am new to this
i have 2gb indian varient
can you make a full youtube tutorial of twrp installation
or give correct steps how to do twrp
---------- Post added at 05:48 AM ---------- Previous post was at 05:42 AM ----------
Ga_hap_la_chanh said:
Disclaimer: I'm not a dev, i'm just someone who has a lot of time to do research on Windows, Android... So that i can say i'm quite a talent that stuffs when other don't, may be just know to use Facebook, Youtube or something similar. But when you're here, want to read my topic, i'm happy you're something like me, want your phone yours and yours only, want to do more with your phone. So let's get started.
- My Phone: Redmi 8A -4/64 China Variant, i'm not from China though. Running Xiaomi.eu rom 11.0.4.0 as base to install gsi. I have tried Global 10.3 but it's incompatible with my phone (random reboot, missing imei, no MAC address...) so please flash another market version with caution.
- Why i write this topic? Because firstly i want to demonstrate how to install a GSI rom. Secondly, i feel somehow wifi speed on MIUI is ridiculous, only 500-600kb/s, it takes me 15 minutes to download a 16mb app; random ping in game, that make the game not enjoyable. This wifi symptom is like on a phone from my country, Vsmart joy 2+, run on the same entry variant 4xx.
Compare to MIUI, Havoc 3.1 has somethings i like:
+ Faster download/upload speed: almost the same as the speed of my network
+ Doesn't have some bloatwares, you choose what you want to install
+ All known bugs i mentioned in my previous topic are fixed, except Auto Brightness - i don't use it though
+ D2TW needs to be fixed. But i have a workaround using Magisk.
And a lot that i dont write all here.
Instructions:
Read my previous topic first, all instructions below will focus on Havoc OS only.https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
0) Backup Backup Backup, be sure to have a plan in case anything goes wrong. I use a offline disk drive to backup anything important to me.
1) Unlock Bootloader, Install TWRP or Orange Fox. If you come from stock MIUI, use Volume Up + Power to enter recovery directly after flash with Fastboot, ortherwise, stock recovery will be replaced.
Remember to flash vbmeta.img.
2) Download all the files in my post, download Havoc OS GSI from ExpressLuke and extract to get system imagehttps://sourceforge.net/projects/expressluke-gsis/files/HavocOS/Ten/A64/AB/
Download Opengapps (optional) from opengapps (10/arm/nano or pico)
Download boot.img from my previous topic, choose the right version matched your phone version.
3) Copy all the files to the phone. I recommend use a micro sd card because internal storage may be encrypted, or you can format data first, your call.
4) Format the following partitions: Cache, Dalvik, Data and System
5) Install system image to system partition.
6) Install permissiver_v5
7) Resize system partition to install opengapps.
8) Install Opengapps or what gapps you choose
9) Flash Certification + Patch
10) Reboot. If bootloop, format data. Not wipe data. Then setup your phone.
11) Install Magisk Manager. Follow the app instructions.
12) Install d2tw module to have d2tw feature.
13) Enjoy Havoc OS. Install apps, configure settings...
Bugs
I don't use the phone often so i can say it's stable enough to be a daily driver rom. If there's any, just comment below so i can add them.
Additions
- Here are all apps i want to install on my phone: Youtube Vanced from vanced.app; Bromite for browsing; modded messenger from @evilwombatHere, outdated version but still okay.
- If you don't like stock camera, you can use gcam, here is a working version i download from Telegram group: Here
And that's all. Now enjoy!
Click to expand...
Click to collapse
Hi
can you make a youtube video of twrp and gsi installation
please man for redmi 8a
eddy law paul king said:
Hi bro
i am new to this
i have 2gb indian varient
can you make a full youtube tutorial of twrp installation
or give correct steps how to do twrp
---------- Post added at 05:48 AM ---------- Previous post was at 05:42 AM ----------
Hi
can you make a youtube video of twrp and gsi installation
please man for redmi 8a
Click to expand...
Click to collapse
I've considered making a complete tutorial on installing recovery, root, & rom installation for this phone. Next time I go back to stock I probably will make a video. Until then you can definitely follow the tutorials on this forum to install a custom recovery and rom. Personally I would recommend installing OrangeFox recovery because TWRP has touchscreen issues sometimes.
You will have to unlock the bootloader first which takes 14 days if you have not already.
The tool to unlock the Bootloader is here: https://en.miui.com/unlock/download_en.html
Once your bootloader is unlocked you're ready to install OrangeFox custom recovery, the files and instructions can be found here:
https://forum.xda-developers.com/xi...t/orangefox-recovery-xiaomi-redmi-8a-t4032583
Once you have OrangeFox recovery installed you can follow this tutorial in this thread to install HavocOS rom or the other thread
https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
Try it out and then come back and let us know what problems you run into
ways2 said:
I've considered making a complete tutorial on installing recovery, root, & rom installation for this phone. Next time I go back to stock I probably will make a video. Until then you can definitely follow the tutorials on this forum to install a custom recovery and rom. Personally I would recommend installing OrangeFox recovery because TWRP has touchscreen issues sometimes.
You will have to unlock the bootloader first which takes 14 days if you have not already.
The tool to unlock the Bootloader is here: https://en.miui.com/unlock/download_en.html
Once your bootloader is unlocked you're ready to install OrangeFox custom recovery, the files and instructions can be found here:
https://forum.xda-developers.com/xi...t/orangefox-recovery-xiaomi-redmi-8a-t4032583
Once you have OrangeFox recovery installed you can follow this tutorial in this thread to install HavocOS rom or the other thread
https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
Try it out and then come back and let us know what problems you run into
Click to expand...
Click to collapse
i am very afraid that i brick my devise
so make a video
it is accurate and much helpful and easy to understand
i am waiting
Can I use the attached files for installing gsi in redmi 9 ?
vinith 32 said:
Can I use the attached files for installing gsi in redmi 9 ?
Click to expand...
Click to collapse
no
this is for 8 and 8a only
@Ga_hap_la_chanh
I'm wondering if that d2tw module not working for me has something similar to do with how the touch screen becomes unresponsive in TWRP for some people. What recovery did you use on your redmi?
ways2 said:
@Ga_hap_la_chanh
I'm wondering if that d2tw module not working for me has something similar to do with how the touch screen becomes unresponsive in TWRP for some people. What recovery did you use on your redmi?
Click to expand...
Click to collapse
I used TWRP then moved to Orange Fox. Everything working fine, may be your screen is different. In d2tw module, there's a file called readme.md: Manual usage : - enable $ set-dt2w 1 - disable $ set-dt2w 0
Just try it -))))))))
Great GSI. I have this one problem though. I cannot backup anything from TWRP. Is it really normal because it's encrypted?
createTarFork() process ended with ERROR: 255
Ga_hap_la_chanh said:
Disclaimer: I'm not a dev, i'm just someone who has a lot of time to do research on Windows, Android... So that i can say i'm quite a talent that stuffs when other don't, may be just know to use Facebook, Youtube or something similar. But when you're here, want to read my topic, i'm happy you're something like me, want your phone yours and yours only, want to do more with your phone. So let's get started.
- My Phone: Redmi 8A -4/64 China Variant, i'm not from China though. Running Xiaomi.eu rom 11.0.4.0 as base to install gsi. I have tried Global 10.3 but it's incompatible with my phone (random reboot, missing imei, no MAC address...) so please flash another market version with caution.
- Why i write this topic? Because firstly i want to demonstrate how to install a GSI rom. Secondly, i feel somehow wifi speed on MIUI is ridiculous, only 500-600kb/s, it takes me 15 minutes to download a 16mb app; random ping in game, that make the game not enjoyable. This wifi symptom is like on a phone from my country, Vsmart joy 2+, run on the same entry variant 4xx.
Compare to MIUI, Havoc 3.1 has somethings i like:
+ Faster download/upload speed: almost the same as the speed of my network
+ Doesn't have some bloatwares, you choose what you want to install
+ All known bugs i mentioned in my previous topic are fixed, except Auto Brightness - i don't use it though
+ D2TW needs to be fixed. But i have a workaround using Magisk.
And a lot that i dont write all here.
Instructions:
Read my previous topic first, all instructions below will focus on Havoc OS only.https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
0) Backup Backup Backup, be sure to have a plan in case anything goes wrong. I use a offline disk drive to backup anything important to me.
1) Unlock Bootloader, Install TWRP or Orange Fox. If you come from stock MIUI, use Volume Up + Power to enter recovery directly after flash with Fastboot, ortherwise, stock recovery will be replaced.
Remember to flash vbmeta.img.
2) Download all the files in my post, download Havoc OS GSI from ExpressLuke and extract to get system imagehttps://sourceforge.net/projects/expressluke-gsis/files/HavocOS/Ten/A64/AB/
Download Opengapps (optional) from opengapps (10/arm/nano or pico)
Download boot.img from my previous topic, choose the right version matched your phone version.
3) Copy all the files to the phone. I recommend use a micro sd card because internal storage may be encrypted, or you can format data first, your call.
4) Format the following partitions: Cache, Dalvik, Data and System
5) Install system image to system partition.
6) Install permissiver_v5
7) Resize system partition to install opengapps.
8) Install Opengapps or what gapps you choose
9) Flash Certification + Patch
10) Reboot. If bootloop, format data. Not wipe data. Then setup your phone.
11) Install Magisk Manager. Follow the app instructions.
12) Install d2tw module to have d2tw feature.
13) Enjoy Havoc OS. Install apps, configure settings...
Bugs
I don't use the phone often so i can say it's stable enough to be a daily driver rom. If there's any, just comment below so i can add them.
Additions
- Here are all apps i want to install on my phone: Youtube Vanced from vanced.app; Bromite for browsing; modded messenger from @evilwombatHere, outdated version but still okay.
- If you don't like stock camera, you can use gcam, here is a working version i download from Telegram group: Here
And that's all. Now enjoy!
Click to expand...
Click to collapse
Bro having oragane fox recovery installed on my redmi 8a device, can you please tell me at which step of flashing gsi we have to flash vbmeta.img and boot. Img
---------- Post added at 03:13 AM ---------- Previous post was at 02:26 AM ----------
ways2 said:
I wasn't able to encrypt my phone it would just reboot and nothing change.
So I ended up re-flashing back to MIUI stock firmware.
Flashing OrangeFox and HavocOS 3.1
Flashed all of the other necessary stuff EXCEPT for Disable_ForceEncrypt.
Now my phone is encrypted and able to set up a Screen Lock .
Now I'm still not able to use dt2w for some odd reason. No worries though I'm able to set up tap status bar to lock so that'll help for Now until I can keep dt2w to work.
Click to expand...
Click to collapse
bro can you tell me that have you flashed the boot.img while flashing the gsi and if yes then at which step..
ItsmeTushar said:
Bro having oragane fox recovery installed on my redmi 8a device, can you please tell me at which step of flashing gsi we have to flash vbmeta.img and boot. Img
---------- Post added at 03:13 AM ---------- Previous post was at 02:26 AM ----------
bro can you tell me that have you flashed the boot.img while flashing the gsi and if yes then at which step..
Click to expand...
Click to collapse
Boot.img and vbmeta are done before flashing the gsi. I'd recommend reading this thread first for better understanding
https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
Zzzleepy said:
Great GSI. I have this one problem though. I cannot backup anything from TWRP. Is it really normal because it's encrypted?
createTarFork() process ended with ERROR: 255
Click to expand...
Click to collapse
I'm getting the same error with attempting to make a back up in orangefox. After seeing you have the same problem now I'm assuming it is indeed a problem with encryption? I was able to make backups successfully before my phone was encrypted so I still have an old back up on my PC. However it would be nice to be able to make a new fresh back up.
I'm getting the same error with attempting to make a back up in orangefox. After seeing you have the same problem now I'm assuming it is indeed a problem with encryption? I was able to make backups successfully before my phone was encrypted so I still have an old back up on my PC. However it would be nice to be able to make a new fresh back up.
Click to expand...
Click to collapse
That was weird. In stock ROM, I can back up the /data/media just fine even when encrypted. But after having Havoc OS, I cannot do that anymore. Tried on both TWRP and OrangeFox. I can, with an unencrypted phone, but I do not feel comfortable without a lockscreen. Tried all things I have researched on that error. Not one worked. Might as well just stick to Titanium Backup for backups.
Overall, great GSI. Loading is faster than on stock (with the internet too)! Though, I have another issue with regards to the locking of apps, so that the app would not be cleared. Speaking of clearing apps, it is tiring to scroll left just to see the "Clear All" option in Recents. Autostart too.
I know you are not the developer, but just letting you know my concerns.
How to resize system partition for install gapps?
Soerex24 said:
How to resize system partition for install gapps?
Click to expand...
Click to collapse
Reboot to custom recovery > Menu > Manage Partitions > System > Resize or Repair
So, since there is not alot of development going on for our device, i thought we could maybe work together to get something done four our Mi Note 10.
Android Q (10) Guide
1) Flash Miui 12 beta
2) Flash Latest OrangeFox Recovery
3) Format Data
4) Wipe dalvik and cache
5) Reboot to Recovery
6) Flash an GSI of your choice (Arm64-AB)
7)Resize the system partition
8) Optional: Flash Opengapps
9) Optional: Flash Magisk
Restart system
Enjoy
(Big thanks to deathhall)
For me Havoc Q works really well, also face unlock works with Havoc
Havoc specific bugs: SMS doesnt work with 4G, Gcam works only with the main lens and frontfacing lens
Havoc 3.6
Android Pie (9) Guide
How to flash these on the Mi Note 10?
1) Flash Orange Fox TWRP
2) Factory reset in TWRP / format Data!
4) Fastboot: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5) Download the ARM64-AB version of your desired rom
6) Flash AB system.img of your GSI in TWRP
7) Flash magisk
8) reboot
That worked for me with both GSIs
Lineage OS 16.0
HAVOC OS 2.9
Whats not working?
- Fingerprint (Needs custom overlay)
- Automatic Brightness (Needs custom overlay)
- Camera works fine, but Video seems a little bit weird
- NFC, but this can be fixed with a magisk module
NFC FIX
Kind of a fix for automatic brightness
Video fix
If you have weird notification sounds delete the SoundFX folder from /Vendor/lib and /Vendor/lib64
Framework-res.apk (Provided by ChriZer)
Great work my friend, hopefully these will be the stepping stones to development and we can get the ball rolling on more in the future!
Sent from my MI CC9 Pro using Tapatalk
- flash an Xiaomi OTA update like 1.0.1.0 (around 2,5gb)
Link please.
ztocker said:
- flash an Xiaomi OTA update like 1.0.1.0 (around 2,5gb)
Link please.
Click to expand...
Click to collapse
Try with 11.0.12
Couldnt get either to actually boot, couldn't get any OTA's to actually flash with OrangeFox.
I flashed:
miui_TUCANAEEAGlobal_V11.0.11.0.PFDEUXM_9fa3ae20ce_9.0
then tried to flash:
miui-blockota-tucana_eea_global-V11.0.11.0.PFDEUXM-V11.0.12.0.PFDEUXM-ecf4ee46b2-9.0
and just get an error.
I tried following your steps written in the OP, but the BlockOTA fails to flash. Or if I just use a fresh install and Format data, and try to install the GSI's it rewrites the system to system_root and magisk won't install and it just bootloops.
deathhall said:
Couldnt get either to actually boot, couldn't get any OTA's to actually flash with OrangeFox.
I flashed:
miui_TUCANAEEAGlobal_V11.0.11.0.PFDEUXM_9fa3ae20ce_9.0
then tried to flash:
miui-blockota-tucana_eea_global-V11.0.11.0.PFDEUXM-V11.0.12.0.PFDEUXM-ecf4ee46b2-9.0
and just get an error.
I tried following your steps written in the OP, but the BlockOTA fails to flash. Or if I just use a fresh install and Format data, and try to install the GSI's it rewrites the system to system_root and magisk won't install and it just bootloops.
Click to expand...
Click to collapse
Maybe try 11.0.1. since its alot bigger than 12 and 11
Android 11 GSi is out can you give it a shot?
Status?
Is anybody using the LOS GSI as a daily driver?
If there is just the small amount of bugs like in the description, it might be fine for now. At least for me.
Or are there other small bugs 'not worth mentioning' ?
In another parallel thread 'Will there be a custom ROM?', two heros decided to work on our phone... I wish them the best!
Hi all, I have spent a good few weeks testing almost all Android 10 (Q) GSIs for tucana (our device). My findings are relatively positive and are as follows:
I got Pixel Experience as well as EvolutionX from @expressLukeGSI to boot and both seem to work with minimal bugs... The main bug I found was an audio bug commoly associated with GSIs; the audio sounds as if the device is underwater. A simple fix to this bug was flashing audiofix for GSIs.
I also got OxygenOS to boot from @erfanGSI as well as others but these had major bugs (e.g. device reboots automatically, immediately after connecting to WIFI).
Other Android Q GSIs that booted include LineageOS, CAOS, AOSP, Descendant as well as Havoc (from GSI page - Android Q Section - on Github). With regards to LineageOS, once rooted with magisk it will NOT boot.
Under Display Fingerprint does NOT work on any GSIs currently and Face Unlock only works on specific GSIs.
If you'd like more info on the GSIs I have tested or would like me to test further please don't hesitate to contact me via private message, I'll be glad to help wherever possible.
LDP12 said:
Hi all, I have spent a good few weeks testing almost all Android 10 (Q) GSIs for tucana (our device). My findings are relatively positive and are as follows:
I got Pixel Experience as well as EvolutionX from @expressLukeGSI to boot and both seem to work with minimal bugs... The main bug I found was an audio bug commoly associated with GSIs; the audio sounds as if the device is underwater. A simple fix to this bug was flashing audiofix for GSIs.
I also got OxygenOS to boot from @erfanGSI as well as others but these had major bugs (e.g. device reboots automatically, immediately after connecting to WIFI).
Other Android Q GSIs that booted include CAOS, AOSP, Descendant as well as Havoc (from GSI page - Android Q Section - on Github).
If you'd like more info on the GSIs I have tested or would like me to test further please don't hesitate to contact me via private message, I'll be glad to help wherever possible.
Click to expand...
Click to collapse
No fingerprint right?
Fingerprint on GSIs
iSonik said:
No fingerprint right?
Click to expand...
Click to collapse
Unfortunately no fingerprint on any GSIs currently
LDP12 said:
Unfortunately no fingerprint on any GSIs currently
Click to expand...
Click to collapse
Thats not a minor bug imo
iSonik said:
Thats not a minor bug imo
Click to expand...
Click to collapse
Completely opinion based; I can live without it.
I have edited my original post to include this.
LDP12 said:
Completely opinion based; I can live without it.
I have edited my original post to include this.
Click to expand...
Click to collapse
Yeah thats why i said "imo". But that also means no autobrightness
iSonik said:
Yeah thats why i said "imo". But that also means no autobrightness
Click to expand...
Click to collapse
Sorry, I never saw the "imo" part of your reply.
That is correct, once again this is minor for me but maybe not for some. Although I can confirm that battery drain is significantly decreased when using GSIs. Even without the auto brightness battery life is much better.
I am currently using/testing the Evolution X GSI from ExpressLukeGSI.
LDP12 said:
Sorry, I never saw the "imo" part of your reply.
That is correct, once again this is minor for me but maybe not for some. Although I can confirm that battery drain is significantly decreased when using GSIs. Even without the auto brightness battery life is much better.
I am currently using/testing the Evolution X GSI from ExpressLukeGSI.
Click to expand...
Click to collapse
Yeah batterylife on GSIs is insane, maybe ill try one again. But the missing fingerprint and faceunlock bother me quite alot
BTW are you using Q GSIs?
iSonik said:
Yeah batterylife on GSIs is insane, maybe ill try one again. But the missing fingerprint and faceunlock bother me quite alot
BTW are you using Q GSIs?
Click to expand...
Click to collapse
Yes, I am using Q GSIs
Interesting, i cant get GSIs to boot, did you do something different?
Are you wiping Dalvik, System, Data and Cache, and then flashing the preferred GSI?
If the above method is not working, search "Download the MIUI 12 Closed Beta for Xiaomi and Redmi devices XDA" on google, download MIUI 12 beta for tucana/Mi Note 10 (our device) and flash it in TWRP. Then perform a wipe as usual and flash preferred GSI.
iSonik said:
Interesting, i cant get GSIs to boot, did you do something different?
Click to expand...
Click to collapse
I was on MIUI 20.6.11 -MiRoom when I flashed the Bliss GSI, my exact steps where:
Flash Latest OrangeFox Recovery
Formata Data
Format dalvik and cache
Reboot to Recovery
Flash GSI -Arm64-AB or BvN depending on the owner
Go to Data in the manage partition menu and resize partition
Flash Opengapps, I used 10.0 Pico
Restart system
Admittedly, I flashed the GSI but not the gapps first, just to see if it would boot, which it did. then I formatted only cache and dalvik, then resized and flashed Gapps. and it booted and took me right into the setup from the notification that came up when it booted.