Develop Bugs

[ROM] EZbase v3.0 [25/04/2011] - odin / heimdall - Easy Full Graphical How-To

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EZbase, is a fully deodexed and zipaligned pre rooted odin / heimdall image for people wanting to move from stock ROM's to custom ROM's. It used by a lot of people for a recovery image if it all goes wrong, simply flash this and you on a stock Samsung image with root and 2e recovery.
Still testing the new recovery & kernel so attached is a copy of EZbase with stock CWM Recovery, until the new recovery has been 100% tested!
Screenshots:
Main Recovery - Recovery Backup - Recovery Install - EZOdin​
Features:
Gingerbread & Froyo
Simple Recovery Menu
Added:
RomManager 3.0.xxx
TitaniumBackup 3.7.2
Notes:
Please read the EZbase How-To v2.00 - http://nfye.eu/EZbase/i9000/EZbase-2.00.pdf
Donators:
Euphoria
Thanks To:
RazvanG - 3-Button Combo Fix
Tr0jAn - Testing & Documentation Review
​

Downloads:
EZbase How-To
ROM
Gingerbread EZbase v4.0
Froyo EZbase v2.0
Other
EZOdin
Android Debug Bridge (a.k.a. adb)​

Reserved
Reserved 10 Chars

This is a Step by Step guide how to flash EZbase to your Samsung Galaxy S.​
There are lots of different ways to flash ROMs to your Samsung Galaxy S, Personally I use heimdall but thats because I use *nix. I find this one to be easiest and fastest for windows users.
If you complete this guide there the worlds your oyster, simply copy different mods/ROMs to the SD Card and flash directly from there going back to your base at any time should you need to revert back.
If you have any issues what so ever, the best place to begin is a clean EZbase flash.
NOTE: No root or anything is required, you can simply do this on a stock Samsung ROM.
Contents
What you need
Flash EZbase
Install Custom ROM
Other Information
ADB - Android Debug Bridge
Enable Debugging Mode
Mass Storage
Download Mode
Recovery Mode
3-Button Combo Fix
Warning!
There have been many reports about a problematic batch of Samsung Galaxy S phones that are not able to boot into recovery or download mode. If you are going to flash a ROM please make sure you can enter these modes before doing ANYTHING. See the 3-button combo fix if you cannot access Recovery Mode.
What you need:
EZOdin - http://nfye.eu/EZbase/i9000/EZOdin.exe
EZbase
Custom ROM (only if you wish to use a third party ROM)
- E.G. insanity - http://forum.xda-developers.com/showthread.php?t=843019
Nice to Have
Android Debug Bridge (a.k.a. adb) - http://nfye.eu/EZbase/i9000/adb.zip
Download all the EZOdin, EZbase CSC, PDA, PHONE and PIT if you do not have Samsung Kies installed, The Samsung USB Drivers will be required to. For simplicity sake place all the files into a single directory e.g. c:\toolkit\ however they can be placed where you like, hopefully in the future I might get all the requirements into an installer.
If you do not have Samsung Kies installed please install the Samsung USB Drivers and make sure your device is recognised by the OS. Once all the pre requisites have been fulfilled, then please continue to Step One or Step Two. If Samsung Kies is used please make sure you kill all Samsung Kies related services that are running (kies, tray agent, etc.)
Check that your phone has sufficient power, unplug your phone if it is plugged into USB or wall charger. Type *#0228# in to the dialler and check Voltage is at least 3800(mV).
Flash EZbase
Repartition is not mandatory, but it does not hurt to repartition the phone.
Start Phone in Download Mode (No Cable Attached)
Open EZOdin.
- Check Re-Partition
- Select EZbase.pit as PIT
- Select EZbase-PDA-XWJS3.tar.md5 as PDA
- Select EZbase-PHONE-XXJVE.tar.md5 as PHONE
- Select EZbase-CSC-XXJV1.tar.md5 as CSC
Connect Phone with USB Cable - Once ID:COM is yellow you are safe to continue.
Select Start
Complete, now wait for your phone to fully start-up before you continue with anything.
Install Custom ROM
Copy the ROM onto the Internal SD Card. This can be done via adb or placing your phone in USB debug mode and mounting the USB as storage.
Reboot the phone in recovery mode
Select "Install ZIP File"
Select "choose zip from sdcard"
Select "insanity-0.x.x.zip"
Select "Yes - Install"
Wait a while it installs the new ROM.
Select "Reboot Phone"
NOTE: As this is a de-odex`d ROM, First boot will take some time.
Other Information
ADB - Android Debug Bridge
To use the Android Debug Bridge you need to enable Debugging Mode first. Once enabled you will be able to use ADB and do a number of things.
Enable Debugging Mode
Press "Menu"
Select "Settings"
Select "Applications"
Select "Development"
Check "USB debugging"
Select "Yes"
Connect the phone to the USB cable and plug the other end directly into the PC.
NOTE: The computer should start installing the necessary ADB drivers. A total of three devices will be installed (Samsung Android Composite ADB Interface, Samsung Android USB Modem, Samsung USB Composite Device.
You should also now see two icons in the notification area.
Mass Storage
It is possible to mount the internal SD and microSD card as storage on your local pc, this is useful if you do not wish to use adb to copy files around.
If you wish to use your device as Mass Storage:
Pull down the notification area
Select "USB connected"
Select "Connect USB storage"
You should now be able to see your device in explorer
You should always safely eject the storage
Select "Turn Off"
Download Mode
To enter download mode, you hold the Volume Down + Home + Power. See image bellow:
Recovery Mode
To enter download mode, you hold the Volume Up + Home + Power See image bellow:
3-Button Combo Fix
You will need the following:
adb
root
xvi32 - http://nfye.eu/EZbase/i9000/xvi32.exe
P-SBL.tar.md5 - http://nfye.eu/EZbase/i9000/P-SBL.tar.md5
How To Check is Phone is Compatible:
adb shell
$ su (a superuser request will be displayed on the phone screen, accept it).
# dd if=/dev/block/bml1 of=/sdcard/bml1.dump
# exit
C:\adb pull /sdcard/bml1.dump
Open the bml1.dump file with XVI32.
- Search (in ASCII Mode) for OFNI.
If the block reads "[email protected]" just follow the tutorial below, as it is safe to fix.
NOTE: If it reads "x0" then STOP as this FiX will BRICK your phone if applied.
Open EZOdin
- Select the "P-SBL.tar.md5" as PDA file.
- Check "Bootloader Update"
Connect Phone with USB Cable and place phone in download mode (ADB method)
Once "ID:COM" is yellow you are safe to continue.
Select "Start"
NOTE: It should take three seconds to complete. After the update phone will reboot automatically. Do this at your own risk!

Reserved
Reserved Number 2

I was looking for this. Thanks. Will try insanity after this.
Darky's 9.3|Voodoo 5.4.1|ZSJPE|Lagfix OFF

Thanks again nitr8, I will use this on your next update of Insanity rom...
Nice

Great stuff - used EZBase earlier before flashing Insanity 0.6.6.
Like rixsta will use this method before future Rom flashes
Sent from my GT-I9000 using XDA Premium App

Thank you nitr8 =]

As always if you need any help man give me a call

Is this EZOdin safe/tested?
How is it different than the original (besides the UI, ofc)?

RayearthX said:
Is this EZOdin safe/tested?
How is it different than the original (besides the UI, ofc)?
Click to expand...
Click to collapse
Do you think I would release this untested? Yes its been tested, its STOCK Odin, with a revamped UI.

nitr8 said:
Do you think I would release this untested? Yes its been tested, its STOCK Odin, with a revamped UI.
Click to expand...
Click to collapse
YES! You could release it just for testing purposes
Just wanted to be sure.

RayearthX said:
YES! You could release it just for testing purposes
Just wanted to be sure.
Click to expand...
Click to collapse
it is check out post2

Nice you're pulling this up now!
I wondered, why you didn't release this.
Cheers,
Joël
Sent from my GT-I9000 using XDA Premium App

Darkyy said:
Nice you're pulling this up now!
I wondered, why you didn't release this.
Cheers,
Joël
Click to expand...
Click to collapse
It was ready a while back, we was about to do it and then a new firware came out and it got put on the back burner
My phone was on 6.6 but as it needed testing I redid it as per the written instructions just so we knew it worked 100%
IF people follow the guide then they SHOULD get a 100% working insanity rom with no hassle.. (we live in hope )
TrOjAn

Thanks for this, it's a nice initiative. I've been doing the same, just with different files from samfirmwares + I've needed to install a kernel to get easy access to root + cwm so this lets me skip that part
One thing though, you might want to either put this in your guide, or alternatively modify the app, but that Odin you have is version 1.7.. which has given me trouble (Windows 7, 32bit) in the past. Odin 1.82 works fine so just as a tip for people who might have problems getting odin to work
Aside from that this is a great idea!

akselic said:
One thing though, you might want to either put this in your guide, or alternatively modify the app, but that Odin you have is version 1.7.. which has given me trouble (Windows 7, 32bit) in the past. Odin 1.82 works fine so just as a tip for people who might have problems getting odin to work
Aside from that this is a great idea!
Click to expand...
Click to collapse
Hmm.. strange, Im on 1.7 Windows 7 32bit and I have not seen any issues.
What sort of issues have you had??
TrOjAn

TrOjAnUK said:
Hmm.. strange, Im on 1.7 Windows 7 32bit and I have not seen any issues.
What sort of issues have you had??
TrOjAn
Click to expand...
Click to collapse
odin either not connecting or just standing there doing nothing, never found out why but after using 1.82 its worked fine so I never felt like going back
and your files work with the standard odin anyway so it's not a big deal

akselic said:
odin either not connecting or just standing there doing nothing, never found out why but after using 1.82 its worked fine so I never felt like going back
and your files work with the standard odin anyway so it's not a big deal
Click to expand...
Click to collapse
Yes I have has similar like that happen as it goes, re installing the drivers normally fixed it
Anyway, glad you like it.. hopefully more will find the benifits of EZBase
TrOjAn

Kindle Fire + Mac Guide

If you're like me, you have a Kindle Fire, but you would prefer to use it with a Mac than with a Windows computer. I'm writing up a guide on how to do numerous things such as rooting the Fire, but with a Mac.
Rooting
If you want to modify your device, the first thing to do is to root it. You can then install many apps that require root privileges, as well as install TWRP and FireFireFire Bootloader.
I use the utility Breakdroid, and it is easier to use than KindleFireUtility, the Windows counterpart, because it does not require you to install any drivers, it just works. Here is the website. Go to downloads to download the Breakdroid tool for Kindle Fire.
http://northmendo.com/breakdroid/ Feel free to donate to the guy who made this.
1. Download Breakdroid and mount the DMG file.
2. Make a folder on your desktop or applications folder called 'Breakdroid' and copy over all the files.
3. Open the Breakdroid application. It will open a terminal window. Use option 5 'Kindle Fire Tools' and hit return.
4. An icon will bounce on your dock. It may bounce for up to a minute. It will then ask you if you want to open this application downloaded from the web. Click ok.
5. It will then show a dialog warning you that this voids your warranty. If you are attempting this, you should know this already.
6. Now it opens another terminal window.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7. Type '1' and press enter. Follow prompts. Make sure you follow any instructions exactly. Follow all the steps until step 8. You can use step 9 to donate to the guy who made this. It is optional.
8. Finally you can use step 10 to quit the Kindle Fire tools.
9. FireFireFire has been installed as bootloader and you have rooted your device.
Recovery
You can use TWRP which has been installed by the previous guide to install ROMS, backup the current system and recover from any problems.
1. To access the TWRP recovery, shut down your kindle by holding down the power button until it shows a shut down dialog. Tap shut down.
2. Now turn the Fire on again. It will show a blue 'Kindle Fire' logo. This is the new FireFireFire bootloader which has been installed.
3. Keep your eye on the power button light. It should be green. Wait for it to flicker slightly. Or you can wait 2 seconds. Then press the power button again. It will show boot options.
4. Use the power button to cycle between the boot modes. Choose recovery to boot into recovery, then leave your Fire to boot.
5. Team Win logo will show, then the curtain will rise, showing a grid of buttons.
6. You have booted into recovery! Reboot without choosing recovery mode to get back to the normal system.
Install a ROM
1. Hook up your Fire with your Mac with a Micro-B USB cable. You can get them cheap on eBay, but mine broke after a few weeks, so feel free to find a more reliable vendor.
2. Download a ROM for your Fire. I'd recommend the GedeROM if you want an Ice Cream Sandwich ROM, or MoDaCo if you want a modified stock ROM with Google Play Store preinstalled.
3. Copy over the .zip file, placing on the Fire which has mounted on your desktop. Also copy over the gapps .zip if provided if you want the Google Apps package.
4. Eject the Fire and disconnect it from the Mac.
5. Use the previous guide to boot into Recovery.
6. Tap the Backup button and backup your system. This is very important, especially when installing your first ROM.
7. BACKUP YOUR CURRENT SYSTEM! For good measure.
8. Now tap the home button at the top right of the screen. Now tap Wipe, then tap Factory Reset. Then wipe Cache, then wipe Davlik Cache. Finally System Wipe. (Thanks to Thepooch for the best way to do this bit!)
9. This will wipe the device, so make sure you've Backed up your Fire! (See steps 6 and 7).
10. Now go back to the home screen using the home button and tap the install button.
11. Choose the ROM .zip file which you placed on the sdcard. I hope you named it something easy to remember and identify.
12. Tap install.
13. If it fails, restore from the backup you made (see how important backing up before wiping is?) and make sure your ROM you downloaded was downloaded properly. Also make sure it's the original zip file, not expanded or recompressed. Then repeat. If all else fails, try a different ROM or just stay with stock.
14. If it was successful, then go back to the home screen, and if you downloaded a gapps zip file, flash this as well, in the same manner as the ROM zip.
15. Reboot into system using the reboot button on the home screen.
16. Successful? If you don't like your ROM, you can always revert to stock using your backup, or install a new ROM following these steps.
_________________________________________________________________________
If you found this guide helpful, please click the Thanks button. It means a lot.

great guide nice job really

Ok, I'll add that.
Yea, I'm just annoyed how little support there is for Macs so I wanted to show that it can be done

where can i get the link to the rom
I tried googling for the rom, and i downloaded the rom from MoDaCo, but when it finished downloaded, it's not written as .zip file.
I tried to place the entire folder in the sd card, but when go thru the TWRP recovery, of course, i couldnt find any .zip file.
Anybody can help?

This is a common problem. Open Safari, then press Command + (comma). This opens your preferences. Untick the option of automatically opening 'safe' files which is automatically unzipping your zip files. Now you can redownload the ROM and find the zip in your Downloads folder

some links to make this happen
Great info, will test much of it shortly. A few links that I found helpful and are ref'd above:
for the Google Apps package, Rootzwiki was helpful
http://wiki.rootzwiki.com/Google_Apps#Jelly_Bean_.28Android_4.1.x.29
and points to Jelly Bean universal apps:
http://goo.im/gapps/gapps-jb-20120726-signed.zip
Kudos to twa_priv for a start to that trail.
Also twa_priv has useful info here (not mac specific, check the changelog for udpates)
http://forum.xda-developers.com/showthread.php?t=1778010&highlight=jelly+bean+gapps+fire
that also links to hashcode's kernel_omap (now over my skill set, but might be useful)
https://github.com/KFire-Android/kernel_omap/tree/p-android-omap-3.0
A couple of ROMs for Jelly Bean (I've not tested yet, but they're on my list):
Jandy Cane
http://forum.xda-developers.com/showthread.php?t=1766829&highlight=mac+kindle+fire
and since I can't find the post with the .sig file where I found AlienDroidV2.0 (which I'm told has hashcode's kernel in it), here's a bonus page that seems to have lots of good info:
http://forum.xda-developers.com/showthread.php?t=1859851&highlight=mac+kindle+fire
northmendo's breakdroid always worth mentioning, cuz you might need to start there:
http://northmendo.com/breakdroid/ (I found kindlewater mysterious but worked for me)
and the video to Root Kindle Fire Mac (6.3 & 6.3.1)
http://www.youtube.com/watch?v=5K_sw1quZlw
That ought to get you started. All links good as of today, 9/9 2012.

Most of that info is already on the original post :/

links were missing
jji7skyline said:
Most of that info is already on the original post :/
Click to expand...
Click to collapse
Info yes, but links to all things downloadable were missing (except breakdroid), which is why I spent time documenting it.

nice job I`m sure that your research will help others

