I have a problem with my phone ... i unlocked bootloader,flashed boot.img via fastboot, installed custom rom.
Then i installed windows 10 on my pc and when i try to install adb fastboot drivers,i turn off phone,press power + volume up,light turns blue but after that it skip to Sony logo screen and device is on after. So my problem is i can't put my phone in fastboot mode.. I did it in past, a few times when i tried several custom room and needed to flash img via fastboot,but now it seems it won't work. Anyone know how to solve this?
VladHD said:
I have a problem with my phone ... i unlocked bootloader,flashed boot.img via fastboot, installed custom rom.
Then i installed windows 10 on my pc and when i try to install adb fastboot drivers,i turn off phone,press power + volume up,light turns blue but after that it skip to Sony logo screen and device is on after. So my problem is i can't put my phone in fastboot mode.. I did it in past, a few times when i tried several custom room and needed to flash img via fastboot,but now it seems it won't work. Anyone know how to solve this?
Click to expand...
Click to collapse
1. Disable driver signature verification.
2. Reinstall adb fastboot drivers
Yeah ... i did that again and now is working ... dunno what was the problem from the begging. Thanks
Related
Hello dear guru's =)
I have an HTC One international. Today i try to get root access and install custom recovery, whent i flash recovery i missed that chose a boot partition to install it. Now phone boots only into recovery, and from my PC, adb or fastboot don see it, but in usb devices its present.
Im on linux Ubuntu 13.04.
In phone dont have any backup.
The phone can't boot in bootloader?
Guich said:
The phone can't boot in bootloader?
Click to expand...
Click to collapse
When i chose from CWM recovery menu "Reboot recovery", phone boot into download mode, and thats all. Fastboot or adb dont see it.
But. In usb device list:
In download mode:
Bus 002 Device 061: ID 0bb4:0ff9 HTC (High Tech Computer Corp.) Desire / Desire HD / Hero / Thunderbolt (Charge Mode)
In recovery mode:
Bus 002 Device 063: ID 0bb4:0f91 HTC (High Tech Computer Corp.)
Assuming you didn't corrupt your boot loader you should be able to get at the boot loader and use fastboot to flash a new recovery.
Power the device off
Hold power and volume down, the phone should turn on and load into the boot loader.
From there you can select fastboot (navigate menu with volumn buttons, power button to select fastboot).
You can use this command to flash a recovery:
Code:
fastboot flash recovery recovery.img
If you can enter bootloader,you may try formatting partitions from fastboot,and flashing them afterwards,that is if bootloader is unlocked.
You can also lock your bootloader and try installing RUU,it will put your phone back to stock,
P.S. - I'm new to this,so please consult with more experienced members,before doing anything
ZloY909 said:
Hello dear guru's =)
I have an HTC One international. Today i try to get root access and install custom recovery, whent i flash recovery i missed that chose a boot partition to install it. Now phone boots only into recovery, and from my PC, adb or fastboot don see it, but in usb devices its present.
Im on linux Ubuntu 13.04.
In phone dont have any backup.
Click to expand...
Click to collapse
you "fastboot flash boot recovery.img"? you may want to check this thread: http://forum.xda-developers.com/showthread.php?t=2478438&page=3
if that doesn't help, post back
Guys, we have to check if he can boot in bootloader/fastboot.
So, @ZloY909, if you're in recovery, adb can recognize your phone?
And, in CWM, there is the option: reboot bootloader?
As download mode you mean bootloader?
ZloY909 said:
Has the same problem, flashed CWM Recovery to the boot partiotion. Can you give me more info about that magic what you are done to cennect your phone to fastboot? =)
Thanks.
Best Regards.
Click to expand...
Click to collapse
fastboot shouldn't be affected.
when you connect your phone to the PC, does it the text in bootloader change from "FASTBOOT" to "FASTBOOT USB"
Guich said:
Guys, we have to check if he can boot in bootloader/fastboot.
So, @ZloY909, if you're in recovery, adb can recognize your phone?
And, in CWM, there is the option: reboot bootloader?
As download mode you mean bootloader?
Click to expand...
Click to collapse
adb or fastboot is not recognize my phone. In cwm recovery i have only reboot option or reboot into recovery. I have the same situation as tha developer in other post.
when i chose boot to recovery i have : "screen with a phone icon and a green image like i can connect via usb or something, but then it turns red after about 30 seconds"
ZloY909 said:
adb or fastboot is not recognize my phone. In cwm recovery i have only reboot option or reboot into recovery. I have the same situation as tha developer in other post.
when i chose boot to recovery i have : "screen with a phone icon and a green image like i can connect via usb or something, but then it turns red after about 30 seconds"
Click to expand...
Click to collapse
"screen with a phone icon and a green image like i can connect via usb or something, but then it turns red after about 30 seconds" -> that's stock recovery
Before, when you are in bootloader (image attached), are you able to "fastboot devices" and it shows up? because the bootloader is not affected by the recovery.
basically "fastboot flash boot recovery.img" put the custom recovery where the kernel is supposed to be.
First thing you need to get/confirm working is bootloader/fastboot.
ZloY909 said:
adb or fastboot is not recognize my phone. In cwm recovery i have only reboot option or reboot into recovery. I have the same situation as tha developer in other post.
when i chose boot to recovery i have : "screen with a phone icon and a green image like i can connect via usb or something, but then it turns red after about 30 seconds"
Click to expand...
Click to collapse
In cwm adb will work.
So i think you have some issue with drivers.
And, however, if you turn off the phone, you can't access in bootloader with a longpress of power and vol-?
Hey, so I'm the one who had this same situation. What I had to do from what I recall is go to CWM screen, cleared the cache, even in advanced the davlik cache, then I believe (and you might have to try different combinations of this, because I don't 100% remember as I had before tried so many different ways) I unmounted the system mount, then went to reboot from the first screen to get to the bootloader (hold power button and volume down). After this, I clicked on Fastboot and it then went to Fastboot USB. This is where you should be able to connect. Don't leave this screen until you flash the recovery in the right place and then properly install the ROM. Let me know if you get to at least connecting and I can even send over an image for your boot, so you can at least get your phone back.
It can be done, I had the same situation so your phone is not bricked. Just keep working at it.
herrfricke said:
Hey, so I'm the one who had this same situation. What I had to do from what I recall is go to CWM screen, cleared the cache, even in advanced the davlik cache, then I believe (and you might have to try different combinations of this, because I don't 100% remember as I had before tried so many different ways) I unmounted the system mount, then went to reboot from the first screen to get to the bootloader (hold power button and volume down). After this, I clicked on Fastboot and it then went to Fastboot USB. This is where you should be able to connect. Don't leave this screen until you flash the recovery in the right place and then properly install the ROM. Let me know if you get to at least connecting and I can even send over an image for your boot, so you can at least get your phone back.
It can be done, I had the same situation so your phone is not bricked. Just keep working at it.
Click to expand...
Click to collapse
I will check this out. Thanks for your reply.
Now i reinstall to win8, reinstall drivers and adb.
Guich said:
In cwm adb will work.
So i think you have some issue with drivers.
And, however, if you turn off the phone, you can't access in bootloader with a longpress of power and vol-?
Click to expand...
Click to collapse
Thanks for your reply. This help me to get to the bootloader.
Now i try to flash boot.img into boot =)
Ok. I have working phone =)
Thanks for yours replies.
I recently got a z3c and decided to try to get a slim rom on it.
I have done the following:
I unlocked the bootloader.
This was done successfully to the best of my knowledge
The next thing I did was flash a cwm image to by z3c using fastboot. The problem was that I flashed the z3 version on my z3c.
The device would boot but the screen would be blank.
Later I flashed the z3c boot loader named : Z3c_DooMLoRD_AdvStkKernel_v01_FW-105
After this the device goes in a boot loop. I am able to access CWM.
I have tried to root the phone as well as flash the slim rom in an attempt to fix it....
Wiping disk / cache doesn't help.
Also for some reason even though adb drivers are installed I cannot use it so I can't get the twrp install to work.
I have no idea what to do can someone please help?
Thanks,
stp
I have same issue....Phone is ib bootloop...i can still go to fastboot mode....
Anything can be done here????
Flash an factory image with flashtool then you will have original recovery. Then reinstall CWM, maybe smth went wrong.
Tried flashtool---Ended up with errors as attached pic
As i cant bootup my phone...USB Debugging option cant be ticked
I was running SlimLP (unofficial) while bricked my phone....
Anything on that please....
I managed to recover my phone. I don't think you need usb debugging for flash tool. What I did was turn the phone off (power and volume up seem to be the buttons that force shutdown and break the reboot loop).
flashtool will prompt you to connect when you flash the ftf file and you hold power up and volume down when you connect the usb cable. If you have issues flashing (it hanged on me on system.bin) try restarting your computer.
Resolution and Problem Exp
Right after flashing the device recovery through fastboot the USB cable is plugged and that seems to loop the boot loader, so you need to force shutdown while looping by pressing POWER + VOLUME UP, and after that unplug the USB cable. You will notice that on boot now the light is no longer red.
splitthepositive said:
I recently got a z3c and decided to try to get a slim rom on it.
I have done the following:
I unlocked the bootloader.
This was done successfully to the best of my knowledge
The next thing I did was flash a cwm image to by z3c using fastboot. The problem was that I flashed the z3 version on my z3c.
The device would boot but the screen would be blank.
Later I flashed the z3c boot loader named : Z3c_DooMLoRD_AdvStkKernel_v01_FW-105
After this the device goes in a boot loop. I am able to access CWM.
I have tried to root the phone as well as flash the slim rom in an attempt to fix it....
Wiping disk / cache doesn't help.
Also for some reason even though adb drivers are installed I cannot use it so I can't get the twrp install to work.
I have no idea what to do can someone please help?
Thanks,
stp
Click to expand...
Click to collapse
Which is weird as it worked before.
Basic stuff. Android 6.0.1, MIUI 8.1
Bootloader unlocked
USB ADB drivers installed
Debugging on
Run TWRP and device is recognised, TWRP isntalled successfully but when I reboot phone into recovery, I get the standard "phone connected to usb cable" graphic. Im at a loss to know it wont go into TWRP, suggestions please?
Need to root to adjust in cqll volume settings, thx.
2bullish said:
Which is weird as it worked before.
Basic stuff. Android 6.0.1, MIUI 8.1
Bootloader unlocked
USB ADB drivers installed
Debugging on
Run TWRP and device is recognised, TWRP isntalled successfully but when I reboot phone into recovery, I get the standard "phone connected to usb cable" graphic. Im at a loss to know it wont go into TWRP, suggestions please?
Need to root to adjust in cqll volume settings, thx.
Click to expand...
Click to collapse
Not sure about alle the steps you did or did not do.
But if you install TWRP and then reboot back to MIUI, it will overwrite the recovery again.
From the TWRP.me site:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Ok, followed all the steps exactly, the phone boots into twrp, then i reboot in system, or let it reboot by disconnecting, same thing happens. Black screen MI logo, bootloader unlock, in red, at the bottom of the screen with an open padlock.
Now it wont boot at all.
This is weird, I can boot into fastboot and recovery but when i try to flash, the device is redognised but i cannot see it in the drop down menu to find the rom. Grrrrrr im stuck.
2bullish said:
This is weird, I can boot into fastboot and recovery but when i try to flash, the device is redognised but i cannot see it in the drop down menu to find the rom. Grrrrrr im stuck.
Click to expand...
Click to collapse
OK, if you want to keep MIUI, just flash MIUI again and it should install the needed firmware, recovery etc.
You can use the recovery zip for this or the fastboot gz version to install (both should work).
If you want a custom rom installed, go to the Lineage thread (i use that since feb, with weekly updates) or another one.
Read the first few post carefully, but if you want to install it (Lineage), do flash the firmware first via recovery before flashing the rom (don't forget this one).
Update. I can get into TWRP recovery but have no back up.
If I try to boot into system I get a black screen with Mi logo and a red unlocked boot loader padlock graphic.
If i boot into fast boot and run miflash, the phone is recognised but the sd storage does not appear in the drop down at all.
I cannot use the pcsuite software and if the phone is not in TWRP or fastboot mode it is on the black screen with logo with red unlocked padlock and is not recognised by the PC. I dont know what else to do, any help will be greatly appreciated.
Found out the problem it was supersu, gonna try a different version
2bullish said:
Found out the problem it was supersu, gonna try a different version
Click to expand...
Click to collapse
Glad you found the problem.
I think that MIUI has already build in the SU via the Developer options, but i'm not sure of that.
If you think of Lineage, just flash the Lineage Su addon after the Lineage rom.
Works great.
2bullish said:
Update. I can get into TWRP recovery but have no back up.
If I try to boot into system I get a black screen with Mi logo and a red unlocked boot loader padlock graphic.
If i boot into fast boot and run miflash, the phone is recognised but the sd storage does not appear in the drop down at all.
I cannot use the pcsuite software and if the phone is not in TWRP or fastboot mode it is on the black screen with logo with red unlocked padlock and is not recognised by the PC. I dont know what else to do, any help will be greatly appreciated.
Click to expand...
Click to collapse
MIUI has some sort of verification on boot. If it detects a custom recovery different from stock one, it won't boot. You need to use zcx twrp. It can bypass this verification.
Hey guys,
I have a problem while trying to flash TWRP on my Xiaomi Mi5. TWRP was installed earlier and worked completly fine with flashing custom ROMs, flashing OpenGAPs or rooting the device but now for some reason TWRP got lost and the standard Xiaomi recovery is on the device again. Installed was MIUI 8 in the Dev-Version (weekly patches) for the last half year and was the last ROM flashed with TWRP.
And now comes the problem when i try to install/flash the twrp image via fastboot: If i reboot the device in fastboot mode it shows the following behaviour:
1. It show the fastboot logo on the screen for about 10-30 seconds before it reboots automaticly (doesn't matter if i connect it via USB before or while it shows the fastboot logo)
2. While it shows the logo on the screen and it is connected via USB it's not showing up in the console when i list the all connected fastboot devices
I can still use the devices standard recovery and the installed OS, just the fastboot part seems to be brocken. Am i missing a driver on my computer or something?
Has somebody else an idea how i can solve this automatic reboot in fastboot mode?
Edit: If this Thread belongs into another catagory, i apologize
Make sure minimal adb and fastboot are installed in your pc. After that, enable usb debugging from developer options and connect with your pc and let it there for a while to install drivers on your pc. Then go to twrp and your phone should no longer reboot after your connect usb. Flash twrp here.
Sent from my Xiaomi Mi5 using Tapatalk
SilverMarcs said:
Make sure minimal adb and fastboot are installed in your pc. After that, enable usb debugging from developer options and connect with your pc and let it there for a while to install drivers on your pc.
Click to expand...
Click to collapse
ADB and FASTBOOT installed -> checked!
USB-Debugging enabled -> checked!
Windows installing drivers automaticly -> unsure. Windows didn't installed anything it just notified me that there is a new USB-Device (Device is also showen as ADB-Device and appears in the list of connected adb devices)
SilverMarcs said:
Then go to twrp and your phone should no longer reboot after your connect usb. Flash twrp here.
Click to expand...
Click to collapse
To that: TWRP is not installed on the phone anymore. I just have the standard xiaomi recovery where i'm not able to flash a .zip or something. I can just wipe all my data there
The reboot behaviour also appears if i switch to fastboot via "adb reboot bootloader" command while spamming "fastboot devices" to check if it appears before it reboots.
The standard recovery is usable as it should be without any reboots only the fastboot mode seems brocken.
FrozenPie1 said:
ADB and FASTBOOT installed -> checked!
USB-Debugging enabled -> checked!
Windows installing drivers automaticly -> unsure. Windows didn't installed anything it just notified me that there is a new USB-Device (Device is also showen as ADB-Device and appears in the list of connected adb devices)
To that: TWRP is not installed on the phone anymore. I just have the standard xiaomi recovery where i'm not able to flash a .zip or something. I can just wipe all my data there
The reboot behaviour also appears if i switch to fastboot via "adb reboot bootloader" command while spamming "fastboot devices" to check if it appears before it reboots.
The standard recovery is usable as it should be without any reboots only the fastboot mode seems brocken.
Click to expand...
Click to collapse
Weird. Everytime this sorta problem happens to me, its because windows didnt have the drivers installed after you connect your pc with debugging enabled. So thats the only troubleshooting i did to fix things. And yeah it did show me drivers installed correctly after i connected phone with debugging enabled. Maybe for some reasonn those drivers arent being installed to windows. Give it more time maybe? [emoji23]
Sent from my Xiaomi Mi5 using Tapatalk
SilverMarcs said:
Weird. Everytime this sorta problem happens to me, its because windows didnt have the drivers installed after you connect your pc with debugging enabled. So thats the only troubleshooting i did to fix things. And yeah it did show me drivers installed correctly after i connected phone with debugging enabled. Maybe for some reasonn those drivers arent being installed to windows. Give it more time maybe? [emoji23]
Click to expand...
Click to collapse
It's not working on both Windows 10 Machines i have. I'll try to install Windows 7 on my Laptop (or in a VM) and look if that works when i'm home again
Edit: Well, now i'm totally confused... For some reason fastboot started working again this morning so i was able to flash TWRP again. Anyway thanks for the help
FrozenPie1 said:
Hey guys,
I have a problem while trying to flash TWRP on my Xiaomi Mi5. TWRP was installed earlier and worked completly fine with flashing custom ROMs, flashing OpenGAPs or rooting the device but now for some reason TWRP got lost and the standard Xiaomi recovery is on the device again. Installed was MIUI 8 in the Dev-Version (weekly patches) for the last half year and was the last ROM flashed with TWRP.
And now comes the problem when i try to install/flash the twrp image via fastboot: If i reboot the device in fastboot mode it shows the following behaviour:
1. It show the fastboot logo on the screen for about 10-30 seconds before it reboots automaticly (doesn't matter if i connect it via USB before or while it shows the fastboot logo)
2. While it shows the logo on the screen and it is connected via USB it's not showing up in the console when i list the all connected fastboot devices
I can still use the devices standard recovery and the installed OS, just the fastboot part seems to be brocken. Am i missing a driver on my computer or something?
Has somebody else an idea how i can solve this automatic reboot in fastboot mode?
Edit: If this Thread belongs into another catagory, i apologize
Click to expand...
Click to collapse
I too have the same problem..****
Install MiFlash on your PC and try again, the device will show up correctly on fastbook devices command. It was a USB drivers issue in my case.
Hi All, I need fastboot!
Perhaps someone can help with my brick? I've unlocked the bootloader, installed TWRP and had lineageOS 18.1 installed once. The screen was dim so I tried to flash DotOS. And got a "failed to mount /tmp/com.android.resolv.apex to loop device /dev/block/loop16" error so I tried to reinstall stock 57 ROM.
I did "fastboot flash recovery boot.img" with the decrypted boot.img hoping to get colourOS recovery.
The phone is now bootlooping trying to get into recovery mode. It won't power off or respond to button presses except vol up + vol down seems to delay the reboot on a blank screen.
I was hoping to get to fastboot mode to flash TWRP. Can anyone help? Should I surrender and accept the bricking?
you can get back to stock by install the stock rom, vendor, and kernel with adb drivers and commands.
or
if your mobile is MIUI you can just use the software to revert back to stock rom remember it re-locks the bootloader and again you need to unlock
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
frolyx said:
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
Click to expand...
Click to collapse
did you ever get this solved and fixed? i have accidently done the same thing.
hey guys follow this youtube
managed to unbrick my phone
smiley.raver said:
did you ever get this solved and fixed? i have accidently done the same thing.
Click to expand...
Click to collapse
Not yet, but I will try the youtube method above..
This recovered the Phone!
But, win10 reported the MCT extractor contained a worm (the python script under linux didn't work). I'm not sure I can trust this phone 100% from now on LOL!
the bypass just deactivates mtk hardware verificaton as normally they have a special dongle they use with the software download
I havent had any issues
I will upload thw bypass i use which doesnt havw any virus