Related
Installation Steps (Warranty can be restored whenever you wish)
-------------------------
Before starting your rom flashing journey it is always better to have Flashtool (latest -by androxyde) installed in your PC and your stock rom handy ; incase of any mishappenings.
Type *#*#7378423#*#* in your phone and see if your bootloader status is unlockable under service-->Configuration. Procede with below steps, only if your device is unlockable.
It is important that you follow the steps in order
1) First step for installing a custom rom over a mobile with stock rom is to backup the existing state of bootloader .Usually warranty will get void if any modification is done to bootloader. The below tool ensures that it takes the backup of existing state of bootloader when device is under warranty.
Goto
Backup TA for Sony Xperia (This tool helps you to have a )
http://forum.xda-developers.com/showthread.php?t=2292598.
Download the tool.This tool will backup your DRM Securtiy keys . Successful backup can only be taken after the existing stock rom is rooted (Use towelroot application if your device is not already rooted) .Root it first then follow the process given in above link .
Once this is over , u will have a backup of the existing state of bootloader/TA partition (If you later wish to move back to stock rom from custom rom use the same tool to restore the backup you have just created.This means you will get your Warranty back);
2) Goto this website , follow the steps and get your unlock code via e mail.
Use fastboot mode to unlock your bootloader (Make sure that you have already backuped your existing DRM keys-Step 1).Follow it fully to unlock your bootloader
http://unlockbootloader.sonymobile.com/unlock/step1
3)Download any custom rom zips with recovery, for your mobile from xda developers forum and have fun.Extract boot.img using winrar or winzip .
Flash boot.img via fastboot mode
fastboot flash boot boot.img
fastboot reboot
4)As the device reboots, when you see your LED glow press volume up or down. It will take you to CWM Recovery or TWRP recovery based on the rom that you have downloaded.
5)Just install the custom rom(*.zip ) from within the recovery.
What if that i already have the custom recovery?
So, just wipe data, dalvik, and cache, then flash the zip?
That's it?
AndreIrawan97 said:
What if that i already have the custom recovery?
So, just wipe data, dalvik, and cache, then flash the zip?
That's it?
Click to expand...
Click to collapse
yes.
AndreIrawan97 said:
What if that i already have the custom recovery?
So, just wipe data, dalvik, and cache, then flash the zip?
That's it?
Click to expand...
Click to collapse
Absolutely right. But before installing an custom rom in the first place i hope you have already backed up your DRM keys for warranty purpose(as mentioned in the guide) since if you unlock your bootloader without backing up your DRM keys, DRM keys might be lost forever .
gokukaushik said:
Absolutely right. But before installing an custom rom in the first place i hope you have already backed up your DRM keys for warranty purpose(as mentioned in the guide) since if you unlock your bootloader without backing up your DRM keys, DRM keys might be lost forever .
Click to expand...
Click to collapse
Can i backup my app on stock rom then restore it to a custom rom?
AndreIrawan97 said:
Can i backup my app on stock rom then restore it to a custom rom?
Click to expand...
Click to collapse
Sure. Easiest way to do it is by using an app called, 'Titanium Backup Pro'.But you have to root your stock rom first for this application to run(Use towelroot if you are yet to root).Except for sony proprietary apps like walkman,Album,etc (will run only on stock rom as they use sony developed system libraries/API'S) other apps will get restored/run fine on a custom rom.
gokukaushik said:
Sure. Easiest way to do it is by using an app called, 'Titanium Backup Pro'.But you have to root your stock rom first for this application to run(Use towelroot if you are yet to root).Except for sony proprietary apps like walkman,Album,etc (will run only on stock rom as they use sony developed system libraries/API'S) other apps will get restored/run fine on a custom rom.
Click to expand...
Click to collapse
And one think left.... How to know if my bootloader is unlocked or not?
AndreIrawan97 said:
And one think left.... How to know if my bootloader is unlocked or not?
Click to expand...
Click to collapse
its in the OP....on the phones dialpad, type: *#*#7378423#*#*
then look in > service > configuration
it should show the status as "bootloader locked", "bootloader unlocked", "bootloader unlockable" or "not unlockable" (sorry wording may not be exact, but you'll get the idea)
foomanjackel said:
its in the OP....on the phones dialpad, type: *#*#7378423#*#*
then look in > service > configuration
it should show the status as "bootloader locked", "bootloader unlocked", "bootloader unlockable" or "not unlockable" (sorry wording may not be exact, but you'll get the idea)
Click to expand...
Click to collapse
no.. i mean, how to know if my bootloader is already unlocked or not?
Anyway, what happened if i flash it without unlocking it first?
Sorry, did you type that in the phone and check the status? That's where it will tell you if its already unlocked or if its even unlockable at all.
Do not try to install a custom ROM on your phone if it is not unlocked! Your phone will not boot.
AndreIrawan97 said:
no.. i mean, how to know if my bootloader is already unlocked or not?
Anyway, what happened if i flash it without unlocking it first?
Click to expand...
Click to collapse
Thanks to @ foomanjackel for answering your questions.Regarding your 2nd question, 'Experience is the mother of invention'.Why don't you try and see what happens...just kidding.Couldn't resist it. Practically speaking of you install a custom rom with an custom kernel on a locked bootloader you will hard brick it.It will not boot and chances are that you might not be able to goto flashmode or fastbootmode anymoreto repair it.Reason this happens is that both your recovery and bootloader resides in the same partition in your mobile.If you try to install custom kernel on a locked bootloader in every probability, it not only corrupts your existing stocks kernel but also might corrupt your recovery leaving u helpless.
Theoretically, You should be able to install any custom-stock based rom on a locked bootloader (which runs exactly on ur stock kernel).In other words a custom rom which doesn't come up with a custom kernel but based on your existing stock kernel should be able to run on a locked bootloader.But my advice is you do not risk it.
foomanjackel said:
Sorry, did you type that in the phone and check the status? That's where it will tell you if its already unlocked or if its even unlockable at all.
Do not try to install a custom ROM on your phone if it is not unlocked! Your phone will not boot.
Click to expand...
Click to collapse
Yes it said boot loader unlockable : yes
And couple months ago, i want to unlock my bootloader, but i dont know what went wrong, but my xperia got boot loop...
So is that bcs i already unlocked it? Or... ?
AndreIrawan97 said:
Yes it said boot loader unlockable : yes
And couple months ago, i want to unlock my bootloader, but i dont know what went wrong, but my xperia got boot loop...
So is that bcs i already unlocked it? Or... ?
Click to expand...
Click to collapse
If you get this message "Bootloader unlockable: yes" then your bootloader is still locked.
gokukaushik said:
If you get this message "Bootloader unlockable: yes" then your bootloader is still locked.
Click to expand...
Click to collapse
Is unlocking bootloader can make me lose my root?
AndreIrawan97 said:
Is unlocking bootloader can make me lose my root?
Click to expand...
Click to collapse
I suppose it won't.I don't see the reason why u want to unlock the bootloader unless you want to install a new custom rom.
SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.
jdubya45 said:
SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.
Click to expand...
Click to collapse
Can you boot into bootloader mode what so ever?
Yes only into bootloader. Can't unlock again though. Won't let me.
stevew84 said:
Can you boot into bootloader mode what so ever?
Click to expand...
Click to collapse
Only can get into bootloader but cannot unlock again. Everything else is gone.
jdubya45 said:
Yes only into bootloader. Can't unlock again though. Won't let me.
Click to expand...
Click to collapse
Have you tried to manually do this with ADB with the command prompt?
fastboot flashing unlock
stevew84 said:
Can you boot into bootloader mode what so ever?
Click to expand...
Click to collapse
stevew84 said:
Have you tried to manually do this with ADB with the command prompt?
fastboot flashing unlock
Click to expand...
Click to collapse
Yes. Fails. Remote fail and not allowed.
jdubya45 said:
Yes. Fails. Remote fail and not allowed.
Click to expand...
Click to collapse
I don't have the Pixel, so I'm going off of what I know from the 6P.
Does the Toolkit work for the Pixel? There has to be a way to get it working if you can get into bootloader.
stevew84 said:
I don't have the Pixel, so I'm going off of what I know from the 6P.
Does the Toolkit work for the Pixel? There has to be a way to get it working if you can get into bootloader.
Click to expand...
Click to collapse
I am not sure. I think I need Unlocked bootloader.
Actually i think you just need to reunlock using depixel8. That should unlock your bootloader and allow you to flash new firmware
Did you try using dePixel8 to to unlock your bootloader back? I would try that.
Sent from my Pixel XL using XDA Labs
Marghost said:
Did you try using dePixel8 to to unlock your bootloader back? I would try that.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
You have to be booted in Android for dePixel8 to work.
Am I missing something? why can't you just flash factory image again from the bootloader and then unlock your bootloader with the depixel8?
Sent from my Pixel XL using Tapatalk
MArtyChubbs said:
Am I missing something? why can't you just flash factory image again from the bootloader and then unlock your bootloader with the depixel8?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
He said that he tried to unlock the bootloader again and it won't let him. With a locked bootloader, you can't flash the system images.
Sent from my Pixel XL using XDA-Developers mobile app
Moderator warning,
I have cleaned this thread. XDA does not allow users to discuss fraud on this site.
jdubya45 said:
SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.
Click to expand...
Click to collapse
My mind is blown on how you accomplished this. Did you ERASE the partitions and then plan on flashing stock ones yourself? Why not just run the script (flash-all.bat) that would have automatically done the ENTIRE process for you, except re-locking the bootloader?
If all you did was re-lock the bootloader, it should have done a factory reset on the next boot and used the existing system partition. If you erased the system partition and then re-locked the bootloader, you are almost certainly screwed and had better hope Google has some mercy to let you RMA the phone.
Couple options you could try off the top of my head. The pixel has A/B patitions try adb sideloading an update zip to get it to switch to the backup partition that might still be there.
You could also try downloading the Factory images and extracting the system and go into fastboot and type
Code:
fastboot boot system system.img
and see if that works. Then if it boots on the temp image run deadpixel8 or whatever its called and reflash the stock image with the flash-all.bat.
have the same problem on my pixel after accidentally relocking after root before flashing back to stock.
Does anyone have the stock pixel xl recovery.img? I thinking if I boot into recovery "fast boot boot recovery.img" then I can add side load etc the ota from google.
jdubya45 said:
SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.
Click to expand...
Click to collapse
Insert BRICK emoji here
Atlantian said:
Insert BRICK emoji here
Click to expand...
Click to collapse
Hey, I unlocked my bootloader using fastboot like I've done 100 times.
After that I flashed the newest TWRP for the 5x and then it wouldn't decrypt my data.
I figured I'd boot into android but it's just stuck in the boot animation, what can I do?
Edit:
I can't keep the bootloader unlocked, as soon as I reboot anywhere, it's locked again.
Shebee said:
Hey, I unlocked my bootloader using fastboot like I've done 100 times.
After that I flashed the newest TWRP for the 5x and then it wouldn't decrypt my data.
I figured I'd boot into android but it's just stuck in the boot animation, what can I do?
Edit:
I can't keep the bootloader unlocked, as soon as I reboot anywhere, it's locked again.
Click to expand...
Click to collapse
Can you boot into the bootloader? if you can try reflashing it back stock also when you flashed the latest TWRP, did you flash via fastboot or did you flash it in twrp?
dominoeflux said:
Can you boot into the bootloader? if you can try reflashing it back stock also when you flashed the latest TWRP, did you flash via fastboot or did you flash it in twrp?
Click to expand...
Click to collapse
Yes, I can boot, the issue seems to be that the bootloader won't stay unlocked.
As soon asni restart it's locked again. I think that's why twrp can't encrypt my partition. And that somehow messes up the Android installation.
Any ideas why the bootloader won't stay unlocked?
Shebee said:
Yes, I can boot, the issue seems to be that the bootloader won't stay unlocked.
As soon asni restart it's locked again. I think that's why twrp can't encrypt my partition. And that somehow messes up the Android installation.
Any ideas why the bootloader won't stay unlocked?
Click to expand...
Click to collapse
You have a phone with a replaced motherboard just like the individual in the link below. If the phone was recently replaced, I recommend getting another refurb. If that's not possible, the reddit link in this thread may be helpful for you:
https://forum.xda-developers.com/nexus-5x/help/secure-boot-enabled-rpmb-t3617929
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
You have a phone with a replaced motherboard just like the individual in the link below. If the phone was recently replaced, I recommend getting another refurb. If that's not possible, the reddit link in this thread may be helpful for you:
https://forum.xda-developers.com/nexus-5x/help/secure-boot-enabled-rpmb-t3617929
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Well that sucks :/
Guess I'll just wait for my next phone.
Hello guys, I'm on LineageOS. I want to go back to Oxygen OS. But I can't because of my locked bootloader.
I did try to connect with the pc via adb: "Fastboot flash recovery recovery.img" and it's says everytime bootloader is locked enable OEM. I know the OEM is in the Developer Options but not for me. It's not available.
What to do now?
Code:
fastboot oem unlock
It will wipe all of your data.
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
djmcnz said:
It will wipe all of your data.
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
Click to expand...
Click to collapse
Just did it. And than this error.
tap build number 7 times to enable developer options, enable usb debugging, then u do the adb.
MrTalon4 said:
Just did it. And than this error.
Click to expand...
Click to collapse
Yes, that means it's not enabled in developer options.
Now you say you don't have that OEM option available in the developer options - are you sure you've turned developer options on? If not do as @gorillaCF says above.
If you have done that and still don't have the option then back everything up, do a factory reset and try again immediately after that.
Flash factory images and go back to clean stock. Boot OOS and enable oem unlock in dev options
EugenStanis said:
Flash factory images and go back to clean stock. Boot OOS and enable oem unlock in dev options
Click to expand...
Click to collapse
Flash with locked bootloader? Is this possible?
What's broken with TWRP? What happens when you boot to recovery? Do you have adb access in any sort of recovery state?
djmcnz said:
What's broken with TWRP? What happens when you boot to recovery? Do you have adb access in any sort of recovery state?
Click to expand...
Click to collapse
I can't boot in recovery I will be stuck in the OnePlus logo.
And yes, I have adb access but my bootloader locked...
MrTalon4 said:
I can't boot in recovery I will be stuck in the OnePlus logo.
And yes, I have adb access but my bootloader locked...
Click to expand...
Click to collapse
Can you boot the stock recovery using fastboot?
the Doctor said:
Can you boot the stock recovery using fastboot?
Click to expand...
Click to collapse
It always says FAILED: "unlock device to use command". (Fastboot boot recovery.img)
MrTalon4 said:
It always says FAILED: "unlock device to use command". (Fastboot boot recovery.img)
Click to expand...
Click to collapse
There is always this, but it will wipe everything and completely reset your phone:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
^
do that.
LineageOS 15.1 doesn't have the OEM unlock feature. Normally, if you temper with the system and lock the bootloader it won't boot at all making this option useless. At least that's what I've experienced. As others stated you can only use the unbrick tool which will definitely work or contact OnePlus for an L2 technician who will use the same tool to do so.
So how did you do this? Did you do "fastboot oem lock" with TWRP and LineageOS on the device?
Macusercom said:
LineageOS 15.1 doesn't have the OEM unlock feature. Normally, if you temper with the system and lock the bootloader it won't boot at all making this option useless. At least that's what I've experienced. As others stated you can only use the unbrick tool which will definitely work or contact OnePlus for an L2 technician who will use the same tool to do so.
Click to expand...
Click to collapse
Why the hell LineageOS 15.1 don't have the OEM unlock? This makes no sense, because now I have a big problem.
Yeah, the unbrick tool I'm lucky but for the others with different devices will not have this unbrick tool. That's very stupid. It will be last time for me, with LineageOS.
the Doctor said:
So how did you do this? Did you do "fastboot oem lock" with TWRP and LineageOS on the device?
Click to expand...
Click to collapse
I did nothing like this. It was just locked I was surprised to.
MrTalon4 said:
I did nothing like this. It was just locked I was surprised to.
Click to expand...
Click to collapse
Normally, it is impossible to lock it without fastboot. Again, it's not LOS's fault. You should never lock your bootloader if on a custom ROM or modified system. I've been running LOS 15.1 for almost a week and never had such an issue.
MrTalon4 said:
Flash with locked bootloader? Is this possible?
Click to expand...
Click to collapse
Yes, afaik You can flash factory images without unlocking bootloader
EugenStanis said:
Yes, afaik You can flash factory images without unlocking bootloader
Click to expand...
Click to collapse
Sorry sir, but the factory Images means stock ROM and stock recovery.
Can't flash both
Why there is no backdoor for this situation? Why is this not possible, that you need by Factory images no unlocked bootloader. That would fix many problems.
Hey guys,
i just want to ask if there is a tested method to relock the bootloader of a rooted A2 Lite.
I use the stock rom, just unlocked and rooted it.
I've read something about the MiFlashTool and the Clean and Lock Option.
But I'm not sure about that, because the MiFlashTool is for Miui.
So what are the steps to relock the bootloader?
Thank you for your help
Mansil234 said:
Hey guys,
i just want to ask if there is a tested method to relock the bootloader of a rooted A2 Lite.
I use the stock rom, just unlocked and rooted it.
I've read something about the MiFlashTool and the Clean and Lock Option.
But I'm not sure about that, because the MiFlashTool is for Miui.
So what are the steps to relock the bootloader?
Thank you for your help
Click to expand...
Click to collapse
The MiFlashTool is also for the Stock Rom of the Mi A2 Lite (Not only MIUI!)
Download the Stock Rom and you can flash it via MiFlash. If you choose the option, you can relock the Bootloader when you do this.
Woah there buddy, if you try to lock a rooted phone you will have a hard brick. Don't try to lock the bootloader of a phone that is rooted or have system/boot etc. modifications.
marstonpear said:
Woah there buddy, if you try to lock a rooted phone you will have a hard brick. Don't try to lock the bootloader of a phone that is rooted or have system/boot etc. modifications.
Click to expand...
Click to collapse
And If i First delete the root-rights?
Mansil234 said:
And If i First delete the root-rights?
Click to expand...
Click to collapse
Not sure if it would work, the cleanest way would be to download official fastboot ROM, flash it via MiFlash (select clean and lock option). This will erase all your data and turn your phone to stock ROM. I'm saying this is the cleanest way because you may have issues by unrooting and locking the phone. Maybe it would work. Unsure.
marstonpear said:
Not sure if it would work, the cleanest way would be to download official fastboot ROM, flash it via MiFlash (select clean and lock option). This will erase all your data and turn your phone to stock ROM. I'm saying this is the cleanest way because you may have issues by unrooting and locking the phone. Maybe it would work. Unsure.
Click to expand...
Click to collapse
But you said that this would brick my device?
Mansil234 said:
But you said that this would brick my device?
Click to expand...
Click to collapse
He meant: If you have root acces with magisk first of all uninstall root and relock bootloader
Kineceleran said:
He meant: If you have root acces with magisk first of all uninstall root and relock bootloader
Click to expand...
Click to collapse
Ok, this was a misunderstanding
If you lock your bl at a modified system, you will get the message "your system got destroyed", I once had this. But I was lucky being able to unlock again... So no hardbrick... But doing all that leads to nothing. Btw. it's always useful to have an open bl... For example, if you mess up with a magik module and stuck @boot... Just ignore the stupid message of xiaomi!
Voodoojonny said:
If you lock your bl at a modified system, you will get the message "your system got destroyed", I once had this. But I was lucky being able to unlock again... So no hardbrick... But doing all that leads to nothing. Btw. it's always useful to have an open bl... For example, if you mess up with a magik module and stuck @boot... Just ignore the stupid message of xiaomi!
Click to expand...
Click to collapse
To prevent this, i want to remove the root access in the first place.
That i have a clean stock rom.
I tried it with no-data-loss method and it says, system is destroyed, i have it to unlock it.
With root, you can relock it, but it's useless.
Mansil234 said:
To prevent this, i want to remove the root access in the first place.
That i have a clean stock rom.
Click to expand...
Click to collapse
Backup up everything first
Download MiFlash and the correct ROM (not OTA version)
Then you can flash the Stock ROM which will remove everything
You can also choose to leave unlocked or lock the bootloader (re-lock is selected by default)
As this is a somewhat new device I wouldn't tick the option to save your data.
capajga said:
Backup up everything first
Download MiFlash and the correct ROM (not OTA version)
Then you can flash the Stock ROM which will remove everything
You can also choose to leave unlocked or lock the bootloader (re-lock is selected by default)
As this is a somewhat new device I wouldn't tick the option to save your data.
Click to expand...
Click to collapse
What is the correct rom if not the OTA-Version?
Mansil234 said:
What is the correct rom if not the OTA-Version?
Click to expand...
Click to collapse
Take a look at this thread:
https://forum.xda-developers.com/mi-a2-lite/how-to/ota-v9-6-4-0-odlmiff-t3823913
you can find pretty much all ota's and fastboot rom links.
All full ROMs end with .tgz extension
like this one:
http://bigota.d.miui.com/V9.6.4.0.O...0.ODLMIFF_20180724.0000.00_8.1_4afd3431a2.tgz
you have to extract it to be able to use it with MiFlash but I'm sure you'll find all the answers in the thread above
capajga said:
Take a look at this thread:
https://forum.xda-developers.com/mi-a2-lite/how-to/ota-v9-6-4-0-odlmiff-t3823913
you can find pretty much all ota's and fastboot rom links.
All full ROMs end with .tgz extension
like this one:
http://bigota.d.miui.com/V9.6.4.0.O...0.ODLMIFF_20180724.0000.00_8.1_4afd3431a2.tgz
you have to extract it to be able to use it with MiFlash but I'm sure you'll find all the answers in the thread above
Click to expand...
Click to collapse
Thanks! Everything went fine!
Mansil234 said:
Thanks! Everything went fine!
Click to expand...
Click to collapse
Glad to hear it :laugh: