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.

Help mytouch 4g not turning on

Hello there today my phone stop working all i did was remove the battery and remove the sim card to put a new one in. When i put it back on and turn on the phone, the phone vibrates for three times and the charging led starts blinking ,also the screen is black. I cant even get into bootloader mode anyone knows a fix. I was running Ossymod MIUI and have an engineer boot loader.
Did i mention that this happened because i pull the battery out while phone was on this could be what f*ck it up.
Problem
Phones off --> Hit the on button---> Three Vibrates with black Screen ----> Orange LED Blinking.
Things i tried
Try to get into Fast boot but i only get a black screen with a Green Led while connected to the pc, Device manager detects my mytouch as a "Qualcomm CDMA Technologies MSM".

i thought i posted this on Q&A can some move this to Q&a Section

Me the issue I may br - able to help or post it here mine does that
Sent from my HTC Glacier using XDA Premium App

Does it turn on atall ??
Sent from my HTC Glacier using XDA Premium App

pbedard said:
Me the issue I may br - able to help or post it here mine does that
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Huh?
Sent from my demonSPEED Glacier using XDA Premium App

thederekjay said:
Huh?
Sent from my demonSPEED Glacier using XDA Premium App
Click to expand...
Click to collapse
At least he tried? To the OP, sounds to me like your battery was probably almost dead before you took it out. Try charging it before you try turning it on again...

battery had 50 percent im trying to get it on fastboot by holding the power and volume down while connected to the pc but all i get is a black screen and in my pc it shows "Qualcomm CDMA Technologies MSM" could this have been cause ,by pulling the battery while the phone was on.

jeff7790 said:
battery had 50 percent im trying to get it on fastboot by holding the power and volume down while connected to the pc but all i get is a black screen and im my pc it shows "Qualcomm CDMA Technologies MSM" could this have been cause ,by pulling the battery while the phone was on.
Click to expand...
Click to collapse
I dnt believe that pullin the battery while the phone is on would cause that issue,ive dropped my phone numerous times while it was on,while playin a game or by just gettin out my car while listenin to music & not once had that issue...
Mytouch 4g-white
Permrooted s-off
Root Method-gfree
CWR-3.0.2.4
Rom-Royalginger v2.1
Kernel-Ckisgen~smartass~v1.2

I cannot figure out how you got to this point, but I think you have a bad radio.
That Qualcomm MSM device is something that I think happens only with the engineering bootloader installed. I believe it could provide a way to access the radio directly, but I have never seen any info on how to do that.
I mistakenly flashed the wrong data to the radio partition while I was trying to reset to factory and since I had the engineering bootloader, I got the same results as you. As a result, mine was effectively bricked and I had to return it to T-mobile like that. This was a couple of months ago and I have not heard anything about it.

G8351427 said:
I cannot figure out how you got to this point, but I think you have a bad radio.
That Qualcomm MSM device is something that I think happens only with the engineering bootloader installed. I believe it could provide a way to access the radio directly, but I have never seen any info on how to do that.
I mistakenly flashed the wrong data to the radio partition while I was trying to reset to factory and since I had the engineering bootloader, I got the same results as you. As a result, mine was effectively bricked and I had to return it to T-mobile like that. This was a couple of months ago and I have not heard anything about it.
Click to expand...
Click to collapse
Ever since I've had this phone i never try to flash radios or beta test radios i always kept it stock . The only thing i flash were Roms and yes i have a engineering bootloader.

I am not saying you did any of those things, I am only telling you how I got to that point and that once there, I had zero luck in recovering.

This happened to me before. I had a full charge and turned off the phone, pulled out the battery, and put it back in. Tried turning it on, it wouldn't. Plugged it in the charger, had the blinking light. I simply googled "amber blinking led mytouch 4g" or something like that. It happens when the phone thinks the battery is really low. So just leave it off, plug in your charger and wait.

ill try that

I am pretty sure that if the radio is bad it will not charge. So if you can charge, then you do not have a bad radio.
I found this thread for the same issue on an HD2. They say a JTAG is required to fix a bad flash on an HD2; may be the same on a Glacier, I don't know.
I am fairly certain that this Qualcomm MSM is the radio itself and if you had the right drivers you could send it commands, though flashing the emmc may not be possible from there.

the device does charge no blinking at all so it might not be a radio ,funny thing this happened without me flashing anything.
Edit: i though it was charging but then 5 minutes later i see a green LED on ,i think the phone turn on while it was charging not sure.
Edit2: Yeah its not charging i plug the phone then it just turns on to a black screen
Thanks for the Help

Can we remove this thread or post it where it is supposed to be? Thanks!
Sent from my HTC Glacier using XDA App

bretjrodgers said:
Can we remove this thread or post it where it is supposed to be? Thanks!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
dude read the second post i told them to move it ,you dont have to say it twice

