Database Users

[GUIDE] Manually up- or downgrade firmware

Responsibility
I am not responsible for your bricked devices, dead ad-card or anything else you did because of this guide. It is up to you, to read this guide carefully and to inform you also on other places, so that you know what you are doing and what are the risks.
If you have fear to brick your Note then better wait and take your time. The official OTA update will also came in some days.
If something goes wrong then don't hesitate and post it here. I - and surly others - will try to help you.
Upgrade
I didn't want to wait for the next OTA update to MK1 (which include user management and other improvements). So, I start to update manually and because I didn't find clearly answers here in the forum, I make afterwards this guide.
This guide should work for all different kind of 10.1 Notes Edition 2014 (WiFi only, GSM, LTE) so long you download the corresponding, correct firmware for your Note version. I did it for a P600 (WiFi only) and it works without any issues.
Results
Updated to newest firmware (MK1)
Normally you don't lose your data and configuration just as by a OTA update. But make however a backup of everything for the case something goes wrong and you have to made a factory reset!
Still everything is working what I use. I didn't and can't test everything and maybe something is not longer working because of the region switch.
The warranty bit is still 0 (after the update):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Preparation
First we need the firmware, we want to flash to our Note. I got mine from here: Sammobile but you can get it also from here: Samsungis.
You can find a list of all firmwares for your Note model by searching. In the list I choose the newest one for the MK1 update also it is for a different region. Until now I didn't see any issues because of this region switch.
Issue is maybe that you can't download here the firmware because both sides use hotfile for file hosting. Here you can use the pCloud service. I did it and from there I could download the file.
Next we need some tools: Odin (I use version 3.09) and maybe a Samsung usb driver (I got mine because of an earlier installed Kies). There are many places where you can find Odin but I got mine from here: Odin 3.09 (xda).
If you don't have a Windows computer in your reach then there are also tools for MacOS and Linux but I didn't test any of them!
A Samsung USB driver which by example is installed when you install the Kies application from Samsung.
Upgrading
There are many good tutorials for using the Odin application. Therefore I will only describe in a nutshell what I did. When you search for a more detailed guide then you can use one of them: Samsungsi: Using Odin, rootSU (xda): Odin flash guide. They also exists in other languages, you are free to use a search tool.
Start Odin as administrator
Connect the Note via USB too the computer and check that Odin got a connection: One of the ID:COM fields should contain the port number and also the background should be blue (or yellow if you use an older Odin version).
Press the AP (PDA in older versions) button to add the downloaded firmware (tar.md5). In the message box you should see (depending from your Odin version):
Code:
...
<OSM> Please wait...
<OSM> (*) is valid
<OSM> Checking MD5 finishes Successfully...
<OSM> Leave CS..
(*) the filename of your firmware download.
Power-off the Note and wait for 1 minute (I didn't understand this step but found it in some guides)
Hold the power and volume down button pressed until you see the triangle screen.
Press the volume up button to go to the download mode (Odin mode):
New press the Start button in Odin and wait until flash is down. Be very carefully here!
And no, I don't have any photos to show what happens now. Look into other more detailed Odin guides.
At the end the Note reboot by his own and the update is done :laugh:
When something goes wrong then look in the tutorials, how to solve it.
Downgrade
A downgrade works in the same way with Odin. So, you can download an older firmware and flash it in the same way with Odin.
You can here also use Kies to recover an old firmware and Kies download the correct version for you. I try this with the current Kies version 3 for Windows and MacOS and with both it works.
Special thanks to
xda for his great community
Sammobile for the firmware
beanstown106, bigbiff, nrage23 and many others here in the forum for their knowledge and help
lap777 for correction on this guide
rootSU for his Odin guide

F.A.Q
Will the warranty bit change to 1?
As you can see above mine is still 0. I also expect this because with this guide we flash a by Samsung signed firmware. But I read also in other guides for other devices that in some cases the bit is increased to 1. So, don't be surprised when this happens.
Can I get system status 'Official' back?
Yes, with both methods from above, you got current binary: 'Samsung Official' and system status: 'Official' back after you flash a custom recovery or ROM. Only the warranty bit will in this case stay 1.

I would have thought the AP button (PDA?), not CP (Phone/modem?). Sorry, I'm new at this

lap777 said:
I would have thought the AP button (PDA?), not CP (Phone/modem?). Sorry, I'm new at this
Click to expand...
Click to collapse
We are all new to this and you are right. Next time I write my guide in parallel.
PS. The guide is corrected.

I’m wandering if i can flash different regional version and donot trigger knox?

yobyzal said:
I’m wandering if i can flash different regional version and donot trigger knox?
Click to expand...
Click to collapse
I, like others, did it (the MK1 is only for some regions available) and didn't trigger knox. Like I said, this firmwares (from the sources above) are the original ones which are still signed by Samsung. If you flash something with a custom recovery or already rooted than this will not be the case and you will trigger knox.
PS. If you have also an P600: I flash "P600UEUBMK1_P600XARBMK1_HOME.tar.md5" which is for region "Cellular south" which is surly not "Luxembourg".
PPS. And until now I didn't have any other problem because of the different region.
PPPS. In the meantime I rooted my Note and trigger therefore knox. But also this seems no problem for me. I can still flash the stock firmware and got then OTAs (set bit is still set to 1). And the warranty will be still given for 6 month in Europa. Only extra guaranties by Samsung will be maybe a problem. And here I didn't care.

I can confirm that the method provided in this guide has updated my Galaxy Note 10.1 (2014 German Edition) to firmware version MK1 without triggering Knox. Warranty bit still 0.

sbeanie said:
I can confirm that the method provided in this guide has updated my Galaxy Note 10.1 (2014 Edition), German Edition, to firmware version MK1 without triggering Knox. Warranty bit still 0.
Click to expand...
Click to collapse
Congratulations. And German Edition is the original edition for your device, right?

yobyzal said:
Congratulations. And German Edition is the original edition for your device, right?
Click to expand...
Click to collapse
Yes my device was bought in Germany.

my p600was tripped by just flashing the stock firmware again using Odin.

moom999 said:
my p600was tripped by just flashing the stock firmware again using Odin.
Click to expand...
Click to collapse
What did you mean with "again"? (a) you flash it again and then it was tripped or (b) it was already tripped and after flashing was not changed?
b) will be normal because this flag will stay on 1 for ever

