Database Users

[Guide? May be not] N9005 - How I delete KNOX and flash BMJ3 over BMJ1

(Flashed MJ1 over MI7 before...)
Hi @all
Because I'm a retired man I need my Note 3 for my personal use only. Not for Enterprise or Government working, then I don't need the hateful KNOX.
After customer recovery install and root access, the first thing I make is delete all apk and more from it.
1 - From system/app I delete:
ContainerAgent.apk + odex
ContainerEventsRelayManager.apk + odex
FusedLocation.apk + odex
KLMSAgent.apk + odex
KNOXAgent.apk + odex
KNOXAttestationAgent.apk + odex
KNOXStore.apk + odex
KNOXStub.apk
SPDClient.apk + odex
From system/containers I delete:
All .apk + .zip file and 2 apk inside subfolder framework
2 - Before flash by Odin3 v3.09 I make my Rom BMJ1 reduced, only whit: (Now BMJ3)
boot.img
cache.img.ext4
hidden.img.ext4
modem.bin
NON-HLOS.bin
recovery.img
system.img.ext4 ---> ONLY
No KNOX bootloader, no tz.mbn (this is TIMA from Knox)
I make this with the Tool Tar.md5.Packager from A.S._id DEV. Thanks A.S._id, this is a good tool. Thanks bohdans also.
At end I have a Rom-BMJ1.tar.md5 only whit that 7 modules. (Now BMJ3)
Flashed twice for a double test over data, worked well whithout issues.
3 - Now if I type getprop on Shell Terminal Emulator I have:
[ro.bootloader]: [N9005XXUBMI7] --> This is the original bootloader not changed.
But and:
[ro.build.PDA]: [N9005XXUBMJ1] --> and more MJ1 the new. (Now MJ3)
[ril.product_code]: [SM-N9005ZKETPH] --> Replaced the original csc by TPH from my Country by default.
If I help somebody whit I'm happy
If someone have some different opinions, please post here.
Thanks

Today flashed MJ3 over MJ1 whit same method. Replaced the csc version from OXA to OXX whit the TPH, csc from my Country.
Made a Rom MJ3 reduced, all like on OP but to MJ3.
The bootloader continue [ro.bootloader]: [N9005XXUBMI7] --> Original bootloader not changed.
Works well.

If you care about privacy and permissions you will find that Knox is actually great. Like having two separate smartphones on one smartphone where you can keep all your personal stuff on Knox and stuff you do not care about on the regular side.

desiregeek said:
If you care about privacy and permissions you will find that Knox is actually great. Like having two separate smartphones on one smartphone where you can keep all your personal stuff on Knox and stuff you do not care about on the regular side.
Click to expand...
Click to collapse
Thank You but I know all that reading this:
http://www.samsung.com/global/business/mobile/solution/security/samsung-knox
And this:
https://www.samsungknox.com/overview/technical-details
I not need that.

Some data about KNOX:
Attached

Today Flashed the Rom from my Country, complete, no more reduced like on OP:
Model: SM-N9005
Country: Portugal (TPH)
Version: Android 4.3
Product Code: TPH
PDA: N9005XXUBMJ3
CSC: N9005OXXBMJ3
MODEM: N9005XXUBMJ2
My bootloader now is [ro.bootloader]: [N9005XXUBMJ3]
Whit Odin3 v3.09, no issues, works well.

