[Q] How to get rid of locked bootloader? - Galaxy Note 3 Q&A, Help & Troubleshooting

Hi there,
I had to do a Firmware Upgrade and Initialization with Kies which put the latest firmware (N9005XXUBMJ3 for my country) on my device . As we know, everything from J3 upwards contains a locked bootloader which means that there is no way of downgrading stock or rooting with RDLV without tripping Knox 0x1.
Searched everywhere but couldn't find reliable information, so is anybody aware of a way to get rid of the locked bootloader as I absolutely want my root back without tripping Knox.
Any help is warmly welcome and appreciated!

Don Mueang said:
Hi there,
I had to do a Firmware Upgrade and Initialization with Kies which put the latest firmware (N9005XXUBMJ3 for my country) on my device . As we know, everything from J3 upwards contains a locked bootloader which means that there is no way of downgrading stock or rooting with RDLV without tripping Knox 0x1.
Searched everywhere but couldn't find reliable information, so is anybody aware of a way to get rid of the locked bootloader as I absolutely want my root back without tripping Knox.
Any help is warmly welcome and appreciated!
Click to expand...
Click to collapse
As for now it is not possible to get rid of the locked bootloader without tripping knox.
Hope that helps
Sent from my SM-N9005 using XDA Premium 4 mobile app

Is anyone aware of a way which modifies the secondary bootloader (turning off the security flag) or just replace the OEM bootloader without Knox being touched?
I am sure there is a dev out there who has invented something to circumvent this limitation, would you know?

Don Mueang said:
Is anyone aware of a way which modifies the secondary bootloader (turning off the security flag) or just replace the OEM bootloader without Knox being touched?
I am sure there is a dev out there who has invented something to circumvent this limitation, would you know?
Click to expand...
Click to collapse
Havent heard about something like this, and i am reading this note3 forum on xda much, as i have too much time at school
Seems like (for now) you cant get rid of the bootloader... or root with 0x0
Hope that helps
Sent from my SM-N9005 using XDA Premium 4 mobile app

What if I downloaded latest firmware which comes with a locked bootloader (e.g. N9005XXUDMJ6 or J7), kicked out the aboot.mbn file and replace it with the aboot.mbn from a firmware which still contains an unlocked bootloader (e.g. N9005XXUBMJ1)?
Would that work or will I get problems due to different firmwares (i.e. XXUDMJ7 vs. XXUBMJ1)? If so, please let me (and the interested reader in this thread) know what exactly will create an issue (e.g. first-stage vs. second-stage bootloader etc.). I am trying to understand more about (locked) bootloaders, thanks for your effort.

Don Mueang said:
What if I downloaded latest firmware which comes with a locked bootloader (e.g. N9005XXUDMJ6 or J7), kicked out the aboot.mbn file and replace it with the aboot.mbn from a firmware which still contains an unlocked bootloader (e.g. N9005XXUBMJ1)?
Would that work or will I get problems due to different firmwares (i.e. XXUDMJ7 vs. XXUBMJ1)? If so, please let me (and the interested reader in this thread) know what exactly will create an issue (e.g. first-stage vs. second-stage bootloader etc.). I am trying to understand more about (locked) bootloaders, thanks for your effort.
Click to expand...
Click to collapse
Don't you think one of the skilled dev's of these forums would have done it by now if it would work.
Forget about dreaming..
Sent from my SM-N9005 using Tapatalk

Don Mueang said:
What if I downloaded latest firmware which comes with a locked bootloader (e.g. N9005XXUDMJ6 or J7), kicked out the aboot.mbn file and replace it with the aboot.mbn from a firmware which still contains an unlocked bootloader (e.g. N9005XXUBMJ1)?
Would that work or will I get problems due to different firmwares (i.e. XXUDMJ7 vs. XXUBMJ1)? If so, please let me (and the interested reader in this thread) know what exactly will create an issue (e.g. first-stage vs. second-stage bootloader etc.). I am trying to understand more about (locked) bootloaders, thanks for your effort.
Click to expand...
Click to collapse
Wil definitely trip knox
Sent from my SM-N9005 using XDA Premium 4 mobile app

