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
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:
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
First of All i dont own this device !!!! so i cant test by myself
Twrp is based on A22 4g and modified for A22 5g
if someone is brave enough to test it please pm me
for flash instructions - Look Here
Boot.img/Recovery.img is from A226BXXU1AUEH Firmware
To Root your device try magisk prepatched boot.img (magiskboot.tar)
TWRP didnt work so i deleted it
Has anyone tried this yet?
physwizz said:
Has anyone tried this yet?
Click to expand...
Click to collapse
did you try this?
aviv926 said:
did you try this?
Click to expand...
Click to collapse
I don't have a22
any chance you can dumb this down for me to try? I'm new to android and rooting
This isn't working for my SM-A226B. It works through step #9 (flash vbmeta & twrpa22, then restart)--ie, flash indicates 'pass' for both. But at step #10, vol+ and power, my phone never goes into TWRP. I've tried several versions of the twrp file, various combinations of having the USB plugged in while I do it, holding for different lengths of time, etc. It just gets stuck in the Samsung logo boot loop. I can't even turn it off with vol- and power. The only response I can get is moving it to download mode with vol+,vol-,usb. The phone is fully charged.
Root works for me, just attached the magiskboot to odin AP, not im rooted!, not bothered about twrp but thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rooted thru magisk method, not this one posted. also call recording by default activated and screen record enabled.
Made the root img for you all, odin place it in AB, anyone need help just msg.
I tried the TWRP and VBMeta tar, it just got into a bootloop like another guy. I tried flashing the Magisk tar, didn't work, so I tried using my own boot image from the stock rom, didn't work either.
Cheese-ass said:
First of All i dont own this device !!!! so i cant test by myself
Twrp is based on A22 4g and modified for A22 5g
if someone is brave enough to test it please pm me
for flash instructions - Look Here
Boot.img/Recovery.img is from A226BXXU1AUEH Firmware
To Root your device try magisk prepatched boot.img (magiskboot.tar)
Click to expand...
Click to collapse
Would it work in galaxy f22
Yangasto said:
Would it work in galaxy f22
Click to expand...
Click to collapse
Similar in specs but most likely incorrect values in the BoardConfig.mk and other files. You could attempt it but just be prepared with Odin and your device's firmware file.
Magisk patched boot works but twrp doesn't, only shows samsung logo.
koosman911 said:
Magisk patched boot works but twrp doesn't, only shows samsung logo.
Click to expand...
Click to collapse
Same with me and everyone else.
jtownsle said:
This isn't working for my SM-A226B. It works through step #9 (flash vbmeta & twrpa22, then restart)--ie, flash indicates 'pass' for both. But at step #10, vol+ and power, my phone never goes into TWRP. I've tried several versions of the twrp file, various combinations of having the USB plugged in while I do it, holding for different lengths of time, etc. It just gets stuck in the Samsung logo boot loop. I can't even turn it off with vol- and power. The only response I can get is moving it to download mode with vol+,vol-,usb. The phone is fully charged.
Click to expand...
Click to collapse
Greetings.
I had tried this twrp+vbmeta stuff. I got stucked on it too, because there is no way to go to recovery mode as described in the list.
What I did and that worked for me on my A225M/DSN was downloading fisrt the vbmeta file, without autoreboot, then, gone to power+vol down(-) untill it reboot and gone to download mode again and downloaded the twrp file to the device. When it got finished to download with success, i went to power+vol down(-) again and went into recovery mode and did the rest of the list as written there.... At list it worked this way for me.
I hope I had helped with this...
Platypus Enthusiast said:
I tried the TWRP and VBMeta tar, it just got into a bootloop like another guy. I tried flashing the Magisk tar, didn't work, so I tried using my own boot image from the stock rom, didn't work either.
Click to expand...
Click to collapse
I tried this method too, but in my case, when I connected it to my computer, it showed as a A225F instead of A225M/DSN, so I had undone all, flashed the stock rom back, locked the bootloader and restored it to original form.
After that, I had found a post on the internet, showing how to patch Magisk on the AP file from the stock firmware, and I did it. Now my A225M/DSN is rooted with no problem.
About twrp, there is no official from teamwin and that one I had found here, is kinda bugged.
I Tried using the twrp+vbmeta from here to the A225F but no lucky. If there were a way to find a twrp that worked for the A225M/DSN, it would be nice, so I could use another firmware flavor... but... I can only wait and see...
Hi. I tried flashing the twrp.img from first post of this thread to the recovery partition but unfortunately my phone ended up in a very slow, very tricky, annoying and very dark bootloop. Almost as dark as the black hole in the milky way galaxy. The sort of bootloop you don't want to find your device in. Xiaomi bootloops are so much easier to get out of let me tell you! Especially since they ship with a fully working , non-crippled fastboot! Ain't that right @samsung?
Here's the log:
Spoiler: brick_log
heimdall flash --recovery ./recovery.img --no-reboot
Heimdall v1.4.1
Copyright (c) 2010-2014 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...
Releasing device interface...
After hours upon hours of trying in vain I somehow managed to get the Galaxy device to boot into Download mode (don't ask me how - it just happened)
Then I tried to flash the stock recovery.img from first post of this thread and it gave me this result:
Thank god phone is still in Odin mode
Spoiler: fail_log
heimdall flash --recovery ./recovery.img
Heimdall v1.4.1
Copyright (c) 2010-2014 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...
And on phone itself it give this error:
SW REV CHECK FAIL : [recovery]
Fused 4 > Binary 1
RP check error : recovery
Click to expand...
Click to collapse
EDIT: problem solved
lebigmac said:
Hi. I tried flashing the twrp.img from first post of this thread to the recovery partition but unfortunately my phone ended up in a very slow, very tricky, annoying and very dark bootloop. Almost as dark as the black hole in the milky way galaxy. The sort of bootloop you don't want to find your device in. Xiaomi bootloops are so much easier to get out of let me tell you! Especially since they ship with a fully working , non-crippled fastboot! Ain't that right @samsung?
Here's the log:
Spoiler: brick_log
heimdall flash --recovery ./recovery.img --no-reboot
Heimdall v1.4.1
Copyright (c) 2010-2014 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...
Releasing device interface...
After hours upon hours of trying in vain I somehow managed to get the Galaxy device to boot into Download mode (don't ask me how - it just happened)
Then I tried to flash the stock recovery.img from first post of this thread and it gave me this result:
Thank god phone is still in Odin mode
Spoiler: fail_log
heimdall flash --recovery ./recovery.img
Heimdall v1.4.1
Copyright (c) 2010-2014 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...
And on phone itself it give this error:
All these different Samsung firmware websites only offer slow download speed 300 KB/s max. and I don't got premium account!
And whole firmware is 5GB that means I must wait 6 hours +
Should I keep the phone in download mode until then? Then I must leave it plugged in because screen will drain battery fast. I guarantee you that I will never ever be able to get it back into download mode again if I turn it off now. Can I even turn it off?! Nope. I can force reboot with vol down + power (hold for 10 seconds) but there is no key combo for force power off or shutdown
Can someone reading this please upload only the stock recovery of their Samsung Galaxy A22 5G (SM-A226B)? Or upload only the official file that the stock recovery is contained in such as one of those AP, CP or CSC files.
Thank you very much!
I think the firmware my device was running was Android 11 and February 2022 security patch or something. That shouldn't really matter as long as it's stock Android 11.
Maybe it's somehow possible to fix this annoying bootloop without having to download the full 5 GB of the firmware. I only overwrote the recovery partition.
I think next time I will flash using Odin like everyone else and I'll leave Heimdall to the real pro's
Does anyone know how to flash only recovery with Odin? Do I flash the AP, CP or CSC file? I guess not the BL that sounds like BOOTLOADER!
Thanks
Now I am very confident that soon I will finally be able to get this phone out of this mess and back up and running!
Click to expand...
Click to collapse
Sorry you didn't get help immediately, I don't check my emails often unless I want a verification code from some website.
I also screwed up my A226B (different cause), I deleted an old copy of firmware files because they were outdated, so I went to Sammobile for a different one, spent 4 hours downloading an archive that turned out to be corrupted. It was already 1 AM at that point so I went to bed. The next day, I tried downloading it again, thinking my slow internet at the time corrupted the download, waited another 4 hours, but same result. I decided to take a risk and try out those sketchy websites. I tried out samfw.com and it worked good, so you might want to try that.
About which files to flash, flash BL, AP, CSC, and CP to do a restore. HOME_CSC is if you want to keep your files, CSC if you want to start out fresh.
Edit: BL is bootloader, CP is the modem, CSC is the region specific features, and AP is the main file. Usually flashing AP will make your phone work again, but you won't be able to get software updates unless you flash the others. Also samfw downloads pretty fast.
Thanks for the quick reply.
I finally got the phone back up and running by flashing the full firmware with Odin.
Thank god this nightmare is now finally over. What's the best way to root this thing without bricking your device? Thanks
lebigmac said:
Thanks for the quick reply.
I finally got the phone back up and running by flashing the full firmware with Odin.
Thank god this nightmare is now finally over. What's the best way to root this thing without bricking your device? Thanks
Click to expand...
Click to collapse
Recovering from a brick is all part of the samsung learning experience
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?