Database Info

softbricked sk4g pain in the arse!

Hello, i recently messed up my SK4G by trying to root it and basically the last thing I did before my SK4G became stuck on the loading screen was click recovery in the QuickBoot app. So now everytime I turn it on, it becomes stuck on the loading screen.
From this, I simply googled up how to solve this, and got Odin and Heimdall.
So with Odin, I was able to put my phone in Download mode but Odin was never actually able to connect with my phone... I don't know why however and simply moved on to Heimdall.
With Heimdall, it connects and everything works fine.
UNTIL THE MODEM THING + ITS REBOOT. Once it reboots, the SK4G turns off and goes right back to its annoying stuck loading screen.
Please help I'm more stuck than Sharpie on your clothes
HERE IS WHAT THE HEIMDALL STATUS IS:
Total Stock UVKG2 is ready for your device.
Operating System: Windows
Found Heimdall Version: v1.3.1
Connect your device in Download Mode to procede.
Device not connected.
Ready for flash.Repartition was requested but bootloaders are not to be flashed.
Omiting Bootloaders.
KERNEL RECOVERY FACTORYFS DATAFS CACHE MODEM
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
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:
Initialising connection...
Detecting device...
Claiming interface...
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: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
KERNEL upload successful
Uploading RECOVERY
RECOVERY upload successful
Uploading MODEM
MODEM upload failed!
Ending session...
Rebooting device...
Device not connected.
Click to expand...
Click to collapse

I had a similar issue, check this out:
http://forum.xda-developers.com/showthread.php?t=1717592

[Q] GT-P5110 stuck at splash screen

Hi Folks,
I was asked to attempt a repair on this stock GT-P5110 that has stuck on its logo screen since doing an ota update.
First i tried using stock recovery:
Wipe data/factory reset ran ok but rebooted to the same stuck logo.
Wipe cache partition just gives "ERROR" and reboots to stuck logo
Then i attempred to flash via Odin in download mode
I know it works ok as i had used it to flash a samsung galaxy phone no problem.
On this tab however although it recognised the tab, it hangs whilst trying to send the img.
I switched to Ubuntu and Heimdall.
Again, tab recognized and was able to print the PIT, when i came to install CWM recovery, I get the following:
sudo heimdall flash --RECOVERY recovery.img
[sudo] password for john:
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...
ERROR: Protocol initialisation failed!
Releasing device interface...
I think that USB debugging isn't switched on, so the device cant communicate?
Is there any update.zip that i can load from stock recovery that might help?
Update from cache allows me to navigate to /cache/recovery, but there is nothing in the folder
Can anyone offer advice please?
Regards
John
Update,
Following the same commands i had success uploading CWM recovery.img to the tab.
It reboots to stuck Logo screen. When i enter recovery mode, the stock recovery appears, with no CWM.
[email protected]:~$ sudo heimdall flash --RECOVERY Recovery.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...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
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...
Re-attaching kernel driver...

Fixed
I was able to flash a stock firmware with Odin today, which brought the tablet back to life.

Good. .

Thanks PP:good:

[Q] Stock boot image for Verizon S3?

So, in an attempt to root a verizon Galaxy S3 i have laying around, I seem to have messed things up a bit.
I was following this:
http://wiki.cyanogenmod.org/w/Install_CM_for_d2vzw
I got as far as getting Heimdall working, and attempting to flash aboot, and then boot.img.
I ran the aboot flash, and didnt notice that it failed to flash. The phone then auto-rebooted. I got it back to download mode, and flashed boot.img.
This worked, and rebooted. After the reboot, Verizon gave me the finger. The device now wont boot. I believe i need to either replace the boot.img with stock, OR get the aboot flash working. Once i get one or the other, i think i'll be back in business.
Here is the output of my failed aboot.
Code:
kenshin:S3Root war$ heimdall flash --ABOOT aboot.mbn
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...
PIT file download successful.
Uploading ABOOT
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: ABOOT upload failed!
Ending session...
Rebooting device...
Releasing device interface...
kenshin:S3Root war$ heimdall info | head -n1
Heimdall v1.4.0
Any help here?
Thanks.

Also, i neglected to check what update the device was at when i started. and of course, now i cant.
I can say that the phone has been powered off since october 2014.

