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.
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
I've scoured the internet for hours trying to figure what I'm doing wrong with no luck.
I've recently flashed my N910T with _mone's developer build of lineageos. But it's not doing well with the old modem that I was using when i was back on CM12. So I've attempted to flash the modem using heimdall. I've tried both the EPK2 and EPG2 modems. Both times, heimdall throws an error back at me that says this:
ERROR: Failed to confirm end of file transfer sequence!
I've tried a couple different heimdall git repos (Benjamin Dobell's and a couple forks) just in case someone had fixed a bug in heimdall.
But is there something I've got wrong? Any idea why this is happening. I'm at a total loss. Any help would be hugely appreciated. My
Code:
> sudo ~/gitClones/karabijavadHeimdall/Heimdall/heimdall/heimdall flash --MODEM modem.bin --APNHLOS NON-HLOS.bin
Heimdall v1.4.1
Copyright (c) 2010-2014 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...
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 data received, read 'empty' packet...
PIT file data receive completed, send kRequestEndTransfer...
PIT file download successful.
Uploading MODEM
100%
MODEM upload successful
Uploading APNHLOS
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: APNHLOS upload failed!
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
I have flashed TWRP 3.0.2 with heimdall to my SM-P600. According to the output everything went out fine:
Code:
$ heimdall flash --no-reboot --RECOVERY twrp-3.0.2-0-lt03wifiue.img
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
[Link removed to comply with xdadevelopers policy]
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:
[Link removed to comply with xdadevelopers policy]
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%
RECOVERY upload successful
Ending session...
Releasing device interface...
However, when afterwards I boot the tablet in recovery mode I get the following error message:
Could not do normal boot. Invalid KERNEL LENGTH!
Click to expand...
Click to collapse
What could be the cause of this error? Thank you.
I'm following these instructions: https://wiki.lineageos.org/devices/starlte/install
But the first step fails: From within the Developer options menu, enable OEM unlock.
I don't have this option. Ok, doing this: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
Fine, OEM unlock appears in the menu. But I have to erase everything after enabling it - done. Now I have a completely new installed android 10. Yippie, I can start an endless loop
I try to continue without OEM unlock.
1. Installing a custom recovery using heimdall
Code:
heimdall flash --RECOVERY lineage-17.1-20200501-recovery-starlte.img --no-reboot
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...
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%
RECOVERY upload successful
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
On the phone it's written Only official released binaries are allowed to be flashed(RECOVERY) in red letters.
2. Installing LineageOS from recovery
Code:
adb sideload lineage-17.1-20200501-nightly-starlte-signed.zip
Total xfer: 1.00x
Errors on the phone:
Code:
...
E: failed to verify whole-file signature
Update package verification took 47.2 s (result 1).
E: Signature verification failed
E: error: 21
Install from ADB completed with status 2.
Installation aborted.#1
Solved: The second try was successful.
Hi hukd, I understand that this is kind of necromancy, but do you have any idea what you did the second time? Was it perhaps 7 days after you launched into development mode? I'm having this issue, and am wondering if being in prenormal state is an issue, even after unlocking OEM.
Hey waveBidder, I would really like to help you, but I have absolutely no glue why it has worked the second time. If I did something different, it was accidental.