I flashed a rom last night, but it froze before it was complete. The problem is I flashed a firmware zip that included stock recovery. I'm now stuck in download mode or stock recovery. I have backups that I can restore, but I'm unable to get heimdall to restore twrp recovery.
The phone is detected. I found a Pit file KLTE_USA_VZW.Pit I did not check the repartition check box.
The error I receive is:
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!
l used to have a Chromebook and chroot to Linux it was awesome I miss those days but back to your topic
I've never used heimdall but these are what I would tell you
First try to flash using Odin on windows PC on a friends computer
Next try wine on linux and Odin and try to flash
If no go then try
virtual box and put windows iso file on it
I think you can still do trial where you get thirty days before you have to activate
then download Samsung drivers from Samsung's website
then Odin and it may allow you to flash
If none of these work download Verizon upgrade/repair assistant for Samsung devices I think it is only is available for windows PC
Related
So, I have here a great old Note 4.
It has the generic mmc errors that cause it issues when booting and sleeping so I decided to give it a new rom. I bumped it into developer options, enabled usb debugging and fastboot and turned it off. I opened up odin, found the right twrp file to flash as well as a stock rom. I loaded it up and fired. The issue then was that the PIT partition had issues. Pit partition failed on odin's side, and flash read failure as well as a pit error of some sort on the phone's side. So I did my homework. I then tried to flash a new .pit file, I made sure the boxes were filled out correctly, had the right pit file as well as a correct stock rom, and the right drivers. It failed again with exactly the same errors. I don't know how you can manage saying that you can't flash the file your trying to fix but whatever. So I did more research and continued to change the usb cable to the original one that came with the phone, change the usb port, change versions of odin, use administrator privileges, find another .pit file, and change the pc. None of these worked, they all gave the same errors no matter what I did. So I moved on to see what else I could do, there was only one more issue though, the phone wouldn't boot up to an OS, if I tried to boot up normally it would boot into recovery, and if I booted into recovery it would boot into download mode with a message saying that the mme error caused it to. SO I couldn't do anything like flashfire or rom manager nor could I do something like root the device! So I did more homework, I turned to adb, because I saw something about an alternative to odin. Unfortunately, the phone has to boot up so you can connect it properly before you boot into download mode. So I did more homework and can't get anywhere, I am completely lost as to what to do because I can't flash odin or adb and sd card can only flash .zip files. I have no idea where to find a .zip for cwm or twrp that will work for my phone and the 2 files that I thought would work only gave me errors. I definitely am drowning in error messages and hope someone who knows what in the world is going on can help me get out of this mess.
Sincerely,
TiffPiff
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!
I don't know how to leave well enough alone, and I've been working on the Onn 8" Pro (100003561) tablet trying to at least get root. I managed to unlock the bootloader, but was unable to use SP Flash Tool to dump my own boot.img, so I picked up one I found online that I'm pretty sure is from an older firmware version (https://forum.xda-developers.com/t/stock-stock-backups-images-otas.3998227/page-9#post-82619259) and now it keeps giving me errors, bluetooth crashing, etc, even after a factory restore from the recovery.
I CANNOT get SP Flash Tool to load the scatter file that deadman was using in his comment (https://forum.xda-developers.com/t/stock-stock-backups-images-otas.3998227/page-9#post-82619259) it just gives me an invalid scatter file error. I just want it back to factory, start all over, but no matter what I do I can't figure out how to flash deadman's firmware file, or ANY firmware backup for that matter. I keep getting scatter file errors, and SP Flash doesn't even wanna find my device. I've got the drivers installed properly, it shows up as "MediaTek PreLoader USB VCOM (Android) (COM3)" in my device manager. I've tried changing the COM port, running the flash tool in compatibility mode for Windows 7 (I'm on Windows 11 btw) running it as admin, and nothing. I can get an empty scatter file from WWR 2.51 to load in flash tool, but when I plug my device in it just does nothing. If I unplug my device, it gives an error that says "BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)".
I can get into fastboot mode, but I can't open the settings in the normal boot because it instantly crashes to the ONN boot logo whenever I open anything. I'm at a complete loss here.
sethfoxen said:
I don't know how to leave well enough alone, and I've been working on the Onn 8" Pro (100003561) tablet trying to at least get root. I managed to unlock the bootloader, but was unable to use SP Flash Tool to dump my own boot.img, so I picked up one I found online that I'm pretty sure is from an older firmware version (https://forum.xda-developers.com/t/stock-stock-backups-images-otas.3998227/page-9#post-82619259) and now it keeps giving me errors, bluetooth crashing, etc, even after a factory restore from the recovery.
I CANNOT get SP Flash Tool to load the scatter file that deadman was using in his comment (https://forum.xda-developers.com/t/stock-stock-backups-images-otas.3998227/page-9#post-82619259) it just gives me an invalid scatter file error. I just want it back to factory, start all over, but no matter what I do I can't figure out how to flash deadman's firmware file, or ANY firmware backup for that matter. I keep getting scatter file errors, and SP Flash doesn't even wanna find my device. I've got the drivers installed properly, it shows up as "MediaTek PreLoader USB VCOM (Android) (COM3)" in my device manager. I've tried changing the COM port, running the flash tool in compatibility mode for Windows 7 (I'm on Windows 11 btw) running it as admin, and nothing. I can get an empty scatter file from WWR 2.51 to load in flash tool, but when I plug my device in it just does nothing. If I unplug my device, it gives an error that says "BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)".
I can get into fastboot mode, but I can't open the settings in the normal boot because it instantly crashes to the ONN boot logo whenever I open anything. I'm at a complete loss here.
Click to expand...
Click to collapse
Ugh, I feel so stupid. I FINALLY got SP Flash to recognise my device, by FOLLOWING THE DIRECTIONS :eyeroll:
So yes, you DO have to tear the back off of the tablet, and unhook the battery before you can do anything.
Hello every one. Total noob here. But this is to answer a question I had earlier but found no help with at least upon a basic google search. Earlier I bricked my Tab S6 Lite while trying to install TWRP to replace the current recovery. Hind sight being 20/20 I know now that TWRP is no long active and that is was simply a bad idea. I ended up stuck in odin boot loop with the error message of..
Odin Mode (DT Load Fail)
[DTH] dt table header check Fail: <unknown error>
Load_kernal: Could not do normal boot. (DT LOAD FAILURE)
vbmeta: Error verifying vbmeta image: OK_NOT_SIGNED (3)
CUSTOM VBMETA
VBMETA : No sign info
This put me in a bad spot as ADB, and Fastboot were no longer an option and I could not pull a viable pit from Tab using Heimdall, and Odin will not allow you to flash the recovery that can be found in Lineage downloads page as they are img files.
The solution I found was to use a program to change the recovery.img file found in the Nightly lineage zip folder into to a tar file using the program. And then flash that tar file using odin. This brought me back to standard liniage with no data loss.
Disclaimer: The file attached is not my own, download and use at your own risk.
I do not recommend you mess with software if you're not ready to brick and fix your own device.
Thanks