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
hallo i bought the note 4 n910f before 1 week and i would like to ask why i can not flash any rom with odin exept the german. with the other roms alwais fail or stuck to hidden.
anyone;;;
ADRIKOS22 said:
anyone;;;
Click to expand...
Click to collapse
hey there to root your Note 4 smn910f you first go to settings/security and then you will see a V behind reactivation deactivate this
after that's done connect to odin and flash cf root
you will see that it will not fail
i dont want to root yet i just want to change official rom and i can't flash via odin
it says when odin write hidden.img.ext4 volume size is too big 81920<184320
Can I ask which firmware you are trying to flash? Is it for the 910f if it's for a different variant that will probably be why
I have the German and I want to flash the Greek I downloaded them from sam mobile for the n910f
just came across the same issue something is messed with hidden partition image size, the default partition size is smaller whereas the the img file on the odin file is much bigger
bala_gamer said:
just came across the same issue something is messed with hidden partition image size, the default partition size is smaller whereas the the img file on the odin file is much bigger
Click to expand...
Click to collapse
Got the same problem today, cant flash any rom other than the latest UK (BTU) When trying to flash any other rom I get this message. Any idea how to fix it?
Some serious problem with Odin flashing the n910f. I have just gone through a night of torment, having tried flashing the newest firmware and getting a failure due to the hidden partition problem mentioned above.
Originally, my firmware was on n910fxxu1anj4. I flashed n910fxxu1ank6, the flash failed on flashing the hidden partition with:
Volume Size is too big 81920 < 204800
ODIN: Invalid ext4 image
and the phone was stuck in a bootloop on the first screen with the text “Note 4”.
Then even with wipe, restore of backup etc the phone wouldn't boot.
Flashed n910fxxu1ank5, same failure, didn't record the numbers, couldn't get it to boot in no way...
Flashed the original n910fxxu1anj4, flash failed also on the hidden partition with:
Volume Size is too big 81920 < 471040
Stuck in bootloop, but upon reflash of CWM recovery and cache and data clean, the phone booted, and I was able to restore a backup which works fine now...
However there must be some serious problem.
Anyone have an idea what this is?
--
白い熊
I think we need a correct PIT file for each firmware maybe ?
ADRIKOS22 said:
hallo i bought the note 4 n910f before 1 week and i would like to ask why i can not flash any rom with odin exept the german. with the other roms alwais fail or stuck to hidden.
Click to expand...
Click to collapse
From what I have gathered on some of the models is that the only firmware that you can flash to your phone are the ones made for the CSC of your phone. Navigate to system/csc then look at the different CSC files in that folder. Those are the only ones I can flash on my H model anyways.
CodeNameRedNeck said:
From what I have gathered on some of the models is that the only firmware that you can flash to your phone are the ones made for the CSC of your phone. Navigate to system/csc then look at the different CSC files in that folder. Those are the only ones I can flash on my H model anyways.
Click to expand...
Click to collapse
I had Swedish firmware with CSC NEE and could flash a firmware with CSC BTU. But I cant flash back the NEE firmware again. And looking at the hidden.img.ext4 and cache.img.ext4 in the only firmware I can flash it has the smallest. All the other firmwares have bigger hidden and cache files. So I think the phone needs to flashed with re-partition checked in Odin and that is not possible without the correct PIT file. I am relly tired of this phone, Samsung has made it too complicated to flash firmwares
easycure1974 said:
I had Swedish firmware with CSC NEE and could flash a firmware with CSC BTU. But I cant flash back the NEE firmware again. And looking at the hidden.img.ext4 and cache.img.ext4 in the only firmware I can flash it has the smallest. All the other firmwares have bigger hidden and cache files. So I think the phone needs to flashed with re-partition checked in Odin and that is not possible without the correct PIT file. I am relly tired of this phone, Samsung has made it too complicated to flash firmwares
Click to expand...
Click to collapse
Have you tried using Kies to do a firmware upgrade and initialization? When you plug your phone in Kies may warn you that it doesn't support your phone but you can still do it. You may be better off just leaving it alone though.
CodeNameRedNeck said:
Have you tried using Kies to do a firmware upgrade and initialization? When you plug your phone in Kies may warn you that it doesn't support your phone but you can still do it. You may be better off just leaving it alone though.
Click to expand...
Click to collapse
Yes tried that but with no luck, seems I am stuck with my BTU firmware. It gets the same error message on the phone "size is too big" and got a new error message on the phone [99] eMMC write fail: HIDDEN
Guys I tried flash latest Sweden and have same problem size too big and ext4 failed,then I flash Philz recovery and voila phone booted everything its ok!!!
Ogy77 said:
Guys I tried flash latest Sweden and have same problem size too big and ext4 failed,then I flash Philz recovery and voila phone booted everything its ok!!!
Click to expand...
Click to collapse
What was your original software? Could root have messed this up? Before rooting I flashed the BTU and DBT and NEE firmwares without problem. But then staying at BTU for some weeks and then rooted. And after that I can flash no other firmware. Trying to restore the phone to the NEE firmware as I am going to sell the phone.
Any more input on this? I did the same as Ogy77 and sure the phone boots but I got some strange crashes and did a factory reset and flashed back the stock recovery. So it boots but the CSC is gone as the cache.img.ext not is flashed so no OTAs will work as Kies does not regonize the phone with a firmware witout CSC?
I have the same problem, Im using xnote as i cant flash my vodafone UK stock rom
I was stuck in a bootloop but flashed twrp and installed xnote again as it was stored on my sd card luckily! I would like to know how to flash back to stock
I have same problem. I have a open 910F and get the same error on odin file size is too big. What can i do?
Hi all,
I have a TTT region N900 OS 4.3
Modem : N900UBUCMK1
I try to flash via Odin to upgrade to TGY region N900 OS 4.4.2 but realised flashing failed at end of process "
<ID:0/005> cache.img
<ID:0/005> FAIL!"
Question:
I saw the TGY modem is "N900XXUENG1", is is because the modem difference region having this problem?
I try to flash back the TTT 4.3 OS ROM but failed..
Need advise and help
Thanks !!!
Try latest kk but not TGY
Sent from my SM-N9005 using Tapatalk
qunnin said:
Hi all,
I have a TTT region N900 OS 4.3
Modem : N900UBUCMK1
I try to flash via Odin to upgrade to TGY region N900 OS 4.4.2 but realised flashing failed at end of process "
<ID:0/005> cache.img
<ID:0/005> FAIL!"
Question:
I saw the TGY modem is "N900XXUENG1", is is because the modem difference region having this problem?
I try to flash back the TTT 4.3 OS ROM but failed..
Need advise and help
Thanks !!!
Click to expand...
Click to collapse
Unfortunately TGY firmware is not compatible with other firmware (including TTT region)
Now you will need the PIT file to flash with the appropriate firmware (with the option Re-Partition selected).
- If you want to flash TGY firmware, you will need the PIT file from TGY device.
- If you want to flash TTT firmware, you will need the original PIT file from your device.
And note that do not flash back to the 4.3 as that may brick your device.
Try to flash only 4.4.2 from now on.
Thanks for your informative reply.
Do you know where I can download TTT or TGY pit file?
Most sites only have the ROM but not pit files
Thanks alot for your advice.
I successfully flash the TGY ROM via Odin using a TGY Pit with Re-Partition option
Phone reboot stuck at "Samsung Logo" ... go to Recovery ... reset data .. phone boot ok !
But keep show S pen input failed...then I reflash via odin without re-parition option... working well now
Thanks !!! Thanks !!
qunnin said:
Thanks alot for your advice.
I successfully flash the TGY ROM via Odin using a TGY Pit with Re-Partition option
Phone reboot stuck at "Samsung Logo" ... go to Recovery ... reset data .. phone boot ok !
But keep show S pen input failed...then I reflash via odin without re-parition option... working well now
Thanks !!! Thanks !!
Click to expand...
Click to collapse
Glad that it's useful to you.
And also thanks for your instruction.
Great.
Hello every one, i just want to ask question about my device, after i rooted and istall cm13 it works fine, but then im trying to back to stock rom it keep boot looping. And the knox warranty void goes to 1. I tried installign many stock rom and custom rom but all ended up with boot looping, only one rom work for me, the cm13 unofficial. Can somebody help my rblem?
1- download pit file http://www.mediafire.com/download/k4thfu9tnx02xjk/2-PIT-files-for-Samsung-+Devices.zip
2- flash pit file (N910C) with Odin 3.09
3- flash Stock rom
4- ENJOY !!
Muhammad Hesham said:
1- download pit file http://www.mediafire.com/download/k4thfu9tnx02xjk/2-PIT-files-for-Samsung-+Devices.zip
2- flash pit file (N910C) with Odin 3.09
3- flash Stock rom
4- ENJOY !!
Click to expand...
Click to collapse
i just flash this pit file along side stock rom in odin? will i retain my imei? ive read some where that after flash pit and stock rom it will loose imei, pls reply back thanks
Did you try wiping data in TWRP?
Solution here http://forum.xda-developers.com/note-4/help/fix-note4-exynos-n910c-bootloop-problem-t3312161
Hello,
I time ago i've updated my galaxy s5 900F to Marsmallow.
I've also updated the bootloader and modem for MM.
Now i want to go back to Lollipop because of bluetooth problems but do i als need to flash an other bootloader and modem again?
Where can i find these for Lollipop?
thx
stangerjunior said:
Hello,
I time ago i've updated my galaxy s5 900F to Marsmallow.
I've also updated the bootloader and modem for MM.
Now i want to go back to Lollipop because of bluetooth problems but do i als need to flash an other bootloader and modem again?
Where can i find these for Lollipop?
thx
Click to expand...
Click to collapse
No you can't boot a lollipop firmware with marshmallow bootloader,first of all make a backup because when you downgrade you have to factory reset your phone
You can find the S5 (G900F) firmware on sammobile,go to select country and search for your country or country that have the latest lollipop build BPE3(like Italy,Germany,Spain),then when you find the firmware you want to download click on it and find the product code(for example the prouct code of the italian fimwares is ITV), now download samfirm open it,and insert: on Model SM-G900F and on Region the product code of the firmware you chose to download(check the CRC32 and Decrypt option and uncheck binary nature because it will include userdata partition,useless in this case and also the firmware will be bigger to download) when it has finished to download extract the firmware zip,you should get a tar.md5 file out of it, download Odin,open it and insert your firmware on AP (uncheck repartition if it's checked) , now factory reset your phone from recovery(it will wipe also the internal sd so be sure to backup it) and reboot it in download mode,plug your phone in the computer , click start on odin and wait until the flashing process end,it will reboot automatically
Link:
G900F firmware: http://www.sammobile.com/firmwares/database/SM-G900F/
SamFirm: http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Odin: http://dl.sammobile.com/Odin3-v3.11.1.zip
Thx KillersEnergy
I have a question, will the process trigger knox counter?
my knox is still 0x0 and MM sucks will back to lollipop :/
and on SamFirm i cant Download the Lollipop Image, i just download it via sammobile...G900FXXS1BPE3_G900FDBT1BOJ1_G900FXXU1BOJ1_HOME.tar.md5
Checking firmware for SM-G900F/DBT/G900FXXS1BPE3/G900FDBT1BOJ1/G900FXXU1BOJ1
Newer firmware available:
Model: SM-G900F
Version: G900FXXU1CPEM/G900FDBT1CPE2/G900FXXU1CPC9/G900FXXU1CPEM
OS: Marshmallow(Android 6.0.1)
Filename: SM-G900F_1_20160603201627_g0majg44uu.zip.enc4
Size: 1504405616 bytes
LogicValue: r48jglz3xb5fxsrk
Click to expand...
Click to collapse
s3kt0r-7g said:
Thx KillersEnergy
I have a question, will the process trigger knox counter?
my knox is still 0x0 and MM sucks will back to lollipop :/
and on SamFirm i cant Download the Lollipop Image, i just download it via sammobile...G900FXXS1BPE3_G900FDBT1BOJ1_G900FXXU1BOJ1_HOME.tar.md5
Click to expand...
Click to collapse
No it will not trip knox as long as it have the proper signature: if the recovery.img and boot.img are signed from Samsung and you don't modify it because if you do the signature will become invalid(it's long to explain but if you want i'll explain it) it's impossible that knox will be tripped