Hi,
The problem i'm having is every few days my radio will spam the phone asking for root. I have to press accept about 10 times before it goes away (even remembering the selection) only for it to re-appear a few days later asking again. I've tried a different modem and the situation seems to have improved but it's not gone completely (it used to spam over 100 entries at a time).
The rom i'm using is a recent cyanogen JB nightly, and I believe the siyah kernel.
Has anyone else had this issue? Surely the radio shouldn't be asking for root at all, since normal phones don't have that access.
I'm on Vodafone UK. I'm not sure I have the right rom's / radio / kernal so I'll post down what the phone lists here:
Baseband: I9300XXDLID
Kernel Version: 3.0.31-CM-g9ee66ec [email protected] #1
Nightly version: 10-20121202-NIGHTLY-I9300
Build number: cm_i9300-userdebug 4.1.2 JZO54K eng..20121202.091641 test-keys
Does anything look majorly wrong with this?
Thanks,
I've had the same issue the other week on a cm10 nightly.. I've researched it a bit but just put it down to an error of some kind. Would like to know why?
I already posted in the wrong place one... I hope this is the right place.
------------------------------------------------------------------------------------------------------------
Hi,
I have a problem with my S2 after flashing to new firmware. This is the story:
- I purchased a S2. Everything worked fine. This was the data before I did something I shouldn’t have done:
PDA: I9100XWLQ2
PHONE: I9100XXLQ6
CSC: I9100DBTLPO
Sales code: DBT (only)
Android 4.0.4
Baseband version: I9100XXLQ6
Kernel version
3.0.15-1157945
[email protected] #3
SMP PREEMPT Fri Oct 26 16:17:36 KST
2012
Build number: IMM76D.XWLQ2
Kies worked fine (updated to the above).
- The only problem is that the firmware was DBT (German). The UI was in English but some applications were German. Nothing against Germany but I’m UK based.
- I decided to update to a new version using Odin, so I flashed:
I9100XWLPT_I9100XXLQ6_I9100XEULPA
This is where all the problems started:
Every time I boot I got a message saying the process android.(...).acore stopped
Clearing contacts cache/data did not address the problem
I read in this thread that this was due to instability of LP9 and it was advisable to use LP8.
- Flashed using Odin
Kernel_I9100XWLP8.tar.md5
I9100XWLPT_I9100XXLQ6_I9100XEULPA
- Now I have UK applications (which is good) but:
a) Every time I boot I get the message "Unfortunately, LogsProvider has stopped"
Clearing contacts cache/data doesn’t help.
b) When I try to use the phone (e.g. dial a number) I got a black screen for a minute or so and then the LogsProvider message. After that the phone application closes.
c) Kies stopped working with the message:
Your device's current firmware version is not supported to update firmware via Kies
Current firmware version: PDA:LPT / PHONE:LQ6 / CSC:LPA (DBT)
- Flashed I9100XWLPT_I9100XXLQ6_I9100XEULPA_HOME
Same problems
Now internal data is:
Android 4.0.4
Baseband version: I9100XXLQ6
Kernel version
3.0.15-I9100XWLPT-CL941023
[email protected] #3
SMP PREEMPT Fri Jul 27 18:08:15 KST
2012
Build number: IMM76D.XWLPT
In ideal world I would like to have an UK, unbranded, S2 and use Kies for future updates. Having said that, considering that the phone is almost dead any suggestion to bring the S2 back to life would be great.
I’m a little bit desperate... help... please
Thanks
~sf
P.S. I did search and read post, guides, notes, comments and info. I am not sure I understood all of it but I did try - I promise.
Well....why don't you just flash an unbranded stock ROM then? You could always update it via kies or OTA.
Should get 4.0.3 tho, dancing with 4.0.4's kernel might brick your device.
what you mean by "bring back to life", It is still working right?
gastonw said:
Well....why don't you just flash an unbranded stock ROM then?
Click to expand...
Click to collapse
This was the plan:
- Install an unbranded version
- Update via Kies
I didn't work
Do you have any suggestion for a UK-unbranded fimware version (4.0.3) that should work. My understanding is that it should be
a) for GT-I9100 (obviously)
b) XEU version (aka UK)
c) Android 4.0.3
Apart from that, is there any other important requirement?
Would this be ok: http://forum.xda-developers.com/showthread.php?t=1604254
gastonw said:
Should get 4.0.3 tho, dancing with 4.0.4's kernel might brick your device.
Click to expand...
Click to collapse
Ok - Message received. I'll use 4.0.3.
gastonw said:
What you mean by "bring back to life", It is still working right?
Click to expand...
Click to collapse
Well, not exacly. I can't make calls...
Don't worry about either your country or your calls. Search for an unbranded samsung official stock 4.0.3 ROM, flash it, check it out (smoothness and all) and then try to make a call. If it doesn't fly, just flash another modem
gastonw said:
Don't worry about either your country or your calls. Search for an unbranded samsung official stock 4.0.3 ROM, flash it, check it out (smoothness and all) and then try to make a call. If it doesn't fly, just flash another modem
Click to expand...
Click to collapse
I flashed
XEU 2012 April 4.0.3
I9100XWLP7_I9100XEULP5_I9100XXLPS\I9100XWLP7_I9100XXLPS_I9100XEULP5_HOME.tar.md5
I got the following messages:
"Unfortunately, Messaging has stopped working"
"Unfortunately, the process androind.process.acore has stopped"
"Unfortunately, LogsProvider has stopped"
I still can't make calls (black screen + above messages)
:crying:
factory reset & reboot maybe?
those are simple android errors.
gastonw said:
factory reset & reboot maybe?
those are simple android errors.
Click to expand...
Click to collapse
Good news. It looks like the situation has improved after the factory reset.
I'll go to sleep now (it's 2:50am here in London/UK). Tomorrow I'll check all the functions and but it looks like I'm going are in the right direction.
I'll post tomorrow about the results.
Thanks for your help gastonw - it is really appreciated. :good:
np, go get some rest now.
[Q] Brand new S2. After flash: errors, slow... (more questions)
Bingo! The factory reset worked. Everything back to normal. I have my UK application and Kies update to:
Android version: 4.0.4
Base version: I9100XXLQ6
Kernel version: 3.0.15-I9100XWLPT-CL941023
[email protected] #3
SMP PREEMPT Fri Jul 27 18:08:15 KST
2012
Build number: IMM76D.XWLPT
The only odd thing that the "About phone screen/Status" shows serial number 0000000000*. Not the end of the world.
Just a few additional questions
Now, before I make the same mistake again (do something I shouldn't, panic and ask for help)... If I want to root:
a) Can I do it without risking to brick?
b) Can I still use Kies after rooting?
c) Is there a recommended procedure that I should follow?
*update about it the next post.
Quick update about serial number 0000000000. Apparently, it is a 4.0.4 bug. The serial number is stored correctly internally but Android UI shows 0000000000.
The majority of people here probably already know that but just in case...
~sf said:
Now, before I make the same mistake again (do something I shouldn't, panic and ask for help)... If I want to root:
a) Can I do it without risking to brick?
b) Can I still use Kies after rooting?
c) Is there a recommended procedure that I should follow?
Click to expand...
Click to collapse
I manage to find the answers to my own questions :silly:
a/c) I followed the procedure described here. It worked great.
b) Yes. Kies doesn’t seem to care that the S2 is rooted
Result:
- 4.0.4 generic/unbranded/XEU firmware
- Updated and recognised by Kies.
- Rooted successfully.
- So far everything works smoothly and fast
Lesson learned:
- Factory reset after firmware flash resolved the problem.
I couldn’t be happier :good:
~sf said:
I manage to find the answers to my own questions :silly:
a/c) I followed the procedure described here. It worked great.
b) Yes. Kies doesn’t seem to care that the S2 is rooted
Result:
- 4.0.4 generic/unbranded/XEU firmware
- Updated and recognised by Kies.
- Rooted successfully.
- So far everything works smoothly and fast
Lesson learned:
- Factory reset after firmware flash resolved the problem.
I couldn’t be happier :good:
Click to expand...
Click to collapse
Happy to hear that, It's good to find answers just by reading a couple of post or googling around.
Now, I'd like you to read a little more about the brick bug and 4.0.4 ICS.
In the meanwhile, enjoy your device.
gastonw said:
(...)
Now, I'd like you to read a little more about the brick bug and 4.0.4 ICS.
Click to expand...
Click to collapse
I heard of it - although I don't know the details. The 4.0.4 Brick Bug is the reason why I flashed to 4.0.3 instead of 4.0.4.
The Samsung Update application updated to 4.0.4. It wasn't, strictly speaking, my direct choice. I could have ignored the suggestion of updating but I though that, since the update was coming from Samsung and it was applied to stock firmware, it was a safe choice.
gastonw said:
(...)
In the meanwhile, enjoy your device.
Click to expand...
Click to collapse
This sounds a little bit scary Should I be worried about something?
Lol, I remember you were on 4.0.4, told you It would be wise to go 4.0.3 and kies threw you back at 4.0.4.
Download gotbrickbug app from the store and check your chip (just for kicks). If it's insane, well...you can always go back to 4.0.3 and wait for the Jelly Bean update thru both Kies & OTA (Over The Air).
The thing is, you're completly safe whereas you don't flash any ROM or custom ROM, and perform things like wipes thru recovery and what not.
If you want to go in a flashing frenzee, then you might flash a safe kernel (like Siyah), but I think it's not the case, you seem to love Kies updates
The important thing is that your device is running smoothly on ICS; so, enjoy.
gastonw said:
Lol, I remember you were on 4.0.4, told you It would be wise to go 4.0.3 and kies threw you back at 4.0.4.
Download gotbrickbug app from the store and check your chip (just for kicks). If it's insane, well...you can always go back to 4.0.3 and wait for the Jelly Bean update thru both Kies & OTA (Over The Air).
The thing is, you're completly safe whereas you don't flash any ROM or custom ROM, and perform things like wipes thru recovery and what not.
If you want to go in a flashing frenzee, then you might flash a safe kernel (like Siyah), but I think it's not the case, you seem to love Kies updates
Click to expand...
Click to collapse
Hi gastonw,
Thanks again for you useful comments.
I suspected your comments about 4.0.3 vs 4.0.4 were related to my previous attemps of flashing 4.0... and your advice of staying away from it.
I run gotbrickbug and I'm happy to say it reports "Brick Bug? NO. Sane chip" - which I guess is good news.
gastonw said:
The important thing is that your device is running smoothly on ICS; so, enjoy.
Click to expand...
Click to collapse
I haven't tried all the functions but, so far, it works smoothly.
Well, ain't this a good weekend for you? lol
gastonw said:
Well, ain't this a good weekend for you? lol
Click to expand...
Click to collapse
Intense but rewarding :laugh: lol
This is my phone:
Model: Samsung Galaxy SII GT-I9100
Android Version: 4.0.3
Baseband Version: I9100XXLPS
Kernel Version: 3.0.15-I9100XWLP7-CL340913
[email protected] #3
Build number: IML74K.XWLP7
I've successfully flashed the "leaked" JB 4.1.2 ROM on my SGSII, just to see if I could do it - and then restored it back to ICS 4.0.3, with all my apps and data intact, using CWM recovery. While I had JB installed, I found that I couldn’t enable USB debugging, which made me nervous, as I know that a number of the utilities I’ve been using require it.
So my questions are these:
1. any ideas why USB debugging wouldn’t switch on, and what could be done about this?
2. if I were to do the JB thing again and keep it this time, could I use the same rooting mechanism that worked on ICS, and get all the apps and data restored - but this time running under JB? The package I used went by the name CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5 – it includes CWM Recovery.
3. or if not, what is the best way to restore apps and data in this scenario? I really, really don't want to have to restore all my apps and data one by one when I upgrade my phone.
Of course I could just sit on my hands and wait until the official release.... Where’s the fun in that?
alecxm said:
This is my phone:
Model: Samsung Galaxy SII GT-I9100
Android Version: 4.0.3
Baseband Version: I9100XXLPS
Kernel Version: 3.0.15-I9100XWLP7-CL340913
[email protected] #3
Build number: IML74K.XWLP7
I've successfully flashed the "leaked" JB 4.1.2 ROM on my SGSII, just to see if I could do it - and then restored it back to ICS 4.0.3, with all my apps and data intact, using CWM recovery. While I had JB installed, I found that I couldn’t enable USB debugging, which made me nervous, as I know that a number of the utilities I’ve been using require it.
So my questions are these:
1. any ideas why USB debugging wouldn’t switch on, and what could be done about this?
2. if I were to do the JB thing again and keep it this time, could I use the same rooting mechanism that worked on ICS, and get all the apps and data restored - but this time running under JB? The package I used went by the name CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5 – it includes CWM Recovery.
3. or if not, what is the best way to restore apps and data in this scenario? I really, really don't want to have to restore all my apps and data one by one when I upgrade my phone.
Of course I could just sit on my hands and wait until the official release.... Where’s the fun in that?
Click to expand...
Click to collapse
Might get a better answer in the Samsung Galaxy SII GT-I9100 forums.
Everyone just loves our forums so much they post here! We must be that awesome.
Hello everyone I just bought a new phone which is galaxy s3 , I read that my model may suffer the sudden death problem.
The device is new from the box and it is the 16GB model.
Its unrooted and running android 4.1.2
More information about it:
Baseband version: I9300BOLK3
Kernel version : 3.0.31 - 742798 [email protected] -111#1 SMP PREEMPT Sat Dec 22 17:04:04 KST 2012
Build number: JZO54K.I9300XXELLA
Sould I be afraid of audswn death or any proccesor bugs ?
check the SDS threads in General, they have all the info you need
samsung claimed the latest update has fixed sudden death issue,so far I do not see anyone who updated to latest firmware complain about sudden death.
wait, was there an official statement? got a link?
depends on how damage ur s3 had taken and if ur on the safe kernels and recoveries
If you are on XXELLA and haven't rooted and changed kernel then as far as anyone is aware you are protected.....although there has been no official confirmation, but analysis by the hard working devs suggests you're safe.
If you decide to root then make sure you install a recovery that has the fix(most of them now) if you change recovery - likewise with kernel, if you change that.
Thanks alot for helping so i understood that i am protected , i didnt root / change anyting all is stock and i am on XXELLA is that right ?
eyal1728 said:
Thanks alot for helping so i understood that i am protected , i didnt root / change anyting all is stock and i am on XXELLA is that right ?
Click to expand...
Click to collapse
Correct
Hi,
I have a Galaxy S3, unbranded purchased in South Africa. I live in Serbia. Although I read a lot of forum about root still there are things that I have found and I do not understand.
About phone:
Model number: GT-I9300
Android version: 4.1.2
Baseband version: I9300XXELLA or CP:I9300XXELLA
Kernel version: 3.0.31-836582
Build number: JZ054K.I9300XXEMA2 or AP: I9300XXEMA2 and,
CSC: I9300JVEMA1
Because the phone was not taken to the contract, was not cheap (650eur), I would like to turn it into a brick.
First, I do not have a lot of apps, but the phone is a lot slower than when it was new - empty, otherwise is 5 months old. In the task manager, after killing all processes, 20 remain active, and only 150MB of RAM, known to fall at 80MB. Processes that kill will always return immediately, so that you only have to stop, but do not know which are needed and which are not. Probably when the phone root, there are more options in terms of this. Now we come to the question of.
I know that at root, it must taking care of versions, but I would particularly like someone said, the above things which must be matched and what might not.
For example: Baseband version must be the same version but does not have, you can make this and that, or Build number must be the same version but does not have, you can make this and that and and at the end of CSC must be the same version but does not have. You know what I mean.
I read on the forum, it must first model to be the same, meaning I9300, then build number, if all must be the same, in my case JZ054K.I9300KKEMA2 or just the first part JZ054K?
I know that the CSC does not need to be the same, this is a South African, would I have got if you would put a European or Serbian?
I see the signatures of various kernel, how do I know that I can use on my phone?
I know that these questions are for you who know the funny, but to us who are novices in this not so much. If there were no consequences if something goes wrong, the financial think there would be no problem experimenting, but this just is not. Not urgent, slow when you have time, you respond.
Appreciate in advance.
Cheers !!!
There is always risk when you try to flash something on your phone that it could never go on again. The risk is pretty small but it`s there.
If you still want to Root, there are several different methods, one very easy way is to flash a Kernel, that will Root your device.
Since you have Android 4.1.2 Jelly Bean installed you can flash the Siyah Kernel. This Kernel will root your device and it supports all Samsung Jelly Bean ROMs.
You can get it here:
http://forum.xda-developers.com/showthread.php?t=1709686
Download the tar file and flash it through Odin.