Can someone confirm that TA works on EMC2?
I'm trying to return completely to stock including resetting flash counter and getting rid of that red exclamation mark and so I'm guessing TA is the route?
Also, I remember reading that CSC changer no longer works? - is there a way around this yet? The last time I flashed stock via Odin I ended up with KOR when I needed BTU so i didn't get OTA until afterwards
My only thought if this doesn't work would be to revert back to the ICS bootloader?
Thanks in Advance!
Tom
Related
My phone was bought originally with salescode(CSC) NEE. Now I have replaced ROM with stock XEU, wiped, reset to fabric etc.
But when I boot Android recovery, sound button up, Home key and Power it says:
Applying Multi-CSC
Installing Multi-CSC
Can't access to '/system/csc/XEU/system/'
Suceccfully applied multi-SCS.
This message happens every time.
Rembember the phone was original NEE and I flashed an original XEU rom.
It seems that the ROM-flashing doesn't completely do what I expected. When I flash a stock NEE rom the "can't access..." is gone, probably because it's the original NEE as the phone was bought with.
Anyone have a solution to get rid of this "can't access.." message? Or do I have to root it to get it fixed. (I'm sending the phone back to Samsung for repair, in another country where I bought it)
nilste said:
My phone was bought originally with salescode(CSC) NEE. Now I have replaced ROM with stock XEU, wiped, reset to fabric etc.
But when I boot Android recovery, sound button up, Home key and Power it says:
Applying Multi-CSC
Installing Multi-CSC
Can't access to '/system/csc/XEU/system/'
Suceccfully applied multi-SCS.
This message happens every time.
Rembember the phone was original NEE and I flashed an original XEU rom.
It seems that the ROM-flashing doesn't completely do what I expected. When I flash a stock NEE rom the "can't access..." is gone, probably because it's the original NEE as the phone was bought with.
Anyone have a solution to get rid of this "can't access.." message? Or do I have to root it to get it fixed. (I'm sending the phone back to Samsung for repair, in another country where I bought it)
Click to expand...
Click to collapse
If you root phone you void warranty .
jje
JJEgan said:
If you root phone you void warranty .
jje
Click to expand...
Click to collapse
I know.
But I was thinking of rooting, fix this, and unroot. But how to fix?
Flash a different stock rom.
jje
Hi all I've been on this for a while, since the weekend looked at a serious amount of posts and guides on rooting and unrooting but I'm no further forward.
The problem I have is I wanted to upgrade from gingerbread to ics so I could eventually put the latest cyanogen mod on my phone. I rooted the phone no problem there flashed an insecure kernel with odin 1.85 as per the instructions from one of the guides got the CWM and superuser apps then flashed the original back, got rid of the yellow triangle every thing good so far. I did this coz I expected I had to, to put cyanogenmod on my phone.
Samsung kies says there is a update to ICS but every time I try to update it fails. Try using Odin with a stock mod and it fails. I rang Samsung and they say my build number is the up to date version. One of my colleagues has an older sgs2 and he managed to update his no problem with kies. I'm wondering if there is a problem with my phone preventing it from being updated? Also every time a look at a post or a guide it seems like that post is specific to a particular android version and I can't find one that is specific to mine such as carrier Orange, gingerbread2.3.3 as I think it's too old. PDA I9100BVKH2.
Now I'm thinking I might just try unrooting it and take it to orange and get them to update it but uprooting it to stock seems to be a pain, I need to get rid of that doing flash counter.
Do I need to go to orange or is this easy to update and I'm just missing something. Before I get flamed I did search not just here but all over the Internet to find a reason why I couldn't update but didn't get a definitive answer.
Dodgeyhodgeyuk said:
Hi all I've been on this for a while, since the weekend looked at a serious amount of posts and guides on rooting and unrooting but I'm no further forward.
The problem I have is I wanted to upgrade from gingerbread to ics so I could eventually put the latest cyanogen mod on my phone. I rooted the phone no problem there flashed an insecure kernel with odin 1.85 as per the instructions from one of the guides got the CWM and superuser apps then flashed the original back, got rid of the yellow triangle every thing good so far. I did this coz I expected I had to, to put cyanogenmod on my phone.
Samsung kies says there is a update to ICS but every time I try to update it fails. Try using Odin with a stock mod and it fails. I rang Samsung and they say my build number is the up to date version. One of my colleagues has an older sgs2 and he managed to update his no problem with kies. I'm wondering if there is a problem with my phone preventing it from being updated? Also every time a look at a post or a guide it seems like that post is specific to a particular android version and I can't find one that is specific to mine such as carrier Orange, gingerbread2.3.3 as I think it's too old. PDA I9100BVKH2.
Now I'm thinking I might just try unrooting it and take it to orange and get them to update it but uprooting it to stock seems to be a pain, I need to get rid of that doing flash counter.
Do I need to go to orange or is this easy to update and I'm just missing something. Before I get flamed I did search not just here but all over the Internet to find a reason why I couldn't update but didn't get a definitive answer.
Click to expand...
Click to collapse
There are two ways to do this:
1. Update the phone to ICS on your own.
- Visit Sammobile
- Download the firmware for your country/carrier
- Extract the zip file.
- Flash the firmware via odin
- Boot to recovery and perform a factory reset.
done.
2. Reset your binary counter and take it to Orange!
- you can use USB jig to reset your counter.
or
- Flash a Samsung based custom rom via CWM recovery,
- Download Triangle away app by Chainfire
- Use Triangle away app, to reset your binary counter
- flash back your Stock ROM (you can also get it from Sammobile if you dont have a copy)
- take your phone to Orange.
done.
cheers
OK thanks for your help. will give it a go.
You dont need kies or orange-this is why your getting confused.You could go to sammobile and get an unbranded ics for your region/model,and to be "safe",go for 4.0.3.
Then you can flash like siyah kernel,make a nand backup,and efs backup then install whatever rom you want.
theunderling said:
You dont need kies or orange-this is why your getting confused.You could go to sammobile and get an unbranded ics for your region/model,and to be "safe",go for 4.0.3.
Then you can flash like siyah kernel,make a nand backup,and efs backup then install whatever rom you want.
Click to expand...
Click to collapse
would like to try that but now odin failed after i flashed a stock rom and now i'm stuck on the samsung galaxy logo with no recovery mode. I can get into download mode though but thats it.
Odin wont flash anything exept kernels.
Seriously thinking about throwing it in the bin. Now i spend days trying to get the phone usable again. why the hell cant i flash roms WTF!
Thanks for your replies.
There's a wealth of knowledge on this forum but i cant seem to find a solution on here to get my phone back.
Ive got my phone back. used upstairs pc and flashed original insecure kernel and recovery came up. ive now done a factory reset. back to square one but at least phone is back on. guess it was the laptop i was using. What is that all about?
Looking at all the how to's on upgrading to ICS i thought if i stuck to the steps it would just work but it didn't
Thanks for every ones input.
Chris.
Before everyone goes on to say that I need to read the forums, please understand that I've tried everything I could think of or find in the last week trying to get this thing back to stock.
Background:
I was on the leaked 4.3 firmware and the skynote ROM without problems. I tried switching to N3bula and flashing the official 4.3 firmware from Beanstown. I still couldn't get the N3bula ROM past the verizon logo and so i restored my backup from skynote. I (possibly mistakenly) unchecked the option to restore boot.img thinking i wouldn't need it. Everything booted into the backup just fine with the exception of WiFi. I tried rebooting into recovery and I soft bricked.
Things I've done since the brick:
- I used Odin and restored my phone to the root66 ROM (rooted VRALJB) - this allowed my phone to boot into a weird recovery program (probably some kind of stock) and it allowed me to actually use my phone as a phone.
- I tried flashing a new recovery in Odin (which probably should've been my first step instead of restoring to stock)
- I repartioned my PIT to the one from the forum on returning to stock
- I've (unsuccessfully) tried casual for VRALJB and VRAMC3
- I've (unsuccessfully) tried using Odin to go to either VRAMC3 and (normal) VRALJB
Device Info (from the app I downloaded named, "Device Info"):
These just seem peculiar to me...
- My bootloader is VRALL4
- My Baseband is VRAMC3
- My Incremental version is VRALJB
Help: - note that I do have root access
- Should these match? ^ and would those listed above cause casual to fail?
- Did i lock my bootloader when I unchecked the option to restore it in my backup after flashing the 4.3 firmware in Odin?
- Since my bootloader and my baseband are on different versions, would that cause casual to fail?
- Is there a way to downgrade my Baseband or upgrade my bootloader to make casual work?
I know these questions are probably way out of most people's leagues to answer, but anything helps guys!
Hey guys,
Could someone please help me with my problem. I'll try to be as clear as possible.
I had my fully working, factory unlocked from Three carrier GT-I9300 with 4.1.2 version, however yesterday I decided to updated my phones firmware via Odin 3.07 to 4.3 I9300XXUGML3. Everything went smoothly but after a while i noticed that it does not have any reception.
In phones status it shows:
Network: Unknown
Service state: Out of Service
My Phone Number: Unknown
IMEI: 00499901640000
Device status: Official
I figured it out that culprit might be IMEI code, so I reinstalled 4.3 version a few times but without success. After that I rooted my phone with Kingo Android root in order to fix my reception problem but It did not work out. In the end I thought to just send it to Samsung's warranty.However before sending phone I wanted to run TriangleAway in order to reset my binary count, but It does not resets. I thought that Knox might be stopping it from resetting as it's 4.3, however phone does not have Knox installed in it, even when in Download mode there is nothing written about Knox.
So I'm now in a pickle as I have:
-Corrupted IMEI
-No Reception
-TriangleAway does not resets binary
-Knox nowhere to be found (But I guess it's a good thing)
It would be really good to at least to reset binary count in order to send it to warranty to just forget about this mess :laugh:
Any ideas what is going on? I could not find any solution or problem which is similar to mine.
Triangle away won't work on later bootloader, downgrade to ICS bootloader.
boomboomer said:
Triangle away won't work on later bootloader, downgrade to ICS bootloader.
Click to expand...
Click to collapse
Isn't there a high chance of bricking phone while downgrading from 4.3 to ICS?
I tried now to flash my phone with stock I9300XXUGMK6 firmware in order to root it with CF-Auto-Root and then use Triangle Away to reset my binary counter. However It did not reset it.
Before that tried CWM, flashed kernel, flashed modem, used mobile odin. Sadly everything was in vain. I'm at loss now, don't know what do to. Maybe i'm doing something wrong? Maybe there is some kind of problem with the phone?
Eskis said:
Isn't there a high chance of bricking phone while downgrading from 4.3 to ICS?
I tried now to flash my phone with stock I9300XXUGMK6 firmware in order to root it with CF-Auto-Root and then use Triangle Away to reset my binary counter. However It did not reset it.
Before that tried CWM, flashed kernel, flashed modem, used mobile odin. Sadly everything was in vain. I'm at loss now, don't know what do to. Maybe i'm doing something wrong? Maybe there is some kind of problem with the phone?
Click to expand...
Click to collapse
Just the bootloader
Method 2 easiest
http://forum.xda-developers.com/galaxy-s3/general/how-to-flash-to-bootloader-updated-t2083860
Sent from my GT-I9300 using Tapatalk
Fixed
So I fixed it!
I had Mk6 firmware installed with cf-auto root.
After that I installed Boeffla's kernel (beta5 version) with mobile Odin and used TriangleAway 3.26 in order to reset my binary counter. Immediately after using mobile Odin again I installed official mk6 firmware and voila! Everything official and binary count set to 0, however I still had problem with IMEI and network so I sent phone to samsung as I have warranty.
Thanks everyone for helping out
Flashed stock Lollipop 5.1.1 ROM using ODIN, Device binary & status are CUSTOM? Help!
Hey guys! First time poster!
A few months back, I tried using CF-Auto root in order to gain root access on my phone, but I flashed something incorrectly and I was never able to get root working correctly. I know because of this, I tripped KNOX, and whenever I rebooted, there was a "Set Warranty Bit: Kernel" at the top of the device.
Due to the recent Marshmallow 6.0.1 upgrade, I want to unroot and get stock firmware, so I decided to do some research and go ahead and try to flash the stock G900T 5.1.1 FOJ4 firmware (tar.md5 file), so I can get my ability to update my phone via OTA updates. I looked up my matching firmware (FOJ4) through Android File Host and then unzipped it to my desktop.
I followed a guide and used ODIN 3.10.7 to flash the stock firmware file onto my phone. I also wiped cache/ factory reset before and after flashing the stock image.
Everything went well and I no longer see the "Set Warranty Bit: Kernel" when I boot. The problem I have is that when I go into download mode, the CURRENT BINARY and SYSTEM STATUS are both CUSTOM.
I was under the impression as long as you flash a stock firmware to your device, you will unroot and your device will be official, and then you'll be able to do OTA updates. Maybe its because I have KNOX tripped? Maybe can someone clarify that for me?
My main questions/concerns are:
1.) Is there anyway to make my device status/binary as OFFICIAL, in order to regain OTA updates?
2.) If I want to download the 6.0.1 Marshmallow update, should I just try through KIES or downloading the tar.md5 file to flashing via ODIN like I did with stock?
3.) Will there be any risk of bricking since my device is still "custom", if I go the above route?
4.) As a last ditch effort, should I just try downloading a different stock Lollipop firmware, and try flashing with ODIN again?
5.) What does this sub think of Marshmallow 6.0.1 update? Is it worth it?
Thank you guys in advance! Hope you have an awesome day!
@Root_S5_Please
#2 with Odin will work and is the correct way to go, #3 will not happen as long as you use Odin, you can't untrip Knox but that's OK since it doesn't have any effect on functionality. #4 is unnecessary and won't do anything to help. Someone else will have to answer #5, I Odined the update and immediately went back to CM13