So lots of bad things have happened while trying to install a rom to my note 3. I had it rooted, with the safestrap bootloader installed, but then I tried to upload the Dynamic Kat rom but it when it went to boot it just had a blue flashing light. I then tried to restore through download mode and now it is saying
ODIN MODE
PRODUCT NAME: SM-N900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION ENABLE
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So I went through Odinv 3.09 and tried to flash back to stock using N900AUCUBMI9, but I keep getting failed messages through that. I also downloaded another program that was a one-click odin based restore but that also gave the same fail message. I eventually tried to go through Kies 3 & Kies but both said my device was not compatible with it. I am at a loss.
When trying to use odin I get this.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> One Click Downloader Mode
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
tomdrumtomthumb said:
So lots of bad things have happened while trying to install a rom to my note 3. I had it rooted, with the safestrap bootloader installed, but then I tried to upload the Dynamic Kat rom but it when it went to boot it just had a blue flashing light. I then tried to restore through download mode and now it is saying
ODIN MODE
PRODUCT NAME: SM-N900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION ENABLE
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So I went through Odinv 3.09 and tried to flash back to stock using N900AUCUBMI9, but I keep getting failed messages through that. I also downloaded another program that was a one-click odin based restore but that also gave the same fail message. I eventually tried to go through Kies 3 & Kies but both said my device was not compatible with it. I am at a loss.
When trying to use odin I get this.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> One Click Downloader Mode
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
UPDATE:
Through Odin, I have flashed just the .pit file. This allowed me to boot back into the stock OS. However, the stock OS is very buggy (Direct Pen Input has stopped x10) and various other problems.
The problem is now, that I still can't flash the stock OS through Odin. I just keep getting fails. Any idea why?
What baseband version does your device show in Settings/General/About Device?
andygev35 said:
What baseband version does your device show in Settings/General/About Device?
Click to expand...
Click to collapse
I don't know, because now its stuck in a bootloop.... it should be the baseband version for the stock firmware at 4.3 though. So it should've been N900AUCUBMI9.
I could be wrong here, but isn't DynamicKat based on kitkat? That would make it incompatible with 4.3. You may need to just Odin to stock kitkat 4.4.2. (NOT 4.4.4) Then you can use safestrap 3.75 and load DynamicKat.
http://forum.xda-developers.com/showthread.php?t=2703006
Use the four-file restore method and use the download links I provided in the OP.
andygev35 said:
I could be wrong here, but isn't DynamicKat based on kitkat? That would make it incompatible with 4.3. You may need to just Odin to stock kitkat 4.4.2. Then you can use safestrap 3.75 and load DynamicKat.
http://forum.xda-developers.com/showthread.php?t=2703006
Click to expand...
Click to collapse
I did flash to dynamic kat from 4.3 which resulted where I couldn't boot. But then I restored to 4.3. (It was broken as I said, something about the pen not working and lots of lag). The note 3 was on 4.3 to begin with. Right now I'm trying to get my 4.3 to work but Odin just gives me fail messages for when I try to flash 4.3. Flashing the BL and AP end in errors. Flashing everything else gives a pass.
The only thing I know to try is to update to NC2 (4.4.2) via Odin. Maybe someone else knows how to restore to JB.
andygev35 said:
I could be wrong here, but isn't DynamicKat based on kitkat? That would make it incompatible with 4.3. You may need to just Odin to stock kitkat 4.4.2. (NOT 4.4.4) Then you can use safestrap 3.75 and load DynamicKat.
http://forum.xda-developers.com/showthread.php?t=2703006
Use the four-file restore method and use the download links I provided in the OP.
Click to expand...
Click to collapse
Alright, I did this and it worked! Its on kitkat now! Thank you!
Related
Hi,
I have downloaded the latest version of De La Vega for my AT&T Note 3. (Just FYI, I dont know if it makes a difference, but my phone did the recent AT&T update) After unzipping the folder, I ran the N900AUCUBMI9_OneClickBin.exe file and got this message on the application:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> One Click Downloader Mode
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
Also, I noticed on my phone that in ODIN Mode that it says "SW REV CHECK FAIL Fused 2 > Binary 1. In order to restart my phone, I have to pull out the battery. I have tried Kingo without any success. I would love to root my phone and also install BobCat Rom but I dont understand why I cant root my phone. Any help is appreciated.
shamlyn said:
Hi,
I have downloaded the latest version of De La Vega for my AT&T Note 3. (Just FYI, I dont know if it makes a difference, but my phone did the recent AT&T update) After unzipping the folder, I ran the N900AUCUBMI9_OneClickBin.exe file and got this message on the application:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> One Click Downloader Mode
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
Also, I noticed on my phone that in ODIN Mode that it says "SW REV CHECK FAIL Fused 2 > Binary 1. In order to restart my phone, I have to pull out the battery. I have tried Kingo without any success. I would love to root my phone and also install BobCat Rom but I dont understand why I cant root my phone. Any help is appreciated.
Click to expand...
Click to collapse
You cannot odin mi9 over mj5 you will end up with mi9 rom and mj5 bootloaders which will give you problems. If you have already done this you can flash the pit file only and possibly save yourself however this hasnt worked for everyone. Search the forum there is a thread with the pit file available. Kingo will root your phone but by trying to dowmgrade you have other issues to fix first. The bootloadera do not allow themself to be downgraded
---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------
Also idk what you are thinking but we do not hqve any custom roms or recovery available for the att note 3 yet due to the locked bootloaders and other security methods used by att
I lost root after update but I just went to recovery mode did a factory reset and supersu was in my system apps. So I went to unknown sources and turned on went back to supersu and it works I have full root. I installed several apps that require root access and they installed fine and everything works perfect
khoury1 said:
I lost root after update but I just went to recovery mode did a factory reset and supersu was in my system apps. So I went to unknown sources and turned on went back to supersu and it works I have full root. I installed several apps that require root access and they installed fine and everything works perfect
Click to expand...
Click to collapse
Is there an easier solution which does not require a factory wipe?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Not that I know of
Kingo work fine for me after the update. What version of Kingo are you using?
I didn't use kingo...I tried but it keep failing
Galaxy SIII I9305 shows up with not booting, getting stuck at the SIII logo.
Does the same when trying to get into recovery, so I tried to flash it with Odin.
Flash screen says:
Odin Mode
Product Name: GT-I9305
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Knox Warranty Void: 0
RP SWREV: A2
Click to expand...
Click to collapse
I tried to flash it with the latest packages from Sammobile, but no matter what I try, Odin always fails right away when flashing boot.img... any idea what the problem might be, or what I'm doing wrong?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXUENE4_I9305H3GENE1_I9305NEUEML2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Centrumgsm said:
Galaxy SIII I9305 shows up with not booting, getting stuck at the SIII logo.
Does the same when trying to get into recovery, so I tried to flash it with Odin.
Flash screen says:
I tried to flash it with the latest packages from Sammobile, but no matter what I try, Odin always fails right away when flashing boot.img... any idea what the problem might be, or what I'm doing wrong?
Click to expand...
Click to collapse
stupid question, but did you go in to download mode when flashing? thats by pressing menu button + volume down button + power button. then press volume up to agree with download mode and then flash with odin. And make sure you have all drivers installed
klemen241 said:
stupid question, but did you go in to download mode when flashing? thats by pressing menu button + volume down button + power button. then press volume up to agree with download mode and then flash with odin. And make sure you have all drivers installed
Click to expand...
Click to collapse
I did. As far as I can tell, I did everything according to the guides.
[edit] I also managed to flash a different I9305 without problem, so I'm sure it's not driver or flash file related. There is something with this specific phone that prevents flashing.
I've seen a "rescue firmware" for the I9300 with separate PDA, MODEM and CSC (+.pit) files for when the regular stock firmware wouldn't flash, and I was wondering if such a thing exists for the I9305 or if there is a guide on how I could make one.
Try to get a PIT file for the i9305 and add it to ODIN. If you don't do this, ODIN extracts the PIT from the device, and that might be corrupted.
daedric said:
Try to get a PIT file for the i9305 and add it to ODIN. If you don't do this, ODIN extracts the PIT from the device, and that might be corrupted.
Click to expand...
Click to collapse
Can't brick the device much more than it already is, right? I tried it, but it just gets stuck here:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
Click to expand...
Click to collapse
I got bored after 15 minutes, turned off the target, turned on the target, no change, still the same error when flashing.
Thought about the Knox bootloader preventing me from updating it, but that usually gives me some kind of error message right on the flash screen. Plus I'm using the latest images, and the other I9305 also says "SWREV A2", so that shouldn't be a problem.
This looks more and more like a motherboard replacement...
All i have to say is, good luck. Things don't look good.
Try to flash just a recovery via ODIN. You'll kiss knox goodbye, but we're out of options.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9305/
daedric said:
Try to flash just a recovery via ODIN. You'll kiss knox goodbye, but we're out of options.
Click to expand...
Click to collapse
Tried it, no go. Same error, still won't boot into recovery. On the upside, it didn't trip Knox either
Ok, just for good measure, let's get down to the basics.
Questions:
1. What type of USB cable are you using? Can you try another?
2. Is the USB cable connected directly to the computer , or via HUB / Front ports ?
3. Have you tried cleaning the usb port on the device ?
I've covered all the basics, even tried another computer. Same results.
I couldn't find a solution, ended up sending the phone for a motherboard replacement. Thanks for the suggestions, everyone!
I did something stupid I know and I have looked everywhere and seem to find only info about rooted fixes Here is the steps that now have me brickked:
Started with 4.4.1 Rooted
Flashed via Oden 4.4.2 Stock
Then Did OTA updates to 5.1.1
Tried To Revert to 4.4.2 Stock Via ODEN - Phone Said Firmware Error Load KIES and restore... never worked again
Tried Loading G900A_OC4_Stock_Partitions.tar.md5 got me to Black and white Samsing Logo Nothing Else
I dont care what I get I just need a phone, HELP!!!!!
Flash the 5.0 file and you will be good once you upgrade to lollipop you can't go back to 4.4.4 after upgrading and there is no way to go back after
Sent from my SAMSUNG-SM-G900A using Tapatalk
I have looked for 5.0 files where might I find one?
Tried this G900AUCU3BOC4_OneClick
but it fails and goes to SW REV FAIL : [aboot]Fused 4 > Binary 3
On Oden it says
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> One Click Downloader Mode
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004>
<ID:0/004>
<OSM> All threads completed. (succeed 0 / failed 1)
ThanksTons!
Since you did OTA updates, your bootloader has been updated and you can NOT revert back to older version. You basically need to reflash 5.1.1 firmware and stay there. Try to restore using Kies application.
LoSt180 said:
Since you did OTA updates, your bootloader has been updated and you can NOT revert back to older version. You basically need to reflash 5.1.1 firmware and stay there. Try to restore using Kies application.
Click to expand...
Click to collapse
Again tried Kies, Kies 3, and the new smart swap, nothing allows me to complete this they all say no repair option available when tools and emergency recovery is selected. Tried initialization and it tried v 4.4.2 which crashes.
HELP!!
You should be able to use ODIN and the link to the 5.1.1 firmware in the top of this post http://forum.xda-developers.com/att...w-to-update-to-g900aoi5-5-1-unrooted-t3235774
Did you figure out what to do? I'm in the same boat. My phone boots to "Firmware Upgrade encountered an issue". Kies does not find the phone. I was on OF3 trying to downgrade to stock ROM. Link posted above does not have ODIN flashable files except for bootloader it seems.
Found out how to go back to working phone by flashing file at the end of first post here (http://forum.xda-developers.com/att...w-to-unbrick-flash-to-stocknce-g900a-t3077652)
Mine still is bricked did anyone have a fix?
This is the OI5 files. Try and see if these work in Odin.
http://forum.xda-developers.com/showthread.php?t=3360699
Sent from my SAMSUNG-SM-G870A using Tapatalk
Ok guys, so I flashed 5.1.1 on my phone but I lost root. So I decided to root using the Skipsoft Toolkit. I think it tried to install a bootloader (pretty sure it did). Before this I tried to use the chainfire root but didnt work. ok So then the phone started boot-looping and I decided to flash 4.4.4 back on. But now Odin keeps giving me this error
Code:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1100)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
On the phone side the error I'm getting is this:
Code:
UDC START
SW REV CHECK FAIL : [ABOOT]Fused 2 > Binary 1
[1] eMMC write fail: ABOOT
Idk what to do at this point. I'm assuming I have to flash the boot-loader right?
If I could get some advice, so I don't brick my phone further.
Please please please, help! v__v
If you mean latest 5.1.1 you most likely have updated Samsung kernel security that won't let you downgrade bootloader, you need to flash current stock firmware to recover your device.
Pp.
PanchoPlanet said:
If you mean latest 5.1.1 you most likely have updated Samsung kernel security that won't let you downgrade bootloader, you need to flash current stock firmware to recover your device.
Pp.
Click to expand...
Click to collapse
I tried flashing 5.1.1 But to no avail. Anything else I could do?
I had a similar problem with my note 3. What in did was I backed up my sd card and wiped it, redownloaded stock bootloader and firmwares, and used a different usb cable and port . Then odin worked like charm
My friend ended up putting 4.4.4 on it somehow. Maybe it was just an issue with my computer? Thank you guys for your suggestions btw. I tried all of them.
ChameleonQS said:
My friend ended up putting 4.4.4 on it somehow. Maybe it was just an issue with my computer? Thank you guys for your suggestions btw. I tried all of them.
Click to expand...
Click to collapse
Do you happen to have the link to the 4.4 build? I'm trying to downgrade from 5.1.1 as well
For the past couple of days I've been unable to unroot my device using Odin, which I have done many of times on the past. I went to Sammobile and got the latest firmware to flash back to stock, but everytime I attempt to do so the process Fails. USB Debugging is enabled so I don't have a clue what the problem could be. I will list some general information as well as the results of the Odin process below:
Baseband Version: N910TUVUD0K2
Odin process result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910T3UVU1DOK2_N910T3TMB1DOK2_N910T3UVU1DOK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks
Updated: I've stumbled across a thread here on XDA which has a mirror link to Stock TW Firmware/Bootloader/Modem N910TUVU2DOK2, and after flashing this mirror link using Odin... my phone now is unrooted and back to stock. Many thanks to ShrekOpher for posting the mirror link and here is a link to his post: http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
Same issue
I just posted about this same issue a couple of days ago, if you go to my only post ive done so far you can see how we are in the same boat. What were you using before you got to your problem, which custom ROM?
I had this problem on the note edge. What helped me was flashing cwm recovery and wiping everything
Trebor313 said:
For the past couple of days I've been unable to unroot my device using Odin, which I have done many of times on the past. I went to Sammobile and got the latest firmware to flash back to stock, but everytime I attempt to do so the process Fails. USB Debugging is enabled so I don't have a clue what the problem could be. I will list some general information as well as the results of the Odin process below:
Baseband Version: N910TUVUD0K2
Odin process result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910T3UVU1DOK2_N910T3TMB1DOK2_N910T3UVU1DOK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks
Click to expand...
Click to collapse
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...
Catfish197621 said:
I just posted about this same issue a couple of days ago, if you go to my only post ive done so far you can see how we are in the same boat. What were you using before you got to your problem, which custom ROM?
Click to expand...
Click to collapse
I'm currently using [DOK2] TEKXodus HYBRID N4 URv7
mdiaz33685 said:
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...
Click to expand...
Click to collapse
I check and made sure that the reactivation lock was disabled, but it still didn't work. I guess I will keep an eye open to see if this issue can get resolved sometime in the near future
mdiaz33685 said:
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...
Click to expand...
Click to collapse
What are the odin settings for doing this install? I can't get it to recognize the file
Nevermind, quick google showed i should extract the file which im not used to doing for roms and use "AP"
waywardfrantz said:
What are the odin settings for doing this install? I can't get it to recognize the file
Nevermind, quick google showed i should extract the file which im not used to doing for roms and use "AP"
Click to expand...
Click to collapse
U have to unziip the firmware and in Odin u need to goto AP and point to the firmware... sometimes i have to remove the extention .md5 after u unzip the firmware depending on which Odin u use...
make sure u have the samsung drivers installed..
mdiaz33685 said:
U have to unziip the firmware and in Odin u need to goto AP and point to the firmware... sometimes i have to remove the extention .md5 after u unzip the firmware depending on which Odin u use...
make sure u have the samsung drivers installed..
Click to expand...
Click to collapse
I can't Odin to stock unless I change the name of the firmware file to .tar. it skips the md5 check I believe.
---------- Post added at 06:17 PM ---------- Previous post was at 06:14 PM ----------
Also go to supersu and do a full unroot before. I'm thinking maybe the supersu backup script could cause issues too