Database Users

My Device is done. please help.

i have to have the worst luck in the world..
got my nexus one today. condition is MINT. seller also included the receipt from HTC proving that it got replaced.
popped in my sim, everything worked fine. turned it off to swap batteries and thats when the hell started.
im not able to get past the nexus logo. NOTHING. it would turn on, than go to the screen, vibrate, than repeat multiple times. phone has never been rooted.
i did EVERYTHING. i did the volume down plus power and than i cleared wiped the memory, same result.
than i tried downloading 2.2.1, renaming it to update.zip, put it on my zip, but that doesnt work. the phone can't tell theres a update.
like **** man. i than went here
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials
read that i needed FRG33 and rename it to PASSIMG.ZIP. when the phone turns on, it gives me the message if i want to update, i get excited. i click yes, everything says ok, than i reboot and bam, still endless reboot. tried to do the passimg again but this time i get a fail on radio V2 or something like that.
WTF is going on. i didnt do anything. ANYBODY HELP?

maybe the battery you swapped in is bad?

same result with both batteries :/
i hate my effing luck.

Make sure your batteries are fully charged, seriously.

great, now when i click recovery, it doesnt even go to the android guy with the exclamation mark, it just gets stuck at the logo. all im able to do is get to hboot. WTF.
i mean the battery has half a charge. just checked with my desire. i even tried with it plugged in in the wall. nothing.

my aim is screwupboy444. your welcome to help me there or even laugh at me for being a bone head and getting in this situation.

Do you have a different SD card you can use?
Sent from my Nexus One using XDA App

yeah, i was using both the desire 8gb and the nexus one 4gb. both were reading fine in the desire. i read that if it gets to the nexus one logo then my phone isn't bricked, but im starting to think otherwise. nothing works.
ive been searching for the past hour half. everyone seemed to have fixed there by doing the passimg method or wiping data. but unfortunately none of that is working. i tried placing the froyo "update.zip" and running it but when i clicked recovery, it went into the boot cycle again.

http://forum.xda-developers.com/showthread.php?t=614850
thinking about doing that but i have a feeling it doesnt apply to me. that and i don't understand any of the process. i dont think my phone will even be read by my comp.

did the passimg for the third time. went past the logo and actually to the set up screen. than it rebooted again. and now its stuck on the nexus one logo again.

could it actually be that? i left the battery charging in the desire for about 40 minutes, than took it out and put it in the nexus one and actually got to the set up screen for the first time.
but my question is, if thats the solution, does that mean my phone is gonna trip out everytime its less than 60 percent battery power?

this is what i get when i put the 2.2.1 update on my sd card and go into recovery mode
Uploaded with ImageShack.us
most of the threads where people got this fixed required them unlocking the bootloader and doing something. im the second owner of the phone but would like to avoid rooting but if its required in this situation, i will. i just need a dummies guide to do it..

No, there's threads for recalibrating the battery, if needed.
Keep it fully charged, and see if it will run for a reasonable period... That way, we can see if it really is the battery...
Sent from my Nexus One using XDA App

Don't worry about the exclamation and Android for now, and see if the phone will boot and run with a fully charged battery...
Sent from my Nexus One using XDA App

frick, i know thats what i should do. it just blows that i got this today and theres already a chance that its trashed...

danger-rat said:
Don't worry about the exclamation and Android for now, and see if the phone will boot and run with a fully charged battery...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
thanks for all the help man. you dont think i need to unlock the bootloader right...? im just more curious on why the desire can work with either party no matter the charge. damn.

Wait until your battery is about 75% or more would be better, then try the passimg again...
Sent from my Nexus One using XDA App

not sure if its good news or not but (i apologize for my lack of patient before hand haha), i took out the battery the desire was charging again and put it in the nexus one. it got to the set up screen all three times before it resets again. i tried plugging it in the wall charger but it still resets at that area.
edit:
the battery level was at 74% when i tried it.

75% is not a hard number, and I'd let it charge as much as possible. I'd also quit switching batteries, and just stick with one until you isolate the problem...
Sent from my Nexus One using XDA App

