Database Develop

[ROM] [UNLOCKED BOOTLOADER] Fire OS 4.5.2

For anyone who has an unlocked bootloader and wants to update to Fire OS 4, here's a stock 4.5.2 ROM that won't overwrite your current unlocked bootloader or recovery partition.
DOWNLOAD HERE
All credit goes to Cpasjuste for the current version - I might be uploading 4.5.5 here soon.

bmccoy11 said:
For anyone who has an unlocked bootloader and wants to update to Fire OS 4, here's a stock 4.5.2 ROM that won't overwrite your current unlocked bootloader or recovery partition.
DOWNLOAD HERE
All credit goes to Cpasjuste for the current version - I might be uploading 4.5.5 here soon.
Click to expand...
Click to collapse
Any feedback on this ROM?
Can this be installed on its own? Can I wipe /system and install? Downloading now but figured I'd ask here.

riggsandroid said:
Any feedback on this ROM?
Can this be installed on its own? Can I wipe /system and install? Downloading now but figured I'd ask here.
Click to expand...
Click to collapse
Yes, it can be installed over a cleanly wiped system partition. This is just the stock ROM that doesn't overwrite unlocked bootloaders when flashed.

bmccoy11 said:
Yes, it can be installed over a cleanly wiped system partition. This is just the stock ROM that doesn't overwrite unlocked bootloaders when flashed.
Click to expand...
Click to collapse
Right so when I borked my previous rom (ooooops) without a backup, this will give me stock Amazon rom back.
Thanks.
@bmccoy11
Ok so it flashed fine and I noticed you already did otacerts.old in /system/etc/security and I don't see the dcp apk in /system/app, however it tried DL'ing an update right away.
How do you recommend stopping OTAs?
Trying this method - http://forum.xda-developers.com/kindle-fire-hdx/general/tut-disable-ota-4-5-2-install-gapps-t3043550 - seems to work
Thanks.

bmccoy11 said:
Yes, it can be installed over a cleanly wiped system partition. This is just the stock ROM that doesn't overwrite unlocked bootloaders when flashed.
Click to expand...
Click to collapse
Is the 4.5.5 build far away? Might give it a crack over the weekend if it will be up.

Yes, the 4.5.5 is available here, already OTA blocked. I had to do a factory reset after flashing it (use ONLY the factory reset within TWRP, NOT the native factory reset) to get it to work, but after that, clear sailing, works great.

Ok, I'm a little confused about the process. My kindle fire is sitting at 4.5.4. I have refused to turn it on, because I don't want it to take 4.5.5. I want to re-establish root. I understand there is a downgrade process that allows you to move back to 4.5.2, then you can install root.
My question is, how do I unlock the boot loader at this point? Do I need to have an unlocked boot loader to install new images. I really want to be able to root and have the google play store installed, and not have all the bull**** errors like before with the playstore crashing.
Thanks to all you guys that have the answers and knowledge.

rlkellyjr said:
Ok, I'm a little confused about the process. My kindle fire is sitting at 4.5.4. I have refused to turn it on, because I don't want it to take 4.5.5. I want to re-establish root. I understand there is a downgrade process that allows you to move back to 4.5.2, then you can install root.
My question is, how do I unlock the boot loader at this point? Do I need to have an unlocked boot loader to install new images. I really want to be able to root and have the google play store installed, and not have all the bull**** errors like before with the playstore crashing.
Thanks to all you guys that have the answers and knowledge.
Click to expand...
Click to collapse
You can not unlock the bootloader on that device as it can not be rolled back to a version of FireOS (3.2.3.2 or below) containing the vulnerability that the unlock procedure exploits. The lowest you can go is 3.2.8. Any attempt to go further will result in a brick.
To get to 4.5.2 you rollback to 3.2.8 first using the procedure in this thread. Follow instructions precisely or you can damage/brick your device. Understand there are risks involved; this is not a task for the uninformed. There are no step-by-step guides or slick videos. Copious reading is your best friend along with the community servicing HDX forums.
Once on 3.2.8 you can upgrade to 4.5.2, block OTA, root, install Safestrap v4 and then Nexus v4 or cm11 both of which give full access to the Google Play Store. I strongly advise against attempting to install the play store under FireOS. Amazon and Google components do not play nice. Best use a different rom.
Do some reading and decide if you are up for the adventure. Ask questions before acting. Make sure you fully understand the relevant tasks, expected outcomes and things you should never do (like enable WiFi while on 3.2.8 - instant brick).
Edit: Fixed typos...

Thanks! but i have a question, why CM ROM the sound quality is very bad, even i install Dolby.

a442509097 said:
Thanks! but i have a question, why CM ROM the sound quality is very bad, even i install Dolby.
Click to expand...
Click to collapse
Search the HDX LineageOS 14.1 thread; many claim Viper4 is a better solution. Seems a bit complicated to obtain/install but that may be a faux impression. I am satisfied with Dolby but don't demand much from my device from an audio performance perspective.

how to delete this reply…

