So I just got a Moto E, (boost mobile version), and immediately unlocked the bootloader, and rooted it, installed TWRP. But I'm at Android 5.1, and thinking I should at least go up to 5.11 to get rid of Stagefright vulnerability. I assume I can't just take the OTA update without losing both root and maybe TWRP.
What's the best update route? Or should I just burn a custom ROM using TWRP install zip option?
I don't want to brick my new baby
android94301 said:
So I just got a Moto E, (boost mobile version), and immediately unlocked the bootloader, and rooted it, installed TWRP. But I'm at Android 5.1, and thinking I should at least go up to 5.11 to get rid of Stagefright vulnerability. I assume I can't just take the OTA update without losing both root and maybe TWRP.
What's the best update route? Or should I just burn a custom ROM using TWRP install zip option?
I don't want to brick my new baby
Click to expand...
Click to collapse
There's no 5.1.1 for moto e. So you may want to flash a custom rom
Sent from my Moto E ?
Should I flash a new rom, or just stay at 5.1?
You can use rom android 6 : cm13, vanir, aosp, cyanpop ...
Related
Hi my step son has this phone running blisspop 5.1.1 I want to update his phone to marshmallow. Can I just flash the latest cm 13 or should I odin back to stock and update that way then go through the rooting process? Im not sure if the bootloader and radio and kernel should be updated the stock way first.
I do know with my note 2 I could just flash the latest cm and flash the radio seperate. But this phone is a little foreign to me.
mojorisin7178 said:
Hi my step son has this phone running blisspop 5.1.1 I want to update his phone to marshmallow. Can I just flash the latest cm 13 or should I odin back to stock and update that way then go through the rooting process? Im not sure if the bootloader and radio and kernel should be updated the stock way first.
I do know with my note 2 I could just flash the latest cm and flash the radio seperate. But this phone is a little foreign to me.
Click to expand...
Click to collapse
Currently all the CM-13.0 based ROMs cannot boot with the official marshmallow bootloader. So it would be better to just clean flash the latest CM 13
Good thing I asked. I'm sure the cm team will figure that out at some point. It's actually the reason I asked because I remember on my note 2 going from JB mr1 to mr2 Samsung implemented Knox and sxrewed up everything. Dam girls phone was stock so I did the over he air update this morning. Oh well she doesn't really care anyway.
it's not like you'll wait long for CM to work with the latest bootloader https://review.cyanogenmod.org/#/c/146515
EDIT: it's not like you cant update either, just install CM13 WITHOUT updating stock (which will include the bootloader), aka if you're G900TUVS1FOL1 or older, then CM13 (marshmallow) should work as it has been for the last 5 months
Hey folks,
i have a fresh flashed fire hd7 with downgrade to 4.5.3, root and twrp.
but i dont understand whats the next step to upgrade it to a new version with root.
i think i its better to use the amazon rom, because the actual CM hase some not working components like bluetooth, right?
is there a zip to flash 5.x.x to my firehd?
Hi guys I have an AT&T HTC ONE M8 and it was rooted and running 4.4.4 and TWRP and then something happened to it which caused me to go RUU and restore the device and unroot it and everything. Then I was on 6.0 and rooted it with the HTC ONE M8 rootkit and flashed SuperSU and TWRP on it and currently its still running rooted 6.0 with TWRP, I don't like marshmallow and I want to downgrade to kitkat or lollipop. My bootloader is unlocked and I am S-ON! Please someone explain very thoroughly how I can downgrade as I am not 100% tech-savy as we speak.
Thank You Guys So Much!
You can simply TWRP flash a 5.0 based M8 ROM, or restore a 5.0 backup and it will work. I believe the same is also true for 4.4.4. But not 4.4.3, as it is not compatible with newer firmware (hboot, radio, etc.). And you need s-off to downgrade that firmware.
Be aware, whatever you think you are gaining from downgrading; you are losing by not having years of Android security updates (patches to vulnerabilities, etc.).
Thanks Mate! Can you redirect me to a 5.0 Rom?
TechMan123456 said:
Thanks Mate! Can you redirect me to a 5.0 Rom?
Click to expand...
Click to collapse
Not specifically, no. You can search the ATT Dev section for 5.0 ROM as easily as I can. Or if you don't need or want an ATT based ROM, you can also look in the "international" Dev section: https://forum.xda-developers.com/htc-one-m8/development
Also, ROMs which have been updated (Android 6, 7) may or may not still have links to 5.0 versions.
Alternately (and probably easier to find) just restore a stock TWRP backup of a 5.0 ROM: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You don't need (or want) to restore the data partition, so it is essentially the same as flashing a ROM (although getting the files to the right location is a bit trickier). Also, no need to install stock recovery (as getting an OTA update is not what you want). Then root if desired.
First, I had a rooted G3. Never updated it. Now, I have an H830 (T-Moble) variant. I've been rooted since I bought the phone and have never updated because I don't know how to do it without losing root. I'm still on software version H83010d (Android 6.0.1).
From what I've gathered, I just download the .zip in here and install via TWRP and then flash superSU afterwards?
I'm not completely sure what the talk of modifying boot.img or removing recovery-from-boot.p...
My reason for updating is because I want to try the Fulmics ROM or any optimized ROM for that matter. I had one on my G3 and it ran so much better.
But then as a follow up question, is the update process the same from a ROM? Do you just flash an update over the Rom and then re-flash the ROM?
Any links or answers are appreciated so I can finally figure out how to update while retaining root on my devices. :laugh:
Hello,
I have searched a lot on xda and google and didn't find any answer thus far. Maybe somebody knows this.
I have Griffin model 1650-03 I believe. It was running 7.1 stock RETEU. I have unlocked the bootloader, and proceeded to install the 8.0 a whole ago RETUS (I believe it was the december one). Worked fine, installed magisk and it bootlooped. No problem, I'll just install a custom 8.0 ROM (currently RRO), working fin for months, but now, for reasons and mods, I got to install stock. I usually don't use this device, my main is a Google, so I have read countless posts about how dangerous it is to install stock back, devices bricking left and right. I came across an unbricking solution just in case, but sadly that is for nougat faults, oreo is no-go. And all the guides I've found here and on Google are for 7.1 and I'm on 8.1 with feb security patch. I believe I still have the bootloader from that RETUS update.
TLDR, what is a safe way to return to stock from Custom 8.1 rom?
Thanks
I think since the stock rom is 8.0 it might brick your device... Not sure though.
snsone said:
Hello,
I have searched a lot on xda and google and didn't find any answer thus far. Maybe somebody knows this.
I have Griffin model 1650-03 I believe. It was running 7.1 stock RETEU. I have unlocked the bootloader, and proceeded to install the 8.0 a whole ago RETUS (I believe it was the december one). Worked fine, installed magisk and it bootlooped. No problem, I'll just install a custom 8.0 ROM (currently RRO), working fin for months, but now, for reasons and mods, I got to install stock. I usually don't use this device, my main is a Google, so I have read countless posts about how dangerous it is to install stock back, devices bricking left and right. I came across an unbricking solution just in case, but sadly that is for nougat faults, oreo is no-go. And all the guides I've found here and on Google are for 7.1 and I'm on 8.1 with feb security patch. I believe I still have the bootloader from that RETUS update.
TLDR, what is a safe way to return to stock from Custom 8.1 rom?
Thanks
Click to expand...
Click to collapse
Restore the TWRP backup you did for the stock rom, if you didn't do a TWRP backup you should be fine flashing stock rom the same version you had before installing custom ROMs. Remember if you get a brick it means you are most likely downgrading or upgrading (upgrade should be done with OTA and incrementally to stay safe)
Vcek said:
Restore the TWRP backup you did for the stock rom, if you didn't do a TWRP backup you should be fine flashing stock rom the same version you had before installing custom ROMs. Remember if you get a brick it means you are most likely downgrading or upgrading (upgrade should be done with OTA and incrementally to stay safe)
Click to expand...
Click to collapse
Hello, thank for replying,
So I should be fine if I install via fastboot the same stock RETUS I did before going custom. Should I ota over motorola's software or fastboot? Also, can I be able to OTA RETEU over RETUS?
Thank you
snsone said:
Hello, thank for replying,
So I should be fine if I install via fastboot the same stock RETUS I did before going custom. Should I ota over motorola's software or fastboot? Also, can I be able to OTA RETEU over RETUS?
Thank you
Click to expand...
Click to collapse
I would recommend OTA through the device but it's not reversible (once you flash it you can't downgrade because of bootloader upgrade)
Flashing reteu over retus should be fine as long as you are doing it manually and are aware which partitions you are flashing and which you are omitting. I don't recommend this because sometimes it can break certain things like wifi or data signal (especially if you are on stock rom) and doing OTA later through the device can cause errors
Tldr;
If you want to stay on stock rom, flash back to stock then update everything through rom
If you need root or play around with custom ROMs then don't flash anything just reinstall a stock-like custom ROM
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-install-official-oreo-t3768712 this is the guide i've used to update to oreo (which is RETUS and my device is RETEU), then installed RRO. My guess is I have to install all oreo partitions again (I installed all as stated in that guide) and let it do its OTAs. I had no problems with IMEI and signal on RRO.