hey guys, i'm not a complete newbie about roms and flashing, etc. but treble is a whole new thing for me and I'm running into lot ot trebles (lol) and I hope someone helps me.
1. I dont need to do system wipe to flash GSI, right? only Factory Reset.
2. Also, I can get to use GApps and such, but my contacts, chrome, etc, would not sync. no matter what.
3. How can I know if the image can be flash over Oreo base, and what is this /vendor thing?
please help me, i've read a lot of guides but i can't quite figure it all out.
Vendor is a partition similar to system where your device specific things stay which are no longer in system in treble. Such as camera libraries, gps,Bluetooth,wifi and links to firmware files. When a gsi is flashed to system , it will read the information present in vendor, so you will need to flash vendor first via treble ROM or vendor image and then flash a gsi after wiping system.
Related
Hi all,
so today I found a treble-enabled ROM of Android Pie and wanted to flash it. Thing is, I need to enable treble for me first. The treble check says that Treble is indeed supported, and so does the OnePlus website, but I don't have access to the vendor partition in TWRP. Using TWRP 3.2.3-1, by the way.
So, I read that MoKee enables Treble. Tried that, flashed the rom, flashed the radio and then the rom, factory wiped, flashed rom, factory wiped, flashed radio and rom, nothing. Still can't get Treble support. Then I tried kylothow's Trebliser, but nothing there either. I am realy at a loss here - I even reinstalled OOS (newest beta of course) and I couldn't get the vendor partition to show up, which is weird considering installing said trebliser actually states "Vendor partition found, good!" when installing, and then proceeds to in fact patch the vendor partition. It just doesn"t do anything, I can't install GSIs, can't even get the treble check to register that I do in fact have treble.
So this is where I turn to you guys. Do you have any idea what I could do in this situation? Please answer genuinely and don't post "just wait for an official android p".
Thanks!
Okay there's a few things remember here after flashing the mokee trebleize pack you should have had the addition of the vendor partition included in your TWRP file system if you have the blue spark TWRP version YOU SHOULD BE ABLE TO SEE THE ADDITION OF THE VENDOR PARTITION WHEN YOU GO TO MOUNT FOLLOWING THAT.
*** Make sure that after the trebleize is installed or whatever don't touch vendor partition ever just leave it alone you don't need to do anything to it it's fine if some ROM needs to update it you don't have to worry about wiping it first because it'll take care of that with the configuration script in the zip file. Even if you want to go back to a regular Android 8. 1 ROM you don't have to worry about the vendor partition the way it's set up the vendor partition that exist inside the one plus 5T that was created for Treble is not seen by any AOSP ROMs so it's going to create its own vendor folder inside of the system partition like it normally does and that you will not conflict because the fs tab does not Mount the new vendor. By leaving vendor alone and never touching it you're just ensuring that when you flashed yes eyes you're not missing something that's essential to the boot up process and it's one thing that you can from any potential uncertainty as to why a treble mage may or may not be booting.
Follow this....
Normal Android ROMs you would usually wipe system data cache D-cache if you were going to install a new ROM that wasn't just an upgraded version of the one that you were already running you'd have to start from scratch always. This is still what you should do it whenever you want to start and flash a fresh regular ROM or treble run always do that but it's how you proceed from here that is a little difference between the two.
With a regular ROM you would just go on to flash the ROM that you want to install followed by Gapps and so on.
When you want to flash a treble image you need to be on a clean fresh ROM that has treble support already good to go in that it can see that vendor partition that was made before and that it contains the binderized HALs needed as well. Because official treble support is still in beta with the OnePlus 5T the only officially supported treble Android 8. 1 ROM is mokee so you always want to start with a clean flash of the Mokee ROM because it also contains the supported kernel and ramdisk and other things as well.
Upon flashing a fresh version of mokee you want to go ahead and Flash no-dm-variety to ensure data is not encrypted because it will lead to a bootloop and the only way to get it to work will be to either format your SD card or to install the no variety which is the way to go just install it every time you flash mokee so that way you know everything is good.
**** I've only had experience using Android 8. 1 GSi so I'm not sure exactly how it would work concerning open G apps because I've only had to do it with two 8. 1 apps I'm not touching the Android P treble ROM until it's official so anything that I'm saying here has nothing to do with that if that's the image you're trying to install that I can't help you with it because I don't honestly know I remember reading something about that changing something different with it and I got to read up more on it.****
So next part depends on whether the GSI you're trying to flash comes with GFS included inside of it some do some don't I think most do but just make sure you read the instructions on the forms from where you download them from where they will tell you about the gf's the ones that I've installed that didn't have gf's on I would install mokee then I would flashed gf's to mokee but I've seen ones where people have flashed the gf's after flashing the treble images well and they didn't have any problem so just make sure you read into that one. obviously if the GS I can change the gf's then don't flash any before flashing or after as it will be flashed when we install it to the image and everything will be.
Which brings us to the last part if you did everything right up to this point then you should have no trouble installing the GSI through either TWRP or fastboot but before you do just make sure you go back to White and you just swipe to factory reset again so that we know that we cleaned out the data and we're on something clean after on encrypting the data if you did Flash no variety but remember don't wipe any partitions you want to make sure that you leave mokee on there. if you do it correctly you won't even need to wipe anything afterwards you should literally just need to be able to install the image into the system partition now and then reboot and it should work fine
It's your choice on how to go about doing it I've had success with TWRP but I've had more success using the fastboot method if for some reason you do try TWRP and it flashes and says success in 10 seconds then just reboot to fastboot mode in just flash it from there because you probably going to run into an issue just factory reset it again before you do it by swiping you don't have to wipe any of the partitions leave those alone.
So either go to the fastboot route which is put the phone in fastboot Point your terminal to the area where your GSI is located on your computer and then type fastboot flash system xxxGSI NAMEXXX.IMG.... OBVIOUSLY REPLACE THE FIRST PART WITH THE ACTUAL NAME OF YOURS. Next press enter and give it a few seconds and then you should see it's a success at which time you can reboot the phone and it should boot after a few short minutes.
If you wanted to use the twrp I believe I saw something about how you have to be on version 3.2.2 or above most likely for blue spark version as I use that one because it has treble support and I can see the vendor image even though I don't touch it. So if you flash it here you want to make sure instead of rebooting to fastboot like before you would just go to install and select image then find the image on your phone select it and then select the system images where you are installing it and then wipe the bar at the bottom for Flash and then upon it finishing you should hit reboot and let the phone boot up the first time set it up and then you can go back and you can go back to TWRP if you want to flash magisk or any other modules or TWRP Zips I've stated first then make sure you move the phone and go back and do all the modifying after otherwise you're getting stuck. I hope this helps feel free to contact me if you have any trouble.
theandroidas said:
Hi all,
so today I found a treble-enabled ROM of Android Pie and wanted to flash it. Thing is, I need to enable treble for me first. The treble check says that Treble is indeed supported, and so does the OnePlus website, but I don't have access to the vendor partition in TWRP. Using TWRP 3.2.3-1, by the way.
So, I read that MoKee enables Treble. Tried that, flashed the rom, flashed the radio and then the rom, factory wiped, flashed rom, factory wiped, flashed radio and rom, nothing. Still can't get Treble support. Then I tried kylothow's Trebliser, but nothing there either. I am realy at a loss here - I even reinstalled OOS (newest beta of course) and I couldn't get the vendor partition to show up, which is weird considering installing said trebliser actually states "Vendor partition found, good!" when installing, and then proceeds to in fact patch the vendor partition. It just doesn"t do anything, I can't install GSIs, can't even get the treble check to register that I do in fact have treble.
So this is where I turn to you guys. Do you have any idea what I could do in this situation? Please answer genuinely and don't post "just wait for an official android p".
Thanks!
Click to expand...
Click to collapse
Bro can u plz tell me how to get back to 8.1 oreo i am on 9.0 and didn't get treble support
Although I'm new to GSI system, I am not a newbie on the whole flashing thing. But I just can't seem to boot any of the roms out there. I got to install one, actually, but then on device startup there's a point I get to a screen saying my device is not certified and I can't get past it, just can't use the phone so that id apk thing won't do.
I have a Moto G6 Play and recently forced upgrade to android Pie soak test. I do follow instructions as they are taught: factory reset, flash GSI image, flash GApps if wanted, but nothing works. And, you might know, my device is treble enabled...
do not flash gapps.
I should first apologize for statements made in threads that said gsi's made the A8 crap and were not usable. There's a lot of work put into these projects and part of making them great comes from trying them on different devices and giving the results back to the devs.
After my whining i decided to shut up and make it an easier process to switch gsi's without having to re-partition anymore.
To my surprise this was a pretty easy process. And of course easy because of tools and info on Xda.
It can be flashed as soon as you are treble ready, or after trying a gsi or 3. Just wipe vendor, cache, dalvik, system and data.
It's for w variant so if there's interest i'll do one for F.
Has radio, app lock, and pretty much all basic features. Magisk can be flashed after first boot and requires apk for manager after flash/boot.
No gapps or patches needed. CSC features, no knox, and no places tab in dialer. It's made from latest release, which i never flashed. I am BL3 and it's fine.
Hope it helps. I don't think i am able to strip it more and put alternative choices... if so i'll include them.
https://mega.nz/#!3R5ihYyA
The link is a leaner version of the latest firmware. (sma530w) Anyone interested in making their own can use superr's kitchen. Does a fantastic job When I packed it I had my phone rooted and wired. Options ext4 and sparse.
No hassle transitions between stable and GSI images. Time to start messing with GSI images. Partitions remain treble throughout.
Just wipe everything except internal.
download key
Decryption key for mega?
mindlery said:
I should first apologize for statements made in threads that said gsi's made the A8 crap and were not usable. There's a lot of work put into these projects and part of making them great comes from trying them on different devices and giving the results back to the devs.
After my whining i decided to shut up and make it an easier process to switch gsi's without having to re-partition anymore.
To my surprise this was a pretty easy process. And of course easy because of tools and info on Xda.
It can be flashed as soon as you are treble ready, or after trying a gsi or 3. Just wipe vendor, cache, dalvik, system and data.
It's for w variant so if there's interest i'll do one for F.
Has radio, app lock, and pretty much all basic features. Magisk can be flashed after first boot and requires apk for manager after flash/boot.
No gapps or patches needed. CSC features, no knox, and no places tab in dialer. It's made from latest release, which i never flashed. I am BL3 and it's fine.
Hope it helps. I don't think i am able to strip it more and put alternative choices... if so i'll include them.
mega /#!3R5ihYyA
The link is a leaner version of the latest firmware. (sma530w) Anyone interested in making their own can use superr's kitchen. Does a fantastic job When I packed it I had my phone rooted and wired. Options ext4 and sparse.
No hassle transitions between stable and GSI images. Time to start messing with GSI images. Partitions remain treble throughout.
Just wipe everything except internal.
Click to expand...
Click to collapse
Oh man that is gone. I will make another one. Sorry i forgot all about that. I'll have it ready sometime late tonight. Have to work. If you have the ability, you can get superr's kitchen and it'll extract your system image. I'll see if i have time right now.
Ok pulling my current system image right now. There's no Chrome, and system webview works. LOTS of bloat removed and overall pretty lean. Might have it before work.
Ok uploading to google drive and it's REALLY slow. A system image is almost 4 gigs. I put boot and recovery in as well. If you're using the Canadian W variant you'll be fine. If you're with Virgin even better. If not, copy stuff from the VMC cscfeature.xml for the extras such as app lock, call recording, and others.
Ok so the best way for you to do this is to simply restore just "system" and "data" from a non treble back up. Oh and "boot" You"ll want to do a full wipe first of course (i do internal as well but up to you).
You'll notice your partitions remain treble and you can use treble images like you usually would.
Using my image is only good for my phone i think. Been busy and now with pie i am just getting the full download from sam. So i'll need to re-install linux (long story) and see how well it goes making a pie image that'll work in the w model A8 phones. Not too good at it so have patience!
dathius said:
Decryption key for mega?
Click to expand...
Click to collapse
If you're still looking for something like this, you could use the zipoed package i posted and get the same results.
I have been switching between descent and the post "one bleeping ui" in A8 with no problems and treble partitions. I wipe everything except internal in between. Vendor for a8 and a gsi, to pie debloat rom and back again. Sorry for the delay. Choices are getting much better now at least.
Hey there,
For the most part, I kind of understand how GSIs work and how you're meant to flash them. But the information on both of those things are honestly really scant right now. As such, I have a couple of questions to ask with regards to how they function and how they affect my approach to "dirty flashing" them.
1) The Resurrection Remix GSI thread states to wipe /system. Correct me if I'm wrong, but wouldn't that completely break everything and not work at all? At least in the case of my device (Moto G6 Play), I'm fairly certain it has to be sitting on top of stock firmware to work...which would be removed if you wiped /system.
2) Whilst I'm aware you can easily throw "Derivative" GSIs like Descendant on top of Phh's AOSP GSI with minimal repercussions, what about dirty flashing derivative GSIs onto derivative GSIs? Currently, I'm on the aforementioned Descendant and wish to try out the Resurrection Remix GSI, but I figure that since they both add custom stuff to the AOSP base, it might mess something up if I just dirty flashed - or would any problems be fixed by the factory reset that comes afterward?
3) Is there seriously no way to have a fully "clean" GSI installation without going back and starting from the beginning by reinstalling stock FW then going through the process of flashing the GSI etc? Is Dirty Flash + Factory Reset my only option with this?
I know these all probably have very obvious answers that I somehow can't see, but I appreciate your patience. Thanks!
Howdy!
Please forgive me if this is the wrong place / my google-skills are insufficient!
This is my first post to this forum, because I can't resolve what part is important in rooting (w Magisk?) my RN8P.
First about myself (and my abilities): I did flash some phones (S4 mini, Zenphone2, Yoga Tab 3 plus) with TWRP and Lineage, so basic knowledge should be present, but nothing "in depth"!...
What I did to my RN8P (begonia, global, EU):
OTA-Updated to MIUI A10
Unlocked Bootloader
Reflashed MIUI A9 (because reasons )
Fastboot flashed lk & preloader from CFW MEGATHREAD & non-CFW TWRP
Flashed crDroid (with CFW and TWRP batch) and the crDroid Rom itself w. openGapps via TWRP
What I want to achieve:
Limit my battery charging to a certain percentage
Maybe use the often praised camera app praised with magisk
Let the rest of the system "as is", so have AntiBrick, TWRP and "invisible" Root
Maybe use other magisk-goodies
Versions used:
CFW A10 20200530
TWRP from crDroid-pkg (3.3.1-0)
crDroid 10 20200721 begonia
open gapps arm64 / 10 / pico / 20200730
My question:
I've read about installing MAGISK can trip the AVB, which is to avoid at all costs(?!?), so where is my starting-point for MAGISK?
So what are the pitfalls I have to avoid / consider? / Which guide to follow on how to do it proper?
Forgive my ignorance, any help / bump in the right direction is highly appreciated!
Thoughts so far
Hey!
I think my understanding has grown a little bit...
There is only one Version (no A - A/B) of MAGISK any more, so no fuss about picking the right tool. And being brought via zip-file for flashing within TWRP seems very convenient.
There seem to be TWRP-versions out there, which can mitigate the AVB-tripping for our RN8P, are they CFW compatible? (and which is recommended?)
So basically these questions remain:
Which exact TWRP-version is recommended?
Shall I completely reflash CFW, crDroid, openGapps, when I flash MAGISK? Or just wipe cache / davlik and reset to factory?
Are there other pitfalls or downsides of using MAGISK in my combination of Hard & Software?
Cheers, Mecky85
Not using CFW (Stock MIUI with Magisk benefits), but here is some advice:
0. Make sure you follow every step on TWRP site (especially the vbmeta flashing part). It can save you from headache. I don't say you have to use TWRP, tho. Also make sure you do this step if you return to stock boot image. Do it once, and you are fine.
1. Use CFW-compliance recovery, as recovery has it's own firmware.
2. In my case (I'm doing update with this procedure: MIUI+Magisk>vanillafy>update MIUI>Mod), no need to reset anything. But resetting dalvik+cache is not bad either.
3. Out of question.
Hope that help.
Thanks for the headsup with vbmeta, will have time to look (and hopefolly have a got at it) after the weekend!
Will post my experiences in here.
After a good batch of reading into the topic... I'm not convinced any more I'll cope with it...
Not worth for me to figure everything out, if reading into this is such a hassle... :silly: