Related
I decided to unlock it, then im stuck in bootloop... At first it says failed, then after i press it again, it says succrss, but i got a bootloop...
What causing this problem?
AndreIrawan97 said:
I decided to unlock it, then im stuck in bootloop... At first it says failed, then after i press it again, it says succrss, but i got a bootloop...
What causing this problem?
Click to expand...
Click to collapse
When you unlock the bootloader via sony's official way (using fastboot mode) your security related contents (DRM keys) in trim/TA partition gets erased and you will have access to install a new custom rom . But while unlocking is under progress, say for any reason it gets interrupted,there is a chance that all security related data might not be erased fully / In other words there is a chance that TA partition might have been corrupted
Usually when your phone boots its verifies for the intactness of TA/Trim partition, either it should have all security data (locked bootloader) or fully erased security related data (unlocked bootloader), if partial security information is available, it considers that TA partition has been tampered and will refuse to boot
gokukaushik said:
When you unlock the bootloader via sony's official way (using fastboot mode) your security related contents (DRM keys) in trim/TA partition gets erased and you will have access to install a new custom rom . But while unlocking is under progress, say for any reason it gets interrupted,there is a chance that all security related data might not be erased fully / In other words there is a chance that TA partition might have been corrupted
Usually when your phone boots its verifies for the intactness of TA/Trim partition, either it should have all security data (locked bootloader) or fully erased security related data (unlocked bootloader), if partial security information is available, it considers that TA partition has been tampered and will refuse to boot
Click to expand...
Click to collapse
So.... How to properly unlock it? And what should i do if i got a bootloop again?
AndreIrawan97 said:
So.... How to properly unlock it? And what should i do if i got a bootloop again?
Click to expand...
Click to collapse
Right now if you are able to boot into your phone, leave it, you have already unlocked/relocked it. If you are in the same situation again,
Steps
1) Relock your bootloader via flashtool
2) Now flash a fully bundled sony official ftf via flashtool.(This will ensure that if any discrepencies in TA partition are there, will be corrected)
Note: This will not restore your DRM keys.I am afraid if you have not backed up your DRM keys during first unlocking trail.they are lost.
3) Follow sony's official bootloader unlock method (www.developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader)
gokukaushik said:
Right now if you are able to boot into your phone, leave it, you have already unlocked/relocked it. If you are in the same situation again,
Steps
1) Relock your bootloader via flashtool
2) Now flash a fully bundled sony official ftf via flashtool.(This will ensure that if any discrepencies in TA partition are there, will be corrected)
Note: This will not restore your DRM keys.I am afraid if you have not backed up your DRM keys during first unlocking trail.they are lost.
3) Follow sony's official bootloader unlock method (www.developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader)
Click to expand...
Click to collapse
So... Can i just restore TA and unlock it? Because i have a TA backup
AndreIrawan97 said:
So... Can i just restore TA and unlock it? Because i have a TA backup
Click to expand...
Click to collapse
Good that you had a TA backup before unlocking.If you restore your TA backup and unlock it again , it will again erase your security keys, which will lead you to where you started.What is your requirement . Unlock your bootloader only if you want to install a custom rom. Believe me, TA partition is not the one to be played with; it can even render your mobile into a costly paper weight(hardbrick), if it gets messed up pretty bad . If you are already unlocked do not try to restore your TA partition,and unlock again.Its already unlocked and doesnt make any sense to unlock it again ; Restore it only when you want to go back to a locked bootloader.
Ok so i have read many posts on XDA about bricked nexus 5x's and many others, sometimes the main probelm is the oem isnt unlocked. I myself have a Nexus 5x that is completely stock no custom recovery no root no nothing, i just update the phone, right now on Nougat 7.0 sep security update.
So my question is, should i check the OEM unlocking in the settings ? i will never install any recovery or root but i think by reading the posts, it seems like its a major problem if this is not checked, should i check it just to be safe ?
U_Midrar said:
Ok so i have read many posts on XDA about bricked nexus 5x's and many others, sometimes the main probelm is the oem isnt unlocked. I myself have a Nexus 5x that is completely stock no custom recovery no root no nothing, i just update the phone, right now on Nougat 7.0 sep security update.
So my question is, should i check the OEM unlocking in the settings ? i will never install any recovery or root but i think by reading the posts, it seems like its a major problem if this is not checked, should i check it just to be safe ?
Click to expand...
Click to collapse
If you have issues in your current state they will most likely be hardware related and unfixable via software. But even locked you can completely reinstall the OS via sideloading an OTA or using the TOT method.
Enabling OEM unlock disables Factory Reset Protection (FRP). FRP is a security feature that prevents a stolen device from being activated. There is allot of info about it online if you wish to learn more.
So you need to decide if you want FRP or the ability to flash the factory images.
Sent from my XT1650 using Tapatalk
PiousInquisitor said:
If you have issues in your current state they will most likely be hardware related and unfixable via software. But even locked you can completely reinstall the OS via sideloading an OTA or using the TOT method.
Enabling OEM unlock disables Factory Reset Protection (FRP). FRP is a security feature that prevents a stolen device from being activated. There is allot of info about it online if you wish to learn more.
So you need to decide if you want FRP or the ability to flash the factory images.
Click to expand...
Click to collapse
ok thx dude for the reply, nah i dont care about the FRP. so flashing factory images is easier right ? rather than sideloading or whatever this TOT method is...., and do most mobiles have a oem locked or unlocked ?
U_Midrar said:
ok thx dude for the reply, nah i dont care about the FRP. so flashing factory images is easier right ? rather than sideloading or whatever this TOT method is...., and do most mobiles have a oem locked or unlocked ?
Click to expand...
Click to collapse
Sure, flashing the factory images is probably slightly easier than the other methods. Note that in your case you would need to actually unlock the bootloader to flash the images. With those added steps it's probably faster to sideload.
The Allow OEM unlock toggle has been around since LP I think. An pretty sure it's in phones that shipped with LP. It didn't automagically mean that the phones bootloader can be unlocked though. It should stop disable FRP though.
Sent from my XT1650 using Tapatalk
Yes, most, I think all OEMs leave the possibility to unlock the bootloader.
By default the bootloader is locked on most OEMs (Sony, Samsung, HTC, Motorola, even Nexus devices).
For Nexus devices it's a simple one liner to unlock/lock the bootloader which will also trigger a data wipe but. On Nexus devices it doesn't void your warranty.
For most other OEMs phones you have to follow some steps and usually get some kind of code in order to unlock the bootloader the first time. This will void your warranty!
If you don't know whether or not you should unlock/lock the bootloader, the answer is: NO!
It seems you're not modifying your phones software (Custom Kernel, Custom Rom, Root etc) and you seem to have no intention doing so. So it's not needed and even less "secure" than with locked bootloader. If you do, you should know that you have to unlock the bootloader in order to change the phones software.
Why would you want to unlock the bootloader when the only reason to do so is to modify the software and you do not plan to do this?
On a stock nexus there is no need to unlock the bootloader, you can even reflash your phone with locked bootloader with the stock software image.
creambyemute said:
Yes, most, I think all OEMs leave the possibility to unlock the bootloader.
By default the bootloader is locked on most OEMs (Sony, Samsung, HTC, Motorola, even Nexus devices).
For Nexus devices it's a simple one liner to unlock/lock the bootloader which will also trigger a data wipe but. On Nexus devices it doesn't void your warranty.
For most other OEMs phones you have to follow some steps and usually get some kind of code in order to unlock the bootloader the first time. This will void your warranty!
If you don't know whether or not you should unlock/lock the bootloader, the answer is: NO!
It seems you're not modifying your phones software (Custom Kernel, Custom Rom, Root etc) and you seem to have no intention doing so. So it's not needed and even less "secure" than with locked bootloader. If you do, you should know that you have to unlock the bootloader in order to change the phones software.
Why would you want to unlock the bootloader when the only reason to do so is to modify the software and you do not plan to do this?
On a stock nexus there is no need to unlock the bootloader, you can even reflash your phone with locked bootloader with the stock software image.
Click to expand...
Click to collapse
yo dude thx for the reply, as i said in my first post, i saw some bricked nexus 5x (they didnt mod anything i think) that couldnt be repaired cause he had the option unchecked about OEM, that is why i was asking for like a safety precaution that if something goes wrong it would be okay cause oem could be unlocked then... what do u say now ? (and yea im not gonna ever mod anything in the phone, learned fom my last phone which i somehow bricked and a man fixed it for for 5$ )
U_Midrar said:
yo dude thx for the reply, as i said in my first post, i saw some bricked nexus 5x (they didnt mod anything i think) that couldnt be repaired cause he had the option unchecked about OEM, that is why i was asking for like a safety precaution that if something goes wrong it would be okay cause oem could be unlocked then... what do u say now ? (and yea im not gonna ever mod anything in the phone, learned fom my last phone which i somehow bricked and a man fixed it for for 5$ )
Click to expand...
Click to collapse
That catch is if if you checked OEM unloking and chose to not perform oem unlock command now.
When something did went wrong afterward, you are able to perform oem unlock but it will wipe your data.
There is no point for doing it.
HebeGuess said:
That catch is if if you checked OEM unloking and chose to not perform oem unlock command now.
When something did went wrong afterward, you are able to perform oem unlock but it will wipe your data.
There is no point for doing it.
Click to expand...
Click to collapse
so i shouldnt do it like just leave it be ?
F IT I DID IT
i just read this site and also got to know a bootloop can occur with OTA update so yea i have done it.
Site: http://android.wonderhowto.com/news...ting-before-modding-anything-android-0167840/
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
mapki said:
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
Click to expand...
Click to collapse
I believe you're not able to relock the bootloader until Motorola release a signed bootloader. I had the page once before I'll see if I can find it again and add an edit if I do.
mapki said:
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
Click to expand...
Click to collapse
Don't relock your bootloader unless you want a brick. Technically you can relock it, but everything has to be legit. You've already voided the warranty, relocking won't reinstate that, all that will happen is you'll be bricked with nothing to do about it because you've locked the bootloader.
Why do you want to relock it?
I would like to relock my bootloader and wondering the accuracy of this last post. Will relocking my Sprint Z2 Force bootloader brick my device?
I'm running completely stock via OTA 8.0.0 no root. The reason I want to relock my bootloader is bringing my phone to out of box status and pass SafetyNet. I don't want to root to get this done and I want to continue receiving OTA's.
I understand that my warranty is void when I unlocked bootloader originally and I understand relocking my bootloader will wipe data (factory reset).
Will this brick my phone?
Can I relock anymore?
What are the fastboot commands to relock the Z2?
Thanks!
jeffritz1 said:
I would like to relock my bootloader and wondering the accuracy of this last post. Will relocking my Sprint Z2 Force bootloader brick my device?
I'm running completely stock via OTA 8.0.0 no root. The reason I want to relock my bootloader is bringing my phone to out of box status and pass SafetyNet. I don't want to root to get this done and I want to continue receiving OTA's.
I understand that my warranty is void when I unlocked bootloader originally and I understand relocking my bootloader will wipe data (factory reset).
Will this brick my phone?
Can I relock anymore?
What are the fastboot commands to relock the Z2?
Thanks!
Click to expand...
Click to collapse
I would suggest flashing one of the flash alls for sprint before doing it to ensure being fully stock. The command is below. Also i f you ever have any issues and want to reunlock, you always can with your original unlock code.
"fastboot oem lock"
You'll get a "are you sure" message. Type in the command again and poof, relocked status.
Uzephi said:
I would suggest flashing one of the flash alls for sprint before doing it to ensure being fully stock. The command is below. Also i f you ever have any issues and want to reunlock, you always can with your original unlock code.
"fastboot oem lock"
You'll get a "are you sure" message. Type in the command again and poof, relocked status.
Click to expand...
Click to collapse
So, I did a "fastboot oem lock" and it re locked the bootloader. Restart bootloader, shows locked. Restart phone and still getting a splash screen similar to the one when your unlocked but this time it says "Device has loaded a different Operating System". Continues to boot normally into the system without issues. This was odd so I unlocked again did a Flashall w/ "XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" and "fastboot oem lock". Both times said the lock was successful. But I'm still getting this boot splash screen with test reading "Device has loaded a different Operating System". System boots but still fails SafetyNet.
What gives? What am I missing?
From what I can muster up on XDA I can see that "you need a signed boot.img". Does this mean something and how can I find this?
Can anyone who has unlocked and then relocked their bootloader report on the behavior of your phone? Do you get the same "different OS" splash screen? Has anyone been successful at making it go away and passing safetynet?
jeffritz1 said:
Can anyone who has unlocked and then relocked their bootloader report on the behavior of your phone? Do you get the same "different OS" splash screen? Has anyone been successful at making it go away and passing safetynet?
Click to expand...
Click to collapse
I've been working on this all morning trying a couple different methods. But none have been successful. But the best I can figure, when in bootloader, there is a message stating that your system is "Modified". Somehow, that needs to get changed to what I can only speculate as "unmodified", or something alike.
I tried 3 different versions of returning to stock
First one I tired I cannot seemed to find now
Secondly, I tired:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
Posted by Uzephi
I added the command "fastboot oem lock" 2 times just above the fastboot reboot command; thus locking bootloader.
But upon reboot, I still get the modified OS message.
Lastly, I tried this method
https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
I downloaded https://mirrors.lolinet.com/firmware/moto/nash/official/TMO/XT1789-04_NASH_TMO_C_8.0.0_OCX27.109-36_subsidy-TMO_regulatory-DEFAULT_CFC.xml.zip
Followed the instructions (to some degree) and modified them for Linux since I am not a windows user.
After reboot, radio did not work. No WiFi, not data, nothing. Developer options was already enabled, but oem bootloader unlocking option was grayed out. Now I cannot unlock my bootloader and flash an updated OS.
Thanks for the reply! As of now I am stock latest Sprint 8.0.0 July update with bootloader locked. I get the "Your device has loaded a different Operating System" splash screen when I boot up with a "ID:" followed by nothing. I don't know what this "ID:" with nothing following this means. Also when I run a SafetyNet status app is says failed. But, everything else in the OS appears to be working. Google Play shows "Certified" status and all my apps that require SafetyNet is working (Banking apps, Netflix, Hulu, Google Pay, etc...). So I accomplished my mission in getting these apps working and everything else appears stock. The only thing that troubles me is this "Your device has loaded a different Operating System" splash screen and the failed status in the SafetyNet app. Would love to know how to fix this or an explanation on why.
jeffritz1 said:
Thanks for the reply! As of now I am stock latest Sprint 8.0.0 July update with bootloader locked. I get the "Your device has loaded a different Operating System" splash screen when I boot up with a "ID:" followed by nothing. I don't know what this "ID:" with nothing following this means. Also when I run a SafetyNet status app is says failed. But, everything else in the OS appears to be working. Google Play shows "Certified" status and all my apps that require SafetyNet is working (Banking apps, Netflix, Hulu, Google Pay, etc...). So I accomplished my mission in getting these apps working and everything else appears stock. The only thing that troubles me is this "Your device has loaded a different Operating System" splash screen and the failed status in the SafetyNet app. Would love to know how to fix this or an explanation on why.
Click to expand...
Click to collapse
That message appear because you've unlocked your bootloader before, I'm getting that message too and I can update my device via OTA. If you change that splash screen OTAs will fail.
Marcowe said:
That message appear because you've unlocked your bootloader before, I'm getting that message too and I can update my device via OTA. If you change that splash screen OTAs will fail.
Click to expand...
Click to collapse
Yeah, I was trying to find out if the phone could be reverted back to an out of back state. Another words, no splash screen saying "HEY! I HAVE BEEN MESSED WITH!" like you can on any other phone I have ever owned.
Thanks!
Yes you can
thomas.raines said:
I've been working on this all morning trying a couple different methods. But none have been successful. But the best I can figure, when in bootloader, there is a message stating that your system is "Modified". Somehow, that needs to get changed to what I can only speculate as "unmodified", or something alike.
I tried 3 different versions of returning to stock
First one I tired I cannot seemed to find now
Secondly, I tired:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
Posted by Uzephi
I added the command "fastboot oem lock" 2 times just above the fastboot reboot command; thus locking bootloader.
But upon reboot, I still get the modified OS message.
Lastly, I tried this method
https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
I downloaded https://mirrors.lolinet.com/firmware/moto/nash/official/TMO/XT1789-04_NASH_TMO_C_8.0.0_OCX27.109-36_subsidy-TMO_regulatory-DEFAULT_CFC.xml.zip
Followed the instructions (to some degree) and modified them for Linux since I am not a windows user.
After reboot, radio did not work. No WiFi, not data, nothing. Developer options was already enabled, but oem bootloader unlocking option was grayed out. Now I cannot unlock my bootloader and flash an updated OS.
Click to expand...
Click to collapse
Yes you can , I already had this issue with my moto z2 force in Morocco , so what I did is I connected the phone to internet via bluetooth and when I added my google accounte the unlocking oem in dev option was normal , so I was able to flash roms again . Hope this will help you
I think there is no way to relock bootloader without wipe the device. Also you can relock the bootloader and you will not have any problems. I've already done it, at least with my sprint moto z2 force. the message there is no way to remove it, only flashing a logo.bin, "the boot splash" or replacing the logo.bin of the flash all package by the one of your preference.
EddiePR said:
I think there is no way to relock bootloader without wipe the device. Also you can relock the bootloader and you will not have any problems. I've already done it, at least with my sprint moto z2 force. the message there is no way to remove it, only flashing a logo.bin, "the boot splash" or replacing the logo.bin of the flash all package by the one of your preference.
Click to expand...
Click to collapse
If you do that OTAs will fail
Marcowe said:
If you do that OTAs will fail
Click to expand...
Click to collapse
Yes, you are rigth
So, which of the methods to re-lock did finally work? I was running on Android 8 before, OTA failes for at least 10 times, but suddenly it worked to upgrade to Android 9. Now I am weirdly not passing SafetyNet-check anymore (was working fine on Android 8, GooglePay etc).
Any recommendations? I just need the stupid GPay thing working
Would there be a way to do one-click-root on the Motorola Moto G5 (XT1672) or another way that is easy and does not do a factory reset? Thanks!
vanhead said:
Would there be a way to do one-click-root on the Motorola Moto G5 (XT1672) or another way that is easy and does not do a factory reset? Thanks!
Click to expand...
Click to collapse
I really don't know how this is going from root very well, but as I understand it, you need to unlock the bootloader of the device (which requires a factory reset). If you already have the bootloader unlocked, try KingRoot, The truth is the only root of a click that I know, I have not really tried it on this device, but on an old phone, and it worked fine. The only problem I have had and I do not know if it is the fault of the device or KingRoot, and is that when I try to uninstall an application which I gave it the root permissions, the phone restarts, to uninstall an application I had to deny it permissions and then I could uninstall it, I repeat, I do not know if it is a problem that only happens to me
Postdata: Sorry for my english
vanhead said:
Would there be a way to do one-click-root on the Motorola Moto G5 (XT1672) or another way that is easy and does not do a factory reset? Thanks!
Click to expand...
Click to collapse
Rooting the phone does not require a factory reset but unlocking the bootloader does
So if you haven't unlocked the bootloader you will have to factory reset it during the process
If the bootloader is already unlocked you do not need to factory reset your device again in order to root it
Magisk should be the only way you should root your device - do not use other methods like kingroot as this has bloat and is not systemless (meaning it alters the system partition)
You need to root with magisk in order to maintain the system partition in its original state in order to pass basic integrity & to be able to pass cts profile (may need a magisk module) and to hide the fact you are rooted from apps that will not work if your device is rooted
TheFixItMan said:
Rooting the phone does not require a factory reset but unlocking the bootloader does
So if you haven't unlocked the bootloader you will have to factory reset it during the process
If the bootloader is already unlocked you do not need to factory reset your device again in order to root it
Magisk should be the only way you should root your device - do not use other methods like kingroot as this has bloat and is not systemless (meaning it alters the system partition)
You need to root with magisk in order to maintain the system partition in its original state in order to pass basic integrity & to be able to pass cts profile (may need a magisk module) and to hide the fact you are rooted from apps that will not work if your device is rooted
Click to expand...
Click to collapse
Thank you for your help. I tried several One-click-root, none worked, so I researched, they only work on android 7.
Could you tell me if it is possible to Downgrade from Android 8.1 to 7 without unlocking the bootloader? All the videos I find, the bootloaders are already unlocked.
vanhead said:
Thank you for your help. I tried several One-click-root, none worked, so I researched, they only work on android 7.
Could you tell me if it is possible to Downgrade from Android 8.1 to 7 without unlocking the bootloader? All the videos I find, the bootloaders are already unlocked.
Click to expand...
Click to collapse
As mentioned before - you cannot root a device without unlocking the bootloader!
Why do you want a one click root? They are buggy & full of bloatware
Magisk should be the only method you should be using to root a device - either flashing through twrp or by patching the kernel and flashing the patched image through fastboot
What ever method you choose you need an unlocked bootloader to root!
Why would you want to downgrade? You can flash all parts of a firmware image except gpt & bootloader but again you might need an unlocked bootloader to do this but I don't see the point
TheFixItMan said:
As mentioned before - you cannot root a device without unlocking the bootloader!
Why do you want a one click root? They are buggy & full of bloatware
Magisk should be the only method you should be using to root a device - either flashing through twrp or by patching the kernel and flashing the patched image through fastboot
What ever method you choose you need an unlocked bootloader to root!
Why would you want to downgrade? You can flash all parts of a firmware image except gpt & bootloader but again you might need an unlocked bootloader to do this but I don't see the point
Click to expand...
Click to collapse
In fact, since i need to unlock the bootloader to root, for now, it wouldn't be a good option for me.
But there are apps that I really need and that don't work correctly on Android versions above Nougat, if I could get Downgrade without losing data, that would help me immensely for now.
Is there a possibility that I can downgrade to android 7 with the locked bootloader ? What can go wrong? Brick?
vanhead said:
In fact, since i need to unlock the bootloader to root, for now, it wouldn't be a good option for me.
But there are apps that I really need and that don't work correctly on Android versions above Nougat, if I could get Downgrade without losing data, that would help me immensely for now.
Is there a possibility that I can downgrade to android 7 with the locked bootloader ? What can go wrong? Brick?
Click to expand...
Click to collapse
You would have to format data - it would bootloop otherwise and I've already said. Flash all parts of firmware except gpt and bootloader however it may not flash as your bootloader is not unlocked
If the flashing goes wrong and your bootloader is not unlocked you will not be able to recover the device without taking it to a repair shop
My advice just don't bother - if you want to mod your phone unlock the bootloader!
And what app doesn't work above nougat?
Hello.
I am currently looking to buy this phone and flash a custom os, if someone could please answer them that would be great:
1) After unlocking and locking does the phone go back to Widevine L1?
2) How easy is it to unlock the phone's bootloader (is it as simple as fastboot oem unlock or similar?) and how hard is it to lock the phone's bootloader (is it as easy as fastboot oem lock?)
3) Do most custom OS's support Widevine L1?
4) If I lock the bootloader whilst having a custom OS how hard is it to flash back the stock OS?
Looking forward for replies.
Hey there!
1. I am currently rooted and it still says Widevine L1 (checked with DRM Info app).
2. I don't think there's a phone that has easier bootloader unlocking/locking.
3. The Zephyrus custom ROM, which I currently use has Widevine L1 support. I don't know about other roms.
4. Haven't done that personally, I know GrapheneOS recommends locking the bootloader for better security, but I am pretty sure it doesn't have to be permanent, and it should be fairly easy to go back to the stock firmware. Just remember not to lock the bootloader while rooted, as that would brick your device and it probably wouldn't be easy to fix.
Hello. For exact instructions on how to unlock the bootloader, click the yellow "How-To Guide" quick filter at the top of the list of threads in this section. You'll see three or more guides that include the subject.