Develop Bugs

problems rooting

I have KFHD 8.9 v8.3. I am having problems getting fastboot working. I have read threads that there are specific "fastboot drivers" and then I have seen other threads where fastboot drivers are a part of the Kindle Fire drivers installed by ...\sdk\extras\amazon\kindle_fire_usb_driver\KindleDrivers.exe. No matter what I do I am unable to get "fastboot -i 0x1949 getvar product" to work. At one point I had it rooted with validation from suchecker, still couldnt get fastboot to work, but factory restored to 8.3 to validate steps and instructions and it is a nogo at the moment.
Any help would be appreciated.

So, is your device rooted or not? Your post in another forum seems to contradict what you are saying here.

Liek Soupmagnet said are you positive that your device has root access? If so, I would try wipe the drivers and start from scratch.
As far as I know and it worked for me, fastboot drivers are loaded when you install Android SDK on your PC. See picture bellow.
However in case you need the fastboot drivers you can download here: https://docs.google.com/folder/d/0B4lZEJI5lYeMdzJobG5jSk9QSEk/edit?pli=1 as referenced here: http://forum.xda-developers.com/showpost.php?p=34589184&postcount=6
These ADB drivers worked for me: http://forum.xda-developers.com/showthread.php?t=1890413
For Kindle drivers and Amazon drivers for Windows 8 (if the case),please take a look here: http://forum.xda-developers.com/showthread.php?t=2185402 however I did need not need them.
Is your Kindle showing up when you type the command ADB Devices cmd/terminal window?
I hope it helps.

soupmaget,
I responded to your PM and I said I would try the SoupKit tonight. Calling me out in forums doesn't help you or me and dont know why you keep doing that. I am trying many things but it boils down to the same specific commands. I have even tried the below downloads manually grabbing the commands and typing them in manually.
Last night I refreshed my env following the amazon tutorials step by step. I finally got root by running Root_with_Restore_by_Bin4ry_v25 twice and then Kindle_Fire_Utility_v0.9.6 rooting via recommended option twice. ADB does work, I can "adb reboot", "adb shell" push files, mv files, etc. SUCheck validates I have root.
When I continue to hashchodes TWRP and 2nd bootloader tutorial it states that "you should have working fastboot drivers" which to me means that there is a separate download/driver to install for it to work. I know fastboot.exe is included in the ADK and tried using the other tools for getting fastboot working but its not working.
I do run these with administrative rights....
D:\android\sdk\platform-tools>adb devices
List of devices attached
B0CA060424841KF0 device

So technically this thread is specific to rooting and can be closed as I am passed rooting now and on to fastboot issue...

rwideman said:
So technically this thread is specific to rooting and can be closed as I am passed rooting now and on to fastboot issue...
Click to expand...
Click to collapse
You are blowing my mind right now with your refusal to be helped. Why are you so hell bent on making this difficult for yourself? You have a $300 device that doesn't work and you're being resistant to someone who can most likely help you get it working again. Why? I don't get it...
From what I gather in your various posts, your device is rooted but you cannot access fastboot via the traditional method of entering "fastboot -i 0x1949 getvar product" in the terminal and powering the device up.
Assuming you have a usb/adb/fastboot connection problem with your Mac, you can use SoupKit, but only in certain VMs. But if you have had a previous connection with either fastboot or adb, that probably isn't the case.
Theres a good chance that you can install the Android Terminal Emulator, enter 'su' to gain root privileges and enter "reboot bootloader". That should boot your device into fastboot so you can enter fastboot commands. But, as I told you before, if there is a usb connection problem, and you cannot send fastboot commands to your device, you will be stuck in fastboot. If you have another non-Mac computer available to you, it would be best to boot it into Linux and install soupkit to make sure that doesn't happen. BTW, that is nearly verbatim to what I told you via the first PM.

Are you looking at the timestamps of my postings? Things change over time....
Did you read my PM response? I will try SoupKit tonight, I mentioned this after you told me to try it.
Thank you for your efforts.

