AOSP ROM Questions (XT1072) - Moto G 2014 LTE Q&A, Help & Troubleshooting

Hello All,
I've just flashed the AOSP ROM for THEA XT1072 and I'm very happy with the results, it's exactly the return to stock I was looking for. However, I have a few questions I hope somebody can kindly answer:
1) Is it possible to re-lock the bootloader once an unofficial ROM has been installed? My device is telling me I need an officially signed ROM and refusing to relock when I do "mfastboot oem lock".
2) What's the update process for installing later builds of the AOSP ROM? Is it just a case of checking back here and re-flashing the whole new image as and when it is released? Or is there an OTA update alternative?
3) Is the current AOSP build 20150828 inclusive of the various security fixes that Google rolled out recently (Stagefright etc.)? I know they were released to AOSP source code but that presumably doesn't guarantee they are in the current THEA 20150828 AOSP build yet.
Thanks
sharkyblunt

sharkyblunt said:
Hello All,
I've just flashed the AOSP ROM for THEA XT1072 and I'm very happy with the results, it's exactly the return to stock I was looking for. However, I have a few questions I hope somebody can kindly answer:
1) Is it possible to re-lock the bootloader once an unofficial ROM has been installed? My device is telling me I need an officially signed ROM and refusing to relock when I do "mfastboot oem lock".
2) What's the update process for installing later builds of the AOSP ROM? Is it just a case of checking back here and re-flashing the whole new image as and when it is released? Or is there an OTA update alternative?
3) Is the current AOSP build 20150828 inclusive of the various security fixes that Google rolled out recently (Stagefright etc.)? I know they were released to AOSP source code but that presumably doesn't guarantee they are in the current THEA 20150828 AOSP build yet.
Thanks
sharkyblunt
Click to expand...
Click to collapse
1. No.
2. Just flash rom without any wipes as there's no OTA functionality.
3. Yes.

Thanks Luk. Great work on this ROM. It flies compared to the stock 5.0.2 and no issues yet.

Only one issue so far, after 24 hours of using it. I'm getting a battery drain whereby Miscellaneous is by far the biggest culprit (currently at 22% since taking it off charge this morning). It was the same yesterday too, and I rebooted it last night just in case it was a hangover from the original flashing, but it's still draining faster than stock 5.0.2 did.

