[Q] Question coming from cyanogen 10 - T-Mobile, Samsung Galaxy SIII

I noticed that some people in other threads were having a problem flashing a jelly bean rom while coming from cyanogen, and some said that its because cyanogen uses a different kernel. Right now I am on cyan and if I look to flash a different jelly bean rom what would be the proper procedure? Plus I have a nandroid backup of both frosty jelly, as well as the official jelly bean, would it be possible to do a full restore of one of these and then flash a different rom?
Just checking before I do anything, I dont want to be another "think I bricked my phone".
On a seperate note cyanogen is awesome, Im just trying to find the right the fit.
Thanks.

Related

[Q] Clarification of Using Roms and version updates

I have a few questions about flashing ROMS on my E4GT.
I've read a little about the different ROMS and I'm not sure which one to choose. I think Codename ICS is the right one for me but I need help with that. What I'm looking for:
Faster and more stable
Customization such as battery percent instead of the battery
Working WiFi and 4G
"Bloatware" doesn't really matter to me...can any of the apps be installed if I decide I want them?
Will I need to flash a new ROM when there's a Jelly Bean update or will there be an upgrade option?
Number 1 can not be accurately be answered.
Number 2 is in Samsung's stock ICS as well as CyanogenMod9 and I would assume AOKP. Many custom gingerbread roms had it.
Number 3.... usually not an issue
Number 4 custom roms, aosp roms all usually very stripped. If your not on AOSP then most touchwiz stuff can be put back on a custom touchwiz rom. Some include a removed apps folder.
Flashing a rom, broad term. All updates are "rom flashes" minor updates will replace some files major updates can do a whole lot more including pushing new bootloaders.
Jelly Bean update? I laugh very hard and then return to the ways you will get jelly bean. Flash a ported rom of Jelly Bean, CM10 when it comes out, AOKP when it goes Jelly Bean. Maybe someone will waste the time to port a GS3 jelly bean rom?
From what I can tell, there are no "official" CyanogenMod ROMs that work well on the E4GT. CM7 has issues with 4G. I can't remember where I read that. I believe it was a fairly recent post.
To clarify my question about upgrading, are there ways of simply upgrading from GB to ICS the way we do with the OTAs from the carriers? Could one just upgrade from CM7 to CM9 to CM10 without flashing it fresh?

flashing from rom tool box with vicious jelly been rom

I'm runnung vicious jelly bean rom on my verizon Gnex, love it, but I'd like to make a few changes of my own, such as font, batt circle, etc. I have tryed using rom tool box and that didn't work. Can it be done, how. If not why? I'm new to rooting and flashing and using roms and i'd like to learn all i can. Somebody help me please.

[Q] now this MAY sound stupid but...

