Database Info

[Q] [E C1505] [SOLVED] A bunch of Questions

Hi guys,
i'm somewhat of a noob when it comes to Android devices, so please excuse my stupid questions.
First some facts about my device:
ROOT: Enabled
BOOTLOADER: Locked and not changeable
ROM: Latest available official release
(hope that helps at least a bit)
#1: Is it possible to bypass the bootloader lock via root? If so, how?
#2: If there is no way to bypass the lock, is it possible to modify the rom anyway? Because i want to add the swapon/swapoff functionality to expand the available ram via a swap partition on my external SD card. (already checked via terminal if swapon/swapoff is available)
Thank you in advance for your help. I hope there's a solution to my problem.

BrainInBlack said:
Hi guys,
i'm somewhat of a noob when it comes to Android devices, so please excuse my stupid questions.
First some facts about my device:
ROOT: Enabled
BOOTLOADER: Locked and not changeable
ROM: Latest available official release
(hope that helps at least a bit)
#1: Is it possible to bypass the bootloader lock via root? If so, how?
#2: If there is no way to bypass the lock, is it possible to modify the rom anyway? Because i want to add the swapon/swapoff functionality to expand the available ram via a swap partition on my external SD card. (already checked via terminal if swapon/swapoff is available)
Thank you in advance for your help. I hope there's a solution to my problem.
Click to expand...
Click to collapse
Can u plzz upload a screenshot of the page of ur device's bootloader status. Because as far as i know xperia e's bootloader isn't harlocked and can be unlocked easily.

Well, i don't known how to take a screenshot, at least on an android device.
Gesendet von meinem C1505 mit Tapatalk

BrainInBlack said:
Well, i don't known how to take a screenshot, at least on an android device.
Gesendet von meinem C1505 mit Tapatalk
Click to expand...
Click to collapse
Hold the volume down button + power button simultaneously .
Have a nice day
Sent from my C1505 using XDA Premium 4 mobile app

Img .tapatalk. com/d/14/01/24/uqe6y4ez.jpg
(had to bypass the 10 post linking thing)
Thanks again

BrainInBlack said:
Img .tapatalk. com/d/14/01/24/uqe6y4ez.jpg
(had to bypass the 10 post linking thing)
Thanks again
Click to expand...
Click to collapse
You're right - your phone isn't allowed a bootloader unlock.
Without bootloader unlock, you can't change ROMs, but you can install ICS, which is a bit faster than Jelly Bean, even slightly more than CyanogenMod. In fact, even with an unlocked bootloader, I'm using ICS. Here's how: http://forum.xda-developers.com/showthread.php?t=2579233
Now, you said you're a noob when it comes to Android, so here's how to flash an FTF:
This process will remove all installed apps, contacts and settings. Any music, stuff on the internal storage (the one for music etc.) or the microSD will be preserved.
0. Make sure you're on Windows 7 or below. For some reason, this doesn't work with Windows 8 or 8.1, so you'll have to get a 7 PC somehow.
1. Download Androxyde's Flashtool here: http://forum.xda-developers.com/showthread.php?t=920746 (use the unrestrict.li link, it's better)
2. Install it. By default, it is installed to C:\Flashtool. Open this folder, and then the "drivers" one. You'll see a driver setup file. Install the Flashtool and Fastboot drivers (in the list, they're on the bottom).
3. Now go back to the Flashtool folder, and open "firmwares". Put your FTF file here.
4. Open Flashtool. Click the lightning icon. Ensure that Flashmode is selected, and press OK. Choose the C1605 11.1.A.0.68 file, and press Flash.
5. When it tells you to, turn off your phone. Plug in the USB cable into your computer. Hold volume down (do not hold the power button), and (point of no return now) plug the phone into the USB cable connected to your phone. The notification light will glow green, and hopefully everything will start flashing. When the Flashtool window tells you to disconnect your phone and turn it on, do so. Set it up, and you're on ICS!
If you want to go back to Jelly Bean, download this FTF: https://www.mediafire.com/?3fmmkbmlqtjd6cy and put it into the "firmwares" folder. Now follow the guide step 4 onward, but select "11.3.A.2.23" for Jelly Bean.
Whew, long post.

So, in principle i downgrade the device to ics with an unlocked bootloader and then can flash a custom rom that is jb based, with all features i need to expand the ram?
BrainInBlack from a C1505

BrainInBlack said:
So, in principle i downgrade the device to ics with an unlocked bootloader and then can flash a custom rom that is jb based, with all features i need to expand the ram?
BrainInBlack from a C1505
Click to expand...
Click to collapse
No, ICS won't enable you to unlock your bootloader OR install CWM OR install a custom ROM. ICS is faster than any other custom ROM (other than XboosT, which is basically ICS on steroids), so if you can't have custom ROMs, the next best thing is ICS.

Another noob's question:
I installed Xposed a few days ago on my c1505 (stock firmware, locked bl). It worked perfectly. But i've read from another post that if i remove it my phone won't boot. So is there any way to remove it without breaking my device?? Waiting for answers.

buinghia98 said:
Another noob's question:
I installed Xposed a few days ago on my c1505 (stock firmware, locked bl). It worked perfectly. But i've read from another post that if i remove it my phone won't boot. So is there any way to remove it without breaking my device?? Waiting for answers.
Click to expand...
Click to collapse
It never bricked my device!!!
Sent from my C1604 using xda app-developers app

Xmoose said:
It never bricked my device!!!
Sent from my C1604 using xda app-developers app
Click to expand...
Click to collapse
B-b-but...
http://forum.xda-developers.com/showthread.php?t=2498202
I'm using XE single... i think that makes the difference. Even tipos got bricked...

