Database Develop

Problem with recovery z1 Help please.

Ok so i've made a mistake, fortunately I can still use my phone but i'm in unfamiliar territory.
What I did was download the 4.3 Rom by RomAur, installed the rom and the recovery as per the instructions within the thread, then rebooted to flashmode and entered flashtool so I could flash the kernel and baseband from 290, but made the mistake of excluding kernel and baseband and flashing the only other option which was BOOTBUNDLE, and since then my recovery has been inaccessible.
I've reflashed the dual recovery but it won't allow me to access it via the power on up or down method or the adb reboot recovery method.
I really can't continue with this phone or flash anything without a working recovery, does anyone have any idea how to get my recovery back please??
Any help would be appreciated.
I'm also wanting to unlock the bootloader but without a working recovery i'm a little hesitant to begin.
Phone: Sony Z1 C6903
Rom: RomAur v4.0
Bootloader status: Locked

Flash the kernel and baseband from 290 in flashtool then.

gregbradley said:
Flash the kernel and baseband from 290 in flashtool then.
Click to expand...
Click to collapse
Well i've gone and downgraded but used an unbranded ftf, which has now taken over my IMEI, which now reads 0000000000000000.
In a bad way here and stuck in work with limited internet, i'm now back on a 534 rom and feel like smashing this thing up.
Going home soon so will sit down and go through it all again from scratch, wish i'd just left it on my old monx rom now.
Bad times.
Any other ideas Greg ? Or anyone else?

just upgrade back, I believe you get your IMEI back that way..
The problem you are having is that you need unlocked boot to get a properly working recovery and root on 4.3

gregbradley said:
just upgrade back, I believe you get your IMEI back that way..
The problem you are having is that you need unlocked boot to get a properly working recovery and root on 4.3
Click to expand...
Click to collapse
Ah i see, well i'm downloading an ftf which is t-mobile 534, it's the closest thing i could get to EE, as at the moment i have no recovery and no root.
So should i do this in this order.
get this tmobile 534 and re root and get recovery, i imagine at this point my IMEI will still be missing (hopefully not) then what would you do?
Update to 4.3 by using one of those roms? and then unlock the bootloader? As thats where I ended up losing recovery, i'm thinking thats maybe down to me flashing boot bundle instead of kernel and baseband through flash tool.
Also doesn't unlocking the bootloader require system rw access?
And thanks by the way Greg, i appreciate your help.

Same thing happened to me. So I flashed Nordic 4.3 kept my data booted then flashed the kernel that comes with twrp. So far everything is great
Sent from my C6903 using xda app-developers app

1) Update to 4.3 using a FTF of your choice.
2) Unlock bootloader (This will wipe system and internal memory so have a backup of internal sdcard)
3) Flash any of the three kernels from the top of this post, I am using the third one with philz recovery.
4) enter recovery and flash the SuperSU.zip found in that same post.
Done.
You do not need root to unlock bootloader. The kernels have the recovery incorporated into them

pikeylfc said:
Same thing happened to me. So I flashed Nordic 4.3 kept my data booted then flashed the kernel that comes with twrp. So far everything is great
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
How do you flash a rom without a recovery though? sideload? Not sure, but nevermind, i ended up doing what i said i was going to do and now i'm back online and have re rooted but still on 4.2, will probably stay on 4.2 until 4.3 is 100%
Not being able to use things was too much of a pain in the arse.
Cheers by the way m8

gregbradley said:
1) Update to 4.3 using a FTF of your choice.
2) Unlock bootloader (This will wipe system and internal memory so have a backup of internal sdcard)
3) Flash any of the three kernels from the top of this post, I am using the third one with philz recovery.
4) enter recovery and flash the SuperSU.zip found in that same post.
Done.
You do not need root to unlock bootloader. The kernels have the recovery incorporated into them
Click to expand...
Click to collapse
Ahh that sounds simple enough, cheers m8, well i'll maybe give that a whirl as i'm at home and obviously my internal has been wiped anyway, got a back up in work so i'm running on minimum until i go back there.
While i'm in this state i may as well give it a go.
Cheers Greg, will let you know here if it worked out.

gregbradley said:
1) Update to 4.3 using a FTF of your choice.
2) Unlock bootloader (This will wipe system and internal memory so have a backup of internal sdcard)
3) Flash any of the three kernels from the top of this post, I am using the third one with philz recovery.
4) enter recovery and flash the SuperSU.zip found in that same post.
Done.
You do not need root to unlock bootloader. The kernels have the recovery incorporated into them
Click to expand...
Click to collapse
Well i've not attempted the unlock because after following the instructions it says in my phone that my bootloader cannot be unlocked.
I downloaded a vodafone UK ftf if that makes any difference, i got my phone from EE.
I noticed that you said to someone that they couldn't unlock the bootloader if it said that? Is there no way around it?

dladz said:
I noticed that you said to someone that they couldn't unlock the bootloader if it said that? Is there no way around it?
Click to expand...
Click to collapse
Bootloader Unlocking Allowed: NO
You can't unlock bootloader. Is impossible and no confirmation if even will be in some "unofficial" way.

eclyptos said:
Bootloader Unlocking Allowed: NO
You can't unlock bootloader. Is impossible and no confirmation if even will be in some "unofficial" way.
Click to expand...
Click to collapse
Yea i've just learnt that from Greg, that is ridiculous, I've never had a phone that this has happened to.
First and last Sony i ever buy, period.
Cheers.

dladz said:
Yea i've just learnt that from Greg, that is ridiculous, I've never had a phone that this has happened to.
First and last Sony i ever buy, period.
Cheers.
Click to expand...
Click to collapse
So if you know why you opening a new thread? We are here to learn, what the difference if I said what he said 100 times, is because I do not have 1000thanx. Still the source good and confirmed.

dladz said:
Yea i've just learnt that from Greg, that is ridiculous, I've never had a phone that this has happened to.
First and last Sony i ever buy, period.
Cheers.
Click to expand...
Click to collapse
Get your Sony phones from Vodafone, all 3 of my Xperia T's and my Z1 have been able to be unlocked.
Sent from my C6903 using XDA Premium 4 mobile app

eclyptos said:
So if you know why you opening a new thread? We are here to learn, what the difference if I said what he said 100 times, is because I do not have 1000thanx. Still the source good and confirmed.
Click to expand...
Click to collapse
Oh i'm sorry, i'm just coming to terms with myself being shafted by yet another company, i'm sorry i didn't click the damn thanks button, there i clicked it is that ok ?
I learnt about the answer to my thread after i'd heard from Greg, I don't plant one seed i plant several, I find out what i need to know quickly because my life doesn't give me time very often.
Apologies if i seem harsh, i'm not in a very good mood at the moment.

gregbradley said:
Get your Sony phones from Vodafone, all 3 of my Xperia T's and my Z1 have been able to be unlocked.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So what youre saying is that if the phones unlocked then the bootloader unlock will work?
I seriously can't have an android phone as restricted as this.

dladz said:
Apologies if i seem harsh, i'm not in a very good mood at the moment.
Click to expand...
Click to collapse
I understand.
dladz said:
I seriously can't have an android phone as restricted as this.
Click to expand...
Click to collapse
Agree with you.

dladz said:
So what youre saying is that if the phones unlocked then the bootloader unlock will work?.
Click to expand...
Click to collapse
No, just that Vodafone do not restrict the boot loader
Sent from my C6903 using XDA Premium 4 mobile app

gregbradley said:
No, just that Vodafone do not restrict the boot loader
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Is there any solid data on how/why some Z1s cannot be bootloader unlocked? I have a C6906 from Overseas Electronics which I think was sourced from Canda and cannot be BL unlocked, though it's sim unlocked and otherwise works fine on AT&T LTE.
I found a thread/post here mentioning that Sony may be able to "fix" these devices (and possibly for free, at that). I'm going to run down that angle, but if there's any technical data on what could be preventing the BL unlock I'd be very interested in doing some legwork on my own.

xasbo said:
Is there any solid data on how/why some Z1s cannot be bootloader unlocked? I have a C6906 from Overseas Electronics which I think was sourced from Canda and cannot be BL unlocked, though it's sim unlocked and otherwise works fine on AT&T LTE.
I found a thread/post here mentioning that Sony may be able to "fix" these devices (and possibly for free, at that). I'm going to run down that angle, but if there's any technical data on what could be preventing the BL unlock I'd be very interested in doing some legwork on my own.
Click to expand...
Click to collapse
Not too sure mate, think its coded not to be unlockable, in which case someone would have to do quite a bit of digging to undo whatever was done. And seeing as that the vast majority of people knew to buy from a source that doesn't have the NO to unlocking the BL I would say that its not going to happen any time soon. I usually do a bit of digging before I buy a phone, rushed into this one and I'm paying for it now.
I'll check out that link you put up, maybe there's hope yet.
Edit: as for the link you put up, that's just for the sim lock.
If you want an unlockable phone then you'll either have to claim from a 3rd party insurer an hope that they give you an unlocked phone or contact Sony for an RMA and hope that they give you one. Otherwise I can't see it.
But in all fairness your missing custom kernels and aosp type ROMs. Most everything else will work fine, including all (well most) the ROMs that are in the android development section, so that's not a total loss by any means.
When roots fixed completely for 4.3, well see more.
Sent from my C6903 using XDA Premium 4 mobile app

