Hi guys, so a bit of info first
So i bought my kindle fire overseas (Cyprus - where I live) - Amazon is not officially represented and i had a faulty screen that the retail didn't want to help me with as it was noticeably a factory flaw. After a heated debate they accepted it and replaced it with what i assume was a refurbished model.
At the time i was happy to have a kindle back. last night i noticed a scratch, small but annoying and i don't know how it got there as its never dropped and its always protected, i can only assume that it was there when they replaced it i just didnt see it as it only really shows when you have a white background.
they will not replace it again, so this is my question.
Is there a way for me to brick my kindle fire on purpose or permanently drain the batter so that it doesn't start up again.
I don't believe the tech guys are that savvy but you never know
PS I know this is mean and nasty but this retailer is really bad with its customer service and the service department in general.
at the time they were the only ones selling the Kindle Fire here.
Thanks for any info you may provide.
Not quite permanent, but... You could kill a few partitions, including the bootloader.
So if they refuse to replace it again, you can at least get it working (though you'd have to crack open the case and do the USB pin shorting).
Thanks Dasanko for the reply
quick question:
im guessing that killing the partition would cause it to give an error on boot,would this look/feel like a non user created error?
also if i go down that path any info on how to kill the partitions?
It'll most likely get stuck on a black screen right away if you kill the bootloader.
For the rest, depending on what you wipe, it'll probably show the splash screen (bootloader) and then get stuck either there or on a black screen.
Related
Hey guys,, just got my new Galaxy Nexus, brand new one
Charged it to full as it said in the manual and turned in on, it got into the first 'setup' window and decided to crash, ever since it's boot-looping on the Google logo like in this video and won't do anything else.
I tried factory reset from recovery, I tried to remove battery and try again, I tried with and without SIM, same thing...
now my question is - did i get a faulty phone and i should replace it or it's something I can fix myself? Thank you
As long as there's no icon of a lock under the google logo in the first screen you see while booting, it's a production problem.
all options given to you by people around here about how to unlock it and try to fix it yourself are redicioulus in your case. When you have the phone for less than 7 or 14 days (depending on the country you life in, best way to check is by going over the shop receipt it should be mentioned all the way down. If you bought it online you got a mail) you can walk to the store and demand a new one. If they tell you that they send it to the factory point them on the law and the promises on their receipt... you have the right to give them the package back and pick a new one from the shelf with the same price.
But remember to take everything you bought (cables, earplugs, guide, the cardboard inside the box and the box itself) with you! If you don't they will tell you that you did not bring anything and have no right to pick a new one.
Just get a fresh one it's the best way for you since this problem emerged within the first few hours (and literally on it's first boot). It's most likely a production error. Waiting for a fix at the factory will cost you weeks... and many people report scratches on their screen and broken covers since the phones are not always treated nicely during their travel and fix.
Please post future news on your case here... it's a great help for people with the same problem.
Sent from my Galaxy Nexus using XDA
Same problem but after months
Hi there,
I just had the exact same problem, with a difference : my phone had been working just fine for months. Now, impossible to get it to boot. It cycles the "Google" screen, and that's it. I found that when I hold the volume button down as I start the phone it shows "odin mode", but I do not know what it is for and it does not seem to download anything.
Any ideas?
When it happens right after you purchased the phone, it's better to bring it back to where you bought it from.
On the other hand, try this. Hope this helps.
I was just trying to root my friend's mom's kindle fire and install a new rom and now there is a purple line on the screen. Honestly I didn't check beforehand if there was anything wrong with the screen and his mom is asleep so we don't know if it might've already been there or not.
Couldn't some part of rooting,installing twrp, installing jb, gapps etc have messed up the screen? If so, is there a fix? I tried restoring to stock but the line is still there.
Did I screw up her kindle?! :crying:
I hope you checked with her before modifying her device as its not cool to modify someone's device if they don't wish it to be done. If I was her I would be much more perturbed at that than a purple line, its called respect for other people's property... so I hope you guys had permission.
That being said, I don't see how flashing dev apps or custom Rom to it could possibly cause something like this. Have you tried holding down the power button for 20 seconds to do a hard reboot? You could also try doing a factory reset through the stock os to ensure that it is indeed not a software issue. If all else fails return it to stock as it may still be under warranty to ship it back.
Also you did check to make sure it was a first gen before flashing right?
This post should be in q&a section as well...
Sent from my Amazon Kindle Fire using xda app-developers app
Never heard of such problem. Maybe hardware problems.
Sent from my Amazon Kindle Fire using Tapatalk 2
Let me preface by saying I'm not a 12 year old who stole my friend's mom's kindle.
I have rooted 2 other kindles and never had an issue and I of course was asked to do this.
I did a hard reboot didn't help anything.
I restored the stock os and it is still there.
I did a search and someone posted about this problem once in the Kindle Fire Utility thread but it doesn't look like anyone ever responded to it.
http://forum.xda-developers.com/showthread.php?t=1399889&page=105
My friend says his mom has bad vision so it's possible she never noticed it but I dunno, I honestly didn't even turn look at the screen I just went right to rooting it.
Any more help would be greatly appreciated.
If I can't fix it I will just try and get amazon to replace it. Question: I own a kindle fire as well. If I tell them this one is mine and send it back to them will they replace it or notice it's not the one I bought? I could ask my friend's mom to do it but I'd rather do it to save her the trouble.
Did you just restore the stock os or did you flash stock? Where is the purple line located?
Thepooch said:
Did you just restore the stock os or did you flash stock? Where is the purple line located?
Click to expand...
Click to collapse
I restored to stock following the instructions in the restore stock thread using the file from amazon. The line is about 25% down from the top of the screen.
So no more fff and twrp? Sounds more hardware related than software. Is it still in warranty? Rather than a dead pixel it seems more like a string of bad pixels. Pretty good chance it was already there. Do a factory reset if it is to be returned.
Thepooch said:
So no more fff and twrp? Sounds more hardware related than software. Is it still in warranty? Rather than a dead pixel it seems more like a string of bad pixels. Pretty good chance it was already there. Do a factory reset if it is to be returned.
Click to expand...
Click to collapse
Thanks that makes me feel better. There might have been something wrong with how I rooted it but I don't see why that would mess up the screen.
I am going to find out tomorrow if I can return it.
Do you think that if I've bought a kindle but I try and return a different one that amazon will notice?
Amazon is only selling 2nd gen. devices from now on. I think they would notice. If you send back a 1st gen. device they will try to replace it with a 1st gen. till they run out.
Thepooch said:
Amazon is only selling 2nd gen. devices from now on. I think they would notice. If you send back a 1st gen. device they will try to replace it with a 1st gen. till they run out.
Click to expand...
Click to collapse
Well that would be fine. I bought and have a first gen that works fine. Got it back in march. Although I bought it refurbed from amazon.
If I could return this one and tell them it was mine that would be perfect. Not sure what the return policy on a refurb is though.
I think you still have the issue of a serial number.
So they know the serial number of the kindle they sold me and they will check it? Damn, I was hoping I could get away with it.
I'll check with my friend's mom to see if she can try getting it replaced.
I believe they do and they will 200$ is 200$.
The serial number in the device is listed on your account at Amazon.com, no chance of slipping it past them
Sent from my Amazon Kindle Fire using xda app-developers app
Much searching has left me half confused and half hopeful for something I may have missed. I don't think its immediately obvious, so please, if for the sake of making google answer people more effectively, I want to get a straight answer on this.
I have a dark KFHD 8.9 - I tried running BreakDroid on it after it had been rooted and loaded with various google apps ( that probably doesn't matter, but its here for the sake of completeness ).
My computer sees nothing now, and attempts to fastboot at the kindle result in an endless waiting for device messages.
The Question:
Assuming my KFHD 8.9 is so badly bricked that fastboot will not work - is there any other known method to get it back to working?
I am willing to take it apart, solder things to it, surrond it with pentagrams of chicken blood, etc... but I need to know if I am just wasting my time with a paperweight.
Thanks
Assuming the device doesn't show any outward signs of life (no display, etc), there isn't anything that can be done at the moment.
Contact Amazon and say it is dead and not responding!
Contact Amazon and say it is dead and not responding! They should be able to help you.
souplogic said:
Much searching has left me half confused and half hopeful for something I may have missed. I don't think its immediately obvious, so please, if for the sake of making google answer people more effectively, I want to get a straight answer on this.
I have a dark KFHD 8.9 - I tried running BreakDroid on it after it had been rooted and loaded with various google apps ( that probably doesn't matter, but its here for the sake of completeness ).
My computer sees nothing now, and attempts to fastboot at the kindle result in an endless waiting for device messages.
The Question:
Assuming my KFHD 8.9 is so badly bricked that fastboot will not work - is there any other known method to get it back to working?
I am willing to take it apart, solder things to it, surrond it with pentagrams of chicken blood, etc... but I need to know if I am just wasting my time with a paperweight.
Thanks
Click to expand...
Click to collapse
amit.talukdar said:
Contact Amazon and say it is dead and not responding! They should be able to help you.
Click to expand...
Click to collapse
I am thinking about doing this, but I am not good about leaving the fact that I have rooted, flashed, and actually completely disassembled this device. Might have my wife call, and tell them all she "knows", just saying her husband is an idiot, which in this case is true.
souplogic said:
I am thinking about doing this, but I am not good about leaving the fact that I have rooted, flashed, and actually completely disassembled this device. Might have my wife call, and tell them all she "knows", just saying her husband is an idiot, which in this case is true.
Click to expand...
Click to collapse
Souplogic - I bricked my 8.9 by installing the wrong bootloader. I tried to fix it - took it apart, built a 'factory cable', and sent it to an expert. Bottom line was that the device was bricked, Amazon replaced it no questions asked, and it appears that the returned device went directly to a contractor that processes/refurbs them.
We're a five Kindle family - Amazon has replaced early devices (gen 1 Fires) due to USB port problems, and my HD 8.9. Sorry to hear that you 'get' to have 'this much fun' with your Kindle - but if you choose to send it back to Amazon they'll take care of you.
Hello,
Recently my Nexus 7 (2013) battery ran out because I forgot to charge it. Since then, it won't boot back into Android when it's turned on - all I get is the black screen with "Google" written on it. I have searched all over the internet for the past few days, but I'm unable to find a solution. I'm hoping that someone here can help me, because the tablet's warranty has expired and I'm completely out of ideas. Here are the things I've tried or noticed:
I can't boot into Android. The tablet gets stuck on the black screen with "Google" written on it.
I can access the bootloader and interact with the tablet via fastboot.
The bootloader is locked. Trying to unlock it via fastboot oem unlock displays the "Unlock bootloader?" screen on the tablet. After I select "Yes", the command line output on the computer shows the following output, but doesn't get any further:
Code:
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
Trying to boot into recovery mode from the bootloader results in the tablet being stuck on that black screen with "Google" written on it.
I have removed the back cover from the tablet and reconnected every exposed connector. I couldn't take the battery out because I don't have the appropriate screwdriver. Doing this changed nothing.
Any help would be sincerely appreciated. At this point I'm worried that it is a hardware issue, but I'd like to exhaust all options before declaring it as such, as it would essentially mean the tablet is going in the garbage bin.
How long did you let it sit at "erasing userdata"?
I don't recall specifically on my N7 but I know when I unlocked the bootloader on my 2013 Moto X it seemed like an eternity, which was mostly because there is no progress indicator, it just said "erasing userdata" and sat there for a while. Probably like 5-10 minutes.
fury683 said:
How long did you let it sit at "erasing userdata"?
Click to expand...
Click to collapse
It'll be around 2 hours now.
Wengard said:
It'll be around 2 hours now.
Click to expand...
Click to collapse
Well that is surely too long. Not sure what else to suggest. Someone else with more experience might able to help.. It sounds like your partitions may have been messed up somehow, which I have seen others post about recently with the updates. I'm not sure what causes this or if there are any fixes, but I know there are threads about people being stuck on the Google screen and having issues after the update to 5.0/.1/.2.
fury683 said:
Well that is surely too long. Not sure what else to suggest. Someone else with more experience might able to help.. It sounds like your partitions may have been messed up somehow, which I have seen others post about recently with the updates. I'm not sure what causes this or if there are any fixes, but I know there are threads about people being stuck on the Google screen and having issues after the update to 5.0/.1/.2.
Click to expand...
Click to collapse
Hi,
i had exactly the same problem. I tried everything to fix it and no luck. I had to resort in sending it to Asus for repair. Unfortunately my warranty has expired. I just got a quote from them saying the motherboard has gone and it will cost me £250 to repair!!!!! I almost fell off my chair. A brand new 32gb tablet will cost be around £180. This is surely a joke? I will be giving them a call tomorrow to complain!
I hope yours is still under warranty because it is most likely your motherboard that has gone. I've read a few others having the same issue and its been the motherboard.
Mo
mo123456789 said:
Hi,
i had exactly the same problem. I tried everything to fix it and no luck. I had to resort in sending it to Asus for repair. Unfortunately my warranty has expired. I just got a quote from them saying the motherboard has gone and it will cost me £250 to repair!!!!! I almost fell off my chair. A brand new 32gb tablet will cost be around £180. This is surely a joke? I will be giving them a call tomorrow to complain!
I hope yours is still under warranty because it is most likely your motherboard that has gone. I've read a few others having the same issue and its been the motherboard.
Mo
Click to expand...
Click to collapse
Thank you for your response.
I'm sorry to hear about what happened to you. I've been reading around and guessed it's probably a hardware problem based on other people's similar experiences. Unfortunately my tablet is out of warranty as well, and I'm definitely not going to spend more on the repairs than I would on a brand new tablet. I regret purchasing the tablet in the first place, I really expected it to last longer than a year.
If you can, please let me know what ASUS says about this, if you intend to call them. They don't have a subsidiary in my country, but if you get lucky, I might press my chances as well and perhaps I can get this repaired for a reasonable price.
Mine has lasted 5 years more but my Nexus 7 has ended its days the same way as yours. Stuck at google when switched on, and stuck at bootloader when triying to flash it.
Time to go, it seems.
Hi! So, a couple of months ago I bought the HTC 10, and it's safe to say that I love the phone, the only thing I wasn't a big fan of was Sense OS, so I decided to fire up Lineage OS into the phone and lo and behold, the perfect phone was born. It was beautiful, and the customization I could do was on another level, not to mention performance. Until I decided to tinker a bit with the phone's look and then the problems started.
I was prompted to update my OS which I gladly do every week, but I hadn't customized the software that much before, so when I flashed the update, I was stuck in bootloop. I flashed the zips that supposedly uninstalled everything I did to the phone and was still stuck in bootloop, did a wipe, still bootloop, it wasn't until I did a complete factory reset when I got my phone back. But then, I saw something.
After booting up, I saw a tiny bright spot under the lower left of the screen, I barely noticed it, but it was there. I decided to go back to stock, and it was still there. Looked into the problem and apparently it's a hardware issue. Called HTC and they told me that they could come for the phone on Tuesday, but the thing is, my phone's status is "modified" I try to lock the phone again and it changed from "unlocked" to "relocked", I'm afraid that these guys might have something to say about that and they'll give me back my phone with no repair at all...
So, what do you guys think? Do HTC care if the phone was unlocked and rooted once before, or that the software status is modified? How can I change those things? Is it really worth it to send my phone for repair? (the spot is really small and not that noticeable, but I'm scared it might get bigger over time)
Sorry for the lengthy post, hopefully you understand. Thanks in advance!
Since this is apparently a defective hardware issue, they shouldn't care. My first HTC 10 was broken (vibration didn't work), and it took me 6 weeks of going back and forth with them to get it replaced and it was completely unmodified. I would say you shouldn't have any issues getting a replacement, because only the software was modified, and you returned that to complete stock, then the issue with the screen spot occurred.
I agree, just returning it to stock should be enough. From what I remember they don't specifically say that unlocking the bootloader completely voids the warranty even for hardwaee issues.
I say send it in and let them replace the screen.
taker714 said:
Hi! So, a couple of months ago I bought the HTC 10, and it's safe to say that I love the phone, the only thing I wasn't a big fan of was Sense OS, so I decided to fire up Lineage OS into the phone and lo and behold, the perfect phone was born. It was beautiful, and the customization I could do was on another level, not to mention performance. Until I decided to tinker a bit with the phone's look and then the problems started.
I was prompted to update my OS which I gladly do every week, but I hadn't customized the software that much before, so when I flashed the update, I was stuck in bootloop. I flashed the zips that supposedly uninstalled everything I did to the phone and was still stuck in bootloop, did a wipe, still bootloop, it wasn't until I did a complete factory reset when I got my phone back. But then, I saw something.
After booting up, I saw a tiny bright spot under the lower left of the screen, I barely noticed it, but it was there. I decided to go back to stock, and it was still there. Looked into the problem and apparently it's a hardware issue. Called HTC and they told me that they could come for the phone on Tuesday, but the thing is, my phone's status is "modified" I try to lock the phone again and it changed from "unlocked" to "relocked", I'm afraid that these guys might have something to say about that and they'll give me back my phone with no repair at all...
So, what do you guys think? Do HTC care if the phone was unlocked and rooted once before, or that the software status is modified? How can I change those things? Is it really worth it to send my phone for repair? (the spot is really small and not that noticeable, but I'm scared it might get bigger over time)
Sorry for the lengthy post, hopefully you understand. Thanks in advance!
Click to expand...
Click to collapse
If your that worried about it, doing a ruu to get completely back to stock should fix the modified message
First of all, I want to thank everyone who answered this post, really appreciate your opinions.
So, quick update, after I sent my phone, literally got a call the next day telling me that the software was modified and it breached HTC's guarantee. So unfortunately it's a thing... I'm probably going to ignore the issue with the screen since for now it's not that big of a deal, but I have a feeling that I'll have to buy a screen replacement and try and replace it myself down the line. Kinda bummed, always been a Nexus guy but loved and admired HTC's phone designs and quality, so when my Nexus 5 died earlier this year (After three years of abuse, Android bless his soul), I thought that it was time to get "HTC's comeback phone", since the Pixel was so expensive and hard to get. Not saying I regret buying the 10, still is a joy to hold and use, and in my opinion, a lot more better looking and manageable than the HTC U11, but still, had my expectations just a tiny bit higher... I guess that's what you get when you try out new ROMs haha.
Thanks again to everyone who responded this post, hopefully this helped someone.
So even you return your htc 10 back to stock and relock bootloader phone is not under warranty?Wtf?
johnnyman25 said:
So even you return your htc 10 back to stock and relock bootloader phone is not under warranty?Wtf?
Click to expand...
Click to collapse
Ikr? The thing is that even if you flash with RUU and lock the phone, the system doesn't change to a "locked" status again, but it changes to a "relocked" status... And while it's that way, the system will appear modified in the bootloader. And any modification to software goes against HTC's guarantee because they basically blame your hardware issue on you tinkering with the software. Pretty funny if you ask me, but oh well xd
taker714 said:
Ikr? The thing is that even if you flash with RUU and lock the phone, the system doesn't change to a "locked" status again, but it changes to a "relocked" status... And while it's that way, the system will appear modified in the bootloader. And any modification to software goes against HTC's guarantee because they basically blame your hardware issue on you tinkering with the software. Pretty funny if you ask me, but oh well xd
Click to expand...
Click to collapse
But I read the htc accepts phones with stock software and relocked bootloader. It's a lie?
HTC 10 Matte Black Power
I mean, it probably depends who takes the phone and how they check for faults... Maybe I was flat out unlucky