So now that I am rooted a can no longer receive OTA updates. Also, being a Sprint\Tmo device, I don't have "Local Upgrade" option.
Can someone tell me how I would now go about updating my device?
Do I simply wait for A11-based rom?
Do I need to remove magisk\modules in order to re-enable OTA?
Any help is appreciated.
I was actually about to ask this very question myself, the local update is missing on mine too, so that didn't change when you rooted? Maybe you can flash one of the stable releases they came out with recently? My question was would the global version work for our tmobile branded devices.
Also wondering wtf is up with tmobile cutting features out of the updates like shelf that dropped in July.
There is a guide to switch to global firmware.
It seems straight forward.
I would rather not.
If there was a stock rom image that we could simply flash via magisk or twrp, the process would be far simpler.
My guess is that for the method above to work, we will need to wait for A11 source code to drop.
Afterwards, we will likely see full A11 roms that we can use.
Ideally we would wipe system, data, cache. Flash rom. Wipe data again. Reboot.
Related
I have successfully rooted my note 12.2 - thanks to this awesome forum.
With that I can't do OTA or use Kies to stay up to date. So I'd like to know how I can stay up to date as Samsung releases new firmwares? For example I just downloaded the newly released 5.0.2 from Samobile and flashed it with Odin 3.09. That went well but of course it wiped my machine so I'm starting fresh again. I'd like to be able to stay up to date with out a complete re-wipe each time if possible. Thoughts?
As a long time root user I can tell you that the cardinal rule is that one should give up the notion of getting OTA updates for good once one roots for the simple fact that with each major OTA update comes the risk of losing root forever should the update lock the doors on the exploit used to gain root to begin with.
Casual root users are best served by watching forum threads after updates are released to see how more experienced users are fairing with getting their devices up to date. The exception to this is if a custom ROM is installed and the developer updates the ROM periodically to integrate the updated software or features that the device manufacturer releases. Even then, if a major update is released that let's say jumps to a new system like kitkat to lollipop there's a chance that a full wipe can't be avoided. ROM developers typically warn users when clean installs are required, and some even distribute their own OTAs.
I'm a religious user of titanium backup, and I will often dirty flash a ROM update or use prior titanium backups to restore data but this can be risky business when major updates are released because if software or drivers change from one major firmware release to another a backup of a particular application may no longer be compatible and stability may be affected upon restore.
Bottom line, if you want lollipop on your note pro, rooted, can live with the current bluetooth issues and want to be able to update further easily while retaining root then go with a custom ROM like civs and just monitor the thread of that ROM for updates.
Hope this helps.
Thanks for the excellent advice. One two more more question on the topic. I had root on KitKat, but after flashing the new stock Lollipop via Odin, I lost root. So after installing the stock Lollipop I had to re-do the root flash via Odin to get root back, thankfully it all worked out. (Lollipop is awesome BTW).
Questions:
1. Was I in danger of forever losing root as you state above or was this a safe route? I understand that OTA and even Kies can make me lose root forever, but what about flashing a stock via Odin?
2. Are you saying that next time there's an update I could try to dirty flash the ROM via TWM (after doing a good backup via Titanium of course)? Basically find ROM on samobile, download, copy to SD card and dirty flash away using these suggestions: https://www.reddit.com/r/Android/comments/sthr8/dirty_flashing_what_it_is_and_is_not_lets_set_the/
Typically to keep root the stock recovery is replaced with a custom one, TWRP is the main one used for our device. Stock updates from Samsung downloaded as OTA will typically fail to flash in TWRP. Odin flashing stock images will erase everything including the custom recovery, thus causing loss of root. In other words you'll typically lose root one way or another and the key to retaining it is to not blindly update until a root method is ensured for the next version of firmware. Resign to the fact that with each update you will temporarily lose root and need to redo it. Plan ahead, wait for root confirmation and then update with a plan of how to get root again.
I typically don't TWRP flash stock so I don't know if it works but in the distant past I recall that it wouldn't so thus I never try. Maybe someone can confirm. For me I haven't updated firmware on my note pro for a year now and I am not missing anything. ..
Sent from my SM-N910T using Tapatalk
Just wondering if I'll be able to take an OTA update from 6.0 to 6.0.1 whenever it is available? I received a message saying a software update was available and when I told it to install it, it rebooted into TWRP, checked the current software for about 3 minutes, then rebooted? Upon looking, I am still on 6.0? I had the system check to see if there was still an update available, but it said there was nothing. Maybe it was just a radio update? I am anxiously awaiting the update so that I may install Xposed. Any input would be greatly appreciated :good:
AT+T US Unlocked
Rooted/S-off
6.0
1.10.502.3
You can't take OTAs with rooted phones and twrp. The OTA looks at the system partition and if anything is changed...it will not install.
You have to either take a backup somebody made with the OTA/stock basically. Flash it via TWRP. Or RUU back to the lastest for your phone. Then, take all OTA updates, then TWRP, Format Data, then SuperSU again, reboot...start/restore phone.
There is no easy way without Dev support/Custom Roms to get latest bases/OTAs right now without wiping/starting over somehow.
This is why having devs creating Roms is really a luxury. Because they already have the proven installer/Rom customized. They will then take OTAs/new bases, roll that into their Rom, and you just do an update/flash, like Viper, and not lose anything, and no need to wipe.
Likely never to happen with this phone since Devs really only work on the Mainline/Flagship M models, like M8/M9/M10 etc...
I just bought one of those in-store display models off of eBay for ~$270 to play around with while I'm waiting for my next phone. First of all, those phones have incredibly severe screen burn-in - I don't recommend them.
The unit I bought was a T-Mobile model that is sim-unlocked (I'm also on T-Mobile, so I can eventually legitimately unlock it myself, if necessary, as I'll be running it on a spare line).
My high-level goals are:
1. Flash to Int'l
2. Flash & run xXx NoLimits
3. Flash & run Open Beta
4. Call Screening is a must! (I understand xXx NoLimits has it built-in but this is my Plan B for enabling it: Google Call Screening)
This is my more scripted-out plan for accomplishing these things:
0. Check out the device in general, make sure it works, and do a factory reset.
1. Install Drivers (Plug phone in -> install from Windows Explorer USB file share thingie)
2. Use MSM to flash stock TMo firmware
3. Fully update it via System -> Check for Updates
4. Use MSM to flash to int'l
5. Factory reset & fully update via System -> Check for Updates
6. Flash the latest Open Beta
7. Unlock bootloader, Flash TWRP, and install Magisk. (alternate guide)
8. Flash & run xXx NoLimits
9. Flash & run Open Beta
My general questions:
1. Is this a solid plan?
2. Am I missing anything important here?
3. Will these things work together?
4. What "gotchas" might I run into? Netflix support? Play Store support? Functional Call Screening? Anything else?
Jaxidian said:
I just bought one of those in-store display models off of eBay for ~$270 to play around with while I'm waiting for my next phone. First of all, those phones have incredibly severe screen burn-in - I don't recommend them.
The unit I bought was a T-Mobile model that is sim-unlocked (I'm also on T-Mobile, so I can eventually legitimately unlock it myself, if necessary, as I'll be running it on a spare line).
My high-level goals are:
1. Flash to Int'l
2. Flash & run xXx NoLimits
3. Flash & run Open Beta
4. Call Screening is a must! (I understand xXx NoLimits has it built-in but this is my Plan B for enabling it: Google Call Screening)
This is my more scripted-out plan for accomplishing these things:
0. Check out the device in general, make sure it works, and do a factory reset.
1. Install Drivers (Plug phone in -> install from Windows Explorer USB file share thingie)
2. Use MSM to flash stock TMo firmware
3. Fully update it via System -> Check for Updates
4. Use MSM to flash to int'l
5. Factory reset & fully update via System -> Check for Updates
6. Flash the latest Open Beta
7. Unlock bootloader, Flash TWRP, and install Magisk. (alternate guide)
8. Flash & run xXx NoLimits
9. Flash & run Open Beta
My general questions:
1. Is this a solid plan?
2. Am I missing anything important here?
3. Will these things work together?
4. What "gotchas" might I run into? Netflix support? Play Store support? Functional Call Screening? Anything else?
Click to expand...
Click to collapse
After reading all of that, just give up because you have no idea what you're doing. Why flash a ROM if you are flashing open beta? Open beta is the beta version of stock ROM(OOS) so it will overwrite xxx rom
jamescable said:
After reading all of that, just give up because you have no idea what you're doing. Why flash a ROM if you are flashing open beta? Open beta is the beta version of stock ROM(OOS) so it will overwrite xxx rom
Click to expand...
Click to collapse
My bad, I thought I posted in a Q&A forum where questions were encouraged. I also thought the Open Beta was an OTA update on top of stock OOS and that xxx claimed things like "Still working after OOS version upgrade" and "Support OOS Stock Rom OTA's" and "When a new OOS OTA is available, just run the OOS update, flash Magisk again and xXx NoLimits is still in place and working like before".
Not sure what your problem is but go piss in somebody else's punch bowl.
Jaxidian said:
My bad, I thought I posted in a Q&A forum where questions were encouraged. I also thought the Open Beta was an OTA update on top of stock OOS and that xxx claimed things like "Still working after OOS version upgrade" and "Support OOS Stock Rom OTA's" and "When a new OOS OTA is available, just run the OOS update, flash Magisk again and xXx NoLimits is still in place and working like before".
Not sure what your problem is but go piss in somebody else's punch bowl.
Click to expand...
Click to collapse
I am running open beta on a stock TMobile 7pro. Works great. You don't need to do all the updates. Just flash the open beta after you switch to international.
Hey if u do the call screening magisk way. Be sure to use the Google dailer 39. Apkmirror and make sure the updates is turned off for it.
Alright, so I was in the same boat as you, I bought a T-Mobile 7 Pro model earlier in the week; and nicely asked T-Mobile support through the App a few times to help me SIM-Unlock it so I could do my bootloader unlock and linked the Oneplus Support website and the Unlock page.
I ran into many issues so I'll help you out as I just finished my 6 day journey of making it functional.... Along the way, I lost cell service, I lost all my sensors.... So I'd recommend taking a TWRP backup everytime you're able to successfully boot into the device; Note: my goal was Havoc, so I ended up in a different place than where you're trying to go. I don't know what exact problems you'll run into, but I'm letting you know what I think makes sense from my previous experience over the week.
Your scripted-out plan:
0. Sure, test it, but you'll end up automatically wiping it later when you unlock the bootloader.
1. Sure, install the drivers.
2. You probably don't need to flash stock T-Mobile firmware as it's already running it.
3. You probably don't need to update it.
4. Yes, Flash it to international.
5. You probably don't need to update it. However I'd recommend to unlock the bootloader here;
5a. (The Damned T-Mobile model makes flashing TWRP a bit difficult) I'd recommend taking a note on what Slot is currently active (A or B).
Use "fastboot getvar current-slot" to find out; Then I'd recommend switching to the other slot ( If you're on Slot A, switch to Slot B, vice versa) to flash TWRP first (this overrides your boot image on your active slot, but is the only way to boot TWRP on the T-Mobile variant) and then flash the TWRP installer (this will flash TWRP to both Slots).
5b. After using the TWRP installer from your 2nd Slot, Use TWRP to swap back to the 1st Slot. Now make a complete full TWRP backup with all the boxes checked. Then, copy that backup to your computer so that it won't get wiped in the next few steps. (Do not skip this. If you did this correctly, You will have a place to come back to just in case you **** up your sensors, and cell service like I did.).
5c. Doublecheck if you can actually boot to your original Slot and if everything's functioning. Check if you can boot to your other Slot and see if everything's functioning. (This is where you super-need to make sure you have a safe place to come back to).
6. Sure, you can try flashing the latest Open Beta, but you might have to install TWRP again back in step 5b.
7. You might or might not have to unlock the bootloader, depending on what method you use to flash the Open Beta, your bootloader status might save; Sure, flash Magisk using TWRP.
8. Sure, flash xXx NoLimits using Magisk Manager.
9. Why undo your work and flash the Open Beta again? Don't do this.
With that you should be done.
If at any point you had an issue, I'd recommend using the TWRP backup you created earlier in 5b.
If you super-super have an issue, you'll have to use MSM to go back to stock International firmware.
In my case.... I had super-super issues and I had no TWRP backups.... and I had to use MSM to go back all the way back to T-Mobile stock firmware and start over because I had no service, and no sensors (proximity, gyroscope, accelorometer, etc).
But in the end, I think I have everything functioning the way I want to on HavocOS.
It's been a minute but I now have an update to my journey.
I had to take a quick pause at step 4 of my plan. The phone was SIM-unlocked but the bootloader itself was locked. So I had to do the dance with OnePlus and wait a couple weeks for that unlock code. Well, I finally got that puppy, so was able to start this project this weekend. Here's what I've done and where I'm at so far:
0. Device checked out well. Works great, aside from the screen burn-in issues (which is why I got it so dang cheap).
1. Drivers installed. ADB & Fastboot work great.
2. I used MSM to flash back to TMo firmware after my previous failings when I hit the locked bootloader wall. It worked great to get me to the point where I could generate the phone unlock code request to send to OP.
3. Not needed, although I did this while waiting 2 weeks for OP to send me a code.
4. Done. Worked perfectly. Hello, TMo-less firmware. Also, hello SIM #2 (the 2-week delay gave me time to buy a dual-sim tray).
5. Factory reset as part of the flashing and unlocking. Not bothering with system updates yet.
6. Not yet done this.
7. Bootloader is now unlocked. Magisk is installed but TWRP is not yet installed. This is where I'm at now.
Not hitting any problems. Just ran into dinnertime and my kiddo's bedtime. Thought I'd post this update before I started back up. So far, so good, other than that surprise 2-week delay waiting for an email.
Hi everyone,
I read in the latest XDA-newsletter that finally Poco had released the MIUI 12 update. This firmware update was considered to be more important than an Android version 11 upgrade.
Can anyone tell me if the .zip file: miui_SURYAEEAGlobal_V12.0.6.0.RJGEUXM_246b1aa34f_11.0.zip (found on XDA) can be used to install, but without having to lose all the personal data and apps?
Thanks for your help.
Greetings,
Lepapron
Hi. I don't quite understand what you are trying to say but V12.0.6.0.RJGEUXM is Android 11 based rom. It also is the Europe version not Global. Theoretically if currently you're on, lets say 12.0.7 or 12.0.8 Global or Europe you'll not lose any personal data and apps if you flash this. It should be treated by your device as an update. If you decide to go back to your OG firmware though you'll have to do FORMAT DATA or you'll end up in a boot loop.
To be clear. I am not advising you to do this and do not guarantee it'll succeed.
MocnePifko said:
Hi. I don't quite understand what you are trying to say but V12.0.6.0.RJGEUXM is Android 11 based rom. It also is the Europe version not Global. Theoretically if currently you're on, lets say 12.0.7 or 12.0.8 Global or Europe you'll not lose any personal data and apps if you flash this. It should be treated by your device as an update. If you decide to go back to your OG firmware though you'll have to do FORMAT DATA or you'll end up in a boot loop.
To be clear. I am not advising you to do this and do not guarantee it'll succeed.
Click to expand...
Click to collapse
Thank you.
Although you did not quite understand what I meant, you answered my question perfectly well. Don't do it..! I won´t, because I downloaded the file as a zip file here on XDA, so when I unzip it, I assume my POCO X3 NFC will not see it as a regular update. And the foresight of a boot loop is not a very prosperous sight, so I'll just wait until it arrives as OTA.
Well done, that was very helpful.
The 2117 model is not mentioned in official compatibility, but all the others are. Any Tmobile users running Lineage or know if it works?
I used it for a bit. Works good as any other device IMO.
Follow This guide on the official page.
Im just iffy on the whole thing- Still on A11 OOS11 and Im hearing Ill possibly need A12 firmware as a base before install? I cant just use TWRP and flash? Its been ages since I went custom (HTC One Cyanogen with CWM, I believe we were able to use TWRP as well back then) and it sounds like you need Lineage Recovery?
Can I follow that guide straight from rooted *BL unlocked A11 OOS11? No updates have been applied to my phone afaik. Disabled right away.
TimmyP said:
Im just iffy on the whole thing- Still on A11 OOS11 and Im hearing Ill possibly need A12 firmware as a base before install? I cant just use TWRP and flash? Its been ages since I went custom (HTC One Cyanogen with CWM, I believe we were able to use TWRP as well back then) and it sounds like you need Lineage Recovery?
Can I follow that guide straight from rooted *BL unlocked A11 OOS11? No updates have been applied to my phone afaik. Disabled right away.
Click to expand...
Click to collapse
Lineage updates the firmware as part of the install.
Ah thank you! Ill prolly do it after some time. I'm completely happy on 11 for now. Have it debloated and set up with xposed modules and everything.
I've used lineage before on the le2117 but decided to switch to evolution x since it's packed with features
What the battery life like between the two? I dont necessarily need features since I add everything I need with magisk\lsposed. This stock rooted rom Im on now is getting great battery life.
On both installation pages for this and EvoX, it says you need to be on A13 firmware. Is this a hard requirement? Or can I truly just flash my phone as it is currently? Stock root, A11, OOS11?
I cant do OTA updates, nor can I install downloaded updates (via the settings app) either because I converted, or its Magisk or something...
How did you get you Tmos to 13? Were you already updated before rooting? Did the OTA work after root for you? I just get install failed immediately with the downloaded package.
Any input would be appreciated Im in no rush, and I already have a backup setup for after conversion (assuming Migrate works on this phone, seems to so far).