Figured it would be good to make this common knowledge. If some of you have been following my testing on the knox safe root you'll know this already.
WARNING
It appears that the new mj4 update contains a new bootloader. This seems to prevent downgrades to earlier firmwares.
There have been reports that..
Trying to downgrade from mj4 on even a stock unrooted system will flip knox.
The downgrade may make your phone temporarily unusable.
It appears the only way to recover from a botched downgrade at this time is to use twrp to flash a new system. This will flip knox even if it hasn't been.
There is no official mj4 file at this time. So no way to flash a full mj4 in odin to fix your mistakes.
This is especially troubling for anyone with root and knox 0x0.
If your knox is already 0x1 it's probably not going to be a big deal.
We really need an official mj4 full tar from samsung. Especially if downgrading a stock system flips knox with no warning.
Sent from my SM-N900P using Tapatalk
The procedure I've been recommending to recover from this is to install TWRP with odin and flash a mj4 rom in twrp. Freeza's stock rooted mj4 should fix you up if you get stuck.
This will flip knox 0x1.if it's not already.
Sent from my SM-N900P using Tapatalk
mjcollum said:
The procedure I've been recommending to recover from this is to install TWRP with odin and flash a mj4 rom in twrp. Freeza's stock rooted mj4 should fix you up if you get stuck.
This will flip knox 0x1.if it's not already.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Good information. +2
All info is verified and correct!
Sent from my SM-N900P using XDA Premium 4 mobile app
Sounds to me like Samsung has some explaining to do as to why they did not release this information with the update notes. Seems really shady to me. They can take their KNOX and shove it.
We really could use a full mj4 tar from samsung.
Sent from my SM-N900P using Tapatalk
mjcollum said:
We really could use a full mj4 tar from samsung.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
This is true, I totally bricked my phone and its stuck in boot loop because I tried to flash the new software and restore a nandroid. Must be because of the bootloader because now I cant even odin back to stock the phone is toast. So be careful with this new software until we get a full one from samsung.
suavethekid said:
This is true, I totally bricked my phone and its stuck in boot loop because I tried to flash the new software and restore a nandroid. Must be because of the bootloader because now I cant even odin back to stock the phone is toast. So be careful with this new software until we get a full one from samsung.
Click to expand...
Click to collapse
Odin twrp.
Flash Freeza's stock rooted.
Sent from my SM-N900P using Tapatalk
suavethekid said:
This is true, I totally bricked my phone and its stuck in boot loop because I tried to flash the new software and restore a nandroid. Must be because of the bootloader because now I cant even odin back to stock the phone is toast. So be careful with this new software until we get a full one from samsung.
Click to expand...
Click to collapse
Why can't you Odin back to stock?
Sent from my SM-N900P using Xparent Purple Tapatalk 2
cherylbaker said:
Why can't you Odin back to stock?
Sent from my SM-N900P using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
If your on mj4 mess something up. and you try and flash a mi5 or mi3 backup it fails. And since there is no full mj4 you have to flash a system with twrp.
Sent from my SM-N900P using Tapatalk
mjcollum said:
If your on mj4 mess something up. and you try and flash a mi5 or mi3 backup it fails. And since there is no full mj4 you have to flash a system with twrp.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Do you have a link to a system I can flash in twrp? The only ones I can find are odin tars
suavethekid said:
Do you have a link to a system I can flash in twrp? The only ones I can find are odin tars
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2472664
Sent from my SM-N900P using Tapatalk
mjcollum said:
http://forum.xda-developers.com/showthread.php?t=2472664
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Unfortunately that doesn't work for me either, I get an unable to mount /usb storage error and it says it completes but it resets and just continues in a boot loop.
thanks anyway I think i'm giving up and just getting sprint to replace it luckily they were not smart enough to notice the knox counter was tripped.
suavethekid said:
Unfortunately that doesn't work for me either, I get an unable to mount /usb storage error and it says it completes but it resets and just continues in a boot loop.
thanks anyway I think i'm giving up and just getting sprint to replace it luckily they were not smart enough to notice the knox counter was tripped.
Click to expand...
Click to collapse
Ignore the usb error. It's checking for a usb ota device like a memory stick.
Check your download. Should be a md5 to check it against. Maybe a bad download.
Sent from my SM-N900P using Tapatalk
Is it just MJ4 bootloader that prevents downgrade? Did MI5 allow bootloader downgrade?
mmf01 said:
Is it just MJ4 bootloader that prevents downgrade? Did MI5 allow bootloader downgrade?
Click to expand...
Click to collapse
Yes I downgraded from mi5 to mi3 numerous times.
Sent from my SM-N900P using Xparent Purple Tapatalk 2
suavethekid said:
Unfortunately that doesn't work for me either, I get an unable to mount /usb storage error and it says it completes but it resets and just continues in a boot loop.
thanks anyway I think i'm giving up and just getting sprint to replace it luckily they were not smart enough to notice the knox counter was tripped.
Click to expand...
Click to collapse
Also look here
http://forum.xda-developers.com/showthread.php?t=2495174
Sent from my SM-N900P using Tapatalk
So if I want to return my phone to complete stock, there is no way correct? Because I need to take my note 3 to sprint but I am currently on Stock rooted MJ4.
powerstroke said:
So if I want to return my phone to complete stock, there is no way correct? Because I need to take my note 3 to sprint but I am currently on Stock rooted MJ4.
Click to expand...
Click to collapse
Provided you haven't tripped knox. Use supersu to remove root. Reboot. Factory reset.
Sent from my SM-N900P using Tapatalk
mjcollum said:
Provided you haven't tripped knox. Use supersu to remove root. Reboot. Factory reset.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Awesome, thanks man
Related
Hello,
I have a Verizon Galaxy S4. Today I rooted it. It all went fine, but I wanted to install a custom recovery. I followed a tutorial online, which lead me to downloading the Goo manager, and installing TWRP via that. I rebooted, and it went straight into download mode. It would not leave download mode, it continuously loops back to that. I connected it up to Odin, and downloaded the stock firmware to flash. The progress bar came up, loaded for a few minutes. Then, I got a big FAIL message. (Using 3.04). Now, its still in DL mode, but it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Tried flashing the stock firmware again, but keeps failing. Tried different USB ports, but keeps failing. Any suggestions?
Try flashing another recovery via odin
Sent from my GT-I9300 using xda premium
Jamiew1977 said:
Try flashing another recovery via odin
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
On it.
It happened to me with my s3, installed twrp with goo and I had no recovery. Flashed a different recovery with Odin and all was sweet, Hope you fix it.
Sent from my GT-I9300 using xda premium
Jamiew1977 said:
It happened to me with my s3, installed twrp with goo and I had no recovery. Flashed a different recovery with Odin and all was sweet, Hope you fix it.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Can't find a tar file flashable via Odin. All I can find is the Loki method, which I cannot do because I'm stuck in DL mode. Waiting on a download of a different stock firmware.
Dont think there is any recoveries flashable via odin. Were you on me7 by chance?
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
Dont think there is any recoveries flashable via odin. Were you on me7 by chance?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Nope.
Turn your phone all the way off and then use the button combo for odin, decline and it should boot. DoubleCheck your firmware version because what youre describing is what happens when you flash a recovery on me7, which you cant.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
Turn your phone all the way off and then use the button combo for odin, decline and it should boot. DoubleCheck your firmware version because what youre describing is what happens when you flash a recovery on me7, which you cant.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Didn't work. Went right back into DL mode after I declined.
When you were flashing the firmware via odin did it error when it was going to flash aboot?
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
When you were flashing the firmware via odin did it error when it was going to flash aboot?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Yes. It says FAIL! (Auth) right after aboot.mbn
Do you have a link to the root method you used?
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
Do you have a link to the root method you used?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Yep here it is: http://forum.xda-developers.com/showthread.php?t=2380325
PS: Thank you so much for sticking with me so far
Not a problem. Yep youre on the me7 firmware like I thought. Im guessing your trying to flash the mdk firmware thru odin? Me7 wont let you flash anything prior is why youre getting the errors. Youll have to download the me7 odin file (in dev section) and flash again. Once you get your phone booted again you cant flash a custom recovery or else itll do the same again. Theres a few people working on unlocking/bypassing the bootloader so hopefully it wont be much longer until me7 has custom recovery.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
Not a problem. Yep youre on the me7 firmware like I thought. Im guessing your trying to flash the mdk firmware thru odin? Me7 wont let you flash anything prior is why youre getting the errors. Youll have to download the me7 odin file (in dev section) and flash again. Once you get your phone booted again you cant flash a custom recovery or else itll do the same again. Theres a few people working on unlocking/bypassing the bootloader so hopefully it wont be much longer until me7 has custom recovery.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You are a savior my man. Thank you.
Not a problem
Sent from my SCH-I545 using Tapatalk 2
So I have tried every trick under the sun to get my baseband up to MJ4 so I can fully enjoy StrongSteves Odexed Blue. I have been a huge fan of Odexed Blue since the Epic Days.
I am still getting noises in calls and poor wireless signal compared to my friends fully stock MJ4. I have tripped knox and when i try to go to fully stock MI5 for an OTA update, I am told my phone has been modified and cannot receive updates. I can get the build and the firmware to tick up to MJ4 but nothing I try can get the baseband updated. I am on stock kernel.
Can I offer a bounty of around $50 to anyone that can help me?
I will be online for several hours today.
EDIT: Solution is on my reply (#21) on page 3 of this thread.
Do u mean mj4?
Sent from my SM-N900P using XDA Premium 4 mobile app
aFoodStampBaby said:
Do u mean mj4?
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I did. I just fixed it, thanks!
drewbuntu said:
Yes I did. I just fixed it, thanks!
Click to expand...
Click to collapse
You have also tried Odin the full stock MJ4? If not just do that, if you have then maybe try this, Odin MI5, reboot to STOCK recovery and factory reset, then Odin MI5 again then reboot to STOCK recovery factory reset again, boot device then set everything up and wait for update. After update, if it takes, flash CF autoroot in Odin, flash TWRP in Odin then go Blue.
ifly4vamerica said:
You have also tried Odin the full stock MJ4? If not just do that, if you have then maybe try this, Odin MI5, reboot to STOCK recovery and factory reset, then Odin MI5 again then reboot to STOCK recovery factory reset again, boot device then set everything up and wait for update. After update, if it takes, flash CF autoroot in Odin, flash TWRP in Odin then go Blue.
Click to expand...
Click to collapse
I have tried flashing with Odin: N900PVPUBMJ4_N900PSPTBMJ4_N900PVPUBMJ4_HOME.tar.md5
Even tried factory reset etc on it several times and flashing again.
I am downloading N900PVPUBMI5_N900PSPTBMI5_SPR.zip and will try your double odin method, even though I am sure I tried this 2 weeks ago.
ifly4vamerica said:
... Odin MI5, reboot to STOCK recovery and factory reset, then Odin MI5 again then reboot to STOCK recovery factory reset again, boot device then set everything up and wait for update. After update, if it takes, flash CF autoroot in Odin, flash TWRP in Odin then go Blue.
Click to expand...
Click to collapse
I tried this. Everything running at MI5 now, but OTA refuses to run still. I attached some screeshots.
As you can see it says "custom" on the "status page" and whatever is triggering that is preventing OTA.
Have you tried using Wanam X posed to fake the system status?
Sent from my SM-N900P using Xparent Skyblue Tapatalk 2
drewbuntu said:
So I have tried every trick under the sun to get my baseband up to MJ4 so I can fully enjoy StrongSteves Odexed Blue. I have been a huge fan of Odexed Blue since the Epic Days.
I am still getting noises in calls and poor wireless signal compared to my friends fully stock MJ4. I have tripped knox and when i try to go to fully stock MI5 for an OTA update, I am told my phone has been modified and cannot receive updates. I can get the build and the firmware to tick up to MJ4 but nothing I try can get the baseband updated. I am on stock kernel.
Can I offer a bounty of around $50 to anyone that can help me?
I will be online for several hours today.
Click to expand...
Click to collapse
So you have the full MJ4 stock rom or just the modem?
Sent from my SM-N900P using XDA Premium 4 mobile app
drewbuntu said:
I tried this. Everything running at MI5 now, but OTA refuses to run still. I attached some screeshots.
As you can see it says "custom" on the "status page" and whatever is triggering that is preventing OTA.
Click to expand...
Click to collapse
Weird even if it was custom it should still flash in Odin when you do the stock MJ4 tar. Not sure what you have going on there. Maybe try a different Odin and stock MJ4 Tar. Good luck.
I've had success with odin3v1.85
Getting Nowhere Fast
mhutton said:
Have you tried using Wanam X posed to fake the system status?
Sent from my SM-N900P using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
@mhutton When I try Wanam eXposed, it allows me to check the box and then requests a reboot, but reboots in custom still.
What I tried to do was set Custom flag off and during reboot, boot into Odin and reflash the stock MI5 and MJ4 and neither work out
luisrod03 said:
So you have the full MJ4 stock rom or just the modem?
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
@luisrod03 I have tried stock full Odin MJ4 and SM-N900P-HLTESPR-MJ4-DeOdex-v2.zip, which is FULL stock rooted deodexed for freeza. Still nothing.
What else can I try to get my baseband up to MJ4? I am almost certain that knox and the custom flag is preventing this, but I am not experienced enough to know how to look at the logs or whatever to prove that.
drewbuntu said:
@mhutton When I try Wanam eXposed, it allows me to check the box and then requests a reboot, but reboots in custom still.
What I tried to do was set Custom flag off and during reboot, boot into Odin and reflash the stock MI5 and MJ4 and neither work out
@luisrod03 I have tried stock full Odin MJ4 and SM-N900P-HLTESPR-MJ4-DeOdex-v2.zip, which is FULL stock rooted deodexed for freeza. Still nothing.
What else can I try to get my baseband up to MJ4? I am almost certain that knox and the custom flag is preventing this, but I am not experienced enough to know how to look at the logs or whatever to prove that.
Click to expand...
Click to collapse
Maybe try going back to MI3, I think it was MI3 anyway, whatever was before MI5. It is important to do the factory reset and wipe data betweeb ODIN flashes though with the STOCK recovery. Last thing to check is that your MJ4 tar actually has the modems in it.
Firmware and Modem only
Full tar
MI3
Guide and links
Also have you tried removing the sd card? Seems I remember some people having trouble with the sd card in the phone steps would be:
remove SD
wipe data, internal sd, davlik and cache in twrp
odin stock (try MJ4 first to avoid the manual update if that doesnt take go back to MI3)
reboot into STOCK recovery and factory reset a couple times
re odin
before phone boots force it to recovery factory reset again
boot normally and see if you have mj4 (or see if you can get the update)
Once you get the update on the internal storage I think it remains flagged as bad until you wipe it so thus the need to pull the sd card and wipe internal memory. (this is just a theory though)
Let us know if this works
Also remember (just in case) some of the files will download as zips so you will need to extract the to flash the. tar.md5 or .tar file in Odin.
ifly4vamerica said:
Maybe try going back to MI3, I think it was MI3 anyway, whatever was before MI5. It is important to do the factory reset and wipe data betweeb ODIN flashes though with the STOCK recovery. Last thing to check is that your MJ4 tar actually has the modems in it.
Firmware and Modem only
Full tar
MI3
Guide and links
Also have you tried removing the sd card? Seems I remember some people having trouble with the sd card in the phone steps would be:
remove SD
wipe data, internal sd, davlik and cache in twrp
odin stock (try MJ4 first to avoid the manual update if that doesnt take go back to MI3)
reboot into STOCK recovery and factory reset a couple times
re odin
before phone boots force it to recovery factory reset again
boot normally and see if you have mj4 (or see if you can get the update)
Once you get the update on the internal storage I think it remains flagged as bad until you wipe it so thus the need to pull the sd card and wipe internal memory. (this is just a theory though)
Let us know if this works
Also remember (just in case) some of the files will download as zips so you will need to extract the to flash the. tar.md5 or .tar file in Odin.
Click to expand...
Click to collapse
Has downgrading from MI5 to MI3 caused issues for anyone? I'm aware of some that had issues with downgrading from MJ4 to MI5.
Sent from my SM-N900P using Xparent BlueTapatalk 2
---------- Post added at 10:28 AM ---------- Previous post was at 10:27 AM ----------
drewbuntu said:
@mhutton When I try Wanam eXposed, it allows me to check the box and then requests a reboot, but reboots in custom still.
What I tried to do was set Custom flag off and during reboot, boot into Odin and reflash the stock MI5 and MJ4 and neither work out
@luisrod03 I have tried stock full Odin MJ4 and SM-N900P-HLTESPR-MJ4-DeOdex-v2.zip, which is FULL stock rooted deodexed for freeza. Still nothing.
What else can I try to get my baseband up to MJ4? I am almost certain that knox and the custom flag is preventing this, but I am not experienced enough to know how to look at the logs or whatever to prove that.
Click to expand...
Click to collapse
Could you post a screenshot of your about phone screen, or are you unable to boot?
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Has downgrading from MI5 to MI3 caused issues for anyone? I'm aware of some that had issues with downgrading from MJ4 to MI5.
Sent from my SM-N900P using Xparent BlueTapatalk 2
---------- Post added at 10:28 AM ---------- Previous post was at 10:27 AM ----------
Could you post a screenshot of your about phone screen, or are you unable to boot?
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I know you can't downgrade from MJ4 to MI5 I tried that a few times and had to restore a nandroid to be able to boot. It wouldn't flash anything even through odin. I did however downgrade a few times from MI5 to MI3 initially. I don't recall having any issues at all.
micmars said:
Has downgrading from MI5 to MI3 caused issues for anyone? I'm aware of some that had issues with downgrading from MJ4 to MI5.
Sent from my SM-N900P using Xparent BlueTapatalk 2
---------- Post added at 10:28 AM ---------- Previous post was at 10:27 AM ----------
Could you post a screenshot of your about phone screen, or are you unable to boot?
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
The mi5 to mi3 downgrade is no problem.
It's how I first got root before tripping knox. (I had a whole thread on it somewhere)
MJ4 to mi5 not possible.
I guess I can read through this thread a bit.
There shouldn't be a situation where flashing the full samsung mj4 file in Odin won't set you straight...
Is it possibly an Odin pc side driver issue.
In theory the Kies program should be able to wipe it to new also though I've never tried.
Sent from my SM-N900P using Tapatalk
mjcollum said:
The mi5 to mi3 downgrade is no problem.
It's how I first got root before tripping knox. (I had a whole thread on it somewhere)
MJ4 to mi5 not possible.
I guess I can read through this thread a bit.
There shouldn't be a situation where flashing the full samsung mj4 file in Odin won't set you straight...
Is it possibly an Odin pc side driver issue.
In theory the Kies program should be able to wipe it to new also though I've never tried.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Thanks for confirming that. I got my phone after taking the MJ4 update right at the Sprint store.
I'm surprised Skunk Ape's stock MJ4 build using Odin hasn't worked. Seems to be the go-to in these situations.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Thanks for confirming that. I got my phone after taking the MJ4 update right at the Sprint store.
I'm surprised Skunk Ape's stock MJ4 build using Odin hasn't worked. Seems to be the go-to in these situations.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Yea...
If the stock mj4 full samsung file through Odin doesn't do it ???
It should work every time. No matter what.
Though, I would bet any failures here would be a pc/Odin version/driver issue and not really a phone issue.
Of course I've been wrong before I guess.
Sent from my SM-N900P using Tapatalk
Good point on the MJ4 to MI5 downgrade but I think he is able to get back to MI5 just not able to get it to MJ4 which is strange... You would think if Odin worked to go back to MI5 it would work to go to MJ4.
Note 3 or Gear Sent
ifly4vamerica said:
Good point on the MJ4 to MI5 downgrade but I think he is able to get back to MI5 just not able to get it to MJ4 which is strange... You would think if Odin worked to go back to MI5 it would work to go to MJ4.
Note 3 or Gear Sent
Click to expand...
Click to collapse
Right I should clarify in the hopes it may help.
The issue with going back to mi5 from MJ4 is the bootloader and modems don't downgrade.
So at that point you'd have mj4 baseband stuff but mi5 system.
With mi5 a downgrade puts you at full mi3.
However you should still be able to flash the full samsung mj4 package regardless.
There is currently nothing newer out so no worry there.
Inability to flash a full zip from odin, provided it's a good md5 checked complete zip, is 99.99999999% likely to be an issue with odin , the pc, or drivers. (This is in my experience only so fwiw)
If the phone can get in download mode it shouldn't make any difference what information if any even is written to the necessary partitions. These will all be wiped and re installed anyway.
So...
If his baseband is mi5
There are two real options.
Get mi5 back to completely official. To take ota.
Flash a full mj4. (Usually odin, i don't believe the other packages are updating bootloaders, ect.)
In theory this is super simple.
You would just flash the full samsung mj4 in odin.
That should solve all the problems.
And would leave you with a completely stock phone. (With the exception of knox trip but that is a non issue.)
If for some reason you are not able to flash it with odin, you may give Kies a try. It should also be able to fully wipe and recover to the latest update.
Though in this situation I would probably spend my energy troubleshooting odin.
I'm going to stand behind my bet of it being a odin version or driver issue here.
Though if you are able to flash other things in odin it could also just be a bad file.
I have yet to have a phone that I could get into download mode that was not completely recoverable.
Though I have had issues with specific odin versions and drivers especially on windows 8.
Just my opinion. I'm not sure I even know what I'm talking about. And am probably safe to ignore.
Sent from my SM-N900P using Tapatalk
micmars said:
Has downgrading from MI5 to MI3 caused issues for anyone? I'm aware of some that had issues with downgrading from MJ4 to MI5.
Sent from my SM-N900P using Xparent BlueTapatalk 2
---------- Post added at 10:28 AM ---------- Previous post was at 10:27 AM ----------
Could you post a screenshot of your about phone screen, or are you unable to boot?
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I have been trying to get an MI3 image all day but the downloads fail or get interrupted.
I posted some screenshots in a previous post, and no matter what I try, I end up with version and baseband at MI5 and build at MJ5. I can flip flop build and sometimes version, but not baseband at all.
I have tried the wipe and flash trick 3 times in a row, I have tried Odin version 1.85 and 3.07 and 3.09, none of them complete the job. I have also tried going back to MI5 and then running the MJ5 ROM and then reboot into download and run just the baseband update then wipe, nothing.
Looks like I am about 8 hours + until i have a full MI3 rom.
Here I have with me the engineering bootloader for our Galaxy Note 3. It is version NC5 so as long as you're on a KitKat bootloader, you can flash this. I recommend being on software NC5 or NC5D already, but if you are on NAB[D] this will also work. Please note I will not handle support or take responsibility for anything you do outside of flashing this bootloader on recommended software versions.
[size=+1]WARNING[/size]:
This has the potential to BRICK your device, so use it at your own risk.
What is the purpose of this bootloader?
Well, I believe that having this bootloader will allow us to easily flash basebands in the future, as long as you don't flash any Odin TAR files, or take any OTAs, you will retain the bootloader. I do not know if you will be able to downgrade again in the future to this bootloader, but for now, you have it.
Who is this for?
Devs, enthusiasts, flashaholics, people that know what they're doing.
Who this is not for?
Average Joes, those who want to take very little risk with their phones, those who don't know what they're doing or what potential an engineering bootloader has outside of basebands, and those who don't like seeing a bunch of engineering text when booting up, into recovery, or into download mode.
Instructions:
Again, make sure you are already on NC5 or NC5D.
Flash with Odin.
Profit.
Download:
NC5 engineering bootloader
Installing as we speak, I just seen the post for NC5(D) and was wondering when/if this would be released. Thanks freeza, your the man!
Thank you sir!
Sent from my SM-N900P using Xparent BlueTapatalk 2
Flashing this will still not allow the flashing of the update correct? Still need to go back to stock and all that stuff?
MikeyLee said:
Flashing this will still not allow the flashing of the update correct? Still need to go back to stock and all that stuff?
Click to expand...
Click to collapse
Thanks, as always!
MikeyLee said:
Flashing this will still not allow the flashing of the update correct? Still need to go back to stock and all that stuff?
Click to expand...
Click to collapse
It will allow flashing of the baseband, and if you choose to stay on nc5 and not nc5d, then you won't need to flash the update because the stock rooted as well as the baseband are on the way.
freeza said:
It will allow flashing of the baseband, and if you choose to stay on nc5 and not nc5d, then you won't need to flash the update because the stock rooted as well as the baseband are on the way.
Click to expand...
Click to collapse
Stock rooted NC5 on the way? That's awesome! You're the man!
Looking good Freeza. Nice Job getting this out there. Very useful indeed.
freeza said:
Here I have with me the engineering bootloader for our Galaxy Note 3. It is version NC5 so as long as you're on a
.
.
.
NC5 engineering bootloader
Click to expand...
Click to collapse
Thanks freeza.
I want to thank you for all your work and time Freeza. Here is something in appreciation for your time, rom, leaks, kernel.... confirmation 6TX83637NM934200U. Thank you once again.
Sent from my SM-N900P using XDA Premium 4 mobile app
So this is ok to flash via odin if Im on the nab bootloader. I had flashed your nab tar in odin in the past. Im running sacs v3 nab rom. I'll need to re-root as well?
mta1981 said:
So this is ok to flash via odin if Im on the nab bootloader. I had flashed your nab tar in odin in the past. Im running sacs v3 nab rom. I'll need to re-root as well?
Click to expand...
Click to collapse
Bootloader can go right on top of your setup, interchange with the regular.
That stated, please read the OP and know that which you are getting into (ie, your phone, your property, your risk).
Take a look at the NAB bootloader thread, and its associated comments, for reference.
Sent from my SM-N900P using Xparent BlueTapatalk 2
@micmars, flashing went just fine, I put the tar in the bootloader slot of odin and all, but the baseband and software version after reboot still says nab. Is that because im still on a nab rom? I'm going through the trouble just cuz I'm a guy who likes to keep his devices up to date. And I like a little more than just stock, rom-wise.
mta1981 said:
@micmars, flashing went just fine, I put the tar in the bootloader slot of odin and all, but the baseband and software version after reboot still says nab. Is that because im still on a nab rom? I'm going through the trouble just cuz I'm a guy who likes to keep his devices up to date. And I like a little more than just stock, rom-wise.
Click to expand...
Click to collapse
You have everything right. The bootloader is what allows you to boot anything. If you like being up-to-date, then that bootloader plus the full build would do it.
But the bootloader alone is now on your device.
Sent from my SM-N900P using Xparent BlueTapatalk 2
freeza said:
It will allow flashing of the baseband, and if you choose to stay on nc5 and not nc5d, then you won't need to flash the update because the stock rooted as well as the baseband are on the way.
Click to expand...
Click to collapse
Odin or twrp?
Cheryl
cherylbaker said:
Odin or twrp?
Cheryl
Click to expand...
Click to collapse
Odin
Sent from my SM-N900P using Tapatalk 2
Maybe my Odin is just screwed up but I have no option other than the PDA option to put something in. Everything else is grayed out. I did flash this though but everything still shows NABD
***EDIT*** Fixed Odin but everything still shows NABD after flashing
MikeyLee said:
Maybe my Odin is just screwed up but I have no option other than the PDA option to put something in. Everything else is grayed out. I did flash this though but everything still shows NABD
Click to expand...
Click to collapse
Try this 3.07 version, file goes in boot, nothing should be grayed out, you'll be done in less that 10 seconds...
https://www.dropbox.com/s/z2n10tjzmxlhaz4/Odin3 v3.07.zip
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Try this 3.07 version, file goes in boot, nothing should be grayed out, you'll be done in less that 10 seconds...
https://www.dropbox.com/s/z2n10tjzmxlhaz4/Odin3 v3.07.zip
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I got it but still it seems like the Baseband should show NC5. Or am I thinking of when you flash a modem?
MikeyLee said:
I got it but still it seems like the Baseband should show NC5. Or am I thinking of when you flash a modem?
Click to expand...
Click to collapse
Your baseband won't change (that'd be modem), this is just what boots the phone up, shuts it down, or bricks it if you have the wrong one.
Sent from my SM-N900P using Xparent BlueTapatalk 2
So I have been working on a friend of mines Verizon Note 2 (SCH-I605) and have run into an issue... I had rooted it successfully to root66 VZW stock sys, then attempted to unlock the bootloader according to the [email protected] galaxynote2root(dot)com/galaxy-note-2-tutorials/how-to-unlock-bootloader-on-verizon-galaxy-note-2-sch-i605.... without reviewing the multiplicity of comments below the article which should have caught my attention and let me know that many people were unsuccessful with that method.
So now i appear to be screwed because it will boot into ODIN but thats it. I cant even get into stock recovery. Upon boot the Galaxy Note 2 splash stays on indefinitely, as it does when i follow the instructions on this site to restore it from a failed unlock, or unroot...... ODIN 3 + sch-I605-16gb.pit + Root66-VZW-stock_sys, when it reboots following flash the splash screen stays on. I have checked the NAND erase All as suggested on this site, and it makes no difference.
When vol up/home/power is pressed it says something to the effect that 'you are a dumb*ss and have screwed up your firmware dipsh*t'....
So what now? Id hate to have to replace my buddies Note 2.... and I had absolutely 0 difficulties unlocking and rooting my HTC One, so this sucks....
Use this guide to flash back to the appropriate version.
http://forum.xda-developers.com/showthread.php?t=2024207
It's a great guide. Saved me last week after I flashed the wrong file in Odin.
Sent from my SCH-I605 using Tapatalk
michigan66 said:
Use this guide to flash back to the appropriate version.
http://forum.xda-developers.com/showthread.php?t=2024207
It's a great guide. Saved me last week after I flashed the wrong file in Odin.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
yea i did that already to no avail.... used odin to flash the pit and root66... doesnt boot...
Moridin68 said:
yea i did that already to no avail.... used odin to flash the pit and root66... doesnt boot...
Click to expand...
Click to collapse
Have you tried using a different image? What version of stock was on it before you messed with it?
Edit: If the stock version wasn't MJ9 or above then don't flash those. There currently isn't and probably won't be a way to unlock the bootloader on MJ9 and above.
Sent from my SCH-I605 using XDA Premium 4 mobile app
BluGuy said:
Have you tried using a different image? What version of stock was on it before you messed with it?
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
well, thats a good question... it was already in a messed up state when i got ahold of it... i tried flashing root66 and it kept failing, i checked NAND ERASE ALL and flashed CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar
as per a suggestion i read on xda.. it too failed as well, but then when i flashed root66 again (also i think with NAND ERASE on) it booted up beautifully...
Moridin68 said:
well, thats a good question... it was already in a messed up state when i got ahold of it... i tried flashing root66 and it kept failing, i checked NAND ERASE ALL and flashed CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar
as per a suggestion i read on xda.. it too failed as well, but then when i flashed root66 again (also i think with NAND ERASE on) it booted up beautifully...
Click to expand...
Click to collapse
i have recently read on a site that offers a bootloader downgrade service that if it has a knox counter, then it was updated to a version with a 'permalocked' bootloader... and if this is referring to the counter on the ODIN screen that says KNOX WARRANTY VOID:0 then this one is such a device.....
Moridin68 said:
well, thats a good question... it was already in a messed up state when i got ahold of it... i tried flashing root66 and it kept failing, i checked NAND ERASE ALL and flashed CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar
as per a suggestion i read on xda.. it too failed as well, but then when i flashed root66 again (also i think with NAND ERASE on) it booted up beautifully...
Click to expand...
Click to collapse
When you enter download mode does it say anything about Knox?
Edit: I didn't see your last post. Since it had the updated firmware with Knox, you should be at least able to get the phone working again by flashing that version of the firmware in odin. If it was on Android 4.3 then you should be able to odin MJ9 and it will work again. If it was on 4.4.2 then using odin to flash the ND7 image should fix it.
Sent from my SCH-I605 using XDA Premium 4 mobile app
BluGuy said:
When you enter download mode does it say anything about Knox?
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
on the download screen there is a line that says KNOX WARRANTY VOID:0
BluGuy said:
When you enter download mode does it say anything about Knox?
Edit: I didn't see your last post. Since it had the updated firmware with Knox, you should be at least able to get the phone working again by flashing that version of the firmware in odin. If it was on Android 4.3 then you should be able to odin MJ9 and it will work again. If it was on 4.4.2 then using odin to flash the ND7 image should fix it.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
he hadnt had service on that phone for several months so i guess ill try the older one first. 4.4.2.
and do i flash the pit file with those as well?
this bs is so much more tedious than working with my HTC One.
Moridin68 said:
So I have been working on a friend of mines Verizon Note 2 (SCH-I605) and have run into an issue... I had rooted it successfully to root66 VZW stock sys, then attempted to unlock the bootloader according to the [email protected] galaxynote2root(dot)com/galaxy-note-2-tutorials/how-to-unlock-bootloader-on-verizon-galaxy-note-2-sch-i605.... without reviewing the multiplicity of comments below the article which should have caught my attention and let me know that many people were unsuccessful with that method.
So now i appear to be screwed because it will boot into ODIN but thats it. I cant even get into stock recovery. Upon boot the Galaxy Note 2 splash stays on indefinitely, as it does when i follow the instructions on this site to restore it from a failed unlock, or unroot...... ODIN 3 + sch-I605-16gb.pit + Root66-VZW-stock_sys, when it reboots following flash the splash screen stays on. I have checked the NAND erase All as suggested on this site, and it makes no difference.
When vol up/home/power is pressed it says something to the effect that 'you are a dumb*ss and have screwed up your firmware dipsh*t'....
So what now? Id hate to have to replace my buddies Note 2.... and I had absolutely 0 difficulties unlocking and rooting my HTC One, so this sucks....
Click to expand...
Click to collapse
Did ID:COM turn blue in Odin? . You might have a driver problem.
doctor-cool said:
Did ID:COM turn blue in Odin? . You might have a driver problem.
Click to expand...
Click to collapse
no driver problem... it recognizes the device.... it is blue
Moridin68 said:
he hadnt had service on that phone for several months so i guess ill try the older one first. 4.4.2.
and do i flash the pit file with those as well?
this bs is so much more tedious than working with my HTC One.
Click to expand...
Click to collapse
The older one would be 4.3 which is MJ9. And yes use the pit file with it.
And just in case, I know you probably don't need it, the instructions for flashing with odin are in the return to stock section of the first post in this thread: http://forum.xda-developers.com/showthread.php?t=2024207
Sent from my SCH-I605 using XDA Premium 4 mobile app
BluGuy said:
The older one would be 4.3 which is MJ9. And yes use the pit file with it.
And just in case, I know you probably don't need it, the instructions for flashing with odin are in the return to stock section of the first post in this thread: http://forum.xda-developers.com/showthread.php?t=2024207
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
right you are about 4.3 being older... i was looking through the stock roms in that very guide and saw 4.1.2 and thought that was the one you had mentioned... im downloading MJ9 now..... thanks... hope this works...
so let me ask you this, if i get it back to stock, and rooted again... even though i cant unlock the bootloader, can i get it network unlocked? this entire dilemma occurred because he wants to be able to throw a straight talk sim in this phone.
i had intended to try this www(dot)scottsroms(dot)com/showthread.php?2786-How-I-turned-my-Verizon-Note-2-into-a-World-capable-GSM-phone
once i fixed the disaster....
Moridin68 said:
right you are about 4.3 being older... i was looking through the stock roms in that very guide and saw 4.1.2 and thought that was the one you had mentioned... im downloading MJ9 now..... thanks... hope this works...
so let me ask you this, if i get it back to stock, and rooted again... even though i cant unlock the bootloader, can i get it network unlocked? this entire dilemma occurred because he wants to be able to throw a straight talk sim in this phone.
i had intended to try this www(dot)scottsroms(dot)com/showthread.php?2786-How-I-turned-my-Verizon-Note-2-into-a-World-capable-GSM-phone
once i fixed the disaster....
Click to expand...
Click to collapse
Once you get the phone working you can use Saferoot to root it, that is as long as it's working on MJ9. If the phone had been updated to ND7 which is Android 4.4.2 then there currently isn't a way to root it.
Remember even if you get root you won't be able to use a custom recovery to flash stuff.
Also the sch-i605 is already Sim unlocked from Verizon. You just have to be able to edit the apn settings.
Sent from my SCH-I605 using XDA Premium 4 mobile app
BluGuy said:
Once you get the phone working you can use Saferoot to root it, that is as long as it's working on MJ9. If the phone had been updated to ND7 which is Android 4.4.2 then there currently isn't a way to root it.
Remember even if you get root you won't be able to use a custom recovery to flash stuff.
Also the sch-i605 is already Sim unlocked from Verizon. You just have to be able to edit the apn settings.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ok one last thing before i try this MJ9.... if it had been updated then how was i able to flash it to root66 prior to attempting to unlock the bootloader?
i really appreciate your time bro..thanks btw..
Moridin68 said:
ok one last thing before i try this MJ9.... if it had been updated then how was i able to flash it to root66 prior to attempting to unlock the bootloader?
i really appreciate your time bro..thanks btw..
Click to expand...
Click to collapse
Sorry it took so long to get back to you. I don't know a lot about root66 so I can't help you much there, but I do know that while in download mode if it says something about Knox warranty then the bootloader had been updated to a version with Knox which started with mj9 for the i605.
Sent from my SCH-I605 using XDA Premium 4 mobile app
BluGuy said:
Sorry it took so long to get back to you. I don't know a lot about root66 so I can't help you much there, but I do know that while in download mode if it says something about Knox warranty then the bootloader had been updated to a version with Knox which started with mj9 for the i605.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
cool then.. thanks...
BluGuy said:
Sorry it took so long to get back to you. I don't know a lot about root66 so I can't help you much there, but I do know that while in download mode if it says something about Knox warranty then the bootloader had been updated to a version with Knox which started with mj9 for the i605.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
booting up on MJ9... nicely done.
so ill check out saferoot as you said, and then edit the APN
Moridin68 said:
booting up on MJ9... nicely done.
so ill check out saferoot as you said, and then edit the APN
Click to expand...
Click to collapse
Glad it worked.
Sent from my SCH-I605 using XDA Premium 4 mobile app
BluGuy said:
Sorry it took so long to get back to you. I don't know a lot about root66 so I can't help you much there, but I do know that while in download mode if it says something about Knox warranty then the bootloader had been updated to a version with Knox which started with mj9 for the i605.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
so now i have stock recovery menu and download menu and it boots and then hangs at the white verizon screen... i have already done a factory reset, and it still hangs.
ok I have been out of the loop for awhile.. But I odined to stock nh7 with stock recovery. when I go to upgrade it says my device has been modified??? Is it refusing to let me cause I tripped knox???? if so is there anyway to get lollipop?? if it is not cause of knox than what could be wrong???
cherylbaker said:
ok I have been out of the loop for awhile.. But I odined to stock nh7 with stock recovery. when I go to upgrade it says my device has been modified??? Is it refusing to let me cause I tripped knox???? if so is there anyway to get lollipop?? if it is not cause of knox than what could be wrong???
Click to expand...
Click to collapse
After you Odin NH7 you need to factory reset in stock recovery to get your status back to official
Sent from my SM-N910P using Tapatalk 2
Did that. . I got it to work by redoing the odin process. All working now.. course i don't like any of the cosmetics
Sent from my SM-N900P using Xparent Purple Tapatalk 2