Hi guys
I bought an S4 i337M used but in really mint condition. The first thing I noticed is that USB Debugging isn't working good, sometimes it connects, sometimes the device says unathorized (but no message appeared on the phone), charging is working, also HDMI Out and connection in Download Mode, maybe I need a reflash of stock ROM? I'm in Linux and haven't such errors before (I had a S4 from Sprint two days and no problem)
Already rooted with towelroot method but I want to install CWM even if it voids my warranty (don't have much time left anyway) but when I try to install with Heimdall I get this error
Code:
ERROR: Failed to send file part packet!
In Odin, the process start but freezes (presumably is the same that happens with heimdall)
I have read a lot but can't find proper information, with the latest firmwares, can't we flash custom recovery using heimdall/odin? should I go for the Loki method? or safestrap? I don't know where to go from here, any advice is apreciated.
Thanks
The full output from Heimdall is
Code:
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...
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%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 file part packet!
ERROR: RECOVERY upload failed!
Ending session...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet.
ERROR: Failed to receive session end confirmation!
Releasing device interface...
Re-attaching kernel driver...
Thanks for taking the time to see this
For someone experiencing this: solved it by installing ROM Manager through Google Play, I installed non touch CWM first but then paid for touch version to help devs (in that step Knox Warranty Void is 0x0). I made a Nandroid and then installed CM 11 and it worked good. For my surprise Knox Warranty Void still shows 0x0 .
I'll share the steps I made in a new thread if that works for someone else with a i337m
Related
Here's the error log:
01:48:11, March 31, 2011
Line: 340
ERROR: Interface AP-OS: Error flashing subscriber unit. Device API Error: 0xE0020090 Address: 0x2000 Command: BIN
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
01:49:09, March 31, 2011
Line: 1190
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
01:49:09, March 31, 2011
Line: 597
ERROR: Flash failure: Interface AP-OS: Error flashing subscriber unit. Device API Error: 0xE0020090 Address: 0x2000 Command: BIN (Error Code: e0020090),
Detailed Error Details: Direction of the Error=3000, Command Value=300000, Code Group Number=2
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
This was after installing Gingerblur. Tried to flash back to stock ROM to get the OTA update but couldn't complete it. Please help, thanks!
http://forum.xda-developers.com/showthread.php?p=32877250#post32877250
Here is a part of log from RSD lite:
04/22/12 01:53:07 Multi upgrade started for 1 phones
04/22/12 01:53:07 [Device ID: 0] Flashing phone.
04/22/12 01:53:20 ERROR: Phone[0000]: Error sending TI ROM data packet request. Device API Error: 0xE003009F - on device ID 0.
04/22/12 01:53:20 ERROR: Flash failure: Phone[0000]: Error sending TI ROM data packet request. Device API Error: 0xE003009F (Error Code: e003009f),
Detailed Error Details: Direction of the Error=1000, Command Value=0, Code Group Number=No Codegroup - on device ID 0.
04/22/12 01:53:20 [Device ID: 0] Phone[0000]: Error sending TI ROM data packet request. Device API Error: 0xE003009F
04/22/12 01:53:20 ERROR: Failed flashing process. - on device ID 0.
04/22/12 01:53:20 Multi upgrade finished.
So, prior to my stupidity, I made a system.img dump via dd
However, after my stupidity (tried flashing some lib files....), I am now stuck with only stock recovery mode, or download mode.
How can I flash back my system.img? I tried in download mode with heimdall... but it fails with
Code:
[email protected]:/media/MediaTwo/MyRom# heimdall flash --verbose --no-reboot --SYSTEM system.img
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...
Attempt failed. Detaching driver...
Claiming interface again...
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
ERROR: Failed to receive handshake response. Retrying...
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 SYSTEM
0%
1%
ERROR: Failed to unpack received packet.
ERROR: Failed to confirm end of file transfer sequence!
ERROR: SYSTEM upload failed!
Ending session...
Releasing device interface...
Re-attaching kernel driver...
so I tried creating an update.zip that I could sideload flash in stock recovery, but that fails as well with
Code:
E: footer is wrong
E: signature verification failed
If I could get into adb shell, I'd be set... all I'd have to do is dd the system.img back (been there done that in SafeStrap), but when I try adb shell in stock recovery I just get "error: device not found", and in sideload mode, I get "error: closed"
Please help? :crying:
kevp75 said:
So, prior to my stupidity, I made a system.img dump via dd
However, after my stupidity (tried flashing some lib files....), I am now stuck with only stock recovery mode, or download mode.
How can I flash back my system.img? I tried in download mode with heimdall... but it fails with
Code:
[email protected]:/media/MediaTwo/MyRom# heimdall flash --verbose --no-reboot --SYSTEM system.img
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...
Attempt failed. Detaching driver...
Claiming interface again...
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
ERROR: Failed to receive handshake response. Retrying...
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 SYSTEM
0%
1%
ERROR: Failed to unpack received packet.
ERROR: Failed to confirm end of file transfer sequence!
ERROR: SYSTEM upload failed!
Ending session...
Releasing device interface...
Re-attaching kernel driver...
so I tried creating an update.zip that I could sideload flash in stock recovery, but that fails as well with
Code:
E: footer is wrong
E: signature verification failed
If I could get into adb shell, I'd be set... all I'd have to do is dd the system.img back (been there done that in SafeStrap), but when I try adb shell in stock recovery I just get "error: device not found", and in sideload mode, I get "error: closed"
Please help? :crying:
Click to expand...
Click to collapse
Can't use heimdall or stock recovery because it isn't a signed file and stock recovery doesn't allow adb shell. Your only option is to reflash unless you have Safestrap.
Sent from my SGH-I337 running GPE
DeadlySin9 said:
Can't use heimdall or stock recovery because it isn't a signed file and stock recovery doesn't allow adb shell. Your only option is to reflash unless you have Safestrap.
Sent from my SGH-I337 running GPE
Click to expand...
Click to collapse
I had SafeStrap, but not aymore... only stock recovery and download mode.
Is there a Odin/Heimdall flashable version of SafeStrap floating around somewhere that I have not seen?
kevp75 said:
I had SafeStrap, but not aymore... only stock recovery and download mode.
Is there a Odin/Heimdall flashable version of SafeStrap floating around somewhere that I have not seen?
Click to expand...
Click to collapse
Is it really my only option to go back, Odin flash NB1, upgrade to NC1, install SELinux Mode Changer and SafeStrap, then restore my system.img from within SafeStrap?
I have my data "files" backed up as an image (which I'll need to un-image, because it's too big for my Fat32 SDCard clocking in at 8.7G LOL), but I can adb push those back in as well...
I'm going to end up doing this, but I would like to keep this open in case another solution comes along....
kevp75 said:
Is it really my only option to go back, Odin flash NB1, upgrade to NC1, install SELinux Mode Changer and SafeStrap, then restore my system.img from within SafeStrap?
I have my data "files" backed up as an image (which I'll need to un-image, because it's too big for my Fat32 SDCard clocking in at 8.7G LOL), but I can adb push those back in as well...
I'm going to end up doing this, but I would like to keep this open in case another solution comes along....
Click to expand...
Click to collapse
unfortunately I had to odin back... but up and running
Rockin' it from my Smartly GoldenEye 35 NF1 (muchas gracias:* @iB4STiD @loganfarrell @muniz_ri @Venom0642 @ted77usa @rebel1699* @iB4STiD) ~ 20GB free cloud https://copy.com?r=vtiraF
Check me out online @ http://kevin.pirnie.us
Yes I know to reflash but having reflashed for 10+ times and being returned the similar errors, these errors are probably the USB hw problems, and not likely to be phones-sided. The root solution is to renew the USB tethers, even the Macs.
DeadlySin9 said:
Can't use heimdall or stock recovery because it isn't a signed file and stock recovery doesn't allow adb shell. Your only option is to reflash unless you have Safestrap.
Click to expand...
Click to collapse
Hi,
I've got a I9301I with build KOT49H.I9301IXXSAPG5
Cannot root it:
Kingroot crashes instantly with VerifyError exception
Heimdall cannot retrieve PIT from phone in download mode
Heimdall log:
Code:
$ heimdall print-pit --usb-log-level info --verbose
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...
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.
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.
ERROR: Failed to send end session packet!
Releasing device interface...
I was able to read the I8730 (already rooted) pit without problems using the same cable and usb port.
Any idea? did they close all backdoors so rooting isn't possible anymore?
thanks
It is a new firmware. We have to wait for us to be root or return to a previous firmware.
Install a custom recovey...
sahilkhan9557 said:
Install a custom recovey...
Click to expand...
Click to collapse
how, if neither rooting apps nor reading PIT from download mode work? could you provide a PIT file?
JPT223 said:
how, if neither rooting apps nor reading PIT from download mode work? could you provide a PIT file?
Click to expand...
Click to collapse
U just need to flash twrp.zip using odin
Was an unknown problem with heimdall. using odin on windows 7 it worked. thanks
JPT223 said:
Was an unknown problem with heimdall. using odin on windows 7 it worked. thanks
Click to expand...
Click to collapse
root plese help
I've been screwing around with this for three weeks and I'm unable to make ANY headway no matter how much I search.
I had rooted my s7 edge when I first got it 6 months ago and followed a guide on here which I'm unable to locate. My phone started acting super crazy and losing running apps and apps closing unexpectedly. For example while watching Netflix, the card with the netflix controls in the dropdown would disappear after only a few minutes and netflix would forget it was connected to a chromecast, among other things.
I performed a factory reset. Upon reset and reinstalling my apps I went to try a system update in Settings. Clicking on it immediately results in "Unfortunately Settings has Stopped" and crashing out to the home screen. I recall the root method had some sort of add-on you could flash that disabled/removed many bloatwares and certain "features" and things on the phone including system update.
As I can't find the instructions I used I decided to simply flash the latest firmware using Odin 3.10.7 and 3.11.1 and this method: https://forum.xda-developers.com/verizon-s7-edge/how-to/odin-stock-nougat-firmware-t3570156
Odin checks the files just fine. When the start button is pressed odin sits for 3minutes attempting to set up the connection, then fails out with a red FAIL.
Attempting to install TWRP using heimdall on windows results in:
Code:
C:\Users\pl\Desktop\Heimdall Suite>heimdall flash --RECOVERY twrp-3.1.1-0-hero2lte.img --no-reboot --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: "MSM8996"
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%
...
100%
RECOVERY upload successful
Ending session...
ERROR: Failed to unpack received packet.
ERROR: Failed to receive session end confirmation!
Releasing device interface...
A similar attempt on linux using Heimdall 1.4.1 results in dozens of warnings throughout
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway..."
On the phone itself the little progress bar starts moving across the screen, but immediately stops and a red error appears
SECURE CHECK FAIL : recovery
The full text of the information on the screen is as follows
Code:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G935V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE
AP SWREV: B2(2, 1, 1, 1, 1) K1 S1
SECURE DOWNLOAD : ENABLE
I have attempted to perform this on 3 separate machines, one each of windows, mac and linux, using all sorts of various versions of odin, and heimdall and I've been unable to get anything working. Any help is appreciated.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
might seem like a stupid question but do you have the proper drivers installed and are you using the factory cable? You can also try a different Odin I know some people have luck with different ones.
I cant provide much input other than unplug replug see if your computer will recognize the phone as being attached...or try a different odin.
We can't install twrp on the s7 with the snapdragon processor. The bootloaders are locked tight.
Correct, the moment I read TWRP, I had a moment of silence for the OP's phone.
TWRP is a no go due to locked bootloader. The reason system update crashes is because the apps needed for the updater are removed during the root fix process. You can flash back to stock with Odin. Marshmallow and Nougat can both be rooted, so take your pick. As for Netflix, I have issues with it forgetting that it's connected to my Chromecast all the time. I'm currently on a non-rooted ROM, but I've had this issue when the phone was stock or rooted.
tacticalone said:
Code:
C:\Users\pl\Desktop\Heimdall Suite>heimdall flash --RECOVERY wrp-3.1.1-0-hero2lte.img t --no-reboot --verbose
Click to expand...
Click to collapse
Bit of a dredge, I realise, as I've just dug out an old 310F as a spare handset and had a similar problem
I fixed it by renaming the recovery image as recovery.img (as opposed to wrp-3.1.1-0-hero2lte.img, for example)
Code:
heimdall flash --RECOVERY recovery.img t --no-reboot --verbose