Related
Hi all
Anyone here had any experiences of returning a flashed phone for a warranty claim? I wonder how carefully they inspect the set-up. I'm suffering very bad battery life (<4 hours) and a dead camera on my Vario II, but I'm sure T-Mobile won't accept a claim (WM6, Radio 1.43, HardSPL, unlocked etc).
I can revert some things, for instance I got the original T-Mobile WM5 installed OK but can't find the original Radio ROM (1.05).
If there's no hope I'll just open the bugger up and try jiggling the camera connector or just remove it completely!!
sim
if youre returning your phone to a brick and mortar store then as long as it looks unmodded then I don't think they'd notice. Like if you reflashed with the provider's logo, etc.... they are just sales people, MOST of them know very little about any technical aspect of the phone. From my experience of getting one of my phones exchanged the reps I spoke to were not able to answer my technical problems, which is why I replaced it... so i say go for it
Hi zammykoo,
Do they not send it back to a service centre for evaluation? I'm a bit worried that even if the shop gives me a replacement on the spot, they might check out my busted model later and then slap me with a penalty fee or something.
sim
what exactly is the problem you are having with the camera? if it is under warranty then shouldn't it cover manufacturer defects like that? if that is the case. and it should apply to the bad battery life too, if those things were not caused by you (like water damage, they can tell) then they wouldn't have anything to say..... but as far as software reflash then i really don't think it'll matter cause they will probably reflash it themselves to clear out any previous user settings before putting back on the market
Hi there,
I just found an official WM6 flash from T-Mobile UK, so I've flashed that and taken it back to the shop for repair. Thought I'd take a chance as the phone is effectively useless at the moment (camera is dead and battery loses 20% per hour).
Thanks for your advice!
sim
Undo HardSPL? Mtty's format command clears everything?
Hi...I have a few questions about this topic as well.
It looks like my radio (hardware) died on me after a soft reset...I'd been having some problems with it before then. Anyways, I went through my provider's warranty exchange and I'm about to send my old handset back. My questions:
1) I'm stuck in the bootloader screen, since I couldn't upgrade my radio. I have Hard-SPL installed on my device, and you can see that (it says "Olipro" in the bootloader screen). Is there any way to remove Hard-SPL, or do you guys think I even need to worry/bother with that?
2) In the process of trying to reflash my phone and fix things myself, I used mtty and its format command...What exactly does that format? Is my phone's memory completely clean? That's fine by me if it is; I don't think that would be an issue with service personnel. I'm just wanting to know exactly what mtty's format does.
In addition, if anyone else has had to make a return under similar conditions, I'd appreciate hearing about your experience. THANKS!
i dont think any spl have a format command!!!!
r u kidding???
No, SPL's don't have a format command (that I know of!); I used this utility called mtty...I read about it here in the forums; it comes in handy when you're trying to recover from a bad flash, I think.
Anyone else have an answer to my questions?
1) I'm stuck in the bootloader screen, since I couldn't upgrade my radio. I have Hard-SPL installed on my device, and you can see that (it says "Olipro" in the bootloader screen). Is there any way to remove Hard-SPL, or do you guys think I even need to worry/bother with that?
2) In the process of trying to reflash my phone and fix things myself, I used mtty and its format command...What exactly does that format? Is my phone's memory completely clean? That's fine by me if it is; I don't think that would be an issue with service personnel. I'm just wanting to know exactly what mtty's format does.
Click to expand...
Click to collapse
I had no problem with AT&T returning several unlocked and upgraded phones for replacement.
Thank for the response...
tvone said:
I had no problem with AT&T returning several unlocked and upgraded phones for replacement.
Click to expand...
Click to collapse
tvone, thanks for taking the time to respond; I appreciate it.
Based on what you're telling me, I guess I won't worry about "downgrading" from HardSPL before taking it in.
If anyone has a different experience - or would just like to provide more reassurance (I'd love to have it!) - please let me know soon...I'll be taking care of this today!
THANKS!
Hi,
I have a Jasjam which is getting NoGSM errors. I believe this may be causing my hanging issues that I've been having a lot of.
I've had a look at the Wiki page on this, and a couple of things aren't very clear.
I'm currently running Bootloader SPL-1.10, and it says to go back to 1.04. Can I change to SPL-2.10Oli to do this as well (I guess this is easier).
Also, after this step, it says to Flash the patched radio to simunlock my jasjam, however it is already simunlocked.
I just wanted to clarify these things before giving this a go, so if anybody can enlighten me it would be greatly appreciated, as it is really starting to get to me.
Thanks for your help.
Paul
NoGSM Error in Jasjam - clarification of wiki
Just wanted to change the title...
Just wanted to bump this to see if anybody can help me out. I'm still having NoGSM problems, have tried the fix on the Wiki, but things aren't completely clear, as so far it hasn't made any difference.
Sorry mate, probably because no-one HAS a surefire method to fix the "No GSM" problem. Lots of people claim that something fixed it but they seem to keep popping up in the threads still trying to fix their problem. You might have to just try everything until you either give up or something noticeably improves or someone pulls the answer out of thin air.. We all live under the threat of "No GSM" and dread the day if/when it will finally arrive... Sorry to be the bearer of bad news but you can shoot me til your hearts content.
Cheers...
Thanks for that, so pretty much I should keep on trying to flash different radios until I find one that sticks around for a while?
Would try to flash a stock rom 1st. What Telco are you with? Use their "Official"rom and see if that works. THEN go nus trying radio only roms. Chances are though that if you can't flash 1 radio rom your radio has been corrupted and is unrecoverable.
Good Luck
ultramag69 said:
Would try to flash a stock rom 1st. What Telco are you with? Use their "Official"rom and see if that works. THEN go nus trying radio only roms. Chances are though that if you can't flash 1 radio rom your radio has been corrupted and is unrecoverable.
Good Luck
Click to expand...
Click to collapse
Hi, I've got a Jasjam (so therefore it's a Telstra phone). I've gone from the official rom to unofficial roms and back again. I've installed individual radio roms. Most things go onto the phone fine, and it will work perfectly for maybe half a day, and then it crashes, and when I restart I get NoGSM. I might reset it 5 times, and then the radio will come back.
I bought it on ebay, but I've managed to get hold of the details to get a duplicate invoice, so I've put the phone back onto Telstra ROM and a standard SPL, and I'm going to get them to have a look at it, as it looks as though it's a hardware problem, unless any of you smart bods here have other ideas...
Can anybody shed any extra light before I take it into the shop? Just don't want to admit defeat if I can
If you can, the best way to fix is through warranty. If they try to fix 3 times and fail they have to give you a new handset. I believe Telstra no longer have the jasjams so you might be upgraded to the Tytn II.
Cheers....
So I'm sure that the majority of the people that are going to read this thread have already read about the spacing problems that people have been experiencing with 6.5. I was one of the people that flashed the first build from Da_G that had the spacing issue, and figured I would flash another rom to solve the problem.
I flashed another rom, and the problem still existed. I was getting either no spaces between words (randomly) or two spaces. No big deal, I figured, I would just flash another rom.
So I did; and I still had the problem. This was getting annoying. Back to 6.1. So I flashed to 6.1. Still the same problem. WHAT THE %&[email protected]! I thought. I guess the chef cooked in some of the 6.5 files into 6.1 or something. Now this was getting REALLY old. I needed to end it quickly.
That brings me to tonight, when I flashed the official latest at&t fuze rom straight from htc's website. I KNEW this would be foolproof. And guess what.
IT STILL HAS THE PROBLEM!!!!!!!!!!!!!!
So my question is: after flashing numerous times, and soft resetting of course, how is it possible that this problem still exists? It happened exactly after flashing the rom that everyone else had spacing problems with, and hasn't gone away.
PLEASE. Someone help me. I can't even use the device and it's getting to the point where I'm really close to just dumping it and going to get something else. I hope someone out there has the answer.
which keyboard or input are you using, I've been on Da G's, NRG's, Shep's and the latest at&t stock rom, wm6.1 and wm6.5 and don't have any issues. I have issues with input on certain areas of the TF3D2 stuff but nothing with spaces.
flyboy009 said:
which keyboard or input are you using, I've been on Da G's, NRG's, Shep's and the latest at&t stock rom, wm6.1 and wm6.5 and don't have any issues. I have issues with input on certain areas of the TF3D2 stuff but nothing with spaces.
Click to expand...
Click to collapse
I've used almost every possible configuration with everything, and the problems I am experiencing is with the hardware keyboard. But I've used the new ezinput2, old ezinput, abc, xt9, enabling and disabling auto correct and the other options, and ive also tried a cab by monx that didnt seem to work. I'm completely out of ideas. The fact that ive flashed over the original tons of times and the problem still exists RIGHT AFTER the flash, before I even touch anything, baffles my mind.
djcaston said:
I've used almost every possible configuration with everything, and the problems I am experiencing is with the hardware keyboard. But I've used the new ezinput2, old ezinput, abc, xt9, enabling and disabling auto correct and the other options, and ive also tried a cab by monx that didnt seem to work. I'm completely out of ideas. The fact that ive flashed over the original tons of times and the problem still exists RIGHT AFTER the flash, before I even touch anything, baffles my mind.
Click to expand...
Click to collapse
Is it not possibly you've just got a duff space key on your keyboard, and it's nothing to do with the ROM?
Cheers,
Steve.
StevePritchard said:
Is it not possibly you've just got a duff space key on your keyboard, and it's nothing to do with the ROM?
Cheers,
Steve.
Click to expand...
Click to collapse
Although I've thought about this, it woul be EXTREMELY strange if my space bar decided to crap out in the exact same way and at the exact same time that everyone else started having issues
djcaston said:
Although I've thought about this, it woul be EXTREMELY strange if my space bar decided to crap out in the exact same way and at the exact same time that everyone else started having issues
Click to expand...
Click to collapse
"Its like rain on your wedding day or a free ride when you already paid"
compressed air/hair dryer with a cooling switch
"its the good advice that you just didn't take and who would of thought, it figures. isn't it ironic"
k that was lame
djcaston said:
So I'm sure that the majority of the people that are going to read this thread have already read about the spacing problems that people have been experiencing with 6.5.
Click to expand...
Click to collapse
Never heard of it and have flashed 6.5 ROMs many times.
Back to 6.1. So I flashed to 6.1. Still the same problem.
.
.
That brings me to tonight, when I flashed the official latest at&t fuze rom straight from htc's website. I KNEW this would be foolproof. And guess what.
IT STILL HAS THE PROBLEM!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Yeah, no. I think what you are experiencing is a problem that your DEVICE is retaining, not a defect in each and every ROM you happen to flash. It is either something not getting flashed correctly or a hardware problem or something else that you are installing each time. If there ARE other people with this problem, get them together in a thread like this and share notes.
I havent had any space issues.
You said you've done tons of soft resets, but have you done any hard resets? If not, that is the very first thing that I would do if I were you. I suspect it's a hardware problem, but a hard reset may cure your ills. If you do this, don't run UC or install anything until you've tested the keyboard. You haven't mentioned what you do to customize your device (like run a sprite restore, lol?), but before you blame someone else, you should do a hard investigation to make sure you're not screwing things uo yourself.
As I'm sure you already know, the Custom ROM Flash tool has been modified such that it does not issue a full wipe of the flash. Therefore, it's possible that some bits are still set. When I experience such occasional anomalies, I have resolved them by applying the official HTC 5.05.405.1 WWE (6.1) stock ROM to my device.
Here's the thread:
http://forum.xda-developers.com/showthread.php?t=478657
This will downgrade/upgrade your Radio and change the Splash; you can always re-apply your personal favorites afterwards.
Once installed, I use the CWSLayout registry entry to change the keyboard and test all of the features of the device. In your situation, if the keyboard remains "broken", it's would indicate that the keyboard has somehow failed and requires replacement or servicing.
HTH,
Anyone Else Have HW Space Bar Problems?
BigBadger said:
Never heard of [the space bar problem]...I think what you are experiencing is a problem that your DEVICE is retaining...If there ARE other people with this problem, get them together in a thread like this and share notes.
Click to expand...
Click to collapse
VERY pragmatic approach!
Farmer Ted said:
You said you've done tons of soft resets, but have you done any hard resets? If not, that is the very first thing that I would do if I were you. I suspect it's a hardware problem, but a hard reset may cure your ills. If you do this, don't run UC or install anything until you've tested the keyboard. You haven't mentioned what you do to customize your device (like run a sprite restore, lol?), but before you blame someone else, you should do a hard investigation to make sure you're not screwing things uo yourself.
Click to expand...
Click to collapse
This is the advice I was going to give as well. It's recommended that you hard reset after every ROM flash once you get to screen alignment to wipe out any data that may have been retained.
fb401 said:
This is the advice I was going to give as well. It's recommended that you hard reset after every ROM flash once you get to screen alignment to wipe out any data that may have been retained.
Click to expand...
Click to collapse
Completely agree, a hard reset pre or post ROM flash is always good practice.
I've been using the following sequence (recommended by a few senior members) for several months now and results have been positive.
Hard Reset: Volume Down & Action & Reset/Power On
Hard Reset: Volume Up
Bootloader: Volume Down
Lastly, I'm not an advocate of using Backup applications in situations where different versions of ROM's are frequently flashed. It introduces too many "unknowns".
Cheers,
Do a Task 29 in mtty
I will say if you can't figure it out and your device is till under warranty, flash back to original and ask for a new one. claiming defective product.
That's really weird I had the exact same problem. I thought it was my space key, so i got a warranty replacement saying i had lost my phone, meaning I still have the old one. I will have to test when i get home and see if it was the hardware keys or something to do with the ROM. After getting a new phone I did notice my space key was a little sloppy, so I immediately assumed this was the problem. Hopefully I was wrong and have 2 working phones.
edit: nevermind forget it.
djcaston said:
So I'm sure that the majority of the people that are going to read this thread have already read about the spacing problems that people have been experiencing with 6.5. I was one of the people that flashed the first build from Da_G that had the spacing issue, and figured I would flash another rom to solve the problem.
I flashed another rom, and the problem still existed. I was getting either no spaces between words (randomly) or two spaces. No big deal, I figured, I would just flash another rom.
So I did; and I still had the problem. This was getting annoying. Back to 6.1. So I flashed to 6.1. Still the same problem. WHAT THE %&[email protected]! I thought. I guess the chef cooked in some of the 6.5 files into 6.1 or something. Now this was getting REALLY old. I needed to end it quickly.
That brings me to tonight, when I flashed the official latest at&t fuze rom straight from htc's website. I KNEW this would be foolproof. And guess what.
IT STILL HAS THE PROBLEM!!!!!!!!!!!!!!
So my question is: after flashing numerous times, and soft resetting of course, how is it possible that this problem still exists? It happened exactly after flashing the rom that everyone else had spacing problems with, and hasn't gone away.
PLEASE. Someone help me. I can't even use the device and it's getting to the point where I'm really close to just dumping it and going to get something else. I hope someone out there has the answer.
Click to expand...
Click to collapse
Had the same problem. There is a driver issue that may have caused what you're experiencing. It was discussed in the WM6.5 ROM kitchen by the chefs. I did everything you did and still had the same issues. Best fix, call AT&T and have them ship a replacement if your device is under warranty. Others have had similar issues and haven't found a solution yet. Most likely because it's a hardware failure. Wish I had better news for you.
I know it seems more than a coincident (I thought the same thing) but I've done some extensive searching and found that this is too random of an incident to blame ROMs. If it was a ROM issue, there would be a lot more people and a thread would have existed prior to yours.
If your device is under warranty, depending on where you live, there may be an AT&T Device Support Center and they carry the FUZE and will exchange the device for you. Otherwise, you'll get it in the mail in a few business days.
Cheers!
Reefermattness said:
That's really weird I had the exact same problem. I thought it was my space key, so i got a warranty replacement saying i had lost my phone, meaning I still have the old one. I will have to test when i get home and see if it was the hardware keys or something to do with the ROM. After getting a new phone I did notice my space key was a little sloppy, so I immediately assumed this was the problem. Hopefully I was wrong and have 2 working phones.
Click to expand...
Click to collapse
What do you mean by "sloppy"? can you elaborate a little? I just got my replacement yesterday (because of the same keyboard space bar issue as mentioned here) and I'm already running NRG's Latest WM6.5 ROM. So far so good.
"Apparently (as discussed in the Kitchen thread), there's an issue with the input driver of the 21812 build ROM. I'm not sure if that's the build NRG was using on 6/13, but it's very possible. So, Da_G has included the CompIME.dll from a working build (in this case, 21731) in the kitchen to correct the error, which was isolated in that thread by pyrorob. " ~Captain_Throwback~
Here's the cab compliments of Captain_Throwback...
by "sloppy" i meant that its not as springy and clicky as my replacement, so it made me think that the button had worn out from smashing it with my fat fingers so much and that's why it was bugging out! It must have been NRG 6/12 ROM that did it to my TP as well. Good to see there is a fix. Maybe my gf will let me trade her for her G1 now to add to my collection.
ok. i flashed the hyperrom ultra v15.0 to my tmobile us hd2 and decided i wanted to flash a new radio.. just to see if i was missing the speed and agility that i hear about so much from others. i started off with a 2.10.50.26 i believe. then flashed the 2.08.50.05 with much slower speed than the original. THEN, i flashed the 2.07.51.22_2 and my phone has not powered up since. it will not go into bootloader and when the update util was done, my laptop said it needed to install a new hardware driver for qualcomm cdma. now i now this is bad. but could someone explain why it did this and why my phone isnt powering on and if ill ever be able to use it again??!!?!?! any help would be appreciated.
That sounds Bad ...
Sorry pal, you have a serious problem. The .51 radio is the culprit. I'm afraid you will have to search this out, but I am unaware of any solutions.
Good luck. Warranty?
jswllms3 said:
ok. i flashed the hyperrom ultra v15.0 to my tmobile us hd2 and decided i wanted to flash a new radio.. just to see if i was missing the speed and agility that i hear about so much from others. i started off with a 2.10.50.26 i believe. then flashed the 2.08.50.05 with much slower speed than the original. THEN, i flashed the 2.07.51.22_2 and my phone has not powered up since. it will not go into bootloader and when the update util was done, my laptop said it needed to install a new hardware driver for qualcomm cdma. now i now this is bad. but could someone explain why it did this and why my phone isnt powering on and if ill ever be able to use it again??!!?!?! any help would be appreciated.
Click to expand...
Click to collapse
jswllms3 said:
ok. i flashed the hyperrom ultra v15.0 to my tmobile us hd2 and decided i wanted to flash a new radio.. just to see if i was missing the speed and agility that i hear about so much from others. i started off with a 2.10.50.26 i believe. then flashed the 2.08.50.05 with much slower speed than the original. THEN, i flashed the 2.07.51.22_2 and my phone has not powered up since. it will not go into bootloader and when the update util was done, my laptop said it needed to install a new hardware driver for qualcomm cdma. now i now this is bad. but could someone explain why it did this and why my phone isnt powering on and if ill ever be able to use it again??!!?!?! any help would be appreciated.
Click to expand...
Click to collapse
Somebody on this forum already reported about similar problem. I don't remember whether the solution was found.
jswllms3 said:
ok. i flashed the hyperrom ultra v15.0 to my tmobile us hd2 and decided i wanted to flash a new radio.. just to see if i was missing the speed and agility that i hear about so much from others. i started off with a 2.10.50.26 i believe. then flashed the 2.08.50.05 with much slower speed than the original. THEN, i flashed the 2.07.51.22_2 and my phone has not powered up since. it will not go into bootloader and when the update util was done, my laptop said it needed to install a new hardware driver for qualcomm cdma. now i now this is bad. but could someone explain why it did this and why my phone isnt powering on and if ill ever be able to use it again??!!?!?! any help would be appreciated.
Click to expand...
Click to collapse
Why do people not read, you CANNOT FLASH A .51 RADIO ON A T-MOBILE DEVICE. LEARN TO READ AND THIS WON'T HAPPEN.
uniqs said:
Somebody on this forum already reported about similar problem. I don't remember whether the solution was found.
Click to expand...
Click to collapse
Somebody? lol, quite a few people are in that boat actually.
@jswllms3
Try searching for Jtag or .51 radio brick. And maybe post in this thread
warranty will be ok so long as you dont mention flashing.
jswllms3 said:
ok. i flashed the hyperrom ultra v15.0 to my tmobile us hd2 and decided i wanted to flash a new radio.. just to see if i was missing the speed and agility that i hear about so much from others. i started off with a 2.10.50.26 i believe. then flashed the 2.08.50.05 with much slower speed than the original. THEN, i flashed the 2.07.51.22_2 and my phone has not powered up since. it will not go into bootloader and when the update util was done, my laptop said it needed to install a new hardware driver for qualcomm cdma. now i now this is bad. but could someone explain why it did this and why my phone isnt powering on and if ill ever be able to use it again??!!?!?! any help would be appreciated.
Click to expand...
Click to collapse
How Cute
You flashed a 2.07.51 radio ! ! !
Take your phone back for warranty and never flash a .51 radio again as every one else saying...
Good luck with it.
ok. lol. so its abrick. ill search a little more butthe strange thing is, when i plug it in via usb to my comp it still shows that its searching for new hardware.. i dont think its a total loss. i have the odd feeling i can revive it. but in any case, how do i turn it in for a warranty and what would i say? lol.
jswllms3 said:
ok. lol. so its abrick. ill search a little more butthe strange thing is, when i plug it in via usb to my comp it still shows that its searching for new hardware.. i dont think its a total loss. i have the odd feeling i can revive it. but in any case, how do i turn it in for a warranty and what would i say? lol.
Click to expand...
Click to collapse
You say. I don't know what happen. I was charging it over night...and when I work up it was off. I turn it on and nothing happens.
what i meant to say is, im guessing i turn it into htc for the warranty, but other then flash custm roms and different radios, what other excuse would they take? i mean, they have ways of finding out right?
Maybe HELP YOU
jswllms3 said:
ok. i flashed the hyperrom ultra v15.0 to my tmobile us hd2 and decided i wanted to flash a new radio.. just to see if i was missing the speed and agility that i hear about so much from others. i started off with a 2.10.50.26 i believe. then flashed the 2.08.50.05 with much slower speed than the original. THEN, i flashed the 2.07.51.22_2 and my phone has not powered up since. it will not go into bootloader and when the update util was done, my laptop said it needed to install a new hardware driver for qualcomm cdma. now i now this is bad. but could someone explain why it did this and why my phone isnt powering on and if ill ever be able to use it again??!!?!?! any help would be appreciated.
Click to expand...
Click to collapse
I don't know if I can help you But you can enter in bootloader mode and via usb cable connect to your computer? If you can...and have Bepe&Cotulla HARDSPL3... Do a Task29 and when near 100% push volume down to stay in bootloader mode... then... Flash a radio 50 (my sig have a link to my current radio)... and without exit bootloader mode (when near 100% push volume down) Flash a ROM you want in your device...
Sorry... I only try help you... maybe don't have luck or... many luck
ddgarcia05 said:
You say. I don't know what happen. I was charging it over night...and when I work up it was off. I turn it on and nothing happens.
Click to expand...
Click to collapse
Say this ^^^^
Fidalgos said:
I don't know if I can help you But you can enter in bootloader mode and via usb cable connect to your computer? If you can...and have Bepe&Cotulla HARDSPL3... Do a Task29 and when near 100% push volume down to stay in bootloader mode... then... Flash a radio 50 (my sig have a link to my current radio)... and without exit bootloader mode (when near 100% push volume down) Flash a ROM you want in your device...
Sorry... I only try help you... maybe don't have luck or... many luck
Click to expand...
Click to collapse
no. it will not enter bootloader or anything. wont connect via activesync nothing. tried a hard reset, soft reset. every type of reset. nothing works. tried bootloader and.. NOTHING!!!! ah.. but its bugging me out that its trying to install new device driver. i feel like i can fix it... if christ was real i would pray to him!!!!
if you read the dozens of other people that did this, you will see they all say the pc looks for drivers for "qualcomm blah blah blah". don't kid yourself, its gone.
jswllms3 said:
ok. i flashed the hyperrom ultra v15.0 to my tmobile us hd2 and decided i wanted to flash a new radio.. just to see if i was missing the speed and agility that i hear about so much from others. i started off with a 2.10.50.26 i believe. then flashed the 2.08.50.05 with much slower speed than the original. THEN, i flashed the 2.07.51.22_2 and my phone has not powered up since. it will not go into bootloader and when the update util was done, my laptop said it needed to install a new hardware driver for qualcomm cdma. now i now this is bad. but could someone explain why it did this and why my phone isnt powering on and if ill ever be able to use it again??!!?!?! any help would be appreciated.
Click to expand...
Click to collapse
Simple: The .51 radio raped your TMOUS's internals. It will never work again. Play dumb with the warranty people.
haaahha! so i called the warranty people and told them it was dead. asked a few questions, specifically: "what voids the warranty and why would i be charged for any repairs?" i got a number of answers including, "flashing a new os, rom or radio." hahahaha!!! so essentially, im f**ked, right? i mean this is htc, how could they not find out?
so ive read part of three threads where everyone is stating that as long as they cannot get it to go into bootloader, they cannot charge me and theyll repair my phone or send me a new one. though i am worried that i havent read anything about any phones coming back to the peoples having this problem.. i dont have insurance through tmobile so im assuming i cant send it back to them, i am however still under the year manufacturers warranty provided by htc. does it matter who i send it to? and has anyone had experience with this particular problem that can acclaim to or deny me the assurance of me getting my phone back? lol.
Do not lie, as that could bite you in ways you don't want to deal with; as in fraud, etc. Our phones are around $550, a retainer for an Attorney to defend you against criminal charges would be a lot more.
I would go into tmobile, and when you go into store you simply tell them the truth that the phone doesn't work.
Definitely a drag that you bricked the phone. Could have been me, probably will be someday when I get too eager or careless.
Anyhow, let us know what happens.
jswllms3 said:
so ive read part of three threads where everyone is stating that as long as they cannot get it to go into bootloader, they cannot charge me and theyll repair my phone or send me a new one. though i am worried that i havent read anything about any phones coming back to the peoples having this problem.. i dont have insurance through tmobile so im assuming i cant send it back to them, i am however still under the year manufacturers warranty provided by htc. does it matter who i send it to? and has anyone had experience with this particular problem that can acclaim to or deny me the assurance of me getting my phone back? lol.
Click to expand...
Click to collapse
well for a start this is the regular hd2 section, have you read any of the posts in the tmous section? (Well, no, else you would have seen the myrriad warnings about flashing ..51.. radios )
Loads of people have had them repaired after this type of brick, and the only people that haven't have been those that confessed to flashing.
And no, just because it is HTC, they cant see into a broken bootloader. The best they can do is JTAG the phone, and that flashes a new bootloader anyway, wiping out any trace of what you did.
Please bare with me.
This is the second time this particular problem has happened to my device.
So I was on the tram coming back from my maths exam today.
(Running a ROM with Hardcore's SpeedMod K2-15)
I decide to change the song, all of a sudden, my screen turns black and I can't turn my phone back on. I as soon as it happened I thought uh oh. (the battery was at 74%.
So I tried to reboot my phone, didn't work.
Tried to get into download mode, didn't work.
Tried to get into recovery mode, didn't work.
Went to see if anything happened if I put in my charger AND USB cable. Both instances nothing happened.
When the incident happened last time, I was about to have it shipped to Samsung, was in the car on the way there and I was still pressing the power button in hope that it would work. Low and behold, it turned on, I flashed a different ROM and kernel and was on my merry way until today.
After browsing Q&A for around an hour the only other instances I've found with this problem are my original thread (around a month ago) when the same problem occurred.
http://forum.xda-developers.com/showthread.php?t=1302645
And another one I found today whilst browsing.
http://forum.xda-developers.com/showthread.php?t=1289063
also here
http://forum.xda-developers.com/showthread.php?p=18139062
So up to my knowledge this seems like a problem that isn't only a one off if I'm not the only one reporting it.
Is there anything I can possibly do to fix my phone or something to avoid doing so others don't run into the same unfortunate set of circumstances?
PS. two days ago I deleted a few folders on my USB storage as they were taking up too much storage space. I doubt they had anything to do with the problem though and that's the only difference I can think of that MAY have trigged the event. But I have no reason as to why it happened. I am also using NoMoarPowah and Chainfires3D mod (which I've been using for ages and i'm sure had nothing at all to do with the problem)
hopefully someone knows of a definite solution. :\
Wow the same thing is happening to my phone as well. Thanks for the detailed description. Hopefully we'll find a response soon. Also, I would suggest you investigate the volume of chode in the nearby vicinity of your phone, may be a problem (personal experience)
I just dropped mine off a stepladder in kfc, and i'm experiencing the same problem. Avoid doing this. Hopefully someone else has a better solution to your problem but for now, just don't drop it off any stepladders.
x0x0 leopardkitty69
pokergirl said:
You spelt bare wrong
Click to expand...
Click to collapse
I've made similar mistakes in life. You don't want to mix them up at the wrong time. *Shows bear scars*
leopardkitty69 said:
I just dropped mine off a stepladder in kfc, and i'm experiencing the same problem. Avoid doing this. Hopefully someone else has a better solution to your problem but for now, just don't drop it off any stepladders.
x0x0 leopardkitty69
Click to expand...
Click to collapse
ALSO Don't dinosaur with it, nor allow for sluts to touch it xoxoxoxoxoxoxoxoxox bb <3
pokergirl said:
last edited by pokergirl; today at 01:04 pm. Reason: I did it wrong!
Click to expand...
Click to collapse
you're doing it wrong!
Too late for the sluts, they're all over it! x0x0x0x0x0x
H3h3
H3h3h3h3h3h3h3h3h3 its ****ed darl <3 xxxxxx
Leopardkitty69 stop degrading urself g1rL g3t urs31f @ [email protected] xo
- A girl who knows how to control balls
leopardkitty69 said:
I just dropped mine off a stepladder in kfc, and i'm experiencing the same problem. Avoid doing this. Hopefully someone else has a better solution to your problem but for now, just don't drop it off any stepladders.
x0x0 leopardkitty69
Click to expand...
Click to collapse
I dropped it quite hard and it caused corruption on /efs partition.
lol'd
This thread has suddenly become a lot more interesting.
pokergirl said:
Through implementing my CAS 89 values and inserting chode = 2x length into my TVM solver i introduced the viagra into my phonem therefore, bringing its pwoer to 9001 and causing for it to groan in pleasure. Through utilising square volume = 2 * x * l with x = your vaginas length and y = The radius of your arsehole i solved this problem. (Personal experience, for more information visit (it made me delete the link))
P.s chodemaster - Your personal experience is obviously limited and incredibly detrimental to the phone. When YOU have caught all 151 original chodes you should post in this forum in a SERIOUS and well rounded individual manner
P.P.S NEED MOAR PYLONS
P.P.P.S THIS IS YOUR BIRTHDAY CARD FOR NEXT YEAR
Click to expand...
Click to collapse
Sigh I really need a solution. Not thread spam >.<
This sounds like a serious issue with your phone's hardware. You should return it to Samsung.
with the phones hardware itself?
If they manage to fix it do you think the'll notice it's been rooted?
I've removed the triangle and reset the flash count i've just got a new ROM on it.
(as in will it still be under warranty)
If you manage to reset the counter and get the original stock rom on it (or a new version which was meant for your device and came by kies) you should be perfectly fine, just don't root it again (until you get it back, that is).
Freakgs said:
If you manage to reset the counter and get the original stock rom on it (or a new version which was meant for your device and came by kies) you should be perfectly fine, just don't root it again (until you get it back, that is).
Click to expand...
Click to collapse
but it currently won't turn on at all ;|
giga502 said:
but it currently won't turn on at all ;|
Click to expand...
Click to collapse
In that case chances are very high that Samsung will simply replace it, given that they probably won't be able to turn it on, too.
That's what I've heard from many people atleast, who had issues turning their devices on.
Only way to find out: see if you can get warranty.
Other option: be honest that you rooted and hope for the best, yet I don't know how Samsung staff would react to that, probably not too good.
Ps:
I take it that you have a JIG and tried that one already? As you stated, that you did reset the counter.
Freakgs said:
In that case chances are very high that Samsung will simply replace it, given that they probably won't be able to turn it on, too.
That's what I've heard from many people atleast, who had issues turning their devices on.
Only way to find out: see if you can get warranty.
Other option: be honest that you rooted and hope for the best, yet I don't know how Samsung staff would react to that, probably not too good.
Ps:
I take it that you have a JIG and tried that one already? As you stated, that you did reset the counter.
Click to expand...
Click to collapse
I've given it to a friend but I highly doubt it would work. Anyway for now, I'm going to place it in rice JUST IN CASE there is a tiny bit of moisture on some part of the motherboard which is messing things up. If that dosn't work i'm going to go down to my mobile dealer and hope for the best
thanks for your help!
One question: Did you pull the battery, and put it back in?
I have had this sometimes before, it seems to be caused of overheating... But I'm not 100%. I have checked Logcat but nothing in there of interest.
ante0 said:
One question: Did you pull the battery, and put it back in?
I have had this sometimes before, it seems to be caused of overheating... But I'm not 100%. I have checked Logcat but nothing in there of interest.
Click to expand...
Click to collapse
no I havn't done that. I'm taking it back later today