Database Users

Broken touch screen, need to get Stock

The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).

drk.hd said:
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
Click to expand...
Click to collapse
There is a way to do this with adb... I just do not know the proper commands. Sorry

Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.

sengwall said:
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
Click to expand...
Click to collapse
No, I don't think it does, but I'd rather not take the chance.

drk.hd said:
No, I don't think it does, but I'd rather not take the chance.
Click to expand...
Click to collapse
YES! It absolutely does. The second the device was rooted it broke warranty.
Sent from my myTouch_4G_Slide using XDA App

The same thing actually happened to me earlier today. I was just browsing some sites on the ICS rom when it just stopped responding. I couldn't get it to recognize any touches even after a bunch of reboots, so I just figured it to be some bug that hadn't been squashed yet. When I dropped down to recovery and saw the same issue, I knew I had a real problem.
Hoping against hope, I tried both CWMR and TWRP on it and got no results. Like you, I figured it would have to go back to Amazon, so I started searching for a way to get it back to stock... nothing obvious jumped out at me because everything is written with access to recovery in mind... which doesn't help.
So, I started reading about adb and going through the built-in help. As I was familiarizing myself with some basic adb commands and options, I left TWRP open in front of me. I don't know how long I had it that way when I mindlessly tapped on the screen and thought I saw it flicker. Yes! I had pressed the Wipe button and it had taken me to that section. It's been working fine ever since.
I'm not claiming I did anything and I don't have a how-to on how to fix it, but it couldn't hurt to just leave the thing running in recovery for a while and see if the touchscreen comes back to life for you too.
Still, I'd love to see someone with more adb knowledge provide a simple tutorial on how to get it back to stock without access to recovery. I'm sure it would be helpful to someone in the future... maybe even me if the same problem comes up again.
Best of luck to you.

Just ignore my comment
Sent from my Amazon Kindle Fire using Tapatalk

If your on the rooted stock rom you could always wait until Amazon pushing the next OTA

You will have to make a fastboot image and flash that with fastboot. But before you create the image, you will have to create all the appropriate symlinks. Then you run...
Code:
make_ext4fs -l 512m -a system -s /path/to/fastboot_system.img /path/to/system_folder
That will create the fastboot image. Then when FFF gives you fastboot access, you run...
Code:
fastboot flash system fastboot_system.img
You will also need a fastboot image for recovery and the bootloader.

Isn't there any easy way like with my desire, simple ruu.
Or hasn't anyone created these images to flash. I also need to get back to stock everything and send it to amazon, my wifi gets error after some period of time and some times when screen goes off, try'd 3 roms and stock.

There is a way to tell the device to install /sdcard/update.zip via shell commands. I forget what they are tho. Something about the extendedcommands. If I have time tomorrow I'll look it up.

here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/

b63 said:
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
Click to expand...
Click to collapse
Thanks for the link. I'm back on this thread because I think my Kindle Fire touchscreen is now dead for good. However, those instructions do not work as-is because you need to press a button on the screen to tell the Kindle Fire to allow the host to mount it as a USB Mass Storage device. Although those instructions don't get you all the way there, I was able to use the core idea to get my Kindle Fire back to stock. So, many thanks for pointing me in the right direction.
On top of the touchscreen not working, I ended up partially bricking the device trying to find a way to flash it back to stock, so I had also posted in the Unbricking thread. I posted my solution there....
http://forum.xda-developers.com/showpost.php?p=23226260&postcount=701
Odds are, if you have a device that is booting correctly, you will be able to ignore steps 3 and 4 and get it booting back to stock. I do have a couple of other suggestions... Leave your USB cable hooked up to the Kindle Fire as it boots into stock for the first time. This is the only time that it will automatically mount the /sdcard to your computer and you will have a chance to reclaim (and delete) all the files stored there. You can also do something like 'adb pull /sdcard C:\sdcard' before you flash. Also, depending on what ROM and apps you were using before starting the process, you might want to delete your user data and reset the device to factory defaults. You can do this with 'fastboot erase userdata' and the next time you start the device, you'll get a warning that it's about to reset. Hit the power button and you should have a clean, fresh from the factory Kindle fire... albeit with a broken touchscreen. Good luck!

