Database Users

[Q] ODIN flashing older rom.

Hey guys so i have heard that if i install the old firmware for my s4 from sammobile using Odin one from early 2013 that it will give me access to service menu so that i can unlock my phone. So my question is that is it 100% safe to Odin flash the older 4.2.2 rom when i am on 4.3? Can i flash it unlock my phone then upgrade my phone to a custom rom again? Thank you
Sent from my SGH-M919V using xda app-developers app

Do not do this. This will brick your phone. If I am not mistaken, there is a method to unlock mk2 in the general section.
Sent from my SAMSUNG-SGH-I337 using Tapatalk

zee24 said:
Hey guys so i have heard that if i install the old firmware for my s4 from sammobile using Odin one from early 2013 that it will give me access to service menu so that i can unlock my phone. So my question is that is it 100% safe to Odin flash the older 4.2.2 rom when i am on 4.3? Can i flash it unlock my phone then upgrade my phone to a custom rom again? Thank you
Sent from my SGH-M919V using xda app-developers app
Click to expand...
Click to collapse
You should ask this in the t mobile s4 forum. I believe your bootloader is unlocked and you can flash an older firmware version. But check there first. This is the att s4 forum. It can't be done on the at&t s4.

Is the service menu missing on the stock T-mo 4.3 ?

Nooo guys i have an unlocked bootloader i have the s4 that is very similar to the tmobile and it's the same as the Canadian versions. And yes the Canadian version which is 1337m and mine which is m919v don't have access to service menus but i have flashed a lot of custom roms simply by philz recovery so doesn't that mean i have an unlocked bootloader?

zee24 said:
Nooo guys i have an unlocked bootloader i have the s4 that is very similar to the tmobile and it's the same as the Canadian versions. And yes the Canadian version which is 1337m and mine which is m919v don't have access to service menus but i have flashed a lot of custom roms simply by philz recovery so doesn't that mean i have an unlocked bootloader?
Click to expand...
Click to collapse
If you're on 4.3 I believe you also have Knox, in which case I don't think you'll be able to go back to 4.2.2. Read through this http://forum.xda-developers.com/showthread.php?p=40903040

jd1639 said:
If you're on 4.3 I believe you also have Knox, in which case I don't think you'll be able to go back to 4.2.2. Read through this http://forum.xda-developers.com/showthread.php?p=40903040
Click to expand...
Click to collapse
I'm actually running a custom rom i shouldve mentioned im on phoenix rom. So i don't have knox at the moment. Does that matter?

zee24 said:
I'm actually running a custom rom i shouldve mentioned im on phoenix rom. So i don't have knox at the moment. Does that matter?
Click to expand...
Click to collapse
Did you ever take the ota to 4.3? Do you know what firmware your device is on? A 4.3 custom Rom wouldn't have knox but if you took the official update to 4.3 you would have Knox.

jd1639 said:
Did you ever take the ota to 4.3? Do you know what firmware your device is on? A 4.3 custom Rom wouldn't have knox but if you took the official update to 4.3 you would have Knox.
Click to expand...
Click to collapse
Hmm i think then yes i might have knox. I think at one point i might have been on stock 4.3 is there any way that i can check to see if i have knox? And if i have knox i cant flash an older stock firmware for my s4?

zee24 said:
Hmm i think then yes i might have knox. I think at one point i might have been on stock 4.3 is there any way that i can check to see if i have knox? And if i have knox i cant flash an older stock firmware for my s4?
Click to expand...
Click to collapse
Idk, I'm not that familiar with your device. From the little bit of reading I've done I would say no, you can't flash an older firmware. But again, I'd post this question in the t mobile forum. They'd be more familiar with your device.

zee24 said:
Hmm i think then yes i might have knox. I think at one point i might have been on stock 4.3 is there any way that i can check to see if i have knox? And if i have knox i cant flash an older stock firmware for my s4?
Click to expand...
Click to collapse
Did you ever update you device with kies or ever take an over the air update ? It's fine if you were on a stock based 4.3 rom as long as you never took an official update. If so then you can't go back. Just flashing a stock 4.3 rom won't change that status but the 4.3 bootloader would.
You would have know by checking in settings under SE

hednik said:
Did you ever update you device with kies or ever take an over the air update ? It's fine if you were on a stock based 4.3 rom as long as you never took an official update. If so then you can't go back. Just flashing a stock 4.3 rom won't change that status but the 4.3 bootloader would. You would have know by checking in settings under SE
Click to expand...
Click to collapse
I remember i soft bricked my phone one time and had to flash my firmware but the 4.3 latest one from sammobile and after i did that i got knox but i believe i already tripped the knox counter because in download mode it says 0x1 so i guess i cant?

