Database Develop

Possibly a dead Kaiser, suggestions? (or purchase!)

So, I plugged my Kaiser (Tilt) into my computer the other day to charge it, and the next morning when I unplugged it, I noticed it was locked up. No biggie, I soft-reset it, and it came directly back to the bootloader (right before the bootloader shows is a white screen, that says "Loading image... No image found!", that flashes for a fraction of a second.
If I plug it into my computer at this point, Windows says the USB device has malfunctioned and it doesn't recognize it. I can't flash it ("connection error"), and it wouldn't hard reset.
Then it kinda came back to life, kinda. Suddenly it'll boot into WM. Windows still doesn't recognize it, but I used JumpSPL to get it into a bootloader, and tried to install a HardSPL on it so I could flash a new ROM (to this point it's been stock-only because it belongs to the company I work for). The HardSPL flash failed partway through, and then it was stuck in bootloader for real. At that point I tried flashing a stock ROM, and it kept failing at different points, never getting more than about halfway through.
Does anyone have any suggestions? Or, do you want to buy it? At this point it's mine (company doesn't want it back), so I'm willing to experiment freely with it. Right up until my Touch Pro 2 comes in and I lose interest
*** UPDATE ***
So after writing this, just for kicks, I decided to give re-flashing the original ROM one more shot (it's been off and untouched now for several days at this point) and the flash succeeded. We'll see where it goes from here

Good luck with your phone.. I hope all goes well.. If you find out what the problem was/is, let me know

Hey godefroi, im new to all of this, just bought a messed up tilt from my friend, and i want to know if you could givve me the link for the insturctions to refalsh my tilt

Just hit up AT&T's site (which redirects you to HTC's site) and download the ROM. The file you want is "_ATT Tilt_RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe", which was the latest update for the phone.

Seems it's not fixed. After playing around with it for a couple days, it's back into bootloader and stuck there. Taking out the battery and leaving it for a few hours brings it back for a while, but it seems there's no permanant fix. Next step will be flashing HardSPL and a custom ROM. I'll update when that happens.

awww dang, that sucks. thank you for tellin me. hopin your tilt comes out ok

Did you ever get this resolved?
Hey man did you ever get this fixed? I cant find anything on it.
I can get to a boot loader screen and it shows USB and when I plug it into my computer I hear the sound that it's recognized but my active sync wont connect.
This is what I posted earlier and a moderator killed the post because I didn't spend hours hunting for a solution first before posting. I don't think one exists but if there is I would be glad to know it. I have flashed this phone and my older HTC Wizard dozens of times with no issues so Im not a "noob"
Earlier today I was taking a picture and the screen kind of stuck so I has to soft reboot it.
It didn't come back up. I was left at the rainbow bootloader screen.
I tried holding the camera button down and rebooting but it didn't change anything.
I tried several different combo's of holding keys down and rebooting and it always came back to that bootloader screen.
So the next thing I did was to format my cd card and downloaded KaisDiagTest1.zip and then coppied the KAISDIAG.NBH image file from the zip on to the root of the sd card.
That worked fine and I was left at a screen saying SPL 1.00.OliNex.
Next thing I did is were I think I screwed up. I flashed it with _ATT Tilt_RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign _22.45.88.07_1.27.14.09R2_Ship.exe which is the ROM from the HTC site and I think I was only supose to use a custom ROM and now after it finished flashing the ROM it rebooted and is stuck showing loading ... on the screen.
It goes past the boot loader and is stuck at loading...
Please advise if there is anything I can do.
Cheers,
Chris
godefroi said:
So, I plugged my Kaiser (Tilt) into my computer the other day to charge it, and the next morning when I unplugged it, I noticed it was locked up. No biggie, I soft-reset it, and it came directly back to the bootloader (right before the bootloader shows is a white screen, that says "Loading image... No image found!", that flashes for a fraction of a second.
If I plug it into my computer at this point, Windows says the USB device has malfunctioned and it doesn't recognize it. I can't flash it ("connection error"), and it wouldn't hard reset.
Then it kinda came back to life, kinda. Suddenly it'll boot into WM. Windows still doesn't recognize it, but I used JumpSPL to get it into a bootloader, and tried to install a HardSPL on it so I could flash a new ROM (to this point it's been stock-only because it belongs to the company I work for). The HardSPL flash failed partway through, and then it was stuck in bootloader for real. At that point I tried flashing a stock ROM, and it kept failing at different points, never getting more than about halfway through.
Does anyone have any suggestions? Or, do you want to buy it? At this point it's mine (company doesn't want it back), so I'm willing to experiment freely with it. Right up until my Touch Pro 2 comes in and I lose interest
*** UPDATE ***
So after writing this, just for kicks, I decided to give re-flashing the original ROM one more shot (it's been off and untouched now for several days at this point) and the flash succeeded. We'll see where it goes from here
Click to expand...
Click to collapse

I never did. Every once in a while I can get it reflashed, but inevitably it stops working. Just like yours, I'll sfot reset it and it'll be stuck in bootloader.

Best bet is when it gets stuck on the bootloader or on the "white screen" as to put it. Do the following:
1) Unplug battery, memory car and simcard. Reinsert battery ONLY after 3 seconds (cards stay out!)
2) Hold BOTH softkeys down at the same time
3) Whilst holding softkeys, turn the unit on
4) You will be prompted to press "SEND" to reset all user data (you will lose everything on the internal storage. Press the Dial (green button) to reset.
5) When it's finished, you will be prompted to press "SEND" to reboot. Press send and it will boot into WM but might take slightly longer.
6) Realign your pointer and tada. It's up and running.
n.b. This often happens when the radio version of your phone isn't correct. If you notice, when you get stuck in the "white screen" the "gsm signal sight" is frashing green!
I've got to warn you again, this procedure WILL delete all of your internal user storage, hence why I recommend taking out all of the cards before proceeding.

