Verizon Droid Stuck in Bootloader - Motorola Droid and Milestone General

So I obtained a phone that someone gave to me cause its not working. It will only turn on when I plug it up and it shows the motorola logo then it flashes bootloader mode and it says battery to low to program.
How can I fix this? This phone had never been rooted or flashed or anything. And I dont have a another battery for this phone to try with

i done a usb battery cable thing and got the battery issue fixed now when trying to reflash with rsd lite it stops at 99% sayiing switching to bp passthru mode

I'm sure if you took it into a store, they would replace it for you. If you are still within your 30 days, you will get a new device, otherwise it will be "certified like new".

jakson0100 said:
I'm sure if you took it into a store, they would replace it for you. If you are still within your 30 days, you will get a new device, otherwise it will be "certified like new".
Click to expand...
Click to collapse
I dont think u read my entire post....
For one It was giving to me from someone. 2 its looks older than a year for warrenty and 3 I DONT HAVE VERIZON

Related

My Kaiser is Bricked! I need help!

So, all yesterday, I was having problems getting service anywhere I went. Towards the end of the day I got no service anywhere. So... put my phone on the charger all night, woke up and... Nothing.
Phone wont turn on, battery pull won't work, can't get into bootloader. Orange light turns on when I plug into charge.
I was running the stock HTC ROM with a couple programs installed. Google maps, iContact and Soft Key Changer. Thats it. Had no problems until now.
I called the company I got if from said bring it back they will get me a new one (just got it last Sunday). I can't get Activesync to see the phone so reflash is not a possibility.
They won't be able to turn it on at the store, this thing is gone. But if someone somewhere sees its a new ROM when they send it back (if they can get it on), am I screwed? I think I'd just say the guy in the store did it cause he had is last...
from what I understand you void the warranty by using a different rom.
xconradx said:
So, all yesterday, I was having problems getting service anywhere I went. Towards the end of the day I got no service anywhere. So... put my phone on the charger all night, woke up and... Nothing.
Phone wont turn on, battery pull won't work, can't get into bootloader. Orange light turns on when I plug into charge.
I was running the stock HTC ROM with a couple programs installed. Google maps, iContact and Soft Key Changer. Thats it. Had no problems until now.
I called the company I got if from said bring it back they will get me a new one (just got it last Sunday). I can't get Activesync to see the phone so reflash is not a possibility.
They won't be able to turn it on at the store, this thing is gone. But if someone somewhere sees its a new ROM when they send it back (if they can get it on), am I screwed? I think I'd just say the guy in the store did it cause he had is last...
Click to expand...
Click to collapse
Try a different battery or a different charger first.
brynwall said:
from what I understand you void the warranty by using a different rom.
Click to expand...
Click to collapse
Thats what I understand too. However, you can't get the thing on, no connections - nothing. They won't be able to tell at the dealer for sure. And I think in this state it goes to the junk pile cause I can't get any connection on it period.
From my dealing with Cingular and having to exchange my 8125/Wizard, they always include the statement regarding voiding your warranty if you load unauthorized rom images on your phone.
That being said, I have sent back many bricked 8125's for various reasons (none of which were bad rom images), and I never had an issue with them actually noticing that I had a custom rom loaded on it.
Of course every carrier is different, but judging from my experiences, I think you'll be fine.
NotATreoFan said:
From my dealing with Cingular and having to exchange my 8125/Wizard, they always include the statement regarding voiding your warranty if you load unauthorized rom images on your phone.
That being said, I have sent back many bricked 8125's for various reasons (none of which were bad rom images), and I never had an issue with them actually noticing that I had a custom rom loaded on it.
Of course every carrier is different, but judging from my experiences, I think you'll be fine.
Click to expand...
Click to collapse
Cool, thanks man. I think I'll be fine too. I feel that the issues has nothing to do with the ROM, as the ROM has been working fine for a few days now with no glitches except for the service problem yesterday. I wont mention the ROm of course, but the thing does not turn on in any way whatsoever. The only thing that happens is when you plug in the power you get a orange light up top.
Thanks for your help, I'm glad they haven noticed even on working phones with different roms.
It sounds like it could be as simple as a power issue. Either charger or battery.
But I had the same thing happen to a Razor once. Bricked at the bootlloader screen and would not take a charge from that point on. My carrier (AT&T) had told me the device was beyond repair (translation: they had no clue at the store). Ended up having to borrow a charged battery to re-flash the device.
Haha, I bricked a razr once too, and was able to revive it with via a number of things (barely). I was trying to change the boot screen. Those phones are fun to mess with - at least you could get into the boot loader most of the time even if it was near death.
I'll try a different battery when I get to the store.
I went to the store just now, they changed the battery and... nothing she tried my battery in a new phone and it worked, so the battery is fine, but my phone is f*cked.
I am replaceing tomorrow.

