I installed the radio 5.08.00.04 (using the same file I had used previously).
Now it will not power ON. I tried 3 batteries. Nothing happens when I plug it to the wall either.
Any ideas?
thanks
2000a said:
I installed the radio 5.08.00.04 (using the same file I had used previously).
Now it will not power ON. I tried 3 batteries. Nothing happens when I plug it to the wall either.
Any ideas?
thanks
Click to expand...
Click to collapse
Most likely a brick. Sorry bro.
Did you verify that the Md5's matched?
MD5 matched. I used this same file to install before.
was this caused because I had previously installed the same radio?
It installed as usual, then i pressed something for it to reboot (prompt) but it powered off.
Why would you flash the same radio you had before? What file did you use, link to source, and how did you flash it? As a rule of thumb you should never flash the radio via recovery.
my device was rebooting in a loop and once, i was able to stop it by turning off data. i thought that maybe it could be the radio.
i used the file from >>> cyanogen wiki android.d3xt3r01.tk/cyanogen/passion/radios/passion.5.08.00.04.zip
like i said, i had that file in the SD card and i re-installed it today, but i had already installed it before.
now the nexus doesn't power on. i tried all the buttons (vol- + power, wheel + power)... nothing on the screen. completely black. i took out the battery for 30 minutes, and nothing.
after installing the radio, it powered off (there was an image of a box with an arrow towards the android)...
wasn't planning on buying another phone.
its possible your power button is damage.
Plug your N1 via usb to a pc, the charge light will come on, remove the battery. once the light goes off, quickly put the battery back in the phone. this should reboot your phone.
If your phone reboots, it means your power button is flawed, its common with N1. Take the battery out and do it again, this time hold the trackball. this will boot your phone into fastboot mode.
I tried connecting to the power adapter, but no light. the button was fine, and the device shut off at the end of flashing the radio. i think that it's supposed to reboot, or prompt.
the phone is dead.
So you flashed it in recovery... Time to work on that JTAG.
yah, flashed in recovery, not fastboot.
Jtag? Any links?
thanks
Weird I might say? I flashed mine in recovery and it was fine. And JTAG is a year old method manually tricking the device to boot up being bricked. Google it. Like I said, its really old. Good luck.
Sent from my Xoom using XDA Premium App
Related
Recently tried to flash from JF6 to JH3 and failed. It's now stuck at the phone ! computer screen.
Here's what I've tried so far starting with all the pull sd,sim,batt out and put battery back in:
1. Hold both vol up and down, then plug in usb.
2. Hold both vol up and down, then plug in usb, and then hold power. Let it flash on and off until I get to the 2nd blank screen, then release power.
3. Hold vol up and power, then plug in usb. Let it flash on and off until 2nd blank screen, then release power.
Holding down and power doesn't make the phone!computer flash at all.
I'm really at a loss now. No idea how to get back into download mode... I wasn't able to use the key combos to do it before; just used adb.
Any tips? Help is much appreciated. Thanks in advance.
I've always done after turning off the phone:
1. Plug in USB
2. Hold volume up + down
3. Press and hold power until it turns off for second time then let go (although it's worked for me on the first time it goes off)
Worked every single time for me.
tysj said:
I've always done after turning off the phone:
1. Plug in USB
2. Hold volume up + down
3. Press and hold power until it turns off for second time then let go (although it's worked for me on the first time it goes off)
Worked every single time for me.
Click to expand...
Click to collapse
Doesn't seem to work for me... anything else you can think of?
Have you tied to Flash it with Odin back to stock? Always flash back to stock before flashing. Every thread starts with the same instructions, flash back to stock first. Not to kick you when you're down.
I'd flash back to stock with Odin.
Rhiannon224 said:
Have you tied to Flash it with Odin back to stock? Always flash back to stock before flashing. Every thread starts with the same instructions, flash back to stock first. Not to kick you when you're down.
I'd flash back to stock with Odin.
Click to expand...
Click to collapse
He wouldn't be able to flash without getting into download mode now would he?
op: Make sure that odin is open and ready on your computer. if that doesn't work then i hate to say it but...
Looks like I've got an expensive paperweight? Luckily for me I got it yesterday...
Stupidly enough though, I probably should have returned it in the first place. It wasn't working quite right... I've never seen a phone not respond to button combos or have problems connecting to a computer via USB and I've owned my share of Samsungs. Each boot into their own recovery mode just fine via buttons... guess I won the lottery?
If anyone has some ridiculously convoluted way to get into download mode, I'd be glad to try it.
Did a bit of snooping...
http://forum.xda-developers.com/showthread.php?t=765703
It seems there are a fair amount of phones with disabled button combos...
when i flashed to jh3, i found doing the adb reboot download the easiest way to get into download, even when i messed up my phone and it would boot to galaxy s screen and it would get stuck. Found plugging it in via usb and then running the adb command
Ah... I see. Well, considering I can't get it to recognize it or anything... it's pretty much fubar. I tried my sister's captivate and it boots into download mode just fine with both vol + plug in usb.. so I assume I just had a defective unit that became more defective.
Thanks for the help all, and let's just have this be a lesson to anybody who wants to know, if you follow the instructions on the odin thread and you can't get in, either you're doing something wrong or the phone is wrong...
And adb never hurt anybody.
Thanks again everybody.
pokedoke said:
Did a bit of snooping...
http://forum.xda-developers.com/showthread.php?t=765703
It seems there are a fair amount of phones with disabled button combos...
Click to expand...
Click to collapse
I just exchanged a Captivate for shutting down by itself, got one that can't three button reboot, accidentally bricked it and couldn't recover it. Exchanged it for yet another one that also can't three button reboot. Uggh!
I decided to upgrade to Cog2.2beta5 from Cog2.1.4 today using ROM Manager. Everything seemed to go well but after install and reboot all I got was a black screen and subsequent reboots landed me at the same result.
So I thought restoring back to stock with Odin One Click from this forum, the one with all the ROM files built right in, was the best next step. I downloaded Odin and followed the instruction to the T and it got stuck at the PIT step. After a few attempts at it now my phone won't even power on. I've let it sit without a battery in for several minutes and even charged it on a wall charger for 30 minutes just to make sure it wasn't a dead battery. Still won't power on or respond at all.
I'm fairly new to all of this... Any ideas on what would cause a total melt down of the phone to the point of not even powering on? It has been flawless for me since launch.
Didi you download the drivers? also did you unplug the phone while doing the flash>/
pull battery sim and sd if you have one
Wait a minutes or so
plug in USB
hold vol up and down
put in battery
If the phone does not immediately go to download mode, you have a fancy paper weight that doesn't even weigh that much.
chibixzero said:
Didi you download the drivers? also did you unplug the phone while doing the flash>/
Click to expand...
Click to collapse
I did download the drivers and from everything I could see, my system and Odin recognized the phone without issue.
I had to unplug it during the process because the process froze in the same spot for well over an hour. I didn't see any other choice.
l7777 said:
pull battery sim and sd if you have one
Wait a minutes or so
plug in USB
hold vol up and down
put in battery
If the phone does not immediately go to download mode, you have a fancy paper weight that doesn't even weigh that much.
Click to expand...
Click to collapse
Guess it's a paper weight then because the phone won't power up at all let alone go into download mode.
Thanks for your time guys.
sounds like you might have done exactly what i did with my first captivate and yes it IS bricked! i know you will read "its impossible" to do that but i "thought" i followed the correct steps and flashed only a pit file. what it does is repartition your file system but apparently nothing is added after that...
not sure what steps you took on odin but it sounds like you got the same error i did and then the same issue so im going to assume the same thing has happened here...sorry matey
tnt533 said:
Guess it's a paper weight then because the phone won't power up at all let alone go into download mode.
Thanks for your time guys.
Click to expand...
Click to collapse
I had mine hosed for a while and this is what I did to get it back.
When it is unplugged and everything is out of the phone (sd, sim, batt) , hold the power button down for 10 sec, then release.
Put in battery, hold vol up + vol dwn, Plug into different usb port, Plug into phone.
That should get you into download mode
Mine did this too and the steps mentioned fixed it for me
Sent from my SAMSUNG-SGH-I897 using XDA App
I too accidently only wrote the pit file and it wouldn't do anything at all just blank screen . Make sure you remove everything open Odin one click, plug in your phone with the USB cable, hold down volume up and down and plug in battery it should start in download mode. It does work.
Sent from my SAMSUNG-SGH-I897 using XDA App
samsung captivate wont turn on after failed odin update
got an at&t samsung captivate. I want to try on something new with this phone so I search on some articles on how change rom..
first got the download mode showing on my phone then i connect it to pc with odin3 already started, I click on start button however my phone just suddenly shut off. tried turning it on but nothing happens. tried 3 key combos still wont turn on, tried removing sim, sd and batt connect phone without batt then pushing vol up and down then inserting batt still nothing. tried charging it, no light came up, still wont turn on..i would like to ask some help if how to turn my phone back on..
sorry for bad English
thank you
boangon said:
got an at&t samsung captivate. I want to try on something new with this phone so I search on some articles on how change rom..
first got the download mode showing on my phone then i connect it to pc with odin3 already started, I click on start button however my phone just suddenly shut off. tried turning it on but nothing happens. tried 3 key combos still wont turn on, tried removing sim, sd and batt connect phone without batt then pushing vol up and down then inserting batt still nothing. tried charging it, no light came up, still wont turn on..i would like to ask some help if how to turn my phone back on..
sorry for bad English
thank you
Click to expand...
Click to collapse
What did you try to flash with Odin? (with version, variant #, with/without bootloaders)
What was the Odin log?
nothing, no roms yet. i was in the first part of the instruction. this is what i follow
1. Download and install the correct drivers below (mac and linux don't need drivers)
2. Plug in your usb cable to your phone and computer
3. Open Odin
4. Enter Download Mode (see below)
5. Click Start
6. Be Patient, the first boot will take a while
where can i find the odin logs?
This might not be bricked, but if it isn't it must be as close as it can get. I flashed my phone back to stock 2.1 yesterday, and today when I tried to flash to cognition 8.1 it got stuck on "<ID:0/005> boot.bin" for a half hour. I unplugged it, and now my phone is stuck on the picture in the attachment.
- I can't get my computer to even pick it up with USB. Nothing happens at all.
- The only time it turns off is when I hold power, volume up, and volume down. Even then, it immediately boots right back into that picture. Nothing else happens.
- I can't get into download mode.
- When I remove the battery, it goes right back to this screen.
What can I do?
Happened to me earlier.
Do the following to get into download mode:
1) take out battery
2) put in battery
3) hold the vol up and vol down keys, then plug in the USB cord.
It will boot into download mode. Then try do what you were doing.
stuff said:
Happened to me earlier.
Do the following to get into download mode:
1) take out battery
2) put in battery
3) hold the vol up and vol down keys, then plug in the USB cord.
It will boot into download mode. Then try do what you were doing.
Click to expand...
Click to collapse
This hasn't worked before, but I went ahead and tried it again. It still just goes straight to the black screen with that picture in the center.
Hmm.
Well, I'm sure one of the 3 methods posted in the odin3 thread, on how to get to download mode, should work.
For me, it was the volume up and down buttons together, then plugging in the usb. It would turn on automatically and go straight to download mode.
None of the ones from this thread work:
http://forum.xda-developers.com/showthread.php?t=731989&page=96
evanstapler said:
None of the ones from this thread work:
http://forum.xda-developers.com/showthread.php?t=731989&page=96
Click to expand...
Click to collapse
Look under your battery below the serial numder of you phone and see if your batch is 1008. If it is those batches don't go into download mode. Send your phone in for waranty repair.
Rhiannon224 said:
Look under your battery below the serial numder of you phone and see if your batch is 1008. If it is those batches don't go into download mode. Send your phone in for waranty repair.
Click to expand...
Click to collapse
I don't see 1008 at all. I've booted into download mode before, even using the three button combo, I just can't now.
Would AT&T even cover this? Will they know I was tampering with stuff I shouldn't have?
Have you tried running Odin as administrator? Uninstall and reinstall the drivers for Odin. Keep trying, remove SIM, battery and external, hold the volume buttons only and plug phone in, keep trying, it should work. Blame the OTA for the "brick" and send it for warranty if you can't get Odin to work.
Rhiannon224 said:
Uninstall and reinstall the drivers for Odin.
Click to expand...
Click to collapse
Try doing this.
You know its interesting to see how many times I see people tell you to pull the battery, sim etc. Maybe I'm just lucky, but when I put my phone into download mode I power it off, open odin on my pc, hold down the volume buttons but NOT the power button and plug in the micro usb cable. Works everytime for me even with the PC /!\ Phone screen.
Rhiannon224 said:
Have you tried running Odin as administrator? Uninstall and reinstall the drivers for Odin. Keep trying, remove SIM, battery and external, hold the volume buttons only and plug phone in, keep trying, it should work. Blame the OTA for the "brick" and send it for warranty if you can't get Odin to work.
Click to expand...
Click to collapse
I've uninstalled and reinstalled twice, kept rebooting and removing my SIM and battery (no SD), changed USB ports, made sure each USB port works... Nothing has worked.
EDIT: The drivers I used were from here: http://forum.xda-developers.com/showthread.php?t=731989
Man, I'm not sure.
Either you're doing the button combo wrong.. since you said it worked before, or you're gonna have to send it in for warranty.
Remember don't press the power button. Just hold the volume up, volume down button, and plug in the usb cable
I'm about to go to AT&T for an exchange. Wish me luck.
In the meantime, though, what's the easiest, least-risk of screwing up way to get a brand new captivate on cognition 8.1 with the z4mod?
I would say wait until the CW issues are worked out with BETA9 and just CW flash it. I've bricked two batch 1008 Captivates from Odin freezing mid-flash today. I even flashed DG's 3ButtonFix first, to make sure I'd be able to do a button combo to get back into download mode, and no dice.
Epiphany said:
I would say wait until the CW issues are worked out with BETA9 and just CW flash it. I've bricked two batch 1008 Captivates from Odin freezing mid-flash today. I even flashed DG's 3ButtonFix first, to make sure I'd be able to do a button combo to get back into download mode, and no dice.
Click to expand...
Click to collapse
Wow that's interesting. I also have a batch 1008 and when I flash with odin it's fine. But after every time I flash to stock jf6 I lose 3 button combo and just reinstall the fix zip using clockwork. Download mode using both volume keys then plug in usb always works for me though even without the fix.
Sent from my SAMSUNG-SGH-I897 using XDA App
silverslotcar said:
Wow that's interesting. I also have a batch 1008 and when I flash with odin it's fine. But after every time I flash to stock jf6 I lose 3 button combo and just reinstall the fix zip using clockwork. Download mode using both volume keys then plug in usb always works for me though even without the fix.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Same here...I have 1008 and no issues flashiing back to stock losing the three button and either using adb or fix zip to get into Download mode.
A friend of mines son was installing roms on his HTC Hero and bootlooped it. I've followed all the methods I could find to put this thing in a flash mode, or a recovery mode but all it does is flash the HTC logo. Home/End seems to be the way to get into the recovery mode but it does nothing.
Can you put this thing into a flash only mode and at least get it to its original state? It is unknown as to what exactly he did to it. I was told that he had been installing lots of roms and eventually one made it do this.
I found this link http://forum.xda-developers.com/showthread.php?t=682551&page=2 but pushing the volume up/end keys only makes it vibrate 3 times then sit idle not doing anything.
thanks.
talktojer said:
A friend of mines son was installing roms on his HTC Hero and bootlooped it. I've followed all the methods I could find to put this thing in a flash mode, or a recovery mode but all it does is flash the HTC logo. Home/End seems to be the way to get into the recovery mode but it does nothing.
Can you put this thing into a flash only mode and at least get it to its original state? It is unknown as to what exactly he did to it. I was told that he had been installing lots of roms and eventually one made it do this.
I found this link http://forum.xda-developers.com/showthread.php?t=682551&page=2 but pushing the volume up/end keys only makes it vibrate 3 times then sit idle not doing anything.
thanks.
Click to expand...
Click to collapse
The only way to effectively help you/him is to know how he got there, and what recovery/rom/kernel/theme/etc he is running. It would also help to know if this phone has an eng-spl fastboot or an s-off hboot.
il Duce said:
The only way to effectively help you/him is to know how he got there, and what recovery/rom/kernel/theme/etc he is running. It would also help to know if this phone has an eng-spl fastboot or an s-off hboot.
Click to expand...
Click to collapse
theres no standard way to get to a flash mode with a sprint htc hero? what are some other key combinations i might try?
talktojer said:
theres no standard way to get to a flash mode with a sprint htc hero? what are some other key combinations i might try?
Click to expand...
Click to collapse
you mean like this: hold home and then power?
il Duce said:
you mean like this: hold home and then power?
Click to expand...
Click to collapse
yeah, so if that didnt work..screwed?
talktojer said:
yeah, so if that didnt work..screwed?
Click to expand...
Click to collapse
Not really... in very rare cases has the hero been bricked.
If nothing else, you could always run the Sprint/HTC RUU through your computer, that will restore the Hero to "Out-of-Box" state. From there you could root back again and flash any ROM you would like.
With the phone turned off, press and hold the volume up button. Whole holding it press the power button. When you see the logo let go of the volume up button. If that doesn't work you'll have to run an ruu from fastboot or get a hercimg and flash it from fastboot.
Sent from my HERO200 using XDA App
unCoRrUpTeD said:
With the phone turned off, press and hold the volume up button. Whole holding it press the power button. When you see the logo let go of the volume up button. If that doesn't work you'll have to run an ruu from fastboot or get a hercimg and flash it from fastboot.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
how do I get into this fastboot mode? I'd love to restore it to factory software, but I'm unable to figure out how to get the phone into a mode that the PC will recognize. Volume up/end vibrates 3 times but never actually turns on or shows a logo. just stays black. If I could get this thing back to its original state that would be great.
unCoRrUpTeD said:
If that doesn't work you'll have to run an ruu from fastboot or get a hercimg and flash it from fastboot.
Click to expand...
Click to collapse
Anyone know how to do this? I can't figure out how to get into the fastboot mode. I run the ruu executable, and it says it can't find the phone. I'm sure I need to put it in some kind of flash mode, but seem to be unable.
Not to hijack your thread, but I'm having this same problem. I've run several ROMs including cyanogen 6.0 and 6.1 and today was installing the cyanogen 7 with 2.3 android. I wiped everything and flashed the rom and the gapps and the phone went into constant reboot cycles. I could at that point, hold the power/home and get it back to the recovery menu. I had the Amon RA recovery and thought I would try the 3.0 clockwork, so I flashed that recovery image...rebooted without a problem. I tried wiping and reflashing, but still the constant reboot. So I took the advice on the wiki and flashed the DecaFuct-12222010-691.zip kernel. My phone rebooted and did not start the cycling, so I thought it was an improvement. However, 1/2 an hour later, it's still sitting at the HTC logo and the power/home does not reboot into recovery. Nor does trying to adb find any devices.
Apparently I haven't posted enough on these forums to be able to post to the dev thread. But I've done some base development work on the phone and have been using adb for over a year now. Any help on getting back to a working phone would be greatly appreciated!
Lynne
Ah, a coworker manager to get the buttons to respond. Yay! At least I'm back to recovery and can push a different ROM. Tho not CM7 since it keeps rebooting constantly!
lrandolph said:
Ah, a coworker manager to get the buttons to respond. Yay! At least I'm back to recovery and can push a different ROM. Tho not CM7 since it keeps rebooting constantly!
Click to expand...
Click to collapse
any idea what he/she did to get the buttons to respond? I still am unable to get into the recovery mode.
talktojer said:
any idea what he/she did to get the buttons to respond? I still am unable to get into the recovery mode.
Click to expand...
Click to collapse
First, power off and remove the battery. Make sure the USB is not plugged in
This is why you get 3 vibrations and no power on. If it does this again, remove the battery and start over
With the power off and the USB unplugged, hold Vol Up and press power on (End key)
It should then boot into fastboot. (a white page with green letters) At this time, plug the USB in (should change from Fastboot to Fastboot USB) and run the RUU .5 or .6 from your computer.
AT some point the RUU install will say waiting for bootloader. When this happens, you will already be in bootloader (Fastboot USB)
This should work to get you back to fully unrooted stock ROM. From there, reroot, install a custom recovery and rom.
Let me know if this works
ccrosno said:
First, power off and remove the battery. Make sure the USB is not plugged in
This is why you get 3 vibrations and no power on. If it does this again, remove the battery and start over
With the power off and the USB unplugged, hold Vol Up and press power on (End key)
It should then boot into fastboot. (a white page with green letters) At this time, plug the USB in (should change from Fastboot to Fastboot USB) and run the RUU .5 or .6 from your computer.
AT some point the RUU install will say waiting for bootloader. When this happens, you will already be in bootloader (Fastboot USB)
This should work to get you back to fully unrooted stock ROM. From there, reroot, install a custom recovery and rom.
Let me know if this works
Click to expand...
Click to collapse
here's what happens.
1. Remove battery
2. Replace battery
3. Press and hold volume up
4. While holding volume up, press and hold end key to turn unit on.
5. Unit vibrates 3 times and never powers on
This is without USB plugged in.
I asked the guy who owns the phone what he was doing, he said he had flashed ASOP Gingerbread or something and it never worked again.
talktojer said:
here's what happens.
1. Remove battery
2. Replace battery
3. Press and hold volume up
4. While holding volume up, press and hold end key to turn unit on.
5. Unit vibrates 3 times and never powers on
This is without USB plugged in.
I asked the guy who owns the phone what he was doing, he said he had flashed ASOP Gingerbread or something and it never worked again.
Click to expand...
Click to collapse
Interesting. Mine only does the 3 vibrate thing when I have the USB plugged in and I am trying to enter Fastboot. I unplug the USB, remove the battery, replace the battery, hold vol up and press end. Bing, right into Fastboot.
Do you know if he has the ENG SPL/S-Off installed? If not, the issue may lay in that. Not for sure though.
Also, it may have to do with the way the phone was originally rooted, that has an affect on things as well. Some of the overclocked kernels have an affect on boot. Some Heros wont boot with the kernel set to over 691.
I have installed every build pf ASOP 2.3.2 GB that has been posted, now grated they each had there issues but none of them put me in a loop or froze the phone.
I would also suggest downloading android commander to your computer. Just Google android commander and you will find it. With this program you can boot to bootloader. If you are getting to the HTC screen then Android Commander should recognize the phone. It is a great program.
talktojer said:
Anyone know how to do this? I can't figure out how to get into the fastboot mode. I run the ruu executable, and it says it can't find the phone. I'm sure I need to put it in some kind of flash mode, but seem to be unable.
Click to expand...
Click to collapse
Not sure, but you may try removing the sdcard and/or putting a different one in. Or when the phone first gets to the HTC screen press and hold the menu button and keep holding it.
Sent from my dual-booted liquidsense 2.1
unCoRrUpTeD said:
Not sure, but you may try removing the sdcard and/or putting a different one in. Or when the phone first gets to the HTC screen press and hold the menu button and keep holding it.
Sent from my dual-booted liquidsense 2.1
Click to expand...
Click to collapse
ive removed the sdcard, results are no different.
ccrosno said:
Interesting. Mine only does the 3 vibrate thing when I have the USB plugged in and I am trying to enter Fastboot. I unplug the USB, remove the battery, replace the battery, hold vol up and press end. Bing, right into Fastboot.
Do you know if he has the ENG SPL/S-Off installed? If not, the issue may lay in that. Not for sure though.
Also, it may have to do with the way the phone was originally rooted, that has an affect on things as well. Some of the overclocked kernels have an affect on boot. Some Heros wont boot with the kernel set to over 691.
I have installed every build pf ASOP 2.3.2 GB that has been posted, now grated they each had there issues but none of them put me in a loop or froze the phone.
I would also suggest downloading android commander to your computer. Just Google android commander and you will find it. With this program you can boot to bootloader. If you are getting to the HTC screen then Android Commander should recognize the phone. It is a great program.
Click to expand...
Click to collapse
android commander relies on adb..i've already tried adb and it can't see the device. already tried that the first night. I think I'm about out of options.
talktojer said:
android commander relies on adb..i've already tried adb and it can't see the device. already tried that the first night. I think I'm about out of options.
Click to expand...
Click to collapse
Interesting you say that. Here are 2 snips taken at the same time. One of my ADB shell showing no devics found and the other of my android command shell clearly showing connection to the device.
Try the android commander. It is a great program and it is GUI based.
Let me know
Edit: Even stranger, although ADB shows no devices, if I type LS, a list of the phone directories shows up.
ccrosno said:
Interesting you say that. Here are 2 snips taken at the same time. One of my ADB shell showing no devics found and the other of my android command shell clearly showing connection to the device.
Try the android commander. It is a great program and it is GUI based.
Let me know
Edit: Even stranger, although ADB shows no devices, if I type LS, a list of the phone directories shows up.
Click to expand...
Click to collapse
You would actually do
adb devices
You don't do it from inside adb.
Sent from my dual-booted liquidsense 2.1
Hello.
I woke up yesterday, dig into my pocket tried to turn it on... battery was dead so I plugged it in, and then ever since, the power button is unresponsive. It showed no previous signs of flakiness. But I've since spent the last 2 days digging and searching for ways to salvage. I see that Cyanogenmod has a nice trackball wake feature that could solve my problem. I download the sdk, and try to unlock the bootloader with fastboot, but fastboot FAILED with status read failed too many links (on windows 7). I tried on a Mac and it also failed for similar reasons. ./fastboot-mac oem unlock
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory
So from what I've read, pretty much all flashing of roms require either a power button and/or fastboot (because of the radio?). Is there another option I'm missing? I was able to root the phone by downgrading from 2.3.4 to 2.2.1 using the passimg method and using superoneclick. So now I have a rooted froyo phone, with no power button and can't seem to access with fastboot.
Any assistance would be great. I'm just trying to salvage the phone and resurrect it.
Thanks.
Ok, I think I've done something wrong. I used ROM manager to download and install cyanogenmod 7 but now my phone hangs on the X. I let it sit for like 30 mins. Then pulled the battery and booted into recovery mode and reloaded the passimg file from before. It is currently back to froyo. What, if anything can I do? Thanks.
You're never going to be able to use fastboot, because unlocking the bootloader requires you to use the power button to confirm that you wish to unlock...
Make sure you wipe before you flash a new ROM.
Using the ROM manager I selected to wipe everything and then it reboots into the triangle exclamation point. What is the method to flash without fastboot or a power button... it seems even the ROM manager needs the power button. What am missing here?
You need to install a custom recovery. You can do this from ROM Manager - don't use Clockwork 3.x
Thank you so much! I was able to push it through that way. Now that I've got CM7 on it I'm good... but now I'm left wondering if there are better ROMs out there... guess its time to play. Thanks again.
Ok, Now of course... there have been issues. Just getting it up and running had me a bit too excited. Now it seems that the screen is fading in and out... while 'sleeping' and usually when I unlock the screen the power off/airplane mode menu comes up. I 'think' the power button has regained some limited function... and is constantly pressed perhaps. Because now when the screen does remain asleep for a second, I can push the power button and it will wake. But when the phone is on, if I push it, it doesn't go to sleep. I've done some searching but haven't been able to find an app that disables the power button on the N1.
Any thoughts on what I could do, because this is quite annoying. It just flashes off and on and off and on. Thanks again.
The power button is on a separate board connected by a ribbon cable. You could just disconnect the cable?
You could just buy the button with a flex cable, and fix the phone...
Yeah, that too - lol!
Once inside the box, its sometimes difficult to think outside it! xD