Related
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'.
I'm running Overcome currently. Is it possible to flash to a stock system from Clockworkmod, such that the system I'm running is stock?
I don't need the tablet itself to be bone stock, but I'd just like to switch back to the stock system, with none of the Overcome modifications.
Ideally, I'd love to be able to keep Clockworkmod and still use Clockworkmod to flash modified kernels. Even more ideally, being able to stay on ext4 would be great.
The reason I ask is I've been seeing some weird bugs lately, mainly with my AT&T wireless account mysteriously breaking down and not working until I reselect the APN and reboot, as well as 30 second hanging on boot, and I'd like to try stock again to see if those problems go away.
I think you can apply Clockworkmod afterwards, if you have already successfully applied Overcome. This means that you have Odin ready on your PC, drivers for USB ready and your tablet is rooted.
I applied stock_safe ROM included in Odin package to fix my freezing tablet. Lost CWM, but right now I am looking how to apply it separately of Overcome.
edit: I think I have just found it on the market, you have free and premium version. I think this guy deserves free coffee, so let's buy premium.
For my at&t tab i use JQ1, which is stock gingerbread, then i applied the CF-Root v3.3 to have root and CWM. Then I flashed Dip7 kernel for speed improvements.
I was having the lag issue too so I reverted to this set up, and I really like it.
As for the connection issue, you have your apn correct, but remind me what modem you have? Maybe an experiment is in order.
rangercaptain said:
For my at&t tab i use JQ1, which is stock gingerbread, then i applied the CF-Root v3.3 to have root and CWM. Then I flashed Dip7 kernel for speed improvements.
I was having the lag issue too so I reverted to this set up, and I really like it.
As for the connection issue, you have your apn correct, but remind me what modem you have? Maybe an experiment is in order.
Click to expand...
Click to collapse
Okay, so I can flash to Overcome's stock safe (which will change me back off of ext4), and then using Odin flash one of the stock firmwares, and then apply CF-Root to get root/CWM. Does that sounds right?
It's actually pretty disappointing that AT&T still hasn't released or even announced its own Gingerbread update yet, which I hadn't realized while typing this, since I had really wanted to flash back to stock to fix the AT&T connection issue, but it may still work on other firmwares. Going back to Froyo seems like too much of a step backwards.
I'm currently on the KM2 modem. What do you recommend?
Flash stock safe then flash CF root, overcome kernel (only kernel), or Koxudaxi or dip7 or whatever pleases you then flash the modem that works best for you.
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.
Firmware : 2.3.6
Build Number : GINGERBREAD.XXJW4
Galaxy S I9000
I've rooted my phone...
And I've been looking for a way to lagfix my phone...
But I keep failing; won't work..
Can someone please help me with it?
I'm a beginner...
Please help...
Just install ( Flash ) any custom rom because it's already have lagfix !
you can try this one :
http://forum.xda-developers.com/showthread.php?t=1829256
or choose anyone as you like ^_^ >>>>>> http://forum.xda-developers.com/forumdisplay.php?f=665
thanks
Hi there, try XWJW6. Its much better and lag-free already.
Then, you may flash CF Root kernel and convert the filesystem from RFS to EXT4.
GINGERBREAD.XWJW8 - Lag?
lifehijack said:
Hi there, try XWJW6. Its much better and lag-free already.
Then, you may flash CF Root kernel and convert the filesystem from RFS to EXT4.
Click to expand...
Click to collapse
Hi - forgive the noob question....it's 2013 and I've got Gingerbread.XWJW8 and find it a bit laggy. I wanted to reflash a custom kernel to address occasional lag. But from above the lagfix is standard. Does this kernel include these anti-lag features? Should I reflash or let it lie.
OBTW, tried to root it using developer mode from a couple of techniques on youtube and it failed. Is this because Samsung blocks it?
nope, flash custom kernel, semaphore or cf root n ur fone will be rooted
Sent from my GT-I9000 using xda premium
Squishy61 said:
Hi - forgive the noob question....it's 2013 and I've got Gingerbread.XWJW8 and find it a bit laggy. I wanted to reflash a custom kernel to address occasional lag. But from above the lagfix is standard. Does this kernel include these anti-lag features? Should I reflash or let it lie.
OBTW, tried to root it using developer mode from a couple of techniques on youtube and it failed. Is this because Samsung blocks it?
Click to expand...
Click to collapse
Yes the above mentioned kernel includes lagfix.
Samsung doesn't block anything. You are not following the correct method.
lifehijack said:
Yes the above mentioned kernel includes lagfix.
Samsung doesn't block anything. You are not following the correct method.
Click to expand...
Click to collapse
Thanks - but may need more help as my phone is in a rebooting cycle now
Downloaded and installed standard Firmware from Sammobile - all good
Followed directions on http://forum.xda-developers.com/showthread.php?t=1044519 and downloaded SpeedMod kernel K16 series which works on older Samsung 2.3.x roms. (mine is 2.3.6 GB). Started Odin3 and installed the .tar and it appeared to flash fine, then rebooted inot a continuous cycle. I followed directions to the letter - what could I have done wrong?
I'll try another older speedmod kernel and see what happens, otherwise it's back to the standard one again.
There shouldn't of been just one .tar, it looks like you may of flashed an update instead of a whole rom.
If there was 3 .tars then you probably put them in the wrong place. Try use a guide off android souls website. They really simple and I used them when I first started.
Hi Guys,
I wondered if any of you (more experienced, long serving) users are aware of any Gingerbread ROMs? Preferably a CM or any 2.3.7 based, but if they don't exist, any build will do... It needs to be a safe build, a non eMMC bug version, or DeOxed (is that the term)?
Sure, you're gonna say, why bother.. There's JB and KK now, but I like GB and wanted to see what it's like on the N7000?
All help gratefully welcomed..
Thanks, Lister
all GB kernels are safe to wipe data (only stock ICS kernel is unsafe)
i advise you to try Checkrom HD v6, still my favorite GB rom
Sent from my GT-N7000 using xda premium
Hi @ASMI1,
Thanks for such a fast reply.. I've been to the main website where I can download it.. One thing I'm worried about, I've seen in this ROM and mentioned in another GB based ROM for our phones is: CSC?
the CheckRom v6 features "Multi CSC" what does this mean, and is it dangerous?
Do I flash Philz Kernel, and install with that? Do I need to flash another kernel afterwards? Does this room raise the counter or anything?
I'm OK flashing JB or KK, but not done a GB ROM and worried in case summit not aware of, don't want to brick this...?
Thanks, Lister
ASMI1 said:
all GB kernels are safe to wipe data (only stock ICS kernel is unsafe)
i advise you to try Checkrom HD v6, still my favorite GB rom
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
CSC means customer service code. Multi csc means that this rom is not locked to any country or carrier.
Yes you can flag it under philz kernel.
Sent from my LG-E410
Hi @kaborayyan / @ASMI1 / Guys,
I've flashed Philz original Recovery/Kernel first, and then do all the usual wipes... Factory Reset, System, Davlik Cache (and even tried Pre-Load? after first failed) and same result each time.
During the flashing process it seems to backup the EFS (even though that was the first thing I did when I got this phone, so hope it hasnt over written my original EFS backup) but then gets stuck. It seems to stay on Flashing Modem for ages, and progress bar doesnt move... And then the phone goes black, and it reboots... But then gets stuck on the white Samsung splash screen "Samsung Galaxy Note - GT-N7000" and stays like that, unless I reboot....
I reboot, but notice CWM 5.0.2.7 is installed (not sure if thats a safe one?) so I flash Philz from within that, reboot recovery and then do all the wipes again... and the phone seems like normal again. However I dont know if I've done anything wrong, or if the phone is still safe or if I've killed it any way??? lol
Cheers for any help/support.
Thanks, Lister
Lister Of Smeg said:
Hi @kaborayyan / @ASMI1 / Guys,
I've flashed Philz original Recovery/Kernel first, and then do all the usual wipes... Factory Reset, System, Davlik Cache (and even tried Pre-Load? after first failed) and same result each time.
During the flashing process it seems to backup the EFS (even though that was the first thing I did when I got this phone, so hope it hasnt over written my original EFS backup) but then gets stuck. It seems to stay on Flashing Modem for ages, and progress bar doesnt move... And then the phone goes black, and it reboots... But then gets stuck on the white Samsung splash screen "Samsung Galaxy Note - GT-N7000" and stays like that, unless I reboot....
I reboot, but notice CWM 5.0.2.7 is installed (not sure if thats a safe one?) so I flash Philz from within that, reboot recovery and then do all the wipes again... and the phone seems like normal again. However I dont know if I've done anything wrong, or if the phone is still safe or if I've killed it any way??? lol
Cheers for any help/support.
Thanks, Lister
Click to expand...
Click to collapse
Reboot into recovery again if you found the touch colored recovery then you're on philz kernel. If not be sure that you selected the suitable philz kernel.
If I helped hit the thanks button.
Hi @kaborayyan,
Yep, I'm certainly on Philz Kernel.... when it's loaded, its kind of a pink/purple-ish colour.... (not sure what version, but something like 5.1.1.1) It's the first one I downloaded when I got this phone a couple of months back, that I used to root/and then flash custom roms with... (namely, JB).
However, I fancy seeing what GB is like on it, but get stuck... it seems to hang on Flashing Modem, sits there, and then reboots without finishing by the looks of things...?
Its a UK Vodafone, N7000
Thanks, Lister
Did you try to flash a stock GB ROM through Odin? May be you get better results. Then root it and flash whatever you want of custom GB based Roms.
Sent from my GT-N7000
yeah like kaborayyan said, try to flash any stock GB rom using odin3 v1.85 only (you can find instructions and download links in the sticky thread in the orginal development section, you should look for mirrors because hotfile is down or just download chainfire prerooted stock rom)
After you get a stock rooted GB rom installed on your phone, install checkrom using the recovery after wiping data, cache and dalvik.
as i said stock ICS roms are unsafe, other roms are safe... just keep a backup of your efs
and be careful when using odin3.
btw, hitting the "thanks" button is easier than writing it
cheers
Sent from my GT-N7000 using xda premium
Lister Of Smeg said:
However, I fancy seeing what GB is like on it, but get stuck... it seems to hang on Flashing Modem, sits there, and then reboots without finishing by the looks of things...?
Click to expand...
Click to collapse
Go to www.samsung-updates.com firmware section. There are a few 2.3.6 roms available. Stock though. These roms might be non root able. Not really sure as there are not many methods of rooting GB (check Dr ketans thread for more info) . It could also be possible that for rooting again you will need to flash an ICS or JB rom again using Odin.
If you just want to taste the ginger then stock GB rom is quite fast.
Lister Of Smeg said:
Hi Guys,
I wondered if any of you (more experienced, long serving) users are aware of any Gingerbread ROMs? Preferably a CM or any 2.3.7 based, but if they don't exist, any build will do... It needs to be a safe build, a non eMMC bug version, or DeOxed (is that the term)?
Sure, you're gonna say, why bother.. There's JB and KK now, but I like GB and wanted to see what it's like on the N7000?
All help gratefully welcomed..
Thanks, Lister
Click to expand...
Click to collapse
Pristine LC1 is a good option. Its in the OP of the pristine thread. All GB kernels are safe, as above mentioned.
There is no 2.3.7 or CM based N7000 rom
Sent from Nexus 5 on Slimkat
Hi @ASMI1, @kaborayyan, @nokiamodeln91, @AndroidSlave,
Thanks guys, with you're help.... I've finally made it !!! It appears CheckROM HD v6 does not want to flash under Philz (or some other recovery, cant think what now??) However I did manage to get it to Flash under Abyss Recovery Kernel (which is based on GB kernel, apparently).
So it has flashed now, not had chance to play around with it yet as am at work... But just by looking at it, it's bringing back the GB love....
Yes I know it's sad, why go back to GB?? lol. But sometimes it's just nice to go over, for old times sake... Used to do it on my ZTE Blade many a times...
So, (quick questions).
1) With this stock-ish rom, can I remove/tweak/clean up, and then package it (in CWM) as a flashable rom?? or do I have to backup/restore only in that version of CWM??
2) It safe to flash any version of CM9, without using flashing a seperate recovery afterwards... and still avoid the eMMC. It's only official STOCK firmware that killed them....
Thanks once again guys for all your support, I know its not normal (and frowned upon) to use older firmware... But just wanted to see what GB was like again...
Cheers, Lister
Lister Of Smeg said:
Hi @ASMI1, @kaborayyan, @nokiamodeln91, @AndroidSlave,
Thanks guys, with you're help.... I've finally made it !!! It appears CheckROM HD v6 does not want to flash under Philz (or some other recovery, cant think what now??) However I did manage to get it to Flash under Abyss Recovery Kernel (which is based on GB kernel, apparently).
So it has flashed now, not had chance to play around with it yet as am at work... But just by looking at it, it's bringing back the GB love....
Yes I know it's sad, why go back to GB?? lol. But sometimes it's just nice to go over, for old times sake... Used to do it on my ZTE Blade many a times...
So, (quick questions).
1) With this stock-ish rom, can I remove/tweak/clean up, and then package it (in CWM) as a flashable rom?? or do I have to backup/restore only in that version of CWM??
2) It safe to flash any version of CM9, without using flashing a seperate recovery afterwards... and still avoid the eMMC. It's only official STOCK firmware that killed them....
Thanks once again guys for all your support, I know its not normal (and frowned upon) to use older firmware... But just wanted to see what GB was like again...
Cheers, Lister
Click to expand...
Click to collapse
1) not really unless you use a new version of philz touch recovery, which wouldn't happen because on the n7000 the recovery sits on the kernel, thus you are stuck with an old kernel and old recovery. As such your best bet is to do a nandroid backup. Further - when you restore such a backup, I recommend flashing abyss again first so you are in the Ame recovery it was made in
2) yes. Just be concerned of Stock ICS (4.0.4) with a custom recovery. Never flash temporary cwm.zip. matter of fact, just avoid stock ICS at all costs. Newer versions of cm9 are safe. Avoid very old cm9 versions. My personal recommendation to you would be Paranoid Android cm9 ( I think it stopped at around .4a) that one was amazing.
Sent from Nexus 5 on Slimkat