I think I understand the idea behind the device-specific Treble system, and the device-agnostic GIS images, which can work on any phone that has Treble. The app "Treble Check" says that the Sony Xperia 10 III is fully supported.
Here's my questions / educated guesses, please tell me if they're wrong or right:
1. This phone already comes with a Treble-compliant hardware layer (kernel+drivers) and GSI-compliant user-facing ROM, directly from Sony.
2. I can install any other GSI ROM (or from XDA) as long as it's an A/B arm64 ROM, and the hardware should work perfectly.
3. Can the phone still get OTA vendor updates for the hardware stuff after I unlock bootloader/install 3rd party GIS, or do I have to get the new images and flash them manually? Or do I get cut off from them altogether?
4. The original bootloader can take commands from the standard fastboot util in the Android SDK Platform Tools.
5. I understand I need to unlock the bootloader in order to be able to flash anything, but why is it necessary to overwrite the vbmeta partition?
6. Is the procedure to get Magisk working still patching the bootloader, regardless what GSI ROM I install?
7. Did anybody pass Safety Net with Magisk and a 3rd-party GIS ROM? Can it be passed anymore after unlocking bootloader?
8. I see there's no TWRP recovery for this device. Does it matter? Are there alternatives? In theory, if I have Magisk->root I can do pretty much anything so it doesn't sound like a big deal.
wirespot said:
1. This phone already comes with a Treble-compliant hardware layer (kernel+drivers) and GSI-compliant user-facing ROM, directly from Sony.
Click to expand...
Click to collapse
Yes.
wirespot said:
2. I can install any other GSI ROM (or from XDA) as long as it's an A/B arm64 ROM, and the hardware should work perfectly.
Click to expand...
Click to collapse
In theory. In practice it still depends on how the GSI ROM was implemented, there can still be issues.
wirespot said:
3. Can the phone still get OTA vendor updates for the hardware stuff after I unlock bootloader/install 3rd party GIS, or do I have to get the new images and flash them manually? Or do I get cut off from them altogether?
Click to expand...
Click to collapse
Not totally sure about this one. I think you don't get to install OTA updates anymore. You can probably download a new firmware with XperiFirm and flash pieces of it but no idea how that would work or what would happen.
wirespot said:
4. The original bootloader can take commands from the standard fastboot util in the Android SDK Platform Tools.
Click to expand...
Click to collapse
Yes. Sony did a great job going for standard things.
wirespot said:
5. I understand I need to unlock the bootloader in order to be able to flash anything, but why is it necessary to overwrite the vbmeta partition?
Click to expand...
Click to collapse
The original vbmeta partition contains a mechanism that checks for the other partitions to not be modified. The image downloaded from Google disables that mechanism, so you can put whatever you want on any partition.
wirespot said:
6. Is the procedure to get Magisk working still patching the bootloader, regardless what GSI ROM I install?
Click to expand...
Click to collapse
Yes, it's for the best. A large amount of what Magisk does is based on it being "hidden" from the regular system. Not just for hiding from SafetyNet, since you may not care about that with a 3rd party GSI ROM, but because keeping system modifications separate and keeping the original ROM is a very, very good practice.
wirespot said:
7. Did anybody pass Safety Net with Magisk and a 3rd-party GIS ROM? Can it be passed anymore after unlocking bootloader?
Click to expand...
Click to collapse
You can pass SafetyNet on the stock ROM, with unlocked bootloader and boot image patched to load Magisk. See my how to guide. I don't know about 3rd party GIS ROMs.
wirespot said:
8. I see there's no TWRP recovery for this device. Does it matter? Are there alternatives? In theory, if I have Magisk->root I can do pretty much anything so it doesn't sound like a big deal.
Click to expand...
Click to collapse
I've looked into this some more. The biggest downsides seem to be inability to restore backups of the userdata, and inability to disable problematic Magisk modules. There are modules such as Magisk Bootloop Protector which will disable all modules if it detects a bootloop, but if the problem is not a bootloop and still prevents your access you're out of luck...
Please feel free to add more info.
Related
Hi guys, I'm going to buy a OnePlus 5T, coming from a Motorola Moto X Play.
I used to do basic and old modding, without a need to think about project Treble or encrypt/decrypt.
I know now it is project Treble enabled also in stable channel, so now I would like to take away some doubts.
I actively watched threads and updates but I'm really confused by a big amount of things to consider, like:
- Do I need a Treble compatible Magisk?
- Do I need a Treble compatible TWRP?
- What's "no-verity" useful for? Why could I need to decrypt my OP5T?
- Do I have to follow a specific procedure to flash official updates if I have a custom recovery and Magisk installed?
So... A good list of ToDo, things I need to know before bricking the new beautiful entry is the request :angel:
If you can help me also with links, I'll appreciate.
nplezka said:
- Do I need a Treble compatible Magisk?
- Do I need a Treble compatible TWRP?
- What's "no-verity" useful for? Why could I need to decrypt my OP5T?
- Do I have to follow a specific procedure to flash official updates if I have a custom recovery and Magisk installed?
Click to expand...
Click to collapse
This guide is great to give you a start.
- No, you don't need Treble compatible Magisk. Magisk 16.0 works fine.
- Yes, you need the latest blu_spark or codeworkx TWRP. You can get to them from the guide above. Don't use the official TWRP btw.
- (I'm not very knowledgeable about this) I believe no-verity is to keep the device decrypted. I'm running it encrypted at the moment and see no reason to decrypt the phone.
- Kinda specific but nothing special. Here's my procedure (I'm running stable OOS ROM):
Download Full ZIP file (~1.6 GiB), not the OTA one. If your phone is rooted, system update will download the full file (instead of the ota); or you can use Oxygen Updater from the app store.
Change lockscreen lock from passcode to none (because my TWRP can't run properly with passcode. I have heard that many people don't need to do this)
Reboot to TWRP recovery
Flash Full Zip and Magisk in that order
(Some people say clear cache/dalvik before and after flashing, idk)
Reboot to system and change lock screen back to normal.
I think there's no big to do stuff with oneplus if you only do basic modding but I run my device fairly basic anyway so others can chime in with more advanced stuffs.
squaresmile said:
[*]Change lockscreen lock from passcode to none (because my TWRP can't run properly with passcode. I have heard that many people don't need to do this)
Click to expand...
Click to collapse
Maybe it's a stupid question, but I never had a pin or password on my lockscreen, and for sure I will simply use the fingerprint (or face-unlock? ?) on my future OP5T, so this point is only for who use a password/pin/sequence, right?
nplezka said:
Maybe it's a stupid question, but I never had a pin or password on my lockscreen, and for sure I will simply use the fingerprint (or face-unlock? ) on my future OP5T, so this point is only for who use a password/pin/sequence, right?
Click to expand...
Click to collapse
Pretty sure you need password/pin to use fingerprint/face unlock. However, I have heard that others can go to TWRP fine with a password/pin so you probably will be fine. I must have messed up somewhere I'm too lazy to fix now.
squaresmile said:
Pretty sure you need password/pin to use fingerprint/face unlock. However, I have heard that others can go to TWRP fine with a password/pin so you probably will be fine. I must have messed up somewhere I'm too lazy to fix now.
Click to expand...
Click to collapse
Do you think I have to do something in particular when I'll update to the OOS update with Treble, starting from the in-built firmware (don't know the exact version, but I'm talking about Nougat)? Or I can update normally?
It'll be the first thing I'll do, before unlocking and rooting. :cyclops:
nplezka said:
Do you think I have to do something in particular when I'll update to the OOS update with Treble, starting from the in-built firmware (don't know the exact version, but I'm talking about Nougat)? Or I can update normally?
It'll be the first thing I'll do, before unlocking and rooting. :cyclops:
Click to expand...
Click to collapse
Probably not if you follow the updater in settings. I would expect the stock update process to be pretty stable.
Hello,
I have a device that I obtained through beta testing that has not been released yet. I am allowed to keep the device now that testing is over. I am not happy with the stock rom and some of the apps it forces you to keep. I cannot remove them through ABD either. There is no stock ROM image available yet. Therefore, I cannot port TWRp or root.
I stumbled on project treble. I ran treble check and it says my phone is supported as it came with android 11. It supports systemless updates and has A/B system partition. I really like stock android ASOP. Is there anyway I can flash a generic image? What's the odds of it working correctly? Since there is no image available yet and I cannot port TWRP I have to worrying about not being able to recover the device if things go wrong. I know you can flash without TWRP which is why I decided to ask about this. Would I have a better chance flashing roms for supported devices with similar hardware? How should I proceed?
Thanks,
Rocky
as long as you have a compatible custom recovery AND the stock rom in case something go wrong, you can flash any GSI according to your device's architecture
Roizoulou said:
as long as you have a compatible custom recovery AND the stock rom in case something go wrong, you can flash any GSI according to your device's architecture
Click to expand...
Click to collapse
Since it is a beta unit I have neither as it has not been officially released. I have never flashed one of these roms so I do not know how well they work after flashing. I know the device has a pretty popular SOC which is a snapdragon 750g so I would assume if a gai runs good on another device using the 750g then it should work.
bigroc2223 said:
Since it is a beta unit I have neither as it has not been officially released. I have never flashed one of these roms so I do not know how well they work after flashing. I know the device has a pretty popular SOC which is a snapdragon 750g so I would assume if a gai runs good on another device using the 750g then it should work.
Click to expand...
Click to collapse
best you can do is dump the whole rom, make a backup before going any further
Roizoulou said:
best you can do is dump the whole rom, make a backup before going any further
Click to expand...
Click to collapse
I don't think I can dump it without root right?
bigroc2223 said:
I don't think I can dump it without root right?
Click to expand...
Click to collapse
an unlocked bootloader first and just search for how to dump system on google. it usually just need a pc and ADB
bigroc2223 said:
I don't think I can dump it without root right?
Click to expand...
Click to collapse
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
Roizoulou said:
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried this before it requires root. I just double checked and the prereqs say root required too. This sucks because the device has decent specs. It's just the ROM and software on it are crappy. After doing some reading the biggest thing I'm worried about is flashing and not having mobile data since it is a 5g phone. I read about someone else flashing and not being able to get their mobile data to work.
bigroc2223 said:
I tried this before it requires root. I just double checked and the prereqs say root required too. This sucks because the device has decent specs. It's just the ROM and software on it are crappy. After doing some reading the biggest thing I'm worried about is flashing and not having mobile data since it is a 5g phone. I read about someone else flashing and not being able to get their mobile data to work.
Click to expand...
Click to collapse
what is the device?
Roizoulou said:
what is the device?
Click to expand...
Click to collapse
It's a beta device from TCL. It has not been released yet. I read that phh GSI should be compatible with all android phones with treble support. Therefore, I think I might just go for it. The only thing is if I end up with a bug I more than likely will probably have to figure it out on my own.
bigroc2223 said:
It's a beta device from TCL. It has not been released yet. I read that phh GSI should be compatible with all android phones with treble support. Therefore, I think I might just go for it. The only thing is if I end up with a bug I more than likely will probably have to figure it out on my own.
Click to expand...
Click to collapse
just try phh's first and if you encounter issues, try other custom roms
Roizoulou said:
just try phh's first and if you encounter issues, try other custom roms
Click to expand...
Click to collapse
I think I might of found a solution. I am pretty sure there is a way to boot a ROM before flashing it. I could of sworn I read this somewhere. It was an adb command. It allowed you too boot the ROM instead of flashing it. This would allow me to preview the ROM before officially flashing it to the device. I just cannot remember where I saw this at or the command.
My goal is to get a working gsi installed. From there I would like to get TWRP flashed on the device so it can be rooted. If I would need to port TWRP I think I could figure it out. This way when the device is officially released it will have TWRP ready to go for it. Also, since it will have TWRP I will be able to start porting roms as soon as they release the system image.
bigroc2223 said:
I think I might of found a solution. I am pretty sure there is a way to boot a ROM before flashing it. I could of sworn I read this somewhere. It was an adb command. It allowed you too boot the ROM instead of flashing it. This would allow me to preview the ROM before officially flashing it to the device. I just cannot remember where I saw this at or the command.
My goal is to get a working gsi installed. From there I would like to get TWRP flashed on the device so it can be rooted. If I would need to port TWRP I think I could figure it out. This way when the device is officially released it will have TWRP ready to go for it. Also, since it will have TWRP I will be able to start porting roms as soon as they release the system image.
Click to expand...
Click to collapse
like DSU loader?
Roizoulou said:
like DSU loader?
Click to expand...
Click to collapse
Never heard of that this was just an adb command.
I just downloaded ASOP 11.0 v309. Treble info says my device requires system-arm64-ab.img.xz. So I downloaded system-roar-arm64-ab-gapps.img.xz and system-roar-arm64-ab-vanilla.ikg.gz so hopefully those are the right ones. One has Gapps and one does not. Was going to flash the Gapps version first and see how things go. Then if need be flash vanilla.
I got a problem with phone calls. When I dial out I get call ended. Incoming calls I can hear them ring but get no way to answer. Also I am not getting text messages.
Roizoulou said:
like DSU loader?
Click to expand...
Click to collapse
I got it all working bro thanks for your help
bigroc2223 said:
I got it all working bro thanks for your help
Click to expand...
Click to collapse
gapps or vanilla?
Roizoulou said:
gapps or vanilla?
Click to expand...
Click to collapse
I was able to get them both to work. However, I am trying to use the gapps version, but I am getting an error that the device is not google certified. I cannot find a workaround unless I unroot which I do not want to do =(
bigroc2223 said:
I was able to get them both to work. However, I am trying to use the gapps version, but I am getting an error that the device is not google certified. I cannot find a workaround unless I unroot which I do not want to do =(
Click to expand...
Click to collapse
rooted with magisk?
Roizoulou said:
rooted with magisk
Click to expand...
Click to collapse
It comes rooted with phh superuser. I'm trying to find a way to pull my boot.img from the device so I can use it to flash magisk since it has a workaround for non Google certified devices.
The last time I rooted a phone was 3 years ago, in general whenever I try to root a phone I feel like the entire process has changed and im completely out of the loop.
All i want to do is make it so i can install f.lux and youtube vanced, how do I do this?
I know that I need to install magisk but apparently I also need to enable the bootloader whatever that means?
Sideload, flashing, caprip, boot-image, fastboot, TWRP: these words mean nothing to me, they serve to confuse and demean me.
Is there any resource for figuring out how to go from a new out-of-the-box moto g30 to one which lets me install youtube vanced? Usually I'd look up a tutorial but the only one I found was in spanish and I don't speak spanish.
Thanks for any help you can give.
First things first.
Android has Night Light built in and Youtube Vanced doesn't need root.
But, if you're still serious about rooting and installing magisk to make use of all of the really useful modules, you'll need:
An Unlocked Bootloader: Motorola's Own Guide
Keep in mind that unlocking the bootloader will wipe your phone and void its warranty, so be absolutely sure you want to do it and back up your files.
Then you'll need to manually patch a boot.img from your stock ROM (can be found here.) and flash it using ADB (Android Debug Bridge) using your PC.
I rooted mine within 3 days of owning it and have been enjoying it with no problems whatsoever ever since.
I used this guide as reference. If you have any questions you can always just message me here or on Telegram (@Kuntitled).
samjoebobtomted said:
The last time I rooted a phone was 3 years ago, in general whenever I try to root a phone I feel like the entire process has changed and im completely out of the loop.
All i want to do is make it so i can install f.lux and youtube vanced, how do I do this?
I know that I need to install magisk but apparently I also need to enable the bootloader whatever that means?
Click to expand...
Click to collapse
Bootloader is small program which runs before Android operating system running. Bootloader is first program to run so It is specific for board and processor. -RootJunky
Click to expand...
Click to collapse
Unlocking the bootloader
You can flash a custom system only if the bootloader allows it. Note, though, that the bootloader is locked by default. You can unlock the bootloader, but doing so deletes user data for privacy reasons. After unlocking, all data on the device is erased, that is, both private app data and shared data accessible over USB (including photos and movies). Before attempting to unlock the bootloader, back up any important files on the device. - https://source.android.com/setup/build/running
Click to expand...
Click to collapse
samjoebobtomted said:
Sideload,
Click to expand...
Click to collapse
Generally sideload means installing an app without the playstore.
samjoebobtomted said:
flashing,
Click to expand...
Click to collapse
Flashing usually refers to installing through fastboot mode or recovery
samjoebobtomted said:
caprip,
Click to expand...
Click to collapse
codename or development name for Moto G30
samjoebobtomted said:
boot-image
Click to expand...
Click to collapse
The boot.img is the fie that creates the boot partition
/bootThis is the boot partition of your Android device, as the name suggests. It includes the android kernel and the ramdisk. The device will not boot without this partition. Wiping this partition from recovery should only be done if absolutely required and once done, the device must NOT be rebooted before installing a new one, which can be done by installing a ROM that includes a /boot partition.
-RootJunky
Click to expand...
Click to collapse
samjoebobtomted said:
fastboot,
Click to expand...
Click to collapse
Fastboot refers to several things
Fastboot is the fastboot protocol to communicate with an Android device.
Fastboot.exe is the part of SDK Platform-Tools used to communicate with an Android device when it's in fastboot mode.
samjoebobtomted said:
TWRP:
Click to expand...
Click to collapse
Twrp is a Custom recovery,
The stock recovery has very limited functions,
a custom recovery has more options
/recoveryThis is specially designed for backup. The recovery partition can be considered as an alternative boot partition, that lets the device boot into a recovery console for performing advanced recovery and maintenance operations on it. -RootJunky
Click to expand...
Click to collapse
samjoebobtomted said:
these words mean nothing to me, they serve to confuse and demean me.
Is there any resource for figuring out how to go from a new out-of-the-box moto g30 to one which lets me install youtube vanced? Usually I'd look up a tutorial but the only one I found was in spanish and I don't speak spanish.
Thanks for any help you can give.
Click to expand...
Click to collapse
I have general Moto rooting instructions here
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Kuntitled said:
First things first.
Android has Night Light built in and Youtube Vanced doesn't need root.
Click to expand...
Click to collapse
Wait really I didn't even realize I didn't need a root for that lol.
Kuntitled said:
But, if you're still serious about rooting and installing magisk to make use of all of the really useful modules, you'll need:
An Unlocked Bootloader: Motorola's Own Guide
Keep in mind that unlocking the bootloader will wipe your phone and void its warranty, so be absolutely sure you want to do it and back up your files.
Then you'll need to manually patch a boot.img from your stock ROM (can be found here.) and flash it using ADB (Android Debug Bridge) using your PC.
I rooted mine within 3 days of owning it and have been enjoying it with no problems whatsoever ever since.
I used this guide as reference. If you have any questions you can always just message me here or on Telegram (@Kuntitled).
Click to expand...
Click to collapse
Hi thanks this really helped me get the grip of things haha.
I managed to unlock the bootloader but I'm a bit confused on what stock ROM you were referring to, the link you sent had a bunch of possibilities, I assume I need a reteu one since that's the name of my phone's software channel but there's a wide variety of them and the guide you sent seems to have their own ROM as well.
Either way thanks for all the help!
samjoebobtomted said:
Wait really I didn't even realize I didn't need a root for that lol.
Hi thanks this really helped me get the grip of things haha.
I managed to unlock the bootloader but I'm a bit confused on what stock ROM you were referring to, the link you sent had a bunch of possibilities, I assume I need a reteu one since that's the name of my phone's software channel but there's a wide variety of them and the guide you sent seems to have their own ROM as well.
Either way thanks for all the help!
Click to expand...
Click to collapse
You should check the Build Number under "About Phone" in settings, and match it what you find on that link i sent.
I would really like to try xiaomi.eu on mi 10T, but it needs open boot loader, which can be detected, and then all app's don't work.
Yes I know you can use magisk and have an eternal battle with safety net while some apps still refuse to work (Mcdonalds is a good example).
rajatapaus00 said:
I would really like to try xiaomi.eu on mi 10T, but it needs open boot loader, which can be detected, and then all app's don't work.
Yes I know you can use magisk and have an eternal battle with safety net while some apps still refuse to work (Mcdonalds is a good example).
Click to expand...
Click to collapse
I have an mtk phone which i upgraded to android 10(q) when I flashed pixel 10 gsi my bootloader was set to locked, so you just need to find the line for it in a build.prop (search the internet) and add it in a module or something
that way system thinks bootloader is locked even if its not
flairepathos.info said:
I have an mtk phone which i upgraded to android 10(q) when I flashed pixel 10 gsi my bootloader was set to locked, so you just need to find the line for it in a build.prop (search the internet) and add it in a module or something
that way system thinks bootloader is locked even if its not
Click to expand...
Click to collapse
I heard that modifying that requires rooting.
rajatapaus00 said:
I heard that modifying that requires rooting.
Click to expand...
Click to collapse
Yes or
you can just flash twrp
copy the needed file to pc edit what you want
overwrite the old one in phone
flash stock recovery and voila
I have an interesting idea, but I don't have enough technical skills to implement it.
I noticed that edload mode can brush all partitions without BL unlocked. So i`m think, if i can modify init_boot.img and package it into the flashing package, can I bypass the BL lock and forcibly flash root into the device?
If that available, I can own rooted devices without data loss, fingerprint also does not appear abnormal.
No. Root require a patched boot.img, so you have to get access to other partition.
To do this the unlocked bootloader is needed.
CrazyMoney said:
modify init_boot.img and package it into the flashing package
Click to expand...
Click to collapse
AFAIK this won't work because this image needs to be signed. If we can patch init_boot.img, sign it, flash it and also flash signature of this file, we might be able to relock bootloader. Try with caution: unless there's good instruction for EDL unbricking, you might end up with a bricked device without any free way to fix it.
zSyntex said:
No. Root require a patched boot.img, so you have to get access to other partition.
To do this the unlocked bootloader is needed.
Click to expand...
Click to collapse
I remember Andriod 13 need patch init_boot.img instead of boot.img. And edload mode doesen`t need anything because that used a underlying layer.
aaa.bbb111222 said:
AFAIK this won't work because this image needs to be signed. If we can patch init_boot.img, sign it, flash it and also flash signature of this file, we might be able to relock bootloader. Try with caution: unless there's good instruction for EDL unbricking, you might end up with a bricked device without any free way to fix it.
Click to expand...
Click to collapse
I think you are right. But in the past, I can make fake signature in the past, just don`t know how to deal now.
CrazyMoney said:
I think you are right. But in the past, I can make fake signature in the past, just don`t know how to deal now.
Click to expand...
Click to collapse
From the past a lot of things had changed.
Now you need to unlock the BL to get root in the correct and safe way.
zSyntex said:
From the past a lot of things had changed.
Now you need to unlock the BL to get root in the correct and safe way.
Click to expand...
Click to collapse
Maybe, but everything only by trying can step foreward. Isn`t it?
I'm just sharing my ideas, not necessarily implementing them, just discussing a possibility.