Database Info

[Q] Please help unlock bootloader after flash a ship rom

my htc chacha had a boot loop, so i flashed a ship rom (stock) that downloaded from here
shipped-roms.com/index.php?category=android&model=Chacha (file name : ruu_chacha_htc_asia_wwe_1.57.707.2_radio_47.23.35.3033h_7.51.35.19_release_228383_signed.exe)
the phone works ok now but i want to root it, fist, i try unlock the bootloader at htcdev but it not success, it say error at [fastboot oem get_identifier_token​] command. (htc sync is installed on my XP).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
in that picture i don't know the bootloader status, please help :laugh:

You need to update hboot. Your version is 1.07, and I believe that in order to unlock it you need at least 1.10 version. That's the step before step 1 on HTC Dev site. Find the appropriate RUU for your rom and flash RUU. After that you will see a bootloader status in hboot and you will be able to unlock the bootloader.

didije said:
You need to update hboot. Your version is 1.07, and I believe that in order to unlock it you need at least 1.10 version. That's the step before step 1 on HTC Dev site. Find the appropriate RUU for your rom and flash RUU. After that you will see a bootloader status in hboot and you will be able to unlock the bootloader.
Click to expand...
Click to collapse
thanks, i update the phone via OTA and the bootloader status show it's locked again (hboot updated to v1.13), so i went to htcdev and unlocked successfully. :good:

Dont write on fast boot please help..

Dont write drivers installed my computer read the phone usb debuging on oem unlock on
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G935F using Tapatalk

What this directory that has 3? Rename it to English

i think cmd cannot read/recognise hewbrew.
you need to rename or replace the folder into one that is in english mate.

You said drivers are installed, USB debugging is on, and OEM unlock is enabled. Have you unlocked the bootloader via fastboot? If not, that is likely your problem.

gamer649 said:
You said drivers are installed, USB debugging is on, and OEM unlock is enabled. Have you unlocked the bootloader via fastboot? If not, that is likely your problem.
Click to expand...
Click to collapse
how i unlock bootloader on e6633 dual?

t_bahar said:
how i unlock bootloader on e6633 dual?
Click to expand...
Click to collapse
First check if you can unlock your bootloader, to do this follow these steps:
1) Open the Phone dialer
2) Type *#*#7378423#*#* to open the service menu
3) Tap Service info
4) Tap Configuration
5) Look to your rooting status, it will say one of three strings;
5.1) Bootloader unlocked: Yes (it shouldn't say this as your bootloader should be locked)
5.2) Bootloader unlock allowed: Yes (this means you can unlock your bootloader)
5.3) Bootloader unlock allowed: No (this means you can't unlock your bootloader)
If your bootloader lock status is 5.2 follow this guide. The process for unlocking bootloader is under Stock ROM > Guide.

Its work thanksssss
Any rom custom for e6633 ???
Sent from my SM-G935F using Tapatalk

Unlocking bootloader in LYF LS-4008 help

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Respected everyone,
My phone model is LYF LS-4008 manufacturer - fortuneship .... All the drivers are correctly install i.e, Adb, fastboot....and m trying to unlock is the bootloader for twrp and rooting purposes but m failed.... When I type adb devices it shows serial number then I type adb reboot bootloader my phone reboots to fastboot then I type fastboot devices then it shows serial number but when I type fastboot oem unlock or fastboot oem unlock-go on minimal software it only goes on loading and nothing happens in cmd and also in my phone it doesn't for unlock bootloader yes or no as you can see on the above image .....what to do sir please help me....
Thank you..

psusanta056 said:
Respected everyone,
My phone model is LYF LS-4008 manufacturer - fortuneship .... All the drivers are correctly install i.e, Adb, fastboot....and m trying to unlock is the bootloader for twrp and rooting purposes but m failed.... When I type adb devices it shows serial number then I type adb reboot bootloader my phone reboots to fastboot then I type fastboot devices then it shows serial number but when I type fastboot oem unlock or fastboot oem unlock-go on minimal software it only goes on loading and nothing happens in cmd and also in my phone it doesn't for unlock bootloader yes or no as you can see on the above image .....what to do sir please help me....
Thank you..
Click to expand...
Click to collapse
Vivo y51

No my model is LYF LS-4008

Fastboot stuck after printing three dots "..."

I'm trying to enable the bootloader on my XZ Premium (G8141, Firmware @47.1.A.12.75).
I was following their official guide.
Everything ran fine until i ran "fastboot -i 0x0fce oem unlock 0x<unlock c.>". For some reason it's getting stuck after printing "..." :
Code:
[email protected]:/home/user/Android/Sdk/platform-tools# ./fastboot devices
CB512EG2PN fastboot
[email protected]:/home/user/Android/Sdk/platform-tools# ./fastboot -i 0x0fce oem unlock 0x<...>
...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I ran everything as root, device seems to be visible and in fastboot mode (blue LED is on).
Additional info:
Android version: 8.0
dev. options: OEM Unlocking: ON, USB debugging: ON
rooting status: "Bootloader unlock allowed: Yes"
OS: Ubuntu 16.04 xenial
fastboot version 0.0.1-4500957
device is connected via USB 2.0

Your fastboot version is ancient.
Here on Debian Stretch:
fastboot version 1:7.0.0+r33-1
fastboot should be in your path once you installed the Android SDK.
You can try to update the SDK. On xda-developers you will find some threads to get you started. But that is far fetched for just unlocking the BL.
BTW: Did you backup the Trim Area with your unique Device keys which you are about to loose?
which fastboot
here: /usr/bin/fastboot
ls -l /usr/bin/fastboot
here: lrwxrwxrwx 1 root root 42 Apr 24 2017 /usr/bin/fastboot -> ../lib/android-sdk/platform-tools/fastboot
look if you have alternatives:
locate fastboot | grep fastboot$
If you are on a very good unmetered internet connection you could even boot up a live CD of Debian Stretch/Buster or 18.04 Beta1 of Ubuntu and install the SDK there.

Delete Userdata

I'm trying to delete userdata using fastboot, but this command "fastboot erase userdata" gives me okay reply, but when I reset phone, the userdata is still there. Any ideas?

Fastboot operates on phone's bootloader, not on Android OS where user data are stored in.
Use ADB to remove user data.

fastboot commands disabled on locked bootloader. post full output pls

Wrong: on devices that support fastboot you after having turned on OEM unlock you e.g. run
Code:
fastboot flashing unlock
to unlock its bootloader.

right. fastboot boot format erase flash are forbidden in locked state, to be nitpicky...
unlocking bootloader will perform factory reset, therefore it is protect by OEM toggle in developer options, too.

the phone's Bootloader is unlocked, and I can't do anything else with the phone when it can only fastboot. I can't even normal start phone to go into ADB.......

Rescueme said:
but when I reset phone, the userdata is still there.
Click to expand...
Click to collapse
How do you know if you cannot boot android?

Rescueme said:
the phone's Bootloader is unlocked, and I can't do anything else with the phone when it can only fastboot. I can't even normal start phone to go into ADB.......
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Re-flash Stock ROM, and if successful immediately enable ADB.