Database Users

[Q] Downgrading Canadian Galaxy S4 & a Q about Knox

Hello,
I recently picked up a Canadian Galaxy S4. This is my first android device after using an iPhone 4 for the last 3 years. I'm a tinkering kind of guy so when I heard about the whole custom ROM community for the s4, I was excited. I've been reading up on this for the last 3 weeks and I still have a couple questions that I haven't really seen a solid answer for specifically regarding the 1337m model.
1) If I root it would be nice to be able to reverse things should I need to send it in for warranty repair. I understand that triangle away isn't working on the latest MG1 firmware (which my device came with). I know that the ME7 update on the US version included a bootloader that no longer allowed downgrading firmware. Is this the case with the Canadian models as well? If it is possible to downgrade are there any special steps that need to be taken, or can I just flash a stock MDJ image via odin/heimdall
2) I have read the whole thread about the issues with the knox warranty void efuse. I checked the download mode on my phone and it does not have any of the knox info on it, so as I understand it, knox isn't enabled and therefore as long as I don't update to new stock firmware and I shouldn't trip the efuse. I have disabled auto-update in the settings. Is there anything else that I should do or be aware of to make sure that my phone doesn't update and force the knox stuff on my phone.
At the end of the day, if my warranty is permanently void, that's fine, but if there's a way that I can still keep the ability to restore my phone to 100% stock without tripping and binary counters or efuses I'd like to make sure that I know and understand how to do that before I start flashing custom roms rather than trying to figure it out in a panic if something goes wrong on my device.

[Q] Will updating a rooted Note 3 in Kies brick my phone?

Hey guys
I have a Galaxy note 3 with Rogers here in Canada (SM-N900W8) and I know there has been 2 updates released (MJ1 and MJ4) but I havent been able to update over the air because my phone is rooted and flagged and my knox trigger is flagged as well.
Using Wanam xposed I have my status set to official and I can download the new update but the installation will fail.
Anyway so I connected my phone to KIES and it says I can update, however before I update it says if my phone is rooted its possible I can brick my phone.
So my questions are, 2 install these updates (MJ1 and MJ4), will it brick my phone? If it doesnt will I lose my root? Can I reroot on these latest firmwares and lastly is there reasons why maybe I should stay at my current firmware?
Sorry if this has been asked before. Ive tried searching and I didnt have much luck
Thanks

djtiko said:
Hey guys
I have a Galaxy note 3 with Rogers here in Canada (SM-N900W8) and I know there has been 2 updates released (MJ1 and MJ4) but I havent been able to update over the air because my phone is rooted and flagged and my knox trigger is flagged as well.
Using Wanam xposed I have my status set to official and I can download the new update but the installation will fail.
Anyway so I connected my phone to KIES and it says I can update, however before I update it says if my phone is rooted its possible I can brick my phone.
So my questions are, 2 install these updates (MJ1 and MJ4), will it brick my phone? If it doesnt will I lose my root? Can I reroot on these latest firmwares and lastly is there reasons why maybe I should stay at my current firmware?
Sorry if this has been asked before. Ive tried searching and I didnt have much luck
Thanks
Click to expand...
Click to collapse
Short answer is NO.
I updated mine via KIES to MJ7 (I'm on the N9005) - while rooted. KIES says you "may" encounter problems but mine was fine and I re-rooted with ease (already tripped KNOX so no worry there for me) _- as for your firmware on the N900W8 - not sure if you can root with the latest firmware or not personally

Updating to 5.0 and keeping root?

Hi Guys
There's an OTA 5.0 update ready for my GS5. The problem is that I have root (Towelroot) and want to keep it.
From what I've been reading it looks like all root methods are either ustable of KNOX tripping.
Thanks in advance.

Same issue here
I've got a G900F - no carrier, but running on 3 in the UK anyway. When I got it, it was on Kitkat, and Towelroot wouldn't work due to the compile date being > Towelroot's ability. I downgraded the kernal as per the thread in the General section (as a note, the thread "How to root - all variants" is so far out of date, it's going to lead to people with less experience nuking their devices, perhaps we should unsticky that thread and write up a cleaner version for all the variants out there?) then rooted, and changed the kernal back to my original one.
Great - now I have a rooted, KNOX 0x0 S5 running kitkat. Now Lollipop is available and I'd like to update. So some questions on how I do this and...
1. Retain root with KNOX 0x0
2. Not trash my installed apps / configurations
I know I'll need to update via say Kies as OTA won't be available to me but if/when I update will I keep installed apps / configs? And how do I keep root without affecting KNOX?
This would, I imagine, be a common scenario and worth creating a sticky / section in an updated "How to root all variants" sticky.
Thanks everyone,
a.