I flashed yesterday without tripping Knox.

Maybe I should try this too. Tired of waiting for OTA. Samsung support gave me a generic "we are looking into this matter" reply so my guess is they are totally clueless about eta of MK1 in Europe and probably don't even understand what I'm talking about...

Elim said:
What did you mean with "again"? (a) you flash it again and then it was tripped or (b) it was already tripped and after flashing was not changed?
b) will be normal because this flag will stay on 1 for ever
Click to expand...
Click to collapse
I flashed the stock firmware again then it was tripped

Now I flashed different regional version and the result shows that WARRANTY BIT still be zero.:victory:

home button problem
Is anyone else having problems with their home button not working? I press the home button and it doesnt take me to my "home screen" but it will wake up and return back to the screens from the app drawer. If anyone else has the same problem let me know if you have came to a solution. Thanks

osbrandon said:
Is anyone else having problems with their home button not working? I press the home button and it doesnt take me to my "home screen" but it will wake up and return back to the screens from the app drawer. If anyone else has the same problem let me know if you have came to a solution. Thanks
Click to expand...
Click to collapse
Way to bump a 5 month old thread with a completely unrelated problem. Good work.

osbrandon said:
Is anyone else having problems with their home button not working? confused
Click to expand...
Click to collapse
Yes, you seem to be a little bit confused because this topic has nothing do with your question and otherwise this question is already asked many times.

Stock firmware includes the stock recovery?
Which is the correct Country/Carrier for the US?