so im on stock ICS. not rooted.
and i want android jelly bean.
now all i've seen is that you have to get CM10 to do it. but i don't like to use "non stock roms", so is there anyway I can still get jelly bean without using CM?
and if not CM, then i really dont wanna use other ROMs either.
so in other words, is there a way to get jelly bean on sprint s3 using the "official" look of the jelly bean OS (and not other ROMs' looks)?
thanks! (and yes ill root and do all that too)
Closest thing to stock jelly bean.
http://forum.xda-developers.com/sho...T999UVDLI3 Leak Port) - 09/08/2012 (NEW BASE)
Right in the development section.... But read about the rom before flashing it. Make sure it's something you want on your phone.
Sent from Pluto.
Speedin07si said:
Closest thing to stock jelly bean.
http://forum.xda-developers.com/sho...T999UVDLI3 Leak Port) - 09/08/2012 (NEW BASE)
Right in the development section.... But read about the rom before flashing it. Make sure it's something you want on your phone.
Sent from Pluto.
Click to expand...
Click to collapse
so if i don't want to risk somethign crazy, the closest, most stable, and sexiest way is to use CM10 correct?
i just wanted touchwiz jelly bean stock
thegame2388 said:
so im on stock ICS. not rooted.
and i want android jelly bean.
now all i've seen is that you have to get CM10 to do it. but i don't like to use "non stock roms", so is there anyway I can still get jelly bean without using CM?
and if not CM, then i really dont wanna use other ROMs either.
so in other words, is there a way to get jelly bean on sprint s3 using the "official" look of the jelly bean OS (and not other ROMs' looks)?
thanks! (and yes ill root and do all that too)
Click to expand...
Click to collapse
Not yet, but there's someone saying they have some leaked update.zips. These will be leaked builds so when it goes official you'll either need to go custom or Odin back to stock. Either way it's the equivalent of a factory reset. It will also probably have annoying bugs. If you want a strong, stable build you'll just have to be patient. If this guy posts the update zips, feel free to give a go, but know you might as well be custom because stock recovery will probably reject the official OTA when it drops.
---------- Post added at 10:01 PM ---------- Previous post was at 09:59 PM ----------
thegame2388 said:
so if i don't want to risk somethign crazy, the closest, most stable, and sexiest way is to use CM10 correct?
i just wanted touchwiz jelly bean stock
Click to expand...
Click to collapse
Does he not want clockwork recovery or cyanogenmod? Now I'm not sure which... Nevermind, reread.
so i guess CM10 is the safest bet.
now another question:
since jelly bean (stock) is going to be coming out from sprint update sometime in october, what will I have to do? do a factory install, install stock ICS? and then manually update to jelly bean?
thegame2388 said:
so i guess CM10 is the safest bet.
now another question:
since jelly bean (stock) is going to be coming out from sprint update sometime in october, what will I have to do? do a factory install, install stock ICS? and then manually update to jelly bean?
Click to expand...
Click to collapse
Just to help assuage your fears, the creator of Cyanogen is like head developer for Samsung or something now. It's as safe as a stock build. I personally don't love CM roms and people seem to love aokp just as much. It's all personal preference. Just follow the rules of switching between because it can be a rocky ride. When in doubt Odin back to stop and rework from there. There is a lot of fun in it. Stock is stock, it's also made by developers who may or may not be as qualified or passionate as anyone on here. All up to you though.
I would just be patient and wait a month or 2 for the real official jb update Thayer sprint will send to your phone
ReapersDeath said:
I would just be patient and wait a month or 2 for the real official jb update Thayer sprint will send to your phone
Click to expand...
Click to collapse
1) so i got CM10 on this, so obvi thatst jellybean and it looks pretty sexy. except SOMETIMES, the screen will random flicker or glitch up for a microsecond. whats up with that?
2) when i open up the hotmail app, it only shows the text and now the attachment or any of the interactive stuff that was possible in ICS
3) i cant change the input method to something else!!!
thegame2388 said:
1) so i got CM10 on this, so obvi thatst jellybean and it looks pretty sexy. except SOMETIMES, the screen will random flicker or glitch up for a microsecond. whats up with that?
2) when i open up the hotmail app, it only shows the text and now the attachment or any of the interactive stuff that was possible in ICS
3) i cant change the input method to something else!!!
Click to expand...
Click to collapse
1) flash ktoonez kernel. Check HW overlay in developer settings.
2)Don't know the issue your referring to.
3)download another keyboard if you need to because this only comes with one keyboard so you can't change the input method until you download another one
thanks a lot man!
new issues:
1) the battery is GOD awful! i lasted like 6-7 hours with about 1.5hrs screen time. i was used to 30hrs+ using stock ICS. is there a battery fix for this?
2) should i use SetCPU or will this make matters worse? juice defender is already pretty awesome
3) i fixed the swype thing
bump

Will rooting be any different on the HOX with official JB Update ?

Hey Fellaz,
another noob, another question:
I'm kinda getting into the process to root my device and install a custom ROM, which in my case will be Slim Bean.
But first I want to wait for the official JB Update via OTA and after that i want to root my phone and install the custom ROM.
My Question won't be how to do it, don't worry.
Here it goes:
When i receive the update, will the rooting process be any different from when you do it on ICS ? I mean there are lots of guides on the internet, how to flash fastboot and CWM and so on.
There are links to fastboot, to the htc drivers, to the CWM, the files you need to do that. My Question is, will those be outdated when you have JB or does all stay the same ?
The same for Slim Bean, will the flashing process stay the same if I have official JB or will the files change which i need to use (hboot and stuff) ? I just coudn't find information if all the necessary files only run if you go from ICS>JB.
In my case i will be going from official JB>custom JB rom.
Jesus my english sucks when i'm excited, sorry !
Thanks in advance and have a nice day !
Nope....nothing changed. All in the same way
thanks for the reply !
And what will be about the hboot, if I get the official JB update, will there still be a need to chance hboot in order to flash Slim Bean ?
Don't think so, slim bean is a JB rom ? And after the update you will be on a JB hboot ...well that's clear as glass i think
alright thanks, yes Slim Bean is an AOSP based JB rom
As I saw in the JB Thread there will be a problem and in the second post of the JB discussion thread, it says that out there is only 1 rom which supports the hboot version coming with the JB Update.
So what's the truth now ? Can't anyone make a clear statement ?

