Database Develop

[Q] reflash stock in fastboot

Hello,
I bricked my KFHD and it is in a reset loop right now. I got a factory cable and plan to try repairing it via fastboot. I need your kind assistance with the proper commands to flash the stock ROM and get out of fastboot if needed. I know that there are instructions for doing so in the original KF but I am not sure that it applies.
Thanks.

samio2 said:
Hello,
I bricked my KFHD and it is in a reset loop right now. I got a factory cable and plan to try repairing it via fastboot. I need your kind assistance with the proper commands to flash the stock ROM and get out of fastboot if needed. I know that there are instructions for doing so in the original KF but I am not sure that it applies.
Thanks.
Click to expand...
Click to collapse
Please describe the "reset loop" you are experiencing.

Well at boot it detects something wrong and it prompts me either to reset or reboot. Regardless of what I choose it always returns me to the same prompt. Meanwhile there is no usb connectivity what so ever. I tried the 20 second hold on the power button but nothing changed

samio2 said:
Well at boot it detects something wrong and it prompts me either to reset or reboot. Regardless of what I choose it always returns me to the same prompt. Meanwhile there is no usb connectivity what so ever. I tried the 20 second hold on the power button but nothing changed
Click to expand...
Click to collapse
When choosing "reset" does it look like its doing anything or does it just reboot?

Hello!
Ive got the same Q.
Messed up preinstalled keyboard, added some apk to /system/app folder. Now my kindle acts very bad....
Default settings in device section doesn't help. I tried to copy update....bin file to kindleupdate folder but it doesn't help, kindle won't flash (as i've already have last ver)
So, is there any way to flash KHD in fastboot mode, or using update.zip file? Mayby have someth like [UTILITY] Kindle Fire Unbrick Utility V1.1! ?
Thx a lot

It starts resetting and a progress bar shows and completes in a couple of seconds. Then it reboots back to the same prompt

I doubt factory reset would help. If my experience is any indication, factory reset will not undo any changes you did to /system. If you messed it up before resetting, you'll still be messed up after.

I think I messed up the /system and I want to try to reflash it

the good news is once you disconnect the cable the device exits fastboot also it shows up as android adb interface in device manager. but I could not get adb to see it. don't know why. I used the same PC that I used to root it and a mac but could not get adb to see it.

samio2 said:
I think I messed up the /system and I want to try to reflash it
Click to expand...
Click to collapse
What were you doing in /system before the problem started?

Was trying to install Google play. Not sure where i messed up

Do you still have adb access?

The device shows up in the device manager. But adb can't see them

samio2 said:
The device shows up in the device manager. But adb can't see them
Click to expand...
Click to collapse
What does your device manager say?

on windows it said android adb deive (or interface). as for the mac it is the same case and I used the usb probe and here is the output
Code:
High Speed device @ 2 (0x26200000): ............................................. Composite device: "Tate-PVT-08"
Port Information: 0x001f
Captive
Attached to Root Hub
Internal Device
Connected
Enabled
Device Descriptor
Descriptor Version Number: 0x0200
Device Class: 0 (Composite)
Device Subclass: 0
Device Protocol: 0
Device MaxPacketSize: 64
Device VendorID/ProductID: 0x1949/0x0007 (Lab126)
Device Version Number: 0x0100
Number of Configurations: 1
Manufacturer String: 5 "Texas Instruments"
Product String: 1 "Tate-PVT-08"
Serial Number String: 2 "XXX"
Configuration Descriptor: ....................................... "Android Fastboot"
Length (and contents): 32
Raw Descriptor (hex) 0000: 09 02 20 00 01 01 03 C0 32 09 04 00 00 02 FF 42
Raw Descriptor (hex) 0010: 03 04 07 05 81 02 00 02 00 07 05 01 02 00 02 00
Unknown Descriptor 0020:
Number of Interfaces: 1
Configuration Value: 1
Attributes: 0xC0 (self-powered)
MaxPower: 100 ma
Interface #0 - Vendor-specific .............................................. "Android Fastboot"
Alternate Setting 0
Number of Endpoints 2
Interface Class: 255 (Vendor-specific)
Interface Subclass; 66 (Vendor-specific)
Interface Protocol: 3
Endpoint 0x81 - Bulk Input
Address: 0x81 (IN)
Attributes: 0x02 (Bulk no synchronization data endpoint)
Max Packet Size: 512
Polling Interval: 0 ( Endpoint never NAKs)
Endpoint 0x01 - Bulk Output
Address: 0x01 (OUT)
Attributes: 0x02 (Bulk no synchronization data endpoint)
Max Packet Size: 512
Polling Interval: 0 ( Endpoint never NAKs)
Device Qualifier Descriptor
Descriptor Version Number: 0x0200
Device Class 255 (Vendor-specific)
Device Subclass 255 (Vendor-specific)
Device Protocol 255
Device MaxPacketSize: 64
Number of Configurations: 1
bReserved: 0
Configuration Descriptor Device gave an error kIOReturnSuccess (0x0) when asked for first 4 bytes of descriptor
Configuration Descriptor Device gave an error kIOReturnSuccess (0x0) when asked for first 9 bytes of descriptor

