Develop Bugs

Dead USB port and MicroSD slot

So today, I was upgrading from modaco 2.7 to 2.7.1,
after the upgrade (using recover mode and the signed zip file (core chinese)), I did a system wipe and reboot the device with the USB still plugged in my PC, and everything seems to be normal until my pc's tray notification pops up with the "unknown device found" message - i thought it was a little bit odd, so then I waited for the hero to boot up completely - it reboots after showing the HTC logo once, and then it boots normally to the setup wizard (select language, etc);
I then followed the normal procedure of typing all the wifi, flickr, gmail stuff in, and when i got into Rosie, it shows a notification icon on the hero saying "SD Card removed". I can't access the SD card, nor my pc can recognize the hero. I ejected the SDCard and re-insert it but it's not detected either. HTC Sync on the device does not give a notification nor the mass storage notification shows up either.
I tried rebooting into recovery mode, (Hero 1.2.3) and i can see the menus just fine; however, when i try to mount SD card as usb, or flash update.zip or any zip, or fix ext3, or clear dalvik-cache or wipe the sdcard's ext partition, it keeps giving me errors saying
error: run 'whateverprogram' in terminal
when i try to set 'USB Mass storage on', it says "Error enabling USB mass storage! Run ums_enable manually from console.
I then try to login the device using adb shell through window's command prompt, it says device not found as well.
giving up, i tried to reboot teh device into fastboot mode, the PC recognizes the USB device just fine. it's really odd.
Anyway I can do a recovery on this to make these device work again?
p.s. when i try to choose zip file in recovery mode, it says
Code:
"E: Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)
Can't mount sdcard, aborting".
after every reboot (shutdown, start), the setup wizard shows up again as if I have not written anything on my device after any setup.
I can't download anything to run on the Hero as it requires the SD card. I can't flash any recovery images either as again it requires the SD card.
Any ideas??? I'm left with a half-brick now

Update1: using ConnectBot I can login my own device using root,
it shows the following when i run df -h:
Code:
/dev/block/mtdblock3 1700M 157.3M 12.7M 93% /system
/dev/block/mtdblock5 165.8MB 12.8M 152.9M 8% /data
/dev/block/mtdblock4 130.0M 1.2M 128.8M 1% /cache

kazuni,
Can you read SD card in your PC?
Several persons reported problems with SD card after upgrading to modaco 2.7 or 2.7.1. They have to format SD card.

Al936 said:
kazuni,
Can you read SD card in your PC?
Several persons reported problems with SD card after upgrading to modaco 2.7 or 2.7.1. They have to format SD card.
Click to expand...
Click to collapse
Thanks for the quick reply.
I have tried doing so, in fact, i have 4 SD cards to try and none of them are readable in the Hero; they are readable using a card reader in my PC though.

kazuni said:
Thanks for the quick reply.
I have tried doing so, in fact, i have 4 SD cards to try and none of them are readable in the Hero; they are readable using a card reader in my PC though.
Click to expand...
Click to collapse
Update2: the only way that my pc can detect my device as "My HTC" is when i boot it into fastboot mode; unfortuantely there are no way for me to update the device in this mode, so i can't do anything to modify the rom, or to check it using dropbear or any shell client. =\
C:\Documents and Settings\user>fastboot devices
HT97RL900725 fastboot
it sees it just fine.
I wonder if the goldcard method + fastboot update will work or not; let me give it a shot and try to flash it back to 405.5 first ;\
update3: can't. fastboot update is still locked for any rom type.

damn man. its freaking. i am not going to update to 2.7.1 untill this issue is resolved.

still no go.
im left with a half-bricked device that:
1) clean wiped, normal boot, cannot detect SD card nor the Hero is detectable by XP.
2) clean wiped, recovery mode, can't run any of the script except :
Reboot System Now
Wipe data/factory reset
Fix apk uid mismatches
Fix rotate
3) can't download anythign from browser as it needs to save onto sd card.
4) android market doesn't have flashrec so i can't reinstall the recovery image.

wget ftp://myhost/system.img /data/
flash_image system /data/system.img
hope this works

