Related
Ive see a lot of threads about Prime's screen tearing and stuff but nothing like what is happiening with mine...
I've got this the first time a few months ago, and usually a reboot, or a long time without using it, or even a factory reset would make it go back... I wasnt getting it for a while, but now... no reboot is working...
want to know if anyone got anything like this, and if its really hardware and i will have to take it to ASUS...
Taking to ASUS is not really an option right now cuz I am not in the country I bought it right now and will take more two weeks to go back there...
Is there any way to flash a firmware through adb? would love if someone could walk me through it... thats the only hope I have right now.... unless someone have a better idea...
I am still hoping this is software... maybe a variant of what many people has been getting... since as far as I remember this started happen after ICS update
Thanks guys
It's dead Jim. RMA it. Looks like a loose connection.
leppie said:
It's dead Jim. RMA it. Looks like a loose connection.
Click to expand...
Click to collapse
Maybe, but only if it is a cable I couldn't check.... I just opened it, checked the cables and still same ****....
I had the same issue. I dropped my prime and then this happened. I had to RMA it.
have you tried reboot it using the pin hole by the micro sd card?
Guys i just want to report I had to RMA it. About 3 weeks after i gt it back perfectly working. They replaced the lcd pannel. But the most interesting is the device has an unlocked bootloader. Nevertheless it was taken care of under the warranty! Amazing that Asus is honoring unlocked devices' warranties for problems unrelated to it. Great job Asus!
Hi, uh I started another thread on making sure things got backed up. Which I did properly and everything was good. So today I haven't done anythign and was waiting for the new slim rom to make it's debute hopefully this week sometime as that is the one that appeals to me the most. Anyways, today my phone just got super hot, far hotter than before and it decided to die on me...I think. it shut off and I haven't been able to turn it on. Could this be a side effect of installing twrp/unlocking the bootloader/rooting? Or would it be a defective unit? One concern I had was getting a defective unit so i waited out my 30 days before even considering doing all this. So yea my 30 days from att is up. Would there possibly be a way to get a new phone from att or does anyone have any tricks on getting it back online? I personally think it was an overheating issue, but my phone is now cooled down.
So i went to the att store and of course they won't do anything. They told me to call some number they gave me. If I return it will they know it was boot unlocked and rooted? I can't turn it on at all. Using a power source or connecting to my computer nor my car charger...
blamster said:
Hi, uh I started another thread on making sure things got backed up. Which I did properly and everything was good. So today I haven't done anythign and was waiting for the new slim rom to make it's debute hopefully this week sometime as that is the one that appeals to me the most. Anyways, today my phone just got super hot, far hotter than before and it decided to die on me...I think. it shut off and I haven't been able to turn it on. Could this be a side effect of installing twrp/unlocking the bootloader/rooting? Or would it be a defective unit? One concern I had was getting a defective unit so i waited out my 30 days before even considering doing all this. So yea my 30 days from att is up. Would there possibly be a way to get a new phone from att or does anyone have any tricks on getting it back online? I personally think it was an overheating issue, but my phone is now cooled down.
So i went to the att store and of course they won't do anything. They told me to call some number they gave me. If I return it will they know it was boot unlocked and rooted? I can't turn it on at all. Using a power source or connecting to my computer nor my car charger...
Click to expand...
Click to collapse
Ok, so, im not sure if by return you mean, return for an exchange or simply a return as ATT will probably only send you a reman unit for yours and not allow an actual return. If you havent called them yet, i would recommend it. I have dealt with them many times in the past and one thing that has always shocked me is that they never have asked me about, or even commented on, how rooting or unlocking prevents them from exchanging it. Even during the disclaimer, they have never once said that if the device has been modified they wont allow the exchange.
I say all of this because should they not mention anything like that, and you send it back, im fairly sure you can claim you didnt know and werent told, and they will take care of it. Also, i say this because i personally sent back 3 bricked GS2s and an lg nitro as defective and got my reman units and every single one of them were rooted and such. So, i would feel safe. As long as they dont ask, and you dont lie to them, then there shouldnt be an issue. I wouldnt lie to them, i just dont mention it. AGAIN DO NOT lie to them or attempt to decieve them, i would never encourage that, but if its something they dont ask about, then, it, in my opinion, is not something that they are too concerned with.
cloudraker said:
Ok, so, im not sure if by return you mean, return for an exchange or simply a return as ATT will probably only send you a reman unit for yours and not allow an actual return. If you havent called them yet, i would recommend it. I have dealt with them many times in the past and one thing that has always shocked me is that they never have asked me about, or even commented on, how rooting or unlocking prevents them from exchanging it. Even during the disclaimer, they have never once said that if the device has been modified they wont allow the exchange.
I say all of this because should they not mention anything like that, and you send it back, im fairly sure you can claim you didnt know and werent told, and they will take care of it. Also, i say this because i personally sent back 3 bricked GS2s and an lg nitro as defective and got my reman units and every single one of them were rooted and such. So, i would feel safe. As long as they dont ask, and you dont lie to them, then there shouldnt be an issue. I wouldnt lie to them, i just dont mention it. AGAIN DO NOT lie to them or attempt to decieve them, i would never encourage that, but if its something they dont ask about, then, it, in my opinion, is not something that they are too concerned with.
Click to expand...
Click to collapse
Okay, thanks for the response. Sorry I was in a bit of a panic when I wrote that. But I have called ATT and they didn't ask me or mention in any disclaimer that if it's rooted or unlocked it won't qualify. I didn't mention it and so that does make me feel a lot better. Hasn't been physically damaged or come in contact with water so i'm pretty sure I'm safe. Thanks again.
blamster said:
Okay, thanks for the response. Sorry I was in a bit of a panic when I wrote that. But I have called ATT and they didn't ask me or mention in any disclaimer that if it's rooted or unlocked it won't qualify. I didn't mention it and so that does make me feel a lot better. Hasn't been physically damaged or come in contact with water so i'm pretty sure I'm safe. Thanks again.
Click to expand...
Click to collapse
They may or may not check when you return the phone. I returned my S3 a few months ago in exchange for a different phone but I forgot to unroot it and uninstall Superuser. The representative at AT&T didn't even turn the phone on. I didn't have anything to hide though, if they told me I couldn't return it because it was rooted then I would have sold it and purchased something else. I think the manufacturer is the one to worry about with these things. LG would definitely know if it were unlocked and they would be able to determine if rooting and unlocking the phone caused the problems you described.
johnbyebye said:
They may or may not check when you return the phone. I returned my S3 a few months ago in exchange for a different phone but I forgot to unroot it and uninstall Superuser. The representative at AT&T didn't even turn the phone on. I didn't have anything to hide though, if they told me I couldn't return it because it was rooted then I would have sold it and purchased something else. I think the manufacturer is the one to worry about with these things. LG would definitely know if it were unlocked and they would be able to determine if rooting and unlocking the phone caused the problems you described.
Click to expand...
Click to collapse
Well if they can turn it on I will gladly take it back due to them not accepting. I couldn't turn it on by anymeans, even plugging it in there is no lights to signifying it is receiving power. But i heard this phone had overheating issues in the first wave (or two) so it's probably for the best to get a new one. They are currently mailing me a new one and so I should receive it next week sometime hopefully.
blamster said:
Well if they can turn it on I will gladly take it back due to them not accepting. I couldn't turn it on by anymeans, even plugging it in there is no lights to signifying it is receiving power. But i heard this phone had overheating issues in the first wave (or two) so it's probably for the best to get a new one. They are currently mailing me a new one and so I should receive it next week sometime hopefully.
Click to expand...
Click to collapse
Sounds like everything worked out.
im in the same boat as you... completely dead phone. But I did open it to see of the battery pull would work. Do you think that theyll check and refuse my warranty because I opened it? the phone on the outside is NEW. Btw do you have a contract/account with ATT? I bought mine off ebay and used it on tmo...
I have the exact same problem! Totally dead phone that the charging light won't even turn on for. Unfortunately there is a small crack in the bottom left of the phone that was caused months prior so ATT wont give me a new one...
send it for repairs! I had rooted and unlocked mine so ATT didnt cover my warranty, but I only paid 50 bucks for the repairs and now I have my phone back!
Hello kind and helpful people of XDA.
I am currently looking for some help regarding warranty on my recently diseased Galaxy S2 (SN: i9100GSMH).
Story:
I dropped it on a wooden floor while it was on. The OS kept chugging along, but would only open apps that was already in RAM after the incident.
Noticing trouble, I immediately thought a reboot would fix all my problems. Now it seems the internal memory is dead.
Now I'm trying to make it eligible for warranty, at least by removing the traces of root and unsafe kernel.
I figure that even though I'm sending it in because of a physical defect, they will send it back immediately because of the unsupported firmware.
Symptoms:
I can't enter recovery mode.
I can't boot the OS. It gets stuck on the Siyah kernel logo (big root giveaway, I want it gone).
I can't write to NAND neither through Odin nor Kies (Kies doesn't even connect).
I can enter Download Mode, but of course it shows that I have a custom binary installed. My install count is 1.
Do I have any options? I've heard of some JTAG method that would be able to at least reset the counter (as far as I understand). Is this true?
Regarding the warranty: I am not referring to the standard warranty.
I've paid big cash for a warranty/insurance that covers accidents. My brother dropped his LG Optimus X2 in the toilet, returned it to the exact same store with the exact same type of warranty and got a new one.
With a service like this at hand I really want to try anything to make it eligible for warranty(/insurance).
I have never used my root permissions in any harmful way. I only did it because of the AdFree app, and my favourite ROM DiLiDroid.
I've had great success with rooting and installing various software on my old SE Xperia X1 and HTC Desire (they aren't dead yet, and are my current backup phones),
so I thought it wouldn't hurt with the GS2. Seems I'm paying the price now :crying:
Thank you very much for your time!
If anyone can help me, I'll definitely buy you a beer or a cup of coffee!
Well, an usb jig will reset the binary counter.
About the siyah animaton boot....yakes, if your nand is damaged you'll have to brick it (with a pit file no one is gonna know what the hell you've done with your device).
Then again, have you even tried to make the pc to see the phone? It's worth the try.
Sent from the little guy
Nobody here can do or say anything about any warranty. Anyone claiming the same is lying to you.
If this warranty of yours covers accidents & you had an 'accident', send it in & see what happens. You're not going to get the certainty you're looking for from anyone on an internet forum.
If the phone won't boot, there isn't anything further you can do with it.
I've just read all the little details about my insurance.
It covers liquid damage, screen fractures and other physical accidents one time a year, so I guess I have to give it a whirl in the toilet.
Hopefully that will kill the traces.
The jig sounds like a must have for anyone tinkering with root. Thanks for confirming my theory.
I will definitely crawl the net for one. Special electronics 'equipment' is hard to come by here in Denmark, and I don't think I have the required solder skills to make one myself.
I do find this guide very helpful though: http://forum.xda-developers.com/showthread.php?t=1604707
This also sounds like the best way to go about this situation, as I can be totally honest about the reason for my phone not working anymore.
Thank you for your time!
If you're gonna flush it, do it right
S2 are hardcore muthaf***ers, they don't die easy. Make sure it doesn't boot after spending 2 days in a bucket of rice.
Sent from the little guy
I realize this as my device has been through some terrible things.
I've ordered a USB Jig, costing about 10$ in total, it should arrive on Wednesday.
If it works I'll be a very happy man as I won't have to lie about the actual defect.:victory:
Here's my problem XDA Gods:
I've recently made a huge mistake, I was %&$#ing around with roms for the HDX and with Hashcode's Safestrap and had my phone fully rooted with the ADB drivers installed on my pc. I was using the default rom slot to operate(Yes it's stupid, but I have problems working with under 8gb of space and it was working fine.). Through an accidental factory reset I managed to delete my safestrap backup and screw up the current Rom. So I went into safestrap and tried to flash a new rom which suddenly wouldn't flash correctly. So I did advanced wipe and cleared everything and rebooted the device whilst still set to bootup from the default rom slot. My Proceeded to then bootloop the grey kindle logo. In a panic trying to fix it, I did the factory reset by holding the volume and power buttons (Another stupid move in my game of life.). Now when I plug it into a PC it reads the device as MTP USB Device and proceeds to fail installing Drivers that I've already installed. Adb wont recognize the device and I'm currently attempting to reinstall all my drivers.
To Sum It Up:
* My Device Can't Boot Into Safestrap
* My Device Can't Boot Past The Kindle Gray Logo
* My Computers wont recognize the kindle and calls it an MTP USB Device and fails driver installation.
*ADB also rejects my love.
Dear XDA Gods, I pray to thee for divine help and request the speedy help of thy talents. Many goats I will sacrifice for any that will help. I have scoured the Internet looking for a holy answer and have stumbled only upon ADB fixes to which I cannot. Please look upon my request and help me fly through this terrible storm.
From what I understand...
...this is a brick situation. Not to be a debby downer but I found myself in the same situation. I spent countless hours in the XDA forums and beyond, read every Android Cowboy post (who knows his way around this issue), tried a fastboot cable (didn't work), and even looked for a way to JTAG the internal memory - all to no avail. My advice - if you can't get ADB to wreckonize, accept your fate and flaunt your expensive taste in paperweights because, indeed, the stakes of being a tinkerer are high.
zomblitous said:
Here's my problem XDA Gods:
I've recently made a huge mistake, I was %&$#ing around with roms for the HDX and with Hashcode's Safestrap and had my phone fully rooted with the ADB drivers installed on my pc. I was using the default rom slot to operate(Yes it's stupid, but I have problems working with under 8gb of space and it was working fine.). Through an accidental factory reset I managed to delete my safestrap backup and screw up the current Rom. So I went into safestrap and tried to flash a new rom which suddenly wouldn't flash correctly. So I did advanced wipe and cleared everything and rebooted the device whilst still set to bootup from the default rom slot. My Proceeded to then bootloop the grey kindle logo. In a panic trying to fix it, I did the factory reset by holding the volume and power buttons (Another stupid move in my game of life.). Now when I plug it into a PC it reads the device as MTP USB Device and proceeds to fail installing Drivers that I've already installed. Adb wont recognize the device and I'm currently attempting to reinstall all my drivers.
To Sum It Up:
* My Device Can't Boot Into Safestrap
* My Device Can't Boot Past The Kindle Gray Logo
* My Computers wont recognize the kindle and calls it an MTP USB Device and fails driver installation.
*ADB also rejects my love.
Dear XDA Gods, I pray to thee for divine help and request the speedy help of thy talents. Many goats I will sacrifice for any that will help. I have scoured the Internet looking for a holy answer and have stumbled only upon ADB fixes to which I cannot. Please look upon my request and help me fly through this terrible storm.
Click to expand...
Click to collapse
---------- Post added at 12:18 PM ---------- Previous post was at 12:04 PM ----------
Google "Setting Up Your Kindle Fire Tablet for Testing" there is an article that might help to get ADB up.
This may be helpful to try to get ADB working. Also, a fastboot cable might be worth a try, though I don't think it will work if you don't get ADB working. Did you modify build.prop? Delete any system files?
I am sure that there is a way to restore through QPST:
http://forum.xda-developers.com/showthread.php?p=49862146
but I lack the skills to complete this process
Thanks
Thanks for the speedey responses guys, I'll try the QTSP method when I have time, but still thanks. Any other help is good to.
Same happened to me also , and i contacted with Amazon Customer Service. I explained whole situation ( that i tried the install gapps and bricked it like you - same way - ) they offered me a replacement. Then they sent me a new Kindle.
If you cant do anything just contact with them and explain everything. They will help im sure about that.
They are the most amazing Customer Service i've ever seen in my life. Just 2 days , i got my new Kindle and sent bricked one back.
Also they sent me a email for return shipping expenses. I used it at UPS and did not paid any money for return shipping.
Aren't they amazing?
Really!?!?
squee9 said:
Same happened to me also , and i contacted with Amazon Customer Service. I explained whole situation ( that i tried the install gapps and bricked it like you - same way - ) they offered me a replacement. Then they sent me a new Kindle.
If you cant do anything just contact with them and explain everything. They will help im sure about that.
They are the most amazing Customer Service i've ever seen in my life. Just 2 days , i got my new Kindle and sent bricked one back.
Also they sent me a email for return shipping expenses. I used it at UPS and did not paid any money for return shipping.
Aren't they amazing?
Click to expand...
Click to collapse
So even after ""breaking the system"" I'll get my money back. I dont have a warranty by the way, and I got it in December. Will that effect anything.
zomblitous said:
So even after ""breaking the system"" I'll get my money back. I dont have a warranty by the way, and I got it in December. Will that effect anything.
Click to expand...
Click to collapse
I have to admit I went through something very similar to you with my first HDX. I wiped the system without fully understanding it and afterwards it was bricked with my computer being unable to recognize it.
I also spent quite a bit of time looking for a solution but ultimately it was far easier talking to Amazon about this and having them send a replacement. Now with my second HDX I didn't make the same mistake twice.
I didn't tell the truth though. I just said that after I powered it on one day it would get stuck on the boot screen and after a troubleshoot run through Amazon offered a replacement.
Good luck.
Fastboot & the system
lawnnewm said:
...this is a brick situation. Not to be a debby downer but I found myself in the same situation. I spent countless hours in the XDA forums and beyond, read every Android Cowboy post (who knows his way around this issue), tried a fastboot cable (didn't work), and even looked for a way to JTAG the internal memory - all to no avail. My advice - if you can't get ADB to wreckonize, accept your fate and flaunt your expensive taste in paperweights because, indeed, the stakes of being a tinkerer are high.
---------- Post added at 12:18 PM ---------- Previous post was at 12:04 PM ----------
Google "Setting Up Your Kindle Fire Tablet for Testing" there is an article that might help to get ADB up.
This may be helpful to try to get ADB working. Also, a fastboot cable might be worth a try, though I don't think it will work if you don't get ADB working. Did you modify build.prop? Delete any system files?
Click to expand...
Click to collapse
Well I did the advanced system wipe, I think I may have just wiped off all traces of a rom by formatting the system, I havent touched the build.prop or any file like that, only format. Also I'll grab a fastboot cable off ebay and give tinkering a try,
Thanks
zXiC said:
I have to admit I went through something very similar to you with my first HDX. I wiped the system without fully understanding it and afterwards it was bricked with my computer being unable to recognize it.
I also spent quite a bit of time looking for a solution but ultimately it was far easier talking to Amazon about this and having them send a replacement. Now with my second HDX I didn't make the same mistake twice.
I didn't tell the truth though. I just said that after I powered it on one day it would get stuck on the boot screen and after a troubleshoot run through Amazon offered a replacement.
Good luck.
Click to expand...
Click to collapse
Well, best to have a working kindle and bad karma than an expensive paperweight, i'll give a fastboot cable a try first and use this as a last attempt. Thanks, also, when did you get the replacement and did you have a warranty?
zomblitous said:
Well, best to have a working kindle and bad karma than an expensive paperweight, i'll give a fastboot cable a try first and use this as a last attempt. Thanks, also, when did you get the replacement and did you have a warranty?
Click to expand...
Click to collapse
Rubbish. A bad kindle is a temporary thing. Bad karma lasts a lifetime & even if you can work it off, it's on a sliding scale approximately 1000:1.
The worst thing you can do is panic. 99.999% of devices can be recovered. However, you greatly increase your chances of being in that screwed .001% statistically by panicking & doing things like factory resetting or rebooting.
Personally, after sitting down to think about it, I can say I have actually borked my device 23 times. Nearly every three times, it was a different issue, since I was recreating issues to find solutions for others. To this day, I still have my FIRST HDX. I even got the update, the one that nobody can reverse. Guess what? I'm rooted, have SafeStrap & GAPPS still, because I didn't panic.
When you screw something up, you have to walk away. 3 out of 4 times, if you react to an issue without planning & reasoning, you will only make things worse, particularly if you really have no idea what you are doing & how Linux, Android Bootloaders & firmware in general work together. You don't need to know every detail, but a basic understanding at the very least. Listen, I am by no means a developer. I am a butcher hack of a coder, but I am a mechanical engineer & so I approach everything methodically, especially when dealing with something I do not know. Knowing your limits can be the most important thing to know at times & when you have stepped outside of your knowledge base, reacting with a guess rarely goes good. Just ask all the folks leaving Las Vegas casinos without their money. The bottom line is that bad things happen when you panic & let fear take hold. Bad things happen when you think you know more than you do.
What also helps me, is that this is my NEWEST username (you used to be able to have multiple, for different devices, etc), which is from 2006. I am pretty sure my first login was from 2002, maybe early 2003. When I joined I didn't do anything other than lurk, read, ask questions & follow things that interested me in IRC for a year & a half. I never even posted for the first 9 months I was around. I used PM & IRC, then it was only to ask questions to things I could find answers too reading through the earlier posts. Again, there are brand new members that understand & have abilities in technology that far outstrip anything I'll ever comprehend. Just like there were over a decade ago. Find those people & become friends. Follow one of the tutorials on building a basic app or building a rom like CM or AOSP or any of the other open roms from scratch. You'll learn something new, I garuntee it & it will come in handy some day, even if it's just a hobby. Of course things are different at XDA these days. It used to be that EVERY member was here to learn how to do these things for themselves & to share the experience & what was learned. Now, you still have some of those types, but predominantly, you have members that are here just because they want someone else to make a theme, or mod, or fix for them & they have no desire to contribute.
At any rate, I don't have the time to keep up with all the bootloops & bricks these days. Right now, work is crazy busy & that is what pays the bills, so it takes precedence over everything else. I'll start answering PM's & taking a look at borked devices again when things slow down again, however, I think I could probably recover 8 out of 10 if I had it in my hands & so could you. For those of you unwilling to give up, I suggest you read around other forums, check out some of the qualcomm developer forums & find some of the very talented developers that participate in those communities too. Most of them WILL take the time, not necessarily to fix your problem, but to answer questions & even to teach you a thing or two, if you are sincere about wanting to learn & not just looking for the first sucker to fix whatever problem you have.
GSLEON3 said:
Rubbish. A bad kindle is a temporary thing. Bad karma lasts a lifetime & even if you can work it off, it's on a sliding scale approximately 1000:1.
The worst thing you can do is panic. 99.999% of devices can be recovered. However, you greatly increase your chances of being in that screwed .001% statistically by panicking & doing things like factory resetting or rebooting.
Personally, after sitting down to think about it, I can say I have actually borked my device 23 times. Nearly every three times, it was a different issue, since I was recreating issues to find solutions for others. To this day, I still have my FIRST HDX. I even got the update, the one that nobody can reverse. Guess what? I'm rooted, have SafeStrap & GAPPS still, because I didn't panic.
When you screw something up, you have to walk away. 3 out of 4 times, if you react to an issue without planning & reasoning, you will only make things worse, particularly if you really have no idea what you are doing & how Linux, Android Bootloaders & firmware in general work together. You don't need to know every detail, but a basic understanding at the very least. Listen, I am by no means a developer. I am a butcher hack of a coder, but I am a mechanical engineer & so I approach everything methodically, especially when dealing with something I do not know. Knowing your limits can be the most important thing to know at times & when you have stepped outside of your knowledge base, reacting with a guess rarely goes good. Just ask all the folks leaving Las Vegas casinos without their money. The bottom line is that bad things happen when you panic & let fear take hold. Bad things happen when you think you know more than you do.
What also helps me, is that this is my NEWEST username (you used to be able to have multiple, for different devices, etc), which is from 2006. I am pretty sure my first login was from 2002, maybe early 2003. When I joined I didn't do anything other than lurk, read, ask questions & follow things that interested me in IRC for a year & a half. I never even posted for the first 9 months I was around. I used PM & IRC, then it was only to ask questions to things I could find answers too reading through the earlier posts. Again, there are brand new members that understand & have abilities in technology that far outstrip anything I'll ever comprehend. Just like there were over a decade ago. Find those people & become friends. Follow one of the tutorials on building a basic app or building a rom like CM or AOSP or any of the other open roms from scratch. You'll learn something new, I garuntee it & it will come in handy some day, even if it's just a hobby. Of course things are different at XDA these days. It used to be that EVERY member was here to learn how to do these things for themselves & to share the experience & what was learned. Now, you still have some of those types, but predominantly, you have members that are here just because they want someone else to make a theme, or mod, or fix for them & they have no desire to contribute.
At any rate, I don't have the time to keep up with all the bootloops & bricks these days. Right now, work is crazy busy & that is what pays the bills, so it takes precedence over everything else. I'll start answering PM's & taking a look at borked devices again when things slow down again, however, I think I could probably recover 8 out of 10 if I had it in my hands & so could you. For those of you unwilling to give up, I suggest you read around other forums, check out some of the qualcomm developer forums & find some of the very talented developers that participate in those communities too. Most of them WILL take the time, not necessarily to fix your problem, but to answer questions & even to teach you a thing or two, if you are sincere about wanting to learn & not just looking for the first sucker to fix whatever problem you have.
Click to expand...
Click to collapse
Thanks for the pep-talk, I haven't even thought about giving up, and I don't really want to just get out the easy lying way. But sadly my problem is one of few and will take time even with the help of power techies. I really only have one option at the moment and that is to continue troubleshooting and ignore everyone who just says that i have acquired a taste in paperweights. And Thanks anyway, means alot when a member takes time just to cheer ya on.
zomblitous said:
Well, best to have a working kindle and bad karma than an expensive paperweight, i'll give a fastboot cable a try first and use this as a last attempt. Thanks, also, when did you get the replacement and did you have a warranty?
Click to expand...
Click to collapse
Replacement was expediated by Amazon so in two days.
You have a limited warranty for a year. You just have to convince Amazon that your problem falls under that.
Edit: It's admirable to try and fix it yourself but in my opinion it's far too time consuming.
1 year then...
zXiC said:
Replacement was expediated by Amazon so in two days.
You have a limited warranty for a year. You just have to convince Amazon that your problem falls under that.
Edit: It's admirable to try and fix it yourself but in my opinion it's far too time consuming.
Click to expand...
Click to collapse
Well I have about a year then.
I've got insurance for my cell phone through my credit card. If it breaks, they'll send me $250 to buy a new one. And my RAZR Maxx is definitely messed up.
The problem is, the problems are intermittent. And for me to make a successful claim, I have to get a technician to look at the phone and write a letter saying it's broken. I had to go through this process a couple of years ago with a Motorola Atrix that was clearly, obviously broken. And the technicians are always like, "what? what do you mean? what good is a letter like that going to do?" No matter how many times I try to explain to them. It's like they think I'm trying to trap them.
Anyway, is there anything short of throwing the phone off the top of my house that I can do to my phone that makes it easy to show to a technician and have him verify there are issues with it? I'd like not to destroy the phone in case my claim is denied. There are other criteria other than just proving phone is broken. And if the claim is denied, I may need to use the phone for a few more months till I can afford to buy a new one.
The phone is rooted. So I can install whatever software that needs the phone to be rooted. And I have asked in the past, rooting the phone does not cancel my insurance. The case is basically the cell phone insurance department doesn't seem very technologically savvy and don't have a lot of clauses you see when cell phone company's are describing cell phone warranties. Then they have other clauses that you would never see in a cell phone warranty.
If you want to know what's wrong with my phone, like occasionally, nothing it can do will it lock onto the GPS satellites, and I'm stuck somewhere trying to navigate my way to some place.. Occasionally it'll pop up on my screen saying "HDMI cable detected" and orient my screen sideways like if the phone were in a dock. It does this even though there's clearly no HDMI cable connected and I have turned HDMI detection off in the settings. Plus, the phone is just god awful slow a lot of times. Trying to use Chrome on the phone, a lot of times it'll hang and eventually I'll get the message "Chrome is not reponding", then I have options like do you want to wait for it, or go ahead and kill it.
levander said:
I've got insurance for my cell phone through my credit card. If it breaks, they'll send me $250 to buy a new one. And my RAZR Maxx is definitely messed up.
The problem is, the problems are intermittent. And for me to make a successful claim, I have to get a technician to look at the phone and write a letter saying it's broken. I had to go through this process a couple of years ago with a Motorola Atrix that was clearly, obviously broken. And the technicians are always like, "what? what do you mean? what good is a letter like that going to do?" No matter how many times I try to explain to them. It's like they think I'm trying to trap them.
Anyway, is there anything short of throwing the phone off the top of my house that I can do to my phone that makes it easy to show to a technician and have him verify there are issues with it? I'd like not to destroy the phone in case my claim is denied. There are other criteria other than just proving phone is broken. And if the claim is denied, I may need to use the phone for a few more months till I can afford to buy a new one.
The phone is rooted. So I can install whatever software that needs the phone to be rooted. And I have asked in the past, rooting the phone does not cancel my insurance. The case is basically the cell phone insurance department doesn't seem very technologically savvy and don't have a lot of clauses you see when cell phone company's are describing cell phone warranties. Then they have other clauses that you would never see in a cell phone warranty.
If you want to know what's wrong with my phone, like occasionally, nothing it can do will it lock onto the GPS satellites, and I'm stuck somewhere trying to navigate my way to some place.. Occasionally it'll pop up on my screen saying "HDMI cable detected" and orient my screen sideways like if the phone were in a dock. It does this even though there's clearly no HDMI cable connected and I have turned HDMI detection off in the settings. Plus, the phone is just god awful slow a lot of times. Trying to use Chrome on the phone, a lot of times it'll hang and eventually I'll get the message "Chrome is not reponding", then I have options like do you want to wait for it, or go ahead and kill it.
Click to expand...
Click to collapse
Have you tried returning the phone to bone stock with a stock recovery image and rsd lite? Be fore warned, you will lose root but, you can get it back. Afterwards it will be like a new phone(faster, a lot less buggy and force closes) unless it is truly a hardware issue. I have a motorola xoom that started having serious issues, I went through the whole process, and it was like a completely new tablet when was done, battery life I hadn't seen in over a year, very responsive, it was like I had just unboxed it from the store.
Truthfully the technicians probably DO think you are trying to trap them when you are talking about intermittent problems. Intermittent problems are hard to diagnose with anything unless you can tell them a specific action or pattern of actions that leads up to the problem. I am sure they get a lot of people all the time with "it doesn't work right" claims to try to get money for a new phone.
IMHO it would be worth the shot to see if it legitimately has a goofy problem, or can be easily fixed at home.
Draxin said:
Have you tried returning the phone to bone stock with a stock recovery image and rsd lite?
Click to expand...
Click to collapse
Yeah, thanks Draxin. I've tried restoring to a factory image. And it seems to work okay for a couple of days before small things start back up. A couple of months later, the phone is as flaky as it ever was. It could just be software, that is possible. But it's not like I can go in and fix the software myself or anything. And I think hanging around the internet, looking for tweaks and fixes any more than I already have is really an unreasonable request by the insurance company.
What you say about an easily repeatable pattern, that's what I was hoping to figure out by posting here.
But getting no responses, I think I'm just gonna start my claim and when it gets to the point of proving it's broken, I'm just gonna microwave the phone. Googling all over the Internet that's the only advice people seem to offer.
Basically as it is now, I'm gonna have to pay for a new phone and hope this clumsy phone insurance through my credit card company makes good on my claim. I know I meet the criteria because I've read the policy. It's just the hoops they put you through to prove you meet the criteria that I'm worried about.
levander said:
Yeah, thanks Draxin. I've tried restoring to a factory image. And it seems to work okay for a couple of days before small things start back up.
Click to expand...
Click to collapse
With a full wipe and stock motorola firmware? Or just a factory reset?
Either way wish you the best of luck
Yeah try using rsd to fully restore. I fixed a lot of my problems that way .
Sent from my XT912 using Tapatalk
tydiamond11 said:
Yeah try using rsd to fully restore. I fixed a lot of my problems that way .
Sent from my XT912 using Tapatalk
Click to expand...
Click to collapse
Very true. It is funny/sad. Spend some time on a site like this and it seems like everybody knows these things. Talk to your friend or the typical consumer of smartphones and it is foreign to them. They feed into the advertising that the newest and greatest will solve all their problems, not realizing they are falling into the same viscous circle. They will actually disbelieve you, cause... well come on, the phone is two years old! "The guy at my carriers store is surprised my phone still works. Sure he got the job two months ago, won't be there five from now and has no idea what a OTG cable is, or a independently powered usb hub but, still he works there.. so he must know what he is talking about! I am sure it has nothing to do with commission of sales!" (that was facetious, by the way)
I am curious how many people have thought that their smartphone was dying or to old because a factory reset didn't work(not talking about you lavender, I don't know what you have done to fix your device( guess I am semi-hijacking your thread)).
Motorola(or any device manufacturer for that matter) isn't going to tell the typical user that a firmware reflash is required to get a couple more years out of their device when they can sell a user (that won't waste the time to Google)another device. Certainly won't advertise it right next to their latest and greatest device. Really how many people outside of the power users or gamers REQUIRE a quad core processor with 1500-1800 mhz, or 2-3 gb of RAM. When typically, it will end up the same way in a years time, depending on how much they use it.
Porn doesn't require those specs!!!
Draxin said:
Very true. It is funny/sad. Spend some time on a site like this and it seems like everybody knows these things. Talk to your friend or the typical consumer of smartphones and it is foreign to them. They feed into the advertising that the newest and greatest will solve all their problems, not realizing they are falling into the same viscous circle. They will actually disbelieve you, cause... well come on, the phone is two years old! "The guy at my carriers store is surprised my phone still works. Sure he got the job two months ago, won't be there five from now and has no idea what a OTG cable is, or a independently powered usb hub but, still he works there.. so he must know what he is talking about! I am sure it has nothing to do with commission of sales!" (that was facetious, by the way)
I am curious how many people have thought that their smartphone was dying or to old because a factory reset didn't work(not talking about you lavender, I don't know what you have done to fix your device( guess I am semi-hijacking your thread)).
Motorola(or any device manufacturer for that matter) isn't going to tell the typical user that a firmware reflash is required to get a couple more years out of their device when they can sell a user (that won't waste the time to Google)another device. Certainly won't advertise it right next to their latest and greatest device. Really how many people outside of the power users or gamers REQUIRE a quad core processor with 1500-1800 mhz, or 2-3 gb of RAM. When typically, it will end up the same way in a years time, depending on how much they use it.
Porn doesn't require those specs!!!
Click to expand...
Click to collapse
You are right. Just the last part is not really relevant to this form by the way.
Sent from my XT912 using Tapatalk