After several failed attempts to follow this guide (no offense to posters; I appreciate your contributions), I found this to be the simplest method.
http://stackoverflow.com/questions/10817721/wipe-data-factory-reset-through-adb
Download stock update, then it's basic procedure in adb:
adb push C:/update.zip /sdcard/update.zip
adb shell
recovery --wipe_data
After reboot, go back into to adb shell and do "recovery--update_package=/sdcard/update.zip"
Factory reset, etc. and you're good to go.

[Q] Kindle Stuck in TWRP Recovery

Okay,I've read everything on this topic. I've tried almost everything (except using the factory cable). If you can help me fix this I will paypal you (or the charity of your choice) the $25 dollars I would've spent on a factory cable.
I just want to know if I'm missing anything before I try and make or buy a cable.
My Problem:
I rooted my Kindle fire 6.3 using KFU, everything went flawlessly
(This is when I should've stopped, enjoyed my new root, and be problem free...but I didn't)
I saw a thread for the CM9 Reloaded Rom and thought "Hey I should push my luck and install this rom immediately!"
so with KFU I installed TWRP and then from there all hell broke loose
and by all hell I mean that I got stuck in TWRP recovery and couldn't boot my device normally
blah blah blah, I tried everything and somewhere along the way wiped everything from my kindle, I dont know why or how but it happened
The only thing I can do now is boot into twrp recovery. I've tried literally everything but if there's anyways you can fix this I will paypal you the $25 I would've spent on the factory cable.
I will be on this forum all day seeing as it's sunday and I am ready and willing to answer any and all questions about my predicament to further clarify the issue.
THANKS!!
p.s.
This isn't a knock against ReloadedRom or TWRP, I understand people have worked hard on them and I really appreciate all the devs do around here. this is simply an IBM (Idiot Behind Machine) problem!

gdr425 said:
Okay,I've read everything on this topic. I've tried almost everything (except using the factory cable). If you can help me fix this I will paypal you (or the charity of your choice) the $25 dollars I would've spent on a factory cable.
I just want to know if I'm missing anything before I try and make or buy a cable.
My Problem:
I rooted my Kindle fire 6.3 using KFU, everything went flawlessly
(This is when I should've stopped, enjoyed my new root, and be problem free...but I didn't)
I saw a thread for the CM9 Reloaded Rom and thought "Hey I should push my luck and install this rom immediately!"
so with KFU I installed TWRP and then from there all hell broke loose
and by all hell I mean that I got stuck in TWRP recovery and couldn't boot my device normally
blah blah blah, I tried everything and somewhere along the way wiped everything from my kindle, I dont know why or how but it happened
The only thing I can do now is boot into twrp recovery. I've tried literally everything but if there's anyways you can fix this I will paypal you the $25 I would've spent on the factory cable.
I will be on this forum all day seeing as it's sunday and I am ready and willing to answer any and all questions about my predicament to further clarify the issue.
THANKS!!
p.s.
This isn't a knock against ReloadedRom or TWRP, I understand people have worked hard on them and I really appreciate all the devs do around here. this is simply an IBM (Idiot Behind Machine) problem!
Click to expand...
Click to collapse
If you know how to use fast boot try this command:
fastboot -i 0x1949 oem idme bootmode 4000
That should get you out of the twrp loop.
Sent from my Amazon Kindle Fire using XDA