When you are in the shell check out the file /proc/cmdline.
Would be interresting to see if the HBOOT send a command line to the kernel to disable the SD card.

packetlss said:
When you are in the shell check out the file /proc/cmdline.
Would be interresting to see if the HBOOT send a command line to the kernel to disable the SD card.
Click to expand...
Click to collapse
can't. It doesn't even boot into normal mode, nor boot loop. it just holds at the HERO logo.

I think I have the same problem, i can charge my phone but trying to mount my phone to either my pc or mac it just won't be picked up

tried using RUU with a goldcard, no go. remote not allowed (fastboot flash system system_rel.img, nor fastboot boot boot.img or fastboot flash boot boot.img. no go. sigh.)
now i have a brick :\
wonder if there is any way to go into fastboot mode and flash ANY part of the blocks (device, recovery, or system, if at all).

Some progress: using hboot mode, i placed HEROIMG.zip into the sdcard and it loads successfully. it works! and im now rolled back to official 2.7.405.5; however, the USB and the sd card is still dead ;\

I guess I'll be bringing it back to HTC to see if they would do anything about it (fortunately It's now back to stock recovery and 2.74.405.5)

I managed to do the same thing, i'm hoping the tmobile will replace my phone

hi all,
I am having the same issue... what I don't understand is: it has to be a software problem, because, from what I've read, everyone of us have been installing radio and firmware updates to the htc hero, and since some of these updates the USB and sdcard mounting is not properly working... I believe it's not possible to break a USB port just by installing software...
so there should be a way to fix this other than sending the phones back... If anyone has any suggestion I can try it on my phone
cheers : )

I know it's weird! Funny thing is, official updates includes radio + recovery + pretty much every part of the rom is being re-flashed (including hboot, from what i understand); how ever, ONLY in hboot mode, the device is recognized properly as "Android USB" by windows.

Some of your problems I had to. To be exact: that my pc wouldn't recognize the phone when connected with usb except for fastboot and charging.
For weeks I searched and found some people with similar problems, but never a solution.
I had no problems with my sdcard however.
Now my problem is gone. How? I had the HTC Generic 2.73.405.5 ROM (pre-rooted and packaged as update.zip by MoDaCo) and decided to update to Paul's ROM v2.5.
After I was finished with the installation wizard and connected the phone with usb to my pc everything suddenly worked again!!!
So I got the usb and HTC Sync notification at the top of the screen and can mount the sdcard using the notification bar.
This tells me that in my case it definately wasn't a hardware problem as I always thought, but a software one.
I hope you can something with my experiences because I know how frustrating it is when this doesn't work!

dennis333 said:
Some of your problems I had to. To be exact: that my pc wouldn't recognize the phone when connected with usb except for fastboot and charging.
For weeks I searched and found some people with similar problems, but never a solution.
I had no problems with my sdcard however.
Now my problem is gone. How? I had the HTC Generic 2.73.405.5 ROM (pre-rooted and packaged as update.zip by MoDaCo) and decided to update to Paul's ROM v2.5.
After I was finished with the installation wizard and connected the phone with usb to my pc everything suddenly worked again!!!
So I got the usb and HTC Sync notification at the top of the screen and can mount the sdcard using the notification bar.
This tells me that in my case it definately wasn't a hardware problem as I always thought, but a software one.
I hope you can something with my experiences because I know how frustrating it is when this doesn't work!
Click to expand...
Click to collapse
I tried this but it didn't seem to work for me, so I just put the official rom update and sent the phone back to my network saying that it was broken, now i've gotta wait for another 2-3 weeks to get my phone back , but i'm hoping they'll give me a new phone as i did kinda drop it and there two scuff marks on it

hello dennis333,
today I tried going from 2.8 to the HTC generic ROM you told, and then to 2.5. no results.
I also installed the official HTC / Orange Rom update, which I have now. It has improved a bit because now when I plug the USB cable the PC detects something, but it does'nt work... it says 'unknown device' (tried this on two computers)
when I boot to fastboot ( BACK + POWER BTN ) my computer detects Hero ok (My Htc)
I really don't know what else to try...
I saw another post from someone who had the exact same problem and got it fixed by installing SPL and ROM from fastboot menu
http://forum.xda-developers.com/showthread.php?t=556038
I tried it too, but when trying to use the SPL zip file he says I get an error ( I guess it's because he has a T-Mobile and I have an Orange Hero)
[update]: I finally got the SPL to flash correctly and then installed a modaco 2.8 ROM, but I still cannot connect the Htc Hero to the PC via USB.
regards

Bricked Kindle Partitions corrupted

After trying to do a factory reset with the latest CWMR, my kindle no longer mounts any of the partitions. I have been able to view the folders when directly loading TWRP through fastboot, but fastboot oem format doesnt work, nor does firekit usb tools, nor rekindle, and yes I've tried the short into usbboot mode method. The kindle was fully functional this morning until trying to do a factory reset.
Unfortunately, I missed the little one line blurb buried in the CWM dev post about not doing this, but it completely ruined all adb partitioning functions. I can access an adb shell and fastboot, but no repartition tools are working. This includes the entire thread about reformatting each partition http://forum.xda-developers.com/showthread.php?t=1388996
Nearly every command I issue in parted, when booting from fastboot directly into cwm, hangs, and I have to ctrl+c out of it.
I do not know where else to turn at this point. It seems like I need to completely wipe the emmc, but it won't respond to any commands required to do this.
I checked the emmc type, I forget the post, and it was not the type affected by the one-time-write bug.
Does anyone have any ideas on how to reformat the kindle from the ground up, becuase that's the only thing left... basically ripping out the memory chip and erasing it.

I am on the same page as you, others are too
Dont know what to do, i live in brazil and will cost as much as a new kindle to send it to repair.
I am thinking about formating the /dev/block/mmcblk0 in ext4 but dont know if it will make things even worse.

I thought about asking for fastboot images and flashing all the partitions through that, but I'm not sure that would work because the partition table is still ruined beyond repair.
edit:
if we completely erase the emmc, can it still do a usbboot shorting the pin to ground? then maybe the partition table would take.

Do you think the eMMC is the problem? I think its only the partitions, maybe the master /dev/block/mmcblk0 is corrupt and the other are too.
If you try to Mount USB Storage on TWRP or CWR, it will say, at least on mine, that the windows needs to format the storage and if you agree, it dont recognize the size of the partition

I have read a few threads where others have gone ahead and let windows format their SD card it seems they had good results I don't know how this pertains to the problem you guys are having maybe the only recourse is to buy another motherboard sadly I will dig around later to see if I can find a solution.

I never got it to mount the usb partition, but I agree, it's definitely partition table related. Under adb shell I can view all the files on there that should be there, specifically the ones I downloaded. Not sure what I could do from here, since installing anything would be moot anyway without partitions to install to.
Can you run an adb shell? What is the result of running 'fdisk /dev/block/mmcblk0' ? My shell just hangs until i ctrl-c out of it. The problem with this whole situation is that every tool that could possibly format the disk just hangs when used...

have you read through this thread? http://forum.xda-developers.com/showthread.php?t=1654498
---------- Post added at 12:35 AM ---------- Previous post was at 12:32 AM ----------
the nipad rom might have some rescue for you only issue its in chinese.

Already a dozen times
My fdisk returns this
~ # fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
fdisk: can't read from /dev/block/mmcblk0
I think we need to format the master partition, /dev/block/mmcblk0
if we could do this, maybe we have a chance i think, but dont know if doing this it will screw everything up
fastboot oem format runs in about 0.6 seconds and returns success. Tried Firekit too, samething

[Q] Bricked Kindle Fire?

Hello all. I sincerely hope one of you can help me.
I was trying to install a ROM onto my Kindle Fire but now I believe I have bricked my device. I ran into the issue where the Kindle does not have enough battery life to boot after I had flashed TWRP so I waited until it charged and then tried flashing the ROM a few times. Now it says that the internal SD card is unmounted and it will not boot properly either (a la the minimal battery life issue). I have tried mounting the SD card through TWRP to no avail. Any help would be greatly appreciated!!

arjunvenkawhat said:
Hello all. I sincerely hope one of you can help me.
I was trying to install a ROM onto my Kindle Fire but now I believe I have bricked my device. I ran into the issue where the Kindle does not have enough battery life to boot after I had flashed TWRP so I waited until it charged and then tried flashing the ROM a few times. Now it says that the internal SD card is unmounted and it will not boot properly either (a la the minimal battery life issue). I have tried mounting the SD card through TWRP to no avail. Any help would be greatly appreciated!!
Click to expand...
Click to collapse
What happens when you try to boot up your kindle?

It first shows the FFF boot screen then boots into TWRP even without me manually selecting boot into recovery. If I choose to boot into system in TWRP then it goes into a bootloop which I can get out of by booting into recovery and then shutting down in TWRP.

you didn't happen to create a nandroid backup before attempting to flash this new ROM, did you? Also, What happens when you plug your kindle into your computer?

nschiwy said:
you didn't happen to create a nandroid backup before attempting to flash this new ROM, did you? Also, What happens when you plug your kindle into your computer?
Click to expand...
Click to collapse
Unfortunately I did not. Also, the Kindle is not recognized by the computer even as an external hard drive.

arjunvenkawhat said:
Unfortunately I did not. Also, the Kindle is not recognized by the computer even as an external hard drive.
Click to expand...
Click to collapse
Any suggestions guys? I'm at my wits end over here!

How much battery left does TWRP report?
While you're on TWRP, what's the output of the file partitions.txt? (type the following to obtain it)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Also, what versions of FFF and TWRP do you have installed?

just on the off chance, in the mount menu in twrp you should only have sdcard ticked

lovejoy777 said:
just on the off chance, in the mount menu in twrp you should only have sdcard ticked
Click to expand...
Click to collapse
I keep trying to tick off SDcard in TWRP but it won't even let me. When I do, it says "E:failed to mount /sdcard (Invalid argument.)
However, I am able to access /sdcard (I believe) on the file manager.

Dasanko said:
How much battery left does TWRP report?
While you're on TWRP, what's the output of the file partitions.txt? (type the following to obtain it)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Also, what versions of FFF and TWRP do you have installed?
Click to expand...
Click to collapse
I have FFF v.1.4a and TWRP v 2.1.1. TWRP says I have 95% battery left. I will look up a guide on how to use adb and try the command you suggested.

sdcard is the one you need ticked not unticked on mine I have a check in sdcard and in cache no checks in system and data select mount works fine.

Thepooch said:
sdcard is the one you need ticked not unticked on mine I have a check in sdcard and in cache no checks in system and data select mount works fine.
Click to expand...
Click to collapse
I understand that I need sdcard checked. However, it will not allow me to check the sdcard.

arjunvenkawhat said:
I understand that I need sdcard checked. However, it will not allow me to check the sdcard.
Click to expand...
Click to collapse
Its an extreme measure but To mount your sdcard:Boot into recovery and enter...adb shell (hit enter) echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file (hit enter)And if you have to, format your sdcard FAT32 block size 4096 Obviously, by formatting your sdcard, you will lose all the data that's on it. Very likely you won't have to format
---------- Post added at 02:36 AM ---------- Previous post was at 02:33 AM ----------
Good luck

S3 Won't Boot Properly

I am running my S3 on TMO, with 4.3 booloader & latest modem. I was also running a 4.3.2 TW rom.
This morning, I decided to wipe the rom, then restore it, as it was the one I had in backup. I was having stuttering problems, and thought that because I had added & deleted so much stuff in the past few days, restoring my clean backup would clear it up.
I have the latest TWRP recovery, and wiped the cache & dalvik, then went to restore the rom. But when it finished, and I rebooted, got stuck at the ktoonez (my kernel) logo. I did a battery pull, and went back into recovery, did a full wipe, then tried to restore the rom. This time, 3/4 of the way through, it rebooted on its own, and started to bootloop. When I tried to get back into recovery, it would only boot to the Samsung logo, so I knew that now my recovery was gone. I used Odin on my PC to restore it, but it does the same thing. I do a complete wipe, restore the backup, but it again reboots by itself out of recovery about 3/4 of the way through, then it gets stuck at the kernel logo.
I don't have anything other than the backup stored on the phone. Is there a way that I can load a rom from my PC through recovery so that I can just start over? Or will I probably have to Odin everything back to stock, and start from there (which I've never done from the PC. I have used mobile odin though)?

Update:
I decided to do a odin back to stock. Now though, after setting for a few minutes, it says optimizing apps, goes through it, gets to the little android guy shooting upwards, goes to the Samsung logo, then starts all over again. It just keeps going through it again & again.

anyone?

Did you go into recovery and do a factory reset?
Sent from my SGH-M919 using Tapatalk

serio22 said:
Did you go into recovery and do a factory reset?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Yes, a couple times.
I have also tried taking the card out the phone and putting it into the pc to manually place the rom on it, then flash it, but my pc wont see the card. It makes the sound that something has been inserted to a usb port, but shows nothing on the computer.

What if you flash a recovery and then a ROM?
Sent from my SGH-M919 using Tapatalk

Kamau54 said:
Update:
I decided to do a odin back to stock. Now though, after setting for a few minutes, it says optimizing apps, goes through it, gets to the little android guy shooting upwards, goes to the Samsung logo, then starts all over again. It just keeps going through it again & again.
Click to expand...
Click to collapse
In TWRP recovery there is an option to sideload a file. Go to Advanced>ADB Sideload. From here you should be able to use the command:
Code:
adb sideload location/of/ROM.zip
This should transfer the ROM to your internal sd card.
You should make sure that your computer detects the phone before the transfer with the command:
Code:
adb devices
It should should return:
Code:
List of devices attached
phone id recovery
If it returns the above, you know you're okay to transfer. If it doesn't show your phone's model, that means that the computer doesn't recognize your phone as being detected (probably driver related); therefore, your file will not transfer with the sideload command.
I saw your post in the S3Rx thread that your computer won't read your sd card either. I'm not sure if you're using Windows/OSX/Linux, but if you're using Windows, you might want to try installing Linux on a USB drive, booting from that, then plugging in your sd card. In the past, I have had success mounting drives on Linux that would not mount on Windows. I know that this is a little more effort than is probably necessary lol. But I'm not nearly as versed as others here. I just like to tinker a little.
I hope you're able to get your phone booting again!

