Ok guys, yes...I'm a noob...
I did a master reset on the phone and now I get nothing...
It won't turn on unless I plug it in to the charger.
When it does turn on, all I get is a few vibrations, and
the icons at the bottom light up.
I can get windows to see the two "drives" of the phone,
but they are empty (have 0 bytes if you right click and check properties. If you left click, it says please insert disc).
I've tried a new battery and my battery turns another phone on...
I've also tried two cables and two PCs.
It hasn't been rooted or messed with, the battery died and I went to charge
it and nothing...I left it on charge overnight and at least see a bit life.
Any ideas, or should I just send it on to HTC??
So that others have a better idea... can you get into hboot or fastboot?
try a nwe battery
xboarder56 said:
try a nwe battery
Click to expand...
Click to collapse
he said he already tried a new charged battery, so it can't be that. I'm thinking his phone's OS might be gone so he should probably installed a RUU or something.
In the dark...
Can't see anything come up on screen...
no idea what mode it's in, hboot, fastboot or anything ??!?!!
Think it might be possible to install just a stock (Tmobile) RUU?? If so, how ?????
karaokekarnival said:
Can't see anything come up on screen...
no idea what mode it's in, hboot, fastboot or anything ??!?!!
Think it might be possible to install just a stock (Tmobile) RUU?? If so, how ?????
Click to expand...
Click to collapse
if you can't get into hboot/fastboot (totally forgot which, basically same thing) then you can't do the RUU
Hmmm, OK
Do you think there is anything that I can do to get it running ??
And where do I find the thanks button ???
karaokekarnival said:
Do you think there is anything that I can do to get it running ??
And where do If ind the thanks button ???
Click to expand...
Click to collapse
if you rooted and custom recovery you could but right now you out of luck you gonna have to return
Duh, I found the thanks button !!!
I was afraid of that...guess I'll ship it off Monday. If anyone knows a way before then, let me know...can't hurt to try, eh ??
karaokekarnival said:
Duh, I found the thanks button !!!
I was afraid of that...guess I'll ship it off Monday. If anyone knows a way before then, let me know...can't hurt to try, eh ??
Click to expand...
Click to collapse
There isn't a way if your phone isn't detected or you can't get into hboot. Meaning you have no control over your phone to do anything.
Anyways, for htc warranty exchanges that is done with tmobile... they usually send you the phone first and then you send one back in return. Unless your policy is different. So i suggest you calling them immediately.
Update
I can go into control panel and "see" the phone listed in device manager under portable devices as "F" and "G". Click properties and they are found as HTC devices. Does this mean I can do anything to it? I just want my phone back working as fast as I can. Sending it in will take a while. I bought this phone for the camera. We have a 1 yr old and don't wanna miss the Christmas pics...
karaokekarnival said:
I can go into control panel and "see" the phone listed in device manager under portable devices as "F" and "G". Click properties and they are found as HTC devices. Does this mean I can do anything to it? I just want my phone back working as fast as I can. Sending it in will take a while. I bought this phone for the camera. We have a 1 yr old and don't wanna miss the Christmas pics...
Click to expand...
Click to collapse
are you on tmobile? they usually send within 2 days, their distribution center is in texas or something. I usually get it next day.
You said your screen doesn't turn on or doesn't show anything. It's gonna be hard to determine what you're doing even if you can run ADB to put it in oem fastboot and to flash a RUU that way. But it sounds like your display might be a problem too then. It'll be quicker to do an exchange. If you call in today, they'll probably ship it on monday and you'll get it wednesday latest. unless you have tmobile insurance plan. it should be next day and you'll get it tuesday.
Thanks
Well that might work for me then...can't hurt to give it a try.
Thanks a bunch for letting me know !!!
No problem, I had my fair share dealing with tmobile exchanges lol.
If you purchased directly from tmobile it should be very easy to do an exchange because your warranty is verified.
If you bought it off craigslist/ebay. sometimes the previous users used a different carriers that makes the warranty no longer verified. HOWEVER many customer reps will still try to process the exchange (you can determine by their upbeat personalities lol).
If you run into someone who won't do it, just call again and talk to another rep. Most of the time they will push it through because it's still a newly released phone.
Have you already contacted T-Mobile support? You'll have to talk to them anyway before they agree to replace your phone.
The reason I am asking this is because there might be an unpublished backdoor way to restore your device if your device is not completely (hardware-wise) dead. For example, Dell Streak has a complete firmware image on its internal SD card and you needed to somehow trigger an IPL routine to restore the device to its original condition.
I haven't heard of anything similar on HTC devices yet, but hey, it's just a thought. And if there actually is a way, and you are the first one to post it here, you'll be a hero!
ringochan said:
Have you already contacted T-Mobile support? You'll have to talk to them anyway before they agree to replace your phone.
The reason I am asking this is because there might be an unpublished backdoor way to restore your device if your device is not completely (hardware-wise) dead. For example, Dell Streak has a complete firmware image on its internal SD card and you needed to somehow trigger an IPL routine to restore the device to its original condition.
I haven't heard of anything similar on HTC devices yet, but hey, it's just a thought. And if there actually is a way, and you are the first one to post it here, you'll be a hero!
Click to expand...
Click to collapse
yeah we normally just flash a RUU, but you can't even see the screen, so we can't even be certain that we're in the correct modes to be flashing and stuff. because we require to ADB it to restart in fastboot, but we can't even see if its going to fastboot. or if it already is in fastboot to begin with, so we're not certain which commands to run with the screen being off. Well you can always try commands and it should only work in certain modes, but do you really want to do it blindly? I would rather just exchange the thing.
Not afraid to try....
Well, I can't use it as it is...exchange is a hassle even in 2-3 days. Can't do anything until tomorrow anyway. I was thinking today, I've heard they can port Android to iPhone...there's no fastboot there, is there ??? Soooooo, if it's turning on, I should be able to do something...I want my phone back !!!
Edit: I misunderstood the issue
Sent from my HTC Ruby using xda premium
Please share....
Snargaflab, please share, it might help me or others to think !!
Flashing green light ???
It is now turning on and has a flashing green light, does that mean anything??
Related
Well, i ****ed up my phone.
Trying to bring it back alive failed, so I'm going to bring it
back to T-Mobile.
Does someone know a very good lie I can tell them, so I don't have to pay for the repair.
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
CCRDude said:
I don't think using bold letters and the clear word "lie" will help you a lot... you just highlight that you ask for illegal help
Maybe you should take a look at the bricked-devices topic for a chance to revive it?
Click to expand...
Click to collapse
I have spent the last 3 days 30 hours orso fixing my phone. Revive is something my dead baby won't do.
vayip said:
I have spent the last 3 days 30 hours orso fixing my phone. Revive is something my dead baby won't do.
Click to expand...
Click to collapse
enter the bootloader; try to flash a regular update from your provider to it.
vayip said:
Well, i ****ed up my phone.
Trying to bring it back alive failed, so I'm going to bring it
back to T-Mobile.
Does someone know a very good lie I can tell them, so I don't have to pay for the repair.
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
Click to expand...
Click to collapse
I did the same with my Vodafone (UK). I just told them I'd hard reset and this is all I can see on the screen (don't get stroppy etc).
Mine will be back Tuesday, warranty repaired.
Vod UK use an outside repair centre so will probably be the same as T-Mobile if you are in UK. Mine needed a new motherboard, but there is a bit of a shortage in the UK (too many bricks???). I guess it depends on the outside service centre contract whether they charge you or T-mobile (and maybe also because I had warranty and Insurance)..
Just go in and plead ignorance, but if they want to charge you, ultimately it was you that ****ed it and not them
Toast it in the microwave for 5 seconds!
boz said:
Toast it in the microwave for 5 seconds!
Click to expand...
Click to collapse
That's a new one - when car radio codes first came out they always said to put them in the freezer then stroke the chips legs to erase the cmos... never worked for me, but I'd probably get away with the microwave thing with 3 kids at home!!!
@ Olipro
If you mean the SD-card flashing, T-Mobile Holland doesn't have an update available. There is an T-Mobile Holland ROM available, but the image is older than the image installed on my phone. When checking the ROM in the white screen, it says not allow. I think i need ROM 1.21.114.3 from T-Mobile if I want to do the SD-card flash.
I only have access to the bootloader, I have bootloader 1.04, and I have access to KITL mode, but the Windows CE Platform Builder fix also doesn't work
@ ach2
I was thinking also something like that. That I hard reset my phone and now it's broke. I was also thinking something like I left my phone on the charger for the weekend, and when I came back I did a soft reset because it wouldn't go on and know I only see a HTC splash screen.
vayip said:
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
Click to expand...
Click to collapse
Can you think of a good reason whey the boot screen has changed from the normal T-Mobile one... just hope they don't turn on the phone. Did you try Olipro's suggestion?
@ Wam7
The T-Mobile splash screen is in the extended ROM. If the extended ROM is ****ed up like mine is, it probably goes back to its embedded splash screen, and that's the one from HTC. But thats not what I'm going to say, I'm going to say how should I know.
If I remember correctly a guy has managed to dump the ROM from a Hermes and flash it to the phone... saw a thread somewhere here. If that's the case then you should just need a ROM from a fellow dutch T-Mobile owner with the newer ROM. I take it your phone is not SuperCID
vayip said:
@ Olipro
If you mean the SD-card flashing, T-Mobile Holland doesn't have an update available. There is an T-Mobile Holland ROM available, but the image is older than the image installed on my phone. When checking the ROM in the white screen, it says not allow. I think i need ROM 1.21.114.3 from T-Mobile if I want to do the SD-card flash.
I only have access to the bootloader, I have bootloader 1.04, and I have access to KITL mode, but the Windows CE Platform Builder fix also doesn't work
Click to expand...
Click to collapse
if you have 1.04; run the RUU on your computer; you will get a "Vender ID Error" immediately ignore this and run the updater AGAIN (do not touch or unplug your PDA) after doing this a second time it will begin to flash
vayip said:
Well, i ****ed up my phone.
Trying to bring it back alive failed, so I'm going to bring it
back to T-Mobile.
Does someone know a very good lie I can tell them, so I don't have to pay for the repair.
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
Click to expand...
Click to collapse
seriously this is why MS and Carriers HATE us
Olipro said:
if you have 1.04; run the RUU on your computer; you will get a "Vender ID Error" immediately ignore this and run the updater AGAIN (do not touch or unplug your PDA) after doing this a second time it will begin to flash
Click to expand...
Click to collapse
I did what you said. I connected the phone to my laptop in bootloader. I started the RUU from WMXL 0.20. My phone goes to the white screen and at 0% i get a message on my laptop the connection got disconnected. So i start the RUU again, but again the message my connection got disconnected.
So still working on a good lie.
@vayip: sounds like a problem with the USB on your laptop. Try using a different computer. BL1.04 will let you flash any OS provided your NAND isn't full of bad blocks. You're a long way away from returning your device to Tmo IMO.
On the new computer:
direct USB connect to rear port only no usb hubs
pc running windows XP
turn off screensaver/Powersave mode
close all other apps
hands off the computer for the 25 minutes or so that it takes
Sleuth255 said:
@vayip: sounds like a problem with the USB on your laptop. Try using a different computer. BL1.04 will let you flash any OS provided your NAND isn't full of bad blocks. You're a long way away from returning your device to Tmo IMO.[/list]
Click to expand...
Click to collapse
Does it matter if the phone is simlocked or not. My phone is not SuperCID.
The strange thing than is, i have 2 laptops. Doing the upgrade don't work on both.
Will try a normal pc then. Maybe more luck.
Follow Oli's advice about retrying the update if you get an initial vendor ID error. BL1.04 will flash any rom without SuperCID due to a bug.
You might want to jump in with mtty first to see if your NAND is full of bad blocks. If it is then your device is toast fttb.....
spiritofseth said:
seriously this is why MS and Carriers HATE us
Click to expand...
Click to collapse
I completely agree! If you ****ed up your device, than you should have the courage to stand up for it and if it was not your fault, than just tell them the truth! But suggestions like "put it in the microwave for 5secs".... come on
And just a small hint: If you (for example) really put it in the microwave, than you'll better pray that no technician ever analyses your device - if so you could get into serious trouble, mate.
Btw, if you microwave it, you probalby need a new microwave too.
Edit: And i dont think its warranty would cover "I just put my Phone in there"
"So still working on a good lie."
Doesn't breaking your phone through your own actions and then getting it repaired/ replaced for free by telling lies make you a liar and a thief?
I trashed 8525, and that sucks, but it was my fault so I have to pay for it.
In my adventures flashing Roms, I've only bricked 1 Hermes (Cingular 8525). I actually told the local Cingular shop that I broke it 2 weeks after I bought it. The manager told me to bring it in and she replaced it under the 30 day in-store return policy. I was suprised because I had caused the bad NAND Block problem on the device but she said that since I was able to get an official Cingular Rom flashed onto it and it booted into WM5 (just wouldn't do anything because of memory errors).
Now I also have a very good working relationship with this store. I've gotten a phone about every 6 months from them over tha past 2 years and have given them some great info regarding WM5 devices (reccomendations on screen protectors, software & cases etc). I have 3 lines (2 with Data) and even if they don't know me by name eveyone in the store knows me by reputation.
Tomorrow I will have my spare Hermes (also 8525) so we can begin experimenting with getting some additional storage memory without risking bricking my primary phone.
The way I see it, we are taking a chance when we modify our devices.
I've had to return 2 Wizards for Warranty replacement to Cingular, both were CID Unlocked but the problems were unrelated to flashing Roms (One was because the touch screen developed a dead spot the other was because of Radio hardware issues).
The problem: I flashed a radio to my device that is (obviously) incompatible with my device (if you really want the details, its embarassing, but I'll post if necessary). My phone freezes on bootup, and never initializes the Radio/ROM (and for good reason).
This is what happens now: If my phone is off, I can turn it on, but I only get the first boot up screen, and the red numbers in the bottom right-hand corner never appear. At that point, I cannot turn off my phone without taking out the battery. If I take out the battery and put it back in, and attach the phone to a charger (or USB cable), the light on the phone will "breathe", as if its charging. However, if I then disconnect the phone, the light will CONTINUE breathing.
I also cannot turn on the phone while its connected to either the charger or USB cable.
My phone is Hard-SPL'ed and Security Unlocked. But the real issue I'm having is that I can't get into Bootloader to flash something else. Apparently, I've corrupted the Bootloader. When I turn the phone on, and press the reset button while holding Vol-down, the phone just goes black.
I might be okay getting a warranty exchange if not for this: I can still hard reset my phone. It doesn't make any sense to me, but when I turn it on, I can do the soft-reset-button, Vol-down, Action button combo, and my phone flashes through Bootloader to give the the hard reset menu. It flashes that screen just long enough to see that my phone has 1.90Olinex as the SPL. So, I think I may be screwed, unless someone here can help.
My wife is very . . . upset . . . about this, and is worried that we'll have to spend money because of my continuous "tinkering" with my phone.
Any help anyone can offer is greatly appreciated.
I know this is my own stupid fault, and I should've known better, but it would be nice to get confirmation from the experts here that I'm just going to have to chalk one up in the "L" column at this point.
Q
Have you tried to flash from the SD card?
Hi Captain_Throwback,
Try copying Raph Radio 1.11.25.01 to the root of a FAT32 SD Card ... you'll need to rename the .NBH to RAPHIMG.NBH.
Pull the SIM out of the phone and power it back on as per usual; I've noticed that the phone "blacks out" for a bit but then switches to flash mode.
Good luck.
PS: suggest getting the large carry-on with the wheels for the guilt trip - heaven knows it's come in handy for me
That's a bummer, man. You gotta at least 'fess up part of the story to prevent someone else from falling into the same trap (however unlikely that may be). And maybe, just maybe, it will help someone else figure out how to fix your problem.
What radio did you try and flash.
Hopefully it wasn't the new Rhodium radio? Or a Rose radio?
I have done this a few times on my tilt, all I did was put it into the boot loader, it worked from hard reset screen as well, and flashed the rom via activesync. I am assuming that you are not able to get a sync, or have you tried yet? I know my fize will also sync [to flash] from bootloadr.
Captain_Throwback said:
The problem: I flashed a radio to my device that is (obviously) incompatible with my device (if you really want the details, its embarassing, but I'll post if necessary). My phone freezes on bootup, and never initializes the Radio/ROM (and for good reason).
This is what happens now: If my phone is off, I can turn it on, but I only get the first boot up screen, and the red numbers in the bottom right-hand corner never appear. At that point, I cannot turn off my phone without taking out the battery. If I take out the battery and put it back in, and attach the phone to a charger (or USB cable), the light on the phone will "breathe", as if its charging. However, if I then disconnect the phone, the light will CONTINUE breathing.
I also cannot turn on the phone while its connected to either the charger or USB cable.
My phone is Hard-SPL'ed and Security Unlocked. But the real issue I'm having is that I can't get into Bootloader to flash something else. Apparently, I've corrupted the Bootloader. When I turn the phone on, and press the reset button while holding Vol-down, the phone just goes black.
I might be okay getting a warranty exchange if not for this: I can still hard reset my phone. It doesn't make any sense to me, but when I turn it on, I can do the soft-reset-button, Vol-down, Action button combo, and my phone flashes through Bootloader to give the the hard reset menu. It flashes that screen just long enough to see that my phone has 1.90Olinex as the SPL. So, I think I may be screwed, unless someone here can help.
My wife is very . . . upset . . . about this, and is worried that we'll have to spend money because of my continuous "tinkering" with my phone.
Any help anyone can offer is greatly appreciated.
I know this is my own stupid fault, and I should've known better, but it would be nice to get confirmation from the experts here that I'm just going to have to chalk one up in the "L" column at this point.
Click to expand...
Click to collapse
Damn I'm sorry to hear about your issue and i feel for ya because I did some stupid **** myself a lil' while back if you remember. Your advice to reflash the oem rom worked for me 100%. Have you tried hard resetting and then trying to get into bootloader mode?
AllTheWay said:
What radio did you try and flash.
Hopefully it wasn't the new Rhodium radio? Or a Rose radio?
Click to expand...
Click to collapse
Ok, I'll tell you . . . it wasn't a Rose radio (I know P1Tater bricked his phone that way) . . . but I figured, the Rhodium, its got the same hardware, right? I mean, T-Mobile is a GSM carrier . . . If I patch it for Raph, it may work . . . even though the radio number is so much different . . . I should still be able to get into Bootloader if it doesn't work, because I'm HardSPL'ed . . .
But no. I can't get into Bootloader. Believe me, I've tried. Every time I try, the phone just goes black. And I have a nice stock AT&T ROM on my Storage Card ready to flash, if only I could get it onto the phone.
I tried plugging into the computer, but it won't recognize the phone at all.
I wish it was REALLY bricked, but the fact that I can still hard reset it is very disappointing.
Captain_Throwback said:
Ok, I'll tell you . . . it wasn't a Rose radio (I know P1Tater bricked his phone that way) . . . but I figured, the Rhodium, its got the same hardware, right? I mean, T-Mobile is a GSM carrier . . . If I patch it for Raph, it may work . . . even though the radio number is so much different . . . I should still be able to get into Bootloader if it doesn't work, because I'm HardSPL'ed . . .
But no. I can't get into Bootloader. Believe me, I've tried. Every time I try, the phone just goes black. And I have a nice stock AT&T ROM on my Storage Card ready to flash, if only I could get it onto the phone.
I tried plugging into the computer, but it won't recognize the phone at all.
I wish it was REALLY bricked, but the fact that I can still hard reset it is very disappointing.
Click to expand...
Click to collapse
This happened to me (sort of.) I flashed a diamond radio to my fuze... without security unlocking it first. Symptom wise, Exact same thing happened. I was able to (after days of tinkering) get it into bootloader from the hard reset screen. I just kept pressing the Hard rest sequence over and over while connected to USB. I noticed, one time, I got the USB at the bottom. Don't know how, don't know why, it just happened, I was then able to flash the Stock Cing ROM. Wierd stuff, But lucky. Hope you get it back on board. Is it insured? Because it would really suck if someone stole your bricked fuze.
Intertrochanterica said:
This happened to me (sort of.) I flashed a diamond radio to my fuze... without security unlocking it first. Symptom wise, Exact same thing happened. I was able to (after days of tinkering) get it into bootloader from the hard reset screen. I just kept pressing the Hard rest sequence over and over while connected to USB. I noticed, one time, I got the USB at the bottom. Don't know how, don't know why, it just happened, I was then able to flash the Stock Cing ROM. Wierd stuff, But lucky. Hope you get it back on board. Is it insured? Because it would really suck if someone stole your bricked fuze.
Click to expand...
Click to collapse
It is insured, and paying $125 is better than having to buy a brand new phone, but if I can avoid spending money, my wife would be much happier .
I can hard reset just fine . . . if only the phone would stay on the bootloader screen when doing that . . . but it doesn't. I assume the bootloader has been corrupted, which is why the phone blacks out when trying to enter bootloader mode. I'll keep trying, I guess. I can't make it any worse. Actually, if I could, I'd be better off, so that way they can't find out my phone is Hard-SPL'ed.
Captain_Throwback said:
I can hard reset just fine . . . if only the phone would stay on the bootloader screen when doing that . . . but it doesn't. I assume the bootloader has been corrupted, which is why the phone blacks out when trying to enter bootloader mode. I'll keep trying, I guess. I can't make it any worse. Actually, if I could, I'd be better off, so that way they can't find out my phone is Hard-SPL'ed.
Click to expand...
Click to collapse
Try plugging it into a car battery, or something like that, and fry the sucker. That's my only piece of advice.
Captain_Throwback said:
I can't make it any worse. Actually, if I could, I'd be better off, so that way they can't find out my phone is Hard-SPL'ed.
Click to expand...
Click to collapse
You could make it worse if you get the white sticker wet and make it turn pink, but that would be very bad for you.
You are at the point to where you cant move beyond your current predicament in wither way. Im afraid I see no other alternative than to pay the $125.
Maybe you could sell your Fuze on Ebay for 125 to cover your insurance cost and you could make a notation on the Ebay site saying something like 'PARTIALLY USED FUZE' like that Carfax commercial does.
update
My phone is still bricked, but I'm taking it to a repair shop after work, where I'll find out whether I'll be getting a free warranty replacement, or paying $125 for an insurance replacement. At least I've been able to successfully determine that a Rhodium radio cannot be flashed to a Raphael. So no one else has to try it .
Keep us updated dude. Also, if you slip the guy $50 he may do the free warranty replacement for you... it might save you $75 and you wont have to use up one of your insurance claims.
Captain_Throwback said:
My phone is still bricked, but I'm taking it to a repair shop after work, where I'll find out whether I'll be getting a free warranty replacement, or paying $125 for an insurance replacement. At least I've been able to successfully determine that a Rhodium radio cannot be flashed to a Raphael. So no one else has to try it .
Click to expand...
Click to collapse
Crap, sorry to hear that. HAAH, just walk into the ATT store and say," I tried turning the phone on and this is what happened." And that you have never heard of XDA forums, roms, and though a radio was only for people in trucks or that wear camo.
iceman4357 said:
Crap, sorry to hear that. HAAH, just walk into the ATT store and say," I tried turning the phone on and this is what happened." And that you have never heard of XDA forums, roms, and though a radio was only for people in trucks or that wear camo.
Click to expand...
Click to collapse
That might work, if I hadn't bought the phone from my best friend, who just happens to manage an AT&T store. He actually knows that I had a custom ROM on my phone, and called ahead to the repair shop to let them know I was coming, and he said hopefully they won't notice the SPL in my bootloader if they try and hard reset it. So it is possible they'll just give the phone a cursory look to make sure its really not working, and then go ahead with a warranty replacement. I'll be sure to let everyone know what happens. In the meantime, the word of the day is "dumbass", LOL.
Farmer Ted said:
Try plugging it into a car battery, or something like that, and fry the sucker. That's my only piece of advice.
Click to expand...
Click to collapse
That's what I would do.
Captain_Throwback said:
My phone is still bricked, but I'm taking it to a repair shop after work, where I'll find out whether I'll be getting a free warranty replacement, or paying $125 for an insurance replacement. At least I've been able to successfully determine that a Rhodium radio cannot be flashed to a Raphael. So no one else has to try it .
Click to expand...
Click to collapse
Honestly I would not take it to the repair shop.
Here is what I would do. Call the warranty replacement department at AT&T. 1-800-801-1101. Tell them that you woke up and now your phone won't turn on. Once you go through all the steps they have to do to fix it, then they will ship you a replacement Fuze right away. The refurbished Fuze will have everything except for a battery and a back cover. Typically when I did this I received a new one the next day that I called.
Now take your battery out of your phone and your SIM card and microSD card. Put your phone in the microwave for 2 seconds. Walla. Now it's bricked and AT&T will have no way to tell if you have HardSPL or a cooked ROM on your phone. Trust me. It will work.
When you get your new phone just send the phone back in packing material that they provide to you and you won't have to spend any money to get a new phone or spend money to fix a phone.
Just do what I told you about. I promise it will work. Just trust me. I've done it before and it worked like a charm. No worries. Trust me, I'm not trying to lead you down the wrong path. I'm trying to get you a replacement just like I got when I bricked my last fuze trying out different radios. And use the phone number that AllTheWay posted just above me once you do what I told you.
P1Tater said:
Just do what I told you about. I promise it will work. Just trust me. I've done it before and it worked like a charm. No worries. Trust me, I'm not trying to lead you down the wrong path. I'm trying to get you a replacement just like I got when I bricked my last fuze trying out different radios. And use the phone number that AllTheWay posted just above me once you do what I told you.
Click to expand...
Click to collapse
I'm curious what it is you told him, in case i'm in a similar position at any point !!
Lemme kno please here or PM is cool!
Thx
JFlitt
AllTheWay said:
That's what I would do.
Honestly I would not take it to the repair shop.
Here is what I would do. Call the warranty replacement department at AT&T. 1-800-801-1101. Tell them that you woke up and now your phone won't turn on. Once you go through all the steps they have to do to fix it, then they will ship you a replacement Fuze right away. The refurbished Fuze will have everything except for a battery and a back cover. Typically when I did this I received a new one the next day that I called.
Now take your battery out of your phone and your SIM card and microSD card. Put your phone in the microwave for 2 seconds. Walla. Now it's bricked and AT&T will have no way to tell if you have HardSPL or a cooked ROM on your phone. Trust me. It will work.
When you get your new phone just send the phone back in packing material that they provide to you and you won't have to spend any money to get a new phone or spend money to fix a phone.
Click to expand...
Click to collapse
Agree with this. If your friend works at the store and knows what you have done, I wouldnt go there. Call the number, fry the damn phone and get a new one. We need you back on your feet to help solve ROM issues my friend.
So I changed a few things in the build.prop-file to get incompatible apps work on my TF 201 but then I somehow restarted it and now it won't boot anymore. Well it shows up the Asus logo and so one but then the screen just stays black (but still illuminated).
I already wiped the data and tried the recovery mode (with the Volume-down/up-button) but they didnt work, it still doesnt boot.
So any ideas which could help me? Im thankful for every help I can get
Maybe let the battery run out. There is also the reset button in the pinhole next to the SD card slot.
Why do people keep taking such risks. There has been a few threads already of some trying to do the same thing and bricking their device. Where these apps so great n important to now have possibly bricked your device? Instead of editing build. Props you could've used another device with same screen size resolution. For example a gameloft game, modern combat 3. Won't work on Prime because it says its incompatible. That is b.s. Prime just wasn't added to support list yet. So I used an Acer500 , same screen size resolution, version and it worked perfectly. A simple wrkaround without risking editing the app and causing a possible bootloop or brick.
Hope you get it up n running soon. Maybe letting the battery completely die and charging back up may clear whatever you did. I won't risk anything till atleast bootloader unlocked n we have recovery also. GOOD LUCK.
I already let the battery run out twice but it doesnt help, when I plug it in again, it just boots normally till the part where the screen stays black.
And the reset button under the sd card slot just reboots the device normally.
try to return it from wherever you bought it they will never even know what happened to it
fliger5 said:
So I changed a few things in the build.prop-file to get incompatible apps work on my TF 201 but then I somehow restarted it and now it won't boot anymore. Well it shows up the Asus logo and so one but then the screen just stays black (but still illuminated).
I already wiped the data and tried the recovery mode (with the Volume-down/up-button) but they didnt work, it still doesnt boot.
So any ideas which could help me? Im thankful for every help I can get
Click to expand...
Click to collapse
I have the same problem with being stuck in bootloop. I've done the pinhole reset, as well as the power+volume reset... nothing works. I've let the battery drain.. nothing.
I just got off the phone with Asus customer support. They told me to return the tablet. Guess where I'm going today? Best Buy and returning it.
And yes, I'll probably get another Prime. They are just so Beautiful!
tylermaciaszek said:
try to return it from wherever you bought it they will never even know what happened to it
Click to expand...
Click to collapse
You sure about that? I bought it from Amazon btw. But I read that some people got the same problem by just applying an official firmware update, so I guess it's really possible that they will never find out what really happened .
but I think there's no other possibility but returning it. :/
I'll give you $50 for it. J/K.... Good luck getting it running.
I don't quite understand how some people can make changes with out us being able to use Clockwork recovery yet. I would return it, they will probably give you a replacement.
Wait til Feb. Asus will prolly release a restore tool along with the bootloader unlock. Like the ruu for htc phones.
Sent from my Transformer Prime TF201 using xda premium
fliger5 said:
You sure about that? I bought it from Amazon btw. But I read that some people got the same problem by just applying an official firmware update, so I guess it's really possible that they will never find out what really happened .
but I think there's no other possibility but returning it. :/
Click to expand...
Click to collapse
Yes. I just did it today. Got the new one on order.
!
Yes. I just did it today. Got the new one on order.
!
Click to expand...
Click to collapse
And did you have to say anything how it happened? If yes, what did you tell them?
fliger5 said:
And did you have to say anything how it happened? If yes, what did you tell them?
Click to expand...
Click to collapse
Nope. Didn't have to tell them anything. It wouldn't leave the bootloader screen. So I did both types of factory resets. They only way thy find out that I rooted it is when it gets back to Asus, they are somehow to get a computer to recognize it (mine won't), and look at the root files therein.
I had no problem returning mine!
Hope that helps!
Did you at least make a backup of the build.prop? I think the system will make one automatically I am just not sure how to go about getting it. I would guess if you can get into it with adb you could pull the backup rename it and push it to the /system. I don't know the commands but I am guessing someone who has posted stuff in the development section does, maybe that would work. Also, I am not sure there is a way to clear the cache/dalvik cache. Maybe through adb somehow which might have to be done as well.
I just don't know enough about adb and the commands to get it done.
Problem is, adb doesnt work because the device isnt recognized. It always says "No device found" or anything like that. Well I'll send it back to Amazon but I think they will send it then to Asus, so there's a chance that they will find it out, right?
Hi all,
I am a proud owner of HTC Amaze, running BulletProof ROM with Faux Kernel v08.
The issue I am experiencing is most probably hardware issue, but I still hope it is not.
My backlight does not work at all. The phone works fine, and under heavy light you can see the actual screen, and can operate the phone as usual, but of course, otherwise, the phone is unusable, since you cannot see anything.
I've tried factory reset, restored to previous backup, charged it till full, left it without battery for few hours, nothing helped. Backlight is simply not there.
Soft buttons have the backlight, but not the screen.
There is a chance that it could be a battery issue (caused by phone), since it is my second battery, original one just died one day and refused to be charged. I got a new battery under warranty.
But even with a new battery it's been acting wierd. Random restarts after which the battery indicator would show red explanation mark. Had to take out the battery and reboot for it to work normal again.
It might be that my phone is defective and just kills batteries.
But in case of the backlight, the battery still charges normally (at least the indicators shows that it does).
Any idea what is going on with my phone? Had anyone experienced something similar? Could it be caused by software? Are there any hard reset options I can try?
And second question, if I will have to go to warranty, is there a way to relock the bootloader? And, I am sure I could find it, but if anyone has it handy, could you link me to a place where I can get the original WIND ROM and original Kernel?
What do you think are my chances of the warranty being granted?
Greg
Porcupine00 said:
Hi all,
I am a proud owner of HTC Amaze, running BulletProof ROM with Faux Kernel v08.
The issue I am experiencing is most probably hardware issue, but I still hope it is not.
My backlight does not work at all. The phone works fine, and under heavy light you can see the actual screen, and can operate the phone as usual, but of course, otherwise, the phone is unusable, since you cannot see anything.
I've tried factory reset, restored to previous backup, charged it till full, left it without battery for few hours, nothing helped. Backlight is simply not there.
Soft buttons have the backlight, but not the screen.
There is a chance that it could be a battery issue (caused by phone), since it is my second battery, original one just died one day and refused to be charged. I got a new battery under warranty.
But even with a new battery it's been acting wierd. Random restarts after which the battery indicator would show read explanation mark. Had to take out the battery and reboot for it to work normal again.
It might be that my phone is defective and just kills batteries.
But in case of the backlight, the battery still charges normally (at least the indicators shows that it does).
Any idea what is going on with my phone? Had anyone experienced something similar? Could it be caused by software? Are there any hard reset options I can try?
And second question, if I will have to go to warranty, is there a way to relock the bootloader? And, I am sure I could find it, but if anyone has it handy, could you link me to a place where I can get the original WIND ROM and original Kernel?
What do you think are my chances of the warranty being granted?
Greg
Click to expand...
Click to collapse
Well i am sorry to say i cant tell you whats wrong, but i can answer one of your questions. Yes, you can relock the bootloader, but it says "relocked". But if it is a hardware problem, being unlocked or relocked shouldnt matter, they should still warranty it for you.. if it is in fact a hardware issue that is..
Sent from my NRGized Amaze...
via xda premium
If you plan on sending in for warranty, there's no harm in using the ruu to go back to stock and seeing if in fact it is something with the software
mrmako777 said:
If you plan on sending in for warranty, there's no harm in using the ruu to go back to stock and seeing if in fact it is something with the software
Click to expand...
Click to collapse
I was just thinking the same thing. but he had mentioned he didnt kno where to get the original wind rom from. But ya, definately go back to stock and see what happens. If ur still having the problem, then i would bet its safe to say that is a problem with the phone not something you did.
As for the shipped Wind Mobile rom, you can find the RUU here:
http://forum.xda-developers.com/showthread.php?t=1335703
Rom||RUU|| Shipped Ruby ROM Collection
There is also a link in that thread to show you how to "relock" you bootloader.
Hope this helps. If you need help or run into any problems when trying to relock and go back to stock rom, just let me know man, ive had to do it on my phone too so ya, Good luck bro!
Sent from my NRGized Amaze...
via xda premium
Thanks all for the reply.
Well, finding WIND RUU wasn't a challenge at all . Thanks for the link anyways.
Never thought I would have to go back to that creature again.
I will give it a try. Also one of my work buddies has the same phone, so I'll swap batteries with him to eliminate another potential issue.
Even though we have the same phones and the same provider, he always jokes around by saying that I have a crappy phone (our old tradition, back from the time we had different phones). Well at last he might be correct
Porcupine00 said:
Thanks all for the reply.
Well, finding WIND RUU wasn't a challenge at all . Thanks for the link anyways.
Never thought I would have to go back to that creature again.
I will give it a try. Also one of my work buddies has the same phone, so I'll swap batteries with him to eliminate another potential issue.
Even though we have the same phones and the same provider, he always jokes around by saying that I have a crappy phone (our old tradition, back from the time we had different phones). Well at last he might be correct
Click to expand...
Click to collapse
Hah i was going to suggest that, but then i thought about it and if ur phone is for some reason frying batteries, then i figured u wouldnt want to try someone elses and then end up having to buy them a new battery lol
Sent from my NRGized Amaze...
via xda premium
aj_2423 said:
Hah i was going to suggest that, but then i thought about it and if ur phone is for some reason frying batteries, then i figured u wouldnt want to try someone elses and then end up having to buy them a new battery lol
Sent from my NRGized Amaze...
via xda premium
Click to expand...
Click to collapse
Well, it's not like it fries it instantaneously, it takes time and effort from my phone to do it
So if I'll insert it for few second to see if my backlight will come back, battery won't die, and I'll I know what's wrong with my phone, and that there is no point of me getting the third battery, since the same fate will be awaiting it.
In any case, if return to stock won't help, warranty is the only option, which is sad
I was given a htc DNA and it's been one headache after another. It had a cracked digitizer, s-off, eng hboot, unlocked boot loader and a custom recovery installed on it when it was given to me. Trying to make a long story short, I ended up having to replace the board with the sim card reader on it and immediately after putting the new board in the cameras quit working along with the speakers and microphone. I was able to get all but the cameras working, but then I bricked it, and here is how. I was attempting to return back to stock, relocked the boot loader, was attempting to use a ruu which wasn't working, so I decided to unlock my boot loader again. The story ends with me attempting the unlock with ez-unlock, and when I did it said successful and I was able to keep using the phone as normal, but after turning the phone off it wouldnt turn back on, and the only sign of life comes when I plug it into my computer. As soon as i connect it to my computer, htc sync manager opens up but says no phone connected, device manager will show the phone as my htc and android 1.0.. I've experienced similar signs of life from an htc vivid, but it's issues were due to a bad battery, so I am hoping for the best but expecting this to end with jtag. Can anybody help me out please, it would be great to not require jtag services, but it would be better yet if I could gain a better understanding of at least what went wrong. Thank you
TELE-FLASH said:
I was given a htc DNA and it's been one headache after another. It had a cracked digitizer, s-off, eng hboot, unlocked boot loader and a custom recovery installed on it when it was given to me. Trying to make a long story short, I ended up having to replace the board with the sim card reader on it and immediately after putting the new board in the cameras quit working along with the speakers and microphone. I was able to get all but the cameras working, but then I bricked it, and here is how. I was attempting to return back to stock, relocked the boot loader, was attempting to use a ruu which wasn't working, so I decided to unlock my boot loader again. The story ends with me attempting the unlock with ez-unlock, and when I did it said successful and I was able to keep using the phone as normal, but after turning the phone off it wouldnt turn back on, and the only sign of life comes when I plug it into my computer. As soon as i connect it to my computer, htc sync manager opens up but says no phone connected, device manager will show the phone as my htc and android 1.0.. I've experienced similar signs of life from an htc vivid, but it's issues were due to a bad battery, so I am hoping for the best but expecting this to end with jtag. Can anybody help me out please, it would be great to not require jtag services, but it would be better yet if I could gain a better understanding of at least what went wrong. Thank you
Click to expand...
Click to collapse
You can't boot into anything? Not even bootloader mode?
.torrented said:
You can't boot into anything? Not even bootloader mode?
Click to expand...
Click to collapse
Sadly no, I can't get it to boot at all. I also need to mention that the lights don't come on when it's plugged in either. I'm thrown for a loop by it all because my computers will still react to it if I hook it up to them with usb, but that's about all they will do. Why would sync manager open up when I plug it in, but then state that there is no device connected.
Ive seen where people have said to leave phone charging for 24 hours without trying to turn it on and it worked. I've also seen people run a calibration test on the battery but I forgot how to do it.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
EZ-Unlock is an unsupported method by the DNA hardware. It will always cause a hard-brick. Which you have done. I did this to myself at one point, too. I tried EZ-Unlock and it hard-bricked my DNA. Call Verizon. Tell them that it just randomly started doing this. Don't mention root or anything. They'll replace it for free. That's what I did.
Sorry about that bud. Try to do some more research before modding your phone next time.
TELE-FLASH said:
Sadly no, I can't get it to boot at all. I also need to mention that the lights don't come on when it's plugged in either. I'm thrown for a loop by it all because my computers will still react to it if I hook it up to them with usb, but that's about all they will do. Why would sync manager open up when I plug it in, but then state that there is no device connected.
Click to expand...
Click to collapse
Oh I see.
ryanguy426 said:
EZ-Unlock is an unsupported method by the DNA hardware. It will always cause a hard-brick. Which you have done. I did this to myself at one point, too. I tried EZ-Unlock and it hard-bricked my DNA. Call Verizon. Tell them that it just randomly started doing this. Don't mention root or anything. They'll replace it for free. That's what I did.
Sorry about that bud. Try to do some more research before modding your phone next time.
Click to expand...
Click to collapse
Or, he could so kindly ask Zarboz to jtag it for him and fix it possibly. I'm not saying he will jtag it but he does jtag work, so if you want to know more you should pm him about it.
Yeah I forgot Z could JTAG it... Thanks for posting that. I am sure that he will be more than happy to JTAG it for him.
Sent from my HTC Droid DNA using XDA Premium 4 mobile app
Can you get into the bootloader by holding power+volume down for any amount of time?
Have you let it sit on the charger over night?
Hold power down for at least 20 seconds to a minute?
Sent from my HTC Droid DNA using XDA Premium 4 mobile app
.torrented said:
Oh I see.
Or, he could so kindly ask Zarboz to jtag it for him and fix it possibly. I'm not saying he will jtag it but he does jtag work, so if you want to know more you should pm him about it.
Click to expand...
Click to collapse
Well thank you for your feedback, and assistance. I owe most everything I know about phones to XDA and it's members! Regarding my situation with the DNA, yup sure enough it is bricked. I figured it was, but have had similar reactions from a bad battery in the past, so.. Regarding the process of unlocking the boot loader, this is the first time I've ever directly seen anything regarding the cid. Not sure if maybe it has been part of the process in ways that I was unaware of in the past with other phones or if this is more device specific, but either way would anybody possibly know where I could find more in depth information regarding this and if there is anybody who is knowledgeable with this that wouldn't mind helping somebody out?
sorry for the run on sentences lol
oh, and thank you for the referral to Zarboz, I will definitely be getting in touch with him.