- January 21, 2017 at 11:30 PM #11684
One of the output of the following command: fastboot oem device-info
(bootloader) Device unlocked: true
Which tells the bootloader is unlocked.January 21, 2017 at 11:35 PM #11685
Yes, it is completely possible that after unlocking the bootloader data might not be wiped. It all depends on the OEMs the way they lock the bootloader. Many of the OEMs do not unlock the bootloader at all.
Now for the TWRP installation part, here goes another step-by-step guide that explains: how to install TWRP recovery on an Android phone.January 21, 2017 at 11:41 PM #11687
The command window waits at “waiting device”, when the device is not yet recognized by the system.
It is possible that you might have connected the device to the PC but either of the following is causing a problem:
- Either Android debugging is not enabled
- If Debugging is Enabled, check if OEM unlock is enabled in Developer Options
This guide explains how to enable USB debugging and OEM unlocking
- Finally, if everything is enabled, then check if you have given permission for the system to use ADB
When debugging is enabled and the device is connected to a system, it may ask for a permission on the phone to allow the ADB access to the system. Please verify all and let me know if you have enabled everything and still it does not work.
You must be logged in to reply to this topic.