[EDIT 2] I've noticed that I am having an issue with charging since I installed the rom. It will only recognize the charger when the Kindle is turned on, and it charges VERY slow. Anyone have any insight to this? [EDIT 2]
[EDIT] Nevermind! The play store was included! This TOTALLY reinvented the Fire for me. [EDIT]
Thanks so much for this! Working on it now.
One question.. The site that I downloaded gede from didn't come with the GApps zip. I went searching, but it looks like there are many different versions. Could you please inform me of where to get the right one?
Thank you again. Very, very much!

handamputation said:
[EDIT 2] I've noticed that I am having an issue with charging since I installed the rom. It will only recognize the charger when the Kindle is turned on, and it charges VERY slow. Anyone have any insight to this? [EDIT 2]
[EDIT] Nevermind! The play store was included! This TOTALLY reinvented the Fire for me. [EDIT]
Thanks so much for this! Working on it now.
One question.. The site that I downloaded gede from didn't come with the GApps zip. I went searching, but it looks like there are many different versions. Could you please inform me of where to get the right one?
Thank you again. Very, very much!
Click to expand...
Click to collapse
The latest version of jandycane ROM seems to fix a lot of charging glitches.

this is an incredible tool, thanks for sharing!!

device not found
hey guys... got my kindle today and I'm trying to root with the help of your guide. But after starting step one the the tool starts working but soon it wont find any device and stops. any ideas? Do I have to turn the kindle on or off?
btw: I've got the newer version of the kindle fire with 1gb RAM
[EDIT]
I just disabled and renalbed ADB and now it seems to find my device but now I'm getting this error "fail opening shift: No such file or directory" and after this its stuck "< waiting for device >".
Pleas anybody help me