My wife took the MBP for the night so I tried 2 old laptops with win7 x64 on them. copied over files and installed the kindle drivers as normal, got KFHD working with adb and then fastboot sits at the prompt waiting just like on my other env, even installed latest jdk 6 and nogo. I am SOL for the day so I will have a drink or 2 tonight and take one of those old laptops to work and install ubuntu 12.10 tomorrow and try again.
Thanks for the help.
FYI, I tried installing the terminal emu and runing "reboot bootloader" with a few fastboot command tries and nogo. I was able to hold the power button and get it to shut off once I got to fastboot mode.
FYI #2, under my previous env with vmware workstation 9 running unbuntu 12.04 in a vm I could not get fastboot to recognize the device but adb was recognizing it perfectly. Trying native ubuntu tomorrow.
FYI #3, In the professional world it is better to stick to non-psychologist bashing, what someone is and is not doing/thinking/acting, and sticking to the issue at hand. I have been in the IT world for 15 years and troubleshooting is my day job (windows, vmware, SAP, *nix, .net, java, j2ee, storage, UCS, routers, switches, nexus, cloud automation, orchestration, etc). Professionalism frowns upon psychologist speak.

rwideman said:
My wife took the MBP for the night so I tried 2 old laptops with win7 x64 on them. copied over files and installed the kindle drivers as normal, got KFHD working with adb and then fastboot sits at the prompt waiting just like on my other env, even installed latest jdk 6 and nogo. I am SOL for the day so I will have a drink or 2 tonight and take one of those old laptops to work and install ubuntu 12.10 tomorrow and try again.
Thanks for the help.
FYI, I tried installing the terminal emu and runing "reboot bootloader" with a few fastboot command tries and nogo. I was able to hold the power button and get it to shut off once I got to fastboot mode.
FYI #2, under my previous env with vmware workstation 9 running unbuntu 12.04 in a vm I could not get fastboot to recognize the device but adb was recognizing it perfectly. Trying native ubuntu tomorrow.
Click to expand...
Click to collapse
You're most likely looking at a driver issue. You might still be able to get them working in Windows. What did you use to install your drivers? Did you use an install package or did you do it manually?

I think I have the same problem. twrp installed on my device, but no OS running, and it can't be recognized on my computer, said driver incorrect, tried so many times, but can't get adb and fastboot work without driver supported. Don't know how to do.

soupmagnet said:
You're most likely looking at a driver issue. You might still be able to get them working in Windows. What did you use to install your drivers? Did you use an install package or did you do it manually?
Click to expand...
Click to collapse
I used these instructions:
https://developer.amazon.com/sdk/fire/connect-adb.html
using ...\sdk\extras\amazon\kindle_fire_usb_driver\KindleDrivers.exe
I tried a few different driver sets/packages by different places on the XDA threads but they all ended up being the same driver or detected the KDFHD89 exactly the same.

rwideman said:
I used these instructions:
https://developer.amazon.com/sdk/fire/connect-adb.html
using ...\sdk\extras\amazon\kindle_fire_usb_driver\KindleDrivers.exe
I tried a few different driver sets/packages by different places on the XDA threads but they all ended up being the same driver or detected the KDFHD89 exactly the same.
Click to expand...
Click to collapse
When it's in fastboot, do you see anything show up in the device manager?

soupmagnet said:
When it's in fastboot, do you see anything show up in the device manager?
Click to expand...
Click to collapse
Unfortunately no. I haven't had time doing linux with soupkit yet.

I had exactly the.problem still can't get fastboot too see my kindle8.9.
used amrzon driver from sdk.
Adb devices is fine i see the kfhd serial number. .but once use fastboot cmd waiting for device then.never boot in fastboot mode. just boot back to lock screen .This is rooted 8.9 with 8.3 os.
maybe i should do a factory reset.
in order to install a 2nd bootloader and tw-recovery u have to have a rooted kindle hd8.9?

jonahy said:
I had exactly the.problem still can't get fastboot too see my kindle8.9.
used amrzon driver from sdk.
Adb devices is fine i see the kfhd serial number. .but once use fastboot cmd waiting for device then.never boot in fastboot mode. just boot back to lock screen .This is rooted 8.9 with 8.3 os.
maybe i should do a factory reset.
in order to install a 2nd bootloader and tw-recovery u have to have a rooted kindle hd8.9?
Click to expand...
Click to collapse
Yes, you have to be rooted to install the 2nd bootloader and TWRP. I put together the SoupKit so people with driver issues such as yourself can use Linux without much trouble because it is 100 times more reliable than Windows. You should look into it. You can use RootPlus to get root but don't use it to install the 2nd bootloader on 8.3.0 or you will be bricked, likely permanently. But you will be able to use fastboot without any problem to do it manually.

