Related
Ok, so i have had a samsung captivate since last summer. I just did the official froyo update the other day and it was successful with kies mini. I then decided to root it using super1click which also worked successfully. I have superuser, titanium backup with busybox installed, and super manager and terminal emulator. I also successfully got clockworkmod flashed and working.
My problem is that ive got the new cognition rom on my internal sd card, but when i try to flash it with cwm, i get the 3e recovery failure message. Ive been reading various sites today on how to fix this problem, but every site seems to tell me something different. I ask this question here, because it seems to be the most knowledgeable site to go to.
How do i get my rooted captivate, with all the above installed and running, to allow me to flash a new rom and possible a new kernal down the road? Im about to go insane trying to decipher through all the info all the different sites have said. Sorry to write such a novel on a tired subject, but im going crazy. Any help will be GREATLY appreciated. Thanks.
trontheman said:
Ok, so i have had a samsung captivate since last summer. I just did the official froyo update the other day and it was successful with kies mini. I then decided to root it using super1click which also worked successfully. I have superuser, titanium backup with busybox installed, and super manager and terminal emulator. I also successfully got clockworkmod flashed and working.
My problem is that ive got the new cognition rom on my internal sd card, but when i try to flash it with cwm, i get the 3e recovery failure message. Ive been reading various sites today on how to fix this problem, but every site seems to tell me something different. I ask this question here, because it seems to be the most knowledgeable site to go to.
How do i get my rooted captivate, with all the above installed and running, to allow me to flash a new rom and possible a new kernal down the road? Im about to go insane trying to decipher through all the info all the different sites have said. Sorry to write such a novel on a tired subject, but im going crazy. Any help will be GREATLY appreciated. Thanks.
Click to expand...
Click to collapse
If you would have done a search here then you would have found that you need to do one of 2 things.
1. Flash back to 2.1
2. Replace the 3e recovery with one that doesnt check for the sig.
I dont know how to replace the 3e recovery. I think ill go with flashing back to 2.1. Once i dl Odin and flash back to 2.1, then i can flash a new rom or a new kernel? Will it undo everything i've done so far? Thanks for the help.
trontheman said:
I dont know how to replace the 3e recovery. I think ill go with flashing back to 2.1. Once i dl Odin and flash back to 2.1, then i can flash a new rom or a new kernel? Will it undo everything i've done so far? Thanks for the help.
Click to expand...
Click to collapse
Here is a link to the replacement recovery.
Make sure you have the right odin and that your 3 button works right.
Yesh doing this will wipe out everything. Make sure to back up. Do not back up system data at all as when you restore it, it can lead to major issues. Once done with a custom rom it will be wiped clean. You will have to redo contacts, email, and all other settings
Thanks. Would it be okay to just flash a new kernel like speedmod kernal and just use the stock rom? Is that possible to do while im on rooted 2.2? I like the rom just fine, i just want it faster mainly. Thanks again.
trontheman said:
Thanks. Would it be okay to just flash a new kernel like speedmod kernal and just use the stock rom? Is that possible to do while im on rooted 2.2? I like the rom just fine, i just want it faster mainly. Thanks again.
Click to expand...
Click to collapse
To be honest I am not sure. I only had the stock on for a few hours as it was just not that great compared to the 2.2.1 rom that I have been used to running. I need BT voice dial and the added exchange options so 2.2 was not really for me. If you want a stock feel but faster then I would go with COG or one of the other roms based on the kb1 rom.
So I've come to the conclusion that I should just flash back to 2.1 and go from there. I have odin downloaded, but I'm not certain how to use it. Do you guys think I should flash a custom rom from stock, or just flash a kernel with lag fix and delete the bloatware? Thanks.
first flash 2.1 stock to get rid of the damn 3e. custom roms dont replace that always. also most custom roms dont flash with odin.
get a stock rom. read the instructions, flash
trontheman said:
So I've come to the conclusion that I should just flash back to 2.1 and go from there. I have odin downloaded, but I'm not certain how to use it. Do you guys think I should flash a custom rom from stock, or just flash a kernel with lag fix and delete the bloatware? Thanks.
Click to expand...
Click to collapse
If you are getting .zip signature errors when trying to flash a rom (because you are using 3e recovery) you will not be able to flash a kernel.
Supercurio did make a KB1 kernel that is installable via Odin. If you install that, you will also get CWM recovery. Then you can flash anything you want.
Either way you will need an Odin program. Either Odin One Click to flash back to stock 2.1 or Odin v1.7 to flash the Supercurio KB1 Kernel .tar file.
trontheman said:
Thanks. Would it be okay to just flash a new kernel like speedmod kernal and just use the stock rom? Is that possible to do while im on rooted 2.2? I like the rom just fine, i just want it faster mainly. Thanks again.
Click to expand...
Click to collapse
Correct me if i'm wrong but I think the speedmod kernal is i9000 based which would cause a major headache/bootloop on the stock rom.
Sent from my SAMSUNG-SGH-I897 using XDA App
Johnnie5000 said:
Correct me if i'm wrong but I think the speedmod kernal is i9000 based which would cause a major headache/bootloop on the stock rom.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
....it works fine on stock 2.2, as does any other 2.2/2.2.1 kernel
Pirateghost said:
....it works fine on stock 2.2, as does any other 2.2/2.2.1 kernel
Click to expand...
Click to collapse
The problem is, the OP has no idea what he's doing. It sounds like he's wanting to flash to 2.1, then add a I9000 kernel. Since he's all over the place, it's hard to decipher what he's thinking.
To the OP. I'd HIGHLY suggest you look for the stickied "how to" video's by Connexxion. They will tell you what you need to do and show you EXACTLY how to do it. Invaluable info for the noobs.
Here is the link your looking for, download the installer zip file at the bottom of the first post. Extract to your fancy, use the install.bat file once extracted. Be sure to have the phone connect to the pc (DO NOT MOUNT) and have USB Debugging on.
Modded 3e recovery that works like 2e
trontheman said:
Ok, so i have had a samsung captivate since last summer. I just did the official froyo update the other day and it was successful with kies mini. I then decided to root it using super1click which also worked successfully. I have superuser, titanium backup with busybox installed, and super manager and terminal emulator. I also successfully got clockworkmod flashed and working.
My problem is that ive got the new cognition rom on my internal sd card, but when i try to flash it with cwm, i get the 3e recovery failure message. Ive been reading various sites today on how to fix this problem, but every site seems to tell me something different. I ask this question here, because it seems to be the most knowledgeable site to go to.
How do i get my rooted captivate, with all the above installed and running, to allow me to flash a new rom and possible a new kernal down the road? Im about to go insane trying to decipher through all the info all the different sites have said. Sorry to write such a novel on a tired subject, but im going crazy. Any help will be GREATLY appreciated. Thanks.
Click to expand...
Click to collapse
I am wanting to flash back to 2.1 and go from there. I have the drivers installed and I have odin downloaded. I tried it last night, but I couldn't get it to work. I got it to download mode, but still nothing. What could the problem be? Thanks.
I tried odin one click again today, but still nothing. All i want to do is flash back to 2.1, root, then flash a rom or custom kernel. Im losing my mind, any more help is greatly appreciated. Thanks.
Bump. Thanks.
trontheman said:
I tried odin one click again today, but still nothing. All i want to do is flash back to 2.1, root, then flash a rom or custom kernel. Im losing my mind, any more help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
ok no need to flash 2.1
get neldars kernel flashing app from the market
get a kernel for froyo without 3e recovery in the dev section. this one is great
http://forum.xda-developers.com/attachment.php?attachmentid=547852&d=1300708475
use neldars app (edit) "sgs kernel flasher" or something to that effect. to flash this kernel
then flash cognition
you can also use odin3 but not the oneclick downloader without the .pit file and flash the same kernel placed in the pda slot.
when you installed keis mini, it installed new WRONG drivers (for odin)
reinstall the original other drivers.
BUT. in your OP all you wanted was to be able to flash COG or something.
ALL you have to do is fix your 3e recovery, SEVERAL people including myself have told you how to fix it. then CWM will work! you dont need a computer to fix 3e if you have root explorer (google it $) .
if you are going to flash a custom rom anyway dont bother going back to 2.1.
if you are going to stay stock, 2.2 is better anyway. (aside from 3e but staying stock dont matter)
you can also use odin3 but not the oneclick downloader without the .pit file and the same kernel placed in the pda slot.
Click to expand...
Click to collapse
@ dani - dude read the thread. odin doesn't recognize his phone.!! try to catch up before butting in...
well that doesn't make my whole post irrelivent. if he is rooted and has busy box he can use neldars kernel flasher. sorry if i over looked something.
Ok, well i got the aio toolbox, and i flashed back to stock. Now im running 2.1-update1. How do i go about rooting now? I cant seem to find a root file. Thanks.
Sorry for dumb question.. as I am really novice for installing custom rom..
I read similar contents from [BIONIX BIUI] but there is no Q&A of [BIONIX BIUI] here so allow me to post here...
I was in Darky Rom and switched to FusionXII direct through CWM qithout any problem and now hope to flash BINIX BIUI...
Do I have to flash UCKL2's stock bootloader first through ODIN then should flash KJ2 based custom rom or can flash direct through CWM ???
Anything should I be careful when switching from one rom to another ??
Thanks, guys...
Pls consider I am learning step by step...
Yes you still have bootloadets
Sent from my SGH-I997 using xda premium
Loaders
Sent from my SGH-I997 using xda premium
You should avoid messing with bootloaders whenever possible.
The only reason EVER to flash a bootloader on Infuse is to transition from Froyo to Gingerbread - once you're on a Gingerbread bootloader, if you're staying with a Gingerbread ROM, keep the bootloader.
Entropy512 said:
You should avoid messing with bootloaders whenever possible.
The only reason EVER to flash a bootloader on Infuse is to transition from Froyo to Gingerbread - once you're on a Gingerbread bootloader, if you're staying with a Gingerbread ROM, keep the bootloader.
Click to expand...
Click to collapse
I had GB running. Last night I flashed Infused 1.6.0 (Froyo), and then came back to GB rom, with no issues. So I think once we are on GB, we can switch back and forth while being careful not to mess with CWM.
Or maybe I was lucky 'cos the the line in Infused 1.6.0 changelog:
"Removed recovery binary to prevent the phone from booting into green CWM"
stick with gingerbread bootloaders after you install them
I'd avoid Bionix for the time being. I've been doing this for a while and I it's taking some work to get back.. flash around with the others for a while and get some experience.. Doesn't mean you don't have good work nopco..
Ok, thanks guys...
Sorry again for novice question again..
I want to "Stick" to GB bootloarder... the problem is "HOW?"
I read through forum and found out there is no way to check whether I am in GB' bootloader or not...
Already flashed with UCKL2 Stock Rom once, so can I consider I have GB bootloader now ???
I flashed other rom such as MaxQ, FusionXII and re-flash to BIONIX without Rainbow problem so this is ok now ?
Thanks again for advice again, duds..
diablo009 said:
I had GB running. Last night I flashed Infused 1.6.0 (Froyo), and then came back to GB rom, with no issues. So I think once we are on GB, we can switch back and forth while being careful not to mess with CWM.
Or maybe I was lucky 'cos the the line in Infused 1.6.0 changelog:
"Removed recovery binary to prevent the phone from booting into green CWM"
Click to expand...
Click to collapse
During switch between one rom to another, my device also booted in "Green Recovery" then I ODIN with community kernel to get Red CWM recovery to re-flash other rom.
Did I do something wrong ??
Paxunion said:
During switch between one rom to another, my device also booted in "Green Recovery" then I ODIN with community kernel to get Red CWM recovery to re-flash other rom.
Did I do something wrong ??
Click to expand...
Click to collapse
Everyone has their way of installing roms. What's weird is I have no idea how everyone is getting different color recovery screens other than red. The only recovery I've ever had has always been red in Cwm. Simple if your on Froyo if you flash the community kernel v8 reboot into recovery, you'll be in red Cwm and can flash any rom you want without issues. You don't need to worry about changing the kernel cause most roms come with a kernel and will erase the community kernel v8. Why is this all so difficult?
Sent from my SAMSUNG-SGH-I997 using xda premium
Yes, I also though as you explained...
I have flashed GB based rom as I believe... never flashed to Froyo Rom.
So there should be no worries about bootloader or kernel.
But when I flashed BOINIX which is based on stock Kernel, things messed up with shown Rainbow affect and this was caused because I was in Froyo Kernel as I read.
Ok, so now I want to make really sure I am in GB bootloader.
Question is,
If flashed successfully to GB based Rom, bootloader is not to be concerned ??
Is there anyway to flash ONLY GB BOOTLOADER with ODIN to make sure I am on GB bootloader ?
Sorry again for dumb question again...
I am really, really newbie not only for Infuse but for ANDROID totally so need help and advice.
Thanks, Axiomkid and all...
Paxunion said:
Yes, I also though as you explained...
I have flashed GB based rom as I believe... never flashed to Froyo Rom.
So there should be no worries about bootloader or kernel.
But when I flashed BOINIX which is based on stock Kernel, things messed up with shown Rainbow affect and this was caused because I was in Froyo Kernel as I read.
Ok, so now I want to make really sure I am in GB bootloader.
Question is,
If flashed successfully to GB based Rom, bootloader is not to be concerned ??
Is there anyway to flash ONLY GB BOOTLOADER with ODIN to make sure I am on GB bootloader ?
Sorry again for dumb question again...
I am really, really newbie not only for Infuse but for ANDROID totally so need help and advice.
Thanks, Axiomkid and all...
Click to expand...
Click to collapse
The bootloader are found within the kernel itself. So if you flashed a gb rom using a gb based kernel you are on gb bootloader and not froyo. Froyo stock based kernels may cause rainbow screens cause it won't work with gb roms this is why you are getting them.
Sent from my SAMSUNG-SGH-I997 using xda premium
Axiomkid said:
The bootloader are found within the kernel itself. So if you flashed a gb rom using a gb based kernel you are on gb bootloader and not froyo. Froyo stock based kernels may cause rainbow screens cause it won't work with gb roms this is why you are getting them.
Edit: community kernel v8 works for both froyo and gb. I flash it using sgs kernel flasher from the market and then I'm able to flash gb roms without getting bootloops and other issues. You can't flash a gb kernel over Froyo cause it will cause bootloops and it won't load and you'll have to gtg to stock again.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I997 using xda premium
@Axiomkid,
Thanks for kind advice, now I know clearly,
1) Bootloader is in the kernel so unnecessary to flash separately.
2) Community kernel V8 works both for Gb and Froyo so it will be ok to flash Community kernel v8 to get Red CWM to re-flash other GB Rom from existing GB Rom.
Another question is,
If I want to flash Froyo Rom from existing GB Rom, what is the right way to do and if flash to Froyo Rom, I am on Froyo Bootloader, right ??
Thanks again & Merry Christmas !
If you wanna go back to Froyo use Odin and flash GTG ultimate unbrick to reformat the phone back to original Froyo.
Sent from my SAMSUNG-SGH-I997 using xda premium
It is very important if you install a rom and you don't like the kernel, sometimes it can be flashed with a different kernel but chances are it will screw your phone up. I tried using a different kernel on someone's rom and I had a tint of yellow on my screen. The Devs give us a kernel that works specifically for their rom and should not be replaced with another kernel unless told otherwise. People get errors cause of this and fill up a lot of forum space asking why their phone is screwed up. You just need to read before installing a rom. Each rom includes each own set of directions.
Most kernels allow overclocking and under volting your phone, and to be honest I don't mess with the settings so I don't end up with a burnt CPU
Sent from my SAMSUNG-SGH-I997 using xda premium
Axiomkid said:
The bootloader are found within the kernel itself. So if you flashed a gb rom using a gb based kernel you are on gb bootloader and not froyo. Froyo stock based kernels may cause rainbow screens cause it won't work with gb roms this is why you are getting them.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
WRONG. DEAD WRONG.
The bootloader is a COMPLETELY different entity than the kernel.
Custom Gingerbread kernels (such as Infusion-GB and Daily Driver) have a workaround that allows operation with Froyo bootloaders.
However, working video acceleration in the latest leaks can only be obtained with a stock kernel from one of those leaks. If you flash a kernel and system image from a leak (such as UCKL2) and you get rainbows, you need to flash new bootloaders. If you don't get rainbows - you don't need new bootloaders and should avoid flashing them if at all possible.
(Basically, don't flash anything with boot.bin or sbl.bin using Heimdall or Odin once you're on GB bootloaders.)
Entropy512 said:
WRONG. DEAD WRONG.
The bootloader is a COMPLETELY different entity than the kernel.
Custom Gingerbread kernels (such as Infusion-GB and Daily Driver) have a workaround that allows operation with Froyo bootloaders.
However, working video acceleration in the latest leaks can only be obtained with a stock kernel from one of those leaks. If you flash a kernel and system image from a leak (such as UCKL2) and you get rainbows, you need to flash new bootloaders. If you don't get rainbows - you don't need new bootloaders and should avoid flashing them if at all possible.
(Basically, don't flash anything with boot.bin or sbl.bin using Heimdall or Odin once you're on GB bootloaders.)
Click to expand...
Click to collapse
Boy, I wish I read this yesterday.
I had struggled with this yesterday trying to install Bionix using heimdall.
Managd to boot loop in 3e blue recovery several times until I flashed bootloaders in heimdall to get back to a working stock.
Paxunion, if I may suggest, if you are on froyo,
I think it'll be easier for you to use Adam outler's heimdall uckj4 return to stock.
Put your phone in the download mode. Flash it once then flash it again with the bootloader checked.
Go to his second post and flash the kernel to get recovery and then you will have gb bootloader and be able to flash the ROM of your choice.
If you did want Bionix, very nice, use the heimdall package that Dani included in the bionix thread. You won't have to flash the kernel step if you use Dani's heimdall package.
Do not check the repartition or partition box with the bionix flash.
qkster said:
Boy, I wish I read this yesterday.
I had struggled with this yesterday trying to install Bionix using heimdall.
Managd to boot loop in 3e blue recovery several times until I flashed bootloaders in heimdall to get back to a working stock.
Paxunion, if I may suggest, if you are on froyo,
I think it'll be easier for you to use Adam outler's heimdall uckj4 return to stock.
Put your phone in the download mode. Flash it once then flash it again with the bootloader checked.
Go to his second post and flash the kernel to get recovery and then you will have gb bootloader and be able to flash the ROM of your choice.
If you did want Bionix, very nice, use the heimdall package that Dani included in the bionix thread. You won't have to flash the kernel step if you use Dani's heimdall package.
Do not check the repartition or partition box with the bionix flash.
Click to expand...
Click to collapse
I was wondering if anyone actually used that...
good to know it worked out. I've wanted to do a rom with stock kernel for a while but nop can do it better. just glad I could help in a way.
Dani897 said:
I was wondering if anyone actually used that...
good to know it worked out. I've wanted to do a rom with stock kernel for a while but nop can do it better. just glad I could help in a way.
Click to expand...
Click to collapse
I ran into some problem due to checking of the repartition box and screwed up everything. Had to reflashed bootloader to get the phone working again.
I found it was easiest to flash adam's uckj4. Then heimdall fronend your package.
Two steps. Simple. If i have some time, i might do a faq step guide thread in the q a
Several months ago I purchased a NS4G on Craigslist. I wanted to use it as an iPod touch without the data. It came rooted with SuperUser. The phone keeps prompting me to OTA to 2.3.7 (it's currently on 2.3.5) I used Gingerbreak to unroot and it worked, SuperUser is now gone. However, ClockWorkMod Recovery is still present and 2.3.7 won't install. The phone reboots, goes to about 1/3 of the progress bar, and then fails. I just want to get the phone on completely stock 2.3.7, in preparation for the coming 4.0 OTA.
Hopefully the solution doesn't involve flashing a custom ROM, I've never done that before. Thanks!!
No need to get it OTA, you can just flash the stock ICS ROM found in the stickies of the development forum of this phone. Of course follow instructions closely.
Sent from my Nexus S using xda premium
But I'm selling it and need it to be completely 100% original and stock, which is what the buyer requested..
You want to use fastboot to flash a stock recovery. Peter Alfonso has them all listed on his site.
Thanks. I'm really not familiar with fastboot, and is there any way you could give me a link with instructions or the files I need? My build number is GRJ90.
And if there's anyway for me to avoid a rooted stock ROM, that'd be great. Just pure stock 2.3.7.
The stock image on Rom manager has the recovery bootloader included.
Flash a stock gb rom from cwm. You will find a list of them in either general or android development threads, not sure which. Completely stock, unrooted and as far as I remember the stock recovery is included. If not then the person will never know anyway as if someone doesn't want any non stock features then they won't know how to get to recovery anyway.
Actually I don't think they have stock recovery. Just flash the stock rom and then fastboot flash the stock recovery like was mentioned above. All you need to type is:
Fastboot flash recovery xxxxx.img
Xxxxx.img is the name of the image file you download.
Don't cheat the buyer...Tell him exactly what he's buying...And that you returned thedevice back to stock again.It's just not worth it.
Hello!
I just got a pretty good deal on a stock Froyo Infuse 4G, so I bought it.
A little help please! I would love to have the stock ATT rom with the ability to overclock the processor. This is was I have done so far.. plrease don't be so hard on me since this is my first non-HTC device lol.
So the first thing I did was install a "leaked" Gingerbread ATT stock rom using a program called Odin. Then, I root it using that Superoneclick software... I actually clicked a million times instead trying to get it working because I had GingerBread instead of Froyo ... but somehow managed to do it, it is properly rooted and well tested. So! now with my rooted device, I downloaded Rom Manager from the market, flashed it succesfully (at least that's what the screen said)... and when trying to boot into CWM Recovery I got the following errors:
verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
installation aborted.
I tried to flash it via RomManager several times, also did it via SD-Card renaming it to Update.zip and flashing it with the stock recovery.. same error. I searched for more information, someone in the forum said the reason could be an incompatible Kernel, so I flashed the Community V8 Kernel... and my device didn't boot past the Samsung screen... but somehow if I tried manaully to get into CWM recovery, it worked! (just the recovery). Flashed a custom rom that I didn't like... then suddenly I lost the CWM Recovery and cannot then bricked it and was unable to flash it again..
I managed to restore the phone to ATT factory condition using a guide here on Xda (this time the phone kept the leaked GB rom)... then rooted it again and haven't done anything else. Mu question is:
How can I keep this stock rom with the ability to overclock the processor? (flashing different kernels just makes it freeze on boot at Samsung logo).
Thanks for your help!::
here a good start by me:
http://forum.xda-developers.com/showthread.php?t=1437548
Thanks, it is a useful link but I still don't find the answer to my question (or maybe I just don't undertand it).
I am beyond frustration... could anyone please tell me what to do to step by step to flash an overclockable Kernel keeping my GingerBread stock ATT rom? like if you were explaining it to a retarded person?
many thanks...
domenicostorino said:
Thanks, it is a useful link but I still don't find the answer to my question (or maybe I just don't undertand it).
I am beyond frustration... could anyone please tell me what to do to step by step to flash an overclockable Kernel keeping my GingerBread stock ATT rom? like if you were explaining it to a retarded person?
many thanks...
Click to expand...
Click to collapse
1. You need to restore you phone back to stock using gtg's unbrick or heimdall 1 click. (See my post)
2. ATT's GB latest is not rootable thru SOC. You can use odin to flash an insecure kernel (http://forum.xda-developers.com/showthread.php?t=1212485) but you will also need to update superuser binaries and busybox as well. Running the insecure kernel for OC, you will lose the video recorder and video player.
It doesn't sound like you can understand enough yet to do this.
3. If you want a stock att and rooted, go to the dev section:
check out zeus stock 5.2, vagabond or victory. These are GB stock base roms with root already done. There is also dman's deodexed, rooted gb uclb3 already with oc kernel...no video
qkster said:
1. You need to restore you phone back to stock using gtg's unbrick or heimdall 1 click. (See my post)
2. ATT's GB latest is not rootable thru SOC. You can use odin to flash an insecure kernel (http://forum.xda-developers.com/showthread.php?t=1212485) but you will also need to update superuser binaries and busybox as well. Running the insecure kernel for OC, you will lose the video recorder and video player.
It doesn't sound like you can understand enough yet to do this.
3. If you want a stock att and rooted, go to the dev section:
check out zeus stock 5.2, vagabond or victory. These are GB stock base roms with root already done. There is also dman's deodexed, rooted gb uclb3 already with oc kernel...no video
Click to expand...
Click to collapse
Thanks for the info!
The first step has been done, restored the phone using Heimdall one click after bricking it, the phone was restored with a UCKJ4 2.36 GingerBread stock ATT rom (Kernel 2.6.35.7-I997uckj4-cl694350) and I am also rooted using SuperOneClick.
I don't fully understand step two, will try it once I get some more knowledge.
Question about the third step... does HDMI work in any of those custom stock roms? I use HDMI a lot.
domenicostorino said:
Thanks for the info!
The first step has been done, restored the phone using Heimdall one click after bricking it, the phone was restored with a UCKJ4 2.36 GingerBread stock ATT rom (Kernel 2.6.35.7-I997uckj4-cl694350) and I am also rooted using SuperOneClick.
I don't fully understand step two, will try it once I get some more knowledge.
Question about the third step... does HDMI work in any of those custom stock roms? I use HDMI a lot.
Click to expand...
Click to collapse
My Vagabond ROM runs the stock kernel if you follow directions.
HDMI will work. Battery is excellent. Feel free to check it out
qkster said:
My Vagabond ROM runs the stock kernel if you follow directions.
HDMI will work. Battery is excellent. Feel free to check it out
Click to expand...
Click to collapse
Thanks, but is it overclockable?
domenicostorino said:
Thanks, but is it overclockable?
Click to expand...
Click to collapse
you cant have your cake and eat it too.
stock kernel = HDMI. no oc
oc = no HDMI, and currently, no video on some rom
Phone is rooted, CWM installed latest, recovery e3 does not check signatures.
Can I just create nandroid backup, wipe phone and install this one rom for example?
AjvarXX said:
Phone is rooted, CWM installed latest, recovery e3 does not check signatures.
Can I just create nandroid backup, wipe phone and install this one rom for example?
Click to expand...
Click to collapse
Yep.. You take a backup, wipe cache,data and dalvik cache. You are ready to flash your custom rom.. But while changing kernels you gotta flash your stock rom+stock kernel then root then flash new kernel then the custom rom.
haridevil99 said:
Yep.. You take a backup, wipe cache,data and dalvik cache. You are ready to flash your custom rom.. But while changing kernels you gotta flash your stock rom+stock kernel then root then flash new kernel then the custom rom.
Click to expand...
Click to collapse
Appreciate. So I now will backup and wipe everything and then update it with kies mini. And then will ask more about custom stuff, am I doing right?
The problem about SGS4G is that it is WAY TOO MUCH information about it as well as kernels, mods, articles and you are lost because some of them conflicts with other.
P.S. I spent a week for going into Android stuff and Galaxy S.
AjvarXX said:
Appreciate. So I now will backup and wipe everything and then update it with kies mini. And then will ask more about custom stuff, am I doing right?
The problem about SGS4G is that it is WAY TOO MUCH information about it as well as kernels, mods, articles and you are lost because some of them conflicts with other.
P.S. I spent a week for going into Android stuff and Galaxy S.
Click to expand...
Click to collapse
Well.. If you were talking bout updating your stock rom using kies... I dont see any use of that if you are going to flash a custom rom. Its just mere waste of time.
haridevil99 said:
Well.. If you were talking bout updating your stock rom using kies... I dont see any use of that if you are going to flash a custom rom. Its just mere waste of time.
Click to expand...
Click to collapse
it's because 2.2 version is so hard for modding that I didn't risk to update from it.
Now I have modded kernel on stock 2.3.6. And thinking about what ROM to use.
Here is a link I found recently and it is so very helpful! http://forum.xda-developers.com/showthread.php?t=1470716
AjvarXX said:
it's because 2.2 version is so hard for modding that I didn't risk to update from it.
Now I have modded kernel on stock 2.3.6. And thinking about what ROM to use.
Here is a link I found recently and it is so very helpful! http://forum.xda-developers.com/showthread.php?t=1470716
Click to expand...
Click to collapse
The guide seems good enough but a bit more complicated that it should be. Anyway here are two tips or info for you. First, whatever you do, have Odin and Stock Firmware ready to flash coz when everything else fails, Odin to the rescue and also flash stock firmware (Rom+kernel) whenever you change kernel as changing kernels without doing so removes root access and you cant apply root update on a custom kernel unless it has pre root access. Second, you dont need any kind of manager to flash firmwares and updates. CWM is a replacement to all. But its all your choice.