Kindle Fire Brick Utility not working - Kindle Fire Q&A, Help & Troubleshooting

So i think I bricked my kindle fire. It is rooted and when trying to install a new ROM, i accidentally selected the fastboot option. Now, when I power it on, all i get is the logo and it never loads. I cannot get into the boot manager to try anything. I have tried the Kindle Unbrick utility from this link: http://forum.xda-developers.com/showthread.php?t=1428428 and it says waiting for device when I run the stuck on logo option. Is there anything else I can do? I really dont want to get another one. Any help would be appreciated! I can't post in the development forum so thats why i posted here. Thanks everyone.

What version of Windows are you using?

Read the WHOLE first post of the Unbrick Utility thread. It's a driver problem.

Thanks I got it to work now but now when I plug it into the USB, it does not show that I can open it and drop files. I go into TWRP and try to mount the USB and it will not let me and I am unsure what to do!

roykurka said:
Thanks I got it to work now but now when I plug it into the USB, it does not show that I can open it and drop files. I go into TWRP and try to mount the USB and it will not let me and I am unsure what to do!
Click to expand...
Click to collapse
If you're using an ICS ROM I don't believe mounting "mass storage" works on all of them.
Does it saying anything when trying to mount USB in TWRP? What does "won't let me" imply? Windows or TWRP throws an error message?

When I go into TWRP and go to MOUNT and then try to select Mount SDCard it will not let me check the box. I have a ROM running on it now but I cannot access the SD card when I plug it into the computer.

roykurka said:
When I go into TWRP and go to MOUNT and then try to select Mount SDCard it will not let me check the box. I have a ROM running on it now but I cannot access the SD card when I plug it into the computer.
Click to expand...
Click to collapse
What ROM are you using?

nchevaux said:
What ROM are you using?
Click to expand...
Click to collapse
i am using CyanogenMod 9.0.0-RCO-otter-UNNOFFICIAL
Also, when i go to the about tablet on the Kindle and look at Model Number, it shows Galaxy Nexus.....

Any other suggestions or help?

roykurka said:
Any other suggestions or help?
Click to expand...
Click to collapse
Boot into TWRP and get to a prompt using adb shell. Then use this command to open parted...
Code:
parted /dev/block/mmcblk0
When you get to the "(parted)" prompt...
Code:
print
The last line, the media partition, is what gets mounted as /sdcard on your device. It should have a "fat32" file system type. If you don't have that, you need to make a new filesystem on that partition.
Code:
mkfs 12 fat32
12 is the partition number and fat32 is the filesystem type you want to use to format the partition. If memory serves, parted will ask you for this information again to confirm. Remember... 12 and fat32. Once you are done, you can...
Code:
quit
Once you've done that, TWRP should be able to see the partition and allow you to mount it on your host computer. You might have to restart TWRP... I don't remember.

I have not been able to get adb to run. When i boot to TWRP and go to the command prompt and type adb devices it says " 'adb' is not recognized as an internal or external command, operable program or batch file."
I set the path to where the android sdk is located and it still doesnt work.
Im sure I sound like a newb or something but I am just not as tech savy with these kind of things. thanks everyone for your help with this.

roykurka said:
I have not been able to get adb to run. When i boot to TWRP and go to the command prompt and type adb devices it says " 'adb' is not recognized as an internal or external command, operable program or batch file."
I set the path to where the android sdk is located and it still doesnt work.
Im sure I sound like a newb or something but I am just not as tech savy with these kind of things. thanks everyone for your help with this.
Click to expand...
Click to collapse
Find the adb executable through Windows Explorer. Once you find the folder containing adb, shift-right-click inside that folder and select "Open command window here" and then you'll be able to use the adb command.
Another way to do it is to download the Kindle Fire Utility distribution and follow the third post in this link...
http://forum.xda-developers.com/showthread.php?t=1552547
You don't have to set the path to anything special if you do it one of those two ways.

roykurka said:
I have not been able to get adb to run. When i boot to TWRP and go to the command prompt and type adb devices it says " 'adb' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
It seems you have set your path incorrectly. I found it easiest to just copy the entire platform-tools folder to the root of C:\ and run adb from there (You could also use a Windows shortcut to cmd with "start in" filled out, or use shift-right click through explorer).
Definitely try to get adb working; when I first rooted my Kindle it took me an hour to fix a boot-loop without adb (damn drivers), and only seconds with adb.

kinfauns said:
Boot into TWRP and get to a prompt using adb shell. Then use this command to open parted...
Code:
parted /dev/block/mmcblk0
When you get to the "(parted)" prompt...
Code:
print
The last line, the media partition, is what gets mounted as /sdcard on your device. It should have a "fat32" file system type. If you don't have that, you need to make a new filesystem on that partition.
Code:
mkfs 12 fat32
12 is the partition number and fat32 is the filesystem type you want to use to format the partition. If memory serves, parted will ask you for this information again to confirm. Remember... 12 and fat32. Once you are done, you can...
Code:
quit
Once you've done that, TWRP should be able to see the partition and allow you to mount it on your host computer. You might have to restart TWRP... I don't remember.
Click to expand...
Click to collapse
When i try the first command, i get the same response saying parted is not recognized as an internal or external command, operable program or batch file.
I have the kindle in TWRP and connected to the PC. What do I do now?

