I'm trying to flash a recovery with heimdall, and when I do it, it says it's successful, reboots. So when it boots normally, I restart the unit with
Code:
adb reboot recovery
or by holding down the up volume button, however it still boots into the stock recovery.
I thought for a second the flash was happening to the wrong memory address/parition, so I downloaded the pit file and reapplied the recovery flash with the pit file.
Can anyone suggest what I might be doing wrong?
Code:
1819 sudo heimdall flash --recovery recovery-cwmtouch-6.0.2.7-GTI9300.tar
1821 sudo heimdall flash --recovery recovery.img
1824 sudo heimdall download-pit --output YP70-michael.pit
1826 sudo heimdall flash --recovery recovery.img --pit YP70-michael.pit
Promethyl said:
I'm trying to flash a recovery with heimdall, and when I do it, it says it's successful, reboots. So when it boots normally, I restart the unit with
Code:
adb reboot recovery
or by holding down the up volume button, however it still boots into the stock recovery.
I thought for a second the flash was happening to the wrong memory address/parition, so I downloaded the pit file and reapplied the recovery flash with the pit file.
Can anyone suggest what I might be doing wrong?
Code:
1819 sudo heimdall flash --recovery recovery-cwmtouch-6.0.2.7-GTI9300.tar
1821 sudo heimdall flash --recovery recovery.img
1824 sudo heimdall download-pit --output YP70-michael.pit
1826 sudo heimdall flash --recovery recovery.img --pit YP70-michael.pit
Click to expand...
Click to collapse
I suggest just flashing a kernel that has CWM for your device using Odin. This should solve your problem.
Can you suggest one? I'm having a hard time figuring out which are compatible with Odin/Heimdall.
joshm95 said:
I suggest just flashing a kernel that has CWM for your device using Odin. This should solve your problem.
Click to expand...
Click to collapse
Promethyl said:
Can you suggest one? I'm having a hard time figuring out which are compatible with Odin/Heimdall.
Click to expand...
Click to collapse
I've heard that Steve's Kernel is CWM-compatable, but I can't confirm or deny this
Related
I've see the amazingly simple rooting method by DooMLoRD (ZergRush) listed here:
http://forum.xda-developers.com/showthread.php?t=1321582
And I'm wondering if something like that could be done for, once you have root, install CWM.
This would be interesting as it would add a new way to get CWM other than flashing some CWM-containing kernel or using the terrifying Rom manager app...
I am not sure if it would be so simple as DooMLoRD's script since CWM doesn't seem to be an "app" like su / busybox...
What do you think?
Genrauser said:
I've see the amazingly simple rooting method by DooMLoRD (ZergRush) listed here:
http://forum.xda-developers.com/showthread.php?t=1321582
And I'm wondering if something like that could be done for, once you have root, install CWM.
This would be interesting as it would add a new way to get CWM other than flashing some CWM-containing kernel or using the terrifying Rom manager app...
I am not sure if it would be so simple as DooMLoRD's script since CWM doesn't seem to be an "app" like su / busybox...
What do you think?
Click to expand...
Click to collapse
Your best bet at attempting this would be using Heimdall. From the help file:
Code:
7. Use the instructions to manually enter a command with all the files you want to flash.
Here is an example that does a full flash and repartition on a GT-I9000:
heimdall flash --repartition --pit s1_odin_20100512.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --primary-boot boot.bin --secondary-boot Sbl.bin --param param.lfs --kernel zImage --modem modem.bin
NOTE: The above command assumes the files specified are installed in the same directory as Heimdall.
Simply grab a CWM kernel, extract so you have the zimage then heimdall flash --kernel zImage. It would be easy enough to setup a .bat file to give you a few options/menus like the one in your link. Note that this requires the device to be in download mode and I can't imagine any other safe or even possible ways apart from download mode using odin/heimdall or flashing a zip via a custom recovery. Considering that you either have to be in download mode/recovery it seems a little counter productive to go to the extra effort of extracting images or using a command prompt but the above should work.
Genrauser said:
This would be interesting as it would add a new way to get CWM other than flashing some CWM-containing kernel
Click to expand...
Click to collapse
As the recovery mode is part of the kernel, you HAVE TO flash a kernel that contains CWM if you want to use CWM.
THAT however can be done via ADB, yes.
Code:
adb push zImage /sdcard/zImage
adb shell su -c dd if=/sdcard/zImage of=/dev/block/mmcblk0p5 bs=4096
I see.. so what I was thinging is not possible
As you both says, you need to flash a kernel whatsoever.. so the stardart way is much faster than having to extract the zimage and then flash it via adb on download mode (this is the problem, if it could be done on normal mode like that rooting method via adb, getting the zimage and then applying it whenever would be awesome.. but as far as you say it is not ).
Well, really a shame. Thanks both for your help on this!
For what I posted above, you do not need to go into download mode.
If your phone is rooted it works from "normal" mode (i.e. the system running).
You could also check out my little kTool (see sig), that allows you to dump the current kernel or flash a zImage from /sdcard (and a few more things).
The choice of kernels containing is huge for our beloved S2, from ones being very close to original stock down to totally custom ones.
Okay, my bad then, since you didn't elaborate more I implyied you agreed with Hollow.Droid on the "only download mode" subject.
So you actually can change the entire zImage for the CWM with the phone on normal mode... it woud be from the CWM only, not the entire kernel right? Because if a new entire kernel is needed we are on the same stuff again, then its faster to just flash the file via odin and go on.
Otherwise, it would be as simple as getting the CWM's zImage from somewhere and then add it to the phone via adb whenever..
CWM is part of the kernel, the zImage contains the kernel that contains the CWM.
You can not "install CWM" without flashing a whole kernel zImage, the "zImage" *is* the kernel, not only some CWM files.
Okay thanks, sorry for the late answering.
Then I have to flash a new kernel anyway, so it's just faster to do it via odin rather than extracting a zimage and then having to connect, config adb incase you didn't before, etc.
Thanks a lot for your time!
Hey guys, i used to flash with odin, but those times are now gone. moved to linux for real, so i installed heimdall (and heimdall-frontend).
Honestly it seems that command line is easier to understand. My question is: how do i flash only the bootloader?
I need to use the jig, so i need the old bootloader. i already have the TAR.
to execute a normal rom installation, it seems these are the commands:
heimdall flash --factoryfs factoryfs.rfs --cache cache.rfs --param param.lfs --kernel zImage --modem modem.bin --pit s1_odin_20100512.pit
Click to expand...
Click to collapse
But how about flashing just the bootloader?
Also, i didn't install any samsung drivers...is that possible on ubuntu?
This is linuxmint, but anyway, is ubuntu based. thanks
Well, nevermind guys... i'm going to flash it on a friend's computer. However i would like to learn some more about heimdall. the videos i see on youtube, and on google, are from an early version. as the interface changed, i'm kinda lost now.
appreciate any tips. ty
If you just type "heimdall" in Terminal, then there will be a list of possible arguments you can use.
As far as i know you just have to type:
sudo heimdall flash --primary-boot "boot.bin" --secondary-boot "Sbl.bin"
Click to expand...
Click to collapse
I never flashed only a bootloader, so i don't know if there will be any compatibility problems. But command should work.
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?
I have tried following various intructions but am now in a bit off a mess.
At first I could not install TWRP so I read about a custom Kernel is needed.
The phone boots into TWRP 3.1.1.0 after I ran the following command:
heimdall flash --repartition --pit I9100_1.5GB-System_6GB-Data_512MB-Preload_by-the.gangster.pit --KERNEL boot.img --RECOVERY twrp-3.1.0-0-i9100.img
What is weird is that vol down/home/power still boots to stock recovery. Phone boots to TWRP if no buttons are presses.
If I try to upgrade TWRP to 3.5 from within 3.1 it says it has flashed but it still boots into 3.1
Any help please?
After following lots of guides, this is the one that got it working .
Big thanks for that thread.