> Attention!

We strongly recommend to readRules section "Android - firmware"

New threads need to be created only inroot partition! In the future, they will be processed by moderators.



Amazon Kindle Fire - Firmware



Rep: (175)
Amazon Kindle Fire - Firmware
PictureKindle fire
Description | Discussion » | Purchase » | Firmware »

Important information!
This topic applies only to the first generation Kindle Fire. See the firmware version!6.С….С…_user_xxxxxxxxx - it means to you here)
Do not attempt to do the following manipulations on the Kindle Fire 2 gen (10.x.x_user_xxxxxxxxx), HD 7 "(7.x.x_user_xxxxxxxxx) and HD 8.9 "(8.x.x_user_xxxxxxxxx)!

The author of a topic is not responsible for YOUR actions !!! Everything that you do, do at YOUR fear and risk !!!
Before all manipulations, we do a backup!

Formulate the questions clearly, informatively and clearly - then the probability is high that the answer will be just as intelligible and useful.
Example: "Hello, I have installed<firmware version>. I'm trying to get<some result>. I did<actions>. As a result, I got<the result that is obtained>. WHERE? "


This topic discusses issues related to KindleFire firmware! Offtop and posts not related to the topic will be deleted without warning !!!

Drivers and utilities:
TWRP Otter

TWRP Otterx
• TWRP OtterX 2.7.0.1Attached filezip-otterx-twrp-2.7.1.0-recovery.zip(7.28 MB)

• TWRP OtterX 2.8.2.0Attached filezip-otterx-twrp-2.8.2.0-recovery.zip(7.38 MB)

OtterX ROM / TWRP / Bootloader topic on xda beta
OtterX Bootloader
Android SDK Tools
Kindle Fire Utility 0.9.9
Kindle_Fire_Utility features:
    • Automatic installation of temporary and permanent ROOT
    • Automatic download and install TWRP Recovery
    • Automatic download and installation of GoogleApps / Market / GoLauncherEX.
    • Definition and selection of operating modes of the device.
    • Auto-installer drivers (Kindle Fire Utility Driversinstall_drivers)
    • Automatic download and install stock firmware.
    • Mounting the system to Write / Read.
    v. 9.9 Ability to install COTR Recovery, Dual-Boot and rollback with Dual-Boot.
    v. 8-9 Fixed some points in the installation of root and drivers.
    v. 9.1 Fixed and improved driver installation.
    v. 9.2 Fixed and improved installation of TWRP Recovery.
    v. 9.3 A new version of BurritoRoot has been included to eliminate errors during rutting.
    v. 9.5 Getting root-rights on firmware including 6.3 and 6.3.1.
    v. 9.6 Fixed SuperUser installation.

Universal rootto get ROOT rights on firmware 6.3.2. fromGuns_tm
KFU_Repack by s-tnovikov
What is changed / added:
    1. Based on version 0.9.2
    2. The item with the download and installation of TWRP is replaced by "Installing Recovery and FireFireFire"
    3. Added items with different recovery installation options (you don’t need to upload anything else, everything you need is already included in the utility and located in the recovery folder)
    4. Added item to quickly return toNORMALmode(fastboot -i 0x1949 oem idme bootmode 4000; fastboot -i 0x1949 reboot)
    5. Fixed driver installation.


Firmware
Official firmware:

Modified firmware:

Mods of official firmware
[*] Mod based on of. 6.2.1 (+ root, + busybox) by user eldarerathis . Topic on XDA ( On the people. )
Short description and changelog:
    Official firmware from Amazon v.6.2.1 with Root and Busybox installed.

[*] Mod based on of. 6.2.2 (+ root, + busybox) by usereldarerathis. Topic onXDA
Short description and changelog:
    Official firmware from Amazon v.6.2.2 with built-in Root and Busybox.

[*] MoDaCo Custom ROM based on. 6.2.2 from the userPaulOBrien. Topic onMoDaCo
Short description and changelog:
    Modified firmware from Amazon v.6.2.2.
    - improved performance
    - reduced firmware size
    - Google Services Framework and Android Market installed initially
    - the device will be defined as Galaxy Tab for the ability to download officially not supported applications and games
    - Root and Busybox

