Related
I have an SGH-I337 running UCUAMDB that I've rooted, TWRP'd, etc. via CASUAL 527b. Are there any downsides to upgrading to whatever the current AT&T ROM version is? I just got notified of a new version which I assume fixes the package signing vulnerability that affects all versions of Android 1.6+, which would be a good thing.
Thank you in advance to those of you who weigh in.
You'd lose your root until an exploit is released for the current update.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=2357272
Fat Rat Bastard said:
I have an SGH-I337 running UCUAMDB that I've rooted, TWRP'd, etc. via CASUAL 527b. Are there any downsides to upgrading to whatever the current AT&T ROM version is? I just got notified of a new version which I assume fixes the package signing vulnerability that affects all versions of Android 1.6+, which would be a good thing.
Thank you in advance to those of you who weigh in.
Click to expand...
Click to collapse
HiTideBlastoise said:
You'd lose your root until an exploit is released for the current update.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Kadin said:
http://forum.xda-developers.com/showthread.php?t=2357272
Click to expand...
Click to collapse
Both posts are correct. You will lose TWRP, and Root.
If you want you can flash just the modem. http://forum.xda-developers.com/showthread.php?p=43432287#post43432287
If you want the newest firmware, I highly recommend running GoldenEye Rom. It is based on the International version of the rom they just released for the US variants basically. So you will get the new features and fixes, and still be rooted. (they had it 1-2 weeks ago for other versions). You can flash/try GoldenEye and flash the modem in the link and be all up to date and rooted on stock based firmware.
WoodburyMan said:
Both posts are correct. You will lose TWRP, and Root.
If you want you can flash just the modem. http://forum.xda-developers.com/showthread.php?p=43432287#post43432287
If you want the newest firmware, I highly recommend running GoldenEye Rom. It is based on the International version of the rom they just released for the US variants basically. So you will get the new features and fixes, and still be rooted. (they had it 1-2 weeks ago for other versions). You can flash/try GoldenEye and flash the modem in the link and be all up to date and rooted on stock based firmware.
Click to expand...
Click to collapse
I'm sure there is pros & cons to go back to the stone age but I can't see it!
YOU can have the best of both worlds by...
Rooting
getting a good stable rom.. (many to choose from)
installing latest TWRP or what ever is your choice for recoveries
latest kernel (remember for your phone model)
latest modem...
and remember thats not taking any OTA's
or you could let the carriers control your life.. Heh, heh..
its all your choice!
Now that the OTA has locked everyone up or those of us that got a device that didn't have the chance to unlock the bootloader, do most/some/all/etc roms that we have for the Razr M work with Safestrap?
Sorry if this is posted elsewhere but I didn't see it and only saw mention of roms having to be compatible with it
collins521 said:
Now that the OTA has locked everyone up or those of us that got a device that didn't have the chance to unlock the bootloader, do most/some/all/etc roms that we have for the Razr M work with Safestrap?
Sorry if this is posted elsewhere but I didn't see it and only saw mention of roms having to be compatible with it
Click to expand...
Click to collapse
I don't know the exact roms, but I know there are a few. Since the bootloader was unlocked though, the development for safestrap roms has slowed or stopped. Check in the Android Development section and scroll through for the safestrap roms. I believe they were 4.1.2 roms only, but don't quote me on that.
Sent from my Droid Razr M using xda app-developers app
Jersey846 said:
I don't know the exact roms, but I know there are a few. Since the bootloader was unlocked though, the development for safestrap roms has slowed or stopped. Check in the Android Development section and scroll through for the safestrap roms. I believe they were 4.1.2 roms only, but don't quote me on that.
Sent from my Droid Razr M using xda app-developers app
Click to expand...
Click to collapse
ROMs developed for SS stopped at 4.1.1, meaning that there not any 4.1.2 custom ROMs available. bootloader was unlocked prior to 4.1.2 rolling out.
there might be a way to convert them to SS though - I know that a dev was able to convert a SS ROM to TWRP flashable recovery, so perhaps he might be able to do the reverse.
jco23 said:
ROMs developed for SS stopped at 4.1.1, meaning that there not any 4.1.2 custom ROMs available. bootloader was unlocked prior to 4.1.2 rolling out.
there might be a way to convert them to SS though - I know that a dev was able to convert a SS ROM to TWRP flashable recovery, so perhaps he might be able to do the reverse.
Click to expand...
Click to collapse
I believe DeadCalm was updated to 4.1.2. Also, Eclipse v1.2 is still SS compatible but it leans more heavily on AOSP styling.
SS compatible ROMs:
-Early builds of CM10 (way early, like at the beginning of thread early)
-DeadCalm was SS enabled, not sure if it was modified for an unlocked bootloader only
-Energy is SS enabled and never altered for unlocked bootloader
-Flying Jelly was SS enabled and I don't think it was modified to work only on an unlock bootloader
-Eclipse v1.2 was SS enabled, I don't think it was modified for unlocked bootloader
RikRong said:
I believe DeadCalm was updated to 4.1.2. Also, Eclipse v1.2 is still SS compatible but it leans more heavily on AOSP styling.
SS compatible ROMs:
-Early builds of CM10 (way early, like at the beginning of thread early)
-DeadCalm was SS enabled, not sure if it was modified for an unlocked bootloader only
-Energy is SS enabled and never altered for unlocked bootloader
-Flying Jelly was SS enabled and I don't think it was modified to work only on an unlock bootloader
-Eclipse v1.2 was SS enabled, I don't think it was modified for unlocked bootloader
Click to expand...
Click to collapse
yeah, but those are all 4.1.1 ROMs - and I'm fairly certain deadcalm is unlocked bootloader only, as it was created for just 4.1.2.
but I really don't think it matters much anymore - Motorola has been quite diligent on providing updates, so I would not be surprised to see an official 4.2.2 release by the end of this year, with a 4.3 release by next summer.
jco23 said:
yeah, but those are all 4.1.1 ROMs - and I'm fairly certain deadcalm is unlocked bootloader only, as it was created for just 4.1.2.
but I really don't think it matters much anymore - Motorola has been quite diligent on providing updates, so I would not be surprised to see an official 4.2.2 release by the end of this year, with a 4.3 release by next summer.
Click to expand...
Click to collapse
Yeah, you're right on all those being 4.1.1, but I was just throwing out some options. Personally, I think very few of the devs, if any, will develop for SS. Sure, the people that are getting new phones or maintenance replacements are hosed. However, people that owned the phone and decided to install the update and not unlock their bootloader? Well, it's their own fault. They've been warned for 4 months that the patch could be locked. Look what happened, it was locked. The one thing the devs could do, that would be fairly easy, is just update the older SS ROMs to the newer OTA. That would help out a lot of people.
RikRong said:
Yeah, you're right on all those being 4.1.1, but I was just throwing out some options. Personally, I think very few of the devs, if any, will develop for SS. Sure, the people that are getting new phones or maintenance replacements are hosed. However, people that owned the phone and decided to install the update and not unlock their bootloader? Well, it's their own fault. They've been warned for 4 months that the patch could be locked. Look what happened, it was locked. The one thing the devs could do, that would be fairly easy, is just update the older SS ROMs to the newer OTA. That would help out a lot of people.
Click to expand...
Click to collapse
100% agreed on the warnings - but I also understand why folks may have been skittish beforehand (took me 3 months of reading before I rooted my first device). given that this phone is now offered for free, I can see many new folks to this community, but they'll be SOL unless we are blessed with the help from a dev to unlock their bootloader.
that being said, the devs are not required to create a hack or make their ROMs SS-compatible, but I would not be surprised if locked bootloader phones soon begin to outnumber the locked one. i'm just thankful that they are here.
To be fair, the droid razr m that I'm working on has its bootloader locked because my girlfriend is skittish about me touching her phone. Women
I could barely even get any to work when they were still developing SS Roms, so goodluck... Never accept OTA's...
AK47sForAll said:
I could barely even get any to work when they were still developing SS Roms, so goodluck... Never accept OTA's...
Click to expand...
Click to collapse
Unfortunately the one I have had the OTA already downloaded so I didn't even get a chance to unlock the bootloader...been trying to find a white one at a reasonable price and haven't' had much luck
collins521 said:
Unfortunately the one I have had the OTA already downloaded so I didn't even get a chance to unlock the bootloader...been trying to find a white one at a reasonable price and haven't' had much luck
Click to expand...
Click to collapse
What do you consider reasonable? And have you tried eBay?
AK47sForAll said:
What do you consider reasonable? And have you tried eBay?
Click to expand...
Click to collapse
Ya I've been watching eBay and other sites for a good deal on a white one. Under $200 and in great shape is where I'm looking to get one. I'm in no real rush so I can wait for a deal to pop up
http://www.droidrzr.com/index.php/t...calm-v14-7172013-412-base/page-30#entry333531
That being said.
An activated DC is a path to this & you take your data with you.
http://forum.xda-developers.com/showthread.php?t=2246081
Edit Yet this is a backup made by the full twrp. Yet again they are supposed to be compatible....
Who shall be the first to build ?
The race is on
Buahahhahahhaha
Sent from my LG-D851 using Tapatalk
brolic925t said:
Who shall be the first to build ?
The race is on
Buahahhahahhaha
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Source ?
Sent from my LG-D852 using XDA Free mobile app
shahkam said:
Source ?
Sent from my LG-D852 using XDA Free mobile app
Click to expand...
Click to collapse
http://www.androidpolice.com/2014/1...roid-5-0-lollipop-source-code-aosp-right-now/
I'm OK now, I'm happy to have waited this long for an AOSP ROM.
I can wait longer if it becomes a L ROM for our G3!!
Great news !
it's hard to say...i'm working on a lollypop port since weeks now and the main problem is a kernel panic related to the modem resetting.. i think that once i will figure out how to solve it i will be able to release a first beta
It is usually very hard to get new android versions ported to a device where there is no official rom of the same version for it - you basically are going in blind trying to get all the hardware to work.
If we are lucky we might see one or two builds before LG release theirs (which is now less than 2 months away!) but I would expect them to be buggy with some hardware not working - so far we don't even have a fully working Kitkat AOSP build for our device.
manups4e said:
it's hard to say...i'm working on a lollypop port since weeks now and the main problem is a kernel panic related to the modem resetting.. i think that once i will figure out how to solve it i will be able to release a first beta
Click to expand...
Click to collapse
good luck bro!!! lets see if you can beat LG to the draw...
please keep us posted!!!
Thanks in advance
Deeemm79 said:
good luck bro!!! lets see if you can beat LG to the draw...
please keep us posted!!!
Thanks in advance
Click to expand...
Click to collapse
if someone would like to help here is last_kmsg at the very end you'll find the kernel panic about modem
bah, who needs the LG Lollipop rom? probably gonna have their own skin again which, in my opinion, is inferior to stock lollipop. plus, if you have not read, Android 5.0 Lollipop gives developers the option to completely lockdown devices and prevent root, specifically in our devices where bootloader is not unlockable. Don't think I'll take the risk though. It's a huge one!
http://www.xda-developers.com/android/android-l-lockdown/
Oooh. I so happy. ????
jayzhoukj said:
bah, who needs the LG Lollipop rom? probably gonna have their own skin again which, in my opinion, is inferior to stock lollipop. plus, if you have not read, Android 5.0 Lollipop gives developers the option to completely lockdown devices and prevent root, specifically in our devices where bootloader is not unlockable. Don't think I'll take the risk though. It's a huge one!
http://www.xda-developers.com/android/android-l-lockdown/
Click to expand...
Click to collapse
this is true although (and i may well be wrong) i would presume this would only apply if you take the update from OEM and not custom rom .... if we take a flashable custom rom i would assume that this lockdown is completely irrelevant and fairly risk free providing the devs can get all the hardware side of things up and running
ah yes, you are right. personally though i would prefer to go straight to stock rom after rooting. not really sure what the difference is (if any big changes) between a rooted and non-rooted stock rom
jayzhoukj said:
ah yes, you are right. personally though i would prefer to go straight to stock rom after rooting. not really sure what the difference is (if any big changes) between a rooted and non-rooted stock rom
Click to expand...
Click to collapse
that all depends what you want to be able to do on your device ..... without root you cannot use xposed (although until made to run on ART it wont work with lollipop onwards ) ... you need root to delete / modify any / all system apps and other tweaks under the hood ..... there are many things you could need root for
jayzhoukj said:
not really sure what the difference is (if any big changes) between a rooted and non-rooted stock rom
Click to expand...
Click to collapse
Root alone does nothing. It's what you do with the elevated privileges that matters. With root access, you pretty much have complete control over the phone's software, so you can do next to nothing, or completely overhaul everything to the point where it is indistinguishable from a stock, non-modified phone.
By the way... If LG isn't blowing smoke up our backsides, we'll have a working Optimus UI w/ 5.0.. guessing 6 weeks, give or take. And it remains to be seen how quickly they release their sources. Until those sources are released, any 5.0 custom ROMs are going to be Lollipop on top of LG's KK stuff (kernel, radio/modem, graphics drivers, etc). Not sure how stable that will all be. My only experience with a phone running a ROM like that was running early KK builds on my old Galaxy S3, which was Android 4.4 built on top of Samsung's Jelly Bean stuff. And that was buggy as hell, tons of problems. Basic stuff, like every time it switched from Wi-Fi to mobile data, I got a kernel panic and it would reboot.
So I would be wary of any LP ROMs for the G3 that didn't include the native LP stuff from LG.
LeoRex said:
Root alone does nothing. It's what you do with the elevated privileges that matters. With root access, you pretty much have complete control over the phone's software, so you can do next to nothing, or completely overhaul everything to the point where it is indistinguishable from a stock, non-modified phone.
By the way... If LG isn't blowing smoke up our backsides, we'll have a working Optimus UI w/ 5.0.. guessing 6 weeks, give or take. And it remains to be seen how quickly they release their sources. Until those sources are released, any 5.0 custom ROMs are going to be Lollipop on top of LG's KK stuff (kernel, radio/modem, graphics drivers, etc). Not sure how stable that will all be. My only experience with a phone running a ROM like that was running early KK builds on my old Galaxy S3, which was Android 4.4 built on top of Samsung's Jelly Bean stuff. And that was buggy as hell, tons of problems. Basic stuff, like every time it switched from Wi-Fi to mobile data, I got a kernel panic and it would reboot.
So I would be wary of any LP ROMs for the G3 that didn't include the native LP stuff from LG.
Click to expand...
Click to collapse
infact since 1 month i'm trying to port lollypop and i'm blocked by kernel panic at boot due to modem resetting
My concern is for our d850 development .... It will pick up im guessing
2SHAYNEZ
OEM Unlock feature in Lollipop dev options
Lollipop has an OEM Unlock feature in the development options. Chainfire already utilized it to root the N9. See attached.
so excited in looking forward to your effort - friends....
hwong96 said:
Lollipop has an OEM Unlock feature in the development options. Chainfire already utilized it to root the N9. See attached.
Click to expand...
Click to collapse
OEM unlock meaning ?
I just received the update for Fire OS 5!!
It is FIRE OS 5.0.3 (532008220)
First findings:
ADB is still buggy. (firestarter gives an error. ADB needs to be pushed off/on to get it working.)
Audio passthrough in Kodi is not working. (same as in the Fire OS5 preview)
Lol, is anything actually fixed?
Sent from my SM-N9005 using Tapatalk
Don't even try updating until the stable official version is released. Everything is beta right now
I also got OS 5.0.3 update. The good news is that it includes Alexa and many voice functions work now. 5.0 was incredibly slow and buggy for me. 5.0.3 seems more responsive but that may be because I had to do a factory reset in order to upgrade successfully.
solorzano_felipe said:
Don't even try updating until the stable official version is released. Everything is beta right now
Click to expand...
Click to collapse
This is the official version, so it is not a beta anymore. Whether or not it is stable we shall see:
http://www.aftvnews.com/fire-os-5-public-software-update-makes-first-appearance/
Edit: actually it is confusing if OP got official OS 5 or just an update to the developer preview.
jpeg42 said:
This is the official version, so it is not a beta anymore. Whether or not it is stable we shall see:
http://www.aftvnews.com/fire-os-5-public-software-update-makes-first-appearance/
Edit: actually it is confusing if OP got official OS 5 or just an update to the developer preview.
Click to expand...
Click to collapse
It seems like this is a beta just for those who have the developer preview installed. I agree, it's a bit confusing, especially since it looks like the official version will be 5.0.2 while this possibly beta version is 5.0.3. But I haven't heard of anyone NOT running the developer preview that received the update, which is why I wrote that it's a developer preview update. I'm sure we'll know more as more devices get updated.
Hi all,
seems that the installation methods are a little different compared to the normal run of the mill installations which is normally required.
As im on custom ROM and always have been I'm not aware of what is available on stock.
Slightly hesitant to commit to installing if there is an impending official version.
cheers.
Yes, Oreo OOS 5 is official. There are plenty of threads on this particular subject.
dladz said:
Hi all,
seems that the installation methods are a little different compared to the normal run of the mill installations which is normally required.
As im on custom ROM and always have been I'm not aware of what is available on stock.
Slightly hesitant to commit to installing if there is an impending official version.
cheers.
Click to expand...
Click to collapse
MadCow809 said:
Yes, Oreo OOS 5 is official. There are plenty of threads on this particular subject.
Click to expand...
Click to collapse
Oreo has been released officially but yesterday they cancelled the rollout due to some unspecified bugs.
Anyway, it seems fairly stable and the there are some download links for the full ROM here: https://forum.xda-developers.com/showpost.php?p=72799046&postcount=2
ulxerker said:
Oreo has been released officially but yesterday they cancelled the rollout due to some unspecified bugs.
Anyway, it seems fairly stable and the there are some download links for the full ROM here: https://forum.xda-developers.com/showpost.php?p=72799046&postcount=2
Click to expand...
Click to collapse
Wonderful and oops if they've pulled it, so it's not quite released then..
ok good to know..
I'll hold fire on stock, sorry should have made that clear, I only flash custom ROMs although stock OOS isn't too shabby, I'd miss the mods I use
thanks though mate, I'll keep an eye out for it, appreciate it :good:
I was really considering upgrading to OS 5.0 but I've seen mixed reviews about it. It seems like the installation is sort of hassle as well. I don't see anything wrong with nougat as of right now.
Dchoi229 said:
I was really considering upgrading to OS 5.0 but I've seen mixed reviews about it. It seems like the installation is sort of hassle as well. I don't see anything wrong with nougat as of right now.
Click to expand...
Click to collapse
precisely what I was thinking, my thinking is I can upgrade but I'd be leaving behind some serious stability, stamina and performance. Not to mention that I don't know what does or doesn't work on Oreo.
I think it would make perfect sense to hold fire until it's official.
dladz said:
precisely what I was thinking, my thinking is I can upgrade but I'd be leaving behind some serious stability, stamina and performance. Not to mention that I don't know what does or doesn't work on Oreo.
I think it would make perfect sense to hold fire until it's official.
Click to expand...
Click to collapse
yup.. pretty much what I'm thinking too.
dladz said:
precisely what I was thinking, my thinking is I can upgrade but I'd be leaving behind some serious stability, stamina and performance. Not to mention that I don't know what does or doesn't work on Oreo.
Click to expand...
Click to collapse
I could be wrong on this, but I think xposed won't work on Oreo. Most other apps shouldn't have any compatibility issues.
So far the overall experience of official Oreo OOS 5 seems to be a bit snappier and performs better than Nougat.
MadCow809 said:
Yes, Oreo OOS 5 is official. There are plenty of threads on this particular subject.
Click to expand...
Click to collapse
No it is not, it was pulled, no need to tell me about threads it's not helpful nor does it make you look clever.
MadCow809 said:
I could be wrong on this, but I think xposed won't work on Oreo. Most other apps shouldn't have any compatibility issues.
So far the overall experience of official Oreo OOS 5 seems to be a bit snappier and performs better than Nougat.
Click to expand...
Click to collapse
I don't care for xposed and until it's a final release I highly doubt it'll give the same stability I have right now.
Either way I won't be committing to Oreo until it's officially released and stably within custom ROMs.
I have installed OREO on my work phone, and for the moment I am not impressed by O. Nougat is so stable and refined after all, not very clear why to upgrade...?!?!?!?! I will maintaine N on the OP5 until FaceLock comes includede in O-
mlara.particular said:
I have installed OREO on my work phone, and for the moment I am not impressed by O. Nougat is so stable and refined after all, not very clear why to upgrade...?!?!?!?! I will maintaine N on the OP5 until FaceLock comes includede in O-
Click to expand...
Click to collapse
yep that's where my heads at, again I'll be holding fire for the time being.
Fair enough. It's hardly a secret that many users have experienced boot loop issues when upgrading to OOS 5.0, maybe that was the main reason why OnePlus decided to pull back the OTA. But loads of users have successfully flashed the rom and it stable as a daily driver, not to mention several users have already noticed a performance gain over the old Nougat rom.
MadCow809 said:
Fair enough. It's hardly a secret that many users have experienced boot loop issues when upgrading to OOS 5.0, maybe that was the main reason why OnePlus decided to pull back the OTA. But loads of users have successfully flashed the rom and it stable as a daily driver, not to mention several users have already noticed a performance gain over the old Nougat rom.
Click to expand...
Click to collapse
That's irrelevant, I'm not installing it, such is the thinking of many others.
dladz said:
That's irrelevant, I'm not installing it, such is the thinking of many others.
Click to expand...
Click to collapse
They've actually released another update over 5.0. I'm still not convinced either lol.
Dchoi229 said:
They've actually released another update over 5.0. I'm still not convinced either lol.
Click to expand...
Click to collapse
Suppose we'll know once a few custom rom's have been released.
What about an official H2os? the only downloads on the official h2os site are beta 1 and beta 2. Any expected dates for oreo h2os?
OcazPrime said:
What about an official H2os? the only downloads on the official h2os site are beta 1 and beta 2. Any expected dates for oreo h2os?
Click to expand...
Click to collapse
that's kind of what I'm getting at, we need an officially released base which can be used without any odd Flashing instructions and only with bugs which would affect the device as expected.
ie: stock OOS should work fine, LOS and AOSP will more then likely have some issues, which is to be expected.
From what I've read, there has been another base released.
dladz said:
that's kind of what I'm getting at, we need an officially released base which can be used without any odd Flashing instructions and only with bugs which would affect the device add expected.
I've: stock OOS should work fine, LOS and AOSP will more then likely have some issues, which is to be expected.
From what I've read, there has been another base released.
Click to expand...
Click to collapse
exactly.. what kind if update wipes your data and forces you to lock your bootloader.
dladz said:
that's kind of what I'm getting at, we need an officially released base which can be used without any odd Flashing instructions and only with bugs which would affect the device add expected.
I've: stock OOS should work fine, LOS and AOSP will more then likely have some issues, which is to be expected.
From what I've read, there has been another base released.
Click to expand...
Click to collapse
I agree completely. I refuse to use anything other than h2os now. I get such insane battery out of it but it seems to be on the back burner in terms of updates so i expect oreo to be a long ways out. Its cool there are open betas for it though but unfortunately the betas dont allow google apps. Side thought, it would be amazing to see some development for h2os.