Hello!
i have got a Problem...
my usb c port is broken. the only thing that is working is loading the battery.
i can factory reset the smartphone for return to google, but my problem is the bootloader. any ideas, how i can relock the bootloader withput using my computer? ?
thank you!
Blooddrunked said:
Hello!
i have got a Problem...
my usb c port is broken. the only thing that is working is loading the battery.
i can factory reset the smartphone for return to google, but my problem is the bootloader. any ideas, how i can relock the bootloader withput using my computer?
thank you!
Click to expand...
Click to collapse
if you're returning it to Google they don't really care if it's locked or not. I've sent them back for an RMA both ways never had any problems
Agree, relocking shouldn't be needed for a RMA...
Just make sure your device is completely stock at the very least.
Personally, I'd flash the factory images to both slots and lock the bootloader. However, if others have suggested they don't have any issues sending it back with the bootloader unlocked, then just flash the factory images.
Although, it is just one command to lock it (just be absolutely sure you're completely stock before locking, if you go that route).
thank you All! but i need to get the stock recovery... how can i install the Stock recovery without an pc and without twrp? because i have the twrp edition with the encryption problem on Android pie... ??
Blooddrunked said:
thank you All! but i need to get the stock recovery... how can i install the Stock recovery without an pc and without twrp? because i have the twrp edition with the encryption problem on Android pie... ?
Click to expand...
Click to collapse
You can't, and don't worry about it.
Blooddrunked said:
thank you All! but i need to get the stock recovery... how can i install the Stock recovery without an pc and without twrp? because i have the twrp edition with the encryption problem on Android pie... ??
Click to expand...
Click to collapse
You could download the OTA zip and move it to your data folder with a root explorer type app, then flash it with twrp. Will twrp not decrypt without screen lock security?
Badger50 said:
You could download the OTA zip and move it to your data folder with a root explorer type app, then flash it with twrp. Will twrp not decrypt without screen lock security?
Click to expand...
Click to collapse
Thank you! it worked!
Blooddrunked said:
Thank you! it worked!
Click to expand...
Click to collapse
Well there ya go! Your welcome. :good::good:
how long does it take to get the replacement from google??
That's exactly why I never unlock the bootloader, root, install custom ROMs, etc. I don't want to be in the situation where I can't use my warranty or insurance.
kismetmookz said:
how long does it take to get the replacement from google??
Click to expand...
Click to collapse
My bootloader was unlocked and it was not an issue. I sent my phone back and got a new phone in 6 days. I guess it would also depend on where you live. I live on the east coast and sent my phone to Texas and they sent me a new one from Illinois.
Related
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
Hi guys, my nexus 5x is locked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
MaxOptim said:
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
Click to expand...
Click to collapse
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
ybregeon2016 said:
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
Click to expand...
Click to collapse
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
MaxOptim said:
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
Click to expand...
Click to collapse
Forgive my ignorance but how can I do this?
ybregeon2016 said:
Forgive my ignorance but how can I do this?
Click to expand...
Click to collapse
follow instructions here: https://developers.google.com/android/ota
MaxOptim said:
follow instructions here: https://developers.google.com/android/ota
Click to expand...
Click to collapse
Actually I was talking about the RMA, I bought it in Egypt.
ybregeon2016 said:
Actually I was talking about the RMA, I bought it in Egypt.
Click to expand...
Click to collapse
ah, no idea then, sorry.
ybregeon2016 said:
Hi guys, my nexus 5x is unlocked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
Click to expand...
Click to collapse
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
dominoeflux said:
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Click to expand...
Click to collapse
Man i remind you that my bootloader is locked and for this reason can't start twrp.
ybregeon2016 said:
Man i remind you that my bootloader is locked and for this reason can't start twrp.
Click to expand...
Click to collapse
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
dominoeflux said:
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
Click to expand...
Click to collapse
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
ybregeon2016 said:
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
Click to expand...
Click to collapse
Oohhh OK I got you...have you been able to look in doing a tot recovery with Odin? I'm almost home so I'll see what I can do to help u out
Edit: have u tried unlocking it again in bootloader?
LGUP install a firmware as a TOT, it was a TOT file. Isnt Odin for Samsung phones?
tauio111 said:
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
Click to expand...
Click to collapse
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
ybregeon2016 said:
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
Click to expand...
Click to collapse
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
tauio111 said:
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
Click to expand...
Click to collapse
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
ybregeon2016 said:
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
Click to expand...
Click to collapse
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
tauio111 said:
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
Click to expand...
Click to collapse
Failed (remote: OEM unlock is not allowed)
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.
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:
I see that TWRP users have experienced a touchscreen issue, so they need to use an OTG cable with wireless mouse. Does anyone know when will the touch issue be fixed?
NickDeveloper said:
I see that TWRP users have experienced a touchscreen issue, so they need to use an OTG cable with wireless mouse. Does anyone know when will the touch issue be fixed?
Click to expand...
Click to collapse
So, we don't know when will be fixed
NickDeveloper said:
I see that TWRP users have experienced a touchscreen issue, so they need to use an OTG cable with wireless mouse. Does anyone know when will the touch issue be fixed?
Click to expand...
Click to collapse
But you can use the OTG touch twrp
Arobase40 said:
I experimented this no touch TWRP but it is mostly buggy excluding the non touch issue there is a bigger issue which is that once installed you can't get out from it as it bootloops into this recovery mode. Flashing a stock recovery won't change anything.
You will have to totally restock your phone from scratch and then re root it and restore all your apps and data !!! ^^
I found out the twrp tree for A52 4G and was able to build a TWRP but obviously I can't test it.
I'm not able to build a twrp for A52S 5G for now as there are missing many kernel modules and other stuffs so I have to build them from kernel source code. So for now I'm working on the device and vendor config files...
Click to expand...
Click to collapse
But how can I fix my phone if I get a bootloop?
Arobase40 said:
You can't that is why I don't recommend you to use this no touch TWRP !
I was told to use a multidisabler but doesn't seem to work...
Click to expand...
Click to collapse
But it is only a soft brick, there is no need to change the motherboard. Would there be a way to reinstall stock firmware with Odin?
Arobase40 said:
I didn't say it will break your motherboard but if you want to waste your time in restocking your phone it's up to you.
Click to expand...
Click to collapse
Can I reinstall stock firmware with Odin? Will it work?
NickDeveloper said:
Can I reinstall stock firmware with Odin? Will it work?
Click to expand...
Click to collapse
Yes.
Arobase40 said:
As I said if you want to waste your time, YES you can reinstall stock firmware but of course you will lose your no touch twrp...
You will have to choose one or the other but not both...
Click to expand...
Click to collapse
Unfortunately, I have tried to reinstall stock firmware, but it failed. Looks like my bootloader became locked. Odin software showed "FAIL". There was a message that I could barely read, so that was the reason it failed to reinstall the firmware.
What should I do now?
Arobase40 said:
You can't that is why I don't recommend you to use this no touch TWRP !
I was told to use a multidisabler but doesn't seem to work...
Click to expand...
Click to collapse
So you got stuck in a bootloop after installing twrp. Have you tried just extracting the stock boot.img from firmware AP file and flashing it with odin? I really don't get it why you had to reinstall everything to stock. It's not necessary to reflash every partition if you only messed up one
Arm1nas said:
So you got stuck in a bootloop after installing twrp. Have you tried just extracting the stock boot.img from firmware AP file and flashing it with odin? I really don't get it why you had to reinstall everything to stock. It's not necessary to reflash every partition if you only messed up one
Click to expand...
Click to collapse
Nope, I did not make the backup of anything. Unfortunately, my bootloader is now locked and I cannot reinstall stock firmware. What now??
NickDeveloper said:
Nope, I did not make the backup of anything. Unfortunately, my bootloader is now locked and I cannot reinstall stock firmware. What now??
Click to expand...
Click to collapse
While the phone is completely off, press vol up and vol down buttons at the same time and then plug in the usb cable to the computer. I had that happen too, when the device fails to boot it automatically puts you into download mode and it says that the OEM LOCK is on. You just have to reboot to download mode manually.
Arm1nas said:
While the phone is completely off, press vol up and vol down buttons at the same time and then plug in the usb cable to the computer. I had that happen too, when the device fails to boot it automatically puts you into download mode and it says that the OEM LOCK is on. You just have to reboot to download mode manually.
Click to expand...
Click to collapse
But how can I reinstall stock firmware when the OEM is locked? I tried to reinstall with all required binaries, including HOME_CSC and it showed "FAIL".
NickDeveloper said:
But how can I reinstall stock firmware when the OEM is locked? I tried to reinstall with all required binaries, including HOME_CSC and it showed "FAIL".
Click to expand...
Click to collapse
You don't need to unlock bootloader to flash stock fw with Odin.
Your problem is most likely related to something else.
Where did you download your fw?
Have you tried different cables?
What Odin version are you trying?
ShaDisNX255 said:
You don't need to unlock bootloader to flash stock fw with Odin.
Your problem is most likely related to something else.
Where did you download your fw?
Have you tried different cables?
What Odin version are you trying?
Click to expand...
Click to collapse
I don't understand why would it be possible to flash stock firmware with locked bootloader, I thought that locked bootloader won't allow the OS to be reinstalled.
NickDeveloper said:
I don't understand why would it be possible to flash stock firmware with locked bootloader, I thought that locked bootloader won't allow the OS to be reinstalled.
Click to expand...
Click to collapse
A Locked bootloader will prevent you from installing any custom things, like recovery or custom roms. It will allow you to install stock firmware via odin. Use Odin 3.14 to install firmware downloaded from here. Use the AP, Bl, Cp, and CSC_OXM files. That will get you started from scratch, all previous data and stuff will be deleted.