Hi,
I've just bought a new M919 device.
Now, it seems like the bootloader is locked..
is there is any unlock known right now?
also, i've already flashed i9505 rom into it, and had to flash m919 kernel.
if i get it right,it is becuase the bootloader is asking from the kernel "load m919 device" and if it's not supported the device won't load.
so generally, with an unlocked bootloader, will i be able to flash i9505 device and use i9505 kernels as well?
because the hardware should be the same..
Edit:
it will be good to mention that i'm not living inside the USA, and i don't have tmobile vendor here..
so "loosing" tmobile bloatware or lte support is not something i care..
M1919'z dont have locked bootloaders only att and Verizon....
Gotta be something ur flashing....
Dont mean to be rude at all but u better be carefull what u flash on that fone with other firmware....
Need more info... whats rom u on? N whats ur end goal? U flash the wrong thing and BAM BRICK :banghead:
Sent from my SGH-M919 using xda app-developers app
DxCx said:
Hi,
I've just bought a new M919 device.
Now, it seems like the bootloader is locked..
is there is any unlock known right now?
also, i've already flashed i9505 rom into it, and had to flash m919 kernel.
if i get it right,it is becuase the bootloader is asking from the kernel "load m919 device" and if it's not supported the device won't load.
so generally, with an unlocked bootloader, will i be able to flash i9505 device and use i9505 kernels as well?
because the hardware should be the same..
Edit:
it will be good to mention that i'm not living inside the USA, and i don't have tmobile vendor here..
so "loosing" tmobile bloatware or lte support is not something i care..
Click to expand...
Click to collapse
I have a guide for that...better READ first. In my sig.
re: bootloader
DxCx said:
Hi,
I've just bought a new M919 device.
Now, it seems like the bootloader is locked..
is there is any unlock known right now?
also, i've already flashed i9505 rom into it, and had to flash m919 kernel.
if i get it right,it is becuase the bootloader is asking from the kernel "load m919 device" and if it's not supported the device won't load.
so generally, with an unlocked bootloader, will i be able to flash i9505 device and use i9505 kernels as well?
because the hardware should be the same..
Edit:
it will be good to mention that i'm not living inside the USA, and i don't have tmobile vendor here..
so "loosing" tmobile bloatware or lte support is not something i care..
Click to expand...
Click to collapse
The bootloader is not locked on a Tmobile M919 S3, what we do have is a root restricted kernel.
Your best bet before doing anything else is to flash the Deviant kernel which is unrestricted or any
other custom kernel for the M919.
Here is the link for the deviant kernel: http://d-h.st/X0b
Good luck!
Ok,
So first of all, i might be confusing you, i do have some technical knowledge, and what i did is:
Restore the device (Using Odin) to "M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar"
then flashed CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar to gain root, and openrecovery-twrp-2.5.0.1-jfltexx-i9505 to gain recovery.
Next (After the system loaded) i've copied the files:
I9505_Omega_v3.1_XXUAME2
and
KT-SGS4-TW-JB-TMO-06-06-2013
And in recovery i've flashed them.
so i have Omega 3.1 for I9505 with TMO's kernel.
About the bootloader, when i'm in download mode, it says:
"Write Protection: Enable" i tought it means it is locked bootloader..
what i would like to really achive is to run a FULLY i9505 code on the hardware
which means also i9505 bootloader and kernel..
re: odin flash
DxCx said:
Ok,
So first of all, i might be confusing you, i do have some technical knowledge, and what i did is:
Restore the device (Using Odin) to "M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar"
then flashed CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar to gain root, and openrecovery-twrp-2.5.0.1-jfltexx-i9505 to gain recovery.
Next (After the system loaded) i've copied the files:
I9505_Omega_v3.1_XXUAME2
and
KT-SGS4-TW-JB-TMO-06-06-2013
And in recovery i've flashed them.
so i have Omega 3.1 for I9505 with TMO's kernel.
About the bootloader, when i'm in download mode, it says:
"Write Protection: Enable" i tought it means it is locked bootloader..
what i would like to really achive is to run a FULLY i9505 code on the hardware
which means also i9505 bootloader and kernel..
Click to expand...
Click to collapse
You cannot odin flash the i9505 firmware to a Tmobile S4 M919 phone.
Most likely if you would have odin flashed that firmware you would have ended up with a shiny brick.
Never try odin flashing any other device's firmware to your M919 S4 phone.
Only flash the appropriate and compatible cwm/twrp flashable custom roms.
Good luck!
Thanks for your quick reply ,
i did not get why you've said i can brick my device with the FW i've flashed with odin,
I've flashed the M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME which is for the M919 phone..
Also,
do you know what that "Write Protection: Enable" means in download mode?
do you know if replacing the bootloader (in the future when available) will give me the option to use i9505 kernels?
or i'm doomed to use M919 bootloader & Kernel for forever..?
re: odin flash
DxCx said:
Thanks for your quick reply ,
i did not get why you've said i can brick my device with the FW i've flashed with odin,
I've flashed the M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME which is for the M919 phone..
Also,
do you know what that "Write Protection: Enable" means in download mode?
do you know if replacing the bootloader (in the future when available) will give me the option to use i9505 kernels?
or i'm doomed to use M919 bootloader & Kernel for forever..?
Click to expand...
Click to collapse
What I said was never flash any other device's "Odin" flashable firmware to a M919 Galalxy S4 phone.
(other devices include the international i9505 S4 phone)
The Odin flashable M919UVUAMDL firmware is perfectly safe to flash if your device is the Tmobile M919 S4 phone.
There are some i9505 custom roms which are "NOT" Odin flashable and require CWM/TWRP to flash.
Those cwm/twrp zip file roms can be safely flashed to a M919 S4 phone but you will loose wifi calling.
There are many custom kernels in these M919 S4 Tmobile threads which you can choose from and flash
if you are not satisfied with the default kernels which all of the cwm/twrp flashable zip file roms come with.
As far as bootloaders go, if your phone is working properly there is no reason or advantages in flashing any bootloaders.
Flashing bootloaders can be a sure way to brick your phone. If it gets bricked you will have to ship it off to be Jtag'ed. ($35-$60)
Flashing different bootloaders have nothing to do with improving your phone's performance in any way.
It seems that you're trying to make your M919 into a i9505. If you wanted an i9505, you should have gotten an i9505 to begin with. What made you choose a M919 when you're not in the US and don't care about LTE or T-Mobile bloatware? I'm on AT&T service but got a M919 because of unlocked bootloader. I'm on stock T-Mobile ROM but with TWRP recovery and rooted and also got rig of all of the T-Mobile and Samsung bloat. I'm still able to to use AT&T's HSPA and LTE network. That's the beauty of using a M919 on an AT&T network.
Auctly i had a week in USA, and i couldn't find any i9505 only the carriers..
the m919 was the lowest i've found for 680$..
in my country, buying the --i9500-- will cost around 990$
so.. so this is the reason i got the m919..
i would like to "turn it" to be as i9505 as possible..
and i do have some experience in the embedded area,
all i was asking is what "Write Protect: Enable" Means if that's not a locked bootloader.
and if it's not locked, why flashing i9505 bootloader & kernel would not work (since as far as i understand from earlier reading the hardware are the same)..
Also, am i able to flash i9505 modems? or i'm restricted to m919 modems as well?
re: bootloaders
DxCx said:
Auctly i had a week in USA, and i couldn't find any i9505 only the carriers..
the m919 was the lowest i've found for 680$..
in my country, buying the --i9500-- will cost around 990$
so.. so this is the reason i got the m919..
i would like to "turn it" to be as i9505 as possible..
and i do have some experience in the embedded area,
all i was asking is what "Write Protect: Enable" Means if that's not a locked bootloader.
and if it's not locked, why flashing i9505 bootloader & kernel would not work (since as far as i understand from earlier reading the hardware are the same)..
Also, am i able to flash i9505 modems? or i'm restricted to m919 modems as well?
Click to expand...
Click to collapse
The i9505 phones with the original MDM firmware do not have Write Protection: Enabled.
The i9505 phones with MDM firmware released in May 2013 will have Write Protection: Enabled
The i9505 phones that have been upgraded using OTA to ME2 firmware will
have the bootloader updated and will have Write Protection: Enabled.
Hope this helps,
Misterjunky said:
The i9505 phones with the original MDM firmware do not have Write Protection: Enabled.
The i9505 phones with MDM firmware released in May 2013 will have Write Protection: Enabled
The i9505 phones that have been upgraded using OTA to ME2 firmware will
have the bootloader updated and will have Write Protection: Enabled.
Hope this helps,
Click to expand...
Click to collapse
Thanks alot, so since i bought my phone after May 2013 i have this write protection..
can you give me more info about this protection? is that just ro flag on some partitions on the eMMC (such as boot i guess) ?
is that what is called locked bootloader? i had like 5 android phones before and never seen this..
re: bootloaders
DxCx said:
Thanks alot, so since i bought my phone after May 2013 i have this write protection..
can you give me more info about this protection? is that just ro flag on some partitions on the eMMC (such as boot i guess) ?
is that what is called locked bootloader? i had like 5 android phones before and never seen this..
Click to expand...
Click to collapse
If I recall correctly, a locked bootloader prevents the flashing of any AOSP/AOKP/CM10/MIUI roms because
they require cm10/aosp/aokp/miui kernels, they will not work with stock or stock based kernels or any other
custom kernels unless they are specifically designed for those Cyanogen type roms..
However you can flash most any cwm/twrp flashable custom rom which is based on stock Tmobile M919
Touchwiz Jellybean 2.2 MDB or MDL roms. All the the kernels for these roms are based on the stock rom.
Misterjunky said:
If I recall correctly, a locked bootloader prevents the flashing of any AOSP/AOKP/CM10/MIUI roms because
they require cm10/aosp/aokp/miui kernels, they will not work with stock or stock based kernels or any other
custom kernels unless they are specifically designed for those Cyanogen type roms..
However you can flash most any cwm/twrp flashable custom rom which is based on stock Tmobile M919
Touchwiz Jellybean 2.2 MDB or MDL roms. All the the kernels for these roms are based on the stock rom.
Click to expand...
Click to collapse
Hmm, i've already flashed AOKP on the phone and it worked (with M919 kernel),
but this write protect does mean "locked bootloader"?
what i think, is that the lock is just on the "boot.img" sector of the emmc.
so we are not able to switch the bootloader.
and the bootloader set deviceId for the kernel for the m919.
so the kernel must be compiled with m919 machine-id..
P.S
i do have some knowledge in embedded linux and linux kernel.
that's the reason i want to understand what they are locking
do you know the name of the bootloader? is that u-boot? or some other developed by Samsung?
DxCx said:
Hmm, i've already flashed AOKP on the phone and it worked (with M919 kernel),
but this write protect does mean "locked bootloader"?
what i think, is that the lock is just on the "boot.img" sector of the emmc.
so we are not able to switch the bootloader.
and the bootloader set deviceId for the kernel for the m919.
so the kernel must be compiled with m919 machine-id..
P.S
i do have some knowledge in embedded linux and linux kernel.
that's the reason i want to understand what they are locking
do you know the name of the bootloader? is that u-boot? or some other developed by Samsung?
Click to expand...
Click to collapse
Also, i did not understand if i can switch my modem''s to any i9505 modem or not .. ?
DxCx said:
Also, i did not understand if i can switch my modem''s to any i9505 modem or not .. ?
Click to expand...
Click to collapse
The guy could never answer your question about the write protection and what it means whether or not it means bootloader is locked. I understand what you're saying. Just like with the HTC phone lines they say s-on and has locked in the fastbbot screen which means it's a locked bootloader. The question here is, does the write protection on the tmobile s4 m919 mean a locked bootloader. With the HTC s-off means you can flash other HTC model numbers specificity the HTC one series. With an unlocked bootloader you can have a tmobile phone and flash an AT&T custom rom. I think the write protection on the s4 m919 means bootloader locked because I've tried different custom roms and get the status 7 errors. I can only flash m919 and cyanogen custom roms only. So to me the write protection means locked bootloader, until someone can confirm different and answer the write protection question correctly.
Getting status 7 errors when flashing a custom ROM could mean that the recovery is outdated or the phone is not supported by the custom ROM. A good way to check would be to examine the updater script in the custom ROM to ensure that the phone's model can be flashed.
Related
re 7100 bootloaders
(please forgive my lack of knowledge)
i am on phoenix 17 rom currently, bootloader MJ5 (no knox as far as i understand. later bootloaders ie MK4 are knoxed IIRC)
am I understanding correctly that custom roms do not install bootloaders (ie 4.3 roms or 4.4 based on stock or leaked stock)?
and that is why it is possible to still revert backwards if one has a non knoxed BL?
do stock roms install bootloaders (via kies or odin)?
so if for some reason i installed a stock 4.3 i would then be stuck with a knoxed bootloader?
thanks for the info
entdoc said:
am I understanding correctly that custom roms do not install bootloaders (ie 4.3 roms or 4.4 based on stock or leaked stock)?
and that is why it is possible to still revert backwards if one has a non knoxed BL?
do stock roms install bootloaders (via kies or odin)?
so if for some reason i installed a stock 4.3 i would then be stuck with a knoxed bootloader?
thanks for the info
Click to expand...
Click to collapse
-Custom Roms does NOT include bootloaders(as far as I know). I'm still in MJ5 BL even after installing DN3 4 Kitkat.
-Yup, i believe you can still revert back if you want to, as long as the bootloader does NOT have knox.
-It depends with what version you will install. Be informed by the "bootloader version" of the 4.3 stock rom that you will install(visible in sammobile). As long as the included bootloader is lower than MJ5(and NOT MK4 onwards) everything will be fine, I hope.
Hope I help. ^.^
erljayp said:
-Custom Roms does NOT include bootloaders(as far as I know). I'm still in MJ5 BL even after installing DN3 4 Kitkat.
-Yup, i believe you can still revert back if you want to, as long as the bootloader does NOT have knox.
-It depends with what version you will install. Be informed by the "bootloader version" of the 4.3 stock rom that you will install(visible in sammobile). As long as the included bootloader is lower than MJ5(and NOT MK4 onwards) everything will be fine, I hope.
Hope I help. ^.^
Click to expand...
Click to collapse
where is bootloader version listed in sammobile details i see PDA CSC MODEM
also are any stock sammy roms available without bootloader (new ones)
if not is there a way to install a stock rom without the newer bootloader (can the necessary files EXCEPT the bootloader be extracted out of the .tar files and somehow be installed
thanks
Is it possible to install a stock ROM once 4.3 and a locked bootloader is in place. I've looked all over and I seem to read conflicting stories. So...
I have a Samsung S3 Telus (AT&T) version running the latest 4.3 as of May1st, my bootloader is locked and I have a tripped flash counter.
If someone actually posts a I747MVLUEND2 rooted image can I flash it?
Can I flash an older version I747MVLUEM series?
Oh yeah my phone is NOT rooted.
Check post #5, 11, 27 here Guide: How I unlocked my ATT S3 [ 1 2 3 ... Last ]
Thread By: Jasonator
I think you didn't understand the question. You pointed me to a thread about unlocking.
With a 4.3 bootloader, you will need to install a custom recovery to flash ROMs. If you want to restore a stock 4.3 ROM, try this: http://forum.xda-developers.com/showthread.php?t=2658486
With a 4.3 bootloader, you cannot use Odin to flash a stock ROM unless that ROM was specifically compiled for flashing via Odin.
No this is not possible. I have a LOCKED boot loader. I can't flash a custom recovery as far as I know.
Also how would one know a ROM is made to be flashed by Odin even if it was possible? Maybe I missed something here.
I re-read your original post and I'm a bit confused. You have a Telus s3 (i747m) or AT&T s3 (i747)?
I have never heard of an s3 having a locked bootloader. All of the phones with a stock 4.3 ROM have a bootloader that cannot be downgraded.
audit13 said:
I re-read your original post and I'm a bit confused. You have a Telus s3 (i747m) or AT&T s3 (i747)?
I have never heard of an s3 having a locked bootloader. All of the phones with a stock 4.3 ROM have a bootloader that cannot be downgraded.
Click to expand...
Click to collapse
Sorry, I have a Telus I747M.
It seems all AT&T and Telus S3's have a locked boot loader after the upgrade to 4.3. This means you cannot flash CWM recovery to the phone anymore.
So, I beleive I can't fix it to put CWM recovery on but I may be able to flash a stock rom, I'm just not sure at this point what I can do. Based on your response it is not surprising I'm confused, there seems to be a LOT of conflicting information.
There are some stock ROMS that have already been rooted and I'm hoping I can flash one of those without bricking my phone.
horga_83 said:
Sorry, I have a Telus I747M.
It seems all AT&T and Telus S3's have a locked boot loader after the upgrade to 4.3. This means you cannot flash CWM recovery to the phone anymore.
So, I beleive I can't fix it to put CWM recovery on but I may be able to flash a stock rom, I'm just not sure at this point what I can do. Based on your response it is not surprising I'm confused, there seems to be a LOT of conflicting information.
There are some stock ROMS that have already been rooted and I'm hoping I can flash one of those without bricking my phone.
Click to expand...
Click to collapse
sir, the one who got the wrong idea is you
the only S3 with locked bootloader is the verizon version
i747/M doesn't regardless of which version
which occurs to me that you might have done something wrong trying to root your device
though i've never tried this tool to root but many people succeeded rooting their phone with this http://forum.xda-developers.com/showthread.php?t=1963790
so try it out
but again, you said to flash a stock rom... you can do it via Kies(is that how it is called? it had been so long since i last used it) or you can just use ODIN to flash it
Regardless of the subject of that thread, the posts I indicated directly speak to your 747m downgrade question.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
horga_83 said:
Sorry, I have a Telus I747M.
It seems all AT&T and Telus S3's have a locked boot loader after the upgrade to 4.3. This means you cannot flash CWM recovery to the phone anymore.
So, I beleive I can't fix it to put CWM recovery on but I may be able to flash a stock rom, I'm just not sure at this point what I can do. Based on your response it is not surprising I'm confused, there seems to be a LOT of conflicting information.
There are some stock ROMS that have already been rooted and I'm hoping I can flash one of those without bricking my phone.
Click to expand...
Click to collapse
Can understand why some may be confused about the question. If you have stock 4.3 already (which is the latest version available), why would you want to flash another stock ROM? If you are talking about flashing an older stock ROM, yes it is possible, and there have been several posts on how you can successfully downgrade the system only without altering the bootloader. Attempting to downgrade the bootloader will, of course, cause a brick so downgrading ROM only is a rather complicated process that should be attempted only if there is a very worthwhile reason for this. So far, there are very few arguments, if any, for downgrading from 4.3 to any older stock ROM version. If you are trying to flash a rooted version of the same stock, you need to be sure it's one with the same bootloader. You may, however, find it easier simply keeping the current system and rooting via Safe Root. You can, however, flash a custom ROM if it won't attempt to mess with your bootloader . As far as recovery goes, even if you have stock 4.3, you can still flash custom recovery via Odin or other prescribed installation route. I'm not aware of 4.3 preventing the flashing of a custom recovery. I have an AT&T i747 with stock 4.3 and I've flashed custom recovery several times.
pcshano said:
sir, the one who got the wrong idea is you
the only S3 with locked bootloader is the verizon version
i747/M doesn't regardless of which version
which occurs to me that you might have done something wrong trying to root your device
though i've never tried this tool to root but many people succeeded rooting their phone with this http://forum.xda-developers.com/showthread.php?t=1963790
so try it out
but again, you said to flash a stock rom... you can do it via Kies(is that how it is called? it had been so long since i last used it) or you can just use ODIN to flash it
Click to expand...
Click to collapse
So when my bootloader says Qualcomm secure boot = 1, that means what exactly?
I haven't tried to root my phone yet.
Well actually it's a stock ROM that has been rooted. As per this page:
http://forum.xda-developers.com/showthread.php?t=1739426&__utma=248941774.1179961654.1399404439.1400082744.1400099749.11&__utmb=248941774.1.10.1400099749&__utmc=248941774&__utmx=-&__utmz=248941774.1400099749.11.3.utmcsr=forum.xda-developers.com|utmccn=%28referral%29|utmcmd=referral|utmcct=/galaxy-s3-att/&__utmv=-&__utmk=261245838
horga_83 said:
So when my bootloader says Qualcomm secure boot = 1, that means what exactly?
I haven't tried to root my phone yet.
Well actually it's a stock ROM that has been rooted. As per this page:
http://forum.xda-developers.com/showthread.php?t=1739426&__utma=248941774.1179961654.1399404439.1400082744.1400099749.11&__utmb=248941774.1.10.1400099749&__utmc=248941774&__utmx=-&__utmz=248941774.1400099749.11.3.utmcsr=forum.xda-developers.com|utmccn=%28referral%29|utmcmd=referral|utmcct=/galaxy-s3-att/&__utmv=-&__utmk=261245838
Click to expand...
Click to collapse
I think that means secure booting has been enabled. Secure booting has nothing to do with having a locked bootloader. From what I have read in other forums, a locked bootload would not allow you to load a custom kernel.
I unlock both my Koodo SGH-I747M by following the instructions (just by punching a bunch of codes) from one of those YT video and I've been using T-Mobile's prepaid service since.
http://forum.xda-developers.com/galaxy-s3/general/american-canadian-sgs3-read-flashing-t1757755
Since the specs are all the same for SGH-I747M (AT&T/Telus/Bells/Koodo/Rogers) + my phones are unlock, does that mean I can flash both my phones with Kit-Kat (once released) by any of these carriers (AT&T/Telus/Bells/Koodo/Rogers)?
Thanks.
p/s currently still on the original 4.1.1
I would not do it as att and koodo use different bootloaders and modems.
audit13 said:
I would not do it as att and koodo use different bootloaders and modems.
Click to expand...
Click to collapse
Glad I asked first, thanks for the reply and it makes sense :good:.
Personally, I would avoid knox as most custom KK ROMs will work fine with the 4.1.2 bootloader. I would only upgrade the bootloader if it was required for a ROM I really wanted to use.
Your unlock means nothing to the ability to install a ROM or not.
Now, you can install the Samsung ported Sprint Kitkat ROM for AT&T if you update your bootloader and modem to the MK5 version and never use ODIN or try to downgrade your bootloader ever again ! This ROM will not work without the MK5 bootloader and modem. If you proceed that way, your warranty will be void
Also, you can always flash Koodo builds
If you wish to keep your current bootloader, you can always install any of the non samsung ROMs, but some will require that you have the MF1 bootloader at the least (CM for example).
So I'm confused, is there an official Kitkat for the UK note 2? I have looked on Sam mobile , and do not see a UK version. If I put on the France Version, will the Modem need changing for best reception? Is there a fool proof Root and de -Knox available?
Thanks
wilx said:
So I'm confused, is there an official Kitkat for the UK note 2? I have looked on Sam mobile , and do not see a UK version. If I put on the France Version, will the Modem need changing for best reception? Is there a fool proof Root and de -Knox available?
Thanks
Click to expand...
Click to collapse
No de-knox available.Are you still under warranty?
Deknox is available for roms. Not for bootloaders. So, if you aren't already on a knoxed bootloader and want to stay that way do not flash anything stock 4.3+ through odin. I'm not sure of the specifics with the n7100, but with the n7105 4.3+ kernels do not work with 4.1.2 bootloaders (no network) so a custom one is required. Again, if you are not already on a 4.3 bootloader (check by going to download mode and seeing if there is anything about knox there - which would mean you are on 4.3+), then you can flash a custom recovery through odin, and then backup and flash a rom and kernel in the custom recovery. Otherwise, if you are knoxed already, I imagine can flash some stock rom / modem combo.
I've made some assumptions about the n7100 development scene.
singhpratik87 said:
No de-knox available.Are you still under warranty?
Click to expand...
Click to collapse
No, I am not under warranty, I currently have rooted 4.3 on, and I think it is Stock UK, Rooted and deknoxed
Baseband n7100xxuemj9
Kernel 3.0.31-2138564
Build No. JSS15J.N7100XXUEMK9
SE for android status
SEPF_GT-N7100_4_3_0010
I am just sick of this one having long delay on un lock screen sometimes, and thought a fix may have been done
EmptyArea said:
Deknox is available for roms. Not for bootloaders. So, if you aren't already on a knoxed bootloader and want to stay that way do not flash anything stock 4.3+ through odin. I'm not sure of the specifics with the n7100, but with the n7105 4.3+ kernels do not work with 4.1.2 bootloaders (no network) so a custom one is required. Again, if you are not already on a 4.3 bootloader (check by going to download mode and seeing if there is anything about knox there - which would mean you are on 4.3+), then you can flash a custom recovery through odin, and then backup and flash a rom and kernel in the custom recovery. Otherwise, if you are knoxed already, I imagine can flash some stock rom / modem combo.
I've made some assumptions about the n7100 development scene.
Click to expand...
Click to collapse
Its a while since I put my Rom on , but I did use ODIN
Download says
Custom Binary Download: Yes (1 Event)
Current Binary: Custom
System Status: Custom
Warranty Bit (Grayed out) : 0
Any recommendations on what to put on and how appreciated, I generally stay stock with Root ( and de Knox would be good), as I say its the screen unlock freeze ( sometimes 10 seconds) that is getting me looking to change
oh dear , Ive just bricked my phone by Running Triangle away, now only boots to download mode HELP PLEASE
wilx said:
oh dear , Ive just bricked my phone by Running Triangle away, now only boots to download mode HELP PLEASE
Click to expand...
Click to collapse
Not sure how but I got it back, using odin 3.07 and some info from here
http://forum.xda-developers.com/showthread.php?t=2758855
Phew
I have the Canadian SGH-T999V on Mobilicity, and I just flashed stock 4.4.2 and used towelroot to get my phone rooted. I am now planning on installing TWRP back onto my phone after having removed it a while back so that I can install ROMS. I just have some questions regarding the bootloader.
1. Does the bootloader only needs to be unlocked when flashing custom roms? ( I have read in old posts that it was required unlocked to get root but I am going to guess and say that this now starting to be a thing of the past?)
2. I have flashed custom recovery (back when i was on 4.1.1) and my bootloader was locked ( I am assuming it is because Qualcomm Secureboot:Enabled; why does flashing custom recovery not brick the phone with a locked bootloader?
3.Can you always flash stock android with a locked bootloader?
4.Can you point me to a guide that shows how to unlock the bootloader for GS3 SGH-T999V
5. OT:I updated from 4.1.2 --> 4.4.2 and I skipped 4.3 does that mean I can still downgrade, because I have read once you update to 4.3 you can't downgrade because of KNOX. Is it the same deal with 4.4.2.
1) don't know what device you read this about but its always been unlocked
2) it didn't brick because it was not locked
3) yes
4) no need to because it is unlocked
5) you still cannot downgrade, its the same with KK
serio22 said:
1) don't know what device you read this about but its always been unlocked
2) it didn't brick because it was not locked
3) yes
4) no need to because it is unlocked
5) you still cannot downgrade, its the same with KK
Click to expand...
Click to collapse
So what does Qualcomm Secure Boot mean? I'm surprised the bootloader comes unlocked, I thought Samsung would lock it. Thanks for the info really helps.
The locking is up to the carriers in most cases. So far T-Mobile and the Canadian carriers have been very good about this.
But just a quick correction to serio22's post (depending on interpretation). On a locked bootloader you cannot flash kernels or recoveries, so in turn you cannot flash many custom roms. If by stock android you meant vanilla aosp, no you could not. If you meant it like we use it, stock = touchwiz, then yes, there are ways to flash on a locked bootloader.
Qualcomm Secure Boot is intended to prevent tampering to access Knox encrypted containers if I'm not mistaken. Can't remember if that was there before knox.
DocHoliday77 said:
The locking is up to the carriers in most cases. So far T-Mobile and the Canadian carriers have been very good about this.
But just a quick correction to serio22's post (depending on interpretation). On a locked bootloader you cannot flash kernels or recoveries, so in turn you cannot flash many custom roms. If by stock android you meant vanilla aosp, no you could not. If you meant it like we use it, stock = touchwiz, then yes, there are ways to flash on a locked bootloader.
Qualcomm Secure Boot is intended to prevent tampering to access Knox encrypted containers if I'm not mistaken. Can't remember if that was there before knox.
Click to expand...
Click to collapse
I meant touchwiz stock, thanks a lot guys i wanted to make sure I was in the clear before I started to go and flash Cyanogen Mods.