Difference between model number and about device - Galaxy S 5 Q&A, Help & Troubleshooting

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

Related

Brand new N9005 Root Question without tripping Knox flag

hi,
i got my n9005 (quad core, 32gb, sadly simlocked[provider]) today.
Yet i did not do anything to it, not even boot it.
I don't wanna screw anything up for later.
I want to make a complete backup of it and root it without tripping knox flag.
I read about auto root from chainfire but since that trips knox flag i cannot choose that.
Then I came across Root de la Vega from designgears and chainfire that does not trip knox flag
but as i understand it, it will not work on n9005 since i dont see my device being mentioned,
so what choice do i have now?
Can I power on the device now anyways just to ota or would that be bad (before a complete backup)?
Thanks
Please help me out here
You need to establish what firmware version you have first, take a look in the settings, what version off firmware do you have?
RavenY2K3 said:
You need to establish what firmware version you have first, take a look in the settings, what version off firmware do you have?
Click to expand...
Click to collapse
Austria (A1) 2013 September 4.3 N9005XXUBMI7 N9005VFGBMI1
Baseband N9005XXUBMI6
Even if i can root with URdlV 0.2, can i still remove provider simlock without tripping knox?
Somehow i get the impression i might be better off chainfireing it with autoroot after i flashed official unlocked german stock 4.3 over the current os. Triangleaway might come out in the next months so i can undo the knox trigger. Otherwise i might wait ages until i can use this phone...cos of the provider sim lock..
Thx
Do NOT update FW if you going to RDLV. MJ3 has new locked bootloader so you have to root first, then modify update FW.
Odinary carrier sim lock doesn't matter..
Read RDLV thread carefully again..
Sim lock has nothing to do with FW as long it's from same region and not special carrier locked bootloader
Sent from my SM-N9005 using Tapatalk
Ok, i will not update stock fw!
Why doesn't provider lock matter and what bootloader do i have? I read everyone writing mj3 blabla but where do u actually see what i got.
My stock fw was 4.3 when i got the phone and i never changed anything
cassinni said:
Ok, i will not update stock fw!
Why doesn't provider lock matter and what bootloader do i have? I read everyone writing mj3 blabla but where do u actually see what i got.
My stock fw was 4.3 when i got the phone and i never changed anything
Click to expand...
Click to collapse
Every Note 3 firmware is 4.3 until 4.4 kitkat arrives.
Find out your fw by settings/general/about phone, bottom line. If it has not .....MJ3, .....MJ6, ......MJ7 yet, your bootloader is not locked and you can RDLV.
If you're not gonna use the knox program, go for CF-autoroot instead.
Edit. Didn't see yor post above you said XXUBMI7. Do not update yet couse you have an early fw and can use RDLV
You clearly have some reading to do about firmwares and rooting etc..
Sent from my SM-N9005 using Tapatalk
Yea, its weird cos it says MI and nowhere mJ but everyone mentions it.
What about the provider lock?
Where can i read up on all that important info and esp. The No-No's?
cassinni said:
Yea, its weird cos it says MI and nowhere mJ but everyone mentions it.
What about the provider lock?
Where can i read up on all that important info and esp. The No-No's?
Click to expand...
Click to collapse
?? ...MI7 is your current fw. Newer update fw's: ....MJ3-7, you can download from sammobile.com and flash manually by software "Odin" later after if you wish to root.
If not rooted, you can get these updates OTA.
Read the RDLV thread to learn about that rooting method first. Search around in Note 3 forums for answers.
Sim-lock has nothing to do with this at all. You can not unlock sim by rooting.
You can remove sim lock if you buy special dial code at some web sites. You give them your IMEI and pay them for the unlocking code. Thats all I know about that.
Sent from my SM-N9005 using Tapatalk

[Q] flash a newer firmware via odin

Hi
I would like to know whether flashing a newer official firmware downloaded from sammobile would trip the KNOX warranty void?
The reason I'm asking is that I want to change my device's CSC code. Since it's not rooted or anything, I don't know any other ways of changing the code.
edit
no, it wouldnt. also, didnt find a way to change csc except rooting
http://forum.xda-developers.com/showthread.php?t=2565758
http://www.w0lfdroid.com/2013/12/Safe-Root-Android-4.3-Galaxy-S3-S4-Note-No-Warranty-Void.html
PS, mods can delete the thread.

