Develop Bugs

[Q] Kindle Fire with 6.3 Help with Rooting Please

Hi,
I am a total noob. I don't even know the proper expressions for this whole thing.
So this is my case:
I am outside the US and bought the Kindle Fire with a 6.3 firmware, couple of days ago.
Being curious about what it all can do, created a fake account with a test credit card as I read somewhere in the net.
Then downloaded the KFU 0.9.5 and rooted the device, everything went according to the plan, so I thought.
Then I discovered I had to use something called Market Opener to install other apps. But this Market Opener never worked.
So I found out that I had to change permissions. But this cannot happen as I get that message that adb services can not run in production builds etc. whatever that may mean.
So I downloaded Android SDK, followed the instructions installed it but I still cannot get into the root and change folder permissions. Sometimes it recognizes the device, sometimes not and when it does it tells me the same thing as above.
Then I would need some .apk to do the thing on the device but I cannot install those as I don't have the Market Opener or the Google Play and I cannot get those if I don't have superuser permissions to change things in Folders.
Basically I have been spending the last 3 days in searching the net for answers but to no avail.
So, can someone help me please? What I need to do is being able to install some apps including Market Opener / Google Play and being able to watch Amazon VOD. Is this possible?
Please bear in mind that I have no clue of the specific language, i.e. I don't know what flash is and how to do it nor I know how to do a backup and restore or how to reset everything in the original state.
SO if some of you have the patience to help, please advice me with some noob language so that I can understand.
Thanks in advance for the help that will come

Are you looking to put a custom rom on it or just root? If you're looking to keep Amazon services, you can put MoDaCo's rom on it, which is just like your kindle out of the box with a few extra bells and whistles. There are alot of guides floating around on how to get ADB working. There's an excellent beginners guide in the General section that I highly advise checking out.
Noob terms: if you want to keep the Amazon experience, I reccomend MoDaCo. Look for it in the development fourms.

brainchow said:
Are you looking to put a custom rom on it or just root? If you're looking to keep Amazon services, you can put MoDaCo's rom on it, which is just like your kindle out of the box with a few extra bells and whistles. There are alot of guides floating around on how to get ADB working. There's an excellent beginners guide in the General section that I highly advise checking out.
Noob terms: if you want to keep the Amazon experience, I reccomend MoDaCo. Look for it in the development fourms.
Click to expand...
Click to collapse
Thanks for ur answer.
I have read a lot of guides out there but I seem not to be able to get the ADB working as I always get the message I gave in the original post plus the fact that sometimes it recognizes the device and sometimes not.
I have read the beginners guide which was excellent but without the ADB working there is little I can do I suppose.
As I wrote, I want to play with the device to see what it is able to do and want to use the Amazon VOD if possible. I.e. I would like to be able to use Google Play to get apps on will and still keep the Amazon services. Would that be possible with the MoDaCo staff?
Ok. I downloaded the MoDaCo staff.
Must I reset the kindle to the factory settings before I install that? If yes, how?
And how do I flash it?

Make sure you are in fact rooted.
You seem like you know enough about adb to try the following commands.
adb shell
ls /system/xbin
Look for a file called "su" in the list
Then...
ls /system/app
Look for a file called "Superuser.apk"
A lack of either of these means you're not rooted and may be the source of your problems
If you are trying to change system file permissions through adb...
adb root
adb remount
adb shell chmod blah /blah/blah/yadayada
Just don't literally type "blah /blah/blah/yadayada"
Sent from my Amazon Kindle Fire using xda premium

a factory reset won't really help you because you're basically replacing the operating system. pretty sure all amazon services are working with modaco. to install it, look around for a guide on how to install something called firefirefire (FFF) and TWRP. pretty sure that can all be done with kfu in a couple clicks. then copy the modaco zip onto your kindle, go into the wipe menu and clear out system, cache, dalvik cache, and data (factory reset), then go into install and choose the modaco zip. reboot and you should be set.

