Did I just mess up? - Nexus One Q&A, Help & Troubleshooting

I'm afraid I'm in the process of bricking my phone.
I've done it before, and I thought I remembered exactly how to but I'm afraid I was wrong.
What I have done is to start up the phone in fastboot mode and in windows terminal typed:
fastboot flash radio radio.img
and it has now been saying "sending 'radio' 24960kb..." for at least 15 minutes and nothing is happening. Still the same screen on the phone as well.
I don't really dare to press anything at this point. Have I done something wrong? If so, is there anything I can do at this point?

what does the phone say?

It didn't say anything, nothing happened on it at all. After 30 minutes I figured what the hell and rebooted the phone and it seems to work fine, so I guess I dodged a bullet there

krasenpaskaa said:
It didn't say anything, nothing happened on it at all. After 30 minutes I figured what the hell and rebooted the phone and it seems to work fine, so I guess I dodged a bullet there
Click to expand...
Click to collapse
you sure you were in fastboot on the phone?
Next time before you do anything, type fastboot devices and see if your phone shows up. If it doesn't then your not in fastboot mode on the phone.

That was probably it, thanks a lot for the help

Related

How to COMPLETELY unroot

So I posted a thread about how my 3G wasn't working, and it's still not working. So after talking with Sprint for about 2 hours yesterday, I'm getting a refurbished phone. They told me when I get the refurb, to send back the one I have now, which is rooted. So I need to completely unroot the phone I have now. Is there a tutorial online that will show me how to completely unroot my phone?
Thanks
EDIT: Will this do it? If I just run this file with my phone connected to the computer?
Yes, the RUU completely restores the phone back to factory, unrooted stock condition, just like if it were fresh out of the box.
chromiumleaf said:
Yes, the RUU completely restores the phone back to factory, unrooted stock condition, just like if it were fresh out of the box.
Click to expand...
Click to collapse
Nice, also, I saw what you posted in my other 3G thread. I'm gonna give that a shot. The update profile thing I tried a few times (a few times myself as well as with the Sprint rep), but I never tried the airplane mode. Thanks for the info.
EDIT: Thanks, but it didn't help..still the same thing. I don't get what could be wrong though, I literally tried everything. I even factory reset my phone twice, still no go..I wonder if it's a hardware error, I don't know what else it could be at this point.
Okay so I'm trying to flash the originial RUU that I posted in my OP, but for some reason, when I start it up, it says "Waiting for Bootloader..." and it does that for about a minute, and then an error comes up saying that the phone couldn't be updated and to try again.. I did it twice and I'm getting the same error. Does anyone know how to get past this?
spatel9114 said:
Okay so I'm trying to flash the originial RUU that I posted in my OP, but for some reason, when I start it up, it says "Waiting for Bootloader..." and it does that for about a minute, and then an error comes up saying that the phone couldn't be updated and to try again.. I did it twice and I'm getting the same error. Does anyone know how to get past this?
Click to expand...
Click to collapse
Make sure your battery is charged pretty well (at least past 50% or so). Turn off your phone and turn it back on. Does it get stuck at the black HTC screen? Or the white one?
If so, leave it this way, plug your USB into the phone and computer, then try re-running the RUU with the phone stuck like that. Sometimes this works for people who get these types of errors.
Also check out this thread, some of that may be helpful: http://forum.xda-developers.com/showthread.php?t=586258
This one is similar: http://forum.xda-developers.com/showthread.php?t=703602
chromiumleaf said:
Make sure your battery is charged pretty well (at least past 50% or so). Turn off your phone and turn it back on. Does it get stuck at the black HTC screen? Or the white one?
If so, leave it this way, plug your USB into the phone and computer, then try re-running the RUU with the phone stuck like that. Sometimes this works for people who get these types of errors.
Also check out this thread, some of that may be helpful: http://forum.xda-developers.com/showthread.php?t=586258
This one is similar: http://forum.xda-developers.com/showthread.php?t=703602
Click to expand...
Click to collapse
Wow, you are just helping out left and right today, aren't ya, lol
Thanks, the first post on the first link you posted did the trick, thanks again.

[Q] Odin dosent seem to want to finish

