Is it possible to unbrick after accidentally locking bootloader? - OnePlus 7T Pro (Regular & McLaren) Q & A

Hi,
I tried to install twrp on my device and must have done something wrong. I then tried to use one of the fastboot roms to go back to stock. However, this didnt work and i was unable to boot past the fastboot bootloader. For some reason i then decided to run 'fastboot oem lock' and have locked the bootloader. I understand that was stupid and now i'm stuck at a screen that says 'Your device is corrupt. It can't be trusted and will not boot'. Is it possible to fix this or have i permanently bricked this. Thanks for any answers and i'll happily get any other information you need.
Also i have seen the thread that says to use the msm tool to reflash the stock firmware/unbrick but i can't get the device to go into EDL mode. Every time i hold the volume + and - buttons while booting the device shows up on my pc for about 5 seconds before disconnecting. Sorry if i've misunderstood these instructions but i've tried it so many times and it just doesn't seem to go to EDL mode.

Keep trying with MSM tool. It can be very finicky from what I've heard.
Try different usb ports, maybe different cable or computer.
Since you can start your device it's not really hard bricked and you should be able to restore it completely.
Sent from my OnePlus7TPro using XDA Labs

No need to worry.
Flashing the stock rom with fastboot did not work because you have relocked the bootloader. Unlock the bootloader again with fastboot oem unlock and then flash the fastboot stock rom. It would work just fine and you would be able to boot into stock rom.

Related

[Q] Failed fastboot oem unlock

So, I have an Atrix 4G (2.3.6) and decided to try rooting in order to install a proper adblock. I'm a bit new to Android so I did some careful research and I found some tutorials that showed to do a fastboot oem unlock.
But I guess the Atrix doesn't unlock from a straight fastboot oem unlock command? Because it now boots directly to the fastboot screen with a "(ap) fastboot flash mode (s) flash failure" error.
I can get it to boot normally by holding the volume and power buttons and selecting 'normal' but that is a pain and can only be done with a good charge on it.
I'm going to say I don't know what I'm doing here. First and foremost I'd like to restore a normal boot, though I wouldn't mind knowing what to do from here to properly root it.
Lt.bird said:
So, I have an Atrix 4G (2.3.6) and decided to try rooting in order to install a proper adblock. I'm a bit new to Android so I did some careful research and I found some tutorials that showed to do a fastboot oem unlock.
But I guess the Atrix doesn't unlock from a straight fastboot oem unlock command? Because it now boots directly to the fastboot screen with a "(ap) fastboot flash mode (s) flash failure" error.
I can get it to boot normally by holding the volume and power buttons and selecting 'normal' but that is a pain and can only be done with a good charge on it.
I'm going to say I don't know what I'm doing here. First and foremost I'd like to restore a normal boot, though I wouldn't mind knowing what to do from here to properly root it.
Click to expand...
Click to collapse
what steps did you take? fastboot oem unlock only works when the bootloader isn't locked anymore. By default, manufacturers lock their bootloaders so also with motorola you need to unlock it first. There are some ways to do this, the sbf method and whatnot but it's not really idiotproof.
Is all you did the fastboot oem unlock? else you might want to relock it by "fastboot oem lock" and just root your phone if you don't want to go custom rom
Have you tried this: - http://forum.xda-developers.com/showthread.php?t=1182871

Completely f****d my G-Watch

SO, tl;dr-- My LG G watch turns on, then enters into a point where it is stuck doing the swirling colors boot animation until the battery dies. If I boot into bootloader mode, I cannot do anything other than reboot bootloader or power off. Recovery does not work, when I try it gives me the android guy on his back and tapping the screen does nothing. The restore tool used to be able to interface with my device, but now it does not even show up under 'adb devices.' If anyone could tell me something I can do, it would be greatly appreciated.
Is your bootloader unlocked?
Yes, I have an unlocked bootloader. When I turn the device on, it shows the little 'unlocked' symbol.
If you boot to bootloader mode can you run fastboot commands? If so, download one of the 6.0.1 roms from XDA and then follow the install instructions. If not....hmmm, not sure!
feyd2blak said:
If you boot to bootloader mode can you run fastboot commands? If so, download one of the 6.0.1 roms from XDA and then follow the install instructions. If not....hmmm, not sure!
Click to expand...
Click to collapse
How do I do fastboot commands? I can boot to bootloader mode, and the restore tool talks with my watch and recognizes it as a device sometimes.
Via a USB cable connected to a computer and the fastboot tool installed on that computer. You also need the correct fastboot drivers for this.

Stuck in bootloop after flashing custom recovery. Please help.

