hello,i tried to change the CID of my phone(gsm) and the usb cable was removed. now i think that it is bricked,and it shows "error device not found" in cmd. can anyone help me plz?:crying: am ready to donate as much as you want.
Can you still get fastboot to work? If so, try typing this command fastboot oem writecid 11111111
No mate,only the red led lights when connected to my pc. No sign of life after that. When i adb reeboot bootloader,it shows "device not found".
can you boot into bootloader using power+vol down(pull batery first)? If so go into fastboot mode and check if device is detected (type "fastboot devices" )
if all goes well you could maybe try running an RUU to get your phone working again
EM|NEM said:
can you boot into bootloader using power+vol down(pull batery first)? If so go into fastboot mode and check if device is detected (type "fastboot devices" )
if all goes well you could maybe try running an RUU to get your phone working again
Click to expand...
Click to collapse
Nothing hapens mate. Can't get in bootloader nor recovery. If i connect to charger or pc via usb,only the red led lights up. Nothing more.
Related
Hi there,
I have a problem that i suspect others may have, i did my searching on google and on xda but found nothing so i have no other choice but to post. I am trying to fastboot flash a prerooted .67 firmware, i put my phone into fastboot and connected the usb cable, the led STAYS blue that seems to be fine(i have installed fastboot drivers using flashtool /drivers directory), i type in the fastboot command to flash it and it just sticks at "waiting for device".
Any ideas?
Thanks
What happens when you type:
fastboot.exe -i 0x0fce getvar version
Also:
1. Disable any antivirus
2. reboot your PC
3. Change to another USB port
4. Make sure the .img is in the same folder as the fastboot.exe
Try fastbooting an official firmware instead if that works then I believe you have encountered the 'bug' in the bootloader that is currently stopping any custom roms
unrealboot1 said:
Hi there,
I have a problem that i suspect others may have, i did my searching on google and on xda but found nothing so i have no other choice but to post. I am trying to fastboot flash a prerooted .67 firmware, i put my phone into fastboot and connected the usb cable, the led STAYS blue that seems to be fine(i have installed fastboot drivers using flashtool /drivers directory), i type in the fastboot command to flash it and it just sticks at "waiting for device".
Any ideas?
Thanks
Click to expand...
Click to collapse
Hi,
you know that every smartphone has a flash and a fast boot Feature ?
Some Smartphone, look´s like Sony, use:
Speaker UP Button and USB Connect for Fastboot
(by Sony the Home Button lights blue)
and
Speaker Down Button and USB Connect for Flash
(by Sony the Home Button lights green)
For Fastboot.exe ........ xy.img must be use the Fastboot
Feature.
In first using Fastboot.exe, after Phone Connect you must
wait that the PC find all Drivers.
If Fastboot doesn´t work again, maybe you need "SDK Android"
and "Google SDK Driver"... will find over Net.
Doesn´t work again, the use "Flashtool.exe" Methode and
convert the xy.xy Firmware to xy.ftf for Flashtool use.
Onex1
my version is 0.5
i tried all of this except the last point of Onex1. Nothing works still sticks at waiting for device. Also havent restarted my pc i will try that soon but i think that might be a long shot.
Also my device is recognised as an adb device if that helps.
Any ideas guys? I have been trying but now im all spent. My xperia s is unlocked and factory bootloader unlocked if that helps
I know this thread is really old, but I was having this same issue and it was fixed by using a newer version of the Android SDK. So if you're having problems, try updating!
U must enable USB debugging mode
Send from Xperia U
i have the same issue
power on off button is broke
i can boot to recovery but i cant select to flash anything because of the button its not working
adb works for me too because its recognized when i write adb devices but when i write fastboot devices nothing happens and everything i do it says waiting for device
anyway PrakashGD, he said adb is working, that means USB Debugging is ON, if it was off adb would've not worked duh
Ensure fastboot driver is installed
Sent from my ST25i using xda premium
Hi!
I recently got my new Acer Tablet A3-A30. After unlocking developer options and activating debugging I was able to use adb. So I rebooted into bootloader to see if fastboot works - it did not! The output of fastboot devices was empty (this and the following commands were typed as root).
So I killed adb with adb kill-server, disconnected it from my computer and turned it off. After a few moments I turned it on by pressing power while holding Vol[-]-Key. Again the tablet booted into fastboot mode. Now I connected it with my computer and hoped fastboot will recognize the device now. Again, the output was empty.
I noticed, that after connecting the tablet, the text fastboot mode on the display didn't change - all other devices I put into fastboot mode showed fastboot usb mode or similar after I connected them with my computer.
I tried different USB ports - nothing changed.
I'm just wondering, since I'm not familiar with acer devices: Is there a hidden key sequence to get into fastboot usb mode?
Thanks,
Tintom1
Tintom1 said:
Hi!
I recently got my new Acer Tablet A3-A30. After unlocking developer options and activating debugging I was able to use adb. So I rebooted into bootloader to see if fastboot works - it did not! The output of fastboot devices was empty (this and the following commands were typed as root).
So I killed adb with adb kill-server, disconnected it from my computer and turned it off. After a few moments I turned it on by pressing power while holding Vol[-]-Key. Again the tablet booted into fastboot mode. Now I connected it with my computer and hoped fastboot will recognize the device now. Again, the output was empty.
I noticed, that after connecting the tablet, the text fastboot mode on the display didn't change - all other devices I put into fastboot mode showed fastboot usb mode or similar after I connected them with my computer.
I tried different USB ports - nothing changed.
I'm just wondering, since I'm not familiar with acer devices: Is there a hidden key sequence to get into fastboot usb mode?
Thanks,
Tintom1
Click to expand...
Click to collapse
I have an a1-830 and it can be a real pain in the ass to get anything working on them. Try this, since you got adb working, adb reboot bootloader, then wait till it says fastboot cmd waiting or something. If that din't work, reply!
RAZERZDAHACKER said:
I have an a1-830 and it can be a real pain in the ass to get anything working on them. Try this, since you got adb working, adb reboot bootloader, then wait till it says fastboot cmd waiting or something. If that din't work, reply!
Click to expand...
Click to collapse
It worked, I got the fastboot mode with fastboot cmd waiting message!
Tintom1 said:
It worked, I got the fastboot mode with fastboot cmd waiting message!
Click to expand...
Click to collapse
Ayyy, hit thanks if I helped
RAZERZDAHACKER said:
Ayyy, hit thanks if I helped
Click to expand...
Click to collapse
But this is what I already got. It says fastboot mode (now with the waiting message), but not fastboot usb, so fastboot still doesn't see the device
Tintom1 said:
But this is what I already got. It says fastboot mode (now with the waiting message), but not fastboot usb, so fastboot still doesn't see the device
Click to expand...
Click to collapse
And fastboot devices shows...?
RAZERZDAHACKER said:
And fastboot devices shows...?
Click to expand...
Click to collapse
Nothing:
# fastboot devices
#
Tintom1 said:
Nothing:
# fastboot devices
#
Click to expand...
Click to collapse
If you are using Linux, try running fastboot with the sudo command. Also, the drivers might not be properly installed, check out this to download them.
Its not broken as it works to boot up into recovery. I am trying to unlock the bootloader on my blu studio one S0110UU. "Fastboot devices" shows my device so its connected properly Any help would be greatly appreciated. "Fastboot oem unlock" shows the confirmation screen but only the volume down button seems to work and get a response.
Also when trying to sideload in adb or flash in fastboot I consistently come across the error "Could not find "META-INF/com/google/andriod/update-binary in the zip file" Am i not using the correct file or something?
stickyfingers88 said:
Its not broken as it works to boot up into recovery. I am trying to unlock the bootloader on my blu studio one S0110UU. "Fastboot devices" shows my device so its connected properly Any help would be greatly appreciated. "Fastboot oem unlock" shows the confirmation screen but only the volume down button seems to work and get a response.
Also when trying to sideload in adb or flash in fastboot I consistently come across the error "Could not find "META-INF/com/google/andriod/update-binary in the zip file" Am i not using the correct file or something?
Click to expand...
Click to collapse
I have the same problem with Lenovo C2 phone. R u find the resolv alredy?
Hello,
Well i was trying to root my phone (leeco le 2 pro x620), i was following a guide that gave me a recovery.img.
I put the debugging mode and oem unlocked in developer options before start, then i put the phone in fastboot with "adb reboot bootloader" i checked with fastboot devices and all was ok, i wrote "fastboot flash recovery recovery.img" and that put this message in console "FAILED (remote: size too large)", after that i wrote "fastboot reboot", and its everything, the phone doesnt start, doesnt come in recovery or bootloader, and if i connect it to my pc, the pc makes a loop with the sound of connect and disconnect and the phone turn on the notification red light.
What can i do?
Trying to get TWRP onto my Sony Xperia S, LT26ii
Kernel version: 3.0.8+1.0.21100-30145-01956-g43358ca [email protected] host #1
Android Version 4.0.4
Bootloader unlocked, device rooted.
Typing "adb devices" shows my device as connected
Typing "fastboot devices" does nothing.
Typing "adb reboot bootloader" reboots device show a blue light on my phone charging light for 1 second then boots normally
Typing "fastboot flash recovery TWRP.img" displays "waiting for device"
So I turned phone off, disconected phone from USB and held power and volume up to test bootloader. I got a black screen and a single vibration followed by a gap of 1 sec and then 3 vibrations this repeated until I released the buttons.
I have no idea whats at fault but I would presume its android's bootloader or fastboot drivers or both any help would be appreiciated.