Related
The new Device Protection features of Android 5.1 on the Nexus 9 and Nexus 6 can, in certain cases, cause you to have a bootloader which can not be unlocked.
Please have a read of the following links:
https://support.google.com/nexus/answer/6172890?hl=en
http://forum.xda-developers.com/nexus-6/help/update-to-5-1-lock-bootloader-t3058480
http://forum.xda-developers.com/nexus-6/general/relock-bootloader-time-updating-to-5-1-t3053497
What a pita
Sent from my Nexus 5 using XDA Free mobile app
i would never relock my bootloader
people unlock there bootloader for a reason
but to relock it after thats just wrong...
thats one of the things i hate about CM
they recommend you to relock your bootloader...
Agreed, why would you lock your bootloader unless sending in for repairs maybe?
But Google is really messing up the flow. The nexus 6 5.1 OTA is a mess right now but I will leave that for another thread.
Android 5.1 for Nexus 9? You must be joking.
So, I just purchased a Nexus 9 via the 4-hour online-only sale at Best Buy. It was $100 off, couldn't pass it up. My question is: is this likely going to be shipped in such a condition as to prevent me from permanently unlocking the bootloader? Or is a permanent lock something one must deliberately do?
disturbd1 said:
So, I just purchased a Nexus 9 via the 4-hour online-only sale at Best Buy. It was $100 off, couldn't pass it up. My question is: is this likely going to be shipped in such a condition as to prevent me from permanently unlocking the bootloader? Or is a permanent lock something one must deliberately do?
Click to expand...
Click to collapse
No no you can still unlock it
But if you relock it that's the problem
disturbd1 said:
So, I just purchased a Nexus 9 via the 4-hour online-only sale at Best Buy. It was $100 off, couldn't pass it up. My question is: is this likely going to be shipped in such a condition as to prevent me from permanently unlocking the bootloader? Or is a permanent lock something one must deliberately do?
Click to expand...
Click to collapse
As USBhost said, you'll be able to unlock it. However, when you are first setting it up and are running through the set-up wizard, there will be an option to "Protect Device" or something like that. If you enable it, and re-lock the bootloader, it will put you in a situation where you can only unlock the booloader in certain situations -- and if you happen to have a bootloop with a locked bootloader, that's when you are in trouble.
EDIT: On Nexus devices, I personally unlock the bootloader as soon as I take it out of the box, without first booting into Android, and then leave it unlocked. But of course, you give up some security by doing that.
efrant said:
As USBhost said, you'll be able to unlock it. However, when you are first setting it up and are running through the set-up wizard, there will be an option to "Protect Device" or something like that. If you enable it, and re-lock the bootloader, it will put you in a situation where you can only unlock the booloader in certain situations -- and if you happen to have a bootloop with a locked bootloader, that's when you are in trouble.
EDIT: On Nexus devices, I personally unlock the bootloader as soon as I take it out of the box, without first booting into Android, and then leave it unlocked. But of course, you give up some security by doing that.
Click to expand...
Click to collapse
Considering this is a tablet, hopefully I won't lose or misplace it
Thanks, guys! Glad I stumbled across this thread before the thing arrived.
Locking the bootloader doesn't protect you from anything. If the device leaves your physical control in a potentially hostile environment, whatever is on the system or boot partition becomes suspect, regardless of whether the bootloader is locked or unlocked.
doitright said:
Locking the bootloader doesn't protect you from anything. If the device leaves your physical control in a potentially hostile environment, whatever is on the system or boot partition becomes suspect, regardless of whether the bootloader is locked or unlocked.
Click to expand...
Click to collapse
Example: I have a device running a stock ROM with no encryption, the stock recovery and a lock screen password. I happen to lose my phone. What happens to the photos of me dancing to Old Time Rock & Roll in my underwear that are stored on the device? If the bootloader is unlocked, someone just plugs it into a PC, boots TWRP and pulls them off. If the bootloader is locked, there is no easy way to see or get the photos off the device.
That is all I was saying about security. Nothing to do with you leaving your device somewhere or losing it, and then finding it again. Strictly about the personal content on the device.
efrant said:
EDIT: On Nexus devices, I personally unlock the bootloader as soon as I take it out of the box, without first booting into Android, and then leave it unlocked. But of course, you give up some security by doing that.
Click to expand...
Click to collapse
I thought Lollipop always requires you to go in and check the Enable OEM Unlock box? Or is that not true if you never booted into Android even once?
bailyc said:
I thought Lollipop always requires you to go in and check the Enable OEM Unlock box? Or is that not true if you never booted into Android even once?
Click to expand...
Click to collapse
If you have never booted into Android, then you don't need to check that setting. As I said, that's the way I did it on my N6: take out of box -> charge -> boot directly into bootloader -> "fastboot oem unlock". No other steps required if you don't boot into Android first.
can i use this guide for safely relock my Bl on Nexus 9 ..... Relocking coz of RMA and warranty purpose as bought from amazon India instead of Play Store
http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
lilliput222 said:
can i use this guide for safely relock my Bl on Nexus 9 ..... Relocking coz of RMA and warranty purpose as bought from amazon India instead of Play Store
http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Click to expand...
Click to collapse
Yes, that should work for the N9 as well.
The bootloader on my Nexus 9 Android 5.1.1 is locked forever due to my mistake
Short backstory:
- I wanted to install the Android M developer Preview for the Nexus 9 but I forgot to check "Enable OEM unlock" in developer options (worst mistake).
- I used adb command to flash the new image but failed somehow
- I carelessly type # fastboot oem lock
- I tried to factory reset from bootloader to bring it back to Stock. Now it couldn't factory reset and my Nexus 9 hangs in a nice boot loop.
- I try # fastboot oem unlock but failed with permission denied error
I tried some ways to save my device but no hopes
- I used Nexus Root Tookit to unlock bootloader or restore image with force mode but failed,
- I follow instruction in HTC dev forum to get identifier token in order to receive your unlock code binary file but failed
- Unluckily, I don't installed any custom recovery.
Please help if you know a way unlock the bootloader or flash the factory ROM to save the nexus 9
quekl84 said:
Please help if you know a way unlock the bootloader or flash the factory ROM to save the nexus 9
Click to expand...
Click to collapse
Not possible. You will have to return it to HTC for repair or replacement.
quekl84 said:
Short backstory:
- I wanted to install the Android M developer Preview for the Nexus 9 but I forgot to uncheck "Enable OEM unlock" in developer options (worst mistake).
- I used adb command to flash the new image but failed somehow
- I carelessly type # fastboot oem lock
- I tried to factory reset from bootloader to bring it back to Stock. Now it couldn't factory reset and my Nexus 9 hangs in a nice boot loop.
- I try # fastboot oem unlock but failed with permission denied error
I tried some ways to save my device but no hopes
- I used Nexus Root Tookit to unlock bootloader or restore image with force mode but failed,
- I follow instruction in HTC dev forum to get identifier token in order to receive your unlock code binary file but failed
- Unluckily, I don't installed any custom recovery.
Please help if you know a way unlock the bootloader or flash the factory ROM to save the nexus 9
Click to expand...
Click to collapse
u mean u forgot to CHECK to box to allow oem UNLOCK? im confused lol
cobyman7035 said:
u mean u forgot to CHECK to box to allow oem UNLOCK? im confused lol
Click to expand...
Click to collapse
Yes, I forgot to check the box to allow oem UNLOCK. And now my device is locked forever.
A quick question: A lot of N9 ROMs require flashing an updated bootloader from the factory image. Aren't these bootloaders locked by default? Can we flash a factory bootloader over a custom ROM?
It seems that we might bork our Nexus 9s if we flash a locked bootloader in.
I'm new to Android. Recently I got a new nexus 6p. I was so confused that whether I have to unlock bootloader or not. Currently I just want to experience the pure Android simply without rooting or changing anything. But I heard a lot about bricked nexus 6 that the device would not be manually fixed if it was not bootloader unlocked before. As I am in China where I have no warranty for my nexus 6p, I have to keep my device safe as possible as I can.
So my question is under the circumstance that I haven't unlocked bootloader or OEM:
How much probability could it be I do nothing but unexpectedly brick the device?
If it is bricked, is it possible to recover it?
Do common nexus 6p users have to unlock bootloader?
Another important thing should be mentioned. Generally I can't access to any service by google in China, so I utilize a proxy tool to get over the great firewall to use google. Is there any experience about the situation like me? I also heard a saying that upgrading nexus 6 firmware by OTA through a proxy tool in China may brick the device, because google can not save the upgrading information of the device for the reason that the proxy IP is not static, then google will push update again, and once you click it, brick.
Puzzled enough...Thanks in advance.
I am not 100% certain what you are asking... If you do not unlock the bootloader, you should not be able to brick your device. The only reason to unlock it is to flash a custom ROM (not official from Google) or to flash Google factory images, which it sounds like might be necessary for you being that you are in China and may not receive OTAs properly. This is a process of downloading a file from Google and flashing to your device after unlocking the bootloader.
Your post was not exactly clear partially, but is your phone already bricked and you are trying to recover, or simply asking for your own reference?
fury683 said:
I am not 100% certain what you are asking... If you do not unlock the bootloader, you should not be able to brick your device. The only reason to unlock it is to flash a custom ROM (not official from Google) or to flash Google factory images, which it sounds like might be necessary for you being that you are in China and may not receive OTAs properly. This is a process of downloading a file from Google and flashing to your device after unlocking the bootloader.
Your post was not exactly clear partially, but is your phone already bricked and you are trying to recover, or simply asking for your own reference?
Click to expand...
Click to collapse
Thanks for replying. Could you please point out the unclear expressions? And I could edit them.
I have only unlocked nexus 6p bootloader, and the device is running well. I do not understand exactly why I have to do this, I just do it in case the situation described by other nexus 6 users happen to my nexus 6p. So I want to figure out the logic.
If you have no reason to unlock it, then you can relock it. Unlocking will always cause a full wipe (factory reset) of the device. Some users have stated that relocking the bootloader will also induce a wipe. If you want to leave it unlocked, this will allow you to flash factory images (such as updates from Google) as often as you'd like. It is possible to flash a factory image without losing any data by modifying the batch file used to flash the firmware.
Simply having the bootloader unlocked should not pose any threat to your device. You have to try very intentionally to flash firmware and risk bricking the device, it's not really something you can do by accident. The one thing I will mention is that with the bootloader unlocked, someone with the correct knowledge could flash a new image on your phone without needing your password or other security information. They would only need to power off the device, enter bootloader mode and plug into a PC to begin flashing. This would remove every trace of you and your data from the device and make it like it was brand new from the factory.
By keeping the bootloader locked and the "Allow OEM unlocking" option turned OFF, a person would need to have your password (or fingerprint) to gain access to this option in the settings, thus not allowing them to flash over the device as it is today.
Hope this helps.
fury683 said:
If you have no reason to unlock it, then you can relock it. Unlocking will always cause a full wipe (factory reset) of the device. Some users have stated that relocking the bootloader will also induce a wipe. If you want to leave it unlocked, this will allow you to flash factory images (such as updates from Google) as often as you'd like. It is possible to flash a factory image without losing any data by modifying the batch file used to flash the firmware.
Simply having the bootloader unlocked should not pose any threat to your device. You have to try very intentionally to flash firmware and risk bricking the device, it's not really something you can do by accident. The one thing I will mention is that with the bootloader unlocked, someone with the correct knowledge could flash a new image on your phone without needing your password or other security information. They would only need to power off the device, enter bootloader mode and plug into a PC to begin flashing. This would remove every trace of you and your data from the device and make it like it was brand new from the factory.
By keeping the bootloader locked and the "Allow OEM unlocking" option turned OFF, a person would need to have your password (or fingerprint) to gain access to this option in the settings, thus not allowing them to flash over the device as it is today.
Hope this helps.
Click to expand...
Click to collapse
According to you, I should not be able to brick my device if I did not unlock the device. I can understand this. But the problem is I am in China...By using proxy, I could receive OTAs correctly. But some nexus 6 users in China still encountered with device bricked after upgrading firmware by OTAs even they didn't unlock bootloader. One possible reason is like what I mentioned in last paragraph #1.
I don't like the prompt each time when I reboot the device after unlocking bootloader. Let's make the problem simpler. Can I unbrick the device if it is bricked and bootloader locked?
I can't really speak to your concern regarding bricking from OTA. This should nearly never happen, but I would suspect that the proxy is the issue. If you are concerned about that particular instance being an issue, I would simply not accept the OTA and don't install it. The file will download to your device and you will see a notification very similar to this: http://images.tapatalk-cdn.com/15/08/12/1c244e92c6a0cd69ca6e1a3037a05d62.jpg If you do not click Install, it will not install itself. You can click Later but usually cannot dismiss the notification. I have had the update pending on my Nexus 7 tablet that I don't often for months, but simply have not upgraded because I don't use it often enough to justify it.
If you want to be on the latest firmware for security reasons (Android 6/M will have monthly security patch releases from Google), you can download the factory images and flash yourself. However, if you believe there may be an issue because of the proxy you are using, the factory image could face the same issue as the OTA as you described. As I said, because I am not in China and do not use a proxy as you do, I cannot comment on how or why other users may have faced a hard brick scenario.
Ultimately, having the bootloader unlocked will allow you to flash the factory image over a bricked firmware caused by a corrupt (or otherwise unusable) OTA. If the phone can enter bootloader mode, you can flash the firmware and restore it to like new state. The warning message you see when booting is not able to be disabled without locking the bootloader again, but it only appears for a few moments. It was previously hidden on the Nexus 6 (not the 6p) so it might be possible in the future, but that is just a guess.
fury683 said:
I can't really speak to your concern regarding bricking from OTA. This should nearly never happen, but I would suspect that the proxy is the issue. If you are concerned about that particular instance being an issue, I would simply not accept the OTA and don't install it. The file will download to your device and you will see a notification very similar to this: If you do not click Install, it will not install itself. You can click Later but usually cannot dismiss the notification. I have had the update pending on my Nexus 7 tablet that I don't often for months, but simply have not upgraded because I don't use it often enough to justify it.
If you want to be on the latest firmware for security reasons (Android 6/M will have monthly security patch releases from Google), you can download the factory images and flash yourself. However, if you believe there may be an issue because of the proxy you are using, the factory image could face the same issue as the OTA as you described. As I said, because I am not in China and do not use a proxy as you do, I cannot comment on how or why other users may have faced a hard brick scenario.
Ultimately, having the bootloader unlocked will allow you to flash the factory image over a bricked firmware caused by a corrupt (or otherwise unusable) OTA. If the phone can enter bootloader mode, you can flash the firmware and restore it to like new state. The warning message you see when booting is not able to be disabled without locking the bootloader again, but it only appears for a few moments. It was previously hidden on the Nexus 6 (not the 6p) so it might be possible in the future, but that is just a guess.
Click to expand...
Click to collapse
OK I choose to give in...leave it unlocked there.
Thank you very much!
gnange said:
OK I choose to give in...leave it unlocked there.
Thank you very much!
Click to expand...
Click to collapse
The decision to leave it unlocked is the right decision. The other person replying in this thread is completely wrong when he says you can't brick a phone if you don't unlock it, that's completely and utterly incorrect. Sometimes things happen, unforeseen spontaneous problems happen all the time with smartphones. If this happens to you and your bootloader is locked there's absolutely nothing you can do to fix it. So yes, leave your bootloader unlocked as an insurance policy against the unforeseen.
@fury683, I'd think twice before telling someone that nothing bad can happen to their phone as long as it's locked, this is false information, and could potentially lead to someone being unable to repair a soft-bricked device due to following your advice.
Heisenberg said:
The decision to leave it unlocked is the right decision. The other person replying in this thread is completely wrong when he says you can't brick a phone if you don't unlock it, that's completely and utterly incorrect. Sometimes things happen, unforeseen spontaneous problems happen all the time with smartphones. If this happens to you and your bootloader is locked there's absolutely nothing you can do to fix it. So yes, leave your bootloader unlocked as an insurance policy against the unforeseen.
@fury683, I'd think twice before telling someone that nothing bad can happen to their phone as long as it's locked, this is false information, and could potentially lead to someone being unable to repair a soft-bricked device due to following your advice.
Click to expand...
Click to collapse
To be fair, I said should not. I've never bricked a device from normal use.
I offered my opinion, and the reasons why. I've been burned by comments and advice from people plenty of times and try my best to help out where I can. I don't think my post was misleading, and I appreciate your comments on the matter as well.
Heisenberg said:
The decision to leave it unlocked is the right decision. The other person replying in this thread is completely wrong when he says you can't brick a phone if you don't unlock it, that's completely and utterly incorrect. Sometimes things happen, unforeseen spontaneous problems happen all the time with smartphones. If this happens to you and your bootloader is locked there's absolutely nothing you can do to fix it. So yes, leave your bootloader unlocked as an insurance policy against the unforeseen.
@fury683, I'd think twice before telling someone that nothing bad can happen to their phone as long as it's locked, this is false information, and could potentially lead to someone being unable to repair a soft-bricked device due to following your advice.
Click to expand...
Click to collapse
Thanks for your advice. So, I can make the conclusion that we should unlock nexus bootloader no matter where we are, when it is and whether we will root or not, right ?
gnange said:
Thanks for your advice. So, I can make the conclusion that we should unlock nexus bootloader no matter where we are, when it is and whether we will root or not, right ?
Click to expand...
Click to collapse
The choice is ultimately yours, but my advice is always to have it unlocked, that way you're able to access and use fastboot in the event that something goes wrong.
fury683 said:
To be fair, I said should not. I've never bricked a device from normal use.
I offered my opinion, and the reasons why. I've been burned by comments and advice from people plenty of times and try my best to help out where I can. I don't think my post was misleading, and I appreciate your comments on the matter as well.
Click to expand...
Click to collapse
As I am new to android, your reply benefits me a lot. I notice you replied me before dawn while it was afternoon in China, thanks for your kindness but you should pay more attention to getting enough sleep, don't burn yourself out. : )
Heisenberg said:
The choice is ultimately yours, but my advice is always to have it unlocked, that way you're able to access and use fastboot in the event that something goes wrong.
Click to expand...
Click to collapse
Actually I used to suppose one has to unlock bootloader only if in China. Now I get it. Thank you !
Heisenberg said:
The choice is ultimately yours, but my advice is always to have it unlocked, that way you're able to access and use fastboot in the event that something goes wrong.
Click to expand...
Click to collapse
Yep what Heisenberg said is 100% true. My phone got bricked after the OTA update resulted in an error. I hadn't enabled the OEM Unlock setting, so couldn't unlock the phone. Have to wait for a replacement now
Temporarily Locked - until I prepare complete method
!!! WARNING !!!
This method is currently in testing
Do this at your own risk! I'm not responsible for bricks.
Read and follow this steps correctly!
Description:
Regarding OllieD thread (available in Credits) he found that bootloader have several references in persistent partition which was correct. I was trying to continue his research and I found that before unlock and after unlock some partitions not included in KDZ files are modificated by unlock.bin key.
This partitions are: cust, drm, misc, modemst1, modemst2, mpt, persistent and sns. I knew that drm, modemst1, modemst2, mpt and sns partitions cannot be important in unlocking / locking process so I was able to check 3 partitions which was CUST, MISC and PERSISTENT.
This first contains informations about whole boot process like boot image, boot procedure and also information about bootloader state which is visible on the top of the screen while bootloader is unlocked.
Second partition is the most important - it contains DEVICE-ID needed to unlock device and real bootloader state which can be check using "fastboot getvar unlocked" and also used unlock.bin when bootloader is unlocked. There are some references between this partitions which check them both so this partitions MUST be flashed together.
Persistent partition contains procedure for unlocking bootloader (parse command to flash unlock.bin) so we dont need to flash it - but if you want, you can
Result of relock:
- "Bootloader Unlocked!" message disappear while booting. (CONFIRMED)
- "fastboot getvar unlocked" returns "no" (CONFIRMED)
Requirements:
- ADB and FASTBOOT
- ADB Driver installed
- LGUP (which can be downloaded from here)
- LG_ROOT (which can be downloaded from here)
After relock, you can use the same Unlock Key which was used to unlock bootloader for the first time (this one from official LG Bootloader Unlock Site)
INSTRUCTION:
IN PREPARATION...
Video (Prove - not instruction):
WARNING! DONT TRY METHOD SHOWED IN THIS VIDEO FOR THIS MOMENT !!!
COMMANDS USED IN THIS VIDEO ARE DEDICATED TO H815 EU VARIANT
IF YOU DONT HAVE THIS VARIANT, THIS COMMANDS CAN HARD-BRICK YOUR PHONE!!!
Credits:
- OllieD (for: Relocking Bootloader May Be Possible...)
- shakeyabooti (for: "LGUP - NEW!!! - INSTALL KDZ - MM or LP - FACTORY RESET/UPGRADE")
- thecubed (for: "[ROOT] TMO/VZW/ATT/SPRINT/INTL Root your LG G4 with Low Effort Root!")
- Unjustified Dev (for: "[GUIDE] New Root Method for LG Devices")
- dominik-p (for: "[How to] Determine dd Parameters For All LG G4 Models")
- leptdre (for: "Unbrick LG G4 H815 9008 Qualcomm")
You are the man if it works!
Oh man,big up for u!
Uhmm.... Does this mean that... if we get the bootloop issue.... we will be able to relock and send back to LG for warranty purposes???!?!?
(I mean, if it's really shown as locked in every possible aspect, after relocking...)
polfrank said:
Uhmm.... Does this mean that... if we get the bootloop issue.... we will be able to relock and send back to LG for warranty purposes???!?!?
(I mean, if it's really shown as locked in every possible aspect, after relocking...)
Click to expand...
Click to collapse
Yes, but you don't need to.
I had bootloader unlocked, and LG repaired it under warranty
Just place LG G4 motherboard to your cooker, 200 celsius degrees for 10 minutes and device is broken forever without any traces - send it to them, tell "i dont know what's happened - just bootlooped and now died" - and voilÃ*. They replaced motherboard and after 2-3 days, i got my LG working without any bootloop (and with locked bootloader). And of course for free :highfive:
So, I've just extracted all partitions "BEFORE" unlocking bootloader, then i unlocked it, again extracted all partitions to make a HEX compare, and that's it - just flash important (2 or 3) partitions from state BEFORE bootloader was unlocked and wow - relocked, unlocked, again relocked, unlocked - no crash, no brick, working as hell.
And as I wrote:
xVANKO said:
Result of relock:
- "Bootloader Unlocked!" message disappear while booting. (CONFIRMED)
- "fastboot getvar unlocked" returns "no" (CONFIRMED)
- [I need to find is there any other method to check, is bootloader locked or not - IF YOU KNOW ANY OTHER METHOD TO CHECK BOOTLOADER STATE PLEASE WRITE IT IN COMMENT OR SEND ME VIA PM]
Click to expand...
Click to collapse
There is no information while booting about unlocked bootloader, and also fastboot command "getvar unlocked" returns "no" - so official command to check bootloader state returns that bootloader is locked. I don't know is there any other method of checking bootloader state but it seems to be fully locked.
The biggest problem for me is 1 of this important partitions - becouse, what if this partition contains DEVICE-ID needed to unlock bootloader. If you relock it using my method, probably your phone will get DEVICE-ID of my phone - which can be easly detected by LG Support. I need to check some things before I make this release.
Well, one option would be to create a script for those that did not unlock yet, so they save the 3 partitions and then they can happily unlock, knowing that they can relock. What do you say about this as a partial solution, if some device dependent information is stored in those partitions.?
ObiDanKenobi said:
Well, one option would be to create a script for those that did not unlock yet, so they save the 3 partitions and then they can happily unlock, knowing that they can relock. What do you say about this as a partial solution, if some device dependent information is stored in those partitions.?
Click to expand...
Click to collapse
First partition store data which customize boot screen (like boot logo, information about bootloader lock state, etc). Second partition store bootloader extra configuration like used unlock key, real unlock state. Third partition is unknown for me at this moment. For sure, people with locked bootloader will have the most secure way to relock it after unlock - just using their own partitions dump - not shared and published for all. If second partition does not contain informations about DEVICE_ID, there wiil be only one simply method to relock bootloader again.
Locked bootloader for 1,5 years, so this will be huge for me, finally unlocking the bootloader and back again in case of something happens! Great....
Sent from my LG-H815 using Tapatalk
Oh man! If you'll do that and it'll be working 100% I will try to donate to you for that! I wanted to unlock my bootloader but I was always worried about some problems that I might get
Wysłane z mojego LG-H815 przy użyciu Tapatalka
All the people are worried about warranty in case of a bootloop. How would you revert the 3 partitions content when the phone is bootlooping and you have access only to send_command.exe?
Oh, while my G4 is still in the owen now, I'm reading this thread H815 506 bootlooped this April. Warranty repair rejected. Worked with big-core disable tool for 6 months, until it finally died today.
Ok, if it is not finally dead after baking in the owen, then I will try to lock again and give it to the repair
Now I'm just waiting for proper LG G5 Port until Nougat is released [emoji14]
Wysłane z mojego LG-H815 przy użyciu Tapatalka
ObiDanKenobi said:
All the people are worried about warranty in case of a bootloop. How would you revert the 3 partitions content when the phone is bootlooping and you have access only to send_command.exe?
Click to expand...
Click to collapse
Maybe you can flash the kdz that disables the big cores and then you have a properly working phone, where you can do anything you like, such as relocking the bootloader...
ObiDanKenobi said:
All the people are worried about warranty in case of a bootloop. How would you revert the 3 partitions content when the phone is bootlooping and you have access only to send_command.exe?
Click to expand...
Click to collapse
You can import partition files to sdcard and flash it via send_command - and bootloader will be locked.
undef1ned said:
Oh, while my G4 is still in the owen now, I'm reading this thread H815 506 bootlooped this April. Warranty repair rejected. Worked with big-core disable tool for 6 months, until it finally died today.
Ok, if it is not finally dead after baking in the owen, then I will try to lock again and give it to the repair
Click to expand...
Click to collapse
As I wrote, I had bootloader UNLOCKED and i LG repaired my phone under warranty - i just destroyed it completly in the cooker and sent it to them just telling "i dont know whats happen, just bootloped and now died" - they wouldnt able to check bootloader state so ... >
xVANKO said:
As I wrote, I had bootloader UNLOCKED and i LG repaired my phone under warranty - i just destroyed it completly in the cooker and sent it to them just telling "i dont know whats happen, just bootloped and now died" - they wouldnt able to check bootloader state so ... >
Click to expand...
Click to collapse
I've bought mine in Poland. Unfortunately sent to repair with "Bootloader Unlocked" message on, just read several forums (including forum.android.com.pl) and some ppl shared positive experience of the unlocked phone to be fixed. Not sure if I can apply for the second time, may-be they've marked it as an unlocked somewhere in the database. Anyway I need to cross the UA/PL border twice to do it.
After baking method, my phone is on, but switching 4 small CPUs on - makes it supper laggy & unresponsive, however it does not go into bootloop mode
When are you going to post instructions?
Minto107 said:
Now I'm just waiting for proper LG G5 Port until Nougat is released [emoji14]
Wysłane z mojego LG-H815 przy użyciu Tapatalka
Click to expand...
Click to collapse
Relock will work also for LG G5 - this is the same security level and the same procedure
undef1ned said:
I've bought mine in Poland. Unfortunately sent to repair with "Bootloader Unlocked" message on, just read several forums (including forum.android.com.pl) and some ppl shared positive experience of the unlocked phone to be fixed. Not sure if I can apply for the second time, may-be they've marked it as an unlocked somewhere in the database. Anyway I need to cross the UA/PL border twice to do it.
After baking method, my phone is on, but switching 4 small CPUs on - makes it supper laggy & unresponsive, however it does not go into bootloop mode
When are you going to post instructions?
Click to expand...
Click to collapse
Tomorrow i will post video showing this method, instruction will be on Monday or Tuesday
Does that mean that there is a chance for an unofficial unlock in the near future? for those without EUR devices?
tim455 said:
Does that mean that there is a chance for an unofficial unlock in the near future? for those without EUR devices?
Click to expand...
Click to collapse
Yes, there is a big chance to unlock non-euro devices. Probably if you flash prepared by me dumps I can transorm any LG variant to EURO variant - of course with possibility to go back to stock.
Just uploaded video to main thread.
Nice ! Thanks .but i wait step by step instructions video very laggy :
When we can get dumps to flash ??
Hi, I want to backup my TA/DRM key. However the "Universal (Dirtycow-based) TA Backup v2" seems not compatible with Android Nougat. It asked me to downgrade my device first. Is there a way to downgrade Xperia X Compact without unlocking it (or without losing the DRM key)? Thanks.
yjcbn said:
Hi, I want to backup my TA/DRM key. However the "Universal (Dirtycow-based) TA Backup v2" seems not compatible with Android Nougat. It asked me to downgrade my device first. Is there a way to downgrade Xperia X Compact without unlocking it (or without losing the DRM key)? Thanks.
Click to expand...
Click to collapse
Just use the flashtool, you don't need to be unlocked to flash firmware.
XperienceD said:
Just use the flashtool, you don't need to be unlocked to flash firmware.
Click to expand...
Click to collapse
Thanks! Sucessfully downgrade to 6.0.1 and make a backup of the TA/DRM key just now.
XperienceD said:
Just use the flashtool, you don't need to be unlocked to flash firmware.
Click to expand...
Click to collapse
Another question. My phone is showing up "Bootloader unlock allowed: No" in the Service Menu. I've already turn on "OEM unlocking" and "USB debugging" (
authorized, and confirmed all the necessary drivers were installed).
The "Unlock your boot loader" site is saying that "It will only be possible to unlock the boot loader for certain releases." Does that means I should flash another firmware with differnt region or Android version? I've already tried to downgrade my phone to MM again, however the issue still exists. Thanks.
P.s. I am able to get the unlock code from the "Unlock your boot loader" site.
yjcbn said:
Another question. My phone is showing up "Bootloader unlock allowed: No" in the Service Menu. I've already turn on "OEM unlocking" and "USB debugging" (
authorized, and confirmed all the necessary drivers were installed).
The "Unlock your boot loader" site is saying that "It will only be possible to unlock the boot loader for certain releases." Does that means I should flash another firmware with differnt region or Android version? I've already tried to downgrade my phone to MM again, however the issue still exists. Thanks.
P.s. I am able to get the unlock code from the "Unlock your boot loader" site.
Click to expand...
Click to collapse
If your phone says that is is NOT allowed... sorry, but it is not possible.
Even though Sony is happy for us to unlock the bootloader, if the carrier/operator (verizon, o2, virgin, etc) wants - these companies can ask Sony to stop the bootloader from being unlocked.
Sim lock is one thing... at least that can be removed. I have no idea why they would choose to prevent the bootloader from being unlocked.
Actually, maybe because in some countries the consumer laws are very good, so even if you root or something, your warranty still exists.
But if you cannot unlock the bl -> you can't root -> less device problems/bricks -> less money on repairs for the phone operator? (just an idea)
The first (used) Xperia X Compact I bought, it was carrier branded, and the bootloader was unable to be unlocked.
I talked to the shop owner, I chose the other device in stock, it was unbranded, I could unlock it
qvmuhuuxz said:
If your phone says that is is NOT allowed... sorry, but it is not possible.
Even though Sony is happy for us to unlock the bootloader, if the carrier/operator (verizon, o2, virgin, etc) wants - these companies can ask Sony to stop the bootloader from being unlocked.
Sim lock is one thing... at least that can be removed. I have no idea why they would choose to prevent the bootloader from being unlocked.
Actually, maybe because in some countries the consumer laws are very good, so even if you root or something, your warranty still exists.
But if you cannot unlock the bl -> you can't root -> less device problems/bricks -> less money on repairs for the phone operator? (just an idea)
The first (used) Xperia X Compact I bought, it was carrier branded, and the bootloader was unable to be unlocked.
I talked to the shop owner, I chose the other device in stock, it was unbranded, I could unlock it
Click to expand...
Click to collapse
Thanks for your answer. Though it's a bad news for me. [emoji30]
Since it's impossible to unlock my device, can I just modify the FTF and flash it through the Flashtool? If it's possible, then how to modify the FTF file? I want to change the font into another.
yjcbn said:
Since it's impossible to unlock my device, can I just modify the FTF and flash it through the Flashtool?
Click to expand...
Click to collapse
No. If you've still got time to return it do so now otherwise your modding is going to be limited.
guys some one please explain me ...
why people are not providing their back ups to help others....?
1. what happens if they provide atleast boot loader image ?
2. can i take the same boot loader from other moto g5 plus or g5s plus which i very recent ?
3. after hard bricking my phone i installed Moto Zplay boot loader using albus blank flash to revive my phone again using custom rom.. Is there no way to change my phone's bootloader back to normal so that i can get back my boot loader??
if it is possible to provide, just provide me boot loader for Moto g5 plus....
will be waiting for Answers guys please help me out.
I'll try to answer
1)Though you could in theory back up your device bootloader with the dd command (partition level copy) via TWRP, I would not be comfortable advising you to dd any of the bootloader partitions to your device. The reason being that the bootloader is a critical part of your device's firmware and messing around with it, unless you are confident in rescuing the bootloader, is not something I can recommend. Besides, the bootloader is often the 'guardian of trust' and ensuring your device is not tampered with, so another reason to not flash any bootloaders besides those provided in stock firmware.
2)In theory, those bootloader images may work as your device's verification key should be the same as theirs (probably not G5S Pluses as their firmware is on 7.1.1 and likely use a different verification key). However, having the Moto Z Play bootloader would likely block a flash of the bootloader, since it's a different bootloader.
3)If you've previously hard bricked your device, then at the moment, as I understand it, there does not appear to be a way to get the Potter stock bootloader back on your device besides sending your device to service repair and possibly paying for a new motherboard. Your best bet otherwise is to stay with TWRP flashables. Maybe the stock Oreo fastboot ROM when that arrives may be able to repair your bootloader, but it's a long shot and it's entirely dependent on if the Oreo stock ROM comes with a new bootloader. You may also want to wait for a Oreo blankflash for potter, which may also restore your bootloader to the proper bootloader. Of course, this is the big problem with hard bricking - without the correct tools, it's difficult to properly recover from such an incident. I currently would not recommend going back to stock firmware and of course, you cannot re-lock your bootloader.
The bootloader images are provided with every fastboot image, in the form of the bootloader.img. For Indian devices (which I recall yours is), the latest potter firmware is NPNS25.137-92-8, though you could try NPN25.137-92 or NPNS25.137-92-4. https://forum.xda-developers.com/showpost.php?p=75839280&postcount=11 for NPNS25.137-92-4.
echo92 is totally correct in his explanations. As one who has "sacrificed" his device in the name of testing, I can affirm his assumptions regarding the bootloader. My device is usable but with being on albus it is limited in what I can test. One hope that we can cling to is, soak test has started on Moto Z Play, but evidently Lenovo engineers are having problems, as there has been several revisions, with very varied feedback. My thoughts are, if they can't get it right, how can we, without their source code.