It seems no matter what I do, Odin gets stuck in the middle of flashing back to stock. Sometimes its at 20%, others its at 80 or 90%. It just stops and sits there (Ive let it sit for over 20 minutes in the same place). So I take out the battery and wait a minute and try it again. The next time it will stop in a different place and never finish.
What now?
Have you made sure your phone is in debug mode first, and that your sd card isn't mounted? This was happening to me when I rushed on flashing one night, and forgot to change it.
Well I cant boot the phone... and I have seen the solid yellow screen, and the solid blue screen now while trying to flash Odin.
There is no way for me to boot the phone and make sure if the phone is in debug mode.
Sorry, I'm not a developer or programmer, all I know is the dumb obvious stuff because I've messed it up a couple times myself. The only other dumb maybe not as obvious thing I can think of is trying another USB port on the computer, one directly off the motherboard. Sometimes USB hubs or alternate ports seem to have difficulty providing enough power for extended times during flashes.
Thanks guys. Somehow, it meraculiously just finally finished. I let it sit there at the 80% for over 30 minutes and then it finally just finished and rebooted.
Im scared to actually flash something else now lol
AdamNimrod said:
Thanks guys. Somehow, it meraculiously just finally finished. I let it sit there at the 80% for over 30 minutes and then it finally just finished and rebooted.
Im scared to actually flash something else now lol
Click to expand...
Click to collapse
I can understand, but if you do want to try something else some time, just skip the flash to stock. It's really not necessary and, as you can see, can be dangerous.
Hmm...I was having the same problem using one-click on my laptop (non-one-click Odin worked fine). I tried my desktop and it finished successfully on the first try (both computers are running Windows 7 64-bit with the same drivers and same USB cable).

[Q] fastboot in recovery??

hey guys... not that its anything threatening... as far as i know, but earlier i was testing some roms and i had to remove and mtd partition(not sure if this is related to issue) so i flashed fr-remove, than did superwipe and powered off device... my battery was getting low last time i seen it so i figured i connect usb and let it charge a little before rebooting to flash rom.. so after a while of charging i reboot the device into recovery (forgetting to disconnect usb) holding home+power, as the normal G1 screen booted up it also had a 'FASTBOOT USB' in red lettering on top left corner of screen..
it never went any further.. just stayed at G1 screen and had fastboot usb on the top corner.. so i pulled the battery disconnected the usb than rebooted to recovery and flashed rom..
everything is ok so far im not sure if it affected anything... but i figured i would mention it on here and maybe someone knows what happened or at least why... and possibly could tell me if something bad is going to happen later on down the road lol
Hay
I have had that a few times when i erroed a flash or forgot to flash something proply or at all lol... mine seems to be going fine still, so i wouldnt worry about it. (unless someone esle says its a big ehem fkup.. lol)
Ethy
haha yeah so far so good for me too lol thanks for reply, kinda makes me feel a little better knowing im not the only one i think its fine though

D415 won't turn on

I use ClockworkMod's RecoveryInstaller, ran the .apk, installed it then opened it. There was a large button labeled "flash recovery" and when I pressed it, the phone turned off and won't turn on.
I plugged the phone into my computer and it continuously plays the "plugged in" sound. If I hold down the volume down and the power button, the "plugged in" sound plays more often and has another sound playing right after it, but the phone won't turn on.
I haven't unlocked my bootloader, but I have rooted the phone.
I believe it is in a boot loop or something, because the "plugged in" sound keeps repeating itself, or something like that.
I have an SD card if that is required in fixing the device.
I can't boot into recovery at all, screen keeps black.
rft2149 said:
I use ClockworkMod's RecoveryInstaller, ran the .apk, installed it then opened it. There was a large button labeled "flash recovery" and when I pressed it, the phone turned off and won't turn on.
I plugged the phone into my computer and it continuously plays the "plugged in" sound. If I hold down the volume down and the power button, the "plugged in" sound plays more often and has another sound playing right after it, but the phone won't turn on.
I haven't unlocked my bootloader, but I have rooted the phone.
I believe it is in a boot loop or something, because the "plugged in" sound keeps repeating itself, or something like that.
I have an SD card if that is required in fixing the device.
I can't boot into recovery at all, screen keeps black.
Click to expand...
Click to collapse
Try this
SubliemeSiem said:
Try this
Click to expand...
Click to collapse
I've been trying that, but I can't access my IMEI to get a KDZ file, and I've tried my IMEI on that thread before, and I didn't get any download. I've gotten an IMEI for my model from another thread, but that thread you sent me needs for my phone to connect to my computer, which it can't.
rft2149 said:
I've been trying that, but I can't access my IMEI to get a KDZ file, and I've tried my IMEI on that thread before, and I didn't get any download. I've gotten an IMEI for my model from another thread, but that thread you sent me needs for my phone to connect to my computer, which it can't.
Click to expand...
Click to collapse
Right, you already said that, sorry. In that case I'm afraid there's nothing else you can do, that phone is dead.. I do believe other users who had this kind of problem had to rely on the warranty to get a new phone, so you should go back to the store. And from now on, don't use one-click solutions to do this kind of stuff, the process isn't that hard and there is less risk involved when you just follow a step-by-step guide.
SubliemeSiem said:
Right, you already said that, sorry. In that case I'm afraid there's nothing else you can do, that phone is dead.. I do believe other users who had this kind of problem had to rely on the warranty to get a new phone, so you should go back to the store. And from now on, don't use one-click solutions to do this kind of stuff, the process isn't that hard and there is less risk involved when you just follow a step-by-step guide.
Click to expand...
Click to collapse
I am sending this phone in for a warranty repair. But since I rooted the phone, will they accept it? Keep in mind, I have rooted it with TowelRoot, but I haven't unlocked the bootloader.
rft2149 said:
I am sending this phone in for a warranty repair. But since I rooted the phone, will they accept it? Keep in mind, I have rooted it with TowelRoot, but I haven't unlocked the bootloader.
Click to expand...
Click to collapse
Not sure, in theory they wouldn't have to, since trying to install the bootloader caused your problems in the first place. But I've also heard of other people who did the same kind of thing and could still use the warranty. I just wouldn't tell them how it got bricked, play dumb and say the phone suddenly wouldn't boot up any more Best of luck, mate!
SubliemeSiem said:
Not sure, in theory they wouldn't have to, since trying to install the bootloader caused your problems in the first place. But I've also heard of other people who did the same kind of thing and could still use the warranty. I just wouldn't tell them how it got bricked, play dumb and say the phone suddenly wouldn't boot up any more Best of luck, mate!
Click to expand...
Click to collapse
The main issue I told them, was that it wouldn't boot or turn on. Somehow, battery issues played into it, but I told them that the MAIN issue was that it wouldn't turn on. I don't think they can turn it on if I can't. They have the money and power to try, but I'm pretty sure they're not going to spend a load of time trying to figure it out.
rft2149 said:
The main issue I told them, was that it wouldn't boot or turn on. Somehow, battery issues played into it, but I told them that the MAIN issue was that it wouldn't turn on. I don't think they can turn it on if I can't. They have the money and power to try, but I'm pretty sure they're not going to spend a load of time trying to figure it out.
Click to expand...
Click to collapse
They can easily find out is it rooted or not....................?
If u connect ur phone via usb by pressing vol down button..
U'll enter into download mode..
It clearly says ROOTED.........
But instead u have to try to update phone using B2CAppSetup.exe (official software update tool)
I have a lg d415 it just cut off yesterday n won't turn on i have no clue what to do

