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.
I am new and fresh to this field, so what exactly is rooting and bootloader unlock?
Is it necessary for us to unlock bootloader before rooting the phone like most of the thread that i have read so far?
if we installing custom rom like Xperia Ultimate HD, paranoid,etc. is it necessary just to root/unlock bootloader or both is required?
Can we install custom rom without unlock the bootloader or rooting?
What is is the downfall of rooting and bootloader unlock?
Thanks for the reply in advance.
Rooting gives "admin" rights - allowing you to make changes to the system files on the phone.
Unlocking bootloader enables you to write to the /boot partition on the phone ( ie flash custom kernel) which is normally not writable even with root access.
it is phone dependent. Some phones need unlocked bootloader to be rooted, some do not. We have several rooting tools for locked bootloader, it's in the general section use the search button.
There are different types of rom - stock based and CM based.
But before that - kernels are only compatible with android version. You cannot use, say, JB kernel on ICS rom.
Stock based roms ( UHD, Zelly Cream etc) do not need unlocked BL bc they can run on the stock kernel.
CM based roms ( CM7.2, CM9, MIUI V5) need unlocked BL because they cannot run on stock.
So if you have locked BL, you root, copy Rom into sdcard, install recovery then install rom.
if you have unlocked BL, you simply flash kernel then flash rom. No need to root because custom roms are pre rooted.
Rooting does no harm to phone. Unlocking BL via official method makes u lose DRM keys and warranty but u can always relock and get warranty back. ( providing service centre does not check for DRM)
This is a simple overview for a more in-depth understanding check the general section there are many great guides in there.
Sent from my MiUI-ed Xperia arc S
\ press thanks if I've helped /
tangosierra_ said:
Rooting gives "admin" rights - allowing you to make changes to the system files on the phone.
Unlocking bootloader enables you to write to the /boot partition on the phone ( ie flash custom kernel) which is normally not writable even with root access.
it is phone dependent. Some phones need unlocked bootloader to be rooted, some do not. We have several rooting tools for locked bootloader, it's in the general section use the search button.
There are different types of rom - stock based and CM based.
But before that - kernels are only compatible with android version. You cannot use, say, JB kernel on ICS rom.
Stock based roms ( UHD, Zelly Cream etc) do not need unlocked BL bc they can run on the stock kernel.
CM based roms ( CM7.2, CM9, MIUI V5) need unlocked BL because they cannot run on stock.
So if you have locked BL, you root, copy Rom into sdcard, install recovery then install rom.
if you have unlocked BL, you simply flash kernel then flash rom. No need to root because custom roms are pre rooted.
Rooting does no harm to phone. Unlocking BL via official method makes u lose DRM keys and warranty but u can always relock and get warranty back. ( providing service centre does not check for DRM)
This is a simple overview for a more in-depth understanding check the general section there are many great guides in there.
Sent from my MiUI-ed Xperia arc S
\ press thanks if I've helped /
Click to expand...
Click to collapse
So, how about Xperia Arc and Xperia Arc S? does it require to unlock bootloader to root?
What is the main difference of Stock based roms and CM based roms? How to differentiate it?
Correct me if i mistake. Unlock the bootloader normally only required for flashing the custom kernel like lupus kernel which it is required for CM based rom. And if it is stock based it will only need root for the installation.
shuffle1990 said:
So, how about Xperia Arc and Xperia Arc S? does it require to unlock bootloader to root?
What is the main difference of Stock based roms and CM based roms? How to differentiate it?
Correct me if i mistake. Unlock the bootloader normally only required for flashing the custom kernel like lupus kernel which it is required for CM based rom. And if it is stock based it will only need root for the installation.
Click to expand...
Click to collapse
Firstly, Xperia Arc and Xperia Arc S use the same kernels, and the same ROMs, they're most likely the same phone. The stock-based ROMs, as far on my stay on xda I've learned that they are the ones based on the ROMs already released by sony, i.e Ice Cream Sandwich or Gingerbread. How to differentiate? Easy, on a first place the Rom Thread should clearly say if it's stock based or no, and you can see the tags [ICS] or [.587], or tags like that. CM based ROMs should be clearly stated too, plus it must say [CM10] or [CM10.1].
And yes, you're right, without unlocking bootloader you can still have a custom ROM, ICS based or GB based. You actually don't need root for the installation, and generally the ROMs that you install come pre-rooted. Hope it helped.
tangosierra_ said:
Unlocking bootloader enables you to write to the /boot partition on the phone ( ie flash custom kernel) which is normally not writable even with root access.
Click to expand...
Click to collapse
Just to correct this, unlocking bootloader allows custom, unsigned, kernels to be installed. /boot partition can still be edited by using stock kernels, which have been signed by Sony, these are the kernels within Flashtool FTF files. This can still be done with locked bootloader.
The thread titles will tell if it is stock or CM based
Ah yes forgot about the stock kernel, damn
Is carrier unlocking (only) bootloader related?
In other words, will a custom rom or a custom recovery interfere with the carrier unlock?
If you want to carrier unlock the phone you must be on the original stock rom (the bootloader can be unlocked). You can't carrier unlock the phone on a custom rom. So no they are not related.
So the advice is to carrier unlock the device first before even unlocking the bootloader and after that proceed with custom roms if you wish.
my bootload is unlocked, i have a custom recovery and a custom rom installed
so you are recommending that i restore stock recovery and stock rom and then unlock it (but i dont need to lock the bootloader)?
To carrier unlock you must return to your stock rom and recovery otherwise it won't work. The bootloader can stay unlocked.
I unlocked mine while using MaximusHD with lyapota kernel and twrp recovery installed and I had no problems at all, maybe you just need a Rom based on sense and NOT aosp, cyanogen mod etc.
I know the answer is 99% NO but still how did this person do it? Does the galaxy use a different "kind" of bootloader that allows this?
https://www.youtube.com/watch?v=bZDMHktN3sc
has anyone with a rooted (but locked bootloader) G4 actually tried the latest flashfire with a G4 custom rom like resurrection?
I tried lollipop genisys and its way faster
Sent from my LG-H815 using Tapatalk
You can install Roms with locked bootloader.
I have CamUIX installed, which is based on the original rom.
I am not 100% sure but I know that you can not install custom roms which use a different kernel (any cm rom).
So it wouldn't be very useful :/
By the way, the rom in the Video is also a Touchwiz based rom
Sure you can... You can flash ANY rom that is compatible with stock kernel... Locked bootloader is only about signed boot.img and recovery.img not about system.img
oh interesting.. is there any custom G4 roms that uses stock kernel? i'm hesitant beacuse i have a h812 which has a locked bootloader and none of the roms that i see say that they can flashed for h812
it looks like genisys: http://forum.xda-developers.com/g4/orig-development/bl-lock-ul-android-6-0-marshmallow-t3459260 uses stock kernel..? will it work on my H812 if i flash with flashfire?
You can flash custom system images ONLY also on lollipop ONLY. Boot.img and recovery must be signed by lg to load with locked bootloader, they obviously arent so cant do a single s**t really.
Hi i would just like to ask something that has been confusing me for quite a while now. I've had my hydrogen for a week and ive unlocked bl, rooted now with a custom rom(rr rom 5.7.4 working great!!) I did not actually wanted to unlock the bootloader but to be safe, i followed the instructions.
so here it is, before mi max, I had a mi4i, an xperia, and a zenfone 4, done the same, root,install custom recovery, and flashed custom roms.. the only unit i unlocked bl was the xperia since i wanted to flash Official CM, (CM's comes with their own kernel right? so flashing them needs bl unlocked) but when BL was locked i could still flash roms, manual update, (ROMs that are meant for locked bl only). then with mi4i (locked bl) i was able to root, install twrp, manual flash updates, official roms, and custom rom (CM13).
The part where I am confused is, why do i need my bootloader unlocked if i was going to root,install twrp, and flash custom roms only on my max without touching the kernel? When in my previous experiences as long as i dont need touch/tweak the kernel, i dont need my bootloader to be unlocked.
Sorry for long post..
I hope my question makes sense