Database Users

[Tut] Unroot the Galaxy SIII (for stock updates/warranty)

Hi All,
I put together a tutorial on how to unroot the galaxy s3 and get it back to stock (for warranty or to get stock updates)
Things you will need...
1. PC Odin
(Check Attachment)
2. Your Firmware
Sammobile.com
Video Instructions
Written Instructions
1. Backup what you need to
2. Install ADB Drivers (Samsung Kies)
3. Put your phone in download mode - Hold Vol Dn + Power + Home for 10 seconds then press Vol Up to continue
4. Check if Custom Binary Download is NO, if Yes then proceed to step 6 if it says 1 count or something like that then go to step 5
5. Follow the thread below to reset the binary counter (or check my video tutorial to do so...) once reset get back to download mode
http://forum.xda-developers.com/showthread.php?t=1494114
(Thanks to Chainfire)
6. Go to SamMobile.com and download the latest firmware for GT-I9300 (Galaxy S3)
http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-I9300&r=-1#modelsa
7. The downloaded firmware would be a zip file right click and extract it to get a .tar.md5 file
8. Connect the phone to the pc via usb cable
9. Run Extract the zip file that you downloaded from the attachment below and run Odin3 1.85. exe
10. Make sure that only Auto Reboot and F.Reset Time are checked and click on PDA, select the .tar.md5 file that we just extracted
11. Now hit Start
12. Once the phone is up go to Settings -> About Device -> Status, check if the device status says NORMAL... if it does, then the device is unrooted if it still says MODIFIED continue...
13. Reboot into Android Recovery by holding Vol UP + Home + Power till you see Samsung Galaxy S3 displayed on screen...
14. Do a factory wipe and wipe cache then reboot
15. Check Download mode again, if 0 or NO you are done and the S3 can be sent in for warranty if it still shows 1 go to step 16.
16. If the counter stays at 1 it means u were on a non stock kernel... what u need to do now is root (since u have just unrooted you are now on a stock kernel) use triangle away and then flash the stock rom again.... the counter will then be 0 but status might show modified, in that case do a factory wipe and youd be back to a totally stock s3
Hope this guide helps someone
Ash aka Cursed4Eva

Is there a way to keep all my files on the phone?
Specifically when I get my SGS3, I want to keep/transfer my data files of my games from my old X10, you think it'll be possible?

OK, just to make sure I understand everything:
- Step 2 means "Install Kies"
- I will be able to update from Kies and whatnot after the "unroot" is over.
- Any SD card files will still be accessible, as long as they're official (say, an app loaded onto the SD card).
Thanks for your help in advance.

My system shows NORMAL yet Titanium backup still works just fine????????

custom rom
Does this work if i come from a custom rom galaxy s3? or i should first restore phone to rooted stock rom then follow the steps?

zaid10 said:
Does this work if i come from a custom rom galaxy s3? or i should first restore phone to rooted stock rom then follow the steps?
Click to expand...
Click to collapse
This will work no matter what's on your phone.
It's so easy.
1. Download your firmware and extract it to your Odin folder so you have your .tar.md5 file, flash it to your phone while your phone is in download mode using Odin. Use it as the PDA in Odin. Wait 5-15 minutes. Go to recovery and wipe everything. Done.
I'm doing it now

Hey guys,
i have cm10 on my i9300 and i'd like to revert back to stock rom, unrooting is not needed, nor is triangle away needed. just want to try stock JB.
Problem is that i have Linux on my machines. I flashed my i9300 using cfroot and heimdall. can something similar be done with stock rom? i got the rom from sammobile.com.
Should i search for windows machine or?
Thanks in advance!
Edit: after untaring that .tar.md5 file i can see -rwxr--r-- root/root 1101420964 2012-08-21 10:44 system.img
-rwxr--r-- root/root 4964608 2012-08-21 10:44 boot.img
-rwxr--r-- root/root 52855268 2012-08-21 13:04 cache.img
-rwxr--r-- root/root 109941124 2012-08-21 13:04 hidden.img
-rwxr--r-- root/root 5652736 2012-08-21 10:44 recovery.img
-rwxr--r-- root/root 12583168 2012-08-27 08:43 modem.bin
should i try with heimdall -- cache cache.img --modem modem.bin --hidden hidden.img --recovery recovery.img
what to use for boot?
--primary-boot or?
anyone tried that?