New Nexus Not Working

Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Sounds like a DOA. Really bad luck.
If you send it back you should not pay duty to get it back usually, unless you live in a very tax hungry country! Between US and CAN you would not get duty.
Beside try speaking with cust support, DOA are usually well handled by company and so far HTC seem to be handling repair quite well as per the few post about broken screen I have seen.
Did you try running the phone WITHOUT an SD card ? good luck!
Krypton1984 said:
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Click to expand...
Click to collapse
If the boots, has never been rooted (boot unlock), no immediate physical damage, and has no signs of liquid damage or tampering (check void sticker).... it's likely just a software issue. Reload original firmware, or load a new firmware... Don't give up, sounds like the phone is still okay.
Was it bnib?
mrbkkt1 said:
Was it bnib?
Click to expand...
Click to collapse
So it seems.
Where are you from, Krypton1984 ?
Looks like some rogue app is loading at boot, causing reset. Possibly corrupt ROM image - but not sure. Might be software, might be hardware. But here's one thing to try:
If you're on a T-Mobile-compatible phone (900/1700/2100), do yourself a favor and flash stock Froyo. No need to root for that. The guide is in the sticky thread. In case of corrupted ROM image it'll do the trick.
I think you should factory reset it. Maybe even download the official 2.1 rom and install it. See if it fixes it.
Try a battery trade in first. Believe it or not, my first N1 seemed dead, and support gave me a swap for a new unit. When the new unit came in, it was still "dead" with the battery that originally shipped with the device. A new battery is what caused my N1 to finally come to life. The batteries that ship with N1's have QC issues, because I was one of many to report a DOA battery in the Google support forums.
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Krypton1984 said:
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Click to expand...
Click to collapse
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
You can also try a full factory reset through the bootloader. Search for the instructions as i do not know them off the top of my head
P00r said:
Between US and CAN you would not get duty.
Click to expand...
Click to collapse
Yeah, North America is all one big happy family. We've got NAFTA and everything now.
OP, I am assuming you've allowed the battery to charge full?
badomen said:
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
Click to expand...
Click to collapse
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
You'll probably need to swap based on what you're saying. I, though, actually think Refurbished devices are just as good or even better than new. Think about it, if you keep getting dust under the screen maybe a refurbished phone will already have the fix? For that scenario it works out.
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
I really think this is a bad RAM issue.
I had this happen to my Nexus (ATT). It was prior to flashing froyo. I tried everything, flashing back to stock (including radio), cyan's latest, Paul's (stock) Froyo (with and without radio). Same result. Seemingly random reboots.
I thought initially that it was a software issue - It would not reboot while in fastboot/Amon's Recovery. But having tried every software combination, I've concluded that it MUST be hardware, unless I'm missing something big.
The phone, for the most part, would be fine as long as I DON'T TOUCH IT. It would stay idle for a long period of time (24hrs+), then I would use it Everything from web browsing to downloading apps to making calls, and it would reboot. It's frustrating because it seems that it's rebooting for no reason except that I'm touching it.
Sent in for a replacement, it arrives today. Hopefully it will not suffer this problem.
After talking with HTC they told me i need to swap the phone.
Because i'm out of america i need to send it to someone in the US amd then they send him the new divice after he sends my old one,
I am not satisfide with google's (first guy I talked with) and HTC because none of whome understand the severity and the hard feeling of getting a BRAND NEW IN BOX paper-weight. nothing about we'll compensate you or nada.
For me it tells me the brand is not strong enough to manage an outer state service and i wouldn't recomend them for countries that they don't cell it for.
If you where born in a HTC GOOGLE compatible country enjoy!
As i'm am probably less lucky and still in 2010 nationality counts

Phone won't turn on

