Database Info

My tab is stuck on Samsung Galaxy Tab 7.7 logo

Hi!
I had PacMan Rom Milestone 1 on my tab. Then the official Jelly Bean rom from Samsung was ported to the p6810 and I wanted to try it because I had problems with wifi.
After flashing with Mobile Odin the tab was stuck at Samsung logo (the animated and colored one). (I waited for +10 minutes, maybe I wasn t patient enogh)
So I tryed reflashing with Heimdall (as I only have a linux machine at the moment):
-First I flashed with the GUI and it did flash all the files except sbl (No correct response (or something like that) at the end of the transfer of sbl.bin).
-So I tryed flashing form command line but the command line tool did completely ignore the sbl. I also tryed to flash only sbl but so it didn´t flash anything, but didn´t give out any errors.
-Ok let´s flash the new rom released by Samsung for Spain in September. Sadly now the tab is stuck at the first boot screen
$ sudo heimdall flash --cache cache.img --factoryfs factoryfs.img --hidden hidden.img --recovery recovery.img --secondary-boot Sbl.bin --kernel zImage --param param.lfs
Password or swipe finger:
Heimdall v1.3.1, Copyright (c) 2010-2011, 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...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
100%
KERNEL upload successful
Uploading RECOVERY
100%
RECOVERY upload successful
Uploading CACHE
100%
CACHE upload successful
Uploading FACTORYFS
100%
FACTORYFS upload successful
Uploading HIDDEN
100%
HIDDEN upload successful
Uploading SBL1
100%
SBL1 upload successful
Uploading PARAM
100%
PARAM upload successful
Ending session...
Rebooting device...
Re-attaching kernel driver...
Click to expand...
Click to collapse
I read many threads about this problem and I´m trying to discharge the tab now but I don´t have the same problems (I can go into recovery without problems).
Can I do a "wipe data/factory reset" without risking the brick bug?
Thank you for reading the long explanation.
Teddy

Ok I got it running with PacMan flashed from CWM and I restted the flash counter . Now I'll see if get Stock GB running...

twrp installation, still boot on stock recovery

opensuse 13.1 x86_64
heimdall 1.4.1
Samsung s2 plus i9105p
i installed with no problem twrp-3.0.2-0-s2vep.img from twrp site or twrp-recovery-2.6.30_4.2.2.img from http://forum.xda-developers.com/showthread.php?t=1538053
but when i boot with home+volume up+power the stock recovery is launched instead of twrp.
log of the flashing:
**********************************************************************************************************
[email protected]:~/rpmd/samsung> heimdall flash --RECOVERY twrp-3.0.2-0-s2vep.img
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%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
[email protected]:
**********************************************************************************************************

ok i found solution.
use this statement:
heimdall flash --RECOVERY twrp-3.0.2-0-s2vep.img --no-reboot
once flashing is finished then use home+volume up+power. thus you launch twrp.
at the first launch twrp becomes the default recovery for the system.

[Solved] Heimdall problem s10e "an error has occured while updating device software"

