[Q] I727 roms on Galaxy S2 4G i9210t - AT&T Samsung Galaxy S II Skyrocket SGH-I727

Hi Devs, just to start off I am not a dev and there am not able to solve the question below.
I am a proud owner of the Galaxy S2 4G i9210t the Australia Telstra version, we are able to flash all gingerbread roms from the i727 and they run perfect except for one little problem when we flash the gingerbread rom from i727 we lose our capacative button it completely stops to function so to get it back to work we have to restore the original boot.img from our nandroid backup and then the rom starts to function perfectly.
So I decided to try your ics roms from the i727, so obviously it has the same problem everything works except of the capacative buttons so the problem is we have to restore the boot.img from the nandroid backup, but the boot.img is from a gingerbread roms so the rom does not boot.
So the ics roms work perfectly except for that one problem and I believe the problem is somewhere in the boot.img. I hope someone can help.

you're SOL (sh1t outta luck). U need an ICS kernel for your device, and until u get one (from an ICS release) or source drops for our device and someone ports it, its not gonna happen.
so basically, no. Sorry bud.

icenight89 said:
you're SOL (sh1t outta luck). U need an ICS kernel for your device, and until u get one (from an ICS release) or source drops for our device and someone ports it, its not gonna happen.
so basically, no. Sorry bud.
Click to expand...
Click to collapse
thanks buddy, what about for the gingerbread kernel can anything be done with it so that we don't have to restore original boot.img every time we flash a gingerbread rom to get the capacitive buttons working?

madshabz said:
problem everything works except of the capacative buttons so the problem is we have to restore the boot.img from the nandroid backup
Click to expand...
Click to collapse
Hi,
I just stumbled across this thread as I was looking for ROMs for an I9210 that I need to repair, just something that sprung to mind and that was a similar situation between the Samsung Galaxy S, Samsung Vibrant and Samsung Captivate. Although the Vibrant and Captivate were running Cortex-A8 core and the Galaxy S was running S5PC110 and yes the boot.img files were completely different, I found that the ROMs were essentially the same except for the same issue you were having. As a work around I figured out that the key mappings could be switched around to allow the back button to function correctly
I know that this is dead thread and I am necro-bumping like a zombie, however if you run into this issue in the future it might be something to consider? Especially considering ROMs for I9210 stop at ICS now and I would assume that the i727 has gone on to Jellybean due to it's popularity in the US?
In the Vibrant the keys were found in /system/usr/keylayout/
The other things that were different between them were the modules them selves, in the S1 they were located in /system/lib/modules although I am fairly certain this is a symlink not an actual location but it will give you or someone else something to consider when thinking of porting any roms over in the future.
Edit: If you want to port ROMs, you need to go back to the closest possible denominator and work backwards. What I mean is that you download two standard firmware packages for I727 and I9210 both in Gingerbread 2.3.6 and then diff the both packages against each other. From the files that differ, if you cannot simply trade them in/out because of significant changes in Android versions then you can resort to decompiling the files that differ from each device and then proceed to diff the decompiled code. It's not impossible it's just very difficult and time consuming. I have managed to port ROMs from I9100(Galaxy S2) to I9000(Galaxy S), I9020(Nexus S) to I9000(Galaxy S), I897(Captivate) to I9000(Galaxy S) and T959(Vibrant) to I9000(Galaxy S).
James

Related

[Q] SGS black screen and have to remove battery..any ideas??