ValenteL said:
Today Flashed the Rom from my Country, complete, no more reduced like on OP:
Model: SM-N9005
Country: Portugal (TPH)
Version: Android 4.3
Product Code: TPH
PDA: N9005XXUBMJ3
CSC: N9005OXXBMJ3
MODEM: N9005XXUBMJ2
My bootloader now is [ro.bootloader]: [N9005XXUBMJ3]
Whit Odin3 v3.09, no issues, works well.
Click to expand...
Click to collapse
Hi ValenteL, I am having different issue from yours but i think your method would help me to unbrick my phone.
I have a N9005 16G hongkong TGY stock rom. And 1 beautiful day i've decided to change my rom to UK BTU latest rom (as i always did for my note 2). Downloaded the rom, flashed via odin and got stuck at Odin: Imvalid ext4 Image.
Then I flashed back my stock rom (1 file .tar.md5, and all 4 files including AP, BL, CP, CSC files. All not succeeded with the error on the phone is SW REV check fail [aboot] fused 2 > binary 1. In Odin it stopped at aboot.mbn fail.
As consulted from other people, because i flashed a newer rom than my stock, even it was not successful, I can't go back to my older stock, and i have to wait for the Hk TGY rom to be upgraded. It will take forever because they are still on MI7 firmware.
And other thing is my N9005 is 16G phone, so i cant flash the 32G either (it said something about storage, i forgot).
So reading your posts, i thought i could extract newer bootloader, and put it in older stock rom? Please help me with this.
Thank you very much.

blackj30 said:
Hi ValenteL, I am having different issue from yours but i think your method would help me to unbrick my phone.
I have a N9005 16G hongkong TGY stock rom. And 1 beautiful day i've decided to change my rom to UK BTU latest rom (as i always did for my note
Click to expand...
Click to collapse
Hi
Unfortunately I can't help You. Your Note 3 is 16 GB and mine is 32 GB. We can't compare the Note 2 whit Note 3, see my post before whit attachments. On first we have at left the Note 2 at right the Note 3 whit all controlled by KNOX Bootloader.
But I try.
If you flash the customer Recovery 6.0.4.4 by Odin3 v3.09 (always 09) after, the Note 3 reboot whit the Rom working now?
If Yes install the Shell terminal emulator from Play Store, start it and type getprop. You see a big listing. See a line [ro.bootloader]: [N9005xxxxxx] where xxx.. is the bootloader installed. Send me this line.
PS. The UK BTU you tried is XXUBMJ3?
Good luck

ValenteL said:
(Flashed MJ1 over MI7 before...)
Hi @all
Because I'm a retired man I need my Note 3 for my personal use only. Not for Enterprise or Government working, then I don't need the hateful KNOX.
After customer recovery install and root access, the first thing I make is delete all apk and more from it.
1 - From system/app I delete:
ContainerAgent.apk + odex
ContainerEventsRelayManager.apk + odex
FusedLocation.apk + odex
KLMSAgent.apk + odex
KNOXAgent.apk + odex
KNOXAttestationAgent.apk + odex
KNOXStore.apk + odex
KNOXStub.apk
SPDClient.apk + odex
From system/containers I delete:
All .apk + .zip file and 2 apk inside subfolder framework
2 - Before flash by Odin3 v3.09 I make my Rom BMJ1 reduced, only whit: (Now BMJ3)
boot.img
cache.img.ext4
hidden.img.ext4
modem.bin
NON-HLOS.bin
recovery.img
system.img.ext4 ---> ONLY
No KNOX bootloader, no tz.mbn (this is TIMA from Knox)
I make this with the Tool Tar.md5.Packager from A.S._id DEV. Thanks A.S._id, this is a good tool. Thanks bohdans also.
At end I have a Rom-BMJ1.tar.md5 only whit that 7 modules. (Now BMJ3)
Flashed twice for a double test over data, worked well whithout issues.
3 - Now if I type getprop on Shell Terminal Emulator I have:
[ro.bootloader]: [N9005XXUBMI7] --> This is the original bootloader not changed.
But and:
[ro.build.PDA]: [N9005XXUBMJ1] --> and more MJ1 the new. (Now MJ3)
[ril.product_code]: [SM-N9005ZKETPH] --> Replaced the original csc by TPH from my Country by default.
If I help somebody whit I'm happy
If someone have some different opinions, please post here.
Thanks
Click to expand...
Click to collapse
Hello! could you help me? I have on board the [ROM]> <N9005 XXUBMJ1 JB 4.3> <Pre-Rooted STOCK ROM's - and therefore already with root. I would like to flash the BMJ3 and always get back the root without modifying the binary counters. What to do?

ValenteL said:
Hi
Unfortunately I can't help You. Your Note 3 is 16 GB and mine is 32 GB. We can't compare the Note 2 whit Note 3, see my post before whit attachments. On first we have at left the Note 2 at right the Note 3 whit all controlled by KNOX Bootloader.
But I try.
If you flash the customer Recovery 6.0.4.4 by Odin3 v3.09 (always 09) after, the Note 3 reboot whit the Rom working now?
If Yes install the Shell terminal emulator from Play Store, start it and type getprop. You see a big listing. See a line [ro.bootloader]: [N9005xxxxxx] where xxx.. is the bootloader installed. Send me this line.
Good luck
Click to expand...
Click to collapse
Dear ValenteL, all i can get in now is download mode (when i turn on my phone, it goes to a screen with pix of phone and computer connected, ask me to do recovery through kies _ that didnt work either). I will try to flash custom recovery see what happen then.

blackj30 said:
Dear ValenteL, all i can get in now is download mode (when i turn on my phone, it goes to a screen with pix of phone and computer connected, ask me to do recovery through kies _ that didnt work either). I will try to flash custom recovery see what happen then.
Click to expand...
Click to collapse
It's arrived to me when I have MJ3 and I tried flash a MJ1. Not possible now to return to a older bootloader.
But I included after a PS: The rom You tried from UK BTU is a XXUBMJ3?

ValenteL said:
It's arrived to me when I have MJ3 and I tried flash a MJ1. Not possible now to return to a older bootloader.
But I included after a PS: The rom You tried from UK BTU is a XXUBMJ3?
Click to expand...
Click to collapse
Hi ValenteL, the BTU rom was PDA N9005XXUBMJ3, CSC N9005OXABMJ3, modem N9005XXUBMJ2. And my old TGY rom was PDA N9005ZHUBMI7, CSC N9005ZZHBMI7, and modem N9005XXUBMI5 (different region). From my old rom, i flashed the newer BTU, now i want to go back to my old rom and got Bootloader error. So i thought i could use your method to go back from MJ3 to MI7.
Cheers

blackj30 said:
Hi ValenteL, the BTU rom was PDA N9005XXUBMJ3, CSC N9005OXABMJ3, modem N9005XXUBMJ2. And my old TGY rom was PDA N9005ZHUBMI7, CSC N9005ZZHBMI7, and modem N9005XXUBMI5. From my old rom, i flashed the newer BTU, now i want to go back to my old rom and got Bootloader error. So i thought i could use your method to go back from MJ3 to MI7.
Cheers
Click to expand...
Click to collapse
Now if You flashed the XXUBMJ3 You have the XXUBMJ3 bootloader. The aboot.mbn (bootloader) is the first module to be installed to control bootloaders.
You can't install an older booloader like MI7 from HK now. You have always this "SW REV check fail [aboot] fused 2 > binary 1".
And when You had a error on image.ext4 I think is region not compatible. You had a ZH and You tried a XX. I think that Chainfire have something to solve this, You must search where.
If You have HERE the Rom HK TGY N9005ZHUBMI7. Try this whit this Rom:
Make a Rom BMI7 reduced, only whit:
boot.img
cache.img.ext4
hidden.img.ext4
modem.bin
NON-HLOS.bin
recovery.img
system.img.ext4 ---> ONLY
No KNOX bootloader, no tz.mbn (this is TIMA from Knox)
Make this with the Tool Tar.md5.Packager from A.S._id DEV. Thanks A.S._id, this is a good tool. Thanks bohdans also.
( \in is the root of packager. )

.....!!!!

ValenteL said:
Now if You flashed the XXUBMJ3 You have the XXUBMJ3 bootloader. The aboot.mbn (bootloader) is the first module to be installed to control bootloaders.
You can't install an older booloader like MI7 from HK now. You have always this "SW REV check fail [aboot] fused 2 > binary 1".
And when You had a error on image.ext4 I think is region not compatible. You had a ZH and You tried a XX. I think that Chainfire have something to solve this, You must search where.
If You have HERE the Rom HK TGY N9005ZHUBMI7. Try this whit this Rom:
Make a Rom BMI7 reduced, only whit:
boot.img
cache.img.ext4
hidden.img.ext4
modem.bin
NON-HLOS.bin
recovery.img
system.img.ext4 ---> ONLY
No KNOX bootloader, no tz.mbn (this is TIMA from Knox)
Make this with the Tool Tar.md5.Packager from A.S._id DEV. Thanks A.S._id, this is a good tool. Thanks bohdans also.
( \in is the root of packager. )
Click to expand...
Click to collapse
Ok. Thanks. Let me try. Hopefully it will not kill my phones power

blackj30 said:
Ok. Thanks. Let me try. Hopefully it will not kill my phones power
Click to expand...
Click to collapse
To MI7 Firmwares Chainfire have THIS to "RegionLock Away [ROOT]"

ValenteL said:
Now if You flashed the XXUBMJ3 You have the XXUBMJ3 bootloader. The aboot.mbn (bootloader) is the first module to be installed to control bootloaders.
You can't install an older booloader like MI7 from HK now. You have always this "SW REV check fail [aboot] fused 2 > binary 1".
...............................
Make a Rom BMI7 reduced, only whit:
boot.img
cache.img.ext4
hidden.img.ext4
modem.bin
NON-HLOS.bin
recovery.img
system.img.ext4 ---> ONLY
No KNOX bootloader, no tz.mbn (this is TIMA from Knox)
Click to expand...
Click to collapse
Not work the reduced Rom. The new MJ3 bootloader controls all:
I have a MJ1 reduced, 7 files only. Tried flash it, I had error Cache and stop whit a message on phone about the error. Cache.img.ext4 MJ1 over MJ3, not compatible.
Flashed the custom recovery and reboot on Rom MJ3 I have working.

ValenteL said:
Not work the reduced Rom. The new MJ3 bootloader controls all:
I have a MJ1 reduced, 7 files only. Tried flash it, I had error Cache and stop whit a message on phone about the error. Cache.img.ext4 MJ1 over MJ3, not compatible.
Flashed the custom recovery and reboot on Rom MJ3 I have working.
Click to expand...
Click to collapse
You mean it will not work for my case?

blackj30 said:
You mean it will not work for my case?
Click to expand...
Click to collapse
Unfortunately I think not. Tried just to see if is good for You.
But from XXUBMJ3 the bootloader controls all about Rom MJ3.
BTW, You flashed the custom recovery and reboot? Not worked?

ValenteL said:
Unfortunately I think not. Tried just to see if is good for You.
But from XXUBMJ3 the bootloader controls all about Rom MJ3.
BTW, You flashed the custom recovery and reboot? Not worked?
Click to expand...
Click to collapse
Dear ValenteL, I got it work mate. With a gent jeezy85. We simply deleted the aboot.mbn in the stock rom Wonderful. Thank you for your help a lot. Very happy when i thought i have to buy a new phone

[Q] Vodafone UK - anyone updated their software today?

I've got BMI6 (baseband) BMI7 (build) and I've been offered an update OTA today which I've postoned
Has anyone updated their Vodafone UK branded N3 in the last couple of days, what version does it go to?
I'm guessing the update will make it more difficult to root? I haven't rooted yet but I'm not sure how much longer I can resist the temptation!

You can root anytime mate. I'm on MJ7 currently. .. It's the bootloader that gets updated meaning you can't go back to old firmware. The bootloader gets locked from MJ3 onwards. You can root your phone without triggering knox...I wasn't bothered about it so I used the normal way ?
Sent from my SM-N9005 using Tapatalk

DO NOT TAKE OTA IF YOU WANT TO ROOT! It contains the new bootloader...
How to update to latest firmware without bootloader, but camera and wifi working:
Step 1)
Download URDLV (script, sd card files, odin v3.09) from its thread http://forum.xda-developers.com/showthread.php?t=2498850
Download your latest firmware from www.sammobile.com/firmwares
-> to do so type *#1234# in the dialer and put your csc minus the last 4 signs into the sammobile search box (sould look like n9005dbt) and download the topmost file
Put urdlv.bat and all its components in c:/urdlv
Win+r
Cmd.exe
Press Enter
Cd c:/urdlv
Urdlv full
Drag your firmware in the console window
press Enter
Wait until its done
Your files are in the output folder
Untar them with e.g. 7zip
Step 2)
Prepare:
NON-HLOS.bin <- extracted from original firmware
boot.img <- extracted from original firmware
cache.img.ext4 <- created by Universal RDLV
hidden.img.ext4 <- extracted from original firmware
modem.bin <- extracted from original firmware
recovery.img <- extracted from original firmware
system.img.ext4 <- created by Universal RDLV
then follow these steps:
install cygwin64 (with all default)
start it once
go to c:/cygwin/home/<username_u_have>
put mentioned files there
in cygwin:
tar -H ustar -c NON-HLOS.bin boot.img cache.img.ext4 hidden.img.ext4 modem.bin recovery.img system.img.ext4 > DMJ7.tar
md5sum -t DMJ7.tar >> DMJ7.tar
mv DMJ7.tar DMJ7.tar.md5
Step 3)
flash generated file with odin v3.09
step 4)
put the rootdelavega.sh and root_files on your internal storage
reboot
remove the files
reboot
RESULT: KNOX 0x0, binary official, latest firmware, root
leave a 'thanks' if i helped
SM-N9005 URDLV 0x0
XDA Developers 4 premium app

