Hi everyone, quick newbie question for you if you could be kind enough to answer it.
Yesterday I managed my first root and flash. My aim was to install the latest version of cyanogen on my s3, and following a tutorial everything went well, I'm now rocking kit kat. The only problem is that I've just realised I installed a sspencer10 Rom, which have since been discontinued, meaning I'm not going to get any updates, and there are some more stable snapshots that have been released on the official cyanogen site since that discontinuation.
I thought it would be easy to remedy: just flash an official Rom, just like I flashed the sspencer10 one yesterday - but the cyanogen install guide has this warning: 'you must be a 4.2.2 or older build or this will not work. In fact, if you try to use this method on a newer revision, you will almost certainly brick your device. Seriously don't try it. Downgrading won't work either. If you've updated, a qfuse is already tripped and any attempt to downgrade will also result in a brick.'
I'm hoping they mean that about stock upgrades and not cyanogen ROMs, but they don't say anything about that.
Can I flash a new cyanogen without bricking?
Thanks!
Noam Chomsky said:
Hi everyone, quick newbie question for you if you could be kind enough to answer it.
Yesterday I managed my first root and flash. My aim was to install the latest version of cyanogen on my s3, and following a tutorial everything went well, I'm now rocking kit kat. The only problem is that I've just realised I installed a sspencer10 Rom, which have since been discontinued, meaning I'm not going to get any updates, and there are some more stable snapshots that have been released on the official cyanogen site since that discontinuation.
I thought it would be easy to remedy: just flash an official Rom, just like I flashed the sspencer10 one yesterday - but the cyanogen install guide has this warning: 'you must be a 4.2.2 or older build or this will not work. In fact, if you try to use this method on a newer revision, you will almost certainly brick your device. Seriously don't try it. Downgrading won't work either. If you've updated, a qfuse is already tripped and any attempt to downgrade will also result in a brick.'
I'm hoping they mean that about stock upgrades and not cyanogen ROMs, but they don't say anything about that.
Can I flash a new cyanogen without bricking?
Thanks!
Click to expand...
Click to collapse
You're right, they're talking about flashing a ROM from the new stock 4.3 software, not if you've already successfully rooted, flashed a custom recovery, and flashed a ROM. You'll be fine, just do a factory reset/wipe before flashing.
It's a little strange that they'd mention 4.2.2, since the S3 never had an official 4.2.x release from Samsung, we went straight from 4.1.2 to 4.3.
Brilliant, thanks so much Jacquestrapp. Downloading that snapshot now - hoping for a bit more stability!
Yup, all worked perfectly - just tried recreating crashes that were happening in the earlier rom and I can definitely say the update is a huge improvement on stability. Just hoping that impression lasts! If necessary there shouldn't be any trouble with downgrading to cyanogen 10, right?
Noam Chomsky said:
Yup, all worked perfectly - just tried recreating crashes that were happening in the earlier rom and I can definitely say the update is a huge improvement on stability. Just hoping that impression lasts! If necessary there shouldn't be any trouble with downgrading to cyanogen 10, right?
Click to expand...
Click to collapse
Right. Actually there is a fairly recent stable version of CM10, 10.2.1, released just last month.
Noam Chomsky said:
Yup, all worked perfectly - just tried recreating crashes that were happening in the earlier rom and I can definitely say the update is a huge improvement on stability. Just hoping that impression lasts! If necessary there shouldn't be any trouble with downgrading to cyanogen 10, right?
Click to expand...
Click to collapse
I don't think you'll need to downgrade, I'm running the latest of the CM nightlies and, so far, it's good. There were some problems with the camera, WiFi, etc. with the earlier nightlies but they seem to be all worked out and CM 11 is my daily driver now. Hope it works as well for you.
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
Hey guys!
I still havent installed android 4.4.3 in my nexus. Reading in different websites I've seen there are many bugs so I was wondering whether it is worth it to upgrade or whether I should stick with android 4.4.2 for now.
Cheers!
nad4321 said:
Hey guys!
I still havent installed android 4.4.3 in my nexus. Reading in different websites I've seen there are many bugs so I was wondering whether it is worth it to upgrade or whether I should stick with android 4.4.2 for now.
Cheers!
Click to expand...
Click to collapse
always better to upgrade, it includes several fixes that are really helpful.
If you're afraid that you might get any bugs (but I don't think that you will) you could flash the whole stock 4.4.3 image and start from scratch.
Sent from my Nexus 5 using Tapatalk
nad4321 said:
Hey guys!
I still havent installed android 4.4.3 in my nexus. Reading in different websites I've seen there are many bugs so I was wondering whether it is worth it to upgrade or whether I should stick with android 4.4.2 for now.
Cheers!
Click to expand...
Click to collapse
Many of those bugs and issues are isolated cases. Personally I'd rather upgrade to an OS that has more fixes, is less Bugless should be more stable.
I'm on the DIrty Unicors 4.4.3 build with Franco R53 kernel and my N5 is performing fantastic. Smooth, stabile, seems even faster, and more fluid transitions. I also flashed the new modem/radio (wasn't in the DU 4.4.3 build) and not that I even had an issue with the last radio, but this one seems to be working great for me on MetroPCS. I'm getting more bars and LTE reception in areas that usually struggle with singnal and my WiFi to data transition seems quicker to.
No to mention that there are all the modems/radios I. A flashable zip through a custom recovey and then you can test to see which one works be for you.
On the other hand... If you find that you don't like it (which I doubt) try a custom 4.4.3 ROM.
I f you have one you could always just reflash a nandroid backup to a previous version 4.4.2
You could also always flash back the stock images to 4.4.2 using the same method that you upgraded to 4.4.3 and there's other method you can do this way without losing user data.
Upgrade and enjoy the latest and greatest on your Nexus5!
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.
We need to know the status about the android lollipop, the google play edition is not enough, though the only variant which received or started receiving android lollipop is XT1033, if anyone knows what is the current status, please confirm. And one last thing why there is no roms developed in AOSP not CM as CM is currently buggy, and not stable.
Rostomania said:
We need to know the status about the android lollipop, the google play edition is not enough, though the only variant which received or started receiving android lollipop is XT1033, if anyone knows what is the current status, please confirm. And one last thing why there is no roms developed in AOSP not CM as CM is currently buggy, and not stable.
Click to expand...
Click to collapse
Your questions have been asked and answered already throughout the forums; besides, this is the wrong section. But anyways, XT1033 got 5.0.0 soak test and it looks like it's getting 5.0.1 official OTA as we speak. GPe got 5.0.1 official OTA aswell. You can install both of these firmwares on your phone if you do not like AOSP roms; these, to start, are not "buggy", they are almost as stable as the official. And if they have bugs it is because we don't have moto's official lollipop source yet, and most ROMs just use CMs source without modifying it, and it hasn't been updated in a while now.
anerik said:
Your questions have been asked and answered already throughout the forums; besides, this is the wrong section. But anyways, XT1033 got 5.0.0 soak test and it looks like it's getting 5.0.1 official OTA as we speak. GPe got 5.0.1 official OTA aswell. You can install both of these firmwares on your phone if you do not like AOSP roms; these, to start, are not "buggy", they are almost as stable as the official. And if they have bugs it is because we don't have moto's official lollipop source yet, and most ROMs just use CMs source without modifying it, and it hasn't been updated in a while now.
Click to expand...
Click to collapse
Am sorry I posted wrong section, my bad, please move to the right section, and thanks for the reply ...
Hello, it's been some time since I've last rooted and flashed kernels on my devices. My device is having problems with certain apps and I feel it's time to update my root or change my rom or flash a stock rom etc. Here is what I am using now:
Build: MOAR v6.1 OA6
Software: G900PVPU1BOA6
Hardware: G900P.04
Android: 5.0
Kernel: 3.4.0-3859396
Would you recommend I unroot then flash a stock kernel? What is a new root I can use with this phone? Thanks
I would recommend Odin a fresh stock MM rom. Then boot to the desktop, by pass set up. Go to dialer ##72786# it will do a reactivate and update prl and profile.. Then Odin TWRP, and flash a new rom or your choice.. If you like MOAR then Odin a LP stock rom, and do as mentioned and flash MOAR 7.0 it works best. Right now, I'm running crdroid 3.8.5 baset off of Nouget with 7.1 gapps and it works very well You need the latest MM firmware to run it, and at least TWRP 3.2.1-0-ktle.img If you do flash crdroid download ktledv
https://forum.xda-developers.com/galaxy-s5/unified-development/rom-crdroid-t2860894
First off, thanks for the reply. I really appreciate the help. What's the battery life like on MM compared to Lollipop?
I would prefer to use something like a stock rom but just extremely debloated. I also want to be able to play pokemom go without problems and super su keeps giving me problems when trying to play. Do you know of any setups that would allow for pokemon go and are fast, battery effecient, and debloated?
doubledragon5 said:
I would recommend Odin a fresh stock MM rom. Then boot to the desktop, by pass set up. Go to dialer ##72786# it will do a reactivate and update prl and profile.. Then Odin TWRP, and flash a new rom or your choice.. If you like MOAR then Odin a LP stock rom, and do as mentioned and flash MOAR 7.0 it works best. Right now, I'm running crdroid 3.8.5 baset off of Nouget with 7.1 gapps and it works very well You need the latest MM firmware to run it, and at least TWRP 3.2.1-0-ktle.img If you do flash crdroid download ktledv
https://forum.xda-developers.com/galaxy-s5/unified-development/rom-crdroid-t2860894
Click to expand...
Click to collapse
How's the mm baseband? I know the obvious response is updated is better but I experienced better LTE on the firmware I currently have, no idea honestly other than it's lolipop, maybe ok4? I want to upgrade phones but having trouble finding one with sprint newer that can be customized how I like so I'm also looking at playing with this one prior to and after getting maybe a pixel unlocked
andrew2432 said:
How's the mm baseband? I know the obvious response is updated is better but I experienced better LTE on the firmware I currently have, no idea honestly other than it's lolipop, maybe ok4? I want to upgrade phones but having trouble finding one with sprint newer that can be customized how I like so I'm also looking at playing with this one prior to and after getting maybe a pixel unlocked
Click to expand...
Click to collapse
I would stick with Lollipop OK4 and flash MOAR 7.0. I to find better LTE and all around connectivity on Lollipop than MM.. I once again, went back to MOAR 7.0 from crdroid.. Crdroid is a great rom, but battery life, sucks, as well as connectivity on calls and data. When in aroma and you get to the point about the kernel, choose don't touch kernel, and finish from there. I never like MM and those are the reasons why.. Crdroid I flashed was 7.0 but naturally on the MM base band, but it was still the same.
Thanks sir nobody could really answer that for me. I found the ok4 of all lollipop got the best LTE where I live, plus I'm on sprint so I'm a bit restricted on ROMs, unified dev leave some bugs with sprints network but not too badly!!
andrew2432 said:
Thanks sir nobody could really answer that for me. I found the ok4 of all lollipop got the best LTE where I live, plus I'm on sprint so I'm a bit restricted on ROMs, unified dev leave some bugs with sprints network but not too badly!!
Click to expand...
Click to collapse
You probably already know, but I will ask anyways. Are you using the KLTEDV version of the unified ROM? KLTE roms does not work very well with sprint.
Fear_The_Fluff said:
You probably already know, but I will ask anyways. Are you using the KLTEDV version of the unified ROM? KLTE roms does not work very well with sprint.
Click to expand...
Click to collapse
Thanks! I'll make sure to read which I should use. My daily is still on MM while my old one that's kinda beat up is now on N as it us now the practice phone. Playing with it before Oreo, may stay for a while. And I installed kltespr on both devices as there were still options available for specifically this device with the spr tag. My CM 13 network is fine, no worse than just regular sprint...
Haven't tried the move to either N or O on my daily, worried about the signal discussion. I'll use an old kltespr to test before the newer maintained kltedv if its there probably to see how it goes.
Fear_The_Fluff said:
You probably already know, but I will ask anyways. Are you using the KLTEDV version of the unified ROM? KLTE roms does not work very well with sprint.
Click to expand...
Click to collapse
Delete
andrew2432 said:
Thanks! I'll make sure to read which I should use. My daily is still on MM while my old one that's kinda beat up is now on N as it us now the practice phone. Playing with it before Oreo, may stay for a while. And I installed kltespr on both devices as there were still options available for specifically this device with the spr tag. My CM 13 network is fine, no worse than just regular sprint...
Haven't tried the move to either N or O on my daily, worried about the signal discussion. I'll use an old kltespr to test before the newer maintained kltedv if its there probably to see how it goes.
Click to expand...
Click to collapse
Unfortunately my sprint s5 is one of the phone with that signal issue. I was in the process of changing carrier so to try and fix that issue wasn't worth it for me. My new S5 did not have that issue, when i went to verizon, its a really weird bug.
Fear_The_Fluff said:
Unfortunately my sprint s5 is one of the phone with that signal issue. I was in the process of changing carrier so to try and fix that issue wasn't worth it for me. My new S5 did not have that issue, when i went to verizon, its a really weird bug.
Click to expand...
Click to collapse
I think it took a bit to stat with the sprint APN, changed some settings, messed with some stuff, and it seems fine now, I'll have to remember to check back at that before upgrading. I'm on the ok4 baseband