My kindle kinda took a digger onto the hardwood floor lol. How easy is it to replace the digitizer?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
T10NAZ said:
My kindle kinda took a digger onto the hardwood floor lol. How easy is it to replace the digitizer?
Click to expand...
Click to collapse
It's pretty easy but you have to make sure you get the right part. As @asf58967 can attest, the one difference between the hardware configurations of the KF1 and KF2 is the little connector on the digitizer.
soupmagnet said:
It's pretty easy but you have to make sure you get the right part. As @asf58967 can attest, the one difference between the hardware configurations of the KF1 and KF2 is the little connector on the digitizer.
Click to expand...
Click to collapse
Not true
I put a 1st GEN digitizer onto a 2nd GEN device.
Same connector and same screen
There is a nice guide on iFixit
Sent from my Amazon Kindle Fire using xda app-developers app
Did it work?
Markyzz said:
Not true
I put a 1st GEN digitizer onto a 2nd GEN device.
Same connector and same screen
Click to expand...
Click to collapse
Did you run into any issues with this? Think I may have accidentally put a kf1 digitizer on my kf2. It's working in recovery but stuck in boot loop on all roms I try...also he ribbon cable was too short to seat right...
wkustu said:
Did you run into any issues with this? Think I may have accidentally put a kf1 digitizer on my kf2. It's working in recovery but stuck in boot loop on all roms I try...also he ribbon cable was too short to seat right...
Click to expand...
Click to collapse
I think you just have to factory reset in TWRP.
soupmagnet said:
I think you just have to factory reset in TWRP.
Click to expand...
Click to collapse
I tried all sorts of wipes, some roms that had previously worked, even restoring my old original KF backup. No luck.
Bump this
wkustu said:
I tried all sorts of wipes, some roms that had previously worked, even restoring my old original KF backup. No luck.
Click to expand...
Click to collapse
I am also having this error
Related
Hi,
I recently acquired a Kindle Fire that was previously used as a Demo unit in a store, I'd like to get it out of Demo mode but having tried since Sunday (and following several threads on here with similar problems) with no success I thought I'd see if I can get any help.
This is my first Kindle, so I'm new to that, but I've owned several Android devices in the past, so I'd consider myself fairly familiar with ADB, Fastboot, etc.
Since I can't get into the settings on the Demo unit I haven't been able to enable USB Debugging, to cut a long story short after playing around all day Sunday trying to get KFU to communicate with the device I gave up and ordered a Factory USB Cable to get it into Fastboot mode.
That arrived This morning and the Kindle is now in Fastboot mode, but I'm not sure what to do next, the PC (Windows 8 64bit, but I've also tried on Vista 32bit) sees the device as: Otter2-Prod-04 with a yellow exclamation mark icon and KFU still doesn't seem to be able to communicate with the device.
I'm running out of ideas, any help would be appreciated.
Thanks,
Jason
Never mind, I got KFU to recognise the device finally but I think it's bricked it, it's just black now with no light on the power button or anything.
I don't suppose there's any way to fix that?
JFenlon said:
Never mind, I got KFU to recognise the device finally but I think it's bricked it, it's just black now with no light on the power button or anything.
I don't suppose there's any way to fix that?
Click to expand...
Click to collapse
how did you do to make windows recognize the kindle under otter2-prod-4???
JFenlon said:
Never mind, I got KFU to recognise the device finally but I think it's bricked it, it's just black now with no light on the power button or anything.
I don't suppose there's any way to fix that?
Click to expand...
Click to collapse
My Motivation For work LOL
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Great cup I like it, looks good, I recommend to get one, thanks!
Redbubble Sale
As of now, I'm trying to unbrick my kindle fire 1st generation, but my computer isn't recognizing it as ADB, only as Android, is there anyway to get it recognized as ADB so I can install twrp and flash a rom?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
carlybelle said:
As of now, I'm trying to unbrick my kindle fire 1st generation, but my computer isn't recognizing it as ADB, only as Android, is there anyway to get it recognized as ADB so I can install twrp and flash a rom?
Click to expand...
Click to collapse
Try updating the driver in driver settings. That was the problem with my PC once. I just updated and ADB was recognized
Sent from my Amazon Kindle Fire using xda app-developers app
404-Not Found said:
Try updating the driver in driver settings. That was the problem with my PC once. I just updated and ADB was recognized
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Nope, but thank you anyway, the problem is that my kindle fire has no os and it's just stuck at the stock boot up screen without any recovery...
You need a Fastboot cable/adapter/etc.
You can make one yourself by soldering 4th contact/the one with the missing spot to the 1st contact (red wire/power wire).
And then you can use whatever to recover.
AND make sure you use Kindle Fire FIRST GENERATION SOFTWARE. OTHERWISE YOU WILL BRICK AGAIN, AND THEN, COMES JTAG.
mr_verystock said:
You need a Fastboot cable/adapter/etc.
You can make one yourself by soldering 4th contact/the one with the missing spot to the 1st contact (red wire/power wire).
And then you can use whatever to recover.
AND make sure you use Kindle Fire FIRST GENERATION SOFTWARE. OTHERWISE YOU WILL BRICK AGAIN, AND THEN, COMES JTAG.
Click to expand...
Click to collapse
Okay thank you!
currently trying to update to jellybean using rwilco12's method it is currently on factory.img and hasn't progressed any further. It's been there for about 20 minutes and the status bar hasn't moved on my device or my PC. am i screwed?
gmc2jz said:
currently trying to update to jellybean using rwilco12's method it is currently on factory.img and hasn't progressed any further. It's been there for about 20 minutes and the status bar hasn't moved on my device or my PC. am i screwed?
Click to expand...
Click to collapse
Would you be able to provide some additional info? What build were you previously on, have you had issues in the past, etc.
Thanks!
i was on 4.0.4 ics tried using kies to update but kies ides everytime i try so i tried a oneclick method but when i got to factroyfs.img the status bar stopped moving at all i ust switched usb cords and ports and restarted the process maybe it will work this time
same results oh and no issues before this but this is the first attempt a rom flashing on this device
rwilco12 said:
Would you be able to provide some additional info? What build were you previously on, have you had issues in the past, etc.
Thanks!
Click to expand...
Click to collapse
how long does it normally take maybe i'm just being impatient?
gmc2jz said:
how long does it normally take maybe i'm just being impatient?
Click to expand...
Click to collapse
It usually takes a good half hour or so for the whole process
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For future use, NEVER, EVER remove the USB while flashing. Unless you wait at least an hour and nothing happens. Had it been flashing the recovery/bootloader right then you may have bricked your device.
Also, while flashing it may appear to hang. It isn't always the case.
gorei23 said:
For future use, NEVER, EVER remove the USB while flashing. Unless you wait at least an hour and nothing happens. Had it been flashing the recovery/bootloader right then you may have bricked your device.
Also, while flashing it may appear to hang. It isn't always the case.
Click to expand...
Click to collapse
It was hanging with the one click just got it working had to use the battery from my captivate with some modification was a crap phone any way.
Hello experts,
I hard bricked my phone, but with the tool I managed to repair it. But after unbricking it while starting phone, it got stuck in boot logo and screen appear to be broken but its not.
This is how phone look like and everytime it happene same.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https ://drive.google.com/open?id=0B_S-tkD3eHy5Y3h3NnB3Y013Uy1qbTZycnpTWHN3OXlEc05F
What to do in this case? I don't have any idea now.
Please provide any solution.
unnat1993 said:
Hello experts,
I hard bricked my phone, but with the tool I managed to repair it. But after unbricking it while starting phone, it got stuck in boot logo and screen appear to be broken but its not.
This is how phone look like and everytime it happene same.
https ://drive.google.com/open?id=0B_S-tkD3eHy5Y3h3NnB3Y013Uy1qbTZycnpTWHN3OXlEc05F
What to do in this case? I don't have any idea now.
Please provide any solution.
Click to expand...
Click to collapse
It appears to get to the part where it starts to load the OS. In this case try to get into recovery. If you can get into recovery, great! Then just adb sideload the latest ROM from OnePlus.
ZVNexus said:
It appears to get to the part where it starts to load the OS. In this case try to get into recovery. If you can get into recovery, great! Then just adb sideload the latest ROM from OnePlus.
Click to expand...
Click to collapse
Did it, but after sideloading latest ROM from oneplus, it runs perfectly for sometime and again doing same thing.
Un brick by method 2
unnat1993 said:
Did it, but after sideloading latest ROM from oneplus, it runs perfectly for sometime and again doing same thing.
Click to expand...
Click to collapse
This actually sounds like a hardware issue to me, but I have no idea what I am talking about so idk.
drmuruga said:
Un brick by method 2
Click to expand...
Click to collapse
Did it, problem persist. :crying:
I'm not see the video but why you flash twrp and flash any other rom and try ?
Finally, OnePlus has told me that motherboard is not working. So have to change phone.
I have a Fire TV 2nd Gen that I have not used in years. I recently fired it up and after attempting to boot up a few times it ends up on a recovery screen as seen in the photo.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there a way out of this? I would love to be able to factory wipe to stock firmware if at all possible?
PartisanEntity said:
I have a Fire TV 2nd Gen that I have not used in years. I recently fired it up and after attempting to boot up a few times it ends up on a recovery screen as seen in the photo.
View attachment 5733235
Is there a way out of this? I would love to be able to factory wipe to stock firmware if at all possible?
Click to expand...
Click to collapse
Looks like your eMMC is read/only, i.e. faulty.
There are a few reports about something like this, for sloane especially with faulty samsung eMMC chips.
I would sell the box (for parts only).
Thank you, that would be a shame.
However reading through my original post, I failed to mention that this Fire TV had in fact been rooted. I forgot how I did it back then, and as I said, I haven't used it in a really long time.
Do you think, given the new info that this device has previousy been rooted, that it is still is faulty memory?
PartisanEntity said:
Do you think, given the new info that this device has previousy been rooted, that it is still is faulty memory?
Click to expand...
Click to collapse
In case of a rooted box the eMMC may be fine, if something like the GPT or partitions are messed up.
You can always try the unlock/unbrick for sloane.
All you need is an USB a-a cable, a PC running ubuntu, the latest amonet.zip file for sloane and careful hands The last thing is the most important point as you would need to open up the box and short a special point to ground with something soft but conductive like small copper wire (i.e. no steel parts). The point to short is a really small SMD part and if the part gets lost or damaged, the eMMC gets not accessible... The shorting is a bit annoying as you may need about 50 attempts until the unbrick will work (the sloane isn't as easy to short like a firestick, because the box use a power brick and sucks power via usb too).
There is no guarantee at all that this will help you, since a broken eMMC is only fixable with a replacement chip...
but in case it's only a partition problem, a messed up filesystem or something like this you may get the box fixed. Try it.