a442509097 said:
Viper4 is same too, i think this is about audio drive problem, because i try 4.22 or 4.4.4 system(however custom) sound quality has enough bass.
Click to expand...
Click to collapse
Might reach out to those who have installed (and presumably customized) Viper4 for this device. They claim sound quality is equal to if not superior to stock FireOS v4 (4.4.x base). I did notice a mild degradation going from Fire Nexus KTU84Q (4.4.4) to Android 5+ but not enough to warrant additional actions beyond installation of Dolby for noise reduction (random pops during quiet passages) and extended volume range. The builds were heavily customized when development resources were heavily focused on ROM enrichment. Things are different now; you'll likely have to roll your own if you believe this issue is with core binaries. Third gen devices have been out of production for 2+ years.

You sure about that? Wikipedia page for the series is under the impression they're still producing and selling the 7 inch HDX (which never got a 4th gen release), at least for LTE users.

Insidious622 said:
You sure about that? Wikipedia page for the series is under the impression they're still producing and selling the 7 inch HDX (which never got a 4th gen release), at least for LTE users.
Click to expand...
Click to collapse
LOL - since when did Wikipedia become the definative resource for Amazon devices? 3rd gen HDX is definitely out of production and has been for quite some time.

Fair enough, I just wasn't sure. Sometimes it's accurate, sometimes it isn't

Hi guys i need a zip or a backup. fore the orginal apollo room. i delet the backup fore safetrap and now i stuck at cm 4.4.4 and i will unlock my bootloader and install a other room but i need a orginal apollo backup or a zip to flash.

Serbest955 said:
Hi guys i need a zip or a backup. fore the orginal apollo room. i delet the backup fore safetrap and now i stuck at cm 4.4.4 and i will unlock my bootloader and install a other room but i need a orginal apollo backup or a zip to flash.
Click to expand...
Click to collapse
Bootloader can be unlocked while using CM 11 (KitKat 4.4.4) under Safestrap. Just follow the instructions. No need to reload FireOS.

Davey126 said:
Bootloader can be unlocked while using CM 11 (KitKat 4.4.4) under Safestrap. Just follow the instructions. No need to reload FireOS.
Click to expand...
Click to collapse
I need help while I understand the service not quite? How do I create this unlock file?
i follow this instruktion https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982 and i have now install twrp and need now the unlock file.

texmexdud said:
Yes, the 4.5.5 is available here, already OTA blocked. I had to do a factory reset after flashing it (use ONLY the factory reset within TWRP, NOT the native factory reset) to get it to work, but after that, clear sailing, works great.
Click to expand...
Click to collapse
Links to that one are dead, could you please give up to date links?

[GUIDE] Installing OxygenOS on Chinese models, easy rooting guide and much more!