danger-rat said:
75% is not a hard number, and I'd let it charge as much as possible. I'd also quit switching batteries, and just stick with one until you isolate the problem...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
oh iam. im charging the nexus one battery in the desire because once i turn on the nexus one, it gets frozen there, and than i cant turn it off.

[Q] Doesn't boot past Motorola logo. Help, anyone?

Hi, yesterday I installed CM7 on my android, all went well, very awesome.
Soon the LED Light messed up when I would plug the phone in via usb.
The LED had colors that were like mixed and all.
Searched on Google, and found nothing... So I then did the whole process over (wiped data...) And near the last step I wiped data instead of wiping cache.
It was like 5 in the am and I got sleepy so when I restarted the phone(Of course it would take a while), I went to lie down, then fell asleep. Woke up and my phone was still at the Motorola Logo screen. I also seen that I forgot to put it on the charger before went to sleep.
Long story short, My phone won't get past the logo screen, I would try to go back to 2.2 sbf but when I get into the bootloader screen the battery low cannot program.. error comes up.
Yeah, I explained practically everything..
What can I do to get it back to normal, so I can get CM7 back?
I only got to enjoy 20 minutes of the rom...
My phone: Motorola Bravo
Service: AT&T

You need to charge your battery some how? Does it charge at all
Do you know someone with phone?
If not ask for a battery replacement from at&t store and hope it has enough charge
Sent from my MB525 using XDA App

rdannar said:
You need to charge your battery some how? Does it charge at all
Do you know someone with phone?
If not ask for a battery replacement from at&t store and hope it has enough charge
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
My thought on charging was when the phone is off and you charge it, it goes to the charging screen, then eventually the display turns off.
Instead of that, it just stays at the Motorola Logo screen..
I've also had it on the charger for about 4 hours now. Still remaining at the logo screen, BUT it has also gotten warm..Maybe that means its charging? (right??)
2. Since I've moved, nope. Don't know anyone that has this phone and is near me.
3. Battery Replacement. It's 1am here so, I guess I'll just keep it on the charge till the morningmorning..
I could do the bootloader sbf back to froyo thing but since the phone's battery is dead to the max, I get the error, meaning I can't do that option.
I'll call my local AT&T store to see if I could get a battery replacement if I can't get it to turn on to at least the Recovery or bootloader.
Pain.. pain in my brain.

try to get it plugged in w/ no logo, to ensure it's off off... if not you might have to let it sit off the charger till it's dead enough that it doesn't try to boot...
i think it's trying to boot, but boot looping and not aquiring enough of a charge,
do you have it on a wall charger? make sure it's like 800 mah or higher, i think the phone comes with a 5.1v 800mah which was weird to me tha tit was 5.1 cause all other phones are 5.0 but anyway maybe you're not getting enough of a current to it to overcome the drain from the bootloop?
Are you able to get into custom recovery? (Do you see the blue LED at any point when the phone begins to try to power on?)

You have soft bricked your phone, so the only way to get it working is to sbf back to 2.2. The problem is, the bootloader doesn't allow you to sbf if your battery is below a certain point. You need to either get that battery charged or get a new one.

If you can't get anything at your store, I will cross-ship/trade you a charged battery (1 year old) for your current one and $3 for shipping? Let me know if you'd be interested in something like that...
I also bought a battery from Amazon (OEMShop or something), and I think it came 40%ish charged... You could try your luck?

Just so you understand the charging, Android uses the OS to monitor the charging. If the phone is bricked it doesn't charge… plain and simple. It sucks if you try to sbf after the battery is drained, but the only thing you can do is get another one. Hope your search for one comes up well.
Sent from my MB525 using XDA App

dontbejeff said:
Just so you understand the charging, Android uses the OS to monitor the charging. If the phone is bricked it doesn't charge… plain and simple. It sucks if you try to sbf after the battery is drained, but the only thing you can do is get another one. Hope your search for one comes up well.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Yeah..no.. I'll be getting a replacement phone (same one). Basically in 4 to 6 days..
I'm so happy, my phone kept restarting anyway when using data.. But yeah, thanks though.

