Related
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
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
Hi,
I have a rooted GT-i9000m (bell Galaxy S Vibrant). I used the one click lag fix to root my phone and it works fine.
A few days ago out of no where all the apps started auto closing as soon as i opened them and then both the menu and back touch buttons lit up and the screen went black. I held the power down till it rebooted only to get and error with com.android.calendar even tho I never use the app. When it finish's booting none of my installed apps are showing.
The first time it happened with com.android.app and I did a full wipe and factory reset and just reinstalled everything.
Ideally I don't want to system reset to factory settings again and lose all my files and notes that i copied back on to the phone 2days ago...
Please note I have tried clearing the data for the calendar app in settings -> apps and i cleared the calendar back up. My problem is that none of my installed apps are showing...
(Update) I also cant reinstall or update apps due to a Installation error - Insufficient storage. But there's room on both SD cards. I also set 850mb for apps when i did the one click lag fix and i don't have 850mb of apps installed.
(Update 2) I did a factory reset again this time i didn't format the internal and external SD cards. (It works like new again) Thus I got to keep all my personal files and ring tones ect. The only thing that was deleted that I didn't back up is my Notes. This leads me to my new question whats best for backing up apps on a rooted SGS (bell Vibrant)?
If anyone has answers they would be much appreciated.
i had the same problem
install rom manager from the market place
there is a option in there "Fix Permissions" just run that and it will fix it up for you
only takes 1-2min to run
Tried what you said but i cant install anything... I get Installation Error - Insufficient storage available.
I now understand the cause of the problem. I change my battery once and some times twice a day. At first I would wait for the long shut down (untill the screen goes totaly black) and then take off the back and swap out the battery. At least 3 times the phone would boot up and ask me for the network unlock code (I bought the unlock code directly from bell for 75$). I found this rather annoying so i tried just taking the battery out wile it was on (idle) and it appeared to work flawlessly at least 20-30 times before the phone would start to do an endless force close loop cycle. This kept forcing me to do a factory reset on the phone. I can only assume the one click lag fix and my disregard for the need of the shutdown before removing the battery must be all the cause of my problems.
I will try and see if my phone is more stable with out the one click lag fix.
nope that is not the cause of the problem
but it sounds like you are another victim of the lag fixes that is killing your internal SD card.
not the fault of the lag fix, it just make the problem apear sooner than later
I have been having a similar issue and I'm using Voodoo lagfix. I think it's because I took the battery out before it had completely shut down.
read this
http://forum.xda-developers.com/showthread.php?t=793404
Well the phone bit the dust today. I opened up google maps to look up an address and it crashed with the usual error. So i rebooted the phone and now it stays stuck at the boot logo. (the glowing S with both touch keys staying lit) So i did the recovery thing again but this time I had to do the Vol-up + home + power in order to get the phone working some what. IDK but it wont let me log into my google account to sync my contacts. My APN settings are correct and working and I even tried off my Wifi at home. I'll just hope its a google problem and not my phone acting up. Thanks for the pointer to the bad internal SD. That may be the problem kinda hard to prove it to Samy thoe...
I get force close errors after about 4-7 days of use. Now its gotten worse. A few days ago I was looking up an address and my phone crashed and rebooted it self. It then hug at the S boot logo for 20mins. I got to my friends apartment building to find my phone still stuck at this boot logo. I couldn't remember his apartment number or buzzer code... Normally i just check my contacts list and buzz the code. I was standing out side in the Canadian fall cold wind trying to get this phone to work... OMG i almost just smashed it on the spot. Anyways I remembered about something i had read on this forum about the recovery mode ( i had used it to root ) so i tried that out got the little menu and tried every option before having to do the dreaded factory reset. Well nothing work with the exception of the factory reset it got my phone working in about 5mins... LOL
Anyways I thought I might try upgrading the firmware when I got home. What a mistake... I cant control my phones MP3 player via my bluetooth car stereo any longer. Tried everything even a factory reset and formatting the internal and external SD's. I tried running it with out rooting it again and with out the lag fix in hopes that I wouldn't get a force close error. Wouldn't you know it about 5 hours after the factory reset un-rooted just after i finish coping over all my music. I get a force close error! So I tried again and this time the phone ran for about 30hours before it started giving me force close errors about the email now...
Sigh I've tried just about everything in my power to make this phone work. So I assumed it must be the phone... I called Samsung up to get a RMA going... Wouldn't you know it they tell me that I have to call my carrier to get it RMA/repaired. I try to explain that I bought the phone with out a contract and bought the unlock code from Bell so I could use it on Fido. They tell me to call Fido... ROFL Fido wouldn't even give me their APN settings when i got this phone so knew they would be of no help. They don't even have one android phone in their line up i tell the sammy rep. So they tell me I should go back to the Bell store I bought it from to get it repaired/RMA'ed.
I doubt Bell will be of much help but here's hoping.
Do you think my phone is broken, bad flash, buggy memory, ect and needs to be RMA'ed?
Update...
I got my phone back from repairs 2 weeks ago. They flat out replaced the phone for a new one. This was a huge headache for me because the new one wasn't unlocked. Took Bell 2 hours to get the new one unlocked wile my wife waited out side double parked downtown! (I thought it would be a quick pick up and I would be out) The blue-tooth works flawlessly again!!
Much to my dismay the replacement phone has started acting up much like my first one did. It gets several force close errors a day and has gotten to the point where it no longer can send or receive text messages (using Handcent). The stock Music Player app also force closes at random with more frequently. It looks like I got another Lemon. This time around I did NOT root, lag-fix, or flash firmware. I will be sending it for repairs as soon as I can afford to buy another phone to use wile this one is off at repairs. My back up phone is a 3~ year old Iphone3g that my son has made his... (cracked screen, vol rockers dont work, power button is jammed in, the LCD screen it self is bleeding on the top edge)
The Vibrant never let me down other than as a phone. As a divx player or using all-share it rocks! I use these features A LOT to play my 720p divx movies on any TV or the projector in the bedroom .
with that being said I might keep the phone just as a portable movie player to bring from place to place and put my sim in something more stable.
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
Hello all,
Firstly, I hope this is the right place to put this thread. I did a search and did not find anyone else having this issue so I decided to put my post here. I am having a problem with my note 4 randomly restarting a few times every hour. It goes through its shutdown procedure and turns right back on. Occasionally it will shutdown and stay off. It seems to be software related, but I'm no expert on these things. I did however download 'Device Temperature' from the play store to check to see if it might be overheating. As far as I can tell it has stayed a cool 24-25 degrees Celsius (77 Fahrenheit) the entire time.
It does this at unpredictable times, whether or not the phone is in my pocket, in my hands, or laying flat on a desk with or without the charger plugged in.
I don't think I can take it back to Tmobile to have it replaced as I bought it from a friend a few weeks ago to use on cricket. This just started 2 days ago.
The device is SIM unlocked, but not rooted with stock everything. It's still in mint condition and to my knowledge has never been dropped.
Can anyone help?
More Information
I did a Google search for "Galaxy Note 4 Random Reboot" and I found some information saying to reformat my SD card or try doing a factory reset on the phone.
I tried both (I actually removed the SD card completely instead of just reformating it), and about a half hour later... boom restart again. FML.
Once again I turn to the wonderful folks at XDA for help. Thanks to all in advance.
Sounds like it could be bad eMMC flash memory. Go with your friend and have Tmobile replace it. Also get Square Trade insurance if you can.
Got it fixed
I called Samsung about the issue and after some brief troubleshooting they recommended having it reflashed at a samsung experience center. The closest one to me was in a Best Buy. I dropped it off, after explaining what was happening, and an hour later it was ready to be picked working good as new. I haven't noticed it restart even once since.
Samsung offered to replace the entire unit but it would cost me $28 for 2 day shipping (assuming that they had my model in stock). I will go that route if the issue returns. I'm hoping not to go this route because I already paid for this phone to be unlocked once - I'd rather not pay again if I don't have to.
I'll keep you guys updated if the rebooting issue returns again.
Also check to make sure the battery is properly seated and contacts are not bent/damaged.
railshot said:
Also check to make sure the battery is properly seated and contacts are not bent/damaged.
Click to expand...
Click to collapse
This. I kept having this issue with my Note 3 and could not figure it out. Eventually I just took out the battery, cleaned the contacts, put it back in, and it never had a random reboot after that.
Are you guys running any custom roms, or is it still stock?