Related

Does flashing a different region stock trigger knox flag?

I'll have the aussie model in couple of days and I want to flash a stock ROM from a different region onto it (to bypass some of the dumb lock downs the aussie one has...)
Questions:
Will this trigger the knox warranty e fuse flag?
And
Will i then need worry about regional locks?
Sent from my GT-N7105T using Tapatalk 2
Also keen to know as well. I've seen some people say yes and others say no.
Sent from my SM-N9005 using XDA Premium 4 mobile app
I *think* its ok, provided the firmware you're loading isn't an older one than what you already have.
Even more sure if you don't have a knox firmware currently...
Sent from my GT-N7105T using Tapatalk now Free
I asked the question in another thread and got two different answers so I wanted to see if anyone tried it.
This one said yes:
http://forum.xda-developers.com/showthread.php?p=46122037#post46122037
This one said no:
http://forum.xda-developers.com/showthread.php?p=46247553#post46247553
I've also got an Australian Note 3 and in the past with my previous phones (Note 2 and S4) I flashed the UK stock ROM to get around the restrictions imposed on the Australian ROM. Before I do it again, I want to see if someone has tried it without any negative impact.
I started a previous thread with this question:
"I have a Note 3 n9005 XXUBMI7 firmware with csc N9005XSABMI1 (Australia) - unlocked, no carrier.
Will the Omega ROM V1.0 work on my phone (ie will, it support English(Australia)?)"
I am interested (ultimately) in experimenting with custom roms - as I did in my previous Note 1. This process will require a root and TWRP/CWM and will almost certainly void warranty because Knox Security digit will be set from 0 to 1 - unless someone finds a workaround.
What I am not sure about is the region coding - it seems that Samsung has a firmware version for every region (Australia is XSA)
playdough said:
I started a previous thread with this question:
"I have a Note 3 n9005 XXUBMI7 firmware with csc N9005XSABMI1 (Australia) - unlocked, no carrier.
Will the Omega ROM V1.0 work on my phone (ie will, it support English(Australia)?)"
I am interested (ultimately) in experimenting with custom roms - as I did in my previous Note 1. This process will require a root and TWRP/CWM and will almost certainly void warranty because Knox Security digit will be set from 0 to 1 - unless someone finds a workaround.
What I am not sure about is the region coding - it seems that Samsung has a firmware version for every region (Australia is XSA)
Click to expand...
Click to collapse
All I know is that after being boot looped, I was able to load the mexican firmware... but then after trying to flash SuperSU, which caused nothing but bugs, I tried to reinstall that same firmware and got another boot loop. I am now unable to install any available n900w8 firmware successfully. Some type of flag has been triggered on my phone that's preventing me from using a stock kernel/firmware... that's all I know.
Apra24 said:
All I know is that after being boot looped, I was able to load the mexican firmware... but then after trying to flash SuperSU, which caused nothing but bugs, I tried to reinstall that same firmware and got another boot loop. I am now unable to install any available n900w8 firmware successfully. Some type of flag has been triggered on my phone that's preventing me from using a stock kernel/firmware... that's all I know.
Click to expand...
Click to collapse
I'm pretty sure that Samsung's strategy is to make their devices a Samsung managed (and standardised) product (ala Apple and Microsoft) by locking owners into their firmware and even going beyond with region control. The only options, I believe, are either to stick with them at their behest or void warranty and support for personal freedom of choice. My view is that if software does not physically damage a device then I should be entitled to warranty claim if there is a manufacturing fault.
I was really referring to stock ROMs rather than custom.
Custom ROMs will flip the Knox switch.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Do not try and flash stock firmware from another region. It will not trigger the knox flag but the flash will fail in Odin and then you'll have to flash back the correct stock firmware for your region in order to be able to boot the phone again. The only way around it is to install a custom recovery and flash modified firmware which definitely will trigger the Knox flag.
Sent from my SM-N9005
dr.m0x said:
Do not try and flash stock firmware from another region. It will not trigger the knox flag but the flash will fail in Odin and then you'll have to flash back the correct stock firmware for your region in order to be able to boot the phone again. The only way around it is to install a custom recovery and flash modified firmware which definitely will trigger the Knox flag.
Sent from my SM-N9005
Click to expand...
Click to collapse
The mexican stock for sm-n900w8 went through fine as a Bell/Canadian user... but only the first time. I tried it because there are no Bell firmwares available. After trying to flash SuperSU, and having it crash constantly, causing me to re-flash the firmware.. it no longer worked.
Apra24 said:
The mexican stock for sm-n900w8 went through fine as a Bell/Canadian user... but only the first time. I tried it because there are no Bell firmwares available. After trying to flash SuperSU, and having it crash constantly, causing me to re-flash the firmware.. it no longer worked.
Click to expand...
Click to collapse
If your Knox flag is already set you may as well try the custom recovery and ROM option since it sounds like your phone is buggered.
Sent from my SM-N9005
Got the same question, I want to switch from the swiss unlocked (AUT) stock rom to either the german (DBT) or UK (BTU) one. I even compared the files of the AUT and DBT tar.md5 and only cache.img.ext4 and hidden.img.ext4 are different, all others a binary identical.
Could I limit Odin to only exchange those two data files and nothing else?
In Android-Hilfe.de an User tried it..
First he had Vodafone Branding, then he flashed the Open Germany Firmware.. Without Problems.. Knox is still 0x0
gesendet von meinem Samsung Galaxy Note II
My EE (UK) SM-N9005 CSC is N9005EVRBMI2 and I've just used Odin v3.09 to flash the KIES ROM with the CSC N9005OXABMI6 (same as SIM-free phones).
Knox warranty is still 0x0
Apra24 said:
All I know is that after being boot looped, I was able to load the mexican firmware... but then after trying to flash SuperSU, which caused nothing but bugs, I tried to reinstall that same firmware and got another boot loop. I am now unable to install any available n900w8 firmware successfully. Some type of flag has been triggered on my phone that's preventing me from using a stock kernel/firmware... that's all I know.
Click to expand...
Click to collapse
You've probably set the reactivation lock enabled, therefore stopping the restore
Sent from my SM-N9005 using Tapatalk 4
dehaani said:
My EE (UK) SM-N9005 CSC is N9005EVRBMI2 and I've just used Odin v3.09 to flash the KIES ROM with the CSC N9005OXABMI6 (same as SIM-free phones).
Knox warranty is still 0x0
Click to expand...
Click to collapse
I had to do a device wipe from recovery menu to reset the CSC from EVR to BTU.
Then I got the FOTA update to MJ1 so it seemed like my phone is now indistinguishable from a SIM-free device but...
Kies still knows something's up. It reports the CSC as BTU but says "Your device's current firmware version is not supported to update firmware via Kies".
I wonder how Kies knows? Any ideas?
I found a local user that has been able to do this successfully
Used this Firmware:
N9005XXUBMI7_N9005OJVBMI2_XSI.zip
http://www.sammobile.com/firmwares/1/?model=SM-N9005&pcode=XSI#firmware
https://lh3.googleusercontent.com/-..._A/E3sK9J9W9L0/w831-h661-no/note3firmware.png
senectus said:
I found a local user that has been able to do this successfully
Used this Firmware:
N9005XXUBMI7_N9005OJVBMI2_XSI.zip
http://www.sammobile.com/firmwares/1/?model=SM-N9005&pcode=XSI#firmware
https://lh3.googleusercontent.com/-..._A/E3sK9J9W9L0/w831-h661-no/note3firmware.png
Click to expand...
Click to collapse
Does he still have HD Voice with that firmware?
Will endeavour to find out... How does one check?
(still waiting on my unit to turn up :-[)
Sent from my GT-N7105T using Tapatalk now Free
senectus said:
Will endeavour to find out... How does one check?
(still waiting on my unit to turn up :-[)
Sent from my GT-N7105T using Tapatalk now Free
Click to expand...
Click to collapse
Nevermind. I've taken the plunge and trying it. I'll report back.
---------- Post added at 04:28 PM ---------- Previous post was at 03:53 PM ----------
Ok.
I flashed the latest Unknown Country ROM (XSI) from SamMobile which was "N9005XXUBMJ1_N9005OJVBMI2_XSI". Originally, I was running a Vodafone Australia ROM (VAU).
I used ODIN 3.04 and reset the device in recovery after the ROM was updated.
The CSC is now XSI and the KNOX warranty trigger is 0x0 (Woohoo)!
With the new ROM, it also bypassed all the Australian restrictions. These were:
- Unable to change dock applications
- No auto rotate in gallery
- Unable to silence camera shutter
- Shortcuts not available as an option on lock screen
HD Voice is also still working.

[Q] Note 3 OTA update

Hi,
I have question regarding the OTA update, which I am not get it in my Note 3 SM-N9005 (not rooted),my current firmware is MJ1. When i click on check for update it tells me that i have the latest firmware!!
Am i missing something?why my note 3 not updating?
thank you.
It hasn't been rolled out to your region yet.
ilikegoogle said:
It hasn't been rolled out to your region yet.
Click to expand...
Click to collapse
how long does it take to rollout to all regions?
I live in Malaysia
thank you
OTA
I got my OTA update yesterday yet to find out the change log for your region I guess the update has not yet been rolled out it will take some more time
Dahdoul said:
Hi,
I have question regarding the OTA update, which I am not get it in my Note 3 SM-N9005 (not rooted),my current firmware is MJ1. When i click on check for update it tells me that i have the latest firmware!!
Am i missing something?why my note 3 not updating?
thank you.
Click to expand...
Click to collapse
just go here and download latest update http://samsung-updates.com/device/?id=SM-N9005
and save yourself lot of time waiting for update
Just be aware you will change your CSC and also your bootloader to the newest. As your region hasn't updated to a firmware with the latest bootloader if you have a problem and need to do an emergency firmware restore, it won't work. Your phone will start bootlooping as the older firmware is incompatible with the new bootloader...
ultramag69 said:
Just be aware you will change your CSC and also your bootloader to the newest. As your region hasn't updated to a firmware with the latest bootloader if you have a problem and need to do an emergency firmware restore, it won't work. Your phone will start bootlooping as the older firmware is incompatible with the new bootloader...
Click to expand...
Click to collapse
so I shouldn't update if I'm rooted?
wudien said:
so I shouldn't update if I'm rooted?
Click to expand...
Click to collapse
OK, depends how you do it. I've used Mobile ODIN Pro to upgrade firmware from MJ1 to MJ7 while still retaining root. This also has the extra benefit of NOT flashing that new crusty bootloader that won't allow root or triggering warranty void.
Also I can still do my emergency recovery as it has the old bootloader.
There are people using RDLVC to upgrade to newer firmwares but Mobile ODIN Pro is easier for me (just remember though, Knox will ALWAYS be triggered if you flash a custom kernel\recovery - this is for stock flash only).
As long as you have the old bootloader, you can upgrade using MOP without triggering Knox.
Kingoapp and Vroot have been removed from XDA as there was extra information being taken from your device for no good reason... You will probably see clone phones with these IMEI's coming out in a while...
ultramag69 said:
OK, depends how you do it. I've used Mobile ODIN Pro to upgrade firmware from MJ1 to MJ7 while still retaining root. This also has the extra benefit of NOT flashing that new crusty bootloader that won't allow root or triggering warranty void.
Also I can still do my emergency recovery as it has the old bootloader.
There are people using RDLVC to upgrade to newer firmwares but Mobile ODIN Pro is easier for me (just remember though, Knox will ALWAYS be triggered if you flash a custom kernel\recovery - this is for stock flash only).
As long as you have the old bootloader, you can upgrade using MOP without triggering Knox.
Kingoapp and Vroot have been removed from XDA as there was extra information being taken from your device for no good reason... You will probably see clone phones with these IMEI's coming out in a while...
Click to expand...
Click to collapse
well. Unfortunately att forcefully updated my phone while I was sleeping and broke root . but it says I'm still on MJ5..
wudien said:
well. Unfortunately att forcefully updated my phone while I was sleeping and broke root . but it says I'm still on MJ5..
Click to expand...
Click to collapse
As far as I've read, anything over MJ3 contains the new anti-root bootloader. Flashing any form of root will trigger knox warranty void...

[Q] I want to gain root to install Xposed possible without triping Knox?

Hey XDA. I was seeing that Exposed will allow me to install App ops again in 4.4.2 when it goes OTA .
is there a way I can root my note3 without triping knox? I wont install a new rom or anything. ill just keep the stock firmware. as the stock firmware is pretty sorted with app ops.
Firstly what is your firmware?
And secondly have a search round, you'll see different guides and advice.
Sent from my SM-N9005 using XDA Premium 4 mobile app
MJ3 and above will trip knox... A little looking and reading would find this out.
As for KitKat, might be different method to root when that comes out... Might not be able to use Mobile ODIN Pro to upgade as there have been a few problems reported with the latest firmwares...
radicalisto said:
Firstly what is your firmware?
And secondly have a search round, you'll see different guides and advice.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hey mate.
im android 4.3
baseband is N9005XXUDMJ7
I was asking (probably in a weird way) I thought I read Knox wont trip if you just gain root! it trips Knox when you install a new ROM after you root it.??
So if I gain root, and just keep the same baseband will that be safe? as I really like app opps in 4.3 I have a public transpot timetable app that wants to read my contact list, my call logs, and other crap! If google wont police these permissions, then I'm sooo happy we have ap ops and with 4.2.2 O/S performance improves so much not to mention lots of security fixes. I would hate to disable OTA updates. and I think the stock samsung rom is so sorted. I dont see the point in installing a new O/S (maybe to debloat, which I agree there is a lot of crap, wish you could do a custom install on your stock samsung to say no I dont want all bloat)
Knox will trip when you root because you have MJ7 - no way around it currently. -
As for OTA updates, all you gotta do is flash back to stock again to make the device official.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Hey guys my baseband is MJ7 and the build is UDMK2, does that mean I cannot root without tripping knox? I think so but not sure. So the baseband/modem has the bootloader in it or the build MK2???
Sent from my SM-N9005 using XDA Premium 4 mobile app
benc88 said:
Hey guys my baseband is MJ7 and the build is UDMK2, does that mean I cannot root without tripping knox? I think so but not sure. So the baseband/modem has the bootloader in it or the build MK2???
Click to expand...
Click to collapse
Not necessarily 100% true, the baseband, the system and the bootloader are different things, and you CAN have an older bootloader and a newer system, but NOT the other way around.
However when you only install firmware "the Samsung way" those are kept pretty much "in sync", so in your case you can be pretty certain that you have the new bootloader and you can not root without tripping knox
Technically you could find more precise info on the bootloader with:
adb shell getprop ro.boot.bootloader

[Q] Bootloader decision

Hello everybody,
I have an unlocked (debranded) romanian N9005 currently rooted using Mobile Odin Pro with Knox intact on 4.3 MJ7. With the current release of 4.4.2, I read that I need to update the bootloader if I flash it using MOP or else I'll experience bootloops.
Updating the bootloader won't be so bad assuming I'll be at least able to update to newer options with root and Knox intact since other then App Ops I can't think of any reason to downgrade to 4.3. But my worry is that once I update the bootloader, if I will ever have to turn my phone for a repair (presuming it will be something that's not caused by my modifications) I won't be able to re-root my phone without tripping Knox (since even without having Knox tripped I'd have to get rid of root before handing it to Samsung) because I won't be able to downgrade to 4.3 so I can re-root using URLDV. So basically, I also want to know if it's possible and worth waiting for a supposed method to downgrade to 4.3 that's somehow dependent on this bootloader I have. This is my first Android phone and that's why I'm not very familiar with what developers can do for these kinds of situations.
Thank you!
TwasBeats said:
Hello everybody,
I have an unlocked (debranded) romanian N9005 currently rooted using Mobile Odin Pro with Knox intact on 4.3 MJ7. With the current release of 4.4.2, I read that I need to update the bootloader if I flash it using MOP or else I'll experience bootloops.
Updating the bootloader won't be so bad assuming I'll be at least able to update to newer options with root and Knox intact since other then App Ops I can't think of any reason to downgrade to 4.3. But my worry is that once I update the bootloader, if I will ever have to turn my phone for a repair (presuming it will be something that's not caused by my modifications) I won't be able to re-root my phone without tripping Knox (since even without having Knox tripped I'd have to get rid of root before handing it to Samsung) because I won't be able to downgrade to 4.3 so I can re-root using URLDV. So basically, I also want to know if it's possible and worth waiting for a supposed method to downgrade to 4.3 that's somehow dependent on this bootloader I have. This is my first Android phone and that's why I'm not very familiar with what developers can do for these kinds of situations.
Thank you!
Click to expand...
Click to collapse
Chances of downgrade happening in the future are slim to non existent.
Upgrading, via Odin to Official ROM won't hurt your phone. - If you update the bootloader you Must upgrade the ROM also.
You won't be able to re-root your phone unless you update via Mobile Odin - correct.
radicalisto said:
Chances of downgrade happening in the future are slim to non existent.
Click to expand...
Click to collapse
So basically you say that I should wait for Samsung to unlock their bootloader sometime in the future when the phone inevitably goes out of the spotlight?
radicalisto said:
Upgrading, via Odin to Official ROM won't hurt your phone. - If you update the bootloader you Must upgrade the ROM also.
Click to expand...
Click to collapse
I was talking about upgrading to the official rom and thus updating the bootloader too.
TwasBeats said:
So basically you say that I should wait for Samsung to unlock their bootloader sometime in the future when the phone inevitably goes out of the spotlight?
Click to expand...
Click to collapse
Won't ever happen, Samsung have locked them on purpose. - Same happened on MJ7 downgrade was impossible, Samsung class downgrading as a security risk hence them blocking it.
I was talking about upgrading to the official rom and thus updating the bootloader too.
Click to expand...
Click to collapse
Was just checking.
radicalisto said:
Won't ever happen, Samsung have locked them on purpose. - Same happened on MJ7 downgrade was impossible, Samsung class downgrading as a security risk hence them blocking it.
Click to expand...
Click to collapse
It's one thing to not let you downgrade without tripping Knox which is fairly reasonable but not letting you downgrade at all even when you have tripped Knox and having the phone deemed by Samsung as a security risk is ridiculous. It may be my first Samsung phone but chances are it's going to also going to be my last one if they continue this ridiculous policy.
TwasBeats said:
It's one thing to not let you downgrade without tripping Knox which is fairly reasonable but not letting you downgrade at all even when you have tripped Knox and having the phone deemed by Samsung as a security risk is ridiculous. It may be my first Samsung phone but chances are it's going to also going to be my last one if they continue this ridiculous policy.
Click to expand...
Click to collapse
Welcome to Samsung lol.
Is it possible that Samsung might release 4.4.2 for N9005 in one of regions it's available? I read that the Mexican N900W8 has the bootloader unlocked.
TwasBeats said:
It's one thing to not let you downgrade without tripping Knox which is fairly reasonable but not letting you downgrade at all even when you have tripped Knox and having the phone deemed by Samsung as a security risk is ridiculous. It may be my first Samsung phone but chances are it's going to also going to be my last one if they continue this ridiculous policy.
Click to expand...
Click to collapse
You're not alone, it's not my 1st Samsung phone but it might be the last one.
Apparently you can upgrade with MOP, will still require a factory reset so backup, by flashing KK with MOP then using PC ODIN to flash the bootloader (and MODEM?). You need the broken up rom though...
Don't know for sure as I had already tripprd Knox long ago and updated to KK...
I was well aware of that but my main concern is a downgrade solution would get developed that requires the old bootloader after I've presumably already updated. Anyhow I think today I'll just update today and get rid of a worry.
Wiping everything isn't necessary, but I will still do it.

