Database Users

Upgrading/Downgrading the Note 3

Hi, quick question. I read that with Note 3, because all the stock ROMs are knox-enabled, I can upgrade by flashing via Odin (even if I have Knox tripped).
So this:
If you try to downgrade to KNOX-disabled system(MGA for example) your device will be flaged as KNOX Void Warranty 0×1 and will get a special lock – you won’t be able to update to any KNOX-enabled firmware even by ODIN.
Click to expand...
Click to collapse
doesn't apply because there aren't knox-disabled firmwares.
What about if I downgrade using Odin? By flashing an older firmware? If I'm not on the newer bootloaders I can, right? But will Knox be tripped?
I also read that if you try to flash a non-Knox firmware onto a Knox phone you'll be bricked. I can't remember which thread/what circumstances, so hoping someone can shed some light on that.
Lastly, if I'm on unrooted stock firmware, can I use URDLV to "patch" the newest firmware, then flash it to get the rooted latest firmware WITHOUT the newer bootloader and WITHOUT tripping knox? So I can choose to downgrade should the new firmware has any problems.

Situation on trip the Knox or not: (No idea on downgrade as I never try, I think it won't under same bootloader version)
Flash any stock ROM including Kitkat officially or not with odin without rooting - won't trip knox.
Officially phone came with MJ1 or older - root with URDLV won't trip knox.
Officially phone came with MJ7 or later - root with any method will trip knox.
Officially phone came with MJ1 but later updates to MJ7 with OTA/KIES/PC Odin and later - root with any method will trip knox.
Officially at MJ1 and rooted and update to any firmware excluding KitKat ROM using Mobile Odin Pro only - root will remain and won't trip the knox.
Install any custom recovery and custom kernel will trip the knox.
Update KitKat via Mobile Odin Pro (MOP) without trip the Knox:
Your current bootloader is not newer than MJ1.
Load Official Poland ROM in MOP
Enable EverRoot, Choose option "Download mode" in after flashing. Start flashing.
After booted into Download Mode, connect your phone to your computer and run PC Odin 3.09.
Load this bootloader http://forum.xda-developers.com/showpost.php?p=49425513&postcount=352 in the BL section
Check Phone Bootloader Update and F.Reset.time, un-check Auto Reboot and Start Flashing.
When Odin says RESET!, switch off your phone and reboot normally.

How to flash prerooted ROM to new android 5 device without root and keep knox 0x0?

Hi all,
I want to install ROM by _alexndr on a new G900F. I want to keep KNOX 0x0, so I need root to flash this ROM using flashfire.
However, the device came with android 5 when I bought it, so towelroot does not work. If I understood correctly, I have to flash stock 4.4.2 firmware (where do I get it? which tool to use for flashing? Just flash, or other things to take care of?), then I can use towelroot and flash ROM by _alexndr with flashfire. Did I miss anything important?

Get the ROM and ODIN the flashing tool from sammobile .com firmware section
Instructions under the download (Free account might be needed to download the ROM)

Can I just flash the old 4.4.2 firmware over the current 5.0 firmware, or do I have to consider something else?

I've flashed KK over LP before, and first boot didn't boot, flashed it again the same way, and it booted fine
Might need to factory reset before/after flashing if you have problems

I337UCUGOC3 bootloader locked, want to update to I337UCUGOK2 to unlock bootloader

I hit on UPDATE on the phone for an OTA update but it only says UNABLE TO CONNECT AT&T SERVER. When I bought it, it had 5.0.1 (I337UCUGOC3) out of the box. Searching on internet says that is bootloader locked (so I cant do anything).
- Can I Update to I337UCUGOK2 and bootloader will be unlocked (I mean, will I be able to do it)?
- Does anyone know where can I grab I337UCUGOK2 for offline install and is it ODIN safe to update it (remember I have I337UCUGOC3 bootloader locked)?
please help

Once the bootloader is locked, it will always be locked until someone finds a way to unlock it. Updating the bootloader will not allow it to be unlocked.

cybercuate said:
I hit on UPDATE on the phone for an OTA update but it only says UNABLE TO CONNECT AT&T SERVER. When I bought it, it had 5.0.1 (I337UCUGOC3) out of the box. Searching on internet says that is bootloader locked (so I cant do anything).
- Can I Update to I337UCUGOK2 and bootloader will be unlocked (I mean, will I be able to do it)?
- Does anyone know where can I grab I337UCUGOK2 for offline install and is it ODIN safe to update it (remember I have I337UCUGOC3 bootloader locked)?
please help
Click to expand...
Click to collapse
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.

help... I want to RMA it
sway8966 said:
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
Click to expand...
Click to collapse
Everywhere says I need a kitkat rom as base.
My s4 came with 5.0.1 with OC3 and bootloader locked out of the box. I tried some post where says I can flash TWRP and CWM but my phone stucked on bootloops. Then I managed to get back to stock rom and now when I want to turn it on it says " SAMSUNG (and lower on the screen) Custom"
Camera began to fail and I want to return it as RMA but I was looking to reset the flash counter but every post I read is that OC3 bootloader locked users are just doomed.
Do you know a method that I can do for reset that counter?
Camera dont focus anymore and I tried all the posts about safemode, etc.

cybercuate said:
Everywhere says I need a kitkat rom as base.
My s4 came with 5.0.1 with OC3 and bootloader locked out of the box. I tried some post where says I can flash TWRP and CWM but my phone stucked on bootloops. Then I managed to get back to stock rom and now when I want to turn it on it says " SAMSUNG (and lower on the screen) Custom"
Camera began to fail and I want to return it as RMA but I was looking to reset the flash counter but every post I read is that OC3 bootloader locked users are just doomed.
Do you know a method that I can do for reset that counter?
Camera dont focus anymore and I tried all the posts about safemode, etc.
Click to expand...
Click to collapse
Flashing TWRP and CWM is for the AT&T S4 with older bootloader (MDL, MDB). After that two firmware versions the bootloader is locked.
For AT&T S4 the last full firmware released is NB1. After that they released incremental updates via OTA. That is why you need kitkat (NB1) as base.
For NB1, Muniz uploaded two firmwares. One is the stock and the other is rootable stock. Try the stock one and see you still have the custom symbol.
To reset the counter, there is an app calls Triangle away by Chainfire. However, it does not work on AT&T S4 with locked bootloader.

Trying Odin-Stock NB1
sway8966 said:
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
Click to expand...
Click to collapse
sway8966 said:
Flashing TWRP and CWM is for the AT&T S4 with older bootloader (MDL, MDB). After that two firmware versions the bootloader is locked.
For AT&T S4 the last full firmware released is NB1. After that they released incremental updates via OTA. That is why you need kitkat (NB1) as base.
For NB1, Muniz uploaded two firmwares. One is the stock and the other is rootable stock. Try the stock one and see you still have the custom symbol.
To reset the counter, there is an app calls Triangle away by Chainfire. However, it does not work on AT&T S4 with locked bootloader.
Click to expand...
Click to collapse
Thanks. I'll try Odin it with the stock rom from your link. I'll post news here when it finish flashing

1st part - Success
I'm on 4.4.2 NB1, flash counter back to normal but still bootloader locked
Now I have to go back to OC3 to RMA it.
OTA does nothing, smartswitch shows no updates neither kies.
I'll have to Odin it back to OC3
Can I have some help?

And Success. I'm back on stock OC3 no root.
time to RMA
- camera still doesn't focus
- boot screen is back to normal but when in odin mode the counter shows 0x1
- sometimes shows "sim card could not be detected" or similar messages and force me to restart the phone (just happend 2 times until now, never happend before)
I followed this thread
http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
Post 2
Thanks to sway8966

Can I use Odin to go right from 4.4 to 5.0?

I unrooted my phone and flashed it back to NI2 using Odin and wiped all my data. Can I, while still in this mode, flash the latest stock rom with odin (Lollipop BPB1)?

doncaruana said:
I unrooted my phone and flashed it back to NI2 using Odin and wiped all my data. Can I, while still in this mode, flash the latest stock rom with odin (Lollipop BPB1)?
Click to expand...
Click to collapse
If you want the latest stock rom (unrooted) just take the Ota or you can download and Odin. If you need root rom , just root , install recovery and use safestrap and install the latest root pb1 rom.

doncaruana said:
I unrooted my phone and flashed it back to NI2 using Odin and wiped all my data. Can I, while still in this mode, flash the latest stock rom with odin (Lollipop BPB1)?
Click to expand...
Click to collapse
You can, but then you can never downgrade back to NI2.
If instead you want to retain the ability to downgrade,you can either 1) root the NI2, install SafeStrap, and then install a rooted PB1 ROM, or 2) Use Odin to flash a modified PB1 stock image that has a BOD5 bootloader.