buinghia98 said:
B-b-but...
http://forum.xda-developers.com/showthread.php?t=2498202
I'm using XE single... i think that makes the difference. Even tipos got bricked...
Click to expand...
Click to collapse
But UltraGamerHD is still using his phone (in fact, he's making CM11...), right?
Right now, I uninstalled Xposed, rebooted, installed Xposed, rebooted. Nothing called a brick (although I did lose a cool Xposed mod for a reboot). Well, whatever. Uninstalling doesn't brick.
In fact, the problem in the topic is either:
1. The phone hard-bricking, which is not related to Xposed at all.
OR
2. The phone's battery being discharged to 0%, to the point where the phone cannot turn itself on and start charging.

NSDCars5 said:
But UltraGamerHD is still using his phone (in fact, he's making CM11...), right?
Right now, I uninstalled Xposed, rebooted, installed Xposed, rebooted. Nothing called a brick (although I did lose a cool Xposed mod for a reboot). Well, whatever. Uninstalling doesn't brick.
In fact, the problem in the topic is either:
1. The phone hard-bricking, which is not related to Xposed at all.
OR
2. The phone's battery being discharged to 0%, to the point where the phone cannot turn itself on and start charging.
Click to expand...
Click to collapse
Are you single or married?
Just kidding. Are you using XE single or dual sim. And do you know how did UltraGamerHD repaired his phone?

buinghia98 said:
Are you single or married?
Just kidding. Are you using XE single or dual sim. And do you know how did UltraGamerHD repaired his phone?
Click to expand...
Click to collapse
1. I'm a teen. So, yeah, single.
2. My phone's single too, but it's not a teen.
3. UltraGamerHD has been making CM11 (KitKat) for our phones, he's even shown an image - too bad it's been deleted now - but I think he's still (a bit) active here, so...
4. @UltraGamerHD? Your phone's working?

NSDCars5 said:
1. I'm a teen. So, yeah, single.
2. My phone's single too, but it's not a teen.
3. UltraGamerHD has been making CM11 (KitKat) for our phones, he's even shown an image - too bad it's been deleted now - but I think he's still (a bit) active here, so...
4. @UltraGamerHD? Your phone's working?
Click to expand...
Click to collapse
1. I dont think so... there are about 4 to 5 people are experiencing this, including you (if not, why did u take it to sony?)
2. What are u developing? And do you have a Facebook account?
3. Another question... how to install PurePerformance on locked bl? Flash gordon doesn't work.

NSDCars5 said:
1. I'm a teen. So, yeah, single.
2. My phone's single too, but it's not a teen.
3. UltraGamerHD has been making CM11 (KitKat) for our phones, he's even shown an image - too bad it's been deleted now - but I think he's still (a bit) active here, so...
4. @UltraGamerHD? Your phone's working?
Click to expand...
Click to collapse
My Xperia E is Working Fine, it was just me bieng stupid.

Okay, last questions:
1 @UltraGamerHD? How did you bricked it? And How did you repair it?
2.How to install PurePerformance on locked bootloader? My XE says "bootloader unlock allowed: no" so i cant use cwm or twrp. Flash gordon doesn't work.

buinghia98 said:
1. I dont think so... there are about 4 to 5 people are experiencing this, including you (if not, why did u take it to sony?)
2. What are u developing? And do you have a Facebook account?
3. Another question... how to install PurePerformance on locked bl? Flash gordon doesn't work.
Click to expand...
Click to collapse
1. I went to Sony cause I didn't know what the issue was - they fixed it by using a Z1 or Z Ultra charger to charge it to 9%, powered it off, and let me charge the rest at home.
2. I can't say what I'm making... it's a closely guarded secret. Nope, no Facebook. I had it, but I deleted it.
3. No idea, sorry.

buinghia98 said:
Okay, last questions:
1 @UltraGamerHD? How did you bricked it? And How did you repair it?
2.How to install PurePerformance on locked bootloader? My XE says "bootloader unlock allowed: no" so i cant use cwm or twrp. Flash gordon doesn't work.
Click to expand...
Click to collapse
I did brick it once, I went to the Orange UK store in my local town and he said he used software similar to PC Companion.
Go to phoneunlockserver.com and unlock your bootloader even if it says no for £10 GBP --> Use Google Currency to Convert Price.

Since it is kind of on topic.
 @UltraGamerHD: Any status of CM11 for Xperia E?
Bug list please? and why did the thread get deleted? :/ :|

[Q] Considering rooting the Nexus 5

So I have a black Nexus 5 with a capacity of 16GB. The device is only about 4 months old, so I still have it covered with warranty until June 2016. The device is as good as new and I'm very happy with it because everything is so fast and smooth.
Recently I've been thinking about rooting the device for maybe some little extras. For example, I have GTA SA installed but I would like to play it with the Cleo mod to have a little bit more fun. Or maybe I'll install some kind of adblocker so I could enjoy my brand new phone without the annoying gold diggers. Or perhaps I want to hide some apps from my app drawer so it would look neat and organised. Or I would like to install an apk that isn't available for non-rooted devices. Or in case I want to see the battery percentage next to the time display or anything like that.
As you can see I would only want to root it for rather small reasons. I definitely don't want to overclock anything because it already meets my criteria for speed, nor do I want to install any custom ROMs because I really like the pure android experience. So I have a few questions because I'm a total noob at the field of tweaking android:
Is my current data going to be wiped if I would want to root it?
I'm aware of the upcoming Android L release, so would I be able to update it right away (remember, I'm not going to use any custom ROMs) or would I have to unroot and reset everything first?
In case something goes wrong and I want to use my warranty, could any traces be found after I would have unrooted the device? (because rooting voids your warranty, right?)
What would be the top reasons to root the Nexus 5? For example, any features the device should've had but unfortunately hasn't.
And is it actually 100% safe...?
So regarding to the last question... A friend of mine has a rooted Moto G, he made me familiar with rooting and it's probably thanks to him that I'm considering it. Everything was going well but there were a few times that he woke up and his phone wasn't worth more than a brick. Apparently, it was because of some ROM he installed. This probably won't affect me in any way because like I said, I'm not going to install any custom ROMs, but my friend expected everything to be normal while it wasn't. He probably did everything like it should be done but then he suddenly woke up with a brick next to his head. So apparently, even if you do everything exactly like they tell you to do it, there's still a slight chance that it's going to end up badly, right?
So basically, I'm considering rooting my device but I'm still not sure what I would have to do because there are lots of tutorials and everything is quite confusing and I have some questions. All the help would be greatly appreciated, thanks in advance!

root/unlockbootloader/install twrp&busybox no data loss
root/unlockbootloader/install twrp&busybox no data loss without P.C, okay here we go mod's remove if you think it's not helping. download towelroot by geohot,now the rest from playstore, es file exploer,super su,busybox,reboot app,nexus unlock bootloader,
make sure you have security unknowen sources ticked and verify apps unticked.
download towelroot from chrome with es file exploer open and install hit make it rain tab, next install busybox,next install super su app.unlockbootloader with in the app.,install twrp and auto install recovery for hammerhead from twrp, now you should have full root after reboot.super user and busybox unlocked bootloader and twrp installed, and you know what the reboot app is for . no data loss and without a P.C, or you could use fastboot install just look in Q&A, kind regard's joe hope this help's.

Spaceblow said:
Is my current data going to be wiped if I would want to root it?
Click to expand...
Click to collapse
Yep; when you unlock bootloader of your device (before root), all of data will be wiped.
Spaceblow said:
I'm aware of the upcoming Android L release, so would I be able to update it right away (remember, I'm not going to use any custom ROMs) or would I have to unroot and reset everything first?
Click to expand...
Click to collapse
Nope. When you upgrade to Android L, it might be overwrite existing system clearly.
Spaceblow said:
In case something goes wrong and I want to use my warranty, could any traces be found after I would have unrooted the device? (because rooting voids your warranty, right?)
Click to expand...
Click to collapse
We are using Google Nexus. Just revert with Nexus Factory Image.
http://developers.google.com/android/nexus/images
Spaceblow said:
What would be the top reasons to root the Nexus 5? For example, any features the device should've had but unfortunately hasn't.
Click to expand...
Click to collapse
In my case, to connect NTFS filesystem.
Spaceblow said:
And is it actually 100% safe...?
Click to expand...
Click to collapse
Maybe, but it's at your own risk.