Ok so I've seen a lot of confusion on how to correctly flash OxygenOS on your brand new OnePlus 5, and also how to correctly and easily root your phone.. This guide aims to clear up any confusion regarding this. Ready? Let's move on.
Q: What's the difference between International and Chinese versions of the OnePlus 5?
A: Hardware-wise there is absolutely no difference between the 2 versions. In terms of software, the international version runs OxygenOS (OOS) while the Chinese version runs HydrogenOS(H2OS). H2OS has no Google services pre-installed and is generally not recommended for use outside China. Both OxygenOS and HydrogenOS are official updates by OnePlus.
Q: I bought a Chinese phone. How do I install OxygenOS then?
A: 1. Download the latest OxygenOS from here. Download the full zip and NOT the OTA update.
2. Place it in the root of your internal memory. Basically don't put the file in any folder.
3. Go to Settings > System updates, press the gear icon and select Local upgrade.
4. Choose the file, the phone will boot into recovery and everything is done.
Q: OK I want to root my phone but I don't want to lose Android Pay, Netflix, Pokemon GO etc. Is it possible?
Simple answer: Yes. Long answer: Maybe not in the long run.
Why is that so? You see, back in the old days there were little downsides to rooting. Alas, Android Pay and Pokemon GO came along, and in an effort to tighten up security, Google implemented this thing called
SafetyNet. Basically it's a measure to test your system integrity, meaning that any modification to system will trigger SafetyNet and many apps will be "locked down". Android Pay and Pokemon GO will not work,
and Netflix won't show up on Google Play anymore. Some devices even check for unlocked bootloader, but apparently not the OnePlus 5, so you don't have to switch to a custom kernel to root.
To overcome this problem, the brilliant minds at XDA came up with system-less root. Chainfire was the first to implement it in SuperSU, but right now nobody uses SuperSU anymore. Magisk is the new kid in town,
and quite frankly much better IMO.
Q: Alright enough talk, how do I root the phone?
A: Patience my young Padawan. I will get to that in a moment. But here are some things you have to know.
1. Rooting involves unlocking your bootloader, and ALL YOUR DATA WILL BE WIPED. Keep a backup and move everything in your internal memory somewhere else.
2. Magisk may beat SafetyNet now, but there is no guarantee this will always be the case. So your SafetyNet enabled apps may not work all the time.
3. OTA updates from OnePlus will work differently when you are rooted. But hey that's what this guide is for. :good:
Easy rooting guide
1. Install ADB drivers.
2. Go into settings > about phone. Press the build no. a few times to activate developer options.
3. Turn on developer options, OEM unlocking and USB debugging.
4. Connect phone to PC and allow ADB access on phone. Wait for drivers to finish installing.
5. Download and install this simple tool on your PC.
6. Download one of the 2 TWRP recoveries below.
TWRP Official
xdvs23's TWRP
7. Open the All-in-One tool and make sure your device is recognised as OnePlus 5. Click on Unlock bootloader. Your bootloader is now unlocked and all your DATA WILL BE WIPED!
8. Select the "and boot it" arrow and click flash TWRP, click manual mode and choose the TWRP.img file you downloaded earlier.
9. After everything is done, your phone should now boot into TWRP successfully. Do not reboot yet.
10. On your PC, download the latest version of Magisk. Place the zip file onto your phone using USB and flash it with TWRP. Clear cache and reboot into system.
11. You should now see a new app called Magisk Manager. Check for updates!
12. However, do keep in mind not to mess around the system. If you need something, check to see if there any Magisk Modules available. There is also a small repo in the downloads section in Magisk Manager. Also Adaway works great with Magisk. Just make sure to turn on systemless host file in Magisk manager.
14. Congrats you are now rooted!:highfive:
Q: Alright now that I'm rooted, how do I get official updates?
A: 1. Download the latest OxygenOS from here. Download the full zip and NOT the OTA update. Place it on your phone. Make sure you also have your Magisk zip.
2. Boot into TWRP. Press the volume button when the bootloader unlocked screen comes up. Use volume buttons and power button to select recovery.
3. Flash the OxygenOS zip file. DO NOT reboot yet!
4. Tap the home button and flash Magisk. Clear cache.
5. Reboot into system and you are done!
Hope this guide is simple enough for you guys to understand. It might seem daunting at first, but practice makes perfect.
Also it is not a requirement to root, most people get by fine without ever rooting. But we are not like normal people, are we? Why else would we be on XDA then?
Further questions
Q1: Why Magisk and not SuperSU?
A: Besides the fact that Magisk is being constantly updated to bypass SafetyNet, it is also open-source. Wish I could say the same for SuperSU, the app is not what it used to be. Chainfire is no longer aware of the changes made in his app and I for one am not willing to take my chances with a shady developer. I had countless bad experiences with Chinese apps, many of them created by large companies. Check out this thread for more info.
Q2: Why exactly is HydrogenOS not recommended for use outside China?
A: Besides the aforementioned lack of Google apps, HydrogenOS is also tweaked differently from OxygenOS. It is significantly more aggressive in killing apps and not letting them run in the background, as you would expect with the number of rogue apps in China, made worse by the fact that there is no Play Store in China. OxygenOS on the other hand has a limit of 32 apps in memory, which I guess is a nice compromise between performance and battery life.

Reserved just in case. Probably will never need it though.

to be fair, there are still lots of people using SuperSU..

What should I do if I still want to use SuperSU?

2 noob questions @jasonwsc or anyone who knows
How about wiping dalvik and cache?
And how about encryption? Do I need to remove my fingerprint/security pattern before flashing OR rooting?
Thanks a lot for your help, the OP5 will be the first phone I can actually root. My old Xperia Z (2013) had a locked bootloader that was not unlockable haha.

ipredatorv said:
2 noob questions @jasonwsc or anyone who knows
How about wiping dalvik and cache?
And how about encryption? Do I need to remove my fingerprint/security pattern before flashing OR rooting?
Thanks a lot for your help, the OP5 will be the first phone I can actually root. My old Xperia Z (2013) had a locked bootloader that was not unlockable haha.
Click to expand...
Click to collapse
Wiping Dalvik and cache is usually done after flashing a ROM in TWRP. Not that big of deal now that many apps use ART, but still good to do to prevent app crashes.
No need to remove fingerprint security before rooting.

iamelton said:
to be fair, there are still lots of people using SuperSU..
Click to expand...
Click to collapse
Ningyou Higeki said:
What should I do if I still want to use SuperSU?
Click to expand...
Click to collapse
Just flash SuperSU zip instead of Magisk.
I don't know why anyone still uses SuperSU though. For one, it's sold to a Chinese company and is no longer open source. Not to mention it doesn't pass SafetyNet at all.

jasonwsc said:
Wiping Dalvik and cache is usually done after flashing a ROM in TWRP. Not that big of deal now that many apps use ART, but still good to do to prevent app crashes.
No need to remove fingerprint security before rooting.
Click to expand...
Click to collapse
Thanks for the clarification!
I only asked about wiping dalvik/cache because some other people here recommended that, as it may help to fix my battery drain issue.
Sent from my ONEPLUS A5000 using Tapatalk

ipredatorv said:
Thanks for the clarification!
I only asked about wiping dalvik/cache because some other people here recommended that, as it may help to fix my battery drain issue.
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
It might help with your battery drain issue, but chances are some apps are running in the background draining your battery.

Google services not working
I have installed oxygen OS in my chinese version OP5 following above method. However, after installing oxygen OS my google play store isnt working. When I open google play store, it stucks on checking info.