[*] MoDaCo Custom ROM based on. 6.3 fromPaulOBrien. Topic onMoDaCo
Short description and changelog:
    Amazon Modified Firmware v.6.3
    - improved performance
    - reduced firmware size
    - Google Services Framework and Android Market installed initially
    - the device will be defined as Galaxy Tab for the ability to download officially not supported applications and games
    - Root and Busybox

[*] Modaco_GR9_V & M & S_edition v2.0SELECTION OF USERSfrom usersVedroid (sergeysadoha), M1sterGrace andsam_top7. Topic onkindle-fire.in.ua
Short description and changelog:
    Amazon Modified Firmware v.6.3
    - Based on MoDaCo Custom ROM 6.3
    - Carousel removed (in replacement - ADW Launcher EX), Audible, Pulse, IMTb
    - Custom download animation
    - Changed the standard wallpaper
    - Changed unlock slider
    - Gallery from CM7 (pictures open much faster + multitouch works correctly, i.e. when scaling, the image increases smoothly, and does not leave under your fingers as in stock)
    - added Jbak Keyboard
    - built-in CPU Master to switch the profile and frequency of the processor to improve performance and smoothness (on the Quadrant (perfomance) test = ~ 2200 - 2300 b)
    - modified build.prop (disguise under Galaxy Tab + accelerator scripts)
    - MultiPicture Live Wallpaper for changing wallpaper without repacking and clipping
    - A package of firmware and widgets, i.e. the firmware in fact in the state "ready to use"

Android 2.x.x based firmware
[*] CyanogenMod 7 firmware fromwhistlestopSELECTION OF USERS(current update 01/13/2012) Topic onXDA
Short description and changelog:
    CyanogenMod 7 firmware with Android 2.3.7 version. It is characterized by a more familiar user interface and increased speed. Of the minus, you can note less battery life and the presence of the telephone part.

[*] Skimp Killah Super Kang Project 1.3 based on CM7 fromSkimp killah(current update 02/02/2012) Topic onXDA
Short description and changelog:
    CyanogenMod 7 firmware with Android 2.3.7 version with a number of additional improvements and programs:
  • ICS Keyboard
  • ICS Theme
  • Embedded Google Apps (Market, Talk, ...)
  • Removed unnecessary applications (Phone, sms / mms, DSP manager, ...)
  • Galaxy Nexus Booth Animation
  • It uses a custom core from IntersectRaven (ATTENTION!Characterized by increased power consumption!)
    Changelog:
    Version 1.2
    - Used custom kernel from IntersectRaven.
    - Fixed USB mount.
    Version 1.3
    - Fixed statusbar errors.

[*] CM7 Barebones fromTakenover83. Topic onXDA(current update is 03/29/12)
Short description and changelog:
    CyanogenMod 7 firmware with Android 2.3.7 version with a number of changes:
  • - ICS Theme

  • - Custom download animation
  • - Stock keyboard Kindle Fire
  • - overclocked kernel intersectRaven kernel OC 1.2Ghz
  • - Samsung Galaxy Tab masking to access officially unsupported applications
  • - QuickPic instead of Gallery, also included Button Savior and Volume Control
  • - Removed the "telephone" part of the application

[*] MIUI2.1.20(current update 02/01/2012) Topic onXDA.
Russian version by sergmurtazin
Short description and changelog:
    Firmware from Chinese developers with Android version 2.3.7. It is characterized by a beautiful and convenient user interface, good speed. Of the minus can be noted the lack of Russian language.

[*] HellFire Kindle CM 7.2 v1.1 fromx0xhellx0x. Topic onXDA(current update 04/18/12)
Short description and changelog:
    CyanogenMod 7 firmware with Android 2.3.7 version with a number of changes:
  • - Wallpaper in the style of Hell
  • - Theme, ICS live wallpaper
  • - New icons
  • - Amazon Apps, Gapps, TiBackUp embedded

ICS firmware