Jongmin Kim said:
Yep; when you unlock your device (before root), all of data will be wiped.
Nope. When you upgrade to Android L, it might be overwrite existing system clearly.
No. We are using Google Nexus. Just revert with Nexus Factory Image.
http://developers.google.com/android/nexus/images
In my case, to connect NTFS filesystem.
Maybe, but it's at your own risk.
English is too difficult... I'm trying to understand right now.
Click to expand...
Click to collapse
root and then unlock bootloader with the app from playstore. has to be this way. regard's p.s no data wiped ,

Spaceblow said:
So I have a black Nexus 5 with a capacity of 16GB. The device is only about 4 months old, so I still have it covered with warranty until June 2016. The device is as good as new and I'm very happy with it because everything is so fast and smooth.
Click to expand...
Click to collapse
First of all:
Lethargy said:
I think OP got his question reversed. Should be:
"Why buy a Nexus 5 if you're not going to root?"
:angel:
Click to expand...
Click to collapse
Spaceblow said:
So I have a few questions because I'm a total noob at the field of tweaking android:
Is my current data going to be wiped if I would want to root it?
I'm aware of the upcoming Android L release, so would I be able to update it right away (remember, I'm not going to use any custom ROMs) or would I have to unroot and reset everything first?
In case something goes wrong and I want to use my warranty, could any traces be found after I would have unrooted the device? (because rooting voids your warranty, right?)
What would be the top reasons to root the Nexus 5? For example, any features the device should've had but unfortunately hasn't.
And is it actually 100% safe...?
Click to expand...
Click to collapse
1. Unlocking the bootloader is what wipes the data partition, not root access.
2. Don't bother with OTAs to update, they're too much of a bother to try to get to work, when you can just flash factory images/zip, most likely before you even get the OTA pushed to you.
3. Depends where you bought it from. If you got it off the Play Store, then Google does not care about the software you have on your device as long as it's a legitimate manufacturing fault covered by the warranty. You can RMA to Google with a custom ROM and kernel if you wanted to. If you bought it from elsewhere, You'll have to send it to LG for repair. It's possible to reflash factory images and reset the tamper flag, there isn't anything else on the Nexus 5 that will tell LG anything. The easiest way is using LG Flashtool, which can be found in the first link of my signature. If your device is completely dead however, it doesn't matter since LG wouldn't be able to boot it up.
4. Root access is simply root access. You get access to /system, and therefore can use root apps and other modifications.
5. The root process itself is pretty much 100% safe. The Nexus 5 is really, really hard to brick, unless you flash something that isn't meant for your device or something similar, so user error is the only risk in the process. Software-wise, of course root access comes at some form of a security risk. Just be sure of what apps you're granting root access to and you should have no problem.
Spaceblow said:
So regarding to the last question... A friend of mine has a rooted Moto G, he made me familiar with rooting and it's probably thanks to him that I'm considering it. Everything was going well but there were a few times that he woke up and his phone wasn't worth more than a brick. Apparently, it was because of some ROM he installed. This probably won't affect me in any way because like I said, I'm not going to install any custom ROMs, but my friend expected everything to be normal while it wasn't. He probably did everything like it should be done but then he suddenly woke up with a brick next to his head. So apparently, even if you do everything exactly like they tell you to do it, there's still a slight chance that it's going to end up badly, right?
Click to expand...
Click to collapse
Most likely user error, or simply because a Moto device could be locked down more (which also makes it riskier and harder to restore) and not as easy to develop for. The Nexus 5 is one of the hardest devices to brick (again, excluding user error), and if you have any issues it would either be user error or a bug in the ROM/kernel.
Spaceblow said:
So basically, I'm considering rooting my device but I'm still not sure what I would have to do because there are lots of tutorials and everything is quite confusing and I have some questions. All the help would be greatly appreciated, thanks in advance!
Click to expand...
Click to collapse
Check out the first link of my signature and read some threads before proceeding blindly.
There are ways to gain root access without unlocking the bootloader and without a PC as mentioned above, but it's recommended to do it the traditional way by backing up your internal storage to a PC first and using fastboot. Those methods are useful for other devices that are more locked down. This is a Nexus device, it's better to do it properly.