soupkit Folder Empty out
soupmagnet said:
Yes, you have to be rooted to install the 2nd bootloader and TWRP. I put together the SoupKit so people with driver issues such as yourself can use Linux without much trouble because it is 100 times more reliable than Windows. You should look into it. You can use RootPlus to get root but don't use it to install the 2nd bootloader on 8.3.0 or you will be bricked, likely permanently. But you will be able to use fastboot without any problem to do it manually.
Click to expand...
Click to collapse
Hi Thank you for the direction.
I made a Ubuntu 12.10 usbkey booted
then copied ur soupkit folder on desktop Run install.sh ( have to go into permisions check the allow excute)
Run in terminal then terminal show 2 " closed then all the file in soupkit is gone..ha.
didnt see option 1 and 2.
Then i try in Ubuntu termal do abd and fastboot but same as in window 7 KFHD89 just boot into lock screen.
(adb devices it can see devices though
Setting up android-tools-adb (4.1.1+git20120801-1) ...
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
B0C9100425160LG8 device)
fastboot not
([email protected]:~$ sudo apt-get install android-tools-fastboot
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
android-tools-fastboot
0 upgraded, 1 newly installed, 0 to remove and 337 not upgraded.
Need to get 48.6 kB of archives.
After this operation, 129 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu/ quantal/universe android-tools-fastboot i386 4.1.1+git20120801-1 [48.6 kB]
Fetched 48.6 kB in 0s (105 kB/s)
Selecting previously unselected package android-tools-fastboot.
(Reading database ... 161214 files and directories currently installed.)
Unpacking android-tools-fastboot (from .../android-tools-fastboot_4.1.1+git20120801-1_i386.deb) ...
Setting up android-tools-fastboot (4.1.1+git20120801-1) ...
[email protected]:~$ fastboot -i 0x1949 getvar product
< waiting for device >
I was thinking maybe its the Root_with_Restore_by_Bin4ry_v26 mess up somthing? I know my KFHD is rooted it by, but if i load any app need root never show the window ask me if i allow this app in superuser massege.
anyway any tips abot that soupkit Folder Empty out issue?
(just got this tablet last friday, good device so far but put a recovery on it seems a bit harder then my other tablets...But hey I guess thats part of fun too right? )
Thank you in advance.

I think you're confused in how fastboot works. The device must be in fastboot (display says fastboot) in order for fastboot commands to work. There was no need to install android tools. There's a possibility that in doing so you may have made things worse, but we'll see...
Since you have access to adb, try the following command to boot into fastboot:
Code:
adb shell su -c "reboot bootloader"
This, of course, assumes your device is already rooted.
[Edit:] Also, to access Root Plus after installation, enter "rootplus" (without quotes) in the terminal.

Installed 2ND-BOOTLOADER
soupmagnet said:
I think you're confused in how fastboot works. The device must be in fastboot (display says fastboot) in order for fastboot commands to work. There was no need to install android tools. There's a possibility that in doing so you may have made things worse, but we'll see...
Since you have access to adb, try the following command to boot into fastboot:
Code:
adb shell su -c "reboot bootloader"
This, of course, assumes your device is already rooted.
[Edit:] Also, to access Root Plus after installation, enter "rootplus" (without quotes) in the terminal.
Click to expand...
Click to collapse
Great! Got Installed the 2nd bootloader and recovery .
adb shell su -c "reboot bootloader" boot device to fastboot mode.
thanks a lot! SoupMagnet.
Share steps:
D:\sdk\sdk\platform-tools>adb devices
List of devices attached
B0C9100425160LG8 device
D:\sdk\sdk\platform-tools>adb shell su -c "reboot bootloader"
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 getvar product
product: Jem-PVT-Prod-04
finished. total time: 0.006s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.003s
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/dev/block/platform/omap/omap_h
smmc.1/by-name/boot of=/sdcard/stock-boot.img"
16384+0 records in
16384+0 records out
8388608 bytes transferred in 0.939 secs (8933554 bytes/sec)
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/dev/block/platform/omap/omap_h
smmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
16384+0 records in
16384+0 records out
8388608 bytes transferred in 0.937 secs (8952623 bytes/sec)
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/dev/block/platform/omap/omap_h
smmc.1/by-name/system of=/sdcard/stock-system.img"
1814528+0 records in
1814528+0 records out
929038336 bytes transferred in 116.782 secs (7955321 bytes/sec)
D:\sdk\sdk\platform-tools>adb pull /sdcard/stock-boot.img
2794 KB/s (8388608 bytes in 2.931s)
D:\sdk\sdk\platform-tools>adb pull /sdcard/stock-recovery.img
3008 KB/s (8388608 bytes in 2.723s)
D:\sdk\sdk\platform-tools>adb pull /sdcard/stock-system.img
3004 KB/s (929038336 bytes in 301.978s)
D:\sdk\sdk\platform-tools>adb push stack /data/local/tmp/
571 KB/s (4096 bytes in 0.007s)
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/data/local/tmp/stack of=/dev/b
lock/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
0+1 records in
0+1 records out
4096 bytes transferred in 0.001 secs (4096000 bytes/sec)
D:\sdk\sdk\platform-tools>adb shell su -c "mount -o remount,rw ext4 /system"
D:\sdk\sdk\platform-tools>adb shell su -c "mv /system/etc/install-recovery.sh /s
ystem/etc/install-recovery.sh.bak"
D:\sdk\sdk\platform-tools>adb shell su -c "mount -o remount,ro ext4 /system"
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-
8.1.4.bin
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.026s]
writing 'bootloader'...
OKAY [ 0.045s]
finished. total time: 0.075s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.3.0
.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.455s]
writing 'boot'...
OKAY [ 0.567s]
finished. total time: 1.030s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 flash recovery kfhd8-twrp-2.4.4.0-r
ecovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.454s]
writing 'recovery'...
OKAY [ 0.567s]
finished. total time: 1.029s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.004s
D:\sdk\sdk\platform-tools>