fz9999 said:
I've got BMI6 (baseband) BMI7 (build) and I've been offered an update OTA today which I've postoned
Has anyone updated their Vodafone UK branded N3 in the last couple of days, what version does it go to?
I'm guessing the update will make it more difficult to root? I haven't rooted yet but I'm not sure how much longer I can resist the temptation!
Click to expand...
Click to collapse
I'm on Vodafone UK. I rooted using URDLV method while on MI7 and won't update via OTA. If you're not already rooted, updating to MJ7 via OTA will mean you will flash a locked bootloader. This means you will trip your Knox warranty flag if you try to root after OTA.
This update looks like it's the MJ6 release according to what's available on sammobile.com
PDA: N9005XXUDMJ6
CSC: N9005VFGDMJ1
MODEM: N9005XXUDMJ4
If you're already rooted, the easiest method to update would be to use mobile odin pro 3.85. I.e. download the update zip file from sammobile.com, extract zip to tar.md5 and copy it to your phone storage. Then flash using mobile odin pro. This won't flash your bootloader but will update your phone software.
Sent from my SM-N9005 using Tapatalk

dsm52 said:
I'm on Vodafone UK. I rooted using URDLV method while on MI7 and won't update via OTA. If you're not already rooted, updating to MJ7 via OTA will mean you will flash a locked bootloader. This means you will trip your Knox warranty flag if you try to root after OTA.
This update looks like it's the MJ6 release according to what's available on sammobile.com
PDA: N9005XXUDMJ6
CSC: N9005VFGDMJ1
MODEM: N9005XXUDMJ4
If you're already rooted, the easiest method to update would be to use mobile odin pro 3.85. I.e. download the update zip file from sammobile.com, extract zip to tar.md5 and copy it to your phone storage. Then flash using mobile odin pro. This won't flash your bootloader but will update your phone software.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Have to admit thats far easier thsn mine
And working
Thumbs up!
hit 'thanks' if i helped you
SM-N9005 DMJ7 0x0
XDA Developers 4 premium app

