Hello,
on the webpage from chainfire (autoroot.chainfire.eu) you will find these lines:
"UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !"
What does this mean ?
Is that an "UNLOCK BOOTLOADER before flash the following files!" ???
Is that " if you try to flash a bootloader instead of PDA and your bootloader is locked it will brick your device"
so, do i need to unlock the bootloader before using autoroot ?
thanks for help.
Thanks
Sent from my SM-N9005 using Tapatalk
I'm also looking for an answer to this. It's kind of confusing. But I've read a lot of articles and I think I can assume that if your bootloader is locked, you cannot flash custom ROM or custom recovery else it could brick your device. So we have to unlock our bootloaders. Which I have no clue how to, still looking into this .
@firasusman What the? You just said "thanks" when this is asking a question. Please stop spamming, thanks.
jaydeeph said:
I'm also looking for an answer to this. It's kind of confusing. But I've read a lot of articles and I think I can assume that if your bootloader is locked, you cannot flash custom ROM or custom recovery else it could brick your device. So we have to unlock our bootloaders. Which I have no clue how to, still looking into this .
@firasusman What the? You just said "thanks" when this is asking a question. Please stop spamming, thanks.
Click to expand...
Click to collapse
yes, its look like this is the big conspiracy, as i have often seen post with this question, but it never got answered
But i realy cant belive that i need to unlock the bootloader first, as no tutorial mentioned it, but i want to be sure....
I only want to root the device, so i believe that i dont flash a custom rom here. But who knows
unic09 said:
yes, its look like this is the big conspiracy, as i have often seen post with this question, but it never got answered
But i realy cant belive that i need to unlock the bootloader first, as no tutorial mentioned it, but i want to be sure....
I only want to root the device, so i believe that i dont flash a custom rom here. But who knows
Click to expand...
Click to collapse
You havent said what device you have, a n9005?
Sent from my SM-N9005
celderic said:
You havent said what device you have, a n9005?
Sent from my SM-N9005
Click to expand...
Click to collapse
Hi,
sry i forgot about it :I
I have an SM-9005 Telekom branded...
The reason you need an unlocked bootloader is because the auto root flashes a custom recovery and cache temporarily to root, then flashes a stock recovery back in its place. You cannot flash a custom recovery on a locked bootloader.
Sent from my leanKernel 2.3 powered stock 4.4.2 SM-N900T
---------- Post added at 05:39 PM ---------- Previous post was at 05:37 PM ----------
The good news, however, is that most of the note 3 variants (except att, sprint, Verizon in the us) come with unlocked bootloaders by default.
Sent from my leanKernel 2.3 powered stock 4.4.2 SM-N900T
PHP:
toastido said:
The reason you need an unlocked bootloader is because the auto root flashes a custom recovery and cache temporarily to root, then flashes a stock recovery back in its place. You cannot flash a custom recovery on a locked bootloader.
Sent from my leanKernel 2.3 powered stock 4.4.2 SM-N900T
Click to expand...
Click to collapse
Thx for reply.
To clarify that: i need to unlock the Bootloader BEFORE i use cf-autoroot, or will autoroot do this for me ?
unic09 said:
PHP:
Thx for reply.
To clarify that: i need to unlock the Bootloader BEFORE i use cf-autoroot, or will autoroot do this for me ?
Click to expand...
Click to collapse
See the second part of my post above - if you're on a 9005 or 900T it's already unlocked; you can use autoroot without having to do anything else.
Sent from my leanKernel 2.3 powered stock 4.4.2 SM-N900T
However, just to be on the safe side. How does one check if the bootloader is unlocked?
toastido said:
See the second part of my post above - if you're on a 9005 or 900T it's already unlocked; you can use autoroot without having to do anything else.
Sent from my leanKernel 2.3 powered stock 4.4.2 SM-N900T
Click to expand...
Click to collapse
Whow whow, hold your horses. I already knew that most bootloaders outside US come unlocked, which is what I had. However many, many users have updated to KitKat meaning a new bootloader is flashed thus the new bootloader is locked in all KK versions! Which is the same mistake I made, as well as many other users who were in a haste up update to KK. So @op do you have KK or not is also a question.
voncrane said:
However, just to be on the safe side. How does one check if the bootloader is unlocked?
Click to expand...
Click to collapse
I think if you check Odin Download Mode, it should tell you there.
jaydeeph said:
Whow whow, hold your horses. I already knew that most bootloaders outside US come unlocked, which is what I had. However many, many users have updated to KitKat meaning a new bootloader is flashed thus the new bootloader is locked in all KK versions! Which is the same mistake I made, as well as many other users who were in a haste up update to KK. So @op do you have KK or not is also a question.
Click to expand...
Click to collapse
false. All kk bootloaders are NOT locked.
Sent from my leanKernel 2.3 powered stock 4.4.2 SM-N900T
toastido said:
false. All kk bootloaders are NOT locked.
Sent from my leanKernel 2.3 powered stock 4.4.2 SM-N900T
Click to expand...
Click to collapse
Interesting, my bad. Still learning about everything since the Note 3 is my first Android phone. So how do I check if my bootloader is locked?
Does this image tell you anything?:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I believe the n9005 is unlocked, period. You may have a region lock, or a carrier lock, or a reactivation lock, but I belive the bootloader is unlocked.
Sent from my leanKernel 2.3 powered stock 4.4.2 SM-N900T
toastido said:
I believe the n9005 is unlocked, period. You may have a region lock, or a carrier lock, or a reactivation lock, but I belive the bootloader is unlocked.
Sent from my leanKernel 2.3 powered stock 4.4.2 SM-N900T
Click to expand...
Click to collapse
I tend to make a distinction between locked and locking
Technically all Note 3 bootloaders are locked - you can NOT program a bootloader that is not "signed" by Samsung
After that point the bootloader can be LOCKING the next boot stage (kernel and/or recovery) or not (depending on many factors). The bootloader-related programs (basically download mode) can also apply certain LOCKING to what can be written to bootloader files (hence almost all versions will stop you from downgrading the bootloader).
As far as I know indeed N9005 (and a few other versions) accept custom kernels and recovery, but there ARE certain versions (US specific carriers) that do not.
xclub_101 said:
I tend to make a distinction between locked and locking
Technically all Note 3 bootloaders are locked - you can NOT program a bootloader that is not "signed" by Samsung
After that point the bootloader can be LOCKING the next boot stage (kernel and/or recovery) or not (depending on many factors). The bootloader-related programs (basically download mode) can also apply certain LOCKING to what can be written to bootloader files (hence almost all versions will stop you from downgrading the bootloader).
As far as I know indeed N9005 (and a few other versions) accept custom kernels and recovery, but there ARE certain versions (US specific carriers) that do not.
Click to expand...
Click to collapse
True, however the terms used here on xda (and commonly in the community) refer to a locked bootloader as being one that will not boot custom kernels and recoveries. To prevent confusion, I was putting it into those terms.
I believe it goes back to the original android devices by Google, where to use custom kernels or recoveries you had to boot into the bootloader and use fastboot to "oem unlock". Since the note 3 bootloader is not fastboot enabled, this is obviously not an option, so there are either locked, or unlocked, varients of the bootloader, mainly dependent upon the model/carrier used.
The only models I'm 99% sure are unlocked are the SM-900W8, SM-900T, and SM-900/9005. I've heard the 900V and 9006/9007/9002 are as well, but I don't have enough info on those to say for sure. I DO know the SM-900A IS locked (yay att).
Hope that helps clarify further.
Sent from my leanKernel 2.4 powered stock 4.4.2 SM-N900T
Okay,
i now have rooted my german telekom kitkatversion of the my phone without any problems. Thanks for the support !
I have a rooted super su note 3 n9005 does it already unlock the bootloader?
Helpless999 said:
I have a rooted super su note 3 n9005 does it already unlock the bootloader?
Click to expand...
Click to collapse
N9005 does not have a locked bootloader .
If your bootloader is locked its not a N9005
Related
I updated 3 weeks ago to BTU MH8 with knox components and all is perfect., Knox warranty 0x00....
Since my phone originally was ITV (Italy) I'd like to recover the original CSC to ITV with the new firmare ITV MHB released today.
Is there any problem, with knox installed, to flash MHB with Odin? I'm going to sell my S4 and I prefer to return it to the original status.
Thank you
Umberto
umberto.sulla said:
I updated 3 weeks ago to BTU MH8 with knox components and all is perfect., Knox warranty 0x00....
Since my phone originally was ITV (Italy) I'd like to recover the original CSC to ITV with the new firmare ITV MHB released today.
Is there any problem, with knox installed, to flash MHB with Odin? I'm going to sell my S4 and I prefer to return it to the original status.
Thank you
Umberto
Click to expand...
Click to collapse
I would like to know if you can flash with KNOX (using ODIN)?
Guys, all NEW FW's have KNOX on-board and most important the NEW irreversible Bootloader.
You can flash new FW through Odin but it MUST be newer or the same version as your current build.
For example, if you're using XXUDMH8 then you can flash ONLY firmwares with XXU.. on the beginning and anything greater than ...MH8
You can use XXUDMHB as it's newer FW.. it goes from 1-9 and A-Z..
Simple as that..
DjeMBeY said:
Guys, all NEW FW's have KNOX on-board and most important the NEW irreversible Bootloader.
You can flash new FW through Odin but it MUST be newer or the same version as your current build.
For example, if you're using XXUDMH8 then you can flash ONLY firmwares with XXU.. on the beginning and anything greater than ...MH8
You can use XXUDMHB as it's newer FW.. it goes from 1-9 and A-Z..
Simple as that..
Click to expand...
Click to collapse
Thank you for you isimple answer... I only want to be sure that changing CSC from BTU to DTM to ITV etc (going ahead with fw versions) is allowed ...
I don't want to brick my device
DjeMBeY said:
Guys, all NEW FW's have KNOX on-board and most important the NEW irreversible Bootloader.
You can flash new FW through Odin but it MUST be newer or the same version as your current build.
For example, if you're using XXUDMH8 then you can flash ONLY firmwares with XXU.. on the beginning and anything greater than ...MH8
You can use XXUDMHB as it's newer FW.. it goes from 1-9 and A-Z..
Simple as that..
Click to expand...
Click to collapse
Are you 100% sure about that?
I heard once you have KNOX warranty void 0x1 then no matter what firmware you're trying to flash Odin will fail. Even if it's a newer firmware.
I hope you're right and they're wrong.
Obagleyfreer said:
Are you 100% sure about that?
I heard once you have KNOX warranty void 0x1 then no matter what firmware you're trying to flash Odin will fail. Even if it's a newer firmware.
I hope you're right and they're wrong.
Click to expand...
Click to collapse
??? What are you talking about??
I've got KNOX WARRANTY VOID 0x1 and no probs at all, you can flash whatever you want through Odin (same or upwards FW's ONLY)
My KNOX Status got messed up while installing MGG and now I'm running pre-rooted XXUDMI1
DjeMBeY said:
??? What are you talking about??
I've got KNOX WARRANTY VOID 0x1 and no probs at all, you can flash whatever you want through Odin (same or upwards FW's ONLY)
My KNOX Status got messed up while installing MGG and now I'm running pre-rooted XXUDMI1
Click to expand...
Click to collapse
Ok, updated to MHB through Odin and no problem.
Status Knox Warranty still 0x00
umberto.sulla said:
Ok, updated to MHB through Odin and no problem.
Status Knox Warranty still 0x00
Click to expand...
Click to collapse
Yeah, DO NOT flash any Custom Recovery nor Root and your status will stay at 0x0..
You can flash any newer FW but think twice as you can't go back if you don't like it...
No knox voice in my download mode:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is it hidden or is normal until you flash the new knox bootloader?
Diomorgan said:
No knox voice in my download mode:
....
is it hidden or is normal until you flash the new knox bootloader?
Click to expand...
Click to collapse
You have OLD bootloader, no KNOX in it... You're safe for now..
BTW, your Download Mode will look different after you flash new FW..
DjeMBeY said:
You have OLD bootloader, no KNOX in it... You're safe for now..
BTW, your Download Mode will look different after you flash new FW..
Click to expand...
Click to collapse
Thank you for the fast answer, so I'll wait untill you'll release the superslim MI1 to keep my old bootloader
Do you have any picture for the new knox counter on the bootloader of MH8?
mkh.mourad said:
Do you have any picture for the new knox counter on the bootloader of MH8?
Click to expand...
Click to collapse
It's NOT a counter, it's flag, stays at 0x1 no matter how many times you flash..
here is the picture http://forum.xda-developers.com/showpost.php?p=45877809&postcount=108
DjeMBeY said:
It's NOT a counter, it's flag, stays at 0x1 no matter how many times you flash..
here is the picture http://forum.xda-developers.com/showpost.php?p=45877809&postcount=108
Click to expand...
Click to collapse
hmmmmm
That's a great problem. I stay using my UBMGA firmware.
DjeMBeY said:
??? What are you talking about??
I've got KNOX WARRANTY VOID 0x1 and no probs at all, you can flash whatever you want through Odin (same or upwards FW's ONLY)
My KNOX Status got messed up while installing MGG and now I'm running pre-rooted XXUDMI1
Click to expand...
Click to collapse
But you didn't flash the bootloader, did you?
So if you have new bootloader and knox 0x1 status you can still flash stock firmware in Odin and run it fine, even with stock kernel?
mkh.mourad said:
hmmmmm
That's a great problem. I stay using my UBMGA firmware.
Click to expand...
Click to collapse
You can install latest XXUDMI1 but CWM version as bootloader won't be flashed..
Obagleyfreer said:
But you didn't flash the bootloader, did you?
So if you have new bootloader and knox 0x1 status you can still flash stock firmware in Odin and run it fine, even with stock kernel?
Click to expand...
Click to collapse
I'm using pre-rooted MI1 (Odin version) with latest bootloader so yes, you can.
@ both of you
Check my thread in Development section for more informations
Thanks
On the S3 if I used MobileOdin to flash a new Rom it wouldn't update the bootloader. Can someone confirm the same is true on the S4?
Sent from my GT-I9505 using Tapatalk 4
DjeMBeY said:
You can install latest XXUDMI1 but CWM version as bootloader won't be flashed..
I'm using pre-rooted MI1 (Odin version) with latest bootloader so yes, you can.
@ both of you
Check my thread in Development section for more informations
Click to expand...
Click to collapse
Awesome thanks dude, and we can find this Mi1 firmware in your thread?
Painman1963 said:
On the S3 if I used MobileOdin to flash a new Rom it wouldn't update the bootloader. Can someone confirm the same is true on the S4?
Sent from my GT-I9505 using Tapatalk 4
Click to expand...
Click to collapse
That would probably be an instant KNOX warranty void due to the fact that Mobile ODIN only runs on rooted devices...
But I'm not gonna experiment with it due to the uncertainty of it...
Hi, my phone is less than a week old, I want to root it in order to debloat it initially, but with the possibility of at some point going totally custom.
Now I know there's virtually no way of modifying without tripping KNOX (towelroot does not work with my OS release)......what I need are some clear answers (I've seen a lot of conflicting information) as to what tripping KNOX will mean for the device....
So here are my questions....
1) if I go fully custom, will I be able to return to full stock with Odin?
2) if I return to full stock, will I be able to receive OTA updates?
3) with a tripped device, will I see a KNOX message on normal start up of the phone?
4) is my warranty totally screwed even If I have a totally unrelated hardware issue?
5) is EU Regulation (1999/44/CE) ANY REAL help, or can manufacturers interpret it in their favor?
Thanks in advance......Keith.
Sent from my SM-G900F
keithross39 said:
Hi, my phone is less than a week old, I want to root it in order to debloat it initially, but with the possibility of at some point going totally custom.
Now I know there's virtually no way of modifying without tripping KNOX (towelroot does not work with my OS release)......what I need are some clear answers (I've seen a lot of conflicting information) as to what tripping KNOX will mean for the device....
So here are my questions....
1) if I go fully custom, will I be able to return to full stock with Odin?
2) if I return to full stock, will I be able to receive OTA updates?
3) with a tripped device, will I see a KNOX message on normal start up of the phone?
4) is my warranty totally screwed even If I have a totally unrelated hardware issue?
5) is EU Regulation (1999/44/CE) ANY REAL help, or can manufacturers interpret it in their favor?
Thanks in advance......Keith.
Sent from my SM-G900F
Click to expand...
Click to collapse
1) Yes, you just need to download firmware from sammobile and flash it with Odin
2) By going to fully custom you trip knox to 0x1 and theoretically you can`t get OTA updates but I received it after I had knox 0x1 and on fully stock ROM
3) No
4) Yes if you send it to Samsung service
5) I don`t even know what that is
Thank you for your reply.....
Number 5 is an EU ruling that covers consumer protection and statutory warranty and it *appears* to contradict what Samsung says about KNOX voiding warranty.....The thing is, I'm not a lawyer so I can't be 100% certain......
Sent from my SM-G900F
Honestly i don't know if that EU rulling has any real application or at least it doesn't in every country because Samsung or their repair centers will check for knox and will use that excuse to avoid fixing the phone under warranty for something that a rom or mod wouldn't cause.
But it also depends on who repairs your phone and if they check that or not, so is really just rolling the dice.
Lol...I guess you're right.....
I'm gonna root this beast anyway, it's just that it would have been good to get a watertight legal perspective first......
It's a shame that the legal profession seems to have little interest in rooting their phones.....
Sent from my SM-G900F
Here's a screen shot of an email I just sent to Samsung UK......
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It'll be interesting to see what (if any) reply I get from them.......
I'll update here if/when they do reply......
Sent from my SM-G900F
If you follow the steps of the tutorial here on the s5 section of xda you shouldn't have a problem with knox. I rooted my s5 and it didn't trip knox, the only thing that changed was the status from "oficial" to "custom", but after reflash a stock rom on odin and not rooting it, it went back to saying "official", so they can't claim i rooted the phone.
So, as long as you keep stock (not custom recovery and custom roms) and just root following the steps on the tutorial, it should be fine.
Many of the big companies use root detection systems and don't support root and they use that to decide if they fix the phone or not. Most of the times the problem is unrelated to software but they still claim it. Its a bit of a grey are and depends on the company. I do remember reading that there were some countries where root was considered legal and i think the UK was one of them, so i might get a positive reply from them but im not sure.
Are you talking about this thread?
http://forum.xda-developers.com/showthread.php?t=2699648
If so, I already tried towelroot and it failed, which means I have to downgrade to an earlier version of the OS in order to root.....The only trouble with that being that I looked on sammobile and there didn't appear to be an earlier OS from my carrier.......
Sent from my SM-G900F
No, this one : http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044
That's the one i followed without flag knox. If towelroot didn't give you knox 0x1, then you can try that method to keep 0x0 when you root.
Ah ok cheers mate.......
So let me see if I've got this right......
First the build and baseband numbers on my phone both say ANG2.
So.......
1) Odin (3.09) flash ANE2 kernel.
2) Reboot, install towelroot and root
3) Reboot into download mode and reflash ANG2 kernel.
4) Reboot as normal.
No data wipes required?
Won't re flashing the original kernel kill root?
Can I use mobile odin to re flash the original kernel?
Edit.......just had a thought, could the flash kernel that mobile odin uses trigger KNOX?
Sent from my SM-G900F
Ah.....don't think it's gonna work mate.....just put my glasses on and had a closer read......
It says to have towelroot installed before flashing the temporary kernel......
I can't even get towelroot to install.....Every time I try I get a pop up box appearing that says something about security. If I press install anyway, it simply fails........
Sent from my SM-G900F
keithross39 said:
Ah ok cheers mate.......
So let me see if I've got this right......
First the build and baseband numbers on my phone both say ANG2.
So.......
1) Odin (3.09) flash ANE2 kernel.
2) Reboot, install towelroot and root
3) Reboot into download mode and reflash ANG2 kernel.
4) Reboot as normal.
No data wipes required?
Won't re flashing the original kernel kill root?
Can I use mobile odin to re flash the original kernel?
Edit.......just had a thought, could the flash kernel that mobile odin uses trigger KNOX?
Sent from my SM-G900F
Click to expand...
Click to collapse
That's it!
I don't remember making any wipes, so i don't think they are needed.I followed those stepsand the kernel didn't change the root.
I don't know if you can use mobile odin, i would use the pc version just to be sure.
Also don't forget these steps:
5. DISABLE REACTIVATION LOCK
6. IF YOUR DEVICE IS ENCRYPTED, DECRYPT IT
Click to expand...
Click to collapse
ยด
That security warning is probably because you have the option to not allow unkown apps to install, which is on by default. Go to settings-security-tick unknown sources and untick app verification
Uh......probably being thick, but never seen this version of odin before. Which button do I click to insert the kernel?
Sent from my SM-G900F
It's on the AP button and then find the kernel
griffin_1 said:
It's on the AP button and then find the kernel
Click to expand...
Click to collapse
Ah ok fella......see you on the other side lol.
Sent from my SM-G900F
@griffin_1 You sir, are a scholar and a gent........
Rooted and KNOX at 0x0......
Many many thanks........
Sent from my SM-G900F
No problem! Im glad it worked well for you also The devs behind the root and tutorial deserve props for giving us a way to fully enjoy our phone without compromise the warranty.
Enjoy the root freedom
Well.....The emails continue......
This is how Samsung replied to my email.....
And this is how I replied....
Just have to wait and see what happens now........
Samsung's final reply to me.......
I think it's pretty obvious that Samsung's policy is to "wash it's hands" of anybody who modifies their phones........
sent from my rooted Kn0x0 SM-G900f
Keep us posted on their reply. But honestly i don't think it will change much from the "it voids the warranty" claim they like to use
This is literally just the Odin Flashable bootloader and tar files. These files don't allow direct flashing of lp from nk2 as previously suspected. As there are some new differences between nk2 and lp that don't allow this. This is basically obsolete for general use. Ill leave the files for a few of those that are on roms like cm12 and some nk2 that want to use the modem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads:
Modem : here
Bootloader : here
sms gps
Will flashing these fix sms and gps issues on lp roms?
When I took the Ota from NK2 to BOB7. After that I jacked it up and I was able to go back to NK2 via Odin. Is it me or did it used to be once you updated to new version of Android you couldn't go back? Or is it how you update?
Can you get the stock kernel?
MJ523 said:
Will flashing these fix sms and gps issues on lp roms?
Click to expand...
Click to collapse
Not likely, this is for OFFICIAL BOB7 roms. (which there is only 1 currrently out and it doesn't have either of those problems to my knowledge)
sml2004 said:
When I took the Ota from NK2 to BOB7. After that I jacked it up and I was able to go back to NK2 via Odin. Is it me or did it used to be once you updated to new version of Android you couldn't go back? Or is it how you update?
Click to expand...
Click to collapse
You can go back, some devices don't allow you to downgrade. Its normally a bootloader things to not allow this. But they were nice and allowed it this time. Rom's seem to be able to be flashed (if you have a custom kernel to flash) on the newer bootloaders as well.
Androidwarrior said:
Can you get the stock kernel?
Click to expand...
Click to collapse
Search Function. Not going to confuse ODIN flashables and recovery flashables in the same area.
millerboy3 said:
Not likely, this is for OFFICIAL BOB7 roms. (which there is only 1 currrently out and it doesn't have either of those problems to my knowledge)
You can go back, some devices don't allow you to downgrade. Its normally a bootloader things to not allow this. But they were nice and allowed it this time. Rom's seem to be able to be flashed (if you have a custom kernel to flash) on the newer bootloaders as well.
Search Function. Not going to confuse ODIN flashables and recovery flashables in the same area.
Click to expand...
Click to collapse
Thanks for your help.
Flashed the bootloader and modem successfully. Cant activate phone on Sprint network so no OTA.
BOB7 shows up in About device.
Flash LP ViSion-X Rom , reboot loop at startup.
Maybe the DL of the rom was corrupt...doubtful. Will try again.
Anyway this is just a note for people in similar situation who want to update to TW LP.
At any rate, thanks so much for the BL and Modem tar files.
oa12 said:
Flashed the bootloader and modem successfully. Cant activate phone on Sprint network so no OTA.
BOB7 shows up in About device.
Flash LP ViSion-X Rom , reboot loop at startup.
Maybe the DL of the rom was corrupt...doubtful. Will try again.
Anyway this is just a note for people in similar situation who want to update to TW LP.
At any rate, thanks so much for the BL and Modem tar files.
Click to expand...
Click to collapse
I had this same problem trying to flash a LP rom.
Can I flash just the modem over a CM12 based rom?
I realize that historically modems have nothing to do with the OS but I am already on a CM12 based rom and have TWRP recovery installed.
Thank you!
hermeticist said:
Can I flash just the modem over a CM12 based rom?
I realize that historically modems have nothing to do with the OS but I am already on a CM12 based rom and have TWRP recovery installed.
Thank you!
Click to expand...
Click to collapse
I guess you could try. Not sure what it will do for/with CM12 at all. I'm only aware of the effects on TW based LP.
oa12 said:
Flashed the bootloader and modem successfully. Cant activate phone on Sprint network so no OTA.
BOB7 shows up in About device.
Flash LP ViSion-X Rom , reboot loop at startup.
Maybe the DL of the rom was corrupt...doubtful. Will try again.
Anyway this is just a note for people in similar situation who want to update to TW LP.
At any rate, thanks so much for the BL and Modem tar files.
Click to expand...
Click to collapse
treo4life said:
I had this same problem trying to flash a LP rom.
Click to expand...
Click to collapse
I did the same thing when I first made this. It did work however going from KK custom rom-> LP custom rom with this method. Didn't try a fresh install of LP with it however. I'm doing more testing now. But the files themselves are good, came from the official tar and packaged correctly in the correct order. So Not sure what the problem is. It seems as though the bootloader isn't sticking? I'm getting a bootloop like I'm not on LP when I flash the bootloader/modem from stock nk2 -> stock LP. I'll double check things.
millerboy3 said:
I guess you could try. Not sure what it will do for/with CM12 at all. I'm only aware of the effects on TW based LP.
Click to expand...
Click to collapse
Generally newer modems include some network performance upgrades.
millerboy3 said:
I did the same thing when I first made this. It did work however going from KK custom rom-> LP custom rom with this method. Didn't try a fresh install of LP with it however. I'm doing more testing now. But the files themselves are good, came from the official tar and packaged correctly in the correct order. So Not sure what the problem is. It seems as though the bootloader isn't sticking? I'm getting a bootloop like I'm not on LP when I flash the bootloader/modem from stock nk2 -> stock LP. I'll double check things.
Click to expand...
Click to collapse
Thanks for the update, im trying it again with another LP rom, keep us updated on what you find.:good:
UPDATE: it failed trying on another LP rom as well..
hermeticist said:
Can I flash just the modem over a CM12 based rom?
I realize that historically modems have nothing to do with the OS but I am already on a CM12 based rom and have TWRP recovery installed.
Thank you!
Click to expand...
Click to collapse
yes I did, after the boot loop trouble. I restored cm12 with BOB7 modem and BL and it worked fine.
LP OTA tar for Odin was posted here:
http://forum.xda-developers.com/note-4-sprint/general/stock-tar-odin-flashable-t3056478
flashed Odin and worked. Currently updating apps.
edit- sammobile has posted the official stock for 910P! woot! let the games begin.
oa12 said:
yes I did, after the boot loop trouble. I restored cm12 with BOB7 modem and BL and it worked fine.
LP OTA tar for Odin was posted here:
http://forum.xda-developers.com/note-4-sprint/general/stock-tar-odin-flashable-t3056478
flashed Odin and worked. Currently updating apps.
edit- sammobile has posted the official stock for 910P! woot! let the games begin.
Click to expand...
Click to collapse
The link is the same file as Sammobile. Just faster download.
I just wanted to point this out for people who might not know. This is only the Lollipop BOB7 modem & bootloader and it's purpose is straight forward for those who need it. Thanks for sharing @millerboy3
However, in order to fully and correctly upgrade from any KK rom you will first need to either take the Lollipop ota update OR odin flash the BOB7 stock rom tar. There are several other partitions that must be written/updated. If you've never updated to Lollipop by one of these two methods then you really need to. So in other words you can't simply flash this modem/bootloader tar and expect to be able to flash a custom Lollipop rom without problems.
tx_dbs_tx said:
I just wanted to point this out for people who might not know. This is only the Lollipop BOB7 modem & bootloader and it's purpose is straight forward for those who need it. Thanks for sharing @millerboy3
However, in order to fully and correctly upgrade from any KK rom you will first need to either take the Lollipop ota update OR odin flash the BOB7 stock rom tar. There are several other partitions that must be written/updated. If you've never updated to Lollipop by one of these two methods then you really need to. So in other words you can't simply flash this modem/bootloader tar and expect to be able to flash a custom Lollipop rom without problems.
Click to expand...
Click to collapse
Correct after testing and testing we discovered this. Editing the op for the file usages. Thanks @tx_dbs_tx for confirming our suspicions!
tx_dbs_tx said:
I just wanted to point this out for people who might not know. This is only the Lollipop BOB7 modem & bootloader and it's purpose is straight forward for those who need it. Thanks for sharing @millerboy3
However, in order to fully and correctly upgrade from any KK rom you will first need to either take the Lollipop ota update OR odin flash the BOB7 stock rom tar. There are several other partitions that must be written/updated. If you've never updated to Lollipop by one of these two methods then you really need to. So in other words you can't simply flash this modem/bootloader tar and expect to be able to flash a custom Lollipop rom without problems.
Click to expand...
Click to collapse
I'm a little confused by this.
I've been on a CM12 based lollipop rom for a couple months now.
I flashed the modem and have already noticed improved handover.
Are you saying that I should flash the bootloader as well?
(ie back up my system, flash bootloader, then restore recovery and system).
Mods please close this thread.
Thread closed at OP request
Edfunkycold
Have a great day!
Hey all.
I've a question. In GT-i9500, is there the need to unlock bootloader as in Motorola devices before flashing custom ROMs. Or it comes with it's bootloader pre-unlocked?
Would be very glad on your response
Thank You!
munimjaffer said:
Hey all.
I've a question. In GT-i9500, is there the need to unlock bootloader as in Motorola devices before flashing custom ROMs. Or it comes with it's bootloader pre-unlocked?
Would be very glad on your response
Thank You!
Click to expand...
Click to collapse
in I9500 we can update bootloader and go back to old without problems and we can flash roms without need to unlock
Verizon and AT&T devices usually have locked bootloaders. Everything else should be unlocked.
Ngadhnjim said:
in I9500 we can update bootloader and go back to old without problems and we can flash roms without need to unlock
Click to expand...
Click to collapse
thanks alot for ur reply
GDReaper said:
Verizon and AT&T devices usually have locked bootloaders. Everything else should be unlocked.
Click to expand...
Click to collapse
Then we should first of all unlock bootloader before flashing roms?
Unless the S4 is a US model sold by AT&T or Verizon, which yours isn't, the bootloader will be unlocked. That means being able to update the bootloader, radio, and installing custom ROMs, as previously stated. Keep in mind the following: Samsung does not use fastboot, thus any commands you could use on a Motorola device will not work on a Samsung device. You will have to use Odin.
munimjaffer said:
Then we should first of all unlock bootloader before flashing roms?
Click to expand...
Click to collapse
i dont known for verzion ,he ask for i9500
munimjaffer said:
Then we should first of all unlock bootloader before flashing roms?
Click to expand...
Click to collapse
I-9500 came with factory unlocked bootloader.
If your phone really is i-9500 as you said,
install the custom recovery like TWPR or CWM via odin and
flash the custom rom of your choice via the custom recovery.
sway8966 said:
I-9500 came with factory unlocked bootloader.
If your phone really is i-9500 as you said,
install the custom recovery like TWPR or CWM via odin and
flash the custom rom of your choice via the custom recovery.
Click to expand...
Click to collapse
Ok thanks
l have a question if my i9500 says secure download enabled does that mean its bootloader locked +++
Asked and answered already in this thread. Unless your S4 is an SGH-I337 or SCH-I545 (AT&T and Verizon respectively) your bootloader will not be locked.
i need a bunch of help. getting TWRP on my galaxy S5 S930VL, rooting, and all the other good stuff. if anyone has time to help, id appreciate it.
Thanks XDA Community.
Bump
I have these files. Anyone know what to do to make it into root?
AP_S903VLUDU4APH3_CL8867563_QB10607737_REV00_user_ low_ship_MULTI_CERT.tar.md5
AP_S903VLUDU4APH3_CL8867563_QB10607737_REV00_user_ low_ship_MULTI_CERT.tar.md5
CP_S903VLUDU4APH3_CL8867563_QB10607737_REV00_user_ low_ship_MULTI_CERT.tar.md5
CSC_TFN_S903VLTFN4APH3_CL8867563_QB10607737_REV00_ user_low_ship_MULTI_CERT.tar.md5
KLTE_USA_TFNVZWFRP.pit
Download them from my drive... https://drive.google.com/open?id=0B4954IfsDiYKUmkyZkNIMVhrOUk
if it has an unlocked bootloader, just flash twrp 3.0.2 and root from recovery. but do NOT flash a pit unless instructed to do so by a dev or very knowledgeable senior member
also, i assume that youre referring to the s903vl, not the s930vl
youdoofus said:
if it has an unlocked bootloader, just flash twrp 3.0.2 and root from recovery. but do NOT flash a pit unless instructed to do so by a dev or very knowledgeable senior member
also, i assume that youre referring to the s903vl, not the s930vl
Click to expand...
Click to collapse
Flashing twrp ends in fail auth with odin, phone says secure check fail: recovery
mortj19 said:
Flashing twrp ends in fail auth with odin, phone says secure check fail: recovery
Click to expand...
Click to collapse
usually the sign of a locked bootloader
youdoofus said:
usually the sign of a locked bootloader
Click to expand...
Click to collapse
Pretty sure its not locked, its straight talk and they have unlocked bootloaders
mortj19 said:
Pretty sure its not locked, its straight talk and they have unlocked bootloaders
Click to expand...
Click to collapse
im not saying it is locked, im just saying the error youre getting is usually the sign of a locked bootloader. what version of twrp are you flashing?
youdoofus said:
im not saying it is locked, im just saying the error youre getting is usually the sign of a locked bootloader. what version of twrp are you flashing?
Click to expand...
Click to collapse
I tried the latest twrp for different versions of the s5 nothing has worked thus far
mortj19 said:
I tried the latest twrp for different versions of the s5 nothing has worked thus far
Click to expand...
Click to collapse
there arent different versions of the S5 as far as TWRP is concerned. There is only the qualcomm and xynos. Try a different Odin (3.7.10 is whats worked most universally for me when flashing stuff on many different galaxy devices) and dont use a twrp past 3.0.2. Stay away from 3.0.2-1 and 3.0.2-2
youdoofus said:
there arent different versions of the S5 as far as TWRP is concerned. There is only the qualcomm and xynos. Try a different Odin (3.7.10 is whats worked most universally for me when flashing stuff on many different galaxy devices) and dont use a twrp past 3.0.2. Stay away from 3.0.2-1 and 3.0.2-2
Click to expand...
Click to collapse
Tried it with same results, also if yiy check out the page for the s5 qualcomm it indeed has different versions for each model of s5
I found a root method, kind of... https://forum.xda-developers.com/galaxy-s5/general/downgrade-to-4-4-2-factory-test-t3530449
Mortj19 did you ever get your device rooted?
The bootloaders on the sm-s903vl are sadly locked I am positive bc it's just another variant of the Sm-g900v (Verizon) if you take out the battery and look at the back you will see 900v. But the SM-S902L is unlocked though and very much possible to root
My understanding is it's a locked bootloader as well. Any update? If it's the same as g900v then cf auto root has root software for it. Can you just use the root for the g900v on the s903vl?
lotto44 said:
My understanding is it's a locked bootloader as well. Any update? If it's the same as g900v then cf auto root has root software for it. Can you just use the root for the g900v on the s903vl?
Click to expand...
Click to collapse
I'm going to try and see if I have any success
---------- Post added at 05:51 AM ---------- Previous post was at 05:39 AM ----------
It does not work. I'm guessing whenever Odin flashes the file since the model is different from ours it won't work. But since the phones are the same except for the model numbers and all that do you think it would be possible to edit the CF auto root file for the g900v to make it compatible with the s903vl ?