I have a 6 or 7 month old Kaiser branded by AT&T. I got seperated from it late last week, so it ran it battery down till failure. When I went to recharge the phone, it started attempting to boot, staying at the AT&T globe screen and then appearing to boot again, (black screen and momentary vibrate.) With a bit of searching I found the suggestion of boot to loading screen and leave it there to charge. After 6 hours, the battery has a measured voltage of 4.17V so that should be enough, but the phone continues the booting loop.
I tried hard resetting with the two keys and stylus. The phone acted like a normal hard reset with the questions, but when it tried to boot, it continued the reboot loop.
My question, do you think I should attempt to reload the stock AT&T ROM?
I'm new at this so there's a large learning curve. If you guys think this is a low probably solution, then I'll sent it back / buy another one and save the long learning curve. I use this for business so I could spead the learning curve time writing software I get paid for writing.
Thanks,
Bernie
your phone got damaged from battery drain? is that possible?
i think your phone has another problem... i really dont think the battery drain was the reason...
can you go to bootloader if so try flashing new ROM (you will loose data) but again you said you have performed hard reset (partial HR) so your phone is clean!
if you want send your phone back - yes you need to get stocked ROM and stocked SPL back
BernieHunt said:
I have a 6 or 7 month old Kaiser branded by AT&T. I got seperated from it late last week, so it ran it battery down till failure. When I went to recharge the phone, it started attempting to boot, staying at the AT&T globe screen and then appearing to boot again, (black screen and momentary vibrate.) With a bit of searching I found the suggestion of boot to loading screen and leave it there to charge. After 6 hours, the battery has a measured voltage of 4.17V so that should be enough, but the phone continues the booting loop.
I tried hard resetting with the two keys and stylus. The phone acted like a normal hard reset with the questions, but when it tried to boot, it continued the reboot loop.
My question, do you think I should attempt to reload the stock AT&T ROM?
I'm new at this so there's a large learning curve. If you guys think this is a low probably solution, then I'll sent it back / buy another one and save the long learning curve. I use this for business so I could spead the learning curve time writing software I get paid for writing.
Thanks,
Bernie
Click to expand...
Click to collapse
If you already have Hard-SPL installed and it is a version capable, you may try to put the Rom with a Radio onto the Micro-SD card and re-flash the phone that way. I had an issue where i got a boot loop and it turned out that flashing the radio fixed the issue. I hope you at least had a current backup prior to the hard reset because as of now, there is no way to retrieve it
No worries on the backup, it's backed up daily and I only use it as a data carrier. The only drag of the reset is the time of reloading apps.
I agree it may be more than just software issue due to dead battery, but I have to try everything I can. I've back on my old Moto smart phone and it's just not the same, hahahaha.
Now back to studying Kaiser ROMs and how to.
Bernie
As a follow up for anyone who runs across this in the future. I flashed the original AT&T rom and the problem still exists. I spoke to tech support yesterday and they are mailing out a new/reman replacement. So the problem appears to be terminal.
Thanks guys for trying to help.
Bernie
Related
Hey all,
I posted a while ago about my phone having died and only having red flashing lights...I managed to solve that- thanks for you help, but now have a completely different problem.
Since then about a week has passed and approximately every 36 hours the phone seems to crash. When I take out the battery and turn it on again it invariably hangs at the Ericsson logo screen. When I then leave it off for a period of time (between 2 and 12 hours) I either find it starts to work again, or that I'll have the red flashing lights and have to leave it for longer.
When it does start working, it always seem to have been hard reset and I have to go through the set up again.
It's possible heating the battery speeds up how long it takes to start working again (although I've tried it with 2 batteries so I'm not sure why that would work) - and I'm not sure if that is actually the case yet or not anyway.
- It's very frustrating to lose all of my contacts daily, but I don't want to give up on £250 worth of kit... any ideas?
Thanks so much
welbis said:
Hey all,
I posted a while ago about my phone having died and only having red flashing lights...I managed to solve that- thanks for you help, but now have a completely different problem.
Since then about a week has passed and approximately every 36 hours the phone seems to crash. When I take out the battery and turn it on again it invariably hangs at the Ericsson logo screen. When I then leave it off for a period of time (between 2 and 12 hours) I either find it starts to work again, or that I'll have the red flashing lights and have to leave it for longer.
When it does start working, it always seem to have been hard reset and I have to go through the set up again.
It's possible heating the battery speeds up how long it takes to start working again (although I've tried it with 2 batteries so I'm not sure why that would work) - and I'm not sure if that is actually the case yet or not anyway.
- It's very frustrating to lose all of my contacts daily, but I don't want to give up on £250 worth of kit... any ideas?
Thanks so much
Click to expand...
Click to collapse
LOL,
no idea why.
Installed any tweaking software??
Sadly no - and I've tried it with 2 different roms too
welbis said:
Sadly no - and I've tried it with 2 different roms too
Click to expand...
Click to collapse
Heh, don't know.
Maybe some other rom's installation messed up something....
hmm... I faced the same problem...
So.. I did have to send it for repair :S ....
maybe i have the same problem... many roms tried, many soft and hard-reset, but the lifetime cycle of the phone before to re-flash the device is at maximum 1-2 days... now i'm trying the tips about quickgps (maybe could be correlated) on the thread in this forum... but the most probably truth i think that could be an internal memory rom damage... if anyone find a soluzion about this problem via software i'm here...
I seem to be having the same problem.
A week ago i tested the latest roms with winmo 6.5.1, after several roms i settled with a rom with build 23081, enabled htc sense, played around abit and went to bed and put the phone to charge. when i woke and touched the screen, the phone immediately froze.
After removing battery it froze again in SE boot screen and after second removal of battery the phone hard reseted it self.
The phone has been freezing and flashing itself ever sense, sometimes the uptime is minutes sometimes over day.
Currently the phone has survived 3 days without a spontaneous flash, the only difference is that i didn't bother to enable htc sense last time it flashed. So i enabled htc sense once again and will see if the phone survives a day.
ristiisa said:
A week ago i tested the latest roms with winmo 6.5.1, after several roms i settled with a rom with build 23081, enabled htc sense, played around abit and went to bed and put the phone to charge. when i woke and touched the screen, the phone immediately froze.
After removing battery it froze again in SE boot screen and after second removal of battery the phone hard reseted it self.
The phone has been freezing and flashing itself ever sense, sometimes the uptime is minutes sometimes over day.
Currently the phone has survived 3 days without a spontaneous flash, the only difference is that i didn't bother to enable htc sense last time it flashed. So i enabled htc sense once again and will see if the phone survives a day.
Click to expand...
Click to collapse
i had approximatively also the same problem... i'm trying to understand what is the reason of this instable situation... gps location? memory? graphic instance that use HTC sense? is heavy to understand... if anyone could also find the right solution...
was having the same problem tried the method in this thread http://forum.xda-developers.com/showthread.php?t=540290 and it is working on my X1 so far
lebkom said:
was having the same problem tried the method in this thread http://forum.xda-developers.com/showthread.php?t=540290 and it is working on my X1 so far
Click to expand...
Click to collapse
Did the "task 29" do anything?
I tried the method suggested but no change besides hard reset. And the X1 froze about 12h after that...
ristiisa said:
Did the "task 29" do anything?
I tried the method suggested but no change besides hard reset. And the X1 froze about 12h after that...
Click to expand...
Click to collapse
ye mine did it again aswell this morning
i just tried hard reseting then install a stock rom then hardreset again and install a custom rom, will let you know if it works
Do you guys often use Opera Mobile?
Ahah!
Very encouraging to see other people had the same difficulties... and I suppose that it's just a question of making sure a fresh ROM flash works properly.
Sadly mine has reached the stage where it's no longer working for 'a day' before crashing... it's just pretty much dead.
Now I can bring up the tricolour screen if I'm plugged in, the ROM then begins to flash off the memory card, but crashes half way through every time.
I have tried this with 2 batteries, one of which (which I have used once and was working fine but only lasted 2 days before breaking) now does nothing whatsoever. The other lets me get half way through the flash every time.
- I can't send it back on the warranty until I reflash it myself (and I don't have a receipt anyway) so I'm going to go find a high street mobile fixing place and see if they can help.
hardresetting then flashing a stock rom (R3A generic) then hardresetting again then installing custom rom and hardresetting, definately fixed my phone, has been working for more than 2 days now it usually stops in less than 1 day.
FYI - high street phone guys managed to reflash the device for £15....it lasted 4 days but has just died again.
Hi All,
While on a business trip last week, my Tilt 2 (at the time, running the April 14 Energy ROM), my phone--for lack of a better word--crashed on me.
Everything had been working fine, I was sitting there with my phone connected to my laptop via a USB cable, and out of the blue, for no apparent reason, my phone re-booted, and never came back up. It would get to the splash screen, start loading the OS, reboot mid-stream, and get stuck in a loop. Weirder still, if I pulled the battery, let the phone sit, then put the battery back in, hitting the power button did nothing--even with the phone plugged in to power. On top of that, even if the phone was off, after a few minutes, it would power itself back on randomly, and get stuck in the re-boot loop. Very weird.
So, when I got home, before heading to the AT&T store and asking for a replacement, I thought I'd try to restore the phone myself.
At first, I pulled the battery, then stuck it back in, and sat there holding the volume down button, waiting to put the phone into bootloader mode. That worked, but even in bootloader mode, it would randomly re-boot. So, I started the process again, and immediately plugged the phone into my computer while in bootloader mode and ran the Task 29 tool. That completed properly.
At this point, I popped in another battery I had laying around and just let the phone charge for a few hours. Then, for the heck of it, I re-ran the HardSPL tool. Re-Flashed to the .91 radio (it was already on the phone), and then flashed to the latest Energy ROM.
Since then, my phone has been better than ever. Seems faster, battery life is better (Went three days without having to charge it), no dropped calls, and no weirdness with the latest ROM (that I've found so far).
Does it pay to REALLY start fresh from time to time, and re-flash everything on the phone?
Thanks for any input.
I have no idea, but hopefully the WinMo experts will see this and have an idea, so here's a bump for you. Most of my computer expertise revolves around Unix, Linux, and a bit of Windows, not so much these phones.
I do know that task 29 is awesome, though. It seems like DBAN for your phone...
DBAN=Darik's Boot and Nuke. Look it up.
I don't know what happened with your phone, sounds like something broke in the area of booting.
I don't think you should need to re-flash HardSPL radios just for the sake of it, but I'd strongly recommend task29 every time you flash a new ROM.
bricked my TP2
My TP2 seems to have a similar problem which I haven't been able to fix it just yet. The bootloader reboot loop is too short to succesfully run task 29 and flashing it using the microSD gets stuck around 40%
during bootloader mode there's an unreadable errormessage since it's on the same line as some of the usual information.
any thoughts/suggestions would be very welcome since i can't afford to send it to the factory.
cheers.
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
Hello,
Tried to look up some answers to my problem, however I'm not sure exactly what is wrong which makes any troubleshooting rather difficult.
I bought a new ADP1 a few months ago. I haven't had much time to play around with the phone, have just been using it stock and haven't even added any applications. There has been no physical damage to this phone, no drops etc.
Yesterday the phone locked up when I was using the browser and would not function. When I would try and reboot it, it would lock up at the first android screen and would fail to start up. I ended up doing a hard reset to factory defaults and the phone finally booted. After setting everything up again the phone seemed to be working fine.
A few hours later it locked up again while using the browser. This time no reboot/safe mode/factory reset would get it to boot. I can't even get to recovery mode or even get the phone to attempt to boot up. The screen remains black and the phone will not power on. It won't even charge when I plug it into the charger.
Not sure how to proceed here and I can't seem to find any information in regards to RMA, it is still in warranty.
Any help would be greatly appreciated.
Take out the battery for hour or so put it back in and try again.. but this sounds like my issue What happen to Me is my mobo was crapping out and eventually just died on me
Sent from my Nexus One using XDA App
Yeah, the mobo going to **** was my original thought.
I already tried taking out the battery last night for about 3 hours, it still didn't work.
Guess I'm going to have to look into an RMA, I hear they are a pain in the ass. The phone is still within it's 1 year.
Yea I would get that done quick
Sent from my Nexus One
Hi guys.
First post, apologies if it is in the wrong place.
I was given a Motorola XT925 3 days ago, running what I can only assume is the most recent version of android (i tried updating it, and it claimed it was up to date). No SIM card in, no SD card.
All was well, until I noticed an app, "media" sucking 50% of the battery. It was killing me, so I did some extremely brief Googl-ing and arrived at the conclusion that a factory reset would be a sensible thing to do to nip the problem in the bud.
Unfortunately, my battery ran out half way through the reset (derrrrrrpppp), leaving my new phone semi-hard-bricked.
The loading icon will come on sometimes if it's put on to charge after some time off charge, and sometimes the stupid little robot even pops up, with a loading bar underneath him, and a tangled blue web protruding from his abdomen. He freezes a short time later.
The power and volume buttons are unresponsive, and the whole semi-booting pattern is erratic, but things seem to happen if I leave it off/on the charger all day.
I have a suspicion that my phone in it's current state has half the operating system un-installed, and will therefore not boot correctly.
Anyway I was hoping to get some recommendations for the most appropriate next step. I will be taking it to a nearby shop tomorrow, and see-ing if the people who sold it to the person that gave it to me can help...
I have read about "flashing" devices etc, and if the shop-people can't work it out, I'm probably going to give it a try. I am running a mac as well, so many flashing programs will probably be incompatible.
Thanks for the help
tl;dr: Motorola XT925 hard-bricked following complete battery depletion during factory reset. Wat do?
metal man007 said:
Hi guys.
First post, apologies if it is in the wrong place.
I was given a Motorola XT925 3 days ago, running what I can only assume is the most recent version of android (i tried updating it, and it claimed it was up to date). No SIM card in, no SD card.
All was well, until I noticed an app, "media" sucking 50% of the battery. It was killing me, so I did some extremely brief Googl-ing and arrived at the conclusion that a factory reset would be a sensible thing to do to nip the problem in the bud.
Unfortunately, my battery ran out half way through the reset (derrrrrrpppp), leaving my new phone semi-hard-bricked.
The loading icon will come on sometimes if it's put on to charge after some time off charge, and sometimes the stupid little robot even pops up, with a loading bar underneath him, and a tangled blue web protruding from his abdomen. He freezes a short time later.
The power and volume buttons are unresponsive, and the whole semi-booting pattern is erratic, but things seem to happen if I leave it off/on the charger all day.
I have a suspicion that my phone in it's current state has half the operating system un-installed, and will therefore not boot correctly.
Anyway I was hoping to get some recommendations for the most appropriate next step. I will be taking it to a nearby shop tomorrow, and see-ing if the people who sold it to the person that gave it to me can help...
I have read about "flashing" devices etc, and if the shop-people can't work it out, I'm probably going to give it a try. I am running a mac as well, so many flashing programs will probably be incompatible.
Thanks for the help
tl;dr: Motorola XT925 hard-bricked following complete battery depletion during factory reset. Wat do?
Click to expand...
Click to collapse
Hi,
Unfortunately, we cannot help you with your XT925 on the Moto X forum.
You can post your request here: http://forum.xda-developers.com/droid-razr-hd/help
Someone in the Razr HD Forum will be better suited to help you with this.
Good Luck.