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
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
So as some of you may know the S4 had it's exploit fixed and since then we haven't been able to get away from Touchwiz based roms.
Before I go get the G3 I just wanted to be 100% clear that even the latest firmware hasn't fixed Bump, and I will be able to do other AOSP roms. From my quick research it seems like it's fine, but I only have 20 minutes left to get it friday instead of monday, so I figured I would just ask to be safe.
failedjedi said:
So as some of you may know the S4 had it's exploit fixed and since then we haven't been able to get away from Touchwiz based roms.
Before I go get the G3 I just wanted to be 100% clear that even the latest firmware hasn't fixed Bump, and I will be able to do other AOSP roms. From my quick research it seems like it's fine, but I only have 20 minutes left to get it friday instead of monday, so I figured I would just ask to be safe.
Click to expand...
Click to collapse
AT&T released firmware Build number: KVT49L.D85010f to patch root exploit. Read this thread
http://forum.xda-developers.com/att-lg-g3/general/d850-software-update-t2937550
When Android Lollipop rolls out to G3 in the near future, rooting will be harder to accomplish. Same for other brands.
hwong96 said:
AT&T released firmware Build number: KVT49L.D85010f to patch root exploit. Read this thread
http://forum.xda-developers.com/att-lg-g3/general/d850-software-update-t2937550
When Android Lollipop rolls out to G3 in the near future, rooting will be harder to accomplish. Same for other brands.
Click to expand...
Click to collapse
But that is recent enough that a phone bought today will not come with it out of the box, so I'm not worried about that.
And in theory I can just flash a bumped lollipop build later anyway right?
I just want to make sure it's not in the same current state as the S4 where you have to have touchwiz and match roms to bootloader version and what not.
I know there isn't too many roms yet with bump being fairly new, but as long as I stay on the current build I should be fine going forward no?
And I guess on that note, the stock rom isn't nearly as bad touchwiz is it?
failedjedi said:
But that is recent enough that a phone bought today will not come with it out of the box, so I'm not worried about that.
And in theory I can just flash a bumped lollipop build later anyway right?
I just want to make sure it's not in the same current state as the S4 where you have to have touchwiz and match roms to bootloader version and what not.
I know there isn't too many roms yet with bump being fairly new, but as long as I stay on the current build I should be fine going forward no?
And I guess on that note, the stock rom isn't nearly as bad touchwiz is it?
Click to expand...
Click to collapse
Yes, yes and Lg is better than TW imo.
hwong96 said:
Yes, yes and Lg is better than TW imo.
Click to expand...
Click to collapse
Cool, I went for it, thanks for the quick clarifications. I can read all about everything now while I impatiently wait for UPS friday.
with LG phones you can always downgrade the software to a version where you can root.
I am sure there will be a way to get official lollipop while keeping custom recovery and root.
Once again, LG locked the door but forgot to close it before locking like what they did on the G2. So we were still able to upgrade while keeping custom recovery and root by mixing and matching partitions from upgrade and previous versions.
I am on 4.16.401.10 Is this the current build? If not what is the current and are they incremental? I am S-OFF and rooted using Venom rom. Thanks!
That rom isn't based off Verizon software. .401 is international build. Are you asking if you are up to date on firmware? If so, boot to your boot loader and tell me the os version listed there.
I have OS version 4.17.605.5
Your version of firmware is 4.17.605.5. These most recent that I am aware of, is 4.17.605.9 . The person that posted before you, dottat, and whom I have great personal respect for, is the dev that brought us this FW. It includes the patch for stagefright. I have been running it now fort a few days with lollisense ROM (I too like venom, I currently have 4.6.0 in multi ROM but have not yet booted it). Will probably do that now that you have reminded me by way of this post.
Anyways the firware you want can be found here. Be sure to thank dottat (and the other dev's out there as well) for his hard work at keeping our devices running smoothly and helping out from time to time when we run into trouble.
Good luck
This is not a 'best ROM' thread, simply a request for assistance.
My friend experienced abysmal battery life when her phone updated to the (stock) Lollipop ROM. I rooted it, installed Multirom and flashed a Kit Kat ROM for her, which means she could actually use her phone for more than 7hrs without it dying.
Now Marshmallow is out I want to give her a secondary ROM to test out. But I don't see her that often and I want a ROM that offers auto-updates so that so long as the dev releases delta updates then she'll get them. This is to assuage my concern regarding her going for the next year with no security updates.
1. Can anyone recommend a MM ROM that has this feature?
2. Is there any reason why Multirom would interfere with an update system like this?
Thanks.
Sent from my Nexus 5 using Tapatalk
Why would you install MM on a device that belongs to someone else?
a hammerhead wrote this.
I'm struggling to understand the question. If your friend isn't technically able, then surely the simple course is to wipe and install MM, leave it stock, and she'll get all the Android OTA updates as they arrive. Is this not exactly what you want? Why over-complicate her life with multiple ROMs?
Just asking...
Hey guys! So I have a few questions about the oneplus one here, I'm checking for a friend and I always had a nexus where matching firmware doesn't really matter much. So here they are.
1) What happens if you have the wrong firmware for a rom? Softbrick? Hardbrick? Nothing at all?
2) For a Nougat rom, what firmware do you use? Since this phone hasn't got an official firmware update for Nougat yet.
3) Is there a special recovery here on XDA that can flash all roms? (there was one for the oneplus two) or is TWRP good for all roms?
What confuses me the most about oneplus devices is how the firmware works different from most Android devices. Thanks guys!
H4X0R46 said:
Hey guys! So I have a few questions about the oneplus one here, I'm checking for a friend and I always had a nexus where matching firmware doesn't really matter much. So here they are.
1) What happens if you have the wrong firmware for a rom? Softbrick? Hardbrick? Nothing at all?
2) For a Nougat rom, what firmware do you use? Since this phone hasn't got an official firmware update for Nougat yet.
3) Is there a special recovery here on XDA that can flash all roms? (there was one for the oneplus two) or is TWRP good for all roms?
What confuses me the most about oneplus devices is how the firmware works different from most Android devices. Thanks guys!
Click to expand...
Click to collapse
1)I tried all below firmware, nothing wrong happens, I cannot identify any differences. I'm now just use the stock firmware: DI.3.0.c6
* http://forum.xda-developers.com/oneplus-one/general/firmware-modem-oneplus-one-lollipop-t3300907
** actually this post copy the exact my same post from "cyanogenmod forum"
bacon_firmware_update_2015_05-15_DI.3.0.c6-00241.zip <--- Currently bundled with latest CM13 nightly
bacon_firmware_update_2015_10-15_.4.0.1.c7-00013.zip
bacon_firmware_update_2015_12-30_.4.0.1.c7-00011.zip
bacon_firmware_h2os_update_2015_12-30_.4.0.1.c1.11-00004.zip
bacon_firmware_oxygen_update_2016_01_22_.4.0.1.c7-00013
bacon_firmware_update_2016_1-25_.4.0.1.c7-00011.zip
2)I'm now using ROM: "lineage-14.1-20170126-Okeys-bacon" from https://forum.xda-developers.com/oneplus-one/development/rom-unofficial-okeys-builds-t3534899
* it provide firmware "DI.3.0.c6" by default
3)TWRP is preferred, it is powerful and support for all ROMs
xiaoguazh said:
1)I tried all below firmware, nothing wrong happens, I cannot identify any differences. I'm now just use the stock firmware: DI.3.0.c6
* http://forum.xda-developers.com/oneplus-one/general/firmware-modem-oneplus-one-lollipop-t3300907
** actually this post copy the exact my same post from "cyanogenmod forum"
bacon_firmware_update_2015_05-15_DI.3.0.c6-00241.zip <--- Currently bundled with latest CM13 nightly
bacon_firmware_update_2015_10-15_.4.0.1.c7-00013.zip
bacon_firmware_update_2015_12-30_.4.0.1.c7-00011.zip
bacon_firmware_h2os_update_2015_12-30_.4.0.1.c1.11-00004.zip
bacon_firmware_oxygen_update_2016_01_22_.4.0.1.c7-00013
bacon_firmware_update_2016_1-25_.4.0.1.c7-00011.zip
2)I'm now using ROM: "lineage-14.1-20170126-Okeys-bacon" from https://forum.xda-developers.com/oneplus-one/development/rom-unofficial-okeys-builds-t3534899
* it provide firmware "DI.3.0.c6" by default
3)TWRP is preferred, it is powerful and support for all ROMs
Click to expand...
Click to collapse
Thanks! So it's not as important as it seems? I notice some roms here on XDA specifically say to have the newest firmware, or a certain version. The rom is still expected to boot? And what's the worst case scenario? A soft brick that can be easily fixed with TWRP or something worse? Thanks for the reply! Like I said, I'm coming from a Nexus 6 where none of this firmware stuff really applies :angel:
H4X0R46 said:
Thanks! So it's not as important as it seems? I notice some roms here on XDA specifically say to have the newest firmware, or a certain version. The rom is still expected to boot? And what's the worst case scenario? A soft brick that can be easily fixed with TWRP or something worse? Thanks for the reply! Like I said, I'm coming from a Nexus 6 where none of this firmware stuff really applies :angel:
Click to expand...
Click to collapse
Yes the rom is a still expected to boot,though,the recommended frimware is to be used so as to avoid any bugs.
However,some roms do require the recommended frimware in order to boot but I don't think even if flash any rom which needs recommended frimware will take you in any kind of brick condition as when you flash a rom on incompatible frimware you'll see error in Twrp,if so happens you just need to have recommended frimware in your storage and flash it then flash the rom again and you'll not face any errors.
Good luck!
H4X0R46 said:
Hey guys! So I have a few questions about the oneplus one here, I'm checking for a friend and I always had a nexus where matching firmware doesn't really matter much. So here they are.
1) What happens if you have the wrong firmware for a rom? Softbrick? Hardbrick? Nothing at all?
2) For a Nougat rom, what firmware do you use? Since this phone hasn't got an official firmware update for Nougat yet.
3) Is there a special recovery here on XDA that can flash all roms? (there was one for the oneplus two) or is TWRP good for all roms?
What confuses me the most about oneplus devices is how the firmware works different from most Android devices. Thanks guys!
Click to expand...
Click to collapse
1. If you are using TWRP, nothing will happens. Because when you flash a ROM, TWRP will comparing your phone model with build.prop on the targeted ROM. Because based on my experience, somehow i download LineageOS for d802 and flash it to my bacon. TWRP gives an error and didn't flash any firmware. I don't know about CWM or other recovery
2. I'm using Lineage OS. It's pretty good so far. No bug or whatever
3. TWRP is good for all ROM. i think any recovery will do