Hi all....
I am an infrequent user of this site, the last time I pored over the information housed in here was a couple of years ago when I found the site and various threads invaluable for me when rooting my old and trusty HTC Desire.
I am now the owner of a fab and groovy galaxy S3 which I aquired in the UK from carphone warehouse.
I am using Vodafone as a carrier, but my understanding is that the stock phone was not tied in any way to a carrier.
It didn't take me long to root the phone, I only rooted the device because I wanted to get rid of various bits of samsung/bloatware, not in order to Flash a new rom to the phone.
I was more than happy with this until I received a notification that there was an OTA update, this I deemed to be the JB OS, which of course would not install due to the fact the phone was rooted and was using cwm etc.
After a week of cancelling the update and being reminded of it every three hours I decided that it was maybe time to update, I discovered that in order to do this I needed in effect to put the phone back to its factory state, soo I completed a factory reset on the phone and in no time at all I was up and running again with an unrooted S3....however, despite this in the last three weeks I have seen hide nor hair of the update that seemed to be banging at my door for so long!
My question therefore is:
is there something I am unaware of that is now stopping my phone from receiving the OTA update via settings/about device/software update/update(check for updates)?
To help those of you that know about this stuff here are the details from the phone that may help you to help me...and anyone else not in the know enough!
Device Status = Normal (while rooted this obviously showed as being modified)
Model Number GT-19300
Android version 4.0.4
baseband version - 19300XXLG8
kernel version - 3.0.15-928452-user [email protected] #1 SMP PREEMPT Thu Jul 26 12:06:08 KST 2012
Build Number IMM76D.19300XXBLGB
In addition prior to unrooting the phone the foillowing info was parsed and returned :
AP: 19300XXBLG8
CP: 19300XXLH1
CSC: 19300OXABLG8
Following unrooting and completing a factory reset.....the same process returns this information.....
AP: 19300XXBLG8
CP: 19300XXLG8
CSC: Unknown.
My apologies for the length of the post for what is probably a trivial matter, but as a Phone noob (but a systems pro) you can never have too much info!
many thanks in anticipation!
It's because your CSC was lost when you unrooted and hence OTA won't work. You would have been better off using the toolkit (see original development forum) to simply download and flash the JB ROM yourself, then no need to unroot etc.
You can still do this and you'll also get updates usually faster than OTA.
Regarding your bust CSC, try:
http://forum.xda-developers.com/showthread.php?t=1845103
Hmmm...well...
many thanks for the info re the cause of the issue, however, having looked at the following I still am having no joy.
1) downloaded a correct csc file and using odin flashed it to my phone, however, it is still showing the same information as before.
2) Found a stock Rom. the exact same Rom as that which is installed, that has been flashed using Odin and once again, upon reboot the information is exactly the same.
I'm not quite sure why you want to fix it, flashing jb yourself is much quicker, but a quick search found:
Q. I have flashed XXXX ROM and now my CSC is unknown?
A. Generally Speaking CSC does not make much of a difference. If you are really facing a problem which is related to CSC such as some specific apps not working, some language not there etc. Either:
Use
Type *#272*Device IMEI# at Phone dial pad.
Select the CSC that you want.
Click Install.
or Install CSC changer app from the Market and change the CSC
Both ways yopur device will be factory resetted.
Good luck.
I can....
...find all of that myself, It doesn't really help much if the person searching amongst the huge amount of disarticulated information liberally strewn around this forum is faced constantly with broken links or unhelpful replies and threads that vanish up their own orifice.
In order to decorticate that information it helps if some form of standardisation or common language is employed.
I have my reasons for asking the original question.
I am facing a problem and asking for advice and help in order to rectify the issue.
I have tried to flash the JB ROm myself, I am despite what you may consider not stupid, however, I am receiving errors when flashing the rom from the 'update' menu from the recovery menu within the phone.
Elsewhere on this forum I discover that it may be an issue with the csc being in an unknown state, hence my post in the first place, If I was able to follow the instructions and all was working as it should I would not bother anyone here or indeed waste my time doing so.
by querying the csc by using the dial pad it shows me that the correct one is still there, so installing it seems pointless, however, as stated at the very beginning of the question, when parsing the phone for detail info it tells me that the csc is 'UNKNOWN'
Greywolf907 said:
many thanks for the info re the cause of the issue, however, having looked at the following I still am having no joy.
1) downloaded a correct csc file and using odin flashed it to my phone, however, it is still showing the same information as before.
2) Found a stock Rom. the exact same Rom as that which is installed, that has been flashed using Odin and once again, upon reboot the information is exactly the same.
Click to expand...
Click to collapse
Try installing this from the Android Market
https://play.google.com/store/apps/details?id=com.manniakk.cscselector&
Run it and update your CSC to your correct one
EDIT :- Just looked at your phone info in post 1 again, this relates to UK unbranded version so your CSC should be BTU
You shouldn't normally have a problem updating a rooted phone to newer versions provided the base rom is still stock I have never had a problem with mine but everyone is different I guess, I did mine via Kies then just re-rooted afterwards.
...well...
ag4751 said:
Try installing this from the Android Market
Run it and update your CSC to your correct one
Click to expand...
Click to collapse
Hi and thank you also...however, I have checked the sales code and it is properly installed and shown as being BTU, which is correct, this is shown of course by typing into the dial pad...et al ad nausea....whatever, it is correctly displayed, the issue is that when typing into the dial pad *#1234# in order to retrieve the information contained there, it is returning CSC UNKNOWN.
Greywolf907 said:
Hi and thank you also...however, I have checked the sales code and it is properly installed and shown as being BTU, which is correct, this is shown of course by typing into the dial pad...et al ad nausea....whatever, it is correctly displayed, the issue is that when typing into the dial pad *#1234# in order to retrieve the information contained there, it is returning CSC UNKNOWN.
Click to expand...
Click to collapse
OK you wrote this while I was writing my edit in the previous post.
Have you tried just installing the latest 4.1.1 BTU version using Odin you can get it from the Sammobile web site its the PDA version I9300XXDLJ4
http://www.sammobile.com/firmware/?page=3&model=GT-I9300&pcode=BTU&os=1&type=1#firmware
......not
ag4751 said:
OK you wrote this while I was writing my edit in the previous post.
Have you tried just installing the latest 4.1.1 BTU version using Odin you can get it from the Sammobile web site its the PDA version I9300XXDLJ4
....that version no........I did d/l and try this version
United Kingdom 8 Sep 2012 4.1.1 I9300XXBLG8 I9300XXDLI4 283.2 MB Download
which seemed to be relevant to my original build, this is the one that I have been having issues with.
I am also somewhat confused as to how to install the zip file via Odin, I more or less think that the pda file needs to be a single tar/md5 file and of course these things are coming as zips...well..at least the last one I d/l'd did.....
I am as I type sucking the file you suggest down and as soon as hotfile finishes dribbling it into my machine I'll give it a bash and let you know what happens.....many many thanks for taking the time to help me and do it with such good grace and civility, it's refreshing.
Cheers for now!
PS: I tried Kies, on three different machines, two running XP and one running Seven, each time it just doesnt want to know that the phone is even connected...ie. it knows its there, but just doesnt want to actually connect to it...just whirrs and clicks until I get fed up and unplug it....hence the grief I am having one way or another trying to update the O/S...so I can root it again!
Click to expand...
Click to collapse
I am also somewhat confused as to how to install the zip file via Odin, I more or less think that the pda file needs to be a single tar/md5 file and of course these things are coming as zips...well..at least the last one I d/l'd did.....
Click to expand...
Click to collapse
You need to extract the file located inside the zip file, then start Odin, click the PDA button and find the extracted file, put your phone in download mode, connect to your PC, wait for Odin to connect then start the update.
mucho...
ag4751 said:
You need to extract the file located inside the zip file, then start Odin, click the PDA button and find the extracted file, put your phone in download mode, connect to your PC, wait for Odin to connect then start the update.
Click to expand...
Click to collapse
yes I understand all that bit, I didn't make myself clear maybe....The problem I had was that the file I had downloaded seemed to be a zip file containing the whole system, i.e a cloned image, it didn't work...however, the link you so very helpfully provided was just waht i was looking for and couldn't find myself, a single tar/md5 file which has been downloaded, installed and is up and running....I now have JB, but still the csc is classified as unknown...anyhow, that doesn't matter much until the next time I need to update.
My very best regards to you and huge thanks.
have a good 'un
:good:
Got there eventually, strange abut the CSC
If you want to root your phone use this thread, 3rd post if you don't already have it
http://forum.xda-developers.com/showthread.php?t=1957273
Then install this for easy access to recovery
http://forum.xda-developers.com/showthread.php?t=1768142
Related
Seeing as I`m still a relatively noobish poster I`m unable to ask this question in the relevant thread. I`ve just debranded the phone following the 8 step guide but I had issues following step 8 where you change the CSC code. I couldnt quite figure it out so step 8 never got followed. As a result, despite losing the Three branding on the phone I now have a phone that displays the CSC as "unknown" and may well explain why Kies cannot pick up the firmware version on the phone. If I follow step 8 and key in *#272*<your IMEI># on my phone it then shows me a screen headed "Preconfig" with "Sales Code" underneath and "H3G" in the box to the right. Underneath is a radio button thats deselected. if I press to highlight it then press "install" at the bottom of the screen I keep getting an error saying "Must be THREE chars".
Can anyone shed any light on this and give me any hope of rectifying?
Will I need to manually input the Three APN settings once I successfuly change the CSC code?
Thanks in advance. I have spent ages scouring the web but there`s not a great deal of info out there about the CSC part of the debranding process.
id like some more info on how important the csc is too, im got told it hold some carrier information but i dont know if that is true or not.
the reason you cant pick on is probably as since debranding you havent flashed the csc you need, you could find the one you need for your firmware over in the dev section.
Cheers for the reply, interestingly i`ve just re-flashed the phone and this time it is showing my CSC as XEU. Even so, I still cannot follow step 8. When I input that code including my IMEI in it shows XEU but when I press "install" it gives me the same old error of "Must be THREE chars". So not sure whether its worked or not and what diference it makes. At least Kies now shows something in the firmware field, even if it doesnt show what I was expecting. Hopefully someone can assist with this at some point later.
RedAl said:
Cheers for the reply, interestingly i`ve just re-flashed the phone and this time it is showing my CSC as XEU. Even so, I still cannot follow step 8. When I input that code including my IMEI in it shows XEU but when I press "install" it gives me the same old error of "Must be THREE chars". So not sure whether its worked or not and what diference it makes. At least Kies now shows something in the firmware field, even if it doesnt show what I was expecting. Hopefully someone can assist with this at some point later.
Click to expand...
Click to collapse
Hi there
If it says XEU after inputting the imei then it's working fine. You're not supposed to have to press install at this stage. Also to make sure it's working fine, I always boot into recovery mode. If you look down the code as recovery is loading, it will say which csc is being used/implemented (xue etc). Always reset data in recovery after rom flash from (especially from different csc.
I've had issues in the past when I flashed back to T-Mobile (after originally flashing ke7 stock) and then back again to T-Mobile. When I re-flashed back to stock after this, I couldn't get it to change from tmu (t-mobile) csc back to xeu, no matter how I flashed it. In the end the only way I could revert csc back to xeu was using the jig I had purchased. Apart from resetting the customer binery counter, it seemed to reset other settings, as once I had done this, I was able to install stock ke7 with xeu csc.
redbullman said:
Hi there
If it says XEU after inputting the imei then it's working fine. You're not supposed to have to press install at this stage. Also to make sure it's working fine, I always boot into recovery mode. If you look down the code as recovery is loading, it will say which csc is being used/implemented (xue etc). Always reset data in recovery after rom flash from (especially from different csc.
I've had issues in the past when I flashed back to T-Mobile (after originally flashing ke7 stock) and then back again to T-Mobile. When I re-flashed back to stock after this, I couldn't get it to change from tmu (t-mobile) csc back to xeu, no matter how I flashed it. In the end the only way I could revert csc back to xeu was using the jig I had purchased. Apart from resetting the customer binery counter, it seemed to reset other settings, as once I had done this, I was able to install stock ke7 with xeu csc.
Click to expand...
Click to collapse
Cheers for that. I just did a recovery as you suggested and saw it was done using the Multi-CSC so hopefully that means its all sorted.
Does this mean I should now be able to see the latest Firmware update available in Kies?
RedAl said:
Cheers for that. I just did a recovery as you suggested and saw it was done using the Multi-CSC so hopefully that means its all sorted.
Does this mean I should now be able to see the latest Firmware update available in Kies?
Click to expand...
Click to collapse
Yes you should be able to see the latest available update for your csc via kies. Although kies seems much slower to get the updates. It's much easier to use Odin. Most people update by this method. It's really easy and pretty safe.
redbullman said:
Yes you should be able to see the latest available update for your csc via kies. Although kies seems much slower to get the updates. It's much easier to use Odin. Most people update by this method. It's really easy and pretty safe.
Click to expand...
Click to collapse
The csc will be sorted now. Also if you plug your phone into kies, this will confirm what csc you are using.
redbullman said:
The csc will be sorted now. Also if you plug your phone into kies, this will confirm what csc you are using.
Click to expand...
Click to collapse
Cheers Redbullman. I can get into Kies now but on the firmware information section it says "Current Firmware Version : PDA:KDD / PHONE:KDH / CSC:KD1 (H3G)"
Its not telling me there`s a firmware update available so I have a horrible feeling something`s still not quite right but I`ve flashed it twice now and done 2 factory resets.
Would it be easier to find the stock KE7 kernel (forgive me if I`m using the wrong words) in Odin to flash it that way? If I can manually do it then I`d rather do it that way. Only problem is I`ve not yet found any tutorials on doing that, unless its the same (mostly) as the tutorial for debranding, except using a different .tar file (KE7).
Hey everyone,
First post, n00b question - please be gentle.
First, I'll start with a positive. I have come from using an iPhone, and I was quiet comfortable with jailbreaking and cydia. I now have a Samsung Galaxy S 2 / II (GT-I9100T). I am from Australia, and on the Telstra network. Whoever is in the same boat would know it is quiet an adjustment, but you can root! (if you wanted to know).
I followed this persons 3 part guide and with sucess:
I cannot post the link but it is on YouTube and the video title is:
How To Root The Samsung Galaxy S II - Part 1
How To Root The Samsung Galaxy S II - Part 2
How To Root The Samsung Galaxy S II - Part 3
Username is mattj101101
I had Android 2.3.3 installed.
Second part is a question, is there any debranding roms / kernals that is ok for the GT-I9100T? I have tried the *#272*IMEI# but it only had 'Preconfig - TEL'
My phones info:
PDA: 19100TDVKF4
PHONE: I9100TDVKF2
CSC: I9100TTELFK3
My Kernal version, after the root is 2.6.35.7-I9100XWKDD-CL161513root<insertATsymbol>DELL103 #2
Hopefully with these answers I can help other fellow people out with this particular model (that are sold in Australia). Also if someone has the stock Telstra rom for re-flashing (if needed for warrenty) please point me in the right direction.
Thank-you.
Hey,
Ive got the GT-I9100T from Vodafone (both can run on the telstra bandwidth now ) and have had no issues flashing most roms. Only thing you may notice is the new modems aren't as good as the stock ones you currently have, so you may need to reflash the original modem through odin to get the best support.
Before you do flash though, make sure you back up your /efs folder, it contains the bin files for your IMEI for your phone, and people have reported flashing a rom can change that, so beware! also, before you do flash, try find the stock telstra rom for your phone incase you need to reflash. There are a few threads about it all, so good luck
The i9100T can use i9100 roms, but it will change the product code to i9100.
Easiest way to root is using CF-root, match the part of the version number in bold "PDA: 19100TDVKF4"
My phones info:
PDA: The rom/kernel
PHONE: The modem/radio, responsable for signal quality and speed, you dont need to match this to rom version, and the best way to find a good one is to test different ones.
CSC: APN settings and bundles apps, no need to match this, but if you do chose to all you may have todo is enter your APN settings for internet and MMS manually.
You can flash any rom onto any SGS2 via odin, see this guide, that will debrand etc.
Also, you rooted using a very old insecure kernel, people have had random reboots with that one, I suggest you flash back your stock kernel (you will keep root) or flash a version of cf-root (you will gain clockworkmod recovery, a way to flash roms/etc from your phone, and nandroid, a whole phone backup system, like snapshots)
I would recommend flashing DarkyRom2 on your S2. Runs fast, stable and great battery life. It roots your phone as well and changes your kernel to SuperCore which has a lot of optimisations.
Instructions:
Since you're not rooted (stock firmware/kernel)
1. Flash SuperCore_1.7.tar with Odin (put in PDA and do NOT tick repartition)
2. Get DarkyROM2 Tool and Superuser from market
3. Upload DarkyROM2_XXKH3_Base_R2.zip to SD-Card (INTERNAL)
4. Open DarkyROM2 tool. Accept SuperUser access request notification (this confirms you are rooted.
4. Under the DarkyRom tab, be sure "Wipe User data" is selected AND "INSTALL MODEM" is NOT SELECTED. (this will wipe everything from your phone but keep your stock KF4 modem. Any other modem causes signal problems for our I-9100T. )
5. No need to select "Install Kernel" Since SuperCore 1.7 is already installed.
5. Go back to the General Tab and use "Flash/Install File from SDCARD" to browse to and install DarkyROM2_XXKH3_Base_R2.zip
6. Wait for the phone to reboot and flash the new firmware
Get the files here:
http://www.darkyrom.com/community/index.php?threads/rom-cwm-sgs2-darkyrom2-kh3-base.4950/
I modified the instructions given on that link and posted it above for you since it's a little different for our I-9100T phones.
more info on I-9100T here:
http://forum.xda-developers.com/showpost.php?p=16824749&postcount=10
Interestingly, I just purchased a SGS2 here in Thailand (I'm also an Aussie) and the model of the phone is GT-I9100T.
Unfortunately I cannot seem to find a KL2 kernel for CF-Root to patch it with... any suggestions?
Also, the site that held all the OEM kernels (MultiUpload) for download is now showing a "Shut down by the FBI" logo : )
As long as you're certain you've got a I9100T, use the KL1 CFRoot kernel. Will work fine.
ApriliaM3 said:
Interestingly, I just purchased a SGS2 here in Thailand (I'm also an Aussie) and the model of the phone is GT-I9100T.
Unfortunately I cannot seem to find a KL2 kernel for CF-Root to patch it with... any suggestions?
Also, the site that held all the OEM kernels (MultiUpload) for download is now showing a "Shut down by the FBI" logo : )
Click to expand...
Click to collapse
My phone details are as follows:
Model: GT-I9100T
Android: 2.3.6
Baseband: I9100TDCKL1
Kernel: 2.6.35.7-I9100TDCKL2-CL767350 [email protected]#2
Build: GINGERBREAD.DCKL2
This is not an Aussie phone such as the Telstra I9100T that I see spoken about.
I purchased this phone here in Thailand 3 days ago and I have a few questions.
1. Is there a way to backup the original kernel before rooting?
2. Will the KL1 kernal make me lose things such as Thai language options etc?
3. Any way to restore the KL2 kernel in the future?
Thanks for taking the time to reply!
MistahBungle said:
As long as you're certain you've got a I9100T, use the KL1 CFRoot kernel. Will work fine.
Click to expand...
Click to collapse
1) Doubt it. And the only link for DCKL2/Thailand in Intra's official firmware thread is dead as it was MegaUpload, and he more than likely won't have a backup (you could always ask him tho). Search around elsewhere online, you might find a copy of this kernel somewhere.
2) I don't know for certain, but I don't think so. I would have thought something like language would be more firmware-related.
3) Refer to 1) I don't see why you'd need to ? In order to get warranty service from Samsung, all you'd need to do is flash the most recent firmware available for your phone (for all they know you could easily have got this from an OTA update via Kies), do a factory reset/make sure there's no apps left on your phone that could tip off whomever repairs it that the phone was rooted, and use a jig to reset the flash counter. Obviously there are no rolled gold guarantees with getting warranty service once you've voided same by rooting the phone/running non-stock firmware firmware on it, tho.
ApriliaM3 said:
My phone details are as follows:
Model: GT-I9100T
Android: 2.3.6
Baseband: I9100TDCKL1
Kernel: 2.6.35.7-I9100TDCKL2-CL767350 [email protected]#2
Build: GINGERBREAD.DCKL2
This is not an Aussie phone such as the Telstra I9100T that I see spoken about.
I purchased this phone here in Thailand 3 days ago and I have a few questions.
1. Is there a way to backup the original kernel before rooting?
2. Will the KL1 kernal make me lose things such as Thai language options etc?
3. Any way to restore the KL2 kernel in the future?
Thanks for taking the time to reply!
Click to expand...
Click to collapse
I was just worried it might stop future updates to ICS or similar via Kies.
At least I think I've managed to find another copy of the latest kernal on a site other than MegaUpload...
It's at 50% and counting : )
3) Refer to 1) I don't see why you'd need to ? In order to get warranty service
Running a CFRoot kernel over stock firmware should still allow you to receive OTA updates via Kies. If you find it doesn't, simply use Checkfus (search for it on here), it allows you to find/download the latest firmware for your phone/country that you'd normally get via Kies.
Really ? Cool Might wanna post a linky to your source over in Intra's thread. I'm sure there will be other people who might need it at some stage.
ApriliaM3 said:
I was just worried it might stop future updates to ICS or similar via Kies.
At least I think I've managed to find another copy of the latest kernal on a site other than MegaUpload...
It's at 50% and counting : )
3) Refer to 1) I don't see why you'd need to ? In order to get warranty service
Click to expand...
Click to collapse
Ok so would you believe...
I ran the guide from Intra.
Installed an insecure ROM and then ran SuperOneClick and was rooted.
I restored the OEM kernel that I found online and BINGO - UNROOTED!
I repeated the procedure just to check everything again... same deal!
Phone is currently unrooted again...
MistahBungle said:
Running a CFRoot kernel over stock firmware should still allow you to receive OTA updates via Kies. If you find it doesn't, simply use Checkfus (search for it on here), it allows you to find/download the latest firmware for your phone/country that you'd normally get via Kies.
Really ? Cool Might wanna post a linky to your source over in Intra's thread. I'm sure there will be other people who might need it at some stage.
Click to expand...
Click to collapse
Yeah, if you flash an original (unrooted) kernel over your rooted kernel you'll lose root.
There's a procedure for removing the yellow warning triangle at boot in the CFRoot thread & also retaining root, but I found it too fiddly when I first rooted my phone so I simply bought a jig & did it that way.
I can't speak for anything to do with SuperOneClick as I've never used it.
ApriliaM3 said:
Ok so would you believe...
I ran the guide from Intra.
Installed an insecure ROM and then ran SuperOneClick and was rooted.
I restored the OEM kernel that I found online and BINGO - UNROOTED!
I repeated the procedure just to check everything again... same deal!
Phone is currently unrooted again...
Click to expand...
Click to collapse
Apparently so... now I'm confused about what the guide was trying to achieve.
Also, Kies now tells me it's not compatible with my device... Perfect!
MistahBungle said:
Yeah, if you flash an original (unrooted) kernel over your rooted kernel you'll lose root.
QUOTE]
Click to expand...
Click to collapse
As I said, I have no idea whatsoever about anything to do with SuperOneClick. If you want a rooted phone minus the yellow warning triangle at boot without fiddling around, root it with a CFRoot kernel, buy a $3 jig from eBay, done.
So far as Kies not working, you could try uninstalling/reinstalling Kies, or simply use Checkfus as I've said previously. Me, I'd use Checkfus. Quick, easy & like the paragraph above, no fiddling around.
Edit to add - Yes, obviously Kies won't work if you're running an "insecure rom" as per your post above. I presume you mean a custom rom you found somewhere on here or elsewhere ? One of my earlier posts did say Kies should (not always) work if you're running a rooted kernel over a stock Samsung rom. If you're running a non-stock rom Kies won't work.
ApriliaM3 said:
Apparently so... now I'm confused about what the guide was trying to achieve.
Also, Kies now tells me it's not compatible with my device... Perfect!
Click to expand...
Click to collapse
ApriliaM3 said:
Apparently so... now I'm confused about what the guide was trying to achieve.
Also, Kies now tells me it's not compatible with my device... Perfect!
MistahBungle said:
Yeah, if you flash an original (unrooted) kernel over your rooted kernel you'll lose root.
QUOTE]
Click to expand...
Click to collapse
Ditch Kies there is a better alternative out there. MyphoneExplore, do a seach via google. You'll also need to get the app client software from the android market. I use it to synch my work Outlook Calendar to my phone. You can also back up your contacts, sms and call records.
Click to expand...
Click to collapse
Edit: I tried CF-Root KL3 (wanted KL2) and it seems fine so far.
I have root and everything else seems the same (Thai language support etc.)
I'll keep you posted : )
Thanks for taking the time to deal with my issues!
Hope I can do the same for some others on this Forum in the future.
I'd not heard of Checkfus so I'll give that a try, thanks : )
There's no CF-Root to match my phone exactly but I guess there's nothing to lose now by trying something close : P
I ordered the jig almost a week before getting the phone but it seems the postage to Thailand is sloooow.
I'm running a stock ROM and unrooted but Kies is still misbehaving.
MistahBungle said:
As I said, I have no idea whatsoever about anything to do with SuperOneClick. If you want a rooted phone minus the yellow warning triangle at boot without fiddling around, root it with a CFRoot kernel, buy a $3 jig from eBay, done.
So far as Kies not working, you could try uninstalling/reinstalling Kies, or simply use Checkfus as I've said previously. Me, I'd use Checkfus. Quick, easy & like the paragraph above, no fiddling around.
Edit to add - Yes, obviously Kies won't work if you're running an "insecure rom" as per your post above. I presume you mean a custom rom you found somewhere on here or elsewhere ? One of my earlier posts did say Kies should (not always) work if you're running a rooted kernel over a stock Samsung rom. If you're running a non-stock rom Kies won't work.
Click to expand...
Click to collapse
Something may have borked so far as the CSC goes (which tells Kies, the Market, etc where you are). I did say you should be able to use Kies, you're not the first person to have problems with it after rooting
Personally speaking, I've never used Kies & almost certainly won't use it. Ever. Custom roms/kernels are a piece of you know what to flash via CWRecovery (or Odin for that matter), and official firmware updates are easy to get with Checkfus & flash via Odin if I ever have to go down that path for warranty purposes or whatever.
Kies is a truly awful piece of software
Edit to add after your edit - No worries
ApriliaM3 said:
I'd not heard of Checkfus so I'll give that a try, thanks : )
I'm running a stock ROM and unrooted but Kies is still misbehaving.
Click to expand...
Click to collapse
Yeah Kies is dodgy...
When I got home I plugged it into Kies on the home PC and everything was fine!
Have you experimented much with any Custom ROM's?
MistahBungle said:
Something may have borked so far as the CSC goes (which tells Kies, the Market, etc where you are). I did say you should be able to use Kies, you're not the first person to have problems with it after rooting
Kies is a truly awful piece of software
Click to expand...
Click to collapse
I installed CSC_XEU_I9100XEUKH2 after i noticed Kies said my CSC was KI3 (KOR) and not XEU. Kies still says this however.
Under phone settings I can see Baseband and kernel and build. They are all XXKI3.
Why does kies show my csc as KOR? Did the CSC file not install properly?
Look her for your csc code.
codes.docx
Hmmm.. that document doesn't even list KOR. I would have thought it was Korea. TBH I think my phone first showed KOR in Kies after I put nimphetamine kernel on it. I just don't understand why subsequent flashes leave it still saying KOR. I would have thought it would now be back XEU like it was at first.
I am trying to fix a bluetooth car problem (another thread) and don't want to be wasting my time flashing what I think is different software if it isn't flashing properly.
I really understood my HD2 but I'm still climbing a steep learning curve with this phone.
Also in another thread someone posted a screen capture and it was title version. It listed PDA, phone and CSC. I can't seem to find this screen. See 1st post here:
http://forum.xda-developers.com/showthread.php?t=1169338
You can change the CSC code to anything you want.
Just flashed clockwork mod. Now Kies shows CSC KH2 (KOR).
Where did KOR come from and how do you change it? Why does flashing an XEU CSC not return it?
Dexter_Morgan said:
Hmmm.. that document doesn't even list KOR. I would have thought it was Korea. TBH I think my phone first showed KOR in Kies after I put nimphetamine kernel on it. I just don't understand why subsequent flashes leave it still saying KOR. I would have thought it would now be back XEU like it was at first.
I am trying to fix a bluetooth car problem (another thread) and don't want to be wasting my time flashing what I think is different software if it isn't flashing properly.
I really understood my HD2 but I'm still climbing a steep learning curve with this phone.
Also in another thread someone posted a screen capture and it was title version. It listed PDA, phone and CSC. I can't seem to find this screen. See 1st post here:
http://forum.xda-developers.com/showthread.php?t=1169338
Click to expand...
Click to collapse
*#06# gives your IMEI number
*#272*IMEI# gives the CSC Code (!!!!!!!!!!!If you change the CSC code you'll get a factory reset !!!!!!!!!!!!)
*#1234# gives the CSC version
Nitrality from Market does this all for you.
Cheers. that 1234 gave me that version screen. under this csc is listed as xeu.
Can someone explain what flashing clockwork mod changes. is this another csc or does it just modify the one you have to give a new recovery menu. i also seem to still have root after flashing clockwork despite the saying it would be gone.
Dexter_Morgan said:
Cheers. that 1234 gave me that version screen. under this csc is listed as xeu.
Can someone explain what flashing clockwork mod changes. is this another csc or does it just modify the one you have to give a new recovery menu. i also seem to still have root after flashing clockwork despite the saying it would be gone.
Click to expand...
Click to collapse
Guide
http://forum.xda-developers.com/showthread.php?t=1125282
Clockworkmod is a 'custom recovery' made by xda member koush. Every phone had a recovery partition designed so that if the user messes up a ROM installation, they can recover their phone. CWM is a modified recovery installed into the recovery partition that allows advanced control over ROM recovery, installation and much more.
Features of CWM include:
- NANDroid Backup, This allows you to completely back up your existing ROM with all its files, data and apps
- Restore Backup, Restores a previous backup (obviously...)
- ROM installation, Allows you to install a ROM contained inside a flashable .zip file
- Wipe data/Factory reset, completely erases all of your data contacts, apps etc, leaving your phone 'as new'
Amongst others...
How to install CWM
If you have already rooted your phone using the CF-root Kernel, then you already have CWM! If not, then just install the kernel linked to above in the 'how to root your phone' section
AP: I9505XXUAMDM
CP: I9505XXUAMDM
CSC: I9505OXXAMDB
Can somebody please tell me what my region is? I purchased it through handtec.co.uk sim free unlocked. wondering ever since why it isn't showing BTU
Or is it that this information itself is BTU??
When I read in various forums, I read that many have the ability to update their phone to 2.3.5. I'm still running with 2.3.3 and examine every day there's a new update. I connect my phone to Kies or I put the phone to see whether there is a software update - but no.
What is it that makes some can update and others can not?
My phone was purchased without subscription to any mobile operator.
Short answer:
KIES is crap.
Slightly longer answer:
For some reason this software is unreliable. I had exactly the same problem when I wanted to flash a stock rom back on my phone. I got the oldest one available on the Web and wanted to update it using KIES. But it didn't work.
My suggestion:
Find the update you're waiting for here on xda and flash it with Odin.
Sent from my GT-I9100 using XDA App
Is it equally safe to use Odin, and how do I ensure that it is the real "file" I use -
If you follow the instructions it works safely. The best is to compare the screenshot on the thread with your actual window before flashing. Odin has some features you don't want to use like the "pit-file". However it's said multiple times that you should never flash it unless strictly told to do so, what stock firmwares don't.
So just check everything twice and you're good to go.
You know whether you have the right update if you have a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1075278
So unless you live in India, a firmware with the Indian letter-code is wrong for you.
Just get the most recent, official one available for you region, read the instructions carefully and forget about KIES. KIES needs longer to recognize my phone than Odin needs to update it. I think that reason is enough to uninstall KIES and use Odin instead.
Sent from my GT-I9100 using XDA App
+1 forget upgrading with keis. Go with Odin and intratechs firmware.
Sent from my GT-I9100 using XDA App
How to Upadate
a site www.sammobile.com has all the latest official ROMs for all the Samsung phones. These ROMs do not require rooting or anything. Though these are "official" they might not be perfect by they offer the latest Samsung has to offer.
I never update with Kies. Learn to use Odin. Usually, the ROMs on www.sammobile.com have the appropriate version of ODIN attached as well as any PIT file that is necessary.
Spend some time learning how to flash with ODIN. I've flashed both my Samsung phones 10s of times with no problem whatsoever.
The great thing about buying an international version of the Samsung phones is that there are software updates at least monthly and sometimes twice a month (posted on sammobile.
Samsung got a bad rap for being slow to update it's software a couple years ago. That has changed. I consider them the best now and buy Samsung Phones over HTC primarly for this reason.
I have install "Android CSC Select" and the only one I can see is "XEF", is this because I have en international firmware in my phone right now ?
I'm from Denmark sow why can't I see the NEE for scandinavian ?
I am very unsure about which file I need when I update with "odin" ..
Is there a good and safe program that allowsme to take a backup of the firmware I have now so I can use if all goes wrong?
stonefox said:
I have install "Android CSC Select" and the only one I can see is "XEF", is this because I have en international firmware in my phone right now ?
I'm from Denmark sow why can't I see the NEE for scandinavian ?
I am very unsure about which file I need when I update with "odin" ..
Is there a good and safe program that allowsme to take a backup of the firmware I have now so I can use if all goes wrong?
Click to expand...
Click to collapse
There are, but they require root-permissions to run.
As for the firmware. Take a look at your system information, at which firmware you have installed right now.
Sent from my GT-I9100 using XDA App
I am very unsure about which file I need when I update with "odin" ..
Maybe there is one here who can help to find out which file I shall download - look at the 2 screensdump I've attached
http://gupl.dk/668019/
http://gupl.dk/668020/
http://gupl.dk/668021/
I took the time to install and test both firmwares (the one you have right now and the one I think to be the proper one for you now) on my Phone.
Worked nicely.
Here is what firmware I took and why:
Your "Baseband Version" is:
I9100XXKG1
Your "Kernel Version" is:
blah....I9100XWKG1...blah
And your "Sales Code" is:
XEF
This is the following firmware on Intratech's thread:
XWKG1
Firmware info
PDA:XWKG1
PHONE: XXKG1
Date: 05/07/2011
Android 2.3.3
XEF (France): "Downloadlink you would use..."
Click to expand...
Click to collapse
The updated firmware is this one:
XWKJ1
Android 2.3.5
This package has: PDA: XWKJ1| Modem/phone: XXKI3| CSC: XEUKH2
Download: "Downloadlink for the first file"
Click to expand...
Click to collapse
Note that it has the "XEU" Sales Code instead of the "XEF" Sales Code.
However, if you scroll down you can see:
Individual CSC Packages
...blah
XEF CSC (XEFKE2): "Downloadlink for the second file..."
Click to expand...
Click to collapse
So what you do is:
Download the first file (.exe ~ 276mb)
Download the second file (.exe ~ 14,9mb)
Extract them both (you get a ~ 539mb .tar.md5 and a ~ 33mb .tar file)
Make sure KIES does not run (not in the tray as well)
Put your Galaxy S2 in download mode and confirm that you know what you're doing
Start Odin and connect your phone
Click on "PDA" and select the ~ 539 mb ".tar.md5"-file
Click on "CSC" and select the ~ 33 mb ".tar"-file
Make sure that only the following 4 checkboxes are checked (Auto Reboot; F. Reset Time; PDA, CSC)
Wait until "ID:COM" has an entry and becomes yellow (entry like: 0:[COM12])
Click on "Start" and wait untill it finishes
Disconnect your phone once it reboots
Report back if it works
The links to the 2 files I should download does not work.
What is the reason that I also need to install a CSC file (I'm just curious)? and the files you reference makes it possible to run my phone in Danish?
You find them in Intratech's thread I posted earlier.
http://forum.xda-developers.com/showthread.php?t=1075278
The CSC is the contry specific code and contains info for your mobile network. To keep it simple, just flash both. Otherwise you'd have to set up your mobile network manually.
PS:
I ran both firmwares on danish when I tested them.
First file:
http://www.multiupload.com/QYQLC8KGJ8
Second file:
http://www.multiupload.com/1TCEUGSFKA
Before I start I would like to hear whether you use a backup program that makes it easy to restore programs and settings after the opdate ?
You don't need to wipe data (at least I didn't and the settings weren't reset). So you shouldn't have any problems. You're not flashing an entirely different rom, just an updated version of the same.
I don't know, doesn't KIES have some sort of backup function? Besides that your contacts, calender and google-mail can be synced with your google-account.
Anyway, if you want proper backups, you'll need to root you phone.
Sent from my GT-I9100 using XDA App
Thank for your help - Every work and look fine .
Hmm i might give this a go later... wasn't going to root this phone i got too addicted with my desire so this could satisfy my urge to update constantly...
I will prob root at some stage
Hi all,
I have the SM-N9005 Galaxy Note 3 (Snapdragon) running android 4.4.2. I had a bit of a **** up the other day and finally managed to get my phone booting again. My issue now is that I can't seem to root my phone at all.
A copy of SuperSU was installed (by a failed CF-Auto-Root while trying to fix my device), but wouldn't run when I tried it. I've now tried to root the device by:
CF-Auto-Root - Runs smoothly but still no root
Towelroot - Device not supported message
CWM -> Install via zip - Says it worked but root unsuccessful
Kingo - Failed to root
I've tried multiple things now but no matter what I do, the final result will be a device that isn't rooted even if whatever rooting method says it was successful. I also can't run apps that won't run on rooted devices because they think my device is rooted (not sure if this is knox? mine has been tripped).
Anyone have any idea?
Try root genius it works
Downloaded root genius, ran it, everything went perfect and it said "Gratz".
Still no root according to root checker and Xposed. I have Kinguser installed now too which says root access is "ON".
Sidalol said:
Downloaded root genius, ran it, everything went perfect and it said "Gratz".
Still no root according to root checker and Xposed. I have Kinguser installed now too which says root access is "ON".
Click to expand...
Click to collapse
Anyone giving you advice on how to root without knowing your build version of the software you are currently using shouldn't be trying to "help". Since you have not had any success and having leftover apps / files that you can't delete without root means you should reinstall the stock operating system via Odin and restart the process. You absolutely need to be aware of the build version - just saying I have 4.3 or 4.4.2 installed is not enough information and the methods can vary depending on that and even, sometimes, via carrier or region.
es0tericcha0s said:
Anyone giving you advice on how to root without knowing your build version of the software you are currently using shouldn't be trying to "help". Since you have not had any success and having leftover apps / files that you can't delete without root means you should reinstall the stock operating system via Odin and restart the process. You absolutely need to be aware of the build version - just saying I have 4.3 or 4.4.2 installed is not enough information and the methods can vary depending on that and even, sometimes, via carrier or region.
Click to expand...
Click to collapse
Oh man that's how I broke it the first time. I didn't realise I needed version numbers etc, I simply followed te "how to unroot galaxy note 3" guide on galaxynote3root. The guide looked simple enough and linked me to the SM-N9005 firmware so I just followed the instructions. The flash failed in ODIN, phone wouldn't boot, and I was stuck in this mess of trying to learn about all these different ways of flashing with no idea what my version numbers were as I couldn't boot the phone.
After trying to flash all kinds of versions on to it (didn't really have much choice) I luckily stumbled across an old cwm backup, so I got cwm and restored that backup. Turns out it was a backup I did for my ex's phone (also Galaxy Note 3 but from Bulgaria, no idea which model, mine is from UK). I reset factory settings and that's where I am now.
If I post my version numbers here could you show me where to find the right files for Odin? I really had such a hard time trying to figure out what the hell was what with the million different firmware versions...
Model Number: SM-N9005
Android Version: 4.4.2
Baseband Version: N9005ZHUENE2
Kernel Version: 3.4.0-1955971
Build Number: KOT49H.N9005XXUGNG1
SE for Android Status: Enforcing
Security Software Version: MDF v1.0 Release 3
Edit: Been looking at firmware on sammobile and there's multiple versions of stock for N9005XXUGNG1 in all different languages, the difference is the CSC code however there isn't one for mine (mine seems to be from hong kong or something), does the CSC matter or can I download the United Kingdom N9005XXUGNG1 and flash that regardless of matchng CSC? Or can I fix my CSC? :/
Could someone move this thread to http://forum.xda-developers.com/galaxy-note-3/help please I think it would be a better place.
Sidalol said:
Oh man that's how I broke it the first time. I didn't realise I needed version numbers etc, I simply followed te "how to unroot galaxy note 3" guide on galaxynote3root. The guide looked simple enough and linked me to the SM-N9005 firmware so I just followed the instructions. The flash failed in ODIN, phone wouldn't boot, and I was stuck in this mess of trying to learn about all these different ways of flashing with no idea what my version numbers were as I couldn't boot the phone.
After trying to flash all kinds of versions on to it (didn't really have much choice) I luckily stumbled across an old cwm backup, so I got cwm and restored that backup. Turns out it was a backup I did for my ex's phone (also Galaxy Note 3 but from Bulgaria, no idea which model, mine is from UK). I reset factory settings and that's where I am now.
If I post my version numbers here could you show me where to find the right files for Odin? I really had such a hard time trying to figure out what the hell was what with the million different firmware versions...
Model Number: SM-N9005
Android Version: 4.4.2
Baseband Version: N9005ZHUENE2
Kernel Version: 3.4.0-1955971
Build Number: KOT49H.N9005XXUGNG1
SE for Android Status: Enforcing
Security Software Version: MDF v1.0 Release 3
Edit: Been looking at firmware on sammobile and there's multiple versions of stock for N9005XXUGNG1 in all different languages, the difference is the CSC code however there isn't one for mine (mine seems to be from hong kong or something), does the CSC matter or can I download the United Kingdom N9005XXUGNG1 and flash that regardless of matchng CSC? Or can I fix my CSC? :/
Click to expand...
Click to collapse
Yea, it does get a little tricky since there are so many different versions of the software for Samsungs like these that are world phones. So your Build Number suggests that it's the version for the UK firmware, yet the baseband is from the Hong Kong region. You mentioned that the Odin install failed so I wouldn't think that the baseband had been changed, suggesting that originally it was an HK phone. With most of the unlocked non-carrier specific Note 3s, you should be able to install the official firmwares from whichever region, though there might be differences in service from the modem/baseband version or apps and languages specific to that region, but these problems should be easily solveable. I think I would try this one: http://www.sammobile.com/firmwares/download/38070/N9005XXUGNG1_N9005OXAGNJ3_BTU.zip/ This is the unbranded version for the UK region.
http://www.cpkb.org/wiki/Samsung_firmware_naming_conventions#2._Region_code
http://forum.xda-developers.com/showthread.php?t=2666907
Another thing I was thinking...you obviously have a custom recovery if you restored your gf's backup and tried to install SU that way...why not just pick a custom rom which is already rooted and could contain other fun / useful mods?
es0tericcha0s said:
Yea, it does get a little tricky since there are so many different versions of the software for Samsungs like these that are world phones. So your Build Number suggests that it's the version for the UK firmware, yet the baseband is from the Hong Kong region. You mentioned that the Odin install failed so I wouldn't think that the baseband had been changed, suggesting that originally it was an HK phone. With most of the unlocked non-carrier specific Note 3s, you should be able to install the official firmwares from whichever region, though there might be differences in service from the modem/baseband version or apps and languages specific to that region, but these problems should be easily solveable. I think I would try this one: http://www.sammobile.com/firmwares/download/38070/N9005XXUGNG1_N9005OXAGNJ3_BTU.zip/ This is the unbranded version for the UK region.
http://www.cpkb.org/wiki/Samsung_firmware_naming_conventions#2._Region_code
http://forum.xda-developers.com/showthread.php?t=2666907
Another thing I was thinking...you obviously have a custom recovery if you restored your gf's backup and tried to install SU that way...why not just pick a custom rom which is already rooted and could contain other fun / useful mods?
Click to expand...
Click to collapse
Thanks so much. Do I have to download one of the CSC files from the bottom link to use at the same time in Odin? I want to reset everything back to stock first as it feels pretty screwed atm but afterwards is there any custom rom you recommend for note 3?
Sidalol said:
Thanks so much. Do I have to download one of the CSC files from the bottom link to use at the same time in Odin? I want to reset everything back to stock first as it feels pretty screwed atm but afterwards is there any custom rom you recommend for note 3?
Click to expand...
Click to collapse
No, the full firmware flash has the CSC built in, I just provided the other link for further info. As far as roms, I can't really say. I mod phones for people as part hobby / extra money and don't see the international version often enough to know the roms that well as I tend to just get the carrier specific ones to work on. Now that Lollipop is out for it, looks like there are a lot more choices which we don't have here in the US yet. Just think about what you want to focus on (battery life, mods, stability, etc) and read through the reviews to see if people are experiencing good things. I personally don't care for Touchwiz and the Samsung devices I've owned, I just jump straight to something CM based, but it's not for everyone and you might lose some functionality in some respects (some S-Pen features) and gain it in other places (ability to mod almost everything, slimmer, no bloat, etc) For my customers though, I almost always recommend something stock based as there tends to be less of a learning curve and thus less issues I have to help people navigate through.
es0tericcha0s said:
No, the full firmware flash has the CSC built in, I just provided the other link for further info. As far as roms, I can't really say. I mod phones for people as part hobby / extra money and don't see the international version often enough to know the roms that well as I tend to just get the carrier specific ones to work on. Now that Lollipop is out for it, looks like there are a lot more choices which we don't have here in the US yet. Just think about what you want to focus on (battery life, mods, stability, etc) and read through the reviews to see if people are experiencing good things. I personally don't care for Touchwiz and the Samsung devices I've owned, I just jump straight to something CM based, but it's not for everyone and you might lose some functionality in some respects (some S-Pen features) and gain it in other places (ability to mod almost everything, slimmer, no bloat, etc) For my customers though, I almost always recommend something stock based as there tends to be less of a learning curve and thus less issues I have to help people navigate through.
Click to expand...
Click to collapse
Crap, just tried to load that one...same problem I had the first time round. It gets to "system.img.ext4" then fails. My phone will stay on the downloading screen now until I reboot it then I probably can't boot
Phone shows:
UDC START
ODIN: Invalid ext4 image
Odin shows:
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Edit: Yeah I get "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". Won't work in Kies though it'll say unsupported version.
Edit 2: Tried again with a different cable (official samsung also) and different usb port, same result. Also ran files from desktop instead of usb this time but didn't help.
Sidalol said:
Crap, just tried to load that one...same problem I had the first time round. It gets to "system.img.ext4" then fails. My phone will stay on the downloading screen now until I reboot it then I probably can't boot
Phone shows:
UDC START
ODIN: Invalid ext4 image
Odin shows:
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Edit: Yeah I get "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". Won't work in Kies though it'll say unsupported version.
Click to expand...
Click to collapse
That' s really odd... Maybe try the HK version then, matching the baseband version you have. Sucks that all the links are so darn slow. You might want to spring for the premium Sammobile account to expedite the process. They have a week membership for 5 pounds and should provide a significant increase in download speeds if you need to get your phone back up in a hurry.
You might try the Emergency mode in Kies to described here: http://www.samsung.com/us/support/faq/FAQ00059169/81100 to see if that helps anything.
es0tericcha0s said:
That' s really odd... Maybe try the HK version then, matching the baseband version you have. Sucks that all the links are so darn slow. You might want to spring for the premium Sammobile account to expediate the process. They have a week membership for 5 pounds and should provide a significant increase in download speeds if you need to get your phone back up in a hurry.
Click to expand...
Click to collapse
I already got the week membership 2 days ago when I was trying this the first time Downloads were going to take 6 hours each and I'd already signed up to like 5 other sites (free) which all turned out useless anyway lol. Will try the HK one now (http://www.sammobile.com/firmwares/download/29373/N9005ZHUENE3_N9005ZZHENE3_TGY.zip/) Hope it's right
Sidalol said:
I already got the week membership 2 days ago when I was trying this the first time Will try the HK one now (http://www.sammobile.com/firmwares/download/29373/N9005ZHUENE3_N9005ZZHENE3_TGY.zip/) Hope it's right
Click to expand...
Click to collapse
Won't make it any worse.
es0tericcha0s said:
Won't make it any worse.
Click to expand...
Click to collapse
Well damn it actually worked! Something is wrong through because apps are crashing and constantly spamming error boxes making it unusable...would it be some compatability thing with it being the kong kong firmware and me in uk? Don't know if it matters whether it's the hong kong one.
"Unfortunately, the process android.process.acore has stopped."
endless spam.
Edit: Ok I reset factory settings and now it works but it's in chinese. If I simply change the language to english is that it? It's the same as having everything back at stock and will work fine in uk? Or can I change to a proper uk stock?
Sidalol said:
Well damn it actually worked! Something is wrong through because apps are crashing and constantly spamming error boxes making it unusable...would it be some compatability thing with it being the kong kong firmware and me in uk? Don't know if it matters whether it's the hong kong one.
"Unfortunately, the process android.process.acore has stopped."
endless spam.
Edit: Ok I reset factory settings and now it works but it's in chinese. If I simply change the language to english is that it? It's the same as having everything back at stock and will work fine in uk? Or can I change to a proper uk stock?
Click to expand...
Click to collapse
That should be it. You have the same baseband with this version as you had so you should not notice any difference in service or the like. I WAS going to suggest the HK version first but you said you got it in the UK so thought it should work that way. Sorry!
es0tericcha0s said:
That should be it. You have the same baseband with this version as you had so you should not notice any difference in service or the like. I WAS going to suggest the HK version first but you said you got it in the UK so thought it should work that way. Sorry!
Click to expand...
Click to collapse
Thanks so much man, this was driving me mad for a few days. One final thing if you don't mind, it's offering me a samsung update to the firmware, it says it's for VoLTE support and after updating the firmware I will be unable to downgrade due to the security policy. Is it fine to update or will it interfere with things in future like using a custom rom?
Thanks again really.
Sidalol said:
Thanks so much man, this was driving me mad for a few days. One final thing if you don't mind, it's offering me a samsung update to the firmware, it says it's for VoLTE support and after updating the firmware I will be unable to downgrade due to the security policy. Is it fine to update or will it interfere with things in future like using a custom rom?
Thanks again really.
Click to expand...
Click to collapse
My pleasure. I know how frustrating these things can be and I have a crazy amount of experience with this kind of stuff. You shouldn't have an issue with the update or doing custom things afterwards as the bootloader on that model is not locked, so you would still be able to install a custom recovery and custom rom, if you would like. If it's the 5.0 update, then you might have trouble using KK roms and you definitely can't go back to official 4.4.4 at that point, but it's probably just a minor update for the modem and not the full 5.0 update yet.