Related
So... believe me, I know I'm an idiot for doing this. When trying to install Voodoo for official 2.2.1 I accidentally flashed the 5.5 for GT-I9000 that I forgot to delete when I was first starting to mess around with attempting to install voodoo, before doing much research.
When I tried to reboot it just sat at the I9000 boot screen forever and started to get hot so I pulled the battery.
I rebooted and came to a screen with lots of error messages from CWM on the bottom of the screen and the stock recovery options at the top.
When I try to reboot it just sits at the I9000 boot screen forever.
I tried reflashing 2.2.1 with ODIN as described in this thread http://forum.xda-developers.com/showthread.php?t=881064 That doesn't seem to get very far.
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> All threads complete. (succeed 0 / failed 1)
Did I completely brick my phone or is there some way to get it working again? really desperate here... I don't want to have to go back to my RAZR2 for another year until I can get an upgrade.
Thanks in advance to any golden saint that can help me out!
Never mind, I got ODIN to work (I hastily left out the step loading the tar file) and all seems to be working fine now. Albeit minus a hundred apps or so...
I apologize to anybody who spent time reading this thread.
Fidelis83 said:
Never mind, I got ODIN to work (I hastily left out the step loading the tar file) and all seems to be working fine now. Albeit minus a hundred apps or so...
I apologize to anybody who spent time reading this thread.
Click to expand...
Click to collapse
haha glad you got it working. Hope you had titanium for your apps! If not lesson learned! I thought I trashed my phone a few times thank the Devs for Odin! And boot camp for my mac...haha
droidzach said:
haha glad you got it working. Hope you had titanium for your apps! If not lesson learned! I thought I trashed my phone a few times thank the Devs for Odin! And boot camp for my mac...haha
Click to expand...
Click to collapse
Yep, got Titanium first thing after I rooted.
A million thanks to phidelt82 for the ODIN writeup!
I also flashed Voodoo5.5 to my Epic! Please Help!
I obviously didn't do my homework and flashed the latest voodoo kernel to my epic. I'm running a Rooted Epic w/ Fyoyo and have clockwork mod. So here's how it went: The kernel flashed (said it installed )and phone returtned to clockwork mod. I rebooted and phone stuck in a boot loop just as yours was. I have to pull the battery to shut the phone off. I can get into clockwork mod....where do I go from here? I have the phone backed up with titanium, which is great if I can get it to boot up. Please Help. Thanks.
Cbisk said:
I obviously didn't do my homework and flashed the latest voodoo kernel to my epic. I'm running a Rooted Epic w/ Fyoyo and have clockwork mod. So here's how it went: The kernel flashed (said it installed )and phone returtned to clockwork mod. I rebooted and phone stuck in a boot loop just as yours was. I have to pull the battery to shut the phone off. I can get into clockwork mod....where do I go from here? I have the phone backed up with titanium, which is great if I can get it to boot up. Please Help. Thanks.
Click to expand...
Click to collapse
Flash the correct kernel for your phone, that will fix you up. If you need any more help with that, you should post in the epic forum - since this is the mesmerize forum .
Fidelis83 said:
So... believe me, I know I'm an idiot for doing this. When trying to install Voodoo for official 2.2.1 I accidentally flashed the 5.5 for GT-I9000 that I forgot to delete when I was first starting to mess around with attempting to install voodoo, before doing much research.
When I tried to reboot it just sat at the I9000 boot screen forever and started to get hot so I pulled the battery.
Click to expand...
Click to collapse
You were even then a step ahead of me. Until I read this thread, I didn't even know that was the wrong Voodoo, in spite of it saying GT-I9000, I just figured that was the default behavior of Voodoo. XD I would have gone home tonight, maybe tomorrow, and kept beating my head against it, wondering why it wasn't working. XD
The Newbie Guide from bdemartino doesn't seem to specify---which version of Voodoo did you go with, and where did you get it from? The only Froyo Voodoo kernels I can find on the Project-Voodoo site are the 5.5 ones for the GT-I9000.
If you are on an i500 (fascinate, mesmerize, or showcase) you can flash any of the EC10 based kernels in the fascinate forum here on xda. Just remember that if you are on a touchwiz based rom (stock, PnP, etc) you need to make sure you use a touchwiz compatible kernel. Off you are running AOSP you must use an AOSP compatible kernel.
Sent from my voodoo froyo Mesmerize
Like the OP, I too flashed the wrong Voodoo kernel, the one for the GT-I9000. When I flashed it, I got the robot voice, and then it wouldn't complete the boot process.
So I panicked. I followed the instructions in the post titled "Files to get your Mesmerize back to stock 2.1 and 2.2.1", with the exception of disabling lagfix.
Everything seems to be working okay now, with one exception. I can't get the correct Voodoo lagfix working. I can get the kernel installed, but I never get the robot voice for the conversion.
I have BLN working so it seems like voodoo is installed, but my quadrant scores seem to indicate that it is not.
Help?
If that were me, and I'm certainly no expert, I'd start by taking a Titanium backup of all your apps. Next I'd boot into recovery and disable lagfix if you still can; even if the actual lagfix itself isn't working, just turn the setting off. Then I'd try to flash the stock 2.1 (or 2.2.1 as you prefer) with stock kernel and stock recovery, to treat it like a brand new phone (not sure if you did that or grabbed the stock + custom recovery). Then, just start the customization process over from scratch. Finally, once you've got it tweaked, load up Titanium again and bring over all your apps.
That is IF I understand it all correctly; if I'm telling him wrong, someone please chime in and correct, or confirm. XD (jrusch, I might wait till someone can confirm or deny my instructions, but I figured I'd least give you some food for thought)
I just can't get it to work. I disabled lagfix (even though it didn't seem to be running), and then I used Odin to flash the stock 2.2.1.
I tried a few Voodoo kernels (EC10_ulv_voodoo.zip, TW_kernel-0327-2.zip, and ec10_voodoo.zip) all with the same results. They install, I get the goofy startup screen with the flashing "android" in the middle, but no robot voice announcing the conversion process. After installing the Voodoo kernel I verify it creates the Voodoo folder in the root of the phone's memory and on the sdcard and no disable_lagfix folder exists.
jrusch said:
I just can't get it to work. I disabled lagfix (even though it didn't seem to be running), and then I used Odin to flash the stock 2.2.1.
I tried a few Voodoo kernels (EC10_ulv_voodoo.zip, TW_kernel-0327-2.zip, and ec10_voodoo.zip) all with the same results. They install, I get the goofy startup screen with the flashing "android" in the middle, but no robot voice announcing the conversion process. After installing the Voodoo kernel I verify it creates the Voodoo folder in the root of the phone's memory and on the sdcard and no disable_lagfix folder exists.
Click to expand...
Click to collapse
I'm pretty sure your system is either still in EXT4 or it thinks it is, and that's why disabling voodoo through CWM isn't doing anything for you - what has worked for me in the past is injecting the empty file named "disable-lagfix" into the clockwork folder on your SD Card, then rebooting. It should then disable it, then I would do a clean odin flash to make sure everything is working properly, then you should be able to pick up where you left off (adding voodoo, custom ROM etc.)
This has happened to me in the past when I've forgotten to disable lagfix and tried using odin to go to stock (this returns your kernel to stock and gives you issues because the internal file system is still formatted in EXT4 but the odin flash tries with the stock RFS format, and that's where the problem occurs.)
I used Root Explorer to create a new file named "disable-lagfix" in the clockework folder and rebooted. I then did a clean odin flash, etc.
I still can't get voodoo lagfix to work. When I boot to recovery (CwM Voodoo Lagfix Recovery v2.5.1.x) the voodoo menu shows:
Voodoo lagfix is actually: disabled
next boot: enabled
But at the next boot it doesn't do the conversion.
jrusch said:
I used Root Explorer to create a new file named "disable-lagfix" in the clockework folder and rebooted. I then did a clean odin flash, etc.
I still can't get voodoo lagfix to work. When I boot to recovery (CwM Voodoo Lagfix Recovery v2.5.1.x) the voodoo menu shows:
Voodoo lagfix is actually: disabled
next boot: enabled
But at the next boot it doesn't do the conversion.
Click to expand...
Click to collapse
I don't know if creating the file with root explorer will work, I had to create an empty file in my linux box and renamed to "disable-lagfix" (no quotes) once that file is in the clockwork folder and you reboot you should hear the sound of it being disabled - if you don't hear the voice then something is wrong with the file or where you put it.
right now you're stuck with it enabled, if you have the voodoo control app you can check to see if using the toggle in that app will work, but I'm guessing you're going to have to do it the manual way as stated above.
I still can't get it to work. I created the "disable-lagfix" file on a linux box and then copied the file to the sd card into the clockwork folder. I still can't get lagfix to disable/enable.
When I boot a voodoo_log.txt file is created, does this give any clues:
2011-04-12 13:03:18 model not detected
2011-04-12 13:03:18 manage fat.format in /sbin
2011-04-12 13:03:18 fat.format wrapper installed in /sbin
2011-04-12 13:03:18 fat.format renamed to fat.format.real & symlink created to fat.format_wrapper.sh
2011-04-12 13:03:18 running init !
I was trying to install the Voodoo kernel. I had the stock+froyo one installed just fine using Odin3. Then I went to their main page, and saw the 5.5 version. Titled Voodoo lagfix for Froyo stable. I used Odin to install it from the Download Mode. everything went fine till the voice said something about not enough space on the partition.
Then the T-Mobile pink screen appears, then the Samsung Vibrant S screen, then it goes black. Nothing happens after that except the bottom lights come on if I touch them. Odin3 still sees my phone as plugged in. I have a really hard time trying to get into the Recovery screen, but when I do, I have no idea what to do once I'm there.
I've tried using Odin3+Download Mode to reinstall the stock+voodoo-froyo-t959-UVKA6.tar which worked fine the first time, but I can never get back to the main home screen.
Any advice would be much appreciated, I'll be online for the next few hours refreshing this page, so my responses should be fairly quick. Thank you in advance.
Update: I tried searching for solutions, came across a post in the samsungvibrant.c o m forums with a youtube video.
I followed the instructions, everything worked as intended, until after the S screen, I just got a black screen. Never went to the home screen. This where I am currently at.
rtekbillabong said:
I was trying to install the Voodoo kernel. I had the stock+froyo one installed just fine using Odin3. Then I went to their main page, and saw the 5.5 version. Titled Voodoo lagfix for Froyo stable. I used Odin to install it from the Download Mode. everything went fine till the voice said something about not enough space on the partition.
Then the T-Mobile pink screen appears, then the Samsung Vibrant S screen, then it goes black. Nothing happens after that except the bottom lights come on if I touch them. Odin3 still sees my phone as plugged in. I have a really hard time trying to get into the Recovery screen, but when I do, I have no idea what to do once I'm there.
I've tried using Odin3+Download Mode to reinstall the stock+voodoo-froyo-t959-UVKA6.tar which worked fine the first time, but I can never get back to the main home screen.
Any advice would be much appreciated, I'll be online for the next few hours refreshing this page, so my responses should be fairly quick. Thank you in advance.
Update: I tried searching for solutions, came across a post in the samsungvibrant.c o m forums with a youtube video.
I followed the instructions, everything worked as intended, until after the S screen, I just got a black screen. Never went to the home screen. This where I am currently at.
Click to expand...
Click to collapse
WTF? Do you even have a Mes/Showcase?
Sounds like someone didn't check which forum they were in after they Googled.
You probably need to look around in this forum instead.
To all i500 users.... don't go to the project voodoo site looking for voodoo kernels. Those are generic or made just for OTHER phones. Any and all voodoo kernels you flash should be found either in this forum or the fascinate forum. This goes back to the old DO NOT FLASH PACKAGES FROM OTHER PHONES…
just trying to be helpful.
Sent from my SCH-I500 using XDA App
I have a question regarding Voodoo flashing methods, specifically relating to Odin & CWM. The Voodoo website (which contains the INCORRECT kernels for our I500s, I DID gather that already ) recommends placing the file directly onto the SD card, renaming it "update.zip" and using stock recovery to flash it. I have noticed that this sentiment is not reflected here are all - everyone seems to recommend using CWM Recovery and/or flashing everything with Odin. What gives?
If someone with a stock EC10 ROM just wanted the benefits of the Voodoo conversion, and isn't really interested in flashing a new ROM, is it really necessary to install CWM and Odin, or will the stock stuff work? From what I've gathered, this is all the OP was really trying to do from the start.
BTW, yeah, it's my first post, and yes I've been reading a lot, but definitely not nearly enough. I'm very impressed with the level of assistance forum members are willing to provide, but I, like many others, want to make sure I have it 100% correct before I turn my phone into a very fancy, very worthless piece of silicon, glass and plastic. Thanks, everybody!
Hello, please let me know what I'm doing wrong, I've looked exhaustively for a solution to my problem on my own but I can't seem to find one:
1.) Rooted my G2x
2.) Installed Clockwork ROM Manager
3.) Copied two separate Gingerbread ROMs, Cyanogen 7, and Modaco into Root Folder (no sd card, just phone storage)
4.) Tried flashing both Roms multiple times with Rom Manager by both rebooting into recovery and installing from .zip (this option won't display either of the ROMs, just the log file folder.) I have tried installing .zip from SD in ROM Manager, and the phone just reboots as if nothing has happened.
*I believe ROM Manager does have difficulty mounting the phone storage, as it takes a full twenty count before attempting to flash the ROM.
**I don't know if this helps, but I have not received the OTA Gingerbread update from T-Mobile (even when my phone was unrooted), and when I prompt for the OTA update, I receive a "connection error" message. The LG Updater Tool indicates that my phone is "up to date" when it clearly, is Froyo 2.2.2.
Any help would be greatly appreciated with this issue guys, I usually scour forums for answers to my questions or fumble my way through it myself, but this has really sucked out lots of hours from my life.
No external sd card
You have to have a external to flash roms if im not mistaken
when you install recovery there are 2 choices external storage and internal storage if you dont have an sdcard reinstall clockwork using the internal option. that should do the trick for you.
eagle1967 said:
when you install recovery there are 2 choices external storage and internal storage if you dont have an sdcard reinstall clockwork using the internal option. that should do the trick for you.
Click to expand...
Click to collapse
I am going to try with an external SD card. Also, I am unsure of how to flash it to use internal storage, I checked the settings through ROM manager and couldn't find out how to do it. Is this something I access during Recovery mode? Thanks for the suggestions so far guys, I'll definitely post with results.
pathmarkpolice said:
Hello, please let me know what I'm doing wrong, I've looked exhaustively for a solution to my problem on my own but I can't seem to find one:
1.) Rooted my G2x
2.) Installed Clockwork ROM Manager
3.) Copied two separate Gingerbread ROMs, Cyanogen 7, and Modaco into Root Folder (no sd card, just phone storage)
4.) Tried flashing both Roms multiple times with Rom Manager by both rebooting into recovery and installing from .zip (this option won't display either of the ROMs, just the log file folder.) I have tried installing .zip from SD in ROM Manager, and the phone just reboots as if nothing has happened.
*I believe ROM Manager does have difficulty mounting the phone storage, as it takes a full twenty count before attempting to flash the ROM.
**I don't know if this helps, but I have not received the OTA Gingerbread update from T-Mobile (even when my phone was unrooted), and when I prompt for the OTA update, I receive a "connection error" message. The LG Updater Tool indicates that my phone is "up to date" when it clearly, is Froyo 2.2.2.
Any help would be greatly appreciated with this issue guys, I usually scour forums for answers to my questions or fumble my way through it myself, but this has really sucked out lots of hours from my life.
Click to expand...
Click to collapse
I can't quite tell if you used rom manager to flash CWM, but if you did then make sure to use nvflash. I don't know if it could cause things not to work, but it's the only way to guarantee you can always get into recovery. As people have said above, try to use external, although I hadn't read anything about problems with using internal to flash roms, at least if nvflash has been used.
I'll assume you've already heard of wiping/factory reset and all that since you joined a few years back, but make sure to do it when going to a new rom. As for the update issues, I would say just restore stock froyo, maybe from the nandroid tgagunman created if something is wrong with yours, factory reset it just to be careful, unroot using superoneclick, flash stock recovery using tgagunman's one click recovery flasher, and make sure usb drivers are up to date.
If you really can't get the new baseband and roms working after all that... tell t-mobile you can't get the update and ask for a new one haha.
Thanks Guys...
Danish, Eagle, Water, thanks a lot to all of you guys. I was able to flash a new ROM using an External SD card, I'm still having problems finding a ROM that is stable and is compatible with all of the apps I want to use (I'm currently having difficulty installing Tooyoou on the Bionix ROM I downloaded, which is otherwise AWESOME). I mean, it's not that big of a deal, but I'd like to get my extra $2.50 a month from the program.
Oh and NV Flash...
NV Flash helped me when I messed up my G2x's ability to boot into recovery with a Cyanogenmod 7 ROM build. Here's a link to a guide that helped immensely for anyone who finds themselves in this thread with a similar issue:
http://forum.xda-developers.com/showthread.php?t=1056847
Hi need a bit of help with this one if possible.
start the top..
went to flash leedroids rom..flashed boot image but forgot to pull rom over.
so had various issues getting over in the end had to mess around with recoverys and totally wipe my sd for it to be recognized.
so i solved all this then..now the issue is..of everything i push over..only one rom boots up and installs fine..and that is a cm9 test without sd mounting..so it solves nothing.
any ideas of how to get a rom on there where i can mount the sd..download a rom and put it on..
ill be honest..htc+internal sd card=not happy
ive pushed leedroids..virtuous..utbs rom but nothing.
i tried aokp but it didnt even push.
with these also some get corrupted by a protocol failure..
many questions. currently has cm9 on..but no mounting..so great
Did you already try a factory reset after flashing the stock recovery (e.g. from MoDaCo)?
-
Hi rootrider, yeah i followed a post i found..
basically i used the one click toolkit to flash the stock recovery..then cleared storage and all data etc.then installed clockwork back..it doesnt like the working roms though
cm9 is the only one i can boot up..at least it sees the sd card again in clockwork though
Had your problem as well... I don't remember exactly what I did to get out among many other things (sh..).
Had some trouble as well flashing stock recovery with the one click tool kit. It didn't work as expected. So I did it with adb. Just keep on trying, there is a way out.
-
My next course of action is, to flash the stock recovery, clear everything,reinstall clockwork then install aokp..if its something with the type of rom.maybe that will work..i can mount..get a rom on the sd and resume business as usual..
debatebale whether itll work lol
If this doesn't help get Thor's hammer and flash your appropriate RUU (again).
Easiest method would be to run an RUU and start over again. I see your vodafone UK so try this one
http://dl.dropbox.com/u/69014495/RU..._2_10.23.31501S.10L_release_258386_signed.exe
It also includes the new radio too !
Just relock bootloader before running it, After its finished unlock and fastboot flash cwm..
easy peasy !!
--
thanks people, im running leedroids rom now, seemed my issue was is after pushing the file over i just tried to install immediatley..after a couple of reboots just for the hell of it,untouchables rom started installing...phew..
sadly all my sd contents have gone..very dissapointed with the sd card business!
still least its working again!
thankfully azzle didnt need to go back to ruu
Aye, captain. Glad to read this.
I don't know what to do next, and I need my phone. I can answer any questions, but I wouldn't know what to start with. Can someone help??
Quick questions to answer:
1. What Rom were you on prior to flashing?
2. What Rom were you flashing to?
3. What do you see on your screen?
4. Do button presses give any reaction?
1. http://forum.xda-developers.com/showthread.php?t=1136128 v5.0, it's Gingerbread.
2. I was flashing to CM7, but it didn't flash, so I did what was probably a mistake and went straight for http://forum.xda-developers.com/showthread.php?t=1625619&page=1.
3. I see "DevilKernel" Samsung Galaxy S.
4. If I hold down the volume and power buttons, the DevilKernal boot screen will flash. If I keep the power button held down it resets, if I don't it just flashes and nothing else.
By the way, thanks.
Ok, here's what happened:
The first bootloop you were seeing with CM7 is actually a normal occurrence. You usually have to flash CM-based roms twice to get them to "take" (the first time sets up MTD over BML, the second time installs the rom).
What you're seeing now is the devil kernel trying to load up the CM9-based system, but not having all the parts in place.
Thankfully, you're not in that bad of a place. The easiest thing to do right now is to grab an Odin- or Heimdall-based one click Gingerbread stock package without bootloaders. There's a sticky in the Development section that has them, or you can grab the one in my signature.
Flash the one-click, go to recovery, and flash either CM7 twice or TWICS twice.
That should fix you up.
When I tried flashing the CM7, it said it failed. I'm not sure what went wrong. The TWICS I planned on flashing twice, but it got stuck.
Hard to say - it could be something as simple as a bad download of the flash file.
But you think if I Odin it and try TWICS again it'll work?
It should. Doing the Odin one-click will reset everything back to a factory state, which should remove all the obstacles that would normally stand in the way of a successful installation.
Hey man, for that ROM, this theme will work, right?
http://forum.xda-developers.com/showthread.php?t=1095911
I don't know anything about themes. Or this, apparently. I also got into Recovery and installed it twice, I don't really know what's going on.
So you're now fully set up with TWICS, or you're saying that it's still misbehaving?
Also, that theme should work - I had a CM7 theme that I was able to use with a CM9 rom's theme chooser. Wasn't 100%, but it generally worked.
I'm not sure WHAT is going on. The ROM seems to be working fine, I am reinstalling my apps from Titanium Backup and a "Low on space" popup is here, but that makes no sense since it's the same phone, it's a smaller ROM, and a 32gig SD Card. I also just got a text message that was "rejected due to low space".
What is going on??
It seems my phone always is unable to continue once Super Monkey Ball 2 tries to be backed up.
Look around in the cm7 thread for the dbdata full issue. I think there were some suggestions for how to deal with it in there.
Hello all,
Okay, I admit that I am gonna get a lot of "use the search tool first" replies, but please hear me out. I have done my fair share of searching. Its not that I haven't found anything, its just the things I found are useless for this SGS 4G. I really wanted to install Cyanogen Mo on the SGS (its not actually mine, a friend asked me to do it since he saw my old SGS GT-I9000 running CM).
I am gonna try and give a detailed report . The phone was originally from T-Mobile and now unlocked permanently. Its running firmware version 2.3.3 that I installed just recently. I found out that I can't install CWM on the stock kernel or bootloader or whatever and I needed a new of the thing. So I went on searching and searching....found a handful of help but none work. Every method breaks at some point and I go to the "firmware update failed" thing on the phone, which I then install 2.3.3 again using ODIN and try another method. I have tried a lot of things. Hemidall, ODIN, SuperOneClick, and a lot of gibbrish-sounding methods. None work. I am now running 2.3.3. Here are some infos:
ABOUT PHONE:
Model Number: SGH-T959V
Firmware Version: 2.3.3
Baseband Version: T959VUVKF1
Kernel Version: 2.6.35.7-T959VUVKF1-CL270364
Build Number: GINGERBREAD.VUVKF1
The files I used to flash to 2.3.3 using ODIN v1.85:
PIT: Hawk_Sidekick_VibrantPlus_831.pit
PDA: CODE_T959VUVKF1_CL270364_REV00_user_low_noship.tar.md5
PHONE: T959VUVKF1-Phone-CL1020302.tar.md5
CSC: SGH-T959V-CSC-TMB-VIBRANTP.tar.md5
I hope the above infos are enough. So, can anyone help me and point me to the right direction on how to install CWM and then install CM10 or 9 on my friends SGS 4G?
Thanks,
Tamrat
Hmmm, an interesting set of binaries, ones that don't ring a bell with me. I'm used to seeing T959VUVKJ6.
Where did you find those? Half curiosity, half trying to understand the problem, half since much of the "old" images for the phones got lost when Multiupload and what have you were shut down.
For the SGS4G, the kernel, root file system, and recovery file system are all in "boot.img" -- flash one, you flash them all. They can be flashed through Odin (assuming you really like Windows), heimdall (multi-platform), through recovery, or from a root command line (for the adventurous only).
I would say the most robust way to get where you need to be would be to use Lumin's guide to make sure you've got a viable Gingerbread set-up going, then flash something reliable to get you to MTD, like TeamAcid's CM9.
From there, you should know that some of the KK ROMs use slightly different MTD partitioning and aren't a "just flash this ROM and keep your data" kind of thing.
jeffsf said:
Hmmm, an interesting set of binaries, ones that don't ring a bell with me. I'm used to seeing T959VUVKJ6.
Where did you find those? Half curiosity, half trying to understand the problem, half since much of the "old" images for the phones got lost when Multiupload and what have you were shut down.
Click to expand...
Click to collapse
A long day Googling... and then a site turned up. One thing I forgot to mention was, before I installed this firmware, I had to use the "remove battery->plug usb->press the button combos->insert the battery" to enter download mode, but now I juts have to press vol down and power button.
Thanks for the reply,
Failure again
UPDATE:::
I tried to update to 2.3.6 as the guide suggests and I also wanted a clean stock OS in case the old one was not. But once again updating to 2.3.6 has been a pain. Kies Mini recognizes the phone but it doesn't recognize the firmware running on the phone. And also, firmware update is impossible since the button is greyed out.
I googled again and found the official 2.3.6 firmware for the phone (file name: T959VUVKJ6-REV00-home-low-CL694130.tar.md5) and tried flashing it using ODIN; absolutely no luck. It fails at the stage which says Slb.bin. Restarting the phone after that gives a "firmware upgrade failure" display. Only way to wake up the phone is to flash the previous OS back.
I am really confused here.
*********************EDIT***************
Some how, after like 10 retires and fiddling with ODIN, it finally flashed 2.3.6 to the SGS 4G. Still, fingers crossed.
*********************EDIT 2***************
Finally, its all working fine now. Thank you @jeffsf, thank you very much.
F*****************K
forgot an important step and now my IEMI number is gone........
do i throw the phone now, or is there any other way???
Don't throw your phone away! How do you know that you have "no IMEI" on your phone? We'll go from there.
Hopefully, you've backed up your data before starting to play around with ROMS. If so just load your backed up efs folder onto your storage & use Root Explorer to drop it over your existing one , it will overwrite your imei file & you will be good as new.
========================================================================================
I'm also in need of help, I have been running SlimSaber since last weekend, was wanting to try out Beanstalk. First full wipe, install & reboot wipe again, reinstall etc as per Dao's OP, but after the first install, it won't boot past the kernel splash. Tried again with same result. Decided to click it back to stock & start over, using Gremlin Remover (odin). Then saw that others were having similar issue so I tried to load in build from April1st.
But now it only boots back into recovery, won't boot to the OS ( everything indicated install was complete & no errors.)
1 clicked back again & just tried to put SlimSaber back on again, but have the same problem, will only boot into recovery.
I had to first load CM9 to get CWM 6.xx so I could install kk using TWRP
What am I not doing correctly? Thanks for any suggestions.
Flash kernel
Reboot recovery
Wipe all partitions
(Reboot recovery for good measure and wipe again if paranoid)
Install
Boot
If that doesn't do it, it is likely ROM or hardware.
---
Posted from whatever phone booted today
Since this is running GB VUVKG4, could you recommend a kernel that would work & get me to TWRP (or CWM 5.xx+)?
Either the Team Acid CM9 or Hefe Kernel should work.
---
Posted from whatever phone booted today