gdr425 said:
Okay,I've read everything on this topic. I've tried almost everything (except using the factory cable). If you can help me fix this I will paypal you (or the charity of your choice) the $25 dollars I would've spent on a factory cable.
I just want to know if I'm missing anything before I try and make or buy a cable.
My Problem:
I rooted my Kindle fire 6.3 using KFU, everything went flawlessly
(This is when I should've stopped, enjoyed my new root, and be problem free...but I didn't)
I saw a thread for the CM9 Reloaded Rom and thought "Hey I should push my luck and install this rom immediately!"
so with KFU I installed TWRP and then from there all hell broke loose
and by all hell I mean that I got stuck in TWRP recovery and couldn't boot my device normally
blah blah blah, I tried everything and somewhere along the way wiped everything from my kindle, I dont know why or how but it happened
The only thing I can do now is boot into twrp recovery. I've tried literally everything but if there's anyways you can fix this I will paypal you the $25 I would've spent on the factory cable.
I will be on this forum all day seeing as it's sunday and I am ready and willing to answer any and all questions about my predicament to further clarify the issue.
THANKS!!
p.s.
This isn't a knock against ReloadedRom or TWRP, I understand people have worked hard on them and I really appreciate all the devs do around here. this is simply an IBM (Idiot Behind Machine) problem!
Click to expand...
Click to collapse
I'll help you if you'll spend the money on a factory cable anyway so you can get out of your next situation.
Read this post and make sure your drivers are in order.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
You'll have to get that done first before anything else. If you are completely lost, reading the first post in that thread wouldn't be a bad idea either.
Basically, you have to set the bootmode back to normal using either adb or fastboot... but like I mentioned before, you have to make sure your drivers are working and recognizing your KF.

kinfauns said:
I'll help you if you'll spend the money on a factory cable anyway so you can get out of your next situation.
Read this post and make sure your drivers are in order.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
You'll have to get that done first before anything else. If you are completely lost, reading the first post in that thread wouldn't be a bad idea either.
Basically, you have to set the bootmode back to normal using either adb or fastboot... but like I mentioned before, you have to make sure your drivers are working and recognizing your KF.
Click to expand...
Click to collapse
I'm sorry for asking noob like questions
I swear i've had an android phone rooted and all that for over 2 years...anyways
what do you mean "recognizing your KF"
It shows up in my list of devices when I plug it in

gdr425 said:
I'm sorry for asking noob like questions
I swear i've had an android phone rooted and all that for over 2 years...anyways
what do you mean "recognizing your KF"
It shows up in my list of devices when I plug it in
Click to expand...
Click to collapse
Just having it show up isn't good enough. With TWRP open... you need to have it show up exactly as "Android Phone -> Android Composite ADB Interface" and "Composite" must be in there.
If it does that... Go to your Kindle Fire Utility folder, open the tools folder inside there. Once you have that open, shift-right-click inside the folder and select "Open command window here" to get to the command line. Then inside that enter these two commands... one after the other....
Code:
adb shell idme bootmode 4000
adb reboot
Your KF should restart back into a normal boot and get you to your system.
EDIT: I guess I should mention that the "shift-right-click" inside a folder works in Windows 7, but I'm not sure that it does in previous versions.

When I did that, it reboots, shows the yellow triangle telling me to press the power button to enter recovery, if i press i get to twrp if i don't it just shuts off with the amber power button on
I think i may have to manually install the drivers?

gdr425 said:
When I did that, it reboots, shows the yellow triangle telling me to press the power button to enter recovery, if i press i get to twrp if i don't it just shuts off with the amber power button on
I think i may have to manually install the drivers?
Click to expand...
Click to collapse
If it's able to reboot with the "adb reboot" command, I'm guessing your drivers are working fine, but just to verify... What device is shown in the device manager when you have it booted into TWRP?
It's possible that you have a broken ROM flashed onto your device right now and it can't complete a normal boot. You might want to try flashing a new ROM...

If it's rebooting after issuing the commands, then you shouldn't have to press the power button once the yellow triangle comes up. Just give it a few seconds to get past that part and to the KF screen.
I was having the same issues yesterday after flashing, but resolved once I realized I could issue the commands.

if I dont press the power button it just shuts down, I actually figured out a fix for this brick that worked for me I'll post it in a thread today because i've seen a lot of people having the same problem without much success, THANKS to EVERYONE who helped me with this!

http://forum.xda-developers.com/showthread.php?t=1576675
should take care of your problem

Kindle Fire bricked. Need major help

