Develop Bugs

[Q] Wiped the WHOLE Kindle, Need help ASAP!

so yesterday i got tired of my ICS Rom. So, i went to recovery (TWRP) then recovered my old back up of stock. But since it had all the settings like when I flashed the rom, I Factory reseted it. But then suddenly it had deleted the whole stock rom! Couldn't go back. So my kindle was stuck on recovery loop over and over again. I got really impatient. So I started moving around then I mounted my Kindle to my computer and apped the ICS Rom that I used before. Then it flashed but it was still stuck on recovery. started moving more stuff on it, clicked the partitioning sd card and now I can't mount my kindle via Usb -___- and Then I new it was on Recovery fastboot. Please help! I Need this fixed. it deleted everything. and when I connected it to Adb shell, it says "Missing system/bin/sh"
Help me! i'm going to california on next week and I would like my kindle to work for me to play, listen to music, watch tv on it on the way.
Sorry for bad Grammar -___-

Do you have FFF? Is fastboot working at all? If so, have you tried fastboot oem format? (this will cause all your data to get lost), or booting/reflashing TWRP?

Dasanko said:
Do you have FFF? Is fastboot working at all? If so, have you tried fastboot oem format? (this will cause all your data to get lost), or booting/reflashing TWRP?
Click to expand...
Click to collapse
I Have FFF 1.4, have TWRP 2.1 and fastboot works. But Mounting USB don't work. In recovery it says (cannot mount /sdcard/ (Invalid argument).)

What's the output of
adb shell "parted /dev/block/mmcblk0 p"
?

Can you please explain what that means. i really don't now many of these commands. I need more like a Step-by-step. Like in ADB Shell, it says error: device not found

Luise. said:
Can you please explain what that means. i really don't now many of these commands. I need more like a Step-by-step. Like in ADB Shell, it says error: device not found
Click to expand...
Click to collapse
Means your KF is either not plugged in, or the drivers are wrong. You can't go on until the drivers are properly installed, if that's your issue. Take a look here: http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2

Okay, Installed ADB Drives I think it now works it just tells me (exec '/system/bin/sh' failed: No such file or directory (2))

Can you type "fastboot getvar product" and then restart/plug in the KF?

Dasanko said:
Can you type "fastboot getvar product" and then restart/plug in the KF?
Click to expand...
Click to collapse
Yes i did and it says "Kindle"