janowhatever said:
hey guys... got my kindle today and I'm trying to root with the help of your guide. But after starting step one the the tool starts working but soon it wont find any device and stops. any ideas? Do I have to turn the kindle on or off?
btw: I've got the newer version of the kindle fire with 1gb RAM
[EDIT]
I just disabled and renalbed ADB and now it seems to find my device but now I'm getting this error "fail opening shift: No such file or directory" and after this its stuck "< waiting for device >".
Pleas anybody help me
Click to expand...
Click to collapse
This will NOT work on the new kindle, as although it looks similar, it is very different inside. You stand an extremely high chance of a permanent hard-brick for your kindle fire. DO NOT PROCEED.

Hello guys!
I've been trying to root my kindle fire... I follow all the steps 1 to 7. Step 8 from me return "Invalid option".
I have installed Root Explorer but when I try to move "vending" apk from /sdcard/Documents to /system/app I get the message: "Your phone doesn't appear to be rooted...."
I need to follow some additional steps?
My device version is 6.3.1
Regards!

Issue
Why is it that at step 1 i am stuck on "waiting for device" ?

eliasn said:
Hello guys!
I've been trying to root my kindle fire... I follow all the steps 1 to 7. Step 8 from me return "Invalid option".
I have installed Root Explorer but when I try to move "vending" apk from /sdcard/Documents to /system/app I get the message: "Your phone doesn't appear to be rooted...."
I need to follow some additional steps?
My device version is 6.3.1
Regards!
Click to expand...
Click to collapse
Maybe you should go through the steps again? It shouldn't say "Invalid option" at all. Make sure you power off and power on the kindle fire in all the necessary steps.
@behhtaran: Is your kindle fire connected directly to your Mac?

Help!
Hey everyone,
I need your help. I rooted my Kindle Fire HD (7.2.3) with http://forum.xda-developers.com/showthread.php?t=2074565. I now have 'SuperSU' and 'Root Check Basic' Applications on my Kindle Fire HD.
What I want is to have the 'Google Play Store' and the latest 'Jelly Bean' version. How can I do this? The other website shows me only the way with a PC but not with a Mac.
Thanks for all your responses!

