So I managed to root+unlock my Mate SE bootloader and test drive a couple of GSI roms, mainly from OpenKirin. The problem is they take their sweet time to release new builds (RR latest build is from september, for example) and I'd like to try some other roms.
However, most of the roms from Phhusson don't run and roms from other sources require twrp, which on my phone has been totally useless with all kinds of errors and totally unable to flash anything at all, so I'm stuck with fastboot roms.
Is there a specific sequence in which I have to do things in order to flash roms that require twrp?
So far, the only way I can install roms is fastboot mode -> fastboot flash image -> boot to recovery -> factory reset+wipe -> reboot to system. Any other way doesn't work for me. Also, what is an oreo/pie friendly version of twrp for the Mate SE?
I also have the Mate SE but use TWRP and around 3/4 work from on the treble roms page work, maybe you could try using the TWRP method (theres a guide on here named something like how to install resurrection remix)
Thanks a lot! Can you point me to a twrp that's proven to work on pie roms?
Related
Hey guys,
I have recently bought my "Whyred" (4/64 global) and have already unlocked the bootloader.
After switching to Miui 10 global developer rom (with official MiFlash Tool) I wanted to test some custom roms. Therefore I have enabled the developer options, USB-Debugging and OEM Unlock. After this I have booted TWRP 3.2.2.0 with fastboot and flashed the TWRP image to the phone via the booted recovery. Followed by the no-verity-opt-zip (6.0) and Magisk v16.7 to root the phone.
On this basis I went back to the recovery and did a factory reset, followed by an advanced wipe of dalvik, cache, data, system and vendor. Afterwards I have moved the whyred-treble-vendor (zip-file) and the PixelExperience GSI to my phone. First I have flashed the vendor-zip and then switched to image and flashed the GSI as system-image.
And now comes the problem: when I try to reboot to the system it always states "No Os installed". By wiping the cache and data again, I am able to boot to the system, but the phone is stucked on the Mi-Logo
After recovering my phone with the MiFlash Tool (Miui 10 global developer rom), I have tried to flash the GSI in different ways according to a lot of guides I have found in the net, but nothing is working. All methods are leading to the same result: my phone stucks on Mi-Logo
Could anyone of you give me a hint about what I am doing wrong?
Thank you!
Best regards,
nkl
At a guess with wiping system and data. Your also removing changes done by "no-verity-opt-zip (6.0)", and since your still using the MIUI Bootloader the device won't boot the associated GSI.
Maybe try flashing/booting a Treble enabled custom rom, first and then install your GSI. Or avoid the whole Treble thing and just use a custom rom.
You may get more assistance in Treble specific threads/forums.
corkiejp said:
At a guess with wiping system and data. Your also removing changes done by "no-verity-opt-zip (6.0)", and since your still using the MIUI Bootloader the device won't boot the associated GSI.
Maybe try flashing/booting a Treble enabled custom rom, first and then install your GSI. Or avoid the whole Treble thing and just use a custom rom.
You may get more assistance in Treble specific threads/forums.
Click to expand...
Click to collapse
Hey,
Thank you for your quick reaction!
But did I get something wrong? Doing a factory reset and then doing an advanced wipe of dalvik, cache, data, system and vendor is more or less an essential part of all the guides out there?
So you think, I should try to flash for example LineageOS first and then take an approach on the GSI? And which steps should I take? Should I flash no-verity-opt and Magisk under Miui 10 global dev first and then flash custom, i.e. LineageOS? Or should I flash LineageOS first (on a fresh Miui dev rom) and then no-verity-opt and Magisk?
Thanks!
@nkl0806 After installing the GSI while using MIUI as the base you could try flashing no-verity-opt before trying to boot.
no-verity-opt is only required on MIUI based roms (or in your case with a GSI).
Flash a custom rom and boot it. Don't worry about magisk etc.
Then install your GSI and boot it, avoid flashing magisk or gapps.
Once it boots, go back and install magisk and gapps etc and wipe data.
Hopefully then boot and setup your GSI rom.
Also make sure your using a Treble enabled TWRP!
Noob guide to install GSI on whyred
Again look for support in Treble Threads/Forums, I haven't experiment with it, so only going by what I have read.
corkiejp said:
@nkl0806 After installing the GSI while using MIUI as the base you could try flashing no-verity-opt before trying to boot.
no-verity-opt is only required on MIUI based roms (or in your case with a GSI).
Flash a custom rom and boot it. Don't worry about magisk etc.
Then install your GSI and boot it, avoid flashing magisk or gapps.
Once it boots, go back and install magisk and gapps etc and wipe data.
Hopefully then boot and setup your GSI rom.
Also make sure your using a Treble enabled TWRP!
Noob guide to install GSI on whyred
Again look for support in Treble Threads/Forums, I haven't experiment with it, so only going by what I have read.
Click to expand...
Click to collapse
Thank you!
I have also followed this noob guide to flash the GSI, but it did not work out. Maybe I should really skip the Treble stuff and just use the normal custom rom!
I will try to flash the PixelExperience rom and not the GSI - or maybe follow another Guide and flash the Mokee rom first as a base for the GSI.
Thanks again!
Okay, lemme get this clear that I'm not a pro in all this stuff. Infact, I'm a total idiot.
I have tried to flash a lot of ROMs on my Moto G5 (cedric) but only 3 of them have worked, namely:
1) Pixel Expirience 7.1.2
2) Ressurection Remix 7.1.2
3) Viper OS 7.1.2
I don't know whats the problem and whether it is with my phone or the ROMs. Also, even after i used these ROMs, the apps which need root access weren't working and yes i did select the Root Access setting to ADB only(cause thats was the only option other than Off). Plz help me guys.....
Astitva_ said:
Okay, lemme get this clear that I'm not a pro in all this stuff. Infact, I'm a total idiot.
I have tried to flash a lot of ROMs on my Moto G5 (cedric) but only 3 of them have worked, namely:
1) Pixel Expirience 7.1.2
2) Ressurection Remix 7.1.2
3) Viper OS 7.1.2
I don't know whats the problem and whether it is with my phone or the ROMs. Also, even after i used these ROMs, the apps which need root access weren't working and yes i did select the Root Access setting to ADB only(cause thats was the only option other than Off). Plz help me guys.....
Click to expand...
Click to collapse
First you need to say how you have done the flashing of roms and which rom didn't flash, or what error you got while installing the rom. And second is you need to install magisk manager to gain root access with twrp, by enabling the root access in developer option won't give you root access you need to install it via twrp.
riyan65 said:
First you need to say how you have done the flashing of roms and which rom didn't flash, or what error you got while installing the rom. And second is you need to install magisk manager to gain root access with twrp, by enabling the root access in developer option won't give you root access you need to install it via twrp.
Click to expand...
Click to collapse
I tried flashing them through TWRP. They all were based on Oreo 8.1. I tried Lineage, Invicta, Viper, RR and pixel expirience. As for the error, i don't really know what error it was but Lineage and RR were stuck on the boot loader and the rest just didnt flash.....
Astitva_ said:
I tried flashing them through TWRP. They all were based on Oreo 8.1. I tried Lineage, Invicta, Viper, RR and pixel expirience. As for the error, i don't really know what error it was but Lineage and RR were stuck on the boot loader and the rest just didnt flash.....
Click to expand...
Click to collapse
Chance are you are using the wrong twrp
64bit roms require you to use the 64bit twrp
See the first post of the lineageos thread for the 64bit twrp
Or you can test out the 64bit twrp that uses my encryption edits
https://forum.xda-developers.com/g5/help/help-testing-build-twrp-arm64-t3874472
If you want to root flash the latest version of Magisk and then install the magisk manager app manually if it's not installed
TheFixItMan said:
Chance are you are using the wrong twrp
64bit roms require you to use the 64bit twrp
See the first post of the lineageos thread for the 64bit twrp
Or you can test out the 64bit twrp that uses my encryption edits
https://forum.xda-developers.com/g5/help/help-testing-build-twrp-arm64-t3874472
If you want to root flash the latest version of Magisk and then install the magisk manager app manually if it's not installed
Click to expand...
Click to collapse
I'm sorry but i didn't get what you said. I'm really sorry but I'm really a noob. I would like it if you helped me out a bit....
Astitva_ said:
I'm sorry but i didn't get what you said. I'm really sorry but I'm really a noob. I would like it if you helped me out a bit....
Click to expand...
Click to collapse
All custom oero roms for this device are 64 bit
You need to flash them with a twrp that has been compiled for 64bit twrp use
My official twrp is for 32bit roms only and will not flash 64bit roms - you will get error 7 or I think error 256 or something like that
Flash the 64bit twrp if you want to flash 64bit custom roms - process is the same as if flashing the official twrp via fastboot but you obviously use the 64bit twrp image instead
As mentioned link to 64bit twrp is on the lineageos 15.1 thread first page or try the version in the link I posted in previous post
TheFixItMan said:
All custom oero roms for this device are 64 bit
You need to flash them with a twrp that has been compiled for 64bit twrp use
My official twrp is for 32bit roms only and will not flash 64bit roms - you will get error 7 or I think error 256 or something like that
Flash the 64bit twrp if you want to flash 64bit custom roms - process is the same as if flashing the official twrp via fastboot but you obviously use the 64bit twrp image instead
As mentioned link to 64bit twrp is on the lineageos 15.1 thread first page or try the version in the link I posted in previous post
Click to expand...
Click to collapse
So, I can directly flash the new twrp like i flash the roms right?? Also, what can i do for project treble in my phone...i mean, i cant find redwolf for moto g5(cedric)
Astitva_ said:
So, I can directly flash the new twrp like i flash the roms right?? Also, what can i do for project treble in my phone...i mean, i cant find redwolf for moto g5(cedric)
Click to expand...
Click to collapse
You flash twrp via fastboot commands
fastboot flash recovery recovery.img
Although it is technically possible to flash twrp via twrp if you select image flash & select recovery as the image you are flashing but I'd stick with the fastboot method
I don't own this device anymore so no idea about files that are no longer available
TheFixItMan said:
You flash twrp via fastboot commands
fastboot flash recovery recovery.img
Although it is technically possible to flash twrp via twrp if you select image flash & select recovery as the image you are flashing but I'd stick with the fastboot method
I don't own this device anymore so no idea about files that are no longer available
Click to expand...
Click to collapse
Okay, so i flashed the twrp...but still therom isnt flashing....should i upload the rom so that you can see it?
basically;
if a rom has [64bit] in the title, then it's 64 bit, if it is then you need a 64bit recovery which you can easily find on the forum. you dont even need to know what that means.
Astitva_ said:
Okay, so i flashed the twrp...but still therom isnt flashing....should i upload the rom so that you can see it?
Click to expand...
Click to collapse
Just link to the rom on xda and give the twrp error
The rom either isn't for this device eg you are trying to flash a moto g5 plus or s rom or you are using the wrong twrp or you haven't formatted system data cache before flashing the rom
Hello.
When I Am Trying To Flash Custom Rom (MIUI EU, or others) Twrp Ask To Restart In TWRP To Continue Update 1/2 Completed.
But It Dont Open Twrp When I Reboot In To Recovery It Didnot Boot It Shows Some Custom Recovery Which Is Useless.
What Can I Do To Fix That ?
Thank You In Advance.
You don't seem to be very experienced with that kinda stuff. Watch a tutorial on YouTube on how to flash a Custom ROM like Xiaomi.eu (i think that's what you mean?).
You'll find a lot of tutorials for that. I can recommend "Munchy", he's a good YouTuber, makes very clear tutorials on how to do stuff on Xiaomi devices.
dreamytom said:
You don't seem to be very experienced with that kinda stuff. Watch a tutorial on YouTube on how to flash a Custom ROM like Xiaomi.eu (i think that's what you mean?).
You'll find a lot of tutorials for that. I can recommend "Munchy", he's a good YouTuber, makes very clear tutorials on how to do stuff on Xiaomi devices.
Click to expand...
Click to collapse
i am so experienced but i am new on a/b partitions so ... i havenot find that videos how to flash custom roms on new phones everyone just flash that but when i try to flash it stuck 1/2 and flash end unsuccesful it tells to restart device to continue install but when i restart twrp is gone...
Well. Of course you are going to find a new recovery.
Look. To avoid any issues.
- Flash official
- reboot to fastboot once you see MIUI boot animation.
- boot TWRP vasi to get to inject TWRP again. Since when you reboot to recovery you return to another recovery which is the flashed ROM.
- Then reboot to recovery
-Format data
-Reboot to system.
And that's all. If you're having issues following the steps. You better watch a video on YouTube.
Hi all,
I have recently shifted from Samsung A52S to Onpelus 9 PRO.
I'm now a bit confused about flashing method....
I mean :
on Samsung devices, you have to use ODIN ( that is a Fastboot replacement tool ) in order to flash the TWRP and then, on TWRP, you can freely flash any new custom ROM or any other img files, by simply press "INSTALL" button instad of ADB sideload commands.
If I well understood, in order to flash this custom ROM, I have to do that through Fastboot commands before and through TWRP ADB sideload commands after......
My question is : may I flash boot.img / vendor_boot.img / dtbo.img and ROM zip directly through TWRP "INSTALL" button instead ???
If not, can someone kindly explain which is the reason why ?
Sorry for this noob question but I'm doing my first step into Oneplus and I don't want to do a mess.....
Many thanks for the help !
I personally been wanting to know why we no longer can simply flash custom roms via TWRP like we use to. I do believe its got to do with the way the A/B partition works however that does not really answers why we can't just flash via TWRP. Unfortunately, I have not been able to find the answer so I am interested too on why we can't simply flash custom roms in TWRP and have to resort in sideloading or via fastboot. I would think flashing via a zip in TWRP will have less user errors compare to using a command line to do your flashing.
Saying that, I have been flashing via fastboot since I got this phone and even though its a longer process, it only takes a few more minutes.
twrp is not even fully adapted for android 12 or 13 (but who needs twrp anymore?)
I prefer to flash via fastbootd
(is less work for me)
best way is the magisk install
ChrisFeiveel84 said:
twrp is not even fully adapted for android 12 or 13 (but who needs twrp anymore?)
Click to expand...
Click to collapse
twrp is still the only way to backup the whole rom
it exist a non official version for 12/13
TWRP is the best tool to recover files when the OS does not boot. Since there is no ROM or kernel out there that recommend or uses TWRP for flashing. There is little reason to use TWRP unless is for file recovery. This is in respective to OP 9.
Hi everyone,
I'm writing this blog post to ask for some help from the XDA community. I have a Samsung A22 SM-A225F and I want to install a custom ROM on it, preferably an Android 12 GSI. However, I'm having some trouble getting it to boot properly.
I'm following the directions on this blog post which claims to have successfully installed Android 12 GSI on the same device. The steps I'm following are as follows:
Use Odin tool to flash the stock verified ROMs on my phone to start from zero.
Flash the (magisk patched.tar) file on AP
Boot to Android and set it up then install Magisk app to check for root (I'm doing this because it doesn't work otherwise)
Flash TWRP and run multidisabler then boot again to check if everything is working.
Finally flash the system.img, I'm not sure about vbmeta so I'm skipping it.
But I keep getting a bootloop no matter what I try, I've tried wiping cache and everything.
Weirdly enough I have flashed stock Android like two days ago except that it actually booted to set up but it didn't detect the network and kept mini rebooting from time to time.
I've tried the steps in that blog for Android 11 to flash crDroid but that also didn't work, I've also tried flashing crDroid even when following the steps for Android 12. Still no success.
I'm wondering if anyone has any idea what I'm doing wrong or what I can do to fix this issue. I've read some other guides on how to install custom ROMs and GSIs on Samsung devices without TWRP but they seem too complicated for me.
If anyone can help me out or point me in the right direction, I would really appreciate it. Thanks in advance! and i'll gladly provide any information required when i have time as it's currenlty night time
what twrp u using also where u flashing it using fastboot or from TWRP ?
i recommend u using fastboot to flash GSI