Take this only as a pointer because I can't remember exactly what I read, but I think you can update to Lollipop using Mobile ODIN Pro with the Pre-Root option checked, using a stock Lollipop ROM from sammobile / XDA so long as you are already running a rooted KitKat ROM, and that doesn't flag the KNOX counter
Im new to the S5 and just gathering info myself, so make sure you check up on that yourself thoroughly first

*Detection* said:
Take this only as a pointer because I can't remember exactly what I read, but I think you can update to Lollipop using Mobile ODIN Pro with the Pre-Root option checked, using a stock Lollipop ROM from sammobile / XDA so long as you are already running a rooted KitKat ROM, and that doesn't flag the KNOX counter
Im new to the S5 and just gathering info myself, so make sure you check up on that yourself thoroughly first
Click to expand...
Click to collapse
Thanks for reminding us of Mobile Odin Pro. It's got the ability to reinject root on firmware installation and not tripping the binary counter.
Can someone confirm whether this method still works on Galaxy S5 when installing 5.0 firmware?

The last comment from Chainfire in his mobile odin thread was that it wasn't compatible yet.....but being worked on......no updates since that post.
Sent from my rooted kn0x0 SM-G900F S5

Yep, that's what I thought as well. I guess I will have to wait a bit. No big deal.
Thanks Keithross

Downgrading to 4.2.2

Hey guys i have a galaxy s4 19500 running android 4.4.2 kitkat ( argentian (aro) firmware )
My phone was recently on 5.0.1 lollipop (indian ) version and i downgraded to 4.4.2 argentian firmware following a thread here on xda
I was wondering if a downgraded to 4.2.2 JELLYBEAN was possible ?
I mean i know it's super messy becuase of knox but if we take all the precautions like backing up efs partition then can the downgrade be done ?
I really think that jellybean is the perfect firmware for s4 and kitkat and lollipop have both made my s4 experience only worse
It would be awesome if i could go back to 4.2.2 jellybean and enjoy my old device

If you downgrade to 4.2.2 you will brick the device. Since new bootloader( version of Android 4.4.2 i think), you are not able to install 4.2.2 without brick.

@sgalchev: Not true at all. It is possible to replace 4.4.2 with 4.2.2 as I have done it in order to resolve issues I had with my S4. What ends up happening after doing the downgrade is that upon every boot and upon every trip into the recovery you will get a notification that the kernel or recovery is not SEAndroid enforcing. Other than that everything works normally.
Now, downgrading from 5.0.1 to 4.2.2 may be a completely different matter, but I suspect it too is possible.

Yea, shure, but you can't do it without ticking the Knox flag[emoji6] Goodbye warranty...

Strephon Alkhalikoi said:
@sgalchev: Not true at all. It is possible to replace 4.4.2 with 4.2.2 as I have done it in order to resolve issues I had with my S4. What ends up happening after doing the downgrade is that upon every boot and upon every trip into the recovery you will get a notification that the kernel or recovery is not SEAndroid enforcing. Other than that everything works normally.
Now, downgrading from 5.0.1 to 4.2.2 may be a completely different matter, but I suspect it too is possible.
Click to expand...
Click to collapse
Hey man it feels awesome to know that it is possible to do can you please give detailed explanation of how you did it
I would really like to do it no matter how much hard or risky it is and i have already downgraded from 5.0.1 to 4.4.2 now i just need to downgrade to stock out of the box jellybean software