[Q] When coming from a 4.3 ROM to a 4.4 KitKat and the New Bootloader

I have just been having a read about the 4.4 for N3 and people are talking about the new bootloader and not forcing it and some people being hard bricked.
My question is this, is going from a custom 4.3 to a custom 4.4 is there anything I need to do to make sure it installs correctly or doesn't hard brick?
Or is the only problem going from 4.4 back to 4.3?
At the moment on X-Note and just looking at a couple of the other Touchwiz 4.4 custom roms, if I install one of them can I not go back?
And is this the same for the CM 4.4 Nightlies?
Thanks

alpward said:
I have just been having a read about the 4.4 for N3 and people are talking about the new bootloader and not forcing it and some people being hard bricked.
My question is this, is going from a custom 4.3 to a custom 4.4 is there anything I need to do to make sure it installs correctly or doesn't hard brick?
Or is the only problem going from 4.4 back to 4.3?
At the moment on X-Note and just looking at a couple of the other Touchwiz 4.4 custom roms, if I install one of them can I not go back?
And is this the same for the CM 4.4 Nightlies?
Thanks
Click to expand...
Click to collapse
Bootloader will auto install if you choose XEO package.
You cannot go back once you upgrade, so no CM no XNOTE etc (for now at least) - You can go on SweetROM or AndroidNOW and a couple of others though.

radicalisto said:
Bootloader will auto install if you choose XEO package.
You cannot go back once you upgrade, so no CM no XNOTE etc (for now at least) - You can go on SweetROM or AndroidNOW and a couple of others though.
Click to expand...
Click to collapse
But I can go from any 4.4 ROM to any other 4.4 ROM? So I could go to CM11 from SweetROM or AndroidNOW?

alpward said:
But I can go from any 4.4 ROM to any other 4.4 ROM? So I could go to CM11 from SweetROM or AndroidNOW?
Click to expand...
Click to collapse
CM is 4.4 but the bootloader is MJ7 based. Which means it will not work on the NA6 Bootloader that comes with 4.4.2 -- You can use SweetROM AndroidNOW, KINGDROID or FlexKAT only. No CM Build will run on the NA6 Bootloader currently and probably not for a long time yet.

radicalisto said:
CM is 4.4 but the bootloader is MJ7 based. Which means it will not work on the NA6 Bootloader that comes with 4.4.2 -- You can use SweetROM AndroidNOW, KINGDROID or FlexKAT only. No CM Build will run on the NA6 Bootloader currently and probably not for a long time yet.
Click to expand...
Click to collapse
Cool, good to know. If I had backed up a ROM not on NA6, could I restore back to that? That restores the old bootloader, yeah?

Nope, Samsung block all downgrades. And this applies to NA6, which means once you upgrade to NA6 you are stuck with it until further notice with no return. Chances are a return will never be possible the same as going back before MJ7 which is still impossible.

radicalisto said:
Nope, Samsung block all downgrades. And this applies to NA6, which means once you upgrade to NA6 you are stuck with it until further notice with no return. Chances are a return will never be possible the same as going back before MJ7 which is still impossible.
Click to expand...
Click to collapse
Just, hopefully, one last thing:
If I do go from a NA6 back to MJ7, will I brick my phone?

alpward said:
Just, hopefully, one last thing:
If I do go from a NA6 back to MJ7, will I brick my phone?
Click to expand...
Click to collapse
IF you attempt it you will bootloop, so basically a soft brick yes. And you'll need to reflash NA6 to get out of the bootloop

alpward said:
But I can go from any 4.4 ROM to any other 4.4 ROM? So I could go to CM11 from SweetROM or AndroidNOW?
Click to expand...
Click to collapse
What region is your phone? If its Hong Kong TGY, then you can install only Hong Kong Firmware. So, be careful.

rinuvimal said:
What region is your phone? If its Hong Kong TGY, then you can install only Hong Kong Firmware. So, be careful.
Click to expand...
Click to collapse
I think I've got a French version, how do I check?

alpward said:
I think I've got a French version, how do I check?
Click to expand...
Click to collapse
Dial *#1234# on your phone. You'll you'll see three codes, AP, CP and CSC.
In CSC, check what code you see.
compare it to these region codes : http://forum.xda-developers.com/wiki/Csc

