need some advice - T-Mobile Samsung Galaxy S 5

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

Related

[Q] Changing ROM

Hey guys. I posted a few days ago with a question about restoring my dad's phone to stock for warranty and this got me thinking about making some changes to my phone as well. I'm currently on Beans rom (Now called Alliance I believe) build 21. I'm thinking about trying out CM11 which I believe is Android 4.4. I went to the CM website to check out a guide on how to do this and came across this: http://wiki.cyanogenmod.org/w/Install_CM_for_i605
This guide APPEARS to be written for Note 2's that took the OTA that locked the bootloader. I still have an unlocked bootloader on Beans rom. So my question is do I need to bother with all the steps in that guide? Or is that only if bootloader is locked? Do I need Heimdall or Clockworkmod Recovery? Can I just use TWRP that I already have and do a data/cache wipe and flash the CM11 Rom? Any firmware files needed? Since my current rom is only Android 4.1.2? The Alliance rom thread says to flash MJ9 firmware before flashing their rom but I see no mention of it in the CM guide.
Thanks so much. You guys are the best!

Galaxy S3 Downgrade CM 11 - 10.1 i747

I have been a long time lurker on these forums, and to start on here would like to thank all the helpful posts I have read. Currently I am using a Galaxy SIII (i747). I'm not sure what firmware I got it on, however I downloaded the CM installer from the website and used it to flash my phone. It currently is on a really unstable CM11 build (kind of mad the installer pushed a non-RC to my phone) and I would like to downgrade to CM10.x. I checked the d2att wiki and there are no RC or stable CM 11 builds. From what I read there was a bootloader introduced in 4.3 that locked down the phone. I'm not sure if a) I have this locked down bootloader? I currently have TWRP installed, which I think a locked bootloader would prevent. b) Is it safe for me to try and downgrade to CM 10 with ODIN? Any help would be much appreciated.
jdkuki said:
I have been a long time lurker on these forums, and to start on here would like to thank all the helpful posts I have read. Currently I am using a Galaxy SIII (i747). I'm not sure what firmware I got it on, however I downloaded the CM installer from the website and used it to flash my phone. It currently is on a really unstable CM11 build (kind of mad the installer pushed a non-RC to my phone) and I would like to downgrade to CM10.x. I checked the d2att wiki and there are no RC or stable CM 11 builds. From what I read there was a bootloader introduced in 4.3 that locked down the phone. I'm not sure if a) I have this locked down bootloader? I currently have TWRP installed, which I think a locked bootloader would prevent. b) Is it safe for me to try and downgrade to CM 10 with ODIN? Any help would be much appreciated.
Click to expand...
Click to collapse
I also have an ATT S3 (I747) - It's running flawlessly on CM 10.2.1 (4.3) with the UCUEMJB bootloader (which can not be downgraded at this time to my knowledge). It also has TWRP 2.8.1.0 installed. I used this to downgrade from CM11 to CM 10.2.1 by restoring thru TWRP.
So, you should be good to go. Just make a Nandroid backup using TWRP and then flash CM 10.2.1 (zip file) using TWRP.
BTW - the MJB bootloader can not be downgraded. The MJ2 and earlier bootloaders (prior to 4.3) can be. I believe this is what you're referring to as "locked"???
Hope this helps . . .

Wanting to Upgrade to Nougat

My phone is currently using VipreOneM9 3.5.0, my Android version is 5.1 Lollipop, and my HTC Sense version is 7.0. My carrier (and thus where I got my phone) is Sprint.
I've rooted plenty, but I've never had to unroot or update, usually by the time I feel the need to upgrade my phone's version it's time to just upgrade my phone anyway. I'd like to upgrade to Nougat, but I'm not sure exactly what I need to do and I want to make sure I don't screw it up and possibly brick my phone. I'm also wanting to upgrade to ViperOneM9 6.0, and since it's such a big jump I was told to just treat it like a new install instead of an upgrade.
Scaevus said:
I'd like to upgrade to Nougat
Click to expand...
Click to collapse
I've been on AOSP for awhile now, did the official HTC Nougat update finally drop for Sprint M9's?
For LineageOS 14.1 builds by @irocevo, you'll need to:
Have, at the very least, an unlocked boot loader
Have TWRP 3.0.3-0 installed
Since you're currently on a Sense ROM, start from scratch (wipe boot, system, data, etc)
Don't forget the Nougat 7.1 GApps for ARM64
Lacedaemon said:
I've been on AOSP for awhile now, did the official HTC Nougat update finally drop for Sprint M9's?
For LineageOS 14.1 builds by @irocevo, you'll need to:
Have, at the very least, an unlocked boot loader
Have TWRP 3.0.3-0 installed
Since you're currently on a Sense ROM, start from scratch (wipe boot, system, data, etc)
Don't forget the Nougat 7.1 GApps for ARM64
Click to expand...
Click to collapse
I'm not sure if it dropped or not, but either way I would actually like to just upgrade in general to whatever my phone has at the moment!
I unfortunately don't have my original OS also, so I can't flash to it. :/
Scaevus said:
I'm not sure if it dropped or not, but either way I would actually like to just upgrade in general to whatever my phone has at the moment!
I unfortunately don't have my original OS also, so I can't flash to it. :/
Click to expand...
Click to collapse
I'm not sure what your preference is when it comes to Sense vs AOSP, but until HTC's Nougat update drops, the very latest that I am aware of is the LineageOS 14.1 I mentioned.
You don't need your original OS for LineageOS.
Scaevus said:
My phone is currently using VipreOneM9 3.5.0, my Android version is 5.1 Lollipop, and my HTC Sense version is 7.0. My carrier (and thus where I got my phone) is Sprint.
I've rooted plenty, but I've never had to unroot or update, usually by the time I feel the need to upgrade my phone's version it's time to just upgrade my phone anyway. I'd like to upgrade to Nougat, but I'm not sure exactly what I need to do and I want to make sure I don't screw it up and possibly brick my phone. I'm also wanting to upgrade to ViperOneM9 6.0, and since it's such a big jump I was told to just treat it like a new install instead of an upgrade.
Click to expand...
Click to collapse
The first thing you should do is install the latest stock update for your device. Then you can upgrade to the latest version of Viper or any other Nougat that has support for Sprint handsets.
Dark Stranger said:
The first thing you should do is install the latest stock update for your device. Then you can upgrade to the latest version of Viper or any other Nougat that has support for Sprint handsets.
Click to expand...
Click to collapse
Go to this thread, in this forum, [RUU][Firmware][Stock Rooted ROM]Sprint HTC One M9 | 3.41.651.41 | Updated 12.14.16. Download the RUU 3.41.651.41. Follow the instructions in the OP. To the best of my knowledge, this is the latest firmware for the Sprint M9. Run the RUU first, then the ROM and everything else.
Completely stock Sprint M9 here - NO Nougat update as yet . . .
davidtm0 said:
Completely stock Sprint M9 here - NO Nougat update as yet . . .
Click to expand...
Click to collapse
Sprint has not released a Nougat rom as of this time, so no there isn't a completely stock Nougat rom. However, I have Sprint HTC M9 and I am running a Nougat rom. Update your firmware to the latest, see a post or two above this. It is critical that you are on the latest firmware. Then after flashing TWRP, go to the HTC M9 thread, not the Sprint M9 thread. There are a couple of different Nougat roms in that thread. I am running the Vipre V6, flashed it a couple of days ago.

Can I downgrade HTC ONE M8 from 6.0 to 5.0 or 4.4.4?

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.

The quest for stock

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.

Categories

Resources