@Killberty
Hi,
I finally took the pludge after a good week of research and tried your method, I was on URDLV MI7 and wanted to upgrade to MK2.
I followed your instructions but it appeared that I encountered a boot loop (3/4 times) so had to power off the phone and then Odin back the stock MI7 to recover the device. Yes I tripped. Phone was also very laggy, the camera didn't work and I got errors such as Process system isn´t responding (wait/ok). WIFI was ok. No SIM was present so I didn't check network connection.
After URDLV'ing MI7 again, I then used Mobile Odin pro to get to MK2 with no problems and the phone was back to its normal performance.
@GalaxHe also described a similar method in the Universal Root de la Vega v0.5 [ Root without tripping KNOX or Malware! ] thread (direct post link) but his method includes the additional files:
rpm.mbn sbl1.mbn sdi.mbn tz.mbn
I would like to ask please;
how long did your device take to install/reboot when you upgraded to the latest bootloader?
how many times did your device reboot?
why did you not include the same files that @GalaxHe did?
Many thanks
& thanks to @Chainfire for Mobile Odin as I was not confident in trying your method a 2nd time in an attempt to recover.
All good.

xitobor said:
@Killberty
Hi,
I finally took the pludge after a good week of research and tried your method, I was on URDLV MI7 and wanted to upgrade to MK2.
I followed your instructions but it appeared that I encountered a boot loop (3/4 times) so had to power off the phone and then Odin back the stock MI7 to recover the device. Yes I tripped. Phone was also very laggy, the camera didn't work and I got errors such as Process system isn´t responding (wait/ok). WIFI was ok. No SIM was present so I didn't check network connection.
After URDLV'ing MI7 again, I then used Mobile Odin pro to get to MK2 with no problems and the phone was back to its normal performance.
@GalaxHe also described a similar method in the Universal Root de la Vega v0.5 [ Root without tripping KNOX or Malware! ] thread (direct post link) but his method includes the additional files:
rpm.mbn sbl1.mbn sdi.mbn tz.mbn
I would like to ask please;
how long did your device take to install/reboot when you upgraded to the latest bootloader?
how many times did your device reboot?
why did you not include the same files that @GalaxHe did?
Many thanks
& thanks to @Chainfire for Mobile Odin as I was not confident in trying your method a 2nd time in an attempt to recover.
All good.
Click to expand...
Click to collapse
1) i did never upgard my bootloader thats why i didnt trip
2) once then i rebooted twice for the URDLV sd card part
3) sbl= secondary bootloader bl1 = bootloader1 so i dont inculde em, no bootloader updates
u might have skipped some step but i myself any many others can confirm it works...

