Database Develop

How to revert to stock kernel

I have a Bell SGS, GT-I9000m. I'm considering installing hardcore kernel only, i.e. no custom ROM. If later I want to revert to the stock kernel, how would I do that?
Thanks for your help.
Sent from my GT-I9000M using XDA App

I'm not quite sure if it is possible with the stock-kernel but if you can make a full backup (like with CWM) you could restore it later. But why do you want to get back to stock-kernel?
If the backup-possibility does not work you have to find the stock-kernel for downloading and flash it via Odin or you have to flash the whole stock-ROM with Odin.

Thanks for your answer. I can't make a Nandroid backup while I'm on stock (because I can't install CWM recovery because I'm on 3e stock recovery, not 2e)
I'm not sure why I would want to go back to stock... Maybe something goes terribly wrong? I guess I just wanted to know if it was possible.
Last question: when you say I would have to find the stock kernel, is that just Google, or are there sites/repositories out there for this sort of thing?
Sent from my GT-I9000M using XDA App

I should add, the site/repo question is for kernels and stock ROMs...
Thanks.
Sent from my GT-I9000M using XDA App

site1ca said:
I'm not sure why I would want to go back to stock... Maybe something goes terribly wrong?
Click to expand...
Click to collapse
Well, then just flash the whole stock-ROM and flash it (look at samnfirmware.com for firmwares).
site1ca said:
Last question: when you say I would have to find the stock kernel, is that just Google, or are there sites/repositories out there for this sort of thing?
Click to expand...
Click to collapse
Don't know if you'll find it anywhere cause nobody needs it.

Possible scenario
Alright, thanks for your help. I guess the one scenario that is bothering me is as follows:
1) Bell - FINALLY - releases their official Gingerbread update.
2) I've installed Hardcore kernel, which according to - http://forum.xda-developers.com/showthread.php?t=822756 - "works on all 2.2 and 2.2.1 ROMs".
3) Would I be able to install the Bell Gingerbread update with Hardcore kernel?
This is why I keep asking how I would revert from Hardcore because I obviously don't want to lock myself out of Bell updates forever.

It doesn't matter which kernel you are using when you are flashing with Odin. And Bell releases the updates later than Samsung, so you'd have the advantage of getting updates earlier with a 'free' firmware.

One solution to flash back the stock kernel is to extract the zImage (the kernel) from the stock rom and flash that with Odin or Heimdall.
But as far as I know having a custom kernel would not cause problems with installing a stock upgrade.

Done
I've installed Hardcore's kernel. Everything seems to be working fine, phone started up and picked up service.
I booted into recovery, enabled lagfix, turned on all of the recommended tweaks and then ran the Quadrant Standard. Things seem a bit faster, so I guess it's all good.
Next step, Darky's 10.1.
Thanks for your help, everyone.

One more question:
I did a Nandroid backup of everything (so data, dbdata, cache AND system). The restore option says "Be careful!". What's up with that? I mean, what's the caveat?
Thanks.

I've already made some NANDROID-backups, but never seen 'Be careful!'.
If the backup was succesful I wouldn't care about that.

*sigh*, I hate to keep adding questions on to this thread, but I must.
After installing the hardcore kernel and enabling tweaks and lagfix, I'm running into exactly this problem: http://forum.xda-developers.com/showthread.php?t=851970
My phone was extremely hot for a while, then I got a warning indicating that my internal phone storage was running low, etc.
Eventually, I found this file (/data/local/tsprsp) to be the culprit. I deleted it and rebooted and now my phone is fine. However, vibration just doesn't work at all!
Any ideas? Has anyone else run into this problem?

I was told that if you do a 'full' backup, in some cases restoration will fail with some error. But it depends on the version of the ROM you are using.
That is the reason why it is recommended to backup only data and if you want to restore, then first reflash your rom, then restore the data.

Thanks, zsori. That explains the "Be careful!".
Sent from my GT-I9000M using XDA App

After trying MIUI, a stock ROM will never touch my SGS again.

meresis said:
After trying MIUI, a stock ROM will never touch my SGS again.
Click to expand...
Click to collapse
you will have to flash back a stock rom via odin if anything wrong happen during the flashing of custom roms, although chances are low if you follow the instructions carefully.
good luck and have fun flashing custom roms!

