I have a question and I cant seem to figure out the answer. Im sure this is a no brainer but Im still not sure on the answer. So i have my phone rooted and been using mostly slimbean or liquidsmooth roms, but I have been looking into roms that are based on samsungs touchwiz or whatever there called.
I know theat Slim and liquid is based on AOSP roms (if thats the correct term) but I want to try different ones too, im happy with what I have running as my daily, but i also like to try to change things up, once in a while.
My question is, can I go from an aosp rom to the ones based on the Touchwiz and vise versa? ill go through the usual steps, wipe/reset data, cache and delvik, format system and then install rom and gapps. Is that all thats needed? Does it really matter what rom it is as long as its for the d2att (im on canadian virgin mobile s3) as long as I follow the usual installation steps?
Thanks
does not matter. just go about your regular steps. i do it all the time.
brjig said:
My question is, can I go from an aosp rom to the ones based on the Touchwiz and vise versa? ill go through the usual steps, wipe/reset data, cache and delvik, format system and then install rom and gapps. Is that all thats needed? Does it really matter what rom it is as long as its for the d2att (im on canadian virgin mobile s3) as long as I follow the usual installation steps?
Thanks
Click to expand...
Click to collapse
As long as you wipe all that you have mentioned you should be good. Just so you know...do not flash gapps on Touchwiz roms unless the dev specifically says to do so. They are normally already included. AOSP are the ones you need Gapps with normally. Heads up regarding internal storage as well. If you are on a 4.2.2 AOSP rom and go to a 4.1.x rom, your internal storage will mostly be moved to a folder "0". This is a known issue so don't panic. Everything is in that folder.
Related
I have been looking in Q&A and all other subforums but I cant find a straight answer or a sticky.
What is the procedure for going from TWizz to AOSP and vise versa? Isn't there an internal SDCard issue going back to TW from AOSP? Can I not just do an Nandroid from TWRP back to my TWizz ROM?
spotopolis said:
I have been looking in Q&A and all other subforums but I cant find a straight answer or a sticky.
What is the procedure for going from TWizz to AOSP and vise versa? Isn't there an internal SDCard issue going back to TW from AOSP? Can I not just do an Nandroid from TWRP back to my TWizz ROM?
Click to expand...
Click to collapse
Thats what I did. The only problem I had with aosp was the internal sd, but I went back to touchwiz via nandroid and everything seems to be working fine. I only tried aisp for about a day and then went back. Hopefully I helped.
Somewhere, in some thread (at work, can't find it for you ATM) there is a flashable zip to fix the internal partitioning (?) issue going from 4.1 to 4.2... Hold on....
http://forum.xda-developers.com/showthread.php?p=37008568
Sent from my calculator watch.
Also, is CWM required for some reason? Can I still just use TWRP? Or is there some scripting issues or something? All the AOSP threads say use/flash CWM. Maybe they are just saying CWM as in a generic term for recovery?
spotopolis said:
Also, is CWM required for some reason? Can I still just use TWRP? Or is there some scripting issues or something? All the AOSP threads say use/flash CWM. Maybe they are just saying CWM as in a generic term for recovery?
Click to expand...
Click to collapse
honestly don't know, have not played with AOSP/CM on my note2 yet.
It was just random that I read the thread OP (i usually do for everything), retained that bit of info. Let me/us know what ya find out.
Sent from my calculator watch.
Installed AOSP Carbon. Let all my apps restore from Google. Right from the get go I could tell it was really fast, But I'm already going back to my TW ROM. I just couldn't be away from all of Sammy's add-ons.
I used the latest TWRP and flashed the AOSP + GApps with no problems. It booted fine. Played with it for a bit. Like I said let all my apps download again and played with some of the AOSP settings and ran a few benchmarks.
Process I used to go back to TW ROM.
Rebooted to TWRP
Wiped Cache/Delvik
Factory Reset
Wiped System
Formatted Data
Rebooted Recovery
Restored TWizz Backup
Flashed restore-sdcard-after-downgrade.zip
Wiped Cache/Delvik
Copied my internal SD backup back to internal SDCard
Reboot System
My restore had no issues and I am now back up and running just like I was before the AOSP ROM.
Hello friends,
I'm a happy touchwiz user running DN3 v3 with mj5 bootloader (knox free). All is well.
But i want to try new AOSP 4.4 builds like PARANOIDANDROID, PAC, omni etc. Is it possible to do that like from latest knox free bootloader and tw4.3 TO aosp?
Has anybody tried this? please suggest what procedure should i follow.
thanks
mani16985 said:
Hello friends,
I'm a happy touchwiz user running DN3 v3 with mj5 bootloader (knox free). All is well.
But i want to try new AOSP 4.4 builds like PARANOIDANDROID, PAC, omni etc. Is it possible to do that like from latest knox free bootloader and tw4.3 TO aosp?
Has anybody tried this? please suggest what procedure should i follow.
thanks
Click to expand...
Click to collapse
Hey,
You will love AOSP! I have tried CM11 and OMNI, and both were smooth and stable. You will have a much faster phone but you will use all the Samsung apps, including the S-Pen tricks. Your S-pen will still work though.
My advice? Well:
1. Make a Nandroid Backup (using your custom recovery). You might wanna get back to your current ROM if anything goes south or you just don't like AOSP.
2. Update your custom recovery. Actually I would suggest you do this even if you don't flash any AOSP 4.4 ROMs. I recommend TWRP 2.6.3.x.
3. Make a full wipe before installing anything. Full wipe means everything but your SD cards (internal and external). Though, I would recommend to also wipe your internal SD card, after you back up your stuff (watch out not to lose your nandroid backups that might be on your internal SD).
4. Flash the ROM you choose and be very careful to read the flashing instructions. You'll feel like an a$$hole if you ask for help on the ROMs thread and find out that you missed some step because you didn't read the OP carefully.
5. Usually you'll have to flash other fixes/addons for everything to work. Look for them in the OP, if it's needed or recommended, it will be listed there.
I hope that helps! Come back if you have trouble.
flash AOSP
Just flash as usual but remember you need to read the instruction carefully for each aosp rom forum.
1. you need to use cwm 6.0.3.7 version onward or TWRP 2.6.1.0 ( can search through xda forum)
2. Do full wipe including System, Data, Cache, Dalvik, Android Secure, and Preload.
3. Flash the aosp rom you prefer
4. Flash the gapps
5. reboots (It might take some time for first time)
Ok thanks guys, I'll try it today.
Sent from my BE(a)ST.. Samsung Galaxy Note2
So I have decided to finally root my Galaxy S III, and I haven't installed a custom ROM since my Galaxy S days a few years back, so I am a little iffy on certain things. I was successfully able to root it and everything, I just have a quick question about backing up. When installing a custom ROM and wiping everything, I will lose everything on my phone currently correct? This includes music, photos, etc? I have backed up my phone using Titanium Backup Pro, but I am assuming since that is just for data and apps, that won't include my music and photos on my internal storage, correct? So, will I need to manually back those up? Thank you for help. Also any suggestions ROM's would be helpful; I was thinking of flashing Masterpiece V7 since that is based off of Cyanogen 11 with KitKat 4.4.4. Thanks once again!
Internal sdcard wont be wiped unless you factory reset while stock recovery is installed. Still, you should always have a backup of ALL your important data. Things can always go wrong. You are never guaranteed anything.
Ah, so my internal storage won't be wiped when I perform a factory data/reset using CWM Recovery? That's mandatory since this will be my first ROM install, correct?
BigWorldJust said:
Ah, so my internal storage won't be wiped when I perform a factory data/reset using CWM Recovery? That's mandatory since this will be my first ROM install, correct?
Click to expand...
Click to collapse
Yeah it won't wipe your internal SD and yup, its mandatory!
Thanks for all of the help! What exactly is erased when performing those functions?
Everything on the /data partition except internal sd.
Ah, alright. Are there any specific ROM's you guys recommend? I am trying to have the most stable version of 4.4.4, essentially.
BigWorldJust said:
Ah, alright. Are there any specific ROM's you guys recommend? I am trying to have the most stable version of 4.4.4, essentially.
Click to expand...
Click to collapse
We cannot "recommend" any specific ROMS here since everybody's needs and usability requirements are different and we don't want to take away from other developers who have worked hard on their ROMS. I can however suggest not to go with 4.4.4 because it can make rooting and modding more difficult and it adds absolutely nothing to the 4.4.2 usability. It just adds some security features. If you like stock and TW, go with a stock based ROM. if you don't like all that bloatware and want a more "pure android" experience, go with a AOSP based ROM. But I would suggest just trying a few out until you find one that you like.
Ah, so my internal storage won't be wiped when I perform a factory data/reset using CWM Recovery? That's mandatory since this will be my first ROM install, correct?
Click to expand...
Click to collapse
From my experience, you don't have to do a factory reset if you are going from a TW based ROM to TW or AOSP to AOSP of the same or new version of android (4.3 -> 4.3 or 4.2 -> 4.3), although it is generally recommended. But you do have to factory reset when switching between AOSP, AOKP and TW or downgrading versions.
As far as I know, not near enough Galaxy s3 owners are taking advantage of this amazing utility. It allows you to install multiple ROMs on your device without having to wipe the one you already have. I currently have 5 ROMs on my phone ranging from touchwiz to Cyanogenmod, Lollipop to Jelly Bean. It's very versatile and guess what!
It was recently updated to work with Lollipop ROMs! You can install any ROM you want as a secondary ROM and test to see if it works as a daily driver! No more getting scared about a brick or bootloop because a simple REBOOT switches you to your primary ROM!!
I constantly switch between CM ROMs for fluidity, Lollipop ROMs for cutting edge features, and TouchWiz ROMs to unleash the full potential of the camera, as well as get all those TouchWiz features like WiFi calling! You can flash any ROM, test experimental builds and flash any kind of ROM you want all without wiping the ones you already have! Unlimited ROMs!(space permitting)
Now, it may not be as simple as ROM manager for Nexus devices but it's pretty darn easy. here's the steps:
Flash MultiBoot Recovery(based on twrp 2.8.3.0)
Go to Advanced>
MultiBoot>
Create ROM>
Set ROM(to what you created)>
"Flash the ROM and gapps just like any other">
Set ROM>
Boot ROM(Click on one you just created)>
A menu will pop up saying Boot ROM!
There. You are done. I can boot into recovery and boot a ROM in a matter of seconds. Slimkat, SlimLP, CM11, CM12, TouchWiz 4.1.2, 4.3, 4.4.2, PAC ROM, any of them!
I just want more people to take advantage of this wonderful feat of developer genius!!! I feel like only have of the phones potential is had without this amazing recovery. Now that it is updated to allow Lollipop ROMs, it is too hard to keep it in.
Head over to development, it should be on the first page and try it! Alternately search for "Multiboot" and look for the thread.
All credits go to @Phil_Suz for being an amazing god.
but my question to you is, do you have to wipe out the current rom? and then do the process? or can you keep the current ROM? if so that would be awesome.
ALso another question.. if I am on 4.4.2 TW, can i still install lollipop as a multiboot rom with out having to wipe out my current rom (TW 4.4.2 Likewise S5)?
YPG70 said:
but my question to you is, do you have to wipe out the current rom? and then do the process? or can you keep the current ROM? if so that would be awesome.
ALso another question.. if I am on 4.4.2 TW, can i still install lollipop as a multiboot rom with out having to wipe out my current rom (TW 4.4.2 Likewise S5)?
Click to expand...
Click to collapse
You don't have to wipe your main ROM at all! It is just a recovery, and each secondary ROM is like a whole different device on your sdcard, you just have to switch to it it's amazing let me tell you. Your primary ROM, kernel, modem etc will not be affected at all until you decide to change it, which you just do like any other ROM (just be careful formatting because that will delete the multiboot folder on root of phone). If you flash another ROM and it doesn't boot, just reboot the phone to your main ROM and or go to recovery and try again you can create and delete ROM's as much as you please and even set up how much space you want to make the different parts of the ROM take on your sdcard (data, system, cache). Flash the multi boot recovery, read how to use it and you're golden there's also a video someone made of how to use it. If you don't like multiboot just flash another recovery and reboot the recovery. You won't lose anything unless you created an additional ROM or ROMs.
Can you give me instructions on how to do this properly? The video is a bit confusing. I understand how to create a new rom. I am just a bit lost, on how to switch to my current ROM, or set it up.
This is true its useful... for those who could figure out what to do at right times.
not only that but other carriers have it baked into the kernels for simply a reboot option.
we have more complicated version yet out phones are not bootlocked. if more people got tmobile phones I am sure they would have worked these issues out by now.
I certainly have taken advantage of this. Alternate between your favorite roms with ease.
reminds me of safestrap, which i used on my droid4, and appears to be available for some flavors of the SGS4 and some galaxy Notes. it also uses twrp. think of it as creating partitions on your PC - you make a partition for each Rom - they were called ROM Slots in safestrap - make a given slot active, then flash the rom and whatever else you want as you normaly would right there in twrp. if something breaks or you find a showstopper bug or just need to switch roms, simply reboot into recovery, change which rom is "active" and then exit - it loads the rom you just selected. it was great on my droid4 since gps and camera were both kinda buggy in almost any custom rom, and i was nervous not having it on my galaxy relay, but it worked out. it'll be nice to have on the sgs3, especially since I want to try out some L roms.
here's the thread for the multiboot recovery, so nobody else has to search for it:
http://forum.xda-developers.com/showthread.php?t=2646528
At a bit of a loss here. I have here a d2att/I747 that was working up until today on PAC-Rom, then I decided to wipe it clean and install a Touchwiz ROM. I tried S3RX, I tried a supposed Note V port, hell, I'm trying stock. None of them will finish booting. S3RX and the Note V port give me a perpetual boot logo, stock gets past the Samsung logo, plays the sound, then gets stuck at the AT&T logo. I've given each one at least an hour to do something, and they're apparently not going anywhere.
I've tried everything I know how to do; I've wiped EVERYTHING (system, data, internal storage, formatted data, the whole shebang) and nothing seems to make a difference. It's on NJ2 and I even just tried reflashing the NJ2 bootloader/modem, but that doesn't seem to have done anything either. Totally at a loss here. What could be causing this? I mean, it boots into download/recovery fine and always -starts- booting the roms, but never finishes. Could I have a corrupted partition or something?
EDIT: Oh, so I put PAC back on it and it boots again. So yeah, this seems specific to TW roms. I don't get it.
which recovery/version do you have ?
are the touchwiz roms the same android version as the pac-rom version ?
checked the touchwiz md5 to make sure has not been bad downloads ? (i know , far-fetched for them all to be bad DLs. just a thought).
"err on the side of kindness"
First off when you went from CM/AOSP based ROM to TW did you wipe everything but external storage? When going from CM/AOSP to TW & vice versa you MUST wipe internal storage. If you do this & it still fails to boot you'll need to flash the stock recovery wipe with it & install stock. Then Odin TWRP & you're good to go.
You can get the stock recovery from enewman17's NE4 thread.
Just be sure to do your research. d2att is the easiest of all d2's to hard brick thanks to At&t not releasing full firmwares.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Flashable AT&T Galaxy S3 NJ2 Stock Recovery Zip (Pulled last fall) Google Drive Links
https://drive.google.com/file/d/0B0lfMZeSyJnYT2xFbUxKVUR0RGM/view?usp=drivesdk
Chuckles5150 said:
Flashable AT&T Galaxy S3 NJ2 Stock Recovery Zip (Pulled last fall) Google Drive Links
https://drive.google.com/file/d/0B0lfMZeSyJnYT2xFbUxKVUR0RGM/view?usp=drivesdk
Click to expand...
Click to collapse
Nice!
? d2att Oct-M KrAkEn Kernel ?
Jaitsu said:
At a bit of a loss here. I have here a d2att/I747 that was working up until today on PAC-Rom, then I decided to wipe it clean and install a Touchwiz ROM. I tried S3RX, I tried a supposed Note V port, hell, I'm trying stock. None of them will finish booting. S3RX and the Note V port give me a perpetual boot logo, stock gets past the Samsung logo, plays the sound, then gets stuck at the AT&T logo. I've given each one at least an hour to do something, and they're apparently not going anywhere.
I've tried everything I know how to do; I've wiped EVERYTHING (system, data, internal storage, formatted data, the whole shebang) and nothing seems to make a difference. It's on NJ2 and I even just tried reflashing the NJ2 bootloader/modem, but that doesn't seem to have done anything either. Totally at a loss here. What could be causing this? I mean, it boots into download/recovery fine and always -starts- booting the roms, but never finishes. Could I have a corrupted partition or something?
EDIT: Oh, so I put PAC back on it and it boots again. So yeah, this seems specific to TW roms. I don't get it.
Click to expand...
Click to collapse
Flash slimkat ROM and then flash TW ROM. It will work I had same problem
Oh wow, I didn't mean to abandon this thread. I haven't been getting email notifications 'til today for some reason. Anyway, yeah, I've wiped *everything* including internal storage; I'm flashing from an external SD. Nada. I was really hoping there was some NJ2 Odin-able package I could use that'd guarantee I wasn't screwing anything up, but oh well. Anyhow, I don't have the device on hand anymore (doing this for a family member), but perhaps I'll get it back and try that slimkat idea...? To answer mrrocketdog's question, no, actually. PAC is 5.1, every TW ROM I've found is 4.4. Shouldn't matter if I'm wiping every partition I can first, though, no?
Jaitsu said:
Oh wow, I didn't mean to abandon this thread. I haven't been getting email notifications 'til today for some reason. Anyway, yeah, I've wiped *everything* including internal storage; I'm flashing from an external SD. Nada. I was really hoping there was some NJ2 Odin-able package I could use that'd guarantee I wasn't screwing anything up, but oh well. Anyhow, I don't have the device on hand anymore (doing this for a family member), but perhaps I'll get it back and try that slimkat idea...? To answer mrrocketdog's question, no, actually. PAC is 5.1, every TW ROM I've found is 4.4. Shouldn't matter if I'm wiping every partition I can first, though, no?
Click to expand...
Click to collapse
Definitely try flashing the slimkat ROM. I had the same prob as you and read someone's reply about it. It fixed the issue for the touchwiz ROMs. After flashing slimkat go back to a touhwiz ROM. Do this before messing with the phone. I have a slimkat ROM on my SD card ready to be flashed at any moment for whenever I want to go back to touchwiz haha
Sent from my SAMSUNG-SGH-I747 using XDA-Developers mobile app
BakedOnSomeSour said:
Definitely try flashing the slimkat ROM. I had the same prob as you and read someone's reply about it. It fixed the issue for the touchwiz ROMs. After flashing slimkat go back to a touhwiz ROM. Do this before messing with the phone. I have a slimkat ROM on my SD card ready to be flashed at any moment for whenever I want to go back to touchwiz haha
Sent from my SAMSUNG-SGH-I747 using XDA-Developers mobile app
Click to expand...
Click to collapse
So do I have to flash Slimkat and then dirty flash TW? Seems like that'd have to be the case, otherwise anything it adds would get wiped away, unless it messes with partitions or something... I need to read up on this ****. That's weird.