Killberty said:
1) i did never upgard my bootloader thats why i didnt trip
2) once then i rebooted twice for the URDLV sd card part
3) sbl= secondary bootloader bl1 = bootloader1 so i dont inculde em, no bootloader updates
u might have skipped some step but i myself any many others can confirm it works...
Click to expand...
Click to collapse
Thank you for your reply.
Doh, @1) I didn't mean bootloader, I meant to say firmware.
I didn't upgrade my bootloader either and I didn't skip any steps. As I said, its all good, my phone is ok but who knows what happened in my case. Just had a few questions to see if I could understand it more.
Cheers.

xitobor said:
Thank you for your reply.
Doh, @1) I didn't mean bootloader, I meant to say firmware.
I didn't upgrade my bootloader either and I didn't skip any steps. As I said, its all good, my phone is ok but who knows what happened in my case. Just had a few questions to see if I could understand it more.
Cheers.
Click to expand...
Click to collapse
Hahah np and sorry for your knox :/
Maybe you had kies open or a lil bug in the cable or whatever (noone knows what samsung software does....) well i dont understand it at all as is worked for at leasr 5 people...
hit 'thanks' if i helped you
SM-N9005 0x0 X-Note7 ML2
XDA Developers 4 premium app

[HowTo] SM-G900FD with Android 5.0 Root if all seems to fail