rinuvimal said:
Dial *#1234# on your phone. You'll you'll see three codes, AP, CP and CSC.
In CSC, check what code you see.
compare it to these region codes : http://forum.xda-developers.com/wiki/Csc
Click to expand...
Click to collapse
My CSC is N9005OXXDMK3, it doesn't match any of the codes...

@alpward , did you try to update your firmware using Kies3? Since you have a Poland CSC, you should get the Official 4.4.2 update via Kies. Give it a try.

rinuvimal said:
@alpward , did you try to update your firmware using Kies3? Since you have a Poland CSC, you should get the Official 4.4.2 update via Kies. Give it a try.
Click to expand...
Click to collapse
I don't really want to go to a non-custom ROM. My other question is, if I backup a pre 4.4 pre-new bootloader ROM, can I restore back to it after going to the new bootloader or does it lock it forever?

alpward said:
I don't really want to go to a non-custom ROM. My other question is, if I backup a pre 4.4 pre-new bootloader ROM, can I restore back to it after going to the new bootloader or does it lock it forever?
Click to expand...
Click to collapse
You are locked to the new bootloader forever until further notice.

radicalisto said:
You are locked to the new bootloader forever until further notice.
Click to expand...
Click to collapse
Lucky, cause I haven't updated just yet.

alpward said:
Lucky, cause I haven't updated just yet.
Click to expand...
Click to collapse
Yip, I'd sit on your current BL for now, see what happens with this new KK stuff in the next few weeks... Especially now sources are available etc also.

radicalisto said:
Yip, I'd sit on your current BL for now, see what happens with this new KK stuff in the next few weeks... Especially now sources are available etc also.
Click to expand...
Click to collapse
How can you tell what bootloader the ROM has before installing? As in, CM11 doesn't have the new bootloader, right?

ROM Post should tell you what BL it's running, and yes, CM runs on the old BL either MJ7 or MK* depending on build.

[share] about knox , root and odin firmware [please read before posting]

Hey friends:
im a normal member and everything above is only sharing
So you may get upset because of this thread
but i'll make things clear, everytime i open Q&A forum i see repeated questions everywhere
so here ill put some repeated answers about those stuff above
1. knox: well when you buy a new galaxy s5 the knox state will be 0*0 , but when you root your phone, flash custom recovery,custom kernel or custom rom this will trip knox and the knox state will be 0*1 and your warrenty will be void.
P.S: flashing firmware via odin will not trip knox
- so if you want to root without tripping knox you can go to this website : http://www.towelroot.com install apk by pressing the sign.
you will be able to root your phone quick from the phone itself but only if your phone on firmware from 3rd june or less
or your phone will not be rooted, but you can also root it by chainfire method from here: http://forum.xda-developers.com/showthread.php?t=2696537
you can also use mobile odin to flash firmwares but be carefull to be sure about your phone model.
you can install the app from playstore or from this thread: http://forum.xda-developers.com/showthread.php?t=1347899
P.S: firmwares can be downloaded from here : http://www.sammobile.com
i hope you Moderators understand me and dont get angry or close this thread because im only sharing and thought it will help my friends and the new forum members.
and at last im a member and i have the right to post what it usefull to xda community
hope that i helped.

Is is possible to use any Odin (I have 3 or 4 on my downloads) to flash stock over unlocked O2?

swipermusic said:
Is is possible to use any Odin (I have 3 or 4 on my downloads) to flash stock over unlocked O2?
Click to expand...
Click to collapse
to flash firmware you can use computer odin v3.09 and then extract the md5 file from the firmware zip and put it in AP in odin (and maybe different version of odin says PDA)

?
What about "System Status", in recovery I have a "System Status: Custom", knox 0x0 though, I'm rooted and use Xposed, what does this mean? how can I reverse it to "OFFICIAL", is this important when it comes to warranty?
THANKS! :highfive: :good: :fingers-crossed:

aguarello said:
What about "System Status", in recovery I have a "System Status: Custom", knox 0x0 though, I'm rooted and use Xposed, what does this mean? how can I reverse it to "OFFICIAL", is this important when it comes to warranty?
THANKS! :highfive: :good: :fingers-crossed:
Click to expand...
Click to collapse
well i think its not so important.
and look in settings>>about>>states
is it official or custom?

Galaxy_Guy said:
well i think its not so important.
and look in settings>>about>>states
is it official or custom?
Click to expand...
Click to collapse
Custom

aguarello said:
Custom
Click to expand...
Click to collapse
means your system has been modified and no OTA's will be available

?
wajiman said:
means your system has been modified and no OTA's will be available
Click to expand...
Click to collapse
I don't care about OTA's, but how does this impacts warranty? Can be reversed to "Official?
Thanks man I really appreciate your help.