Before you send other phone back... sbf with other battery back to stock.
AndroidRocksSocks said:
Yeah..no.. I'll be getting a replacement phone (same one). Basically in 4 to 6 days..
I'm so happy, my phone kept restarting anyway when using data.. But yeah, thanks though.
Click to expand...
Click to collapse
Sent from my MB525 using XDA App

rdannar said:
Before you send other phone back... sbf with other battery back to stock.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Yeah, I thought of that when I got of the phone with them. Thanks for the heads up though!

My replacement phone came in the mail earlier this afternoon! Thanks for all the help you guys. Glad I came here. So excited, just 10% more and it's fully charged.

I think I may get a extra battery just in case for my phone. Great post!

This just happened to me too. I thought what to do...
Spliced one of my old car phone chargers and hooked it to my phone battery... plugged it into my car fir 5 minutes and was charged enough to sbf.
Don't recommend it if you don't know what your doing
Cheers
Sent from my MB525 using XDA App

rubbachicken said:
try to get it plugged in w/ no logo, to ensure it's off off... if not you might have to let it sit off the charger till it's dead enough that it doesn't try to boot...
i think it's trying to boot, but boot looping and not aquiring enough of a charge,
do you have it on a wall charger? make sure it's like 800 mah or higher, i think the phone comes with a 5.1v 800mah which was weird to me tha tit was 5.1 cause all other phones are 5.0 but anyway maybe you're not getting enough of a current to it to overcome the drain from the bootloop?
Are you able to get into custom recovery? (Do you see the blue LED at any point when the phone begins to try to power on?)
Click to expand...
Click to collapse
Volume up... not down... got it

(Update: I Managed to recover) My N4 is bricked! Anyone managed to recover?

Hello everyone
I installed AOKP and was running CF-BENCH, no OC or UV. The device got very hot it shut down and can no longer start it or charge, all i get is the LED flashing red.
I managed to get into Bootloader but once i remove the usb cable the device shuts off, i flashed factory image and re locked the bootloader to no avail. i think thermal throttling got over ridden somehow.
Has anyone recovered from this, or should i go RMA?
thnx
Update------
I tried everything, i even got the weird LG download mode. finally i plugged the device to the PC (PC was off) and went to sleep, when i woke up the LED no longer flashed red and the device was running normally.

ragiut1 said:
Hello everyone
I installed AOKP and was running CF-BENCH, no OC or UV. The device got very hot it shut down and can no longer start it or charge, all i get is the LED flashing red.
I managed to get into Bootloader but once i remove the usb cable the device shuts off, i flashed factory image and re locked the bootloader to no avail. i think thermal throttling got over ridden somehow.
Has anyone recovered from this, or should i go RMA?
thnx
Click to expand...
Click to collapse
Ugh "thermal throttling"...
I hate that term and how people are really over doing it on it on this device.
If you followed the ROMS OP instructions one by one perfectly, I don't see how you ran into that issue.
If anything, let it cool down, give it a day, and see what happens.
Sent from my Nexus 4 using xda app-developers app

Do a search I know there is a couple of threads that mention how to fix the red LED of death.
Sent from my Nexus 4 using Tapatalk 2

Reminds me of a ps3 yellow light error.. Once its over heated it wouldn't turn on again until it was opened.. I never run benchmarks so I'm lucky lol
Sent from my Nexus 4 using Tapatalk 2

ATM, no hope 4 you. I used to be in your situation and i had to send it back to GG. RMA time!

Thnx everyone
They must've known that over heating bricks the device ,that's why they implemented thermal throttling

This is strange though as you didn't oc
Sent from my Nexus 4 using Tapatalk 2

italia0101 said:
This is strange though as you didn't oc
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I was thinking the same thing.. I'm running aokp as well, starting to worry a little..
Sent from my Nexus 4 using Tapatalk 2

I mean at stock there's no way it should fail unless it was already on the edge ... What kernel was it using ?
Sent from my Nexus 4 using Tapatalk 2

Update------
I tried everything, i even got the weird LG download mode. finally i plugged the device to the PC (PC was off) and went to sleep, when i woke up the LED no longer flashed red and the device was running normally.