Recovering from the dead

So, I was clean flashing Titan Prime back into my XT1064 after testing CM12.
Everything went well, same apps, same configurations as always, no major changes.
I was about to reboot the phone when it did it by itself.
The boot screen (you know, the white one that burns your eyes) showed up, then it went away, and then oh surprise!, it came back again.
So the phone was in this bootloop within the boot screen.
I tried to enter to the Bootloader and the key presses (Power + Volume Down) did not work.
Every time I would try that, the phone screen would stay off for as long those keys were pressed down, and then, Bootloop.
After many tries I was about to let the phone stay in the bootloop until I find a solution here on XDA.
But I tried one more time, and lo and behold, it went into the Bootloader.
From there everything went as normal.
Now, the question is, could I have bad sectors?, could the Bootloader be corrupted?, could I have a ghost trapped?.
Thank you for answers and/or ideas.
And if any of you happens to be in my same situation, do not give up, let it be, try many times, and it finally will work (hopefully)
Strange. There wouldn't be bad sectors in internal memory. If it was me and I had your phone I'd try a complete wipe again. Of course that would be scary because you don't have a clue as to why it happened the first time. I wonder if it's your power button going screwy or maybe sticking.
That's the worst kind of problem, you do everything right and it still screws up then mysteriously fixes itself.
Did you maybe do any special changes/settings or similar things?
As Teil864 al ready says, you could reflash your rom and hope it'll never happen again.
Tel864 said:
Strange. There wouldn't be bad sectors in internal memory. If it was me and I had your phone I'd try a complete wipe again. Of course that would be scary because you don't have a clue as to why it happened the first time. I wonder if it's your power button going screwy or maybe sticking.
That's the worst kind of problem, you do everything right and it still screws up then mysteriously fixes itself.
Click to expand...
Click to collapse
You do everything right, the phone gets screwed, it gets fixed, and the problem is something no one else has had so you have no freaking idea of why or what it was.
It is not my power button, the only times I use it is when I turn the screen on, and it would not be the reason because it made a difference when it was pressed.
I will try some fastboot commands to scan sectors, but I need to remember how they worked. The last time I used them it was when I had a Galaxy Note 1.
Lars124 said:
Did you maybe do any special changes/settings or similar things?
As Teil864 al ready says, you could reflash your rom and hope it'll never happen again.
Click to expand...
Click to collapse
As noted on the first post, I did not do anything out of the ordinary. Same apps, same configuration as always.
The good thing is that I now can say I have every app that I need, with the configurations that I need, so I almost never need to change.
Let's hope it will not happen again.

Categories

Resources