[ Read the How To at the second post ]
Heya guys,
I just got yesterday my new Galaxy S5. I'm actually someone who is switching from the iPhone world to Galaxy.
I had a Note 2 in the past for some time and I'm sys admin so I'm a bit familiar with flashing and technical stuff.
Phone Information:
Model: SM-G900FD (or SM-G900MD?) (DuoS)
Country of Origin: United Arab Emirates
The phone came with stock rom 4.4.2. On the About Phone screen it shown SM-G900FD as model, directly from unboxing.
But when entering the Odin Mode it shows as product name SM-G900MD (which would fit the origin of course).
The first I did was downloading G900FDXXU1BNL9 (Android 5.0 SER (Russia)) and flash it with Odin. It works like a charm.
Then I tried dozen of different rooting methods, and failed every time, I spent I believe 10 hours on it already and flashed the phone about 30 times.
When flashing the stock rom, either the new G900FDXXU1BNL9 (5.0) or old G900FDXXU1ANF6 (4.4.2) it works like a charm.
The phone comes to life, Android is working fine.
As soon as I try to flash *any* other image, CWM, CF-Auto-Root or anything, it starts with "NAND Write Start!" and then in some seconds stops with "Complete(Write) operation failed." and the system ends up in a soft brick (Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.). I tried from every piece of software I could find many different versions. Different Odin versions. I tried Heimdall (Mac) and fastboot (Windows & Mac) without success. These two don't work at all with the phone. Heimdall can't correctly connect to the phone and download the PIT, I was reading its a bug with the newest bootloader of Samsung. And fastboot/adb can't see the phone, at all. While heimdall or odin can see the phone, so its not a driver issue that the OS can't recognize the phone.
I tried also different versions of CWM, CF-Auto-Root, either for SM-G900FD or SM-G900MD. No luck.
What I tried then was using towelroot, but it doesn't work with the newest Android. So I found a thread that stated to flash a old Kernel, which will give errors during booting but you can then root the phone with towelroot, and then flash the newest kernel back to the phone. I tried that, taking out the boot.img files from old and new firmware out and use a script to package them into .tar.md5 files and try to flash them with Odin. Even there, Odin reports FAIL! With the boot.img files from the stock images, which work fine flashing if I flash the entire stock image.
I tried also installing a old stock rom and try rooting it there with CWM/CF-Auto-Root. Same stuff, FAIL! flashing.
I'm a bit out of ideas right now. Does anyone ever encountered this? Or does have a hint on what could cause this problems?
Some threads I was reading (its a way more, but the list would be too long, I just add the most recent ones) and following:
[How to] Root for 4.4.2 and Flash rooted Stock Android 5.0 with KNOX 0x0?
http://forum.xda-developers.com/showpost.php?p=54745709&postcount=13
Galaxy S5 G900FD
http://forum.xda-developers.com/showpost.php?p=55994495&postcount=102
[Script][Tool] how to create a tar.md5 file from img For Odin
http://forum.xda-developers.com/showthread.php?t=2446269
Click to expand...
Click to collapse
Thank you very much for any assistance. I hope there is a possibility to root this phone
Cheers,
Sven
PS: My KNOX Warranty Void is already increased, so the warranty is killed already.