aguarello said:
What about "System Status", in recovery I have a "System Status: Custom", knox 0x0 though, I'm rooted and use Xposed, what does this mean? how can I reverse it to "OFFICIAL", is this important when it comes to warranty?
THANKS! :highfive: :good: :fingers-crossed:
Click to expand...
Click to collapse
Use Triangle Away by chainfire, the system status will be reverted to Official.

This Thread - Fully redundant

pda4g said:
This Thread - Fully redundant
Click to expand...
Click to collapse
but its usefull for some new S5 users, its not necessary to be usefull for you.

?
Luckzao said:
Use Triangle Away by chainfire, the system status will be reverted to Official.
Click to expand...
Click to collapse
Will this be permanent or the status will be just "faked"?
thanks! :victory:

aguarello said:
Will this be permanent or the status will be just "faked"?
thanks! :victory:
Click to expand...
Click to collapse
AFAIK it will be fake, the only way to officially convert it to original is, uninstall root reboot and then reinstall root and SuperSU to user directory, not to system. This method worked for Roms prior to 3rd June.

wajiman said:
AFAIK it will be fake, the only way to officially convert it to original is, uninstall root reboot and then reinstall root and SuperSU to user directory, not to system. This method worked for Roms prior to 3rd June.
Click to expand...
Click to collapse
Ughhhh should have know that before updating and installing SuperSU to system... So no way to revert it if ROM is posterior to 3rd June? Even flashing official ROM again without root? :crying:
THANKS!

aguarello said:
Ughhhh should have know that before updating and installing SuperSU to system... So no way to revert it if ROM is posterior to 3rd June? Even flashing official ROM again without root? :crying:
THANKS!
Click to expand...
Click to collapse
Yes you can downgrade, i downgraded from NG2 to NE2 myself without problems. Just flash the NE2 rom with Odin and data factory reset afterwards. Then use TR to root again.

gee2012 said:
Yes you can downgrade, i downgraded from NG2 to NE2 myself without problems. Just flash the NE2 rom with Odin and data factory reset afterwards. Then use TR to root again.
Click to expand...
Click to collapse
Downgrade is possible without tripp knox,without problems?

AEkiz said:
Downgrade is possible without tripp knox,without problems?
Click to expand...
Click to collapse
Yes, KNOX is still 0x0 for me after the downgrade and the bootloader is downgraded to the NE2 one.

gee2012 said:
Yes, KNOX is still 0x0 for me after the downgrade and the bootloader is downgraded to the NE2 one.
Click to expand...
Click to collapse
Thanks for your reply
maybe I'll try tomorrow

gee2012 said:
Yes you can downgrade, i downgraded from NG2 to NE2 myself without problems. Just flash the NE2 rom with Odin and data factory reset afterwards. Then use TR to root again.
Click to expand...
Click to collapse
THANKS! To downgrade you just have to flash the NE2 rom? No more files? Sorry I'm kind of a noob

aguarello said:
THANKS! To downgrade you just have to flash the NE2 rom? No more files? Sorry I'm kind of a noob
Click to expand...
Click to collapse
Yes, i only flashed the older firmware without a extra PIT file or bootloader file. Make sure to untick Auto Reboot first in Odin, after the flash pull the battery, wait for 10-20 seconds, boot into recovery and do a data factory reset and then the phone should boot normal and both the firmware and bootloader are downgraded to NE2 and KNOX remains 0x0. At least it worked for me this way and i expect it to work for others the same way

Stock NG1 rom/root confusion

