After numerous issues with ICS I'm trying to revert to 2.3.6.
-I have (2) different 2.3.6 .zip roms that I'm trying and both produce install aborted errors in CWM. ROM's I've tried so far can be found here...
(2nd and 3rd on the list)
http://forum.xda-developers.com/showthread.php?t=1548750
-install of "ICS Smooth Ice 3.1" DOES work via CWM
-.tar via Odin 1.85 to stock ATT 2.3.5 DOES work
-CWM version is as follows
"ClockworkMod TOUCH 5.5.0.4 v3.5"
I'm doing all the regular things such as wiping caches, formatting etc... and as stated above the ICS rom does work still, just not GB. Is there some MD5 check it does that's failing or something similar? I've gone through everything starting with stock out of box 2.3.5 rom and can't flash anything but ICS. Looking for more GB roms to test right now.
Edit: BoneSTOCKeteer rom from November seems to be working as well. So maybe it's limited to the ROM's from the link above. I don't see any reason why all these others would work while those specifically, do not.
Dug a little deeper and found other's having MD5 checksum errors with the .zip
Did this, and am up and running now!
http://forum.xda-developers.com/showpost.php?p=23746464&postcount=56
Hi all,
I got a verizon samsung galaxy s3 about a week ago and immediately flashed the pre-rooted stock ROM and then unlocked bootloader and flashed CM10 with success. I have been using it and enjoy the ROM but want to experiment with the stock (rooted) touchwiz ROM because some of the features seemed nice.
I downloaded the pre-rooted ROM which comes up if you search that term and verizon galaxy s3. I flashed it to my phone using Odin as instructed and it says "pass!" But the phone will not boot past the "Samasung Galaxy S3" splash screen. I tried clearing user data/factory reset from recovery but still does not boot. I was able to restore my previous CM10 backup using recovery, thank god, but still I'm unable to flash the original stock-prerooted ROM and boot. I tried it about 4 times with two different downloads and two different versions of Odin.
Is there a version which I can flash from CWM rather than going through Odin? Any help would be appreciated.
Thanks
There's plenty of stock roms, such as cleanrom, synergy, bean's, which will all give you the stock experience plus some. Did you make a backup after you rooted? That should always be the FIRST thing you do after you root.
iamjackspost said:
There's plenty of stock roms, such as cleanrom, synergy, bean's, which will all give you the stock experience plus some. Did you make a backup after you rooted? That should always be the FIRST thing you do after you root.
Click to expand...
Click to collapse
No I did not unfortunately. Which of those ROMs you mentioned would you recommend? I liked the contact groups, Swype contact to call or text, but not the bloatware.
Why not try CleanROM??
jmorton10 said:
Why not try CleanROM??
Click to expand...
Click to collapse
Thanks y'all. Just downloaded and flashed CleanROM. What a fancy installer.
I made a GOBackup of my apps and messages/calls prior to flashing the new ROM. I can restore that to this different ROM, right?
Thanks again
Hi
Everyone is talking about this aroma something to wipe before flashing new roms
I googled it, but i found there are 2 aromas, installer and file manager
Which one is used to do the full wipe?
Do i need both software?
Thank you
Sent from my GT-N8000 using xda app-developers app
bombamanz said:
Hi
Everyone is talking about this aroma something to wipe before flashing new roms
I googled it, but i found there are 2 aromas, installer and file manager
Which one is used to do the full wipe?
Do i need both software?
Thank you
Sent from my GT-N8000 using xda app-developers app
Click to expand...
Click to collapse
Aroma is a dev tool allowing a graphical user interface for users installing custom roms. It is customized by a dev to allow users the ability to add/change/modify rom features and settings. For our device there are 3 roms installed through aroma though only 2 give us the option to perform a wipe android revolution hd by mike1986 and omega by indie when running the script from your recovery it launches aroma installer and both of the mentioned roms give you the option of wiping your device before continuing with setup. Be careful of which recovery you use, most users agree the newer cwm recoveries dont like aroma and freeze on some screens. Not a huge deal as this just requires a reboot which will bring you back to cwm. The original high on android from the android dev how to root guide by zedomax seems to work well and from personal experience i can tell you twrp works as well. Hope this helps
Specialp said:
Aroma is a dev tool allowing a graphical user interface for users installing custom roms. It is customized by a dev to allow users the ability to add/change/modify rom features and settings. For our device there are 3 roms installed through aroma though only 2 give us the option to perform a wipe android revolution hd by mike1986 and omega by indie when running the script from your recovery it launches aroma installer and both of the mentioned roms give you the option of wiping your device before continuing with setup. Be careful of which recovery you use, most users agree the newer cwm recoveries dont like aroma and freeze on some screens. Not a huge deal as this just requires a reboot which will bring you back to cwm. The original high on android from the android dev how to root guide by zedomax seems to work well and from personal experience i can tell you twrp works as well. Hope this helps
Click to expand...
Click to collapse
First off, I have the N8013, not sure what you have. I found your post because i couldn't figure out what this damn aroma thing everyone is talking about is. so thanks for your response on that.
But i have a question, what version on TWRP are/were you using? Did you just install it from goomanager or rommanager(clockwork) or did you have to flash from odin?
I'm not excited about using this high on android recovery, so when you said you used twrp i figured i would ask.
Best recovery is:
eggwardo said:
First off, I have the N8013, not sure what you have. I found your post because i couldn't figure out what this damn aroma thing everyone is talking about is. so thanks for your response on that.
But i have a question, what version on TWRP are/were you using? Did you just install it from goomanager or rommanager(clockwork) or did you have to flash from odin?
I'm not excited about using this high on android recovery, so when you said you used twrp i figured i would ask.
Click to expand...
Click to collapse
Some RECOVERY had problems with aroma instaler. I tried a lot of them CWM, TRW etc. but only one of them have no problem when I instaling something where was the aroma been. This Recovery is in my signature. Here : HighOnAndroid Recovery
Even KitKat custom ROMs I flashed without problem.
It's my opinion only, but I'm very satisfied with it! Peter
I've crawled through the development. I've flashed a ROM before, but went back to a rooted stock version because of the bugs in the builds I was using. But now, basically any time I flash something new, it bricks at the Galaxy Tab 2 7.0 screen.
I've done:
Flashed back to non-root stock firmware (newer)
Then flashed the CF Autoroot, installed Mobile Odin, flashed CWM official 6.0.2.3 for the 3113. When I install CM9, brick.
PA doesn't brick immediately but sticks at the splash with the shark.
So, I flashed back to non-root stock, CF Autoroot, installed CWM 6.0.1.1 and tried again. All ROMS besides PA hang at boot screen (like before), PA hanging at the shark.
I figured it was a kernel issue? So, I've tried both Dhollmen and AGNI. No change.
I can get it to rooted stock JB, but I don't *want* that, I want something that isn't so freaking bloated and buggy.
Ideas?
*edit*
So, after installing TWRP 2.5 on top of stock, I downloaded Rom Manager, installed CWM and CM9 through that. Got past the initial boot screen, but seem to be stuck on CM Splash. Would flashing older stock image and trying from there help?
This might seem like a dumb question since you say you have flashed ROMs before: are you doing a "clean" install? I also will wipe cache and dalvic cache AFTER each install. I only have "bricked" a device one time and that is when I tried short cuts. I also ALWAYS follow the developers instructions to the letter.
Sent from my GT-3113 running DF-2
I am trying to update my Radio/modem file with the JB Android 4.3 Radio file. It requires that I install CWM 6.0.3.7. Can I install this alongside my TWRP 2.6.3.0 installation or as I have read, it will overwrite my TWRP recovery mode? If it will overwrite, how do I switch between? Just reflash through ODIN using PDA? That seems like a lot of work and the possibilities of breaking might be high just overwriting Customer Recoveries?
If I would install this JB Radio for Android 4.3, how would I go back to GB? I can't find a single GB Radio/Modem. Could I use Radio files for GB instead of wiping and installing stock GB ROM [No Root, No Custom Recovery, but it includes the GB Radio/modem]. The reason I am worried about this, if I need to load my original stock GB 2.3.6 backup with root from my nandroid, I would need the original GB Radio and the nandroid backup/restore feature doesn't include that. All advice is greatly appreciated.
The Radio Does Not Get Backed Up By Cwm/twrp Backup(nandroid) Method.
Click to expand...
Click to collapse
[RADIO][UCMC1] For I727/I727R [09-APR-2013]
http://forum.xda-developers.com/showthread.php?t=2228292
[Q] I have CWM and TWRP installed, is that OK?
http://forum.xda-developers.com/showthread.php?t=2122152
[ROM][ics][uclf5] •∞ EMBRYO •∞ 4.1 •∞ [08-jul-2012] [It has ICS radio files, but no GB files]
http://forum.xda-developers.com/showthread.php?t=1754473
Just flash it with twrp. It'll work just like if you did it with cwm.
I have read that some of the zip files does work with TWRP as well. However I am interested in using the following Custom Rom [SuperLite AOKP JB 4.3 v1.0]. That installation requires CWM 6.0.3.7, because it will prevent the infamous black screen reboot issue. What about GB radio file & installing on top of or installing side by side TWRP & CWM?
[ROM][AOKP]SUPERLITE AOKP JB 4.3 V1.0| BYO | SLgapps | SEPT 30/13
http://forum.xda-developers.com/showthread.php?p=46066949
Pick a recovery and use it. Backups are not cross compatible. If you make a backup with cwm it won't work with twrp.
You can flash radios with either. Just pick one.
Sent from my HTC One using Tapatalk 4
lowao said:
I have read that some of the zip files does work with TWRP as well. However I am interested in using the following Custom Rom [SuperLite AOKP JB 4.3 v1.0]. That installation requires CWM 6.0.3.7, because it will prevent the infamous black screen reboot issue. What about GB radio file & installing on top of or installing side by side TWRP & CWM?
[ROM][AOKP]SUPERLITE AOKP JB 4.3 V1.0| BYO | SLgapps | SEPT 30/13
http://forum.xda-developers.com/showthread.php?p=46066949
Click to expand...
Click to collapse
If you have not already installed a 4.3 ROM, then you are recommended (nay, required) to use CWM 6.0.3.7 to do the initial wipe and install, after that you can switch to TWRP for any flashing after that.There is something that 6.0.3.7 does to the data partition that TWRP doesn't, on the initial setup. Once that is done, it doesn't matter. Flash the JB radio when you flash the 4.3 ROM. And going back to GB if you need to is fairly simple, just follow Vincom's guide. There are lots of flashable zips of GB radios you can use.
I am still a bit confused regarding TWRP & CWM being installed at the same time or side by side. So, let me get this straight. If I want to install JB 4.3 ROM, I must first boot into ODIN, install CWM through ODIN, reboot, boot into CWM, wipe the system, reboot, boot back into ODIN, install TWRP, reboot, boot into TWRP, install the JB 4.3 ROM, and finally preform the last reboot. Is this correct & it won't break either of the custom recoveries? However rpr69 said "switch back to TWRP." Are you inferring TWRP & CWM can be installed side by side? If so, how do I access one over the other?
Regarding GB's radio files:
Which of the following links is the Radio/modem files? Is it the second one? I know of them is the official stock ROM and the other requires the OTA updates. However the poster didn't include the OTA updates yet...
ATT-UCLI3-odexed-cwm.zip http://d-h.st/rDZ
kernel-ucli3-sgh-i727-RD01-cwm.zip http://d-h.st/QfR
[ROM][ICS][UCLI3][09-NOV-2012] Stock odexed & deodexed UNTOUCHED
http://forum.xda-developers.com/showthread.php?t=1982467
Try this, wipe cache and dalvik.....no promises lol [Link is dead.]
https://dl.dropbox.com/u/60567424/modem-UCLI3.zip
http://forum.xda-developers.com/showpost.php?p=33344009&postcount=22
Sadly no link for UCLI3 [GB's Radio files.]
[ROM][ics][uclf5] •∞ EMBRYO •∞ 4.1 •∞ [08-jul-2012]
http://forum.xda-developers.com/showthread.php?t=1754473
The 1Stop post from Vincom:
http://forum.xda-developers.com/showthread.php?t=1785999
Sadly there are no more links for GB / UCLI3 radio files.
I know you posted but its confusing, let me simplify, I hope:
im assuming you have either cwm or twrp installed, if on stock read this.
you cannot have two recoveries installed at the sametime:
recovery install procedure:
if not on cwm6037 flash cwm6037 with what ever recovery you have now and reboot back into recovery.
then flash any custom jb4.3 rom, preferably latest cm10.2 nightly found here and reboot rom at least twice.
if you like cwm 6037 stay with it, I don't, or else just flash twrp 2.6.3.0 w/cwm 6037 and reboot back into recovery or rom.
now you can just stay w/the cm10.2 nightly you flashed with cwm 6037 or flash any other rom w/twrp 2.6.3.0 which is now your installed recovery.
that's it you should not have the reboot problems on any jb4.3 roms.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
above recovery install procedure is only if a jb4.3 rom on its 2nd reboot just has a black screen and wont boot into rom, but 2nd boot does usually take longer than normal upto a full minute.
if flashing a rom or restoring from nandroid(recovery backup) prior to jb4.3 and then later decide to flash a jb4.3 rom you need todo above recovery installation procedure b4 flashing a jb4.3 rom.
restoring backups only work with whatever recovery they were made with, you cannot restore a cwm backup w/twrp recovery and vice a versa.
newest versions of recoveries should restore backups made with their older versions.
why do u want an old radio, they will not work w/jb roms
old radios are linked in the 1stop sticky under "old stuff".
installing the radio has nothing todo with the recovery you are using.
flash jb radios for jb roms which happen to be all the current roms.
reread the radio section in the 1stop sticky.
I linked this post in the recovery section of the 1stop sticky
Thank you vincom for explaining the process of using both CWM 6.0.3.7 & TWRP 2.6.3.0 together. I am familiar with backups ONLY working with their original customer recovery. I didn't even think about older versions of backups (not) working with newer custom recoveries. Was there an issue working with older backups in the past?
The reason I need the old GB Radio/Modem files, because when I have to return the phone to stock & load up my old Gingerbeard nandroid, I will be able to return it back to AT&T with the original Radio files and the original Gingerbeard OS. Anywho, thank you for the GB radio. I really appreciate it!
lowao said:
Thank you vincom for explaining the process of using both CWM 6.0.3.7 & TWRP 2.6.3.0 together. I am familiar with backups ONLY working with their original customer recovery. I didn't even think about older versions of backups (not) working with newer custom recoveries. Was there an issue working with older backups in the past?
The reason I need the old GB Radio/Modem files, because when I have to return the phone to stock & load up my old Gingerbeard nandroid, I will be able to return it back to AT&T with the original Radio files and the original Gingerbeard OS. Anywho, thank you for the GB radio. I really appreciate it!
Click to expand...
Click to collapse
u can return any phone that has any stock firmware, with our phones that would be stock jb4.1.2 and using odin would be the way to do it , link in my sig. this is assuming your carrier used the latest firmware as with att and rogers.
I am with AT&T and I never got the official ICS or JB through updates. Actually, I thought ICS was discontinue, because it was bricking phones. Thus the stock ICS & JB Roms here were ported over?
lowao said:
I am with AT&T and I never got the official ICS or JB through updates. Actually, I thought ICS was discontinue, because it was bricking phones. Thus the stock ICS & JB Roms here were ported over?
Click to expand...
Click to collapse
these are untouched full official stock firmwares( radio, recovery, kernel and apps/bloatware), just use odin and flash whatever version you want, all info is in the restore to stock sticky
lowao said:
I am with AT&T and I never got the official ICS or JB through updates. Actually, I thought ICS was discontinue, because it was bricking phones. Thus the stock ICS & JB Roms here were ported over?
Click to expand...
Click to collapse
nope, both are fine and are still available officially. You don't need gingerbread to return it.
Sent from my HTC One using Tapatalk 4
I have to go to Samsung's website and download their Kies software to upgrade to Jelly Bean right? It won't be pushed out through Settings > About Phone > System Update then?
Or you can use Odin.
Sent from my HTC One using Tapatalk 4
So if you're flashing 4.3 ROMs just use cwm? Went from twrp to cwm and back to twrp and am getting the same black boot screen on a slim 4.3 weekly.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
beachmiles said:
So if you're flashing 4.3 ROMs just use cwm? Went from twrp to cwm and back to twrp and am getting the same black boot screen on a slim 4.3 weekly.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
To properly set everything up, you need to use the recommended CWM for 4.3, do a full factory wipe, and make sure that data is formatted. Then install the ROM and boot it up. Reboot to verify it works properly. Then you can go to TWRP 2.6.0.1 or later.
I've been using twrp since release and not had any issues why do we need cwm? What's the technical reasoning.
Sent from my XT1080 using Tapatalk
Didn't work
I followed this procedure exactly and it still didn't work.
I gave it ten minutes between boots and ended up having to pull the battery each of the three times I rebooted.
Fortunately I've gotten into the habit of making a backup before flashing, so it was just a loss of 45 minutes of my evening.
I was trying to get the latest CM10.2 Stable build. Has anyone gotten this thing to flash and work as well as 10.1.3 RC2 or 10.1.3 Final? This issue started for me with the second 10.2 Nightly.
...
Just NOW began seeing the replies to the main post. I don't have ANOTHER fresh install in me: I've already had to do that twice with the 2012 Nexus7 and once with the Skyrocket in the last six weeks.