Lethargy said:
First of all:
1. Unlocking the bootloader is what wipes the data partition, not root access.
2. Don't bother with OTAs to update, they're too much of a bother to try to get to work, when you can just flash factory images/zip, most likely before you even get the OTA pushed to you.
3. Depends where you bought it from. If you got it off the Play Store, then Google does not care about the software you have on your device as long as it's a legitimate manufacturing fault covered by the warranty. You can RMA to Google with a custom ROM and kernel if you wanted to. If you bought it from elsewhere, You'll have to send it to LG for repair. It's possible to reflash factory images and reset the tamper flag, there isn't anything else on the Nexus 5 that will tell LG anything. The easiest way is using LG Flashtool, which can be found in the first link of my signature. If your device is completely dead however, it doesn't matter since LG wouldn't be able to boot it up.
4. Root access is simply root access. You get access to /system, and therefore can use root apps and other modifications.
5. The root process itself is pretty much 100% safe. The Nexus 5 is really, really hard to brick, unless you flash something that isn't meant for your device or something similar, so user error is the only risk in the process. Software-wise, of course root access comes at some form of a security risk. Just be sure of what apps you're granting root access to and you should have no problem.
Most likely user error, or simply because a Moto device could be locked down more (which also makes it riskier and harder to restore). The Nexus 5 is one of the hardest devices to brick (again, excluding user error), and if you have any issues it would either be user error or a bug in the ROM/kernel.
Check out the first link of my signature and read some threads before proceeding blindly.
There are ways to gain root access without unlocking the bootloader and without a PC as mentioned above, but it's recommended to do it the traditional way by backing up your internal storage to a PC first and using fastboot. Those methods are useful for other devices that are more locked down. This is a Nexus device, it's better to do it properly.
Click to expand...
Click to collapse
lol yeah i have to agree with you, but i find this help's when on the go,

joecool666 said:
lol yeah i have to agree with you, but i find this help's when on the go,
Click to expand...
Click to collapse
If you don't have access to a PC, or you're using a locked-down Samsung/HTC/Moto/Sony/whatever device, then sure, go ahead and use the exploit methods.
But if you do have access to a PC, and it's a Nexus device, just do it properly, it'll cause fewer possible issues.

Lethargy said:
If you don't have access to a PC, or you're using a locked-down Samsung/HTC/Moto/Sony/whatever device, then sure, go ahead and use the exploit methods.
But if you do have access to a PC, and it's a Nexus device, just do it properly, it'll cause fewer possible issues.
Click to expand...
Click to collapse
i do use my p.c and lg flashtool and fastboot.just incase lol.and it is the better way of doing it, p.s when OTG rooting don't forget to bring the XDA app.

joecool666 said:
root and then unlock bootloader with the app from playstore. has to be this way. regard's p.s no data wiped ,
Click to expand...
Click to collapse
You mean Towelroot? I'm also considering this option because it would be nice to keep all my data.
Lethargy said:
First of all:
1. Unlocking the bootloader is what wipes the data partition, not root access.
2. Don't bother with OTAs to update, they're too much of a bother to try to get to work, when you can just flash factory images/zip, most likely before you even get the OTA pushed to you.
3. Depends where you bought it from. If you got it off the Play Store, then Google does not care about the software you have on your device as long as it's a legitimate manufacturing fault covered by the warranty. You can RMA to Google with a custom ROM and kernel if you wanted to. If you bought it from elsewhere, You'll have to send it to LG for repair. It's possible to reflash factory images and reset the tamper flag, there isn't anything else on the Nexus 5 that will tell LG anything. The easiest way is using LG Flashtool, which can be found in the first link of my signature. If your device is completely dead however, it doesn't matter since LG wouldn't be able to boot it up.
4. Root access is simply root access. You get access to /system, and therefore can use root apps and other modifications.
5. The root process itself is pretty much 100% safe. The Nexus 5 is really, really hard to brick, unless you flash something that isn't meant for your device or something similar, so user error is the only risk in the process. Software-wise, of course root access comes at some form of a security risk. Just be sure of what apps you're granting root access to and you should have no problem.
Most likely user error, or simply because a Moto device could be locked down more (which also makes it riskier and harder to restore) and not as easy to develop for. The Nexus 5 is one of the hardest devices to brick (again, excluding user error), and if you have any issues it would either be user error or a bug in the ROM/kernel.
Check out the first link of my signature and read some threads before proceeding blindly.
There are ways to gain root access without unlocking the bootloader and without a PC as mentioned above, but it's recommended to do it the traditional way by backing up your internal storage to a PC first and using fastboot. Those methods are useful for other devices that are more locked down. This is a Nexus device, it's better to do it properly.
Click to expand...
Click to collapse
This is some great information, thank you very much! So in case I would want to do it manually, this thread has everything I need (in combination with the 15 seconds ADB Installer)?

Spaceblow said:
This is some great information, thank you very much! So in case I would want to do it manually, this thread has everything I need (in combination with the 15 seconds ADB Installer)?
Click to expand...
Click to collapse
Yep. :good: I also recommend using TWRP instead of CWM as your recovery. PhilZ Touch is also another good alternative, but it is no longer maintained and probably won't work for Lollipop's default encryption.
Latest SuperSU is located here, flashable in a custom recovery.

Lethargy said:
Yep. :good: I also recommend using TWRP instead of CWM as your recovery. PhilZ Touch is also another good alternative, but it is no longer maintained and probably won't work for Lollipop's default encryption.
Latest SuperSU is located here, flashable in a custom recovery.
Click to expand...
Click to collapse
Thanks for helping me but I used Towelroot and it works flawlessly!

Spaceblow said:
Thanks for helping me but I used Towelroot and it works flawlessly!
Click to expand...
Click to collapse
Cool. :good:
Even though you now have root access, I recommend using Bootunlocker or whatever app to unlock the bootloader from within Android (which doesn't wipe), then flashing a custom recovery with fastboot while in the bootloader anyways.
Why?
If something goes wrong and your phone doesn't boot, you'll have no choice but to unlock the bootloader WITH a wipe using fastboot, then flash a custom recovery or reflash factory images, unless you've done the above, in which case you can dirty-flash (no wipe) a stock ROM zip downloadable here. :angel:

back up
Spaceblow said:
Thanks for helping me but I used Towelroot and it works flawlessly!
Click to expand...
Click to collapse
make sure you make a back up back up most important,regard's joe

To be clear, the *whole* phone including your sdcard partition will be wiped so make sure you back up before unlocking your bootloader. I would use an app like ES File Explorer and copy all your files to Dropbox or Google Drive if you dont have a computer but you'll need a computer anyway.
Sent from my Nexus 5 using XDA Free mobile app

MrObvious said:
To be clear, the *whole* phone including your sdcard partition will be wiped
Click to expand...
Click to collapse
If we want to be clear, we should also be accurate. The *whole* phone is not wiped. The /data partition is wiped, which includes /data/app (where user apps are stored) /data/data (where user settings and app data is stored) and /data/media (where /sdcard data is stored)

Lethargy said:
Cool. :good:
Even though you now have root access, I recommend using Bootunlocker or whatever app to unlock the bootloader from within Android (which doesn't wipe), then flashing a custom recovery with fastboot while in the bootloader anyways.
Why?
If something goes wrong and your phone doesn't boot, you'll have no choice but to unlock the bootloader WITH a wipe using fastboot, then flash a custom recovery or reflash factory images, unless you've done the above, in which case you can dirty-flash (no wipe) a stock ROM zip downloadable here. :angel:
Click to expand...
Click to collapse
Thanks for the tip but then I'll be unable to receive OTA updates unless I restore everything, including everything being wiped, right?
joecool666 said:
make sure you make a back up back up most important,regard's joe
Click to expand...
Click to collapse
By using Titanium Backup?

Spaceblow said:
Thanks for the tip but then I'll be unable to receive OTA updates unless I restore everything, including everything being wiped, right?
Click to expand...
Click to collapse
All guides and info threads are in my signature. One such INFO thread is OTA help-desk, which explains that you can receive OTA with custom recovery, however there are extra steps.
However, please let me explain 1 thing. OTA is the ultimate noob move. Only root-noobs receive OTA updates. They are the most inconvenient method of updating your OS if you are rooted. Long before you even receive the OTA update, there will be a pre-rooted flashable.zip that can be flashed via recovery.
noobs will often say "but..but..but I wont have to wipe if I accept an OTA"... Little do they know... Even after an official OTA, things screw up. Whenever an OS is upgraded, a wipe is highly recommended as OTA's are imperfect and data between apps and settings conflicts between versions.
OTA is a fools errand if you're rooted. Now you're rooted, leave OTA to the unrooted and learn to manage your rooted device properly. All the info you could ever need is available in my signature as previously mentioned.

Spaceblow said:
Thanks for the tip but then I'll be unable to receive OTA updates unless I restore everything, including everything being wiped, right?
By using Titanium Backup?
Click to expand...
Click to collapse
or helium back up

Owning a Nexus makes fastboot your best friend, especially if you have issues.
Read up on adb/fastboot and forget OTA's. Nothing like a clean fresh install of a new version. And there's many options to save /backup your data and important files.
Without learning fastboot and adb.... Simple fix issues can become major headaches.
Don't be intimidated. Read, learn, then do. ?
---------- Post added at 09:49 AM ---------- Previous post was at 09:48 AM ----------
@rootSU has everything you need in his sticky roll up thread.

rootSU said:
All guides and info threads are in my signature. One such INFO thread is OTA help-desk, which explains that you can receive OTA with custom recovery, however there are extra steps.
However, please let me explain 1 thing. OTA is the ultimate noob move. Only root-noobs receive OTA updates. They are the most inconvenient method of updating your OS if you are rooted. Long before you even receive the OTA update, there will be a pre-rooted flashable.zip that can be flashed via recovery.
noobs will often say "but..but..but I wont have to wipe if I accept an OTA"... Little do they know... Even after an official OTA, things screw up. Whenever an OS is upgraded, a wipe is highly recommended as OTA's are imperfect and data between apps and settings conflicts between versions.
OTA is a fools errand if you're rooted. Now you're rooted, leave OTA to the unrooted and learn to manage your rooted device properly. All the info you could ever need is available in my signature as previously mentioned.
Click to expand...
Click to collapse
Well, you convinced me to take my N5 to a step further.
So I already Towelrooted my phone which gave me root access and an untouched bootloader and recovery. My next step would be to backup every app and all data to be sure in case something goes wrong, this would be done by using Titanium Backup. Then I should be unlocking the bootloader by simply using BootUnlocker for Nexus Devices so I wouldn't get my data wiped (I know I would be able to restore it with my backup but I rather do it a bit faster and less complex). When I did that, I have to head over to this thread and flash TWRP by following the instructions at "2. Installing a Custom Recovery".
So after all these steps my phone would have no limitations and it would be as unlocked as for example your Nexus 5, right?

How to root sony xperia xa f3111

How to root sony xperia xa f3111

hung2161998 said:
How to root sony xperia xa f3111
Click to expand...
Click to collapse
At the moment you can't, locked Bootloader root may also be a thing of the past since the introduction of drm-verity security with the z3+, kingroot doesn't work either and apparently they want several hundred requests before offering device support if it'll work at all. Until someone builds a kernel+recovery for unlocked bootloader root were stuck. I get mine this week all being well so will try and help in this department for lb+ulb time permitting as my m2 has always been rooted. Will take some getting used to a stock device. There's nothing on 4pda yet either

aidy.lucas said:
At the moment you can't, locked Bootloader root may also be a thing of the past since the introduction of drm-verity security with the z3+, kingroot doesn't work either and apparently they want several hundred requests before offering device support if it'll work at all. Until someone builds a kernel+recovery for unlocked bootloader root were stuck. I get mine this week all being well so will try and help in this department for lb+ulb time permitting as my m2 has always been rooted. Will take some getting used to a stock device. There's nothing on 4pda yet either
Click to expand...
Click to collapse
Boss im gonna wait for your method
Sent from my F3112 using Tapatalk

yeyi01 said:
Boss im gonna wait for your method
Click to expand...
Click to collapse
Still stock here, currently no way to back up ta keys and not unlocking till there is. No working twrp either as far as I know. I'll wait for now
Sent from my Xperia XA using XDA Labs

aidy.lucas said:
Still stock here, currently no way to back up ta keys and not unlocking till there is. No working twrp either as far as I know. I'll wait for now
Click to expand...
Click to collapse
+1

To answer your question root is working on f3111 (as long as no bad feedback reported) and now for XA ultra too! TWRP is fully working as long as you don't have any encrypted partition or if you know the pin/password, it's a little different than before because of news Marshmallow security not because of me or TWRP.
OK, now you need to unlock your bootloader and void your warranty, and nothing more than that. You can wait for a exploit to come and backup your TA but for me it's a wast of time or wait for Kingroot but result will be same, not sure to backup TA. An other thing, I can bet that Kingroot will not be OTA survivor

rrvuhpg said:
To answer your question root is working on f3111 (as long as no bad feedback reported) and now for XA ultra too! TWRP is fully working as long as you don't have any encrypted partition or if you know the pin/password, it's a little different than before because of news Marshmallow security not because of me or TWRP.
OK, now you need to unlock your bootloader and void your warranty, and nothing more than that. You can wait for a exploit to come and backup your TA but for me it's a wast of time or wait for Kingroot but result will be same, not sure to backup TA. An other thing, I can bet that Kingroot will not be OTA survivor
Click to expand...
Click to collapse
I'd stay stock before I use dodgy kingroot. If you still get ota updates after rooting with Kingroot you ain't fully rooted for a start and Sony ric is still active. Encryption is on by default there's no way to change it or the password that I see. Until there's a way to keep my ta keys it's not gonna happen I don't think.
Sent from my Xperia XA using XDA Labs

aidy.lucas said:
I'd stay stock before I use dodgy kingroot. If you still get ota updates after rooting with Kingroot you ain't fully rooted for a start and Sony ric is still active. Encryption is on by default there's no way to change it or the password that I see. Until there's a way to keep my ta keys it's not gonna happen I don't think.
Click to expand...
Click to collapse
You can stay with a default disabled encryption only after root and you can switch back on and set your own password if you want. That's the only way I found but it's possible. What I want to say for Kingroot is I have a big doubt if it will be possible to dump TA with temp root on Marshmallow. You right for RIC but you forget dm-verity as additional security

What about temp root? Anyone anything know about it on XA? Titanium Backup & Trimmer should work fine with it

Rafixxxx said:
What about temp root? Anyone anything know about it on XA? Titanium Backup & Trimmer should work fine with it
Click to expand...
Click to collapse
There is no temp root or ta keys back up or use of ivy root. Unlocked bootloader currently only way to get any sort of root then tb should work fine though I've not used it in years
Sent from my Xperia XA using XDA Labs

I C,
hope there will be an Exploit soon

Hey everyone,
Was directed here by a few friends, I will admit that I am only a month into my android and I admit I know bugger all around this subject.
Basically I want to root my XA, get rid of the stupid apps that Sony insist on clogging my internal memory and also force install to my SD card as I keep getting on certain apps "not enough storage space" on my all but empty 200gb card.
I understand very little about rooting, I have tried many different things, I have spent last 2 hours working with SDK stuff and going thru cmd to get to the end and have "error: java.lang.securityexception: package android does not belong on 2000" appear to then find the phone needs to be rooted in the first place *growling a lot at the lappy by now*.
All I want is a way to root my phone successfully and force apps to install onto my huge SD card, if after that I can delete playstions, spotify, hangouts and other clutter than thats a bonus.
Remember please I am totally new to this field and rather dense with my lack of knowledge so pretend I am a lil kid that needs the big verion with pictures lol.
Thank you in advance

mogi99999 said:
I C,
hope there will be an Exploit soon
Click to expand...
Click to collapse
We can cross fingers with the "Dirty Cow" kernel exploit CVE-2016-5195 :fingers-crossed:

rrvuhpg said:
We can cross fingers with the "Dirty Cow" kernel exploit CVE-2016-5195 :fingers-crossed:
Click to expand...
Click to collapse
what this ?

leap_ahead said:
what this ?
Click to expand...
Click to collapse
Thats a 9yr old Root exploit that literally works on any android

.

DAM11MAD said:
I have unlocked bootloader but I still can't root it I have looked for manual rooting paths but no luck they are all out of date and don't work with ADB drivers anymore. So don't waste your time unlocking bootloader because It takes forever due to the fact that nothing works for the XA atm, I spent 5 hours unlocking bootloader only to find I still can't root it.
Click to expand...
Click to collapse
I think you are not good enough to root your device, root is working on XA and Ultra since months ago.

is there a toolkit to do the root and flash twrp?

Bootloader Unlocked - Camera not working - DRM patch anyone?

Hi everbody,
I've my device since 2 days and i'm looking for a solution to my problem : when i take a photo with the stock app, it shows me a green screen after the shutter :/
Of course i tasted all i can before this post : restore my device, Emme (not possible when bootloader unlock), ... Maybe if someone send me the original apk, i can install it and resolve my pb.
Hope someone can do it
Thx

Pretty sure this is the one you need.
http://www.apkmirror.com/apk/sony-mobile-communications/sony-camera/camera-sony-mobile-communications-2-0-0-release/sony-camera-2-0-0-4-android-apk-download/
It's the same version as I have.

jms.flynn said:
Pretty sure this is the one you need.
http://www.apkmirror.com/apk/sony-mobile-communications/sony-camera/camera-sony-mobile-communications-2-0-0-release/sony-camera-2-0-0-4-android-apk-download/
It's the same version as I have.
Click to expand...
Click to collapse
Thanks for your reply ! Unfortunately, it's "corrupted" (i'm french, sorry for my english)
I made a test with other apps and it works... But not Sony camera

Today, Emma detects my device and software is downloading new version (1309 vs 1306). Crosse my fingers to resolve my pb with this !

Nikom69 said:
Today, Emma detects my device and software is downloading new version (1309 vs 1306). Crosse my fingers to resolve my pb with this !
Click to expand...
Click to collapse
Probably won't but fingers crossed - This looks like something that happens when you unlock bootloader. Some functions might get disabled (it's usually only the advanced camera functions such as noise cancelling, but on my X camera was only showing green). Try the Emma dev version - should work (should give you at least some functionality), or wait for a kernel to be developed.
As a cautionary tale, it's way too early for BL unlock where there is No dev support. This release is just too recent. Personally, I'll wait for tested root methods and hopefully a TA backup solution.

Do you know where I can find Emma dev version ?
Coz you're right : it didn't work...

Nikom69 said:
Do you know where I can find Emma dev version ?
Coz you're right : it didn't work...
Click to expand...
Click to collapse
Download the EMMA from sony website. As soon as it detects your unlocked bootloader it will automagically download the latest dev fw version - customization is outside of what xperiafirm offers and it should work. Should. I'm still waiting for my phone to be delivered so I can't help you further than that. I just know it works for terrible failures.
In any case, a kernel that addresses the DRM content functionality is probably weeks away weeks away. Maybe relocking the bootloader will help? Could restore partial camera functionality, instead of a green screen.
Again, I'm coming with ideas under a huge maybe but you should give it a try.

Sebi673 said:
Download the EMMA from sony website. As soon as it detects your unlocked bootloader it will automagically download the latest dev fw version - customization is outside of what xperiafirm offers and it should work. Should. I'm still waiting for my phone to be delivered so I can't help you further than that. I just know it works for terrible failures.
In any case, a kernel that addresses the DRM content functionality is probably weeks away weeks away. Maybe relocking the bootloader will help? Could restore partial camera functionality, instead of a green screen.
Again, I'm coming with ideas under a huge maybe but you should give it a try.
Click to expand...
Click to collapse
i think for the moment relocking bootloader is the best... but how ? Could you (or someone) help me step by step ?
In flashtool / Emma the "volume down + plug usb" isn't working, so i have only fastboot command...