Why Are There So Many Bricked Nexi?

Is it because people are trying to downgrade their bootloaders? In general, you should never do that on a motorola phone although sometimes you can get away with it.
Or is it because people are messing around with their phones without unlocking the bootloaders?

JulesJam said:
Is it because people are trying to downgrade their bootloaders? In general, you should never do that on a motorola phone although sometimes you can get away with it.
Or is it because people are messing around with their phones without unlocking the bootloaders?
Click to expand...
Click to collapse
I believe they are relocking the bootloader, and then not being able to unlock again causing it to bootloop

jiv101 said:
I believe they are relocking the bootloader, and then not being able to unlock again causing it to bootloop
Click to expand...
Click to collapse
There are two separete issues. One is what you're describing, and one is the device just completely dying - "you can't even get to fastboot". The first one has thread here, as for the second one, there really isn't a comprehensive thread yet. I'm not even sure what is causing it anymore, at first I thought the bootloader doesn't like being downgraded (which you can do accidentally very easily, since CM ZIPs contain bootloader, for some reason), but there are people reporting bricked devices with pretty much no cause :/

JulesJam said:
Is it because people are trying to downgrade their bootloaders? In general, you should never do that on a motorola phone although sometimes you can get away with it.
Or is it because people are messing around with their phones without unlocking the bootloaders?
Click to expand...
Click to collapse
This is a Nexus phone made by motorola, not a Motorola phone. Big difference.
Sent from my Nexus 6 using XDA Free mobile app

Tasssadar said:
as for the second one, there really isn't a comprehensive thread yet. I'm not even sure what is causing it anymore, at first I thought the bootloader doesn't like being downgraded (which you can do accidentally very easily, since CM ZIPs contain bootloader, for some reason), but there are people reporting bricked devices with pretty much no no cause :/
Click to expand...
Click to collapse
Are they sure of what bootloader versions they had?
I know this is a Nexus device but it has a Motorola bootloader. It is safest not to downgrade the bootloader OR the partition table from my experience with the Moto X. I know there were some exceptions and that is how jcase was able to get root on at least one bootloader version, but the general rule was don't try to downgrade the bootloader or the partition table to stay out of trouble.
I was thinking of making a post on General with this advice in it for people to help them stay out of trouble:
1) know your bootloader and partition table versions before you flash anything and if you aren't sure what will happen, do not attempt to downgrade either the bootloader or the partition table; and
2) make sure OEM unlock and USB debugging are enabled before you flash anything.
I understand that the advice above may be overkill for those who know what they are doing, but clearly people who don't know what they are doing are bricking their devices. I feel bad for them and don't want to see more people in that situation.

I was bricked by CM. Last nexus I had with cm was galaxy nexus so I don't know how cm is done on nexus 5 but why do they reflash bootloader and radios on each update. It wasn't that way before. Thats what bricked my device. I just got confirmation that I'm getting my replacement device.

akellar said:
This is a Nexus phone made by motorola, not a Motorola phone. Big difference.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Still a Motorola bootloader

rootSU said:
Still a Motorola bootloader
Click to expand...
Click to collapse
Not in the manner that is being discussed. It can't be downgraded because of the new security implemented in 5.1, not because moto is involved.
Sent from my Nexus 6 using XDA Free mobile app

akellar said:
Not in the manner that is being discussed. It can't be downgraded because of the new security implemented in 5.1, not because moto is involved.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Fair enough

[Q] Best way to get off of 5.1 LMY47D?

Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!

you can always use fastboot to go back to 5.0.1

stas333 said:
you can always use fastboot to go back to 5.0.1
Click to expand...
Click to collapse
Word, thanks!
Just curious then... how are all these people bricking by downgrading? Does the wugfresh toolkit not use the fastboot method to downgrade or something?

