Database Info

The first case reset Warranty Bit in Galaxy Note 3 Exynos N900 successfully!!!

Hello forum,
I come from Vietnam, I have participated in this forum for a long time. The devs helped guys like me so much to be able to use our phone in the best ways.
Today I have one thing to share with you, may be it will help the devs to find a way to solve the problem of reseting warranty bit in Samsung Galaxy Note 3 into 0.
I bought my Note 3 N900 five months ago. At that time, I rooted my phone and then update my note 3 via OTA. But from the fist update which showed Warranty Bit: 1 (MJ7). I didn't update it via OTA any more.
Then I download a stock rom named "STOCK-DEODEX-ROOT-N900XXUCMJ7_N900OLBCMJ3_N900DXUCMJ3_HOME" of developer @nguyenxuanhoa then rooted it again and used it untill yesterday.
Yesterday, I found that my device wasn't rooted and CWM disappear. I couldn't understand. Then I installed CWM and rooted it again. After that. I uploaded rom cook version 9.0 then 8.1 (android 4.4.2) of developer @nguyenxuanhoa but it did't work well (couldn't use apps restored from titanium backup and couldn't logged in evernote)
Then I used the stock Mj7 4 files but just uploaded 1 file AP in order to restore my phone to android 4.3 but it was suspended at samsung logo. Then I went to stock recovey to wipe data and reboot, but it was fault: force close samsung keyboard.
In the last time, I flashed 4 files in stock MJ7 to restore again and OMG! The warranty bit was restored to 0. I can't understand but very happy. I can use Knox, of course. Everything in my phone was restored as when i bought it from the seller.
I hope that information will help you to guess how could we resset warranty bit of Galaxy Note 3 N900 into 0.
Stock Rom Mj7 4 files: Link/
STOCK-DEODEX-ROOT-N900XXUCMJ7_N900OLBCMJ3_N900DXUCMJ3_HOME: Part 1 Part 2
Rom cook by @nguyenxuanhoa: Link
{
"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"
}
View attachment 2628353
View attachment 2628354

Maaaaaaaaaaaaaaaaan
if what you did is true and we can all do it.
then thank you very much my freind and hope that this will help the devs defeat this knox app.

We need someone to try this I hope that is true
Sent from my SM-N900

DON AMIGO said:
Maaaaaaaaaaaaaaaaan
if what you did is true and we can all do it.
then thank you very much my freind and hope that this will help the devs defeat this knox app.
Click to expand...
Click to collapse
dannycanrock said:
We need someone to try this I hope that is true
Sent from my SM-N900
Click to expand...
Click to collapse
I'm not sure, because there are not many people keep their N3 in firmware Mj7 like me, so I don't know if this case is right with the other. I just post my case there and hope that someone can follow this and reset warranty bit successfully, too.

ii have a note 2, i have full wipe and flashed 4 tar in bl, csc, ap and nothing happens, i still have knox bit 1, i am curious how did you do that, is it because you download bl then upload it agian? hummm

If you look a little the menu is a little different for n900 not like n9005.Maybe different bootloaders diferent knox and maybe for n900 work.

luckyboy_103 said:
I'm not sure, because there are not many people keep their N3 in firmware Mj7 like me, so I don't know if this case is right with the other. I just post my case there and hope that someone can follow this and reset warranty bit successfully, too.
Click to expand...
Click to collapse
Yeaahh, thanks for your report. We are working on testing progress. I think maybe the reason that you flash many time and get luck. I don't know how and why but good work.
Send from my SM-N900 using Tapatalk 4 Pre

newxdabie said:
ii have a note 2, i have full wipe and flashed 4 tar in bl, csc, ap and nothing happens, i still have knox bit 1, i am curious how did you do that, is it because you download bl then upload it agian? hummm
Click to expand...
Click to collapse
No, I just flashed AP file for the first time, then flashed all 4 files in stock mj7 for the second time and.. it worked :d
Sent from my SM-N900 using Tapatalk

will somebody test this method.

luckyboy_103 said:
No, I just flashed AP file for the first time, then flashed all 4 files in stock mj7 for the second time and.. it worked :d
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
Make a guide for amateur like us...
Sent from my SM-N900 using XDA Premium 4 mobile app

ghalib87 said:
Make a guide for amateur like us...
Sent from my SM-N900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Maybe he got luck. Let's see how to do. Hope that's guide for developers to fix it perfect.
Send from my SM-N900 using Tapatalk 4 Pre

luckyboy_103 said:
No, I just flashed AP file for the first time, then flashed all 4 files in stock mj7 for the second time and.. it worked :d
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
I cant understand it... flashing ap before flash 4 files dont make any sense about it...because i realized that their flash bl first if you have knox bit the bl will load thia information and do not replace it...i guess there something is missing in your steps or because you flashed deox knox rom or rom with bl lower before...not sure