hey everyone couple of questions
im currently on stock nb7 with lean kernel
im getting some issues so i want to go back to scratch. ive seen on sam updates this is the latest version for BTU N9005XXUGNG1. is this the latest one?
im wondering if BTU s the correct one for me? im currently using btu and have been since ive gotten this phone. (just something id like to confirm.)
also ive seen a few threads about issues rooting NG1? this is the thread im referring to,
http://forum.xda-developers.com/galaxy-note-3/general/root-root-xxufnf4-stock-firmware-knox-t2840150.
ive already tripped knox as soon as i got this phone so im not concerned with that.
the method i know for flashing stock is,
1.open odin 3
2.connect phone (just did that and odin sees 0:com5 (so thats good)
3. click on pda and load the tar/md5 file and click start
4. to root, load cf auto root file in pda mode and click send
5. flash twrp via mobile odin
any mistakes?
edit: also and rom recommendations, i currently looking at bobcat,echoe,x-note, x-note s5 port

thedan55 said:
hey everyone couple of questions
im currently on stock nb7 with lean kernel
im getting some issues so i want to go back to scratch. ive seen on sam updates this is the latest version for BTU N9005XXUGNG1. is this the latest one?
im wondering if BTU s the correct one for me? im currently using btu and have been since ive gotten this phone. (just something id like to confirm.)
also ive seen a few threads about issues rooting NG1? this is the thread im referring to,
http://forum.xda-developers.com/galaxy-note-3/general/root-root-xxufnf4-stock-firmware-knox-t2840150.
ive already tripped knox as soon as i got this phone so im not concerned with that.
the method i know for flashing stock is,
1.open odin 3
2.connect phone (just did that and odin sees 0:com5 (so thats good)
3. click on pda and load the tar/md5 file and click start
4. to root, load cf auto root file in pda mode and click send
5. flash twrp via mobile odin
any mistakes?
edit: also and rom recommendations, i currently looking at bobcat,echoe,x-note, x-note s5 port
Click to expand...
Click to collapse
The method done in your link was to enable the use of towelroot which does not trip knox when rooting. But at the same time it does not work on new firmwares like the NG1. BTU is fine, but if you want to try other ones then there are some ROMS with multi-csc via aroma. I'm no longer into TW roms, but was on XNote v16 before, pretty good for me.
Sent from my SM-N9005

jdgamble said:
The method done in your link was to enable the use of towelroot which does not trip knox when rooting. But at the same time it does not work on new firmwares like the NG1. BTU is fine, but if you want to try other ones then there are some ROMS with multi-csc via aroma. I'm no longer into TW roms, but was on XNote v16 before, pretty good for me.
Sent from my SM-N9005
Click to expand...
Click to collapse
so to root NG1 i use odin 3 and cf auto root correct?? what rom are you currently using? whats the use of multi csc?

thedan55 said:
so to root NG1 i use odin 3 and cf auto root correct?? what rom are you currently using? whats the use of multi csc?
Click to expand...
Click to collapse
Well since you've already tripped knox then yes, cf autoroot is a go. Wait, how did you triP knox and not be rooted? Do you have custom recovery? if yes, then some ROMS come pre-rooted and can be flashed through custom recovery. I'm on Temasek CM11, rock solid stable rom. About csc, i suggest staying with your current csc which is BTU.
Sent from my SM-N9005

jdgamble said:
Well since you've already tripped knox then yes, cf autoroot is a go. Wait, how did you triP knox and not be rooted? Do you have custom recovery? if yes, then some ROMS come pre-rooted and can be flashed through custom recovery. I'm on Temasek CM11, rock solid stable rom. About csc, i suggest staying with your current csc which is BTU.
Sent from my SM-N9005
Click to expand...
Click to collapse
No I am rooted and I have a custom recovery. You mean some stock roms come pre rooted? That would be helpful. Just flash through recovery. Doesn't flashing the official stock, update more, like the bootloader etc. Would flashing a stock rooted room be the same as flashing official

thedan55 said:
No I am rooted and I have a custom recovery. You mean some stock roms come pre rooted? That would be helpful. Just flash through recovery. Doesn't flashing the official stock, update more, like the bootloader etc. Would flashing a stock rooted room be the same as flashing official
Click to expand...
Click to collapse
No, custom ROMS come pre-rooted. Flashing official from Samsung should always be done via odin. Now, flashing custom rom can be done through custom recovery or depends on the instruction of the developer.
Sent from my SM-N9005

Yeah. Thought you were talking about official. Cool thanks for the help.

[Q] Upgrading rooted SM-N9005 to 5.0 Lollipop

I have a rooted SM-N9005 with CWM recovery and unfortunately now my KNOX is tripped 0x1. I'm running the stock Samsung rom Android 4.4.2 and when I run the software update the message, "Your device has been modified. Software updates are not available" appears.
My question is when 5.0 Lollipop officially rolls out for the SM-N9005, how could I update my phone?

Very simple actually. You just need to download the full ROM from www.sammobile.com and flash it via Odin.

Thanks doublesdevil makes total sense.:good:

devilsdouble said:
Very simple actually. You just need to download the full ROM from www.sammobile.com and flash it via Odin.
Click to expand...
Click to collapse
worng he can't do anything about this just deal with this probem and forget OTA

sva260 said:
worng he can't do anything about this just deal with this probem and forget OTA
Click to expand...
Click to collapse
I guess the only downside to having Knox 0x1 is having to update manually through Odin. I bought my sim free N9005 overseas to use back in my country where my carrier doesn't offer this model of phone so I could forget about getting any warranty support anyways.