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 guys, just a short question.
I rooted my GS3 with CF-root. Later, I updated to the latest firmware with Kies, I9300XXELL4. I like the update a lot, and I think I will be using this for a while. Now the root is lost, that was expected. I have read instructions about how to unroot, in case there is a warranty issue, or if you want to sell the device.
My question is, the phone now being officially unrooted, is there still a way to see, that it previously has been rooted, or am I good to go like this, if I want to sell later, and want no traces of rooting to bee seen?
Thanks for the help.
Take care.
Agoston
szaboagoston said:
Hi guys, just a short question.
I rooted my GS3 with CF-root. Later, I updated to the latest firmware with Kies, I9300XXELL4. I like the update a lot, and I think I will be using this for a while. Now the root is lost, that was expected. I have read instructions about how to unroot, in case there is a warranty issue, or if you want to sell the device.
My question is, the phone now being officially unrooted, is there still a way to see, that it previously has been rooted, or am I good to go like this, if I want to sell later, and want no traces of rooting to bee seen?
Thanks for the help.
Take care.
Yes read the posts /sticky on unrooting and returning to stock for warranty .
jje
Click to expand...
Click to collapse
RESOLVED
Okay, I think I found everything here:
http://forum.xda-developers.com/showthread.php?t=1710613
Google search was better then xda search.
Now my device status says "Normal", however, I never got to reset binary download counter. That's not needed than, is it?
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 have a rooted Nook tablet so not a complete noob, but how safe is the root process for a verizon Galaxy s4? I'd like to root it so I can get rid of some of the junk apps and install others I want, but I void my two yr warranty...thoughts from the experts? just want to feel comfortable moving forward and if so, is there a set of clear instructions somewhere?
Thanks to all
The search button is your friend.
I have also rooted verizon schi545 cm10'd I did not see aps to sd so now I went back to stock mdk 4.2.2 so now what take update or is there another rom that has aps to sd ?
Sent from my SCH-I545 using Tapatalk 4 Beta
wedmiston said:
I have a rooted Nook tablet so not a complete noob, but how safe is the root process for a verizon Galaxy s4? I'd like to root it so I can get rid of some of the junk apps and install others I want, but I void my two yr warranty...thoughts from the experts? just want to feel comfortable moving forward and if so, is there a set of clear instructions somewhere?
Thanks to all
Click to expand...
Click to collapse
Instead of an asinine comment that does you no go, here's some info.
Yes, rooting will void the warranty. However, you can always Odin to go back to stock should you have an issue that requires returning your phone to VZW.
I've rooted both my old S3 and my current S4. I JUST started rooting on the S3, so I'm relatively new as well but have learned a lot. My S3 was stock rooted, but I took the plunge with my S4 and am running HyperDrive ROM which is HOLY MOLY sweetness.
It's up to you, but if you're going to root, perhaps look at the ROMs that are available and flash one. I'm not sorry that I started flashing Roms. Not one bit
Wolffgirl
Three replies thus far and yours is the only one of solid benefit..thanks. Can you point me anywhere to see step by step to accomplish what you did on your S4?
wedmiston said:
Wolffgirl
Three replies thus far and yours is the only one of solid benefit..thanks. Can you point me anywhere to see step by step to accomplish what you did on your S4?
Click to expand...
Click to collapse
Here is the link to root: http://forum.xda-developers.com/showthread.php?t=2290798
How old is your S4? The reason that I ask is that there was an OTA update the broke root. Currently there are Dev's looking into how to root with the new firmware.
Have you installed the OTA update?
Phone is about a month old...I have made no changes to the existing phone so I don.t know about the OTA update (although the VW software that came with it appears to update the phones software when plugged into laptop)
wedmiston said:
Phone is about a month old...I have made no changes to the existing phone so I don.t know about the OTA update (although the VW software that came with it appears to update the phones software when plugged into laptop)
Click to expand...
Click to collapse
Go to ->Setting->More->About Phone and tell me what you Baseband version says. If it's VRUAME7, you have the OTA update. If it's VRUAMDK, you do not.
confirming VRUAME7
wolfgrrl said:
Go to ->Setting->More->About Phone and tell me what you Baseband version says. If it's VRUAME7, you have the OTA update. If it's VRUAMDK, you do not.
Click to expand...
Click to collapse
wedmiston said:
confirming VRUAME7
Click to expand...
Click to collapse
Unfortunately you will not be able to root until a new method becomes available.
is it possible to back up to pre-OTA update status?
wolfgrrl said:
Unfortunately you will not be able to root until a new method becomes available.
Click to expand...
Click to collapse
wedmiston said:
is it possible to back up to pre-OTA update status?
Click to expand...
Click to collapse
No.....there is no way to uninstall the update. Patience, young rooting grasshopper! A new method will be out shortly, I would imagine. Doesn't usually take too long,
Much appreciated...and lastly can you point me to how I would reinstall what you refer to as Odin should I screw up a future root process?
wedmiston said:
Much appreciated...and lastly can you point me to how I would reinstall what you refer to as Odin should I screw up a future root process?
Click to expand...
Click to collapse
This link explains how to go back to stock by using Odin: http://www.sxtpdevelopers.com/showthread.php?t=237
Ok. I know the models N950U and N950U1 can swap firmware. So since Sprint had released Pie for N950U on its network, I got to thinking if that firmware can be flashed via Odin on N950U1.
The answer is Yes! I successfully flashed the N950USQU5DSC1/N950UOYN5DSC1 OS: Pie(Android 9) on my N950U1. And without the Sprint bloats.
After some discussions with @Mr. Orange 645 , I felt I needed to put some caveats in this post. So anyone attempting this should be reminded of some inherent risks.
1. There's a possibility that your OTA updates could be broken.
2. If you do get updates via OTA it will include Sprint bloats and stuff.
3. You will have to flash via Odin PIE for N950U1 when it's out.
4. Use only the files included in the Sprint PIE firmware. Do not mix with other files.
5. And something could always go wrong and you end up bricking your phone. DO NOT DO THIS IF YOUR PHONE BRICKING TOLERANCE IS LESS THAN 0.1%
6. A full factory reset is a must
This is simply really. Use the regular Odin 3.13.1 and select BL, AP, etc. But only IGNORE the Home_csc file and the User_Data file. Don't flash these.
Also, do not mix any other CSC files. Flash only the files you see in the Sprint PIE firmware.
If you do it right, your N950U1 will boot to Pie without any Sprint apps or other bloat.
Importantly Knox is not tripped. Phone status still official. In download mode Knox still reads 0x0.
OTA still works (at least it still connects to server and returns a result). However, if there is an update and you installed it, I can't say the effect it will have on the phone.
More pics
jopancy said:
This is simply really. Use the regular Odin 3.13.1 and select BL, AP, etc. But only IGNORE the Home_csc file and the User_Data file. Don't flash these.
Click to expand...
Click to collapse
Just be aware that this (only partially flashing a firmware update) will most likely break OTA updates on your device. As a consequence you will always need to use ODIN to flash future updates unless you flash the full set of files again.
Of course this won't trip Knox. It's all official firmware. And it will break OTAs, so when you want to update, you will have to use ODIN.
My suggestion is:
1. Wait for the official OTA. It should be pushed soon since the carriers have released Pie. OR
2. Follow my guide to get the Pie beta for the U1. OR
3. Just flash the full carrier firmware and deal with the bloat.
Mr. Orange 645 said:
Of course this won't trip Knox. It's all official firmware. And it will break OTAs, so when you want to update, you will have to use ODIN.
My suggestion is:
1. Wait for the official OTA. It should be pushed soon since the carriers have released Pie. OR
2. Follow my guide to get the Pie beta for the U1. OR
3. Just flash the full carrier firmware and deal with the bloat.
Click to expand...
Click to collapse
Of course some will wait for the official OTA. But for people like me who want to see what Pie has to offer NOW, this is a way of doing that. Official OTA updates can be reinstated when PIE for N950U1 is out and is flashed via Odin.
People got the unlocked version because they didn't want the bloat that comes with carrier branded firmware.
jopancy said:
Of course some will wait for the official OTA. But for people like me who want to see what Pie has to offer NOW, this is a way of doing that. Official OTA updates can be reinstated when PIE for N950U1 is out and is flashed via Odin.
People got the unlocked version because they didn't want the bloat that comes with carrier branded firmware.
Click to expand...
Click to collapse
PIE is available now for people to see what it has to offer on the U1 without mix matching firmware files and breaking things.
Yes I know why people buy the U1. I've had several of them myself since the S8+
Mr. Orange 645 said:
PIE is available now for people to see what it has to offer on the U1 without mix matching firmware files and breaking things.
Yes I know why people buy the U1. I've had several of them myself since the S8+
Click to expand...
Click to collapse
Stop writing contradictory things and creating panic where there is non. How many people got to join the Beta? Moreover the beta is now closed. N950U1 has to wait for the official PIE when most of the carriers have done their test. And that could be weeks. Like I explained if one cannot wait, this method is an option to get pie now. You agree that both N950U1 and N950U has the same Hardware, so what is to break? I could point you to older posts where some have flashed different carrier firmware on their phones without issues. I have been using Sprint PIE Firmware on N950U1 without issues, Samsung pay works, Secure folder works, not a single issue.
If you are afraid to 'break things' then you shouldn't even be on xda.
jopancy said:
Stop writing contradictory things and creating panic where there is non. How many people got to join the Beta? Moreover the beta is now closed. N950U1 has to wait for the official PIE when most of the carriers have done their test. And that could be weeks. Like I explained if one cannot wait, this method is an option to get pie now. You agree that both N950U1 and N950U has the same Hardware, so what is to break? I could point you to older posts where some have flashed different carrier firmware on their phones without issues. I have been using Sprint PIE Firmware on N950U1 without issues, Samsung pay works, Secure folder works, not a single issue.
If you are afraid to 'break things' then you shouldn't even be on xda.
Click to expand...
Click to collapse
I don't think you know what the word contradictory means. I never said anything contradictory, nor am I creating panic. I believe I have a little more experience at this than you do. And I'm trying to help you out as well as others. Have you even read my guide?
Mr. Orange 645 said:
I don't think you know what the word contradictory means. I never said anything contradictory, nor am I creating panic. I believe I have a little more experience at this than you do. And I'm trying to help you out as well as others. Have you even read my guide?
Click to expand...
Click to collapse
Yes I have read your guide. In fact, it is one of the reasons I felt what I did could work. I only posted the results of following your guide. So I am confused at why you are so critical.
N950U1 is supposed to work on ANY carrier. Including Sprint. So it should follow that Sprint firmware could be flashed on N950U1.
For all it's worth, you should see my post as a confirmation of your guide.
And OTA isn't broken. I tested it and it works. See pics.
jopancy said:
Yes I have read your guide. In fact, it is one of the reasons I felt what I did could work. I only posted the results of following your guide. So I am confused at why you are so critical.
N950U1 is supposed to work on ANY carrier. Including Sprint. So it should follow that Sprint firmware could be flashed on N950U1.
For all it's worth, you should see my post as a confirmation of your guide.
And OTA isn't broken. I tested it and it works. See pics.
Click to expand...
Click to collapse
I'm confused as to why you are determined to take what I'm saying so personal. I'm not being critical.
And again, yes, the devices are identical hardware-wise and you can cross flash carrier firmware on the U1 and U1 firmware on the carrier models. That's not the question.
I was merely pointing out that mixing firmware files (using some from U1 and using some from U) can break things, including OTAs. That's not being critical, that's letting you and everyone else know the downside. The only person who's been critical is you, telling me I shouldn't even be on XDA, merely because I dared to tell you a con to mixing firmwares.
By the way, your screenshot proves nothing. That just means you CHECKED for an OTA. When I say OTAs will be broken, I mean even if your phone recognizes there's an update available, it won't be able to apply it, as the OTA update checks to make sure you're on a specific firmware version.
As I said before, I personally helped someone do EXACTLY what you did through PM, and he went back to regular firmware because his OTAs were broken and he didn't want to have to use ODIN each time he wanted to update.