Elim said:
What did you mean with "again"? (a) you flash it again and then it was tripped or (b) it was already tripped and after flashing was not changed?
b) will be normal because this flag will stay on 1 for ever
Click to expand...
Click to collapse
Will this work or have you heard if it working for the new Verizon LTE model...mine came with 442 and would like to downgrade so I can root & custom recovery? But I dont see US firmware listed by Samsung lloks like they remvoed it.

[GUIDE] Baseband/Radio "stuck" and not updating? Here's how to fix it!

Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Remember: This guide is specifically for those of you who have tried other methods and are still stuck on an old baseband. If you're just looking how to flash your radio, there are easier and less involved methods that don't require any wiping - I strongly advise you to try those first.
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.

Nice....it helped me :good:
Thanks :highfive:

neoKushan said:
Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.
Click to expand...
Click to collapse
No need this，too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband

nforce4 said:
No need this，too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband
Click to expand...
Click to collapse
Thanks, but unfortunately that didn't work for me.

neoKushan said:
Thanks, but unfortunately that didn't work for me.
Click to expand...
Click to collapse
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.

IzArsha said:
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.
Click to expand...
Click to collapse
Believe me when I say that I tried that, I tried just about everything before it would finally stick. Removing battery, leaving it off for 10s+ (I did this numerous times as TriangleAway demands it due to the risk if bricking your phone and one time left it off/unplugged for a good 20mins to no avail). There was some kind of write protection in place, Mobile ODIN (yeah tried that as well) mentioned it when trying to flash the Radio - hence why TriangleAway is needed.
Before it got "Stuck", I had manually updated my Modem a few times without issue. I've had the Note 3 since launch and voided Knox within about 2 days of getting it - believe me, I've been there and done that

Nothing worked for me also until I tried this method...
Sent from my SM-N9005 using XDA Premium 4 mobile app

Here's what I don't like, and what I "Do" Like...
Like....
1) A post in the proper forum that seems to help a few people fix their issue when other methods didn't seem to work.
Dislike...
1) Somebody coming in touting their own method (which may or may not work for a particular user). This, believe it or not, only adds to confusion when a person looks for an answer. Now there are different methods in the same thread topic.
2) 2 pages of back and forth arguing as a result of the above ^^^
So, I'll delete all posts concerning this debate on procedures.
Folks, don't go poaching other users threads please. If they provide a solution that helps a few users, then that is GREAT!!! Not all normal solutions work for all users. Stick around long and you will discover this on your own one day.
Cleaned thread, please don't make me come back and do it again.
MD

Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.

neoKushan said:
Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.
Click to expand...
Click to collapse
Much better. I didn't mean to start an argument... But it happened somehow.
Good detailed guide however. See you around XDA.

I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks

MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?

neoKushan said:
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?
Click to expand...
Click to collapse
I've done almost every method, but not yours. BTW I don't have any other triangle icon except the yellow triangle at the start of Download mode.

MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Unpack the tar file, and flash just the modem.bin into phone (not pda) in Odin.

not working on SM-N900w8
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?

jsecruzvalencia said:
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=53632129&postcount=1
In the first box.

Best method to root on 4.2.2?

My phone was rooted and I did a factory reset to send it to have the screen repaired. I lost root and I get the message "com.android.phone not responding" all the time if I restart the phone but it works fine. Someone told me to use Odin to wipe the phone and get rid of that message. After I do that, what tool should I use to root on 4.2.2?

Need MORE info. What was the Original firmware/ what firmware do you have right now? You said 4.2.2 but which one? MDB? MDL? or MF3?
MDB and MDL you can do a lot note with and use motochopper + Loki bootloader bypass. MF3 patched the exploit and can only use safestrap recovery.
Read some of the threads once you find which firmware you have and/or on right now. If your stock, then beware it will AUTO UPDATE you without your consent. So find out what you have and need to do quickly.

