My Note 2 was on stock 4.1.2, never rooted or flashed anything. And I have upgraded to 4.3 via OTA.
Before downgrading, everything was fine in Download Mode.
Today, I downgraded back to stock 4.1.1 (from Sammobile), and in Settings, Device Status says Modified.
In Download Mode, KNOX Warranty Void: 1, Custom Binary Download: Yes - 1, System Status and Current Binary: Custom.
So I wonder why my phone is detected as it has been hacked when everything is stock.
KNOX by nature disables you from downgrading your firmware. By doing so you've tripped it and raised a flag of 0x1. It doesn't matter whether you were rooted or stock. It's all the same.
So I have read these 2 threads talking about how to downgrade the bootloader, making it KNOX free.
One is for AT&T model and the other is for international model.
On the AT&T thread, they are flashing the old bootloader from 4.1.2.
The files they are using are sbin (I don't know the extension), tz.img, sboot.bin, and param.bin.
I found sboot.bin and tz.img from the 4.1.2 stock firmware (downloaded from Sammobile).
http://forum.xda-developers.com/showthread.php?t=2500823
http://forum.xda-developers.com/showthread.php?t=2502464
Double-post. Deleted.
Related
I want the stock MK4 stock rom and a working bootloader without Knox (and prefer not to use the Wi-fi patch from Dr)
1: Flash MJ5 bootloader from odin
2: Download MK4 from sammobile (Hong kong)
3: Flash MK4 from odin and untick to flash "MK4 knox bootloder"
And now if i like to root the phone will the MJ5 bootloader break the knox to 0x1?
(i know the latest MK4 bootloader will change the knox status to 0x1)
Does anyone know if using the following will work with a rooted Sprint GSIII having taken the 4.3 OTA update running a custom ROM and having removed the Knox software??
http://forum.xda-developers.com/showthread.php?t=1904099
In download mode I do not have the Knox warranty void line...
Short answer...Do NOT flash that file. You'll have a fancy paperweight. You said you took the 4.3 OTA update meaning your custom rom and Knox apps removal has ZERO effect on the 4.3 KNOXED bootloader you have.
The 4.3 stock tar is here::[ROM][TAR] Stock MK3 Odin flashable
the md5 issue is resolved in that thread^^^
SGSIIIJB said:
Short answer...Do NOT flash that file. You'll have a fancy paperweight. You said you took the 4.3 OTA update meaning your custom rom and Knox apps removal has ZERO effect on the 4.3 KNOXED bootloader you have.
The 4.3 stock tar is here::[ROM][TAR] Stock MK3 Odin flashable
Click to expand...
Click to collapse
thanks for the help but getting the following error when attempting to load as instructed:
MD5 hash value is invalid
??
So like an idiot I upgraded to 4.3 without reading up on it first. I used ODIN to flash the 4.3 root66 version and my 'warrenty bit' changed to 1. From what I have read the way that I did it shouldn't have triggered that. I've been reading forum after forum in a way to reset the bit and I guess it is an efuse. With that being said does anyone have a way to successfully downgrade the bootloader to get rid of the Warrenty Bit 1? I don't care if it bricks the phone if I can send it in for warranty and get another one that is status 0.
I think you are out of luck. There is no way to reset that bit period.
Now if you tried to flash Root66 for UVDMD5, your phone for sure will brick. I am not sure if the Service personnel can salvage it.
I think Water damage may be covered by all carrier insurances.
I may have a problem too. I recently rooted my S3 with root66 4.3 stock rom from unrooted 4.1.2 with Odin. I don't see KNOX anywhere in the phone. The phone works but I just can't make or receive calls. The update probably updated the modem. Is it safe to downgrade it back to my original unrooted 4.1.2 using Odin? This is what i see in download mode:
PRODUCT NAME: SGH-T999V
CURRENT BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: Enabled
Warranty Bit: 0
BOOTLOADER RP SWREV: 1
If I can't downgrade the firmware, can I downgrade the modem? The modem maybe causing problems with making/receiving calls. I'm also worried if the BOOTLOADER line is related to KNOX.
cd964 said:
I may have a problem too. I recently rooted my S3 with root66 4.3 stock rom from unrooted 4.1.2 with Odin. I don't see KNOX anywhere in the phone. The phone works but I just can't make or receive calls. The update probably updated the modem. Is it safe to downgrade it back to my original unrooted 4.1.2 using Odin? This is what i see in download mode:
PRODUCT NAME: SGH-T999V
CURRENT BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: Enabled
Warranty Bit: 0
BOOTLOADER RP SWREV: 1
If I can't downgrade the firmware, can I downgrade the modem? The modem maybe causing problems with making/receiving calls. I'm also worried if the BOOTLOADER line is related to KNOX.
Click to expand...
Click to collapse
No you cannot downgrade with Odin.. What I suggest you do first is backup any files you want to keep, re-Odin the 4.3 firmware, after that reboot to recovery and do a factory reset and reboot.. If you still encounter problems them flash a 4.1.2 ROM.. That's pretty much the only way to downgrade, you can try downgrading modems if there's a different 4.3 modem for your device
Sent from my SGH-M919 using Tapatalk
Addition. You can flash a 4.1.2 Rom VIA RECOVERY ONLY. Do not flash it via Odin.
I might have made things worse by installing TWRP before reading the responses. The phone started updating on its own right after I flashed TWRP and rebooted. Now it says:
CURRENT BINARY DOWNLOAD: Yes (1 Count)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: Enabled
Warranty Bit: 1
BOOTLOADER RP SWREV: 1
I guess it was the KNOX bootloader from the root66 4.3 rom in the phone that detected the change and decided to update the phone plus change the counts. So probably there's no way of downgrading now and I would just have to deal with a rooted 4.3 which sucks. The phone can make calls/receive calls now but the signal is weak and constantly cuts out plus the battery drain is horrendous. Some apps won't even download to, or install or work with the phone.
Using TWRP for recovery of the 4.1.2 official stock rom would probably brick my phone since the bootloader will probably take over again.
Greetings!
I urgently need help to verify what files and in what order to flash to restore my GF's Note2:
It's a GT-7100 that is still on 4.1.1 and eMMC Brickbug Check app reports it as SDS vulnerable... original firmware, execpt for Exynos Abuse, SuperSU and AFwall+, but that was apparently enough to trigger "modified" state and so prevent OTA updates. Installing Wanam Exposed to hide modificatioon did not work, so we unrooted, but forgot to reverse Exynos Abuse fix. Now we're still unable to OTA, but without root as well
I think the next best step will be to flash to 4.3 via Odin and then apply saferoot from cosmyndemeter.
To prevent any warranty issues, I would prefer to keep the phone knox-free, which means that 4.4 update is not an option, and I need the botloader to keep to version mj5 or below.
I got N7100XXUEMK9_N7100VIAEML2_VIA.zip from sammobile.com, which seems applicable (region- and operator-wise), and BL_MJ5_DN3.rar for the unknoxed bootloader.
If I simply flash those two files, will that already trigger a reaction from knox (preventing any future BL-upgrades) or am I safe as long as the phone does not reboot between the two flash processes?
LordHelmchen138 said:
Click to expand...
Click to collapse
Here's what I know.sorry if i cant answer all.
-Stock firmwares from sammobile or other site already have a bootloader included with it, no need to flash other BL.
-Not sure if the bootloader from the MK9 is MJ5 or below, please search.
-Knox enabled bootloaders are upgradable, but can no longer have downgrade.
-If based from your search that MK9 base has a bootloader MJ5 or below, you are good to go.backup and flash via odin.
-Else, find an older rom base with BL MJ5 or below from sammobile.
Good luck. ^.^
Sent from my GT-N7100 using XDA Premium 4 mobile app
Well... I decided to go a longer way that seemed a bit safer:
- got N7100XXDLL4_N7100VIADLL2_VIA from sammobile, which is still exynos-abusable.
- rooted with exynosAbuse
- installed Mobile Odin
- flashed the aforementioned N7100XXUEMK9_N7100VIAEML2_VIA with Mobile Odin, relaxing in the knowlege that Mobile Odin will not flash the bootloader
- flashed the aforementioned mj5 bootloader only with Odin
- unsuccessfully flashed UPDATE-SuperSU-v1.94.zip with Mobile Odin. I guess this was stupid
- rooted with saferoot
result:
rooted phone on 4.3 , so far so good.
Phone Info app reports:
Code:
Knox Warranty Void: 0x0
Bootloader Version: N7100XXUEMJ5
Baseband Version: N7100XXUEMK9
PDA Version: N7100XXUEMK9
CSC Version: N7100VIAEML2
Only my noobishly overoptimistic attempt at rerooting is now visible:
Code:
CUSTOM BINARY DOWNLOAD: yes (1 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: custom
WARRANTY BIT: 0
Can anyone reassure that mj5 bootloader means that knox warranty void cannot trigger, so using triangle away is safe ? I'm still slightly worried that the bootloader simply does not display the knox bit, but that it is still 'primed' in the background and just waiting to blow up...
LordHelmchen138 said:
Code:
Knox Warranty Void: 0x0
Bootloader Version: N7100XXUEMJ5
Baseband Version: N7100XXUEMK9
PDA Version: N7100XXUEMK9
CSC Version: N7100VIAEML2
Only my noobishly overoptimistic attempt at rerooting is now visible:
Code:
CUSTOM BINARY DOWNLOAD: yes (1 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: custom
WARRANTY BIT: 0
Can anyone reassure that mj5 bootloader means that knox warranty void cannot trigger, so using triangle away is safe ? I'm still slightly worried that the bootloader simply does not display the knox bit, but that it is still 'primed' in the background and just waiting to blow up...
Click to expand...
Click to collapse
Knox warranty void 0x0 means the bootloader didn't trigger the Knox but honestly after a point we should all stop caring about Knox ( unless you use it for business purposes or still under warranty ). Now you can flash any custom KitKat ROM and be on Mj5 bootloader. Only thing is that phone won't charge when turned off ( draw back of mj5 and other jelly bean bootloaders ) only being on KK boot loader can charge your phone when turned off . here you got two options if you only flash nd3 bootloader after upgrading to custom KK ROM it will trigger Knox and it will show 0x1 or you can flash the official stock KK rom via odin that will flash the ND3 boot loader and knox remains 0x0 since its an official ROM . So it depends on you what do you plan on doing on your note II ,if you want to try newer ROMs or stick to 4.3 based ROMs
Sent from my GT-N7100 using Tapatalk
Well, the phone is not mine, and there's still about six months of warranty left. So yes, I still have to care about knox
As it stands, 4.3 and mj5 bootloader look fine, so it's only the flash counter and system :modified that I want to take care of.
Sent from my D5503 using XDA Free mobile app
I've been trying to unroot and go back to stock for a couple of days now with no luck. I was running latest Omni and TWRP. When I try to flash via Odin it says FAILED then reboot hangs on Samsung GN2 screen. When I go to "Downloading..." screen it shows:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
AP SWREV: A3
SW REV. CHECK FAIL. DEVICE: 3, BINARY: 1
I wish I could help but I am having a similar issue. If you have had any success with this please let me know what you have found. Good luck!
Y`all need to ODIN flash a firmware version that does not have the boot.IMG. You most likely have a firmware version that has a locked boot loader.
MK6 or the latest NE5 are such animals.
You also need to add more info for people to help. Like where Odin failed, why you are flashing back, what version of Odin, etc.
Makes it easier to tell you a possible solution.
I had no issues coming back to stock after running pretty much all the 4.4 AOSP roms, going to sell the device so I wanted to sell it stock.
I was on the MC3 or LJ2 bootloader, not sure which one but I rarely, if ever, change radios. I first went back to TW 4.1 using Odin and following the steps on this thread. http://forum.xda-developers.com/showthread.php?t=2275844