I can confirm this, However im not sure of the method. But I do remember It involved the MJ7 Firmware. At a point of flashing where my Phone got Soft Bricked, I noticed that the Warranty Bit was Reset and 0x0. At that Point the phone was not useable, and it was soft-bricked with a "Stuck on Boot Logo" Situation. However, After I installed CWM and SuperSu again, It was gone. In order to find out the exact method and to create a guide (And of course to take the bounty! ) I tried to recreate this over and over again, But It never worked out. Then I just ditched the idea thinking it might be a fault in the Recovery. Now that you have posted this in OP, I believe there is a trigger within the phone itself. The Phone which I tested too was a N900 and I was playing with the MJ7 Firmware.

newxdabie said:
I cant understand it... flashing ap before flash 4 files dont make any sense about it...because i realized that their flash bl first if you have knox bit the bl will load thia information and do not replace it...i guess there something is missing in your steps or because you flashed deox knox rom or rom with bl lower before...not sure
Click to expand...
Click to collapse
I can't understand, too. I flashed 4 files after flashing ap just because it was fault. There was nothing in my steps missed. I absolutely sure about that.
Sent from my SM-N900 using Tapatalk

JazonX said:
I can confirm this, However im not sure of the method. But I do remember It involved the MJ7 Firmware. At a point of flashing where my Phone got Soft Bricked, I noticed that the Warranty Bit was Reset and 0x0. At that Point the phone was not useable, and it was soft-bricked with a "Stuck on Boot Logo" Situation. However, After I installed CWM and SuperSu again, It was gone. In order to find out the exact method and to create a guide (And of course to take the bounty! ) I tried to recreate this over and over again, But It never worked out. Then I just ditched the idea thinking it might be a fault in the Recovery. Now that you have posted this in OP, I believe there is a trigger within the phone itself. The Phone which I tested too was a N900 and I was playing with the MJ7 Firmware.
Click to expand...
Click to collapse
Thank you for your confirmation. I am luckier than you while my phone was reset to 0x0 within any fault. I'm not sure it could happen again :d
Sent from my SM-N900 using Tapatalk

i'm sure that someone in this great forum will help us in this matter
and give us the method and hopefully help the devs here to defeat this knox app.

DON AMIGO said:
i'm sure that someone in this great forum will help us in this matter
and give us the method and hopefully help the devs here to defeat this knox app.
Click to expand...
Click to collapse
matbe downgrade between knox enable bootload can reset knox counter, i am in note 2 we have only 4.3 mk9, i ve doing this process lot of times and still knox bit =1 and i realized there are note 3 that have odin mode diffrent from yours, we have knox warrenty bit and ap swaev : A2, and your phone only has warenty bit, and tell me more one thing, when you flash the second time, you need turn indo odin mode(download mode) you already seeing knox bit = 0 this step or just after flashing 4 files? and what is your configuretion with odin? what version are you using? thx

newxdabie said:
matbe downgrade between knox enable bootload can reset knox counter, i am in note 2 we have only 4.3 mk9, i ve doing this process lot of times and still knox bit =1 and i realized there are note 3 that have odin mode diffrent from yours, we have knox warrenty bit and ap swaev : A2, and your phone only has warenty bit, and tell me more one thing, when you flash the second time, you need turn indo odin mode(download mode) you already seeing knox bit = 0 this step or just after flashing 4 files? and what is your configuretion with odin? what version are you using? thx
Click to expand...
Click to collapse
Regret that I didn't see warranty line when I flashed 4 files and even after that. I only saw it after flashing CWM failed as I mentioned in #1.
I just flashed files by odin normally. Version of odin is 3.04!

luckyboy_103 said:
Regret that I didn't see warranty line when I flashed 4 files and even after that. I only saw it after flashing CWM failed as I mentioned in #1.
I just flashed files by odin normally. Version of odin is 3.04!
Click to expand...
Click to collapse
so you flashed it dont in odin mode?, if you in odin mode you should see it

It mean that:
- flash 4.4.2 rom - > flash ap -> let's it boot in 20-30s -> wipe -> flash all 4 file (bootloader MJ7 again?) -> wipe
So, simply it can tell: Maybe a software bug in MJ7 bootloader that will check system integrity of system and set KNOX flag again to 0 (it was 1) in bootloader.
Why it's a bootloader bug? It didn't check check warranty bit was writen. It will check and rewrite everytime you flash it. (Maybe bootloader will check a flag/file in data/system/hidden partition that was set by kernel/OS that tell integrity state of system and set know flag)
So now i need a volunteer that have equal or below MJ7 (MJ1/MJ7)... And flash AP (MJ7) - when flash with odin please don't check reboot. when it flashed. Go to Recovery and wipe. Then flash 4 files include bootloader again.

How to restore warranty at sammy custom roms 4.3, 4.4.2, updated added ZSUFNJ2