FIXED
soupmagnet,
Finally had time to install ubuntu 12.10 on my laptop. I used soupkit for KFHD89 and root-plus from the same posting you had. This worked like a charm. rootplus' version of the play store actually worked compared to other versions I had installed, same for youtube and a few other google apps.
I will toy with TWRP tomorrow. Just glad I got normal google apps installed now.

[Q] Cyanogenmod on Samsung Note 2 (i605)

I'm running in to the following error when attempting to flash my Samsun Note 2 (i605). Can anyone provide some help on getting past this issue?
I've used adb to reboot the device into download and attempted to run the below.
Here is the resources I'm using
Instructions I'm using are here: Wiki CyanogenMod on Samsung Galaxy Note 2 LTE (Verizon) ("i605")
Using Heimdall Suite v1.4.0
Recovery: recovery-clockwork-6.0.4.3-i605.img
On MAC: OSx 10.9.5
Here is the output
#sudo heimdall flash --RECOVERY recovery-clockwork-6.0.4.3-i605.img --no-reboot --verbose
Heimdall v1.4.0
Copyright © 2010-2013, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VIDID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
0%
14%
28%
42%
56%
70%
84%
98%
100%
ERROR: Failed to unpack received packet.
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!
Releasing device interface...

I'm not a big fan of clockworkmod recovery...
Install twrp http://teamw.in/project/twrp2/133

FUSIONdev said:
I'm not a big fan of clockworkmod recovery...
Install twrp teamw.in/project/ twrp2/133
Click to expand...
Click to collapse
Can you clarify one thing. I"m guessing the instructions on that page may be out of date? When I go there from my Samsung Galaxy Note 2 (verizion i605), it doesn't download goo manager. It brings up TWRP Manager (ROOT) by Jmz Software. Is this correct?

jjones312 said:
Can you clarify one thing. I"m guessing the instructions on that page may be out of date? When I go there from my Samsung Galaxy Note 2 (verizion i605), it doesn't download goo manager. It brings up TWRP Manager (ROOT) by Jmz Software. Is this correct?
Click to expand...
Click to collapse
You have to install this! https://play.google.com/store/apps/details?id=com.s0up.goomanager