Afaik you can't root the HD (correct me if I'm wrong but) you risk bricking your device.
Sent from my Amazon Kindle Fire using xda app-developers app

unfoldyourwings said:
Hey everyone,
I need your help. I rooted my Kindle Fire HD (7.2.3) with http://forum.xda-developers.com/showthread.php?t=2074565. I now have 'SuperSU' and 'Root Check Basic' Applications on my Kindle Fire HD.
What I want is to have the 'Google Play Store' and the latest 'Jelly Bean' version. How can I do this? The other website shows me only the way with a PC but not with a Mac.
Thanks for all your responses!
Click to expand...
Click to collapse
Use the search, Luke...
http://forum.xda-developers.com/showthread.php?t=2074565

[Galaxy Note2 TOOLKIT V6 SPRINT] Drivers, Backup, Root, Recovery, Flash to Stock

[TOOLKIT] UNIFIED ANDROID TOOLKIT - SAMSUNG GALAXY NOTE 2 - Drivers, Root, Recovery + MORE
GSM (GT-N7100) and LTE (GT-N7105) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1923956
AUSTRALIAN GSM (GT-N7100T) and LTE (GT-N7105T) SUPPORTED. USE GSM THREAD
SPRINT (SPH-L900) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957155
TMOBILE (SGH-T889) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957720
MOBILICITY, VIDEOTRON, WIND [SGH-T889V] SUPPORTED. NO THREAD YET. USE TMOBILE THREAD
AT&T (SGH-L317) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052779
BELL, ROGERS, SASKTEL, TELUS [SGH-I317M] SUPPORTED. NO THREAD YET. USE AT&T THREAD
VERIZON ([SCH-I605]) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052788
US CELLULAR (SCH-R950) SUPPORTED. NO THREAD YET. USE ANY
KOREAN SK TELECOM [SHV-E250S] SUPPORTED. NO THREAD YET. USE ANY
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit/Windows 10
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.

**FAQ**
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF (e.g removing system apps).
From Google:
Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
----------------------------------------------------------------------------
Q. I flashed CWM but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on Android that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from the Market). Delete the file recovery-from-boot.p from /system. Now when you flash CWM Recovery it will NOT be overwritten after a reboot. You can also use the Toolkit to rename the files if you wish.
----------------------------------------------------------------------------
Q. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.
Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).
----------------------------------------------------------------------------
Q. When would i perform a nandroid vs a titanium backup?
You would perform a nandroid backup to back up your entire system including boot image and data and system partitions so you can restore your entire system back to that particular point in the future.
You would use Titanium Backup mainly to back up your installed apps and settings so they could be reinstalled easily and quickly on any future roms. You can also choose individual apps to backup or restore on Titanium Backup whereas if you restore your boot partition via CWM Recovery you are stuck with the whole lot.
----------------------------------------------------------------------------
Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.
The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) will pick it up as potentially harmful when it is not. They pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
----------------------------------------------------------------------------
Q. I donated but where do I get my activation code from?
Donation Codes are sent out manually to your PayPal email address [unless otherwise stated] after a confirmation email from PayPal has been receive. The Code can then be entered in the ToolKit Settings, Activate Donators Features Screen. This will enable The Auto Updates, Quick Picks and Extras Features in the ToolKit. Please be patient when waiting for the Code to be sent as it depends very much on what I am doing and whether I am at my PC when the donation is made. Please do not post in the ToolKit's thread or pm me asking for the activation code as it clogs up the thread and my messages. If you haven't received your code after 24 hours then feel free to email me via the skipsoft.net contact page.
Don't worry that you have been forgotten about, I check all emails personally and will deal with it as soon as I can.
----------------------------------------------------------------------------
Q. I have Windows 8 and cannot install the drivers
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.
----------------------------------------------------------------------------
Q. I flashed the Stock Firmware Image. Odin flashes the file successfully and the phone reboots but it stays stuck on the samsung logo
If the firmware tar file does not include a userdata image (which most Samsung firmware do not) then your userdata partition will be left from your previous setup. If this is incompatible with the new firmware because of build or something else then your system will freeze on boot up.
This is easily fixable by holding the Volume UP, Home and Power buttons all at the same time for about 10 seconds until the device reboots to the Stock Recovery screen. Use the Volume Down button to scroll down to 'wipe data/factory reset' and press the Home button to select it. Go down to yes to confirm and your userdata partition will be wiped. Your device should now boot fine.

**RESERVED FOR MANUAL INSTRUCTIONS**

How To Videos on the Samsung Galaxy Note II ToolKit
Reserved for how to videos on this incredible toolkit!
http://www.youtube.com/playlist?list=PLwCVKEYxr_z7FBQYT32dbYw_kdSJmSDH2
How To Root
http://www.youtube.com/watch?v=M9zF6x1MURM
How To Flash Stock Recovery
http://www.youtube.com/watch?v=9CL5x84Tu_U

i did this now im stuck in boot loops anyone know what i should to [email protected]

tfaulk88 said:
i did this now im stuck in boot loops anyone know what i should to [email protected]
Click to expand...
Click to collapse
You did what exactly?
Mark.

tfaulk88 said:
i did this now im stuck in boot loops anyone know what i should to [email protected]
Click to expand...
Click to collapse
Worked for me! https://twitter.com/wwjoshdew/status/261983982898511872

ToolKit v2.0.0 (27th October 2012)
+Added FULL support for Sprint (SPH-L900)
Click to expand...
Click to collapse
When you say full support does that mean you have the factory images?

scrosler said:
When you say full support does that mean you have the factory images?
Click to expand...
Click to collapse
That should fix a few soft bricks if so
Sent from my SPH-L900 using xda premium

thanks
thank you so much

Not updating?
Not able to updat from ver 1.1 to ver 2.0? I've donated...
Thanks for any help or info...

Didnt the OP say multiwindow at one point? Was that a typo or am i dreaming?
Thanks,
JD

i tried to flash the stock image now im getting firmware upfrade encountered an issue please select recovery mode in kies and try again
---------- Post added at 12:32 PM ---------- Previous post was at 11:36 AM ----------
has anyone flashed back to stock with this tool kit with success

JudasD said:
Didnt the OP say multiwindow at one point? Was that a typo or am i dreaming?
Thanks,
JD
Click to expand...
Click to collapse
Yeah I saw it too. Imagine my disappointment when I couldn't find a hint of the option. The toolkit is still really good. I hope such a feature is added soon.
Sent from my SPH-L900 using Tapatalk 2

Sess said:
Yeah I saw it too. Imagine my disappointment when I couldn't find a hint of the option. The toolkit is still really good. I hope such a feature is added soon.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
That was for the N7100 thread lol and yes I did take it off as I thought it would be confusing. The Multiwindow function was added in the ALJ3 firmware and I think most of the US Models are on the ALJ1 firmware at the moment so as soon as your firmware gets updated or someone posts a mod patch you should be able to use it. Its one of the best functions I have seen on a phone and very useful on the big screen.
Mark.

