Related
So I'd like to know how I can use Chainfire's new systemless root to then still use Android Pay. I downloaded the Android binaries from Google for the 5X and proceeded like so:
(I was already rooted with the normal method that modifies the /system parition)
1. Run flash-all.bat to flash all partitions and go back to stock.
2. Install the modified boot.img from Chainfire
3. Install the latest TWRP 2.8.7.2
4. Reboot into TWRP
5. Install using adb sideload from TWRP the beta SuperSU
6. Reboot into phone and set it up... restore Titanium Backups...
The problem is that Android Pay still won't let me add a card to it....
Did I do something wrong in this process here?
Would love it if someone who has done this could help me out here..
Thanks!
chickentech said:
So I'd like to know how I can use Chainfire's new systemless root to then still use Android Pay. I downloaded the Android binaries from Google for the 5X and proceeded like so:
(I was already rooted with the normal method that modifies the /system parition)
1. Run flash-all.bat to flash all partitions and go back to stock.
2. Install the modified boot.img from Chainfire
3. Install the latest TWRP 2.8.7.2
4. Reboot into TWRP
5. Install using adb sideload from TWRP the beta SuperSU
6. Reboot into phone and set it up... restore Titanium Backups...
The problem is that Android Pay still won't let me add a card to it....
Did I do something wrong in this process here?
Would love it if someone who has done this could help me out here..
Thanks!
Click to expand...
Click to collapse
Did you hide/disable/uninstall supersu and reboot before opening the Android pay app?
If not, do that, and clear app data for Android pay. Then try to set it up.
Android pay and root don't work. If you want Android Pay to work, you need to disable root anytime you want to use it and even then it may not work.
buru898 said:
Did you hide/disable/uninstall supersu and reboot before opening the Android pay app?
If not, do that, and clear app data for Android pay. Then try to set it up.
Click to expand...
Click to collapse
metpage said:
Android pay and root don't work. If you want Android Pay to work, you need to disable root anytime you want to use it and even then it may not work.
Click to expand...
Click to collapse
Systemless root does work with Android Pay when root is on. At the very least, you should be able to add cards. Which means you should be able to use pay in general. Safetynet checks in Pay are not that strict.
Did you flash TWRP and boot into recovery or did you boot it from fastboot USB?
Have you tried simply putting the zip on the device and flashing it from there?
Did you let TWRP install SU/Root in the prompt before rebooting? (The answer should be no)
formula91 said:
Systemless root does work with Android Pay when root is on. At the very least, you should be able to add cards. Which means you should be able to use pay in general. Safetynet checks in Pay are not that strict.
Did you flash TWRP and boot into recovery or did you boot it from fastboot USB?
Have you tried simply putting the zip on the device and flashing it from there?
Did you let TWRP install SU/Root in the prompt before rebooting? (The answer should be no)
Click to expand...
Click to collapse
To answer,
You can read exactly what I did above. I did not let TWRP install SU for me, and rebooted using the power button I believe after installing the Beta SU from TWRP's ADB sideload..
I'll try again tonight as I KNOW Android Pay DOES work with the new Systemless Root, I just haven't gotten it right on my first try here.
Thanks.
chickentech said:
To answer,
You can read exactly what I did above. I did not let TWRP install SU for me, and rebooted using the power button I believe after installing the Beta SU from TWRP's ADB sideload..
I'll try again tonight as I KNOW Android Pay DOES work with the new Systemless Root, I just haven't gotten it right on my first try here.
Thanks.
Click to expand...
Click to collapse
Have you tried doing Android Pay before restoring stuff from Titanium Backups? There is a slim possibility that it may be altering something from system, making it fail the safetynet checks.
I would try flashing the zip from TWRP instead of sideloading as well. Just in case.
chickentech said:
...
I'll try again tonight as I KNOW Android Pay DOES work with the new Systemless Root, I just haven't gotten it right on my first try here.
Click to expand...
Click to collapse
Uh... how exactly can you know something "DOES" work if your one and only attempt at making it work was a complete failure and no one else has been able to get it to work?
Not saying Android Pay can't work with systemless route in one form or another. But to make a statement as if something is of fact when you've proven nothing to support that fact is a bit idiotic.
But hey, people said Einstein and Tesla had idiotic ideas. So here's to hoping.
sn0warmy said:
Uh... how exactly can you know something "DOES" work if your one and only attempt at making it work was a complete failure and no one else has been able to get it to work?
Not saying Android Pay can't work with systemless route in one form or another. But to make a statement as if something is of fact when you've proven nothing to support that fact is a bit idiotic.
But hey, people said Einstein and Tesla had idiotic ideas. So here's to hoping.
Click to expand...
Click to collapse
The same could be said for not doing your own research. This is a section for helping others
Right at the bottom: http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Update: Reddit user MajorNoodles has informed that Android Pay works on his Nexus 5. Chainfire, on his Google+ post, does mention that the working of Android Pay is by accident and not by design. He expects Android Pay to be updated in the future to counteract this.
Click to expand...
Click to collapse
Unless that hole has been patched already, it should still work, but we won't know for how long.
@chickentech I'm not in much of a position to help, given my location, but this might help you debug whether it is Pay being weird or if SafetyNet is tripped: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground
nvm
PhoenixTank said:
The same could be said for not doing your own research. This is a section for helping others
Right at the bottom: http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Unless that hole has been patched already, it should still work, but we won't know for how long.
@chickentech I'm not in much of a position to help, given my location, but this might help you debug whether it is Pay being weird or if SafetyNet is tripped: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground
Click to expand...
Click to collapse
Thanks...
I said I knew because I actually READ.. As you have.
Probably something to do with the order I'm doing things in.. Or as mentioned, the Titanium backup could definitely do it..
You know, I wouldn't even Root if there was a good way to block ads without - but most of what I've seen isn't quite there for me.
Again, thank you @PhoenixTank
chickentech said:
Thanks...
I said I knew because I actually READ.. As you have.
Probably something to do with the order I'm doing things in.. Or as mentioned, the Titanium backup could definitely do it..
You know, I wouldn't even Root if there was a good way to block ads without - but most of what I've seen isn't quite there for me.
Again, thank you @PhoenixTank
Click to expand...
Click to collapse
If you're rooting to modify the hosts file to block ads.... that changes system, and will trip Android Pay's SafetyNet checks. The best adblocking I can get without changing System is Adblock Plus for Android. (Root on ABP seems to only allow some sort of localhost proxy network rerouting instead)
FYI Safetynet Playground trips for me, but Android Pay works just fine.
UPDATE: Weird, now I pass, must be because I recently re-encrypted my phone.
So now it's confirmed, I can use Android Pay and not trip SafetyNet API. Neato.
Thanks! That hosts file was it.. A fresh install and I'm gold with Safetynet Many thanks all around!
You're very welcome!
Right now I'm using adblock plus + a "patcher" that's pretty "lucky" heh.
Hi there everyone !!
I gone a long way till now...
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
http://forum.xda-developers.com/nexus-5x/help/how-to-enable-oem-unlocking-bricked-t3249003
And now I'm trying to get full Stock phone with Encryption, Locked oem and systemless Root without No warnings. = S E L R N
As far as I went was S R N when i tried to encrypt it got stucked on colorful bubbles screen.
Anyone got idea how to reach this ?
Did somone checked is AdAway after changing location of host file and symlinking it, stops Google Pay/Makes additional warning while booting ?
Hi
Does anyone know anything a out the current status of Flashfire on the Pixel (XL)?
I've tried to backup data and the screen turned black, afterwards I hard to hard reset the phone to get it working again.
niko26 said:
Hi
Does anyone know anything a out the current status of Flashfire on the Pixel (XL)?
I've tried to backup data and the screen turned black, afterwards I hard to hard reset the phone to get it working again.
Click to expand...
Click to collapse
Good place to start https://plus.google.com/+Chainfire
danw_oz said:
Good place to start https://plus.google.com/+Chainfire
Click to expand...
Click to collapse
I've tried to contact him already, plus asked him in one of his threads/posts. No response.
niko26 said:
I've tried to contact him already, plus asked him in one of his threads/posts. No response.
Click to expand...
Click to collapse
It's probably because he got sick of being asked the same question over and over again.
If I read the XDA forums http://forum.xda-developers.com/general/paid-software/flashfire-t3075433 searching for the word PIXEL. This app appears that people have this working on Pixel XL, but not since the November release
danw_oz said:
It's probably because he got sick of being asked the same question over and over again.
If I read the XDA forums http://forum.xda-developers.com/general/paid-software/flashfire-t3075433 searching for the word PIXEL. This app appears that people have this working on Pixel XL, but not since the November release
Click to expand...
Click to collapse
Thanks for your comment.
I was not asking why he was not replying to my questions - I've got total sympathy for that because the number of messages he might get must be insane.
My question still stands: Obviously Flashfire is not yet aware of the different layout of partitions on the Pixel phones. Does it still work correctly? If not, did Chainfire say anything about Flashfire being fixed to work with the pixels? I couldn't find anything, that's why I'm asking here.
I assume any announcement on it working on the Pixel will be made when it works on the Pixel. Much like superSU. (hope that doesnt sound like an ass thing to say) it's just the way things have been. unless someone else works on something and it looks like they are going to beat another dev to the punch, you don't usually see any info, much like boot-loader unlocks, rooting of a certain phone etc.. i.e when there is a bounty and team blahblah looks like they gonna take the glory, BANG! suddenly there's a solution that said dev was already working on secretly but wasn't planing on releasing any time soon but since there's competition, kinda thing. Know what I mean?
SuperSU is going to be a much higher priority for him to get going reliably with twrp and the new partition layout.
larsdennert said:
SuperSU is going to be a much higher priority for him to get going reliably with twrp and the new partition layout.
Click to expand...
Click to collapse
Hey just curious what you mean by this. I know that TWRP has some bugs but I thought everything with SuperSU was worked out
I'm thinking they are still working on having them coexist without one wiping the other
larsdennert said:
I'm thinking they are still working on having them coexist without one wiping the other
Click to expand...
Click to collapse
No they work fine, especially SuperSU. TWRP is in alpha but works for installing and most other things but backup and restore does not yet.
larsdennert said:
I'm thinking they are still working on having them coexist without one wiping the other
Click to expand...
Click to collapse
Wow, that was like week number one.
You're waaaaaay behind on updates.
Lol then we should get on chain fires case
larsdennert said:
SuperSU is going to be a much higher priority for him to get going reliably with twrp and the new partition layout.
Click to expand...
Click to collapse
What? SuperSU working perfectly with twrp. As others said twrp still in alpha and some features are iffy, but SuperSU is solid.
Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?
s1dest3pnate said:
Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?
Click to expand...
Click to collapse
Are you verizon?
Because if you're verizon then add Verizon to your profile so people can appropriately address your questions.
And add your freaking state/country while you're at it. :good:
CZ Eddie said:
Are you verizon?
Because if you're verizon then add Verizon to your profile so people can appropriately address your questions.
And add your freaking state/country while you're at it. :good:
Click to expand...
Click to collapse
My apologies. T-Mobile, US - added to profile. Thanks for the suggestion!
s1dest3pnate said:
Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?
Click to expand...
Click to collapse
You can sideload the update via ADB supposedly.
I've never used that method though.
I just flash the entire update on top of my old OS using flashboot and my guide here:
http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Make sure to remove the -w from the script if you don't want your old data/apps wiped.
Then re-root your phone afterwards.
Nothing to worry about there if it's not a Verizon phone.
s1dest3pnate said:
Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?
Click to expand...
Click to collapse
I do it like in this guide http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
Very helpful, thanks guys. I did it and it worked - ran flash-all with -w removed. I wonder though if there's any downside to doing this that may not have been identified yet, such as extra space being taken up or diminished performance (even if negligible) possibly due to some duplication of data or something like that.
s1dest3pnate said:
Very helpful, thanks guys. I did it and it worked - ran flash-all with -w removed. I wonder though if there's any downside to doing this that may not have been identified yet, such as extra space being taken up or diminished performance (even if negligible) possibly due to some duplication of data or something like that.
Click to expand...
Click to collapse
No, no downside at all. Flash all without the -w is how most people do it. It could even be argued that it is better.
Sent from my Pixel XL using XDA Labs
Hi all,
Pixel 3 XL
Android 10(QP1A.190711.020)
ELEMENTALX-P3-2.05
Have a look at attached screenshots, how would one apply the new update without messing it up, i finally have GPay working, and I really want to keep it that way.
Thanks
I cant seem to be able to upload attachments, "url can not prase" ?
Not sure about keeping Google pay, but I followed A/B slot update from here https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
Everything is working fine on QP1A.190711.020.C3
You will need to reflash the kernel.
Only using systemless hosts and edge sense modules in magisk.
rob42ert said:
Hi all,
Pixel 3 XL
Android 10(QP1A.190711.020)
ELEMENTALX-P3-2.05
Have a look at attached screenshots, how would one apply the new update without messing it up, i finally have GPay working, and I really want to keep it that way.
Thanks
I cant seem to be able to upload attachments, "url can not prase"
Click to expand...
Click to collapse
How'd you get Google Pay working?
I flashed the complete system img removing the -w and re-rooted (pulled boot.img from the zip and had magisk patch it and flash in fastboot)
rquinn19 said:
How'd you get Google Pay working?
I flashed the complete system img removing the -w and re-rooted (pulled boot.img from the zip and had magisk patch it and flash in fastboot)
Click to expand...
Click to collapse
Gpay i got it working with BostonDan method.
Can you please link Boston Dan method?
skaforey said:
Can you please link Boston Dan method?
Click to expand...
Click to collapse
pretty easy to google BostonDan and Google Pay. First result. https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
Edit: Just tried it on my rooted Android 10 3XL and I was able to add my cards. Haven't used it yet but generally if I can add cards I can use it. Thanks
henderjr said:
pretty easy to google BostonDan and Google Pay. First result. https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
Edit: Just tried it on my rooted Android 10 3XL and I was able to add my cards. Haven't used it yet but generally if I can add cards I can use it. Thanks
Click to expand...
Click to collapse
I have been using that method since the day he posted it on a 3 and 3 XL. Both are on 10, and got clean wiped to do so. Both had card reinstalled and have been used at the terminal since the c3 update.
sliding_billy said:
I have been using that method since the day he posted it on a 3 and 3 XL. Both are on 10, and got clean wiped to do so. Both had card reinstalled and have been used at the terminal since the c3 update.
Click to expand...
Click to collapse
Good to hear.! I have a WearOS watch with Google Pay so I haven't had a need to use my phone much.
I have to get rid of ElementalX without losing all my stuff. This kernel has many bugs, my assistent won't start when squeezed anymore.
Is there a way?
rob42ert said:
I have to get rid of ElementalX without losing all my stuff. This kernel has many bugs, my assistent won't start when squeezed anymore.
Is there a way?
Click to expand...
Click to collapse
How exactly have you determined that it is the kernel, and what does "many bug" mean? There are a lot of us who are using ElementalX on 10 with no issues including assistant squeeze. You can start by installing any other kernel available in the "Google Pixel 3 XL ROMs, Kernels, Recoveries, & Other Development" section (you will need to re-root) and see if it makes any difference. It would also be a good idea if you posted in the dedicated thread for ElementalX. Besides getting user answers, @flar2 will be able to answer any questions specific since it is his kernel.
As for possible issues, how you installed could (dirty, clean, OTA/OTA sideload, factory image in BL) make a very possible difference as well as what version you have installed (specifically if you installed the new c3 image). It sounds like you have a bad Android 10 install and are going to end up needing a full clean install. Good luck.
rob42ert said:
I have to get rid of ElementalX without losing all my stuff. This kernel has many bugs, my assistent won't start when squeezed anymore.
Is there a way?
Click to expand...
Click to collapse
There are no bugs in ElementalX kernel.
Hi!
Like the title said i have an redmi note 8 pro with ANDROID 9 stock firmware rooted but while im try to change the name of magisk
i recive an error and dont let me change the name and also my CTS profile is false....
Someone can help me pls?
You won't be able to get around the CTS false flag now without completely removing Magisk. The requirements have changed recently.
wang1chung said:
You won't be able to get around the CTS false flag now without completely removing Magisk. The requirements have changed recently.
Click to expand...
Click to collapse
so what i need to do right now?
roberto_1986 said:
so what i need to do right now?
Click to expand...
Click to collapse
Use the uninstall feature in the Magisk manager app and reboot. If it still fails the safety net pass, I think you need to lock your bootloader which is dicey. Might want to wait for someone else to confirm the steps as it's unique to your ROM version and may cause a hard brick, but typically flashing an unmodified MiFlash tool ROM and then locking the bootloader after should do it.
wang1chung said:
Use the uninstall feature in the Magisk manager app and reboot. If it still fails the safety net pass, I think you need to lock your bootloader which is dicey. Might want to wait for someone else to confirm the steps as it's unique to your ROM version and may cause a hard brick, but typically flashing an unmodified MiFlash tool ROM and then locking the bootloader after should do it.
Click to expand...
Click to collapse
My bootloader is locked atm because im unlocked for downgrade my android 10 to android 9 then im installed stock firmware
then my bootloader is locked again and now i show u some screenshot below.
wang1chung said:
Use the uninstall feature in the Magisk manager app and reboot. If it still fails the safety net pass, I think you need to lock your bootloader which is dicey. Might want to wait for someone else to confirm the steps as it's unique to your ROM version and may cause a hard brick, but typically flashing an unmodified MiFlash tool ROM and then locking the bootloader after should do it.
Click to expand...
Click to collapse
Sorry i was unable to attach so im uploaded online then shared here
https://ibb.co/Jn3Hf20
https://ibb.co/vQPs9hB
https://ibb.co/rmZF07L
https://ibb.co/g7KX1Zc
https://ibb.co/XV77MnF
https://ibb.co/12K06DY
wang1chung said:
You won't be able to get around the CTS false flag now without completely removing Magisk. The requirements have changed recently.
Click to expand...
Click to collapse
You can get around it by using the "MagiskHide Props Config" module and using it to change your devices fingerprint. At least on Android 10(Pixel Experience, CFW, Used Pixel 4 XL fingerprint)
Images don't appear to be working so here: https://m.imgur.com/a/wZ70wOG
Sapphiress said:
You can get around it by using the "MagiskHide Props Config" module and using it to change your devices fingerprint. At least on Android 10(Pixel Experience, CFW, Used Pixel 4 XL fingerprint)
Images don't appear to be working so here: https://m.imgur.com/a/wZ70wOG
Click to expand...
Click to collapse
already tryed this method and didnt worked...
roberto_1986 said:
already tryed this method and didnt worked...
Click to expand...
Click to collapse
Did you run the script or did you just install the module?
roberto_1986 said:
already tryed this method and didnt worked...
Click to expand...
Click to collapse
Same here, that's why I thought locking was the only way. There was a thread about this somewhere, didn't think magisk hide worked anymore.
I'll try what @Sapphiress mentioned, thanks!
Edit: no dice, didn't work with the GSI option for finger print. Any suggestions on which fingerprint to use for Android 10 GSI Quack?
wang1chung said:
Same here, that's why I thought locking was the only way. There was a thread about this somewhere, didn't think magisk hide worked anymore.
I'll try what @Sapphiress mentioned, thanks!
Edit: no dice, didn't work with the GSI option for finger print. Any suggestions on which fingerprint to use for Android 10 GSI Quack?
Click to expand...
Click to collapse
im tryed doing fingerprint also but didnt worked for my phone too...thats too bad...
and what did u mean for "lock"?
Sapphiress said:
Did you run the script or did you just install the module?
Click to expand...
Click to collapse
what script are u talking about? are u talaking about fingerprint? if yes didnt worked for me
maybe with a custom rom can work?
roberto_1986 said:
im tryed doing fingerprint also but didnt worked for my phone too...thats too bad...
and what did u mean for "lock"?
Click to expand...
Click to collapse
My bootloader is unlocked and I read elsewhere that that can cause the CTS flag to fail. I tried simulating a K20 fingerprint and all it did was disable my sim, lol.
roberto_1986 said:
what script are u talking about? are u talaking about fingerprint? if yes didnt worked for me
maybe with a custom rom can work?
Click to expand...
Click to collapse
He means did you run the "props" script from a terminal
wang1chung said:
My bootloader is unlocked and I read elsewhere that that can cause the CTS flag to fail. I tried simulating a K20 fingerprint and all it did was disable my sim, lol.
He means did you run the "props" script from a terminal
Click to expand...
Click to collapse
yhea i followed the "Didgeridoohan" tutorial but didnt worked for me
also my phone is rooted but my bootloader is locked atm
Must only work on CFW then.
My bootloader is also unlocked.
My exact load out is:
CFW Pixel experience
CFW TWRP
CFW Zentisu kernel
I used the emulate device option in the props script and set it to Pixel 4 XL.
I can confirm that Netflix and Google Play works. At least on global with My setup.
Sapphiress said:
Must only work on CFW then.
My bootloader is also unlocked.
My exact load out is:
CFW Pixel experience
CFW TWRP
CFW Zentisu kernel
I used the emulate device option in the props script and set it to Pixel 4 XL.
I can confirm that Netflix and Google Play works. At least on global with My setup.
Click to expand...
Click to collapse
My bootloader in NOT unlocked
also can u be more specific?
did u have my same phone redmi note 8 pro?
wich android version are u running? mine is 9
both CTS profile and basic security is on true?
did u able to change the name of magisk?
also can u link where did u downloaded your CFW + the guide?
answer all my question pls ty
roberto_1986 said:
My bootloader in NOT unlocked
also can u be more specific?
did u have my same phone redmi note 8 pro?
wich android version are u running? mine is 9
both CTS profile and basic security is on true?
did u able to change the name of magisk?
also can u link where did u downloaded your CFW + the guide?
answer all my question pls ty
Click to expand...
Click to collapse
Yes, I have a Redmi Note 8 Pro(Global)
Android 10 CFW (Pixel Experience)
CTS Profile and basicSec are True, I've already stated that GooglePay and Netflix both work.
No, I haven't, as I don't see a reason too. If it's to hide it from other people then this can be accomplished with a 3rd party launcher, otherwise I don't see the point.
All of these questions have been answered in my previous posts aside from renaming magisk.
Everything you need to know about CFW and flashing custom ROMS is available in the Redmi Note 8 Pro megatread I advise reading it in its entirety and reading the entire comment chain(i know it's a lot buts it's important) before attempting anything, and everything else I'm using is in the Development ROMS, KERNELS, Etc. Section.
I can't really comment links right now as I'm in using the labs app.
Sapphiress said:
Yes, I have a Redmi Note 8 Pro(Global)
Android 10 CFW (Pixel Experience)
CTS Profile and basicSec are True, I've already stated that GooglePay and Netflix both work.
No, I haven't, as I don't see a reason too. If it's to hide it from other people then this can be accomplished with a 3rd party launcher, otherwise I don't see the point.
All of these questions have been answered in my previous posts aside from renaming magisk.
Everything you need to know about CFW and flashing custom ROMS is available in the Redmi Note 8 Pro megatread I advise reading it in its entirety and reading the entire comment chain(i know it's a lot buts it's important) before attempting anything, and everything else I'm using is in the Development ROMS, KERNELS, Etc. Section.
I can't really comment links right now as I'm in using the labs app.
Click to expand...
Click to collapse
well ty so much
anyway the point to change magisk manager name is because to hack some game i need to change this name or it wont work.
Sapphiress said:
Yes, I have a Redmi Note 8 Pro(Global)
Android 10 CFW (Pixel Experience)
CTS Profile and basicSec are True, I've already stated that GooglePay and Netflix both work.
No, I haven't, as I don't see a reason too. If it's to hide it from other people then this can be accomplished with a 3rd party launcher, otherwise I don't see the point.
All of these questions have been answered in my previous posts aside from renaming magisk.
Everything you need to know about CFW and flashing custom ROMS is available in the Redmi Note 8 Pro megatread I advise reading it in its entirety and reading the entire comment chain(i know it's a lot buts it's important) before attempting anything, and everything else I'm using is in the Development ROMS, KERNELS, Etc. Section.
I can't really comment links right now as I'm in using the labs app.
Click to expand...
Click to collapse
last thing....
did u used official twrp 3.4.0?
because atm im using not official twrp
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.