Related
Hello
I did accidentally have a power failure on my computer when flashing version 4.0.4 to my Galaxy Nexus and the phone keeps booting on recovery menu automatically.
I have tried to flash different version using fastboot and Odin but always get an error saying my bootloader is locked use "fastboot oem unlock"
When try to unlock using the command the phone displays a selection screen asking to unlock the bootloader YES/NO, If I select YES the fastboot line returns the following error FAILED (remote: Unknown Partition) and the bootloader keep locked.
I have tried a thousand times without success and I am not able to utilize any firmware because is not permitted until I manage to get the bootloader finally Unlocked.
Pls help
Thanks
How about you
a) Flash an official rom via stock recovery and try it then
b) Ask this question in the Questions and Answers section instead of the Development section because I don't see any development relevant information in this post...
gevenerof said:
Hello
I did accidentally have a power failure on my computer when flashing version 4.0.4 to my Galaxy Nexus and the phone keeps booting on recovery menu automatically.
I have tried to flash different version using fastboot and Odin but always get an error saying my bootloader is locked use "fastboot oem unlock"
When try to unlock using the command the phone displays a selection screen asking to unlock the bootloader YES/NO, If I select YES the fastboot line returns the following error FAILED (remote: Unknown Partition) and the bootloader keep locked.
I have tried a thousand times without success and I am not able to utilize any firmware because is not permitted until I manage to get the bootloader finally Unlocked.
Pls help
Thanks
Click to expand...
Click to collapse
Try using the Gnex Toolkit posted on the development page as a sticky.
since u can't use fastboot (and the toolkit is useless in this case), i think u should try odin
THIS IS NOT DEVELOPMENT
Do not post question threads here
Read forum rules before posting threads
Thread moved
FNM
First of all, use ANY toolkit (Mine's in the description ^^)
Then unlock your bootloader (Open cmdthe type:
Code:
fastboot oem unlock
You'll need ADB/fastboot drivers installed, though...)
There's no point using a toolkit, how it sounds to me is you somehow messed up a partition when flashing the update.
As someone already said try flashing an ota update through the stock recovery (if you have stock recovery)
It was probably the bootloader that got messed up when your power went.
Try flash a new bootloader too, see how that goes.
Fastboot flash bootloader filename.img
I am having the exact same issue. Trying to flash, format or dare i even say erase won't do anything to the bootloader, trying to access recovery on mine it says failed, trying to unlock the bootloader through oem unlock, prompts the failed : remote unknown error code. :S
use the galaxy nexus toolkit to unlock bootloader, root
Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.
Petrovski80 said:
Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.
Click to expand...
Click to collapse
Thats true, every tool kit i have tried has failed, even fastboot commands, at least the latter tell you that it fails. Where can i download the bootunlocker app? Does my Nexus 7 have to boot into the rom to do this? Because mine can't. :S
Petrovski80 said:
Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.
Click to expand...
Click to collapse
Incorrect.
Signed images will flash correctly with a locked bootloader.
Jubakuba said:
Incorrect.
Signed images will flash correctly with a locked bootloader.
Click to expand...
Click to collapse
Would you be kind to help me with the instructions and the signed image for nexus 7 needed to be flashed over a locked bootloader? I would greatly appreciate it
AndiS21 said:
Would you be kind to help me with the instructions and the signed image for nexus 7 needed to be flashed over a locked bootloader? I would greatly appreciate it
Click to expand...
Click to collapse
Ask Google or Samsung, they have the keys to sign it. Also, this is the galaxy nexus forums.
Sent from my i9250
OP, OMAP flash?
Hi all,
I recently picked up a new Pixel and was wanting to flash it. I ended up enabling USB debugging and set OEM unlock within Android settings.
Yet when I use fastboot flashing unlock, it keeps telling me that OEM unlock isn't set. In my haste, I ran flash-all with a new Google build and this overwrote the existing ROM, but left the bootloader intact it seems. Now when I boot, it says I have a damaged OS and I should use recovery. The problem is that even recovery is damaged and it keeps rebooting to the bootloader. So adb won't work either. The only thing that works is fastboot.
Is there anything I can do to fix this or is it completely bricked? I can't seem to use fastboot to flash any ROM to the device - keeps erroring. I tried to match a ROM with the bootloader but that didn't work either.
Any ideas?
I used Nexus Root Toolkit when I got semi-bricked.
Use erase Command on flashboot for data and system then do flash_all again
As was mentioned, if you have fastboot you are ok. You can flash as mentioned above or use this -
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
NRT is good for people like me who barely know what they're doing, enough to get bricked in the first place like I did. What i like is that it takes away a little of the uncertainty about whether I'm using the right files.
I hadn't rooted and unlocked and done all the setup in about a year so I forgot everything.
Save yourself some trouble and look at the "TWRP bootloops" thread. It's easy to avoid if you follow some specific steps, frustrating otherwise.
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
d j a said:
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
Click to expand...
Click to collapse
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
cam30era said:
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
Click to expand...
Click to collapse
Yeah didn't think NRT would work because of the locked bootloader! Fastboot continue just gets out of fastboot - what is that gonna solve? I have a damaged set of partitions it seems - going from bootloader -> recovery boots back to the bootloader so it's clear that partition is damaged.
Is there any way I can just push some build to rebuild the partitions or can I do absolutely nothing until the bootloader is unlocked. And if so, how on earth can i unlock it if the only thing that works is fastboot?
hamazoza said:
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
Click to expand...
Click to collapse
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
I'll try that tonight. FWIW, I know I copied the line from flash-all to just flash recovery.img and even the system image, and both failed.
The only difference I see between that and yours is you have '-w update'. Maybe that's the trick.
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
hamazoza said:
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
Click to expand...
Click to collapse
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
d j a said:
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
Click to expand...
Click to collapse
I don't think that'll work. OEM unlock wasn't set in developer settings.
hamazoza said:
I don't think that'll work. OEM unlock wasn't set in developer settings.
Click to expand...
Click to collapse
You don't need that. I actually unlocked mine without it. The tool also has a unlock feature. Its worth a try.
Look for this forum post: flashing to stock android npd90g twrp t3424863
This helped me too. Only difference is I had TWRP installed.
Try unlocking bootloader via termjnal, then use the fastboot command via terminal (pc) fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable fastboot, then erase the partitions manually as mentioned in the tutorial and reflash them either manually or together using skipsoft / nrt or manual commands and a factory image.
Normally there should not be anything wrong with your bootloader image since modifying it is disabled for bootloader locked devices. Let us know about your progress.
Oh, also never flash an older system image than your current one.
Hi friends
Please give me suggestion or guide how to solve problem about handset booting after mistakenly handset OEM locked through fastboot
It enter to fastboot mode but not going to recovery mode or restart in system mode
Is there any solution
If yes then please help me
fastboot oem unlock ?
Actually ive unlocked OEM and install twrp recovery and installed freedom os
Then while checking OEM status ive enter command fastboot OEM lock
It ask me I've pressed yes after that the massage is came after restart as your device is corrupt it can't be trusted and will not boot
After that it enter to fastboot but not going to recovery mode or system
While type command in fastboot OEM unlock massege come failed
This happens because your bootloader has been unlocked at one time. There is no going back, even if you use "fastboot oem lock" later.
Edit: Just noticed the part about your device will not boot. You need to find the system image and flash it. I read somewhere today that OnePlus just released the system image for 4.7.4.
Can you unlock again?
@op, IMHO the best possible solution will be to flash stock rom image and stock recovery if required but I think when you flash stock image it will also flash stock recovery.
When you turn off the phone and boot it with VOLUME UP plus POWER, this should send you straight away to Fastboot. Try if you can unlock again, otherwise... bad luck - you'll need a restore session with 1+.
the Doctor said:
This happens because your bootloader has been unlocked at one time. There is no going back, even if you use "fastboot oem lock" later.
Click to expand...
Click to collapse
Not to be unrespectful, but you're wrong, it is absolutely possible to relock bootloader without problems.
IMHO, trouble happened because he had a custom rom onboard... and a locked bootloader does exactly its purpose... to not boot insecure firmware!
jonsat said:
Not to be unrespectful, but you're wrong, it is absolutely possible to relock bootloader without problems.
IMHO, trouble happened because he had a custom rom onboard... and a locked bootloader does exactly its purpose... to not boot insecure firmware!
Click to expand...
Click to collapse
After looking into it further, I agree with you. That's what I get for having a bootloader-locked Samsung device for two years. I must be getting rusty!
Yes, the bootloader can be re-locked. There may still be a tamper flag as with previous OnePlus devices. But having a locked bootloader with non-OEM software would likely cause the problem he is describing. So, he needs to flash the factory image from bootloader.
I've requested to 1+support for restore remote session
Support send me file link and l2 will assist me in within 2 days
DO NOT RELOCK BOOTLOADER UNLESS U READ UP FIRST!!!!!, its worth just waiting the few seconds after reboot, then to go and try to relock the bootloader
I've restored oneplus 5t through remote session
it become as company new mobile
After that OEM also unlock
Thanks oneplus supports.
kaihansen2001 said:
Can you unlock again?
Click to expand...
Click to collapse
Yes ive unlock Bootloader
Rdxsammm said:
I've restored oneplus 5t through remote session
it become as company new mobile
After that OEM also unlock
Thanks oneplus supports.
Click to expand...
Click to collapse
How did you do it? can you guide me too?
sam razzy said:
How did you do it? can you guide me too?
Click to expand...
Click to collapse
Have you dumpling files and MSM download tools for oneplus 5t
If you have then restore op5t after success it work as new mobile.
But you can get basic dumpling file from oneplus support remote session.
You have to create ticket and chat with oneplus support
oneplus 5 device corrupt and it cant be trusted and will not bootr
hrushi0130 said:
oneplus 5 device corrupt and it cant be trusted and will not bootr
Click to expand...
Click to collapse
Did you by any chance re-lock the bootloader with a custom recovery and custom ROM flashed?
It's because of custom recovery.
Just flash stock recovery image before locking the bootloader.
This fixed for me.
Rdxsammm said:
Actually ive unlocked OEM and install twrp recovery and installed freedom os
Then while checking OEM status ive enter command fastboot OEM lock
It ask me I've pressed yes after that the massage is came after restart as your device is corrupt it can't be trusted and will not boot
After that it enter to fastboot but not going to recovery mode or system
While type command in fastboot OEM unlock massege come failed
Click to expand...
Click to collapse
You unlocked bootloader, flashed rom (custom) and relocked bootloader? Never lock your bootloader on a custom rom! Just enter fastboot again flash twrp (manual/force reboot recovery), copy internal storage to pc then wipe/format everything. Format data. Factory reset then flash latest official rom and reboot
Hi there ,
i unlocked the boot loader and installed twrp and rooted my pixel 3xl and every thing was fine
until i wanted to install the new update for Feb under this link https://dl.google.com/dl/android/aosp/crosshatch-ota-pq2a.190205.001-4225fb81.zip
so i flashed the update over twrp and it gave me an error then i treid with flashify same thing .
when i couldn't install the new update i wanted to lock the boot loader again and i locked it by typing fastboot flashing lock
and of course the device did't boot up, so i unlocked the boot loader again and then entered to twrp and i wiped every thing 'including the operation system i think'
so now i can just lock and unlock the boot loader and i can't install the twrp again
when i try that this error pop up
fastboot boot twrp-3.2.3-3-crosshatch.img
Downloading 'boot.img' OKAY [ 1.493s]
booting FAILED (remote: 'Error calling AvbLoadAndVerifyBootImages Load Error')
Finished. Total time: 1.606s
i'm using the last version of the fastboot > platform-tools_r28.0.1-windows and 've an original cable i used it befor for the unlock the boot loader and installing the twrp
so now what please , how can i to install a new Rom for the my pixel , and there is no operation system i think cause i deleted every thing including the system throw twrp !
thank you in advance
Bashar Bachir said:
Hi there ,
i unlocked the boot loader and installed twrp and rooted my pixel 3xl and every thing was fine
until i wanted to install the new update for Feb under this link https://dl.google.com/dl/android/aosp/crosshatch-ota-pq2a.190205.001-4225fb81.zip
so i flashed the update over twrp and it gave me an error then i treid with flashify same thing .
when i couldn't install the new update i wanted to lock the boot loader again and i locked it by typing fastboot flashing lock
and of course the device did't boot up, so i unlocked the boot loader again and then entered to twrp and i wiped every thing 'including the operation system i think'
so now i can just lock and unlock the boot loader and i can't install the twrp again
when i try that this error pop up
fastboot boot twrp-3.2.3-3-crosshatch.img
Downloading 'boot.img' OKAY [ 1.493s]
booting FAILED (remote: 'Error calling AvbLoadAndVerifyBootImages Load Error')
Finished. Total time: 1.606s
i'm using the last version of the fastboot > platform-tools_r28.0.1-windows and 've an original cable i used it befor for the unlock the boot loader and installing the twrp
so now what please , how can i to install a new Rom for the my pixel , and there is no operation system i think cause i deleted every thing including the system throw twrp !
thank you in advance
Click to expand...
Click to collapse
I would not keep locking/unlocking the bootloader unless you want to brick your phone.
If you can get to the bootloader, flash-all the latest factory image #4 'Keep data' in this guide: [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by homeboy76
Then look at #11 in the guide.
Homeboy76 said:
I would not keep locking/unlocking the bootloader unless you want to brick your phone.
If you can get to the bootloader, flash-all the latest factory image #4 'Keep data' in this guide: [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by homeboy76
Then look at #11 in the guide.
Click to expand...
Click to collapse
thanks a lot for your reply , yes i can get to the bootloader
i'm downloading now the factory image .thanks again
Bashar Bachir said:
thanks a lot for your reply , yes i can get to the bootloader
but there is no flash-all.bat inside platform-tools folder, from where can i get it please
Click to expand...
Click to collapse
- There is also no 'fastboot' nor 'adb' in your Platform-tools folder.
First, download the latest SDK Platform-tools r28.0.1 from here.
Then read #4 again, pay particular attention to #4B.
Homeboy76 said:
I would not keep locking/unlocking the bootloader unless you want to brick your phone.
If you can get to the bootloader, flash-all the latest factory image #4 'Keep data' in this guide: [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by homeboy76
Then look at #11 in the guide.
Click to expand...
Click to collapse
thanks a lot for your help , i installed the Factory image and unlocked the boot loader then the i could flash the rom finally ,
best regards
Stop locking your bootloader.
Homeboy76 said:
- There is also no 'fastboot' nor 'adb' in your Platform-tools folder.
First, download the latest SDK Platform-tools r28.0.1 from here.
Then read #4 again, pay particular attention to #4B.
Click to expand...
Click to collapse
thanks a lot for your help , the problem has been solved.
i hope all the best for you
best regards
TonikJDK said:
Stop locking your bootloader.
Click to expand...
Click to collapse
thanks a lot for you reply, maybe you mean Stop unlocking
cause the boot loader as you know is by default locked .so i returned it as it was .
thanks again
best regards
Bashar Bachir said:
thanks a lot for you reply, maybe you mean Stop unlocking
cause the boot loader as you know is by default locked .so i returned it as it was .
thanks again
best regards
Click to expand...
Click to collapse
From your first post:
"when i couldn't install the new update i wanted to lock the boot loader again and i locked it by typing fastboot flashing lock and of course the device did't boot up"
You got lucky, you locked it and it bricked. When that happens and you are locked you can often end up on a situation where you can't unlock again.
So I said what I meant, stop locking your bootloader unless you are 100 percent stock and working perfectly.
TonikJDK said:
From your first post:
"when i couldn't install the new update i wanted to lock the boot loader again and i locked it by typing fastboot flashing lock and of course the device did't boot up"
You got lucky, you locked it and it bricked. When that happens and you are locked you can often end up on a situation where you can't unlock again.
So I said what I meant, stop locking your bootloader unless you are 100 percent stock and working perfectly.
Click to expand...
Click to collapse
oh i understand now why you said that , sorry brother ,
i'll keep that in my mind , thanks for all your replays
So, long story short I recently decided to try and root my oneplus7t I unfortunately made some mistakes and somehow corrupted some files. I read elsewhere in the forum that I could download the stock rom which I did and then use flash-all and that would allow me to go back to the factory settings so I could lock the oem and just go back to normal because I was tired of the headache. Unfortunately, after using flash-all I locked the oem thinking everything should be stock and it would work properly. But it says device is corrupt and trying to unlock the oem says oem unlocking is disabled.
So did I just completely brick my phone? I don't know of anyway to fix it at this point :/.
kschmitz4 said:
So, long story short I recently decided to try and root my oneplus7t I unfortunately made some mistakes and somehow corrupted some files. I read elsewhere in the forum that I could download the stock rom which I did and then use flash-all and that would allow me to go back to the factory settings so I could lock the oem and just go back to normal because I was tired of the headache. Unfortunately, after using flash-all I locked the oem thinking everything should be stock and it would work properly. But it says device is corrupt and trying to unlock the oem says oem unlocking is disabled.
So did I just completely brick my phone? I don't know of anyway to fix it at this point :/.
Click to expand...
Click to collapse
Can you still boot into bootloader via the hardware keys, whatever that combo is on the 7t?
Boot to bootloader or recovery and factory reset it or so.
Josh McGrath said:
Can you still boot into bootloader via the hardware keys, whatever that combo is on the 7t?
Boot to bootloader or recovery and factory reset it or so.
Click to expand...
Click to collapse
I can get to the bootloader but it's Device State -locked and when I tell it to boot into recovery it says the device is corrupt. When I use fastboot to oem unlock it says I cannot, and I can't flash when oem is locked either.
kschmitz4 said:
I can get to the bootloader but it's Device State -locked and when I tell it to boot into recovery it says the device is corrupt. When I use fastboot to oem unlock it says I cannot, and I can't flash when oem is locked either.
Click to expand...
Click to collapse
Try
fastboot erase userdata and
Fastboot erase cache
Let me know if that works or not we will move on. Probably won't work since it's bootloader locked
You may have to contact OP and while you're at it, get the MSM tool for us all :good:
It says erase is not allowed in locked state . I think this is probably all she wrote for this one. I think I'm just going to send it back tbh, the whole reason I was trying to root it was because it didn't work with Sprint like they said it would. and I was wondering if I could find a way too make it work with custom software. Thanks for trying
Are you able to flash one of these Fastboot ROMs?
Maybe Sideload can work!
https://support.oneplus.com/app/answers/detail/a_id/4583/kw/7t here is official stock file.
https://forums.oneplus.com/threads/how-to-do-flash-through-adb-sideload.509377/
https://www.the***********.com/sideload-ota-update-stock-recovery-adb/
Please refer above links for your knowledge purpose maybe it can help.....
I unfortunately no longer have Twrp installed as I did a flash-all with a stock rom already . If I try and flash recovery it says "flashing is not alllowed in lock state". Sideloading wasn't functional back when I had twrp either as the functionality for it is still in progress. I'll probably try contacting support one more time and see if I can get a T2 who can unbrick it, otherwise I'm just going to send it back. Thanks for the attempts guys!
Edit: As to the flashboot roms I flash-all'ed one of them and that's how I got into this mess :/.
kschmitz4 said:
I unfortunately no longer have Twrp installed as I did a flash-all with a stock rom already . If I try and flash recovery it says "flashing is not alllowed in lock state". Sideloading wasn't functional back when I had twrp either as the functionality for it is still in progress. I'll probably try contacting support one more time and see if I can get a T2 who can unbrick it, otherwise I'm just going to send it back. Thanks for the attempts guys!
Edit: As to the flashboot roms I flash-all'ed one of them and that's how I got into this mess :/.
Click to expand...
Click to collapse
I ended up needing to flash the fastboot 10.0.3 firmware and was able to do a local upgrade to 10.0.4 that way, then flashing a patched boot.img via fastboot
I can't run any flash commands as my oem is locked. I don't suppose there's anyway around that?
kschmitz4 said:
I can't run any flash commands as my oem is locked. I don't suppose there's anyway around that?
Click to expand...
Click to collapse
How did you flash twrp with it oem locked??That doesnt make sense
I had twrp on it when the oem was unlocked, I was trying to reset the device to stock, so I did a flash-all and then oem locked it. But for some reason the repair was unsuccessful, and now it says my device is corrupted and I forgot to turn on oem unlocking in the settings on my phone after the flash-all before I did the oem-lock.
kschmitz4 said:
I had twrp on it when the oem was unlocked, I was trying to reset the device to stock, so I did a flash-all and then oem locked it. But for some reason the repair was unsuccessful, and now it says my device is corrupted and I forgot to turn on oem unlocking in the settings on my phone after the flash-all before I did the oem-lock.
Click to expand...
Click to collapse
You should have no issues reflashing the stock images
I cannot flash anything. Because my OEM state is locked.
Boot to Stock Recovery ?
Holding for a long time Volume Down + Power Buttons while booting your phone ?
Volume down plus power button takes me to "Your device is corrupt and will not boot"
kschmitz4 said:
Volume down plus power button takes me to "Your device is corrupt and will not boot"
Click to expand...
Click to collapse
Looks like you will need the MSM tool to fix this issue. You'll have to contact OP support and they will remote in your PC, load their software and flash it 100pct back to stock.
Also, disconnect them before they can delete the MSM tool so we can have it here in the community
kschmitz4 said:
Volume down plus power button takes me to "Your device is corrupt and will not boot"
Click to expand...
Click to collapse
Press volume up/down and power, reboot to fastboot. Unlock bootloader again. Install update from settings, reboot and install it again. (local install)
Factory reset in setting, reboot fastboot, lock bootloader. Reboot and untick unlock bootloader in developer settings.
Don't know if it's too late but I believe there's a working MSM tool now