Related
Ok so I got tired of the problem with the random shut down, so I returned the phone back to amazon for a brand new one I already rooted it and unlocked it and side-loaded it already. Before I started to run custom roms on it, I want to ask you guys on here what ROMS that are "stable" as in many people have used it and gave feedback that their phone will not shut down or crash.
I also have suggestion that hopefully can be done on this forum, and that is if a mod on here or an admin can make a separate section under android development for just roms only, so that way it is not all jumbled up and mixed up with other mods, or any other development guides
Thank you for all your inputs!
If you want stability then go for assonance 5.0 with a no oc kernel (xcaliber's). It is very good with all features working.
I saw the Assonance 5.0 thread but I do not see anything about the non-oc/uv section... Is there anything extra that I need to do or just download the .zip and flash it using clockwork? Also will I get the swype keyboard and all the function that the stock have and better?
I am on assinance v 5 with xcal voodoo kendal non oc. What you have to do its flash rom, disable the lagfix, download the new kernel, flash in clockwork recovery.
I also changed the modem from jk3 to jl3 to try and improve reception and battery.
This all sounds hard, I am sure but it is as easy as what you did to root your phone. You just need to learn the steps
Sent from my SAMSUNG-SGH-I897 using XDA App
mcord, I got the rom, flashed it but how do I disable the lagfix? Why do I have to download a new kernel and changed modem from jk3 to jl3? I thought it is all included in the .zip of the rom?
xterminater07 said:
mcord, I got the rom, flashed it but how do I disable the lagfix? Why do I have to download a new kernel and changed modem from jk3 to jl3? I thought it is all included in the .zip of the rom?
Click to expand...
Click to collapse
You don't have to change the kernel or modem. I did out of preference. I like xcal with voodoo more the the pre packaged kernel. I like jl3 more then jk3. The rom is fully functioning without the changes I made, and some may not like what I have done.
If you want to disable lagfix you have to get into recovery.
Advanced lf options
Lagfix
Disable lagfix
Reboot
Select backup and restore
Done.
The stock kernel is an oc kernel and I.am not interested in over clocking
Sent from my SAMSUNG-SGH-I897 using XDA App
How do you use non-oc version with this rom? I heard several people complained about battery issue not lasting as long with the assonance?!? I'm trying the di11igaf's 3.0 rom
If you want a non oc kernel on assinance download this
http://etc.muteheadlight.net/android/I9000_reoriented_v2.2.1_bln.zip
disable current lagfix using steps listed above.
Go into clockwork recovery
Select install zip from sd
Search for this file
Select
Select
Reboot
Your phone will talk to you as this installs.
done
Sent from my SAMSUNG-SGH-I897 using XDA App
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'.
Hello All,
This is my first post! But I have been visitor of this forum for some time now. Its been a great learning experience! OK ...let me come straight to the point..
Important Phone Specs:
-Samsung Captivate with stock ATT froyo (UCKB1)
-rooted, installed one-click lag fix (other minor things, like removed all bloatware, overclocked etc.)
I am planning on changing the icons in the notification bar (for example battery icon mod) using UOT (ultimate online theme kitchen) and I have the UOT zip file ready.
Q1. It is not clear if this zip file can be flashed from the stock recovery mode.
Per my understanding, these are unsigned files and hence might not work with stock recovery mode. Can some one please confirm?
Q2. If stock recovery mode does not work, then I plan to install clockwork mod recovery from the ROM Manager apk available on the market.
a) Since I will be using a custom recovery image, I assume I will no longer be able to use KIES to perform any stock updates if and when they become available. Is that correct?
b) How easy is it to revert back to stock recovery? Can you please let me know the procedure (or) point me to a link with this information?
The reason I ask is because I would like to stay stock as much as I can for the moment.
Thanks all for your help.
Regards.
I have used the UOT kitchen zips on stock KB1 but not with the stock recovery. I think you have to use CWM recovery. There's really no reason to go back to stock recovery. If you ever want to use Kies in the future to get updates (assuming ATT ever releases GB through Kies), you would have to flash back to stock anyway for Kies to recognize the phone.
Jackman,
Thanks for the response. I agree with you. I am not hopeful that ATT would release GB any time soon for captivate...so yeah I makes sense to go ahead with the CWM recovery.
I just wanted to know the pros and cons before I get started with the process.
read the how to flash custom roms link in my sig. new user guide too, find the part about stickies.
#1 correct.
#2 rom manager is only good for froyo roms on captivate... there are froyo kernels with CWM built in and tweaked that run fine on stock roms, but you must Odin flash the kernel.... which leads to...
#3 keis is garbage we use odin, the official samsung flasher utility. and we flash the same .tar files keis uses.
#4 easy to get back to stock. odin-one-click stock flashes are ONE CLICK. Sticky in Captivate Dev section. (use new user guide to find.)
Kies is trash. Even if you go back o stock, you probably need to modify code to make sure your phone's ID is still the correct one. It really isn't worth it considering Kies is just ODIN with a different UI and a craptistic amount of "checks" wich makes it fail 90% of the time.
I hardly ever have problems with odin. odin 1.3 sucked 1.5and newer work great. the homemade one clicks can be buggy. md5 check wont let you edit file names of tars. other than that i DONT have problems. its all i use. dont like heimdall and having to change my drivers for it.
Hi guys, I'm new here and have been scouring the forums on how to do things but I keep getting caught with uncertainties.
I have an i896 Samsung Galaxy S Captivate with a Rogers 2.3.3 Gingerbread installed.
I have rooted it with no issues and its also unlocked.
What I want to do:
1. CyanogenMod 7
2. Overclock the CPU
But what I don't know is...
1. Since i'm running a Rogers ROM, do I have to flash to an AT&T ROM then to any custom ROM?
2. I read the instructions on how to update to the CM7 ROM but every instruction I read says I must have Froyo/Eclair to goto CM7. So do I downgrade and if so, how can I do that? I tried and what ends up happening is the phone's reception bars have an X and data doesn't work either. In the phone About properties, states that the baseband is "unknown". I suspect I need something more than a stock Rogers ROM without bootloaders. I couldn't find a 2.1 or 2.2 stock Rogers ROM with bootloders.
3. For overclocking, I installed Voltage Control and Control Freak and neither let me overclock, the max CPU is 1000Mhz. I assume I need a custom Kernal to do this but haven't been able to find how to do this during the CM7 upgrade.
I just need someone to point me in the right direction on what order to do all this and whether me having a Rogers stock 2.3.3 ROM causes an issue. I've done a lot of reading on these forums so its not like I just signed up and wanted to know the easy way out. I simply want the proper way to do things so I don't repeat the same mistakes many people may have done in the past.
I have used Odin, Heimdall, Odin One Click, Super One Click for rooting.
Hopefully someone can guide me in the right direction and help me achieve these goals!
You dont need to go back to Froyo, as GB bootloader is compatible. but you need CWM to flash CM7. you can use Rom Manager app to flash the CWM.
Just download CM7 zip file, wipe data, system and cache and install it using CWM. It comes with custom kernel so you can overclock it using those apps you mentioned. You can also flash Glitch kernel....
See that's what i've been trying to do but when it comes to installing the nightly rom in zip format, it tells me the signature failed.
Do I need to buy the premium version of rom manager or can I get away with the free version? I don't want to use my credit card, i rather wait until paypal is implemented with android market.
This is so frustrating...
BadBoiSinZ said:
See that's what i've been trying to do but when it comes to installing the nightly rom in zip format, it tells me the signature failed.
Do I need to buy the premium version of rom manager or can I get away with the free version? I don't want to use my credit card, i rather wait until paypal is implemented with android market.
This is so frustrating...
Click to expand...
Click to collapse
You need to Odin flash a custom kernel that has CWM in it and then install the zip from CWM. I don't know if all kernels for the i897 are compatable with i896 just have to read. I
Currently Fusionized
Wdustin1 said:
You need to Odin flash a custom kernel that has CWM in it and then install the zip from CWM. I don't know if all kernels for the i897 are compatable with i896 just have to read. I
Currently Fusionized
Click to expand...
Click to collapse
Ya that's what I don't know either...I read tons of threads where people with i896 Rogers roms tried to flash with AT&T based roms or i897 roms and either bricked their phones or made a mess that took much more to get them back to stock...problem is the people that have i896 roms here I can't contact until I hit 10 posts...so I'm here stuck until then...
Just flash a custom I897 kernel with cwm, once complete, yank battery, replace and button combo boot into recovery and flash the ROM. Whichever kernel you choose doesn't really matter as zip will flash a compatible kernel, the I896 and I897 are identical other than cosmetic branding.
I was on stock rogers 2.3.3.
Installed Sumari kernel. Booted into the sumari recovery, installed CM7 zip, the phone rebooted into cwm recovery, and continued installing.
It worked pretty smoothly.
okay so i flashed my phone with a stock 2.3.5 rom with CWM, but how do I update to CM7? When i boot into recovery the only option I have is reinstall package. Do i rename the CM7 zip file to update.zip and that should work? I'm so lost...
In CWM recovery you need to choose install zip from sdcard, make sure you are in fact in cwm recovery
Before you do that....you need to flash a kernel with Odin that has cwm in it...
Woo! that worked like a charm haha yea baby yea!! Thank you soo much!! i was so scared to flash my cappy going from Rogers to AT&T that it would brick the phone. Got CM7 with Glitch Kernel and overclocked to 1.4 sawweeeeet!!
Now time to fiddle around and customize!
Thanks everyone!!
Hello all,
Couldn't find a stock flashable kernel for in between kernel flashes, so I slapped this one together. I used an old kernel script I had from back in the day (see my thread history) and just put the boot.img inside and changed the UI text. Tested working. Enjoy!
Handy! Thanks for your efforts.
Thank you?
No problem! I made it for myself and realized nobody had one up here so I figured it could help at least one person.
Thanks, always handy when you've tried a kernel that is not good
Thank you very much for this man!
Thanks
First of all, thank you for sharing it with us.
Then, from my understanding since this is Google Stock Kernel that comes with Lollipop, I'm assuming it won't allow root even flashing SuperSU ? (Last time I've read the kernel needed to be somewhat compliant with root so you can use root), am I right?
Cheers!
MidnightDevil said:
First of all, thank you for sharing it with us.
Then, from my understanding since this is Google Stock Kernel that comes with Lollipop, I'm assuming it won't allow root even flashing SuperSU ? (Last time I've read the kernel needed to be somewhat compliant with root so you can use root), am I right?
Cheers!
Click to expand...
Click to collapse
You're correct. So basically what I do is flash this, then immediately flash the next kernel I want to use in the same TWRP session.
jlink38 said:
You're correct. So basically what I do is flash this, then immediately flash the next kernel I want to use in the same TWRP session.
Click to expand...
Click to collapse
Thanks, also, from my understanding, some users reporting broken scripts when switching from one custom kernel to another. The solution so far was to flash Stock kernel before flashing another custom kernel. This happene(d) betweeen Franco Kernel and ElementalX, where sweep2wake functions wouldn't work.
Thanks for clearing this up, a stock kernel is always handy whatever the reason
So, I'm on Franco Rom can I flash this kernel and then xxkernelxx? Thanks in advance
Duilio Patiño said:
So, I'm on Franco Rom can I flash this kernel and then xxkernelxx? Thanks in advance
Click to expand...
Click to collapse
Sure, flash away, as long as it is stock 5.0. Not sure how it would fare with AOSP. YMMV.
jlink38 said:
Sure, flash away, as long as it is stock 5.0. Not sure how it would fare with AOSP. YMMV.
Click to expand...
Click to collapse
Thanks
Duilio Patiño said:
So, I'm on Franco Rom can I flash this kernel and then xxkernelxx? Thanks in advance
Click to expand...
Click to collapse
Not all kernels modify the devices system files.
I believe though that since Franco kernel modifies the system files and Since flashing just the stock recovery wouldn't alter or restore those modified system files back to normal otherwise it may/will cause conflicts and errors while running the new kernel.
You would need to (depending on your current setup)
1. Dirty flash the 5.0 ROM that your running to replace those system files back to normal and then flash the OP's stock recovery.
2. Fastboot flash the 5.0 Google Factory System.img (whick would reaplace the modified system files) and or the google factory boot.img or just flash the OP,s stock recovery and then any other compatible kernel in one setting.
3. Restore a stock nandroid backup that has the stock system.img and then flash any comparable kernel.
@jlink38
Thank you for this... Very Much appreciate and it will definitely come in very handy! :good:
I like to have a copy of evey stock recovery version for the N5 in a flashable.zip
xdrc45 said:
Not all kernels modify the devices system files.
I believe though that since Franco kernel modifies the system files and Since flashing just the stock recovery wouldn't alter or restore those modified system files back to normal otherwise it may/will cause conflicts and errors while running the new kernel.
You would need to (depending on your current setup)
1. Dirty flash the 5.0 ROM that your running to replace those system files back to normal and then flash the OP's stock recovery.
2. Fastboot flash the 5.0 Google Factory System.img (whick would reaplace the modified system files) and or the google factory boot.img or just flash the OP,s stock recovery and then any other compatible kernel in one setting.
3. Restore a stock nandroid backup that has the stock system.img and then flash any comparable kernel.
@jlink38
Thank you for this... Very Much appreciate and it will definitely come in very handy! :good:
I like to have a copy of evey stock recovery version for the N5 in a flashable.zip
Click to expand...
Click to collapse
No problem!
Thank you very much for the thoughtful upload, OP!!
Been meaning to try out Franco's latest nightly for LP to see if I get an improvement in battery life
I'm assuming if I don't like Franco's kernel, I just simply flash this zip in recovery (I use Philz CWM) to return back to the stock LP kernel?
RevoWution said:
Thank you very much for the thoughtful upload, OP!!
Been meaning to try out Franco's latest nightly for LP to see if I get an improvement in battery life
I'm assuming if I don't like Franco's kernel, I just simply flash this zip in recovery (I use Philz CWM) to return back to the stock LP kernel?
Click to expand...
Click to collapse
Pretty much, yeah
Sent from my Nexus 5
amir7777 said:
Pretty much, yeah
Sent from my Nexus 5
Click to expand...
Click to collapse
Cheers buddy
I'm in Elementalx kernel and Rom stock. To receive OTA, flash stock kernel is enough?
danifeb said:
I'm in Elementalx kernel and Rom stock. To receive OTA, flash stock kernel is enough?
Click to expand...
Click to collapse
You should be OK. I don't know what else you have tweaked.