Jelly Bean firmware

Kit Kat firmware
Official Cyanogenmod 11 for otterX
Short description and changelog:

ROM: SlimKat (unoffical) for the OtterX topic on xda
Short description and changelog:
Merge in 4.4.3
TRDS for some packages due to 4.4.3
Update Nova Launcher
Updated Addons
Fix some translations
Device specific
Kona: Update some audio configs, camera bugs and graphic glitches
Toro: Fix up some RIL problems
Rhine: Merge in CM changes

OtterX ROM / TWRP / Bootloader topic on xda beta
Instructions for returning from Otterx to Otterfromkbm113
Short description and changelog:
IMPROVEMENTS:
All new mainline u-boot sources from "2014.01" release
All new multi level expandable text-based menu system. Uses 2 styles of power button presses to navigate. Regular press = move down, Long press = select.
Long press power to turn on device. This eliminates those accidental power ons while traveling, etc.
Improved fastboot handling and shows shown on LCD
Native "reboot recovery" support (OtterX ROM build needed)
Native handling of serial # and mac addr passed into kernel (no more idme binary needed)
Support for "Charger" bootmode (OtterX ROM build needed)
New splashscreen (similar to HDX models), low-battery screen and fastboot mode screen
Added device binary support in boot.img (for loading newer kernels)
ALSO REQUIRES NEW RECOVERY AND OtterX ROM build
[v2.03] Splashscreen can be loaded as BMP file from "splash" partition (can be applied by: fastboot flash splash initlogo.bmp)
[v2.03] Built-in menu option for EMMC corrupted devices
[v2.03] press button
[v2.03]] menu new load a bootloader)
[v2.03] Fixed partition mode to detect what's actually on the device vs. some random setting
[v2.03] Fixed fastboot erase command
[v2.03] Fixed fastboot flash bootpart command
[v2.04] Handle charger mode correctly
[v2.05] Tweaked the USB plug-in detection for fastboot mode
v Adj ter future future future future future future future future future future future

[CM11] [OFFICIAL] InFriction ROM v11 [SPEED] [PERFORMANCE] topic on xda
Short description and changelog:
20131222 - Initial Release

20131225 - Fixed Youtube Bug
Cleaned up useless and memory hungry apps
New Boot Animation
Google Play included

20140107-Fixed Google Play Store error
New Tweaks for much better performance

20140208-Updated with latest CM changes
KSM for more free RAM
New boot animation
Added Jeeko's Performance Engine for smooth operation
Added my own speed tweaks.

OtterKat Rom (CM based KK) topic on xda
Short description and changelog:
.

[ROM] [4.4.2] [Official] [CMB Roms cmb4.4.2] [Kindle Fire] [01/25/2014] topic on xda
Short description and changelog:
.

[KK 4.4.2] CM11.0 / SGT7 for the Kindle Fire topic on xda
Short description and changelog:
[20140502]
* Latest device / kernel and CM changes

* Additional OtterX build

[20140417]
* Latest device / kernel and CM changes

[20140323]
* Kernel: trim fix [Hashcode]

[20140314]
* Latest device and CM changes (e.g. IMDB fix [Hashcode])

[20140221]
* Latest device and CM changes

[20140129]
* Latest device and CM changes

[20131230]
* frameworks / native: Fix boot animation rotation problem when ro.sf.hwrotation is set to 90 or 270 [Clyde Tan]

[20131215]
* Settings: Fix for quick settings tiles and loading [sbrady]

[20131212]
* Android 4.4.2
* Framework / Settings: Large recent thumbnails, recents panel color and dual pane preference [sbrady]
* Framework / Settings: Notification panel and quick settings tile color [sbrady]
* Kernel: zRAM (Enable in performance settings)

[20131208]
* Android 4.4.1

[20131206]
* Device: Enable translucent lockscreen
* Framework / Settings: Add setting to enable or disable navigation bar [sbrady]
* Framework / Settings: Add forceHighEndGfx property to override isHighEndGfx [sbrady]