my GF has a SGS I9000...i updated her via Kies to the latest firmware because it was performing like crap. The update fixed that but every now and again it stops responding and the screen goes black...lights are still working on the buttons.
You can't power it off with the power button and the only way to fix it is to remove the battery. I've just updated her the the latest ROM from XDA for the SGS from http://forum.xda-developers.com/showthread.php?t=1102881 XWJVZ/XXJVT/OXXJV9/Sbl (MultiCSC) but it still does it...any ideas??
I've seen a few posts but no fixes..any ideas...HW vs. SW..was fine before the updates.
tia
First thing to do is isolate the problem as a hardware or software one. Simple task: flash stock, and see if it happens. If it does, you know it's hardware.
If it isn't, ask the developer (if it's a custom rom), or post under the appropriate phone of the forum. Chances are, if it is software, someone else with the same device has had it before.
NType3 said:
First thing to do is isolate the problem as a hardware or software one. Simple task: flash stock, and see if it happens. If it does, you know it's hardware.
If it isn't, ask the developer (if it's a custom rom), or post under the appropriate phone of the forum. Chances are, if it is software, someone else with the same device has had it before.
Click to expand...
Click to collapse
Tried a stock ROM straight from the Telco, now flashed to a stock ROM from XDA. Happening on 2 phones, both SG2 i9000. Both have different ROMS from different Telco's both were fine before the latest ROM updates.
One appears better with the latest official stock ROM from XDA but just monitoring it at the moment...just wanted to know if it was a know issue before spending too much time on it
ta

[Q] Planning to root and put a custom rom on a friends phone

Hi there, my friend is coming round soon and I was planning to give it a custom rom
Now, I've done this type of stuff before (on my nexus) I just want to see how you would do it for this samsung phone
Now, what recoveries can you get? I use 4EXT on mine
And, can anybody send me to a stable and up-to-date rom that can be used everyday and has nearly no issues? I need one without all the samsung stuff, just a normal default android one
And, how would I go by rooting the phone?
On mine, I used the zergrush exploit, does it work for this phone??
If you want one with everything working, then use the Froyo roms. CM7 is under development. The major bugs are bluetooth and youtube hq. Leaving that, even thats useable. It's even better than Froyo.
I suggest you to try either Kyorarom or Kyrillos v9.6. Both of them are froyo based, pre-rooted, and have other mods to make it even more faster than a stock one.
Happy flashing!
ak700 said:
If you want one with everything working, then use the Froyo roms. CM7 is under development. The major bugs are bluetooth and youtube hq. Leaving that, even thats useable. It's even better than Froyo.
I suggest you to try either Kyorarom or Kyrillos v9.6. Both of them are froyo based, pre-rooted, and have other mods to make it even more faster than a stock one.
Happy flashing!
Click to expand...
Click to collapse
Thanks, and how do I go about flashing the rom, would I have to root it first?
No need.
This is something to good to read http://forum.xda-developers.com/showthread.php?t=1372414
BTW to root the phone use super one click root (or sth like that )
Ah, I get it now, thanks
Just one more question, does ODIN delete the phones data before installing the rom?
You have to wipe all your data after flashing(or not if from Froyo to Froyo)
I mean from recovery. ODIN don't delete user data
I exactly I don't know the working of odin, but after flashing you are directly taken to the recovery and advised to wipe data and factory reset.

[Q] Capacitive Button Help