Galaxy s4 att stuck on screen with costum and a padlock

Okay, here is the deal. I was trying to install a costum rom on my att galaxy s4. What I did was I rooted it using king root and tried to flash a rom through rom toolbox, but I believe it was just going to take me to my recovery. After that the screen got stuck on the costum screen with the padlock, and only seems to turn on with a charger plugged into it. I am on 5.0.1 lollipop and have managed to flash the original recovery, but any stock rom I try to flash using Odin fails by saying complete thread failed or something like that, and says on my phone binary 1 or something like that. I really need help on where to start.
Thanks

What is the exact Odin error?
AT&T never released a full firmware for flashing via Odin beyond 4.1.2. Look here for a possible solution: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
Once the phone is running a 4.3 or higher bootloader, the bootloader is locked and custom ROMs can't be installed unless the custom ROM is based on a stock ROM.

There's an ODIN flashable Android 4.2.2 MDL bootloader tar file out there somewhere too.

If the bootloader is locked, and it sounds like it is since it's running 5.01, Odin will not be able to flash a 4.2.2 ROM or bootloader.

audit13 said:
If the bootloader is locked, and it sounds like it is since it's running 5.01, Odin will not be able to flash a 4.2.2 ROM or bootloader.
Click to expand...
Click to collapse
Are there any other options, or should I just give up on it?

Look at this thread: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814.
Pay attention to this part of the post which may help:
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+), root with Towelroot, then proceed with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/show...10&postcount=2​

audit13 said:
Look at this thread: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814.
Pay attention to this part of the post which may help:
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+), root with Towelroot, then proceed with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/show...10&postcount=2​
Click to expand...
Click to collapse
I finally fixed it. I had downloaded that rom before, but it hadn't worked. I decided to try it again and used a different USB port and it worked! Thanks for the help!