soupmagnet said:
Make sure you are in fact rooted.
You seem like you know enough about adb to try the following commands.
adb shell
ls /system/xbin
Look for a file called "su" in the list
Then...
ls /system/app
Look for a file called "Superuser.apk"
A lack of either of these means you're not rooted and may be the source of your problems
If you are trying to change system file permissions through adb...
adb root
adb remount
adb shell chmod blah /blah/blah/yadayada
Just don't literally type "blah /blah/blah/yadayada"
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Thank you for your answer.
I would gladly follow your advice but the adb does not find my device. I don't know whether this is normal and if I must reboot my PC.
The kfu also gives me an offline status...

brainchow said:
a factory reset won't really help you because you're basically replacing the operating system. pretty sure all amazon services are working with modaco. to install it, look around for a guide on how to install something called firefirefire (FFF) and TWRP. pretty sure that can all be done with kfu in a couple clicks. then copy the modaco zip onto your kindle, go into the wipe menu and clear out system, cache, dalvik cache, and data (factory reset), then go into install and choose the modaco zip. reboot and you should be set.
Click to expand...
Click to collapse
Thanks again for the fast answer. I am impressed!
Doesn't the FFF and the TWRP get installed automatically with the kfu?

its most likely your computer. a reboot might help. if not, how did you install the drivers? are you using a mac or pc? try installing the drivers that came bundled with KFU.
if you're using a PC, go into device manager and see if something about android ADB pops up. if not, it's your drivers.
---------- Post added at 07:53 PM ---------- Previous post was at 07:51 PM ----------
GreekCY said:
Thanks again for the fast answer. I am impressed!
Doesn't the FFF and the TWRP get installed automatically with the kfu?
Click to expand...
Click to collapse
haha, no problem .
if FFF was installed, you should see a picture of fire in a caution sign or an android logo over the kindle fire logo when you boot it up. if all you see is kindle fire, then you don't have fff. im pretty sure you need fff to get into twrp. if fff is installed, you should be able to hop into fastboot and install twrp if it's not installed yet.

brainchow said:
its most likely your computer. a reboot might help. if not, how did you install the drivers? are you using a mac or pc? try installing the drivers that came bundled with KFU.
if you're using a PC, go into device manager and see if something about android ADB pops up. if not, it's your drivers.
Click to expand...
Click to collapse
I am using a PC ( a netbook, don't laugh, I'm on vacation!!)
I installed the drivers using the install_bat from the kfu.
In device manager I see Android Phone and underneath Android Composite ADB Interface...

interesting. check my previous post and see if you have FFF installed. adb should be working fine if device manager can find it. if you can, run adb devices into cmd and see if it picks up your kindle. not sure if the stock rom has a development switch in the settings.. if there's an option to enable usb debugging, make sure that is on. if not, just try moving usb ports and running adb devices.

If adb has trouble recognizing your device, it means it's a driver issue. Either Windows, KFU or a combination of the two causes the drivers to fail for some reason.
Uninstall/delete your current drivers in device manager (may require reboot)
Turn your Kindle off
Reinstall drivers
Turn your Kindle on
Retry adb commands
Sent from my Amazon Kindle Fire using xda premium

brainchow said:
interesting. check my previous post and see if you have FFF installed. adb should be working fine if device manager can find it. if you can, run adb devices into cmd and see if it picks up your kindle. not sure if the stock rom has a development switch in the settings.. if there's an option to enable usb debugging, make sure that is on. if not, just try moving usb ports and running adb devices.
Click to expand...
Click to collapse
I have FFF as I see the fire in a caution sign (yellow triangle thing right?)
ADB still doesn't pick my kindle after a PC restart.
No usb debugging available in the stock rom.
I will uninstall and reinstall the drivers from device manager.
Thanks again for your prompt help. I am oblidged!

GreekCY said:
I have FFF as I see the fire in a caution sign (yellow triangle thing right?)
ADB still doesn't pick my kindle after a PC restart.
No usb debugging available in the stock rom.
I will uninstall and reinstall the drivers from device manager.
Thanks again for your prompt help. I am oblidged!
Click to expand...
Click to collapse
that's fantastic... if you have FFF, try pressing the power button a couple times as it turns on and see if you can get into recovery. you shouldn't need adb now. if you can get into recovery, just wipe and flash the new rom. if you don't, you can use fastboot to install it.

