Develop Bugs

RN8Pro EEA TWRP & Root

So,
I have a RN8PRO running MIUI 11.0.3, on Android 9 (PGGEUXM)
From my understanding, it says global on about phone, but this is really EEA.
My question is, do all Global TWRP and Magisk support EEA?
How do I know this is a chinese device running PGGEUXM?
Has anyone put TWRP and rooted there phone running this software?
What is the best TWRP for this device? Should I go for the Official one or are there better ones that perhaps support OTA updates?
Why do some guides tell you to disable AVB where as others don't?
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
And why do some guides tell you to delete "recovery_fromboot.p"
My ultimate goal would be to have a custom recovery and root on stock MIUI.
I'm hoping someone could clear this up and perhaps reduce the rate of bricking phones! I will be using AgentFabulous preloader & lk.img as well in a preventive measure!
Tia!

I have the global model as well, LR-TWRP is what you want as most others will give you a black screen. If/when you upgrade to Q, there's an LR-TWRP that supports that too. Nice thing is, it comes with AVB and dm-verity feature built in. The regular Magisk will work fine too.
I removed the recovery_boot file as it would flash stock recovery on reboot if I didn't. Try it without and see.

wang1chung said:
I have the global model as well, LR-TWRP is what you want as most others will give you a black screen. If/when you upgrade to Q, there's an LR-TWRP that supports that too. Nice thing is, it comes with AVB and dm-verity feature built in. The regular Magisk will work fine too.
I removed the recovery_boot file as it would flash stock recovery on reboot if I didn't. Try it without and see.
Click to expand...
Click to collapse
Okay thanks, that clears quite a few things up, I believe in that case I'm going to follow pritish1998 guide on this, as he is uing LR-TWRP. I'm so out of touch it's been years since I've done any of this previously owning an s7 edge for 4 years.

Clarification needed regarding rooting and bootloader for installing LineageOS 17.1

Hi all,
so my current smartphone died for good and instead of getting a new one, I thought I'd revive my old Sony Xperia Z1 Compact. It's been a while since I switched it on so the battery is dead but I'm planning to buy a new battery and replace it. Then I plan to install LineageOS (which is based on Android 10 I believe?)
However I've never done rooting or anything more than basic end user stuff so I've searched the internet and thought I needed to root my phone and then flash the LineageOS. I've read some beginner guides on this forum and other places. However, I've ran into some conflicting/confusing(?) info and need some clarification before starting out. Hope someone can help with my admittedly-very-noobie questions:
1) Can I install LineageOS WITHOUT rooting my phone?
I believe that the bootloader needs to be unlocked first but is rooting necessary? The reason being is that I just want to get rid of the current stock ROM (I think it was Lollipop - can't know for sure because the new battery hasn't arrived yet) and install LineageOS. I don't want a rooted phone because it might conflict with banking apps and such (I know there are workarounds i.e. masking/reflashing/unrooting but as I am not that familiar with the development systems I will just be exposing myself to unknown vulnerabilities) so is it possible to just have the custom ROM and not completely root the phone?
2) Unlocking the bootloader
So I read I have to do a backup first before unlocking the bootloader. Is an SD card necessary or only for rooting? Since unlocking the bootloader will format the SD card anyway? Where should the backup be stored then?
I'd really appreciate some guidance. Thanks!!
Cheers,
traegr

LineageOS or most other roms aren't rooted by default. You will have to install solutions like magisk.
If you install twrp https://forum.xda-developers.com/sony-xperia-z1-compact/development/recovery-twrp-3-3-1-t3960699 make sure you are on latest stock firmware as you need the latest bootloader which allows booting into recovery. Flash firmware with Xperia Flashtool which has inbuilt firmware downloader. http://www.flashtool.net/index.php
If you can't boot into TWRP, you can try flashing attached file with xperia flashtool.
Instead of unofficial lineage I recommend AICP forum.xda-developers.com/sony-xperia-z1-compact/orig-development/rom-aicp-15-0-q10-0-amami-t4005457 . It's got good battery life and nice inbuilt tweaks and customization options..
Hope this helps