tfaulk88 said:
i tried to flash the stock image now im getting firmware upfrade encountered an issue please select recovery mode in kies and try again
---------- Post added at 12:32 PM ---------- Previous post was at 11:36 AM ----------
has anyone flashed back to stock with this tool kit with success
Click to expand...
Click to collapse
What stock image?
The stock images listed in the download section are only N7100 models right now but hopefully some images should be leaked soon for the other variants.
Mark.

WhiteEVO said:
Not able to updat from ver 1.1 to ver 2.0? I've donated...
Thanks for any help or info...
Click to expand...
Click to collapse
I am trying to upload the v2.0.0 Auto Update version to my server but my hoster only allows files upto a certain size so I have had to emai them to explain what the file is and why I need to upload it. Hopefully it will be resolved tonight but you can allways download the full version for now as it will install over 1.1.0 without problems. This was a huge update in terms of file size so the update size is more than half the size of the entire toolkit lol.
Mark.

scrosler said:
When you say full support does that mean you have the factory images?
Click to expand...
Click to collapse
No there are no factory images available yet so I guess its not 100% full lol.
As you are a recognised dev can you get me the mount points for the sprint model please? I need to know what/if changes there are over the N7100 model.
Mark.

mskip said:
That was for the N7100 thread lol and yes I did take it off as I thought it would be confusing. The Multiwindow function was added in the ALJ3 firmware and I think most of the US Models are on the ALJ1 firmware at the moment so as soon as your firmware gets updated or someone posts a mod patch you should be able to use it. Its one of the best functions I have seen on a phone and very useful on the big screen.
Mark.
Click to expand...
Click to collapse
Well that would explain it. I was perusing the original threads for quite a while before I was able to get the phone. It's very likely that I just confused the two. I hope the update comes out soon. Videos of multi window on youtube are quite awesome.
Sent from my SPH-L900 using Tapatalk 2

Wow, I mean wow is this slick, so easy, so nice this tool kit is BOSS! seriously awesome work to everyone involved in not only the toolkit, but the rooting and recovery, everything so freakin' slick!
I was so excited to get this phone I didn't even consider rooting it until I was standing in the store paying for it, then It was like someone kicked me in the gut, I hope they can get root on this pretty quick, no way did I think it would be the first day, let alone this full blown tool kit so soon.
So yeah, once again nice job!

Reverting back to Fire OS from CM11

Hello All!
I decided to install CM 11 a few days ago and then thought I'd like to go back to Fire OS. I followed the instructions as much as I could from the thread on here to revert back but I have ran into a problem. I could only get 4.6.1 installed but obviously, 4.6.3 is out and my phone can see it's there to download (and it does (try to) download - every time I restart my phone). When the download finishes the phone says there is an error and it can't update but then I can search for the update and so on. I have tried doing it the way Amazon suggest from my PC but to no avail.
I can only assume that this has something to do with the fact I went from 4.6.3 to CM 11 and then back to 4.6.1 and the phones still sees itself has partially being on 4.6.3?
Any help is much appreciated!
Thanks

doing it the way Amazon suggest from my PC but to no avail
Click to expand...
Click to collapse
That means you downloaded the 4.6.3 BIN image and tried sideloading it via ADB?
If not, take a look at this (scroll down to the paragraph "Recovery / Sideload Factory Images")
I think OTA update is useless at this point but using the Amazon stock recovery is very reliable, I used it many times in the beginning for testing purposes.
Just give us some details when you encounter problems, e.g. driver missing when connected to PC, etc. ... and don't forget your backup for important apps & app settings.

I tried doing this before and the CMD does not show as any devices being connected. I have it in debugging mode and plugged it in but Windows did not see it even though the phone shows as being connected. Also, just in case I tried using the command you send and it just says "* cannot read 'update.bin' *".

You have the phone connected while booted up in Fire OS OR booted up in recovery mode like the guide suggests?
Sounds like you're missing ADB drivers / Windows failed to change the drivers when phone is connected in ADB recovery mode. Indicators:
• Windows did not "see" the phone
• The command line in CMD doesn't work without proper ADB configuration
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.
That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try this tool (& driver) ADB, Fastboot and Drivers
Maybe you need to manually check for the "new" device and update the drivers:
Open the device manager while your phone is connected in recovery mode.
Look for its entry in the device list.
Remove it (Deinstall it).
Then "scan for hardware changes":
The device should appear in list the again, it will install the needed driver automatically (best case scenario)
or
you will have to update the device drivers manually:
You can even use (old) "Google USB drivers", I successfully tested google drivers from 2010 on Win 7 x64 with this phone in ADB mode.
If everything worked as planned, it should look like this: next to your device name, it will say "sideload":

It seems that on Windows 10 it works/looks different. I updated the driver that was suggested but I had another one which also needed updating which I have just done and appears to now let the cmd see the device properly and also allowing me to sideload.
Device manager does not see it as an Android device but as a Samsung device. Not sure why this is unless the device drivers used were Samsung ones but I guess that is irrelevant now. I will post my results once the update has finished.
Also, thanks for the help with this. Your information did help and with a bit of tweaking, it appears to have worked.

Thanks for mentioning so early that you use Windows 10, that makes it so much easier for me. :laugh:
Nah, but it looks like you will be good from here on out...
Btw. by sideloading the image, it will erase "everything" on your device, so you get clean system without leftovers, just like you hoped for.

Can you add the link for the thread you used to revert back from CM11 to FireOS?

paulalva05 said:
Can you add the link for the thread you used to revert back from CM11 to FireOS?
Click to expand...
Click to collapse
The link is actually in the first reply but I have put it below anyway!
http://forum.xda-developers.com/showpost.php?p=61271723&postcount=2

Bingo Bronson said:
You have the phone connected while booted up in Fire OS OR booted up in recovery mode like the guide suggests?
Sounds like you're missing ADB drivers / Windows failed to change the drivers when phone is connected in ADB recovery mode. Indicators:
• Windows did not "see" the phone
• The command line in CMD doesn't work without proper ADB configuration
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.
That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
Try this tool (& driver) ADB, Fastboot and Drivers
Maybe you need to manually check for the "new" device and update the drivers:
Open the device manager while your phone is connected in recovery mode.
Look for its entry in the device list.
Remove it (Deinstall it).
Then "scan for hardware changes":
The device should appear in list the again, it will install the needed driver automatically (best case scenario)
or
you will have to update the device drivers manually:
You can even use (old) "Google USB drivers", I successfully tested google drivers from 2010 on Win 7 x64 with this phone in ADB mode.
If everything worked as planned, it should look like this: next to your device name, it will say "sideload":
Click to expand...
Click to collapse
Hi, thank you for the detailed instruction. My pc can recognize and show the name of my firephone, just like what you showed in the image. But when I type "adb sideload update.bin", it still says "cannot read update.bin" What can I do now? Thank you so much.