Running AOSP kernels

Hi guys,
I'm running stock 4.1.2 Jelly Bean on my d2tmo Galaxy S3. When I look up kernels and whatnot, they are labelled many different ways. Some have JB in the name, some with AOSP in the name. I'm wondering: what types of kernels can I flash if I'm running a rooted stock ROM? I don't want to flash any custom ROMs because I'm a musichead and I like the stock music player
Thank you!
First of all you can get then stock music player with a custom rom
Second you can only run aosp kernels with an aosp rom. Aosp stands for android open source project. Aosp is not stock.
You can only use kernels labeled stock or touchwiz if you are using stock based rom
Sent from my SGH-T999 using Tapatalk 2
3rd of all, what in the heck do you want? Haha, you say you are running a 4.1.2 rom (only aosp available on TMO) so AOSP... but you want a kernel for stock (4.1.1) touchwiz rom? The stock music apk is great and works on all stock touchwiz based roms, and in my resource guide I have a huge list of what is available and what is what, if the kernel says 4.1.1 TouchWiz then it is for 4.1.1 TouchWiz. if it says 4.2 AOSP it is for 4.2 AOSP, if it says 4.1 AOSP then it is for 4.1 AOSP... Look in my resource bible in my signature, or in the dev sections for [kernel].
See, that's where I get confused. Sorry for the noob questions. I've been looking around but can't find clear, precise answers.
I'm running the stock TouchWiz, out of the box, 4.1.1 Jelly Bean (updated while not rooted to 4.1.2). That stock ROM is not the same as an AOSP ROM or an AOKP ROM, is it? I have another Android device that runs CM10.1 so I know a bit here and a bit there about ROMs and whatnot, but I'm not so confident when it comes to my S3.
Simply put, I want to keep that stock ROM, but get a custom kernel, because the stock kernel SUCKS. I need to know what kernels I can flash, and clninja already said I can only flash kernels labelled stock or TW. Am I correct, so far?
Thank you!
Well here's a Kernel that is supposed to be supported for STOCK rooted : http://forum.xda-developers.com/showthread.php?t=1785466 :highfive: But seriously you should get a custom ROM, the performance improvement is incredible and power management too ! :laugh:
There is a 4.1.2 stock ota ROM?!? I suck lol.
Sent from my SGH-T999 using xda premium
kruse1944 said:
Well here's a Kernel that is supposed to be supported for STOCK rooted : http://forum.xda-developers.com/showthread.php?t=1785466 :highfive: But seriously you should get a custom ROM, the performance improvement is incredible and power management too ! :laugh:
Click to expand...
Click to collapse
That ROM is labelled Jelly Bean in the title but underneath that it says it's only compatible with ICS. Question mark.
Question: when you're running a custom ROM, if there's an update for it, say from 1.0.0 to 1.0.1, you can just flash the update right over and not worry about problems right? Or do you need to factory reset through recovery and wipe the caches all over again?
seokhun said:
That ROM is labelled Jelly Bean in the title but underneath that it says it's only compatible with ICS. Question mark.
Question: when you're running a custom ROM, if there's an update for it, say from 1.0.0 to 1.0.1, you can just flash the update right over and not worry about problems right? Or do you need to factory reset through recovery and wipe the caches all over again?
Click to expand...
Click to collapse
There are a couple of touchwiz kernal's around, Ktoonsez is one that I would recommend, http://forum.xda-developers.com/showthread.php?t=1871946
Usually the general rule of thumb with upgrading custom rom is full wipe and flash, but some users has dirty flashed and had no problems so it depends whether your phone likes you or not.
mt3g said:
There is a 4.1.2 stock ota ROM?!? I suck lol.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I see what you did there. :highfive:
seokhun said:
Question: when you're running a custom ROM, if there's an update for it, say from 1.0.0 to 1.0.1, you can just flash the update right over and not worry about problems right? Or do you need to factory reset through recovery and wipe the caches all over again?
Click to expand...
Click to collapse
Most of the times when you flash a ROM that is built off itself, you can "dirty flash". Example--> That means if you are already on a RootBox Nightly 2/17 with a clean install and RootBox 3/6 comes out, all you have to do is wipe /cache and /dalvik-cache and then flash the new version of the ROM. If any bugs creep up, then if you dirty flashed, chances are that is why.
If you are going to go from a TWiz ROM to an AOSP/AOKP ROM then I suggest a full factory reset and wipe accordingly. That way you have a clean install.
Read the OPs of the ROMs
TieDye21 said:
Usually the general rule of thumb with upgrading custom rom is full wipe and flash, but some users has dirty flashed and had no problems so it depends whether your phone likes you or not.
Click to expand...
Click to collapse
Yup. Thankfully my phone likes me, plus I kind of know what I am doing with regards to diagnosis.
@OP Can you please post exactly what your Build Number says in Settings>About Phone?
seokhun said:
That ROM is labelled Jelly Bean in the title but underneath that it says it's only compatible with ICS. Question mark.
Question: when you're running a custom ROM, if there's an update for it, say from 1.0.0 to 1.0.1, you can just flash the update right over and not worry about problems right? Or do you need to factory reset through recovery and wipe the caches all over again?
Click to expand...
Click to collapse
You could install the update, but seriously I never do updates. I manual flash the whole new ROM. ( and I never had any accidents or bugs)
For the kernel, its was a example kernel chose the one you prefert ( THAT SUPPORT TOUCHWIZ STOCK ROM ) or just flash a new ROM with build-in kernel like the ParanoidKANGdroid 10.2 ROM !
I flashed the FrostyJellybean ROM with Xone kernel and it's been good so far. I'm a religious person when it comes to battery, but so far it's about the same as the normal drainage on the stock ROM, no noticeable improvements.
Another question (whoop): if I run a Nandroid backup, does that backup include the ROM itself? In other words, if I'm running the Frosty ROM, and there's a ROM I want to test, will creating a Nandroid include the Frosty, or will it just backup the system image excluding the ROM itself? I'm asking this because I have wanted to restore my Nandroids but didn't know if that backup may overwrite my existing ROM with the previous ROM.
Thank you guys for taking your time to help me out, I really appreciate it!
Woody said:
@OP Can you please post exactly what your Build Number says in Settings>About Phone?
Click to expand...
Click to collapse
I have flashed a new ROM, so I no longer have the stock Build Number. It now says FrostyJellybean v11.6. I can tell you for a fact that I was previously running 4.1.1 rooted but without any customization or mod whatsoever outside the phone's original settings, so as stock as you can get.
A Nandroid is essentially a snapshot of your ROM at that point in time. You can back it up, try a new ROM and if you don't like it, then restore your Nandroid. A Nandroid should be done before you flash anything. You don't necessarily have to keep them all except your latest, but at least have one for when you try something out.
You can flash and restore just fine from ROM to ROM. Only thing is, you can't restore across platforms. Meaning, if you are on JB 4.1.1, you couldn't restore to ICS 4.0.4. Likewise you can restore a JB 4.1.1 if you are on a JB 4.2.2 ROM because of the file structure. There are ways to do it, but I won't go into that right now. Moral of that story is you can flash and restore laterally as far as builds go, but you cannot restore across different base builds.
*************
I just wanted to see your Settings>About Phone>Build Number because in your OP, you stated that you were running "stock 4.1.2 Jelly Bean". We don't have a stock 4.1.2 ROM, so I was making sure you didn't have another phone. Sure, could be a T999 but there are Canadian versions out there that require different things.
Oh, about the Android version, yes, it's 4.1.1. I wrote 4.1.2 because I thought there was some stuff going on, like wireless and whatnot, and had previously read somewhere that 4.1.2 was rolling out and my phone was doing the "Android is upgrading" thing when it booted up and I didn't check the version before writing that. No worries, it was the stock 4.1.1.
Thank you so much for answering my questions, you guys are awesome!

Categories

Resources