Also you need to flash Gapps if you want to use certain apps. Important point for AICP is that you can use microg instead. https://microg.org/

drater2 said:
LineageOS or most other roms aren't rooted by default. You will have to install solutions like magisk.
If you install twrp https://forum.xda-developers.com/sony-xperia-z1-compact/development/recovery-twrp-3-3-1-t3960699 make sure you are on latest stock firmware as you need the latest bootloader which allows booting into recovery. Flash firmware with Xperia Flashtool which has inbuilt firmware downloader. http://www.flashtool.net/index.php
If you can't boot into TWRP, you can try flashing attached file with xperia flashtool.
Instead of unofficial lineage I recommend AICP forum.xda-developers.com/sony-xperia-z1-compact/orig-development/rom-aicp-15-0-q10-0-amami-t4005457 . It's got good battery life and nice inbuilt tweaks and customization options..
Hope this helps
Click to expand...
Click to collapse
Hi, thanks for replying.
What's the difference between the lineage and AICP?

traegr said:
Hi, thanks for replying.
What's the difference between the lineage and AICP?
Click to expand...
Click to collapse
AICP provides more customizations while lineage is a "cleaner" approach. In the end AICP builds on top of lineage sources and adds several features. It totally depends on your personal taste. I consider it to be a bit overloaded. But that's my opinion. Which may be a bit influenced as I build the lineage version. Hehe
But once you have a recovery set up you can easily flash one, test it, and try the other one afterwards.
Hardware functionality should be same as AICP (SpiritCroc) and lineage (mse and me) share the same device tree sources. If one of us repairs something the other one will also get the fixes.
Both AICP and lineage have OTA update support. If you need microg you can either go with AICP 15 (Android 10) or Lineage 16 (Android 9).

Also you can easily backup your entire system with twrp if something goes wrong when flashing or whatever.
And when "hopping" roms you can make backups with Titatnium (root needed)

Need some starting help

Hello guys,
I recently bought a used OnePlus 7T, with the goal in mind, to try to install Ubuntu Touch on it. There were some tries to do this in the past, there is posts on the forums here where a 7 Pro was successfully running UT.
Now while I am a software developer, I am a total beginner regarding 1) UT porting 2) Android in general. I have never used an Android device, and I am unfamiliar with the OS and all related terminology. The latter seems to give me some headaches at the moment, so I would like to ask you guys for some starting help.
When I received the phone it was running OOS 11, and I downgraded to OOS 10 as described here after I unlocked the boot loader and also installed TWRP (I think this was not needed yet, but well ...). And I think I didnt pay enough attention to it, since now it does not seem to be the EU version anymore; the about page tells me: "10.3.1.HD65AA", which I think means global? Does it have any impact on the functionality of the phone? Can I switch back to EU version? If so, how? Should I pick a EU-zip from here and flash it again?
Now since I was trying to downgrade even further to android 9 (in order to begin with the Ubuntu Touch related stuff), I tried to find a ZIP containing the OOS 9 downgrade, but I could find none. The closest which I found was this. However when I place the downloaded ZIP in the root folder ("OnePlus 7T" is the root folder? E.g. the one where I see subfolders like ".OTA", "SysQS", "TWRP"?), the system update will not pick it up in the local upgrade menu. It just doesn't find it. I already renamend it from .jar to .zip, but still it does not work. This makes me believe I downloaded the wrong ZIP.
Long story short, can someone help me to achieve the following:
1) Switch back to EU version
2) Downgrade to OOS 9
And I have some general questions:
1) TWRP is a tool which is installed on the recovery partition of the phone, and it can be booted into to install various things. It would for example allow to install a different Android version, as alternative to system -> software update -> gears -> local. Is that a correct summary? For which step would I actually need TWRP during the a) the downgrade process from 11 -> 9 and b) porting to UT?
2) Does the phone need to be rooted during the downgrade process, or when porting to UT?
3) What are the two slots which are shown in TWRP? Are those 2 partitions on the internal storage?
4) How many partitions (in the regular PC sense of partitions of a hard disk) does the phone have? 2? One for recovery, and one for the operating system? In the UBPorts docs I read that the vendor blobs reside on a separate partition since Android 9, so there must be at least 3 partitions on the phone? How do I make sure that I don't accidentially write e.g. on the vendor blobs partition? I guess that `fastboot flash recovery twrp.img` means that the *recovery* partition should be flashed, right?
I think thats it for now. Sorry for the wall of text, but its just so much information for a beginner, and its a bit overwhelming. But I want to get into it bit by bit, and maybe in the end contribute to the device porting, in case I manage to do it.

