Unlock Bootloader soft-bricked HTC Desire 320 - Android Q&A, Help & Troubleshooting

Hi everyone,
I have a HTC Desire 320 (4Gb/512M ram Kernel v4.4.2). One day when I woke up the screen, I had a flood of errors: <Unfortunately, ******* has stopped> and nothing could be done further except removing the battery.
Also, when I tried to restore the phone to its facytory settings through Recovery Menu, nothing has changed and popup errors 5 sec after startup.
So I'm here trying to unlock my Bootloader using the step-by-step guide from htc.dev but I have NO fastboot entry in Recovery Menu.
Using <adb reboot bootloader> command I could see " =>fastboot mode..." in the bottom of screen but <fastboot oem get_identifier_token> or any other command is responding..
Also I can't flash my phone using SPFlash Tool, installing CWM or TWRP from sdcard or using adb was impossible (read only file system...)
Ultimately, I wanna flash the ROM so here i'm stuck with the bootloader issue...
PS. Unrooted phone, Debugging USB enabled, All usb drivers are installed, NO OEM Setting entry in Developper Options

Any suggestion is welcome..
Come on, I'm struggling here :crying:

Related

[Q] T-mobile HTC one Brick

I've had this phone for about a good 4 months now, was getting bored so i decide to unlock the bootloader, root, and install a new rom. Then i heard youwer able to activate the HTC logo button to wake and sleep your device with using a different kernel. tbaldens kernel v3.6. I have TWRP recovery installed with trickdroid as my rom.After i ran threw all the procedures to flash in Aroma installer. My phone won't turn on, when i connect it to my computer it shows up as a MTP device. When I do get it to power on its stuck at the "quietly brilliant" screen. cant get into recovery to restore from back up. PLEASE HELP! SOLDIER DEPLOYED!!!!!!!! dont have the means of sending it in. Any suggestion. Mac is my primary means of rooting. windows 8 drivers are kinda funky:crying::crying::crying::crying::crying::crying::crying:
If you have access to a Windows 7 PC, then download the RUU for your device. Next, relock your bootloader (fastboot oem lock) Next step, if you have bootloader access to your device, then you can go into fastboot (make sure it says fastboot USB). Open a command prompt, and type in fastboot oem rebootRUU. You're in RUU mode, where you can run the RUU and reset everything back to stock.
crashfocus said:
If you have access to a Windows 7 PC, then download the RUU for your device. Next, relock your bootloader (fastboot oem lock) Next step, if you have bootloader access to your device, then you can go into fastboot (make sure it says fastboot USB). Open a command prompt, and type in fastboot oem rebootRUU. You're in RUU mode, where you can run the RUU and reset everything back to stock.
Click to expand...
Click to collapse
can i do this from a mac? and i can't get into fastboot because it wont go past the htc logo screen. it is identified as a MTP device in windows
Ahhhh thankfully i was able to get into my bootloader and flash my recovery! but thanks for the reply bro

KIW-L24 Unlocked device but can't root device

After 2-3 hours of work I finally managed to unlock my Honor5x, but my phone seems to **** up on these few steps of the xda guide:
Step 9
Boot back into the bootloader by typing the following
"adb reboot bootloader"
Step 10
Flash the recovery with the following command:
"fastboot flash recovery twrp_kiwi.img"
Step 11
Once it finishes type the following
"fastboot reboot"
My phone gets recognized by adb generally, but whenever I use the command adb reboot bootloader, immediately after my phone doesn't get recognized by fastboot, so the following steps don't work. The phone is in bootloader mode however, and it DOES say that it's unlocked.
Things I've tried:
Using different USB ports
Using different USB s
Unplugging and replugging while my phone is in fastboot
Installing TWRP from the TWRP manager app (It gives me an error with every single version that's available. The error message is "Something went wrong. Flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occured. Would you like to attempt rebooting to recovery now?" Pressing the button reboot now doesn't do anything.
Re-enabled developer mode and made sure that usb debug and oem unlock are both enabled.
Computer is: Win 10 64 bit
Wtf do I do?
Araschon said:
After 2-3 hours of work I finally managed to unlock my Honor5x, but my phone seems to **** up on these few steps of the xda guide:
Step 9
Boot back into the bootloader by typing the following
"adb reboot bootloader"
Step 10
Flash the recovery with the following command:
"fastboot flash recovery twrp_kiwi.img"
Step 11
Once it finishes type the following
"fastboot reboot"
My phone gets recognized by adb generally, but whenever I use the command adb reboot bootloader, immediately after my phone doesn't get recognized by adb anymore, so the following steps don't work. The phone is in bootloader mode however, and it DOES say that it's unlocked.
Things I've tried:
Using different USB ports
Using different USB s
Unplugging and replugging while my phone is in fastboot
Installing TWRP from the TWRP manager app (It gives me an error with every single version that's available. The error message is "Something went wrong. Flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occured. Would you like to attempt rebooting to recovery now?" Pressing the button reboot now doesn't do anything.
Re-enabled developer mode and made sure that usb debug and oem unlock are both enabled.
Computer is: Win 10 64 bit
Wtf do I do?
Click to expand...
Click to collapse
Install the Huawei fastboot drivers
Sent from my SM-N920T using Tapatalk
I have HiSuite, which seems to be the USB drivers for huawei, but are you talking about the ones from team android? I can't post the link because this is a new account.

Unlocking bootloader via ADB

Hey all,
So Ive tried to unlock my bootloader but its not working, ive followed the steps from this site to unlock it but its stuck on the unlock bootloader screen. I have two options to choose from yes or no I click yes but it doesnt work, yet I click no and it takes me back to choose from fastboot, recovery and normal. My phone is a Alcatel Pixi 4.
I have enabled developer mode enabled usb debugging. I also have confirmed the RSA fingerprint for the computer. Also I have enabled OEM unlock in dev settings. This is what my cmd prompt window loooks like. I will also take a photo of my alcatel frozen on bootloader screen.
C:\Users\Dan\AppData\Local\Android\android-sdk\platform-tools>adb devices
List of devices attached
5HQGTCEQCAVS7TTS device
C:\Users\Dan\AppData\Local\Android\android-sdk\platform-tools>adb reboot-bootloader
C:\Users\Dan\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlock
...
This is what my phone looks like that im stuck on.
https://s11.postimg.org/8e2cjxooj/IM...129_172555.jpg
does anyone know why this is happening or know how to fix?
Issue has been solved as the bootloader is unlocked this process is not necessary.

CUBOT X12 - Bootloader returns to "locked" after unlock processing

Hi,
First I bricked my phone. Then I flashed the official stock rom using the SP Flash Tool. Then I started the phone and went directly to the build number and tapped it 7x. That made me a developer. Next I enabled USB developer options and enabled OEM bootloader unlocking. Then I connect my device to my Windows PC and start adb
Code:
adb reboot bootloader
That brings me into fastboot. There I use this command to unlock my bootloader:
Code:
fastboot oem unlock
After that I have tried two options:
Flashing twrp using
Code:
fastboot flash recovery x12-twrp.img
Which ends in a twrp bootloop. I guess because the cache was not wiped.
Using adb to reboot
Code:
fastboot reboot
. This however starts the rebootprocess and shows the Android man shortly - I guess that is wehere the cache is wiped - but then when I'm in the OS again everything is gone. It's like a factory reset. I can start over again by making myself a developer --> enable USB-developer options and allwo OEM bootlaoder unlock etc.
What am I doing wrong? I want to see the twrp screen on my phone. What should I do?
Many thanks for your help.

Nokia 1 (TA-1047) "No Command" screen and OEM unlocking issue

Hi, My Nokia 1 (TA-1047) is now in "No Command" mode.
I installed TWRP recovery previously and tried to root but failed. Then I installed stock recovery and phone started normally. As the phone started normally, I locked OEM through Fastboot mode and disabled OEM unlocking from "Developer Option".
But while installing "system update" from "Settings", it showed error and went to "No Command" mode.
Now I'm unable to flash anything through Fastboot mode because the OEM is locked. Also I'm unable to change OEM unlocking from "Developer Option" as the phone is not starting.
Is there any option to unlock OEM without the help of "Developer Option"?
salmanvai said:
Hi, My Nokia 1 (TA-1047) is now in "No Command" mode.
I installed TWRP recovery previously and tried to root but failed. Then I installed stock recovery and phone started normally. As the phone started normally, I locked OEM through Fastboot mode and disabled OEM unlocking from "Developer Option".
But while installing "system update" from "Settings", it showed error and went to "No Command" mode.
Now I'm unable to flash anything through Fastboot mode because the OEM is locked. Also I'm unable to change OEM unlocking from "Developer Option" as the phone is not starting.
Is there any option to unlock OEM without the help of "Developer Option"?
Click to expand...
Click to collapse
Edit. Okay, ignore most of what i said down there as after re-reading your post you seem to have a grasp on fastboot, the no command bit still applies though i think
"No Command" mode
If your talking about the recovery with the android image in the background, then there might still be hope, for some reason, the recovery starts up in this mode, showing the "no cammand" message, its fiddly, but you have to press the power button and either volume up or volume down repeatedly, in the end i was button spamming all the buttons and eventually the recovery menu showed up. Carefull to stop pushing buttons when the menu shows up as the buttons are how you navigate(v+,v-) and choose options(power button)
Whether that gives you any options i dont know, you could try a factory reset from the recovery menu, i suppose, or try the posted ota in the other thread if nokia has`nt released official firmware, although im not sure if you can use stock recovery to flash unofficial firmware, best bet is to try and boot into fastboot and use adb on another computer to flash the firmware that way, assuming the firmware files are available.
Most android devices have a way to boot into recovery or fastboot/bootloader using hardware keys
Quick google found this (works?)
Power off
Connect Micro USB to computer.
"In the next step hold down Volume Down + Power key for a short while"
Let go of the buttons when fastboot comes up
Using the computer with adb installed, go to a command terminal and type "fastboot devices" without quotes, you`ll know everythings working if your the device is listed in terminal after typing that command. From there look up fastboot flashing firmware or something to that extent, this is assuming you managed to find the correct firmware for your device and have it stored in your computer
I`d be real carefull here with fastboot, flashing wrong image file could make things much worse, at least it seems you can boot to recovery, so hopefully a factory reset fixes things, use fastboot as last resort i.e if its new job is a paperweight, as i dont think theres any particular guide on doing this specifically for the nokia 1, but i havent checked thouroughly so i could be wrong, take a look and see..............
And let us know if/how you managed to get it working
Goodluck

Categories

Resources