[Q] Software Update for my S5 (SM-G900F)

Hello there!
I need your help to be sure about some things.
(Oh! Sorry for my bad English, not my native language)
I have a Galaxy S5, I bought this with my country operator. The latest software for the SM-G900F model released by my operator is G900FXXU1ANCE.
I read that Samsung has updated the software with some better and this update is G900FXXU1ANE2.
My questions are:
1) If I download the G900FXXU1ANE2 version and install via ODIN, you modify a 0x1 Knox void warranty? Or is maintained in 0x0?
2) If I install G900FXXU1ANE2 and sometime I go to claim warranty, could reinstall the G900FXXU1ANCE version? Ie make downgrade. Or this could change me knox void warranty?
Thanks in advance for your answers.
gevensa said:
Hello there!
I need your help to be sure about some things.
(Oh! Sorry for my bad English, not my native language)
I have a Galaxy S5, I bought this with my country operator. The latest software for the SM-G900F model released by my operator is G900FXXU1ANCE.
I read that Samsung has updated the software with some better and this update is G900FXXU1ANE2.
My questions are:
1) If I download the G900FXXU1ANE2 version and install via ODIN, you modify a 0x1 Knox void warranty? Or is maintained in 0x0?
2) If I install G900FXXU1ANE2 and sometime I go to claim warranty, could reinstall the G900FXXU1ANCE version? Ie make downgrade. Or this could change me knox void warranty?
Thanks in advance for your answers.
Click to expand...
Click to collapse
First of all flashing official firmware with Odin will NEVER trip KNOX. Don`t know if you can flash an older rom, if the bootloader is the same it should be possible, just try it mate and if it should fail you reflash the rom you have now. You can flash any compatible rom with Odin, also the ones that are not for your region.
gevensa said:
1) If I download the G900FXXU1ANE2 version and install via ODIN, you modify a 0x1 Knox void warranty? Or is maintained in 0x0?
2) If I install G900FXXU1ANE2 and sometime I go to claim warranty, could reinstall the G900FXXU1ANCE version? Ie make downgrade. Or this could change me knox void warranty?
Click to expand...
Click to collapse
Installing this update should not change the Knox bit. It should remain at 0x0 in this situation. Flashing stock firmware will not normally change Knox, although if you try installing a pre KitKat firmware e.g. 4.2.1, may corrupt the bootloader and increment the Knox counter. A power interruption during the flash process may also trip Knox. More commonly, installing a custom kernel or recovery will also trip the Knox counter.
You should be able to revert or downgrade to the earlier firmware in your example. And that won't affect your warranty (or be necessary for warranty purposes). Note though that you cannot downgrade all firmware versions. For example, Samsung introduced the Knox DRM in 4.3 and don't want you downgrading to remove it, consequently you cannot downgrade from 4.3 to 4.2.x (or earlier).
Thanks for your answers.
Another question: I have csc CRM What if I install the csc PHE, I will receive in the future the OTAs to release in Spain?
Sent from my SM-G900F using XDA Free mobile app
gee2012 said:
First of all flashing official firmware with Odin will NEVER trip KNOX. Don`t know if you can flash an older rom, if the bootloader is the same it should be possible, just try it mate and if it should fail you reflash the rom you have now. You can flash any compatible rom with Odin, also the ones that are not for your region.
Click to expand...
Click to collapse
fffft said:
Installing this update should not change the Knox bit. It should remain at 0x0 in this situation. Flashing stock firmware will not normally change Knox, although if you try installing a pre KitKat firmware e.g. 4.2.1, may corrupt the bootloader and increment the Knox counter. A power interruption during the flash process may also trip Knox. More commonly, installing a custom kernel or recovery will also trip the Knox counter.
You should be able to revert or downgrade to the earlier firmware in your example. And that won't affect your warranty (or be necessary for warranty purposes). Note though that you cannot downgrade all firmware versions. For example, Samsung introduced the Knox DRM in 4.3 and don't want you downgrading to remove it, consequently you cannot downgrade from 4.3 to 4.2.x (or earlier).
Click to expand...
Click to collapse
Thanks for your answers!!
Sent from my SM-G900F using XDA
Free mobile app
gee2012 said:
...
You can flash any compatible rom with Odin, also the ones that are not for your region.
Click to expand...
Click to collapse
Well, i tried to flash a PHN firmware once but it failed at hidden.img.ext4 with "FAIL! (size)".
So there are some exceptions =/
my stock firmware said:
Model: SM-G900F
Model name: GALAXY S5
Country: Czech Republic
Version: Android 4.4.2
Changelist: 1539356
Build date: Thu, 08 May 2014 03:44:41 +0000
Product Code: ETL
PDA: G900FXXU1ANE2
CSC: G900FETL1AND3
MODEM: G900FXXU1ANE2
Click to expand...
Click to collapse
born4trance said:
Well, i tried to flash a PHN firmware once but it failed at hidden.img.ext4 with "FAIL! (size)".
So there are some exceptions =/
Click to expand...
Click to collapse
Where is your device from, if i may ask? Is it a Dutch device or imported?
I ordered mine from a dutch webshop (i'm also dutch btw) who import their devices from EU countries.
born4trance said:
I ordered mine from a dutch webshop (i'm also dutch btw) who import their devices from EU countries.
Click to expand...
Click to collapse
Yup, saw that. So you can`t flash a Dutch PHN rom to your device? Strange as it its a EU device as you say Have you tried a German DBT rom?
gee2012 said:
Yup, saw that. So you can`t flash a Dutch PHN rom to your device? Strange as it its a EU device as you say Have you tried a German DBT rom?
Click to expand...
Click to collapse
Everything flashes fine, until it encounters hidden.img.ext4
I haven't looked at other firmwares yet but i did notice that the mentioned file's filesize differed from the PHN .tar one.
Its a shame that there are so many differences amongst the same model.
born4trance said:
Correct > FAIL! (Size) @ hidden.img.ext4
I haven't looked at other firmwares yet but i did notice that the file in question differed from the one inside the PHN .tar
Click to expand...
Click to collapse
What software version do you have now annd what is your CSC file? In the dialpad type *#1234#.
gee2012 said:
What software version do you have now annd what is your CSC file? In the dialpad type *#1234#.
Click to expand...
Click to collapse
I already quoted the firmware i (currently) have, a few posts back
born4trance said:
I already quoted the firmware i (currently) have, a few posts back
Click to expand...
Click to collapse
Sorry for not reading that Usualy it shouldn`t be a problem to flash a different European rom. I got my phone with a TNL (T-Mobile) rom and flashed a PHN rom and it wasn`t a problem for me. I`ll try flashing a DBT rom just to see if it works.
gee2012 said:
Sorry for not reading that Usualy it shouldn`t be a problem to flash a different European rom. I got my phone with a TNL (T-Mobile) rom and flashed a PHN rom and it wasn`t a problem for me. I`ll try flashing a DBT rom just to see if it works.
Click to expand...
Click to collapse
Perhaps it will work for you but not for me Í'm not sure if or when i'll flash another FW, i don't really want to lose/give up towelroot :angel:
gevensa said:
Another question: I have csc CRM What if I install the csc PHE, I will receive in the future the OTAs to release in SpaIn?
Click to expand...
Click to collapse
An OTA update will check your CSC to see if the update should be applied to your system. If you change your CSC from AAA to BBB, you can't expect to receive OTA's for AAA any longer. If your intent in doing this is wanting to receive BBB updates, the CSC change will usually suffice. It's a carrier implementation though and a more conservative carrier could also do secondary checks such as matching the baseband CSC as well.
Also you shouldn't change a CSC unless you are confident that the BBB OTA is compatible with your current firmware.
.
---------- Post added at 11:06 PM ---------- Previous post was at 10:17 PM ----------
born4trance said:
Well, i tried to flash a PHN firmware once but it failed at hidden.img.ext4 with "FAIL! (size)".
So there are some exceptions =/
Click to expand...
Click to collapse
That doesn't surprise me at all. As I said earlier, you cannot expect to flash any firmware with Odin. It is dismaying how many people state that you can do so when they don't really know that to be true. Or to be more precise, they think they know and want to help someone. But in fact, they don't understand the subject in any depth, have no reasonable basis to believe that they do and good intentions notwithstanding, do a real disservice by spreading dangerously inaccurate information.
To reiterate, you cannot flash any file with Odin. Someone who tells you that you can flash any carrier's S5 firmware onto your S5 is demonstrably wrong. It will work in some cases and they are making a bad assumption that because it worked in one case that it can be universally done. As you found out firsthand, that is not true. Someone who assumes it is universally true and further presents that unfounded assertion as fact isn't exercising sound judgement.
This is an oversimplification, but to give you a rough idea of what is going on.. hidden.img.ext4 contains carrier specific information. And it is partitioned. So if you flash a firmware from another carrier and it happens to be formatted as a larger partition, the flash will corrupt the partition structure, leading to the Odin error writing to hidden.img.ex4 and soft brick your phone.
Long story short, don't blindly believe everyone that makes authoratative statements about what you can safely do. Try to understand the process as much as possible yourself, so that you can spot the worst inconsistencies. And look for a sense of how deep and consistent someone's knowledge of a subject is before taking their advice.
To recover after flashing an incompatible flash from another carrier, you would ideally flash a stock copy of hidden.img.ext4 and the PIT from the original carrier. If you don't care aout Knox, flashing CWM will typically resolve the issue as well. Also if you understand partitioning structures, better informed users can discern in advance if a carrier x firmware can be safely flashed or not.
.
fffft said:
That doesn't surprise me at all. As I said earlier, you cannot expect to flash any firmware with Odin. It is dismaying how many people state that you can do so when they don't really know that to be true. Or to be more precise, they think they know and want to help someone. But in fact, they don't understand the subject in any depth, have no reasonable basis to believe that they do and good intentions notwithstanding, do a real disservice by spreading dangerously inaccurate information.
To reiterate, you cannot flash any file with Odin. Someone who tells you that you can flash any carrier's S5 firmware onto your S5 is demonstrably wrong. It will work in some cases and they are making a bad assumption that because it worked in one case that it can be universally done. As you found out firsthand, that is not true. Someone who assumes it is universally true and further presents that unfounded assertion as fact isn't exercising sound judgement.
This is an oversimplification, but to give you a rough idea of what is going on.. hidden.img.ext4 contains carrier specific information. And it is partitioned. So if you flash a firmware from another carrier and it happens to be formatted as a larger partition, the flash will corrupt the partition structure, leading to the Odin error writing to hidden.img.ex4 and soft brick your phone.
Long story short, don't blindly believe everyone that makes authoratative statements about what you can safely do. Try to understand the process as much as possible yourself, so that you can spot the worst inconsistencies. And look for a sense of how deep and consistent someone's knowledge of a subject is before taking their advice.
To recover after flashing an incompatible flash from another carrier, you would ideally flash a stock copy of hidden.img.ext4 and the PIT from the original carrier. If you don't care out Knox, flashing CWM will typically resolve the issue as well. Also if you understand partitioning structures, better informed users can discern in advance if a carrier x firmware can be safely flashed or not.
Click to expand...
Click to collapse
Wow.. and wow (+thanks )
So (long story short): besides flashing CWM/TWRP/Philz i could flash a .pit from a 16GB S5 (of the same model) that comes with a PHN firmware, and then flash the PHN firmware itself and retain 0x0
born4trance said:
So (long story short): besides flashing CWM/TWRP/Philz i could flash a .pit from a 16GB S5 that has a PHN firmware on it (and retain 0x0)
Click to expand...
Click to collapse
Flashing a custom recovery would increment Knox to 0x1. But it should remain 0x0 if you use the proper PIT corresponding to the new stock firmware. I haven't tested that (as I don't really care about Knox personally) but I don't see any logical reason that Knox would be concerned with that scenario, nor heard of any reports of it happening to anyone.
PHN.. is Netherlands? So assuming that you have say, a 16 GB SM-G900F, you should be able to flash a 900F PHN firmware successfully and safely if you do so in conjunction with a PIT file for a 16 GB PHN 900F. I presume that the flash won't trip Knox either but I have not actually done so personally.
Theoretically the write could still fail on an aboot auth failure but I haven't seen any evidence that carriers are locking down their bootloaders that tightly and don't think that would be a likely impediment.
.
fffft said:
PHN.. is Netherands?
Click to expand...
Click to collapse
Correct: For non branded / SIM-lock free
fffft said:
So assuming that you have say, a 16 GB SM-G900F, you should be able to flash a 900F PHN firmware successfully and safely if you do so in conjunction with a PIT file for a 16 GB PHN 900F. I presume that the flash won't trip Knox either but I have not actually done so personally.
Click to expand...
Click to collapse
I indeed own a SM-G900F and its also important to mention that the partition layout differs between 16GB/32GB models
Now to get ahold of the correct .pit (still looking)

Need help with downgrade (Galaxy S4 GT-I9515)

Hello,
I am sorry if I'm posting this in a wrong section or something. As stated in tittle i need to downgrade Lollipop to Kitkat 4.4.2 but i need your help finding the right firmware since I'm doing this for the first time. I've red some guides and i think i will manage to do it properly once I've found the right firmware. Anyway here are some details (if you need me to provide additional information please ask):
AP: I9515XXU1BOC3
CP: I9515XXU1BOC3
CSC: I9515AUT1BOC1
Model number: GT-I9515
Baseband version I9515XXU1BOC3
Build number LRX22C.I9515XXU1BOC3
Thank you in advance,
Milos
Is this phone unlocked? Who is your carrier? What country are you in?
Strephon Alkhalikoi said:
Is this phone unlocked? Who is your carrier? What country are you in?
Click to expand...
Click to collapse
I live in Montenegro and the phone is unlocked.
Look here. As your phone is unlocked, you're not limited to a specific firmware. Pick one and download it, though I'd recommend staying away from the ones that have carrier names in parenthesis.
Strephon Alkhalikoi said:
As your phone is unlocked, you're not limited to a specific firmware. Pick one and download it, though I'd recommend staying away from the ones that have carrier names in parenthesis.
Click to expand...
Click to collapse
Will this one work? (Since I'm new it won't allow me to post links)
Model: GT-I9515
Model name: GALAXY S4 VE
Country: Switzerland
Version: Android 4.4.2
Changelist 2882604
Build date Fri, 26 Sep 2014 08:59:00
Product code : AUT
PDA : I9515XXU1ANI3
CSC: I9515AUT1ANJ1
That should work fine.
Strephon Alkhalikoi said:
That should work fine.
Click to expand...
Click to collapse
Everything went smoothly. Thanks a lot man!
Sorry if I sound noobish, but mine isn't rooted yet...
I do however want to downgrade my phone back to kit kat.
Does any of you know if there already is a new root method?
For the I9515, CF-AutoRoot is the only root method that works, as the old tutorials in the forum that mentioned using Towelroot required using versions of Android your device never had, i.e. Android 4.2.2. Therefore, while you can downgrade to 4.4.2 it's not going to help you root without tripping Knox.
So if I'm reading you correctly, CF-autoroot is the only method for root without tripping Knox?
nick1524 said:
So if I'm reading you correctly, CF-autoroot is the only method for root without tripping Knox?
Click to expand...
Click to collapse
yes, that's correct except you would be capable and doing all on your own JK
nick1524 said:
So if I'm reading you correctly, CF-autoroot is the only method for root without tripping Knox?
Click to expand...
Click to collapse
CF-AutoRoot trips Knox as it temporarily installs a custom recovery to deliver its payload.
Great...
So I have to choose to either learn to live with lollipop or to accept
that I will lose my warranty.
That's the last time for me to install an update without checking it out first
The update isn't at fault here, because on the I9515 only two versions of Android are available (4.4.2 and 5.x) and Towelroot doesn't work on either of them. So, your choices are even simpler. You either can root and possibly void your warranty*, or don't root and use the device as is.
*Depending on location, you may or may not lose your warranty. Some countries do not permit warranties to be voided because of software modifications, so you want to check this out for yourself.
Strephon Alkhalikoi said:
The update isn't at fault here, because on the I9515 only two versions of Android are available (4.4.2 and 5.x) and Towelroot doesn't work on either of them. So, your choices are even simpler. You either can root and possibly void your warranty*, or don't root and use the device as is.
*Depending on location, you may or may not lose your warranty. Some countries do not permit warranties to be voided because of software modifications, so you want to check this out for yourself.
Click to expand...
Click to collapse
If I may correct a little bit. Towelroot works on some version of 4.4.2. It was "fixed" in the newer versions of 4.4.2.
nick1524 said:
Great...
So I have to choose to either learn to live with lollipop or to accept
that I will lose my warranty.
That's the last time for me to install an update without checking it out first
Click to expand...
Click to collapse
Use this for reference:
http://forum.xda-developers.com/galaxy-s4/help/how-to-root-samsung-galaxy-s4-i9515-t2863400
According to this poster, the firmware you suggested (I9515XXU1ANI3) works with towelroot.
http://forum.xda-developers.com/gal...pping-knox-t2887705/post56847621#post56847621
ps why do you assume you need root for downgrade? Because you don't.
@Lennyz1988: Feel free to correct, as more people chiming in can only help.
I honestly didn't know about Towelroot being updated, but then again I haven't had a need to catch up on the Towelroot-related threads since my device already had a tripped Knox when I purchased it.
Phone locked or not.
How can i check that my phone is unlocked or not?

S5 from kitkat to lolipop info

hi guys my name is mike i have S5 G900F model with stock 4.4.2 kitkat rooted with towelroot method Knox (0x0)
if i flashed with stock rom again to lolipop i lost root ? if yes can u tell me other way to do it without tripped know of course
ty in advance
nwmn said:
hi guys my name is mike i have S5 G900F model with stock 4.4.2 kitkat rooted with towelroot method Knox (0x0)
if i flashed with stock rom again to lolipop i lost root ? if yes can u tell me other way to do it without tripped know of course
ty in advance
Click to expand...
Click to collapse
Hi Mike, search the forums before asking any questions. Search google. Don't expect everyone to do your job for you. Post your threads in the right section. This question has been asked and answered a million times and you'd know this if you took 5 minutes to search a little bit.
Here's your answer https://www.reddit.com/r/galaxys5/comments/2ubsbs/guide_rooted_android_50_for_the_international/
out of curiosity, why dont you want to trip knox flag
"This question has been asked a million times and you'd know this if you took 5 minutes of your precious time to search a little bit."
Ironic for a man that follows people around *****ing at them to post in Q&A
Sorry guys i have spend many hours on forums to find a anwser but i dont find anything thanx for time anyways the link give me lingo is not exactly what i want i ask if can upgrader via odin in last lolipop stock filmware without loosing root exackly the way i do downgrade and other question is i have unlocked bootloader ? how can find that
i dont want void knox cuz phone is new
nwmn said:
Sorry guys i have spend many hours on forums to find a anwser but i dont find anything thanx for time anyways the link give me lingo is not exactly what i want i ask if can upgrader via odin in last lolipop stock filmware without loosing root exackly the way i do downgrade and other question is i have unlocked bootloader ? how can find that
i dont want void knox cuz phone is new
Click to expand...
Click to collapse
What model do you have? Find out in phone settings in system / phone info. Sm-g900a has locked bootloader. I think verizon's phone also has a locked bootloader.
The link I gave you shows how to upgrade to lollipop, root it and keep knox 0x0.
Isn't that what you're looking for?
lingowistico said:
What model do you have? Find out in phone settings in system / phone info. Sm-g900a has locked bootloader. I think verizon's phone also has a locked bootloader.
The link I gave you shows how to upgrade to lollipop, root it and keep knox 0x0.
Isn't that what you're looking for?
Click to expand...
Click to collapse
i have G900F i think i write it in first post , anyway well that i looking for but not exactly i wanna know if g900f have unlocking bootloader or how can find it and if i upgrade stock rom from kitkat to lolipop i lost root without change modem or anything else downgrade was easy my s5 was braned vodafone germany i download stock rom from samsung mobile and i made unbrand greece whymi must flash modem and why i must use moblile odin that is some questions turture me ty for ur time
ps. always i must put image verification to post this change after 10 post ?
nwmn said:
i have G900F i think i write it in first post , anyway well that i looking for but not exactly i wanna know if g900f have unlocking bootloader or how can find it and if i upgrade stock rom from kitkat to lolipop i lost root without change modem or anything else downgrade was easy my s5 was braned vodafone germany i download stock rom from samsung mobile and i made unbrand greece whymi must flash modem and why i must use moblile odin that is some questions turture me ty for ur time
ps. always i must put image verification to post this change after 10 post ?
Click to expand...
Click to collapse
my bad, you did. 900f has an unlocked bootloader. when you upgrade to stock lollipop through OTA or Kies (or odin) it already includes bootloader and modem. When you do it the way described in that reddit link you flash the lollipop firmware, modem and bootloader separately. Apparently that method of updating needs it to be done so.
Honestly I have Knox 0x1 so I never cared for those methods, btw if you live in Germany then there's no need to care about Knox. In EU we're allowed to flash whatever we want and the guarantee stays intact even if you have Knox 0x1
ps. yes =p
lingowistico said:
my bad, you did. 900f has an unlocked bootloader. when you upgrade to stock lollipop through OTA or Kies (or odin) it already includes bootloader and modem. When you do it the way described in that reddit link you flash the lollipop firmware, modem and bootloader separately. Apparently that method of updating needs it to be done so.
Honestly I have Knox 0x1 so I never cared for those methods, btw if you live in Germany then there's no need to care about Knox. In EU we're allowed to flash whatever we want and the guarantee stays intact even if you have Knox 0x1
ps. yes =p
Click to expand...
Click to collapse
thats is awesome news u r sure bootloader is unlock with all G900F models?
two more questions ty for your petions
1)i still have OTA if upgrade with SuperSU survival mode to last lolipop i keep root/data?
2)if upgrade with odin last lolipop i keep root/data?
nwmn said:
thats is awesome news u r sure bootloader is unlock with all G900F models?
two more questions ty for your petions
1)i still have OTA if upgrade with SuperSU survival mode to last lolipop i keep root/data?
2)if upgrade with odin last lolipop i keep root/data?
Click to expand...
Click to collapse
Honestly, I don't know. That reddit link I gave you, I haven't read the guide myself. I just skimmed though it to be sure it was real but I don't know the details of it. Yes all G900Fs have an unlocked bootloader. :good:
nwmn said:
thats is awesome news u r sure bootloader is unlock with all G900F models?
two more questions ty for your petions
1)i still have OTA if upgrade with SuperSU survival mode to last lolipop i keep root/data?
2)if upgrade with odin last lolipop i keep root/data?
Click to expand...
Click to collapse
Do you mean ota stock firmware notification? If yes then you will have it if Knox is still 0x0 if Knox however is 0x1 you will no longer be able to update via ota.
If you want to upgrade from KitKat to lollipop you must wipe data from recovery to avoid any issues. It is also not recommended by me to use titanium backup to restore apps because some might not be compatible with lollipop yet or some of the app data made for KitKat may have a conflict with lollipop system, however lots of apps have compatibility with lollipop and there is a chance you will have no issues at all when using titanium backup. Even if I said I don't recommend restoring data after such a major upgrade I do recommend having a backup whether it's with titanium backup or nandroid etc because you're able to restore apps one by one and make sure that what you restore won't be problematic.
Edit - if you update with flashfire app, there is an option to keep root when flashing from rooted KitKat to lollipop and users have reported that that feature does work for them (I personally haven't tried it).
Sent from my SM-G900F using Tapatalk
Here's a version of the method on XDA
http://forum.xda-developers.com/gal...2nd-method-t2843044/post54719865#post54719865

Categories

Resources