Root [AT&T] New GS3 - Unlocked - Can't Update OS!?!?

[rexbaum]

I purchased a new (in sealed box) GS3 about two weeks ago. When it came, the initial setup language was French, so setting it to USA English and setup went as normal. It is running 4.04, and a software update is obviously available.

It will DL the update, then the Android Robot begins his update annimation, when it hits 33%, it crashes / fails. I have tried this update several times and the results are the same.

Anyone have any ideas what is going on here?

Thanks guys / gals!

Rex

 

[jmatherly411]

Try doing a factory data reset, then try the update again.

 

[rexbaum]

Well, I DID a complete factory reset, then attempted the OS update.......

FAIL!

Made it to 33% and the little android guy fell over.

Frustrating! Anyone have any ideas?

Thanks

 

[funkylogik]

Sorry to say this but its an international (outside of N America) device. Does it work as it is?
You arent gona get an update the normal way :beer:

 

[rexbaum]

Yes, the phone functions great! I did some reading and was about to determine the CSC code "XEF" is for France.

This blows!

 

[funkylogik]

Root, custom 4.3 rom, keep the same baseband (radio firmware) that works :thumbup:
Have a quad-core s3 running nearly raw android in the US

 

[rexbaum]

I am going to have to do some serious reading.....

I don't have the slightest idea how to do any of that. :what:

 

[funkylogik]

Defo read a lot n check out the "international s3 all things root" sub forum in this page bro. Youve got a lil pocket rocket there :beer:

 

[rexbaum]

Okay, been doing some reading..............

"SUPERUSER" app is on my phone! Am I already rooted? As mentioned earlier, this phone was in a sealed Samsung box and sold as being an unlocked international version.

 

[CDPlant]

Okay, been doing some reading..............

"SUPERUSER" app is on my phone! Am I already rooted? As mentioned earlier, this phone was in a sealed Samsung box and sold as being an unlocked international version.

Do you mean that the phone came with the Superuser app, or did you put it on there?

 

[rexbaum]

The phone came with the app. I run the check on it and result for root access states "okay"

 

[rexbaum]

Do you mean that the phone came with the Superuser app, or did you put it on there?

The superuser app was on the phone from the start! I had no idea what it was and never opened the app, that is until I read about the app's use for rooted phones.

If I tap to check updates, it runs a system test and "root access" test result reads "okay"

Is it possible that Samsung packaged GS3 phones for international use that were unlocked AND rooted?

 

[CDPlant]

The superuser app was on the phone from the start! I had no idea what it was and never opened the app, that is until I read about the app's use for rooted phones.

If I tap to check updates, it runs a system test and "root access" test result reads "okay"

Is it possible that Samsung packaged GS3 phones for international use that were unlocked AND rooted?

That is really bizarre But it would explain why you can't update the OS. You may have a custom recovery, which means that any official update from Samsung will fail every time. You can check this by turning the phone off, and then holding down the power button + home button + volume up. This will boot into the recovery. If you do this, let us know what is says. You'll either get 'Android Recovery 3e' (I think) or a custom one might be called Philz, CWM or TWRP.
[To get back from recovery, press 'reboot system now' and nothing else. You use the volume buttons and the power button to select options.]

Where did you buy this S3 from? It is incredibly unlikely that Samsung would sell it pre-rooted, so it's looking like it's been repackaged and possibly 2nd hand

 

[rexbaum]

That is really bizarre But it would explain why you can't update the OS. You may have a custom recovery, which means that any official update from Samsung will fail every time. You can check this by turning the phone off, and then holding down the power button + home button + volume up. This will boot into the recovery. If you do this, let us know what is says. You'll either get 'Android Recovery 3e' (I think) or a custom one might be called Philz, CWM or TWRP.
[To get back from recovery, press 'reboot system now' and nothing else. You use the volume buttons and the power button to select options.]

Where did you buy this S3 from? It is incredibly unlikely that Samsung would sell it pre-rooted, so it's looking like it's been repackaged and possibly 2nd hand

I did the boot into recovery and the first line at the top said
"Android Recovery <3e>"

Here is a screen cap of the Superuser test results.

I have no idea what I am talking about, but I suspect the phone is rooted! That being said, is it possible to get an OS beyond 4.04?

 

[rexbaum]

CDPlant,

Sorry buddy, I failed to answer you second half of your reply. I bought the phone from Newegg. I was skeptical, but when the phone arrived, I found the Samsung S3 box was pristine, and unmolested MFG tape on both sides of the box (identical to the unboxing videos on youtube). Contents of the box, ie. battery, ear buds, charger, data cable, etc., all packaged tightly. I am very certain that this phone is not used. Very pleased with the purchase!

 

[CDPlant]

CDPlant,

Sorry buddy, I failed to answer you second half of your reply. I bought the phone from Newegg. I was skeptical, but when the phone arrived, I found the Samsung S3 box was pristine, and unmolested MFG tape on both sides of the box (identical to the unboxing videos on youtube). Contents of the box, ie. battery, ear buds, charger, data cable, etc., all packaged tightly. I am very certain that this phone is not used. Very pleased with the purchase!

