Hello,
I have recently purchased a Galaxy S Advance phone, and I am quite new to the android os.
I have read already many guides and forums about the whole process of rooting / flashing etc, so I have some knowledge of the terminology.
I already have a rooted phone with GB on it (yes, I know JB is about to come out officially ) and I wanted to change some of the UI elements.
I installed the rom manager app by koush, but yet to use it because I saw that in the past that the phone wasn't supported.
My question is: Does ROM Manager support this phone? Can I go ahead and flash CWM on it from the rom manager app, and then use it to flash other roms?
If not, which is the best solution to backup and replace roms? ODIN?
Thanks,
Одг: Is Galaxy S advance supported with Rom Manager? If Not, other ways to change ROM
YMatrix said:
Hello,
I have recently purchased a Galaxy S Advance phone, and I am quite new to the android os.
I have read already many guides and forums about the whole process of rooting / flashing etc, so I have some knowledge of the terminology.
I already have a rooted phone with GB on it (yes, I know JB is about to come out officially ) and I wanted to change some of the UI elements.
I installed the rom manager app by koush, but yet to use it because I saw that in the past that the phone wasn't supported.
My question is: Does ROM Manager support this phone? Can I go ahead and flash CWM on it from the rom manager app, and then use it to flash other roms?
If not, which is the best solution to backup and replace roms? ODIN?
Thanks,
Click to expand...
Click to collapse
Other way to change roms is custom recovery. On GB TWRP, on JB CWM.
Sent from Galaxy S Advance
Thanks fro your quick reply!
And what about ROM Manager? Does it work in this device?
YMatrix said:
Thanks fro your quick reply!
And what about ROM Manager? Does it work in this device?
Click to expand...
Click to collapse
I think it is not working. It is not supported. Way we install custom ROMs: download ROM zip, transfer to SD, then go to recovery and install it from there.
I checked TWRP supported devices list (tried to link it but forum wont allow new users to link ) and I don't see the galaxy advance S on their list either.
Is there a special mod version for this device?
And another question, if installed, will this wipe the current phone data or just the recovery loader? Since I want to backup my current ROM (+ contacts, settings etc.) before doing anything sketchy...
YMatrix said:
I checked TWRP supported devices list (tried to link it but forum wont allow new users to link ) and I don't see the galaxy advance S on their list either.
Is there a special mod version for this device?
And another question, if installed, will this wipe the current phone data or just the recovery loader? Since I want to backup my current ROM (+ contacts, settings etc.) before doing anything sketchy...
Click to expand...
Click to collapse
You have GB? Look here.
On I9070 recovery is on the same partition as kernel. So it can't be installed separatly. It is ported. You need to install this kernel, or CoCore. If you install with Odin - you will increase binary counter. For installation with ADB shell, or Terminal emulator (app from market) you need root - and it will not increase bc.
So I am guessing I will use the dd command line way since it doesn't increase the binary counter (why would we want to do that ).
Is it possible to backup the current ROM before flashing it with the TWRP modified ROM?
And another thing, since I will be using other ROMs, how can i add the TWRP recovery loader to them (you said that the recovery is on the same partition as the kernel, making me believe that each ROM I load will need to have TWRP on it)?
YMatrix said:
So I am guessing I will use the dd command line way since it doesn't increase the binary counter (why would we want to do that ).
Is it possible to backup the current ROM before flashing it with the TWRP modified ROM?
And another thing, since I will be using other ROMs, how can i add the TWRP recovery loader to them (you said that the recovery is on the same partition as the kernel, making me believe that each ROM I load will need to have TWRP on it)?
Click to expand...
Click to collapse
No, only JetMOD have embendend kernel too. And it have TWRP.
Hm, another thing. You better use non binary counter increaing root method. But it need you to flash whole firmware with Odin. And maybe you loose data. But if you do not do factory reset - it will be ok.
Sorry, I didn't understand your last post.
YMatrix said:
Sorry, I didn't understand your last post.
Click to expand...
Click to collapse
If you want to get TWRP with dd command you need to root your phone first.
There are 2 root methods. One that increase binary counter, and one that do not..
With one that do not increase - you need to flash whole firmware with Odin. And by doing that you might need to do factory reset. That will cause your data and app delete. You can try to boot, maybe it will be ok.
Oh, I already said I have a rooted device, so this wont be an issue.
What I asked was:
1) If I can backup my current ROM before installing the TWRP ROM you linked (in case something goes wrong).
2) When I install other modified ROMs, will they override the TWRP I installed, or just change the kernel system leaving TWRP in the recovery?
Одг: Is Galaxy S advance supported with Rom Manager? If Not, other ways to change ROM
YMatrix said:
Oh, I already said I have a rooted device, so this wont be an issue.
What I asked was:
1) If I can backup my current ROM before installing the TWRP ROM you linked (in case something goes wrong).
2) When I install other modified ROMs, will they override the TWRP I installed, or just change the kernel system leaving TWRP in the recovery?
Click to expand...
Click to collapse
Didn't pay attention.
You have backup option in TWRP, and you can restore it.
Custom roms do not have connection with kernel, just JetMod who do have kernel with TWRP too.
P.S. lol you confuse me. TWRP is kernel related, nothing to do with ROM.
When you want stock kernel back, just flash your firmware from sammobile.com.
So you need to change kernel to get TWRP. And with TWRP you do backup of system.
Sent from Galaxy S Advance
Bos manForu
Hmmmm, now I am a little confused.
Since I don't want to touch the kernel (yet), all I want to do is change the ROM (as in UI changes etc...).
I wanted to backup my current ROM and then load other ROMS.
I started off with ROM Manager because it seemed to answer what I wanted to do, but as you said ROM Manager doesn't support this phone and we went from there to TWRP.
Since I now get that TWRP is kernel related only and not ROM management, what would you advise right now for:
1) Backing up the current ROM
2) Loading other ROMs to the device?
YMatrix said:
Hmmmm, now I am a little confused.
Since I don't want to touch the kernel (yet), all I want to do is change the ROM (as in UI changes etc...).
I wanted to backup my current ROM and then load other ROMS.
I started off with ROM Manager because it seemed to answer what I wanted to do, but as you said ROM Manager doesn't support this phone and we went from there to TWRP.
Since I now get that TWRP is kernel related only and not ROM management, what would you advise right now for:
1) Backing up the current ROM
2) Loading other ROMs to the device?
Click to expand...
Click to collapse
You can do that only with TWRP.
And did you read ROM manager description?
* Flash your recovery to the latest and greatest ClockworkMod recovery.
Click to expand...
Click to collapse
For ROM manager you need custom recovery. And for I9070 that is embended in kernel. Full stop.
And it is connected to CWM, not to TWRP. We do not have CWM for Android 2.3.6. ported.
P.S. So to close this:
- You can't do any backup, installation of ROMs without custom recovery (in our case TWRP) on our phone.
- Custom recovery couldn't be installed separatly - it is embended inside kernel file - and has nothing to do with ROM.
It is clear now?
I think I got you now
1) CWM doesn't work on my phone because the recovery is attached to the kernel.
2) In order for me to backup my ROM I need to install the kernel with TWRP embedded (the one you linked me).
3) I also can't backup my current kernel without TWRP so in order for me to have TWRP I will be doing #2 without any backup? I am guessing this is the part where bricking has a chance of occurrence?
YMatrix said:
I think I got you now
1) CWM doesn't work on my phone because the recovery is attached to the kernel.
2) In order for me to backup my ROM I need to install the kernel with TWRP embedded (the one you linked me).
3) I also can't backup my current kernel without TWRP so in order for me to have TWRP I will be doing #2 without any backup? I am guessing this is the part where bricking has a chance of occurrence?
Click to expand...
Click to collapse
CWM = TWRP
Both are custom recoveryes. Not the same, but same purpose.
1) Our phone have same partition for kernel and recovery. So we can't install it separatly
2) You can backup kernel, but you will need Terminal emulator, and similiar command like instalation of other kernel
Code:
$ su
# dd if=/dev/block/mmcblk0p15 of=/sdcard/boot.bin
# reboot
This will backup your stock kernel on your sdcard. You can install it later this way (ofcourse if boot.bin file is on your sd)
Code:
$ su
# dd if=/sdcard/boot.bin of=/dev/block/mmcblk0p15
# reboot
You always can flash your stock kernel, Download mode do not have anything to do with kernel and recovery partition.
If this is little hard for you, just install custom kernel with TWRP. Or do not do anything. :laugh:
P.S. Trust me, you can't hard brick device with installing kernel. I am tester, and I flashed at least 10 non booting kernels, and 50+ booting ones.
I do trust you, just trying to get an understanding of how the things work on these devices.
So I now understand the backing up and flashing commands (I would like to know how you knew the mmcblk0p15 was the kernel partition for this phone), so where does the "Download mode" come in handy if u can flash directly from a terminal window?
If for some reason the flash wasn't successful, can you enter download mode and restore the backup you created?
YMatrix said:
I do trust you, just trying to get an understanding of how the things work on these devices.
So I now understand the backing up and flashing commands (I would like to know how you knew the mmcblk0p15 was the kernel partition for this phone), so where does the "Download mode" come in handy if u can flash directly from a terminal window?
If for some reason the flash wasn't successful, can you enter download mode and restore the backup you created?
Click to expand...
Click to collapse
Most likely you will have to flash whole firmware if something goes wrong. I told you what I know.
And if you can go in TWRP recovery, it can restore krenel with other things you backed up. And you can flash new kernel in TWRP too.
Somewhere is written what partition is for what. I do not know that. And developers told us what partition is for kernel and recovery.
I do not think that that thing with restoring downlaod mode will work. Newer tried or heard of it.
I tried to explain you, but maybe I was little confusing. :angel: My english is not great, and I didn't provide 1, 2, 3... steps explanation. Like I throw everything to you. :laugh::laugh::laugh:
:laugh: More or less I understand you :laugh:
So to sum up:
1) Create a backup of the current kernel
2) Flash Stock Kernel + TWRP
if all goes well....
3) Create full phone phone backup from TWRP
4) flash custom ROMs (or kernels) with TWRP
Hows that?
YMatrix said:
:laugh: More or less I understand you :laugh:
So to sum up:
1) Create a backup of the current kernel
2) Flash Stock Kernel + TWRP
if all goes well....
3) Create full phone phone backup from TWRP
4) flash custom ROMs (or kernels) with TWRP
Hows that?
Click to expand...
Click to collapse
That is ok.
And you backup old kernel that you can easy go back to stock one. Without flashing whole firmware, when you want stock. Like you want to go to service for warranty or something like that...
how do I flash a new Booting.img though CWM... what I did was I made a backup of my custom rom then swapped the booting.img with new booting.img from withing my backup then flashed it but CWM said MD5 mismatch. Also tried flashing new booting.img in CMW advance options with no luck... how do I flash this guys?
Swapping files inside backup won't work at all. You need to create a custom update.zip with the boot.img you want to flash.
For what for you want to flash boot.img anyways? OC Kernel, stock rom, or something else?
oh right I see, so how do I create an update.zip for a custom kernal?
I think you can use the this update.zip which is originally a OC Kernel, and simply delete the one there, and insert your boot.img. I do not guarantee that this will work. Make a backup!
http://www43.zippyshare.com/v/24843785/file.html
Hlo Everyone,
I Am a Newbie To Custom Android Roms on Galaxy S Advance .I am on Stock JB with Cocore Kernel And Twrp . I Want To ask if i make a nandroid backup of stock android and try to install other custom rom ,can i revert back to stock jb via backup in case problem arises ...
I had tried this on a different phone but at that time it said md5 sum mismatch .
So Simply I am asking u can i revert back to stock jb via twrp recovery ...
Waiting for reply From GS Advance users ...
SultanRTS said:
Hlo Everyone,
I Am a Newbie To Custom Android Roms on Galaxy S Advance .I am on Stock JB with Cocore Kernel And Twrp . I Want To ask if i make a nandroid backup of stock android and try to install other custom rom ,can i revert back to stock jb via backup in case problem arises ...
I had tried this on a different phone but at that time it said md5 sum mismatch .
So Simply I am asking u can i revert back to stock jb via twrp recovery ...
Waiting for reply From GS Advance users ...
Click to expand...
Click to collapse
That mismatch happen because of bad backup I think. You can if you are on other stock based or on CM10.1. For CM10.2 and CM11 ROMs you must repartiton preload partition to be able to do that. HOW.
SultanRTS said:
Hlo Everyone,
I Am a Newbie To Custom Android Roms on Galaxy S Advance .I am on Stock JB with Cocore Kernel And Twrp . I Want To ask if i make a nandroid backup of stock android and try to install other custom rom ,can i revert back to stock jb via backup in case problem arises ...
I had tried this on a different phone but at that time it said md5 sum mismatch .
So Simply I am asking u can i revert back to stock jb via twrp recovery ...
Waiting for reply From GS Advance users ...
Click to expand...
Click to collapse
It is possible.
that md5 sum mismatch you had on different phone was most probably related to corrupted backup file - not related with current ROM installed as long as backup is not cross recovery (CWM / TWRP).
I have lost one backup same way due to corrupted files.
To be sure that it will work you can try to restore backup just after it was created - if it will work, then it should work later on.
if you will be trying CM11 revert procedure is a bit more tricky (as /preload partition is used differently than in stock):
it might need odin flash of stock, install CoCore, restore backup
EDIT ... or faster way presented by shut_down ;]
th3cr0w said:
It is possible.
that md5 sum mismatch you had on different phone was most probably related to corrupted backup file - not related with current ROM installed as long as backup is not cross recovery (CWM / TWRP).
I have lost one backup same way due to corrupted files.
To be sure that it will work you can try to restore backup just after it was created - if it will work, then it should work later on.
if you will be trying CM11 revert procedure is a bit more tricky (as /preload partition is used differently than in stock):
it might need odin flash of stock, install CoCore, restore backup
EDIT ... or faster way presented by shut_down ;]
Click to expand...
Click to collapse
I had tried this on galaxy fit ,but there also i got same problem and i had to use odin to get stock back ... i don't want to go over the same pls help me.my phone is hanging a lot and i cant stay on stock so pls help me
To be sure it is not corrupted backup file you can perform restore backup just after it was created.
If it is corrupted due to some reason it will not work from the beginning.
If it go smooth you are sure that you got correct backup - just store it some place safe (not on crappy SD that might go corrupt over time or sth ...)
At that point it is safe to assume it will work as system restore point from any custom ROM back to state of when it was made (official JB with cocore and all your apps / contacts / messages / etc already in place) - with exception of CM10.2 and CM11 ROMS (and those that are based on them) as explained already - those ROMs would need one extra step before reverting (but it is still possible, just not as straight forward as on other ROMs)
Hi, I'm going to install the new CM 12.1 rom and I've never installed any custom rom, just the ota's and stable versions of miui.
First of, the recovery. If I'm not wrong the recommended is TWRP, so I go to their website and flash the last version (actually 2.8.7.0).
Now, about partitions. I've been reading in the website that the resize2fs feature will make a 32GB partition instead of the real space (I have the 64GB version). But I'm not sure if I have to use this feature to flash the cm rom. I suppose I have just to perform the factory reset wipe, cache and dalvik and then flash the zip. Will the user partition have the full capacity? (55,3GB i think)
Until now everything seems easy enough and reasonably understandable... The big deal is about the system partitions, I'm kind of lost about this, what's the difference between them, which one should I use for the rom, and the other one is if i want/need dual boot? (two different roms installed at once?). I think I read that they can be unified (merge the partitions and have more space in the system partition, what is this for?). I really don't know what to do but I know I don't need dual boot or tdb (once merged can be restored, right?).
And 1 last thing, about the kernel... Since it's open source I don't know if a custom one will be included in the rom or the stock will be used for cm12.1.
Thanks!
Hi, You are confusing so many things in your query.
1- If you are talking about the Offical CM12.1 nightlies then you need not to worry about partitions as it will work on stock partition layout, that's what written in device wiki page of CM website. You just need to flash it via TWRP/CWM.
2- If you are talking about other CM 12.1, then you might need to repartition system of your Mi3/Mi4, in that case you will loss the ability of dual boot, which I think is useless.
3- About repartition, As you know that Mi3/Mi4 has two system partitions of 650MB~ each but due to ROMs new partition table, it's quite difficult to merge install those ROM, so repartitioning is simply merging both systems to get more space to install such ROMS. You just need to flash a zip file via CWM recovery to repartition your device system partition & an other zip to get back to stock partition layout.
4- If I am not wrong you can use custom kernels on CM12.1.
I hope this help you to understand things you are asking, you can type back, if you need more help.
Good day.
Thanks for the answer!
Yes, I was talking about the official CM12.1 for my MI 3W. I won't bother with partitions, I'll just flash the zip.
And about the kernels, I saw there are many. But I'll focus on stock and the CM kernel, as they're probably the best and most stable. The CM kernel for cancro is the one in the github repo? How can I install it? I suppose I have to compile it, zip it and flash it. This is the stock kernel, right?
You know if there's some improvement or difference between stock and CM kernel?
So i have an already rooted phone with TWRP. You have to format the data partition to remove the encryption. Will flashing stock over that with odin enrypt it again? If yes how can i create a flashable zip from samsung stock roms? I could not find anything about new phones like my one.
I'm 90% sure that flashing with odin will not overwrite the data partition. The HOME CSC file has a userdata img file but if you are just wanting the new OS updates, modem, bootloader etc you don't need to flash that I believe.
I am more than 90% sure that after flashing stock Firmware with ODIN, your data Partition will be encrypted onesmore.
Anyone can help me out with something that i can create my own flashable zip from a stock rom so i don't have to always wipe my phone... There are only old guides that i could find