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
Related
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
Has anyone gotten the L update? I won't get any updates as I'm on prepaid service, but was wondering if it's even available to us or did AT&T just say screw you?
pre4speed said:
Has anyone gotten the L update? I won't get any updates as I'm on prepaid service, but was wondering if it's even available to us or did AT&T just say screw you?
Click to expand...
Click to collapse
It's not available yet. None of the AT&T branded models have gotten an official update yet, not even the 10.1
thisisapoorusernamechoice said:
It's not available yet. None of the AT&T branded models have gotten an official update yet, not even the 10.1
Click to expand...
Click to collapse
Thanks so that's a big SCREW YOU from AT&T. Too busy buying Directv which also sucks.
My AT&T T337A has lollipop. It was OTA upgraded but I have an update.zip you can flash. Now ... can anyone help debrick my device since I went and mucked it up trying to get Viper on it?
uudruid74 said:
My AT&T T337A has lollipop. It was OTA upgraded but I have an update.zip you can flash. Now ... can anyone help debrick my device since I went and mucked it up trying to get Viper on it?
Click to expand...
Click to collapse
Code:
[email protected]:/t-src/Heimdall/bin# ./heimdall download-pit --output pit
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...
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.
Ending session...
Rebooting device...
Releasing device interface...
dude pm, i haven't tested write yet but if pit spits correct then write should do, thanks @sub77 :good:
Code:
[email protected]:/t-src/Heimdall/bin# file pit
pit: Partition Information Table for Samsung smartphone, 30 entries;
#1 APNHLOS (0x1) "NON-HLOS.bin";
#2 MODEM (0x2) "modem.bin";
#3 SBL1 (0x3) "sbl1.mbn";
#4 DBI (0x4) "sdi.mbn";
#5 DDR (0x5);
#6 ABOOT (0x6) "aboot.mbn";
#7 RPM (0x7) "rpm.mbn";
#8 TZ (0x8) "tz.mbn";
#9 PAD (0x9);
#10 PARAM (0xa);
#11 EFS (0xb) "efs.img.ext4";
#12 MODEMST1 (0xc) "nvrebuild1.bin";
#13 MODEMST2 (0xd) "nvrebuild2.bin";
#14 BOOT (0xe) "boot.img";
#15 RECOVERY (0xf) "recovery.img";
#16 FOTA (0x10); #17 BACKUP (0x11);
#18 FSG (0x12)
[email protected]:/t-src/Heimdall/bin#
seems a bit short, but let me try a write of aboot and see what happens, if it goes good i'll uplload a zip of the heimdall build i'm using and the program sub77 pointed me too.
DAMMIT !!!
Code:
[email protected]:/t-src/Heimdall/bin# ./heimdall flash --ABOOT aboot-6
....
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.
WARNING: Setting protocol to 1
Downloading device's PIT file...
PIT file download successful.
Uploading ABOOT
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: ABOOT upload failed!
Ending session...
Rebooting device...
i didn't brick but the write still breaks... grumble
okay when ./heimdall print-pit, this looks odd
Code:
...
...
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 139904
Partition Block Count: 4096
[COLOR="Red"]File Offset (Obsolete): 0
File Size (Obsolete): 0[/COLOR]
Partition Name: ABOOT
Flash Filename: aboot.mbn
FOTA Filename:
...
...
Okay, I'm being stoppped by Qualcomm secure boot Secure check aboot
..dang flabbit.
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
Yesterday, I was running some apps (WeChat, Photo, etc) on my phone, but then my phone starts to lag, and suddenly restart by itself, and the following error appears after small NOKIA logo:
"ERROR: Unable to find a bootable option. Press any key to shutdown"
I've tried all possible solution I've found, which is:
1) Hard reset key combo: hold "volume down" until exclamation mark shown. (no exclamation mark shown for me)
2) Windows Device Recovery Tool
- it shown model phone is "Lumia phone" and Firmware version is unknown.
- When press install, it shown error once it starting to flash FFU, and show "Operation ended with failure. Software installation failed. Please try restarting your device, and try software installation again..."
3) Nokia Care Suite
- same as WDRT, when boot to flash mode, it shown error when the program try to flash FFU.
- FFU downloaded by WDRT, it shown error that said FFU is invalid
- FFU downloaded from http://lumiafirmware.com/ error message
Code:
DEV_REPORTED_ERROR_DURING_PROGRAMMING: 0x00030003
Exception:
Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.MurzimProgrammingException: DEV_REPORTED_ERROR_DURING_PROGRAMMING: 0x00030003
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__c(Object state)
4) "Unbrick Lumia without JTAG"
- THOR2 can't find connection on the following command
Code:
thor2 -mode emergency -hexfile HEX.hex -mbnfile msimage.mbn -orig_gpt
Error:
Code:
Debugging enabled for emergency
Initiating emergency download
Operation took about 11.00 seconds.
THOR2_ERROR_CONNECTION_NOT_FOUND
THOR2 1.8.2.18 exited with error code 84000 (0x14820)
- can't "flash" vpl to phone
Code:
thor2.exe -mode vpl -maxtransfersizekb 1 -vplfile C:\ProgramData\Nokia\Packages\Products\rm-915\XXX.vpl
Error
Code:
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2.exe -mode vpl -maxtransfersizekb 1 -vplfile C:\ProgramData\Microsoft\Packages\Products\RM-914\RM914_059S3J0_3058.50000.1425.0004_034.vpl
Process started Fri Sep 30 19:47:41 2016
Logging to file C:\Users\...\AppData\Local\Temp\thor2_win_20160930194741_ThreadId-4880.log
Parsing VPL file C:\ProgramData\Microsoft\Packages\Products\RM-914\RM914_059S3J0_3058.50000.1425.0004_034.vpl
Successfully parsed VPL
Flashing .ffu file RM914_3058.50000.1425.0004_RETAIL_apac_malaysia_307_04_441880_prd_signed.ffu (SW version 3058.50000.1425.0004)
Debugging enabled for uefiflash
Initiating FFU flash operation
WinUSB in use.
isDeviceInNcsdMode
isDeviceInNcsdMode is false
Device mode 6 Uefi mode
[THOR2_flash_state] Pre-programming operations
Disable timeouts
Get flashing parameters
Lumia Boot Manager detected
Check status of battery
State of charge 3, charging current 1
Warning: Battery level low. Charge battery to 10 % of max charge.
Protocol version 1.1 Implementation version 1.16
Detecting UEFI responder
HELLO success
Lumia Boot Manager detected
Check status of battery
State of charge 3, charging current 220
Warning: Battery level low. Charge battery to 10 % of max charge.
Protocol version 1.1 Implementation version 1.16
Booting to FlashApp
Reboot to FlashApp command sent successfully.
DetachFrom connection
Verifying that device is online
Device is online
Detecting UEFI responder
HELLO success
Lumia Flash detected
Protocol version 1.15 Implementation version 1.28
Disable timeouts
Get flashing parameters
Lumia Flash detected
Protocol version 1.15 Implementation version 1.28
Size of one transfer is 2363392
Size of buffer is 2359296
Number of eMMC sectors: 15269888
Platform ID of device: Nokia.MSM8227.P6036.1.2
Async protocol version: 01
Security info:
Platform secure boot disabled
Secure FFU disabled
JTAG eFuse blown
RDC not found
Authentication not done
UEFI secure boot enabled
SHK enabled
Device supports FFU protocols: 0019
[THOR2_flash_state] Device programming started
Using secure flash method
CoreProgrammer version 2015.06.10.001.
Start programming signed ffu file C:\ProgramData\Microsoft\Packages\Products\RM-914\RM914_3058.50000.1425.0004_RETAIL_apac_malaysia_307_04_441880_prd_signed.ffu
FfuReader version is 2015061501
Send FlashApp write parameter: 0x4d544f00
Perform handshake with UEFI...
Flash app: Protocol Version 1.15 Implementation Version 1.28
DevicePlatformInfo: Nokia.MSM8227.P6036.1.2
Unknown sub block detected. Skip...
Unknown sub block detected. Skip...
Supported protocol versions bitmap is 19
Secure FFU sync version 1 supported.
Secure FFU async version 1 supported.
Secure FFU async version 3 supported.
Get CID of the device...
Get EMMC size of the device...
Emmc size in sectors: 15269888
CID: Samsung, Size 7456 MB
Start charging...
Requested write param 0x43485247 is not supported by this flash app version.
Start charging... DONE. Status = 0
Unable to send ECHO REQ or ECHO REQ not supported
Get security Status...
Security Status:
Platform secure boot is disabled.
Secure eFUSE is disabled.
JTAG is disabled.
RDC is missing from the device.
Authentication is not done.
UEFI secure boot is enabled.
Secondary HW key exists.
Get ISSW Version...
Get ISSW Version, SKIPPED!
Get system memory size...
Size of system mem: 524288 KB
Read antitheft status...
Requested read param 0x41545250 is not supported by this flash app version.
Send backup to RAM req...
Clearing the backup GPT, startsector = 15269854
UEFI returned error: 4
Clear GPT has failed!
Operation took about 9.00 seconds.
Unknown error code.
THOR2 1.8.2.18 exited with error code 196611 (0x30003)
5) Try to flash FFU with WPInternal
- Doesn't work for flashing FFU (Error shown when trying to flash, Error 0x1106: Security header validation failed)
- Somehow flashing separate partitions (EFIESP, MainOS, Data) works, but I've flash old ROM that I've backup doesn't work
- able to boot to mass storage mode, able to read, able to backup (don't know about write)
Please help me, I've tried all of these above and my phone still bricked :crying:
Did you find the solution and unbrick your phone?
It sounds like the Flash memory in your phone is going bad or at least has some bad blocks. The error states that the phone reported an error while trying to flash over the image
i connect not one, 3-4 pieces to jtag riff box. the problem is emmc/nand memory, this chip have a bug, is not the only one have this problem.
the state of the memory chip is READ ONLY!, so you can't write this.
one box apear and change the state of the memory on other phones with same kind of problem. need to send some special command to emmc to change the state.
How to backup stockRom S5 before starting to follow any instructions to root + flash + LineageOS ...
What I want:
* backup my brand new stock ROM Galaxy S5 SM-G900F
* before I even start with TWRP, root, etc.
* with an apk, via USB on a PC ... any way that would work
* or if total backup does not exist, then at least the EFS partitions?
because:
* I might want to sell it later
* I might have to send it back
* flashing TWRP & LineageOS might fail
* I have lost mobileInternet on an LG-V20 already because something went strange when flashing
* I am careful
Is there any way to backup a Samsung S5 before I even start with following any instructions here?
Am I asking for something impossible?
Was I on the right way already (see below), but have done something wrong?
Is it perhaps only possible after rooting? If so, then which tool do you recommend then?
Thanks a lot!
What I have tried:
* xda developer galaxy-s5/general every thread title until page 5 https://forum.xda-developers.com/galaxy-s5/general/page5
* xda developer search for "S5 backup", "S5 EFS", and a few other searches. Sorry for being dumb, please help me search, thanks.
* Heimdall PIT, but "ERROR: Failed to send request to end PIT file transfer!"
* Odin PIT, but "Can't open the specified file. (Line: 1892)"
* Samsung Tool 5.0 com.sec.ricky310711.samsungtool.apk https://forum.xda-developers.com/showthread.php?t=2696153 but the app-->Backup-EFS hangs at "Please Wait..." <-- probably because I could not install busybox because no root yet.
* manual EFS backup with dd https://forum.xda-developers.com/showthread.php?t=2737448 but I get a "su: not found", obviously, because unrooted
Code:
Heimdall v1.4.0
...
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...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 0 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Can't open the specified file. (Line: 1892)
<OSM> All threads completed. (succeed 0 / failed 1)
Anyone?
ankade said:
Anyone?
Click to expand...
Click to collapse
Though, I don't have your specific variant, the typical "just in case" files (that I personally always begin with) to obtain are the following:
1) Stock Firmware File (I just go with the latest and sometimes the 1 previously released).
2) Latest Odin PC Software.
3) Latest Samsung USB Drivers for the PC.
4) PIT file (PIT = Partition Information Table).
Those are usually the bare essentials that I begin with.
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
Great, thanks a lot. That is a helpful list.
Ibuprophen said:
2) Latest Odin PC Software.
Click to expand...
Click to collapse
Which is the latest you are using? The version "Odin3-v3.13.1" does NOT work, see above.
How exactly do I extract the current state of my (still unrooted) SM-G900F ?
Thanks.
I have now tried again manually:
Code:
heimdall download-pit --output s5.pit
Is that the right command?
It only worked after overwriting the MSM8960 driver with zadig.exe
Then it looks like this:
Code:
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...
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...
then after a while:
Code:
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
heimdall 1.4.2
Hooray, big progress. It was a version problem, older versions of heimdall seem faulty. And grrrmpf: the "heimdall" website which comes up at the top on search engines ... provides an outdated 1.4.0 version. Which seems broken. But hooray, the 1.4.2 version of heimdall works:
this looks good, no?
Code:
cd heimdall_1.4.2_win64
heimdall print-pit --no-reboot
Code:
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.
Code:
Entry Count: 30
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21325
Unknown 4: 14413
Unknown 5: 14137
Unknown 6: 52
Unknown 7: 0
Unknown 8: 0
now there are 30 such entries:
Code:
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 30720
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: APNHLOS
Flash Filename: NON-HLOS.bin
FOTA Filename:
I got the new heimdall 1.4.2 version from here:
https://github.com/Benjamin-Dobell/Heimdall/issues/295#issuecomment-364729538
and because he only provides the source, the binary from here
https://github.com/tothphu/heimdall_build/
this worked too:
Code:
heimdall download-pit --no-reboot --output S5-download-pit.pit
It resulted in a non-human-readable binary file of 8192 bytes.
But:
How to backup partitions?
with
Code:
heimdall --help
I can see that there I can flash ONTO the device with e.g.
Code:
heimdall flash --RECOVERY twrp-x.x.x-x-klte.img --no-reboot
but there does not seem to be a
Code:
heimdall read --RECOVERY --file recovery.img --no-reboot
?
how to READ a partition FROM the device?
?
Now I have tried it via USB debugging, with "minimal_adb_fastboot_1.4.3_portable.zip"
but
Code:
adb shell
ls -al /dev/block/platform/msm_sdcc.1/by-name/efs
lrwxrwxrwx root root 2014-05-24 16:36 efs -> /dev/block/mmcblk0p12
dd if=/dev/block/mmcblk0p12 of=/storage/3164-3234/S5/efs.img
results in
Code:
dd: /dev/block/mmcblk0p12: Permission denied
and
Code:
su -
/system/bin/sh: su: not found
so it looks as if my first hope has to be declared dead ...
No system backup without root, right?
?
But what I don't understand ... How did people extract these here then: https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/ ???
I have found instructions how to get back to stock rom, but I would like to use my own original stockROM for that. But I don't know how to back it up. Please help. Thanks.
how to root?
The phone is this one:
Samsung S5
SM-G900F
Android version 6.0.1
Android security patch level: 1 January 2017
I have tried these root tools:
Kingroot (NewKingrootV5.3.7_C197_B451_xda_release_2018_06_19_20180620193529_242043.apk) --> "Generating adaptation strategy, please come back later"
Towelroot v1.0 (tr.apk) --> "This phone isn't currently supported"
I did not want to try CF-Auto-Root because it says "If you have a Samsung-KNOX-enabled device, this package will trip the KNOX warranty flag. This flag cannot be reset, and will prevent some applications from working."
Is there really no way to get root without first installing TWRP ?
?