I just installed UCLD2 Smooth ICE 5.0 followed his instructions and I like the Rom, but I have an issue. My home button and search button do not work at all. I've gone into the settings to see if there is anything to change what the buttons do, but I've found nothing.
Does anyone know what could be causing this? Or what I can do to fix it.
I had the same issue with flashing sky is. I did a nandroid recovery, then reflashed the whole thing and allowed the system to settle longer than the suggested 5 minutes. It works great now. Buttons are fine.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Well as it turns out that was only one of a myriad of problems, I may or may not have permanantly bricked my phone. I let the system settle, but now the screen isn't very responsive when I try to do anything on it. I also tried returning to stock, and have had the same problems.
I don't have any idea what happened, but it seems to be like a kernel problem.
CrazyLineman777 said:
Well as it turns out that was only one of a myriad of problems, I may or may not have permanantly bricked my phone. I let the system settle, but now the screen isn't very responsive when I try to do anything on it. I also tried returning to stock, and have had the same problems.
I don't have any idea what happened, but it seems to be like a kernel problem.
Click to expand...
Click to collapse
If it turns on then its far from bricked. What was your method of returning to stock?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
There's been way too much of this nonsense recently. You don't even know what a brick is. All the new guys need to stop flashing everything they can get their hands on. Stop and read before you do this stuff to your phone. I read for almost a whole month, everything I could find before doing anything. Before I even flashed anything, I had everything needed to fix and return to stock, and made sure I completely understood what I was doing. Read and understand before you break stuff so you can fix it!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I...I....I give up Congrats noobs not just op you have killed my faith in humanity you all have won and destroyed my spirits
Sent from my SGH-T989 using Tapatalk 2
When most of us first installed the leak the fix was to install it again with the 1 click or factory reset.... Are you coming from stock gb or stock ics leak?
Edit: nrm and dx you guys crack me up
CM9 Skyrocket
I didn't flash whatever I could get my hands on thank you. I flashed NexusMod 4.3 Nexus UI first about a week and a half ago. Then I wanted to try and get something a little more like stock, but still ICS so after READING ALL THE INFORMATION on the post for ICS Smoothie v2 I flashed it after wiping data, cache, and dalvik and following the instructions regarding an ICS radio which I had not followed previously with Nexus Mod when I flashed it. Then the problems started.
There is no lockscreen even when the phone decides to work. When I start up the phone. Process.google.acore force closes as does process.google.gapps
Also when I unlock the phone the screen will respond to 1 maybe 2 swipes to find a homescreen then it'll hang.
I used ODIN to return to stock following the instructions on the Stickied post about doing so in the Development section. Also I'm sorry if some of what I said comes off rude I've just been trying to fix this for about 4 days with no luck and I really need some help.
Also I would've responded sooner, but it's finals week at my college so I've only got so much time.
Also I apologize for calling it a brick even though it was not. I do know what a brick is. It's when your device is unresponsive and will not turn on or do anything. It'a a paperweight or a brick.
I was freaking out my bad. I am sort of seasoned I was rooting my HTC Inspire when I got it almost a year ago, and I put ICS on it when the first leaks started coming out. I'm sorry I'm new to this phone. I will be getting better trust me. I just need some time to get used to the different quirks involved in this phone compared to my last one.
CrazyLineman777 said:
Also I apologize for calling it a brick even though it was not. I do know what a brick is. It's when your device is unresponsive and will not turn on or do anything. It'a a paperweight or a brick.
I was freaking out my bad. I am sort of seasoned I was rooting my HTC Inspire when I got it almost a year ago, and I put ICS on it when the first leaks started coming out. I'm sorry I'm new to this phone. I will be getting better trust me. I just need some time to get used to the different quirks involved in this phone compared to my last one.
Click to expand...
Click to collapse
My suggestion still stands use the ics leak 1 click then root see how you like stock ics twiz if you want a more custom rom then goto cwm and wipe cache , factory reset, then in mounts wipe sys, wipe cache and wipe data do all of these 3 times before installing rom and kernel always let.it sit a few minutes to settle....
CM9 Skyrocket
Ok I'm sorry for causing all of these issues I think I found a solution. In the General section and since I can't post links it is entitled:
[FIX] No Power Menu, No Lockscreen, Corrupt Efs FIX! Skyrocket and T989
Sorry I didn't look in General before posting this in Q&A the General section in the HTC Inspire forum wasn't usually gonna have fixes in it maybe root methods, but not fixes for stuff like this.
CrazyLineman777 said:
Ok I'm sorry for causing all of these issues I think I found a solution. In the General section and since I can't post links it is entitled:
[FIX] No Power Menu, No Lockscreen, Corrupt Efs FIX! Skyrocket and T989
Sorry I didn't look in General before posting this in Q&A the General section in the HTC Inspire forum wasn't usually gonna have fixes in it maybe root methods, but not fixes for stuff like this.
Click to expand...
Click to collapse
What radio did you flash?
I did realize I had done it wrong I flashed this: ATT-GALAXY-NOTE UCLC5 radio
but it was the one located in the post for Embryo 2.2 and I didn't flash the embryo rom, so the radio file which Mohan made specifically for his rom didn't go over well with the rom I flashed.
I did get back to stock eventually. It just took a few tries and the efs fix. I'm now putting CWM touch back on my phone and flashing a Gingerbread Rom because ICS on our phone is still a little too iffy for my likeing. I'll probably just wait till Samsung releases source for the kernel and cook my own rom.
CrazyLineman777 said:
I did realize I had done it wrong I flashed this: ATT-GALAXY-NOTE UCLC5 radio
but it was the one located in the post for Embryo 2.2 and I didn't flash the embryo rom, so the radio file which Mohan made specifically for his rom didn't go over well with the rom I flashed.
I did get back to stock eventually. It just took a few tries and the efs fix. I'm now putting CWM touch back on my phone and flashing a Gingerbread Rom because ICS on our phone is still a little too iffy for my likeing. I'll probably just wait till Samsung releases source for the kernel and cook my own rom.
Click to expand...
Click to collapse
I see, the note modem corrupts the efs partition. Glad you read some things and got it fixed!

Having problems after official 4.0.4 update via kies

I have been waiting for the official ics update and it finally came out and i updated my phone through samsung kies. After it was done updating i had a ton of problems. Applications would foreclose on me, my phone would hang up on the lock screen and would reset and this literally happened every 10 minutes. I just dont know what to do. i want to keep ics but have no choice but to go back to GB or unofficial ics(4.0.3). Can someone help me out why im getting these problems?
cpat258 said:
I have been waiting for the official ics update and it finally came out and i updated my phone through samsung kies. After it was done updating i had a ton of problems. Applications would foreclose on me, my phone would hang up on the lock screen and would reset and this literally happened every 10 minutes. I just dont know what to do. i want to keep ics but have no choice but to go back to GB or unofficial ics(4.0.3). Can someone help me out why im getting these problems?
Click to expand...
Click to collapse
do a factory reset, or try the odin tar.
I would say use Odin to flash back to 2.3.5 and then take the 2.3.6 ota. If u really want the stock ics released by att you can then try to update again through kies but I would recommend a rom instead.
Sent from my Skyrocket i727 running Sky ICS
cpat258 said:
I have been waiting for the official ics update and it finally came out and i updated my phone through samsung kies. After it was done updating i had a ton of problems. Applications would foreclose on me, my phone would hang up on the lock screen and would reset and this literally happened every 10 minutes. I just dont know what to do. i want to keep ics but have no choice but to go back to GB or unofficial ics(4.0.3). Can someone help me out why im getting these problems?
Click to expand...
Click to collapse
I believe u can also go into standard recovery and wipe caches. I heard this can help fix fc issues. Dont do a factory reset in settigs! Can someone confirm cache clear on stock recovery or is cwm necessary. I don't want to steer him wrong.
Sent from my Skyrocket i727 running Sky ICS
Mike on XDA said:
I believe u can also go into standard recovery and wipe caches. I heard this can help fix fc issues. Dont do a factory reset in settigs! Can someone confirm cache clear on stock recovery or is cwm necessary. I don't want to steer him wrong.
Sent from my Skyrocket i727 running Sky ICS
Click to expand...
Click to collapse
explain why he shouldn't do a factory reset?
as i can tell his os is busted already so he might as well try it.
and don't do roms they are just bad stick with stock and mod it yourself.
popcorn900 said:
explain why he shouldn't do a factory reset?
as i can tell his os is busted already so he might as well try it.
and don't do roms they are just bad stick with stock and mod it yourself.
Click to expand...
Click to collapse
Source has not been released yet so it can't be known whether the kernels have the brick bug fix. The rule of thumb at least until source comes out is never do any wiping within ics. It will corrupt a partition (I forget which particular one) as the MMC_CAP_ERASE command is giving resulting in something like 20 0's being placed in the partition renderring it useless. If this occurres then nothing (as of now anyway) can repair the phone. No jtag, no USB jig, etc will be able to save it. Samsung was aware of the issue and probably fixed the kernels but until source is dropped better be safe than end up with a paper weight
Sent from my Skyrocket i727 running Sky ICS
popcorn900 said:
explain why he shouldn't do a factory reset?
as i can tell his os is busted already so he might as well try it.
and don't do roms they are just bad stick with stock and mod it yourself.
Click to expand...
Click to collapse
How do u possibly think roms are bad lol and unless u are simply talking about button mods, changing signal/ battery icon, 14 toggle notification bar and a change in kernel there isn't much the average user will be able to change. Roms are so much better than stock. If u don't feel the same then u must of had difficulties with the particular rom u used or chose an unstable rom. I have had 0 problems on SeanZ Sky ICS....I highly recommend it
Sent from my Skyrocket i727 running Sky ICS
Mike on XDA said:
How do u possibly think roms are bad lol and unless u are simply talking about button mods, changing signal/ battery icon, 14 toggle notification bar and a change in kernel there isn't much the average user will be able to change. Roms are so much better than stock. If u don't feel the same then u must of had difficulties with the particular rom u used or chose an unstable rom. I have had 0 problems on SeanZ Sky ICS....I highly recommend it
Sent from my Skyrocket i727 running Sky ICS
Click to expand...
Click to collapse
that brick bug you talk of is probably non existent with the new samsung releases.
also its been very well observed that mod roms are plagued with problems fc's ect ect.
he can make his stock rom look and feel like Google ice 4.0.4 very easily.
the only thing he needs is a unsecured kernel, then he is on his way.
this is just my opinion.
i have rogers stock 4.0.4 with mohens kernel and a couple of other mods and i have my sgs2 looking exactly like a nexus and everything works as it should no fc's and other crap like that.
popcorn900 said:
that brick bug you talk of is probably non existent with the new samsung releases.
also its been very well observed that mod roms are plagued with problems fc's ect ect.
he can make his stock rom look and feel like Google ice 4.0.4 very easily.
the only thing he needs is a unsecured kernel, then he is on his way.
this is just my opinion.
i have rogers stock 4.0.4 with mohens kernel and a couple of other mods and i have my sgs2 looking exactly like a nexus and everything works as it should no fc's and other crap like that.
Click to expand...
Click to collapse
Key words here are "probably". I agree it is most likely fixed but I don't want to see someone end up with a broken phone because we think Samsung "probably" fixed their kernels.
As for the rom I have not had any fc's lag etc. You can do what you like with your phone I am just merely stating that I have been issue free with Sky ICS as have many others. There is always the chance of issues arising but following instructions and reading the thread will clear up any problems. If u do ur homework ie read and/or ask questions if u don't understand something then many of these problems people have could be avoided IMHO. People on XDA wouldn't constantly be flashing roms if they were all filled with bugs and stock were there best option. Just saying...
For the sake of this thread and helping the OP I will avoid the back and forth about custom rom vs stock as the main point here is to help the OP get his Skyrocket back up and running as it should
Sent from my Skyrocket i727 running Sky ICS
PS: If I was able to help you then hit thanks
Mike on XDA said:
Key words here are "probably". I agree it is most likely fixed but I don't want to see someone end up with a broken phone because we think Samsung "probably" fixed their kernels.
As for the rom I have not had any fc's lag etc. You can do what you like with your phone I am just merely stating that I have been issue free with Sky ICS as have many others. There is always the chance of issues arising but following instructions and reading the thread will clear up any problems. If u do ur homework ie read and/or ask questions if u don't understand something then many of these problems people have could be avoided IMHO. People on XDA wouldn't constantly be flashing roms if they were all filled with bugs and stock were there best option. Just saying...
Sent from my Skyrocket i727 running Sky ICS
PS: If I was able to help you then hit thanks
Click to expand...
Click to collapse
well im happy you satisfied with sky ice. my point if i didn't make it clear is that mod roms use stuff from different roms and phones that don't work right with our phones and there will always be problems with it. it is easier and safer to stick with stock and build it up yourself. i have tried everything out there for my phone and hard bricked it twice and i have come to the conclusion that stock is best but for the kernel a unsecured is a must and maybe a good Governor will help.
cpat258 said:
I have been waiting for the official ics update and it finally came out and i updated my phone through samsung kies. After it was done updating i had a ton of problems. Applications would foreclose on me, my phone would hang up on the lock screen and would reset and this literally happened every 10 minutes. I just dont know what to do. i want to keep ics but have no choice but to go back to GB or unofficial ics(4.0.3). Can someone help me out why im getting these problems?
Click to expand...
Click to collapse
You could odin a version of Clockwork Mod onto your phone and wipe the cache and dalvik cache if you want to try saving everything. That would eliminate any concerns about the "brick bug"
Did you do the update install or the wipe install? See this post for info on the different methods.
I suggest that you do the wipe install. You will have to re-install all your apps. It will like setting your phone up when it was new. In many cases an upgrade install will have problems.
.
Thanks alot guys...i wiped data/factory reset, wiped cache, and wiped dalvik cache and flash stock first and then updated it through kies. Its finally working normally

