Related
Is there a current ICS leak that has cwm built into it after loading it now?
I am currently running Calkulins.E4GT.ROM.v2.8.1 with Rogue recovery...
Is there an ics i can flash using that recovery, and once done still have recovery?
Is that what this Rogue *Stock FB17* v1.2.1 (CWM Zip) is, from http://forum.xda-developers.com/showthread.php?t=1390393 here?
I dont ever want to touch Odin again, i seem to have problems with that.
I also want to be able to flash back to a stock backup if i need, so i dont want to lose my recovery ability.
Scribes said:
Is there a current ICS leak that has cwm built into it after loading it now?
I am currently running Calkulins.E4GT.ROM.v2.8.1 with Rogue recovery...
Is there an ics i can flash using that recovery, and once done still have recovery?
Is that what this Rogue *Stock FB17* v1.2.1 (CWM Zip) is, from http://forum.xda-developers.com/showthread.php?t=1390393 here?
I dont ever want to touch Odin again, i seem to have problems with that.
I also want to be able to flash back to a stock backup if i need, so i dont want to lose my recovery ability.
Click to expand...
Click to collapse
Technically, not really.
The official way to do it is flash calks fb17, boot up, and then odin rogues fb17 kernel/recovery.
HOWEVER.... Once booted into calks fb17 you can download rom manager,
Flash recovery from there selecting sgs2 as the phone and NOT e4gt
Boot into recovery from rom manager
Flash Rogue's fb17 kernel/recovery
Worked well for me.
ics
There have been many many bricks when trying to flash from ics back to gb .. The data partition on several phones has been fried leading to unrecoverable brick .... so far most going back to gb from ics have been using odin to be safe .... dont touch the cwm touch recovery with ics .... it leads to bricks .... The safest so far has been odin a gb rom then odin cwm recovery and then run your nandroid from there ..Be safe
I am running the ICS FB17 pre-rooted leak and flashed the zip with rouge, it had the stock ics recovery so i went back to this page (http://forum.xda-developers.com/showthread.php?t=1342728) and downloaded the latest auto root and ran option D and the option A to flash the rouge for the FB15 modem.
Scribes said:
Is there a current ICS leak that has cwm built into it after loading it now?
I am currently running Calkulins.E4GT.ROM.v2.8.1 with Rogue recovery...
Is there an ics i can flash using that recovery, and once done still have recovery?
Is that what this Rogue *Stock FB17* v1.2.1 (CWM Zip) is, from http://forum.xda-developers.com/showthread.php?t=1390393 here?
I dont ever want to touch Odin again, i seem to have problems with that.
I also want to be able to flash back to a stock backup if i need, so i dont want to lose my recovery ability.
Click to expand...
Click to collapse
If you are concerned about having to "touch" Odin again, then you shouldn't be flashing any of this stuff for now..
ICS/CWM
did just as RigorousNinja went back to GB 4.0 by PhathomHacker no problemshttp://forum.xda-developers.com/showthread.php?t=1342728
The oneclick installer will put cwm on any ics build I have seen so far. I just used it on FB21 Rooted in fact. Just run letter D then CWS-15;Rogue
http://uperoo.com/index.php?r=dl&a=1293311
Sorry to whoever for reposting but I have no idea where I got it from now..
Thanks to Steady Hawkin for FB17+CWM-Rogue(repack)
It is available in the Auto Root sticky in Development or in my signature.
The latest one includes FB17+CWM-Rogue as well.
Epix4G said:
There have been many many bricks when trying to flash from ics back to gb .. The data partition on several phones has been fried leading to unrecoverable brick .... so far most going back to gb from ics have been using odin to be safe .... dont touch the cwm touch recovery with ics .... it leads to bricks .... The safest so far has been odin a gb rom then odin cwm recovery and then run your nandroid from there ..Be safe
Click to expand...
Click to collapse
Can you elaborate why it is bad to flash back to GB through CWM? I've done it twice already due to overheating in ICS and haven't had any issues. I just want to know if damaging my phone by doing that :/
SuperSwagSauce said:
Can you elaborate why it is bad to flash back to GB through CWM? I've done it twice already due to overheating in ICS and haven't had any issues. I just want to know if damaging my phone by doing that :/
Click to expand...
Click to collapse
It isn't bad to flash back to GB through CWM per se.
It is bad to fake flash CWM Touch onto an ICS linux 3.0 kernel and do a restore or wipe. The combination of CWM Touch and the ICS linux 3.0 kernel has caused many people to hose their /data partition in such a way that even repartition using ODIN doesn't allow /data to be written to anymore.
sfhub said:
It isn't bad to flash back to GB through CWM per se.
It is bad to fake flash CWM Touch onto an ICS linux 3.0 kernel and do a restore or wipe. The combination of CWM Touch and the ICS linux 3.0 kernel has caused many people to hose their /data partition in such a way that even repartition using ODIN doesn't allow /data to be written to anymore.
Click to expand...
Click to collapse
Ahh so it's a CWM Touch issue you say? That's a relief
SuperSwagSauce said:
Ahh so it's a CWM Touch issue you say? That's a relief
Click to expand...
Click to collapse
That's the one people happen to have had bad experiences with, but the general issue is "fake/temporary" flashes which end up pairing recoveries with kernels they may not have been intended to work with or may not have been tested with, then trying to operations on your phone which may overwrite sections that are hard to recover from.
CWM Touch if integrated (ie repacked with) and tested with a kernel it appears to work ok.
Honestly, just take the time to get to know Odin... its really safe and useful when you invest the time (which is very little). and this is coming from a 'noobs' perspective. As for CWM i have used it as well (not touch) and been okay, but like everyone else has warned... be careful.
sfhub said:
That's the one people happen to have had bad experiences with, but the general issue is "fake/temporary" flashes which end up pairing recoveries with kernels they may not have been intended to work with or may not have been tested with, then trying to operations on your phone which may overwrite sections that are hard to recover from.
CWM Touch if integrated (ie repacked with) and tested with a kernel it appears to work ok.
Click to expand...
Click to collapse
Gotcha, so my steady hawkin FB17 kernel/recovery should be good.
I'm currently on Calkulin's GB ROM and am ready to finally make the jump to ICS, likely the Blazer ROM. That ROM hasn't been updated for a few weeks, which has obviously been a pretty eventful period of time. So I'm assuming, after I flash this from my existing CWM custom recovery, and because this ROM includes the stock kernel, that I'll need to additionally flash something like agat63's kernel and recovery to be considered "safe"? And because I'll be initially using the stock recovery with the ROM, that means I'll need to do it through ODIN or Mobile ODIN? Trying to make sure I've got all of my ducks in a row before I attempt the upgrade.
And I suppose I should ask this too, even though I know it will be speculation... I'm not in a huge hurry to make the jump to ICS, so would you guess that the Blazer ROM will eventually be upgraded to include an updated/safe kernel and recovery, thereby saving myself this small effort (which in my amateur hands still has the chance to go wrong)?
Thanks for the feedback.
Yes using the stock kernel can cause bricks. You can use mobile Odin to flash agat kernel with recovery. I did. Then from there you should be safe.
So wipe, flash ICS rom you want, then flash the agat kernel (this way you don't have to do it in mobile Odin or Odin) then from there you should be good to go
Sent from my SPH-D710 using xda app-developers app
1. Odin the touchwiz kernel by chris41g which has a safe CWM recovery
2. Boot into said recovery and wipe data
3. Flash Blazer ICS
4. Enjoy
So perhaps this speaks to some basic misunderstanding of how this works, but since I'm on an EL29 GB ROM and kernel/recovery (Rogue kernel & recovery), can I not flash to Blazer ICS directly? And if I flash that new ROM, won't I end up with the stock kernel/recovery included in that ROM? And therefore still be "unsafe" at the end?
I hope that if I'm dead wrong that at least the question makes sense.
Thanks.
gg_99 said:
So perhaps this speaks to some basic misunderstanding of how this works, but since I'm on an EL29 GB ROM and kernel/recovery (Rogue kernel & recovery), can I not flash to Blazer ICS directly? And if I flash that new ROM, won't I end up with the stock kernel/recovery included in that ROM? And therefore still be "unsafe" at the end?
I hope that if I'm dead wrong that at least the question makes sense.
Thanks.
Click to expand...
Click to collapse
I just did what your asking. Make a back up. Flash the calks wipe all and then flash the rom. Read the blazer OP before you doing anything. I had no issues running like a champ
Sent from my SPH-D710 using xda app-developers app
And what was the resulting kernel/recovery *after* the flash? That seems to be the trick in my mind. Want to make sure I end up with a safe kernel/recovery after flashing the ROM.
I just went back to calks. im not sure on the kernel but the recovery was Agats tREC v0.2.0 sorry for the late response and lack of info.
i just flashed my phone to ff18 using mobile odin. it is completely stock but i want to add cwm. i was going to use sfhub's autoroot pacakge to flash cwm. however im confused if i should choose ff18 cwm agat src or cwm agat?
any help would be appreciated...thanks
hardwirk1 said:
i just flashed my phone to ff18 using mobile odin. it is completely stock but i want to add cwm. i was going to use sfhub's autoroot pacakge to flash cwm. however im confused if i should choose ff18 cwm agat src or cwm agat?
any help would be appreciated...thanks
Click to expand...
Click to collapse
Depends what you're going to flash as a ROM...I think SRC means safe recovery meaning you can flash cm9 or an aosp rom thru it. Your best bet is just read up on his kernel and then decide.
Edit: from sfhub on his one click post
FF18+CWM-agat-src which is a recompiled kernel that is safe from EMMC along with agat's variation of CWM. chris worked with agat on this release, but it isn't the same as chris's CWM, however it is safe.
FF18+CWM-agat this is the same safe CWM as above, but repacked with the stock unsafe kernel. That means all operations handled by the recovery like wipe data/factory reset, and nandroid restore are safe. There is only slight exposure if a ROM install does a format() and include an unsafe update-binary in their installs. AFAIK no *current* ROMs do that anymore, but if you install older AOKP/CM9 ROMs you might run into that situation.
You can always just use Mobile ODIN to install whichever CWM you desire, or you can just stick the zImage from any ROM install package into the copy2sd\000root directory and choose the "generic" zImage option (there is a video on how to do that in the first post. Basically the generic zImage option will install any zImage you want to provide in the same fashion as the built-in zImage (kernel/recovery)
Sent from my SPH-D710 using xda app-developers app
I suggest you find Agat's thread in the dev section with all his new kernels built from source code and flash version 2.3 that just got released yesterday. You can use Odin on your pc but that will give you the yellow triangle. Mobile Odin won't.
I just got my replacement(after a hard brick trying JB) and I've got a few questions before I brick this one too:
1. Ive decided to odin EL29 EVERY TIME I want to flash a new rom, just to be safe. If I use CMW with EL29 and decide to try out CM9, Do I always need to flash a aokp kernel? Or is that built into the CM9 install?
2. If I like CM9, and want to make a nandroid backup of it, do I need to Odin back to EL29 first to back it up? Or is it safe to do it with the recovery that comes with CM9?
3. If the answer to #2 is yes, meaning I do have to odin back to EL29, how do I restore my backup? Let me explain:Lets say I flash CM9, make a nandroid of CM9, then decide to try out say a different rom, like a TW rom. Then I hate the TW rom and wanna restore my backup of CM9. Do I need to ODIN back to EL29 to restore the nandroid? I read in the "how not to brick my..." thread its bad to restore a ICS rom from a GB Kernel. Can someone please explain?
Ive really, really tried to search and read as much as possible before asking, but a lot of the threads are old and have contradicting information. Sorry for being so noobish but I dont wanna brick my new phone. I come from Evo, Evo3d, Hp Touchpad, etc, where there arent as many issues to flash customs roms. Ive rooted and flashed custom roms ever since the PPC6600, 100's of times and NEVER had a problem. Sorry, this just really confuses me for some reason!!!
You really don't need to Odin back to el29 but if you wanna play it safe and not brick just Odin the el26 kernel and flash from there thats all you can flash from internal and from external, I don't have anything against other devs ics kernel but I just like to keep it safe even if I'm on a jb from I use the kernel that's on that jb kernel to flash the el26 reboot recovery and start flashing or restoring backups I do use the ics or jb kernels to flash but not to flash roms.
Sent from my SPH-D710 using Tapatalk 2
vinscuzzy said:
I just got my replacement(after a hard brick trying JB) and I've got a few questions before I brick this one too:
1. Ive decided to odin EL29 EVERY TIME I want to flash a new rom, just to be safe. If I use CMW with EL29 and decide to try out CM9, Do I always need to flash a aokp kernel? Or is that built into the CM9 install?
Click to expand...
Click to collapse
A kernel is already included with CM9, so there's no need to flash anything else. However, if you'd like to use one of chris41g's custom kernels like RC10-CWM6 or RC11-TWRP, you're welcome to flash them during your ROM flash session or after the fact.
vinscuzzy said:
2. If I like CM9, and want to make a nandroid backup of it, do I need to Odin back to EL29 first to back it up? Or is it safe to do it with the recovery that comes with CM9?
Click to expand...
Click to collapse
It's always safe to make a Nandroid backup, regardless of the kernel/recovery on your phone. Where a problem could potentially arise is on a Nandroid restore, because the restore function formats the EMMC. However, it should be perfectly safe to restore a Nandroid backup using the kernel/recovery included with CM9. The bottom line is, you want to make sure that if the kernel/recovery on your phone that your using to restore the backup is based on ICS, that it's been properly patched for EMMC lock safety.
vinscuzzy said:
3. If the answer to #2 is yes, meaning I do have to odin back to EL29, how do I restore my backup? Let me explain:Lets say I flash CM9, make a nandroid of CM9, then decide to try out say a different rom, like a TW rom. Then I hate the TW rom and wanna restore my backup of CM9. Do I need to ODIN back to EL29 to restore the nandroid? I read in the "how not to brick my..." thread its bad to restore a ICS rom from a GB Kernel. Can someone please explain?
Click to expand...
Click to collapse
If you want to be extra careful, and only use a GB based kernel/recovery like EL26 to restore your Nandroid backups, you would Mobile Odin the EL26 kernel+CWM, hold down the power button or pull the battery on the reboot, then boot into that recovery and restore your backup. Whatever kernel/recovery was in your backup will overwrite the EL26 kernel and that will be the new kernel/recovery on your phone when you reboot.
Thanks for the quick responses. Still kinda confused. :angel:
Do I have to use mobile Odin for what you explained in #3? And is mobile Odin as safe as pc Odin?
And, would it be safe to have the el26 kernel on my card and just flash that(with recovery, not odin) everytime I wanna do any flashing/wiping?
I feel so stupid!! Maybe someone could write down THEIR step by step "safe" procedure on flashing/wiping a new rom and backing up/restoring, and ill just follow that. :laugh:
Here's the step by step safe method
1: get mobile Odin or mobile Odin pro
2: download the flash kernel from mobile Odin pro
2a: if using mobile Odin download the flash kernel for sph-d710 from chainfires mobile Odin thread
3: download el26+cwm kernel.tar to your PC
4: copy kernel to SD card and keep a copy on your PC in case of an oh sh!t moment
5: download a cm9 compatible kernel.zip(you will need this in recovery)
6: backup mobile Odin and it's data in titanium backup or similar app
7: open mobile Odin and choose the el26+cwm kernel.tar
8: flash kernel.tar with flash firmware option in mobile Odin
9: when the device reboots hold vol+ and power til you boot to recovery(or pull battery then boot to recovery)
10: flash cm9 kernel.zip in recovery
11: make nandroid backup
12: reboot to cm9
12a: if you forgot to flash the cm9 kernel before making the nandroid flash it now to boot cm9
12b: if kernel wasn't flashed before making nandroid, when u restore the nandroid flash the kernel before rebooting.
13: profit!
These steps work for any rom 4.0.3 and above with very minimal chance of bricking, since el26+cwm is considered immune to the brick bug
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
vinscuzzy said:
Thanks for the quick responses. Still kinda confused. :angel:
Do I have to use mobile Odin for what you explained in #3? And is mobile Odin as safe as pc Odin?
And, would it be safe to have the el26 kernel on my card and just flash that(with recovery, not odin) everytime I wanna do any flashing/wiping?
Click to expand...
Click to collapse
I think it's been proven via user experience that Mobile Odin is a safe as PC Odin. In fact, one could make the argument that its safer, as there's no way to kick out the cord during a flash, or stick the wrong file in the wrong slot. The only negative to it is it will not flash modem files on CDMA devices like ours.
Mobile Odin is generally preferred to temp flash a GB kernel because 1) it's easier and 2) it doesn't trigger the yellow triangle or increase the Odin flash count like PC Odin does when you flash a kernel that has not been signed by Samsung. So while being easier, MO makes life even easier by not having to fix those two issues later.
So with that said, yes it's a good idea to keep the EL26+CWM5.zip file on your sd card at all times. Mine is always there, hanging out and drinking beers with Calkulin's Format All zip.
-EViL-KoNCEPTz- said:
Here's the step by step safe method
1: get mobile Odin or mobile Odin pro
2: download the flash kernel from mobile Odin pro
2a: if using mobile Odin download the flash kernel for sph-d710 from chainfires mobile Odin thread
3: download el26+cwm kernel.tar to your PC
4: copy kernel to SD card and keep a copy on your PC in case of an oh sh!t moment
5: download a cm9 compatible kernel.zip(you will need this in recovery)
6: backup mobile Odin and it's data in titanium backup or similar app
7: open mobile Odin and choose the el26+cwm kernel.tar
8: flash kernel.tar with flash firmware option in mobile Odin
9: when the device reboots hold vol+ and power til you boot to recovery(or pull battery then boot to recovery)
10: flash cm9 kernel.zip in recovery
11: make nandroid backup
12: reboot to cm9
12a: if you forgot to flash the cm9 kernel before making the nandroid flash it now to boot cm9
12b: if kernel wasn't flashed before making nandroid, when u restore the nandroid flash the kernel before rebooting.
Click to expand...
Click to collapse
Awesome man, thanks so much for clarifying!
So from here on out, if want to flash ANY other rom, aosp or TW, I'd:
Follow steps 7-9, then wipe(data,cache,dalvik) then flash the rom right?
And if I'm NOT making a nandroid backup, skip 10-12?
Also, should steps 7-9 be repeated if I'm restoring a backup?
I mobile odin the el26 kernel for testing the Jelly Bean roms but since I have not been returning to stock and only going between CM9 Nightlies I have been doing it from CWM 1 or more times a day. CM9 alpha 6 has a safe recovery and all the of the nightlies as well. There was a couple of mismerged versions of Chris41G's kernel that were safe to wipe from but unsafe to flash unsafe roms from.
CM9 Alpha 5 for example has an unsafe updater binary while Alpha 6 does not, I would never flash Alpha 5 from an ICS kernel unless that kernel is one that replaces updater binaries for flashing.
When in doubt EL26 CWM. The rest of the time just use a safe kernel and a known safe rom.
vinscuzzy said:
Awesome man, thanks so much for clarifying!
So from here on out, if want to flash ANY other rom, aosp or TW, I'd:
Follow steps 7-9, then wipe(data,cache,dalvik) then flash the rom right?
And if I'm NOT making a nandroid backup, skip 10-12?
Also, should steps 7-9 be repeated if I'm restoring a backup?
Click to expand...
Click to collapse
You will still need to flash an ics kernel in cwm to get it to boot after flashing el26 to use recovery unless you are freshly installing a rom cuz it will include a kernel in the rom zip. I just mOdin el26+cwm anytime I need to use recovery. But yeah you have to steps right. If you ever end up in a boot loop having the el26 tar on your PC is your go to to get back into recovery when you can't boot android to use mOdin
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
-EViL-KoNCEPTz- said:
You will still need to flash an ics kernel in cwm to get it to boot after flashing el26 to use recovery unless you are freshly installing a rom cuz it will include a kernel in the rom zip. I just mOdin el26+cwm anytime I need to use recovery. But yeah you have to steps right. If you ever end up in a boot loop having the el26 tar on your PC is your go to to get back into recovery when you can't boot android to use mOdin
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
Click to expand...
Click to collapse
Thanks again for ALL the responses!
OK, think I'm getting a handle on all of this now. Will it ever get to a point where its just safe all the time to flash roms? It'd be cool if someone came up with an app that could scan the .zips to make sure they're safe. Or, why don't devs just always use .tar files to flash through Odin instead of zips through recovery? OR Is it a big pain to make .tar files?
P.s. I hope that didn't sound at all condescending to any of the wonderful devs. I'm just curious and obviously new to Samsung, and they're flashing procedures. :angel:
They do have tars available you have to flash them threw PC Odin. Zips are usually safe & handy on the go when your away from the computer with CWM & M. Odin just flash & go! Options are always good...
vinscuzzy said:
Thanks again for ALL the responses!
OK, think I'm getting a handle on all of this now. Will it ever get to a point where its just safe all the time to flash roms? It'd be cool if someone came up with an app that could scan the .zips to make sure they're safe. Or, why don't devs just always use .tar files to flash through Odin instead of zips through recovery? OR Is it a big pain to make .tar files?
P.s. I hope that didn't sound at all condescending to any of the wonderful devs. I'm just curious and obviously new to Samsung, and they're flashing procedures. :angel:
Click to expand...
Click to collapse
The emmc bug is a Samsung issue and, while trigged by the emmc_cap_erase code in ICS kernels during wipes, is actually located in the firmware for the emmc controller itself. As such its not likely we'll ever have a true "fix" for it as it would require Samsung to 1. Directly admit fault... and 2. Somehow patch the affected firmware... What we have now are basically known-good workarounds, essentially the "safe" kernels have the code that triggers the bug removed. These are more than sufficient, and a huge thanks to the kernel devs who've made ICS flashing possible and to sfhub/entropy512/garwynn and others who did the research on the emmc bug and figured out how it was triggered...
So that said the rom you are flashing shouldn't have a whole hell of a lot to do with whether it is safe or now, all that matters is how the kernel you are on handles the wipe when flashing, as that is the point at which the emmc bug is triggered.
Sent from my SPH-D710 using xda app-developers app
Wow, there are some really well written, intelligent, and we'll informed replies in this thread. What the hell is going on around here?
Sent from my SPH-D710 using Tapatalk 2
I have installed several roms with no issues in the past, but I seem to have gotten myself turned around. I had no issues with ICS roms, but I can't quite remember what process I was using. I am wanting to install CM10, and I tried using ODIN 1.85 to install the EL26 tar, but when my phone rebooted into CWM, I wasn't sure what to do from there. I am using ODIN to go back to GB (Odin One Click) right now, and then I am going to flash CM10...could anyone provide me any direction? I am reverting to GB from stock ICS. I read in the wiki that flashing to GB from ICS with a bad USB cable can cause brick? Was the flash necessary, or could I have just stuck with flashing the EL26 tar file, and done a factory wipe/reset, dalvik cache wipe, etc from there. I have no idea why I am so confused. Thanks for the help.
I guess the bigger question may be as well...do I need to flash back to stock GB before flashing any rom, or is flashing the EL26 CWM tar file in ODIN 1.85 sufficient, and then reboot into that recovery (vol up + power) and wipe and flash zips from there?
Thanks!
Using the el26+cwm kernel for recovery is OK, it's not necessary to revert the entire rom to GB. You just won't be able to boot to your ics rom when having el26 installed since a GB kernel won't boot an ICS rom.
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
Thanks evil konceptz. You are always very helpful sir.
Sent from my SPH-D710 using xda premium
yea.. just odin to el26 cwm tar and go into recovery then do proper wipes flash cm10 and jb gapps and reboot.. i prefer calks format all instead of wiping seperately
Sent from my SPH-D710 using xda app-developers app