[Q] S3 device status detected as "modified" after JB update yesterday night.
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.
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.
Tony_YYZ said:
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.
Click to expand...
Click to collapse
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.
zadigre said:
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.
Click to expand...
Click to collapse
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.
Tony_YYZ said:
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.
Click to expand...
Click to collapse
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.
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
thatsupnow said:
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
Click to expand...
Click to collapse
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.
Tony_YYZ said:
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.
Click to expand...
Click to collapse
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.
zadigre said:
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.
Click to expand...
Click to collapse
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.
Tony_YYZ said:
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.
Click to expand...
Click to collapse
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.
zadigre said:
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.
Click to expand...
Click to collapse
Hmm, hopefully the answer surfaces from one of the devs soon.
I have ROOT but my Device Status is Normal
Sent from my SGH-I747M
yulet said:
I have ROOT but my Device Status is Normal
Sent from my SGH-I747M
Click to expand...
Click to collapse
which su binary are using (supersuser or supersu)?
I think that supersu has an option to hide the root availability... is this the one that you are using?
thatsupnow said:
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
Click to expand...
Click to collapse
Sam here, as far as I can tell it wasn't as a result of the SD card. It was fine when I had stock unrooted Rogers ALH1, but it changed to modified when I flashed the root injected Rogers ALH1 for the no counter trip thread, and it was in ODIN too.
zadigre said:
which su binary are using (supersuser or supersu)?
I think that supersu has an option to hide the root availability... is this the one that you are using?
Click to expand...
Click to collapse
I'm also rooted on the JB update and status shows normal. I'm using supersu but can't find an option to hide. With rooted ics it always showed modified.
I wasn't sure if it was connected to the flash counter in some way since I'm not at 0 anymore but apparently that's not the case.
Sent from my SGH-I747M using xda app-developers app
acloaf said:
I'm also rooted on the JB update and status shows normal. I'm using supersu but can't find an option to hide. With rooted ics it always showed modified.
I wasn't sure if it was connected to the flash counter in some way since I'm not at 0 anymore but apparently that's not the case.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
It's all based upon files in /system ALSO flash counter.
Modified, meh.
Just if you DO NOT root and updated to JB 4.1 and it now shows modified...that's weird.
Yet most of the time when you flash to a rooted version and it says modified thats cause of /system files and flash counter.
caha2639 said:
It's all based upon files in /system ALSO flash counter.
Modified, meh.
Just if you DO NOT root and updated to JB 4.1 and it now shows modified...that's weird.
Yet most of the time when you flash to a rooted version and it says modified thats cause of /system files and flash counter.
Click to expand...
Click to collapse
My phone has a stock rom and flash counter is 0.
This morning, I had all my music files on my microsd card... Status was modified. I removed all files, reboot... Status normal. Yes this is weird.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I have the same weird problem too. I bought my phone 4-5 days ago from a famous shop. It was totally new and unused, never rooted, never flashed anything, no simlock, no root required app installed AND no sdcard. These days it is mostly Modified, rarely it turns to Normal after restarting the device...
I don't know what was really going on... I removed one song, got the "Normal" status. I removed some other files, got "modified". ReAdd the first file that was removed, got the "Normal" status again.
What I've decided to do is put my memory card in my MacBook Pro. I got an error that the card wasn't readable. My MacBook is supposed to support SDXC standard with and extFAT formated card... so it looks like that my card had a problem. I decided to reformat the card with FAT32 even if SDXC card are supposed to be extFAT. I put the card back into my phone. I synched all music files.... and I got the "normal" status again. I modified my playing list in iTunes... I synched again... status stil shown as "normal".
So I don't know what was the problem exactly... I suppose that the file system on the card was damaged in some way... but I really do not know what caused this problem at first.
Anyway it works fine now... so this is the most important thing.
Related
I just got the notification for it, but I don't want to risk anything. Is it good to go?
no, before this gets moved, not good to go. don't flash it. you will lose root
seems like you will lose the root...
but some have posted that even after the ota update... the current root process will still work.
Strange. Thanks, guys.
You'd loose your root.
gabemeyers said:
seems like you will lose the root...
but some have posted that even after the ota update... the current root process will still work.
Click to expand...
Click to collapse
I rooted did OTA and still seemed to have root access. Just re-rooted and it seems cool flashing stock rom in a second I guess to confirm
Ok I didnt flash a rom but it is letting me do data wipes and all other functions it seems cool!
Flipz confirmed my successful Re-root looks like OTA is safe!
I rooted mine BEFORE the OTA upgrade.. and it stayed rooted after.. -m
I'm not taking any chances. The other dev team is supposed to release their root and it may be more complete than what we have now. No reason to take a chance on an update that isn't totally critical.
I just tried it.. it appears to fail, reboots, and you're still on 1.32.651.1.
sph33r said:
I just tried it.. it appears to fail, reboots, and you're still on 1.32.651.1.
Click to expand...
Click to collapse
What exactly does the this ota do anyway?
1wingangel said:
What exactly does the this ota do anyway?
Click to expand...
Click to collapse
It's supposed to fix the read/write permissions glitch with the MicroSD card.
diomark said:
I rooted mine BEFORE the OTA upgrade.. and it stayed rooted after.. -m
Click to expand...
Click to collapse
Let me correct this.. The OTA update did not work.. (I stayed at the old software version after trying to apply it.. but root stayed around..)
NOW has anyone managed to place the SD card fix on here manually?
-mark
Yes please. Just update.zip that goodness please. I am sure a complete SuperFresh Rom is on its way.
Well i guess I got this all backwards
I didnt know any better when I got the phone in the store, and I did the update...
then decided to root it.... did the process....
it worked.... but then I had the insufficient permissions on the SD card issue...
after reading a bunch of yea's and nay's on OTA update
I finally made the decision to just due the OTA update cuz I that SD card issue really bugged me...
I did the OTA update, the phone did this funny thing where its showing a green progress bar and then in the middle of it, a red question mark pops up as if it were saying " what the hell is this??" lol
it rebooted... and phone came back online, and now my SD card isnt having the same issue anymore...
UPDATE: Its back.... so now what do I do? Is there any way I can include all my info and settings and apps in a custom recovery cuz if i have to do this again im gonna freak. lol
lbheightsboy said:
I did the OTA update, the phone did this funny thing where its showing a green progress bar and then in the middidle of it, a red question mark pops up as if it were saying " what the hell is this??" lol
Click to expand...
Click to collapse
your having the same problem as me... the update failed.. which is why were waiting on a way to manually apply the update.
OTA worked perfectly. And I get root access
I still haven't gotten the OTA...no matter how many times I manually "check now" in HTC Software Updates, it does not show up. I don't know why this is happening, it's very odd. I'm waiting for someone to cook the update into a custom, or rather stock, ROM. It's driving me insane at the moment, not to mention a bunch of apps are missing from the market (a whole other issue in it's own right). If anyone has an update.zip I can flash or a way to fix this, please please please let me know. Thanks.
I wasn't getting the OTA notification either until I enabled WiFi, then restarted the phone. Worked perfectly after that. Didn't even have to go to system updates.
-------------------------------------
Sent via the XDA Tapatalk App
Hello, hope I'm doing this right. Tried searching forum for similar issues but no luck. Here goes.
I own the T-Mobile variant of the Galaxy Note 2. It is stock, never rooted but I am getting this strange message when I attempt to check for new software updates under "about device." The message is "Your device has been modified. Software updates are not available. " This happened once before but solved it with a factory reset. Any idea what's causing it? No new apps installed that I can think of. Would appreciate any advice.
Sent from my SGH-T889 using xda app-developers app
ronman71 said:
Hello, hope I'm doing this right. Tried searching forum for similar issues but no luck. Here goes.
I own the T-Mobile variant of the Galaxy Note 2. It is stock, never rooted but I am getting this strange message when I attempt to check for new software updates under "about device." The message is "Your device has been modified. Software updates are not available. " This happened once before but solved it with a factory reset. Any idea what's causing it? No new apps installed that I can think of. Would appreciate any advice.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
something is triggering android into thinking you modified it. since you aren't rooted, I can't really think of a way to fix this... unless you root.
This means that the device has been modded, like custom recovery, etc. Either you rooted it at one time or someone owned this device rooted it with a custom recovering. If you just got this device from T-Mobile then return to them and let them know that you got it this way. Bad form for a store or carrier to repackage a return (even reseal) and resale it, but it does happened.
Otherwise you need flash a root version, best use stock root injection version of rooted rom, into the device. Check to see if you have the stock recovery. If not then flash stock recovery. Now use Triangle Away to reset "Custom Binary" to 1. Once you do that then flash the stock rom unroot version (this will unroot the device). Then do a factory reset to get rid of anything left from root. After that then you will have "Normal" as your "Device Status" and can successfully check for updates.
Note - You will never get the "Custom Binary" back to "no". So if you need repair or replacement from Samsung you may have to pay for it (this depends on the tech working on your device). But with the T-Mobile Protection Bundle insurance ($7.99 per month) you may get around this problem. In returning to T-Mobile they seem to only check the "Device Status". So after resetting the "Custom Binary" to 1 you should be able to return to T-Mobile for repair or replacement under that insurance or your grace time (14 days or CA 30 days) with no problem. This getting around the Samsung's returning issues.
Note - I like the injection version of rooting. The injection version of rooting doesn't trigger the "Custom Binary". This solving this problem from the start. At least for the moment.
Go to menu-settings-about device-status
Scroll all the way to the bottom. It will tell you under device status whether your device is modified or not.
If it's modified then only thing you can do is Odin back the original Samsung Rom. You should do the triangle away thing first to reset the mod counter to "0"
Sent from my SGH-T889 using Tapatalk 2
whatsitsnamenow said:
You should do the triangle away thing first to reset the mod counter to "0"
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Actually it doesn't reset the "Custom Binary" counter to "0" or "no". This only resets the "Custom Binary" counter to "1".
But it does reset the "Device Status" to "Normal". And allows you to successfully check for updates.
Sent from my SGH-T889 using xda premium
Only if you have a custom recovery. If you have factory recovery on a factory rom it will reset to 0 if you use triangle away. Which is kind of a moot point since he says its never been rooted, therefore there should be no way a custom binary reading of anything higher than 0.
Thanks for your replies. Strange thing is that I've never rooted this particular device. Also, the factory reset fixes it temporarily. Could it be something in my micro sd card that I transferred from my previous device which was rooted?
Sent from my SGH-T889 using xda app-developers app
If you have a sdcard in there, then that is the reason. Boot up without the sdcard and the status will say normal.
lt23 said:
If you have a sdcard in there, then that is the reason. Boot up without the sdcard and the status will say normal.
Click to expand...
Click to collapse
What?
Wow, totally worked! Weird. Guess I should back up and reformat my micro sd card. Thanks guys!
Sent from my SGH-T889 using xda app-developers app
stevessvt said:
What?
Click to expand...
Click to collapse
Turn off phone, take out the sdcard. Turn on phone. Check status, should say Normal again. This is for those with no root/custom recovery or for those rooted with the injected rom.
ClockWorkMod sometimes likes to use SD Card to put some files. It is weird. But this "Custom Binary" counter thing would "Modify" you if you have some root files, including SuperUser, SuperSU, ClockWorkMod, BusyBox, etc. These files can be anywhere including SD card. I find this weird because I don't have this problem with SuperSU, SuperSU Pro and BusyBox. But for some reason this comes up with some people.
Here is an idea. Copy all files into its own folder in your computer. After that then delete all files and folders within your SD card. Then copy whatever files you like to have with your Galaxy Note 2 back into your SD card. Then try your SD card with your Galaxy Note 2.
Personally I feel that it is not the place of the manufacturer to stop rooting on Open Source and Google encouraging rooting Android Devices. If you don't want to fix my rooting mess, then you can refuse to fix it. But doing things like this is only causing more problems with my rooting than ir would if you didn't do this. Mind you that T-Mobile don't care if we root, they just don't want to fix it. So this is not T-Mobile issue. This is Samsung issue. That speaking to manufacturers.
-
JaguarXT said:
Actually it doesn't reset the "Custom Binary" counter to "0" or "no". This only resets the "Custom Binary" counter to "1".
But it does reset the "Device Status" to "Normal". And allows you to successfully check for updates.
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
I've actually rooted the stock T-Mobile Note 2 as well and used Triangle-Away and my counter was reset but my status is still "Modified" :laugh: I don't mind, though... once you root your first phone, you root everything anyways! Just waiting for a good ROM...
Your device has been modified
I didn't root my galaxy s3. In my country, Indonesia, i don't know 4.1.2 version will come. i just check to software update and it said your device has been modified. i tried take off sd card things, it didn't work. any solution that can change back to normal?
topikdinata said:
I didn't root my galaxy s3. In my country, Indonesia, i don't know 4.1.2 version will come. i just check to software update and it said your device has been modified. i tried take off sd card things, it didn't work. any solution that can change back to normal?
Click to expand...
Click to collapse
You need a stock kernel and a factory reset to get back to normal.
Hastily spouted for your befuddlement
You can remove "modified" and reset the flash counter to zero with a jig (and I thought triangle away was supposed to as well), because I've done it on my SGH-T889 Note 2. You have to Odin back to non rooted stock with stock recovery, remove your external sd card, go into download mode, then plug in the jig and Bob's your Uncle it's reset. I'm not sure why someone said you can never reset the custom binary to no because you definitely can.
Sent from my 1992 Motorola StarTAC
jeep447 said:
You can remove "modified" and reset the flash counter to zero with a jig (and I thought triangle away was supposed to as well), because I've done it on my SGH-T889 Note 2. You have to Odin back to non rooted stock with stock recovery, remove your external sd card, go into download mode, then plug in the jig and Bob's your Uncle it's reset. I'm not sure why someone said you can never reset the counter to zero because you definitely can.
Sent from my 1992 Motorola StarTAC
Click to expand...
Click to collapse
I set mine back to zero by Odining mrRobinson's root66 to get stock recovery. Then while stock rooted I used Triangle Away to reset the counter. After that a factory reset gets me back to status normal. Seemed to work when I did it. Maybe I don't know what I saw as I'm new to Samsung devices.
Hastily spouted for your befuddlement
Coug76 said:
I set mine back to zero by Odining mrRobinson's root66 to get stock recovery. Then while stock rooted I used Triangle Away to reset the counter. After that a factory reset gets me back to status normal. Seemed to work when I did it. Maybe I don't know what I saw as I'm new to Samsung devices.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Yeah I'm pretty sure that's what you saw because it's definitely doable. If you have the time and know how, I'd definitely suggest building a jig for your phone, because according to Chainfire it's actually a lot safer than using Triangle Away. It's way easier to build one than most people think, and it literally only costs a couple of bucks at Radio Shack for everything you need. I made one for a friend of mine and wound up keeping it, and I'm really glad I did now that I have a Samsung phone.
Sent from my 1992 Motorola StarTAC
I too had this issue last month, I brought my Note II from T-Mobile store, it was sealed and it used to show device status as Normal.
I never rooted or flashed any ROM. I did install/uninstall lots of games/applications and I did disable Amazon app.
Earlier this month I checked my phone and it was showing as Modified, I then reset to factory defaults and now everything looks okay.
I do use external memory card but it only has few media files.
How did the device status change then ?
I am new to Android and rooting and can make the following guesses.
1) Maybe one of the applications I had installed rooted my phone or modified some files via Exynos Abuse (discovered this week) and which is why my device was showing modified.
But again if my phone was rooted, why this device status is Normal ? I was able to update my phone with the OTA released today.
2) Applications like Antivirus or Task Killers have almost full access and maybe they modified some system files.
Like I said I am new to Android so just making guesses hoping experts can shed some light on this.
Wanting to go back to stock, but afraid to do so. Im on jedi x7, rooted, no custom kernal and with two addons from goodybag. I have dowloaded the tar to go back to stock. I've also downloaded triangle away. Im wanting to boot into TWRP recovery, do a wipe/Factory reset, reboot start triangle away and reset counter then use odin and return back to stock. My counter shows 1 on download mode. Would this be the right way to go and resetting the counter back to 0 without any issues? Thanx.
Sent from my SGH-T889 using xda app-developers app
In a bit of a pickle.
No matter what I do, my system status is always modified.
I've unrooted with TA, flashed stock, then wiped cache, wipe data, and wipe cache.
It shows normal the first boot.
Then when it restarts, it's modified again.
Suggestions?
AjunNg said:
In a bit of a pickle.
No matter what I do, my system status is always modified.
I've unrooted with TA, flashed stock, then wiped cache, wipe data, and wipe cache.
It shows normal the first boot.
Then when it restarts, it's modified again.
Suggestions?
Click to expand...
Click to collapse
You have to do a data/factory reset in settings/backup and restore mate.That should fix it.
Tried that, still modified.
Get it rooted again. Install triangle away and use it. Then flash stock rom via odin, wipe cache/data and factory reset. Viola!
Thats what I did and it worked.
Sent from my GT-N7100 using xda app-developers app
vash_h said:
Get it rooted again. Install triangle away and use it. Then flash stock rom via odin, wipe cache/data and factory reset. Viola!
Thats what I did and it worked.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
That's the steps I went through.
Are there any special steps I need before I flash via Odin?
Just TA?
Does it still show Normal after a restart?
Cos for me, it's shows Normal, and just after one reboot, it's automagically modified.
Try to factory reset again. I did it twice
Sent from my GT-N7100 using xda app-developers app
Done that loads of times.
As soon as I restart device, it shows modified.
I need to claim warranty, which is why I need it normal normal normal.
Could it be a problem of the stock firmware?
Does anyone know the CSC of the unlocked version of the N7100?
a friend of mine wanted to claim warranty at o2 in Leeds but couldn't due to device modified. He raised hell but the store wouldn't budge. One of the store sales people asked him if he had insurance, he had.. puked him to one side pretending to calm him down, and told him to go home, or coffee over the phone and come back tomorrow to claim insurance for a new phone.
My friend went back, did that.. and the store salesguy have him another phone under insurance.
My friend could b real lucky and might not work for u. For obvious reasons he won't tell me the name of the kind understanding fellow. But he left a letter of compliment for the sales guy good service.
Sent from my GT-N7100 using xda app-developers app
I would do that, but won't accept a refurbished device over my new one.
If only they give new replacements.
Anyway, I finally got it back to Normal.
I used Kies to restore it, and it's on Normal no matter how many times I restart.
I think I just needed to reflash it twice to get it back to Normal.
We'll see what they say today, as I went in yesterday, and they somehow said my CSC isn't valid... wtf.
Apologies if not relevant...
...but my brand new, sealed box Vodafone N-7100 shows "Modified" until I remove the SD card, at which point it show "Unmodified" and allows update check etc. but as soon as I put in the SD card again.
I was panicking that it had been rooted or something but I think it's just a weird software bug. I found a guy in a forum mentioning the SD card thing and sure enough it fixed it for me.
My SD card is 64GB, formatted as exFAT by the phone itself, incidentally.
Anyone else having this problem with a 100% stock, unrooted, unhacked phone?
U mean if u insert a 64gb sdcard formatted to exfat or will show modified? That's weird. Lucky I use 32gb cards
Sent from my GT-N7100 using xda app-developers app
Hi,
Yes that's exactly right. I haven't actually tried formatting FAT32 to see if it has the same issue. Also I haven't tried other SD cards - I've only had the phone a short while.
I used to use the same SD card in my Galaxy S2 with no issues.
vash_h said:
U mean if u insert a 64gb sdcard formatted to exfat or will show modified? That's weird. Lucky I use 32gb cards
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
RedRecidivist said:
...but my brand new, sealed box Vodafone N-7100 shows "Modified" until I remove the SD card, at which point it show "Unmodified" and allows update check etc. but as soon as I put in the SD card again.
I was panicking that it had been rooted or something but I think it's just a weird software bug. I found a guy in a forum mentioning the SD card thing and sure enough it fixed it for me.
My SD card is 64GB, formatted as exFAT by the phone itself, incidentally.
Anyone else having this problem with a 100% stock, unrooted, unhacked phone?
Click to expand...
Click to collapse
I have the same issue with a T-Mobile (US) version. Removing the 64GB exFAT micro SD card and rebooting causes the device status to change from Modified to Normal. Reinserting the micro SD card causes the device status to show as Modified. Is the only fix to format the SD card as FAT32?
AjunNg said:
I would do that, but won't accept a refurbished device over my new one.
If only they give new replacements.
Anyway, I finally got it back to Normal.
I used Kies to restore it, and it's on Normal no matter how many times I restart.
I think I just needed to reflash it twice to get it back to Normal.
We'll see what they say today, as I went in yesterday, and they somehow said my CSC isn't valid... wtf.
Click to expand...
Click to collapse
Hello,
You really need to check your original csc sold in your country, then you must download it from sammobile and flash again!
Sent from my GT-N7100
skins07 said:
Is the only fix to format the SD card as FAT32?
Click to expand...
Click to collapse
I haven't actually got around to trying that - can you confirm that it works?
RedRecidivist said:
I haven't actually got around to trying that - can you confirm that it works?
Click to expand...
Click to collapse
I haven't tried it either. The issue still exists following the T-Mobile system update that I just installed today. I was able to install the update with the SD card removed.
I had something very odd happen. I got my replacement note and when I took it out of the box and fired it up there was an OTA waiting for me. I installed it right away. Afterwards I went to check to see if there were more updates.. It then told me my device was modified and couldn't update. The status shows "custom" I was able to update via kies and got the latest OTA but it still shows custom. I haven't rooted or modified the device in anyway. In Odin mode it shows warranty flag as 0.
Had this happened to anyone else? No matter what I do it keeps saying custom. In Odin I flashed a full official firmwares.. Still says custom.. It's driving me nuts..
USA wifi model SM-P600
Sent from my Nexus 5 using Tapatalk
Don't know if it will help, did you tried removing the extsdcard and reboot?
was it factory sealed? sounds like you got someone else's returned note. has the Knox flag been tripped?
It was factory sealed. The seal was intact. The odd thing is that it got the first ota but after that it showed modified. I haven't tried removing the ext sd card. Would that really matter?
Sent from my Nexus 5 using Tapatalk
can you boot into dlownload mode and see if knox has been flagged? if it is then this as gotta be some freaky stuff going on and pretty crappy if younare denied a warranty repair bc of a faulty ota.
madsquabbles said:
can you boot into dlownload mode and see if knox has been flagged? if it is then this as gotta be some freaky stuff going on and pretty crappy if younare denied a warranty repair bc of a faulty ota.
Click to expand...
Click to collapse
OP, who's a dev, said in his post KNOX is at "0."
bruce16878 said:
Don't know if it will help, did you tried removing the extsdcard and reboot?
Click to expand...
Click to collapse
I've seen this before on XDA but can't remember where. Here's an offline post referencing it. The issue's never been explained but rebooting the device without the SD card in it corrects the problem.
https://community.optus.com.au/t5/M...eventing-Galaxy-s4-Software-update/td-p/57034
Thanks Barry I will try without the bad card in.. Haven't seen you in a while.. Hope all is well
And yes.. Removing the SD card made it say official again.. Thanks man. Odd that an SD card would make it show modified. I'm going to read that link you posted now.
Sent from my Nexus 5 using Tapatalk
Well, have a nice day.
Sent from my GT-N7105 using xda app-developers app
Hello,
I'm new to this forum, and I could not find anything related to this issue. I'm successfully downloading the latest update and when I try to install it, the installation goes up to 25% and I get the red exclamation mark afterwards. The phone then restarts, and I'm back at the beginning, where I have to re-download the update all over again. I don't have any custom ROMs flashed on my device, it's just like I bought it, the latest update that I made was the update to Android v6.0.1. Current software number is v2.10.401.1, if that is of any importance. I've factory reset the phone, and tried applying the update on a fresh phone, but it still won't work.
Also, while I'm here, I might just ask... I'm getting frequent app crashes/unresponsive app, mostly on the apps that I'm using the most, Facebook and Instagram. Facebook is more stable, crash/unresponsiveness does not happen very often, but for Instagram it's always happening after scrolling 3-4 images. Also, the Sense Home app is always getting unresponsive after a phone restart, and I have to restart it several times until it gets back to normal, since it cannot recover from it, I'm not seeing the home screen at all.
I was very satisfied with my phone before the update to Android 6, but after upgrade, I'm frequently having these minor problems, another one of which is the SD card "unexpectedly removed" error, which is happening when I open up the gallery or the file manager. I'm running low on patience, I really hoped that this last update will fix things, but I'm very close to slamming the phone off the wall, that's how frustrated I am. Please help
Well I'm no expert here but I've also experienced the freezes in such apps and even normal restart didn't work, so I had to force restart it. This happened in marshmallow and lollipop both so i tried removing my sd card and freezes were gone. In my case it was the sd card, so you can try that.
And for the update check if your bootloader is locked, assuming you bought it refurbished or used, the previous owner might have done some tinkering.
Hope you find the solution soon :good:
spiderwebmkd said:
Hello,
I'm new to this forum, and I could not find anything related to this issue. I'm successfully downloading the latest update and when I try to install it, the installation goes up to 25% and I get the red exclamation mark afterwards. The phone then restarts, and I'm back at the beginning, where I have to re-download the update all over again. I don't have any custom ROMs flashed on my device, it's just like I bought it, the latest update that I made was the update to Android v6.0.1. Current software number is v2.10.401.1, if that is of any importance. I've factory reset the phone, and tried applying the update on a fresh phone, but it still won't work.
Also, while I'm here, I might just ask... I'm getting frequent app crashes/unresponsive app, mostly on the apps that I'm using the most, Facebook and Instagram. Facebook is more stable, crash/unresponsiveness does not happen very often, but for Instagram it's always happening after scrolling 3-4 images. Also, the Sense Home app is always getting unresponsive after a phone restart, and I have to restart it several times until it gets back to normal, since it cannot recover from it, I'm not seeing the home screen at all.
I was very satisfied with my phone before the update to Android 6, but after upgrade, I'm frequently having these minor problems, another one of which is the SD card "unexpectedly removed" error, which is happening when I open up the gallery or the file manager. I'm running low on patience, I really hoped that this last update will fix things, but I'm very close to slamming the phone off the wall, that's how frustrated I am. Please help
Click to expand...
Click to collapse
If you are willing to, you can unlock the bootloader from http://www.htcdev.com/bootloader/ and flash a stock sense ROM or other custom ROMs and that might solve the app crash problem.
bilal.fanatic said:
Well I'm no expert here but I've also experienced the freezes in such apps and even normal restart didn't work, so I had to force restart it. This happened in marshmallow and lollipop both so i tried removing my sd card and freezes were gone. In my case it was the sd card, so you can try that.
And for the update check if your bootloader is locked, assuming you bought it refurbished or used, the previous owner might have done some tinkering.
Hope you find the solution soon :good:
Click to expand...
Click to collapse
I've already tried removing the SD card, and I've seen slight improvement in the app crashes, but they were still occurring. My bootloader is locked, but I'm going to unlock it now and flash a new ROM, I can't play around with it anymore
spiderwebmkd said:
I've already tried removing the SD card, and I've seen slight improvement in the app crashes, but they were still occurring. My bootloader is locked, but I'm going to unlock it now and flash a new ROM, I can't play around with it anymore
Click to expand...
Click to collapse
Before you do that .. as there is almost no custom ROM available for M8s except CM which is in progress, I don't suggest to unlock bootloader.. try to find and install 2.10.401.1 RUU
Installing RUU will usually fix this kind of problem if the data partition is sort of corrupted but not damaged.
ckpv5 said:
Before you do that .. as there is almost no custom ROM available for M8s except CM which is in progress, I don't suggest to unlock bootloader.. try to find and install 2.10.401.1 RUU
Installing RUU will usually fix this kind of problem if the data partition is sort of corrupted but not damaged.
Click to expand...
Click to collapse
You are suggesting to install the same software version that I currently have? Where do I find it and how do I install it manually?
spiderwebmkd said:
You are suggesting to install the same software version that I currently have? Where do I find it and how do I install it manually?
Click to expand...
Click to collapse
Yeah, same version then after OTA to 2.20.401.1
You can read this - http://forum.xda-developers.com/htc...lp-thread-htc-one-m8s-to-stock-howto-t3190238
and this - http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
on how to manually install RUU
And for the RUU .. I have to check my PC for the full filename so it is easier to find link. I'll let you know tomorrow (on mobile now)
spiderwebmkd said:
I've already tried removing the SD card, and I've seen slight improvement in the app crashes, but they were still occurring. My bootloader is locked, but I'm going to unlock it now and flash a new ROM, I can't play around with it anymore
Click to expand...
Click to collapse
If thats what you want to do I'd suggest you try cm12.1 . Unfortunately its the only ROM available to us but its way better than stock in terms of performance imho. But do that if you're willing to sacrifice some things such as double tap to wake and also any 3rd party camera apps, because they crash alot and yeah no boomsound. :fingers-crossed:
bilal.fanatic said:
If thats what you want to do I'd suggest you try cm12.1 . Unfortunately its the only ROM available to us but its way better than stock in terms of performance imho. But do that if you're willing to sacrifice some things such as double tap to wake and also any 3rd party camera apps, because they crash alot and yeah no boomsound. :fingers-crossed:
Click to expand...
Click to collapse
I'll try with @ckpv5 suggestion, to install 2.10.401.1 RUU and then try OTA upgrade to 2.20.401.1. If it fails, or if it succeeds but apps are still crashing as they were before, I'll definitely switch to cm, whatever version is stable at the moment. Double tap to wake is really annoying and I don't need it, I don't use 3rd party camera apps, and I guess I'll have to live without boomsound Thanks for the tip, though.
ckpv5 said:
Yeah, same version then after OTA to 2.20.401.1
You can read this - http://forum.xda-developers.com/htc...lp-thread-htc-one-m8s-to-stock-howto-t3190238
and this - http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
on how to manually install RUU
And for the RUU .. I have to check my PC for the full filename so it is easier to find link. I'll let you know tomorrow (on mobile now)
Click to expand...
Click to collapse
I did a bit of digging, and what I found is this:
0PKVIMG_M8_QL_UL_M60_SENSE70_HTC_Europe_2.10.401.1_Radio_1.0.U20410.1 @ 60201_20.05_018_F_release_479349_combined_signed.zip
which I downloaded from https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC)
I'll wait for you to confirm that this is the one that I need, before I continue with the procedure (rename, put to SD, boot to bootloader, fastboot)
does someone have stock marshmallow twrp backup. I accidentally deleted mine and now stuck with cm only
spiderwebmkd said:
I did a bit of digging, and what I found is this:
0PKVIMG_M8_QL_UL_M60_SENSE70_HTC_Europe_2.10.401.1_Radio_1.0.U20410.1 @ 60201_20.05_018_F_release_479349_combined_signed.zip
which I downloaded from https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC)
I'll wait for you to confirm that this is the one that I need, before I continue with the procedure (rename, put to SD, boot to bootloader, fastboot)
Click to expand...
Click to collapse
I can't access that site but it is the same file that I have that I got from different link.
Yes .. use that one.
I cant update the firmware either. Stucks at 25% the same. Couldn't solve. Tried to flash the firmware mentioned above. Didnt change. :/
EDit: Nevermind it passed 25% barrier lol. 70% and installing
parser said:
I cant update the firmware either. Stucks at 25% the same. Couldn't solve. Tried to flash the firmware mentioned above. Didnt change. :/
EDit: Nevermind it passed 25% barrier lol. 70% and installing
Click to expand...
Click to collapse
It passed after you flashed the RUU? the same procedure that I'm about to do?
spiderwebmkd said:
It passed after you flashed the RUU? the same procedure that I'm about to do?
Click to expand...
Click to collapse
yep sameway. Downloaded and flashed the firmware after renaming. Downloaded the ota via software update and voila.
took a little long but worked at the and.
parser said:
yep sameway. Downloaded and flashed the firmware after renaming. Downloaded the ota via software update and voila.
took a little long but worked at the and.
Click to expand...
Click to collapse
Worked for me as well. I'm at v2.20 now, so far no app crashes, the "SD card unexpectedly removed" is still there, but I'll live. Thanks a lot @ckpv5 for your suggestion, I practically got a brand new phone now!
spiderwebmkd said:
Worked for me as well. I'm at v2.20 now, so far no app crashes, the "SD card unexpectedly removed" is still there, but I'll live. Thanks a lot @ckpv5 for your suggestion, I practically got a brand new phone now!
Click to expand...
Click to collapse
hey! can you, if you have, send me a clean backup of the v2.20. I kinda rushed in and forgot to take a backup and now I am stuck with cm :/.
parser said:
hey! can you, if you have, send me a clean backup of the v2.20. I kinda rushed in and forgot to take a backup and now I am stuck with cm :/.
Click to expand...
Click to collapse
I don't have a backup of v2.20. I flashed the v2.10 from https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC) , and then I downloaded the OTA update on top of it.
spiderwebmkd said:
https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC)
Click to expand...
Click to collapse
no no not that. I mean TWRP backup. I dont want to go back to zero relock the phone and flash the zip and re-unlock the phone root again bla bla.
Since you did the same process, I thought maybe you took a backup of the rom after you updated it.
I made a mistake by not taking a backup of it so now it is a problem for me :/
Edit: damn! thanks anyway. I have a long night in front of me clearly. I hate this phone :/
V4A is not working anymore with the latest update. Is it me or everyone has the same problem.