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.
Related
Hey guys I need help. My HTC One is stuck in bootloader mode. I was trying to upgrade to the latest T-Mobile update. I tried downgrading with an RUU and I tired to flash stock recovery. I'm not all too sure what exactly happened, but I have no OS or recovery mode. All I have is bootloader mode. When I try to reboot to OS there is a bootloop. When I try to go into recovery a picture of a phone shows up with a red triangle and exclamation point. When I enter Fastboot in the bootloader it shows up on the phone as Fastboot USB. Although it says Fastboot USB, the phone is not recognized on the computer. When I try to enter fastboot commands, the prompt says "waiting for device" no matter what command I type.
If I could get the computer to recognize the phone, I could flash a recovery and a ROM or run an RUU. But that is only if I could get it to recognize the phone and I can't. I have searched for days and I can't find anything that works.
I have no OS, no recovery mode, and the bootloader isn't recognized on the computer. Please help! any help/advice will be greatly appriciated!
Please and thank you! :good:
amkivb said:
Hey guys I need help. My HTC One is stuck in bootloader mode. I was trying to upgrade to the latest T-Mobile update. I tried downgrading with an RUU and I tired to flash stock recovery. I'm not all too sure what exactly happened, but I have no OS or recovery mode. All I have is bootloader mode. When I try to reboot to OS there is a bootloop. When I try to go into recovery a picture of a phone shows up with a red triangle and exclamation point. When I enter Fastboot in the bootloader it shows up on the phone as Fastboot USB. Although it says Fastboot USB, the phone is not recognized on the computer. When I try to enter fastboot commands, the prompt says "waiting for device" no matter what command I type.
If I could get the computer to recognize the phone, I could flash a recovery and a ROM or run an RUU. But that is only if I could get it to recognize the phone and I can't. I have searched for days and I can't find anything that works.
I have no OS, no recovery mode, and the bootloader isn't recognized on the computer. Please help! any help/advice will be greatly appriciated!
Please and thank you! :good:
Click to expand...
Click to collapse
keep on rebooting until it's seen in the PC. Make sure the driver is installed (or forcible install it if it's an unknown device).
After that, once you're able to see it... re-flash the unlock token (fastboot flase unlocktoken unlock_code.bin). That will get you back into the ROM. At least, that's what did for me:
http://forum.xda-developers.com/showthread.php?t=2665481
But I can't reflash an older RUU at all, so I can't downgrade.
Drashna said:
keep on rebooting until it's seen in the PC. Make sure the driver is installed (or forcible install it if it's an unknown device).
After that, once you're able to see it... re-flash the unlock token (fastboot flase unlocktoken unlock_code.bin). That will get you back into the ROM. At least, that's what did for me:
http://forum.xda-developers.com/showthread.php?t=2665481
But I can't reflash an older RUU at all, so I can't downgrade.
Click to expand...
Click to collapse
I figured it out. All I needed was windows 7 instead of 8 for some reason. After I installed 7 I just ran the 4.3 RUU. Now I have a different problem. Originally this all happened because I was going to upgrade to the new 4.4.2. Now I can't flash stock recovery. I have cwm but I need stock recovery to upgrade to 4.4.2. Since there is no 4.4.2 RUU I don't know what to do now.
Hi,
I am trying to see if I can spring an old Karbonn Titanium s2 back to life by installing a compatinble Cyanogen OS in it if I can find one.
I have ADB and FastBoot installed in my Windows 7 PC.
Now the problem I am facing is I just cant boot this damn thing into Fastboot mode.
So,When I do this
adb reboot bootloader
The phone simply reboots. Literally. Reboots.
On the other hand, commands like
adb reboot recovery
works just fine.
Its just the reboot bootloader command that isnt working, which is halting my endeavor at the very first step because I cant unlock a bootloader that is invisible and so I cant install a custom recovery in it.
Any Help??
Thanks in advance.
P.S: The device runs Android JB and is rooted.
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.
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.
I have a xiaomi mi8 with the unknown baseband
so I wanted to flash a full rom and supposedly fix the problem
but the phone when I put it in fastboot mode with the bootloader already free, there is no way to connect either by adb or miflah or fastboot adb etc it comes out of fastboot and there is no way to load twrp or any other type of flah
Does anyone know why this happens??
thank you
@spock2010
This post understands who want to, me not.
I can not make flash in any usual way, that's the problem or my flash, nor install twrp anything, fastboot mode does not allow to do anything