Hi guys,
I have a pebble blue 32gb S3 running on custom ROM jellyBAM - the latest version with cm kernal.. I would like to know if i flash XXELLA kernal via odin directly to this ROM without bricking it or do i have to go back to official ROM to get XXELLA update.. Also many people are trying to downgrade from XXELLA to old kernals...Why is that.. Does XXELLA truely fixes the EXYNOS bug and the sudden death issues?
Thanks
You are completely confused - CM kernels and JB stock kernels are not interchangeable for one thing. ROMs, Bootloaders and Kernels - read up a little.
Respectfully but strongly suggest you stick with what you currently have... based on your current experience level.
This should also be in the Q and A forum - and for Pete's sake lose the multiple exclamation marks (!!!!!!!).
It's kernEl.
But you're indeed confused, seems like you are talking about the bootloader, not the kernel. You can flash it via Odin and some people think that it fixes the sudden death. The exploit bug, on the other hand, is kernel - related, and most current kernel have it fixed
jtndinesh said:
Hi guys,
I have a pebble blue 32gb S3 running on custom ROM jellyBAM
Thanks
Click to expand...
Click to collapse
I don't think there's one reported case of a SD for a 32GB model. Stay where you are....
Related
Hi, I have the orange i9100p - and rooted using the rachmat3 method
I could really do with a few pointers- Especially from people with the same phone version and root method
I've flashed ROMs before on other phones (desire, desire HD Touch Diamond) but the whole thing seems bewildering on this phone, I've spent days reading and still dont really know whats going on and whats the best way to proceed
So my phone is as stock, still with the Orange ROM updated to ICS, I assume it has stock kernels, but it is rooted etc
I was hoping to flash another ROM, maybe without the Orange stuff, and perhaps one that can use JKAY or something as everyone seems to think thats great and mine dosent seem to be supported. Also maybe deodexed if thats worth doing. I dont like the stock unlock screen, and also tried the s3 launcher and it didnt work on this current ROM - so I want to switch to something that will allow me to do these things.
The only trouble is I have no idea what do. Nothing ever seems to be the obvious way forward
These are some of the questions I keep coming up against -
Should I be able to do these things on my current ROM -
If I change ROMS will I loose NFC (should I care?)
Do I need to keep the same kernel to avoid brickbug risk, and to keep things simple, and if so how do I do that, they all seem to come with Kernel with Chainfire installed which I dont need right? (delete zimage out of the zip file?)
Should I flash with the temporary CWM, or use odin (I haven't used odin yet - can I use it with only the temporary CWM)
Are there any obvious ROMs that would be easy for me to get the above from
Here are some details -
model - gt i9100p
Android version 4.0.3
Baseband version i9100pbvlp7
kernel version [email protected]#3
build number IML74K.BVLP8
Anyone with this phone model in particular, or if you used Rachmat3's method - I'd love to hear what you've done
Free bump for an interesting title.
I'm in a similar situation to the original poster. Got the I9100P UK Orange phone and wanting to flash new firmware but a bit daunted by the information and options out there. I've flashed the old Samsung i8910 and that was pretty painless. The S2 seems a lot more complicated and with more potential problems!
If you can afford the risk, all you need to do is take the leap of faith. Rom and kernel are mostly "safe" to flash (except stock 4.0.4), if incompatible will result in soft brick the phone, where you only have to get it back to download mode and flash back a working one.
Yes, i think you will lose NFC...
It is daunting but dont just be like most of the noobs on here and proceed without doing any research first.
They dont even have the decency to read about basics like
What is cwm
How do I root
What is Odin
Sent from my GT-I9100
L1ndon said:
Hi, I have the orange i9100p - and rooted using the rachmat3 method
I could really do with a few pointers- Especially from people with the same phone version and root method
I've flashed ROMs before on other phones (desire, desire HD Touch Diamond) but the whole thing seems bewildering on this phone, I've spent days reading and still dont really know whats going on and whats the best way to proceed
So my phone is as stock, still with the Orange ROM updated to ICS, I assume it has stock kernels, but it is rooted etc
I was hoping to flash another ROM, maybe without the Orange stuff, and perhaps one that can use JKAY or something as everyone seems to think thats great and mine dosent seem to be supported. Also maybe deodexed if thats worth doing. I dont like the stock unlock screen, and also tried the s3 launcher and it didnt work on this current ROM - so I want to switch to something that will allow me to do these things.
The only trouble is I have no idea what do. Nothing ever seems to be the obvious way forward
These are some of the questions I keep coming up against -
Should I be able to do these things on my current ROM -
If I change ROMS will I loose NFC (should I care?)
Do I need to keep the same kernel to avoid brickbug risk, and to keep things simple, and if so how do I do that, they all seem to come with Kernel with Chainfire installed which I dont need right? (delete zimage out of the zip file?)
Should I flash with the temporary CWM, or use odin (I haven't used odin yet - can I use it with only the temporary CWM)
Are there any obvious ROMs that would be easy for me to get the above from
Here are some details -
model - gt i9100p
Android version 4.0.3
Baseband version i9100pbvlp7
kernel version [email protected]#3
build number IML74K.BVLP8
Anyone with this phone model in particular, or if you used Rachmat3's method - I'd love to hear what you've done
Click to expand...
Click to collapse
So, I have one galaxy s2 i9100p (O2). I come from a stock gb, rooted and flashed a new custom rom using the recovery mode, full wipe and every other things... I lost the nfc function and never found a method to bring this back but every other things are working fine, very fast and stable on 4.0.3 version with siyah kernel... i think you don't will have problems too but you will lose the nfc. it's your choise BTW, I have the stock ics rom with NFC (o2), I don't know but if you need, send me a PM, just flash the .tar file with odin and everything will work again (NFC), like factory new one (sorry my english :/)
L1ndon said:
Hi, I have the orange i9100p - and rooted using the rachmat3 method
I could really do with a few pointers- Especially from people with the same phone version and root method
I've flashed ROMs before on other phones (desire, desire HD Touch Diamond) but the whole thing seems bewildering on this phone, I've spent days reading and still dont really know whats going on and whats the best way to proceed
So my phone is as stock, still with the Orange ROM updated to ICS, I assume it has stock kernels, but it is rooted etc
I was hoping to flash another ROM, maybe without the Orange stuff, and perhaps one that can use JKAY or something as everyone seems to think thats great and mine dosent seem to be supported. Also maybe deodexed if thats worth doing. I dont like the stock unlock screen, and also tried the s3 launcher and it didnt work on this current ROM - so I want to switch to something that will allow me to do these things.
The only trouble is I have no idea what do. Nothing ever seems to be the obvious way forward
These are some of the questions I keep coming up against -
Should I be able to do these things on my current ROM -
If I change ROMS will I loose NFC (should I care?)
Do I need to keep the same kernel to avoid brickbug risk, and to keep things simple, and if so how do I do that, they all seem to come with Kernel with Chainfire installed which I dont need right? (delete zimage out of the zip file?)
Should I flash with the temporary CWM, or use odin (I haven't used odin yet - can I use it with only the temporary CWM)
Are there any obvious ROMs that would be easy for me to get the above from
Here are some details -
model - gt i9100p
Android version 4.0.3
Baseband version i9100pbvlp7
kernel version [email protected]#3
build number IML74K.BVLP8
Anyone with this phone model in particular, or if you used Rachmat3's method - I'd love to hear what you've done
Click to expand...
Click to collapse
Hi there,
I have the same phone model with the same kernel, radio and stock rom.
Did you manage to upgrade firmware to JB (which kernel and rom did you use) and keep NFC??
hello I´m from Panama Latin america today my GT-9300 just recive this:
GTI9300 ( TTT )
PDA: I9300UBEMA1
CSC: I9300UUBELL1
compilation date: 04.01.2013
changes: 789635
my question is if this rom has the fix for the sudden death and security bugs?
titivu said:
hello I´m from Panama Latin america today my GT-9300 just recive this:
GTI9300 ( TTT )
PDA: I9300UBEMA1
CSC: I9300UUBELL1
compilation date: 04.01.2013
changes: 789635
my question is if this rom has the fix for the sudden death and security bugs?
Click to expand...
Click to collapse
Yes, it does.
Looking at this forum its not,
http://forum.xda-developers.com/showpost.php?p=36499838&postcount=1
Quote from forum;
Stock:
The following ROMs include a Kernel and recovery with the Update 7 "Fixes" applied. If you have one of these, officially consider yourself "Safe".
If you rooted one of the below stock ROMs, you will also be safe, however - if you changed to a custom kernel or recovery, you need to look at the below custom sections.
If you have never rooted, the stock section is all you need read.
As It appears all 4.1.2 kernels have the fixes, there is no longer a need to test them all. See below for a list of tested kernels that have the fix. All kernels subsequent to these will also be regarded as safe.
•XXELKC
•XXELL1
•XXELL4
•XXELL5
•XXELL6
•XXELLA
•XXELLB
•XXELLC
People who have never rooted need not read any further. Essentially, if you have an official, never rooted 4.1.2 ROM, you're "safe"
cooza said:
Looking at this forum its not,
http://forum.xda-developers.com/showpost.php?p=36499838&postcount=1
Quote from forum;
Stock:
The following ROMs include a Kernel and recovery with the Update 7 "Fixes" applied. If you have one of these, officially consider yourself "Safe".
If you rooted one of the below stock ROMs, you will also be safe, however - if you changed to a custom kernel or recovery, you need to look at the below custom sections.
If you have never rooted, the stock section is all you need read.
As It appears all 4.1.2 kernels have the fixes, there is no longer a need to test them all. See below for a list of tested kernels that have the fix. All kernels subsequent to these will also be regarded as safe.
•XXELKC
•XXELL1
•XXELL4
•XXELL5
•XXELL6
•XXELLA
•XXELLB
•XXELLC
People who have never rooted need not read any further. Essentially, if you have an official, never rooted 4.1.2 ROM, you're "safe"
Click to expand...
Click to collapse
This ROM is newer. Both by looking at Sammobile and by looking at the build number, it's obvious that it is included.
sweet:good:
A friend of mine has a i9100 (16GB) running Gingerbread 2.3.4 and is tempted to upgrade but my experience on that is limited so I decided to ask here first:
- was there any change in partitioning on i9100 from 2.3.4 to 4.1.x ? or any major change that I should be aware?
- he seems to have the original boot and recovery - best way to upgrade those?
- the battery life seems to be very poor for him right now - would an update to a custom ROM improve things? would something based on 4.1.x be the best improvement?
- overall - what are the steps that you would recommend in going from 2.3.4 to 4.1.x?
xclub_101 said:
A friend of mine has a i9100 (16GB) running Gingerbread 2.3.4 and is tempted to upgrade but my experience on that is limited so I decided to ask here first:
- was there any change in partitioning on i9100 from 2.3.4 to 4.1.x ? or any major change that I should be aware?
- he seems to have the original boot and recovery - best way to upgrade those?
- the battery life seems to be very poor for him right now - would an update to a custom ROM improve things? would something based on 4.1.x be the best improvement?
- overall - what are the steps that you would recommend in going from 2.3.4 to 4.1.x?
Click to expand...
Click to collapse
GB is 2 years old OS.
JB is 7 month old.
Yes, things have improved, in every android aspect.
Right path to upgrade? ODIN.
Safest path? MOBILE ODIN.
What you should do before trying anything:
Read, Watch, Learn and Read again.
Sent from the little guy
The overall improvement was quite good.
It was a little tricky since I first wanted to update the recovery to the latest from philz - which did not work by using the original recovery and a signed zip (which would have avoided the triangle and flash counter) - so in the end I updated the recovery from odin.
Of course that the kernel coming with that was no longer booting the phone, so immediately after that I installed the latest omega - and that started to work fine 'out of the box'. I also had to update things with triangleaway.
I have also added the Siyah kernel for the BLN feature.
Hi,
had my S2 for a while now and installed ICS through ODIN as here in NZ the updates seem to come a little slower than the rest of the world!
but id like to be on Jellybean and heard so much about unsafe Kernels etc (most of it goes over my head haha)
but i figure my best option, as i dont want a bricked phone, is to go back to stock and get my updates the old fashioned way.
what is the best way to do this? i know other phones can do this through KIES itself...(entering a serial etc), does this work with all phones?
any help would be greatly appreciated!
ICS 4.0.4 stock kernel has brick bug. If you are on stock 4.0.4 then avoid any kind of wiping. If you want to flash official JB go here
Hi friends I own Galaxy s 2 i9100....I got it from UK 3 mobile.. After coming to India I have flashed it with a ROM which is unlocked version as its is locked to 3 network...after the flashing I connected it to kies for backup and found the same message as others in this thread mentioned...so I tried reflashing it with a ROM that is compatible with Indian version and got the issue solved ...I am providing the details of the rom now I am using
PDA: I9100XWLQ2
phnoe: I9100DDLPC
CSC: I9100ODDLPD
BUILD info: Fri oct 26 16:04:15 KST 2012
But recently KIES software in my laptop got updated and when I connected my S2 it stated that my phone is not compatible to update from KIES. But, the same day when I connected wifi in my phone I got a message that an update is available and its done successfully.
Now can any body help me to get that issue sorted out when connected to KIES as it accepted before and now why it is not accepting ??
Thanks in Advance
Peaceful Droid said:
ICS 4.0.4 stock kernel has brick bug. If you are on stock 4.0.4 then avoid any kind of wiping. If you want to flash official JB go here
Click to expand...
Click to collapse
thankyou! very helpful...now that i have read that entire post i just have one question....isnt that still classed as a wipe? the first thing it says to do is put your phone into recovery mode then wipe?
Flash Siyah or Dorimanx kernel first (without wiping ANYTHING). Then use the CWM that is installed with either of those to...
A) complete the wipe processes. And
B) flash your chosen stock ROM.
When you flash your ROM, you WILL overwrite the Siyah or Dorimanx kernel you previously flashed as your ROM has its own kernel (and CWM). As things stand at the moment, this is probably for the best because there have been some changes to CM10.1 that have made a lot of standalone custom kernels incompatible with the ROM..... for example, I lost my baseband when I flashed Siyah on top of CM10.1 and I'm told that there can be issues with video recording too. Which brings me to make one more point....before starting any of this...
MAKE A NANDROID BACKUP....
it's your safety net if it all goes wrong (personal experience is a brilliant teacher lol).......
Sent from my CM10 powered Galaxy S2 with tapatalk 2
Hello everyone,
I have recently purchased this phone from my (much) younger brother, who is requires it for school next year. I got it for only £25 used, which was a bargain in my opinion.
My plans are to upgrade it directly to Cyanogenmod 12.1 Lollipop, as I use the same ROM on my other two devices (Nexus 7 2k13, Moto G)
However, I have just found out about the "superbrick" bug which affects our devices. I ran Chainfires app, and it said that my emmc chip and firmware were known to cause issues. The phone is currently still on android version 4.0.3 (ics), so am I right in saying that the superbrick bug is present on this phone currently?
Therefore, what is the best way that I can safely upgrade the phone to Cyanogenmod 12.1, without experiencing this bug? In addition, does CM 12 have the "fix" for superbrick, so that it will not happen again in the future?
Finally, I have read a bit about system partitioning. I would quite like to not have to do this, so can I just Flash CM 12 with the MINI GApps, and not run into any issues?
Thanks a lot for the support, and I look forward to receiving and answer
xN1ghtShadoWx said:
Hello everyone,
I have recently purchased this phone from my (much) younger brother, who is requires it for school next year. I got it for only £25 used, which was a bargain in my opinion.
My plans are to upgrade it directly to Cyanogenmod 12.1 Lollipop, as I use the same ROM on my other two devices (Nexus 7 2k13, Moto G)
However, I have just found out about the "superbrick" bug which affects our devices. I ran Chainfires app, and it said that my emmc chip and firmware were known to cause issues. The phone is currently still on android version 4.0.3 (ics), so am I right in saying that the superbrick bug is present on this phone currently?
Therefore, what is the best way that I can safely upgrade the phone to Cyanogenmod 12.1, without experiencing this bug? In addition, does CM 12 have the "fix" for superbrick, so that it will not happen again in the future?
Finally, I have read a bit about system partitioning. I would quite like to not have to do this, so can I just Flash CM 12 with the MINI GApps, and not run into any issues?
Thanks a lot for the support, and I look forward to receiving and answer
Click to expand...
Click to collapse
First thing I would do is upgrade to jellybean stock. The kernel you have(4.0.3) is vulnerable to the superbrick bug, and rooting the phone from 4.1.2 is easier/safer. Once you do this, you almost never need to worry about this bug again, as the newer kernels are safe. From there use philz kernel to root the phone. Just follow the steps in that thread and match the kernel to the rom. Have a good read, but particularly the 2nd and 3rd posts. Then you need a "kitkat compatible" recovery to flash cm12. You can use the newer philz recovery from HERE. Just flash it then reboot straight back to recovery. Then flash cm12 and gapps etc as normal
Bootloader
Hi, I have recovery installed fine, but inside the CM 12 rom zip, I see a boot.img. If I brick my phone whilst installing the rom, can I still unbrick with the offical 4.1.2 firmware via odin?
Thanks!
xN1ghtShadoWx said:
Hi, I have recovery installed fine, but inside the CM 12 rom zip, I see a boot.img. If I brick my phone whilst installing the rom, can I still unbrick with the offical 4.1.2 firmware via odin?
Thanks!
Click to expand...
Click to collapse
Don't worry about that. That is just the kernel(not bootloader if thats what you thought). Yes it is fine to flash stock firmware if you need.