Related
I have rooted my Note 3 succesfully with RDLV, without tripping Knox. I am really happy with that.
My phone is branded Vodafone, with CSC N9005VFGBMI1. The latest Firmware for that is MI7.
I have a few questions about this, hope someone can help me with this.
I want to update to N9005XXUDMK2_N9005OXADMK2_BTU.zip. I know it's a different csc, is that possible? (I know I will lose Knox 0x0)
If that is possible, how do I do that?
Thanks!
Pierre118 said:
I have rooted my Note 3 succesfully with RDLV, without tripping Knox. I am really happy with that.
My phone is branded Vodafone, with CSC N9005VFGBMI1. The latest Firmware for that is MI7.
I have a few questions about this, hope someone can help me with this.
I want to update to N9005XXUDMK2_N9005OXADMK2_BTU.zip. I know it's a different csc, is that possible? (I know I will lose Knox 0x0)
If that is possible, how do I do that?
Thanks!
Click to expand...
Click to collapse
Somebody show me the way? Just flash the BTU with Odin? I don't mind tripping knox.
Pierre118 said:
I have rooted my Note 3 succesfully with RDLV, without tripping Knox. I am really happy with that.
My phone is branded Vodafone, with CSC N9005VFGBMI1. The latest Firmware for that is MI7.
I have a few questions about this, hope someone can help me with this.
I want to update to N9005XXUDMK2_N9005OXADMK2_BTU.zip. I know it's a different csc, is that possible? (I know I will lose Knox 0x0)
If that is possible, how do I do that?
Thanks!
Click to expand...
Click to collapse
1. You should read the thread on how to update the system using Mobile Odin PRO without losing knox 0x0. Also keep in mind that you need to stop both ROM and security automatic updates in order to avoid having the knox flag triggered.
2. Also check http://www.sammobile.com/firmwares/1/?model=SM-N9005&pcode=VOD#firmware
3. If you really want to change CSC away from VOD and for instance to BTU you should probably do that first at MI7 level (from your current MI7 VOD to MI7 BTU) if you want maximum safety and to be able to root again with knox 0x0. You might also need an app to help you checking/changing CSC, look around for threads discussing that specific topic.
Can I safely use a firmware with a CSC N9005VFGDMJ1? Or do I always have to use a firmware of the original CSC? (N9005VFGBMI1)?
Pierre118 said:
Can I safely use a firmware with a CSC N9005VFGDMJ1? Or do I always have to use a firmware of the original CSC? (N9005VFGBMI1)?
Click to expand...
Click to collapse
You do not need to use a firmware with the original CSC, BUT:
- you should try to do as much of the changes as possible on OLDER versions with the old bootloader (so that you can still root and keep knox 0x0)
- writing a ROM with a different CSC will very often NOT change your effective CSC - many ROMs are multi-CSC and you might keep existing CSC on the new ROM; in order to finalize the change you will need to use a program that forces the CSC change (and you will see that the CSC was changed since it will totally wipe the user data in the phone - like a full factory reset)
- you should also be aware that some changes might mess things on your phone, so instead of jumping to the first change you can think-off you should first try to read more around here.
xclub_101 said:
You do not need to use a firmware with the original CSC, BUT:
- you should try to do as much of the changes as possible on OLDER versions with the old bootloader (so that you can still root and keep knox 0x0)
- writing a ROM with a different CSC will very often NOT change your effective CSC - many ROMs are multi-CSC and you might keep existing CSC on the new ROM; in order to finalize the change you will need to use a program that forces the CSC change (and you will see that the CSC was changed since it will totally wipe the user data in the phone - like a full factory reset)
- you should also be aware that some changes might mess things on your phone, so instead of jumping to the first change you can think-off you should first try to read more around here.
Click to expand...
Click to collapse
Thanks for your helpful reply. I will take your advice and will read more around here before I do things I don't understand. I'm rooted now at firmware MI7, with 0x0 Knox. I did a lot of reading before I took that step. I will take time before I do the next one.
Pierre118 said:
Thanks for your helpful reply. I will take your advice and will read more around here before I do things I don't understand. I'm rooted now at firmware MI7, with 0x0 Knox. I did a lot of reading before I took that step. I will take time before I do the next one.
Click to expand...
Click to collapse
Don't forget to disable automatic updates and security updates. Especially read the thread on Mobile Odin PRO and updating while keeping knox 0x0. (CSC is almost irrelevant in most cases - as long as 3G/4G from your provider is correctly detected; if you are rooted with knox 0x0 you will ALWAYS want to update the ROM manually under YOUR control and not when Samsung or your carrier wants to update your phone).
xclub_101 said:
Don't forget to disable automatic updates and security updates. Especially read the thread on Mobile Odin PRO and updating while keeping knox 0x0. (CSC is almost irrelevant in most cases - as long as 3G/4G from your provider is correctly detected; if you are rooted with knox 0x0 you will ALWAYS want to update the ROM manually under YOUR control and not when Samsung or your carrier wants to update your phone).
Click to expand...
Click to collapse
What do you freeze in titanium backup so it won't update.
Dattack said:
What do you freeze in titanium backup so it won't update.
Click to expand...
Click to collapse
Software Update (also Samsung Hub Update, but that is just since I never use the Samsung Hub). Right now I did not freeze the Security Policy Update but I am tempted - but on that I first disabled automatic security updates somewhere in settings.
Pierre118 said:
Can I safely use a firmware with a CSC N9005VFGDMJ1? Or do I always have to use a firmware of the original CSC? (N9005VFGBMI1)?
Click to expand...
Click to collapse
In fact N9005VFGDMJ1 and N9005VFGBMI1 are from the same CSC
Hola,
Got my Note 3 a while back, and I'm getting itchy firmware fingers!
Maybe I'm being stupid - but so far I haven't had any luck in 'automatically' finding updated firmwares - still sitting on the MHN one that was installed when I bought the phone back on November.
Am I doing anything wrong? Do I need to root to be able to update the firmware? KIES says I'm on the latest... Not a network locked phone - have used t-mob, orange and currently a 3 sim.
Halp!
Hup we go!
No updates have ever come through either OTA or KIES... why me!
pipohippo said:
Hup we go!
No updates have ever come through either OTA or KIES... why me!
Click to expand...
Click to collapse
mate why dont you update via pc odin then ? and you dont need root to upgrade via kies
here try this for guide
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
get your firmware from here
http://www.samfirmware.com/
pipohippo said:
Hup we go!
No updates have ever come through either OTA or KIES... why me!
Click to expand...
Click to collapse
Maybe you should post more details - for instance what version of Note 3 do you have (ideally you want to know the original code, something like N9005ZWE or N9005ZKEBTU, which identifies a N9005 for UK) and what firmware are you right now. And eventually what have you asked when originally asked about the country where you are (for the license agreement). If the combinations above get very weird you also need to know your effective CSC, but that could be a longer shot.
Thanks for the responses guys - I assumed Odin also required rooting, so I will have a proper look! Good questions to ask as well, so just for reference, phone is the following:
Product Code SM-N9005ZKEBTU
Bootloader Version N9005XXUBMHN
Baseband Version N9005XXUBMHN
Android Version 4.3 (whatever came out of the box)
pipohippo said:
Thanks for the responses guys - I assumed Odin also required rooting, so I will have a proper look! Good questions to ask as well, so just for reference, phone is the following:
Product Code SM-N9005ZKEBTU
Bootloader Version N9005XXUBMHN
Baseband Version N9005XXUBMHN
Android Version 4.3 (whatever came out of the box)
Click to expand...
Click to collapse
No my friend as I said before updating via odi n dsnt require root... great now you can just download 4.4.2 firmware for your note 3 and update
Sent from my SM-N900 using Tapatalk
pipohippo said:
Thanks for the responses guys - I assumed Odin also required rooting, so I will have a proper look! Good questions to ask as well, so just for reference, phone is the following:
Product Code SM-N9005ZKEBTU
Bootloader Version N9005XXUBMHN
Baseband Version N9005XXUBMHN
Android Version 4.3 (whatever came out of the box)
Click to expand...
Click to collapse
N9005ZKEBTU seems to be be EU-British unlocked N9005 - I would assume that you also picked UK when asked about the license agreement.
N9005XXUBMHN is a very interesting version of the firmware that is not even listed here:
http://www.sammobile.com/firmwares/1/?model=SM-N9005&pcode=BTU#firmware
You seem to have a fairly recent firmware and for the moment there is no 4.4.2 version of the BTU sub-region.
I am guessing that the firmware is actually way old, so it's not listed! Assuming the firmwares are in alphabetical order!
MHx < MJx
All UK aye - good to know that the phone is actually unlocked though I'll have a look on SamMobile and grab a nice 4.3 firmware - not ready for KitKat yet!
xclub_101 said:
N9005ZKEBTU seems to be be EU-British unlocked N9005 - I would assume that you also picked UK when asked about the license agreement.
N9005XXUBMHN is a very interesting version of the firmware that is not even listed here:
-
You seem to have a fairly recent firmware and for the moment there is no 4.4.2 version of the BTU sub-region.
Click to expand...
Click to collapse
pipohippo said:
I am guessing that the firmware is actually way old, so it's not listed! Assuming the firmwares are in alphabetical order!
MHx < MJx
All UK aye - good to know that the phone is actually unlocked though I'll have a look on SamMobile and grab a nice 4.3 firmware - not ready for KitKat yet!
Click to expand...
Click to collapse
Hmm, for some reason I was thinking MK instead of MH, indeed your firmware is unusual! But please be aware that those old firmware versions are the only ones that can be safely rooted without triggering the knox warranty flag. Which reminds me - if you go to download mode do you see any reference to knox?
Knox Kernal Lock: 0x0
Knox Warranty Void: 0x0
I am guessing that is kind of good right?
final clarification - rooting has the possibility of triggering knox warranty shizzle, but just doing a 'standard' firmware update (even via odin) should keep things fine right?
xclub_101 said:
Hmm, for some reason I was thinking MK instead of MH, indeed your firmware is unusual! But please be aware that those old firmware versions are the only ones that can be safely rooted without triggering the knox warranty flag. Which reminds me - if you go to download mode do you see any reference to knox?
Click to expand...
Click to collapse
pipohippo said:
Knox Kernal Lock: 0x0
Knox Warranty Void: 0x0
I am guessing that is kind of good right?
final clarification - rooting has the possibility of triggering knox warranty shizzle, but just doing a 'standard' firmware update (even via odin) should keep things fine right?
Click to expand...
Click to collapse
Correct, standard Odin update WITH THE RIGHT FIRMWARE will be fine.
IMHO your absolute best path from this point would be something like this:
- save whatever you need to save to the cloud or eventually on the external microSD (just in case)
- disable reactivation lock; disable any updates and security updates in the current ROM; stop mobile data and WiFi; keep all updates off and all network off until the very last step of the entire procedure
- using normal Odin and download mode install oldest BTU firmware you can get - MI7 in the link I provided above; that update should go without any problem; reboot and check everything is OK (and stop again any network or update if re-enabled); this step is only needed in order to get you on the EXACT same path that the huge majority of the people around (including me) have used with URDLV; it might be possible to skip this and still have everything working 100% (and this is quite very likely but I have not tested it);
- using Universal Root de la Vega (URDLV) and the same MI7 from above you will generate a N9005XX____MI7_HOME_VEGA.tar.md5 file which then you will again write with normal Odin and in download mode; this will get you rooted on MI7 with knox 0x0 ; you can read more about this in the URDLV thread
- then using Mobile Odin Pro (NOT normal Odin / download mode) and the most recent 4.3 version available for BTU you can update to MJ7 or MK2 - while keeping root and knox 0x0!
Read for more details on the last step this thread:
http://forum.xda-developers.com/showthread.php?t=2522729
Also note that Mobile Odin Pro will also let you update to 4.4 and keep root and knox 0x0, so it is not a bad investment. Also note that at this point there is no other way to root with knox 0x0 once you got past a certain firmware, nor is it possible to go back before the version of your bootloader (so in other words the above procedure also would guarantee that you can get back to MI7 if for instance you do not like MK2, something you would never otherwise be able to do).
As my signature shows - MJ7 / MK2 are currently very solid versions (and if you are rooted you can get amazing battery life and performance) and I would strongly suggest avoiding any upgrade towards 4.4 in the immediate future.
Hi,
I've just got a Note 3 so not sure of all the ins and outs. I've been reading the forum and worked out it's status is Custom.
I don't think it's rooted, I certainly haven't done it.
Basically I want the Kit Kat update but it tells me I can't update OTA as it's modified and through Kies it says it's up to date which isn't true. I'm on 4.3.
Anyway If I can do the update with Odin I'd be happy but could you help me:
Firstly what version of Odin should I use. I can see a 3.07. It seems old but is that OK ?
Secondly I can't work out what firmware I need to download for it. I have done *#1234# and this is what it tells me the following:
AP: N9005XXUBMJ3
CP: N9005XXUBMJ1
CSC:N9005DBTBMJ3
Any ideas what it is and which I'd need to download for it ? When I got it the phone was set to German by default but I'm not sure if that means it is German or not.
I'd like to use a UK firmware if I can but would that screw the phone up in some way. I've read about KNOX.... not really sure what that's about but it doesn't sound too good if I break it.
Basically any help on what to download and I guess how to use Odin to put it on there would be greatly appreciated!!
Thank you
Daniel
diggott said:
Hi,
I've just got a Note 3 so not sure of all the ins and outs. I've been reading the forum and worked out it's status is Custom.
I don't think it's rooted, I certainly haven't done it.
Basically I want the Kit Kat update but it tells me I can't update OTA as it's modified and through Kies it says it's up to date which isn't true. I'm on 4.3.
Anyway If I can do the update with Odin I'd be happy but could you help me:
Firstly what version of Odin should I use. I can see a 3.07. It seems old but is that OK ?
Secondly I can't work out what firmware I need to download for it. I have done *#1234# and this is what it tells me the following:
AP: N9005XXUBMJ3
CP: N9005XXUBMJ1
CSC:N9005DBTBMJ3
Any ideas what it is and which I'd need to download for it ? When I got it the phone was set to German by default but I'm not sure if that means it is German or not.
I'd like to use a UK firmware if I can but would that screw the phone up in some way. I've read about KNOX.... not really sure what that's about but it doesn't sound too good if I break it.
Basically any help on what to download and I guess how to use Odin to put it on there would be greatly appreciated!!
Thank you
Daniel
Click to expand...
Click to collapse
any ODIN will do. I used 3.0.9, and flashed well.
You can download any firmware. don't worry. If you wish to use German firmware, there's NB7 - DBT, but this firmware need a pit file to be flashed together with it.
If you want UK, there's also UK version
The latest one, which most of the dev use as a base for custom ROM is NC2 czech. I personally have flashed this stock firmware into some of my friend's Note 3, and run into no trouble with ODIN 3.0.9.
You should try to go into download mode, and see what is written down there. As you said your system status is modified/custom, I believe if you go into download mode, you will find KNOX = 0x1.
I found this state as well on my friend's new N9005 stock 4.3 unrooted. My friend bought an export set for Europe countries (and it happened to be German firmware as well, same as yours)
cheers.
Thanks for the reply. It's good to know it shouldn't hurt whichever I decide to go with.
In terms of where I should get the ROM from. Is http://samsung-updates.com/ the best place to get it ?
Here http://samsung-updates.com/device/?id=SM-N9005 I see there are some NC2 ones but no Czech one. Would the top one the Philipines one work ?
Also I can't get into Download Mode. It just comes up with android system recovery (3e). Is that a problem ?
Sorry I really haven't a clue with all this.
Thanks
diggott said:
Thanks for the reply. It's good to know it shouldn't hurt whichever I decide to go with.
In terms of where I should get the ROM from. Is http://samsung-updates.com/ the best place to get it ?
Here http://samsung-updates.com/device/?id=SM-N9005 I see there are some NC2 ones but no Czech one. Would the top one the Philipines one work ?
Also I can't get into Download Mode. It just comes up with android system recovery (3e). Is that a problem ?
Sorry I really haven't a clue with all this.
Thanks
Click to expand...
Click to collapse
go to here : www.samfirmware.com
login there / sign up if you have no account.
just type ur device on the textbox firmware. you will find the firmware that you want
philipines one should also work. try to find those without the provider carrier (less bloatware)
to go into download mode : power down your device. after that you can power up by using ==> vol down + home + power, once you go in then press vol up to continue.
to go into recovery mode (the one u mentioned above) : power down your device. after that power up using ==> vol up + home + power.
Right just realised what I was doing wrong and got into the Download Mode. It says KNOX Warranty Void 0x1
Does that matter ? I don't need to use the private file storage thing really to be honest.
Can I still flash a ROM OK ?
And again is that one on samsung-updates.com OK ?
Thank you!
diggott said:
Right just realised what I was doing wrong and got into the Download Mode. It says KNOX Warranty Void 0x1
Does that matter ? I don't need to use the private file storage thing really to be honest.
Can I still flash a ROM OK ?
And again is that one on samsung-updates.com OK ?
Thank you!
Click to expand...
Click to collapse
to be honest, KNOX flag trip will only affect if you have use the KNOX container earlier before it trip.
But if you never use, it should be fine. It will only a matter of warranty which is the main issue. But since you said you have never done anything to your phone, I believe you have bought it from 3rd party (non samsung store) which claim to be an export set (which come without samsung warranty). This thing happen to 1 of my friend actually which I mentioned on my above posting.
But don't worry, means now you don't need to worry about KNOX trip anymore (unless you want to bring up the issue to whom you bought the phone from, and actually it will be useless as well, as no prove the knox is tripped by the seller).
You can just download any firmware. Go to the site I mentioned earlier (to get the newest) : www.samfirmware.com
get it from there.
OR
you can visit this thread, and get it from the mirror link there : http://forum.xda-developers.com/showthread.php?t=2643109
the NC2 is listed at the 1st post on the top part (easy for you to find). My opinion better go to this thread. This thread using mega storage, faster download compare to the at at samfirmware
cheers!
antique_sonic said:
to be honest, KNOX flag trip will only affect if you have use the KNOX container earlier before it trip.
But if you never use, it should be fine. It will only a matter of warranty which is the main issue. But since you said you have never done anything to your phone, I believe you have bought it from 3rd party (non samsung store) which claim to be an export set (which come without samsung warranty). This thing happen to 1 of my friend actually which I mentioned on my above posting.
But don't worry, means now you don't need to worry about KNOX trip anymore (unless you want to bring up the issue to whom you bought the phone from, and actually it will be useless as well, as no prove the knox is tripped by the seller).
You can just download any firmware. Go to the site I mentioned earlier (to get the newest) : www.samfirmware.com
get it from there.
OR
you can visit this thread, and get it from the mirror link there : http://forum.xda-developers.com/showthread.php?t=2643109
the NC2 is listed at the 1st post on the top part (easy for you to find). My opinion better go to this thread. This thread using mega storage, faster download compare to the at at samfirmware
cheers!
Click to expand...
Click to collapse
Brilliant! Thank you for all your help I have now flashed it with Odin to 4.4.2. I went for the UK one in the end which might not be the very latest version but I'm happy
Thanks again that's made my day. You're right I don't care about KNOX and couldn't prove anything anyway so I shall carry on and enjoy my nice new KitKat Note 3
Daniel
[Q] Downgrading Galaxy Note 3 SM-N9005 from 4.4.2→4.3 without E-Fuse/Guarantee Loss
Hello everybody.
Is there any way to downgrade the Galaxy Note 3 SM-N9005 from 4.4.2 to 4.3, without triggering the E-Fuse-Chip to short-circuit which causes feautre-loss and guarantee loss?
It's OK, if the Guarantee is just TEMPORAIRLY disabled, while the downgrade is in progress
But after the downgrade, the device should be like a new one.
I also don't want any damage on my device like lower processing power, guarantee loss, heat problems or compatibility problems.
Also, i've already backed all data up, so backup isn't really needed.
Please don't ask me, why i want to take this downgrade. KitKat has so many unknown software disadvantages, and compatibility problems and it's too bogus.
If you know, how to do this, but you don't think, that a downgrade is not needed, please post it yet.
Short Story
The Shop, where the Note 3 is bought from mentioned this device to have Android 4.3 Jelly Bean, but i was shocked/disappointed, after i saw KitKat.
The KitKat-Wafer is quite tasty, but the Android-Operation-System is quite bitter.
I really appreciate any help you can provide.
Far as I know flashing an official binary will not trip your Knox. Don't know about KK to JB downgrades because the bootloader can not be flashing back to JB after KK has been applied.
AO7 said:
Far as I know flashing an official binary will not trip your Knox. Don't know about KK to JB downgrades because the bootloader can not be flashing back to JB after KK has been applied.
Click to expand...
Click to collapse
Thank you very much for answering.
So, i just have to start ODIN, and let's/here we go?
Right?
What i understand
So that means:
Download ODIN
Install ODIN
Download Firmware
Connect Note 3 to PC
[*]Let's go (Load Firmware on Note 3)
Will the downgrade be sucessfully?
No Guarantee Loss
[*]No eFuse-Trigger
No Feature Loss
No Other Problems
Temporaire guarantee loss is OK, if it can be restored.
But i don't want to Trigger the EFuse-Short Circuit.
Missing
Step 1 download and install Samsung/ Kies USB drivers .
Open Odin put relevant files in correct box.
Connect phone to PC
Make sure correct boxes ticked in Odin .
Hit start button
No Guarantee Loss >>> No not 100% possible .
Knox Triggered by custom rom / kernel/ recovery not by stock rom .
Really would not downgrade as i don't see you as understanding the basics .
Is your EFS folder backed up is question 1 as a downgrade may lose your IMEI .
Hannah Stern said:
What i understand
So that means:
Download ODIN
Install ODIN
Download Firmware
Connect Note 3 to PC
[*]Let's go (Load Firmware on Note 3)
Will the downgrade be sucessfully?
No Guarantee Loss
[*]No eFuse-Trigger
No Feature Loss
No Other Problems
Temporaire guarantee loss is OK, if it can be restored.
But i don't want to Trigger the EFuse-Short Circuit.
Click to expand...
Click to collapse
I'm gonna agree with the poster above Hannah. It looks like you don't really understand what you are doing.
Here's a very quick rundown:
1. Get the Samsung phone drivers
2. Get Odin 3.09
3. Get EFS professional and make several EFS backups of all partitions
4. If your phone is carrier branded only download stock firmware specifically for your carrier brand. Otherwise any region stock firmware should work. Do not use Hong Kong FW unless your phone is from HK. for safety, stick to firmware of your approximate geographical area to avoid possible issues with modems.
5. Read, read, and read as many threads on this forum as you can.
6. There are a bunch of steps after this which i won't all type out. Refer to point 5...
JJEgan said:
Missing
Step 1 download and install Samsung/ Kies USB drivers .
Open Odin put relevant files in correct box.
Connect phone to PC
Make sure correct boxes ticked in Odin .
Hit start button
No Guarantee Loss >>> No not 100% possible .
Knox Triggered by custom rom / kernel/ recovery not by stock rom .
Really would not downgrade as i don't see you as understanding the basics .
Is your EFS folder backed up is question 1 as a downgrade may lose your IMEI .
Click to expand...
Click to collapse
OK, Understood
AO7 said:
I'm gonna agree with the poster above Hannah. It looks like you don't really understand what you are doing.
Here's a very quick rundown:
1. Get the Samsung phone drivers
2. Get Odin 3.09
3. Get EFS professional and make several EFS backups of all partitions
4. If your phone is carrier branded only download stock firmware specifically for your carrier brand. Otherwise any region stock firmware should work. Do not use Hong Kong FW unless your phone is from HK. for safety, stick to firmware of your approximate geographical area to avoid possible issues with modems.
5. Read, read, and read as many threads on this forum as you can.
6. There are a bunch of steps after this which i won't all type out. Refer to point 5...
Click to expand...
Click to collapse
OK, Thanks very much.
I've got a German SM-N9005
What is the Newest Baseband Version with Android 4.3?
I think, it is:
PDA: N9005XXUDMJ7
CSC: N9005OXADMJ4
Or is MK2 newer?
Hannah Stern said:
I've got a German SM-N9005
What is the Newest Baseband Version with Android 4.3?
I think, it is:
PDA: N9005XXUDMJ7
CSC: N9005OXADMJ4
Or is MK2 newer?
Click to expand...
Click to collapse
Very basic Samsung FW decoder:
Device identifer - region code - FW identificator ( The lower the letter in the alphabet the newer the software)
N9005 - XXU - MJ7
This is the last 4.3 FW for DBT (Generic Germany)
http://samsung-updates.com/details/22095/Galaxy_Note_3_Snapdragon/SM-N9005/DBT/N9005XXUDMK2.html
AO7 said:
It looks like you don't really understand what you are doing.
Click to expand...
Click to collapse
That's why i was asking.
>>> But thank you very much for letting me know, which is the lastest 4.3-JB-Firmware for the Galaxy Note 3 and telling me, how Samsung's Firmware Codes work.
I owe you something for that great post...
The only problems are the upload sites:
Both pages Suck
UL.TO - Dead Link
RapidGator - Struggle to Download
But i managed it to download that file.
Thank you very much @AO7. The world needs more people like you.
Baseband is Modem and not always updated at the same time as firmware updated .
@JJEgan
@AO7
I'm trapped.
Is there any way to
Root without triggering EFuse
or EFS-Backup without root?
Here's my thread about EFuse. (This text is the link itself)
Hannah Stern said:
@JJEgan
@AO7
I'm trapped.
Is there any way to
Root without triggering EFuse
or EFS-Backup without root?
Here's my thread about EFuse. (This text is the link itself)
Click to expand...
Click to collapse
I use EFS Backup Pro to backup my modem and EFS partitions but that requires root. TWRP also has the ability to backup the modem partition, but flashing a custom recovery will trigger knox 0x1.
I've tripped my knox over a year ago so I don't keep up with how to root the phone while keeping knox 0x0. A quick google gave me this post but I have not tried it myself.
If you manage to root your phone and keep it 0x0 than technically I imagine you can backup your EFS. The question is it's still worthwhile to go to all this trouble. The N9005 is approaching its' second birthday. In my personal case, since I don't care for extended warranties on electronics, my legal basic warranty already expired some time ago anyway.
there might be some obscure proprietary Samsung features that depend on Knox. But other than those, I see no real point in trying to keep your phone 0x0.
AO7 said:
I use EFS Backup Pro to backup my modem and EFS partitions but that requires root. TWRP also has the ability to backup the modem partition, but flashing a custom recovery will trigger knox 0x1.
I've tripped my knox over a year ago so I don't keep up with how to root the phone while keeping knox 0x0. A quick google gave me this post but I have not tried it myself.
If you manage to root your phone and keep it 0x0 than technically I imagine you can backup your EFS. The question is it's still worthwhile to go to all this trouble. The N9005 is approaching its' second birthday. In my personal case, since I don't care for extended warranties on electronics, my legal basic warranty already expired some time ago anyway.
there might be some obscure proprietary Samsung features that depend on Knox. But other than those, I see no real point in trying to keep your phone 0x0.
Click to expand...
Click to collapse
EFS backup always shows up an error while starting up. Then it closes itself.
EFS and EFuse...:crying:
does anyone here still have that jelly bean file?
pottylotty said:
does anyone here still have that jelly bean file?
Click to expand...
Click to collapse
What JB file ???
Hi, i know there is another thread but i think is not the same problem.
In "About Device" my S5 show SM-G900F branded for United Arab Emirates (XSG - G900FXXU1POEC) but in "Download Mode" the screen info show me different version of galaxy S5..... SM-G9006V wich is from China.....wtf?
Is something like that legit?
My question is if i want to flash new firmware for XSG ( G900FXXU1POI1 ) will it work or i brick device / or trip Knox?
The firmware for SM-G9006V use different CSC and if i try to flash this will triping KNOX waranty, is corect?
INFO
-I forgot to mention that sees no new firmware via Kies, OTA or Smart Switch although there are two firmware already released.
-When i try "Firmware upgrade and initialization" in Kies 3 after type of Model name field -SM-G900F and serial number
its say my serial number is wrong but when type in Model name field SM-G9006V and serial the procedure want to continue wich meant is OK.
The System operational you need to download the exact one that is described on Download Mode.
The Download mode is the real one.
If you want to flash only the modem/CSC you can flash the G900F.
But the Kernel and the Bootloader i think you need to flash the G9006V.
if you flash an Firmware differently from your download mode you can brick your device (Soft-Brick, not Hard-Brick)
If you bought it from someone, you can easily edit on config to show anything you want on About Device.
Hi, thanks for answer, but its something i dont get it.
How they manage to do some thing, flashing G9006V firmware and after that flashing G900F XSG firmware ( AP-CP-CSC) without triger the Knox.
Anyway, Is there an easier way to flash the latest update for the UAE of September 2015 and to keep the same configuration, the bootloader from G9006V,
XSG G900F kernel and CSC from UAE without enable Knox or brick my phone.
cryogent said:
Hi, thanks for answer, but its something i dont get it.
How they manage to do some thing, flashing G9006V firmware and after that flashing G900F XSG firmware ( AP-CP-CSC) without triger the Knox.
Anyway, Is there an easier way to flash the latest update for the UAE of September 2015 and to keep the same configuration, the bootloader from G9006V,
XSG G900F kernel and CSC from UAE without enable Knox or brick my phone.
Click to expand...
Click to collapse
As far as I know only custom kernels and custom recoveries trigger Knox. Technically custom non touchwiz roms also will I believe, but since you flash them from recovery that's a little implied, not 100% sure on that though, someone correct me if I'm wrong.
Sent from my SAMSUNG-SM-G900A using Tapatalk
To flash anything you need to root. therefore you are going to trigger the knox.
I BELIEVE that you can only flash original firmware TOUCH WIZ without root
DBlackFireD said:
To flash anything you need to root. therefore you are going to trigger the knox.
I BELIEVE that you can only flash original firmware TOUCH WIZ without root
Click to expand...
Click to collapse
Rooting does not trigger Knox.
Sent from my SAMSUNG-SM-G900A using Tapatalk
The only root method that WON'T trip knox is towelroot, and that method won't work on anything other than KitKat.
CF Root WILL trip knox.
TWRP WILL trip knox.
So for most people rooting will trip knox
http://i.imgur.com/rVnFwJM.jpg
I would like to point out that using apps such as kingoroot allow one click roots that won't trip Knox. After the build.prop is modified they can just unroot and it'll be like nothing happened
justinxfan said:
I would like to point out that using apps such as kingoroot allow one click roots that won't trip Knox. After the build.prop is modified they can just unroot and it'll be like nothing happened
Click to expand...
Click to collapse
Point noted....I have no experience of those root methods....
The methods I mentioned are the main methods (with dedicated threads) to be found/mentioned on XDA........
http://i.imgur.com/rVnFwJM.jpg
Thank you all for your help but leave this thread because I gave the phone back and chose another producer.
The problem could not be solved by those at the store because all the phones were lot of the same trouble.
Sorry I can not help you with other information in the future.
Thank
Sent from my XT1063 using Tapatalk