Related
I have been researching the forums for a few weeks now but I have not stumbled across enough threads that would assist me to fully understanding the proper process for restoring via CWM back to a stock ROM (without going back to ODIN to flash it).
Of course this all relates to my Samsung Gio GT-S5660M from Bell in Canada (Pay as you Go). I really only purchased the phone to play with it to learn more. My wife has had the same phone for over a year. Her phone was rooted in order to be none carrier specific so she could use it to replace a phone under contract that was stolen. Other than that, it is stock.
I tried not to post and continue reading but now I am at the point where I need to ask a some specific questions.
First, some background as to what I am trying to do and what I have done so far.
The goal, as I am sure is the case with others, is to test custom ROMs but also be able to restore back to a factory default Samsung based ROM CWM backup at any point in the most convenient fashion.
I would like to perform this process with known working tools on this forum.
To start, I am familiar with the installation of the CWM from phiexz's work http://forum.xda-developers.com/showthread.php?t=1421650. I have installed 5.0.2.7 via Flash from Recovery signed_cwm-5.0.2.7-flashablezip-ext4+rfs. After the installation of CWM I performed a backup of the stock rom.
Once that was complete, I began playing with some custom ROMs installing them via CWM off the SD card from zip files.
I learned after installing the custom ROMs that my phone was reformatted to EXT4 file system. This obviously makes it difficult to simply restore back to the stock ROMs original RFS file system easily. I received the obvious errors message (E:format_volume: format_rfs_device failed on /dev/block/stl12 Error while formatting /system!) when trying to restore the original ROM files via nandroid restore within CWM.
I have reviewed the nandroid backups stored on the SD card in the \clockworkmod\backup\appropriate dated file and I can see that the file names include RFS before the .tar extension for the system, data and cache files. From everything I have read this is normal since stock Samsung ROMs (at least FROYO and Gingerbread based ones) are based on the RFS file system as opposed to most custom ROMs which are based on EXT4. I made backups of some of the ROMs I was playing with from within CWM nandroid backup. I did notice those files had ext4 before the .tar extension in the file names. So I believe I am clear in understanding that portion.
I read that the only way to really get back to the RFS file version is to use ODIN to flash back the stock firmware all in one package retrieved from www.sammobile.com for the GT-S5660M for Bell in Canada. That again worked perfectly fine. I again went back into restore mode and re-installed signed_cwm-5.0.2.7-flashablezip-ext4+rfs. Once CWM was installed I tried to restore the original stock ROM backup I had saved originally and it gave me the same error (E:format_volume: format_rfs_device failed on /dev/block/stl12 Error while formatting /system!) even though I know the phone is now back at RFS file system again. Even when I try to perform a backup from CWM of the ODIN installed stock rom it complains stating (Backing up system.... Can't mount /system!.
I of course can reinstall Custom ROMs and restore them just fine after one initial installation and the file system being formatted back to EXT4.
So here are the questions.
1. What is the proper way to restore a stock ROM backup?
2. Is it possible to convert the RFS backup or existing system to EXT4 and have it still operate?
From what I can tell there is custom kernels that support EXT4 that can be injected via ODIN or CWM. Such as CF-ROOT however it is completely confusing to me on how to do that. I tried the ODIN method and that complained. I am not sure what version of CF-ROOT to use. Really I would like to stay with the EXT4 file system and convert the Stock backup to run with a custom ROM if need be. The goal is really just to be able to do it all within CWM and not require a computer other than for transferring files to the SD card as required.
I do not mind using ODIN but I would like to be able to restore with all the settings and changes I made in the stock OS to carry forward so I do not have to do that again.
3. Is there an easier or more reliable method to carry these steps out? Overall I would choose a method that consistently works over convenience.
Any assistance that could be provided would be appreciated.
Thank you in advance for your time in reading and/or hopefully replying to this thread.
Backup with cwm 5.0.2.6 and then when you have ext4 flash stock via odin. Root with stock cwm and then flash cwm 5.0.2.6 and restore.
Sent from my GT-S5660 using Tapatalk
AvrX said:
Backup with cwm 5.0.2.6 and then when you have ext4 flash stock via odin. Root with stock cwm and then flash cwm 5.0.2.6 and restore.
Sent from my GT-S5660 using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply AvrX.
Is there any particular reason you are suggesting that I use an older version of cwm (5.0.2.6) over 5.0.2.7? Is it due to your experience with stability between the two versions or support of RFS over EXT4?
Also your procedure is a bit vague to me.
Why would backing up another version of the stock ROM again assist me? Converting the stock ROM to EXT4 and then reflashing stock ROM again with Odin does not really make sense. Does the phone have to be rooted again? I thought once rooted you did not have to root it again.
I believe I am even more confused now.
I am confident these are all noob questions that can be answered by someone out there with S5660 experience. Then maybe this thread can be locked for future reference for everyone.
http://forum.xda-developers.com/showthread.php?t=1449320
The thread above is not in the S5660 area but it seems like a step in the right direction. I just can not figure out what version of CF-Root to install via CWM from the following thread http://forum.xda-developers.com/showthread.php?t=788108 for the GT-S5560M. I realize the thread is for a different model phone though.
There is the thread for the GT-S5660 http://forum.xda-developers.com/showthread.php?t=1564629 but I do not see where you download the file for CF-ROOT 3.7. I have signed up for Gio Community forum but my account is not approved yet.
Hence I am still at a loss as to what to do next.
So as you can see I have done research which leads me to believe it is possible but I have no proof it can be done or I just do not fully understand and/or have access/knowledge of the tools to achieve it.
(I have the Canada Model of Galaxy Gio)
1. First use EXT4-only version of CWM
2. You could do a nandroid backup of your EXT4 ROM, the rename then files from .[highlight]EXT4[/highlight].IMG to .[highlight]RFS[/highlight].IMG
3. If you do this, make sure you also edit the [highlight]md5sum[/highlight]
4. Now use RFS+EXT4 version of CWM
5. Replace boot.img in the folder where you saved the backup, with a RFS kernel only! (Stock Kernel) To avoid bricking...
6. Then restore using CWM or nandroid
NOTE:Do with your own risk. I plan to do it myself soon, but be careful...
I've re-read your post a few times and I'm not 100% certain that I get what you're trying to do... Going back to a completely stock, out-of-the-box phone from CWM?
Different builds of CWM are available for the Gio. Some support RFS, others ext4. I'd rather avoid those with dual support as they're not very clear regarding what format they're using for which operation.
Let's clarify the types of ROMs out there, you've got:
-Stock, Samsung releases, RFS, Odin-flashable. Leaked images (such as those from samfirmware et al.) contain the CSC image, "put-together" ones (like my early 5660M stock backup) don't as the files are already integrated.
-Stock-based. Community-made ROMs with varying levels of modification; earlier ones were typically Odin-flashable (with a number of issues due to modem and kernel changes, especially for 5660M and V users), later releases usually CWM-flashable. File system support depends on the kernel used. The Samsung kernel only runs RFS, whereas others such as Phiexz's will run either ext4 or RFS.
-AOSP and derivatives. Community-made, CWM-flashable, ext4 ROMs, such as CM7, 9 and 10, or MIUI.
Recoveries:
-CWM, as previously discussed
-Stock: the Samsung recovery you've overwritten pretty early on if you're a typical XDA poster. It does provide for proper CSC installation when flashing a stock ROM through Odin. Can also do a factory reset and reformat /data and /cache RFS partitions.
In most situations you would want to go back to a stock ROM and kernel, but keep the CWM recovery, that's relatively easy to do with an RFS-compatible CWM and a nandroid backup. Even a non-RFS compatible CWM could be made to work with appropriate images and the (ADB shell) dd command.
But back to the question: going back to a completely stock, out-of-the-box phone from CWM, stock recovery, CSC and all?
I've thought about it for a few minutes, and it might just be possible to do. Neat? Kinda. Worth the trouble? Meh.
It would involve dd-ing RFS-format /system, /data and /cache partitions, boot.img and recovery.img, into place.
The part I'm not sure about is how to go about extracting CSC.rfs in the proper location and issuing a reboot recovery command at the end of the script, which should kick stock recovery into gear and apply CSC.
Maybe one manual reboot to finish the process.
Let us know if that helped,
Darkshado
Thank you for the replies Peteragent5 and Darkshado. Again I really do appreciate your time and your support of those out there interested in learning more about android based devices.
Going back to a completely stock, out-of-the-box phone from CWM?
Click to expand...
Click to collapse
Good question Darkshado....let me try to clarify things again. I apologize as I tend to ramble. I would rather give more information than not enough.
Yes that is the goal. Or at least I would like the ability to do that. I understand it is not entirely accurate though as with the installation of CWM it is not really stock.
Let's clarify the types of ROMs out there, you've got:
-Stock, Samsung releases, RFS, Odin-flashable. Leaked images (such as those from samfirmware et al.) contain the CSC image, "put-together" ones (like my early 5660M stock backup) don't as the files are already integrated.
-Stock-based. Community-made ROMs with varying levels of modification; earlier ones were typically Odin-flashable (with a number of issues due to modem and kernel changes, especially for 5660M and V users), later releases usually CWM-flashable. File system support depends on the kernel used. The Samsung kernel only runs RFS, whereas others such as Phiexz's will run either ext4 or RFS.
-AOSP and derivatives. Community-made, CWM-flashable, ext4 ROMs, such as CM7, 9 and 10, or MIUI.
Click to expand...
Click to collapse
Well of course I started with the Out-of-Box Stock Samsung/Bell Canada ROM on the phone based on Gingerbread 2.3.4. I rooted it of course. Then I installed CWM that supported both RFS and EXT4. I believe 5.2.0.7 by Phiexz as mentioned in my first post. To be honest, since I am a noob and I wanted to get started so quickly, I cannot honestly remember which version of CWM I used originally. It may have even been px-CWM-v2.zip. Regardless of the version it obviously supported Stock Samsung/Bell Canada RFS based file system and I used that to make the Nandroid based backup within CWM of the existing Stock ROM on the phone.
After that point I thought I would be safe to start playing with Community-made ROMs CWM-flashable installs based on the GT-S5660 although of course I had the GT-S5660M Canadian version. So I went forward and tried [ROM] Enhanced236 - stock 2.3.6 (06.08.2012 update) http://forum.xda-developers.com/showthread.php?t=1654317 as I wanted something close to original version of Gingerbread that came Out-of-Box with the phone but was upgraded to fix and issue I had with version 2.3.4 of Gingerbread.
The main drive for doing this was to assist my wife with an issue she has on her Bell GT-S5660M running on the SaskTel telco in SK. There is an issue with her SMS/texting. She always has to turn on/off Settings, Wireless and Network, Mobile Networks, Use Packet Data to get texting to send out. Receiving is fine. It seems to be a known issue when the phone is used with Telus or SaskTel networks in Canada. From what I understand the phone with 2.3.4 of Gingerbread is not affected on the Bell and Rogers network in Canada. It seems to be related to a bug in the phone at the particular Gingerbread version 2.3.4 from what I read. Since Kies did not have an update for the Bell based phone beyond version 2.3.4 I thought it is time to check out custom ROMs. After trying her SIM card with the Enhanced236 - stock 2.3.6 everything worked perfectly on my test phone for texting. So I took a Nandroid backup via CWM of that ROM. Then I tried [DEV] CyanogenMod 9.1 / CyanogenMod 10 by MacławStudios http://forum.xda-developers.com/showthread.php?t=1414173 to see what the Jelly Bean hype was about and again made a CWM backup of the ROM to maintain my settings.
I had a friend over and I was showing him what I had learned so far and I was showing all the capabilities of CWM. Then I told him I could even restore back to original factory ROM as well although I had not tried it yet thinking CWM was full proof. I tried it and it failed in front of him. So then I thought...wow...I do not understand as much as I think. That is when I stumbled on the difference between RFS in Stock Samsung ROMs and EXT4 in the Community-made ROMs. Sorry I know that is quite a bit of background information but it helps to show where I am coming from in terms of wanting to accomplish to here.
So I read a bunch and realized that the only way to go back was to flash back to Stock with ODIN. So that at that point I tried your Stock ROM GT-S5660M_MUGKG3_stock_rooted_ROM and the one from sammobile for the GT-5660M from Bell GT-S5660M_BMC_S5660MUGKG3_S5660MUGKG3_S5660MBMCKG3. I thought then I could simply install CWM again (the version that obviously supports RFS and EXT4 5.2.0.7) and then restore the original Stock Nandroid backup I made of the original Out-of-Box ROM. As mentioned in the previous post I saw the rfs in the file names of the back before the .tar extension.
That is when the failures in restoring via CWM occurred noted in the first post (E:format_volume: format_rfs_device failed on /dev/block/stl12 Error while formatting /system!). I thought this would work for sure. That is when I started to think if I could get this all to work I would convert the stock ROM with a custom kernel to running exclusively on EXT4 so that if I ever wanted to go back to 2.3.4 I could do it easier with out having to use ODIN and going back to stock RFS file system. So I guess really I do not want to go back to Stock but the Stock Files in EXT4 formatted form...which I understand would require a custom kernel. Regardless I am not able to restore the original backup so obviously there is something I am missing. That is where I would like to start. I thought as long as I can not get the original backup to restore....then I do not understand enough to continue on the journey. Hence to post requesting assistance.
Can also do a factory reset and reformat /data and /cache RFS partitions.
Click to expand...
Click to collapse
I am not exactly sure what you mean here. Once I flashed the Stock RFS Samsung/Bell Canada ROM back via ODIN in some cases it would not boot. It was in a boot loop stuck on the Samsung logo. I went into normal recovery mode (Not CWM recovery mode since I did not reinstall it yet at that point) and I would perform the Wipe Data and Wipe Cache functions within recovery to get it out of the boot loop. I always made sure the OS fully loaded and functioned before moving to the next step of what I was trying to do. It was at that point I would install CWM again and then find out the original backup I took would not restore with the same error (E:format_volume: format_rfs_device failed on /dev/block/stl12 Error while formatting /system!).
In most situations you would want to go back to a stock ROM and kernel, but keep the CWM recovery, that's relatively easy to do with an RFS-compatible CWM and a nandroid backup. Even a non-RFS compatible CWM could be made to work with appropriate images and the (ADB shell) dd command.
Click to expand...
Click to collapse
I read a bit about this but I did not completely understand it. Is there a thread you can point me to in regard to this? Ultimately the goal is just to be able to restore to stock (or stock converted to EXT4 with a custom "close to original" kernel like CF-Root) if and when I want to in the easiest fashion.
But back to the question: going back to a completely stock, out-of-the-box phone from CWM, stock recovery, CSC and all?
I've thought about it for a few minutes, and it might just be possible to do. Neat? Kinda. Worth the trouble? Meh.
Click to expand...
Click to collapse
Yes I can understand that it is a bit of an odd request and not one that many would really be that interested in...but I am simply from the point of view of just seeing if it is possible. Once I get something in my head I want to prove or disprove it is possible. But I need knowledgeable people like you to offer suggestions and share past experience. I do not mind performing the work....I just need some help from time to time. I have been employed in the IT field for over 15 years but I am more of Windows guys.... but I am not afraid to play with anything and learn. Please do not bash me on the Windows/Microsoft thing....it pays the bills.
Again the goal is to keep everything within CWM so that you do not really need to go back to a computer. It might take some work and effort to get there though. I am not sure who else would be interested but it then could be shared with the masses on this forum. Again not sure of the value to everyone.
It would involve dd-ing RFS-format /system, /data and /cache partitions, boot.img and recovery.img, into place
Click to expand...
Click to collapse
GREAT!!!...I am game to try it. Again if you have a post of step by step on how to achieve this it would be appreciated. I believe I saw a post of yours when I was performing my research about this but it may not be exact for what we are trying to accomplish here. Perhaps it is though.
The part I'm not sure about is how to go about extracting CSC.rfs in the proper location and issuing a reboot recovery command at the end of the script, which should kick stock recovery into gear and apply CSC.
Click to expand...
Click to collapse
Well based on the posts I have read on your dissection of the partitions on the GT-S5660, you are one of the great resources to assist on this. I noticed that the CSC.rfs in not in your GT-S5660M_MUGKG3_stock_rooted_ROM but it was included in the S5660MUGKG3_S5660MUGKG3_S5660MBMCKG3_home from samsmobile. So I am not sure where that version came from if it was leaked or what. I would guess that my original Out-of-Box CSC.rfs has been overwritten by the S5660MUGKG3_S5660MUGKG3_S5660MBMCKG3_home version if there happen to be any differences. My wife's phone is still available so I could still extract the original file from her phone. Maybe that would not help though....I am not really sure what is contained in the CSC.rfs if it is phone, ROM specific...etc.
Anyway regardless I appreciate the time anyone has put in reading or thinking about my post. Again thank you for your time and effort. This is really a great forum full of great information.
ps. How much do I dislike the ReCaptcha spam blocker when trying to post? Very much!!!....you have to hit refresh about 100 times before you can actually make out some words you can type.....FAIL. I see it on numerous sites....really annoying...I like the pattern based ones that you put together way better.
NOTE:Do with your own risk. I plan to do it myself soon, but be careful...
Click to expand...
Click to collapse
You first. You seem to have more experience. Ha!!!. Kinda joking but also kinda serious. I guess I am still a noob so I would be leery to try this. I always have the fear of the bricking.
LOL I admire you for your long list of explanations. As well as Darkshado's posts.
Let's backtrack shall we?
The reason it gave you "error while formatting /system" is because CWM doesn't support converting the filesystem back to RFS. At least that's what I know. But for ODIN, you can do this fine. The thing about ODIN, is that it includes the base RFS files and doesn't come with other RFS partitions because it assumes your phone is already RFS
Hmmm I don't know any reason to go back to Stock RFS if you have already converted your partitions into a far more superior filesystem --> EXT4. Darkshado has his own custom ROM that has these specifications
A CF-Root kernel is a kernel that includes root. So when you flash the kernel, it also gives you root and possibly busybox.
Busybox is a series of UNIX tools for Linux and derivatives (Android) to use in the Terminal.
Hehe. It's fine if you're getting paid at IT, or doing IT, dunno which one.. But if you wanna learn more about Android and whatever stuff about it, that's great! It's a nice place to start. Then make your way towards linux.
Linux Distros (Distributions):
Ubuntu = Newbies
Debian = Ubuntu based on this
Fedora = Productivity
Linux Mint 12/13 = Ease of Use
Arch Linux =Advanced
BackTrack = Hacking/Cracking
Tails = Security
Bohdi = Speed
SliTaz = Small & For old hardware + Nice UI
(Just giving you tips here, if you do wanna do this )
Be careful if you're dd'ing your data, cache, system, stl, bml, etc..
Because there is a chance of bricking your device. I know dd'ing stl5 has a high chance that you'll brick your device.
The CSC contains all the info about your carrier, and some other stuff... Lol
Yes I hate the 5 minute waiting period to post a reply or thread, and i hate the captcha..
Sent from my BlackBerry PlayBook
Let's backtrack shall we?
Click to expand...
Click to collapse
Fine by me.
The reason it gave you "error while formatting /system" is because CWM doesn't support converting the filesystem back to RFS. At least that's what I know. But for ODIN, you can do this fine. The thing about ODIN, is that it includes the base RFS files and doesn't come with other RFS partitions because it assumes your phone is already RFS
Click to expand...
Click to collapse
Okay I understand that. However when I made my first backup via CWM the system was stock with RFS. When I restored back to stock ROM after playing with custom ROMs with EXT4 filesystem, the system was back to RFS right? Therefore how come the original restore would not work when the filesystem of the stock rom was back to RFS. That is where I am struggling. Is there an easy way to confirm you are on RFS vs EXT4 from within CWM? Or does ODIN have the ability to restore the RFS Stock version back to a EXT4 formatted phone. I assumed it converts the system back to RFS during the flashing. Is that an incorrect assumption?
Hmmm I don't know any reason to go back to Stock RFS if you have already converted your partitions into a far more superior filesystem --> EXT4. Darkshado has his own custom ROM that has these specifications
Click to expand...
Click to collapse
I guess I have not spent the time to really check out every single Custom ROM. So are you saying Darkshado's ROM is Gingerbread based with EXT4? I agree I would like to stay with EXT4 over all as I understand it is superior and that even Samsung has finally moved to it for its Stock ROMs on newer phones. Really I just want the stock image converted to EXT4 and the ability to restore to that EXT4 based version of the stock ROM via CWM.
A CF-Root kernel is a kernel that includes root. So when you flash the kernel, it also gives you root and possibly busybox.
Click to expand...
Click to collapse
I also understand that CF-Root supports EXT4 and is supposed to be the closest to the original Samsung based kernel.
Hehe. It's fine if you're getting paid at IT, or doing IT, dunno which one.. But if you wanna learn more about Android and whatever stuff about it, that's great! It's a nice place to start. Then make your way towards linux.
Linux Distros (Distributions):
Ubuntu = Newbies
Debian = Ubuntu based on this
Fedora = Productivity
Linux Mint 12/13 = Ease of Use
Arch Linux =Advanced
BackTrack = Hacking/Cracking
Tails = Security
Bohdi = Speed
SliTaz = Small & For old hardware + Nice UI
(Just giving you tips here, if you do wanna do this )
Click to expand...
Click to collapse
To be more clear I am employed in the IT field/profession..however you want to describe it...for the past 15 years. More of a Windows Server Administrator position and previous to that various other positions starting in client support. I have played with Ubuntu before and I have used bootable versions of Knoppix and other linux based distros in the past. I just do not use them enough on a regular basis. It is more of a time issue than anything. Arch Linux looks interesting to me. Perhaps enough to try. I appreciate the tips. Regardless playing with the phone is fun for me for now. I have an iPhone as well but I love the flexibility and NON closed ecosystem that android offers. I guess ultimately both are based on Unix/Linux based OSs.
Be careful if you're dd'ing your data, cache, system, stl, bml, etc..
Because there is a chance of bricking your device. I know dd'ing stl5 has a high chance that you'll brick your device.
Click to expand...
Click to collapse
That is exactly why I am asking for step by step. It is really not worth it to me if the potential of bricking is high. I am interesting in playing and learning but not at the stake of losing the cash I put in to play with the phone.
The CSC contains all the info about your carrier, and some other stuff... Lol
Click to expand...
Click to collapse
I figured based on what I read in Darkshado partition mapping post that CSC has the carrier content. Really then that does not seem that important if the carrier is the main part of it to consider it for restoration. Again unless there is other items in there I should be concerned about.
Yes I hate the 5 minute waiting period to post a reply or thread, and i hate the captcha..
Click to expand...
Click to collapse
Well that is 2 votes. Moderators please consider another spam deterrent. Ha!!!
AvrX said:
Backup with cwm 5.0.2.6 and then when you have ext4 flash stock via odin. Root with stock cwm and then flash cwm 5.0.2.6 and restore.
Sent from my GT-S5660 using Tapatalk
Click to expand...
Click to collapse
Well it appears that CWM 5.0.2.7 may have been one of my issues in getting my original backup to restore.
I loaded CWM 5.0.2.6 from the following thread http://forum.xda-developers.com/showthread.php?t=1493932 and I was able to restore my original backup of the stock ROM with no issues. Thanks again Peteragent5 for putting that great post together.
Also a thank you AvrX for that for the suggestion of going back to 5.02.6. Also Darkshado's guidance of sticking with a CWM that supports one file system or the other.
I downloaded and installed the second version of 5.0.2.6 indicated in the 1st post of the thread named S5660M_cwm-5.0.2.6_feb_26_12.zip. Not sure if that is correct or not Peteragent5 as I not totally understanding the difference between Phiexz & Maclaw Roms and My ROMs in your post. I would assume you are speaking of the Custom ROMS created by Phiexz & Maclaw vs ones created by you? Regardless it would be nice to have a bit greater detail so I am confident in which tool to use in which situation.
So question 1 from my original post in this thread has been solved. Well sort of. Still not clear why 5.0.2.7 supports both RFS and EXT4 but it seems like all the functions for formatting are EXT4 based within it. Although the backup I made within it still shows the rfs prior to the *.tar extension.
Based on my last post I have a few new questions. After performing some more testing (trial by fire/trial and error) with CWM I am not sure that I really understand the support of CWM 5.0.2.7 RFS and EXT4 file system as mentioned in my last post.
Typically before I perform a backup of a ROM (in this case the stock ROM which is RFS filesystem based) I perform the following procedure in CWM regardless of the version of CWM
1. wipe data/factory reset
2. wipe cache partition
3. go to advanced menu
4. Wipe Dalvik Cache
5. Wipe Battery Stats
6. Main Menu -> backup and restore
7. Backup
Questions:
1. Is that the correct procedure? Could some steps be left out or added? What is the safest most reliable way? Should I even use those steps before I perform a backup or are they only really to be used when you are having problems? These are all really the same question presented in different ways.
2. If I am using CWM 5.0.2.7 (supports both RFS and EFS) and I perform the wipe data/factory reset, I see that it is Formatting /data /cache /sd-ext etc on the screen. Also with the wipe cache partition option I see Formatting /cache displayed on the screen. When using these functions in CWM 5.0.2.7 does this format the phone for those partitions from RFS to EXT4?
I am beginning to agree with Darkshado's comment
Different builds of CWM are available for the Gio. Some support RFS, others ext4. I'd rather avoid those with dual support as they're not very clear regarding what format they're using for which operation.
Click to expand...
Click to collapse
However if anyone else has done some extensive testing and know the answer to this....then I can move on and stop using tools. I believe that some of the tools are suppose to work and perform a certain operation but do the opposite or not what is claimed or do not explain the functions well enough for me to understand what operation does what. I want to understand....not just do.
The reason I am asking is that when I try to run a restore of an RFS (stock ROM) backup that was preformed in CWM 5.0.2.6 (only RFS supported) or a backup from CWM 5.0.2.7 (supports RFS and EXT4) after performing the above procedures within CWM 5.0.2.7, it always fails with the
dreaded (E:format_volume: format_rfs_device failed on /dev/block/stl12 Error while formatting /system!) error. This is of course after flashing via Odin back to the stock RFS based ROM GT-S5660M_BMC_S5660MUGKG3_S5660MUGKG3_S5660MBMCKG3 from sammobile.com and then entering stock recovery mode and installing CWM 5.0.2.7.
Does CWM 5.0.2.7 change the stock Kernel on my phone to one that supports RFS and EXT4? My assumption is yes but it would be nice to know for sure.
Based on my testing and findings so far I can tell right now that 5.0.2.7 is more EXT4 based then RFS. It will read RFS files and install on an RFS based filesystem (Stock ROM) and it will even make good backups of the RFS system. However it will not restore those RFS backups regardless if they were made in CWM 5.0.2.6 or CWM 5.0.2.7. Now if you flash back to stock ROM again via ODIN and install CWM 5.0.2.6 only RFS supported, you can restore backups of RFS based file systems backups( on a stock ROM system) made in either CWM 5.0.2.6 or CWM 5.0.2.7.
So the verdict is again (finding out the hard way)....DarkShado and AvrX are indeed correct. Use CWM 5.0.2.6 for backups and restores of Stock ROM.
For custom ROMs...which are predominantly EXT4 based now...I guess you need to use 5.0.2.7....but I will use the soley EXT4 based one from now on as the RFS & EXT4 based one I believe is limited. The only thing is if you install the 5.0.2.7 EXT4 only supported version, you will need to use the EXT4 Formatter (installed via CWM) before to make everything work properly before playing with EXT4 based Custom ROMs. Unless EXT4 formatting is built into the installer like it is with enhanced236_06.08.2012.
Morale of the story is again Darkshado is correct in what he was implying....what I am trying to accomplish is "Neat?" "Worth the Trouble"....My answer now...is a "NO".
None of the current versions of CWM "Fully" (read and write) support RFS and EXT4 at the same time and allow you to return to the stock based RFS backup plus play with EXT4 based new Custom ROMs. I know about the EXT4 Formatter....does anyone know of RFS Formatter tool that installable via CWM?
That tool might accomplish what I would like to achieve. Then it really is only a matter of the procedure to follow to make it all work within CWM. Just have to switch between CWM 5.0.2.6 and CWM 5.0.2.7.
Thanks for following the thread and reading my "trial and error" findings. I may perform a summary of my current findings in this post. It would be be a reply to my questions in the first post with the answer to my own questions. However I think I will wait to see if anyone is interested in providing any further comments.
modem issues after flashing anything other than stock
I am facing a similar issue to you TrippleRipple.
Sorry for the lengthy back story..but here it goes;
I am in Saskatchewan on Sasktel and I had originally given this phone to my son flashed with CM9 as a cheap android media and games device...but the screen on my SGS2 broke the other day and my son offered to "rent" his to me to use until my screen replacement comes in. When I put my SIM in the device (unlocked by retrieving code via ADB) it can connect to some providers in the area (Rogers)...but not to my home network of Sasktel. I read in a previous thread here on XDA that there is an issue with the baseband of custom firmware and that you should keep your stock modem for Bell/Telus handsets (Sasktel also falls in that category)....and so..I am trying to completely restore stock FW...to be able to connect to my home network.
Did you/do you have this modem issue as well?
kid___icarus said:
I am facing a similar issue to you TrippleRipple.
Sorry for the lengthy back story..but here it goes;
I am in Saskatchewan on Sasktel and I had originally given this phone to my son flashed with CM9 as a cheap android media and games device...but the screen on my SGS2 broke the other day and my son offered to "rent" his to me to use until my screen replacement comes in. When I put my SIM in the device (unlocked by retrieving code via ADB) it can connect to some providers in the area (Rogers)...but not to my home network of Sasktel. I read in a previous thread here on XDA that there is an issue with the baseband of custom firmware and that you should keep your stock modem for Bell/Telus handsets (Sasktel also falls in that category)....and so..I am trying to completely restore stock FW...to be able to connect to my home network.
Did you/do you have this modem issue as well?
Click to expand...
Click to collapse
To be honest, I have only really been playing with the custom ROMs but not really using them with an active SIM. So unfortunately I am not the best point of reference. I do know the stock firmware on sammobile does have the correct baseband in it as I copied down all of the details of the original out of box rom and it was the same once restored with the stock firmware from sammobile via odin. However with the out of box stock rom, there were issues with texting on SaskTel. You might want to try the enhanced236 ROM. That seemed to work fine on SaskTel with texting as well. However you should of course backup what you have now with CWM so that you can restore it back for your son when you get your other phone back.
I have not tried CM9 with the SIM chip...only with enhanced236. I did however play with CM9 and CM10. Sorry I could not have been of more assistance. Good luck.
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
spuzwuzzel said:
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
Click to expand...
Click to collapse
Odin back to stock, or flash twrp and try that. Also this should not be in this section bud. Prepare to be flamed by the community
Sent from my SGH-T989 using xda app-developers app
I had the same thing happen to me when I updated to the latest one, it would freeze at either restoring, or wiping cache. Luckily I was able to just reboot, and everything was fine on the phone, I then downgraded to 5.XXX
I've been having the same issue on stock recovery, where it sometimes it freezes at wiping, then flash the one from rom manager and its all good. by the way mods please move the thread to Q/A
Wrong section bro. Please see the noob video.
Sent from my SGH-T989 using xda premium
You don't have to Odin stock or any of that stuff, just fastboot flash the 6.0.0.5 version (or that last one that worked for you) and you should be fine.
spuzwuzzel said:
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
Click to expand...
Click to collapse
Ok, don't panic. I've been having this twice a day every day for the past little while. I first started having this problem when I flashed MIUI JB, but very soon after every JB ROM out there started hanging on me, or killing my recovery in this fashion. It's fixable, though for the life of me I can't tell you what causes it.
Don't ODIN back to stock. Not yet anyway.
ODIN your very first recovery, just as if you are about to root your phone for the first time. ODIN CWM 5.0.2.7, not 6.0.1.4. Yes, it's ancient, I know. Catch your phone as it's rebooting after the flash, and get it to enter recovery. Don't let it boot into whichever ROM you have installed. Then go to MOUNT > MOUNT USB and attach your phone to the computer. Copy Darkside Superwipe over. Unmount from the computer and unmount from the phone. Then get CWM to run the script. You must superwipe your phone, so if you have something important, hope you have a backup. This time around it won't hang on you.
Your phone is recovered, you can now flash anything you want and it will work. You can restore your nondroid backup as well and this will also work. If your nandroid back is in the new CWM format, you will want to flash CWM v6 first. Feel free to flash whichever recovery works for you, but CWM 5.0.2.7 is your fallback recovery in case you need to recover your phone again. It is the only one that does not seem to get corrupted in this way.
You can ODIN back to stock now if you want to make absolutely sure everything is wiped clean, but in my experience this does not contribute much to the overall cleanliness of things: it's not called Superwipe for nothing. It doesn't hurt, though: as long as you do it AFTER you have superwiped, or not even ODIN will recover your phone. It really scared me once when I skipped the superwipe step and was left with a 100% stock phone which wouldn't boot.
---------- Post added at 10:28 PM ---------- Previous post was at 10:12 PM ----------
Careful with ODIN: Make sure you have NO PIT file selected, or you will kill your phone! Been there, done that, and I don't recommend it. Do it by the book!
kangelov said:
Ok, don't panic. I've been having this twice a day every day for the past little while. I first started having this problem when I flashed MIUI JB, but very soon after every JB ROM out there started hanging on me, or killing my recovery in this fashion. It's fixable, though for the life of me I can't tell you what causes it.
Don't ODIN back to stock. Not yet anyway.
ODIN your very first recovery, just as if you are about to root your phone for the first time. ODIN CWM 5.0.2.7, not 6.0.1.4. Yes, it's ancient, I know. Catch your phone as it's rebooting after the flash, and get it to enter recovery. Don't let it boot into whichever ROM you have installed. Then go to MOUNT > MOUNT USB and attach your phone to the computer. Copy Darkside Superwipe over. Unmount from the computer and unmount from the phone. Then get CWM to run the script. You must superwipe your phone, so if you have something important, hope you have a backup. This time around it won't hang on you.
Your phone is recovered, you can now flash anything you want and it will work. You can restore your nondroid backup as well and this will also work. If your nandroid back is in the new CWM format, you will want to flash CWM v6 first. Feel free to flash whichever recovery works for you, but CWM 5.0.2.7 is your fallback recovery in case you need to recover your phone again. It is the only one that does not seem to get corrupted in this way.
You can ODIN back to stock now if you want to make absolutely sure everything is wiped clean, but in my experience this does not contribute much to the overall cleanliness of things: it's not called Superwipe for nothing. It doesn't hurt, though: as long as you do it AFTER you have superwiped, or not even ODIN will recover your phone. It really scared me once when I skipped the superwipe step and was left with a 100% stock phone which wouldn't boot.
---------- Post added at 10:28 PM ---------- Previous post was at 10:12 PM ----------
Careful with ODIN: Make sure you have NO PIT file selected, or you will kill your phone! Been there, done that, and I don't recommend it. Do it by the book!
Click to expand...
Click to collapse
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
spuzwuzzel said:
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
Click to expand...
Click to collapse
Look, I'm sorry for your troubles but there is a good reason why we have four different sections. This thread being in DEVELOPMENT is only causing clutter. You will get much better help if its moved to its proper place, Q&A or general. Please PM a Mod to move this.
Sent from my SGH-T989 using xda premium
spuzwuzzel said:
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
Click to expand...
Click to collapse
I am referring to the process you followed to install CWM on a stock phone. It didn't come with CWM already loaded, so you must have loaded it somehow. If not with ODIN, then what did you use?
kangelov said:
I am referring to the process you followed to install CWM on a stock phone. It didn't come with CWM already loaded, so you must have loaded it somehow. If not with ODIN, then what did you use?
Click to expand...
Click to collapse
I dont really know where to find 5.0.2.7. the website doesnt seem to have it. I used revolutionary
Thank you for your contribution to the development of the gs2.
Sent from my SGH-T989 using xda premium
Download the clock work mod app from playstore. Then your first choice after opening the apk, your first possible choice is flash cwm, do that. Pm me after that if you need help. he should be good now thanks
Sent from my SGH-T989 using xda app-developers app
Rushing said:
Download the clock work mod app from playstore. Then your first choice after opening the apk, your first possible choice is flash cwm, do that. Pm me after that if you need help. he should be good now thanks
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
There is no clockworkmod app, unless you mean rom manager. At least, I can't find any. Also, I can't even get my rom to load at all
spuzwuzzel said:
There is no clockworkmod app, unless you mean rom manager. At least, I can't find any. Also, I can't even get my rom to load at all
Click to expand...
Click to collapse
Now that you are in the right place, I will help you. It looks like you flashed a corrupted recovery. What you need to is Odin flash CWM. Go here
http://forum.xda-developers.com/showthread.php?p=27290471
Download Odin and recovery.tar, and Odin flash it. Will boot up just fine after. Don't fear Odin. Its safe as long as you are careful and READ!!
Sent from my SGH-T989 using xda premium
LoopDoGG79 said:
Now that you are in the right place, I will help you. It looks like you flashed a corrupted recovery. What you need to is Odin flash CWM. Go here
http://forum.xda-developers.com/showthread.php?p=27290471
Download Odin and recovery.tar, and Odin flash it. Will boot up just fine after. Don't fear Odin. Its safe as long as you are careful and READ!!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Ya Odin flash the recovery tar is probably the easiest way to go
Sent from my Galaxy Nexus using xda app-developers app
Odin is a tool used internally by Samsung. As such, you can't expect Samsung to write you a manual. Be very careful, you can cause a lot of damage with it. It is powerful, though: it can bring your phone back from the brink of death. Or it can take a healthy phone and send it over the edge. What you are doing now is something every rooter does on day 1, and only after days and days of research. I am uncomfortable with what you are going to do now given that you have never done this before, but you have no choice: it's this or a useless phone.
Here's the rundown:
A PIT file is something like the Master Boot Record of your harddisk. Problem is, the first partition is something like your computer's BIOS: it tells your phone how to bootstrap. It can bootstrap into the normal mode, which runs Android, or it can initiate Download mode. Download mode is what ODIN needs to replace parts or all of your phone's software. If something goes wrong with that bootloader, your phone is something called a hard brick: it won't power on, it won't even run Download mode so that you can recover it back to stock. It is dead. If that ever happens, you need something called a JTAG flash: you send your phone out somewhere, and someone takes it apart, hopefully carefully, plugs a programmer into an engineering port on your phone's logic board, and reprograms the bootloader back again). Now with PIT file having the major potential to trash things completely, you really have to pay attention you don't load the wrong one. Problem is, the ODIN you just downloaded DOES come with a PIT file, and that PIT file is WRONG for your device. Follow the instructions! Follow the instructions really really carefully. Don't check off extra things! Don't uncheck things that should be checked! Don't add PIT files! Make sure you load the right file to the right place in ODIN. Your phone depends on it.
ODIN will program your phone from scratch, but you wouldn't want to use it too often. It's a dangerous tool, as you can imagine, and it is meant to replace your phone's software, not maintain it! That's why we have Recovery. Recovery is what you use to do basic maintenance to Android, such as factory reset and clean cache and stuff. With those custom recoveries out there, you gain the added ability to flash custom ROMs and a few other things as well, which is what this forum is all about. So, step one in anyone seeking to root their phone is, flash a custom recovery using ODIN, since you need Download mode for that. In an ideal world, you will never need to use ODIN again after you flash your custom recovery. Well, in the real world, you should needed it only very infrequently.
Your phone first got its custom recovery from a tool designed to automate things for you, and sent you flashing without ever giving you an idea how your phone works. Now you don't know how to recover your phone from a flash gone wrong: in the long run that tool did not do any favours to you. The steps I gave you will bring your phone back to life, it brought mine several times already. Something about those new JB ROMs corrupts every recovery I have tried. I don't know why, I don't know how, but it does it. To make matters worse, ODIN without a proper PIT file cannot repartition your phone and fix whatever mess caused the problem to begin with, so restoring stock directly won't do the trick, you need to flash custom recovery, to fix recovery, and then Superwipe to recreate and realign your system, data and cache partitions: that's a good chunk of your phone. So, after you do this, you should be back in business. From beginning to end, if you know what you are doing, the entire process should not take more than 30 minutes, but don't rush. Take your time: take hours, take days. Take all the time you need.
Read before you do anything, and ask if you don't understand.
I have this issue every now and then when I use the stock recovery (the one i use to root) with ODIN, where it get stuck on everytime i try to wipe or flash, What I used to do is factory stock with Odin, then realize the even though it froze on wiping factory data, the rom wiped!! so what i do know is install rom manager and flash their recovery and problem solve,
this thread is very useful thanks guys.
by the way i dont flash JB roms yet until I they completely fix the call issues so. do you think its not only JB roms?
gypsy214 said:
I have this issue every now and then when I use the stock recovery (the one i use to root) with ODIN, where it get stuck on everytime i try to wipe or flash, What I used to do is factory stock with Odin, then realize the even though it froze on wiping factory data, the rom wiped!! so what i do know is install rom manager and flash their recovery and problem solve,
this thread is very useful thanks guys.
by the way i dont flash JB roms yet until I they completely fix the call issues so. do you think its not only JB roms?
Click to expand...
Click to collapse
I have had the problem you describe as well. Some ROMs like certain recoveries better than others and if you end up with the wrong combo, they don't boot. Flashing the right recovery after that fixes it instantly, without even a need to reflash the ROM. No, this is a different problem.
We are talking about a problem where flashing a ROM corrupts your recovery so it will stop working on you completely: it just hangs, it won't restore, it won't flash anything. Also, one or more of the ROM partitions on your phone get corrupted somehow so that even ODIN back to stock doesn't get your phone working again (you end up with a fully stock phone that doesn't boot). Maybe the two are related, but I will let those who know more speak. I am just a regular guy who fiddles with his phone a lot more than he should.
As for the problem being on JB only: I've only had it when flashing JB ROMs. I first noticed it with MIUI, but then AOKP started acting up, and when I finally dared to flash a CM10 unofficial nightly for the first time, it happened too... And then I noticed it doesn't happen always, only sometimes, and other times it just leaves me with a JB ROM that doesn't boot, and in some rare occasions: it works without a hitch. Go figure.
Ok, so I've been flashing Roms since I first had the G1 but my step sons Galaxy S II is giving me fits as of late.
I've been working on it for over 2 days now and can not figure the problem even after reading through all the how to's and individual rom threads. I initialy rooted his phone back in April/May and had a early ICS phandroid rom on it. However I wanted to move him to JB. I've done the customary wipe data/cache but no matter what JB rom I flash it goes into what I believe is a bootloop. I've read several places it been said to let sit after flashing for 10 minutes so I let sit for 20 and it was still on boot (but no obvious point where you can tell it's looping).
When I went to restore his backup that would no longer boot at all, just a blank screen. So long story short I restored everything to stock then updated to ICS through keis. and tried the process again thinking it might need updated firmware/radio. Same thing happened and I had to restore stock and update through keis again. I am now at a complete loss as I update my phone (One S) and wifes (GSIII) atleast once a week on nightlies.
The one thing that I thought was odd is both on the original 2.3.6 and now 4.0.4 when I go into settings at search for update i get a message saying "no firmware". Not sure if that means anything but it didn't sound right to me.
Any help or suggestions would be overwhelmingly appreciated.
You will get different methods on here but for starters what recovery are you running. Thats problem 1 I guarantee for your bootloop. I use TWRP 2.3 which can be found by downloading goo.im and flashing it from the menu screen. You can also go to the forum here in development for the zip file.
When using TWRP or any touch recovery do not use the wipe scripts. Lets start there.... Since the method to flashing is basically the same all over its just the wiping procedure with the wrong recovery can be tricky
I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.
jhenson496 said:
I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.
Click to expand...
Click to collapse
I personally prefer that recovery and I'm running a cm 10 on my phone with no issues at never had anything. Yes it's rather simple to put on an even if you want to try the CWM touch recovery by all means go ahead
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.
jhenson496 said:
Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.
Click to expand...
Click to collapse
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
Click to expand...
Click to collapse
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637
I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped
abesgs2 said:
I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped
Click to expand...
Click to collapse
My friend I linked the zips in the post right above yours
playya said:
CHANGELOG for 2.3.0.0:
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637
Click to expand...
Click to collapse
Just saw that last part by Playa, sorry didnt mean to kang you haha... but hes got it down ^^^
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
lordcheeto03 said:
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
Click to expand...
Click to collapse
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
Swetnes said:
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
SectorNine50 said:
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
Click to expand...
Click to collapse
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
SectorNine50 said:
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
Click to expand...
Click to collapse
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
drumist said:
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
Click to expand...
Click to collapse
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
You are correct, the Nitro is P930. And I'm sure this doesn't need pointing out, but when you download the ROM, make sure it's for P93x and not SU640. Most of the ROMS in the developer section have versions for both models.
Also, when you say you can't access CWM after flashing a ROM, how are you trying to access it? Holding Power+Volume down until the Factory Reset screen pops up? It still shows that screen even with CWM installed, but when you press the power button to perform the factory reset it SHOULD take you into CWM Recovery instead.
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
To access recovery, turn the device completely off. (If you're in a bootloop, pull battery or hold power button for ~20 seconds until screen stays off.) Then when phone is off, press and hold volume down and power buttons at the same time, not releasing until you see text asking if you want to factory reset. Press power button twice to confirm and you'll get to recovery.
Is this the method you're using to try to get to CWM?
My guess as to why you are getting bootloops is that you aren't wiping data first.
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
SectorNine50 said:
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
Click to expand...
Click to collapse
Good luck. Other possible things to try:
1) Check zip MD5 hash (or just redownload and replace) to make sure it's not corrupted.
2) Reformat entire SD card.
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
SectorNine50 said:
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
Click to expand...
Click to collapse
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
drumist said:
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
Click to expand...
Click to collapse
Ah, thank you! I must've been viewing an old thread. Now that I look at the version number, it appears that's the version I had been hunting for since the newest one didn't work.
Interesting, I most certainly misunderstood, I was under the impression that "rooting" the device was a filesystem level permission change. Good to know!
It seems like we are getting closer to a solution here. Thanks for your patience!
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
SectorNine50 said:
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
Click to expand...
Click to collapse
Yeah, the new one (6.0.1.5) just came out. I'll have to test it to see if it works for me.
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Malnilion said:
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Click to expand...
Click to collapse
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I really enjoy the integration Rom Manager/CM Updater has with CWM. If twrp is capable of running the install scripts those two use, I might consider trying it out, but I don't really like manually going through the steps to flash a rom every day.
I have been looking around for about an hour or two trying to find a solid tutorial on how to install a custom recovery to install new Roms. I flashed my phone onto Virgin Mobile on FH13. It seems to me that there is more than meets the eye to installing a recovery on this phone. I really don't want to mess anything up at all. Could anyone guide me the right way as to how I can get CWM on my phone? I appreciate any help you can give me. Thanks!
Recovery is packed into the kernel on this phone. Flash a kernel tar through ODIN if you want, it will trigger the yellow triangle though. If your already rooted you could use Mobile ODIN. If you already have some form of custom recovery and are just trying to switch up you can flash the kernel zip in recovery.
rwilco has pretty much every kernel for every purpose but since your on stock you will either want a repacked stock or custom tw kernel - http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/ICS
If your unfamiliar then keep asking questions. Our phone has a bug in its eMMC firmware triggered during format operations on the stock kernel as of Android 4.0. The specifics are detailed but all you really need to know is grab a kernel with a safe recovery, or even going as far as AGAT's custom kernel which has more work around in place to prevent a factory reset or rom install from turning your phone into a super brick.
RainMotorsports said:
Recovery is packed into the kernel on this phone. Flash a kernel tar through ODIN if you want, it will trigger the yellow triangle though. If your already rooted you could use Mobile ODIN. If you already have some form of custom recovery and are just trying to switch up you can flash the kernel zip in recovery.
rwilco has pretty much every kernel for every purpose but since your on stock you will either want a repacked stock or custom tw kernel - http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/ICS
If your unfamiliar then keep asking questions. Our phone has a bug in its eMMC firmware triggered during format operations on the stock kernel as of Android 4.0. The specifics are detailed but all you really need to know is grab a kernel with a safe recovery, or even going as far as AGAT's custom kernel which has more work around in place to prevent a factory reset or rom install from turning your phone into a super brick.
Click to expand...
Click to collapse
Also new to the e4gt, im currently rooted on fh13.
say i want to flash paranoidandroid, which kernel (which includes recovery?) would you recommend?
also this is either flashed from odin (pc) or can be done through mobile odin?
then once kernel is flashed, i can then reboot into recovery, wipe and flash rom/gapps?
sorry for all the questions, just want to make sure!
bongzilla said:
Also new to the e4gt, im currently rooted on fh13.
say i want to flash paranoidandroid, which kernel (which includes recovery?) would you recommend?
also this is either flashed from odin (pc) or can be done through mobile odin?
then once kernel is flashed, i can then reboot into recovery, wipe and flash rom/gapps?
sorry for all the questions, just want to make sure!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1953783
RainMotorsports said:
Recovery is packed into the kernel on this phone. Flash a kernel tar through ODIN if you want, it will trigger the yellow triangle though. If your already rooted you could use Mobile ODIN. If you already have some form of custom recovery and are just trying to switch up you can flash the kernel zip in recovery.
rwilco has pretty much every kernel for every purpose but since your on stock you will either want a repacked stock or custom tw kernel - http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/ICS
If your unfamiliar then keep asking questions. Our phone has a bug in its eMMC firmware triggered during format operations on the stock kernel as of Android 4.0. The specifics are detailed but all you really need to know is grab a kernel with a safe recovery, or even going as far as AGAT's custom kernel which has more work around in place to prevent a factory reset or rom install from turning your phone into a super brick.
Click to expand...
Click to collapse
My phone already has root. Everything else is stock. 4.0.4, build FH13, with no custom recoveries.
I don't understand what you mean in your second paragraph with "repacked stock" or "custom tw kernel".
I am completely lost as to where I should be going. My plan is to install this rom: http://goo.im/devs/Shabbypenguin/E4GT-Nightlies
How would I go around to getting this on my phone?
Also, what about this rom: http://forum.xda-developers.com/showthread.php?t=1810315
I am not sure which rom runs the fastest and most efficient. There are so many kernels for so many things, I have absolutely no idea which kernel to flash and how to flash it.
EDIT: So I have done some more reading up and I THINK I can starting to understand some of it. I assume the steps are to:
1. Install Mobile Odin Lite on my phone.
2. Flash the EL26 kernel on Odin Lite. Link to kernel: http://forum.xda-developers.com/showthread.php?t=1662295 (first kernel on the page)
3. This part I am kinda lost. Not sure if that kernel installed a new recovery or not. I assume I just reboot and go into recovery.
4. Nandroid a backup of my ICS stock that is on now? Can I even go back to this stock backup after putting on a new Rom? Which kernel would I need to install backup of stock?
5. Wipe data, dalvic, and install new Rom using instruction it came with. My problem is I want to run this Rom: http://goo.im/devs/Shabbypenguin/E4GT-Nightlies and it has no instructions. I assume you just wipe data and dalvic?
6. flash Rom, then flash Gapp? It doesn't have a link for any of the Gapps, so either I have to find a link to download Gapp or that rom already comes with it? Not sure.
7. Reboot into new Rom? Not sure if I missed a step or not.
Another question I have is with the kernels. Can I just leave it on the EL26 kernel for daily use of the phone? Say I want to install maybe cm10 next, do I just keep it on EL26?
Sorry for the spam of questions. I like to be 100% certain.
Best bet if your trying to install CM9 is to go to the EL26 CWM kernel as all of the AOSP rom instructions dictate. Using the EL26 kernel means your phone will only boot to Download and Recovery as it will only boot gingerbread roms.
Download the nightly you want to the device and then flash the EL26 CWM kernel in Mobile ODIN. After its all over with you might need to battery pull if you messed up booting into recovery and then boot into recovery (power + vol up). Install the rom. Install gapps. Wipe cache/dalvik but as I will recommend below you should just backup everything and a full wipe.
You can nandroid if you want but it will be making a copy of the ICS rom you have with the EL26 kernel on it so it is literally a restore to the point your starting from not where you were just before that. Its still a good idea if your afraid of losing things. I would use Super Backup from the market to backup your Contacts, Call Logs and MMS. Wipe cache and dalvik and all that. But realisticly you should backup your apps and data if you have Titanium Backup and start fresh just factory reset after your on CM9. Restore your apps with data (no system data) after that. A clean install will present the least of issues, even the Samsung updates from one rom to another are not without issues.
You can not boot anything but gingerbread with EL26 and once you install a rom you will be on the kernel with that rom. So you will have a Linux 3 android kernel with cwm 6 if you go with a CM9 nightly. From there you can flash the next nightly or the next beta etc. Older stuff will not flash from your new setup as AOSP roms have switched to a new device name in the build.prop.
As far as gapps here it is - http://goo.im/gapps/gapps-ics-20120429-signed.zip and don't forget to put this on the device ahead of time or you will have to mount usb and transfer using the pc in recovery.
RainMotorsports said:
Best bet if your trying to install CM9 is to go to the EL26 CWM kernel as all of the AOSP rom instructions dictate. Using the EL26 kernel means your phone will only boot to Download and Recovery as it will only boot gingerbread roms.
Download the nightly you want to the device and then flash the EL26 CWM kernel in Mobile ODIN. After its all over with you might need to battery pull if you messed up booting into recovery and then boot into recovery (power + vol up). Install the rom. Install gapps. Wipe cache/dalvik but as I will recommend below you should just backup everything and a full wipe.
You can nandroid if you want but it will be making a copy of the ICS rom you have with the EL26 kernel on it so it is literally a restore to the point your starting from not where you were just before that. Its still a good idea if your afraid of losing things. I would use Super Backup from the market to backup your Contacts, Call Logs and MMS. Wipe cache and dalvik and all that. But realisticly you should backup your apps and data if you have Titanium Backup and start fresh just factory reset after your on CM9. Restore your apps with data (no system data) after that. A clean install will present the least of issues, even the Samsung updates from one rom to another are not without issues.
You can not boot anything but gingerbread with EL26 and once you install a rom you will be on the kernel with that rom. So you will have a Linux 3 android kernel with cwm 6 if you go with a CM9 nightly. From there you can flash the next nightly or the next beta etc. Older stuff will not flash from your new setup as AOSP roms have switched to a new device name in the build.prop.
As far as gapps here it is - http://goo.im/gapps/gapps-ics-20120429-signed.zip and don't forget to put this on the device ahead of time or you will have to mount usb and transfer using the pc in recovery.
Click to expand...
Click to collapse
Ah, I read it twice and now it makes more sense. I have a pretty good idea of what to do now.
Put rom and gapp on phone, install EL26, backup, full wipe, flash rom and gapp, rom will install new kernel for me, then just reboot.
Last question, I just want to make sure. What exactly is a full wipe on this phone. I have done plenty of full wipes on the evo 4g. I am just asking because I hear some people have problems when they do a full wipe.
I really appreciate your help. Thank you!
Sorry if I jumbled everything together in my post by the I was running out the door. But this Hurricanne has stopped that and I regret not taking my time.
Well what I mean is a factory reset which formats /Cache and /Data. When you install the rom its going to format /System prior to writing the new firmware/rom. /Data has all your user apps, their data and your information etc. This does not wipe the Internal SD or the External SD though at times a line saying it was does come up in CWM.
Just don't do a Factory reset on the stock kernel you are on now, its fine on EL26 its fine on the kernels that come with the CM9 nightlies. Super Backup apparently does app's now too. I have never used it since I have Titanium Backup Pro but figured its also worth mentioning.
A note on turning back. As I said before if you flash the EL26 CWM kernel you wont be able to boot the ICS rom installed on the phone. At that point to go back instead of forward you can flash the FH13 kernel in desktop ODIN or the zip in CWM and you will have the FH13 kernel instead of EL26 and be back where you were. But once you flash the EL26 CWM kernel your goal at that point is flashing your rom of choice in CWM and not things like booting the phone.
You should be "okay" coming from a dirty install just wiping cache. But you may never know if a problem your having is the rom or some left over data unless you go clean and factory reset. Its a choice and its also a choice you can make later as you can always reset later. I would back up anything important first before doing any of this. Not so much a worry about bricking, as just about any normal situation will be recoverable, but more so to the point of if you have to wipe the phone and start from scratch.
RainMotorsports said:
Sorry if I jumbled everything together in my post by the I was running out the door. But this Hurricanne has stopped that and I regret not taking my time.
Well what I mean is a factory reset which formats /Cache and /Data. When you install the rom its going to format /System prior to writing the new firmware/rom. /Data has all your user apps, their data and your information etc. This does not wipe the Internal SD or the External SD though at times a line saying it was does come up in CWM.
Just don't do a Factory reset on the stock kernel you are on now, its fine on EL26 its fine on the kernels that come with the CM9 nightlies. Super Backup apparently does app's now too. I have never used it since I have Titanium Backup Pro but figured its also worth mentioning.
A note on turning back. As I said before if you flash the EL26 CWM kernel you wont be able to boot the ICS rom installed on the phone. At that point to go back instead of forward you can flash the FH13 kernel in desktop ODIN or the zip in CWM and you will have the FH13 kernel instead of EL26 and be back where you were. But once you flash the EL26 CWM kernel your goal at that point is flashing your rom of choice in CWM and not things like booting the phone.
You should be "okay" coming from a dirty install just wiping cache. But you may never know if a problem your having is the rom or some left over data unless you go clean and factory reset. Its a choice and its also a choice you can make later as you can always reset later. I would back up anything important first before doing any of this. Not so much a worry about bricking, as just about any normal situation will be recoverable, but more so to the point of if you have to wipe the phone and start from scratch.
Click to expand...
Click to collapse
That clarified a lot, thanks.
So I did it all. I did a factory reset from the new kernel. did dalvic also. I installed the new rom and gapp. Problem is that once I reboot, it shows the Galaxy SII screen, then goes into a black screen. I can't turn it back on again, so I remove the battery and it can restart. Does the same thing though. I followed your instruction and http://e4gtcm.blogspot.com/p/cm9-install-guide.html
What did I do wrong? I am worried I messed up my phone completely.
EDIT: So I went back into recovery and it was now a new version of CWM. I did everything over again; factory reset, cache, dalvic, and it is doing the same thing. Boots up "Galaxy SII" screen, then a black screen. It seems to still be on in the black screen seeing that it doesn't "turn" on again. I can hold if for 15 second or so for it to reset and does the same thing. Why is there a black screen?
Sorry for not checking back. Your probably freaking right now lol but relax your at a good point everything is fine.
Either a bad download or the nightly you went with happens to be a baddy. I am still on 10/20 I was gonna flash 10/28 today but the weather is screwing with me. goo.im seems pretty slow today.
Download another, battery pull and hold vol up + power until it hits recovery then go into mounts and mount usb storage hook a usb cable to the pc and copy over another build. I would say try 10/20 just because it works pretty good but that won't stop another bad download in which case you have to try try again.
Worst case from here we can just odin you back to stock rooted FH13 or your choice of other. Your phone is fine from what you have told me so far. I can upload one of the builds I have if you think ti would help any.
RainMotorsports said:
Sorry for not checking back. Your probably freaking right now lol but relax your at a good point everything is fine.
Either a bad download or the nightly you went with happens to be a baddy. I am still on 10/20 I was gonna flash 10/28 today but the weather is screwing with me.
Download another, battery pull and hold vol up + power until it hits recovery then go into mounts and mount usb storage hook a usb cable to the pc and copy over another build. I would say try 10/20 just because it works pretty good but that won't stop another bad download in which case you have to try try again.
Worst case from here we can just odin you back to stock rooted FH13 or your choice of other. Your phone is fine from what you have told me so far.
Click to expand...
Click to collapse
Phew! I was pretty positive that I could still get back to something working, just my paranoid self was getting tense. I got 10/28. I guess I will do 10/20. Do you know what the other updates have? I would hate to install something that isn't working its most efficient.
Again, thank you so much. You were of great help! Good luck with the weather issue. Hope you're safe!
I stopped following chris's experimentals so i am not sure what the most recent focuses have been. The Nightlies have whatever code was commited. They are built automatically and can range from very stable to not booting at all. I dont have any of the links on me but someone can get it to you. Reading commits is not exactly 100% user friendly especially if your not a developer. But they often have clues. I would follow the CM9 Beta thread and the CM9 User Support Threads - http://forum.xda-developers.com/showthread.php?t=1874374 and http://forum.xda-developers.com/showthread.php?t=1720771
I used to DL nightlies from work over 3g or 4g all the time and would get a bad dl and end up in situations where even my experienced self felt like I couldn't fix it till I got home and always got the phone running within an hour without the assistance of a near by pc.
I am uploading 10/20 to my server just in case its in Chicago so if your away from the weather it should be unaffected for the most part. Glad its not in NY anymore.
EDIT - http://android.rainmotorsports.net/10-20-CM9-d710-KANG.zip the md5 hash as I have it is 66246125ACDBEF2EBF2144E0CBFEBB7B and it matches the md5 listed on goo.im
RainMotorsports said:
I stopped following chris's experimentals so i am not sure what the most recent focuses have been. The Nightlies have whatever code was commited. They are built automatically and can range from very stable to not booting at all. I dont have any of the links on me but someone can get it to you. Reading commits is not exactly 100% user friendly especially if your not a developer. But they often have clues. I would follow the CM9 Beta thread and the CM9 User Support Threads - http://forum.xda-developers.com/showthread.php?t=1874374 and http://forum.xda-developers.com/showthread.php?t=1720771
I used to DL nightlies from work over 3g or 4g all the time and would get a bad dl and end up in situations where even my experienced self felt like I couldn't fix it till I got home and always got the phone running within an hour without the assistance of a near by pc.
I am uploading 10/20 to my server just in case its in Chicago so if your away from the weather it should be unaffected for the most part. Glad its not in NY anymore.
EDIT - http://android.rainmotorsports.net/10-20-CM9-d710-KANG.zip the md5 hash as I have it is 66246125ACDBEF2EBF2144E0CBFEBB7B and it matches the md5 listed on goo.im
Click to expand...
Click to collapse
I just got it downloaded. It is now up and running perfectly. I appreciate all your help man, thanks a bunch. I live in Washington state. So the weather wont affect me.
Good evening all. I hope this is the right forum to post my question about recovery for my e4g touch. I recently rooted my phone and my phone is currently on the fi27 build. Is there a recovery i can put on there now to go ahead and start flashing ruins, or will i have to wait for qbkng77 to post his video on you tube on putting cwm recovery on fi27 rooted e4g touch? Thanks in advance for the help!
Sent from my SPH-D710 using xda app-developers app
n1stunna84 said:
Good evening all. I hope this is the right forum to post my question about recovery for my e4g touch. I recently rooted my phone and my phone is currently on the fi27 build. Is there a recovery i can put on there now to go ahead and start flashing ruins, or will i have to wait for qbkng77 to post his video on you tube on putting cwm recovery on fi27 rooted e4g touch? Thanks in advance for the help!
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I assume you do the same thing as I did. Get the EL26 kernel and flash it with Mobile Odin. I would wait on someone else to confirm that though.
Another really quick question. I want to overclock my phone. I tried using setcpu and the overclocker it came with. It only goes to a max of 1200 but I know it can go higher. I am guessing I need another kernel. What kernel can I use?
joshlete said:
Another really quick question. I want to overclock my phone. I tried using setcpu and the overclocker it came with. It only goes to a max of 1200 but I know it can go higher. I am guessing I need another kernel. What kernel can I use?
Click to expand...
Click to collapse
You either need a kernel with built in over clock support(you'd see the CPU slider go up to 1400-1600 automatically if it was). Or a kernel that supports over locking in tegrak, which you "load over clock module" with in tegrak.
Both Kuban kernel and some of Agats kernels have built in support, mine you need to use tegrak as I have not added built in yet
You can get them all in rwilco's (awesome) kernel repository stickied in development
Sent from my SPH-D710 using xda premium