FUSIONdev said:
You have to install this! (this link your posted goes here.. noobs can't post URLs yet./QUOTE]
I'd love to but that link returns "We're sorry, the requested URL was not found on this server.", when browsing to that URL on phone or laptop.
Do you have an alternate download? and if so, can I install using ADP?
I was able to download "openrecovery-twrp-2.3.1.1-t0ltevzw.img" from the direct download link.
Click to expand...
Click to collapse

jjones312 said:
FUSIONdev said:
You have to install this! (this link your posted goes here.. noobs can't post URLs yet./QUOTE]
I'd love to but that link returns "We're sorry, the requested URL was not found on this server.", when browsing to that URL on phone or laptop.
Do you have an alternate download? and if so, can I install using ADP?
I was able to download "openrecovery-twrp-2.3.1.1-t0ltevzw.img" from the direct download link.
Click to expand...
Click to collapse
Just search "GooManager" on play store... by Snipanet Apps
Click to expand...
Click to collapse

FUSIONdev said:
jjones312 said:
Just search "GooManager" on play store... by Snipanet Apps
Click to expand...
Click to collapse
Thanks.. But unfortunately when searching for "GooManager" it doesn't return anything w/ that name or by that company/dev. Searching for Snipanet Apps returns nothing.
Searching "GooManager" returns the following list in order (first 10)
TWRP Manager (ROOT) by Jmz Software
ROM Manager by ClockworkMOd
Flashify (for root users) by Christian Gollner
ROM Installer by JRummy Apps
Superuser by ClockworkMod
Recovery Manaer by joeykrim
[ROOT]Rashr - Flash Tool by DsLneXus
Goodev Download Manager by goodev
Gapps Manager by Weidi Zhang
Click to expand...
Click to collapse

jjones312 said:
... cut ...
Click to expand...
Click to collapse
Ok... so you have two alternatives.
-If do you have a windows pc, flash with ODIN this https://goo.im/devs/OpenRecovery/t0ltevzw/openrecovery-twrp-2.7.2.1-t0ltevzw.img.tar
(flash using the "AP" button and selection on Odin v3.09 or newer version)
-If you prefere or use Linux, you can use the DD method described on the page I linked on my first reply (http://teamw.in/project/twrp2/133)
EDIT:
OK I'm an Idiot xD you are a mac user... so with heimdal flash this: https://goo.im/devs/OpenRecovery/t0ltevzw/openrecovery-twrp-2.7.2.1-t0ltevzw.img
I suggest you to flash 2.7.2.1 version (as I linked to you) because it's stable and I had some issues with 2.8.0 version... fixed on 2.8.1, but it's not available for your device...

FUSIONdev said:
Ok... so you have two alternatives.
-If do you have a windows pc, flash with ODIN this site removed
(flash using the "AP" button and selection on Odin v3.09 or newer version)
-If you prefere or use Linux, you can use the DD method described on the page I linked on my first reply site removed)
EDIT:
OK I'm an Idiot xD you are a mac user... so with heimdal flash this: site removed
I suggest you to flash 2.7.2.1 version (as I linked to you) because it's stable and I had some issues with 2.8.0 version... fixed on 2.8.1, but it's not available for your device...
Click to expand...
Click to collapse
Thanks for the info and links..
So... The fun begins
I have Heimdall version 1.4.0 installed along with ADP. Here is the steps I did to attempt to flash TWRP.
1. Rebooted MAC
2. Connected Phone
3. ran ./ADP reboot download
4. ran heimdall detect (found device)
5. based on some issues I noted at Cyanogendmod with heimdall and Samsung drivers did the follow to unload drivers
sudo kextunload -b com.devguru.driver.SamsungComposite
sudo kextunload -b com.devguru.driver.SamsungACMData
sudo kextunload -b com.devguru.driver.SamsungACMControl
6. sudo heimdall flash --RECOVERY openrecovery-twrp-2.7.2.1-t0ltevzw.img --no-reboot
Here is the output from the screen:
sudo heimdall flash --RECOVERY openrecovery-twrp-2.7.2.1-t0ltevzw.img --no-reboot
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
site removed
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
site removed
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
air:Mac Jesse$

Did you try just the DD method ?
adb push openrecovery-twrp-2.7.2.1-t0ltevzw.img /sdcard
adb shell dd if=/sdcard/openrecovery-twrp-2.7.2.1-t0ltevzw.img of=/dev/block/mmcblk0p9

FUSIONdev said:
Did you try just the DD method ?
adb push openrecovery-twrp-2.7.2.1-t0ltevzw.img /sdcard
adb shell dd if=/sdcard/openrecovery-twrp-2.7.2.1-t0ltevzw.img of=/dev/block/mmcblk0p9
Click to expand...
Click to collapse
Here is what happens running that from download mode
jesses-air:Mac Jesse$ heimdall detect
Device detected
jesses-air:Mac Jesse$ sudo ./adb push openrecovery-twrp-2.7.2.1-t0ltevzw.img /sdcard
error: device not found
jesses-air:Mac Jesse$
Also tried to ./adb kill-server and ./adb start-server

You have to make these steps with phone in normal mode, not download mode...

FUSIONdev said:
Did you try just the DD method ?
adb push openrecovery-twrp-2.7.2.1-t0ltevzw.img /sdcard
adb shell dd if=/sdcard/openrecovery-twrp-2.7.2.1-t0ltevzw.img of=/dev/block/mmcblk0p9
Click to expand...
Click to collapse
By the way thanks for the help so far..
I'm not rooted so getting
/dev/block/mmcblk0p9: cannot open for write: Permission denied
gotta root first correct?
sorry if silly questions.. First time
Android v 4.4.2
i605VRUFND7
Kernel v 3.0.31

jjones312 said:
By the way thanks for the help so far..
I'm not rooted so getting
/dev/block/mmcblk0p9: cannot open for write: Permission denied
gotta root first correct?
sorry if silly questions.. First time
Android v 4.4.2
i605VRUFND7
Kernel v 3.0.31
Click to expand...
Click to collapse
You can try to root easily using https://towelroot.com/
(ps check that you enabled USB Debugging on developer settings)

I tried Towel Root. it said my device was not supported. I'm going to try to get a Windows PC today..
USB debugging is on

FUSIONdev said:
Ok... so you have two alternatives.
-If do you have a windows pc, flash with ODIN this (site link removed for allow noob topost)
(flash using the "AP" button and selection on Odin v3.09 or newer version).
Click to expand...
Click to collapse
Do you have a link to Odin.exe? Initially I tried just google searching and downloaded an Odin.exe that installed malware etc etc.. (i'm cleaning that PC now). From what I understanding Odin is a stand-alone app that doesn't install, just runs.
thanks!
ps: I have an Windows PC to attempt from

jjones312 said:
Do you have a link to Odin.exe? Initially I tried just google searching and downloaded an Odin.exe that installed malware etc etc.. (i'm cleaning that PC now). From what I understanding Odin is a stand-alone app that doesn't install, just runs.
thanks!
ps: I have an Windows PC to attempt from
Click to expand...
Click to collapse
I think I found it by searching here in the forum.
http://forum.xda-developers.com/galaxy-s3/themes-apps/27-08-2013-odin-3-09-odin-1-85-versions-t2189539

That link doesn't appear to have download links to Odin 3.09 anymore? Know where it can be found?

jjones312 said:
That link doesn't appear to have download links to Odin 3.09 anymore? Know where it can be found?
Click to expand...
Click to collapse
You have no luck with this root xD
I uploaded it for you: https://www.dropbox.com/s/up732djqp0ysmhv/Odin_v3.09.zip?dl=0
Maybe you will need to install drivers before: http://d-h.st/a7H
Remember to reboot the phone...
Odin must show the COM port with blu background... then you can flash the package (remember to select it on AP)
{
"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"
}

FUSIONdev said:
You have no luck with this root xD
I uploaded it for you: https://www.dropbox.com/s/up732djqp0ysmhv/Odin_v3.09.zip?dl=0
Maybe you will need to install drivers before: http://d-h.st/a7H
Remember to reboot the phone...
Odin must show the COM port with blu background... then you can flash the package (remember to select it on AP)
View attachment 2971173
Click to expand...
Click to collapse
Just tried and got the following. in the message windows:
<ID:0/003>Added!!
<ID:0/003>Odin v.3engine (IE:3)
<ID:0/003>File analysis...
<ID:0/003>SetupConnection..
<ID:0/003>Initialization..
<ID:0/003>Get PIT for mapping..
<ID:0/003>Firmware update start..
<ID:0/003>SingleDownload.
<ID:0/003>recovery.img
<ID:0/003>NAND Write Start!!
<ID:0/003>
<ID:0/003>Complete(Write) operation failed.
<OSM>All threads completed. (success 0 / failed 1)
Starting to research that error.

Using heimdall with a Mac

I need some help,
I am trying to install CM11 on my Galaxy Tab Pro. I have a macbook pro running yosemite and I cannot get heimdall to work. I followed the guide on the CM's wiki page and I get this error message: (See bold at bottom of screenshot)
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to send data!Releasing device interface...
after sending the command through to push a new recovery. On CM's wiki page it says that if you encounter the error message you have to enter in these commands to disable the default usb drivers:
"On Mac OS X you may see this message: "ERROR: Claiming interface failed!". If so, you need to disable the default USB drivers with the following commands:
sudo kextunload -b com.apple.driver.AppleUSBCDC;
sudo kextunload -b com.apple.driver.AppleUSBCDCACMControl;
sudo kextunload -b com.apple.driver.AppleUSBCDCACMData;-"
But when I enter these commands into Terminal it just comes up with this error message for all three of them:
(kernel) Kext com.apple.driver.AppleUSBCDCACMData not found for unload request.
Failed to unload com.apple.driver.AppleUSBCDCACMData - (libkern/kext) not found.
Does anyone have any insight as to why this isn't working for me. Would really like to get CM up and running on tabpro but with option currently not working and there being no other solution that works on mac's, Im kind of SOL right now. Any help would be greatly appreciated
-Thanks

Can't find answers to my specific issues

I tried to root my 8.9 kfhd 8.5.1 from a youtube video. I got stuck on the blue kindlefire screen. Through different guides I am able to get to twrp and fastboot. I have not been able to install a rom zip on the device through a cut and paste or a push command. I have left messages in a few threads and got a little response, but nothing that got me fixed. I've working on this for 2 weeks and read dozens of threads and cannot find a solution. I guess I had adb working at one time and had the drivers installed, but I'm not sure if ADB is working and my drivers are gone. I tried this thread "Frequently Asked Questions - 2nd Generation Kindle Fires " which directed me to this thread " [GUIDE] Kindle Fire For Beginners [GUIDE] Kindle Fire For Beginn… Post #2 " where I thought following this "How do I install the ADB drivers?" would be the way to go. So I followed it to here "[Root][TWRP][FFF][CWM]Kindle Fire Utility v0.9.6 (5/09/12) [First Gen Only] " and it warns me not to use it on my 8.9. So I looked some more and found this "Let's take some of the mystery out of getting ADB working in Windows ". I think I can get through these instructions correctly, but I now not sure if I this is the proper course of action considering I can get to fastboot and twrp. I've looked for a simpler solution to fix this. I even tried the push command to try and get liquid smooth rom and gapps onto the devices sdcard with no luck.
I am a total newbee and most of the lingo goes right over my head. The following is the original log of my first rooting attempt using this guide ......
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Home>cd desktop
C:\Users\Home\Desktop> cd kindlefire/stuff
C:\Users\Home\Desktop\kindlefire\stuff>adb push stack /data/local/tmp/
800 KB/s (4096 bytes in 0.005s)
C:\Users\Home\Desktop\kindlefire\stuff>adb shell
[email protected]:/ # su
su
/system/bin/sh: su: cannot execute - Permission denied
126|[email protected]:/ # dd if=/data/local/tmp/stack of=/dev/block/platform/omap/oma
p_hsmmc.1/by-name/system bs=6519488 seek=1
f=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1 <
0+1 records in
0+1 records out
4096 bytes transferred in 0.001 secs (4096000 bytes/sec)
[email protected]:/ # mount -o remount,rw ext4 /system
mount -o remount,rw ext4 /system
[email protected]:/ # mv /system/etc/install-recovery.sh /system/etc/install-recovery
.sh.bak
.sh /system/etc/install-recovery.sh.bak <
[email protected]:/ # mount -o remount,ro ext4 /system
mount -o remount,ro ext4 /system
[email protected]:/ # reboot bootloader
reboot bootloader
C:\Users\Home\Desktop\kindlefire\stuff>fastboot -i 0x1949 flash bootloader kfhd8
-u-boot-prod-8.1.4.bin
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.021s]
writing 'bootloader'...
OKAY [ 0.046s]
finished. total time: 0.069s
C:\Users\Home\Desktop\kindlefire\stuff>fastboot -i 0x1949 flash boot kfhd8-freed
om-boot-8.4.3.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.447s]
writing 'boot'...
OKAY [ 0.773s]
finished. total time: 1.225s
C:\Users\Home\Desktop\kindlefire\stuff>49 flash boot kfhd8-freedom-boot-8.4.3.im
g
'49' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Home\Desktop\kindlefire\stuff>fastboot -i 0x1949 flash recovery kfhd8-t
wrp-2.6.0.0-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.451s]
writing 'recovery'...
OKAY [ 0.754s]
finished. total time: 1.208s
C:\Users\Home\Desktop\kindlefire\stuff>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.001s
Today I tried a factory reset thinking I could push a rom and gapps on the sdcard, but of course that didn't work either.
I don't want to ask people to rehash the same questions over and over but being this far down the road I don't know if I can start the rooting process over or just what. Any help would be appreciated.
Wes

Did you flash the custom rom and gapps to your device?
post the link from which guide you follow the instructions to install a custom rom

This is the video guide I used..
https://www.youtube.com/watch?v=hUW6KARo8Y4
After this I was stuck at the blue kindlefire screen. I found can get to twrp and fastboot mode (twrp by rebooting and holding the up volume and into fastboot by entering "fastboot -i 0x1949 getvar product" in a command prompt). When in twrp my computer (win7) sees the kindle in "devices and printers" and also in device manager but the yellow exclamation mark shows that the drivers are not installed.

I reinstalled my drivers and in device manager I have listed...
"Android ADB Interface" as a sub listing under "android phone" (it doesn't list the kindle any longer)
I ran the RunMe.bat file and got the original root script. I have 5 choices...
1) normal
2) Special (....)
3) New xperia....
G) Goodle glass
x) Unroot
This is all the while I have my device connected to my computer with the usb cable.
My computer sees the device in "devices and printers" and in device manager but does not see it in windows explorer.
Now what?