Hey Everyone,
Just seeing if anyone might have a solution to my problem that I'm facing. I had rooted my phone when the root originally came out, and everything seemed to be working fine. I had been texting on my phone when it suddenly froze, I waited to see if it would come back, but it never did so I pulled the battery.
The phone originally booted to the M logo, but froze, after another battery pull the phone now won't turn on at all. As in it's not responding to the power button press at all. It's not being recognized by a computer, and there doesn't seem like much I can do.
Any suggestions out there? If my phone is bricked and can't even turn on, will a Verizon store know this? How could they?
thanks.
If u froze something like a system app that may have bricked it. Theres something u can flash which was a cracked version of an ota update that should fix it but u may not be able to receive official updates if u do that. Other option is to wait for an official sbf file
Sent from my DROID3 using XDA App
How can I flash something? There doesn't appear to be a way for me to access my phone. I can't get into restore or the bootloader.
What happens when you plug the phone into your charger(using the stock charger and cable)?
Nothing, no light, no anything
I actually haven't tried it in a situation like that so I can't give instructions :/
Sent from my DROID3 using XDA
Just take the phone into Verizon and tell them it has stopped working. You don't have to go into any detail at all.
g3m1n1 said:
Just take the phone into Verizon and tell them it has stopped working. You don't have to go into any detail at all.
Click to expand...
Click to collapse
I think that might be what I do, I can't imagine they would have a way of knowing it's rooted if the phone won't even turn on, charge, or anything.
Thank you, btw.
Try taking out the battery and plugging it in to the wall without it in it. If it starts to boot, let it. Then replace the batter and plug it into the wall again and let it charge up. Happened to my Droid X before and I was able to get it working by doing this.
Tried this, but couldn't get it to work.
Took it to a Verizon store and they said they would send me a new one tomorrow, and then all I do is send mine in afterwards.
Is there a chance that after I send them my phone they could find out I rooted it? I'm worried they would charge me full price for the phone they sent me if they discover it.
Niviac said:
Tried this, but couldn't get it to work.
Took it to a Verizon store and they said they would send me a new one tomorrow, and then all I do is send mine in afterwards.
Is there a chance that after I send them my phone they could find out I rooted it? I'm worried they would charge me full price for the phone they sent me if they discover it.
Click to expand...
Click to collapse
Honestly the Magnuson-Moss act protects you in that VZW has to prove that rooting caused the phone to fail. However in practice you end up having to take them to court which is too costly and time consuming. But to answer your question yes they could pretty easily figure it out.
But to put it differently no one else that I've read about has had a failure like yours. People have bootlooped and such, but no one has just had nothing happen on power-up. It doesn't sound like you did anything other than root, which couldn't possible cause this. Freezing apps and deleting system apps only causes force closes and bootlooping, you had neither.

Think I Bricked my phone somehow....

I rooted when the phone first came out, did the forever root method days ago, was using ROM manager to boot into recovery and BAM!!! phone went completely dead. I had just taken it off the docking station about 15 minutes prior, had a full charge, tried swapping with my original battery, nothing...took it to verizon store, they couldn't do anything and ordered me another phone to come on Tuesday. What do you guys think??? I haven't installed any roms, radio changes, NOTHING!!!... pulled the battery a hundred times, nothing comes on
Dude, first of all, if you mess up your phone by rooting it, DO NOT take it to Verizon. Cardinal rule #1.
Second, a quick view of the threads here and you would have found this:
http://forum.xda-developers.com/showthread.php?t=1279825
Do this and you'll be fine.
Sent from my DROID BIONIC using xda premium
That's the thing
I can't get to fastboot or any boot screen. Phone is completely lifeless, doesn't even show when plugged in, tried multiple chargers, batteries, everything...nothing.
Sorry bro, sounds like a hard brick to me. if you cant power it on and holding VolumeDown+Power or holding both volume buttons+power does nothing at all, you're hard bricked (you cant fix it)
You need to buy a new device. Tell verizon you lost it or somebody stole it or something, but DO NOT take it into verizon.
Happened to me too over the weekend. Was playing Greedy Spiders and the phone froze. Rebooted and got the dual core screen twice then kaput. Tried everything and it won't turn on. Did some research and this isn't a one off problem. Took it VZW and they replaced but I have to wait for it to ship. I love how if you are buying the phone, they have them at the store, if you BOUGHT the phone and need it replaced due to warranty you have to wait.
Of course because they make more money that way

[Q] Boot Loop while charging - no charge