heyadrian said:
Best bet is when it gets stuck on the bootloader or on the "white screen" as to put it. Do the following:
1) Unplug battery, memory car and simcard. Reinsert battery ONLY after 3 seconds (cards stay out!)
2) Hold BOTH softkeys down at the same time
3) Whilst holding softkeys, turn the unit on
4) You will be prompted to press "SEND" to reset all user data (you will lose everything on the internal storage. Press the Dial (green button) to reset.
Click to expand...
Click to collapse
Nope. Stuck in bootloader is stuck in bootloader. Like, stuck. No, really, it's stuck. Hard-resetting doesn't get it out.
heyadrian said:
n.b. This often happens when the radio version of your phone isn't correct. If you notice, when you get stuck in the "white screen" the "gsm signal sight" is frashing green!
Click to expand...
Click to collapse
There's no white screen, just bootloader rainbow. Also, there's no chance that I flashed the wrong radio, because this phone has never been flashed with anything but the official ROM. It's never even had a HardSPL flashed on it.

hmmm...now that you mention it has never had a hardSPL, maybe that could be the next step?
i understand that some people may want to keep a "stock" configuration in case waranty needs to be claimed or for any other valid reasons...but if the phone is out of waranty, theres little to lose.
only reason i'm suggesting it is because cmonex has a hardSPL that aims to fix EXACTLY this problem, among others (if i understand your problem and cmonex's fix correctly):
http://forum.xda-developers.com/showthread.php?t=420683
also, this thread links to a page in the wiki about your problem (or something along the same lines):
http://forum.xda-developers.com/showthread.php?t=423486
finally, a collection of hardSPL versions can be found in this "roll up" thread:
http://forum.xda-developers.com/showthread.php?t=498320
i guess you may have already gone through the above mentioned links but if not, they may open up more avenues for troubleshooting or even a permanent resolution.

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

[Q] Bell Vibrant will not go Pass the Galaxy S logo once powered on

