Related
Hello
I have a HTC10 bought from official distribution in Europe, Poland, polish telecom operator.
I am currently on Android 6.0.1 (1.95.401.4). Plan to wait for OTA with Nougat and after this, unlock my phone and install TWRP and maybe a custom rom. Since last time I rooted anything was almost 5 years ago, and I heard rumors or true statements, that rooting HTC10 can mess up my encryption I want to find some simple answers to my lack of knowledge.
1. Is it possible after unlocking and rooting or installing custom rom to fall back to my original software and state out of the box, so the HTC service center will service my phone under warranty without noticing anything?
2. Does unlocking and flashing custom rom like LeeDroid mess up or disable entirely Encryption feature? I want to use it.
3. Do I need to s-off to flash custom rom like LeeDroid or similar?
4. If I need to s-off, can I go back to my out of the box software version and lock my phone so the HTC service center will repair it under warranty?
5. How to check what "version/edition" of european HTC I have to download a proper RUU for my phone in case something goes wrong?
I know that flashing anything is connected to wiping my data, that is not a problem.
1. yes, you can go back to complete stock. bootloader unlocking is covered in warrenty
2. Encryption is not messed with, stock you will be encrypted always. with custom roms like leedroid and viper you have to option to turn it off or on. Currently with android N and custom roms you need to run without encryption at the moment for everything to work properly. this is only temporary and only if you want to run N currenty.
3. no, s-off is needed for downgrading firmware or using different firmware then your suppose to most of the time.
4.yes again, this is pretty much same answer as #1
5. hold down the volume down button and power until you boot into download mode. it will display your proper model number and current firmware version
Thank you very much for your answer. I do not plan to flash Nougat right now, I will wait for official release via OTA, after than I will check for custom rom if it supports encryption without problems and then flash it.
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!
Regards,
PoseidonKing
How can I change my keyboard to an Apple IOS one?
Hey all, just copped a US Verizon HTC 10. Haven't unboxed it yet. If I fire it up, can I take any OTA and still unlock the bootloader / root it when I want to, down the line?
I come from many Samsung Galaxy S phones - this is my first HTC - from Galaxy S experience, certain updates made rooting / safestrapping a pain or downright impossible without backpeddling to an old version of the phone.
From all I've read, I see no big red flags about <this version> or <that version> is not rootable / bypassable. It looks as if the HTC 10 is a lot easier to get around, load on a custom recovery and ROM. Please correct me if I'm wrong.
Thanks very much!
Got a couple of questions as I'm coming from a Moto X with near-stock M, and would like something a bit closer to that experience on my HTC 10. I'm not new to using custom ROMs, but I'm no expert either.
1) Is it possible to change the default clock app (click action on HTC clock widget), lockscreen (to stock android) and/or lockscreen clock widget without root or custom ROM? Lockscreen apps don't quite do it for me as every single one I've tried lags quite a lot (homescreen flashes).
2) Is it possible to install a custom ROM and stay UNrooted (for payment services etc which refuse to work on rooted devices)? I have no real need for root access other than to change my device's default apps.
3) What would be the go-to ROM and/or customization path for a GPE-like experience on the HTC 10 (Stock Android w/o Sense and HTC apps, OTA updates, stable)? Like mentioned above I have no need for performance enhancements, further tweaks or even root access. In the past I'd go for official CM, but that's not an option now I suppose.
InTents said:
How can I change my keyboard to an Apple IOS one?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1016053
---------- Post added at 08:30 PM ---------- Previous post was at 08:27 PM ----------
Trying to remove sense 8 completely, tried titanium backup but it just removed the updated version and shows in the play store to update. Tried solid browser to remove everything but fails, tried app system remover on playstore but that fails as well. Is there any zip that can remove it like on viperrom?
dbilodeau said:
Hey all, just copped a US Verizon HTC 10. Haven't unboxed it yet. If I fire it up, can I take any OTA and still unlock the bootloader / root it when I want to, down the line?
I come from many Samsung Galaxy S phones - this is my first HTC - from Galaxy S experience, certain updates made rooting / safestrapping a pain or downright impossible without backpeddling to an old version of the phone.
From all I've read, I see no big red flags about <this version> or <that version> is not rootable / bypassable. It looks as if the HTC 10 is a lot easier to get around, load on a custom recovery and ROM. Please correct me if I'm wrong.
Thanks very much!
Click to expand...
Click to collapse
Hi
some of the carriers lock their devices down, so they won't be bootloader unlocked, even through HTC. As far as I know Sprint or Verizon are one of the carriers doing this. Can't tell you for sure, as I don't use those carriers.
If unlocking is possible it can be activated in developer settings and done via HTCDev. This you'd be able to flash the latest TWRP as well as root your device using SuperSU or phhsupersu.
The 10 gets, to use someone others words, finickery as soon as you start tinkering with other firmware e.g. debranding, up- and downgrading. It's by far the most complex HTC device. And I'm using them quite a long time as you can see in my signature.
Sent from my htc_pmeuhl using XDA Labs
dbilodeau said:
Hey all, just copped a US Verizon HTC 10. Haven't unboxed it yet. If I fire it up, can I take any OTA and still unlock the bootloader / root it when I want to, down the line?
I come from many Samsung Galaxy S phones - this is my first HTC - from Galaxy S experience, certain updates made rooting / safestrapping a pain or downright impossible without backpeddling to an old version of the phone.
From all I've read, I see no big red flags about <this version> or <that version> is not rootable / bypassable. It looks as if the HTC 10 is a lot easier to get around, load on a custom recovery and ROM. Please correct me if I'm wrong.
Thanks very much!
Click to expand...
Click to collapse
Verizon bootloader cannot be unlocked. Your only option is to S-off with Sunshine, which then allows you to do whatever like flash Roms, root, etc. You should do that before flashing any of the latest updates, sunshine may not work with latest/future firmware.
ske said:
Got a couple of questions as I'm coming from a Moto X with near-stock M, and would like something a bit closer to that experience on my HTC 10. I'm not new to using custom ROMs, but I'm no expert either.
1) Is it possible to change the default clock app (click action on HTC clock widget), lockscreen (to stock android) and/or lockscreen clock widget without root or custom ROM? Lockscreen apps don't quite do it for me as every single one I've tried lags quite a lot (homescreen flashes).
2) Is it possible to install a custom ROM and stay UNrooted (for payment services etc which refuse to work on rooted devices)? I have no real need for root access other than to change my device's default apps.
3) What would be the go-to ROM and/or customization path for a GPE-like experience on the HTC 10 (Stock Android w/o Sense and HTC apps, OTA updates, stable)? Like mentioned above I have no need for performance enhancements, further tweaks or even root access. In the past I'd go for official CM, but that's not an option now I suppose.
Click to expand...
Click to collapse
Regarding your questions some hopefully helpful answers:
1) not as long as you're using a Sense based ROM. As soon as you use e.g. Viper10 in full de-sensed mode, or any CM/AOSP based custom ROM, yes.
2) in this case it'd be better to take the disadvantages named in 1), just unlock your bootloader, flash TWRP, flash magisk, and flash e.g. the Viper 10 magisk version. This you'd keep a full stock based ROM passing safety net, hobtaining full carrier features, and could load the custom ROM as a magisk module to obtain all tweaks and additions.
3) currently I'd say crpalmer's CM14.1, or one of the Resurrection Remix ROM. All are, quite stable and N based. Alternatively you could use Viper10 with a lot if tweaks and a de-sense option.
Sent from my htc_pmeuhl using XDA Labs
5m4r7ph0n36uru said:
Regarding your questions some hopefully helpful answers:
2) in this case it'd be better to take the disadvantages named in 1), just unlock your bootloader, flash TWRP, flash magisk, and flash e.g. the Viper 10 magisk version. This you'd keep a full stock based ROM passing safety net, hobtaining full carrier features, and could load the custom ROM as a magisk module to obtain all tweaks and additions.
Click to expand...
Click to collapse
Thanks, I'll look into Magisk - that one's new to me but looks very interesting.
Haven't read up on/understood it fully yet, but is the "Magisk version" just a mod "layer" on top of the stock ROM? As in I'll still be "stock" but able to disable/tweak parts of the OS?
And TWRP doesn't break safety net by itself? That's what I was starting to worry about.
ske said:
Thanks, I'll look into Magisk - that one's new to me but looks very interesting.
Haven't read up on/understood it fully yet, but is the "Magisk version" just a mod "layer" on top of the stock ROM? As in I'll still be "stock" but able to disable/tweak parts of the OS?
And TWRP doesn't break safety net by itself? That's what I was starting to worry about.
Click to expand...
Click to collapse
I'd say it is a mod directory, as magisk mounts the additional folders needed for the tweaks to work as well as replacing mount points of specific tweaked, or replaced system apps. In a custom Sense ROM it e.g. virtually replaces the prism.apk installed on system, by the tweaked one, without uninstalling the original file. To be correct without even touching the system partition of your stock ROM.
Same can be done to single apps. The GPE dialer magisk module is an example for such a mod.
After installation of magisk and magisk root you can easily reinstall the stock recovery, as far as I know. This is exactly how you preserve the safety-net functionality.
Sent from my htc_pmeuhl using XDA Labs
OK so I ran Sunshine on my Verizon HTC 10 and got bootloader and s-off. Changed cid to us unlocked and flashed us unlocked ruu. Took about 5 otas and now running 7.0 Nougat. Attempted to flash tarp thru download mode and looks like it was successful but when I boot into recovery I get this black HTC screen with red letters! After a few seconds the phone will just reboot into the os! Is there anything im doing wrong or that I need to do?
asj2583 said:
OK so I ran Sunshine on my Verizon HTC 10 and got bootloader and s-off. Changed cid to us unlocked and flashed us unlocked ruu. Took about 5 otas and now running 7.0 Nougat. Attempted to flash tarp thru download mode and looks like it was successful but when I boot into recovery I get this black HTC screen with red letters! After a few seconds the phone will just reboot into the os! Is there anything im doing wrong or that I need to do?
Click to expand...
Click to collapse
Doesn't sound like you flashed twrp successfully. Try again and pay attention to the command window messages.
Tarima said:
Doesn't sound like you flashed twrp successfully. Try again and pay attention to the command window messages.
Click to expand...
Click to collapse
What I ended up doing was unlock bootloader thru HTC device website and reflashed TWRP after and that seemed to do the trick! Funny thing was I didn't get the unlock screen after flashing the unlock token I got from htc asking if I want to unlock my bootloader!
asj2583 said:
What I ended up doing was unlock bootloader thru HTC device website and reflashed TWRP after and that seemed to do the trick! Funny thing was I didn't get the unlock screen after flashing the unlock token I got from htc asking if I want to unlock my bootloader!
Click to expand...
Click to collapse
If your on Nougat make sure you flashed the latest TWRP 3.0.3-0 unofficial which you'll find over at the TWRP thread, in the downloads tab. It sounds as if you fried to flash TWRP 3.0.2-6 which isn't compatible to Android N firmware and thus won't boot at all.
Edit: nvm saw only your previous post at first. Kind if tired. Will go to bed to read a bit better tomorrow.
Sent from my htc_pmeuhl using XDA Labs
After upgrading Viper10 1.2.1 to 4.4.0, when I press on a contacts name, I now have to hit call afterwards, whereas before, I could (from the dialer screen) just start typing someone's name using the numbers and then tap on their name and it would automatically start dialing without hitting call. Can I change it back?
aSilvrHaze said:
After upgrading Viper10 1.2.1 to 4.4.0, when I press on a contacts name, I now have to hit call afterwards, whereas before, I could (from the dialer screen) just start typing someone's name using the numbers and then tap on their name and it would automatically start dialing without hitting call. Can I change it back?
Click to expand...
Click to collapse
Weird. I'm running Viper 4.4.0 as well an don't fave this Bug at all. Doesn't seem to be ROM related. Did go up from 1.2.1 to 4.0.0 right away, or did you take all the Updates provided in between. I always updated to the latest ROM as soon as they published it, This the last time I went from 4.3.1 to 4.4.0.
Did you always check the md5 of your ROM download to make sure the download went fine!? Did you try to reinstall Viper, using a clean flash?
Sent from my htc_pmeuhl using XDA Labs
Thanks for getting back so quickly. I went straight from 1.2.1 to 4.2.0 after flashing the lastest RUU from sprint. Then up to 4.3 and now 4.4 but I noticed the issue after the initial 1.2.1 to 4.4. I didn't check the md5, but I will and then reflash and see what happens.
ADB BACKUP from pc whit android 7 nougat
i have a problem in my htc 10 usa unlocked whit nougat 2.38 .617.6 , when i have upgraded to android 7 adb backup and restore from pc dont works more.
i think why nougat encrypted to default, well i have rooted my htc 10 whit 3.0.3-0_UNOFFICIAL and supersu 279R and make it s-off ,after my phone is decrypted but have same issue when i try adb backup of my htc10 from pc fail again . any tips for enable this function again in my htc 10 whit nougat?
thanks
caxio
aSilvrHaze said:
After upgrading Viper10 1.2.1 to 4.4.0, when I press on a contacts name, I now have to hit call afterwards, whereas before, I could (from the dialer screen) just start typing someone's name using the numbers and then tap on their name and it would automatically start dialing without hitting call. Can I change it back?
Click to expand...
Click to collapse
I used to have this problem on my Verizon 10, and it went away when I converted to U.S Unlocked (and wiped my phone in the process). I'm not sure what did it exactly, but perhaps a clean flash will help. If not you can also try to update the phone apk.
Help @@
I'm getting a HTC 10 soon, and there's some question that I need to ask before I modify anything.
I saw there's some thread about radio missing and other problems when rooting (something to do with force encryption), is that still unsolved?
And here's a list that I'm planning to do, mind help me checking it?
Unlock bootloader and root
S-off
Change CID MID and RUU to US Unlocked firmware(Nougat)
Install Leedroid (Marshmallow, can't live without xposed)
Any help or advice is highly appreciated
Hello all the people out there.
Im new in the forum and english is not my mother language so, please be kind.
Hardware:
Moto G5 cedric (XT1060)
Situation:
Installed twrp-3.2.1-0-cedric.img without problems
Installed lineage-15.1-20180415-UNOFFICIAL-cedric.zip without problems
Installed open_gapps-arm64-8.1-aroma-20181116.zip without problems
Problem:
When the phone inits, the fingerprint sensor does nothing at all.
When i go to Security > Screen lock the fingerprint option doesnt exists at all. Exploring the coms (Apps > All Apps) i dont see the fingerprint service installed.
I have installed the "Ampare Fingerprint test" app and when run only says "Native Fingerprint API not found!".
Thing done:
Flash all again (TWRP + Lineage 15.1 + gapps) and the situation is the same.
Anyone have an idea and can guide me?
sk8avp said:
Hello all the people out there.
Im new in the forum and english is not my mother language so, please be kind.
Hardware:
Moto G5 cedric (XT1060)
Situation:
Installed twrp-3.2.1-0-cedric.img without problems
Installed lineage-15.1-20180415-UNOFFICIAL-cedric.zip without problems
Installed open_gapps-arm64-8.1-aroma-20181116.zip without problems
Problem:
When the phone inits, the fingerprint sensor does nothing at all.
When i go to Security > Screen lock the fingerprint option doesnt exists at all. Exploring the coms (Apps > All Apps) i dont see the fingerprint service installed.
I have installed the "Ampare Fingerprint test" app and when run only says "Native Fingerprint API not found!".
Thing done:
Flash all again (TWRP + Lineage 15.1 + gapps) and the situation is the same.
Anyone have an idea and can guide me?
Click to expand...
Click to collapse
Did you flash stock 8.1 before?
Andrej_SK said:
Did you flash stock 8.1 before?
Click to expand...
Click to collapse
Hi Andrej_SK, thanks for your reply.
This phone was never flashed.
I had the stock version and it was updated with Android Oreo 8.1, which was updated a few weeks ago.
sk8avp said:
Hi Andrej_SK, thanks for your reply.
This phone was never flashed.
I had the stock version and it was updated with Android Oreo 8.1, which was updated a few weeks ago.
Click to expand...
Click to collapse
If you installed stock Oreo 8.1 using any method (OTA, Fastboot...), you have to downgrade to stock Nougat first (using fastboot image) to make fingerprint work with CustomROMs. However, you need unlocked bootloader to downgrade. Don't flash both gpt and bootloader (if flashed any of these, you will get hardbrick because gpt/bootloader downgrade is not allowed). Also, don't run erase modem commands, they will wipe your IMEI in this case. As soon as you downgrade to stock Nougat, check the fingerprint availibility in Settings. If you can see options related to it, you're good to go - you can install any CustomROM as you normally would and your fingerprint will work.
Andrej_SK said:
If you installed stock Oreo 8.1 using any method (OTA, Fastboot...), you have to downgrade to stock Nougat first (using fastboot image) to make fingerprint work with CustomROMs. However, you need unlocked bootloader to downgrade. Don't flash both gpt and bootloader (if flashed any of these, you will get hardbrick because gpt/bootloader downgrade is not allowed). Also, don't run erase modem commands, they will wipe your IMEI in this case. As soon as you downgrade to stock Nougat, check the fingerprint availibility in Settings. If you can see options related to it, you're good to go - you can install any CustomROM as you normally would and your fingerprint will work.
Click to expand...
Click to collapse
Hi Andrej_SK, really thanks for your help.
Sorry but I'm pretty new flashing android 6+.
Lets see if i have done the correct step.
Flashed 7.x Nougat following this post: https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
IMEI is OK, fingerprint working perfectly.
This has erased TWRP, so, now i can install TWRP and then install any custom rom?
sk8avp said:
Hi Andrej_SK, really thanks for your help.
Sorry but I'm pretty new flashing android 6+.
Lets see if i have done the correct step.
Flashed 7.x Nougat following this post: https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
IMEI is OK, fingerprint working perfectly.
This has erased TWRP, so, now i can install TWRP and then install any custom rom?
Click to expand...
Click to collapse
Yes. Keep in mind that if you want to install any Oreo CustomROM, you need to do it using 64bit TWRP. If you decide to install Gapps alongside with any Oreo CustomROM too, use this tutorial https://forum.xda-developers.com/g5/how-to/how-to-repair-bootloop-oreo-roms-t3791189 to avoid bootloop.
Andrej_SK said:
Yes. Keep in mind that if you want to install any Oreo CustomROM, you need to do it using 64bit TWRP. If you decide to install Gapps alongside with any Oreo CustomROM too, use this tutorial https://forum.xda-developers.com/g5/how-to/how-to-repair-bootloop-oreo-roms-t3791189 to avoid bootloop.
Click to expand...
Click to collapse
Andrej_SK I have no words to thank you for your help.
I decided to continue using the stock rom, at least until Lineage OS is in a more stable state.
Some functions work better and I really need them.
Again thank you very much!
Fingerprint not working
Andrej_SK said:
If you installed stock Oreo 8.1 using any method (OTA, Fastboot...), you have to downgrade to stock Nougat first (using fastboot image) to make fingerprint work with CustomROMs. However, you need unlocked bootloader to downgrade. Don't flash both gpt and bootloader (if flashed any of these, you will get hardbrick because gpt/bootloader downgrade is not allowed). Also, don't run erase modem commands, they will wipe your IMEI in this case. As soon as you downgrade to stock Nougat, check the fingerprint availibility in Settings. If you can see options related to it, you're good to go - you can install any CustomROM as you normally would and your fingerprint will work.
Click to expand...
Click to collapse
Hello,
I'm facing the same problem, I came Stock rom Oreo 8.1 and then fingerprint is not working on any custom rom I've tested.
Detail: Project Treble does not even start the boot for me.
I will perform the procedure that you mentioned and leave the feedback here if the problem was solved since I saw in other forums for this device that many are with the same problem.
Edit
I downgraded to the Nougat stock rom and installation rom Pixel Experience 8.1, fingerprint is working for me now =D
Thanks Andrej_SK for the great help
Hey there, can't get my fingerprint to work on LOS 17.1, it's like it's there, but it doesn't react to anything. When I go to the fingerprint settings, it ask me to touch it in order to setup the thing, but when I place my finger on it, it does nothing. Did anyone ever heard of this issue or any fix for it? Thanks in advance.
jaroulz said:
Hey there, can't get my fingerprint to work on LOS 17.1, it's like it's there, but it doesn't react to anything. When I go to the fingerprint settings, it ask me to touch it in order to setup the thing, but when I place my finger on it, it does nothing. Did anyone ever heard of this issue or any fix for it? Thanks in advance.
Click to expand...
Click to collapse
Did you flash stock Oreo prior to flashing LOS 17.1?
rahimali said:
Did you flash stock Oreo prior to flashing LOS 17.1?
Click to expand...
Click to collapse
Nope coz I use a Galaxy S7 so Oreo is not compatible with it, isn't it?
jaroulz said:
Nope coz I use a Galaxy S7 so Oreo is not compatible with it, isn't it?
Click to expand...
Click to collapse
You are posting in the Moto G5 forum
If you are using a galaxy s7 I suggest that you go and post your question in the correct rom section for your phone as no one here will be able to help you
Goto the following thread for Los 17 on a galaxy s7 & make sure you are using that build
https://forum.xda-developers.com/ga...ta-lineageos-17-0-galaxy-s7-build-1-t3980101/
please delete this post, can't find the option to delete...
My wife had been on whatever stock ROM came on her Pixel 2 since i bought it with no issues. She ran into a problem after maxing out her storage that the phone wouldn't boot and stayed stuck at the "G" boot screen. I got that fixed by sideloading an OTA of what seems to be some pre-release version of Android. it says "R" version. Many vital apps aren't working correctly - messaging, gmail, can't search from google bar, camera stopped working properly. So i am thinking i should start fresh and install something else now that at least the OS is back booting properly and hopefully everything will work ok.
I just want to make sure if anyone can help tell me what i'm dealing with, i believe this was a locked bootloader? not sure i can or need to unlock it.... > Install twrp... > Flash stock rom...? she doesn't need a fancy rom just something simple and stable.
Here's some of her vital info, any tips greatly apprecaited as i'm out of the loop on this stuff and an old pedestrian user at best.
Android Version
R
Baseband version
g8998-00020-1912200251
kernel version
4.4.210-gf13e65034114-ab6213703
Build Number
Rpp2.20227.009
Since your phone boots now. Simply wiping out everything should do the trick i guess.
Yeah. You can a factory reset. Your are currently on Android 11(R) preview ROM, it's still in the early phases and not suitable as a daily driver.
If all fails you can always flash a factory image, just remember to backup your data first.
Is this device a carrier device and if so, which carrier? You can only flash factory images with an unlocked bootloader so you need to figure that out first.
To figure out if you can unlock the bootloader you will first have to figure out if you have a Google or Verizon variant. Google variants can be unlocked. Verizon variants, for the most part, can't (although there is a thread where I believe someone may have done it on a Verizon variant). To figure out if you have a Google or Verizon, go here... https://www.imeipro.info/check_lg.html
Under "Buyer Name", if it says Google you're good to go. If it says Verizon or VZW, then you can't unlock the bootloader (unless the method in the thread I mentioned above actually works).
If you find you have a Google variant then via fastboot unlock the bootloader and fastboot flash the latest Q factory image.
https://9to5google.com/2020/04/23/h...d-11-dp1-to-android-10-on-google-pixel-video/
u need check ur phone can or not unlock bootloader.
if can... first thing u need to do is enable " oem unlock" in "development options"
when u unlock u can flash whatever firmware you want.
.
the problem u in android 11 . this very much bug.
Once you unlock, it'll wipe the phone.
You say you're running 11 DP1... At this point, I'd suggest signing up for the beta program and let the system update to I'd imagine the latest preview. Doing this should not wipe the phone.
From there you should have a working device and can back up what you want.
You should be given the option to unenroll on the beta website. Doing that, will downgrade the phone to the latest 10 release. it WILL also wipe the phone.
Go here. I see there's a link that could help you out.
google.com/android/beta
As title really, never flashed a custom ROM (at least not since my Galaxy S2) and while wait the 7 days to unlock the bootloader i'm trying to gather as much info as possible. So here goes;
1) Whilst I wait for the bootloader to unlock can I still turn off my phone and swap sim cards or will it reset the timer?
2) My Poco F3 is on MIUI Global 13.0.7.0 (SKHEUXM) - do I need to downgrade to 13.0.3.0 as per the instructions here?
3) The instructions for installing Crdroid lists an optional step for installing "DFE" but I cant seem to find out what DFE actually is.
4) Is it important to know if my phone has an A/B partition system and if it is how do I check for it?
5) After installing Magisk what other modules/tools/apps do I need to ensure Google Pay/Wallet will work as it seems a recent update has made it harder to fix.
6) Are there any bits of advice you can give for a avoiding a bootloop and/or bricked phone situation? Are there any common mistakes people make leading to a bootloop or bricked phone?
I think that's everything for now
Thanks
Goooober said:
As title really, never flashed a custom ROM (at least not since my Galaxy S2) and while wait the 7 days to unlock the bootloader i'm trying to gather as much info as possible. So here goes;
1) Whilst I wait for the bootloader to unlock can I still turn off my phone and swap sim cards or will it reset the timer?
2) My Poco F3 is on MIUI Global 13.0.7.0 (SKHEUXM) - do I need to downgrade to 13.0.3.0 as per the instructions here?
3) The instructions for installing Crdroid lists an optional step for installing "DFE" but I cant seem to find out what DFE actually is.
4) Is it important to know if my phone has an A/B partition system and if it is how do I check for it?
5) After installing Magisk what other modules/tools/apps do I need to ensure Google Pay/Wallet will work as it seems a recent update has made it harder to fix.
6) Are there any bits of advice you can give for a avoiding a bootloop and/or bricked phone situation? Are there any common mistakes people make leading to a bootloop or bricked phone?
I think that's everything for now
Thanks
Click to expand...
Click to collapse
1) Yes.
2) No, 13.0.3.0 is the required minimum, you can always use higher.
3) It disables forced encryption.
4) Poco F3 is A/B.
5) If any issues arise, you can always hide magisk and use safetynet fix.
6) When people don't follow installation instructions properly.
Dfe is disable force encryption but i dont think it works for android 12 so no need to flash it
ApexPrime said:
Dfe is disable force encryption but i dont think it works for android 12 so no need to flash it
Click to expand...
Click to collapse
It works, with DFE you can flash files from internal storage in twrp. But it also compromises phone security, so it's recommended not to use it.
If my phone is A/B do i have to do anything different when i flash Crdroid in TWRP?
Goooober said:
If my phone is A/B do i have to do anything different when i flash Crdroid in TWRP?
Click to expand...
Click to collapse
Almost all modern phones now ship with A/B partitions. So no, just follow the instructions given by the rom developer.
1. I unfortunately can't answer.
2. I wouldn't, 13.0.3 to 13.0.7 is very minor
3. DFE = Disable-Force-Encrypt = Android by default is encrypted.
DFE.zip removes the Boot-argument responsible for encrypting the Userdata-partition on the first boot, located in /vendor/etc/fstab
4. Poco F3 has an A/B-Partitionlayout. Most phones released with ~Android 10+ have A/B.
5. Personally, with the recent change, I tried many things to get GPay to work, got fed up with the Cat & Mouse Game with Google, and locked my BL.
6. If you flash using Fastboot Mode and the Flash aborts during a Partition-flash, don't reboot your phone, because otherwise your phone may never reboot back into Fastboot etc, and only show a Black screen.
ApexPrime said:
Dfe is disable force encryption but i dont think it works for android 12 so no need to flash it
Click to expand...
Click to collapse
It works on Android 12.
Goooober said:
If my phone is A/B do i have to do anything different when i flash Crdroid in TWRP?
Click to expand...
Click to collapse
No difference.
Further Notes about DFE:
If you don't use DFE before First Boot, userdata-partition gets encrypted, which means, beyond that, only TWRP SKKK will be able to access the userdata-partition.
If you decide to flash DFE once, you must flash it directly after every Update in TWRP, otherwise your phone may bootloop. At least that was the case for me! Before an update I decided I want my storage encrypted, but I got a bootloop. ^^
I wouldn't use DFE. Just leave it encrypted.
cyanGalaxy said:
5. Personally, with the recent change, I tried many things to get GPay to work, got fed up with the Cat & Mouse Game with Google, and locked my BL.
Click to expand...
Click to collapse
If you lock your bootloader after flashing a custom ROM does the custom ROM still work as intended or do you have to go back to stock?
Goooober said:
If you lock your bootloader after flashing a custom ROM does the custom ROM still work as intended or do you have to go back to stock?
Click to expand...
Click to collapse
Your phone will bootloop if you do that, because locked bootloader prevents custom roms from starting, thus it can only be used on stock roms.
Goooober said:
If you lock your bootloader after flashing a custom ROM does the custom ROM still work as intended or do you have to go back to stock?
Click to expand...
Click to collapse
No, I don't use a Custom ROM anymore. I'm back to Stock ROM, MIUI 13.0.7 for Europe.
Don't lock the BL with a Custom ROM. Only the Official ROM. Otherwise you risk hardbricking your phone.