brainchow said:
that's fantastic... if you have FFF, try pressing the power button a couple times as it turns on and see if you can get into recovery. you shouldn't need adb now. if you can get into recovery, just wipe and flash the new rom. if you don't, you can use fastboot to install it.
Click to expand...
Click to collapse
Ok...I reinstalled the drivers
now ADB gets the kindle
I do adb shell
then ls / system /xbin
no such file or directrory
the same goes with the
ls / system / app
But if I give su I get
su
#
Now what?
And in which directory should I transfer the MoDaCo Rom?

GreekCY said:
Ok...I reinstalled the drivers
now ADB gets the kindle
I do adb shell
then ls / system /xbin
no such file or directrory
the same goes with the
ls / system / app
But if I give su I get
su
#
Now what?
Click to expand...
Click to collapse
SU (substitute user) in shell is different from the su binary
Make sure you are typing "L"s, not "i"s then /system/xbin
Sent from my Amazon Kindle Fire using xda premium

soupmagnet said:
SU (substitute user) in shell is different from the su binary
Make sure you are typing "L"s, not "i"s then /system/xbin
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I really do type "L"...still ls/system/xbin: not found

modaco can go anywhere in the kindle.. just copy it somewhere. then press the power button a couple times when FFF comes up and see if you can get into twrp.

brainchow said:
modaco can go anywhere in the kindle.. just copy it somewhere. then press the power button a couple times when FFF comes up and see if you can get into twrp.
Click to expand...
Click to collapse
Guys? I just installed ModaCo and it seems it works fine. Google Play seems to work and all my data are still there (I mean the books I uploaded). If this is right then.... THANKS TO ALL OF YOU SO MUCH!!!!
Drinks are on me! Now I go to sleep! Will keep you informed!!!
Thanks again!!!!

GreekCY said:
I really do type "L"...still ls/system/xbin: not found
Click to expand...
Click to collapse
Space between ls and /system/xbin and no other spaces
It IS there, your Kindle wouldn't work otherwise
Sent from my Amazon Kindle Fire using xda premium

GreekCY said:
I really do type "L"...still ls/system/xbin: not found
Click to expand...
Click to collapse
if you want to use adb, should be ls /system/xbin. make sure you put the space after the ls. i would still recommend flashing modaco nevertheless... that shouldn't need adb. just maybe fastboot if your recovery isnt installed.
---------- Post added at 08:59 PM ---------- Previous post was at 08:57 PM ----------
GreekCY said:
Guys? I just installed ModaCo and it seems it works fine. Google Play seems to work and all my data are still there (I mean the books I uploaded). If this is right then.... THANKS TO ALL OF YOU SO MUCH!!!!
Drinks are on me! Now I go to sleep! Will keep you informed!!!
Thanks again!!!!
Click to expand...
Click to collapse
no problem... enjoy
i would still recommend wiping data and the two caches to ensure that it's bug free. but if everything works fine, so be it.
have fun

Kindle Fire Sort-of Bricked

Can you get into recovery
You probably should just flash a new rom
Sent from my Kindle Fire using xda premium
if you find something I posted helpful please thank me

Did you try wiping then recovering
Sent from my Kindle Fire using xda premium
if you find something I posted helpful please thank me

For future reference, when you're working from recovery:
adb shell mount system
adb push framework-res.apk /system/framework/
adb shell umount system
adb reboot

