Hi, this is my first post. I'm a total noob in customizing phones and since my phone is quite old, all the information I can find is years old, talking about file versions that don't exist anymore, or became outdated since there are so many different versions of android.
I have been trying to find a good guide to help me do the correct steps to follow to flash Cyanogenmod. I might try the latest 12.1, and then see if I like it.
This is what I have so far:
- international i9100, I live in panama if that's relevant to any help I need
- stock ICS 4.0.3 (with XWLP7 kernel)
- used superoneclick to root, it installed CMW PhilZ touch 6.0.1.7 (I think, can't remember the last digit.)
- used "galaxy s unlock" app to unlock the phone
I downloaded this: philz_touch_6.07.1-i9100 from d-h.st/hUX, sorry I can't post the links correctly for being a new user.
I just made a backup before i will attempt to load philz touch 6.07.1. I read that I need to have a kitkat compatible recovery, is this one compatible. Can I simply flash it or do I need to do anything specific before.
I am trying to follow the steps explained in wiki.cyanogenmod.org/w/Install_CM_for_i9100, but the warnings scare me a bit, can someone please explain the workarounds, thanks.
So, what I'd like to know is the specific steps for my version of android to make it migrate to CM12.1, and what to do about the warnings (should i find a custom kernel, do i need to backup anything else, I read also that the recovery I have doesn't backup efs, so how can I do that?)
Thanks a lot for taking your time to help me out.
@milen_506
So when you reboot into recovery, you have philz recovery?
If yes, all you need to do is install a newer recovery such as the one from this post. Once you flash it, reboot straight back to recovery(you will get a bootloop if you try to reboot into the system). This newer recovery is compatible with the latest versions of android and gapps, so just need to have the rom .zip and gapps(if you want play store/services) .zip ready to flash before you upgrade this recovery. Do a nandroid backup before you flash the new rom/gapps
There are several ways to backup efs, HERE is a link to one option
And as far as custom kernels, you are probably better off sticking to the kernel that comes with the rom unless you are comfortable adjusting kernel settings and you know what you are doing. It would be easy to mess things up if you didin't have a basic knowledge of the changes. Also with cm12/LP roms on the S2, custom kernels are only starting to be developed and are a little unstable for some users at this stage.
Related
Hi all,
I expect to receive my new SGSII in the next few days, but want to make sure that I have a full backup concept in place, so that I can always get back to a state that I want.
At the moment I am not too concerned with custom ROMs, just the abaility to Backup the state of my own device, and then bviously be able to restore it later.
My current intention is the following,
1) Get SGSII
2) Perform root as per thread- http://forum.xda-developers.com/showthread.php?t=1056334&page=1' by Chainfire.
3) Then install 'Titanium Backup Root' (To be able to backup application settings, and freexe apps where necessary)
4) Install ROM Manager from ClockWorkMOD.
5) Flash ClockWorkMOD Recovery(requires Custom Recovery image to have been developed by ClockWorkMOD devs).
6) From Custom Recovery select Nandroid and created backup.
7) Then if needed repeat step 5 then perform Nandroid Restore.
My concern is regarding Step 5. As I read it someone needs to have written a custom recovery image for SGSII for this step to be possible. Does anyone know if a custom recovery image exists in ClockWorkMOD for SGSII? Or whether one is likely to come soon?
Secondly, is a better option to use SPRecovery and Nandroid backup\restore, or does this have the same Custom recovery image problem?
p.s. Does ClockWorkMOD Custom Recovery image replace the standard recovery image, or is it possible to backup this up somehow, so that I can always get back to the factory default.
Thanks
link does not work
AaronUK said:
link does not work
Click to expand...
Click to collapse
Fixed link, sorry about that
Clockworkmod will come soon. But the kernel devs need the full kernel sources, which have not yet been released. Once they are out work on adding clockworkmod will begin. I would say 2-3 Weeks max before clockworkmod.
My concern is regarding Step 5. As I read it someone needs to have written a custom recovery image for SGSII for this step to be possible. Does anyone know if a custom recovery image exists in ClockWorkMOD for SGSII? Or whether one is likely to come soon?
Secondly, is a better option to use SPRecovery and Nandroid backup\restore, or does this have the same Custom recovery image problem?
p.s. Does ClockWorkMOD Custom Recovery image replace the standard recovery image, or is it possible to backup this up somehow, so that I can always get back to the factory default.
Click to expand...
Click to collapse
Unlike what some people say, you don't actually need kernel source to make a kernel with CWM. It is by no means easy, and not always possible to do, but usually it's possible (the SGS2 kernels are weird, though).
There is no kernel with CWM yet. But I expect it won't take long. I'll probably get started on one as soon as I have an SGS2 myself (3 more weeks from now at least) - assuming I have time at that point. I won't even try before I have the device myself, too much things need to be tweaked / adjusted / tested for CWM.
Any decent recovery needs a custom kernel, SPRecovery, CWM, something homegrown, it's all the same A recovery tool needs to be in the kernel's file system to work perfectly. It can be done outside of the kernel's file system, but it'd be less reliable.
I'm saying kernel here instead of recovery image, because on previous Galaxy devices they are the same thing, unlike some other brands of Android devices. I'm not sure if it is the same thing with the SGS2 (yet), but so far I assume so (I have no reason to believe otherwise so far). In this case, it is usually not possible to actually backup your original recovery image, because you need root for this. But to get root, you need to flash a custom kernel. Do you see the cyclic reference? Luckily, we have the flash binaries for a fair number of firmwares, so it's possible you will actually be able to download your original recovery image and/or kernel.
Thanks for the clear explanation Chainfire, and for all the'Root' work thus far
Thanks for the explanation Chainfire, but I have a question. Is it safe now to root it before having the CWM? I mean can we restore the phone if we do something wrong and the phone comes to brick? It's the first time I use Android so I'll have many questions
In such a case you download a full firmware and flash that ...
i was wondering how i can backup firmware before rooting but now it clear that i don't need to as one can download and flash the full original firmware. Thanks for the info chainfire.
Chainfire said:
I'm saying kernel here instead of recovery image, because on previous Galaxy devices they are the same thing, unlike some other brands of Android devices. I'm not sure if it is the same thing with the SGS2 (yet), but so far I assume so (I have no reason to believe otherwise so far).
Click to expand...
Click to collapse
Checking the .PIT file, RECOVERY is blank which 99.9% means that the kernel and recovery are the same thing.
Unlike the SGS1 though, FACTORYFS and DATA seem to be two seperate images, which seems strange, since in the SGS1 data.img was inside factoryfs.img and was copied across whenever /data was blank. This might/might not have implications for custom roms.
Getting a bit confused about all this, so am wondering if i've got it right. A rom is the whole thing, it includes a kernel and so forth? So a Kernel is a part of the rom right? And you can flash kernels individually without flashing a whole new rom? But what is a firmware then? Just another name of a rom?
Also on the Galaxy S2 can you flash custom roms, like Lite'ning, without getting root first? Or do you need to get root before flashing custom roms? If you can flash custom roms first without rooting, will the custom rom then give you root as long as it includes it?
And you also got recovery, which is a separate thing again? Galaxy S2 comes with a very basic one if i've understood correctly, but there is others out there that you can install, which also gives you the ability of flashing roms straight from the microsd/phone storage?
So have i gotten any of this? Hope am not to far off
Edit: http://forum.xda-developers.com/showthread.php?t=1246131 looks like most of my questions where answered there, though am still a bit unsure if it's possible to flash a custom rom before you root?
ROM's and FIRMWARE: The ROM or Read Only Memory is the internal flash memory where the core operating system resides. The Firmware is a device specific part of the ROM that controls various hardware components. So the firmware is contained in the ROM but in the context of Android the terms are often used interchangeably.
KERNELS: Different kernels offer different advantages, some are fast, some are light weight on the battery and some are a mix, so yes you can in most cases flash a different kernel with a ROM, and then your phone will be running the custom ROM you picked with the new kernel you flashed.
Rooting: You must have a rooted phone inorder to flash a custom rom, but rooting in my opinion seems really safe and it really easy to do on the SG2
There are things that allow you to flash from your SD card and you do that by entering clockworkmod revovery, apps like rom manager also allow you to flash from sd card, but you can always use odin, which is safe and fast
hope this helps
Thanks, and very nicely explained =) Another question then, what is the reason one need root before you can flash custom firmwares? As i heard Galaxy S2 doesn't really have any safety measures put in to stop things, like HTC do with their bootloader. Another thing is that i checked the thread for the Lite'ning rom, and saw the installation procedure, and it doesn't mention anything about having root before starting, so am getting a bit confused there.
You don't need to root before flashing a custom ROM as long as you can enter download mode (power up with volume down, home and power button pressed) and can flash the ROM via Odin.
If the ROM is flashable only via ClockWorkMod recovery (a zip that you copy on your phone) then you need to flash something that includes that recovery before flashing the rom (like CF-Root or any kernel that includes CWM).
Lite'ning ROM that you mentioned earlier is flashable via Odin so no problem.
Every ROM includes a Kernel, the only thing they sometimes don't include is the modem like in VillainROM, you have to flash it separately. And also, if a ROM is announced as rooted, when you flash it, you will have root regardless of the state before flashing
Thanks once again =)
Another question, if one want to get back to stock, flashing one of these "official firmwares": http://forum.xda-developers.com/showthread.php?t=1075278 well revert everything right? Even if i got CWM recovery, after flashing on of those "official firmwares" will give me back the original recovery as well?
Edit: Also you mention "modem", if one ROM don't include one, do you have to flash it separately for the ROM to function at all? Or will it just use the modem that's already on the phone or something? Checked out the VillainROM thread and it doesn't say anything about a modem.
Nitrius said:
Another question, if one want to get back to stock, flashing one of these "official firmwares": http://forum.xda-developers.com/showthread.php?t=1075278 well revert everything right? Even if i got CWM recovery, after flashing on of those "official firmwares" will give me back the original recovery as well?
Click to expand...
Click to collapse
Yes it will revert back everything
Nitrius said:
Edit: Also you mention "modem", if one ROM don't include one, do you have to flash it separately for the ROM to function at all? Or will it just use the modem that's already on the phone or something? Checked out the VillainROM thread and it doesn't say anything about a modem.
Click to expand...
Click to collapse
If you dont flash a modem it will just use the one you had before. They talk about it in the old thread and also in the new but not in the firsts posts, you'll have to do a search.
Plus Modem Kernels are interchangeable .
KH3 Firmware with KI4 modem and KH1 kernel .
Guide
http://forum.xda-developers.com/showthread.php?t=1125282
jje
I bought sgs2 few weeks ago, had some fun with stock and samsung apps, then I decided that some changes would be nice
found this great forum, with all knowledge and I have to admit I'm overwhelmed and kinda lost.
rooted my phone with Doomlord method (zerg rush exploit), worked like a charm, installed Titanium Backup, that went smoothly too. From what I understand that didn't change flash counter so I can unroot and keep my warranty in case of hardware problems, am I right?
Then I installed ROM manager and here is where problems started, when I click Flash Recovery it's downloading some file, but when I boot to recovery mode, there is info about e: failed to verify whole-file signature and I can only reboot. If that failed, what did it exactly do with my stock firmware and flash counter? please forgive my noob questions, it's my first android device, I'm reading and learning, but it's a lot to process.
I have branded Play (polish provider) firmware (2.3.3, XWKE7) and I can't upgrade it, cuz I can't backup stock firmware with CWM, I'm afraid to flash without backup in case I need take my phone to samsung.
I would love to at least upgrade to 2.3.5 or try some nice custom roms you guy cook here so skillfully but need some advice any info will be greatly appreciated
Hey hey,
This happens to me too when I installed ROM Manager, and then Flashed a recovery. It does not boot into the orange ClockworkMod Recovery, instead it boots into the stock recovery saying an error.
Don't worry, it did not do anything bad to your phone, it just attempted to install the ClockworkMod recovery but just fails, no biggie All you have to do is flash a custom kernel through Odin, such as CF-Root or Ninphetamine, then you will have ClockworkMod Recovery installed by default. The flash recovery option is for other phones that do not have the secure kernel that Samsung installs into your phone by default.
I use CriskeloROM on my phone, in my opinion, this is my favorite ROM because of the constant updates and massive collection of add ons. It is currently running on 2.3.5 and has a base of XWKJ2. Check out the link in my signature for more details about the ROM.
thank you so much for your answer, good to know I didn't break anything (yet! )
as you advice I will take a look at Criskelo ROM
But I'm a bit (really) confused about a lot of things regarding this process. I've been reading for a week now and barely getting anywhere.
So first, a little history.
I'm running a stock vibrant, Froyo.UVKB5, 2.6.32.9 kernel, never been rooted.
Now, one of the main reasons for my upgrade is the loss of wifi connectivity. For some reason I can no longer connect to most ISP's or WIFI hotspots, especially my own.
Now, here's the kicker; I don't have a data package on my service so I am dependent on wifi only. Now that I can't get wifi, I'm not sure if I can get all the files I need to do this upgrade. I'm hoping this upgrade will reconnect me to wifi.
Reading through the Wiki for rooting (http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959), it says I am to use Superuser AND binary, is this correct?
I've found a boatload of Superuser files one the ClockworkMod ROM Manager website, ... which one do I use, there's no explanation?
And I understand I need to install SuperSU AFTER I have it rooted.?.
Regarding an updated OS, from the questions and remarks on this post (http://forum.xda-developers.com/showthread.php?t=1900763), I need both a kernel AND a rom? But other threads I've read say the kernel is in the ROM. Does this mean that CyanogenMod's CM7.2.0 is kernel only and doesn't get you anywhere?
Also from this thread, suggestions were made to upgrade to one kernel, then a rom, then to another kernel and rom, and finally to the kernel and rom the user wants. Why is this necessary?
I have many more questions but they branch off depending on answers to these fundamental questions here.
So, if there's anyone with enough patience and willing to hold my hand through this process, I would greatly appreciate it.
And I need to go cancel my monthly paid warranty fee on this old phone too.
ROMs typically include a kernel in their update zip. CyanogenMod is a ROM and as such includes our own kernel when you install it. Be aware of the 911 issues before upgrading your os to a custom rom.
Sent from my Galaxy Nexus using xda premium
To install Clockworkmod, if you are using Android 2.2 Froyo, go here: http://forum.xda-developers.com/showthread.php?t=833423
Run the "3e_recovery_installer" from your computer with the phone connected and USB debugging mode enabled. Then boot into stock recovery (Hold VOL+ and VOL- and POWER with the phone off, release when you see the logo) and flash the "update.zip" twice. It will boot into a green CWM that temporarily exist until you turn off the phone, beware that this temp CWM only let you flash zips from your Vibrant internal storage, it will not recognize your microSD.
Note: If you are using Eclair 2.1, you should be able flash the update.zip directly without the "3e recovery installer".
You can either flash root from CWM, or download a rom like SlimBean and flash it directly. When you flash a custom rom, it will install a newer version of CWM first (because the older version of CWM will not be able to flash the rom) and the phone will reboot. Take off the battery and put it back, boot into recovery again to see the new version of CWM, then you can install the custom rom again fully this time. Generally you should do a "wipe data and cache" before installing a rom, but sometimes, you might also need to go to "mount and storage" and format the /system folder before you can flash a new rom successfully. This can help avoid system files from your old Android installation to exist and merge with the new rom installation. However, the /system folder is where most of the OS important files are locate so without it the phone won't boot, so you need to have a custom rom in the phone (or microSD) to flash after you format it.
That should pretty much cover most of it. If you ever run into problems you can always use ODIN to recover the phone to factory stock. In fact, if you want to stay with stock and just want your WiFi to get fixed, its probably better to simply do an ODIN recovery (or a factory reset) first, before looking at custom roms.
Most of what I just said is covered in this sticky: http://forum.xda-developers.com/showthread.php?t=849028
Hi sirs,
The title says it all, I want to change back to stock rom or change to other custom roms but I am not sure what to do. I have cm12.1 nightly build 5.1.1 (i guess that's the name) currently installed in my phone. I followed a tutorial on how to do THINGS in my phone but I am unsure whether it will work or not. I am SO VERY VERY VERY new to these things and I don't know how to proceed. And also, i get confused of the terms like KERNEL or ROM and i kind of mixed them up. So I am here to ask for your help and clarification on my problem.
According to a tutorial that I've read, a custom recovery is needed. So, following a tutorial, I replaced the Cyanogenmod recovery with TWRP recovery. My questions are:
1. Is it safe to flash a ROM (like Omega Series Rom, which I kind of bumped in while doing research) over the current CM12.1 system?
2.Is there any patterns or magical incantations in order to flash a new rom into my device successfully? If so, can someone show me a step-by-step instructions?
3.Will it brick my phone if I missed a step?
I know this is too much to ask for, but please help me Sirs/Maams. I'm desperate. THANKS SO SO SO MUCH in advance.
P.S. Sorry if my english is so horrible. English is not my first language.
Sincerly,
Me
To install a new ROM, boot into recovery, and wipe /data and /cache and if you want also /system. After that install the ROM and Gapps zip files. Always double-check you're using & choosing the correct files. I recommend to always use the smallest possible Gapps package to make sure it fits into the /system partition.
Make sure you're using the right recovery. For example Cm12.1 needed a KitKat-compatible recovery for a successful install.
Notice that all apps and app data will be deleted at a new flash. In some cases, the recovery is included in the ROM, then it will overwrite the one you had before.
I personally think flashing a new ROM isn't that dangerous. There are more critical things, for example repartition. But there are some rare cases at almost every ROM where someone's phone dies, for whatever reason. So there's always a little risk. But even if you should succeed soft-bricking your phone, there already are some guides how to solve it.
And one more tip: in general, always read as much as possible about a ROM before flashing it. Avoid less documented ROM threads. You decide what you risk and do everything on your own responsibility.
I know this things are logical, but it seems as if there are still people flashing everything, reading nothing, spamming everything with their problems they get then
Hope I helped you a little bit.
BenjyTec said:
To install a new ROM, boot into recovery, and wipe /data and /cache and if you want also /system. After that install the ROM and Gapps zip files. Always double-check you're using & choosing the correct files. I recommend to always use the smallest possible Gapps package to make sure it fits into the /system partition.
Make sure you're using the right recovery. For example Cm12.1 needed a KitKat-compatible recovery for a successful install.
Notice that all apps and app data will be deleted at a new flash. In some cases, the recovery is included in the ROM, then it will overwrite the one you had before.
I personally think flashing a new ROM isn't that dangerous. There are more critical things, for example repartition. But there are some rare cases at almost every ROM where someone's phone dies, for whatever reason. So there's always a little risk. But even if you should succeed soft-bricking your phone, there already are some guides how to solve it.
And one more tip: in general, always read as much as possible about a ROM before flashing it. Avoid less documented ROM threads. You decide what you risk and do everything on your own responsibility.
I know this things are logical, but it seems as if there are still people flashing everything, reading nothing, spamming everything with their problems they get then
Hope I helped you a little bit.
Click to expand...
Click to collapse
Thanks for the reply kind sir.
So it's safe to flash a new ROM over the current CM12.1 system? And if so, will my current recovery (which is TWRP recovery) suffice for flashing a new ROM? or do I have to replace my recovery? If ROMs have compatibility issues with recovery systems, can you please give or show me a list of ROMs that can be flashed using TWRP recovery (I'm so sorry, I have don't completely understand these kinds of things).
Thanks for your help sir. I really appreciate it. And sorry for the questions.
ZaorotheFirst said:
Thanks for the reply kind sir.
So it's safe to flash a new ROM over the current CM12.1 system? And if so, will my current recovery (which is TWRP recovery) suffice for flashing a new ROM? or do I have to replace my recovery? If ROMs have compatibility issues with recovery systems, can you please give or show me a list of ROMs that can be flashed using TWRP recovery (I'm so sorry, I have don't completely understand these kinds of things).
Thanks for your help sir. I really appreciate it. And sorry for the questions.
Click to expand...
Click to collapse
It's safe to flash whichever rom you want over cm12.1. The only thing to keep in mind is whether it is a .zip file or .tar file(as for stock rom), which will tell you whether to use recovery(your TWRP is fine for this), or odin(for stock rom in .tar format)
But as BenjiTec said, READ, READ, READ before you go ahead and flash a rom. Always read the OP(first post) and maybe first 2 or 3 pages of the rom thread, plus the all the pages from when the rom version you want to flash was released(maybe 10-20 pages). You probably don't need to read ALL pages if it is an old version. Understand what you are doing, rather than follow steps blindly, and you will always know what to do in case of something going wrong
Thanks a lot sirs, both of you, BenjyTec and noppy22, for the clarification.
One last question (or sets of questions. sorry )
So I have decided that I will flash a stock ROM to my S2 from SamMobiles using Odin. Do I have to wipe the the /data, /system, etc. before flashing the stock ROM via Odin? Or i can just directly flash the ROM over the CM12.1 system and TWRP recovery? And I have searched a lot of the possible outcomes and failures (like Odin ROM installment failure). What are the chances that the installation will fail? And what do I do if it DID fail (let's hope not)?
I know that these kinds of questions have been already answered in many threads but I just want to have my answers DIRECTLY from experts. Not from old threads and guide thingies.
Again, THANK YOU SO MUCH for the clarifications and answers. GOD BLESS
ZaorotheFirst said:
Thanks a lot sirs, both of you, BenjyTec and noppy22, for the clarification.
One last question (or sets of questions. sorry )
So I have decided that I will flash a stock ROM to my S2 from SamMobiles using Odin. Do I have to wipe the the /data, /system, etc. before flashing the stock ROM via Odin? Or i can just directly flash the ROM over the CM12.1 system and TWRP recovery? And I have searched a lot of the possible outcomes and failures (like Odin ROM installment failure). What are the chances that the installation will fail? And what do I do if it DID fail (let's hope not)?
I know that these kinds of questions have been already answered in many threads but I just want to have my answers DIRECTLY from experts. Not from old threads and guide thingies.
Again, THANK YOU SO MUCH for the clarifications and answers. GOD BLESS
Click to expand...
Click to collapse
It doesn't matter so much whether you wipe before or after. The easiest way is:
1. Run odin on your pc
2. Connect your phone, after booting in download mode(turn off, then hold vol down, home, power buttons until samsung screen) Use a trusted data cable, not all cables work
3. Flash stock rom through odin until PASSED(untick reboot device/auto reboot before flash)
4. Disconnect phone, take battery out, then put it back in. Reboot to recovery(vol up, home, power buttons)
5. In stock(3e) recovery, do a factory reset
6. Reboot and leave it for 5-10 minutes until you get a brand new stock rom
Stock ROM installing succeeded! THANKS SO MUCH SIRS! THANKS for all the clarifications and answers to my questions! KUDOS to both of you!!!