i flashed 5.0.2 roms after flashing a 5.1 rom, and my device isnt bricked.

simms22 said:
i flashed 5.0.2 roms after flashing a 5.1 rom, and my device isnt bricked.
Click to expand...
Click to collapse
Hmm, I guess I am confused as to what is causing the bricks for those that downgraded? I'll go ahead and do that right now but... I've read direct quotes from others stating that downgrading a Motorola bootloader is an instant brick and others have said it has happened to them.

EmperorX said:
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
Click to expand...
Click to collapse
Unlock your bootloader and enable oem-unlock in developer options and you can flash any image in fastboot.

gee2012 said:
Unlock your bootloader and enable oem-unlock in developer options and you can flash any image in fastboot.
Click to expand...
Click to collapse
Thanks man, I think I will just wait for the M images to be posted... Any harm in relocking my bootloader after I get them installed? I've read that too... though, some people it works out for, others not so much.

EmperorX said:
Word, thanks!
Just curious then... how are all these people bricking by downgrading? Does the wugfresh toolkit not use the fastboot method to downgrade or something?
Click to expand...
Click to collapse
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
EmperorX said:
Thanks man, I think I will just wait for the M images to be posted... Any harm in relocking my bootloader after I get them installed? I've read that too... though, some people it works out for, others not so much.
Click to expand...
Click to collapse
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flash anything anymore if an incident would occur and you`re without a OS.

gee2012 said:
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
Click to expand...
Click to collapse
I wasn't planning on it, just curious how all these people are bricking?

gee2012 said:
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flashing anymore if an incident would occur.
Click to expand...
Click to collapse
Also, I will absolutely need to relock my bootloader per organizational policies.

EmperorX said:
I wasn't planning on it, just curious how all these people are bricking?
Click to expand...
Click to collapse
Most of them because they wiped their system and couldn`t flash a image anymore because oem-unlock wasn`t enabled as i heard.

Sweet, successful downgrade!

I saw it mentioned in another thread that now that I have successfully downgraded I may brick when I get the T-Mobile 5.1 OTA.
Is there any credence to this? I am back on 5.0.1 now, relocked my bootloader, etc. Just wanted to make sure. It doesn't seem as if that would be the case to me but... Just wanted to be safe rather than sorry.
Thanks!

Disregard! Got it handled. Thanks guys!

Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flash anything anymore if an incident would occur and you`re without a OS.
Click to expand...
Click to collapse
Couldn't agree with you more....specially on the sentence I highlighted in bold. Got into the same problem yesterday. I excitedly upgraded from LMY47D to LMY47E. Later realised it's a Verizon image. So, thought let me go down to 5.0.1 and get a OTA - the "proper" way to upgrade.
While flashing, it didn't let me downgrade my bootloader. Mistake #1.
Then continued to flash the remaining images (radio, recovery, cache, system, userdata).
Then I locked my bootloader, so that it continues to look like "fresh out of the box". Mistake #2.
Then when I rebooted, it was constantly giving the error that NFC has failed and the Phone has failed. I couldn't get past those errors. It was continuously giving me that error.
It wouldn't let me unlock the bootloader, as the new bootloader (5.1) needs the OEM unlocking enabled in Developer's options.
Then I realised that there was a slight gap of time between showing the NFC & Phone error and the next set of NFC & Phone error. Using that, with great difficulty, setup the phone - going through every tap using the gap that was available between 2 sets of errors. Then I unlocked the developer's options, then enabled the OEM unlocking and finally got my bootloader unlocked.
Torrid - Horrible task. Was scared I had bricked my phone....but through some hard work (and sleepless night - up until 6am), got this finished.
Guys - seriously suggesting you NOT to lock the bootloader, IF you have unlocked the bootloader. Speaking with experience. Learn from my mistakes.
EDIT: I realised what the problem was and why NFC & Phone were erroring out. It was because I forgot to flash the Boot image. So, Bootloader & Boot were 5.1 & the rest were 5.0.1

EmperorX said:
Sweet, successful downgrade!
Click to expand...
Click to collapse
How did you downgraded the bootloader??

Downgrade of bootloader is not possible.
Sent from my Nexus 6 using XDA Free mobile app

EmperorX said:
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
Click to expand...
Click to collapse
How about you just leave it on D?
What do you think you will gain by changing to M?

Nexus 6 Cyanogenmod carrier ROM ?

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

What keeps us from flashing H815 and h811 Roms onto our phones?

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