I tried using the Stunt's wallpaper fix today and I kept getting the following error messages:
First I got a message at the start saying "'findstr' is not recognized as an internal or external command, operable program or batch file"
Then, when I hit one and enter, i get an error message saying the memory is too low when I have over 10 GB of storage left.
I'm running 8.4.6 on the Kindle Fire HD 8.9"
It is has to do with the findstr error, I can't really do much to help your fix this outside of saying make sure the command prompt or batch file is being run as admin, because findstr is a command that is built into windows, if it's not finding it then either your computer is messed up or it's a permissions issue, or possibly Ur system paths are messed up.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
It is has to do with the findstr error, I can't really do much to help your fix this outside of saying make sure the command prompt or batch file is being run as admin, because findstr is a command that is built into windows, if it's not finding it then either your computer is messed up or it's a permissions issue, or possibly Ur system paths are messed up.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Ok so i tried running it as admin, but after selecting 1 and hitting enter, the window just closes down.
Probably closing from findstr error, if you can find command prompt on your start menu under accessories, then right click it and hit run as admin, CD to the wallpaper fix directory, and run the bat that way, it will show u why its closing, and I'm gunna take a guess at somehow your system paths are messed up.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Probably closing from findstr error, if you can find command prompt on your start menu under accessories, then right click it and hit run as admin, CD to the wallpaper fix directory, and run the bat that way, it will show u why its closing, and I'm gunna take a guess at somehow your system paths are messed up.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
This is the error message that i get:
Cleaning Up...
Could Not Find C:\Users\Ig-Jun\Downloads\Stunts Wallpaper Fix\framework-res.apk
Could Not Find C:\Users\Ig-Jun\Downloads\Stunts Wallpaper Fix\newframework-res.apk
Could Not Find C:\Users\Ig-Jun\Downloads\Stunts Wallpaper Fix\resources.arsc
The system cannot find the file specified.
'find' is not recognized as an internal or external command,
operable program or batch file.
*****************************************************************
* Stunt's Wallpaper Fix v2.1 *
*****************************************************************
* Notice a bug or unsafe portion of the script I've missed? *
* PM me(stunts513) on the xda forums! *
*****************************************************************
* Credit goes to pjeby and JulianPaoloThiry *
* Major credit to soupmagnet for overhauling my linux script *
* and cleaning it up! *
*****************************************************************
'findstr' is not recognized as an internal or external command,
operable program or batch file.
ADB Status: Online
Please make a selection or hit ENTER to exit:
'find' is not recognized as an internal or external command,
operable program or batch file.
Could Not Find C:\Users\Ig-Jun\Downloads\Stunts Wallpaper Fix\framework-res.apk.orig
Doing prelim checks...
***********************************************
* Your system partition is too low on disk *
* space to complete the procedure, please *
* delete your alternate launchers, widget *
* picker, and live wallpaper chooser if *
* installed and try again. *
***********************************************
rm: can't remove '/data/local/framework-res.apk.orig': No such file or directory
rm: can't remove '/system/framework/framework-res.tmp': No such file or directory
Press any key to continue . . .
Yea it is probably your system paths or something weirder, though I'm curious why the second reference said find instead of findstr. You should do some googling about windows and the paths variable, I might be able to help a bit, but usually it has several paths in it, but if its just missing a path that's standard it should be pretty easy to fix.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Yea it is probably your system paths or something weirder, though I'm curious why the second reference said find instead of findstr. You should do some googling about windows and the paths variable, I might be able to help a bit, but usually it has several paths in it, but if its just missing a path that's standard it should be pretty easy to fix.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
So what should I do to try and fix it?
Shotaku said:
So what should I do to try and fix it?
Click to expand...
Click to collapse
From here: http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/findstr-is-not-recognized-as-an-internal-or/87f77967-538c-4a77-a9d8-917b6e577a84
The reason is "environment variables"
Add "C:\Windows\System32" to the "Path" of "system variables" is OK.
Click to expand...
Click to collapse
See if that helps.
i tried that and it still doesn't work.
Also, after digging around, it seems as though the files are called framework-res.apk, framework.jar, and framework.odex in /system/framework
Um I don't know how framework.jar is related to this, but anyways, try running findstr from a command prompt, if your system paths are setup right it should work, if it still doesn't, go into I think its c:\windows\system32, and see if the command is in that folder, if not, it got deleted then there's your reason why its not working, and you should try finding a copy off the internet. If it is there and for some weird reason it still isn't working, copy findstr into the wallpaper fix directory, that might fix it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
this is the error message i get:
Could Not Find C:\Users\Ig-Jun\Downloads\Stunts Wallpaper Fix\framework-res.apk.orig
Doing prelim checks...
***********************************************
* Your system partition is too low on disk *
* space to complete the procedure, please *
* delete your alternate launchers, widget *
* picker, and live wallpaper chooser if *
* installed and try again. *
***********************************************
rm: can't remove '/data/local/framework-res.apk.orig': No such file or directory
rm: can't remove '/system/framework/framework-res.tmp': No such file or directory
Press any key to continue . . .
So wait what exactly did you do before running it?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
i did the RunMe as Run as administrator, hit one and enter, and that error message popped up
OK so I must realized (stupid me) that the fix got past the main selection screen this time, correct? If that is a the case that message is probably accurate, you can find out for sure by either running an adb shell or running a mobile terminal on the kindle and running this command to see what it outputs: df /system
That should tell you how much space is left on the system partition, if it errors, add the word "busybox" before it, but I think that command is built into the os.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I had the same problem.
The script requires that you have 40MB of free space in your kindle's /system directory.
I simply opened a command prompt in the Wallpaper Fix folder and ran "adb shell "df /system" to check how much space was left. I had to delete some kindle bloatware (Specifically the OfficeSuite demo) to make more space as I think I had 39MB free.
what would be safe to remove?
Any launchers you installed and aren't using, the widget picker, live wallpaper picker. Those are the things I typically see that use up that space.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
It worked! Thanks!
Related
Daughter installed an app named Smart App Protector on her Kindle Fire and forgot the password. The app prevents access to anything. Worked with Amazon and can't do anything that gets around it, they even deregistered it. Finally suggested going through Android Debugger Bridge. After researching, found this forum. Have searched for similar question. So,
1) Can ADB be used to remove that app and leave Kindle as it was?
2) If I need to reset to Stock, which set of instructions on this forum should I follow. Still downloading all of the Android SDK files and have downloaded Kindle Fire Utility 0.9.6, but haven't installed.
How familiar are you with adb and/or basic shell commands?
Complete novice
To use adb you must do so while booted into custom recovery since Amazon has disabled it.
Assuming you have custom recovery installed and you are rooted you need to search a few directories to find where the program and it's data are installed.
The directories (path to) are...
/data/app (for apks installed on internal memory)
/data/data (for app data stored on internal memory)
/system/app (for system apks, just in case)
/sdcard/android/data (for app data stored on sdcard)
You need to open a shell in adb
Code:
adb shell
...your prompt will change to a #. From here you'll need to know a couple commands.
Code:
ls
("ell ess" to list the files in a particular directory)
Code:
rm
(to remove or delete a particular file or directory)
First pick a directory and list the contents
Code:
ls /data/app
When you find the file or folder you want removed...
Code:
rm /data/app/problematic_file.apk
"Data" folders will only contain folders, not apks. Sometimes they are named kind of weird but if you look closely enough you can figure out the right one to delete.
If you are running 100% stock, you'll have to install custom recovery to go any further, even if you want to revert back to full stock.
thanks, but KFU status says ADB status is <offline> and boot status is <unknown>. Since I can't get past the 'enter password' screen on the Kindle, i can't change anything from it. From Windows Devices, it shows the Kindle as a Android ADB Interface, so the kfu must have loaded properly.
Make sure you're in recovery and reinstall your drivers if you have to.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
If you don't have access to recovery, you'll have to use fastboot to install it.
Hello. I was trying to Root my 1st gen Kindle Fire with KFU, but when I type 2 to Install Permanent Boot, I encounter several problems:
'find' is not recognized as an internal or external command,
operable program or batch file.
***********************************************
* Installing Permanent Root *
***********************************************
***********************************************
* Activating Fastboot (4002) *
***********************************************
2756 KB/s (510876 bytes in 0.181s)
fail opening shift: No such file or directory
The kindle has been told to reboot in Fastboot Mode.
twrp.img is missing.
So we will download it for you!
'find' is not recognized as an internal or external command,
operable program or batch file.
'find' is not recognized as an internal or external command,
operable program or batch file.
wget: missing URL
Usage: wget OPTION... URL...
Try `wget --help' for more options.
Cannot open input file recovery\twrp.img
Download successful.
fff.bin is missing.
So we will download it for you!
'find' is not recognized as an internal or external command,
operable program or batch file.
'find' is not recognized as an internal or external command,
operable program or batch file.
wget: missing URL
Usage: wget OPTION... URL...
Try `wget --help' for more options.
Cannot open input file recovery\fff.bin
Download successful.
***********************************************
* NOTICE *
***********************************************
'find' is not recognized as an internal or external command,
operable program or batch file.
'find' is not recognized as an internal or external command,
operable program or batch file.
Fastboot uses a different device than ADB.
You should check device manager for "Kindle" or "Amazon"
If you see it, rerun the driver installer that came packaged with KFU.
Installing FFF...
Cannot open input file recovery\fff.bin
error: cannot load 'recovery\fff.bin'
Installing TWRP...
Cannot open input file recovery\twrp.img
error: cannot load 'recovery\twrp.img'
Setting Recovery Bootmode.
< waiting for device >
I don't know why all of this is happening, I followed several tutorials for Rooting with KFU. I've looked everywhere for a fix to this, but I've yet to find one. Hopefully someone could tell me what I'm doing wrong?
Looks like at least one or two possible things driver and possibly java try installing jdk and reinstalling the driver. What os are you using? Could also be a corruption in the kfu you are using as well redownload it.
Okay
Thepooch said:
Looks like at least one or two possible things driver and possibly java try installing jdk and reinstalling the driver. What os are you using? Could also be a corruption in the kfu you are using as well redownload it.
Click to expand...
Click to collapse
I'll try what you said, and I am using Windows 7
UPDATE: I reinstalled JDK, the drivers, and KFU, yet still getting the same things. I've tried this on two computers, both running Windows 7.
Sounds like your path in windows might not be set up properly. Search the KFU thread for my post on what to look for. If I remember correctly it was that C:\Windows\system32 has to be in the PATH environment variable.
EDIT: Found it:
Check your PATH variable in Windows. Either view it by right clicking on My Computer and selecting Properties, then going to the Advanced Tab and selecting Environment Variables, or open a CMD window and type
echo %path:;=&echo.%
That will show all the entries, each on a new line so they are easier to read. Make sure there is a path entry for C:\WINDOWS\system32. If there is not add the following:
%SystemRoot%\system32
redbean25 said:
Sounds like your path in windows might not be set up properly. Search the KFU thread for my post on what to look for. If I remember correctly it was that C:\Windows\system32 has to be in the PATH environment variable.
EDIT: Found it:
Check your PATH variable in Windows. Either view it by right clicking on My Computer and selecting Properties, then going to the Advanced Tab and selecting Environment Variables, or open a CMD window and type
echo %path:;=&echo.%
That will show all the entries, each on a new line so they are easier to read. Make sure there is a path entry for C:\WINDOWS\system32. If there is not add the following:
%SystemRoot%\system32
Click to expand...
Click to collapse
There is a path entry for C:\Windows\system32. So then what's wrong?
UPDATE: Okay, sorry about that, one of the computers has the path entry, the other doesn't, but when I try %SystemRoot%\system32 it says
'C:\Windows\system32' is not recognized as an internal or external command,
operable program or batch file.
If it's something simple, I apologize for my ignorance.
UPDATE: I just got it working on one of the Computers, but at one point it says
***********************************************
* NOTICE *
***********************************************
Fastboot uses a different device than ADB.
You should check device manager for "Kindle" or "Amazon"
If you see it, rerun the driver installer that came packaged with KFU.
Installing FFF...
< waiting for device >
It's been like that for 10 minutes or so. What do I do?
Madnessfan34537 said:
There is a path entry for C:\Windows\system32. So then what's wrong?
UPDATE: Okay, sorry about that, one of the computers has the path entry, the other doesn't, but when I try %SystemRoot%\system32 it says
'C:\Windows\system32' is not recognized as an internal or external command,
operable program or batch file.
If it's something simple, I apologize for my ignorance.
UPDATE: I just got it working on one of the Computers, but at one point it says
***********************************************
* NOTICE *
***********************************************
Fastboot uses a different device than ADB.
You should check device manager for "Kindle" or "Amazon"
If you see it, rerun the driver installer that came packaged with KFU.
Installing FFF...
< waiting for device >
It's been like that for 10 minutes or so. What do I do?
Click to expand...
Click to collapse
Reboot the device and it should continue when it reboots .
redbean25 said:
Reboot the device and it should continue when it reboots .
Click to expand...
Click to collapse
Nothing happens.
Madnessfan34537 said:
Nothing happens.
Click to expand...
Click to collapse
Sound like the driver for fast boot mode is not installed correctly then. Double check that your drivers are installed properly.
redbean25 said:
Sound like the driver for fast boot mode is not installed correctly then. Double check that your drivers are installed properly.
Click to expand...
Click to collapse
Everything seems to be in order, hmm.
UPDATE: I was trying to do other things through cmd with the Kindle Fire, and it would say <waiting for device> every time. There is definitely something wrong, I just don't know how to fix it, because I don't know what exactly is wrong. Someone help?
UPDATE: Screencap of what's going on http://i.imgur.com/rjx0azF.jpg
The kindle fire 8.9 is disabled wallpaper.
I fixed it by modify framework.odex and services.odex (no lost any 8.4.3 functions) files.
Step:
1. Nandroid backup
2. Copy two files to /system/framework/
3. Change permission to 644 (rw-r--r--) for two files
4. Reboot
5. Enjoy!
does this really work?
I recently rooted my Kindle Fire HD 8.9. I have Superuser and ES File Explorer. I don't have permissions to delete or overwrite the two files you mentioned. What's the best way to approach this? Should I change the permissions to 777 for the files and then overwrite them? Will i be able to do this. Did I need to have done the 2nd bootloader - TWRP thing? Any help would be appreciated... also I need to find the nandriod backup procedure as I have not done this yet.
maxwelledison said:
I recently rooted my Kindle Fire HD 8.9. I have Superuser and ES File Explorer. I don't have permissions to delete or overwrite the two files you mentioned. What's the best way to approach this? Should I change the permissions to 777 for the files and then overwrite them? Will i be able to do this. Did I need to have done the 2nd bootloader - TWRP thing? Any help would be appreciated... also I need to find the nandriod backup procedure as I have not done this yet.
Click to expand...
Click to collapse
you need to mount your system partition as rw, then everything will be ok. actually, i use root explorer, much better thsn es file explorer
binhgreat said:
you need to mount your system partition as rw, then everything will be ok. actually, i use root explorer, much better thsn es file explorer
Click to expand...
Click to collapse
So close... I just did that. When I copied to the framework directory it says "not enough space"
required space: 12.46 MB
available space: 12.25 MB
Can i free up space? How and what could I remove?
binhgreat said:
you need to mount your system partition as rw, then everything will be ok. actually, i use root explorer, much better thsn es file explorer
Click to expand...
Click to collapse
Off topic but- yes it is! I've been loving the update to root explorer as well. Was using BOTH until the latest update. The dev on root explorer is just awesome.
Sent from my SGH-I727 using Tapatalk 2
binhgreat said:
you need to mount your system partition as rw, then everything will be ok. actually, i use root explorer, much better thsn es file explorer
Click to expand...
Click to collapse
I freed space in the system folder by converting some system apps to user apps... nothing important... just some launchers i installed. When I copied the files you included and clicked overwrite.. the kindle rebooted in the middle... not even sure both files copied. I got the system rcovery screen and tried reboot. Now it's just a reboot loop. Help!
---------- Post added at 07:57 PM ---------- Previous post was at 07:31 PM ----------
maxwelledison said:
I freed space in the system folder by converting some system apps to user apps... nothing important... just some launchers i installed. When I copied the files you included and clicked overwrite.. the kindle rebooted in the middle... not even sure both files copied. I got the system rcovery screen and tried reboot. Now it's just a reboot loop. Help!
Click to expand...
Click to collapse
Well...looks like it's bricked. Not sure. I get the Kindle Fire System Recovery screen every time. I can't even shut down. Two options... Reboot your kindle and Reset to factory defaults. Not sure there's anything I can do. If anyone can help... please let me know.
Well...looks like it's bricked. Not sure. I get the Kindle Fire System Recovery screen every time. I can't even shut down. Two options... Reboot your kindle and Reset to factory defaults. Not sure there's anything I can do. If anyone can help... please let me know.[/QUOTE]
Well, I think that you copy one by one?
If you enabled ADB then you can do as bellow:
I assume that you place those two odex files at /sdcard/
1. Plug usb cable to PC
2. Boot your kindle fire hd
3. On the PC command line, type
Code:
adb logcat
4. When you see the logcat output, then press Ctrl+C, and do as bellows
Code:
adb shell
su
mount -o rw,remount /system
cp /sdcard/framework.odex /system/framework/
cp /sdcard/services.odex /system/framework/
chmod 644 /system/framework/framework.odex
chmod 644 /system/framework/services.odex
5. Do it and let me know the result
binhgreat said:
Well...looks like it's bricked. Not sure. I get the Kindle Fire System Recovery screen every time. I can't even shut down. Two options... Reboot your kindle and Reset to factory defaults. Not sure there's anything I can do. If anyone can help... please let me know.
Click to expand...
Click to collapse
Well, I think that you copy one by one?
If you enabled ADB then you can do as bellow:
I assume that you place those two odex files at /sdcard/
1. Plug usb cable to PC
2. Boot your kindle fire hd
3. On the PC command line, type
Code:
adb logcat
4. When you see the logcat output, then press Ctrl+C, and do as bellows
Code:
adb shell
su
mount -o rw,remount /system
cp /sdcard/framework.odex /system/framework/
cp /sdcard/services.odex /system/framework/
chmod 644 /system/framework/framework.odex
chmod 644 /system/framework/services.odex
5. Do it and let me know the result[/QUOTE]
PC does not recognize the device so can't pass commands to it...it is bricked.
THANKS!!!
Thanks a lot :good: I've been surfing XDA for years.. but never made an account.. I made this just to thank you :fingers-crossed: You made the impossible possible.. I've been trying to solve this since a month.. Thanks a lot :good:
does it apply to kindle fire hd7?
dustpop said:
does it apply to kindle fire hd7?
Click to expand...
Click to collapse
Afaik yes. But to be save make a nandroid backup.
Gesendet von meinem Amazon Kindle Fire2 mit Tapatalk 2
I am curious what exactly you did to fix this, you said it replaces or puts 2 files in your system framework folder? I am just curious of the method because I released a script that fixes the black background of x.4.1 and up, has safeties in it too to make it fairly safe since there some bricks initially. My fix modifies the framework-res.apk, so I am curious how this fix works differently, it didn't seem like you were modifying the framework-res.apk.
If you happened to be interested in looking at my fix it is on page 8 of this link.
http://forum.xda-developers.com/showthread.php?t=2295750
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
would you give me a instruction on how to use nandroid to backup kftt?
Fixed wallpaper issue kindle 8.9
stunts513 said:
I am curious what exactly you did to fix this, you said it replaces or puts 2 files in your system framework folder? I am just curious of the method because I released a script that fixes the black background of x.4.1 and up, has safeties in it too to make it fairly safe since there some bricks initially. My fix modifies the framework-res.apk, so I am curious how this fix works differently, it didn't seem like you were modifying the framework-res.apk.
If you happened to be interested in looking at my fix it is on page 8 of this link.
http://forum.xda-developers.com/showthread.php?t=2295750
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Stunts: I replaced the two odex files in system/framework with the two like files in this zip and I had wallpapers immediately.
I first tried the stunts fix script in LINUX with a fresh 8.4.3 OS without ADW launcher being installed.
Ran the LINUX script which ran successfully (At least there are two framework.res files now - one named .orig)
Rebooted Kindle and installed ADW launcher using KFFA and still had my black screen and I was not able to add any wallpaper with long press.
I then took the two odex files from this wallpaper fix zip file and placed them in the system/framework folder and changed permissions.
When I long pressed the desktop and selected a wallpaper, I was now able to select save and my desktop had a wallpaper.
I am not sure how these two files differ from the recompiling method but, I now have wallpapers....
BTW: It is really difficult to find a wallpaper that is no blury on the Kindle Fire HD.........?
______________________________________________________
Update: I blew away the OS on the kindle 8.9 and reloaded from scratch:
1: Rooted the tablet
2: Installed Fireflash and File Manager.
3: Transferred the two odex files from this post zip file onto the SDcard
4: Transferred the "default-honeycomb-wallpapers-bucky.jpg" file to the SDcard
Wallpaper post: http://forum.xda-developers.com/showthread.php?p=20804452
4: Installed 2nd bootloader using fireflash
5: Using File Manager, renamed framework.odex, and services.odex in the system/framework folder.
6: Using File Manager, copied the two ODEX files from the SDcard to the system/framework folder and changed permissions.
7: Using File Manager, transfered the ADW launcher "org.adw.launcher-1.apk" to the system/app folder and changed permissions.
Could have used KFFA as well to install ADW launcher
8: Rebooted the tablet and ADW was offered as my default launcher.
9: Long pressed the desktop and chose the default_honeycomb_wallpaper.jpg as my wallpaper, clicked save and the desktop changed to the wallpaper.
10: In this case, no Stunts wallpaper fix was applied and wallpapers work perfectly. I have no idea if the two ODEX files are the same for the KFHD7 tablet or not.
Regards
Will it work on Kindle Fire 2 7"?
being patient
I have a 2nd gen KF 10.4.3. I rooted it and put a few working launchers on it. of course everything works except the wallpapers. i noticed that xda is coming out with answers but the answers they have at the moment are a little bit too complicated and risky. I am confident that they will figure out a way to get these wallpapers working without twrp and 2nd bootloader. i really dont wanna have to go that route cuase like I said, the only thing i need is a wallpaper. i have widgets, play store all that good stuff. just trying to find a easier way to get wallpapers.
You don't have to have twrp and second boot loader for this method and mine, its just highly recomended because its much easier to fix in case you get stuck in a boot loop, that way you wouldn't need a fastboot cable to fix it, though if u mess up flashing 2nd boot loader you may need one anyway. My latest release isn't near as risky because I added a safety to prevent the main cause of bricks my script was generating. So it should be much safer if u want to have a look.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
giving it a try
Ive been following you on here and I noticed that you bricked your device quite a few times doing this. Im not nearly as smart as you and if i brick my device, im affraid i wont be able to fix it. I will have another look. Im not sure if I saw your latest release. Do you have a link to that page? or a video tutorial would be awesome.:good::highfive:
Its page 8 on this thread: http://forum.xda-developers.com/showthread.php?t=2295750
Not sure how to make a link directly to it from my kindle.
I would love to have a video tutorial of using it, but I don't run stock anymore, I am on cm 10.1 tablet ui, I have been avoiding flashing back so I don't have to reflash my boot loader in case my os updates from my backup I have. I could attempt to record a video tutorial sometime I suppose, though I will say this now, my PC is from 2003, it has a single core processor and 2gb of ram, so screen capture may be laggy if I do it, especially in windows, I use Linux by default partially because I need to reformat windows but my 1tb backup drive has no space left on it.... Yes I somehow managed to use it all up, and its such a drag to sort through it. If someone else would do it before me then I wouldn't mind in the least, it would be very helpful.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I am going to follow this thread and when the fix for the wallpaper is reliable and not likely to brick my device I might try it.
I have a Kindle Fire HD 8.9 32 GB. I rooted it recently and installed Google Play, which is working fine for me. After installing Golauncher Ex I realized that the wallpapers would not install. That led me here. See a lot of people bricking their kindles and I don't want to risk that, at least not right now an SANS factory cable. I would rather just revert to the carousel.
Thanks to all the developers and hackers here that devote so much time to helping the rest of us out here! I couldn't have rooted or installed Google Play without the information on this site.
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
hello, after some trouble installing the bootloader, I finally got it!!
But I have another problem, I thought it would start no problem then, so here I have no rom in sd!! and now will not start!
I can go into recovery mode, go to the usb storage option, but it does not work, I get on the computer!!
some way to spend a rom to the sd from l recovery / TWRP??????
Put the ROM and gapps in the same folder as an adb command, open a command prompt and CD to the directory with adb, now type something along the lines of this: adb push romname.zip /sdcard/
That should put the ROM on the sdcard so you can flash, use same thing for gapps as well.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Put the ROM and gapps in the same folder as an adb command, open a command prompt and CD to the directory with adb, now type something along the lines of this: adb push romname.zip /sdcard/
That should put the ROM on the sdcard so you can flash, use same thing for gapps as well.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
thank you!
the problem is that now ADB does not recognize the tablet.
In device manager, I get the yellow triangle on kindle fire.
Reinstall the SDK but nothing, still without recognizing
EDIT I finally got it! you saved my life!! thank you very much!!