New: XDA launches forum for app developers. Discuss coding, tools, marketing, and more.
XDA Developers Android and Mobile Development Forum
Forgot your password?
 
Post Reply+
Tip us?
 
acerti0519
Old
#231  
Junior Member
Thanks Meter 0
Posts: 4
Join Date: Feb 2012
Default CM9 and Clockwork Recovery Issue.

Hello, I'm new to the Epic Touch and flashed CM9 and I keep loosing the clockwork recovery. I use the GB rooted odin image to restore back to and then
flash the cm recovery and flash the rom I want. Now my question is can I just flash back cwm recovery while on cm9 without bricking my device. And is team win recovery stable enough yet.
 
watchout5
Old
#232  
Junior Member
Thanks Meter 0
Posts: 5
Join Date: Dec 2011
Quote:
Originally Posted by acerti0519 View Post
Hello, I'm new to the Epic Touch and flashed CM9 and I keep loosing the clockwork recovery. I use the GB rooted odin image to restore back to and then
flash the cm recovery and flash the rom I want. Now my question is can I just flash back cwm recovery while on cm9 without bricking my device. And is team win recovery stable enough yet.
The way I understood CM9 when I used it in alpha 3 there was no CWM recovery, just stock, I don't think alpha4 added a custom recovery. Currently there are some issues where if you use Factory Wipe data from a ICS recovery it will completely brick your phone, it's not 100%, we really don't know all the specifics, but since the beginning of CM9 they didn't include a custom recovery for this reason. Some people have had luck using odin to flash a custom recovery on it however I'd advise against it. If you really want CM9 to have a custom recovery look to see if other people have had better success with. Personally I went to Blu FE10 ROM because there are a lot more kernals other people have tested as working but I'm still rocking the FD26 rogue kernal that may be your best bet for a custom recovery.
 
ih8aol
Old
(Last edited by ih8aol; 19th May 2012 at 02:06 PM.) Reason: forgot to include quoted text so post would have been confusing otherwise
#233  
ih8aol's Avatar
Junior Member
Thanks Meter 0
Posts: 23
Join Date: May 2008
Location: Cloquet
Quote:
Blazer released his Alpha ICS ROM for VIPs so I went ahead and tried it. I made a Nandroid for GB just in case something messed up. The instructions said flash CWM Touch after flashing ICS so that's what I did. Everything worked for like the first 20 minutes... I was having fun with Face Unlock and everything. But then all of a sudden I was locked out of my phone - the Face Unlock prompt wouldn't even show and it would say my PIN was incorrect. So I naturally freaked out and tried to restore GB...and yeah you know the rest. It got stuck so like 30 minutes later I pulled the battery. I tried Odining back to EL29 but then I would get stuck at Data.img.

I really really want to try an ICS ROM but now I'm nervous that I'll brick again :/
From what I have read in this thread http://forum.xda-developers.com/show....php?t=1644364 , two things were probably responsible for your brick. The CWM touch and restoring a GB from ICS.
I guess you could say "Double Whammy!"
 
Kebetz
Old
#234  
Account currently disabled
Thanks Meter 105
Posts: 305
Join Date: Jan 2012
Location: Seattle

 
DONATE TO ME
Quote:
Originally Posted by watchout5 View Post
The way I understood CM9 when I used it in alpha 3 there was no CWM recovery, just stock, I don't think alpha4 added a custom recovery. Currently there are some issues where if you use Factory Wipe data from a ICS recovery it will completely brick your phone, it's not 100%, we really don't know all the specifics, but since the beginning of CM9 they didn't include a custom recovery for this reason. Some people have had luck using odin to flash a custom recovery on it however I'd advise against it. If you really want CM9 to have a custom recovery look to see if other people have had better success with. Personally I went to Blu FE10 ROM because there are a lot more kernals other people have tested as working but I'm still rocking the FD26 rogue kernal that may be your best bet for a custom recovery.
Quote:
Originally Posted by ih8aol View Post
From what I have read in this thread http://forum.xda-developers.com/show....php?t=1644364 , two things were probably responsible for your brick. The CWM touch and restoring a GB from ICS.
I guess you could say "Double Whammy!"
My hard brick was neither touch recovery or a cross-compatible restore.
Simply factory resetting on ICS with an ICS based kernel's recovery while getting ready for a fresh install.
People have let their guard down as far as custom recovery goes as long as you aren't using it for anything that touches partitions.
I personally would recommend playing it safe and handling all of your flashing/backup/restoring through EL26, as suggested almost everywhere.
 
ih8aol
Old
#235  
ih8aol's Avatar
Junior Member
Thanks Meter 0
Posts: 23
Join Date: May 2008
Location: Cloquet
Quote:
Originally Posted by Kebetz View Post
My hard brick was neither touch recovery or a cross-compatible restore.
Simply factory resetting on ICS with an ICS based kernel's recovery while getting ready for a fresh install.
People have let their guard down as far as custom recovery goes as long as you aren't using it for anything that touches partitions.
I personally would recommend playing it safe and handling all of your flashing/backup/restoring through EL26, as suggested almost everywhere.
I did a factory reset with one of the first ICS leaks; FC07 I believe and went back to EL26 for a while. I probably got lucky.
 
