Need a good ToDo list for a new OnePlus 5T with project Treble - OnePlus 5T Questions & Answers

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.

Related

How to Root my new Moto Z2 Play?

OK, I just bought a new Moto Z2 Play, and I of course, want to Root it. I have done Root on all my previous smart phones so I have some experience. I read thru all the threads here, but still have some remaining questions.
Where can I get the latest Moto drivers for Win 10 64-bit? I rather have just the drivers, if possible, than some other bloat Moto utilities too.
Where can I get the latest ADB ? I know, there are lots of sources if I search, but I am looking for a safe copy.
What do I use for TWRP? TWRP 3.2.1-0 ? [TWRP][64 bit][3.2.1_r12] ? Alternate TWRP v3.1.1.0 ? I am even asking, because I read a post and its reply, that mentioned that the 64-bit had to be used, but I haven't seen that mentioned anywhere else.
As part of TWRP, should I do the "Swipe to allow modifications for /system" ? I have read posts suggesting either way, and remain unsure which is best.
I plan to install the latest Magisk Manager, v5.5.5. Or should I install simply Magisk v15.3?
Should I plan to Hide the Magisk Manager?
Do I need to, also, install SuperSU and BusyBox from the Google Play Store?
Is there anything additional I need to do, to successfully handle Safety Net ?
Thanks!
Did you read?
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615
I used Juniors version of TWRP.
https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Yes to Magisk Manager.
Yes to Magisk.
No to SuperSU.
No to Busy Box.
First, let me start with a heartfelt thanks! :highfive:
pizza_pablo said:
Did you read?
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615
Click to expand...
Click to collapse
Yes, but it has instructions like this:
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 SuperSU or flash any of the verity disabler zips there in xda.
Click to expand...
Click to collapse
Which is why it left feeling unsure, do I swipe or not? Is having the system partition modified "good" and a normal part of this type of root'ing?
Plus, the mention of flashing SuperSU, lead to my question about going that (which you replied 'no').
Maybe I am simply having a case of information overload. With possibly, a strong addition of having too many different opinions which might not all be valid.
WaltA said:
First, let me start with a heartfelt thanks! :highfive:
Yes, but it has instructions like this:
Which is why it left feeling unsure, do I swipe or not? Is having the system partition modified "good" and a normal part of this type of root'ing?
Plus, the mention of flashing SuperSU, lead to my question about going that (which you replied 'no').
Maybe I am simply having a case of information overload. With possibly, a strong addition of having too many different opinions which might not all be valid.
Click to expand...
Click to collapse
I'm glad you have read! :good:
I understand you're dilemma and have also experience info overload, when researching rooting / flashing procedures. It never hurts to read it, yet again and watch any YouTube videos available on the subject.
I always swipe to allow modifications when installing TWRP. Otherwise, TWRP will be in READ ONLY mode.
I am not certain about Busy Box, but haven't needed it. Magisk has A Super User function, so SuperSU is not needed.
I am no expert, just trying to help, so please don't take anything I've said as the gospel. Read everything and then read it again.
pizza_pablo said:
Did you read?
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615
I used Juniors version of TWRP.
https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Yes to Magisk Manager.
Yes to Magisk.
No to SuperSU.
No to Busy Box.
Click to expand...
Click to collapse
Any hint up to which 8.0 security patch update will @Junior Passos method will work
Sent from my Moto Z2 Play using XDA Labs
The Analog Kid said:
Any hint up to which 8.0 security patch update will @Junior Passos method will work
Click to expand...
Click to collapse
No. I'm still on Nougat. I have no interest in Oreo, for this device.
The Analog Kid said:
Any hint up to which 8.0 security patch update will @Junior Passos method will work
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
I'm on August security patch.

Call Recording and Indonesia ROM

