Related
I want to Flash Team ICSSGS [Android 4.0.3] (Link to ROM Thread) but I am not for sure what Bootloaders or Kernel I need to use.
I currently have:
Firmware Version: 2.2
Baseband Version: I897UCKB1
Kernel Version: 2.6.32.9
Build Number: FROYO.UCKB1
In general, the Gingerbread bootloaders are preferred with any of the ICS ROMs, because they are more ubiquitous and can be used with virtually any version 2.1 thru 4.0. Kernel-wise, the ICS ROMs come with a kernel, and your only other option is Glitch v14 beta right now...but mostly, you shouldn't need to worry about flashing anything beyond what's in the ROM itself right now.
WindRunnerXC said:
In general, the Gingerbread bootloaders are preferred with any of the ICS ROMs, because they are more ubiquitous and can be used with virtually any version 2.1 thru 4.0. Kernel-wise, the ICS ROMs come with a kernel, and your only other option is Glitch v14 beta right now...but mostly, you shouldn't need to worry about flashing anything beyond what's in the ROM itself right now.
Click to expand...
Click to collapse
So that ROM I listed in my OP comes with its own Kernel?
And is there a particular Bootloader I should use?
If there is, may you please link me to it?
Hey im currently running the ROM you are asking about. To answer your questions you have to be on the gingerbread bootloaders. You can flash those using odin, or since there is an official update out, use Kies mini to update your phone to gingerbread and that will flash the bootloaders for you.
About the kernel, the ROM you posted includes a kernel in the .zip and when you install the .zip it will flash the kernel for you. Its a fine kernel and works great so dont worry about changing it unless you have problems.
Here is the link on how to flash the bootloaders using Odin. Its not a hard process and pretty safe so let us know how you come out on the other side!
http://forum.xda-developers.com/showthread.php?t=1129821&highlight=gingerbread+bootloader
capocaccia said:
Hey im currently running the ROM you are asking about. To answer your questions you have to be on the gingerbread bootloaders. You can flash those using odin, or since there is an official update out, use Kies mini to update your phone to gingerbread and that will flash the bootloaders for you.
About the kernel, the ROM you posted includes a kernel in the .zip and when you install the .zip it will flash the kernel for you. Its a fine kernel and works great so dont worry about changing it unless you have problems.
Here is the link on how to flash the bootloaders using Odin. Its not a hard process and pretty safe so let us know how you come out on the other side!
http://forum.xda-developers.com/showthread.php?t=1129821&highlight=gingerbread+bootloader
Click to expand...
Click to collapse
Now when I flash this bootloader you listed, will Froyo still boot or will I have to flash my ROM afterwards?
froyo will still boot. GB BL are backwards compatible and the ISCSGS script should allow it to flash over any ROM
Hi all.
as i can't post yet in a thread mentioned by mrnapolean1 (http://forum.xda-developers.com/showthread.php?t=1362092) I'll try to ask my question here, as it related to a question asked by this thread starter
so i have gingerbread 2.3.5, installed CornKernel_UCKK4_v603 and custom rom SimplyStock KK4 V1.0 , so if i wanted to switch Team ICSSGS [Android 4.0.3] should i do following?
1. wipe data /factory reset
2.wipe system
3.flash from recovery mode Android 4.0.3 zip?
I already have a backup made with Efs Pro as a tar file
anything else i need to do?
thank you so much in advance
mrnapolean1 said:
Now when I flash this bootloader you listed, will Froyo still boot or will I have to flash my ROM afterwards?
Click to expand...
Click to collapse
Yes, Froyo will still boot. If this were a layer cake it would go something like bootloader, kernel, rom. So basically, your bootloader has nothing to do with your kernel or your rom but it is at the bottom layer of the boot process. It does effect which ROMs you can use though as gingerbread and ICS roms require GB bootloaders. So flash the bootloaders, you will still be on Froyo. Update to GB. Root GB. Place the ROM on your internal SD and then flash it. If you run into any problems check the common problems page found on the first page of the SGSICS ROM.
gugman said:
Hi all.
as i can't post yet in a thread mentioned by mrnapolean1 (http://forum.xda-developers.com/showthread.php?t=1362092) I'll try to ask my question here, as it related to a question asked by this thread starter
so i have gingerbread 2.3.5, installed CornKernel_UCKK4_v603 and custom rom SimplyStock KK4 V1.0 , so if i wanted to switch Team ICSSGS [Android 4.0.3] should i do following?
1. wipe data /factory reset
2.wipe system
3.flash from recovery mode Android 4.0.3 zip?
I already have a backup made with Efs Pro as a tar file
anything else i need to do?
thank you so much in advance
Click to expand...
Click to collapse
First, if you want to keep any of your apps or contacts backup those as well using Titanium Backup. Make sure to backup to the External SD card or make a copy of the backup somewhere other than the phones internal SD.
Second, you dont have to wipe data/factory reset before you flash. This is only if you have the problem of a bootloop when you try to install. I had this problem and when I did the wipe data afterward it fixed it immediately. So follow this:
1: Boot into CWM
2: install rom
IF you have an issue with a boot loop at this point
1: Get back into CWM using the button combination
2: Wipe data/Factory Rest and Wipe Cach
capocaccia
thank you !
one more question, i understood about data/factory/cash, but dont i need to format system before flashing new rom? i thought its always better to do before new rom flashing?
gugman said:
capocaccia
thank you !
one more question, i understood about data/factory/cash, but dont i need to format system before flashing new rom? i thought its always better to do before new rom flashing?
Click to expand...
Click to collapse
I think this was true when flashing older roms. When I flashed that ROM I did not format system and it worked fine. Let me know if you have any problems when you flash.
capocaccia said:
I think this was true when flashing older roms. When I flashed that ROM I did not format system and it worked fine. Let me know if you have any problems when you flash.
Click to expand...
Click to collapse
i see. okey, thanx a lot again. will be able to flash in about an hour and will let you know
after flashing all went good and phone booted with no problem, except that i don't have a wi-fi, it is connected after typing my password in, wifi icon is on home screen, but could not enter any website or connect to my google account. any ideas?
Try flashing this: http://code.google.com/p/ice-cream-.../detail?name=WifiFix.zip&can=2&q=#makechanges
Sent from my Captivate running Android 4.0.3 ICS
capocaccia said:
Try flashing this: http://code.google.com/p/ice-cream-.../detail?name=WifiFix.zip&can=2&q=#makechanges
Sent from my Captivate running Android 4.0.3 ICS
Click to expand...
Click to collapse
so after flashing that file my phone gives me screen like this
Power Reset or Uknown Upload Mode
and it is stucked. so may i pull the battery off and go to recovery mode again and go back to my previous room? should i perform system format in this case?
Try to reboot. If it won't reboot then ask around in the icssgs Q and A thread.
Sent from my Captivate running Android 4.0.3 ICS
capocaccia said:
Try to reboot. If it won't reboot then ask around in the icssgs Q and A thread.
Sent from my Captivate running Android 4.0.3 ICS
Click to expand...
Click to collapse
with keys+power button combination i've been able to exit that screen and reinstalled 4.0.3
do you know safe way how do i go back to SimplyStock KK4 V1.0? should i first flash CornKernel_UCKK4_v603 with odin? but is it safe to do over android 4.0.3?
sorry for bothering you, but i am kind of stucked
---------- Post added at 02:52 AM ---------- Previous post was at 02:33 AM ----------
ok, in the end managed to boot the phone with working wifi but still would like to know how to flash back to SimplyStock KK4 V1.0, just in case ;-) if that won't be problem for you. thank you !!!
IMHO the best way to go from gingerbread to ics 4.0 is to
- in the development section download stock kk4 without bootloaders, unless you dont have them http://forum.xda-developers.com/showthread.php?t=1300843
- then download a kernel of your choice probably cornkernal and put it on your internal sd card
- download ICS latest build and gapps and put them on your internal sd
- oneclick odin the stock kk4, let it boot up completely
- power off and install kernal via odin without aut reset
- boot into recovery, factory/data reset, clean cache, clear dalvik, install latest ics, then install gapps right after,
- reboot system and youre done.
IF you want to go back to your other rom the simplest way is to just kk4 fresh install, install kernal via odin, then isntall your rom.
I always keep all my contacts synced with gmail, and titanium backup any game data or app data i need, and reinstall apps through the market.
hope this helps
capocaccia said:
Yes, Froyo will still boot. If this were a layer cake it would go something like bootloader, kernel, rom. So basically, your bootloader has nothing to do with your kernel or your rom but it is at the bottom layer of the boot process. It does effect which ROMs you can use though as gingerbread and ICS roms require GB bootloaders. So flash the bootloaders, you will still be on Froyo. Update to GB. Root GB. Place the ROM on your internal SD and then flash it. If you run into any problems check the common problems page found on the first page of the SGSICS ROM.
First, if you want to keep any of your apps or contacts backup those as well using Titanium Backup. Make sure to backup to the External SD card or make a copy of the backup somewhere other than the phones internal SD.
Second, you dont have to wipe data/factory reset before you flash. This is only if you have the problem of a bootloop when you try to install. I had this problem and when I did the wipe data afterward it fixed it immediately. So follow this:
1: Boot into CWM
2: install rom
IF you have an issue with a boot loop at this point
1: Get back into CWM using the button combination
2: Wipe data/Factory Rest and Wipe Cach
Click to expand...
Click to collapse
Now can I go strait from Froyo to the ROM i listed in my OP?
okey, so at the end i decided to switch Doc's Master ICS and so far so good thank you all again for your support !!!!
mrnapolean1 said:
Now can I go strait from Froyo to the ROM i listed in my OP?
Click to expand...
Click to collapse
I gone ahead and flashed ICS onto my phone. It is working good but the Hang up button does not work. In order to hang up, i have to lock it and unlock it.
Now i did a Backup of Froyo from within CWM. if I do have a problem, can i go to DWM and restore the backed up Froyo?
hello, I installed [ROM][ICS] KingDroid ICS NoteMania Edition v2.0 and it worked, then I did a nandroid backup and after I installed the S3 optional MOD.
The phone worked fine for some days, then I wanted to delete the S3 MOD so I did a nandroid restore from the previous backup, something went wrong during restoring. So I tried to flash the ROM again from SDcard, I did a dalvik cache wipe and a cache wipe and after I tried to reflash the kingdroid rom from recovery, it flashed the kernel and hung during MODEM flashing.
Now when I turn on the phone it hangs on galaxy note logo.
How can I solve this situation? Go back to GB? How? PC ODIN?
Thanks
Please read the thread before doing anything. NEVER EVER RESTORE A NANDROID BACKUP FROM ICS KERNELS. I think you just did that and now you are a part of Superbrick family. I think just read threads about how to revive your bricked note and follow the procedure or Samsung service is the only way out
Check if your phone enters download mode ( power+home+volume down ). If so - you're not bricked and can flash GB stock rom with ODIN.
Akiainavas said:
Check if your phone enters download mode ( power+home+volume down ). If so - you're not bricked and can flash GB stock rom with ODIN.
Click to expand...
Click to collapse
It enters in download mode after warning me about the danger of flashign a custom os. So I canm proceed to flash a stock GB rom? N7000XILB1 ?
As you said your phone hangs on Samsung screen. When this thing happened first time with me i was too scared.
Dont panic. So you can go to download/Recovery mode. Flash a stok GB ROM. It worked for me. Dont worry about warning.
See Dr. Ketan's Thread for step by step guide. Carefully follow his instructions.
Best of luck..
chintamanijaipuri said:
As you said your phone hangs on Samsung screen. When this thing happened first time with me i was too scared.
Dont panic. So you can go to download/Recovery mode. Flash a stok GB ROM. It worked for me. Dont worry about warning.
See Dr. Ketan's Thread for step by step guide. Carefully follow his instructions.
Best of luck..
Click to expand...
Click to collapse
Do I need to replace the pit first? I think the kingdroid rom replaced the pit and created new different partitions, so if I put the stock rom won't it need the original pit? I'm lost on that.
..To be honest I go back and forth from GB to ICS to CM9 without any problems (maybe I'm one of the lucky guy and maybe at certain point I will brick as well!)...BUT what I do (when from ICS I move to GB) is to pass ALWAYS through AbyssNote Kernel 4.2.
So hoping you have a GB previous nandroid backup AND you can still enter in recovery modified mode, I would suggest the following steps
1. enter in recovery mode
2. flash the Abyss Kernel by choosing the zip
3. WITHOUT reboot the phone > go Advanced
4. re-boot recovery
5. once in Abyss kernel> factory reset, wipe cache, wipe dalvik cache
6. restore
7. choose GB backup
8. start restoring
Before learning about Abyss, I had very similar soft-brick like your one....but I easly managed it with the above method
Hope it helps
so, it was not super bricked. I flashed the pit and then Gb without any problem. now it's working.
Good deal, just make sure you read the stickies next time and don't restore nandroid backups in CWM (Use abyss kernel).
There's plenty of safe kernels now that have disabled the brick bug as a workaround though. If you want stock ICS, flash Franco or Speedmod kernels. If you want a CM9 rom, there's plenty of variations. There's also an aokp rom.
chriz74 said:
so, it was not super bricked. I flashed the pit and then Gb without any problem. now it's working.
Click to expand...
Click to collapse
Congrats.....
Its your lucky day.
Enjoy your note..
chriz74 said:
so, it was not super bricked. I flashed the pit and then Gb without any problem. now it's working.
Click to expand...
Click to collapse
GREAT DAY...thanks to this GREAT forum the way out is always possible....:thumbup:
Sent from my GT-N7000 using XDA
Before I begin, yes... I did search and look through a few threads with similar titles but did not find my problem.
I am not a phone geek and I am new to all this, but I rooted my Note along with a "Franco kernel", which worked successfully. My phone booted up as it was before (in fact I noticed absolutely no difference in my phone, whatsoever).
The problems begun when I tried to install an "Abyss" kernel via CWM, which apparently installed successfully, but the phone would never get past boot-up (not so successful after all, huh?). I realized that it wasn't going to work, so I though no problem, and went back into CWM and re-installed the Franco kernel that I was using before (which worked). Strangely, this kernel, too, would now no longer boot.
I successfully restored the phone with a GB rom via odin (teriible rom), and proceeded to install the so-called "Hydracore" kernel (love the names) via cwm.... this kernel made things even worse. Once again the installation was supposedly "successful", but the phone doesn't go past boot. This time, it gets stuck on a very dim black screen, which isn't actually black, it is a dark creamy/pink hue that you can only notice in absolute darkness. (WTF?) This screen has random black blotches on it, but again, if you are in a lit up room the screen looks completely black and you cannot tell that it is actually lit. When I say that this kernel made the problems even worse, I say that because when this happens (dim black screen), I cannot even enter CWM recovery at all to try and install a different kernel. From here, I can only access download mode, and have no choice but to restore the phone with the GB rom via odin. I did so, and proceeded to install the latest version of "Hydracore" (v5.4) posted right here on XDA by the member 'chasmodo.' This time, I did the installation of the kernel via odin, which, once again, was supposedly successful... and once again a lie, as the phone just goes into the same black screen, with no option other than download mode.
The sole reason I have wasted hours of my life researching and understanding mobile phone terminology in the past few days is so that I can have jellybean on my Note. It seems that I am unable to do this because the Kernels are not working on my device. I have a very powerful and capable phone, which is currently stuck on this GB rom (which I think has to be the most terrible piece of coding ever made) so any help on this would be immensely appreciated.
Thanks in advance.
can you try go back to stock GB rom.. then upgrade to ICS and root using Dr Ketans method and then install Hydracore
You flashed Hydracore on GB rom? that's the main reason behind your problem, this Kernel is not for GB. Now either flash custom GB kernel or flash stock GB firmware using pc odin and then root it. Check post # 2 in this thread for rooting. (I guess you know how to do this )
Once you have root and cwm recovery, you can flash any custom rom you want.
jeetu1981 said:
You flashed Hydracore on GB rom? that's the main reason behind your problem, this Kernel is not for GB. Now either flash custom GB kernel or flash stock GB firmware using pc odin and then root it. Check post # 2 in this thread for rooting. (I guess you know how to do this )
Once you have root and cwm recovery, you can flash any custom rom you want.
Click to expand...
Click to collapse
Hot damn you guys are quick!
Silly me! :silly:
If I install any GB kernal can I then install CM10?
S-pen said:
Before I begin, yes... I did search and look through a few threads with similar titles but did not find my problem.
I am not a phone geek and I am new to all this, but I rooted my Note along with a "Franco kernel", which worked successfully. My phone booted up as it was before (in fact I noticed absolutely no difference in my phone, whatsoever).
The problems begun when I tried to install an "Abyss" kernel via CWM, which apparently installed successfully, but the phone would never get past boot-up (not so successful after all, huh?). I realized that it wasn't going to work, so I though no problem, and went back into CWM and re-installed the Franco kernel that I was using before (which worked). Strangely, this kernel, too, would now no longer boot.
I successfully restored the phone with a GB rom via odin (teriible rom), and proceeded to install the so-called "Hydracore" kernel (love the names) via cwm.... this kernel made things even worse. Once again the installation was supposedly "successful", but the phone doesn't go past boot. This time, it gets stuck on a very dim black screen, which isn't actually black, it is a dark creamy/pink hue that you can only notice in absolute darkness. (WTF?) This screen has random black blotches on it, but again, if you are in a lit up room the screen looks completely black and you cannot tell that it is actually lit. When I say that this kernel made the problems even worse, I say that because when this happens (dim black screen), I cannot even enter CWM recovery at all to try and install a different kernel. From here, I can only access download mode, and have no choice but to restore the phone with the GB rom via odin. I did so, and proceeded to install the latest version of "Hydracore" (v5.4) posted right here on XDA by the member 'chasmodo.' This time, I did the installation of the kernel via odin, which, once again, was supposedly successful... and once again a lie, as the phone just goes into the same black screen, with no option other than download mode.
The sole reason I have wasted hours of my life researching and understanding mobile phone terminology in the past few days is so that I can have jellybean on my Note. It seems that I am unable to do this because the Kernels are not working on my device. I have a very powerful and capable phone, which is currently stuck on this GB rom (which I think has to be the most terrible piece of coding ever made) so any help on this would be immensely appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Hi there, sorry to hear of your challenges.
One thing to remember before flashing is the nature of safe / unsafe kernels. Equally as important is compatible / non compatible kernels. It's not clear from your post but did you flash Abyss on an ICS ROM? If so, Abyss is a GB kernel. It will install but the ROM wont run due to lack of compatibility.
Abyss is used by many as a Safe kernel, a base to flash a new ROM from . Alternatively, it can be used to "downgrade" to Gingerbread ROMs.
If you are intent on trying a JB ROM, I would suggest a doing a full wipe (use the numerous guides on XDA) and a kernel clean (jBroid Script Cleaner for example). Now, research Chasmodo's excellent Kernel Repository and choose a kernel. Hydracore 4.3 Standard is a good "benchmark" however you could try the Official CM10 kernel from Entropy. Reboot to Recovery and flash your JB ROM of choice.
You will now have "Full Wiped" (including Script Clean), installed a Safe (Compatible) Kernel and flashed a compatible ROM.
For what its worth, I found GB to be an excellent ROM, particularly 2.3.6 and 2.3.7. CheckROM was one of my favorite ROMs on the S2 and they didnt even feel the need (till recently) to make an ICS version.
I hope this helps. Please hit THANKS if it did.
Alba Donzo said:
Hi there, sorry to hear of your challenges.
One thing to remember before flashing is the nature of safe / unsafe kernels. Equally as important is compatible / non compatible kernels. It's not clear from your post but did you flash Abyss on an ICS ROM? If so, Abyss is a GB kernel. It will install but the ROM wont run due to lack of compatibility.
Abyss is used by many as a Safe kernel, a base to flash a new ROM from . Alternatively, it can be used to "downgrade" to Gingerbread ROMs.
If you are intent on trying a JB ROM, I would suggest a doing a full wipe (use the numerous guides on XDA) and a kernel clean (jBroid Script Cleaner for example). Now, research Chasmodo's excellent Kernel Repository and choose a kernel. Hydracore 4.3 Standard is a good "benchmark" however you could try the Official CM10 kernel from Entropy. Reboot to Recovery and flash your JB ROM of choice.
You will now have "Full Wiped" (including Script Clean), installed a Safe (Compatible) Kernel and flashed a compatible ROM.
For what its worth, I found GB to be an excellent ROM, particularly 2.3.6 and 2.3.7. CheckROM was one of my favorite ROMs on the S2 and they didnt even feel the need (till recently) to make an ICS version.
I hope this helps. Please hit THANKS if it did.
Click to expand...
Click to collapse
Yes, I forgot to mention that when I rooted it I was running official 4.0.3 which I got OTA. After I rooted I tried the Abyss kernel. I had read that if you try and install CM10 straight from ICS you can brick, and that you had to downgrade to GB to do this. There must have been a misunderstanding on my part as I though that installing Abyss would downgrade me to GB.
What I don't understand is that I have now installed a GB rom, yet the Abyss gb kernel still does not work.
The two members that posted mentioned that I should root, though I did mention in the OP that it is already rooted... Am I missing something?
Anyway, I want to avoid having to download any more big files. I already have the latest "nightly" build of CM10 in my SD card. Is there any GB kernel that I can install from where I am now that would make it safe to install the CM10 zip?
S-pen said:
Yes, I forgot to mention that when I rooted it I was running official 4.0.3 which I got OTA. After I rooted I tried the Abyss kernel. I had read that if you try and install CM10 straight from ICS you can brick, and that you had to downgrade to GB to do this. There must have been a misunderstanding on my part as I though that installing Abyss would downgrade me to GB.
What I don't understand is that I have now installed a GB rom, yet the Abyss gb kernel still does not work.
The two members that posted mentioned that I should root, though I did mention in the OP that it is already rooted... Am I missing something?
Anyway, I want to avoid having to download any more big files. I already have the latest "nightly" build of CM10 in my SD card. Is there any GB kernel that I can install from where I am now that would make it safe to install the CM10 zip?
Click to expand...
Click to collapse
If I were on a GB ROM and wanted to run CM10 I would Full Wipe (including Cache and Dalvik) then do the following -
Flash Official CM10 kernel.
Reboot to Recovery (do not go straight to ROM flash)
Once back in Recovery, flash the CM10 ROM.
Reboot device.
Alba Donzo said:
If I were on a GB ROM and wanted to run CM10 I would Full Wipe (including Cache and Dalvik) then do the following -
Flash Official CM10 kernel.
Reboot to Recovery (do not go straight to ROM flash)
Once back in Recovery, flash the CM10 ROM.
Reboot device.
Click to expand...
Click to collapse
So the official CM10 kernel is a gb kernel? Because remember that is what I'm currently on.
And just to make sure I got you... wipe everything, install kernel (I don't understand what you mean by "go straight to rom flash"), but then not "reboot system", instead "reboot to recovery", then install CM10 rom?
Also, when you say a "full wipe" do you mean that it will erase everything like a factory reset and delete all my apps and everything else? And is there anyway to install CM10 without doing this or is that the only way?
Cm10 kernel is a jelly bean kernel, so gb rom will not run under it.
Full wipe does mean erasing everything. Coming from gb, there is no other way to install, you need a full wipe, remember, you're updating two full revisions of the os, so it's not surprising a full wipe is needed. If you're worried about your apps, root gb before upgrading and use titanium backup to backup you're apps and then restore them when on cm10.
Sent from my GT-N7000 using xda premium
Alba Donzo said:
If I were on a GB ROM and wanted to run CM10 I would Full Wipe (including Cache and Dalvik) then do the following -
Flash Official CM10 kernel.
Reboot to Recovery (do not go straight to ROM flash)
Once back in Recovery, flash the CM10 ROM.
Reboot device.
Click to expand...
Click to collapse
If you are on rooted GB Rom and want to flash a custom JB or ICS one, this is what you do:
1. drop into recovery
2. do a full wife™ (factory reset, wipe cache and dalvik)
3. flash your JB/ICS Rom
4. reboob
Nothing else is needed, no intermediate steps like flashing another kernel in between, and especially no running Jbroid or Sybr kernel cleaning script.
chasmodo said:
If you are on rooted GB Rom and want to flash a custom JB or ICS one, this is what you do:
1. drop into recovery
2. do a full wife™ (factory reset, wipe cache and dalvik)
3. flash your JB/ICS Rom
4. reboob
Click to expand...
Click to collapse
How original was that....
Sent from my GT-N7000 using xda premium
SpyderTracks said:
If you're worried about your apps, root gb before upgrading and use titanium backup to backup you're apps and then restore them when on cm10.
Click to expand...
Click to collapse
Once again, my phone is already rooted... I have mentioned this several times.
chasmodo said:
If you are on rooted GB Rom and want to flash a custom JB or ICS one, this is what you do:
1. drop into recovery
2. do a full wife™ (factory reset, wipe cache and dalvik)
3. flash your JB/ICS Rom
4. reboob
Nothing else is needed, no intermediate steps like flashing another kernel in between, and especially no running Jbroid or Sybr kernel cleaning script.
Click to expand...
Click to collapse
You telling me that I can safely go straight to JB from my current GB rom and kernel?
I already have a "nightly" JB rom on my SD card, so just to be clear, all I do is go into CWM recovery, do a "full" wipe (how do I do that by the way?) and install the JB rom from zip?
Yes, you can go ahead. Just follow the instructions kindly provided by chasmodo.
But please, do not forget to flash GApps after you flashed the JB "nightly ROM which is on your SD Card". Otherwise you won't have Google account, play store etc yada yada.
Full wipe (aka full-wife™) means wipe data/factory reset. Nothing else.
AA1973 said:
Yes, you can go ahead. Just follow the instructions kindly provided by chasmodo.
But please, do not forget to flash GApps after you flashed the JB "nightly ROM which is on your SD Card". Otherwise you won't have Google account, play store etc yada yada.
Full wipe (aka full-wife™) means wipe data/factory reset. Nothing else.
Click to expand...
Click to collapse
Great! I am downloading the GApps for JB now. How do I install them? I understand that this is also done through CWM recovery, but how do I instal them? do I install the JB rom and reboot to recovery and then just install GApps from zip before rebooting system?
Also, does the full wipe have to be done in CWM recovery, or can I just do the normal wipe on the phone menu before entering recovery?
You flash the ROM by pointing the recovery to the "ROM.zip", the same is valid for "GApps.zip".
So you do the following, no reboot in recovery in between those 2 steps!
Install zip (from where it is located, internal/external SD )
*ROM.zip
*Gapps.zip
*reboot system
Wipe data/factory reset is done (most of the times) in recovery. Just get used to it. Saves you some bad habits on doing it on stock ICS ...
AA1973 said:
You flash the ROM by pointing the recovery to the "ROM.zip", the same is valid for "GApps.zip".
So you do the following, no reboot in recovery in between those 2 steps!
Install zip (from where it is located, internal/external SD )
*ROM.zip
*Gapps.zip
*reboot system
Wipe data/factory reset is done (most of the times) in recovery. Just get used to it. Saves you some bad habits on doing it on stock ICS ...
Click to expand...
Click to collapse
OK install ROM and then install GApps straight away, got it.
Just about the wipe, is it a simple one button wipe that wipes everything, or are there several things that I have to wipe independently? This is the part I'm not too sure about.
Just go into recovery and have a look. I mean, a really close look! Your topic was "need help to install a kernel" not "I don't know how to use recovery and please can someone come over to my place in order to explain me CWM recovery".
Sorry. Everything has been explained. Can't (or rather dont want to) help you further than what has been already mentioned. Period.
AA1973 said:
Just go into recovery and have a look. I mean, a really close look! Your topic was "need help to install a kernel" not "I don't know how to use recovery and please can someone come over to my place in order to explain me CWM recovery".
Sorry. Everything has been explained. Can't (or rather dont want to) help you further than what has been already mentioned. Period.
Click to expand...
Click to collapse
That's fine. I'll go into recovery and have a look. Thanks for the help that you did give anyway.
It worked! I have been messing around with my new Note on Jellybean and looking through all the settings. It doesn't have project butter (or at least the project wasn't very successful), but still miles ahead of Touchwiz.
Just want to extend a big thanks to everyone that has helped me out. Much appreciated.
Hi all,
I'm still using my Galaxy S on Froyo and don't feel I need to upgrade to a new handset yet but I would like some advice on rooting and getting my phone updated to the latest and greatest F/W (Custom or standard) so that I can get the best out of my phone and give it a new lease of life. Can anyone point me in the right direction? I've already used Odin a while ago to update from Eclair to Froyo so I've had a bit of experience with this apart from rooting and loading custom ROM's Any help or advice would be much appreciated.
th3rmi1t3 said:
Hi all,
I'm still using my Galaxy S on Froyo and don't feel I need to upgrade to a new handset yet but I would like some advice on rooting and getting my phone updated to the latest and greatest F/W (Custom or standard) so that I can get the best out of my phone and give it a new lease of life. Can anyone point me in the right direction? I've already used Odin a while ago to update from Eclair to Froyo so I've had a bit of experience with this apart from rooting and loading custom ROM's Any help or advice would be much appreciated.
Click to expand...
Click to collapse
download 2.3.6 Firmware from this thread
http://forum.xda-developers.com/showthread.php?t=1102881
then download CM 9 from
http://get.cm/?device=galaxysmtd and flash
if you want JB , install any costum rom from development section
The Tox said:
download 2.3.6 Firmware from this thread
http://forum.xda-developers.com/showthread.php?t=1102881
then download CM 9 from
http://get.cm/?device=galaxysmtd and flash
if you want JB , install any costum rom from development section
Click to expand...
Click to collapse
Thanks for that. What is CM9? Will I need to root first?
I've just attempted rooting. Does this result from Odin look normal?
Hey, Tox. Thanks for the advice. Why CM9? There are later versions, is CM9 the most stable? I'd like to try Slim Bean. Do I need to install that CM9 before I attempt to put Slim Bean on? Also, will I need any other files/apps? I've checked that my i9000 is rooted ok by doing an su in a terminal emulator.
Could anybody point me to a straight forward tutorial which could help me from where I'm currently at?
I've now installed clockworkmod recovery and created a backup to the SD card in recovery mode. I'm guessing the next steps should be pretty straight forward. I just need to know which files I have to download. What's the best Slim Bean for me to try and what other apps should I install with it?
Ok, I've screwed up. I installed clockworkmod recovery and created a backup. I tried flashing the latest Slim Bean ROM and addon pak but my phone wouldn't connect to the cell network. I attempted to recover from the backup using CWM but my phone is now stuck in a bootloop with the Samsung splash screen. Can anybody help me please?
th3rmi1t3 said:
Ok, I've screwed up. I installed clockworkmod recovery and created a backup. I tried flashing the latest Slim Bean ROM and addon pak but my phone wouldn't connect to the cell network. I attempted to recover from the backup using CWM but my phone is now stuck in a bootloop with the Samsung splash screen. Can anybody help me please?
Click to expand...
Click to collapse
you lost your IMEI , that's why i told you to flash CM9 first , to avoid loosing IMEI ,
reflash 2.3.6 firmware via odin , root it , flash CM9 , then flash slim bean rom
Thanks. I've just flashed 2.3.6 again and then applied CWM recovery but it still boot loops. Do you know why I couldn't just restore from the backup I'd created?
How can I flash the CM9 pack with Odin? It's a ZIP folder and wont recognise it. Please help.
Is there any other way around this? I've just installed SB again with the addon pack just so that I could get the CM9 onto my SD card. What's the best way to sort this out and get my IMEI number sorted?
Can anyone help me at all?? I have the IMEI number in the back of the phone if that's any use?
th3rmi1t3 said:
Is there any other way around this? I've just installed SB again with the addon pack just so that I could get the CM9 onto my SD card. What's the best way to sort this out and get my IMEI number sorted?
Click to expand...
Click to collapse
this how to install cm 9
Put it ( zip file ) to your phone's internal sd-card
Reboot to recovery (vol up + home + power)
Wipe data/factory reset
Wipe cache
Advanced > wipe dalvik cache
Install zip from sd-card
Choose zip from sd-card
Select cm-9.0.0-galaxysmtd.zip
Confirm
Wait
Go back
Reboot
the same you way you do with a JB rom
and please push thanks button ,
Thanks for the reply T. So should I do a full wipe (Wipe data/factory reset Wipe cache Advanced > wipe dalvik cache) before installing 2.3.6, then apply the CWM update followed by your instructions above? Will that recover my IMEI because, as you said, it's definitely no longer there.
I've just wiped everything and installed GB 2.3.6 and got the following messages. Does this look ok? Also, after I'd done that, I rooted it with CWM then tried installing the latest stable CM10 but now when I reboot, it shows the CM/Samsung screen as if it was booting then it just goes back to the CWM recovery What do I do now??
Success!
I've just powered up my phone again and suddenly the Cyanogen startup screen appeared! I powered down and put the SIM back in from my backup phone and I'm back on the phone network. I was reading up on lots of other complicated ways of recovering the IMEI and this has been really straight forward. I'm liking the Cyanogen 10.1.2 so far so might stick with that. Thanks so much for your help TT!
So to answer a few of your questions, I know I'm late to the party but for future reference
-The reason why Tox recommended flashing CM9 first is because problems can occur going straight from 2.3.6 to Jelly Bean in terms of your IMEI- your device's "identification". If you lose the IMEI, you lose the ability to connect to your network provider. Flashing CM9 and letting it boot as an intermediate step prevents this from happening. Once you've booted CM9 when you flash and you have reception, you're all goods to flash any JB rom from there.
-Your bootloop from recovering the backup that you made from Slim- I'm guessing it was a backup from 2.3.6- has nothing to do with the IMEI. Phones can boot without the IMEI. Its because the data partitions in 2.3.6 are different to those in Jelly Bean. Hence they're incompatible with each other- you tried to restore a different data partition that what was available on Slim Bean (because it was Jelly Bean).
-Flashing any 2.3.6 rom will restore your IMEI. However regarding the photo you took with the red error messages...
-That's because of the reason I mentioned above, with the data partitions. Because they're different, the phone can't recognise them and so can't boot, hence resulting in a bootloop. Easy way to fix this- there's a file called dbsdata.rfs.tar (its somewhere in these forums, right now I can't find a link). If you get that situation again, just pul the battery and reinsert it, go back into download mode, put dbsdata.rfs.tar in PDA, let it flash. That should put the right data partition on the phone.
Hope that these clarified some of your questions!
Sent from my GT-P7510
Thanks for the tips and clarifying all that for me Soryuu. Much appreciated. Now I've learned a little more, I can have a play around with different ROMS with a bit of confidence. :good: Any suggestions on good things to try out? I think I still need to apply some add-on's for this CM10.1.2 build as I don't have market place, google, FB etc.
th3rmi1t3 said:
Thanks for the tips and clarifying all that for me Soryuu. Much appreciated. Now I've learned a little more, I can have a play around with different ROMS with a bit of confidence. :good: Any suggestions on good things to try out? I think I still need to apply some add-on's for this CM10.1.2 build as I don't have market place, google, FB etc.
Click to expand...
Click to collapse
Don't forget your Gapps ;3 (most roms need them to be flashed seperately)
Good things to try out as in?
Sent from my GT-P7510
Hi everybody,
just got an old yet effective SGS and I wanted root and get rid of touchwizz and all the crap from my carrier
I was unable to boot into DL mode, i tried everything, so I had to do it with adb reboot
I never had to use Odin to do my hacking with android so i'm not used to it but short story : I rename my rom.zip into rom rom.tar, it failed and all I have is this now :
https://www.dropbox.com/s/wk42jbmp33a3ftu/IMG_20140715_152917.jpg
Also I need to unsimlock, flashing a new rom will also do the trick right ?
thanks
What you just did is bricking your phone. It it was a zip file you need to install it from the recovery. Renaming it is not the way it works. I'm not sure if now you can fix it. Sorry, man
Sent from my GT-I9000 using XDA Premium 4 mobile app
Do you know what I can at least try?
If you can get into download mode:
Follow sections 2 and 3 in this guide.
If you can't:
Follow this guide and after that do what I sails to do if you have download mode.
Does 3-button-combo not work to get into the download mode?
(power & home & volume down)
tetakpatalked from Nexus 7 flo
so i tried the resistance thing but i was unable to find all of the part required so i bought one of these already done solution thingy
It worked, I'm now able to boot into DL mode
I also succesfully install a random 2.x rom from an unknown european carrier, no root, lots of crap installed, and simlocked
How do i get from that to my CM 11 rom ? (this time it's in .tar format via 7zip ^^')
I tried via Odin in PDA it says fail right away
what can I do ?
thanks fr all the answers guys
@Idealith simlock has nothing to do with the firmware.
You need now any root kernel for that firmware, it has to be compatible with the intiframs of your 2.x version and it will give you a custom recovery.
There you can flash first CM10.2 to get the modified partition sizes and KK ready recovery and after that you can flash CM11
IMHO, the new Mackay ICS 2014 rom based on CM9 is a lot faster than any KitKat and works better on the i9000
tetakpatalked from N7100
my question about the rom still applies cause this one is awful
but with what does it have to do then ?
EDIT : my browser didn't render the end of your answer
I'm afraid i'm not following though :/
I got my 2.3 rom to stop crashing
and I once boot into recovery mod idk how ..
I selected the 10.2 CM rom but it started rebooting over and over again
I'm really not following everything that is happening over here :/
Idealith said:
I got my 2.3 rom to stop crashing
and I once boot into recovery mod idk how ..
I selected the 10.2 CM rom but it started rebooting over and over again
I'm really not following everything that is happening over here :/
Click to expand...
Click to collapse
Hey, could you tell me which country you are at? I could then take a few steps to help you
PFFFFFFFFFFFFFFFFTTT, sent from my i9000
I am currently in France
last news : been able to reboot into CWM, I selected the mackay cm 9 based rom, it rebooted halfway thrugh only to reboot in TWRP (idk how, are both installed or is twrp in the rom too ???)
so i tried from twrp wiping everything before and it wen through, then on bot it told me it needed to factory reset, it never worker though
so now i can boot into CWM but can't access my sd card ...
thanks
Idealith said:
I am currently in France
last news : been able to reboot into CWM, I selected the mackay cm 9 based rom, it rebooted halfway thrugh only to reboot in TWRP (idk how, are both installed or is twrp in the rom too ???)
so i tried from twrp wiping everything before and it wen through, then on bot it told me it needed to factory reset, it never worker though
so now i can boot into CWM but can't access my sd card ...
thanks
Click to expand...
Click to collapse
It was perfectly normal behavior, as after flashing the zip from CM, it will in firat step upgrade your recovery to TWRP 2.2.2.0
As you have wiped already before, it would be perfectly fine to just flash the rom.zip in the new TWRP recovery, and your gapps right afterwards. The recovery upgrade is totally common on the i9000 as first step.
The i9000 can easily be unbricked by flashing a stock image with Odin.
tetakpatalked from Nexus 7 flo
tetakpatak said:
It was perfectly normal behavior, as after flashing the zip from CM, it will in firat step upgrade your recovery to TWRP 2.2.2.0
As you have wiped already before, it would be perfectly fine to just flash the rom.zip in the new TWRP recovery, and your gapps right afterwards. The recovery upgrade is totally common on the i9000 as first step.
The i9000 can easily be unbricked by flashing a stock image with Odin.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
I suppose my phone has been unbricked I made a 2.3 stock rom work
What i do now :
I flash the stock rom, go back to DL mode, flash the recovery, take the battery off, boot back in recovery, wipe everything ( do I really have to wipe system and all ?), select the ROM, nd once I'm in TWRP i reselect than same ROM
for the cm9 based mackay one it keep rebooting over and over again
for CM 10.2 it says the encryption failed and I need to factory reset, then nothing works
Idealith said:
I suppose my phone has been unbricked I made a 2.3 stock rom work
What i do now :
I flash the stock rom, go back to DL mode, flash the recovery, take the battery off, boot back in recovery, wipe everything ( do I really have to wipe system and all ?), select the ROM, nd once I'm in TWRP i reselect than same ROM
for the cm9 based mackay one it keep rebooting over and over again
for CM 10.2 it says the encryption failed and I need to factory reset, then nothing works
Click to expand...
Click to collapse
Yes, that would be correct procedure. To install CM9 you will have to format data, cache and dalvik cache.
If you have never had a JVU or JVZ firmware installed, it is likely that you still have a Froyo bootloader which could be reason of the problems with Android 4.xx
tetakpatalked from N7100
tetakpatak said:
Yes, that would be correct procedure. To install CM9 you will have to format data, cache and dalvik cache.
If you have never had a JVU or JVZ firmware installed, it is likely that you still have a Froyo bootloader which could be reason of the problems with Android 4.xx
tetakpatalked from N7100
Click to expand...
Click to collapse
and how do i get that bootloader set up ?
Idealith said:
and how do i get that bootloader set up ?
Click to expand...
Click to collapse
Either by flashing a whole JVU or JVZ stock firmware, or by flashing a bootloader only.
Check my sticky thread here under the same section (help & troubleshooting), I have described whole the procedure in the OP. I have even attached the files and also video is there: http://forum.xda-developers.com/showthread.php?t=2444308
Right point would be to do it first.
tetakpatalked from N7100
tetakpatak said:
Either by flashing a whole JVU or JVZ stock firmware, or by flashing a bootloader only.
Check my sticky thread here under the same section (help & troubleshooting), I have described whole the procedure in the OP. I have even attached the files and also video is there: http://forum.xda-developers.com/showthread.php?t=2444308
Right point would be to do it first.
tetakpatalked from N7100
Click to expand...
Click to collapse
thanks you so much i have now CM 10.2 running
would you know by any chance how to un simlock it ?
Idealith said:
thanks you so much i have now CM 10.2 running
would you know by any chance how to un simlock it ?
Click to expand...
Click to collapse
Ask your carrier, I assume the phone contract isn't new anymore (or expired) so you'll get unlock code for free. Here in Europe one can obtain the unlock code after 2 years for free.
Otherwise you can ask one of the online unlock services, it costs usually around 15-20$ to get the code
tetakpatalked from N7100
Idealith said:
so i tried the resistance thing but i was unable to find all of the part required so i bought one of these already done solution thingy
It worked, I'm now able to boot into DL mode
I also succesfully install a random 2.x rom from an unknown european carrier, no root, lots of crap installed, and simlocked
How do i get from that to my CM 11 rom ? (this time it's in .tar format via 7zip ^^')
I tried via Odin in PDA it says fail right away
what can I do ?
thanks fr all the answers guys
Click to expand...
Click to collapse
I'm glad that the JIG helped you (I know I'm late )
danielbe said:
I'm glad that the JIG helped you (I know I'm late )
Click to expand...
Click to collapse
yeah that worked like a charm
it was a good idea to buy it, i would have use the resistors so much
is there a more xda way to unlock it ? my carrier wants me to send the phone and have it unlock, they won't just provide the code :/