Well, that's helpful. It says you're in fastboot. Try using fastboot to change your bootmode to either recovery or normal mode and see if you can get a different result.

Shouldn't adb recognize it to work with faatboot or are they separate?
how do change the bootmode? How to change it back?
I tried fastboot reboot but all i got is waiting for device message.

samio2 said:
Shouldn't adb recognize it to work with faatboot or are they separate?
how do change the bootmode? How to change it back?
I tried fastboot reboot but all i got is waiting for device message.
Click to expand...
Click to collapse
ADB and fastboot are completely separate.
Try "fastboot devices"

fastboot devices shows nothing for me

That's likely an issue with your drivers. Try reinstalling them. Or better yet, try the SoupKit and save yourself some hassle.

Heimdall 1.4 RC1 Debian

Hello all,
I am trying to make working Heimdall 1.4RC1 in order to flash my N7000.
I have install the Heimdall-flash version in Sid repos but it don't work with this issue :
Code:
Heimdall v1.4 RC1
Copyright (c) 2010-2012, 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: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 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...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
ERROR: libusb error -7 whilst receiving packet.
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Session begun with device of type: 180.
Downloading device's PIT file...
PIT file download successful.
Ending session...
Releasing device interface...
Re-attaching kernel driver...
Can anyone help me to make it work ???

Try to use this http://yadi.sk/d/gAQzOkkh16jE6
How to, look into my signature...

Thanks for your response.
I have put a question on your thread : Heimdall_Flasher

Heimdall on Linux with Note 4

I am attempting to use Heimdall (with the S5 patch) with my Note 4 in Xubuntu 14.10, but I keep getting the following error:
Code:
Initialising protocol...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
In a clean install of Xubuntu 14.10 I did the following:
Code:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-uprade -y
sudo apt-get install android-tools-adb build-essential git libudev-dev pkg-config zlib1g-dev
sudo wget https://raw.githubusercontent.com/snowdream/51-android/master/51-android.rules -O /etc/udev/rules.d/51-android.rules
sudo chmod a+r /etc/udev/rules.d/51-android.rules
sudo service udev restart
mkdir ~/.source
cd ~/.source
wget 'http://sourceforge.net/projects/libusb/files/libusb-1.0/libusb-1.0.19/libusb-1.0.19.tar.bz2'
tar -vxjf libusb-1.0.19.tar.bz2
rm libusb-1.0.19.tar.bz2
cd libusb-1.0.19
./configure
make
sudo make install
cd ~/.source
git clone https://github.com/sshimko/Heimdall.git --branch gs5 --single-branch heimdall-gs5
cd heimdall-gs5/libpit
./configure
make
cd ../heimdall
./configure
make
sudo make install
sudo udevadm control --reload-rules
adb reboot download
heimdall print-pit --verbose
Here is the result of "heimdall print-pit --verbose":
Code:
Heimdall v1.4.1
Copyright (c) 2010-2014 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...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
Releasing device interface...
Re-attaching kernel driver...
Does anyone who has been able to use Heimdall with the Note 4 in Linux have any suggestions as to how I can get this setup correctly?
Thanks.

