I rooted my phone a few weeks ago while I'm on mi1 software using de la Vega method and a little after I decided to use goomanager to flash a custom bootloader but instead got stuck in Odin with the message going something like (Odin mode cant boot normal) got out of it by pressing volume down + power then restart but now I can't even update my phone to 4.3 because everytime I do It goes back to that Odin downloading error screen please help I'd be gracious for any response .thank you
I'm getting a similar issue. Mine says:
Could not do normal boot.
ODIN MODE
Product name: SCH-I545
Current binary: samsung official
system status: Official
CSB-config-lsb: 0x30
Write protection: enable
then i just see the android guy with Downloading Do not turn off target.
doesn;t seem to be doing anything else, and i can;t push any buttons to get out.
illtrytohelpyou said:
I rooted my phone a few weeks ago while I'm on mi1 software using de la Vega method and a little after I decided to use goomanager to flash a custom bootloader but instead got stuck in Odin with the message going something like (Odin mode cant boot normal) got out of it by pressing volume down + power then restart but now I can't even update my phone to 4.3 because everytime I do It goes back to that Odin downloading error screen please help I'd be gracious for any response .thank you
Click to expand...
Click to collapse
Flash back to MI1. It does not support custom bootloaders.
You can use SafeStrap and that is about it.
joshrys said:
I'm getting a similar issue. Mine says:
Could not do normal boot.
ODIN MODE
Product name: SCH-I545
Current binary: samsung official
system status: Official
CSB-config-lsb: 0x30
Write protection: enable
then i just see the android guy with Downloading Do not turn off target.
doesn;t seem to be doing anything else, and i can;t push any buttons to get out.
Click to expand...
Click to collapse
Yea I just can't figure it out I hope this thread helps you too
tech_head said:
Flash back to MI1. It does not support custom bootloaders.
You can use SafeStrap and that is about it.
Click to expand...
Click to collapse
How would I go about flashing back to mi1 stock boot loader?
You'll need to look at one of the other threads on flashing with Odin. You will need the MI1 Odin file.
Sent from my SCH-I545 using Tapatalk
tech_head said:
You'll need to look at one of the other threads on flashing with Odin. You will need the MI1 Odin file.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Will it restore my phone ? Like loose all my stuff? And will I loose root sorry for all the questions but I really appreciate your help
illtrytohelpyou said:
Will it restore my phone ? Like loose all my stuff? And will I loose root sorry for all the questions but I really appreciate your help
Click to expand...
Click to collapse
Yes, it will wipe the phone and you will lose root.
I think there is a "no wipe version also" check the forums.
Check out -> http://forum.xda-developers.com/showthread.php?t=2301259
also - http://forum.xda-developers.com/showthread.php?t=2503676&page=3
After Installing 4.3 Update On Rooted MK2.... Update Stopped In Download Mode Now
illtrytohelpyou said:
Yea I just can't figure it out I hope this thread helps you too
Click to expand...
Click to collapse
My S4 Verizon Does And Says The Same As His But My System Status Says Custom.
Related
Purchased a Verizon S4 on swappa. The phone was rooted - in the description it said "It has not been updated to 4.3 and is currently rooted on 4.2.2 ME7 baseband" I am upgrading from a Galaxy Nexus I rooted as I run stuff like XPrivacy etc..
I get the phone, install titanium backup and do a full backup. The OTA update notification started popping up as well. Go to reboot the phone and reboot into recovery. (Familiar with doing that n the Galaxy Nexus, so why not? I am a foolish man)
The phone reboots into what I now learn is odin mode and says:
Could not do normal boot.
Odin Mode
Product name: SCH-I545
Current Binary: Samsung Official
System Status: Custom
CSB-CONFIG-LSB: 0x30
What has happened and how do I resolve it? Assuming it is fixable is it better to stay where I am OS version wise or accept the OTA update?
Thanks in advance for the help.
Thadster
Thadster said:
Purchased a Verizon S4 on swappa. The phone was rooted - in the description it said "It has not been updated to 4.3 and is currently rooted on 4.2.2 ME7 baseband" I am upgrading from a Galaxy Nexus I rooted as I run stuff like XPrivacy etc..
I get the phone, install titanium backup and do a full backup. The OTA update notification started popping up as well. Go to reboot the phone and reboot into recovery. (Familiar with doing that n the Galaxy Nexus, so why not? I am a foolish man)
The phone reboots into what I now learn is odin mode and says:
Could not do normal boot.
Odin Mode
Product name: SCH-I545
Current Binary: Samsung Official
System Status: Custom
CSB-CONFIG-LSB: 0x30
What has happened and how do I resolve it? Assuming it is fixable is it better to stay where I am OS version wise or accept the OTA update?
Thanks in advance for the help.
Thadster
Click to expand...
Click to collapse
Star here: http://forum.xda-developers.com/showthread.php?t=2606501
The guy who sold you it is an idiot. He attempted to use goomanager to flash a custom recovery. You can stay the way you are and not have a recovery, but if you want it back you should flash a no wipe ME7 Odin image. I did the same thing and is easily fixed
aidankiller4 said:
The guy who sold you it is an idiot. He attempted to use goomanager to flash a custom recovery. You can stay the way you are and not have a recovery, but if you want it back you should flash a no wipe ME7 Odin image. I did the same thing and is easily fixed
Click to expand...
Click to collapse
First off thank you for the rapid reply. While waiting, I have been research odin - kinda get what I have to do. First can you point me to the odin image you suggest? Would that file then go into the pda slot and get pushed to the phone? Will I have to reroot?
Thadster said:
First off thank you for the rapid reply. While waiting, I have been research odin - kinda get what I have to do. First can you point me to the odin image you suggest? Would that file then go into the pda slot and get pushed to the phone? Will I have to reroot?
Click to expand...
Click to collapse
Here's the odin file for your phone
http://forum.xda-developers.com/showthread.php?t=2357235
That file goes into the pda slot
After that go into the Dev section and search for how to root your phone.
Do some research and see if staying on an older build like me7 is worth it for you. Either way, you'll have safestrap and root. Everything past me7 has the Knox bootloader and security. Just read up a bit that's all.
Until you decide flash that in Odin... Root it.... and grab titanium backup and freeze SDM and FWupdater and you won't get any annoying OTA notifications.
Edit
The no wipe images are here
http://forum.xda-developers.com/showthread.php?t=2301259
Maybe you can get away with just doing a no wipe. Try it first.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Thank you.
The no-wipe did not work, but the other did. (Phew).
Phone is now operational and re-rooted. What are my recovery options with regards to backing up this current phone image? Having difficulty getting clockwork recovery to work. (Hesitant probably) Is sage strap a better option?
Thadster said:
Thank you.
The no-wipe did not work, but the other did. (Phew).
Phone is now operational and re-rooted. What are my recovery options with regards to backing up this current phone image? Having difficulty getting clockwork recovery to work. (Hesitant probably) Is sage strap a better option?
Click to expand...
Click to collapse
Like I said before. Start here: http://forum.xda-developers.com/showthread.php?t=2606501
Thadster said:
Thank you.
The no-wipe did not work, but the other did. (Phew).
Phone is now operational and re-rooted. What are my recovery options with regards to backing up this current phone image? Having difficulty getting clockwork recovery to work. (Hesitant probably) Is sage strap a better option?
Click to expand...
Click to collapse
You can't use clockwork, or any other custom recovery, on your phone. Safestrap is your only choice.
Brand new Samsung S4, had successful root (checked via Root Checker). I had previously installed Clockworkmod but after some difficulty with flashing Cyanogenmod 10.2 I downloaded GooManager and installed it's preferred recovery, then re-downloaded the CM 10.2 and directed GooManager to install the .zip, and it popped up the "Downloading... Do not turn off target!!" The script in the top left says as follows
"Could not do normal boot.
ODIN MODE
Product Name: SSCH-1545
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x0
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
eMMC BURST MODE enabled"
It has been on this downloading screen with no changes for 2 hours. After researching other threads, I tried to reboot into recovery, only for this exact screen to pop up immediately, and again with no change for prolonged periods of time.
Any help would be greatly appreciated! I am fairly new to this as well, so the more user-friendly the better.
What software version are you running?
Sent from my SCH-I545 using Tapatalk
joshuabg said:
What software version are you running?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I can't remember off the top of my head... 4.2.3 pops in to mind, I'll research and post as soon as I find.
You can't ****ing use goomanager, god dammit read alittle before you **** up your phone. Just boot holding power, home, and volume down, and when prompted press no
I managed to get back to stock with root; I used Goo Manager -because- I did some reading, but obviously I read the wrong things. If someone could assist with the best structure to use (which recovery, best method for flashing, etc.) I would greatly appreciate it.
ziggums said:
I managed to get back to stock with root; I used Goo Manager -because- I did some reading, but obviously I read the wrong things. If someone could assist with the best structure to use (which recovery, best method for flashing, etc.) I would greatly appreciate it.
Click to expand...
Click to collapse
Search in android development. Factory Firmware is there. You'll need to Odin at this point. Whatever came on your phone stock. The firmware version matters here. Can't Odin a previous version. Only what's on it or a newer version. After that a reroot and find the safestrap thread in android development. Read up. This will be your recovery. No aosp. No custom kernels just touch wiz ROMs.
Sent from my SCH-I545 using XDA Premium 4 mobile app
ziggums said:
Brand new Samsung S4, had successful root (checked via Root Checker). I had previously installed Clockworkmod but after some difficulty with flashing Cyanogenmod 10.2 I downloaded GooManager and installed it's preferred recovery, then re-downloaded the CM 10.2 and directed GooManager to install the .zip, and it popped up the "Downloading... Do not turn off target!!" The script in the top left says as follows
"Could not do normal boot.
ODIN MODE
Product Name: SSCH-1545
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x0
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
eMMC BURST MODE enabled"
It has been on this downloading screen with no changes for 2 hours. After researching other threads, I tried to reboot into recovery, only for this exact screen to pop up immediately, and again with no change for prolonged periods of time.
Any help would be greatly appreciated! I am fairly new to this as well, so the more user-friendly the better.
Click to expand...
Click to collapse
you have soft bricked your phone by not understanding what you can and can't do with it. Better learn about odin process
Mightycaptain said:
Search in android development. Factory Firmware is there. You'll need to Odin at this point. Whatever came on your phone stock. The firmware version matters here. Can't Odin a previous version. Only what's on it or a newer version. After that a reroot and find the safestrap thread in android development. Read up. This will be your recovery. No aosp. No custom kernels just touch wiz ROMs.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I found several guides about flashing to original, but none of them match my build (I am MK2). The phone is behaving exactly as before except when I try to boot into recovery mode it sends me back to the "Downloading.... Do not turn off target!!" screen, and I have to go through the process to get back to "normal" behavior. Could I simply just flash a different recovery, or do I need to try to find MK2 to go back to original first?
I appreciate all the help so far!
ziggums said:
I found several guides about flashing to original, but none of them match my build (I am MK2). The phone is behaving exactly as before except when I try to boot into recovery mode it sends me back to the "Downloading.... Do not turn off target!!" screen, and I have to go through the process to get back to "normal" behavior. Could I simply just flash a different recovery, or do I need to try to find MK2 to go back to original first?
I appreciate all the help so far!
Click to expand...
Click to collapse
You CAN'T flash a recovery on your build. That's the whole problem. You need to Odin back to your stock build. There is an MK2 file in the development section.
Sent from my NCC 1701 using Tapatalk 4
riker147 said:
You CAN'T flash a recovery on your build. That's the whole problem. You need to Odin back to your stock build. There is an MK2 file in the development section.
Sent from my NCC 1701 using Tapatalk 4
Click to expand...
Click to collapse
Could you link me to it? I can't find anything that deals with soft-brick reversing for MK2.
ziggums said:
Could you link me to it? I can't find anything that deals with soft-brick reversing for MK2.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2578209
douger1957 said:
http://forum.xda-developers.com/showthread.php?t=2578209
Click to expand...
Click to collapse
Thanks! I assume I would need to do the full-wipe process rather than the no-wipe process?
ziggums said:
Thanks! I assume I would need to do the full-wipe process rather than the no-wipe process?
Click to expand...
Click to collapse
I think in the long run a full wipe is always the best route.
douger1957 said:
I think in the long run a full wipe is always the best route.
Click to expand...
Click to collapse
The link was exactly what I needed! The video link they had was especially helpful, I returned to stock. I do have a question moving on from here though... Can I use Odin to try to flash CM10.2 (the one that was unsuccessful previously)? And what recovery do you recommend? The other posters mentioned something about Safe... I'm really just trying to get a smooth, stable ROM so I don't have to deal with the bloatware and can customize a bit more for what I need. Sorry if I'm annoying, but I appreciate all the help!
ziggums said:
The link was exactly what I needed! The video link they had was especially helpful, I returned to stock. I do have a question moving on from here though... Can I use Odin to try to flash CM10.2 (the one that was unsuccessful previously)? And what recovery do you recommend? The other posters mentioned something about Safe... I'm really just trying to get a smooth, stable ROM so I don't have to deal with the bloatware and can customize a bit more for what I need. Sorry if I'm annoying, but I appreciate all the help!
Click to expand...
Click to collapse
Being on MK2 your ONLY option is Safestrap. No Cm, no AOSP.....Just TW. You have a lot of research to do. Start here: http://forum.xda-developers.com/showthread.php?t=2606501
ziggums said:
The link was exactly what I needed! The video link they had was especially helpful, I returned to stock. I do have a question moving on from here though... Can I use Odin to try to flash CM10.2 (the one that was unsuccessful previously)? And what recovery do you recommend? The other posters mentioned something about Safe... I'm really just trying to get a smooth, stable ROM so I don't have to deal with the bloatware and can customize a bit more for what I need. Sorry if I'm annoying, but I appreciate all the help!
Click to expand...
Click to collapse
Please do some research...you can't install cm or asop base roms or custom recovery like cwm or twrp...your only option is safestrap.
Sent from my SCH-I545 using XDA Premium 4 mobile app
so i was planning on turning in my note 2 tomorrow to get a new phone...so i wanted to put the stock image back on it...went back to 4.1.2, no problem. then it updates to 4.3 and it's stuck in bootloop...just shows the "note 2" logo...i can't get into the volume up + power + home to erase the cache...it won't even get to that screen...all i can do is get into the odin menu...i have reloaded 4.3 about 6 times, trying different combinations of partitioning and not partitioning, neither works.
if i choose the "nand erase all" box...am i just asking for trouble? i've been messing with this for about 5 hours now...any help is greatly appreciated, i tried googling for at least 2 hours but i can't find anyone that has this specific issue...
also, i've tried using kies, it won't recognize the phone...i can't do the one where you put in the model number, says my phone can't initialize the update...grr...
RONxBURGUNDY said:
so i was planning on turning in my note 2 tomorrow to get a new phone...so i wanted to put the stock image back on it...went back to 4.1.2, no problem. then it updates to 4.3 and it's stuck in bootloop...just shows the "note 2" logo...i can't get into the volume up + power + home to erase the cache...it won't even get to that screen...all i can do is get into the odin menu...i have reloaded 4.3 about 6 times, trying different combinations of partitioning and not partitioning, neither works.
if i choose the "nand erase all" box...am i just asking for trouble? i've been messing with this for about 5 hours now...any help is greatly appreciated, i tried googling for at least 2 hours but i can't find anyone that has this specific issue...
Click to expand...
Click to collapse
RONxBURGUNDY said:
also, i've tried using kies, it won't recognize the phone...i can't do the one where you put in the model number, says my phone can't initialize the update...grr...
Click to expand...
Click to collapse
if i remember correctly, i stumble something like this a while back with my cousin phone.
what i do back then is to odin cwm recovery, and after that for some reason i could get to recovery
Bonkurei said:
if i remember correctly, i stumble something like this a while back with my cousin phone.
what i do back then is to odin cwm recovery, and after that for some reason i could get to recovery
Click to expand...
Click to collapse
just tried to put cwm on it...odin won't let it work...says "nand write start"...then says "fail!"...could it be because i "think" it's on 4.3 now? there's a message that says "knox warranty void: 0"...i think that's a new thing on 4.3...?
i'm about to just smash it and squaretrade warranty it lol
RONxBURGUNDY said:
just tried to put cwm on it...odin won't let it work...says "nand write start"...then says "fail!"...could it be because i "think" it's on 4.3 now? there's a message that says "knox warranty void: 0"...i think that's a new thing on 4.3...?
i'm about to just smash it and squaretrade warranty it lol
Click to expand...
Click to collapse
lol kinda sad to see it smash, sorry it dont work for you.
also if my memory serve me right, my cousin phone are s3 with 4.3 on it, so in my case it work on 4.3
RONxBURGUNDY said:
just tried to put cwm on it...odin won't let it work...says "nand write start"...then says "fail!"...could it be because i "think" it's on 4.3 now? there's a message that says "knox warranty void: 0"...i think that's a new thing on 4.3...?
i'm about to just smash it and squaretrade warranty it lol
Click to expand...
Click to collapse
That would be correct.. You are on a 4.3 bootloader
You need to flash via odin..MJ9 Kies tar.. Also use the pit when flashing
Sent from my SCH-I605 using xda app-developers app
lacoursiere18 said:
That would be correct.. You are on a 4.3 bootloader
You need to flash via odin..MJ9 Kies tar.. Also use the pit when flashing
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
used the pit...flashed I605VRUEMJ9_I605VZWEMJ9_I605VRUEMJ9_HOME.tar.md5 that i downloaded from here...still stuck on note II splash logo, can't get into recovery, can still get in odin. computer will recognize it's hooked up, but kies won't connect either. think i'm giving up on it
RONxBURGUNDY said:
used the pit...flashed I605VRUEMJ9_I605VZWEMJ9_I605VRUEMJ9_HOME.tar.md5 that i downloaded from here...still stuck on note II splash logo, can't get into recovery, can still get in odin. computer will recognize it's hooked up, but kies won't connect either. think i'm giving up on it
Click to expand...
Click to collapse
Recovery meaning stock recovery? Bc your on 4.3 bootloader so you won't be able to have a custom recovery unless on safe strap.. see if you have stock recovery and do a factory reset once Odin goes though fine
Sent from my SCH-I605 using xda app-developers app
lacoursiere18 said:
Recovery meaning stock recovery? Bc your on 4.3 bootloader so you won't be able to have a custom recovery unless on safe strap.. see if you have stock recovery and do a factory reset once Odin goes though fine
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
yup i think what he meant is stock recovery, and after taking ota 4.3 his phone goes bootloop and he cant perform factory reset because he cant get in to stock recovery. cmiiw.
Bonkurei said:
yup i think what he meant is stock recovery, and after taking ota 4.3 his phone goes bootloop and he cant perform factory reset because he cant get in to stock recovery. cmiiw.
Click to expand...
Click to collapse
yup, exactly right. pretty close to giving up here but that's ok...i can just break it. i've already traded in another phone...got myself an m8...
thanks anyways.
After my grand daughter got my SCH-i650 into TWRP recovery mode and then proceeded to really (&#$^@# it up, needless to say it was totally screwed. My fault though. I ended up flashing with odin back to stock and used the MJ9 4.3 version.I didn't know that the boot loader was locked up tight on this one so I am stuck with it. I rooted, then put the new safe strap on it and got stuck in a splash screen. I could hear messages coming through but my screen was locked. Long story short, what finally worked was what you all said to do in this thread and then stock recovery and factory reset. At least I have my phone back. I really miss Alliance and Trent's rom but glad to at least have my phone working. Thank you all for all the help and suggestions.
Sorry if this is answered on another thread; I couldn't find any answer that helped me, so I am opening this thread.
My Galaxy S3 I9300 is stuck with the error: "Firmware Upgrade encountered an issue. Please select recovery mode in Kies & try again."
But when I try to upgrade using Kies I get the error message "This device's version cannot be updated." I get as far as entering my model number and S/N.
I cannot enter recovery mode on my S3, only download mode, so I am unable to perform a hard reset.
My phone is not compatible with Kies3 so I am using Kies.
Any suggestions?
make sure your phone is not rooted,otherwise kies becomes unvailable.
Flash stock ROM via Odin Download at http://www.sammobile.com/firmwares/
How can I tell?
alecore said:
make sure your phone is not rooted,otherwise kies becomes unvailable.
Click to expand...
Click to collapse
How can I tell if the phone is rooted? I got the phone second hand last week, and I don't know if it had previously been rooted.
In download mode, I see the following:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
I am guessing this means it hasn't been rooted?
rmurray1975 said:
How can I tell if the phone is rooted? I got the phone second hand last week, and I don't know if it had previously been rooted.
In download mode, I see the following:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
I am guessing this means it hasn't been rooted?
Click to expand...
Click to collapse
Download root checker from google play
On what?
nikctsh said:
Download root checker from google play
Click to expand...
Click to collapse
This may seem a stupid question but on what am I supposed to download Root Checker? I cannot access my S3 (the reason for this thread).
rmurray1975 said:
This may seem a stupid question but on what am I supposed to download Root Checker? I cannot access my S3 (the reason for this thread).
Click to expand...
Click to collapse
So why don't you provide us more details on why your phone stuck with that error message so that we can help you. You say you just got the phone second hand last week, so apparently the phone still works when you first get your hand on it. You must have done something to it, causing it to stuck with that error?
This is how I got it
nikctsh said:
So why don't you provide us more details on why your phone stuck with that error message so that we can help you. You say you just got the phone second hand last week, so apparently the phone still works when you first get your hand on it. You must have done something to it, causing it to stuck with that error?
Click to expand...
Click to collapse
This is the state I got the phone in. I had taken a quick check on the internet to see how to resolve the issue, and thought it would be worth the cost of the phone (40 Euros) to try to fix it myself. Guess I was wrong!
rmurray1975 said:
This is the state I got the phone in. I had taken a quick check on the internet to see how to resolve the issue, and thought it would be worth the cost of the phone (40 Euros) to try to fix it myself. Guess I was wrong!
Click to expand...
Click to collapse
I'm not sure whether this can help, but try mate.
1) Enter download mode and install stock rom using ODIN (preferred)
If this doesn't do the trick, try another EXPERIMENTAL alternative way,
2) Enter download mode, root your device using CF root using ODIN, flash a custom recovery using ODIN, boot into your custom recovery, flash a custom rom (risky)
I never encountered this before so I have no idea whether this can actually help or not, so do this at your own risk.
You are a star!
nikctsh said:
I'm not sure whether this can help, but try mate.
1) Enter download mode and install stock rom using ODIN (preferred)
If this doesn't do the trick, try another EXPERIMENTAL alternative way,
2) Enter download mode, root your device using CF root using ODIN, flash a custom recovery using ODIN, boot into your custom recovery, flash a custom rom (risky)
I never encountered this before so I have no idea whether this can actually help or not, so do this at your own risk.
Click to expand...
Click to collapse
You are my new hero!!!
I flashed the stock rom in Odin 3.09 and it worked a treat! I have a working telephone!
Thank you very much!!!
rmurray1975 said:
You are my new hero!!!
I flashed the stock rom in Odin 3.09 and it worked a treat! I have a working telephone!
Thank you very much!!!
Click to expand...
Click to collapse
You are welcome mate, glad that I helped you
Ok, I've had this phone rooted since a few months back using the towelroot method, the phone has been giving me issues this past week so I wanted to do a factory reset and unroot the phone.
The TR method worked in rooting the phone but I was never able to access the recovery mode, something like seandroid enforcing error.
Well, I noticed in one forum that I would be able to use the updated SuperSU app on the chainfire website to unroot. I followed this process but still couldn't boot to recovery. I then dowloaded the mj4 tar and tried to push it through odin 3.07 and it says fail.
Now my phone is bricked, kies 3 doesn't recognize it for an emergency firmware update, and I'm in the process of downloading nc5 to try that one.
Please if anyone can help me out in figuring how to restore my phone I would greatly appreciate it, I start classes on Monday only have this weekend to fix it. Any advice would be awesome, thanks!
If you can boot into download mode ( press the power button, home button, volume up button, at the same time) great !! first download Odin to PC desktop here is the link http://www.downloadodin.info/download-odin-1-85 then you need an OS .tar ( kk 4.4.2 NC5 ) here is the link http://forum.xda-developers.com/showthread.php?t=2712205 download to PC desktop.
Extract the zip NC5 file to PC desktop this changes it to a .tar file. Now boot device into download mode, then extract and open odin on desktop, connect device to PC via USB cable a box in upper left corner will light up COM: doesn't matter what color it is just shows a connection. Click on the PDA box another box will open click on NC5 .tar file it should show in box to the right of PDA box. Now your ready don't touch anything else, click start and it will say pass when done this will take at least 15 minutes.
I have unrooted my Note 3 a couple of times, the best way is a new OS through Odin.
Thank you so much jimzweb1!! That worked like a charm, I was freaking out! Not a noob to rooting but every now and then I run into some hiccup! Thanks to xda for having helpful people like you to remedy the situation ☺.... You da man jimzweb1!
everlast716 said:
Thank you so much jimzweb1!! That worked like a charm, I was freaking out! Not a noob to rooting but every now and then I run into some hiccup! Thanks to xda for having helpful people like you to remedy the situation ☺.... You da man jimzweb1!
Click to expand...
Click to collapse
No problem, now that you are back with the living. Lol !!! Remember, once you upgrade to KK 4.4.2 NC5, you can downgrade to NAB but NO further !!! The bootloader in KK 4.4.2 NC5 will not let you go back to Mj4, you will soft brick the device.
Is your warranty still KNOX 0x0 ?
jimzweb1 said:
No problem, now that you are back with the living. Lol !!! Remember, once you upgrade to KK 4.4.2 NC5, you can downgrade to NAB but NO further !!! The bootloader in KK 4.4.2 NC5 will not let you go back to Mj4, you will soft brick the device.
Is your warranty still KNOX 0x0 ?
Click to expand...
Click to collapse
Sorry Jimz, I just saw this reply! Currently, knox says 0x1....I don't know how to get that back to 0x0 unless triangle away now works?
Unrooting/Restoring your phone
everlast716 said:
Sorry Jimz, I just saw this reply! Currently, knox says 0x1....I don't know how to get that back to 0x0 unless triangle away now works?
Click to expand...
Click to collapse
If you join the sam mobile website You can look your phone up by model number. Once you do download the .tar and open it through Odin. Make sure your phone is in download mode. Use the PDA box and locate the .tar and load it through Odin. It will restore Knox and reset your phone to factory.
Hope this helps.
Android Extremist said:
If you join the sam mobile website You can look your phone up by model number. Once you do download the .tar and open it through Odin. Make sure your phone is in download mode. Use the PDA box and locate the .tar and load it through Odin. It will restore Knox and reset your phone to factory.
Hope this helps.
Click to expand...
Click to collapse
I thought there was no way to untrip knox? Has something changed?
Sent from my SM-G900P using Xparent Purple Tapatalk 2
cherylbaker said:
I thought there was no way to untrip knox? Has something changed?
Click to expand...
Click to collapse
AMAIK, nothing will bring Knox warranty back to 0x0 once it was 0x1
tetakpatalked from Nexus 7 flo
tetakpatak said:
AMAIK, nothing will bring Knox warranty back to 0x0 once it was 0x1
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Thats what I thought.. android extremist just said you coukd was why I was asking
Sent from my SM-G900P using Xparent Purple Tapatalk 2
Well actually to answer the question fully, yes they can reset Knox 0x1 warranty e-fuse. However, only for Exynos processor based note 3's. Sprint note 3's use a Qualcomm processor. There getting closer, you can read up on this in Developer Discussions/A few things about Knox.