Josepho1997 said:
So, I was going to replace my framework-res(don't ask why), but I wanted to keep a backup of it. So, I renamed it framework-res.apk1, and was planning to put the modded one in /system/framework. But, once I renamed it, everything crashed. I got a bunch of Chinese/Japanese writing(don't ask me why ). Now nothing will open and my notification bar is gone. Anyways, I rebooted into recovery and mounted from there(because it wouldn't mount). Now I need to know how to install framework-res.apk to /system/framework using adb. I tried:
I've never needed to install an apk with adb, so I don't even know if thats the right code.
EDIT: I used:
to move it to /system/framework
I tried using
but it just gives me the list of option for adb(like when you first open it)
EDIT:
I tried to make it RW by using:
EDIT:
Great! Now it won't even get to the boot animation. Its stuck on the White and orange Kindle Fire screen(before it gets to the boot animation)
Click to expand...
Click to collapse
Yeah like stated above, you need to use adb push because you are just moving it not actually installing it.

also a tip for replacing your framework.
put new framework.apk on sdcard then with root explorer copy or move to the main directory and fix permissions, then move to framework and paste, it will ask if you want to over write other apk say yes, your phone will reboot with the new framework apk.
if you want a backup just copy the original first and save it somewhere else.
Sent from my Galaxy Nexus using xda premium

Can't copy GoogleServicesFramework.apk to /system/app directory

I have been able to root my Kindle and want to get the store working.
I think I need to copy the Google Services Framework APK to the /system/app directory.
I am using ES File Explorer version 1.6.2.5.
My Kindle is version 6.3.2.
When I try to copy the file from the SD card to the /system/app directory it says unable to copy.
Thanks in advance for the help

Did you mount system as read/write?

I'm afraid I don't know what that means. I used KFU 0.9.6 to root the device. I had installed ES file explorer before I did the rooting. Does explorer need to be read/write, or is that an option for KFU? Is it an option I can change or do I have to re-install something?

robvia said:
I'm afraid I don't know what that means. I used KFU 0.9.6 to root the device. I had installed ES file explorer before I did the rooting. Does explorer need to be read/write, or is that an option for KFU? Is it an option I can change or do I have to re-install something?
Click to expand...
Click to collapse
ES File Explorer should have the option to do so, but I don't use it so I couldn't say for sure. If you can't figure it out, I'm sure someone around here will be able to help.

I found the Root settings in ES F E and checked the option for Root Explorer. It gave me a message that test fails option not allowed on your phone. Not sure if that is what I should be looking for or not.

robvia said:
I found the Root settings in ES F E and checked the option for Root Explorer. It gave me a message that test fails option not allowed on your phone. Not sure if that is what I should be looking for or not.
Click to expand...
Click to collapse
Do you have an ADB connection?

The Mount File System option is greyed out.
Below that it says Mount/ , /system as writable.
Does that have to be installed after the rooting is done?
Is there another file explorer option that is better?
Should I uninstall and re-install ES?

ES is on the Kindle. I have copied the APK to the kindle and to the SDcard directory. When I am connected to the computer, my computer only has access to the sdcard directory. I can't even see the /system folder.
ES can see the folder, but can't write to it.

robvia said:
ES is on the Kindle. I have copied the APK to the kindle and to the SDcard directory. When I am connected to the computer, my computer only has access to the sdcard directory. I can't even see the /system folder.
ES can see the folder, but can't write to it.
Click to expand...
Click to collapse
You still didn't answer my question. Do you have a connection with ADB? You were able to root it weren't you? You must have had an ADB connection at some point.

Sorry, Since I was trying to copy the file with out the device connected to the computer, I didn't think it mattered.
When connected to the computer, in device manager, it's Android Composite ADB Interface.
The Kindle shows up as a drive in Windows Explorer. At one point when I was doing the root, it did not show up as a drive.
If I can copy from my computer to the /system directory, that would be great, but since i don't have access to that through the computer, I was copying from the download directory on the Kindle to the /system directory on the Kindle.

robvia said:
Sorry, Since I was trying to copy the file with out the device connected to the computer, I didn't think it mattered.
When connected to the computer, in device manager, it's Android Composite ADB Interface.
The Kindle shows up as a drive in Windows Explorer. At one point when I was doing the root, it did not show up as a drive.
If I can copy from my computer to the /system directory, that would be great, but since i don't have access to that through the computer, I was copying from the download directory on the Kindle to the /system directory on the Kindle.
Click to expand...
Click to collapse
You say you used the KFU to root...do you still have it available? Run it and see if it shows ADB ONLINE.

Yes, the ADB status is online when I run KFU. I also ran Super One Click and it said your device apears to be rooted.
I also installed the app, mount /system (rw/ro).
when I select mount rw, it says the system dir remounted with r/w permission.

robvia said:
Yes, the ADB status is online when I run KFU. I also ran Super One Click and it said your device apears to be rooted.
I also installed the app, mount /system (rw/ro).
when I select mount rw, it says the system dir remounted with r/w permission.
Click to expand...
Click to collapse
Soooo...problem solved, right?

I wish it were that easy. Even though it says it's mounted in r/w mode, I can't get it to copy. Should I try and root it again? Could I have done something wrong? I used KFU and did root with superuser. Should I use Super One Click and unroot then try to root again? I don't remember any options for me to select wrong. Is there a PC tool that alllows you to copy directly to the /system directory? I really thought I was past the hard part. Thanks again for all the help.

Okay, since you have KFU and you have connection with ADB, press Shift then Right-click on the KFU "tools" folder and select "Open command window here". At the command prompt that opens up enter the following (omitting the comments in red, of course) ;
Code:
$ adb push /local/path/to/GoogleServicesFramework.apk /sdcard/ [COLOR=Red]<-- Replace "/local/path/to/..." with the location of GoogleServicesFramework.apk on your computer
[/COLOR]
$ adb shell
$ su [COLOR=Red]<-- If you receive an error here, you need to re-root
[/COLOR]~ # mount -o remount,rw ext4 /system [COLOR=Red]
[/COLOR]~ # mv /sdcard/GoogleServicesFramework.apk /system/app/GoogleServicesFramework.apk
~ # chmod 644 /system/app/GoogleServicesFramework.apk
~ # pm install -r /system/app/GoogleServicesFramework.apk
do the same for AccountAndSyncSettings and GoogleLoginService, reboot, then do the same for Vending.apk (I'm assuming you are trying to install the Market, right?)

Ok. I think I might see the issue. When I rooted the Kindle I did not have the apk copied to the device. It looks like there is a move command that copies the APK file from the SDcard to /sysstem/app folder. I think I need to put the apk in the proper place on the device and then un-root and then try and root it again.
Yes I am tyring to get the market running.
So you are saying there are 3 files that need to be copies? I have the file com.android.vending_3.8.15.apk, but I do not have AccountAndSyncSettings.
The more I read your reply, I'm less sure of myself. Before I root with KFU (or maybe super one click) do I need to have files copied to the Kindle? I guess I would have expected KFU to have these files, but OK if not included. Does KFU attempt to copy the framework file to the proper directory? If so, where does the files need to exist before starting?
I think your instructions here are a command line version of what I am trying to do with ES File Explorer. Is that true?

robvia said:
Ok. I think I might see the issue. When I rooted the Kindle I did not have the apk copied to the device. It looks like there is a move command that copies the APK file from the SDcard to /sysstem/app folder. I think I need to put the apk in the proper place on the device and then un-root and then try and root it again.
Yes I am tyring to get the market running.
So you are saying there are 3 files that need to be copies? I have the file com.android.vending_3.8.15.apk, but I do not have AccountAndSyncSettings.
The more I read your reply, I'm less sure of myself. Before I root with KFU (or maybe super one click) do I need to have files copied to the Kindle? I guess I would have expected KFU to have these files, but OK if not included. Does KFU attempt to copy the framework file to the proper directory? If so, where does the files need to exist before starting?
I think your instructions here are a command line version of what I am trying to do with ES File Explorer. Is that true?
Click to expand...
Click to collapse
You need AccountAndSyncSettings. Are you using a tutorial for this? If so, which, one?
And yes, it is the command line version of what you're trying to accomplish with ES. It will give you more control and you'll be less likely to screw up.

Sure is rooted?
I recently back to stock firm to can check battery issues. I was using JB Hashcode very happy so far and was thinking go back again, but a short pass by the stock firmware was a really bad idea because got an update on the air (6.3.2) and lose my rooted status. I've used KFU again with no luck. Root explorer, droidwall says that i'm not rooted... So sad. Any ideas?

chocaru said:
I recently back to stock firm to can check battery issues. I was using JB Hashcode very happy so far and was thinking go back again, but a short pass by the stock firmware was a really bad idea because got an update on the air (6.3.2) and lose my rooted status. I've used KFU again with no luck. Root explorer, droidwall says that i'm not rooted... So sad. Any ideas?
Click to expand...
Click to collapse
What does this have to do with the topic at hand?

Sorry for not getting back earlier. My weekend included getting hit by a deer. Really messed all my plans up.
I used the instructions here http://forum.xda-developers.com/showthread.php?t=1399889.
These screenshots show an option to install Google Apps, but I don't see that option when I run it. I guess I'm a little confused. Are there different instructions I should be following?

can't get into settings after root

Hi, I rooted with KFF and now i can't swip from the top of the screen and i have no back arrow or home button. i was trying to remove root with KFF and bin4ry but no luck. Can somebody give me some instructions? Thanks

Rooting alone will not cause the type of problems you are describing. Have you installed a custom ROM, custom launcher, or any other alterations to /system that would require root privileges?

No 2nd bootloader. just root and i can't enable adb

Adb was required for root, it should still be enabled if you never were able to get into settings after root. Weird... If worst comes to worst u might have to reflash the system image, which on the bright side is prerooted. But I just don't see how rooting it could cause such a weird error, sounds like something got messed up with the systemui apk, and root doesn't modify that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

cubiche said:
No 2nd bootloader. just root and i can't enable adb
Click to expand...
Click to collapse
To remove "root", simply enter the following commands in a terminal emulator:
Code:
su
mount -o remount,rw /system
rm /system/app/Superuser.apk
rm /system/xbin/su
mount -o remount,ro /system
exit
But, be warned. If having "root" is not the source of your problem, as I suspect, and you have some additional changes to your /system directory that you've failed to mention, you will not only be stuck with the problem you had to begin with, but you will also not have root permissions or the adb connection you would need to fix your device.

He should be able to get it in fastboot though with the fastboot getvar product command if he plugs in his kindle when off after running it since a 8.9" model right? That would be useful even if adb is disabled.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

I can get into fastboot with kff, but I don't know where go from there.

You can restore a saved system.img, but it will still be rooted when it's finished.

I have a saved image from another kindle HD 8.9. I think it was 8.3.0. Will that work? Can someone will me through the process?

cubiche said:
I have a saved image from another kindle HD 8.9. I think it was 8.3.0. Will that work? Can someone will me through the process?
Click to expand...
Click to collapse
Code:
fastboot -i 0x1949 flash system system.img

Hey soupmagnet, thanks for the help. Is there a risk of bricking the tablet?

The risk is considerably lower than installing the 2nd bootloader.

How do I enter that line. From adb?

ok, i'm done but i'm stuck on the kindle fire screen.

Where did you get your system.img?
[Edit:] Nevermind. I forgot you already told us. Is it safe to assume you have a boot.img as well?

it was saved on my computer from a different hd 8.9. i saved it before frashing 2nd bootloader and twrp. should i also flash the recovery and boot?

yes i have boot and recovery.img

fastboot -i 0x1949 flash boot boot.img
That should fix it.

i flashed recovery, boot and system and still don't have the navigation buttons. system is still rooted, i assume because i flash a rooted system.img. i also have the stock-system, recovery and boot. do you think that will fix it?

I guess I assumed that's what you meant when you said you had saved images.
Unless you unpack, unroot and repack your system.img, it's going to be rooted either way because you have to have root permissions to save your system.img. But it seems beyond all logic and reasoning to think that having "root", which consists of two files that are completely independent of the systemui.apk and framework-res.apk, would have any effect on the navbar at all.
By all means, restore your stock images. I'm very interested to see if it has any effect.

Kindle fire 8.9 bricked need help

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