[HowTo]
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
$ COPYFILE_DISABLE=1 gtar -H ustar -c NON-HLOS.bin aboot.mbn boot.img cache.img.ext4 hidden.img.ext4 modem.bin recovery.img rpm.mbn sbl1.mbn sdi.mbn system.img.ext4 tz.mbn > image.tar
$ gmd5sum -t image.tar >> image.tar
$ mv image.tar image.tar.md5
Click to expand...
Click to collapse
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven

Well done!!
af2k said:
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven
Click to expand...
Click to collapse
Well done !!
i was looking for this root for my phone M-G900FD
until i read your thread ,so please upload the ready made file to root my phone as i am not experienced in this matter
waiting for your feed back
thanks

I had the same problem. I couldn't flash any other image whatever I did. And what I did was disabling reactivation lock within the settings. Worked since then.

free007 said:
please upload the ready made file
Click to expand...
Click to collapse
I will look into this tomorrow and provide a ready image for this.
AlwaysAndroid said:
what I did was disabling reactivation lock within the settings. Worked since then.
Click to expand...
Click to collapse
It didn't work out of the box at me. I checked right now within the settings and the reactivation lock is disabled already.
So we seem to face different problems. I still don't understand why flashing anything but an entire firmware is failing.

Well done indeed, would love to get my hands on your modded ROM, as in Dubai with new Duos just purchased today.
Any problems with Wifi passwords not being stored on re-boot?

af2k said:
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven
Click to expand...
Click to collapse
Looks like gtar needs to be installed separately.
$ brew install gnu-tar

This is what I was looking for...
I am not on OSX. Is there a possibility to get access to the modified image?

[Q] Att i337 firmware odin fail

I have read read read cant find a specific solution ..Ok im on KOT49H I337ucufmld. I was on 4.3 before I have flashed with odin many times at first I got a fail at the start aboot.mbn nand fail ..so I removed that file and it started to install but failed at the end... my knox is set to 01 . my boot loader of course was locked down when I tried to flash another recovery.. so I read and people suggested pit files along with tar so I did that. no firmware Samsung official or otherwise will try to install at all with the aboot.mbn intact within the tar . ive flashed and flashed ..everything... so then I got a 32 gb pit file and did a nand erase in odin...and I noticed that by doing that I have my stock recovery back . I then re flashed the proper 16gb pit file and it remained working..so now I have download mode and stock recovery both working but have NO SYSTEM at all installed and cant seem to install one....I need good solid advise..is it a paper weight or is ther a way to zip or tar back either by odin or stock recovery.. help please.

walkerlaney said:
I have read read read cant find a specific solution ..Ok im on KOT49H I337ucufmld. I was on 4.3 before I have flashed with odin many times at first I got a fail at the start aboot.mbn nand fail ..so I removed that file and it started to install but failed at the end... my knox is set to 01 . my boot loader of course was locked down when I tried to flash another recovery.. so I read and people suggested pit files along with tar so I did that. no firmware Samsung official or otherwise will try to install at all with the aboot.mbn intact within the tar . ive flashed and flashed ..everything... so then I got a 32 gb pit file and did a nand erase in odin...and I noticed that by doing that I have my stock recovery back . I then re flashed the proper 16gb pit file and it remained working..so now I have download mode and stock recovery both working but have NO SYSTEM at all installed and cant seem to install one....I need good solid advise..is it a paper weight or is ther a way to zip or tar back either by odin or stock recovery.. help please.
Click to expand...
Click to collapse
Are you sure you're on the mdl bootloader? What do you mean when you say you're on 4.3? That's not consistent with mdl bootloader. My guess is you're not on the mdl bootloader and that flashing the mdl tar in Odin won't work for you. In a terminal emulator on your phone type
su
getprop ro.bootloader
They'll tell you what bootloader you're on.
If you're not on the mdl bootloader flash the nb1 tar in Odin.
Sent from my Nexus 5 using XDA Free mobile app

correct information
I was on 4.3 before I updated I have flashed several tar files ..I don't have any system working on phone I can't do what you have recommended. But
The Information I gave came from the top of the the screen in recovery mode.