iHuyou said:
But when I type "adb sideload update.bin", it still says "cannot read update.bin" What can I do now? Thank you so much.
Click to expand...
Click to collapse
Validate the MD5 checksum, maybe your downloaded image is corrupted...

Is the update.bin file in a different directory?

Bingo Bronson said:
Validate the MD5 checksum maybe your downloaded image is corrupted...
Click to expand...
Click to collapse
Hi, Bingo Bronson, thank you for your reply. What I downloaded from the link in your original post is a WinRAR ZIP archive. When I open it, there are multiple file and folders in there. There is a file called boot.img, should I change its name to update.bin and sideload it? But it is only 8Mb. Can you give a little more detailed instruction? Thanks

iHuyou said:
[...] is a WinRAR ZIP archive. But it is only 8Mb. Can you give a little more detailed instruction? Thanks
Click to expand...
Click to collapse
Whoops, I think you took a wrong turn there somewhere, too many files, what to choose...!?!
edit: Slight misunderstanding, luckily iHuyou found the solution by himself. :victory:
This is the direct download link from Amazon for the latest GSM unlocked version: http://fire-phone-updates.s3.amazon...update-fire-phone-35.4.6.3_user_463001620.bin
An here is the direct download link from Amazon for the latest AT&T version: http://fire-phone-updates.s3.amazon...HC5/update-kindle-32.4.6.5_user_465000520.bin
I don't know which version you had installed, so just pick the link according to your initial Fire OS version. Reply again if you have further questions. :good:

Bingo Bronson said:
Whoops, I think you took a wrong turn there somewhere, too many files, what to choose...!?!
I don't know which version you had installed, so just pick the link according to your initial Fire OS version. Reply again if you have further questions. :good:
Click to expand...
Click to collapse
Thanks again, Bingo Bronson. I figured it out. The bin file has to be in the same directory as the adb file, otherwise adb cannot find the bin file therefore cannot read it. I have successfully sideloaded 4.6.5 following your post. Thank you!

Blank Screen amazon fire phone
Hello Guys i need help with my amazon fire phone, I tried to revert back from cm11 to stock rom (http://www.android.gs/downgrade-amazon-fire-phone-to-stock-fire-os-3-5/) using this site's method i got error sideloading from stock recovery then i tried it from safe strap recovery and it went successful but before sideloading update.bin from safestrap recovey i wiped and i did not know what options i selected but now my fone wont boot only black screen and when i connect it to pc it shows 3,4 partitions and says format, format... what went wrong ?

[Help Thread]Kindle Fire 2] Ask Any Question, Noob Friendly

[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
Kindle Fire 2 - 2012​
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters@sd_shadow
...
...
...​To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. If you are not eligible of posting there, you may post here. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
Fire Index: Which Amazon (Kindle) Fire Do I have? There are several 7' Amazon Fires. Be sure you know which one you have
[Index] Amazon 7" Kindle Fire HD, 8.9" Kindle Fire HD, Kindle Fire 2
[REF]All Things About Kindle Fire 2
Frequently Asked Questions - 2nd Generation Kindle Fires
Please look for a similar [HELP THREAD] when visiting another device forum.
If you would like to create a similar [Help Thread] please Click Here.
​

[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]Kindle Fire 2[/SIZE]​
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. [/SIZE]
[SIZE=+1]Q1: How do I know if i have a Kindle Fire 2?[/SIZE]Kindle Fire 2 has a 7" screen, No Camera, No Volume Buttons, Looks just like the Kindle Fire 1​[SIZE=+1]Q2: How do I tell the Kindle Fire 1 from 2?[/SIZE]kindle Fire 1's will have a system version that starts with 6 (6.3.3, 6.3.4...).​*​Forum Rules | New Users Guide | XDA Tour | Report Posts​A special thanks to everyone who contributed to the production of this FAQ​

Basic Info
Kindle Fire 2 - 2012
7" screen, No Camera, No Volume Buttons
Model # KFOT
Serial #D026
Codename: Otter2
[REF]All Things About Kindle Fire 2 Last edited by Zeuscluts; 2nd July 2014
Frequently Asked Questions - 2nd Generation Kindle Fires

Need help rooting Kindle Fire gen 2
(Another weekend.. another attempt!)
I have a Kindle Fire Gen 2
System Version: Current version 10.5.1
Serial number starts with D0026
OS: Windows 7
I have looked at this thread/post:
http://forum.xda-developers.com/showthread.php?t=2247493
And am trying to following this rooting tutorial:
http://forum.xda-developers.com/showthread.php?t=2075959
When I get to this step:
Step 1: Type this in the window, hitting enter after each line.
cd ..\..\Root
runme.bat
I get these results:
Code:
Device type:
0) New Z2 Root Method by cubeandcube (thanks man!)
1) 2014 root (thx jcase for nice pwn binary :) and xsacha for the exploit)
2) Xperia Root by cubeundcube
3) New Standard-Root (thx Ariel Berkman)
4) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
5) Old
6) Old-Special (for example: Sony Tablet S, Medion Lifetab)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 1
Exploit type:
0) xsacha Z2 Tablet Root
1) jcase Z1S Root (make sure to download the pwn binary first from XDA thread!)
Make a choice:
Please connect your device with enabled USB-Debugging ...
adb server is out of date. killing...
* daemon started successfully *
and then it does nothing.
after a while.. I tried to quit, and got this:
Code:
Terminate batch job (Y/N)? n
Copy needed files ...
error: device not found
error: device not found
error: device not found
error: device not found
..........................
I have performed the Windows 7 mod here:
http://forum.xda-developers.com/showthread.php?p=36373627#post36373627
I have also verified the ADB drivers as mentioned here:
http://forum.xda-developers.com/showthread.php?t=2069117
"Once this driver has been properly installed you will see "Android Composite ADB Interface" under "Kindle Fire" in the Windows Device Manager which is located by Right Hand Mouse Click Computer, Choose Properties, then Devices or Device Manager. Expand the tree. Expand Kindle. This is where you will see "Android Composite ADB Interface"."
^^ which I do show/have in my Device Manager
Can anyone help me getting my Kindle Fire Gen 2 rooted? Or suggest something I may have overlooked/not done correctly?
thanks.