First a big thanks to anyone who is cooking roms writing apps scripts etc here and to user faria for the param.bin file.
Now the point, i found a solution to restore warranty at custom roms and i like to share with you.
This checked and working at any 4.3, 4.4 sammy rom.
Now what u need
1) mj5 bootloader
2) a rom compatible with mobile odin
3) mobile odin (i am using pro but i think is not necessary such as everoot is not necessary, don't forget if u don't use pro u have to download with app and the proper mobile odin kernel from chainfire's post)
4) triangle away
5) the files attached at end
6) stock kernel and recovery ( u can extract them from same version original rom, attention don't use other rom with other version stock kernel because u will have not wifi)
Ok now the procedure install and open mobile odin
Put at the place is saying param the param.bin file
Put at the place is saying kernel the stock kernel
check to wipe the dalvik cache (is not necessary but do it)
Flash and reboot
Check root, is ok 99% but if is not ok flash with your custom recovery supersuupdate
and after reboot check again root
If ok open again mobile odin and
put at the place is saying recovery stock recovery and flash it
After reboot install triangle away follow dev instuctions and reset the counter.
Thats all after reboot shut down your phone enter download mode and check your warranty.
Now i am attaching the param.bin file (u have to extract with winrar)
and some ready packets (kernel, recovery, param.bin) for some 4.4.2 versions, u can use them or use your own with param.bin file).
The srvr is paid but u can download as free user too (is not necessary to pay)
Thanks for reading.
Files:
4.4.2 XXUFND3.rar - 15.1 MB
4.4.2 XXUFNE1.rar - 15.1 MB
4.4.2 XXUFNE2.rar - 15.2 MB
param.rar - 877 KB
4.4.2 XXUFNG4.rar - 27.4 MB
4.4.2 XXUFNG3.rar - 15.0 MB
4.4.2 XXUFNH2.rar - 15.0 MB
4.4.2 XXUFNI1.rar - 15.0 MB
4.4.2 XXUFNI4.rar - 15.0 MB
4.4.2 ZSUFNJ2.rar - 15.6 MB
And some new important info.
I tried to a rom not compatible with mobile odin (the mobile odin didn't restart to flash the kernel etc)
I rebooted at once manual with 4way reboot to recovery without closing the app and mobile odin worked made the flash.
After reboot i tried to see if my custom recovery was ok and was everything ok.
After i flashed stock recovery and made the same didn't restart,i restarted again with 4way reboot at recovery and made the flash safe.
And know the good one, it did the same with triangle away, i checked reset counter and didn't restart, i restarted at recovery at once with 4way reboot and worked.
Custom Binary Download No, official, official, warranty bit 0 with any custom rom (sammy base)
This is a personal experience which i am sharing with u, i am not a developer or something other and i am not responsible if something goes bad.
Use it with your own responsibility.
{
"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"
}
[/URL][/IMG]

Great stuff
vagsvag said:
First a big thanks to anyone who is cooking roms here and to user faria for the param.bin file.
Now the point, i found a solution to restore warranty at custom roms and i like to share with you.
This checked and working at any 4.3, 4.4 sammy rom (only at latest 4.4.2 XXUFNG4 i haven't test it)
Now what u need
1) mj5 bootloader
2) a rom compatible with mobile odin
3) mobile odin (i am using pro but i think is not necessary such us everoot is not necessary, don't forget if u don't use pro u have to download with app and the proper mobile odin kernel from chainfire's post)
4) triangle away
5) the files attached at end
6) stock kernel and recovery ( u can extract them from same version original rom, attention don't use other rom with other version stock kernel because u will have not wifi)
Ok now the procedure install and open mobile odin
Put at the place is saying param the param.bin file
Put at the place is saying kernel the stock kernel
check to wipe the dalvik cache (is not necessary but do it)
Flash and reboot
Check root, is ok 99% but if is not ok flash with your custom recovery supersuupdate
and after reboot check again root
If ok open again mobile odin and
put at the place is saying recovery stock recovery and flash it
After reboot install triangle away follow dev instuctions and reset the counter.
Thats all after reboot shut down your phone enter download mode and check your warranty.
Now i am attaching the param.bin file (u have to extract with winrar)
and some ready packets (kernel, recovery, param.bin) for some 4.4.2 versions, u can use it or use your own with param.bin file).
The srvr is paid but u can download as free user too (is not necessary to pay)
Thanks for reading and again to user faria for the param.bin file.
Files:
4.4.2 XXUFND3.rar - 15.1 MB
4.4.2 XXUFNE1.rar - 15.1 MB
4.4.2 XXUFNE2.rar - 15.2 MB
param.rar - 877 KB
Click to expand...
Click to collapse
Great stuff. :good:
Waiting for 4.4.2 XXUFNG4 version.

xbean said:
Great stuff. :good:
Waiting for 4.4.2 XXUFNG4 version.
Click to expand...
Click to collapse
Thank you, u can try it with XXUFNG4 too 99,99% will work extract kernel and recovery from original rom and use and the param.bin file with the posted procedure.
It is the same param.bin file everywhere. You can use this procedure at 4.3 too.