I don't think there is oos9 for op7t

Nope, came with oos10

Question A bunch more questions from a noob

As title really, never flashed a custom ROM (at least not since my Galaxy S2) and while wait the 7 days to unlock the bootloader i'm trying to gather as much info as possible. So here goes;
1) Whilst I wait for the bootloader to unlock can I still turn off my phone and swap sim cards or will it reset the timer?
2) My Poco F3 is on MIUI Global 13.0.7.0 (SKHEUXM) - do I need to downgrade to 13.0.3.0 as per the instructions here?
3) The instructions for installing Crdroid lists an optional step for installing "DFE" but I cant seem to find out what DFE actually is.
4) Is it important to know if my phone has an A/B partition system and if it is how do I check for it?
5) After installing Magisk what other modules/tools/apps do I need to ensure Google Pay/Wallet will work as it seems a recent update has made it harder to fix.
6) Are there any bits of advice you can give for a avoiding a bootloop and/or bricked phone situation? Are there any common mistakes people make leading to a bootloop or bricked phone?
I think that's everything for now
Thanks

Goooober said:
As title really, never flashed a custom ROM (at least not since my Galaxy S2) and while wait the 7 days to unlock the bootloader i'm trying to gather as much info as possible. So here goes;
1) Whilst I wait for the bootloader to unlock can I still turn off my phone and swap sim cards or will it reset the timer?
2) My Poco F3 is on MIUI Global 13.0.7.0 (SKHEUXM) - do I need to downgrade to 13.0.3.0 as per the instructions here?
3) The instructions for installing Crdroid lists an optional step for installing "DFE" but I cant seem to find out what DFE actually is.
4) Is it important to know if my phone has an A/B partition system and if it is how do I check for it?
5) After installing Magisk what other modules/tools/apps do I need to ensure Google Pay/Wallet will work as it seems a recent update has made it harder to fix.
6) Are there any bits of advice you can give for a avoiding a bootloop and/or bricked phone situation? Are there any common mistakes people make leading to a bootloop or bricked phone?
I think that's everything for now
Thanks
Click to expand...
Click to collapse
1) Yes.
2) No, 13.0.3.0 is the required minimum, you can always use higher.
3) It disables forced encryption.
4) Poco F3 is A/B.
5) If any issues arise, you can always hide magisk and use safetynet fix.
6) When people don't follow installation instructions properly.

Dfe is disable force encryption but i dont think it works for android 12 so no need to flash it

ApexPrime said:
Dfe is disable force encryption but i dont think it works for android 12 so no need to flash it
Click to expand...
Click to collapse
It works, with DFE you can flash files from internal storage in twrp. But it also compromises phone security, so it's recommended not to use it.

If my phone is A/B do i have to do anything different when i flash Crdroid in TWRP?

Goooober said:
If my phone is A/B do i have to do anything different when i flash Crdroid in TWRP?
Click to expand...
Click to collapse
Almost all modern phones now ship with A/B partitions. So no, just follow the instructions given by the rom developer.

