Related
Hello,
I own a galaxy s4 i 9505 (internationnal version)
I bought it with Samsung rom, modem version XXUBMGA.
now, I recently upgraded my modem, because I try some ROM like GE roms.
this is working fine.
I noticed, today, using a software to have infos about my device, and 3G signal (Signal network info) that my device has this bootloader :
I9505XXUBMGA.
it is too old (I bought it in May 2013, so the modem, boot loader etc... have more than 6 month now...
how can I update it ? where to find boot loader ? I find easily modem, but no boot loader.
thanks for any info
Olivier
re: bootloader
orobin said:
Hello,
I own a galaxy s4 i 9505 (internationnal version)
I bought it with Samsung rom, modem version XXUBMGA.
now, I recently upgraded my modem, because I try some ROM like GE roms.
this is working fine.
I noticed, today, using a software to have infos about my device, and 3G signal (Signal network info) that my device has this bootloader :
I9505XXUBMGA.
it is too old (I bought it in May 2013, so the modem, boot loader etc... have more than 6 month now...
how can I update it ? where to find boot loader ? I find easily modem, but no boot loader.
thanks for any info
Olivier
Click to expand...
Click to collapse
Why in the world would you want to "update" your bootloader?
I think it would be worth your while to read up on bootloaders
before you end up with a shiny brick with a 5 inch black screen.
Here is a good link to find out what a bootloader is and does:
http://forum.xda-developers.com/wiki/Bootloader
Bootloaders have nothing to do with the speed or the stability of the phone.
Good luck!
orobin said:
Hello,
I own a galaxy s4 i 9505 (internationnal version)
I bought it with Samsung rom, modem version XXUBMGA.
now, I recently upgraded my modem, because I try some ROM like GE roms.
this is working fine.
I noticed, today, using a software to have infos about my device, and 3G signal (Signal network info) that my device has this bootloader :
I9505XXUBMGA.
it is too old (I bought it in May 2013, so the modem, boot loader etc... have more than 6 month now...
how can I update it ? where to find boot loader ? I find easily modem, but no boot loader.
thanks for any info
Olivier
Click to expand...
Click to collapse
lol this is the first time I see someone wants a newer bootloader.. As the post above me, a newer bootloader won't make your phone faster ..Anyway you already have the latest knox one
AnaMajhol said:
lol this is the first time I see someone wants a newer bootloader.. As the post above me, a newer bootloader won't make your phone faster ..Anyway you already have the latest knox one
Click to expand...
Click to collapse
hi,
no I don't look for speed.
I was thinking that it could have some impact when trying some ROM, like :
kitkat GE Rom which are not stable, even if the rom comes i9505GE official Google edition rom which should be stable...
I was thinking that the difference between a i9505 and a i9505GE could be the bootloader, as the hardware is exactly the same...
thanks
Olivier
You are on a pre KNOX boot loader so stick with it. No need to update. Updating to a KNOX boot loader will give you a knox flag once it a tripped there's no going back. With a KNOX boot loader you can not downgrade as well. I'm on the old boot loader and custom 4.3 roms work well.
Sent from my GT-I9505 using Tapatalk
Mobile ODIN is the reason
Hello,
I have a MJ5 bootloader and to use the app Mobile ODIN I am advised to use the MJ7 version or I might soft-brick my phone...
I already have the KNOX flag at 1, so I suppose I should not worry about that... And I can't find anywhere (I did search the forum and google) how to do this.
Before anyone asks.. I have and work with OS X and I am aware of Heimdall (ODIN replacement for macs). But I tried using it and it did not recognize my phone to download my .PIT file. Also, its quite confusing about heimdall packages instead of normal files..
So, Im going for Mobile ODIN which seems to be the easiest way to ODIN.
Can anyone help? Should I worry about anything else than KNOX flag that I am not aware of when changing the bootloader?
Thanks in advance.
hi, i just got my note 3 n9005 international a couple of days ago & now its time to root...you can say i am a little new to samsung because the last device i used was an s3 & that was a long time ago.....
i dont have any warranty so knox isnt that big of a concern unless it may cause some sort of damage to the phone...so far i have read..its only for warranty purposes like the flash counter for s3.
i was wondering if anyone would be kind enough to point me to rooting & everything else i need to do to install custom roms including recovery...
i tried to read through the instructions of root de la vega but i find it too complicated...so i was thinking of doing cf auto root....
thank you
linx1287 said:
hi, i just got my note 3 n9005 international a couple of days ago & now its time to root...you can say i am a little new to samsung because the last device i used was an s3 & that was a long time ago.....
i dont have any warranty so knox isnt that big of a concern unless it may cause some sort of damage to the phone...so far i have read..its only for warranty purposes like the flash counter for s3.
i was wondering if anyone would be kind enough to point me to rooting & everything else i need to do to install custom roms including recovery...
i tried to read through the instructions of root de la vega but i find it too complicated...so i was thinking of doing cf auto root....
thank you
Click to expand...
Click to collapse
Samsung issue a 24month warranty on the Note 3 (maybe country specific?) -
If KNOX isn't an issue for you and you do not mind tripping it, the CF-Auto is the way to go.
RDLV is complicated if you're lazy, but it does preserve KNOX status depending on your bootloader version, put in #*1234# into your dial pad and post the results. We can know if you can use RDLV.
However, if you want to flash a Custom ROM, then you will need a custom recovery, which will trip your KNOX (can't be done without) - on the Android dev section and Orginal Android dev section (in this sub forum) are some Custom ROMs and the instructions on how to do so.
I have used X-Note, Crash and am currently using AllianceROM, but there are a few others.
Just be careful with custom kernels until you're pretty confident cause you can bootloop and ruin your EFS quite easily (it is fixable 99% of the time tho, script is on here also)
EDIT : All you need is here pretty much
thank you for your reply & these are the stats
AP: N9005XXUDMJ6
CP: N9005XXUDMJ4
CSC: N9005EVRDMJ4
also RDLV is way too complicated for me & besides i do plan to install a custom recovery so i think that defeats the point ....since you seem to have tripped knox, there hasnt been any kind of system issue i hope? this whole knox business gave me cold feet when i read about it...but so far as i can see..its just a flash counter.... could you tell me the tools i need to get started with? i already downloaded the usb drivers & odin 3.09..is there anything else i should need?
p.s. i was reading about "before or later MJ7 4" whatever...& i was wondering which of these was it refering to? ap? thank you
Once you trip the knox counter it makes no difference to the phone except not being able to use knox containers, and of course the warranty which you know. -- if you have the drivers and odin. Go grab cf-autoroot, run it thru odin and voila all done, similar for twrp or Cwm which ever you choose as your custom recovery (I use twrp) flash in odin and that's it all set.
Just make sure and I can't stress this enough, that you flash the right ROM for the N9005, and N900 doesn't work. - avoid doing restores with twrp for now also when you do a back up, some issues have arose recently and not sure of they're resolved or not yet.
Have fun man, just read everything about the ROM etc before you flash the odd one has FC's or NFC issues
Sent from my SM-N9005 using XDA Premium 4 mobile app
ok so backing up & restoring with recovery is, for the time being, a no no? yes i will make sure to see if the roms are made for n9005 only....i will probably start off with omega roms as they are the 1st choice i had when i started modding the s3 ....thank you soo much mate for all the info...1 last thing to clear up is i am reading on developers talking about MJ or MK or whatever it is....are they talking about the build number i find in Settings/About??
1 thing i couldnt get a proper answer for...is how does 1 know they have the international variant of the n9005 anyway? normally if a n9005 is under some sort of carrier...the carrier logo would flash when booting up right? because thats what happens on my brother's note 3 n9005...when he boots up his phone..it shows SFR logo before going to the samsung bootanimation.....but on mine there is no such thing...the simple note 3 n9005 text then samsung boot animation & then straight to system...that means mine is the unbranded 1 am i correct?
linx1287 said:
1 thing i couldnt get a proper answer for...is how does 1 know they have the international variant of the n9005 anyway? normally if a n9005 is under some sort of carrier...the carrier logo would flash when booting up right? because thats what happens on my brother's note 3 n9005...when he boots up his phone..it shows SFR logo before going to the samsung bootanimation.....but on mine there is no such thing...the simple note 3 n9005 text then samsung boot animation & then straight to system...that means mine is the unbranded 1 am i correct?
Click to expand...
Click to collapse
Yeah yours is unbranded, only thing that may/will apply to you is region lock (which unless you're leaving the country your purchased your phone in isn't an issue at the start.
Although I see your CSC is EVR (if I recall correctly that is EE UK's firmware on board)
EDIT: Yes MK/ML are build numbers
no i dont have region lock..THAT i checked...so can i go forwards with all the rooting recovery & custom roms? i did find a orange core services apk on my apps manager under ALL tab..... also what original firmware can i roll back to incase anything goes wrong? any specifics?
linx1287 said:
no i dont have region lock..THAT i checked...so can i go forwards with all the rooting recovery & custom roms? i did find a orange core services apk on my apps manager under ALL tab..... also what original firmware can i roll back to incase anything goes wrong? any specifics?
Click to expand...
Click to collapse
Yup can go forwards. EVR (EE aka Orange/T-Mobile) have unlocked phones so yeah you won't have region lock. Which means yours is unbranded but carrier unbranded.
As for firmware, it depends on what region you are using? And what country you are in (you could use BTU (also UK, unbranded but EVR is ok also) - You are **now I say this depending on your country/region** OK on MJ7 or MK2 IF you upgrade since you're using a UK based ROM/CSC your network obviously supports it. However battery life is better on lower than MJ6. So it's your choice really.
Most custom ROMs are MK2 or ML2 atm I think, - Not sure if any upgrade your bootloader to MJ7 (if they do, you can't roll back any lower currently)
i just need a stock firmware so as i have a fallback if anything goes wrong...nothing more really as i plan to stick with custom roms...will this do?
http://samsung-updates.com/details/17028/Galaxy_Note_3_Snapdragon/SM-N9005/EVR/N9005XXUDMJ6.html
i am in Bangladesh so i am pretty confident that there isnt any rom for my region
yea i was wondering about the battery life myself...i dont know what version my brother's note is but his battery lasts noticibly longer than mine does....i was even planning on swapping batteries as i thought it might be a cell related issue
linx1287 said:
i just need a stock firmware so as i have a fallback if anything goes wrong...nothing more really as i plan to stick with custom roms...will this do?
http://samsung-updates.com/details/17028/Galaxy_Note_3_Snapdragon/SM-N9005/EVR/N9005XXUDMJ6.html
i am in Bangladesh so i am pretty confident that there isnt any rom for my region
yea i was wondering about the battery life myself...i dont know what version my brother's note is but his battery lasts noticibly longer than mine does....i was even planning on swapping batteries as i thought it might be a cell related issue
Click to expand...
Click to collapse
As long as your bootloader doesn't go to MJ7 - that firmware is OK, If your bootloader updates ( I think it may with the custom ROM) you can't roll back to MJ6, you can go to MJ7 or MK2 via BTU which will work for you since EVR works.
the latest omega is ML2 so by that measure...i wont be able to roll back to MK2 either & the latest on this thread http://forum.xda-developers.com/showthread.php?t=2459328 is MK2
linx1287 said:
the latest omega is ML2 so by that measure...i wont be able to roll back to MK2 either & the latest on this thread http://forum.xda-developers.com/showthread.php?t=2459328 is MK2
Click to expand...
Click to collapse
You can drop back as far as MJ7 ( I have at least when I've returned to stock due to mess ups) my build is MK2 atm
the bootloader only goes to MJ7 (last I checked, If it has changed then mine still lets me roll to MJ7)
csc seems a very complicated mess...GOD when did the mod friendly samsung go this crazy? the s3 was the most fun thing to mod...now this feels more complicated then Sony's!! :'( since my csc is EVR...is it possible to put BTU? i saw someone post this but didnt get any replies... http://www.usofttech.com/t128991.html
OH CRAP you said this BTU already...sorry my bad.... just trying to absorb all this
1 last query & i think i can start....with my current MJ6 build...can i do the cf auto root? or do i need to be on a lower build? if i can...then i think i will start or should i wait for the MJ7 to finish downloading & root that with cf auto root? & mate...thank you... you helped clear a lot of the confusions stopping me from modding this...now i think i can start things with a bit of confidence...thank you.... MUCH appreciated
linx1287 said:
1 last query & i think i can start....with my current MJ6 build...can i do the cf auto root? or do i need to be on a lower build? if i can...then i think i will start or should i wait for the MJ7 to finish downloading & root that with cf auto root? & mate...thank you... you helped clear a lot of the confusions stopping me from modding this...now i think i can start things with a bit of confidence...thank you.... MUCH appreciated
Click to expand...
Click to collapse
You can CF root straight away, - since you're triggering KNOX anyway it won't affect you. Then on with custom recovery etc, just keep MJ7 as your stock back up on your PC just incase. and IF you run into any issues with EFS (bootloops/no signal/wifi/baseband etc) use THIS It has saved me and quite a few others.
EDIT: And no problem man, glad to help, we all start somewhere with new devices
mate....the odin inside the cf root is 1.85 & the 1 got from google is 3.09 which should i use? & is PDA & AP the same thing because they are diff in the 2 versions of odin
linx1287 said:
mate....the odin inside the cf root is 1.85 & the 1 got from google is 3.09 which should i use? & is PDA & AP the same thing because they are diff in the 2 versions of odin
Click to expand...
Click to collapse
I use 3.07 personally - and flash using PDA -- Use the one with CF root if you're unsure
the phone is rooted ahhh feels like home again ....mate you said earlier that restoring backups on twrp causes system issues....i was wondering if this is true for just twrp or ALL current recoveries in general? which recovery would you suggest? also i was wondering about that script you told me about...the 1 about soft brick.... that fixes corrupt efs due to flashes yes? if so, does that mean it doesnt require my backup of efs?
linx1287 said:
the phone is rooted ahhh feels like home again ....mate you said earlier that restoring backups on twrp causes system issues....i was wondering if this is true for just twrp or ALL current recoveries in general? which recovery would you suggest? also i was wondering about that script you told me about...the 1 about soft brick.... that fixes corrupt efs due to flashes yes? if so, does that mean it doesnt require my backup of efs?
Click to expand...
Click to collapse
TWRP has issues *sometimes* there's a few posts about it around, I personally have had no problems and use TWRP fine, but I mentioned it because what works for one, doesn't always for another.
As for EFS backup, keep it just incase -- IT seems Android can rebuild the EFS again with that fire script. -- It's handy though, gotten a few out of the crapper including myself
First of all, I'm not interested in actually going from 4.4.2 to 4.3, I just want to understand why it is only possible on the N900W8.
So, if I get it right, when you update to android 4.4.2 you also flash the new bootloader, which doesn't allow you to go back to the old one and is not compatible with android 4.3. Which makes me wonder:
Why doesn't 4.4.2 work with the older bootloader?
Why doesn't 4.3 work with the newer bootloader?
Since I have root, why I can't just overwrite the new bootloader with the old? Is that particular partition/block/whatever of the eMMC write-protected or the part of the bootloader that needs updating is not on the eMMC?
Why the N900W8 can be downgraded?
dp_alvarez said:
First of all, I'm not interested in actually going from 4.4.2 to 4.3, I just want to understand why it is only possible on the N900W8.
So, if I get it right, when you update to android 4.4.2 you also flash the new bootloader, which doesn't allow you to go back to the old one and is not compatible with android 4.3. Which makes me wonder:
Why doesn't 4.4.2 work with the older bootloader?
Why doesn't 4.3 work with the newer bootloader?
Since I have root, why I can't just overwrite the new bootloader with the old? Is that particular partition/block/whatever of the eMMC write-protected or the part of the bootloader that needs updating is not on the eMMC?
Why the N900W8 can be downgraded?
Click to expand...
Click to collapse
Try Google and XDA search for getting more info on your questions
dp_alvarez said:
First of all, I'm not interested in actually going from 4.4.2 to 4.3, I just want to understand why it is only possible on the N900W8.
So, if I get it right, when you update to android 4.4.2 you also flash the new bootloader, which doesn't allow you to go back to the old one and is not compatible with android 4.3. Which makes me wonder:
Why doesn't 4.4.2 work with the older bootloader?
Why doesn't 4.3 work with the newer bootloader?
Since I have root, why I can't just overwrite the new bootloader with the old? Is that particular partition/block/whatever of the eMMC write-protected or the part of the bootloader that needs updating is not on the eMMC?
Why the N900W8 can be downgraded?
Click to expand...
Click to collapse
You need to read around in the threads related to knox and development probably starting here:
http://forum.xda-developers.com/showthread.php?t=2642207
but as a huge summary of things:
- the boot sequence is secure in all high-end Samsung phones, meaning not any code can be just booted; the bootloader itself is the part most restricted; restrictions are not necessarily identical between Exynos and Qualcomm versions but the idea is the same, the parts of the bootloader must be all cryptographically signed (or similar)
- apparently there are some special version-related restrictions added on top of that by Samsung - the goal is of course to provide a secure environment where knox security is enforced (and can not be circumvented by downgrading to a previous version with a known security bug) and enterprise customers that pay heavy money for that security know that their data is not easy to extract from a phone
- yes, certain parts of EMMC are write-protected before the code-flow leaves the secure bootloader sequence; those regions can only be written from bootloader code (Odin, or maybe some regions could be written from stock recovery, but it must be stock - I think that problem is seen when writing modem files for instance in Mobile Odin Pro).
gee2012 said:
Try Google and XDA search for getting more info on your questions
Click to expand...
Click to collapse
I did, but didn't find any answers. Lots of people trying to downgrade, to flash older bootloaders, etc but nothing explaining what changed as to make 4.4.2 require a new bootloader or why that bootloader is incompatible with 4.3.
Maybe I've been using the wrong terms in my searches, or I'm searching in the wrong place. If you got any link that explains what happened (or points me on where to find that info), please do share it.
xclub_101 said:
You need to read around in the threads related to knox and development probably starting here:
http://forum.xda-developers.com/showthread.php?t=2642207
but as a huge summary of things:
- the boot sequence is secure in all high-end Samsung phones, meaning not any code can be just booted; the bootloader itself is the part most restricted; restrictions are not necessarily identical between Exynos and Qualcomm versions but the idea is the same, the parts of the bootloader must be all cryptographically signed (or similar)
- apparently there are some special version-related restrictions added on top of that by Samsung - the goal is of course to provide a secure environment where knox security is enforced (and can not be circumvented by downgrading to a previous version with a known security bug) and enterprise customers that pay heavy money for that security know that their data is not easy to extract from a phone
- yes, certain parts of EMMC are write-protected before the code-flow leaves the secure bootloader sequence; those regions can only be written from bootloader code (Odin, or maybe some regions could be written from stock recovery, but it must be stock - I think that problem is seen when writing modem files for instance in Mobile Odin Pro).
Click to expand...
Click to collapse
Thanks for the link, I started reading that topic but did not find out what made 4.4.2 incompatible with the older bootloader. Will read the full thread and also the other threads in the development section, thanks.
But, in short, the incompatibility of 4.4.2 is because the samsung bootloader explicitly refuses to load 4.4.2, or some changes in 4.4.2 made it incompatible with the previous boot process? If it is the later, then all devices that were updated to 4.4.2 also had to update their bootloaders, right?
Also, even with the security checks it loads a kernel that isn't necessarily signed right? Then isn't it possible to patch the 4.4.2 kernel to be compatible with the boot process of 4.3 and/or to report like 4.3 so it runs with the older bootloader?
dp_alvarez said:
...
But, in short, the incompatibility of 4.4.2 is because the samsung bootloader explicitly refuses to load 4.4.2, or some changes in 4.4.2 made it incompatible with the previous boot process? If it is the later, then all devices that were updated to 4.4.2 also had to update their bootloaders, right?
Also, even with the security checks it loads a kernel that isn't necessarily signed right? Then isn't it possible to patch the 4.4.2 kernel to be compatible with the boot process of 4.3 and/or to report like 4.3 so it runs with the older bootloader?
Click to expand...
Click to collapse
It IS an incompatibility created on purpose. And yes, all "normal" (N900, N9005) devices that were updated to 4.4.2 have updated bootloaders (the exception is N900W8 and maybe some of the other carrier-specific devices that have bootloaders controlled by themselves and not by Samsung). However there is one extra element - the bootloader itself can not be downgraded since there is 'somewhere' a list that actively prevents that.
On top of that you have the knox warranty flag - each time a kernel or recovery that is not signed is detected that flag is set.
downgrade from 4.4.2 to 4.3
I have note 3 verizon,, I can odin back to 4.3 from 4.4.2,, I have done it several times. Not sure if this is true for all note 3's
ronschuck said:
I have note 3 verizon,, I can odin back to 4.3 from 4.4.2,, I have done it several times. Not sure if this is true for all note 3's
Click to expand...
Click to collapse
'Tis not true for all Note 3s.
xclub_101 said:
It IS an incompatibility created on purpose. And yes, all "normal" (N900, N9005) devices that were updated to 4.4.2 have updated bootloaders (the exception is N900W8 and maybe some of the other carrier-specific devices that have bootloaders controlled by themselves and not by Samsung). However there is one extra element - the bootloader itself can not be downgraded since there is 'somewhere' a list that actively prevents that.
On top of that you have the knox warranty flag - each time a kernel or recovery that is not signed is detected that flag is set.
Click to expand...
Click to collapse
Thanks, I'm starting to understand it a little better now.
Now just one more question if you are still patient enough to put up my quesetions: Why can't we install the 4.4.2 kernel and chainload the 4.3 kernel from there?
I promise I will read better the development threads before I ask questions like these again
dp_alvarez said:
Thanks, I'm starting to understand it a little better now.
Now just one more question if you are still patient enough to put up my quesetions: Why can't we install the 4.4.2 kernel and chainload the 4.3 kernel from there?
I promise I will read better the development threads before I ask questions like these again
Click to expand...
Click to collapse
Hmm, that should be something "doable" as long as you have root in the primary 4.4.2 boot environment, probably that could work in a safestrap-like approach (as long as the Samsung 4.4.2 kernel does not specifically prohibit that somehow, which i doubt). Eventually look after the safestrap threads and ask there.
ronschuck said:
I have note 3 verizon,, I can odin back to 4.3 from 4.4.2,, I have done it several times. Not sure if this is true for all note 3's
Click to expand...
Click to collapse
Are you saying you can odin back to Jellybean from the OTA updated kitkat firmware?
I'd love to see this, can you write up a quick howto? Lots and lots of people would be very thankful for this if it's true...
No not if you take the OTA update,, sorry if I mislead.. I was speaking of running a NC2 rom which is 4.4.2 and then odin back to 4.3..
Hey Guys,
I am a proud owner of a new S5 and I am no root newby as I had any other android devices before.
I read that it was possible to downgrade to 4.2 ANE2 Bootloader in order to root with Towelroot, so I might not trigger KNOX
But I read that the ne Models of the S5 have a locked bootloader, so a downgrade to ANE2 is not possible anymore.
Is this strill true?
I would love to see my Phone rooted but if its not possilble (its still in my package lol) I would rather send it back and decide for another phone -.- since I would like to keep my warranty intact.
Appreciate any answers
Regards!
the first thing when you ask put max information about your phone lol y know s5 have many series 900f 900h 900a and ....
Yup, need the model S5 first, then we can check if it can be rooted or not
Hey
it is 900f sorry I did not mention!
HustleberryFinn said:
Hey
it is 900f sorry I did not mention!
Click to expand...
Click to collapse
Flash this with ODIN
http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
If that doesn't work, flash TWRP 2.8.7.0 with ODIN, then flash SuperSu.zip from TWRP recovery
As I said in my beginning post. I would like to have my warranty intact, so I guess rooting with CF Auto Root is not the best Idea, isn't it? (It triggers KNOX)
My Problem is simply, that I would like to know if a downgrade to an earlier bootloader is still possible if the device is delivered with Android 5.0.
You are describing the procedure for towelrooting......flashing an older kernel, using Towelroot and then re - flashing your original kernel. This has worked for many people (myself included) who were on KitKat before they rooted.......
You are on lollipop, this method won't work for you as flashing a KK kernel onto a lollipop firmware will more than likely make the phone unbootable. .....meaning you won't be able to use towelroot at all.
If you want rooted lollipop and knox at 0x0, you'll have to downgrade the entire firmware to KK, towelroot it and use Flashfire to return to your original but root injected lollipop firmware.
http://i.imgur.com/rVnFwJM.jpg
Rooting brand new s5 lollipop
Sorry if this a seems to be noob question (but i did not find any answer nowhere).
I want to root my S5 kltexx (G900F) through Odin3_v3.10.7 with TWRP.tar + UPDATE-SuperSU-v2.46.
Q:
What the difference between them (excepting date of publication and version)?:
- openrecovery-twrp-2.8.4.0-klte.tar
- openrecovery-twrp-2.8.4.0-gt-klte.tar
- twrp-2.8.7.0-klte.img
Which should i use?
Thanks in advance for answer.
triceraptor said:
Sorry if this a seems to be noob question (but i did not find any answer nowhere).
I want to root my S5 kltexx (G900F) through Odin3_v3.10.7 with TWRP.tar + UPDATE-SuperSU-v2.46.
Q:
What the difference between them (excepting date of publication and version)?:
- openrecovery-twrp-2.8.4.0-klte.tar
- openrecovery-twrp-2.8.4.0-gt-klte.tar
- twrp-2.8.7.0-klte.img
Which should i use?
Thanks in advance for answer.
Click to expand...
Click to collapse
lol install the last release if you want to be sure no bug with latest custom roms
@triceraptor The 2.8.7.0 seems to be the only version of TWRP that works with some Lollipop firmwares too......
The 'img' file you quoted won't work with odin....you need the .tar version.
Also, make sure re-activation lock is off before you start......otherwise this WILL interfere with the flash.
You *should* be able to find it under....
Settings>>Security......
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
You are describing the procedure for towelrooting......flashing an older kernel, using Towelroot and then re - flashing your original kernel. This has worked for many people (myself included) who were on KitKat before they rooted.......
You are on lollipop, this method won't work for you as flashing a KK kernel onto a lollipop firmware will more than likely make the phone unbootable. .....meaning you won't be able to use towelroot at all.
If you want rooted lollipop and knox at 0x0, you'll have to downgrade the entire firmware to KK, towelroot it and use Flashfire to return to your original but root injected lollipop firmware.
Click to expand...
Click to collapse
Hey! Thanks for your post!
My problem is, that it is mentioned that you cannot fully downgrade to KK because the new Devices with Lolli have a locked bootloader. And with that, downgrading to an older KK OS will not do anything because with a modern bootloader its not possible to use towlroot.
So my original intention was simply to find out if it is true - Do the new devices have a locked loader or not.
If your option works, I am glad to try it out, but with a locked loader your advice seems kind of complicated.
To the best of my knowledge. locked bootloaders are carrier specific......
AT&T and (I believe) Verizon are the primary culprits.....There may be 'enhanced security' on newer bootloaders/firmware, but that's a separate issue. If your device is the 'F' variant, which is used mainly in Europe and the UK, a locked bootloader shouldn't be an issue.....It *might* be necessary to flash a .pit file simultaneously to the downgrade though, just to make sure that *every* trace of the LP firmware is removed (this isn't required every time, but is there as an option if needed).
However you play it, it would be best to keep checking to see that re-activation lock is disabled, as this will only lead to issues if it becomes enabled.
http://i.imgur.com/rVnFwJM.jpg
HustleberryFinn said:
Hey! Thanks for your post!
My problem is, that it is mentioned that you cannot fully downgrade to KK because the new Devices with Lolli have a locked bootloader. And with that, downgrading to an older KK OS will not do anything because with a modern bootloader its not possible to use towlroot.
So my original intention was simply to find out if it is true - Do the new devices have a locked loader or not.
If your option works, I am glad to try it out, but with a locked loader your advice seems kind of complicated.
Click to expand...
Click to collapse
I agree with Kieth. I was 90% sure it was carrier specific. You could use the towel root method, but I have rooted my phone the Cf way, and already get 0x1 so there is no point for me. You should be able to flash an older firmware. Then just reset all data and reboot good as old.
Sent from my SM-G900W8 using Tapatalk
keithross39 said:
To the best of my knowledge. locked bootloaders are carrier specific......
AT&T and (I believe) Verizon are the primary culprits.....There may be 'enhanced security' on newer bootloaders/firmware, but that's a separate issue. If your device is the 'F' variant, which is used mainly in Europe and the UK, a locked bootloader shouldn't be an issue.....It *might* be necessary to flash a .pit file simultaneously to the downgrade though, just to make sure that *every* trace of the LP firmware is removed (this isn't required every time, but is there as an option if needed).
However you play it, it would be best to keep checking to see that re-activation lock is disabled, as this will only lead to issues if it becomes enabled.
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Hey! Thanks again!
So I tried to downgrade but my screen of my new 900f stays totally black after downgrading.
I found a thread with the same problems - btw u participated in it as well- http://forum.xda-developers.com/galaxy-s5/help/custom-recovery-protection-samsung-t3135004/page8
Do you know any solutions for it? I would really like to use the towlroot method
Did you downgrade with or without pit?
As I mentioned in my earlier reply, the pit will erase EVERY trace of the old firmware from the device. Just make sure you get the CORRECT pit as flashing the wrong pit has the *potential* to permanently brick your device.
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Did you downgrade with or without pit?
As I mentioned in my earlier reply, the pit will erase EVERY trace of the old firmware from the device. Just make sure you get the CORRECT pit as flashing the wrong pit has the *potential* to permanently brick your device.
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
I haven't tried it with a PIT file yet, but ins on my schedule for tomorrow!
Just in Case - I search for tutorials right now - do I have to flash the pit simultaneously or is there any special order I have to do it?
With all my past devices I never had to put so much effort for a root -.-"
Lol.....newer device = bigger headache.
Yes the pit is flashed simultaneously....
Load it into odin as a file with pit extension (kinda obvious that one lol) and then load the firmware tar.....and flash.
Can't stress this enough though.......
MAKE SURE YOU GET THE CORRECT PIT.....
Good luck fella....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Lol.....newer device = bigger headache.
Yes the pit is flashed simultaneously....
Load it into odin as a file with pit extension (kinda obvious that one lol) and then load the firmware tar.....and flash.
Can't stress this enough though.......
MAKE SURE YOU GET THE CORRECT PIT.....
Good luck fella....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Got some time the last hour. With the pit file - worked perfectly and rooted! Knox 0x0.
Thank you very much for your effort!
Glad I could help fella......
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Glad I could help fella......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Hey! Same problem again. I had to send the device with the working downgrade back, because the mic was defect -.-
Now I tried to do the Same stuff with PIT file, but this time the Phone screen stays black
(Downgrade to ANE with Pit file. No Samsung Logo and nothing...have to geht to the Downgrad Menu blind in order to Flash the old 5.0 LP OS. Then it works again)
Do you have and other advices for me?
Hi Guys,
New to this device, but not new to Android... Read all over the web, various sites (esp this one) about this device and seeing mixed views/comments. Some saying its possible, others saying it will brick or flag the Knox.
Is it possible to downgrade this phone (G900F) currently on the latest 6.0.1 stock rom. But was wondering if I could try either official stock of 4.4.2 or 5.1.1 of this device.
Or due to this bootloader, is it likely to brick or even trip Knox?
Thanks, Lister
Lister Of Smeg said:
Hi Guys,
New to this device, but not new to Android... Read all over the web, various sites (esp this one) about this device and seeing mixed views/comments. Some saying its possible, others saying it will brick or flag the Knox.
Is it possible to downgrade this phone (G900F) currently on the latest 6.0.1 stock rom. But was wondering if I could try either official stock of 4.4.2 or 5.1.1 of this device.
Or due to this bootloader, is it likely to brick or even trip Knox?
Thanks, Lister
Click to expand...
Click to collapse
Official stock ROMs shouldn't trip Knox because they are, ummm, official.
I think the G900F bootloader is unlocked.
Sent from my Samsung SM-G900I using XDA Labs
Why downgrade in the first place..... ? 6.0.1 is way better than previous FWs...
Hi @Dirty Flasher,
Yeah, that's what I thought... It's all stock, so all should be good... But I've read reports saying it will trip Knox as since a certain version of Marshmallow, the bootloader has been locked to only go with future firmwares and not allow downgrades. I assume to prevent people restoring to the older firmware (with bootloader) which was unlocked, that allowed rooting without tripping. But some say it will trip, others say it will not... I'm confused, and wondered if anyone has tried this, and what the outcome was... Don't want to trip Knox unnecessarily... if someone has already tried and tested it.
Dirty Flasher said:
Official stock ROMs shouldn't trip Knox because they are, ummm, official.
I think the G900F bootloader is unlocked.
Sent from my Samsung SM-G900I using XDA Labs
Click to expand...
Click to collapse
Hi @Zlate2255,
I got this device when it was already one 6.0.1, so I missed seeing it go through the various stages. I would like to see how it used to look like and work. As there are some features that have been removed since, such Face Unlock and Iris tracking when viewing pages. Whilst the latter is still there burried away, it barely works, so should be removed completely. But would just be nice to see what it did look like.
Zlate2255 said:
Why downgrade in the first place..... ? 6.0.1 is way better than previous FWs...
Click to expand...
Click to collapse
Thanks, Lister
With my G900W8, I could downgrade to 4.4.2 with very-first firmware for G900W8 (NCG). Just try the earliest version of 4.4.2 and then upgrade back to 5.1.1
You can downgrade the g900f to every firmware (if unlocked) you want. On some s5 devices who have a locked bootloader like the at&t version there have been reported some problems.
Therefore, you shouldn't run into any problems while downgrading.
If you want some pro and cons to the firmwares:
Kitkat:
+ dark design (the touchwiz apps like contacts)
+ more battery friendly than marshmallow
- less security due to no security updates
- you might run into some minimal bugs, for example on wikipedia you sometimes have to reload the page to watch pictures (at least on mine)
- no app permissions can be removed (only with root and app ops)
Lollipop:
Honestly, I havent used this one that much, but here you have a white design with the different statusbar and pull down menu, better security (but not as good as on marshmallow) and the material design, but slightly worse battery time.
Marshmallow:
+ OTA Updates still available, best option for security
+/- White design, material design
+ new icons (but tbh not a real deal)
- less battery friendly (atleast for me even tho doze is enabled on marshmallow)
So yeah, choose what you want
And be sure that you have an unbranded device (check your csc) before downgrading/updating.
Hi @tm60405,
Wow, what a fantastic post... Thank you, exactly what I was looking for, and thanks for your reviews of each rom too.
- appreciate that, cheers
Quick question, how do I know if my Bootloader is unlocked??
Its a G900F (UK) was originally on the Three network, however I've flashed it to pure stock BTU, and to the EE network and back to stock BTU (all Marshmallow roms).
So where am I looking, or how do I know if the Bootloader is unlocked? Also, what am I looking for in the CSC info...??
Many thanks, Lister
Install the app called phone info from the play store.
Then, you swipe to the csc code and you can see your info and remember the csc you are on.
If it is BTU, you can install another firmware based on BTU without problems. But even if you don't have BTU, you can try installing BTU because it doesn't contain much bloatware. In the worst case, you just install the firmware with the csc you had before.
Then, follow the instructions on sammobile.com and there will be no problems during the installing process.
After downgrading, you might get a bootloop. Then, you have to factory reset your device, so get the data from the internal storage elsewhere BEFORE the installation.
And if the download takes too long, try another browser like opera, for me it takes around 1 hour only instead of 4-5 hours on chrome.
If you might have another problem while installing the firmware, say so.