Database Develop

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.

Screen logo repeats on samsung galaxy i9000m

I may have bricked my phone while flashing with odin to stock froyo 2.2 rom. The download mode works but i cannot get into recovery mode it just flashes at the logo screen gt-i9000m over and over and over again.
Is there a way past this or do i have to send this phone in for repair?

I have stock everything.
My phone battery died and I have spare batteries and changed it to a fully charged one. It booted up and said that a bunch of apps have to be FORCE closed... so I rebooted it.
Now it's doing the same thing yours is... the logo screen flashes over and over.
I pulled the battery to hard boot it. Then without turning it on I plugged it in to charge... so it tries to go to the charging battery icon and then flashes the logo screen over and over again.
This is my second phone... first one kept eating battery life and got real real hot.

omg stoopid samsung. I can get into download mode just fine, when i reflash it just stuck at the boot logo. Are you able to send yours away for repairs? i have mine unlocked but i also got warranty from where i bought it at wireless wave. i rather not send it in though...

I couldn't get into any menu's... sent the piece of **** away for repairs. I almost threw it at the wall behind the clerk at the bell store.

same boat here, i woke up this morning to find a bunch of forced closed messages. so i hit okay, my phone was all screwy so i turned it off, pulled out the battery, put it back in and started the phone and ta-da the galaxy S TEXT (not logo) kept...well it looks like it would boot over and over again just to the title screen, shut off and boot again. If i do the 3 button press to get to download mode i see that screen and i cant do anything else, actually i dont know what to do there.
I bought this thing in august so i am good for warranty, oh i haven't once rooted or lagfixed or anything, i just unlocked it, and with rogers instead of bell, but yeah i called bell and they refuse to help. The guy was not cool with me unlocking the phone, says i might not be covered under warranty anymore.
Next week i am going to take it to the bell repair center in person, see what they say.
Not sure what to do now. EFF!
Last samsung phone ever. the LG optimus 2X looks pretty awesome.

I'm having the same issue, my phones all stock.
When I got my phone this morning is was turned off, I plugged it in, powered it up, saw the Samsung logo and intro play and I walked away. When I came back I tired using my phone but only the lights, on the buttons, turn on but the screen and the rest of the phone doesn't respond. The lights will stay on forever.

If you can get into download mode, have you tried flashing it with some other Rom? Like DocX custom rom?
Sent from my GT-I9000 using XDA App

Try booting into recovery mode (vol-up, home and power). Do you get an error message under the menu? If so, report it here or do a search on that specific error. It appears that some errors are easily recoverable from via flashing while others are not.

gtg2 - Try booting into recovery mode (vol-up, home and power). Do you get an error message under the menu? If so, report it here or do a search on that specific error. It appears that some errors are easily recoverable from via flashing while others are not.
The flash will go through completely and pass, as soon as it reboots to the Gt-i9000m logo it will just loop continuously. even when you hold down vol-up, home and power, it just doesn't recongize those buttons but will recongize vol down, home, power what gives?
Valinorian - If you can get into download mode, have you tried flashing it with some other Rom? Like DocX custom rom?
Yeah tried darkys 5.6 rom, does the same thing shows gt-i9000m logo then loops it self
dtran00 - that sucks man, but bell offers unlock codes so i dont' see how that can void your warrenty when you have to pay $70 for the unlock codes no?
Spudsicles - hopefully i won't have any troubles but i might end up throwing it at them lol
Seriously this is a good phone but the problems omgosh.

regarding everyone with the boot loop errors, Sounds like you have got the corrupted internal memory. This is a common problem everyone has been having including me. You will have to send the phone off at bell. I'm still waiting for mine to come back to me, sent it off Dec 1, although some people are reporting repair times within 5 business days.

To the best of my knowledge, that does NOT necessarily indicate flawed internal memory. I've experienced a few errors myself - one was a real SDCard issue which required repair while the others I was able to recover from.
Have you tried reflashing firmwares via Odin with the repartition option checked?
Have you tried booting into recovery using ADB? I'm not an ADB pro myself but do know it's possible. You'll have to google for instructions.

[Q] Help softBrick, or broken phone?

So This morning I decided to give my phone a restart, when I am holding the button to turn the phone one and the samsung boot screen comes on (the white one thats says I896 and samsung in white) and then after that it just goes blank and you can here it play that noise that it would normally make with the samsung boot screen.
After waiting on the blank screen for a few minutes I touched the buttons and the button lights came on. I pulled out the battery and I was able to boot the phone in the recovery screen where i tried to clear all user data and clear the cache, this did't change anything.
This phone was on android 2.1 stock build for rogers, with z4root and oclf (oneclicklagfix) v2 or v2.2 i think. I bought this phone on sunday so it is pretty new.
I am wondering what I should do about this, I spoke to my friend and he said He should be able to fix it with odin and even put 2.2 on it. If anyone has ever had this happen to them or they know anything about it i would be happy to know.

Rather than having your friend void your warranty, why not just return it?

if he purchased it from a reseller such as craigslist or ebay, then he might not be able to take his phone in though. Odin1click to stock usually solves soft-brick like issues though..

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.

Stuck at no command error and freezing

Hey guys,
I have a problem with this phone. I got my relative's note 8 for trying to fix ( i'm not android expert ).
As she says, for no reason phone freezed and shuted down. After that charging problem started, and battery doesn't show real percentage.
After that i got the phone, and tried to go factory reset in recovery menu. Now phone stucks at samsung logo. Sometimes it stucks at blue screen with "no command" text.
Phone doesn't works all the time also. For example, somehow phone charged %100, after that i tried to open it, it stucked at samsung logo. I tried hard reset, screen off and no more screen. After 4-5 hours it worked again, but stuck at samsung screen again.
I send phone to trusted local repair shop. They couldn't managed to fix also, they reported me that it should be motherboard issue and they can't do anything about it. I don't know did they tried to install stock rom again.
I see no reason for motherboard issue. No water, no big damage or something else happened to phone. There should be a way to fix this and i seek your support here.

Whaki said:
Hey guys,
I have a problem with this phone. I got my relative's note 8 for trying to fix ( i'm not android expert ).
As she says, for no reason phone freezed and shuted down. After that charging problem started, and battery doesn't show real percentage.
After that i got the phone, and tried to go factory reset in recovery menu. Now phone stucks at samsung logo. Sometimes it stucks at blue screen with "no command" text.
Phone doesn't works all the time also. For example, somehow phone charged %100, after that i tried to open it, it stucked at samsung logo. I tried hard reset, screen off and no more screen. After 4-5 hours it worked again, but stuck at samsung screen again.
I send phone to trusted local repair shop. They couldn't managed to fix also, they reported me that it should be motherboard issue and they can't do anything about it. I don't know did they tried to install stock rom again.
I see no reason for motherboard issue. No water, no big damage or something else happened to phone. There should be a way to fix this and i seek your support here.
Click to expand...
Click to collapse
I would go with what the repair shop said personally. They certainly know a lot more than I do. Unfortunately things do just break even with no error for the owner themselves.
It is definitely worth trying to flash stock rom with Odin though.

stonedpsycho said:
I would go with what the repair shop said personally. They certainly know a lot more than I do. Unfortunately things do just break even with no error for the owner themselves.
It is definitely worth trying to flash stock rom with Odin though.
Click to expand...
Click to collapse
Thanks for your thoughts, honestly i don't expect it to work again, but before throw away i want to try all chances