I just want to start off by saying that I don't know too much about rooting or much of Android/Amazon OS in general. I have had my (Apollo) Fire HDX 8.9" since March 2, 2013. I have side-loaded apps and I am just a typical user. I know how to modify applications and such, so I know a bit but probably not as much as I should. I'm up-to-date with a lot of tech, but not all the rooting stuff. Anyway... Last night (November 25, 2015) I decided that I wanted to root. I started by finding some important info, specifically from this forum. (http://forum.xda-developers.com/kindle-fire-hdx/general/rollback-13-3-2-8-rollback-ota-captured-t3046204) So being as lazy as I am I did as much as I could without my computer and got 14.3.2.8 up and running over night. When I woke up I started the setup and enabled the wifi just quick enough to get ES File Manager. I got it installed successfully with no problems and turned off the wifi. After that I didn't really understand the OTA thing and TBH I still don't. I am assuming that is what updates my Kindle automatically. Anyway I just ignored that and moved on to my next step, installing 14.4.5.2. (Which I did on my computer.) After realizing my internet was really slow I decided to go reset the modem. Doing this messed up the modem and it kept going into "Limited mode". I had an idea that it could just be my Ethernet cable so to check that I turned my Kindle's wifi to see if I could connect through wireless. It still didn't work so I just decided to get ready for the day. This was around 11 AM (MST)(Thanksgiving 2015). When I am all done getting ready I go check my computer to see if my wifi is working, and it was finally working. So I go grab my Kindle, but now it wont turn on at all. I am assuming that this is a hard brick. I am still on 14.3.2.8 (I'm guessing that there is still stuff on my Kindle) and have no root and never did turn on developer options. When I connect it to my computer it takes a second and then say that it is unrecognizable. I am aware of "Restore2Stock", but I want to know if there are any other options. I don't want to spend $20 on a service that I don't necessarily trust. Anyone able to help???
My original post was a reply on a different thread. (http://forum.xda-developers.com/kindle-fire-hdx/help/help-thread-question-noob-friendly-t3206752/page11#post64025036)
DiaperBandit said:
I just want to start off by saying that I don't know too much about rooting or much of Android/Amazon OS in general. I have had my (Apollo) Fire HDX 8.9" since March 2, 2013. I have side-loaded apps and I am just a typical user. I know how to modify applications and such, so I know a bit but probably not as much as I should. I'm up-to-date with a lot of tech, but not all the rooting stuff. Anyway... Last night (November 25, 2015) I decided that I wanted to root. I started by finding some important info, specifically from this forum. (http://forum.xda-developers.com/kin...lback-13-3-2-8-rollback-ota-captured-t3046204) So being as lazy as I am I did as much as I could without my computer and got 14.3.2.8 up and running over night. When I woke up I started the setup and enabled the wifi just quick enough to get ES File Manager. I got it installed successfully with no problems and turned off the wifi. After that I didn't really understand the OTA thing and TBH I still don't. I am assuming that is what updates my Kindle automatically. Anyway I just ignored that and moved on to my next step, installing 14.4.5.2. (Which I did on my computer.) After realizing my internet was really slow I decided to go reset the modem. Doing this messed up the modem and it kept going into "Limited mode". I had an idea that it could just be my Ethernet cable so to check that I turned my Kindle's wifi to see if I could connect through wireless. It still didn't work so I just decided to get ready for the day. This was around 11 AM (MST)(Thanksgiving 2015). When I am all done getting ready I go check my computer to see if my wifi is working, and it was finally working. So I go grab my Kindle, but now it wont turn on at all. I am assuming that this is a hard brick. I am still on 14.3.2.8 (I'm guessing that there is still stuff on my Kindle) and have no root and never did turn on developer options. When I connect it to my computer it takes a second and then say that it is unrecognizable. I am aware of "Restore2Stock", but I want to know if there are any other options. I don't want to spend $20 on a service that I don't necessarily trust. Anyone able to help???
My original post was a reply on a different thread. (http://forum.xda-developers.com/kin...on-noob-friendly-t3206752/page11#post64025036)
Click to expand...
Click to collapse
As you probably realize your device is toast. Leaving WiFi enabled resulted in receiving an incompatible OTA (over the air) update from Amazon. There is no recovery.
Davey126 said:
As you probably realize your device is toast. Leaving WiFi enabled resulted in receiving an incompatible OTA (over the air) update from Amazon. There is no recovery.
Click to expand...
Click to collapse
So is there anything that I can do with my $300 tablet now called a brick? Can I call support and see of they can do something? I'm sad and I realize that it is my fault but I'm pretty over the top that my tablet now has a worth of a dime. I would expect there to be some sort of company that would buy my "brick". Like a junkyard for disfunctional devices. My guess it that there is not a single thing in the entire world that can fix this.
DiaperBandit said:
So is there anything that I can do with my $300 tablet now called a brick? Can I call support and see of they can do something? I'm sad and I realize that it is my fault but I'm pretty over the top that my tablet now has a worth of a dime. I would expect there to be some sort of company that would buy my "brick". Like a junkyard for disfunctional devices. My guess it that there is not a single thing in the entire world that can fix this.
Click to expand...
Click to collapse
Check eBay or similar auction sites to get an idea what your device is worth (very little) in its current state. To my knowledge there is no company that refurbishes bricked Kindles (at least HDX models) and no one on XDA has figured out how to resurrect crippled devices. Sorry for your loss.
Davey126 said:
Check eBay or similar auction sites to get an idea what your device is worth (very little) in its current state. To my knowledge there is no company that refurbishes bricked Kindles (at least HDX models) and no one on XDA has figured out how to resurrect crippled devices. Sorry for your loss.
Click to expand...
Click to collapse
Thanks for the help. I'll see how much I can get.
I'm in a position equal to his own , I have nuna 3rd kindle fire and think that just left on the wifi was going to be the tablet is useless crap ..
Friend anything that might serve to regain our fire I notice , just hope you do the same , never give that friend to relive our Kindle
I just replaced the motherboard in mine. The 16gb board I bought was $36
I just ordered a daughter board also. I must have damaged it also when I was messing with it.
I took the daughterboard out of my wife's to test just to make sure.
Daughterboard was $14
Bought both from ifixit but they are out of motherboards.
Google them and you should be able to find one.
Be patient removing the display from the back frame.
Just posted a thread with a link for motherboards.
Sent from my SM-N920T using Tapatalk
donharden2002 said:
I just replaced the motherboard in mine. The 16gb board I bought was $36
I just ordered a daughter board also. I must have damaged it also when I was messing with it.
I took the daughterboard out of my wife's to test just to make sure.
Daughterboard was $14
Bought both from ifixit but they are out of motherboards.
Google them and you should be able to find one.
Be patient removing the display from the back frame.
Just posted a thread with a link for motherboards.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Good stuff! Offers some hope for those with bricked devices (especially pricey Apollo/Saturns) and moderate skills in electronics disassembly/repair. At present there are few viable alternatives to the outstanding display and unique form factor of the HDX line. Thanks for sharing.
Related
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
My Apollo is stuck trying to upgrade itself.
Background
Previously I did have Safestrap 3.75 and was running Nexus 1.0.1 is in a slot. I had 14.3.2.8 sitting in the Stock Rom slot.
Decided to upgrade to Nexus 4.0.5 so I went back to the stock slot and uninstalled safestrap 3.75.
Saw in the Safestrap 4.0.1 thread that I needed to be on 14.4.5.2 for it to work, so I manually forced upgrade to that version.
Then while I was attempting to get root back (quickly allowing wifi access for it to work) the damn machine downloaded a newer version of stock and tried to install it.
Well I thought "fine I will let it upgrade and then roll back to 14.3.2.8 and start again"
Wrong!. The HDX rebooted and then when it restarted it is now stuck at "Fire is upgrading..." and "Starting applications..." (shortly after the second orange Kindle Fire boot logo)
Now I cant access by adb because the unit is "unauthorized".
Any hope of getting it back online? Its been stuck at boot for a day now. Any hope of a way to bypass the upgrade during the boot phase?
Thanks in advance.
maccaberry said:
My Apollo is stuck trying to upgrade itself.
Background
Previously I did have Safestrap 3.75 and was running Nexus 1.0.1 is in a slot. I had 14.3.2.8 sitting in the Stock Rom slot.
Decided to upgrade to Nexus 4.0.5 so I went back to the stock slot and uninstalled safestrap 3.75.
Saw in the Safestrap 4.0.1 thread that I needed to be on 14.4.5.2 for it to work, so I manually forced upgrade to that version.
Then while I was attempting to get root back (quickly allowing wifi access for it to work) the damn machine downloaded a newer version of stock and tried to install it.
Well I thought "fine I will let it upgrade and then roll back to 14.3.2.8 and start again"
Wrong!. The HDX rebooted and then when it restarted it is now stuck at "Fire is upgrading..." and "Starting applications..." (shortly after the second orange Kindle Fire boot logo)
Now I cant access by adb because the unit is "unauthorized".
Any hope of getting it back online? Its been stuck at boot for a day now. Any hope of a way to bypass the upgrade during the boot phase?
Thanks in advance.
Click to expand...
Click to collapse
Unfortunately, not much you can do without adb access. As a long shot try a factory reset from the native Kindle Fire recovery menu. Often this makes things worse but you have little to loose given the symptoms and age of device (likely long out of warranty).
Davey126 said:
Unfortunately, not much you can do without adb access. As a long shot try a factory reset from the native Kindle Fire recovery menu. Often this makes things worse but you have little to loose given the symptoms and age of device (likely long out of warranty).
Click to expand...
Click to collapse
On the phone with Amazon right now. They also suggested Factory Reset. I know it cant get worse because I already have no root. So I gave it a go. Just bootloops now - still trying to upgrade itself.
They want me to replace it with a refurb at my cost.
Thanks for nothing Amazon. I was on stock when this happened and it was your update that screwed me! LOL Probably get a Samsung or Nexus to replace. It was fun while it lasted though.
maccaberry said:
On the phone with Amazon right now. They also suggested Factory Reset. I know it cant get worse because I already have no root. So I gave it a go. Just bootloops now - still trying to upgrade itself.
They want me to replace it with a refurb at my cost.
Thanks for nothing Amazon. I was on stock when this happened and it was your update that screwed me! LOL Probably get a Samsung or Nexus to replace. It was fun while it lasted though.
Click to expand...
Click to collapse
What you experienced is not uncommon based comments posted in XDA forums and Amazon customer reviews. OTAs are never 100% reliable but HDX devices seem to be more vulnerable to soft bricks with limited/no recovery options. Obviously the vast majority of users upgrade without incident but even a low single digit failure rate during the expected lifespan of the device raises a red flag. Amazon's replacement policy is also consistent: once out of warranty they will offer a refurb at current prices occasionally muted with a modest discount (eg: $20 USD off). BFD.
HDX is a great hunk of hardware if you can tame it. Nexus and Samsung tablets are a notch below imo but are much easier to mod. Sorry for your loss; good luck with whatever direction you opt to go.
Davey126 said:
What you experienced is not uncommon based comments posted in XDA forums and Amazon customer reviews. OTAs are never 100% reliable but HDX devices seem to be more vulnerable to soft bricks with limited/no recovery options. Obviously the vast majority of users upgrade without incident but even a low single digit failure rate during the expected lifespan of the device raises a red flag. Amazon's replacement policy is also consistent: once out of warranty they will offer a refurb at current prices occasionally muted with a modest discount (eg: $20 USD off). BFD.
HDX is a great hunk of hardware if you can tame it. Nexus and Samsung tablets are a notch below imo but are much easier to mod. Sorry for your loss; good luck with whatever direction you opt to go.
Click to expand...
Click to collapse
Hi Davey, thanks for the thoughts. Its the truth that after 2 years this specs on the 3rd gen HDX are still right up there. The image quality and sound quality are outstanding compared to just about anything available - even today. But unfortunately if you like to tinker then its just too much work. Samsung and other manufacturers are heading down the same path with locked bootloaders but even so modding seems a dream compared to the HDX.
Probably going to get a tablet that utilizes a stylus since I really want to use it as a digital notepad for work and a movie player for leisure. My regular kindle e-reader is still the best option for reading books due to very light weight. As good as the HDX is (and any tablet for that matter), tablets are still a bit to heavy for serious reading in bed and the back light disturbs your sleep patterns.
If anyone else reading this has a viable option to get the unit to reboot without upgrading I am all ears, because as I have said I would love to get a bit more life out of this fantastic HDX hardware.
maccaberry said:
If anyone else reading this has a viable option to get the unit to reboot without upgrading I am all ears, because as I have said I would love to get a bit more life out of this fantastic HDX hardware.
Click to expand...
Click to collapse
Take a peek at this thread for ideas. Long shot at best. The small glimmer of hope is you made it past the grey logo so dealing with a soft vs hard brick. That said, if USB debug wasn't enabled on 4.5.2 you will be hard pressed to secure meaningful access. Sorry this happened. Might look at grabbing a HDX from an auction site. You are wiser now and would likely make it through the rollback/upgrade procedure intact.
stackoverflow.com/questions/18011685/cant-connect-nexus-4-to-adb-unauthorized
maccaberry said:
Hi Davey, thanks for the thoughts. Its the truth that after 2 years this specs on the 3rd gen HDX are still right up there. The image quality and sound quality are outstanding compared to just about anything available - even today. But unfortunately if you like to tinker then its just too much work. Samsung and other manufacturers are heading down the same path with locked bootloaders but even so modding seems a dream compared to the HDX.
Probably going to get a tablet that utilizes a stylus since I really want to use it as a digital notepad for work and a movie player for leisure. My regular kindle e-reader is still the best option for reading books due to very light weight. As good as the HDX is (and any tablet for that matter), tablets are still a bit to heavy for serious reading in bed and the back light disturbs your sleep patterns.
If anyone else reading this has a viable option to get the unit to reboot without upgrading I am all ears, because as I have said I would love to get a bit more life out of this fantastic HDX hardware.
Click to expand...
Click to collapse
Hi did you ever manage to find a way to bring it back, my HDX has just done the same thing today.
Another Fire HDX 3rd gen. Stock FireOS have same issue today. Still looking for answer...
aedahh said:
Another Fire HDX 3rd gen. Stock FireOS have same issue today. Still looking for answer...
Click to expand...
Click to collapse
Unfortunately, no solution if you can't connect via ADB. Tough loss ...
Last year I got annoyed that the Wishlist icon was repopulating itself to my Favorites every time I deleted it, so I got a wild hair to root my Kindle and take care of that junk for good. I did this before reading the numerous warnings about how this was an awful device to root on a whim. I proceeded to delete a bunch of system files related to Amazon ads and tracking. After a reboot, I found myself stuck at a flashing white Favorites screen. I could get to the Settings menus, but most choices didn't work and just took me back to Settings without changing anything. I couldn't connect to a wifi network, but I could see the networks, click on Connect to Network, and then it just took me back to Settings. I couldn't change any of the Developer settings. I did hard resets from that mode and from the boot up recovery menu. Nothing could get me out of this state.
Anyway, I posted thread about this when it happened, here: http://forum.xda-developers.com/kin...iles-flashing-favorites-screen-t3116682/page1
In the end, I didn't have the heart to scam Amazon, so I just bought a used HDX 7 and put the bricked one in the drawer in hopes of a future fix. Last night, my replacement Kindle's screen was crushed by some mysterious force, possibly a kitty cat or an adjustable bed. Though it's tempting to think about trying to swap the screens, I don't want to crack the screen and wind up with two broken displays (plus a bricked Kindle). So I thought I'd check back and see if there were any developments on the fixing-dumb-newbie-mistakes front for the bricked one.
The device does not show up in Windows XP, 7, or 8.1. The Kindle itself recognizes it's charging. As I mentioned in the old thread, I tried a Fastboot cable, but that apparently doesn't work on this model. So any hope? It's so frustrating because it seems like if I could just get the wifi to work I could download the latest OS update and it would fix this.
I understand if there still are no fixes for this. It was a dumb move to tinker with this in the first place. I was just hopeful something might have changed, since last I asked about it.
No adb access? That sucks, as it should be pretty easy to fix if you could adb push. Were it mine, I'd go ahead and try to replace the screen on the functioning tablet. Not what you want to hear, but I think that's the only way to get working again. Best of luck.
Valence1981 said:
Last year I got annoyed that the Wishlist icon was repopulating itself to my Favorites every time I deleted it, so I got a wild hair to root my Kindle and take care of that junk for good. I did this before reading the numerous warnings about how this was an awful device to root on a whim. I proceeded to delete a bunch of system files related to Amazon ads and tracking. After a reboot, I found myself stuck at a flashing white Favorites screen. I could get to the Settings menus, but most choices didn't work and just took me back to Settings without changing anything. I couldn't connect to a wifi network, but I could see the networks, click on Connect to Network, and then it just took me back to Settings. I couldn't change any of the Developer settings. I did hard resets from that mode and from the boot up recovery menu. Nothing could get me out of this state.
Anyway, I posted thread about this when it happened, here: http://forum.xda-developers.com/kin...iles-flashing-favorites-screen-t3116682/page1
In the end, I didn't have the heart to scam Amazon, so I just bought a used HDX 7 and put the bricked one in the drawer in hopes of a future fix. Last night, my replacement Kindle's screen was crushed by some mysterious force, possibly a kitty cat or an adjustable bed. Though it's tempting to think about trying to swap the screens, I don't want to crack the screen and wind up with two broken displays (plus a bricked Kindle). So I thought I'd check back and see if there were any developments on the fixing-dumb-newbie-mistakes front for the bricked one.
The device does not show up in Windows XP, 7, or 8.1. The Kindle itself recognizes it's charging. As I mentioned in the old thread, I tried a Fastboot cable, but that apparently doesn't work on this model. So any hope? It's so frustrating because it seems like if I could just get the wifi to work I could download the latest OS update and it would fix this.
I understand if there still are no fixes for this. It was a dumb move to tinker with this in the first place. I was just hopeful something might have changed, since last I asked about it.
Click to expand...
Click to collapse
You're done if device is running 4.5.2 w/no adb access. There are a few last resort unbrick methods/tools but they are geared toward older versions of FireOS (v3.2.6 and below). Replacing the screen on a 7" HDX is difficult; copious use of glue makes for a tough job. Might check auction sites; prices are pretty low for 16GB models. Also consider the latest 7" tab from Amazon (2015 Fire). Specs are awful vs HDX but it really isn't that bad, especially for video and with apps designed for lower resolution screens (many are). Fully rootable with option for custom roms. FireOS v5 is a nice step up from v4, faster and more 'android like' (although still heavily skinned).
I cannot even find any information on this device let alone a root method. Apparently from my searches methods for the zenphone may work but im not sure if I want to risk bricking this device, but verizon would just replace it anyway. I guess its fairly new? It came with MM and already has an OTA which i keep putting off while I am going to try out various methods to get this one rooted and unleashed since one verizon store essentially scammed me over my new s7 edge so another store refunded everything for me. Now I got this 4g tablet I want to fasten in my car and it would be nice to root or unlock and put some custom vehicle firmware on it or something like that.
I have the same issue with my new Zenpad 3 8.0 . KingRoot and some other rooting apps didn't work for me.
At least someone finally replies.... I am still stuck trying to root this thing. I've tried nearly everything to no success. Even the temporary cwm wouldn't work for me
Same here buddy. Why did ASUS remove such features as App to SD and multi user support?
Anyone found anything? I have the tablet too...
Well damn this sux, Verizon stuck me with another unrootable device, at least I can say I got my pixel in time to unlock the bootloader and route it but not much activity for it since decided to lock them down. I thought I learned with my G4 that's why I got the pixel got home just to find out they're going to be locked down too lol Oh God how I loath Verizon
dadrumgod said:
Well damn this sux, Verizon stuck me with another unrootable device, at least I can say I got my pixel in time to unlock the bootloader and route it but not much activity for it since decided to lock them down. I thought I learned with my G4 that's why I got the pixel got home just to find out they're going to be locked down too lol Oh God how I loath Verizon
Click to expand...
Click to collapse
I hear ya. I have this tablet too: Asus Verizon Zenpad Z8 ZT581KL with V.3.4.23. Despite my best efforts, the damn system update notification keeps coming up telling me to update to Android 7--which I DO NOT want to do since doing that very well could kill any small hope I have on rooting the device. Since this is a Verizon branded tablet, they made an agreement with Asus to lock it down like Gitmo, so any official bootloader unlocker will not work with Verizon. Maybe one day when Verizon get's their head out of their ass and understands that people have the right to screw with their phones, they will allow unlocking options--though I doubt it.
This would be a great little tablet, if Verizon gave us more control over it--Jesus Christ, you're still getting $$ from me on your non-unlimited data. Bunch of ****-tards---I used to work for them back in the day at one of their corporate locations in Folsom, CA. Sadly, I think it's that prison mentality (Folsom Prison) that must have been carried in the air a few miles to the Verizon offices there. That was WDTS (Wireless Data Tech Support)....I was there right when EVDO just came out/expanding (Before Iphones...closest thing would have been a BES-Enabled Blackberry, or a fancy PDA)--oh those were the days...
There are rooting options available if you understand Chinese--but even its for older software versions 3.3.x, etc, and from what I can understand, the flash might actually take (hackers take note: if the flash can take..maybe we can piece together a flash with proper rooted versions)...but since this is a Sim/LTE tablet by doing that it will screw up the radio (Cellular) and recovery partitions. But maybe something round-about could be done that does that, then reflashes modified signed firmware to root it--I dunno.
My google-fu is pretty good and I came across some cached, or snippet that said SRSroot might root 6.0.1 on the ZT581KL, but not sure now legit it is.
Unless more people get this tablet/devs play with it, I don't think we will get root/bootloader/recovery anytime soon. I wish I lived in a country that allowed multiple wifes, because I would do a bounty for root on this devices and give away one of my wives for payment.
I used the tablet mostly for navigation, but I want root/twrp for backup purposes, if I need to wipe the device crossing the border since police now wanting to look at peoples phones/tablets. I love using Waze since I'll be driving down the road with a FAT blunt smoking away, so it's good to know if cops are around.
Zenpad z8 running on Fi
I also have this pad. I bought it from Verizon because it's USB-C and I loathe micro USB and even more so because the helpful sales guy at Verizon let me try my Google Fi data only sim...and sure enough it works awesome after setting h2g2 as the apn. Would love to root it though I hate how I can only have one user account on this for now.
Kind of off-topic, but I can't find any clear answer to my question about the Z8 and Z8s. I'm considering buying one, but I do not want a data-plan. Do these tablets work without a SIM in them, or will I be stuck at a home screen that says "Insert SIM..."?
_HighVoltage_ said:
Kind of off-topic, but I can't find any clear answer to my question about the Z8 and Z8s. I'm considering buying one, but I do not want a data-plan. Do these tablets work without a SIM in them, or will I be stuck at a home screen that says "Insert SIM..."?
Click to expand...
Click to collapse
Of course you can use it without a SIM.
I just ordered this tablet. I'm sad I can't root it, but I mainly use root for adblocking. I will have to use DNS66 or BlockThis instead.
This method doesn't work?
https://neopodapsi.com/how-to-root-asus-zenpad-z8/
replica9000 said:
This method doesn't work?
Nope, just a scam to fill out never ending surveys
Click to expand...
Click to collapse
Zenpad P008 Verizon root - no luck
I just tried One Click Root and that didn't work either. Upon chatting with support they were stymied by the lack of an 'OEM Override' debug mode setting.
Can anybody help, I'm new at this stuff. Plus I'm teaching myself. I've rooted some devices. Did some firmware jobs, kinda' familiar with Odin. But I've tried everything from KingRoot PC to adb tryna' root this thing (P008). Between this thing and that Knox MDM shizzle. Man!, Anybody got anything on these topics......
Anyone try Magisk?? I also want to root this thing. Cannot get a usb gaming controller to recognize either.