This is very strange... stock recovery, SU access and a sealed box I'm honestly not sure why it won't update to a newer Android version, it should be fine with your setup. I'm going to see if I can bring anyone else into this to weigh in on the situation.

 

[rexbaum]

This is very strange... stock recovery, SU access and a sealed box I'm honestly not sure why it won't update to a newer Android version, it should be fine with your setup. I'm going to see if I can bring anyone else into this to weigh in on the situation.

I really appreciate your assistance! I am lost and I would very much like to have the latest operating software.

 

[scary alien]

rexbaum,

Did you buy this device as a refurbished one or was it advertised as brand-new?

It certainly looks to me as if the device was/is rooted and that there are things that have been changed in the O/S (i.e., system components) that are being checked by the OTA that's trying to be installed but is failing because the consistency cross-checks are failing.

If you can install the Android Terminal Emulator app (free in the Play Store), start it, and type these commands (and show us the output here) it might help us figure-out what is going on:

$ su
# ls -al /cache
# ls -al /system/*bin/su
# ls -al /system/app/Super*
# ls -al /cache/recovery

If you see a last_log file in the /cache/recovery directory, you could use a root-enabled file manager (like ES File Explorer) and copy that file to your SD card and paste it here. That last_log file should show you what issues the OTA is having in installing.

Let us know!

 

[funkylogik]

Phew this is strange stuff. Glad the experts caught this one. Ill be spectating. What id wana do though is flash philz or CWM then you have a world of roms to choose from. You can even have a rooted debloated version of the official 4.3 samsung update :thumbup:

 

[rexbaum]

Scary Alien,

I'll do this shortly and post the results; I work nights for the next few months and I have a great opportunity to tinker at work.

I appreciate your help!

 

[rexbaum]

rexbaum,

Did you buy this device as a refurbished one or was it advertised as brand-new?

It certainly looks to me as if the device was/is rooted and that there are things that have been changed in the O/S (i.e., system components) that are being checked by the OTA that's trying to be installed but is failing because the consistency cross-checks are failing.

Not sure if I did this correctly, however here is the results (or a lack thereof).

 

[scary alien]

Ah, thanks rexbaum...sorry I didn't tell you that the spaces are meaningful.

Here it is again with the spacing emphasized:

$ [COLOR="Red"][B]su[/B][/COLOR]
# [COLOR="red"][B]ls  -al  /cache[/B][/COLOR]
# [COLOR="red"][B]ls  -al  /system/*bin/su[/B][/COLOR]
# [COLOR="red"][B]ls  -al  /system/app/Super*[/B][/COLOR]
# [COLOR="red"][B]ls  -al  /cache/recovery[/B][/COLOR]

By the way, that's a lowercase "L" (not a one or a vertical bar) after the "a" in the "-al" portion of the "ls -al".

edit: by the way, your output does indeed confirm you are rooted (note the "#" prompt after you typed the "su" command).

 

[rexbaum]

Sitting here with my mouth hanging open! You guys have superhuman powers. I might have done it right this time.....

Thank you very much!

 

[rexbaum]

Here is pics of the box. It was sealed!

Being a transformed iPhone user, I have used a couple androids in the past year or so. HTC One X, HTC one and mist recent being the Nexus 4. THIS phone has captures me! I love everything about it!

Can't express my gratitude for your help and being somewhat of a teacher. You ROCK!

 

[scary alien]

No problem, rexbaum--that's what we do here at AF .

And those pics you posted show a couple things:

1. confirms you are rooted by verifying the su and Superuser.apk binaries existence and security settings

2. shows there is not OTA (over-the-air) .zip file located in your /cache folder (at least currently); however, I'm am curious about the /cache/fota directory (more on this in a second)

3. those pics of your box are pretty wild--someone's got some explaining to do, LOL, if a carrier or manufacturer shipped-out a new device pre-rooted

~ ~ ~

Okay, next steps:

1. I'd like you to type this command in the Android Terminal Emulator window and show us the output:

# [COLOR="Red"][B]ls  -al  /cache/fota/*[/B][/COLOR]

I'm wondering if there's OTA .zip file within that directory. If there is, we can use my OTA Verifier app if necessary to scan it.

2. If you can copy the last_install and last_log files from your /cache/recovery directory over to your SD card and post those up for us, that would be very helpful and illustrative. Hopefully your device will have an /sdcard folder that we can copy to:

# [COLOR="red"][B]cat  /cache/recovery/last_log  >  /sdcard/last_log.txt[/B][/COLOR]
# [COLOR="red"][B]cat  /cache/recovery/last_install  >  /sdcard/last_install.txt[/B][/COLOR]

So, after you use the above commands to copy those files to you SD card (/sdcard), you should be able find them with a file manager and/or Gmail and/or copy them over to your PC and them post them up here (as text or an attachment).

I'm very interested in your last_log file and think that will tell us the most.

Okay, that's enough for now...let us know!