Interesting 1st attempt

Hey guys, I'm new to the community and I just wanted to post my 1st experience with rooting etc and follow up with a few questions!
A bit of background on my device: I've had my NS for just over 3 years now and I just recently decided (when I bought my Xperia V) that I'd like to play around with it a bit. To my knowledge, my device was one of the 1st in the country and a test dummy, and I purchased it from a friend who was working and testing for Samsung at the time. It was not linked or affiliated to Vodacom (who, if I'm correct, was the only network provider to offer the NS in S. Africa) or any other carrier for that matter. So basically due to the lack of link to any carrier, I've never received any updates or notifications to update, and have been running my stock 2.3.5 for 3 years!
Anyway, my story from yesterday was a huge learning experience. I decided that I wanted to root my NS and possibly try out a new kernel before deciding whether or not I wanted to install a custom ROM. I followed this link and managed to root my NS, install CWM recovery and everything was working pretty well using UPDATE-SuperSU-v1.65.
http://forum.xda-developers.com/showthread.php?t=2034264
However I think I flashed the wrong kernel (marmite_v9.1) or for some other reason messed up, keep in mind that I was still running my stock GB which the phone came with. Either way, I was stuck on the Google boot screen for more than an hour. I fired up into fastboot and then recovery, but couldn't boot from there (I just realized that I DIDN'T make an actual backup ). To top it off I wiped the device (another great idea) and the device wouldn't boot into fastboot, giving me a "fastboot mode no boot recovery img" message. Somehow through flashing the CWM I managed to get the device into the correct fastboot mode, and eventually after digging for a few hours I managed to find this (stock?) soju GB ROM download, and managed to flash the boot and system images using fastboot, for some reason " fastboot flash userdata data.img" refused to flash. http://forum.xda-developers.com/showthread.php?t=478820
Anyway, I managed to get back to GB 2.3.5, but get this, after about half an hour on charge, I was given an update to ICS 4.0.4 which I obviously jumped at, and to top it off, I also have JB 4.1.1 available. My NS has finally seen the light of ICS and JB!!
I have a few questions for those who have used ICS and JB though. On the NS, does stock JB provide a notable difference in battery life and speed? With it's hardware, is it capable of handling ICS and JB effectively?
Also, which version of marmite would be compatible with ICS? From what I've picked up, marmite 9.1 is compatible with JB, but is it compatible with ICS too, and if not, can someone please point me in the right direction for kernel(s) which work with ICS (not just marmite).
Second, are the Oxygen and Rasbeanjelly ROMs still up to date? When searching for Oxygen for NS on the forum, the most recent version I find is this which was posted over a year ago: http://forum.xda-developers.com/showthread.php?t=1605273
And this for Rasbeanjelly (among others): http://forum.xda-developers.com/showthread.php?t=2028718
When checking out fitsnugly.euroskank, I don't see anything for the NS. . But maybe I'll consider a shot at the PA and CM ROMs and try them both in a few days
Finally, and this 1 is way over my head, but how does CWM work? If I do a wipe before flashing a ROM/kernel, won't that wipe my backups? Do I need to partition my sd before wiping, or does CWM do that for me, and if it not, does wiping not touch the backups?
Anyway, thanks in advance, and I hope I haven't asked too many questions which have been answered before. If I have, please bare with me and point me to the correct discussion(s) and I'll go bug some other people.
uwais27 said:
Hey guys, I'm new to the community and I just wanted to post my 1st experience with rooting etc and follow up with a few questions!
A bit of background on my device: I've had my NS for just over 3 years now and I just recently decided (when I bought my Xperia V) that I'd like to play around with it a bit. To my knowledge, my device was one of the 1st in the country and a test dummy, and I purchased it from a friend who was working and testing for Samsung at the time. It was not linked or affiliated to Vodacom (who, if I'm correct, was the only network provider to offer the NS in S. Africa) or any other carrier for that matter. So basically due to the lack of link to any carrier, I've never received any updates or notifications to update, and have been running my stock 2.3.5 for 3 years!
Anyway, my story from yesterday was a huge learning experience. I decided that I wanted to root my NS and possibly try out a new kernel before deciding whether or not I wanted to install a custom ROM. I followed this link and managed to root my NS, install CWM recovery and everything was working pretty well using UPDATE-SuperSU-v1.65.
http://forum.xda-developers.com/showthread.php?t=2034264
However I think I flashed the wrong kernel (marmite_v9.1) or for some other reason messed up, keep in mind that I was still running my stock GB which the phone came with. Either way, I was stuck on the Google boot screen for more than an hour. I fired up into fastboot and then recovery, but couldn't boot from there (I just realized that I DIDN'T make an actual backup ). To top it off I wiped the device (another great idea) and the device wouldn't boot into fastboot, giving me a "fastboot mode no boot recovery img" message. Somehow through flashing the CWM I managed to get the device into the correct fastboot mode, and eventually after digging for a few hours I managed to find this (stock?) soju GB ROM download, and managed to flash the boot and system images using fastboot, for some reason " fastboot flash userdata data.img" refused to flash. http://forum.xda-developers.com/showthread.php?t=478820
Anyway, I managed to get back to GB 2.3.5, but get this, after about half an hour on charge, I was given an update to ICS 4.0.4 which I obviously jumped at, and to top it off, I also have JB 4.1.1 available. My NS has finally seen the light of ICS and JB!!
I have a few questions for those who have used ICS and JB though. On the NS, does stock JB provide a notable difference in battery life and speed? With it's hardware, is it capable of handling ICS and JB effectively?
Also, which version of marmite would be compatible with ICS? From what I've picked up, marmite 9.1 is compatible with JB, but is it compatible with ICS too, and if not, can someone please point me in the right direction for kernel(s) which work with ICS (not just marmite).
Second, are the Oxygen and Rasbeanjelly ROMs still up to date? When searching for Oxygen for NS on the forum, the most recent version I find is this which was posted over a year ago: http://forum.xda-developers.com/showthread.php?t=1605273
And this for Rasbeanjelly (among others): http://forum.xda-developers.com/showthread.php?t=2028718
When checking out fitsnugly.euroskank, I don't see anything for the NS. . But maybe I'll consider a shot at the PA and CM ROMs and try them both in a few days
Finally, and this 1 is way over my head, but how does CWM work? If I do a wipe before flashing a ROM/kernel, won't that wipe my backups? Do I need to partition my sd before wiping, or does CWM do that for me, and if it not, does wiping not touch the backups?
Anyway, thanks in advance, and I hope I haven't asked too many questions which have been answered before. If I have, please bare with me and point me to the correct discussion(s) and I'll go bug some other people.
Click to expand...
Click to collapse
Follow the link in my signature for a ROM review... I've heard debates over the best versions for battery life, but JB in my opinion is far superior to ICS... Oxygen is a great ROM, but it won't get more updates and kernels/mods ect.. Are harder to obtain.. It may be a bit challenging to do, but I'd use 4.1.2 JB (follow my chart) or skip to 4.3 JB (Mokee or Slimbean)
Sent from my Nexus S using xda premium
good flashing
uwais27 said:
On the NS, does stock JB provide a notable difference in battery life and speed?
Click to expand...
Click to collapse
Speed yes. Battery life no.
uwais27 said:
With it's hardware, is it capable of handling ICS and JB effectively?
Click to expand...
Click to collapse
There are stutters here and there. You need to overclock to obtain "optimal" ICS and JB performance. JB is smoother than ICS.
uwais27 said:
Second, are the Oxygen and Rasbeanjelly ROMs still up to date?
Click to expand...
Click to collapse
No.
uwais27 said:
If I do a wipe before flashing a ROM/kernel, won't that wipe my backups?
Click to expand...
Click to collapse
No.
uwais27 said:
Do I need to partition my sd before wiping,
Click to expand...
Click to collapse
No.
uwais27 said:
....does wiping not touch the backups?
Click to expand...
Click to collapse
Normally it does not. Unless you select "wipe external sd card"

Categories

Resources