So first off I have the SM-N900V (Samsung Galaxy Note 3 - Verizon) [hltevzw]
Currently following the instructions over on the CyanogenMod website, and have ran into a problem while trying to flash the PhilZ Touch Recovery. I have tried to flash with Odin-on almost every version-and have failed every time. So I took the path with Heimdall, and got the farthest. This was the process I took:
1) Power off device and boot into download mode (Volume down + Home + Power).
2) Plug in device and open command window in folder location (Where the recover.img is).
3) Run this command: heimdall flash --recovery recovery.img --no-reboot
4) This is the outcome:
Initializing connection...
Detecting device...
Claiming interface...
Setting up interface...
Initializing protocol...
Protocol initialization 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...
Click to expand...
Click to collapse
1) Does the phone need to be rooted?
2) Any reason why it is failing the send a request?
Any feedback would be much appreciated. Thanks!
Firstly, the Verizon model is bootloader locked and there is no unlock. You cannot use custom recoveries or kernels. Secondly, heimdall doesn't work if you're on 4.4 or higher for some reason.
Sent from my leanKernel 3.7 powered stock 4.4.2 (NF4) SM-N900T
Related
I just bought a brandnew i9505 today here in Germany
I tried to install CWM on the S4
sudo heimdall flash --recovery recovery-clockwork-6.0.3.3-jfltexx.img --no-reboot
This device 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...
Re-attaching kernel driver...
===========
The blue transfer bar appears and than i tried to restart the phone into CWM but it always loads into stock firmware
I tried it several times and i tried several times to immediately booting into CWM after flashing CWM with heimdall
any suggestions?
MasterBrush said:
I just bought a brandnew i9505 today here in Germany
I tried to install CWM on the S4
sudo heimdall flash --recovery recovery-clockwork-6.0.3.3-jfltexx.img --no-reboot
This device 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...
Re-attaching kernel driver...
===========
The blue transfer bar appears and than i tried to restart the phone into CWM but it always loads into stock firmware
I tried it several times and i tried several times to immediately booting into CWM after flashing CWM with heimdall
any suggestions?
Click to expand...
Click to collapse
Hi,
Do you havee the option in heimdall to NOT reboot?
Go into the ROM,then , power off and try to get into CWM.
When you power on,hold power +volume up button
When you see the blue writing,press and let go volume down button only.
Also , try a different CWM.
problem solved
When you see the Samsung logo, keep holding down Volume Up and Center Home buttons but let go of the Power button.
I did not know this...
Gurus,
I have Note 3 (N9005), running Lollipop (5.0).
While trying to install custom recovery (CyanogenMod), version 3.0.2, using Heimdall, I get the following error, and results in failure of installation of the custom recovery:
==============
heimdall flash --RECOVERY twrp-2.8.7.img --no-reboot
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.
Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
Releasing device interface...
=====================
Have tried ODIN as well, but with no luck so far.
Would request inputs on how I could move forward with successfully completing the installation of the recovery.
FYI, tried installing the recovery using Windows and Mac, but it yields the same result
Cheers!!
Just a quick add:
On my device, I see the following message in Red in the end:
SECURE CHECK FAILED : recovery
Many thanks in advance for any assistance
Probably the files you are using are wrong or corrupt .
Are you using the original Samsung USB cable to flash via Odin? Tried different USB cables and USB ports?
Thanks for all your recommendations friends.
I could finally manage to solve the problem as follows:
1. Disable Reactivation Lock
2. Root the device (CM root)
3. Installed TWRP
And now running Phronesis Rom v1.2 with Dark Lord Kernel 2.0.... and enjoying the 'New' Note-3
Thanks-n-Cheers!!
I have an SM-T280 that I've been trying to put LineageOS on, so I can use my MicroSD card as app storage. I downloaded TWRP Recovery, used Heimdall to transfer it over... DISASTER! Heimdall says:
Code:
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...
And on the screen of the tablet itself, "Custom Binary(Recovery) Blocked by FRP Lock". Now my phone is stuck in Odin Download Mode (won't turn on or off), I can't find the stock firmware because I don't have the CSC code, and worst of all, Heimdall won't even connect to the tablet anymore. It gives me this error:
Code:
Initialising protocol...
ERROR: Protocol initialisation failed!
Anyone got any ideas?
nickmatavka said:
I have an SM-T280 that I've been trying to put LineageOS on, so I can use my MicroSD card as app storage. I downloaded TWRP Recovery, used Heimdall to transfer it over... DISASTER! Heimdall says:
And on the screen of the tablet itself, "Custom Binary(Recovery) Blocked by FRP Lock". Now my phone is stuck in Odin Download Mode (won't turn on or off), I can't find the stock firmware because I don't have the CSC code, and worst of all, Heimdall won't even connect to the tablet anymore. It gives me this error:
Anyone got any ideas?
Click to expand...
Click to collapse
Just reboot to download mode (before you say you can't, I guarantee you can) then either just install the stock recovery or the whole firmware.
Boot to the OS and enable OEM_UNLOCK.
I suggest in future you read the installation instructions properly.
@OP
Whats the update? Did you manage to install LigeageOS?
I have the same device and want to install another OS for the same reason.
Did you have any luck installing another OS?
Today i wanted to update my phone from cynaogenmod to a recent lineageos. It followed this guide jfltexx/install, but when i tried to "heimdall flash --RECOVERY ...", the blue progress bar on the phone got to ~99% - then heimdall crashed:
Code:
...
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%libusb: error [udev_hotplug_event] ignoring udev action bind
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...
Because at that point nothing would change anymore, i unplugged the phone and rebooted. Since then the phone won't boot android anymore and reports "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." when booting to recovery mode. Download mode is still accessible, but worthless:
Flashing the original ROM fails with "Complete(Write) operation failed": imgur
Flashing it with a PIT i found on this forum doesn't work either: imgur
Is my phone completely lost? Is there something i can do?
aenderboy said:
Today i wanted to update my phone from cynaogenmod to a recent lineageos. It followed this guide jfltexx/install, but when i tried to "heimdall flash --RECOVERY ...", the blue progress bar on the phone got to ~99% - then heimdall crashed:
Code:
...
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%libusb: error [udev_hotplug_event] ignoring udev action bind
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...
Because at that point nothing would change anymore, i unplugged the phone and rebooted. Since then the phone won't boot android anymore and reports "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." when booting to recovery mode. Download mode is still accessible, but worthless:
Flashing the original ROM fails with "Complete(Write) operation failed": imgur
Flashing it with a PIT i found on this forum doesn't work either: imgur
Is my phone completely lost? Is there something i can do?
Click to expand...
Click to collapse
Hello,
Please follow my Guides. I recommend you to follow the guide "clean install from scratch" and also use Odin. Everything you need it's on my thread and in my collection.
Issue Resolved
The solution was to use a shorter USB cable. Thank you so much for making me not loose my faith!
Hi all,
I am trying to flash the LoS recovery (and later LoS itself) on my A7 2016 using heimdall on Debian Buster: I enabled the developers settings, activated ADB and "OEM Unlock", but when trying to flash the recovery using heimdall version 1.4.2 it gets stuck here:
[email protected]:/tmp/bla/Heimdall/build/bin# ./heimdall flash --RECOVERY ~mistersixt/Downloads/lineage-17.1-20210529-recovery-a7xelte.img
Heimdall v1.4.2
...
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%"
At this stage the device shows a (new) screen saying "Installation Failure" and "You need to unlock your device to install a custom OS" with some extra text.
Which step did I miss? Any help is welcome!
Kind regards, mistersixt.