ragiut1 said:
Update------
I tried everything, i even got the weird LG download mode. finally i plugged the device to the PC (PC was off) and went to sleep, when i woke up the LED no longer flashed red and the device was running normally.
Click to expand...
Click to collapse
what I want to know is how you could possibly sleep knowing your brand new nexus 4 is bricked!

Mohit12 said:
what I want to know is how you could possibly sleep knowing your brand new nexus 4 is bricked!
Click to expand...
Click to collapse
I gave up on it actually, and was going to ship back the next day

[Q] Phone Turned Off By Itself (Red LED flash)

So I just beat DeadSpace (yay), then I decided to reply on a harder difficulty. Within 15 minutes the phone turned itself off and the LED flashed RED once really briefly. Now it won't power on at all. The issue just happened, I don't know what's up.
I hope it isn't in the untouchable state (soft-bricked) again...................... Of course this stuff happens to me at this time in the night when nobody is awake to respone ......... What do I do? How can I fix it?
If it fixes itself I'll let you know.... I know for sure that I'm not playing Deadspace again after this...
EDIT 1* Just unplugged the charger and popped it into another wall. Now the Red Flash is just staying on, the phone is plugged in. What's going on?.......
EDIT 2* The Red LED stopped, phone still won't power on
EDIT 3* The phone now shows the low battery screen while being powered off... I'm guessing it'll power on now
EDIT 4* The phone successfully powered on, nothing is wrong with it now
Sorry for posting this thread it seems like a waste now..
Soooo! To make it not so pointless, I think I found out why it does this. I think Deadspace drained more battery than the phone could charge so the phone died (battery drain) with no warning. And when it did die the phone was in a state of "what the heck - - - computing - - - enjoy this RED LED!!!!!!". I guess it just means "Super dead battery". So in case anybody else fears for their $500 investment, just give it 10-15 minutes before you panic, and let your phones actually charge

From what I can gather from the various threads about the "Red Led Of Death" is that if it's flashing - it's recoverable in some way, if it's just a solid glow you're SOL. I've spent the last 2 days trying to get my N4 to live again Would actually help if people where more specific about if it's flashing or not.
Just got off the phone to the Play Store and arranging for them to start the RMA process. I guess I'll find out in a couple of weeks what the problem is.

When I first rooted I had the light for 4 hours, got it in and out of the red LED state 3 times that night. It was a horrifying experience. I do not know how I fixed it. I was jamming buttons and eventually got into the boot loader mode, from there I flashed stock boot.img and the rest is history... I wish you luck!!!
Sent from my Nexus 4 using xda app-developers app

I've read it has something to do with the stock charger..

calanizzle said:
I've read it has something to do with the stock charger..
Click to expand...
Click to collapse
I wasn't using the stock charger
Sent from my Nexus 4 using xda app-developers app

My Nexus 7 is doomed...

A few weeks ago, i flashed a stock rom on my wifi nexus. I was happy with it until last week. Charging became incredibly slow - 30% over 8 hours. I threw it in my bag and wheb i got home 8 hours later, the battery was depleted completely. I couldn't turn it on. I plugged it in over night and it stayed at zero percent. I booted into recovery and reflashed my stock rom abd wiped my data. Still didn't charge. I tried going into my bootloader and hitting power off and then plugging in, but it still wouldn't charge. I can't flash my backup because it's on my card that i lost, and even if i had it, i wouldn't be able to keep it on long enough to flash it. ADB won't run on my pc and i don't know how to use the program anyway. What can i do to save my device? Please help.....
Sent from my YP-G1 using xda app-developers app

Replace battery?

veeman said:
Replace battery?
Click to expand...
Click to collapse
Not the average flasher knows how to tear apart a device - including myself. Anyways, this thing won't power up at all? You tried leaving it plugged in and booted into bootloader? If so, sounds like a hardware issue or the battery is defective.

I would be willing to bet that your battery connection came loose. Start at your USB port with a thin piece of plastic, such as a guitar pic. Work your way around the device and remove the back.
Sent from my Nexus 7 using xda app-developers app