I had the same results with https://github.com/karabijavad/Heimdall/tree/issue-197 and https://github.com/Benjamin-Dobell/Heimdall/issues/232.

Did you ever figure this out? I'm getting the same "Failed to send request to end PIT file transfer!" error.

As far as i I know, there's only so much heimdall can do. I've only had success on windows for flashing the full firmware. I'm on Linux mint and I'm still not sure. You could try jodin on this site. It's a web based Odin.

Jodin uses Heimdall, so it doesn't fix the problem. On windows I couldn't get the stupid Samsung drivers to work.
Sent from my SM-N910T using XDA Free mobile app

DieHappy said:
I am attempting to use Heimdall (with the S5 patch) with my Note 4 in Xubuntu 14.10, but I keep getting the following error:
Code:
Initialising protocol...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
In a clean install of Xubuntu 14.10 I did the following:
Code:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-uprade -y
sudo apt-get install android-tools-adb build-essential git libudev-dev pkg-config zlib1g-dev
sudo wget https://raw.githubusercontent.com/snowdream/51-android/master/51-android.rules -O /etc/udev/rules.d/51-android.rules
sudo chmod a+r /etc/udev/rules.d/51-android.rules
sudo service udev restart
mkdir ~/.source
cd ~/.source
wget 'http://sourceforge.net/projects/libusb/files/libusb-1.0/libusb-1.0.19/libusb-1.0.19.tar.bz2'
tar -vxjf libusb-1.0.19.tar.bz2
rm libusb-1.0.19.tar.bz2
cd libusb-1.0.19
./configure
make
sudo make install
cd ~/.source
git clone https://github.com/sshimko/Heimdall.git --branch gs5 --single-branch heimdall-gs5
cd heimdall-gs5/libpit
./configure
make
cd ../heimdall
./configure
make
sudo make install
sudo udevadm control --reload-rules
adb reboot download
heimdall print-pit --verbose
Here is the result of "heimdall print-pit --verbose":
Code:
Heimdall v1.4.1
Copyright (c) 2010-2014 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...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
Releasing device interface...
Re-attaching kernel driver...
Does anyone who has been able to use Heimdall with the Note 4 in Linux have any suggestions as to how I can get this setup correctly?
Thanks.
Click to expand...
Click to collapse
Did you put it to work?
BR

I have not been able to get it to work with my Note 4.
Sent from my SM-N910T using XDA Free mobile app

I am currently running into the same problems as well
Nobody has a fix yet.

