Hey XDA,
I Recently attempted to flash my Kernel to KhasMek Voodoo plus v5 using SGS flasher and heimdall. But upon reboot, the system gets stuck at the samsung screen, and i can't boot into recovery.
I end up having to boot into download mode and recover to stock VZW (using heimdall and the necessary files)
---------------------------------------------------------------------------
The procedure I used is as follows:
Started with: Stock VZW SGT w/4gb microSD (about 3gb free)
1: I rooted using superoneclick
2: Then Used Koush's CWM Recovery Method
- Downloaded The "Verizon Tab Bootstrapper" application to convert my SD card to ext4, then downloaded Rom Manager, flashed recovery for a VZW tab and backed it up.
3: I Flashed with SGS Flasher
-I put the v4 Kernel on my SD card (along with the v5 zip for later) and flashed to it. The software recognized the root & successfully flased the device, but could not reboot the device ( I rebooted manually)
And....that's as far as i got, i'm stuck at an empty battery picture if plugged in, or the samsung screen if unplugged. But i can get into download mode, and subsequently get back to stock.
I tried again without applying the prompted android update (Is this the EC02 update?) and had the same outcome.
Can anyone spot my blunder?
Thanks a ton
In a true show of ignorance, the solution was in the developer's thread about 40 pages in.
The solution was to use The .tar kernel file (linked for option 3) instead of the .zImage (linked for option 2)
SGS flasher worked this time, still didnt auto-reboot
But now i'm running boush's kernel and it's @1.4ghz Stable.
(quadrant score from ~950 - ~2100)
Related
Hi,
I've been checking around the forums, and I've seen similar instances, but they seem to all be with the Canadian version which is why I thought I would ask before doing anything else.
I have the Galaxy S i9000 european version. Was rooted, and had lagfix (Voodoo) and was using stock ROM.
Using ROM manager I flashed the clockwork mod recovery. Booted into recovery everything went well. (was just testing that it works).
So now I click reboot and it gives me the static galaxy s screen, then the moving S. Waits for about a min or two, then screen goes black.
So i tried going to recovery mode, that works, but its the samsung 2e recovery mode not the clockwork recovery mod.
So now I'm not sure how to continue. Before I put on the voodoo fix, I did a backup using CWM. its on the internal SD card though. So I though if there was some way to access CW recovery mode perhaps I could restore my backup (assuming that my internal SD card isn't toast like from what I understand most people in Canada are experiencing). I haven't tried flashing with ODIN or adb as I don't want to screw things up more. I can however confirm that I put the phone in download mode, connected to PC, and ODIN did recognize it as 0:[COM15]
Just for reference, I've downloaded I9000XXJF3 (I'm 99% sure that is the version it shipped with) from Samfirmware, which contains a few .tar files. (no pit files) Just in case I have to flash with ODIN (never used it before), please let me know if I do need a pit file.
Sorry for the long winded thread, just wanted to provide all info.
Follow up: I attempted to flash I9000XXJF3 with ODIN with PIT512 and re-partition enabled. Flash seemed ok. Phone rebooted as expected, except it went into 2e recovery. So I selected reboot, and now it did its normal boot got to the moving galaxy s screen and then black again. Any suggestions before I try to take it in for service?
Hello, sorry if this has been posted before but the search function is awful.
I have a UK i9000 (SGS) on Vodafone
I had my phone working great with some custom rom, Tayutama edition was my favourite. I dropped the phone on top of my computer, it went haywire and started resetting every few minutes. It would do it if you flicked it or jolted it so I assumed that it was probably a connector in the battery. It was not something I could fix so I prepared to phone so I could send it back as a warranty job. With a lot of work, I managed to return it to a stock firmware 2.1 (via ODIN), I have sucessfully updated it (via ODIN) to XXJPY and I am using kernel 2.6.32.9 hardcore_speedmod-k12r-500hz #6. My Phone is rooted with ch root.
I can get into clockworkmod recovery fine (by installing ROM Manager), i can install a custom rom no problem (it flashes correctly), but it refuses to boot after the flash process is complete. It just gets stuck at the 2nd boot screen (whether this is custom or the standard SGS gleam logo). It does this with various custom rom's and I was wondering what the problem might be. As I said, I could flash custom roms at my leisure until i dropped the phone, now it wont work. I am sure that it is not the phone that is phsyically broken as this sounds likely, but probably my flashing root.
To get the phone working, after flashing a problem rom, I must always use ODIN to flash JM6 with 512 pit and the XX CSC. Then I can flash JPY with ODIN (using an all in one package, so no CSC/modem etc), then root, speedmod kernel etc.
Anyone got any suggestions as to why?
do you have lagfix enabled on your speedmod kernel ? that can cause issues..
also how long are you letting it boot for ?? after a flash my phone can take upto 15mins to get past the boot screen.
last few times i had it disabled i think.
I did a full wipe of the SD card and the internal SD card, then flashed from download with odin successfully. Therefore the lagfix cant have been enabled as I understand it. I have disabled it the proper way (cant remember how) and still unsucessful.
In my experience it normally takes between 3-5 mins for the first boot, I had left it well over 2 hours once (to prove to myself that it was not my lack of patience) with out any change. I have tried taking out the battery, re-inserting it and booting again (for another 2 hours) and no success.
Is there a foolproof way to ensure the lagfix is disabled? Last time I tried a custom rom, I was coming from a totally stock firmware phone. No lagfix applied, no custom kernel, only rooted to allow clockwork recovery to install, should I try it again without rooting the phone, IE just using clockworkmod's update.zip at recovery?
miles
http://www.multiupload.com/PUSOOBQ8K5 download that and flash it with odin using the pit included and CHECK REPARTITION.. then when thats done flash JPY thru odin and then you could flash speedmod kernel thru odin..
when all that is done it will leave you with CWM and in there you can root / unroot You will be un rooted as default, also you can enable lagfix / disable lagfix you will have lagfix disabled by default too.
you are right about lagfix being removed when going back to stock.
so when all that is done your phone will be stock except the kernel, if all that works you should be good to start again..
just one more thing, when you are flashing a rom thru CWM you are choosing install update from sd card >> chose update from sd card right ??? you dont need to be rooted to flash speedmod kernel
Hi everyone, it's my first post here and I'm majorly confused.
What's going on? In a nutshell, I somehow can't fully flash the voodoo kernel.
Let me first describe my setup:
Samsung Galaxy S GT-I9000 with 2.2.1 FROYO.XWJS5 firmware.
For flashing I'm using Odin v1.7 running on a Sony Vaio Win 7 laptop and the Samsung supplied USB cable directly from the USB port, no hub or anything.
With that setup (unflashed kernel, no tweaks) my phone scored between 950 and 1050 points with Quadrant.
I am root
So what did I do?
After reading about the audio improvements that voodoo can make, I wanted to flash the Voodoo kernel from dl.project-voodoo.org/Voodoo-stable-5.4.1-Froyo-2.2.1-GT-I9000-unsigned-update.zip
When I enter recovery mode (up+home+power) all I get is the < 3e > recovery mode which doesn't have any other useful option than run update.zip. When I rename the kernel's zip file to update.zip it of course won't let me run it since it's unsigned.
So I used Odin with dl.project-voodoo.org/Voodoo-stable-5.4.1-Froyo-2.2.1-GT-I9000-odin-pda.tar
I put the phone in download mode (down+home+power), start Odin v1.7, add the .tar as PDA and the only(!) boxes checked are Auto Reboot and F. Reset Time.
I then connect the phone via USB, the box saying something like 0:COM9 turns yellow and I start the flashing.
It seems to flash and reboots, but I get no options and it obviously doesn't convert anything since the boot time is normal. Entering "mount | grep -i ext4" in the terminal doesn't return anything and the Quadrant score stays the same.
Booting into recovery gives the same old < 3e > recovery. BUT the settings->about tells me that I have 2.6.32.9 curio carton #Voodoo_stable_5.4.1 running. So I install the Voodoo Control App 0.8.4 and it seems to work since I can set force analog vol. key and set the analog output level with it.
But seemingly no lag fix. So I enter IRC project-voodoo and ask for help. Among others, phalanger takes care of me. After trying various methods (ROM Manager, Odin, SGS Kernel Flasher) I flashed the speedmod-kernel-k13c-500hz-CWM kernel (dl from xda) with Odin. This worked flawlessly, and I now can boot into CWM recovery.
Here it get's weird. I applied the lagfix (converted to ext4), which worked smoothly. Quadrant scored 1300 points, "mount | grep -i ext4" returned something and the system was snappier. Cool, I thought, let's see what happens if I now run the Voodoo .zip from the CWM recovery, which I did without reverting to rfs. It worked, but it reset my firmware.
So I again flash speedmod with Odin, revert to rfs (data, cache and dbdata are now rfs) and restore a backup from before the lagfix (all this in CWM recovery). The phone is back to "normal", I have all my apps and the speedmod kernel, but of course no ext4! And now Quadrant still scores around 1200 points, how is that possible? I now again used SGS Kernel Flasher to flash the Voodoo Kernel to give me the audio options, what seemingly works, but I'm very confused.
Why can't I run the Voodoo lagfix, why do I still have < 3e > recovery and why isn't the phone running faster?
Davestar2000 said:
Hi everyone, it's my first post here and I'm majorly confused.
What's going on? In a nutshell, I somehow can't fully flash the voodoo kernel.
Let me first describe my setup:
Samsung Galaxy S GT-I9000 with 2.2.1 FROYO.XWJS5 firmware.
For flashing I'm using Odin v1.7 running on a Sony Vaio Win 7 laptop and the Samsung supplied USB cable directly from the USB port, no hub or anything.
With that setup (unflashed kernel, no tweaks) my phone scored between 950 and 1050 points with Quadrant.
I am root
So what did I do?
After reading about the audio improvements that voodoo can make, I wanted to flash the Voodoo kernel from dl.project-voodoo.org/Voodoo-stable-5.4.1-Froyo-2.2.1-GT-I9000-unsigned-update.zip
When I enter recovery mode (up+home+power) all I get is the < 3e > recovery mode which doesn't have any other useful option than run update.zip. When I rename the kernel's zip file to update.zip it of course won't let me run it since it's unsigned.
So I used Odin with dl.project-voodoo.org/Voodoo-stable-5.4.1-Froyo-2.2.1-GT-I9000-odin-pda.tar
I put the phone in download mode (down+home+power), start Odin v1.7, add the .tar as PDA and the only(!) boxes checked are Auto Reboot and F. Reset Time.
I then connect the phone via USB, the box saying something like 0:COM9 turns yellow and I start the flashing.
It seems to flash and reboots, but I get no options and it obviously doesn't convert anything since the boot time is normal. Entering "mount | grep -i ext4" in the terminal doesn't return anything and the Quadrant score stays the same.
Booting into recovery gives the same old < 3e > recovery. BUT the settings->about tells me that I have 2.6.32.9 curio carton #Voodoo_stable_5.4.1 running. So I install the Voodoo Control App 0.8.4 and it seems to work since I can set force analog vol. key and set the analog output level with it.
But seemingly no lag fix. So I enter IRC project-voodoo and ask for help. Among others, phalanger takes care of me. After trying various methods (ROM Manager, Odin, SGS Kernel Flasher) I flashed the speedmod-kernel-k13c-500hz-CWM kernel (dl from xda) with Odin. This worked flawlessly, and I now can boot into CWM recovery.
Here it get's weird. I applied the lagfix (converted to ext4), which worked smoothly. Quadrant scored 1300 points, "mount | grep -i ext4" returned something and the system was snappier. Cool, I thought, let's see what happens if I now run the Voodoo .zip from the CWM recovery, which I did without reverting to rfs. It worked, but it reset my firmware.
So I again flash speedmod with Odin, revert to rfs (data, cache and dbdata are now rfs) and restore a backup from before the lagfix (all this in CWM recovery). The phone is back to "normal", I have all my apps and the speedmod kernel, but of course no ext4! And now Quadrant still scores around 1200 points, how is that possible? I now again used SGS Kernel Flasher to flash the Voodoo Kernel to give me the audio options, what seemingly works, but I'm very confused.
Why can't I run the Voodoo lagfix, why do I still have < 3e > recovery and why isn't the phone running faster?
Click to expand...
Click to collapse
OK for me, you are confusing the hell out of yourself by doing too much at once.
If you are willing, then I would try the darkys resurrection method, I KNOW this will install the kernel and also initiate lagfix, as you indicated, you should hear it talking to you during the long boot.
With you doing so many things at once, not sure where the issue may be, but try the above and see if you get the same results as most people do.
Heh, that's true, too many things at once.
I looked at the Darky's ROM Resurrection Edition tutorial and noticed something. The attached image is from said tutorial, and when I flash a kernel with Odin it says Removed! before Completed...
Is that an issue?
Davestar2000 said:
Heh, that's true, too many things at once.
I looked at the Darky's ROM Resurrection Edition tutorial and noticed something. The attached image is from said tutorial, and when I flash a kernel with Odin it says Removed! before Completed...
Is that an issue?
Click to expand...
Click to collapse
THAT threw me as well, I 'think' all it is referring to is the fact it has 'removed' the serial port interface (USB) when it does the reboot.
The reason for suggesting darkys, is the lagfix thing, if you don't need to use it (I don't, mine is fine without it) then you can also try this one
http://forum.xda-developers.com/showthread.php?t=926399
This fixed me up when I did a boo boo, learnt me a few things in the process as well.
At some point, I will make my own install and instructions, I used to write technical instruction manuals, maybe I need to do some for here LoL
I tried the resurrect ROM, didn't work as planned. Step1 worked fine (basic ROM) but it wouldn't install the CWM recovery with the Voodoo kernel, and as a consequence it of course wouldn't let me run the resurrect.zip in the second step.
I now reverted to JPY (2.2.1) from Samfirmware, installed the speedmod kernel via Odin and will shortly flash the Darky v9.2 from the internal SD. We'll see how that works.
I think the whole trouble is caused by the JS5 bootloader, maybe?!
The fresh JPY scored 1326 points in Quadrant...
Okay, with the CWM recovery (thanks to speedmod kernel) installing the v9.2 Rom from the SD worked fine. I'm now running 2.2.1 I9000XXJPY with the 2.6.32.9 Voodoo_stable_5.4.1 kernel.
Now I again have the problem that I don't have the CWM recovery. When I enter the recovery it's plain old <2e>. What's going on here?!
Davestar2000 said:
Okay, with the CWM recovery (thanks to speedmod kernel) installing the v9.2 Rom from the SD worked fine. I'm now running 2.2.1 I9000XXJPY with the 2.6.32.9 Voodoo_stable_5.4.1 kernel.
Now I again have the problem that I don't have the CWM recovery. When I enter the recovery it's plain old <2e>. What's going on here?!
Click to expand...
Click to collapse
reflash the kernel
Tried that, maybe 20 times, to no avail. Different methods, from withing speedmod CWM recovery, SGS kernel flaser and Odin. Nothing.
Now back to JPY with speedmod and lagfix. Scoring around 1300 with Quadrant. I Don't think I'll flash anything till 2.3 comes out...
Davestar2000 said:
... I Don't think I'll flash anything till 2.3 comes out...
Click to expand...
Click to collapse
Dang: http://forum.xda-developers.com/showthread.php?t=974117
Edit: The irony...had I checked samfirmware maybe an hour later...
My Tab is stuck at GalaxyTab Samsung" boot screen after i try to flash Roto-JMI-v2, before i was running Overcome v1.1.2 rom and [Kernel] [EURO] [1.4ghz OC/UV] MCR EXT4 v12 and it work like a charm. But becurse i deside to sell my TAB i flash back to Roto JMI.
I flash with Odin 1.7 with success, but now it stuck at boot logo.
After that I try many other ROM and flash with Heimdal but no lock.
I have no problem to get download mode, and flash with odin and Heimdal. But I can't get into recovery mode (power+vol up)
I have try almost every solution in the Forum...
What to do next...??
Have you tried flashing kernel only? like the overcome kernel v1.0?
Perhaps that will get you ClockWorkMod Recovery back...and you can go from there.
I try it now, shall i use odin or Helmdall to flash kernel only
With overcome kernel v1.0 it fail in Odin
That's odd. Odin should flash the kernel fine.
Does it give an error? or it just says successful, but you still cannot get into CWM?
It give a error, and I still cannot get into CWM, shall i use a pit to flash
And I have try this....
1.Get a stock rom package (any of Rotohammer's firmwares will work)
2.Get P1_add_hidden.zip attached to this post and extract the P1_add_hidden.pit file
3.Using Odin 1.7, put stock rom (Roto-JME-Full-v4.tar for example) in PDA slot.
4.Put P1_add_hidden.pit in Pit slot
5.Check repartition box
6.Put Tab in download mode by holding Volume Down and Power, connect to the computer, and press start.
7.After this, the Tab will reboot normally. Shut it down and return to download mode.
8.Open Odin 1.7 and reconnect the Tab.
9.In the PDA slot, choose the Overcome Kernel v2.0 tar file for use with Odin. Press start
10.It will flash the kernel then reboot. Upon reboot, you should hear the sexy robot voices informing you of the status of the EXT4 conversion.
11.Once done, the Tab will boot normally. At this point you can load Overcome v1.2.2 rom (or any other Rom of your choosing)
12.NOTE - Overcome 1.2.2 includes v2.0 of the kernel, so no reflashing is required after install.
Hi,
I try this from Samsung stock ROM P1000JK5 and i stuck on the Samsung boot imge. Can i only upgrade to kernel 2 when i have a JM* (Rotohammer rom?)
This is very weerd, other with some god solution
NN1123 said:
This is very weerd, other with some god solution
Click to expand...
Click to collapse
You are correct - he needs to repartition the sd card, using the .pit file because it was formatted to ext4.
Your steps are great! I do them one at a time with a reboot between each one.
sreins said:
Hi,
I try this from Samsung stock ROM P1000JK5 and i stuck on the Samsung boot imge.
Click to expand...
Click to collapse
Oops - if you got your rom from samsung you have a locked bootloader. You can continue to flash those updates, or you can use a patch to remove the lock, then you can continue on.
Can someone please paste the link to the patch?
how about the Verizon gtab...
same thing is happening to me on the galaxy tab from verizon... samsung says to send it.. but i dont want to wait two weeks without my tab... thanks..
Stuck in Bootup Screen
I also have same problem,
I flashed a Rom from "samfirmware" and after it finished it stuck on bootup screen, unable to do recovery mode.
only goes to bootup screen or Dawnload .
can you guys help ?
You gentlemen have a locked bootloader. If you search the tab development forum you will find the solution. A member named Chainfire developed an app you download to your sd card, then install it, then run it, and it will move the offending bootloader. I can't get the link here - google "locked bootloader patch" or posts by Chainfire.
When it is removed, don't flash roms with the samsung kies - all those roms have the locked bootloader.
Stuck in Bootup Screen
thanks
but I can not get the tab to load in order to run any app. it is stuck in boot screen. any suggestion ?
You cannot get into download mode? That is power + volume down.
Do you know of the adb program?
stuck on bootup screen
I havent used ADB before.
any other solution?
rangercaptain said:
You gentlemen have a locked bootloader. If you search the tab development forum you will find the solution. A member named Chainfire developed an app you download to your sd card, then install it, then run it, and it will move the offending bootloader. I can't get the link here - google "locked bootloader patch" or posts by Chainfire.
When it is removed, don't flash roms with the samsung kies - all those roms have the locked bootloader.
Click to expand...
Click to collapse
how install apk boot pacth phone only samsung logo or only enter download mode how install boot patch ?
newbie comes here to learn how to flash kernel.
Hi there,
I ask for help bringing my phone back to life.
I want to make better use of my GT-I9000 and started to install CyanogenMod. I made two separate backups of my files and contacts and flashed the kernel - just to see that the memo notes were not included*.
So I'm stuck in the beginning of installing a custom ROM and want to give a last glimpse at my old phone again. There are many tutorials about how to install the original sotck ROM for the Galaxy S. But I want to be careful not to delete old data and make things worse.
What exact OS was running before?
Model number: GT-I9000
Firmware version: 2.3.6
Kernel version: 2.6.35.7-I9000XXJVU-CL851880 [email protected] #2
Build number: GINGERBREAD.XXJVU
What have you done so far?
I followed the exact procedure as described in the CyanogenMod wiki: wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
Necessary USB drivers are installed; the phone is recognized and I could connect with programs like MyPhoneExplorer
Download recovery: Semaphore_2.7.4.tar
Put the Galaxy S into download mode, connect to PC (Windows 7 64bit)
Run zadig.exe. Replace Driver.
Flash the kernel:
heimdall flash --KERNEL zImage --no-reboot
KERNEL upload successful
Boot into recovery mode
That's where I stopped. Other than that, I didn't make any changes. The data on the SD-card are still the same, I didn't wipe the data or cache partition, I didn't apply an update, I didn't format.
I did flash another kernel though, the zImage from XEU-I9000XXJW4-20120405163836.zip (but not the rest like modem.bin or boot.bin). It didn't bring back the previous OS, so I switched back to the Semaphore 2.7.4
What happens when you turn on the phone?
When I turn on the phone, it shows the initial Galaxy S GT-I9000 boot screen in a boot loop.
I can still boot into download mode
I can boot into recovery mode (Semaphore CWM Recovery v5.0.2.7)
I can then mount the phone as USB storage and browse the data on the PC
What programs can you use?
Heimdall Suite as mentioned in the guide, version 1.4.0
The kernel flash was successful (after capitalizing --kernel)
zadig.exe as mentioned in the guide, it recognizes the phone as SAMSUNG USB Composite Device
Before: Driver sscdbus (v5.0.30.0)
After: WinUSB (v6.0.1.0)
I later tried to connect the then flashed phone to Odin v1.82 and v3.07, but Odin wouldn't recognize any ID:COM. Flashing with Heimdall works though
What do you want to achieve?
I ultimately want to get hold of my memo notes the one way or the other, then just go on with the CyanogenMod installation.
So right now I try to recover the original state that I had before flashing the Semaphore zImage, since most parts of the OS should still be there. I want to boot the old system one more time, copy the memos by hand and go on with a fresh Cyanogen installation.
* Another way would be the backup files. I can't find the memos, there is no /dbdata/databases/com.sec.android.app.memo or *.vnt file in the backup. I backed up External storage, Memory card and System storage in case you have another idea about the location.
TL;DR
I flashed Semaphore on my Galaxy S and want to boot the original OS again.
What is the problem?
There are some good tutorials on how to restore the original stock ROM for the GT-I9000.
But I don't know what part of which ROM I have to flash at the state I am in right now, without making it worse. Also, I can use Heimdall only.
My guess is I just have to flash the right zImage, but the one I tried (from XEU-I9000XXJW4-20120405163836.zip) did not work.