DroidOnRoids said:
Not the average flasher knows how to tear apart a device - including myself. Anyways, this thing won't power up at all? You tried leaving it plugged in and booted into bootloader? If so, sounds like a hardware issue or the battery is defective.
Click to expand...
Click to collapse
It's not too difficult. iFixit has a good tutorial on it. http://www.ifixit.com/Guide/Installing+Nexus+7+Battery/9895/1

happyjack96 said:
A few weeks ago, i flashed a stock rom on my wifi nexus. I was happy with it until last week. Charging became incredibly slow - 30% over 8 hours. I threw it in my bag and wheb i got home 8 hours later, the battery was depleted completely. I couldn't turn it on. I plugged it in over night and it stayed at zero percent. I booted into recovery and reflashed my stock rom abd wiped my data. Still didn't charge. I tried going into my bootloader and hitting power off and then plugging in, but it still wouldn't charge. I can't flash my backup because it's on my card that i lost, and even if i had it, i wouldn't be able to keep it on long enough to flash it. ADB won't run on my pc and i don't know how to use the program anyway. What can i do to save my device? Please help.....
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
Sounds like my device... only I even can't get into the bootloader nothing... Someone suggested that the battery got so far depleted that it will nor recharge.
However seems you at least can run the bootloader... for me it just stays black ..... nothing nopes nadda

dkd2625 said:
Sounds like my device... only I even can't get into the bootloader nothing... Someone suggested that the battery got so far depleted that it will nor recharge.
However seems you at least can run the bootloader... for me it just stays black ..... nothing nopes nadda
Click to expand...
Click to collapse
Actually, there's a sticky for these issues haha
N7 Turns Off/Won't Turn Back On/Battery Status Issues - The Fixes **UPDATE**...
---------- Post added at 11:28 AM ---------- Previous post was at 11:27 AM ----------
veeman said:
It's not too difficult. iFixit has a good tutorial on it. http://www.ifixit.com/Guide/Installing+Nexus+7+Battery/9895/1
Click to expand...
Click to collapse
I heard that was a good site. I'm more scared of screwing up any hardware than doing the actually tearing apart.

I can boot for like 30 seconds and then it shuts off. I've tried the solutions in the thread link above; however, i still think it is a software issue. I've used other roms that had really slow charging, but i was able to switch to another one before the battery got depleted. So i think my best bet is to somehow get a new rom on my device somehow. ADB won't run on my computer. It just flashes a command prompt on the screen for like half a second and closes.
Sent from my YP-G1 using xda app-developers app

happyjack96 said:
I can boot for like 30 seconds and then it shuts off. I've tried the solutions in the thread link above; however, i still think it is a software issue. I've used other roms that had really slow charging, but i was able to switch to another one before the battery got depleted. So i think my best bet is to somehow get a new rom on my device somehow. ADB won't run on my computer. It just flashes a command prompt on the screen for like half a second and closes.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
What kernel are you on? The kernel is what does the charging operations.

happyjack96 said:
I can boot for like 30 seconds and then it shuts off. I've tried the solutions in the thread link above; however, i still think it is a software issue. I've used other roms that had really slow charging, but i was able to switch to another one before the battery got depleted. So i think my best bet is to somehow get a new rom on my device somehow. ADB won't run on my computer. It just flashes a command prompt on the screen for like half a second and closes.
Click to expand...
Click to collapse
I had a similar situation in that after the battery died, I got it to the point where I could boot up, but after a screen timeout, it would be dead again. Finally, I got it booted again (while plugged into power) and immediately went to developer options and checked the Stay Awake, never sleep while charging. Keeping the screen awake kept the N7 on and it charged up.

Funny my Galaxy Nexus started doing this crap on me too after I updated the rom and kernel. The phone and battery are only 2 months old replaced in April.
Occasionally it won't take a charge. I have to **** with the battery, removing it several times. Then all of a sudden it starts charging again after 10-15 resets.
Haven't had a problem in a while. Typically hits me like every 2 weeks.
No problem on N7 though but it happens. First thing is to change your kernel and rom to something else. If still draining, flash stock and relock, unlock, relock, wipe. Boot, upgrade to 4.2.2 and test.
Sent from my Nexus 7 using XDA Premium HD app