Related
My Nexus one won't turn on. I tried flashing RADIO 32.24.00.22U_4.03.00.21_2 that I downloaded from Modaco.
After it failed to install showing the error message like
"Multiple Radio images"
and a few others I try to reboot it.
when trying to reboot it there showed a picture of a android and a orangish arrow and a box.
Help...I think I bricked it.
Help?
Please?
Can you get into boot loader? Hold down the track ball, then power on, and keep holding down the track ball...
Also, try holding down the "volume down" toggle button while powering on if the track ball method doesn't work...
If both don't do anything but take you to that same screen, let it sit on that screen for a bit, say 10 minutes just in case...
If still nothing, see what happens when you plug your phone into your computer with the data cable, is it recognized? If so, can you get ADB to recognize it?
Jackasaur said:
Help?
Please?
Click to expand...
Click to collapse
can u get to the recovery image? if u can, its not bricked.
well I tried plugging it into the computer, I tried the wall charger, and nothing seems to work. The LED doesn't come on, and the button combination doesn't work. So I think it's dead for good. :C Before everything got screwed All I saw was a box and an arrow pointing at a android. Which I think meant it was unboxing. I then thought it froze so I tried to take the battery out, and after that it didn't turn on anymore. No LED, no recovery, no nothing. :C Quite sad.
Why the f are so many people intent on taking their batteries out while the phone is updating? I'm not saying that led to the bricking...but it probably didn't help.
Jackasaur said:
well I tried plugging it into the computer, I tried the wall charger, and nothing seems to work. The LED doesn't come on, and the button combination doesn't work. So I think it's dead for good. :C Before everything got screwed All I saw was a box and an arrow pointing at a android. Which I think meant it was unboxing. I then thought it froze so I tried to take the battery out, and after that it didn't turn on anymore. No LED, no recovery, no nothing. :C Quite sad.
Click to expand...
Click to collapse
This part takes a few minutes. I am not totally sure what is happening at this point but I'm assuming it's not good to remove battery during this. Mine sat on that screen for a few min and then finished.
Try to boot up with volume down button held. Then use volume arrows to choose recovery and hit power.
uansari1 said:
Why the f are so many people intent on taking their batteries out while the phone is updating? I'm not saying that led to the bricking...but it probably didn't help.
Click to expand...
Click to collapse
Everyone expects everything to be instant these days... "Uh oh! The screen isn't doing anything, it's been at least 20 seconds! I could just wait and leave it for a few minutes like all the guides say to do. Or I could take my battery out...how could that hurt, right?"
For me it took a good 3-4 minutes on the screen with the arrow and the box.
Anyways, if you can't get to the recovery then you might be buying a new N1.
ahh it took like 5 minutes for me, I have to admit I was a little worried since you dont see status bars or anything, but like said, the guides warn for this.
I cant imagine that removing the battery broke it though, he should be able to load a recovery image
I feel sad for him so bumping
Bleh. I'll just have to wait and see. I'll contact HTC.
tomsan84 said:
ahh it took like 5 minutes for me, I have to admit I was a little worried since you dont see status bars or anything, but like said, the guides warn for this.
I cant imagine that removing the battery broke it though, he should be able to load a recovery image
I feel sad for him so bumping
Click to expand...
Click to collapse
If you remove the battery during the period he did, which is when the phone is actually flashing the radio ROM, yes removing the battery can and likely did break it for him. There are 2 ways to brick an Android device, while flashing a radio ROM and while flashing an SPL...
OP, have you tried any of the button combos we have recommended? Have you tried putting your battery in the phone, then without turning it on, putting it on the charger to see if it can charge the battery at least (you said it wasn't even turning on, which is likely because you have a dead battery)... charge the battery first, then try the button combo's we recommended.
And please, when you report back, and not to sound like an ass, do so clearly and systematically (I can't tell from your posts what did or didn't happen, and whether you tried anything we suggested, nor what the current state of the phone is)... so, please use this format to make it clear to us trying to help:
Battery: Charged or Wouldn't Charge (LED will come on if it is charging)
Trackball+Power: Booted into boot loader, yay! or Went to the damn box
Volume down+Power: Booted into fast boot! or Went to the damn box
And remember, you have to hold down the button, either trackball or volume down, then press the power and keep holding down the trackball or volume down until it either goes to boot loader or it goes to the box screen... you might want to even wait for a minute on the box screen(if it goes to that) while holding down the button to make sure it can't get into boot loader...
Okay so I took the battery out, put it back in, and tried charging it. The Battery LED did not come on, so I'm guessing it's not charging.
The Trackball+Power did not work.
The Volume down+Power did not work.
I think I most likely broke it, due to the fact that I took the battery out while it was flashing the radio ROM onto the phone. I kinda did it on a impulse, which is my fault. So do you think it'd be possible if I did contact HTC they'd send me a swap, and not be able to make my phone work or turn on, and everything will go on as if I "broke" it and not unlock it or anything?
Jackasaur said:
Okay so I took the battery out, put it back in, and tried charging it. The Battery LED did not come on, so I'm guessing it's not charging.
The Trackball+Power did not work.
The Volume down+Power did not work.
I think I most likely broke it, due to the fact that I took the battery out while it was flashing the radio ROM onto the phone. I kinda did it on a impulse, which is my fault. So do you think it'd be possible if I did contact HTC they'd send me a swap, and not be able to make my phone work or turn on, and everything will go on as if I "broke" it and not unlock it or anything?
Click to expand...
Click to collapse
It sounds like you have a true brick... disruption of the radio ROM flashing causes lots of bricks, and did so for you.
It is pretty common, at least with T-Mobile with the G1, to call them up and tell them your phone asked you to update, and while updating it froze and won't turn on or charge anymore. Not sure if HTC will handle it the same as T-Mobile did, but if they do they will just send you a new unit, you send the old one back, and you are back up and running... they might ask that you send it to them first, but there is no way for them to test if it was rooted/unlock boot loader if it can't be powered on, so you should be fine.
Sweet. So I called HTC, and they said they'll repair it, but I asked for a swap instead, so I'll be getting one by either Wednesday, or Thursday. Good stuff! I'll tell you all how it goes. :] Now I am stuck with my Nokia N95. Thanks for all your help.
Did you tell them you have an unlocked bootloader?
uansari1 said:
Did you tell them you have an unlocked bootloader?
Click to expand...
Click to collapse
he doesnt have 2 tell em
lightforce said:
he doesnt have 2 tell em
Click to expand...
Click to collapse
Yeah, he doesn't have to tell them... but they don't have to cover his phone either.
If they find out it's unlocked after the fact, they can charge you to repair the phone.
How exactly will they know he unlocked the bootloader if the device cannot even properly turn on, unless htc has other methods of being able to "restore" the phone, then he should be rather ok. Am I not looking into this deeply enough? Can the phone turn on with a new battery or something? Does HTC have alternatives ways of checking?
Eclair~ said:
How exactly will they know he unlocked the bootloader if the device cannot even properly turn on, unless htc has other methods of being able to "restore" the phone, then he should be rather ok. Am I not looking into this deeply enough? Can the phone turn on with a new battery or something?
Click to expand...
Click to collapse
That's my point man.. I don't know. All they have to see is that open padlock and they can deny the claim.
I'm not positive what exactly happened with my phone, I was syncing up my info so that I could flash a new rom and after it had all finished, my phone had froze. So I attempted to restart my phone and now it doesn't turn on unless it is connected to a source of power (charge/cpu). It attempts to start up and gives me the standard t-mobile load up logo and recognizes the rom and radio but then continues to restart itself. Any suggestions on how to fix this?
Hmm just boot it into bootloader mode, run a task 29.. and flash a new rom of your choice.it might work..
to get into boot loader hold down volume down while pressing power..
Thanks. I tried and it was successful without a SIM card but when I put it back in, the same thing started happening again so I tried with the SIM card and no luck. I'm still getting the T-Mo start up and restarts itself over.
check the battery connectors.more than one person has bent one of them when pulling the battery with pretty much identical results that you are seeing.
if you have been using the push reset button make sure it hasn't caught under the body and is staying pressed.
it was the battery connectors, just had to push the battery in a different way. thanks a lot for the help.
samsamuel said:
check the battery connectors.more than one person has bent one of them when pulling the battery with pretty much identical results seals you are seeing.
if you have been using the push reset burin make sure it hasn't caught under the body and is staying pressed.
Click to expand...
Click to collapse
good call Sam, I was thinking the same thing. I guess we can add one more to the list where that was the root issue
I'm wondering how many more people are having unresolved issues where this is the cause...I'm gonna start including it in my regular troubleshooting steps for all reboot-loop issues at least
my focus has gone crazy. it keeps beeping like i received a text message. i try to lock the screen and it goes black for 5 seconds, then immediately lights up and dings like i have a text message. from there it dings constantly. there are no pauses, just ding, ding, ding, ding. you get the picture.
battery drains within an hour due to this. i've reseated the battery, restarted, even did the full reset. nothing has changed. i did the nodo update manually before it became available via the xda update about 6 weeks ago.
does anyone know what's going on....has this ever happened to anyone before? i bought the phone in november...can i warranty it or go to att and switch out?
First thing, you have a couple of options. Any product that you buy in an att store has a warranty on it for a year: phones, cases, chargers, anything. Second thing, I can't say that I have or have heard many instances of whats going on with your phone. The easiest way to deal with this is to go to att tell them whats happeneing and tell them you would like a new phone. The other option is to do another full recovery but do it with the diagnosis app; the diagnosis codes are located in the thread in the general section of the focus forum. Another option is to use one of the official roms from the development section and reflash the rom. So, all in all I think you might of had a faulty update manually updating to nodo. Also, I would try updating through zune the official att/micorsoft nodo. The last thing I assume your focus was unlocked. If you flash the official rom from the development section it flashes, I think, to 7004 version and you can unlock your phone again, prevent the unlock to nodo, so on and so on. Good luck
tuffluck said:
my focus has gone crazy. it keeps beeping like i received a text message. i try to lock the screen and it goes black for 5 seconds, then immediately lights up and dings like i have a text message. from there it dings constantly. there are no pauses, just ding, ding, ding, ding. you get the picture.
battery drains within an hour due to this. i've reseated the battery, restarted, even did the full reset. nothing has changed. i did the nodo update manually before it became available via the xda update about 6 weeks ago.
does anyone know what's going on....has this ever happened to anyone before? i bought the phone in november...can i warranty it or go to att and switch out?
Click to expand...
Click to collapse
okay so the problem now is that the device is not being recognized via the usb port. it reads "one of the devices connected via usb has malfunctioned and is not recognized." does anyone know what is going on???
i think before i did a full reset on the phone, it was programmed to tether. when i reset it, would it revert back to tethering or sync with zune? either way it has never been showing as malfunctioning in windows, so something is definitely wrong. should i do a complete reset using the diagnosis app? i don't know how to do that, but might it help?
does anyone know why i am getting "device has malfunctioned" warning?
tuffluck said:
does anyone know why i am getting "device has malfunctioned" warning?
Click to expand...
Click to collapse
Your going to need to put it in download mode and reflash the original firmware you can do that and download all the tools in this thread.
bsbokc said:
Your going to need to put it in download mode and reflash the original firmware you can do that and download all the tools in this thread.
Click to expand...
Click to collapse
And if that doesn't work (might not, considering the USB issue) you will have to go warranty...
okay thanks for the help. i decided to go back to ATT and they replaced it for no charge. it was an easy fix, BUT i tried to buy a new micro sd card from microcenter, and the phone will not recognize it at all. is this pretty normal to happen?
ATT put the memory card from the old phone into the new phone without my permission. obviously it did not work, but i'm wondering if them putting it in the new phone at all might cause the memory slot to go awry and not read any new card?
You have to do a hard reset to initialize the sd card. Once you do this, it's not removable
Sent from my SGH-i917 using XDA Windows Phone 7 App
so i turn the phone off, put the card in, turn the phone on and go into settings and do a hard reset, and then it should be good to go?
tuffluck said:
so i turn the phone off, put the card in, turn the phone on and go into settings and do a hard reset, and then it should be good to go?
Click to expand...
Click to collapse
No, turn on the phone with the 3 buttons method, or read here about all the methods:
With the phone off, hold down the Power button, volume down button, and camera button and when the screen turns on, release power button, then the other 2.
You will be asked to press Win to continue, twice (hard reset).
So there is a guy in my town selling a bricked G2, his ad says "was trying to root my LG G2, Now it wont turn on or anything, even when I try and charge it or plug it in. No idea what do to but dont have time to figure it out and needed a phone for work so have already replaced it."
I don't have one of these phones or know anything about the specifics of rooting them or installing ROMs on them, but I have installed them on my own phone (Optimus G) as well as bricked my own phone a number of times and fixed it.
My main question is, if this guy isn't lying and he didn't just drop it in a toilet and dry it out or something like that, is it possible for rooting or installing a ROM or whatever to completely brick it beyond repair? Or if I hop on IRC and get the necessary tools should it be fixable even if its a slight pain in the ass?
I found with my phone no matter how bad I had messed up there was always LGNPST with the stock software to fix it, so I figured it would be similar for this phone but I wanted some more opinions on it, thanks for the help and sorry for my lack of knowledge.
There are a couple of ways of hard bricking g2s so I'd be really careful with this one. If it won't even light up he might be in qhsusb bulkmode or something. Ask him to let you play around with it, if it goes in download mode and pc recognises it you should get it. If he didn't drop it in the toilet of course.
If the phone wont do a Factory Reset, Vol - and power then at the LG logo let go of power then hold again. I would stay away.
My LG G2 was totally dead that I couldnt get it to boot, download mode, factory reset, or even show the battery charging screen when it was off.
Good thing I was under warranty.
daytonasportster said:
If the phone wont do a Factory Reset, Vol - and power then at the LG logo let go of power then hold again. I would stay away.
My LG G2 was totally dead that I couldnt get it to boot, download mode, factory reset, or even show the battery charging screen when it was off.
Good thing I was under warranty.
Click to expand...
Click to collapse
how did you go with replacing it? like what did you tell them?
idonttakedrugs said:
how did you go with replacing it? like what did you tell them?
Click to expand...
Click to collapse
The "truth" I took an OTA and it died. I IM'd with tech support and after me telling her its DEAD she wanted me to go to settings, general.... I said its DEAD. So we tried the 2button method and when that didnt work she promptly arraigned to FedEx me a new one.
daytonasportster said:
The "truth" I took an OTA and it died. I IM'd with tech support and after me telling her its DEAD she wanted me to go to settings, general.... I said its DEAD. So we tried the 2button method and when that didnt work she promptly arraigned to FedEx me a new one.
Click to expand...
Click to collapse
how did it die may i ask? did your phone crash during the update?
idonttakedrugs said:
how did it die may i ask? did your phone crash during the update?
Click to expand...
Click to collapse
It started to process the update, rebooting and stuck. All I could get it to do was show the LG logo if I power cycled it or plugged it in the usb or charger. 2finger factory reset would show the screen but never start.
daytonasportster said:
It started to process the update, rebooting and stuck. All I could get it to do was show the LG logo if I power cycled it or plugged it in the usb or charger. 2finger factory reset would show the screen but never start.
Click to expand...
Click to collapse
alright mate im gonna say that
I've had this Motorola Droid RAZR for like two years now and a friend of mine took it and worked on it, adding something called "Cyanogen Mod" and he 'rooted' it I believe? Ever since, phone has worked great. However, today I tapped the home button and the whole screen had a weird visual glitch where the wallpaper was entirely intact but the icons and such were only half appearing, like someone scratched them out with fingernails or something. It would go away and come back so I got frustrated and rebooted my phone. It starts up normally and goes to this screen where you can do different stuff with Cyanogen mod (like changing the rom? or changing boot options) and usually I just continue past that because for 1) I know nothing about it and 2) It always was fine. But when it did the typical boot up, it just skipped back to the first screen you get when you turn the phone on and repeats. It never goes to the second part of the Cyanogen Mod where the words appear and the little thing spins, it simply skips back to the screen you get when you power up and repeats. It keeps doing this and I looked online how to fix it, tried about twelve different things (like restoring different aspects and using different roms or making new roms) and it just didn't work. Eventually it got bugged out where the screen was just black, couldn't get it to do anything but reboot and go back to black. I let it sit until the battery ran dry I believe and now I'm at a brick wall.
Is there a way I can totally just revamp and start fresh? Like remove all of it and reinstall Cyanogen mod/the OS and all that jazz? I don't mind losing everything if I can just keep the phone, I don't pay for a cellphone and I don't want one I just use the droid for texting apps/games/reddit/etc. If anyone could help me save this thing I'd appreciate it.
Hi there,
Please stand by until mods will move this thread to the related forum for Droid RAZR.
For reply or ask other questions you must register an account.
Stand by
Hello? Can Somebody help me out, I've waited a couple days now and no one has said a thing?
You have safestrap installed, correct? If so, what version?
Dr. Mario said:
You have safestrap installed, correct? If so, what version?
Click to expand...
Click to collapse
How would I know if I had it installed? I remember when I booted up the phone something came on with a picture of a little robot that said "Safestrap Enabled" and then when I had this problem it was saying "Safestrap Disabled". I can't get the phone to turn on right now though, is there a way I can check what version I have another way?
Ah. I see. First. try entering Safestrap menu upon rebooting, instead of allowing it to boot normally, and look at ROM slot and see if custom OS' ROM slot is active. If it's there and is not active try reactivate it. If it won't budge, get microSD card and find XT910 (RAZR - spyder) CM 11. If you don't know what to pick, I will look in a bit.
Dr. Mario said:
Ah. I see. First. try entering Safestrap menu upon rebooting, instead of allowing it to boot normally, and look at ROM slot and see if custom OS' ROM slot is active. If it's there and is not active try reactivate it. If it won't budge, get microSD card and find XT910 (RAZR - spyder) CM 11. If you don't know what to pick, I will look in a bit.
Click to expand...
Click to collapse
Just tried booting it up, nothing is working I think the phone is dead. I plug it into the charger and only the notification light on the top left goes on a blueish white and stays on as long as it is plugged into the charger. Nothing will turn on at all and the phone doesn't seem to respond to anything. Is my phone just dead..?
Soft bricked. Try pushing both volume down and up button while plugged into either computer or charger, and hold down power button until it boots. I hope you won't need to buy Motorola factory cable at this point.
Let your device charge for a few hours until it boots up. Then boot it into APfastboot and flash the stock firmware with RSDLite.
ATTACK said:
Let your device charge for a few hours until it boots up. Then boot it into APfastboot and flash the stock firmware with RSDLite.
Click to expand...
Click to collapse
In English please?
Edit: Just plugged it in like you said and instantly the boot screen came on rather than simply that silly light so I think my phone is improving but I still would like to entirely revamp it or redo it or whatever you wanna call it so that everything is fresh and new and my phone is okay.
Good. I think it could be because the battery died somehow. Good thing the protection mechanism on the bootloader didn't have the wild idea of disabling the phone.