@sgalchev: Changing the goalposts? You flat out stated the OP would brick his S4 if he attempted to downgrade. When called on it, you switched your argument to tripping the Knox flag. As he mentioned in his latest post, he had downgraded to Android 4.4.2 from Android 5.0.1, so it's likely his Knox flag is already tripped. Even if it wasn't, I can't comfirm whether the Knox flag will get tripped as my Knox flag was tripped when I bought my I9505. Tripping the Knox flag != bricking the S4.
@tdssmarty16: Keep in mind that while everything worked, it took two flashes of the ROM to do it, and I only kept it on 4.2.2 long enough to verify that the hardware and firmware issues I was having were resolved. I then went back to 4.4.2. In downgrading to 4.2.2 I went to sammobile.com and downloaded the 4.2.2 firmware from them. Other than that, I simply treated it as if I was doing an upgrade through Odin. Unlike going from Android 5.0.1 to Android 4.4.2, going from 4.4.2 to 4.2.2 should be a piece of cake.

Strephon Alkhalikoi said:
@sgalchev: Changing the goalposts? You flat out stated the OP would brick his S4 if he attempted to downgrade. When called on it, you switched your argument to tripping the Knox flag. As he mentioned in his latest post, he had downgraded to Android 4.4.2 from Android 5.0.1, so it's likely his Knox flag is already tripped. Even if it wasn't, I can't comfirm whether the Knox flag will get tripped as my Knox flag was tripped when I bought my I9505. Tripping the Knox flag != bricking the S4.
@tdssmarty16: Keep in mind that while everything worked, it took two flashes of the ROM to do it, and I only kept it on 4.2.2 long enough to verify that the hardware and firmware issues I was having were resolved. I then went back to 4.4.2. In downgrading to 4.2.2 I went to sammobile.com and downloaded the 4.2.2 firmware from them. Other than that, I simply treated it as if I was doing an upgrade through Odin. Unlike going from Android 5.0.1 to Android 4.4.2, going from 4.4.2 to 4.2.2 should be a piece of cake.
Click to expand...
Click to collapse
okay bro i will try to do it this way thanx for info

Hi I would appreciate alot if someone can teach me how to downgrade form 5.0 to 4.4.2 or at least 4.2.2 . I spent the whole day yesterday figuring out how to do it i'm not good with technology and I'm using a macbook. I'm using S4. Thank you.

Which model S4 do you have? Only certain models can be downgraded to 4.2.2.

Downgrade i9505
Strephon Alkhalikoi said:
Which model S4 do you have? Only certain models can be downgraded to 4.2.2.
Click to expand...
Click to collapse
I downgraded my i9505 from 4.4.2 to 4.2.2 but had no sound so I went back to kitkat.It is possible to downgrade but I don't know is it possible to be fully functional.

I did it long enough to both check my SIM tray at the time, and to unlock the device. I wasn't getting any signal (expected), but I didn't check sound. I do suspect that if the 4.2.2 modem is flashed a second time everything would work. The only indicator that you were ever on anything higher would be the warning the bootloader pops up on every reboot about SELinux.

No sound,no wifi
I forgot first time to say wifi also didn't worked.I don't care for my warranty because flag was already tripped and now my device is older than 2 years so I can try some solution If someone has one.

anyone active here? it's not possible to downgrade to jelly bean anymore as the bootloader is locked to downgrade max at 4.4 as 4.2 will not work at all
if anyone has a ideea on how to do it (some people did it) i would be verry happy if you could share that info

I have not seen a post where someone running a 4.4.2 or 5.01 bootloader had successfully downgraded the bootloader to 4.2.2

A few simple questions