Nishatian1 said:
I have installed oxygen OS in my chinese version OP5 following above method. However, after installing oxygen OS my google play store isnt working. When I open google play store, it stucks on checking info.
Click to expand...
Click to collapse
Just a wild guess, but are you still in China? Check your VPN before trying to access the Google Playstore. Otherwise, remove the Playstore and download the most recent Playstore apk from a website like apkmirror. If they offer multiple versions, go for ARM 64.
Sent from my ONEPLUS A5000 using Tapatalk

jasonwsc said:
Just flash SuperSU zip instead of Magisk.
I don't know why anyone still uses SuperSU though. For one, it's sold to a Chinese company and is no longer open source. Not to mention it doesn't pass SafetyNet at all.
Click to expand...
Click to collapse
I'm a little tired of tuning my phone now. And I don't care about SafetyNet. BTW, how's Magisk's compatibility now?

jasonwsc said:
Just flash SuperSU zip instead of Magisk.
I don't know why anyone still uses SuperSU though. For one, it's sold to a Chinese company and is no longer open source. Not to mention it doesn't pass SafetyNet at all.
Click to expand...
Click to collapse
I got my Chinese OP5 two days ago and went through the whole procedure of unlocking, rooting, and flashing OxygenOS. Now I see that somebody took the time to write a nice guide on how to do it. Thanks @jasonwsc! I really wish I had this available to me already. I am sure it's gonna be a great help to others though!
I wasn't aware that SuperSU had been sold to a Chinese company through and that it is no longer open source. Knowing what I know now I regret flashing SuperSU yesterday and would love to switch to Magisk.
My question would be: what's the "proper way" to switch from SuperSU to Magisk? Just unroot via SuperSU and flash Magisk, or is there a better, cleaner way?
Edit:
Nevermind, just searched it and there's a super nice guide here.

Ningyou Higeki said:
I'm a little tired of tuning my phone now. And I don't care about SafetyNet. BTW, how's Magisk's compatibility now?
Click to expand...
Click to collapse
Magisk works fine, have no issues so far.

Hello,
I have the opportunity to receive an OP5T (128 GB)
from China. The ROM will be Hydrogen OS and not Oxygen OS.
I would like to be sure that the procedure used to install Oxygen OS will be the same as for the OP5?

Moazamali said:
Hello,
I have the opportunity to receive an OP5T (128 GB)
from China. The ROM will be Hydrogen OS and not Oxygen OS.
I would like to be sure that the procedure used to install Oxygen OS will be the same as for the OP5?
Click to expand...
Click to collapse
Yes it's the same. Just flash the firmware file for OP5T instead of the OP5.

i have international model oneplus 5. My phone was bricked, so i unbricked the phone by flashing h2os. I have rooted my phone with supersu and unrooted it again by flashing stock recovery. i want to now flash my phone with oxygenos. i have tried but no success. Please guide me with correct method.
Thanks

nayemohd said:
i have international model oneplus 5. My phone was bricked, so i unbricked the phone by flashing h2os. I have rooted my phone with supersu and unrooted it again by flashing stock recovery. i want to now flash my phone with oxygenos. i have tried but no success. Please guide me with correct method.
Thanks
Click to expand...
Click to collapse
See here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 it might be useful to format internal storage.

strongst said:
See here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 it might be useful to format internal storage.
Click to expand...
Click to collapse
Good morning all,
I have the same problem. Installed a H2os on a international oneplus 5.
Didn't like it so much so I formatted the system and installed the open beta 26.
However if I want to use the latest recovery either to clear cache or davlik cache I get a bunch of errors.
Any idea why?

kimon60 said:
Good morning all,
I have the same problem. Installed a H2os on a international oneplus 5.
Didn't like it so much so I formatted the system and installed the open beta 26.
However if I want to use the latest recovery either to clear cache or davlik cache I get a bunch of errors.
Any idea why?
Click to expand...
Click to collapse
Which h2os version and which recovery version did you use(file names please)? What do you mean with formatting the system? What did you wipe or format exactly?

News about root for this device?

Anyone know a secure procedure and a custom recovery compatible?

marte66 said:
Anyone know a secure procedure and a custom recovery compatible?
Click to expand...
Click to collapse
We don't have TWRP yet, it's not officially out yet for any G7 models and I don't know when ours may be.
Root your G7 with Magisk
I noticed this method without using TWRP on the G7 XDA forum but haven't tried it, and you must unlock the bootloader first. Apparently it's working for a few G7 users so it should on G7+ too if the correct boot.img is used (for G7+/'lake' not G7/'river') according to your release channel. You still wouldn't have a custom recovery but could install Adaway, Magisk modules, and gain full access to the file system.
EDIT:
If anyone tries this method please report back, and don't forget to unlock the bootloader first and use the Lake/G7 Plus firmware from lolinet. No one has reported it not working but only a handful have used it afaik. I'm on RETLA w/Dec security patch so would rather wait until OTA updated and then I might try it because it would give me everything I need from root except nandroid backups and installing ROMs (of which there aren't any yet). I have my unlock code ready to go and have the needed boot.img from my channel-specific firmware but remain fully stock.
The instructions aren't that detailed but I found you can install Magisk Manager as an apk, open it and when you tap on Install Magisk 18.1 (which isn't installed yet) it also gives the option to "patch boot.img" (which I didn't select but assume it'll let you navigate to where you put the one from firmware & not alter the currently booted partition). When finished you put/copy that altered one on your pc (preferably in your Fastboot/ABD folder) and fastboot flash it, then reboot and you should be rooted in Magisk.
EDIT #2:
Tried it, it works!