RockRatt said:
Need MORE info. What was the Original firmware/ what firmware do you have right now? You said 4.2.2 but which one? MDB? MDL? or MF3?
MDB and MDL you can do a lot note with and use motochopper + Loki bootloader bypass. MF3 patched the exploit and can only use safestrap recovery.
Read some of the threads once you find which firmware you have and/or on right now. If your stock, then beware it will AUTO UPDATE you without your consent. So find out what you have and need to do quickly.
Click to expand...
Click to collapse
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks like it's MDL?. So I guess motochopper then. Mine cannot auto update fortunately. It fails every time. I've had it like that for a while but now I really want to root it again. I think it's because of that error I get on start-up that the update fails.

SRCP said:
Thanks.
Looks like it's MDL?. So I guess motochopper then. Mine cannot auto update fortunately. It fails every time. I've had it like that for a while but now I really want to root it again. I think it's because of that error I get on start-up that the update fails.
Click to expand...
Click to collapse
I had a similar situation, and the AT&T updates would fail at ~28%, even though I never approved the updates (my guess is that after I've said no more than 3 time, they did it anyways?). At that point I was stuck, and to make things worse, the WiFi was working only in my house, but no data over the ATT network, just voice. Even reflashing with ODIN didn't resolved the problem.
Had to bite the bullet and get the phone replaced by the warranty. I hope this doesn't happen to anyone else,

SRCP said:
Thanks.
Looks like it's MDL?. So I guess motochopper then. Mine cannot auto update fortunately. It fails every time. I've had it like that for a while but now I really want to root it again. I think it's because of that error I get on start-up that the update fails.
Click to expand...
Click to collapse
Since it is MDL firmware just use Motochopper + Loki and you will have a custom recovery (TWRP or CWM YOUR CHOICE). Then flash ANY custom ROM on your phone. You can have the best of BOTH worlds. You can flash a updated firmware ROM like ShoStock for the Touchwiz based Roms or a AOSP based ROMs. NO need to update firmware from ATT. In fact you lose what you can do with your phone if you do.
If you REALLY want to update to ATT newest firmware you can download the STOCK MDL firmware from samfirmware. Flash it which will make your phone PURE STOCK firmware and recovery. Then you will be able to update from ATT. The reason it fails is because you are rooted and probably custom recovery already?

Thanks. Well, I had it rooted but it seems like I lost root when I did something, I don't remember but I think it's when I factory reset it to send it to be repaired. It still says custom when I turn restart it but I am not rooted. I'm not very knowledgeable at this, I just follow guides step by step. I used an old method to root, it was an automated tool, can't remember the name. Anyway, in my current custom, non-rooted state, sgould I do something first before using motochopper?

SRCP said:
Thanks. Well, I had it rooted but it seems like I lost root when I did something, I don't remember but I think it's when I factory reset it to send it to be repaired. It still says custom when I turn restart it but I am not rooted. I'm not very knowledgeable at this, I just follow guides step by step. I used an old method to root, it was an automated tool, can't remember the name. Anyway, in my current custom, non-rooted state, sgould I do something first before using motochopper?
Click to expand...
Click to collapse
If you got it repaired does it have the same firmware version on it? Got to menu, settings, more, about device and look for the last three characters of your baseband. What are they?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
If you got it repaired does it have the same firmware version on it? Got to menu, settings, more, about device and look for the last three characters of your baseband. What are they?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, that pic is recent. I got it repaired months ago.

New Firmware QA1 released 1/26/2017...Security update

January 1 Security update. Everything else seems to have stayed the same.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Another update! Cool.

These security updates are coming very frequently. I would be careful updating if you value an unlocked bootloader. I wouldn't bet that Samsung wouldn't pull a fast one and lock it down even at this stage of the N4's life span. So be careful just incase.

Could anyone installed this update, confirms that the bootloader still unlocked, plz?
Sent from my SM-N910P using Tapatalk

tx_dbs_tx said:
These security updates are coming very frequently. I would be careful updating if you value an unlocked bootloader. I wouldn't bet that Samsung wouldn't pull a fast one and lock it down even at this stage of the N4's life span. So be careful just incase.
Click to expand...
Click to collapse
I agree. I never update until i have an Odin file!

aaron74 said:
I agree. I never update until i have an Odin file!
Click to expand...
Click to collapse
When you get the full tar file which files you remove from the tar before flashing to make sure that your bootloader still the old unlocked one?

anees02 said:
When you get the full tar file which files you remove from the tar before flashing to make sure that your bootloader still the old unlocked one?
Click to expand...
Click to collapse
I dont remove anything. But just use the name to verify the bootloader is same version. I cant verify this but I read somewhere that as long as the version number doesnt change, then its backwards flashable. Heres an example of what I mean.
Heres current firmware on sammobile N910PVPS4DPK1
and following so on like these N910PVPS4DPJ1, N910PVPU4DPH4, etc.
After the PVP is the bootloader version # as "S4" and "U4". Now what I read is as long as that # is same, that determines what firmware you can use.
So if you go back to firmware that we cant go back to like N910PVPU3BOF5. You can see its a 3. This is why we can only go back to N910PVPU4COG5
So in other words, as long as that stays a "4" , we should be able to downgrade to any firmware that is a "4".
As I already stated, I dont know this first hand, but have read it somewhere here!!
Hope this was helpful!!

aaron74 said:
I dont remove anything. But just use the name to verify the bootloader is same version. I cant verify this but I read somewhere that as long as the version number doesnt change, then its backwards flashable. Heres an example of what I mean.
Heres current firmware on sammobile N910PVPS4DPK1
and following so on like these N910PVPS4DPJ1, N910PVPU4DPH4, etc.
After the PVP is the bootloader version # as "S4" and "U4". Now what I read is as long as that # is same, that determines what firmware you can use.
So if you go back to firmware that we cant go back to like N910PVPU3BOF5. You can see its a 3. This is why we can only go back to N910PVPU4COG5
So in other words, as long as that stays a "4" , we should be able to downgrade to any firmware that is a "4".
As I already stated, I dont know this first hand, but have read it somewhere here!!
Hope this was helpful!!
Click to expand...
Click to collapse
Thank you very much.
I knew something new today because of you... Thanks again.
When I see to the latest OTA QA1 there are two things T4 and S4 what does that mean?
Maybe different CSC versions?

anees02 said:
Thank you very much.
I knew something new today because of you... Thanks again.
When I see to the latest OTA QA1 there are two things T4 and S4 what does that mean?
Maybe different CSC versions?
Click to expand...
Click to collapse
On all firmwares. The middle listing is the csc version, and its always got a different numbering than the others.
There's 3 version numbers here. 1st is the PDA (which is the actual rom firmware) 2nd is CSC (which is region) 3rd is the PHONE (which is the modem)
So this one is still #4 so it should be alright to still downgrade.
Now the last 3 digits just rep the date. Q=2017 A=January 1= 1st revision.
https://forum.xda-developers.com/showthread.php?t=1356325

wow. learning new things. thank guys.
just a little too late, after taking the update myself.
Has anyone been able to twrp/root? or odin backwards is the only way right now?

linhnd2000 said:
wow. learning new things. thank guys.
just a little too late, after taking the update myself.
Has anyone been able to twrp/root? or odin backwards is the only way right now?
Click to expand...
Click to collapse
You can Odin back as far as OG5 which is Android Lollipop 5.1
You can Odin TWRP on any of those updates. But Odin the desired update first if that's your goal.
What gets overlooked with TWRP flash is that you should boot directly into recovery after flashing. If you boot system first, immediately after TWRP flash, stock recovery gets restored.
That pattern and timing is tricky so it's recommended to uncheck auto reboot in Odin options when flashing TWRP. Once you get the success, 0 failed in Odin status, pull the USB cable and battery and wait at least 30 seconds (some suggest waiting at least a minute while discharging power circuit by holding power button down *Don't go Beastmode on that power button*). Reinstall battery and pattern boot into recovery (Vol+, Power and Home simultaneously until phone vibrates).
If you're rooting stock with stock kernel, you need systemless superuser. Flash SuperSU zip by Chainfire in recovery.
If flashing a custom ROM, you only need TWRP. No pre-root required for that.
Sent from my SM-N920P using Tapatalk

