Related
This is a thread to see if anyone has ideas on Unlocking the Bootloader & porting/creating CWM or TWRP to our device? Any ideas are helpful and welcomed.
krazie1 said:
This is a thread to see if anyone has ideas on porting CWM or TWRP to our device? Any ideas of getting a custom recovery on this phone is welcomed. We have Root for the At&t/Verizon variants, custom recovery would be topping to the cake.
Click to expand...
Click to collapse
Dont we need an unlocked bootloader first?
chrisexv6 said:
Dont we need an unlocked bootloader first?
Click to expand...
Click to collapse
I'm not to sure, I know you need the bootloader unlocked for Roms and Kernels
EDIT: I thought about it and your right, you always have to unlock the bootloader before you install the Custom Recovery.
krazie1 said:
I'm not to sure, I know you need the bootloader unlocked for Roms and Kernels
Click to expand...
Click to collapse
Are you sure the bootloader needs to be unlocked in order to install roms?? Thought that was only for custom kernels. Moto devices have always had pretty locked down devices, yet had recoveries and ability to install roms, if I remember correctly...
dmbfan13 said:
Are you sure the bootloader needs to be unlocked in order to install roms?? Thought that was only for custom kernels. Moto devices have always had pretty locked down devices, yet had recoveries and ability to install roms, if I remember correctly...
Click to expand...
Click to collapse
http://forums.androidcentral.com/ht...oader-custom-recovery-root-flashing-roms.html
Why should I unlock?
The explanation to this question is really simple. If you want root, you’d be wanting to flash Custom ROM post-root, and if you want to install a Custom ROM, you’d need to have your stock bootloader unlocked. In simple terms Unlocking the bootloader allows you to install custom Firmware on your Android phone
Warning: Unlocking your phone’s bootloader voids its warranty. It also completely wipes (formats) your Android phone’s internal memory including applications, contacts, SMS and MMS messages etc.
dmbfan13 said:
Are you sure the bootloader needs to be unlocked in order to install roms?? Thought that was only for custom kernels. Moto devices have always had pretty locked down devices, yet had recoveries and ability to install roms, if I remember correctly...
Click to expand...
Click to collapse
kexec is required to flash a kernel.
Safestrap is a way to flash somewhat custom ROMs (without kexec you need to use stock kernel) without recovery installed but it needs to be adapted to each specific phone. Right now I think they are working on a version that will work with the S4, not sure how attractive the G2 is (or will be).
krazie1 said:
This is a thread to see if anyone has ideas on Unlocking the Bootloader & porting/creating CWM or TWRP to our device? Any ideas are helpful and welcomed.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2443165 <---- these guys are the ones who worked most of the magic for Optimus G (and Pro?).
You guys first need Root to do anything (which i believe you have). Then you need a Custom Recovery. Installing a Custom Recovery can be accomplished via a workaround or by unlocking the bootloader. A workaround like loki by djrbliss on the Galaxy S4 which isn't an unlock but more so a bypass or like Safestrap by Hashcode.
Here is the man djrbliss.
http://forum.xda-developers.com/showthread.php?t=2358871
https://twitter.com/djrbliss
Is there any news on this? I cant even find a good place to look for info about this phone yet.
WACOMalt said:
Is there any news on this? I cant even find a good place to look for info about this phone yet.
Click to expand...
Click to collapse
There was someone who posted an IRC room for the g2 but i can't find it and i don't recall who posted it.
Darkestred said:
There was someone who posted an IRC room for the g2 but i can't find it and i don't recall who posted it.
Click to expand...
Click to collapse
what is the channel name? I wanna hop in there.
I just ripped my aboot.img from my system. Trying to figure out who to send that too for it to be of use.
WACOMalt said:
Is there any news on this? I cant even find a good place to look for info about this phone yet.
Click to expand...
Click to collapse
WACOMalt said:
what is the channel name? I wanna hop in there.
I just ripped my aboot.img from my system. Trying to figure out who to send that too for it to be of use.
Click to expand...
Click to collapse
I found it. server is chat.freenode.net room is lg-g2. Not very much going on in there at the moment.
i completely agree with the said explanation. but I'm having difficulties with my device i.e. LG G2 (D802).
I'm rooted with custom recovery TWRP and unable to install most of AOSP roms based on 4.4 KitKat. New Custom roms are coming up very frequently now for this device but so far I'm able to flash ParanoidAndroid Rom and modifited stock rom... Apart from this I always gets error while flashing the rom.
Most of the time Error comes up saying 'Status 7 Error' and 'unable to execute update binary'.
I did google on this subject and tried everything i found but the problem still exist.
I never had these problem flashing LG Stock or Android 4.3 based roms. Need advise on this subject. By the way any help on unlocking the bootloader????
thanks:good:
krazie1 said:
http://forums.androidcentral.com/ht...oader-custom-recovery-root-flashing-roms.html
Why should I unlock?
The explanation to this question is really simple. If you want root, you’d be wanting to flash Custom ROM post-root, and if you want to install a Custom ROM, you’d need to have your stock bootloader unlocked. In simple terms Unlocking the bootloader allows you to install custom Firmware on your Android phone
Warning: Unlocking your phone’s bootloader voids its warranty. It also completely wipes (formats) your Android phone’s internal memory including applications, contacts, SMS and MMS messages etc.
Click to expand...
Click to collapse
OK so I have no clue really want safestrap is really. I've only had phones that I could unlock my bootloader.
I guess my questions are is how much different is safestrap vs unlocked bootloader and did Verizon/Samsung lock this thing down to the point we can't unlock this thing.?
I just bought this phone on Verizon edge and had no knowledge about this thing being locked down.
Simple search will help.
Safe strap allows you to Flash stock ROMs and stock kernels. It is not a bootloader bypass. You cannot have recovery at this time. The chance of an actual bootloader unlock and/or recovery is slim.
We currently do have root.
If you want to do anything other than flash stock based ROMs and kernels (when SS is available, which is likely soon), then you should use a different device or get the Dev edition when it comes out.
You should do more research before putting that much money on a device down. I want the Note3 very much, but I much prefer a device with more flexibility, even if it isn't as badass.
I've had safe strap on my bionic and flashed asop ...but why would anyone on this device want asop??? ...that would not make a lot of..."touchwiz" lol.
Thanks for the reply. Yes your correct but no need to be an douche. Yes search answers questions but people who have used safestrap can sometimes provide better answers. This is the q&a section so that means you can ask questions. Anyways thanks for part of your reply.
Sent from my SM-N900V using xda app-developers app
jprovan1 said:
Thanks for the reply. Yes your correct but no need to be an douche. Yes search answers questions but people who have used safestrap can sometimes provide better answers. This is the q&a section so that means you can ask questions. Anyways thanks for part of your reply.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
I hope that was for the jerk and not the joke.....
Was for the jerk. I liked the joke
Sent from my SM-N900V using xda app-developers app
xdadevnube said:
Simple search will help.
Safe strap allows you to Flash stock ROMs and stock kernels. It is not a bootloader bypass. You cannot have recovery at this time. The chance of an actual bootloader unlock and/or recovery is slim.
We currently do have root.
If you want to do anything other than flash stock based ROMs and kernels (when SS is available, which is likely soon), then you should use a different device or get the Dev edition when it comes out.
You should do more research before putting that much money on a device down. I want the Note3 very much, but I much prefer a device with more flexibility, even if it isn't as badass.
Click to expand...
Click to collapse
This is wrong. Safestrap is a bootstrap recovery. It IS a "bootloader bypass" of sorts. Once everything is squared away, safestrap WILL allow flashing of non-stock ROMs and the execution of Kexec kernels. We will have access to almost everything available with an unlocked bootloader, except it will require room on our internal storage for the ROM files.
Banggugyangu said:
This is wrong. Safestrap is a bootstrap recovery. It IS a "bootloader bypass" of sorts. Once everything is squared away, safestrap WILL allow flashing of non-stock ROMs and the execution of Kexec kernels. We will have access to almost everything available with an unlocked bootloader, except it will require room on our internal storage for the ROM files.
Click to expand...
Click to collapse
AFAIK, it will not allow kexec, as that is a different exploit. Also, it cannot modify aboot. So you will not be able to install AOSP ROMs or anything but a modified stock kernel. Believe me, I would love to be wrong.
xdadevnube said:
AFAIK, it will not allow kexec, as that is a different exploit. Also, it cannot modify aboot. So you will not be able to install AOSP ROMs or anything but a modified stock kernel. Believe me, I would love to be wrong.
Click to expand...
Click to collapse
Hashcode has implemented kexec into nearly every device's safestrap. Also, AOSP is still possible with the stock kernel. You simply have to incorporate certain parts of the stock ROM. I did all of this on the Droid Bionic. I had an AOSP ROM before safestrap was even created. It had a couple Blur elements that were very minor, but required.
Do we loose safestrap if we take OTA upgrade to Kitkat (when it's available)?
Banggugyangu said:
Hashcode has implemented kexec into nearly every device's safestrap. Also, AOSP is still possible with the stock kernel. You simply have to incorporate certain parts of the stock ROM. I did all of this on the Droid Bionic. I had an AOSP ROM before safestrap was even created. It had a couple Blur elements that were very minor, but required.
Click to expand...
Click to collapse
I was thinking of the S4 that doesn't have kexec and cannot flash AOSP. It is reasonable to assume that the N3 could get kexec even although the S4 doesn't have it.
SS is not bootloader bypass. Many benefits of an unlocked bootloader will not be realized with SS. However, it should be a decent option for at least getting some ROMs. With kexec, then most people will be happy.
xdadevnube said:
I was thinking of the S4 that doesn't have kexec and cannot flash AOSP. It is reasonable to assume that the N3 could get kexec even although the S4 doesn't have it.
SS is not bootloader bypass. Many benefits of an unlocked bootloader will not be realized with SS. However, it should be a decent option for at least getting some ROMs. With kexec, then most people will be happy.
Click to expand...
Click to collapse
There is a huge difference when Hashcode has the phone in question. It's my understanding that this is the first Samsung phone he has had.
So he's stated that he plans to add kexec? That would be [email protected]$$.
Sent from my SM-N900V using Tapatalk
Okay! So I present you all with a question. I've read multiple threads on safestrap ROMs and id you have the MDL loader on how you can in-fact load custom ROMs.
But here's my biggest question, (I'm not sure if this should go in a dev sub-forum or here, but this seemed to make the most sense) but here it is, Is there any reason or advantage to stay on the MF3 bootloader firmware (4.2.2) which is locked to safestrap.
As in is there any progress whatsoever on the ability to install custom ROMs on this version, or any estimations or just plain and simple to not be rude, but is there remotely any way to install custom non-TW, non 4.2.2 ROMs, via safestrap on the firmware?
Or would I be better off upgrading via OTA to 4.3.3 so that I can utilize my Galaxy Gear, with retaining my root from SuperSU Pro "Survival Mode"? To be totally honest from the looks of the forums and Q+A recently most ATT users have done this exact thing.
That being said is there any sort of progress or planned progress/development towards the ability to create custom ROMs for these new MK2 bootloaders? I'm sure any ROM developer that wishes to continue to create ROMs that can be used by more than a slim picking would be on this development already but that's my questions!
Xeon.Jamal said:
Okay! So I present you all with a question. I've read multiple threads on safestrap ROMs and id you have the MDL loader on how you can in-fact load custom ROMs.
But here's my biggest question, (I'm not sure if this should go in a dev sub-forum or here, but this seemed to make the most sense) but here it is, Is there any reason or advantage to stay on the MF3 bootloader firmware (4.2.2) which is locked to safestrap.
As in is there any progress whatsoever on the ability to install custom ROMs on this version, or any estimations or just plain and simple to not be rude, but is there remotely any way to install custom non-TW, non 4.2.2 ROMs, via safestrap on the firmware?
Or would I be better off upgrading via OTA to 4.3.3 so that I can utilize my Galaxy Gear, with retaining my root from SuperSU Pro "Survival Mode"? To be totally honest from the looks of the forums and Q+A recently most ATT users have done this exact thing.
That being said is there any sort of progress or planned progress/development towards the ability to create custom ROMs for these new MK2 bootloaders? I'm sure any ROM developer that wishes to continue to create ROMs that can be used by more than a slim picking would be on this development already but that's my questions!
Click to expand...
Click to collapse
Hashcode the man behind safestrap Is working on bri ging safestrap to 4.3....other than that, other people may be working on it or they may not. 99% of rom devs dont have the skill to unlock a bootloader, not saying they are bad devs but it takes a completely differnt set of dev skills to unlock a bootloader...alot more coding
Sent from my SAMSUNG-SGH-I337 using Tapatalk
mg2195 said:
Hashcode the man behind safestrap Is working on bri ging safestrap to 4.3....other than that, other people may be working on it or they may not. 99% of rom devs dont have the skill to unlock a bootloader, not saying they are bad devs but it takes a completely differnt set of dev skills to unlock a bootloader...alot more coding
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Awesome, but there would still be no way to truly get ROMs like Dandroid or anything that has kitkat or non TW right? I know what you are saying about the devs. Its a totally different skillset. I hadn't thought of that. D'Oh! Thanks for the reply! I might upgrade to 4.3.3 so I can utilize my hear now!
So I just rooted my Verizon Samsung Galaxy Note 3 with Kingo. All I have installed so far is SuperSu Pro and Titanium backup. Im on android 4.3 and I have the MJE version. (which seems to be the most uncommon because I cant find any help anywhere, so im posting this thread). All I want to know is how or if I even can get the CyanogenMod rom on my phone. This is my first android device ever and I've had it for 5 months and Im definitely never going back to Apple devices. Anyway, I just rooted, I dont care about tripping Knox because I dont have a warranty anyways. I just need someone to explain to me how to get all the things I need including CM. From what ive read I need CWM and GAPPS.
khampton_03 said:
So I just rooted my Verizon Samsung Galaxy Note 3 with Kingo. All I have installed so far is SuperSu Pro and Titanium backup. Im on android 4.3 and I have the MJE version. (which seems to be the most uncommon because I cant find any help anywhere, so im posting this thread). All I want to know is how or if I even can get the CyanogenMod rom on my phone. This is my first android device ever and I've had it for 5 months and Im definitely never going back to Apple devices. Anyway, I just rooted, I dont care about tripping Knox because I dont have a warranty anyways. I just need someone to explain to me how to get all the things I need including CM. From what ive read I need CWM and GAPPS.
Click to expand...
Click to collapse
Slow down there. Lol. Do you have a developer edition Note 3 or just a regular retail Note 3 you purchased from Verizon?
Adam Browning said:
Slow down there. Lol. Do you have a developer edition Note 3 or just a regular retail Note 3 you purchased from Verizon?
Click to expand...
Click to collapse
Lol sorry Im very new to android. I got it from Verizon but i enabled Developer mode if thats what youre asking haha.
khampton_03 said:
Lol sorry Im very new to android. I got it from Verizon but i enabled Developer mode if thats what youre asking haha.
Click to expand...
Click to collapse
It's all good lol. No, developer mode just gives you some extra features if you want to debug your device. A developer edition Note 3 is a phone that was available directly from Samsung in a small quantity. It had the bootloader unlocked, which is a must for a AOSP ROM such as Cyanogenmod. Cyanogenmod requires a custom kernal, which a retail Note 3 (that you purchase through Verizon or another retail store) can not flash due to the locked bootloader. I would suggest peeking over in the Android Development section to check out the ROMs you are able to flash. Just steer clear of the ones saying for the developer edition or DE (for short). If you're wanting a ROM that has an AOSP feel to it though, check out Eclipse.
Here is a link for the Eclipse thread: http://forum.xda-developers.com/showthread.php?t=2620723
Adam Browning said:
It's all good lol. No, developer mode just gives you some extra features if you want to debug your device. A developer edition Note 3 is a phone that was available directly from Samsung in a small quantity. It had the bootloader unlocked, which is a must for a AOSP ROM such as Cyanogenmod. Cyanogenmod requires a custom kernal, which a retail Note 3 (that you purchase through Verizon or another retail store) can not flash due to the locked bootloader. I would suggest peeking over in the Android Development section to check out the ROMs you are able to flash. Just steer clear of the ones saying for the developer edition or DE (for short). If you're wanting a ROM that has an AOSP feel to it though, check out Eclipse.
Click to expand...
Click to collapse
So could I somehow unlock the bootloader??
khampton_03 said:
So could I somehow unlock the bootloader??
Click to expand...
Click to collapse
Many people have looked into that, and no luck so far. It is still locked for devices such as ours. Kind of sucks, I know. Almost every Android phone I've owned, I have ran Cyanogenmod on it. With Verizon being difficult about locking the bootloaders, and Samsung introducing Knox, I don't think we will see a bootloader unlock anytime soon, if ever. With the new 4.4.2 leak that BeansTown106 has made available for us here:
http://forum.xda-developers.com/showthread.php?t=2726558
Kernal modules are enabled, so we may have a workaround in the near future for the locked bootloader. I would suggest not taking the OTA for 4.4.2, but instead flashing the leaked 4.4.2 that is available via that thread. Once you take the OTA, it isn't known if you'll ever be able to flash this leak, which may allow for a modified kernal and therefore AOSP ROMs. I may be mistaken in some of the details, and someone can correct me if I have said something wrong in this, but this thread will explain it a little better:
http://forum.xda-developers.com/showthread.php?t=2727876
Adam Browning said:
Many people have looked into that, and no luck so far. It is still locked for devices such as ours. Kind of sucks, I know. Almost every Android phone I've owned, I have ran Cyanogenmod on it. With Verizon being difficult about locking the bootloaders, and Samsung introducing Knox, I don't think we will see a bootloader unlock anytime soon, if ever. With the new 4.4.2 leak that BeansTown106 has made available for us here:
http://forum.xda-developers.com/showthread.php?t=2726558
Kernal modules are enabled, so we may have a workaround in the near future for the locked bootloader. I would suggest not taking the OTA for 4.4.2, but instead flashing the leaked 4.4.2 that is available via that thread. Once you take the OTA, it isn't known if you'll ever be able to flash this leak, which may allow for a modified kernal and therefore AOSP ROMs. I may be mistaken in some of the details, and someone can correct me if I have said something wrong in this, but this thread will explain it a little better:
http://forum.xda-developers.com/showthread.php?t=2727876
Click to expand...
Click to collapse
So back to the beginning haha how do I flash a rom or what should I do since I just rooted and only have supersu haha
khampton_03 said:
So back to the beginning haha how do I flash a rom or what should I do since I just rooted and only have supersu haha
Click to expand...
Click to collapse
It all depends on what you want to do. How knowledgeable are you with rooting, Odin, and flashing in general?
Adam Browning said:
It all depends on what you want to do. How knowledgeable are you with rooting, Odin, and flashing in general?
Click to expand...
Click to collapse
Ive never flashed anything and I dont know how to use odin. Lol
khampton_03 said:
Ive never flashed anything and I dont know how to use odin. Lol
Click to expand...
Click to collapse
Lol. Oh goody. Well you're in for a lot of reading then. If you're already rooted and have supersu installed, then at least you have that part out of the way. The way that we install custom ROMs onto our phones (since the bootloader is locked) is by using Safestrap, developed by Hashcode. You can find any and all information you will need on it here:
http://forum.xda-developers.com/showthread.php?t=2517610
Safestrap gives you the ability to have multiple custom ROMs on your phone, without having to flash directly over your stock ROM (if you don't want). It is an application that you download onto your phone, you then open it up and install custom recovery. Once that is completed, you will then see a Safestrap screen everytime you turn on or restart your phone. I would suggest reading through or at least skimming the thread via the link provided above.
Once you have created a ROM slot and have it selected as the active slot, you can then proceed to install a custom ROM into that slot. Once you have everything set up, you can then switch between the custom ROM in "Slot x" to the stock ROM slot, giving you a cushion in case you completely screw up.
You're going to have to decide whether or not you want to stay on the 4.3 base, or update to the 4.4.2 base leak. The only advantages of either one are strictly your personal preference. There are a few that prefer the 4.4.2 base over the 4.3 base due to one reason or another. If you want to update the the newest 4.4.2 base leak though, follow the instructions provided via this link:
http://forum.xda-developers.com/showthread.php?t=2726558
Adam Browning said:
Lol. Oh goody. Well you're in for a lot of reading then. If you're already rooted and have supersu installed, then at least you have that part out of the way. The way that we install custom ROMs onto our phones (since the bootloader is locked) is by using Safestrap, developed by Hashcode. You can find any and all information you will need on it here:
http://forum.xda-developers.com/showthread.php?t=2517610
Safestrap gives you the ability to have multiple custom ROMs on your phone, without having to flash directly over your stock ROM (if you don't want). It is an application that you download onto your phone, you then open it up and install custom recovery. Once that is completed, you will then see a Safestrap screen everytime you turn on or restart your phone. I would suggest reading through or at least skimming the thread via the link provided above.
Once you have created a ROM slot and have it selected as the active slot, you can then proceed to install a custom ROM into that slot. Once you have everything set up, you can then switch between the custom ROM in "Slot x" to the stock ROM slot, giving you a cushion in case you completely screw up.
You're going to have to decide whether or not you want to stay on the 4.3 base, or update to the 4.4.2 base leak. The only advantages of either one are strictly your personal preference. There are a few that prefer the 4.4.2 base over the 4.3 base due to one reason or another. If you want to update the the newest 4.4.2 base leak though, follow the instructions provided via this link:
http://forum.xda-developers.com/showthread.php?t=2726558
Click to expand...
Click to collapse
So I am going to install Kitkat by watching the video on the thread. He said something about making sure the "MD5's match". What does that mean?
khampton_03 said:
So I am going to install Kitkat by watching the video on the thread. He said something about making sure the "MD5's match". What does that mean?
Click to expand...
Click to collapse
That, you don't really have to worry about honestly. I never check, though it may be good practice to. Just follow along with the video in the thread and you will be good to go. Just remember that after you install 4.4.2, you cannot flash 4.3 based ROMs. Also, there is a bug in Safestrap right now that renders the ROM slots somewhat useless, though you can attempt to use them at your own risk. If you want to flash one of the 4.4.2 based ROMs afterwards, it is suggested to back up the stock ROM, and flash the custom ROM in the stock ROM slot. All I can say is, goodluck. Lol. It is a fun process, though somewhat difficult at times. If you have anymore questions after the fact, just reply here. I'll help out as much as I can. It always puts a smile on my face to help convert an Apple fanboy/girl over to Android.
I know this question has been asked, and have been searching around the forums, but everything I am seeing says the reason that there are no real custom roms for this device is because the Bootloader is locked.. In my developer options on my device I am given the choice to enable OEM Unlock. Will this allow me to bypass the issues others are having? My Goal is to eventually learn what needs to be done so I can create my own rom or take a stock debloated rom and customize it completely to an end result I am happy with including UI/apps etc..
Thanks,
KaboneIsLegend
KaboneIsLegend said:
I know this question has been asked, and have been searching around the forums, but everything I am seeing says the reason that there are no real custom roms for this device is because the Bootloader is locked.. In my developer options on my device I am given the choice to enable OEM Unlock. Will this allow me to bypass the issues others are having? My Goal is to eventually learn what needs to be done so I can create my own rom or take a stock debloated rom and customize it completely to an end result I am happy with including UI/apps etc..
Thanks,
KaboneIsLegend
Click to expand...
Click to collapse
Nope. We can still have custom roms but we're just stuck with the one kernel required for root.
KaboneIsLegend said:
I know this question has been asked, and have been searching around the forums, but everything I am seeing says the reason that there are no real custom roms for this device is because the Bootloader is locked.. In my developer options on my device I am given the choice to enable OEM Unlock. Will this allow me to bypass the issues others are having? My Goal is to eventually learn what needs to be done so I can create my own rom or take a stock debloated rom and customize it completely to an end result I am happy with including UI/apps etc..
Thanks,
KaboneIsLegend
Click to expand...
Click to collapse
Bootloader is still locked. As of right now there is no way to unlock it so there is no way to have a custom ROM.
If you look at the development thread, you can see the options. One is a mod of the OEM ROM (PD8 only), but the other two are ROMs - on bade on 935U (echoe) and the other is a cleaned up modified Stock ROM.
With the locked bootloader you can only flash signed by Samsung ROMs - so no ASOP, CMxx ROMs. But by taking a stock ROM or the exiting unbloated one (with permission if you want to post your ROM - which would be welcome) it is something you can do right now (after you are rooted of course).
We also don't have custom recoveries, but flashing and backing up with FlashFire works pretty good, so go for it !
Binary100100 said:
Nope. We can still have custom roms but we're just stuck with the one kernel required for root.
Click to expand...
Click to collapse
Your talking the engineering boot.img ?
ShrekOpher said:
Bootloader is still locked. As of right now there is no way to unlock it so there is no way to have a custom ROM.
Click to expand...
Click to collapse
No way to force this?
gaww said:
If you look at the development thread, you can see the options. One is a mod of the OEM ROM (PD8 only), but the other two are ROMs - on bade on 935U (echoe) and the other is a cleaned up modified Stock ROM.
With the locked bootloader you can only flash signed by Samsung ROMs - so no ASOP, CMxx ROMs. But by taking a stock ROM or the exiting unbloated one (with permission if you want to post your ROM - which would be welcome) it is something you can do right now (after you are rooted of course).
We also don't have custom recoveries, but flashing and backing up with FlashFire works pretty good, so go for it !
Click to expand...
Click to collapse
I'm sure I know the answer to this, but can we fake signing? Also where would I need to go to research what needs to be done to remove the locked bootloader for my specific device? Maybe I can contribute something towards helping this get done. Are there any places people have shared their research?
Thanks guys for the awesome replies
KaboneIsLegend said:
I'm sure I know the answer to this, but can we fake signing? Also where would I need to go to research what needs to be done to remove the locked bootloader for my specific device? Maybe I can contribute something towards helping this get done. Are there any places people have shared their research?
Click to expand...
Click to collapse
People have been working on this since the device launched back in March. As far as I know, the files are cryptographically signed by Samsung, and the only way to bypass that is to find some kind of security exploit. As of yet, it hasn't been done. The leaked engineering kernel is basically the only known path at the moment to step outside of Samsung's locked down system.
andrewNY said:
People have been working on this since the device launched back in March. As far as I know, the files are cryptographically signed by Samsung, and the only way to bypass that is to find some kind of security exploit. As of yet, it hasn't been done. The leaked engineering kernel is basically the only known path at the moment to step outside of Samsung's locked down system.
Click to expand...
Click to collapse
Alright I will look into this then. I'm new to the android scene, but have experience with disassembly for applications, and reverse engineering for the older video game consoles. So why is there an option to oem unlock the phone if it doesn't really do that?
KaboneIsLegend said:
Alright I will look into this then. I'm new to the android scene, but have experience with disassembly for applications, and reverse engineering for the older video game consoles. So why is there an option to oem unlock the phone if it doesn't really do that?
Click to expand...
Click to collapse
Because not all variants have a locked bootloader. Just the US Qualcomm versions.
Binary100100 said:
Because not all variants have a locked bootloader. Just the US Qualcomm versions.
Click to expand...
Click to collapse
Thanks for that. I understand now.
We are rooted only because of the engineering bootloader. Stupid question time - with the problems with the kernel which are only partially fixed, ccouyld the kernel inself be modified or would it then be blocked by the bootloader.
There may custom kernels out there that would not work on a locked bootloader, but is the engineering kernel possibly open to modifications?