Hi all
I would like to thank everyone in advance and hopefully someone will be able to guide me to resolve my concern, Bell Samsung Vibrant will not go Pass the Galaxy S logo once powered on.
-Was the Phone ever rooted in the past? No, it's less than 2 weeks old, First ever Android, previous Windows mobile/ Iphone User.
-Did I encounter any error? Yes, Invalid or Damaged internal SD, I believe my main mistake was taking the battery off while the device was left powered on. The device was stuck on a loop cycle then after.
-Did I install any Apps on an External SD card? No, never got a chance to.
- Why not save the hassle and just return/ repair phone from your carrier? Unit bought online from craigslist and was not provided with a receipt, Paid a decent price and confirmed IMEI doesn't have any negative file from carrier at the time of purchase.
- Did I contact Samsung Canada at all? Yes and they won't take any accountability as the carrier must follow their own repair/ return process.
Just a Summary of what was done:
Charged and attached for atleast an hour.
- Tested by plugging it to the Wall charger (Device assumed OFF), the screen goes on a loop cycle from the Galaxy S Logo to a blank black Screen back to the Galaxy S logo and so on.
-Attached and tested ALL USB ports (Windows 7 64 bit) and the screen goes on a loop cycle however this time I get a drained battery logo and a stuck time capsule in the middle of the screen.
Downloaded Samsung softwares: Kies_1.5.1.10074_2_6, Kies_1.5.0.10024_74, Kies_1.5.1.10074_45.
-The device only goes on a loop cycle from a drained battery logo back to a black screen while connected to the USB port. It appears the device is not being detected. No visible partnership between Bell Vibrant device and the Kies drivers.
Desperate to attempt anything, I even tried rooting the device by attempting all possibilities to get it to Recovery mode or Download mode however my best efforts did not avail. Before anything was attempted, I confirmed the device was powered off first before taking the battery out.
-Held down the Up volume button and Power button and released the power button only
-Held down the Down volume button and Power button and released the power button only
-Pressed Up volume, Down volume button and Power button and released the power button only
-Held down the Down volume button, Home button and Power button and released the power button only
-Held down the Down Volume button, Home button and Power button and released the Home(middle) button only
-Held down the UP volume button, Home button and Power button and released the power button only
-Held down the UP volume button, Home button and Power button and released the Home(middle) button only
Also downloaded Update.zip and android-sdk_r06-windows.zip
-extracted and confirmed SDK was installed successfully however my device was not detected. Ran from CMD [unable to enable the USB debugging in Applications]
-confirmed the how to steps taken intended for Bell.
Im still optimistic that I can expect the best possible outcome from this situation or I have to hunt down the individual who sold the device
Please verify if I can attempt an alternative or if took a wrong turn with any of the steps mentioned above.
If you live locally in Toronto [GTA] and would like to take on this challenge, Please PM me..
Feel free to drop your comments as to how this issue can be resolved. Please!
Thanks in advance!
Kind Regards,
mamasboy

Update: 3:00am
Hours later and still no luck!
Any ideas how I can approach Samsung Canada directly and have them deal with the situation?

here is a post here on how you can access using something called ADB ? It can be used apparently where the three button recovery can not be entered. Try looking under three button recovery in the search on the forum. Hope this helps.

How i get into recovery mode is by restarting the phone by holding the power button and continuously tapping all 3 Home +power+ vol up at the same time
And if it works it will go into the recovery mode before the screen changes.

see if you can boot into recovery mode
wiki has instruction to get into recovery mode http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/Vibrant_GT-I9000M
once in recovery mode, try the data wipe option, also the cache wipe option
then reboot back to normal

Tehpriest said:
here is a post here on how you can access using something called ADB ? It can be used apparently where the three button recovery can not be entered. Try looking under three button recovery in the search on the forum. Hope this helps.
Click to expand...
Click to collapse
Hey,
The SDK was successfully updated. It downloaded all the new patches and required files, the sdk does work however when I get to the point of:
adb device (Hit enter)
list of devices attached (blank entry)
-even attempted other commands but getting error: device not found

NezumiYaro said:
How i get into recovery mode is by restarting the phone by holding the power button and continuously tapping all 3 Home +power+ vol up at the same time
And if it works it will go into the recovery mode before the screen changes.
Click to expand...
Click to collapse
Hey NezumiYaro,
Thanks for the tip but still no luck

AllGamer said:
see if you can boot into recovery mode
wiki has instruction to get into recovery mode http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/Vibrant_GT-I9000M
once in recovery mode, try the data wipe option, also the cache wipe option
then reboot back to normal
Click to expand...
Click to collapse
Hey AllGamer,
Thanks for the help and I checked the link and reviewed and re-attempted but still to no avail..
I may have the disabled recovery/download mode Bell batch and it seems the only option out of this is to get the device replaced

I had the same problem...Currently Samsung is 'repairing' my phone. Instead of going through all this trouble, I would rather suggest you to go and exchange it.
If they dont replace the phone for you, just call samsung social hub help desk (1-888-751-4078). They will give you a ticket number and then you can send your phone to samsung via any Bell corporate store.
The samsung social hub guy told me that it would take 5 business day to repair but the person at Bell store told me that it can take 2-6 weeks.