1. I unfortunately can't answer.
2. I wouldn't, 13.0.3 to 13.0.7 is very minor
3. DFE = Disable-Force-Encrypt = Android by default is encrypted.
DFE.zip removes the Boot-argument responsible for encrypting the Userdata-partition on the first boot, located in /vendor/etc/fstab
4. Poco F3 has an A/B-Partitionlayout. Most phones released with ~Android 10+ have A/B.
5. Personally, with the recent change, I tried many things to get GPay to work, got fed up with the Cat & Mouse Game with Google, and locked my BL.
6. If you flash using Fastboot Mode and the Flash aborts during a Partition-flash, don't reboot your phone, because otherwise your phone may never reboot back into Fastboot etc, and only show a Black screen.
ApexPrime said:
Dfe is disable force encryption but i dont think it works for android 12 so no need to flash it
Click to expand...
Click to collapse
It works on Android 12.
Goooober said:
If my phone is A/B do i have to do anything different when i flash Crdroid in TWRP?
Click to expand...
Click to collapse
No difference.
Further Notes about DFE:
If you don't use DFE before First Boot, userdata-partition gets encrypted, which means, beyond that, only TWRP SKKK will be able to access the userdata-partition.
If you decide to flash DFE once, you must flash it directly after every Update in TWRP, otherwise your phone may bootloop. At least that was the case for me! Before an update I decided I want my storage encrypted, but I got a bootloop. ^^
I wouldn't use DFE. Just leave it encrypted.

cyanGalaxy said:
5. Personally, with the recent change, I tried many things to get GPay to work, got fed up with the Cat & Mouse Game with Google, and locked my BL.
Click to expand...
Click to collapse
If you lock your bootloader after flashing a custom ROM does the custom ROM still work as intended or do you have to go back to stock?

Goooober said:
If you lock your bootloader after flashing a custom ROM does the custom ROM still work as intended or do you have to go back to stock?
Click to expand...
Click to collapse
Your phone will bootloop if you do that, because locked bootloader prevents custom roms from starting, thus it can only be used on stock roms.

Goooober said:
If you lock your bootloader after flashing a custom ROM does the custom ROM still work as intended or do you have to go back to stock?
Click to expand...
Click to collapse
No, I don't use a Custom ROM anymore. I'm back to Stock ROM, MIUI 13.0.7 for Europe.
Don't lock the BL with a Custom ROM. Only the Official ROM. Otherwise you risk hardbricking your phone.

ROOT Android 12 , Redmi Note 9 Pro (Joyeuse)

Hello, I've tried and "tested" pretty much everything with my Joyeuse, from various custom roms, recovery and root. It even had been totally "destroyed" many people know the event, when nothing seems to work anymore and it with a lot of trouble getting it back. Now I've come to the conclusion that a normal Miui firmware Global or EEA with Magisk ROOT is completely sufficient and the "best", despite everything still n few.I would like My current MIUI 14 Android 12 rooting, with Magisk 26.1 now it's getting "exciting".I'am really Not a Expert
-TWRP 3.7.0 12-0 FBEv2 joyeuse-dereference.zip / img ??
-PBRP miatoll 4.0 202330404 official.zip / img ??
-OrangeFox joyeuse stable R11.1_4_A12.zip / img
??
Now comes the point where I don't quite see through, need some FBE Recovery something with disable/No verity opt encrypt and as that doesn't mean everything, there are 2-3 different ones. I have to despite.....something else the vbmeta.img and all the other things that aren't there???
Could someone PLEASE help me with this.
Does ROOT of "Original" Global Firmware work??
How and in which order ???????if something with disable/no verity opt encrypt (no idea which of the 2-3 there are) when which and when??
If what with vbmeta.img, which one and when?
And which of the 3 recovery, all 3 have FBE, or am I misunderstanding it even more than I think and a recovery without FBE??
Which steps And order to ROOT with Magisk?
Magisk 26.1 good?Or another better??
1. - Recovery Install with PC and fastboot
2. - Boot into recovery.
3. - ????
4. -?????
5. -????
Etc ,etc
Must be Install Disable/No verity opt encrypt or vbmeta.img??Or somthing like this??
What steps and in wich order are the best for save Root MIUI 14 Global or EEA?
Forgive me if I repeat myself!!!!And for my bad bad English
Best regards
Michael
If this post ended up in the wrong place, please forgive me and "move" it to where it "belongs".