I looked on Cyanogenmod's website below:
https://download.cyanogenmod.org/?device=shamu
and it just has 1 ROM for Nexus 6. I have Nexus 6 for Sprint. Is there only 1 version of the ROM that works for all carriers ?
My old Galaxy S4 has many different builds for Sprint, ATT, Verizon, etc.... wasn't sure if Nexus has the same set up.
Yes, applies to all N6 variants.
thats because every sgs4 has a different setup for different carriers. we only have one nexus 6, and its the same for every carrier.
simms22 said:
thats because every sgs4 has a different setup for different carriers. we only have one nexus 6, and its the same for every carrier.
Click to expand...
Click to collapse
I didn't have a locked bootloader with Sprint Galaxy S4. If I were to restore the Nexus 6 back to stock to do an OTA update to update everything, then re-root and put a new custom ROM does the bootloader need to be re-locked, or can the factory .img be suffice to do an OTA ?
I'm still trying to learn how to do this as it is much different than the Samsung GS4. I saw there is a Nexus Toolkit by wug fresh. Is there any benefit to doing these processes by adb vs just using this progra which seems easier ?
mikeprius said:
I didn't have a locked bootloader with Sprint Galaxy S4. If I were to restore the Nexus 6 back to stock to do an OTA update to update everything, then re-root and put a new custom ROM does the bootloader need to be re-locked, or can the factory .img be suffice to do an OTA ?
I'm still trying to learn how to do this as it is much different than the Samsung GS4. I saw there is a Nexus Toolkit by wug fresh. Is there any benefit to doing these processes by adb vs just using this progra which seems easier ?
Click to expand...
Click to collapse
you dont use adb for it, you use fastboot. and doung it right vs a toolkit.. toolkits dont teach you anything, and can mess things up.
simms22 said:
you dont use adb for it, you use fastboot. and doung it right vs a toolkit.. toolkits dont teach you anything, and can mess things up.
Click to expand...
Click to collapse
Does the bootloader need to be locked to do OTAs or does the stock ROM with leaving the bootloader unlock suffice for an OTA ?
mikeprius said:
Does the bootloader need to be locked to do OTAs or does the stock ROM with leaving the bootloader unlock suffice for an OTA ?
Click to expand...
Click to collapse
bootloader can be locked or unlocked, it doesnt matter. but i recommend that you keep it unlocked forever, as it can save your phone in certain situations. and having it locked can be the end of your device, in the same situations.
simms22 said:
bootloader can be locked or unlocked, it doesnt matter. but i recommend that you keep it unlocked forever, as it can save your phone in certain situations. and having it locked can be the end of your device, in the same situations.
Click to expand...
Click to collapse
Ok. That's what I was planning on doing once it becomes unlocked. I was going to have it set like my previous GS4 and just toggle custom ROMs from there. When you mention having it locked, are you referring to when people have re-locked the bootloader then had an error flashing the stock custom ROM thus bricking the phone ? That's what worries me. Looks like the security is more stringent on the new Nexus vs. older versions.
mikeprius said:
Ok. That's what I was planning on doing once it becomes unlocked. I was going to have it set like my previous GS4 and just toggle custom ROMs from there. When you mention having it locked, are you referring to when people have re-locked the bootloader then had an error flashing the stock custom ROM thus bricking the phone ? That's what worries me. Looks like the security is more stringent on the new Nexus vs. older versions.
Click to expand...
Click to collapse
i was actually refering to it because of the unlock setting that has to be ticked to unlock. some stock users got caught in a bootloop, then cant boot up to tick the setting, to fix their bootloop. since it cant get unlocked, their phones are a "brick".
simms22 said:
i was actually refering to it because of the unlock setting that has to be ticked to unlock. some stock users got caught in a bootloop, then cant boot up to tick the setting, to fix their bootloop. since it cant get unlocked, their phones are a "brick".
Click to expand...
Click to collapse
Is this what happened to this person below ?:
http://forum.xda-developers.com/nexus-6/help/help-nexus-6-brick-t3227126
Since the stock rom did not have developer options "checked" then the bootloader can't be unlocked ? How can you tick the OEM unlock if it is in a bootloop ?
mikeprius said:
Is this what happened to this person below ?:
http://forum.xda-developers.com/nexus-6/help/help-nexus-6-brick-t3227126
Since the stock rom did not have developer options "checked" then the bootloader can't be unlocked ? How can you tick the OEM unlock if it is in a bootloop ?
Click to expand...
Click to collapse
you cant, thats why i said that you should keep it unlocked.
simms22 said:
you cant, thats why i said that you should keep it unlocked.
Click to expand...
Click to collapse
Ok that makes sense. What is the purpose of having the bootloader come locked in a stock phone then ? What does it actually do ? Prevents root ? I probably took it for granted mine was always unlocked before so all I had to do was worry about flashing the proper carrier ROM
mikeprius said:
Ok that makes sense. What is the purpose of having the bootloader come locked in a stock phone then ? What does it actually do ? Prevents root ? I probably took it for granted mine was always unlocked before so all I had to do was worry about flashing the proper carrier ROM
Click to expand...
Click to collapse
Security.
Security in that if stolen your phone cannot be made to work for someone else...
Someone can (and likely will [emoji14]) correct me if I am wrong... But does little to secure your data...ESPECIALLY if you stay encrypted.
scryan said:
Security in that if stolen your phone cannot be made to work for someone else...
Someone can (and likely will [emoji14]) correct me if I am wrong... But does little to secure your data...ESPECIALLY if you stay encrypted.
Click to expand...
Click to collapse
It does nothing to secure data from remote access, but it will protect data (if set with a password) from physical access, providing they do not know the password. The bootloader being unlocked, with no password on encryption would allow them to flash a custom recovery and pull the data off. This will be decrypted on the fly. So it works in conjunction with Encryption. To secure data from physical access, you need both.
IF your bootloader is unlocked and you have no password, you may aswell not be encrypted
Related
I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):
You should check out the 'Chinese Middleman' thread. If you get the bootloader unlocked you should be able to fix anything.
I can't unlock the bootloader since this is not a Dev edition. Unless something has changed, I'll check it.
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Even though it's not a Dev edition?
Yes you should be able too.
Sent from my XT1053 using Tapatalk
danman421 said:
Even though it's not a Dev edition?
Click to expand...
Click to collapse
All XT1053s can be unlocked, yes. Additionally, if you follow my advice, you don't NEED to unlock. If one of the commands fails, simply skip to the next as I previously advised, and TRY flashing with RSD Lite after you have run the commands I listed.
If you want to check and make sure fastboot is working, type:
fastboot devices
if you see your phone and it's serial number listed, you fastboot IS properly communicating with your phone.
You do not need to unlock your BL to do any of this...but if you are interested in ROOTING, you will need to.
All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?
shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.
danman421 said:
All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?
Click to expand...
Click to collapse
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
danman421 said:
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.
Click to expand...
Click to collapse
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.
samwathegreat said:
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.
Click to expand...
Click to collapse
So if I am reading this correctly, there is no way to keep all of my data and take the update?
danman421 said:
So if I am reading this correctly, there is no way to keep all of my data and take the update?
Click to expand...
Click to collapse
You can attempt to, by either editing the XML in the SBF and removing the line that says "erase userdata", or by skipping the erase userdata if you use the manual method, but either way CAN mess everything up.
You used an EXPLOIT previously. Any time you use an exploit, you should -expect- to have to wipe everything and re-install from scratch if you want to get back to stock in order to be able to take updates. Keep this in mind if you use any exploits in the future.
Hi! This hasn't seemed to spelled out yet..... But many Moto x's can be unlocked, not just dev editions. However, you stated in the opening post that you have a Verizon Non dev, which can not be unlocked. Only way is to pay the "China middleman" (See thread in general with that name).
And personally.... I would stay on 4.2.2 and do the Slapmymoto method to get root and write protection disabled. That is the best root scenario, aside from unlocking the bootloader.
If you update to 4.4.2 or higher, you will have write protection enabled always, and no root, or sorta root with towelroot and pie. But that will limit what you can do.
See the How do I root my phone sticky thread in general for your options.
I should have posted earlier. I ran RSDLite and put the newest version on. I am unrooted. My Moto X is a Sept '13 version the the middleman probably wont work anyways. Its not worth it with this phone, im tired of the rooting, I guess im at that point in my life... Thanks for all your help though guys!
danman421 said:
I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):
Click to expand...
Click to collapse
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.
You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.
KidJoe said:
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.
Click to expand...
Click to collapse
Good catch! ?
OP... Perhaps full disclosure of what you have done on the phone would help.
Or is that how it was?
If it's been downgraded to 4.2.2 after being on 4.4.2... As said above.... You could brick now... Especially if you OTA.
I'd tread lightly at this point.
danman421 said:
You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.
Click to expand...
Click to collapse
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.
Yes, that was a good catch. What I did was RSD Lite to 4.4.4 now which reset all my data.
KidJoe said:
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.
Click to expand...
Click to collapse
Correct, I do not need help anymore but thank you.
Hello Guys
Do you relock the bootloader after root of nexus 6?
It's probably not the best idea. Though now the "OEM unlocking" option seems to stick after a reboot on 5.1+ it's probably not as risky as it was.
Oniska said:
Hello Guys
Do you relock the bootloader after root of nexus 6?
Click to expand...
Click to collapse
I'm going to go ahead and just say no. No reason to relock other than RMA or resale. Best to leave unlocked just because if you run into issues, it's much easier to recover if your bootloader is unlocked.
Never relock unless you are on a stock image
I have never relocked a bootloader, ever.
Old thread I realize, but wouldn't this be useful to keep the anti-theft feature intact while rooted? And furthermore, does it actually work? I.e. does it leave root intact after it's locked but forbid flashing new roms to circumvent anti-theft. (I own a Nexus 6P by the way, but imagine the regular 6 has an updated bootloader with the same features.)
Rakeesh_j said:
Old thread I realize, but wouldn't this be useful to keep the anti-theft feature intact while rooted? And furthermore, does it actually work? I.e. does it leave root intact after it's locked but forbid flashing new roms to circumvent anti-theft. (I own a Nexus 6P by the way, but imagine the regular 6 has an updated bootloader with the same features.)
Click to expand...
Click to collapse
the problem is if your bootloader is locked, and you ho into a bootloop for amy reason, and your oem unlock option is not enabled in the developer options, then you bricked your phone. most people that lock their bootloaders, or have them locked, dont enable the oem unlick option. if thats not enabled, and youre in a bootloop, you cant flash a factory image or do anything else to fix it.
Rakeesh_j said:
Old thread I realize, but wouldn't this be useful to keep the anti-theft feature intact while rooted? And furthermore, does it actually work? I.e. does it leave root intact after it's locked but forbid flashing new roms to circumvent anti-theft. (I own a Nexus 6P by the way, but imagine the regular 6 has an updated bootloader with the same features.)
Click to expand...
Click to collapse
If you are encrypted, the only thing a locked bootloader adds is the ability to flash a custom boot.img that can decrypt your data (which doesn't exist). It's a very hypothetical scenario. The problems with locking the bootloader are as mentioned above by @simms22
Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
H4X0R46 said:
Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
Click to expand...
Click to collapse
Thing is, when your bootloader is unlocked, the device is almost unbrickable. Also, you can be unlocked, 100% stock and still get OTA's if you want. If you have a locked bootloader, mess something up and end up in a bootloop, and can't boot to android, you're stuck.
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
H4X0R46 said:
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
Click to expand...
Click to collapse
Yes to all your questions.
Unlock it, its free insurance and wont change or harm a thing.
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
simms22 said:
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
Click to expand...
Click to collapse
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
danarama said:
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
Click to expand...
Click to collapse
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Evolution_Tech said:
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Click to expand...
Click to collapse
Well it shouldn't matter. When you tick that box, it writes the change to mmcblk0p18, which is OS independent. Now that booting the rom doesn't revert that partition, if it is ticked once, it shouldn't matter if there is an OS at all.
H4X0R46 said:
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Click to expand...
Click to collapse
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
cam30era said:
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
Click to expand...
Click to collapse
Scripts don't check recovery. It's just the OTA zip won't work without it.
-Jonny- said:
here you go!
Click to expand...
Click to collapse
Correct. Just taking this shortcut.
Great! Thanks guys! Appreciate all the help and support on this! I would HATE to brick a $700 device! Haha
Sent from my Nexus 6
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
H4X0R46 said:
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
Click to expand...
Click to collapse
N6 is ARM. Arm 64 is for 64 bit devices such as the N9.
Clarification question
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
alryder said:
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
Click to expand...
Click to collapse
Correct.
Does anyone know if there is a zip that is recovery flashable which can lock and relock the bootloader through recovery? I guess what I'm wondering about is there is a Aroma zip HTC users use called Guru which can lock and unlock the bootloader without a the need for a PC. If no big deal....
tapPeD fROM my neXus 6
probably possible, but its a god damn horrible idea to re-lock the bootloader once you have made ANY modifications to the phone.... We get enough "Phone wont boot for me to switch on "Allow OEM Unlock and bootloader is locked" threads.
The only thing relocking your phone does is prevent a thief from wiping it so they can use it. At that point your phone is stolen anyways, you really want to limit your ability to fix it should you have problems just to stop someone else from using the phone once you no longer have it in the first place?
I guess the only reason why I was asking is because I'm assuming you cannot use Android Pay while the bootloader is unlocked. Is that true or no? Otherwise, I completely agree.
tapPeD fROM my neXus 6
well, if you need a zip to unlock your bootloader via recovery, then itll never exist, as you need to unlock your bootloader before flashing a recovery.
andrewjt19 said:
I guess the only reason why I was asking is because I'm assuming you cannot use Android Pay while the bootloader is unlocked. Is that true or no? Otherwise, I completely agree.
tapPeD fROM my neXus 6
Click to expand...
Click to collapse
you can use android pay with an unlocked bootloader. In fact the only thing that prevents android pay from working is root access or core system file modification (xposed level).
I've currently got the viper/dolby atmos mod installed (adds apps to /system), docs sheets and slides uninstalled from system(deletes things from system) , elementalx (doesn't mod system) and cataclysm installed (mods system.. lightly I guess?) and android pay still works if you disable root.
Also you can use this app to test if android pay will work adding mods 1 by 1 without having to go through the card adding and pay testing. If it shows green android pay should work.
andrewjt19 said:
I guess the only reason why I was asking is because I'm assuming you cannot use Android Pay while the bootloader is unlocked. Is that true or no? Otherwise, I completely agree.
tapPeD fROM my neXus 6
Click to expand...
Click to collapse
No. Android Pay is based off your ROM not the bootloader. I flashed my phone back to stock with a unlocked bootloader and it worked (well it would have but my bank is not participating in it yet). You can also do OTA updates on a stock ROM with an unlocked bootloader.
I know that this has been said before but I agree with it, there's no point in re-locking your bootloader unless you have to send it back in or are turning it back to 100% stock. Just causes more problems than it's worth.
We have flashify/flashfire, so why can't we just flash using these?
The locked bootloader won't allow booting an unsigned kernel.
l33tlinuxh4x0r said:
The locked bootloader won't allow booting an unsigned kernel.
Click to expand...
Click to collapse
But we can install custom Roms?
cjc2040 said:
But we can install custom Roms?
Click to expand...
Click to collapse
If the rom is using the stock kernel there is no problem. That is why we don't have AOSP like CM 13 yet.
In theory you could flash a rom form another G4 but your radio probably won't work. I remember that with the G3 you could do this and then there was a fix for the radio to get it working but they also have an unlocked bootloader.
l33tlinuxh4x0r said:
If the rom is using the stock kernel there is no problem. That is why we don't have AOSP like CM 13 yet.
In theory you could flash a rom form another G4 but your radio probably won't work. I remember that with the G3 you could do this and then there was a fix for the radio to get it working but they also have an unlocked bootloader.
Click to expand...
Click to collapse
I see so then what is preventing us from unlocking the bootloader or even installing TWRP. I know TWRP usually requires unlocked bootloader but can't we set it to read AND write permissions?
cjc2040 said:
I see so then what is preventing us from unlocking the bootloader or even installing TWRP. I know TWRP usually requires unlocked bootloader but can't we set it to read AND write permissions?
Click to expand...
Click to collapse
TWRP has a custom kernel. It is pretty much a kernel image so you need an unlocked bootloader. As far as unlocking the bootloader, it has a encryption key. If we had that we would be good but we don't so we need to bypass it somehow.
I think that our best bet is to wait and see if the sprint g5 gets unlocked and try to use that. Other than that I remember with the droid razr maxx that I had they used a program called safestrap instead of TWRP. It essentially took the stock kernel and loaded whatever you told it to software wise. However it had a boot screen which took 5 seconds longer to boot. Kind of like dual booting on a PC with grub.
P.S. I'm looking to get a Sprint G4 and start development on it but they are still too expensive.
l33tlinuxh4x0r said:
TWRP has a custom kernel. It is pretty much a kernel image so you need an unlocked bootloader. As far as unlocking the bootloader, it has a encryption key. If we had that we would be good but we don't so we need to bypass it somehow.
I think that our best bet is to wait and see if the sprint g5 gets unlocked and try to use that. Other than that I remember with the droid razr maxx that I had they used a program called safestrap instead of TWRP. It essentially took the stock kernel and loaded whatever you told it to software wise. However it had a boot screen which took 5 seconds longer to boot. Kind of like dual booting on a PC with grub.
P.S. I'm looking to get a Sprint G4 and start development on it but they are still too expensive.
Click to expand...
Click to collapse
Development is dead on this device. We can make stock modified system images hardly call it a rom. Ure wasting ure time buying this. There will not be a bootloader unlock. Cant be hacked as of yet some of the worlds greatest android minds have tried may even still be. Fact is its prob not gonna happent any time soon. And the solution will either come from g5 or whatever they make after that. The bootloader partitions are to highly encrypted to hack. It does it really sucks but like i said lost cause