I took pictures of my screen but I haven't figured out how to add images.

ironrod60 said:
I took pictures of my screen but I haven't figured out how to add images.
Click to expand...
Click to collapse
Help?? Anyone?? Mods?? I've done everything that was laid out in the newbee's section and have found nothing that fits the problem I am having with rooting my device. It said that if I did that people would be more than happy to help. I've been working on it since 14 Jan.

can't flash twrp (no error - just not installed)

hello,
im trying to flash my S4 Mini with lineage os - first step installing twrp fails.
i tried using heimdall to to flash twrp with the gui and via cli, but fail the same way: they report no error at all! finish the flashing and reboot. when i then try to go into recovery the standard recovery is still there! everything is jsut as stock as it was before.
here is the cli output:
Code:
sudo heimdall flash --RECOVERY twrp-3.2.3-0-serranoltexx.img --verbose
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
0%
11%
22%
33%
45%
56%
67%
79%
90%
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
note that: i tried 2 different versions of the latest twrp (one compiled by someone from xda), and i tried the gui too - adding the path to the save pit -> same result.
my problem seems similar to this post:
https://forum.xda-developers.com/galaxy-s4-mini/help/heimdall-reboot-to-custom-recovery-t3474163
but there was no response
also, ive read that sudo can be problem for heimdall, but without sudo it cant access the usb....
if anyone has any idea, please dont be shy to attempt to help, or point to other places where i could get help thank you!
about me: this is literally the first time im having an android device (im a sailfish user), so forgive me the possible beginners mistakes. also, my host pc is runing mint19.