[Q] Rooting on Vodafone UK

Hi,
Wondered if someone could please help, as I wish to root without tripping knox, as it's important I have secured work emails.
Just upgraded from Xperia Z, and got experience of rooting that in various ways, along with rooting other Android phones. However, been a while since I had a Samsung phone, but not had one with knox before.
Phone has come with the following firmware:
PDA: N9005XXUBMI7
Phone: N9005XXUBMI6
CSC: N9005VFGBMI1
I've done loads of reading on the subject, and appears that I can use Root de la Vega universal 0.5 without tripping knox with the above firmware.
Could someone please confirm what I believe that it's possible to root the above firmware without tripping root?
Assuming that it is possible, Vodafone have also issued the following firmware update, which I've downloaded to pc from SamMobile, but not yet installed:
N9005XXUDMJ6_N9005VFGDMJ1_VOD
Is there a way I can then flash this update, say with Odin, without tripping root?
Really appreciate any assistance thanks
You can root mi7 without tripping knox using urdlv, then upgrade to your latest vodafone software using mobile odin pro, keeing your root and your knox 0x0
hit 'thanks' if i helped you
SM-N9005 0x0 X-Note7 ML2
XDA Developers 4 premium app
Hi Killberty,
Really appreciate your response thanks.
Once rooted with URDLV, would I then upgrade with Odin Pro as per the instructions here:
http://forum.xda-developers.com/showthread.php?t=2522729
Many thanks again.
Killberty said:
You can root mi7 without tripping knox using urdlv, then upgrade to your latest vodafone software using mobile odin pro, keeing your root and your knox 0x0
hit 'thanks' if i helped you
SM-N9005 0x0 X-Note7 ML2
XDA Developers 4 premium app
Click to expand...
Click to collapse
Hi,
Does anyone else know the answer to the above please?
Many thanks
LEGGYMAMBO said:
Hi Killberty,
Really appreciate your response thanks.
Once rooted with URDLV, would I then upgrade with Odin Pro as per the instructions here:
http://forum.xda-developers.com/showthread.php?t=2522729
Many thanks again.
Click to expand...
Click to collapse
Yep, this is what I've done. I had a locked vodafone uk N9005 with MI7 initially. I urdlv to root. Then mop only to MJ7.
Note if you want to flash kitkat U'll need to use MOP 4.00 to flash rom and pc odin to flash bootloader only.
I'm still knox 0x0 & have root.
Sent from my SM-N9005 using Tapatalk
LEGGYMAMBO said:
...
I've done loads of reading on the subject, and appears that I can use Root de la Vega universal 0.5 without tripping knox with the above firmware.
Could someone please confirm what I believe that it's possible to root the above firmware without tripping root?
...
Click to expand...
Click to collapse
If you mean "without tripping Knox" - the answer is yes, it should work with URDLV.
LEGGYMAMBO said:
...
Assuming that it is possible, Vodafone have also issued the following firmware update, which I've downloaded to pc from SamMobile, but not yet installed:
N9005XXUDMJ6_N9005VFGDMJ1_VOD
Is there a way I can then flash this update, say with Odin, without tripping root?
...
Click to expand...
Click to collapse
Again - "without tripping Knox" - yes, but not with Odin but instead much easier with a program called Mobile Odin Pro - see the detailed thread on that here:
http://forum.xda-developers.com/showthread.php?t=2522729
(in theory I do not like paid hacking programs but that one is an exception since it is from Chainfire and buying it is a way to encourage him to keep doing great hacks for the community).
Many thanks for your reply dsm52!!
I'm now rooted using URDLV, ready for the next process.
Is the following file classed as MJ6 or MJ1, as it appears Vodafone UK haven't released MJ7?!
N9005XXUDMJ6_N9005VFGDMJ1_VOD
The reason I ask, is because the following thread states "UNSUCCESSFUL ROOT :MJ6 and later":
http://forum.xda-developers.com/showthread.php?t=2522729
In addition, do you mind me asking which version of KK you've used, as Vodafone UK haven't released this yet?
I need to retain knox 0x0
Many thanks again
dsm52 said:
Yep, this is what I've done. I had a locked vodafone uk N9005 with MI7 initially. I urdlv to root. Then mop only to MJ7.
Note if you want to flash kitkat U'll need to use MOP 4.00 to flash rom and pc odin to flash bootloader only.
I'm still knox 0x0 & have root.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Hi xclub_101,
Many thanks for your reply. Aye, I did mean "without tripping knox", doh!!
Bought MOP as a big fan of the work and help produced by Chainfire.
Cheers
xclub_101 said:
If you mean "without tripping Knox" - the answer is yes, it should work with URDLV.
Again - "without tripping Knox" - yes, but not with Odin but instead much easier with a program called Mobile Odin Pro - see the detailed thread on that here:
http://forum.xda-developers.com/showthread.php?t=2522729
(in theory I do not like paid hacking programs but that one is an exception since it is from Chainfire and buying it is a way to encourage him to keep doing great hacks for the community).
Click to expand...
Click to collapse
LEGGYMAMBO said:
Many thanks for your reply dsm52!!
I'm now rooted using URDLV, ready for the next process.
Is the following file classed as MJ6 or MJ1, as it appears Vodafone UK haven't released MJ7?!
N9005XXUDMJ6_N9005VFGDMJ1_VOD
The reason I ask, is because the following thread states "UNSUCCESSFUL ROOT :MJ6 and later":
http://forum.xda-developers.com/showthread.php?t=2522729
In addition, do you mind me asking which version of KK you've used, as Vodafone UK haven't released this yet?
I need to retain knox 0x0
Many thanks again
Click to expand...
Click to collapse
It sounds like you want to stay with official Vodafone rom versions.
I didn't see any need to, so I flashed MJ7 BTU (UK) using MOP as the next step, which worked perfectly.
I flashed mk2 btu wheb that came out in the same way.
Fir kitkat, like most others, i flashed the Polish XEO NA6 official rom. Like I said kitkat flash is a little more tricky due to the extra bootloader flashing step. Personally, kitkat release isn't quite ready for prime time so samsung haven't rolled it out in more regions. There a few little quirks about it, e.g. genuine s view cover not working for all. I'd suggest waiting for the official BTU release before flashing by which time they may have ironed out the little bugs.
Good luck!
Sent from my SM-N9005 using Tapatalk
I'm getting Vodafone note 3 do they come sim locked? Does chain fires sim lock app work on Vodafone phones thanks.
I prefer to use my EE sim.
Thanks for reading.
riz157 said:
I'm getting Vodafone note 3 do they come sim locked? Does chain fires sim lock app work on Vodafone phones thanks.
I prefer to use my EE sim.
Thanks for reading.
Click to expand...
Click to collapse
They do come sim locked. However, getting an unlock code isn't difficult. Worth calling customer services in your 1st 7 days & saying u need to use the phone abroad. Worked for me.
Sent from my SM-N9005 using Tapatalk
dsm52 said:
They do come sim locked. However, getting an unlock code isn't difficult. Worth calling customer services in your 1st 7 days & saying u need to use the phone abroad. Worked for me.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Yes I could try that but I was looking for a quicker and cheaper way.
riz157 said:
Yes I could try that but I was looking for a quicker and cheaper way.
Click to expand...
Click to collapse
Actually I was unlocked within a few mins of making the call - unlock code got texted to me. And it was free - most likely because I was within my first 7 days of a new contract.
If it's not a new contract phone, then some others have reported chainfire's region lock away to work:
http://forum.xda-developers.com/showthread.php?t=2470551
Sent from my SM-N9005 using Tapatalk

Categories

Resources