Related
Have been reading all the forums and had used the info here to put a custom ROM on my T-Mobile Wing. Unfortunately my Wing is now suffering a hardware problem and has to go back for a warranty replacement. This could obviously be a problem if it has a non-standard ROM on it. Because of this, I went ahead and grabbed the RUU_Atlas_TMO_US_4[1].10.531.3_4.1.13.37_02.83.90_Ship.exe file via the threads and attempted to reflash my phone.
I am running the flash attempt from a physical Windows XP system. My phone is fully charged. I have an active partnership set up with the phone and active via ActiveSync. I start the flash process and the phone reboots into bootloader mode as expected. The flash process gets to 1% then the phone reboots into regular mode again and the RUU reports that the flash failed.
Am I missing something?
Update: apparently I was missing something. I had read the thread indicating the phone reboots at 1% and 30% (though mine only rebooted at 1%), but I assumed it would go back into the boot loader automatically which it didn't. On a hunch I tried forcing it into the boot loader and the RUU continued. Weird.
Have you HardSPLed your phone before? If you have, you have to bypass the SPL... Rumor goes, flashing the stock RUU WITH USPL will do this for you. I haven't tried it so I don't know if this will work or brick the device.
I had my phone picked up for warranty this very day. It was running Itje's latest ROM before the 6.1 update, but it totally died on my the other day. So now I'm hoping they won't mind too much about the hard-spl ing and the flashing and the overclocking *cough*
Good luck restoring your phone though. Maybe they won't care, I'm hoping for that
I basically took ivanmmj's advice and wrote a lil guide, I hope it gets sticky'd. http://forum.xda-developers.com/showthread.php?t=364543
DaMyth said:
I basically took ivanmmj's advice and wrote a lil guide, I hope it gets sticky'd. http://forum.xda-developers.com/showthread.php?t=364543
Click to expand...
Click to collapse
Glad to hear it worked. ^_^ I think that's the second account I hear of it working, so it must be something that DOES work.
Not to raise the dead but good thing I found this thread, worked or me too. Anyone know anything about the warranty replacements tmobile sends out? I'm assuming a refurbished model but anyone know the type o condition they are in?
The model that I got as a replacement, oh so long ago, has been working like a champ since I got it. It looked brand new, but then again, the original had problems not too long after I first got it, when the Wing was still a pretty new device.
Thats good to know, should only have to last me a month or two seeing how tmobile in their infinate wisdom lost the cell tower near my house a few months ago and contract is done on the 29th.... hello tilt!! (or touch pro )
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
So I was hoping that anyone here could shed some light on an issue that one of my friends who just bought a Nexus is having. His N1 is bone stock, and is an AT&T model. Every once in a while, completely out of the blue, the screen will turn black and restart, but then enter an infinite boot loop, where the only solution is to remove the power adapter and battery.
In trying to pinpoint the problem, we have noticed:
-It really only tends to happen when the device is plugged in.
-It's not related to the battery, charger, or microSD (since we tried mine to no avail)
-It's probably not kernel, ROM, or radio related (we let it do the OTA 2.2 update, and the crashes were still present)
I don't understand why it only happens when the phone is plugged in. The phone isn't hot to the touch, so I doubt that the battery is over heating.
Any help will be greatly appreciated. Thanks!
PS. I tried searching, but the only mention of boot loops I could find were on custom ROMs and Kernels...
Exact Same problem and Phone here!!!
Just got it today too! Please any suggestions would be nice! Want to root this phone but to afraid there is a hardware issue!
My friend ended up calling HTC and they asked him to return it, which he did, for a full refund. Ironically, he ended up getting a Samsung Galaxy S (ATT Captivate variety). Nexus one, although less powerful, is more sleek in my book...
I've got almost the exact same problem on an AT&T N1 running Froyo FRF91, the two differences I have are that the phone does feel hot to the touch, and that it never happened on 2.1. If anybody has some info on this it would be greatly appreciated, but I will be calling HTC/Google in the next few days to see if we can resolve this problem.
Hey guys,
I had a very similar problem with my phone rebooting while charging especially on the Car Dock. I ended up doing an exchange with Google/HTC and received another unit. This one now has no problems with rebooting. I suggest calling and getting your units replaced. My guess is there was a bad batch that have hardware issues.
Jay
jpav80 said:
Hey guys,
I had a very similar problem with my phone rebooting while charging especially on the Car Dock. I ended up doing an exchange with Google/HTC and received another unit. This one now has no problems with rebooting. I suggest calling and getting your units replaced. My guess is there was a bad batch that have hardware issues.
Jay
Click to expand...
Click to collapse
What can I do if it is unlocked? Any chance they still help you out? Or just forget it?
I don't think it would hurt to just give them a call. I have read some forums where people have sent unlocked phones in for repair and then got them back fixed and re-locked. It is worth a shot instead of having a faulty phone. I did the exchange option and it did take me a while to get my replacement phone, but that was due to HTC moving their repair facility according to the tech. The techs that I have talked to have been helpful. If I thought a tech was no good I just hang up and try again with a different person.
Jay
I have been having pretty much the exact same issues.
I have an AT&T unlocked/rooted N1.
Random reboots frequently when the phone is charging via plug or USB for seemingly no reason. I thought it may have been an app, or combination of apps, so I tried a combination of different steps to try and find a solution.
Wiped data/cache
Wiped data/cache & fix apk permissions (Amon Ra 1.7.0.1)
Wiped data/cache and flashed the current ROM I was using again
Wiped data/cache and flashed different ROMs (both 2.1 and 2.2 w/proper radio) including MCR r16-21, PhoenRom, LeoFroYo, Cyanogen 5/6 RC1 and even tried intersectRaven's Kernel's
Reformated the SDCard both via gparted from Ubuntu live cd and Amon Ra's recovery 1.7.0.1
Swapped out the SDCard thinking possibly a bad block
And finally re-flashed back to shipping stock 2.1 and stock recovery w/successful OTA 2.2 install
All steps I was able to get my N1 to randomly reboot plugged in or not. I even had it sitting on my desk at work unused for 30-40 min (running CM RC1) and it rebooted with no user input what-so-ever. It happens more often while plugged in but was not limited to charging state.
All that said, I finally called support, took about 30 min total to arrange a replacement. This included a factory reset while on the phone with the tech and I was able to get the phone to reboot within a few minutes of first boot.
Take it for what it is worth, but I am positive that this is a hardware issue in my case. Just hope my replacement goes without penalty (unlocked and all) and that my new N1 doesn't have the same issues.
Hey guys, I've got a problem and am hoping the minds at XDA can help.
My brother and I both have a Nexus One and both have unlocked bootloaders. I've never had a problem installing custom roms or restoring back to the shipping rom, or suffered any problems whatsoever.
However his phone, suffers random reboots all the time. I unlocked his bootloader and from the very first Rom we had problems. I double-checked my methods and even tested it again on my phone with no problem whatsoever. So, he got back into town today and I restored his phone to the shipping rom (userdata, boot, system, radio, etc.) It still randomly reboots. I thought it might have been a bad battery and swapped it out with a different one, and I was able to mess around longer with the phone, but it still rebooted on its own accord.
I told him he could call HTC, but more than likely he would have to pay 180 dollars to replace the motherboard on the phone. He says he'll just deal with the random reboots instead of the possibility of paying the money.
Does anyone have any suggestions as to what the problem could be, because after reflashing the shipping rom I'm out of ideas. Another odd thing I noticed with his phone from the get-go was the haptic feedback and vibrations in general, they were barely noticeable, almost non-existent as compared to my and my friend's nexus one.
Ok, so Friday morning I woke up and my phone was stuck in exhibition (desk) mode. I had to remove the battery twice to get it to boot into android and stay there.
This is a NON ROOTED Captivate. Using stock Froyo from Kies.
After I get it into Froyo, I went to make a phone call, and then the dialer sends the call, and vanishes. The phone freezes. The call goes through, but I now have no access to the rest of the phone. No ability to use the dial pad, or even to shut off the phone. I have to manually remove the battery.
After 48 hours I was pissed off. I'm out of warranty with AT&T by a month because I bought it on launch day last year.
So I used Odin to reset it to stock Eclair, and tested it, worse than in Froyo! The phone actually froze and the call didn't even go through! So I re-updated via Kies.
I'm back to square one. I have no idea where to go from here. HELP! I don't want to suffer this until the Galaxy S 2's come out here in the states, and I don't want to flash it to a custom rom if at all possible. Resetting it to stock should have fixed the issue if it was software, right? So it has to be hardware, right? But how does that make sense that only the phone function would be affected?
HELP!
Thanks in advance,
Tiberius Reign
^ Any recently downloaded app, widget, etc. that could be suspect ?? Anything come to mind that u may have done right before this started ??
I see u went to stock eclair, but i ask the above just in case u might have reinstalled everything after u went stock.
I tested the phone without installing any apps. I had a worse problem. The damn phone rebooted. I upgraded back to Froyo, and it became manageable. I saw someone else who was having similar issues with com.android.phone freezing and locking up all the time. Mine does it some of the time, and it's getting worse. I tried the delvik clear etc that was listed, and it still didn't help.
I'm kind of at my wits end here.
A lot of us i think are starting to have this problem. I had started a thread a while back about it but was never able to solve the problem. here is my original thread http://forum.xda-developers.com/showthread.php?t=1168128
here are threads of other people having a similar problem that i have also replied in
http://forum.xda-developers.com/showthread.php?t=1204823
http://forum.xda-developers.com/showthread.php?t=1226807
i think would should all stick to replying back to one thread maybe this one because its newer, this way it can be easier for us to help each other find a solution to this problem.