SD Card deleted accidently now, no rom, no recovery no fastboot usb - Nexus One Q&A, Help & Troubleshooting

problem solved, thx guys
my damn usb cable was the reason why fastboot did not change to fastboot usb
new cable, no probs
yay!!!!
hope anybody can help me....
my Google NexusOne is not running any rom
if i start the phone its starting 1-3 secs as normal than it stucks by the anDROID logo...
but if i start into the bootloader mode/fastboot - i can`t start recovery cause the phone restarts after that in the bootloader mode.´again...
if i plug in the usb cable - theres only FASTBOOT MODE but not the fastboot-mode USB
with the result that i can`t flash any boot.img or custom rom by adb/fastboot console
if i want to do anything by ADB-console/cmd-console the computer can`t not find my devices
who can help me....thx so many for your attention....

Related

[Q] flashing recovery from sd card ?

is there a way to boot or flash recovery from sd card,,in the fastboot mode??
i mean to skip installing the driver for android,,it keeps tellin me <waiting for device> ,,thanks in advance
Is your phone connected to your pc? Open fast boot after you connected the phone with your usb cable, otherwise it wil says waiting for device.

My Z1 doesn't determined by PC in fastboot mode

Hi guys! I need your help. I have z1 with ROOT and custom recovery and i would like to update it to android m. The main probleme - bootloader, i should unlock it. But i can't do it because phone doesn't determined by pc in fastboot mode or flashmode and when phone is off doesn't determined at all. But even when phone is on, pc detected phone not always, just sometimes, and phone doesn't charging. ADB drivers is installed, drivers for flashtool mode and fastboot is installed. Command window says "waiting for device" when i want to boot my phone in fastboot. When phone is on ADB works fine. So i've read many topics about problems like that and didn't find the solution. Maybe can anybody help me please?
In ADB , use the command: adb reboot bootloader
The phone will reboot and you'll be in fastboot mode and the phone will show a deep blue notification light.
You need to install fastboot drivers from the driver package bundled along with flashtool before this. So u have to donwload flashtool first
Also, if u're going to unlock the bootloader then back up your TA partition.
In ADB , use the command: adb reboot bootloader
The phone will reboot and you'll be in fastboot mode and the phone will show a deep blue notification light
Click to expand...
Click to collapse
Yeah, I did it, the phone was showing blue led, but then it goes nothing, then pc doesn't "see" the phone. I have already installed flashtool and drivers with it for fastest and flashtool. Also I have already made a backup of TA through flashtool.
So I can do something with phone through flashtool or adb when phone is on, but when phone is off I can't do anything. I have heard that reason of that problem can be broken phone's USB port. What do you think?
And sorry for my terrible English
I've connected phone to pc in flashmode through NDR Utils, but fastboot still doesn't work
honestly, im stumped!! . AFAIK its not a problem with the usb port cuz as you said it works fine with adb. Did you try a different usb cable.
You should probably try to reinstall the fastboot drivers
But if you just wanna unlock the bootloader then you can do that with flashtool I think.
But if you just wanna unlock the bootloader then you can do that with flashtool I think.
Click to expand...
Click to collapse
Yes, but to unlock bootloader through flashtool I should go to fastboot
wait, does the blue led come on and disappear?? it sounds like a loose USB cable
masterofnocrack said:
wait, does the blue led come on and disappear?? it sounds like a loose USB cable
Click to expand...
Click to collapse
No, the blue led come on and lights until i unplug the cable.
Is it not a normal?
I have the same problem xD
All the time it worked, wtf
zawy. said:
I have the same problem xD
All the time it worked, wtf
Click to expand...
Click to collapse
Did you find the solution?
What did you do to fix it? Maybe we can help to each other
Hi! It's me again And i still didn't solved my probleme. So, i can connect my phone to PC and it recognize as Android device -> ADB interface, and as Xperia z1. If i just connect powered off phone to PC or connect phone in flash mode, then it recognize as USB devices -> SOMC Flash Device, is it right? Ok, when i want to connect phone in fastboot, phone shows blue LED and it goes nothing, PC don't determine the phone and i can't unlock bootloader

X620 bricked/ hard bricked after TWRP update by fastboot commands from 3.0 to 3.1

Hi,
Today i bricked/hard bricked my X620. I had TWRP 3.0.x, but i decide to flash with 3.1.x. I made it through by commands in windows using twrp.img file, and finished with fastboot reboot command, and phone died. Last info was something with the flow. I read many threads, and i found, that it's not alowd to finish flashing with this command. Now, im not able to switch on my phone, enter fastboot or TWRP, and when i conect my phone to pc, red light apears and i can hear a sound i win7 that something has been connected to pc, and disconnect, and connected, disconnected ...................., and nothing i happening with the phone. So, i'm not able to connect my phone to pc to make new flash by flash tool.
Can somebody help me with this problem????
Q
I can help you, just visit my blog
tickernel.tk
Present status
QbaQbaPL said:
Hi,
Today i bricked/hard bricked my X620. I had TWRP 3.0.x, but i decide to flash with 3.1.x. I made it through by commands in windows using twrp.img file, and finished with fastboot reboot command, and phone died. Last info was something with the flow. I read many threads, and i found, that it's not alowd to finish flashing with this command. Now, im not able to switch on my phone, enter fastboot or TWRP, and when i conect my phone to pc, red light apears and i can hear a sound i win7 that something has been connected to pc, and disconnect, and connected, disconnected ...................., and nothing i happening with the phone. So, i'm not able to connect my phone to pc to make new flash by flash tool.
Can somebody help me with this problem????
Q
Click to expand...
Click to collapse
Is it solved? I am also facing same problem.
BiswashKoirala said:
Is it solved? I am also facing same problem.
Click to expand...
Click to collapse
I am facing the same problem as well. Can anybody help pls??
No..I tried few solutions but the phone was still dead. So I bought a new phone.

Phone not detected

Hello,
I was on 10.0.7 version, rooted with magisk.
I had error while installing 10.0.8 version, then I downloaded 10.0.7 full rom, and used flash_all_except_data.bat.
Then after rebooting, it runs infinitely on loading animation (colors bar).
When I enter in fastboot, fastboot logo is displayed, but pc doesn't recognize phone anymore (fastboot devices show nothing).
[UPDATE]
I managed to boot with wiping data from recovery (Xiaomi stock recovery).
Now I can use the phone, but I don't have wifi (maybe something messed with vendor).
And I can't flash it because it is not recognized in fastboot mode (tried 3 W10 PCs, and 1 W7, it doesn't show in device manager)...
Can you help me ?
This is because the phone presents different device identifiers to the computer in these modes, and different drivers are needed, so it is possible to have proper drivers installed for one mode, but not the other. The fastboot program is simple and will just show the < waiting for device > message forever if drivers are missing. However, the same message may appear if the drivers are installed correctly, but the phone is not in the proper state with fastboot device IDs.
Make sure you aren't using a USB 3.0 port. Trying changing ports. The USB cable might also be the problem.
try using a direct usb 2.0 port on the pc ....
Otherwise reboot everything , erase cache first ?
Fastboot erase cache
or
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.
If the problem still exists the let me know
What's the exact error ? Waiting for device
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?
MIN313 said:
This is because the phone presents different device identifiers to the computer in these modes, and different drivers are needed, so it is possible to have proper drivers installed for one mode, but not the other. The fastboot program is simple and will just show the < waiting for device > message forever if drivers are missing. However, the same message may appear if the drivers are installed correctly, but the phone is not in the proper state with fastboot device IDs.
Make sure you aren't using a USB 3.0 port. Trying changing ports. The USB cable might also be the problem.
try using a direct usb 2.0 port on the pc ....
Otherwise reboot everything , erase cache first ?
Fastboot erase cache
or
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.
If the problem still exists the let me know
What's the exact error ? Waiting for device
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?
Click to expand...
Click to collapse
In fastboot mode nothing shows in device manager, with 3 different cables, with 4 different computers (3x W10, 1xW7).
I tried connecting with a live cd of CentOS.
Same results, adb connect when phone is started, but when I go in fastboot mode nothings shows in lsusb or dmesg...
Looks like the phone doesn't connect to pc in fastboot, very very strange...

(FIX)Press any key to shutdown, phone dead, fastboot not working, +2 days without it

I was texting, using xiaomi.eu rom stable lastest, stock kernel, no root.
Gallery stopped, then camera, whatsapp closed, instagram gave black screen...
I turned the phone off and then turned it on, bootlop, so I went to TWRP and wiped all partitions and also formatted data. I also did a selinux fix contents or something like that, I flashed another recovery, a custom one via zip and then phone died, mi logo and rebooted, only fastboot available.
When I use fastboot and connect it to my pc it gets detected as kedacom adb automatically, I tried lots of drivers, uninstalling any driver and installing google drivers and lots of things, got ADB and fastboot 15s installed, I also tried different cable, other pc, 2.0 ports, 3.0 ports, other Windows, virtualbox, doing fastboot flash recovery twrp.img with waiting device and then connecting...everything I've seen and know. I bricked my phone and other phones more than one time, and managed with almost no issue to fix it, but now i'm just lost.
I get Press any key to shutdown, on the left top corner of the phone, I do the following:
fastboot devices(gets detected by fastboot)
fastboot flash recovery twrp.img(instantly I get press any key to shutdown)
I can't do anything, it's dead, any tips or something? Thanks guys.
I needed 13h in total to fix it, so I wanna share what to do, the fix is in the post, scroll down a little bit and you'll see it. Hope it worked.
I fixed it finally, if anyone wants info, pm or reply
I need to tell this honestly, you should share what you did and how you did, so you can help anyone anytime if they encounter this problem anyhow. They can use this thread as a guide and don’t need to start a new topic and we save the forum from flood messages and topics. Thanks in advance.
THE FIX
It was very hard and tricky, but possible, you'll need a computer, usb data transfer cable, type c to usb, and a usb mouse, you'll need your device to be unlocked first, if it's not unlocked, I can't help you.
I used Tool All In One by Mauronofrio, installed drivers and with phone in fastboot connected it, if I press check, it will reboot and fail, you have to go to recovery flasher, if no recoveries are available, then download and put it on the same folder where the tool is. Go to recovery flasher(not zip one) select it, I recommend mauronofrio one, the lastest, and then select when going to flash flash and boot, it should be black screen with waiting devices and the phone with the press any key thing, then just disconnect the phone from the cable, restart it to fastboot and connect it, it should boot, you'll have mi logo or fastboot for a minute or 2 and then it will boot to twrp, but you may not have your touch working, just connect the type c to usb adapter and use a mouse, you should be able to use it, go to wipe, wipe all partitions, then format data and connect the phone back to computer, if it does get detected, you'll see the phone in file explorer, so you'll be able to move any files, move any rom to internal storage, use then the usb adapter and with the mouse, flash the rom, reboot and everything will work.
IF IT DOES NOT GET DETECTED, Go to recovery flasher(not zip one) select it, I recommend mauronofrio one, the lastest, and then select when going to flash flash and boot, it should be black screen with waiting devices and the phone with the press any key thing, then just disconnect the phone from the cable, restart it to fastboot and connect it, it should boot, you'll have mi logo or fastboot for a minute or 2 and then it will boot to twrp, but you may not have your touch working, just connect the type c to usb adapter and use a mouse, you should be able to use it, partitions allready wiped, so just put the rom file if it was deleted and flashbe sure that under partitions is MTP enabled, if it is and it still does not work, just go to reboot and select recovery, wait for it to boot to recovery. If it goes to fastboot and does not work, When booted, your twrp touch will be working again, if not, just flash another one.
There are other options, trying usb hub, 2.0 ports, a non amd pc, uninstall drivers and install google ones with internet disabled all time when flashing... But this is the one that worked, if anyone needs help, I can help you with Discord or pm.
Thanks for sharing the fix.

Categories

Resources