I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?

washoq said:
I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?
Click to expand...
Click to collapse
If someone on your channel could capture their PPW29.98-66 OTA before installing, otherwise I think you'd have to wait until it appears on lolinet or Motorola's site, or we get TWRP. I realized I'd be in the same boat because my current firmware was also the only one so far on lolinet, so I decided to go ahead because I'd only get January's security patch (on Dec now) and still be a few months behind anyway.
Having done it I can say that Magisk Manager does let you navigate to the stock boot.img file after offering to patch it, then it goes through the same familiar steps as when installing in TWRP, and at the end tells you it's in your Download folder with the name patched_boot.img. After transferring to my pc I renamed it to boot.img and just manually typed in the fastboot flash boot command.
I also want to repeat that although rooted there's still no custom recovery/TWRP so you can't do nandroid backups, and now when my channel's OTA comes along I'll have to disable Magisk & flash back to my original boot.img before taking it, which I hope works but it should. It's great being rooted though on G7+ with Adaway and Youtube vanced background play, also Root Explorer to change my boot animation or debloat or whatever.

Dahenjo said:
If someone on your channel could capture their PPW29.98-66 OTA before installing, otherwise I think you'd have to wait until it appears on lolinet or Motorola's site, or we get TWRP. I realized I'd be in the same boat because my current firmware was also the only one so far on lolinet, so I decided to go ahead because I'd only get January's security patch (on Dec now) and still be a few months behind anyway.
Click to expand...
Click to collapse
Yeah, I thought so. Thanks anyway.

washoq said:
I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?
Click to expand...
Click to collapse
I see there is a PPW29.98-66 RETAIL channel firmware on lolinet:
https://mirrors.lolinet.com/firmware/moto/lake/official/RETAIL/
I'm not sure what difference the boot.img would have between them if any, and the RETAIL channel is more a 'generic' type which might be a safer choice than others of the same build version. I know the G5+ debloated ROMs by NZedPred ended up with just one version (instead of by various channels as he did originally) after finding he didn't need to bother, though I believe he did make other changes. He'd be a good one to ask though if you want to PM him.
After I get updated (revert to full stock etc) I may try the RETAIL one to re-root to see if we can use it for this purpose regardless of channel. My 'international model' from Amazon is actually just the RETLA channel since it wasn't released in the US, so I'd almost rather be on the more generic channel if it works.
EDIT:
Did some experimenting, reverted to full stock then successfully tried it again with the boot.img from the RETAIL firmware (which for my version is still PPW29.98-28), so I believe RETAIL could be used for other channels too.

This process worked for me. Moto G7 Plus, International Unlocked version.

This worked for me, XT1965-2, AT&T mexican version. Also, managed to run Substratum, just needed to compile, reboot and activate each time I changed theme.

Well I am on the same Page...
Also my Channel Islands reteu2, I can only find reteu...
My g7pluswas shipped already with a newer Version than available. Anyone tried the retail bootloader?
Alternatively, can we somehow flash the whole "retail" version on this phone?

shaDNfro said:
Well I am on the same Page...
Also my Channel Islands reteu2, I can only find reteu...
My g7 was shipped already with a newer Version than available. Anyone tried the retail bootloader?
Alternatively, can we somehow flash the whole "retail" version on this phone?
Click to expand...
Click to collapse
I assume you have G7 Plus (not G7) with the build number you showed.
To answer your question:
I successfully fastboot flashed the full RETAIL channel PPW29.98-66 firmware a few days ago. I was on RETLA PPW29.98-28 with the December security patch and now have the January patch, and my channel is still shown as RETLA. I used the batch file posted in this thread which worked perfectly. Everything for my XT1965-2 RETLA model is working as it should on the newer RETAIL firmware, but I don't know if your RETEU2 has anything different that could cause issues.

Enforced Verity, Unlocked Bootloader, rooted Lake OPENMX Not working with Google Pay
"Couldn't finish setup to pay in stores
This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
Did I screw up by not preserving dm/verity when I patched the boot and if so, is there a way to fix it? Reflash oem rom, reinstall magisk, repatch boot, rereflash new rom with dm/verity preserved?

vvarrior said:
"Couldn't finish setup to pay in stores
This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
Did I screw up by not preserving dm/verity when I patched the boot and if so, is there a way to fix it? Reflash oem rom, reinstall magisk, repatch boot, rereflash new rom with dm/verity preserved?
Click to expand...
Click to collapse
I tried everything but its not working stalble for me either.
You can do delete google pay cache+data and google play services cache+data, reboot and then you can configure a payment method (e.g. add credit card). Afterwards I was able to pay exactly one time... next time it refues my card telling me I am not able to pay with that card any more...
(Bye the way, people say the issue might be connected with wifi as well, so I turned off wifi for that procedure I mentioned above)
Anyway I deleted google pay now using my banks own application, which does not detect root using magisk hide

shaDNfro said:
I tried everything but its not working stalble for me either.
You can do delete google pay cache+data and google play services cache+data, reboot and then you can configure a payment method (e.g. add credit card). Afterwards I was able to pay exactly one time... next time it refues my card telling me I am not able to pay with that card any more...
(Bye the way, people say the issue might be connected with wifi as well, so I turned off wifi for that procedure I mentioned above)
Anyway I deleted google pay now using my banks own application, which does not detect root using magisk hide
Click to expand...
Click to collapse
There's a bunch of Google apps that need verity to be enforced I think. I think we need the stock ROM with the stock boot. Maybe the phone has to be rooted to patch the stock boot.img with verity enforced? I'm not sure but I stepped up to the G7 Plus because it finally has NFC so I can use it to pay and it was an unlocked international version that works good with Google Fi (which also needs verity enforced).
Still looking for a solution and will probably just go back to my old phone until I can get Google Fi and Pay working.

Help a new owner out with a couple of root questions

Hi! So a brand new MI 9 owner here wondering about a few things in regards to rooting the phone (without TWRP). My main concerns are, 1) is there still a waiting period to unlock the bootloader? 2) Does rooting cause some system apps to not work properly? For example in my previous phone the cost for rooting (or unlocking bootloader) was terrible camera quality.. And 3) can I still get regular system updates without having to manually flash a full rom?
Oh and a bonus question! Has anyone tried if there's any way to use Xperia keyboard on this phone? It's the only keyboard that hasn't made me want to go toss my phones in the river...

Not sure if there's any way to root mi9 without twrp, someone will hopefully correct if i'm wrong, but i've not heard of one - you need the advanced options twrp offers over stock recovery to flash magisk, but i may be wrong. Perhaps you may be able to extract ur boot img or something and inject magisk, so it's pre-rooted, but i don't know how to do that, sorry. Most peoples banking apps work in most places using magisk hide but i've read that some banks/regions require further work. Not heard of any reports of camera degradation tho.
Why don't you wanna flash twrp? Yes, there's a waiting period to unlock bl. Not sure about the keyboard, don't have it