OFFICIAL CM11.0 + 3.0.72 Kernel for Kindle Fire [NIGHTLIES] topic on xda
Brief Description and Changelog
[11/25] Released updated build for cm11.0
[08/12] Kernel updated to 3.0.72 (on par w / Google / common kernel)
[07/30] Updated to CM10.2 build
[05/26] Backlight driver update to help w / SODs
[05/24] Sensor updates (includes light sensor now usable in Android OS
[05/24] Remark for audio w / headset function - testing needed.
[05/14] New audio driver (WIP)
[03/27] Reboot Recovery mode is now fixed
[01/17] Updated SGX / PowerVR driver to latest binaries from omapzoom (still showing [email protected])
[01/15] CM10.1 updates + reverted some USB changes
[01/07] Battery life / sleep improvements
[01/06] Update to 3.0.50 kernel
[01/06] Update wifi firmware to R5.SP3.06
[12/16] Fixed Deep Sleep
[12/15] Added multi-profile fix

[ROM] [OFFICIAL] [4.4.2] HELLKAT | LINARO 4.8 | 3.0.101 Diablo Kernel | Kindle fire topic on xda
Brief Description and Changelog
.

[CM11] [UNOFFICIAL] InFriction ROM v4.4.2 [FOR-FREE-RAM] [OTTER] topic on xda
Brief Description and Changelog
20131222 - Initial Release

20131225 - Fixed Youtube Bug
Cleaned up useless and memory hungry apps
New Boot Animation
Google Play included

20140107-Fixed Google Play Store error
New Tweaks for much better performance

[ROM] [Carbon] [UNOFFICIAL] [KITKAT] [KINDLE FIRE] [WEEKLIES] [JAN 24, 2014] topic on xda
Brief Description and Changelog
.

Flash Player on Android 4.4 Kitkat
change_to_nexus7-4.4

Lollipop firmware
[ROM] [OFFICIAL] [5.0.2] AICP for OtterX [NIGHTLIES] topic onxda
Brief Description and Changelog

Slimpop for the OtterX LRX21VAlpha topic on xda
Brief Description and Changelog

[ROM / KERNEL] UNOFFICIAL CM12.0 for OtterXAlpha topic on xda
Brief Description and Changelog
• [11/30] Alpha build made public

Ubuntu
[ROM] Ubuntu Touch Preview [02/27: Alpha Update # 1] topic on xda
CHANGES:
[02/27] Fixed the UI DPI settings. Needs to re-flash following the instructions below.

List of current versions of firmware, kernels and utilities on XDA


Instructions:
What is what?
    It is useful to get acquainted withAndroid OS FAQ where you can find answers to common questions about the Android operating system and Glossary where the basic terms are explained.

    Firefirefire
      FireFireFire - modified bootloader (bootloader), giving the opportunity to choose the device boot mode: Normal (normal) or Recovery (recovery).

    TWRP Recovery
      TWRP Recovery is a modified unofficial recovery specially made for touch control.
      Allows:
    • Install unofficial firmware
    • Install add-ons and fixes
    • Connect to PC via USB in removable storage mode
    • Connect to PC via USB in ADB mode
    • Create a backup of both the entire firmware and its individual parts (system, settings, installed programs)
    • Recover data from previously created backup
    • Reset the data to the factory settings (Wipe - factory reset), clear the cache partition (wipe - cache), clear the dalwick cache (wipe - Dalvik-cache), clear the battery statistics (wipe - battery stats)
    • Format and create partitions on a memory card.
      Benefits:
    • convenient interface fitted to the touch control
    • ability to install * .zip from any folder
    • advanced settings and functions
      Screenshots:
      Attached Image


    Clockworlmod recovery (CWM)
      Clockworlmod Recovery is a modified unofficial recovery that is released for most Android devices. It has much more features than native recovery. On some devices it is installed instead of native recovery, on other devices it is installed in parallel.
      Allows:
    • Install unofficial firmware
    • Install add-ons and fixes
    • Connect to PC via USB in removable storage mode
    • Connect to PC via USB in ADB mode
    • Create a backup of both the entire firmware and its individual parts (system, settings, installed programs)
    • Recover data from previously created backup
    • Reset the data to the factory settings (Wipe - factory reset), clear the cache partition (wipe - cache), clear the dalwick cache (wipe - Dalvik-cache), clear the battery statistics (wipe - battery stats)
    • Format and create partitions on a memory card.
      Benefits:
    • familiar and simple interface
    • ability to select device boot mode
    • fast work
      Screenshots:
      Attached Image



[*] Video instruction for OtterX ROM / TWRP / Bootloader
[*] Instructions for obtaining root-rights for firmware 6.3.3
[*] Instructions for obtaining root-rights (for firmware up to version 6.2.1)(old method)
[*] Manual driver installation manual (not via install_driver)
[*] Instructions for obtaining root-rights for firmware version 6.2.1 and higher (Attention sometimes it is impossible to get root by this method !!! Use the latest version Kindle_Fire_Utility))
[*] Instructions for obtaining root-rights for Linux
[*] Video instruction "Route + TVRP"fromShiFT_UA
[*] Video instructions for changing the firmware when the TVRP is already installedfromEvgeshaHouse
[*] Dualboot bootloader installation instructionsAttention: on the map after installation only 3.6 GB will be available.
[*] Instructions for installing Amazon Silk on custom firmware
[*] Resetting the boot mode (the device is loaded only in the recovery, flashing does not help)[color = red]
Installing custom firmware (for example, CM7 + GoogleApps) via TWRP Recovery
    1. Download the zip-archive with the firmware you need.
    2. Downloading the latest versionGoogleapps(For ICS we take gapps from the topic header, for the rest of the firmware this item is skipped).
    3. We drop the downloaded archives into the root of the memory card (sdcard /).
    4. Reboot to TWRP Recovery.
    5. We do all the wipes: wipe / dalvik-cache, cache, factory reset, system.
    6. Go back to the main menu (upper right arrow back) and enter the Install section.
    7. Select update.zip in the right panel, click install and wait for the operation to finish.
    8. Select GoogleApps ..... signed.zip in the right panel, click install and wait for the operation to finish. (for the rest of the firmware, except for ICS, we skip this point)
    9. Return to the main menu and click Reboot / System
    We use everything.

Installing FIREFIREFIRE + TWRP or CWM Recovery
    ATTENTION!!! The device must be Rutovan !! !
    1. Download the KindleFireUtility utility, unzip it to any convenient place for you.
    2. We connect the "light" to the computer (on the stock firmware, installation of third-party applications should be allowed and the connection as a flash drive is turned off !!!)
    3. Go to the folder with KFU and runinstall_drivers.bat(as administrator). Install / reinstall drivers.
    4. In the same folder, runrun.bat.
    5. Check whether the device has been determined (i.e. it should be the same as on the screen):
    Attached Image

    6. Select the 5 point (enter 5 and click inter) - "Installing Recovery and FireFireFire".
    7. In the next menu, select, depending on what kind of recovery you intend to install, point 4 or 5. I advise installing CWM, as it is more reliable. IMHO.
    We are waiting for the end of all operations (the device reboots first in fastboot, and then in normal mode).
    Do not try to remove the cable during the installation process !!!
    To enter the recovery: when a yellow triangle appears, press and hold, until the color changes to red, the power button.

Extreme Recovery Method
    Making a repair cable

    warlock_bc @ 12/22/2011, 00:19*
    Brik about fireworks, he encountered yesterday, today, I resolved the problem. Generally requires a so-called factory cable - conventional cable with micro yusb, with a link between 1m Ping (+ 5V) and 4m (default is not connected), naturally prdetsya razderbanit whole to solder a jumper, but the usefulness of this simple devaysa invaluable. In any case connecting Kindle through it we come in fastboot, and from there it is already possible to put the same TWRP c pomoischyu Kindle Fire Utility (see. Cap) that I did today and what inexpressibly glad. Here fotoinstruktsiya for the manufacture of the cable:

    Cut as pictured on both sides
    Attached Image

    The result is
    Attached Image

    Attached Image

    Attached Image


[/ list]

miscellanea
What to do if the device does not load inNormal modeand drivers are not installed in the modeFastboot
    Answer 1st
      S-tnovikov @ 12/27/2011, 08:24 *
      1. Calm down and do not panic. You haven't done anything, you are just in FastBoot mode.
      2. Turn off the device by long pressing the power key.
      3. Restart the computer, just in)
      4. Open the device manager so that while the next item is executed, you have managed to update the driver.
      5. Devays atoffable to connect to the computer and he himself turn on, though all in the same FastBoote.
      6. Start KFU and in the first paragraph select the normal mode (that the program will not be determined by the device and writes “FastBoot status: offline” is not paid attention).
      Attention!!!Perhaps the first time you do not succeed, then repeat paragraphs 4,5,6 again. Also, when defining a device as an "unknown" or "compound" device, delete it and update the device list - this can also help.


    Answer 2nd
      Diverrus @ 12/27/2011, 10:35 *
      I should add that people do not panic too much:
      statuses:
      launch logo: KindleFire on a slightly dimmed screen by backlight - fast boot device mode
      starting logo: yellow triangle 3fire - fast boot mode.

      Add to recipes-tnovikov , as I did with my flash in fast boot mode:
      Notice how we select the normal boot mode (4000) in KFU v 7.0
      We see such message:
      ***********************************************
      * Activating Normal (4000) *
      ***********************************************
      <waiting for device>
      do not panic, go todevice Manager and most likely we find some kind of USB device there, opening which you can see that it is still Kindle (I saw such an inscription somewhere, now I’ll not say for sure - I am writing from memory)
      doingupdate driver and forcibly handles indicate the path for example: C: Kindle Fire Utilitydrivers38
      Winda picks up a light, and KFU gives him a command to the normal reboot (4000)
      At some point I had an incomprehensible bug and the firewood from KFU v7 was not hooked up, I picked up firewood from TWRP (although it seems they are identical)
      Here is a supplement! Good luck to all! AT)


    3rd answer
      Monten @ 01/03/2012, 15:56 *
      Calbas @ 01/03/2012, 13:23 *
      Irpich 10th day. 6.2.1, then TWRP, through it according to the instructions "modified Amazon firmware 6.2.1 + root + busybox", when rebooting, only TWRP mode, downloaded the drain from Amazon, uploaded, installed - fastboot (or similar to it visually). I tried all the described methods of respected members of the forum, and from the cap, and from the discussion - while the situation - opa, sorry. I attach the screenshots, maybe someone like that too ...

      as far as I can see you have at least the wrong drivers installed (must be an Android ADB Interface device).
      remove the third line for the 1949 vendor from the android_winusb.inf file, i.e. leave it like this:
      ; Kindle Fire
      % SingleAdbInterface% = USB_Install, USBVID_1949 & PID_0006
      % CompositeAdbInterface% = USB_Install, USBVID_1949 & PID_0006 & MI_01

      After that, save the file and reinstall the driver


    How to simplify sound adjustment on the CM7?
      Naromdvd @ 12/21/2011, 07:36 *
      so far only: (c) http://kindle-fire.in.ua/news/110-obnovlen...l"Taking up That the Kindle Fire does not have special volume buttons, sound control can be a daunting task. You will have to go to the desktop, go to “Menu”, select “Settings”>"Sound", and only then "Volume" to be able to adjust the volume. Or you can install third-party applications that allow you to adjust the volume directly from the desktop or any other "window". One of them is called Volume control , released by the developer RubberBigPepper, inspires confidence, and allows you to adjust the volume by moving your finger up and down in the right side of the screen. "


    Access to officially unsupported AndroidMarket applications (issued for Samsung GalaxyTab)
      1. RootExplorer om go to the system folder and find the file build.prop there.
      2. Long hold on it and select "Open in Text Editor".
      3. Replace the values ​​in the corresponding lines with these:
      ro.product.model = GT-P1000
      ro.product.brand = Samsung
      ro.product.device = GT-P1000
      ro.product.manufacturer = samsung
      ro.build.description = GT-P1000-user 2.3.3 GINGERBREAD DXJPI release-keys
      ro.build.fingerprint = samsung / GT-P1000 / GT-P1000: 2.3.3 / GINGERBREAD / DXJPI: user / release-keys

      4. After editing, press Menu - select "Save Changes" and agree with the changes.
      5. Restart the device and use a large number of applications from the market.

  • A very good program for emulating hardware buttons.Button savior
  • How to make a photo frame from Kindle firefromMirrorbuoy