samep said:
You can Odin back as far as OG5 which is Android Lollipop 5.1
You can Odin TWRP on any of those updates. But Odin the desired update first if that's your goal.
What gets overlooked with TWRP flash is that you should boot directly into recovery after flashing. If you boot system first, immediately after TWRP flash, stock recovery gets restored.
That pattern and timing is tricky so it's recommended to uncheck auto reboot in Odin options when flashing TWRP. Once you get the success, 0 failed in Odin status, pull the USB cable and battery and wait at least 30 seconds (some suggest waiting at least a minute while discharging power circuit by holding power button down *Don't go Beastmode on that power button*). Reinstall battery and pattern boot into recovery (Vol+, Power and Home simultaneously until phone vibrates).
If you're rooting stock with stock kernel, you need systemless superuser. Flash SuperSU zip by Chainfire in recovery.
If flashing a custom ROM, you only need TWRP. No pre-root required for that.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
works perfectly. thanks. I went back to PK1 so I can use the debloated rom.

Bought a Samsung Tab A SM-T387V, apparently has doordash on it, how can I wipe it and use it as a normal tablet?

EDIT 2022-06-30: FOUND A RELIABLE SOLUTION FOR MY NEW T307U TABLET! May work for other models! https://forum.xda-developers.com/t/...e-it-as-a-normal-tablet.4316969/post-87091297
Original post from 2021-08-09 below:
Following this thread to no avail: https://forum.xda-developers.com/t/doordash-knox-customized-tablet-unable-to-remove.3890522/
Setup requires an internet connection, at which point it sets up MobiControl:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My friend's an IT so he set up Meraki for me which I can enroll in instead of MobiControl, but a minute later this pops up:
I still have access to the settings but cannot enable USB Debugging.
I flashed a combination file which got me to the "factory binary" where I can unlock OEM and enable USB Debugging, but I don't know where to go from here:
I flashed a stock ROM, but that doesn't get rid of doordash and MobiControl during setup.
Please help!