wrong forum {deleted)

How do you check which country your handset is from? Thanks.

Yeah, I have a similar query. Which firmware would I need? Even after selecting my country and network I see a massive list of firmwares for the phone on SamMobile.

Take the latest one according to the date...all will work fine.....
Just in case if you will take the old one, you will need to do OTA Update or from kies to update the latest one

awesome tut..
thanks a lot, you saved me, very easy steps for unrooting SGS3 and resetting flash counters. Done it without any problems, but hard had to hard reset at the end. Thanks again, awesome work.:good:

After I unroot my S3 can they check my root record??
Sent from my GT-I9300 using xda app-developers app

Great work, thanks for the info, easy & clean. :good:

I need to use my warranty coz i can't connect my pc to charger/ pc, any way to roll back to stock stuff?
To know more read this lol: http://forum.xda-developers.com/showthread.php?t=1929215

I cant find my exact firmware guys i need help... the PDA and CSC limit it to singapore and malaysia. Its region is SFR(france). I live in pakistan and i am not receiving updates on my SGS3. While all others are. That led me to conclude that something was wrong. And this issue is more related to flashing stock firmware than unrooting but the latter is also a problem. I cant unroot as i cant find my exact firmware. If i need to claim my warranty i have to have my device status normal, no modifications,stock everything etc BUT the same product code with which i bought it and the same IMEI. Strange issue yes and im quite unlucky. Will those remain unchanged? region can be changed to france by an app but its the product code and IMEI im worried about. Any sugessions guys?

Can any one help me please im using 4.0.4 ics rooted but want to update to offical 4.1.1 jellybean?
Sent from my GT-I9300 using xda premium

I can't find the firmware for the United States. Can someone direct me to it?

how to unroot galaxy s3 I9300 on MAC. Kindly help.

What if our screen gets broken or a button stops working? What if the only thing we can do is handing the phone to service?

[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

[HELP] updatet to dmj7 dbt - no camera, no wifi, binary custom

Hi guys,
Did urdlv dmj7
Falshed it
Falshed modem bin
Flashed non hlos bin
Did sd card part
-> root access
-> Knox 0x0
But:
-> binary custom
-> no wifi
-> camera force close
Any help is appreciated
Sent from my SM-N9005 using XDA Premium 4 mobile app

Tried to flash modem and no hlos again, did not change a thing... pls help
Sent from my SM-N9005 using XDA Premium 4 mobile app

Be sure m8 that modem is really changed and is written.
Sent from my SM-N9005 using Tapatalk

BlueChris said:
Be sure m8 that modem is really changed and is written.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Modem xxudmj7 ...
What to do?
Sent from my SM-N9005 using XDA Premium 4 mobile app

I have same problem
I done URDLV DMJ7 witch success
flashed it
rooted
flashed modem bin
flashed non hlos bin
Did full wipe
I have root access , Knox 0x0 ,but CAMERA FC ,No WIFI . And Kernel is old one from 11 september.I think the no wifi and camera is because my kernel is old.Schould be kernel dated to 30 oct .
Any ideas ?

staffik said:
I have same problem
I done URDLV DMJ7 witch success
flashed it
rooted
flashed modem bin
flashed non hlos bin
Did full wipe
I have root access , Knox 0x0 ,but CAMERA FC ,No WIFI . And Kernel is old one from 11 september.I think the no wifi and camera is because my kernel is old.Schould be kernel dated to 30 oct .
Any ideas ?
Click to expand...
Click to collapse
yes i have fixed it myself
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
HOW TO:
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
-> flash generated file
PROFIT
hope that helps it does for actually
but i have bigger battery consumption
EDIT: KNOX 0x0 binary official

Killberty said:
yes i have fixed it myself
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
HOW TO:
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
-> flash generated file
PROFIT
hope that helps it does for actually
but i have bigger battery consumption
EDIT: KNOX 0x0 binary official
Click to expand...
Click to collapse
Thanks! Works like a charm!
:good:
Sent from my SM-N9005 using Tapatalk

Same issue. RDLV creates a file that is 10,0 KB big. Weird... Any help.
MODE: full
FILE TYPE: tar
FILENAME: N9005XXUDMJ7_N9005OXADMJ4_N9005XXUDMJ7_HOME.tar
Extracting Tar...
Hex Editing System Image...
Checking System Image Hook...
System Image Successfully Hooked
Creating Odin Flashable Tar...
/usr/bin/tar: value 4294967295 out of uid_t range 0..2097151
/usr/bin/tar: value 4294967295 out of uid_t range 0..2097151
/usr/bin/tar: Exiting with failure status due to previous errors
ODIN FILE: N9005XXUDMJ7_N9005OXADMJ4_N9005XXUDMJ7_HOME_VEGA.tar
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
D:\Universal-RDLV>

Flowbax said:
Same issue. RDLV creates a file that is 10,0 KB big. Weird... Any help.
MODE: full
FILE TYPE: tar
FILENAME: N9005XXUDMJ7_N9005OXADMJ4_N9005XXUDMJ7_HOME.tar
Extracting Tar...
Hex Editing System Image...
Checking System Image Hook...
System Image Successfully Hooked
Creating Odin Flashable Tar...
/usr/bin/tar: value 4294967295 out of uid_t range 0..2097151
/usr/bin/tar: value 4294967295 out of uid_t range 0..2097151
/usr/bin/tar: Exiting with failure status due to previous errors
ODIN FILE: N9005XXUDMJ7_N9005OXADMJ4_N9005XXUDMJ7_HOME_VEGA.tar
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT DE LA VEGA
D:\Universal-RDLV>
Click to expand...
Click to collapse
Sure i can help u
Use cygwin to call the script
- Install Cygwin64
- Start the Cygwin terminal
- cd to proper drive and URDLV folder OR put the URDLV.bat in c/cygwin/home/
- chmod +x URDLV.bat
- ./URDLV.bat full c:/URDLV/.tar.md5 (drag-n-drop the path to the file)
Leave a 'Thanks' if i helped you
SM-N9005 MJ7 Knox 0x0
XDA Premium 4 mobile app

Thanks Killberty that worked but it didn't solve my problem with WiFi and camera.

Flowbax said:
Thanks Killberty that worked but it didn't solve my problem with WiFi and camera.
Click to expand...
Click to collapse
Pls write excactly what firmware u r on, device, and what step you took
Leave a 'Thanks' if i helped you
SM-N9005 MJ7 Knox 0x0
XDA Premium 4 mobile app

SM-N9005 bought in Sweden. My latest firmware that worked just fine was SM-N9005XXUBMJ1-PRE-ROOTED-DEODEX-SUPER-SLIM-KNOX-FREE.tar
After upgrading to stock N9005XXUDMJ7_N9005OXADMJ4_BTU.zip
Firmware - N9005XXUDMJ7 - SM-N9005
Model: SM-N9005
Country: United Kingdom
Version: Android 4.3
Build date: 30 Oct 2013
Product Code: BTU
PDA: N9005XXUDMJ7
CSC: N9005OXADMJ4
MODEM: N9005XXUDMJ7
Changelist: 2019540
I started to get WiFi problems (camera worked). Now I managed to get the Wifi working by flashing Note 3 - leanKernel_hltetmo-v1.2 that I used before on MJ1 without any issues. So now my WiFi works just fine but the camera gives my FC. So my options is camera OR WiFi and I can't downgrade to any other firmware. Tried that and I don't get any boot sound on Samsung logo (weird) when homescreen shows up I get some System FC crap... WiFi and camera not working (after 15 sec) the phone reboots over and over again. I think that is because the bootloader was upgraded. I also tried my nandroid backup of MJ1, but I still get System FC something... Time to throw the phone away after spending 2 days trying to fix this I'm out of any good options. Maybe I find someone that has a CWM flashable file of working MJ7 LOL... Wiping everything and installing pure stock MJ7 should work but it does not for me.
Thanks for trying to help out mate. :highfive:

Flowbax said:
SM-N9005 bought in Sweden. My latest firmware that worked just fine was SM-N9005XXUBMJ1-PRE-ROOTED-DEODEX-SUPER-SLIM-KNOX-FREE.tar
After upgrading to stock N9005XXUDMJ7_N9005OXADMJ4_BTU.zip
Firmware - N9005XXUDMJ7 - SM-N9005
Model: SM-N9005
Country: United Kingdom
Version: Android 4.3
Build date: 30 Oct 2013
Product Code: BTU
PDA: N9005XXUDMJ7
CSC: N9005OXADMJ4
MODEM: N9005XXUDMJ7
Changelist: 2019540
I started to get WiFi problems (camera worked). Now I managed to get the Wifi working by flashing Note 3 - leanKernel_hltetmo-v1.2 that I used before on MJ1 without any issues. So now my WiFi works just fine but the camera gives my FC. So my options is camera OR WiFi and I can't downgrade to any other firmware. Tried that and I don't get any boot sound on Samsung logo (weird) when homescreen shows up I get some System FC crap... WiFi and camera not working (after 15 sec) the phone reboots over and over again. I think that is because the bootloader was upgraded. I also tried my nandroid backup of MJ1, but I still get System FC something... Time to throw the phone away after spending 2 days trying to fix this I'm out of any good options. Maybe I find someone that has a CWM flashable file of working MJ7 LOL... Wiping everything and installing pure stock MJ7 should work but it does not for me.
Thanks for trying to help out mate. :highfive:
Click to expand...
Click to collapse
Sorry but i have neither expeirence in custom roms nor in custom kernels nor custom recoveries with note 3
Flash stock mj7 with my guides and itll work, i cant help u as i am a complte android noob (10days)
I just have some computer knowledge and learn fast
My guide was just lucky logical combinig
Sorry i cant help u, just post a seperate thread.
Sent from my SM-N9005 using XDA Premium 4 mobile app

Thank You
Killberty said:
yes i have fixed it myself
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
HOW TO:
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
-> flash generated file
PROFIT
hope that helps it does for actually
but i have bigger battery consumption
EDIT: KNOX 0x0 binary official
Click to expand...
Click to collapse
OMG it's work YOUR ARE MY GOD TTTTHHHHAAAAANNNKKK YYYYYOOOOUUUUUU

re
raphou20 said:
OMG it's work YOUR ARE MY GOD TTTTHHHHAAAAANNNKKK YYYYYOOOOUUUUUU
Click to expand...
Click to collapse
i spok too fast my device is rooted yes but system status is custom and knox warranty void is 0x1

Since OP already have root...reflashing full stock MJ7 via MobileOdin should bring back your wifi and solved other problem. And you will still have your root intact.
Flashing via MobileOdin did not trigger Knox flag...provided your Knox still 0x0.

raphou20 said:
i spok too fast my device is rooted yes but system status is custom and knox warranty void is 0x1
Click to expand...
Click to collapse
System status can be faked by wanam exposed
And knox 0x1 isnt my fault, i am still on 0x0, so you maybe did something wrong
leave a 'thanks' if i helped
SM-N9005 URDLV 0x0
XDA Developers 4 premium app

waveweaver said:
Since OP already have root...reflashing full stock MJ7 via MobileOdin should bring back your wifi and solved other problem. And you will still have your root intact.
Flashing via MobileOdin did not trigger Knox flag...provided your Knox still 0x0.
Click to expand...
Click to collapse
Confirmed.
Its an easyier way not to flash the bootloader, but for unrooted devices that are on mj1 my tutorial is still the only possibility( until @designgears finally brings his updates)
leave a 'thanks' if i helped
SM-N9005 URDLV 0x0
XDA Developers 4 premium app

piats said:
Thanks! Works like a charm!
:good:
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Glad i could help, feel free to ask any questions
leave a 'thanks' if i helped
SM-N9005 URDLV 0x0
XDA Developers 4 premium app

Anyway one day the dev Will found how to reset Knox to 0x0.
Envoyé de mon SM-N9005 en utilisant Tapatalk now Free

[Q] Firmwareupdate after Root without triping KNOX or loosing root.

I successfully rooted my Note 3(N9005) with Universal Root de la Vega v0.5 ( wasn't alowed to post a thanks in that thread or leave my commend but donated and used thanks button ).
I got the Note 3 last Saturday, mission was to get root without trigger KNOX warenty bit in 14 days or send device back without comment. So far I succeed.
I keept my orginal Firmware Version before root, because I learnt from my Note 1(N7000) that putting the an actual firmware on the device and want to get root is a bad idea.
So now I want to put the actual firmware on device but don't trigger KNOX or loose root.
Mobile Odin is abad idea because it will trigger KNOX. I have also bad expirens with it on my Note 1. 2 times soft brick and once damaged chache partition, needed to use Odin(used v1.85) to get device back running. No succsessfull flash, so never used it again.
I now found what Mobile Odin should work with Knox 0x0: http://forum.xda-developers.com/showthread.php?t=2522729
I still not sure if Ishould use it.
Update over OTA or Kies will not work or update to newer bootloader and loose root.
My idea is to use latest Firmware and Odin( v3.07 version used for Root de la Vega) without flashing bootloader(I never done on my old).
With Odin I will loose root, so I need to root with Universal Root de la Vega method again?
Which partition are nessary AP,CP, CSC and UMS?
Of course not BL and EFS.
Ordered my Note 3 over Amazon. Strange is I got a dutch/netherland version.
I most likly want to have german version(downloaded N9005XXUDMK2_N9005DBTDMK2_DBT from SamMobile).
So far I know the diffrenz is in the cache so maybee I need to wipe cache.
So here also a question why can I flash cache and still have data on, which I need to wipe if I hasve problems?
Are this different partitions?
Could be the old bootloader makes problem with newer firmware?
Is were a save way to dowload actual firmware over Kies without starting the update(will install new bootloader).
Like disconnect device while downloading, can't try because my Note 1 has already actual Firmware and my Note 3 I don't want to risk.
On the Note 1 I could download firmware wit Kies but Update failed(I think because of root), but the I had the firmware and could use Odin.
On my old Note 1 I just flashed back to older firmware with Odin then something was wrong(warenty counter was already one).
I'm just not sure about this KNOX counter, should I use Odin with Universal Root de la Vega on actual Firmware or use Mobile Odin.
Or have you another save method to update with keep root.
Let me hear your comments.

Sony667 said:
I successfully rooted my Note 3(N9005) with Universal Root de la Vega v0.5 ( wasn't alowed to post a thanks in that thread or leave my commend but donated and used thanks button ).
I got the Note 3 last Saturday, mission was to get root without trigger KNOX warenty bit in 14 days or send device back without comment. So far I succeed.
I keept my orginal Firmware Version before root, because I learnt from my Note 1(N7000) that putting the an actual firmware on the device and want to get root is a bad idea.
So now I want to put the actual firmware on device but don't trigger KNOX or loose root.
Mobile Odin is abad idea because it will trigger KNOX. I have also bad expirens with it on my Note 1. 2 times soft brick and once damaged chache partition, needed to use Odin(used v1.85) to get device back running. No succsessfull flash, so never used it again.
I now found what Mobile Odin should work with Knox 0x0: http://forum.xda-developers.com/showthread.php?t=2522729
I still not sure if Ishould use it.
Update over OTA or Kies will not work or update to newer bootloader and loose root.
My idea is to use latest Firmware and Odin( v3.07 version used for Root de la Vega) without flashing bootloader(I never done on my old).
With Odin I will loose root, so I need to root with Universal Root de la Vega method again?
Which partition are nessary AP,CP, CSC and UMS?
Of course not BL and EFS.
Ordered my Note 3 over Amazon. Strange is I got a dutch/netherland version.
I most likly want to have german version(downloaded N9005XXUDMK2_N9005DBTDMK2_DBT from SamMobile).
So far I know the diffrenz is in the cache so maybee I need to wipe cache.
So here also a question why can I flash cache and still have data on, which I need to wipe if I hasve problems?
Are this different partitions?
Could be the old bootloader makes problem with newer firmware?
Is were a save way to dowload actual firmware over Kies without starting the update(will install new bootloader).
Like disconnect device while downloading, can't try because my Note 1 has already actual Firmware and my Note 3 I don't want to risk.
On the Note 1 I could download firmware wit Kies but Update failed(I think because of root), but the I had the firmware and could use Odin.
On my old Note 1 I just flashed back to older firmware with Odin then something was wrong(warenty counter was already one).
I'm just not sure about this KNOX counter, should I use Odin with Universal Root de la Vega on actual Firmware or use Mobile Odin.
Or have you another save method to update with keep root.
Let me hear your comments.
Click to expand...
Click to collapse
Ok, so download the DBT firmware you need to match your bootloader from Sammobile (*#1234# to check current firmware) -- You won't be able to go any higher firmware than your current without upgrading your bootloader without using Mobile ODIN as far as I know. However @Killberty may chime in here as he uses DBT also and may be able to help you better.

Sony667 said:
...
So now I want to put the actual firmware on device but don't trigger KNOX or loose root.
Mobile Odin is a bad idea because it will trigger KNOX.
...
Click to expand...
Click to collapse
Mobile Odin is a bad idea because you will lose root.
Mobile Odin PRO is a great idea - there is an entire thread about that and I have used it with zero problems. We don't know 100% certain that in future versions of firmware it will still work with knox 0x0 , but so far is OK.

So I more and more thing I will give Mobile Odin Pro a change.
Yes I have the Pro version already, but had the bad experience like I posted.
Sorry I forgot to post my current version, I thought I did.
AP: N9005XXUBMI7
CP: N9005XXUBMI6
CSC: N9005PHNBMI2
So I used N9005XXUBMI7_N9005PHNBMI2_PHN to make root(same version as original).
So you think it better to flash first to the N9005XXUBMI7 N9005DBTBMI1 to have german to have same bootloader.
And later go to actual N9005XXUDMK2 N9005DBTDMK2 using Mobil Odin Pro.
Or better first try N9005XXUDMJ7 N9005DBTDMJ4 which is confirmed to work with MOP.
I'm not sure about the change XXUB to XXUD but i think a change in the former digits I also have seen on my Note 1.
Maybe this is the bootloader.
About flash with Odin, I think you right, it Flash always the complete package, this is the reason I flashed on rooting firmware 2 times.
Because I had but the package on AP and CSC.
So the only way to flash without bootloader is to repackage like in Universal RDLV.

Sony667 said:
...
So you think it better to flash first to the N9005XXUBMI7 N9005DBTBMI1 to have german to have same bootloader.
And later go to actual N9005XXUDMK2 N9005DBTDMK2 using Mobil Odin Pro.
Or better first try N9005XXUDMJ7 N9005DBTDMJ4 which is confirmed to work with MOP.
...
Click to expand...
Click to collapse
I have MJ7 but do not know about MK2 - the URDLV + Mobile Odin Pro thread is probably the right place to ask.
http://forum.xda-developers.com/showthread.php?t=2522729

OK Thanks for the answer.
I'm currently reading the URDLV + Mobile Odin Pro thread, if after what it's not clear I will ask were.
Thanks.

If u dont wanna pay 5 bucks for the MOP, just quote me
10mins of work - save 5 bucks
EDIT: uhh mk2 is out ill use my method to flash it soon
EDIT2:
http://forum.xda-developers.com/showthread.php?p=47390175
This btw.
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app

I have now flashed the MK2 with Mobile Odin Pro.
I had trouble to download the flash-kernel with MOP, so I downloaded it here in the forum.
The Problem was unstable WiFi with Firmware MI7.
With MK2 I get the full speed of my Internet connection(50 MBit/s,WiFi Interface is 65 MBit/s), the Note 1 didn't(about 5-10 MBit/s).
@Killberty: I have read your thread very nice, I would have used your method if MOP had failed.
It's very good to know the command to create firmware update package.
I had bought MOB over a year ago for my Note 1, but because of 3 times it failed, I newer used it again.
I flashed with Odin and inserted root(Super User + Busybox) with temporary CWM.
This is why I hesitated and asked back here, but after all the positive response I tried.
Only Samsung realy detects what the firmware is rooted, so no firmware downloads from Samsung, I have to trust SamMobiles.
And Knox is not running, they tell you before activation of knox what all your data(in Knox Software) are lost if firmware is modified(won't start).

So I give a status update.
I wanted to find out why I can't update and maybe try Knox.
The strange think was Kies has shown PHN version, but i flashed DBT version with MOP.
I thought maybe language version is in bootloader.
So I first flashed back to MI7 with MOP. Now I don't have Modem acces(no wifi, gms..) and device restarts regulary.
So I wanted to flash the N9005XXUBMI7 N9005DBTBMI1 with standard odin, but failed because of to small hidden partition.
Hidden update for PHN was 8MB and for DBT over 60Mb, I think hidden partion is about 10MB.
So this was why Kies still have shown PHN version, because it couldn't be updated.
So I flashed original N9005XXUBMI7_N9005PHNBMI2_PHN, this was working.
Because I can't flash DBT I downloaded latest PHN N9005XXUDMJ7_N9005PHNDMJ4_PHN without bootloader of course(Killberty method, thanks.).
So I find following out.
I can't change to DBT version, because of to small hidden partition. I need a PIT file to repartition and could probably brick my device I will check forum if someone have successfully done it(I mean successfully repartitioned to other language, not bricked the device).
Kies updates can still be done, problem was I had version language combination with didn't exit from Samsung.
Downgrade is not possible, because modem isn't running.
OTA updates are available on unrooted device, even with RDLV updated script, so it should be possible to unroot by put the system partition to original state except RDLV script and get root later back without re flash.
This will not help to get Knox running, because Knox will check bootloader and not run with old one.(state from Samsung https://www.samsungknox.com/en/blog/about-root-de-la-vega).

I now have changed to DBT version.
To do what I needed a pit file, hadn't found the information on XDA but I found it on another forum.
It's in german and very nicely explained:
http://www.android-hilfe.de/anleitu...note-3-debranding-alle-eu-modelle-zu-dbt.html
http://www.android-hilfe.de/anleitu...8844-anleitung-pit-file-backup-erstellen.html
If somone need this ifo I can try to translate.
So to create a backup of your N9005 pit file you open terminal Emulator on rooted device.
su
dd if=/dev/block/mmcblk0 of=/sdcard/My-N9005.pit bs=1 skip=17408 count=4244
So you have the pit file on your internal sdcard.
I have now attached 2 pit files.
Netherlands N9005_PHN.pit
German N9005_DBT.pit
The DBT has 10 times bigger hidden volume, so the data partition is smaller. The rest is equal.
You need to flash with Re-Partition and Firmware with old boot-loader.
Go in recovery and format data partition.
Now install the actual Firmware with RDLV(without boot-loader).

Glad u got sorted
hit 'thanks' if i helped you
SM-N9005 0x0 X-Note7 ML2
XDA Developers 4 premium app

I9505 Downgrade from 4.4.2 to 4.3

Hi guys.
Some of you have read that in Note 3 its actually possible to downgrade from Kit Kat to 4.3 stock rom without trigger the knox counter.
Well, I made this thread so we can change some experiences.
So far, I was able to flash the 4.3 XXEMJ7 firmware on a 4.4.2 phone by doing the follow:
1- Extract a 4.4.2 rom to a folder using 7Zip
2- Extract a 4.3 XXEMJ7 rom to another folder using 7Zip
3- Move system.img.ext4 hidden.img.ext4 mdem.bin NON-HLOS.bin and rpm.bin from the 4.3 folder to the 4.4.2 folder.
4- In a linux terminal: tar -cvf output.tar <File1 File2 file3 ....>
5- Flash with Odin the Output.tar.
The phone flashed till the end and power ok without bootloops. Basically I flashed a Knoxed 4.4.2 Bootloader to the phone with all it's appendices (sbl1.mbn sbl2.mbn sbl3.mbn aboot.mbn boot.mbn and recovery.img) but with a 4.3 System, Modem and Rel Power Managment (rpm.bin).
The phone powered up ok and we can see on the phone 4.3 XXEMJ7 under the Android Version and baseband I9505XXEMJ7.
BUT KNOX GET TRIGGED.
Now the challenge: Do all this without trigger the knox.
Any toughs ?

BrunoWestone said:
Hi guys.
Some of you have read that in Note 3 its actually possible to downgrade from Kit Kat to 4.3 stock rom without trigger the knox counter.
Well, I made this thread so we can change some experiences.
So far, I was able to flash the 4.3 XXEMJ7 firmware on a 4.4.2 phone by doing the follow:
1- Extract a 4.4.2 rom to a folder using 7Zip
2- Extract a 4.3 XXEMJ7 rom to another folder using 7Zip
3- Move system.img.ext4 hidden.img.ext4 mdem.bin NON-HLOS.bin and rpm.bin from the 4.3 folder to the 4.4.2 folder.
4- In a linux terminal: tar -cvf output.tar <File1 File2 file3 ....>
5- Flash with Odin the Output.tar.
The phone flashed till the end and power ok without bootloops. Basically I flashed a Knoxed 4.4.2 Bootloader to the phone with all it's appendices (sbl1.mbn sbl2.mbn sbl3.mbn aboot.mbn boot.mbn and recovery.img) but with a 4.3 System, Modem and Rel Power Managment (rpm.bin).
The phone powered up ok and we can see on the phone 4.3 XXEMJ7 under the Android Version and baseband I9505XXEMJ7.
BUT KNOX GET TRIGGED.
Now the challenge: Do all this without trigger the knox.
Any toughs ?
Click to expand...
Click to collapse
is sound working?

Dosnt work over here.. can extract and add all the files without a problem.. but flashing the tar fails every time..

tommyukuk said:
Dosnt work over here.. can extract and add all the files without a problem.. but flashing the tar fails every time..
Click to expand...
Click to collapse
Have you tar the files in linux terminal using "tar -cvf output.tar file1 fle2 file3 file4 etc.... ?
It's working for me.

Yeah exactly how you wrote, creates the file no probs but odin refuses to flash it what so ever.. never mind tho..
Sent from my GT-I9505 using xda premium

Downgrade flash
BrunoWestone said:
Hi guys.
Some of you have read that in Note 3 its actually possible to downgrade from Kit Kat to 4.3 stock rom without trigger the knox counter.
Well, I made this thread so we can change some experiences.
So far, I was able to flash the 4.3 XXEMJ7 firmware on a 4.4.2 phone by doing the follow:
1- Extract a 4.4.2 rom to a folder using 7Zip
2- Extract a 4.3 XXEMJ7 rom to another folder using 7Zip
3- Move system.img.ext4 hidden.img.ext4 mdem.bin NON-HLOS.bin and rpm.bin from the 4.3 folder to the 4.4.2 folder.
4- In a linux terminal: tar -cvf output.tar <File1 File2 file3 ....>
5- Flash with Odin the Output.tar.
The phone flashed till the end and power ok without bootloops. Basically I flashed a Knoxed 4.4.2 Bootloader to the phone with all it's appendices (sbl1.mbn sbl2.mbn sbl3.mbn aboot.mbn boot.mbn and recovery.img) but with a 4.3 System, Modem and Rel Power Managment (rpm.bin).
The phone powered up ok and we can see on the phone 4.3 XXEMJ7 under the Android Version and baseband I9505XXEMJ7.
BUT KNOX GET TRIGGED.
Now the challenge: Do all this without trigger the knox.
Any toughs ?
Click to expand...
Click to collapse
Yesterday, I made output.tar file as you write. I used 4.4.2 ROM and 4.3 ROM for my S4. I flashed output.tar to my phone via Odin and it passed OK. Bud when finished phone displays logo and then only black screen. I am not able to go to recovery. I had to go to download mode and flash original 4.4.2 ROM to phone. Then it works fine again. Twice same result...

Hi,
I did it in an other way. I removed the file aboot.mbn in the firmware-archive of the android-verion 4.3 and renamed it to I9505XXUEMKE.tar.
In odin I selected the tar file and flashed my S4. Well, it works, but I have no sound in the system. In which way can I fix this problem?
Thx so much
I'm looking forward.
Best wishes.

Look here: https://forum.xda-developers.com/galaxy-s4/help/downgrade-lollipop-to-jellybean-t3334506