[Solved] Heimdall problem s10e "an error has occured while updating device software"
Hi there, I was trying to change my firmware (to prepare my phone before flashing a lineageos rom), I did so using heimdall (last samsung firmware downloaded from sammobile), and it crashed in the middle of the process (while copying VENDOR file). Not sure if it is a problem with the firmware or something else (but I guess not the cable as I tried with 2 cables and the problem arrives always at the same moment).
The phone is a SM-G970F, I was trying to flash the firmware U9DTJA.
Anyway, I can still flash with heimdall, although the screen is not the "standard" download mode screen… but I don't know what to do!? I tried to install virtualbox+samsung drivers + odin (standard version and then patched version), I can't get odin to recognize my phone. Windows just tells me "this device can perform faster" when I allow virtualbox to detect the phone (which appears as Samsung Gadget Serial [021B]). I also tried smart switch without success (I don't know what it is suppose to do, but looks like it does not recognize any phone). Do you think this is normal due to the fact that the phone is not truly in download mode? Or is it a problem with windows drivers? An idea to either fix things with heimdall or to get odin working?
I would appreciate if someone has any hints as it's my only phone and I'm kind of stuck
-------------- EDIT: this is what I get when flashing:
heimdall flash --BOOTLOADER sboot.bin --CM cm.bin --PARAM param.bin --UP_PARAM up_param.bin --KEYSTORAGE keystorage.bin --UH uh.bin --DTB dt.img --DTBO dtbo.img --BOOT boot.img --RECOVERY recovery.img --RADIO modem.bin --DQMDBG dqmdbg.img --VBMETA vbmeta.img --SYSTEM system.img --VENDOR vendor.img --PRODUCT product.img --CACHE cache.img --OMR omr.img --CP_DEBUG modem_debug.bin --USERDATA userdata.img
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.
Uploading BOOTLOADER
100%
BOOTLOADER upload successful
Uploading CM
100%
CM upload successful
Uploading PARAM
100%
PARAM upload successful
Uploading UP_PARAM
100%
UP_PARAM upload successful
Uploading KEYSTORAGE
100%
KEYSTORAGE upload successful
Uploading UH
100%
UH upload successful
Uploading DTB
100%
DTB upload successful
Uploading DTBO
100%
DTBO upload successful
Uploading BOOT
100%
BOOT upload successful
Uploading RECOVERY
100%
RECOVERY upload successful
Uploading RADIO
100%
RADIO upload successful
Uploading DQMDBG
100%
DQMDBG upload successful
Uploading VBMETA
100%
VBMETA upload successful
Uploading SYSTEM
100%
SYSTEM upload successful
Uploading VENDOR
21%
ERROR: Failed to send file part packet!
ERROR: VENDOR upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Click to expand...
Click to collapse

Well I found a workaround. Apparently:
- There is a bug with heimdall or libusb, I don't know at which level exactly but it does not work well with this device and I'm apparently not the only one for which it happened
- Altough the screen was not the "standard" download mode ,the phone was ready to be flashed, no problem with that.
- I managed to flash with odin by borrowing a windows computer… … …
- I have no idea why it does not work with virtualbox, but apparently this was really a virtualbox problem (or the way linux deals with usb, no idea) and nothing related to the phone in particular. It would be great to find a way to get that working, but I have no clue so far.
At least, I have a working phone now…

Question What custom ROM suggest to this device?

Hi,
I would like to get suggestions on a ROM to flash on A12,
Lineage is available?
Suggestions.
Thank you.

Try some gsi roms.

Yes, i’m going to flash GSI’s on my PIT partition for system.img, but that partition isn’t found from my PIT file
An i’m encountering this error below on Heimdall,
Code:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to send handshake!ERROR: Protocol initialisation failed!
Releasing device interface...
But my Android side is below, and feels like ok,
Code:
Heimdall Download mode (high speed)
Product name: SM-A125F
Current binary: Samsung official
OEM lock: Off (U)
KG status: Checking
MTK secure boot: Enable
Warranty void: 0x0 (0x0)
PR SWREV: B1 NS1 K1 S1
Secure Download: Enable
CASS: 0x1
DID: 000ac3086b58
CARRIER_ID: TGY

Im trying to install some GSI's too, the problem is that we have the system.img but to make the changes we have to flash it in the "super" partition, thats why Heimdall doesnt recognized it from the A12's pit... Please let me know if you guys solve it...

I guess, instead flash your GSI .img files on your super partition, and you instead need to download online PIT docs, according to your ‘‘Product name’’.

I tried to flash the Lineage GSI by Andy Yan on SF using Heimdall (yes i’m no longer on Windows), and also AOSP one, but unfortunately and somewhy,
Code:
SW REV check failed!

I cant follow you , Im not so much familiarized with this dynamic partition but Ill try to...

For me, on LinageOs when I turn off the screen and then turn it back on screen touch doesn't work.
GSI 11 same problem and the 3 button navigation pannel not working.

Adb sideload crashes all time i try again and odin stucks at setupconection

i found my old samsung galaxy trend plus(gt-s7580) and it bootloops. if i try to sideload firmware it says:failed to write data: protocol fault (couldn't read status): Broken pipe. and odin stucks at setupconnection. (odin woks on other devices.() can somebod help pls?

Still waiting

May be ADB is out of date.

jwoegerbauer said:
May be ADB is out of date.
Click to expand...
Click to collapse
Okay... but how can i fix odin

With patched odin it says after setupconnection:Complete(write) operation failed plsss helpp