i had this happen to me once when i first got this phone. pulled the battery and it started right up. now sure what the cause was tho?

Have u tried takin out the battery,sim card & sd card,leave it out for about 10 min or so & then put everythin bck on & try of it starts that way,a friend of mine called me earlier & sd his phone just shut dwn & wouldnt start & thats what he did & it wrked... He sd he thinks the phone was thinkin the battery was dead & thats what fixed it? Just a thought : )
Mytouch 4g-white
Permrooted s-off
Root Method-gfree
CWR-3.0.2.4
Rom-Royalginger v2.1
Kernel-Ckisgen~smartass~v1.2

bretjrodgers said:
Can we remove this thread or post it where it is supposed to be? Thanks!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
the above quote is very helpful towards the topic this is why xda is failing as a community based forum

my xoom appears to be dead (?)

Hello, android developer here.
The other day my xoom drained all the way to 0% (this happened overnight while I was asleep). I noticed right away because I use the xoom as my alarm clock. I ended up sleeping in that day (doh!)
Anyways, now the darn thing simply wont turn on. I try to soft reset (vol up + power) but nothing happens. I tried plugging it in via usb thinking I could reboot it with adb, but my computer fails to see the device. So its turned off and simply will not turn on. I've even let it charge for 2 days straight (green charge light on device).
Nothing.
What the heck man?

Dumb question.... How long have you held the power button? My Xoom (maybe others?) won't turn on unless I hold the button for 2-3 seconds.

Ive gone up to 60 seconds of button pressing...when it doesnt work one tends to go to extremes lol
I can't believe this, first time I've ever had a device die like this :-/

Did you charge it before you tried to turn it back on? My Milestone tends not to turn on after it drained below zero for like ten minutes until the battery has at least some basic charge again.

Try turning on right 3~4 minutes later putting on a yiur charger
Sent from my MZ605 using XDA App

Zhenech said:
Did you charge it before you tried to turn it back on? My Milestone tends not to turn on after it drained below zero for like ten minutes until the battery has at least some basic charge again.
Click to expand...
Click to collapse
Yeah its been charged for 48 hours now, green light on power indicator as well.
It still wont boot. I tell ya its the strangest thing I've seen in a while...

did you try booting in recovery? vol down ±power

zylith said:
did you try booting in recovery? vol down ±power
Click to expand...
Click to collapse
Of course. I've tried every combo imaginable.
F this, I'm getting an ipad.

techs1200 said:
Of course. I've tried every combo imaginable.
F this, I'm getting an ipad.
Click to expand...
Click to collapse
If you really want the iPad, here's the perfect excuse.
However, if you want to save your Xoom, you might want to check out the Motorola Factory cable from Team Black Hat (Google it). If there was ever a use for this cable, your situation seems to define it. Your Xoom seems to think it's not charged (drained) or can't take a charge, but it sounds more like the former situation. The Factory/Programming cable obviously makes a different electrical connection and makes the Xoom think it's charged...something like that. Check it out.
Also, at least one person made one out of a usb cable and it saved his bacon. You'll have to do a search for his thread...it was a while back.
Good luck, what ever you do.

You need to make or buy the motorola factory cable. That will get you booting.
Sent from my Xoom using xda premium

Well I did buy an iPad2 a few days ago, but I will definitely be making one of those cables.
Wow, thanks so much! XDA never disappoints

Remove your SD card then restart... Happens to me all the time..
Sent from my GT-N7000 using XDA App

davidblaine021 said:
Remove your SD card then restart... Happens to me all the time..
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
Yes, I have seen this also. Pull out the SD card and the unit comes back to life.

[Q] HELP!! Phone died, wont charge

Hi. I loved this phone till today.
My phone died while working, went home to charge it..and it wont charge, plug it in to several different outlets nothing works. No lights, nothing..
Any suggestions?

See this thread and good luck.
http://forum.xda-developers.com/showthread.php?t=2013977
Sent from my Nexus 4 using xda app-developers app

chelsierae said:
Hi. I loved this phone till today.
My phone died while working, went home to charge it..and it wont charge, plug it in to several different outlets nothing works. No lights, nothing..
Any suggestions?
Click to expand...
Click to collapse
Where you running Faux's kernel?
Can you hold down the Vol +/- and then plug in your USB cable? If it is a red blinking light then I think it's a battery issue not supplying power to your motherboard.

elliot.newnham said:
Where you running Faux's kernel?
Can you hold down the Vol +/- and then plug in your USB cable? If it is a red blinking light then I think it's a battery issue not supplying power to your motherboard.
Click to expand...
Click to collapse
I dont even know what Fauz's Kernel is... I tired that and I still get nothing