xl97 said:
(Another weekend.. another attempt!)
I have a Kindle Fire Gen 2
System Version: Current version 10.5.1
Serial number starts with D0026
OS: Windows 7
I have looked at this thread/post:
http://forum.xda-developers.com/showthread.php?t=2247493
And am trying to following this rooting tutorial:
http://forum.xda-developers.com/showthread.php?t=2075959
When I get to this step:
Step 1: Type this in the window, hitting enter after each line.
cd ..\..\Root
runme.bat
I get these results:
and then it does nothing.
after a while.. I tried to quit, and got this:
I have performed the Windows 7 mod here:
http://forum.xda-developers.com/showthread.php?p=36373627#post36373627
I have also verified the ADB drivers as mentioned here:
http://forum.xda-developers.com/showthread.php?t=2069117
"Once this driver has been properly installed you will see "Android Composite ADB Interface" under "Kindle Fire" in the Windows Device Manager which is located by Right Hand Mouse Click Computer, Choose Properties, then Devices or Device Manager. Expand the tree. Expand Kindle. This is where you will see "Android Composite ADB Interface"."
^^ which I do show/have in my Device Manager
Can anyone help me getting my Kindle Fire Gen 2 rooted? Or suggest something I may have overlooked/not done correctly?
thanks.
Click to expand...
Click to collapse
reboot pc
try a different USB port

sd_shadow said:
reboot pc
try a different USB port
Click to expand...
Click to collapse
done as suggested (rebooted.. tried 2 different USB ports)
my results:
Code:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry =
= (15.06.2014) v36 =
======================================================================
Device type:
0) New Z2 Root Method by cubeandcube (thanks man!)
1) 2014 root (thx jcase for nice pwn binary :) and xsacha for the exploit)
2) Xperia Root by cubeundcube
3) New Standard-Root (thx Ariel Berkman)
4) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
5) Old
6) Old-Special (for example: Sony Tablet S, Medion Lifetab)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 1
Exploit type:
0) xsacha Z2 Tablet Root
1) jcase Z1S Root (make sure to download the pwn binary first from XDA thread!)
Make a choice: 1
Please connect your device with enabled USB-Debugging ...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Kindle does nothing.. sits on home screen
funny thing now.. when I plug/un-plug the kindle from the USB port.. I am no longer getting the 'prompt' asking me what I want to do.. (open folder..etc)

xl97 said:
done as suggested (rebooted.. tried 2 different USB ports)
my results:
Kindle does nothing.. sits on home screen
funny thing now.. when I plug/un-plug the kindle from the USB port.. I am no longer getting the 'prompt' asking me what I want to do.. (open folder..etc)
Click to expand...
Click to collapse
try kingroot
KINGROOT Thread
Sent from my XT1060 using XDA Labs

xl97 said:
done as suggested (rebooted.. tried 2 different USB ports)
my results:
Kindle does nothing.. sits on home screen
funny thing now.. when I plug/un-plug the kindle from the USB port.. I am no longer getting the 'prompt' asking me what I want to do.. (open folder..etc)
Click to expand...
Click to collapse
Edit!:..
sd_shadow said:
try kingroot
Click to expand...
Click to collapse
Indeed it does! Thank You! Take~Care!
For one I have yet to find any root on XDA or elsewhere that is working on the KF2 System Version 10.5.1 Be sure that you have Enable ADB in Settings > Security set to on. Also be sure you have Allow installation of Applications / From unknown Sources in Settings > Device set to on.
After that please enter the folder Root_with_Restore_by_Bin4ry_v36\stuff and open a command prompt - I use elevated cmd prompt in my context menu so all I need to do is right mouse click on the folder where I wish cmd prompt to open and select > Open command window here as Administrator.. If you wish you can download the .reg file to give you this option with instructions if needed here...
Code:
http://www.sevenforums.com/tutorials/47415-open-command-window-here-administrator.html
Once cmd prompt is open in that folder please type....
adb devices
You should see a message something like
List of devices attached
D026A0A0328601E8 device
If not I would UNinstall any drivers you have installed > Reboot > INstall the drivers linked below > reboot and try the above steps again...
Code:
http://www.mediafire.com/download/cizq7o8mwwqh9ji/Kindle_Fire2_ADB_Drivers.zip
If still no listed devices after opening cmd prompt > adb devices then I would check your factory cable maybe try another.
My apologies if this is to be no help. Take~Care!

rb2tfm said:
Edit!:..
Indeed it does! Thank You! Take~Care!
For one I have yet to find any root on XDA or elsewhere that is working on the KF2 System Version 10.5.1 Be sure that you have Enable ADB in Settings > Security set to on. Also be sure you have Allow installation of Applications / From unknown Sources in Settings > Device set to on.
After that please enter the folder Root_with_Restore_by_Bin4ry_v36\stuff and open a command prompt - I use elevated cmd prompt in my context menu so all I need to do is right mouse click on the folder where I wish cmd prompt to open and select > Open command window here as Administrator.. If you wish you can download the .reg file to give you this option with instructions if needed here...
Code:
http://www.sevenforums.com/tutorials/47415-open-command-window-here-administrator.html
Once cmd prompt is open in that folder please type....
adb devices
You should see a message something like
List of devices attached
D026A0A0328601E8 device
If not I would UNinstall any drivers you have installed > Reboot > INstall the drivers linked below > reboot and try the above steps again...
Code:
http://www.mediafire.com/download/cizq7o8mwwqh9ji/Kindle_Fire2_ADB_Drivers.zip
If still no listed devices after opening cmd prompt > adb devices then I would check your factory cable maybe try another.
My apologies if this is to be no help. Take~Care!
Click to expand...
Click to collapse
update:
ok.. well things are looking up! lol
* I am now getting a prompt when I connect the KF to the PC.. (so I can open up folders/directories..etc)
* I also now get a number back in the device list (adb device command suggested above) as well.
I tried the ROOT and QEMU steps above again.. and the device is now being somewhat responsive (as in rebooting when the screen says it will..etc)
most lines that say::
UNABLE TO CHMOD....
FAILED TO COPY FILE...
QEMU always ends with 'ROOTING FAILED!' message..
but at least its a start in the right direction!
@sd_shadow -
If RootKing approach is still recommended.. I have a some questions from quickly reading the link/overview.
* this can -not- be installed after install? (am I reading that correctly?)
* do I use the desktop or .apk approach?
* If .apk...this is done by transferring the file to my KF.. where does it get transferred to? (and how to 'run it')
thanks.