Hello, so this is my first time trying to root an android device, and I think I messed up. I watched a tutorial on youtube on how to do it and successfully installed superuser and twrp from a batch file ( I had to install adb drivers first ). I wasn't really sure I did it in the correct steps, so I wanted to revert back to the stock os. I booted into twrp and wiped the data ( cache, system, etc) from twrp. I then mounted it and transfered the kindle fire update 6.3.1 to my KF. I used the option on twrp to revert back to stock using the newly transferred zip. It ran for awhile then prompted me to click reboot. So I did. And this is where it gets tricky
After the reboot, all I see is the boot screen displaying "kindle fire." It never booted and lasted like this for hours. I tried to boot into twrp but I think it got deleted. I googled the problem and found it was in some sort of fastboot loop. I tried many fixes, using adb and other fastboot commands. Every time I tried anything, all I got was "waiting for device." Also, I couldn't use adb shell because it said system/bin/sh was not found. I went to my computer and found that the kindle fire no longer showed up as a removable device, but it showed up in device manager as adb composite interface under android phone. I thought that somehow all of my system files got deleted and thats why it says system/bin/sh not found. I tried to use the adb push command to manually send the update.zip to the KF but it is no longer a mounted drive, so there is nowhere to send it to. I'm at a loss here, Ive tried numerous utilities such as KFU, firekit, unbrick utility. I just need to figure out a way to remount the KF and copy over the folder "system" in the update.zip. If anyone could help me that would be great, as I have been trying to fix this for three days now.:fingers-crossed:

Read the How To in the attached link and it should help you figure out what the problem is and get you unbricked, http://forum.xda-developers.com/showthread.php?t=1552547.

tazmanhawaii said:
Read the How To in the attached link and it should help you figure out what the problem is and get you unbricked, http://forum.xda-developers.com/showthread.php?t=1552547.
Click to expand...
Click to collapse
That doesn't really help me at all, as I have tried the solutions that what you just posted provides, and none of them have worked. I have tried flashing firefirefire and twrp to the kindle fire using fastboot, but to no avail. I think I need a bit more help than a beginner's guide can provide, but thanks for the link.

Marblesnake said:
That doesn't really help me at all, as I have tried the solutions that what you just posted provides, and none of them have worked. I have tried flashing firefirefire and twrp to the kindle fire using fastboot, but to no avail. I think I need a bit more help than a beginner's guide can provide, but thanks for the link.
Click to expand...
Click to collapse
First of all, when you try to revert to stock without wiping the necessary partitions, bad things will happen. What usually happens is you end up with some sort of frankenROM with no working shell and no custom bootloader or recovery.
Based on your description, it seems like you aren't in fastboot at all. You can confirm this by paying attention to the boot screen at the device starts up. If you see a bright Kindle Fire logo that stays bright, you're in fastboot. If you see a bright Kindle Fire logo that dims a little after a few seconds, you're no longer in fastboot and the device is trying to boot normally. What usually happens in situations like yours is, not only does the system have no way of booting, but there is also no working shell to send the necessary commands to change the bootmode, and you will receive the typical "system/bin/sh not found" error.
The problem is without a working shell, you cannot get into fastboot to install custom recovery and you cannot install recovery while booted "normally" without a working shell.
You have two options:
* Acquire a factory cable. A Motorola style factory programming cable to be exact. You can purchase one, or make one yourself. There is a thread in the KF General forum with information regarding both. The factory cable will put the device in fastboot so you will be able to install custom recovery and repair your system.
or
* Use Firekit. But in order for Firekit to work properly in your situation, you need to put the device in USBboot to install a "new" bootloader and recovery. This consists of opening the device and using the "shorting trick" as described in the Firekit thread. I would suggest creating a liveUSB with "persistence" and install the SoupKit. SoupKit comes with Firekit along with a number of other tools you may find useful.
Either way, you need to get custom recovery installed so you can wipe your system and data (factory reset) partitions and flash a new ROM. If it's the stock ROM you want, MoDaCo is your best bet. Once you install a custom ROM, there is no need to "root" as all custom ROMs come pre-rooted.
Hope that helps.