Post has been editedstarkonov - 11.01.18, 09:51
Reason for editing: Updated link to KFU



Rep: (22)
Hardly ... I did not get into this situation ...
I'll tell you that's what (Kindle discharged) ... yet I have not seen the information about the killed reinsertion Kindle. The decision will come.
Goodnight



Rep: (7)
GrashAlex,
while the Kindle screen is always brightly lit when the cable is connected?
And drivers in the system should be defined as adb android interfaces
And he CFI also do not need to see the device

Try to boot Windows F8 and boot to last known good configuration. The idea is that on the Seven, the first time the driver must get up without problems



Rep: (0)
Marancano @ 08.01.2012, 13:11*
And drivers in the system should be defined as adb android interfaces
And he CFI also do not need to see the device

Now I have the driver is now so determined
CFI and not see the device
and what to do? O_o
Cable changed (



Rep: (0)
generally funny
if the device is defined as Android ADB Interface - i.e. installed driver of KFU, then himself KFU and generally does not see the device
and if both Android Composite ADB Interface - ie automatically installed Windows, then KFU sees the device, but ADB ROOTED: NO, and nothing is set, and temporary and permanent Root does not attempt ..
Well, more accurately put it, and he says, such as that he put, but overloads the device and the status of writing again, what is not.



Rep: (0)
Marancano
Yes, the screen lights up brightly with "kindle fire" inscription.
driver in the system is defined as the adb android interfaces.
KFU but does not see it and did not put. Rather something somewhere puts, but the result is the same - obsessed CM7
I and through the command line using the adb tried to reach devaysa - writes "Connect the device"
Maybe I'm doing something wrong?
Throw off anyone a link to this thread in XDA. I have an English tight, but still, suddenly there that will advise ...
Spark was going to his wife's birthday present .... What to do now? ... And why do I have this Reset Recovery in CM7 pressed? ...

Post has been editedGrashAlex - 08.01.12, 14:54



Rep: (0)
By the way, this cable can be factory in St. Petersburg somewhere to buy?
and the soldering iron is not present at home :(



Rep: (17)
GrashAlex @ 08.01.2012, 14:51*
Spark was going to his wife's birthday present .... What to do now? ... And why do I have this Reset Recovery in CM7 pressed? ...


there is a cap for the spark Developer SM7:
Reboot into TWRP (when the FireFireFire screen comes up hit the power button to launch TWRP.
-If you reboot by holding the power button until the power screen comes up make sure when you select reboot that youDO NOT say boot into recovery as this will put you into a loop where the device always boots into TWRP (Even if you do not press the power button during the boot) READ THIS PART AS ALMOST EVERYONE IS MISSING THIS PIECE: If you find yourself in this loop then connect with "adb shell" and issue "idme bootmode 4000"
-For me I hold the power button until it goes orange. Just pressing it quickly does not do the trick at least for me.


P.S. links to topics rom given in the header.

Post has been editedMonten - 08.01.12, 15:16



Rep: (94)
Prompt please) after installing SM7 noticed that when I open a picture in the gallery it is taken first black cubes flickering in the process of adjusting a screen, then everything is OK, and leaf through - everything is OK, the following open - normally. Close gallery will open again have another picture - the same story ... At the same time when I open through filemanager then everything is fine. Alter to 6.2.1 through TVRP - the exact same problem. Who knows what trouble?



Rep: (17)
Sedrak @ 07.01.2012, 23:33*
Quote (repka20 @ 07.01.2012, 23:56)
twrp image need to download here and drop a folder kindle fire utility / recovery

there was already this file .. now they are 2


The problem is that the image is automatically bad for rekaveri swinging (created image of the size of 8KB, instead of the 10MB). Therefore, the image of self swing rekaverifrom here, then rename it to twrp.img and copy it to the folder ... kindle fire utility \ recovery \ (if the recovery folders along with the tools, files, drivers folders are not in the KFU directory, then create it and just drop it into the folder you just downloaded and renamed image of recovery).
In your case, it turns all the same "the broken" image rekaveri twrp.img size 8 kB, as when copying the complete image there, not renamed it twrp.img

Post has been editedMonten - 08.01.12, 15:24



Rep: (0)
Monten @ 08.01.2012, 16:21*
The problem is that the image is automatically bad for rekaveri swinging (created image of the size of 8KB, instead of the 10MB). Therefore, the image of self swing rekaveri here, then rename it to twrp.img and copy the replacement to the folder ... kindle fire utility \ recovery \ (if the recovery folder along with folders, tools, files, drivers in the directory CFI is not present, create it and just to throw just downloaded and renamed rekaveri image).
In your case, it turns all the same "the broken" image rekaveri twrp.img size 8 kB, as when copying the complete image there, not renamed it twrp.img

Yes, thank you, I already did, but it did not help ..
The main problem - it ..

Sedrak @ 08.01.2012, 14:28*
generally funny
if the device is defined as Android ADB Interface - i.e. installed driver of KFU, then himself KFU and generally does not see the device
and if both Android Composite ADB Interface - ie automatically installed Windows, then KFU sees the device, but ADB ROOTED: NO, and nothing is set, and temporary and permanent Root does not attempt ..
Well, more accurately put it, and he says, such as that he put, but overloads the device and the status of writing again, what is not.


Post has been editedSedrak - 08.01.12, 15:29



Rep: (0)
Monten,
there is a cap for the spark Developer SM7:

Unfortunately, adb flame does not see



Rep: (17)
in my case it is quite often not seen the device, but all the action on transition between modes were properly ... (driver initially set manually by pointing them in the folder with the CFI)

Sedrak @ 07.01.2012, 19:36*
In this case, when you try to manually install the driver issues that do not need to install the driver, because the new well.


if you are already on, select "uninstall" on the Kindle in the Device Manager, you should see another window (win7), where it is necessary to put a tick on the item "Delete the driver software for this device" (this is basically how to remove the old drivers before slip new hand)

Post has been editedMonten - 08.01.12, 15:53



Rep: (2)
Please tell me, you can connect a 3G modem from MTS ???



Rep: (66)
Roland90,
How sorry



Rep: (7)
People, I was a little zamodil MIUI, can it in a hat?
on changes
- Added Russian language
- Integrated CPU control
- Added font from android 4.0
- What is the feature of the Sony bravia, assure that the picture is getting better
- The same Sony Xloud only for sound
- In addition, a new theme
- Still what then appeared Supermarket
Swinginghere
What works what does not work, is not the answer. While not a test. But it works like a stable

Post has been editedmulinby - 08.01.12, 19:23



Rep: (66)
mulinby,
better than tsinagen?



Rep: (7)
ivleyantosha,
I generally uneven breathing to MIUI, I standing on it at SGS. According yuzabetelnosti considered one of the best operating systems, I like it more than IOS. Customize the look of it all a fairy tale, there are online on any topic bunch. However, there are some minuses to spark. In particular, have not done the normal emulation hardware buttons below the desktop icons 4x5 grid, you can imagine when the distance between the icons twice themselves icons: D. But luncher on MIUI put this blasphemy. In general the issues still missing, but MIUI is known that once it came to any device that is no more than a month, you can expect a full shaft. Plus, developers consistently every Friday vykladyvat new version.



Rep: (66)
mulinby,
Come on) until I put



Rep: (81)
since 1 out MIUI version of the video it does not work today. and where the fixes?

and 4th android generally dull all ...



Rep: (7)
power007, but as a way for a long time she left? I just saw it today


Full version    

Help     rules

Time is now: 04/04/20, 18:50