What version are you trying to flash through Odin?

Downgrade to previous version & SW REV. Check Fail

Samsung Bootloader does not allow to downgrade the ROM, Therefore I found a way to Downgrade Specially from Nougat to Marshmallow and Solution to SW REV. Check Fail.
Required:
1. Marshmallow or which you need Odin Firmware (Can be downloaded from Sammobile) for your Mobile.
2. 7zip installed.
3. WinRar installed (if 7Zip Shows error while Extracting the .tar file of firmware). I recommend this for extracting the tar file.
Steps:
1. Rename the Firmware from .tar.md5 to .tar so that WinRar can open it.
2. Extract the Firmware files except sboot.bin, cm.bin and modem.bin .
3. Now compress the extracted files to tar archive using 7Zip.
4. Done, Firmware is ready to flash through Odin.
cm.bin and sboot.bin causes to SW Rev check fail so If you face this error remove them from firmware.
If you like please hit Thanks button.

Hello, So basically we need to remove all .bin files? ok
I also need to downgrade my modem.bin because I'm facing Wi-Fi and Bluetooth issues (they don't turn on). So is it possible to flash those files separately after? Will it work?

x.shayan.x said:
Hello, So basically we need to remove all .bin files? ok
I also need to downgrade my modem.bin because I'm facing Wi-Fi and Bluetooth issues (they don't turn on). So is it possible to flash those files separately after? Will it work?
Click to expand...
Click to collapse
Yes you can flash

Afzal922 said:
Yes you can flash
Click to expand...
Click to collapse
I removed the files you mentioned and I flashed marshmallow on Nougat successfully but i have constantly getting error message ""Unfortunately, Touchwiz has stopped"" and "Unfortunately, The process. Android.process has stopped" and I can't boot in my mobile. Please help..!

alipezu said:
I removed the files you mentioned and I flashed marshmallow on Nougat successfully but i have constantly getting error message ""Unfortunately, Touchwiz has stopped"" and "Unfortunately, The process. Android.process has stopped" and I can't boot in my mobile. Please help..!
Click to expand...
Click to collapse
Try another firmware.

Afzal922 said:
Samsung Bootloader does not allow to downgrade the ROM, Therefore I found a way to Downgrade Specially from Nougat to Marshmallow and Solution to SW REV. Check Fail.
Required:
1. Marshmallow or which you need Odin Firmware (Can be downloaded from Sammobile) for your Mobile.
2. 7zip installed.
3. WinRar installed (if 7Zip Shows error while Extracting the .tar file of firmware). I recommend this for extracting the tar file.
Steps:
1. Rename the Firmware from .tar.md5 to .tar so that WinRar can open it.
2. Extract the Firmware files except sboot.bin, cm.bin and modem.bin .
3. Now compress the extracted files to tar archive using 7Zip.
4. Done, Firmware is ready to flash through Odin.
cm.bin and sboot.bin causes to SW Rev check fail so If you face this error remove them from firmware.
If you like please hit Thanks button.
Click to expand...
Click to collapse
mind telling us how to flash the .bin files to get back signals and wifi and other stuff?

if we not going to flash the CM and modem, i dont think the Wifi and the mobile signal is going to work....
Regards

i try this wat downgrade samsung 51 and its not work

Afzal922 said:
Samsung Bootloader does not allow to downgrade the ROM, Therefore I found a way to Downgrade Specially from Nougat to Marshmallow and Solution to SW REV. Check Fail.
Required:
1. Marshmallow or which you need Odin Firmware (Can be downloaded from Sammobile) for your Mobile.
2. 7zip installed.
3. WinRar installed (if 7Zip Shows error while Extracting the .tar file of firmware). I recommend this for extracting the tar file.
Steps:
1. Rename the Firmware from .tar.md5 to .tar so that WinRar can open it.
2. Extract the Firmware files except sboot.bin, cm.bin and modem.bin .
3. Now compress the extracted files to tar archive using 7Zip.
4. Done, Firmware is ready to flash through Odin.
cm.bin and sboot.bin causes to SW Rev check fail so If you face this error remove them from firmware.
If you like please hit Thanks button.
Click to expand...
Click to collapse
Hello, this is a well old post. Would this work with the Note 20 Ultra Snapdragon version?

N1NJATH3ORY said:
Hello, this is a well old post. Would this work with the Note 20 Ultra Snapdragon version?
Click to expand...
Click to collapse
Yes