soupmagnet said:
First of all, when you try to revert to stock without wiping the necessary partitions, bad things will happen. What usually happens is you end up with some sort of frankenROM with no working shell and no custom bootloader or recovery.
Based on your description, it seems like you aren't in fastboot at all. You can confirm this by paying attention to the boot screen at the device starts up. If you see a bright Kindle Fire logo that stays bright, you're in fastboot. If you see a bright Kindle Fire logo that dims a little after a few seconds, you're no longer in fastboot and the device is trying to boot normally. What usually happens in situations like yours is, not only does the system have no way of booting, but there is also no working shell to send the necessary commands to change the bootmode, and you will receive the typical "system/bin/sh not found" error.
The problem is without a working shell, you cannot get into fastboot to install custom recovery and you cannot install recovery while booted "normally" without a working shell.
You have two options:
* Acquire a factory cable. A Motorola style factory programming cable to be exact. You can purchase one, or make one yourself. There is a thread in the KF General forum with information regarding both. The factory cable will put the device in fastboot so you will be able to install custom recovery and repair your system.
or
* Use Firekit. But in order for Firekit to work properly in your situation, you need to put the device in USBboot to install a "new" bootloader and recovery. This consists of opening the device and using the "shorting trick" as described in the Firekit thread. I would suggest creating a liveUSB with "persistence" and install the SoupKit. SoupKit comes with Firekit along with a number of other tools you may find useful.
Either way, you need to get custom recovery installed so you can wipe your system and data (factory reset) partitions and flash a new ROM. If it's the stock ROM you want, MoDaCo is your best bet. Once you install a custom ROM, there is no need to "root" as all custom ROMs come pre-rooted.
Hope that helps.
Click to expand...
Click to collapse
Thanks for the help. Yeah, I tried the firekit method but didn't use the shorting trick. I have scoured the internet for information and tricks and it seems like these are my last two options before I throw this thing out the window. I have seen your posts in other threads and you have been a great help throughout this ordeal.

factory cable
thank you for this information. I am in the same predicament. I am purchasing a factory cable from Amazon $1.27.
It is sold by Earlybirdsavings and is a 3ft micro USB factory cable for kindle fire and Motorola Xoom.
thank you for all the helpful information!

[Q] Unbricked & rooted 3.0.1 - can't update to ICS or JB.

Ok here goes. Sorry for the long post but I want to give as much info as possible so I don't leave any of you in the dark about anything. Been working on / researching this for four days now to no avail.
My A500 which was running ICS 4.0.2 just randomly bricked itself one night, so I downloaded EUUs_SBK_Acer_A500_1.016.05_COM_GEN1 from here. It worked, but I really don't want to stay on HC 3.0.1 so I decided to go through the updates. It updated great, HC 3.1...3.2...then when the ICS update came along BAM it bricked itself again (stuck on Acer loading screen)
So, I decided I might as well root it, since I've always wanted to. Ran EUUS again to reset to HC 3.0.1 then ran gingerbreak. Installed Acer Recovery Installer and used Thor's recovery 1.7 I believe it was. Booted into recovery and tried to install update.zip from the STOCK Acer_A500_7.014.16_041.206.01_COM_GEN1.zip I downloaded and BAM bricked again...my tablet doesn't like ICS now all of a sudden? Strange...
I then downloaded NVFLASH from here and installed skrilax's V8 bootloader w/recovery. Booted into recovery great, wiped the partitions etc. and tried to install the same ICS update.zip. BRICKED again!!!! Back to the drawing board...run EUUS...3.0.1 again...
So after days of working on this I decided maybe my Tab hates ICS now for some reason unbeknownst to me. Not very rational (lol) but anyway. I saw the JB ROM that's been put up http://forum.xda-developers.com/showthread.php?t=2239476&highlight=rom+ics and figured heck, why not, maybe the ICS ROM I have is corrupt. So I used NVFLASH, Skrilax's V8, and flashed the ROM...bricked again
I think the only thing I haven't tried is
I think I'm going to go crazy now.
Please help, I'm at wit's end.
More info:
I have acquired mmcblk0 (renamed to mmcblk0_start), my CPUID, and my SBK
I enable USB Debugging and Unknown Sources every time.
I have Windows 7, but also have UBUNTU installed on a Virtual Machine if the need arises.
Oh and I've booted into fastboot mode and run Babsector as well which did not help.
Hope I didn't miss anything. My brain is tired from working on this for so many days. I really want my A500 back! Either JB or ICS & rooted if possible!!!