The AOSP-5.1.1-20150905 build is perfect (once I'd erased the modemst1 & modemst2 to get GPS working). No issues whatsoever from me. Great work.
By the way, I'm commenting here as I've not done enough posts to participate in the developers sub-forum.

Related

[Q] SYSTEM UI issues; How come I cannot install any "ghost" rom?

PRIMARY QUESTION: I cannot seem to install any "ghost" KitKat or Lollipop ROM on my XT1058. Can anyone please help shed some light on this? I've spent around a combined 12+ hours searching, researching, and tinkering trying to figure this out, but no success. I typically receive a "com.android.systemui" error message or "Unfortunately, System UI has stopped" message. After I acknowledge the message, it pops up again in a second or two. I have to force a shutdown of the phone and recover via TWRP. I've detailed my history and attempts below.
On the CM website, it says something about how "ghost" is a unified OS for every Moto X, except AT&T, since it's not unlockable. With Sunshine, shouldn't I be able to install the "ghost" ROM? Or does it not matter? I hope this isn't a case of, "even though you have an unlocked bootloader, the 'ghost' ROM isn't intended for your version of the phone." If that's true, it looks like all development on the XT1058 has pretty much stopped.
Many thanks, XDA Community, for helping me understand all this!
Secondary Questions:
I recently tried using the feature, "fixing permission" in TWRP thinking it might help with the "ghost" installations. I started getting bootloops when trying to restore to previous ROMs. The only restore that worked was my true original stock backup; the other restore attempts on SlimKat and other stock instances failed. That worries me. While I have successfully restored my phone, does anyone know if I may have screwed up my phone for the long-term?
(Answered by KidJoe; thank you!) Since I unlocked my bootloader at 4.2.2, can I freely upgrade and downgrade stock OSs? i.e., Can I install AT&T's stock 4.4.4 and then downgrade to 4.4.2?
(Answered by KidJoe; thank you!) Why do so many people seem to care to downgrade their stock OS? While I'm sure some may not be happy with some changes that come with upgrades, what could possibly be so "upsetting" that people need to downgrade?
HISTORY
Phone: AT&T Moto X XT1058, non-developer edition
Android: 4.2.2 | No attempt has been made to upgrade the OS beyond 4.2.2
Used Sunshine to unlock the bootloader while still on 4.2.2
Recovery: Installed TWRP v2.8.1.0, and I use TWRP to backup and install old and new ROMs (I think it's version 2.8.3... I never downloaded a version 2.8.1, but that's what the screen says. I'm wondering if the authors just forgot to update the version number in the program.)
Successful ROM installs:
SlimKat build 7 Official, msm8960dt
Cyanogenmod 11 Snapshot M5 msm8960dt (2014-04-05)
Failed ROM installs:
Cyanogenmod 11 Snapshot M12 ghost (2014-11-15)
Cyanogenmod 11 Nightly ghost (2014-12-19)
LiquidSmooth KitKat v3.2 Nightly ghost (2014-10-31)
LiquidSmooth Lollipop v4.0 Nightly ghost (2014-12-20)
Other Notes:
GApps were always installed when available. I also tried not installing them.
cxwong1 said:
Many thanks, XDA Community, for helping me understand all this!
Secondary Questions:
Since I unlocked my bootloader at 4.2.2, can I freely upgrade and downgrade stock OSs? i.e., Can I install AT&T's stock 4.4.4 and then downgrade to 4.4.2?
Why do so many people seem to care to downgrade their stock OS? While I'm sure some may not be happy with some changes that come with upgrades, what could possibly be so "upsetting" that people need to downgrade?
Click to expand...
Click to collapse
I will answer these two....
1. NO you can not. Once you have 4.4.2, 4.4.3 or 4.4.4 on your phone, do NOT attempt to downgrade, even if you have an unlocked bootloader... For more details see what I typed here -> http://forum.xda-developers.com/moto-x/general/4-4-4-downgrade-possibility-t2971847/post57563419 along with the other discussions in that SHORT thread.
2. The older root and write protection disable processes for a Moto X with a locked bootloader (like ATT and Verizon) rely on taking advantage of vulnerabilities in the 4.2.2 w/Camera update rom version, or the 4.4 rom. These processes walk you through downgrading your ROM to 4.2.2 w/Camera update and following a set of steps to upgrade which will keep root and disable write protection. NOTE: It was safe to downgrade from 4.4. to 4.2.2 w/Camera update when following the SlapMyMoto/MotoWpNoMo processes. But that was the only time it was safe!!!!
KidJoe, thank you much!
Does anyone else have any idea about my "systemui" issue?
cxwong1 said:
KidJoe, thank you much!
Does anyone else have any idea about my "systemui" issue?
Click to expand...
Click to collapse
Just got a Moto X 1st gen replacement from Motorola and getting same problem after unlocking/rooting. Have you found a fix for this? Or does anyone know how to fix? Spent all day working on this and its driving me nuts.
syckman said:
Just got a Moto X 1st gen replacement from Motorola and getting same problem after unlocking/rooting. Have you found a fix for this? Or does anyone know how to fix? Spent all day working on this and its driving me nuts.
Click to expand...
Click to collapse
Hey! Nope, I haven't found the answer, unfortunately. I haven't really tried to upgrade my OS since.
cxwong1 said:
PRIMARY QUESTION: I cannot seem to install any "ghost" KitKat or Lollipop ROM on my XT1058. Can anyone please help shed some light on this?
Click to expand...
Click to collapse
I bit the bullet yesterday and paid for the Sunshine bootloader unlock. After replacing the stock bootloader with TWRP and making a backup, I started looking into putting CyanogenMod onto it, as I had just updated a Galaxy Tab 2 7.0 to KitKat (via CyanogenMod 11) last week and it wasn't right that my phone had an older Android build than my tablet. I ran into conflicting information here and elsewhere, but the bottom line:
I have CyanogenMod 11 running on my AT&T Moto X.
More specifically, it's this zipball (remove spaces in next line to bypass the forum's lame link blocking):
https :// download.cyanogenmod.org / get / jenkins / 90775 / cm-11-20141115-SNAPSHOT-M12-ghost.zip
I also tried the latest 12.1 nightly, but while it appears to boot up, it reboots almost as soon as you try to set it up.
One thing that seems to help: before loading any ROM (whether stock, CyanogenMod, or whatever), wipe the flash. I have the ROM and Google Apps files on a flashstick that gets connected through an OTG cable, so I just tell TWRP to wipe everything but OTG storage, restore the ROM, let it boot up, then go back to TWRP to install the Google apps.
(Good thing I had the stock ROM backed up...had to revert to it this morning to back up aCar and Stocard data so I could bring them into CM.)
Starting configuration for my phone: AT&T XT1058, stock 4.4 firmware, rooted with the usual means for doing so, bootloader locked until Sunshine worked its magic.

OnePlus 3T Update or flash a ROM?

Hi! So, for now I'm running OOS 3.5.4 because I hated the 4.0.1 (I downgraded from it). So, now I don't know if updating to 4.1.1 or getting a ROM. I heard a lot of discordant opinions about the new update of OOS and myself didn't like the first nougat update. If I'll flash ROM, what should I flash(without bugs and with a good camera quality, because seems that all the roms have ****ty camera quality)?
Just my take: Asking for advice about the 4.1.1 update vs. custom ROM (and for that matter which custom ROM) is a matter of personal preference. As you've said yourself, opinions on the update are discordant (as will be true for any update). Just because someone gives your a particular response one way or the other, doesn't mean it will be the right answer for you. The only way to conclusively answer the question for yourself, is to try out the update and/or ROMs.
I would generally recommend updating firmware/modem in any case, whether you decide on the official update or a custom ROM. So it may make sense just to do the update (which will also update firmware and modem) then see if you like it. If not, try a custom ROM.
Alternately, even if you opt to go right to a custom ROM (after unlocking bootloader and flashing TWRP), I'd suggest at least flashing one of the updated firmware/modem zips posted in the 3T Guides, News & Discussion section.
redpoint73 said:
Just my take: Asking for advice about the 4.1.1 update vs. custom ROM (and for that matter which custom ROM) is a matter of personal preference. As you've said yourself, opinions on the update are discordant (as will be true for any update). Just because someone gives your a particular response one way or the other, doesn't mean it will be the right answer for you. The only way to conclusively answer the question for yourself, is to try out the update and/or ROMs.
I would generally recommend updating firmware/modem in any case, whether you decide on the official update or a custom ROM. So it may make sense just to do the update (which will also update firmware and modem) then see if you like it. If not, try a custom ROM.
Alternately, even if you opt to go right to a custom ROM (after unlocking bootloader and flashing TWRP), I'd suggest at least flashing one of the updated firmware/modem zips posted in the 3T Guides, News & Discussion section.
Click to expand...
Click to collapse
Thank you. I will probably update then, and if I won't like it I'll go to a custom ROM. Could you suggest me any good/stable ROM out there (especially without bugs and with a good camera quality)? Thanks
_HaZaRD_ said:
Could you suggest me any good/stable ROM out there (especially without bugs and with a good camera quality)?
Click to expand...
Click to collapse
As I already mentioned, what I said about update vs. custom ROM, will also apply to asking for recommendations about a particular custom ROM. It depends on your personal needs and preferences. You have to make the decision yourself.
Further, I'm still on stock 7.1.1, rooted; and haven't tried any custom ROMs on this device yet. So I have no custom ROM recommendations.
redpoint73 said:
As I already mentioned, what I said about update vs. custom ROM, will also apply to asking for recommendations about a particular custom ROM. It depends on your personal needs and preferences. You have to make the decision yourself.
Further, I'm still on stock 7.1.1, rooted; and haven't tried any custom ROMs on this device yet. So I have no custom ROM recommendations.
Click to expand...
Click to collapse
Ok
I updated from 4.0.3 to beta 4 via local, but now I want to go back because of the battery drain problem. I tried several times via adb sideload to flash the zip but I keep getting the same error <cannot read 4.0.4.zip> over and over again. Even after installing the drivers, I got a little yellow exclamation triangle near the driver in device manager. Honestly I'm starting to give up, I think I wiped my phone more than 5 times in order to flash via sideload, only to get the same error continuously. as far as I know, I cannot go back to 4.0.3 via local from beta 4 right?
Please help...

Downgrade 4.1.3 to 4.1.1 (and beyond)

Hi all,
I am having issues with my Bluetooth and GSM. I am considering trying to downgrade from OOS 4.1.3 to 4.1.1. I am completely stock, not rooted and don't even have TWRP.
Would appreciate some clarification to the following questions:
1) Can I downgrade by just flashing the official full 4.1.1 zip found in OP website?
2) Should I only flash the modem zip? And if so, can I use 4.1.1 modem while having 4.1.3 installed?
3) Since 4.1.1 already has nougat 7.1.1, is 1) also safe for further downgrades, for example, directly to 4.0.4?
Thanks.
Best regards,
Oldiamond
If your bootloader is locked, you can't downgrade (unless you exploit the security vulnerability from a few weeks back).
If your bootloader is unlocked, use TWRP or fastboot to clean flash whatever version of OOS you want.
You should consider flashing the latest open beta release, I think it's already fixed over there plus there are some Extra goodies and its stable as ****
Anova's Origin said:
If your bootloader is locked, you can't downgrade (unless you exploit the security vulnerability from a few weeks back).
If your bootloader is unlocked, use TWRP or fastboot to clean flash whatever version of OOS you want.
Click to expand...
Click to collapse
Pharrax said:
You should consider flashing the latest open beta release, I think it's already fixed over there plus there are some Extra goodies and its stable as ****
Click to expand...
Click to collapse
Thanks to both. I am this close to send it back to RMA, as I did not install anything other than 4.1.3, and didn't even unroot it. I don't know... perhaps by sending it back without ever installing TWRP or unlocking anything would provide more feedback to the manufacturer, other than saying "damn guy, started fiddling with the phone and ROMs, and here's the result".
Regarding the beta, I initially considered avoiding it because i read in the forums about issues such as sometimes alarms not ringing. I figure that my boss wouldn't like that
Going back from BETA to regular version also requires TWRP?
Best regards,
Old
oldiamond said:
Thanks to both. I am this close to send it back to RMA, as I did not install anything other than 4.1.3, and didn't even unroot it. I don't know... perhaps by sending it back without ever installing TWRP or unlocking anything would provide more feedback to the manufacturer, other than saying "damn guy, started fiddling with the phone and ROMs, and here's the result".
Regarding the beta, I initially considered avoiding it because i read in the forums about issues such as sometimes alarms not ringing. I figure that my boss wouldn't like that
Going back from BETA to regular version also requires TWRP?
Best regards,
Old
Click to expand...
Click to collapse
Alarm issues were fixed, also it never happened to me I and I've been on beta a long time i think on the official page there are the steps to switch between stable and beta. I don't think it requires twrp but don't take my word for it.