Hello, I've had my G Watch R for not quite a full week so far and I've really enjoyed it. Two days ago, I believe that I let the battery die so I placed it on the charger before going to bed. When I woke in the morning i grabbed the watch off the charger without looking at it. Just before i stepped out the door i noticed that it wasn't waking up and It wouldn't even power on. I ran back and slapped it on the charger thinking that it would be more than charged by lunch time. Thats when i noticed the apparent boot issue you can see in the video attached. It hasn't been dropped at all and I have the basic apps installed; facer, watchmaker etc. At this point, Is there anything that I can try short of sending it back?
I've left it on the charger for 24+ hours, it gets slightly warm and stays in the boot loop. As soon as its taken off the charger it has no visible charge and refuses to respond to anything. I purchased it through amazon, so I'm thinking it shouldn't be an issue for me to return it...
http://youtu.be/GgF3iXAhTTI/
Sorry i tried to embed the video but the youtube link for xda seems to be breaking the url somehow
So I have already initiated the return process with amazon and it should be pretty painless. I have almost 3 weeks to send it back, so if anyone has any tips/tricks or ideas I'm more than open to try them....The watch is 100% stock as far as firmware or root is concerned.
Any luck with this? I just got back an RMA for a broken touch sensor, I don't want to have to RMA it again.
try to see if you can get in to the bootloader, and restart the watch from there
i have notice when i charge the watch from empty (so thewatch boots up while charging) it causes problems, usually boot loops as well
I just watched the video (should've done this before hijacking the thread, sorry) and it seems like I'm having a different issue. Instead, mine does the android boot animation, the goes to "Starting Apps" and counting ("x of y Apps"; the y value seems to be different every time), then "Staring Apps" with no count, then it says "Powering Off" and shuts off. But I will post my experience in case someone else with my issue finds this thread.
I'm back up & running today. I got it into the bootloader last night and put it on the charger before I went to sleep (to avoid battery rundown by bootlooping while it charges). I woke up this morning to it bootlooping again. I'm guessing that it restarted itself sometime during the night. I took it off the charger and let it sit for a while (it was pretty warm, so I figured it would be better to let it cool down before trying anything else). I tried to restart it again after about a half hour, but it still only got to "Starting Apps" before shutting off. I reflashed the stock boot, recovery & system images found here: Stock Boot, Recovery and System for G Watch R . I restarted it and completed the initial pairing process (due to wipe when I unlocked it in order to flash system image) and it is now working.
I don't know if what I did actually fixed anything or if it just decided to start working, but I will post again if something happens again. If you don't see any more replies from me, then all is still OK.
EDIT 6/22/15 9:53 pm EDT: No good, see below.
To workaround the bootloop while charging, you can boot into recovery (swipe 10 to 4 a clock while Logo is shown, select and press okay to recovery), than charge battery for a while, after that, you can boot to as normally to AW-system and charge to fully battery!
You can charge with USB on PC, it's work fine for me.
scidon37 said:
I just watched the video
I don't know if what I did actually fixed anything or if it just decided to start working, but I will post again if something happens again. If you don't see any more replies from me, then all is still OK.
EDIT 6/22/15 9:53 pm EDT: No good, see below.
Click to expand...
Click to collapse
So your gwatch r started doing the same thing again? I have the same problem and it won't connect to the computer via fastboot or adb. How did you get on with the RMA? I cant send mine back due to voided warranty. Still hoping for a solution.
Have you tried taking it off the charger and booting it? Also are you running custom software?
bricked watch
atmosphrericks said:
So your gwatch r started doing the same thing again? I have the same problem and it won't connect to the computer via fastboot or adb. How did you get on with the RMA? I cant send mine back due to voided warranty. Still hoping for a solution.
Click to expand...
Click to collapse
Ever find a fix for this? I've been searching like mad the last few weeks. :/
biohazard1150 said:
Ever find a fix for this? I've been searching like mad the last few weeks. :/
Click to expand...
Click to collapse
So i took off the back plate, and found that the spring contact pins inside the watch weren't making good connections to the connect points on the inside of the back plate. Be careful, they are fragile, but you want to bend them out slightly. If you can source parts, get a new contact pin module.
After this, i was able to connect my watch and flash over stock firmware.
I can't guarantee this is what is happening with yours, but let us know if it does work.
I've scince broken the screen and can't find where to get parts!
atmosphrericks said:
So i took off the back plate, and found that the spring contact pins inside the watch weren't making good connections to the connect points on the inside of the back plate. Be careful, they are fragile, but you want to bend them out slightly. If you can source parts, get a new contact pin module.
After this, i was able to connect my watch and flash over stock firmware.
I can't guarantee this is what is happening with yours, but let us know if it does work.
I've scince broken the screen and can't find where to get parts!
Click to expand...
Click to collapse
I still haven't found a fix. My charging works fine, but no PC connection. The bootloader/fastboot wont come up, no logo or anything. I'm sure the EMMC chip is fried, it sounds like many are seeing this issue, some with a black screen and some with a snowy screen. I've had several galaxy phones do the exact same so I'm doubting it can be fixed without going to the manufacturer which mine came from redflagdeals and LG wont service the random online store purchases
I had to take the back off and clean and adjust the contacts that make contact through the back panel. Then I could connect via fastboot.
ouranos2k said:
You can charge with USB on PC, it's work fine for me.
Click to expand...
Click to collapse
This solved my problem. As soon as I plugged it into my PC it booted just fine
ouranos2k said:
You can charge with USB on PC, it's work fine for me.
Click to expand...
Click to collapse
This works for me too! Thank you!
Sent from my SM-N920C using Tapatalk

Categories

Resources