TWRP Doesnt show my backed up to restore! and i have not any rom placed on my sd-card to install and iam wiped :cyclops::crying:
Kindle Fire 8.9 and TWRP 2.6.0.0 by the way, why the usb storage mounting doesnt work in TWRP?
DSH said:
TWRP Doesnt show my backed up to restore! and i have not any rom placed on my sd-card to install and iam wiped :cyclops::crying:
Kindle Fire 8.9 and TWRP 2.6.0.0 by the way, why the usb storage mounting doesnt work in TWRP?
Click to expand...
Click to collapse
i have figuerd out what must i do!
now i have ADB and ADB doesnt find my device to push the rom on it!
plz plz plz help me
i had Drivers installed but when in fastboot connected to pc windows cannt find JEM-Prod... (something like this)
i neeed your help im so confused
Why are you in fastboot, you just need to sideload the ROM onto twrp. Usually u just goto advanced>side load and swipe the thing. Then on your PC put the ROM in the same folder as adb command if you haven't setup your paths, and run adb.exe sideload filename.zip. that will typically do the job.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Why are you in fastboot, you just need to sideload the ROM onto twrp. Usually u just goto advanced>side load and swipe the thing. Then on your PC put the ROM in the same folder as adb command if you haven't setup your paths, and run adb.exe sideload filename.zip. that will typically do the job.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
thanks for your help but adb doesnt recognize my kindle fire! when in CMD i type "ADB Devices" no devices showd up and when "ADB usb" error shows
i think this is the cuase why your tip doesnt work for me (
ive tried this but step 3 give an error
Had been searching on & off over 2 months & finally found the sol
This now lets you use the KFU util and others to root & install new OS etc
You need to have installed ANDROID SDK and extras-usb & JAVA se
1)
you will need to modify the following two files:
a. adb_usb.ini – You can find it under your Users\YourUsername\.android folder
In a typical Windows 7 installation, adb_usb.ini will be located under C:\Users\YourUserNameHere\.android
Open the adb_usb.ini file with a text editor (Notepad is just fine) and add the following line at the end (on a new line). Save and exit.
0×1949
2)
android_winusb.inf – You can find it under the folder you installed the Android SDK, in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver
Open the file with a text editor (notepad is again good enough), locate [Google.NTx86] section and also the [Google.NTamd64] section and add the following lines to each section, like in the screenshot.
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
3)
Note: If your device list is empty, maybe you plugged-in Kindle Fire before you installed Android SDK and Android USB Drivers. In this case you’ll need to force load the Android USB driver. Right click on My Computer and select Properties then navigate to Device Manager. Under Other Devices you should see Kindle with a yellow icon containing an exclamation point.
Right Click on Kindle name and select Update Driver Software. A Dialog will pop-up asking how do you want to search for driver software. Select Browse and point toward the folder containing Google USB Driver (in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver). Select Next and proceed with the installation, choose Install this driver anyway when prompted.
Ok now you can
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
d. type adb kill-server followed by enter
e. type adb devices. If everything is fine, you should see a connected device (your Kindle Fire)
0000666665555 device
Click to expand...
Click to collapse
Sounds like you have a driver issue or the device would be showing up with adb devices, try using my drivers from this post: http://forum.xda-developers.com/showthread.php?p=44319953
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Sounds like you have a driver issue or the device would be showing up with adb devices, try using my drivers from this post: http://forum.xda-developers.com/showthread.php?p=44319953
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
thank you very much, but how must i install that?
in device manager i select update driver and locate this folder and it says windows was unable to install you kindle fire HD
i put my kf in recovery mod and plug in the cable!
why have i these problems ?
but again i wanna say thank you bro:good:
So in the task manager is showing a device with an exclamation mark over it right? If so right click the device and hit properties, then goto the details tab, and choose hardware id's from the drop down menu and post them here, I'll see about modifying the driver if I can. Don't know why mine wouldn't work I had the old and new vendor id's for twrp in that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
When i connect to pc in fastboot, in device manager shows as Other devices "Jem-PVT-Prod-04" and the Hardware Ids is:
USB\VID_1949&PID_0008&REV0100
USB\VID_1949&PID_0008
and when just plug the usb cable in recovery mod task manager show it as Portable Device and "Amazon Kindle Fire HD" with a yellow mark! and the hardware Ids is:
USB\VID_1949&PID_0008&REV_0216
USB\VID_1949&PID_0008
thank you bro
ok i guess the hd 8'd have a slightly different pid than the 7 inch model, here i uploaded the updated version to this thread. Try updating the amazon kindle hd device and using recovery if u can, its a better option to just reflash stuff from that rather than fastboot unless u need to, makes things little bit easier imo. This should also work with the jem-pvt-prod-04 device as well,
stunts513 said:
ok i guess the hd 8'd have a slightly different pid than the 7 inch model, here i uploaded the updated version to this thread. Try updating the amazon kindle hd device and using recovery if u can, its a better option to just reflash stuff from that rather than fastboot unless u need to, makes things little bit easier imo. This should also work with the jem-pvt-prod-04 device as well,
Click to expand...
Click to collapse
OMG OMG OMG you saved me and my KINDLE FIRE
i have best wishes for you bro best wishes :good::good::good::good::good::good:
Help!?!?!?
stunts513 said:
ok i guess the hd 8'd have a slightly different pid than the 7 inch model, here i uploaded the updated version to this thread. Try updating the amazon kindle hd device and using recovery if u can, its a better option to just reflash stuff from that rather than fastboot unless u need to, makes things little bit easier imo. This should also work with the jem-pvt-prod-04 device as well,
Click to expand...
Click to collapse
i flashed recovery.img to my kindle using flashify and than i rebooted it than it came up saying kindle fire than the red screen slides across the screen. the app says that you may see a red screen.so im stuck now.
You probably just need to reflash the recovery partition from fastboot.
Related
Hi guys! I'm new to the forum but not new to the IT world and not new to Linux or Android devices.
I'm stuck at the Kindle Fire screen after a failed attempt to root the device. Here's what I did. I'm hoping somebody can please help me. I did lots of Google searches to try to solve my issue and I can't seem to find the right solution.
So here's the background. I tried to root my KF by using this process http://www.pcworld.com/article/244303/how_to_root_your_kindle_fire.html on an Windows 7 VM. Then I found that SuperOneClick didn't work for KF6.3. So then I tried to KF Utility v.0.9.5 http://forum.xda-developers.com/showthread.php?t=1399889
I selected the option to root the KF. After it went through the process and I got the Kindle Fire screen (which is sounds like the KF is in the fastboot process) I couldn't get anything to work at that point. I couldn't get the VM to even see the KF nor Ubuntu (which is the main OS of that laptop). So then I figured I bricked the device. So I followed these instructions http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/ but that won't work ecause the KF isn't being recognized by the OS. SO at that point, I couldn't get anything to work. So I rebooted the laptop (which is running Ubuntu 12) and the KF booted back up and it fired back up.
If I power off the KF and turn it back on, it gets stuck at the KF bootup screen.
So at that point I decided to throw Windows 7 on a different laptop that I have and see if I can get it to work. So I installed java & Android ADK for my OS (Windows 7). I installed the USB driver and updated the packages. So I go through these instructions first http://forum.xda-developers.com/showthread.php?t=1568340 and I can't get the KF to be recognized as a device through adb. So I go back to the PC World instructions (linked above) and I follow steps through step 8. And I still can't get the KF to be displayed through adb. When I try to kill the adb server and then enter adb devices, I still can't get the KF to be recognized.
Oh and btw, Windows 7 does recognize the device as a "Kindle".
Any help would be greatly appreciated.
Sparty On!
Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works:
Sent from my Amazon Kindle Fire using Tapatalk 2
Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.
I'm having the same problem I think since windows doesn't recognize my kindle I can't install the drivers.
AndroidSparty said:
Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.
Click to expand...
Click to collapse
Us the same commands without -i 0x1949
fastboot oem idme bootmode 4000
fastboot reboot
Sent from my Amazon Kindle Fire using Tapatalk 2
ammubarak said:
Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works
Click to expand...
Click to collapse
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567
From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA
I received mine with 6.3 and KFU wouldn't recognize it even after using the driver installation. BUT I found way around it. You need to install the drivers manually, and then KFU will work. Download the drivers, then extract the .android folder (create it if you don't have one) to
C:\Documents and Settings\YOURUSERNAME\.android open up your device manager, click on the Kindle and follow the UI to select the .android folder. Restart and use KFU. Enjoy!
soupmagnet said:
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567
Click to expand...
Click to collapse
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
backspacepc said:
From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!
AndroidSparty said:
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!
Click to expand...
Click to collapse
Actually it will, status will still be off line, just select the boot mode option, and then on the next screen select normal bootmode
Sent from my MB860 using XDA
For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.
soupmagnet said:
For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.
Click to expand...
Click to collapse
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA
backspacepc said:
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Actually...I'm a she.
Since I have both available to me...it sounds like I should scrap the Windows (which is an understatement anyway) and use Linux/Ubuntu. That I can do!
I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
AndroidSparty said:
I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
You may also want to try to rerun your root script, oddly enough I've had that work before too.
Sent from my MB860 using XDA
AndroidSparty said:
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Did you notice the second post in the Linux tutorial?
kinfauns said:
Thanks for the guide on setting this up for linux. I just wanted to point out a small error in the instructions. The echo command above is incorrect and will not do what you intended. It should be corrected to
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
Click to expand...
Click to collapse
backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
I just ran kfu and I I was able to get it to do a normal boot. YAY!
Then I ran the .bat file in the KFU and I selected the permanent root. During the activating fastboot, it said that "Oops something went wrong...." it couldn't find the kindle. Then it installed twrp.img is missing and it downloaded successfully. So then I got the Notice, and it's installing TWRP and it's waiting for the device. I turned the Kindle off & on a few times to get the KFU to recognize the Kindle, and no luck. At least I was able to boot into the KF while it's still still waiting for the device. BUT....at this point during the TWRP install process, it's waiting for the device and not recognizing it.
soupmagnet said:
Did you notice the second post in the Linux tutorial?
Click to expand...
Click to collapse
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.
AndroidSparty said:
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.
Click to expand...
Click to collapse
I can't imagine why using vi would make any difference but you could try gedit to see if it works.
As for TWRP, you could install it manually (Windows). Make sure you have a connection with adb/fastboot and use KFU to set your device to fastboot mode. Keep in mind when you do this that you may have to go through the whole process of fixing your drivers again (blame Windows/KFU).
When you're in fastboot mode, hold the power button until the device shuts down.
Shift + right click the KFU folder that contains fastboot (tools) and open as a command
In the prompt that comes up, enter:
Code:
fastboot -i 0x1949 flash recovery /path/to/twrp2.1.img
When your prompt says "waiting for device", turn the device back on.
Make sure it's twrp 2.1 Version 2.0 is installed in a different manner and will most likely cause problems if installed with the "flash recovery" command.
hallo
1)i have a kindle2-root this-install cm10.1-but the mistake was "wipe internal storage".after install.
now it starts but no menue etc.
now i have to restore back to stock and flash again.
2)i have a fastboot-cabel
how can i flash the stock software/OS ????????
thx for help
reinhardrudi
Use this:
http://forum.xda-developers.com/showthread.php?t=2096888
If you have issues i can tell you the steps to restore manually, but it should work for you.
Edit: if that doesn't work you can also try this instead:
http://forum.xda-developers.com/showthread.php?t=2035047
--
Sent from my mind to your screen.
mindmajick said:
Use this:
http://forum.xda-developers.com/showthread.php?t=2096888
If you have issues i can tell you the steps to restore manually, but it should work for you..
Click to expand...
Click to collapse
hello
i have issues-is it possible you can tell me the steps ??
my bigest problem is,that i cant really install ADB driver-i test a lot of tutorials, also in german forums,but nothing helps.perhaps the kindle cant aktivate the adb at himself ??? because of the broken CM10.1 installation (wipe internal storage)
mfg
reinhardrudi
Windows or Linux? What version?
Sent from my SGH-I727 using Tapatalk 2
Enhaphym she
mindmajick said:
Windows or Linux? What version?
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
servus
win7x64
THX
@reinhardrudi,
when you say "i cant really install ADB driver", do you mean you have installed the drivers, but Windows fails to detect your Kindle when plugged into your PC's USB port?
On your PC, please check if file "adb_usb.ini" is present in folder "C:\Users\<your username>\.android\" (please note the leading dot in ".android").
I should contain the line "0x1949".
If you don't have this file (or it does not contain above-mentioned line), just create it with a normal text editor, e.g. Notepad.
Again, it only needs to contain one single line:
0x1949
and must be located in folder
C:\Users\<your username>\.android\ (assuming you have not changed the location of the user profiles on your PC).
Hope this helps
E_Zatopek said:
@reinhardrudi,
when you say "i cant really install ADB driver", do you mean you have installed the drivers, but Windows fails to detect your Kindle when plugged into your PC's USB port?
On your PC, please check if file "adb_usb.ini" is present in folder "C:\Users\<your username>\.android\" (please note the leading dot in ".android").
I should contain the line "0x1949".
Hope this helps
Click to expand...
Click to collapse
hello and THX
i have access to kindle to put files on it.but all the ADB/fastboot access test are failed. the kindle does not respond.i have no separately entry in the device manager.only under "mobile devices (in german "tragbare geräte")
Amazon Kindle Fire2 and the driver is a microsoft driver!
yes-i have this ini with "0x1949".
thx
reinhardrudi
@reinhardrudi
OK, let's try it this way:
In your very first post of this thread you mentioned you had a "fastboot-cabel".
When you connect the Kindle to your PC via this cable, does it come up in fastboot mode? If it it does, it will clearly display "fastboot" on the Kindle's screen - so there's no mistaking any other condition with the fastboot mode.
With the Kindle in fastboot mode, please open a command prompt (aka DOS box) and enter "fastboot -i 0x1949 getvar product" (without the quotation marks) and hit the [Enter/Return] key (assuming the directory where you have fastboot.exe and adb.exe residing is your current directory - if not cd into this directory first). Please post the result.
If your cable does not trigger the device to boot into fastboot, then it's most probably NOT a factory cable. Please note that the USB cable that comes with the Kindle by default is NOT a factory cable. A factory cable is specially wired to force the Kindle to fastboot mode.
Please run the test described above and come back here with the results. We'll then take it from there.
E_Zatopek said:
@reinhardrudi
In your very first post of this thread you mentioned you had a "fastboot-cabel".
When you connect the Kindle to your PC via this cable, does it come up in fastboot mode? If it it does, it will clearly display "fastboot" on the Kindle's screen - so there's no mistaking any other condition with the fastboot mode.
With the Kindle in fastboot mode, please open a command prompt (aka DOS box) and enter "fastboot -i 0x1949 getvar product" (without the quotation marks) and hit the [Enter/Return] key (assuming the directory where you have fastboot.exe and adb.exe residing is your current directory - if not cd into this directory first). Please post the result.
Please run the test described above and come back here with the results. We'll then take it from there.
Click to expand...
Click to collapse
hallo and THX for help
look at this picture-link:desktop-screenshot.
http://imageshack.us/photo/my-images/96/fastboot2.png/
and look her,my device manager after install all kindle drivers and boot kindle in fastboot-mode.
http://img18.imageshack.us/img18/5925/otter2.png
1)i get fastboot on my kindle-
2)but with your command i get a message: "waiting for device" .
mfg
reinhardrudi
reinhardrudi said:
hallo and THX for help
look at this picture-link:desktop-screenshot.
http://imageshack.us/photo/my-images/96/fastboot2.png/
and look her,my device manager after install all kindle drivers and boot kindle in fastboot-mode.
http://img18.imageshack.us/img18/5925/otter2.png
1)i get fastboot on my kindle-
2)but with your command i get a message: "waiting for device" .
mfg
reinhardrudi
Click to expand...
Click to collapse
The picture quality is awful.. But- it looks like there is an exclamation point next to your otter2 device.
Is that correct?
If so, the drivers are not installed
Sent from my SGH-I727 using Tapatalk 2
mindmajick said:
The picture quality is awful.. But- it looks like there is an exclamation point next to your otter2 device.
Is that correct?
If so, the drivers are not installed
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
yes i know-i test every driver here and in german forums-but no driver works for me.
did you know the name of the driver in the windows driverstore??????perhaps i can install the driver manually.
i never had so mutch trouble with any device what i get/buy,and i buy a lot of devices for PC etc.
THX
I used the drivers from here:
http://forum.xda-developers.com/showthread.php?t=1893838
I also installed manually. Please let me know if this helps
--
Sent from my mind to your screen.
hello again
after 2 hard weeks,and a lot of reading in this and other forums,many questions etc. i found a solution to install the driver correkly for my kindle
:laugh:
what did i have done??
after i had tested every cm 10.1 nigthly and the original 4.2.2 rom,every kindle USB- driver in this world--nothing,--no chance to install the kindle on 3 div. PC (win8+ win7) and 1virtual. Win7 Prof. x86
than i delete my cm10.1 inkl. gapps installation complete,and test the UNOFFICIAL TeamBAKED Black Bean 9 inkl. team baked's inverted gapps
http://forum.xda-developers.com/showthread.php?t=2237167
and -its magic-after the first boot and plug-in in my PC, the driver install is correkt in the device manager. i see kindel-ADB device and the driver comes from amazon - :good: Yeeaah.
now i test the kindle first aid again, to go back to stock.rom with the "Option1" when im at home (after work)
i hope everything goes well!!!!!
thx at all people who helps
EDIT: everything OK.first stock rom. Than cm10.1
reinhardrudi
So I rooted my kindle fire 8.9 and installed a 2nd bootloader along with team win recovery the root went fine but as soon as I installed the 2nd bootloader the kindle dose not go past silver kindle fire page I can load custom recovery but nothing else
Someone please help me with this
So it won't boot into the os, but will go into recovery. That a been happening with the latest update apparently, if it detects twrp or the modded boot loader it throws a fit and won't boot, you need to push a rom to flash to twrp and either downgrade the os, or flash a custom ROM. To do this you need to know how to use command prompt and adb, so if you know that much you would run something like this: adb push filetoflash.zip /sdcard/filetoflash.zip
From there its a simple matter of installing the file from inside twrp. If you need more details just reply back.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
So it won't boot into the os, but will go into recovery. That a been happening with the latest update apparently, if it detects twrp or the modded boot loader it throws a fit and won't boot, you need to push a rom to flash to twrp and either downgrade the os, or flash a custom ROM. To do this you need to know how to use command prompt and adb, so if you know that much you would run something like this: adb push filetoflash.zip /sdcard/filetoflash.zip
From there its a simple matter of installing the file from inside twrp. If you need more details just reply back.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for that is there any tutorials on this?
Eh idk if there's a tutorial for this exactly but there are plenty of threads with this problem and something similar where they accidentally wiped the internal storage and had to do same thing that you are having to do basically. I can point you in the right direction, just tell me what ROM you want on it, and I'll do my best to give you some instructions to get it onto the device.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Eh idk if there's a tutorial for this exactly but there are plenty of threads with this problem and something similar where they accidentally wiped the internal storage and had to do same thing that you are having to do basically. I can point you in the right direction, just tell me what ROM you want on it, and I'll do my best to give you some instructions to get it onto the device.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
cm 10.1 i guess just want to get this fixed so all help is appreciated don't want to have to throw the kindle away
OK sorry for the long wait, my friend bought me a copy of reach today since it was the only halo game I hadn't played so I put off writing a small tutorial until I was done.
First you need a working copy of adb, and your drivers working with twrp, so if you don't have a copy of adb handy, download my wallpaper fix and extract it so that there's a folder on the c drive called"stunts wallpaper fix", if you have adb somewhere else, just adjust how I say to do that to using the other path. So after u have extracted my fix to c:\, you should open the folder and see adb.exe in there, now download these 2 files into that folder:
http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130812-UNOFFICIAL-jem.zip
http://goo.im/gapps/gapps-jb-20130812-signed.zip
Now boot the kindle into twrp and plug it i to your pc and open a command prompt, I usually do it from a run box but searching the start menu for it works also. Once its open type "CD c:\stunts wallpaper fix" and press enter, now type "adb.exe devices" and make sure your device is listed' if it isn't open the device manager and check for a device with a triangle, if there is use the driver link in my signature to update the drivers to that and it should work. Anyways if your drivers are going well and it lists itself under devices, type this into command prompt "adb.exe push cm-10.1-20130812-UNOFFICIAL-jem.zip /sdcard/", then when it's done type "adb.exe push gapps-jb-20130812-signed.zip /sdcard/". If all goes well the files should be on the device, if you are coming from stock amazon I would tell twrp to backup only the data partition, since your system partition is kinda useless at this point, and once u have a backup you need to do a factory reset under wipe I believe, I don't remember for sure so I'll say do this even though the factory reset probably covers most of this, do a advanced wipe as well, only check cache, dalvik cache, and system. Now tell it to wipe. Once that is done hit install on the home screen and choose the cm 10.1 file on the sdcard first, and swipe to install it, then once done go to install again and choose the gapps and install it too, now reboot into the system. Tada!
If this is confusing or you need help with something else just post back, I know I didn't exactly organize this post very well but I kinda did it from my kindle so it wasn't easy to format it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK sorry for the long wait, my friend bought me a copy of reach today since it was the only halo game I hadn't played so I put off writing a small tutorial until I was done.
First you need a working copy of adb, and your drivers working with twrp, so if you don't have a copy of adb handy, download my wallpaper fix and extract it so that there's a folder on the c drive called"stunts wallpaper fix", if you have adb somewhere else, just adjust how I say to do that to using the other path. So after u have extracted my fix to c:\, you should open the folder and see adb.exe in there, now download these 2 files into that folder:
http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130812-UNOFFICIAL-jem.zip
http://goo.im/gapps/gapps-jb-20130812-signed.zip
Now boot the kindle into twrp and plug it i to your pc and open a command prompt, I usually do it from a run box but searching the start menu for it works also. Once its open type "CD c:\stunts wallpaper fix" and press enter, now type "adb.exe devices" and make sure your device is listed' if it isn't open the device manager and check for a device with a triangle, if there is use the driver link in my signature to update the drivers to that and it should work. Anyways if your drivers are going well and it lists itself under devices, type this into command prompt "adb.exe push cm-10.1-20130812-UNOFFICIAL-jem.zip /sdcard/", then when it's done type "adb.exe push gapps-jb-20130812-signed.zip /sdcard/". If all goes well the files should be on the device, if you are coming from stock amazon I would tell twrp to backup only the data partition, since your system partition is kinda useless at this point, and once u have a backup you need to do a factory reset under wipe I believe, I don't remember for sure so I'll say do this even though the factory reset probably covers most of this, do a advanced wipe as well, only check cache, dalvik cache, and system. Now tell it to wipe. Once that is done hit install on the home screen and choose the cm 10.1 file on the sdcard first, and swipe to install it, then once done go to install again and choose the gapps and install it too, now reboot into the system. Tada!
If this is confusing or you need help with something else just post back, I know I didn't exactly organize this post very well but I kinda did it from my kindle so it wasn't easy to format it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thank you so much you guide has fixed the brick I am now running cm.
stunts513 said:
OK sorry for the long wait, my friend bought me a copy of reach today since it was the only halo game I hadn't played so I put off writing a small tutorial until I was done.
First you need a working copy of adb, and your drivers working with twrp, so if you don't have a copy of adb handy, download my wallpaper fix and extract it so that there's a folder on the c drive called"stunts wallpaper fix", if you have adb somewhere else, just adjust how I say to do that to using the other path. So after u have extracted my fix to c:\, you should open the folder and see adb.exe in there, now download these 2 files into that folder:
http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130812-UNOFFICIAL-jem.zip
http://goo.im/gapps/gapps-jb-20130812-signed.zip
Now boot the kindle into twrp and plug it i to your pc and open a command prompt, I usually do it from a run box but searching the start menu for it works also. Once its open type "CD c:\stunts wallpaper fix" and press enter, now type "adb.exe devices" and make sure your device is listed' if it isn't open the device manager and check for a device with a triangle, if there is use the driver link in my signature to update the drivers to that and it should work. Anyways if your drivers are going well and it lists itself under devices, type this into command prompt "adb.exe push cm-10.1-20130812-UNOFFICIAL-jem.zip /sdcard/", then when it's done type "adb.exe push gapps-jb-20130812-signed.zip /sdcard/". If all goes well the files should be on the device, if you are coming from stock amazon I would tell twrp to backup only the data partition, since your system partition is kinda useless at this point, and once u have a backup you need to do a factory reset under wipe I believe, I don't remember for sure so I'll say do this even though the factory reset probably covers most of this, do a advanced wipe as well, only check cache, dalvik cache, and system. Now tell it to wipe. Once that is done hit install on the home screen and choose the cm 10.1 file on the sdcard first, and swipe to install it, then once done go to install again and choose the gapps and install it too, now reboot into the system. Tada!
If this is confusing or you need help with something else just post back, I know I didn't exactly organize this post very well but I kinda did it from my kindle so it wasn't easy to format it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Ok how do you use the driver link from your signature, I'm using windows 8 and can't get any drivers to install. I sold my kindle and now it's stuck on the blue kindle fire logo. I stupidly wiped everything including system in twrp .
Windows 8 is a bit more tricky because you have to boot the os up with driver signature enforcement disabled, look it up on Google, once you do that you go into the device manager a d find the device with an exclamation and hit update driver, then browse to the folder where you extracted the files from the zip in my signature,
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Windows 8 is a bit more tricky because you have to boot the os up with driver signature enforcement disabled, look it up on Google, once you do that you go into the device manager a d find the device with an exclamation and hit update driver, then browse to the folder where you extracted the files from the zip in my signature,
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks .. I'll give it a go tonight
I've cracked the kindle code for ADB Sideload / Push In TWRP recovery! :highfive:
If you have access to TWRP and nothing else, this is for you.
Like many, I foolishly formatted my internal storage on my Kindle Fire 2 while in TWRP. with no Zips to flash I was stuck trying everything I could think of to get a file onto my Device. Read up on ADB Sideload.. But my PC would not recognize ADB Sideload AT ALL, and I Couldn't Find the Drivers.
Read up on Mounting.. No drivers no mount. Updated my Android SDK, drivers there didn’t work. Almost threw my kindle in the river.
But then I Found A certain set of Drivers from Amazon's support section. (See Attached)
So here's how to get your kindle back: :fingers-crossed:
Download and Extract the driver files. Run the Kindle Drivers. Once the Drivers are finished plug in your kindle fire 2, windows will not recognize it and we need to install the driver manually.
Go to My Computer icon. Right click and select Properties. Open Device manager in the top left.
Your Kindle will show as a yellow triangle Kindle or Kindle Fire Device (or in some cases it will have the wrong driver installed, {right click and uninstall current driver, your PC will have to restart.})
Right Click on Kindle Fire Device> Click Update Driver Software..> Click Browse my computer for Driver software> Click Let Me pick from a list of device drivers on my computer>
NOW {Kindle} will show up on the list a few times, find the one that has: ADNROID COMPOSITE ADB INTERFACE and install this driver for your kindle. If everything worked your kindle fire will now be recognized and install.
NEXT STEP!
Sideload will not work for this, so don’t even try. No SDK is required for this process just the ADB Files (Attached)
Make sure you extract the ADB.zip right onto your C:/ drive to make this easy.
Download any Kindle Fire 2 Rom (Found in Kindle Fire 2 Android Development section, preferably a Small File Size like CM 10.1),
Rename this ZIP to kindle.zip (or another short name)
Download the Gapps File for the version of ROM you just downloaded from Goo.im,
Rename this ZIP to gapps.zip (or another short name)
Place both ZIPs directly into the C:/ADB folder
Open a command prompt by going to Start > Run > CMD and hit enter. A DOS Command prompt will open.
First line will say
C:\USERS\YOURNAME>
Type> CD C:\ADB Now it will change your Directory to the C:\ Drive ADB folder
Ok on your Tablet now in TWRP, Tap MOUNT> next check [x]DATA and [x]System and tap MOUNT USB SYSTEM
Windows will not notify you of the change so don’t freak out.
ADB needs to be at least Version 1.0.29, you can check by typing the command: ADB version
Next type> ADB devices
Will now say>
LIST OF DEVICES ATTACHED:
123456789ABCDEF RECOVERY
(IF it doesn’t say anything under list of devices you will have to uninstall and reinstall the driver in step 1)
Next TYPE> adb push kindle.zip \sdcard\kindle.zip
Wait about 30-40 seconds without touching anything, it will be sending the file.
IT WILL SAY>
3589 KB/s (128302247 bytes in 34.908s) or something similar.
Next Type> adb push gapps.zip \sdcard\gapps.zip
Wait about 30-40 seconds without touching anything, it will be sending the file.
IT WILL SAY>
3262 KB/s (57280392 bytes in 17.143s) or something similar.
BAM! Files are on your device!
BACK TO THE TABLET!
Tap Unmount and click the home icon in the top right.
Click INSTALL and tap (UP A LEVEL) to get to the root of the kindle fire.
Your files should be there Labeled Kindle.zip and Gapps.zip!
Install normally! AND Don’t forget to Wipe your Dalvik/Cache! :good:
All this info is available in the forums here but I'm really glad you did this. It should prevent a lot of redundant questions. Very well written, simplified and explained.
Kudos!
-> Sent from my mind to your screen.
Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime.
hi, i am using Chinookgod's method to push the kindle.zip and gapps.zip to my kindle successfully
but when i try to 'swip to confirm flash', it shows 'Failed' ,
and E:Mount: Unable to find partition for path '/\sdcard\kindle.zip'
Error flashing zip '/\sdcard\kindle.zip'
Updating partition details..
below is the screen cap
hxxp://imgur.com/ecjcZZF (please change hxxp to http)
what should i do? plz help :crying:
below is my cmd.exe screen cap, please note that it still shows
LIST OF DEVICES ATTACHED:
123456789ABCDEF RECOVERY
hxxp://imgur.com/WJs4ABY (please change hxxp to http)
Easy.
bon1025hk said:
hi, i am using Chinookgod's method to push the kindle.zip and gapps.zip to my kindle successfully
but when i try to 'swip to confirm flash', it shows 'Failed' ,
and E:Mount: Unable to find partition for path '/\sdcard\kindle.zip'
Error flashing zip '/\sdcard\kindle.zip'
Updating partition details..
below is the screen cap
hxxp://imgur.com/ecjcZZF (please change hxxp to http)
what should i do? plz help :crying:
below is my cmd.exe screen cap, please note that it still shows
LIST OF DEVICES ATTACHED:
123456789ABCDEF RECOVERY
hxxp://imgur.com/WJs4ABY (please change hxxp to http)
Click to expand...
Click to collapse
Thats easy. You can fix this by doing a system wipe then do a factory data reset to prep the system.
Will it work for me?
I got backup of my rom in my sdcard but having the same problem when try to restore. stuck with no OS. Help
My Phone Lg lu6200
Still need help
Chinookgod said:
Thats easy. You can fix this by doing a system wipe then do a factory data reset to prep the system.
Click to expand...
Click to collapse
I tried following your instructions and the directory came up. I then tried entering "adb shell" as a command and got the following:
Doesn't work for my Kindle HD 8.9...any help please?
I get an error closed closed
Chinookgod said:
Thats easy. You can fix this by doing a system wipe then do a factory data reset to prep the system.
Click to expand...
Click to collapse
hi,
i have Kindle Fire HD 7" after some issues i try to flashing, voip all data and delete backup etc, my WTRP V.2.7.8.0 changed to v.2.6.3.1 and stuck in kindle fire logo and not connected to pc or not show storage in my computer.
please help me and restore my kindle fire tate. thanks a lot (i am using Ubuntu 14.04 LTS)
I have a second gen kindle fire (rooted) and looked and looked all over and have not seen any way to use custom launchers on my kindle fire. It downloads and installs but does not show up in the carousel or application list. i go into lucky patcher and it cannot open the launcher. Please give reason and or fix
illusion_insanity said:
I have a second gen kindle fire (rooted) and looked and looked all over and have not seen any way to use custom launchers on my kindle fire. It downloads and installs but does not show up in the carousel or application list. i go into lucky patcher and it cannot open the launcher. Please give reason and or fix
Click to expand...
Click to collapse
Try rebooting. It could also be intentional behavior on Amazon's side (they won't let you change the default launcher, and they might prevent you from even opening another one).
Sent from my Amazon Jem using XDA Labs
thanks
i am no a pro at this but i think someone said its because it has a locked bootloader.
illusion_insanity said:
i am no a pro at this but i think someone said its because it has a locked bootloader.
Click to expand...
Click to collapse
The issue isn't caused by a locked bootloader; however, unlocking or replacing the bootloader will allow you to use a custom ROM and sidestep the stock OS's restrictions.
Thanks
monster1612 said:
The issue isn't caused by a locked bootloader; however, unlocking or replacing the bootloader will allow you to use a custom ROM and sidestep the stock OS's restrictions.
Click to expand...
Click to collapse
I guess I can trial and error my way until it works! do you think I should just get cyanogem mod on it if I can't get a launcher?
illusion_insanity said:
I guess I can trial and error my way until it works! do you think I should just get cyanogem mod on it if I can't get a launcher?
Click to expand...
Click to collapse
Yep - it'd be more up to date than Amazon's stock OS, too.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Yep - it'd be more up to date than Amazon's stock OS, too.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
the thing is, I don't have the adb drivers to use kindle fire utility
illusion_insanity said:
the thing is, I don't have the adb drivers to use kindle fire utility
Click to expand...
Click to collapse
What OS are you using on your PC? If you're running Linux (Ubuntu, etc.), no drivers are needed.
windows
monster1612 said:
What OS are you using on your PC? If you're running Linux (Ubuntu, etc.), no drivers are needed.
Click to expand...
Click to collapse
I am using windows seven. but it wants me to have android sdk in the majority of the tutorials I've read
illusion_insanity said:
I am using windows seven. but it wants me to have android sdk in the majority of the tutorials I've read
Click to expand...
Click to collapse
The tutorials recommend you install the Android SDK, but unless you're planning on doing Android app development, most of the SDK will be useless. Instead of using the SDK (which is quite bulky), I'd recommend that you run the 15 second ADB installer, which can be downloaded here. Run the program as administrator, and when you're asked the questions, answer Yes/Y for the "install ADB and fastboot" and "install ADB system wide" questions, and No/N to the "Install device drivers" question. The reason we're not installing the drivers bundled with the installer is because the drivers are for Google devices, which will clearly not work with the Kindle.
Because of this, we're going to install the Kindle drivers separately. Go ahead and download the zip file in this thread, which contains installers for the Kindle drivers. Unzip the folder, run one of the executables as administrator, and install the drivers as prompted. You may get errors about installing unsigned drivers - continue anyway. Once the drivers successfully install, reboot your machine. Once you're rebooted, plug in your kindle (make sure it's booted into either recovery or a ROM). (NOTE: If you're booted into a ROM, you may get a prompt asking if you want to allow USB debugging. If you get this message, check the "Always allow from this computer" checkbox, and then OK.) Open a command prompt window and type adb devices. Below "list of devices attached", you should get a random string back (this is your device's ID) and either "unauthorized", "offline", or "device" next to it. If you don't see any text below "List of devices attached", then check to make sure ADB is enabled on your kindle (which it probably is if you rooted it ).
AWESOME
Have see it tried it yet but I will I gave ed up with sdk I have crap internet so it takes forever to download. I needed this thanks alot