chelsierae said:
I dont even know what Fauz's Kernel is... I tired that and I still get nothing
Click to expand...
Click to collapse
I believe it is the phone, not the charger. Grabbed my old phone that uses the same charger, and it charges that phone instantly..Not very happy with the Google Nexus 4

chelsierae said:
I believe it is the phone, not the charger. Grabbed my old phone that uses the same charger, and it charges that phone instantly..Not very happy with the Google Nexus 4
Click to expand...
Click to collapse
This happened to me today. The battery indicator is incorrect, and shuts down before notifying you sometimes.
Phone shut down on me randomly and wouldn't turn back on today. Plugging into the wall didn't help. It was only when I plugged it into my PC and let it charge for 5 minutes that it came back. Scary bug.

chelsierae said:
I dont even know what Fauz's Kernel is... I tired that and I still get nothing
Click to expand...
Click to collapse
No need to type in bold...
Faux is a developer who is putting together a new kernel for our device, basically it allows one to modify the 'engine' of our phone.
I think the consensus here is there is a manufacturing defect in your phone and a lot of other phones. It seems like this issue is connected to running a custom kernel but there are reports of 100% stock phone bricking (like yours)
It's time to call up google, nothing we can do from here.

elliot.newnham said:
No need to type in bold...
Faux is a developer who is putting together a new kernel for our device, basically it allows one to modify the 'engine' of our phone.
I think the consensus here is there is a manufacturing defect in your phone and a lot of other phones. It seems like this issue is connected to running a custom kernel but there are reports of 100% stock phone bricking (like yours)
It's time to call up google, nothing we can do from here.
Click to expand...
Click to collapse
I thanked you on accident, you didn't deserve it. There is no evidence that his phone is bricked, a user above reported the same thing happening and how he resolved it.
Also, he can type in bold if he wants to.

I hope the OP issue gets resolved. Wish you all the best buddy!

I'm having the same issue. Except this happened when I pulled the device new out of the box. Can't even get it to stay on long enough to get into bootloader mode. :-/ RMA time

Good luck on fixing the problem.
Sent from my Nexus 4 using Tapatalk 2

[Q] Tablet bricked by USB OTG

Hey guys,
Well I screwed up and I think the only thing to ask is whether this situation is covered by warranty.
Yesterday I received my new USB OTG cable, because the other one stopped working as soon as you would turn it a little. I tested it with a mouse yesterday and it was running flawlessly. Today, I wanted to test whether it would be able to mount USB sticks, so I took the nearest one and plugged it in. The screen was locked, and after nothing happened I tried to unlock the screen, which wouldn't work. The rest is history and a lot of confusion and anger.
The problem might have been that it was a bootable USB stick containing Ubuntu 13.04, but I'm heavily doubting that this caused a brick. I mean, just plugging a USB stick in cannot brick a tablet? Wubi is an .exe-file an AFAIK Android cannot do anything with this by itself.
I was running PA 3.98/stock kernel and didn't have any program like stickmount installed. I cannot access the bootloader, charging the tablet gives no response at all and when I try to connect it to the computer, it just says that it cannot recognize the device.
Thanks in advance :crying:

Hmm, anyone? I guess I'll ask it in the Ubuntu forums tomorrow too.
Sent from my Nexus 4 using xda app-developers app

Have you tried holding down the power button for 20-30 seconds to force a reboot? Is it possible it is suffering from the low battery bug? By that I mean is it possible it had a low battery or it thinks it had a low battery and freaked out?

SlowCobra96 said:
Have you tried holding down the power button for 20-30 seconds to force a reboot? Is it possible it is suffering from the low battery bug? By that I mean is it possible it had a low battery or it thinks it had a low battery and freaked out?
Click to expand...
Click to collapse
Just wow, this really worked.
I feel so retarded now, I already tried holding down power for a while but nothing happened. Guess I was kind of freaking out and couldn't think straight anymore.
Could you tell me more about this low batt bug? Because my tablet was at 1% when it just booted and it was around 40-50 when it gave up.
Sent from my Nexus 4 using xda app-developers app

Remcotjuuh said:
Just wow, this really worked.
I feel so retarded now, I already tried holding down power for a while but nothing happened. Guess I was kind of freaking out and couldn't think straight anymore.
Could you tell me more about this low batt bug? Because my tablet was at 1% when it just booted and it was around 40-50 when it gave up.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Glad I could help, sometimes it's the simple stuff that gets overlooked in moments of panic. There is a sticky in this section and other posts as well regarding the battery bug.
http://forum.xda-developers.com/showthread.php?t=2090826

I guess most of the panic came from the coincidence that it shut down at the exact moment of connecting a bootable USB using a new USB OTG cable gehehe.
Sent from my Nexus 7 using xda app-developers app