serio22 said:
What if you flash a recovery and then a ROM?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
The phone doesn't have a rom to start with I don't think. This is what I Odin:
http://www.androidfilehost.com/?fid=23212708291682181
It's the right one, as I have the TMO S3, and I already had it on my phone to begin with. I thought it came with the stock rom included, but when I rebooted, it just gets caught in a bootloop after it says optimizing apps. I can get the recovery back, but I don't know how to get a rom on the card to flash. I even tried to use a old card, but again, my pc won't see it, so I can't put a rom on it to flash.

VolcanicSkunk said:
In TWRP recovery there is an option to sideload a file. Go to Advanced>ADB Sideload. From here you should be able to use the command:
Code:
adb sideload location/of/ROM.zip
This should transfer the ROM to your internal sd card.
You should make sure that your computer detects the phone before the transfer with the command:
Code:
adb devices
It should should return:
Code:
List of devices attached
phone id recovery
If it returns the above, you know you're okay to transfer. If it doesn't show your phone's model, that means that the computer doesn't recognize your phone as being detected (probably driver related); therefore, your file will not transfer with the sideload command.
I saw your post in the S3Rx thread that your computer won't read your sd card either. I'm not sure if you're using Windows/OSX/Linux, but if you're using Windows, you might want to try installing Linux on a USB drive, booting from that, then plugging in your sd card. In the past, I have had success mounting drives on Linux that would not mount on Windows. I know that this is a little more effort than is probably necessary lol. But I'm not nearly as versed as others here. I just like to tinker a little.
I hope you're able to get your phone booting again!
Click to expand...
Click to collapse
I am on a windows, and have only used the command prompt once a couple years ago, so my experience with it is limited.
But when I tried the command "adb devices", I got an error message saying that it was not a recognized command .
Also, What is Linux? If it is bigger than a couple gigs, then I don't have any place to put it.