1rst post updated
Ok guys i checked at 4.4.2 XXUFNG4 and working
I am attaching kernel recovery and param.bin (by mistake i uploaded and the modem ignore it)
Link:
4.4.2 XXUFNG4.rar - 27.4 MB
And some new important info.
I tried to a rom not compatible with mobile odin (the mobile odin didn't restart to flash the kernel etc)
I rebooted at once manual with 4way reboot to recovery without closing the app and mobile odin worked made the flash.
After reboot i tried to see if my custom recovery was ok and was everything ok.
After i flashed stock recovery and made the same didn't restart,i restarted again with 4way reboot at recovery and made the flash safe.
And know the good one, it did the same with triangle away, i checked reset counter and didn't restart, i restarted at recovery at once with 4way reboot and worked.
Custom Binary Download No, official, official, warranty bit 0 with DEEP IMPACT ROM v2.3
This is a personal experience which i am sharing with u, i am not a developer or something other and i am not responsible if something goes bad.
Use it with your own responsibility.

hi dev,
my note2 has xxufng4 bootloader,
i am noob for this work pls give with screenshots for safe side
thank u

Is this a method to reset the warranty bit from 1x1 to 0x1?
My warranty bit is 1x1 since I flashed the mk9 bootloader and then a custom recovery. I've since updated the bootloader to ND3.

JGKUMAR1976 said:
hi dev,
my note2 has xxufng4 bootloader,
i am noob for this work pls give with screenshots for safe side
thank u
Click to expand...
Click to collapse
tonylee000 said:
Is this a method to reset the warranty bit from 1x1 to 0x1?
My warranty bit is 1x1 since I flashed the mk9 bootloader and then a custom recovery. I've since updated the bootloader to ND3.
Click to expand...
Click to collapse
@JGKUMAR1976 Sorry this is working only with mj5 bootloader
@tonylee000 Sorry i don't know a way to change warranty bit, this guide is resetting Custom Binary Download from any number to no

vagsvag said:
@JGKUMAR1976 Sorry this is working only with mj5 bootloader
@tonylee000 Sorry i don't know a way to change warranty bit, this guide is resetting Custom Binary Download from any number to no
Click to expand...
Click to collapse
Ok cool. That's what I suspected. I don't see the point in the risk involved? If you've not flashed a bootloader newer than mj5 then its a simple case of flashing a stock rom from sammobile, root, triangle away, unroot. Job done. Then your phone is in a condition where it can be returned for repairs under warranty. If you return it with a custom rom installed then it's gonna be obvious the warranty been violated or is there something I'm missing here?
Ifyour not returning the phone to use warranty then you don't need to bother?

tonylee000 said:
Ok cool. That's what I suspected. I don't see the point in the risk involved? If you've not flashed a bootloader newer than mj5 then its a simple case of flashing a stock rom from sammobile, root, triangle away, unroot. Job done. Then your phone is in a condition where it can be returned for repairs under warranty. If you return it with a custom rom installed then it's gonna be obvious the warranty been violated or is there something I'm missing here?
Ifyour not returning the phone to use warranty then you don't need to bother?
Click to expand...
Click to collapse
You missed a point, the point is that most of us have phones with faulty emmc chip etc and many of our phone die suddenly, how do you flash your 9 months phone when is totally dead and goes only in download mode? Impossible, the next thing is to sent it 4 repair to change motherboard. The first thing they look at service is your binary count, if is ok your repair is free if is not 180 euro from your pocket goes away. I hope you understand the meaning of all this now.
Sent from my GT-N7100 using Tapatalk 2

vagsvag said:
You missed a point, the point is that most of us have phones with faulty emmc chip etc and many of our phone die suddenly, how do you flash your 9 months phone when is totally dead and goes only in download mode? Impossible, the next thing is to sent it 4 repair to change motherboard. The first thing they look at service is your binary count, if is ok your repair is free if is not 180 euro from your pocket goes away. I hope you understand the meaning of all this now.
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
I wasn't being funny with you was wondering what the end game was. I wouldn't worry too much about the Emmc problem. If your phone is only 9 months old you should be fine. Early note 2s had the dodgy chip or 'insane' chip. My note 2 is one of those. There are apps you can get off the play store to tell you if you have an insane chip or a safe one. If the service centre can see download mode and see the binary counter is 0 then wouldnt they be able to see the warranty bit too? Unfortunately my warranty bit is now set to 1 so my warranty is probably not valid. I've had mine for 22 months now so I only have 2 months left on the warranty anyway so its not really a big problems for me now. As i recall the 'insane' emmc problems occurred because of a kernel issue in android 4.1.1 that burnt the chip out which was fixed in the 412 uodate

tonylee000 said:
I wasn't being funny with you was wondering what the end game was. I wouldn't worry too much about the Emmc problem. If your phone is only 9 months old you should be fine. Early note 2s had the dodgy chip or 'insane' chip. My note 2 is one of those. There are apps you can get off the play store to tell you if you have an insane chip or a safe one. If the service centre can see download mode and see the binary counter is 0 then wouldnt they be able to see the warranty bit too? Unfortunately my warranty bit is now set to 1 so my warranty is probably not valid. I've had mine for 22 months now so I only have 2 months left on the warranty anyway so its not really a big problems for me now. As i recall the 'insane' emmc problems occurred because of a kernel issue in android 4.1.1 that burnt the chip out which was fixed in the 412 uodate
Click to expand...
Click to collapse
The warranty bit at mj5 bootloader is cosmetic 1000 flashes to do 0 will stay. Mine is 18 months old.
The fix they made is dirty fix and not really fix also the kernel hadn't any problem at 4.1.1 the problem was the chip and the fix they made was to setup the newer kernels to don't write at certain blocks which had the problem..If you search little about this you will see and "safe" emmc chips 1301 etc have also sds symptom.
The secret with these faulty chips is i believe to don't fill all the internal memory, and also if you have warranty to be active.

First post updated added support for XXUFNG3
4.4.2 XXUFNG3.rar - 15.0 MB

First post updated added XXUFNH2, XXUFNI1
4.4.2 XXUFNH2.rar - 15.0 MB
4.4.2 XXUFNI1.rar - 15.0 MB

Does this still work??
Very Curious!! :crying:

Bunny2rock said:
Does this still work??
Very Curious!! :crying:
Click to expand...
Click to collapse
Working like a charm.
Sent from my GT-N7100 using Tapatalk 2

Do I understand it right that with this method you can reset knox_warranty_void to 0?
Everyone is saying that it is not possible! That would be very nice

teddyteddy92 said:
Do I understand it right that with this method you can reset knox_warranty_void to 0?
Everyone is saying that it is not possible! That would be very nice
Click to expand...
Click to collapse
I too wanted to know same...

teddyteddy92 said:
Do I understand it right that with this method you can reset knox_warranty_void to 0?
Everyone is saying that it is not possible! That would be very nice
Click to expand...
Click to collapse
mietens said:
I too wanted to know same...
Click to expand...
Click to collapse
No guys this method reseting the flash counter (custom binary download from any number to no even if you have custom sammy based rom installed) not the knox warranty void and working with mj5 bootloader and older. At mj5 bootloader the knox warranty is cosmetic, 300 flashes to do 0 will stay. If you have installed newer than mj5 bootloader don't try it you'll loose your time.
Sent from my GT-N7100 using Tapatalk 2

First post updated added support for XXUFNI4
4.4.2 XXUFNI4.rar - 15.0 MB

First post updated added support for ZSUFNJ2
4.4.2 ZSUFNJ2.rar - 15.6 MB

Awful quiet around here about BOE1, who wants the update.zip?

I have the zip file if anyone has a way for me to get it posted here for devs to get to work on it.

chetqwerty said:
I have the zip file if anyone has a way for me to get it posted here for devs to get to work on it.
Click to expand...
Click to collapse
Upload it to android file host if you have dev status but if not you can upload it to google drive or any other hosting site.
EDIT: If you can get it uploaded somewhere, I'm sure @muniz_ri wouldn't mind looking at it and since it sounds like it prevents downgrading, we may be able to make a ROM out of it using the OD5 bootloader like what was done with the VZW S4 Lollipop update.

No not a dev, uploaded it to a free service http://www.fileconvoy.com/dfl.php?id=g71d4dc928ae33b36999687091905b660934562bab don't know why eset said it was unsafe, it downloaded fine when i allowed it. so just allow its fine.
Tried another service, FileDropper for those who have a problem
http://www.filedropper.com/update_3
ESET Antivirus didn't have a problem with this one
Shotty the first release @muniz_ri LOL

This is a OC4 to OE1 update.

timeToy said:
This is a OC4 to OE1 update.
Click to expand...
Click to collapse
Someone in another thread said they took the OTA and can't downgrage back to kikkat or lollipop via odin.
Sent from my SM-G900V using XDA Free mobile app

aholeinthewor1d said:
Someone in another thread said they took the OTA and can't downgrage back to kikkat or lollipop via odin.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
I personally have a Dev. Ed. S5, so I don't mind, as long as I don't flash the bootloader (aboot.mbn), so I am still interested in this.

It's been confirmed by muniz_ri that the qfuse counter was updated. If you update to OE1, there's no going back.

Guess i don't care about going back as long as i can have root and tether. I deleted the file from cache just have to get rid of this nagging install update message.

@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.

muniz_ri said:
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
Click to expand...
Click to collapse
Awesome. Downloading now.

muniz_ri said:
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
Click to expand...
Click to collapse
And here is a deodexed version for testing: G900V_OE1_Stock_Rooted_Deodexed_ROM

muniz_ri said:
And here is a deodexed version for testing: G900V_OE1_Stock_Rooted_Deodexed_ROM
Click to expand...
Click to collapse
I see that you say "if you've taken the ota and kept root" does that mean that you will retain root or is it hit or miss? any reports either way? also, have you done ay tweaks to this? enabled tether or anything besides deodexing? Thanks

I have a dev. ed. and it worked for me, including Advanced Calling, but I also flashed the rest of the firmware from the update file(sbl1.mbn sdi.mbn rpm.mbn and tz.mbn)
{
"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"
}
awesome, Thanks !

muniz_ri said:
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
Click to expand...
Click to collapse
muniz_ri said:
And here is a deodexed version for testing: G900V_OE1_Stock_Rooted_Deodexed_ROM
Click to expand...
Click to collapse
Sorry it's taken so long to reply. I was at a party when I replied and downloaded the ROMs and didn't want to test them without having my computer in case of an Odin emergency. lol.
I'll be testing them shortly.

timeToy said:
I have a dev. ed. and it worked for me, including Advanced Calling, but I also flashed the rest of the firmware from the update file(sbl1.mbn sdi.mbn rpm.mbn and tz.mbn)
awesome, Thanks !
Click to expand...
Click to collapse
Thanks, which ROM did you test or both?

muniz_ri said:
Thanks, which ROM did you test or both?
Click to expand...
Click to collapse
I tried Odexed only, I'm not necessarily interested in deodexed until Xposed is more stable in Lollipop and TW. I also modified your script to avoid wiping. All good

timeToy said:
I tried Odexed only, I'm not necessarily interested in deodexed until Xposed is more stable in Lollipop and TW
Click to expand...
Click to collapse
Thanks, created new thread for the ROM's here: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
---------- Post added at 11:56 PM ---------- Previous post was at 11:24 PM ----------
chetqwerty said:
I see that you say "if you've taken the ota and kept root" does that mean that you will retain root or is it hit or miss? any reports either way? also, have you done ay tweaks to this? enabled tether or anything besides deodexing? Thanks
Click to expand...
Click to collapse
After reviewing the ota zip I have confirmed that it checks for stock /bin/ddexe which is modified when a device is rooted, therefore the official OC4-to-OE1 ota will fail on all rooted devices. I have not seen an OD5-to-OE1 ota update.zip in order to review.

chetqwerty said:
Guess i don't care about going back as long as i can have root and tether. I deleted the file from cache just have to get rid of this nagging install update message.
Click to expand...
Click to collapse
Confirming, if I'm not rooted, there's no way to disable the annoying update nag? I'm on BOC4 and I can't use the phone without the stupid msg popping up!

I'm a bit of a noob, so apologies if this question has an obvious answer:
Does any of this thread mean there's now a way to downgrade or root a non-rooted OE1?

equazcion said:
I'm a bit of a noob, so apologies if this question has an obvious answer:
Does any of this thread mean there's now a way to downgrade or root a non-rooted OE1?
Click to expand...
Click to collapse
No

New Samsung user, where do I start?

Hello everyone, from my new Galaxy S6 Edge on Sprint. I've been with Sprint for 15 years and have been on Android since the HTC Hero. Every time a HTC fagship device on Sprint came out, it found its way into my pocket. I finally decided to jump ship from HTC and give Samsung a shot.
With the Samsung S6 Edge being my first Sammy device, there seems to be a lot I need to learn. Are there any tips or tricks that I should know?
I'm on a cross country drive and picked up the phone in Yakima WA last night. It will be several days before I have access to a PC, so when my trip ends in Wisconsin. I want to have everything researched on how to root and install TWRP.
First of all is this KNOX thing something I should be concerned for? What is the go-to method for root? Best Buy ran the BOI1 update on me yesterday. Is there a one click root available? Anything special needed to know for installing TWRP?
Thanks, misfit0313

misfit0313 said:
Hello everyone, from my new Galaxy S6 Edge on Sprint. I've been with Sprint for 15 years and have been on Android since the HTC Hero. Every time a HTC fagship device on Sprint came out, it found its way into my pocket. I finally decided to jump ship from HTC and give Samsung a shot.
With the Samsung S6 Edge being my first Sammy device, there seems to be a lot I need to learn. Are there any tips or tricks that I should know?
I'm on a cross country drive and picked up the phone in Yakima WA last night. It will be several days before I have access to a PC, so when my trip ends in Wisconsin. I want to have everything researched on how to root and install TWRP.
First of all is this KNOX thing something I should be concerned for? What is the go-to method for root? Best Buy ran the BOI1 update on me yesterday. Is there a one click root available? Anything special needed to know for installing TWRP?
Thanks, misfit0313
Click to expand...
Click to collapse
First you're on the wrong thread. You should be in the Q&A section. First you may need to install the Samsung drivers to your computer. Download the preferred Odin 3.10.6 flashing tool. Go to your phone settings/build number, and tap 10 times until you see developer options enabled. Next go to settings/developer options, scroll down to Oem unlocking and turn it on. Next, to root you will need to use the odin tool to install the custom rooted kernel. Once that's complete, you can install TWRP. I'll include my link to twrp and kernel. Remember to Odin kernel first, then twrp. I don't think I forgot anything.
Follow the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=3102034
Edit:
Knox will be tripped rooting your phone. Will not be able to use Samsung pay, voids your Samsung warranty so you cant send back to Samsung, but does not void your carrier warranty, you can take it to them. Nothing else to worry about knox, doesn't affect anything.

Soooperstar said:
First you're on the wrong thread. You should be in the Q&A section. First you may need to install the Samsung drivers to your computer. Download the preferred Odin 3.10.6 flashing tool. Go to your phone settings/build number, and tap 10 times until you see developer options enabled. Next go to settings/developer options, scroll down to Oem unlocking and turn it on. Next, to root you will need to use the odin tool to install the custom rooted kernel. Once that's complete, you can install TWRP. I'll include my link to twrp and kernel. Remember to Odin kernel first, then twrp. I don't think I forgot anything.
Follow the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=3102034
Edit:
Knox will be tripped rooting your phone. Will not be able to use Samsung pay, voids your Samsung warranty so you cant send back to Samsung, but does not void your carrier warranty, you can take it to them. Nothing else to worry about knox, doesn't affect anything.
Click to expand...
Click to collapse
Hey, I have a question... If he's on OI1 can he root and flash TWRP or should he Odin to OH1 then root and flash TWRP and then rom???

JediMindTrixx said:
Hey, I have a question... If he's on OI1 can he root and flash TWRP or should he Odin to OH1 then root and flash TWRP and then rom???
Click to expand...
Click to collapse
No! He should do the normal root process. According to the OI1 update you can't go back. The rom works on OI1 according to reports
{
"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"
}
Sent from my SM-G925P using Tapatalk

Soooperstar said:
No! He should do the normal root process. According to the OI1 update you can't go back. The rom works on OI1 according to reports View attachment 3492662
Sent from my SM-G925P using Tapatalk
Click to expand...
Click to collapse
That's right forgot about not being able to go back. Thanks! :good:

Thanks Soooperstar... There's a reason why you shouldn't app and drive at the same time, you accidentally post in the wrong thread.
I've rooted, installed recovery, and S-off'ed every single HTC that I owned, the talk about Odin and KNOX threw me off a bit.

misfit0313 said:
Thanks Soooperstar... There's a reason why you shouldn't app and drive at the same time, you accidentally post in the wrong thread.
I've rooted, installed recovery, and S-off'ed every single HTC that I owned, the talk about Odin and KNOX threw me off a bit.
Click to expand...
Click to collapse
Yea I had the OG EVO back in the day. I know all about it. Samsung is much simpler when it comes to rooting

misfit0313 said:
Thanks Soooperstar... There's a reason why you shouldn't app and drive at the same time, you accidentally post in the wrong thread.
I've rooted, installed recovery, and S-off'ed every single HTC that I owned, the talk about Odin and KNOX threw me off a bit.
Click to expand...
Click to collapse
Odin is like RUU and Knox is Sammy's security...
Sent from my SM-G925P using XDA Free mobile app

This looks like the correct kernel to flash to obtain root? http://forum.xda-developers.com/showthread.php?t=3166293
[KERNEL][925P/R4] UniKernel v8-0001

misfit0313 said:
This looks like the correct kernel to flash to obtain root? http://forum.xda-developers.com/showthread.php?t=3166293
[KERNEL][925P/R4] UniKernel v8-0001
Click to expand...
Click to collapse
Correct.... Be sure to get the 925p

Thank you again. I'm rooted and have TWRP installed. A message popped up afterwards ”unauthorized actions have been detected galaxy s6". It was taken care of by freezing "SecurityLogAgent" with TiBu.

[BASEBAND-FIRMWARE-MODEMS]Verizon Samsung Galaxy S5 {SM-G900V/KLTEVZW}[ODIN]

THE OFFICIAL BASEBAND​​
FIRMWARE MODEM UPDATES​​​
Verizon Samsung Galaxy S5​​
{SM-G900V/KLTEVZW}​​
{
"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"
}
{The above image is a refrence of all the Stock Firmware, Release Dates, etc...}
CLICK HERE TO EXPANDED THE ABOVE IMAGE
***INFORMATION REGARDING***
***NEW/REWORKED UPDATES***​
The Modem packages were recently reworked to include the "much needed" Baseband files (of course) pulled from the Official Samsung Stock Firmware.
This is ONLY because the following list of files are ALL of the Baseband/Modem files that are actually the part of the Firmware that controls ALL the radio devices within the GS5 to include (but, not limited to) the GPS, WiFi, Bluetooth, NFC, Cellular Data/Voice, etc...
MODEM.BIN
NON-HLOS.BIN
RPM.MBN
SBL1.MBN
SDI.MBN
TZ.MBN
Please keep in mind that, because these functions are Highly Regulated & Certified, they are actually Separate from the Android Operating System (aka the Firmware ROM installed like AOSP, LineageOS, etc...).
This is the reason that, after flashing the "Baseband Firmware Modem Update", it DOESN'T DIRECTLY AFFECT the Android Firmware installed on your devide. Your Android Firmware (basically) takes note of the update and updates itself to reflect those said changes (simply put without getting too deep).
DISCLAIMER/FYI
- Any process (like updating your modem) via Odin and/or Custom Recovery is simple/easy to do but, as always, if your not sure of what your doing and don't do your research (ie... searching, asking questions, etc... FIRST), then you take the risk of damaging your device.
- I take no responsibility for any unexpected results or damage that may happen but, we are always willing to provide assistance to help you out.
- Also keep in mind that when performing any unconventional updates, unlocking, rooting, etc... you may end up "voiding your warranty"!
INSTRUCTIONS
1. If not already done, be sure your PC/LPTP has the latest "Samsung USB Driver for Mobile Phones" installed.
2. Download the ".tar.md5" Baseband Firmware Modem file you need from any of the Download Links provided (below).
3. Power off your device and then enter Download Mode (aka Odin Mode) by using the required key combination ("Home" & "Volume Down" then "Power").
4. Connect the USB cable to the Device and PC.
5. Open Odin and select the PDA/AP and choose the ".tar.md5" Modem file you downloaded.
{Please Note: It's typically reccomended to use Odin v3.07-v3.12 but, other versions may also work.
6. In Odin, please be sure not to make any additional selections than the default that was already selected when you opened Odin.
7. Select the Odin "Start" button at the bottom & be patient for the process to complete and Odin should reflect a Green "PASS" when completed (The device will reboot automatically when done).
PRIMARY DOWNLOAD LINK
(NEW UPLOADS BEING WORKED ON. PLEASE USE)
(THE BELOW ALTERNATIVE DOWNLOAD LINK)
Baseband Firmware Modem Updates {Odin Flashable} - XDA DevDB Downloads
ALTERNATIVE DOWNLOAD LINK
Baseband Firmware Modem Updates {Odin Flashable} - Android File Host
PLEASE NOTE: It has been decided not to pursue the Recovery Flashable (aka TWRP, CWM, etc...) Modem Updates at the present time. We apologize for the inconvenience...
Special Mentions/Credits
Samsung - For the Device.
Sammobile - For the Software/Firmware.
The XDA fAMILY - For Valuable Member Feedback.
Let's not forget - To All The Girls We've Loved Before... (LOL!)
Click Here If You Would Like To Donate To My Developements
~{Donations Are Appreciated, but Never Necessary...}~
​PLEASE NO MIRRORS!
.
XDA:DevDB Information
[BASEBAND-FIRMWARE-MODEMS]Verizon Samsung Galaxy S5 {SM-G900V/KLTEVZW}[ODIN], Tool/Utility for the Verizon Samsung Galaxy S5
Contributors
Ibuprophen, klabit87
Version Information
Status: Stable
Current Stable Version: G900VVRU2DQL1
Stable Release Date: 2018-01-17
Created 2019-05-02
Last Updated 2019-06-20

Reserved

Reserved

Can i flash them on KK?
What are the differences between them ?
thanks

HazeMC said:
Can i flash them on KK?
What are the differences between them ?
thanks
Click to expand...
Click to collapse
I don't see why not. I know we can on the Verizon S4. @Stupifier may be able to tell you for sure though.
These are all modems from the lollipop releases.
Zips are ss and ff flashable.
And some people prefer Odin so I posted those too.

Thank you for this.
Anyone have the OG5 and OK3 modems? This thread would be the perfect place to add them.

painiac said:
Thank you for this.
Anyone have the OG5 and OK3 modems? This thread would be the perfect place to add them.
Click to expand...
Click to collapse
I will add them tonight. Sorry I lost track of things.

klabit87 said:
I will add them tonight. Sorry I lost track of things.
Click to expand...
Click to collapse
Nothing to apologize for!

painiac said:
Nothing to apologize for!
Click to expand...
Click to collapse
Safestrap flashables are added for OG5 and OK3.

klabit87 said:
Safestrap flashables are added for OG5 and OK3.
Click to expand...
Click to collapse
Very much appreciated!

I have G900V but I'm outside US and my provider does not suport lte band 4, 13.
Can you flash G900F moden on G900V? Would that give my phone access to diferent lte band?
Thanks.

Looking for the PB1 modem for CM13

Nandr0idC0nsumer said:
Looking for the PB1 modem for CM13
Click to expand...
Click to collapse
this one?
https://www.androidfilehost.com/?fid=24459283995308895
Actually this one caused me bootloops. not sure if it works. had to flash back to NCG

thaijunk said:
this one?
https://www.androidfilehost.com/?fid=24459283995308895
Actually this one caused me bootloops. not sure if it works. had to flash back to NCG
Click to expand...
Click to collapse
Thanks. I flashed the full stock PB1 tar to get it (big mistake) and went through hell and back to unlock the bootloader and go back to CM xD

I was wondering if there is a PF4 modem zip file for our phones?

Sorry everybody. PB1, PD1, and PF4 have been added.
If you need/prefer odin tar files let me know.
i dont feel anybody uses them based on the downloads of previous tar files.

I flashed the modem but never changed
Sent from my SM-G900V using XDA-Developers mobile app

ozz200127 said:
I flashed the modem but never changed
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
That does not tell me much.
Did you use FlashFire? Safestrap? or TWRP?
As far as I know they have only been flashed with SafeStrap.
I have not had the chance to test with TWRP.
I can upload others that will work for TWRP if that is the issue.
Might be a day or 2 but I will.

I use twrp...the flash went through but it didn't change
Sent from my SM-G900V using XDA-Developers mobile app

ozz200127 said:
I use twrp...the flash went through but it didn't change
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
ok. I will update them for twrp in the next day or 2.
Sorry. these were started before the bl unlock exploit was developed.
and I never thought to test it myself until you brought it to my attention.