Pareeeee said:
Ok here goes. Sorry for the long post but I want to give as much info as possible so I don't leave any of you in the dark about anything. Been working on / researching this for four days now to no avail.
My A500 which was running ICS 4.0.2 just randomly bricked itself one night, so I downloaded EUUs_SBK_Acer_A500_1.016.05_COM_GEN1 from here. It worked, but I really don't want to stay on HC 3.0.1 so I decided to go through the updates. It updated great, HC 3.1...3.2...then when the ICS update came along BAM it bricked itself again (stuck on Acer loading screen)
So, I decided I might as well root it, since I've always wanted to. Ran EUUS again to reset to HC 3.0.1 then ran gingerbreak. Installed Acer Recovery Installer and used Thor's recovery 1.7 I believe it was. Booted into recovery and tried to install update.zip from the STOCK Acer_A500_7.014.16_041.206.01_COM_GEN1.zip I downloaded and BAM bricked again...my tablet doesn't like ICS now all of a sudden? Strange...
I then downloaded NVFLASH from here and installed skrilax's V8 bootloader w/recovery. Booted into recovery great, wiped the partitions etc. and tried to install the same ICS update.zip. BRICKED again!!!! Back to the drawing board...run EUUS...3.0.1 again...
So after days of working on this I decided maybe my Tab hates ICS now for some reason unbeknownst to me. Not very rational (lol) but anyway. I saw the JB ROM that's been put up http://forum.xda-developers.com/showthread.php?t=2239476&highlight=rom+ics and figured heck, why not, maybe the ICS ROM I have is corrupt. So I used NVFLASH, Skrilax's V8, and flashed the ROM...bricked again
I think the only thing I haven't tried is
I think I'm going to go crazy now.
Please help, I'm at wit's end.
More info:
I have acquired mmcblk0 (renamed to mmcblk0_start), my CPUID, and my SBK
I enable USB Debugging and Unknown Sources every time.
I have Windows 7, but also have UBUNTU installed on a Virtual Machine if the need arises.
Oh and I've booted into fastboot mode and run Babsector as well which did not help.
Hope I didn't miss anything. My brain is tired from working on this for so many days. I really want my A500 back! Either JB or ICS & rooted if possible!!!
Click to expand...
Click to collapse
Wow I thought I was the only one who had this issue. My A501 was working fine on Evil-A V2 (4.1.2) for many months and decided one night to crash and now stuck on V8 boot screen. Ive tried everything however I can get it to boot up on a 3.2 update.zip file.
The only recoveries I can get to work are TWRP 2.5.0.0 (on secboot)
Now I cant get it to flash anything other than 3.2.
It is formatted with ext4 partitions
whenever I try to flash it reboots to ACER download screen but the flashers wont get any further than that. (loads Acer boot recovery driver ok)
Any ideas?

Nice to know I'm not the only one. I hope we get some answers!!
*sigh* My situation has gotten worse. Now TDv4/EUUS won't roll back my device and my tab won't go past the recovery bootscreen (Just says "TEAMWIN" on the screen) That is the ONLY recovery that NVFLASH will flash to my device now, for some reason none of the other recoveries will go back onto it.
My stress level has gone up 800% from working on this. I don't have the money to buy a new tab. I really need to get this one working again.
:crying:

