How can I upgrade to latest android system in smartphone when a new android os comes? Is there any smartphone to do this?
colaxda said:
How can I upgrade to latest android system in smartphone when a new android os comes? Is there any smartphone to do this?
Click to expand...
Click to collapse
Settings/About Device/Software Update for OTA updates, but if there are no updates from the carrier/manufacturer...a lot of devices have custom ROMs that can be installed through custom recovery such as TWRP.
Sent from my XT1609 using Tapatalk
colaxda said:
How can I upgrade to latest android system in smartphone when a new android os comes? Is there any smartphone to do this?
Click to expand...
Click to collapse
If you want to get an update right away when it gets launched, you need to get a Nexus of Google Pixel. No manufacturer is good enough to deliver a fast update.
If you want to check for updates on your phone, go to your settings, scroll all down and go into "System Updates" (the name varies with phone / ROM). If there is any avaiable, you can update.
DarkAlpha.Sete said:
If you want to get an update right away when it gets launched, you need to get a Nexus of Google Pixel. No manufacturer is good enough to deliver a fast update.
If you want to check for updates on your phone, go to your settings, scroll all down and go into "System Updates" (the name varies with phone / ROM). If there is any avaiable, you can update.
Click to expand...
Click to collapse
It's not about all software updates of a smartphone. It's about update from android-6 to android 7 or from android-5 to android-7. Is it possible to do this? I heard it's not possible to update android system from android-5 to android-7.
colaxda said:
It's not about all software updates of a smartphone. It's about update from android-6 to android 7 or from android-5 to android-7. Is it possible to do this? I heard it's not possible to update android system from android-5 to android-7.
Click to expand...
Click to collapse
I dont think you can upgrade directly from android 5 to 7, you would need to upgrade to 6 first, then 7.
DarkAlpha.Sete said:
I dont think you can upgrade directly from android 5 to 7, you would need to upgrade to 6 first, then 7.
Click to expand...
Click to collapse
Is it difficult to upgrade from android-5 to android-6 then to android-7?
colaxda said:
Is it difficult to upgrade from android-5 to android-6 then to android-7?
Click to expand...
Click to collapse
Well, for that you would need for your manufacturer to make the update. If you are sure that there are no more official updates, the choice is to take a risk and flash a new ROM. You don't seem to have much experience in this stuff, so I don't recommend messing with that, because if something goes wrong, you devices bricks (dies). If you really want to proceed, try googling: "*your device name* + *model* ROM". Don't forget to read some guides on flashing first, to get more knowledge about what you are going to do. Making a new thread about that probably would be good.
(By the way, I forgot you asked if there is any smartphone that can get the update right when it is launched. They are the Nexus devices and the Google Pixel)
DarkAlpha.Sete said:
Well, for that you would need for your manufacturer to make the update. If you are sure that there are no more official updates, the choice is to take a risk and flash a new ROM. You don't seem to have much experience in this stuff, so I don't recommend messing with that, because if something goes wrong, you devices bricks (dies). If you really want to proceed, try googling: "*your device name* + *model* ROM". Don't forget to read some guides on flashing first, to get more knowledge about what you are going to do. Making a new thread about that probably would be good.
(By the way, I forgot you asked if there is any smartphone that can get the update right when it is launched. They are the Nexus devices and the Google Pixel)
Click to expand...
Click to collapse
What's flashing a new ROM? What does 'device bricks(dies)' mean?
colaxda said:
What's flashing a new ROM? What does 'device bricks(dies)' mean?
Click to expand...
Click to collapse
Im going to simplify this as much as I can:
First of all, this is modifying your device, and if you do any of this, you will void your warranty.
ROM can be considered the operative system of your device. Flashing means putting a new one(but still android-based). To do that people use custom recoveries, like TWRP or CWM. They are like the one that comes with the phone, but wit a lot of more features.
Bricking a device is when something goes wrong while modifying your device. There are 2 types of bricks: the Soft and Hard. The Soft-Brick is when your ROM/software has any problem and starts bootlooping (this means it will keep restarting). You can easily fix that, by just getting to stock (factory) ROM or flashing the one you had again. The Hard-Brick is when your device doesn't even boot, or something more serious has happened. There is no consistent way on fixing any hard-bricks, as it depends on what you have done, luck and device.
If my explanation is bad or you can't understand it, there are some links that may help you.
Fastboot (I can't explain properly what it is)
What is a custom Recovery
What is a custom ROM
If you really want to proceed, you will lose your warranty of the device. Also, remember that ROMs and custom recoveries are device specific! Don't try using another device compilation on yours.
Related
Hi all!
I bought my GS2 about 3 weeks ago, it had 2.3.4 on it. I didn't root it, I didn't hack anything on it since then.
Two nights ago I installed the official 2.3.6 update from AT&T/Samsung. I was absolutely delighted by how easy and effortless the update was: it downloaded the 20 MB update package over WiFi, it automatically rebooted my phone, it applied the update, automatically rebooted it again, and voila, in about 4-5 minutes I had a new kernel version, a new Android version, and a new baseband version installed and ready to be used on my phone.
Note that I didn't have to root my phone for this and it also preserved all my apps and settings.
So, I have a likely naive question: why don't kernel and OS mods use the same procedure to install themselves? There's obviously a way to update the kernel easily, because it just happened to me 2 nights ago. Same for the OS update. So, why not just "hijack" AT&T's official update procedure for making kernel and OS mod installs as user-friendly as possible? If there are specific technical reasons preventing us from doing so, please, do explain them to me - I am a software engineer, I will understand, although I am an Android n00b.
I'm not 100% sure, but they probably use signed packages, and without the proper key, it won't let you update.
The update files from att are signed. If you can figure out or get your hands on the signature keys you could create any install (including kernels and roms) in an update file that could be installed simply with the stock recovery.
Sent from my SAMSUNG-SGH-I777 using XDA App
imreolajos said:
Hi all!
I bought my GS2 about 3 weeks ago, it had 2.3.4 on it. I didn't root it, I didn't hack anything on it since then.
Two nights ago I installed the official 2.3.6 update from AT&T/Samsung. I was absolutely delighted by how easy and effortless the update was: it downloaded the 20 MB update package over WiFi, it automatically rebooted my phone, it applied the update, automatically rebooted it again, and voila, in about 4-5 minutes I had a new kernel version, a new Android version, and a new baseband version installed and ready to be used on my phone.
Note that I didn't have to root my phone for this and it also preserved all my apps and settings.
So, I have a likely naive question: why don't kernel and OS mods use the same procedure to install themselves? There's obviously a way to update the kernel easily, because it just happened to me 2 nights ago. Same for the OS update. So, why not just "hijack" AT&T's official update procedure for making kernel and OS mod installs as user-friendly as possible? If there are specific technical reasons preventing us from doing so, please, do explain them to me - I am a software engineer, I will understand, although I am an Android n00b.
Click to expand...
Click to collapse
Not to mention making things too easy is a big reason for far more bricks then there should be.
Flashing a custom rom is not ment to be easy as the min you root it you voided your warranty and returning after the fact if you mess up is fraud.
penguinlogik said:
I'm not 100% sure, but they probably use signed packages, and without the proper key, it won't let you update.
Click to expand...
Click to collapse
Correct - stock recovery will only flash packages that have been signed by Samsung or AT&T.
.. and who doesn't like booting into recovery and flashing yourself
Makes me feel like I know what I'm doing
Sent from my SAMSUNG-SGH-I777 using xda premium
zelendel said:
Not to mention making things too easy is a big reason for far more bricks then there should be.
Flashing a custom rom is not ment to be easy as the min you root it you voided your warranty and returning after the fact if you mess up is fraud.
Click to expand...
Click to collapse
Unless your root procedure or use thereof caused the phone or hardware to fail then this statement is not 100% true.
Read up on the Magnusson-Moss Act....of course, the burden is on the consumer to fight it.
To me, a phoned is really a cheap disposable piece of hardware. I prefer to take the risk of damage from use that may void my warranty. To me, having my phone (or car, motorcycle,etc...) work the way I want is more valuable than the peace of mind that a warranty provides.
Back on topic... Flashing a ROM is already pretty damn easy. I've done the entire procedure while sitting at red lights on the way home from work... I wouldn't expect a Dev to jump through the necessary hoops to mimic an OTA update
Sent from my SAMSUNG-SGH-I777 using XDA Premium App
zelendel said:
Flashing a custom rom is not ment to be easy as the min you root it you voided your warranty and returning after the fact if you mess up is fraud.
Click to expand...
Click to collapse
Oh please.
And even if it is, these companies deserve it.
Sent from my SGH-I897
MikeyMike01 said:
Oh please.
And even if it is, these companies deserve it.
Sent from my SGH-I897
Click to expand...
Click to collapse
Without these companies we wouldn't have these products
But yeah, they can be a little unfair at times.
Hi,
I'm very sorry if the problem was in other topic, but I looked first 10-12 pages of topics and couldn't find anything. My wive's Motorola RAZR MAXX (european, retail,non-carrier) is still on ICS, newest software availible, but from time to time get massive battery drain from process called Multimedia. Fully charged phone can run out of battery in few hours, get hot like from the furnace and finally turn off out of "juice". We are aware of the problem, that this single process is draining the battery, since we've looked at battery manager and this process is beeing constantly restarting, causing 100% CPU usage and draining battery. Forced-close helps, but this process manage to restart in background and it's stupid to constantly closing it in task manager every time after finishing some tasks that trigger him to start again. So, are there any temporary solutions for this? Is Motorola aware of the problem and will fix this in upcoming JB update? And finally, when EU versions of RAZR/MAXX get official JB update?
Regards, Jacek
Baronik said:
Hi,
I'm very sorry if the problem was in other topic, but I looked first 10-12 pages of topics and couldn't find anything. My wive's Motorola RAZR MAXX (european, retail,non-carrier) is still on ICS, newest software availible, but from time to time get massive battery drain from process called Multimedia. Fully charged phone can run out of battery in few hours, get hot like from the furnace and finally turn off out of "juice". We are aware of the problem, that this single process is draining the battery, since we've looked at battery manager and this process is beeing constantly restarting, causing 100% CPU usage and draining battery. Forced-close helps, but this process manage to restart in background and it's stupid to constantly closing it in task manager every time after finishing some tasks that trigger him to start again. So, are there any temporary solutions for this? Is Motorola aware of the problem and will fix this in upcoming JB update? And finally, when EU versions of RAZR/MAXX get official JB update?
Regards, Jacek
Click to expand...
Click to collapse
read more in this forum about this phone, the EU versions got the jelly bean update
Do a full wipe from stock recoveru and ser if the problembis gone...
Sent from my XT910 using xda premium
TheMrcool212 said:
read more in this forum about this phone, the EU versions got the jelly bean update
Click to expand...
Click to collapse
Well, If you say so - yesterday I've checked update and had information, that my software is up to date.
Baronik said:
Well, If you say so - yesterday I've checked update and had information, that my software is up to date.
Click to expand...
Click to collapse
i know, that happened to me also, but not all people get the update from the settings, so you need to flash it manually from stock recovery
here's the link for the jelly bean update:
http://forum.xda-developers.com/showthread.php?t=2192532
TheMrcool212 said:
i know, that happened to me also, but not all people get the update from the settings, so you need to flash it manually from stock recovery
here's the link for the jelly bean update:
http://forum.xda-developers.com/showthread.php?t=2192532
Click to expand...
Click to collapse
I'm really aprreciate the help, but this firmware seems to be a leak, not the official one, so I won't risk bricking phone (wife's), especially, we've got iMac, so no windows program work on it (I presume it's needed for forced flashing via recovery) and I've never done any rooting/flashing myself. I'll have to wait for official update via OTA.
But you've mentioned, that you're familiar with the problem - was it fixed with the JB update in your case?
Baronik said:
I'll have to wait for official update via OTA.
Click to expand...
Click to collapse
This may not come.
Only few ROM are updated via OTA: Retail.en.FR, Retail.en.EU, Retail.en.AU, Vodafone.en.EU.
And I think your ROM version is not one of them :/
You need to change ICS to one of upper ROM, and then you can take JB update.
tie7 said:
This may not come.
Only few ROM are updated via OTA: Retail.en.FR, Retail.en.EU, Retail.en.AU, Vodafone.en.EU.
And I think your ROM version is not one of them :/
You need to change ICS to one of upper ROM, and then you can take JB update.
Click to expand...
Click to collapse
Now wife has rom 672.180.41.XT910.NonEFIGSRetail.en.EU - why do You think this Rom won't be updated any time soon? I bought this phone from normal store, it has motorola warranty (non-carrier, it's not imported from foreign country), I live in Poland. If you're right how can I make the update SAFELY on on iMac? Is it possible? The problem is getting stronger everyday - process activating himself randomly and sometimes it's too late to switch it off before it do some damage to battery. It's bloody anoying!
I'm sure that ROM 672.180.41.XT910.NonEFIGSRetail.en.EU won't be updated to JB - This device will remain on Android 4.0.4 (ICS)
You can confirm that at Motorola website (Select Poland and Retail, then Motorola Razr phone):
https://motorola-global-en-roe.custhelp.com/app/software-upgrade-news/g_id/1995
You need to change ICS to one of updated ROM(Retail.en.FR, Retail.en.EU, Retail.en.AU, Vodafone.en.EU), and then you can take JB update.
If you are from Poland you can also check this thread:
http://forum.android.com.pl/f472/ro...-europy-a-aktualizacja-przez-recovery-276361/
tie7 said:
I'm sure that ROM 672.180.41.XT910.NonEFIGSRetail.en.EU won't be updated to JB - This device will remain on Android 4.0.4 (ICS)
You can confirm that at Motorola website (Select Poland and Retail, then Motorola Razr phone):
https://motorola-global-en-roe.custhelp.com/app/software-upgrade-news/g_id/1995
You need to change ICS to one of updated ROM(Retail.en.FR, Retail.en.EU, Retail.en.AU, Vodafone.en.EU), and then you can take JB update.
If you are from Poland you can also check this thread:
http://forum.android.com.pl/f472/ro...-europy-a-aktualizacja-przez-recovery-276361/
Click to expand...
Click to collapse
Yeah, from what I found the phone won't get official OTA update - Motorola SUXX, won't buy any other phone from them, ever. I can't do flashing on Mac, even if I want.. Wife will be sooo disapointed, must find solution to this drain other way. Factory reset?
Baronik said:
I can't do flashing on Mac, even if I want..
Click to expand...
Click to collapse
I'm not sure, I think you can do that, but you need ask someone else because I'm not good in this.
Baronik said:
Factory reset?
Click to expand...
Click to collapse
I think it's not enough.
As I know you must root your ICS, install Safestrap, install new ICS(one of Retail.en.FR, Retail.en.EU, Retail.en.AU, Vodafone.en.EU), root new ICS, install voodoo ota root keeper and buckup root, install JB update, I think this would look something like this.
tie7 said:
I think it's not enough.
As I know you must root your ICS, install Safestrap, install new ICS(one of Retail.en.FR, Retail.en.EU, Retail.en.AU, Vodafone.en.EU), root new ICS, install voodoo ota root keeper and buckup root, install JB update, I think this would look something like this.
Click to expand...
Click to collapse
Why rooting? Does just installing retail version of ICS and then doing OTA update to JB won't work?
Baronik said:
Why rooting? Does just installing retail version of ICS and then doing OTA update to JB won't work?
Click to expand...
Click to collapse
I don't think you can just install other version of ICS without rooting.
Well, it’s looks like I’m ****ed up #$% I can’t update without rooting, I can’t root and update because there is no Mac tools for doing this, Motorola won’t plan to update RAZR/MAXX in my third world country to JB (get confirmation from support), and even if I’ll ask someone to make an update for me (if I found someone from near my location who know how to do this without bricking the phone) I still loose warranty because rooting void warranty. If I know all of this earlier I wold have never buy moto phone. Support guy told me that the only thing I can do is to make a factory reset, and if it won’t solve the problem give the phone to warranty. Either way I don’t have many options here – will try to reset phone first, it doesn’t take much time and doesn’t hurt.
But have one more question (maybe lame, but I’ve never done rooting) – since the rooting void warranty, is it possible to make an update to retail.UK JB and then COMPLETELY remove root with any trails it was on phone? So I won’t lost warranty and have newest software? If yes, then it will make sense to look for someone to help me with the whole update process.
Baronik said:
Well, it’s looks like I’m ****ed up #$% I can’t update without rooting, I can’t root and update because there is no Mac tools for doing this, Motorola won’t plan to update RAZR/MAXX in my third world country to JB (get confirmation from support), and even if I’ll ask someone to make an update for me (if I found someone from near my location who know how to do this without bricking the phone) I still loose warranty because rooting void warranty. If I know all of this earlier I wold have never buy moto phone. Support guy told me that the only thing I can do is to make a factory reset, and if it won’t solve the problem give the phone to warranty. Either way I don’t have many options here – will try to reset phone first, it doesn’t take much time and doesn’t hurt.
But have one more question (maybe lame, but I’ve never done rooting) – since the rooting void warranty, is it possible to make an update to retail.UK JB and then COMPLETELY remove root with any trails it was on phone? So I won’t lost warranty and have newest software? If yes, then it will make sense to look for someone to help me with the whole update process.
Click to expand...
Click to collapse
You dont need root to update, but you will need windows to flash the retail.eu ics flash the ota in the stock recovery
TheMrcool212 said:
You dont need root to update, but you will need windows to flash the retail.eu ics flash the ota in the stock recovery
Click to expand...
Click to collapse
Well, friend in the earlier posts said I can't update without the root, so I'm confused. If you're right, that I'm halfway to update, since I won't void warranty updating without root. Then I have to find someone with the knowlende how to do this and PC to actually do this.
TheMrcool212 said:
You dont need root to update, but you will need windows to flash the retail.eu ics flash the ota in the stock recovery
Click to expand...
Click to collapse
You are sure, that to flash to other version of ICS, there is no need of root?
Baronik said:
Well, friend in the earlier posts said I can't update without the root, so I'm confused. If you're right, that I'm halfway to update, since I won't void warranty updating without root. Then I have to find someone with the knowlende how to do this and PC to actually do this.
Click to expand...
Click to collapse
Take alook in the dev section and search rsdlite with this tool you can flash 672.180.41.en.eu (fastboot file has a different name)
There are many threads on how to
Then you upgrade to JB
Root is not needed for any of this
dude there will be some big media file on ur SD card which would be not able to read like in my case there was 1.4gb mkv video file which was not readable by mediaproces so it was constantly trying to update the gallery so becuase of such files which are unreadble causes media process to constantly run.....so check ur SD card whether u have any such file...if no then search for dev section for root and flash JB rom....
marconz said:
Take alook in the dev section and search rsdlite with this tool you can flash 672.180.41.en.eu (fastboot file has a different name)
Click to expand...
Click to collapse
Can you read I don't have a PC (got iMac) and those tools doesn't work on OSX?
I've been running CyanogenMod 11 for about a month now. I like it a lot, however there are instabilities. Youtube cannot play videos at all, for example; Snapchat totally fails to work; and one or two apps I've tried to install wouldn't even open. Occasionally a program will crash with a "Such-and such service has stopped" error notice.
Can anyone suggest a more stable ROM? I'm a newbie to flashing, I'm not experienced or interested in trying out different ROMs. I'm not a power user, I just want a stable, reliable ROM. Is cm11 known to have the issues I'm experiencing? Can anyone suggest an alternative?
Thanks.
AidanBell said:
I've been running CyanogenMod 11 for about a month now. I like it a lot, however there are instabilities. Youtube cannot play videos at all, for example; Snapchat totally fails to work; and one or two apps I've tried to install wouldn't even open. Occasionally a program will crash with a "Such-and such service has stopped" error notice.
Can anyone suggest a more stable ROM? I'm a newbie to flashing, I'm not experienced or interested in trying out different ROMs. I'm not a power user, I just want a stable, reliable ROM. Is cm11 known to have the issues I'm experiencing? Can anyone suggest an alternative?
Thanks.
Click to expand...
Click to collapse
megalomanic14's MegaFire ROM works great. http://forum.xda-developers.com/showthread.php?t=2608110
AidanBell said:
I've been running CyanogenMod 11 for about a month now. I like it a lot, however there are instabilities. Youtube cannot play videos at all, for example; Snapchat totally fails to work; and one or two apps I've tried to install wouldn't even open. Occasionally a program will crash with a "Such-and such service has stopped" error notice.
Can anyone suggest a more stable ROM? I'm a newbie to flashing, I'm not experienced or interested in trying out different ROMs. I'm not a power user, I just want a stable, reliable ROM. Is cm11 known to have the issues I'm experiencing? Can anyone suggest an alternative?
Thanks.
Click to expand...
Click to collapse
Since cm-11.0 for this device is not in nightlies major bugs should be expected. Sorry, I don't have a suggestion, but I have a question. Does the headphone jack work on cm11?
interloper said:
Since cm-11.0 for this device is not in nightlies major bugs should be expected. Sorry, I don't have a suggestion, but I have a question. Does the headphone jack work on cm11?
Click to expand...
Click to collapse
Yes, the headphone jack works fine.
I've made the decision to return to the official Samsung ROM, so if anybody could point me in the direction of a safe, reliable download for that I'd be very grateful.
Incidentally, what's "nightlies "?
AidanBell said:
Yes, the headphone jack works fine.
I've made the decision to return to the official Samsung ROM, so if anybody could point me in the direction of a safe, reliable download for that I'd be very grateful.
Incidentally, what's "nightlies "?
Click to expand...
Click to collapse
Nightly is the first "Official" status of a device from CM. If the device is very stable, with all system working properly and with minimal buggy behaviors CM begins building the ROM officially as a "Nightly" assuming the dev is following best practices etc.
AidanBell said:
Yes, the headphone jack works fine.
I've made the decision to return to the official Samsung ROM, so if anybody could point me in the direction of a safe, reliable download for that I'd be very grateful.
Incidentally, what's "nightlies "?
Click to expand...
Click to collapse
I don't think that anyone has the stock rom for the Mega(s) yet, waiting patiently for the guys upstairs to crack the bootloader.
however you might try to restore with Kies.
Unicorn69 said:
I don't think that anyone has the stock rom for the Mega(s) yet, waiting patiently for the guys upstairs to crack the bootloader.
however you might try to restore with Kies.
Click to expand...
Click to collapse
You are not right, I for instance have stock ROM on my Mega and I am quite satisfied... Ohhh, maybe I'm a little lying... :silly: it is MegaFireMj2V5 from megalomanic14 which is based upon a stock ROM but is greatly improved - if you are looking for alternative to stock or CM11 rom's it's worth a shot.
As for return to stock ROM - be careful to choose right version: all new firmware (beginning from CNA1) are 'enhanced' with new bootloader and Samsung KIES which is new security system. If you upgrade your Mega by Kies or by Odin with newest firmware you will be lacked possibility to downgrade AND every attempt to root or flash custom recovery will result in tipping flashing counter without any possibility to clear it. So be extremely cautious if you want to mod your Mega with no problems.
You can choose older firmware on Sammobile an flash it thru Odin - then you will have fresh stock ROM on your unit. There are many tutorials how to do it.
trurl3 said:
You are not right, I for instance have stock ROM on my Mega and I am quite satisfied... Ohhh, maybe I'm a little lying... :silly: it is MegaFireMj2V5 from megalomanic14 which is based upon a stock ROM but is greatly improved - if you are looking for alternative to stock or CM11 rom's it's worth a shot.
As for return to stock ROM - be careful to choose right version: all new firmware (beginning from CNA1) are 'enhanced' with new bootloader and Samsung KIES which is new security system. If you upgrade your Mega by Kies or by Odin with newest firmware you will be lacked possibility to downgrade AND every attempt to root or flash custom recovery will result in tipping flashing counter without any possibility to clear it. So be extremely cautious if you want to mod your Mega with no problems.
You can choose older firmware on Sammobile an flash it thru Odin - then you will have fresh stock ROM on your unit. There are many tutorials how to do it.
Click to expand...
Click to collapse
Many thanks, guys.
I've been on Sammobile and selected "I9205XXUCNA2_I9205BTUCNA1_BTU.zip", which I intend to install in the next couple of hours unless anyone on here screams at me that I shouldn't! I'm in the UK with a GT-i9250, so I believe that's the right version for me.
To be honest, I'm not worried about tipping the flashing counter (if I even understand properly what that means). I rooted my phone some time ago, and liked that. Two weeks ago I decided to try Cyanogenmod since I've never used a different ROM. I wasn't impressed, and have decided I want to go back to Samsung original. If, in the process, I prevent myself from ever being able to flash another alternative ROM, or I void the phone's warrenty in any way, I can live with that.
AidanBell said:
Many thanks, guys.
I've been on Sammobile and selected "I9205XXUCNA2_I9205BTUCNA1_BTU.zip", which I intend to install in the next couple of hours unless anyone on here screams at me that I shouldn't! I'm in the UK with a GT-i9250, so I believe that's the right version for me.
To be honest, I'm not worried about tipping the flashing counter (if I even understand properly what that means). I rooted my phone some time ago, and liked that. Two weeks ago I decided to try Cyanogenmod since I've never used a different ROM. I wasn't impressed, and have decided I want to go back to Samsung original. If, in the process, I prevent myself from ever being able to flash another alternative ROM, or I void the phone's warrenty in any way, I can live with that.
Click to expand...
Click to collapse
OK, it's your choice... in fact newest firmware do not offer nothing new but bootloder without return and KNOX. CNA2 it's firmware with KNOX embedded. For mundane user this means nothing special, but for somebody who plan to root and mod it could be pain in... Try to read a little about rooting firmware with KNOX... but as I said, you are warned... tipping counter means setting flag which shows to e.g. service so there was installed unofficial software and it means so you are lacking your warranty. With firmware with KNOX this is irreversible because setting such flag physically burns efuse in system making hardware change. Cheers...
I stay on firmware without KNOX because of possibility to change ROMs and easy install custom software. Waiting for KK which for sure will have 'new type' bootloader and then will be no choice...
trurl3 said:
OK, it's your choice... in fact newest firmware do not offer nothing new but bootloder without return and KNOX. CNA2 it's firmware with KNOX embedded. For mundane user this means nothing special, but for somebody who plan to root and mod it could be pain in... Try to read a little about rooting firmware with KNOX... but as I said, you are warned... tipping counter means setting flag which shows to e.g. service so there was installed unofficial software and it means so you are lacking your warranty. With firmware with KNOX this is irreversible because setting such flag physically burns efuse in system making hardware change. Cheers...
I stay on firmware without KNOX because of possibility to change ROMs and easy install custom software. Waiting for KK which for sure will have 'new type' bootloader and then will be no choice...
Click to expand...
Click to collapse
You make a good case, and perhaps I should install an earlier version, then. Thanks. However, I've looked on Sammobile and they seem to offer only the latest version. Where can I download an earlier KNOX-free version, please?
trurl3 said:
OK, it's your choice... in fact newest firmware do not offer nothing new but bootloder without return and KNOX. CNA2 it's firmware with KNOX embedded. For mundane user this means nothing special, but for somebody who plan to root and mod it could be pain in... Try to read a little about rooting firmware with KNOX... but as I said, you are warned... tipping counter means setting flag which shows to e.g. service so there was installed unofficial software and it means so you are lacking your warranty. With firmware with KNOX this is irreversible because setting such flag physically burns efuse in system making hardware change. Cheers...
I stay on firmware without KNOX because of possibility to change ROMs and easy install custom software. Waiting for KK which for sure will have 'new type' bootloader and then will be no choice...
Click to expand...
Click to collapse
Like you,i still stay on old firmware,new firmware have knox,knox make your phone brick if you root.
rizky123 said:
Like you,i still stay on old firmware,new firmware have knox,knox make your phone brick if you root.
Click to expand...
Click to collapse
Agreed. You guys have convinced me that I should be flashing an old version of Samsung, not the latest with KNOX. But I can only do that if I can find one! Can anyone please point me in the right direction?
AidanBell said:
You make a good case, and perhaps I should install an earlier version, then. Thanks. However, I've looked on Sammobile and they seem to offer only the latest version. Where can I download an earlier KNOX-free version, please?
Click to expand...
Click to collapse
Hmmm, you are right... In such case i recommend you to install custom ROM MegaFireMJ2V6 made by megalomanic14 on basis stock MJ2 which you can find HERE.
Actually I am using this ROM and can say it is very good - looks like stock but is much faster. It's rooted already. Version X offer firmware stripped from unneeded apps to the extent.
trurl3 said:
Hmmm, you are right... In such case i recommend you to install custom ROM MegaFireMJ2V6 made by megalomanic14 on basis stock MJ2 which you can find HERE.
Actually I am using this ROM and can say it is very good - looks like stock but is much faster. It's rooted already. Version X offer firmware stripped from unneeded apps to the extent.
Click to expand...
Click to collapse
Thank you very much. Most of that sentences was Greek to me, but I get the idea! The truth is, I put my foot into the water of flashing custom ROMS, and decided it wasn't for me. I just want one, reliable ROM that I can live with for many months without having to change it. That's why I decided to go back to Samsung, because there were too many bugs in Cyanogenmod and I don't want to start testing one ROM after the next. I just want to install a reliable, bug-free ROM now, and have done with it. So you think that MegaFireMJ2V6 would be such a ROM in my case?
PS:
It seems MegaFireMJ2V6 can't be downloaded from that link anyway?
Type your phone model in the link below and choose the one you want. Create a free account if you need faster download speeds.
http://www.sammobile.com/firmwares/
Silesh.Nair said:
Type your phone model in the link below and choose the one you want. Create a free account if you need faster download speeds.
http://www.sammobile.com/firmwares/
Click to expand...
Click to collapse
Thank you, but I've tried this several times, and the only download available is the most recent.
You are wrong. It shows all the firmwares released for a model. I can see all the releases for GT-I9200. Attached is a screenshot of the older firmware without knox....
As far as I understand it, these are all the same ROM, simply different versions for different countries. When I put in my phone, GT-i9250, I am presented with a similar page, but it's only the one ROM; 4.2.2 with KNOX.
Ok man, I am done trying to explain things to you. The list you showed only displays Knox firmware, but what you said is not true. Here is another site with older firmware displayed for the I9205. There is no I9250 model Mega afaik..
Silesh.Nair said:
Ok man, I am done trying to explain things to you. The list you showed only displays Knox firmware, but what you said is not true. Here is another site with older firmware displayed for the I9205. There is no I9250 model Mega afaik..
Click to expand...
Click to collapse
I apologise if I have offended you in any way, that certainly wasn't my intention. I'm simply new to all of this and don't understand it well. I appreciate the new link, and thank you for your help.
Most of the pinned threads are out of date, so:
TL;DR: What's the current method of getting root, backing up drm/keys, installing custom recovery and roms?
This phone is awesome, but I don't like the default OS from Sony. I'm worried about bricking it since the current method of doing all this is slightly out of date. Let's get things up to date and allow new comers to this BLOODY HUGE BEAST the simplest path towards a custom rom.
4.4.4 Build 14.4.A.0.108
I'm looking for the same, I just was offered the c6833 and sony rom is not my cup of tea....
r4ttyuk said:
Most of the pinned threads are out of date, so:
TL;DR: What's the current method of getting root, backing up drm/keys, installing custom recovery and roms?
This phone is awesome, but I don't like the default OS from Sony. I'm worried about bricking it since the current method of doing all this is slightly out of date. Let's get things up to date and allow new comers to this BLOODY HUGE BEAST the simplest path towards a custom rom.
4.4.4 Build 14.4.A.0.108
Click to expand...
Click to collapse
jiminini said:
I'm looking for the same, I just was offered the c6833 and sony rom is not my cup of tea....
Click to expand...
Click to collapse
http://forum.xda-developers.com/xperia-z-ultra/general/guide-everything-root-4-4-4-t2938098
adfurgerson said:
http://forum.xda-developers.com/xperia-z-ultra/general/guide-everything-root-4-4-4-t2938098
Click to expand...
Click to collapse
Like I said, out of date.
Also now that the official update has come out, even more so.
r4ttyuk said:
Like I said, out of date.
Also now that the official update has come out, even more so.
Click to expand...
Click to collapse
Even if it is a bit out of date, this still holds true.
I used this about a month ago and this still works 100%.
Up until I upgraded to 5.0.1, I lost root via OTA update and with this situation, there is no easy way to root again. Not until you unlock bootloader and downgrade to 4.4.4.
For the simple of heart who don't need the diversity of a custom ROM, but moreso hate the pain of re-rooting after OTA installation. Not intended to host this thread so much as I am here to inspire it...
I updated with flash fire. It worked perfectly. I am on stock rooted. went from 7.0 to 7.1.1.
pickupman66 said:
I updated with flash fire. It worked perfectly. I am on stock rooted. went from 7.0 to 7.1.1.
Click to expand...
Click to collapse
Can you please explain how to do this? I'm on 7.0, and wanna go to 7.1.1 also
Skickat från min Nexus 6P via Tapatalk
Taken from here:
http://forum.xda-developers.com/nexus-6p/general/nougat-7-1-1-roll-begins-t3513139/page8
1. Download the factory image from here.
https://dl.google.com/dl/android/aos...y-ef607244.zip
2. Select the firmware option on FlashFire.
3. Select ONLY system, vendor and boot images. ***DO NOT SELECT BOOTLOADER OR RADIO***
4. Select Flash.
5. Wait for some time.
6. Might bootloop a couple of times. Do not panic.
7. ENJOY!!!
Techstro said:
For the simple of heart who don't need the diversity of a custom ROM, but moreso hate to pain of re-rooting after OTA installation. Not intended to host this thread so much as I am here to inspire it...
Click to expand...
Click to collapse
Seriously! Not to be rude, but if flashing a zip is that painful for you, perhaps you're in the wrong place.
Sincere apologies...
mikexda said:
Seriously! Not to be rude, but if flashing a zip is that painful for you, perhaps you're in the wrong place.
Click to expand...
Click to collapse
Please forgive me sir. I love custom ROM's, I'm just in a phase right now and I figured that what helps me may help someone else. I don't understand how I offended you though sir. Is it because this thread is a waste of space or that it has no business on XDA? I need clarification in order to understand my error. My only clue is that you said flashing a zip, which leaves me feeling misunderstood... I have been flashing zips since the original HTC Desire which was on 2.1 donut before it's final OTA of eclair. Rooted, S-Off'd, flashed all kinds of mods and ROMS, even had a buggy ICS running on it for a while.
HTC Amaze, how hard was it to S-Off that? The wire trick? Had xPosed, custom boot animation, etc. Then there was Alcatel, had 2 that I rooted, the venture and the evolve2, same as above custom everything.
I'm on my Nexus 6P now, as long as we're getting updates OTA I want to remain stock for a change, at least till the updates stop coming. Maybe it's cuz I said there is pain in re-rooting... it's not just the process of re-rooting, it's everything that is undone and uninstalled when you update with a stock zip, and wiping data is a big step for those in my sort of position so flashing "some" custom ROM's is an un-worthy sacrifice at this phase.
If need be I will edit or delete my original post you quoted. I hope I did manage to bring into focus to some degree at some part of cause for the confusion emoji. Any ideas are welcome and thank you for your analytical input.
pickupman66 said:
I updated with flash fire. It worked perfectly. I am on stock rooted. went from 7.0 to 7.1.1.
Click to expand...
Click to collapse
A perfect example. I have flash fiire but never used it, I read somewhere that it doesn't work as one would expect. That it does not preserve root against OTA, and that there truly is no solution available as if it were not possible. I take your word for it though. I personally am not ready to try it yet, just to provide resources for those who are and to be well educated when I am ready.
I'm still waiting for xPosed for the new architecture, I don't want to update just to find out it's available for 7.0 and not 7.1.1 however unlikely that may be. I know I can always back up, but I'd have to do so regularly to keep it up to date which can't be done once you've upgraded and it may be months before the framework is available if it can be done which I hear it has...
Too many variables, I'm on stand-by, ready to pay and grateful for my memories and the devs responsible for them...