Kamau54 said:
I am on a windows, and have only used the command prompt once a couple years ago, so my experience with it is limited.
But when I tried the command "adb devices", I got an error message saying that it was not a recognized command .
Also, What is Linux? If it is bigger than a couple gigs, then I don't have any place to put it.
Click to expand...
Click to collapse
The reason you get the "adb is not a recognized command" is because you don't have the Android Software Development Kit (SDK) installed. The SDK contains an executable command called Android Debug Bridge (adb). You can download and install it from the developer.android.com website. But chances are, you aren't going to have the drivers installed for your computer to recognize your phone in recovery if you don't have the SDK already installed.
If you aren't familiar with Linux, then I would say that going with that route is far more work than you're likely to want to put in to get your phone functioning.
If you'd like to try it though:
Linux is free to use, it is designed and compiled by several different companies. The more well known are: Ubuntu, Mint, Red Hat, and Backtrack. There are many more.
You can visit any of those sites, download the software, and install it on a USB drive. It usually requires a 4GB USB drive. Instructions to install it to a USB drive are usually listed on the site.
After installing it, you can boot your computer from the USB and use Linux like a fully functioning OS right from the USB drive. You won't be required to install it.
You can then try downloading the ROM while on Linux and transferring it to your sd card.
Sidenote:
Linux is an open source operating system on which Android is based. That is why Android is open source, it is ruled by the same GNU General Public License that governs Linux.

VolcanicSkunk said:
The reason you get the "adb is not a recognized command" is because you don't have the Android Software Development Kit (SDK) installed. The SDK contains an executable command called Android Debug Bridge (adb). You can download and install it from the developer.android.com website. But chances are, you aren't going to have the drivers installed for your computer to recognize your phone in recovery if you don't have the SDK already installed.
If you aren't familiar with Linux, then I would say that going with that route is far more work than you're likely to want to put in to get your phone functioning.
If you'd like to try it though:
Linux is free to use, it is designed and compiled by several different companies. The more well known are: Ubuntu, Mint, Red Hat, and Backtrack. There are many more.
You can visit any of those sites, download the software, and install it on a USB drive. It usually requires a 4GB USB drive. Instructions to install it to a USB drive are usually listed on the site.
After installing it, you can boot your computer from the USB and use Linux like a fully functioning OS right from the USB drive. You won't be required to install it.
You can then try downloading the ROM while on Linux and transferring it to your sd card.
Sidenote:
Linux is an open source operating system on which Android is based. That is why Android is open source, it is ruled by the same GNU General Public License that governs Linux.
Click to expand...
Click to collapse
Sounds like I'm screwed then. I don't know why my pc is not seeing it now, because it always sees it when I'm copying files from & to it.

Kamau54 said:
Sounds like I'm screwed then. I don't know why my pc is not seeing it now, because it always sees it when I'm copying files from & to it.
Click to expand...
Click to collapse
Have you tried going to your computer's device manager and seeing if it's picking it up, but just has an error?

VolcanicSkunk said:
Have you tried going to your computer's device manager and seeing if it's picking it up, but just has an error?
Click to expand...
Click to collapse
When I insert it, and go to that, it shows up as removable disk E, but when I double click on it, it says to insert a disk into removable disk E. I think whats happening is that it's seeing the adapter, but not the card that's in it.

Kamau54 said:
When I insert it, and go to that, it shows up as removable disk E, but when I double click on it, it says to insert a disk into removable disk E. I think whats happening is that it's seeing the adapter, but not the card that's in it.
Click to expand...
Click to collapse
When you right-click on the E:/ do you have the option to format the drive? If so, you may want to try formatting it. That may fix your issue. Hopefully you don't have anything on the external sd that you can't put back on it.

VolcanicSkunk said:
When you right-click on the E:/ do you have the option to format the drive? If so, you may want to try formatting it. That may fix your issue. Hopefully you don't have anything on the external sd that you can't put back on it.
Click to expand...
Click to collapse
When I try that, it tells me there's no disk in drive E, to insert a disk and try again.

