I am using smoothest rom. The power off options for the rom just arent there any more. The tw power off options are there. Is it ok to reflash the rom?
If you're already rooted and currently on a custom ROM then yes you can wipe and flash another or even the same ROM or you can even do a ROM restore from settings. Obviously you will want to backup anything before you do anything but I would NOT make a nandroid backup at this point due to the issue you have. It will likely be found in your nandroid backup as well. I'd recommend a clean flash. Remember that ROMS that have some of the Note 3 features tend to have issues and that's why I personally prefer STS or the stock rooted MK4 ROMS from Slesh and LorJay's threads. No issues with either. Also you may want to flash a god compatible recovery such as Phil's recovery version 6.07.9. Since the Jellybean/MK$ upodate there has been compatibility issues with some custom recoveries so I thought you should look into that as well before flashing a new rom. Your issue seems to be unique.
Related
I have a AT&T samsung galaxy S3 rooted by using the samsung galaxy toolkit http://forum.xda-developers.com/showthread.php?t=1746665
I'm interested in flashing the following CM10 Nightly rom http://forum.xda-developers.com/showthread.php?t=1778270 to my phone but have a few questions before I proceed.
1) What precautions should I take before flashing a custom rom? I understand I first need to make a nandoid backup (which I have done) and verify that I have the correct rom for my specific phone model that I will be flashing to. If I were to choose the CM10 Nightly rom, the link from the post goes to http://get.cm/?device=d2att which appears to be correct for my AT&T Samsung Galaxy S3 SGH-1747.
2) Since I flashed with the samsung galaxy toolkit, it flashed the following recovery "CWM-Based Recovery v5.5.0.4 - Do I need to use a different recovery in order to use the CM10 Nightly roms or is this one compatible? If not, how do I go about changing to another recovery?
3) What is the steps for flashing properly? Would I need to update kernel or model or just simply download rom, save to SD card, boot to recovery, then flash the rom in zip form?
I appreciate any your responses in advance. I tend to over analyze and I feel i've read enough about the process of flashing custom roms but I want to be certain. Thank you!
It looks like you got all you ducks in a row, on behalf of the community thanks for being a smart user :good:.
1) You nailed it....make absolutely certain you are downloading the correct software for your device, flashing an incompatible ROM can leave you with a really sexy, expensive paper weight. The d2att identifier is unique to the AT&T variant of the SG3 (i747). Before you flash any new rom or kernel (or anything else for that matter in my opinion) make a nandroid or equivalent backup from your recovery. I do this even for the smallest mod, tweak, theme whatever if for nothing else incase i dont like it it an easy undo 'button'. Besides that i like to keep a fairly recent backup on something other than my phone.
2) For all intensive purposes that version of CWM will work, atleast currently. I would recommend you update it however as that version is several builds behind and there are sometimes updates in the more current ROM builds that may not play nice with older recoveries. The easiest way to do this is download Clockwork Rom Manager from the play store, on the main app screen at the very top is the option to install the latest recovery. It will download, preferably on wifi to minimize downloading errors as much as possible, and then install automatically. There is also atleast one other alternative recovery that i know of, TWRP, which is worth checking out in my opinion. Just keep in mind the backups from the different recoveries are NOT interchangeable.
3) It always best to follow any and all directions in the OP of whatever ROM you are installing as most differ. The generally accepted order for flashing goes something like this although everyone will have an opinion on this i'm sure. ROM > Gapps (if required by the rom) > Reboot > Kernel > Reboot. If you are really concerned you can always just flash one at a time allowing a full reboot in between each flash, personally i think this is overkill but thats just my opinion.
One last personal suggestion, I always keep a copy of my rom, kernel, and any required supporting software on my external sd just in case. It comes in handy if for some reason you try something that doesn't work out the way you had hoped and you are away from a computer and your phone is unable to boot into android. Some would argue that a nandroid makes this unnecessary but with 32 gigs in my current setup its not like im hurting for space. Hope this helps to clarify some things for you, good luck!
dntesinfrno, Thank you very much for your reply and kind words
A lot of the information has been posted on the boards but it can be a little confusing and too much information at once.
You mentioned that I can simply use Rom Manager then click "Flash ClockworkMod Recovery", are there any reports of there being problems in using rom manager to flash the recovery or is the S3 fully supported?
As for the kernel flashing.. I'm really only interested in flashing custom roms (CM10), is it necessary to flash the kernel as well when flashing custom roms? I didn't see anything on the other thread stating anything about flashing kernels so i'm guessing it's not needed?
I'm for sure going to take your recommendation and make a backup of current rom and kernel. Would you recommend Rom Manager to backup the current rom? I see an option that says "Backup current rom" in the application. How do you go about backing those up?
Thank you again! :fingers-crossed:
since I have the cwm-based recovery v5.5.0.4 i'm wondering if I were to use rom manager and flash the latest clockworkmod recovery, would it actually stick after the reboot?
found the following thread here and it looked almost identical to mine: http://forum.xda-developers.com/showthread.php?t=1801534&highlight=cwm-based+recovery
Ended up using rom manager to flash clockworkmod and after rebooting multiple times and booting into recovery, the official clockworkmod recovery is installed. (showing "ClockworkMod 6.0.1.2" now)
As for backing up kernel and everything else, will rom manager do that as well?
Thank you
Hey guys, just got my E4GT yesterday. I installed the rooted GB27 via the one click method. Then installed kernel/recovery through mobile Odin and the tar from here http://forum.xda-developers.com/showthread.php?p=40549220
I am coming the Nexus S 4G (got the epic via a warranty swap) and a Nexus 7, so things here are WAY more complicated. I have been reading like crazy to get a grasp of the flow of how to do things with this device, but I keep getting what seems like either conflicting information or gaps in knowledge.
So what I want to do is switch to an AOSP ROM like PAC or CM, as TW UX is so not jiving with my nexus sensibilities. So since I am currently on all JB partition images I am to understand that I need to switch to a ICS modem. Now this might be a seemingly stupid question, but is there a perfered version of it? I see quite a few ICS modem and don't know to choose and nothing seems to give advice in this regard (at least that I can find). My only guess would be the largest number would be final ICS modem and thus should be the most stable/best available. Thoughts?
Then recovery, I see that the recovery I have installed is for only TW jellybean Roms. So I would have to flash another kernel/recovery prior to flashing my aosp ROM of choice. The GB - EL26 seems to be recommend from many sources, and I want to avoid the whole emmc brick mess. So is that the preferred recovery to flash from? And just so I understand, once I flash a ROM it will then inject its own kernel/recovery images correct?
So every time I want to flash a new ROM, I would start with installing that gingerbread recovery, then reboot recovery into that recovery, full wipe (factory reset,wipe cache/dalvik cache), flash ROM+gapps, and reboot. What about nandroid? Since I am switching recoveries so often are nandroid good across different recoveries? Or not? I am used to being able to have a few backups handy to always be able to get back to a working ROM.
Anyway, thanks in advance for any advice you have to offer. I hated having to ask these questions, but better to ask than end up with a paperwieght.
Your reading has paid off, looks like you got it down. FL24 is the newest ICS modem. EL29 directboot kernel is pretty easy to use, only problem is that it can't flash modems. But you can do that after you get AOSP booted up.
Nandroids are only good on the recovery that they are made on, but all the AOSP ROMs use the same recovery. If you use garwynn's v0.4.1 GB27 kernel it uses that same recovery as well, that's how I go about it. You'll catch on quick don't worry.
Search for Mobile Odin it will save you a lot of time.
bilgerryan said:
Your reading has paid off, looks like you got it down. FL24 is the newest ICS modem. EL29 directboot kernel is pretty easy to use, only problem is that it can't flash modems. But you can do that after you get AOSP booted up.
Nandroids are only good on the recovery that they are made on, but all the AOSP ROMs use the same recovery. If you use garwynn's v0.4.1 GB27 kernel it uses that same recovery as well, that's how I go about it. You'll catch on quick don't worry.
Search for Mobile Odin it will save you a lot of time.
Click to expand...
Click to collapse
I got it working, and am running rootbox. Being back on aosp feels like home, I hate TW!!
Sent from my Nexus 7 using Tapatalk 2
hlxanthus said:
I got it working, and am running rootbox. Being back on aosp feels like home, I hate TW!!
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I like things about both, mostly just the music on TW. But yeah, I usually stick with AOSP. I've got 8 AOSP ROMs in the Android Development section when you get around to it. Welcome to the madhouse btw.
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
So my E980 will not turn wifi on with a custom ROM. I have tried probably 10 different roms and many different android version numbers with no change. The switch is greyed out and will not turn on at all. I have the following installed:
CM12-20150625-Snapshot-YNG4NAO09M
WildKernel
I believe Mack's modem
Gapps
Nothing will fix this. I have read where other people have installed stock Kernels to fix their issues but will doing that cause a problem because I am on android version 5.x+? Everything seems to work ok on the phone other than wifi and I really need that.
Have you tried to flash CM over full stock 4.1 without custom modem? All CM based roms recommended install is: flash stock 4.1 kdz through Lg Flash Tool 2014 cse flash, then root, then freegee + cwm, then CM. And only if something is wrong then patches.
Yeah that's how I have been doing it actually. I only started doing there kernels and stuff yesterday morning. I did find that blisspop v3.6 actually had working WiFi on my phone but it had other weird issues. It would randomly reboot and then go into reinstalling the ROM and it would also randomly shut my cellular data connection off by itself. Like I could watch it turn the switch off and on ine settings app. Those coupled with really bad battery life made me flash back to stock 4.1.2.
Then after flashing back to stock I went on and did the ota update to 4.4.2 but that caused issues with the screen not coming back on after making a phone call without doing a power cycle. I would love to run a custom ROM but none I have found are stable and only one has most all the stock features working in it.
Did you use recommended recovery version? Try upgrading from stock 4.1 directly to BlissPop using latest Philz Touch or TWRP 2.8.6.0 modified? Personally i prefer this recovery: https://www.androidfilehost.com/?fid=95916177934554356 for my E988. It can flash and backup modem and EFS.
xermit said:
Did you use recommended recovery version? Try upgrading from stock 4.1 directly to BlissPop using latest Philz Touch or TWRP 2.8.6.0 modified? Personally i prefer this recovery: https://www.androidfilehost.com/?fid=95916177934554356 for my E988. It can flash and backup modem and EFS.
Click to expand...
Click to collapse
The recovery part has always confused me. Thus far I have been downloading FreeGee Free off the playstore and using it to install CWM. I tried TWRP once but the interface wouldn't work right on my device. Some of the onscreen buttons would do different things than their label said (like Reboot would take me to a different screen, not Reboot) and the slider bar at the bottom wouldn't work.
How do you install the recovery using that Zip file? And could that be causing me problems?
Noggles10 said:
How do you install the recovery using that Zip file? And could that be causing me problems?
Click to expand...
Click to collapse
I'm installing it from recovery just like another zips (ROMs etc)
Problems? Theoretically, yes, if you flash recovery that isn't compatible with your device
I'm already on the stock KK ROM (E98020g)., but with the CWM recovery. I just want to wipe everything while keeping the stock ROM, but I've seen that factory resetting or flashing stock ROMs while on a custom recovery will probably cause a some sort of brick...
I've already briefly seen the pinned stock ROM tutorial already. Before I try that (assuming it still works), can anyone tell me if there's a simpler way? It's going to take me a long time to go through that entire thread so it would be an immense help if someone could just tell me.
Have you try using system setting, storage, hard reset?
hawkwind212 said:
Have you try using system setting, storage, hard reset?
Click to expand...
Click to collapse
That's what I meant by "factory reset", sorry. Everything I've read indicates that this will cause a softbrick, which I'm trying to avoid. Is this info wrong?
I assume the reason that you install cwm and running the stock ROM is so you can have a nandroid backup? Otherwise Why else would you installed a custom recovery? So backup the ROM and do the factory reset with kk instead of cwm, which may be the reason that some people are getting the soft bricks. I can't guarantee you that everything will be according to the plan, but that's the reason backup function is there.
I originally installed CWM because I wanted to wipe and try out a custom ROM (probably CM). But then I noticed all the serious issues people were having with various custom ROMs, so I decided to skip the custom rom (for now) and just get on with wiping. I really don't want to risk any type of brick with this device.
Anyway, I think I'm going to try out the pinned stock rom thread I mentioned in the OP.