I managed to get this worked out.
I was able to get the stock images via this thread:
http://forums.androidcentral.com/ve...verizon-galaxy-s3-how-can-i-return-stock.html
Direct link here:
http://samsung-updates.com/details/30088/Galaxy_S_3_Verizon/SCH-I535/VZW/I535VRUDNE1.html
I decompressed the downloaded zip, then the tar.md5 inside, and found the boot.img i needed to at least get the phone working again. So i'm back where I started at least.

You'll be able to root it via towelroot now that you've updated to the latest firmware 4.4.2 NE1
Sent from my Nexus 5

New S7 stuck in download mode after flashing twrp with heimdall

Hi all
I was just about to install twrp on my brand new S7. I did it as I did it many times before with different Samsung devices with heimdall from Linux.
Now I need urgent advice: The phone is totally stuck in the blue download mode screen and does not react to anything. It is just saying Do not turn off target. Here is the output from the actually somehow successfull heimdall run:
$ heimdall flash --RECOVERY twrp-3.2.1-1-herolte.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%
RECOVERY upload successful
Ending session...
Releasing device interface...
Please guys, any advice appreciated! I cannot turn off the phone neither reboot it. What will happen if the battery is gone?

Hold Power & Volume Down to reboot out of download mode

Thank god! That's a hell of a hint. I have scanned across a lot of posts with "stucked in download" but I haven't found this.
Now I was able to run the original recovery and my stock installation is working again. I will give it another try if I have more time.
Any idea what might went wrong here?
Thanks thanks thanks and best regards!

Most people use ODIN 3.12.3 or newer to flash TWRP, but even if you just enter download mode and don't flash anything, that button combo is needed to exit DL mode

I use Win10 running in VirtualBox on Linux hosts (Debian-based). Dedicate a physical USB port to the VM, instead of connecting USB devices to it. Odin works like a charm.
To determine USB port #:
Plug any device into the physical USB port to dedicate to the VM.
Code:
vboxmanage list usbhost
....and look for Port: for the device. That Port: number goes in a blank USB filter - and only the port number. See attached photo. View attachment 4431742
Sent from my SM-G930W8 using Tapatalk

*Detection* said:
Hold Power & Volume Down to reboot out of download mode
Click to expand...
Click to collapse
All right, all right. Heart rate normalizes ... They somehow missed this ESSENTIAL information between step 6 and 7 in the wiki.

[Resolved] Custom Rom Blocked in DL Mode

Update: Resolved, thanks for the help. --- I was not entering download mode correctly. For any other rookies having this same problem, the phone must be OFF and unplugged. Hold the volume keys while plugging in to computer via USB.
Greetings. I am a first time poster, so sorry if this is in the wrong section. To give a little more context, I am a rookie to flashing phones, though I did manage to brick a Samsung GS4A (Snapdragon, go figure) back in 2013.
I have a N970F/DS, grey-market imported and originally from the UAE. I am having trouble flashing Iode OS using a laptop running Linux Mint. Following the instructions from the page and tutorials, I have done the following:
Unlocked developer settings
Enabled bootloader unlock and USB debugging in developer settings
Downloaded the roms from the host site
Installed Heimdall and ADB on my laptop
Connected to the the laptop via USB cable, I ran the command prompt: "ADB reboot bootloader." This took me to the image attached below. I then held the Vol-Up key, which was supposed to fully unlock the bootloader.
I rebooted to bootloader, then ran the command: "heimdall flash --RECOVERY iode-2.2-20211108-d1-recovery.img --no-reboot"
Upon running step 6, my laptop terminal gave the following message:
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
Glass Echidna
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:
Donate | Glass Echidna
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...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
Click to expand...
Click to collapse
From the download screen, I received the following message in red text:
custom binary blocked
Click to expand...
Click to collapse
I tried running this several times, including rebooting the phone a couple times in between. I still was unable to proceed with flashing the recovery.
Digging a little further into the matter on both XDA and duckduckgo, I found a few potential threads related to other (though older model) Samsung devices. One thing that I tried was flashing the stock firmware. I tried downloading and flashing my phone's stock rom using JOdin3, but I received an error message stating that the rom was corrupted. After that, I ran a factory reset and called it a day.
At this point, I am not sure what I am missing. Any ideas that a novice might be missing?