roykurka said:
When i try the first command, i get the same response saying parted is not recognized as an internal or external command, operable program or batch file.
I have the kindle in TWRP and connected to the PC. What do I do now?
Click to expand...
Click to collapse
okay... I'm going to make this super easy for you... get ADB working...
1. Download attached "adb.zip"
2. Extract adb.zip to a folder
3. Double-click "CLICK ME!!!"
4. Type "adb" and see instructions come up
5. Type "adb devices" and see a 12-digit code
now reread your own thread and try all those instructions again in ADB
P.S. type "ADB shell" before trying the instructions from kinfauns

When I type the adb devcies it says "list of devices attached but does not show anything.
I apologize for probably something so simple

roykurka said:
When I type the adb devcies it says "list of devices attached but does not show anything.
I apologize for probably something so simple
Click to expand...
Click to collapse
I think you should back up a bit and read this...
http://forum.xda-developers.com/showthread.php?t=1552547
Start at post #1... follow the steps in #2 and confirm your device drivers are getting loaded properly... study #3 for fastboot and adb commands.
#2 is going to be the most important for you because it looks like there's a problem with your device drivers or you are missing a necessary initialization file. Following the directions there will get you fixed up.
After doing all that, go back to my previous post.

It works, I got to mount the SD card and everything. Thank You everyone for all of your help!

Related

[Q] Evo Won't charge, see sdcard or be seen by pc

Originally posted in general. Sorry.
My Evo won't charge unless it is turned off. When the phone is on, the usb won't give me any mode option. Phone doesn't see the sdcard. I've tried three different cards. PC won't see the phone. I have usb debugging checked. Device manager gives me three qualcomm CDMA Technologies and can't find drivers. Downloaded qualcomm drivers. Device manager now shows them as samsung items. Everything on the phone works except for apps using the sdcard. With the vol down and power the phone will read the PC36IMG.zip of the sdcard and load and run it. After rebooting it still doesn't recognize the sdcard. Using fastboot the device manager gives me Android Devices, but I can't use adb commands. I get and error device not found. Any help?
it should charge anyway, even without the drivers...but, sounds like you need 'em to me. they're in the forums...somewhere...or, you could just get the most recent sdk, and update the drivers using devmgmt.msc (i'm assuming you're on windows)
this happen to me yesterday, i was able to fix it... i have to find the steps
airauto said:
Originally posted in general. Sorry.
My Evo won't charge unless it is turned off. When the phone is on, the usb won't give me any mode option. Phone doesn't see the sdcard. I've tried three different cards. PC won't see the phone. I have usb debugging checked. Device manager gives me three qualcomm CDMA Technologies and can't find drivers. Downloaded qualcomm drivers. Device manager now shows them as samsung items. Everything on the phone works except for apps using the sdcard. With the vol down and power the phone will read the PC36IMG.zip of the sdcard and load and run it. After rebooting it still doesn't recognize the sdcard. Using fastboot the device manager gives me Android Devices, but I can't use adb commands. I get and error device not found. Any help?
Click to expand...
Click to collapse
here you go
http://forum.xda-developers.com/showthread.php?t=695243
The phone only charges when the phone is off. I've downloaded the latest sdk drivers. I tried the SD Card Fix, but I can't get to an ADB shell.
The phone worked great for a couple of weeks, but when I was using Rom Manager to load a rom, I got an error and a red triangle. I pulled the battery and started the phone. It couldn't load the sdcard, it wouldn't give me usb options. It did give me a short battery life and no way to use ADB commands. I can't use rom manager or titanium backup or nand to restore backups. I really need help please!
airauto said:
The phone only charges when the phone is off. I've downloaded the latest sdk drivers. I tried the SD Card Fix, but I can't get to an ADB shell.
Click to expand...
Click to collapse
if you can't get to a shell, that probably means that an adb devices command is not seeing the device.
i'll refer you to the earlier statement about you not having the drivers.
I checked and I have downloaded android-sdk_r06-windows.zip. I believe these are the latest drivers. They worked fine until it crashed while I was using rom manager to load a different rom. It seems strange that everything works except for charging while on, usb and the sdcard.
airauto said:
I checked and I have downloaded android-sdk_r06-windows.zip. I believe these are the latest drivers. They worked fine until it crashed while I was using rom manager to load a different rom. It seems strange that everything works except for charging while on, usb and the sdcard.
Click to expand...
Click to collapse
just having the sdk doesn't enable drivers. if you are on windows, in the 'search' field (or in a cmd shell) type
devmgmt.msc
there, you will probably see a device , i think it will have a yellow triangle and an exclamation point. right click on that device, choose the option that allows you to install drivers. then, browse for drivers (make sure you have the option to include subfolders checkmarked). the drivers are located in the 'usb drivers' folder in the sdk folder. once you have the 'usb drivers' folder highlighted, just choose 'okay', and it will search that folder and subfolders for the appropriate driver.
I've done that. When I use devmgmt.msc and I connect my phone it gives me three unknowns called Qualcomm CDMA Technologies MSM. I point these to the drivers folder and it doesn't recognize them. I downloaded qualcomm drivers and it recognized them as samsung devices and these don't work. When I hook up usb while in fastboot devmgmt.msc gets one device called android devices, but it still will not recognize the sdk drivers. Something happened when the phone crashed. Is there a way to do anything with hboot or fast boot or the other items in that menu to get the phone to recognize adb commands. The phone does load and install PC36IMG.zip, but the phone still acts the same, no sdcard, no usb and no charge.
I was trying this thread
http://forum.xda-developers.com/showthread.php?t=695243
How do you Run from a terminal emulator in Android since I don't have ADB?
airauto said:
I was trying this thread
http://forum.xda-developers.com/showthread.php?t=695243
How do you Run from a terminal emulator in Android since I don't have ADB?
Click to expand...
Click to collapse
you have to get a terminal emulator. and, you have to have downloaded those files to your sdcard. you also have to be rooted already.
OK, I have the two files extracted and on the sdcard. I called up the terminal emulator and typed
su
cat /sdcard/flash_image > /data/flash_image
at this point I get an error message /sdcard/flash_image: No such file or directory
at one time my phone was rooted, but I no longer have the Superuser Permissions.
help some more?
Edit/Delete Message
Ok thanks, I finally got it all working. After a week of learning about ADB, Terminal and Fastboot commands not to mention the structure of the Evo file system, charging, usb and sdcard are all working thanks to everyone contributing to the forum.
airauto said:
Ok thanks, I finally got it all working. After a week of learning about ADB, Terminal and Fastboot commands not to mention the structure of the Evo file system, charging, usb and sdcard are all working thanks to everyone contributing to the forum.
Click to expand...
Click to collapse
could you provide a step by step to how you got this issue resolved?
my brother's phone is experiencing the exact same symptoms you described.
we have been at it for a week.
we too cannot get the "adb shell" command to work when trying to use SDK.
we get the error "device not found" after typing "adb shell".
Im not sure its being done correctly either.
please assist, your help is greatly appreciated.
I used this thread:
http://forum.xda-developers.com/showthread.php?t=695243
Read through the whole thread and download the files. Install them on the root directory of your sdcard with a card reader/writer. Put the sdcard back in your phone.
Now to use the thread you have to get into recovery.
Hold vol down and press power on your phone.
Plug in the usb, and open device manager on your PC.
Choose recovery and make sure Android USB Devices show up in device manger
On the PC, get to a DOS prompt and change dir to where you have adb and fastboot and follow the thread for SD Card Fix and USB Fix exactly.
Good Luck!
And thank you to Calkulin for the thread!
airauto said:
I used this thread:
http://forum.xda-developers.com/showthread.php?t=695243
Read through the whole thread and download the files. Install them on the root directory of your sdcard with a card reader/writer. Put the sdcard back in your phone.
Now to use the thread you have to get into recovery.
Hold vol down and press power on your phone.
Plug in the usb, and open device manager on your PC.
Choose recovery and make sure Android USB Devices show up in device manger
On the PC, get to a DOS prompt and change dir to where you have adb and fastboot and follow the thread for SD Card Fix and USB Fix exactly.
Good Luck!
And thank you to Calkulin for the thread!
Click to expand...
Click to collapse
Yeah I had found that thread as well, I get all the way up to the adb commands.
when I type adb shell, I get "device not found".
also, just to verify, I boot the phone down and turn it on using "down volume" and "power".
when the "HBOOT" screen shows up and the scan finds nothing, I select "fastboot", and leave it there.
then back to the pc:
before I type "adb shell', I point to the directory "c:/users/desktop/android-sdk-windows/tools".
once the directory is pointed to "c:/users/desktop/android-sdk-windows/tools", I input "adb shell" command.
Is this correct?
That is the procedure I follow and I keep getting "device not found", and yes my sdk is fully updated.
Yes, but don't do ADB shell. In HBOOT hit the vol down button to highlight recovery. Hit the power button to select recovery and let it sit there. Go to your pc check your device manager. Then change dir to where you have ADB. Fastboot is also there
Fastboot is an executable program same as ADB. At the prompt just type the commands for the sdcard fix. ie:
fastboot oem enableqxdm 0
fastboot reboot
Your sdcard should be recognized. For the next section you will need to get the Android Terminal Emulator from the Android Market and enter the commands in it.
Have fun!
jdr6382 said:
Yeah I had found that thread as well, I get all the way up to the adb commands.
when I type adb shell, I get "device not found".
also, just to verify, I boot the phone down and turn it on using "down volume" and "power".
when the "HBOOT" screen shows up and the scan finds nothing, I select "fastboot", and leave it there.
then back to the pc:
before I type "adb shell', I point to the directory "c:/users/desktop/android-sdk-windows/tools".
once the directory is pointed to "c:/users/desktop/android-sdk-windows/tools", I input "adb shell" command.
Is this correct?
That is the procedure I follow and I keep getting "device not found", and yes my sdk is fully updated.
Click to expand...
Click to collapse
airauto said:
I used this thread:
http://forum.xda-developers.com/showthread.php?t=695243
Read through the whole thread and download the files. Install them on the root directory of your sdcard with a card reader/writer. Put the sdcard back in your phone.
Now to use the thread you have to get into recovery.
Hold vol down and press power on your phone.
Plug in the usb, and open device manager on your PC.
Choose recovery and make sure Android USB Devices show up in device manger
On the PC, get to a DOS prompt and change dir to where you have adb and fastboot and follow the thread for SD Card Fix and USB Fix exactly.
Good Luck!
And thank you to Calkulin for the thread!
Click to expand...
Click to collapse
That was it!! once we got the files on the SD card through my phone, and put it back in his phone, we did the commands and it worked!! good stuff, mad appreciation given here.
Congratulations. You got your EVO back better than ever!

[Q] SD card can't be mounted - Desire PVT4 after rooting

Hi guys,
I got a problem:
I rooted my Desire PVT4 with unrevoked and AmonRa-Recovery under Linux Mint Live CD. Everything went fine.
Next, I wanted to prepare for flashing a new rom. I did a Titanium Backup and downloaded Rom Manager. I proceeded to do a nand-backup, which it did, I guess. After that, however, my desire didn't recognize my sd card anymore.
Connecting to Windows 7 didn't work either. (It did work before)
So I went and bought a new sd card. I formatted it and put it in my device. Still, no sd card detected.
Along with the new sd card, I got an adapter, so I can now stick the sd card directly into my computer.
Surprise: I could now see both sd cards in Windows. Still, I formatted both after backing up the files on it.
The Desire wasn't able to boot anymore, though. So I went into recovery mode and partitioned the card manually with AmonRa recovery 2.0.1. This did work.
I can boot the Desire now, but it still won't detect the sd card.
Mounting it with AmonRa doesn't work either.
I read, that the problem might be caused by using RomManager on a PVT4 device.
Installing the HTC drivers didn't help and I can't install the google USB drivers. When I try to do so it says that there were no drivers found in the specified directory (""C:\android-sdk-windows\google-usb_driver")
In the device manager it shows 3 "Qualcomm CDMA Technologies MSM" (bought it in Germany, so shouldn't it read "GSM"?). All of them are marked with a yellow question mark. Upon trying to update the drivers I selected "Install software from a list or source" and specified ""C:\android-sdk-windows\google-usb_driver". I clicked "proceed" but Windows tells me that it couldn't find the drivers. Tried that on Win7 and on my WinXP laptop.
I desperately need help. I'm no pro. Actually I am a complete noob I searched on google but I couldn't find any solution so far.
Since I can't access my sd card (except partitioning in AmonRa, that did work somehow) I can't access any .zip on my sd card.
e. Additional information:
Upon trying to mount in Amonra recovery it says:
""Can't mount /sdcard"
Same, when trying to flash a .zip from sd.
hboot version is 0.93 I think.
I tried the following:
Just fixed it... i think the problem erupted because i have AmonRA recovery and used Rom manager (Clockwork mod recovery based) .. there were several reports
that this may cause a usb brick. ... any way... i searched for how to unbrick it.. and used a clone cd from modaco ((Tinycore.img)) which is linux based to boot from it (with phone connected to fastboot usb) .. and
entered the following commands :
Quote
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
cd /mnt/cdrom/root
/mnt/cdrom/root/fastboot oem enableqxdm 0
and it enabled the sdcard... i checked the sdcard workability from the recovery (i hadn't format it yet) then thought : WTH, why not to try and restart the phone to see if it will log in normally .. and it did (naturally
because the sdcard block was the thing that prevented it from booting from the very start)...
Click to expand...
Click to collapse
Except that I used Linux Mint Live CD.
All I got was:
Code:
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
mount: block device /dev/sr0 is write/protected, mounting read-only
sudo mount /dev/cdrom /mnt/cdrom
mount: block device /dev/sr0 is write-protected, mounting read-only
mount: /dev/sr0 already mounted or /mnt/cdrom busy
mount: according to mtab, /dev/sr0 is already mounted on /mnt/cdrom
cd /mnt/cdrom/root
bash: cd: /mnt/cdrom/root: No such file or directory
Must I use TinyCore? I read somewhere that it only works for Hboot 0.8 and lower? What exactly is TinyCore anyways?
I almost know nothing about linux
No one?
Now I can't even get a signal anymore. I could cry...
Have you tried this procedure?
http://forum.xda-developers.com/showthread.php?t=691639
It worked for me when i bricked (pvt1 s-off). The problem seems to lie in the misc partition, which you have patch with the edited img file...
When I get into fastboot mode, where is the option to "'fastboot oem boot'"?
e. Also, my PC does not recognize the desire when pluggin into USB.
Eiskrem-Kaiser said:
When I get into fastboot mode, where is the option to "'fastboot oem boot'"?
Click to expand...
Click to collapse
You type that into cmd prompt window on your PC.
There are some instructions on SD card fix in this thread:
http://forum.xda-developers.com/showthread.php?t=691639
It happened to me when I partitioned the SD card in windows. Could you chech if your partitions on your SD are both set as primary and also uncheck "Take ownership of filesystem" (or something like that) when you are using the HD utility in linux.
Basically what happened was that the partitions were logical in stead of primary. Banged my had in the wall for two days before I figured this out. Hope it helps.
I'll try the Usb-brick-fix first. But how do I find out which rom version I have? I managed to get my CID by typing "fastboot oem boot" in the command prompt.
e. This is what I get upon writing the command:
http://www.abload.de/img/unbenannt7njw.jpg
e. I noticed, it says "board_bravo.disable-sdcard=1"
what does that mean?
Eiskrem-Kaiser said:
I'll try the Usb-brick-fix first. But how do I find out which rom version I have? I managed to get my CID by typing "fastboot oem boot" in the command prompt.
e. This is what I get upon writing the command:
http://www.abload.de/img/unbenannt7njw.jpg
e. I noticed, it says "board_bravo.disable-sdcard=1"
what does that mean?
Click to expand...
Click to collapse
I guess it means that sdcard can't be mounted...anyway, have you done the hexeditor thing already?
I just put the two files on the sd card and rebooted in fastmode. However, I'm not sure about my rom version. Where can I find out which one I have?
e. I just typed "cat /sdcard/flash_image > /data/flash_image" in ConnectBot, but it says "cannot create /data/flash_image: permission denied"
e.. When I type in "su" first, it still says "/sdcard/flash_image: No such file or directory"
Eiskrem-Kaiser said:
Where can I find out which one I have?
Click to expand...
Click to collapse
Oh sorry, i didn't read that...well i remember i was confused about that too at this point...too bad i can't remember how i found out.
Anyway, i found another solution on modaco:
"2. Enable the SD Card functionality. Boot your phone in FASTBOOT mode (back + power), and enter this command: 'fastboot oem enableqxdm 0' . This will re-enable your SD card.
3. Put THIS (attached) update.zip on your sdcard.
4. Reboot into recovery.
5. Apply sdcard:update.zip.
6. This will automatically fix your MISC partition with the correct CID. Reboot, and your done!"
Try this and tell me if it works in the while
I just booted into fastmode again and typed "fastboot oem enableqxdm 0" into the command prompt.
Now the Desire detects the sd card again :thumbsup:
Now I will try to use the cat command again.
e. I just did the thing with the "update.zip". Rebooting now.
e. I got my sd card back and a phone signal. That's great so far. Now what?
Still, when typing
"cat /sdcard/flash_image > /data/flash_image"
I get
"/sdcard/flash_image: No such file or directory"
I guess you're done if it worked...are you able to connect normally to your pc now? You should be :s
Also, those commands are meant to be used in a terminal emulator, not on your pc, i hope you didn't misread...anyway if you used the modaco tip you shouldn't need that anymore.
When you're done remember to copy your misc folder to a safe place, it will be enough to replace it via root explorer or similar if someday you'll brick again...
Nope, can't get it to connect to my PC quite yet. But I hope I will get that to work after rebooting the phone and/or windows or installing the htc drivers again.
I can not thank you enough right now. I was going crazy about this. Just bought my desire recently, upgrading from the Legend, with the little spare money I had. It would have been bad, if it was broken now.
So: THANK YOU VERY MUCH.
Also, someone tried to call me yesterday, while my phone signal didn't work. Now everytime I start the Phone, it shows me my missed call.
My girlfriend has a similar problem with a message I sent her. Everytime she boots her phone, she gets that message (fortunately it's "I love you" ).
So, I guess, it has something to do with the SIM?
Hmm, if you can't connect it might mean that the usb isn't fully restored...could you turn off the phone, plug it to pc, turn it back on and see if drivers get installed properly? Just to make sure...
I am stupid.
Hold on, it might work now. I had to switch to "local" in ConnectBot. Thought the app would remember that, but it didn't
Hmm.
Do I have to be in fastboot mode to type in those commands? Because I did type them in and rebooted, but Windows still will not detect my Desire :/
or should I type them in the windows command prompt?
Eiskrem-Kaiser said:
Hmm.
Do I have to be in fastboot mode to type in those commands? Because I did type them in and rebooted, but Windows still will not detect my Desire :/
or should I type them in the windows command prompt?
Click to expand...
Click to collapse
Sorry, i'm not sure i got ya. How would you run connectbot while you're in saftboot mode?? Because that's what i did, to make it clearer:
1. Downloaded image file "mtd0.img" and "flash_image" (from here http://forum.xda-developers.com/showthread.php?t=691639) and put them on sdcard (ofc i edited mtd0.img with my CID using some free hex editor before)
2. Installed Android Terminal Emulator app (from market), but connectbot should be the same.
3. Opened emulator, typed "su" command, accepted to give root permissions
executed this commands:
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/misc.img > /data/misc.img
chmod 755 /data/flash_image
/data/flash_image misc /data/misc.img
4. Rebooted phone, connected to pc.
5. Success
Is this exactly what you did?
Yes. I typed exactly that. I just wanted to type it in again, but now it tells me again, that there is no such file or directory on /sdcard. But I can see the file with Astro being on the sdcard.
e. Maybe I used the wrong rom version number?
e.. Someone suggested to run in fastboot mode and type "fastboot oem eraseconfig". What exactly would this do? Which config would be erased?
What exactly is fastboot?
Eiskrem-Kaiser said:
Maybe I used the wrong rom version number?
What exactly is fastboot?
Click to expand...
Click to collapse
You just need the CID, not the rom version for this...
Anyway, please note that when i write misc.img i mean mtd0.img, that's what you typed right? Sorry if i confused you.
I guess there's no need to mess further with fasboot, i didn't need it, except for mounting sdcard.
If this still fails, you can always move mtd0.img and flash_image to /data manually via root explorer app, then go on from the chmod command.

Wiped Phone Now Can't See SD Card On Lappy, PLEASE HELP

I used Team win Recovery Project to wipe my phone Galaxy Nexus, and now when I plug the phone in to the lappy it doesn't show the sd card. Freaking out here cause I can't copy over a zip file to flash a ROM... please help...
The GNEX doesn't have an actual sdcard, so when you wiped the phone i'm guessing you wiped the virtual sd card.
You will have to adb push a rom to your phone.
One the top of the first Q&A page jubakuba has a guide that has a panic section in it.
The guide also shows how to install adb/fastboot and gives you the commands.
try flash the stock img via fastboot using the following line to avoid wiping ur sdcard
fastboot update ***.zip
then wipe data via CWM and enjoy
xskordeal said:
try flash the stock img via fastboot using the following line to avoid wiping ur sdcard
fastboot update ***.zip
then wipe data via CWM and enjoy
Click to expand...
Click to collapse
sorry, complete DOLT here. Where would I input the command?
If you don't know about adb/fastboot, do as suggested in first post. All is explained in the guide.
How to get to a MS-DOS prompt or Windows command line
TheDodgey said:
sorry, complete DOLT here. Where would I input the command?
Click to expand...
Click to collapse
Click Start.
Click Run.
Type cmd or command and press enter.
gpfnzl said:
If you don't know about adb/fastboot, do as suggested in first post. All is explained in the guide.
Click to expand...
Click to collapse
ok, following your instructions, and the instructions of the link, I have install ADB and can use cmd, however when I type adb shell, I get an error returning "device not found"
I see a lot of threads stating to make sure usb debugging is on, it was before I wiped the phone, but obviously I cant get to any settings at the moment.
on the verge of crying now, and noone likes to see a grown man cry
FIXED
I ran the push command whilst in recovery and it worked
not sure that it mattered, but I did change the zip file name to ROM.zip, and whilst in recovery, ran the comand "adb push ROM.zip /sdcard/ROM.zip
Just thought I would put that in there for other dopes like me that might come across this problem
Thanks to all for your help!
LOL
Normally if you can't see your device listed you haven't installed the drivers correctly.(or the correct drivers)
Also you have to open a command prompt window in the same folder as fastboot.exe and adb.exe
To do this in Windows 7:
Click the windows start button (bottom left hand corner)
In the search bar at the bottom type: cmd
At the top of the search list you will see the program cmd.exe right click and copy it.
Paste it into the same folder that has fastboot.exe and adb.exe
Now you can open the cmd window and type the command:
adb devices
Hit ENTER and if you have installed drivers correctly, the serial number of your phone will be listed.
If not, uninstall the drivers, download a new set of drivers from jubakuba or efrants guide and reinstall.
---------- Post added at 11:58 AM ---------- Previous post was at 11:53 AM ----------
TheDodgey said:
FIXED
I ran the push command whilst in recovery and it worked
not sure that it mattered, but I did change the zip file name to ROM.zip, and whilst in recovery, ran the comand "adb push ROM.zip /sdcard/ROM.zip
Just thought I would put that in there for other dopes like me that might come across this problem
Thanks to all for your help!
Click to expand...
Click to collapse
didn't need to change the name of the rom zip. Just needed to type the full name of the .zip file.
Good to see it worked, and the tears have stopped

[Q] Code?

My KF is bricked. It has TWRP on it but it has been wiped clean and my pc will not recognize it. It does in ADB, I keep seeing write the CODE: then stuff. I was told I could to where I needed to write this code by right clicking on the KFU Tools folder. I then get C:\android\Kindle Fire Utility>
Now that being said.. where do I begin to type the fastboot -i Ox1949 and so on. Sure do need some much appreciated help assistance.
Boot into TWRP and then do what Josepho1997 said. Then you can just flash the rom.
The "Rom.zip" would be the file path to wherever the rom is saved on your computer.
Where can I write the tag
Josepho1997 said:
So you just have no OS?
Boot into TWRP. Then Download and transfer the ROM via adb
Code:
adb push Rom.zip /sdcard
Then flash the ROM.
Sent from my Kindle Fire
Click to expand...
Click to collapse
But where do I code?
adb in cmd not recognized as a command
Josepho1997 said:
In cmd. Open up cmd, run adb, and then type that code. And remember what veeman said. When I say Rom.zip, you must put both the correct name and directory applicable to you. (Ex. C:\AlienDroid.zip)
Sent from my Kindle Fire
Click to expand...
Click to collapse
in cmd, adb is not recognized as a internal or external command, operable program or batch file.
Know how long it's been since I used cmd. Help me out please.
You need to open the cmd window when you are in the directory that contains the adb.exe file. Usually this is in C:/kfu/tools directory. The easiest way to do that is to use windows explorer and navigate to that directory then press shift and right click your mouse then select the option "open command window here". You should now be able to issue adb commands.
Sent from my Amazon Kindle Fire using Tapatalk 2
nacraracer said:
in cmd, adb is not recognized as a internal or external command, operable program or batch file.
Know how long it's been since I used cmd. Help me out please.
Click to expand...
Click to collapse
Easiest way is to download the Kindle Fire Utility and then navigate to the tools directory in the command line. Then you can run adb and fastboot commands.
Still won't communicate
veeman said:
Easiest way is to download the Kindle Fire Utility and then navigate to the tools directory in the command line. Then you can run adb and fastboot commands.
Click to expand...
Click to collapse
I have tried everything to get the computer to see the kindle. adb commands are not working. Just says waiting on device, tried to adb push a rom and it just said device not found.
I was able to bring up a fastboot menu one time but once there it wouldn't respond.
Any ideas please.
I am looking at the TWRP v2.2.0 screen. It will not mount either
nacraracer said:
I have tried everything to get the computer to see the kindle. adb commands are not working. Just says waiting on device, tried to adb push a rom and it just said device not found.
I was able to bring up a fastboot menu one time but once there it wouldn't respond.
Any ideas please.
I am looking at the TWRP v2.2.0 screen. It will not mount either
Click to expand...
Click to collapse
Have you installed the drivers?
veeman said:
Have you installed the drivers?
Click to expand...
Click to collapse
I did install the google drivers at the fire tool kit

[Q] Kindle Fire BRICKED (Stuck On Kindle Logo) No Susses in CMD

Hello, I Have a Kindle Fire 1st Gen. I Had CM 10.1 on it. I was attempting to put AOSP back on it for My Wife. I did I Noobish Move at 4 am half asleep, I Did NOT go into advanced mode in TWRP and uncheck DATA in the Wipe tab. So This Screwed me "Bricked" Message comes up in TWRP when rebooting, says ( NO OS ) . I have Tried Kindle unbrick utility with no success when clicking on "Stuck at Logo" in utility I get this Error ...> PIC Attatched!>
I then Tried Using android-sdk ( I have went in and edited the files that need to be edited in program files/android...> File_android_winusb as well as in .android folder in the appdata location) Along with CMD & I get a Error So far into the process of Resetting Kindle OS. Pic Attatched as well. It Seems Like I have something missing ?!?!?
I somewhat Suck at CMD, I don't have much experience with it, so Please go slow on me,when Giving advise....
Thanks In Advance!!
If you still have access to TWRP, use it to mount your sdcard to USB.
soupmagnet said:
If you still have access to TWRP, use it to mount your sdcard to USB.
Click to expand...
Click to collapse
I Tried That. I See the Device But when double clicking, It will not let me access it.
Butt Nugget said:
I Tried That. I See the Device But when double clicking, It will not let me access it.
Click to expand...
Click to collapse
Oh that's right, it won't work on 2nd generation devices.
Do you have your drivers installed? Are you able to send any adb commands (adb devices)?
soupmagnet said:
Oh that's right, it won't work on 2nd generation devices.
Do you have your drivers installed? Are you able to send any adb commands (adb devices)?
Click to expand...
Click to collapse
My Kindle is a 1st Gen. I'm not sure If I understand what You are talking about when You say "send Commands/devices" If Your talking about in CMD I Get all the way to Seeing my Device Serial Number for Kindle. The when I type "adb shell" I get a error saying (Failed: No such file or directory <2> - ) You can see this in the screen shot I attached to this thread..
Sorry, I looked at what forum this was in and got a little confused...silly me :silly:
Anyway, back on track...
You should not be receiving that error in TWRP. If you are, then something is seriously wrong with it and probably needs to be reinstalled. Other than that, I'm having trouble seeing where the problem is. (the pic shows that you're not in recovery, btw)
You clearly have access to adb, so...why aren't you using 'adb push' to transfer a new ROM to your sdcard to flash in recovery?
soupmagnet said:
Sorry, I looked at what forum this was in and got a little confused...silly me :silly:
Anyway, back on track...
You should not be receiving that error in TWRP. If you are, then something is seriously wrong with it and probably needs to be reinstalled. Other than that, I'm having trouble seeing where the problem is. (the pic shows that you're not in recovery, btw)
You clearly have access to adb, so...why aren't you using 'adb push' to transfer a new ROM to your sdcard to flash in recovery?
Click to expand...
Click to collapse
I've Done searches and only found how to attempt recovery, typing in commands on pc's CMD Prompt while kindle is mounted to usb in twrp and typing commands in on CMD in pc I installed Android SDK and Device driver. So Sounds possibly what I tried is totally different from what Your asking if i done? If So, Could You Explain step by step thee method with new roms or send me in the right directions 2 a how to link or video? Anything I would appreciate GREATLY! :fingers-crossed:
Butt Nugget said:
I've Done searches and only found how to attempt recovery, typing in commands on pc's CMD Prompt while kindle is mounted to usb in twrp and typing commands in on CMD in pc I installed Android SDK and Device driver.
Click to expand...
Click to collapse
I have no idea what you're saying.
All you need to do is, boot into recovery (TWRP), use adb to "push" a ROM to your sdcard (adb push...), then install the ROM in recovery.
soupmagnet said:
I have no idea what you're saying.
All you need to do is, boot into recovery (TWRP), use adb to "push" a ROM to your sdcard (adb push...), then install the ROM in recovery.
Click to expand...
Click to collapse
I mentioned Earlier (say, the Drive of the device is :F) In My computer, When I click :F It states Cannot access (Drivers are installed for kindle). I'm asking How Can I Mount USB in TWRP and Put ROM File on sdcard when I cannot access it... I Do Not have a Micro USB OTG to USB 2.0 Cable to plug up to kindle with the files put on a external HD to complete this course.
Does that make more since?
Butt Nugget said:
I mentioned Earlier (say, the Drive of the device is :F) In My computer, When I click :F It states Cannot access (Drivers are installed for kindle). I'm asking How Can I Mount USB in TWRP and Put ROM File on sdcard when I cannot access it... I Do Not have a Micro USB OTG to USB 2.0 Cable to plug up to kindle with the files put on a external HD to complete this course.
Does that make more since?
Click to expand...
Click to collapse
Try to understand what you're being told. I'm not saying anything about mounting your sdcard to transfer files to it so get that idea out of your head for a moment.
You need to boot into recovery and use the command 'adb push' to transfer a ROM to your sdcard, then flash it in recovery.
Now, does that make more sense?
soupmagnet said:
Try to understand what you're being told. I'm not saying anything about mounting your sdcard to transfer files to it so get that idea out of your head for a moment.
You need to boot into recovery and use the command 'adb push' to transfer a ROM to your sdcard, then flash it in recovery.
Now, does that make more sense?
Click to expand...
Click to collapse
I am attempting to understand what u are saying But I'm thinking ur not giving full step after step instructions OR this Version I have (v2.6.0.0) differs from Yours, Because there is No such OPTION as ADB PUSH..... I have ADB sideload (under Advanced Tab) which only wipes Cashe.. I've looked in every single area in TWRP and see nothing of anything You are talking about, other than "MOUNT" obviously.
soupmagnet said:
Try to understand what you're being told. I'm not saying anything about mounting your sdcard to transfer files to it so get that idea out of your head for a moment.
You need to boot into recovery and use the command 'adb push' to transfer a ROM to your sdcard, then flash it in recovery.
Now, does that make more sense?
Click to expand...
Click to collapse
While Searching Google for Help I seen this..> http://forum.xda-developers.com/showthread.php?t=2361144
I'm bout to install a Pc with Linux and try pushing it that way.. Have not tried that.
You don't need Linux to run adb commands *face palm* While I am a linux enthusiast, all he's trying to say is boot into twrp, plug kindle into your PC, and open a command prompt, CD into the directory of adb and run "adb push pathtofile /sdcard/filename" this should push it to the kindle, though their might be something else u need for in prior to this I'm not sure, soupemagnet will probably post back if there is. BTW I don't know if u actually meant u were going to install Linux, but if you don't plan on using it after this or anything in the case u do decide to still use it for this, u don't need to install it, distros like Ubuntu let you boot into a full os from the CD so u don't need to install it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You don't need Linux to run adb commands *face palm* While I am a linux enthusiast, all he's trying to say is boot into twrp, plug kindle into your PC, and open a command prompt, CD into the directory of adb and run "adb push pathtofile /sdcard/filename" this should push it to the kindle, though their might be something else u need for in prior to this I'm not sure, soupemagnet will probably post back if there is. BTW I don't know if u actually meant u were going to install Linux, but if you don't plan on using it after this or anything in the case u do decide to still use it for this, u don't need to install it, distros like Ubuntu let you boot into a full os from the CD so u don't need to install it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Stunt Thnx... You Helped breaking it down. I just used KFU and Fixed this within 3 minutes.. Thnx Man!:good:

Categories

Resources