misc11 said:
hello,.
Click to expand...
Click to collapse
Bro I think you are in stock.....
But which model? If i9192
Then root using https://forum.xda-developers.com/galaxy-s4-mini/general/root-root-s4-mini-i9192-2018-t3780235 and flash twrp.img using apps

HemanthJabalpuri said:
Bro I think you are in stock.....
But which model? If i9192
Then root using https://forum.xda-developers.com/galaxy-s4-mini/general/root-root-s4-mini-i9192-2018-t3780235 and flash twrp.img using apps
Click to expand...
Click to collapse
yes, the phone is still completely stock. not rooted, but apparently the bootloader comes unlocked with samsung phones...
the version is: GT-I9195. so, from your link, i understand that i HAVE to root it?

HemanthJabalpuri said:
Bro I think you are in stock.....
But which model? If i9192
Then root using https://forum.xda-developers.com/galaxy-s4-mini/general/root-root-s4-mini-i9192-2018-t3780235 and flash twrp.img using apps
Click to expand...
Click to collapse
thank you for your help! in fact, rooting the phone was the solution. installing twrp worked right away!

misc11 said:
thank you for your help! in fact, rooting the phone was the solution. installing twrp worked right away!
Click to expand...
Click to collapse
Thanks no worries
HemanthJabalpuri