Mural Watchface Brings 500px to Android Wear

On a traditional watch, you can’t really do too much to change its appearance once … more

Android 5.0 Favorite Features, Release November 3rd? – XDA TV

Google Confirms Android 5.0 Lollipop for November 3rd! That and much more … more

Prepare Your Build Machines: Ubuntu 14.10 Utopic Unicorn Now Official

Today is an important day for any and all Linux enthusiasts. One of the … more

Track the Time You Waste on Social Media with Socials Addict

When you use your phone, you often don’t even realize how much time you … more
Post Reply

[Q] S3 device status detected as "modified" after JB update yesterday night.

OP zadigre

3rd December 2012, 12:59 PM   |  #1  
OP Senior Member
Flag Montreal
Thanks Meter: 251
 
775 posts
Join Date:Joined: Aug 2006
More
First let me say that my Galaxy SIII was not rooted before the update. It's been running full stock rom.

I've done the Jelly Bean update yesterday night through Kies while my phone was connected to my computer.

Update was perfect until I tried the software update app to check if there was anything left to install.
At this moment, I had a message telling me that my phone was modified and updates will not work (I don't remember the exact message).
If I go to Settings, About device, Status... Device Status is "modified".

Again, I don't have anything on my phone to root my device.

So what I tried next... removing my microsd card (64GB Sandisk microSDXC) and reboot my phone. Now, Device status is "Normal".
Put it back again... reboot... and Device status is again "modified".
Format the card... reboot... Device status is Normal.
Put everything back (55GB of music only synched through iSyncr wifi with my Mac)... reboot... Device Status "modified".

So it really looks like that the thing that Samsung uses to detect the "modified" state of the phone is broken in some way because it's detecting my media files (mp3 and m4a) as some sort of modification to the phone... this is completely wrong!!

Am I the only one with this problem?

I will try this week to reduce the amount of music file to see if there is anything that broke the detection system... I will report later if I find anything.

By the way, I found a similar thread with a similar problem... but this thread did not offer any solution and it looks like to be close as I cannot add anything to it.
3rd December 2012, 01:05 PM   |  #2  
Tony_YYZ's Avatar
Senior Member
Thanks Meter: 95
 
430 posts
Join Date:Joined: Oct 2012
Donate to Me
That's very weird because I was rooted using the method in my sig and my device status showed modified as well. I was able to install the update just fine.
3rd December 2012, 01:51 PM   |  #3  
OP Senior Member
Flag Montreal
Thanks Meter: 251
 
775 posts
Join Date:Joined: Aug 2006
More
Quote:
Originally Posted by Tony_YYZ

That's very weird because I was rooted using the method in my sig and my device status showed modified as well. I was able to install the update just fine.

I was also able to install the update... the status was "normal" before the update...

the issue I have now is it says "modified" even if I did not modify anything in my phone.

I did the test again this morning... I removed all the music file on my card... device status is back to normal.

It must be one of my music file that triggers this detection... if it's in fact the case, it means that there is a bug in the detection that Samung have implemented.
3rd December 2012, 02:01 PM   |  #4  
Tony_YYZ's Avatar
Senior Member
Thanks Meter: 95
 
430 posts
Join Date:Joined: Oct 2012
Donate to Me
Quote:
Originally Posted by zadigre

I was also able to install the update... the status was "normal" before the update...

the issue I have now is it says "modified" even if I did not modify anything in my phone.

I did the test again this morning... I removed all the music file on my card... device status is back to normal.

It must be one of my music file that triggers this detection... if it's in fact the case, it means that there is a bug in the detection that Samung have implemented.

Yeah, that is very odd. I'd organize all your files on our SD Card into folders and move them to your PC. Then copy one folder at a time over to the SD card and see which one triggers the phone to show a Modified status. Then you can narrow it down from there.
3rd December 2012, 02:08 PM   |  #5  
OP Senior Member
Flag Montreal
Thanks Meter: 251
 
775 posts
Join Date:Joined: Aug 2006
More
Quote:
Originally Posted by Tony_YYZ

Yeah, that is very odd. I'd organize all your files on our SD Card into folders and move them to your PC. Then copy one folder at a time over to the SD card and see which one triggers the phone to show a Modified status. Then you can narrow it down from there.

this is exactly what I'm going to do... I will also try to logcat command through adb ... I might be able to find something in the log.

I will let everyone know as soon as I find the cause of this problem.
3rd December 2012, 08:04 PM   |  #6  
thatsupnow's Avatar
Senior Member
Flag Vernon
Thanks Meter: 374
 
1,740 posts
Join Date:Joined: Jan 2011
More
Yea mine was modified going into the ota update it updated fine then after when you checked software update it said it was modified and that updates were no longer available

Sent from my SGH-I747M using xda premium
3rd December 2012, 08:13 PM   |  #7  
Tony_YYZ's Avatar
Senior Member
Thanks Meter: 95
 
430 posts
Join Date:Joined: Oct 2012
Donate to Me
Quote:
Originally Posted by thatsupnow

Yea mine was modified going into the ota update it updated fine then after when you checked software update it said it was modified and that updates were no longer available

Sent from my SGH-I747M using xda premium

This is so weird, after my OTA completed yesterday I tried to check for updates again and it just told me I was on the latest version. Now when I check it gives me the modified error.

Blargh. Ahh well, It's not like we're going to be seeing another update anytime soon, unless it's a patch.
3rd December 2012, 08:16 PM   |  #8  
OP Senior Member
Flag Montreal
Thanks Meter: 251
 
775 posts
Join Date:Joined: Aug 2006
More
Quote:
Originally Posted by Tony_YYZ

This is so weird, after my OTA completed yesterday I tried to check for updates again and it just told me I was on the latest version. Now when I check it gives me the modified error.

Blargh. Ahh well, It's not like we're going to be seeing another update anytime soon, unless it's a patch.

are you rooted after updating?

maybe you can do like what I've did (remove microsd card), reboot and see if you still have this "modified" status/message.
3rd December 2012, 08:30 PM   |  #9  
Tony_YYZ's Avatar
Senior Member
Thanks Meter: 95
 
430 posts
Join Date:Joined: Oct 2012
Donate to Me
Quote:
Originally Posted by zadigre

are you rooted after updating?

maybe you can do like what I've did (remove microsd card), reboot and see if you still have this "modified" status/message.

I did restore root after updating. I'll have to temporarily remove root, restart and see what it says then. I'll try to do that later.
3rd December 2012, 08:35 PM   |  #10  
OP Senior Member
Flag Montreal
Thanks Meter: 251
 
775 posts
Join Date:Joined: Aug 2006
More
Quote:
Originally Posted by Tony_YYZ

I did restore root after updating. I'll have to temporarily remove root, restart and see what it says then. I'll try to do that later.

I suspect that they are checking not just the presence of "rooting" app in the system folder, but also other "rooting" files anywhere else on the phone... I'm sure they do this because just by removing my microsd card, even if the only files present were music and jpg file, the status went from modified to normal.

So a temp unroot might not necessarily fix this problem for you.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes