Related
(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
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
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
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
Hi,
I just want to know if it is possible :
I'm working now on an official multi csc firmware (PDA N910FXXU1BOC5 and CSC N910FOXX1BOC2).
In phone info, my csc is "MET"
As you know, oxx's firmware are multi csc firmware, and set "MET" as default when the csc of the phone in previous firmware is not included.
I know CSC's partition is on "cache.img.ext4" of the firmware. So, I just want to know :
Is it possible to extract cache.img.ext4 of the firm, delete every csc you don't want to switch to, (eg. for me I want XEF csc's, so I will let only this one). Repack and flash it, without tripping knox flag ?
Thank you in advence
anthony13 said:
I know CSC's partition is on "cache.img.ext4" of the firmware. So, I just want to know :
Is it possible to extract cache.img.ext4 of the firm, delete every csc you don't want to switch to, (eg. for me I want XEF csc's, so I will let only this one). Repack and flash it, without tripping knox flag ?
Click to expand...
Click to collapse
In my understanding this would trip the KNOX efuse. Any changes to the image files will do that. If however, you were to take the cache.img.ext4 of another official firmware and use that one, then you would probably be ok (if you do it right). However, not all combinations will work (it should probably be the same version, preferably of the same region, e.g. Europe). I can't find a seperate firmware for XEF by the way, it's only in your OXX multi-CSC.
You'd be better of just ignoring the CSC, after all apps can be disabled without root and the firmware will contain the french language anyway; plus you won't get XEF OTA updates anyway, because your phone still knows it is a MET phone and this mismatch will prevent OTA (or Kies) updates.