Which Gingerbread?
So I'm continuing my quest to learn more about all of this custom ROM flashing stuff. And I wanted to get gingerbread on my phone... So I figured I'd just get an image from samfirmware.com and flash it. But then, I went here (because I was also interested in Darky's 10.1 so I was reading their guide): http://www.darkyrom.com/community/i...-darkyrom-gingerbread-jvh-noob-friendly.3080/
It says that flashing "Ficeto_JVH_I9000_Odin" will get me a stock Gingerbread. My question: what's the difference between flashing an image from samfirmware.com or flashing "Ficeto_JVH_I9000_Odin"? How do I know which to pick?
In all my browsing/reading, I realize that there are 3 "separate" parts: kernel, modem and then the "ROM". Ideally, I want to keep my modem as is... What does that correspond to in Odin? I've tried to find what "PIT", "PDA", "PHONE" and "CSC" represent in Odin, but I'm not sure I got it right. PIT = Kernel? PHONE = modem?
And finally, how do I know if a particular kernel is compatible with a particular ROM?
Sorry, I know there are lots of questions there. But please help clearing up a n00b's confusion. Thanks.

site1ca said:
So I'm continuing my quest to learn more about all of this custom ROM flashing stuff. And I wanted to get gingerbread on my phone... So I figured I'd just get an image from samfirmware.com and flash it. But then, I went here (because I was also interested in Darky's 10.1 so I was reading their guide): http://www.darkyrom.com/community/i...-darkyrom-gingerbread-jvh-noob-friendly.3080/
It says that flashing "Ficeto_JVH_I9000_Odin" will get me a stock Gingerbread. My question: what's the difference between flashing an image from samfirmware.com or flashing "Ficeto_JVH_I9000_Odin"? How do I know which to pick?
In all my browsing/reading, I realize that there are 3 "separate" parts: kernel, modem and then the "ROM". Ideally, I want to keep my modem as is... What does that correspond to in Odin? I've tried to find what "PIT", "PDA", "PHONE" and "CSC" represent in Odin, but I'm not sure I got it right. PIT = Kernel? PHONE = modem?
And finally, how do I know if a particular kernel is compatible with a particular ROM?
Sorry, I know there are lots of questions there. But please help clearing up a n00b's confusion. Thanks.
Click to expand...
Click to collapse
you got it wrong.
PIT is for mapping the partitioning of the phone. In most cases you should only use 512 pit file. and only use it when you want to wipe the phone.
the three parts is "pda" (which is the rom), "phone" (which is the modem), and "csc" (which is the carrier customization and apns)
the kernel is in the part of pda (the rom)
check the thread in xda of the kernel to see if its a gingerbread kernel or froyo kernel.
hope this clear things up

Yes, that helps. That's really good to know. So now, in Darky's guide to flashing Flash Ficeto_JVH_Odin, I see that only PIT and PDA are specified. This is reassuring, knowing that the modem and carrier stuff isn't touched.
Many thanks.

There are firmwares with three parts (Phone, PDA, CSC, including bootloader) and with only one part (PDA, no bootloader(?)). The one-part-FW is just an 'update', the one with three parts an 'upgrade'.

[Q] Ext4 to RFS on the Tab

Hello Everyone,
First of all, let me thank everyone on this forum, because it's an endless source of information regarding our favorite gadgets. I'm pretty new to this so please forgive me if this is too basic.
I've searched the forum but couldn't find a clear answer to this. Here's my background:
I have an Euro Tab, and had a few updates via Kies, first to JJ7/JK5/JJ5 (CPW) and then to JMI/JMA/JM2 (CPW).
I rooted with z4root and then with SuperOneClick (on JMI, as z4 wouldn't work). I was a bit afraid of trying custom roms, but finally took the plunge because I was tired of waiting for official Samsung Gingerbread.
I started by patching the bootloaders on JMI, as instructed in the forum and flashed JQ1. I had a few problems, but I was able to solve everything and get GB running and then rooted with CF-Root
Of course, this is like an addiction and less than 24 hours after that, I flashed Overcome Hermes 2.0.1 with 3.1.0 Kernel, adjusted UV settings and installed a few Mods.
This is like having a new tab. it's responsive, battery is better and apart from a few minor bugs, it's really the greatest experience. Congrats to all the devs. This is what it should have been out of the box.
As I understand, OC Hermes 2.0.1 converted the file system to EXT4 while partitioning (please call me wrong if this is not true). On a friend's Galaxy S, he has the option to convert to EXT4 and revert to RFS on the CWM app which doesn't exist on OC Hermes (again, please correct me if I'm wrong).
Now the question(s). (finally) If I ever want to go back to stock (Froyo) either to try the official Samsung GB for my region when it comes out or if I have to send it to Samsung for some reason (knock on wood), can I just use Odin and flash a stock ROM (say JMI) with repartitioning with no problems or do I have to revert to RFS and then flash Froyo?
If so, how should I proceed to go back to RFS?
How can I confirm which file system it's using?
I've seen threads talking about going from Froyo to GB and back, but never with overcome, always with stock ROMs so, to avoid problems, I decided to ask this for a straight yes or no.
Thanks in advance for any help or comment. If this has been answered before, please link me to it. As I said, I couldn't find it through search.
Best, a.

I use chainfire's ext4conversion tool. It has the ability to switch to rfs. I am not on overcome rom so not sure it will work but its an apk available on xda forums, could give it a whirl.
As for the tool it works good.
Reverting to stock will get u back to rfs as well. (from memory stock gb files from overcome 2.0 rc1 were ok / going back to froyo had to use one of roto rom froyo versions ).

ezynow said:
I use chainfire's ext4conversion tool. It has the ability to switch to rfs. I am not on overcome rom so not sure it will work but its an apk available on xda forums, could give it a whirl.
As for the tool it works good.
Reverting to stock will get u back to rfs as well. (from memory stock gb files from overcome 2.0 rc1 were ok / going back to froyo had to use one of roto rom froyo versions ).
Click to expand...
Click to collapse
Thank you. It's amazing that just by searching what you referred in your post, I was able to find a lot more info on this.
For what I understand, Overcome is based on JPZ and there's no CF-Root for that. I think the tools apk can be used with CF-Root only, right?
Maybe I can flash JQ1 (or other ROM supported by CF-Root) and then convert to RFS if needed.
Now I need to know if I have to go back to RFS to flash a stock Froyo ROM.
Again, thanks ;-)

If you use odin + re-partition with the pit file then essesntially you are formating back to rfs. So any stock froyo rom will be ok. Cwm flash / update wont work. I suppose you have already have your original firmware or just download one.

ezynow said:
If you use odin + re-partition with the pit file then essesntially you are formating back to rfs. So any stock froyo rom will be ok. Cwm flash / update wont work. I suppose you have already have your original firmware or just download one.
Click to expand...
Click to collapse
That's what I thought, but wasn't sure. Being a noob has it's quircks
Thank you so much.
BTW, CF-Root is basically superuser+CWM+busybox. If I have these on Overcome, is it safe to assume the EXT4 tool extension for CF-Root will work on Overcome or should I expect other dependencies? I think CWM versions are different in OC and CF-Root.

You can basicly back to froyo rom
As about the ext4 to rfs , you can do that for overcome hermes , just go through cwm and then vodo and then disable it from there (lagfix) after you reboot your system will start convert from ext4 back to rfs and also u can do the same if u wanna back to ext4
Sent from hell to take your soul

k0sh said:
You can basicly back to froyo rom
As about the ext4 to rfs , you can do that for overcome hermes , just go through cwm and then vodo and then disable it from there (lagfix) after you reboot your system will start convert from ext4 back to rfs and also u can do the same if u wanna back to ext4
Sent from hell to take your soul
Click to expand...
Click to collapse
Thank you, k0sh.
It sure is simple when you know what to look for.
Cheers

k0sh said:
You can basicly back to froyo rom
As about the ext4 to rfs , you can do that for overcome hermes , just go through cwm and then vodo and then disable it from there (lagfix) after you reboot your system will start convert from ext4 back to rfs and also u can do the same if u wanna back to ext4
Sent from hell to take your soul
Click to expand...
Click to collapse
How much time that conversion usually takes? 5min., 10min?

Depending on how much data you have on your tab. If your internal memory is studded with apps it will take quite a long time (45 minutes was reported) as the system backs up your data then restores it after conversion. If the system has fewer data it will take less (5-10 minutes).

jykke78 said:
How much time that conversion usually takes? 5min., 10min?
Click to expand...
Click to collapse
for me last time , around 1hour and my tab didn't boot , so i just force reboot it during the convert and i was know that i have to reflash back , but i take the risk and boot it again and its start over the conversion and it takes 5 to 10 mins

[Q] I need some serious help, I keep making things worse!

So my wife got a good deal on some Galaxy Tabs at her work, and being so familiar with rooting and installing custom ROMs with my Galaxy S2, I jumped right in. Stupid mistake #1. I didn't realize there were so many different versions (The S2 is international, so 99% are all I9100, and mine being I9100M, there was no concern about using I9100 firmware - apparently this was not true of the P1000 and P1000M as I've come to learn), and just followed the first comprehensive guide I found to upgrade from 2.2 froyo to 2.3.3 gingerbread, so that I could go to CM9 or CM10. I tried to flash XWJK8 (and one of the kids ran by and bumped out the USB cable!) and it would only power on to the emergency download mode. I somehow managed to get Froyo back on and working by flashing the Euro flash package (Flashing the PIT and XWJJ4), then flashing OXAJK5. I was able to boot up and was running Froyo again.
Undeterred by the set back, I tried again for Gingerbread (again, not realizing that there were GSM-only ROMs that I shouldn't have been using). I followed a guide by Chainfire (I think) that involved flashing XXJQ1, a new bootloader, and a dbdata file in PDA then finished up by flashing the CF Root OXA-JQ1 kernel. I went into CWM and did a factory reset, clear cache, etc... but it wouldn't boot past the Samsung logo. About this time, I learned about the GSM/CDMA thing, and realized I went wrong. So I set out to try and figure it out for CDMA. Unfortunately, everything refers to this Overcome guide, but the page would not load, so I figured that with CWM working then I may as well try for CM9. It failed (assert errors), so I decided to try for the stock Bell Gingerbread ROM (P1000MUGKF6). It flashes successfully, but after flashing - I get the following errors on boot up:
-- Updating filesystem...
E: failed to mount /dbdata (Invalid argument)
E: discard_filesystem_for_rfs: Can't mount /dbdata
-- Wiping cache...
Formatting /cache...
Cache wipe failed.
-- Applying Multi-CSC....
Installing Multi-CSC
Can't access to '/system/csc/KOR/system/'.
Successfully applied multi-CSC.
Click to expand...
Click to collapse
So just for giggles, I tried a factory reset with the following results:
-- Wiping data...
Formatting /data...
Formatting /dbdata
E: format_volume: rfs format failed on /dev/block/stl10
Formatting /cache...
Data wipe complete.
Click to expand...
Click to collapse
I tried doing the Euro flash again (as it got everything working again last time), and it runs successfully but still won't boot up. So I flashed the Gingerbread firmware for Bell again (P1000MUGKF6), and it still won't boot at this point, just hangs at the Samsung logo. Long story short, I've made a mess of things, and I am thinking that the more I try and fix this myself, the more I'm messing things up. I'm praying that someone here is able to help me fix this mess, otherwise I am at the point of throwing in the towel and letting this thing end up as a brick, as if no one on XDA knows how to fix this, I don't think anyone will know how.
Thanks for reading this novel, I can't tell you how much I would appreciate some assistance!

Use overcome method.
Follow my signature.
Download the GB stock safe and the PDF guide
Jump to page 7.
P1000 and P1000M is identical except for the radio.
But they both are gsm.
If you had flashed wrong ROM you would have had a brick.
You just haven't been flashing correctly.
Sent from my GT-P1000 using xda app-developers app

priyana said:
Use overcome method.
Follow my signature.
Download the GB stock safe and the PDF guide
Jump to page 7.
P1000 and P1000M is identical except for the radio.
But they both are gsm.
If you had flashed wrong ROM you would have had a brick.
You just haven't been flashing correctly.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
I just saw your reply on a different post, and gave it a try. I can't thank you enough! It worked perfectly. After I flashed the Stock Safe I was able to get it to boot up no problem, so I went on to do the kernel, and then flash the Overcome ROM from there (which was successful), but now it's been sitting on the Overcome ROM boot screen for the last several minutes, starting to think it's not going to boot... My end goal was to get CM9 installed on it, so even if Overcome ROM won't boot, am I safe at this point to try flashing CM9, or should I get Overcome ROM working first?
Also if anyone happens to know if I need to download the p1c (cdma) version of CM9 (I'm assuming based on your reply that I don't, and the p1 (gsm) version of CM9 should work, but I just want to be safe).
Thanks again for your help, at least I got things working at one point, and am confident I can get back to that point if things go south again.

So I went with my gut, flashed CM9 for the P1000 (non-CDMA) and it works like a charm. Again, can't thank you for all your help! I can't tell you how much time and grief you saved me from!!

Glad it works out.
In the future, you don't need to flash the overcome ROM.
Only overcome kernel is needed o use its cwm recovery.
The stock safe is needed to give you a clean stock baseline that works with overcome kernel.
the ultimate goal is just to have cwm recovery.
Sent from my GT-P1000 using xda app-developers app

priyana said:
Glad it works out.
In the future, you don't need to flash the overcome ROM.
Only overcome kernel is needed o use its cwm recovery.
The stock safe is needed to give you a clean stock baseline that works with overcome kernel.
the ultimate goal is just to have cwm recovery.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Thanks again for the help, she had bought 2 - 1 Bell and 1 Rogers Galaxy Tab. The Bell one was the one I was working on when I posted this, after finishing it (in total close to 12-14 hours of straight working on it and looking stuff up) I was able to get the Rogers one done in less than 20 minutes haha! :highfive:

[Q] GT-P1000 Queries

Hello everyone, a neighbour has given me his Samsung Galaxy Tab GT-P1000, requesting me to flash a stock firmware on it. But, before I do so I have a few basic queries.
:silly:
Consequently, I intend on discussing all my queries pertaining to the said device under this thread I have created, rather than creating individual threads and cluttering this sub-forum.
I intend on flashing the P1000XWJP9, a stock Gingerbread (2.3.6) firmware of the United Kingdom/Ireland region. Hence, do I need to use the gt-p1000_mr_PIT PIT file and the dbdata.tar file while flashing the aforementioned stock firmware? Also, am I required to keep the Re-Partition option enabled in PC ODIN before commencing the flashing procedure?
My neighbour's device details are as follows -
Model number: GT-P1000
Firmware version: 2.3.3
Baseband version: P1000DDJP4
Kernel version: [email protected] #4
Build number: GINGERBREAD.DDJPA
After reading Chainfire's [25.01.2011] WARNING! Do not flash JM*,KA*... README! [Patch released, L/N supported] thread, I learnt that all Gingerbread firmwares have signed bootloaders, but flashing custom kernels and custom firmwares should not be an issue.
Personally, I was keen on rooting my neighbour's device through CF Root, using the CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.zip file, but he is not one bit interested in rooting. So, I have to respect his decision, and make do with just flashing a stock firmware.
I await your expertise, and I thank you all for your patience with my naive queries.

Upon researching further, I learnt about restocking. A massive thank you to priyana, whose signature provides the link to the highly acclaimed Overcome Installation Guide.
:good:
Following the Overcome guide, I believe I could just restock my neighbour's device using the GB-Stock-Safe-v5 package and leave as it is, which would give the device the JQ1 stock Gingerbread (2.3.6) firmware.
But, for the sake of my curiosity, I am keen on learning and thus knowing, if the gt-p1000_mr_PIT and dbdata.tar files along with the Re-Partition option being enabled, are compulsory requirements if I intend on flashing the P1000XWJP9, or any other stock Gingerbread (2.3.x) firmware?
I am aware my queries are naive, but they aid in my learning.
Awaiting your helpful replies.

repartition will be needed if you are returning to stock from custom ROM that uses different partitioning scheme.
It does kind of reformat your storage too, so it is up to you.
I never use dbdata.tar on its own, although I am aware of a few methods that uses that.
If you are using Overcome's method, you use everything that comes in the GB-stock-safe-v5

priyana said:
repartition will be needed if you are returning to stock from custom ROM that uses different partitioning scheme.
It does kind of reformat your storage too, so it is up to you.
I never use dbdata.tar on its own, although I am aware of a few methods that uses that.
If you are using Overcome's method, you use everything that comes in the GB-stock-safe-v5
Click to expand...
Click to collapse
priyana, thank you very much for your prompt response.
:good:
Presently, my neighbour's device is on the JPA stock Gingerbread (2.3.3) firmware, and thus going by your reply, it is clear I do not require the Re-Partition option be enabled. But, I do need the PIT file while flashing another stock Gingerbread (2.3.x) firmware, right?
Also, if I were to root the device based on its current JPA stock firmware, could I use the CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.zip file to do so?
I await your further assistance.

PIT is partition information table.
You only need pit file to repartition.
So no, you dont need pit file.
Sent from my GT-N7100 using xda app-developers app

CM9.1 flashing issue
Hello everyone, my neighbour suddenly decided, and as such has given me the green signal to root and flash a custom firmware on his GT-P1000.
As the device was on the JPA stock Gingerbread (2.3.3) firmware, I restocked using the GB-Stock-Safe-v5 package, and rooted the device flashing the CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar file via PC ODIN.
I was keen on flashing the CyanogenMod Ice Cream Sandwich custom firmware (CM9.1), and thus copied the cm-9.1.0-p1.zip and gapps-ics-20120429-signed.zip files onto the root of the Internal SD. After that, I booted the device into the CWM custom recovery and performed the 3 wipes (data/factory reset, cache and dalvik cache). Subsequently, I chose the CM9.1 zip file to be flashed.
But here is where I hit a roadblock. The device kept rebooting and thus displaying the CyanogenMod boot screen. This continued into what seemingly was, sort of a loop. As of now, I have only restocked the device again.
:fingers-crossed:
Should I have used the Overcome kernel instead of the CF modified kernel? I am still unsure what went wrong whilst attempting to flash the CyanogenMod custom firmware.
I await your expertise.

From stock, you need to flash cm9.1 3 times, not just one.
Sent from my GT-N7100 using xda app-developers app

CM9.1 flashing issue
priyana said:
From stock, you need to flash cm9.1 3 times, not just one.
Click to expand...
Click to collapse
priyana, thank you very much for your valuable response.
I have not understood your advise about flashing CM9.1 three times, and thus humbly implore you to kindly elaborate further, possibly laying out the procedure.
I thank you for your patience and await your further guidance.

Just do exactly like I said. Flash the Rom zip 3 times.
While doing it, try to read what the screen shows.
First flash typically replaces your kernel, and you return to cwm but no longer cwm 4 or 5 from cf-root or overcome. Likely it will be cwm6 from cm/humberos.
Second flash may say something about converting your partition from bml to MTD.
Third flash will say things about flaring your system. That will be the real Rom, and it takes longer than the first two.
Most newbie just flash once and when returned to new cwm, they thought it is a boot loop. The key is, read the screen.
Sent from my GT-N7100 using xda app-developers app

CM9.1 flashing issue
priyana, thank you very much for your clarified response.
:good:
Kindly pardon my naive behaviour, but do I have to flash the CM9.1 zip file three times manually, or do I choose the option 'install zip from SD card', select the said zip file once, and the process will automatically initiate three times?
I humbly implore you to continue guiding me, and I thank you for your immense patience.

No. Manually 3 times.
Sent from my GT-N7100 using xda app-developers app

@priyana Hey man..can u plz hhelp me..I am trying to flash CM10.1 or Alfoger's and CDesai's..but both of them are throwing Status 7 Error? I have a GT P1000 and I am fro India. WHat am I doing wrong?
PLz PLZPLZ HELP...thanks!

CM9.1 flashing procedure was a success!
Thank you very much, priyana. My neighbour's device now breathes a new life on CyanogenMod 9!
:good:

[Q] Captivate 2.2 Froyo to X-Bean

Re: [ROM][4.1.1][PORT] X-Bean **2.0** (fast, stable & superfunctional)
Been browsing for an update on AT&T Captivate SGH-I897 Froyo 2.2 and now on T-Moble
Unlocked, rooted with SOC and CWM recovery..
Read thru development on X-Bean **2.0**
Understood to get: x-bean 1.1Base.zip / gapps-jb20121011-signed.zip / BUT not sure which kernal!!
Early the thread states Devil 1.0.4vc but most recently suggests alternative of semaphore 2.0.3c.
Am I correct in thinking both work, just the semaphore is newer?
Thanks

Tyannt said:
Re: [ROM][4.1.1][PORT] X-Bean **2.0** (fast, stable & superfunctional)
Been browsing for an update on AT&T Captivate SGH-I897 Froyo 2.2 and now on T-Moble
Unlocked, rooted with SOC and CWM recovery..
Read thru development on X-Bean **2.0**
Understood to get: x-bean 1.1Base.zip / gapps-jb20121011-signed.zip / BUT not sure which kernal!!
Early the thread states Devil 1.0.4vc but most recently suggests alternative of semaphore 2.0.3c.
Am I correct in thinking both work, just the semaphore is newer?
Thanks
Click to expand...
Click to collapse
They both work. Just make sure you get the right version.

BWolf56 said:
They both work. Just make sure you get the right version.
Click to expand...
Click to collapse
Appreciate the reply BWolf56!
I will be sure to use either the kernals with the "c" suffix as suggested in the original thread!
NOW! Trying to decide on the best Backup App..

Tyannt said:
Appreciate the reply BWolf56!
I will be sure to use either the kernals with the "c" suffix as suggested in the original thread!
NOW! Trying to decide on the best Backup App..
Click to expand...
Click to collapse
TiBu is my personal fav.

UPDATE... Again, thanks BWolf56!
AT&T Captivate on FROYO 2.2. OneClickRoot, CWM Recovery V2.5.1.2
Did ROM backup, TiBu backup, EFS, APN, Contacts etc
Installed/Flashed:
ROM X-Bean1.1 base.zip
gapps-jb-2012101-signed.zip
Semaphore_jb_2.0.3c.zip
landscape_fix.zip
Phone booted up fine initially, would always revert to landscape view, back button was now the home button.
Could not find any of my backups. "UI" kept crapping out; "Unfortunately UI is not responding" Think that's what it said!
Had to click OK and it was back until i touched anything and kept happening...
Did Advanced Restore -> CWM Recovery of: System, Data, Cache, ext/sd
Phone rebooted.... Stuck on AT&T logo screen, charging pinwheel shows but doesn't move.
Cannot get into recovery.. managed to get into "dowload mode"
tried i897UCJF6-final-OCD-REVO.zip loaded on computer, phone connected in download mode,
loaded PIT file only as the zip had no PAD file....... NO SUCCESS
If I proceeded in a NOOB fashion, it's because I am so I'll take my licks Lol
Any help would be appreciated!
Figured it best to just get back to stock 2.2, maybe even earlier since I wouldn't have the 3e recovery
problem not being able to install from OTHER sources. Then TRY again after brushing up!!!!!!!!

Tyannt said:
UPDATE... Again, thanks BWolf56!
AT&T Captivate on FROYO 2.2. OneClickRoot, CWM Recovery V2.5.1.2
Did ROM backup, TiBu backup, EFS, APN, Contacts etc
Installed/Flashed:
ROM X-Bean1.1 base.zip
gapps-jb-2012101-signed.zip
Semaphore_jb_2.0.3c.zip
landscape_fix.zip
Phone booted up fine initially, would always revert to landscape view, back button was now the home button.
Could not find any of my backups. "UI" kept crapping out; "Unfortunately UI is not responding" Think that's what it said!
Had to click OK and it was back until i touched anything and kept happening...
Did Advanced Restore -> CWM Recovery of: System, Data, Cache, ext/sd
Phone rebooted.... Stuck on AT&T logo screen, charging pinwheel shows but doesn't move.
Cannot get into recovery.. managed to get into "dowload mode"
tried i897UCJF6-final-OCD-REVO.zip loaded on computer, phone connected in download mode,
loaded PIT file only as the zip had no PAD file....... NO SUCCESS
If I proceeded in a NOOB fashion, it's because I am so I'll take my licks Lol
Any help would be appreciated!
Figured it best to just get back to stock 2.2, maybe even earlier since I wouldn't have the 3e recovery
problem not being able to install from OTHER sources. Then TRY again after brushing up!!!!!!!!
Click to expand...
Click to collapse
Did you flash a I9000 ROM? If so, you need the I9000 bootloaders.
Also to downgrade android version, you have to use Odin (i suggest kk4 without bootloaders if you already have the gb ones, which can be found in the stickies).
Make sure you follow the full instructions next time to avoid issues like that.
Sent from my SGH-I747 using xda app-developers app

BWolf56 said:
Did you flash a I9000 ROM? If so, you need the I9000 bootloaders.
Also to downgrade android version, you have to use Odin (i suggest kk4 without bootloaders if you already have the gb ones, which can be found in the stickies).
Make sure you follow the full instructions next time to avoid issues like that.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
---------------------------------------------
Ahhh, fello Canadian i see!
You may be correct thinking i have I9000 "JB"? bootloaders!, in the original
thread : Aceofspades replied to a member question stating: "Port means that this
rom is originally made for i9000 and made it to work for captivate."
Should I assume I've flashed an I9000 Rom? and now have JB bootloader?
Thinking back, I did not wipe before going back and using recovery! Not sure that was the problem
but it was on reboot after restoring CWM/system. data. cache etc that the phone rebooted and ended up
in a continual cycling of the ATT logo screen!
Big question now is how do I do to remedy my situation!!
NOTE...I have made a JIG and can get into "download Mode" now
From this point on I'll document my every move in order to be able to provide
the exact procedure I went through... might be more helpful !!
I know I know... NOOB! Lol
PS, is an alternative to use Kies Mini and update to Gingerbread?

Tyannt said:
---------------------------------------------
Ahhh, fello Canadian i see!
You may be correct thinking i have I9000 "JB"? bootloaders!, in the original
thread : Aceofspades replied to a member question stating: "Port means that this
rom is originally made for i9000 and made it to work for captivate."
Should I assume I've flashed an I9000 Rom? and now have JB bootloader?
Thinking back, I did not wipe before going back and using recovery! Not sure that was the problem
but it was on reboot after restoring CWM/system. data. cache etc that the phone rebooted and ended up
in a continual cycling of the ATT logo screen!
Big question now is how do I do to remedy my situation!!
NOTE...I have made a JIG and can get into "download Mode" now
From this point on I'll document my every move in order to be able to provide
the exact procedure I went through... might be more helpful !!
I know I know... NOOB! Lol
PS, is an alternative to use Kies Mini and update to Gingerbread?
Click to expand...
Click to collapse
First thing: don't use kies at all!
There are no JB bootloaders for the cappy, just eclair, froyo and GB. If the ROM is a port, you'll most likely have to flash the I9000 gb bootloaders but I'd suggest finding another ROM to start with (like CM). Playing with bootloaders is the only thing that will make your phone a paper weight if something goes wrong.
Also, bootloaders aren't included in roms for safety measures. That being said, you can run ICS and JB roms just fine with the GB bootloaders.
As for what comes next. Perhaps use Odin to flash stock kk4 without bootloaders, from there flash corn kernel (once again with Odin) and give CM a whirl following their full flashing instructions. (Which can be found both in their thread and website)
Sent from my SGH-I747 using xda app-developers app

Understood... NO KIES
Sorry but a little confused still...
Do I Odin flash KK4 w/o bootloaders first -> flash corn kernal with Odin -> then flash a CM ROM using their procedure?
Where in the sequence is "flash I9000 bootloaders?
* No luck finding Odin w/o bootloaders yet, outdated download sites. Will search through xda again.
Noted! "There are no JB bootloaders for the cappy, just eclair, froyo and GB." (I was originally ATT captivate on FROYO 2.2)
Noted! "bootloaders aren't included in roms for safety measures." "you can run ICS and JB roms just fine with the GB bootloaders."
As for what comes next. Perhaps use Odin to flash stock kk4 without bootloaders, from there flash corn kernel (once again with Odin) and give CM a whirl following their full flashing instructions. (Which can be found both in their thread and website)
I might be a little hazy on the order of your suggestions so thanks for the patience!
GREATLY APPRECIATING YOUR EFFORTS!!

Tyannt said:
Understood... NO KIES
Sorry but a little confused still...
Do I Odin flash KK4 w/o bootloaders first -> flash corn kernal with Odin -> then flash a CM ROM using their procedure?
Where in the sequence is "flash I9000 bootloaders?
* No luck finding Odin w/o bootloaders yet, outdated download sites. Will search through xda again.
Noted! "There are no JB bootloaders for the cappy, just eclair, froyo and GB." (I was originally ATT captivate on FROYO 2.2)
Noted! "bootloaders aren't included in roms for safety measures." "you can run ICS and JB roms just fine with the GB bootloaders."
As for what comes next. Perhaps use Odin to flash stock kk4 without bootloaders, from there flash corn kernel (once again with Odin) and give CM a whirl following their full flashing instructions. (Which can be found both in their thread and website)
I might be a little hazy on the order of your suggestions so thanks for the patience!
GREATLY APPRECIATING YOUR EFFORTS!!
Click to expand...
Click to collapse
For now, forget about the I9000 bootloaders.
Here's KK4: http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
During your flashing, did you ever flash the GB bootloaders? If not, get the version with bootloaders and make the the flashing isnt't interrupted.
And yeah, from there you got it right, corn kernel; and follow their full flashing instructions.

BWolf56 said:
For now, forget about the I9000 bootloaders.
Here's KK4: http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
During your flashing, did you ever flash the GB bootloaders? If not, get the version with bootloaders and make the the flashing isnt't interrupted.
And yeah, from there you got it right, corn kernel; and follow their full flashing instructions.
Click to expand...
Click to collapse
--------------------------------------------------
* I haven't knowingly flashed GB bootloaders.
* I've been all over the link you provided... no working downloads.
Hmmm, I did try "Odin" a couple of times to get the GingerBread update...After doing that my phone now
boots to the AT&T logo, goes black for a sec and a screen like a bad tv signal comes up! Also, the phone
is now charging and showing the big battery icon! I seem to recall reading somewhere that if that happens
it may be wrong bootloaders? Can't remember exactly what it said but am I correct thinking it was one of
your own replies to another member?
Anyway, done for the night Grrrr
Thanks so much!

Here is a post with a pic about the screen u r seeing. Pixelated screen means u don't have the GB bootloaders... http://forum.xda-developers.com/showpost.php?p=33227557&postcount=2
And i am currently in the process of uploading my Odin and Heimdall Stock KK4 One Clicks. Gonna be using MediaFire. Will post when all uploads are done and new links attached to my post #3 in the Stock Rom stickied thread in the Development forum...
Fixin to crash for the nite. But will get it done asap.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

4-2ndtwin said:
Here is a post with a pic about the screen u r seeing. Pixelated screen means u don't have the GB bootloaders... http://forum.xda-developers.com/showpost.php?p=33227557&postcount=2
And i am currently in the process of uploading my Odin and Heimdall Stock KK4 One Clicks. Gonna be using MediaFire. Will post when all uploads are done and new links attached to my post #3 in the Stock Rom stickied thread in the Development forum...
Fixin to crash for the nite. But will get it done asap.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------
Appreciate you taking the time to reply! The images you displayed are exactly what I am seeing..
Links aren't good forever, i realize that just hard to believe I hadn't found them ANYWHERE yet! Lol
PS ************
* Have since got GB Bootloaders and added thru Odin3 v1.70.. PDA.tar.md5
* Now able to get into recovery mode by 3-button, shows 3e recovery, have ability to install from sdcard,
wipe data/factory reset, wipe cache partition.
* I have an "update.zip" on there but can't remember what it's for so I didn't do it...
but still no UI coming up, just the AT&T logo which cycles ON/OFF
Am I still in the same boat... needing KK4 Odin flash, after doing that will i be able to copy
a KK4 ROM zip to my phone thru PC and flash from the phone?

Tyannt said:
-------------------------------------------------------------------------------------------
Appreciate you taking the time to reply! The images you displayed are exactly what I am seeing..
Links aren't good forever, i realize that just hard to believe I hadn't found them ANYWHERE yet! Lol
PS ************
* Have since got GB Bootloaders and added thru Odin3 v1.70.. PDA.tar.md5
* Now able to get into recovery mode by 3-button, shows 3e recovery, have ability to install from sdcard,
wipe data/factory reset, wipe cache partition.
* I have an "update.zip" on there but can't remember what it's for so I didn't do it...
but still no UI coming up, just the AT&T logo which cycles ON/OFF
Am I still in the same boat... needing KK4 Odin flash, after doing that will i be able to copy
a KK4 ROM zip to my phone thru PC and flash from the phone?
Click to expand...
Click to collapse
KK4 is a one click Odin.
From there, you'll have to use Odin 1.85 or 1.87 to flash Corn kernel to be able to flash your way up to CM.

BWolf56 said:
KK4 is a one click Odin.
From there, you'll have to use Odin 1.85 or 1.87 to flash Corn kernel to be able to flash your way up to CM.
Click to expand...
Click to collapse
Hey there!
* 4-2ndtwin chimed in and said he would post when he uploaded them.
Been looking in the meantime.
* I have both Odin versions, now understand that I can use Odin to flash any file I choose, such as the Corn kernal, not just files it may come with.
* I downloaded a "Stocki897uckk4-zImage.tar, unzipping shows "zImage" file but I
haven't touched it.
Just hanging in for a working link for the Odin KK4 One-Click I guess...
Question!!!
For clarification..Odin KK4 One-Click is just bootloaders, kernal and maybe modem, right? It's not going to give me a working ROM...OR, is it ALSO an alternative way to flash a ROM when I can't add a ROM zip to my phone thru my PC to flash?
Lol... I'll get a handle on this, more of a visual type
As usual, appreciate the help!

Stock KK4 Links up.
...Aaannnd we're back !!!
Links up and going !!!
Stock I897UCKK4 Android 2.3.5 One Clicks *Heimdall and Odin*

4-2ndtwin said:
...Aaannnd we're back !!!
Links up and going !!!
Stock I897UCKK4 Android 2.3.5 One Clicks *Heimdall and Odin*
Click to expand...
Click to collapse
----------------------------------------------------------
HUGE THANKS! , downloading now... Will update
Got my fingers crossed
##### UPDATE #####
Used: I897uckk4 Odin One Click-Stock,NO Bootloaders, Re-partition, Full Wipe.zip
UCCK4 v2.3.5 loaded, running and stable, not rooted.
Time for a break!
Thanks again guys!

Tyannt said:
----------------------------------------------------------
HUGE THANKS! , downloading now... Will update
Got my fingers crossed
##### UPDATE #####
Used: I897uckk4 Odin One Click-Stock,NO Bootloaders, Re-partition, Full Wipe.zip
UCCK4 v2.3.5 loaded, running and stable, not rooted.
Time for a break!
Thanks again guys!
Click to expand...
Click to collapse
From here, it should be a breeze. Just remember to follow the full flashing instructions :good:

BWolf56 said:
From here, it should be a breeze. Just remember to follow the full flashing instructions :good:
Click to expand...
Click to collapse
Still browsing ROMS...
Should I be bothered rooting yet? Not sure if I'll just have to do it again after a ROM switch?
Any suggestions for a root utility?

Tyannt said:
Still browsing ROMS...
Should I be bothered rooting yet? Not sure if I'll just have to do it again after a ROM switch?
Any suggestions for a root utility?
Click to expand...
Click to collapse
I suggest you start with CM.
As for rooting, you can get it directly on the store now (was recently made legal). I believe it's by chainfire. But do you need it atm?
Also, all custom roms come pre-rooted.
Sent from my SGH-I747 using xda app-developers app