Which Android version did you flash? Did you finally get rid of MobiControl?

XDA.Samsung said:
Which Android version didn't you flash? Did you finally get rid of MobiControl?
Click to expand...
Click to collapse
I solved this. Basically, I accidentally bricked the tablet, which I assume is what caused Samsung Knox to fail and thus Mobi Control didn't try installing on a fresh flash of Android 8.1. Fuller story below:
After 3 days straight of trying to reset the tablet, including flashing the combo file, trying anything I can think of, re-flashing the stock rom and seeing if the problem is gone, I finally fixed it.
What ended up happening was, while re-flashing the stock rom on my 4th attempt, I flashed the AP but not one of the other things (I guess CP?) which resulted in the tablet getting bricked.
Long story short, I held both volume buttons and power to boot into a blue download mode (as opposed to a black one via holding power down + volume and selecting download mode, since the volume down + power nor the volume up + power combos weren't working) and flashed the stock rom to it properly.
Upon setup, I was still required to set up wi-fi, but it didn't attempt to install mobicontrol! I've been using the tablet normally since. Who would have known accidentally bricking the tablet was all I needed to do!

genesisboy4 said:
I solved this. Basically, I accidentally bricked the tablet, which I assume is what caused Samsung Knox to fail and thus Mobi Control didn't try installing on a fresh flash of Android 8.1. Fuller story below:
After 3 days straight of trying to reset the tablet, including flashing the combo file, trying anything I can think of, re-flashing the stock rom and seeing if the problem is gone, I finally fixed it.
What ended up happening was, while re-flashing the stock rom on my 4th attempt, I flashed the AP but not one of the other things (I guess CP?) which resulted in the tablet getting bricked.
Long story short, I held both volume buttons and power to boot into a blue download mode (as opposed to a black one via holding power down + volume and selecting download mode, since the volume down + power nor the volume up + power combos weren't working) and flashed the stock rom to it properly.
Upon setup, I was still required to set up wi-fi, but it didn't attempt to install mobicontrol! I've been using the tablet normally since. Who would have known accidentally bricking the tablet was all I needed to do!
Click to expand...
Click to collapse
Good to know. Congratulation. Does it still show secured by knox on boot screen?

I had no luck. I can't flash anything, got error "MDM mode, can't download ".

XDA.Samsung said:
Good to know. Congratulation. Does it still show secured by knox on boot screen?
Click to expand...
Click to collapse
Yes, it does.
XDA.Samsung said:
I had no luck. I can't flash anything, got error "MDM mode, can't download ".
Click to expand...
Click to collapse
Make sure you're using the right version of odin for your tablet and you're flashing the right version of android.

genesisboy4 said:
Yes, it does.
Make sure you're using the right version of odin for your tablet and you're flashing the right version of android.
Click to expand...
Click to collapse
Which version of Odin did you use?

XDA.Samsung said:
Which version of Odin did you use?
Click to expand...
Click to collapse
Odin3_v3.13.3

genesisboy4 said:
Odin3_v3.13.3
Click to expand...
Click to collapse
After tried 5 versions of Odin, include 2 different v3.13.3, finally got a good news. I can flash T387v firmware Andriod 8.1 and 9. But the bad news is I cannot brick it, no matter flashed only AP or BL. I tried to flash with T387W or T387T firmware, I got PIT error messages.
Which version of firmware were you using?

XDA.Samsung said:
After tried 5 versions of Odin, include 2 different v3.13.3, finally got a good news. I can flash T387v firmware Andriod 8.1 and 9. But the bad news is I cannot brick it, no matter flashed only AP or BL. I tried to flash with T387W or T387T firmware, I got PIT error messages.
Which version of firmware were you using?
Click to expand...
Click to collapse
I think I installed android version SM-T387V_1_20200520121029_yelpqjg66y_fac.

genesisboy4 said:
I think I installed android version SM-T387V_1_20200520121029_yelpqjg66y_fac.
Click to expand...
Click to collapse
Thank you. It looks like it's Android 9. Did you update it to Android 10?

XDA.Samsung said:
Thank you. It looks like it's Android 9. Did you update it to Android 10?
Click to expand...
Click to collapse
It's Android 8.1. If that file I mentioned is 9, then it's not the one I flashed, but was instead on my to-do list of troubleshooting steps. I was going to try flashing Android 9 and 10 but I got it working with 8.1 so I'm keeping it on that. Plus, the newer the android, the more secure Samsung Knox will be, so it will be harder breaking it.

Any idea where you downloaded it from? I cant seem to find a link.

quiqsilverr said:
Any idea where you downloaded it from? I cant seem to find a link.
Click to expand...
Click to collapse
Android 10: https://samfrew.com/download/Galaxy__Tab__A__/1hjk/VZW/T387VVRU3CUI2/T387VVZW3CUI2/

"The fact that it has MobiControl installed suggests it's a company device, and is therefore administered by that company's IT department. It's probably going to be difficult to remove MobiControl unless you talk to that IT department about it."
The above is a quote I found regarding Knox and the MobiControl app. Which tells me that this thread, although likely unintentional, is violating XDA Forum Rule #9:
9. Don't get us into trouble.
Don't post copyrighted materials or do other things which will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably shouldn't do it here either. This does not mean that we agree with everything that the software piracy lobby try to impose on us. It simply means that you cannot break any laws here, since we'll end up dealing with the legal hassle caused by you. Please use common sense: respect the forum, its users and those that write great code.
Click to expand...
Click to collapse
XDA does not wish to be held liable for circumventing device security regardless of intent of the user, which is why I'm closing this thread.
-Regards: Badger50