Get TWRP (http://teamw.in/project/twrp2/79) and type "fastboot boot openrecovery-twrp-blaze-2.1.1.img" and see if you can get ADB working now.

Okay I already have TWRP Installed on 2.1.1 so Do I just go on Recovery and try to work adb shell on there instead of FFF Fastboot?

You just hinted at your ADB not working properly, try to fastboot boot into that TWRP to see if ADB works fine from it (I guess your drivers are good on the Device Manager, no errors or warnings showing up?). If it doesn't, then I guess the alternative is to try restoring the entire stock layout...

okay, I have TWRP, and when i have the usb connected to Kindle while its on Recovery, My Internet i use a Easytether so you can tell what android devices are connected and while my kindle is on recovery, The Easytether says My Kindle can connect, (but it really cant) and the ID Shows up that 0000005 number? but I Really Need My kindle to work! -__-

These issues have been fixed.
For future reference, this user was experiencing a combination of bad drivers and a corrupt sd card partition (rm 12 + mkpartfs primary fat32 start end + name 12 media).
The ADB issues were gone after fixing the drivers, without a need to reinstall TWRP.

Can't format /data & /cache

Hi!
I think my /data partition is corrupt. Anytime I flash a new ROM, a handlful of apps I've previously installed are preloaded when then ROM first boots up. I've wiped my dalvik cache, superwiped multiple times, and did a factory reset multiple times, but no matter what ROM i install (JB, CM7, MIUI, Original Sense [Liberation]), those apps are still there, and causes forces closes.
So I went into CWM, and tried to manually format the /data partition and I get the "Error formatting /data" For that matter, this same error happens when I try to format /cache.
I've trired multile ROMs, multiple kernels. I've triend Amon Ra, (I couldn't install TWRP because of a status 7 error). I've deleted the /data folder through adb/fastboot (and it reappears afterwards).Like I said, I've done factory resets, tried formatting each partition (both with the partitions mounted and unmounted), superwipe, fixed permissions..I'm at a complete loss on what to do next. I'm willing to erase everything entirely from the phone and start from scratch if I have to, but I have no access to do anything. Did I brick my phone? I had previously used the EXT4 mod, but I've ran the zips to revert to normal already.

Leshy01 said:
Hi!
I think my /data partition is corrupt. Anytime I flash a new ROM, a handlful of apps I've previously installed are preloaded when then ROM first boots up. I've wiped my dalvik cache, superwiped multiple times, and did a factory reset multiple times, but no matter what ROM i install (JB, CM7, MIUI, Original Sense [Liberation]), those apps are still there, and causes forces closes.
So I went into CWM, and tried to manually format the /data partition and I get the "Error formatting /data" For that matter, this same error happens when I try to format /cache.
I've trired multile ROMs, multiple kernels. I've triend Amon Ra, (I couldn't install TWRP because of a status 7 error). I've deleted the /data folder through adb/fastboot (and it reappears afterwards).Like I said, I've done factory resets, tried formatting each partition (both with the partitions mounted and unmounted), superwipe, fixed permissions..I'm at a complete loss on what to do next. I'm willing to erase everything entirely from the phone and start from scratch if I have to, but I have no access to do anything. Did I brick my phone? I had previously used the EXT4 mod, but I've ran the zips to revert to normal already.
Click to expand...
Click to collapse
First off, i am unaware of a script that reverts the ext4 mods, where did you get it from? First i would try an ruu, if that dosent fix it, i would try fastboot flashing the misc partition, and then do the froyo ruu and reroot. Are you s-off? What radio and hboot version?

cmlusco said:
First off, i am unaware of a script that reverts the ext4 mods, where did you get it from? First i would try an ruu, if that dosent fix it, i would try fastboot flashing the misc partition, and then do the froyo ruu and reroot. Are you s-off? What radio and hboot version?
Click to expand...
Click to collapse
Thanks for the quick reply! I guess I should clarify regarding ext4. I used the "no_data_limit_dalvik_moved" mod to move the unused datadata partition for my /data/dalvik-cache folder. Seeing as how the ext4 modifies the /data AND /cache partitions, and those are the only two that are giving me trouble, I'm thinking that might be the cause of my troubles.
Haven't tried an ruu yet so that'll be my next step. But what do you mean by flashing the "misc" partition? I'm at work so I'll have to try that when I get home. Might have to look up how to flash the ruu too. It's been a while. lol
Am I s-off? Yes.
Radio? 2.15.10.07.07
hboot: 0.92.0000
Edit: So I tried flashing both RUUs (PB31IMG version) Gingerbread AND froyo found here. With both instances, the phone would freeze on the boot image. (Where is says DROID, then those little red dots circle the middle camera twice).It reset and continues to bootloop over and over.

Leshy01 said:
Thanks for the quick reply! I guess I should clarify regarding ext4. I used the "no_data_limit_dalvik_moved" mod to move the unused datadata partition for my /data/dalvik-cache folder. Seeing as how the ext4 modifies the /data AND /cache partitions, and those are the only two that are giving me trouble, I'm thinking that might be the cause of my troubles.
Haven't tried an ruu yet so that'll be my next step. But what do you mean by flashing the "misc" partition? I'm at work so I'll have to try that when I get home. Might have to look up how to flash the ruu too. It's been a while. lol
Am I s-off? Yes.
Radio? 2.15.10.07.07
hboot: 0.92.0000
Edit: So I tried flashing both RUUs (PB31IMG version) Gingerbread AND froyo found here. With both instances, the phone would freeze on the boot image. (Where is says DROID, then those little red dots circle the middle camera twice).It reset and continues to bootloop over and over.
Click to expand...
Click to collapse
Ok do you have adb and fastboot setup on a pc, you will need it to flash the misc partition? It sounds like your partition tables may have gotten messed up. The misc partition is where this info is stored. If or when you have adb fastboot and their drivers installed, i will tell you how to flash misc. Also in the meantime, try flashing this ruu just for kicks http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip.

cmlusco said:
Ok do you have adb and fastboot setup on a pc, you will need it to flash the misc partition? It sounds like your partition tables may have gotten messed up. The misc partition is where this info is stored. If or when you have adb fastboot and their drivers installed, i will tell you how to flash misc. Also in the meantime, try flashing this ruu just for kicks http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip.
Click to expand...
Click to collapse
Thanks! I have adb/fastboot on my home pc, yea. So you can tell me what to do, then I'll get home and try it, and then post results. I'll try that ruu as well and let you know. I tried following some direction online usin parted, but I couldn't make heads or tails of which partition was which.

Leshy01 said:
Thanks! I have adb/fastboot on my home pc, yea. So you can tell me what to do, then I'll get home and try it, and then post results. I'll try that ruu as well and let you know. I tried following some direction online usin parted, but I couldn't make heads or tails of which partition was which.
Click to expand...
Click to collapse
After you run that ruu i posted, your hboot version should be updated to 1.07. You will then need to go to http://www.htcdev.com/bootloader, and follow the steps to unlock your bootloader. Skip the first couple parts where it has you set up fastboot and skip the bootloader update part (ruu) and start where it has you get a code from your phone (Unlock token). Finish the rest, of the unlock steps and you will see at the top of hboot it now says unlocked.
Once unlocked download this file http://dinc.does-it.net/Guide_Root_New_Hboot/mtd0.img, and place it on your pc in the same folder as the fastboot.exe file. Then boot the phone to hboot, and connect it to the pc, and select fastboot from the hboot menu, so that it says fastboot plug in red at the top. Open a cmd prompt on your pc to where fastboot.exe is, and type the folowing:
Code:
fastboot devices
It should show a string of numbers. If it says no devices found, something is wrong with the connection between the phone and pc, or the adb drivers are not setup right on the pc.
If the connections fine and it found your device then type :
Code:
fastboot flash misc mtd0.img
Now download this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip, and flash it thru hboot. Once it compleets reboot, and hopefully it boots up like it should.
If it does boot and all is well, then reroot by flashing cwm http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot, and then flash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip, thru recovery. From there you can flash a rom of your choosing.

cmlusco, you get thanks for being so willing to help other members with their issues. I think you deserve more than I gave you today but I think it's cool how you're always trying to help people with potential bricks and when you tested out kernels and such for me.

tiny4579 said:
cmlusco, you get thanks for being so willing to help other members with their issues. I think you deserve more than I gave you today but I think it's cool how you're always trying to help people with potential bricks and when you tested out kernels and such for me.
Click to expand...
Click to collapse
Thanks tiny, you do great work yourself. I like helping people and i love technical stuff. Knowledge is everything, and its good to pass it on.

cmlusco said:
After you run that ruu i posted, your hboot version should be updated to 1.07. You will then need to go to http://www.htcdev.com/bootloader, and follow the steps to unlock your bootloader. Skip the first couple parts where it has you set up fastboot and skip the bootloader update part (ruu) and start where it has you get a code from your phone (Unlock token). Finish the rest, of the unlock steps and you will see at the top of hboot it now says unlocked.
Once unlocked download this file http://dinc.does-it.net/Guide_Root_New_Hboot/mtd0.img, and place it on your pc in the same folder as the fastboot.exe file. Then boot the phone to hboot, and connect it to the pc. Open a cmd prompt on your pc to where fastboot.exe is, and type the folowing:
Code:
adb devices
It should show a string of numbers. If it says no devices found, something is wrong with the connection between the phone and pc, or the adb drivers are not setup right on the pc.
If the connections fine and it found your device then type :
Code:
fastboot flash misc mtd0.img
Now download this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip, and flash it thru hboot. Once it compleets reboot, and hopefully it boots up like it should.
If it does boot and all is well, then reroot by flashing cwm http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot, and then flash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip, thru recovery. From there you can flash a rom of your choosing.
Click to expand...
Click to collapse
Curiously, I've only gotten as far as "adb devices" Although I can perform "fastboot reboot" and "fastboot devices" I try "adb devices" and the list is blank. I've used the drivers included in the android sdk. I've also used the drivers from htc sync. I don't know why I can't find my device in adb though. To be clear, my phone says "HBOOT USB PLUG" while I'm trying this.
thank you so much by the way for all your help. And you too tiny. I feel like I'm standing on the shoulders of giants here!
Also, is there some irc channel or something with a bit less idle time between forum posts?

Leshy01 said:
Curiously, I've only gotten as far as "adb devices" Although I can perform "fastboot reboot" and "fastboot devices" I try "adb devices" and the list is blank. I've used the drivers included in the android sdk. I've also used the drivers from htc sync. I don't know why I can't find my device in adb though. To be clear, my phone says "HBOOT USB PLUG" while I'm trying this.
thank you so much by the way for all your help. And you too tiny. I feel like I'm standing on the shoulders of giants here!
Also, is there some irc channel or something with a bit less idle time between forum posts?
Click to expand...
Click to collapse
Oops, i ment to put for you to type fastboot devices not adb devices in those instructions, that was just a mistake on my part. I dont think you can even access adb from hboot. As long as fastboot devices works your good to go. Also you will want to select fastboot from the bootloader menu after connecting the phone. So it should say fastboot plug in red not usb plug in blue when entering the commands.
I do not know of an irc channel, and i like to keep the conversation here so that the instructions and common issues and fixes can be seen and learned from by others.

cmlusco said:
Oops, i ment to put for you to type fastboot devices not adb devices in those instructions, that was just a mistake on my part. I dont think you can even access adb from hboot. As long as fastboot devices works your good to go. Also you will want to select fastboot from the bootloader menu after connecting the phone. So it should say fastboot plug in red not usb plug in blue when entering the commands.
Click to expand...
Click to collapse
Oh well in that case I get an entirely different issue. "Fastboot devices" works but when I try the flash command you suggested:
Code:
sending 'misc' (640 KB)...
OKAY [ 0.119s]
writing 'misc'...
FAILED (remote: not allowed)
finished. total time: 0.129s
Man, talk about frustrating.

Leshy01 said:
Oh well in that case I get an entirely different issue. "Fastboot devices" works but when I try the flash command you suggested:
Code:
sending 'misc' (640 KB)...
OKAY [ 0.119s]
writing 'misc'...
FAILED (remote: not allowed)
finished. total time: 0.129s
Man, talk about frustrating.
Click to expand...
Click to collapse
Did you unlock the bootloader with htc dev? Does it say unlocked at the top of hboot?

cmlusco said:
Did you unlock the bootloader with htc dev? Does it say unlocked at the top of hboot?
Click to expand...
Click to collapse
Yep. *** Unlocked *** in pink at the top.
HBOOT 1.07.000
And my screen says FASTBOOT USB in red. When I enter "fastboot devices" I get HT0B2HJ05729 fastboot, so I know that works. As does commans like reboot.

Leshy01 said:
Yep. *** Unlocked *** in pink at the top.
HBOOT 1.07.000
And my screen says FASTBOOT USB in red. When I enter "fastboot devices" I get HT0B2HJ05729 fastboot, so I know that works. As does commans like reboot.
Click to expand...
Click to collapse
Hmm thats strange having the boooader unlocked should allow remote. Mabey thats not allowed, i thought it was. Sorry let me dig up some info i believe there is another way.
---------- Post added at 12:44 AM ---------- Previous post was at 12:17 AM ----------
Ok download this http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img and place it on your pc where fastboot.exe is and open the cmd prompt and type:
Code:
fastboot flash recovery recovery.img
And then reboot the phone to the bootloader again and go to recovery and flash this http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip. Just for kicks see if you can mount data or cache from the mounts and storage menu. If you can your issue is probably fixed, if not try this. Download and unzip these files http://dinc.does-it.net/Guide_Root_New_Hboot/flash_mtd.zip and place both of them in the same folder on your pc as adb.exe. Then while in recovery with the phone connected open a cmd promt to where adb is and type the following hitting enter after each line:
Code:
adb push flash_image /system/
adb push mtd0.img /sdcard/
adb shell (you should get a prompt with a # sign)
cd /system
chmod 0755 /systeml/flash_image
cd /system
./flash_image misc /sdcard/mtd0.img
exit
adb reboot recovery
In recovery go to mounts and storage and mount usb storrage and place this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip on the sdcard. Then in your cmd prompt type:
Code:
adb reboot bootloader
Once in hboot, select bootloader from the menu amd wait a few secs for it to find the ruu and pronpt you to flash it.

cmlusco said:
Hmm thats strange having the boooader unlocked should allow remote. Mabey thats not allowed, i thought it was. Sorry let me dig up some info i believe there is another way.
---------- Post added at 12:44 AM ---------- Previous post was at 12:17 AM ----------
Ok download this http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img and place it on your pc where fastboot.exe is and open the cmd prompt and type:
Code:
fastboot flash recovery recovery.img
And then reboot the phone to the bootloader again and go to recovery and flash this http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip. Just for kicks see if you can mount data or cache from the mounts and storage menu. If you can your issue is probably fixed, if not try this. Download and unzip these files http://dinc.does-it.net/Guide_Root_New_Hboot/flash_mtd.zip and place both of them in the same folder on your pc as adb.exe. Then while in recovery with the phone connected open a cmd promt to where adb is and type the following hitting enter after each line:
Code:
adb push flash_image /system/
adb push mtd0.img /sdcard/
adb shell (you should get a prompt with a # sign)
cd /system
chmod 0755 /systeml/flash_image
cd /system
./flash_image misc /sdcard/mtd0.img
exit
adb reboot recovery
In recovery go to mounts and storage and mount usb storrage and place this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip on the sdcard. Then in your cmd prompt type:
Code:
adb reboot bootloader
Once in hboot, select bootloader from the menu amd wait a few secs for it to find the ruu and pronpt you to flash it.
Click to expand...
Click to collapse
So I was able to complete all your steps without getting any errors. After flashing superuser, I still couldn't format /data or /cache (mounting was never an issue - or at least I wasn't given any errors about it before) However however after flashing the stock ROM, I am still getting the bootloop. I can't check the /data and /cache partition since its no longer running CWM though, but this is the same scenario I was in previously. I'm sure I'm giving you a challange here. Is there a way to manually re-partition everything manually, instead of just formatting?
So like I said, I ran the steps provided above, and still got the bootloop. So I flashed CWM and same as before, I am unable to format the /data and /cache partitions.:/

Leshy01 said:
So I was able to complete all your steps without getting any errors. After flashing superuser, I still couldn't format /data or /cache (mounting was never an issue - or at least I wasn't given any errors about it before) However however after flashing the stock ROM, I am still getting the bootloop. I can't check the /data and /cache partition since its no longer running CWM though, but this is the same scenario I was in previously. I'm sure I'm giving you a challange here. Is there a way to manually re-partition everything manually, instead of just formatting?
So like I said, I ran the steps provided above, and still got the bootloop. So I flashed CWM and same as before, I am unable to format the /data and /cache partitions.:/
Click to expand...
Click to collapse
Im not sure. If there is a program or a way to manually fix the partitions, i am unaware and it is probably over my head.
Flashing the misc partition should have fixed any errors with the partition table. The fact that it didnt fix it leads me to believe that the partitions are fubar.
One thing bugs me though, you said earlier that you never had an issue mounting the partitions, just formating them. So can you mount data in recovery, and then view its contents or pull and push with adb?

Leshy01 said:
So I was able to complete all your steps without getting any errors. After flashing superuser, I still couldn't format /data or /cache (mounting was never an issue - or at least I wasn't given any errors about it before) However however after flashing the stock ROM, I am still getting the bootloop. I can't check the /data and /cache partition since its no longer running CWM though, but this is the same scenario I was in previously. I'm sure I'm giving you a challange here. Is there a way to manually re-partition everything manually, instead of just formatting?
So like I said, I ran the steps provided above, and still got the bootloop. So I flashed CWM and same as before, I am unable to format the /data and /cache partitions.:/
Click to expand...
Click to collapse
Parted. It already exists in recovery and can be run in adb in recovery. Try that. I can't give directions but be careful. I think I tried to help someone before with this but can't recall the thread. It'd b a good starting point.
Sent from my Galaxy Nexus using Tapatalk 2

cmlusco said:
Im not sure. If there is a program or a way to manually fix the partitions, i am unaware and it is probably over my head.
Flashing the misc partition should have fixed any errors with the partition table. The fact that it didnt fix it leads me to believe that the partitions are fubar.
One thing bugs me though, you said earlier that you never had an issue mounting the partitions, just formating them. So can you mount data in recovery, and then view its contents or pull and push with adb?
Click to expand...
Click to collapse
Well... I'm sketchy on the exact terms here, but In CWM, I can mount the drives without getting any errors, but whenI try to format I get errors. I haven't actually "done" anything with those partition besides that.
However. I ran through ALL the steps you had me to. Flash the stock ROM w/ recovery, unlocked bootloader from HTC, pushed all the filies you had me through adb. After all that, I flashed CWM, then I flashed CM7, and then I booted up my device. As if my /data partition was not touched, all my apps were still there (titanium backup, my google accounts were still setup, app data and settings were untouched). So on a whim, I ran titanium backup, and uninstalled every single user app (since the android native uninstaller force closes). I ran it successfully, rebooted, and every other app was still there.
So it can READ the /data partition, but I have no abilities to MODIFY that partition. Through any recovery or formatting.
tiny4579 said:
Parted. It already exists in recovery and can be run in adb in recovery. Try that. I can't give directions but be careful. I think I tried to help someone before with this but can't recall the thread. It'd b a good starting point.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm willing to try anything because at this point nother else works, but I don't know where to start. And even if I find some documentation about other devices' partition table setup, I'm assuming the Incredible is different. Way I see it, I can't mess it up any more than it already is.
I'm hoping you guys have some sort of answer, but I'm looking around elsewhere, and I really appreciate everything you guys have contributed to this thread, and the community. Thanks!!!!!

Hi guys,
I have the same issue (with a galaxy s2 though), anything related to the partition /data is causing me troubles since I first tried to wipe it when I wanted to install CM9.1. (and I had stock ICS 4.0.4 at the time...)
Do you think it is the mmc bug ?
I can enter DL mode but when I try to flash stock rom, it just remains at the animated boot logo for hours...
Tried also to flash rom (with CODE, MODEM, CSC) and Odin stays stuck when starting DATA...
Any luck on your side ?

megosu said:
Hi guys,
I have the same issue (with a galaxy s2 though), anything related to the partition /data is causing me troubles since I first tried to wipe it when I wanted to install CM9.1. (and I had stock ICS 4.0.4 at the time...)
Do you think it is the mmc bug ?
I can enter DL mode but when I try to flash stock rom, it just remains at the animated boot logo for hours...
Tried also to flash rom (with CODE, MODEM, CSC) and Odin stays stuck when starting DATA...
Any luck on your side ?
Click to expand...
Click to collapse
I don't think the mmc bug has anything to do with the Droid Incredible or even affects it. I thought the mmc bug led to a fully bricked phone.
This isn't really the thread for this but have you tried the full Odin Factory reset for your device which includes the /data partition? I think the method that uses a PIT file is the most thorough but most risky. I recommend posting any questions in your device's thread but I've had a few samsungs and am somewhat familiar with that process.

deleted stock rom!!

I don't know how i did this but as i was going to revert back to my stock rom via twrp recovery, my phone couldn't find the file. Somewhere along the way i ended up wiping my phone and now im stuck in recovery with no backup to restore, no zip to flash, and cant even get back to my rom. I can open recovery, and i can go into the boot-loader. Im guessing what i mainly need to do is somehow flash the stock rom using fastboot open window command from my computer, but i still cant seem to find the stock rom.
Im pretty sure the answer is somewhere in these forums but the search isn't working and iv been going through tons of pages with no answer.

Well the good thing is that you're not bricked. If you are S-OFF and know how to use adb go to the link below. Saved my life when I flashed TWRP over my boot img. I'm sorry I can't give you instructions. I just don't feel I could give you clear ones as I know just enough to get around lol. Hopefully that points you in the right direction.
http://forum.xda-developers.com/showthread.php?t=2437436
Sent from my HTC6500LVW using Tapatalk

In this situation all you should have to do is adb sideload the ROM of your choice from your computer and you'll be back in business.

projektorboy said:
In this situation all you should have to do is adb sideload the ROM of your choice from your computer and you'll be back in business.
Click to expand...
Click to collapse
what exactly is adb sideload? is that when i do the open command from adb file and do
fastboot flash zip (Rom.zip) ?

You can also use the Meenova Sd card reader to flash a rom in recovery. Once you flash the. zip you are back up and ready to go. Google Meenova and they have a thread on XDA.
Sent from my Galaxy Tab 10.1

blkoutt8 said:
I don't know how i did this but as i was going to revert back to my stock rom via twrp recovery, my phone couldn't find the file. Somewhere along the way i ended up wiping my phone and now im stuck in recovery with no backup to restore, no zip to flash, and cant even get back to my rom. I can open recovery, and i can go into the boot-loader. Im guessing what i mainly need to do is somehow flash the stock rom using fastboot open window command from my computer, but i still cant seem to find the stock rom.
Im pretty sure the answer is somewhere in these forums but the search isn't working and iv been going through tons of pages with no answer.
Click to expand...
Click to collapse
I did this the first week I bought the phone.
No S-OFF, no RUU. Very scary, but luckily I had @hawknest to guide and save me.
First thing to do is relax, and know your phone is not damaged in anyway and can be recovered quite easily.
The HTC DNA users experienced this as well, so this is nothing new to them.
TWRP houses an "adb sideload" option and it's very easy to use.
or you can adb push the ROM.zip to your internal memory.
I prefer the adb sideload.
If you need help, I will teamview with you (which means I can basically control your computer so I can run the commands) you just need to be there doing what I say.
Hope you get this fixed, it's really dumb how TWRP has it set up for failure like this, and I've tried bringing to their attention but that's a story I will not get into. PM me for help.

andybones said:
I did this the first week I bought the phone.
No S-OFF, no RUU. Very scary, but luckily I had @hawknest to guide and save me.
First thing to do is relax, and know your phone is not damaged in anyway and can be recovered quite easily.
The HTC DNA users experienced this as well, so this is nothing new to them.
TWRP houses an "adb sideload" option and it's very easy to use.
or you can adb push the ROM.zip to your internal memory.
I prefer the adb sideload.
If you need help, I will teamview with you (which means I can basically control your computer so I can run the commands) you just need to be there doing what I say.
Hope you get this fixed, it's really dumb how TWRP has it set up for failure like this, and I've tried bringing to their attention but that's a story I will not get into. PM me for help.
Click to expand...
Click to collapse
I think I pretty much got it. Except just trying to figure out how exactly adb sideload works...is that when I'm in the adb folder doing the open command window to flash my zip?

blkoutt8 said:
I think I pretty much got it. Except just trying to figure out how exactly adb sideload works...is that when I'm in the adb folder doing the open command window to flash my zip?
Click to expand...
Click to collapse
Yes I do believe that sounds correct.
If you don't already know, here is the command
adb sideload /path/to/rom.zip - (rename whatever ROM you are moving over to rom.zip)
Hope to hear you are out of that mess soon, it should never of been set up like that anyway with system where it is.
I have been SOO careful ever since, haha.

blkoutt8 said:
what exactly is adb sideload? is that when i do the open command from adb file and do
fastboot flash zip (Rom.zip) ?
Click to expand...
Click to collapse
No!
adb commands are performed in completely separate places than fastboot commands. adb.exe is completely separate from fastboot.exe. They both help to modify the phone but they depend on completely different conditions to function correctly.
adb.exe commands = when booted into Android & when enabled in recovery
fastboot.exe commands = when fastboot mode is chosen after you've booted to the bootloader (HBOOT screen).
Assuming you're able to install a custom recovery via fastboot, you can boot into that recovery and perform the adb sideload.
Also the "fastboot flash zip" command can only be invoked after you get to the bootloader, go to fastboot mode, and then do 'fastboot oem rebootruu' which is definitely not the typical way for modifying recovery unless you're pushing in a new radio, hboot, or an entire RUU.

projektorboy said:
No!
adb commands are performed in completely separate places than fastboot commands. adb.exe is completely separate from fastboot.exe. They both help to modify the phone but they depend on completely different conditions to function correctly.
adb.exe commands = when booted into Android & when enabled in recovery
fastboot.exe commands = when fastboot mode is chosen after you've booted to the bootloader (HBOOT screen).
Assuming you're able to install a custom recovery via fastboot, you can boot into that recovery and perform the adb sideload.
Also the "fastboot flash zip" command can only be invoked after you get to the bootloader, go to fastboot mode, and then do 'fastboot oem rebootruu' which is definitely not the typical way for modifying recovery unless you're pushing in a new radio, hboot, or an entire RUU.
Click to expand...
Click to collapse
Ok, so how can I flash a .zip or ROM to my phone now through adb sideload? or push a ROM to my internal memory. I just relocked thevbootloader tho in an attempt to flash the RUU .zip that did not work for me.

Which RUU zip did you try using? There are two versions of the RUU that have been posted. Decrypted and Encrypted. Since you re-locked your bootloader I hope you went for the Encrypted version.

blkoutt8 said:
Ok, so how can I flash a .zip or ROM to my phone now through adb sideload?
Click to expand...
Click to collapse
If you have CWM or TWRP installed, you'll have an option for ADB Sideload for a ROM. You don't even have to push a ZIP to the phone. The phone will take the ZIP on the fly.
In CWM, while connected to your computer" you just choose "Install ZIP" > "Install ZIP from Sideload" which will make the device present in ADB
{
"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"
}
After doing the sideload command from your command prompt the phone will start flashing the ZIP as if it were locally stored.

projektorboy said:
If you have CWM or TWRP installed, you'll have an option for ADB Sideload for a ROM. You don't even have to push a ZIP to the phone. The phone will take the ZIP on the fly.
In CWM, while connected to your computer" you just choose "Install ZIP" > "Install ZIP from Sideload" which will make the device present in ADB
After doing the sideload command from your command prompt the phone will start flashing the ZIP as if it were locally stored.
Click to expand...
Click to collapse
Well that helps! Because I am using the decrypted version. I can't find an encrypted one. I found this other file called
PN07IMG_M7_WL_JB_50_VZW_422_VERIZON_WWE_1.10.605.10_Radio_1.12.42.0906_NV_VZW_3.71_002_release_334098_signed_2.zip
and also I am using TWRP

Being you have TWRP, just boot into recovery and select Advanced->Sideload ADB. Now plug your phone into your computer, run adb, and run: adb sideload (zip file name). It should copy the zip to your internal storage.

If you can get into Recovery. You can mount your internal storage and just copy/paste the ROM through your PC to your phone.

blkoutt8 said:
Well that helps! Because I am using the decrypted version. I can't find an encrypted one. I found this other file called
PN07IMG_M7_WL_JB_50_VZW_422_VERIZON_WWE_1.10.605.10_Radio_1.12.42.0906_NV_VZW_3.71_002_release_334098_signed_2.zip
and also I am using TWRP
Click to expand...
Click to collapse
just to be clear. if you're using adb sideload or adb push - as per everyone's instructions - you want to use a rom zip, NOT the RUU zip!
(correct me if i'm wrong here)
so if you want to flash stock get santod's stock rom from the first post here:
http://forum.xda-developers.com/showthread.php?t=2485319
otherwise use any of the roms from the verizon htc forums

XPEric said:
Being you have TWRP, just boot into recovery and select Advanced->Sideload ADB. Now plug your phone into your computer, run adb, and run: adb sideload (zip file name). It should copy the zip to your internal storage.
Click to expand...
Click to collapse
Cares said:
If you can get into Recovery. You can mount your internal storage and just copy/paste the ROM through your PC to your phone.
Click to expand...
Click to collapse
Well, I was on the wrong forum and I relocked my bootloader. I can still go into recovery tho, but my computer seems to freeze. ugh this is crazy, Ive about had it. I wish my windows 8.1 would just recognize the phone, I'm stuck using my moms old laptop

One could also flash santods stock rom through fastboot.
Fastboot oem rebootRUU
Fastboot flash zip nameoffile.zip
It will fail the first time and say something about flushing the image. Just repeat the process and it will work on second round.
Once it's finished just type
Fastboot reboot

Attempted to root, maybe bricked, can I recover?

Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!

enjoyingsilence said:
Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!
Click to expand...
Click to collapse
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.

monster1612 said:
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.
Click to expand...
Click to collapse
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.

enjoyingsilence said:
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.
Click to expand...
Click to collapse
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?

monster1612 said:
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?
Click to expand...
Click to collapse
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.

enjoyingsilence said:
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.
Click to expand...
Click to collapse
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.

monster1612 said:
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.
Click to expand...
Click to collapse
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.

enjoyingsilence said:
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.
Click to expand...
Click to collapse
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.

monster1612 said:
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.
Click to expand...
Click to collapse
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!

enjoyingsilence said:
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!
Click to expand...
Click to collapse
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)

monster1612 said:
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)
Click to expand...
Click to collapse
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
edit: Found the latest CM ROM and Gapps files. Just need options for full recovery back to FireOS if needed in the end.

enjoyingsilence said:
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
Click to expand...
Click to collapse
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.

monster1612 said:
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.
Click to expand...
Click to collapse
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.

enjoyingsilence said:
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.
Click to expand...
Click to collapse
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...

enjoyingsilence said:
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...
Click to expand...
Click to collapse
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.

monster1612 said:
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.
Click to expand...
Click to collapse
Thanks. I was able to update twrp and get the 23rd of Dec's nightly CM12 build installed. It didn't seem to work properly though, and gapps wouldn't install. So I've resigned to the fact that I need to put the original OS back on it. After updating twrp, this doesn't seem possible. When I connect it to the computer, all I'm getting is error: device offline when typing adb shell. This is in linux and windows.
I tried connecting it and mounting the usb storage, then dragging over the fireos images, but after installation it went into this reboot loop due to a corrupt something or other... Now, I can't get cm or the original os back on it.

So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?

enjoyingsilence said:
So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?
Click to expand...
Click to collapse
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!

monster1612 said:
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!
Click to expand...
Click to collapse
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.

enjoyingsilence said:
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.
Click to expand...
Click to collapse
Do you have adb installed system-wide? If you do, try cd'ing to the directory where you placed the boot, recovery, and system images and then running those commands again. If you don't, then move the files to the folder where the adb and fastboot executables are located and run the commands in that folder.

Soft Brick, couldn't flash anything, now can't mount anything

When I boot to twrp in recovery, I am unable to accomplish anything -- wipe or install. When I try to do either I get an error about "unable to mount sdcard". I have seen this thread, but cannot find the zip mentioned anywhere. I am able to run "adb push" to /sdcard and then to actually see the file pushed there in twrp recovery. I'm just not able to do anything with the pushed file in the install function.
Tried mounting with adb shell, but kept getting error of "Invalid argument". Did discover that /sdcard is /dev/block/mmcblk0p36, and using fdisk in adb shell found that it "doesn't contain a valid partition table". I'm not concerned about losing data. Everything was backed up, but anybody know how to create the correct partition table so I can install a ROM?
Original post:
So I screwed up. I rooted my phone according to this post. Unfortunately I then did something stupid when trying to flash a new recovery and get actual SU privileges to remove bloatware. Instead of going back to the first page in that thread and seeing the links to use there, I followed this guide. Unfortunately, when I ran the script, install-insecure-linux.sh, it flashed the boot.insecure.img and then spit out errors related to incompatibility with the ncurses version on my laptop. It seems difficult if not impossible to downgrade the ncurses without causing a ton of other headaches. It went to reboot and just stayed dead.
Thought I was hosed, but then after charging for a while I got signs of life. Managed to boot to fastboot. Connected back up to the laptop and decided to follow the cyanogenmod guide for installing CM11. Flashed the CM recovery img file successfully but after rebooting I can't do anything.
I still occasionally get into the fastboot on the phone. Running fastboot devices on the laptop lists the phone. Running adb devices does not. Running any other fastboot command sticks at either nothing or <waiting for device>. Running any adb command gives "error: Device not found". I added a udev rule and adb_usb.ini with the device id "0bb4" and mode 0666, but no joy.
I only have a linux machine available at the moment, so I'd prefer suggestions for working in linux. If someone knows of a good Windows solution, I can probably try that in a few days. Thanks in advance.
EDIT: Progress
Noticed that for a second when I first connect to the laptop USB the fastboot menu showed in red FASTBOOT USB before going back to just FASTBOOT. Managed to tee up the command for flashing the twrp recovery img and ran it immediately upon plugging in. Was then able to boot to recovery. Not sure what my next step to getting a working phone is though. Help still appreciated.

My last post got swallowed by the ether I guess. I was able to fix it by formatting the sdcard using mkdosfs -F 32 -n INT_SD -s 64 /dev/block/mmcblk0p36. Then rebooting, wiping, and installing CM11. All is good again.