It's pretty obvious from forum threads that if I upgrade to an official Sprint ROM beyond OA6, I will be unable to use Odin to downgrade to a previous Official Sprint ROM. However, I haven't seen anywhere that explains the other options.
Things I haven't seen answered definitively, only --at best-- alluded to
Can I use a custom recovery to downgrade to a previous Official Sprint ROM? I think the answer is no.
Can I flash a modified TouchWiz-based ROM (even, e.g., a simple "stock with root" ROM), based on any Lollipop build? I think the answer is yes.
Can I flash a modified TouchWiz-based ROM, based on a KitKat build??
Can I flash a KitKat AOSP/Cyanogenmod-based ROM??
Can I flash a Lollipop AOSP/Cyanogenmod-based ROM??
Would appreciate if someone could answer/confirm the various options!
Anyone? Any links / resources / answers??
This can't be that uncommon of a quesiton....
Related
I am running the stock rom and flashed the new firmware last night ( 1.55.605.2 ) and am interested in running a rom that is based off of an older firmware. Is there any problem in doing this? Will it roll my firmware back to the old one?
I'm currently running the old version of SkyFall (1.3) based on the old firmware, and I updated my firmware today with no problems. So it should be fine, though ymmv. But whatever ROM you want to run will probably be updated soon anyway.
Sent from my VZW HTC One M8
Joeysface said:
I am running the stock rom and flashed the new firmware last night ( 1.55.605.2 ) and am interested in running a rom that is based off of an older firmware. Is there any problem in doing this? Will it roll my firmware back to the old one?
Click to expand...
Click to collapse
I can't remember exactly where I read it but somewhere in the myriads of posts about this OTA it is pointed out that with different hboots, recoveries, kernels and modifications to system files, framework etc. etc. it is almost inevitable that something may go awry.
If you have taken the trouble and time to migrate to a custom ROM, it usually makes sense to let your dev sort things out. On the other hand, if you aren't experiencing any problems with the new firmware, why roll back?
Beamed from the holodeck of my Nexus 7 FHD.
hgoldner said:
I can't remember exactly where I read it but somewhere in the myriads of posts about this OTA it is pointed out that with different hboots, recoveries, kernels and modifications to system files, framework etc. etc. it is almost inevitable that something may go awry.
If you have taken the trouble and time to migrate to a custom ROM, it usually makes sense to let your dev sort things out. On the other hand, if you aren't experiencing any problems with the new firmware, why roll back?
Beamed from the holodeck of my Nexus 7 FHD.
Click to expand...
Click to collapse
It's not so much that I am having issues as I am wanting to try a rom that is showing based on the older firmware and I don't want to cause any issues with that. On a related note, I am running the stock rom currently and flashed the firmware that Santod posted in RUU but my firmware shows that it is still the 1.12.605.11 even though hboot shows me on 1.55.605.2. Did I botch something?
Joeysface said:
It's not so much that I am having issues as I am wanting to try a rom that is showing based on the older firmware and I don't want to cause any issues with that. On a related note, I am running the stock rom currently and flashed the firmware that Santod posted in RUU but my firmware shows that it is still the 1.12.605.11 even though hboot shows me on 1.55.605.2. Did I botch something?
Click to expand...
Click to collapse
See if my post here answers your question/concern.
I urge you to read more of that thread if you have more questions or concerns, as most of them have been answered there.
And for reference:
Old software with new firmware is almost always fine.
Running new software with old firmware is when real issues usually arise.
santod040 said:
See if my post here answers your question/concern.
I urge you to read more of that thread if you have more questions or concerns, as most of them have been answered there.
And for reference:
Old software with new firmware is almost always fine.
Running new software with old firmware is when real issues usually arise.
Click to expand...
Click to collapse
Hey thanks for replying man, I haven't messed too much with manually flashing firmware and didn't want to screw something up. So does the OTA have some software elements to it as well because I've noticed that people who took it are showing the updated firmware and an "Official" or "Unofficial" status in their settings? I've read through a lot of the forums and saw the post you linked to I just wasn't sure if what you were referring to in that post was the same thing as flashing a rom that shows a specific firmware.
G
Joeysface said:
Hey thanks for replying man, I haven't messed too much with manually flashing firmware and didn't want to screw something up. So does the OTA have some software elements to it as well because I've noticed that people who took it are showing the updated firmware and an "Official" or "Unofficial" status in their settings? I've read through a lot of the forums and saw the post you linked to I just wasn't sure if what you were referring to in that post was the same thing as flashing a rom that shows a specific firmware.
Click to expand...
Click to collapse
Firmware is just firmware.
It's not a Rom. It's something that gets updated with the ota that cannot be flashed in a custom Rom.
So before updating to a newer software version based on the update it's best to flash the firmware as well or you just get the software and no firmware by flashing just the Rom.
The firmware is at a lower level on the device and persists through Rom flashing unless you take an ota or flash an ruu.
When running custom roms it's general rule of thumb not to take otas.
Less issues that way.
So to update everything like you would had you taken the ota, you flash firmware and software to be up to date.
In other words, I've provided the firmware part of the OTA.
You just need someone to post a rooted version of the software update now.
Sent from my HTC6525LVW using Tapatalk
Hi,
I was wondering what steps I would need to take to go from
TF300T
Stock 4.1.1
Build# JRO03C.WW_epad-10.4.2.9-20120809
Click to expand...
Click to collapse
To be able to flash into a Kitkat Stock-based ROM or KatKiss 5.0.1? I need to stick with stock based so my flashed touch firmware will stay.
If someone could link me to the proper tutorials/guides that would be great.
hkp2 said:
Hi,
I was wondering what steps I would need to take to go from
To be able to flash into a Kitkat Stock-based ROM or KatKiss 5.0.1? I need to stick with stock based so my flashed touch firmware will stay.
If someone could link me to the proper tutorials/guides that would be great.
Click to expand...
Click to collapse
In order to use the new KitKat ROMs, you actually have to upgrade to the latest stock firmware (JB 4.2). The new TWRP and ROMs require the newer bootloader. I'm not that familiar with the touch firmware and how that works, but I'm not sure if that is upgradable too?
First OTA to 4.2, then install any recovery (see Question and answer section) and then flash ROM.
I just want to get this straight before I do anything rash. In order to install a custom rom ie MOAR on my sm-900p if the rom says 5.0.2 does my android version have to be the same or can it be 5.0 and still work without bricking? Along these same lines, is it possible to downgrade to 4.4.4 via the stock room and will there be any issues? I have also read about leaked stuff like I am running 5.0 and if I wanted to somehow get a leaked 5.0.2 rom how does this work?
Thanks in advance.
jvenz76 said:
I just want to get this straight before I do anything rash. In order to install a custom rom ie MOAR on my sm-900p if the rom says 5.0.2 does my android version have to be the same or can it be 5.0 and still work without bricking? Along these same lines, is it possible to downgrade to 4.4.4 via the stock room and will there be any issues? I have also read about leaked stuff like I am running 5.0 and if I wanted to somehow get a leaked 5.0.2 rom how does this work?
Thanks in advance.
Click to expand...
Click to collapse
If you want to install MOAR, check the MOAR FAQ and it should answer all you questions. Post#2 is a step by step on installing. Recommend you stay away from leaked versions until you're more comfortable about how to get out of a problem. MOAR 6.0 is based on the official Lollipop release. If you have any MOAR questions after you've read the instructions, feel free to post on that thread.
Ramer said:
If you want to install MOAR, check the MOAR FAQ and it should answer all you questions. Post#2 is a step by step on installing. Recommend you stay away from leaked versions until you're more comfortable about how to get out of a problem. MOAR 6.0 is based on the official Lollipop release. If you have any MOAR questions after you've read the instructions, feel free to post on that thread.
Click to expand...
Click to collapse
Ty for the response, but, I already realize that there is a rom for 5.0 it was just an example. I really wanted to know about the android versions and if they have to be the same ie can I flash a rom that is for 5.0.2 even though my android version is 5.0?
jvenz76 said:
Ty for the response, but, I already realize that there is a rom for 5.0 it was just an example. I really wanted to know about the android versions and if they have to be the same ie can I flash a rom that is for 5.0.2 even though my android version is 5.0?
Click to expand...
Click to collapse
Yes you can. You can also go back to 4.4.x but it requires flashing firmware back for Kitkat.
Ramer said:
Yes you can. You can also go back to 4.4.x but it requires flashing firmware back for Kitkat.
Click to expand...
Click to collapse
Is there a link to describe this process?
jvenz76 said:
Is there a link to describe this process?
Click to expand...
Click to collapse
http://forum.xda-developers.com/spr...irmwareonlyodinflashabl-imagesfor4-4-t2958614
Hi,
I am new to this particular phone. There's so much information here, and although I've tried to search through it I'm still overwhelmed by it all - so I'm hoping someone might be willing to help with a few questions.
I have the XT1540 model, and could use some help. I have the stock rom with TWRP intalled and backups. I was notified that I have the Marshmallow update available, but I can't install due to TWRP. I prefer to keep the Motorola provided ROM. Since this was just released, I assume no one has posted the Marshmallow "stock" rom - is that correct?
I know asking for an ETA is poor form, but you guys know these forums and what can be expected - any idea when a backup image of the Motorola provided Marshmallow rom might be posted?
I assume I can't restore the stock bootloader in order to complete the Marshmallow installation - is this correct?
Final question: Is there a highly stable, all-features-intact custom Marshmallow ROM that comes highly recommended?
Thanks in advance,
Chris
There is no estimate as to when the full stock of MM will be available. There is a TWRP backup of the final soak available over in the General forum. It's been the last soak for quite a while now and I suspect it's the final. I've run all the soaks and that last release is running perfectly on my XT1540 1gb model. It is a backup from a 2gb version but that doesn't matter, it works on either model. Once flashed you won't get the OTA but then with TWRP you won't get that anyway.
Sent from my SM-T530NU using Tapatalk
I'm a bit confused because I can't seem to find everything about that and will my cm11 ROM that I currently have installed and any other hboot2.15 ROMs still work after upgrading to 2.16 and does anyone else have any experience (bad or good) after upgrading to 2.16?
No, 2.15 roms won't work on the latest 4.x firmware (which contains hboot 2.16). The storage handling is completely different on the newer/leaked firmware. Therefore, flashing an outdated rom will result in the phone stating that your storage has a size of 0 MB. This makes the phone unusable and is only fixable by flashing a firmware 4.x-compatible rom via TWRP.
Aside from that, firmware 4.x is definitely better than version 3.x. The storage partitions get unified so that you won't run out of space for apps, anymore. And not to forget that the latest android 7 custom roms all require the newer firmware.
Make sure that you use one of the "good" guides that update the whole firmware. There are some posts that only explain how to update the hboot (e.g. in the themes section). That's not enough. If you only update that one single file then your phone lacks essential files from the newer firmware and this will result in bugs and lags of the roms that you're using. The guide in the general section is fine or you use the original guide in the maximus hd thread where the 4.x firmware got published first or you look for the unofficial RUU.zip that is hidden somewhere in the dev section.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
No, 2.15 roms won't work on the latest 4.x firmware (which contains hboot 2.16). The storage handling is completely different on the newer/leaked firmware. Therefore, flashing an outdated rom will result in the phone stating that your storage has a size of 0 MB. This makes the phone unusable and is only fixable by flashing a firmware 4.x-compatible rom via TWRP.
Aside from that, firmware 4.x is definitely better than version 3.x. The storage partitions get unified so that you won't run out of space for apps, anymore. And not to forget that the latest android 7 custom roms all require the newer firmware.
Make sure that you use one of the "good" guides that update the whole firmware. There are some posts that only explain how to update the hboot (e.g. in the themes section). That's not enough. If you only update that one single file then your phone lacks essential files from the newer firmware and this will result in bugs and lags of the roms that you're using. The guide in the general section is fine or you use the original guide in the maximus hd thread where the 4.x firmware got published first or you look for the unofficial RUU.zip that is hidden somewhere in the dev section.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thank you very much for explaining it really well, same as for the problem that I'm experiencing with the "2nd partition" in app2sd! As soon as my dad gets home, he and I will update the firmware.
Danke vielmals! ^^
Edit:
Oh, and what is the most stable running android rom that you'd recommend? I don't really want to upgrade to the newest android versions because I don't want any lags :/
-----------Update----------------
Never mind, I already found my current ROM that I am using for HBOOT2.16 to download from F-L-Y-E-R
All android 7 roms are stable and they aren't laggier than the stock rom.
Link to the Lineage thread
Link to the Resurrection Remix thread
A link to the latest TWRP version for firmware 4.x can be found in my signature
I'm now also running lineage as I already installed it yesterday. As of now the ROM hasn't let me down just yet, and it seems that I will be able to use it as my daily driver ^^
So far I'm really enjoying lineage!