Related
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...
Hello All,
I am on stock v4.1.2, flashed myself.
Now I want to move on to custom ROM.
My current stock ROM is rooted, and I have also unlocked my bootloader.
Now when I want to install custom ROM, I need to flash CWM, and when I do (tried v6.2.8 and v6.0.3.1), and install any ROM, my WiFi becomes unresponsive (failed to turn on). When I flash V20A back, everything turns normal.
I also gone through http://forum.xda-developers.com/showthread.php?t=2180138&page=43, and install the unsecure boot image after installing CWM 6028, but this make my custom rom hang on startup (on bootload screen).
Kindly help me out.
I have search a lot in the P880 forum, and didn't find any help regarding to this problem.
[email protected] said:
Hello All,
I am on stock v4.1.2, flashed myself.
Now I want to move on to custom ROM.
My current stock ROM is rooted, and I have also unlocked my bootloader.
Now when I want to install custom ROM, I need to flash CWM, and when I do (tried v6.2.8 and v6.0.3.1), and install any ROM, my WiFi becomes unresponsive (failed to turn on). When I flash V20A back, everything turns normal.
I also gone through http://forum.xda-developers.com/showthread.php?t=2180138&page=43, and install the unsecure boot image after installing CWM 6028, but this make my custom rom hang on startup (on bootload screen).
Kindly help me out.
I have search a lot in the P880 forum, and didn't find any help regarding to this problem.
Click to expand...
Click to collapse
i dont understand what the recovery has to do with the wifi. recovery is just an interface to easy install something, copy paste , edit , change permissions , etc , things we do using adb commands. it is just an environment. its something else u are doing wrong there.
<EDIT> yea i saw the thread on your link. others seem to have same problem but with the unsecure boot. why do u need unsecure boot if the bootloader is unlocked ? just install teamwin recovery or cwm recovery and the rom u want.
kessaras said:
i dont understand what the recovery has to do with the wifi. recovery is just an interface to easy install something, copy paste , edit , change permissions , etc , things we do using adb commands. it is just an environment. its something else u are doing wrong there.
<EDIT> yea i saw the thread on your link. others seem to have same problem but with the unsecure boot. why do u need unsecure boot if the bootloader is unlocked ? just install teamwin recovery or cwm recovery and the rom u want.
Click to expand...
Click to collapse
Well, I did. And it all went fine, and I am able to install various custom ROMs, and after I install custom ROM, my WiFi becomes unresponsive. I am completely at lost. I also tried MIUI v5 which is non-CM10.2 based, and it also showed the same issue.
Here are my steps to install a custom ROM.
- Currently I am on my V20A stock ROM.
- Root the stock ROM using the All-In-One-Toolkit v1.4.1
- Flush the CWM 6031 using ADB as
Code:
su
cat /mnt/sdcard/recovery.img > /dev/block/mmcblk0p1
sync
- After reboot, my device has the CWM.
- Copy custom ROM zip files to my device, and reboot to recovery
- Wipe out by data and cache
- Install ROM
thats it
And when I boot into the new custom ROM, my WiFi do not work.
Please help.
[email protected] said:
Well, I did. And it all went fine, and I am able to install various custom ROMs, and after I install custom ROM, my WiFi becomes unresponsive. I am completely at lost. I also tried MIUI v5 which is non-CM10.2 based, and it also showed the same issue.
Here are my steps to install a custom ROM.
- Currently I am on my V20A stock ROM.
- Root the stock ROM using the All-In-One-Toolkit v1.4.1
- Flush the CWM 6031 using ADB as
Code:
su
cat /mnt/sdcard/recovery.img > /dev/block/mmcblk0p1
sync
- After reboot, my device has the CWM.
- Copy custom ROM zip files to my device, and reboot to recovery
- Wipe out by data and cache
- Install ROM
thats it
And when I boot into the new custom ROM, my WiFi do not work.
Please help.
Click to expand...
Click to collapse
not exactly.
And here are my steps to install a custom ROM (if currently I am on my V20A stock ROM)
1. Root the stock ROM using the All-In-One-Toolkit v1.4.1
2. Unlock bootloader using All-In-One-Toolkit v1.4.1 or manually like this.
3. Flash the CWM 6.0.4.5 or 6.0.4.4 or TeamWin Recovery
4. Reboot the device in recovery.
5. Enter ADB sideload and install custom rom or using ADB bootloader or using ADB copy the rom in sd card and use install in recovery.
6. Wipe data and cache and reboot system.
<<STEPS DESCRIBED IN HELP SECTION - FREQUENTLY ASKED QUESTIONS>> ( by the way those must be updated too )
kessaras said:
not exactly.
And here are my steps to install a custom ROM (if currently I am on my V20A stock ROM)
1. Root the stock ROM using the All-In-One-Toolkit v1.4.1
2. Unlock bootloader using All-In-One-Toolkit v1.4.1 or manually like this.
3. Flash the CWM 6.0.4.5 or 6.0.4.4 or TeamWin Recovery
4. Reboot the device in recovery.
5. Enter ADB sideload and install custom rom or using ADB bootloader or using ADB copy the rom in sd card and use install in recovery.
6. Wipe data and cache and reboot system.
<<STEPS DESCRIBED IN HELP SECTION - FREQUENTLY ASKED QUESTIONS>> ( by the way those must be updated too )
Click to expand...
Click to collapse
I did wipe the data and cache after installing the custom ROM. But the result is the same; No WiFi response.
However, I always copy my custom ROMs by mounting my phone through USB to my Win8 laptop, and then copy the ROM file through windows explorer. And then install the ROM from the CWN recovery. Thus do not use ADB for copying files, or installing custom ROM as mentioned above. If this is the main issue reason, then advice.
Also I haven't tried TWRP till yet. Will do now. Till then, what else I can do.
Thanks for the quick replies.
i dont know what else you may doing wrong then. one was the insecure boot which is useless since u have unlocked the bootloader and the other that u had flash older version of cwm recovery. maybe compatibility issue with that version of cwm rec ? test and see.
format system also, when installing a new rom, not just data, cache & dalvik
kessaras said:
i dont know what else you may doing wrong then. one was the insecure boot which is useless since u have unlocked the bootloader and the other that u had flash older version of cwm recovery. maybe compatibility issue with that version of cwm rec ? test and see.
Click to expand...
Click to collapse
One piece of detail I missed to mentioned in my case previously was that, I unlocked my phone using the method mentioned in the thread http://forum.xda-developers.com/showthread.php?t=2263627 as I was unable to unlock using the official method.
After I unlock my bootloader, I have flashed V20A KDZ several times, and each time the SW Upd mode show me that my bootloader status is unlocked. Thus after first attempt of unlocking, I never came across need to unlocked my bootloader again as each time when I do the KDZ flash, I get the bootloader status as unlocked. And after each flash of KDZ, I was able to install CWM and custom ROMs, and boot into them successfully.
Is this something causing the issue?
[email protected] said:
One piece of detail I missed to mentioned in my case previously was that, I unlocked my phone using the method mentioned in the thread http://forum.xda-developers.com/showthread.php?t=2263627 as I was unable to unlock using the official method.
After I unlock my bootloader, I have flashed V20A KDZ several times, and each time the SW Upd mode show me that my bootloader status is unlocked. Thus after first attempt of unlocking, I never came across need to unlocked my bootloader again as each time when I do the KDZ flash, I get the bootloader status as unlocked. And after each flash of KDZ, I was able to install CWM and custom ROMs, and boot into them successfully.
Is this something causing the issue?
Click to expand...
Click to collapse
Now, I have repeated using CWM 6.0.4.5 and TWRP, and no breakthrough .... Starting to lose hope ... Help !!!
sorry , personally i dont know what else u may doing wrong there . and no it doesnt matter which way u unlock the phone, but since u unlock it , it stays that way until u lock it.
at least stock rom is working fine ? if that works fine there, then just install only custom kernel, do your tweaks, install another launcher and then delete the default, etc. u can do any modification u like to the stock one to make it look and work the way u want it.
kessaras said:
sorry , personally i dont know what else u may doing wrong there . and no it doesnt matter which way u unlock the phone, but since u unlock it , it stays that way until u lock it.
at least stock rom is working fine ? if that works fine there, then just install only custom kernel, do your tweaks, install another launcher and then delete the default, etc. u can do any modification u like to the stock one to make it look and work the way u want it.
Click to expand...
Click to collapse
Does it help if I installed a custom kernel on my custom ROM (with WiFi issue). My understanding is that the WiFi driver is compiled inside the kernel. So changing the kernel might reduce the issue. What do you think? If yes, then kindly advice me on which kernel should I install on my till now custom ROM MIUI v5 http://en.miui.com/download-79.html.
[email protected] said:
Does it help if I installed a custom kernel on my custom ROM (with WiFi issue). My understanding is that the WiFi driver is compiled inside the kernel. So changing the kernel might reduce the issue. What do you think? If yes, then kindly advice me on which kernel should I install on my till now custom ROM MIUI v5 http://en.miui.com/download-79.html.
Click to expand...
Click to collapse
a developer would never release a rom in public with wifi issues by default and since i have already tested all roms available before i end up to one, i can say that they all worked , but only had small bugs on homescreen. really i dont know what you are doing wrong and not even a teamviewer connection wouldnt help in this case. but on stock your phone works fine ? only in a custom rom u have this issue ?
<<EDIT>> did you also do a full format before going to another rom ? there is a choice in teamwin recovery ( dont know if its in cwm also ) to format data. careful i dont mean to wipe everything you see because you will remove the recovery too and u will have to flash it back. the format option deletes everything besides the recovery. if you dont format before you go to a totally different rom, then you maybe have issues. especially when going from stock to custom, differences are huge. you must format before flashing. and dont forget the gapps, if they are not inluded in rom. ( in your case miui there must have them inside, because i see its 256 mb+)
kessaras said:
a developer would never release a rom in public with wifi issues by default and since i have already tested all roms available before i end up to one, i can say that they all worked , but only had small bugs on homescreen. really i dont know what you are doing wrong and not even a teamviewer connection wouldnt help in this case. but on stock your phone works fine ? only in a custom rom u have this issue ?
<<EDIT>> did you also do a full format before going to another rom ? there is a choice in teamwin recovery ( dont know if its in cwm also ) to format data. careful i dont mean to wipe everything you see because you will remove the recovery too and u will have to flash it back. the format option deletes everything besides the recovery. if you dont format before you go to a totally different rom, then you maybe have issues. especially when going from stock to custom, differences are huge. you must format before flashing. and dont forget the gapps, if they are not inluded in rom. ( in your case miui there must have them inside, because i see its 256 mb+)
Click to expand...
Click to collapse
YES. When I flashed stock V20A, I never had issues with Wifi. Its when I install custom ROM, and any custom ROM.
So I suppose, either there is something wrong in my installing method, or in my stock ROM that won't allow WiFi to work on any custom ROM. But how much influential will be the stock ROM if it is being replaced by a custom ROM?
Well, I haven't formated before I install any custom ROM, as it was not instructed in the forums. But I will do that now, and let you know the results shortly.
Thanks again for the replies.
[email protected] said:
Well, I haven't formated before I install any custom ROM, as it was not instructed in the forums.
Click to expand...
Click to collapse
yea some informations are always missing from the instructions generally , but this is a developer forum , so it doesnt always include informations that are 100% well known to be done. So format and install again and tell me if its everything ok.
kessaras said:
yea some informations are always missing from the instructions generally , but this is a developer forum , so it doesnt always include informations that are 100% well known to be done. So format and install again and tell me if its everything ok.
Click to expand...
Click to collapse
Can you direct me how to install a custom ROM using ADB? Since when I format my /data, all of my custom roms that I copied will get deleted. So the only remaining option is to copy them using ADB.
[email protected] said:
Can you direct me how to install a custom ROM using ADB? Since when I format my /data, all of my custom roms that I copied will get deleted. So the only remaining option is to copy them using ADB.
Click to expand...
Click to collapse
What?????
Why would wiping your /data folder on internal storage delete your custom ROMs? Surely you keep them on your external SD-Card?
[email protected] said:
Can you direct me how to install a custom ROM using ADB? Since when I format my /data, all of my custom roms that I copied will get deleted. So the only remaining option is to copy them using ADB.
Click to expand...
Click to collapse
you dont need to copy it . u can open adb sideload from recovery and on pc use command : adb sideload [path/filename of rom.zip]
SimonTS said:
What?????
Why would wiping your /data folder on internal storage delete your custom ROMs? Surely you keep them on your external SD-Card?
Click to expand...
Click to collapse
So you are saying that, I copy them to external_sd, and then do the data format. Ok ... Will do and let you know.
BTW, I also found V20B. I will start with this stock rom instead of V20A. This might improves some thing.
[email protected] said:
So you are saying that, I copy them to external_sd, and then do the data format. Ok ... Will do and let you know.
BTW, I also found V20B. I will start with this stock rom instead of V20A. This might improves some thing.
Click to expand...
Click to collapse
AT LAST .... FIXED ...
I did two things, V20B, and format /system, /data before installing new ROM. So my steps were:
1) Flush V20B instead of V20A
2) After rooting, and installed CWM 6044 touch, copy custom ROM MIUI to external SDCARD
3) Reboot into recovery, and format /system, /data, and /cache partitions
4) Install custom ROM from external SDCARD
5) Wipe data and cache
6) Reboot into the new world
:good: formatting did the work sorry i didnt think of it earlier.
Well guys this is my first time on the forums. My phone is rendered near useless right now. A few days ago, i rooted my phone via towelroot. as a friend reccomended, i installed ROM manager and flashed clockworkmod recovery. I backed up my stock, perfect ROM with CWM and decided to try installing cyanogenmod 10.3.1......... it wouldn't install. I even tried other apps like ROM installer. Then i came across the handy dandy Cyanogenmod Installer. This seemed great, i didn't have to do anything except click a few buttons on my PC. as i was ready to enjoy a new custom ROM, the following message popped up, "Root access possibly lost. Fix?". I was given the options of "No" and "Yes - Fix root (/system/xbin/su)". i chose the second one, and waited for my device to boot. when it did, it was stock Touchwiz Android version 4.4.2, just like i had initially. what's more is my imei and bandwidth version were both "unknown" and i my sim card was undetected. I decided that technology had gotten the better of my and i tried to flash my old stock ROM back on. i found the file in recovery mode but it kept saying "no files found" whenever i clicked on it. I tried the cyanogenmod installer again, this time choosing "No", resulting in exactly the same scenario. At this point, I would be fine having the stock ROM since i have had such bad luck with the "developer's world" of Android.......... PLEASE HELP!!!!!
Another note:
ROM manager now is telling me that CWM is not installed, yet it is present in recovery mode......
EddyTeddy01 said:
Another note:
ROM manager now is telling me that CWM is not installed, yet it is present in recovery mode......
Click to expand...
Click to collapse
Have you tried installing some other recovery, like TWRP? You won't be able to install CM from it, but you should be able to install other roms.
touchbattle.mika said:
Have you tried installing some other recovery, like TWRP? You won't be able to install CM from it, but you should be able to install other roms.
Click to expand...
Click to collapse
How do I replace CWM with twrp? If I flash twrp, wouldnt CWM stay on my phone as default recovery?
EddyTeddy01 said:
How do I replace CWM with twrp? If I flash twrp, wouldnt CWM stay on my phone as default recovery?
Click to expand...
Click to collapse
follow the guide and replace your recovery easily. after flashing, what recovery you have flashed will be default recovery, i recommend philz, they are all downloadable in the guide
MaHo_66 said:
follow the guide and replace your recovery easily. after flashing, what recovery you have flashed will be default recovery, i recommend philz, they are all downloadable in the guide
Click to expand...
Click to collapse
Would I have to uninstall CWM? I'm just wondering if the file for CWM will still be on my phone. I'll check out the link.
EddyTeddy01 said:
Would I have to uninstall CWM? I'm just wondering if the file for CWM will still be on my phone. I'll check out the link.
Click to expand...
Click to collapse
it´s the best if you also do a format of internal sd in recovery before changing the recovery, because sometimes there are some folders left of it in interrnal memory and you cant delete it, do that if this will be the case. but i think Philz and CWM use same folder, so if you flash philz it will be okay if im correct otherwise you can always format internal sd afterwards
Edit: dont use rom manager for recovery actions, use recovery itself, much more reliable
MaHo_66 said:
follow the guide and replace your recovery easily. after flashing, what recovery you have flashed will be default recovery, i recommend philz, they are all downloadable in the guide
Click to expand...
Click to collapse
That guide made it possible for me to install all custom roms. Witz the recovery installed first it did not work. Thx
I am planning to flash a custom rom on my phone (for the first time).
Model : Xperia SP(C5302)
Build : 12.1.A.1.205 (Stock) running JB 4.3 with LB
I have rooted my phone using the towelroot method and installed supersu. I have also installed custom recovery from here http://forum.xda-developers.com/showthread.php?t=2649923
I am planning to flash this custom rom http://forum.xda-developers.com/xperia-sp/development/cyanogenmod-11-locked-bootloader-users-t2868398
So I have a few questions that I am not clear about(even after searching the forums). And sorry if they are dumb. I really want to understand as much as possible before flashing roms.:fingers-crossed:
1. After reading the thread of my recovery, from what I understand, the recoveries are installed in /system. But on OP of the custom rom, I am about to install, there is an instruction to format /system before flashing the rom. So my question is if I format the /system partition, won’t my recoveries be removed (by the recoveries itself) before I even flash the rom?
2. Also will the recovery still be available to me if say I enter bootloop for some reason during flashing the rom?(asking for the same reason as above that is wiping my /system should also remove my recoveries)
3. Does CM 11 come with any inbuilt custom recovery? If not can I install the one I am already using (assuming installing a custom rom will remove my installed recoveries)?
4. Say I screw up during the flashing procedure. So if I want to rectify this I should first flash the stock .205 ftf, root, install a recovery again and then restore using the nandroid backup. Am I correct?
5. Is it necessary to wipe cache and dalvik cache before flashing rom? I see this instruction in some roms but not in others. And dalvik should be wiped after flashing rom and gapps, right?
6. Should I install supersu again after I flash the rom. I read in an article that it causes problems with CM. As far as I know CM11 comes pre-installed with superuser. But it also supposedly causes some problems.
7. Is it safe to restore user app+data, messages and contacts backed up using Titanium backup on a newly flashed rom? I have seen conflicted views on this.
Click to expand...
Click to collapse
And that’s it for my questions (for now at least... ).
A Big Thanks in advance for all your helpful answers
Prat92 said:
I am planning to flash a custom rom on my phone (for the first time).
Model : Xperia SP(C5302)
Build : 12.1.A.1.205 (Stock) running JB 4.3 with LB
I have rooted my phone using the towelroot method and installed supersu. I have also installed custom recovery from here http://forum.xda-developers.com/showthread.php?t=2649923
I am planning to flash this custom rom http://forum.xda-developers.com/xperia-sp/development/cyanogenmod-11-locked-bootloader-users-t2868398
So I have a few questions that I am not clear about(even after searching the forums). And sorry if they are dumb. I really want to understand as much as possible before flashing roms.:fingers-crossed:
And that’s it for my questions (for now at least... ).
A Big Thanks in advance for all your helpful answers
Click to expand...
Click to collapse
First of all, I am only explaining the one I know about
1. Well, wiping the system will remove the recovery. That's why you'll have to flash the ROM after wiping the system. Do not ever reboot the phone after wiping the system but haven't yet flashed the ROM zip, else you'll have to do more work to flash the Stock ROM. This is due to the fact your phone does not have an OS to boot into! When flashing the ROM zip, the recovery will be automatically installed.
2. This is based on luck, most of time you'll end up unable to boot into anything. A fix is to flash the Stock ROM again.
3. Every ROM has recovery built with it (unless stated otherwise in the thread)! Upon flashing, it will be automatically installed too.
4. The methods you mentioned is correct. However, only restore the nandroid backup if you want to stay on stock. You could always retry to flash the ROM again. Nandroid backup is an image backup of your android. If you restore your nandroid backup, you'll end up with your previous version of android (like the way before you started flashing the ROM)
5. Wiping /cache and dalvik-cache is a really good practise! It doesn't really matter when you will need to wipe them, but personally I wipe them all before flashing the ROM. Wiping /data and performing a factory reset through recovery is recommended if you're coming from a different ROM. That's why backing up user apps through TiB (Titanium Backup) is recommended for you to easily get your installed apps back. Remember, nandroid backup and apps backup from TiB is different to each other.
6. No, this might cause extreme conflicts. No, I am using SuperUser as long as I have used CM. It never fails to give root permission at all despite the hatred I sense in some apps that overly-recommends SuperSU.
7. Of course it is very safe to restore them backups with TiB. However, based on my experience, messages and contacts were unable to be restored due to the difference in ROM version. I don't know if anyone else faces the same problem as mine. As of this, I really recommend your contacts to be synced with Google.
Heads up!
Based on this post, the dev of the ROM you wanted to flash, MrSteve555, recommends PhilZ when flashing the ROM.
TechnoSparks said:
First of all, I am only explaining the one I know about
1. Well, wiping the system will remove the recovery. That's why you'll have to flash the ROM after wiping the system. Do not ever reboot the phone after wiping the system but haven't yet flashed the ROM zip, else you'll have to do more work to flash the Stock ROM. This is due to the fact your phone does not have an OS to boot into! When flashing the ROM zip, the recovery will be automatically installed.
2. This is based on luck, most of time you'll end up unable to boot into anything. A fix is to flash the Stock ROM again.
3. Every ROM has recovery built with it (unless stated otherwise in the thread)! Upon flashing, it will be automatically installed too.
4. The methods you mentioned is correct. However, only restore the nandroid backup if you want to stay on stock. You could always retry to flash the ROM again. Nandroid backup is an image backup of your android. If you restore your nandroid backup, you'll end up with your previous version of android (like the way before you started flashing the ROM)
5. Wiping /cache and dalvik-cache is a really good practise! It doesn't really matter when you will need to wipe them, but personally I wipe them all before flashing the ROM. Wiping /data and performing a factory reset through recovery is recommended if you're coming from a different ROM. That's why backing up user apps through TiB (Titanium Backup) is recommended for you to easily get your installed apps back. Remember, nandroid backup and apps backup from TiB is different to each other.
6. No, this might cause extreme conflicts. No, I am using SuperUser as long as I have used CM. It never fails to give root permission at all despite the hatred I sense in some apps that overly-recommends SuperSU.
7. Of course it is very safe to restore them backups with TiB. However, based on my experience, messages and contacts were unable to be restored due to the difference in ROM version. I don't know if anyone else faces the same problem as mine. As of this, I really recommend your contacts to be synced with Google.
Heads up!
Based on this post, the dev of the ROM you wanted to flash, MrSteve555, recommends PhilZ when flashing the ROM.
Click to expand...
Click to collapse
Thanks for such detailed answers. That cleared most of my doubts
Just some last few questions(promise!)
1. If wiping /system does remove the recovery before I install the rom, how is it possible to access it even to flash the rom? Shouldn't it like just close right when I wipe /system. Or does it not work like that?
2. Just to be sure the nandroid backup I made on my stock rom won't work if I later try to flash it through recovery while using CM,right?
Prat92 said:
Thanks for such detailed answers. That cleared most of my doubts
Just some last few questions(promise!)
1. If wiping /system does remove the recovery before I install the rom, how is it possible to access it even to flash the rom? Shouldn't it like just close right when I wipe /system. Or does it not work like that?
2. Just to be sure the nandroid backup I made on my stock rom won't work if I later try to flash it through recovery while using CM,right?
Click to expand...
Click to collapse
1. Wiping system wont close the recovery at all. It still runs and you can still navigate within it. But remember do not reboot unless you've flashed the ROM! The mechanism of how the magic works is yet to be acknowledged. So I can't tell why it doesn't closes upon wipe. My best guess here is that the recovery might be running on a temporary partition perhaps. I hope a developer see this post and explains the magic.
2. Nandroid backup works all the time (if they are no errors when you are creating them). Nandroid backup is simply a backup of your whole device. If you're on CM, restoring nandroid backup will get your phone back to the way when you attempted the nandroid backup (stock ROM, rooted, and triple recoveries installed). Nandroid backup is useful when you're about to try something that may damage your ROM, without doing so much work to restore your device.
Say, you created a nandroid backup in cwm in which Cyanogenmod was installed. And then you flashed something afterwards. If that "something" damages the ROM and gives you bootloop, you can simply flash Stock ROM, root it again, install recoveries again, and restore the nandroid backup. Then, voilà, cyanogenmod is back. This will simplify your work rather than flash CM again, then gapps, then restore your apps and all those other things that will consume so much time
So a new nandroid backup will backup the whole device, in a form of an image.
My HTC One is currently unlocked at hboot 1.61, S-On, with ClockworkMod Recovery v6.0.4.6 installed. no carriers
I have a backup of the stock rom before I install any roms, and I have install SU to my device afterwards.
I was intended to install Insertcoin 7.1.3 rom, I did a factory reset/wipe caches and then install the rom via clockworkmod.
However, my device does not boot into the custom but reboot will automatically 'entering in recovery' instead,
perhaps that was to do with the S-On, or it's a failed rom I got?
Anyway, I tried to restore the stock rom backup I did, it said restore completed but it reboot into recovery still...
Now I can only able to access fastboot and recovery, I tried download and put in the by using "mounts and storage" -> "mount USB storage" on ClockworkMod, but it won't let me as it does not appear on my Windows 10 as it usually should.
Can anyone help me to solve this mystery? Ideally, I would like to get back to stock rom at least...
I only had experience on rooting from my Desire HD(retired), there's a sdcard to storage roms back then...
What I've got now is:
- a backup from clockworkmod, and I didn't copy to my PC
- a stock rom and kernel, I downloaded from internet and HTC webpage.
- a InsertCoin rom for m7
I have did some research on similar issue previously, but doesn't seems to help me out. if anyone knows the same issue has been addressed and solved in some posts, please don't hesitate to feed me with those posts, as I could have missed them by struggling on reading foreign language for the entire evening...
lastly, if i did anything idiotic through that process, please don't judge my stupidity
wailon93 said:
My HTC One is currently unlocked at hboot 1.61, S-On, with ClockworkMod Recovery v6.0.4.6 installed. no carriers
I have a backup of the stock rom before I install any roms, and I have install SU to my device afterwards.
I was intended to install Insertcoin 7.1.3 rom, I did a factory reset/wipe caches and then install the rom via clockworkmod.
However, my device does not boot into the custom but reboot will automatically 'entering in recovery' instead,
perhaps that was to do with the S-On, or it's a failed rom I got?
Anyway, I tried to restore the stock rom backup I did, it said restore completed but it reboot into recovery still...
Now I can only able to access fastboot and recovery, I tried download and put in the by using "mounts and storage" -> "mount USB storage" on ClockworkMod, but it won't let me as it does not appear on my Windows 10 as it usually should.
Can anyone help me to solve this mystery? Ideally, I would like to get back to stock rom at least...
I only had experience on rooting from my Desire HD(retired), there's a sdcard to storage roms back then...
What I've got now is:
- a backup from clockworkmod, and I didn't copy to my PC
- a stock rom and kernel, I downloaded from internet and HTC webpage.
- a InsertCoin rom for m7
I have did some research on similar issue previously, but doesn't seems to help me out. if anyone knows the same issue has been addressed and solved in some posts, please don't hesitate to feed me with those posts, as I could have missed them by struggling on reading foreign language for the entire evening...
lastly, if i did anything idiotic through that process, please don't judge my stupidity
Click to expand...
Click to collapse
Change your recovery to TWRP and flash away. If you read Insercoin thread, you would see that TWRP is recomended recovery. And that means you will loose your backup
donkeykong1 said:
Change your recovery to TWRP and flash away. If you read Insercoin thread, you would see that TWRP is recomended recovery. And that means you will loose your backup
Click to expand...
Click to collapse
Thanks for the reply, the backup is what holds me back from doing anything risky unless someone suggest me to do so, but I did risk of losing the backup and flashed TWRP. I have now successfully install InsertCoin rom, the sacrifice of the backup is well worthy. Well, at least my device can work properly, not much to lose. Doesn't seems like a big issue after all.
I also found out the problem was cause by the clockworkmod recovery. If I flashed TWRP in the first place, I could have kept a backup for my stock rom.
Anyway, a BIG thanks for your help! :good:
wailon93 said:
Thanks for the reply, the backup is what holds me back from doing anything risky unless someone suggest me to do so, but I did risk of losing the backup and flashed TWRP. I have now successfully install InsertCoin rom, the sacrifice of the backup is well worthy. Well, at least my device can work properly, not much to lose. Doesn't seems like a big issue after all.
I also found out the problem was cause by the clockworkmod recovery. If I flashed TWRP in the first place, I could have kept a backup for my stock rom.
Anyway, a BIG thanks for your help! :good:
Click to expand...
Click to collapse
You're dead right regarding recoveries! Now, all you need to do is make a backup of your ROM in TWRP for future mishaps and enjoy[emoji6]
And you're very welcome. I'm glad I could be of help