Nikom69 said:
i think for the moment relocking bootloader is the best... but how ? Could you (or someone) help me step by step ?
In flashtool / Emma the "volume down + plug usb" isn't working, so i have only fastboot command...
Click to expand...
Click to collapse
It should be working although you need to install the drivers without Enforcing Driver signature.
To do that you need to restart your PC while holding the Shift key. Shift, click restart and a 'new' screen will appear asking you how do you want to restart. go through the menus till you see the F1-12 options. As far as I remember F7 is the one that disables driver signature enforcement. After that PC should restart normally but without that thingy. Once restarted go to flashtool folder - drivers - and install the drivers - click allow everywhere and voila, drivers are set. From there on, you should see the phone as connected. Emma should also work.
hrs a vid of how to custom restart https://youtu.be/71YAIw7_-kg?t=1m1s

Sebi673 said:
It should be working although you need to install the drivers without Enforcing Driver signature.
To do that you need to restart your PC while holding the Shift key. Shift, click restart and a 'new' screen will appear asking you how do you want to restart. go through the menus till you see the F1-12 options. As far as I remember F7 is the one that disables driver signature enforcement. After that PC should restart normally but without that thingy. Once restarted go to flashtool folder - drivers - and install the drivers - click allow everywhere and voila, drivers are set. From there on, you should see the phone as connected. Emma should also work.
hrs a vid of how to custom restart https://youtu.be/71YAIw7_-kg?t=1m1s
Click to expand...
Click to collapse
After doing all things... same issue ! In FlashTool driver setup, i didn't find exactly xzp drivers... so i install all to make a test and this is what i had :

Nikom69 said:
After doing all things... same issue ! In FlashTool driver setup, i didn't find exactly xzp drivers... so i install all to make a test and this is what i had :
Click to expand...
Click to collapse
You just need the generic adb drivers. but if they're not working try those. https://developer.sonymobile.com/downloads/drivers/xperia-xz-premium-driver/ Although flashtool might not be compatible. I can't confirm this since I'm still waiting for my phone to be delivered. Soon this should be populated, is where you can find a custom kernel that restores DRM functionality https://kernel.andro.plus/yoshino.html

In Windows, my device with green led (volume - and plugged) => SOMC Flash Device. If i click on "upgrade drivers" and go in Sony Driver folder, windows tells me my driver is up to date.
I certainly forget or loose something, but it's the first time i have pb with any device since 10 years !! :/

DRM patch?
@FartyParty @kemod @AndroPlus
Hey guys, can you please help @Nikom69 with his DRM issue?
He unlocked BL and has no camera functionality - green screen. He flashed the FW with EMMA and still no camera. And flashtool isn't working. I did my best to help him but I'm still waiting for my phone to arrive.
So do you have a working DRM patch or something to get him at least basic camera functions back? I told him to wait for AndroPlus Kernel but maybe there's a quick fix or a different idea.

Sebi673 said:
...He unlocked BL and has no camera functionality - green screen. ...
Click to expand...
Click to collapse
Unfortunately no, I experienced the same and also posted this issue on another thread hoping that someone won't repeat my mistake
https://forum.xda-developers.com/showpost.php?p=72645858&postcount=19
It seems like all proprietary post processing is no longer functional after bootloader unlock, but video still work to some extent and you can still use the camera only in manual mode with ISO 100 and all features off (which is useless). My Sony XZP just turn into an expensive and beautiful "worse than AOSP phone" right now. I really hope someone could have a solution to this, heck I even willing to pay for it.

Yes, unlocking the bootloader destroys the drm-keys and disables stuff.
The keys are gone, warranty gone, no amount of flashing this or that will restore anything.
Relocking the bootloader will NOT restore drm-keys because they are gone FOREVER.
Just wait for a custom kernel with drm-fix included and the camera will work again.
How were you even able to unlock the bootloader if you can't get flashtool to work?