Pareeeee said:
Nice to know I'm not the only one. I hope we get some answers!!
*sigh* My situation has gotten worse. Now TDv4/EUUS won't roll back my device and my tab won't go past the recovery bootscreen (Just says "TEAMWIN" on the screen) That is the ONLY recovery that NVFLASH will flash to my device now, for some reason none of the other recoveries will go back onto it.
My stress level has gone up 800% from working on this. I don't have the money to buy a new tab. I really need to get this one working again.
:crying:
Click to expand...
Click to collapse
have you tried lightspeed v8 bootloader and rom? that's the only thing that worked for me. then I could updatw to twrp and jb.
Sent from here

LPMatt said:
have you tried lightspeed v8 bootloader and rom? that's the only thing that worked for me. then I could updatw to twrp and jb.
Sent from here
Click to expand...
Click to collapse
I think my MB is failing/has failed. Either that or something I flashed to it was badly corrupted.
Now my tab has stuck itself in apx mode, bootloader won't load, recovery won't load, every program I have (nvflash, TDv4, EUUs, Babsector, etc) fails. Babsector gives me the fatal error "command 12 NvError 0x120002" and "setting device: 2 3" which I've read means that the tab is shot. Adb.exe tells me the device is not detected, even though all the drivers are installed correctly.
I'm pretty bummed because I don't have the money to buy another tab at the moment, and I used it ALL the time, took it everywhere with me.
On the up-side, I've done some research and it seems if you disassemble your tab and sell the working parts (things like the screen, metal back panel, internal speakers - obviously NOT the MB though!) individually on eBay you can make a bit of your money back.
Can anyone direct me to some good links/video tutorials for dis-assembly?

whoops... I just started a new thread with a very similar issue... My tab also just involuntarily bricked itself... I've made some progress but it's still in bad shape... I don't know about you guys but I had been running at a steady 50% overclock; do you think that could have led to this?

Sorry Man
No @rwilpstra....my a500 is overclocked to 1504 ghz and it runs just fine......as for you pareeeee....Sorry man.....your device is gone....no apx...no fastboot....no recovery.....it's beyond minor corruption....it's like you somehow managed to corrupt every single part of the memory and every partition that there was on your device....you're better off disassembling it.:crying::crying:

FireTV Stick 2 Tank - no wifi after unbrick

Hi
I have a fireTV stick 2 (LY73PR) which was about to install an OTA update when there was a power out. After that it would only loop to the "optimizing system storage..." screen.
Using these instructions:
How To Completely Remove TWRP and Return to Full Stock
Works only on Tank HD and Mantis 4K. The process is really simple and requires very little effort to return back to 100% stock in case you return your device or for many reasons. Ok download and find the official latest stock image for your Fire...
forum.xda-developers.com
and the stock rom 5.2.7.7 from here:
Fire TV Stick 2 Tank 5.2.7.7 OTA ZIP + Launcher Replacement ROOT
Fire TV Stick 2 Tank 5.2.7.7 OTA ZIP 5.2.7.4 https://workupload.com/file/pJMUm5X9bJz 5.2.7.6 https://workupload.com/file/2DTaH3fv2sE 5.2.7.7 https://www.mediafire.com/file/b7dw9i9kqzjmn29/ftvs2k-5.2.7.7.zip/file For Launcher replacement you...
forum.xda-developers.com
I was able to get new life into the stick. It is starting now and asking for the language. After that it gets to the screen "Scanning for networks" but there it cannot find any networks, so I am stuck there.
I tried to restart and reset the stick using the remote but it didnt help.
would really appreaciate if someone could help with this.

Could be that your sticks unique data is messed up.
Easy to check if you boot into TWRP, mount system, connect with adb and run:
Code:
adb shell
idme print
Check that output, wifi needs some valid things in there, like a MAC Address... and maybe that (and other stuff like the serial) is wiped.

I tried again today but realized that the stick is not responding anymore. while it was usually always quite warm, it remains stone cold now. An USB power meter shows the stick is not taking any current. Connecting it to the TV, even for hours, didnt do anything either.
so unless someone has some miracle workaround, I guess the stick is ready for the trashcan...

You probably broken hardware just open it again and clean it from inside