I'm in the same boot as you, altough i'm in a different country.
nevertheless, same sh*t
I did however discovered today that when I start the phone, connected trough usb, I does detect what seems to be a part of the phone, have a look at this image (was done on a XP virtual machine, but my WIN7 does the same.
I get a G: and a H: in the device manager.
But I cannot access those, maybe or maybe not, this might be our only hope, before I send it back.
But I refuse to give up (yet)

Exact same problem you had. Phone would not load past Galaxy S logo. I did not hack or root my phone either. Seems this is becoming a larger issue. Recovery mode was disabled on my phone too. It is now with Bell being sent for repair. I would suggest you do the same, I wasted 3 days trying to get the phone into recovery mode to no avail. If Bell has any in stock they may swap for you. They did not when I took mine in unfortunately.

nalinbhatt said:
I had the same problem...Currently Samsung is 'repairing' my phone. Instead of going through all this trouble, I would rather suggest you to go and exchange it.
If they dont replace the phone for you, just call samsung social hub help desk (1-888-751-4078). They will give you a ticket number and then you can send your phone to samsung via any Bell corporate store.
The samsung social hub guy told me that it would take 5 business day to repair but the person at Bell store told me that it can take 2-6 weeks.
Click to expand...
Click to collapse
Wow thanks 5 business days is acceptable. I'm currently back on my Windows Mobile device as a back up phone for now. I will definitely give them a call first thing tomorrow morning!
This is what concerns me going down the road. Any of you recall the Samsung Instict? aka Iphone Killer.. "roll eyes" Could it be that Samsung didn't put enough research and development into the Operating System/ Hardware and deployed the Galaxy S series prematurely? One can only ponder...
To be continued...

nalinbhatt said:
I had the same problem...Currently Samsung is 'repairing' my phone. Instead of going through all this trouble, I would rather suggest you to go and exchange it.
If they dont replace the phone for you, just call samsung social hub help desk (1-888-751-4078). They will give you a ticket number and then you can send your phone to samsung via any Bell corporate store.
The samsung social hub guy told me that it would take 5 business day to repair but the person at Bell store told me that it can take 2-6 weeks.
Click to expand...
Click to collapse
patj3 said:
I'm in the same boot as you, altough i'm in a different country.
nevertheless, same sh*t
I did however discovered today that when I start the phone, connected trough usb, I does detect what seems to be a part of the phone, have a look at this image (was done on a XP virtual machine, but my WIN7 does the same.
I get a G: and a H: in the device manager.
But I cannot access those, maybe or maybe not, this might be our only hope, before I send it back.
But I refuse to give up (yet)
Click to expand...
Click to collapse
Hey patj3, it seems you have a better chance than the rest of us. Attempt to delete or uninstall what you highlighted in yellow, unplug device, reboot computer and before you plug the device, Install the latest kies software from Samsung and allow it to fully install. It's missing drivers and is unable to recognize the unit. search "[GUIDE] ADB, Fastboot, and Nandroid for Noobs" here in XDA.
Good luck, I may be throwing the towel as early as tomorrow

xZeDgEx said:
Exact same problem you had. Phone would not load past Galaxy S logo. I did not hack or root my phone either. Seems this is becoming a larger issue. Recovery mode was disabled on my phone too. It is now with Bell being sent for repair. I would suggest you do the same, I wasted 3 days trying to get the phone into recovery mode to no avail. If Bell has any in stock they may swap for you. They did not when I took mine in unfortunately.
Click to expand...
Click to collapse
Thanks for the feedback..
I know, my mind is about to explode!
Unfortunately, I'm pass the 14 days/ 30 minutes requirement for Bell's D.O.A policy and sending the device out for repair is my only option.
Post back and let us know your repair experience with Bell and their turn around time.
Cheers

Just an update..
I went through the regular repair process, it looks like I'm looking at 3-6 weeks.
Regards..

I had the exact same problem except I rooted it and it was after I applied a lag fix but luckily it wasn't even a week before I got the phone so I just brought it in and bell gave me a new one on the spot lol. Hope you can get it repaired.

The same problem here also. I did not root it or put anything aftermarket. Only unlocked it with a code. Bestbuy did not want to do anything because it is 4 days pass the 30 day mark, not talking about the 14 days 30 min. I spoke to Samsung support and they told me to go to Bell store and have it sent for repair. I did complain to Samsung that it is unacceptable to have a 34 day use of a device and 2 months for repair. Now I am waiting for the superviser of the tech suppoert to call me by the end of the day today, but no news from hem yet. Tomorrow first thing in the morning I am calling again Samsung to look for the superviser of the superviser.
P.S. Bell did not ask me for an account number of phone number with them. Only took $47.00 in case if there was a water or mechanical domage. It is refundable.

mamasboy32 said:
Thanks for the feedback..
I know, my mind is about to explode!
Unfortunately, I'm pass the 14 days/ 30 minutes requirement for Bell's D.O.A policy and sending the device out for repair is my only option.
Post back and let us know your repair experience with Bell and their turn around time.
Cheers
Click to expand...
Click to collapse
thats the refund policy. doa is 30 days on the spot replacement as long as it says i9000m on the logo before it gets stuck.

Idan73 said:
thats the refund policy. doa is 30 days on the spot replacement as long as it says i9000m on the logo before it gets stuck.
Click to expand...
Click to collapse
What if they dont have it in stock?
That was case with me,
so i went to another bell corporate store,
they send me away, claiming that only the place you got it from can replace it.
its been now 20 days with the phone, and the guy (bell corporate location) does not have it in stock,
he says he does not know when he can get it.
so i dont know if there is truly a shortage, but that is what they are telling me.
help.

if it makes you feel any better
I've had one on order through my corp plan at work for over a week, usually if quantities are low it will say so on the ordering site, or it will say on backorder, well it didn't, they don't have them, supposed to get a shipment this week, shipment hasn't arrived yet.
this will be my 2nd crack at a Vibrant, the first one was riddled with small yet important issues as well as the GPS didn't work. Hoping for a better one this time, if not I'll try and get a 'Desire Z' down the road.
Neil

[Q] Bell Galaxy S Stuck on logo Screen

Ok I have read about 50 different posts that are similar to my situation but none of them seem to be exactly what I'm looking for. Here is what is happening with a little background.
Running Stock 2.1 on a BELL Mobility Vibrant.
No Custom Roms.
I did have the OCLF installed (Almost 3 months ago without issue)
Phone is also Rooted
Last night I was at a friends place showing off my phone as they were ready to get a new one. I showed them all the cool apps, google maps, google Sky, Soundhound, Bar Code Scanner, etc.. They were sold and are no longer getting an iPhone.
I came home and went to bed. I woke up this morning and the phone was off.. I turned on the phone and once it booted up it said the battery was dead.. No problem.. Power the phone down.. Replace battery and reboot.
It would not reboot.. it gets stuck at the Galaxy S logo screen
My phone is one of these earlier models that doesn't have access to the 3 button recovery so I was using the ADB reboot-recovery to access the menu.. However, this no longer works.. it just reboots the phone and gets stuck at the logo.
I have tried ADB logcat and it just loops and loops.. (Thousands of lines of data)
I have tried a few different batteries.. I have tried powering it up connected to a wall outlet (power) as well as to the computer (it does detect the USB and makes the USB connect sounds (windows7))
Keis and ODIn both don't see the device.. (Not surprising)
Have tried 3-4 different methods to get to the download screen as suggested in other posts and none of them work.
Is there anything else I can try short of taking the phone back to Wireless Wave?
Just uploaded a dump of the logfile from AGB Logcat Cmd. In case that helps.

If you can't get the download screen, then your best bet is making a homemade jig. Search google for how to make one. I made mine when I encountered this problem and it works every time when I am unable to get a download screen.
I guarantee that it'll work for you as well. Good luck.

[HOWTO] [REF] Get Download Mode without 3-button combo using homemade JIG

Can you clarify? Are you unable to get into recovery AND download mode?

gtg2 said:
Can you clarify? Are you unable to get into recovery AND download mode?
Click to expand...
Click to collapse
Hey...my phone is currently stuck at a boot screen loop and it doesnt stop doing it. What can i do to fix this? I am able to get into download mode but not recovery mode. i know how to use odin, but can anybody guide me to which files i should use to put into odin to fix my phone? please help, thanks!! BTW, my phone is i9000 from BELL CANADA also!

Alright, follow this link and you'll get your three buttons working.
http://forum.xda-developers.com/showthread.php?t=785201
Make sure you get ODIN v1.3 and not v1.0 because the older one doesn't have a bootloader flash option.

zumi78878 said:
Hey...my phone is currently stuck at a boot screen loop and it doesnt stop doing it. What can i do to fix this? I am able to get into download mode but not recovery mode. i know how to use odin, but can anybody guide me to which files i should use to put into odin to fix my phone? please help, thanks!! BTW, my phone is i9000 from BELL CANADA also!
Click to expand...
Click to collapse
My Galaxy S from Bell is doing the same thing I spent 6 hours yesterday and so far 3 hours trying to get a replacement over the counter and so far its go to where you got the phone (Future Shop) they say only 14 day return window on this phone and mine started do it 16 days after i got it. Future shops says to go to Bell Store. Bell Store says Future shop should be handling this. now I am on my second call to Bell Corp and they are trying to keep me as a customer since I told them if this is not fixed today or replaced I am send the phone back and they can take their 3 year contract and stuff it.
so far looking good she is being very understanding and trying to help me
we shall see how this will go..
well 2 hours on the phone with them and the rep Named Laura is doing her best to get me a swapped phone today but she keeps hitting roadblocks between Future Shop and her own jobs corporate policies
with Bell this phone is 30 Days for straight across exchange but with Future Shop this is a 14 day policy since my phone died at day 16 its no longer covered by Future Shop and Bell hasn't been able to help me yet.
Laura is now trying to go above her bosses heads' and do good for me they have notes that my phone is considered DOA and should just be swapped by Bell Stores wont help me due to this phone being purchased at Future Shop
oh so frustrating...
UPDATE:
well after 2.5 hours on the phone with Laura and full of empty promises she cannot do anything for me Future shop has a 14 day policy Bell has a 30 Day policy and the phone is now 17 day old and nothing but a brick.
so I am heading to the nearest Bell store and dropping off the Phone and telling them to stuff the contract and all my bills good riddance.

nyk0n said:
so I am heading to the nearest Bell store and dropping off the Phone and telling them to stuff the contract and all my bills good riddance.
Click to expand...
Click to collapse
Let us know how that goes.

I predict the first murder in Canada inside a mobile phone dealership occurs in the next month over a Galaxy.

Nexus 6 (rooted, stock rom) won't turn on anymore. Please help

Hello everyone,
I'm experiencing a pretty tough issue mith my beloved (and, so far, flawless) Nexus 6. It had root and a stock rom on it, 6.0.1 (MMB29V). I had unlocked the bootloader and rooted the phone right after buying it more than a year ago and I've been flashing new factory images a couple times (specifically when 6.0.0 and 6.0.1 were released). I usually do everything via Wugfresh's NRT, not because I can't use adb and fastboot, just because it works fine and I'm lazy.
Yesterday, while I was working, I used "Tiny Scanner Pro" to scan a document (legit copy bought on the store, as any other premium app in my phone) and it got stuck for a while, then a popup about Google Play Services came up. I dismissed it and another appeared, and it kept going like that. I was at a client's and I was in a hurry, so I took the pic with my tablet and forced the phone off. Later I turned it on, it seemed to boot regularly, but when the SIM unlock screen appeared and I entered the (right!) PIN, it said that no SIM was found, then the home screen appeared but after a while the screen went black and it started rebooting. Recovery (TWRP) and fastboot were working, so I decided to take it home and re-flash the stock rom: it had been a while since the last time anyway, a new version was out and the OTA update notification was getting annoying. I connected to my PC in recovery mode and transfered my pics and data via adb while I downloaded the latest stock rom (6.0.1 MOB30D). Then I user NRT to flash it (selecting "Soft-bricked/Bootloop" as current status). It appeared to work fine as it went through the usual copying and unpacking. Then, when the phone was supposed to reboot, it just blacked out. I waited a long time, in fact I went out and came back a few hours later, and it was still that way. Now it doesn't power up, no matter how long or hard I press any combination of the three buttons, adb and fastboot do not detect it in any way, of course, and it doesn't seem to charge either (i.e. I left it plugged to its original charger overnight and it still feels dead cold). By the way, the phone warranty shouldn't have expired, but I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
I've taken a look at similar threads but none of them describes the very same situation. Is there something, anything I can try to do before giving up? I hope somebody can help me. I thank you all very much in advance.
lupus

lupusyon said:
.... I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
Click to expand...
Click to collapse
Bricked!. When the phone is still under warranty send it for repair. Do not use arguments.
Just: phone will not switch on and does not charge.

Because this is a Nexus device, the custom recovery shouldn't affect your warranty. It is however, a moot point. The device is totally dead, and a call to Motorola is in order.

lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...

dahawthorne said:
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
Click to expand...
Click to collapse
I bought it on Amazon Italy Marketplace, I'm not sure if they're supposed to handle the thing or if I should contact Motorola. I'll just check with them first. Thank you everybody for the kind advice, I'll let you know how this turns out. :good:

I confirm what dahawthorne wrote above: it took them about a month but Motorola repaired my Nexus under warranty, no questions asked. It seems they replaced the Mainboard PCB.
Thanks everybody!