Just got a Redmi Note 8 Pro with Global ROM and discovered that call recording won't work due to Google/Android Pie limitations.
After some searching, I found (on this forum) that the Indonesia ROM supports call recording on this phone.
Here are my questions:
1. Will burning a different ROM affect my warranty?
2. Will I lose any functionality by switching from Global to Indonesia ROM, and if so, what? Specifically, will NFC functionality be affected?
3. If I ever do a factory reset, will the phone revert to Global ROM?
4. I found the Indonesia ROM files here. There are three files called Recovery, OTA, and Fastboot. Do I need them all? If so, do they need to be burned in any specific order?
5. Where can I find complete instructions for burning the Indonesia ROM? I am new to Xiaomi, and the last time I burned a ROM to a phone was 5 years ago (Samsung); I don't remember anything, so I'd like instructions that assume nothing and don't skip any steps (instructions for intelligent dummies). I found these instructions for installing TWRP, but there's nothing about what to do next, and there's a list of pre-requisites with no explanations (Unlocked Bootloader, Phone Drivers, ADB and Fastboot Drivers), making the instructions insufficient for a noob like me.
Thanks much.
yossidme said:
Just got a Redmi Note 8 Pro with Global ROM and discovered that call recording won't work due to Google/Android Pie limitations.
After some searching, I found (on this forum) that the Indonesia ROM supports call recording on this phone.
Here are my questions:
1. Will burning a different ROM affect my warranty?
2. Will I lose any functionality by switching from Global to Indonesia ROM, and if so, what? Specifically, will NFC functionality be affected?
3. If I ever do a factory reset, will the phone revert to Global ROM?
4. I found the Indonesia ROM files here. There are three files called Recovery, OTA, and Fastboot. Do I need them all? If so, do they need to be burned in any specific order?
5. Where can I find complete instructions for burning the Indonesia ROM? I am new to Xiaomi, and the last time I burned a ROM to a phone was 5 years ago (Samsung); I don't remember anything, so I'd like instructions that assume nothing and don't skip any steps (instructions for intelligent dummies). I found these instructions for installing TWRP, but there's nothing about what to do next, and there's a list of pre-requisites with no explanations (Unlocked Bootloader, Phone Drivers, ADB and Fastboot Drivers), making the instructions insufficient for a noob like me.
Thanks much.
Click to expand...
Click to collapse
Hey,
Before going any further you first need to make sure what region is your phone. Is it a Chinese phone (bought from AliExpress for example) or a real Global phone (bought from a local store/official retail). Because you could very well own a Chinese phone shipped with a Global Rom flashed on it and this could result in some problems for you in terms of what you can do with it and how you can do it.
If you bought/received a phone with already unlocked bootloader, you should return it.
Unlocking bootloader should only be done by you when you need it.
1. Technically unlocking bootloader, ESSENTIAL step prior flashing anything, void your warranty.
However and that's what is interesting, if at some point you decide to flash back your original region rom (here Global) and lock back bootloader, none will know but Xiaomi servers you once unlocked this device certainly not a local reseller. So in term of warranty you should be safe, that is of course unless you brick your phone doing stuff you were not supposed to do with a locked bootloader if you are following.
2. If not mistaking, I think you loose NFC. Indian phones for sure do not have NFC at all, for their version, the chip was replaced with a 2nd SIM card tray (not shared). Not sure if you read the functionality afterward using rooted tricks.
3. No that does not work this way. When you are running a Rom, any version, if you factory reset that room, you just return to installation screen of that given Rom.
To return to Global Rom, you will need to reflash that Global Rom using the same method you did successfully flashing the Indonesian Rom (or any other rom) for example.
Would be wise to first download the exact version of the Rom you are currently using on your phone for archives purpose (BURN IT on good quality medias!) to revert back to it when/if needed. You can also archives OTA updates of that version you may not have taken yet to apply them manually if you ever revert back to that Global Rom and want to.
4. Different versions depends on what you are doing. In your case Fastboot version is what you need at the moment. You can find all different kind of versions of Roms for your RN8PRO on that site
As for the way to flash them, order and everything, you will need to look for guides online,
I dont think any order matters, just make sure to flash them all before rebooting disconnecting device. But if you are unsure of what you are doing, you'd be probably best using a tool such as MiFlash.
5. Here you can find one from the MIUI community website guiding you through the use of MiFlash to flash a stock Rom on your device.
Just note you do not have to use any tools to flash the .images of all partitions, you can easily doing it from command line using fastboot flash command one after an other.
Also note that installing TWRP is usually not needed to flash stock Roms (unlike flashing custom roms). Trying to mess up with the recovery partition is actually what seem to brick most of the devices.
However please note UNLOCKING your BOOTLOADER is MENDATORY.
Hope this helps.
Regards,
doesnt matter if you switch to any rom variant .i have switched mine to indonesian ,europe and indian and alll worked fine execpt indian version felt a bit laggy .just download the fastboot version of the rom and flash it through mi flash tool xiaomiflash .your bootloader needs to be unlocked and dont forget to check cleann all button in mi flash and dont check clean and lock
I have got global version and changed imei with unlocked bootloader. Can i flash indonesian rom without lose f my imei?
Thanks in advance for your answers
Muad.Dib,
Thanks for your detailed reply.
If I understand correctly, unlocking the bootloader voids the warranty just the same as rooting the phone, so if all I want is to get call recording, I may as well just root the phone and save the bother of flashing a different ROM.
Does that make sense to you, or do you see any advantage to flashing a different stock ROM instead of just rooting the phone? From past experience I've seen that rooting has additional benefits anyway.
BTW, I bought my phone on Banggood. It was advertised as Global ROM, and that appears to be what it has. As soon as I turned the phone on it updated to MIUI Global 11.0.2.1; I don't know what version it was before the update.
Muad.Dib said:
Hey,
Before going any further you first need to make sure what region is your phone. Is it a Chinese phone (bought from AliExpress for example) or a real Global phone (bought from a local store/official retail). Because you could very well own a Chinese phone shipped with a Global Rom flashed on it and this could result in some problems for you in terms of what you can do with it and how you can do it.
If you bought/received a phone with already unlocked bootloader, you should return it.
Unlocking bootloader should only be done by you when you need it.
1. Technically unlocking bootloader, ESSENTIAL step prior flashing anything, void your warranty.
However and that's what is interesting, if at some point you decide to flash back your original region rom (here Global) and lock back bootloader, none will know but Xiaomi servers you once unlocked this device certainly not a local reseller. So in term of warranty you should be safe, that is of course unless you brick your phone doing stuff you were not supposed to do with a locked bootloader if you are following.
2. If not mistaking, I think you loose NFC. Indian phones for sure do not have NFC at all, for their version, the chip was replaced with a 2nd SIM card tray (not shared). Not sure if you read the functionality afterward using rooted tricks.
3. No that does not work this way. When you are running a Rom, any version, if you factory reset that room, you just return to installation screen of that given Rom.
To return to Global Rom, you will need to reflash that Global Rom using the same method you did successfully flashing the Indonesian Rom (or any other rom) for example.
Would be wise to first download the exact version of the Rom you are currently using on your phone for archives purpose (BURN IT on good quality medias!) to revert back to it when/if needed. You can also archives OTA updates of that version you may not have taken yet to apply them manually if you ever revert back to that Global Rom and want to.
4. Different versions depends on what you are doing. In your case Fastboot version is what you need at the moment. You can find all different kind of versions of Roms for your RN8PRO on that site
As for the way to flash them, order and everything, you will need to look for guides online,
I dont think any order matters, just make sure to flash them all before rebooting disconnecting device. But if you are unsure of what you are doing, you'd be probably best using a tool such as MiFlash.
5. Here you can find one from the MIUI community website guiding you through the use of MiFlash to flash a stock Rom on your device.
Just note you do not have to use any tools to flash the .images of all partitions, you can easily doing it from command line using fastboot flash command one after an other.
Also note that installing TWRP is usually not needed to flash stock Roms (unlike flashing custom roms). Trying to mess up with the recovery partition is actually what seem to brick most of the devices.
However please note UNLOCKING your BOOTLOADER is MENDATORY.
Hope this helps.
Regards,
Click to expand...
Click to collapse
Did you check if NFC works with Indonesian ROM?
maanni said:
doesnt matter if you switch to any rom variant .i have switched mine to indonesian ,europe and indian and alll worked fine execpt indian version felt a bit laggy .just download the fastboot version of the rom and flash it through mi flash tool xiaomiflash .your bootloader needs to be unlocked and dont forget to check cleann all button in mi flash and dont check clean and lock
Click to expand...
Click to collapse
yossidme said:
Muad.Dib,
Thanks for your detailed reply.
If I understand correctly, unlocking the bootloader voids the warranty just the same as rooting the phone, so if all I want is to get call recording, I may as well just root the phone and save the bother of flashing a different ROM.
Does that make sense to you, or do you see any advantage to flashing a different stock ROM instead of just rooting the phone? From past experience I've seen that rooting has additional benefits anyway.
BTW, I bought my phone on Banggood. It was advertised as Global ROM, and that appears to be what it has. As soon as I turned the phone on it updated to MIUI Global 11.0.2.1; I don't know what version it was before the update.
Click to expand...
Click to collapse
You're welcome, I am happy if I was useful to you in any kind of ways.
Well yes and no. Yes apparently you 'could' achieve call recording when rooted (yet I still fail doing so even if I installed the default MUI apps module I got from Telegram group. The setting to automatic recording is set to on yes, but I dont see recordings in the supposed destination folder nor I can see a simple button to record any voicecall I used to have on older versions of Android. Me failing to make it work - I did not try very hard to be honest - does not mean you cannot find someone who succeeded into doing so in that telegram group for RN8PRO).
That said it would not be a 'native' solution, just a patch/workaround. If it works well great, if not, well...
On an other hand by flashing to a Rom which does support it natively, well you are covered for the use you need.
So the advantage I see (with the included disadvantages) is better support for the function which is not supported for privacy reasons en Glob/EU market.
Does that come at a price?
Probably.
For example are you ready to trade off NFC for native call recording support? That may be a choice you have to make in the end. Again that said, if you root your phone on that new Rom, install NFC drivers manually as root (I see no reasons why that would not be possible after all) you may be able to patch NFC on that other Rom since unlike Indonesians market phone, you do have NFC hardware.
For example, myself, I wish I could have made that kind of bargain/trade off, giving up that NFC feature I have no need for, to get 8GB or Ram + 2x Sims + SD and not an hybrid tray. Unfortunately that's not the kind of trade I could make here in EU unless I would have ordered directly from Amazon.in (assuming that would have been possible) or third party website, but that was not possible for warranty reasons among other things.
Hope this helps.
Regards,
yossidme said:
Did you check if NFC works with Indonesian ROM?
Click to expand...
Click to collapse
Yes it does as it is officially available in every variant expect indian variant.
UPDATE:
I finally had the time to test the MIUI-default-apps Magisk module available for download on Telegram group, originally made for MIUI 11.0.1.0, and it works properly on MIUI 11.0.2.0 EEA. Does not require changing Rom.
Hope this helps.
Well, I have finally started the process, but got stymied by the Bootloader Unlock tool (Couldn't unlock. Please unlock 168 hours later.). Quite frustrating. I see that a lot of people have this problem and had to try again more than once, waiting a week between attempts.
Is there a workaround or do I just have to wait a week and hope for the best?
Also, assuming all goes well and I eventually manage to unlock the bootloader and flash the Indonesia ROM, do I use the same tool to re-lock the bootloader (in order to restore the security of the phone)?
And if I want to unlock again in the future, will I again possibly get the "wait and try again next week" message, or does that only happen the first time?
Thanks.
Muad.Dib said:
UPDATE:
I finally had the time to test the MIUI-default-apps Magisk module available for download on Telegram group, originally made for MIUI 11.0.1.0, and it works properly on MIUI 11.0.2.0 EEA. Does not require changing Rom.
Hope this helps.
Click to expand...
Click to collapse
yossidme said:
Well, I have finally started the process, but got stymied by the Bootloader Unlock tool (Couldn't unlock. Please unlock 168 hours later.). Quite frustrating. I see that a lot of people have this problem and had to try again more than once, waiting a week between attempts.
Is there a workaround or do I just have to wait a week and hope for the best?
Click to expand...
Click to collapse
No workaround, you just have to wait (and yes I know how freaking frustrating it was for me...). You can even start meditation classes meanwhile it helps
yossidme said:
Also, assuming all goes well and I eventually manage to unlock the bootloader and flash the Indonesia ROM, do I use the same tool to re-lock the bootloader (in order to restore the security of the phone)?
Click to expand...
Click to collapse
It depends on what your the flavor of the phone you got. You may want to have a look at that other thread Relock bootloader after flashing ROM Indonesia where we actually covered this exact subject
The good thing about that 7 days wait period is you can gather all the intel you need to be 100% ready when the time come to seriously mess up with things.
So you know, once your bootloader is unlocked, first thing you will want to do BEFORE anything else, is blow off that security which needed Auth Account to unbrick account (ONLY WORKS FOR PIE, ANDROID 9 MIUI VERSION BEWARE).
All information is here: [GUIDE][INFO][PSA] Redmi Note 8 Pro - Megathread
yossidme said:
And if I want to unlock again in the future, will I again possibly get the "wait and try again next week" message, or does that only happen the first time?
Thanks.
Click to expand...
Click to collapse
The waiting time is for one time only (THANKS GOD!).
So if you relock, beside having to get your hands on the unlock tool once again and have added the same infos as for the first time in the phone, you will be able to unlock right away.
That's at least a good news
Hope this helps,
Regards,
Muad.Dib said:
UPDATE:
I finally had the time to test the MIUI-default-apps Magisk module available for download on Telegram group, originally made for MIUI 11.0.1.0, and it works properly on MIUI 11.0.2.0 EEA. Does not require changing Rom.
Hope this helps.
Click to expand...
Click to collapse
My friend,
Would you like be so kind and share that magisk module with others or maybe just indicate the spot where I can get it? I would love to try this out. THX
kamyk70 said:
My friend,
Would you like be so kind and share that magisk module with others or maybe just indicate the spot where I can get it? I would love to try this out. THX
Click to expand...
Click to collapse
Yes of course.
It is a module you can find on the Telegram group called "Redmi Note 8 Pro | OFFICIAL".
Like me you will have to go in there even if you do not use Telegram.
Once there and you got the /notes it is called the default apps.
I cannot share it myself here because I am not the developer of that module, as you can understand that's against forums policies.
All I can tell you is it works correctly on EEA MIUI 11.0.2.0.
Good luck!
Hope this helps.
Muad.Dib said:
Yes of course.
It is a module you can find on the Telegram group called "Redmi Note 8 Pro | OFFICIAL".
Like me you will have to go in there even if you do not use Telegram.
Once there and you got the /notes it is called the default apps.
I cannot share it myself here because I am not the developer of that module, as you can understand that's against forums policies.
All I can tell you is it works correctly on EEA MIUI 11.0.2.0.
Good luck!
Hope this helps.
Click to expand...
Click to collapse
Thanks man, I got it! ?
I have disovered that there are different NGC protocols and that my Redmi Note 8 Pro does not read NFC cards of some protocols. I'm wondering if it might not be a driver issue. where would I look for NFC drivers?
Thanks
Muad.Dib said:
For example are you ready to trade off NFC for native call recording support? That may be a choice you have to make in the end. Again that said, if you root your phone on that new Rom, install NFC drivers manually as root (I see no reasons why that would not be possible after all) you may be able to patch NFC on that other Rom since unlike Indonesians market phone, you do have NFC hardware.
Regards,
Click to expand...
Click to collapse
kamyk70 said:
Thanks man, I got it!
Click to expand...
Click to collapse
You are much welcome, glad I could help
Regards
---------- Post added at 10:21 ---------- Previous post was at 10:20 ----------
yossidme said:
I have disovered that there are different NGC protocols and that my Redmi Note 8 Pro does not read NFC cards of some protocols. I'm wondering if it might not be a driver issue. where would I look for NFC drivers?
Thanks
Click to expand...
Click to collapse
Sadly I have no idea. I think you should make a new thread about this to get more visibility and probably more answers from people who actually knows the answer.
Hope this help.
Regards.
Muad.Dib said:
UPDATE:
I finally had the time to test the MIUI-default-apps Magisk module available for download on Telegram group, originally made for MIUI 11.0.1.0, and it works properly on MIUI 11.0.2.0 EEA. Does not require changing Rom.
Hope this helps.
Click to expand...
Click to collapse
Hi can you share more details???IS IT SAFE?? I want miui message and call apps not Google's one... How can i have them without changing ROM to Indonesian??? Now i have global ROM.
yossidme said:
Did you check if NFC works with Indonesian ROM?
Click to expand...
Click to collapse
yup it is working perfectly fine on indonesian rom as i am still using it
Alisoofi said:
Hi can you share more details???IS IT SAFE?? I want miui message and call apps not Google's one... How can i have them without changing ROM to Indonesian??? Now i have global ROM.
Click to expand...
Click to collapse
Hey,
Sorry was AFK for a while. In case you still need answer, going to reply just in case.
Well there is not much to add, you simply install the module from within Magisk once it installed, you reboot, and it works out of the box, you go in the settings and you set it as you like.
Good luck!
Do i need to root before installing it ?
Do i need to root before installing it ?

Can I flash project treble?

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.

Question Help me understand GIS for Xperia 10 III

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.

Question How to Root? And other pre-purchase questions

Thinking about getting this phone after having some difficulties with a Note10+, considering running either rooted stock or LineageOS.
However I noticed there doesn't seem to be a "how to root" thread anywhere here.
Is it just a matter of installing Magisk and letting it do it's thing? I found LineageOS's instructions on unlocking the bootloader, but nothing beyond that: https://wiki.lineageos.org/devices/lisa/install
Does anyone here run rooted stock? Or would most people recommend running a custom ROM instead?
Are there any problems or difficulties I need to be aware of before I buy?
I see there's no 'lisa' TWRP build. what's the "best" recovery to use for this phone?
mon0theist said:
Thinking about getting this phone after having some difficulties with a Note10+, considering running either rooted stock or LineageOS.
However I noticed there doesn't seem to be a "how to root" thread anywhere here.
Is it just a matter of installing Magisk and letting it do it's thing? I found LineageOS's instructions on unlocking the bootloader, but nothing beyond that: https://wiki.lineageos.org/devices/lisa/install
Does anyone here run rooted stock? Or would most people recommend running a custom ROM instead?
I see there's no 'lisa' TWRP build. what's the "best" recovery to use for this phone?
Click to expand...
Click to collapse
Follow standard/offícial instructions (available on the Magisk GitHub page!!!) and that's it.
No need to have the same thread for every phone
However, for additional things like hiding the root, etc, there are generic threads on XDA, again not specific for this or that phone
There are threads about recoveries, particularly for Orange Fox for Lisa
But again, Magisk (by official instructions) does not require TWRP/OrangeFox for the installation, instead use the officially recommended patch & flash method
zgfg said:
Follow standard/offícial instructions (available on the Magisk GitHub page!!!) and that's it.
No need to have the same thread for every phone
However, for additional things like hiding the root, etc, there are generic threads on XDA, again not specific for this or that phone
There are threads about recoveries, particularly for Orange Fox for Lisa
But again, Magisk (by official instructions) does not require TWRP/OrangeFox for the installation, instead use the recommended patch & flash method
Click to expand...
Click to collapse
Okay great thanks. Haven't rooted a new phone in a couple years so I've been out of the loop
mon0theist said:
Okay great thanks. Haven't rooted a new phone in a couple years so I've been out of the loop
Click to expand...
Click to collapse
I have the same situation like you, and I changed iPhone to Android phone again after 5 years.
I want to root it but it seems there's not too much topic about how to root or flash TWRP .
Let me read more for it.
wajie said:
I have the same situation like you, and I changed iPhone to Android phone again after 5 years.
I want to root it but it seems there's not too much topic about how to root or flash TWRP .
Let me read more for it.
Click to expand...
Click to collapse
Post #2 above - TWRP not needed for installing Magisk (root)
zgfg said:
Post #2 above - TWRP not needed for installing Magisk (root)
Click to expand...
Click to collapse
Yes, I installed Magisk last night, no needed TWRP.
wajie said:
Yes, I installed Magisk last night, no needed TWRP.
Click to expand...
Click to collapse
How are you able to root stock MIUI?
I would suggest to just get a xiaomi 11T or poco f3 if you can. Lisa screen terrible, most if it.
JominatorX said:
How are you able to root stock MIUI?
Click to expand...
Click to collapse
link here: https://magiskcn.com/
choose "小米安装面具"
edzel13 said:
I would suggest to just get a xiaomi 11T or poco f3 if you can. Lisa screen terrible, most if it.
Click to expand...
Click to collapse
Thank you . but I have already bought Lisa. My next phone must be pro/ultra

Categories

Resources