I have the latest 4.3 firmware (UVUEMJC). Anyway, I wanted to see if I could root via CF-AutoRoot. However, Odin for some reason is not detecting the phone in download mode. Interestingly, the phone is detected by the computer in either Recovery mode or when in TouchWiz. I think Knox may have something to do with this.
Odin Mode
Product Name: SGH-T999
Custom Binary Download: Yes (2 counts)
Current Binary: Samsung Official
System Status: Custom
QualComm SecureBoot: Enable
Warranty Bit: 1
Bootloader RP SWREV: 1
So how did you trip your Counter ? Was it before you did the Stock UVUEMJC upgrade ? Anyway, what precise errors do you get when you say ODIN does not detect ?
Also have you considered the leaked 4.3 build that has KNOX removed ? Doc Holliday has a thread for that.
Vigz said:
I have the latest 4.3 firmware (UVUEMJC). Anyway, I wanted to see if I could root via CF-AutoRoot. However, Odin for some reason is not detecting the phone in download mode. Interestingly, the phone is detected by the computer in either Recovery mode or when in TouchWiz. I think Knox may have something to do with this.
Odin Mode
Product Name: SGH-T999
Custom Binary Download: Yes (2 counts)
Current Binary: Samsung Official
System Status: Custom
QualComm SecureBoot: Enable
Warranty Bit: 1
Bootloader RP SWREV: 1
Click to expand...
Click to collapse
Knox is not installed.
Issue is likely driver related. What version are you using?
Just an FYI, this is the same guy from the OTA and Debrick threads. His post was a 2:26 (my time EST), so chances are he has continued his question since in one of those threads.
Woody said:
Just an FYI, this is the same guy from the OTA and Debrick threads. His post was a 2:26 (my time EST), so chances are he has continued his question since in one of those threads.
Click to expand...
Click to collapse
Thanks Woody. Unsubscribed and moving on.
Related
Hi,
I had stock 4.3 firmware on my att i747 galaxy s3, then I decided to flash cyanogenmod. everything went well but i dont really like it.
Now I want to go back to stock. I tried flashing the stock rom with odin but it fails and it says this on the phone:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: Yes (2 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER RP SWREV: 2
SW REV CHECK FAIL : Fused 2 > Binary 0
The android version it shows is 4.3.1 and im able to use it normally with the cyanogenmod.
What can I do to flash a stock rom back?
EDIT: used triangle away and the custom binary download says "no" now and the current binary says "samsung official" but still get the same problem.
Thank You
Watch out with the double threads. Some people can get cranky about it.
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.
So I recently bought a galaxy s3 from a friend and tried rooting it today, but something went horribly wrong and it won't work.
It tells me "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." I have tried doing that and I can not get it to work. The phone won't even connect to Kies... HELP
This is what it says at the top of the screen.
ODIN Mode
Product name: SPH-L710
Custom Binary Download: Yes (1 counts)
Current Binary: Custom
SYSTEM STATUS: Official
Dualcomm Secureboot: Enable
Warranty Bit: 0
Bootloader RP SWREV: 1
PLEASE HELP SOON!!!
Root/Recovery via ODIN stuck at recovery.img push
Jezdan said:
So I recently bought a galaxy s3 from a friend and tried rooting it today, but something went horribly wrong and it won't work.
It tells me "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." I have tried doing that and I can not get it to work. The phone won't even connect to Kies... HELP
This is what it says at the top of the screen.
ODIN Mode
Product name: SPH-L710
Custom Binary Download: Yes (1 counts)
Current Binary: Custom
SYSTEM STATUS: Official
Dualcomm Secureboot: Enable
Warranty Bit: 0
Bootloader RP SWREV: 1
PLEASE HELP SOON!!!
Click to expand...
Click to collapse
Bump!
I am using the GS3 Toolkit v7.5.1 on a Sprint SPH-L710 totally stock untouched ROM.
I kinda made an alteration by adding the TWRP Recovery v2.6.3.1 for this Sprint GS3 variant, and renamed it to the TWRP recovery included with the Toolkit i.e. TWRP 2.5.0.0
Now while going through the Root/Recovery (ALLINONE) option, when Odin comes up, it sends the boot.img fine, but is now stuck on sending down recovery.img.
But I don't know enough about Odin or the GS3, to know if I can just shut down Odin, and it'll trigger the phone to reboot and I can not be sneaky, replace the original recovery, and try again?
This is what my phone says on the "Downloading..." screen
Code:
[COLOR="Red"][B]ODIN Mode[/B][/COLOR]
Product name: SPH-L710
Custom Binary Download: [B][COLOR="Green"]No[/COLOR][/B]
Current Binary: SAMSUNG Official
SYSTEM STATUS: Official
Qualcomm Secureboot: ENABLE
Can I shut down Odin, and manually reboot the phone to the Download mode, and repeat the process?
PLEASE Help!
I may need to send my phone in to Bell or Samsung, and I want to make sure it's back to its original, untampered state. I have rooted it twice before, so first I want to make sure my Flash Counter is at 0. I went into Download mode and I have no idea what any of the stuff written there means so I can't tell whether the Flash Counter has been tripped or not.
So two questions:
1: How do I tell whether I need to reset the flash counter, and...
2: How do I reset the flash counter, if I need to (Will Triangle Away from Play Store work with a 4.4.2 device??)
Thanks
If you are stock and 4.3 or above, your Knox has more than likely been tripped by root so warranty is void. Samsung won't touch it. See if you can post a screenshot of download mode and the more knowledgeable guys can let you know for sure.
pre4speed said:
If you are stock and 4.3 or above, your Knox has more than likely been tripped by root so warranty is void. Samsung won't touch it. See if you can post a screenshot of download mode and the more knowledgeable guys can let you know for sure.
Click to expand...
Click to collapse
The first time I rooted I was on 4.2 using the no-tripping-flash method found on this forum. The second time I rooted was last week when I used TowelRoot, so I'm 99.9999999% sure that tripped the counter. I'm currently running the stock Bell 4.4.2 ROM that they pushed back in June, with TWRP recovery (I was planning on flashing CarbonROM, but that plan has changed)
Here's what it says in download mode:
Product Name: SGH-I747
Current Binary: Samsung Official
System Status: Official
Qualcomm Secureboot: Enable
Warranty Bit: 1
Bootloader AP SWERV: 2
nubreed000 said:
The first time I rooted I was on 4.2 using the no-tripping-flash method found on this forum. The second time I rooted was last week when I used TowelRoot, so I'm 99.9999999% sure that tripped the counter. I'm currently running the stock Bell 4.4.2 ROM that they pushed back in June, with TWRP recovery (I was planning on flashing CarbonROM, but that plan has changed)
Here's what it says in download mode:
Product Name: SGH-I747
Current Binary: Samsung Official
System Status: Official
Qualcomm Secureboot: Enable
Warranty Bit: 1
Bootloader AP SWERV: 2
Click to expand...
Click to collapse
You tripped knox and the warranty bit has been changed from 0 to 1. Samsung may or may not provide warranty service.
audit13 said:
You tripped knox and the warranty bit has been changed from 0 to 1. Samsung may or may not provide warranty service.
Click to expand...
Click to collapse
So I'm basically SOL? A quick search on Google showed that it's not possible to reset Knox.
Any way I can revert the phone to stock unrooted at least? I'm having trouble finding a Odin-flashable 4.4.2 Bell file (the 2 links I found are dead). Could I use a 4.3 file to flash?
No way to reset it that I know of.
It is an refuse that gets tripped.
nubreed000 said:
So I'm basically SOL? A quick search on Google showed that it's not possible to reset Knox.
Any way I can revert the phone to stock unrooted at least? I'm having trouble finding a Odin-flashable 4.4.2 Bell file (the 2 links I found are dead). Could I use a 4.3 file to flash?
Click to expand...
Click to collapse
http://sammobile.com/firmwares
i had my s3 i747m on cm13. i was having a lot of problems with bluetooth. so i tried going back to stock firmware and i bricked my phone. i can still access download mode.
with odin running as admin or not, this is what it says when i try to install stock rom in download mode:
ODIN MODE
PRODUCT NAME: SGH-I747M
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER RP SWREV: 2
SW REV CHECK FAIL : Fused 2 > Binary 0
i've tried looking for solutions, but all say the same thing...which is to use odin and install the stock rom file.
i had twrp recovery installed if that helps.
sal82 said:
i had my s3 i747m on cm13. i was having a lot of problems with bluetooth. so i tried going back to stock firmware and i bricked my phone. i can still access download mode.
with odin running as admin or not, this is what it says when i try to install stock rom in download mode:
ODIN MODE
PRODUCT NAME: SGH-I747M
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER RP SWREV: 2
SW REV CHECK FAIL : Fused 2 > Binary 0
i've tried looking for solutions, but all say the same thing...which is to use odin and install the stock rom file.
i had twrp recovery installed if that helps.
Click to expand...
Click to collapse
can you re-flash twrp recovery?
ethanchow said:
can you re-flash twrp recovery?
Click to expand...
Click to collapse
OMFG!! thank you!! it's working again with cm13! i was pulling my hair out lol.
i just reflashed twrp with odin and it started to work. i guess it was just the recovery files damaged?
sal82 said:
OMFG!! thank you!! it's working again with cm13! i was pulling my hair out lol.
i just reflashed twrp with odin and it started to work. i guess it was just the recovery files damaged?
Click to expand...
Click to collapse
Yes, sometimes stock images won't flash because the bootloader version is lower than the one you have.