xl97 said:
update:
@sd_shadow -
If RootKing approach is still recommended.. I have a some questions from quickly reading the link/overview.
* this can -not- be installed after install? (am I reading that correctly?)
* do I use the desktop or .apk approach?
* If .apk...this is done by transferring the file to my KF.. where does it get transferred to? (and how to 'run it')
thanks.
Click to expand...
Click to collapse
Cool on the looking up =) My apologies for butting in as obviously I'm not sd_shadow....
As I stated in my original post before the edit I have found nothing but kingroot that will work.
So honestly, before you root, unless you have a file manager / explorer already installed on your kindle, I would go to the amazon store on your kindle and download / install ES File Explorer. The one I was working on did not have one installed and it gave me issues due to not being able to locate and install the .apk's unless they were from the amazon store where it could auto-install after downloaded.
Code:
http://www.amazon.com/ES-Mobile-File-Explorer/dp/B008K6HN8I/ref=sr_1_1?s=mobile-apps&ie=UTF8&qid=1458374068&sr=1-1&keywords=es+file+explorer
No settings in ES File Explorer need to be messed with until after root and then I would change the settings to use the recycle bin, show hidden files, root explorer ( root explorer, when enabled will try to get root permission... Just allow it access when prompted ) and a few others, but the rest are simple and I am sure you can get it to your liking.
After ES File Explorer is installed then I would go to the bottom of the first post here...
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
and download the attached KingRoot4.1-release-20150703-for-xda.apk if you downloaded with the kindle then just use ES file explorer to locate the KingRoot4.1-release-20150703-for-xda.apk , select it and it will install. Once installed, run the kingroot app.. it 'may' say there is not root for the device but run it anyway because it will root it.
Remember... No one twisted your arm on rooting your device.... You chose to do so and No damage is done to the device by rooting it.
After root then back to what I said earlier...
I would change the settings to use the recycle bin, show hidden files, root explorer ( root explorer, when enabled will try to get root permission... Just allow it access when prompted ) and a few others, but the rest are simple and I am sure you can get it to your liking.
Click to expand...
Click to collapse
From there you should probably go through this thread awhile if you haven't
http://forum.xda-developers.com/showthread.php?t=2228539
Need anything else... Just let us know. Take~Care!

xl97 said:
Edit!:..
Indeed it does! Thank You! Take~Care!
For one I have yet to find any root on XDA or elsewhere that is working on the KF2 System Version 10.5.1 Be sure that you have Enable ADB in Settings > Security set to on. Also be sure you have Allow installation of Applications / From unknown Sources in Settings > Device set to on.
After that please enter the folder Root_with_Restore_by_Bin4ry_v36stuff and open a command prompt - I use elevated cmd prompt in my context menu so all I need to do is right mouse click on the folder where I wish cmd prompt to open and select > Open command window here as Administrator.. If you wish you can download the .reg file to give you this option with instructions if needed here...
Once cmd prompt is open in that folder please type....
adb devices
You should see a message something like
List of devices attached
D026A0A0328601E8 device
If not I would UNinstall any drivers you have installed > Reboot > INstall the drivers linked below > reboot and try the above steps again...
update:
ok.. well things are looking up! lol
* I am now getting a prompt when I connect the KF to the PC.. (so I can open up folders/directories..etc)
* I also now get a number back in the device list (adb device command suggested above) as well.
I tried the ROOT and QEMU steps above again.. and the device is now being somewhat responsive (as in rebooting when the screen says it will..etc)
most lines that say::
UNABLE TO CHMOD....
FAILED TO COPY FILE...
QEMU always ends with 'ROOTING FAILED!' message..
but at least its a start in the right direction!
@sd_shadow -
If RootKing approach is still recommended.. I have a some questions from quickly reading the link/overview.
* this can -not- be installed after install? (am I reading that correctly?)
* do I use the desktop or .apk approach?
* If .apk...this is done by transferring the file to my KF.. where does it get transferred to? (and how to 'run it')
thanks.
Click to expand...
Click to collapse
I don't always go back and look for edited posts
so if you add information/questions
please add a new post, even if it just says see edit
root king should work, and should be safe
I'm not sure what is meant by "cannot be installed after install" means?
yes, use desktop or apk
if using apk, allow unknown sources on Fire, download apk with Web browser on Fire, after downloading is complete click on download complete notification bar, there will be a install prompt
Sent from my XT1080 using XDA Labs

Hello
I stupidly bricked my kf2, I thought I could do it without a fastboot cable.
the guide I was following was https://wiki.cyanogenmod.org/w/Install_CM_for_otter2
Got to step 6 no problems, kindle rebooted I missed what happened but it said something about having to wipe/format system then rebooted. now it just shows kindle logo for 5 seconds and then reboots and then again
I have ordered a cable after destroying 6 trying to make a fastboot one but going to be waiting weeks from china.
Anyways not the first device I have bricked and likely not the last, my question is what procedure should I follow when I do get it as I dont want to do more damage.
Thank you in advance

@rb2tfm - thanks!
@sd_shadow - thanks as well!
so to re-cap:
I have a fresh system restored KF Gen 2
I downloaded, and installed ES File Explorer.
I downloaded, and installed KingRoot (.apk file)..
When download was complete I ran KingRoot file....
Ran through some screens, had button saying TRY ROOT AGAIN.. I clicked it.. and waited until numbers were done counting..etc..
I walked away and came back to me being at the 'home' page... of the KF..
(page says to go to Google play and download root checker.. but I cant because when I go there is says browser (SILK) not supported)
If I load KingRoot again.. it shows home page with a count -down- from 100% and always seems to stop @ 56%? (Security Index/Checking running state...)
ES File Explorer settings have been changed to allow Root Exploring, Recycle Bin and Show Hidden Files as well..
At this point I'm not really clear what my next step is?
Go to this thread and try to install google play?
http://forum.xda-developers.com/showthread.php?t=2228539
My end goal here is to install the latest version of Android that I can on this device.. (or at least the latest that runs the best!)
Which 'ROM' is suggested for this step (once I get there?)
thanks!

@rb2tfm -
 @sd_shadow -
After a reboot of the device...
and running KingRoot again..
I got the message Root successful, share with friends?
and the Security Index now shows 100% (with text of running state.... under it still)
I'm guessing I'm rooted now? lol..
but really un-clear what my next step is?
thanks!

Honor 7
Sent from my PLK-L01 using Tapatalk

dibbler.c said:
Honor 7
Sent from my PLK-L01 using Tapatalk
Click to expand...
Click to collapse
huh?
Is this a response to me?
What does that (Honor 7) mean?

xl97 said:
@rb2tfm -
@sd_shadow -
After a reboot of the device...
and running KingRoot again..
I got the message Root successful, share with friends?
and the Security Index now shows 100% (with text of running state.... under it still)
I'm guessing I'm rooted now? lol..
but really un-clear what my next step is?
thanks!
Click to expand...
Click to collapse
you need to install the 2nd bootloader from Hashcode
see his thread
Sent from my XT1060 using XDA Labs

xl97 said:
huh?
Is this a response to me?
What does that (Honor 7) mean?
Click to expand...
Click to collapse
just spamming
Sent from my XT1060 using XDA Labs

link to 2nd bootloader thread
http://forum.xda-developers.com/showthread.php?t=2100963
Sent from my XT1060 using XDA Labs

Bricked KF2 trying to install 2nd bootloader. It now turns on, shows the standard boot screen and immediately goes blank except for a white triangle in the middle with an exclamation point inside of it.
I can get it into fastboot mode with my factory cable, but I have no idea how to get it back to working condition.