I can only get into download mode on my phone. So I am trying to flash a stock ROM. When using either Odin or Heimdall its goes to 100% kernel and gets stuck there then fails. In the Heimdall command line its says...
Uploading KERNAL
100%
ERROR: Failed to confirm end of file transfer sequence!
KERNEL upload failed!
Ending session...
ERROR: Failed to send end session packet!
Any ideas what I am doing wrong? I followed Entropy's guide on Heimdall.
Related
So, I compiled my own android image and kernel and want to try it out, it spat out a system.img file.
I've tried both on Windows and Linux to get fastboot working, but I cannot. My device never gets detected.
(Really wondering if it's even possible)....fastboot mode is odin mode...right? I haven't a clue...anyways.
I tried Heimdall as well. Kernel flashing works great, but factoryfs flashing results in an error:
ERROR: Failed to confirm end of file transfer sequence!
So that's out as well.
I've been searching around, but I can't seem to find another option, any ideas?
EDIT:
Came across this: http://blog.coralic.nl/2010/01/25/how-to-create-update-zip-using-your-build-aka-system-img/
Basically system.img -> update.zip.
Guess that's one way to do it.
hi
I'm trying to use this guide to flash my phone:
http://forum.xda-developers.com/showthread.php?t=1453660&page=2
and i get this:
ECHO is off.
Flashing BootLogo....
error: cannot load 'logo.bin'
Flashing EBR....
error: cannot load 'ebr_signed'
Flashing MBR....
error: cannot load 'mbr_signed'
Flashing DevTree....
error: cannot load 'devtree_signed'
Flashing Android System....
error: cannot load 'system_signed'
Flashing Kernel....
error: cannot load 'boot_signed'
Flashing Android Recovery....
error: cannot load 'recovery_signed'
Flashing CDR....
error: cannot load 'cdrom_signed'
Flashing Radio (BP)....
error: cannot load 'radio.img'
Flashing WebTop....
error: cannot load 'webtop_signed'
Click to expand...
Click to collapse
phone reboots and nothing is new
i don't know what I'm doing wrong
I have tried this with the arctic rom gsm version
and this Blur_Version.65.1.12.XT910.AsiaRetail.en.03
I'm trying to roll back so i can root my phone...
my ota is:65.1.21.xt910.Retail.en.il
thanks
Sounds like it cant find the files to flash. Everything is in the same spot? Or extracted properly... Why don't you use cwm to flash arctic? Can you even use rsd to flash arctic rom??
Sent from my XT910 using XDA App
Hello,
Info: After failing at building Mozilla Boot-To-Gecko myself, I downloaded the build by pulser_g2 (from this thread).
Code:
ccfa6d5fd32d13190febf73f323fe302 B2G-flash-ODIN.tar.md5
61e6d69dd68132b593944934254d7f2d data.img
6bde9ff81be3c3834d55ee046393decd factoryfs.img
93fa4b1825d95ed10cd9834975ca6761 zImage
Then, I did
Code:
$ adb reboot download
and ran
Code:
$ heimdall flash --factoryfs factoryfs.img --kernel zImage --data data.img
But the DATAFS is not uploaded completely - it stops at 87%.
[...]
Uploading DATAFS
87%
ERROR: Failed to confirm end of file transfer sequence!
DATAFS upload failed!
Ending session...
ERROR: Failed to send end session packet!
Re-attaching kernel driver...
Click to expand...
Click to collapse
I have tried several times but it always fails at the same point. I have also wiped the data and cache several times.
My Samsung Galaxy S II was bought in Norway bundled with a subscription from the carrier Tele2. It came with the Android 2.3.5 XWKI8 firmware.
Question: Is the file corrupt? Am I doing something wrong? Is the build not compatible with my phone?
Take a closer look.
pulser_g2 said:
Anyway, what is this? Well, it's a TAR to flash via ODIN (codeworkx informs me not to flash userdata partition via heimdall, I suggest you heed that warning, and this tar contains the userdata partition).
Click to expand...
Click to collapse
oinkylicious said:
Take a closer look.
Click to expand...
Click to collapse
Well, that's embarrassing. I usually read carefully before posting questions, but apparently I failed to do so this time :/
I can't flash a recovery image through heimdall every time i try to it either says "heimdall crashed!" or "handshaking with loke...failed"
Hi!
I have a problem with a I9100. I follow the instructions on CyanogenMod wiki for flashing the recovery, but something went wrong.
I used heimdall 1.4.0 in GNU/Linux and execute
Code:
sudo heimdall flash --kernel zImage --no-reboot
All worked well and the blue progress bar appears on the screen. When it finished, I tried to enter recovery using the VolUp+Home+PowerUp buttons combination, the Samsung Galaxy S2 logo appears on the screen but it is stuck on this screen.
I tried to re-download the zImage file (using another link, different from the CM wiki one, but the same happened.
Is there an easy way to reboot into recovery from Heimdall, like with fastboot on other devices?
Is possible to install a recovery in another way?
Best regards and thanks in advance
Lk2 said:
Hi!
I have a problem with a I9100. I follow the instructions on CyanogenMod wiki for flashing the recovery, but something went wrong.
I used heimdall 1.4.0 in GNU/Linux and execute
Code:
sudo heimdall flash --kernel zImage --no-reboot
All worked well and the blue progress bar appears on the screen. When it finished, I tried to enter recovery using the VolUp+Home+PowerUp buttons combination, the Samsung Galaxy S2 logo appears on the screen but it is stuck on this screen.
I tried to re-download the zImage file (using another link, different from the CM wiki one, but the same happened.
Is there an easy way to reboot into recovery from Heimdall, like with fastboot on other devices?
Is possible to install a recovery in another way?
Best regards and thanks in advance
Click to expand...
Click to collapse
try 'Odin flash' of a recovery file from a windows Pc and see
Thanks for your answer.
I tried to flash the TAR package with zImage inside from Odin, and same result.
I tried to flash a stock ROM with Odin, and it gives me a non-readable error (a lot of []).
I tried to decompress the stock ROM and flashing with heimdall:
Code:
sudo heimdall flash --primary-boot boot.bin --cache cache.img --factoryfs factoryfs.img --hidden hidden.img --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --no-reboot
And it fails (primary-boot not recognized):
Beginning session...
Session begun.
Downloading device's PIT file...
PIT file download successful.
ERROR: Partition name for "primary-boot" could not be located
Ending session...
Releasing device interface...
Re-attaching kernel driver...
Click to expand...
Click to collapse
Any idea?
Type this in android terminal emulator:
Su
Reboot recovery
Send from my SGS2 I9100 with HassanROM and latest DorimanX 8.xx kernel
I can't do "reboot recovery" from Android Terminal because I have another issue (read bellow)
Something went wrong with Heimdall. After all, using Odin I was able to boot into recovery mode and flash the ROMs, but when I tried to reboot in "normal mode" I got a "kernel panic upload mode rst_stat=0x200000000" screen.
I did a little research and it appears to be mandatory to flash a stock ROM and begin again with all the process.
I tried it, with the latest stock ROM for my country and company, but Odin return an extrange error when I press in "Start" button. The popup Windows puts the filename and a lot of "squares" (character with a different encoding, like chinese).
EDITED: I was able to flash the stock ROM, but the phone still doesn't boot. The yellow triangle disappeared but it cannot but
What can I try next?