FartyParty said:
Yes, unlocking the bootloader destroys the drm-keys and disables stuff.
The keys are gone, warranty gone, no amount of flashing this or that will restore anything.
Relocking the bootloader will NOT restore drm-keys because they are gone FOREVER.
Just wait for a custom kernel with drm-fix included and the camera will work again.
How were you even able to unlock the bootloader if you can't get flashtool to work?
Click to expand...
Click to collapse
That's simple - Fastboot commands. I'm receiving my XZp today but now I'll think twice and wait for the Androplus.
I was thinking for bootloader relock - cause on my Xperia X after relocking camera was working to some extent, but its not the case here..... Anyway if you think of something write it here. He'll be happy for any solution you find. I know how it feels to go from flagship to brick in under 3 seconds so he's got my full support :laugh:

Sebi673 said:
That's simple - Fastboot commands. I'm receiving my XZp today but now I'll think twice and wait for the Androplus.
I was thinking for bootloader relock - cause on my Xperia X after relocking camera was working to some extent, but its not the case here..... Anyway if you think of something write it here. He'll be happy for any solution you find. I know how it feels to go from flagship to brick in under 3 seconds so he's got my full support :laugh:
Click to expand...
Click to collapse
So he managed to unlock bootloader with adb fastboot but adb flashboot doesn't work?
If he were able to flash twrp he could just flash drm-fix etc.
But eh, just gotta wait a little.

FartyParty said:
So he managed to unlock bootloader with adb fastboot but adb flashboot doesn't work?
If he were able to flash twrp he could just flash drm-fix etc.
But eh, just gotta wait a little.
Click to expand...
Click to collapse
Exactly, he needs the DRMfix, do you have it? Or should he wait for the kernel to come out. This Thread should be a cautionary tale for first timers so information is the key. :cyclops:

Sebi673 said:
Exactly, he needs the DRMfix, do you have it? Or should he wait for the kernel to come out. This Thread should be a cautionary tale for first timers so information is the key. :cyclops:
Click to expand...
Click to collapse
This is what I used on the Sony XZ, XZs
LINK

Nikom69 said:
Hi everbody,
I've my device since 2 days and i'm looking for a solution to my problem : when i take a photo with the stock app, it shows me a green screen after the shutter :/
Of course i tasted all i can before this post : restore my device, Emme (not possible when bootloader unlock), ... Maybe if someone send me the original apk, i can install it and resolve my pb.
Hope someone can do it
Thx
Click to expand...
Click to collapse
You have to flash the modified kernel with the drm patch.. The same thing happened in my XZs, got solved only after I flashed the modified kernel..

Don't Re-Lock Your Bootloader

As a friendly reminder to those unfamiliar with unlocking/re-locking their bootloaders;
Unless your on 100% stock, and planning on reselling your phone, don't re-lock the bootloader.
For some reason re-locking the bootloader while you have a custom ROM installed will cause the phone not to boot (in a way, soft bricking it.)
And, leave "OEM unlocking" in the "Developer Options" CHECKED, once that is unchecked you cannot unlock the phone once a soft brick happens.
The official advice from Essential about re-locking your phone is ONLY for the official firmware. Pretend they never said that on their site, it has caused more trouble then necessary. It's even dangerous to re-lock while running the Oreo beta.
Concerning un-bricking the device, at the moment there is no known way.
And it will be this way until someone figures out a way to exploit the bootloader or reverse engineer it.
So please don't flood this thread with asking for help to un-brick your device, I nor anyone else can help you on that at this given time, all I'm doing is trying to is prevent that happening.
So, safe unlocking! And happy holidays!
EDITS:
1) According to some reports, when you lock your bootloader it will also automatically untoggle the "OEM Unlocking" option.
2) It appears when re-locking the phone on a non-stock ROM some partitions are becoming corrupt, and resulting in the "red boot warning" screen. Under most circumstances you can fix that screen, but not while the bootloader is locked (since you need the fastboot flash command.)
3) When the partitions become corrupt you cannot boot into any mode, including the stock recovery. This is why Essential's suggestions are pointless at this stage of the brick.

Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs

avd said:
Should be pinned and in the OP of every mod thread
Click to expand...
Click to collapse
totally agree, i made this "trick" with one of my first android phone and it never happen me again. But new user who would flash Los or other rom should be aware of this issue, specially when jtag is not an option. As far we'll make some powerfull 500$ brick :crying:. it's our duty to make people aware of this. @invisiblek you guy made an incredible work and so fast but like he said i think you should warn people of the risk in the OP

avd said:
Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.

Ellises said:
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.
Click to expand...
Click to collapse
It's very easy to ask for a thread to get stuck to the top.
Just use the report post button, and ask, whether or not becomes a sticky is up to the Mods.
How to Report a Post.
Sent from my XT1254 using XDA Labs

Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"

That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
ericzhf said:
Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"
Click to expand...
Click to collapse

Ellises said:
That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
Click to expand...
Click to collapse
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.

ericzhf said:
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.
Click to expand...
Click to collapse
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.

tech_head said:
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.
Click to expand...
Click to collapse
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:

ericzhf said:
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:
Click to expand...
Click to collapse
FDR is not "back to stock".
You must to a full flash to get back to stock.

I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.

Ellises said:
I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.
Click to expand...
Click to collapse
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery

I could also mention on their stock build page it wants you to unlock the bootloader to manually update through the bootloader. But on the oreo beta page it mentions nothing about having to be unlocked, or locked to do it via the stock recovery. So the average user could presume they need to be unlocked.
NaterTots said:
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery
Click to expand...
Click to collapse

Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.

WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
No.

WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.

Obamaloominaty said:
No.
Click to expand...
Click to collapse
tech_head said:
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.
Click to expand...
Click to collapse
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.

WiddleyScudds said:
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.
Click to expand...
Click to collapse
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.

tech_head said:
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.
Click to expand...
Click to collapse
I just got an ota notification for OPM1. 180104.092. think I'll be safe I I take it, then factory reset and then lock? Because I can't seem to locate stock NMK24B to flash. Maybe I'm not looking hard enough .