Database Develop

Bricked Nexus One?

Took my Nexus One off my cradle today to see it was locked up. Thought no biggie, I'll pull battery and restart it.
Now when it boots it comes up with four bars. Red, Green, Blue, White and the 3 skateboarding Droid Bots. I have no clue what to do now.
I was running Cyanogenmod (Forget the version, but it was 2-3 months old. I have not done anything to my phone except add the ebay app to it yesterday.
I can not get my computer to recognize it as a Nexus One anymore so I can not use Fastboot. I tried recovery from HBOOT, but keep coming up the same way.
Please Help
Ray

Picture of my Nexus One from Wifes iPhone...

I can get to FASTBOOT and when connected to USB it says FASTBOOT USB, but my computer fails to recognize the device and it goes back to FASTBOOT.
I can not turn on USB Debuging because it will not boot normal. I do not know what to do.

Weird screen, never seen that before.
Is this screen the only thing you see when you turn on the phone or do you still see the splash screen with the unlocked bootloader image prior? Have you tried booting into recovery? (holding the volume down button while turning the phone on)

Yes its the only thing I see.
I do not see anything Prior.
I have tried to boot to recovery many many times. I have 3 different results.
1. Nexus X with nothing else
2. Nexus X with Unlocked icon below
3. The screen you see
Either way, it does not move forward it just hangs. Is there a way to turn on USB debugging from FASTBOOT or HBOOT?
Ray
Russ T. Nail said:
Weird screen, never seen that before.
Is this screen the only thing you see when you turn on the phone or do you still see the splash screen with the unlocked bootloader image prior? Have you tried booting into recovery? (holding the volume down button while turning the phone on)
Click to expand...
Click to collapse

looks like the bootloader screen, thats what the rainbow screen was on the g1.
havent seen it on the nexus though so it could be something else.

Did you try a factory reset using hardware keys?
I believe you do this by holding vol-down, power and trackball for 5 secs.

That does not seem to do anything but take me to FASTBOOT

There has to be a way to turn on USB Debugging from FASTBOOT?

If you can get fastboot usb to work you could try the following (using latest amon_ra recovery.img):
Code:
fastboot boot c:\path\to\recovery.img
To boot into recovery, then use adb or try nand-ing etc.
if you get that far (recovery)
Code:
adb shell reboot normal
should take you into os.
However, the colored bars look like some pretty serious hardware failure I'd guess...

I can not get FASTBOOT USB to work. Any suggestion on how to get this working again?
Windows just says Unknown Device and uses a standard windows USB driver. I try to update the driver pointing it to android_winusb.inf but windows says no go.
Ray

check this out to help you get fastboot to work http://forum.xda-developers.com/showthread.php?t=613217
i know its titled ADB but it might help you out.

TheQue said:
I can not get FASTBOOT USB to work. Any suggestion on how to get this working again?
Windows just says Unknown Device and uses a standard windows USB driver. I try to update the driver pointing it to android_winusb.inf but windows says no go.
Ray
Click to expand...
Click to collapse
Try to enter to recovery but.... first change your microSD maybe that is the problem ... a faulty card .. Im just guessing

have you tried to contact htc or even google?theyve helped me over the phone even knowing i have an unlocked bootloader.

pvillasuso said:
Try to enter to recovery but.... first change your microSD maybe that is the problem ... a faulty card .. Im just guessing
Click to expand...
Click to collapse
not the sd card if it was a bad card it would just bootloop

if you have SDK you can see what the phone is doing with ddms

I would download SDK and install driver in SDK then you can run ddms and watch what the phone does in the realtime device log as it tries to boot

That pic reminds me of the MDA Win Mobile 5 boot screen, real similar...
Don't know how to help, keep us updated if you figure this one out.

gtrplr71 said:
I would download SDK and install driver in SDK then you can run ddms and watch what the phone does in the realtime device log as it tries to boot
Click to expand...
Click to collapse
I 2nd that. Try using ddms or logcat.
Good luck man!

What happens when you try to flash a rom?

[Q] ODIN doesn't see my phone in download mode.

Phone is ATT captivate SGH-I897 1008
Had my phone for 4 months or so, most of the time with cognition 2.x on it. Tried to update to 3.02 yesterday, and it had an error in the middle, left me at a recovery screen of sorts, and I chose to reboot from the possible selections. It got stuck on the ATT worldcom splash screen.
I tried several things. First, I tried to boot into recovery mode (vol up+power, then release) stays on splash screen. However, in this mode, if I connect my phone via USB, an adb devices command shows as connected. From there I tried both an adb reboot recovery, and adb reboot download command. The adb reboot recovery reboots into the worldcom splash screen just like the key combo does. I can't recall what the download option did, though I think it worked.
Secondly, I realized I could reliably get the phone into download mode, so I decided I would try the download mode, and restore to stock. I found an ODIN on the seminal ODIN thread, downloaded it, and started it up. Put the phone into download mode (hold vol + and vol -, plug in the usb) and that worked fine, however, ODIN doesn't see my phone. I left the phone in this mode for a couple hours just to make sure, and tried disconnecting, and reconnecting, and initialized the procedure from the beginning several times -- no go.
So, I am stuck, and coming to the experts. Hopefully, someone has some good suggestions. I was unable to find someone in a similar predicament, so maybe I am SOL.
Thanks in advance for any help.
UPDATE:
I rebooted my laptop (windows XP) and when I plugged in my phone, it saw "new" hardware and the name of the hardware it sees is "gadget serial." This might explain, if it is not initializing the right drivers why ODIN can't see the phone. The only problem is I don't have any clue how to redirect it to see the right hardware now.
Success Update
After reading the seminal ODIN thread a bit more careful, I came across someone who had similar issues with the gadget serial device. Apparently the drivers I got (I think from the Samsung site) are not good enough to cover that aspect of use. I installed with the drivers from links on the ODIN post and my phone was recognized! As I type, I am installing back to stock.
Thanks everyone for their efforts, and I hope my experience could be useful.

Desk top or laptop, have you tried all the ports

I would test to see if adb recognizes your device first during normal operations. I'd that doesn't work, your usb port may not have enough power or you have a bad usb cable. I think adb can also restart right into download mode but check around first.
Sent from my SAMSUNG-SGH-I897 using XDA App

mcord11758 said:
Desk top or laptop, have you tried all the ports
Click to expand...
Click to collapse
I have tried on my laptop mostly. But I did a cursory try on a desktop as well (the desktop has the drivers installed)

trekie86 said:
I would test to see if adb recognizes your device first during normal operations. I'd that doesn't work, your usb port may not have enough power or you have a bad usb cable. I think adb can also restart right into download mode but check around first.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I tried two differing cables, both of good quality. One was the cable that came with the phone, the other was a mini-usb cable with a micro adapter. Neither worked. I can't do normal operations right now (that I know of), seeing how the phone is in a bad state.

jbwray said:
I have tried on my laptop mostly. But I did a cursory try on a desktop as well (the desktop has the drivers installed)
Click to expand...
Click to collapse
Use rear usb ports on desktop. Make sure you are using original oem cord
Have you used odin before

jbwray said:
I can't do normal operations right now (that I know of), seeing how the phone is in a bad state.
Click to expand...
Click to collapse
Sorry, didn't read your first post close enough. I'm not sure what you can do, someone suggested the battery pull method in another thread, but that was just to get their phone in Download mode. It had nothing to do with ODIN after it was in download mode. Hopefully someone will have a suggestion for you. Good luck.

I'm having a similar issue except that odin sees the phone when booted into the rom, which I find odd.
Would you be so kind as to link the drivers?

[STUPID] Managed to get into APX

Heey,
So today I really did something stupid hehe, I risked borking my tablet in the name of science.. I flashed a complete image from the Transformer, with kernel and stuff included. So yes, that kind of destroyed my tablet.
It won't load into fastboot at all, nor will it load up stock recovery.. But... I managed to get my PC to load it as an APX device along with the proper drivers too. Now I wonder, isn't APX the full acces bootloader for Tegra devices?
In any case, I will see if I can get my device back up and running using this APX stuff, I have high hopes it would work but am no expert on this.
If you have suggestions in the meantime, feel free to post them.
(Don't even get the Galaxy Tab boot image with the open lock by the way, only backlight goes on and stays blank all the time)

im sorry! help please!
i have the same problem with my 10.1v

Wouldn't hurt to give this a try
http://www.xda-developers.com/android/one-click-unbrick-for-samsung-captivate/

djmasque said:
Wouldn't hurt to give this a try
http://www.xda-developers.com/android/one-click-unbrick-for-samsung-captivate/
Click to expand...
Click to collapse
Didn't work for me, APX seem to work, but to be able to write files in APX mode you need to have the SBK. Which we don't have ofcourse, so it's back to the shop today, I know some people there and I'm just gonna play stupid. They will fall for it, will just tell them that after the battery was empty it wouldn't boot anymore. They can't even see the padlock since the only thing the thing does when you power it on is turning on the backlight

ONCE IN APX MODE, GO INTO CMD WINDOW (START>RUN>TYPE CMD), DIRECT TO THE DIRECTORY IN C:/NVFLASH, THAN FOLLOW THESE INSTRUCTIONS TO RETURN BACK TO NORM, nvflash folder included in the post,
http://forum.xda-developers.com/showthread.php?t=1130574

[Q] Kindle F.HD 7-doesn't boot and win won't recognize device

Hi Guys,
So a few months ago I was trying to update to CM10 and when I was with TWRP i stupidly pressed wipe all instead of just flash as it was required at that time. I ended up deleting EVERYTHING or so it seams. Kindle won't even show any logos, screens, nothing, key combinations do nothing and when I connect it to any PC the PC "goes crazy" with it, the sound windows make when a USB device is connected and when you disconnet one? it constat, like it connects/disconnects/connects/disconnects/ and so on. I get a message that windows cannot recongize the device.
My guts tell me I absolutely wiped everything even twrp and now its a blank piece of hardware. is there a way to come back from this??
Appreciate any helpo I could get (and yes, regular users should not mess with stuff lie this. i know. )
Thanks, Charlie.

Do you have a fastboot cable? You will need to get into fastboot and flash a full restore.

Red_81 said:
Do you have a fastboot cable? You will need to get into fastboot and flash a full restore.
Click to expand...
Click to collapse
Unfortunately I don't, and customs in my country won't let almost anything go through if I buy it online. If there is still hope to recover it I will try and have a friend buy one when abroad.
Once I get my hands on said cable what will it do and what would the next steps be?
Thanks a lot for replying @Red_81!

You can make one yourself if you're handy. Check out the SRT tool for how to do a full restore

[Q] KFHD Tate Custom ROM Failure - Brick recovery

Hi, Newbie question.
I have a 2nd Gen Kindle Tate that I was looking into installing CM11 on. Up until recently I have managed ok with it being rooted and running apks and apps from Google Play.
Major issue at the moment where I seem to be stuck
Here's what I have done:
A few months ago I had updated the Firmware to 7.5.1.
I had rooted it using Saferoot (Busybox), which has worked fine.
I tried to install CM11 but after failed attempts I found out it couldnt with the current firmware so needed to downgrade to 7.2.3 (Using KFHD_SRT_v1.3.0 tool )
I had stupidly replaced the boot.img & recovery.img files without a backup (BIG BIG mistake i know!)
I wasnt able to boot into the OS anymore
I also tried to install TWRP & COTR using the KFU 0.9.9
Since it turned off I hadnt been able to turn it on since.
I have tried leaving on the charge for hours and still nothing (2A cable).
I have a fastboot cable.
Is there anything I can do or is it completely dead?
Read somewhere before that you can short the KF to make it boot (sort of like a PSP Pandora battery). if this is true any guidance on this.
perhaps a SkOrPn cable?...but cannot find one

before you get too drastic. check adb drivers, a hard boot then plug in to pc
does your pc see the device at all when you plug it in? if so maybe try the KFfirstaide http://forum.xda-developers.com/showpost.php?p=54274465&postcount=3416
or this one
Red_81 said:
You can restore a rooted stock image if you have the ability to get to fastboot.
http://forum.xda-developers.com/showthread.php?t=1951254
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
doing the pin jump.
i got my other kindle into fastboot that way. but i didnt have a blank screen. and adb/fastboot still wont see it
im no guru. just at the point on that one that it didnt matter if it was bricked. i only noticed the other pins as the diagram kinda showed them in the same order. so i tried each one. lol
there is a group of 6 pins total.
power(no shut down. just on/off)* *
fastboot * *
Reboot/restart * *
http://mascote.me/images/kindle_fire_hd_7.jpg

Djskizo said:
before you get too drastic. check adb drivers, a hard boot then plug in to pc
does your pc see the device at all when you plug it in? if so maybe try the KFfirstaide http://forum.xda-developers.com/showpost.php?p=54274465&postcount=3416
or this one
doing the pin jump.
i got my other kindle into fastboot that way. but i didnt have a blank screen. and adb/fastboot still wont see it
im no guru. just at the point on that one that it didnt matter if it was bricked. i only noticed the other pins as the diagram kinda showed them in the same order. so i tried each one. lol
there is a group of 6 pins total.
power(no shut down. just on/off)* *
fastboot * *
Reboot/restart * *
http://mascote.me/images/kindle_fire_hd_7.jpg
Click to expand...
Click to collapse
so connect the pin to the copperish tape? or do i strip the tape??? need connection to mains?? total noob here.

any confirmation on this??? what's the next step?

and old thread...still no joy. any suggestions before i have to part with??

can anyone confirm HOW to unbrick this? jump the wire, etc?

dug this out of an old box................still in the same state, still an issue any updates?