Hello there,
About year ago I've done an update to 6.0 android. Battery was charged near full and everything seemed okey. But, after update I faced a bootloop. So I tried to flash stock firmware and... failed. Many times. I'm unable to boot into recovery mode. Factory mode also isnt working. So, I tried to unlock my bootloader and flash another image, but when I try to unlock, I get a: "Check allow oem unlock in developer options". Sadly, I cant boot to check this option Is there any way to unlock oem without running android? What can I do? :crying:
Jaszka said:
Hello there,
About year ago I've done an update to 6.0 android. Battery was charged near full and everything seemed okey. But, after update I faced a bootloop. So I tried to flash stock firmware and... failed. Many times. I'm unable to boot into recovery mode. Factory mode also isnt working. So, I tried to unlock my bootloader and flash another image, but when I try to unlock, I get a: "Check allow oem unlock in developer options". Sadly, I cant boot to check this option Is there any way to unlock oem without running android? What can I do? :crying:
Click to expand...
Click to collapse
You can flash the /persist partition from a device which has had OEM Unlock previously enabled in Developer Options.
MotoJunkie01 said:
You can flash the /persist partition from a device which has had OEM Unlock previously enabled in Developer Options.
Click to expand...
Click to collapse
How can you flash the /persist partition in a device with a locked bootloader? Doesn't this contain other information as well?
I think the real problem here is either the OP is not using the correct factory firmware image, or incorrect user procedure.
acejavelin said:
How can you flash the /persist partition in a device with a locked bootloader? Doesn't this contain other information as well?
I think the real problem here is either the OP is not using the correct factory firmware image, or incorrect user procedure.
Click to expand...
Click to collapse
You are probably correct. Even with a locked bootloader, certain partitions can be flashed as long as downgrading is not detected. Example, if I have an xt1548 Moto G3 running on stock 5.1.1 firmware, and I have a locked bootloader, I can flash either an updated 6.0.1 stock firmware package or I can reflash the 5.1.1 firmware with the same build as the one already installed. The bootloader will, however, prevent downgrading. In flashing the /persist partition, the .img being flashed would need to be from an equal or newer build as well.
But again, your statement regarding the correct firmware procedure and/or correct firmware package is likely correct.
MotoJunkie01 said:
You are probably correct. Even with a locked bootloader, certain partitions can be flashed as long as downgrading is not detected. Example, if I have an xt1548 Moto G3 running on stock 5.1.1 firmware, and I have a locked bootloader, I can flash either an updated 6.0.1 stock firmware package or I can reflash the 5.1.1 firmware with the same build as the one already installed. The bootloader will, however, prevent downgrading. In flashing the /persist partition, the .img being flashed would need to be from an equal or newer build as well.
But again, your statement regarding the correct firmware procedure and/or correct firmware package is likely correct.
Click to expand...
Click to collapse
You can't flash anything except a bootloader. I was in this situation as MotoJunkie knows and nothing works. I did have a full backup of every partition on the phone and none flashed. Today I bricked it so badly that it doesn't even turn on anymore. My tip is to not mess with the bootloader and stuff and just use the phone normally as many things are encrypted on this phone.
purplefruity said:
You can't flash anything except a bootloader. I was in this situation as MotoJunkie knows and nothing works. I did have a full backup of every partition on the phone and none flashed. Today I bricked it so badly that it doesn't even turn on anymore. My tip is to not mess with the bootloader and stuff and just use the phone normally as many things are encrypted on this phone.
Click to expand...
Click to collapse
Yes I recall your situation and your hard brick. I'm saying that under normal circumstances you can flash full firmware packages with a locked bootloader, as long as downgrading is not attempted.
MotoJunkie01 said:
Yes I recall your situation and your hard brick. I'm saying that under normal circumstances you can flash full firmware packages with a locked bootloader, as long as downgrading is not attempted.
Click to expand...
Click to collapse
You can't flash regular ones too. It has to be a newer firmware for the locked bootloader to let it pass
purplefruity said:
You can't flash regular ones too. It has to be a newer firmware for the locked bootloader to let it pass
Click to expand...
Click to collapse
That's what I was saying. An equal or newer one. Downgrading isn't permitted.
MotoJunkie01 said:
That's what I was saying. An equal or newer one. Downgrading isn't permitted.
Click to expand...
Click to collapse
Mine was on marshmallow and it wouldn't want to flash marshmallow stock so what I was saying is that you can't go anywhere unless stock nougat is released for this device.
purplefruity said:
Mine was on marshmallow and it wouldn't want to flash marshmallow stock so what I was saying is that you can't go anywhere unless stock nougat is released for this device.
Click to expand...
Click to collapse
You obviously developed corrupt partitions some way or another. I flash stock firmware packages with a locked bootloader on a regular basis. You should always be able to flash the same firmware build that is currently installed on your device.
MotoJunkie01 said:
You obviously developed corrupt partitions some way or another. I flash stock firmware packages with a locked bootloader on a regular basis. You should always be able to flash the same firmware build that is currently installed on your device.
Click to expand...
Click to collapse
O well I guess my device was different then. Won't turn on at all now . Gonna sell it for parts so at least I get some money back.
Related
hi, i really want to downgrade my S6 to lollipop but i have one of the latest bootloader (DPFX).
Downgrade was perfectly possible when i was on first build of marshmallow, but now, since i upgraded to DPFX bootloader, i have only fails with odin, and bootloops with custom roms...
is there any solution? if only i could flash an older bootloader, then i will be saved.
but if i flash an old bootloader with odin, i have a fail, so i don't know what to do
Some people suggested to me to use an old TWRP backup and i found it on my pc (with all partitions files: bootloader,system,radio and data, but i didn't use data) but using it, it's the same of flashing a custom rom: bootloop, and i suspect that the old bootloader never was flashed.
help
cescof said:
hi, i really want to downgrade my S6 to lollipop but i have one of the latest bootloader (DPFX).
Downgrade was perfectly possible when i was on first build of marshmallow, but now, since i upgraded to DPFX bootloader, i have only fails with odin, and bootloops with custom roms...
is there any solution? if only i could flash an older bootloader, then i will be saved.
but if i flash an old bootloader with odin, i have a fail, so i don't know what to do
Some people suggested to me to use an old TWRP backup and i found it on my pc (with all partitions files: bootloader,system,radio and data, but i didn't use data) but using it, it's the same of flashing a custom rom: bootloop, and i suspect that the old bootloader never was flashed.
help
Click to expand...
Click to collapse
If you are on a newer mm bootloader then downgrading to lollipop is not possible
sofir786 said:
If you are on a newer mm bootloader then downgrading to lollipop is not possible
Click to expand...
Click to collapse
I knew this, but i want to know if there is a way, a not official way, like reinstalling bootloader in a forced way that doesn't care about security problems... this thing has no sense.... why totally prevent to downgrade? However, i thing it's NORMALLY impossible, but not
TOTALLY impossible
cescof said:
I knew this, but i want to know if there is a way, a not official way, like reinstalling bootloader in a forced way that doesn't care about security problems... this thing has no sense.... why totally prevent to downgrade? However, i thing it's NORMALLY impossible, but not
TOTALLY impossible
Click to expand...
Click to collapse
As far as I know if you're on a newer bootloader official or not there is no current method to downgrade. Maybe a phone shop has specialist equipment to do this but that's me taking a shot in the air
I was able to downgrade but not because i wanted, i flashed a corrupt firmware with ODIN and i have to do an emergency recovery with Smart Switch, my carrier doesn't have Marshmallow on the S6 so my phone restored in Lollipop
hi guys i'm brasilian and my english is pretty poor but lets try. i was flash 4.4.4 rom br retail. and i update via ota for lollipop.. and brick .. i search in forums here ... and i go it to put in boot loader without robot.. already try many ways to recovery my boot loader but always get error remote failure.. and already used 6.0.1 stock .. maybe i need to files atualy for this? i'm very sad my maxx is dead .. someone give me light .. help me fix this ... thank you guys
Is your bootloader locked or unlocked?
ChazzMatt said:
Is your bootloader locked or unlocked?
Click to expand...
Click to collapse
unlocked
kenedi jr said:
unlocked
Click to expand...
Click to collapse
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
ChazzMatt said:
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
Click to expand...
Click to collapse
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
kenedi jr said:
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
Click to expand...
Click to collapse
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
So I'm stuck on the bootloader. If I connect charger or pc it will already pro boot loader without the robot. I have already tried to pass stock 4.4.4 and 6.0 and more etc always from the failure remote failure in bootloader appears in the log something with gt bin downgrade
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
kenedi jr said:
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
Click to expand...
Click to collapse
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
I do not have twrp backup and I can not even install the recovery stock
kenedi jr said:
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
Click to expand...
Click to collapse
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that version to repair. Just reflash the entire full firmware.
Click to expand...
Click to collapse
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
thanks bro you saved me
kenedi jr said:
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
Click to expand...
Click to collapse
You can not flash any older gpt.bin files. You have to omit (leave out) that flash command.
Your gpt.bin file is 6.0.1, and you cannot downgrade. Even on 4.4.4, trying to accept the 5.0.2 OTA update is still older gpt.bin file in that OTA than your 6.0.1.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
i don't have link .. i will wanting you so
kenedi jr said:
i don't have link .. i will wanting you so
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?p=72846593
ChazzMatt said:
https://forum.xda-developers.com/showthread.php?p=72846593
Click to expand...
Click to collapse
I was a bit confused with this link which is the last one? I discovered because I am Brazilian and my English was developed only by playing
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
ChazzMatt said:
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
Click to expand...
Click to collapse
Face first you're a myth. I just passed gpt.bin and got the bootloader ... I'm very happy. Do I need to pass the entire rom ??
:good::laugh:
Hello!
I want to make my phone completely stock again. (Or as close as possible if completely stock isn't possible)
I unlocked, installed TWRP, and then rooted my phone yesterday (thanks to shashank1320's guide which made it very simple), but quickly found out that safetynet will prevent me from downloading and playing certain games on the Google Play Store.
After poking around online, it seems that even switching over to Magisk instead of using SuperSU will leave intermittent gaps in time where the app will be inaccessible due to the new workaround eventually being blocked.
So I want to go back. But like a derp, I forgot to create a backup beforehand.
So far I've unrooted through the SuperSU app itself, and flashed the BOOT.img and RECOVERY.img from Dazed No More's links in the Honor 6x Repository here.
After this is where I'm not sure what to do.
I think I need to find a factory system image to flash (and the vendor.img)?
I've seen a few threads saying that putting the UPDATE.APP in a dload folder into the phone and have the phone run the update worked (This did not work for me, although I'm not sure I have the right files; I downloaded it through a tech guide site here). I extracted the system.img and vendor.img from the update.app off that website using the Huawei Update Extractor, but I am afraid of flashing them in case they are the incorrect ones. But what if they are correct? Would I be able to recover if they are not?
Also, should I download and use unSU?
I know there is this guide on the front page right now. I've downloaded the Huawei Firmware Finder, but I... don't know how to use it. I narrow it down to the model number and that is where I get stuck. How... do I use it?
Some other basic questions I have in addition to this are:
Would I just have to flash the system.img and vendor.img through adb and then it will be stock again?
Would there still be leftover SuperSU files in my phone? I want to remove every trace of it. Would flashing be enough?
Am I even on the right track? And if not, where should I go from here?
Is the term "ROM" here firmware? Are the two terms interchangeable?
Ultimately, I would want to flash stock and then lock the bootloader again.
Thank you very much in advance. I appreciate it.
Edit: Wow I forgot to put any information, sorry about that.
Honor 6x
Model Number: BLN-L24
Build Number: BLN-L24C567B360
EMUI version: 5.0
Android version: 7.0
If you have unrooted, foashed stock boot and stock recovery rhen you are stock completely. For safer side, you can just dload the current firmware whch will lock your bootloader also and remove those device unlocked and cant be trusted message on boot.
shashank1320 said:
If you have unrooted, foashed stock boot and stock recovery rhen you are stock completely. For safer side, you can just dload the current firmware whch will lock your bootloader also and remove those device unlocked and cant be trusted message on boot.
Click to expand...
Click to collapse
Thank you! Currently it's still tripping safetynet, but that may just be due to the phone still being unlocked.
Would it be fine to just lock the bootloader through adb now?
And are all traces of SuperSU gone like this?
Faifie said:
Thank you! Currently it's still tripping safetynet, but that may just be due to the phone still being unlocked.
Would it be fine to just lock the bootloader through adb now?
And are all traces of SuperSU gone like this?
Click to expand...
Click to collapse
Nope. Locking the bootloader will just do it and reset but wont change the boot.img which root modified.
You need to unroot, flash stock recovery and stock boot.img to get rid of it.
shashank1320 said:
Nope. Locking the bootloader will just do it and reset but wont change the boot.img which root modified.
You need to unroot, flash stock recovery and stock boot.img to get rid of it.
Click to expand...
Click to collapse
Okay, since those have been flashed with stock, that means I'm set to re-lock the phone! Will get around to it sometime tomorrow c:
Thank you so, so much ^^
So I first bought my Samsung a11 as an android 10 model,
I then flashed it after I bought it with an open-line android 11 version and got twrp and root. This was a year ago I think.
Now they released the final update for this Samsung phone model, and I want to at least get the latest and last version of my phone.
But I kinda forgot how to do the procedures again.
So my question is does flashing the new android version firmware using odin remove TWRP installed on my device?
my phone model is: A115FXXU2BUJ2 (android 11)
the firmware I want to install: A115FXXU3CV13 (android 12)
if so what do I need to do in order to successfully have both the new firmware I want to install and twrp installed on my device? (i kinda know how to root using twrp and magisk so no problems here)
Any help would be much appreciated!
????.?? said:
So I first bought my Samsung a11 as an android 10 model,
I then flashed it after I bought it with an open-line android 11 version and got twrp and root. This was a year ago I think.
Now they released the final update for this Samsung phone model, and I want to at least get the latest and last version of my phone.
But I kinda forgot how to do the procedures again.
So my question is does flashing the new android version firmware using odin remove TWRP installed on my device?
my phone model is: A115FXXU2BUJ2 (android 11)
the firmware I want to install: A115FXXU3CV13 (android 12)
if so what do I need to do in order to successfully have both the new firmware I want to install and twrp installed on my device? (i kinda know how to root using twrp and magisk so no problems here)
Any help would be much appreciated!
Click to expand...
Click to collapse
Yes, flashing the update via Odin will remove TWRP and root, it will also, more than likely, lock your bootloader, then you won't be able to reinstall TWRP or root the device unless you unlock the bootloader, if it can be unlocked.
Droidriven said:
Yes, flashing the update via Odin will remove TWRP and root, it will also, more than likely, lock your bootloader, then you won't be able to reinstall TWRP or root the device unless you unlock the bootloader, if it can be unlocked.
Click to expand...
Click to collapse
My phone's bootloader is already unlocked, after flashing the updated android version firmware will the bootloader become lock again? and how do i avoid rmm and frp lock?(just incase this happens)
????.?? said:
My phone's bootloader is already unlocked, after flashing the updated android version firmware will the bootloader become lock again? and how do i avoid rmm and frp lock?(just incase this happens)
Click to expand...
Click to collapse
If the bootloader in the update is a securely locked bootloader, it will probably have locked bootloader after flashing and might not be able to be unlocked. That was the whole point of me warning you in my last post. Now I've had to post again just to say the same thing that I already said. I guess I was talking to the wind.
There is no way to know what the results will be after updating unless you find someone that has already updated the exact same model number of A11 or bite the bullet and update yours then see what you get.
Droidriven said:
If the bootloader in the update is a securely locked bootloader, it will probably have locked bootloader after flashing and might not be able to be unlocked. That was the whole point of me warning you in my last post. Now I've had to post again just to say the same thing that I already said. I guess I was talking to the wind.
There is no way to know what the results will be after updating unless you find someone that has already updated the exact same model number of A11 or bite the bullet and update yours then see what you get.
Click to expand...
Click to collapse
I see, looks like i need to find someone who have done it and see if it works. I didnt get what you mean about after flashing, it might have a chance to lock the bootloader depends on the update. I think ill just try and see what happens. Thank you.
I dont know guys with that phone but there should be a tool that bypass auth and unlock the bootloader in any case. I ONLY knows MTK devices, not sure about that samsung i use a .Bat file.
????.?? said:
I see, looks like i need to find someone who have done it and see if it works. I didnt get what you mean about after flashing, it might have a chance to lock the bootloader depends on the update. I think ill just try and see what happens. Thank you.
Click to expand...
Click to collapse
No, I said that after the update, it could cause the bootloader to be locked and then may not be unlockable from that point on. It depends on the bootloader in the update. If this happens, you will be unable to install TWRP or root via Magisk. That is why you need to confirm whether or not flashing the update will relock the bootloader during the flashing process and, if it does, whether or not it can be unlocked again after the update.
In other words, look at exactly what you are about to jump into before you make the jump because you might land in the one place that you absolutely do not want to land.
I want to relock bootloader, but will I get brick if I lock bootloader with old stock ROM installed on device?
Look inside here:
Lock BootLoader after Rooting?
Thanks for taking time to read my query. I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero) and before looking can I take everything backup on titanium backup and then restore everything after locking ? I'm I...
forum.xda-developers.com
jwoegerbauer said:
Look inside here:
Lock BootLoader after Rooting?
Thanks for taking time to read my query. I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero) and before looking can I take everything backup on titanium backup and then restore everything after locking ? I'm I...
forum.xda-developers.com
Click to expand...
Click to collapse
I know that if I install modified ROM and lock bootloader I will get a brick. But will I get a brick if i install official (stock) ROM but old version and then lock bootloader? For example, I installed stock ROM (not modified) with Android 10, but the latest is Android 11 then I locked bootloader. Will I get a brick?
jwoegerbauer said:
Look inside here:
Lock BootLoader after Rooting?
Thanks for taking time to read my query. I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero) and before looking can I take everything backup on titanium backup and then restore everything after locking ? I'm I...
forum.xda-developers.com
Click to expand...
Click to collapse
The question is, can I lock the bootloader with the old version of the official firmware installed without getting a brick. Because the old version of the firmware works smoother.
Locking a bootloader doesn't affect ROM actually installed: Lock or Unlock will wipe your data, that's all.
jwoegerbauer said:
Locking a bootloader doesn't affect ROM actually installed: Lock or Unlock will wipe your data, that's all.
Click to expand...
Click to collapse
So can I install old version of fw? I heard something about rollback protection.
Oybek78 said:
So can I install old version of fw? I heard something about rollback protection.
Click to expand...
Click to collapse
You still, or I didn´t find, that you mention the model of your device, that´s matter to have the right answer.
Also, it depends on which method you used to flash the ROM, if you officially, flashed the ROM, and the rollback didn´t affect your device, then it won´t do, locking or unlocking it.
Oybek78 said:
So can I install old version of fw? I heard something about rollback protection.
Click to expand...
Click to collapse
The stock ROM can be installed on the phone at any time. Mostly via ADB / Fastboot tools.
SubwayChamp said:
You still, or I didn´t find, that you mention the model of your device, that´s matter to have the right answer.
Also, it depends on which method you used to flash the ROM, if you officially, flashed the ROM, and the rollback didn´t affect your device, then it won´t do, locking or unlocking it.
Click to expand...
Click to collapse
My phone is Sony Xperia 1 J9110. I flashed it officially to the latest ROM through settings. Then I unlocked the bootloader and flashed the old stock ROM via newflasher. Then I decided to relock the bootloader with old stock ROM installed. Does this mean that I will get my phone bricked if I lock the bootloader with old stock ROM actually installed?
jwoegerbauer said:
The stock ROM can be installed on the phone at any time. Mostly via ADB / Fastboot tools.
Click to expand...
Click to collapse
But can I lock the bootloader with old stock ROM installed?
I saw somewhere that if you lock the bootloader with the old firmware version, you may get brick. But I'm not sure about that.
Why steadily repeat your posts?
FYI: I hereby opt out of this thread.
jwoegerbauer said:
Why steadily repeat your posts?
FYI: I hereby opt out of this thread.
Click to expand...
Click to collapse
Because you answered me
Oybek78 said:
My phone is Sony Xperia 1 J9110. I flashed it officially to the latest ROM through settings. Then I unlocked the bootloader and flashed the old stock ROM via newflasher. Then I decided to relock the bootloader with old stock ROM installed. Does this mean that I will get my phone bricked if I lock the bootloader with old stock ROM actually installed?
Click to expand...
Click to collapse
Yes, always that you flash a stock ROM, you can re-lock it, fastboot will erase the data as a security measurement.