reg66 said:
Not sure if there's any way to root mi9 without twrp, someone will hopefully correct if i'm wrong, but i've not heard of one - you need the advanced options twrp offers over stock recovery to flash magisk, but i may be wrong. Perhaps you may be able to extract ur boot img or something and inject magisk, so it's pre-rooted, but i don't know how to do that, sorry. Most peoples banking apps work in most places using magisk hide but i've read that some banks/regions require further work. Not heard of any reports of camera degradation tho.
Why don't you wanna flash twrp? Yes, there's a waiting period to unlock bl. Not sure about the keyboard, don't have it
Click to expand...
Click to collapse
Well this was at the top of the Mi 9 Guides, News & Discussion page here: [TUTO] Complete tutorial to root MI9 without TWRP (Keeps intact encryption of the MI9. Encryption is always good and I haven't needed TWRP much before so I figured that's the best option for me. Oh and no, there's no wait time anymore. Just downloaded the unlocker and it gave me the green light to go ahead. Bought the phone yesterday..

Kuunkulta said:
Well this was at the top of the Mi 9 Guides, News & Discussion page here: [TUTO] Complete tutorial to root MI9 without TWRP (Keeps intact encryption of the MI9. Encryption is always good and I haven't needed TWRP much before so I figured that's the best option for me. How do I find out how long of a wait I still have ahead?
Click to expand...
Click to collapse
Ah OK, hadn't seen that thread. Good luck with it all. Download Mi unlock tool and it'll tell you how long to wait, maybe 720 hours.. There is a thread for instant unlock, but it's only worked on a few cases

You definitely want to flash Magisk via TWRP, because you will need a few modules there that really improve the phone, are absolute must haves.

omgomg said:
You definitely want to flash Magisk via TWRP, because you will need a few modules there that really improve the phone, are absolute must haves.
Click to expand...
Click to collapse
Such as?

reg66 said:
Such as?
Click to expand...
Click to collapse
Such as bump audio bitrate when recording up to 6ch, 960kbs; Youtube Vanced, Netflix (yes, if you root it, you will need magiskhide or no Netflix), liboemcrypto disabler; Cloudflare DNS; Viper4Android (this one quite optional, but makes such a difference).
---------- Post added at 03:53 AM ---------- Previous post was at 03:52 AM ----------
Kuunkulta said:
Well this was at the top of the Mi 9 Guides, News & Discussion page here: [TUTO] Complete tutorial to root MI9 without TWRP (Keeps intact encryption of the MI9. Encryption is always good and I haven't needed TWRP much before so I figured that's the best option for me. Oh and no, there's no wait time anymore. Just downloaded the unlocker and it gave me the green light to go ahead. Bought the phone yesterday..
Click to expand...
Click to collapse
I don't know what's your doubt, but mauronofrio's TWRP keeps the encryption per default.

omgomg said:
Such as bump audio bitrate when recording up to 6ch, 960kbs; Youtube Vanced, Netflix (yes, if you root it, you will need magiskhide or no Netflix), liboemcrypto disabler; Cloudflare DNS; Viper4Android (this one quite optional, but makes such a difference).
---------- Post added at 03:53 AM ---------- Previous post was at 03:52 AM ----------
I don't know what's your doubt, but mauronofrio's TWRP keeps the encryption per default.
Click to expand...
Click to collapse
Really? If the encryption is preserved with it, I don't see any reason not to go TWRP. Can't believe I've missed that, I try to do my research before posting Thanks for the tip!

Yeah, encryption is on, I've never had my phone with a decrypted ROM. Using mauronofrio's TWRP -35 currently.

Question I have ne2217. Help root and Global. Please!!!!

These threads have to many things going on, and now I am thoroughly confused. I just want to go to global from stock T-Mobile. I have downloaded so many things and I don't know what to use or not use. I have network unlocked and my bootloader is unlocked. I can enter fastboot and fastbootd.

Loustsoul said:
These threads have to many things going on, and now I am thoroughly confused. I just want to go to global from stock T-Mobile. I have downloaded so many things and I don't know what to use or not use. I have network unlocked and my bootloader is unlocked. I can enter fastboot and fastbootd.
Click to expand...
Click to collapse
There is no way to do it as of now. No one bothered making a conversion from T-Mobile to global with the 10 as there is no reliable MSM tool in case something were to go wrong in the conversion process. The most you can do on the T-Mobile version is unlock and root right now. I personally would love to be on global instead of T-Mobile firmware, but I doubt it will happen with the 10 Pro (although there is work being done on getting a useable MSM tool currently, so who knows).

jeffsga88 said:
There is no way to do it as of now. No one bothered making a conversion from T-Mobile to global with the 10 as there is no reliable MSM tool in case something were to go wrong in the conversion process. The most you can do on the T-Mobile version is unlock and root right now. I personally would love to be on global instead of T-Mobile firmware, but I doubt it will happen with the 10 Pro (although there is work being done on getting a useable MSM tool currently, so who knows).
Click to expand...
Click to collapse
All that'd take would be extracting your boot.img and flashing? Any issues with magisk?

Grin59 said:
All that'd take would be extracting your boot.img and flashing? Any issues with magisk?
Click to expand...
Click to collapse
For root? Just use the global patched boot.img and boot into OS, go to Magisk and perform a direct install. No issues at all with root on T-Mobile firmware. I've been rooted ever since they allowed us to unlock the bootloader and get our tokens.

Removed

EtherealRemnant said:
Really all you should need to do to convert to global is unlock the bootloader, take the NA downgrade package, and flash it with Fastboot Enhance. Make sure you go to the partitions screen and search for cow and delete every one of them so there is room for the image and if you get any other errors, don't continue. Once the flash is successful (the bar will seem to stop, just let it sit for a bit and it will continue), choose English on the phone screen and go through the menus to find where to wipe the phone and then reboot.
There is a risk of a brick if something goes wrong so without the MSM Tool, this is at your own risk, but Fastboot Enhance doesn't tend to brick phones like fastboot scripts do as long as you stop if it gives you an error.
Here is the NA downgrade package.
https://oxygenos.oneplus.net/2370_sign_NE2215_11_A_OTA_0130_all_bb1e47_10100001.zip
Click to expand...
Click to collapse
Yeah, technically should work. Unfortunately the risk is too high without having the MSM in case something goes wrong. Especially if it's your daily phone, like it is mine. But if anyone wants to give it a go, let us know how it goes, just know it could brick your phone and there's no current way to restore it without sending it to OnePlus or paying a scam artist to restore it.

Removed

Can I get my boot.img off of my phone or do I need to download it? Also the 10 pro is not listed in the software on the oneplus website. Where can I get the official stuff I need? Im happy with just root for now, I just want to use Magisk and do the updates......

EtherealRemnant said:
Fastboot Enhance really shouldn't brick. It's flashing the official downgrade package so unless OnePlus changed the hardware between the two significantly (which seems unlikely both because they haven't before other than minor changes like removing dual SIM and adding mmWave to the 9 Pro as well as the added cost of doing so), it should work fine. I made a tutorial for the OnePlus 9 using Fastboot Enhance to convert regions and nobody has reported a brick yet and this is after seeing 30+ bricks from people using fastboot scripts that prompted me to make the guide. Bricks with FBE happen if people ignore warnings about cow partitions or missing partitions and flash anyway. Like it doesn't even reboot the device after the flash is done so if the flash gets cut off in the middle, you just would need to flash the zip again before rebooting. Since all the flashing takes place in fastbootd from the start, it's possible to recover unlike regular flashing where it starts in fastboot and finishes in fastbootd so you're hosed if something goes wrong and you can't get back to fastboot.
I get it though, I wouldn't want to risk my device either. And I made sure to point out the brick risk, even if it's small, because I would never want to take that choice away from someone.
Click to expand...
Click to collapse
Im willing to try but I am too unsure of what to use as far as the correct boot and rom.... You seem to have way more knowledge than I and I would greatly appreciate your help.

Removed

EtherealRemnant said:
Fastboot Enhance really shouldn't brick. It's flashing the official downgrade package so unless OnePlus changed the hardware between the two significantly (which seems unlikely both because they haven't before other than minor changes like removing dual SIM and adding mmWave to the 9 Pro as well as the added cost of doing so), it should work fine. I made a tutorial for the OnePlus 9 using Fastboot Enhance to convert regions and nobody has reported a brick yet and this is after seeing 30+ bricks from people using fastboot scripts that prompted me to make the guide. Bricks with FBE happen if people ignore warnings about cow partitions or missing partitions and flash anyway. Like it doesn't even reboot the device after the flash is done so if the flash gets cut off in the middle, you just would need to flash the zip again before rebooting. Since all the flashing takes place in fastbootd from the start, it's possible to recover unlike regular flashing where it starts in fastboot and finishes in fastbootd so you're hosed if something goes wrong and you can't get back to fastboot.
I get it though, I wouldn't want to risk my device either. And I made sure to point out the brick risk, even if it's small, because I would never want to take that choice away from someone.
Click to expand...
Click to collapse
The only downside I could see then it's that we don't even have the full T-Mobile firmware to flash back to in case it starts to flash global but then failed. I'm tempted to take the plunge and try (would be nice to be on Android 13 now instead of waiting months for T-Mobile to get the update) but just don't want to end up bricking with no way to recover. Also, in the past I know people were using the MSM to convert to global or EU, does using the global downgrade script alone work for converting? I might take a look at your guide for the 9 series and try with the 10 pro. I guess I can always send it in if it does brick, still have my 9 pro I can use in case something goes wrong.

Removed

EtherealRemnant said:
It is a legitimate concern that you can't get back to T-Mobile firmware if something goes wrong and that is definitely something to think about.
I can tell you that the downgrade package is as close as you can get to the MSM Tool in terms of a restore without an MSM. I have used the downgrade packages to convert between regions on my 9 and never had any issues except for when I used the India MSM Tool for the 9 Pro on my 9 and kept losing touchscreen in OOS12. That was only fixed with an MSM Tool modded to get me back on regular global 9 firmware.
Click to expand...
Click to collapse
Well I'm taking the plunge so I'll update after if it's successful or not. Was able to delete all the COW partitions and start the flash no issue, so just have to wait for it to finish.

Removed

I will say this is my 2nd 10 pro because I did this exact method being described and it flashed rebooted all that but when trying to open any app I was greeted with a message that said.. "this app has been disabled due to security".

tman23 said:
I will say this is my 2nd 10 pro because I did this exact method being described and it flashed rebooted all that but when trying to open any app I was greeted with a message that said.. "this app has been disabled due to security".
Click to expand...
Click to collapse
Yeah, don't think it's going to work. Can't fully get out of the setup screen (or if you do it just stays at black screen only able to pull down quick settings and not enter options or anything). Wiped after flashing and won't work. I guess I could try using Fastboot Enhance to flash some of the global update zips and see if that does anything.

From what I've seen and read, switching regions on this phone is quite easy. You just need to use the full downgrade zip of that region and flash it basically. No messing around with FBE. NE2210/3/5/7 all share the same hardware, the full downgrade zips are actually interchangeable from what I've read/seen. There's only been one full zip for NE2217 released, IIRC, so the process to go back would involve a lot of upgrading incrementally. EDIT: I was wrong. There is no true full T-Mobile NE2217 ZiP available.. really sad.
But to go to/from NE2213 to/from NE2215, just take the downgrade zip, with a fully unlocked bootloader, and local update it.
Someone can correct if I'm wrong, but this seems to be the method most people have been using with success. That being said, as said above, root is very easily achievable by just BOOTing a patched global boot.img if you just want to root and maintain your original software.

Prant said:
From what I've seen and read, switching regions on this phone is quite easy. You just need to use the full downgrade zip of that region and flash it basically. No messing around with FBE. NE2210/3/5/7 all share the same hardware, the full downgrade zips are actually interchangeable from what I've read/seen. There's only been one full zip for NE2217 released, IIRC, so the process to go back would involve a lot of upgrading incrementally. But to go to/from NE2213 to/from NE2215, just take the downgrade zip, with a fully unlocked bootloader, and local update it.
Someone can correct if I'm wrong, but this seems to be the method most people have been using with success.
Click to expand...
Click to collapse
I haven't really heard of anyone converting the 10 due to lack of MSM. Also, haven't seen any full zips for the 2217 (T-Mobile version), so if you have a link to it that would be very useful. Also on 2217, you can't flash from in system as it's disabled in firmware (unless the separate apk works).

Stalk the forums enough, I think I've read every post here since I got the device back in March. There's a handful of people here successfully converted regions without any extra work. I believe there are actually 2 now for 2217. Here and here.
EDIT: As mentioned later in the thread even these are not full images for NE2217.

Prant said:
Stalk the forums enough, I think I've read every post here since I got the device back in March. There's a handful of people here successfully converted regions without any extra work. I believe there are actually 2 now for 2217. Here and here.
Click to expand...
Click to collapse
Thank you, not sure how I missed those. If my attempt to restore the device doesn't work I'll try restoring it by flashing T-Mobile firmware again.