VolcanicSkunk said:
Have you tried going to your computer's device manager and seeing if it's picking it up, but just has an error?
Click to expand...
Click to collapse
This happened to me to after I installed the latest s3rx Rom...I haven't been able to recover my data or get anything to read my card.
After researching online a lot of people have had success running the chkdsk command... check it out here
http://www.ehow.com/how_7233441_restore-damaged-memory-stick-data.html

Ok, under Device Manager, the computer does see the phone as "MTP". I tried the troubleshooting process, and it went all the way through its thing, but at the end it said "failed" trying to install drivers. I just installed the proper drivers earlier today from Samsung, so I know they are correct. Also, this is as I am connected to the phone, not the card reader. The phone itself is flashing the Samsung logo, and that's as far as it has gone.
This is so frustrating because all I need to do is to get a rom onto the card. If I can get that, I can get into recovery and straighten this all out.

Anyone else with any ideas? I'm beginning to go a bit nuts thinking I have lost my phone just because I can't get a rom placed on my card.

Flash twrp or cwm, they have options to mount SD card, after that you can copy the zip and flash
Sent from my SGH-M919 using Tapatalk

serio22 said:
Flash twrp or cwm, they have options to mount SD card, after that you can copy the zip and flash
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I have the latest twrp, and have seen that option. You mean, I can copy from the pc to the card, because that's what I need to do.

Origional Kindle Fire & TWRP -> Lost all OS wont boot regular... HELP!!

I have a Kindle Fire 2011 1st gen. I got TWRP on it and had a hell of a time trying to get a ROM flashed or anything like that. I did follow a write up on here how to root it, and it worked. But it was still kindle and just looked like android. So i tried to flash CM11.... I accidently deleted the partition with everything on it, and flashed CW11 but i used OtterX, and it wont boot. I have a fast boot cable, but I cant get the PC to recognize its plugged in so i can get anything on it and try to flash again. What can i do? How do i fix this?!? Please help me!!

It was still kindle and just looked like android? All you're doing when you flash a rom is putting standard android on it, so it should look like android. If the fast boot cable you're referring to is a custom order "factory" cable it won't let you transfer a rom, the point of the cable is for bad issues that won't let you boot back into recovery. I'm guessing you didn't delete the partition since you're wanting to copy a rom over, you just formatted it and erased the rom file, correct? Use a standard usb cable, micro b, that fits the kindle. Plug it in. Boot the kindle into recovery. Find the option in recovery to "mount usb" or "mount mass storage". This will show it on the pc as a mass storage device you can copy a rom to. If however you did the otterx conversion, in other words you didn't just try to install an otterx rom on standard recovery and partitions, then you won't have the option of using the usb mount. You will have to go through the adb push method, which I don't remember, but there are other topics on this forum that explain how to access the adb (android debug) and use the push command as well as others. Good luck and if you get it fixed be more careful next time. If you aren't familiar with how to do these processes you can easily brick your device. Read research and read again to be sure you have all the steps down!

I have been up for HOURS trying to fix it. I used a Kindle Utility Tool and rooted. It Installed some google apps after SU... At this point when using usb the Kindle would show up in "my computer" so i put cm11 on it. Tryed to flash it and it wouldnt work. I deleted something and now all the OS are gone. It says it. When j try to boot it stays stuck on the screen. I can pick to boot recovery but even when i abd push roms. Cm11 and stock kindle os it wont flasb then because of E: partitions not there.
I dont have any idea whats left to try. I really tried everything i could find.!! Now it dosent show up on "my computer" anymore... its like. Gone gone!!!!

I need to figure out a way to get it to work. I need to find out how to add partitions first i guess.... i got twrp and thats like it... i cant get a boot.img to flash. Nothing....
I need some serious help. I gotta fix this atleast back to amazon kindle os before they find out i broke it. Lol

robles4242 said:
I need to figure out a way to get it to work. I need to find out how to add partitions first i guess.... i got twrp and thats like it... i cant get a boot.img to flash. Nothing....
I need some serious help. I gotta fix this atleast back to amazon kindle os before they find out i broke it. Lol
Click to expand...
Click to collapse
Which twrp version?
Sent from my XT907 using Tapatalk