Hello
I unlocked my bootloader 2 days ago. but since i got twrp installed. and testart to bootloader. it shows that it is locked. does anyone had the same issue? TWRP is still installed and can still go to recovery.
Related
First place, i unlocked the bootloader. I don't know if was unlocked cause is not mine and the guy told me that he bought it unlocked for carriers. Well, after the "unlock" the phone lasted a lot for booting up. Well, i installed a based cwm recovery and flashed SuperSu for rooting the phone.
After that, i tried to this rom http://forum.xda-developers.com/showthread.php?p=54537621 I went to do a reset and with the data partition it shows "Error" so it can't format it. I installed the rom, but it's the same, the phone doesn't pass from bootanimation. Any ideas?
Xperia M C1904
Firmware: Android 4.3
migui0401 said:
First place, i unlocked the bootloader. I don't know if was unlocked cause is not mine and the guy told me that he bought it unlocked for carriers. Well, after the "unlock" the phone lasted a lot for booting up. Well, i installed a based cwm recovery and flashed SuperSu for rooting the phone.
After that, i tried to this rom http://forum.xda-developers.com/showthread.php?p=54537621 I went to do a reset and with the data partition it shows "Error" so it can't format it. I installed the rom, but it's the same, the phone doesn't pass from bootanimation. Any ideas?
Xperia M C1904
Firmware: Android 4.3
Click to expand...
Click to collapse
Did you use the CM11 CWM?
Cause you need to use CM11 kernel to flash CM11 ROM, and not from 4.3 kernel
migui0401 said:
First place, i unlocked the bootloader. I don't know if was unlocked cause is not mine and the guy told me that he bought it unlocked for carriers. Well, after the "unlock" the phone lasted a lot for booting up. Well, i installed a based cwm recovery and flashed SuperSu for rooting the phone.
After that, i tried to this rom http://forum.xda-developers.com/showthread.php?p=54537621 I went to do a reset and with the data partition it shows "Error" so it can't format it. I installed the rom, but it's the same, the phone doesn't pass from bootanimation. Any ideas?
Xperia M C1904
Firmware: Android 4.3
Click to expand...
Click to collapse
Hmmm... I think I had the same experience as you. First thing: ALMOST every phone you will buy will have a locked bootloader, while being able to unlock it is more of a 50/50 thing. Second thing: I tried the method on sony's site to unlock bootloader, and that resulted in bootloop. Unlocked with flashtool and worked perfectly.
I think I now understand my mistakes, but I'd love to hear it if there's a way around this. I have the International version H815. My plan was to end up with a rooted version of Marshmallow. At the beginning of the day, I was not so clear about the difference between unlocking and rooting. I followed directions to install a rooted version of Lollipop. That went well. I flashed TWRP but couldn't figure out why that didn't work until I figured out that the bootloader should have been unlocked first. I then went through most of the steps to officially unlock the phone, but my phone just hangs at a fastboot intro screen using the abd reboot bootloader command, so I can't use the fastboot utility to recover the device ID I would need to get an unlock code. And I can't get into the original recovery menu using the power-volume down keys. I think I overwrote the stock Recovery utility when I flashed TWRP from within a rooted system. Switching back to a stock kdz didn't help. The phone still works fine otherwise, but now I see no path to unlocking it and then installing TWRP to load a rooted 6.0 image. Should I just give up now, or are there any other options?
Thanks,
Jim
Got it working
I reinstalled the rooted image and flashed a stock recovery.img. That didn't work. Then I went back to stock with a different kdz image. I still couldn't access the recovery tools with the power and volume down buttons, but I was a able to get fastboot functioning and got the unlock code from LG and entered it - now to see if I can go back to an unlocked system and install TWRP to upgrade to Marshmallow.
Hey everyone,
My nexus 5x froze shutdown yesterday.
My phone uses TWRP and Cyanogenmod. After it happen I couldn't even boot into *recovery* ! The phone just "turns off" and I cannot turn it on for quite a while.
Eventually I was after to get into bootloader to use fastboot.
I tried to reflash the recovery. The flashing worked but I still couldn't boot into recovery.
I read somewhere someone who wrote that he/she locked and than unlocked the OEM lock and it worked for some reason, so STUPIDLY I locked my OEM, and when I try to unlock again it says I cannot unlock it (although I did enable OEM unlock in the first place, that's how I flashed in the first place).
SO HERE's the bottom line:
I am stuck with OEM lock enable and ONLY fastboot (cannot load into recovery).
I thought I installing OTA (which I can install with OEM lock), but I need ADB for that which I don't have.
ANY IDEAS????
THANKS A LOT IN ADVANCE GUYS!
Yeah, it's locked with a TWRP on it.
Now the data partition is unencrypted. I want to upgrade the bootloader, but it says it should be first unlocked.
Will unlocking cause destruction to all my data? If so, can I upgrade the bootloader?
P.S. My data is 20GB. I don't want to make a backup at the moment, if not necessary.
First of all: Yes, unlocking your bootloader will erase your data. Make a backup before you do.
Second of all: Is there a reason you want to do this? Your phone should continue to work fine if you're not on the newest bootloader or radio. Over the course of a year, I had updated mine from 6.0.1 to 7.0 to 7.1 without ever updating the bootloader and radio. It will work fine with an older version.
Third of all: As a curiosity, you have TWRP installed to the /recovery, but will it actually boot TWRP with the locked bootloader? I didn't think it would...
It's booting. I don't know why. I'll post a video if you want. BTW, if I bricked my device with the bootloader locked, is there any chance to re-flash it to stock?
I believe so. Instead of Pwr+VolDown to get into the bootloader, you can do Pwr+VolUp to get into recovery, and I think you can sideload the stock firmware. Don't quote me on that, tho, as I could be mistaken. Never had to do it myself, as I've always been unlocked and used Fastboot.
You may run into problems if you need to flash the factory images as you'd have to unlock the bootloader first so if there were any problems and you were unable to unlock it, you would not be able to flash them. My advice would be to unlock it and leave it that way as long as your device is modified.
I have a Mi 10T purchased in Italy, and therefore coming factory loaded with a "branded" firmware RJDEUHG. It should be a Windtre modded ROM, please correct me if I'm wrong.
The latest known working ROM was the miui_APOLLOEEAHGGlobal_V12.5.3.0.RJDEUHG_da9e1c75b5_11.0.
Tired of waiting for the slow updates, compared to the unbranded global rooms, I decided to de-brand the phone and upgrade to a stock RJDEUXM.
But none of the XM firmware would load from recovery, therefore I applied and successfully unlocked the bootloader.
With the bootloader unlocked I managed to successfully flash
apollo_eea_global_images_V13.0.2.0.SJDEUXM_20220329.0000.00_12.0_eea_ad6f7ce846
apollo_eea_global_images_V12.5.12.0.RJDEUXM_20220208.0000.00_11.0_eea_664a15ed19
but both got stuck in a bootloop right after flashing.
During one of the many attempts, I used the MiFlash tool and accidentally left the default Flash & Lock option, the flashing was successful and the bootloader was locked.
At the moment I'm on V13.0.2.0.SJDEUXM, and can load onto bootloader and recovery, while, as mentioned before, the system won't load and get stuck in bootloop.
If I try to unlock the bootloader once again, the MiUnlock does not recognize the phone while in fastboot mode, remaining in the "Not connected to the phone" screen.
Any help would be really appreciated.
maybe, this is the solution, seems the same issue
https://c.mi.com/thread-3265050-1-0.html
fastboot devices
fastboot continue
if you have some lucky, boot normally
otherwise follow all the step
bye