[Q&A] [PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.4.0 Now Avai

[Q&A] [PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.4.0 Now Avai
Q&A for [PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.4.0 Now Available)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.4.0 Now Available). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Flashing ROM from Mac OS X
Hi,
I tried to flash a ROM (recovery.img) using heimdall command line, I tried with the following command
Code:
sudo heimdall flash --recovery filename.img --no-reboot
The device in download mode got detected, then it says Initializing Protocal. after that I got "Error: failed to send data, releasing device interface"
Any solutions or help, regarding this.

jvigneshcs said:
Hi,
I tried to flash a ROM (recovery.img) using heimdall command line, I tried with the following command
Code:
sudo heimdall flash --recovery filename.img --no-reboot
The device in download mode got detected, then it says Initializing Protocal. after that I got "Error: failed to send data, releasing device interface"
Any solutions or help, regarding this.
Click to expand...
Click to collapse
You didn't mention the device details, i9000? Heimdall 1.4.0 worked with my newer Samsung devices, but there I had to type --RECOVERY instead of --recovery.
It hasn't worked for my i9000 (Ubuntu 12.04 32-bit)
For my old Samsung i9000 (S1) I had to uninstall Heimdall 1.4.0 and install Heimdall 1.3.1
Your typing style would perfectly fit there.
tetakpatalked from Nexus 7 flo

tetakpatak said:
You didn't mention the device details, i9000? Heimdall 1.4.0 worked with my newer Samsung devices, but there I had to type --RECOVERY instead of --recovery.
It hasn't worked for my i9000 (Ubuntu 12.04 32-bit)
For my old Samsung i9000 (S1) I had to uninstall Heimdall 1.4.0 and install Heimdall 1.3.1
Your typing style would perfectly fit there.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Thanks for you response. I tried with my Samsung Galaxy Grand Duos GT-I9082 with suitable recovery.img.
Later I installed using Odin from Windows machine.

Successfully tested on Samsung Galaxy S4 Active (GT-I9295)
The frontend sucks But after some research I understood the logic and managed to (re-)flash my phone with I9295XXUCNH2 . I didn't need to repartition and had a valid .pit file on the phone, so it is pretty straightforward:
Code:
sudo heimdall flash --APNHLOS NON-HLOS.bin --MDM modem.bin --SBL2 sbl2.mbn --SBL3 sbl3.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn --SYSTEM system.img.ext4 --CACHE cache.img.ext4 --BOOT boot.img --RECOVERY recovery.img --HIDDEN hidden.img.ext4

Cannot load PIT from S3 Neo
Hi,
I want to root my i9301. This requires odin... Since I am on linux, I tried Heimdall. But I fail already downloading the PIT file.
Looks like usb problems, any idea?
Code:
Heimdall v1.4.1
...
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...
Protocol initialisation successful.
Beginning session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Some devices may take up to 2 minutes to respond.
Please be patient!
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Session begun.
Downloading device's PIT file...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer.
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer.
ERROR: Failed to send end session packet!
Releasing device interface...
tried i8730 using same cable at motherboard usb port.
worked fine with "WARNING: Empty bulk transfer after sending packet failed. Continuing anyway..."
Ubuntu 16.04 Kernel 4.4.0-34-generic
thanks
Edit: solved, used odin on windows instead.

"No Sim Card" error after flashing

Hi, I've been trying to update my rom, and seem to have messed up the RADIO partition on my J700t.
I've tried flashing it back from stock via heimdall, and it fails
Code:
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RADIO
0%
ERROR: Failed to receive file part response!
ERROR: Retrying...
ERROR: Expected file part index: 0 Received: 1
ERROR: RADIO upload failed!
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
Restoring from TWRP backup doesn't seem to fix this problem. I was thinking about using dd to manually flash it from within recovery but I don't know what the correct partition to dd to would be, and that seems like something I should figure out before I break it harder.
Anyone have this problem before? Anyone know a fix, or have ideas? Thank you in advance.

I think that your best now is try to use the original rom using Odin

rgazapo said:
I think that your best now is try to use the original rom using Odin
Click to expand...
Click to collapse
Can't use Odin, no Windows, using Heimdall. Heimdall gives the above errors when trying to flash certain partitions

Okay fellas, I fixed it! Turns out it was an issue with Heimdall that was fixed in version 1.4.2 (I was using the version available in the repos, 1.4.1)
Had to compile from source to do that, and usually that leads to problems but in this case, it worked the first time, no problem, using only the information in the documentation.
Heimdall sure is some *terrific* software and I would like to thank Benjamin Dobell very much for his work on it. Not only does it work real good, but honestly I can't say I've ever seen any software compile correctly the first time I tried it, but Heimdall did. That's pretty impressive. Thank you, Benjamin, for your work on this.
See the following output if you're interested:
Code:
$ heimdall flash --RADIO modem.bin --verbose
Heimdall v1.4.2
Copyright (c) 2010-2017 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: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 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...
WARNING: Empty bulk transfer after receiving packet failed. Continuing anyway...
PIT file download successful.
Uploading RADIO
0%
3%
6%
9%
12%
15%
18%
21%
24%
28%
31%
34%
37%
40%
43%
46%
49%
52%
56%
59%
62%
65%
68%
71%
74%
77%
80%
84%
87%
90%
93%
96%
99%
100%
RADIO upload successful
Ending session...
Rebooting device...
Releasing device interface...

hmm - i’m using v1.4.2 w my J700T and I am getting the “ERROR: Failed to receive file part response!”
I’m going to hunt down a Windows machine so I can try Odin...

quick update: using Odin 3.14.1 on Win10 solved this issue for me.
how do we (and do we need to) nudge the dev that this issue is still outstanding in other configurations?