I ported TWRP using Android kitchen to flash to my device (Coolpad 801es) since there isn't an official version. For some reason, I can't seem to get fastboot to play nice with my phone (see my earlier post) so I used flashify. On reboot i'm stuck in a bootloop. I did have the foresight to back up my stock recovery with flashify and transfer it to my PC first, in case something went wrong. Now, I can't boot into recovery at all and ADB isn't working since the phone isn't being recognized by my PC when I plug it in. I just want to flash the stock recovery back and fix this. I can get into fastboot, and the PC does recognize the phone in fastboot, but when I try any commands it just hangs at waiting for device. I've googled but every solution i've seen for fixing a bootloop tells you to boot into recovery to do so.
Can someone please help me out?
UPDATE:
Upon further research, I discovered the reason fastboot commands weren't working is because my phone apparently isn't whitelisted in the fastboot exe. However, if I type Fastboot followed by -i 0x1ebf the commands seem to work. Using this method, fastboot devices lists my phone and fastboot reboot reboots the phone.
I think i'm on the right track, but when I try "Fastboot -i 0x1ebf flash recovery (path to recovery.img)" the terminal shows "sending 'recovery' (10240kb)..." and nothing else. No progress indicator, and i've waited 10 minutes for it to complete which should be more than enough time to flash a 10 meg file, but there's no change it just sits there. Like I said, I think i'm on the right track but I could REALLY use some help. I can't be the first person on here with this problem. Can someone, anyone, PLEASE help me.
So, more Googling would indicate that either i'm not using the correct USB port, or that my bootloader is locked. I have tried all the USB ports on my PC (front and back) as well as two different cables, no joy. As far as the bootloader being locked, the phone is rooted which I thought meant that the bootloader is unlocked as that is part of the rooting process. I try "Fastboot oem unlock" to check but I just get "failed remote no such command unlock" and there is no OEM option under developer options on this phone. I'm trying to piece this together but I could really use some help.

stuck on fastboot screen

my friend's redmi note 3 kenzo version just got stucked on fastboot screen because he tried to flash the device recklessly and now he can't do anything about it except turning it off, when he tried to turn it on again it's flashing mi logo and then shutdown, the only thing he can do is to hold the power + volume down button and get to fastboot screen, stucked there and that's it.
he ask me to fix his phone but i'm new to xiaomi customization world, the thing that i learn so far is :
1. this device is kenzo version (i don't even know what's the difference with the kate version)
2. i cannot flash using the miflash tool because it's getting the "remote: partition flashing is not allowed" message
3. i tried to unlock the bootloader using any kind of software and adb tool and i keep getting "remote: token verification failed" message
now, i got stuck and i don't know what to do anymore. what i know is i have to unlock the bootloader to move on to the next step, does anyone know how to solve my problem?
redmi note 3 is Mediatek device
redmi note 3 pro can be Kenzo or Kate (Qualcomm device)
Kenzo has 150mm
Kate 152mm
What file flash your friend? what is recklessly? (you try to write recovery?)
you try with mi flash?
or flash with fastboot?
http://en.miui.com/download-301.html#438
i don't know what ROM or methods he used to flash his device, but when he gave it to me the condition is as i mentioned earlier.
i tried flashing with miflash, got the message "remote: partial flashing is not allowed"
i tried flashing manually with adb tools, i got the same message
i googled for a bit and found out i need to unlock the bootloader, i can't do that since i can't get to developer option to enable "oem unlock"
what can i do now?
Unlock bootloader unofficialy HERE
I dont try that.
You can use EDL mode? HERE
Install rom/recovery with locked Bootloader ... HERE
I never use EDL MODE but is your solution (i think)
Good luck, if my comment help you hit thanks button
phantomsix6 said:
i don't know what ROM or methods he used to flash his device, but when he gave it to me the condition is as i mentioned earlier.
i tried flashing with miflash, got the message "remote: partial flashing is not allowed"
i tried flashing manually with adb tools, i got the same message
i googled for a bit and found out i need to unlock the bootloader, i can't do that since i can't get to developer option to enable "oem unlock"
what can i do now?
Click to expand...
Click to collapse
Only solution is Flash fastboot rom in edl mode. Coz May be ur device is relocked.
i found something while googling, and found this tool called "Android fastboot reset tool v1.2" there is an option to go to EDL mode there, but when i clicked "enter EDL mode" it says failed and the device just turned off, and that's it
there is some function i don't understand though like "reset FRP" or something
See my post i give you some links... The second have moded fastboot (for PC) with this method you can enter to EDL.
If not probably you need a test point method.
i've tried the link to go into EDL mode that you provided, it says "your device rebooted to EDL mode sucessfully" but the device is shutting down, and when i check "fastboot devices" on adb, it showed blank, so the conclusion is, i can't even go to EDL mode.
what do i do now?
http://en.miui.com/thread-650726-1-1.html
Search EDL mode kenzo or redmi note 3 pro

ZTE Z820 (Obsidian) Cant boot fastboot/bootloader bootloop

I tried using the Tool All In One to unlock the bootloader and manually through the adb and fastboot terminal. ADB recognizes the device even though every time i reboot to bootloader through adb or manually through the phone recovery and manual buttons it never sends me to the bootloader. i was able to flash the stock firmware with SP flash tool. I really just want to install TWRP. i have been able to root this device with Wondershare dr.fone root program. I wanted to get it to work with the All in One tool so i can install TWRP to install custom firmware. If anybody can point me in the right direction on why the bootloader never works and fastboot? Maybe this model the bootloader is unaccessible? And if i cannot get to fastboot to unlock the bootloader can i still install twrp somehow. Also when using fastboot command it shows the device id it just says waiting for device everytime and cannot get it to recognize past that point. Not being able to get past this phone problem has been really bothering me and irritating me lately so hopefully i can get it resolved. I will be back later to see if anybody knows a solution to this. it seems like i have been trying to do the same thing and maybe im right and fastboot mode and the bootloader is locked and currently not possible.

Categories

Resources