I have 7 questions, I will +Thank you for all your answers.
1. I'm still on 4.4.2 [XXUFNB9], is that even the latest KitKat? Since people keep telling me to stay on KitKat, not to update to 5.0.1.
2. Second question, since my CSC is [NEEFNB2] which should be NEE region, that should mean that the latest 5.0.1 via OTA is [XXUHOD7] which was released on 2015-May-01. Isn't that outdated?
Source: http://www.sammobile.com/firmwares/database/GT-I9505/NEE/
3. Now if I look at the latest releases, starting from DBT region which is Germany and a lot of others, the latest 5.0.1 for the i9505 is [XXUHOH2] released 2015-September-01. Compared to my NEE region release date, my 5.0.1 update would be outdated right?
4. Last few questions, if I were to update to 5.0.1 via OTA, is going back to KitKat as easy as flashing PDA via Odin including the factory wipe in recovery? Will that trigger Knox?
5. Going back to KitKat from Lollipop I would still be using the Lollipop modem on KitKat, is that bad and why?
Source: http://forum.xda-developers.com/showpost.php?p=62947457&postcount=11
6. I've read a lot about Knox 0x1 and there are a lot of weird explanations about it.
Someone use to say is that you stop receiving OTA updates. Others say is that Knox can't make a container? Whatever that means.
Is the only negative thing Knox 0x1 that you lose your warranty? I dont have that anyway, so why all the fuss about 0x1 if it's only warranty?
7. What's the experience on the latest 5.0.1 [XXUHOH2] OR latest for NEE region [XXUHOD7] if someone has it?

Erroneous91 said:
I have 7 questions, I will +Thank you for all your answers.
1. I'm still on 4.4.2 [XXUFNB9], is that even the latest KitKat? Since people keep telling me to stay on KitKat, not to update to 5.0.1.
2. Second question, since my CSC is [NEEFNB2] which should be NEE region, that should mean that the latest 5.0.1 via OTA is [XXUHOD7] which was released on 2015-May-01. Isn't that outdated?
Source: http://www.sammobile.com/firmwares/database/GT-I9505/NEE/
3. Now if I look at the latest releases, starting from DBT region which is Germany and a lot of others, the latest 5.0.1 for the i9505 is [XXUHOH2] released 2015-September-01. Compared to my NEE region release date, my 5.0.1 update would be outdated right?
4. Last few questions, if I were to update to 5.0.1 via OTA, is going back to KitKat as easy as flashing PDA via Odin including the factory wipe in recovery? Will that trigger Knox?
5. Going back to KitKat from Lollipop I would still be using the Lollipop modem on KitKat, is that bad and why?
Source: http://forum.xda-developers.com/showpost.php?p=62947457&postcount=11
6. I've read a lot about Knox 0x1 and there are a lot of weird explanations about it.
Someone use to say is that you stop receiving OTA updates. Others say is that Knox can't make a container? Whatever that means.
Is the only negative thing Knox 0x1 that you lose your warranty? I dont have that anyway, so why all the fuss about 0x1 if it's only warranty?
7. What's the experience on the latest 5.0.1 [XXUHOH2] OR latest for NEE region [XXUHOD7] if someone has it?
Click to expand...
Click to collapse
The answer to all your questions:
You worry to much. Region is not that important. And who tells you to stay on Kitkat? I wouldn't want to run outdated software on my phone. So just upgrade and you can always downgrade. There are guides in the general section on how to do that. For questions about knox there is a whole thread about it. Also not really important in your case.
Even better would be to flash the CM so you are really on the latest Android version 5.1.1.

Hey,
these people told me not to update: http://forum.xda-developers.com/galaxy-s4/help/quick-q-update-phone-to-lollipop-t3163097
Thank you for your answer.
I am still open for suggestions if there are any, of not. I'll consider trying 5.0.1 soon and hopefully I'l like it.
EDIT:
I have updated to 5.0.1 [XXUHOD7] just now.
I can report my experience after some usage.

Erroneous91 said:
Hey,
these people told me not to update: http://forum.xda-developers.com/galaxy-s4/help/quick-q-update-phone-to-lollipop-t3163097
Thank you for your answer.
I am still open for suggestions if there are any, of not. I'll consider trying 5.0.1 soon and hopefully I'l like it.
EDIT:
I have updated to 5.0.1 [XXUHOD7] just now.
I can report my experience after some usage.
Click to expand...
Click to collapse
Why don't you try the GPE rom or a CM based rom. Way better then stock imo.

Lennyz1988 said:
Why don't you try the GPE rom or a CM based rom. Way better then stock imo.
Click to expand...
Click to collapse
Because for some reason this this one is actually running perfectly, I have no complains yet.
The thing is it is running better than my last KitKat rom, faster in opening apps and smoother scrolling without skipping frames as much.
Battery life? It's repporting 3 days left atm, so I suppose it's the same as it was on KitKat, but will see.