Hi, I am actually trying to fix the lag issue by installing an updated firmware manually from sammobile.com. I know that in windows, the tool that should be used to flash the firmware is Odin, however I am using mac osx mavericks and I am using Odin's mac counterpart which is Heimdall. Heimdall detects my device, but whenever I try to do something either via the frontend or the terminal, I get an error "cannot initialise interface". I had Kies installed then so I uninstalled it and then I get the error message "sending data failed" or something like that. I have also removed Andorid file transfer. But still the same error.
I wanna know, is there anything that I haven't done? Or does Heimdall/Odin support SM-P600 at all?
Thanks in advance for the help!
Related
Rooted with ODIN. The phone worked fine for weeks and then I received this message trying to charge it one day. I get "FAIL! (auth), "FAIL! (Size)," or "FAIL! (Erase)" anytime I try to flash -- whatever I try to flash. I am using ODIN3 3.10.7.
Kies 3 does not recognized this device.
Smart Switch does not recognize this device.
ADB disabled
External Storage disabled.
Using a PIT file and T Flash, it starts to work, but ultimately fails.
Any ideas? What information should I provide?
Flashed a new image, but it won't load. Phone is stuck on the first screen.
Found one to flash through odin, but it won't load on reboot. Kies is attempting to reimage, but last try it also would no reboot. Fails to load image.
zerowrst said:
Rooted with ODIN. The phone worked fine for weeks and then I received this message trying to charge it one day. I get "FAIL! (auth), "FAIL! (Size)," or "FAIL! (Erase)" anytime I try to flash -- whatever I try to flash. I am using ODIN3 3.10.7.
Kies 3 does not recognized this device.
Smart Switch does not recognize this device.
ADB disabled
External Storage disabled.
Using a PIT file and T Flash, it starts to work, but ultimately fails.
Any ideas? What information should I provide?
Click to expand...
Click to collapse
Finally worked. Tried to flash tar from sammobile 10 times. Finally took.
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
Hey guys,
I tried to root my gf's S5 with CF-AutoRoot's package. I got this for the specific version which I double-checked
Included in the package was Odin and the image with an "installer".
Everything was fine, device detected in Odin, selected image in AP and let it rip... Except I got an error after it was in the process, under UDC start, can't remember exactly as I had restarted the device with the loading bar at like 30% of the way... it stated something dev_state
After I restarted, I got the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I would've thought it was going to be pretty straight forward and decided not to do a backup but I'm so getting killed if I'm going to lose the data!!!
Any insight? thanks
I tried to get Samsung Kies for the recovery but under the list of devices requiring emergency recovery it won't detect it...
I managed to retry the Odin flash with the same outcome.
The error message is unsupport dev_type if that makes any sense to someone
Well issue seems to have fixed itself by flashing latest TWRP... The Odin flash went smooth and phone booted normally...
must've been something off with the AutoRoot
Noob here: I need help with my Note 3 (SM-N900V).
I bought a used phone to replace a stolen one; it came with Android 4.0. A few years ago I successfully used Odin to flash TWRP 3.1.0.0 and the stock OF1 Android 5.0 rom, followed by a root with ArabicTool.
Phone works fine for everyday use, including root-requiring apps, but several apps are now requiring a more recent version of Android. Also, I can no longer boot into recovery mode; instead I get a message saying "System software not authorized by Verizon Wireless has been found on your phone".
I thus decided to try to flash the phone from scratch.
First I tried to use ADB and Fastboot to make sure the bootloader is unlocked. Unfortunately, while ADB worked fine, I was never able to get Fastboot to see the phone, despite following the advice of several web pages addressing this issue, and trying several different drivers.
Pressing on, I decided to try to install TWRP again. Booted phone with VolDown, Home, Power. First I tried using Heimdall 1.4, both with drivers from Samsung, and then with the MSM8960 drivers that came with Heimdall, using this command:
heimdall flash --RECOVERY twrp-3.3.1-0-hlte.img --no-reboot
In both cases, all I got was "ERROR: Failed to access device. libusb error: -12"
Therefore, decided to try it with Odin. Booted phone with VolDown, Home, Power. Run Odin 3.12.4_4, which immediately shows "Added". Load TWRP 3.3.1.0 with AP button, click Start...and get a red Fail flag within a few seconds. Log shows "FAIL! (Auth). Phone shows "SYS REV CHECK FAIL: No Version" and "SECURE MAGICCODE CHECK FAIL: recovery".
I didn't even bother trying to flash the LineageOS ROM.
Can someone please tell me what I'm doing wrong? Please don't assume I know anything about what I'm doing.
--
*not an expert*
Verify that you are using the correct build of twrp-3.3.1.
I am using the hlte build of 3.3.1 on my phone (SCL22)... but my gut tells me that you and I wouldn't share the same build.
Nope basic problem is that OP is in the wrong forum for a Verizon phone .
Assuming that download mode still works (if it is, lucky you); I'd suggest reflashing the stock firmware for your Verizon device.
Flashing a stock firmware would *hopefully* fix your recovery and download issues.
Perhaps the errors you described may have been caused by installing the wrong ROM/firmware.
So, NEVER INSTALL/FLASH a custom or stock ROM that is not tested to work on your device. The main reason is because different variants of the same device (N9000, N900A, N900V) use different chipsets, software and drivers. Also, flashing a wrong ROM/kernel/firmware may cause application errors, boot loops, broken recovery/download mode, or a hard brick.
I tried rooting my tablet and I'm using arch linux on my computer, so I had to use Heimdall and Jodin to root it. I got the Heimdall to say "flashed succesfully", but I still didn't have twrp on my tablet.
Then I found Jodin and tried to use that to flash twrp on my tablet, but I really didn't got it to work. It usually said failed, because tablet would disconnect during the flash and reconnect right after.
Right now the tablet is stuck in "bootloop" it just boot's into the black screen where it says "Samsung galaxy tab a etc.". I can boot into download mode, but I really don't know how to fix this. When I boot into download mode, both jodin and heimdall detects the phone. Any tips how to fix this?
Try go to download mode by mtp from windows or micro USB with resistance
If you want to download twrp for root so you can make root with out it
Just by eftus and flash file from site or magisk apk with AP file same ver on your phone
I guess I wrote pretty confusing post. I can go to download mode, but not boot to the android. Right know I got it saying "could not do normal boot invalid kernel length"
Jodin says this when trying to flash:
<ID:0/008> Added!!Device Connected
Device Removed
Device Connected
/usr/bin/heimdallDevice Removed