ijoshv2
Old
#236  
ijoshv2's Avatar
Senior Member
Thanks Meter 48
Posts: 192
Join Date: Apr 2010
Location: Reno, NV
Just posted in the DEV section about this, linking to this page. http://forum.xda-developers.com/show...php?p=26386997

I've heard that flashing a non-ICS kernel from ODIN on a computer solves these issues.. Has ANYONE confirmed this?
Show respect to your fellow XDA members. We're all a family, here.

Phone: SGS II EPIC 4G Touch ROM: CM9 Beta 1 for E4GT
Tab: Debating on my next Tab.. PM me your favorite? (;

"Owned an iPhone once.. Never again will I stoop that low." -Me

If someone helped you, or provided ANY useful knowledge, thank them.
Only takes a moment!
 
garwynn
Old
#237  
garwynn's Avatar
Recognized Developer / Recognized Contributor
Thanks Meter 4933
Posts: 3,115
Join Date: Jul 2011
Location: Chi-town
Until Xstatic has a chance to update the main post there is new information on this issue. Please refer to the first post on this thread:

http://forum.xda-developers.com/show....php?t=1644364

Issue can happen even without being on CM9 or CWM - for now the safest is to do any wipes, factory resets, etc from a GB kernel.
 
xST4T1K
Old
#238  
xST4T1K's Avatar
Senior Member - OP
Thanks Meter 214
Posts: 371
Join Date: Jan 2012
Quote:
Originally Posted by garwynn View Post
Until Xstatic has a chance to update the main post there is new information on this issue. Please refer to the first post on this thread:

http://forum.xda-developers.com/show....php?t=1644364

Issue can happen even without being on CM9 or CWM - for now the safest is to do any wipes, factory resets, etc from a GB kernel.
Just updated with a link to SFHUBS thread
Phone
Samsung Galaxy S2 E4GT
My Wizzing Beanis 1.1.0
------------------------------------------------------
Tablet
Asus Transformer TF300T
Energy Rom JB
The Following 2 Users Say Thank You to xST4T1K For This Useful Post: [ Click to Expand ]
 
RainMotorsports
Old
#239  
RainMotorsports's Avatar
Senior Member
Thanks Meter 648
Posts: 1,243
Join Date: Dec 2011
Quote:
Originally Posted by ijoshv2 View Post
I've heard that flashing a non-ICS kernel from ODIN on a computer solves these issues.. Has ANYONE confirmed this?
Flashing any Kernel is safer through odin than Mobile Odin. No roms kernels or resets should be flashed from an ICS kernel that does not have a workaround for the 0x19 eMMC firmware bug. Flashing kernels and roms or performing resets is safe on gingerbread kernels.

If you flash a non ICS kernel while on an ICS rom your phone will not boot to Android. You will be able to use recovery. Flashing the EL26 CWM kernel through ODIN is the safe way to change roms while on ICS for the moment.
Desktop i5 2500K @ 4.5Ghz | ASUS P8Z68-V PRO | 16GB Corsair Vengeance 1600 | Seasonic X750
MSI GTX570 TF III @ 950/1900/2300 | 2TB 5900 + 2X320GB 7200 RAID0 | Zalman CNPS9900 MAX
Laptop ASUS G50VT | Core2Duo T9600 @ 3.3Ghz | 9800M GS/GTS @ 650/1625/900
Phone Galaxy SII Epic 4G Touch | CyanogenMod 10 | FI25 Modem
 
dynoboot
Old
(Last edited by dynoboot; 23rd May 2012 at 02:52 AM.) Reason: forgot to ask question/clarity
#240  
Junior Member
Thanks Meter 0
Posts: 3
Join Date: May 2012
Thanks for this thread, I didn't realize until today the danger that awaited me. I flashed a leaked 4.0.3 and because of instability wanted to flash back. Last night before realizing the potential troubles by this I attempted to wipe and install from rom manager and CWM (specifically I tried Caulkins format all from Android recovery, and to install Venom rom from Rom manager after and selecting full wipe). They failed, however I haven't noticed any unusual problems beyond that (neither got very far, after probably a second or two gave me the little android guy with a red exclamation, rebooted fine and works as it has). I wanted to Odin back to stock rooted as suggested in this thread, but am now a bit worried that my attempted wipe last night may spell doom if I try to OC now. Is there a specific way to test and see if I can write to /data before flashing?

I'm wondering if I should hold off for a bit and see if perhaps I should wait a bit and see if perhaps devs come up with some sort of fix for this, or if I should try to flash OC and avoid any other potential pitfalls that may arise. Also, when you say do not wipe, does that mean I should use the NODATA flash or can I use the other one? Apologies if this should be posted in QA, I thought it pertinent to the threads topic.