[ROM][8.1.0][OFFICIAL] AOSiP {T-mobile/Sprint}

Aosip for Motorola Z2 Force
What is this?
AOSiP is a quality custom ROM based purely on GOOGLE AOSP source since 6.0 release. Twisted with the latest features and blended with stability. We strive for perfection and it shows.
Obligatory Warning: This guide and ROM assumes you know the fundamentals of fastboot, flashing TWRP, and running a flash all. Your warranty is voided because of the unlocked bootloader. This is a Third Party ROM. Things may not work as expected compared to stock (for better or for worse).
Warning 2: If you can't do fastboot commands, do a flash all, root your device or flash TWRP/ROM, please do not ask for help here. If you cannot flash all back to stock, please stay stock for everyone's sake.
Warning 3: if you don't flash the firmware so you are on Oreo on both slots, when you boot after flashing, you'll be on Nougat firmware and have a brick. Try a flash all as that's your only hope on recovering your phone.
How to install
1. Download the latest ROM from here.
2. Prepare your phone for AOSP style ROMs. (download one of the firmwares depending on your model)
Flash the firmware with the .bat file. (See links below or on Post #2)
3. Boot to TWRP
4. Flash TWRP to boot image (with the zip from their website.) Reboot to Newly flashed recovery.
5. Erase oem, data, and system
6. Flash rom like you would any aosp rom, in twrp.
7. Reboot to bootloader
8. run the command "fastboot -w" (this will erase EVERYTHING from your phone, even internal SD, but is needed to have these ROMs work)
9. reboot.
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Volte (T-Mobile)
Change quick charge
Fingerprint reader
NFC
Lights
Sound / vibration
Some motomods (soundboost mod doesnt work)
Team Illusion:
Josh Fox (xlxfoxxlx)
Akhil Narang
Sri Harsha (@srisurya95)
Shreesha Murthy
Brett Montague
Known issues
1. WiFi Calling hit and miss
2. Cannot flash Gapps (included temporarily)
3. some Audio recording apps will not have audio recording work (phone functions fine)
4. if you don't fastboot -w, you will not boot.
5. if you don't flash the firmware your bootloader might relock itself and be stuck on Nougat.
6. SElinux is passive (meaning CTS check will always fail until further notice.)
Downloads:
official link(aosiprom.com)
​Thanks to everyone at @aosip @mosimchah @moto999999 and @codeworkx for their amazing work
Android OS version: 8.1.0
Security patch level: April 2018
Build author: @Infect_Ed
Source code: https://github.com/AOSiP-Devices/device_motorola_nash - AOSiP source.
https://github.com/InvictrixRom-devices/kernel_motorola_nash - kernel
https://github.com/TheMuppets/proprietary_vendor_motorola - vendor blobs
Contributors
@Infect_Ed @invisiblek @npjohnson @erfanoabdi @joemossjr @jbats @nathanchance
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.4.x
Phone Firmware Required: 8.0
T-Mobile
Sprint
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2018-03-28
Created 2018-03-28
Last Updated 2018-04-10
Note: I did not build this. If you want to give thanks for this ROM build, thank @Infect_Ed for building AOSiP, I am just maintaining the support thread for XDA.
Firmware files needed!
T-Mobile:27.1
Sprint: Found em!
Sources Post:
https://github.com/AOSiP-Devices/device_motorola_nash - AOSiP source.
https://github.com/InvictrixRom-devices/kernel_motorola_nash - kernel
https://github.com/TheMuppets/proprietary_vendor_motorola - vendor blobs
Bug reports:
If you don't flash the firmware and your other slot is nougat, after flashing the ROM, you'll brick. (Custom ROM with a locked nougat slot.) Your only hope is attempting an official flash all and try again after flashing the firmware zip in the posts above.
Fair warning and off-topic: I am okay with some off topic questions. If you have a question, please use the search function. If I have addressed the question before, I will not answer and advise to find it in the thread. I will report the post for a mod to delete along with my response to keep the thread tidy. It seems some users think this ROM has international support. It doesn't and won't unless someone with another variant or an unlocked T-Mobile/Sprint model tests, confirms and debugs for that international carrier. Please keep in mind of what I said below regarding this. I posted this on page 20 or so and copying here for better visibility.
Your SIM is locked. You are trying to run a phone off it's intended network. Please don't post those problems here. It isn't ROM related. Like the thread states. It works for T-Mobile and Sprint only on their respective models on their locked networks. Any other tom foolery isn't supported and must be kept out of the thread. After this it will be considered off topic.
Edit: if you have Sprint or T-Mobile service and run into issues with using your (albeit, expensive) international roaming plan, I will assist with that if it works on stock but not AOSP. If you don't have a sprint or T-Mobile sim, I cannot help. Almost all devs on this device won't be able to help. "Almost" all of us are on US carriers.
Click to expand...
Click to collapse
Images posted here
@Uzephi is your device on sprint? Data works but LTE does not? Does the Moto Mods support Hot Swapping? This is great progress and can't wait to see more on this phone.
xDABZx said:
@Uzephi is your device on sprint? Data works but LTE does not? Does the Moto Mods support Hot Swapping? This is great progress and can't wait to see more on this phone.
Click to expand...
Click to collapse
Motomods work with kernel in ROM (hot swapping should as well iirc, I don't use the mods that often where my projector is outdated) LTE doesn't work on Sprint, but 3G and 1xTT works fine.
@Uzephi if we were to flash your kernel, we would lose motomods support?
cervantesjc said:
@Uzephi if we were to flash your kernel, we would lose motomods support?
Click to expand...
Click to collapse
For now, yes. Still trying to get it work. Clang is being a PITA on my build box, having to go to Linaro which can't build the Motorola Greybus driver correctly.
Thanks sir, I appreciate what you've done for the community, finally can go back to my moto from a GS8+
I'm sorry if this is a dumb question but...
Ive never had to install different firmware before on a ROM. If I install this, will it change the process of installing a different ROM in the future?
Thank you.
Sprint varient if it matters by the way.
Edit: I'm sorry for this but is there a way to do this without the .bat file? currently working on OSX
wcain89 said:
I'm sorry if this is a dumb question but...
Ive never had to install different firmware before on a ROM. If I install this, will it change the process of installing a different ROM in the future?
Thank you.
Sprint varient if it matters by the way.
Edit: I'm sorry for this but is there a way to do this without the .bat file? currently working on OSX
Click to expand...
Click to collapse
Open the bat file in a text editor and run each of those commands one by one.
This I'd a dual boot device. Your other slot has the older Nougat bootloader. That firmware flashed the current Oreo firmware to both slots. If you don't do that, and you flash one of these ROMs, you'll reboot to your nougat slot, locked and pretty much screwed without a flash all and luck of being able to flash OEM images in oem mode.
Edit: you won't need to flash this any consecutive times until there is another big firmware update like nougat to Oreo was.
Uzephi said:
Open the bat file in a text editor and run each of those commands one by one.
This I'd a dual boot device. Your other slot has the older Nougat bootloader. That firmware flashed the current Oreo firmware to both slots. If you don't do that, and you flash one of these ROMs, you'll reboot to your nougat slot, locked and pretty much screwed without a flash all and luck of being able to flash OEM images in oem mode.
Edit: you won't need to flash this any consecutive times until there is another big firmware update like nougat to Oreo was.
Click to expand...
Click to collapse
Thank you for the quick reply. I've installed the firmware, but now when I boot to TWRP and try to install the ROM, it instantly fails with ERROR:1. Tried redownloading with a different browser but got the same result. I feel like I'm missing something obvious.
wcain89 said:
Thank you for the quick reply. I've installed the firmware, but now when I boot to TWRP and try to install the ROM, it instantly fails with ERROR:1. Tried redownloading with a different browser but got the same result. I feel like I'm missing something obvious.
Click to expand...
Click to collapse
Flash twrp zip to your phone, reboot to your phone's newly flashed twrp recovery and flash the rom. If I remember right,you need to wipe oem and system before flashing the ROM as well. I'll add that shortly.
Up and running! Thank you!! Still looking around but I do see a built in updater. Will this function 100%? By that I mean, when the Sprint LTE issue is resolved and whatever else is coming will be handled by the updater?
Thanks again very excited to play around.
wcain89 said:
Up and running! Thank you!! Still looking around but I do see a built in updater. Will this function 100%? By that I mean, when the Sprint LTE issue is resolved and whatever else is coming will be handled by the updater?
Thanks again very excited to play around.
Click to expand...
Click to collapse
Yes, since it's official, it checks the link in OP for any new updates.
For anyone using the ROM, are you seeing notification dots, I tried to get them to work, but they're not working for me.
cervantesjc said:
For anyone using the ROM, are you seeing notification dots, I tried to get them to work, but they're not working for me.
Click to expand...
Click to collapse
Working fine for me thru Evie Launcher. Soundboost mod is broken though. My SoundBoost is recognized and the notification says the mod is attached, but the volume steps are reduced to on/off and no sound comes out.
Edited to reflect that only the sound boost mod isn't working AFAIK.
wcain89 said:
Working fine for me thru Evie Launcher. Mods are broken though. My SoundBoost is recognized and the notification says the mod is attached, but the volume steps are reduced to on/off and no sound comes out.
Click to expand...
Click to collapse
Oh, @npjohnson and @invisiblek don't have the sound mod, so they can't get it to work. All of us in the development discord are trying to mail one out, they can't guarantee when it would get fixed.
Edit: added disclaimer to OP. We can only guarantee what we have works. Like when I do my kernel, the only mod I have is the free projector, so that's the only mod I can guarantee works when I do get it working.
I have an extra soundboost I could mail to someone.

Good low effort way of keeping a rooted stock Mi 9T Pro up to date?

Hello,
I bought a 9T Pro in Europe for my wife and until it arrives I'm trying to research and come up with a low effort process of keeping the stock ROM up to date and rooted for her. I'm confident in manually installing and updating custom ROMs, rooting and dealing with custom ROM issues, but she is not. Therefore I thought the best thing is to use the stock ROM - not custom - since it may be the most stable experience and for me to update and re-root it for her regularly. root is mandatory because we need AdAway and other things. As I understand it, as soon as we unlock and root the phone, OTA updates for stock are impossible and maybe even dangerous. I've tried researching here but am bit struggling to come up with the right infos and I'd be glad for any advice.
Of course I have seen the great thread about unlocking, rooting, etc, but It seems that that deals with non-standard Chinese firmware pre-installed, which is probably not the case on our device. Since it's bought in Europe, I think it will probably come with some Global or EU ROM. And it doesn't answer some of my other questions.
So far my idea is roughly like this:
Phone arrives
Immediately update it via built-in OTA to latest official stock ROM
Unlock, install TWRP, root with Magisk
Use the phone
Whenever a new stock ROM comes out, download it from XDA
Flash new ROM in TWRP and root again with Magisk
Repeat 4-6 as new stock ROM versions are released
Of course regularly backup with Titanium Backup and TWRP
First of all, would this work or did I misunderstand something fundamental?
How does low level firmware / modem update come into play? Would that be included in the stock ROM packages I find here? Or do I need to manually update that separately? How do I know when I have to, since there is no custom ROM maintainer telling me when it's needed?
Is there an easier way of doing this? This process requires me to regularly check for a new stock ROM, then borrow the phone from the wife for some time to backup, update, re-root and so on. Not that convenient but it would work if there is no better way.
Sorry for the long post, but I'd be very thankful for any advice or ideas. I did quite some research, but if all this info is already available and I missed it, my sincere apologies. It's a lot of info about a new device to take in. :silly:
derfraenk said:
Hello,
I bought a 9T Pro in Europe for my wife and until it arrives I'm trying to research and come up with a low effort process of keeping the stock ROM up to date and rooted for her. I'm confident in manually installing and updating custom ROMs, rooting and dealing with custom ROM issues, but she is not. Therefore I thought the best thing is to use the stock ROM - not custom - since it may be the most stable experience and for me to update and re-root it for her regularly. root is mandatory because we need AdAway and other things. As I understand it, as soon as we unlock and root the phone, OTA updates for stock are impossible and maybe even dangerous. I've tried researching here but am bit struggling to come up with the right infos and I'd be glad for any advice.
Of course I have seen the great thread about unlocking, rooting, etc, but It seems that that deals with non-standard Chinese firmware pre-installed, which is probably not the case on our device. Since it's bought in Europe, I think it will probably come with some Global or EU ROM. And it doesn't answer some of my other questions.
So far my idea is roughly like this:
Phone arrives
Immediately update it via built-in OTA to latest official stock ROM
Unlock, install TWRP, root with Magisk
Use the phone
Whenever a new stock ROM comes out, download it from XDA
Flash new ROM in TWRP and root again with Magisk
Repeat 4-6 as new stock ROM versions are released
Of course regularly backup with Titanium Backup and TWRP
First of all, would this work or did I misunderstand something fundamental?
How does low level firmware / modem update come into play? Would that be included in the stock ROM packages I find here? Or do I need to manually update that separately? How do I know when I have to, since there is no custom ROM maintainer telling me when it's needed?
Is there an easier way of doing this? This process requires me to regularly check for a new stock ROM, then borrow the phone from the wife for some time to backup, update, re-root and so on. Not that convenient but it would work if there is no better way.
Sorry for the long post, but I'd be very thankful for any advice or ideas. I did quite some research, but if all this info is already available and I missed it, my sincere apologies. It's a lot of info about a new device to take in. :silly:
Click to expand...
Click to collapse
I didn't keep stock MIUI long enough to know definite answers, but from what I remember, this is my understanding.
OTA will still work and shouldn't cause any issues, just that you will lose TWRP and root whenever you do this.
The steps you give are the normal way to update with TWRP and root.
However, OrangeFox recovery (a heavily modified version of TWRP) is often used instead of TWRP in this circumstance. It is built specifically for MIUI devices and with a little bit of work, I believe that it is able to survive OTA updates. Have another dig around for OrangeFox in this forum section and hopefully you'll find details on how to set it up so that you can still take OTA updates.
Edit:
Found this guide https://forum.xda-developers.com/k2...efox-recovery-mi-9t-pro-t3980579/post80480669
It seems OrangeFox it's a bit hit and miss.
Also Xiaomi.eu ROMs are another alternative to look into.
Robbo.5000 said:
I didn't keep stock MIUI long enough to know definite answers, but from what I remember, this is my understanding.
OTA will still work and shouldn't cause any issues, just that you will lose TWRP and root whenever you do this.
The steps you give are the normal way to update with TWRP and root.
However, OrangeFox recovery (a heavily modified version of TWRP) is often used instead of TWRP in this circumstance. It is built specifically for MIUI devices and with a little bit of work, I believe that it is able to survive OTA updates. Have another dig around for OrangeFox in this forum section and hopefully you'll find details on how to set it up so that you can still take OTA updates.
Edit:
Found this guide https://forum.xda-developers.com/k2...efox-recovery-mi-9t-pro-t3980579/post80480669
It seems OrangeFox it's a bit hit and miss.
Also Xiaomi.eu ROMs are another alternative to look into.
Click to expand...
Click to collapse
Wow, that's a lot of helpful info, thanks a lot for pointing me into these directions. I will definitely look into Xiaomi.eu, I that sounds promising!
Get phone. Apply for unlock. Unlock.
You can use my guide bit.do/raphaelguide
Use orangefox 10.8 use magisk.
You can flash eu ROM. Stable version. From xiaomi.eu
Eu rom installs official twrp after install. You are familiar with that
Once you have eu ROM ( same as stock, better performance, minimal bloat, no ads, no tracking)
Eu ROMs gets OTA, keeps root. This is exactly what you want. Just press update in settings as normal ota. It'll do normal ota update by itself, no titanium, migrate hassle.
Join telegram group if you want or on me for any help.
Sandeeep Kiran said:
Get phone. Apply for unlock. Unlock.
You can use my guide bit.do/raphaelguide
Use orangefox 10.8 use magisk.
You can flash eu ROM. Stable version. From xiaomi.eu
Eu rom installs official twrp after install. You are familiar with that
Once you have eu ROM ( same as stock, better performance, minimal bloat, no ads, no tracking)
Eu ROMs gets OTA, keeps root. This is exactly what you want. Just press update in settings as normal ota. It'll do normal ota update by itself, no titanium, migrate hassle.
Join telegram group if you want or on me for any help.
Click to expand...
Click to collapse
Amazing, I have taken a look at Xiaomi.eu already and decided to try that. But what you're saying sounds even much better than what I expected. Thank you very much too, I will definitely go that route.

Categories

Resources